Professional Documents
Culture Documents
Cisco 3750 ALL Configuration Guide
Cisco 3750 ALL Configuration Guide
Configuration Guide
Cisco IOS Release 12.2(58)SE
April 2011
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
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this
URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership
relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the
document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
Preface xlvii
Audience xlvii
Purpose xlvii
Conventions xlvii
Features 1-1
Performance Features 1-2
Management Options 1-3
Manageability Features 1-3
Availability Features 1-5
VLAN Features 1-6
Layer 2 Virtual Private Network (VPN) Services 1-6
Layer 3 VPN Services 1-7
Security Features 1-7
QoS Features 1-9
Layer 3 Features 1-10
Monitoring Features 1-11
Default Settings After Initial Switch Configuration 1-12
CHAPTER 20 Configuring Flex Links and the MAC Address-Table Move Update Feature 20-1
Understanding Flex Links and the MAC Address-Table Move Update 20-1
Flex Links 20-1
VLAN Flex Link Load Balancing and Support 20-2
Flex Link Multicast Fast Convergence 20-3
Learning the Other Flex Link Port as the mortar Port 20-3
Generating IGMP Reports 20-3
Leaking IGMP Reports 20-4
MAC Address-Table Move Update 20-6
Configuring Flex Links and MAC Address-Table Move Update 20-7
Default Configuration 20-8
Configuration Guidelines 20-8
Configuring Flex Links 20-9
Configuring VLAN Load Balancing on Flex Links 20-11
Configuring the MAC Address-Table Move Update Feature 20-12
Monitoring Flex Links and the MAC Address-Table Move Update 20-14
CHAPTER 44 Configuring MPLS, MPLS VPN, MPLS OAM, and EoMPLS 44-1
APPENDIX A Working with the Cisco IOS File System, Configuration Files, and Software Images A-1
CGMP B-2
Unsupported Privileged EXEC Command B-2
Unsupported Interface Configuration Commands B-2
Debug B-2
Unsupported Privileged EXEC Commands B-2
Interfaces B-7
Unsupported Privileged EXEC Command B-7
Unsupported Global Configuration Command B-8
Unsupported Interface Configuration Commands B-8
IP Multicast Routing B-8
Unsupported Privileged EXEC Commands B-8
Unsupported Global Configuration Commands B-9
Unsupported Interface Configuration Commands B-9
IP Unicast Routing B-9
Unsupported Privileged EXEC or User EXEC Commands B-9
Unsupported Global Configuration Commands B-10
Unsupported Interface Configuration Commands B-10
Unsupported BGP Router Configuration Commands B-11
Unsupported Route Map Commands B-11
Miscellaneous B-11
Unsupported User EXEC Commands B-11
Unsupported Privileged EXEC Command B-11
Unsupported User EXEC Command B-12
Unsupported Global Configuration Commands B-12
MPLS B-12
Unsupported Privileged EXEC or User EXEC Commands B-12
Unsupported Global Configuration Commands B-12
Unsupported Interface Configuration Commands B-12
Physical Interfaces B-12
Tunnel Interfaces B-13
Unsupported Routing Commands B-13
MSDP B-13
Unsupported Privileged EXEC Commands B-13
Unsupported Global Configuration Commands B-13
QoS B-14
Unsupported Policy-Map Configuration Command B-14
RADIUS B-14
Unsupported Global Configuration Commands B-14
SNMP B-14
Unsupported Global Configuration Commands B-14
INDEX
Audience
This guide is for the networking professional managing the Catalyst 3750 Metro switch, hereafter
referred to as the switch. Before using this guide, you should have experience working with the Cisco
IOS software and be familiar with the concepts and terminology of Ethernet and local area networking.
Purpose
The Catalyst 3750 Metro switch supports a set of service-provider features, including multiprotocol
label switching (MPLS), Ethernet over MPLS (EoMPLS), hierarchical QoS, 802.1Q tunneling, and
VLAN mapping. It also supports Layer 2+ features such as access control lists (ACLs) and quality of
service (QoS) and Layer 3 features such as IP unicast routing, IP multicast routing, and fallback
bridging.
This guide provides procedures for using the commands that have been created or changed for use with
the switch. It does not provide detailed information about these commands. For detailed information
about these commands, see the Catalyst 3750 Metro Switch Command Reference for this release. For
information about the standard Cisco IOS Release 12.2 commands, see the Cisco IOS documentation set
available from the Cisco.com home page at Service and Support > Technical Documents. On the Cisco
Product Documentation home page, select Release 12.2 from the Cisco IOS Software drop-down list.
This guide does not describe system messages you might encounter or how to install your switch. For
more information, see the Catalyst 3750 Metro Switch System Message Guide for this release and to the
Catalyst 3750 Metro Switch Hardware Installation Guide.
For documentation updates, see the release notes for this release.
Conventions
This publication uses these conventions to convey instructions and information:
Command descriptions use these conventions:
• Commands and keywords are in boldface text.
• Arguments for which you supply values are in italic.
• Square brackets ([ ]) mean optional elements.
• Braces ({ }) group required choices, and vertical bars ( | ) separate the alternative elements.
• Braces and vertical bars within square brackets ([{ | }]) mean a required choice within an optional
element.
Interactive examples use these conventions:
• Terminal sessions and system displays are in screen font.
• Information you enter is in boldface screen font.
• Nonprinting characters, such as passwords or tabs, are in angle brackets (< >).
Notes, cautions, and timesavers use these conventions and symbols:
Note Means reader take note. Notes contain helpful suggestions or references to materials not contained in
this manual.
Caution Means reader be careful. In this situation, you might do something that could result in equipment
damage or loss of data.
Related Publications
These documents provide complete information about the switch and are available from this Cisco.com
site:
http://www.cisco.com/en/US/products/hw/switches/ps5532/tsd_products_support_series_home.html
Note Before installing, configuring, or upgrading the switch, see these documents:
• For initial configuration information, see the “Using Express Setup” chapter or the “Configuring the
Switch with the CLI-Based Setup Program” appendix in the hardware installation guide.
• For upgrade information, see the “Downloading Software” section in the release notes.
This chapter provides this information about Catalyst 3750 Metro switch software:
• Features, page 1-1
• Default Settings After Initial Switch Configuration, page 1-12
• Network Configuration Examples, page 1-15
• Where to Go Next, page 1-19
Features
Note Some features noted in this chapter are available only on the cryptographic (that is, supports encryption)
versions of the switch software image. You must obtain authorization to use this feature and to download
the cryptographic version of the software from Cisco.com. For more information, see the release notes
for this release.
Performance Features
• Autosensing of port speed and autonegotiation of duplex mode on all switch ports for optimizing
bandwidth
• Automatic-medium-dependent interface crossover (Auto-MDIX) capability on 10/100 Mbps
interfaces and 10/100/1000 BASE-T/TX small form-factor pluggable (SFP) interfaces that enables
the interface to automatically detect the required cable connection type (straight-through or
crossover) and configure the connection appropriately
• Support for up to 1546 bytes for routed frames, up to 9000 bytes for frames that are bridged in
hardware, and up to 2000 bytes for frames that are bridged by software
• IEEE 802.3x flow control on all ports (the switch does not send pause frames)
• EtherChannel for enhanced fault tolerance and for providing up to 2 Gbps (Gigabit EtherChannel)
or 800 Mbps (Fast EtherChannel) full duplex of bandwidth between switches, routers, and servers
• Port Aggregation Protocol (PAgP) and Link Aggregation Control Protocol (LACP) for automatic
creation of EtherChannel links
• Per-port storm control for preventing broadcast, multicast, and unicast storms
• Port blocking on forwarding unknown Layer 2 unknown unicast, multicast, and bridged broadcast
traffic
• Cisco Group Management Protocol (CGMP) server support and Internet Group Management
Protocol (IGMP) snooping for IGMP Versions 1, 2, and 3:
– (For CGMP devices) CGMP for limiting multicast traffic to specified end stations and reducing
overall network traffic
– (For IGMP devices) IGMP snooping for efficiently forwarding multimedia and multicast traffic
• Multicast VLAN registration (MVR) to continuously send multicast streams in a multicast VLAN
while isolating the streams from subscriber VLANs for bandwidth and security reasons
• MVR over trunk port (MVRoT) support to allow you to configure a trunk port as an MVR receiver
port
• IGMP filtering for controlling the set of multicast groups to which hosts on a switch port can belong
• IGMP helper to allow the switch to forward a host request to join a multicast stream to a specific IP
destination address
• IGMP throttling for configuring the action when the maximum number of entries is in the IGMP
forwarding table
• IGMP report suppression for sending only one IGMP report per multicast router query to the
multicast devices (supported only for IGMPv1 or IGMPv2 queries)
• Switch Database Management (SDM) templates for allocating system resources to maximize
support for user-selected features
• Configurable small-frame arrival threshold to prevent storm control when small frames (64 bytes or
less) arrive on an interface at a specified rate (the threshold)
• RADIUS server load balancing to allow access and authentication requests to be distributed evenly
across a server group.
• Multicast VLAN registration (MVR) enhancements include the ability to configure 2000 MVR
groups when the switch is in dynamic MVR mode and a new command (mvr ringmode flood) to
ensure that forwarding in a ring topology is limited to member ports.
• Support for configuration of an alternate MTU value to allow specific interfaces a different MTU
than the global system MTU or jumbo MTU
Management Options
• CLI—The Cisco IOS command-line interface (CLI) software is enhanced to support the
Catalyst 3750 Metro switch features. You can access the CLI either by connecting your management
station directly to the switch console port or by using Telnet from a remote management station. For
more information about the CLI, see Chapter 2, “Using the Command-Line Interface.”
• CNS—Cisco Configuration Engine is network management software that acts as a configuration
service for automating the deployment and management of network devices and services. You can
automate initial configurations and configuration updates by generating switch-specific
configuration changes, sending them to the switch, executing the configuration change, and logging
the results.
For more information about CNS, see Chapter 4, “Configuring Cisco IOS Configuration Engine.”
• SNMP—Simple Network Management Protocol (SNMP) management applications such as
CiscoWorks2000 LAN Management Suite (LMS) and HP OpenView. You can manage from an
SNMP-compatible management station that is running platforms such as HP OpenView or SunNet
Manager. The switch supports a comprehensive set of MIB extensions and four remote monitoring
(RMON) groups. You can also use the CLI to configure collection and transfer of selected MIB data
or to configure a Cisco Process MIB CPU threshold table. For more information about using SNMP,
see Chapter 31, “Configuring SNMP.”
Manageability Features
Note The encrypted Secure Shell (SSH) feature listed in this section is available only on the cryptographic
version of the switch software image.
• Cisco IE2100 Series CNS embedded agents for automating switch management, configuration
storage, and delivery
• DHCP for automating configuration of switch information (such as IP address, default gateway,
hostname, and Domain Name System [DNS] and TFTP server names)
• DHCP relay agent information (option 82) for subscriber identification and IP address management
• DHCP server for automatic assignment of IP addresses and other DHCP options to IP hosts
• DHCP server port-based address allocation for the preassignment of an IP address to a switch port
• DHCPv6 bulk-lease query to support new bulk lease query type (as defined in RFC5460)
• The DHCPv6 relay source configuration feature to configure a source address for DHCPv6 relay
agent
• Directed unicast requests to a DNS server for identifying a switch through its IP address and its
corresponding hostname and to a TFTP server for administering software upgrades from a TFTP
server
• Support for downloading a software image by using a web browser (HTTP).
• Address Resolution Protocol (ARP) for identifying a switch through its IP address and its
corresponding MAC address
• Unicast MAC address filtering to drop packets with specific source or destination MAC addresses
• Configurable MAC address scaling that allows disabling MAC address learning on a VLAN to limit
the size of the MAC address table
• Cisco Discovery Protocol (CDP) Versions 1 and 2 for network topology discovery and mapping
between the switch and other Cisco devices on the network
• Link Layer Discovery Protocol (LLDP) and LLDP Media Endpoint Discovery (LLDP-MED) for
interoperability with third-party IP phones
• CDP and LLDP enhancements for exchanging location information with video end points for
dynamic location-based content distribution from servers
• Network Time Protocol (NTP) version 4 for NTP time synchronization for both IPv4 and IPv6
• Cisco IOS File System (IFS) for providing a single interface to all file systems that the switch uses
• In-band management access for up to 16 simultaneous Telnet connections for multiple CLI-based
sessions over the network
• In-band management access for up to five simultaneous, encrypted SSH connections for multiple
CLI-based sessions over the network (requires the cryptographic version of the switch software
image)
• Support for SSH over IPv4 and IPv6
• In-band management access through SNMP Versions 1 and 2, and 3 get and set requests
• Out-of-band management access through the switch console port to a directly attached terminal or
to a remote terminal through a serial connection or a modem
• Support for metro Ethernet operation, administration, and maintenance (OAM) IEEE 802.1ag
Connectivity Fault Management (CFM), Ethernet Line Management Interface (E-LMI) on
customer-edge and provider-edge switches, and IEEE 802.3ah Ethernet OAM discovery, link
monitoring, remote fault detection, and remote loopback
• CFM support on a customer VLAN (C-VLAN), which allows a customer to provision maintenance
intermediate points (MIPs) and Up maintenance endpoints (MEPs) on a C-VLAN component to
provide a customer with visibility to network traffic on the C-VLAN
• Support for the IEEE CFM (IEEE 802.1ap) MIB, which can be used as a tool to trace paths, to verify
and to manage connectivity, and to detect faults in a network
• DHCP-based autoconfiguration and image update to download a specified configuration a new
image to a large number of switches
• Source Specific Multicast (SSM) mapping for multicast applications to provide a mapping of source
to allowing IGMPv2 clients to utilize SSM, allowing listeners to connect to multicast sources
dynamically and reducing dependencies on the application
• CPU utilization threshold trap monitors CPU utilization.
• LLDP-MED network-policy profile time, length, value (TLV) for creating a profile for voice and
voice-signalling by specifying the values for VLAN, class of service (CoS), differentiated services
code point (DSCP), and tagging mode
• Support for including a hostname in the option 12 field of DHCPDISCOVER packets. This provides
identical configuration files to be sent by using the DHCP protocol.
• DHCP Snooping enhancement to support the selection of a fixed string-based format for the
circuit-id sub-option of the Option 82 DHCP field.
Availability Features
• HSRP for command switch and Layer 3 router redundancy
• UniDirectional Link Detection (UDLD) and aggressive UDLD for detecting and disabling
unidirectional links on fiber-optic interfaces caused by incorrect fiber-optic wiring or port faults
• IEEE 802.1D Spanning Tree Protocol (STP) for redundant backbone connections and loop-free
networks. STP has these features:
– Up to 128 spanning-tree instances supported
– Per-VLAN spanning-tree plus (PVST+) for balancing load across VLANs
– Rapid PVST+ for balancing load across VLANs and providing rapid convergence of
spanning-tree instances
– UplinkFast and BackboneFast for fast convergence after a spanning-tree topology change and
for achieving load balancing between redundant uplinks, including Gigabit uplinks
• IEEE 802.1s Multiple Spanning Tree Protocol (MSTP) for grouping VLANs into a spanning-tree
instance and for providing multiple forwarding paths for data traffic and load balancing and rapid
per-VLAN Spanning-Tree plus (rapid-PVST+) based on the IEEE 802.1w Rapid Spanning Tree
Protocol (RSTP) for rapid convergence of the spanning tree by immediately transitioning root and
designated ports to the forwarding state
• Optional spanning-tree features available in PVST+, rapid-PVST+, and MSTP mode:
– Port Fast for eliminating the forwarding delay by enabling a port to immediately transition from
the blocking state to the forwarding state
– BPDU guard for shutting down Port Fast-enabled ports that receive bridge protocol data units
(BPDUs)
– BPDU filtering for preventing a Port Fast-enabled port from sending or receiving BPDUs
– Root guard for preventing switches outside the network core from becoming the spanning-tree
root
– Loop guard for preventing alternate or root ports from becoming designated ports because of a
failure that leads to a unidirectional link
• Equal-cost routing for link-level and switch-level redundancy
• Flex Link Layer 2 interfaces to back up one another as an alternative to STP for basic link
redundancy.
• Flex Link Multicast Fast Convergence to reduce the multicast traffic convergence time after a Flex
Link failure.
• Link-state tracking to mirror the state of the ports that carry upstream traffic from connected hosts,
servers, and other downstream devices. This feature allows the failover of the downstream traffic to
an operational link on another Cisco Ethernet switch.
• Support for Resilient Ethernet Protocol (REP) for improved convergence times and network loop
prevention without the use of spanning tree
• Counter and timer enhancements to REP support
• REP configuration on edge ports connected to other devices that do not support REP
• Shorter Resilient Ethernet Protocol (REP) hello: Changes the range of the REP link status layer
(LSL) age timer from 3000 to 10000 ms in 500-ms intervals to 120 to 10000 ms in 40-ms intervals.
• Call Home to provide e-mail-based and web-based notification of critical system events. Users with
a service contract directly with Cisco Systems can register Call Home devices for the Cisco Smart
Call Home service that generates automatic service requests with the Cisco TAC.
VLAN Features
• Support for up to 1005 VLANs for assigning users to VLANs associated with appropriate network
resources, traffic patterns, and bandwidth
• Support for VLAN IDs in the full 1 to 4094 range as allowed by the IEEE 802.1Q standard
• VLAN Query Protocol (VQP) for dynamic VLAN membership
• Inter-Switch Link (ISL) and IEEE 802.1Q trunking encapsulation on all ports for network moves,
adds, and changes; management and control of broadcast and multicast traffic; and network security
by establishing VLAN groups for high-security users and network resources
• Dynamic Trunking Protocol (DTP) for negotiating trunking on a link between two devices and for
negotiating the type of trunking encapsulation (802.1Q or ISL) to be used
• VLAN Trunking Protocol (VTP) and VTP pruning for reducing network traffic by restricting
flooded traffic to links destined for stations receiving the traffic
• Voice VLAN for creating subnets for voice traffic from Cisco IP Phones
• VLAN 1 minimization for reducing the risk of spanning-tree loops or storms by allowing VLAN 1
to be disabled on any individual VLAN trunk link. With this feature enabled, no user traffic is sent
or received on the trunk, but the switch CPU continues to send and receive control protocol frames.
• Private VLANs to address VLAN scalability problems, to provide a more controlled IP address
allocation, and to allow Layer 2 ports to be isolated from other ports on the switch
• VLAN mapping on enhanced-services (ES) ports to translate customer VLANs to service-provider
VLANs for transporting packets across the service-provider network without affecting the customer
VLAN IDs
• Custom ethertype to enable the user to change the ethertype value on a port to any value to direct
the tagged and untagged traffic to different VLANs (ES ports only)
• Port security on a PVLAN host to limit the number of MAC addresses learned on a port, or define
which MAC addresses may be learned on a port
• VLAN Flex Link Load Balancing to provide Layer 2 redundancy without requiring Spanning Tree
Protocol (STP). A pair of interfaces configured as primary and backup links can load balance traffic
based on VLAN.
• Intelligent 802.1Q tunneling QoS, the ability to copy the inner cost-of-service (CoS) value to the
outer CoS value for 802.1Q tunneling
• Support for Ethernet over multiprotocol layer switching (EoMPLS) tunneling mechanism for
transporting Ethernet frames over a service-provider MPLS network
• Support for Layer 2 transport over MPLS interworking for Ethernet and VLAN interworking.
• Support for the IEEE 802.1ad standard to provide VLAN scalability in provider networks, giving
provider bridges the same functionality as Layer 2 protocol tunneling (L2PT) and QinQ bridges.
Security Features
Note The Kerberos feature listed in this section is available only on the cryptographic version of the switch
software image.
• Standard and extended IP access control lists (ACLs) for defining security policies in both directions
on routed interfaces (router ACLs) and VLANs and inbound on Layer 2 interfaces (port ACLs)
• Extended MAC access control lists for defining security policies in the inbound direction on Layer 2
interfaces
• VLAN ACLs (VLAN maps) for providing intra-VLAN security by filtering traffic based on
information in the MAC, IP, and TCP/User Datagram Protocol (UDP) headers
• Source and destination MAC-based ACLs for filtering non-IP traffic
• IEEE 802.1x port-based authentication to prevent unauthorized devices (clients) from gaining
access to the network
– IEEE 802.1x with VLAN assignment for restricting 802.1x-authenticated users to a specified
VLAN
– IEEE 802.1x with port security for controlling access to 802.1x ports
– IEEE 802.1x with voice VLAN to permit an IP phone access to the voice VLAN regardless of
the authorized or unauthorized state of the port
– IEEE 802.1x with guest VLAN to provide limited services to non-802.1x-compliant users
– IEEE 802.1x accounting to track network usage.
– Network Edge Access Topology (NEAT) with 802.1X switch supplicant, host authorization
with CISP, and auto enablement to authenticate a switch outside a wiring closet as a supplicant
to another switch.
• TACACS+, a proprietary feature for managing network security through a TACACS server for both
IPv4 and IPv6
• RADIUS for verifying the identity of, granting access to, and tracking the actions of remote users
through authentication, authorization, and accounting (AAA) services for both IPv4 and IPv6
• Enhancements to RADIUS, TACACS+, and SSH to function over IPv6
• Kerberos security system to authenticate requests for network resources by using a trusted third
party (requires the cryptographic [that is, supports encryption] version of the switch software image)
• Password recovery disable capability to protect access to switches at customer sites
• DHCP snooping to filter untrusted DHCP messages between untrusted hosts and DHCP servers
• IP source guard to restrict traffic on nonrouted interfaces by filtering traffic based on the DHCP
snooping database and IP source bindings
• Dynamic ARP inspection to prevent malicious attacks on the switch by not relaying invalid ARP
requests and responses to other ports in the same VLAN
• Secure Socket Layer Version 3.0 support for the HTTP 1.1 server authentication, encryption, and
message integrity, and HTTP client authentication to allow secure HTTP communications (requires
a cryptographic version of the switch image)
• IEEE 802.1x readiness check to determine the readiness of connected end hosts before configuring
IEEE 802.1x on the switch
• Support for IP source guard on static hosts.
• IEEE 802.1x User Distribution to allow deployments with multiple VLANs (for a group of users) to
improve scalability of the network by load balancing users across different VLANs. Authorized
users are assigned to the least populated VLAN in the group, assigned by RADIUS server.
• Support for 3DES and AES with version 3 of the Simple Network Management Protocol (SNMPv3).
This release adds support for the 168-bit Triple Data Encryption Standard (3DES) and the 128-bit,
192-bit, and 256-bit Advanced Encryption Standard (AES) encryption algorithms to SNMPv3.
• Additional IPv6 support to include IPv6 eBGP, IPv6 SNMP, Syslog, and HTTP as well as IPv6 MLD
snooping.
QoS Features
• Standard QoS to classify, police, mark, queue, and schedule incoming traffic on a standard port or
on an ES port, as well as queue and schedule outgoing traffic on a standard port
Classification
– IP type-of-service/Differentiated Services Code Point (IP ToS/DSCP) and 802.1p CoS marking
priorities on a per-port basis for protecting the performance of mission-critical applications
– IP ToS/DSCP and 802.1p CoS marking based on flow-based packet classification (classification
based on information in the MAC, IP, and TCP/UDP headers) for high-performance quality of
service at the network edge, allowing for differentiated service levels for different types of
network traffic and for prioritizing mission-critical traffic in the network
– Trusted port states (CoS, DSCP, and IP precedence) within a QoS domain and with a port
bordering another QoS domain
– Trusted boundary for detecting the presence of a Cisco IP phone, trusting the CoS value
received, and ensuring port security
– DSCP transparency to prevent the switch from rewriting the DSCP field in the user IP packet
when QoS is enabled
Policing and out-of-profile marking
– Traffic-policing policies on the switch port for managing how much of the port bandwidth
should be allocated to a specific traffic flow (single-rate traffic policing)
– Aggregate policing for policing traffic flows in aggregate to restrict specific applications or
traffic flows to metered, predefined rates
– Out-of-profile markdown for packets that exceed bandwidth utilization limits (drop policy
actions are passing through the packet without modification, marking down the assigned DSCP
in the packet, or dropping the packet)
Ingress queueing and scheduling
– Two configurable ingress queues for user traffic (one queue can be the priority queue)
– Weighted tail drop (WTD) as the congestion-avoidance mechanism for managing the queue
lengths and providing drop precedences for different traffic classifications
– Shaped round robin (SRR) as the scheduling service for determining the rate at which packets
are dequeued to the internal ring (sharing is the only supported mode on ingress queues)
Egress queues and scheduling
– Four egress queues per port
– An egress priority queue on a standard port. Shaped round robin (SRR) services the priority
queue until it is empty before servicing the other three queues
– WTD as the congestion-avoidance mechanism for managing the queue lengths and providing
drop precedences for different traffic classifications
– SRR as the scheduling service for determining the rate at which packets are dequeued to the
egress interface (shaping or sharing is supported on egress queues). Shaped egress queues are
guaranteed but limited to using a share of port bandwidth. Shared egress queues are also
guaranteed a configured share of bandwidth, but can use more than the guarantee if other queues
become empty and do not use their share of the bandwidth.
– Configurable control-plane queue assignment to assign control plane traffic for CPU-generated
traffic to a specific egress queue
• Hierarchical QoS on ES ports or EtherChannels containing ES ports to classify, police, mark, queue,
and schedule incoming or outgoing traffic
Classification
– Three QoS configuration levels in the hierarchy: class, VLAN, and physical interface
– Classification based on the CoS value, the DSCP value, the IP precedence value, the MPLS
experimental (EXP) bits, or the VLAN
Policing and out-of-profile marking
– Two-rate traffic policing based on the committed information rate (CIR) and the peak
information rate (PIR)
– Out-of-profile markdown for packets that exceed bandwidth utilization limits (policy actions
are to send packets that conform without modification, to mark down the priority of packets that
exceed, and to drop packets that violate)
Egress queueing and scheduling
– Each packet assigned to an egress queue based on the traffic class and VLAN
– Weighted Random Early Detection (WRED) as the congestion-avoidance mechanism
– Class-based weighted fair queueing (CBWFQ) as a queue scheduling management feature to
provide guaranteed bandwidth to particular traffic classes, such as voice, that are delay
sensitive, while still fairly serving all other traffic in the network
– Low-latency queueing (LLQ) as a scheduling congestion-management feature to provide
strict-priority queueing for a traffic class and to enable delay-sensitive data, such as voice, to be
sent before packets in other queues are sent
– Traffic shaping to decrease the burstiness of Internet traffic
• Automatic QoS (auto-QoS) to simplify the deployment of existing QoS features by classifying
traffic and configuring egress queues
• Support for IPv6 QoS trust capability
• Support for IPv6 features with Catalyst 3750 Metro ES-port specific features, such as hierarchical
QoS
Layer 3 Features
• HSRP Version 1 (HSRPv1) and HSRP Version 2 (HSRPv2) for Layer 3 router redundancy
• Support for the Virtual Router Redundancy Protocol (VRRP) for IPv4, which dynamically assigns
responsibility for one or more virtual routers to the VRRP routers on a LAN, allowing multiple
routers on a multiaccess link to utilize the same virtual IP address
• Support for IPv4 and IPv6 Gateway Load Balancing Protocol (GLBP) for automatic router backup
for IP hosts configured with a single default gateway on a LAN
• IP routing protocols for load balancing and for constructing scalable, routed backbones:
– RIP Versions 1 and 2
– OSPF
– Enhanced Interior Gateway Routing Protocol GRP (EIGRP)
– Border Gateway Protocol (BGP) Version 4
– International Organization for Standardization (ISO) Connectionless Network Service (CLNS).
The switch supports ISO Interior Gateway Routing Protocol (IGRP) and Intermediate
System-to-Intermediate System (IS-IS) routing
– Bidirectional Forwarding Detection (BFD) Protocol to detect forwarding-path failures for
OSPF, IS-IS, BGP, EIGRP, or HSRP routing protocols
– Support for the BFD Protocol on SVIs
• IP routing between VLANs (inter-VLAN routing) for full Layer 3 routing between two or more
VLANs, allowing each VLAN to maintain its own autonomous data-link domain
• Policy-based routing (PBR) for configuring defined policies for traffic flows
• Multiple VPN routing/forwarding (multi-VRF) instances in customer edge (CE) devices to allow
service providers to support multiple virtual private networks (VPNs) and overlap IP addresses
between VPNs (requires the EMI)
• Fallback bridging for forwarding non-IP traffic between two or more VLANs
• Static IP routing for manually building a routing table of network path information
• Equal-cost routing for load balancing and redundancy
• Internet Control Message Protocol (ICMP) and ICMP Router Discovery Protocol (IRDP) for using
router advertisement and router solicitation messages to discover the addresses of routers on directly
attached subnets
• Protocol-Independent Multicast (PIM) for multicast routing within the network, allowing for
devices in the network to receive the multicast feed requested and for switches not participating in
the multicast to be pruned. Includes support for PIM sparse mode (PIM-SM), PIM dense mode
(PIM-DM), and PIM sparse-dense mode.
• Multicast Source Discovery Protocol (MSDP) for connecting multiple PIM-SM domains
• Distance Vector Multicast Routing Protocol (DVMRP) tunnelling for interconnecting two
multicast-enabled networks across non-multicast networks
• DHCP relay for forwarding UDP broadcasts, including IP address requests, from DHCP clients
• Support for IPv6 unicast routing, neighbor discovery, default router preference, DHCP server and
relay, IPv6 eBGP, IPv6 SNMP, Syslog, and HTTP as well as IPv6 MLD snooping. Also supports
IPv6 QoS trust functionality.
Monitoring Features
• Switch LEDs that provide port- and switch-level status
• MAC address notification traps and RADIUS accounting for tracking users on a network by storing
the MAC addresses that the switch has learned or removed
• Switched Port Analyzer (SPAN) and Remote SPAN (RSPAN) for traffic monitoring on any standard
port or VLAN.
• SPAN and RSPAN support of Intrusion Detection Systems (IDS) to monitor, repel, and report
network security violations
• Four groups (history, statistics, alarms, and events) of embedded RMON agents for network
monitoring and traffic analysis
• Syslog facility for logging system messages about authentication or authorization errors, resource
issues, and time-out events
• VACL Logging to generate syslog messages for ACL denied IP packets
• Layer 2 traceroute to identify the physical path that a packet takes from a source device to a
destination device
• SFP module diagnostic management interface to monitor physical or operational status of an SFP
module.
• Enhanced object tracking for HSRP or IP SLAs clients
• EOT and IP SLAs EOT static route support to identify when a preconfigured static route or a DHCP
route goes down
• Support for EEM 3.2, which introduces event detectors for Neighbor Discovery, Identity, and
MAC-Address-Table.
• Support for the TWAMP standard for measuring round-trip network performance between any two
devices that support the protocol.
MVR Disabled
IGMP throttling Deny Chapter 23, “Configuring IGMP
Snooping and MVR”
Port-based Traffic
Broadcast, multicast, and unicast storm Disabled Chapter 24, “Configuring Port-Based
control Traffic Control”
Protected ports None defined
Unicast and multicast traffic flooding Not blocked
Secure ports None configured
CDP Enabled Chapter 25, “Configuring CDP”
UDLD Disabled Chapter 27, “Configuring UDLD”
SPAN and RSPAN Disabled Chapter 28, “Configuring SPAN and
RSPAN”
RMON Disabled Chapter 29, “Configuring RMON”
Syslog messages Enabled; displayed on the console Chapter 30, “Configuring System
Message Logging”
SNMP Enabled; Version 1 Chapter 31, “Configuring SNMP”
ACLs None configured Chapter 33, “Configuring Network
Security with ACLs”
QoS Disabled Chapter 34, “Configuring QoS”
EtherChannels None configured Chapter 35, “Configuring EtherChannels
and Link-State Tracking”
IP unicast routing
IP routing (and routing protocols) Disabled Chapter 36, “Configuring IP Unicast
Multi-VRF-CE Disabled Routing”
MPLS services
Label switching Globally enabled; disabled per Chapter 44, “Configuring MPLS, MPLS
interface VPN, MPLS OAM, and EoMPLS”
EoMPLS Not configured
MPLS QoS Disabled
H-VPLS No VFIs configured
unauthorized devices from becoming the STP root switch. All ports have IGMP snooping or CGMP
enabled for multicast traffic management. ACLs on the uplink ports to the aggregating switches provide
security and bandwidth management.
The aggregating switches and routers have HSRP enabled for load balancing and redundant connectivity
to guarantee mission-critical traffic. This ensures connectivity to the Internet, WAN, and mission-critical
network resources in case one of the routers or switches fails.
When an end station in one VLAN needs to communicate with an end station in another VLAN, a router
or switch routes the traffic to the appropriate destination VLAN, providing inter-VLAN routing. VLAN
access control lists (VLAN maps) provide intra-VLAN security and prevent unauthorized users from
accessing critical pieces of the network.
In addition to inter-VLAN routing, the switch QoS mechanisms such as DSCP prioritize the different
types of network traffic to deliver high-priority traffic in a predictable manner. If congestion occurs, QoS
drops low-priority traffic to allow delivery of high-priority traffic.
The routers also provide firewall services, Network Address Translation (NAT) services, voice-over-IP
(VoIP) gateway services, and WAN and Internet access.
Cisco routers
Service
Provider
POP
Catalyst 6500 switches
Residential
Residential gateways (hubs) location
PC PC
101094
TV TV
Customer building
Customer building
CPE
VRF
interface VLAN 50-120
CPE
Customer SP VLAN 8 Corp B, site 2
VLAN 35-60 SP VLAN 5 PE-CLE CPE
PE-CLE
PE-CLE PE-CLE
VPN_B
VPN_A
CE
P P CE
LDP
VPN_A
CE
PE-CLE P P PE-CLE
VPN_B VPN_B
MP-BGP
CE sessions CE
CE = Customer edge switch
P = Provider router
122009
PE-CLE = Provider edge customer-located
equipment (Catalyst 3750 Metro switch)
See Chapter 44, “Configuring MPLS, MPLS VPN, MPLS OAM, and EoMPLS,” for more information
on configuring MPLS VPN.
Where to Go Next
Before configuring the switch, review these sections for startup information:
• Chapter 2, “Using the Command-Line Interface”
• Chapter 3, “Assigning the Switch IP Address and Default Gateway”
• Chapter 4, “Configuring Cisco IOS Configuration Engine”
To locate and download MIBs for a specific Cisco product and release, use the Cisco MIB Locator:
http://cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
This chapter describes the Cisco IOS command-line interface (CLI) and how to use it to configure your
Catalyst 3750 Metro switch. It contains these sections:
• Understanding Command Modes, page 2-1
• Understanding the Help System, page 2-3
• Understanding Abbreviated Commands, page 2-3
• Understanding no and default Forms of Commands, page 2-4
• Understanding CLI Error Messages, page 2-4
• Using Command History, page 2-4
• Using Editing Features, page 2-6
• Searching and Filtering Output of show and more Commands, page 2-8
• Accessing the CLI, page 2-9
For more detailed information on the command modes, see the command reference for this release.
Command Purpose
help Obtain a brief description of the help system in any command mode.
abbreviated-command-entry? Obtain a list of commands that begin with a particular character string.
For example:
Switch# di?
dir disable disconnect
abbreviated-command-entry<Tab> Complete a partial command name.
For example:
Switch# sh conf<tab>
Switch# show configuration
? List all commands available for a particular command mode.
For example:
Switch> ?
command ? List the associated keywords for a command.
For example:
Switch> show ?
command keyword ? List the associated arguments for a keyword.
For example:
Switch(config)# cdp holdtime ?
<10-255> Length of time (in sec) that receiver must keep this packet
Recalling Commands
To recall commands from the history buffer, perform one of the actions listed in Table 2-4. These actions
are optional.
Action1 Result
Press Ctrl-P or the up arrow key. Recall commands in the history buffer, beginning with the most recent command.
Repeat the key sequence to recall successively older commands.
Press Ctrl-N or the down arrow key. Return 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.
show history While in privileged EXEC mode, list the last several commands that you just
entered. The number of commands that are displayed is controlled by the terminal
history global configuration command and history line configuration command.
1. The arrow keys function only on ANSI-compatible terminals such as VT100s.
To re-enable the enhanced editing mode for the current terminal session, enter this command in
privileged EXEC mode:
Switch# terminal editing
To reconfigure a specific line to have enhanced editing mode, enter this command in line configuration
mode:
Switch(config-line)# editing
Note The arrow keys function only on ANSI-compatible terminals such as VT100s.
In this example, the access-list global configuration command entry extends beyond one line. When the
cursor first reaches the end of the line, the line is shifted ten spaces to the left and redisplayed. The dollar
sign ($) shows that the line has been scrolled to the left. Each time the cursor reaches the end of the line,
the line is again shifted ten spaces to the left.
Switch(config)# access-list 101 permit tcp 131.108.2.5 255.255.255.0 131.108.1
Switch(config)# $ 101 permit tcp 131.108.2.5 255.255.255.0 131.108.1.20 255.25
Switch(config)# $t tcp 131.108.2.5 255.255.255.0 131.108.1.20 255.255.255.0 eq
Switch(config)# $108.2.5 255.255.255.0 131.108.1.20 255.255.255.0 eq 45
After you complete the entry, press Ctrl-A to check the complete syntax before pressing the Return key
to execute the command. The dollar sign ($) appears at the end of the line to show that the line has been
scrolled to the right:
Switch(config)# access-list 101 permit tcp 131.108.2.5 255.255.255.0 131.108.1$
The software assumes you have a terminal screen that is 80 columns wide. If you have a width other than
that, use the terminal width privileged EXEC command to set the width of your terminal.
Use line wrapping with the command history feature to recall and modify previous complex command
entries. For information about recalling previous command entries, see the “Editing Commands through
Keystrokes” section on page 2-6.
This chapter describes how to create the initial switch configuration (for example, assigning the switch
IP address and default gateway information) for the Catalyst 3750 Metro switch by using a variety of
automatic and manual methods. It also describes how to modify the switch startup configuration.
Note For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release and to the Cisco IOS IP Command Reference, Volume 1 of 3: Addressing and
Services, Release 12.2.
The boot loader provides access to the flash file system before the operating system is loaded. Normally,
the boot loader is used only to load, uncompress, and launch the operating system. After the boot loader
gives the operating system control of the CPU, the boot loader is not active until the next system reset
or power-on.
The boot loader also provides trap-door access into the system if the operating system has problems
serious enough that it cannot be used. The trap-door mechanism provides enough access to the system
so that if it is necessary, you can format the flash file system, reinstall the operating system software
image by using the XMODEM Protocol, recover from a lost or forgotten password, and finally restart
the operating system. For more information, see the “Recovering from Corrupted Software By Using the
XMODEM Protocol” section on page 48-2 and the “Recovering from a Lost or Forgotten Password”
section on page 48-3.
Note You can disable password recovery. For more information, see the “Disabling Password Recovery”
section on page 7-5.
Before you can assign switch information, make sure you have connected a PC or terminal to the console
port, and configured the PC or terminal-emulation software baud rate and character format to match
these of the switch console port:
• Baud rate default is 9600.
• Data bits default is 8.
Note If the data bits option is set to 8, set the parity option to none.
Note If you are using DHCP, do not respond to any of the questions in the setup program until the switch
receives the dynamically-assigned IP address and reads the configuration file.
If you are an experienced user familiar with the switch configuration steps, manually configure the
switch. Otherwise, use the setup program described previously.
DHCPDISCOVER (broadcast)
Switch A DHCPOFFER (unicast) DHCP server
DHCPREQUEST (broadcast)
DHCPACK (unicast)
51807
The client, Switch A, broadcasts a DHCPDISCOVER message to locate a DHCP server. The DHCP
server offers configuration parameters (such as an IP address, subnet mask, gateway IP address, DNS IP
address, a lease for the IP address, and so forth) to the client in a DHCPOFFER unicast message.
In a DHCPREQUEST broadcast message, the client returns a formal request for the offered
configuration information to the DHCP server. The formal request is broadcast so that all other DHCP
servers that received the DHCPDISCOVER broadcast message from the client can reclaim the IP
addresses that they offered to the client.
The DHCP server confirms that the IP address has been allocated to the client by returning a DHCPACK
unicast message to the client. With this message, the client and server are bound, and the client uses
configuration information received from the server. The amount of information the switch receives
depends on how you configure the DHCP server. For more information, see the “Configuring the DHCP
Server” section on page 21-10.
If the configuration parameters sent to the client in the DHCPOFFER unicast message are invalid (a
configuration error exists), the client returns a DHCPDECLINE broadcast message to the DHCP server.
The DHCP server sends the client a DHCPNAK denial broadcast message, which means that the offered
configuration parameters have not been assigned, that an error has occurred during the negotiation of the
parameters, or that the client has been slow in responding to the DHCPOFFER message (the DHCP
server assigned the parameters to another client).
A DHCP client might receive offers from multiple DHCP or BOOTP servers and can accept any of the
offers; however, the client usually accepts the first offer it receives. The offer from the DHCP server is
not a guarantee that the IP address is allocated to the client; however, the server usually reserves the
address until the client has had a chance to formally request the address. If the switch accepts replies
from a BOOTP server and configures itself, the switch broadcasts, instead of unicasts, TFTP requests to
obtain the switch configuration file.
The DHCP hostname option allows a group of switches to obtain hostnames and a standard configuration
from the central management DHCP server. A client (switch) includes in its DCHPDISCOVER message
an option 12 field used to request a hostname and other configuration parameters from the DHCP server.
The configuration files on all clients are identical except for their DHCP-obtained hostnames.
If a client has a default hostname (the hostname name global configuration command is not configured
or the no hostname global configuration command is entered to remove the hostname), the DHCP
hostname option is not included in the packet when you enter the ip address dhcp interface
configuration command. In this case, if the client receives the DCHP hostname option from the DHCP
interaction while acquiring an IP address for an interface, the client accepts the DHCP hostname option
and sets the flag to show that the system now has a hostname configured.
DHCP Autoconfiguration
DHCP autoconfiguration downloads a configuration file to one or more switches in your network from
a DHCP server. The downloaded configuration file becomes the running configuration of the switch. It
does not over write the bootup configuration saved in the flash, until you reload the switch.
Note To enable a DHCP auto-image update on the switch, the TFTP server where the image and configuration
files are located must be configured with the correct option 67 (the configuration filename), option 66
(the DHCP server hostname) option 150 (the TFTP server address), and option 125 (description of the
file) settings.
For procedures to configure the switch as a DHCP server, see the “Configuring DHCP-Based
Autoconfiguration” section on page 3-6 and the “Configuring DHCP” section of the “IP addressing and
Services” section of the Cisco IOS IP Configuration Guide, Release 12.2.
After you install the switch in your network, the auto-image update feature starts. The downloaded
configuration file is saved in the running configuration of the switch, and the new image is downloaded
and installed on the switch. When you reboot the switch, the configuration is stored in the saved
configuration on the switch.
• The auto-install process stops if a configuration file cannot be downloaded or it the configuration
file is corrupted.
Note The configuration file that is downloaded from TFTP is merged with the existing configuration in the
running configuration but is not saved in the NVRAM unless you enter the write memory or
copy running-configuration startup-configuration privileged EXEC command. Note that if the
downloaded configuration is saved to the startup configuration, the feature is not triggered during
subsequent system restarts.
If you do not configure the DHCP server with the lease options described previously, it replies to client
requests with only those parameters that are configured. If the IP address and the subnet mask are not in
the reply, the switch is not configured. If the router IP address or the TFTP server name are not found,
the switch might send broadcast, instead of unicast, TFTP requests. Unavailability of other lease options
does not affect autoconfiguration.
The switch can act as a DHCP server. By default, the Cisco IOS DHCP server and relay agent features
are enabled on your switch but are not configured. These features are not operational. If your DHCP
server is a Cisco device, for additional information about configuring DHCP, see the “Configuring
DHCP” section of the “IP Addressing and Services” section of the Cisco IOS IP Configuration Guide
from the Cisco.com page under Documentation > Cisco IOS Software > 12.2 Mainline >
Configuration Guides.
The DNS server can be on the same or on a different LAN as the switch. If it is on a different LAN, the
switch must be able to access it through a router.
On interface 20.0.0.1
router(config-if)# ip helper-address 10.0.0.1
10.0.0.2
10.0.0.1 20.0.0.1
• The IP address and the configuration filename is reserved for the switch, but the TFTP server
address is not provided in the DHCP reply (one-file read method).
The switch receives its IP address, subnet mask, and the configuration filename from the DHCP
server. The switch sends a broadcast message to a TFTP server to retrieve the named configuration
file from the base directory of the server, and upon receipt, completes its boot-up process.
• Only the IP address is reserved for the switch and provided in the DHCP reply. The configuration
filename is not provided (two-file read method).
The switch receives its IP address, subnet mask, and the TFTP server address from the DHCP server.
The switch sends a unicast message to the TFTP server to retrieve the network-confg or cisconet.cfg
default configuration file. (If the network-confg file cannot be read, the switch reads the cisconet.cfg
file.)
The default configuration file contains the hostnames-to-IP-address mapping for the switch. The
switch fills its host table with the information in the file and obtains its hostname. If the hostname
is not found in the file, the switch uses the hostname in the DHCP reply. If the hostname is not
specified in the DHCP reply, the switch uses the default Switch as its hostname.
After obtaining its hostname from the default configuration file or the DHCP reply, the switch reads
the configuration file that has the same name as its hostname (hostname-confg or hostname.cfg,
depending on whether network-confg or cisconet.cfg was read earlier) from the TFTP server. If the
cisconet.cfg file is read, the filename of the host is truncated to eight characters.
If the switch cannot read the network-confg, cisconet.cfg, or the hostname file, it reads the
router-confg file. If the switch cannot read the router-confg file, it reads the ciscortr.cfg file.
Note The switch broadcasts TFTP server requests if the TFTP server is not obtained from the DHCP replies,
if all attempts to read the configuration file through unicast transmissions fail, or if the TFTP server
name cannot be resolved to an IP address.
Example Configuration
Figure 3-3 shows a sample network for retrieving IP information by using DHCP-based autoconfiguration.
Cisco router
10.0.0.10
Table 3-2 shows the configuration of the reserved leases on the DHCP server.
• It reads the configuration file that corresponds to its hostname; for example, it reads switcha-confg
from the TFTP server.
Switches B through D retrieve their configuration files and IP addresses in the same way.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip dhcp poolname Create a name for the DHCP Server address pool, and enter DHCP
pool configuration mode.
Step 3 bootfile filename Specify the name of the configuration file that is used as a boot image.
Step 4 network network-number mask Specify the subnet network number and mask of the DHCP address
prefix-length pool.
Note The prefix length specifies the number of bits that comprise
the address prefix. The prefix is an alternative way of
specifying the network mask of the client. The prefix length
must be preceded by a forward slash (/).
Step 5 default-router address Specify the IP address of the default router for a DHCP client.
Step 6 option 150 address Specify the IP address of the TFTP server.
Step 7 exit Return to global configuration mode.
Step 8 tftp-server flash:filename.text Specify the configuration file on the TFTP server.
Step 9 interface interface-id Specify the address of the client that will receive the configuration
file.
Step 10 no switchport Put the interface into Layer 3 mode.
Step 11 ip address address mask Specify the IP address and mask for the interface.
Step 12 end Return to privileged EXEC mode.
Step 13 copy running-config startup-config (Optional) Save your entries in the configuration file.
This example shows how to configure a switch as a DHCP server so that it will download a
configuration file:
Switch# configure terminal
Switch(config)# ip dhcp pool pool1
Switch(dhcp-config)# network 10.10.10.0 255.255.255.0
Switch(dhcp-config)# bootfile config-boot.text
Switch(dhcp-config)# default-router 10.10.10.1
Switch(dhcp-config)# option 150 10.10.10.1
Switch(dhcp-config)# exit
Switch(config)# tftp-server flash:config-boot.text
Switch(config)# interface gigabitethernet1/0/4
Switch(config-if)# no switchport
Switch(config-if)# ip address 10.10.10.1 255.255.255.0
Switch(config-if)# end
Note Before following the steps in this table, you must create a text file (for example, autoinstall_dhcp) that
will be uploaded to the switch. In the text file, put the name of the image that you want to download (for
example, c3750m-ipservices-mz.122-44.3.SE.tar). This image must be a tar and not a bin file.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip dhcp pool name Create a name for the DHCP server address pool and enter DHCP pool
configuration mode.
Step 3 bootfile filename Specify the name of the file that is used as a boot image.
Step 4 network network-number mask Specify the subnet network number and mask of the DHCP address pool.
prefix-length
Note The prefix length specifies the number of bits that comprise the
address prefix. The prefix is an alternative way of specifying the
network mask of the client. The prefix length must be preceded
by a forward slash (/).
Step 5 default-router address Specify the IP address of the default router for a DHCP client.
Step 6 option 150 address Specify the IP address of the TFTP server.
Step 7 option 125 hex Specify the path to the text file that describes the path to the image file.
Step 8 copy tftp flash filename.txt Upload the text file to the switch.
Step 9 copy tftp flash imagename.tar Upload the tar file for the new image to the switch.
Step 10 exit Return to global configuration mode.
Step 11 tftp-server flash:config.text Specify the Cisco IOS configuration file on the TFTP server.
Step 12 tftp-server flash:imagename.tar Specify the image name on the TFTP server.
Step 13 tftp-server flash:filename.txt Specify the text file that contains the name of the image file to download
Step 14 interface interface-id Specify the address of the client that will receive the configuration file.
Command Purpose
Step 15 no switchport Put the interface into Layer 3 mode.
Step 16 ip address address mask Specify the IP address and mask for the interface.
Step 17 end Return to privileged EXEC mode.
Step 18 copy running-config startup-config (Optional) Save your entries in the configuration file.
This example shows how to configure a switch as a DHCP server so it downloads a configuration file:
Switch# config terminal
Switch(config)# ip dhcp pool pool1
Switch(dhcp-config)# network 10.10.10.0 255.255.255.0
Switch(dhcp-config)# bootfile config-boot.text
Switch(dhcp-config)# default-router 10.10.10.1
Switch(dhcp-config)# option 150 10.10.10.1
Switch(dhcp-config)# option 125 hex
0000.0009.0a05.08661.7574.6f69.6e73.7461.6c6c.5f64.686370
Switch(dhcp-config)# exit
Switch(config)# tftp-server flash:config-boot.text
Switch(config)# tftp-server flash:c3750m-ipservices-mz.122-44.3.SE.tar
Switch(config)# tftp-server flash:boot-config.text
Switch(config)# tftp-server flash: autoinstall_dhcp
Switch(config)# interface gigabitEthernet1/0/4
Switch(config-if)# no switchport
Switch(config-if)# ip address 10.10.10.1 255.255.255.0
Switch(config-if)# end
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 boot host dhcp Enable autoconfiguration with a saved configuration.
Step 3 boot host retry timeout timeout-value (Optional) Set the amount of time the system tries to
download a configuration file.
Note If you do not set a timeout the system will
indefinitely try to obtain an IP address from the
DHCP server.
Step 4 banner config-save ^C warning-message ^C (Optional) Create warning messages to be displayed
when you try to save the configuration file to NVRAM.
Step 5 end Return to privileged EXEC mode.
Step 6 show boot Verify the configuration.
This example uses a Layer 3 SVI interface on VLAN 99 to enable DHCP-based autoconfiguration with
a saved configuration:
Switch# configure terminal
Switch(conf)# boot host dhcp
Switch(conf)# boot host retry timeout 300
Switch(conf)# banner config-save ^C Caution - Saving Configuration File to NVRAM May Cause
You to Nolonger Automatically Download Configuration Files at Reboot^C
Switch(config)# vlan 99
Switch(config-vlan)# interface vlan 99
Switch(config-if)# no shutdown
Switch(config-if)# end
Switch# show boot
BOOT path-list:
Config file: flash:/config.text
Private Config file: flash:/private-config.text
Enable Break: no
Manual Boot: no
HELPER path-list:
NVRAM/Config file
buffer size: 32768
Timeout for Config
Download: 300 seconds
Config Download
via DHCP: enabled (next boot: enabled)
Switch#
Note You should only configure and enable the Layer 3 interface. Do not assign an IP address or DHCP-based
autoconfiguration with a saved configuration.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface vlan vlan-id Enter interface configuration mode, and enter the VLAN to which the IP
information is assigned. The range is 1 to 4094; do not enter leading
zeros.
Step 3 ip address ip-address subnet-mask Enter the IP address and subnet mask.
Step 4 exit Return to global configuration mode.
Step 5 ip default-gateway ip-address Enter the IP address of the next-hop router interface that is directly
connected to the switch where a default gateway is being configured. The
default gateway receives IP packets with unresolved destination IP
addresses from the switch.
Once the default gateway is configured, the switch has connectivity to the
remote networks with which a host needs to communicate.
Note When your switch is configured to route with IP, it does not need
to have a default gateway set.
Step 6 end Return to privileged EXEC mode.
Step 7 show running-config Verify your entries.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove the switch IP address, use the no ip address interface configuration command. If you are
removing the address through a Telnet session, your connection to the switch will be lost. To remove the
default gateway address, use the no ip default-gateway global configuration command.
For information on setting the switch system name, protecting access to privileged EXEC commands,
and setting time and calendar services, see Chapter 5, “Administering the Switch.”
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 boot config-file flash:/file-url Specify the configuration file to load during the next boot cycle.
For file-url, specify the path (directory) and the configuration filename.
Filenames and directory names are case sensitive.
Step 3 end Return to privileged EXEC mode.
Step 4 show boot Verify your entries.
The boot config-file global configuration command changes the setting of
the CONFIG_FILE environment variable.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default setting, use the no boot config-file global configuration command.
Booting Manually
By default, the switch automatically boots; however, you can configure it to manually boot.
Beginning in privileged EXEC mode, follow these steps to configure the switch to manually boot during
the next boot cycle:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 boot manual Enable the switch to manually boot during the next boot cycle.
Step 3 end Return to privileged EXEC mode.
Step 4 show boot Verify your entries.
The boot manual global command changes the setting of the
MANUAL_BOOT environment variable.
The next time you reboot the system, the switch is in boot loader mode,
shown by the switch: prompt. To boot the system, use the boot
filesystem:/file-url boot loader command.
• For filesystem:, use flash: for the system board flash device.
• For file-url, specify the path (directory) and the name of the bootable
image.
Filenames and directory names are case sensitive.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable manual booting, use the no boot manual global configuration command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 boot system filesystem:/file-url Configure the switch to boot a specific image in flash memory during the
next boot cycle.
• For filesystem:, use flash: for the system board flash device.
• For file-url, specify the path (directory) and the name of the bootable
image.
Filenames and directory names are case sensitive.
Command Purpose
Step 3 end Return to privileged EXEC mode.
Step 4 show boot Verify your entries.
The boot system global command changes the setting of the BOOT
environment variable.
During the next boot cycle, the switch attempts to automatically boot the
system using information in the BOOT environment variable.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default setting, use the no boot system global configuration command.
Note For complete syntax and usage information for the boot loader commands and environment variables,
see the command reference for this release.
Table 3-4 describes the function of the most common environment variables.
This command schedules a reload of the software to take affect in the specified minutes or hours and
minutes. The reload must take place within approximately 24 days. You can specify the reason for
the reload in a string up to 255 characters in length.
• reload at hh:mm [month day | day month] [text]
This command schedules a reload of the software to take place at the specified time (using a 24-hour
clock). If you specify the month and day, the reload is scheduled to take place at the specified time
and date. If you do not specify the month and day, the reload takes place at the specified time on the
current day (if the specified time is later than the current time) or on the next day (if the specified
time is earlier than the current time). Specifying 00:00 schedules the reload for midnight.
Note Use the at keyword only if the switch system clock has been set (through Network Time
Protocol (NTP), the hardware calendar, or manually). The time is relative to the configured
time zone on the switch. To schedule reloads across several switches to occur
simultaneously, the time on each switch must be synchronized with NTP.
The reload command halts the system. If the system is not set to manually boot, it reboots itself. Use the
reload command after you save the switch configuration information to the startup configuration (copy
running-config startup-config).
If your switch is configured for manual booting, do not reload it from a virtual terminal. This restriction
prevents the switch from entering the boot loader mode and thereby taking it from the remote user’s
control.
If you modify your configuration file, the switch prompts you to save the configuration before reloading.
During the save operation, the system requests whether you want to proceed with the save if the
CONFIG_FILE environment variable points to a startup configuration file that no longer exists. If you
proceed in this situation, the system enters setup mode upon reload.
This example shows how to reload the software on the switch on the current day at 7:30 p.m:
Switch# reload at 19:30
Reload scheduled for 19:30:00 UTC Wed Jun 5 2003 (in 2 hours and 25 minutes)
Proceed with reload? [confirm]
This example shows how to reload the software on the switch at a future time:
Switch# reload at 02:00 jun 20
Reload scheduled for 02:00:00 UTC Thu Jun 20 2003 (in 344 hours and 53 minutes)
Proceed with reload? [confirm]
To cancel a previously scheduled reload, use the reload cancel privileged EXEC command.
This chapter describes how to configure the feature on the Catalyst 3750 Metro switch.
Note For complete configuration information for the Cisco Configuration Engine, go to
http://www.cisco.com/en/US/products/sw/netmgtsw/ps4617/tsd_products_support_series_home.html
For complete syntax and usage information for the commands used in this chapter, go to the Cisco IOS
Network Management Command Reference, Release 12.4 at
http://www.cisco.com/en/US/docs/ios/netmgmt/command/reference/nm_book.html
Data service
Configuration directory
engine
Configuration server
Event service
Web-based
user interface
141327
Order entry
configuration management
Configuration Service
The Configuration Service is the core component of the Cisco Configuration Engine. It consists of a
configuration server that works with Cisco IOS CNS agents on the switch. The Configuration Service
delivers device and service configurations to the switch for initial configuration and mass
reconfiguration by logical groups. Switches receive their initial configuration from the Configuration
Service when they start up on the network for the first time.
The Configuration Service uses the CNS Event Service to send and receive configuration change events
and to send success and failure notifications.
The configuration server is a web server that uses configuration templates and the device-specific
configuration information stored in the embedded (standalone mode) or remote (server mode) directory.
Configuration templates are text files containing static configuration information in the form of CLI
commands. In the templates, variables are specified using Lightweight Directory Access Protocol
(LDAP) URLs that reference the device-specific configuration information stored in a directory.
The Cisco IOS agent can perform a syntax check on received configuration files and publish events to
show the success or failure of the syntax check. The configuration agent can either apply configurations
immediately or delay the application until receipt of a synchronization event from the configuration
server.
Event Service
The Cisco Configuration Engine uses the Event Service for receipt and generation of configuration
events. The event agent is on the switch and facilitates the communication between the switch and the
event gateway on the Configuration Engine.
The Event Service is a highly capable publish-and-subscribe communication method. The Event Service
uses subject-based addressing to send messages to their destinations. Subject-based addressing
conventions define a simple, uniform namespace for messages and their destinations.
NameSpace Mapper
The Configuration Engine includes the NameSpace Mapper (NSM) that provides a lookup service for
managing logical groups of devices based on application, device or group ID, and event.
Cisco IOS devices recognize only event subject-names that match those configured in Cisco IOS
software; for example, cisco.cns.config.load. You can use the namespace mapping service to designate
events by using any desired naming convention. When you have populated your data store with your
subject names, NSM changes your event subject-name strings to those known by Cisco IOS.
For a subscriber, when given a unique device ID and event, the namespace mapping service returns a set
of events to which to subscribe. Similarly, for a publisher, when given a unique group ID, device ID, and
event, the mapping service returns a set of events on which to publish.
What You Should Know About the CNS IDs and Device Hostnames
The Configuration Engine assumes that a unique identifier is associated with each configured switch.
This unique identifier can take on multiple synonyms, where each synonym is unique within a particular
namespace. The event service uses namespace content for subject-based addressing of messages.
The Configuration Engine intersects two namespaces, one for the event bus and the other for the
configuration server. Within the scope of the configuration server namespace, the term ConfigID is the
unique identifier for a device. Within the scope of the event bus namespace, the term DeviceID is the
CNS unique identifier for a device.
Because the Configuration Engine uses both the event bus and the configuration server to provide
configurations to devices, you must define both ConfigID and Device ID for each configured switch.
Within the scope of a single instance of the configuration server, no two configured switches can share
the same value for ConfigID. Within the scope of a single instance of the event bus, no two configured
switches can share the same value for DeviceID.
ConfigID
Each configured switch has a unique ConfigID, which serves as the key into the Configuration Engine
directory for the corresponding set of switch CLI attributes. The ConfigID defined on the switch must
match the ConfigID for the corresponding switch definition on the Configuration Engine.
The ConfigID is fixed at startup time and cannot be changed until the device restarts, even if the switch
hostname is reconfigured.
DeviceID
Each configured switch participating on the event bus has a unique DeviceID, which is analogous to the
switch source address so that the switch can be targeted as a specific destination on the bus. All switches
configured with the cns config partial global configuration command must access the event bus.
Therefore, the DeviceID, as originated on the switch, must match the DeviceID of the corresponding
switch definition in the Configuration Engine.
The origin of the DeviceID is defined by the Cisco IOS hostname of the switch. However, the DeviceID
variable and its usage reside within the event gateway adjacent to the switch.
The logical Cisco IOS termination point on the event bus is embedded in the event gateway, which in
turn functions as a proxy on behalf of the switch. The event gateway represents the switch and its
corresponding DeviceID to the event bus.
The switch declares its hostname to the event gateway immediately after the successful connection to
the event gateway. The event gateway couples the DeviceID value to the Cisco IOS hostname each time
this connection is established. The event gateway caches this DeviceID value for the duration of its
connection to the switch.
Caution When using the Configuration Engine user interface, you must first set the DeviceID field to the
hostname value that the switch acquires after–not before–you use the cns config initial global
configuration command at the switch. Otherwise, subsequent cns config partial global configuration
command operations malfunction.
Note For more information about running the setup program on the Configuration Engine, see the
Configuration Engine setup and configuration guide at
http://www.cisco.com/en/US/products/sw/netmgtsw/ps4617/prod_installation_guides_list.html
Initial Configuration
When the switch first comes up, it attempts to get an IP address by broadcasting a DHCP request on the
network. Assuming there is no DHCP server on the subnet, the distribution switch acts as a DHCP relay
agent and forwards the request to the DHCP server. Upon receiving the request, the DHCP server assigns
an IP address to the new switch and includes the TFTP server IP address, the path to the bootstrap
configuration file, and the default gateway IP address in a unicast reply to the DHCP relay agent. The
DHCP relay agent forwards the reply to the switch.
The switch automatically configures the assigned IP address on interface VLAN 1 (the default) and
downloads the bootstrap configuration file from the TFTP server. Upon successful download of the
bootstrap configuration file, the switch loads the file in its running configuration.
The Cisco IOS agents initiate communication with the Configuration Engine by using the appropriate
ConfigID and EventID. The Configuration Engine maps the Config ID to a template and downloads the
full configuration file to the switch.
Figure 4-2 shows a sample network configuration for retrieving the initial bootstrap configuration file
by using DHCP-based autoconfiguration.
TFTP
server
Configuration WAN
Engine V
DHCP
server
Access layer
141328
switches
Synchronized Configuration
When the switch receives a configuration, it can defer application of the configuration upon receipt of a
write-signal event. The write-signal event tells the switch not to save the updated configuration into its
NVRAM. The switch uses the updated configuration as its running configuration. This ensures that the
switch configuration is synchronized with other network activities before saving the configuration in
NVRAM for use at the next reboot.
Note For more information about running the setup program and creating templates on the Configuration
Engine, see the Cisco Configuration Engine Installation and Setup Guide, 1.5 for Linux at
http://www.cisco.com/en/US/docs/net_mgmt/configuration_engine/1.5/installation_linux/guide/setup_
1.html
Note You must enable the CNS event agent on the switch before you enable the CNS configuration agent.
Beginning in privileged EXEC mode, follow these steps to enable the CNS event agent on the switch:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 cns event {hostname | ip-address} [port-number] Enable the event agent, and enter the gateway parameters.
[backup] [failover-time seconds] [keepalive seconds
• For {hostname | ip-address}, enter either the
retry-count] [reconnect time] [source ip-address]
hostname or the IP address of the event gateway.
• (Optional) For port number, enter the port number for
the event gateway. The default port number is 11011.
• (Optional) Enter backup to show that this is the
backup gateway. (If omitted, this is the primary
gateway.)
• (Optional) For failover-time seconds, enter how long
the switch waits for the primary gateway route after
the route to the backup gateway is established.
• (Optional) For keepalive seconds, enter how often the
switch sends keepalive messages. For retry-count,
enter the number of unanswered keepalive messages
that the switch sends before the connection is
terminated. The default for each is 0.
• (Optional) For reconnect time, enter the maximum
time interval that the switch waits before trying to
reconnect to the event gateway.
• (Optional) For source ip-address, enter the source IP
address of this device.
Note Though visible in the command-line help string,
the encrypt and the clock-timeout time keywords
are not supported.
Step 3 end Return to privileged EXEC mode.
Step 4 show cns event connections Verify information about the event agent.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable the CNS event agent, use the no cns event {ip-address | hostname} global configuration
command.
This example shows how to enable the CNS event agent, set the IP address gateway to 10.180.1.27, set
120 seconds as the keepalive interval, and set 10 as the retry count.
Switch(config)# cns event 10.180.1.27 keepalive 120 10
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 cns template connect name Enter CNS template connect configuration mode, and
specify the name of the CNS connect template.
Step 3 cli config-text Enter a command line for the CNS connect template.
Repeat this step for each command line in the template.
Step 4 Repeat Steps 2 to 3 to configure another CNS connect
template.
Step 5 exit Return to global configuration mode.
Step 6 cns connect name [retries number] [retry-interval Enter CNS connect configuration mode, specify the name
seconds] [sleep seconds] [timeout seconds] of the CNS connect profile, and define the profile
parameters. The switch uses the CNS connect profile to
connect to the Configuration Engine.
• Enter the name of the CNS connect profile.
• (Optional) For retries number, enter the number of
connection retries. The range is 1 to 30. The default
is 3.
• (Optional) For retry-interval seconds, enter the
interval between successive connection attempts to the
Configuration Engine. The range is 1 to 40 seconds.
The default is 10 seconds.
• (Optional) For sleep seconds, enter the amount of time
before which the first connection attempt occurs. The
range is 0 to 250 seconds. The default is 0.
• (Optional) For timeout seconds, enter the amount of
time after which the connection attempts end. The
range is 10 to 2000 seconds. The default is 120.
Command Purpose
Step 7 discover {controller controller-type | dlci Specify the interface parameters in the CNS connect
[subinterface subinterface-number] | interface profile.
[interface-type] | line line-type}
• For controller controller-type, enter the controller
type.
• For dlci, enter the active data-link connection
identifiers (DLCIs).
(Optional) For subinterface subinterface-number,
specify the point-to-point subinterface number that is
used to search for active DLCIs.
• For interface [interface-type], enter the type of
interface.
• For line line-type, enter the line type.
Step 8 template name [ ... name] Specify the list of CNS connect templates in the CNS
connect profile to be applied to the switch configuration.
You can specify more than one template.
Step 9 Repeat Steps 7 to 8 to specify more interface parameters
and CNS connect templates in the CNS connect profile.
Step 10 exit Return to global configuration mode.
Step 11 hostname name Enter the hostname for the switch.
Step 12 ip route network-number (Optional) Establish a static route to the Configuration
Engine whose IP address is network-number.
Command Purpose
Step 13 cns id interface num {dns-reverse | ipaddress | (Optional) Set the unique EventID or ConfigID used by the
mac-address} [event] [image] Configuration Engine.
or • For interface num, enter the type of interface–for
cns id {hardware-serial | hostname | string string | example, ethernet, group-async, loopback, or
udi} [event] [image] virtual-template. This setting specifies from which
interface the IP or MAC address should be retrieved to
define the unique ID.
• For {dns-reverse | ipaddress | mac-address}, enter
dns-reverse to retrieve the hostname and assign it as
the unique ID, enter ipaddress to use the IP address, or
enter mac-address to use the MAC address as the
unique ID.
• (Optional) Enter event to set the ID to be the event-id
value used to identify the switch.
• (Optional) Enter image to set the ID to be the image-id
value used to identify the switch.
Note If both the event and image keywords are omitted,
the image-id value is used to identify the switch.
Command Purpose
Step 14 cns config initial {hostname | ip-address} Enable the Cisco IOS agent, and initiate an initial
[port-number] [event] [no-persist] [page page] configuration.
[source ip-address] [syntax-check]
• For {hostname | ip-address}, enter the hostname or the
IP address of the configuration server.
• (Optional) For port-number, enter the port number of
the configuration server. The default port number is 80.
• (Optional) Enable event for configuration success,
failure, or warning messages when the configuration is
finished.
• (Optional) Enable no-persist to suppress the
automatic writing to NVRAM of the configuration
pulled as a result of entering the cns config initial
global configuration command. If the no-persist
keyword is not entered, using the cns config initial
command causes the resultant configuration to be
automatically written to NVRAM.
• (Optional) For page page, enter the web page of the
initial configuration. The default is /Config/config/asp.
• (Optional) Enter source ip-address to use for source IP
address.
• (Optional) Enable syntax-check to check the syntax
when this parameter is entered.
Note Though visible in the command-line help string,
the encrypt, status url, and inventory keywords
are not supported.
Step 15 end Return to privileged EXEC mode.
Step 16 show cns config connections Verify information about the configuration agent.
Step 17 show running-config Verify your entries.
To disable the CNS Cisco IOS agent, use the no cns config initial {ip-address | hostname} global
configuration command.
This example shows how to configure an initial configuration on a remote switch when the switch
configuration is unknown (the CNS Zero Touch feature).
Switch(config)# cns template connect template-dhcp
Switch(config-tmpl-conn)# cli ip address dhcp
Switch(config-tmpl-conn)# exit
Switch(config)# cns template connect ip-route
Switch(config-tmpl-conn)# cli ip route 0.0.0.0 0.0.0.0 ${next-hop}
Switch(config-tmpl-conn)# exit
Switch(config)# cns connect dhcp
Switch(config-cns-conn)# discover interface gigabitethernet
Switch(config-cns-conn)# template template-dhcp
Switch(config-cns-conn)# template ip-route
Switch(config-cns-conn)# exit
Switch(config)# hostname RemoteSwitch
RemoteSwitch(config)# cns config initial 10.1.1.1 no-persist
This example shows how to configure an initial configuration on a remote switch when the switch IP
address is known. The Configuration Engine IP address is 172.28.129.22.
Switch(config)# cns template connect template-dhcp
Switch(config-tmpl-conn)# cli ip address dhcp
Switch(config-tmpl-conn)# exit
Switch(config)# cns template connect ip-route
Switch(config-tmpl-conn)# cli ip route 0.0.0.0 0.0.0.0 ${next-hop}
Switch(config-tmpl-conn)# exit
Switch(config)# cns connect dhcp
Switch(config-cns-conn)# discover interface gigabitethernet
Switch(config-cns-conn)# template template-dhcp
Switch(config-cns-conn)# template ip-route
Switch(config-cns-conn)# exit
Switch(config)# hostname RemoteSwitch
RemoteSwitch(config)# ip route 172.28.129.22 255.255.255.255 11.11.11.1
RemoteSwitch(config)# cns id ethernet 0 ipaddress
RemoteSwitch(config)# cns config initial 172.28.129.22 no-persist
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 cns config partial {ip-address | hostname} Enable the configuration agent, and initiate a partial
[port-number] [source ip-address] configuration.
• For {ip-address | hostname}, enter the IP address or
the hostname of the configuration server.
• (Optional) For port-number, enter the port number of
the configuration server. The default port number is 80.
• (Optional) Enter source ip-address to use for the
source IP address.
Note Though visible in the command-line help string,
the encrypt keyword is not supported.
Step 3 end Return to privileged EXEC mode.
Step 4 show cns config stats Verify information about the configuration agent.
or
show cns config outstanding
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable the Cisco IOS agent, use the no cns config partial {ip-address | hostname} global
configuration command. To cancel a partial configuration, use the cns config cancel privileged EXEC
command.
Command Purpose
Step 1 configure terminal Enter global configuration mode
Step 2 ip host {ip-address} {hostname} Enter the IP address and the hostname of the event
gateway.
Step 3 cns trusted-server all-agents {hostname} Specify a trusted server for CNS agent.
Step 4 no cns aaa enable cns event {ip-address} {port number} Disable AAA authentication on the event gateway.
Command Purpose
Step 5 cns image retry {number} Specify the number of times to retry and download the
image.
Step 6 cns image server {ip-address} status {ip-address} Download the image from the server to the switch.
Step 7 end Return to privileged EXEC mode.
This example shows how to upgrade a switch from a server with the address of 172.20.249.20:
Switch(config)> configure terminal
Switch(config)# ip host cns-dsbu.cisco.com 172.20.249.20
Switch(config)# cns trusted-server all-agents cns-dsbu.cisco.com
Switch(config)# no cns aaa enable cns event 172.20.249.20 22022
Switch(config)# cns image retry 1
Switch(config)# cns image server http://172.20.249.20:80/cns/HttpMsgDispatcher status
http://172.20.249.20:80/cns/HttpMsgDispatcher
Switch(config)#end
You can check the status of the image download by using the show cns image status user EXEC
command.
Command Purpose
show cns config connections Displays the status of the CNS Cisco IOS agent connections.
show cns config outstanding Displays information about incremental (partial) CNS
configurations that have started but are not yet completed.
show cns config stats Displays statistics about the Cisco IOS agent.
show cns event connections Displays the status of the CNS event agent connections.
show cns event stats Displays statistics about the CNS event agent.
show cns event subject Displays a list of event agent subjects that are subscribed to by
applications.
This chapter describes how to perform one-time operations to administer the Catalyst 3750 Metro
switch.
This chapter consists of these sections:
• Managing the System Time and Date, page 5-1
• Configuring a System Name and Prompt, page 5-7
• Creating a Banner, page 5-10
• Managing the MAC Address Table, page 5-12
• Managing the ARP Table, page 5-24
Note For complete syntax and usage information for the commands used in this section, see the Cisco IOS
Configuration Fundamentals Command Reference, Release 12.2.
Switch A
Local
workgroup
servers
Switch E
Workstations
Switch F
101349
Workstations
If the network is isolated from the Internet, Cisco’s implementation of NTP allows a device to act as
though it is synchronized through NTP, when in fact it has determined the time by using other means.
Other devices then synchronize to that device through NTP.
When multiple sources of time are available, NTP is always considered to be more authoritative. NTP
time overrides the time set by any other method.
Several manufacturers include NTP software for their host systems, and a publicly available version for
systems running UNIX and its various derivatives is also available. This software allows host systems to
be time-synchronized as well.
NTP Version 4
NTP version 4 is implemented on the switch. NTPv4 is an extension of NTP version 3. NTPv4 supports
both IPv4 and IPv6 and is backward-compatible with NTPv3.
NTPv4 provides these capabilities:
• Support for IPv6.
• Improved security compared to NTPv3. The NTPv4 protocol provides a security framework based
on public key cryptography and standard X509 certificates.
• Automatic calculation of the time-distribution hierarchy for a network. Using specific multicast
groups, NTPv4 automatically configures the hierarchy of the servers to achieve the best time
accuracy for the lowest bandwidth cost. This feature leverages site-local IPv6 multicast addresses.
For details about configuring NTPv4, see the “Implementing NTPv4 in IPv6” chapter of the Cisco IOS
IPv6 Configuration Guide, Release 12.4T.
Command Purpose
Step 1 clock set hh:mm:ss day month year Manually set the system clock using one of these formats.
or • For hh:mm:ss, specify the time in hours (24-hour format), minutes,
clock set hh:mm:ss month day year and seconds. The time specified is relative to the configured time
zone.
• For day, specify the day by date in the month.
• For month, specify the month by name.
• For year, specify the year (no abbreviation).
Step 2 show running-config Verify your entries.
Step 3 copy running-config startup-config (Optional) Save your entries in the configuration file.
This example shows how to manually set the system clock to 1:32 p.m. on July 23, 2001:
Switch# clock set 13:32:00 23 July 2001
The symbol that precedes the show clock display has this meaning:
• *—Time is not authoritative.
• (blank)—Time is authoritative.
• .—Time is authoritative, but NTP is not synchronized.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 clock timezone zone hours-offset Set the time zone.
[minutes-offset]
The switch keeps internal time in universal time coordinated (UTC), so
this command is used only for display purposes and when the time is
manually set.
• For zone, enter the name of the time zone to be displayed when
standard time is in effect. The default is UTC.
• For hours-offset, enter the hours offset from UTC.
• (Optional) For minutes-offset, enter the minutes offset from UTC.
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
The minutes-offset variable in the clock timezone global configuration command is available for those
cases where a local time zone is a percentage of an hour different from UTC. For example, the time zone
for some sections of Atlantic Canada (AST) is UTC-3.5, where the 3 means 3 hours and .5 means 50
percent. In this case, the necessary command is clock timezone AST -3 30.
To set the time to UTC, use the no clock timezone global configuration command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 clock summer-time zone recurring Configure summer time to start and end on the specified days every year.
[week day month hh:mm week day month
Summer time is disabled by default. If you specify clock summer-time
hh:mm [offset]]
zone recurring without parameters, the summer time rules default to the
United States rules.
• For zone, specify the name of the time zone (for example, PDT) to be
displayed when summer time is in effect.
• (Optional) For week, specify the week of the month (1 to 5 or last).
• (Optional) For day, specify the day of the week (Sunday, Monday...).
• (Optional) For month, specify the month (January, February...).
• (Optional) For hh:mm, specify the time (24-hour format) in hours and
minutes.
• (Optional) For offset, specify the number of minutes to add during
summer time. The default is 60.
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
The first part of the clock summer-time global configuration command specifies when summer time
begins, and the second part specifies when it ends. All times are relative to the local time zone. The start
time is relative to standard time. The end time is relative to summer time. If the starting month is after
the ending month, the system assumes that you are in the southern hemisphere.
This example shows how to specify that summer time starts on the first Sunday in April at 02:00 and
ends on the last Sunday in October at 02:00:
Switch(config)# clock summer-time PDT recurring 1 Sunday April 2:00 last Sunday October
2:00
Beginning in privileged EXEC mode, follow these steps if summer time in your area does not follow a
recurring pattern (configure the exact date and time of the next summer time events):
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 clock summer-time zone date [month Configure summer time to start on the first date and end on the second
date year hh:mm month date year hh:mm date.
[offset]] Summer time is disabled by default.
or
• For zone, specify the name of the time zone (for example, PDT) to be
clock summer-time zone date [date displayed when summer time is in effect.
month year hh:mm date month year
• (Optional) For week, specify the week of the month (1 to 5 or last).
hh:mm [offset]]
• (Optional) For day, specify the day of the week (Sunday, Monday...).
• (Optional) For month, specify the month (January, February...).
• (Optional) For hh:mm, specify the time (24-hour format) in hours and
minutes.
• (Optional) For offset, specify the number of minutes to add during
summer time. The default is 60.
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
The first part of the clock summer-time global configuration command specifies when summer time
begins, and the second part specifies when it ends. All times are relative to the local time zone. The start
time is relative to standard time. The end time is relative to summer time. If the starting month is after
the ending month, the system assumes that you are in the southern hemisphere.
To disable summer time, use the no clock summer-time global configuration command.
This example shows how to set summer time to start on October 12, 2003, at 02:00, and end on April 26,
2004, at 02:00:
Switch(config)# clock summer-time pdt date 12 October 2003 2:00 26 April 2004 2:00
Note For complete syntax and usage information for the commands used in this section, see the Cisco IOS
Configuration Fundamentals Command Reference, Release 12.2 and the Cisco IOS IP Command
Reference, Volume 2 of 3: Routing Protocols, Release 12.2.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 hostname name Manually configure a system name.
The default setting is switch.
The name must follow the rules for ARPANET hostnames. They must start
with a letter, end with a letter or digit, and have as interior characters only
letters, digits, and hyphens. Names can be up to 63 characters.
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
When you set the system name, it is also used as the system prompt.
To return to the default hostname, use the no hostname global configuration command.
Understanding DNS
The DNS protocol controls the Domain Name System (DNS), a distributed database with which you can
map hostnames to IP addresses. When you configure DNS on your switch, you can substitute the
hostname for the IP address with all IP commands, such as ping, telnet, connect, and related Telnet
support operations.
IP defines a hierarchical naming scheme that allows a device to be identified by its location or domain.
Domain names are pieced together with periods (.) as the delimiting characters. For example, Cisco
Systems is a commercial organization that IP identifies by a com domain name, so its domain name is
cisco.com. A specific device in this domain, for example, the FTP system is identified as ftp.cisco.com.
To keep track of domain names, IP has defined the concept of a domain name server, which holds a cache
(or database) of names mapped to IP addresses. To map domain names to IP addresses, you must first
identify the hostnames, specify the name server that is present on your network, and enable the DNS.
Setting Up DNS
Beginning in privileged EXEC mode, follow these steps to set up your switch to use the DNS:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip domain-name name Define a default domain name that the software uses to complete unqualified
hostnames (names without a dotted-decimal domain name).
Do not include the initial period that separates an unqualified name from the
domain name.
At boot time, no domain name is configured; however, if the switch
configuration comes from a BOOTP or DHCP server, then the default domain
name might be set by the BOOTP or DHCP server (if the servers were
configured with this information).
Step 3 ip name-server server-address1 Specify the address of one or more name servers to use for name and address
[server-address2 ... resolution.
server-address6]
You can specify up to six name servers. Separate each server address with a
space. The first server specified is the primary server. The switch sends DNS
queries to the primary server first. If that query fails, the backup servers are
queried.
Step 4 ip domain-lookup (Optional) Enable DNS-based hostname-to-address translation on your switch.
This feature is enabled by default.
If your network devices require connectivity with devices in networks for which
you do not control name assignment, you can dynamically assign device names
that uniquely identify your devices by using the global Internet naming scheme
(DNS).
Step 5 end Return to privileged EXEC mode.
Command Purpose
Step 6 show running-config Verify your entries.
Step 7 copy running-config (Optional) Save your entries in the configuration file.
startup-config
If you use the switch IP address as its hostname, the IP address is used and no DNS query occurs. If you
configure a hostname that contains no periods (.), a period followed by the default domain name is
appended to the hostname before the DNS query is made to map the name to an IP address. The default
domain name is the value set by the ip domain-name global configuration command. If there is a
period (.) in the hostname, the Cisco IOS software looks up the IP address without appending any default
domain name to the hostname.
To remove a domain name, use the no ip domain-name name global configuration command. To remove
a name server address, use the no ip name-server server-address global configuration command. To
disable DNS on the switch, use the no ip domain-lookup global configuration command.
Creating a Banner
You can configure a message-of-the-day (MOTD) and a login banner. The MOTD banner displays on all
connected terminals at login and is useful for sending messages that affect all network users (such as
impending system shutdowns).
The login banner also displays on all connected terminals. It is displayed after the MOTD banner and
before the login prompts.
Note For complete syntax and usage information for the commands used in this section, see the Cisco IOS
Configuration Fundamentals Command Reference, Release 12.2.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 banner motd c message c Specify the message of the day.
For c, enter the delimiting character of your choice, for example, a
pound sign (#), and press the Return key. The delimiting character
signifies the beginning and end of the banner text. Characters after the
ending delimiter are discarded.
For message, enter a banner message up to 255 characters. You cannot
use the delimiting character in the message.
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To delete the MOTD banner, use the no banner motd global configuration command.
This example shows how to configure a MOTD banner for the switch by using the pound sign (#) symbol
as the beginning and ending delimiter:
Switch(config)# banner motd #
This is a secure site. Only authorized users are allowed.
For access, contact technical support.
#
Switch(config)#
This example shows the banner displayed from the previous configuration:
Unix> telnet 172.2.5.4
Trying 172.2.5.4...
Connected to 172.2.5.4.
Escape character is '^]'.
Password:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 banner login c message c Specify the login message.
For c, enter the delimiting character of your choice, for example, a pound
sign (#), and press the Return key. The delimiting character signifies the
beginning and end of the banner text. Characters after the ending delimiter
are discarded.
For message, enter a login message up to 255 characters. You cannot use the
delimiting character in the message.
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To delete the login banner, use the no banner login global configuration command.
This example shows how to configure a login banner for the switch by using the dollar sign ($) symbol
as the beginning and ending delimiter:
Switch(config)# banner login $
Access for authorized users only. Please enter your username and password.
$
Switch(config)#
Note For complete syntax and usage information for the commands used in this section, see the command
reference for this release.
Each VLAN maintains its own logical address table. A known address in one VLAN is unknown in
another until it is learned or statically associated with a port in the other VLAN.
When private VLANs are configured, address learning depends on the type of MAC address:
• 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 private-VLAN secondary VLAN is replicated in
the primary VLAN.
• Static MAC addresses configured in a primary or secondary VLAN are not replicated in the
associated VLANs. When you configure a static MAC address in a private VLAN primary or
secondary VLAN, you should also configure the same static MAC address in all associated VLANs.
For more information about private VLANs, see Chapter 13, “Configuring Private VLANs.”
You can disable MAC address learning on a per-VLAN basis. Customers in a service provider network
can tunnel a large number of MAC addresses through the network and fill up the available MAC address
table space. You can control MAC address learning on a VLAN and manage the MAC address table space
that is available on the switch by controlling which VLANs, and therefore which ports, can learn MAC
addresses.
Before you disable MAC address learning, be sure that you are familiar with the network topology and
the switch system configuration. Disabling MAC address learning on a VLAN could cause flooding in
the network. See the “Disabling MAC Address Learning on a VLAN” section on page 5-22 for more
information.
Beginning in privileged EXEC mode, follow these steps to configure the dynamic address table aging
time:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 mac address-table aging-time [0 | Set the length of time that a dynamic entry remains in the MAC
10-1000000] [vlan vlan-id] address table after the entry is used or updated.
The range is 10 to 1000000 seconds. The default is 300. You can also
enter 0, which disables aging. Static address entries are never aged
or removed from the table.
For vlan-id, the range is 1 to 4094.
Step 3 end Return to privileged EXEC mode.
Step 4 show mac address-table aging-time Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default value, use the no mac address-table aging-time global configuration command.
Beginning in privileged EXEC mode, follow these steps to configure the switch to send MAC address
change notification traps to an NMS host:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 snmp-server host host-addr {traps | informs} {version {1 Specify the recipient of the trap message.
| 2c | 3}} community-string notification-type
• For host-addr, specify the name or address of the
NMS.
• Specify traps (the default) to send SNMP traps
to the host. Specify informs to send SNMP
informs to the host.
• Specify the SNMP version to support. Version 1,
the default, is not available with informs.
• For community-string, specify the string to send
with the notification operation. Though you can
set this string by using the snmp-server host
command, we recommend that you define this
string by using the snmp-server community
command before using the snmp-server host
command.
• For notification-type, use the mac-notification
keyword.
Step 3 snmp-server enable traps mac-notification change Enable the switch to send MAC address change
notification traps to the NMS.
Step 4 mac address-table notification change Enable the MAC address change notification feature.
Step 5 mac address-table notification change [interval value] Enter the trap interval time and the history table size.
[history-size value]
• (Optional) For interval value, specify the
notification trap interval in seconds between
each set of traps that are generated to the NMS.
The range is 0 to 2147483647 seconds; the
default is 1 second.
• (Optional) For history-size value, specify the
maximum number of entries in the MAC
notification history table. The range is 0 to 500;
the default is 1.
Step 6 interface interface-id Enter interface configuration mode, and specify the
Layer 2 interface on which to enable the SNMP
MAC address notification trap.
Step 7 snmp trap mac-notification change {added | removed} Enable the MAC address change notification trap on
the interface.
• Enable the trap when a MAC address is added
on this interface.
• Enable the trap when a MAC address is removed
from this interface.
Step 8 end Return to privileged EXEC mode.
Command Purpose
Step 9 show mac address-table notification change interface Verify your entries.
show running-config
Step 10 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable MAC address-change notification traps, use the no snmp-server enable traps
mac-notification change global configuration command. To disable the MAC address-change
notification traps on a specific interface, use the no snmp trap mac-notification change {added |
removed} interface configuration command. To disable the MAC address-change notification feature,
use the no mac address-table notification change global configuration command.
This example shows how to specify 172.20.10.10 as the NMS, enable the switch to send MAC address
notification traps to the NMS, enable the MAC address-change notification feature, set the interval time
to 123 seconds, set the history-size to 100 entries, and enable traps whenever a MAC address is added
on the specified port.
Switch(config)# snmp-server host 172.20.10.10 traps private mac-notification
Switch(config)# snmp-server enable traps mac-notification change
Switch(config)# mac address-table notification change
Switch(config)# mac address-table notification change interval 123
Switch(config)# mac address-table notification change history-size 100
Switch(config)# interface gigabitethernet1/1/2
Switch(config-if)# snmp trap mac-notification change added
You can verify your settings by entering the show mac address-table notification change interface and
the show mac address-table notification change privileged EXEC commands.
Beginning in privileged EXEC mode, follow these steps to configure the switch to send MAC
address-move notification traps to an NMS host:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 snmp-server host host-addr {traps | informs} {version {1 Specify the recipient of the trap message.
| 2c | 3}} community-string notification-type
• For host-addr, specify the name or address of the
NMS.
• Specify traps (the default) to send SNMP traps
to the host. Specify informs to send SNMP
informs to the host.
• Specify the SNMP version to support. Version 1,
the default, is not available with informs.
• For community-string, specify the string to send
with the notification operation. Though you can
set this string by using the snmp-server host
command, we recommend that you define this
string by using the snmp-server community
command before using the snmp-server host
command.
• For notification-type, use the mac-notification
keyword.
Step 3 snmp-server enable traps mac-notification move Enable the switch to send MAC address move
notification traps to the NMS.
Step 4 mac address-table notification mac-move Enable the MAC address move notification feature.
Step 5 end Return to privileged EXEC mode.
Step 6 show mac address-table notification mac-move Verify your entries.
show running-config
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable MAC address-move notification traps, use the no snmp-server enable traps
mac-notification move global configuration command. To disable the MAC address-move notification
feature, use the no mac address-table notification mac-move global configuration command.
This example shows how to specify 172.20.10.10 as the NMS, enable the switch to send MAC address
move notification traps to the NMS, enable the MAC address move notification feature, and enable traps
when a MAC address moves from one port to another.
Switch(config)# snmp-server host 172.20.10.10 traps private mac-notification
Switch(config)# snmp-server enable traps mac-notification move
Switch(config)# mac address-table notification mac-move
You can verify your settings by entering the show mac address-table notification mac-move privileged
EXEC commands.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 snmp-server host host-addr {traps | informs} {version {1 Specify the recipient of the trap message.
| 2c | 3}} community-string notification-type
• For host-addr, specify the name or address of the
NMS.
• Specify traps (the default) to send SNMP traps
to the host. Specify informs to send SNMP
informs to the host.
• Specify the SNMP version to support. Version 1,
the default, is not available with informs.
• For community-string, specify the string to send
with the notification operation. Though you can
set this string by using the snmp-server host
command, we recommend that you define this
string by using the snmp-server community
command before using the snmp-server host
command.
• For notification-type, use the mac-notification
keyword.
Step 3 snmp-server enable traps mac-notification threshold Enable the switch to send MAC threshold
notification traps to the NMS.
Step 4 mac address-table notification threshold Enable the MAC address threshold notification
feature.
Step 5 mac address-table notification threshold [limit Enter the threshold value for the MAC address
percentage] | [interval time] threshold usage monitoring.
• (Optional) For limit percentage, specify the
percentage of the MAC address table use; valid
values are from 1 to 100 percent. The default is
50 percent.
• (Optional) For interval time, specify the time
between notifications; valid values are greater
than or equal to 120 seconds. The default is 120
seconds.
Step 6 end Return to privileged EXEC mode.
Step 7 show mac address-table notification threshold Verify your entries.
show running-config
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable MAC address-threshold notification traps, use the no snmp-server enable traps
mac-notification threshold global configuration command. To disable the MAC address-threshold
notification feature, use the no mac address-table notification threshold global configuration
command.
This example shows how to specify 172.20.10.10 as the NMS, enable the MAC address threshold
notification feature, set the interval time to 123 seconds, and set the limit to 78 per cent.
Switch(config)# snmp-server host 172.20.10.10 traps private mac-notification
Switch(config)# snmp-server enable traps mac-notification threshold
Switch(config)# mac address-table notification threshold
Switch(config)# mac address-table notification threshold interval 123
Switch(config)# mac address-table notification threshold limit 78
You can verify your settings by entering the show mac address-table notification threshold privileged
EXEC commands.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 mac address-table static mac-addr Add a static address to the MAC address table.
vlan vlan-id interface interface-id
• For mac-addr, specify the destination MAC unicast address to add to
the address table. Packets with this destination address received in the
specified VLAN are forwarded to the specified interface.
• For vlan-id, specify the VLAN for which the packet with the
specified MAC address is received. The range is 1 to 4094.
• For interface-id, specify the interface to which the received packet is
forwarded. Valid interfaces include physical ports.
Command Purpose
Step 3 end Return to privileged EXEC mode.
Step 4 show mac address-table static Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove static entries from the address table, use the no mac address-table static mac-addr vlan
vlan-id interface interface-id global configuration command.
This example shows how to add the static address c2f3.220a.12f4 to the MAC address table. When a
packet is received in VLAN 4 with this MAC address as its destination address, the packet is forwarded
to the specified interface:
Switch(config)# mac address-table static c2f3.220a.12f4 vlan 4 interface
gigabitethernet1/0/1
• Packets that are forwarded to the CPU are also not supported.
• If you add a unicast MAC address as a static address and configure unicast MAC address filtering,
the switch either adds the MAC address as a static address or drops packets with that MAC address,
depending on which command was entered last. The second command that you entered overrides the
first command.
For example, if you enter the mac address-table static mac-addr vlan vlan-id interface
interface-id global configuration command followed by the mac address-table static mac-addr
vlan vlan-id drop command, the switch drops packets with the specified MAC address as a source
or destination.
If you enter the mac address-table static mac-addr vlan vlan-id drop global configuration
command followed by the mac address-table static mac-addr vlan vlan-id interface interface-id
command, the switch adds the MAC address as a static address.
You enable unicast MAC address filtering and configure the switch to drop packets with a specific
address by specifying the source or destination unicast MAC address and the VLAN from which it is
received.
Beginning in privileged EXEC mode, follow these steps to configure the switch to drop a source or
destination unicast static address:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 mac address-table static mac-addr Enable unicast MAC address filtering and configure the switch to drop a
vlan vlan-id drop packet with the specified source or destination unicast static address.
• For mac-addr, specify a source or destination unicast MAC address.
Packets with this MAC address are dropped.
• For vlan-id, specify the VLAN for which the packet with the
specified MAC address is received. Valid VLAN IDs are 1 to 4094.
Step 3 end Return to privileged EXEC mode.
Step 4 show mac address-table static Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable unicast MAC address filtering, use the no mac address-table static mac-addr vlan vlan-id
global configuration command.
This example shows how to enable unicast MAC address filtering and to configure the switch to drop
packets that have a source or destination address of c2f3.220a.12f4. When a packet is received in
VLAN 4 with this MAC address as its source or destination, the packet is dropped:
Switch(config)# mac a ddress-table static c2f3.220a.12f4 vlan 4 drop
• If you disable MAC address learning on a VLAN configured as a private-VLAN primary VLAN,
MAC addresses are still learned on the secondary VLAN that belongs to the private VLAN and are
then replicated on the primary VLAN. If you disable MAC address learning on the secondary
VLAN, but not the primary VLAN of a private VLAN, MAC address learning occurs on the primary
VLAN and is replicated on the secondary VLAN.
• You cannot disable MAC address learning on an RSPAN VLAN. The configuration is not allowed.
• If you disable MAC address learning on a VLAN that includes a secure port, MAC address learning
is not disabled on that port. If you disable port security, the configured MAC address learning state
is enabled.
Beginning in privileged EXEC mode, follow these steps to disable MAC address learning on a VLAN:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 no mac address-table learning vlan • Disable MAC address learning on the specified VLAN or VLANs.
vlan-id You can specify a single VLAN or a range of VLANs separated by a
hyphen or comma. Valid VLAN IDs are 1 to 4094. The VLAN cannot
be an internal VLAN.
Step 3 end Return to privileged EXEC mode.
Step 4 show mac address-table learning [vlan Verify the configuration.
vlan-id]
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To re-enable MAC address learning on a VLAN, use the default mac address-table learning vlan
vlan-id global configuration command. You can also reenable MAC address learning on a VLAN by
entering the mac address-table learning vlan vlan-id global configuration command. The first
(default) command returns to a default condition and therefore does not appear in the output from the
show running-config command. The second command causes the configuration to appear in the show
running-config privileged EXEC command display.
This example shows how to disable MAC address learning on VLAN 200:
Switch(config)# no mac a ddress-table learning vlan 200
You can display the MAC address learning status of all VLANs or a specified VLAN by entering the
show mac-address-table learning [vlan vlan-id] privileged EXEC command.
Command Description
show mac address-table address Displays MAC address table information for the specified MAC address.
show mac address-table aging-time Displays the aging time in all VLANs or the specified VLAN.
show mac address-table count Displays the number of addresses present in all VLANs or the specified VLAN.
Table 5-3 Commands for Displaying the MAC Address Table (continued)
Command Description
show mac address-table dynamic Displays only dynamic MAC address table entries.
show mac address-table interface Displays the MAC address table information for the specified interface.
show mac address-table learning Displays MAC address learning status of all VLANs or the specified VLAN.
show mac address-table multicast Displays the Layer 2 multicast entries for all VLANs or the specified VLAN.
show mac address-table notification Displays the MAC notification parameters and history table.
show mac address-table static Displays only static MAC address table entries.
show mac address-table vlan Displays the MAC address table information for the specified VLAN.
This chapter describes how to configure the Switch Database Management (SDM) templates on the
Catalyst 3750 Metro switch.
Note For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
.
Table 6-1 Approximate Number of Feature Resources Allowed by Each Template
Template
Resource Default Routing VLAN
Unicast MAC addresses 6K 3K 12 K
IGMP groups and multicast routes 1K 1K 1K
Unicast routes 8K 11 K 0
• Directly connected hosts 6K 3K 0
• Indirect routes 2K 8K 0
Policy-based routing ACEs 0 512 0
QoS classification ACEs 512 512 512
Security ACEs 1K 1K 1K
Layer 2 VLANs 1K 1K 1K
The first eight rows in the tables (unicast MAC addresses through security ACEs) represent approximate
hardware boundaries set when a template is selected. If a section of a hardware resource is full, all
processing overflow is sent to the CPU, seriously impacting switch performance. The last row is a
guideline used to calculate hardware resource consumption related to the number of Layer 2 VLANs on
the switch.
Note An IPv4 route requires only one TCAM entry. Because of the hardware compression scheme used for
IPv6, an IPv6 route can take more than one TCAM entry, reducing the number of entries forwarded in
hardware.
Table 7-2 defines the approximate feature resources allocated by each dual template. Template
estimations are based on a switch with 8 routed interfaces and approximately 1000 VLANs.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 sdm prefer {default | dual-ipv4-and-ipv6 Specify the SDM template to be used on the switch:
{default | routing | vlan} | routing | vlan}
The keywords have these meanings:
• default—Set the switch to the balance system resources between
Layer 2 and Layer 3 functions.
• dual-ipv4-and-ipv6—Select a template that supports both IPv4
and IPv6 routing.
– default—Balance IPv4 and IPv6 Layer 2 and Layer 3
functionality.
– routing—Provide maximum usage for IPv4 and IPv6
routing, including IPv4 policy-based routing.
– vlan—Provide maximum usage for IPv4 and IPv6 VLANs.
• routing—Maximize routing on the switch.
• vlan—Maximize VLAN configuration on the switch with no
routing supported in hardware.
Step 3 end Return to privileged EXEC mode.
Step 4 reload Reload the operating system.
After the system reboots, you can use the show sdm prefer privileged EXEC command to verify the new
template configuration. If you enter the show sdm prefer command before you enter the reload
privileged EXEC command, the show sdm prefer command shows the template currently in use and the
template that will become active after a reload.
This is an example of an output display when you have changed the template and have not reloaded the
switch:
Switch# show sdm prefer
The current template is "desktop routing" template.
The selected template optimizes the resources in
the switch to support this level of features for
8 routed interfaces and 1024 VLANs.
To return to the default template, use the no sdm prefer global configuration command.
This example shows how to configure a switch with the routing template.
Switch(config)# sdm prefer routing
Switch(config)# end
Switch# reload
Proceed with reload? [confirm]
This is an example of output from the show sdm prefer routing command:
Switch# show sdm prefer routing
"desktop routing" template:
The selected template optimizes the resources in
the switch to support this level of features for
8 routed interfaces and 1024 VLANs.
Note When non-IP host mac-addresses are learned, the "IPv4" directly connected route space is used. (The
IPv4 directly connected route space is always used, even when the learned MAC address is not routed,
or has no associated IP address.)
This chapter describes how to configure switch-based authentication on the Catalyst 3750 Metro switch.
It consists of these sections:
• Preventing Unauthorized Access to Your Switch, page 7-1
• Protecting Access to Privileged EXEC Commands, page 7-2
• Controlling Switch Access with TACACS+, page 7-9
• Controlling Switch Access with RADIUS, page 7-17
• Controlling Switch Access with Kerberos, page 7-32
• Configuring the Switch for Local Authentication and Authorization, page 7-36
• Configuring the Switch for Secure Shell, page 7-37
• Configuring the Switch for Secure Socket Layer HTTP, page 7-41
• Configuring the Switch for Secure Copy Protocol, page 7-48
• If you want to use username and password pairs, but you want to store them centrally on a server
instead of locally, you can store them in a database on a security server. Multiple networking devices
can then use the same database to obtain user authentication (and, if necessary, authorization)
information. For more information, see the “Controlling Switch Access with TACACS+” section on
page 7-9.
Note For complete syntax and usage information for the commands used in this section, see the Cisco IOS
Security Command Reference, Release 12.2.
This section describes how to control access to the configuration file and privileged EXEC commands.
It contains this configuration information:
• Default Password and Privilege Level Configuration, page 7-2
• Setting or Changing a Static Enable Password, page 7-3
• Protecting Enable and Enable Secret Passwords with Encryption, page 7-3
• Disabling Password Recovery, page 7-5
• Setting a Telnet Password for a Terminal Line, page 7-6
• Configuring Username and Password Pairs, page 7-6
• Configuring Multiple Privilege Levels, page 7-7
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 enable password password Define a new password or change an existing password for access to
privileged EXEC mode.
By default, no password is defined.
For password, specify a string from 1 to 25 alphanumeric characters. The
string cannot start with a number, is case sensitive, and allows spaces but
ignores leading spaces. It can contain the question mark (?) character if
you precede the question mark with the key combination Crtl-v when you
create the password; for example, to create the password abc?123, do this:
Enter abc.
Enter Crtl-v.
Enter ?123.
When the system prompts you to enter the enable password, you need not
precede the question mark with the Ctrl-v; you can simply enter abc?123
at the password prompt.
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
The enable password is not encrypted and can be read in the switch
configuration file.
To remove the password, use the no enable password global configuration command.
This example shows how to change the enable password to l1u2c3k4y5. The password is not encrypted
and provides access to level 15 (traditional privileged EXEC mode access):
Switch(config)# enable password l1u2c3k4y5
Beginning in privileged EXEC mode, follow these steps to configure encryption for enable and enable
secret passwords:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 enable password [level level] {password | Define a new password or change an existing password for
encryption-type encrypted-password} access to privileged EXEC mode.
or or
enable secret [level level] {password | Define a secret password, which is saved using a
encryption-type encrypted-password} nonreversible encryption method.
• (Optional) For level, the range is from 0 to 15. Level 1 is
normal user EXEC mode privileges. The default level is
15 (privileged EXEC mode privileges).
• For password, specify a string from 1 to 25
alphanumeric characters. The string cannot start with a
number, is case sensitive, and allows spaces but ignores
leading spaces. By default, no password is defined.
• (Optional) For encryption-type, only type 5, a Cisco
proprietary encryption algorithm, is available. If you
specify an encryption type, you must provide an
encrypted password—an encrypted password that you
copy from another switch configuration.
Note If you specify an encryption type and then enter a
clear text password, you can not re-enter privileged
EXEC mode. You cannot recover a lost encrypted
password by any method.
Step 3 service password-encryption (Optional) Encrypt the password when the password is
defined or when the configuration is written.
Encryption prevents the password from being readable in the
configuration file.
Step 4 end Return to privileged EXEC mode.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
If both the enable and enable secret passwords are defined, users must enter the enable secret password.
Use the level keyword to define a password for a specific privilege level. After you specify the level and
set a password, give the password only to users who need to have access at this level. Use the privilege
level global configuration command to specify commands accessible at various levels. For more
information, see the “Configuring Multiple Privilege Levels” section on page 7-7.
If you enable password encryption, it applies to all passwords including username passwords,
authentication key passwords, the privileged command password, and console and virtual terminal line
passwords.
To remove a password and level, use the no enable password [level level] or no enable secret [level
level] global configuration command. To disable password encryption, use the no service
password-encryption global configuration command.
This example shows how to configure the encrypted password $1$FaD0$Xyti5Rkls3LoyxzS8 for
privilege level 2:
Switch(config)# enable secret level 2 5 $1$FaD0$Xyti5Rkls3LoyxzS8
Note If you disable password recovery, we recommend that you keep a backup copy of the configuration file
on a secure server in case the end user interrupts the boot process and sets the system back to default
values. Do not keep a backup copy of the configuration file on the switch. If the switch is operating in
VTP transparent mode, we recommend that you also keep a backup copy of the VLAN database file on
a secure server. When the switch is returned to the default system configuration, you can download the
saved files to the switch by using the Xmodem protocol. For more information, see the “Recovering from
a Lost or Forgotten Password” section on page 48-3.
Beginning in privileged EXEC mode, follow these steps to disable password recovery:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 no service password-recovery Disable password recovery.
This setting is saved in an area of the flash memory that is accessible by
the boot loader and the Cisco IOS image, but it is not part of the file
system and is not accessible by any user.
Step 3 end Return to privileged EXEC mode.
Step 4 show version Verify the configuration by checking the last few lines of the display.
To re-enable password recovery, use the service password-recovery global configuration command.
Note Disabling password recovery does not work if you have set the switch to boot manually by using the boot
manual global configuration command. This command produces the boot loader prompt (switch:) after
the switch is power cycled.
Command Purpose
Step 1 Attach a PC or workstation with emulation software to the switch console
port.
The default data characteristics of the console port are 9600, 8, 1, no
parity. You might need to press the Return key several times to see the
command-line prompt.
Step 2 enable password password Enter privileged EXEC mode.
Step 3 configure terminal Enter global configuration mode.
Step 4 line vty 0 15 Configure the number of Telnet sessions (lines), and enter line
configuration mode.
There are 16 possible sessions on a command-capable switch. The 0
and 15 mean that you are configuring all 16 possible Telnet sessions.
Step 5 password password Enter a Telnet password for the line or lines.
For password, specify a string from 1 to 25 alphanumeric characters. The
string cannot start with a number, is case sensitive, and allows spaces but
ignores leading spaces. By default, no password is defined.
Step 6 end Return to privileged EXEC mode.
Step 7 show running-config Verify your entries.
The password is listed under the command line vty 0 15.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
Beginning in privileged EXEC mode, follow these steps to establish a username-based authentication
system that requests a login username and a password:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 username name [privilege level] Enter the username, privilege level, and password for each user.
{password encryption-type password}
• For name, specify the user ID as one word. Spaces and quotation
marks are not allowed.
• (Optional) For level, specify the privilege level the user has after
gaining access. The range is 0 to 15. Level 15 gives privileged EXEC
mode access. Level 1 gives user EXEC mode access.
• For encryption-type, enter 0 to specify that an unencrypted password
will follow. Enter 7 to specify that a hidden password will follow.
• For password, specify the password the user must enter to gain access
to the switch. The password must be from 1 to 25 characters, can
contain embedded spaces, and must be the last option specified in the
username command.
Step 3 line console 0 Enter line configuration mode, and configure the console port (line 0) or
the VTY lines (line 0 to 15).
or
line vty 0 15
Step 4 login local Enable local password checking at login time. Authentication is based on
the username specified in Step 2.
Step 5 end Return to privileged EXEC mode.
Step 6 show running-config Verify your entries.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable username authentication for a specific user, use the no username name global configuration
command. To disable password checking and allow connections without a password, use the no login
line configuration command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 privilege mode level level command Set the privilege level for a command.
• For mode, enter configure for global configuration mode, exec for
EXEC mode, interface for interface configuration mode, or line for
line configuration mode.
• For level, the range is from 0 to 15. Level 1 is for normal user EXEC
mode privileges. Level 15 is the level of access permitted by the
enable password.
• For command, specify the command to which you want to restrict
access.
Step 3 enable password level level password Specify the enable password for the privilege level.
• For level, the range is from 0 to 15. Level 1 is for normal user EXEC
mode privileges.
• For password, specify a string from 1 to 25 alphanumeric characters.
The string cannot start with a number, is case sensitive, and allows
spaces but ignores leading spaces. By default, no password is
defined.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
or The first command displays the password and access level configuration.
The second command displays the privilege level configuration.
show privilege
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
When you set a command to a privilege level, all commands whose syntax is a subset of that command
are also set to that level. For example, if you set the show ip traffic command to level 15, the show
commands and show ip commands are automatically set to privilege level 15 unless you set them
individually to different levels.
To return to the default privilege for a given command, use the no privilege mode level level command
global configuration command.
This example shows how to set the configure command to privilege level 14 and define SecretPswd14
as the password users must enter to use level 14 commands:
Switch(config)# privilege exec level 14 configure
Switch(config)# enable password level 14 SecretPswd14
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 line vty line Select the virtual terminal line on which to restrict access.
Step 3 privilege level level Change the default privilege level for the line.
For level, the range is from 0 to 15. Level 1 is for normal user EXEC mode
privileges. Level 15 is the level of access permitted by the enable
password.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
or The first command displays the password and access level configuration.
show privilege The second command displays the privilege level configuration.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
Users can override the privilege level you set using the privilege level line configuration command by
logging in to the line and enabling a different privilege level. They can lower the privilege level by using
the disable command. If users know the password to a higher privilege level, they can use that password
to enable the higher privilege level. You might specify a high level or privilege level for your console
line to restrict line usage.
To return to the default line privilege level, use the no privilege level line configuration command.
Command Purpose
Step 1 enable level Log in to a specified privilege level.
For level, the range is 0 to 15.
Step 2 disable level Exit to a specified privilege level.
For level, the range is 0 to 15.
Beginning with Cisco IOS Release 12.2(58)SE, switches running the IP services image support
TACACS+ for IPv6. Information is in the “TACACS+ Over an IPv6 Transport” section of the
“Implementing ADSL for IPv6” chapter in the Cisco IOS XE IPv6 Configuration Guide, Release 2.
For information about configuring this feature, see the “Configuring TACACS+ over IPv6” section of
the “Implementing ADSL for IPv6” chapter in the Cisco IOS XE IPv6 Configuration Guide, Release 2.
Note For complete syntax and usage information for the commands used in this section, see the Cisco IOS
Security Command Reference, Release 12.2 and the Cisco IOS IPv6 Command Reference.
Understanding TACACS+
TACACS+ is a security application that provides centralized validation of users attempting to gain access
to your switch. TACACS+ services are maintained in a database on a TACACS+ daemon typically
running on a UNIX or Windows NT workstation. You should have access to and should configure a
TACACS+ server before the configuring TACACS+ features on your switch.
TACACS+ provides for separate and modular authentication, authorization, and accounting facilities.
TACACS+ allows for a single access control server (the TACACS+ daemon) to provide each
service—authentication, authorization, and accounting—independently. Each service can be tied into its
own database to take advantage of other services available on that server or on the network, depending
on the capabilities of the daemon.
The goal of TACACS+ is to provide a method for managing multiple network access points from a single
management service. Your switch can be a network access server along with other Cisco routers and
access servers. A network access server provides connections to a single user, to a network or
subnetwork, and to interconnected networks as shown in Figure 7-1.
Router A
1
IGMP report 224.1.2.3
VLAN
PFC
CPU
0
Forwarding
45750
table
2 3 4 5
TACACS+, administered through the AAA security services, can provide these services:
• Authentication—Provides complete control of authentication through login and password dialog,
challenge and response, and messaging support.
The authentication facility can conduct a dialog with the user (for example, after a username and
password are provided, to challenge a user with several questions, such as home address, mother’s
maiden name, service type, and social security number). The TACACS+ authentication service can
also send messages to user screens. For example, a message could notify users that their passwords
must be changed because of the company’s password aging policy.
• Authorization—Provides fine-grained control over user capabilities for the duration of the user’s
session, including but not limited to setting autocommands, access control, session duration, or
protocol support. You can also enforce restrictions on what commands a user can execute with the
TACACS+ authorization feature.
• Accounting—Collects and sends information used for billing, auditing, and reporting to the
TACACS+ daemon. Network managers can use the accounting facility to track user activity for a
security audit or to provide information for user billing. Accounting records include user identities,
start and stop times, executed commands (such as PPP), number of packets, and number of bytes.
The TACACS+ protocol provides authentication between the switch and the TACACS+ daemon, and it
ensures confidentiality because all protocol exchanges between the switch and the TACACS+ daemon
are encrypted.
You need a system running the TACACS+ daemon software to use TACACS+ on your switch.
TACACS+ Operation
When a user attempts a simple ASCII login by authenticating to a switch using TACACS+, this process
occurs:
1. When the connection is established, the switch contacts the TACACS+ daemon to obtain a username
prompt, which is then displayed to the user. The user enters a username, and the switch then contacts
the TACACS+ daemon to obtain a password prompt. The switch displays the password prompt to
the user, the user enters a password, and the password is then sent to the TACACS+ daemon.
TACACS+ allows a conversation to be held between the daemon and the user until the daemon
receives enough information to authenticate the user. The daemon prompts for a username and
password combination, but can include other items, such as the user’s mother’s maiden name.
2. The switch eventually receives one of these responses from the TACACS+ daemon:
• ACCEPT—The user is authenticated and service can begin. If the switch is configured to
require authorization, authorization begins at this time.
• REJECT—The user is not authenticated. The user can be denied access or is prompted to retry
the login sequence, depending on the TACACS+ daemon.
• ERROR—An error occurred at some time during authentication with the daemon or in the
network connection between the daemon and the switch. If an ERROR response is received, the
switch typically tries to use an alternative method for authenticating the user.
• CONTINUE—The user is prompted for additional authentication information.
After authentication, the user undergoes an additional authorization phase if authorization has been
enabled on the switch. Users must first successfully complete TACACS+ authentication before
proceeding to TACACS+ authorization.
3. If TACACS+ authorization is required, the TACACS+ daemon is again contacted, and it returns an
ACCEPT or REJECT authorization response. If an ACCEPT response is returned, the response
contains data in the form of attributes that direct the EXEC or NETWORK session for that user and
the services that the user can access:
• Telnet, Secure Shell (SSH), rlogin, or privileged EXEC services
• Connection parameters, including the host or client IP address, access list, and user timeouts
Configuring TACACS+
This section describes how to configure your switch to support TACACS+. At a minimum, you must
identify the host or hosts maintaining the TACACS+ daemon and define the method lists for TACACS+
authentication. You can optionally define method lists for TACACS+ authorization and accounting. A
method list defines the sequence and methods to be used to authenticate, to authorize, or to keep accounts
on a user. You can use method lists to designate one or more security protocols to be used, thus ensuring
a backup system if the initial method fails. The software uses the first method listed to authenticate, to
authorize, or to keep accounts on users; if that method does not respond, the software selects the next
method in the list. This process continues until there is successful communication with a listed method
or the method list is exhausted.
This section contains this configuration information:
• Default TACACS+ Configuration, page 7-13
• Identifying the TACACS+ Server Host and Setting the Authentication Key, page 7-13
• Configuring TACACS+ Login Authentication, page 7-14
• Configuring TACACS+ Authorization for Privileged EXEC Access and Network Services,
page 7-16
• Starting TACACS+ Accounting, page 7-16
Note Although TACACS+ configuration is performed through the CLI, the TACACS+ server authenticates
HTTP connections that have been configured with a privilege level of 15.
Identifying the TACACS+ Server Host and Setting the Authentication Key
You can configure the switch to use a single server or AAA server groups to group existing server hosts
for authentication. You can group servers to select a subset of the configured server hosts and use them
for a particular service. The server group is used with a global server-host list and contains the list of IP
addresses of the selected server hosts.
Beginning in privileged EXEC mode, follow these steps to identify the IP host or host maintaining
TACACS+ server and optionally set the encryption key:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 tacacs-server host hostname [port Identify the IP host or hosts maintaining a TACACS+ server. Enter this
integer] [timeout integer] [key string] command multiple times to create a list of preferred hosts. The software
searches for hosts in the order in which you specify them.
• For hostname, specify the name or IP address of the host.
• (Optional) For port integer, specify a server port number. The default
is port 49. The range is 1 to 65535.
• (Optional) For timeout integer, specify a time in seconds the switch
waits for a response from the daemon before it times out and declares
an error. The default is 5 seconds. The range is 1 to 1000 seconds.
• (Optional) For key string, specify the encryption key for encrypting
and decrypting all traffic between the switch and the TACACS+
daemon. You must configure the same key on the TACACS+ daemon
for encryption to be successful.
Step 3 aaa new-model Enable AAA.
Step 4 aaa group server tacacs+ group-name (Optional) Define the AAA server-group with a group name.
This command puts the switch in a server group subconfiguration mode.
Step 5 server ip-address (Optional) Associate a particular TACACS+ server with the defined server
group. Repeat this step for each TACACS+ server in the AAA server
group.
Each server in the group must be previously defined in Step 2.
Command Purpose
Step 6 end Return to privileged EXEC mode.
Step 7 show tacacs Verify your entries.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove the specified TACACS+ server name or address, use the no tacacs-server host hostname
global configuration command. To remove a server group from the configuration list, use the no aaa
group server tacacs+ group-name global configuration command. To remove the IP address of a
TACACS+ server, use the no server ip-address server group subconfiguration command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 aaa new-model Enable AAA.
Command Purpose
Step 3 aaa authentication login {default | Create a login authentication method list.
list-name} method1 [method2...]
• To create a default list that is used when a named list is not specified
in the login authentication command, use the default keyword
followed by the methods that are to be used in default situations. The
default method list is automatically applied to all ports.
• For list-name, specify a character string to name the list you are
creating.
• For method1..., specify the actual method the authentication
algorithm tries. The additional methods of authentication are used
only if the previous method returns an error, not if it fails.
Select one of these methods:
• enable—Use the enable password for authentication. Before you can
use this authentication method, you must define an enable password
by using the enable password global configuration command.
• group tacacs+—Uses TACACS+ authentication. Before you can use
this authentication method, you must configure the TACACS+ server.
For more information, see the “Identifying the TACACS+ Server Host
and Setting the Authentication Key” section on page 7-13.
• line—Use the line password for authentication. Before you can use
this authentication method, you must define a line password. Use the
password password line configuration command.
• local—Use the local username database for authentication. You must
enter username information in the database. Use the username
password global configuration command.
• local-case—Use a case-sensitive local username database for
authentication. You must enter username information in the database
by using the username name password global configuration
command.
• none—Do not use any authentication for login.
Step 4 line [console | tty | vty] line-number Enter line configuration mode, and configure the lines to which you want
[ending-line-number] to apply the authentication list.
Step 5 login authentication {default | Apply the authentication list to a line or set of lines.
list-name}
• If you specify default, use the default list created with the aaa
authentication login command.
• For list-name, specify the list created with the aaa authentication
login command.
Step 6 end Return to privileged EXEC mode.
Step 7 show running-config Verify your entries.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable AAA, use the no aaa new-model global configuration command. To disable AAA
authentication, use the no aaa authentication login {default | list-name} method1 [method2...] global
configuration command. To either disable TACACS+ authentication for logins or to return to the default
value, use the no login authentication {default | list-name} line configuration command.
Configuring TACACS+ Authorization for Privileged EXEC Access and Network Services
AAA authorization limits the services available to a user. When AAA authorization is enabled, the
switch uses information retrieved from the user’s profile, which is located either in the local user
database or on the security server, to configure the user’s session. The user is granted access to a
requested service only if the information in the user profile allows it.
You can use the aaa authorization global configuration command with the tacacs+ keyword to set
parameters that restrict a user’s network access to privileged EXEC mode.
The aaa authorization exec tacacs+ local command sets these authorization parameters:
• Use TACACS+ for privileged EXEC access authorization if authentication was performed by using
TACACS+.
• Use the local database if authentication was not performed by using TACACS+.
Note Authorization is bypassed for authenticated users who log in through the CLI even if authorization has
been configured.
Beginning in privileged EXEC mode, follow these steps to specify TACACS+ authorization for
privileged EXEC access and network services:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 aaa authorization network tacacs+ Configure the switch for user TACACS+ authorization for all
network-related service requests.
Step 3 aaa authorization exec tacacs+ Configure the switch for user TACACS+ authorization if the user has
privileged EXEC access.
The exec keyword might return user profile information (such as
autocommand information).
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable authorization, use the no aaa authorization {network | exec} method1 global configuration
command.
Beginning in privileged EXEC mode, follow these steps to enable TACACS+ accounting for each Cisco
IOS privilege level and for network services:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 aaa accounting network start-stop Enable TACACS+ accounting for all network-related service requests.
tacacs+
Step 3 aaa accounting exec start-stop tacacs+ Enable TACACS+ accounting to send a start-record accounting notice at
the beginning of a privileged EXEC process and a stop-record at the end.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable accounting, use the no aaa accounting {network | exec} {start-stop} method1... global
configuration command.
Note For complete syntax and usage information for the commands used in this section, see the Cisco IOS
Security Command Reference, Release 12.2 and the Cisco IOS IPv6 Command Reference.
Understanding RADIUS
RADIUS is a distributed client/server system that secures networks against unauthorized access.
RADIUS clients run on supported Cisco routers and switches. Clients send authentication requests to a
central RADIUS server, which contains all user authentication and network service access information.
The RADIUS host is normally a multiuser system running RADIUS server software from Cisco (Cisco
Secure Access Control Server Version 3.0), Livingston, Merit, Microsoft, or another software provider.
For more information, see the RADIUS server documentation.
Use RADIUS in these network environments that require access security:
• Networks with multiple-vendor access servers, each supporting RADIUS. For example, access
servers from several vendors use a single RADIUS server-based security database. In an IP-based
network with multiple vendors’ access servers, dial-in users are authenticated through a RADIUS
server that has been customized to work with the Kerberos security system.
• Turnkey network security environments in which applications support the RADIUS protocol, such
as in an access environment that uses a smart card access control system. In one case, RADIUS has
been used with Enigma’s security cards to validates users and to grant access to network resources.
• Networks already using RADIUS. You can add a Cisco switch containing a RADIUS client to the
network. This might be the first step when you make a transition to a TACACS+ server. See
Figure 7-2 on page 7-19.
• Network in which the user must only access a single service. Using RADIUS, you can control user
access to a single host, to a single utility such as Telnet, or to the network through a protocol such
as IEEE 802.1x. For more information about this protocol, see Chapter 8, “Configuring IEEE 802.1x
Port-Based Authentication.”
• Networks that require resource accounting. You can use RADIUS accounting independently of
RADIUS authentication or authorization. The RADIUS accounting functions allow data to be sent
at the start and end of services, showing the amount of resources (such as time, packets, bytes, and
so forth) used during the session. An Internet service provider might use a freeware-based version
of RADIUS access control and accounting software to meet special security and billing needs.
RADIUS is not suitable in these network security situations:
• Multiprotocol access environments. RADIUS does not support AppleTalk Remote Access (ARA),
NetBIOS Frame Control Protocol (NBFCP), NetWare Asynchronous Services Interface (NASI), or
X.25 PAD connections.
• Switch-to-switch or router-to-router situations. RADIUS does not provide two-way authentication.
RADIUS can be used to authenticate from one device to a non-Cisco device if the non-Cisco device
requires authentication.
• Networks using a variety of services. RADIUS generally binds a user to one service model.
R1 RADIUS
server
R2 RADIUS
server
T1 TACACS+
server
Remote T2 TACACS+
PC server
86891
Workstation
RADIUS Operation
When a user attempts to log in and authenticate to a switch that is access controlled by a RADIUS server,
these events occur:
1. The user is prompted to enter a username and password.
2. The username and encrypted password are sent over the network to the RADIUS server.
3. The user receives one of these responses from the RADIUS server:
a. ACCEPT—The user is authenticated.
b. REJECT—The user is either not authenticated and is prompted to re-enter the username and
password, or access is denied.
c. CHALLENGE—A challenge requires additional data from the user.
d. CHALLENGE PASSWORD—A response requests the user to select a new password.
The ACCEPT or REJECT response is bundled with additional data that is used for privileged EXEC or
network authorization. Users must first successfully complete RADIUS authentication before
proceeding to RADIUS authorization, if it is enabled. The additional data included with the ACCEPT or
REJECT packets includes these items:
• Telnet, SSH, rlogin, or privileged EXEC services
• Connection parameters, including the host or client IP address, access list, and user timeouts
Configuring RADIUS
This section describes how to configure your switch to support RADIUS. At a minimum, you must
identify the host or hosts that run the RADIUS server software and define the method lists for RADIUS
authentication. You can optionally define method lists for RADIUS authorization and accounting.
A method list defines the sequence and methods to be used to authenticate, to authorize, or to keep
accounts on a user. You can use method lists to designate one or more security protocols to be used (such
as TACACS+ or local username lookup), thus ensuring a backup system if the initial method fails. The
software uses the first method listed to authenticate, to authorize, or to keep accounts on users; if that
method does not respond, the software selects the next method in the list. This process continues until
there is successful communication with a listed method or the method list is exhausted.
You should have access to and should configure a RADIUS server before configuring RADIUS features
on your switch.
This section contains this configuration information:
• Default RADIUS Configuration, page 7-20
• Identifying the RADIUS Server Host, page 7-20 (required)
• Configuring RADIUS Login Authentication, page 7-23 (required)
• Defining AAA Server Groups, page 7-25 (optional)
• Configuring RADIUS Authorization for User Privileged Access and Network Services, page 7-27
(optional)
• Starting RADIUS Accounting, page 7-28 (optional)
• Configuring Settings for All RADIUS Servers, page 7-29 (optional)
• Configuring the Switch to Use Vendor-Specific RADIUS Attributes, page 7-29 (optional)
• Configuring the Switch for Vendor-Proprietary RADIUS Server Communication, page 7-30
(optional)
• Configuring RADIUS Server Load Balancing, page 7-31 (optional)
You identify RADIUS security servers by their hostname or IP address, hostname and specific UDP port
numbers, or their IP address and specific UDP port numbers. The combination of the IP address and the
UDP port number creates a unique identifier, allowing different ports to be individually defined as
RADIUS hosts providing a specific AAA service. This unique identifier 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, accounting—the second host entry configured acts as a fail-over backup to the first one. Using
this example, if the first host entry fails to provide accounting services, the switch tries the second host
entry configured on the same device for accounting services. (The RADIUS host entries are tried in the
order that they are configured.)
A RADIUS server and the switch use a shared secret text string to encrypt passwords and exchange
responses. To configure RADIUS to use the AAA security commands, you must specify the host running
the RADIUS server daemon and a secret text (key) string that it shares with the switch.
The timeout, retransmission, and encryption key values can be configured globally for all RADIUS
servers, on a per-server basis, or in some combination of global and per-server settings. To apply these
settings globally to all RADIUS servers communicating with the switch, use the three unique global
configuration commands: radius-server timeout, radius-server retransmit, and radius-server key. To
apply these values on a specific RADIUS server, use the radius-server host global configuration
command.
Note If you configure both global and per-server functions (timeout, retransmission, and key commands) on
the switch, the per-server timer, retransmission, and key value commands override global timer,
retransmission, and key value commands. For information on configuring these setting on all RADIUS
servers, see the “Configuring Settings for All RADIUS Servers” section on page 7-29.
You can configure the switch to use AAA server groups to group existing server hosts for authentication.
For more information, see the “Defining AAA Server Groups” section on page 7-25.
Beginning in privileged EXEC mode, follow these steps to configure per-server RADIUS server
communication. This procedure is required.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 radius-server host {hostname | Specify the IP address or hostname of the remote RADIUS server host.
ip-address} [auth-port port-number]
• (Optional) For auth-port port-number, specify the UDP destination
[acct-port port-number] [timeout
port for authentication requests.
seconds] [retransmit retries] [key
string] • (Optional) For acct-port port-number, specify the UDP destination
port for accounting requests.
• (Optional) For timeout seconds, specify the time interval that the
switch waits for the RADIUS server to reply before resending. The
range is 1 to 1000. This setting overrides the radius-server timeout
global configuration command setting. If no timeout is set with the
radius-server host command, the setting of the radius-server
timeout command is used.
• (Optional) For retransmit retries, specify the number of times a
RADIUS request is resent to a server if that server is not responding
or responding slowly. The range is 1 to 1000. If no retransmit value is
set with the radius-server host command, the setting of the
radius-server retransmit global configuration command is used.
• (Optional) For key string, specify the authentication and encryption
key used between the switch and the RADIUS daemon running on the
RADIUS server.
Note The key is a text string that must match the encryption key used
on the RADIUS server. Always configure the key as the last item
in the radius-server host command. Leading spaces are ignored,
but spaces within and at the end of the key are used. If you use
spaces in your key, do not enclose the key in quotation marks
unless the quotation marks are part of the key.
To configure the switch to recognize more than one host entry associated
with a single IP address, enter this command as many times as necessary,
making sure that each UDP port number is different. The switch software
searches for hosts in the order in which you specify them. Set the timeout,
retransmit, and encryption key values to use with the specific RADIUS
host.
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove the specified RADIUS server, use the no radius-server host hostname | ip-address global
configuration command.
This example shows how to configure one RADIUS server to be used for authentication and another to
be used for accounting:
Switch(config)# radius-server host 172.29.36.49 auth-port 1612 key rad1
Switch(config)# radius-server host 172.20.36.50 acct-port 1618 key rad2
This example shows how to configure host1 as the RADIUS server and to use the default ports for both
authentication and accounting:
Switch(config)# radius-server host host1
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.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 aaa new-model Enable AAA.
Command Purpose
Step 3 aaa authentication login {default | Create a login authentication method list.
list-name} method1 [method2...]
• To create a default list that is used when a named list is not specified
in the login authentication command, use the default keyword
followed by the methods that are to be used in default situations. The
default method list is automatically applied to all ports.
• For list-name, specify a character string to name the list you are
creating.
• For method1..., specify the actual method the authentication
algorithm tries. The additional methods of authentication are used
only if the previous method returns an error, not if it fails.
Select one of these methods:
– enable—Use the enable password for authentication. Before you
can use this authentication method, you must define an enable
password by using the enable password global configuration
command.
– group radius—Use RADIUS authentication. Before you can use
this authentication method, you must configure the RADIUS
server. For more information, see the “Identifying the RADIUS
Server Host” section on page 7-20.
– line—Use the line password for authentication. Before you can
use this authentication method, you must define a line password.
Use the password password line configuration command.
– local—Use the local username database for authentication. You
must enter username information in the database. Use the
username name password global configuration command.
– local-case—Use a case-sensitive local username database for
authentication. You must enter username information in the
database by using the username password global configuration
command.
– none—Do not use any authentication for login.
Step 4 line [console | tty | vty] line-number Enter line configuration mode, and configure the lines to which you want
[ending-line-number] to apply the authentication list.
Step 5 login authentication {default | Apply the authentication list to a line or set of lines.
list-name}
• If you specify default, use the default list created with the aaa
authentication login command.
• For list-name, specify the list created with the aaa authentication
login command.
Step 6 end Return to privileged EXEC mode.
Step 7 show running-config Verify your entries.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable AAA, use the no aaa new-model global configuration command. To disable AAA
authentication, use the no aaa authentication login {default | list-name} method1 [method2...] global
configuration command. To either disable RADIUS authentication for logins or to return to the default
value, use the no login authentication {default | list-name} line configuration command.
Beginning in privileged EXEC mode, follow these steps to define the AAA server group and associate a
particular RADIUS server with it:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 radius-server host {hostname | Specify the IP address or hostname of the remote RADIUS server host.
ip-address} [auth-port port-number]
• (Optional) For auth-port port-number, specify the UDP destination
[acct-port port-number] [timeout
port for authentication requests.
seconds] [retransmit retries] [key
string] • (Optional) For acct-port port-number, specify the UDP destination
port for accounting requests.
• (Optional) For timeout seconds, specify the time interval that the
switch waits for the RADIUS server to reply before resending. The
range is 1 to 1000. This setting overrides the radius-server timeout
global configuration command setting. If no timeout is set with the
radius-server host command, the setting of the radius-server
timeout command is used.
• (Optional) For retransmit retries, specify the number of times a
RADIUS request is resent to a server if that server is not responding
or responding slowly. The range is 1 to 1000. If no retransmit value is
set with the radius-server host command, the setting of the
radius-server retransmit global configuration command is used.
• (Optional) For key string, specify the authentication and encryption
key used between the switch and the RADIUS daemon running on the
RADIUS server.
Note The key is a text string that must match the encryption key used
on the RADIUS server. Always configure the key as the last item
in the radius-server host command. Leading spaces are ignored,
but spaces within and at the end of the key are used. If you use
spaces in your key, do not enclose the key in quotation marks
unless the quotation marks are part of the key.
To configure the switch to recognize more than one host entry associated
with a single IP address, enter this command as many times as necessary,
making sure that each UDP port number is different. The switch software
searches for hosts in the order in which you specify them. Set the timeout,
retransmit, and encryption key values to use with the specific RADIUS
host.
Step 3 aaa new-model Enable AAA.
Step 4 aaa group server radius group-name Define the AAA server-group with a group name.
This command puts the switch in a server group configuration mode.
Step 5 server ip-address Associate a particular RADIUS server with the defined server group.
Repeat this step for each RADIUS server in the AAA server group.
Each server in the group must be previously defined in Step 2.
Step 6 end Return to privileged EXEC mode.
Step 7 show running-config Verify your entries.
Command Purpose
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
Step 9 Enable RADIUS login authentication. See the “Configuring RADIUS
Login Authentication” section on page 7-23.
To remove the specified RADIUS server, use the no radius-server host hostname | ip-address global
configuration command. To remove a server group from the configuration list, use the no aaa group
server radius group-name global configuration command. To remove the IP address of a RADIUS
server, use the no server ip-address server group configuration command.
In this example, the switch is configured to recognize two different RADIUS group servers (group1 and
group2). Group1 has two different host entries on the same RADIUS server configured for the same
services. The second host entry acts as a fail-over backup to the first entry.
Switch(config)# radius-server host 172.20.0.1 auth-port 1000 acct-port 1001
Switch(config)# radius-server host 172.10.0.1 auth-port 1645 acct-port 1646
Switch(config)# aaa new-model
Switch(config)# aaa group server radius group1
Switch(config-sg-radius)# server 172.20.0.1 auth-port 1000 acct-port 1001
Switch(config-sg-radius)# exit
Switch(config)# aaa group server radius group2
Switch(config-sg-radius)# server 172.20.0.1 auth-port 2000 acct-port 2001
Switch(config-sg-radius)# exit
Configuring RADIUS Authorization for User Privileged Access and Network Services
AAA authorization limits the services available to a user. When AAA authorization is enabled, the
switch uses information retrieved from the user’s profile, which is in the local user database or on the
security server, to configure the user’s session. The user is granted access to a requested service only if
the information in the user profile allows it.
You can use the aaa authorization global configuration command with the radius keyword to set
parameters that restrict a user’s network access to privileged EXEC mode.
The aaa authorization exec radius local command sets these authorization parameters:
• Use RADIUS for privileged EXEC access authorization if authentication was performed by using
RADIUS.
• Use the local database if authentication was not performed by using RADIUS.
Note Authorization is bypassed for authenticated users who log in through the CLI even if authorization has
been configured.
Beginning in privileged EXEC mode, follow these steps to specify RADIUS authorization for privileged
EXEC access and network services:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 aaa authorization network radius Configure the switch for user RADIUS authorization for all
network-related service requests.
Command Purpose
Step 3 aaa authorization exec radius Configure the switch for user RADIUS authorization if the user has
privileged EXEC access.
The exec keyword might return user profile information (such as
autocommand information).
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable authorization, use the no aaa authorization {network | exec} method1 global configuration
command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 aaa accounting network start-stop Enable RADIUS accounting for all network-related service requests.
radius
Step 3 aaa accounting exec start-stop radius Enable RADIUS accounting to send a start-record accounting notice at
the beginning of a privileged EXEC process and a stop-record at the end.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable accounting, use the no aaa accounting {network | exec} {start-stop} method1... global
configuration command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 radius-server key string Specify the shared secret text string used between the switch and all
RADIUS servers.
Note The key is a text string that must match the encryption key used on
the RADIUS server. Leading spaces are ignored, but spaces within
and at the end of the key are used. If you use spaces in your key, do
not enclose the key in quotation marks unless the quotation marks
are part of the key.
Step 3 radius-server retransmit retries Specify the number of times the switch sends each RADIUS request to the
server before giving up. The default is 3; the range 1 to 1000.
Step 4 radius-server timeout seconds Specify the number of seconds a switch waits for a reply to a RADIUS
request before resending the request. The default is 5 seconds; the range is
1 to 1000.
Step 5 radius-server deadtime minutes Specify the number of minutes a RADIUS server, which is not responding
to authentication requests, to be skipped, thus avoiding the wait for the
request to timeout before trying the next configured server. The default is
0; the range is 1 to 1440 minutes.
Step 6 end Return to privileged EXEC mode.
Step 7 show running-config Verify your settings.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default setting for the retransmit, timeout, and deadtime, use the no forms of these
commands.
Protocol is a value of the Cisco protocol attribute for a particular type of authorization. Attribute and
value are an appropriate attribute-value (AV) pair defined in the Cisco TACACS+ specification, and sep
is = for mandatory attributes and is * for optional attributes. The full set of features available for
TACACS+ authorization can then be used for RADIUS.
For example, this AV pair activates Cisco’s multiple named ip address pools feature during IP
authorization (during PPP IPCP address assignment):
cisco-avpair= ”ip:addr-pool=first“
This example shows how to provide a user logging in from a switch with immediate access to privileged
EXEC commands:
cisco-avpair= ”shell:priv-lvl=15“
This example shows how to specify an authorized VLAN in the RADIUS server database:
cisco-avpair= ”tunnel-type(#64)=VLAN(13)”
cisco-avpair= ”tunnel-medium-type(#65)=802 media(6)”
cisco-avpair= ”tunnel-private-group-id(#81)=vlanid”
This example shows how to apply an input ACL in ASCII format to a port for the duration of this
connection:
cisco-avpair= “ip:inacl#1=deny ip 10.10.10.10 0.0.255.255 20.20.20.20 255.255.0.0”
cisco-avpair= “ip:inacl#2=deny ip 10.10.10.10 0.0.255.255 any”
cisco-avpair= “mac:inacl#3=deny any any decnet-iv”
This example shows how to apply an output ACL in ASCII format to a port for the duration of this
connection:
cisco-avpair= “ip:outacl#2=deny ip 10.10.10.10 0.0.255.255 any”
Other vendors have their own unique vendor-IDs, options, and associated VSAs. For more information
about vendor-IDs and VSAs, seeo RFC 2138, “Remote Authentication Dial-In User Service (RADIUS).”
Beginning in privileged EXEC mode, follow these steps to configure the switch to recognize and use
VSAs:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 radius-server vsa send [accounting | Enable the switch to recognize and use VSAs as defined by RADIUS IETF
authentication] attribute 26.
• (Optional) Use the accounting keyword to limit the set of recognized
vendor-specific attributes to only accounting attributes.
• (Optional) Use the authentication keyword to limit the set of
recognized vendor-specific attributes to only authentication attributes.
If you enter this command without keywords, both accounting and
authentication vendor-specific attributes are used.
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify your settings.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
For a complete list of RADIUS attributes or more information about vendor-specific attribute 26, seeo
the “RADIUS Attributes” appendix in the Cisco IOS Security Configuration Guide, Release 12.2.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 radius-server host {hostname | ip-address} non-standard Specify the IP address or hostname of the remote
RADIUS server host and identify that it is using a
vendor-proprietary implementation of RADIUS.
Step 3 radius-server key string Specify the shared secret text string used between the
switch and the vendor-proprietary RADIUS server.
The switch and the RADIUS server use this text
string to encrypt passwords and exchange responses.
Note The key is a text string that must match the
encryption key used on the RADIUS server.
Leading spaces are ignored, but spaces within
and at the end of the key are used. If you use
spaces in your key, do not enclose the key in
quotation marks unless the quotation marks
are part of the key.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your settings.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To delete the vendor-proprietary RADIUS host, use the no radius-server host {hostname | ip-address}
non-standard global configuration command. To disable the key, use the no radius-server key global
configuration command.
This example shows how to specify a vendor-proprietary RADIUS host and to use a secret key of rad124
between the switch and the server:
Switch(config)# radius-server host 172.20.30.15 nonstandard
Switch(config)# radius-server key rad124
Note In the Kerberos configuration examples and in the Cisco IOS Security Command Reference,
Release 12.2, the trusted third party can be a Catalyst 3750 Metro switch that supports Kerberos, that is
configured as a network security server, and that can authenticate users by using the Kerberos Protocol.
Understanding Kerberos
Kerberos is a secret-key network authentication protocol, which was developed at the Massachusetts
Institute of Technology (MIT). It uses the Data Encryption Standard (DES) cryptographic algorithm for
encryption and authentication and authenticates requests for network resources. Kerberos uses the
concept of a trusted third party to perform secure verification of users and services. This trusted third
party is called the key distribution center (KDC).
Kerberos verifies that users are who they claim to be and the network services that they use are what the
services claim to be. To do this, a KDC or trusted Kerberos server issues tickets to users. These tickets,
which have a limited lifespan, are stored in user credential caches. The Kerberos server uses the tickets
instead of usernames and passwords to authenticate users and network services.
Note A Kerberos server can be a Catalyst 3750 Metro switch that is configured as a network security server
and that can authenticate users by using the Kerberos Protocol.
The Kerberos credential scheme uses a process called single logon. This process authenticates a user
once and then allows secure authentication (without encrypting another password) wherever that user
credential is accepted.
This software release supports Kerberos 5, which allows organizations that are already using Kerberos 5
to use the same Kerberos authentication database on the KDC that they are already using on their other
network hosts (such as UNIX servers and PCs).
Term Definition
Authentication A process by which a user or service identifies itself to another service. For
example, a client can authenticate to a switch or a switch can authenticate to
another switch.
Authorization A means by which the switch identifies what privileges the user has in a network
or on the switch and what actions the user can perform.
Credential A general term that refers to authentication tickets, such as ticket granting tickets
(TGTs) and service credentials. Kerberos credentials verify the identity of a user
or service. If a network service decides to trust the Kerberos server that issued a
ticket, it can be used in place of re-entering a username and password. Credentials
have a default lifespan of 8 hours.
Instance An authorization level label for Kerberos principals. Most Kerberos principals are
of the form user@REALM (for example, smith@EXAMPLE.COM). A Kerberos
principal with a Kerberos instance has the form user/instance@REALM (for
example, smith/admin@EXAMPLE.COM). The Kerberos instance can be used to
specify the authorization level for the user if authentication is successful. The
server of each network service might implement and enforce the authorization
mappings of Kerberos instances but is not required to do so.
Note The Kerberos principal and instance names must be in all lowercase
characters. The Kerberos realm name must be in all uppercase characters.
KDC Key distribution center (KDC) that consists of a Kerberos server and database
program that is running on a network host.
Kerberized A term that describes applications and services that have been modified to support
the Kerberos credential infrastructure.
Kerberos realm A domain consisting of users, hosts, and network services that are registered to a
Kerberos server. The Kerberos server is trusted to verify the identity of a user or
network service to another user or network service.
Note The Kerberos realm name must be in all uppercase characters.
Kerberos server A daemon that is running on a network host. Users and network services register
their identity with the Kerberos server. Network services query the Kerberos server
to authenticate to other network services.
KEYTAB A password that a network service shares with the KDC. In Kerberos 5 and later
Kerberos versions, the network service authenticates an encrypted service
credential by using the key table (KEYTAB) to decrypt it. In Kerberos versions
earlier than Kerberos 5, KEYTAB is referred to as server table (SRVTAB).
Principal Also known as a Kerberos identity, this is who you are or what a service is
according to the Kerberos server.
Note The Kerberos principal name must be in all lowercase characters.
Term Definition
Service credential A credential for a network service. When issued from the KDC, this credential is
encrypted with the password shared by the network service and the KDC. The
password is also shared with the user TGT.
SRVTAB A password that a network service shares with the KDC. In Kerberos 5 or later
Kerberos versions, SRVTAB is referred to as KEYTAB.
TGT Ticket granting ticket that is a credential that the KDC issues to authenticated
users. When users receive a TGT, they can authenticate to network services within
the Kerberos realm represented by the KDC.
Kerberos Operation
A Kerberos server can be a Catalyst 3750 Metro switch that is configured as a network security server
and that can authenticate remote users by using the Kerberos Protocol. Although you can customize
Kerberos in a number of ways, remote users attempting to access network services must pass through
three layers of security before they can access network services.
To authenticate to network services by using a Catalyst 3750 Metro switch as a Kerberos server, remote
users must follow these steps:
1. Authenticating to a Boundary Switch, page 7-34
2. Obtaining a TGT from a KDC, page 7-35
3. Authenticating to Network Services, page 7-35
Configuring Kerberos
So that remote users can authenticate to network services, you must configure the hosts and the KDC in
the Kerberos realm to communicate and mutually authenticate users and network services. To do this,
you must identify them to each other. You add entries for the hosts to the Kerberos database on the KDC
and add KEYTAB files generated by the KDC to all hosts in the Kerberos realm. You also create entries
for the users in the KDC database.
When you add or create entries for the hosts and users, follow these guidelines:
• The Kerberos principal name must be in all lowercase characters.
• The Kerberos instance name must be in all lowercase characters.
• The Kerberos realm name must be in all uppercase characters.
Note A Kerberos server can be a Catalyst 3750 Metro switch that is configured as a network security server
and that can authenticate users by using the Kerberos Protocol.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 aaa new-model Enable AAA.
Step 3 aaa authentication login default local Set the login authentication to use the local username database. The
default keyword applies the local user database authentication to all
ports.
Step 4 aaa authorization exec local Configure user AAA authorization, check the local database, and allow
the user to run an EXEC shell.
Step 5 aaa authorization network local Configure user AAA authorization for all network-related service
requests.
Step 6 username name [privilege level] Enter the local database, and establish a username-based authentication
{password encryption-type password} system.
Repeat this command for each user.
• For name, specify the user ID as one word. Spaces and quotation
marks are not allowed.
• (Optional) For level, specify the privilege level the user has after
gaining access. The range is 0 to 15. Level 15 gives privileged EXEC
mode access. Level 0 gives user EXEC mode access.
• For encryption-type, enter 0 to specify that an unencrypted password
follows. Enter 7 to specify that a hidden password follows.
• For password, specify the password the user must enter to gain access
to the switch. The password must be from 1 to 25 characters, can
contain embedded spaces, and must be the last option specified in the
username command.
Step 7 end Return to privileged EXEC mode.
Step 8 show running-config Verify your entries.
Step 9 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable AAA, use the no aaa new-model global configuration command. To disable authorization,
use the no aaa authorization {network | exec} method1 global configuration command.
Note To secure the switch for HTTP access by using AAA methods, you must configure the switch with the
ip http authentication aaa global configuration command. Configuring AAA authentication does not
secure the switch for HTTP access by using AAA methods.
For more information about the ip http authentication command, see the Cisco IOS Security Command
Reference, Release 12.2.
Note For complete syntax and usage information for the commands used in this section, see the command
reference for this release and the command reference for Cisco IOS Release 12.2 at this URL:
http://www.cisco.com/en/US/docs/ios/12_2/security/command/reference/srfssh.html and the Cisco IOS
IPv6 Command Reference.
Understanding SSH
SSH is a protocol that provides a secure, remote connection to a device. SSH provides more security for
remote connections than Telnet does by providing strong encryption when a device is authenticated. This
software release supports SSH Version 1 (SSHv1) and SSH Version 2 (SSHv2).
This section consists of these topics:
• SSH Servers, Integrated Clients, and Supported Versions, page 7-38
• Limitations, page 7-38
Limitations
These limitations apply to SSH:
• The switch supports Rivest, Shamir, and Adelman (RSA) authentication.
• SSH supports only the execution-shell application.
• The SSH server and the SSH client are supported only on DES (56-bit) and 3DES (168-bit) data
encryption software.
• The switch supports the Advanced Encryption Standard (AES) encryption algorithm with a 128-bit
key, 192-bit key, or 256-bit key. However, symmetric cipher AES to encrypt the keys is not
supported.
Configuring SSH
This section has this configuration information:
• Configuration Guidelines, page 7-39
• Setting Up the Switch to Run SSH, page 7-39 (required)
• Configuring the SSH Server, page 7-40 (required only if you are configuring the switch as an SSH
server)
Configuration Guidelines
Follow these guidelines when configuring the switch as an SSH server or SSH client:
• An RSA key pair generated by a SSHv1 server can be used by an SSHv2 server, and the reverse.
• If you get CLI error messages after entering the crypto key generate rsa global configuration
command, an RSA key pair has not been generated. Reconfigure the hostname and domain, and then
enter the crypto key generate rsa command. For more information, see the “Setting Up the Switch
to Run SSH” section on page 7-39.
• When generating the RSA key pair, the message No host name specified might appear. If it does,
you must configure a hostname by using the hostname global configuration command.
• When generating the RSA key pair, the message No domain specified might appear. If it does, you
must configure an IP domain name by using the ip domain-name global configuration command.
• When configuring the local authentication and authorization authentication method, make sure that
AAA is disabled on the console.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 hostname hostname Configure a hostname for your switch.
Step 3 ip domain-name domain_name Configure a host domain for your switch.
Step 4 crypto key generate rsa Enable the SSH server for local and remote authentication on the switch
and generate an RSA key pair.
We recommend that a minimum modulus size of 1024 bits.
When you generate RSA keys, you are prompted to enter a modulus
length. A longer modulus length might be more secure, but it takes longer
to generate and to use.
Step 5 end Return to privileged EXEC mode.
Command Purpose
Step 6 show ip ssh Show the version and configuration information for your SSH server.
or
show ssh Show the status of the SSH server on the switch.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
To delete the RSA key pair, use the crypto key zeroize rsa global configuration command. After the
RSA key pair is deleted, the SSH server is automatically disabled.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip ssh version [1 | 2] (Optional) Configure the switch to run SSH Version 1 or SSH Version 2.
• 1—Configure the switch to run SSH Version 1.
• 2—Configure the switch to run SSH Version 2.
If you do not enter this command or do not specify a keyword, the SSH
server selects the latest SSH version supported by the SSH client. For
example, if the SSH client supports SSHv1 and SSHv2, the SSH server
selects SSHv2.
Step 3 ip ssh {timeout seconds | Configure the SSH control parameters:
authentication-retries number}
• Specify the time-out value in seconds; the default is 120 seconds. The
range is 0 to 120 seconds. This parameter applies to the SSH
negotiation phase. After the connection is established, the switch uses
the default time-out values of the CLI-based sessions.
By default, up to five simultaneous, encrypted SSH connections for
multiple CLI-based sessions over the network are available (session 0
to session 4). After the execution shell starts, the CLI-based session
time-out value returns to the default of 10 minutes.
• Specify the number of times that a client can re-authenticate to the
server. The default is 3; the range is 0 to 5.
Repeat this step when configuring both parameters.
Step 4 line vty line_number (Optional) Configure the virtual terminal line settings.
[ending_line_number]
• Enter line configuration mode to configure the virtual terminal line
transport input ssh settings. For line_number and ending_line_number, specify a pair of
lines. The range is 0 to 15.
• Specify that the switch prevent non-SSH Telnet connections. This
limits the router to only SSH connections.
Step 5 end Return to privileged EXEC mode.
Command Purpose
Step 6 show ip ssh Show the version and configuration information for your SSH server.
or
show ssh Show the status of the SSH server connections on the switch.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default SSH control parameters, use the no ip ssh {timeout | authentication-retries}
global configuration command.
Table 7-3 Commands for Displaying the SSH Server Configuration and Status
Command Purpose
show ip ssh Shows the version and configuration information for the SSH server.
show ssh Shows the status of the SSH server.
For more information about these commands, see the “Secure Shell Commands” section in the “Other
Security Features” chapter of the Cisco IOS Security Command Reference, Cisco IOS Release 12.2, at
this URL:
http://www.cisco.com/en/US/docs/ios/12_2/security/command/reference/srfssh.html
Note The certificate authorities and trustpoints must be configured on each device individually. Copying them
from other devices makes them invalid on the switch.
If a self-signed certificate has been generated, this information is included in the output of the show
running-config privileged EXEC command. This is a partial sample output from that command
displaying a self-signed certificate.
Switch# show running-config
Building configuration...
<output truncated>
<output truncated>
You can remove this self-signed certificate by disabling the secure HTTP server and entering the no
crypto pki trustpoint TP-self-signed-30890755072 global configuration command. If you later
re-enable a secure HTTP server, a new self-signed certificate is generated.
Note The values that follow TP self-signed depend on the serial number of the device.
You can use an optional command (ip http secure-client-auth) to allow the HTTPS server to request an
X.509v3 certificate from the client. Authenticating the client provides more security than server
authentication by itself.
For additional information on Certificate Authorities, see the “Configuring Certification Authority
Interoperability” chapter in the Cisco IOS Security Configuration Guide, Release 12.2.
CipherSuites
A CipherSuite specifies the encryption algorithm and the digest algorithm to use on a SSL connection.
When connecting to the HTTPS server, the client Web browser offers a list of supported CipherSuites,
and the client and server negotiate the best encryption algorithm to use from those on the list that are
supported by both. For example, Netscape Communicator 4.76 supports U.S. security with RSA Public
Key Cryptography, MD2, MD5, RC2-CBC, RC4, DES-CBC, and DES-EDE3-CBC.
For the best possible encryption, you should use a client browser that supports 128-bit encryption, such
as Microsoft Internet Explorer Version 5.5 (or later) or Netscape Communicator Version 4.76 (or later).
The SSL_RSA_WITH_DES_CBC_SHA CipherSuite provides less security than the other CipherSuites,
as it does not offer 128-bit encryption.
The more secure and more complex CipherSuites require slightly more processing time. This list defines
the CipherSuites supported by the switch and ranks them from fastest to slowest in terms of router
processing load (speed):
1. SSL_RSA_WITH_DES_CBC_SHA—RSA key exchange (RSA Public Key Cryptography) with
DES-CBC for message encryption and SHA for message digest
2. SSL_RSA_WITH_RC4_128_MD5—RSA key exchange with RC4 128-bit encryption and MD5 for
message digest
3. SSL_RSA_WITH_RC4_128_SHA—RSA key exchange with RC4 128-bit encryption and SHA for
message digest
Configuring a CA Trustpoint
For secure HTTP connections, we recommend that you configure an official CA trustpoint.
A CA trustpoint is more secure than a self-signed certificate.
Beginning in privileged EXEC mode, follow these steps to configure a CA trustpoint:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 hostname hostname Specify the hostname of the switch (required only if you have not
previously configured a hostname). The hostname is required for security
keys and certificates.
Command Purpose
Step 3 ip domain-name domain-name Specify the IP domain name of the switch (required only if you have not
previously configured an IP domain name). The domain name is required
for security keys and certificates.
Step 4 crypto key generate rsa (Optional) Generate an RSA key pair. RSA key pairs are required before
you can obtain a certificate for the switch. RSA key pairs are generated
automatically. You can use this command to regenerate the keys, if
needed.
Step 5 crypto ca trustpoint name Specify a local configuration name for the CA trustpoint and enter CA
trustpoint configuration mode.
Step 6 enrollment url url Specify the URL to which the switch should send certificate requests.
Step 7 enrollment http-proxy host-name (Optional) Configure the switch to obtain certificates from the CA
port-number through an HTTP proxy server.
Step 8 crl query url Configure the switch to request a certificate revocation list (CRL) to
ensure that the certificate of the peer has not been revoked.
Step 9 primary (Optional) Specify that the trustpoint should be used as the primary
(default) trustpoint for CA requests.
Step 10 exit Exit CA trustpoint configuration mode and return to global configuration
mode.
Step 11 crypto ca authentication name Authenticate the CA by getting the public key of the CA. Use the same
name used in Step 5.
Step 12 crypto ca enroll name Obtain the certificate from the specified CA trustpoint. This command
requests a signed certificate for each RSA key pair.
Step 13 end Return to privileged EXEC mode.
Step 14 show crypto ca trustpoints Verify the configuration.
Step 15 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no crypto ca trustpoint name global configuration command to delete all identity information
and certificates associated with the CA.
Beginning in privileged EXEC mode, follow these steps to configure a secure HTTP server:
Command Purpose
Step 1 show ip http server status (Optional) Display the status of the HTTP server to determine if the secure
HTTP server feature is supported in the software. You should see one of
these lines in the output:
HTTP secure server capability: Present
or
HTTP secure server capability: Not present
Step 2 configure terminal Enter global configuration mode.
Step 3 ip http secure-server Enable the HTTPS server if it has been disabled. The HTTPS server is
enabled by default.
Step 4 ip http secure-port port-number (Optional) Specify the port number to be used for the HTTPS server. The
default port number is 443. Valid options are 443 or any number in the
range 1025 to 65535.
Step 5 ip http secure-ciphersuite (Optional) Specify the CipherSuites (encryption algorithms) to be used
{[3des-ede-cbc-sha] [rc4-128-md5] for encryption over the HTTPS connection. If you do not have a reason to
[rc4-128-sha] [des-cbc-sha]} specify a particularly CipherSuite, you should allow the server and client
to negotiate a CipherSuite that they both support. This is the default.
Step 6 ip http secure-client-auth (Optional) Configure the HTTP server to request an X.509v3 certificate
from the client for authentication during the connection process. The
default is for the client to request a certificate from the server, but the
server does not attempt to authenticate the client.
Step 7 ip http secure-trustpoint name Specify the CA trustpoint to use to get an X.509v3 security certificate and
to authenticate the client certificate connection.
Note Use of this command assumes you have already configured a CA
trustpoint according to the previous procedure.
Step 8 ip http path path-name (Optional) Set a base HTTP path for HTML files. The path specifies the
location of the HTTP server files on the local system (usually located in
system flash memory).
Step 9 ip http access-class access-list-number (Optional) Specify an access list to use to allow access to the HTTP server.
Step 10 ip http max-connections value (Optional) Set the maximum number of concurrent connections that are
allowed to the HTTP server. The range is 1 to 16; the default value is 5.
Step 11 ip http timeout-policy idle seconds life (Optional) Specify how long a connection to the HTTP server can remain
seconds requests value open under the defined circumstances:
• idle—the maximum time period when no data is received or response
data cannot be sent. The range is 1 to 600 seconds. The default is
180 seconds (3 minutes).
• life—the maximum time period from the time that the connection is
established. The range is 1 to 86400 seconds (24 hours). The default
is 180 seconds.
• requests—the maximum number of requests processed on a
persistent connection. The maximum value is 86400. The default is 1.
Step 12 end Return to privileged EXEC mode.
Command Purpose
Step 13 show ip http server secure status Display the status of the HTTP secure server to verify the configuration.
Step 14 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no ip http server global configuration command to disable the standard HTTP server. Use the
no ip http secure-server global configuration command to disable the secure HTTP server. Use the no
ip http secure-port and the no ip http secure-ciphersuite global configuration commands to return to
the default settings. Use the no ip http secure-client-auth global configuration command to remove the
requirement for client authentication.
To verify the secure HTTP connection by using a Web browser, enter https://URL, where the URL is the
IP address or hostname of the server switch. If you configure a port other than the default port, you must
also specify the port number after the URL. For example:
https://209.165.129:1026
or
https://host.domain.com:1026
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip http client secure-trustpoint name (Optional) Specify the CA trustpoint to be used if the remote HTTP server
requests client authentication. Using this command assumes that you have
already configured a CA trustpoint by using the previous procedure. The
command is optional if client authentication is not needed or if a primary
trustpoint has been configured.
Step 3 ip http client secure-ciphersuite (Optional) Specify the CipherSuites (encryption algorithms) to be used
{[3des-ede-cbc-sha] [rc4-128-md5] for encryption over the HTTPS connection. If you do not have a reason to
[rc4-128-sha] [des-cbc-sha]} specify a particular CipherSuite, you should allow the server and client to
negotiate a CipherSuite that they both support. This is the default.
Step 4 end Return to privileged EXEC mode.
Step 5 show ip http client secure status Display the status of the HTTP secure server to verify the configuration.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no ip http client secure-trustpoint name to remove a client trustpoint configuration. Use the
no ip http client secure-ciphersuite to remove a previously configured CipherSuite specification for
the client.
Table 7-4 Commands for Displaying the SSL Secure Server and Client Status
Command Purpose
show ip http client Shows the HTTP secure client configuration.
secure status
show ip http server Shows the HTTP secure server configuration.
secure status
show running-config Shows the generated self-signed certificate for secure HTTP connections.
Note When using SCP, you cannot enter the password into the copy command. You must enter the password
when prompted.
This chapter describes how to configure IEEE 802.1x port-based authentication on the
Catalyst 3750 Metro switch. As LANs extend to hotels, airports, and corporate lobbies, creating insecure
environments, IEEE 802.1x prevents unauthorized devices (clients) from gaining access to the network.
For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
Note Some IEEE 802.1x (dot1x and authentication) commands are visible on the switch but are not
supported. For a list of unsupported commands see Appendix B, “Unsupported Commands in
Cisco IOS Release12.2(58)SE.”
Device Roles
With IEEE 802.1x port-based authentication, the devices in the network have specific roles as shown in
Figure 8-1.
Authentication
server
(RADIUS)
Workstations
(clients)
101229
• Client—the device (workstation) that requests access to the LAN and switch services and responds
to requests from the switch.The workstation must be running IEEE 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 IEEE 802.1x authentication issues, read
the Microsoft Knowledge Base article at this URL:
http://support.microsoft.com/support/kb/articles/Q303/5/97.ASP
• Authentication server—performs 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. In this release, the RADIUS security system with Extensible
Authentication Protocol (EAP) extensions is the only supported authentication server. It is available
in Cisco Secure Access Control Server Version 3.0 or later. RADIUS operates in a client/server
model in which secure authentication information is exchanged between the RADIUS server and
one or more RADIUS clients.
• Switch (edge switch or wireless access point)—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 re-encapsulated 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 server’s frame header is removed, leaving the EAP frame, which is then
encapsulated for Ethernet and sent to the client.
The devices that can act as intermediaries include the Catalyst 3750, Catalyst 3550, Catalyst 2970,
Catalyst 2955, Catalyst 2950, Catalyst 2940 switches, or a wireless access point. These devices must
be running software that supports the RADIUS client and IEEE 802.1x.
Note If IEEE 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 sends 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 8-4.
When the client supplies its identity, the switch begins its role as the intermediary, passing EAP frames
between the client and the authentication server until authentication succeeds or fails. If the
authentication succeeds, the switch port becomes authorized. For more information, see the “Ports in
Authorized and Unauthorized States” section on page 8-4.
The specific exchange of EAP frames depends on the authentication method being used. Figure 8-2
shows a message exchange initiated by the client when the client uses the One-Time-Password (OTP)
authentication method with a RADIUS server.
Authentication
Client server
(RADIUS)
EAPOL-Start
EAP-Request/Identity
EAP-Response/Identity RADIUS Access-Request
EAP-Request/OTP RADIUS Access-Challenge
EAP-Response/OTP RADIUS Access-Request
EAP-Success RADIUS Access-Accept
Port Authorized
EAPOL-Logoff
101228
Port Unauthorized
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 resend 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 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. You can enable
IEEE 802.1x accounting to monitor this activity on IEEE 802.1x-enabled ports:
• User successfully authenticates.
• User logs off.
• Link-down occurs.
• Re-authentication successfully occurs.
• Re-authentication 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.
Supported Topologies
The IEEE 802.1x port-based authentication is supported in two topologies:
• Point-to-point
• Wireless LAN
In a point-to-point configuration (see Figure 8-1 on page 8-2), only one client can be connected to the
IEEE 802.1x-enabled switch port. The switch detects the client when the port link state changes to the
up state. If a client leaves or is replaced with another client, the switch changes the port link state to
down, and the port returns to the unauthorized state.
Figure 8-3 shows IEEE 802.1x port-based authentication in a wireless LAN. The IEEE 802.1x port is
configured as a multiple-hosts port that becomes authorized as soon as one client is authenticated. When
the port is authorized, all other hosts indirectly attached to the port are granted access to the network. If
the port becomes unauthorized (re-authentication fails or an EAPOL-logoff message is received), the
switch denies access to the network to all of the attached clients. In this topology, the wireless access
point is responsible for authenticating the clients attached to it, and the wireless access point acts as a
client to the switch.
Authentication
server
Access point (RADIUS)
Wireless clients
101227
802.1x Readiness Check
The 802.1x readiness check monitors IEEE 802.1x activity on all the switch ports and displays
information about the devices connected to the ports that support IEEE 802.1x. You can use this feature
to determine if the devices connected to the switch ports are IEEE 802.1x-capable. You use an alternate
authentication for the devices that do not support IEEE 802.1x functionality.
This feature only works if the supplicant on the client supports a query with the NOTIFY EAP
notification packet. The client must respond within the IEEE 802.1x timeout value.
For information on configuring the switch for the 802.1x readiness check, see the “Configuring 802.1x
Readiness Check” section on page 8-16.
A voice VLAN port becomes active when there is 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 IEEE 802.1x is enabled on a voice VLAN port, the switch drops packets from
unrecognized IP phones more than one hop away.
When IEEE 802.1x is enabled on a port, you cannot configure a port VLAN that is equal to a voice
VLAN.
For more information about voice VLANs, see the Chapter 14, “Configuring Voice VLAN.”
• 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
IEEE 802.1x-authenticated user.
For examples of tunnel attributes, see the “Configuring the Switch to Use Vendor-Specific RADIUS
Attributes” section on page 7-29.
Note If an EAPOL packet is detected on the wire after the interface has transitioned to the guest VLAN, the
interface reverts to an unauthorized state, and IEEE 802.1x authentication restarts.
Any number of hosts are allowed access when the switch port is moved to the guest VLAN. If an
IEEE 802.1x-capable host 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.
Guest VLANs are supported on 802.1x ports in single host, multiple host, or multi-domain modes.
You can configure any active VLAN except an RSPAN VLAN or a voice VLAN as an IEEE 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.
For more information, see the “Configuring a Guest VLAN” section on page 8-26.
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 indefinitely attempts and fails authentication and the switch port remains
in the spanning-tree blocking state. With this feature, you can configure the switch port to be in the
restricted VLAN after a specified number of authentication attempts (the default value is 3 attempts).
The authenticator counts the failed authentication attempts for the client. When this count exceeds the
configured maximum authentication attempts, the port moves to the restricted VLAN. The failed attempt
count increments when the RADIUS server replies with either an EAP failure or an empty response
without an EAP packet. When the port moves into the restricted VLAN, the failed attempt counter resets.
Users who fail authentication remain in the restricted VLAN until the next re-authentication attempt. A
port in the restricted VLAN tries to re-authenticate at configured intervals (the default is 60 seconds). If
re-authentication fails, the port remains in the restricted VLAN. If re-authentication is successful, the
port moves either to the configured VLAN or to a VLAN sent by the RADIUS server. You can disable
re-authentication. If you do this, the only way to start the authentication process again is for the port to
receive a link down or EAP logoff event. We recommend that you keep re-authentication 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.
After a port moves to the restricted VLAN, it sends a simulated EAP success message to the client
instead of an EAP failure message. This prevents clients from indefinitely attempting authentication.
Some clients (for example, devices running Windows XP) cannot implement DHCP without EAP
success.
Restricted VLANs are supported only on IEEE 802.1x ports in single-host mode and on Layer 2 ports.
You can configure any active VLAN except an RSPAN VLAN, a primary private VLAN, or a voice
VLAN as an IEEE 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.
Other security features such as Dynamic ARP Inspection, DHCP snooping, and IP source guard can be
configured independently on a restricted VLAN.
Note The RADIUS server can send the VLAN information in any combination of VLAN-IDs, VLAN
names, or VLAN groups.
• If the access VLAN is configured on the authenticator switch, it becomes the native VLAN for the
trunk port after successful authentication.
You can enable MDA or multiauth mode on the authenticator switch interface that connects to one more
supplicant switches. Multihost mode is not supported on the authenticator switch interface.
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 8-4.
• 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.)
4
2 3
205718
1 Workstations (clients) 2 Supplicant switch (outside wiring closet)
3 Authenticator switch 4 Access control server (ACS)
5 Trunk port
Guidelines
• 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
• To change the host mode and the apply a standard port configuration on the authenticator switch
port, you can also use AutoSmart ports user-defined macros, instead of the switch VSA. This allows
you to remove unsupported configurations on the authenticator switch port and to change the port
mode from access to trunk. For more information, see Chapter 10, “Configuring Smartports
Macros”.
For more information, see the “Configuring an Authenticator and a Supplicant Switch with NEAT”
section on page 8-30.
Common Session ID
Authentication manager uses a single session ID (referred to as a common session ID) for a client no
matter which authentication method is used. This ID is used for all reporting purposes, such as the show
commands and MIBs. The session ID appears with all per-session syslog messages.
The session ID includes:
• The IP address of the Network Access Device (NAD)
• A monotonically increasing unique 32 bit integer
• The session start time stamp (a 32 bit integer)
This example shows how the session ID appears in the output of the show authentication command. The
session ID in this example is 160000050000000B288508E5:
Switch# show authentication sessions
Interface MAC Address Method Domain Status Session ID
Fa4/0/4 0000.0000.0203 mab DATA Authz Success 160000050000000B288508E5
This is an example of how the session ID appears in the syslog output. The session ID in this example
is also160000050000000B288508E5:
1w0d: %AUTHMGR-5-START: Starting 'mab' for client (0000.0000.0203) on Interface Fa4/0/4
AuditSessionID 160000050000000B288508E5
1w0d: %MAB-5-SUCCESS: Authentication successful for client (0000.0000.0203) on Interface
Fa4/0/4 AuditSessionID 160000050000000B288508E5
1w0d: %AUTHMGR-7-RESULT: Authentication result 'success' from 'mab' for client
(0000.0000.0203) on Interface Fa4/0/4 AuditSessionID 160000050000000B288508E5
The session ID is used by the NAD, the AAA server, and other report-analyzing applications to identify
the client. The ID appears automatically. No configuration is required.
Note In software releases earlier than Cisco IOS Release 12.2(25)EY, if IEEE 802.1x 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 ports—You can
enable IEEE 802.1x on a port that is a SPAN or RSPAN destination port. However, IEEE 802.1x
is disabled until the port is removed as a SPAN or RSPAN destination port. You can enable
IEEE 802.1x on a SPAN or RSPAN source port.
• You can configure any VLAN except an RSPAN VLAN or a voice VLAN as an IEEE 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.
• When IEEE 802.1x is enabled on a port, you cannot configure a port VLAN that is equal to a voice
VLAN.
• The IEEE 802.1x 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 primary private VLAN, or a voice VLAN
as an IEEE 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.
• You can configure IEEE 802.1x on a private-VLAN port, but do not configure IEEE 802.1x with
port security, a voice VLAN, a guest VLAN, a restricted VLAN, or a per-user ACL on
private-VLAN ports.
Beginning in privileged EXEC mode, follow these steps to enable the IEEE 802.1x readiness check on
the switch:
Command Purpose
Step 1 dot1x test eapol-capable [interface Enable the 802.1x readiness check on the switch.
interface-id]
(Optional) For interface-id specify the port on which to check for
IEEE 802.1x readiness.
Note If you omit the optional interface keyword, all interfaces on the
switch are tested.
Step 1 configure terminal (Optional) Enter global configuration mode.
Step 2 dot1x test timeout timeout (Optional) Configure the timeout used to wait for EAPOL response. The
range is from 1 to 65535 seconds. The default is 10 seconds.
Step 3 end (Optional) Return to privileged EXEC mode.
Step 4 show running-config (Optional) Verify your modified timeout values.
This example shows how to enable a readiness check on a switch to query a port. It also shows the
response received from the queried port verifying that the device connected to it is IEEE 802.1x-capable:
switch# dot1x test eapol-capable interface gigabitethernet1/0/13
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 aaa new-model Enable AAA.
Step 3 aaa authentication dot1x {default} Create an IEEE 802.1x authentication method list.
method1 To create a default list that is used when a named list is not specified in
the authentication command, use the default keyword followed by the
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.
Note Though other keywords are visible in the command-line help
string, only the group radius keywords are supported.
Command Purpose
Step 4 interface interface-id Specify the port connected to the client that is to be enabled for
IEEE 802.1x authentication, and enter interface configuration mode.
Step 5 switchport mode access Set the port to access mode.
Step 6 authentication violation{shutdown | Configure the violation mode. The keywords have these meanings:
restrict | protect}
• shutdown–Error disable the port.
• restrict–Generate a syslog error.
• protect–Drop packets from any new device that sends traffic to the
port.
Step 7 end Return to privileged EXEC mode.
Step 8 show authentication Verify your entries.
Step 9 copy running-config startup-config (Optional) Save your entries in the configuration file.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 aaa new-model Enable AAA.
Step 3 aaa authentication dot1x {default} Create an IEEE 802.1x authentication method list.
method1 [method2...]
To create a default list that is used when a named list is not specified in
the authentication command, use the default keyword followed by the
methods that are to be used in default situations. The default method list
is automatically applied to all ports.
Enter at least one of these keywords:
• group radius—Use the list of all RADIUS servers for authentication.
• none—Use no authentication. The client is automatically
authenticated by the switch without using the information supplied by
the client.
Step 4 dot1x system-auth-control Enable IEEE 802.1x authentication globally on the switch.
Command Purpose
Step 5 aaa authorization network {default} (Optional) Configure the switch for user RADIUS authorization for all
group radius network-related service requests, such as per-user ACLs or VLAN
assignment.
Note For per-user ACLs, single-host mode must be configured. This
setting is the default.
Step 6 interface interface-id Specify the port connected to the client that is to be enabled for
IEEE 802.1x authentication, and enter interface configuration mode.
Step 7 dot1x port-control auto Enable IEEE 802.1x authentication on the port.
For feature interaction information, see the “802.1x Configuration
Guidelines” section on page 8-15.
Step 8 dot1x pae authenticator Set the interface Port Access Entity to act only as an authenticator and
ignore messages meant for a supplicant.
Step 9 end Return to privileged EXEC mode.
Step 10 show authentication Verify your entries.
Step 11 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable AAA, use the no aaa new-model global configuration command. To disable 802.1x AAA
authentication, use the no aaa authentication dot1x {default | list-name} global configuration
command. To disable 802.1x AAA authorization, use the no aaa authorization global configuration
command. To disable 802.1x authentication on the switch, use the no dot1x system-auth-control global
configuration command.
This example shows how to enable AAA and 802.1x on a port:
Switch# configure terminal
Switch(config)# aaa new-model
Switch(config)# aaa authentication dot1x default group radius
Switch(config)# dot1x system-auth-control
Switch(config)# interface fastethernet1/0/1
Switch(config)# switchport mode access
Switch(config-if)# authentication port-control auto
Switch(config-if)# end
Beginning in privileged EXEC mode, follow these steps to configure the RADIUS server parameters on
the switch. This procedure is required.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 radius-server host {hostname | Configure the RADIUS server parameters.
ip-address} auth-port port-number key
For hostname | ip-address, specify the hostname or IP address of the
string
remote RADIUS server.
For auth-port port-number, specify the UDP destination port for
authentication requests. The default is 1812. The range is 0 to 65536.
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.
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.
To delete the specified RADIUS server, use the no radius-server host {hostname | ip-address} global
configuration command.
This example shows how to specify the server with IP address 172.20.39.46 as the RADIUS server, to
use port 1612 as the authorization port, and to set the encryption key to rad123, matching the key on the
RADIUS server:
Switch(config)# radius-server host 172.l20.39.46 auth-port 1612 key rad123
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 “Configuring Settings
for All RADIUS Servers” section on page 7-29.
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.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the port to be configured, and enter interface configuration mode.
Step 3 authentication periodic Enable periodic re-authentication of the client, which is disabled by
default.
Note The default value is 3600 seconds. To change the value of the
reauthentication timer or to have the switch use a
RADIUS-provided session timeout, enter the authentication
timer reauthenticate command.
Step 4 authentication timer {{[inactivity | Set the number of seconds between re-authentication attempts.
reauthenticate]} {restart value}}
The authentication timer keywords have these meanings:
• inactivity—Interval in seconds after which if there is no activity from
the client then it is unauthorized
• reauthenticate—Time in seconds after which an automatic
re-authentication attempt is be initiated
• restart value—Interval in seconds after which an attempt is made to
authenticate an unauthorized port
This command affects the behavior of the switch only if periodic
re-authentication is enabled.
Step 5 end Return to privileged EXEC mode.
Step 6 show authentication interface Verify your entries.
interface-id
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the port to be configured, and enter interface configuration mode.
Step 3 authentication timer inactivity seconds Set the number of seconds that the switch remains in the quiet state
following a failed authentication exchange with the client.
The range is 1 to 65535 seconds; the default is 60.
Step 4 end Return to privileged EXEC mode.
Step 5 show authentication interface Verify your entries.
interface-id
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default quiet time, use the no authentication timer inactivity interface configuration
command.
This example shows how to set the quiet time on the switch to 30 seconds:
Switch(config-if)# authentication timer inactivity 30
Note You should change the default value of this command only to adjust for unusual circumstances such as
unreliable links or specific behavioral problems with certain clients and authentication servers.
Beginning in privileged EXEC mode, follow these steps to change the amount of time that the switch
waits for client notification. This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the port to be configured, and enter interface configuration mode.
Step 3 authentication timer reauthenticate Set the number of seconds that the switch waits for a response to an
seconds EAP-request/identity frame from the client before resending the request.
The range is 1 to 65535 seconds; the default is 30.
Step 4 end Return to privileged EXEC mode.
Step 5 show authentication interface Verify your entries.
interface-id
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default retransmission time, use the no authentication timer reauthenticate interface
configuration 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 resending the request:
Switch(config-if)# authentication timer reauthenticate 60
Note You should change the default value of this command only to adjust for unusual circumstances such as
unreliable links or specific behavioral problems with certain clients and authentication servers.
Beginning in privileged EXEC mode, follow these steps to set the switch-to-client frame-retransmission
number. This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the port to be configured, and enter interface configuration mode.
Step 3 dot1x max-reauth-req count Set 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.
Step 4 end Return to privileged EXEC mode.
Step 5 show authentication interface Verify your entries.
interface-id
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default retransmission number, use the no dot1x max-req interface configuration
command.
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:
Switch(config-if)# dot1x max-reauth-req 5
Note You should change the default value of this command only to adjust for unusual circumstances such as
unreliable links or specific behavioral problems with certain clients and authentication servers.
Beginning in privileged EXEC mode, follow these steps to set the re-authentication number. This
procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the port to be configured, and enter interface configuration mode.
Step 3 dot1x max-req count Set the number of times that the switch restarts the authentication process
before the port changes to the unauthorized state. The range is 1 to 10; the
default is 2.
Step 4 end Return to privileged EXEC mode.
Step 5 show authentication interface Verify your entries.
interface-id
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default re-authentication number, use the no dot1x max-reauth-req interface
configuration command.
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:
Switch(config-if)# dot1x max-reauth-req 4
Beginning in privileged EXEC mode, follow these steps to allow multiple hosts (clients) on an
IEEE 802.1x-authorized port that has the authentication port-control interface configuration command
set to auto. This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the port to which multiple hosts are indirectly attached, and enter
interface configuration mode.
Step 3 authentication host-mode [multi-auth | The keywords have these meanings:
multi-domain | multi-host |
• multi-auth–Allow one client on the voice VLAN and multiple
single-host]
authenticated clients on the data VLAN. Each host is individually
authenticated.
Note The multi-auth keyword is only available with the
authentication host-mode command.
Note Although visible in the command-line interface help, the authentication host-mode multi-domain
interface configuration command is not supported. Configuring this command on an interface causes the
interface to go into the error-disabled state.
To disable multiple hosts on the port, use the no authentication host-mode multi-host interface
configuration command.
This example shows how to enable 802.1x on a port and to allow multiple hosts:
Switch(config)# interface fastethernet1/0/1
Switch(config-if)# authentication port-control auto
Switch(config-if)# authentication host-mode multi-host
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the port to be configured, and enter interface configuration mode.
For the supported port types, see the “802.1x Configuration Guidelines”
section on page 8-15.
Step 3 authentication event no-response Specify an active VLAN as an 802.1x guest VLAN. The range is 1 to
action authorize vlan vlan-id 4094.
You can configure any active VLAN except an internal VLANs (routed
port), an RSPAN VLAN, or a voice VLAN as an 802.1x guest VLAN.
Step 4 end Return to privileged EXEC mode.
Step 5 show authentication interface Verify your entries.
interface-id
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable and remove the guest VLAN, use the no authentication event no-response action authorize
vlan vlan-id interface configuration command. If the port is currently authorized in the guest VLAN, the
port returns to the unauthorized state.
This example shows how to enable VLAN 2 as an 802.1x guest VLAN on a port:
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# authentication event no-response action authorize vlan 2
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the port to be configured, and enter interface configuration mode.
For the supported port types, see the “802.1x Configuration Guidelines”
section on page 10-18.
Command Purpose
Step 3 switchport mode access Set the port to access mode,
or or
switchport mode private-vlan host Configure the Layer 2 port as a private-VLAN host port.
Step 4 authentication port-control auto Enable 802.1x authentication on the port.
Step 5 authentication event fail action Specify an active VLAN as an 802.1x restricted VLAN. The range is 1 to
authorize vlan-id 4094.
You can configure any active VLAN except an internal VLAN (routed
port), an RSPAN VLAN, a primary private VLAN, or a voice VLAN as
an 802.1x restricted VLAN.
Step 6 end Return to privileged EXEC mode.
Step 7 show authentication interface (Optional) Verify your entries.
interface-id
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable and remove the restricted VLAN, use the no dot1x auth-fail vlan interface configuration
command. The port returns to the unauthorized state.
This example shows how to enable VLAN 2 as an 802.1x restricted VLAN:
Switch(config)# interface gigabitethernet0/2
Switch(config-if)# authentication event fail action authorize 2
Use the authentication event retry retry count interface configuration command to configure the
maximum number of authentication attempts allowed before a user is assigned to the restricted VLAN.
The range of allowable authentication attempts is 1 to 3. The default is 3 attempts.
Beginning in privileged EXEC mode, follow these steps to configure the maximum number of allowed
authentication attempts. This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the port to be configured, and enter interface configuration mode.
For the supported port types, see the “802.1x Configuration Guidelines”
section on page 10-18.
Step 3 switchport mode access Set the port to access mode,
or or
switchport mode private-vlan host Configure the Layer 2 port as a private-VLAN host port.
Step 4 authentication port-control auto Enable 802.1x authentication on the port.
Step 5 authentication event fail action Specify an active VLAN as an 802.1x restricted VLAN. The range is 1 to
authorize vlan-id 4094.
You can configure any active VLAN except an internal VLAN (routed
port), an RSPAN VLAN, a primary private VLAN, or a voice VLAN as
an 802.1x restricted VLAN.
Step 6 authentication event retry retry count Specify a number of authentication attempts to allow before a port moves
to the restricted VLAN. The range is 1 to 3, and the default is 3.
Command Purpose
Step 7 end Return to privileged EXEC mode.
Step 8 show authentication interface (Optional) Verify your entries.
interface-id
Step 9 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default value, use the no authentication event retry interface configuration command.
This example shows how to set 2 as the number of authentication attempts allowed before the port moves
to the restricted VLAN:
Switch(config-if)# authentication event retry
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the port to be configured, and enter interface configuration mode.
Step 3 dot1x default Reset the configurable 802.1x parameters to the default values.
Step 4 end Return to privileged EXEC mode.
Step 5 show authentication interface Verify your entries.
interface-id
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
When the stop message is not sent successfully, this message appears:
00:09:55: %RADIUS-4-RADIUS_DEAD: RADIUS server 172.20.246.201:1645,1646 is not responding.
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.
Beginning in privileged EXEC mode, follow these steps to configure 802.1x accounting after AAA is
enabled on your switch. This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 aaa accounting dot1x default Enable 802.1x accounting using the list of all RADIUS servers.
start-stop group radius
Step 3 aaa accounting system default (Optional) Enables system accounting (using the list of all RADIUS
start-stop group radius servers) and generates system accounting reload event messages when the
switch reloads.
Step 4 end Return to privileged EXEc mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Saves your entries in the configuration file.
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:
Switch(config)# radius-server host 172.120.39.46 auth-port 1812 acct-port 1813 key rad123
Switch(config)# aaa accounting dot1x default start-stop group radius
Switch(config)# aaa accounting system default start-stop group radius
Command Purpose
Step 1 vlan group vlan-group-name vlan-list vlan-list Configure a VLAN group, and map a single VLAN or a
range of VLANs to it.
Step 2 show vlan group all vlan-group-name Verify the configuration.
Step 3 no vlan group vlan-group-name vlan-list vlan-list Clear the VLAN group configuration or elements of the
VLAN group configuration.
This example shows how to configure the VLAN groups, to map the VLANs to the groups, to and verify
the VLAN group configurations and mapping to the specified VLANs:
switch(config)# vlan group eng-dept vlan-list 10
This example shows how to add a VLAN to an existing VLAN group and to verify that the VLAN was
added:
switch(config)# vlan group eng-dept vlan-list 30
switch(config)# show vlan group eng-dept
Group Name Vlans Mapped
------------- --------------
eng-dept 10,30
This example shows that when all the VLANs are cleared from a VLAN group, the VLAN group is
cleared:
switch(config)# no vlan group eng-dept vlan-list 30
Vlan 30 is successfully cleared from vlan group eng-dept.
Note The cisco-av-pairs must be configured as device-traffic-class=switch on the ACS, which sets the
interface as a trunk after the supplicant is successfully authenticated.
Beginning in privileged EXEC mode, follow these steps to configure a switch as an authenticator:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 cisp enable Enable CISP.
Step 3 interface interface-id Specify the port to be configured, and enter interface configuration
mode.
Step 4 switchport mode access Set the port mode to access.
Command Purpose
Step 5 authentication port-control auto Set the port-authentication mode to auto.
Step 6 dot1x pae authenticator Configure the interface as a port access entity (PAE) authenticator.
Step 7 spanning-tree portfast Enable Port Fast on an access port connected to a single workstation or
server.
Step 8 end Return to privileged EXEC mode.
Step 9 show running-config interface Verify your configuration.
interface-id
Step 10 copy running-config startup-config (Optional) Save your entries in the configuration file.
Beginning in privileged EXEC mode, follow these steps to configure a switch as a supplicant:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 cisp enable Enable CISP.
Step 3 dot1x credentials profile Create 802.1x credentials profile. This must be attached to the port that
is configured as supplicant.
Step 4 username suppswitch Create a username.
Step 5 password password Create a password for the new username.
Step 6 dot1x supplicant force-multicast Force the switch to send only multicast EAPOL packets when it receives
either unicast or multicast packets.
This also allows NEAT to work on the supplicant switch in all host
modes.
Step 7 interface interface-id Specify the port to be configured, and enter interface configuration
mode.
Step 8 switchport trunk encapsulation Set the port to trunk mode.
dot1q
Step 9 switchport mode trunk Configure the interface as a VLAN trunk port.
Step 10 dot1x pae supplicant Configure the interface as a port access entity (PAE) supplicant.
Step 11 dot1x credentials profile-name Attach the 802.1x credentials profile to the interface.
Step 12 end Return to privileged EXEC mode.
Step 13 show running-config interface Verify your configuration.
interface-id
Step 14 copy running-config startup-config (Optional) Save your entries in the configuration file.
Note You must configure a downloadable ACL on the ACS before downloading it to the switch.
After authentication on the port, you can use the show ip access-list privileged EXEC command to
display the downloaded ACLs on the port.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip device tracking Configure the ip device tracking table.
Step 3 aaa new-model Enables AAA.
Step 4 aaa authorization network default group Sets the authorization method to local. To remove the
radius authorization method, use the no aaa authorization network
default group radius command.
Step 5 radius-server vsa send authentication Configure the radius vsa send authentication.
Step 6 interface interface-id Specify the port to be configured, and enter interface
configuration mode.
Step 7 ip access-group acl-id in Configure the default ACL on the port in the input direction.
Note The acl-id is an access list name or number.
Command Purpose
Step 8 show running-config interface interface-id Verify your configuration.
Step 9 copy running-config startup-config (Optional) Save your entries in the configuration file.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 access-list access-list-number deny Defines the default port ACL by using a source address and wildcard.
source source-wildcard log
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 that sends a packet,
such as this:
• 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.
Step 3 interface interface-id Enter interface configuration mode.
Step 4 ip access-group acl-id in Configure the default ACL on the port in the input direction.
Note The acl-id is an access list name or number.
Step 5 exit Returns to global configuration mode.
Step 6 aaa new-model Enables AAA.
Step 7 aaa authorization network default Sets the authorization method to local. To remove the authorization
group radius method, use the no aaa authorization network default group radius
command.
Step 8 ip device tracking Enables the IP device tracking table.
To disable the IP device tracking table, use the no ip device tracking
global configuration commands.
Command Purpose
Step 9 ip device tracking probe [count | (Optional) Configures the IP device tracking table:
interval | use-svi]
• count count—Sets the number of times that the switch sends the ARP
probe. The range is from 1 to 5. The default is 3.
• interval interval—Sets 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.
• use-svi—Uses the switch virtual interface (SVI) IP address as source
of ARP probes.
Step 10 radius-server vsa send authentication Configures the network access server to recognize and use vendor-specific
attributes.
Note The downloadable ACL must be operational.
Step 11 end Returns to privileged EXEC mode.
Step 12 show ip device tracking all Displays information about the entries in the IP device tracking table.
Step 13 copy running-config startup-config (Optional) Saves your entries in the configuration file.
This chapter defines the types of interfaces on the Catalyst 3750 Metro switch and describes how to
configure them.
The chapter has these sections:
• Understanding Interface Types, page 9-1
• Using Interface Configuration Mode, page 9-7
• Configuring Ethernet Interfaces, page 9-11
• Configuring Layer 3 Interfaces, page 9-17
• Configuring the System MTU, page 9-19
• Monitoring and Maintaining the Interfaces, page 9-22
Note For complete syntax and usage information for the commands used in this chapter, see the switch
command reference for this release and the online Cisco IOS Interface Command Reference,
Release 12.2.
Port-Based VLANs
A VLAN is a switched network that is logically segmented by function, team, or application, without
regard to the physical location of the users. For more information about VLANs, see Chapter 11,
“Configuring VLANs.” Packets received on a port are forwarded only to ports that belong to the same
VLAN as the receiving port. Network devices in different VLANs cannot communicate with one another
without a Layer 3 device to route traffic between the VLANs.
VLAN partitions provide hard firewalls for traffic in the VLAN, and each VLAN has its own MAC
address table. A VLAN comes into existence when a local port is configured to be associated with the
VLAN, when the VLAN Trunking Protocol (VTP) learns of its existence from a neighbor on a trunk, or
when a user creates a VLAN.
To configure normal-range VLANs (VLAN IDs 1 to 1005), use the vlan vlan-id global configuration
command to enter config-vlan mode or the vlan database privileged EXEC command to enter VLAN
database configuration mode. The VLAN configurations for VLAN IDs 1 to 1005 are saved in the VLAN
database. To configure extended-range VLANs (VLAN IDs 1006 to 4094), you must use config-vlan
mode with VTP mode set to transparent. Extended-range VLANs are not added to the VLAN database.
When VTP mode is transparent, the VTP and VLAN configuration is saved in the switch running
configuration, and you can save it in the switch startup configuration file by entering the copy
running-config startup-config privileged EXEC command
Add ports to a VLAN by using the switchport interface configuration commands:
• Identify the interface.
• For a trunk port, set trunk characteristics, and if desired, define the VLANs to which it can belong.
• For an access port, set and define the VLAN to which it belongs.
• For a tunnel port, set and define the VLAN ID for the customer-specific VLAN tag. See Chapter 15,
“Configuring IEEE 802.1Q and Layer 2 Protocol Tunneling.”
Switch Ports
Switch ports are Layer 2-only interfaces associated with a physical port. Switch ports belong to one or
more VLANs. A switch port can be an access port, a trunk port, or a tunnel port. You can configure a port
as an access port or trunk port or let the Dynamic Trunking Protocol (DTP) operate on a per-port basis
to determine switchport mode by negotiating with the port on the other end of the link.You must
manually configure tunnel ports as part of an asymmetric link connected to an 802.1Q trunk port. Switch
ports are used for managing the physical interface and associated Layer 2 protocols and do not handle
routing or bridging.
Configure switch ports by using the switchport interface configuration commands. For detailed
information about configuring access port and trunk port characteristics, see Chapter 11, “Configuring
VLANs.” For more information about tunnel ports, see Chapter 15, “Configuring IEEE 802.1Q and
Layer 2 Protocol Tunneling.”
Access Ports
An access port belongs to and carries the traffic of only one VLAN (unless it is configured as a voice
VLAN port). Traffic is received and sent in native formats with no VLAN tagging. Traffic arriving on
an access port is assumed to belong to the VLAN assigned to the port. If an access port receives a tagged
packet (Inter-Switch Link [ISL] or 802.1Q tagged), the packet is dropped, and the source address is not
learned.
Trunk Ports
A trunk port carries the traffic of multiple VLANs and by default is a member of all VLANs in the VLAN
database.
Note Beginning with Cisco IOS Release 12.2(22)EY, on ES trunk ports, only 802.1Q encapsulation is
supported. ES ports do not support ISL encapsulation.
Tunnel Ports
Tunnel ports are used in 802.1Q tunneling to segregate the traffic of customers in a service provider
network from other customers who appear to be on the same VLAN. You configure an asymmetric link
from a tunnel port on a service provider edge switch to an 802.1Q trunk port on the customer switch.
Packets entering the tunnel port on the edge switch, already 802.1Q-tagged with the customer VLANs,
are encapsulated with another layer of 802.1Q tag (called the metro tag) containing a VLAN ID unique
in the service provider network for each customer. The double-tagged packets go through the
service-provider network, keeping the original customer VLANs separate from those of other customers.
At the outbound interface, also a tunnel port, the metro tag is removed, and the original VLAN numbers
from the customer network are retrieved.
Tunnel ports cannot be trunk ports or access ports and must belong to a VLAN unique for each customer.
For more information about tunnel ports, see Chapter 15, “Configuring IEEE 802.1Q and Layer 2
Protocol Tunneling.”
Routed Ports
A routed port is a physical port that acts like a port on a router; it does not have to be connected to a
router. A routed port is not associated with a particular VLAN, as is an access port. A routed port behaves
like a regular router interface, except that it does not support VLAN subinterfaces. Routed ports can be
configured with a Layer 3 routing protocol. A routed port is a Layer 3 interface only and does not support
Layer 2 protocols, such as DTP and STP.
Configure routed ports by putting the interface into Layer 3 mode with the no switchport interface
configuration command. Then assign an IP address to the port, enable routing, and assign routing
protocol characteristics by using the ip routing and router protocol global configuration commands.
Caution Entering a no switchport interface configuration command shuts down the interface and then re-enables
it, which might generate messages on the device to which the interface is connected.
The number of routed ports that you can configure is not limited by software. However, the
interrelationship between this number and the number of other features being configured might impact
CPU performance because of hardware limitations. See the “Configuring Layer 3 Interfaces” section on
page 9-17 for information about what happens when hardware resource limitations are reached.
For more information about IP unicast and multicast routing and routing protocols, see Chapter 36,
“Configuring IP Unicast Routing,” and Chapter 45, “Configuring IP Multicast Routing.”
Although the switch supports a total or 1005 VLANs (and SVIs), the interrelationship between the
number of SVIs and routed ports and the number of other features being configured might impact CPU
performance because of hardware limitations. See the “Configuring Layer 3 Interfaces” section on
page 9-17 for information about what happens when hardware resource limitations are reached.
SVIs are created the first time that you enter the vlan interface configuration command for a VLAN
interface. The VLAN corresponds to the VLAN tag associated with data frames on an ISL or 802.1Q
encapsulated trunk or the VLAN ID configured for an access port. Configure a VLAN interface for each
VLAN for which you want to route traffic, and assign it an IP address. For more information, see the
“Manually Assigning IP Information” section on page 3-14.
Note When you create an SVI, it does not become active until it is associated with a physical port.
SVIs support routing protocols and bridging configurations. For more information about configuring IP
routing, see Chapter 36, “Configuring IP Unicast Routing,” Chapter 45, “Configuring IP Multicast
Routing,” and Chapter 47, “Configuring Fallback Bridging.”
Connecting Interfaces
Devices within a single VLAN can communicate directly through any switch. Ports in different VLANs
cannot exchange data without going through a routing device. With a standard Layer 2 switch, ports in
different VLANs have to exchange information through a router. In the configuration shown in
Figure 9-1, when Host A in VLAN 20 sends data to Host B in VLAN 30, it must go from Host A to the
switch, to the router, back to the switch, and then to Host B.
Cisco router
Switch
Host A Host B
46647
VLAN 20 VLAN 30
By using the switch with routing enabled (as a Layer 3 switch), when you configure VLAN 20 and
VLAN 30 each with an SVI to which an IP address is assigned, packets can be sent from Host A to Host
B directly through the switch with no need for an external router (Figure 9-2).
Layer 3 switch
with routing enabled
Host A Host B
101350
VLAN 20 VLAN 30
The switch supports two methods of forwarding traffic between interfaces: routing and fallback bridging.
Whenever possible, to maintain high performance, forwarding is done by the switch hardware. However,
only IP Version 4 packets with Ethernet II encapsulation can be routed in hardware. Non-IP traffic and
traffic with other encapsulation methods can be fallback-bridged by hardware.
• The routing function can be enabled on all SVIs and routed ports. The switch routes only IP traffic.
When IP routing protocol parameters and address configuration are added to an SVI or routed port,
any IP traffic received from these ports is routed. For more information, see Chapter 36,
“Configuring IP Unicast Routing,” Chapter 45, “Configuring IP Multicast Routing,” and
Chapter 46, “Configuring MSDP.”
• Fallback bridging forwards traffic that the switch does not route or traffic belonging to a nonroutable
protocol, such as DECnet. Fallback bridging connects multiple VLANs into one bridge domain by
bridging between two or more SVIs or routed ports. When configuring fallback bridging, you assign
SVIs or routed ports to bridge groups with each SVI or routed port assigned to only one bridge
group. All interfaces in the same group belong to the same bridge domain. For more information,
see Chapter 47, “Configuring Fallback Bridging.”
Step 1 Enter the configure terminal command at the privileged EXEC prompt:
Switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)#
Step 2 Enter the interface global configuration command. Identify the interface type and number. For physical
interfaces, this includes the switch number (1) and the number of the port to be configured:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)#
Note You do not need to add a space between the physical interface type and the interface number. For
example, in the preceding line, you can specify gigabitethernet 1/0/1, gigabitethernet1/0/1,
gi 1/0/1, or gi1/0/1.
Step 3 Follow each interface command with the interface configuration commands that the interface requires.
The commands that you enter define the protocols and applications that will run on the interface. The
commands are collected and applied to the interface when you enter another interface command or enter
end to return to privileged EXEC mode.
You can also configure a range of interfaces by using the interface range or interface range macro
global configuration commands. Interfaces configured in a range must be the same type and must be
configured with the same feature options.
Step 4 After you configure an interface, verify its status by using the show privileged EXEC commands listed
in the “Monitoring and Maintaining the Interfaces” section on page 9-22.
Enter the show interfaces privileged EXEC command to see a list of all interfaces on or configured for
the switch. A report is provided for each interface that the device supports or for the specified interface.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface range {port-range | macro Enter interface range configuration mode by entering the range of
macro_name} interfaces (VLANs or physical ports) to be configured.
• You can use the interface range command to configure up to five
port ranges or a previously defined macro.
• The macro variable is explained in the “Configuring and Using
Interface Range Macros” section on page 9-10.
• In a comma-separated port-range, you must enter the interface
type for each entry and enter spaces before and after the comma.
• In a hyphen-separated port-range, you do not need to re-enter the
interface type, but you must enter a space before the hyphen.
Step 3 You can now use the normal configuration commands to apply the
configuration parameters to all interfaces in the range.
Step 4 end Return to privileged EXEC mode.
Step 5 show interfaces [interface-id] Verify the configuration of the interfaces in the range.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
When using the interface range global configuration command, note these guidelines:
• Valid entries for port-range:
– vlan vlan-ID - vlan-ID, where VLAN ID is from 1 to 4094
– fastethernet switch/module/{first port} - {last port}, where switch is 1 and module is 0
– gigabitethernet switch/module/{first port} - {last port}, where switch is 1 and module is 0 for
the standard SFP module ports and 1 for the ES SFP module ports
– port-channel port-channel-number - port-channel-number, where port-channel-number is
from 1 to 12
Note When you use the interface range command with port channels, the first and last port
channel number must be active port channels.
• You must add a space between the first interface number and the hyphen when using the
interface range command. For example, the command interface range fastethernet 1/0/1 - 5 is a
valid range; the command interface range fastethernet 1/0/1-5 is not a valid range.
• The interface range command only works with VLAN interfaces that have been configured with
the interface vlan command. The show running-config privileged EXEC command displays the
configured VLAN interfaces. VLAN interfaces not displayed by the show running-config
command cannot be used with the interface range command.
• All interfaces defined as in a range must be the same type (all Fast Ethernet ports, all Gigabit
Ethernet SFP module ports, all EtherChannel ports, or all VLANs), but you can enter multiple
ranges in a command.
This example shows how to use the interface range global configuration command to set the speed on
10/100 ports 1 to 5 to 100 Mb/s:
Switch# configure terminal
Switch(config)# interface range fastethernet1/0/1 - 5
Switch(config-if-range)# speed 100
This example shows how to use a comma to add different interface type strings to the range to enable
Fast Ethernet ports in the range 1 to 3 and Gigabit Ethernet standard SFP module ports 1 and 2 to receive
flow control pause frames:
Switch# configure terminal
Switch(config)# interface range fastethernet1/0/1 - 3, gigabitethernet1/0/1 - 2
Switch(config-if-range)# flowcontrol receive on
If you enter multiple configuration commands while you are in interface range mode, each command is
executed as it is entered. The commands are not batched together and executed after you exit interface
range mode. If you exit interface range configuration mode while the commands are being executed,
some commands might not be executed on all interfaces in the range. Wait until the command prompt
reappears before exiting interface range configuration mode.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 define interface-range macro_name Define the interface-range macro, and save it in NVRAM.
interface-range
• The macro_name is a 32-character maximum character string.
• A macro can contain up to five comma-separated interface ranges.
• Each interface-range must consist of the same port type.
Step 3 interface range macro macro_name Select the interface range to be configured using the values saved in
the interface-range macro called macro_name.
You can now use the normal configuration commands to apply the
configuration to all interfaces in the defined macro.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config | include define Show the defined interface range macro configuration.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no define interface-range macro_name global configuration command to delete a macro.
When using the define interface-range global configuration command, note these guidelines:
• Valid entries for interface-range:
– vlan vlan-ID - vlan-ID, where VLAN ID is from 1 to 4094
– fastethernet switch/module/{first port} - {last port}, where switch is 1 and module is 0
– gigabitethernet switch/module/{first port} - {last port}, where switch is 1 and module is 0 for
the standard SFP module ports and 1 for the ES SFP module ports.
– port-channel port-channel-number - port-channel-number, where port-channel-number is
from 1 to 12.
Note When you use the interface ranges with port channels, the first and last port channel number
must be active port channels.
• You must add a space between the first interface number and the hyphen when entering an
interface-range. For example, fastethernet 1/0/1 - 5 is a valid range; fastethernet 1/0/1-5 is not a
valid range.
• The VLAN interfaces must have been configured with the interface vlan command. The show
running-config privileged EXEC command displays the configured VLAN interfaces. VLAN
interfaces not displayed by the show running-config command cannot be used as interface-ranges.
• All interfaces defined as in a range must be the same type (all Fast Ethernet ports, all Gigabit
Ethernet SFP module ports, all EtherChannel ports, or all VLANs), but you can combine multiple
interface types in a macro.
This example shows how to define an interface-range macro named enet_list to select Fast Ethernet ports
1 to 4 and to verify the macro configuration:
Switch# configure terminal
Switch(config)# define interface-range enet_list fastethernet1/0/1 - 4
Switch(config)# end
Switch# show running-config | include define
define interface-range enet_list FastEthernet1/0/1 - 4
This example shows how to enter interface range configuration mode for the interface-range macro
enet_list:
Switch# configure terminal
Switch(config)# interface range macro enet_list
Switch(config-if-range)#
This example shows how to delete the interface-range macro enet_list and to verify that it was deleted.
Switch# configure terminal
Switch(config)# no define interface-range enet_list
Switch(config)# end
Switch# show run | include define
Switch#
Note To configure Layer 2 parameters, if the interface is in Layer 3 mode, you must enter the switchport
interface configuration command without any parameters to put the interface into Layer 2 mode. This
shuts down the interface and then re-enables it, which might generate messages on the device to which
the interface is connected. Furthermore, when you use this command to put the interface into Layer 2
mode, you are deleting any Layer 3 characteristics configured on the interface.
Caution The ES ports do not support 10 or 100 Mb/s operation. Setting the speed on an ES port to 10 or 100 Mb/s,
or to auto if the interface is connected to a 10/100 interface on another switch, can result in severe data
loss if the interface is connected to a 10/100 interface on another switch.
• When STP is enabled and a port is reconfigured, the switch can take up to 30 seconds to check for
loops. The port LED is amber while STP reconfigures.
Caution Changing the interface speed and duplex mode configuration might shut down and re-enable the
interface during the reconfiguration.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode and the physical interface
identification.
Command Purpose
Step 3 speed {10 | 100 | 1000 | auto [10 | 100 | Enter the appropriate speed parameter for the port:
1000] | nonegotiate}
• Enter 10, 100, or 1000 to set a specific speed for the port. The
1000 keyword is not available on 10/100 Mb/s ports.
• Enter auto to enable the interface to autonegotiate speed with the
device connected to the interface. If you use the 10, 100, or 1000
keywords with the auto keyword, the port only autonegotiates at
the specified speeds.
• The nonegotiate keyword is available only for SFP module ports.
SFP module ports operate only at 1000 Mb/s but can be
configured to not negotiate if connected to a device that does not
support autonegotiation.
For information about speed settings, see the “Speed and Duplex
Configuration Guidelines” section on page 9-13.
Step 4 duplex {auto | full | half} Enter the duplex parameter for the interface.
Beginning with Cisco IOS Release 12.2(25)EXA, you can configure
the duplex setting when the speed is set to auto.
For information about duplex settings, see the “Speed and Duplex
Configuration Guidelines” section on page 9-13.
Step 5 end Return to privileged EXEC mode.
Step 6 show interfaces interface-id Display the interface speed and duplex mode configuration.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no speed and no duplex interface configuration commands to return the interface to the default
speed and duplex settings (autonegotiate). To return all interface settings to the defaults, use the default
interface interface-id interface configuration command.
This example shows how to set the speed to 10 Mb/s and the duplex mode to half on an port:
Switch# configure terminal
Switch(config)# interface fasttethernet1/0/3
Switch(config-if)# speed 10
Switch(config-if)# duplex half
Note Catalyst 3750 Metro switch ports receive, but do not send pause frames.
You use the flowcontrol interface configuration command to set the interface’s ability to receive pause
frames to on, off, or desired. The default state is off.
When set to desired, an interface can operate with an attached device that is required to send
flow-control packets or with an attached device that is not required to but can send flow-control packets.
These rules apply to flow control settings on the device:
• receive on (or desired): The port cannot send pause frames but can operate with an attached device
that is required to or can send pause frames; the port can receive pause frames.
• receive off: Flow control does not operate in either direction. In case of congestion, no indication is
given to the link partner, and no pause frames are sent or received by either device.
Note For details on the command settings and the resulting flow control resolution on local and remote ports,
see the flowcontrol interface configuration command in the command reference for this release.
Beginning in privileged EXEC mode, follow these steps to configure flow control on an interface:
Command Purpose
Step 1 configure terminal Enter global configuration mode
Step 2 interface interface-id Enter interface configuration mode and the physical interface to
be configured.
Step 3 flowcontrol {receive} {on | off | desired} Configure the flow control mode for the port.
Step 4 end Return to privileged EXEC mode.
Step 5 show interfaces interface-id Verify the interface flow control settings.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable flow control, use the flowcontrol receive off interface configuration command.
This example shows how to turn on flow control on a port:
Switch# configure terminal
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# flowcontrol receive on
Switch(config-if)# end
Caution ES ports do not support 10 or 100 Mb/s operation. When a 1000BASE-T SFP module is inserted in an
ES module port, if you set the speed to auto to enable Auto-MDIX, be sure that the interface is connected
to a Gigabit interface. Setting the speed to auto can result in severe data loss if the interface is connected
to a 10/100 interface on another switch.
Table 9-2 shows the link states that results from Auto-MDIX settings and correct and incorrect cabling.
Local Side Auto-MDIX Remote Side Auto-MDIX With Correct Cabling With Incorrect Cabling
On On Link up Link up
On Off Link up Link up
Off On Link up Link up
Off Off Link up Link down
Beginning in privileged EXEC mode, follow these steps to configure Auto-MDIX on a port:
Command Purpose
Step 1 configure terminal Enter global configuration mode
Step 2 interface interface-id Enter interface configuration mode for the physical interface to be
configured.
Step 3 speed auto Configure the port to autonegotiate speed with the connected device.
Step 4 duplex auto Configure the port to autonegotiate duplex mode with the connected device.
Step 5 mdix auto Enable Auto-MDIX on the port.
Note On an ES port, setting the speed to auto can result in severe data
loss if the port is connected to a 10/100 interface on another switch.
Step 6 end Return to privileged EXEC mode.
Step 7 show controllers ethernet-controller Verify the operational state of the Auto-MDIX feature on the interface.
interface-id phy
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and enter the interface for which
you are adding a description.
Step 3 description string Add a description (up to 240 characters) for an interface.
Step 4 end Return to privileged EXEC mode.
Step 5 show interfaces interface-id description Verify your entry.
or
show running-config
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
Note When you create an SVI, it does not become active until it is associated with a physical port.
For information about assigning Layer 2 ports to VLANs, see Chapter 11, “Configuring
VLANs.”
• Routed ports: Routed ports are physical ports configured to be in Layer 3 mode by using the no
switchport interface configuration command.
Note If the physical port is in Layer 2 mode (the default), you must enter the no switchport interface
configuration command to put the interface into Layer 3 mode. Entering a no switchport command
disables and then re-enables the interface, which might generate messages on the device to which the
interface is connected.
Beginning in privileged EXEC mode, follow these steps to configure a Layer 3 interface:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface {{fastethernet | gigabitethernet} interface-id} Enter interface configuration mode, and enter the
| {vlan vlan-id} | {port-channel port-channel-number} interface to be configured as a Layer 3 interface.
Step 3 no switchport For physical ports only, enter Layer 3 mode.
Step 4 ip address ip_address subnet_mask Configure the IP address and IP subnet.
Step 5 no shutdown Enable the interface.
Step 6 end Return to privileged EXEC mode.
Step 7 show interfaces [interface-id] Verify the configuration.
show ip interface [interface-id]
show running-config interface [interface-id]
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove an IP address from an interface, use the no ip address interface configuration command.
This example shows how to configure a port as a routed port and to assign it an IP address:
Switch# configure terminal
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# no switchport
Switch(config-if)# ip address 192.20.135.21 255.255.255.0
Switch(config-if)# no shutdown
Note You cannot configure a routing MTU size that exceeds the system MTU size. If you change the system
MTU size to a value smaller than the currently configured routing MTU size, the configuration change
is accepted, but not applied until the next switch reset. When the configuration change takes effect, the
routing MTU size automatically defaults to the new system MTU size.
Gigabit Ethernet ports MTU size is configured by the system mtu jumbo command. Fast Ethernet ports
are not affected by this command because jumbo frames are not supported on 10/100 interfaces,
including 100BASE-FX and 100BASE-BX SFP modules. If you do not configure the system mtu jumbo
command, the setting of the system mtu command applies to all Gigabit Ethernet interfaces.
On an enhanced-services (ES) port you can use the mpls mtu interface configuration command to set
the MTU size for multiprotocol label switching (MPLS) labeled packets. You can increase the size of
MPLS labeled packets up to the size configured for jumbo packets. Because labeling a packet makes it
larger, we recommend setting the system MTU and the MPLS MTU to the same value, to prevent
dropping of labeled packets.
The switch supports a maxiumum MTU size for 10/100 interfaces of 1998 bytes. The maxiumum MTU
size for Gigabit interfaces is 9000 bytes.
You cannot set the MTU size for an individual interface; you set it for all Fast Ethernet or all Gigabit
Ethernet interfaces on the switch. When you change the MTU size, you must reset the switch before the
new configuration takes effect.The system mtu routing command does not require a switch reset to take
effect.
To define an alternate MTU size, enter the system mtu alternate bytes global configuration command.
You then apply the alternate size to specified interfaces by using the system mtu alternate interface
interface-id global configuration command. The range of the alternate MTU is between the configured
system mtu and system jumbo mtu sizes (1500 to 9000 bytes). When you apply an alternate MTU size
to an interface, frames received on the interface that are greater than the configured size are dropped.
You can configure an alternate MTU size for Fast Ethernet or Gigabit Ethernet interfaces, but you cannot
apply an alternate MTU size greater than 1998 bytes on a Fast Ethernet interface. The alternate MTU
size has no effect on the routing MTU size.
When an alternate MTU size is applied to ES ports, packets are treated as expected (forwarded or
dropped), but large packets are not tagged as giant frames. Accounting is not supported on ES ports.
When you configure an alternate MTU size, you must reload the switch before the configuration takes
effect.
Note The system MTU setting is saved in the switch environmental variable in NVRAM and becomes
effective when the switch reloads. Unlike the system MTU routing configuration, the MTU settings you
enter with the system mtu and system mtu jumbo commands are not saved in the switch configuration
file, even if you enter the copy running-config startup-config privileged EXEC command. Therefore,
if you use TFTP to configure a new switch by using a backup configuration file and want the system
MTU to be other than the default, you must explicitly configure the system mtu and system mtu jumbo
settings on the new switch and then reload the switch.
The size of frames that can be received by the switch CPU is limited to 1998 bytes, no matter what value
was entered with the system mtu or system mtu jumbo commands. Although frames that are forwarded
or routed typically are not received by the CPU, in some cases packets are sent to the CPU, such as traffic
sent to control traffic, SNMP, or Telnet, or routing protocols.
Routed packets are subjected to MTU checks on the egress ports. The MTU value used for routed ports
is derived from the system mtu configured value (not the system mtu jumbo value). That is, the routed
MTU is never greater than the system MTU for any VLAN. The system MTU value is used by routing
protocols when negotiating adjacencies and the MTU of the link. For example Open Shortest Path First
(OSPF) protocol uses this MTU value before setting up an adjacency with a peer router. To view the
MTU value for routed packets for a specific VLAN, use the show platform port-asic mvid privileged
EXEC command.
Routed packets are subjected to MTU checks on the egress ports. The MTU value used for routed ports
is derived from the system mtu configured value (not the system mtu jumbo value). That is, the routed
MTU is never greater than the system MTU for any VLAN. The system MTU value is used by routing
protocols when negotiating adjacencies and the MTU of the link. For example Open Shortest Path First
(OSPF) protocol uses this MTU value before setting up an adjacency with a peer router. To view the
MTU value for routed packets for a specific VLAN, use the show platform port-asic mvid privileged
EXEC command.
Note If Layer 2 Gigabit Ethernet interfaces are configured to accept frames greater than the 10/100 interfaces,
jumbo frames ingressing on a Layer 2 Gigabit Ethernet interface and egressing on a Layer 2 10/100
interface are dropped.
Beginning in privileged EXEC mode, follow these steps to change the MTU size for all 10/100 or Gigabit
Ethernet interfaces and to set an alternate MTU size for specified interfaces:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 system mtu bytes (Optional) Change the MTU size for all interfaces on
the switch that are operating at 10 or 100 Mb/s. The
range is 1500 to 1998 bytes. The default is 1500 bytes.
Step 3 system mtu jumbo bytes (Optional) Change the MTU size for all Gigabit
Ethernet interfaces on the switch. The range is 1500 to
9000 bytes. The default is 1500 bytes.
Command Purpose
Step 4 system mtu alternate bytes (Optional) Set an alternate MTU size. The range is
between the configured system MTU size and the
configured jumbo MTU size (1500 to 9000 bytes). The
default is 1500 bytes.
Step 5 system mtu alternate interface {interface-id | range (Optional) Apply the alternate MTU size to the
interface-range} specified interface or range of interfaces.
Step 6 system mtu routing bytes (Optional) Change the system MTU for routed ports.
The range is 1500 to the system MTU value. This is the
maximum MTU that can be routed for all ports.
Although larger packets can be accepted, they cannot be
routed.
Step 7 end Return to privileged EXEC mode.
Step 8 reload Reload the operating system.
If you enter a value that is outside the allowed range for the specific type of interface, the value is not
accepted.
Once the switch reloads, you can verify your settings by entering the show system mtu privileged EXEC
command. To verify the MTU setting on an interface, enter the show interface interface-id mtu.
This example shows how to set the maximum packet size for Gigabit Ethernet interfaces to 1800 bytes:
Switch(config)# system mtu jumbo 1800
Switch(config)# exit
Switch# reload
This example shows the response when you try to set Gigabit Ethernet interfaces to an out-of-range
number:
Switch(config)# system mtu jumbo 10000
^
% Invalid input detected at '^' marker.
This example shows how to set the maximum packet size for Gigabit Ethernet ports to 1800 bytes, to
define an alternate MTU size of 1700 bytes and apply it to Gigabit Ethernet port 0/8. Changes are not
applied until you reload the switch:
Switch(config)# system mtu jumbo 1800
Switch(config)# system mtu alternate 1700
Changes to the Alternate MTU will not take effect until the next reload is done
Switch(config)# system mtu alternate interface gigabitethernet 1/0/8
Changes to the Alternate MTU on interface will not take effect until the next reload is
done
Switch(config)# exit
Switch# reload
This example shows how to apply the alternate MTU to Gigabit Ethernet interfaces 1 to 10. Changes are
not applied until you reload the switch:
Switch(config)# system mtu alternate interface range gigabitethernet 1/0/1-10
Changes to the Alternate MTU on interface(s) will not take effect until the next reload is done
Switch(config)# exit
Command Purpose
show interfaces [interface-id] Display the status and configuration of all interfaces or a specific
interface.
show interfaces interface-id status [err-disabled] Display interface status or a list of interfaces in an error-disabled state.
show interfaces [interface-id] mtu Display the MTU setting on an interface.
show interfaces [interface-id] switchport Display administrative and operational status of switching
(nonrouting) ports. You can use this command to determine if a port is
in routing or switching mode.
show interfaces [interface-id] description Display the description configured on an interface or all interfaces and
the interface status.
show interfaces [interface-id] transceiver [detail | Display these physical and operational status about an SFP module:
dom-supported-list | module number | properties |
• interface-id–(Optional) Display configuration and status for a
threshold-table] [ | {begin | exclude | include}
specified physical interface.
expression]
• detail–(Optional) Display calibration properties, including high
and low numbers and any alarm information for any Digital
Optical Monitoring (DoM)-capable transceiver if one is installed
in the switch.
• dom-supported-list–(Optional) List all supported DoM
transceivers.
• module number–(Optional) Limit display to interfaces on module
on the switch. The range is 1 to 9. This option is not available if
you entered a specific interface ID.
• properties–(Optional) Display speed, duplex, and inline power
settings on an interface
• threshold-table–(Optional) Display alarm and warning threshold
table
show ip interface [interface-id] Display the usability status of all interfaces configured for IP routing
or the specified interface.
show running-config interface [interface-id] Display the running configuration in RAM for the interface.
Command Purpose
show version Display the hardware configuration, software version, the names and
sources of configuration files, and the boot images.
show controllers ethernet-controller interface-id Verify the operational state of the Auto-MDIX feature on the interface.
phy
Command Purpose
clear counters [interface-id] Clear interface counters.
clear interface interface-id Reset the hardware logic on an interface.
clear line [number | console 0 | vty number] Reset the hardware logic on an asynchronous serial line.
To clear the interface counters shown by the show interfaces privileged EXEC command, use the clear
counters privileged EXEC command. The clear counters command clears all current interface counters
from the interface unless optional arguments are specified to clear only a specific interface type from a
specific interface number.
Note The clear counters privileged EXEC command does not clear counters retrieved by using Simple
Network Management Protocol (SNMP), but only those seen with the show interface privileged EXEC
command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface {vlan vlan-id} | {{fastethernet | gigabitethernet} Select the interface to be configured.
interface-id} | {port-channel port-channel-number}
Step 3 shutdown Shut down an interface.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entry.
This chapter describes how to configure and apply Smartports macros on the Catalyst 3750 Metro
switch.
Note For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
• 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, all 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.
• 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.
There are Cisco-default Smartports macros embedded in the switch software (see Table 10-1). You can
display these macros and the commands they contain by using the show parser macro user EXEC
command.
Follow these guidelines when you apply a Cisco-default Smartports macro on an interface:
• Display all 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 macro-name user EXEC
command.
• Keywords that begin with $ mean that a unique parameter value is required. Append the
Cisco-default macro with the required values by using the parameter value keywords.
The Cisco-default macros use the $ character to help identify required keywords. There is no
restriction on using the $ character to define keywords when you create a macro.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 macro name macro-name Create a macro definition, and enter a macro name. A macro definition
can contain up to 3000 characters.
Enter the macro commands with one command per line. Use the @
character to end the macro. Use the # character at the beginning of a line
to enter comment text within the macro.
(Optional) You can define keywords within a macro by using a help
string to specify the keywords. Enter # macro keywords word to define
the keywords that are available for use with the macro. Separated by a
space, you can enter up to three help string keywords in 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.
We recommend that you do not use the exit or end commands or change
the command mode by using 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.
Step 3 end Return to privileged EXEC mode.
Step 4 show parser macro name macro-name Verify that the macro was created.
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 switchport access VLAN and the number of
secure MAC addresses and also includes two help string keywords by using # macro keywords:
Switch(config)# macro name test
switchport access vlan $VLANID
switchport port-security maximum $MAX
#macro keywords $VLANID $MAX
@
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 macro global {apply | trace} Apply each individual command defined in the macro to the switch by
macro-name [parameter {value}] entering macro global apply macro-name. Specify macro global trace
[parameter {value}] [parameter macro-name to apply and debug a macro to find any syntax or
{value}] configuration errors.
(Optional) Specify unique parameter values that are specific to the
switch. You can enter up to three keyword-value pairs. Parameter
keyword matching is case sensitive. All matching occurrences of the
keyword are replaced with the corresponding value.
Some macros might contain keywords that require a parameter value.
You can use the macro global apply macro-name ? 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.
Step 3 macro global description text (Optional) Enter a description about the macro that is applied to the
switch.
Step 4 interface interface-id (Optional) Enter interface configuration mode, and specify the interface
on which to apply the macro.
Step 5 default interface interface-id (Optional) Clear all configuration from the specified interface.
Step 6 macro {apply | trace} macro-name Apply each individual command defined in the macro to the interface by
[parameter {value}] [parameter entering macro apply macro-name. Specify macro trace macro-name
{value}] [parameter {value}] to apply and debug a macro to find any syntax or configuration errors.
(Optional) Specify unique parameter values that are specific to the
interface. You can enter up to three keyword-value pairs. Parameter
keyword matching is case sensitive. All matching occurrences of the
keyword are replaced with the corresponding value.
Some macros might contain keywords that require a parameter value.
You can use the macro apply macro-name ? 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.
Step 7 macro description text (Optional) Enter a description about the macro that is applied to the
interface.
Step 8 end Return to privileged EXEC mode.
Step 9 show parser macro description [interface Verify that the macro is applied to the interface.
interface-id]
Step 10 copy running-config startup-config (Optional) Save your entries in the configuration file.
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 a macro-applied configuration 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 hostname address to
test-server, and to set the IP precedence value to 7:
Switch(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.
Switch(config)# macro global trace snmp VALUE 7
Applying command...‘snmp-server enable traps port-security’
Applying command...‘snmp-server enable traps linkup’
Applying command...‘snmp-server enable traps linkdown’
Applying command...‘snmp-server host’
%Error Unknown error.
Applying command...‘snmp-server ip precedence 7’
This example shows how to apply the user-created macro called desktop-config and to verify the
configuration.
Switch(config)# interface fastethernet1/0/2
Switch(config-if)# macro apply desktop-config
Switch(config-if)# end
Switch# show parser macro description
Interface Macro Description
--------------------------------------------------------------
Fa1/0/2 desktop-config
--------------------------------------------------------------
This example shows how to apply the user-created macro called desktop-config and to replace all
occurrences of VLAN 1 with VLAN 25:
Switch(config-if)# macro apply desktop-config vlan 25
Command Purpose
Step 1 show parser macro Display the Cisco-default Smartports macros embedded in the switch
software.
Step 2 show parser macro macro-name Display the specific macro that you want to apply.
Step 3 configure terminal Enter global configuration mode.
Step 4 macro global {apply | trace} Append the Cisco-default macro with the required values by using the
macro-name [parameter {value}] parameter value keywords and apply the macro to the switch.
[parameter {value}] [parameter Keywords that begin with $ mean that a unique parameter value is
{value}] required.
You can use the macro global apply macro-name ? 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.
Step 5 interface interface-id (Optional) Enter interface configuration mode, and specify the interface
on which to apply the macro.
Step 6 default interface interface-id (Optional) Clear all configuration from the specified interface.
Command Purpose
Step 7 macro {apply | trace} macro-name Append the Cisco-default macro with the required values by using the
[parameter {value}] [parameter parameter value keywords, and apply the macro to the interface.
{value}] [parameter {value}] Keywords that begin with $ mean that a unique parameter value is
required.
You can use the macro apply macro-name ? 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.
Step 8 end Return to privileged EXEC mode.
Step 9 show running-config interface Verify that the macro is applied to an interface.
interface-id
Step 10 copy running-config startup-config (Optional) Save your entries in the configuration file.
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 a macro-applied configuration on an interface by entering
the default interface interface-id interface configuration command.
This example shows how to display the cisco-desktop macro, how to apply the macro, and to set the
access VLAN ID to 25 on an interface:
Switch# show parser macro cisco-desktop
--------------------------------------------------------------
Macro name : cisco-desktop
Macro type : default
Command Purpose
show parser macro Displays all configured macros.
show parser macro name macro-name Displays a specific macro.
show parser macro brief Displays the configured macro names.
show parser macro description [interface Displays the macro description for all interfaces or for a specified
interface-id] interface.
This chapter describes how to configure normal-range VLANs (VLAN IDs 1 to 1005) and
extended-range VLANs (VLAN IDs 1006 to 4094) on the Catalyst 3750 Metro switch. It includes
information about VLAN membership modes, VLAN configuration modes, VLAN trunks, and dynamic
VLAN assignment from a VLAN Membership Policy Server (VMPS).
Note For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
Understanding VLANs
A VLAN is a switched network that is logically segmented by function, project team, or application,
without regard to the physical locations of the users. VLANs have the same attributes as physical LANs,
but you can group end stations even if they are not physically located on the same LAN segment. Any
switch port can belong to a VLAN, and unicast, broadcast, and multicast packets are forwarded and
flooded only to end stations in the VLAN. Each VLAN is considered a logical network, and packets
destined for stations that do not belong to the VLAN must be forwarded through a router or a switch
supporting fallback bridging, as shown in Figure 11-1. Because a VLAN is considered a separate logical
network, it contains its own bridge MIB information and can support its own implementation of spanning
tree. See Chapter 16, “Configuring STP.”
Note Before you create VLANs, you must decide whether to use VLAN Trunking Protocol (VTP) to maintain
global VLAN configuration for your network. For more information on VTP, see Chapter 12,
“Configuring VTP.”
Figure 11-1 shows an example of VLANs segmented into logically defined networks.
Cisco router
Floor 3
Gigabit
Ethernet
Floor 2
Floor 1
90571
VLANs are often associated with IP subnetworks. For example, all the end stations in a particular IP
subnet belong to the same VLAN. Interface VLAN membership on the switch is assigned manually on
an interface-by-interface basis. When you assign switch interfaces to VLANs by using this method, it is
known as interface-based, or static, VLAN membership.
Traffic between VLANs must be routed or fallback bridged. The switch can route traffic between
VLANs by using switch virtual interfaces (SVIs). An SVI must be explicitly configured and assigned an
IP address to route traffic between VLANs. For more information, see the “Switch Virtual Interfaces”
section on page 9-4 and the “Configuring Layer 3 Interfaces” section on page 9-17.
Note If you plan to configure many VLANs on the switch and to not enable routing, you can use the sdm
prefer vlan global configuration command to set the Switch Database Management (SDM) feature to
the VLAN template, which configures system resources to support the maximum number of unicast
MAC addresses. For more information on the SDM templates, see Chapter 6, “Configuring SDM
Templates,” or see the sdm prefer command in the command reference for this release.
Supported VLANs
The switch supports 1005 VLANs in VTP client, server, and transparent modes. VLANs are identified
with a number from 1 to 4094. VLAN IDs 1002 through 1005 are reserved for Token Ring and FDDI
VLANs. VTP only learns normal-range VLANs, with VLAN IDs 1 to 1005; VLAN IDs greater than
1005 are extended-range VLANs and are not stored in the VLAN database. The switch must be in VTP
transparent mode when you create VLAN IDs from 1006 to 4094.
Although the switch supports a total of 1005 (normal-range and extended-range) VLANs, the number of
routed ports, SVIs, and other configured features affects the use of the switch hardware.
The switch supports per-VLAN spanning-tree plus (PVST+) or rapid PVST+ with a maximum of 128
spanning-tree instances. One spanning-tree instance is allowed per VLAN. See the “Normal-Range
VLAN Configuration Guidelines” section on page 11-6 for more information about the number of
spanning-tree instances and the number of VLANs. The switch supports both Inter-Switch Link (ISL)
and IEEE 802.1Q trunking methods for sending VLAN traffic over Ethernet ports.
For more detailed definitions of the modes and their functions, see Table 11-4 on page 11-16.
When a port belongs to a VLAN, the switch learns and manages the addresses associated with the port
on a per-VLAN basis. For more information, see the “Managing the MAC Address Table” section on
page 5-12.
Note When the switch is in VTP transparent mode, you can also create extended-range VLANs (VLANs with
IDs from 1006 to 4094), but these VLANs are not saved in the VLAN database. See the “Configuring
Extended-Range VLANs” section on page 11-11.
Configurations for VLAN IDs 1 to 1005 are written to the file vlan.dat (VLAN database), and you can
display them by entering the show vlan privileged EXEC command. The vlan.dat file is stored in
NVRAM.
Caution You can cause inconsistency in the VLAN database if you attempt to manually delete the vlan.dat file.
If you want to modify the VLAN configuration, use the commands described in these sections and in the
command reference for this release. To change the VTP configuration, see Chapter 12, “Configuring
VTP.”
You use the interface configuration mode to define the port membership mode and to add and remove
ports from VLANs. The results of these commands are written to the running-configuration file, and you
can display the file by entering the show running-config privileged EXEC command.
You can set these parameters when you create a new normal-range VLAN or modify an existing VLAN
in the VLAN database:
• VLAN ID
• VLAN name
• VLAN type (Ethernet, Fiber Distributed Data Interface [FDDI], FDDI network entity title [NET],
TrBRF, or TrCRF, Token Ring, Token Ring-Net)
• VLAN state (active or suspended)
• Maximum transmission unit (MTU) for the VLAN
• 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
• VLAN number to use when translating from one VLAN type to another
Note This section does not provide configuration details for most of these parameters. For complete
information on the commands and parameters that control VLAN configuration, see the command
reference for this release.
This section includes information about these topics about normal-range VLANs:
• Token Ring VLANs, page 11-6
• Normal-Range VLAN Configuration Guidelines, page 11-6
• Saving VLAN Configuration, page 11-7
• Default Ethernet VLAN Configuration, page 11-7
• Creating or Modifying an Ethernet VLAN, page 11-8
• Deleting a VLAN, page 11-9
• Assigning Static-Access Ports to a VLAN, page 11-10
configuration command description in the command reference for this release. When you have
finished the configuration, you must exit VLAN configuration mode for the configuration to take
effect. To display the VLAN configuration, enter the show vlan privileged EXEC command.
Caution If the VLAN database configuration is used at startup and the startup configuration file contains
extended-range VLAN configuration, this information is lost when the system boots up.
Note The switch supports Ethernet interfaces exclusively. Because FDDI and Token Ring VLANs are not
locally supported, you only configure FDDI and Token Ring media-specific characteristics for VTP
global advertisements to other switches.
Note When the switch is in VTP transparent mode, you can assign VLAN IDs greater than 1006, but they are
not added to the VLAN database. See the “Configuring Extended-Range VLANs” section on
page 11-11.
For the list of default parameters that are assigned when you add a VLAN, see the “Configuring
Normal-Range VLANs” section on page 11-4.
Beginning in privileged EXEC mode, follow these steps to create or modify an Ethernet VLAN:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 vlan vlan-id Enter a VLAN ID, and enter VLAN configuration mode. Enter a new
VLAN ID to create a VLAN, or enter an existing VLAN ID to modify a
VLAN.
Note The available VLAN ID range for this command is 1 to 4094.
For information about adding VLAN IDs greater than 1005
(extended-range VLANs), see the “Configuring
Extended-Range VLANs” section on page 11-11.
Command Purpose
Step 3 name vlan-name (Optional) Enter a name for the VLAN. If no name is entered for the
VLAN, the default is to append the vlan-id with leading zeros to the
word VLAN. For example, VLAN0004 is a default VLAN name for
VLAN 4.
Step 4 mtu mtu-size (Optional) Change the MTU size (or other VLAN characteristic).
Step 5 remote-span (Optional) Configure the VLAN as the RSPAN VLAN for a remote
SPAN session. For more information on remote SPAN, see Chapter 28,
“Configuring SPAN and RSPAN.”
Step 6 end Return to privileged EXEC mode.
Step 7 show vlan {name vlan-name | id vlan-id} Verify your entries.
Step 8 copy running-config startup config (Optional) If the switch is in VTP transparent mode, the VLAN
configuration is saved in the running configuration file as well as in the
VLAN database. This saves the configuration in the switch startup
configuration file.
To return the VLAN name to the default settings, use the no name, no mtu, or no remote-span VLAN
configuration commands.
This example shows how to create Ethernet VLAN 20, name it test20, and add it to the VLAN database:
Switch# configure terminal
Switch(config)# vlan 20
Switch(config-vlan)# name test20
Switch(config-vlan)# end
Deleting a VLAN
When you delete a VLAN from a switch that is in VTP server mode, the VLAN is removed from the
VLAN database for all switches in the VTP domain. When you delete a VLAN from a switch that is in
VTP transparent mode, the VLAN is deleted only on that specific switch.
You cannot delete the default VLANs for the different media types: Ethernet VLAN 1 and FDDI or
Token Ring VLANs 1002 to 1005.
Caution When you delete a VLAN, any ports assigned to that VLAN become inactive. They remain associated
with the VLAN (and thus inactive) until you assign them to a new VLAN.
Beginning in privileged EXEC mode, follow these steps to delete a VLAN on the switch by using global
configuration mode:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 no vlan vlan-id Remove the VLAN by entering the VLAN ID.
Step 3 end Return to privileged EXEC mode.
Command Purpose
Step 4 show vlan brief Verify the VLAN removal.
Step 5 copy running-config startup config (Optional) If the switch is in VTP transparent mode, the VLAN
configuration is saved in the running configuration file as well as in
the VLAN database. This saves the configuration in the switch startup
configuration file.
Note If you assign an interface to a VLAN that does not exist, the new VLAN is created. (See the “Creating
or Modifying an Ethernet VLAN” section on page 11-8.)
Beginning in privileged EXEC mode, follow these steps to assign a port to a VLAN in the VLAN
database:
Command Purpose
Step 1 configure terminal Enter global configuration mode
Step 2 interface interface-id Enter the interface to be added to the VLAN.
Step 3 switchport mode access Define the VLAN membership mode for the port (Layer 2 access
port).
Step 4 switchport access vlan vlan-id Assign the port to a VLAN. Valid VLAN IDs are 1 to 4094.
Step 5 end Return to privileged EXEC mode.
Step 6 show running-config interface interface-id Verify the VLAN membership mode of the interface.
Step 7 show interfaces interface-id switchport Verify your entries in the Administrative Mode and the Access Mode
VLAN fields of the display.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return an interface to its default configuration, use the default interface interface-id interface
configuration command.
This example shows how to configure a port as an access port in VLAN 2:
Switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# switchport mode access
Switch(config-if)# switchport access vlan 2
Switch(config-if)# end
Note Although the switch supports 4094 VLAN IDs, see the “Supported VLANs” section on page 11-2 for
the actual number of VLANs supported.
• STP is enabled by default on extended-range VLANs, but you can disable it by using the no
spanning-tree vlan vlan-id global configuration command. When the maximum number of
spanning-tree instances (128) are on the switch, spanning tree is disabled on any newly created
VLANs. If the number of VLANs on the switch exceeds the maximum number of spanning tree
instances, we recommend that you configure the IEEE 802.1s Multiple STP (MSTP) on your switch
to map multiple VLANs to a single STP instance. For more information about MSTP, see
Chapter 17, “Configuring MSTP.”
• Each routed port on the switch creates an internal VLAN for its use. These internal VLANs use
extended-range VLAN numbers, and the internal VLAN ID cannot be used for an extended-range
VLAN. If you try to create an extended-range VLAN with a VLAN ID that is already allocated as
an internal VLAN, an error message is generated, and the command is rejected.
– Because internal VLAN IDs are in the lower part of the extended range, we recommend that you
create extended-range VLANs beginning from the highest number (4094) and moving to the
lowest (1006) to reduce the possibility of using an internal VLAN ID.
– Before configuring extended-range VLANs, enter the show vlan internal usage privileged
EXEC command to see which VLANs have been allocated as internal VLANs.
– If necessary, you can shut down the routed port assigned to the internal VLAN, which frees up
the internal VLAN, and then create the extended-range VLAN and re-enable the port, which
then uses another VLAN as its internal VLAN. See the “Creating an Extended-Range VLAN
with an Internal VLAN ID” section on page 11-13.
• Although the switch supports a total of 1005 (normal-range and extended-range) VLANs, the
number of routed ports, SVIs, and other configured features affects the use of the switch hardware.
If you try to create an extended-range VLAN and there are not enough hardware resources available,
an error message is generated, and the extended-range VLAN is rejected.
Note Before you create an extended-range VLAN, you can verify that the VLAN ID is not used internally by
entering the show vlan internal usage privileged EXEC command. If the VLAN ID is used internally
and you want to free it up, go to the“Creating an Extended-Range VLAN with an Internal VLAN ID”
section on page 11-13 before creating the extended-range VLAN.
Beginning in privileged EXEC mode, follow these steps to create an extended-range VLAN:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 vtp mode transparent Configure the switch for VTP transparent mode, disabling VTP.
Step 3 vlan vlan-id Enter an extended-range VLAN ID and enter VLAN configuration mode.
The range is 1006 to 4094.
Step 4 mtu mtu-size (Optional) Modify the VLAN by changing the MTU size.
Note Although all VLAN commands appear in the CLI help in VLAN
configuration mode, only the mtu mtu-size and remote-span
commands are supported for extended-range VLANs.
Step 5 remote-span (Optional) Configure the VLAN as the RSPAN VLAN. See the
“Configuring a VLAN as an RSPAN VLAN” section on page 28-16.
Step 6 end Return to privileged EXEC mode.
Step 7 show vlan id vlan-id Verify that the VLAN has been created.
Step 8 copy running-config startup config Save your entries in the switch startup configuration file. To save
extended-range VLAN configurations, you need to save the VTP
transparent mode configuration and the extended-range VLAN
configuration in the switch startup configuration file. Otherwise, if the
switch resets, it will default to VTP server mode, and the extended-range
VLAN IDs will not be saved.
To delete an extended-range VLAN, use the no vlan vlan-id global configuration command.
The procedure for assigning static-access ports to an extended-range VLAN is the same as for
normal-range VLANs. See the “Assigning Static-Access Ports to a VLAN” section on page 11-10.
This example shows how to create a new extended-range VLAN with all default characteristics, enter
VLAN configuration mode, and save the new VLAN in the switch startup configuration file:
Switch(config)# vtp mode transparent
Switch(config)# vlan 2000
Switch(config-vlan)# end
Switch# copy running-config startup config
Beginning in privileged EXEC mode, follow these steps to release a VLAN ID that is assigned to an
internal VLAN and to create an extended-range VLAN with that ID:
Command Purpose
Step 1 show vlan internal usage Display the VLAN IDs being used internally by the switch. If the VLAN
ID that you want to use is an internal VLAN, the display shows the routed
port that is using the VLAN ID. Enter that port number in Step 3.
Step 2 configure terminal Enter global configuration mode.
Step 3 interface interface-id Enter the interface ID for the routed port that is using the VLAN ID.
Step 4 shutdown Shut down the port to free the internal VLAN ID.
Step 5 exit Return to global configuration mode.
Step 6 vtp mode transparent Set the VTP mode to transparent for creating extended-range VLANs.
Step 7 vlan vlan-id Enter the new extended-range VLAN ID, and enter VLAN configuration
mode.
Step 8 exit Exit from VLAN configuration mode, and return to global configuration
mode.
Step 9 interface interface-id Enter the interface ID for the routed port that you shut down in Step 4.
Step 10 no shutdown Re-enable the routed port. It will be assigned a new internal VLAN ID.
Step 11 end Return to privileged EXEC mode.
Step 12 copy running-config startup config Save your entries in the switch startup configuration file. To save an
extended-range VLAN configuration, you need to save the VTP
transparent mode configuration and the extended-range VLAN
configuration in the switch startup configuration file. Otherwise, if the
switch resets, it will default to VTP server mode, and the extended-range
VLAN IDs will not be saved.
Displaying VLANs
Use the show vlan privileged EXEC command to display a list of all VLANs on the switch, including
extended-range VLANs. The display includes VLAN status, ports, and configuration information. For a
list of the VLAN IDs on the switch, use the show vlan privileged EXEC command.
Table 11-3 lists the privileged EXEC commands for monitoring VLANs.
Command Purpose
show interfaces [vlan Display characteristics for all interfaces or for the specified VLAN
vlan-id] configured on the switch.
show vlan [id vlan-id] Display parameters for all VLANs or the specified VLAN on the switch.
For more details about the show command options and explanations of output fields, see the command
reference for this release.
Trunking Overview
A trunk is a point-to-point link between one or more Ethernet switch interfaces and another networking device
such as a router or a switch. Ethernet trunks carry the traffic of multiple VLANs over a single link, and you
can extend the VLANs across an entire network.
Trunking encapsulation is available on 802.1Q Ethernet interfaces. 802.1Q is an industry-standard
trunking encapsulation.
You can configure a trunk on a single Ethernet interface or on an EtherChannel bundle. For more
information about EtherChannel, see Chapter 35, “Configuring EtherChannels and Link-State
Tracking.”
Ethernet trunk interfaces support different trunking modes (see Table 11-4). You can set an interface as
trunking or nontrunking or to negotiate trunking with the neighboring interface. To autonegotiate
trunking, the interfaces must be in the same VTP domain.
Trunk negotiation is managed by the Dynamic Trunking Protocol (DTP), which is a Point-to-Point
Protocol. However, some internetworking devices might forward DTP frames improperly, which could
cause misconfigurations.
To avoid this, you should configure interfaces connected to devices that do not support DTP to not
forward DTP frames, that is, to turn off DTP.
• If you do not intend to trunk across those links, use the switchport mode access interface
configuration command to disable trunking.
• To enable trunking to a device that does not support DTP, use the switchport mode trunk and
switchport nonegotiate interface configuration commands to cause the interface to become a trunk
but to not generate DTP frames. Use the switchport trunk encapsulation dot1q interface to select
the encapsulation type on the trunk port.
Note Beginning with Cisco IOS Release 12.2(22)EY, ES ports support only 802.1 encapsulation. You
cannot configure encapsulation on an ES port.
You can specify on standard DTP interfaces whether the trunk uses ISL or 802.1Q encapsulation or if
the encapsulation type is autonegotiated. The DTP supports autonegotiation of 802.1Q trunks.
Note Tunnel ports do not support DTP. See Chapter 15, “Configuring IEEE 802.1Q and Layer 2
Protocol Tunneling,” for more information on tunnel ports.
Mode Function
switchport mode access Puts the interface (access port) into permanent nontrunking mode and negotiates to
convert the link into a nontrunk link. The interface becomes a nontrunk interface
regardless of whether or not the neighboring interface is a trunk interface.
switchport mode dynamic auto Makes the interface able to convert the link to a trunk link. The interface becomes a trunk
interface if the neighboring interface is set to trunk or desirable mode. The default
switchport mode for all Ethernet interfaces is dynamic auto.
switchport mode dynamic Makes the interface actively attempt to convert the link to a trunk link. The interface
desirable becomes a trunk interface if the neighboring interface is set to trunk, desirable, or auto
mode.
switchport mode trunk Puts the interface into permanent trunking mode and negotiates to convert the
neighboring link into a trunk link. The interface becomes a trunk interface even if the
neighboring interface is not a trunk interface.
switchport nonegotiate Prevents the interface from generating DTP frames. You can use this command only when
the interface switchport mode is access or trunk. You must manually configure the
neighboring interface as a trunk interface to establish a trunk link.
switchport mode dot1q-tunnel Configures the interface as a tunnel (nontrunking) port to be connected in an asymmetric
link with an 802.1Q trunk port. 802.1Q tunneling is used to maintain customer VLAN
integrity across a service provider network. See Chapter 15, “Configuring IEEE 802.1Q
and Layer 2 Protocol Tunneling,” for more information on tunnel ports.
Encapsulation Types
Table 11-5 lists the Ethernet trunk encapsulation types and keywords.
Note Beginning with Cisco IOS Release 12.2(22)EY, ISL trunks are not supported on ES ports. The
encapsulation keyword is no longer visible for ES ports.
Encapsulation Function
switchport trunk encapsulation dot1q Specifies 802.1Q encapsulation on the trunk link.
switchport trunk encapsulation isl Specifies ISL encapsulation on the trunk link.
Encapsulation Function
switchport trunk encapsulation negotiate Specifies that the interface negotiate with the neighboring interface to become
an ISL (preferred) or 802.1Q trunk, depending on the configuration and
capabilities of the neighboring interface. This is the default for standard ports
on the switch.
switchport trunk dot1q ethertype value Sets the ethertype value for 802.1Q encapsulation. Used to select a nonstandard
(nondefault) 2-byte ethertype to identify 802.1Q tagged frames. The default
ethertype value is 0x8100.
This option is supported only on enhanced-services (ES) ports.
Note The switch does not support Layer 3 trunks; you cannot configure subinterfaces or use the encapsulation
keyword on Layer 3 interfaces. The switch does support Layer 2 trunks and Layer 3 VLAN interfaces,
which provide equivalent capabilities.
Note Beginning with Cisco IOS Release 12.2(22)EY, ES ports only support IEEE 802.1Q trunking.
802.1Q trunks impose these limitations on the trunking strategy for a network:
• In a network of Cisco switches connected through 802.1Q trunks, the switches maintain one instance
of spanning tree for each VLAN allowed on the trunks. Non-Cisco devices might support one
spanning-tree instance for all VLANs.
When you connect a Cisco switch to a non-Cisco device through an IEEE 802.1Q trunk, the Cisco
switch combines the spanning-tree instance of the VLAN of the trunk with the spanning-tree
instance of the non-Cisco 802.1Q switch. However, spanning-tree information for each VLAN is
maintained by Cisco switches separated by a cloud of non-Cisco 802.1Q switches. The non-Cisco
802.1Q cloud separating the Cisco switches is treated as a single trunk link between the switches.
• Make sure the native VLAN for an IEEE 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 IEEE 802.1Q trunk without disabling spanning
tree on every VLAN in the network can potentially cause spanning-tree loops. We recommend that
you leave spanning tree enabled on the native VLAN of an 802.1Q trunk or disable spanning tree on
every VLAN in the network. Make sure your network is loop-free before disabling spanning tree.
• On an ES port, you can use the switchport trunk dot1q ethertype value interface configuration
command to program a custom ethertype value for the interface. This feature allows the switch to
interoperate with third-party vendor switches that do not use the standard 0x8100 ethertype to
identify 802.1Q-tagged frames. For example, if you set 0x1234 as the custom IEEE 802.1Q
ethertype on a trunk port, incoming frames containing that ethertype are assigned to the VLAN
contained in the tag following the ethertype as they would be with a standard 802.1Q trunk. Frames
arriving on a trunk port with either the standard ethertype (0x8100) or the custom ethertype value
are treated as valid IEEE 802.1Q traffic; frames containing any other ethertype are assigned to the
native VLAN of that trunk. Egress traffic that has an ethertype value of 0x8100 is mapped to the
customer ethertype.
Note By default, an interface is in Layer 2 mode. The default mode for Layer 2 interfaces is switchport mode
dynamic auto. If the neighboring interface supports trunking and is configured to allow trunking, the
link is a Layer 2 trunk or, if the interface is in Layer 3 mode, it becomes a Layer 2 trunk when you enter
the switchport interface configuration command. By default, standard port trunks (or ES port trunks in
release 12.1(14)AX) negotiate encapsulation. If the neighboring interface supports ISL and 802.1Q
encapsulation and both interfaces are set to negotiate the encapsulation type, the trunk uses ISL
encapsulation. Beginning with Cisco IOS Release 12.2(22)EY, ES ports support only 802.1Q
encapsulation.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter the interface configuration mode and the port to be configured for
trunking.
Command Purpose
Step 3 switchport trunk encapsulation {isl | Configure the port to support ISL or 802.1Q encapsulation or to negotiate
dot1q | negotiate} (the default) with the neighboring interface for encapsulation type.
(no longer visible on ES ports) You must configure each end of the link with the same encapsulation type.
Note The encapsulation keyword is not supported on ES ports for
Cisco IOS Release 12.2(22)EY and later. ES ports support only
802.1Q encapsulation.
Step 4 switchport mode {dynamic {auto | Configure the interface as a Layer 2 trunk (required only if the interface
desirable} | trunk} is a Layer 2 access port or tunnel port or to specify the trunking mode).
• dynamic auto—Set the interface to a trunk link if the neighboring
interface is set to trunk or desirable mode. This is the default.
• dynamic desirable—Set the interface to a trunk link if the
neighboring interface is set to trunk, desirable, or auto mode.
• trunk—Set the interface in permanent trunking mode and negotiate
to convert the link to a trunk link even if the neighboring interface is
not a trunk interface.
Step 5 switchport access vlan vlan-id (Optional) Specify the default VLAN, which is used if the interface stops
trunking.
Step 6 switchport trunk native vlan vlan-id Specify the native VLAN for 802.1Q trunks.
Step 7 end Return to privileged EXEC mode.
Step 8 show interfaces interface-id switchport Display the switchport configuration of the interface in the Administrative
Mode and the Administrative Trunking Encapsulation fields of the
display.
Step 9 show interfaces interface-id trunk Display the trunk configuration of the interface.
Step 10 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return an interface to its default configuration, use the default interface interface-id interface
configuration command. To reset all trunking characteristics of a trunking interface to the defaults, use
the no switchport trunk interface configuration command. To disable trunking, use the switchport
mode access interface configuration command to configure the port as a static-access port.
This example shows how to configure a standard port as an IEEE 802.1Q trunk. The example assumes
that the neighbor interface is configured to support IEEE 802.1Q trunking.
Switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# switchport mode dynamic desirable
Switch(config-if)# switchport trunk encapsulation dot1q
Switch(config-if)# end
Note VLAN 1 is the default VLAN on all trunk ports in all Cisco switches, and it has previously been a
requirement that VLAN 1 always be enabled on every trunk link. You can use the VLAN 1 minimization
feature to disable VLAN 1 on any individual VLAN trunk link so that no user traffic (including spanning
tree advertisements) is sent or received on VLAN 1.
To reduce the risk of spanning-tree loops or storms, you can disable VLAN 1 on any individual VLAN
trunk port by removing VLAN 1 from the allowed list. When you remove VLAN 1 from a trunk port,
the interface continues to sent and receive management traffic, for example, Cisco Discovery Protocol
(CDP), Port Aggregation Protocol (PAgP), Link Aggregation Control Protocol (LACP), Dynamic
Trunking Protocol (DTP), and VLAN Trunking Protocol (VTP) in VLAN 1.
If a trunk port with VLAN 1 disabled is converted to a nontrunk port, it is added to the access VLAN. If
the access VLAN is set to 1, the port will be added to VLAN 1, regardless of the switchport trunk
allowed setting. The same is true for any VLAN that has been disabled on the port.
A trunk port can become a member of a VLAN if the VLAN is enabled, if VTP knows of the VLAN,
and if the VLAN is in the allowed list for the port. When VTP detects a newly enabled VLAN and the
VLAN is in the allowed list for a trunk port, the trunk port automatically becomes a member of the
enabled VLAN. When VTP detects a new VLAN and the VLAN is not in the allowed list for a trunk
port, the trunk port does not become a member of the new VLAN.
Beginning in privileged EXEC mode, follow these steps to modify the allowed list of an ISL
or 802.1Q trunk:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode and the port to be configured.
Step 3 switchport mode trunk Configure the interface as a VLAN trunk port.
Step 4 switchport trunk allowed vlan {add | (Optional) Configure the list of VLANs allowed on the trunk.
all | except | remove} vlan-list
For explanations about using the add, all, except, and remove keywords,
see the command reference for this release.
The vlan-list parameter is either a single VLAN number from 1 to 4094
or a range of VLANs described by two VLAN numbers, the lower one
first, separated by a hyphen. Do not enter any spaces between
comma-separated VLAN parameters or in hyphen-specified ranges.
All VLANs are allowed by default.
Step 5 end Return to privileged EXEC mode.
Step 6 show interfaces interface-id switchport Verify your entries in the Trunking VLANs Enabled field of the display.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default allowed VLAN list of all VLANs, use the no switchport trunk allowed vlan
interface configuration command.
This example shows how to remove VLAN 2 from the allowed VLAN list on a port:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# switchport trunk allowed vlan remove 2
Switch(config-if)# end
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and select the trunk port for which
VLANs should be pruned.
Step 3 switchport trunk pruning vlan {add | Configure the list of VLANs allowed to be pruned from the trunk. (See
except | none | remove} vlan-list the “VTP Pruning” section on page 12-4).
[,vlan[,vlan[,,,]]
For explanations about using the add, except, none, and remove
keywords, see the command reference for this release.
Separate nonconsecutive VLAN IDs with a comma and no spaces; use a
hyphen to designate a range of IDs. Valid IDs are from 2 to 1001.
Extended-range VLANs (VLAN IDs 1006 to 4094) cannot be pruned.
VLANs that are pruning-ineligible receive flooded traffic.
The default list of VLANs allowed to be pruned contains VLANs 2 to
1001.
Step 4 end Return to privileged EXEC mode.
Step 5 show interfaces interface-id switchport Verify your entries in the Pruning VLANs Enabled field of the display.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default pruning-eligible list of all VLANs, use the no switchport trunk pruning vlan
interface configuration command.
For information about 802.1Q configuration issues, see the “IEEE 802.1Q Configuration
Considerations” section on page 11-17.
Beginning in privileged EXEC mode, follow these steps to configure the native VLAN on an 802.1Q
trunk:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and define the interface that is
configured as the 802.1Q trunk.
Step 3 switchport trunk native vlan vlan-id Configure the VLAN that is sending and receiving untagged traffic
on the trunk port.
For vlan-id, the range is 1 to 4094.
Step 4 end Return to privileged EXEC mode.
Step 5 show interfaces interface-id switchport Verify your entries in the Trunking Native Mode VLAN field.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default native VLAN, VLAN 1, use the no switchport trunk native vlan interface
configuration command.
If a packet has a VLAN ID that is the same as the outgoing port native VLAN ID, the packet is sent
untagged; otherwise, the switch sends the packet with a tag.
Switch A
Trunk 1 Trunk 2
VLANs 8 – 10 (priority 16) VLANs 3 – 6 (priority 16)
VLANs 3 – 6 (priority 128) VLANs 8 – 10 (priority 128)
93370
Switch B
Beginning in privileged EXEC mode, follow these steps to configure the network shown in Figure 11-2.
Command Purpose
Step 1 configure terminal Enter global configuration mode on Switch A.
Step 2 vtp domain domain-name Configure a VTP administrative domain.
The domain name can be from 1 to 32 characters.
Step 3 vtp mode server Configure Switch A as the VTP server.
Step 4 end Return to privileged EXEC mode.
Step 5 show vtp status Verify the VTP configuration on both Switch A and Switch B.
In the display, check the VTP Operating Mode and the VTP Domain
Name fields.
Step 6 show vlan Verify that the VLANs exist in the database on Switch A.
Step 7 configure terminal Enter global configuration mode.
Step 8 interface gigabitethernet1/ 0/1 Enter interface configuration mode, and define Gigabit Ethernet
port 1 as the interface to be configured as a trunk.
Step 9 switchport trunk encapsulation {isl | Configure the port to support ISL or 802.1Q encapsulation or to
dot1q | negotiate} negotiate with the neighboring interface. You must configure each
end of the link with the same encapsulation type.
Note Beginning with Cisco IOS Release 12.2(22)EY, ES ports
support only 802.1Q trunking; therefore, these keywords are
only visible on standard ports.
Step 10 switchport mode trunk Configure the port as a trunk port.
Step 11 end Return to privileged EXEC mode.
Step 12 show interfaces gigabitethernet1/ 0/1 Verify the VLAN configuration.
switchport
Step 13 Repeat Steps 7 through 11 on Switch A for a second interface in the
switch.
Command Purpose
Step 14 Repeat Steps 7 through 11 on Switch B to configure the trunk ports
that connect to the trunk ports configured on Switch A.
Step 15 show vlan When the trunk links come up, VTP passes the VTP and VLAN
information to Switch B. Verify that Switch B has learned the VLAN
configuration.
Step 16 configure terminal Enter global configuration mode on Switch A.
Step 17 interface gigabitethernet1/ 0/1 Enter interface configuration mode, and define the interface to set the
STP port priority.
Step 18 spanning-tree vlan 8-10 port-priority 16 Assign the port priority of 16 for VLANs 8 through 10.
Step 19 exit Return to global configuration mode.
Step 20 interface gigabitethernet1/0/2 Enter interface configuration mode, and define the interface to set the
STP port priority.
Step 21 spanning-tree vlan 3-6 port-priority 16 Assign the port priority of 16 for VLANs 3 through 6.
Step 22 end Return to privileged EXEC mode.
Step 23 show running-config Verify your entries.
Step 24 copy running-config startup-config (Optional) Save your entries in the configuration file.
Switch A
90573
Switch B
Beginning in privileged EXEC mode, follow these steps to configure the network shown in Figure 11-3:
Command Purpose
Step 1 configure terminal Enter global configuration mode on Switch A.
Step 2 interface gigabitethernet1/0/1 Enter interface configuration mode, and define Gigabit Ethernet port 1
as the interface to be configured as a trunk.
Step 3 switchport trunk encapsulation Configure the port to support ISL or 802.1Q encapsulation. You must
{isl | dot1q | negotiate} configure each end of the link with the same encapsulation type.
Note Beginning with Cisco IOS Release 12.2(22)EY, ES ports
support only 802.1Q trunking; therefore, these keywords are
only visible on standard ports.
Step 4 switchport mode trunk Configure the port as a trunk port.
The trunk defaults to ISL trunking.
Step 5 exit Return to global configuration mode.
Step 6 Repeat Steps 2 through 4 on a second interface in Switch A.
Step 7 end Return to privileged EXEC mode.
Step 8 show running-config Verify your entries. In the display, make sure that the interfaces
configures in Steps 2 and 6 are configured as trunk ports.
Command Purpose
Step 9 show vlan When the trunk links come up, Switch A receives the VTP information
from the other switches. Verify that Switch A has learned the VLAN
configuration.
Step 10 configure terminal Enter global configuration mode.
Step 11 interface gigabitethernet1/0/1 Enter interface configuration mode, and define Gigabit Ethernet port 1
as the interface on which to set the STP cost.
Step 12 spanning-tree vlan 2-4 cost 30 Set the spanning-tree path cost to 30 for VLANs 2 through 4.
Step 13 end Return to global configuration mode.
Step 14 Repeat Steps 9 through 11 on the other configured trunk interface on
Switch A, and set the spanning-tree path cost to 30 for VLANs 8, 9, and
10.
Step 15 exit Return to privileged EXEC mode.
Step 16 show running-config Verify your entries. In the display, verify that the path costs are set
correctly for both trunk interfaces.
Step 17 copy running-config startup-config (Optional) Save your entries in the configuration file.
Configuring VMPS
The VLAN Query Protocol (VQP) is used to support dynamic-access ports, which are not permanently
assigned to a VLAN, but given VLAN assignments based on the MAC source addresses seen on the port.
Each time an unknown MAC address is seen, the switch sends a VQP query to a remote VMPS; the query
includes the newly seen MAC address and the port on which it was seen. The VMPS responds with a
VLAN assignment for the port. The switch cannot be a VMPS server but can act as a client to the VMPS
and communicate with it through VQP.
This section includes this information about configuring VMPS:
• “Understanding VMPS” section on page 11-28
• “Default VMPS Client Configuration” section on page 11-29
• “VMPS Configuration Guidelines” section on page 11-29
• “Configuring the VMPS Client” section on page 11-30
• “Monitoring the VMPS” section on page 11-32
• “Troubleshooting Dynamic-Access Port VLAN Membership” section on page 11-33
• “VMPS Configuration Example” section on page 11-33
Understanding VMPS
Each time the client switch receives the MAC address of a new host, it sends a VQP query to the VMPS.
When the VMPS receives this query, it searches its database for a MAC-address-to-VLAN mapping. The
server response is based on this mapping and whether or not the server is in open or secure mode. In
secure mode, the server shuts down the port when an illegal host is detected. In open mode, the server
simply denies the host access to the port.
If the port is currently unassigned (that is, it does not yet have a VLAN assignment), the VMPS provides
one of these responses:
• If the host is allowed on the port, the VMPS sends the client a vlan-assignment response containing
the assigned VLAN name and allowing access to the host.
• If the host is not allowed on the port and the VMPS is in open mode, the VMPS sends an
access-denied response.
• If the VLAN is not allowed on the port and the VMPS is in secure mode, the VMPS sends a
port-shutdown response.
If the port already has a VLAN assignment, the VMPS provides one of these responses:
• If the VLAN in the database matches the current VLAN on the port, the VMPS sends an success
response, allowing access to the host.
• If the VLAN in the database does not match the current VLAN on the port and active hosts exist on
the port, the VMPS sends an access-denied or a port-shutdown response, depending on the secure
mode of the VMPS.
If the switch receives an access-denied response from the VMPS, it continues to block traffic to and from
the host MAC address. The switch continues to monitor the packets directed to the port and sends a query
to the VMPS when it identifies a new host address. If the switch receives a port-shutdown response from
the VMPS, it disables the port. The port must be manually re-enabled by using the CLI or SNMP.
Dynamic-access ports can be used for direct host connections, or they can connect to a network. A
maximum of 20 MAC addresses are allowed per port on the switch. A dynamic-access port can belong
to only one VLAN at a time, but the VLAN can change over time, depending on the MAC addresses seen.
Note If the VMPS is being defined for a cluster of switches, enter the address on the command switch.
Beginning in privileged EXEC mode, follow these steps to enter the IP address of the VMPS:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 vmps server ipaddress primary Enter the IP address of the switch acting as the primary VMPS server.
Step 3 vmps server ipaddress (Optional) Enter the IP address of the switch acting as a secondary VMPS
server.
You can enter up to three secondary server addresses.
Step 4 end Return to privileged EXEC mode.
Step 5 show vmps Verify your entries in the VMPS Domain Server field of the display.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
Note You must have IP connectivity to the VMPS for dynamic-access ports to work. You can test for IP
connectivity by pinging the IP address of the VMPS and verifying that you get a response.
Caution Dynamic-access port VLAN membership is for end stations or hubs connected to end stations.
Connecting dynamic-access ports to other switches can cause a loss of connectivity.
Beginning in privileged EXEC mode, follow these steps to configure a dynamic-access port on a VMPS
client switch:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode for the switch port that is
connected to the end station.
Step 3 switchport mode access Set the port to access mode.
Step 4 switchport access vlan dynamic Configure the port as eligible for dynamic VLAN membership.
The dynamic-access port must be connected to an end station.
Step 5 end Return to privileged EXEC mode.
Step 6 show interfaces interface-id switchport Verify your entries in the Operational Mode field of the display.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return an interface to its default configuration, use the default interface interface-id interface
configuration command. To return an interface to its default switchport mode (dynamic auto), use the no
switchport mode interface configuration command. To reset the access mode to the default VLAN for
the switch, use the no switchport access vlan interface configuration command.
Command Purpose
Step 1 vmps reconfirm Reconfirm dynamic-access port VLAN membership.
Step 2 show vmps Verify the dynamic VLAN reconfirmation status.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 vmps reconfirm minutes Enter the number of minutes between reconfirmations of the dynamic
VLAN membership. The range is from 1 to 120. The default is 60 minutes.
Step 3 end Return to privileged EXEC mode.
Command Purpose
Step 4 show vmps Verify the dynamic VLAN reconfirmation status in the Reconfirm Interval
field of the display.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return the switch to its default setting, use the no vmps reconfirm global configuration command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 vmps retry count Change the retry count. The retry range is from 1 to 10; the default is 3.
Step 3 end Return to privileged EXEC mode.
Step 4 show vmps Verify your entry in the Server Retry Count field of the display.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return the switch to its default setting, use the no vmps retry global configuration command.
This is an example of output for the show vmps privileged EXEC command:
Switch# show vmps
Reconfirmation status
---------------------
VMPS Action: other
Primary VMPS
Server 1 Router
172.20.26.150
172.20.22.7
Client switch B
End Dynamic-access port
station 1 172.20.26.151
Trunk port
Switch C
Catalyst 6500 series
Secondary VMPS 172.20.26.152
Server 2
Switch D 172.20.26.153
Ethernet segment
(Trunk link)
Switch E 172.20.26.154
Switch F 172.20.26.155
Switch G 172.20.26.156
Switch H 172.20.26.157
Client switch I
Dynamic-access port
End
station 2 172.20.26.158
Trunk port
101363t
172.20.26.159
Catalyst 6500 series
Secondary VMPS Switch J
Server 3
This chapter describes how to use the VLAN Trunking Protocol (VTP) and the VLAN database for
managing VLANs with the Catalyst 3750 Metro switch.
Note For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
Understanding VTP
VTP is a Layer 2 messaging protocol that maintains VLAN configuration consistency by managing the
addition, deletion, and renaming of VLANs on a network-wide basis. VTP minimizes misconfigurations
and configuration inconsistencies that can cause several 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. Using VTP, you can
make configuration changes centrally on one or more switches and have those changes automatically
communicated to all the other switches in the network. Without VTP, you cannot send information about
VLANs to other switches.
VTP is designed to work in an environment where updates are made on a single switch and are sent
through VTP to other switches in the domain. It does not work well in a situation where multiple updates
to the VLAN database occur simultaneously on switches in the same domain, which would result in an
inconsistency in the VLAN database.
The switch supports 1005 VLANs, but the number of routed ports, SVIs, and other configured features
affects the usage of the switch hardware. If the switch is notified by VTP of a new VLAN and the switch
is already using the maximum available hardware resources, it sends a message that there are not enough
hardware resources available and shuts down the VLAN. The output of the show vlan user EXEC
command shows the VLAN in a suspended state.
VTP only learns about normal-range VLANs (VLAN IDs 1 to 1005). Extended-range VLANs (VLAN
IDs greater than 1005) are not supported by VTP or stored in the VTP VLAN database.
This section contains information about these VTP parameters and characteristics.
• The VTP Domain, page 12-2
• VTP Modes, page 12-3
• VTP Advertisements, page 12-3
• VTP Version 2, page 12-4
• VTP Pruning, page 12-4
Caution Before adding a VTP client switch to a VTP domain, always verify that its VTP configuration revision
number is lower than the configuration revision number of the other switches in the VTP domain.
Switches in a VTP domain always use the VLAN configuration of the switch with the highest VTP
configuration revision number. If you add a switch that has a revision number higher than the revision
number in the VTP domain, it can erase all VLAN information from the VTP server and VTP domain.
See the “Adding a VTP Client Switch to a VTP Domain” section on page 12-12 for the procedure for
verifying and resetting the VTP configuration revision number.
When you make a change to the VLAN configuration on a VTP server, the change is propagated to all
switches in the VTP domain. VTP advertisements are sent over all IEEE trunk connections, including
Inter-Switch Link (ISL) and IEEE 802.1Q. VTP dynamically maps VLANs with unique names and
internal index associates across multiple LAN types. Mapping eliminates excessive device
administration required from network administrators.
If you configure a switch for VTP transparent mode, you can create and modify VLANs, but the changes
are not sent to other switches in the domain, and they affect only the individual switch. However,
configuration changes made when the switch is in this mode are saved in the switch running
configuration and can be saved to the switch startup configuration file.
For domain name and password configuration guidelines, see the “VTP Configuration Guidelines”
section on page 12-7.
VTP Modes
You can configure a supported switch to be in one of the VTP modes listed in Table 12-1.
VTP Advertisements
Each switch in the VTP domain sends periodic global configuration advertisements from each trunk port
to a reserved multicast address. Neighboring switches receive these advertisements and update their VTP
and VLAN configurations as necessary.
Note Because trunk ports send and receive VTP advertisements, you must ensure that at least one trunk port
is configured on the switch and that this trunk port is connected to the trunk port of another switch.
Otherwise, the switch cannot receive any VTP advertisements. For more information on trunk ports, see
the “Configuring VLAN Trunks” section on page 11-15.
• MD5 digest VLAN configuration, including maximum transmission unit (MTU) size for each
VLAN.
• Frame format
VTP advertisements distribute this VLAN information for each configured VLAN:
• VLAN IDs (ISL and 802.1Q)
• VLAN name
• VLAN type
• VLAN state
• Additional VLAN configuration information specific to the VLAN type
VTP Version 2
If you use VTP in your network, you must decide whether to use Version 1 or Version 2. By default, VTP
operates in Version 1.
VTP Version 2 supports these features not supported in Version 1:
• Token Ring support—VTP Version 2 supports Token Ring Bridge Relay Function (TrBRF) and
Token Ring Concentrator Relay Function (TrCRF) VLANs. For more information about Token Ring
VLANs, see the “Configuring Normal-Range VLANs” section on page 11-4.
• Unrecognized Type-Length-Value (TLV) support—A VTP server or client propagates configuration
changes to its other trunks, even for TLVs it is not able to parse. The unrecognized TLV is saved in
NVRAM when the switch is operating in VTP server mode.
• Version-Dependent Transparent Mode—In VTP version 1, a VTP transparent switch inspects VTP
messages for the domain name and version and forwards a message only if the version and domain
name match. Although VTP version 2 supports only one domain, a VTP version 2 transparent switch
forwards a message only when the domain name matches.
• Consistency Checks—In 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 MD5 digest on a received VTP message is correct, its
information is accepted.
VTP Pruning
VTP pruning increases network available bandwidth by restricting flooded traffic to those trunk links
that the traffic must use to reach the destination devices. Without VTP pruning, a switch floods
broadcast, multicast, and unknown unicast traffic across all trunk links within a VTP domain even
though receiving switches might discard them. VTP pruning is disabled by default.
VTP pruning blocks unneeded flooded traffic to VLANs on trunk ports that are included in the
pruning-eligible list. Only VLANs included in the pruning-eligible list can be pruned. By default,
VLANs 2 through 1001 are pruning eligible switch trunk ports. If the VLANs are configured as
pruning-ineligible, the flooding continues. VTP pruning is supported with VTP Version 1 and Version 2.
Figure 12-1 shows a switched network without VTP pruning enabled. Port 1 on Switch A and Port 2 on
Switch D are assigned to the Red VLAN. If a broadcast is sent from the host connected to Switch A,
Switch A floods the broadcast and every switch in the network receives it, even though Switches C, E,
and F have no ports in the Red VLAN.
Switch D
Port 2
Switch E Switch B
Red
VLAN
Port 1
89240
Switch F Switch C Switch A
Figure 12-2 shows a switched network with VTP pruning enabled. The broadcast traffic from Switch A
is not forwarded to Switches C, E, and F because traffic for the Red VLAN has been pruned on the links
shown (Port 5 on Switch B and Port 4 on Switch D).
Switch D
Port 2
Flooded traffic
is pruned. Port
4
Switch B
Red
VLAN
Switch E Flooded traffic
is pruned. Port
5
Port 1
89241
Enabling VTP pruning on a VTP server enables pruning for the entire management domain. Making
VLANs pruning-eligible or pruning-ineligible affects pruning eligibility for those VLANs on that trunk
only (not on all switches in the VTP domain).
See the “Enabling VTP Pruning” section on page 12-12. VTP pruning takes effect several seconds after
you enable it. VTP pruning does not prune traffic from VLANs that are pruning-ineligible. VLAN 1 and
VLANs 1002 to 1005 are always pruning-ineligible; traffic from these VLANs cannot be pruned.
Extended-range VLANs (VLAN IDs higher than 1005) are also pruning-ineligible.
VTP pruning is not designed to function in VTP transparent mode. If one or more switches in the
network are in VTP transparent mode, you should do one of these:
• Turn off VTP pruning in the entire network.
• Turn off VTP pruning by making all VLANs on the trunk of the switch upstream to the VTP
transparent switch pruning ineligible.
To configure VTP pruning on an interface, use the switchport trunk pruning vlan interface
configuration command (see the “Changing the Pruning-Eligible List” section on page 11-22). VTP
pruning operates when an interface is trunking. You can set VLAN pruning-eligibility, whether or not
VTP pruning is enabled for the VTP domain, whether or not any given VLAN exists, and whether or not
the interface is currently trunking.
Configuring VTP
This section includes guidelines and procedures for configuring VTP. These sections are included:
• Default VTP Configuration, page 12-6
• VTP Configuration Guidelines, page 12-7
• Configuring a VTP Server, page 12-8
• Configuring a VTP Client, page 12-9
• Disabling VTP (VTP Transparent Mode), page 12-10
• Enabling VTP Version 2, page 12-11
• Enabling VTP Pruning, page 12-12
• Adding a VTP Client Switch to a VTP Domain, page 12-12
Domain Names
When configuring VTP for the first time, you must always assign a domain name. You must configure
all switches in the VTP domain with the same domain name. Switches in VTP transparent mode do not
exchange VTP messages with other switches, and you do not need to configure a VTP domain name
for them.
Note If NVRAM and DRAM storage is sufficient, all switches in a VTP domain should be in VTP server
mode.
Caution Do not configure a VTP domain if all switches are operating in VTP client mode. If you configure the
domain, it is impossible to make changes to the VLAN configuration of that domain. Make sure that you
configure at least one switch in the VTP domain for VTP server mode.
Passwords
You can configure a password for the VTP domain, but it is not required. If you do configure a domain
password, all domain switches must share the same password and you must configure the password on
each switch in the management domain. Switches without a password or with the wrong password reject
VTP advertisements.
If you configure a VTP password for a domain, a switch that is booted without a VTP configuration does
not accept VTP advertisements until you configure it with the correct password. After the configuration,
the switch accepts the next VTP advertisement that uses the same password and domain name in the
advertisement.
If you are adding a new switch to an existing network with VTP capability, the new switch learns the
domain name only after the applicable password has been configured on it.
Caution When you configure a VTP domain password, the management domain does not function properly if you
do not assign a management domain password to each switch in the domain.
VTP Version
Follow these guidelines when deciding which VTP version to implement:
• All switches in a VTP domain must run the same VTP version.
• A VTP Version 2-capable switch can operate in the same VTP domain as a switch running VTP
Version 1 if Version 2 is disabled on the Version 2-capable switch (Version 2 is disabled by default).
• Do not enable VTP Version 2 on a switch unless all of the switches in the same VTP domain are
Version-2-capable. When you enable Version 2 on a switch, all of the Version-2-capable switches in
the domain enable Version 2. If there is a Version 1-only switch, it does not exchange VTP
information with switches with Version 2 enabled.
• If there are TrBRF and TrCRF Token Ring networks in your environment, you must enable VTP
Version 2 for Token Ring VLAN switching to function properly. To run Token Ring and Token
Ring-Net, disable VTP Version 2.
Configuration Requirements
When you configure VTP, you must configure a trunk port so that the switch can send and receive VTP
advertisements to and from other switches in the domain.
For more information, see the “Configuring VLAN Trunks” section on page 11-15.
If you are configuring VTP on a cluster member switch to a VLAN, use the rcommand privileged EXEC
command to log into the member switch. For more information about the command, see the command
reference for this release.
If you are configuring extended-range VLANs on the switch, the switch must be in VTP transparent
mode.
VTP does not support private VLANs. If you configure private VLANs, the switch must be in VTP
transparent mode. When private VLANs are configured on the switch, do not change the VTP mode from
transparent to client or server mode.
Note If extended-range VLANs are configured on the switch, you cannot change VTP mode to server. You
receive an error message, and the configuration is not allowed.
Beginning in privileged EXEC mode, follow these steps to configure the switch as a VTP server:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 vtp domain domain-name Configure the VTP administrative-domain name. The name can be from
1 to 32 characters. All switches operating in VTP server or client mode
under the same administrative responsibility must be configured with the
same domain name.
Step 3 vtp mode server Configure the switch for VTP server mode (the default).
Step 4 vtp password password (Optional) Set the password for the VTP domain. The password can be
from 8 to 64 characters.
If you configure a VTP password, the VTP domain does not function
properly if you do not assign the same password to each switch in the
domain.
Step 5 end Return to privileged EXEC mode.
Step 6 show vtp status Verify your entries in the VTP Operating Mode and the VTP Domain Name
fields of the display.
When you configure a domain name, it cannot be removed; you can only reassign a switch to a different
domain.
To return the switch to a no-password state, use the no vtp password global configuration command.
This example shows how to use global configuration mode to configure the switch as a VTP server with
the domain name eng_group and the password mypassword:
Switch# config terminal
Switch(config)# vtp domain eng_group
Switch(config)# vtp mode server
Switch(config)# vtp password mypassword
Switch(config)# end
Caution If all switches are operating in VTP client mode, do not configure a VTP domain name. If you do, it is
impossible to make changes to the VLAN configuration of that domain. Therefore, make sure you
configure at least one switch as a VTP server.
Beginning in privileged EXEC mode, follow these steps to configure the switch as a VTP client:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 vtp domain domain-name (Optional) Enter the VTP administrative-domain name. The name can be
from 1 to 32 characters. This should be the same domain name as the VTP
server.
All switches operating in VTP server or client mode under the same
administrative responsibility must be configured with the same domain
name.
Step 3 vtp mode client Configure the switch for VTP client mode. The default setting is VTP
server.
Step 4 vtp password password (Optional) Enter the password for the VTP domain.
Step 5 end Return to privileged EXEC mode.
Step 6 show vtp status Verify your entries in the VTP Operating Mode and the VTP Domain Name
fields of the display.
Use the no vtp mode global configuration command to return the switch to VTP server mode. To return
the switch to a no-password state, use the no vtp password privileged EXEC command. When you
configure a domain name, it cannot be removed; you can only reassign a switch to a different domain.
Note Before you create extended-range VLANs (VLAN IDs 1006 to 4094), you must set VTP mode to
transparent by using the vtp mode transparent global configuration command. Save this configuration
to the startup configuration so that the switch boots up in VTP transparent mode. Otherwise, you lose
the extended-range VLAN configuration if the switch resets and boots up in VTP server mode (the
default).
Beginning in privileged EXEC mode, follow these steps to configure VTP transparent mode and save the
VTP configuration in the switch startup configuration file:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 vtp mode transparent Configure the switch for VTP transparent mode (disable VTP).
Step 3 end Return to privileged EXEC mode.
Step 4 show vtp status Verify your entries in the VTP Operating Mode and the VTP Domain
Name fields of the display.
Step 5 copy running-config startup-config (Optional) Save the configuration in the startup configuration file.
Note Only VTP mode and domain name are saved in the switch running
configuration and can be copied to the startup configuration file.
To return the switch to VTP server mode, use the no vtp mode global configuration command.
Note If extended-range VLANs are configured on the switch, you cannot change the VTP mode to server. You
receive an error message, and the configuration is not allowed.
Caution VTP Version 1 and VTP Version 2 are not interoperable on switches in the same VTP domain. Every
switch in the VTP domain must use the same VTP version. Do not enable VTP Version 2 unless every
switch in the VTP domain supports Version 2.
Note In TrCRF and TrBRF Token ring environments, you must enable VTP Version 2 for Token Ring VLAN
switching to function properly. For Token Ring and Token Ring-Net media, VTP Version 2 must be
disabled.
For more information on VTP version configuration guidelines, see the “VTP Version” section on
page 12-8.
Beginning in privileged EXEC mode, follow these steps to enable VTP Version 2:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 vtp version 2 Enable VTP Version 2 on the switch.
VTP Version 2 is disabled by default on VTP Version 2-capable switches.
Command Purpose
Step 3 end Return to privileged EXEC mode.
Step 4 show vtp status Verify that VTP Version 2 is enabled in the VTP V2 Mode field of the display.
To disable VTP Version 2, use the no vtp version global configuration command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 vtp pruning Enable pruning in the VTP administrative domain.
By default, pruning is disabled. You need to enable pruning on only one switch
in VTP server mode.
Step 3 end Return to privileged EXEC mode.
Step 4 show vtp status Verify your entries in the VTP Pruning Mode field of the display.
To disable VTP pruning, use the no vtp pruning global configuration command.
Pruning is supported with VTP Version 1 and Version 2. If you enable pruning on the VTP server, it is
enabled for the entire VTP domain.
Only VLANs included in the pruning-eligible list can be pruned. By default, VLANs 2 through 1001 are
pruning eligible on trunk ports. Reserved VLANs and extended-range VLANs cannot be pruned. To
change the pruning-eligible VLANs, see the “Changing the Pruning-Eligible List” section on
page 11-22.
Beginning in privileged EXEC mode, follow these steps to verify and reset the VTP configuration
revision number on a switch before adding it to a VTP domain:
Command Purpose
Step 1 show vtp status Check the VTP configuration revision number.
If the number is 0, add the switch to the VTP domain.
If the number is greater than 0, follow these steps:
a. Write down the domain name.
b. Write down the configuration revision number.
c. Continue with the next steps to reset the switch configuration revision number.
Step 2 configure terminal Enter global configuration mode.
Step 3 vtp domain domain-name Change the domain name from the original one displayed in Step 1 to a new name.
Step 4 end The VLAN information on the switch is updated and the configuration revision
number is reset to 0. You return to privileged EXEC mode.
Step 5 show vtp status Verify that the configuration revision number has been reset to 0.
Step 6 configure terminal Enter global configuration mode.
Step 7 vtp domain domain-name Enter the original domain name on the switch.
Step 8 end The VLAN information on the switch is updated, and you return to privileged EXEC
mode.
Step 9 show vtp status (Optional) Verify that the domain name is the same as in Step 1 and that the
configuration revision number is 0.
After resetting the configuration revision number, add the switch to the VTP domain.
Note You can use the vtp mode transparent global configuration command or the vtp transparent VLAN
database configuration command to disable VTP on the switch, and then change its VLAN information
without affecting the other switches in the VTP domain.
Monitoring VTP
You monitor VTP by displaying VTP configuration information: the domain name, the current VTP
revision, and the number of VLANs. You can also display statistics about the advertisements sent and
received by the switch.
Table 12-3 shows the privileged EXEC commands for monitoring VTP activity.
Command Purpose
show vtp status Display the VTP switch configuration information.
show vtp counters Display counters about VTP messages that have been sent and received.
This chapter describes how to configure private VLANs on the Catalyst 3750 Metro switch.
Note For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
Note When you configure private VLANs, the switch must be in VTP transparent mode. See Chapter 12,
“Configuring VTP.”
Primary
VLAN
Private
VLAN
domain
Subdomain Subdomain
Secondary Secondary
community VLAN isolated VLAN
116083
Note Trunk ports carry traffic from regular VLANs and also from primary, isolated, and community VLANs.
Trunk ports
116084
Carries VLAN 100,
201, and 202 traffic
Note that for private VLANs to operate correctly between two switches, you must configure VLAN
translation on both sides of the trunk. We recommend that you configure VLAN translation on the
enhanced-services (ES) port of each switch and use the same private VLAN IDs on the customer ports
of both switches. This allows data to pass between the private VLAN end users.
Because VTP does not support private VLANs, you must manually configure private VLANs on all
switches in the Layer 2 network. If you do not configure the primary and secondary VLAN associations
in some switches in the network, the Layer 2 databases in these switches are not merged. This can result
in unnecessary flooding of private-VLAN traffic on those switches.
Note When configuring private VLANs on the switch, always use the default Switch Database Management
(SDM) template to balance system resources between unicast routes and Layer 2 entries. If another SDM
template is configured, use the sdm prefer default global configuration command to set the default
template. See Chapter 6, “Configuring SDM Templates.”
Note If the VLAN is not created already, the private-VLAN configuration process creates it.
Step 3 Configure interfaces to be isolated or community host ports, and assign VLAN membership to the host
port. See the “Configuring a Layer 2 Interface as a Private-VLAN Host Port” section on page 13-11.
Step 4 Configure interfaces as promiscuous ports, and map the promiscuous ports to the primary-secondary
VLAN pair. See the “Configuring a Layer 2 Interface as a Private-VLAN Promiscuous Port” section on
page 13-12.
Step 5 If inter-VLAN routing will be used, configure the primary SVI, and map secondary VLANs to the
primary. See the “Mapping Secondary VLANs to a Primary VLAN Layer 3 VLAN Interface” section on
page 13-13.
Step 6 Verify private-VLAN configuration.
• 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.
Note In some cases, the configuration is accepted with no error messages, but the commands have no effect.
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.
Note The private-vlan commands do not take effect until you exit VLAN configuration mode.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 vtp mode transparent Set VTP mode to transparent (disable VTP).
Step 3 vlan vlan-id Enter VLAN configuration mode and designate or create a VLAN that
will be the primary VLAN. The VLAN ID range is 2 to 1001 and 1006
to 4094.
Step 4 private-vlan primary Designate the VLAN as the primary VLAN.
Step 5 exit Return to global configuration mode.
Step 6 vlan vlan-id (Optional) Enter VLAN configuration mode and designate or create a
VLAN that will be an isolated VLAN. The VLAN ID range is 2 to 1001
and 1006 to 4094.
Step 7 private-vlan isolated Designate the VLAN as an isolated VLAN.
Step 8 exit Return to global configuration mode.
Step 9 vlan vlan-id (Optional) Enter VLAN configuration mode and designate or create a
VLAN that will be a community VLAN. The VLAN ID range is 2 to
1001 and 1006 to 4094.
Step 10 private-vlan community Designate the VLAN as a community VLAN.
Step 11 exit Return to global configuration mode.
Step 12 vlan vlan-id Enter VLAN configuration mode for the primary VLAN designated in
Step 2.
Step 13 private-vlan association [add | remove] Associate the secondary VLANs with the primary VLAN.
secondary_vlan_list
Step 14 end Return to privileged EXEC mode.
Step 15 show vlan private-vlan [type] Verify the configuration.
or
show interfaces status
Step 16 copy running-config startup config Save your entries in the switch startup configuration file. To save the
private-VLAN configuration, you need to save the VTP transparent
mode configuration and private-VLAN configuration in the switch
startup configuration file. Otherwise, if the switch resets, it defaults to
VTP server mode, which does not support private VLANs.
When you associate secondary VLANs with a primary VLAN, note this syntax 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 but 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 mode.
This example shows how to configure VLAN 20 as a primary VLAN, VLAN 501 as an isolated VLAN,
and VLANs 502 and 503 as community VLANs, to associate them in a private VLAN, and to verify the
configuration:
Switch# configure terminal
Switch(config)# vlan 20
Switch(config-vlan)# private-vlan primary
Switch(config-vlan)# exit
Switch(config)# vlan 501
Switch(config-vlan)# private-vlan isolated
Switch(config-vlan)# exit
Switch(config)# vlan 502
Switch(config-vlan)# private-vlan community
Switch(config-vlan)# exit
Switch(config)# vlan 503
Switch(config-vlan)# private-vlan community
Switch(config-vlan)# exit
Switch(config)# vlan 20
Switch(config-vlan)# private-vlan association 501-503
Switch(config-vlan)# end
Switch(config)# show vlan private vlan
Primary Secondary Type Ports
------- --------- ----------------- ------------------------------------------
20 501 isolated
20 502 community
20 503 community
20 504 non-operational
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode for the Layer 2
interface to be configured.
Step 3 switchport mode private-vlan host Configure the Layer 2 port as a private-VLAN host port.
Step 4 switchport private-vlan host-association Associate the Layer 2 port with a private VLAN.
primary_vlan_id secondary_vlan_id
Step 5 end Return to privileged EXEC mode.
Command Purpose
Step 6 show interfaces [interface-id] switchport Verify the configuration.
Step 7 copy running-config startup config (Optional) Save your entries in the switch startup
configuration file.
This example shows how to configure an interface as a private-VLAN host port, associate it with a
private-VLAN pair, and verify the configuration:
Switch# configure terminal
Switch(config)# interface fastethernet 1/0/22
Switch(config-if)# switchport mode private-vlan host
Switch(config-if)# switchport private-vlan host-association 20 501
Switch(config-if)# end
Switch# show interfaces fastethernet 1/0/22 switchport
Name: Fa1/0/22
Switchport: Enabled
Administrative Mode: private-vlan host
Operational Mode: private-vlan host
Administrative Trunking Encapsulation: negotiate
Operational Trunking Encapsulation: native
Negotiation of Trunking: Off
Access Mode VLAN: 1 (default)
Trunking Native Mode VLAN: 1 (default)
Administrative Native VLAN tagging: enabled
Voice VLAN: none
Administrative private-vlan host-association: 20 501
Administrative private-vlan mapping: none
Administrative private-vlan trunk native VLAN: none
Administrative private-vlan trunk Native VLAN tagging: enabled
Administrative private-vlan trunk encapsulation: dot1q
Administrative private-vlan trunk normal VLANs: none
Administrative private-vlan trunk private VLANs: none
Operational private-vlan:
20 501
<output truncated>
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode for the Layer 2
interface to be configured.
Step 3 switchport mode private-vlan promiscuous Configure the Layer 2 port as a private-VLAN
promiscuous port.
Command Purpose
Step 4 switchport private-vlan mapping primary_vlan_id Map the private-VLAN promiscuous port to a primary
{add | remove} secondary_vlan_list VLAN and to selected secondary VLANs.
Step 5 end Return to privileged EXEC mode.
Step 6 show interfaces [interface-id] switchport Verify the configuration.
Step 7 copy running-config startup config (Optional) Save your entries in the switch startup
configuration file.
When you configure a Layer 2 interface as a private-VLAN promiscuous port, note this syntax
information:
• The secondary_vlan_list parameter cannot contain spaces. It can contain multiple comma-separated
items. Each item can be a single private-VLAN ID or a hyphenated range of private-VLAN IDs.
• Enter a secondary_vlan_list, or use the add keyword with a secondary_vlan_list to map the
secondary VLANs to the private-VLAN promiscuous port.
• Use the remove keyword with a secondary_vlan_list to clear the mapping between secondary
VLANs and the private-VLAN promiscuous port.
This example shows how to configure an interface as a private-VLAN promiscuous port and map it to a
private VLAN. The interface is a member of primary VLAN 20 and secondary VLANs 501 to 503 are
mapped to it.
Switch# configure terminal
Switch(config)# interface fastethernet 1/0/2
Switch(config-if)# switchport mode private-vlan promiscuous
Switch(config-if)# switchport private-vlan mapping 20 add 501-503
Switch(config-if)# end
Use the show vlan private-vlan or the show interface status privileged EXEC command to display
primary and secondary VLANs and private-VLAN ports on the switch.
Beginning in privileged EXEC mode, follow these steps to map secondary VLANs to the SVI of a
primary VLAN to allow Layer 3 switching of private-VLAN traffic:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface vlan primary_vlan_id Enter interface configuration mode for the primary
VLAN, and configure the VLAN as an SVI. The VLAN
ID range is 2 to 1001 and 1006 to 4094.
Command Purpose
Step 3 private-vlan mapping [add | remove] Map the secondary VLANs to the Layer 3 VLAN
secondary_vlan_list interface of a primary VLAN to allow Layer 3 switching
of private-VLAN ingress traffic.
Step 4 end Return to privileged EXEC mode.
Step 5 show interface private-vlan mapping Verify the configuration.
Step 6 copy running-config startup config (Optional) Save your entries in the switch startup
configuration file.
Note The private-vlan mapping interface configuration command only affects private-VLAN traffic that is
switched through Layer 3.
When you map secondary VLANs to the Layer 3 VLAN interface of a primary VLAN, note this syntax
information:
• The secondary_vlan_list parameter cannot contain spaces. It can contain multiple comma-separated
items. Each item can be a single private-VLAN ID or a hyphenated range of private-VLAN IDs.
• Enter a secondary_vlan_list, or use the add keyword with a secondary_vlan_list to map the
secondary VLANs to the primary VLAN.
• Use the remove keyword with a secondary_vlan_list to clear the mapping between secondary
VLANs and the primary VLAN.
This example shows how to map the interfaces of VLANs 501and 502 to primary VLAN 10, which
permits routing of secondary VLAN ingress traffic from private VLANs 501 to 502:
Switch# configure terminal
Switch(config)# interface vlan 10
Switch(config-if)# private-vlan mapping 501-502
Switch(config-if)# end
Switch# show interfaces private-vlan mapping
Interface Secondary VLAN Type
--------- -------------- -----------------
vlan10 501 isolated
vlan10 502 community
Command Purpose
show interfaces status Displays the status of interfaces, including the VLANs to which they
belongs.
show vlan private-vlan Display the private-VLAN information for the switch.
[type]
Command Purpose
show interface switchport Display the private-VLAN configuration on interfaces.
show interface private-vlan Display information about the private-VLAN mapping for VLAN SVIs.
mapping
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 Fa1/0/1, Gi1/0/1, Gi1/0/2
10 502 community Fa1/0/11, Gi1/0/1, Gi1/0/4
10 503 non-operational
This chapter describes how to configure the voice VLAN feature on the Catalyst 3750 Metro switch.
Voice VLAN is also referred to as an auxiliary VLAN in some Catalyst 6500 family switch
documentation.
Note For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
Phone
ASIC
P2 PC
P1 3-port P3
switch Access
port
101351
Cisco IP Phone Voice Traffic
You can configure an 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 phone. You can configure access ports on
the switch to send Cisco Discovery Protocol (CDP) packets that instruct an attached Cisco IP Phone to
send voice traffic to the switch in any of these 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).
Note Untagged traffic from the device attached to the Cisco IP Phone passes through the IP phone unchanged,
regardless of the trust state of the access port on the IP phone.
Note Trunk ports can carry any number of voice VLANs, similar to regular VLANs. The configuration of
voice VLANs is not required on trunk ports.
• You cannot configure static secure MAC addresses in the voice VLAN.
• Voice VLAN ports can also be these port types:
– Dynamic access port. See the “Configuring Dynamic-Access Ports on VMPS Clients” section
on page 11-30 for more information.
– 802.1X authenticated port. See the “Configuring IEEE 802.1x Authentication” section on
page 8-13 for more information.
– Protected port. See the “Configuring Protected Ports” section on page 24-6 for more
information.
– A source or destination port for a SPAN or RSPAN session.
– Secure port. See the “Configuring Port Security” section on page 24-8 for more information.
Note When you enable port security on an interface that is also configured with a voice VLAN,
you must set the maximum allowed secure addresses on the port to two plus the maximum
number of secure addresses allowed on the access VLAN. When the port is connected to a
Cisco IP phone, the IP phone requires up to two MAC addresses. The IP phone address is
learned on the voice VLAN and might also be learned on the access VLAN. Connecting a
PC to the IP phone requires additional MAC addresses.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and specify the interface connected to
the IP phone.
Command Purpose
Step 3 mls qos trust cos Configure the interface to classify ingress traffic packets by using the packet
CoS value. For untagged packets, the port default CoS value is used.
Note Before configuring the port trust state, you must first globally enable
QoS by using the mls qos global configuration command.
Step 4 switchport voice vlan {vlan-id | Configure how the Cisco IP Phone carries voice traffic:
dot1p | none | untagged}
• vlan-id—Configure the Cisco IP Phone to forward all voice traffic
through the specified VLAN. By default, the Cisco IP Phone forwards
the voice traffic with an 802.1Q priority of 5. Valid VLAN IDs are from
1 to 4094.
• dot1p—Configure the Cisco IP Phone to use 802.1P priority tagging for
voice traffic and to use the default native VLAN (VLAN 0) to carry all
traffic. By default, the Cisco IP Phone forwards the voice traffic with an
802.1P priority of 5.
• none—Allow the IP phone to use its own configuration to send untagged
voice traffic.
• untagged—Configure the phone to send untagged voice traffic.
Step 5 end Return to privileged EXEC mode.
Step 6 show interfaces interface-id Verify your voice VLAN entries.
switchport or
show running-config interface Verify your QoS and voice VLAN entries.
interface-id
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
This example shows how to configure a port connected to an IP phone to use the CoS value to classify
ingress traffic, to use 802.1P priority tagging for voice traffic, and to use and the default native VLAN
(VLAN 0) to carry all traffic:
Switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# mls qos trust cos
Switch(config-if)# switchport voice vlan dot1p
Switch(config-if)# end
To return the port to its default setting, use the no switchport voice vlan interface configuration
command.
Beginning in privileged EXEC mode, follow these steps to set the priority of data traffic received from
the nonvoice port on the Cisco IP Phone:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and specify the interface connected to the
IP phone.
Step 3 switchport priority extend Set the priority of data traffic received from the IP phone access port:
{cos value | trust}
• cos value—Configure the IP phone to override the priority received from
the PC or the attached device with the specified CoS value. The value is
a number from 0 to 7, with 7 as the highest priority. The default priority
is cos 0.
• trust—Configure the IP phone access port to trust the priority received
from the PC or the attached device.
Step 4 end Return to privileged EXEC mode.
Step 5 show interfaces interface-id Verify your entries.
switchport
Step 6 copy running-config (Optional) Save your entries in the configuration file.
startup-config
This example shows how to configure a port connected to an IP phone to not change the priority of
frames received from the PC or the attached device:
Switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# switchport priority extend trust
Switch(config-if)# end
To return the port to its default setting, use the no switchport priority extend interface configuration
command.
Virtual private networks (VPNs) provide enterprise-scale connectivity on a shared infrastructure, often
Ethernet-based, with the same security, prioritization, reliability, and manageability requirements of
private networks. Tunneling is a feature designed for service providers who carry traffic of multiple
customers across their networks and are required to maintain the VLAN and Layer 2 protocol
configurations of each customer without impacting the traffic of other customers. The
Catalyst 3750 Metro switch supports IEEE 802.1Q tunneling and Layer 2 protocol tunneling, as well as
VLAN mapping (VLAN-ID translation).
Note For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
Note For information about VPNs used with multiprotocol label switching (MPLS), see Chapter 44,
“Configuring MPLS, MPLS VPN, MPLS OAM, and EoMPLS.”
Using the IEEE 802.1Q tunneling feature, service providers can use a single VLAN to support customers
who have multiple VLANs. Customer VLAN IDs are preserved, and traffic from different customers is
segregated within the service-provider infrastructure, even when they appear to be on the same VLAN.
Using IEEE 802.1Q tunneling expands VLAN space by using a VLAN-in-VLAN hierarchy and tagging
the tagged packets. A port configured to support IEEE 802.1Q tunneling is called a tunnel port. When
you configure tunneling, you assign a tunnel port to a VLAN that is dedicated to tunneling. Each
customer requires a separate service-provider VLAN ID, but that VLAN ID supports all of the
customer’s VLANs.
Customer traffic tagged in the normal way with appropriate VLAN IDs come from an IEEE 802.1Q trunk
port on the customer device and into a tunnel port on the service-provider edge switch. The link between
the customer device and the edge switch is an asymmetric link because one end is configured as an
IEEE 802.1Q trunk port and the other end is configured as a tunnel port. You assign the tunnel port
interface to an access VLAN ID that is unique to each customer. See Figure 15-1.
Customer A
VLANs 1 to 100
Customer A
VLANs 1 to 100
802.1Q
802.1Qtrunk
trunkport
port
Service
provider
802.1Q
802.1Q trunk
trunk port
port Tunnel port 802.1Q
802.1Qtrunk
trunkport
port
VLAN 30 Tunnel port
Tunnel port VLAN 30
VLAN 30 Trunk Trunk
ports ports
74016
Customer B Trunk Customer B
VLANs 1 to 200 Asymmetric link VLANs 1 to 200
Packets coming from the customer trunk port into the tunnel port on the service-provider edge switch
are normally IEEE 802.1Q-tagged with the appropriate VLAN ID. The tagged packets remain intact
inside the switch and, when they exit the trunk port into the service-provider network, are encapsulated
with another layer of an IEEE 802.1Q tag (called the metro tag) that contains the VLAN ID that is unique
to the customer. The original IEEE 802.1Q tag from the customer is preserved in the encapsulated
packet. Therefore, packets entering the service-provider infrastructure are double-tagged, with the outer
tag containing the customer’s access VLAN ID, and the inner VLAN ID being the VLAN of the
incoming traffic.
When the double-tagged packet enters another trunk port in a service-provider core switch, the outer tag
is stripped as the packet is processed inside the switch. When the packet exits another trunk port on the
same core switch, the same metro tag is again added to the packet. Figure 15-2 shows the structure of
the double-tagged packet.
Figure 15-2 Normal, IEEE 802.1Q, and Double-Tagged Ethernet Packet Formats
Source
address
Destination Length/ Frame Check
address EtherType Sequence
74072
DA SA Etype Tag Etype Tag Len/Etype Data FCS
Double-tagged
frame in service
provider
infrastructure
When the packet enters the trunk port of the service-provider egress switch, the outer tag is again
stripped as the packet is processed internally on the switch. However, the metro tag is not added when it
is sent out the tunnel port on the edge switch into the customer network, and the packet is sent as a normal
IEEE 802.1Q-tagged frame to preserve the original VLAN numbers in the customer network.
In Figure 15-1, Customer A was assigned VLAN 30, and Customer B was assigned VLAN 40. Packets
entering the edge-switch tunnel ports with IEEE 802.1Q tags are double-tagged when they enter the
service-provider network, with the outer tag containing VLAN ID 30 or 40, appropriately, and the inner
tag containing the original VLAN number, for example, VLAN 100. Even if both Customers A and B
have VLAN 100 in their networks, the traffic remains segregated within the service-provider network
because the outer tag is different. With IEEE 802.1Q tunneling, each customer controls its own VLAN
numbering space, which is independent of the VLAN numbering space used by other customers and the
VLAN numbering space used by the service-provider network.
At the outbound tunnel port, the original VLAN numbers on the customer’s network are recovered. It is
possible to have multiple levels of tunneling and tagging, but the switch supports only one level in this
release.
If the traffic coming from a customer network is not tagged (native VLAN frames), these packets are
bridged or routed as if they were normal packets. All packets entering the service-provider network
through a tunnel port on an edge switch are treated as untagged packets, whether they are untagged or
already tagged with IEEE 802.1Q headers. The packets are encapsulated with the metro tag VLAN ID
(set to the access VLAN of the tunnel port) when they are sent through the service-provider network on
an IEEE 802.1Q trunk port. The priority field on the metro tag is set to the interface class of service
(CoS) priority configured on the tunnel port (the default is zero if none is configured).
The switch supports intelligent IEEE 802.1Q tunneling QoS, or the ability to copy the inner CoS value
to the outer CoS value. For more information, see the “Configuring the Trust State on Ports Within the
QoS Domain” section on page 34-56 and the “Configuring the CoS Value for an Interface” section on
page 34-59.
Note The switch does not support IPv6 features with any ES-port specific features, such as QinQ trust.
Native VLANs
When configuring IEEE 802.1Q tunneling on an edge switch, you must use IEEE 802.1Q trunk ports for
sending out packets into the service-provider network. However, packets going through the core of the
service-provider network might be carried through IEEE 802.1Q trunks, ISL trunks, or nontrunking
links. When IEEE 802.1Q trunks are used in these core switches, the native VLANs of the IEEE 802.1Q
trunks must not match any native VLAN of the nontrunking (tunneling) port on the same switch because
traffic on the native VLAN would not be tagged on the IEEE 802.1Q transmitting trunk port.
See Figure 15-3. VLAN 40 is configured as the native VLAN for the IEEE 802.1Q trunk port from
Customer X at the ingress edge switch in the service-provider network (Switch B). Switch A of
Customer X sends a tagged packet on VLAN 30 to the ingress tunnel port of Switch B in the
service-provider network, which belongs to access VLAN 40. Because the access VLAN of the tunnel
port (VLAN 40) is the same as the native VLAN of the edge switch trunk port (VLAN 40), the metro tag
is not added to tagged packets received from the tunnel port. The packet carries only the VLAN 30 tag
through the service-provider network to the trunk port of the egress edge switch (Switch C) and is
misdirected through the egress switch tunnel port to Customer Y.
Figure 15-3 Potential Problem with IEEE 802.1Q Tunneling and Native VLANs
Switch D
Tag not added Tag Customer X
for VLAN 40 removed VLANs 30-40
Native VLAN 40
Service
provider
Tunnel port
Switch B VLANs 5-50 Switch C VLAN 40
Packet tagged
for VLAN 30 Q Native Q
VLAN 40
Tunnel port Tunnel port
Switch A Access VLAN 40 Access VLAN 30
Customer X
802.1Q
trunk port
VLANs 30-40 Switch E
Native VLAN 40 Customer Y
Trunk
Asymmetric link
Correct path for traffic
Incorrect path for traffic due to
misconfiguration of native VLAN
101820
by sending port on Switch B
Q = 802.1Q trunk ports
System MTU
The default system MTU for traffic on the Catalyst 3750 Metro switch is 1500 bytes. You can configure
Fast Ethernet ports to support frames larger than 1500 bytes by using the system mtu global
configuration command. You can configure Gigabit Ethernet ports to support frames larger than 1500
bytes by using the system mtu jumbo global configuration command. Because the IEEE 802.1Q
tunneling feature increases the frame size by 4 bytes when the metro tag is added, you must configure
all switches in the service-provider network to be able to process maximum frames by increasing the
switch system MTU size to at least 1504 bytes. The maximum allowable system MTU for Gigabit
Ethernet interfaces is 9000 bytes; the maximum system MTU for Fast Ethernet interfaces is 1998 bytes.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode and the interface to be configured as
a tunnel port. This should be the edge port in the service-provider network
that connects to the customer switch. Valid interfaces include physical
interfaces and port-channel logical interfaces (port channels 1 to 12).
Step 3 switchport access vlan vlan-id Specify the default VLAN, which is used if the interface stops trunking.
This VLAN ID is specific to the particular customer.
Command Purpose
Step 4 switchport mode dot1q-tunnel Set the interface as an IEEE 802.1Q tunnel port.
Step 5 exit Return to global configuration mode.
Step 6 vlan dot1q tag native (Optional) Set the switch to enable tagging of native VLAN packets on all
IEEE 802.1Q trunk ports. When not set, if a customer VLAN ID is the
same as the native VLAN, the trunk port does not apply a metro tag, and
packets might be sent to the wrong destination.
Step 7 end Return to privileged EXEC mode.
Step 8 show dot1q-tunnel Display the tunnel ports on the switch.
Step 9 show vlan dot1q tag native Display IEEE 802.1Q native VLAN tagging status.
Step 10 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no switchport mode dot1q-tunnel interface configuration command to return the port to the
default state of dynamic auto. Use the no vlan dot1q tag native global configuration command to
disable tagging of native VLAN packets.
This example shows how to configure a port as a tunnel port, enable tagging of native VLAN packets,
and verify the configuration. In this configuration, the VLAN ID for the customer connected to Fast
Ethernet port 7 is VLAN 22.
Switch(config)# interface fastethernet1/0/7
Switch(config-if)# switchport access vlan 22
% Access VLAN does not exist. Creating vlan 22
Switch(config-if)# switchport mode dot1q-tunnel
Switch(config-if)# exit
Switch(config)# vlan dot1q tag native
Switch(config)# end
Switch# show dot1q-tunnel interface fastethernet1/0/7
Port
-----
Fa1/0/7
-----
Switch# show vlan dot1q tag native
dot1q native vlan tagging is enabled
Note Do not configure VLAN mapping on an interface configured for MPLS or EoMPLS.
Host
Customer A
VLANs 1-5
Service provider Customer A
Catalyst 3750 Catalyst 3750 VLANs 1-5
Metro switch A Metro switch B
Customer
switches
Catalyst Customer
6500 switch
Customer A
VLANs 1-5 Access, ISL, Access, ISL,
or 802.1Q trunk or 802.1Q trunk
Host
101101
VLAN mapping at
enhanced services ports
Beginning in privileged EXEC mode, follow these steps on an ES port to map a customer VLAN ID to
a service-provider VLAN ID:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode and the ES interface connected to the
service-provider network.
Step 3 switchport vlan mapping vlan-id Enter the VLAN IDs to be mapped:
translated-id
• vlan-id—the customer VLAN ID entering the switch from the
customer network. The range is from 1 to 4094.
• translated-id—the assigned service-provider VLAN ID. The range is
from 1 to 4094.
Step 4 end Return to privileged EXEC mode.
Step 5 show vlan mapping Verify the configuration.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no switchport vlan mapping vlan-id translated-id command to remove the VLAN translation
information.
This example shows how to map VLAN IDs 1, 2, 3, 4, and 5 in the customer network to VLANs 2001,
2002, 2003, and 2004 in the service-provider network as shown in Figure 15-4. You configure these same
VLAN mapping commands for an ES port in Switch A and Switch B.
Switch(config)# interface gigabiethernet1/1/1
Switch(config-if)# switchport vlan mapping 1 1001
Switch(config-if)# switchport vlan mapping 2 1002
Switch(config-if)# switchport vlan mapping 3 1003
Switch(config-if)# switchport vlan mapping 4 1004
Switch(config-if)# switchport vlan mapping 5 1005
Switch(config-if)# exit
In the previous example, at the ingress of the service-provider network, VLAN IDs 1, 2, 3, 4, and 5 in
the customer network are mapped to VLANs 2001, 2002, 2003, and 2004 in the service-provider
network. At the egress of the service-provider network, VLANs 2001, 2002, 2003, and 2004 in the
service-provider network are mapped to VLAN IDs 1, 2, 3, 4, and 5 in the customer network.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode and the ES interface connected to the
service-provider network.
Step 3 switchport vlan mapping dot1q-tunnel Configure the VLAN mapping as a two-to-one mapping, and specify the
outer-vlan-id {inner-vlan-id action to be taken if the outer VLAN ID of the original IEEE 802.1Q
translated-vlan-id | drop} packet matches the specified value:
• outer-vlan-id—Enter the outer VLAN ID of the original IEEE
802.1Q packet. The VLAN ID range is from 1 to 4094.
• inner-vlan-id translated-vlan-id—Enter the inner VLAN ID of the
original IEEE 802.1Q packet and the translated VLAN ID for the
service-provider network. The VLAN ID range is from 1 to 4094.
• drop—Specify that traffic with the specified outer VLAN ID is
dropped unless the inner VLAN ID is matched in the existing VLAN
mappings.
Command Purpose
Step 4 switchport vlan mapping internal Configure the VLAN mapping as a two-to-two mapping, and specify the
dot1q-tunnel internal-outer-vlan-id outer and inner VLAN IDs to be mapped:
internal-inner-vlan-id external
• internal-outer-vlan-id—Enter the outer VLAN ID of the original
dot1q-tunnel external-outer-vlan-id
IEEE 802.1Q packet.
external-inner-vlan-id
• internal-inner-vlan-id—Enter the inner VLAN ID of the original
IEEE 802.1Q packet.
• external-outer-vlan-id—Enter the outer VLAN ID of the
service-provider network.
• external-inner-vlan-id—Enter the inner VLAN ID of the
service-provider network.
The VLAN ID range is from 1 to 4094.
Note The inner VLAN ID of the service-provider network must match
that of the original IEEE 802.1Q packet.
Step 5 end Return to privileged EXEC mode.
Step 6 show vlan mapping Verify the configuration.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
This example shows how to configure a two-to-two mapping on the ES port so that IEEE 802.1Q traffic
with the outer VLAN ID 5 and the inner VLAN ID 6 would leave the switch with the outer VLAN ID
15 and the inner VLAN ID 16:
Switch(config)# interface gigabitethernet1/1/1
Switch(config-if)# switchport vlan mapping internal dot1q-tunnel 5 6 external dot1q tunnel
15 6
See this document for a description of IEEE 802.1ad support on Cisco provider bridges with commands:
http://www.cisco.com/en/US/docs/ios/cether/configuration/guide/ce_cfm-ieee_802_1ad.html
The Catalyst 3750 Metro switch supports these IEEE 802.1ad features:
• a switchport-based model
• all-to-one bundling
• service multiplexing (complex UNI)
In 802.1ad, a switchport is configured as either a customer user-network interface (C-UNI), a
service-provider UNI (S-UNI), or a network-to-network interface (NNI). Only Layer 2 interfaces can be
802.1ad ports.
• C-UNI—can be either an access port or an 802.1Q trunk port. The port uses the customer bridge
addresses. To configure a C-UNI port, enter the ethernet dot1ad uni c-port interface configuration
command. New keywords added to the switchport vlan mapping interface configuration command
allow all-to-one or selective bundling capability for customer VLANs when the interface is
configured as an 802.1ad trunk C-UNI port.
On a Catalyst 3750 Metro switch, you cannot configure an ES port as a C-UNI port.
• S-UNI—an access port that provides the same service to all customer VLANs entering the interface,
marking all C-VLANs entering the port with the same S-VLAN. In this mode, the customer’s port
is configured as a trunk port, and traffic entering the S-UNI is tagged. On S-UNIs, CDP and LLDP
are disabled, and STP BPDU filtering and Port Fast are enabled. You can configure the port as an
access port only; trunk configuration is not allowed.
– CFM C-VLAN configuration is not allowed on an S-UNI.
– You enter the ethernet dot1ad uni s-port interface configuration command to configure the
port in dot1q-tunnel mode. You cannot configure an ES port as an S-UNI.
• NNI—entering the ethernet dot1ad nni interface command on a trunk port creates 802.1ad
EtherType (0x88a8) and uses S-bridge addresses for CPU-generated Layer 2 protocol PDUs. Only
trunk ports can be NNIs. CFM C-VLAN configuration is not allowed on an NNI.
Note On a Catalyst 3750 Metro switch, you can configure 802.1ad NNIs only on ES ports. Non-ES
ports can be configured as C-UNIs or S-UNIs.
See the command reference for more information on commands that support 802.1ad.
Customer A1 Customer A3
Po23 Po23
(F1/0/2-4) (F1/0/21-23)
PE3
Gi1/1/1 Gi1/1/2
Gi0/13 Gi0/9
Gi0/10
Gi0/2 PE2 Gi0/11
Gi0/3 Gi0/10
Gi0/4 Po41
Gi0/5
PE1 Provider (Gi0/5-7)
Gi0/6 cloud
Gi0/2
Gi0/7 Gi0/13
Gi0/3
PE5 Gi0/4
GGi0/15
PE4
Gi1/1/1 Gi1/1/2
Po14 Po14
(Gi0/5-7) (Fa0/2-4)
207483
Customer D1 Customer D2
Configuration on PE-1:
Switch (config)# interface GigabitEthernet0/2
Switch (config-if)# switchport access vlan 4002
Switch (config-if)# ethernet dot1ad uni s-port
Configuration on PE-3
Switch (config)# interface GigabitEthernet1/1/1
Switch (config-if)# switchport trunk allowed vlan 4001-4094
Switch (config-if)# switchport mode trunk
Switch (config-if)# switchport trunk dot1q ethertype 88A8
Switch (config-if)# udld port aggressive
Switch (config-if)# ethernet dot1ad nni
Configuration on PE-2
Switch (config)# interface GigabitEthernet0/9
Switch (config-if)# switchport access vlan 4002
Switch (config-if)# ethernet dot1ad uni s-port
Configuration on Customer A3
Switch (config)# interface Port-channel23
Switch (config-if)# switchport trunk encapsulation dot1q
Switch (config-if)# switchport mode trunk
The configuration on other switches remains the same in the 802.1ad C-UNI scenario.
Note To provide interoperability with third-party vendors, you can use the Layer 2 protocol-tunnel bypass
feature. Bypass mode transparently forwards control PDUs to vendor switches that have different ways
of controlling protocol tunneling. You implement bypass mode by enabling Layer 2 protocol tunneling
on the egress trunk port. When Layer 2 protocol tunneling is enabled on the trunk port, the encapsulated
tunnel MAC address is removed and the protocol packets have their normal MAC address.
Layer 2 protocol tunneling can be used independently or can enhance IEEE 802.1Q tunneling. If protocol
tunneling is not enabled on IEEE 802.1Q tunneling ports, remote switches at the receiving end of the
service-provider network do not receive the PDUs and cannot properly run STP, CDP, and VTP. When
protocol tunneling is enabled, Layer 2 protocols within each customer’s network are totally separate
from those running within the service-provider network. Customer switches on different sites that send
traffic through the service-provider network with IEEE 802.1Q tunneling achieve complete knowledge
of the customer’s VLAN. If IEEE 802.1Q tunneling is not used, you can still enable Layer 2 protocol
tunneling by connecting to the customer switch through access ports or trunk ports and enabling
tunneling on the service-provider access or trunk port.
For example, in Figure 15-6, Customer X has four switches in the same VLAN that are connected
through the service-provider network. If the network does not tunnel PDUs, switches on the far ends of
the network cannot properly run STP, CDP, and VTP. For example, STP for a VLAN on a switch in
Customer X’s Site 1 will build a spanning tree on the switches at that site without considering
convergence parameters based on Customer X’s switch in Site 2. This could result in the topology shown
in Figure 15-7.
Customer X Site 1
VLANs 1 to 100
Customer X Site 2
VLANs 1 to 100
VLAN 30 Service
provider
VLAN 30
VLAN 30
Trunk Trunk
ports ports
Switch A Switch C
Switch B Switch D
Trunk Trunk
ports ports
VLAN 40 VLAN 40
101822
Trunk
Customer Y Site 1 Asymmetric link
VLANs 1 to 200 Customer Y Site 2
VLANs 1 to 200
Customer X
virtual network
VLANs 1 to 100
101821
In a service-provider network, you can use Layer 2 protocol tunneling to enhance the creation of
EtherChannels by emulating a point-to-point network topology. When you enable protocol tunneling
(PAgP or LACP) on the service-provider switch, remote customer switches receive the PDUs and can
negotiate the automatic creation of EtherChannels.
For example, in Figure 15-8, Customer A has two switches in the same VLAN that are connected
through the SP network. When the network tunnels PDUs, switches on the far ends of the network can
negotiate the automatic creation of EtherChannels without needing dedicated lines. See the “Configuring
Layer 2 Tunneling for EtherChannels” section on page 15-23 for instructions on configuring Layer 2
protocol tunneling for EtherChannels.
VLAN 17 VLAN 17
Customer A Customer A
Site 1 Site 2
VLAN 18 Switch A Switch C VLAN 18
VLAN 19 VLAN 19
101844
VLAN 20 VLAN 20
Switch B Switch D
Trunk
Asymmetric link
Caution PAgP, LACP, and UDLD protocol tunneling is only intended to emulate a point-to-point topology. An
erroneous configuration that sends tunneled packets to many ports could lead to a network failure.
When the Layer 2 PDUs that entered the inbound edge switch through a Layer 2 protocol-enabled port
exit the switch through the trunk port into the service-provider network, the switch overwrites the
customer PDU-destination MAC address with a well-known Cisco proprietary multicast address
(01-00-0c-cd-cd-d0). If IEEE 802.1Q tunneling is enabled, packets are also double-tagged; the outer tag
is the customer metro tag and the inner tag is the customer VLAN tag. The core switches ignore the inner
tags and forward the packet to all trunk ports in the same metro VLAN. The edge switches on the
outbound side restore the proper Layer 2 protocol and MAC address information and forward the packets
to all tunnel ports, access ports, and Layer 2 protocol-enabled trunk ports in the same metro VLAN.
Therefore, the Layer 2 PDUs are kept intact and delivered across the service-provider infrastructure to
the other side of the customer network.
See Figure 15-6, with Customer X and Customer Y in access VLANs 30 and 40, respectively.
Asymmetric links connect the customers in Site 1 to edge switches in the service-provider network. The
Layer 2 PDUs (for example, BPDUs) coming into Switch B from Customer Y in Site 1 are forwarded to
the infrastructure as double-tagged packets with the well-known MAC address as the destination MAC
address. These double-tagged packets have the outer VLAN tag of 40 as well as an inner VLAN tag (for
example, VLAN 100). When the double-tagged packets reach Switch D, the outer VLAN tag 40 is
removed, the well-known MAC address is replaced with the respective Layer 2 protocol MAC address,
and the packet is sent to Customer Y on Site 2 as a single-tagged frame in VLAN 100.
You can also enable Layer 2 protocol tunneling on access or trunk ports on the edge switch connected
to access or trunk ports on the customer switch. In this case, the encapsulation and de-encapsulation
behavior is the same as described in the previous paragraph, except that the packets are not
double-tagged in the service-provider network. The single tag is the customer-specific access VLAN tag.
This section contains this information about configuring Layer 2 protocol tunneling:
• Default Layer 2 Protocol Tunneling Configuration, page 15-20
• Layer 2 Protocol Tunneling Configuration Guidelines, page 15-20
• Configuring Layer 2 Tunneling, page 15-22
• Configuring Layer 2 Tunneling for EtherChannels, page 15-23
• If you enable PAgP or LACP tunneling, we recommend that you also enable UDLD on the interface
for faster link-failure detection.
• Loopback detection is not supported on Layer 2 protocol tunneling of PAgP, LACP, or UDLD
packets.
• Dynamic Trunking Protocol (DTP) is not compatible with Layer 2 protocol tunneling because you
must manually configure asymmetric links with tunnel ports and trunk ports.
• The edge switches on the outbound side restore the proper Layer 2 protocol and MAC address
information and forward the packets to all tunnel ports, access ports and Layer 2 protocol-enabled
trunk ports in the same metro VLAN.
• For interoperability with third-party vendor switches, the switch supports a Layer 2 protocol-tunnel
bypass feature. Bypass mode transparently forwards control PDUs to vendor switches that have
different ways of controlling protocol tunneling.When Layer 2 protocol tunneling is enabled on
ingress ports on a switch, egress trunk ports forward the tunneled packets with a special
encapsulation. If you also enable Layer 2 protocol tunneling on the egress trunk port, this behavior
is bypassed and the switch forwards control PDUs without any processing or modification.
• EtherChannel port groups are compatible with tunnel ports as long as the IEEE 802.1Q
configuration is consistent within an EtherChannel port group.
• If an encapsulated PDU (with the proprietary destination MAC address) is received from a tunnel
port or access or trunk port with Layer 2 tunneling enabled, the port is shut down to prevent loops.
The port also shuts down when a configured shutdown threshold for the protocol is reached. You can
manually re-enable the port (by entering a shutdown and no shutdown command sequence) or if
errdisable recovery is enabled, the operation is retried after a specified time interval.
• Only decapsulated PDUs are forwarded to the customer network. The spanning-tree instance
running on the service-provider network does not forward BPDUs to tunnel ports. No CDP packets
are forwarded from tunnel ports.
• When protocol tunneling is enabled on an interface, you can set a per-protocol, per-port, shutdown
threshold for the PDUs generated by the customer network. If the limit is exceeded, the port shuts
down. You can also rate-limit BPDUs by using QoS ACLs and policy maps on a tunnel port.
• When protocol tunneling is enabled on an interface, you can set a per-protocol, per-port, drop
threshold for the PDUs generated by the customer network. If the limit is exceeded, the port drops
PDUs until the rate at which the port receives them is below the drop threshold.
• Because tunneled PDUs (especially STP BPDUs) must be delivered to all remote sites for the
customer virtual network to operate properly, you can give PDUs higher priority within the
service-provider network than data packets received from the same tunnel port. By default, the
PDUs use the same CoS value as data packets.
• Protocol tunneling for LLDP is supported beginning with Cisco IOS Release 12.2(58)SE.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter the interface configuration mode and the interface to be configured as
a tunnel port. This should be the edge port in the service-provider network
that connects to the customer switch. Valid interfaces include physical
interfaces and port-channel logical interfaces (port channels 1 to 12).
Step 3 switchport mode access Configure the interface as an access port, an IEEE 802.1Q tunnel port or a
or trunk port.
switchport mode dot1q-tunnel
or
switchport mode trunk
Step 4 l2protocol-tunnel [cdp | lldp | stp | Enable protocol tunneling for the desired protocol. If no keyword is entered,
vtp] tunneling is enabled for all three Layer 2 protocols.
Step 5 l2protocol-tunnel (Optional) Configure the threshold in packets per second to be received for
shutdown-threshold [cdp | stp | vtp] encapsulation before the interface shuts down. The port is disabled if the
value configured threshold is exceeded. If no protocol option is specified, the
threshold is applied to each of the tunneled Layer 2 protocol types. The
range is 1 to 4096. The default is to have no threshold configured.
Note If you also set a drop threshold on this interface, the
shutdown-threshold value must be greater than or equal to the
drop-threshold value.
Step 6 l2protocol-tunnel drop-threshold (Optional) Configure the threshold in packets per second to be received for
[cdp | lldp | stp | vtp] value encapsulation before the interface drops packets. The port drops packets if
the configured threshold is exceeded. If no protocol option is specified, the
threshold is applied to each of the tunneled Layer 2 protocol types. The
range is 1 to 4096. The default is to have no threshold configured.
Note If you also set a shutdown threshold on this interface, the
drop-threshold value must be less than or equal to the
shutdown-threshold value.
Step 7 exit Return to global configuration mode.
Step 8 errdisable recovery cause l2ptguard (Optional) Configure the recovery mechanism from a Layer 2 maximum
rate error so that the interface can be brought out of the disabled state and
allowed to try again. You can also set the time interval. Errdisable recovery
is disabled by default; when enabled, the default time interval is 300
seconds.
Step 9 l2protocol-tunnel cos value (Optional) Configure the CoS value for all tunneled Layer 2 PDUs. The
range is 0 to 7; the default is the default CoS value for the interface. If none
is configured, the default is 5.
Step 10 end Return to privileged EXEC mode.
Command Purpose
Step 11 show l2protocol Display the Layer 2 tunnel ports on the switch, including the protocols
configured, the threshold, and the counters.
Step 12 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no l2protocol-tunnel [cdp | lldp | stp | vtp] interface configuration command to disable protocol
tunneling for one of the Layer 2 protocols or for all three of them. Use the no l2protocol-tunnel
shutdown-threshold [cdp | lldp | stp | vtp] and the no l2protocol-tunnel drop-threshold [cdp | lldp |
stp | vtp] commands to return the shutdown and drop thresholds to the default settings.
This example shows how to configure Layer 2 protocol tunneling for CDP, STP, and VTP and to verify
the configuration.
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# l2protocol-tunnel cdp
Switch(config-if)# l2protocol-tunnel stp
Switch(config-if)# l2protocol-tunnel vtp
Switch(config-if)# l2protocol-tunnel shutdown-threshold 1500
Switch(config-if)# l2protocol-tunnel drop-threshold 1000
Switch(config-if)# exit
Switch(config)# l2protocol-tunnel cos 7
Switch(config)# end
Switch# show l2protocol
COS for Encapsulated Packets: 7
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and enter the interface to be configured
as a tunnel port. This should be the edge port in the service-provider
network that connects to the customer switch. Valid interfaces are physical
interfaces.
Step 3 switchport mode dot1q-tunnel Configure the interface as an IEEE 802.1Q tunnel port.
Command Purpose
Step 4 l2protocol-tunnel point-to-point Enable point-to-point protocol tunneling for the desired protocol. If no
[pagp | lacp | udld] keyword is entered, tunneling is enabled for all three protocols.
Use the no l2protocol-tunnel [point-to-point [pagp | lacp | udld]] interface configuration command to
disable point-to-point protocol tunneling for one of the Layer 2 protocols or for all three. Use the no
l2protocol-tunnel shutdown-threshold [point-to-point [pagp | lacp | udld]] and the no
l2protocol-tunnel drop-threshold [[point-to-point [pagp | lacp | udld]] commands to return the
shutdown and drop thresholds to the default settings.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter the interface configuration mode. This should be the customer switch
port.
Step 3 switchport trunk encapsulation Set the trunking encapsulation format to IEEE 802.1Q.
dot1q
Note Beginning with Cisco IOS Release 12.2(22)EY, this step is not
required on ES ports. Because ES ports support only IEEE 802.1Q
trunking, the encapsulation keyword is not visible.
Step 4 switchport mode trunk Enable trunking on the interface.
Step 5 udld enable Enable UDLD in normal mode on the interface.
Step 6 channel-group channel-group-number Assign the interface to a channel group, and specify desirable for the PAgP
mode desirable mode. For more information about configuring EtherChannels, see
Chapter 35, “Configuring EtherChannels and Link-State Tracking.”
Step 7 exit Return to global configuration mode.
Step 8 interface port-channel port-channel Enter port-channel interface mode.
number
Step 9 shutdown Shut down the interface.
Step 10 no shutdown Enable the interface.
Step 11 end Return to privileged EXEC mode.
Step 12 show l2protocol Display the Layer2 tunnel ports on the switch, including the protocols
configured, the thresholds, and the counters.
Step 13 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no switchport mode trunk, the no udld enable, and the no channel group
channel-group-number mode desirable interface configuration commands to return the interface to the
default settings.
For EtherChannels, you need to configure both the service-provider edge switches and the customer
switches for Layer 2 protocol tunneling.
This example shows how to configure the service provider edge Switch A and edge Switch B in the
example in Figure 15-8 on page 15-19. VLANs 17, 18, 19, and 20 are the access VLANs, Fast Ethernet
ports 1 and 2 are point-to-point tunnel ports with PAgP and UDLD enabled, the drop threshold is 1000,
and Fast Ethernet port 3 is a trunk port.
Service-provider edge Switch A configuration:
Switch(config)# interface fastethernet1/0/1
Switch(config-if)# switchport access vlan 17
Switch(config-if)# switchport mode dot1q-tunnel
Switch(config-if)# l2protocol-tunnel point-to-point pagp
Switch(config-if)# l2protocol-tunnel point-to-point udld
Switch(config-if)# l2protocol-tunnel drop-threshold point-to-point pagp 1000
Switch(config-if)# exit
Switch(config)# interface fastethernet1/0/2
This example shows how to configure the customer switch at Site 1. Fast Ethernet ports 1, 2, 3, and 4 are
set for IEEE 802.1Q trunking, UDLD is enabled, EtherChannel group 1 is enabled, and the port channel
is shut down and then enabled to activate the EtherChannel configuration.
Switch(config)# interface fastethernet1/0/1
Switch(config-if)# switchport trunk encapsulation dot1q
Switch(config-if)# switchport mode trunk
Switch(config-if)# udld enable
Switch(config-if)# channel-group 1 mode desirable
Switch(config-if)# exit
Switch(config)# interface fastethernet1/0/2
Switch(config-if)# switchport trunk encapsulation dot1q
Switch(config-if)# switchport mode trunk
Switch(config-if)# udld enable
Switch(config-if)# channel-group 1 mode desirable
Switch(config-if)# exit
Switch(config)# interface fastethernet1/0/3
Switch(config-if)# switchport trunk encapsulation dot1q
Switch(config-if)# switchport mode trunk
Switch(config-if)# udld enable
Switch(config-if)# channel-group 1 mode desirable
Switch(config-if)# exit
Switch(config)# interface fastethernet1/0/4
Switch(config-if)# switchport trunk encapsulation dot1q
Switch(config-if)# switchport mode trunk
Switch(config-if)# udld enable
Switch(config-if)# channel-group 1 mode desirable
Switch(config-if)# exit
Switch(config)# interface port-channel 1
Switch(config-if)# shutdown
Switch(config-if)# no shutdown
Switch(config-if)# exit
Table 15-2 Commands for Monitoring and Maintaining Tunneling and VLAN Mapping
Command Purpose
clear l2protocol-tunnel counters Clear the protocol counters on Layer 2 protocol tunneling ports.
show dot1q-tunnel Display IEEE 802.1Q tunnel ports on the switch.
show dot1q-tunnel interface interface-id Verify if a specific interface is a tunnel port.
show l2protocol-tunnel Display information about Layer 2 protocol tunneling ports.
show errdisable recovery Verify if the recovery timer from a Layer 2 protocol-tunnel error disable state
is enabled.
show interface interface-id vlan mapping Display VLAN mapping information for the specified interface. The interface
can be an ES port or a VLAN.
show l2protocol-tunnel interface Display information about a specific Layer 2 protocol tunneling port.
interface-id
show l2protocol-tunnel summary Display only Layer 2 protocol summary information.
show vlan dot1q native Display the status of native VLAN tagging on the switch.
show vlan mapping Display VLAN mapping information (contents of the VLAN mapping table)
for the ES ports.
For detailed information about these displays, see the command reference for this release.
This chapter describes how to configure the Spanning Tree Protocol (STP) on port-based VLANs on the
Catalyst 3750 Metro switch. The switch uses the per-VLAN spanning-tree plus (PVST+) protocol based
on the IEEE 802.1D standard and Cisco proprietary extensions, or it can use the rapid per-VLAN
spanning-tree plus (rapid-PVST+) protocol based on the IEEE 802.1w standard.
For information about the Multiple Spanning Tree Protocol (MSTP) and how to map multiple VLANs
to the same spanning-tree instance, see Chapter 17, “Configuring MSTP.” For information about other
spanning-tree features such as Port Fast, UplinkFast, root guard, and so forth, see Chapter 18,
“Configuring Optional Spanning-Tree Features.”
Note For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
STP Overview
STP is a Layer 2 link management protocol that provides path redundancy while preventing loops in the
network. For a Layer 2 Ethernet network to function properly, only one active path can exist between
any two stations. Multiple active paths among end stations cause loops in the network. If a loop exists
in the network, end stations might receive duplicate messages. Switches might also learn end-station
MAC addresses on multiple Layer 2 interfaces. These conditions result in an unstable network.
Spanning-tree 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.
The STP uses a spanning-tree algorithm to select one switch of a redundantly connected network as the
root of the spanning tree. The algorithm calculates the best loop-free path through a switched Layer 2
network by assigning a role to each port based on the role of the port in the active topology:
• Root—A forwarding port elected for the spanning-tree topology
• Designated—A forwarding port elected for every switched LAN segment
• Alternate—A blocked port providing an alternate path to the root bridge in the spanning tree
• Backup—A blocked port in a loopback configuration
The switch that has all of its ports as the designated role or as the backup role is the root switch. The
switch that has at least one of its ports in the designated role is called the designated switch.
Spanning tree forces redundant data paths into a standby (blocked) state. If a network segment in the
spanning tree fails and a redundant path exists, the spanning-tree algorithm recalculates the
spanning-tree topology and activates the standby path. Switches send and receive spanning-tree frames,
called bridge protocol data units (BPDUs), at regular intervals. The switches do not forward these frames
but use them to construct a loop-free path. BPDUs contain information about the sending switch and its
ports, including switch and MAC addresses, switch priority, port priority, and path cost. Spanning tree
uses this information to elect the root switch and root port for the switched network and the root port and
designated port for each switched segment.
When two ports on a switch are part of a loop, the spanning-tree port priority and path cost settings
control which port is put in the forwarding state and which is put in the blocking state. The spanning-tree
port priority value represents the location of a port in the network topology and how well it is located to
pass traffic. The path cost value represents the media speed.
Note In Cisco IOS Release 12.2(25)EY and later releases, the switch sends keepalive messages (to ensure the
connection is up) only on interfaces that do not have small form-factor pluggable (SFP) modules.
Switch Priority Value Extended System ID (Set Equal to the VLAN ID)
Bit 16 Bit 15 Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9 Bit 8 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1
32768 16384 8192 4096 2048 1024 512 256 128 64 32 16 8 4 2 1
Spanning tree uses the extended system ID, the switch priority, and the allocated spanning-tree MAC
address to make the bridge ID unique for each VLAN.
Support for the extended system ID affects how you manually configure the root switch, the secondary
root switch, and the switch priority of a VLAN. For example, when you change the switch priority value,
you change the probability that the switch will be elected as the root switch. Configuring a higher value
decreases the probability; a lower value increases the probability. For more information, see the
“Configuring the Root Switch” section on page 16-14, the “Configuring a Secondary Root Switch”
section on page 16-16, and the “Configuring the Switch Priority of a VLAN” section on page 16-19.
Power-on
initialization
Blocking
state
Listening Disabled
state state
Learning
state
Forwarding
43569
state
When you power up the switch, spanning tree is enabled by default, and every interface in the switch,
VLAN, or network goes through the blocking state and the transitory states of listening and learning.
Spanning tree stabilizes each interface at the forwarding or blocking state.
When the spanning-tree algorithm places a Layer 2 interface in the forwarding state, this process occurs:
1. The interface is in the listening state while spanning tree waits for protocol information to transition
the interface to the blocking state.
2. While spanning tree waits the forward-delay timer to expire, it moves the interface to the learning
state and resets the forward-delay timer.
3. In the learning state, the interface continues to block frame forwarding as the switch learns
end-station location information for the forwarding database.
4. When the forward-delay timer expires, spanning tree moves the interface to the forwarding state,
where both learning and frame forwarding are enabled.
Blocking State
A Layer 2 interface in the blocking state does not participate in frame forwarding. After initialization, a
BPDU is sent to each switch interface. A switch initially functions as the root until it exchanges BPDUs
with other switches. This exchange establishes which switch in the network is the root or root switch. If
there is only one switch in the network, no exchange occurs, the forward-delay timer expires, and the
interface moves to the listening state. An interface always enters the blocking state after switch
initialization.
An interface in the blocking state performs these functions:
• Discards frames received on the interface
• Discards frames switched from another interface for forwarding
• Does not learn addresses
• Receives BPDUs
Listening State
The listening state is the first state a Layer 2 interface enters after the blocking state. The interface enters
this state when the spanning tree determines that the interface should participate in frame forwarding.
An interface in the listening state performs these functions:
• Discards frames received on the interface
• Discards frames switched from another interface for forwarding
• Does not learn addresses
• Receives BPDUs
Learning State
A Layer 2 interface in the learning state prepares to participate in frame forwarding. The interface enters
the learning state from the listening state.
An interface in the learning state performs these functions:
• Discards frames received on the interface
• Discards frames switched from another interface for forwarding
• Learns addresses
• Receives BPDUs
Forwarding State
A Layer 2 interface in the forwarding state forwards frames. The interface enters the forwarding state
from the learning state.
An interface in the forwarding state performs these functions:
• Receives and forwards frames received on the interface
• Forwards frames switched from another interface
• Learns addresses
• Receives BPDUs
Disabled State
A Layer 2 interface in the disabled state does not participate in frame forwarding or in the spanning tree.
An interface in the disabled state is nonoperational.
A disabled interface performs these functions:
• Discards frames received on the interface
• Discards frames switched from another interface for forwarding
• Does not learn addresses
• Does not receive BPDUs
DP
DP DP
A D
DP RP
RP RP DP
86475
B C
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 an interface that has a higher number than the 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 Gigabit Ethernet link and that another port on
Switch B (a 10/100 link) is the root port. Network traffic might be more efficient over the Gigabit
Ethernet link. By changing the spanning-tree port priority on the Gigabit Ethernet port to a higher
priority (lower numerical value) than the root port, the Gigabit Ethernet port becomes the new root port.
Active link
101226
Blocked link
Workstations
You can also create redundant links between switches by using EtherChannel groups. For more
information, see the Chapter 35, “Configuring EtherChannels and Link-State Tracking.”
Because each VLAN is a separate spanning-tree instance, the switch accelerates aging on a per-VLAN
basis. A spanning-tree reconfiguration on one VLAN can cause the dynamic addresses learned on that
VLAN to be subject to accelerated aging. Dynamic addresses on other VLANs can be unaffected and
remain subject to the aging interval entered for the switch.
In a mixed MSTP and PVST+ network, the common spanning-tree (CST) root must be inside the MST
backbone, and a PVST+ switch cannot connect to multiple MST regions.
When a network contains switches running rapid PVST+ and switches running PVST+, we recommend
that the rapid-PVST+ switches and PVST+ switches be configured for different spanning-tree instances.
In the rapid-PVST+ spanning-tree instances, the root switch must be a rapid-PVST+ switch. In the
PVST+ instances, the root switch must be a PVST+ switch. The PVST+ switches should be at the edge
of the network.
To support VLAN-bridge spanning tree, some of the spanning-tree timers are increased. To use the
fallback bridging feature, you must have the enhanced multilayer software image installed on your
switch. For more information, see Chapter 47, “Configuring Fallback Bridging.”
Caution Switches that are not running spanning tree still forward BPDUs that they receive so that the other
switches on the VLAN that have a running spanning-tree instance can break loops. Therefore, spanning
tree must be running on enough switches to break all the loops in the network; for example, at least one
switch on each loop in the VLAN must be running spanning tree. It is not absolutely necessary to run
spanning tree on all switches in the VLAN. However, if you are running spanning tree only on a minimal
set of switches, an incautious change to the network that introduces another loop into the VLAN can
result in a broadcast storm.
Note If you have already used all available spanning-tree instances on your switch, adding another VLAN
anywhere in the VTP domain creates a VLAN that is not running spanning tree on that switch. If you
have the default allowed list on the trunk ports of that switch, the new VLAN is carried on all trunk ports.
Depending on the topology of the network, this could create a loop in the new VLAN that will not be
broken, particularly if there are several adjacent switches that have all run out of spanning-tree instances.
You can prevent this possibility by setting up allowed lists on the trunk ports of switches that have used
up their allocation of spanning-tree instances. Setting up allowed lists is not necessary in many cases and
can make it more labor-intensive to add another VLAN to the network.
Spanning-tree commands control the configuration of VLAN spanning-tree instances. You create a
spanning-tree instance when you assign an interface to a VLAN. The spanning-tree instance is removed
when the last interface is moved to another VLAN. You can configure switch and port parameters before
a spanning-tree instance is created; these parameters are applied when the spanning-tree instance is
created.
The switch supports PVST+, rapid PVST+, and MSTP, but only one version can be active at any time.
(For example, all VLANs run PVST+, all VLANs run rapid PVST+, or all VLANs run MSTP.) For
information about the different spanning-tree modes and how they interoperate, see the “Spanning-Tree
Interoperability and Backward Compatibility” section on page 16-10.
For configuration guidelines about UplinkFast and BackboneFast, see the “Optional Spanning-Tree
Configuration Guidelines” section on page 18-10.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 spanning-tree mode {pvst | mst | Configure a spanning-tree mode.
rapid-pvst}
• Select pvst to enable PVST+ (the default setting).
• Select mst to enable MSTP (and RSTP). For more configuration
steps, see Chapter 17, “Configuring MSTP.”
• Select rapid-pvst to enable rapid PVST+.
Step 3 interface interface-id (Recommended for rapid-PVST+ mode only) Specify an interface to
configure, and enter interface configuration mode. Valid interfaces
include physical ports, VLANs, and port channels. The VLAN ID range
is 1 to 4094. The port-channel range is 1 to 12.
Step 4 spanning-tree link-type point-to-point (Recommended for rapid-PVST+ mode only) Specify that the link type
for this port is point-to-point.
If you connect this port (local port) to a remote port through a
point-to-point link and the local port becomes a designated port, the
switch negotiates with the remote port and rapidly transitions the local
port to the forwarding state.
Step 5 end Return to privileged EXEC mode.
Step 6 clear spanning-tree detected-protocols (Recommended for rapid-PVST+ mode only) If any port on the switch
is connected to a port on a legacy 802.1D switch, restart the protocol
migration process on the entire switch.
This step is optional if the designated switch detects that this switch is
running rapid PVST+.
Step 7 show spanning-tree summary Verify your entries.
and
show spanning-tree interface
interface-id
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default setting, use the no spanning-tree mode global configuration command. To return
the port to its default setting, use the no spanning-tree link-type interface configuration command.
Caution When spanning tree is disabled and loops are present in the topology, excessive traffic and indefinite
packet duplication can drastically reduce network performance.
Beginning in privileged EXEC mode, follow these steps to disable spanning-tree on a per-VLAN basis.
This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 no spanning-tree vlan vlan-id For vlan-id, the range is 1 to 4094.
Step 3 end Return to privileged EXEC mode.
Step 4 show spanning-tree vlan vlan-id Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To re-enable spanning-tree, use the spanning-tree vlan vlan-id global configuration command.
Note The spanning-tree vlan vlan-id root global configuration command fails if the value necessary to be the
root switch is less than 1.
Note 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 switch. 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.
Note The root switch for each spanning-tree instance should be a backbone or distribution switch. Do not
configure an access switch as the spanning-tree primary root.
Use the diameter keyword to specify the Layer 2 network diameter (that is, the maximum number of
switch 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 After configuring the switch as the root switch, we recommend that you avoid manually configuring the
hello time, forward-delay time, and maximum-age time through the spanning-tree vlan vlan-id
hello-time, spanning-tree vlan vlan-id forward-time, and the spanning-tree vlan vlan-id max-age
global configuration commands.
Beginning in privileged EXEC mode, follow these steps to configure a switch to become the root for the
specified VLAN. This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 spanning-tree vlan vlan-id root primary Configure a switch to become the root for the specified VLAN.
[diameter net-diameter [hello-time seconds]]
• For vlan-id, you can specify a single VLAN identified by
VLAN ID number, a range of VLANs separated by a
hyphen, or a series of VLANs separated by a comma. The
range is 1 to 4094.
• (Optional) For diameter net-diameter, specify the
maximum number of switches between any two end
stations. The range is 2 to 7.
• (Optional) For hello-time seconds, specify the interval in
seconds between the generation of configuration messages
by the root switch. The range is 1 to 10; the default is 2.
Step 3 end Return to privileged EXEC mode.
Step 4 show spanning-tree detail Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default setting, use the no spanning-tree vlan vlan-id root global configuration
command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 spanning-tree vlan vlan-id root secondary Configure a switch to become the secondary root for the specified
[diameter net-diameter [hello-time VLAN.
seconds]]
• For vlan-id, you can specify a single VLAN identified by VLAN
ID number, a range of VLANs separated by a hyphen, or a series
of VLANs separated by a comma. The range is 1 to 4094.
• (Optional) For diameter net-diameter, specify the maximum
number of switches between any two end stations. The range is
2 to 7.
• (Optional) For hello-time seconds, specify the interval in
seconds between the generation of configuration messages by
the root switch. The range is 1 to 10; the default is 2.
Use the same network diameter and hello-time values that you used
when configuring the primary root switch. See the “Configuring the
Root Switch” section on page 16-14.
Step 3 end Return to privileged EXEC mode.
Step 4 show spanning-tree detail Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default setting, use the no spanning-tree vlan vlan-id root global configuration
command.
Beginning in privileged EXEC mode, follow these steps to configure the port priority of an interface.
This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify an interface to configure, and enter interface
configuration mode.
Valid interfaces include physical ports and port-channel
logical interfaces (port-channel port-channel-number).
Step 3 spanning-tree port-priority priority Configure the port priority for an interface.
For priority, the range is 0 to 240, in increments of 16; the
default is 128. Valid values are 0, 16, 32, 48, 64, 80, 96,
112, 128, 144, 160, 176, 192, 208, 224, and 240. All other
values are rejected. The lower the number, the higher the
priority.
Step 4 spanning-tree vlan vlan-id port-priority priority Configure the port priority for a VLAN.
• For vlan-id, you can specify a single VLAN identified
by VLAN ID number, a range of VLANs separated by
a hyphen, or a series of VLANs separated by a comma.
The range is 1 to 4094.
• For priority, the range is 0 to 240, in increments of 16;
the default is 128. Valid values are 0, 16, 32, 48, 64, 80,
96, 112, 128, 144, 160, 176, 192, 208, 224, and 240.
All other values are rejected. The lower the number,
the higher the priority.
Step 5 end Return to privileged EXEC mode.
Step 6 show spanning-tree interface interface-id Verify your entries.
or
show spanning-tree vlan vlan-id
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
Note The show spanning-tree 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 to the default setting, use the no spanning-tree [vlan vlan-id] port-priority interface
configuration command. For information on how to configure load sharing on trunk ports by using
spanning-tree port priorities, see the “Configuring Trunk Ports for Load Sharing” section on page 11-23.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify an interface to configure, and enter interface
configuration mode. Valid interfaces include physical ports and
port-channel logical interfaces (port-channel
port-channel-number).
Step 3 spanning-tree cost cost Configure the cost for an interface.
If a loop occurs, spanning tree uses the path cost when selecting
an interface to place into the forwarding state. A lower path cost
represents higher-speed transmission.
For cost, the range is 1 to 200000000; the default value is derived
from the media speed of the interface.
Step 4 spanning-tree vlan vlan-id cost cost Configure the cost for a VLAN.
If a loop occurs, spanning tree uses the path cost when selecting
an interface to place into the forwarding state. A lower path cost
represents higher-speed transmission.
• For vlan-id, you can specify a single VLAN identified by
VLAN ID number, a range of VLANs separated by a hyphen,
or a series of VLANs separated by a comma. The range is 1
to 4094.
• For cost, the range is 1 to 200000000; the default value is
derived from the media speed of the interface.
Step 5 end Return to privileged EXEC mode.
Step 6 show spanning-tree interface interface-id Verify your entries.
or
show spanning-tree vlan vlan-id
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
Note The show spanning-tree 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 to the default setting, use the no spanning-tree [vlan vlan-id] cost interface configuration
command. For information on how to configure load sharing on trunk ports by using spanning-tree path
costs, see the “Configuring Trunk Ports for Load Sharing” section on page 11-23.
Note Exercise care when using this command. For most situations, we recommend that you use the
spanning-tree vlan vlan-id root primary and the spanning-tree vlan vlan-id root secondary global
configuration commands to modify the switch priority.
Beginning in privileged EXEC mode, follow these steps to configure the switch priority of a VLAN. This
procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 spanning-tree vlan vlan-id priority priority Configure the switch priority of a VLAN.
• For vlan-id, you can specify a single VLAN identified by
VLAN ID number, a range of VLANs separated by a
hyphen, or a series of VLANs separated by a comma. The
range is 1 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 switch.
Valid priority values are 4096, 8192, 12288, 16384,
20480, 24576, 28672, 32768, 36864, 40960, 45056,
49152, 53248, 57344, and 61440. All other values are
rejected.
Step 3 end Return to privileged EXEC mode.
Step 4 show spanning-tree vlan vlan-id Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default setting, use the no spanning-tree vlan vlan-id priority global configuration
command.
Variable Description
Hello timer Controls how often the switch broadcasts hello messages to other switches.
Forward-delay timer Controls how long each of the listening and learning states last before the interface begins
forwarding.
Maximum-age timer Controls the amount of time the switch stores protocol information received on an interface.
Note Exercise care when using this command. For most situations, we recommend that you use the
spanning-tree vlan vlan-id root primary and the spanning-tree vlan vlan-id root secondary global
configuration commands to modify the hello time.
Beginning in privileged EXEC mode, follow these steps to configure the hello time of a VLAN. This
procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 spanning-tree vlan vlan-id hello-time seconds Configure the hello time of a VLAN. The hello time is the
interval between the generation of configuration messages by
the root switch. These messages mean that the switch is alive.
• For vlan-id, you can specify a single VLAN identified by
VLAN ID number, a range of VLANs separated by a
hyphen, or a series of VLANs separated by a comma. The
range is 1 to 4094.
• For seconds, the range is 1 to 10; the default is 2.
Step 3 end Return to privileged EXEC mode.
Step 4 show spanning-tree vlan vlan-id Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default setting, use the no spanning-tree vlan vlan-id hello-time global configuration
command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 spanning-tree vlan vlan-id forward-time Configure the forward time of a VLAN. The forward delay is the
seconds number of seconds an interface waits before changing from its
spanning-tree learning and listening states to the forwarding state.
• For vlan-id, you can specify a single VLAN identified by
VLAN ID number, a range of VLANs separated by a hyphen,
or a series of VLANs separated by a comma. The range is 1 to
4094.
• For seconds, the range is 4 to 30; the default is 15.
Step 3 end Return to privileged EXEC mode.
Step 4 show spanning-tree vlan vlan-id Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default setting, use the no spanning-tree vlan vlan-id forward-time global
configuration command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 spanning-tree vlan vlan-id max-age seconds Configure the maximum-aging time of a VLAN. The
maximum-aging time is the number of seconds a switch waits
without receiving spanning-tree configuration messages before
attempting a reconfiguration.
• For vlan-id, you can specify a single VLAN identified by
VLAN ID number, a range of VLANs separated by a
hyphen, or a series of VLANs separated by a comma. The
range is 1 to 4094.
• For seconds, the range is 6 to 40; the default is 20.
Step 3 end Return to privileged EXEC mode.
Step 4 show spanning-tree vlan vlan-id Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default setting, use the no spanning-tree vlan vlan-id max-age global configuration
command.
Command Purpose
show spanning-tree active Displays spanning-tree information on active interfaces only.
show spanning-tree detail Displays a detailed summary of interface information.
show spanning-tree interface interface-id Displays spanning-tree information for the specified interface.
show spanning-tree summary [totals] Displays a summary of interface states or displays the total lines of the STP
state section.
You can clear spanning-tree counters by using the clear spanning-tree [interface interface-id]
privileged EXEC command.
For information about other keywords for the show spanning-tree privileged EXEC command, see the
command reference for this release.
This chapter describes how to configure the Cisco implementation of the IEEE 802.1s Multiple STP
(MSTP) on the Catalyst 3750 Metro switch.
Note The multiple spanning-tree (MST) implementation in Cisco IOS Release 12.2(25)SEG and later is based
on the IEEE 802.1s standard. The MST implementations in earlier Cisco IOS releases are prestandard.
The MSTP enables multiple VLANs to be mapped to the same spanning-tree instance, thereby reducing
the number of spanning-tree instances needed to support a large number of VLANs. The MSTP provides
for multiple forwarding paths for data traffic and enables load balancing. It 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 MSTP is in the backbone and distribution
layers of a Layer 2 switched network; this deployment provides the highly-available network required
in a service-provider environment.
When the switch is in the multiple spanning-tree (MST) mode, the Rapid Spanning Tree Protocol
(RSTP), which is based on IEEE 802.1w, is automatically enabled. The RSTP provides rapid
convergence of the spanning tree through explicit handshaking that eliminates the IEEE 802.1D
forwarding delay and quickly transitions root ports and designated ports to the forwarding state.
Both MSTP and RSTP improve the spanning-tree operation and maintain backward compatibility with
equipment that is based on the (original) 802.1D spanning tree, with existing Cisco-proprietary Multiple
Instance STP (MISTP), and with existing Cisco per-VLAN spanning-tree plus (PVST+) and rapid
per-VLAN spanning-tree plus (rapid PVST+). For information about PVST+ and rapid PVST+, see
Chapter 16, “Configuring STP.” For information about other spanning-tree features such as Port Fast,
UplinkFast, root guard, and so forth, see Chapter 18, “Configuring Optional Spanning-Tree Features.”
Note For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
Understanding MSTP
MSTP, which uses RSTP for rapid convergence, enables VLANs to be grouped 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.
These sections describe how the MSTP works:
• Multiple Spanning-Tree Regions, page 17-2
• IST, CIST, and CST, page 17-2
• Hop Count, page 17-5
• Boundary Ports, page 17-6
• IEEE 802.1s Implementation, page 17-6
• Interoperability with 802.1D STP, page 17-8
For configuration information, see the “Configuring MSTP Features” section on page 17-13.
The IST is the only spanning-tree instance that sends and receives BPDUs; all of the other
spanning-tree instance information is contained in M-records, which are encapsulated within MSTP
BPDUs. Because the MSTP BPDU carries information for all instances, the number of BPDUs that
need to be processed by a switch 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 switch 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 common and internal spanning tree (CIST), which is a collection of the ISTs in each MST region,
and the common spanning tree (CST) that 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 as a result of the spanning-tree algorithm running between
switches that support the 802.1w, 802.1s, and 802.1D protocols. The CIST inside an MST region is
the same as the CST outside a region.
For more information, see the “Operations Within an MST Region” section on page 17-3 and the
“Operations Between MST Regions” section on page 17-4.
Note The implementation of the IEEE 802.1s standard, changes some of the terminology associated with MST
implementations. For a summary of these changes, see Table 17-1 on page 17-5.
Figure 17-1 MST Regions, IST Masters, and the CST Root
A IST master
and CST root
D
Legacy 802.1D
MST Region 1
B
IST master C IST master
Figure 17-1 does not show additional MST instances for each region. Note that the topology of MST
instances can be different from that of the IST for the same region.
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, port VLAN priority) can be configured on both the CST instance and the MST instance.
MSTP switches use Version 3 RSTP BPDUs or 802.1D STP BPDUs to communicate with legacy 802.1D
switches. MSTP switches use MSTP BPDUs to communicate with MSTP switches.
Hop Count
The IST and MST instances do 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 (trigger a reconfiguration). The root
switch 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’s designated ports at the
boundary.
Boundary Ports
In the Cisco prestandard implementation, a boundary port connects an MST region to a single
spanning-tree region running RSTP, to a single spanning-tree region running PVST+ or rapid PVST+,
or to 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 IEEE 802.1s standard. The IEEE 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 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. This 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 than 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 a legacy STP switch on the segment, messages are always considered external.
The other change from the prestandard implementation is that the CIST regional root switch ID field is
now inserted where an RSTP or legacy IEEE 802.1Q 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.
• The boundary port is not the root port of the CIST regional root—The 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 (MRecords).
In this case, although the boundary role no longer exists, the show commands identify a port as
boundary in the type column of the output.
Segment X MST
Region
Switch A
Switch B
92721
Segment Y
Note We recommend that you minimize the interaction between standard and prestandard MST
implementations.
Figure 17-3 illustrates a unidirectional link failure that typically creates a bridging loop. Switch A is the
root switch, 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 switch. As a result, switch
A blocks (or keeps blocking) its port, thus preventing the bridging loop.
Superior
Switch BPDU Switch
A B
92722
Inferior BPDU,
Designated + Learning bit set
Understanding 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), which is critical for networks carrying delay-sensitive
traffic such as voice and video.
These section describes how the RSTP works:
• Port Roles and the Active Topology, page 17-9
• Rapid Convergence, page 17-9
• Synchronization of Port Roles, page 17-11
• Bridge Protocol Data Unit Format and Processing, page 17-11
For configuration information, see the “Configuring MSTP Features” section on page 17-13.
To be consistent with Cisco STP implementations, this guide documents 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 ports—If 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 ports—If 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 links—If 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 17-4, Switch A is connected to Switch B through a point-to-point link, and all
of the ports are in the blocking state. Assume that the priority of Switch A is a smaller numerical
value than the priority of Switch B. Switch A sends a proposal message (a configuration BPDU with
the proposal flag set) to Switch B, proposing itself as the designated switch.
After receiving the proposal message, Switch B selects as its new root port the port from which the
proposal message was received, forces all nonedge ports to the blocking state, and sends an
agreement message (a BPDU with the agreement flag set) through its new root port.
After receiving Switch B’s 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; 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.
Designated
Root Agreement switch
F F
DP RP
Designated
Root switch Proposal Switch C
F F
DP RP
Designated
Root switch Agreement
F F F F
DP RP DP RP
DP = designated port
88760
RP = root port
F = forwarding
4. Agreement 1. Proposal
5. Forward
Edge port
2. Block 3. Block
9. Forward 11. Forward
Root port
88761
Designated port
Bit Function
0 Topology change (TC)
1 Proposal
2–3: Port role:
00 Unknown
01 Alternate port
10 Root port
11 Designated port
4 Learning
5 Forwarding
6 Agreement
7 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 topology change notification (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.
Topology Changes
This section describes the differences between the RSTP and the 802.1D in handling spanning-tree
topology changes.
• Detection—Unlike 802.1D in which any transition between the blocking and the forwarding state
causes a topology change, only transitions from the blocking to the forwarding state cause a
topology change with RSTP (only an increase in connectivity is considered a topology change).
State changes on an edge port do not cause a topology change. When an RSTP switch detects a
topology change, it flushes the learned information on all of its nonedge ports except on those from
which it received the TC notification.
• Notification—Unlike 802.1D, which uses TCN BPDUs, the RSTP does not use them. However, for
802.1D interoperability, an RSTP switch processes and generates TCN BPDUs.
• Acknowledgement—When 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 topology-change timer in 802.1D) is active on a root port connected
to an 802.1D switch and a configuration BPDU with the TCA bit set is received, the TC-while timer
is reset.
This behavior is only required to support 802.1D switches. The RSTP BPDUs never have the TCA
bit set.
• Propagation—When 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 migration—For 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’s 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.
For information about the supported number of spanning-tree instances, see the “Supported
Spanning-Tree Instances” section on page 16-9.
• PVST+, rapid PVST+, and MSTP are supported, but only one version can be active at any time. (For
example, all VLANs run PVST+, all VLANs run rapid PVST+, or all VLANs run MSTP.) For more
information, see the “Spanning-Tree Interoperability and Backward Compatibility” section on
page 16-10. For information on the recommended trunk port configuration, see the “Interaction with
Other Features” section on page 11-19.
• VTP propagation of the MST configuration is not supported. However, you can manually configure
the MST configuration (region name, revision number, and VLAN-to-instance mapping) on each
switch within the MST region by using the command-line interface (CLI) or through the SNMP
support.
• 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 IST master of the MST
cloud should also 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. You might have to manually configure the switches in the clouds.
• 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 routers or non-Layer 2 devices.
• For configuration guidelines about UplinkFast and BackboneFast, see the “Optional Spanning-Tree
Configuration Guidelines” section on page 18-10.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 spanning-tree mst configuration Enter MST configuration mode.
Command Purpose
Step 3 instance instance-id vlan vlan-range Map 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.
Step 4 name name Specify the configuration name. The name string has a maximum length
of 32 characters and is case sensitive.
Step 5 revision version Specify the configuration revision number. The range is 0 to 65535.
Step 6 show pending Verify your configuration by displaying the pending configuration.
Step 7 exit Apply all changes, and return to global configuration mode.
Step 8 spanning-tree mode mst Enable MSTP. RSTP is also enabled.
You cannot run both MSTP and PVST+ or both MSTP and rapid PVST+
at the same time.
Step 9 end Return to privileged EXEC mode.
Step 10 show running-config Verify your entries.
Step 11 copy running-config startup-config (Optional) Save your entries in the configuration file.
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 re-enable 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:
Switch(config)# spanning-tree mst configuration
Switch(config-mst)# instance 1 vlan 10-20
Switch(config-mst)# name region1
Switch(config-mst)# revision 1
Switch(config-mst)# show pending
Pending MST configuration
Name [region1]
Revision 1
Switch(config-mst)# exit
Switch(config)#
Note After configuring the switch as the root switch, we recommend that you avoid manually configuring the
hello time, forward-delay time, and maximum-age time through the spanning-tree mst hello-time,
spanning-tree mst forward-time, and the spanning-tree mst max-age global configuration
commands.
Beginning in privileged EXEC mode, follow these steps to configure a switch as the root switch. This
procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 spanning-tree mst instance-id root primary Configure a switch as the root switch.
[diameter net-diameter [hello-time seconds]]
• 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 switch. The range is 1 to 10 seconds; the
default is 2 seconds.
Step 3 end Return to privileged EXEC mode.
Step 4 show spanning-tree mst instance-id Verify your entries.
Step 5 copy running-config startup-config (Optional) Save 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.
Beginning in privileged EXEC mode, follow these steps to configure a switch as the secondary root
switch. This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 spanning-tree mst instance-id root Configure a switch as the secondary root switch.
secondary [diameter net-diameter
• For instance-id, you can specify a single instance, a range of
[hello-time seconds]]
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 switch. 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 switch. See the “Configuring the
Root Switch” section on page 17-17.
Step 3 end Return to privileged EXEC mode.
Step 4 show spanning-tree mst instance-id Verify your entries.
Step 5 copy running-config startup-config (Optional) Save 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.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify an interface to configure, and enter interface
configuration mode.
Valid interfaces include physical ports and port-channel
logical interfaces. The port-channel range is 1 to 12.
Command Purpose
Step 3 spanning-tree mst instance-id port-priority priority Configure the port priority.
• For instance-id, you can specify a single instance, a
range of instances separated by a hyphen, or a series of
instances separated by a comma. The range is 0 to
4094.
• For priority, the range is 0 to 240 in increments of 16.
The default is 128. The lower the number, the higher
the priority.
The priority values are 0, 16, 32, 48, 64, 80, 96, 112,
128, 144, 160, 176, 192, 208, 224, and 240. All other
values are rejected.
Step 4 end Return to privileged EXEC mode.
Step 5 show spanning-tree mst interface interface-id Verify your entries.
or
show spanning-tree mst instance-id
Step 6 copy running-config startup-config (Optional) Save 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.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify an interface to configure, and enter interface
configuration mode. Valid interfaces include physical ports and
port-channel logical interfaces. The port-channel range is 1 to 12.
Command Purpose
Step 3 spanning-tree mst instance-id cost cost Configure the cost.
If a loop occurs, the MSTP uses the path cost when selecting an
interface to place into the forwarding state. A lower path cost
represents higher-speed transmission.
• For instance-id, you can specify a single instance, a range of
instances separated by a hyphen, or a series of instances
separated by a comma. The range is 0 to 4094.
• For cost, the range is 1 to 200000000; the default value is
derived from the media speed of the interface.
Step 4 end Return to privileged EXEC mode.
Step 5 show spanning-tree mst interface interface-id Verify your entries.
or
show spanning-tree mst instance-id
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
Note The show spanning-tree mst interface interface-id privileged EXEC command displays information
only for interfaces 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.
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.
Beginning in privileged EXEC mode, follow these steps to configure the switch priority. This procedure
is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 spanning-tree mst instance-id priority priority Configure 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 switch.
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.
Step 3 end Return to privileged EXEC mode.
Step 4 show spanning-tree mst instance-id Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return the switch to its default setting, use the no spanning-tree mst instance-id priority global
configuration command.
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.
Beginning in privileged EXEC mode, follow these steps to configure the hello time for all MST
instances. This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 spanning-tree mst hello-time seconds Configure the hello time for all MST instances. The hello time
is the interval between the generation of configuration
messages by the root switch. These messages mean that the
switch is alive.
For seconds, the range is 1 to 10; the default is 2.
Step 3 end Return to privileged EXEC mode.
Command Purpose
Step 4 show spanning-tree mst Verify your entries.
Step 5 copy running-config startup-config (Optional) Save 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.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 spanning-tree mst forward-time seconds Configure 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.
Step 3 end Return to privileged EXEC mode.
Step 4 show spanning-tree mst Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return the switch to its default setting, use the no spanning-tree mst forward-time global
configuration command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 spanning-tree mst max-age seconds Configure 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.
Step 3 end Return to privileged EXEC mode.
Step 4 show spanning-tree mst Verify your entries.
Step 5 copy running-config startup-config (Optional) Save 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.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 spanning-tree mst max-hops hop-count Specify 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.
Step 3 end Return to privileged EXEC mode.
Step 4 show spanning-tree mst Verify your entries.
Step 5 copy running-config startup-config (Optional) Save 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.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface to configure, and enter interface
configuration mode. Valid interfaces include physical port,
VLANs, and port-channel logical interfaces. The VLAN ID
range is 1 to 4094. The port-channel range is 1 to 12.
Step 3 spanning-tree link-type point-to-point Specify that the link type of a port is point-to-point.
Step 4 end Return to privileged EXEC mode.
Command Purpose
Step 5 show spanning-tree mst interface interface-id Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return the port to its default setting, use the no spanning-tree link-type interface configuration
command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify an interface to configure, and enter interface
configuration mode. Valid interfaces include physical ports.
Step 3 spanning-tree mst pre-standard Specify that the port can send only prestandard BPDUs.
Step 4 end Return to privileged EXEC mode.
Step 5 show spanning-tree mst interface interface-id Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return the port to its default setting, use the no spanning-tree mst prestandard interface
configuration command.
To restart the protocol migration process on a specific port, use the clear spanning-tree
detected-protocols interface interface-id privileged EXEC command.
Command Purpose
show spanning-tree mst configuration Displays the MST region configuration.
show spanning-tree mst configuration digest Displays the MD5 digest included in the current MSTCI.
show spanning-tree mst instance-id Displays MST information for the specified instance.
show spanning-tree mst interface interface-id Displays MST information for the specified interface.
For information about other keywords for the show spanning-tree privileged EXEC command, see the
command reference for this release.
This chapter describes how to configure optional spanning-tree features on the Catalyst 3750 Metro
switch. You can configure all of these features when your switch is running the per-VLAN spanning-tree
plus (PVST+). You can configure only the noted features when your switch is running the Multiple
Spanning Tree Protocol (MSTP) or the rapid per-VLAN spanning-tree plus (rapid-PVST+) protocol.
For information on configuring the PVST+ and rapid PVST+, see Chapter 16, “Configuring STP.” For
information about the Multiple Spanning Tree Protocol (MSTP) and how to map multiple VLANs to the
same spanning-tree instance, see Chapter 17, “Configuring MSTP.”
Note For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
Note Because the purpose of Port Fast is to minimize the time interfaces must wait for spanning-tree to
converge, it is effective only when used on interfaces connected to end stations. If you enable Port Fast
on an interface connecting to another switch, you risk creating a spanning-tree loop.
You can enable this feature by using the spanning-tree portfast interface configuration or the
spanning-tree portfast default global configuration command.
Server
Port
Port Fast-enabled port
Fast-enabled
ports
101225
Workstations Workstations
The BPDU guard feature provides a secure response to invalid configurations because you must
manually put the interface back in service. Use the BPDU guard feature in a service-provider network
to prevent an access port from participating in the spanning tree.
You can enable the BPDU guard feature for the entire switch or for an interface.
Caution Enabling BPDU filtering on an interface is the same as disabling spanning tree on it and can result in
spanning-tree loops.
You can enable the BPDU filtering feature for the entire switch or for an interface.
Understanding UplinkFast
Switches in hierarchical networks can be grouped into backbone switches, distribution switches, and
access switches. Figure 18-2 shows a complex network where distribution switches and access switches
each have at least one redundant link that spanning tree blocks to prevent loops.
Backbone switches
Root bridge
Distribution switches
101231
Active link Access switches
Blocked link
If a switch loses connectivity, it begins using the alternate paths as soon as the spanning tree selects a
new root port. By enabling UplinkFast with the spanning-tree uplinkfast global configuration
command, you can accelerate the choice of a new root port when a link or switch fails or when the
spanning tree reconfigures itself. The root port transitions to the forwarding state immediately without
going through the listening and learning states, as it would with the normal spanning-tree procedures.
When the spanning tree reconfigures the new root port, other interfaces flood the network with multicast
packets, one for each address that was learned on the interface. You can limit these bursts of multicast
traffic by reducing the max-update-rate parameter (the default for this parameter is 150 packets per
second). However, if you enter zero, station-learning frames are not generated, so the spanning-tree
topology converges more slowly after a loss of connectivity.
Note UplinkFast is most useful in wiring-closet switches at the access or edge of the network. It is not
appropriate for backbone devices. This feature might not be useful for other types of applications.
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 ports (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.
Figure 18-3 shows an example topology with no link failures. Switch A, the root switch, is connected
directly to Switch B over link L1 and to Switch C over link L2. The Layer 2 interface on Switch C that
is connected directly to Switch B is in a blocking state.
Switch A
(Root) Switch B
L1
L2 L3
Blocked port
43575
Switch C
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 interface on Switch C and transitions it to the forwarding state without
going through the listening and learning states, as shown in Figure 18-4. This change takes
approximately 1 to 5 seconds.
Switch A
(Root) Switch B
L1
L2 L3
Link failure
UplinkFast transitions port
directly to forwarding state.
43576
Switch C
Understanding BackboneFast
BackboneFast detects indirect failures in the core of the backbone. BackboneFast is a complementary
technology to the UplinkFast feature, which responds to failures on links directly connected to access
switches. BackboneFast optimizes the maximum-age timer, which controls the amount of time the
switch stores protocol information received on an interface. When a switch receives an inferior BPDU
from the designated port of another switch, the BPDU is a signal that the other switch might have lost
its path to the root, and BackboneFast tries to find an alternate path to the root.
BackboneFast, which is enabled by using the spanning-tree backbonefast global configuration
command, starts when a root port or blocked interface on a switch receives inferior BPDUs from its
designated switch. An inferior BPDU identifies a switch that declares itself as both the root bridge and
the designated switch. When a switch receives an inferior BPDU, it means that a link to which the switch
is not directly connected (an indirect link) has failed (that is, the designated switch has lost its connection
to the root switch). Under spanning-tree rules, the switch ignores inferior BPDUs for the configured
maximum aging time specified by the spanning-tree vlan vlan-id max-age global configuration
command.
The switch tries to determine if it has an alternate path to the root switch. If the inferior BPDU arrives
on a blocked interface, the root port and other blocked interfaces on the switch become alternate paths
to the root switch. (Self-looped ports are not considered alternate paths to the root switch.) If the inferior
BPDU arrives on the root port, all blocked interfaces become alternate paths to the root switch. If the
inferior BPDU arrives on the root port and there are no blocked interfaces, the switch assumes that it has
lost connectivity to the root switch, causes the maximum aging time on the root port to expire, and
becomes the root switch according to normal spanning-tree rules.
If the switch has alternate paths to the root switch, it uses these alternate paths to send a root link query
(RLQ) request. The switch sends the RLQ request on all alternate paths and waits for an RLQ reply from
other switches in the network
If the switch discovers that it still has an alternate path to the root, it expires the maximum aging time
on the interface that received the inferior BPDU. If all the alternate paths to the root switch indicate that
the switch has lost connectivity to the root switch, the switch expires the maximum aging time on the
interface that received the RLQ reply. If one or more alternate paths can still connect to the root switch,
the switch makes all interfaces on which it received an inferior BPDU its designated ports and moves
them from the blocking state (if they were in the blocking state), through the listening and learning
states, and into the forwarding state.
Figure 18-5 shows an example topology with no link failures. Switch A, the root switch, connects
directly to Switch B over link L1 and to Switch C over link L2. The Layer 2 interface on Switch C that
connects directly to Switch B is in the blocking state.
Switch A
(Root) Switch B
L1
L2 L3
Blocked port
44963
Switch C
If link L1 fails as shown in Figure 18-6, 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 switch over L1, it detects
the failure, elects itself the root, and begins sending BPDUs to Switch C, identifying itself as the root.
When Switch C receives the inferior BPDUs from Switch B, Switch C assumes that an indirect failure
has occurred. At that point, BackboneFast allows the blocked interface on Switch C to move
immediately to the listening state without waiting for the maximum aging time for the interface to expire.
BackboneFast then transitions the Layer 2 interface on Switch C to the forwarding state, providing a path
from Switch B to Switch A. The root-switch election takes approximately 30 seconds, twice the Forward
Delay time if the default Forward Delay time of 15 seconds is set. Figure 18-6 shows how BackboneFast
reconfigures the topology to account for the failure of link L1.
Switch A
(Root) Switch B
L1
Link failure
L2 L3
44964
Switch C
If a new switch is introduced into a shared-medium topology as shown in Figure 18-7, BackboneFast is
not activated because the inferior BPDUs did not come from the recognized designated switch
(Switch B). The new switch begins sending inferior BPDUs that indicate it is the root switch. However,
the other switches ignore these inferior BPDUs, and the new switch learns that Switch B is the
designated switch to Switch A, the root switch.
Switch A
(Root)
Switch C Switch B
(Designated bridge)
Blocked port
Added switch
44965
Potential
spanning-tree root without
root guard enabled
Desired
root switch
Caution Use Port Fast only when connecting a single end station to an access or trunk port. Enabling this feature
on an interface connected to a switch or hub could prevent spanning tree from detecting and disabling
loops in your network, which could cause broadcast storms and address-learning problems.
If you enable the voice VLAN feature, the Port Fast feature is automatically enabled. When you disable
voice VLAN, the Port Fast feature is not automatically disabled. For more information, see Chapter 14,
“Configuring Voice VLAN.”
You can enable this feature if your switch is running PVST+, rapid PVST+, or MSTP.
Beginning in privileged EXEC mode, follow these steps to enable Port Fast. This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify an interface to configure, and enter interface
configuration mode.
Step 3 spanning-tree portfast [trunk] Enable Port Fast on an access port connected to a single
workstation or server. By specifying the trunk keyword, you can
enable Port Fast on a trunk port.
Note You can use the spanning-tree portfast default global configuration command to globally enable the
Port Fast feature on all nontrunking ports.
To disable the Port Fast feature, use the spanning-tree portfast disable interface configuration
command.
Caution Configure Port Fast only on interfaces that connect to end stations; otherwise, an accidental topology
loop could cause a data packet loop and disrupt switch and network operation.
You also can use the spanning-tree bpduguard enable interface configuration command to enable
BPDU guard on any interface without also enabling the Port Fast feature. When the interface receives a
BPDU, it is put in the error-disabled state.
You can enable the BPDU guard feature if your switch is running PVST+, rapid PVST+, or MSTP.
Beginning in privileged EXEC mode, follow these steps to globally enable the BPDU guard feature. This
procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 spanning-tree portfast bpduguard default Globally enable BPDU guard.
By default, BPDU guard is disabled.
Step 3 interface interface-id Specify the interface connected to an end station, and enter
interface configuration mode.
Step 4 spanning-tree portfast Enable the Port Fast feature.
Step 5 end Return to privileged EXEC mode.
Step 6 show running-config Verify your entries.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable BPDU guard, use the no spanning-tree portfast bpduguard default global configuration
command.
You can override the setting of the no spanning-tree portfast bpduguard default global configuration
command by using the spanning-tree bpduguard enable interface configuration command.
Caution Configure Port Fast only on interfaces that connect to end stations; otherwise, an accidental topology
loop could cause a data packet loop and disrupt switch and network operation.
You can also use the spanning-tree bpdufilter enable interface configuration command to enable
BPDU filtering on any interface without also enabling the Port Fast feature. This command prevents the
interface from sending or receiving BPDUs.
Caution Enabling BPDU filtering on an interface is the same as disabling spanning tree on it and can result in
spanning-tree loops.
You can enable the BPDU filtering feature if your switch is running PVST+, rapid PVST+, or MSTP.
Beginning in privileged EXEC mode, follow these steps to globally enable the BPDU filtering feature.
This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 spanning-tree portfast bpdufilter default Globally enable BPDU filtering.
By default, BPDU filtering is disabled.
Step 3 interface interface-id Specify the interface connected to an end station, and enter
interface configuration mode.
Step 4 spanning-tree portfast Enable the Port Fast feature.
Step 5 end Return to privileged EXEC mode.
Step 6 show running-config Verify your entries.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable BPDU filtering, use the no spanning-tree portfast bpdufilter default global configuration
command.
You can override the setting of the no spanning-tree portfast bpdufilter default global configuration
command by using the spanning-tree bpdufilter enable interface configuration command.
Note When you enable UplinkFast, it affects all VLANs on the switch. You cannot configure UplinkFast on
an individual VLAN.
You can configure the UplinkFast feature for rapid PVST+ or for MSTP, but the feature remains disabled
(inactive) until you change the spanning-tree mode to PVST+.
Beginning in privileged EXEC mode, follow these steps to enable UplinkFast. This procedure is
optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 spanning-tree uplinkfast [max-update-rate Enable UplinkFast.
pkts-per-second]
(Optional) For pkts-per-second, the range is 0 to 32000 packets per
second; the default is 150.
If you set the rate to 0, station-learning frames are not generated,
and the spanning-tree topology converges more slowly after a loss
of connectivity.
Step 3 end Return to privileged EXEC mode.
Step 4 show spanning-tree summary Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
When UplinkFast is enabled, the switch priority of all VLANs is set to 49152. If you change the path
cost to a value less than 3000 and you enable UplinkFast or UplinkFast is already enabled, the path cost
of all interfaces and VLAN trunks is increased by 3000 (if you change the path cost to 3000 or above,
the path cost is not altered). The changes to the switch priority and the path cost reduce the chance that
a switch will become the root switch.
When UplinkFast is disabled, the switch priorities of all VLANs and path costs of all interfaces are set
to default values if you did not modify them from their defaults.
To return the update packet rate to the default setting, use the no spanning-tree uplinkfast
max-update-rate global configuration command. To disable UplinkFast, use the no spanning-tree
uplinkfast command.
Enabling BackboneFast
You can enable BackboneFast to detect indirect link failures and to start the spanning-tree
reconfiguration sooner.
Note If you use BackboneFast, you must enable it on all switches in the network. BackboneFast is not
supported on Token Ring VLANs. This feature is supported for use with third-party switches.
You can configure the BackboneFast feature for rapid PVST+ or for MSTP, but the feature remains
disabled (inactive) until you change the spanning-tree mode to PVST+.
Beginning in privileged EXEC mode, follow these steps to enable BackboneFast. This procedure is
optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 spanning-tree backbonefast Enable BackboneFast.
Step 3 end Return to privileged EXEC mode.
Step 4 show spanning-tree summary Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable the BackboneFast feature, use the no spanning-tree backbonefast global configuration
command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 spanning-tree etherchannel guard Enable EtherChannel guard.
misconfig
Step 3 end Return to privileged EXEC mode.
Step 4 show spanning-tree summary Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable the EtherChannel guard feature, use the no spanning-tree etherchannel guard misconfig
global configuration command.
You can use the show interfaces status err-disabled privileged EXEC command to show which switch
ports are disabled because of an EtherChannel misconfiguration. On the remote device, you can enter
the show etherchannel summary privileged EXEC command to verify the EtherChannel configuration.
After the configuration is corrected, enter the shutdown and no shutdown interface configuration
commands on the port-channel interfaces that were misconfigured.
Note You cannot enable both root guard and loop guard at the same time.
You can enable this feature if your switch is running PVST+, rapid PVST+, or MSTP.
Beginning in privileged EXEC mode, follow these steps to enable root guard on an interface. This
procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify an interface to configure, and enter interface configuration mode.
Step 3 spanning-tree guard root Enable root guard on the interface.
By default, root guard is disabled on all interfaces.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable root guard, use the no spanning-tree guard interface configuration command.
Note You cannot enable both loop guard and root guard at the same time.
You can enable this feature if your switch is running PVST+, rapid PVST+, or MSTP.
Beginning in privileged EXEC mode, follow these steps to enable loop guard. This procedure is optional.
Command Purpose
Step 1 show spanning-tree active Verify which interfaces are alternate or root ports.
or
show spanning-tree mst
Step 2 configure terminal Enter global configuration mode.
Command Purpose
Step 3 spanning-tree loopguard default Enable loop guard.
By default, loop guard is disabled.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To globally disable loop guard, use the no spanning-tree loopguard default global configuration
command. You can override the setting of the no spanning-tree loopguard default global configuration
command by using the spanning-tree guard loop interface configuration command.
Command Purpose
show spanning-tree active Displays spanning-tree information on active interfaces only.
show spanning-tree detail Displays a detailed summary of interface information.
show spanning-tree interface interface-id Displays spanning-tree information for the specified interface.
show spanning-tree mst interface interface-id Displays MST information for the specified interface.
show spanning-tree summary [totals] Displays a summary of interface states or displays the total lines of the
spanning-tree state section.
You can clear spanning-tree counters by using the clear spanning-tree [interface interface-id]
privileged EXEC command.
For information about other keywords for the show spanning-tree privileged EXEC command, see the
command reference for this release.
This chapter describes how to use Resilient Ethernet Protocol (REP) on the Catalyst 3750 Metro switch.
REP is a Cisco proprietary protocol that provides an alternative to Spanning Tree Protocol (STP) to
control network loops, handle link failures, and improve convergence time. REP controls a group of ports
connected in a segment, ensures that the segment does not create any bridging loops, and responds to
link failures within the segment. REP provides a basis for constructing more complex networks and
supports VLAN load balancing.
This chapter includes these sections:
• Understanding REP, page 19-1
• Configuring REP, page 19-7
• Monitoring REP, page 19-15
Understanding REP
One REP segment is a chain of ports connected to each other and configured with a segment ID. Each
segment consists of standard (non-edge) segment ports and two user-configured edge ports. A switch can
have no more than two ports that belong to the same segment, and each segment port can have only one
external neighbor. A segment can go through a shared medium, but on any link only two ports can belong
to the same segment. REP is supported only on Layer 2 trunk interfaces.
Figure 19-1 shows an example of a segment consisting of six ports spread across four switches. Ports E1
and E2 are configured as edge ports. When all ports are operational (as in the segment on the left), a
single port is blocked, shown by the diagonal line. When there is a failure in the network, as shown in
the diagram on the right, the blocked port returns to the forwarding state to minimize network disruption.
E1 Edge port
Blocked port
Link failure
E1 E2 E1 E2
201888
The segment shown in Figure 19-1 is an open segment; there is no connectivity between the two edge
ports. The REP segment cannot cause a bridging loop and it is safe to connect the segment edges to any
network. All hosts connected to switches inside the segment have two possible connections to the rest
of the network through the edge ports, but only one connection is accessible at any time. If a failure
causes a host to be unable to access its usual gateway, REP unblocks all ports to ensure that connectivity
is available through the other gateway.
The segment shown in Figure 19-2, with both edge ports located on the same switch, is a ring segment.
In this configuration, there is connectivity between the edge ports through the segment. With this
configuration, you can create a redundant connection between any two switches in the segment.
E1 E2
201889
You can construct almost any type of network based on REP segments. REP also supports VLAN
load-balancing, controlled by the primary edge port but occurring at any port in the segment.
In access ring topologies, the neighboring switch might not support REP, as shown in Figure 19-3. In
this case, you can configure the non-REP facing ports (E1 and E2) as edge no-neighbor ports. These
ports inherit all properties of edge ports, and you can configure them the same as any edge port, including
configuring them to send STP or REP topology change notices to the aggregation switch. In this case the
STP topology change notice (TCN) that is sent is a multiple spanning-tree (MST) STP message.
E1
REP not
supported
273792
E2
REP ports
Link Integrity
REP does not use an end-to-end polling mechanism between edge ports to verify link integrity. It
implements local link failure detection. The REP Link Status Layer (LSL) detects its REP-aware
neighbor and establishes connectivity within the segment. All VLANs are blocked on an interface until
it detects the neighbor. After the neighbor is identified, REP determines which neighbor port should
become the alternate port and which ports should forward traffic.
Each port in a segment has a unique port ID. The port ID format is similar to that used by the spanning
tree algorithm: a port number (unique on the bridge), associated to a MAC address (unique in the
network). When a segment port is coming up, its LSL starts sending packets that include the segment ID
and the port ID. The port is declared as operational after it performs a three-way handshake with a
neighbor in the same segment.
Fast Convergence
Because REP runs on a physical link basis and not a per-VLAN basis, only one hello message is required
for all VLANs, reducing the load on the protocol. We recommend that you create VLANs consistently
on all switches in a given segment and configure the same allowed VLANs on the REP trunk ports. To
avoid the delay introduced by relaying messages in software, REP also allows some packets to be
flooded to a regular multicast address. These messages operate at the hardware flood layer (HFL) and
are flooded to the whole network, not just the REP segment. Switches that do not belong to the segment
treat them as data traffic. You can control flooding of these messages by configuring a dedicated
administrative VLAN for the whole domain.
The estimated convergence recovery time on fiber interfaces is less than 200 ms for the local segment
with 200 VLANs configured. Convergence for VLAN load balancing is 300 ms or less.
Note You configure offset numbers on the primary edge port by identifying a port’s downstream
position from the primary (or secondary) edge port. You would never enter an offset value of 1
because that is the offset number of the primary edge port itself.
Figure 19-4 shows neighbor offset numbers for a segment where E1 is the primary edge port and E2
is the secondary edge port. The red numbers inside the ring are numbers offset from the primary
edge port; the black numbers outside of the ring show the offset numbers from the secondary edge
port. Note that you can identify all ports (except the primary edge port) by either a positive offset
number (downstream position from the primary edge port) or a negative offset number (downstream
position from the secondary edge port). If E2 became the primary edge port, its offset number would
then be 1 and E1 would be -1.
• By entering the preferred keyword to select the port that you previously configured as the preferred
alternate port with the rep segment segment-id preferred interface configuration command.
-1
E1 = Primary edge port
E1 E2 E2 = Secondary edge port
-9 2 1 10 -2
9 Offset numbers from the primary edge port
Offset numbers from the secondary edge
port (negative numbers)
-8 3 8 -3
4 7
-4
-7 5
201890
6
-5
-6
When the REP segment is complete, all VLANs are blocked. When you configure VLAN load balancing,
you must also configure triggers in one of two ways:
• Manually trigger VLAN load balancing at any time by entering the rep preempt segment
segment-id privileged EXEC command on the switch that has the primary edge port.
• Configure a preempt delay time by entering the rep preempt delay seconds interface configuration
command. After a link failure and recovery, VLAN load balancing begins after the configured
preemption time period elapses. Note that the delay timer restarts if another port fails before the time
has elapsed.
Note When VLAN load balancing is configured, it does not start working until triggered by either manual
intervention or a link failure and recovery.
When VLAN load balancing is triggered, the primary edge port sends out a message to alert all interfaces
in the segment about the preemption. When the secondary port receives the message, it is reflected into
the network to notify the alternate port to block the set of VLANs specified in the message and to notify
the primary edge port to block the remaining VLANs.
You can also configure a particular port in the segment to block all VLANs. Only the primary edge port
initiates VLAN load balancing, which is not possible if the segment is not terminated by an edge port on
each end. The primary edge port determines the local VLAN load balancing configuration.
Reconfigure the primary edge port to reconfigure load balancing. When you change the load balancing
configuration, the primary edge port again waits for the rep preempt segment command or for the
configured preempt delay period after a port failure and recovery before executing the new
configuration. If you change an edge port to a regular segment port, the existing VLAN load balancing
status does not change. Configuring a new edge port might cause a new topology configuration.
Note Do not configure VLAN load balancing on an interface that carries Ethernet over multiprotocol label
switching (EoMPLS) traffic. VLAN load balancing across the REP ring might prevent forwarding some
of the EoMPLS traffic.
REP Ports
Ports in REP segments are Failed, Open, or Alternate.
• A port configured as a regular segment port starts as a failed port.
• After the neighbor adjacencies are determined, the port transitions to alternate port state, blocking
all VLANs on the interface. Blocked port negotiations occur and when the segment settles, one
blocked port remains in the alternate role and all other ports become open ports.
• When a failure occurs in a link, all ports move to the failed state. When the alternate port receives
the failure notification, it changes to the open state, forwarding all VLANs.
A regular segment port converted to an edge port, or an edge port converted to a regular segment port,
does not always result in a topology change. If you convert an edge port into a regular segment port,
VLAN load balancing is not implemented unless it has been configured. For VLAN load balancing, you
must configure two edge ports in the segment.
A segment port that is reconfigured as a spanning tree port restarts according the spanning tree
configuration. By default, this is a designated blocking port. If PortFast is configured or if STP is
disabled, the port goes into the forwarding state.
Configuring REP
A segment is a collection of ports connected one to the other in a chain and configured with a segment
ID. To configure REP segments, you configure the REP administrative VLAN (or use the default
VLAN 1) and then add the ports to the segment using interface configuration mode. You should
configure two edge ports in the segment, with one of them the primary edge port and the other by default
the secondary edge port. A segment has only one primary edge port. If you configure two ports in a
segment as the primary edge port, for example ports on different switches, the REP selects one of them
to serve as the segment primary edge port. You can also optionally configure where to send segment
topology change notices (STCNs) and VLAN load balancing.
• Default REP Configuration, page 19-7
• REP Configuration Guidelines, page 19-7
• Configuring the REP Administrative VLAN, page 19-9
• Configuring REP Interfaces, page 19-10
• Setting Manual Preemption for VLAN Load Balancing, page 19-14
• Configuring SNMP Traps for REP, page 19-14
• If you connect an STP network to the REP segment, be sure that the connection is at the segment
edge. An STP connection that is not at the edge could cause a bridging loop because STP does not
run on REP segments. All STP BPDUs are dropped at REP interfaces.
• You must configure all trunk ports in the segment with the same set of allowed VLANs, or a
misconfiguration occurs.
• REP ports follow these rules:
– There is no limit to the number of REP ports on a switch; however, only two ports on a switch
can belong to the same REP segment.
– If only one port on a switch is configured in a segment, the port should be an edge port.
– If two ports on a switch belong to the same segment, they must be both edge ports, both regular
segment ports, or one regular port and one edge no-neighbor port. An edge port and regular
segment port on a switch cannot belong to the same segment.
– If two ports on a switch belong to the same segment and one is configured as an edge port and
one as a regular segment port (a misconfiguration), the edge port is treated as a regular segment
port.
• REP interfaces come up in a blocked state and remains in a blocked state until notified that it is safe
to unblock. You need to be aware of this to avoid sudden connection losses.
• REP sends all LSL PDUs in untagged frames on the native VLAN. The BPA message sent to the
Cisco multicast address is sent on the administration VLAN, which is VLAN 1 by default.
• You can configure how long a REP interface remains up without receiving a hello from a neighbor.
You can use the rep lsl-age-timer value interface configuration command to set the time from 120
to 10000 ms. The LSL hello timer is then set to the age-timer value divided by 3. In normal
operation, three LSL hellos are sent before the age timer on the peer switch expires and checks for
hello messages.
– In Cisco IOS Release 12.2(52)SE, the LSL age-timer range changes from 3000 to 10000 ms in
500-ms increments to 120 to 10000 ms in 40-ms increments. If the REP neighbor device is not
running Cisco IOS Release 12.2(52) or later, you must use the shorter time range because the
device does not accept values out of the earlier range.
– EtherChannel port channel interfaces do not support LSL age-timer values less than 1000 ms.
If you try to configure a value less than 1000 ms on a port channel, you receive an error message
and the command is rejected.
• REP ports cannot be configured as one of these port types:
– SPAN destination port
– Private VLAN port
– Tunnel port
– Access port
• You should not configure VLAN load balancing on an interface that carries Ethernet over
multiprotocol label switching (EoMPLS) traffic. VLAN load balancing across the REP ring might
prevent forwarding some of the EoMPLS traffic.
• REP is supported on EtherChannels, but not on an individual port that belongs to an EtherChannel.
• There is a maximum of 64 REP segments per switch.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 rep admin vlan vlan-id Specify the administrative VLAN. The range is 2 to 4094.
The default is VLAN 1. To set the admin VLAN to 1,
enter the no rep admin vlan global configuration
command.
Step 3 end Return to privileged EXEC mode.
Step 4 show interface [interface-id] rep detail Verify the configuration on one of the REP interfaces.
Step 5 copy running-config startup config (Optional) Save your entries in the switch startup
configuration file.
This example shows how to configure the administrative VLAN as VLAN 100 and verify the
configuration by entering the show interface rep detail command on one of the REP interfaces:
Switch# configure terminal
Switch (conf)# rep admin vlan 100
Switch (conf-if)# end
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface, and enter interface configuration mode. The
interface can be a physical Layer 2 interface or a port channel
(logical interface). The port-channel range is 1 to 48.
Step 3 switchport mode trunk Configure the interface as a Layer 2 trunk port.
On non-ES ports, you can also configure the encapsulation type by
entering the switchport trunk encapsulation {isl | dot1q |
negotiate} interface configuration command. ES ports support only
IEEE 802.1Q encapsulation.
Command Purpose
Step 4 rep segment segment-id [edge [no-neighbor] Enable REP on the interface, and identify a segment number. The
[primary]] [preferred] segment ID range is from 1 to 1024. These optional keywords are
available.
Note You must configure two edge ports, including one primary
edge port for each segment.
Command Purpose
Step 6 rep block port {id port-id | neighbor_offset | (Optional) Configure VLAN load balancing on the primary edge
preferred} vlan {vlan-list | all} port, identify the REP alternate port in one of three ways, and
configure the VLANs to be blocked on the alternate port.
• Enter the id port-id to identify the alternate port by port ID. The
port ID is automatically generated for each port in the segment.
You can view interface port IDs by entering the show interface
interface-id rep [detail] privileged EXEC command.
• Enter a neighbor_offset number to identify the alternate port as
a downstream neighbor from an edge port. The range is from
–256 to 256, with negative numbers indicating the downstream
neighbor from the secondary edge port. A value of 0 is invalid.
Enter -1 to identify the secondary edge port as the alternate port.
See Figure 19-4 on page 19-5 for an example of neighbor offset
numbering.
Note Because you enter this command at the primary edge port
(offset number 1), you would never enter an offset value of 1
to identify an alternate port.
Enter the no form of each command to return to the default configuration. Enter the show rep topology
privileged EXEC command to see which port in the segment is the primary edge port.
This example shows how to configure an interface as the primary edge port for segment 1, to send STCNs
to segments 2 through 5, and to configure the alternate port as the port with port ID 0009001818D68700
to block all VLANs after a preemption delay of 60 seconds after a segment port failure and recovery.
The interface is configured to remain up for 6000 milliseconds without receiving a hello from a neighbor.
Switch# configure terminal
Switch (conf)# interface gigabitethernet1/0/1
Switch (conf-if)# rep segment 1 edge primary
Switch (conf-if)# rep stcn segment 2-5
Switch (conf-if)# rep block port 0009001818D68700 vlan all
Switch (conf-if)# rep preempt delay 60
Switch (conf-if)# rep lsl-age-timer 6000
Switch (conf-if)# end
This example shows how to configure the same configuration when the interface has no external REP
neighbor:
Switch# configure terminal
Switch (conf)# interface gigabitethernet1/0/1
Switch (conf-if)# rep segment 1 edge no-neighbor primary
Switch (conf-if)# rep stcn segment 2-5
Switch (conf-if)# rep block port 0009001818D68700 vlan all
Switch (conf-if)# rep preempt delay 60
Switch (conf-if)# rep lsl-age-timer 6000
This example shows how to configure the VLAN blocking configuration shown in Figure 19-5. The
alternate port is the neighbor with neighbor offset number 4. After manual preemption, VLANs 100 to
200 are blocked at this port, and all other VLANs are blocked at the primary edge port E1 (Gigabit
Ethernet port 1/0/1).
Switch# configure terminal
Switch (conf)# interface gigabitethernet1/0/1
Switch (conf-if)# rep segment 1 edge primary
Switch (conf-if)# rep block port 4 vlan 100-200
Switch (conf-if)# end
Note Do not configure VLAN load balancing on an interface that carries Ethernet over multiprotocol label
switching (EoMPLS) traffic. VLAN load balancing across the REP ring might prevent forwarding some
of the EoMPLS traffic.
Beginning in privileged EXEC mode, follow these steps on the switch that has the segment primary edge
port to manually trigger VLAN load balancing on a segment:
Command Purpose
Step 1 rep preempt segment segment-id Manually trigger VLAN load balancing on the segment.
You will need to confirm the command before it is executed.
Step 2 show rep topology View REP topology information.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 snmp mib rep trap-rate value Enable the switch to send REP traps, and set the number of
traps sent per second. The range is from 0 to 1000. The default
is 0 (no limit imposed; a trap is sent at every occurrence).
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify the REP trap configuration.
Step 5 copy running-config startup config (Optional) Save your entries in the switch startup configuration
file.
To remove the trap, enter the no snmp mib rep trap-rate global configuration command.
This example configures the switch to send REP traps at a rate of 10 per second:
Switch(config)# snmp mib rep trap-rate 10
Monitoring REP
Use the privileged EXEC commands in Table 19-1to monitor REP.
Command Purpose
show interface [interface-id] rep [detail] Displays REP configuration and status for an interface or for all interfaces.
show rep topology [segment segment_id] Displays REP topology information for a segment or for all segments,
[archive] [detail] including the primary and secondary edge ports in the segment.
This chapter describes how to configure Flex Links, a pair of interfaces on the Catalyst 3750 Metro
switch that provide a mutual backup. It also describes how to configure the MAC address-table move
update feature, also referred to as the Flex Links bidirectional fast convergence feature.
Note For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
Flex Links
Flex Links are a pair of a Layer 2 interfaces (switch ports or port channels) where one interface is
configured to act as a backup to the other. The feature provides an alternative solution to the Spanning
Tree Protocol (STP). Users can disable STP and still retain basic link redundancy. Flex Links are
typically configured in service provider or enterprise networks where customers do not want to run STP
on the switch. If the switch is running STP, Flex Links is not necessary because STP already provides
link-level redundancy or backup.
You configure Flex Links on one Layer 2 interface (the active link) by assigning another Layer 2
interface as the Flex Link or backup link. When one of the links is up and forwarding traffic, the other
link is in standby mode, ready to begin forwarding traffic if the other link shuts down. At any given time,
only one of the interfaces is in the linkup state and forwarding traffic. If the primary link shuts down,
the standby link starts forwarding traffic. When the active link comes back up, it goes into standby mode
and does not forward traffic. STP is disabled on Flex Link interfaces.
In Figure 20-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; the other is in standby mode.
If port 1 is the active link, it begins forwarding traffic between port 1 and switch B; the link between
port 2 (the backup link) and switch C is not forwarding traffic. If port 1 goes down, port 2 comes up and
starts forwarding traffic to switch C. When port 1 comes back up, it goes into standby mode and does
not forward traffic; port 2 continues forwarding traffic.
You can also choose to configure a preemption mechanism, specifying the preferred port for forwarding
traffic. In Figure 20-1, for example, you can configure the Flex Link pair with preemption mode so that
after port 1 comes back up in the scenario, and it has greater bandwidth than port 2, port 1 begins
forwarding after 60 seconds; and port 2 becomes the standby. You do this by entering the interface
configuration switchport backup interface preemption mode bandwidth and switchport backup
interface preemption delay commands.
Uplink Uplink
switch B switch C
Port 1 Port 2
Switch A 116082
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.
Uplink Uplink
switch B switch C
Forwarding Forwarding
(1-50) (51-100)
gi2/0/6 gi2/0/8
201398
Switch A
Configuration Examples
These are configuration examples for learning the other Flex Link port as the mrouter port when Flex
Link is configured on GigabitEthernet1/0/11 and GigabitEthernet1/0/12, and output for the
show interfaces switchport backup command:
Switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# interface GigabitEthernet1/0/11
Switch(config-if)# switchport trunk encapsulation dot1q
Switch(config-if)# switchport mode trunk
Switch(config-if)# switchport backup interface Gi1/0/12
Switch(config-if)# exit
Switch(config)# interface GigabitEthernet1/0/12
Switch(config-if)# switchport trunk encapsulation dot1q
Switch(config-if)# switchport mode trunk
Switch(config-if)# end
Switch# show interfaces switchport backup detail
Switch Backup Interface Pairs:
Active Interface Backup Interface State
GigabitEthernet1/0/11 GigabitEthernet1/0/12 Active Up/Backup Standby
Preemption Mode : off
Multicast Fast Convergence : Off
Bandwidth : 100000 Kbit (Gi1/0/11), 100000 Kbit (Gi1/0/12)
Mac Address Move Update Vlan : auto
This output shows a querier for VLANs 1 and 401, with their queries reaching the switch through
GigabitEthernet1/0/11:
Switch# show ip igmp snooping querier
Vlan IP Address IGMP Version Port
-------------------------------------------------------------
1 1.1.1.1 v2 Gi1/0/11
401 41.41.41.1 v2 Gi1/0/11
Here is output for the show ip igmp snooping mrouter command for VLANs 1 and 401:
Switch# show ip igmp snooping mrouter
Vlan ports
---- -----
1 Gi1/0/11(dynamic), Gi1/0/12(dynamic)
401 Gi1/0/11(dynamic), Gi1/0/12(dynamic)
Similarly, both Flex Link ports are part of learned groups. In this example, GigabitEthernet2/0/11 is a
receiver/host in VLAN 1, which is interested in two multicast groups:
Switch# show ip igmp snooping groups
Vlan Group Type Version Port List
-----------------------------------------------------------------------
1 228.1.5.1 igmp v2 Gi1/0/11, Gi1/0/12, Gi2/0/11
1 228.1.5.2 igmp v2 Gi1/0/11, Gi1/0/12, Gi2/0/11
When a host responds to the general query, the switch forwards this report on all the mrouter ports. In
this example, when a host sends a report for the group 228.1.5.1, it is forwarded only on
GigabitEthernet1/0/11, because the backup port GigabitEthernet1/0/12 is blocked. When the active link,
GigabitEthernet1/0/11, goes down, the backup port, GigabitEthernet1/0/12, begins forwarding.
As soon as this port starts forwarding, the switch sends proxy reports for the groups 228.1.5.1 and
228.1.5.2 on behalf of the host. The upstream router learns the groups and starts forwarding multicast
data. This is the default behavior of Flex Link. This behavior changes when the user configures fast
convergence using the switchport backup interface gigabitEthernet 1/0/12 multicast
fast-convergence command. This example shows turning on this feature:
Switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# interface gigabitEthernet 1/0/11
Switch(config-if)# switchport backup interface gigabitEthernet 1/0/12 multicast
fast-convergence
Switch(config-if)# exit
Switch# show interfaces switchport backup detail
Switch Backup Interface Pairs:
Active Interface Backup Interface State
------------------------------------------------------------------------
GigabitEthernet1/0/11 GigabitEthernet1/0/12 Active Up/Backup Standby
Preemption Mode : off
Multicast Fast Convergence : On
Bandwidth : 100000 Kbit (Gi1/0/11), 100000 Kbit (Gi1/0/12)
Mac Address Move Update Vlan : auto
This output shows a querier for VLAN 1 and 401 with their queries reaching the switch through
GigabitEthernet1/0/11:
Switch# show ip igmp snooping querier
Vlan IP Address IGMP Version Port
-------------------------------------------------------------
1 1.1.1.1 v2 Gi1/0/11
401 41.41.41.1 v2 Gi1/0/11
This is output for the show ip igmp snooping mrouter command for VLAN 1 and 401:
Switch# show ip igmp snooping mrouter
Vlan ports
---- -----
1 Gi1/0/11(dynamic), Gi1/0/12(dynamic)
401 Gi1/0/11(dynamic), Gi1/0/12(dynamic)
Similarly, both the Flex Link ports are a part of the learned groups. In this example,
GigabitEthernet2/0/11 is a receiver/host in VLAN 1, which is interested in two multicast groups:
Switch# show ip igmp snooping groups
Vlan Group Type Version Port List
-----------------------------------------------------------------------
1 228.1.5.1 igmp v2 Gi1/0/11, Gi1/0/12, Gi2/0/11
1 228.1.5.2 igmp v2 Gi1/0/11, Gi1/0/12, Gi2/0/11
Whenever a host responds to the general query, the switch forwards this report on all the mrouter ports.
When you turn on this feature through the command-line port, and when a report is forwarded by the
switch on GigabitEthernet1/0/11, it is also leaked to the backup port GigabitEthernet1/0/12. The
upstream router learns the groups and starts forwarding multicast data, which is dropped at the ingress
because GigabitEthernet1/0/12 is blocked. When the active link, GigabitEthernet1/0/11, goes down, the
backup port, GigabitEthernet1/0/12, begins forwarding. You do not need to send any proxy reports as
the multicast data is already being forwarded by the upstream router. By leaking reports to the backup
port, a redundant multicast path has been set up, and the time taken for the multicast traffic convergence
is very minimal.
Server
Switch C
Port 3 Port 4
Switch B Switch D
Port 1 Port 2
Switch A
141223
PC
Default Configuration
The Flex Links are not configured, and there are no backup interfaces defined.
The preemption mode is off.
The preemption delay is 35 seconds.
Flex Link VLAN load balancing is not configured.
The MAC address-table move update feature is not configured on the switch.
Configuration Guidelines
Follow these guidelines to configure Flex Links:
• You can configure up to 16 backup links.
• You can configure only one Flex Link 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 Link pair. An interface can be a backup link for only one
active link. An active link cannot belong to another Flex Link 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 (Fast Ethernet, Gigabit Ethernet, or port channel)
as the active link. However, you should configure both Flex Links with similar characteristics so that
there are no loops or changes in behavior if the standby link begins to forward traffic.
• STP is disabled on Flex Link ports. A Flex Link port does not participate in STP, even if the VLANs
present on the port are configured for STP. When STP is not enabled, be sure that there are no loops
in the configured topology.
Follow these guidelines to configure VLAN load balancing on the Flex Links feature:
• For Flex Link VLAN load balancing, you must choose the preferred VLANs on the backup interface.
• You cannot configure a preemption mechanism and VLAN load balancing for the same Flex Links
pair.
Follow these guidelines to configure MAC address-table move update feature:
• You can enable and configure this feature on the access switch to send the MAC address-table move
updates.
• You can enable and configure this feature on the uplink switches to get the MAC address-table move
updates.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface, and enter interface configuration
mode. The interface can be a physical Layer 2 interface or
a port channel (logical interface). The port-channel range
is 1 to 48.
Step 3 switchport backup interface interface-id Configure a physical Layer 2 interface (or port channel)
as part of a Flex Link pair with the interface. When one
link is forwarding traffic, the other interface is in standby
mode.
Step 4 end Return to privileged EXEC mode.
Step 5 show interface [interface-id] switchport backup Verify the configuration.
Step 6 copy running-config startup config (Optional) Save your entries in the switch startup
configuration file.
To disable a Flex Link backup interface, use the no switchport backup interface interface-id interface
configuration command.
This example shows how to configure an interface with a backup interface and to verify the
configuration:
Switch# configure terminal
Switch(conf)# interface fastethernet1/0/1
Switch(conf-if)# switchport backup interface fastethernet1/0/2
Switch(conf-if)# end
Switch# show interface switchport backup
Switch Backup Interface Pairs:
Beginning in privileged EXEC mode, follow these steps to configure a preemption scheme for a pair of
Flex Links:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface, and enter interface configuration
mode. The interface can be a physical Layer 2 interface or
a port channel (logical interface). The port-channel range
is 1 to 48.
Command Purpose
Step 3 switchport backup interface interface-id Configure a physical Layer 2 interface (or port channel)
as part of a Flex Link pair with the interface. When one
link is forwarding traffic, the other interface is in standby
mode.
Step 4 switchport backup interface interface-id preemption Configure a preemption mechanism and delay for a Flex
mode [forced | bandwidth | off] Link interface pair. You can configure the preemption
mode as:
• forced—the active interface always preempts the
backup
• bandwidth—the interface with higher bandwidth
always acts as the active interface
• off—no preemption happens from active to backup
Step 5 switchport backup interface interface-id preemption Configure the delay time until a port preempts another
delay delay-time port.
Note Setting a delay time only works with forced and
bandwidth modes.
Step 6 end Return to privileged EXEC mode.
Step 7 show interface [interface-id] switchport backup Verify the configuration.
Step 8 copy running-config startup config (Optional) Save your entries in the switch startup
configuration file.
To remove a preemption scheme, use the no switchport backup interface interface-id preemption
mode interface configuration command. To reset the delay time to the default, use the no switchport
backup interface interface-id preemption delay interface configuration command.
This example shows how to configure preemption mode as bandwidth, for a backup interface pair and to
verify the configuration:
Switch# configure terminal
Switch(conf)# interface gigabitethernet1/0/1
Switch(conf-if)# switchport backup interface gigabitethernet1/0/2
Switch(conf-if)# switchport backup interface gigabitethernet1/0/2 preemption mode forced
Switch(conf-if)# switchport backup interface gigabitethernet1/0/2 preemption delay 50
Switch(conf-if)# end
Switch# show interface switchport backup detail
Active Interface Backup Interface State
------------------------------------------------------------------------
GigabitEthernet1/0/21 GigabitEthernet1/0/2 Active Down/Backup Down
Interface Pair : Gi1/0/21, Gi1/0/2
Preemption Mode : forced
Preemption Delay : 50 seconds
Bandwidth : 10000 Kbit (Gi1/0/1), 10000 Kbit (Gi1/0/2)
Mac Address Move Update Vlan : auto
<output truncated>
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface, and enter interface configuration
mode. The interface can be a physical Layer 2 interface or
a port channel (logical interface). The port-channel range
is 1 to 48.
Step 3 switchport backup interface interface-id prefer vlan Configure a physical Layer 2 interface (or port channel)
vlan-range as part of a Flex Links pair with the interface, and specify
the VLANs carried on the interface. The VLAN ID range
is 1 to 4094.
Step 4 end Return to privileged EXEC mode.
Step 5 show interfaces [interface-id] switchport backup Verify the configuration.
Step 6 copy running-config startup config (Optional) Save your entries in the switch startup
configuration file.
To disable the VLAN load balancing feature, use the no switchport backup interface interface-id
prefer vlan vlan-range interface configuration command.
In this example, VLANs 1 to 50, 60, and 100 to 120 are configured on the switch:
Switch(config)# interface fastEthernet 1/0/6
Switch(config-if)# switchport backup interface fastEthernet 1/0/8 prefer vlan 60,100-120
When both interfaces are up, Fast Ethernet port1/0/8 forwards traffic for VLANs 60 and 100 to 120 and
Fast Ethernet port 1/0/6 forwards traffic for VLANs 1 to 50.
Switch# show interfaces switchport backup
Switch Backup Interface Pairs:
When a Flex Link interface goes down (LINK_DOWN), VLANs preferred on this interface are moved
to the peer interface of the Flex Link pair. In this example, if interface 1/0/6 goes down, interface 1/0/8
carries all VLANs of the Flex Link pair.
Switch# show interfaces switchport backup
Switch Backup Interface Pairs:
When a Flex Link interface comes up, VLANs preferred on this interface are blocked on the peer
interface and moved to the forwarding state on the interface that has just come up. In this example, if
interface Fast Ethernet port 1/0/6 comes up, VLANs preferred on this interface are blocked on the peer
interface Fast Ethernet port 1/0/8 and forwarded on Fast Ethernet port 1//0/6.
Switch# show interfaces switchport backup
Switch Backup Interface Pairs:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface, and enter interface configuration
mode. The interface can be a physical Layer 2 interface or
a port channel (logical interface). The port-channel range
is 1 to 48.
Step 3 switchport backup interface interface-id Configure a physical Layer 2 interface (or port channel),
as part of a Flex Link pair with the interface. The MAC
address-table move update VLAN is the lowest VLAN ID
or on the interface.
switchport backup interface interface-id mmu Configure a physical Layer 2 interface (or port channel)
primary vlan vlan-id and specify the VLAN ID on the interface, which is used
for sending the MAC address-table move update.
When one link is forwarding traffic, the other interface is
in standby mode.
Command Purpose
Step 4 end Return to global configuration mode.
Step 5 mac address-table move update transmit Enable the access switch to send MAC address-table
move updates to other switches in the network if the
primary link goes down and the switch starts forwarding
traffic through the standby link.
Step 6 end Return to privileged EXEC mode.
Step 7 show mac address-table move update Verify the configuration.
Step 8 copy running-config startup config (Optional) Save your entries in the switch startup
configuration file.
To disable the MAC address-table move update feature on the access switch, use the no mac
address-table move update transmit interface configuration command. To display the MAC
address-table move update information, use the show mac address-table move update privileged
EXEC command.
This example shows how to configure an access switch to send MAC address-table move update
messages and to verify the configuration:
Switch# configure terminal
Switch(conf)# interface fastethernet1/0/1
Switch(conf-if)# switchport backup interface fastethernet1/0/2 mmu primary vlan 2
Switch(conf-if)# end
Switch(conf)# mac address-table move update transmit
Switch(conf)# end
Switch# show mac-address-table move update
Switch-ID : 01d0.2bfc.3180
Dst mac-address : 0180.c200.0010
Vlans/Macs supported : 1023/8320
Default/Current settings: Rcv Off/Off, Xmt Off/Off
Max packets per min : Rcv 40, Xmt 60
Rcv packet count : 0
Rcv conforming packet count : 0
Rcv invalid packet count : 0
Rcv packet count this min : 0
Rcv threshold exceed count : 0
Rcv last sequence# this min : 0
Rcv last interface : None
Rcv last src-mac-address : 0000.0000.0000
Rcv last switch-ID : 0000.0000.0000
Xmt packet count : 0
Xmt packet count this min : 0
Xmt threshold exceed count : 0
Xmt pak buf unavail cnt : 0
Xmt last interface : None
Beginning in privileged EXEC mode, follow these steps to configure a switch to get and process MAC
address-table move update messages:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 mac address-table move update receive Enable the switch to get and process the MAC
address-table move updates.
Step 3 end Return to privileged EXEC mode.
Step 4 show mac address-table move update Verify the configuration.
Step 5 copy running-config startup config (Optional) Save your entries in the switch startup
configuration file.
To disable the MAC address-table move update feature on the access switch, use the no mac
address-table move update receive configuration command. To display the MAC address-table move
update information, use the show mac address-table move update privileged EXEC command.
This example shows how to configure a switch to get and process MAC address-table move update
messages:
Switch# configure terminal
Switch(conf)# mac address-table move update receive
Switch(conf)# end
Table 20-1 Flex Links and MAC Address-Table Move Update Monitoring Commands
Command Purpose
show interface [interface-id] switchport Displays the Flex Link backup interface configured for an interface or all the
backup configured Flex Links and the state of each active and backup interface (up or
standby mode).
show mac address-table move update Displays the MAC address-table move update information on the switch.
This chapter describes how to configure DHCP snooping and option-82 data insertion, and the DHCP
server port-based address allocation features on the Catalyst 3750 Metro switch. It also describes how
to configure the IP source guard feature.
Note For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release, and see the “DHCP Commands” section in the Cisco IOS IP Command
Reference, Volume 1 of 3: Addressing and Services, Release 12.2.
DHCP Server
The DHCP server assigns IP addresses from specified address pools on a switch or router to DHCP
clients and manages them. If the DHCP server cannot give the DHCP client the requested configuration
parameters from its database, it forwards the request to one or more secondary DHCP servers defined by
the network administrator.
DHCP Snooping
DHCP snooping is a DHCP security feature that provides network security by filtering untrusted DHCP
messages and by building and maintaining a DHCP snooping binding database, also referred to as a
DHCP snooping binding table. For more information about this database, see the “Displaying DHCP
Snooping Information” section on page 21-15.
DHCP snooping acts like a firewall between untrusted hosts and DHCP servers. You use DHCP snooping
to differentiate between untrusted interfaces connected to the end user and trusted interfaces connected
to the DHCP server or another switch.
Note For DHCP snooping to function properly, all DHCP servers must be connected to the switch through
trusted interfaces.
An untrusted DHCP message is a message that is received from outside the network or firewall. When
you use DHCP snooping in a service-provider environment, an untrusted message is sent from a device
that is not in the service-provider network, such as a customer’s switch. Messages from unknown devices
are untrusted because they can be sources of traffic attacks.
The DHCP snooping binding database has the MAC address, the IP address, the lease time, the binding
type, the VLAN number, and the interface information that corresponds to the local untrusted interfaces
of a switch. It does not have information regarding hosts interconnected with a trusted interface.
In a service-provider network, a trusted interface is connected to a port on a device in the same network.
An untrusted interface is connected to an untrusted interface in the network or to an interface on a device
that is not in the network.
When a switch receives a packet on an untrusted interface and the interface belongs to a VLAN in which
DHCP snooping is enabled, the switch compares the source MAC address and the DHCP client hardware
address. If the addresses match (the default), the switch forwards the packet. If the addresses do not
match, the switch drops the packet.
The switch drops a DHCP packet when one of these situations occurs:
• A packet from a DHCP server, such as a DHCPOFFER, DHCPACK, DHCPNAK, or
DHCPLEASEQUERY packet, is received from outside the network or firewall.
• A packet is received on an untrusted interface, and the source MAC address and the DHCP client
hardware address do not match.
• The switch receives a DHCPRELEASE or DHCPDECLINE broadcast message that has a MAC
address in the DHCP snooping binding database, but the interface information in the binding
database does not match the interface on which the message was received.
• A DHCP relay agent forwards a DHCP packet that includes a relay-agent IP address that is not
0.0.0.0, or the relay agent forwards a packet that includes option-82 information to an untrusted port.
If the switch is an aggregation switch supporting DHCP snooping and is connected to an edge switch
that is inserting DHCP option-82 information, the switch drops packets with option-82 information when
packets are received on an untrusted interface. If DHCP snooping is enabled and packets are received on
a trusted port, the aggregation switch does not learn the DHCP snooping bindings for connected devices
and cannot build a complete DHCP snooping binding database.
When option-82 information is inserted by an edge switch in software releases earlier than Cisco IOS
Release 12.2(25)EY, you cannot configure DHCP snooping on an aggregation switch because the DHCP
snooping bindings database will not be properly populated. You also cannot configure IP source guard
and dynamic Address Resolution Protocol (ARP) inspection on the switch unless you use static bindings
or ARP access control lists (ACLs).
In Cisco IOS Release 12.2(25)EY or later, when an aggregation switch can be connected to an edge
switch through an untrusted interface and you enter the ip dhcp snooping information option
allowed-trust global configuration command, the aggregation switch accepts packets with option-82
information from the edge switch. The aggregation switch learns the bindings for hosts connected
through an untrusted switch interface. The DHCP security features, such as dynamic ARP or IP source
guard, can still be enabled on the aggregation switch while the switch receives packets with option-82
information on ingress untrusted interfaces to which hosts are connected. The port on the edge switch
that connects to the aggregation switch must be configured as a trusted interface.
Note The DHCP option-82 feature is supported only when DHCP snooping is enabled globally and on the
VLANs to which subscriber devices using this feature are assigned.
Figure 21-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
(the Catalyst switch) is configured with a helper address to enable broadcast forwarding and to transfer
DHCP messages between the clients and the server.
DHCP
server
VLAN 10
98813
When you enable 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. By
default, the remote-ID suboption is the switch MAC address, and the circuit-ID suboption is the port
identifier, vlan-mod-port, from which the packet is received. Beginning with Cisco IOS
Release 12.2(25)SEE, you can configure the remote ID and circuit ID. For information on
configuring these suboptions, see the “Enabling DHCP Snooping and Option 82” section on
page 21-11.
• If the IP address of the relay agent is configured, the switch adds this 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,
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. Then the DHCP server
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. 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.
In the default suboption configuration, when the previously described sequence of events occurs, the
values in these fields in Figure 21-2 do not change:
• Circuit-ID suboption fields
– Suboption type
– Length of the suboption type
– Circuit-ID type
– Length of the circuit-ID type
2 8 0 6 MAC address
116300
Figure 21-3 shows the packet formats for user-configured remote-ID and circuit-ID suboptions. The
switch uses these packet formats when you globally enable DHCP snooping and enter the ip dhcp
snooping information option format remote-id global configuration command and the ip dhcp
snooping vlan information option format-type circuit-id string interface configuration command.
The values for these fields in the packets change from the default values when you configure the
remote-ID and circuit-ID suboptions:
• Circuit-ID suboption fields
– The circuit-ID type is 1.
– The length values are variable, depending on the length of the string that you configure.
145774
2 N+2 1 N ASCII Remote ID string or hostname
To keep the bindings when the switch reloads, you must use the DHCP snooping database agent. If the
agent is disabled, dynamic ARP or IP source guard is enabled, and the DHCP snooping binding database
has dynamic bindings, the switch loses its connectivity. If the agent is disabled and only DHCP snooping
is enabled, the switch does not lose its connectivity, but DHCP snooping might not prevent DCHP
spoofing attacks.
When reloading, the switch reads the binding file to build the DHCP snooping binding database. The
switch updates the file when the database changes.
When a switch learns of new bindings or when it loses bindings, the switch immediately updates the
entries in the database. The switch also updates the entries in the binding file. The frequency at which
the file is updated is based on a configurable delay, and the updates are batched. If the file is not updated
in a specified time (set by the write-delay and abort-timeout values), the update stops.
This is the format of the file that has the bindings:
<initial-checksum>
TYPE DHCP-SNOOPING
VERSION 1
BEGIN
<entry-1> <checksum-1>
<entry-2> <checksum-1-2>
...
...
<entry-n> <checksum-1-2-..-n>
END
Each entry in the file is tagged with a checksum value that the switch uses to verify the entries when it
reads the file. The initial-checksum entry on the first line distinguishes entries associated with the latest
file update from entries associated with a previous file update.
This is an example of a binding file:
2bb4c2a1
TYPE DHCP-SNOOPING
VERSION 1
BEGIN
192.1.168.1 3 0003.47d8.c91f 2BB6488E Fa1/0/4 21ae5fbb
192.1.168.3 3 0003.44d6.c52f 2BB648EB Fa1/0/4 1bdb223f
192.1.168.2 3 0003.47d9.c8f1 2BB648AB Fa1/0/4 584a38f0
END
When the switch starts and the calculated checksum value equals the stored checksum value, the switch
reads entries from the binding file and adds the bindings to its DHCP snooping binding database. The
switch ignores an entry when one of these situations occurs:
• The switch reads the entry and the calculated checksum value does not equal the stored checksum
value. The entry and the ones following it are ignored.
• An entry has an expired lease time (the switch might not remove a binding entry when the lease time
expires).
• The interface in the entry no longer exists on the system.
• The interface is a routed interface or a DHCP snooping-trusted interface.
Note Do not enable Dynamic Host Configuration Protocol (DHCP) snooping on RSPAN VLANs. If
DHCP snooping is enabled on RSPAN VLANs, DHCP packets might not reach the RSPAN
destination port.
• When configuring a large number of circuit IDs on a switch, consider the impact of lengthy character
strings on the NVRAM or the flash memory. If the circuit-ID configurations, combined with other
data, exceed the capacity of the NVRAM or the flash memory, an error message appears.
• Before configuring the DHCP relay agent on your switch, make sure to configure the device that is
acting as the DHCP server. For example, you must specify the IP addresses that the DHCP server
can assign or exclude, configure DHCP options for devices, or set up the DHCP database agent.
• If the DHCP relay agent is enabled but DHCP snooping is disabled, the DHCP option-82 data
insertion feature is not supported.
• If a switch port is connected to a DHCP server, configure a port as trusted by entering the ip dhcp
snooping trust interface configuration command.
• If a switch port is connected to a DHCP client, configure a port as untrusted by entering the no ip
dhcp snooping trust interface configuration command.
• Follow these guidelines when configuring the DHCP snooping binding database:
– Because both NVRAM and the flash memory have limited storage capacity, we recommend that
you store the binding file on a TFTP server.
– For network-based URLs (such as TFTP and FTP), you must create an empty file at the
configured URL before the switch can write bindings to the binding file at that URL. See the
documentation for your TFTP server to determine whether you must first create an empty file
on the server; some TFTP servers cannot be configured this way.
– To ensure that the lease time in the database is accurate, we recommend that you enable and
configure NTP. For more information, see the “NTP Version 4” section on page 5-3.
– If NTP is configured, the switch writes binding changes to the binding file only when the switch
system clock is synchronized with NTP.
• Do not enter the ip dhcp snooping information option allowed-untrusted command on an
aggregation switch to which an untrusted device is connected. If you enter this command, an
untrusted device might spoof the option-82 information.
• Starting with Cisco IOS Release 12.2(37)SE, you can display DHCP snooping statistics by entering
the show ip dhcp snooping statistics user EXEC command, and you can clear the snooping
statistics counters by entering the clear ip dhcp snooping statistics privileged EXEC command.
Note Do not enable Dynamic Host Configuration Protocol (DHCP) snooping on RSPAN VLANs. If
DHCP snooping is enabled on RSPAN VLANs, DHCP packets might not reach the RSPAN
destination port.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 service dhcp Enable the DHCP server and relay agent on your switch. By default, this
feature is enabled.
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable the DHCP server and relay agent, use the no service dhcp global configuration command.
See the “Configuring DHCP” section of the “IP Addressing and Services” section of the Cisco IOS IP
Configuration Guide, Release 12.2 for these procedures:
• Checking (validating) the relay agent information
• Configuring the relay agent forwarding policy
Beginning in privileged EXEC mode, follow these steps to specify the packet forwarding address:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface vlan vlan-id Enter interface configuration mode, and create a
switch virtual interface.
Step 3 ip address ip-address subnet-mask Configure the interface with an IP address and an IP
subnet.
Step 4 ip helper-address address Specify the DHCP packet forwarding address.
The helper address can be a specific DHCP server
address, or it can be the network address if other
DHCP servers are on the destination network
segment. Using the network address enables other
servers to respond to DHCP requests.
If you have multiple servers, you can configure one
helper address for each server.
Step 5 exit Return to global configuration mode.
Step 6 interface range port-range Configure multiple physical ports that are connected
to the DHCP clients, and enter interface range
configuration mode.
or or
interface interface-id Configure a single physical port that is connected to
the DHCP client, and enter interface configuration
mode.
Step 7 switchport mode access Define the VLAN membership mode for the port.
Step 8 switchport access vlan vlan-id Assign the ports to the same VLAN as configured in
Step 2.
Step 9 end Return to privileged EXEC mode.
Step 10 show running-config Verify your entries.
Step 11 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove the DHCP packet forwarding address, use the no ip helper-address address interface
configuration command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip dhcp snooping Enable DHCP snooping globally.
Command Purpose
Step 3 ip dhcp snooping vlan vlan-range Enable DHCP snooping on a VLAN or range of VLANs. The range is 1
to 4094.
You can enter a single VLAN ID identified by VLAN ID number, a series
of VLAN IDs separated by commas, a range of VLAN IDs separated by
hyphens, or a range of VLAN IDs separated by entering the starting and
ending VLAN IDs separated by a space.
Step 4 ip dhcp snooping information option Enable the switch to insert and remove DHCP relay information
(option-82 field) in forwarded DHCP request messages to the DHCP
server.
The default is enabled.
Step 5 ip dhcp snooping information option (Optional) Configure the remote-ID suboption.
format remote-id [string ASCII-string |
You can configure the remote ID to be:
hostname]
• String of up to 63 ASCII characters (no spaces)
• Configured hostname for the switch
Note If the hostname is longer than 63 characters, it is truncated to 63
characters in the remote-ID configuration.
Command Purpose
Step 10 ip dhcp snooping limit rate rate (Optional) Configure the number of DHCP packets per second than an
interface can receive. The range is 1 to 2048. The default is no rate limit
configured.
Note We recommend an untrusted rate limit of not more than 100
packets per second. If you configure rate limiting for trusted
interfaces, you might need to increase the rate limit if the port is
a trunk port assigned to more than one VLAN with DHCP
snooping.
Step 11 exit Return to global configuration mode.
Step 12 ip dhcp snooping verify mac-address (Optional) Configure the switch to verify that the source MAC address in
a DHCP packet that is received on untrusted ports matches the client
hardware address in the packet. The default is to verify that the source
MAC address matches the client hardware address in the packet.
Step 13 end Return to privileged EXEC mode.
Step 14 show running-config Verify your entries.
Step 15 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable DHCP snooping, use the no ip dhcp snooping global configuration command. To disable
DHCP snooping on a VLAN or range of VLANs, use the no ip dhcp snooping vlan vlan-range global
configuration command. To disable the insertion and removal of the option-82 field, use the no ip dhcp
snooping information option global configuration command. To configure an aggregation switch to
drop incoming DHCP snooping packets with option-82 information from an edge switch, use the no ip
dhcp snooping information option allowed-untrusted global configuration command.
This example shows how to enable DHCP snooping globally and on VLAN 10 and to configure a rate
limit of 100 packets per second on a port:
Switch(config)# ip dhcp snooping
Switch(config)# ip dhcp snooping vlan 10
Switch(config)# ip dhcp snooping information option
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# ip dhcp snooping limit rate 100
The show ip dhcp snooping privileged EXEC command output shows all VLANs, including primary
and secondary private VLANs, on which DHCP snooping is enabled.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip dhcp snooping database Specify the URL for the database agent or the binding file by using one
{flash:/filename | of these forms:
ftp://user:password@host/filename |
• flash:/filename
http://[[username:password]@]
{hostname | host-ip}[/directory] • ftp://user:password@host/filename
/image-name.tar | • http://[[username:password]@]{hostname |
rcp://user@host/filename} host-ip}[/directory]/image-name.tar
• rcp://user@host/filename
• tftp://host/filename
Step 3 ip dhcp snooping database timeout Specify (in seconds) how long to wait for the database transfer process to
seconds finish before stopping.
The range is from 0 to 86400. Use 0 for an infinite duration. The default
is 300 seconds (5 minutes).
Step 4 ip dhcp snooping database write-delay Specify the duration for which the transfer should be delayed after the
seconds binding database changes. The range is from 15 to 86400 seconds. The
default is 300 seconds (5 minutes).
Step 5 end Return to privileged EXEC mode.
Step 6 ip dhcp snooping binding mac-address (Optional) Add binding entries to the DHCP snooping binding database.
vlan vlan-id ip-address interface The vlan-id range is from 1 to 4904. The seconds range is from 1 to
interface-id expiry seconds 4294967295.
Enter this command for each entry that you add.
Note Use this command when you are testing or debugging the switch.
Step 7 show ip dhcp snooping database Display the status and statistics of the DHCP snooping binding database
[detail] agent.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
To stop using the database agent and binding files, use the no ip dhcp snooping database global
configuration command. To reset the timeout or delay values, use the ip dhcp snooping database
timeout seconds or the ip dhcp snooping database write-delay seconds global configuration
command.
To clear the statistics of the DHCP snooping binding database agent, use the clear ip dhcp snooping
database statistics privileged EXEC command. To renew the database, use the renew ip dhcp snooping
database privileged EXEC command.
To delete binding entries from the DHCP snooping binding database, use the no ip dhcp snooping
binding mac-address vlan vlan-id ip-address interface interface-id privileged EXEC command. Enter
this command for each entry that you want to delete.
Command Purpose
show ip dhcp snooping Displays the DHCP snooping configuration for a switch
show ip dhcp snooping binding Displays only the dynamically configured bindings in the DHCP snooping binding
database, also referred to as a binding table.1
show ip dhcp snooping database Displays the DHCP snooping binding database status and statistics.
show ip dhcp snooping statistics Displays the DHCP snooping statistics in summary or detail form.
show ip source binding Display the dynamically and statically configured bindings.
1. If DHCP snooping is enabled and an interface changes to the down state, the switch does not delete the manually configured bindings.
Note If DHCP snooping is enabled and an interface changes to the down state, the switch does not delete the
statically configured bindings.
Note The port ACL takes precedence over any router ACLs or VLAN maps that affect the same interface.
The IP source binding table bindings are learned by DHCP snooping or are manually configured (static
IP source bindings). An entry in this table has an IP address with its associated MAC address and VLAN
number. The switch uses the IP source binding table only when IP source guard is enabled.
IPSG is supported only on Layer 2 ports, including access and trunk ports.You can configure IPSG with
source IP address filtering or with source IP and MAC address filtering.
Note Do not use IPSG for static hosts on uplink ports or trunk ports.
IPSG for static hosts extends the IPSG capability to non-DHCP and static environments. The previous
IPSG used the entries created by DHCP snooping to validate the hosts connected to a switch. Any traffic
received from a host without a valid DHCP binding entry is dropped. This security feature restricts IP
traffic on nonrouted Layer 2 interfaces. It filters traffic based on the DHCP snooping binding database
and on manually configured IP source bindings. The previous version of IPSG required a DHCP
environment for IPSG to work.
IPSG for static hosts allows IPSG to work without DHCP. IPSG for static hosts relies on IP device
tracking-table entries to install port ACLs. The switch creates static entries based on ARP requests or
other IP packets to maintain the list of valid hosts for a given port. You can also specify the number of
hosts allowed to send traffic to a given port. This is equivalent to port security at Layer 3.
IPSG for static hosts also supports dynamic hosts. If a dynamic host receives a DHCP-assigned IP
address that is available in the IP DHCP snooping table, the same entry is learned by the IP device
tracking table. When you enter the show ip device tracking all EXEC command, the IP device tracking
table displays the entries as ACTIVE.
Note Some IP hosts with multiple network interfaces can inject some invalid packets into a network
interface. The invalid packets contain the IP or MAC address for another network interface of
the host as the source address. The invalid packets can cause IPSG for static hosts to connect to
the host, to learn the invalid IP or MAC address bindings, and to reject the valid bindings.
Consult the vender of the corresponding operating system and the network interface to prevent
the host from injecting invalid packets.
IPSG for static hosts initially learns IP or MAC bindings dynamically through an ACL-based snooping
mechanism. IP or MAC bindings are learned from static hosts by ARP and IP packets. They are stored
in the device tracking database. When the number of IP addresses that have been dynamically learned or
statically configured on a given port reaches a maximum, the hardware drops any packet with a new IP
address. To resolve hosts that have moved or gone away for any reason, IPSG for static hosts leverages
IP device tracking to age out dynamically learned IP address bindings. This feature can be used with
DHCP snooping. Multiple bindings are established on a port that is connected to both DHCP and static
hosts. For example, bindings are stored in both the device tracking database as well as in the DHCP
snooping binding database.
• When IP source guard with source IP filtering is enabled on an interface, DHCP snooping must be
enabled on the access VLAN for that interface.
• If you are enabling IP source guard on a trunk interface with multiple VLANs and DHCP snooping
is enabled on all the VLANs, the source IP address filter is applied on all the VLANs.
Note If IP source guard is enabled and you enable or disable DHCP snooping on a VLAN on the
trunk interface, the switch might not properly filter traffic.
• If you enable IP source guard with source IP and MAC address filtering, DHCP snooping and port
security must be enabled on the interface. You must also enter the ip dhcp snooping information
option global configuration command and ensure that the DHCP server supports option 82. When
IP source guard is enabled with MAC address filtering, the DHCP host MAC address is not learned
until the host is granted a lease. When forwarding packets from the server to the host, DHCP
snooping uses option-82 data to identify the host port.
• When configuring IP source guard on interfaces on which a private VLAN is configured, port
security is not supported.
• IP source guard is not supported on EtherChannels.
• You can enable this feature when IEEE 802.1x port-based authentication is enabled.
• If the number of ternary content addressable memory (TCAM) entries exceeds the maximum
available, the CPU usage increases.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and specify the interface to be
configured.
Step 3 ip verify source Enable IP source guard with source IP address filtering.
or
ip verify source port-security Enable IP source guard with source IP and MAC address filtering.
Note When you enable both IP source guard and port security, using
the ip verify source port-security interface configuration
command, there are two caveats:
• The DHCP server must support option 82, or the client is not
assigned an IP address.
• The MAC address in the DHCP packet is not learned as a secure
address. The MAC address of the DHCP client is learned as a
secure address only when the switch receives non-DHCP data
traffic.
Step 4 exit Return to global configuration mode.
Step 5 ip source binding mac-address vlan Add a static IP source binding.
vlan-id ip-address inteface interface-id
Enter this command for each static binding.
Command Purpose
Step 6 end Return to privileged EXEC mode.
Step 7 show ip verify source [interface Verify the IP source guard configuration.
interface-id]
Step 8 show ip source binding [ip-address] Display the IP source bindings on the switch, on a specific VLAN, or on
[mac-address] [dhcp-snooping | static] a specific interface.
[inteface interface-id] [vlan vlan-id]
Step 9 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable IP source guard with source IP address filtering, use the no ip verify source interface
configuration command.
To delete a static IP source binding entry, use the no ip source global configuration command.
This example shows how to enable IP source guard with source IP and MAC filtering on VLANs 10
and 11:
Switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# ip verify source port-security
Switch(config-if)# exit
Switch(config)# ip source binding 0100.0022.0010 vlan 10 10.0.0.2 interface
gigabitethernet1/0/1
Switch(config)# ip source binding 0100.0230.0002 vlan 11 10.0.0.4 interface
gigabitethernet1/0/1
Switch(config)# end
Note You must configure the ip device tracking maximum limit-number interface configuration command
globally for IPSG for static hosts to work. If you only configure this command on a port without enabling
IP device tracking globally or by setting an IP device tracking maximum on that interface, IPSG with
static hosts rejects all the IP traffic from that interface. This requirement also applies to IPSG with static
hosts on a private VLAN host port.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip device tracking Turn on the IP host table, and globally enable IP device
tracking.
Step 3 interface interface-id Enter interface configuration mode.
Command Purpose
Step 4 switchport mode access Configure a port as access.
Step 5 switchport access vlan vlan-id Configure the VLAN for this port.
Step 6 ip verify source tracking port-security Enable IPSG for static hosts with MAC address filtering.
Note When you enable both IP source guard and port
security by using the ip verify source
port-security interface configuration command:
This example shows how to stop IPSG with static hosts on an interface.
Switch(config-if)# no ip verify source
Switch(config-if)# no ip device tracking max
This example shows how to enable IPSG with static hosts on a port.
Switch(config)# ip device tracking
Switch(config)# ip device tracking max 10
Switch(config-if)# ip verify source tracking port-security
This example shows how to enable IPSG for static hosts with IP filters on a Layer 2 access port and to
verify the valid IP bindings on the interface Gi1/0/3:
This example shows how to enable IPSG for static hosts with IP-MAC filters on a Layer 2 access port,
to verify the valid IP-MAC bindings on the interface Gi1/0/3, and to verify that the number of bindings
on this interface has reached the maximum:
Switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# ip device tracking
Switch(config)# interface gigabitethernet1/0/3
Switch(config-if)# switchport mode access
Switch(config-if)# switchport access vlan 1
Switch(config-if)# ip device tracking maximum 5
Switch(config-if)# switchport port-security
Switch(config-if)# switchport port-security maximum 5
Switch(config-if)# ip verify source tracking port-security
Switch(config-if)# end
This example displays all IP or MAC binding entries for all interfaces. The CLI displays all active as
well as inactive entries. When a host is learned on a interface, the new entry is marked as active. When
the same host is disconnected from that interface and connected to a different interface, a new IP or MAC
binding entry displays as active as soon as the host is detected. The old entry for this host on the previous
interface is marked as INACTIVE.
Switch# show ip device tracking all
IP Device Tracking = Enabled
IP Device Tracking Probe Count = 3
IP Device Tracking Probe Interval = 30
---------------------------------------------------------------------
IP Address MAC Address Vlan Interface STATE
---------------------------------------------------------------------
200.1.1.8 0001.0600.0000 8 GigabitEthernet1/0/1 INACTIVE
200.1.1.9 0001.0600.0000 8 GigabitEthernet1/0/1 INACTIVE
200.1.1.10 0001.0600.0000 8 GigabitEthernet1/0/1 INACTIVE
200.1.1.1 0001.0600.0000 9 GigabitEthernet1/0/2 ACTIVE
200.1.1.1 0001.0600.0000 8 GigabitEthernet1/0/1 INACTIVE
200.1.1.2 0001.0600.0000 9 GigabitEthernet1/0/2 ACTIVE
200.1.1.2 0001.0600.0000 8 GigabitEthernet1/0/1 INACTIVE
200.1.1.3 0001.0600.0000 9 GigabitEthernet1/0/2 ACTIVE
This example displays all active IP or MAC binding entries for all interfaces:
Switch# show ip device tracking all active
IP Device Tracking = Enabled
IP Device Tracking Probe Count = 3
IP Device Tracking Probe Interval = 30
---------------------------------------------------------------------
IP Address MAC Address Vlan Interface STATE
---------------------------------------------------------------------
200.1.1.1 0001.0600.0000 9 GigabitEthernet1/0/1 ACTIVE
200.1.1.2 0001.0600.0000 9 GigabitEthernet1/0/1 ACTIVE
200.1.1.3 0001.0600.0000 9 GigabitEthernet1/0/1 ACTIVE
200.1.1.4 0001.0600.0000 9 GigabitEthernet1/0/1 ACTIVE
200.1.1.5 0001.0600.0000 9 GigabitEthernet1/0/1 ACTIVE
This example displays all inactive IP or MAC binding entries for all interfaces. The host was first learned
on GigabitEthernet 1/0/1 and then moved to GigabitEthernet1/ 0/2. the IP or MAC binding entries
learned on GigabitEthernet1/ 0/1 are marked as inactive.
Switch# show ip device tracking all inactive
IP Device Tracking = Enabled
IP Device Tracking Probe Count = 3
IP Device Tracking Probe Interval = 30
---------------------------------------------------------------------
IP Address MAC Address Vlan Interface STATE
---------------------------------------------------------------------
200.1.1.8 0001.0600.0000 8 GigabitEthernet1/0/1 INACTIVE
200.1.1.9 0001.0600.0000 8 GigabitEthernet1/0/1 INACTIVE
200.1.1.10 0001.0600.0000 8 GigabitEthernet1/0/1 INACTIVE
200.1.1.1 0001.0600.0000 8 GigabitEthernet1/0/1 INACTIVE
200.1.1.2 0001.0600.0000 8 GigabitEthernet1/0/1 INACTIVE
200.1.1.3 0001.0600.0000 8 GigabitEthernet1/0/1 INACTIVE
200.1.1.4 0001.0600.0000 8 GigabitEthernet1/0/1 INACTIVE
200.1.1.5 0001.0600.0000 8 GigabitEthernet1/0/1 INACTIVE
200.1.1.6 0001.0600.0000 8 GigabitEthernet1/0/1 INACTIVE
200.1.1.7 0001.0600.0000 8 GigabitEthernet1/0/1 INACTIVE
This example displays the count of all IP device tracking host entries for all interfaces:
Switch# show ip device tracking all count
Total IP Device Tracking Host entries: 5
---------------------------------------------------------------------
Interface Maximum Limit Number of Entries
---------------------------------------------------------------------
Gi1/0/3 5
Configuring IP Source Guard for Static Hosts on a Private VLAN Host Port
Note You must globally configure the ip device tracking maximum limit-number interface configuration
command globally for IPSG for static hosts to work. If you only configure this command on a port
without enabling IP device tracking globally or setting an IP device tracking maximum on that interface,
IPSG with static hosts will reject all the IP traffic from that interface. This requirement also applies to
IPSG with static hosts on a Layer 2 access port.
Beginning in privileged EXEC mode, follow these steps to configure IPSG for static hosts with IP filters
on a Layer 2 access port:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 vlan vlan-id1 Enter VLAN configuration mode.
Step 3 private-vlan primary Establish a primary VLAN on a private VLAN port.
Step 4 exit Exit VLAN configuration mode.
Step 5 vlan vlan-id2 Enter configuration VLAN mode for another VLAN.
Step 6 private-vlan isolated Establish an isolated VLAN on a private VLAN port.
Step 7 exit Exit VLAN configuration mode.
Step 8 vlan vlan-id1 Enter configuration VLAN mode.
Step 9 private-vlan association 201 Associate the VLAN on an isolated private VLAN port.
Step 10 exit Exit VLAN configuration mode.
Step 11 interface fastEthernet interface-id Enter interface configuration mode.
Step 12 switchport mode private-vlan host (Optional) Establish a port as a private VLAN host.
Step 13 switchport private-vlan host-association vlan-id1 (Optional) Associate this port with the corresponding
vlan-id2 private VLAN.
Step 14 ip device tracking maximum number Establish a maximum for the number of static IPs that
the IP device tracking table allows on the port.
The maximum is 10.
This example shows how to enable IPSG for static hosts with IP filters on a private VLAN host port:
Switch(config)# vlan 200
Switch(config-vlan)# private-vlan primary
Switch(config-vlan)# exit
Switch(config)# vlan 201
Switch(config-vlan)# private-vlan isolated
Switch(config-vlan)# exit
Switch(config)# vlan 200
Switch(config-vlan)# private-vlan association 201
Switch(config-vlan)# exit
Switch(config)# int gigabitethernet1/0/3
Switch(config-if)# switchport mode private-vlan host
Switch(config-if)# switchport private-vlan host-association 200 201
Switch(config-if)# ip device tracking maximum 8
Switch(config-if)# ip verify source tracking
The output shows the five valid IP-MAC bindings that have been learned on the interface Gi1/0/3. For
the private VLAN cases, the bindings are associated with primary VLAN ID. So, in this example, the
primary VLAN ID, 200, is shown in the table.
Switch# show ip verify source
Interface Filter-type Filter-mode IP-address Mac-address Vlan
--------- ----------- ----------- --------------- ----------------- ----
Gi1/0/3 ip trk active 40.1.1.23 200
Gi1/0/3 ip trk active 40.1.1.24 200
Gi1/0/3 ip trk active 40.1.1.20 200
GI1/0/3 ip trk active 40.1.1.21 200
GI1/0/3 ip trk active 40.1.1.22 200
Gi1/0/3 ip trk active 40.1.1.23 201
Gi1/0/3 ip trk active 40.1.1.24 201
Gi1/0/3 ip trk active 40.1.1.20 201
Gi1/0/3 ip trk active 40.1.1.21 201
Gi1/0/3 ip trk active 40.1.1.22 201
The output shows that the five valid IP-MAC bindings are on both the primary and secondary VLAN.
Command Purpose
show ip source binding Display the IP source bindings on a switch.
show ip verify source Display the IP source guard configuration on the switch.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip dhcp use subscriber-id client-id Configure the DHCP server to globally use the
subscriber identifier as the client identifier on all
incoming DHCP messages.
Step 3 ip dhcp subscriber-id interface-name Automatically generate a subscriber identifier based
on the short name of the interface.
A subscriber identifier configured on a specific
interface takes precedence over this command.
Step 4 interface interface-id Specify the interface to be configured, and enter
interface configuration mode.
Step 5 ip dhcp server use subscriber-id client-id Configure the DHCP server to use the subscriber
identifier as the client identifier on all incoming
DHCP messages on the interface.
Step 6 end Return to privileged EXEC mode.
Step 7 show running config Verify your entries.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
After enabling DHCP port-based address allocation on the switch, use the ip dhcp pool global
configuration command to preassign IP addresses and to associate them to clients. To restrict
assignments from the DHCP pool to preconfigured reservations, you can enter the reserved-only DHCP
pool configuration command. Unreserved addresses that are part of the network or on pool ranges are
not offered to the client, and other clients are not served by the pool. By entering this command, users
can configure a group of switches with DHCP pools that share a common IP subnet and that ignore
requests from clients of other switches.
Beginning in privileged EXEC mode follow these steps to preassign an IP address and to associate it to
a client identified by the interface name.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip dhcp pool poolname Enter DHCP pool configuration mode, and define the
name for the DHCP pool. The pool name can be a
symbolic string (such as Engineering) or an integer
(such as 0).
Step 3 network network-number [mask | /prefix-length] Specify the subnet network number and mask of the
DHCP address pool.
Step 4 address ip-address client-id string [ascii] Reserve an IP address for a DHCP client identified by
the interface name.
string—can be an ASCII value or a hexadecimal
value.
Step 5 reserved-only (Optional) Use only reserved addresses in the DHCP
address pool. The default is to not restrict pool
addresses.
Step 6 end Return to privileged EXEC mode.
Step 7 show ip dhcp pool Verify DHCP pool configuration.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable DHCP port-based address allocation, use the no ip dhcp use subscriber-id client-id global
configuration command. To disable the automatic generation of a subscriber identifier, use the no ip
dhcp subscriber-id interface-name global configuration command. To disable the subscriber identifier
on an interface, use the no ip dhcp server use subscriber-id client-id interface configuration command.
To remove an IP address reservation from a DHCP pool, use the no address ip-address client-id string
DHCP pool configuration command. To change the address pool to nonrestricted, enter the no
reserved-only DHCP pool configuration command.
In this example, a subscriber identifier is automatically generated, and the DHCP server ignores any
client identifier fields in the DHCP messages and uses the subscriber identifier instead. The subscriber
identifier is based on the short name of the interface and the client preassigned IP address 10.1.1.7.
switch# show running config
Building configuration...
Current configuration : 4899 bytes
!
version 12.2
!
hostname switch
!
no aaa new-model
clock timezone EST 0
ip subnet-zero
ip dhcp relay information policy removal pad
no ip dhcp use vrf connected
ip dhcp use subscriber-id client-id
ip dhcp subscriber-id interface-name
ip dhcp excluded-address 10.1.1.1 10.1.1.3
!
ip dhcp pool dhcppool
network 10.1.1.0 255.255.255.0
address 10.1.1.7 client-id “Et1/0” ascii
<output truncated>
This example shows that the preassigned address was correctly reserved in the DHCP pool:
switch# show ip dhcp pool dhcppool
Pool dhcp pool:
Utilization mark (high/low) : 100 / 0
Subnet size (first/next) : 0 / 0
Total addresses : 254
Leased addresses : 0
Excluded addresses : 4
Pending event : none
1 subnet is currently in the pool:
Current index IP address range Leased/Excluded/Total
10.1.1.1 10.1.1.1 - 10.1.1.254 0 / 4 / 254
1 reserved address is currently in the pool
Address Client
10.1.1.7 Et1/0
For more information about configuring the DHCP server port-based address allocation feature, go to
Cisco.com, and enter Cisco IOS IP Addressing Services in the Search field to access the Cisco IOS
software documentation. You can also access the documentation here:
http://www.cisco.com/en/US/docs/ios/ipaddr/command/reference/iad_book.html
Table 21-4 Commands for Displaying DHCP Port-Based Address Allocation Information
Command Purpose
show interface interface id Display the status and configuration of a specific interface.
show ip dhcp pool Display the DHCP address pools.
show ip dhcp binding Display address bindings on the Cisco IOS DHCP server.
This chapter describes how to configure dynamic Address Resolution Protocol inspection (dynamic ARP
inspection) on the Catalyst 3750 Metro switch. This feature helps prevent malicious attacks on the switch
by not relaying invalid ARP requests and responses to other ports in the same VLAN.
Note For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
A B
Host A Host B
(IA, MA) (IB, MB)
C
111750
Host C (man-in-the-middle)
(IC, MC)
Hosts A, B, and C are connected to the switch on interfaces A, B and C, all of which are on the same
subnet. Their IP and MAC addresses are shown in parentheses; for example, Host A uses IP address IA
and MAC address MA. When Host A needs to communicate to Host B at the IP layer, it broadcasts an
ARP request for the MAC address associated with IP address IB. When the switch and Host B receive
the ARP request, they populate their ARP caches with an ARP binding for a host with the IP address IA
and a MAC address MA; for example, IP address IA is bound to MAC address MA. When Host B
responds, the switch and Host A populate their ARP caches with a binding for a host with the IP address
IB and the MAC address MB.
Host C can poison the ARP caches of the switch, Host A, and Host B by broadcasting forged ARP
responses with bindings for a host with an IP address of IA (or IB) and a MAC address of MC. Hosts
with poisoned ARP caches use the MAC address MC as the destination MAC address for traffic intended
for IA or IB. This means that Host C intercepts that traffic. Because Host C knows the true MAC
addresses associated with IA and IB, it can forward the intercepted traffic to those hosts by using the
correct MAC address as the destination. Host C has inserted itself into the traffic stream from Host A to
Host B, the classic man-in-the middle attack.
Dynamic ARP inspection is a security feature that validates ARP packets in a network. It intercepts, logs,
and discards ARP packets with invalid IP-to-MAC address bindings. This capability protects the network
from certain man-in-the-middle attacks.
Dynamic ARP inspection 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
Dynamic ARP inspection 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.
You enable dynamic ARP inspection on a per-VLAN basis by using the ip arp inspection vlan
vlan-range global configuration command. For configuration information, see the “Configuring
Dynamic ARP Inspection in DHCP Environments” section on page 22-7.
In non-DHCP environments, dynamic ARP inspection can validate ARP packets against user-configured
ARP access control lists (ACLs) for hosts with statically configured IP addresses. You define an ARP
ACL by using the arp access-list acl-name global configuration command. For configuration
information, see the “Configuring ARP ACLs for Non-DHCP Environments” section on page 22-8. The
switch logs dropped packets. For more information about the log buffer, see the “Logging of Dropped
Packets” section on page 22-4.
You can configure dynamic ARP inspection 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. Use the ip arp inspection validate {[src-mac] [dst-mac] [ip]} global
configuration command. For more information, see the “Performing Validation Checks” section on
page 22-11.
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 22-2, assume that both Switch A and Switch B are running dynamic ARP inspection 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.
Figure 22-2 ARP Packet Validation on a VLAN Enabled for Dynamic ARP Inspection
DHCP server
Switch A Switch B
Port 1 Port 3
111751
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 dynamic ARP inspection, 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 dynamic ARP inspection.
Dynamic ARP inspection ensures that hosts (on untrusted interfaces) connected to a switch running
dynamic ARP inspection do not poison the ARP caches of other hosts in the network. However, dynamic
ARP inspection does not prevent hosts in other portions of the network from poisoning the caches of the
hosts that are connected to a switch running dynamic ARP inspection.
In cases in which some switches in a VLAN run dynamic ARP inspection and other switches do not,
configure the interfaces connecting such switches as untrusted. However, to validate the bindings of
packets from nondynamic ARP inspection switches, configure the switch running dynamic ARP
inspection with ARP ACLs. When you cannot determine such bindings, at Layer 3, isolate switches
running dynamic ARP inspection from switches not running dynamic ARP inspection switches. For
configuration information, see the “Configuring ARP ACLs for Non-DHCP Environments” section on
page 22-8.
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.
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 the Log Buffer”
section on page 22-12.
Note Do not enable Dynamic ARP inspection on RSPAN VLANs. If Dynamic ARP inspection is
enabled on RSPAN VLANs, Dynamic ARP inspection packets might not reach the RSPAN
destination port.
• 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 rate limit is calculated separately on each switch. For a cross-stack EtherChannel, this means
that the actual rate limit might be higher than the configured value. For example, if you set the rate
limit to 30 pps on an EtherChannel that has one port on switch 1 and one port on switch 2, each port
can receive packets at 29 pps without causing the EtherChannel to become error-disabled.
• 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 dynamic ARP
inspection-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.
• When you enable dynamic ARP inspection on the switch, policers that were configured to police
ARP traffic are no longer effective. The result is that all ARP traffic is sent to the CPU.
Note Dynamic ARP inspection 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 21, “Configuring DHCP Features and IP Source Guard.”
For information on how to configure dynamic ARP inspection when only one switch supports the
feature, see the “Configuring ARP ACLs for Non-DHCP Environments” section on page 22-8.
Beginning in privileged EXEC mode, follow these steps to configure dynamic ARP inspection. You must
perform this procedure on both switches. This procedure is required.
Command Purpose
Step 1 show cdp neighbors Verify the connection between the switches.
Step 2 configure terminal Enter global configuration mode.
Step 3 ip arp inspection vlan vlan-range Enable dynamic ARP inspection on a per-VLAN basis. By
default, dynamic ARP inspection is disabled on all VLANs.
For vlan-range, specify a single VLAN identified by VLAN ID
number, a range of VLANs separated by a hyphen, or a series of
VLANs separated by a comma. The range is 1 to 4094.
Specify the same VLAN ID for both switches.
Step 4 interface interface-id Specify the interface connected to the other switch, and enter
interface configuration mode.
Command Purpose
Step 5 ip arp inspection trust Configure the connection between the switches as trusted.
By default, all interfaces are untrusted.
The switch does not check ARP packets that it receives from the
other switch on the trusted interface. It simply forwards the
packets.
For 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 the Log Buffer” section
on page 22-12.
Step 6 end Return to privileged EXEC mode.
Step 7 show ip arp inspection interfaces Verify the dynamic ARP inspection configuration.
show ip arp inspection vlan vlan-range
Step 8 show ip dhcp snooping binding Verify the DHCP bindings.
Step 9 show ip arp inspection statistics vlan Check the dynamic ARP inspection statistics.
vlan-range
Step 10 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable dynamic ARP inspection, use the no ip arp inspection vlan vlan-range global configuration
command. To return the interfaces to an untrusted state, use the no ip arp inspection trust interface
configuration command.
This example shows how to configure dynamic ARP inspection on Switch A in VLAN 1. You would
perform a similar procedure on Switch B:
Switch(config)# ip arp inspection vlan 1
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# ip arp inspection trust
Beginning in privileged EXEC mode, follow these steps to configure an ARP ACL on Switch A. This
procedure is required in non-DHCP environments.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 arp access-list acl-name Define an ARP ACL, and enter ARP access-list
configuration mode. By default, no ARP access lists
are defined.
Note At the end of the ARP access list, there is an
implicit deny ip any mac any command.
Step 3 permit ip host sender-ip mac host sender-mac [log] Permit ARP packets from the specified host (Host 2).
• For sender-ip, enter the IP address of Host 2.
• For sender-mac, enter the MAC address of
Host 2.
• (Optional) Specify log to log a packet in the log
buffer when it matches the access control entry
(ACE). Matches are logged if you also configure
the matchlog keyword in the ip arp inspection
vlan logging global configuration command. For
more information, see the “Configuring the Log
Buffer” section on page 22-12.
Step 4 exit Return to global configuration mode.
Step 5 ip arp inspection filter arp-acl-name vlan vlan-range Apply the ARP ACL to the VLAN. By default, no
[static] defined ARP ACLs are applied to any VLAN.
• For arp-acl-name, specify the name of the ACL
created in Step 2.
• For vlan-range, specify the VLAN that the
switches and hosts are in. You can specify a
single VLAN identified by VLAN ID number, a
range of VLANs separated by a hyphen, or a
series of VLANs separated by a comma. The
range is 1 to 4094.
• (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.
Step 6 interface interface-id Specify the Switch A interface that is connected to
Switch B, and enter interface configuration mode.
Command Purpose
Step 7 no ip arp inspection trust Configure the Switch A interface that is connected to
Switch B as untrusted.
By default, all interfaces are untrusted.
For 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 the Log Buffer”
section on page 22-12.
Step 8 end Return to privileged EXEC mode.
Step 9 show arp access-list [acl-name] Verify your entries.
show ip arp inspection vlan vlan-range
show ip arp inspection interfaces
Step 10 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove the ARP ACL, use the no arp access-list global configuration command. To remove the ARP
ACL attached to a VLAN, use the no ip arp inspection filter arp-acl-name vlan vlan-range global
configuration command.
This example shows how to configure an ARP ACL called host2 on Switch A, to permit ARP packets
from Host 2 (IP address 1.1.1.1 and MAC address 0001.0001.0001), to apply the ACL to VLAN 1, and
to configure port 1 on Switch A as untrusted:
Switch(config)# arp access-list host2
Switch(config-arp-acl)# permit ip host 1.1.1.1 mac host 1.1.1
Switch(config-arp-acl)# exit
Switch(config)# ip arp inspection filter host2 vlan 1
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# no ip arp inspection trust
Note Unless you configure a rate limit on an interface, changing the trust state of the interface also changes
its rate limit to the default value for that trust state. After you configure the rate limit, the interface retains
the rate limit even when its trust state is changed. If you enter the no ip arp inspection limit interface
configuration command, the interface reverts to its default rate limit.
For configuration guidelines for rate limiting trunk ports and EtherChannel ports, see the “Dynamic ARP
Inspection Configuration Guidelines” section on page 22-6.
Beginning in privileged EXEC mode, follow these steps to limit the rate of incoming ARP packets. This
procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface to be rate-limited, and enter interface configuration
mode.
Step 3 ip arp inspection limit {rate pps [burst Limit the rate of incoming ARP requests and responses on the interface.
interval seconds] | none}
The default rate is 15 pps on untrusted interfaces and unlimited on
trusted interfaces. The burst interval is 1 second.
The keywords have these meanings:
• For rate pps, specify an upper limit for the number of incoming
packets processed per second. The range is 0 to 2048 pps.
• (Optional) For burst interval seconds, 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.
• For rate none, specify no upper limit for the rate of incoming ARP
packets that can be processed.
Step 4 exit Return to global configuration mode.
Step 5 errdisable recovery cause (Optional) Enable error recovery from the dynamic ARP inspection
arp-inspection interval interval error-disable state.
By default, recovery is disabled, and the recovery interval is 300
seconds.
For interval interval, specify the time in seconds to recover from the
error-disable state. The range is 30 to 86400.
Step 6 exit Return to privileged EXEC mode.
Step 7 show ip arp inspection interfaces Verify your settings.
show errdisable recovery
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default rate-limit configuration, use the no ip arp inspection limit interface
configuration command. To disable error recovery for dynamic ARP inspection, use the no errdisable
recovery cause arp-inspection global configuration command.
Beginning in privileged EXEC mode, follow these steps to perform specific checks on incoming ARP
packets. This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip arp inspection validate Perform a specific check on incoming ARP packets. By default, no checks
{[src-mac] [dst-mac] [ip]} are performed.
The keywords have these meanings:
• For src-mac, check 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.
• For dst-mac, check 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.
• For ip, check 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.
You must specify at least one of the keywords. Each command overrides the
configuration of the previous command; that is, if a command enables src
and dst mac validations, and a second command enables IP validation only,
the src and dst mac validations are disabled as a result of the second
command.
Step 3 exit Return to privileged EXEC mode.
Step 4 show ip arp inspection vlan Verify your settings.
vlan-range
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable checking, use the no ip arp inspection validate [src-mac] [dst-mac] [ip] global
configuration command. To display statistics for forwarded, dropped, and MAC and IP validation failure
packets, use the show ip arp inspection statistics privileged EXEC command.
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. A -- in the display appears in
place of all data except 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.
Beginning in privileged EXEC mode, follow these steps to configure the log buffer. This procedure is
optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip arp inspection log-buffer {entries Configure the dynamic ARP inspection logging buffer.
number | logs number interval
By default, when dynamic ARP inspection is enabled, denied or dropped
seconds}
ARP packets are logged. The number of log entries is 32. The number of
system messages is limited to 5 per second. The logging-rate interval is 1
second.
The keywords have these meanings:
• For entries number, specify the number of entries to be logged in the
buffer. The range is 0 to 1024.
• For logs number interval seconds, specify the number of entries to
generate system messages in the specified interval.
For logs number, 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 seconds, 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.
The logs and interval settings interact. If the logs number X is greater than
interval seconds Y, X divided by Y (X/Y) system messages are sent every
second. Otherwise, one system message is sent every Y divided by X (Y/X)
seconds.
Command Purpose
Step 3 ip arp inspection vlan vlan-range Control the type of packets that are logged per VLAN. By default, all denied
logging {acl-match {matchlog | or all dropped packets are logged. The term logged means the entry is placed
none} | dhcp-bindings {all | none | in the log buffer and a system message is generated.
permit}} The keywords have these meanings:
• For vlan-range, specify a single VLAN identified by VLAN ID number,
a range of VLANs separated by a hyphen, or a series of VLANs
separated by a comma. The range is 1 to 4094.
• For acl-match matchlog, log packets based on the ACE logging
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.
• For acl-match none, do not log packets that match ACLs.
• For dhcp-bindings all, log all packets that match DHCP bindings.
• For dhcp-bindings none, do not log packets that match DHCP
bindings.
• For dhcp-bindings permit, log DHCP-binding permitted packets.
Step 4 exit Return to privileged EXEC mode.
Step 5 show ip arp inspection log Verify your settings.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default log buffer settings, use the no ip arp inspection log-buffer {entries | logs}
global configuration command. To return to the default VLAN log settings, use the no ip arp inspection
vlan vlan-range logging {acl-match | dhcp-bindings} global configuration command. To clear the log
buffer, use the clear ip arp inspection log privileged EXEC command.
Command Description
show arp access-list [acl-name] Displays detailed information about ARP ACLs.
show ip arp inspection interfaces [interface-id] Displays the trust state and the rate limit of ARP
packets for the specified interface or all interfaces.
show ip arp inspection vlan vlan-range Displays the configuration and the operating state
of dynamic ARP inspection for the specified
VLAN. If no VLANs are specified or if a range is
specified, displays information only for VLANs
with dynamic ARP inspection enabled (active).
To clear or display dynamic ARP inspection statistics, use the privileged EXEC commands in
Table 22-3:
Table 22-3 Commands for Clearing or Displaying Dynamic ARP Inspection Statistics
Command Description
clear ip arp inspection statistics Clears dynamic ARP inspection statistics.
show ip arp inspection statistics [vlan Displays statistics for forwarded, dropped, MAC
vlan-range] 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
dynamic ARP inspection 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 dynamic ARP inspection port. The switch
increments the number of ACL 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 dynamic ARP inspection logging information, use the privileged EXEC commands
in Table 22-4:
Table 22-4 Commands for Clearing or Displaying Dynamic ARP Inspection Logging Information
Command Description
clear ip arp inspection log Clears the dynamic ARP inspection log buffer.
show ip arp inspection log Displays the configuration and contents of the dynamic ARP
inspection log buffer.
For more information about these commands, see the command reference for this release.
This chapter describes how to configure Internet Group Management Protocol (IGMP) snooping on the
Catalyst 3750 Metro switch, including an application of local IGMP snooping, Multicast VLAN
Registration (MVR). It also includes procedures for controlling multicast group membership by using
IGMP filtering.
Note For complete syntax and usage information for the commands used in this chapter, see the switch
command reference for this release and the “IP Multicast Routing Commands” section in the Cisco IOS
IP Command Reference, Volume 3 of 3:Multicast, Release 12.2.
Note You can either manage IP multicast group addresses through features such as IGMP snooping and MVR,
or you can use static IP addresses.
Note For more information on IP multicast and IGMP, see RFC 1112 and RFC 2236.
The multicast router (which could be a Catalyst 3750 Metro switch) sends out periodic general queries
to all VLANs. All hosts interested in this multicast traffic send join requests and are added to the
forwarding table entry. The switch creates one entry per VLAN in the IGMP snooping IP multicast
forwarding table for each group from which it receives an IGMP join request.
The switch supports IP multicast group-based bridging, rather than MAC-addressed based groups. With
multicast MAC address-based groups, if an IP address being configured translates (aliases) to a
previously configured MAC address or to any reserved multicast MAC addresses (in the range
224.0.0.xxx), the command fails. Because the switch uses IP multicast groups, there are no address
aliasing issues.
The IP multicast groups learned through IGMP snooping are dynamic. However, you can statically
configure multicast groups by using the ip igmp snooping vlan vlan-id static ip_address interface
interface-id global configuration command. If you specify group membership for a multicast group
address statically, your setting supersedes any automatic manipulation by IGMP snooping. Multicast
group membership lists can consist of both user-defined and IGMP snooping-learned settings.
You can configure an IGMP snooping querier to support IGMP snooping in subnets without multicast
interfaces because the multicast traffic does not need to be routed. For more information about the IGMP
snooping querier, see the “Configuring the IGMP Snooping Querier” section on page 23-10.
If a port spanning-tree, a port group, or a VLAN ID change occurs, the IGMP snooping-learned multicast
groups from this port on the VLAN are deleted.
These sections describe characteristics of IGMP snooping on the switch:
• IGMP Versions, page 23-2
• Joining a Multicast Group, page 23-3
• Leaving a Multicast Group, page 23-4
• Immediate Leave, page 23-5
IGMP Versions
The switch supports IGMP Version 1, IGMP Version 2, and IGMP Version 3. These versions are
interoperable on the switch. For example, if IGMP snooping is enabled on an IGMPv2 switch and the
switch receives an IGMPv3 report from a host, the switch can forward the IGMPv3 report to the
multicast router.
Note The switch supports IGMPv3 snooping based only on the destination multicast MAC address. It does not
support snooping based on the source MAC address or on proxy reports.
An IGMPv3 switch supports Basic IGMPv3 Snooping Support (BISS), which includes support for the
snooping features on IGMPv1 and IGMPv2 switches and for IGMPv3 membership report messages.
BISS constrains the flooding of multicast traffic when your network includes IGMPv3 hosts. It
constrains traffic to approximately the same set of ports as the IGMP snooping feature on IGMPv2 or
IGMPv1 hosts.
Note IGMPv3 join and leave messages are not supported on switches running IGMP filtering or MVR.
An IGMPv3 switch can receive messages from and forward messages to a device running the Source
Specific Multicast (SSM) feature. For more information about source-specific multicast with IGMPv3
and IGMP, see this URL:
http://www.cisco.com/en/US/docs/ios/12_2/ip/configuration/guide/1cfmulti.html
Router A
1
IGMP report 224.1.2.3
VLAN
PFC
CPU
0
Forwarding
45750
table
2 3 4 5
The switch hardware can distinguish IGMP information packets from other packets for the multicast
group. The information in the table tells the switching engine to send frames addressed to the 224.1.2.3
multicast IP address that are not IGMP packets to the 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 23-2), the CPU receives that message and adds the port number of Host 4 to the forwarding table
as shown in Table 23-2. Note that because the forwarding table directs IGMP messages only the to CPU,
the message is not flooded to other ports on the switch. Any known multicast traffic is forwarded to the
group and not to the CPU.
Router A
VLAN
PFC
CPU
0
Forwarding
45751
table
2 3 4 5
Immediate Leave
Immediate Leave is only supported with IGMP Version 2 hosts.
The switch uses IGMP snooping Immediate-Leave processing to remove from the forwarding table an
interface that sends a leave message without the switch sending group-specific queries to the interface.
The VLAN interface is pruned from the multicast tree for the multicast group specified in the original
leave message. Immediate-Leave processing ensures optimal bandwidth management for all hosts on a
switched network, even when multiple multicast groups are simultaneously in use.
Note You should only use the Immediate-Leave processing feature on VLANs where a single host is
connected to each port. If Immediate Leave is enabled in VLANs where more than one host is connected
to a port, some hosts might be inadvertently dropped.
For configuration steps, see the “Enabling IGMP Immediate Leave” section on page 23-10.
Note IGMP report suppression is supported only when the multicast query has IGMPv1 and IGMPv2 reports.
This feature is not supported when the query includes IGMPv3 reports.
The switch uses IGMP report suppression to forward only one IGMP report per multicast router query
to multicast devices. When IGMP router suppression is enabled (the default), the switch sends the first
IGMP report from all hosts blade servers for a group to all the multicast routers. The switch does not
send the remaining IGMP reports for the group to the multicast routers. This feature prevents duplicate
reports from being sent to the multicast devices.
If the multicast router query includes requests only for IGMPv1 and IGMPv2 reports, the switch
forwards only the first IGMPv1 or IGMPv2 report from all hosts blade servers for a group to all the
multicast routers.
If the multicast router query also includes requests for IGMPv3 reports, the switch forwards all IGMPv1,
IGMPv2, and IGMPv3 reports for a group to the multicast devices.
If you disable IGMP report suppression, all IGMP reports are forwarded to the multicast routers. For
configuration steps, see the “Disabling IGMP Report Suppression” section on page 23-12.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip igmp snooping Globally enable IGMP snooping in all existing VLAN interfaces.
Step 3 end Return to privileged EXEC mode.
Step 4 copy running-config startup-config (Optional) Save your entries in the configuration file.
To globally disable IGMP snooping on all VLAN interfaces, use the no ip igmp snooping global
configuration command.
Beginning in privileged EXEC mode, follow these steps to enable IGMP snooping on a VLAN interface:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip igmp snooping vlan vlan-id Enable IGMP snooping on the VLAN interface.The VLAN ID range
is 1 to 1001 and 1006 to 4094.
Note IGMP snooping must be globally enabled before you can
enable VLAN snooping.
Step 3 end Return to privileged EXEC mode.
Step 4 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable IGMP snooping on a VLAN interface, use the no ip igmp snooping vlan vlan-id global
configuration command for the specified VLAN number.
Note If you want to use CGMP as the learning method and no multicast routers in the VLAN are CGMP
proxy-enabled, you must enter the ip cgmp router-only command to dynamically access the router. For
more information, see Chapter 45, “Configuring IP Multicast Routing.”
Beginning in privileged EXEC mode, follow these steps to alter the method in which a VLAN interface
dynamically accesses a multicast router:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip igmp snooping vlan vlan-id mrouter Enable IGMP snooping on a VLAN.The VLAN ID range is 1 to 1001
learn {cgmp | pim-dvmrp} and 1006 to 4094.
Specify the multicast router learning method:
• cgmp—Listen for CGMP packets. This method is useful for
reducing control traffic.
• pim-dvmrp—Snoop on IGMP queries and PIM-DVMRP packets.
This is the default.
Step 3 end Return to privileged EXEC mode.
Step 4 show ip igmp snooping Verify the configuration.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default learning method, use the no ip igmp snooping vlan vlan-id mrouter learn cgmp
global configuration command.
This example shows how to configure IGMP snooping to use CGMP packets as the learning method:
Switch# configure terminal
Switch(config)# ip igmp snooping vlan 1 mrouter learn cgmp
Switch(config)# end
Note Static connections to multicast routers are supported only on switch ports.
Beginning in privileged EXEC mode, follow these steps to enable a static connection to a multicast
router:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip igmp snooping vlan vlan-id mrouter Specify the multicast router VLAN ID and specify the interface
interface interface-id to the multicast router.
• The VLAN ID range is 1 to 1001 and 1006 to 4094.
• The interface can be a physical interface or a port channel.
The port channel range is 1 to 12.
Step 3 end Return to privileged EXEC mode.
Command Purpose
Step 4 show ip igmp snooping mrouter [vlan vlan-id] Verify that IGMP snooping is enabled on the VLAN interface.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove a multicast router port from the VLAN, use the no ip igmp snooping vlan vlan-id mrouter
interface interface-id global configuration command.
This example shows how to enable a static connection to a multicast router:
Switch# configure terminal
Switch(config)# ip igmp snooping vlan 200 mrouter interface gigabitethernet1/0/2
Switch(config)# end
Command Purpose
Step 1 configure terminal Enter global configuration mode
Step 2 ip igmp snooping vlan vlan-id static ip_address Statically configure a Layer 2 port as a member of a multicast
interface interface-id group:
• vlan-id is the multicast group VLAN ID. The range is 1 to
1001 and 1006 to 4094.
• ip-address is the group IP address.
• interface-id is the member port. It can be a physical
interface or port channel (1 to 12).
Step 3 end Return to privileged EXEC mode.
Step 4 show ip igmp snooping groups Verify the member port and the IP address.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove the Layer 2 port from the multicast group, use the no ip igmp snooping vlan vlan-id static
mac-address interface interface-id global configuration command.
This example shows how to statically configure a host on an interface:
Switch# configure terminal
Switch(config)# ip igmp snooping vlan 105 static 224.2.4.12 interface gigabitethernet1/0/1
Switch(config)# end
Beginning in privileged EXEC mode, follow these steps to enable IGMP Immediate Leave:
Command Purpose
Step 1 configure terminal Enter global configuration mode
Step 2 ip igmp snooping vlan vlan-id Enable IGMP Immediate Leave on the VLAN interface.
immediate-leave
Step 3 end Return to privileged EXEC mode.
Step 4 show ip igmp snooping vlan vlan-id Verify that Immediate Leave is enabled on the VLAN.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable IGMP Immediate Leave on a VLAN, use the no ip igmp snooping vlan vlan-id
immediate-leave global configuration command.
This example shows how to enable IGMP Immediate Leave on VLAN 130:
Switch# configure terminal
Switch(config)# ip igmp snooping vlan 130 immediate-leave
Switch(config)# end
• When it is administratively enabled, the IGMP snooping querier moves to the operationally disabled
state under these conditions:
– IGMP snooping is disabled in the VLAN.
– PIM is enabled on the SVI of the corresponding VLAN.
Beginning in privileged EXEC mode, follow these steps to enable the IGMP snooping querier feature in
a VLAN:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip igmp snooping querier Enable the IGMP snooping querier.
Step 3 ip igmp snooping querier address (Optional) Specify an IP address for the IGMP snooping querier. If
ip_address you do not specify an IP address, the querier tries to use the global IP
address configured for the IGMP querier.
Note The IGMP snooping querier does not generate an IGMP
general query if it cannot find an IP address on the switch.
Step 4 ip igmp snooping querier query-interval (Optional) Set the interval between IGMP queriers. The range is 1 to
interval-count 18000 seconds.
Step 5 ip igmp snooping querier tcn query [count (Optional) Set the time between Topology Change Notification
count | interval interval] (TCN) queries. The count range is 1 to 10. The interval range is 1 to
255 seconds.
Step 6 ip igmp snooping querier timer expiry (Optional) Set the length of time until the IGMP querier expires.The
timeout range is 60 to 300 seconds.
Step 7 ip igmp snooping querier version version (Optional) Select the IGMP version number that the querier feature
uses. Select 1 or 2.
Step 8 end Return to privileged EXEC mode.
Step 9 show ip igmp snooping vlan vlan-id (Optional) Verify that the IGMP snooping querier is enabled on the
VLAN interface. The VLAN ID range is 1 to 1001 and 1006 to 4094.
Step 10 copy running-config startup-config (Optional) Save your entries in the configuration file.
This example shows how to set the IGMP snooping querier source address to 10.0.0.64:
Switch# configure terminal
Switch(config)# ip igmp snooping querier 10.0.0.64
Switch(config)# end
This example shows how to set the IGMP snooping querier maximum response time to 25 seconds:
Switch# configure terminal
Switch(config)# ip igmp snooping querier query-interval 25
Switch(config)# end
This example shows how to set the IGMP snooping querier timeout to 60 seconds:
Switch# configure terminal
Switch(config)# ip igmp snooping querier timeout expiry 60
Switch(config)# end
This example shows how to set the IGMP snooping querier feature to version 2:
Switch# configure terminal
Switch(config)# no ip igmp snooping querier version 2
Switch(config)# end
Note IGMP report suppression is supported only when the multicast query has IGMPv1 and IGMPv2 reports.
This feature is not supported when the query includes IGMPv3 reports.
IGMP report suppression is enabled by default. When it is enabled, the switch forwards only one IGMP
report per multicast router query. When report suppression is disabled, all IGMP reports are forwarded
to the multicast routers.
Beginning in privileged EXEC mode, follow these steps to disable IGMP report suppression:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 no ip igmp snooping report-suppression Disable IGMP report suppression.
Step 3 end Return to privileged EXEC mode.
Step 4 show ip igmp snooping Verify that IGMP report suppression is disabled.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To re-enable IGMP report suppression, use the ip igmp snooping report-suppression global
configuration command.
Command Purpose
show ip igmp snooping [vlan vlan-id] Display the snooping configuration information for all VLANs on the
switch or for a specified VLAN.
(Optional) Enter vlan vlan-id to display information for a single VLAN.
The VLAN ID range is 1 to 1001 and 1006 to 4094.
show ip igmp snooping groups [count | dynamic Display multicast table information for the switch or about a specific
[count] | user [count]] parameter:
• count—Display the total number of entries for the specified
command options instead of the actual entries.
• dynamic—Display entries learned through IGMP snooping.
• user—Display only the user-configured multicast entries.
Command Purpose
show ip igmp snooping groups vlan vlan-id Display multicast table information for a multicast VLAN or about a
[ip_address | count | dynamic [count] | specific parameter for the VLAN:
user[count]]
• vlan-id—The VLAN ID range is 1 to 1001 and 1006 to 4094.
• count—Display the total number of entries for the specified
command options instead of the actual entries.
• dynamic—Display entries learned through IGMP snooping.
• ip_address—Display characteristics of the multicast group with the
specified group IP address.
• user—Display only the user-configured multicast entries.
show ip igmp snooping mrouter [vlan vlan-id] Display information on dynamically learned and manually configured
multicast router interfaces.
Note When you enable IGMP snooping, the switch automatically
learns the interface to which a multicast router is connected.
These are dynamically learned interfaces.
For more information about the keywords and options in these commands, see the command reference
for this release.
The switch CPU identifies the MVR IP multicast streams and their associated IP multicast group in the
switch forwarding table, intercepts the IGMP messages, and modifies the 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.
You can set the switch for compatible or dynamic mode of MVR operation.
• In compatible mode, multicast data received by MVR hosts is forwarded to all MVR data ports,
regardless of MVR host membership on those ports. The multicast data is forwarded only to those
receiver ports which MVR hosts have explicitly joined, either by IGMP reports or by MVR static
configuration. Also, IGMP reports received from MVR hosts are never forwarded out of MVR data
ports that were configured in the switch.
• In dynamic mode, multicast data received by MVR hosts on the switch is forwarded from only those
MVR data and client ports that the MVR hosts have explicitly joined, either by IGMP reports or by
MVR static configuration. Any IGMP reports received from MVR hosts are also forwarded from all
the MVR data ports in the switch. This eliminates using unnecessary bandwidth on MVR data port
links, which occurs when the switch runs in compatible mode.
Only Layer 2 ports take part in MVR. You must configure ports as MVR receiver ports. Only one MVR
multicast VLAN per switch is supported.
Multicast
server
SP
Switch B
SP
SP
SP SP
SP
SP1 SP2
Multicast Multicast
data data
Switch A
PC
101364
TV TV
RP = Receiver Port Note: All source ports belong to
SP = Source Port 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 switch 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.
Without Immediate Leave, 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 Immediate Leave, 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 once—only on the multicast
VLAN. The IGMP leave and join messages are in the VLAN to which the subscriber port is assigned.
These messages dynamically register for streams of multicast traffic in the multicast VLAN on the
Layer 3 device. 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, based on the MVR mode.
Configuring MVR
These sections include basic MVR configuration information:
• Default MVR Configuration, page 23-16
• MVR Configuration Guidelines and Limitations, page 23-16
• Configuring MVR Global Parameters, page 23-17
• Configuring MVR on Access Ports, page 23-18
• Configuring MVR on Trunk Ports, page 23-20
• Displaying MVR Information, page 23-21
this limit is reached, a message is generated that the Maximum hardware limit of groups had been
reached. Note that a hardware entry occurs when there is an IGMP join on a port or when you have
configured the port to join a group by entering the mvr vlan vlan-id group ip-address interface
configuration command.
• MVR multicast data received in the source VLAN and leaving from receiver ports has its
time-to-live (TTL) decremented by 1 in the switch.
• Because MVR on the switch uses IP multicast addresses instead of MAC multicast addresses,
aliased IP multicast addresses are allowed on the switch. However, if the switch is interoperating
with Catalyst 3550 or Catalyst 3500 XL switches, you should not configure IP addresses that alias
between themselves or with the reserved IP multicast addresses (in the range 224.0.0.xxx).
• Do not configure MVR on private VLAN ports.
• MVR is not supported when multicast routing is enabled on a switch. If you enable multicast routing
and a multicast routing protocol while MVR is enabled, MVR is disabled, and you receive a warning
message. If you try to enable MVR while multicast routing and a multicast routing protocol are
enabled, the operation to enable MVR is cancelled, and you receive an error message.
• MVR can coexist with IGMP snooping on a switch.
• MVR data received on an MVR receiver port is not forwarded to MVR source ports.
• MVR does not support IGMPv3 messages.
• Starting with Cisco IOS release 12.2(52)SE, you can enter the mvr ringmode flood global
configuration to ensure that data forwarding in a ring topology is limited to ports detected as
members and excludes forwarding to multicast router ports. This prevents unicast traffic from being
dropped in a ring environment when MVR multicast traffic flows in one direction and unicast traffic
flows in the other direction.
Note For complete syntax and usage information for the commands used in this section, see the command
reference for this release.
Beginning in privileged EXEC mode, follow these steps to configure MVR parameters:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 mvr Enable MVR on the switch.
Step 3 mvr group ip-address [count] Configure an IP multicast address on the switch or use the count parameter to
configure a contiguous series of MVR group addresses. The range for count
is 1 to 2000. However, when the MVR mode is compatible, the switch allows
a maximum count of 512. When the mode is dynamic, you can create 2000
MVR groups. 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.
Command Purpose
Step 4 mvr querytime value (Optional) Define 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 5 tenths or one-half second.
Step 5 mvr vlan vlan-id (Optional) Specify the VLAN in which multicast data is received; all source
ports must belong to this VLAN. The VLAN ID range is 1 to 1001 and 1006
to 4094. The default is VLAN 1.
Step 6 mvr mode {dynamic | compatible} (Optional) Specify the MVR mode of operation:
• dynamic—Allow dynamic MVR membership on source ports. To
configure 2000 MVR groups, the mode must be dynamic.
• compatible—Is compatible with Catalyst 3500 XL and Catalyst 2900 XL
switches and does not support IGMP dynamic joins on source ports.
The default is compatible mode.
Step 7 mvr ringmode flood (Optional) Enable MVR ringmode flooding for access rings. Entering this
command controls traffic flow in egress ports in a ring environment to prevent
the dropping of unicast traffic.
Step 8 end Return to privileged EXEC mode.
Step 9 show mvr or show mvr members Verify the configuration.
Step 10 copy running-config (Optional) Save your entries in the configuration file.
startup-config
To return the switch to its default settings, use the no mvr [mode | group ip-address | querytime | vlan]
global configuration commands.
This example shows how to enable MVR, configure the group address, set the query time to 1 second
(10 tenths), specify the MVR multicast VLAN as VLAN 22, and set the MVR mode as dynamic:
Switch(config)# mvr
Switch(config)# mvr group 228.1.23.4
Switch(config)# mvr querytime 10
Switch(config)# mvr vlan 22
Switch(config)# mvr mode dynamic
Switch(config)# end
You can use the show mvr members privileged EXEC command to verify the MVR multicast group
addresses on the switch.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 mvr Enable MVR on the switch.
Step 3 interface interface-id Enter interface configuration mode, and enter the type and number of the
Layer 2 port to configure.
Command Purpose
Step 4 mvr type {source | receiver} Configure an MVR port as one of these:
• source—Configure 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.
• receiver—Configure 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.
The default configuration is as a non-MVR port. If you attempt to configure
a non-MVR port with MVR characteristics, the operation fails.
Step 5 mvr vlan vlan-id group [ip-address] (Optional) Statically configure a port to receive multicast traffic sent to the
multicast VLAN and the IP multicast address. A port statically configured as
a member of a group remains a member of the group until statically removed.
Note In compatible mode, this command applies to only receiver ports. In
dynamic mode, it applies to receiver ports and source ports.
Receiver ports can also dynamically join multicast groups by using IGMP
join and leave messages.
Step 6 mvr immediate (Optional) Enable the Immediate-Leave feature of MVR on the port.
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 7 end Return to privileged EXEC mode.
Step 8 show mvr [interface | members] Verify the configuration.
Step 9 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return the interface to its default settings, use the no mvr [type | immediate | vlan vlan-id | group]
interface configuration commands.
This example shows how to configure an interface as a receiver port, statically configure the port to
receive multicast traffic sent to the multicast group address, configure Immediate Leave on the interface,
and verify the results.
Switch(config)# mvr
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# mvr type receiver
Switch(config-if)# mvr vlan 22 group 228.1.23.4
Switch(config-if)# mvr immediate
Switch(config)# end
Switch# show mvr interface
Port Type Mode VLAN Status Immediate Leave
---- ---- ---- ---- ------- ---------------
Gia1/0/2 RECEIVER Trunk 201 ACTIVE/DOWN DISABLED
Note For more information about access and trunk ports, see Chapter 9, “Configuring Interface
Characteristics”.
Beginning in privileged EXEC mode, follow these steps to configure a trunk port as an MVR receiver
port:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 mvr Enable MVR on the switch.
Step 3 interface interface-id Enter the Layer 2 port to configure and enter
interface configuration mode.
Step 4 switchport mode trunk Set trunking mode to TRUNK unconditionally.
Step 5 mvr type receiver Specify that the trunk port is an MVR receiver port.
Step 6 mvr vlan source-vlan-id receiver vlan receiver-vlan-id Enable this trunk port to distribute MVR traffic
coming from the MVR VLAN to the VLAN on the
trunk identified by the receiver VLAN.
Step 7 mvr vlan vlan-id group ip-address receiver vlan-id (Optional) Configure the trunk port to be a static
member of the group on the receiver VLAN.
Step 8 end Return to privileged EXEC mode.
Step 9 show mvr Verify the configuration.
show mvr interface
or
show mvr members
Step 10 copy running-config startup-config (Optional) Save your entries in the configuration
file.
This example shows how to configure a port as an MVR trunk receiver port, assign it to a VLAN,
configure the port to be a static member of a group, and verify the results.
Switch(config)# mvr
Switch(config)# interface fastethernet 0/10
Switch(config)# switchport mode trunk
Switch(config)# mvr type receiver
Switch(config)# mvr vlan 100 receiver vlan 201
Switch(config)# mvr vlan 100 group 239.1.1.1 receiver vlan 201
Switch(config)# end
Switch# show mvr interface
To return the interface to its default settings, use the no mvr [type | immediate | vlan
vlan-id | group] interface configuration command.
show mvr Displays MVR status and values for the switch—whether MVR is enabled or disabled,
the multicast VLAN, the maximum (512) and current (0 through 512) number of
multicast groups, the query response time, and the MVR mode.
show mvr interface [interface-id] Displays all MVR interfaces and their MVR configurations.
[members [vlan vlan-id]]
When a specific interface is entered, displays this information:
• Type—Receiver or Source
• Mode—Access or Trunk
• VLAN—The MVR VLAN for the source port and the receiver VLAN for the receiver
port
• Status—One of these:
– Active means the port is part of a VLAN.
– Up/Down means that the port is forwarding or nonforwarding.
– Inactive means that the port is not part of any VLAN.
• Immediate Leave—Enabled or Disabled
If the members keyword is entered, displays all multicast group members on this port or,
if a VLAN identification is entered, all multicast group members on the VLAN. The
VLAN ID range is 1 to 1001 and 1006 to 4094.
show mvr members [ip-address] Displays all receiver and source ports that are members of any IP multicast group or the
specified IP multicast group IP address.
IGMP filtering is only applicable to dynamic learning of IP multicast group addresses; not static
configuration.
With the IGMP throttling feature, you can also set the maximum number of IGMP groups that a Layer 2
interface can join. If the maximum number of IGMP groups is set, the IGMP snooping forwarding table
contains the maximum number of entries, and the interface receives an IGMP join report, you can
configure an interface to drop the IGMP report or to replace the randomly selected multicast entry with
the received IGMP report.
Note IGMPv3 join and leave messages are not supported on switches running IGMP filtering.
When the maximum number of groups is in forwarding table, the default IGMP throttling action is to
deny the IGMP report. For configuration guidelines, see the Configuring the IGMP Throttling Action,
page 23-25.
• range: Specifies a range of IP addresses for the profile. You can enter a single IP address or a range
with a start and an end address.
The default is for the switch to have no IGMP profiles configured. When a profile is configured, if
neither the permit nor deny keyword is included, the default is to deny access to the range of IP
addresses.
Beginning in privileged EXEC mode, follow these steps to create an IGMP profile:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip igmp profile profile number Enter IGMP profile configuration mode, and assign a number to the
profile you are configuring. The range is 1 to 4294967295.
Step 3 permit | deny (Optional) Set the action to permit or deny access to the IP multicast
address. If no action is configured, the default for the profile is to deny
access.
Step 4 range ip multicast address Enter the IP multicast address or range of IP multicast addresses to
which access is being controlled. If entering a range, enter the low IP
multicast address, a space, and the high IP multicast address.
You can use the range command multiple times to enter multiple
addresses or ranges of addresses.
Step 5 end Return to privileged EXEC mode.
Step 6 show ip igmp profile profile number Verify the profile configuration.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
To delete a profile, use the no ip igmp profile profile number global configuration command.
To delete an IP multicast address or range of IP multicast addresses, use the no range ip multicast
address IGMP profile configuration command.
This example shows how to create IGMP profile 4 allowing access to the single IP multicast address and
how to verify the configuration. If the action was to deny (the default), it would not appear in the show
ip igmp profile output display.
Switch(config)# ip igmp profile 4
Switch(config-igmp-profile)# permit
Switch(config-igmp-profile)# range 229.9.9.0
Switch(config-igmp-profile)# end
Switch# show ip igmp profile 4
IGMP Profile 4
permit
range 229.9.9.0 229.9.9.0
Beginning in privileged EXEC mode, follow these steps to apply an IGMP profile to a switch port:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and enter the physical interface to
configure. The interface must be a Layer 2 port that does not belong to
an EtherChannel port group.
Step 3 ip igmp filter profile number Apply the specified IGMP profile to the interface. The profile number
can be from 1 to 4294967295.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config interface Verify the configuration.
interface-id
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove a profile from an interface, use the no ip igmp filter profile number interface configuration
command.
This example shows how to apply IGMP profile 4 to a port:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# ip igmp filter 4
Switch(config-if)# end
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and enter the physical interface to
configure. The interface must be a Layer 2 port that does not belong to
an EtherChannel group.
Step 3 ip igmp max-groups number Set the maximum number of IGMP groups that the interface can join.
The range is 0 to 4294967294. The default is to have no maximum set.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config interface Verify the configuration.
interface-id
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove the maximum group limitation and return to the default of no maximum, use the no ip igmp
max-groups interface configuration command.
This example shows how to limit the number of IGMP groups that a port can join to 25.
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# ip igmp max-groups 25
Switch(config-if)# end
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and enter the physical interface to
configure. The interface can be a Layer 2 port that does not belong to an
EtherChannel group or an EtherChannel interface. The interface cannot
be a trunk port.
Step 3 ip igmp max-groups action {deny | When an interface receives an IGMP report and the maximum number
replace} of entries is in the forwarding table, specify the action that the interface
takes:
• deny—Drop the report.
• replace—Replace the existing group for which the IGMP report
was received.
Command Purpose
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config interface Verify the configuration.
interface-id
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default action of dropping the report, use the no ip igmp max-groups action interface
configuration command.
Table 23-8 Commands for Displaying IGMP Filtering and Throttling Configuration
show ip igmp profile [profile Displays the specified IGMP profile or all IGMP profiles defined on the switch.
number]
show running-config [interface Displays the configuration of the specified interface or the configuration of all interfaces
interface-id] on the switch, including (if configured) the maximum number of IGMP groups to which
an interface can belong and the IGMP profile applied to the interface.
This chapter describes how to configure port-based traffic control features on the Catalyst 3750 Metro
switch.
Note For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
• Traffic rate in bits per second at which broadcast, multicast, or unicast packets are received (Cisco
IOS Release 12.2(25)EY or later)
• Traffic rate in packets per second and for small frames. This feature is enabled globally. The
threshold for small frames is configured for each interface. (Cisco IOS Release 12.2(44)SE or later)
With each method, the port blocks traffic when the rising threshold is reached. The port remains blocked
until the traffic rate drops below the falling threshold (if one is specified) and then resumes normal
forwarding. If the falling suppression level is not specified, the switch blocks all traffic until the traffic
rate drops below the rising suppression level. In general, the higher the level, the less effective the
protection against broadcast storms.
Note When the storm control threshold for multicast traffic is reached, all multicast traffic except control
traffic, such as bridge protocol data unit (BDPU) and Cisco Discovery Protocol (CDP) frames, are
blocked. However, the switch does not differentiate between routing updates, such as OSPF, and regular
multicast data traffic, so both types of traffic are blocked.
When storm control is enabled, the switch monitors packets passing from an interface to the switching
bus and determines if the packet is unicast, multicast, or broadcast. The switch monitors the number of
broadcast, multicast, or unicast packets received within a 200-millisecond time interval, and when a
threshold for one type of traffic is reached, that type of traffic is dropped. This threshold is specified as
a percentage of total available bandwidth that can be used by broadcast (multicast or unicast) traffic.
The graph in Figure 24-1 shows broadcast traffic patterns on an interface over a given period of time.
The example can also be applied to multicast and unicast traffic. In this example, the broadcast traffic
being forwarded exceeded the configured threshold between time intervals T1 and T2 and between T4
and T5. When the amount of specified traffic exceeds the threshold, all traffic of that kind is dropped for
the next time period. Therefore, broadcast traffic is blocked during the intervals following T2 and T5.
At the next time interval (for example, T3), if broadcast traffic does not exceed the threshold, it is again
forwarded.
Forwarded traffic
Blocked traffic
Total
number of
Threshold
broadcast
packets
or bytes
46651
0 T1 T2 T3 T4 T5 Time
The combination of the storm-control suppression level and the 200-millisecond time interval control
the way the storm control algorithm works. A higher threshold allows more packets to pass through. A
threshold value of 100 percent means that no limit is placed on the traffic. A value of 0.0 means that all
broadcast, multicast, or unicast traffic on that port is blocked.
Note Because packets do not arrive at uniform intervals, the 200-millisecond time interval during which traffic
activity is measured can affect the behavior of storm control.
The switch continues to monitor traffic on the port, and when the utilization level is below the threshold
level, the type of traffic that was dropped is forwarded again.
You use the storm-control interface configuration commands to set the threshold value for each traffic
type.
Note Storm control is supported on physical interfaces. You can also configure storm control on an
EtherChannel. When storm control is configured on an EtherChannel, the storm control settings
propagate to the EtherChannel physical interfaces.
Beginning in privileged EXEC mode, follow these steps to enable a particular type of storm control:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and enter the type and number
of the physical interface to configure, for example
gigabitethernet1/0/1.
Command Purpose
Step 3 storm-control {broadcast | multicast | Configure broadcast, multicast, or unicast storm control. By
unicast} level {level [level-low] | bps bps default, storm control is disabled.
[bps-low] | pps pps [pps-low]}
The keywords have these meanings:
• For level, specify the rising threshold level for broadcast,
multicast, or unicast traffic as a percentage (up to two decimal
places) of the bandwidth. The port blocks traffic when the
rising threshold is reached. The range is 0.00 to 100.00.
• (Optional) For level-low, specify the falling threshold level as
a percentage (up to two decimal places) of the bandwidth. This
value must be less than or equal to the rising suppression
value. The port forwards traffic when traffic drops below this
level. If you do not configure a falling suppression level, it is
set to the rising suppression level. The range is 0.00 to 100.00.
If you set the threshold to the maximum value (100 percent),
no limit is placed on the traffic. If you set the threshold to 0.0,
all broadcast, multicast, and unicast traffic on that port is
blocked.
• For bps bps, specify the rising threshold level for broadcast,
multicast, or unicast traffic in bits per second (up to one
decimal place). The port blocks traffic when the rising
threshold is reached. The range is 0.0 to 10000000000.0.
• (Optional) For bps-low, specify the falling threshold level in
bits per second (up to one decimal place). It can be less than or
equal to the rising threshold level. The port forwards traffic
when traffic drops below this level. The range is 0.0 to
10000000000.0.
• For pps pps, specify the rising threshold level for broadcast,
multicast, or unicast traffic in packets per second (up to one
decimal place). The port blocks traffic when the rising
threshold is reached. The range is 0.0 to 10000000000.0.
• (Optional) For pps-low, specify the falling threshold level in
packets per second (up to one decimal place). It can be less
than or equal to the rising threshold level. The port forwards
traffic when traffic drops below this level. The range is 0.0 to
10000000000.0.
For BPS and PPS settings, you can use metric suffixes such as k,
m, and g for large number thresholds.
Step 4 storm-control action {shutdown | trap} Specify the action to be taken when a storm is detected. The default
is to filter out the traffic and not to send traps.
• Select the shutdown keyword to error-disable the port during
a storm.
• Select the trap keyword to generate an SNMP trap when a
storm is detected.
Step 5 end Return to privileged EXEC mode.
Command Purpose
Step 6 show storm-control [interface-id] [broadcast | Verify the storm control suppression levels set on the interface for
multicast | unicast] the specified traffic type. If you do not enter a traffic type,
broadcast storm control settings are displayed.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable storm control, use the no storm-control {broadcast | multicast | unicast} level interface
configuration command.
This example shows how to enable unicast storm control on a port with an 87-percent rising suppression
level and a 65-percent falling suppression level:
Switch# configure terminal
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# storm-control unicast level 87 65
This example shows how to enable broadcast address storm control on a port 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 the traffic-storm-control interval, the switch drops all broadcast traffic until the end of
the traffic-storm-control interval:
Switch# configure terminal
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# storm-control broadcast level 20
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 errdisable detect cause small-frame Enable the small-frame rate-arrival feature on the switch.
Step 3 errdisable recovery interval interval (Optional) Specify the time to recover from the specified
error-disabled state.
Step 4 errdisable recovery cause small-frame (Optional) Configure the recovery time for error-disabled ports to
be automatically re-enabled after they are error disabled by the
arrival of small frames
Command Purpose
Step 5 interface interface-id Enter interface configuration mode, and specify the interface to be
configured.
Step 6 small violation-rate pps Configure the threshold rate for the interface to drop incoming
packets and error disable the port. The range is 1 to 10,000 packets
per second (pps)
Step 7 end Return to privileged EXEC mode.
Step 8 show interfaces interface-id Verify the configuration.
Step 9 copy running-config startup-config (Optional) Save your entries in the configuration file.
This example shows how to enable the small-frame arrival-rate feature, configure the port recovery time,
and configure the threshold for error disabling a port:
Switch# configure terminal
Switch# errdisable detect cause small-frame
Switch# errdisable recovery cause small-frame
Switch(config)# interface fastethernet0/1
Switch(config-if)# small-frame violation rate 10000
Switch(config-if)# end
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and enter the type and
number of the interface to configure, for example
gigabitethernet1/0/1.
Step 3 switchport protected Configure the interface to be a protected port.
Step 4 end Return to privileged EXEC mode.
Step 5 show interfaces interface-id switchport Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable protected port, use the no switchport protected interface configuration command.
This example shows how to configure an interface as a protected port:
Switch# configure terminal
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# switchport protected
Switch(config-if)# end
Note With multicast traffic, the port blocking feature blocks only pure Layer 2 packets. Multicast packets that
contain IPv4 or IPv6 information in the header are not blocked.
Note The interface can be a physical interface (for example, Gigabit Ethernet 1/0/1) or an EtherChannel group
(for example, port-channel 5). When you block multicast or unicast traffic for a port channel, it is
blocked on all ports in the port channel group.
Beginning in privileged EXEC mode, follow these steps to disable the flooding of unicast packets and
Layer 2 multicast packets out of an interface:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and enter the type and
number of the interface to configure, for example
gigabitethernet1/0/1.
Step 3 switchport block multicast Block unknown multicast forwarding out of the port.
Note Only pure Layer 2 multicast traffic is blocked. Multicast
packets that contain IPv4 or IPv6 information in the
header are not blocked.
Step 4 switchport block unicast Block unknown unicast forwarding out of the port.
Step 5 end Return to privileged EXEC mode.
Step 6 show interfaces interface-id switchport Verify your entries.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return the interface to the default condition where no traffic is blocked and normal forwarding occurs
on the port, use the no switchport block {multicast | unicast} interface configuration commands.
This example shows how to block unicast and Layer 2 multicast flooding on an interface:
Switch# configure terminal
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# switchport block multicast
Switch(config-if)# switchport block unicast
Switch(config-if)# end
Note If you try to set the maximum value to a number less than the number of secure addresses already
configured on an interface, the command is rejected.
The maximum number of secure MAC addresses that you can configure on a switch is determined by the
maximum number of available MAC addresses allowed in the system. This number is determined by the
active Switch Database Management (SDM) template. See Chapter 6, “Configuring SDM Templates.”
This number represents the total of available MAC addresses, including those used for other Layer 2
functions and any other secure MAC addresses configured on interfaces.
Security Violations
It is a security violation when one of these situations occurs:
• The maximum number of secure MAC addresses have been added to the address table, and a station
whose MAC address is not in the address table attempts to access the interface.
• An address learned or configured on one secure interface is seen on another secure interface in the
same VLAN.
You can configure the interface for one of three violation modes, based on the action to be taken if a
violation occurs:
• protect—when the number of secure MAC addresses reaches the maximum limit allowed on the
port, packets with unknown source addresses are dropped until you remove a sufficient number of
secure MAC addresses to drop below the maximum value or increase the number of maximum
allowable addresses. You are not notified that a security violation has occurred.
Note We do not recommend configuring the protect violation mode on a trunk port. The protect
mode disables learning when any VLAN reaches its maximum limit, even if the port has not
reached its maximum limit.
• restrict—when the number of secure MAC addresses reaches the maximum limit allowed on the
port, packets with unknown source addresses are dropped until you remove a sufficient number of
secure MAC addresses to drop below the maximum value or increase the number of maximum
allowable addresses. In this mode, you are notified that a security violation has occurred. An SNMP
trap is sent, a syslog message is logged, and the violation counter increments.
• shutdown—a port security violation causes the interface to become error-disabled and to shut down
immediately, and the port LED turns off. An SNMP trap is sent, a syslog message is logged, and the
violation counter increments. When a secure port is in the error-disabled state, you can bring it out
of this state by entering the errdisable recovery cause psecure-violation global configuration
command, or you can manually re-enable it by entering the shutdown and no shut down interface
configuration commands. This is the default mode.
Table 24-1 shows the violation mode and the actions taken when you configure an interface for port
security.
Violation Traffic is Sends SNMP Sends syslog Displays error Violation counter Shuts down
Mode forwarded1 trap message message2 increments port
protect No No No No No No
restrict No Yes Yes No Yes No
shutdown No No No No Yes Yes
1. Packets with unknown source addresses are dropped until you remove a sufficient number of secure MAC addresses.
2. The switch returns an error message if you manually configure an address that would cause a security violation.
Configuration Guidelines
Follow these guidelines when configuring port security:
• Port security can only be configured on static access ports, trunk ports, or tunnel ports. A secure port
cannot be a dynamic access port.
• A secure port cannot be a destination port for Switched Port Analyzer (SPAN).
• A secure port cannot belong to a Fast EtherChannel or a Gigabit EtherChannel port group.
• You cannot configure static secure or sticky secure MAC addresses in the voice VLAN.
Note Voice VLAN is only supported on access ports and not on trunk ports, even though the
configuration is allowed.
• When a voice VLAN is configured on a secure port that is also configured as a sticky secure port,
all addresses on the voice VLAN are learned as dynamic secure addresses, and all addresses seen on
the access VLAN to which the port belongs are learned as sticky secure addresses.
• When you enter a maximum secure address value for an interface, and the new value is greater than
the previous value, the new value overwrites the previously configured value. If the new value is less
than the previous value and the number of configured secure addresses on the interface exceeds the
new value, the command is rejected.
• The switch does not support port security aging of sticky secure MAC addresses.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and enter the physical interface to
configure, for example gigabitethernet1/0/1.
Step 3 switchport mode {access | trunk} Set the interface switchport mode as access or trunk; an interface in the
default mode (dynamic auto) cannot be configured as a secure port.
Step 4 switchport port-security Enable port security on the interface.
Step 5 switchport port-security (Optional) Set the maximum number of secure MAC addresses for the
maximum value [vlan [vlan-list]] interface. If an interface is configured for voice VLAN, configure a maximum
of two secure MAC addresses.
The maximum number of secure MAC addresses that you can configure on a
switch is determined by the maximum number of available MAC addresses
allowed in the system. This number is determined by the active Switch
Database Management (SDM) template. See Chapter 6, “Configuring SDM
Templates.” This number represents the total of available MAC addresses,
including those used for other Layer 2 functions and any other secure MAC
addresses configured on interfaces.
(Optional) For trunk ports, you can set the maximum number of secure MAC
addresses on a VLAN. If the vlan keyword is not entered, the default value is
used.
• vlan—set a per-VLAN maximum value.
• vlan vlan-list—set a per-VLAN maximum value on a range of VLANs
separated by a hyphen, or a series of VLANs separated by commas. For
non-specified VLANs, the per-VLAN maximum value is used.
Command Purpose
Step 6 switchport port-security violation (Optional) Set the violation mode, the action to be taken when a security
{protect | restrict | shutdown} violation is detected, as one of these:
• protect—When the number of port secure MAC addresses reaches the
maximum limit allowed on the port, packets with unknown source
addresses are dropped until you remove a sufficient number of secure
MAC addresses to drop below the maximum value or increase the number
of maximum allowable addresses. You are not notified that a security
violation has occurred.
Note We do not recommend configuring the protect mode on a trunk port.
The protect mode disables learning when any VLAN reaches its
maximum limit, even if the port has not reached its maximum limit.
Command Purpose
Step 11 show port-security Verify your entries.
Step 12 copy running-config (Optional) Save your entries in the configuration file.
startup-config
To return the interface to the default condition as not a secure port, use the no switchport port-security
interface configuration command. If you enter this command when sticky learning is enabled, the sticky
secure addresses remain part of the running configuration but are removed from the address table. All
addresses are now dynamically learned.
To return the interface to the default number of secure MAC addresses, use the no switchport
port-security maximum value interface configuration command. To return the violation mode to the
default condition (shutdown mode), use the no switchport port-security violation {protocol | restrict}
interface configuration command.
To disable sticky learning on an interface, use the no switchport port-security mac-address sticky
interface configuration command. The interface converts the sticky secure MAC addresses to dynamic
secure addresses. However, if you have previously saved the configuration with the sticky MAC
addresses, you should save the configuration again after entering the no switchport port-security
mac-address sticky command, or the sticky addresses will be restored if the switch reboots.
To delete a specific secure MAC address from the address table, use the no switchport port-security
mac-address mac-address interface configuration command.
To delete all dynamic secure addresses on an interface from the address table, enter the no switchport
port-security interface configuration command followed by the switchport port-security command (to
re-enable port security on the interface). If you use the no switchport port-security mac-address sticky
interface configuration command to convert sticky secure MAC addresses to dynamic secure MAC
addresses before entering the no switchport port-security command, all secure addresses on the
interface except those that were manually configured are deleted.
You must specifically delete configured secure MAC addresses from the address table by using the no
switchport port-security mac-address mac-address interface configuration command.
This example shows how to enable port security on an interface and to set the maximum number of
secure addresses to 50. The violation mode is the default, no static secure MAC addresses are configured,
and sticky learning is enabled.
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# switchport mode access
Switch(config-if)# switchport port-security
Switch(config-if)# switchport port-security maximum 50
Switch(config-if)# switchport port-security mac-address sticky
This example shows how to configure a static secure MAC address on VLAN 3 on an interface:
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# switchport mode trunk
Switch(config-if)# switchport port-security
Switch(config-if)# switchport port-security mac-address 0000.02000.0004 vlan 3
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode for the port on which you
want to enable port security aging.
Step 3 switchport port-security aging {static | time time | Enable or disable static aging for the secure port, or set the
type {absolute | inactivity}} aging time or type.
Note The switch does not support port security aging of
sticky secure addresses.
To disable port security aging for all secure addresses on a port, use the no switchport port-security
aging time interface configuration command. To disable aging for only statically configured secure
addresses, use the no switchport port-security aging static interface configuration command.
This example shows how to set the aging time as 2 hours for the secure addresses on an interface:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# switchport port-security aging time 120
This example shows how to set the aging time as 2 minutes for the inactivity aging type with aging
enabled for the configured secure addresses on the interface:
Switch(config-if)# switchport port-security aging time 2
Switch(config-if)# switchport port-security aging type inactivity
Switch(config-if)# switchport port-security aging static
You can verify the previous commands by entering the show port-security interface interface-id
privileged EXEC command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface to be configured, and enter interface
configuration mode.
Step 3 switchport mode private-vlan {host | promiscuous} Enable a private vlan on the interface.
Step 4 switchport port-security Enable port security on the interface.
Step 5 end Return to privileged EXEC mode.
Step 6 show port-security [interface interface-id] Verify your entries.
[address]
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
Note Ports that have both port security and private VLANs configured can be labeled secure PVLAN ports.
When a secure address is learned on a secure PVLAN port, the same secure address cannot be learned
on another secure PVLAN port belonging to the same primary VLAN. However, an address learned on
insecure PVLAN port can be learned on a secure PVLAN port belonging to same primary VLAN.
Secure addresses that are learned on host port get automatically replicated on associated primary
VLANs, and similarly, secure addresses learned on promiscuous ports automatically get replicated on
all associated secondary VLANs. Static addresses (using mac-address-table static command) cannot be
user configured on a secure port. Displaying Port-Based Traffic Control Settings
The show interfaces interface-id switchport privileged EXEC command displays (among other
characteristics) the interface traffic suppression and control configuration. The show storm-control and
show port-security privileged EXEC commands display those features.
To display traffic control information, use one or more of the privileged EXEC commands in Table 24-3.
Table 24-3 Commands for Displaying Traffic Control Status and Configuration
Command Purpose
show interfaces [interface-id] switchport Displays the administrative and operational status of all switching
(nonrouting) ports or the specified port, including port blocking and
port protection settings.
show storm-control [interface-id] [broadcast | Displays storm control suppression levels set on all interfaces or the
multicast | unicast] specified interface for the specified traffic type or for broadcast traffic
if no traffic type is entered.
show port-security [interface interface-id] Displays port security settings for the switch or for the specified
interface, including 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, and
the violation mode.
show port-security [interface interface-id] address Displays all secure MAC addresses configured on all switch interfaces
or on a specified interface with aging information for each address.
show port-security interface interface-id vlan Displays the number of secure MAC addresses configured per VLAN
on the specified interface.
This chapter describes how to configure Cisco Discovery Protocol (CDP) on the Catalyst 3750 Metro
switch.
Note For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release and the “System Management Commands” section in the Cisco IOS
Configuration Fundamentals Command Reference, Release 12.2.
Understanding CDP
CDP is a device discovery protocol that runs over Layer 2 (the data link layer) on all Cisco-manufactured
devices (routers, bridges, access servers, and switches) and allows network management applications to
discover Cisco devices that are neighbors of already known devices. With CDP, network management
applications can learn the device type and the Simple Network Management Protocol (SNMP) agent
address of neighboring devices running lower-layer, transparent protocols. This feature enables
applications to send SNMP queries to neighboring devices.
CDP runs on all media that support Subnetwork Access Protocol (SNAP). Because CDP runs over the
data-link layer only, two systems that support different network-layer protocols can learn about each
other.
Each CDP-configured device sends periodic messages to a multicast address, advertising at least one
address at which it can receive SNMP messages. The advertisements also contain time-to-live, or
holdtime information, which is the length of time a receiving device holds CDP information before
discarding it. Each device also listens to the messages sent by other devices to learn about neighboring
devices.
For a switch and connected endpoint devices running Cisco Medianet
• CDP identifies connected endpoints that communicate directly with the switch.
• To prevent duplicate reports of neighboring devices, only one wired switch reports the location
information.
• The wired switch and the endpoints both send and receive location information.
For information, go to
http://www.cisco.com/en/US/docs/ios/netmgmt/configuration/guide/nm_cdp_discover.html.
The switch supports CDP Version 2.
Configuring CDP
These sections include CDP configuration information and procedures:
• Default CDP Configuration, page 25-2
• Configuring the CDP Characteristics, page 25-2
• Disabling and Enabling CDP, page 25-3
• Disabling and Enabling CDP on an Interface, page 25-4
Note Steps 2 through 4 are all optional and can be performed in any order.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 cdp timer seconds (Optional) Set the transmission frequency of CDP updates in seconds.
The range is 5 to 254; the default is 60 seconds.
Command Purpose
Step 3 cdp holdtime seconds (Optional) Specify the amount of time a receiving device should hold the
information sent by your device before discarding it.
The range is 10 to 255 seconds; the default is 180 seconds.
Step 4 cdp advertise-v2 (Optional) Configure CDP to send Version-2 advertisements.
This is the default state.
Step 5 end Return to privileged EXEC mode.
Step 6 show cdp Verify configuration by displaying global information about CDP on the
device.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no form of the CDP commands to return to the default settings.
This example shows how to configure and verify CDP characteristics.
Switch# configure terminal
Switch(config)# cdp timer 50
Switch(config)# cdp holdtime 120
Switch(config)# cdp advertise-v2
Switch(config)# end
Switch# show cdp
Global CDP information:
Sending CDP packets every 50 seconds
Sending a holdtime value of 120 seconds
Sending CDPv2 advertisements is enabled
For additional CDP show commands, see the “Monitoring and Maintaining CDP” section on page 25-4.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 no cdp run Disable CDP.
Step 3 end Return to privileged EXEC mode.
Beginning in privileged EXEC mode, follow these steps to enable CDP when it has been disabled:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 cdp run Enable CDP after disabling it.
Step 3 end Return to privileged EXEC mode.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and enter the interface on which
you are disabling CDP.
Step 3 no cdp enable Disable CDP on an interface.
Step 4 end Return to privileged EXEC mode.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
Beginning in privileged EXEC mode, follow these steps to enable CDP on an interface when it has been
disabled:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and enter the interface on which
you are enabling CDP.
Step 3 cdp enable Enable CDP on an interface after disabling it.
Step 4 end Return to privileged EXEC mode.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
This example shows how to enable CDP on a port when it has been disabled.
Switch# configure terminal
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# cdp enable
Switch(config-if)# end
Command Description
clear cdp counters Reset the traffic counters to zero.
clear cdp table Delete the CDP table of information about neighbors.
show cdp Display global information, such as frequency of transmissions and the holdtime
for packets being sent.
show cdp entry entry-name Display information about a specific neighbor.
[protocol | version]
You can enter an asterisk (*) to display all CDP neighbors, or you can enter the
name of the neighbor about which you want information.
You can also limit the display to information about the protocols enabled on the
specified neighbor or information about the version of software running on the
device.
show cdp interface [interface-id] Display information about interfaces where CDP is enabled.
Enter an interface ID to display CDP information for that interface only.
show cdp neighbors [interface-id] Display information about neighbors, including device type, interface type and
[detail] number, holdtime settings, capabilities, platform, and port ID.
You can limit the display to neighbors on a specific interface or expand the
display to provide more detailed information.
show cdp traffic Display CDP counters, including the number of packets sent and received and
checksum errors.
This is an example of the output from the show cdp privileged EXEC commands:
Switch# show cdp
Global CDP information:
Sending CDP packets every 50 seconds
Sending a holdtime value of 120 seconds
Sending CDPv2 advertisements is enabled
This chapter describes how to configure the Link Layer Discovery Protocol (LLDP) and LLDP Media
Endpoint Discovery (LLDP-MED) on the Catalyst 3750 Metro switch. Unless otherwise noted, the term
switch refers to a standalone switch.
Note For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release and the “System Management Commands” section in the Cisco IOS
Configuration Fundamentals Command Reference, Release 12.2.
Understanding LLDP
The Cisco Discovery Protocol (CDP) is a device discovery protocol that runs over Layer 2 (the data link
layer) on all Cisco-manufactured devices (routers, bridges, access servers, and switches). CDP allows
network management applications to automatically discover and learn about other Cisco devices
connected to the network.
To support non-Cisco devices and to allow for interoperability between other devices, the switch
supports the IEEE 802.1AB Link Layer Discovery Protocol (LLDP). LLDP is a neighbor discovery
protocol that is used for network devices to advertise information about themselves to other devices on
the network. This protocol runs over the data-link layer, which allows two systems running different
network layer protocols to learn about each other.
LLDP supports a set of attributes that it uses to discover neighbor devices. These attributes contain type,
length, and value descriptions and are referred to as TLVs. LLDP supported devices can use TLVs to receive
and send information to their neighbors. Details such as configuration information, device capabilities,
and device identity can be advertised using this protocol.
The switch supports these basic management TLVs. These are mandatory LLDP TLVs.
• Port description TLV
• System name TLV
• System description
• System capabilities TLV
• Management address TLV
These organizationally specific LLDP TLVs are also advertised to support LLDP-MED.
• Port VLAN ID TLV ((IEEE 802.1 organizationally specific TLVs)
• MAC/PHY configuration/status TLV(IEEE 802.3 organizationally specific TLVs)
Understanding LLDP-MED
LLDP for Media Endpoint Devices (LLDP-MED) is an extension to LLDP that operates between
endpoint devices such as IP phones and network devices such as switches. It specifically provides
support for voice over IP (VoIP) applications and provides additional TLVs for capabilities discovery,
network policy, Power over Ethernet, and inventory management.
LLDP-MED supports these TLVs:
• LLDP-MED capabilities TLV
Allows LLDP-MED endpoints to determine the capabilities that the connected device supports and
what capabilities the device has enabled.
• Network policy TLV
Allows both network connectivity devices and endpoints to advertise VLAN configurations and
associated Layer 2 and Layer 3 attributes for the specific application on that port. For example, the
switch can notify a phone of the VLAN number that it should use. The phone can connect into any
switch, obtain its VLAN number, and then start communicating with the call control
• Power management TLV
Enables advanced power management between LLDP-MED endpoint and network connectivity
devices. Allows switches and phones to convey power information, such as how the device is
powered, power priority, and how much power the device needs.
• Inventory management TLV
Allows an endpoint to transmit detailed inventory information about itself to the switch, including
information hardware revision, firmware version, software version, serial number, manufacturer
name, model name, and asset ID TLV.
• Location TLV
Provides location information from the switch to the endpoint device. The location TLV can send
this information:
– Civic location information
Provides the civic address information and postal information. Examples of civic location
information are street address, road name, and postal community name information.
Note Steps 2 through 5 are all optional and can be performed in any order.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 lldp holdtime seconds (Optional) Specify the amount of time a receiving device should hold the
information sent by your device before discarding it.
The range is 0 to 65535 seconds; the default is 120 seconds.
Step 3 lldp reinit (Optional) Specify the delay time in seconds for LLDP to initialize on any
interface.
The range is 2 to 5 seconds; the default is 2 seconds.
Step 4 lldp timer seconds (Optional) Set the transmission frequency of LLDP updates in seconds.
The range is 5 to 65534 seconds; the default is 30 seconds.
Step 5ll lldp tlv-select (Optional) Specify the LLDP TLVs to send or receive.
Step 6 interface interface-id Specify the interface on which you are enabling LLDP, and enter interface
configuration mode.
Step 7 lldp med-tlv-select (Optional) Specify the LLDP-MED TLVs to send or receive.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no form of each of the LLDP commands to return to the default setting.
This example shows how to configure LLDP characteristics.
Switch# configure terminal
Switch(config)# lldp holdtime 120
Switch(config)# lldp reinit 2
Switch(config)# lldp timer 30
Switch(config)# end
For additional LLDP show commands, see the “Monitoring and Maintaining LLDP and LLDP-MED”
section on page 26-7.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 no lldp run Disable LLDP.
Step 3 end Return to privileged EXEC mode.
Beginning in privileged EXEC mode, follow these steps to enable LLDP-MED when it has been
disabled:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 lldp run Enable LLDP.
Step 3 end Return to privileged EXEC mode.
Beginning in privileged EXEC mode, follow these steps to disable LLDP on an interface.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface on which you are disabling LLDP, and enter
interface configuration mode.
Step 3 no lldp transmit No LLDP packets are sent on the interface.
Step 4 no lldp receive No LLDP packets are received on the interface.
Command Purpose
Step 5 end Return to privileged EXEC mode.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
Beginning in privileged EXEC mode, follow these steps to enable LLDP on an interface when it has been
disabled:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface on which you are enabling LLDP-MED, and
enter interface configuration mode.
Step 3 lldp transmit LLDP packets are sent on the interface.
Step 4 lldp receive LLDP packets are received on the interface.
Step 5 end Return to privileged EXEC mode.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
Beginning in privileged EXEC mode, follow these steps to disable a TLV on an interface:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface on which you are configuring a LLDP-MED
TLV, and enter interface configuration mode.
Step 3 no lldp med-tlv-select tlv Specify the TLV to disable.
Step 4 end Return to privileged EXEC mode.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
Beginning in privileged EXEC mode, follow these steps to enable a TLV on an interface:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface on which you are configuring an LLDP-MED
TLV, and enter interface configuration mode.
Step 3 lldp med-tlv-select tlv Specify the TLV to enable.
Step 4 end Return to privileged EXEC mode.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
This example shows how to enable a TLV on an interface when it has been disabled.
Switch# configure terminal
Switch(config)# interface GigabitEthernet1/0/1
Switch(config-if)# lldp med-tlv-select inventory-management
Switch(config-if)# end
Command Description
clear lldp counters Reset the traffic counters to zero.
clear lldp table Delete the LLDP table of information about neighbors.
show lldp Display global information, such as frequency of transmissions, the holdtime for
packets being sent, and the delay time for LLDP to initialize on an interface.
show lldp entry entry-name Display information about a specific neighbor.
You can enter an asterisk (*) to display all neighbors, or you can enter the name
of the neighbor about which you want information.
show lldp interface [interface-id] Display information about interfaces where LLDP is enabled.
You can limit the display to the interface about which you want information.
Command Description
show lldp neighbors [interface-id] Display information about neighbors, including device type, interface type and
[detail] number, holdtime settings, capabilities, and port ID.
You can limit the display to neighbors of a specific interface or expand the display
to provide more detailed information.
show lldp traffic Display LLDP counters, including the number of packets sent and received,
number of packets discarded, and number of unrecognized TLVs.
This chapter describes how to configure the UniDirectional Link Detection (UDLD) protocol on the
Catalyst 3750 Metro switch.
Note For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
Understanding UDLD
UDLD is a Layer 2 protocol that enables devices connected through fiber-optic or twisted-pair Ethernet
cables to monitor the physical configuration of the cables and detect when a unidirectional link exists.
All connected devices must support UDLD for the protocol to successfully identify and disable
unidirectional links. When UDLD detects a unidirectional link, it administratively shuts down the
affected interface and alerts you. Unidirectional links can cause a variety of problems, including
spanning-tree topology loops.
Modes of Operation
UDLD supports two modes of operation: normal (the default) and aggressive. In normal mode, UDLD
can detect unidirectional links due to misconnected ports on fiber-optic connections. In aggressive mode,
UDLD also can detect unidirectional links due to one-way traffic on fiber-optic and on twisted-pair links
and to misconnected ports on fiber-optic links.
In normal and in aggressive mode, UDLD works with the Layer 1 mechanisms to learn 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 interfaces. When you enable both autonegotiation and UDLD, the 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 sent by a local device is received by its neighbor but traffic
from the neighbor is not received by the local device.
In normal mode, UDLD can detect a unidirectional link when fiber strands in a fiber-optic port are
misconnected and the Layer 1 mechanisms do not detect this misconnection. If the ports are connected
correctly but the traffic is one way, UDLD does not detect the unidirectional link because the Layer 1
mechanism, which is supposed to detect this condition, does not do so. In this case, the logical link is
considered undetermined, and UDLD does not disable the interface.
When UDLD is in normal mode, if one of the fiber strands in a pair is disconnected, as long as
autonegotiation is active, the link does not stay up because the Layer 1 mechanisms detects a physical
problem with the link. In this case, UDLD does not take any action and the logical link is considered
undetermined.
In aggressive mode, UDLD can detect a unidirectional link by using the previous detection methods.
UDLD in aggressive mode also can detect a unidirectional link on a point-to-point link on which no
failure between the two devices is allowed. It also can detect a unidirectional link when one of these
problems exists:
• On fiber-optic or twisted-pair links, one of the interfaces cannot send or receive traffic.
• On fiber-optic or twisted-pair links, one of the interfaces is down while the other is up.
• One of the fiber strands in a pair is disconnected.
In these cases, UDLD shuts down the affected interface.
In a point-to-point link, UDLD hello packets can be considered as a heart beat whose presence
guarantees the health of the link. Conversely, the loss of the heart beat means that the link must be shut
down if it is not possible to re-establish a bidirectional link.
If both fibers are working normally from a Layer 1 perspective, UDLD in aggressive mode detects
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.
Switch A
TX RX
Switch B successfully
receives traffic from
Switch A on this port. However, Switch A does not receive traffic
from Switch B on the same port. If UDLD
is in aggressive mode, it detects the
problem and disables the port. If UDLD is
in normal mode, the logical link is
considered undetermined, and UDLD
does not disable the interface.
TX RX
Switch B 98648
Configuring UDLD
This section describes how to configure UDLD on your switch. It contains this configuration
information:
• Default UDLD Configuration, page 27-4
• UDLD Configuration Guidelines, page 27-4
• Enabling UDLD Globally, page 27-5
• Enabling UDLD on an Interface, page 27-5
• Resetting an Interface Disabled by UDLD, page 27-6
Caution Loop guard works only on point-to-point links. We recommend that each end of the link has a directly
connected device that is running STP.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 udld {aggressive | enable | message time Specify the UDLD mode of operation:
message-timer-interval}
• aggressive—Enables UDLD in aggressive mode on all fiber-optic
ports.
• enable—Enables UDLD in normal mode on all fiber-optic ports on
the switch. UDLD is disabled by default.
An individual interface configuration overrides the setting of the
udld enable global configuration command.
For more information about aggressive and normal modes, see the
“Modes of Operation” section on page 27-1.
• message time message-timer-interval—Configures the period of
time between UDLD probe messages on interfaces that are in the
advertisement phase and are detected to be bidirectional. The range
is 1 to 90 seconds.
Note This command affects fiber-optic ports only. Use the udld
interface configuration command to enable UDLD on other
interface types. For more information, see the “Enabling UDLD
on an Interface” section on page 27-5.
Step 3 end Return to privileged EXEC mode.
Step 4 show udld Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable UDLD globally, use the no udld enable global configuration command to disable normal
mode UDLD on all fiber-optic ports. Use the no udld aggressive global configuration command to
disable aggressive mode UDLD on all fiber-optic ports.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface to be enabled for UDLD, and enter interface
configuration mode.
Command Purpose
Step 3 udld port {aggressive | disable} UDLD is disabled by default.
• udld port—Enables UDLD in normal mode on the specified
interface.
• udld port aggressive—Enables UDLD in aggressive mode on the
specified interface.
• udld port disable—Disables UDLD on the specified fiber-optic
port. This command overrides the UDLD global setting and is
available only on fiber-optic ports.
For more information about aggressive and normal modes, see the
“Modes of Operation” section on page 27-1.
Step 4 end Return to privileged EXEC mode.
Step 5 show udld interface-id Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
Command Purpose
Step 1 udld reset Reset all interfaces disabled by UDLD.
Step 2 show udld Verify your entries.
This chapter describes how to configure Switched Port Analyzer (SPAN) and Remote SPAN (RSPAN)
on the Catalyst 3750 Metro switch.
Note For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
Local SPAN
Local SPAN supports a SPAN session entirely within one switch; all source ports or source VLANs and
destination ports reside in the same switch. Local SPAN copies traffic from one or more source ports in
any VLAN or from one or more VLANs to a destination port for analysis. For example, in Figure 28-1,
all traffic on port 5 (the source port) is mirrored to port 10 (the destination port). A network analyzer on
port 10 receives all network traffic from port 5 without being physically attached to port 5.
6 7
5 8 11
4 9 12
3 10
2
1
43580
Network analyzer
Remote SPAN
RSPAN supports source ports, source VLANs, and destination ports on different switches, enabling
remote monitoring of multiple switches across your network. Figure 28-2 shows RSPAN source ports
configured on Switch A and Switch B with RSPAN destination ports configured on Switch C. The traffic
for each RSPAN session is carried over a user-specified RSPAN VLAN that is dedicated for that RSPAN
session in all participating switches. The RSPAN traffic from the source ports or VLANs is copied into
the RSPAN VLAN and forwarded over trunk ports carrying the RSPAN VLAN to a destination session
monitoring the RSPAN VLAN. Each RSPAN source switch must have either ports or VLANs as RSPAN
sources. The destination is always a physical port.
RSPAN
destination ports
RSPAN
Switch C
destination
session
Intermediate switches
must support RSPAN VLAN
RSPAN
VLAN
Switch A Switch B
RSPAN RSPAN
source source
session A session B
101366
RSPAN RSPAN
source ports source ports
SPAN Sessions
SPAN sessions (local or remote) allow you to monitor traffic on one or more ports, or one or more
VLANs, and send the monitored traffic to one or more destination ports.
A local SPAN session is an association of a destination port with source ports or source VLANs, all on
a single network device. Local SPAN does not have separate source and destination sessions. Local
SPAN sessions gather a set of ingress and egress packets specified by the user and form them into a
stream of SPAN data, which is directed to the destination port.
RSPAN consists of at least one RSPAN source session, an RSPAN VLAN, and at least one RSPAN
destination session. You separately configure RSPAN source sessions and RSPAN destination sessions
on different network devices. To configure an RSPAN source session on a device, you associate a set of
source ports or source VLANs with an RSPAN VLAN. The output of this session is the stream of SPAN
packets that are sent to the RSPAN VLAN. To configure an RSPAN destination session on another
device, you associate the destination port with the RSPAN VLAN. The destination session collects all
RSPAN VLAN traffic and sends it out the RSPAN destination port.
An RSPAN source session is very similar to a local SPAN session, except for where the packet stream
is directed. In an RSPAN source session, SPAN packets are relabeled with the RSPAN VLAN ID and
directed over normal trunk ports to the destination switch.
An RSPAN destination session takes all packets received on the RSPAN VLAN, strips off the VLAN
tagging, and presents them on the destination port. Its purpose is to present a copy of all RSPAN VLAN
packets (except Layer 2 control packets) to the user for analysis.
There can be more than one source session and more than one destination session active in the same
RSPAN VLAN. There can also be intermediate switches separating the RSPAN source and destination
sessions. These switches need not be capable of running RSPAN, but they must handle the requirements
of the RSPAN VLAN (see the “RSPAN VLAN” section on page 28-8).
Traffic monitoring in a SPAN session has these restrictions:
• Sources can be ports or VLANs, but you cannot mix source ports and source VLANs in the same
session.
• The switch supports up to two source sessions (local SPAN and RSPAN source sessions). You can
run both a local SPAN and an RSPAN source session in the same switch. The switch supports a total
of 66 source and RSPAN destination sessions.
• ES ports do not support SPAN source sessions.
• You can have multiple destination ports in a SPAN session, but no more than 64 destination ports.
• You can configure two separate SPAN or RSPAN source sessions with separate or overlapping sets
of SPAN source ports and VLANs. Both switched and routed ports can be configured as SPAN
sources and destinations.
• SPAN sessions do not interfere with the normal operation of the switch. However, an oversubscribed
SPAN destination, for example, a 10-Mbps port monitoring a 100-Mbps port, can result in dropped
or lost packets.
• When RSPAN is enabled, each packet being monitored is transmitted twice, once as normal traffic
and once as a monitored packet. Therefore monitoring a large number of ports or VLANs could
potentially generate large amounts of network traffic.
• You can configure SPAN sessions on disabled ports; however, a SPAN session does not become
active unless you enable the destination port and at least one source port or VLAN for that session.
• The switch does not support a combination of local SPAN and RSPAN in a single session. That is,
an RSPAN source session cannot have a local destination port, an RSPAN destination session cannot
have a local source port, and an RSPAN destination session and an RSPAN source session that are
using the same RSPAN VLAN cannot run on the same switch.
Monitored Traffic
SPAN sessions can monitor these traffic types:
• Receive (Rx) SPAN—The goal of receive (or ingress) SPAN is to monitor as much as possible all
the packets received by the source interface or VLAN before any modification or processing is
performed by the switch. A copy of each packet received by the source is sent to the destination port
for that SPAN session.
Packets that are modified because of routing or quality of service (QoS)—for example, modified
Differentiated Services Code Point (DSCP)—are copied before modification.
Features that can cause a packet to be dropped during receive processing have no effect on ingress
SPAN; the destination port receives a copy of the packet even if the actual incoming packet is
dropped. These features include IP standard and extended input access control lists (ACLs), ingress
QoS policing, VLAN ACLs and egress QoS policing.
• Transmit (Tx) SPAN—The goal of transmit (or egress) SPAN is to monitor as much as possible all
the packets sent by the source interface after all modification and processing is performed by the
switch. A copy of each packet sent by the source is sent to the destination port for that SPAN session.
The copy is provided after the packet is modified.
Packets that are modified because of routing—for example, with modified time-to-live (TTL),
MAC-address, or QoS values—are duplicated (with the modifications) at the destination port.
Features that can cause a packet to be dropped during transmit processing also affect the duplicated
copy for SPAN. These features include IP standard and extended output ACLs and egress QoS
policing.
• Both—In a SPAN session, you can also monitor a port or VLAN for both received and sent packets.
This is the default.
The default configuration for local SPAN session ports is to send all packets untagged. SPAN also does
not normally monitor bridge protocol data unit (BPDU) packets and Layer 2 protocols, such as Cisco
Discovery Protocol (CDP), VLAN Trunk Protocol (VTP), Dynamic Trunking Protocol (DTP), Spanning
Tree Protocol (STP), and Port Aggregation Protocol (PAgP). However, when you enter the
encapsulation replicate keywords when configuring a destination port, these changes occur:
• Packets are sent on the destination port with the same encapsulation—untagged, IEEE 802.1Q, or
Inter-Switch Link (ISL)—that they had on the source port.
• Packets of all types, including BPDU and Layer 2 protocol packets, are monitored.
Therefore, a local SPAN session with encapsulation replicate enabled can have a mixture of untagged,
IEEE 802.1Q, and ISL tagged packets appear on the destination port.
Switch congestion can cause packets to be dropped at ingress source ports, egress source ports, or SPAN
destination ports. In general, these characteristics are independent of one another. For example:
• A packet might be forwarded normally but dropped from monitoring due to an oversubscribed SPAN
destination port.
• An ingress packet might be dropped from normal forwarding, but still appear on the SPAN
destination port.
• An egress packet dropped because of switch congestion is also dropped from egress SPAN.
In some SPAN configurations, multiple copies of the same source packet are sent to the SPAN
destination port. For example, a bidirectional (both Rx and Tx) SPAN session is configured for the Rx
monitor on port A and Tx monitor on port B. If a packet enters the switch through port A and is switched
to port B, both incoming and outgoing packets are sent to the destination port. Both packets are the same
(unless a Layer-3 rewrite occurs, in which case the packets are different because of the packet
modification).
Source Ports
A source port (also called a monitored port) is a switched or routed port that you monitor for network
traffic analysis. In a local SPAN session or RSPAN source session, you can monitor source ports or
VLANs for traffic in one or both directions. The switch supports any number of source ports (up to the
maximum number of available ports on the switch) and any number of source VLANs (up to the
maximum number of VLANs supported). However, the switch supports a maximum of two sessions
(local or RSPAN) with source ports or VLANs and you cannot mix ports and VLANs in a single session.
Source VLANs
VLAN-based SPAN (VSPAN) is the monitoring of the network traffic in one or more VLANs. The SPAN
or RSPAN source interface in VSPAN is a VLAN ID and traffic is monitored on all the ports for that
VLAN.
VSPAN has these characteristics:
• All active ports in the source VLAN (except ES ports) are included as source ports and can be
monitored in either or both directions.
• On a given port, only traffic on the monitored VLAN is sent to the destination port.
• If a destination port belongs to a source VLAN, it is excluded from the source list and is not
monitored.
• If ports are added to or removed from the source VLANs, the traffic on the source VLAN received
by those ports is added to or removed from the sources being monitored.
• You cannot use filter VLANs in the same session with VLAN sources.
• You can monitor only Ethernet VLANs.
VLAN Filtering
When you monitor a trunk port as a source port, by default, all VLANs active on the trunk are monitored.
You can limit SPAN traffic monitoring on trunk source ports to specific VLANs by using VLAN
filtering.
• VLAN filtering applies only to trunk ports or to voice VLAN ports.
• VLAN filtering applies only to port-based sessions and is not allowed in sessions with VLAN
sources.
• When a VLAN filter list is specified, only those VLANs in the list are monitored on trunk ports or
on voice VLAN access ports.
• SPAN traffic coming from other port types is not affected by VLAN filtering; that is, all VLANs are
allowed on other ports.
• VLAN filtering affects only traffic forwarded to the destination SPAN port and does not affect the
switching of normal traffic.
Destination Port
Each local SPAN session or RSPAN destination session must have a destination port (also called a
monitoring port) that receives a copy of traffic from the source ports or VLANs and sends the SPAN
packets to the user, usually a network analyzer.
A destination port has these characteristics:
• For a local SPAN session, the destination port must reside on the same switch as the source port. For
an RSPAN session, it is located on the switch containing the RSPAN destination session. There is
no destination port on a switch running only an RSPAN source session.
• When a port is configured as a SPAN destination port, the configuration overwrites the original port
configuration. When the SPAN destination configuration is removed, the port reverts to its previous
configuration. If a configuration change is made to the port while it is acting as a SPAN destination
port, the change does not take effect until the SPAN destination configuration had been removed.
Note Exception. When QoS is configured on the SPAN destination port, QoS takes effect immediately.
• If the port was in an EtherChannel group, it is removed from the group while it is a destination port.
If it was a routed port, it is no longer a routed port.
• It can be any Ethernet physical port.
• It cannot be a secure port.
• It cannot be a source port.
• It cannot be an EtherChannel group or a VLAN.
• It can participate in only one SPAN session at a time (a destination port in one SPAN session cannot
be a destination port for a second SPAN session).
• When it is active, incoming traffic is disabled. The port does not transmit any traffic except that
required for the SPAN session. Incoming traffic is never learned or forwarded on a destination port.
• If ingress traffic forwarding is enabled for a network security device, the destination port forwards
traffic at Layer 2.
• It does not participate in any of the Layer 2 protocols (STP, VTP, CDP, DTP, PagP).
• A destination port that belongs to a source VLAN of any SPAN session is excluded from the source
list and is not monitored.
• The maximum number of destination ports in a switch is 64.
Local SPAN and RSPAN destination ports behave differently regarding VLAN tagging and
encapsulation:
• For local SPAN, if the encapsulation replicate keywords are specified for the destination port, these
packets appear with the original encapsulation (untagged, ISL, or IEEE 802.1Q). If these keywords
are not specified, packets appear in the untagged format. Therefore, the output of a local SPAN
session with encapsulation replicate enabled can contain a mixture of untagged, IEEE 802.1Q, or
ISL tagged packets.
• For RSPAN, the original VLAN ID is lost because it is overwritten by the RSPAN VLAN
identification. Therefore, all packets appear on the destination port as untagged.
RSPAN VLAN
The RSPAN VLAN carries SPAN traffic between RSPAN source and destination sessions. It has these
special characteristics:
• All traffic in the RSPAN VLAN is always flooded.
• No MAC address learning occurs on the RSPAN VLAN.
• RSPAN VLAN traffic only flows on trunk ports.
• RSPAN VLANs must be configured in VLAN configuration mode by using the remote-span VLAN
configuration mode command.
• STP can run on RSPAN VLAN trunks but not on SPAN destination ports.
• An RSPAN VLAN cannot be a private-VLAN primary or secondary VLAN.
For VLANs 1 to 1005 that are visible to VLAN Trunking Protocol (VTP), the VLAN ID and its
associated RSPAN characteristic are propagated by VTP. If you assign an RSPAN VLAN ID in the
extended VLAN range (1006 to 4094), you must manually configure all intermediate switches.
It is normal to have multiple RSPAN VLANs in a network at the same time with each RSPAN VLAN
defining a network-wide RSPAN session. That is, multiple RSPAN source sessions anywhere in the
network can contribute packets to the RSPAN session. It is also possible to have multiple RSPAN
destination sessions throughout the network, monitoring the same RSPAN VLAN and presenting traffic
to the user. The RSPAN VLAN ID separates the sessions.
A physical port that belongs to an EtherChannel group can be configured as a SPAN source port and
still be a part of the EtherChannel. In this case, data from the physical port is monitored as it
participates in the EtherChannel. However, if a physical port that belongs to an EtherChannel group
is configured as a SPAN destination, it is removed from the group. After the port is removed from
the SPAN session, it rejoins the EtherChannel group. Ports removed from an EtherChannel group
remain members of the group, but they are in the inactive or suspended state.
If a physical port that belongs to an EtherChannel group is a destination port and the EtherChannel
group is a source, the port is removed from the EtherChannel group and from the list of monitored
ports.
• Multicast traffic can be monitored. For egress and ingress port monitoring, only a single unedited
packet is sent to the SPAN destination port. It does not reflect the number of times the multicast
packet is sent.
• A private-VLAN port cannot be a SPAN destination port.
• A secure port cannot be a SPAN destination port.
For SPAN sessions, do not enable port security on ports with monitored egress when ingress
forwarding is enabled on the destination port. For RSPAN source sessions, do not enable port
security on any ports with monitored egress.
• An IEEE 802.1x port can be a SPAN source port. You can enable IEEE 802.1x on a port that is a
SPAN destination port; however, IEEE 802.1x is disabled until the port is removed as a SPAN
destination.
For SPAN sessions, do not enable IEEE 802.1x on ports with monitored egress when ingress
forwarding is enabled on the destination port. For RSPAN source sessions, do not enable IEEE
802.1x on any ports that are egress monitored.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 no monitor session {session_number | all | Remove any existing SPAN configuration for the session.
local | remote}
For session_number, the range is from 1 to 66.
Specify all to remove all SPAN sessions, local to remove all local
sessions, or remote to remove all remote SPAN sessions.
Step 3 monitor session session_number source Specify the SPAN session and the source port (monitored port).
{interface interface-id | vlan vlan-id} [, | -] For session_number, the range is from 1 to 66.
[both | rx | tx]
For interface-id, specify the source port or source VLAN to monitor.
• For source interface-id, specify the source port to monitor. Valid
interfaces include physical interfaces and port-channel logical
interfaces (port-channel port-channel-number). Valid port
channel numbers are 1 to 12.
• For vlan-id, specify the source VLAN to monitor. The range is 1
to 4094 (excluding the RSPAN VLAN).
Note A single session can include multiple sources (ports or
VLANs), defined in a series of commands, but you cannot
combine source ports and source VLANs in one session.
Command Purpose
Step 4 monitor session session_number Specify the SPAN session and the destination port (monitoring port).
destination {interface interface-id [, | -]
For session_number, specify the session number entered in step 3.
[encapsulation replicate]}
Note For local SPAN, you must use the same session number for the
source and destination interfaces.
To delete a SPAN session, use the no monitor session session_number global configuration command.
To remove a source or destination port or VLAN from the SPAN session, use the no monitor session
session_number source {interface interface-id | vlan vlan-id} global configuration command or the no
monitor session session_number destination interface interface-id global configuration command. For
destination interfaces, the encapsulation replicate keywords are ignored with the no form of the
command.
This example shows how to set up local SPAN session 1, for monitoring source port traffic to a
destination port. First, any existing SPAN configuration for session 1 is deleted, and then bidirectional
traffic is mirrored from source Gigabit Ethernet port 1 to destination Gigabit Ethernet port 2, retaining
the encapsulation method.
Switch(config)# no monitor session 1
Switch(config)# monitor session 1 source interface gigabitethernet1/0/1
Switch(config)# monitor session 1 destination interface gigabitethernet1/0/2
encapsulation replicate
Switch(config)# end
This example shows how to remove a port as a SPAN source for SPAN session 1:
Switch(config)# no monitor session 1 source interface gigabitethernet1/0/1
Switch(config)# end
This example shows how to disable monitoring received traffic on a port that was configured for
bidirectional monitoring:
Switch(config)# no monitor session 1 source interface gigabitethernet1/0/1 rx
Traffic received on port 1 is not monitored, but traffic sent from this port continues to be monitored.
This example shows how to remove any existing configuration on SPAN session 2, configure SPAN
session 2 to monitor received traffic on all ports belonging to VLANs 1 through 3, and send it to a
destination interface. The configuration is then modified to also monitor all traffic on all ports belonging
to VLAN 10.
Switch(config)# no monitor session 2
Switch(config)# monitor session 2 source vlan 1 - 3 rx
Switch(config)# monitor session 2 destination interface gigabitethernet1/0/2
Switch(config)# monitor session 2 source vlan 10
Switch(config)# end
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 no monitor session {session_number | all | Remove any existing SPAN configuration for the session.
local | remote}
Step 3 monitor session session_number source Specify the SPAN session and the source port (monitored port).
{interface interface-id | vlan vlan-id} [, | -]
[both | rx | tx]
Step 4 monitor session session_number Specify the SPAN session, the destination port, the packet
destination {interface interface-id [, | -] encapsulation, and the ingress VLAN and encapsulation.
[encapsulation replicate] [ingress {dot1q
For session_number, specify the session number entered in Step 3.
vlan vlan-id | isl | untagged vlan vlan-id |
vlan vlan-id}]} For interface-id, specify the destination port. The destination
interface must be a physical port; it cannot be an EtherChannel, and
it cannot be a VLAN.
(Optional) [, | -] Specify a series or range of interfaces. Enter a space
before and after the comma or hyphen.
(Optional) Enter encapsulation replicate to specify that the
destination interface replicates the source interface encapsulation
method. If not selected, the default is to send packets in native form
(untagged).
Enter ingress with keywords to enable ingress traffic forwarding on
the destination port and specify the encapsulation type:
• dot1q vlan vlan-id—Forward ingress packets with IEEE 802.1Q
encapsulation with the specified VLAN as the default VLAN.
• isl—Forward ingress packets with ISL encapsulation.
• untagged vlan vlan-id or vlan vlan-id—Forward ingress packets
with untagged encapsulation type with the specified VLAN as
the default VLAN.
Step 5 end Return to privileged EXEC mode.
Command Purpose
Step 6 show monitor [session session_number] Verify the configuration.
show running-config
Step 7 copy running-config startup-config (Optional) Save the configuration in the configuration file.
To delete a SPAN session, use the no monitor session session_number global configuration command.
To remove a source or destination port or VLAN from the SPAN session, use the no monitor session
session_number source {interface interface-id | vlan vlan-id} global configuration command or the no
monitor session session_number destination interface interface-id global configuration command. For
destination interfaces, the encapsulation and ingress options are ignored with the no form of the
command.
This example shows how to remove any existing configuration on SPAN session 2, configure SPAN
session 2 to monitor received traffic on Gigabit Ethernet source port 1, and send it to destination Gigabit
Ethernet port 2 with the same egress encapsulation type as the source port, and enable ingress forwarding
with IEEE 802.1Q encapsulation and VLAN 6 as the default ingress VLAN.
Switch(config)# no monitor session 2
Switch(config)# monitor session 2 source gigabitethernet1/0/1 rx
Switch(config)# monitor session 2 destination interface gigabitethernet1/0/2 encapsulation
replicate ingress dot1q vlan 6
Switch(config)# end
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 no monitor session {session_number | all | Remove any existing SPAN configuration for the session.
local | remote}
For session_number, the range is from 1 to 66.
Specify all to remove all SPAN sessions, local to remove all local
sessions, or remote to remove all remote SPAN sessions.
Step 3 monitor session session_number source Specify the characteristics of the source port (monitored port) and
interface interface-id SPAN session.
For session_number, the range is from 1 to 66.
For interface-id, specify the source port to monitor. The interface
specified must already be configured as a trunk port.
Step 4 monitor session session_number filter vlan Limit the SPAN source traffic to specific VLANs.
vlan-id [, | -] For session_number, enter the session number specified in Step 3.
For vlan-id, the range is 1 to 4094.
(Optional) Use a comma (,) to specify a series of VLANs, or use a
hyphen (-) to specify a range of VLANs. Enter a space before and after
the comma; enter a space before and after the hyphen.
Command Purpose
Step 5 monitor session session_number Specify the SPAN session and the destination port (monitoring port).
destination {interface interface-id [, | -]
For session_number, specify the session number entered in step 3.
[encapsulation replicate]}
For interface-id, specify the destination port. The destination interface
must be a physical port; it cannot be an EtherChannel, and it cannot
be a VLAN.
(Optional) [, | -] Specify a series or range of interfaces. Enter a space
before and after the comma; enter a space before and after the hyphen.
(Optional) Enter encapsulation replicate to specify that the
destination interface replicates the source interface encapsulation
method. If not selected, the default is to send packets in native form
(untagged).
Step 6 end Return to privileged EXEC mode.
Step 7 show monitor [session session_number] Verify the configuration.
show running-config
Step 8 copy running-config startup-config (Optional) Save the configuration in the configuration file.
To monitor all VLANs on the trunk port, use the no monitor session session_number filter global
configuration command.
This example shows how to remove any existing configuration on SPAN session 2, configure SPAN
session 2 to monitor traffic received on Gigabit Ethernet trunk port 2, and send traffic for only VLANs
1 through 5 and 9 to destination Gigabit Ethernet port 1.
Switch(config)# no monitor session 2
Switch(config)# monitor session 2 source interface gigabitethernet1/0/2 rx
Switch(config)# monitor session 2 filter vlan 1 - 5, 9
Switch(config)# monitor session 2 destination interface gigabitethernet1/0/1
Switch(config)# end
Configuring RSPAN
This section describes how to configure RSPAN on your switch. It contains this configuration
information:
• RSPAN Configuration Guidelines, page 28-16
• Configuring a VLAN as an RSPAN VLAN, page 28-16
• Creating an RSPAN Source Session, page 28-17
• Creating an RSPAN Destination Session, page 28-19
• Creating an RSPAN Destination Session, page 28-19
• Specifying VLANs to Filter, page 28-22
Beginning in privileged EXEC mode, follow these steps to create an RSPAN VLAN:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 vlan vlan-id Enter a VLAN ID to create a VLAN, or enter the VLAN ID of an
existing VLAN, and enter VLAN configuration mode. The range is
from 2 to 1001 and from 1006 to 4094.
Note The RSPAN VLAN cannot be VLAN 1 (the default VLAN)
or VLAN IDs 1002 through 1005 (reserved for Token Ring
and FDDI VLANs).
Step 3 remote-span Configure the VLAN as an RSPAN VLAN.
Step 4 end Return to privileged EXEC mode.
Step 5 copy running-config startup-config (Optional) Save the configuration in the configuration file.
To remove the remote SPAN characteristic from a VLAN and convert it back to a normal VLAN, use the
no remote-span VLAN configuration command.
This example shows how to create RSPAN VLAN 901.
Switch(config)# vlan 901
Switch(config-vlan)# remote span
Switch(config-vlan)# end
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 no monitor session {session_number | all | Remove any existing RSPAN configuration for the session.
local | remote}
For session_number, the range is from 1 to 66.
Specify all to remove all RSPAN sessions, local to remove all local
sessions, or remote to remove all remote SPAN sessions.
Command Purpose
Step 3 monitor session session_number source Specify the RSPAN session and the source port (monitored port).
{interface interface-id | vlan vlan-id} [, | -]
For session_number, the range is from 1 to 66.
[both | rx | tx]
Enter a source port or source VLAN for the RSPAN session:
• For interface-id, specify the source port to monitor. Valid
interfaces include physical interfaces and port-channel logical
interfaces (port-channel port-channel-number). Valid port
channel numbers are 1 to 12.
• For vlan-id, specify the source VLAN to monitor. The range is 1
to 4094 (excluding the RSPAN VLAN).
Note A single session can include multiple sources (ports or
VLANs), defined in a series of commands, but you cannot
combine source ports and source VLANs in one session.
To delete a SPAN session, use the no monitor session session_number global configuration command.
To remove a source port or VLAN from the SPAN session, use the no monitor session session_number
source {interface interface-id | vlan vlan-id} global configuration command. To remove the RSPAN
VLAN from the session, use the no monitor session session_number destination remote vlan vlan-id.
This example shows how to remove any existing RSPAN configuration for session 1, configure RSPAN
session 1 to monitor multiple source interfaces, and configure the destination as RSPAN VLAN 901.
Switch(config)# no monitor session 1
Switch(config)# monitor session 1 source interface fastethernet1/0/10 tx
Switch(config)# monitor session 1 source interface gigabitethernet1/0/1 rx
Switch(config)# monitor session 1 source interface gigabitethernet1/0/2
Switch(config)# monitor session 1 source interface port-channel 12
Switch(config)# monitor session 1 destination remote vlan 901
Switch(config)# end
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 vlan vlan-id Enter the VLAN ID of the RSPAN VLAN created from the source
switch, and enter VLAN configuration mode.
Note If both switches are participating in VTP and the RSPAN
VLAN ID is from 2 to 1005, Steps 2 through 4 are not
required because the RSPAN VLAN ID is propagated
through the VTP network.
Step 3 remote-span Identify the VLAN as the RSPAN VLAN.
Step 4 exit Return to global configuration mode.
Step 5 no monitor session {session_number | all | Remove any existing RSPAN configuration for the session.
local | remote}
For session_number, the range is from 1 to 66.
Specify all to remove all RSPAN sessions, local to remove all local
sessions, or remote to remove all remote SPAN sessions.
Step 6 monitor session session_number source Specify the RSPAN session and the source RSPAN VLAN.
remote vlan vlan-id
For session_number, the range is from 1 to 66.
For vlan-id, specify the source RSPAN VLAN to monitor.
Step 7 monitor session session_number Specify the RSPAN session and the destination interface.
destination interface interface-id
For session_number, enter the number defined in Step 6.
Note In an RSPAN destination session, you must use the same
session number for the source RSPAN VLAN and the
destination port.
To delete a SPAN session, use the no monitor session session_number global configuration command.
To remove a destination port from the SPAN session, use the no monitor session session_number
destination interface interface-id global configuration command. To remove the RSPAN VLAN from
the session, use the no monitor session session_number source remote vlan vlan-id.
This example shows how to configure VLAN 901 as the source remote VLAN and Gigabit Ethernet
port 2 as the destination interface:
Switch(config)# monitor session 1 source remote vlan 901
Switch(config)# monitor session 1 destination interface gigabitethernet1/0/2
Switch(config)# end
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 no monitor session {session_number | all | Remove any existing SPAN configuration for the session.
local | remote}
Step 3 monitor session session_number source Specify the RSPAN session and the source RSPAN VLAN.
remote vlan vlan-id
For session_number, the range is 1 to 66.
For vlan-id, specify the source RSPAN VLAN to monitor.
Command Purpose
Step 4 monitor session session_number Specify the SPAN session, the destination port, the packet
destination {interface interface-id [, | -] encapsulation, and the incoming VLAN and encapsulation.
[ingress {dot1q vlan vlan-id | isl | untagged For session_number, enter the number defined in Step 4.
vlan vlan-id | vlan vlan-id}]}
Note In an RSPAN destination session, you must use the same
session number for the source RSPAN VLAN and the
destination port.
To delete an RSPAN session, use the no monitor session session_number global configuration
command. To remove a destination port from the RSPAN session, use the no monitor session
session_number destination interface interface-id global configuration command. The ingress options
are ignored with the no form of the command.
This example shows how to configure VLAN 901 as the source remote VLAN in RSPAN session 2, to
configure Gigabit Ethernet source port 2 as the destination interface, and to enable ingress forwarding
on the interface with VLAN 6 as the default receiving VLAN.
Switch(config)# monitor session 2 source remote vlan 901
Switch(config)# monitor session 2 destination interface gigabitethernet1/0/2 ingress
vlan 6
Switch(config)# end
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 no monitor session {session_number | all | Remove any existing SPAN configuration for the session.
local | remote}
For session_number, the range is from 1 to 66.
Specify all to remove all SPAN sessions, local to remove all local
sessions, or remote to remove all remote SPAN sessions.
Step 3 monitor session session_number source Specify the characteristics of the source port (monitored port) and
interface interface-id SPAN session.
For session_number, the range is from 1 to 66.
For interface-id, specify the source port to monitor. The interface
specified must already be configured as a trunk port.
Step 4 monitor session session_number filter vlan Limit the SPAN source traffic to specific VLANs.
vlan-id [, | -]
For session_number, enter the session number specified in step 3.
For vlan-id, the range is 1 to 4094.
(Optional) Use a comma (,) to specify a series of VLANs or use a
hyphen (-) to specify a range of VLANs. Enter a space before and after
the comma; enter a space before and after the hyphen.
Step 5 monitor session session_number Specify the RSPAN session and the destination remote VLAN
destination remote vlan vlan-id (RSPAN VLAN).
For session_number, enter the session number specified in step 3.
For vlan-id, specify the RSPAN VLAN to carry the monitored traffic
to the destination port.
Step 6 end Return to privileged EXEC mode.
Step 7 show monitor [session session_number] Verify the configuration.
show running-config
Step 8 copy running-config startup-config (Optional) Save the configuration in the configuration file.
To monitor all VLANs on the trunk port, use the no monitor session session_number filter vlan global
configuration command.
This example shows how to remove any existing configuration on RSPAN session 2, configure RSPAN
session 2 to monitor traffic received on a trunk port, and send traffic for only VLANs 1 through 5 and 9
to destination RSPAN VLAN 902.
Switch(config)# no monitor session 2
Switch(config)# monitor session 2 source interface gigabitethernet1/0/2 rx
Switch(config)# monitor session 2 filter vlan 1 - 5, 9
Switch(config)# monitor session 2 destination remote vlan 902
Switch(config)# end
This chapter describes how to configure Remote Network Monitoring (RMON) on the
Catalyst 3750 Metro switch.
RMON is a standard monitoring specification that defines a set of statistics and functions that can be
exchanged between RMON-compliant console systems and network probes. RMON provides you with
comprehensive network-fault diagnosis, planning, and performance-tuning information.
Note For complete syntax and usage information for the commands used in this chapter, see the “System
Management Commands” section in the Cisco IOS Configuration Fundamentals Command Reference,
Release 12.2.
Understanding RMON
RMON is an Internet Engineering Task Force (IETF) standard monitoring specification that allows
various network agents and console systems to exchange network monitoring data. You can use the
RMON feature with the Simple Network Management Protocol (SNMP) agent in the switch to monitor
all the traffic flowing among switches on all connected LAN segments.
RMON history
and statistic
collection enabled.
101233
Workstations Workstations
Configuring RMON
These sections describe how to configure RMON on your switch:
• Default RMON Configuration, page 29-3
• Configuring RMON Alarms and Events, page 29-3 (required)
• Collecting Group History Statistics on an Interface, page 29-5 (optional)
• Collecting Group Ethernet Statistics on an Interface, page 29-6 (optional)
Beginning in privileged EXEC mode, follow these steps to enable RMON alarms and events. This
procedure is required.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 rmon alarm number variable interval {absolute | delta} Set an alarm on a MIB object.
rising-threshold value [event-number]
• For number, specify the alarm number. The
falling-threshold value [event-number]
range is 1 to 65535.
[owner string]
• For variable, specify the MIB object to monitor.
• For interval, specify the time in seconds the
alarm monitors the MIB variable. The range is
1 to 4294967295 seconds.
• Specify the absolute keyword to test each MIB
variable directly. Specify the delta keyword to
test the change between samples of a MIB
variable.
• For value, specify a number at which the alarm
is triggered and one for when the alarm is reset.
The range for the rising threshold and falling
threshold values is -2147483648 to
2147483647.
• (Optional) For event-number, specify the event
number to trigger when the rising or falling
threshold exceeds its limit.
• (Optional) For owner string, specify the owner
of the alarm.
Step 3 rmon event number [description string] [log] [owner string] Add an event in the RMON event table that is
[trap community] associated with an RMON event number.
• For number, assign an event number. The range
is 1 to 65535.
• (Optional) For description string, specify a
description of the event.
• (Optional) Use the log keyword to generate an
RMON log entry when the event is triggered.
• (Optional) For owner string, specify the owner
of this event.
• (Optional) For trap community, enter the
SNMP community string used for this trap.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration
file.
To disable an alarm, use the no rmon alarm number global configuration command on each alarm you
configured. You cannot disable at once all the alarms that you configured. To disable an event, use the
no rmon event number global configuration command. To learn more about alarms and events and how
they interact with each other, see RFC 1757.
You can set an alarm on any MIB object. The following example configures RMON alarm number 10 by
using the rmon alarm command. The alarm monitors the MIB variable ifEntry.20.1 once every 20
seconds until the alarm is disabled and checks the change in the variable’s rise or fall. If the ifEntry.20.1
value shows a MIB counter increase of 15 or more, such as from 100000 to 100015, the alarm is
triggered. The alarm in turn triggers event number 1, which is configured with the rmon event
command. Possible events can include a log entry or an SNMP trap. If the ifEntry.20.1 value changes
by 0, the alarm is reset and can be triggered again.
Switch(config)# rmon alarm 10 ifEntry.20.1 20 delta rising-threshold 15 1
falling-threshold 0 owner jjohnson
The following example creates RMON event number 1 by using the rmon event command. The event is
defined as High ifOutErrors and generates a log entry when the event is triggered by the alarm. The user
jjones owns the row that is created in the event table by this command. This example also generates an
SNMP trap when the event is triggered.
Switch(config)# rmon event 1 log trap eventtrap description "High ifOutErrors" owner
jjones
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface on which to collect history, and enter
interface configuration mode.
Step 3 rmon collection history index Enable history collection for the specified number of buckets and
[buckets bucket-number] [interval seconds] time period.
[owner ownername]
• For index, identify the RMON group of statistics The range
is 1 to 65535.
• (Optional) For buckets bucket-number, specify the
maximum number of buckets desired for the RMON
collection history group of statistics. The range is 1 to
65535. The default is 50 buckets.
• (Optional) For interval seconds, specify the number of
seconds in each polling cycle. The range is 1 to 3600. The
default is 1800 seconds.
• (Optional) For owner ownername, enter the name of the
owner of the RMON group of statistics.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 show rmon history Display the contents of the switch history table.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable history collection, use the no rmon collection history index interface configuration
command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface on which to collect statistics, and enter
interface configuration mode.
Step 3 rmon collection stats index [owner ownername] Enable RMON statistic collection on the interface.
• For index, specify the RMON group of statistics. The range
is from 1 to 65535.
• (Optional) For owner ownername, enter the name of the
owner of the RMON group of statistics.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 show rmon statistics Display the contents of the switch statistics table.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable the collection of group Ethernet statistics, use the no rmon collection stats index interface
configuration command.
This example shows how to collect RMON statistics for the owner root:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# rmon collection stats 2 owner root
Command Purpose
show rmon Displays general RMON statistics.
show rmon alarms Displays the RMON alarm table.
show rmon events Displays the RMON event table.
show rmon history Displays the RMON history table.
show rmon statistics Displays the RMON statistics table.
For information about the fields in these displays, see the “System Management Commands” section in
the Cisco IOS Configuration Fundamentals Command Reference, Release 12.2.
This chapter describes how to configure system message logging on the Catalyst 3750 Metro switch.
Note For complete syntax and usage information for the commands used in this chapter, see the Cisco IOS
Configuration Fundamentals Command Reference, Release 12.2.
Caution Logging messages to the console at a high rate can cause high CPU utilization and adversely affect how
the switch operates.
When the logging process is disabled, messages are sent only to the console. The messages are sent as
they are generated, so message and debug output are interspersed with prompts or output from other
commands. Messages are displayed on the console after the process that generated them has finished.
You can set the severity level of the messages to control the type of messages displayed on the consoles
and each of the destinations. You can time-stamp log messages or set the syslog source address to
enhance real-time debugging and management. For information on possible messages, see the system
message guide for this release.
You can access logged system messages by using the switch command-line interface (CLI) or by saving
them to a properly configured syslog server. The switch software saves syslog messages in an internal
buffer on the switch. If the switch fails, the log is lost unless you had saved it to flash memory.
You can remotely monitor system messages by viewing the logs on a syslog server or by accessing the
switch through Telnet or through the console port.
Element Description
seq no: Stamps log messages with a sequence number only if the service sequence-numbers global
configuration command is configured.
For more information, see the “Enabling and Disabling Sequence Numbers in Log Messages”
section on page 30-7.
timestamp formats: Date and time of the message or event. This information appears only if the service timestamps
log [datetime | log] global configuration command is configured.
mm/dd hh:mm:ss
For more information, see the “Enabling and Disabling Timestamps on Log Messages” section on
or
page 30-7.
hh:mm:ss (short uptime)
or
d h (long uptime)
Element Description
facility The facility to which the message refers (for example, SNMP, SYS, and so forth). For a list of
supported facilities, see Table 30-4 on page 30-13.
severity Single-digit code from 0 to 7 that is the severity of the message. For a description of the severity
levels, see Table 30-3 on page 30-9.
MNEMONIC Text string that uniquely describes the message.
description Text string containing detailed information about the event being reported.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 no logging on Disable message logging.
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify your entries.
or
show logging
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
Disabling the logging process can slow down the switch because a process must wait until the messages
are written to the console before continuing. When the logging process is disabled, messages are
displayed on the console as soon as they are produced, often appearing in the middle of command output.
The logging synchronous global configuration command also affects the display of messages to the
console. When this command is enabled, messages appear only after you press Return. For more
information, see the “Synchronizing Log Messages” section on page 30-5.
To re-enable message logging after it has been disabled, use the logging on global configuration
command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 logging buffered [size] Log messages to an internal buffer on the switch. The default buffer size
is 4096. The range is 4096 to 2147483647 bytes.
If the switch, the log file is lost unless you previously saved it to flash
memory. See Step 4.
Note Do not make the buffer size too large because the switch could run
out of memory for other tasks. Use the show memory privileged
EXEC command to view the free processor memory on the switch.
However, this value is the maximum available, and the buffer size
should not be set to this amount.
Command Purpose
Step 3 logging host Log messages to a UNIX syslog server host.
For host, specify the name or IP address of the host to be used as the
syslog server.
To build a list of syslog servers that receive logging messages, enter this
command more than once.
For complete syslog server configuration steps, see the “Configuring
UNIX Syslog Servers” section on page 30-11.
Step 4 logging file flash:filename Store log messages in a file in flash memory on the switch.
[max-file-size [min-file-size]]
• For filename, enter the log message filename.
[severity-level-number | type]
• (Optional) For max-file-size, specify the maximum logging file size.
The range is 4096 to 2147483647. The default is 4096 bytes.
• (Optional) For min-file-size, specify the minimum logging file size.
The range is 1024 to 2147483647. The default is 2048 bytes.
• (Optional) For severity-level-number | type, specify either the logging
severity level or the logging type. The severity range is 0 to 7. For a
list of logging type keywords, see Table 30-3 on page 30-9. By
default, the log file receives debugging messages and numerically
lower levels.
Step 5 end Return to privileged EXEC mode.
Step 6 terminal monitor Log messages to a nonconsole terminal during the current session.
Terminal parameter-setting commands are set locally and do not remain
in effect after the session has ended. You must perform this step for each
session to see the debugging messages.
Step 7 show running-config Verify your entries.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
The logging buffered global configuration command copies logging messages to an internal buffer. The
buffer is circular, so newer messages overwrite older messages after the buffer is full. To display the
messages that are logged in the buffer, use the show logging privileged EXEC command. The first
message displayed is the oldest message in the buffer. To clear the contents of the buffer, use the clear
logging privileged EXEC command.
To disable logging to the console, use the no logging console global configuration command. To disable
logging to a file, use the no logging file [severity-level-number | type] global configuration command.
When synchronous logging of unsolicited messages and debug command output is enabled, unsolicited
device output appears on the console or printed after solicited device output appears or printed.
Unsolicited messages and debug command output appears on the console after the prompt for user input
is returned. Therefore, unsolicited messages and debug command output are not interspersed with
solicited device output and prompts. After the unsolicited messages are displayed, the console again
displays the user prompt.
Beginning in privileged EXEC mode, follow these steps to configure synchronous logging. This
procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 line [console | vty] line-number Specify the line to be configured for synchronous logging of
[ending-line-number] messages.
• Use the console keyword for configurations that occur through
the switch console port.
• Use the line vty line-number command to specify which vty
lines are to have synchronous logging enabled. You use a vty
connection for configurations that occur through a Telnet
session. The range of line numbers is from 0 to 15.
You can change the setting of all 16 vty lines at once by entering:
line vty 0 15
Or you can change the setting of the single vty line being used for
your current connection. For example, to change the setting for vty
line 2, enter:
line vty 2
When you enter this command, the mode changes to line
configuration.
Step 3 logging synchronous [level [severity-level | Enable synchronous logging of messages.
all] | limit number-of-buffers]
• (Optional) For level severity-level, specify the message severity
level. Messages with a severity level equal to or higher than this
value are printed asynchronously. Low numbers mean greater
severity and high numbers mean lesser severity. The default is 2.
• (Optional) Specifying level all means that all messages are
printed asynchronously regardless of the severity level.
• (Optional) For limit number-of-buffers, specify the number of
buffers to be queued for the terminal after which new messages
are dropped. The range is 0 to 2147483647. The default is 20.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable synchronization of unsolicited messages and debug output, use the no logging synchronous
[level severity-level | all] [limit number-of-buffers] line configuration command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 service timestamps log uptime Enable log time-stamps.
or The first command enables time-stamps on log messages,
showing the time since the system was rebooted.
service timestamps log datetime [msec] [localtime]
[show-timezone] The second command enables time-stamps on log messages.
Depending on the options selected, the timestamp can
include the date, time in milliseconds relative to the local
time zone, and the time zone name.
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable time-stamps for both debug and log messages, use the no service timestamps global
configuration command.
This example shows part of a logging display with the service timestamps log datetime global
configuration command enabled:
*Mar 1 18:46:11: %SYS-5-CONFIG_I: Configured from console by vty2 (10.34.195.36)
This example shows part of a logging display with the service timestamps log uptime global
configuration command enabled:
00:00:46: %LINK-3-UPDOWN: Interface Port-channel1, changed state to up
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 service sequence-numbers Enable sequence numbers.
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable sequence numbers, use the no service sequence-numbers global configuration command.
This example shows part of a logging display with sequence numbers enabled:
000019: %SYS-5-CONFIG_I: Configured from console by vty2 (10.34.195.36)
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 logging console level Limit messages logged to the console.
By default, the console receives debugging messages and numerically
lower levels (see Table 30-3 on page 30-9).
Step 3 logging monitor level Limit messages logged to the terminal lines.
By default, the terminal receives debugging messages and numerically
lower levels (see Table 30-3 on page 30-9).
Step 4 logging trap level Limit messages logged to the syslog servers.
By default, syslog servers receive informational messages and
numerically lower levels (see Table 30-3 on page 30-9).
For complete syslog server configuration steps, see the “Configuring
UNIX Syslog Servers” section on page 30-11.
Step 5 end Return to privileged EXEC mode.
Step 6 show running-config Verify your entries.
or
show logging
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
Note Specifying a level causes messages at that level and numerically lower levels to be displayed at the
destination.
To disable logging to the console, use the no logging console global configuration command. To disable
logging to a terminal other than the console, use the no logging monitor global configuration command.
To disable logging to syslog servers, use the no logging trap global configuration command.
Table 30-3 describes the level keywords. It also lists the corresponding UNIX syslog definitions from
the most severe level to the least severe level.
Beginning in privileged EXEC mode, follow these steps to change the level and history table size
defaults. This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 1
logging history level Change the default level of syslog messages stored in the history file and
sent to the SNMP server.
See Table 30-3 on page 30-9 for a list of level keywords.
By default, warnings, errors, critical, alerts, and emergencies messages
are sent.
Step 3 logging history size number Specify the number of syslog messages that can be stored in the history
table.
The default is to store one message. The range is 0 to 500 messages.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
1. Table 30-3 lists the level keywords and severity level. For SNMP usage, the severity level values increase by 1. For example, emergencies
equal 1, not 0, and critical equals 3, not 2.
When the history table is full (it contains the maximum number of message entries specified with the
logging history size global configuration command), the oldest message entry is deleted from the table
to allow the new message entry to be stored.
To return the logging of syslog messages to the default level, use the no logging history global
configuration command. To return the number of messages in the history table to the default value, use
the no logging history size global configuration command.
Beginning in privileged EXEC mode, follow these steps to enable configuration logging:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 archive Enter archive configuration mode.
Step 3 log config Enter configuration-change logger configuration mode.
Step 4 logging enable Enable configuration change logging.
Step 5 logging size entries (Optional) Configure the number of entries retained in the configuration
log. The range is from 1 to 1000. The default is 100.
Note When the configuration log is full, the oldest log entry is removed
each time a new entry is entered.
Step 6 end Return to privileged EXEC mode.
Step 7 show archive log config Verify your entries by viewing the configuration log.
This example shows how to enable the configuration-change logger and to set the number of entries in
the log to 500.
Switch(config)# archive
Switch(config-archive)# log config
Switch(config-archive-log-cfg)# logging enable
Switch(config-archive-log-cfg)# logging size 500
Switch(config-archive-log-cfg)# end
Note Some recent versions of UNIX syslog daemons no longer accept by default syslog packets from the
network. If this is the case with your system, use the UNIX man syslogd command to decide what
options must be added to or removed from the syslog command line to enable logging of remote syslog
messages.
The local7 keyword specifies the logging facility to be used; see Table 30-4 on page 30-13 for
information on the facilities. The debug keyword specifies the syslog level; see Table 30-3 on page 30-9
for information on the severity levels. The syslog daemon sends messages at this level or at a more severe
level to the file specified in the next field. The file must already exist, and the syslog daemon must have
permission to write to it.
Step 2 Create the log file by entering these commands at the UNIX shell prompt:
$ touch /var/log/cisco.log
$ chmod 666 /var/log/cisco.log
Step 3 Make sure the syslog daemon reads the new changes:
$ kill -HUP `cat /etc/syslog.pid`
For more information, see the man syslog.conf and man syslogd commands on your UNIX system.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 logging host Log messages to a UNIX syslog server host by entering its IP address.
To build a list of syslog servers that receive logging messages, enter this
command more than once.
Step 3 logging trap level Limit messages logged to the syslog servers.
Be default, syslog servers receive informational messages and lower. See
Table 30-3 on page 30-9 for level keywords.
Step 4 logging facility facility-type Configure the syslog facility. See Table 30-4 on page 30-13 for
facility-type keywords.
The default is local7.
Step 5 end Return to privileged EXEC mode.
Command Purpose
Step 6 show running-config Verify your entries.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove a syslog server, use the no logging host global configuration command, and specify the syslog
server IP address. To disable logging to syslog servers, enter the no logging trap global configuration
command.
Table 30-4 lists the UNIX system facilities supported by the software. For more information about these
facilities, consult the operator’s manual for your UNIX operating system.
This chapter describes how to configure the Simple Network Management Protocol (SNMP) on the
Catalyst 3750 Metro switch.
Note For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release and the Cisco IOS Network Management Command Reference, Release 12.4
from the Cisco.com page at this URL:
http://www.cisco.com/en/US/docs/ios/netmgmt/command/reference/nm_book.html
For commands for MIB bulk statistics data collection and process MIB configuration, see the Cisco IOS
Commands Master List, Release 12.4, at this URL:
http://www.cisco.com/en/US/products/ps6350/products_product_indices_list.html
Understanding SNMP
SNMP is an application-layer protocol that provides a message format for communication between
managers and agents. The SNMP system consists of an SNMP manager, an SNMP agent, and a MIB.
The SNMP manager can be part of a network management system (NMS) such as CiscoWorks. The agent
and MIB reside on the switch. To configure SNMP on the switch, you define the relationship between
the manager and the agent.
The SNMP agent contains MIB variables whose values the SNMP manager can request or change. A
manager can get a value from an agent or store a value into the agent. The agent gathers data from the
MIB, the repository for information about device parameters and network data. The agent can also
respond to a manager’s requests to get or set data.
An agent can send unsolicited traps to the manager. Traps are messages alerting the SNMP manager to
a condition on the network. Traps can mean improper user authentication, restarts, link status (up or
down), MAC address tracking, closing of a Transmission Control Protocol (TCP) connection, loss of
connection to a neighbor, or other significant events.
Although the switch does not support the Cisco Data Collection MIB, starting with Cisco IOS Release
12.2(37)SE, you can use the command-line interface to periodically transfer selected MIB data to
specified NMS stations. Starting with this release, you can also configure a Cisco Process MIB CPU
threshold table.
This section includes information about these topics:
• SNMP Versions, page 31-2
• SNMP Manager Functions, page 31-4
• SNMP Agent Functions, page 31-4
• SNMP Community Strings, page 31-4
• Using SNMP to Access MIB Variables, page 31-5
• SNMP Notifications, page 31-5
• SNMP ifIndex MIB Object Values, page 31-6
• MIB Data Collection and Transfer, page 31-6
SNMP Versions
This software release supports these SNMP versions:
• SNMPv1—The Simple Network Management Protocol, a Full Internet Standard, defined in
RFC 1157.
• SNMPv2C replaces the Party-based Administrative and Security Framework of SNMPv2Classic
with the community-string-based Administrative Framework of SNMPv2C while retaining the bulk
retrieval and improved error handling of SNMPv2Classic. It has these features:
– SNMPv2—Version 2 of the Simple Network Management Protocol, a Draft Internet Standard,
defined in RFCs 1902 through 1907.
– SNMPv2C—The community-string-based Administrative Framework for SNMPv2, an
Experimental Internet Protocol defined in RFC 1901.
• SNMPv3—Version 3 of the SNMP is an interoperable standards-based protocol defined in RFCs
2273 to 2275. SNMPv3 provides secure access to devices by authenticating and encrypting packets
over the network and includes these security features:
– Message integrity—ensuring that a packet was not tampered with in transit
– Authentication—determining that the message is from a valid source
– Encryption—mixing the contents of a package to prevent it from being read by an unauthorized
source.
Note To select encryption, enter the priv keyword. This keyword is available only when the
crypto (encrypted) software image is installed.
Both SNMPv1 and SNMPv2C use a community-based form of security. The community of managers
able to access the agent’s MIB is defined by an IP address access control list and password.
SNMPv2C includes a bulk retrieval mechanism and more detailed error message reporting to
management stations. The bulk retrieval mechanism retrieves tables and large quantities of information,
minimizing the number of round-trips required. The SNMPv2C improved error-handling includes
expanded error codes that distinguish different kinds of error conditions; these conditions are reported
through a single error code in SNMPv1. Error return codes in SNMPv2C report the error type.
SNMPv3 provides for both security models and security levels. A security model is an authentication
strategy set up for a user and the group within which the user resides. A security level is the permitted
level of security within a security model. A combination of the security level and the security model
determine which security mechanism is used when handling an SNMP packet. Available security models
are SNMPv1, SNMPv2C, and SNMPv3.
Table 31-1 identifies the characteristics of the different combinations of security models and levels.
You must configure the SNMP agent to use the SNMP version supported by the management station.
Because an agent can communicate with multiple managers, you can configure the software to support
communications using SNMPv1, and SNMPv2C, and SNMPv3 protocols.
Operation Description
get-request Retrieves a value from a specific variable.
get-next-request Retrieves a value from a variable within a table.1
get-bulk-request2 Retrieves large blocks of data, such as multiple rows in a table, that would
otherwise require the transmission of many small blocks of data.
get-response Replies to a get-request, get-next-request, and set-request sent by an NMS.
set-request Stores a value in a specific variable.
trap An unsolicited message sent by an SNMP agent to an SNMP manager when some
event has occurred.
1. With this operation, an SNMP manager does not need to know the exact variable name. A sequential search is performed to
find the needed variable from within a table.
2. The get-bulk command only works with SNMPv2 or later.
43581
Get-response, traps MIB
SNMP Manager SNMP Agent
SNMP Notifications
SNMP allows the switch to send notifications to SNMP managers when particular events occur. SNMP
notifications can be sent as traps or inform requests. In command syntax, unless there is an option in the
command to select either traps or informs, the keyword traps refers to either traps or informs, or both.
Use the snmp-server host command to specify whether to send SNMP notifications as traps or informs.
Traps are unreliable because the receiver does not send an acknowledgment when it receives a trap, and
the sender cannot determine if the trap was received. When an SNMP manager receives an inform
request, it acknowledges the message with an SNMP response protocol data unit (PDU). If the sender
does not receive a response, the inform request can be sent again. Because they can be re-sent, informs
are more likely than traps to reach their intended destination.
The characteristics that make informs more reliable than traps also consume more resources in the switch
and in the network. Unlike a trap, which is discarded as soon as it is sent, an inform request is held in
memory until a response is received or the request times out. Traps are sent only once, but an inform
might be re-sent or retried several times. The retries increase traffic and contribute to a higher overhead
on the network. Therefore, traps and informs require a trade-off between reliability and resources. If it
is important that the SNMP manager receive every notification, use inform requests. If traffic on the
network or memory in the switch is a concern and notification is not required, use traps.
Note The switch might not use sequential values within a range.
Configuring SNMP
This section describes how to configure SNMP on your switch. It contains this configuration
information:
• Default SNMP Configuration, page 31-7
• SNMP Configuration Guidelines, page 31-7
• Disabling the SNMP Agent, page 31-8
• Configuring Community Strings, page 31-8
• Configuring SNMP Groups and Users, page 31-10
• Configuring SNMP Notifications, page 31-12
• Setting the Agent Contact and Location Information, page 31-17
• Limiting TFTP Servers Used Through SNMP, page 31-18
• Configuring MIB Data Collection and Transfer, page 31-19
• Configuring the Cisco Process MIB CPU Threshold Table, page 31-22
• SNMP Examples, page 31-23
• To configure a remote user, specify the IP address or port number for the remote SNMP agent of the
device where the user resides.
• Before you configure remote users for a particular agent, configure the SNMP engine ID, using the
snmp-server engineID global configuration with the remote option. The remote agent's SNMP
engine ID and user password are used to compute the authentication and privacy digests. If you do
not configure the remote engine ID first, the configuration command fails.
• When configuring SNMP informs, you need to configure the SNMP engine ID for the remote agent
in the SNMP database before you can send proxy requests or informs to it.
• If a local user is not associated with a remote host, the switch does not send informs for the auth
(authNoPriv) and the priv (authPriv) authentication levels.
• Changing the value of the SNMP engine ID has important side effects. A user's password (entered
on the command line) is converted to an MD5 or SHA security digest based on the password and the
local engine ID. The command-line password is then destroyed, as required by RFC 2274. Because
of this deletion, if the value of the engine ID changes, the security digests of SNMPv3 users become
invalid, and you need to reconfigure SNMP users by using the snmp-server user username global
configuration command. Similar restrictions require the reconfiguration of community strings when
the engine ID changes.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 no snmp-server Disable the SNMP agent operation.
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
The no snmp-server global configuration command disables all running versions (Version 1,
Version 2C, and Version 3) on the device. No specific IOS command exists to enable SNMP. The first
snmp-server global configuration command that you enter enables all versions of SNMP.
Beginning in privileged EXEC mode, follow these steps to configure a community string on the switch:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 snmp-server community string [view Configure the community string.
view-name] [ro | rw] [access-list-number]
Note The @ symbol is used for delimiting the context
information. Avoid using the @ symbol as part of the
SNMP community string when configuring this command.
Note To disable access for an SNMP community, set the community string for that community to the null
string (do not enter a value for the community string).
To remove a specific community string, use the no snmp-server community string global configuration
command.
This example shows how to assign the string comaccess to SNMP, to allow read-only access, and to
specify that IP access list 4 can use the community string to gain access to the switch SNMP agent:
Switch(config)# snmp-server community comaccess ro 4
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 snmp-server engineID {local Configure a name for either the local or remote copy of SNMP.
engineid-string | remote ip-address
• The engineid-string is a 24-character ID string with the name of
[udp-port port-number] engineid-string}
the copy of SNMP. You need not specify the entire 24-character
engine ID if it has trailing zeros. Specify only the portion of the
engine ID up to the point where only zeros remain in the value.
For example, to configure an engine ID of
123400000000000000000000, you can enter this: snmp-server
engineID local 1234
• If you select remote, specify the ip-address of the device that
contains the remote copy of SNMP and the optional UDP port on
the remote device. The default is 162.
Command Purpose
Step 3 snmp-server group groupname {v1 | v2c | Configure a new SNMP group on the remote device.
v3 [auth | noauth | priv]} [read readview]
• For groupname, specify the name of the group.
[write writeview] [notify notifyview]
[access access-list] • Specify a security model:
– v1 is the least secure of the possible security models.
– v2c is the second least secure model. It allows transmission
of informs and integers twice the normal width.
– v3, the most secure, requires you to select an authentication
level:
auth—Enables the Message Digest 5 (MD5) and the Secure
Hash Algorithm (SHA) packet authentication.
noauth—The noAuthNoPriv security level. This is the
default if no keyword is specified.
priv—Enables Data Encryption Standard (DES) packet
encryption (also called privacy).
Note The priv keyword is available only when the crypto software
image is installed.
Command Purpose
Step 4 snmp-server user username groupname Add a new user for an SNMP group.
{remote host [udp-port port]} {v1 [access
• The username is the name of the user on the host that connects to
access-list] | v2c [access access-list] | v3
the agent.
[encrypted] [access access-list] [auth
{md5 | sha} auth-password]} [priv {des | • The groupname is the name of the group to which the user is
3des | aes {128 | 192 | 256}} associated.
priv-password] • Enter remote to specify a remote SNMP entity to which the user
belongs and the hostname or IP address of that entity with the
optional UDP port number. The default is 162.
• Enter the SNMP version number (v1, v2c, or v3). If you enter v3,
you have these additional options:
– encrypted specifies that the password appears in encrypted
format. This keyword is available only when the v3 keyword
is specified.
– auth is an authentication level setting session that can be
either the HMAC-MD5-96 (md5) or the HMAC-SHA-96
(sha) authentication level and requires a password string
auth-password (not to exceed 64 characters).
• If you enter v3 and the switch is running the cryptographic
software image, you can also configure a private (priv)
encryption algorithm and password string priv-password (not to
exceed 64 characters).
– priv specifies the User-based Security Model (USM).
– des specifies the use of the 56-bit DES algorithm.
– 3des specifies the use of the 168-bit DES algorithm.
– aes specifies the use of the DES algorithm. You must select
either 128-bit, 192-bit, or 256-bit encryption.
• (Optional) Enter access access-list with a string (not to exceed 64
characters) that is the name of the access list.
Step 5 end Return to privileged EXEC mode.
Step 6 show running-config Verify your entries.
Note To display SNMPv3 information about auth | noauth | priv
mode configuration, you must enter the show snmp user
privileged command.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
Note Many commands use the word traps in the command syntax. Unless there is an option in the command
to select either traps or informs, the keyword traps refers to traps, informs, or both. Use the snmp-server
host command to specify whether to send SNMP notifications as traps or informs.
Table 31-5 describes some of the supported switch traps (notification types). You can enable any or all
of these traps and configure a trap manager to receive them.
Note Although visible in the command-line interface (CLI) online help, the fru-ctrl keyword is not supported.
Note Though visible in the command-line help string, the fru-ctrl and flash insertion and removal keywords
are not supported. The snmp-server enable informs command is not supported. To enable the sending
of SNMP inform notifications, use the snmp-server enable traps command combined with the
snmp-server host host-addr informs command.
You can use the snmp-server host global configuration command to a specific host to receive the
notification types listed in Table 31-5.
Beginning in privileged EXEC mode, follow these steps to configure the switch to send traps or informs
to a host:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 snmp-server engineID remote Specify the engine ID for the remote host.
ip-address engineid-string
Step 3 snmp-server user username Configure an SNMP user to be associated with the remote host created in
groupname remote host [udp-port Step 2.
port] {v1 | v2c | v3 [auth {md5 | sha}
Note You cannot configure a remote user for an address without first
auth-password]} [encrypted] [access
configuring the engine ID for the remote host. If you try to
access-list]
configure the user before configuring the remote engine ID, you
receive an error message, and the command is not executed.
Command Purpose
Step 4 snmp-server host host-addr Specify the recipient of an SNMP trap operation.
[traps | informs] [version {1 | 2c | 3
• For host-addr, specify the name or Internet address of the host (the
[auth | noauth | priv]}]
targeted recipient).
community-string [udp-port port]
[notification-type] • (Optional) Enter traps (the default) to send SNMP traps to the host.
• (Optional) Enter informs to send SNMP informs to the host.
• (Optional) Specify the SNMP version (1, 2c, or 3). SNMPv1 does
not support informs.
• (Optional) For Version 3, select authentication level auth, noauth, or
priv.
Note The priv keyword is available only when the crypto software
image is installed.
• (Optional) For udp-port port, enter the remote device UDP port.
• (Optional) For notification-type, use the keywords listed in
Table 31-5 on page 31-14. If no type is specified, all notifications are
sent.
Step 5 snmp-server enable traps Enable the switch to send traps or informs and specify the type of
notification-types notifications to be sent. For a list of notification types, see Table 31-5 on
page 31-14, or enter this: snmp-server enable traps ?
To enable multiple types of traps, you must enter a separate snmp-server
enable traps command for each trap type.
Note When you configure a trap by using the notification type
port-security, configure the port security trap first, and then
configure the port security trap rate:
Command Purpose
Step 10 show running-config Verify your entries.
Note To display SNMPv3 information about auth | noauth | priv mode
configuration, you must enter the show snmp user privileged
command.
Step 11 copy running-config startup-config (Optional) Save your entries in the configuration file.
The snmp-server host command specifies which hosts receive the notifications. The snmp-server
enable trap command globally enables the mechanism for the specified notification (for traps and
informs). To enable a host to receive an inform, you must configure an snmp-server host informs
command for the host and globally enable informs by using the snmp-server enable traps command.
To remove the specified host from receiving traps, use the no snmp-server host host global
configuration command. The no snmp-server host command with no keywords disables traps, but not
informs, to the host. To disable informs, use the no snmp-server host informs global configuration
command. To disable a specific trap type, use the no snmp-server enable traps notification-types global
configuration command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 snmp-server contact text Set the system contact string.
For example:
snmp-server contact Dial System Operator at beeper 21555.
Step 3 snmp-server location text Set the system location string.
For example:
snmp-server location Building 3/Room 222
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 snmp-server tftp-server-list Limit TFTP servers used for configuration file copies through
access-list-number SNMP to the servers in the access list.
For access-list-number, enter an IP standard access list numbered
from 1 to 99 and 1300 to 1999.
Step 3 access-list access-list-number {deny | Create a standard access list, repeating the command as many times
permit} source [source-wildcard] as necessary.
• For access-list-number, enter the access list number specified
in Step 2.
• The deny keyword denies access if the conditions are matched.
The permit keyword permits access if the conditions are
matched.
• For source, enter the IP address of the TFTP servers that can
access the switch.
• (Optional) For source-wildcard, enter the wildcard bits, in
dotted decimal notation, to be applied to the source. Place ones
in the bit positions that you want to ignore.
Recall that the access list is always terminated by an implicit deny
statement for everything.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 process cpu threshold type {total | process Set the CPU threshold notification types and values:
| interrupt} rising percentage interval
• total—set the notification type to total CPU utilization.
seconds [falling fall-percentage interval
seconds] • process—set the notification type to CPU process utilization.
• interrupt—set the notification type to CPU interrupt utilization.
• rising percentage—the percentage (1 to 100) of CPU resources
that, when exceeded for the configured interval, sends a CPU
threshold notification.
• interval seconds—the duration of the CPU threshold violation in
seconds (5 to 86400) that, when met, sends a CPU threshold
notification.
• falling fall-percentage—the percentage (1 to 100) of CPU
resources that, when usage falls below this level for the
configured interval, sends a CPU threshold notification.
This value must be equal to or less than the rising percentage
value. If not specified, the falling fall-percentage value is the
same as the rising percentage value.
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 snmp-server mib bulkstat object-list Define an SNMP bulk-statistics object list, and enter bulk-statistics
list-name object-list configuration mode.
Command Purpose
Step 3 add {object-name | oid} Add a MIB object to the bulk-statistics object list.
• For object-name, enter the name of the MIB object to add to the
list. You can enter only object names from the Interfaces MIB
or the Cisco Committed Access Rate MIB.
• For oid, enter the Object ID of the MIB object to add to the list.
All the objects in an object-list must be in the same MIB index, but
the objects need not belong to the same MIB table. Repeat the
command until all objects to be monitored are added.
Step 4 exit Return to global configuration mode.
Step 5 snmp-server mib bulkstat schema Name the SNMP bulk statistics schema, and enter bulk-statistics
schema-name schema configuration mode.
Step 6 object-list list-name Specify the bulk-statistics object list to be included in this schema.
Specify only one object list per schema. If multiple object-list
commands are entered, the most recent command overwrites the
previous command.
Step 7 instance {exact | wild} {interface Specify the instance information for objects in this schema. Enter
interface-id | oid oid} only one instance command per schema. If multiple instance
commands are entered, the most recent command overwrites the
previous command.
• Enter exact when the specified instance appended to the object
list is the complete OID.
• Enter wild when all subindices of the specified OID belong to
the schema.
• Enter an interface interface-id to specify an interface ID
instead of an instance OID.
• Enter oid oid to specify an instance OID for the schema.
Step 8 poll interval interval Set the time interval in minutes for collection of data from the
object instances specified in the schema. The range is from 1 to
20000 minutes; the default is 5 minutes.
Step 9 end Return to privileged EXEC mode.
Step 10 copy running-config startup-config (Optional) Save your entries in the configuration file.
Beginning in privileged EXEC mode, follow these steps to configure bulk-statistics transfer options:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 snmp-server mib bulkstat transfer Identify the transfer configuration with a name, and enter
transfer-id bulk-statistics transfer configuration mode.
Step 3 buffer-size bytes (Optional) Specify the maximum size for the bulk-statistics data
file in bytes. The range is from 1024 to 2147483647 bytes; the
default is 2048 bytes.
Step 4 format {bulkBinary | bulkASCII | (Optional) Specify the format of the bulk-statistics data file. The
schemaASCII} default is schemaASCII.
Step 5 schema schema-name Specify the bulk-statistics schema to be transferred. Repeat this
command for as many schemas as desired. You can associate
multiple schemas with a transfer configuration.
Step 6 transfer-interval minutes (Optional) Specify the length of time that the system should collect
MIB data before attempting the transfer operation. The valid range
is from 1 to 2147483647 minutes; the default is 30 minutes. The
transfer interval is the same as the collection interval.
Step 7 url primary URL Specify the NMS (host) that the bulk-statistics file should be
transferred to and the protocol to use for transfer (FTP, RCP, or
TFTP). You also can optionally enter the url secondary command
to specify a backup transfer destination.
Step 8 retry number (Optional) Specify the number of transmission retries. The range is
from 1 to 100; the default is 0 (no retries).
Step 9 retain minutes (Optional) Specify how long the bulk-statistics file should be kept
in system memory. The valid range is 0 to 20000 minutes; the
default is 0 (the file is deleted immediately after a successful
transfer).
Step 10 enable Begin the bulk-statistics data collection and transfer process for
this configuration. You must enter this command to start periodic
collection and transfer.
Step 11 end Return to privileged EXEC mode.
Step 12 show mib bulk transfer Verify your entries.
Step 13 copy running-config startup-config (Optional) Save your entries in the configuration file.
Enter the no enable bulk statistics transfer configuration mode command to stop the collection process.
Enter the enable command again to restart the operation. Every time you restart the process with the
enable command, data is collected in a new bulk-statistics file.
This is an example of configuring the bulk-statistics transfer and enabling the collection process:
Switch(config)# snmp mib bulkstat transfer testtransfer
Switch(config-bulk-tr)# format schemaASCII
Switch(config-bulk-tr)# buffer-size 2147483647
Switch(config-bulk-tr)# schema testschema1
Switch(config-bulk-tr)# schema testschema2
Switch(config-bulk-tr)# transfer-interval 1
Switch(config-bulk-tr)# url primary tftp://host/folder/bulkstat1
Switch(config-bulk-tr)# retain 20
Switch(config-bulk-tr)# retry 2
Switch(config-bulk-tr)# enable
Switch(config-bulk-tr)# exit
Enter the show snmp mib bulk transfer privileged EXEC command to view the configured transfer
operation.
Note For commands for configuring the Cisco Process MIB CPU threshold table, see the Cisco IOS
Commands Master List, Release 12.4, at this URL at this URL:
http://www.cisco.com/en/US/products/ps6350/products_product_indices_list.html
Beginning in privileged EXEC mode, follow these steps to configure a CPU threshold table:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 process cpu statistics limit Set the process entry limit and the size of the history table for CPU
entry-percentage number [size seconds] utilization statistics.
• For entry-percentage number, enter the percentage (1 to 100)
of CPU utilization that a process must use to become part of the
history table.
• (Optional) For size seconds, set the duration of time in seconds
for which CPU statistics are stored in the history table. The
range is from 5 to 86400 seconds; the default is 600.
Command Purpose
Step 3 process cpu threshold type {total | process | Set CPU threshold notification types and values.
interrupt} rising percentage interval
• Set the threshold type to total CPU utilization, CPU process
seconds [falling percentage interval
utilization, or CPU interrupt utilization.
seconds]
• For rising percentage, enter the percentage (1 to 100) of CPU
resources that triggers a CPU threshold notification when
exceeded.
• For interval seconds, enter the duration of the CPU threshold
violation in seconds (5 to 86400) that must be met to trigger a
CPU threshold notification. The default is 5 seconds.
• (Optional) Set a falling percentage interval seconds that,
when usage falls below this level for the configured interval,
triggers a CPU threshold notification. The percentage must be
equal to or less than the rising percentage. The default is for the
falling percentage to be the same value as the rising
percentage.
Step 4 end Return to privileged EXEC mode.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
SNMP Examples
This example shows how to enable all versions of SNMP. The configuration permits any SNMP manager
to access all objects with read-only permissions using the community string public. This configuration
does not cause the switch to send any traps.
Switch(config)# snmp-server community public
This example shows how to permit any SNMP manager to access all objects with read-only permission
using the community string public. The switch also sends VTP traps to the hosts 192.180.1.111 and
192.180.1.33 using SNMPv1 and to the host 192.180.1.27 using SNMPv2C. The community string
public is sent with the traps.
Switch(config)# snmp-server community public
Switch(config)# snmp-server enable traps vtp
Switch(config)# snmp-server host 192.180.1.27 version 2c public
Switch(config)# snmp-server host 192.180.1.111 version 1 public
Switch(config)# snmp-server host 192.180.1.33 public
This example shows how to allow read-only access for all objects to members of access list 4 that use
the comaccess community string. No other SNMP managers have access to any objects. SNMP
Authentication Failure traps are sent by SNMPv2C to the host cisco.com using the community string
public.
Switch(config)# snmp-server community comaccess ro 4
Switch(config)# snmp-server enable traps snmp authentication
Switch(config)# snmp-server host cisco.com version 2c public
This example shows how to send Entity MIB traps to the host cisco.com. The community string is
restricted. The first line enables the switch to send Entity MIB traps in addition to any traps previously
enabled. The second line specifies the destination of these traps and overwrites any previous
snmp-server host commands for the host cisco.com.
Switch(config)# snmp-server enable traps entity
This example shows how to enable the switch to send all traps to the host myhost.cisco.com using the
community string public:
Switch(config)# snmp-server enable traps
Switch(config)# snmp-server host myhost.cisco.com public
This example shows how to associate a user with a remote host and to send auth (authNoPriv)
authentication-level informs when the user enters global configuration mode:
Switch(config)# snmp-server engineID remote 192.180.1.27 00000063000100a1c0b4011b
Switch(config)# snmp-server group authgroup v3 auth
Switch(config)# snmp-server user authuser authgroup remote 192.180.1.27 v3 auth md5
mypassword
Switch(config)# snmp-server user authuser authgroup v3 auth md5 mypassword
Switch(config)# snmp-server host 192.180.1.27 informs version 3 auth authuser config
Switch(config)# snmp-server enable traps
Switch(config)# snmp-server inform retries 0
This example shows how to enable SNMP notifications to provide information on the transfer status of
the periodic MIB data collection and transfer mechanism (bulk statistics):
Switch(config)# snmp-server enable traps bulkstat
Switch(config)# snmp-server host 192.180.1.27 informs version 2 public bulkstat
This example shows how to enable SNMP notifications to provide information on the Cisco Process MIB
CPU threshold table:
Switch(config)# snmp-server enable traps cpu threshold
Switch(config)# snmp-server host 192.180.1.27 informs version 2 public cpu
Embedded Event Manager (EEM) is a distributed and customized approach to event detection and
recovery within a Cisco IOS device. EEM offers the ability to monitor events and take informational,
corrective, or any other EEM action when the monitored events occur or when a threshold is reached.
An EEM policy defines an event and the actions to be taken when that event occurs.
This chapter tells how to use EEM and how to configure it on the Catalyst 3750 Metro switch. For
complete syntax and usage information for the commands used in this chapter, see the switch command
reference for this release and the Cisco IOS Network Management Command Reference. For the
complete EEM document set, see these documents in the Cisco IOS Network Management Configuration
Guide:
• Embedded Event Manager Overview
http://www.cisco.com/en/US/docs/ios/netmgmt/configuration/guide/nm_eem_overview.html
• Writing Embedded Event Manager Policies Using the Cisco IOS CLI
http://www.cisco.com/en/US/docs/ios/netmgmt/configuration/guide/nm_eem_policy_cli.html
• Writing Embedded Event Manager Policies Using Tcl
http://www.cisco.com/en/US/docs/ios/netmgmt/configuration/guide/nm_eem_policy_tcl.html
This chapter includes these sections:
• Understanding Embedded Event Manager, page 32-1
• Configuring Embedded Event Manager, page 32-6
• Displaying Embedded Event Manager Information, page 32-7
Figure 32-1 shows the relationship between the EEM server, the core event publishers (event detectors),
and the event subscribers (policies). The event publishers screen events and when there is a match on an
event specification that is provided by the event subscriber. Event detectors notify the EEM server when
an event occurs. The EEM policies then implement recovery based on the current state of the system and
the actions specified in the policy for the given event.
127574
EEM APPLET EEM SCRIPT
See the EEM Configuration for Cisco Integrated Services Router Platforms Guide for examples of EEM
deployment.
These sections contain this conceptual information:
• Event Detectors, page 32-3
• Embedded Event Manager Actions, page 32-4
• Embedded Event Manager Policies, page 32-4
• Embedded Event Manager Environment Variables, page 32-5
• EEM 3.2, page 32-5
Event Detectors
EEM software programs known as event detectors determine when an EEM event occurs. Event
detectors are separate systems that provide an interface between the agent being monitored, for example
SNMP, and the EEM polices where an action can be implemented.
EEM allows these event detectors:
• Application-specific event detector—Allows any EEM policy to publish an event.
• IOS CLI event detector—Generates policies based on the commands entered through the CLI.
• Generic Online Diagnostics (GOLD) event detector—Publishes an event when a GOLD failure
event is detected on a specified card and subcard.
• Counter event detector—Publishes an event when a named counter crosses a specified threshold.
• Interface counter event detector—Publishes an event when a generic Cisco IOS interface counter for
a specified interface crosses a defined threshold. A threshold can be specified as an absolute value
or an incremental value.For example, if the incremental value is set to 50, an event would be
published when the interface counter increases by 50.
This detector also publishes an event about an interface based on the rate of change for the entry and
exit values.
• None event detector—Publishes an event when the event manager run CLI command executes an
EEM policy. EEM schedules and runs policies on the basis on an event specification within the
policy itself. An EEM policy must be manually identified and registered before the event manager
run command executes.
• Online insertion and removal event detector—Publishes an event when a hardware insertion or
removal (OIR) event occurs.
• Remote procedure call (RPC) event detector—Invokes EEM policies from outside the switch over
an encrypted connecting using Secure Shell (SSH) and uses Simple Object Access Protocol (SOAP)
data encoding for exchanging XML-based messages. It also runs EEM policies and then gets the
output in a SOAP XML-formatted reply.
• SNMP event detector—Allows a standard SNMP MIB object to be monitored and an event to be
generated when
– The object matches specified values or crosses specified thresholds.
– The SNMP delta value, the difference between the monitored Object Identifier (OID) value at
the beginning the period and the actual OID value when the event is published, matches a
specified value.
• SNMP notification event detector—Intercepts SNMP trap and inform messages received by the
switch. The event is generated when an incoming message matches a specified value or crosses a
defined threshold.
• Syslog event detector—Allows for screening syslog messages for a regular expression pattern
match. The selected messages can be further qualified, requiring that a specific number of
occurrences be logged within a specified time. A match on a specified event criteria triggers a
configured policy action.
• Timer event detector—Publishes events for
– An absolute-time-of-day timer publishes an event when a specified absolute date and time
occurs.
– A countdown timer publishes an event when a timer counts down to zero.
– A watchdog timer publishes an event when a timer counts down to zero. The timer automatically
resets itself to its initial value and starts to count down again.
– A CRON timer publishes an event by using a UNIX standard CRON specification to define
when the event is to be published. A CRON timer never publishes events more than once per
minute.
• Watchdog event detector (IOSWDSysMon)—Publishes an event when one of these events occurs:
– CPU utilization for a Cisco IOS process crosses a threshold.
– Memory utilization for a Cisco IOS process crosses a threshold.
Two events can be monitored at the same time, and the event publishing criteria requires that one or
both events cross their specified thresholds.
EEM 3.2
EEM 3.2 is supported in Cisco IOS Release 12.2(52)SE and later and introduces these event detectors:
• Neighbor Discovery—Neighbor Discovery event detector provides the ability to publish a policy to
respond to automatic neighbor detection when:
– a Cisco Discovery Protocol (CDP) cache entry is added, deleted, or updated.
– a Link Layer Discovery Protocol (LLDP) cache entry is added, deleted or updated.
– an interface link status changes.
– an interface line status changes.
• Identity—Identity event detector generates an event when AAA authorization and authentication is
successful, when failure occurs, or after normal user traffic on the port is allowed to flow.
• Mac-Address-Table—Mac-Address-Table event detector generates an event when a MAC address is
learned in the MAC address table.
Note The Mac-Address-Table event detector is supported only on switch platforms and can be used
only on Layer 2 interfaces where MAC addresses are learned. Layer 3 interfaces do not learn
addresses, and routers do not usually support the MAC address-table infrastructure needed to
notify EEM of a learned MAC address.
EEM 3.2 also introduces CLI commands to support the applets to work with the new event detectors.
For further details about EEM 3.2 features, see the Embedded Event Manager 3.2 document.
http://www.cisco.com/en/US/docs/ios/netmgmt/configuration/guide/nm_eem_3.2.html
Note Only one event applet command is allowed in an EEM applet. Multiple action applet commands are
permitted. If you do not specify the no event and no action commands, the applet is removed when you
exit configuration mode.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 event manager applet applet-name Register the applet with EEM and enter applet configuration mode.
Step 3 event snmp oid oid-value get-type Specify the event criteria that causes the EEM applet to run.
{exact | next} entry-op {gt | ge | eq | ne (Optional) Exit criteria. If exit criteria are not specified, event monitoring
| lt | le} entry-val entry-val [exit-comb is re-enabled immediately.
{or |and}] [exit-op {gt | ge | eq | ne | lt
| le}] [exit-val exit-val] [exit-time
exit-time-val] poll-interval poll-int-val
Step 4 action label syslog [priority Specify the action when an EEM applet is triggered. Repeat this action to
priority-level] msg msg-text add other CLI commands to the applet.
• (Optional) The priority keyword specifies the priority level of the
syslog messages. If selected, you need to define the priority-level
argument.
• For msg-text, the argument can be character text, an environment
variable, or a combination of the two.
Step 5 end Exit applet configuration mode and return to privileged EXEC mode.
This example shows the output for EEM when one of the fields specified by an SNMP object ID crosses
a defined threshold:
Switch(config-applet)# event snmp oid 1.3.6.1.4.1.9.9.48.1.1.1.6.1 get-type exact entry-op
lt entry-val 5120000 poll-interval 10
These examples show actions that are taken in response to an EEM event:
Switch(config-applet)# action 1.0 syslog priority critical msg "Memory exhausted; current
available memory is $_snmp_oid_val bytes"
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 1 show event manager (Optional) The show event manager environment command displays the name and
environment [all | value of the EEM environment variables.
variable-name]
(Optional) The all keyword displays the EEM environment variables.
(Optional) The variable-name argument displays information about the specified
environment variable.
Step 2 configure terminal Enter global configuration mode.
Step 3 event manager environment Configure the value of the specified EEM environment variable. Repeat this step for
variable-name string all the required environment variables.
Step 4 event manager policy Register the EEM policy to be run when the specified event defined within the
policy-file-name [type policy occurs.
system] [trap]
Step 5 exit Exit global configuration mode and return to privileged EXEC mode.
This example shows the sample output for the show event manager environment command:
Switch# show event manager environment all
No. Name Value
1 _cron_entry 0-59/2 0-23/1 * * 0-6
2 _show_cmd show ver
3 _syslog_pattern .*UPDOWN.*Ethernet1/0.*
4 _config_cmd1 interface Ethernet1/0
5 _config_cmd2 no shut
This example shows a CRON timer environment variable, which is assigned by the software, to be set to
every second minute, every hour of every day:
Switch (config)# event manager environment_cron_entry 0-59/2 0-23/1 * * 0-6
This example shows the sample EEM policy named tm_cli_cmd.tcl registered as a system
policy. The system policies are part of the Cisco IOS image. User-defined TCL scripts must
first be copied to flash memory.
This chapter describes how to configure network security on the Catalyst 3750 Metro switch by using
access control lists (ACLs), which are also referred to in commands and tables as access lists.
Note For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release, see the “Configuring IP Services” section in the “IP Addressing and Services”
chapter of the Cisco IOS IP Configuration Guide, Release 12.2, and to these software configuration guides
and command references:
• Cisco IOS IP Command Reference, Volume 1 of 3: Addressing and Services, Release 12.2
• Cisco IOS IP Command Reference, Volume 2 of 3: Routing Protocols, Release 12.2
• Cisco IOS IP Command Reference, Volume 3 of 3: Multicast, Release 12.2
This chapter consists of these sections:
• Understanding ACLs, page 33-1
• Configuring IP ACLs, page 33-6
• Creating Named MAC Extended ACLs, page 33-27
• Configuring VLAN Maps, page 33-29
• Using VLAN Maps with Router ACLs, page 33-38
• Displaying ACL Configuration, page 33-42
Understanding ACLs
Packet filtering can help limit network traffic and restrict network use by certain users or devices. ACLs
can filter traffic as it passes through a router or switch and permit or deny packets crossing specified
interfaces or VLANs. An ACL is a sequential collection of permit and deny conditions that apply to
packets. When a packet is received on an interface, the switch compares the fields in the packet against
any applied ACLs to verify that the packet has the required permissions to be forwarded, based on the
criteria specified in the access lists. It tests packets against the conditions in an access list one by one.
The first match determines whether the switch accepts or rejects the packets. Because the switch stops
testing conditions after the first match, the order of conditions in the list is critical. If no conditions
match, the switch rejects the packets. If there are no restrictions, the switch forwards the packet;
otherwise, the switch drops the packet. The switch can access-control all packets it switches, including
packets bridged within a VLAN.
You configure access lists on a router or Layer 3 switch to provide basic security for your network. If
you do not configure ACLs, all packets passing through the switch could be allowed onto all parts of the
network. You can use ACLs to control which hosts can access different parts of a network or to decide
which types of traffic are forwarded or blocked at router interfaces. For example, you can allow e-mail
traffic to be forwarded but not Telnet traffic. ACLs can be configured to block inbound traffic, outbound
traffic, or both.
An ACL contains an ordered list of access control entries (ACEs). Each ACE specifies permit or deny
and a set of conditions the packet must satisfy in order to match the ACE. The meaning of permit or deny
depends on the context in which the ACL is used.
The switch supports IP ACLs and Ethernet (MAC) ACLs:
• IP ACLs filter IP traffic, including TCP, User Datagram Protocol (UDP), Internet Group
Management Protocol (IGMP), and Internet Control Message Protocol (ICMP).
• Ethernet ACLs filter non-IPv4 traffic.
This switch also supports quality of service (QoS) classification ACLs. For more information, see the
“Ingress Classification Based on QoS ACLs” section on page 34-11.
This section includes information on these topics:
• Supported ACLs, page 33-2
• Handling Fragmented and Unfragmented Traffic, page 33-5
Supported ACLs
The switch supports three applications of ACLs to filter traffic:
• Router ACLs access-control routed traffic between VLANs and are applied to Layer 3 interfaces.
• Port ACLs access-control traffic entering a Layer 2 interface. The switch does not support port ACLs
in the outbound direction. You can apply only one IP access list and one MAC access list to a Layer
2 interface.
• VLAN ACLs or VLAN maps access-control all packets (bridged and routed). You can use VLAN
maps to filter traffic between devices in the same VLAN. VLAN maps are configured to provide
access-control based on Layer 3 addresses for IP. Unsupported protocols are access-controlled
through MAC addresses using Ethernet ACEs. After a VLAN map is applied to a VLAN, all packets
(routed or bridged) entering the VLAN are checked against the VLAN map. Packets can either enter
the VLAN through a switch port or through a routed port after being routed.
You can use router ACLs, input port ACLs, and VLAN maps on the same switch. However, a port ACL
takes precedence over a router ACL or VLAN map.
• When both an input port ACL and a VLAN map are applied, incoming packets received on ports
with a port ACL applied are filtered by the port ACL. Other packets are filtered by the VLAN map
• When an input router ACL and input port ACL exist in an switch virtual interface (SVI), incoming
packets received on ports to which a port ACL is applied are filtered by the port ACL. Incoming
routed IP packets received on other ports are filtered by the router ACL. Other packets are not
filtered.
• When an output router ACL and input port ACL exist in an SVI, incoming packets received on the
ports to which a port ACL is applied are filtered by the port ACL. Outgoing routed IP packets are
filtered by the router ACL. Other packets are not filtered.
• When a VLAN map, input router ACL, and input port ACL exist in an SVI, incoming packets
received on the ports to which a port ACL is applied are only filtered by the port ACL. Incoming
routed IP packets received on other ports are filtered by both the VLAN map and the router ACL.
Other packets are filtered only by the VLAN map.
• When a VLAN map, output router ACL, and input port ACL exist in an SVI, incoming packets
received on the ports to which a port ACL is applied are only filtered by the port ACL. Outgoing
routed IP packets are filtered by both the VLAN map and the router ACL. Other packets are filtered
only by the VLAN map.
Router ACLs
You can apply router ACLs on SVIs, which are Layer 3 interfaces to VLANs; on physical Layer 3
interfaces; and on Layer 3 EtherChannel interfaces. You apply router ACLs on interfaces for specific
directions (inbound or outbound). You can apply one router ACL in each direction on an interface.
One ACL can be used with multiple features for a given interface, and one feature can use multiple
ACLs. When a single router ACL is used by multiple features, it is examined multiple times.
• Standard IP access lists use source addresses for matching operations.
• Extended IP access lists use source and destination addresses and optional protocol type information
for matching operations.
The switch examines ACLs associated with features configured on a given interface and a direction. As
packets enter the switch on an interface, ACLs associated with all inbound features configured on that
interface are examined. After packets are routed and before they are forwarded to the next hop, all ACLs
associated with outbound features configured on the egress interface are examined.
ACLs permit or deny packet forwarding based on how the packet matches the entries in the ACL, and
can be used to control access to a network or to part of a network. In Figure 33-1, ACLs applied at the
switch input allow Host A to access the Human Resources network, but prevent Host B from accessing
the same network.
Host A
Host B
Port ACLs
Port ACLs are ACLs that are applied to Layer 2 interfaces on a switch. Port ACLs are supported only on
physical interfaces and not on EtherChannel interfaces. Port ACLs are applied only on interfaces for
inbound traffic.
These access lists are supported on Layer 2 interfaces:
• Standard IP access lists using source addresses
• Extended IP access lists using source and destination addresses and optional protocol type
information
• MAC extended access lists using source and destination MAC addresses and optional protocol type
information
As with router ACLs, the switch examines ACLs associated with features configured on a given interface
and permits or denies packet forwarding based on how the packet matches the entries in the ACL. ACLs
can only be applied to Layer 2 interfaces in the inbound direction. In the example in Figure 33-1, if all
workstations were in the same VLAN, ACLs applied at the Layer 2 input would allow Host A to access
the Human Resources network, but prevent Host B from accessing the same network.
When you apply a port ACL to a trunk port, the ACL filters traffic on all VLANs present on the trunk
port. When you apply a port ACL to a port with voice VLAN, the ACL filters traffic on both data and
voice VLANs.
With port ACLs, you can filter IPv4 traffic by using IP access lists and non-IPv4 traffic by using MAC
addresses. You can filter both IP and non-IP traffic on the same Layer 2 interface by applying both an IP
access list and a MAC access list to the interface.
Note You cannot apply more than one IP access list and one MAC access list to a Layer 2 interface. If an IP
access list or MAC access list is already configured on a Layer 2 interface and you apply a new IP access
list or MAC access list to the interface, the new ACL replaces the previously configured one.
VLAN Maps
VLAN ACLs or VLAN maps can access-control all traffic. You can apply VLAN maps to all packets
that are routed into or out of a VLAN or are bridged within a VLAN. VLAN maps are used for security
packet filtering. VLAN maps are not defined by direction (input or output).
You can configure VLAN maps to match Layer 3 addresses for IP traffic. All non-IPv4 protocols are
access-controlled through MAC addresses and Ethertype using MAC VLAN maps. (IP traffic is not
access controlled by MAC VLAN maps.) You can enforce VLAN maps only on packets going through
the switch; you cannot enforce VLAN maps on traffic between hosts on a hub or on another switch
connected to this switch.
With VLAN maps, forwarding of packets is permitted or denied, based on the action specified in the
map. Figure 33-2 illustrates how a VLAN map is applied to deny a specific type of traffic from Host A
in VLAN 10 from being forwarded. You can apply only one VLAN map to a VLAN.w
101353
of traffic from Host A
= Packet
Note In the first and second ACEs in the examples, the eq keyword after the destination address means to test
for the TCP-destination-port well-known numbers equaling Simple Mail Transfer Protocol (SMTP) and
Telnet, respectively.
• Packet A is a TCP packet from host 10.2.2.2., port 65000, going to host 10.1.1.1 on the SMTP port.
If this packet is fragmented, the first fragment matches the first ACE (a permit) as if it were a
complete packet because all Layer 4 information is present. The remaining fragments also match the
first ACE, even though they do not contain the SMTP port information, because the first ACE only
checks Layer 3 information when applied to fragments. The information in this example is that the
packet is TCP and that the destination is 10.1.1.1.
• Packet B is from host 10.2.2.2, port 65001, going to host 10.1.1.2 on the Telnet port. If this packet
is fragmented, the first fragment matches the second ACE (a deny) because all Layer 3 and Layer 4
information is present. The remaining fragments in the packet do not match the second ACE because
they are missing Layer 4 information. Instead, they match the third ACE (a permit).
Because the first fragment was denied, host 10.1.1.2 cannot reassemble a complete packet, so packet
B is effectively denied. However, the later fragments that are permitted will consume bandwidth on
the network and resources of host 10.1.1.2 as it tries to reassemble the packet.
• Fragmented packet C is from host 10.2.2.2, port 65001, going to host 10.1.1.3, port ftp. If this packet
is fragmented, the first fragment matches the fourth ACE (a deny). All other fragments also match
the fourth ACE because that ACE does not check any Layer 4 information and because Layer 3
information in all fragments shows that they are being sent to host 10.1.1.3, and the earlier permit
ACEs were checking different hosts.
Configuring IP ACLs
Configuring IP ACLs on the switch is the same as configuring IP ACLs on other Cisco switches and
routers. The process is briefly described here. For more detailed information on configuring ACLs, see
the “Configuring IP Services” section in the “IP Addressing and Services” chapter of the Cisco IOS IP
Configuration Guide, Release 12.2. For detailed information about the commands, see these documents:
• Cisco IOS IP Command Reference, Volume 1 of 3: Addressing and Services, Release 12.2
• Cisco IOS IP Command Reference, Volume 2 of 3: Routing Protocols, Release 12.2
• Cisco IOS IP Command Reference, Volume 3 of 3: Multicast, Release 12.2
The switch does not support these IOS router ACL-related features:
• Non-IPv4 protocol ACLs (see Table 33-1 on page 33-7) or bridge-group ACLs
• IP accounting
• Inbound and outbound rate limiting (except with QoS ACLs)
• Reflexive ACLs or dynamic ACLs
• ACL logging for port ACLs and VLAN maps
These are the steps to use IP ACLs on the switch:
Step 1 Create an ACL by specifying an access list number or name and access conditions.
Step 2 Apply the ACL to interfaces or terminal lines. You can also apply standard and extended IP ACLs to
VLAN maps.
Note In addition to numbered standard and extended ACLs, you can also create standard and extended named
IP ACLs using the supported numbers. That is, the name of a standard IP ACL can be 1 to 99; the name
of an extended IP ACL can be 100 to 199. The advantage of using named ACLs instead of numbered lists
is that you can delete individual entries from a named list.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 access-list access-list-number {deny | permit} Define a standard IP access list by using a source address and
source [source-wildcard] [log] 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:
• The 32-bit quantity in dotted-decimal format.
• The keyword any as an abbreviation for source and
source-wildcard of 0.0.0.0 255.255.255.255. You do not need
to enter a source-wildcard.
• The keyword host as an abbreviation for source and
source-wildcard of source 0.0.0.0.
(Optional) The source-wildcard applies wildcard bits to the
source.
(Optional) Enter log to cause an informational logging message
about the packet that matches the entry to be sent to the console.
Step 3 end Return to privileged EXEC mode.
Step 4 show access-lists [number | name] Show the access list configuration.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no access-list access-list-number global configuration command to delete the entire ACL. You
cannot delete individual ACEs from numbered access lists.
Note When creating an ACL, remember that, by default, the end of the ACL contains an implicit deny
statement for all packets that it did not find a match for before reaching the end. With standard access
lists, if you omit the mask from an associated IP host address ACL specification, 0.0.0.0 is assumed to
be the mask.
This example shows how to create a standard ACL to deny access to IP host 171.69.198.102, permit
access to any others, and display the results.
Switch (config)# access-list 2 deny host 171.69.198.102
Switch (config)# access-list 2 permit any
Switch(config)# end
Switch# show access-lists
Standard IP access list 2
10 deny 171.69.198.102
20 permit any
The switch always rewrites the order of standard access lists so that entries with host matches and entries
with matches having a don’t care mask of 0.0.0.0 are moved to the top of the list, above any entries with
non-zero don’t care masks. Therefore, in show command output and in the configuration file, the ACEs
do not necessarily appear in the order in which they were entered.
The switch software can provide logging messages about packets permitted or denied by a standard IP
access list. That is, any packet that matches the ACL causes an informational logging message about the
packet to be sent to the console. The level of messages logged to the console is controlled by the logging
console commands controlling the syslog messages.
Note Because routing is done in hardware and logging is done in software, if a large number of packets match
a permit or deny ACE containing a log keyword, the software might not be able to match the hardware
processing rate, and not all packets will be logged.
The first packet that triggers the ACL causes a logging message right away, and subsequent packets are
collected over 5-minute intervals before they are displayed or logged. The logging message includes the
access list number, whether the packet was permitted or denied, the source IP address of the packet, and
the number of packets from that source permitted or denied in the prior 5-minute interval.
After creating a numbered standard IP ACL, you can apply it to terminal lines (see the “Applying an IP
ACL to a Terminal Line” section on page 33-18), to interfaces (see the “Applying an IP ACL to an
Interface” section on page 33-19), or to VLANs (see the “Configuring VLAN Maps” section on
page 33-29).
(igrp), any Interior Protocol (ip), IP in IP tunneling (ipinip), KA9Q NOS-compatible IP over IP
tunneling (nos), Open Shortest Path First routing (ospf), Payload Compression Protocol (pcp), Protocol
Independent Multicast (pim), Transmission Control Protocol (tcp), or User Datagram Protocol (udp).
Note ICMP echo-reply cannot be filtered. All other ICMP codes or types can be filtered.
For more details on the specific keywords for each protocol, see these software configuration guides and
command references:
• Cisco IOS IP Command Reference, Volume 1 of 3: Addressing and Services, Release 12.2
• Cisco IOS IP Command Reference, Volume 2 of 3: Routing Protocols, Release 12.2
• Cisco IOS IP Command Reference, Volume 3 of 3: Multicast, Release 12.2
Note The switch does not support dynamic or reflexive access lists. It also does not support filtering based on
the type of service (ToS) minimize-monetary-cost bit.
Supported parameters can be grouped into these categories: TCP, UDP, ICMP, IGMP, or other IP.
Beginning in privileged EXEC mode, follow these steps to create an extended ACL:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2a access-list access-list-number Define an extended IP access list and the access conditions.
{deny | permit} protocol The access-list-number is a decimal number from 100 to 199 or 2000 to 2699.
source source-wildcard
destination destination-wildcard Enter deny or permit to specify whether to deny or permit the packet if
[precedence precedence] [tos tos] conditions are matched.
[fragments] [log] [log-input] For protocol, enter the name or number of an IP protocol: ahp, eigrp, esp, gre,
[time-range time-range-name] icmp, igmp, igrp, ip, ipinip, nos, ospf, pcp, pim, tcp, or udp, or an integer in
[dscp dscp] the range 0 to 255 representing an IP protocol number. To match any Internet
Note If you enter a dscp value, protocol (including ICMP, TCP, and UDP) use the keyword ip.
you cannot enter tos or Note This step includes options for most IP protocols. For additional specific
precedence. You can enter parameters for TCP, UDP, ICMP, and IGMP, see steps 2b through 2e.
both a tos and a
precedence value with no The source is the number of the network or host from which the packet is sent.
dscp.
The source-wildcard applies wildcard bits to the source.
The destination is the network or host number to which the packet is sent.
The destination-wildcard applies wildcard bits to the destination.
Source, source-wildcard, destination, and destination-wildcard can be specified
as:
• The 32-bit quantity in dotted-decimal format.
• The keyword any for 0.0.0.0 255.255.255.255 (any host).
• The keyword host for a single host 0.0.0.0.
The other keywords are optional and have these meanings:
• precedence—Enter to match packets with a precedence level specified as a
number from 0 to 7 or by name: routine (0), priority (1), immediate (2),
flash (3), flash-override (4), critical (5), internet (6), network (7).
• fragments—Enter to check non-initial fragments.
• tos—Enter to match by type of service level, specified by a number from 0
to 15 or a name: normal (0), max-reliability (2), max-throughput (4),
min-delay (8).
• log—Enter to create an informational logging message to be sent to the
console about the packet that matches the entry or log-input to include the
input interface in the log entry.
• time-range—For an explanation of this keyword, see the “Using Time
Ranges with ACLs” section on page 33-16.
• dscp—Enter to match packets with the DSCP value specified by a number
from 0 to 63, or use the question mark (?) to see a list of available values.
Command Purpose
or access-list access-list-number In access-list configuration mode, define an extended IP access list using an
{deny | permit} protocol any any abbreviation for a source and source wildcard of 0.0.0.0 255.255.255.255 and
[precedence precedence] [tos tos] an abbreviation for a destination and destination wildcard of 0.0.0.0
[fragments] [log] [log-input] 255.255.255.255.
[time-range time-range-name] You can use the any keyword in place of source and destination address and
[dscp dscp] wildcard.
or access-list access-list-number Define an extended IP access list using an abbreviation for a source and source
{deny | permit} protocol wildcard of source 0.0.0.0 and an abbreviation for a destination and destination
host source host destination wildcard of destination 0.0.0.0.
[precedence precedence] [tos tos] You can use the host keyword in place of source and destination wildcard
[fragments] [log] [log-input] or mask.
[time-range time-range-name]
[dscp dscp]
Step access-list access-list-number (Optional) Define an extended TCP access list and the access conditions.
2b {deny | permit} tcp source Enter tcp for Transmission Control Protocol.
source-wildcard [operator port]
destination destination-wildcard The parameters are the same as those described in Step 2a with these exceptions:
[operator port] [established] (Optional) Enter an operator and port to compare source (if positioned after
[precedence precedence] [tos tos] source source-wildcard) or destination (if positioned after destination
[fragments] [log] [log-input] destination-wildcard) port. Possible operators include eq (equal), gt (greater
[time-range time-range-name] than), lt (less than), neq (not equal), and range (inclusive range). Operators
[dscp dscp] [flag] require a port number (range requires two port numbers separated by a space).
Enter the port number as a decimal number (from 0 to 65535) or the name of a
TCP port. To see TCP port names, use the ? or see the “Configuring IP Services”
section in the “IP Addressing and Services” chapter of the Cisco IOS IP
Configuration Guide, Release 12.2. Use only TCP port numbers or names when
filtering TCP.
The additional optional keywords have these meanings:
• established—Enter to match an established connection. This has the same
function as matching on the ack or rst flag.
• flag—Enter one of these flags to match by the specified TCP header bits:
ack (acknowledge), fin (finish), psh (push), rst (reset), syn (synchronize),
or urg (urgent).
Step access-list access-list-number (Optional) Define an extended UDP access list and the access conditions.
2c {deny | permit} udp Enter udp for the User Datagram Protocol.
source source-wildcard [operator
port] destination The UDP parameters are the same as those described for TCP except that
destination-wildcard [operator [operator [port]] port number or name must be a UDP port number or name, and
port] [precedence precedence] the flag and established parameters are not valid for UDP.
[tos tos] [fragments] [log]
[log-input] [time-range
time-range-name] [dscp dscp]
Command Purpose
Step access-list access-list-number (Optional) Define an extended ICMP access list and the access conditions.
2d {deny | permit} icmp source Enter icmp for Internet Control Message Protocol.
source-wildcard destination
destination-wildcard [icmp-type | The ICMP parameters are the same as those described for most IP protocols in
[[icmp-type icmp-code] | Step 2a, with the addition of the ICMP message type and code parameters.
[icmp-message]] [precedence These optional keywords have these meanings:
precedence] [tos tos] [fragments] • icmp-type—Enter to filter by ICMP message type, a number from 0 to 255.
[log] [log-input] [time-range
time-range-name] [dscp dscp] • icmp-code—Enter to filter ICMP packets that are filtered by ICMP message
type by the ICMP message code, a number from 0 to 255.
• icmp-message—Enter to filter ICMP packets by ICMP message type name
or ICMP message type and code name. To see a list of ICMP message type
names and ICMP message type and code names, use the ? or see the
“Configuring IP Services” section of the Cisco IOS IP Configuration Guide,
Release 12.2.
Step access-list access-list-number (Optional) Define an extended IGMP access list and the access conditions.
2e {deny | permit} igmp source
Enter igmp for Internet Group Management Protocol.
source-wildcard destination
destination-wildcard [igmp-type] The IGMP parameters are the same as those described for most IP protocols in
[precedence precedence] [tos tos] Step 2a, with the addition of this optional parameter.
[fragments] [log] [log-input] igmp-type—To match IGMP message type, enter a number from 0 to 15, or enter
[time-range time-range-name] the message name (dvmrp, host-query, host-report, pim, or trace).
[dscp dscp]
Step 3 end Return to privileged EXEC mode.
Step 4 show access-lists [number | name] Verify the access list configuration.
Step 5 copy running-config (Optional) Save your entries in the configuration file.
startup-config
Use the no access-list access-list-number global configuration command to delete the entire access list.
You cannot delete individual ACEs from numbered access lists.
This example shows how to create and display an extended access list to deny Telnet access from any
host in network 171.69.198.0 to any host in network 172.20.52.0 and permit any others. (The eq keyword
after the destination address means to test for the TCP destination port number equaling Telnet.)
Switch(config)# access-list 102 deny tcp 171.69.198.0 0.0.0.255 172.20.52.0 0.0.0.255 eq
telnet
Switch(config)# access-list 102 permit tcp any any
Switch(config)# end
Switch# show access-lists
Extended IP access list 102
10 deny tcp 171.69.198.0 0.0.0.255 172.20.52.0 0.0.0.255 eq telnet
20 permit tcp any any
After an ACL is created, any additions (possibly entered from the terminal) are placed at the end of the
list. You cannot selectively add or remove access list entries from a numbered access list.
Note When you are creating an ACL, remember that, by default, the end of the access list contains an implicit
deny statement for all packets if it did not find a match before reaching the end.
After creating a numbered extended ACL, you can apply it to terminal lines (see the “Applying an IP
ACL to a Terminal Line” section on page 33-18), to interfaces (see the “Applying an IP ACL to an
Interface” section on page 33-19), or to VLANs (see the “Configuring VLAN Maps” section on
page 33-29).
Note The name you give to a standard or extended ACL can also be a number in the supported range of access
list numbers. That is, the name of a standard IP ACL can be 1 to 99; the name of an extended IP ACL
can be 100 to 199. The advantage of using named ACLs instead of numbered lists is that you can delete
individual entries from a named list.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip access-list standard name Define a standard IP access list using a name, and enter access-list
configuration mode.
Note The name can be a number from 1 to 99.
Command Purpose
Step 3 deny {source [source-wildcard] | host source | In access-list configuration mode, specify one or more conditions
any} [log] denied or permitted to determine if the packet is forwarded or
dropped.
or
permit {source [source-wildcard] | host source • host source—A source and source wildcard of source 0.0.0.0.
| any} [log] • any—A source and source wildcard of 0.0.0.0
255.255.255.255.
Step 4 end Return to privileged EXEC mode.
Step 5 show access-lists [number | name] Show the access list configuration.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove a named standard ACL, use the no ip access-list standard name global configuration
command.
Beginning in privileged EXEC mode, follow these steps to create an extended ACL using names:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip access-list extended name Define an extended IP access list using a name and enter
access-list configuration mode.
Note The name can be a number from 100 to 199.
Step 3 {deny | permit} protocol {source In access-list configuration mode, specify the conditions allowed
[source-wildcard] | host source | any} or denied. Use the log keyword to get access list logging messages,
{destination [destination-wildcard] | host including violations.
destination | any} [precedence precedence] See the “Creating a Numbered Extended ACL” section on
[tos tos] [established] [log] [time-range page 33-9 for definitions of protocols and other keywords.
time-range-name]
• host source—A source and source wildcard of source 0.0.0.0.
• host destination—A destination and destination wildcard of
destination 0.0.0.0.
• any—A source and source wildcard or destination and
destination wildcard of 0.0.0.0 255.255.255.255.
Step 4 end Return to privileged EXEC mode.
Step 5 show access-lists [number | name] Show the access list configuration.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove a named extended ACL, use the no ip access-list extended name global configuration
command.
When you are creating standard extended ACLs, remember that, by default, the end of the ACL contains
an implicit deny statement for everything if it did not find a match before reaching the end. For standard
ACLs, if you omit the mask from an associated IP host address access list specification, 0.0.0.0 is
assumed to be the mask.
After you create an ACL, any additions are placed at the end of the list. You cannot selectively add ACL
entries to a specific ACL. However, you can use no permit and no deny access-list configuration mode
commands to remove entries from a named ACL. This example shows how you can delete individual
ACEs from the named access list border-list:
Switch(config)# ip access-list extended border-list
Switch(config-ext-nacl)# no permit ip host 10.1.1.3 any
Being able to selectively remove lines from a named ACL is one reason you might use named ACLs
instead of numbered ACLs.
After creating a named ACL, you can apply it to interfaces (see the “Applying an IP ACL to an Interface”
section on page 33-19) or VLANs (see the “Configuring VLAN Maps” section on page 33-29).
Note The time range relies on the switch system clock; therefore, you need a reliable clock source. We
recommend that you use Network Time Protocol (NTP) to synchronize the switch clock. For more
information, see the “Managing the System Time and Date” section on page 5-1.
Beginning in privileged EXEC mode, follow these steps to configure an time-range parameter for an
ACL:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 time-range time-range-name Assign a meaningful name (for example, workhours) to the time range to
be created, and enter time-range configuration mode. The name cannot
contain a space or quotation mark and must begin with a letter.
Command Purpose
Step 3 absolute [start time date] Specify when the function it will be applied to is operational.
[end time date]
• You can use only one absolute statement in the time range. If you
or configure more than one absolute statement, only the one configured
periodic day-of-the-week hh:mm to last is executed.
[day-of-the-week] hh:mm
• You can enter multiple periodic statements. For example, you could
or configure different hours for weekdays and weekends.
periodic {weekdays | weekend | daily}
See the example configurations.
hh:mm to hh:mm
Step 4 end Return to privileged EXEC mode.
Step 5 show time-range Verify the time-range configuration.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
Repeat the steps if you have multiple items that you want in effect at different times.
To remove a configured time-range limitation, use the no time-range time-range-name global
configuration command.
This example shows how to configure time ranges for workhours and for a January 1, 2005 holiday and
to verify your configuration.
Switch(config)# time-range workhours
Switch(config-time-range)# periodic weekdays 8:00 to 12:00
Switch(config-time-range)# periodic weekdays 13:00 to 17:00
Switch(config-time-range)# exit
Switch(config)# time-range new_year_day_2005
Switch(config-time-range)# absolute start 00:00 1 Jan 2005 end 23:59 1 Jan 2005
Switch(config-time-range)# end
Switch# show time-range
time-range entry: new_year_day_2003 (inactive)
absolute start 00:00 01 January 2003 end 23:59 01 January 2003
time-range entry: workhours (inactive)
periodic weekdays 8:00 to 12:00
periodic weekdays 13:00 to 17:00
To apply a time-range, enter the time-range name in an extended ACL that can implement time ranges.
This example shows how to create and verify extended access list 188 that denies TCP traffic from any
source to any destination during the defined holiday times and permits all TCP traffic during work hours.
Switch(config)# access-list 188 deny tcp any any time-range new_year_day_2005
Switch(config)# access-list 188 permit tcp any any time-range workhours
Switch(config)# end
Switch# show access-lists
Extended IP access list 188
10 deny tcp any any time-range new_year_day_2003 (inactive)
20 permit tcp any any time-range workhours (inactive)
This example uses named ACLs to permit and deny the same traffic.
Switch(config)# ip access-list extended deny_access
Switch(config-ext-nacl)# deny tcp any any time-range new_year_day_2005
=Switch(config-ext-nacl)# exit
Switch(config)# ip access-list extended may_access
Switch(config-ext-nacl)# permit tcp any any time-range workhours
Switch(config-ext-nacl)# end
Switch# show ip access-lists
Extended IP access list deny_access
10 deny tcp any any time-range new_year_day_2003 (inactive)
=Extended IP access list may_access
10 permit tcp any any time-range workhours (inactive)
For an entry in a named IP ACL, use the remark access-list configuration command. To remove the
remark, use the no form of this command.
In this example, the Jones subnet is not allowed to use outbound Telnet:
Switch(config)# ip access-list extended telnetting
Switch(config-ext-nacl)# remark Do not allow Jones subnet to telnet out
Switch(config-ext-nacl)# deny tcp host 171.69.2.88 any eq telnet
Beginning in privileged EXEC mode, follow these steps to restrict incoming and outgoing connections
between a virtual terminal line and the addresses in an ACL:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 line [console | vty] line-number Identify a specific line to configure, and enter in-line configuration mode.
• console—Specify the console terminal line. The console port is DCE.
• vty—Specify a virtual terminal for remote console access.
The line-number is the first line number in a contiguous group that you want
to configure when the line type is specified. The range is from 0 to 16.
Step 3 access-class access-list-number Restrict incoming and outgoing connections between a particular virtual
{in | out} terminal line (into a device) and the addresses in an access list.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Display the access list configuration.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove an ACL from a terminal line, use the no access-class access-list-number {in | out} line
configuration command.
Note By default, the router sends Internet Control Message Protocol (ICMP) unreachable messages when a
packet is denied by an access group. These access-group denied packets are not dropped in hardware but
are bridged to the switch CPU so that it can generate the ICMP-unreachable message.
Beginning in privileged EXEC mode, follow these steps to control access to an interface:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Identify a specific interface for configuration, and enter interface
configuration mode.
The interface can be a Layer 2 interface (port ACL), or a Layer 3 interface
(router ACL).
Step 3 ip access-group {access-list-number | Control access to the specified interface.
name} {in | out}
The out keyword is not supported for Layer 2 interfaces (port ACLs).
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Display the access list configuration.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove the specified access group, use the no ip access-group {access-list-number | name} {in | out}
interface configuration command.
This example shows how to apply access list 2 on an interface to filter packets entering the interface:
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# ip access-group 2 in
Note When you apply the ip access-group interface configuration command to a Layer 3 interface (an SVI, a
Layer 3 EtherChannel, or a routed port), the interface must have been configured with an IP address.
Layer 3 access groups filter packets that are routed or are received by Layer 3 processes on the CPU.
They do not affect packets bridged within a VLAN.
For inbound ACLs, after receiving a packet, the switch checks the packet against the ACL. If the ACL
permits the packet, the switch continues to process the packet. If the ACL rejects the packet, the switch
discards the packet.
For outbound ACLs, after receiving and routing a packet to a controlled interface, the switch checks the
packet against the ACL. If the ACL permits the packet, the switch sends the packet. If the ACL rejects
the packet, the switch discards the packet.
By default, the input interface sends ICMP Unreachable messages whenever a packet is discarded,
regardless of whether the packet was discarded because of an ACL on the input interface or because of
an ACL on the output interface. ICMP Unreachables are normally limited to no more than one every
one-half second per input interface, but this can be changed by using the ip icmp rate-limit unreachable
global configuration command.
When you apply an undefined ACL to an interface, the switch acts as if the ACL has not been applied to
the interface and permits all packets. Remember this behavior if you use undefined ACLs for network
security.
Troubleshooting ACLs
If this ACL manager message appears and [chars] is the access-list name,
ACLMGR-2-NOVMR: Cannot generate hardware representation of access list [chars]
The switch has insufficient resources to create a hardware representation of the ACL. The resources
include hardware memory and label space but not CPU memory. A lack of available logical operation
units or specialized hardware resources causes this problem. Logical operation units are needed for a
TCP flag match or a test other than eq (ne, gt, lt, or range) on TCP, UDP, or SCTP port numbers.
Use one of these workarounds:
• Modify the ACL configuration to use fewer resources.
• Rename the ACL with a name or number that alphanumerically precedes the ACL names or
numbers.
To determine the specialized hardware resources, enter the show platform layer4 acl map privileged
EXEC command. If the switch does not have available resources, the output shows that index 0 to
index 15 are not available.
For more information about configuring ACLs with insufficient resources, see CSCsq63926 in the Bug
Toolkit.
For example, if you apply this ACL to an interface:
permit tcp source source-wildcard destination destination-wildcard range 5 60
permit tcp source source-wildcard destination destination-wildcard range 15 160
permit tcp source source-wildcard destination destination-wildcard range 115 1660
permit tcp source source-wildcard destination destination-wildcard
or
• Rename the ACL with a name or number that alphanumerically precedes the other ACLs (for
example, rename ACL 79 to ACL 1).
You can now apply the first ACE in the ACL to the interface. The switch allocates the ACE to available
mapping bits in the Opselect index and then allocates flag-related operators to use the same bits in the
TCAM.
Server A Server B
Benefits Payroll
Port 2 Port 1
101354
This example uses a standard ACL to filter traffic coming into Server B from an interface, permitting
traffic only from Accounting’s source addresses 172.20.128.64 to 172.20.128.95. The ACL is applied to
traffic coming out of routed Port 1 from the specified source address.
Switch(config)# access-list 6 permit 172.20.128.64 0.0.0.31
Switch(config)# end
Switch# show access-lists
Standard IP access list 6
10 permit 172.20.128.64, wildcard bits 0.0.0.31
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# ip access-group 6 out
This example uses an extended ACL to filter traffic coming from Server B into Port 1, permitting traffic
from any source address (in this case Server B) to only the Accounting destination addresses
172.20.128.64 to 172.20.128.95. The ACL is applied to traffic going into routed Port 1, permitting it to
go only to the specified destination addresses. Note that with extended ACLs, you must enter the
protocol (IP) before the source and destination information.
Switch(config)# access-list 106 permit ip any 172.20.128.64 0.0.0.31
Switch(config)# end
Switch# show access-lists
Extended IP access list 106
10 permit ip any 172.20.128.64 0.0.0.31
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# ip access-group 106 in
Numbered ACLs
In this example, network 36.0.0.0 is a Class A network whose second octet specifies a subnet; that is, its
subnet mask is 255.255.0.0. The third and fourth octets of a network 36.0.0.0 address specify a particular
host. Using access list 2, the switch accepts one address on subnet 48 and reject all others on that subnet.
The last line of the list shows that the switch accepts addresses on all other network 36.0.0.0 subnets.
The ACL is then applied to packets entering an interface.
Switch(config)# access-list 2 permit 36.48.0.3
Switch(config)# access-list 2 deny 36.48.0.0 0.0.255.255
Switch(config)# access-list 2 permit 36.0.0.0 0.255.255.255
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# ip access-group 2 in
Extended ACLs
In this example, the first line permits any incoming TCP connections with destination ports greater than
1023. The second line permits incoming TCP connections to the Simple Mail Transfer Protocol (SMTP)
port of host 128.88.1.2. The third line permits incoming ICMP messages for error feedback.
Switch(config)# access-list 102 permit tcp any 128.88.0.0 0.0.255.255 gt 1023
Switch(config)# access-list 102 permit tcp any host 128.88.1.2 eq 25
Switch(config)# access-list 102 permit icmp any any
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# ip access-group 102 in
For another example of using an extended ACL, suppose that you have a network connected to the
Internet, and you want any host on the network to be able to form TCP connections to any host on the
Internet. However, you do not want IP hosts to be able to form TCP connections to hosts on your
network, except to the mail (SMTP) port of a dedicated mail host.
SMTP uses TCP port 25 on one end of the connection and a random port number on the other end. The
same port numbers are used throughout the life of the connection. Mail packets coming in from the
Internet have a destination port of 25. Outbound packets have the port numbers reversed. Because the
secure system of the network always accepts mail connections on port 25, the incoming and outgoing
services are separately controlled. The ACL must be configured as an input ACL on the outbound
interface and an output ACL on the inbound interface.
In this example, the network is a Class B network with the address 128.88.0.0, and the mail host address
is 128.88.1.2. The established keyword is used only for the TCP to show an established connection. A
match occurs if the TCP datagram has the ACK or RST bits set, which show that the packet belongs to
an existing connection. The specified interface is the interface that connects the router to the Internet.
Switch(config)# access-list 102 permit tcp any 128.88.0.0 0.0.255.255 established
Switch(config)# access-list 102 permit tcp any host 128.88.1.2 eq 25
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# ip access-group 102 in
Named ACLs
This example creates a standard ACL named internet_filter and an extended ACL named
marketing_group. The internet_filter ACL allows all traffic from the source address 1.2.3.4.
Switch(config)# ip access-list standard Internet_filter
Switch(config-ext-nacl)# permit 1.2.3.4
Switch(config-ext-nacl)# exit
The marketing_group ACL allows any TCP Telnet traffic to the destination address and wildcard
171.69.0.0 0.0.255.255 and denies any other TCP traffic. It permits ICMP traffic, denies UDP traffic
from any source to the destination address range 171.69.0.0 through 179.69.255.255 with a destination
port less than 1024, denies any other IP traffic, and provides a log of the result.
Switch(config)# ip access-list extended marketing_group
Switch(config-ext-nacl)# permit tcp any 171.69.0.0 0.0.255.255 eq telnet
Switch(config-ext-nacl)# deny tcp any any
Switch(config-ext-nacl)# permit icmp any any
Switch(config-ext-nacl)# deny udp any 171.69.0.0 0.0.255.255 lt 1024
Switch(config-ext-nacl)# deny ip any any log
Switch(config-ext-nacl)# exit
The ACLs are applied to an interface, which is configured as a Layer 3 port, with the Internet_filter ACL
applied to outgoing traffic and the marketing_group ACL applied to incoming traffic.
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# no switchport
Switch(config-if)# ip address 2.0.5.1 255.255.255.0
Switch(config-if)# ip access-group Internet_filter out
Switch(config-if)# ip access-group marketing_group in
In this example of a numbered ACL, the Winter and Smith workstations are not allowed to browse the
web:
Switch(config)# access-list 100 remark Do not allow Winter to browse the web
Switch(config)# access-list 100 deny host 171.69.3.85 any eq www
Switch(config)# access-list 100 remark Do not allow Smith to browse the web
Switch(config)# access-list 100 deny host 171.69.3.13 any eq www
In this example of a named ACL, the Jones subnet is not allowed access:
Switch(config)# ip access-list standard prevention
Switch(config-std-nacl)# remark Do not allow Jones subnet through
Switch(config-std-nacl)# deny 171.69.0.0 0.0.255.255
In this example of a named ACL, the Jones subnet is not allowed to use outbound Telnet:
Switch(config)# ip access-list extended telnetting
Switch(config-ext-nacl)# remark Do not allow Jones subnet to telnet out
Switch(config-ext-nacl)# deny tcp 171.69.0.0 0.0.255.255 any eq telnet
ACL Logging
Two variations of logging are supported on router ACLs. The log keyword sends an informational
logging message to the console about the packet that matches the entry; the log-input keyword includes
the input interface in the log entry.
In this example, standard named access list stan1 denies traffic from 10.1.1.0 0.0.0.255, allows traffic
from all other sources, and includes the log keyword.
Switch(config)# ip access-list standard stan1
Switch(config-std-nacl)# deny 10.1.1.0 0.0.0.255 log
Switch(config-std-nacl)# permit any log
Switch(config-std-nacl)# exit
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# ip access-group stan1 in
Switch(config-if)# end
Switch# show logging
Syslog logging: enabled (0 messages dropped, 0 flushes, 0 overruns)
Console logging: level debugging, 37 messages logged
Monitor logging: level debugging, 0 messages logged
Buffer logging: level debugging, 37 messages logged
File logging: disabled
Trap logging: level debugging, 39 message lines logged
<output truncated>
This example is a named extended access list ext1 that permits ICMP packets from any source to 10.1.1.0
0.0.0.255 and denies all UDP packets.
Switch(config)# ip access-list extended ext1
Switch(config-ext-nacl)# permit icmp any 10.1.1.0 0.0.0.255 log
Switch(config-ext-nacl)# deny udp any any log
Switch(config-std-nacl)# exit
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# ip access-group ext1 in
Note that all logging entries for IP ACLs start with %SEC-6-IPACCESSLOG with minor variations in format
depending on the kind of ACL and the access entry that has been matched.
This is an example of an output message when the log-input keyword is entered:
00:04:21:%SEC-6-IPACCESSLOGDP:list inputlog permitted icmp 10.1.1.10 (Vlan1
0001.42ef.a400) -> 10.1.1.61 (0/0), 1 packet
A log message for the same sort of packet using the log keyword does not include the input interface
information:
00:05:47:%SEC-6-IPACCESSLOGDP:list inputlog permitted icmp 10.1.1.10 -> 10.1.1.61 (0/0), 1
packet
Note You cannot apply named MAC extended ACLs to Layer 3 interfaces.
For more information about the supported non-IPv4 protocols in the mac access-list extended
command, see the command reference for this release.
Note Though visible in the command-line help strings, appletalk is not supported as a matching condition for
the deny and permit MAC access-list configuration mode commands.
Beginning in privileged EXEC mode, follow these steps to create a named MAC extended ACL:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 mac access-list extended name Define an extended MAC access list using a name.
Command Purpose
Step 3 {deny | permit} {any | host source MAC In extended MAC access-list configuration mode, specify to
address | source MAC address mask} {any | permit or deny any source MAC address, a source MAC address
host destination MAC address | destination with a mask, or a specific host source MAC address and any
MAC address mask} [type mask | lsap lsap mask destination MAC address, destination MAC address with a mask,
| aarp | amber | dec-spanning | decnet-iv | or a specific destination MAC address.
diagnostic | dsm | etype-6000 | etype-8042 | lat (Optional) You can also enter these options:
| lavc-sca | mop-console | mop-dump | msdos |
mumps | netbios | vines-echo |vines-ip | • type mask—An arbitrary EtherType number of a packet with
xns-idp | 0-65535] [cos cos] Ethernet II or SNAP encapsulation in decimal, hex, or octal
with optional mask of don’t care bits applied to the EtherType
before testing for a match.
• lsap lsap mask—An LSAP number of a packet with 802.2
encapsulation in decimal, hex, or octal with optional mask of
don’t care bits.
• aarp | amber | dec-spanning | decnet-iv | diagnostic | dsm |
etype-6000 | etype-8042 | lat | lavc-sca | mop-console |
mop-dump | msdos | mumps | netbios | vines-echo |vines-ip
| xns-idp—A non-IP protocol.
• cos cos—An IEEE 802.1p cost of service number from 0 to 7
used to set priority.
Step 4 end Return to privileged EXEC mode.
Step 5 show access-lists [number | name] Show the access list configuration.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no mac access-list extended name global configuration command to delete the entire ACL. You
can also delete individual ACEs from named MAC extended ACLs.
This example shows how to create and display an access list named mac1, denying only EtherType
DECnet Phase IV traffic, but permitting all other types of traffic.
Switch(config)# mac access-list extended mac1
Switch(config-ext-macl)# deny any any decnet-iv
Switch(config-ext-macl)# permit any any
Switch(config-ext-macl)# end
Switch # show access-lists
Extended MAC access list mac1
10 deny any any decnet-iv
20 permit any any
• A Layer 2 interface can have only one MAC access list. If you apply a MAC access list to a Layer
2 interface that has a MAC ACL configured, the new ACL replaces the previously configured one.
Beginning in privileged EXEC mode, follow these steps to apply a MAC access list to control access to
a Layer 2 interface:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Identify a specific interface, and enter interface configuration
mode. The interface must be a physical Layer 2 interface (port
ACL).
Step 3 mac access-group {name} {in} Control access to the specified interface by using the MAC access
list.
Note Port ACLs are supported only in the inbound direction.
Step 4 end Return to privileged EXEC mode.
Step 5 show mac access-group [interface interface-id] Display the MAC access list applied to the interface or all Layer 2
interfaces.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove the specified access group, use the no mac access-group {name} interface configuration
command.
This example shows how to apply MAC access list mac1 on an interface to filter packets entering the
interface:
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# mac access-group mac1 in
Note The mac access-group interface configuration command is only valid when applied to a physical
Layer 2 interface.You cannot use the command on EtherChannel port channels.
After receiving a packet, the switch checks it against the inbound ACL. If the ACL permits it, the switch
continues to process the packet. If the ACL rejects the packet, the switch discards it. When you apply an
undefined ACL to an interface, the switch acts as if the ACL has not been applied and permits all packets.
Remember this behavior if you use undefined ACLs for network security.
Note For complete syntax and usage information for the commands used in this section, see the command
reference for this release.
To create a VLAN map and apply it to one or more VLANs, perform these steps:
Step 1 Create the standard or extended IP ACLs or named MAC extended ACLs that you want to apply to the
VLAN. See the “Creating Standard and Extended IP ACLs” section on page 33-7 and the “Creating a
VLAN Map” section on page 33-31.
Step 2 Enter the vlan access-map global configuration command to create a VLAN ACL map entry.
Step 3 In access map configuration mode, optionally enter an action—forward (the default) or drop—and
enter the match command to specify an IPv4 packet or a non-IPv4 packet (with only a known MAC
address) and to match the packet against one or more ACLs (standard or extended).
Note If the VLAN map is configured with a match clause for a type of packet (IP or MAC) and the map action
is drop, all packets that match the type are dropped. If the VLAN map has no match clause, and the
configured action is drop, then all IP and Layer 2 packets are dropped.
Step 4 Use the vlan filter global configuration command to apply a VLAN map to one or more VLANs.
• See the “Using VLAN Maps in Your Network” section on page 33-34 for configuration examples.
• For information about using both router ACLs and VLAN maps, see the “Guidelines” section on
page 33-38.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 vlan access-map name [number] Create a VLAN map, and give it a name and (optionally) a number. The
number is the sequence number of the entry within the map.
When you create VLAN maps with the same name, numbers are assigned
sequentially in increments of 10. When modifying or deleting maps, you
can enter the number of the map entry that you want to modify or delete.
Entering this command changes to access-map configuration mode.
Step 3 action {drop | forward} (Optional) Set the action for the map entry. The default is to forward.
Step 4 match {ip | mac} address {name | Match the packet (using either the IP or MAC address) against one or more
number} [name | number] standard or extended access lists. Note that packets are only matched
against access lists of the correct protocol type. IP packets are matched
against standard or extended IP access lists. Non-IPv4 packets are only
matched against named MAC extended access lists.
Step 5 end Return to global configuration mode.
Step 6 show running-config Display the access list configuration.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no vlan access-map name global configuration command to delete a map.
Use the no vlan access-map name number global configuration command to delete a single sequence
entry from within the map.
Use the no action access-map configuration command to enforce the default action, which is to forward.
VLAN maps do not use the specific permit or deny keywords. To deny a packet by using VLAN maps,
create an ACL that would match the packet, and set the action to drop. A permit in the ACL counts as a
match. A deny in the ACL means no match.
Example 1
This example shows how to create an ACL and a VLAN map to deny a packet. In the first map, any
packets that match the ip1 ACL (TCP packets) would be dropped. You first create the ip1ACL to permit
any TCP packet and no other packets. Because there is a match clause for IP packets in the VLAN map,
the default action is to drop any IP packet that does not match any of the match clauses.
Switch(config)# ip access-list extended ip1
Switch(config-ext-nacl)# permit tcp any any
Switch(config-ext-nacl)# exit
Switch(config)# vlan access-map map_1 10
Switch(config-access-map)# match ip address ip1
Switch(config-access-map)# action drop
This example shows how to create a VLAN map to permit a packet. ACL ip2 permits UDP packets and
any packets that match the ip2 ACL are forwarded. In this map, any IP packets that did not match any of
the previous ACLs (that is, packets that are not TCP packets or UDP packets) would get dropped.
Switch(config)# ip access-list extended ip2
Switch(config-ext-nacl)# permit udp any any
Switch(config-ext-nacl)# exit
Switch(config)# vlan access-map map_1 20
Switch(config-access-map)# match ip address ip2
Switch(config-access-map)# action forward
Example 2
In this example, the VLAN map has a default action of drop for IP packets and a default action of forward
for MAC packets. Used with standard ACL 101 and extended named access lists igmp-match and
tcp-match, the map will have the following results:
• Forward all UDP packets
• Drop all IGMP packets
• Forward all TCP packets
• Drop all other IP packets
• Forward all non-IPv4 packets
Switch(config)# access-list 101 permit udp any any
Switch(config)# ip access-list extended igmp-match
Switch(config-ext-nacl)# permit igmp any any
Switch(config)# ip access-list extended tcp-match
Switch(config-ext-nacl)# permit tcp any any
Switch(config-ext-nacl)# exit
Switch(config)# vlan access-map drop-ip-default 10
Switch(config-access-map)# match ip address 101
Switch(config-access-map)# action forward
Switch(config-access-map)# exit
Switch(config)# vlan access-map drop-ip-default 20
Switch(config-access-map)# match ip address igmp-match
Switch(config-access-map)# action drop
Switch(config-access-map)# exit
Switch(config)# vlan access-map drop-ip-default 30
Switch(config-access-map)# match ip address tcp-match
Switch(config-access-map)# action forward
Example 3
In this example, the VLAN map has a default action of drop for MAC packets and a default action of
forward for IP packets. Used with MAC extended access lists good-hosts and good-protocols, the map
will have the following results:
• Forward MAC packets from hosts 0000.0c00.0111 and 0000.0c00.0211
• Forward MAC packets with decnet-iv or vines-ip protocols
• Drop all other non-IPv4 packets
• Forward all IP packets
Switch(config)# mac access-list extended good-hosts
Switch(config-ext-macl)# permit host 000.0c00.0111 any
Switch(config-ext-macl)# permit host 000.0c00.0211 any
Switch(config-ext-nacl)# exit
Switch(config)# mac access-list extended good-protocols
Switch(config-ext-macl)# permit any any decnet-ip
Switch(config-ext-macl)# permit any any vines-ip
Switch(config-ext-nacl)# exit
Switch(config)# vlan access-map drop-mac-default 10
Switch(config-access-map)# match mac address good-hosts
Switch(config-access-map)# action forward
Switch(config-access-map)# exit
Switch(config)# vlan access-map drop-mac-default 20
Switch(config-access-map)# match mac address good-protocols
Switch(config-access-map)# action forward
Example 4
In this example, the VLAN map has a default action of drop for all packets (IPv4 and non-IPv4). Used
with access lists tcp-match and good-hosts from Examples 2 and 3, the map will have the following
results:
• Forward all TCP packets
• Forward MAC packets from hosts 0000.0c00.0111 and 0000.0c00.0211
• Drop all other IP packets
• Drop all other MAC packets
Switch(config)# vlan access-map drop-all-default 10
Switch(config-access-map)# match ip address tcp-match
Switch(config-access-map)# action forward
Switch(config-access-map)# exit
Switch(config)# vlan access-map drop-all-default 20
Switch(config-access-map)# match mac address good-hosts
Switch(config-access-map)# action forward
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 vlan filter mapname vlan-list list Apply the VLAN map to one or more VLAN IDs.
The list can be a single VLAN ID (22), a consecutive list (10-22), or a string
of VLAN IDs (12, 22, 30). Spaces around the comma and hyphen are
optional.
Step 3 show running-config Display the access list configuration.
Step 4 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove the VLAN map, use the no vlan filter mapname vlan-list list global configuration command.
This example shows how to apply VLAN map 1 to VLANs 20 through 22:
Switch(config)# vlan filter map 1 vlan-list 20-22
Switch B
Switch A Switch C
Host X Host Y
10.1.1.32 10.1.1.34
VLAN 1
101355
VLAN 2
Packet
If you do not want HTTP traffic switched from Host X to Host Y, you can configure a VLAN map on
Switch A to drop all HTTP traffic from Host X (IP address 10.1.1.32) to Host Y (IP address 10.1.1.34)
at Switch A and not bridge it to Switch B.
First, define the IP access list http that permits (matches) any TCP traffic on the HTTP port.
Switch(config)# ip access-list extended http
Switch(config-ext-nacl)# permit tcp host 10.1.1.32 host 10.1.1.34 eq www
Switch(config-ext-nacl)# exit
Next, create VLAN access map map2 so that traffic that matches the http access list is dropped and all
other IP traffic is forwarded.
Switch(config)# vlan access-map map2 10
Switch(config-access-map)# match ip address http
Switch(config-access-map)# action drop
Switch(config-access-map)# exit
Switch(config)# ip access-list extended match_all
Switch(config-ext-nacl)# permit ip any any
Switch(config-ext-nacl)# exit
Switch(config)# vlan access-map map2 20
Switch(config-access-map)# match ip address match_all
Switch(config-access-map)# action forward
VLAN map
10.1.1.100
Subnet
Server (VLAN 10) 10.1.2.0/8
10.1.1.4
Host (VLAN 20)
Host (VLAN 10) Layer 3 switch
10.1.1.8
101356
Host (VLAN 10) Packet
This example shows how to deny access to a server on another VLAN by creating the VLAN map
SERVER 1 that denies access to hosts in subnet 10.1.2.0/8, host 10.1.1.4, and host 10.1.1.8 and permits
other IP traffic. The final step is to apply the map SERVER1 to VLAN 10.
Step 1 Define the IP ACL that will match the correct packets.
Switch(config)# ip access-list extended SERVER1_ACL
Switch(config-ext-nacl))# permit ip 10.1.2.0 0.0.0.255 host 10.1.1.100
Switch(config-ext-nacl))# permit ip host 10.1.1.4 host 10.1.1.100
Switch(config-ext-nacl))# permit ip host 10.1.1.8 host 10.1.1.100
Switch(config-ext-nacl))# exit
Step 2 Define a VLAN map using this ACL that will drop IP packets that match SERVER1_ACL and forward
IP packets that do not match the ACL.
Switch(config)# vlan access-map SERVER1_MAP
Switch(config-access-map)# match ip address SERVER1_ACL
Switch(config-access-map)# action drop
Switch(config)# vlan access-map SERVER1_MAP 20
Switch(config-access-map)# action forward
Switch(config-access-map)# exit
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. If a flow does not receive any packets in the 5-minute interval, that
flow is removed from the cache. When a syslog message is generated, the timer and packet counter are
reset.
VACL logging restrictions:
• Only denied IP packets are logged.
• Packets that require logging on the outbound port ACLs are not logged if they are denied by a VACL.
Beginning in privileged EXEC mode:
Command Purpose
Step 1 configure terminal Enter the global configuration mode.
Step 2 vlan access-map name [number] Create a VLAN map. Give it a name and optionally a number. The
number is the sequence number of the entry within the map.
The sequence number range is from 0 to 65535.
When you create VLAN maps with the same name, numbers are
assigned sequentially in increments of 10. When modifying or
deleting maps, you can enter the number of the map entry that you
want to modify or delete.
Specifying the map name and optionally a number enters the ac-
cess-map configuration mode.
Step 3 action drop log Set the VLAN access map to drop and log IP packets.
Step 4 exit Exit the VLAN access map configuration mode and return to the
global configuration mode.
Step 5 vlan access-log {maxflow max_number | Configure the VACL logging parameters.
threshold pkt_count}
• maxflow max_number—Set the log table size. The content of
the log table can be deleted by setting the maxflow to 0. When
the log table is full, the software drops logged packets from
new flows.
The range is from 0 to 2048. The default is 500.
• threshold pkt_count—Set the logging threshold. A logging
message is generated if the threshold for a flow is reached before
the 5-minute interval.
The threshold range is from 0 to 2147483647. The default
threshold is 0, which means that a syslog message is generated
every 5 minutes.
Step 6 exit Return to privileged EXEC mode.
Step 7 show vlan access-map Verify your entries.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no vlan access-map command with a sequence number to delete a map sequence. Use the no
version of the command without a sequence number to delete the map.
This example shows how to configure a VLAN access map to drop and log IP packets. Here IP traffic
matching the permit entries in net_10 is dropped and logged.
DomainMember(config)# vlan access-map ganymede 10
DomainMember(config-access-map)# match ip address net_10
DomainMember(config-access-map)# action drop log
DomainMember(config-access-map)# exit
Note For complete syntax and usage information of the commands used in this section, see the Cisco IOS LAN
Switching Command Reference:
http://www.cisco.com/en/US/docs/ios/lanswitch/command/reference/lsw_book.html
Note When you use router ACLs with VLAN maps, packets that require logging on the router ACLs are not
logged if they are denied by a VLAN map.
If the VLAN map has a match clause for the type of packet (IP or MAC) and the packet does not match
the type, the default is to drop the packet. If there is no match clause in the VLAN map, and no action
specified, the packet is forwarded if it does not match any VLAN map entry.
This section includes this information about using VLAN maps with router ACLs:
• Guidelines, page 33-38
• Examples of Router ACLs and VLAN Maps Applied to VLANs, page 33-39
Guidelines
These guidelines are for configurations where you need to have an router ACL and a VLAN map on the
same VLAN. These guidelines do not apply to configurations where you are mapping router ACLs and
VLAN maps on different VLANs.
The switch hardware provides one lookup for security ACLs for each direction (input and output);
therefore, you must merge a router ACL and a VLAN map when they are configured on the same VLAN.
Merging the router ACL with the VLAN map might significantly increase the number of ACEs.
If you must configure a router ACL and a VLAN map on the same VLAN, use these guidelines for both
router ACL and VLAN map configuration:
• You can configure only one VLAN map and one router ACL in each direction (input/output) on a
VLAN interface.
• Whenever possible, try to write the ACL with all entries having a single action except for the final,
default action of the other type. That is, write the ACL using one of these two forms:
permit...
permit...
permit...
deny ip any any
or
deny...
deny...
deny...
permit ip any any
• To define multiple actions in an ACL (permit, deny), group each action type together to reduce the
number of entries.
• Avoid including Layer 4 information in an ACL; adding this information complicates the merging
process. The best merge results are obtained if the ACLs are filtered based on IP addresses (source
and destination) and not on the full flow (source IP address, destination IP address, protocol, and
protocol ports). It is also helpful to use don’t care bits in the IP address, whenever possible.
If you need to specify the full-flow mode and the ACL contains both IP ACEs and TCP/UDP/ICMP
ACEs with Layer 4 information, put the Layer 4 ACEs at the end of the list. This gives priority to
the filtering of traffic based on IP addresses.
Input Output
VLAN 10 router router VLAN 20
map ACL ACL map
Frame
Host A
(VLAN 10)
Routing function or
fallback bridge
Host C
(VLAN 10)
101357
VLAN 10 Packet VLAN 20
VLAN 10 VLAN 20
map map
Frame
Host A Host B
(VLAN 10) (VLAN 20)
Fallback bridge
101358
Input Output
VLAN 10 router router VLAN 20
map ACL ACL map
Frame
Host A Host B
(VLAN 10) (VLAN 20)
Routing function
101359
VLAN 10 Packet VLAN 20
Input Output
VLAN 10 router router VLAN 20
map ACL ACL map
Frame
Host A Host B
(VLAN 10) (VLAN 20)
Routing function
Host C
(VLAN 10)
101360
VLAN 10 Packet VLAN 20
Table 33-2 Commands for Displaying Access Lists and Access Groups
Command Purpose
show access-lists [number | name] Display the contents of one or all current IP and MAC address access lists
or a specific access list (numbered or named).
show ip access-lists [number | name] Display the contents of all current IP access lists or a specific IP access list
(numbered or named).
show ip interface interface-id Display detailed configuration and status of an interface. If IP is enabled
on the interface and ACLs have been applied by using the ip access-group
interface configuration command, the access groups are included in the
display.
show running-config [interface interface-id] Displays the contents of the configuration file for the switch or the
specified interface, including all configured MAC and IP access lists and
which access groups are applied to an interface.
show mac access-group [interface interface-id] Displays MAC access lists applied to all Layer 2 interfaces or the specified
Layer 2 interface.
You can also display information about VLAN access maps or VLAN filters. Use the privileged EXEC
commands in Table 33-3 to display VLAN map information.
Command Purpose
show vlan access-map [mapname] Show information about all VLAN access-maps or the
specified access map.
show vlan filter [access-map name | vlan vlan-id] Show information about all VLAN filters or about a specified
VLAN or VLAN access map.
This chapter describes how to use different methods to configure quality of service (QoS) on the
Catalyst 3750 Metro switch. With QoS, you can provide preferential treatment to certain types of traffic
traffic at the expense of others. Without QoS, the switch offers best-effort service to each packet,
regardless of the packet contents or size. It sends the packets without any assurance of reliability, delay
bounds, or throughput.
You can use auto-QoS to identify ports connected to Cisco IP Phones and to devices running the Cisco
SoftPhone application. You also use the commands to identify ports that receive trusted voice over IP
(VoIP) traffic.
You can use standard QoS to classify, police, mark, queue, and schedule inbound traffic on any port as
well as queue and schedule outbound traffic. On ingress, standard QoS offers classification based on the
class of service (CoS), Differentiated Services Code Point (DSCP), or IP precedence value in the
inbound packet. You can perform the classification based on Layer 2 MAC, IP-standard, or IP-extended
access control lists (ACLs). Standard QoS also offers nonhierarchical single-level policy maps on
physical ports and hierarchical dual-level policy maps on switch virtual interfaces (SVIs). Drop policy
actions are passing through the packet without modification, marking down the assigned DSCP in the
packet, or dropping the packet. Standard QoS performs ingress queueing based on the weighted tail drop
(WTD) algorithm and ingress scheduling based on shaped round robin (SRR). On egress, standard QoS
offers queueing based on WTD and scheduling based on SRR shared or shaped weights. An egress
priority queue is also offered.
Note In the Catalyst 3750, 3560, and 2970 switch software documentation, single-level policy maps are
referred to as nonhierarchical policy maps. Dual-level policy maps are referred to as hierarchical policy
maps with two levels.
You can use hierarchical QoS to classify, police, mark, queue, and schedule inbound or outbound traffic
on an enhanced-services (ES) port or an EtherChannel of ES ports. Hierarchical QoS offers classification
based on the CoS, DSCP, IP precedence, or the multiprotocol label switching (MPLS) experimental
(EXP) bits in the packet. You also can classify a packet based on its VLAN. Hierarchical QoS offers
two-rate traffic policing. Drop policy actions are passing the packet through without modification;
marking down the CoS, DSCP, IP precedence, or the MPLS EXP bits in the packet; or dropping the
packet. Hierarchical QoS performs queueing based on tail drop or Weighted Random Early Detection
(WRED). The queue scheduling management feature is class-based weighted fair queueing (CBWFQ),
and the scheduling congestion-management feature is low-latency queueing (LLQ). You can use traffic
shaping to decrease the burstiness of traffic.
For information about MPLS, Ethernet over MPLS (EoMPLS), and QoS, see the “Configuring MPLS
and EoMPLS QoS” section on page 44-51.
Note For complete syntax and usage information for the commands used in this chapter, see the command
reference this release.
QoS 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.
When you configure the QoS feature, you can select specific network traffic, prioritize it according to
its relative importance, and use congestion-management and congestion-avoidance techniques to
provide preferential treatment. Implementing QoS in your network makes network performance more
predictable and bandwidth utilization more effective.
The QoS implementation is based on the Differentiated Services (Diff-Serv) architecture, an emerging
standard from the Internet Engineering Task Force (IETF). This architecture specifies that each packet
is classified upon entry into the network.
The classification is carried in the IP packet header, using 6 bits from the deprecated IP type of service
(ToS) field to carry the classification (class) information. Classification also can be carried in the
Layer 2 frame. These special bits in the Layer 2 frame or in the Layer 3 packet are described here and
shown in Figure 34-1:
• Prioritization bits in Layer 2 frames:
Layer 2 Inter-Switch Link (ISL) frame headers have a 1-byte User field that carries an IEEE 802.1p
CoS value in the three least-significant bits. On ports configured as Layer 2 ISL trunks, all traffic is
in ISL frames.
Layer 2 802.1Q frame headers have a 2-byte Tag Control Information field that carries the CoS value
in the three most-significant bits, which are called the User Priority bits. On ports configured as
Layer 2 802.1Q trunks, all traffic is in IEEE 802.1Q frames except for traffic in the native VLAN.
Other frame types cannot carry Layer 2 CoS values.
Layer 2 CoS values range from 0 for low priority to 7 for high priority.
• Prioritization bits in Layer 3 packets:
Layer 3 IP packets can carry either an IP precedence value or a DSCP value. QoS supports the use
of either value because DSCP values are backward-compatible with IP precedence values.
IP precedence values range from 0 to 7.
DSCP values range from 0 to 63.
• Cisco IOS Release 12.2(52)SE and later supports IPv6 port-based trust with the dual IPv4 and IPv6
Switch Database Management (SDM) templates. You must reload the switch with the dual IPv4 and
IPv6 templates for switches running IPv6. For more information, see Chapter 6, “Configuring SDM
Templates.”
Encapsulated Packet
Layer 2
IP header Data
header
IP precedence or DSCP
Version
(1 byte) label length header limit address address
IP precedence or DSCP
Note Layer 3 IPv6 packets are treated as non-IP packets and are bridged by the switch.
All switches and routers that access the Internet rely on the class information to provide the same
forwarding treatment to packets with the same class information and different treatment to packets with
different class information. The class information in the packet can be assigned by end hosts or by
switches or routers along the way, based on a configured policy, detailed examination of the packet, or
both. Detailed examination of the packet is expected to happen closer to the edge of the network so that
the core switches and routers are not overloaded with this task.
Switches and routers along the path can use the class information to limit the amount of resources
allocated per traffic class. The behavior of an individual device when handling traffic in the DiffServ
architecture is called per-hop behavior. If all devices along a path provide a consistent per-hop behavior,
you can construct an end-to-end QoS solution.
Implementing QoS in your network can be a simple or complex task and depends on the QoS features
offered by your internetworking devices, the traffic types and patterns in your network, and the degree
of control that you need over inbound and outbound traffic.
In profile or
out of profile Queueing and Traffic sent to an ES port
Classification Policing Mark
scheduling
it according to the
configuration.
To implement QoS, the switch must distinguish (classify) packets or flows from one another, assign a
label to indicate the given quality of service as the packets move through the switch, make the packets
comply with the configured resource usage limits (police and mark), and provide different treatment
(queue and schedule) in all situations where resource contention exists. The switch also needs to ensure
that the traffic it sends meets a specific traffic profile (shape).
These are the standard actions when traffic is received on any port:
• Classification is the process of generating a distinct path for a packet by associating it with a QoS
label. The switch maps the CoS or DSCP in the packet to a QoS label to distinguish one kind of
traffic from another. The QoS label that is generated identifies all future QoS actions to be
performed on this packet. For more information, see the “Ingress Classification” section on
page 34-9.
• Policing decides whether a packet is in or out of profile by comparing the rate of the inbound traffic
to the configured policer. The policer limits the bandwidth consumed by a flow of traffic. The result
is passed to the marker. For more information, see the “Ingress Policing and Marking” section on
page 34-13.
• Marking evaluates the policer configuration information for the action to take when a packet is out
of profile. Marking actions are to pass through a packet without modification, to mark down the QoS
label in the packet, or to drop the packet. For more information, see the “Ingress Policing and
Marking” section on page 34-13.
• Queueing evaluates the QoS label and the corresponding DSCP or CoS value to select into which of
the two ingress queues to place a packet. Queueing is enhanced with the WTD algorithm, a
congestion-avoidance mechanism. If the threshold is exceeded, the packet is dropped. For more
information, see the “Queueing and Scheduling Overview” section on page 34-17.
• Scheduling services the queues based on their configured (SRR) weights. One of the ingress queues
is the priority queue, and SRR services it for its configured share before servicing the other queue.
For more information, see the “SRR Shaping and Sharing” section on page 34-19.
These are the standard actions when traffic is received on or sent to a standard port:
• Queueing evaluates the QoS label and the corresponding DSCP or CoS value to select into which
queue-set (a set of four queues per port) to place a packet. Because congestion can occur when
multiple ingress ports simultaneously send data to an egress port, WTD is used to differentiate traffic
classes and to subject the packets to different thresholds based on the QoS label. If the threshold is
exceeded, the packet is dropped. For more information, see the “Queueing and Scheduling
Overview” section on page 34-17.
• Scheduling services the four egress queues based on their configured SRR shared or shaped weights.
One of the queues (queue 1) can be the priority queue. Before servicing the other queues, SRR
services the priority queue until it is empty.
These are the additional actions when traffic is received on or sent to an ES port:
• Classification is the process of generating a distinct path for a packet by matching the CoS, DSCP,
IP precedence, by matching the MPLS EXP bits in the header, or by matching a packet based on the
inner and the outer VLAN IDs or CoS values. The hierarchical configuration controls the number
of class-level, VLAN-level, and physical-interface-level queues to create. For information, see the
“Understanding Hierarchical QoS” section on page 34-30 and the “Hierarchical Levels” section on
page 34-30. For classification information, see the “Hierarchical Classification Based on Traffic
Classes and Traffic Policies” section on page 34-33.
• Policing decides whether a packet is in or out of profile by comparing the rate of the inbound or the
outbound traffic to the configured policer. The policer limits the bandwidth consumed by a flow of
traffic. The result is passed to the marker. For more information, see the “Hierarchical Policies and
Marking” section on page 34-34.
• Marking evaluates the policer and configuration information for the action to be taken when a packet
is out of profile and resolves what to do with the packet (pass it through without modification, mark
down the QoS label, or drop). For more information, see the “Hierarchical Policies and Marking”
section on page 34-34.
• Queueing is accomplished through a hierarchical queueing framework, in which the switch assigns
each packet to a queue based on the packet class, VLAN, and physical interface. Tail drop or WRED
can be configured per queue as the congestion-avoidance mechanism. With tail drop, packets are
queued until the maximum threshold is exceeded, and then all the packets are dropped. WRED
reduces the chances of tail drop by selectively dropping packets when the port begins to show signs
of congestion. For more information, see the “Queueing and Scheduling of Hierarchical Queues”
section on page 34-37.
• Scheduling is accomplished through Class-based weighted fair queueing (CBWFQ) or LLQ. CBWFQ
provides guaranteed bandwidth to a particular traffic class while still fairly serving all other traffic
in the network. LLQ is another scheduling mechanism, which ensures that delay-sensitive traffic is
queued and sent before the traffic in other queues. Scheduling services the queues through
average-rate shaping. For more information, see the “Queueing and Scheduling of Hierarchical
Queues” section on page 34-37.
Note Note: A two-level policy on an SVI is different than a hierarchical policy with two levels on ES ports.
Table 34-1 shows the types of policy maps supported on different interfaces.
If you add an action to an unsupported policy-map format or interface, you cannot attach the service
policy to the interface.
Note that different software releases also have different levels of support for policy maps:
Ingress Classification
Ingress classification distinguishes one kind of traffic from another by examining the fields in the packet
upon receipt. Classification is enabled only if QoS is globally enabled on the switch. By default, QoS is
globally disabled, so no classification occurs.
During ingress classification, the switch performs a lookup and assigns a QoS label to the packet. The
QoS label identifies all QoS actions to be performed on the packet and from which queue the packet is
sent.
The QoS label is based on the DSCP or the CoS value in the packet and determines the queueing and
scheduling actions to perform on the packet. The label is mapped according to the trust setting and the
packet type as shown in Figure 34-3 on page 34-11.
You specify which fields in the frame or the packet that you want to use to classify inbound traffic. For
non-IP traffic, you have these ingress classification options, as shown in Figure 34-3:
• Trust the CoS value in the inbound frame (configure the port to trust CoS). Then use the configurable
CoS-to-DSCP map to generate a DSCP value for the packet. Layer 2 ISL frame headers carry the
CoS value in the three least-significant bits of the 1-byte User field. Layer 2 IEEE 802.1Q frame
headers carry the CoS value in the three most-significant bits of the Tag Control Information field.
CoS values range from 0 for low priority to 7 for high priority.
• Trust the DSCP or trust IP precedence value in the inbound frame. These configurations are
meaningless for non-IP traffic. If you configure a port with either of these options and non-IP traffic
is received, the switch assigns a CoS value and generates an internal DSCP value from the
CoS-to-DSCP map. The switch uses the internal DSCP value to generate a CoS value representing
the priority of the traffic.
• Perform the classification based on a configured Layer 2 MAC ACL, which can examine the MAC
source address, the MAC destination address, and other fields. If no ACL is configured, the packet
is assigned 0 for the DSCP and CoS values, which means best-effort traffic. Otherwise, the
policy-map action specifies a DSCP or a CoS value to assign to the inbound frame.
For IP traffic, you have these ingress classification options, as shown in Figure 34-3:
• Trust the DSCP value in the inbound packet (configure the port to trust DSCP), and assign the same
DSCP value to the packet. The IETF defines the six most-significant bits of the 1-byte ToS field as
the DSCP. The priority represented by a particular DSCP value is configurable. DSCP values range
from 0 to 63.
For ports that are on the boundary between two QoS administrative domains, you can modify the
DSCP to another value through the configurable DSCP-to-DSCP-mutation map.
• Trust the IP precedence value in the inbound packet (configure the port to trust IP precedence), and
generate a DSCP value for the packet through the configurable IP-precedence-to-DSCP map. The
IP Version 4 specification defines the three most-significant bits of the 1-byte ToS field as the IP
precedence. IP precedence values range from 0 for low priority to 7 for high priority.
• Trust the CoS value (if present) in the inbound packet, and generate a DSCP value for the packet through
the CoS-to-DSCP map. If the CoS value is not present, use the port CoS value.
• Perform the classification based on a configured IP standard or an extended ACL, which examines
various fields in the IP header. If no ACL is configured, the packet is assigned 0 as the DSCP and
CoS values, which means best-effort traffic. Otherwise, the policy-map action specifies a DSCP or
a CoS value to assign to the inbound frame.
For information on the maps described in this section, see the “Mapping Tables” section on page 34-17.
For configuration information on port trust states, see the “Configuring Ingress Classification by Using
Port Trust States” section on page 34-56.
You can configure classification through ACLs, traffic classes, and traffic policies. For more
information, see the “Ingress Classification Based on QoS ACLs” section on page 34-11 and the “Ingress
Classification Based on Traffic Classes and Traffic Policies” section on page 34-12.
After ingress classification, the packet is sent to the policing, marking, and the ingress queueing and
scheduling stages.
Start
Done Done
Assign the DSCP or CoS as specified Assign the default Generate the DSCP by using
by ACL action to generate the QoS label. DSCP (0). the CoS-to-DSCP map.
86834
Done Done
• If a match with a deny action is encountered, the ACL being processed is omitted, and the next ACL
is processed.
• If no match with a permit action is encountered and all the ACEs have been examined, no QoS
processing occurs on the packet, and the switch offers best-effort service to the packet.
• If multiple ACLs are configured on a port, the lookup stops after the packet matches the first ACL
with a permit action, and QoS processing begins.
Note When you create an access list, remember that the end of the access list contains an implicit deny
statement for everything if it did not find a match before reaching the end.
After a traffic class is defined with the ACL, you can attach a policy to it. A policy might contain multiple
classes with actions specified for each one of them. A policy might include commands to classify the
class as a particular aggregate (for example, assign a DSCP) or to rate-limit the class. This ingress policy
is then attached to a port.
You implement IP ACLs to classify IP traffic by using the access-list global configuration command;
you implement Layer 2 MAC ACLs to classify non-IP traffic by using the mac access-list extended
global configuration command. For configuration information, see the “Configuring an Ingress QoS
Policy” section on page 34-63.
An ingress policy map can include police, police aggregate, trust, or set policy-map class configuration
commands. You attach the ingress policy map to a port by using the service-policy input interface
configuration command.
In software releases earlier than Cisco IOS Release 12.2(25)EY, you can apply a nonhierarchical
single-level policy map only to a physical port—in both directions of an ES port and in the input
direction of a standard port. Hierarchical (up to three-level) policy maps were supported only as output
policy maps on ES ports. Cisco IOS Release 12.2(25)EY or later also supports up to two-level policy
maps in the input direction of an SVI and up to three-level policy maps as input policy maps on ES ports.
However, a hierarchical dual-level policy map can only be applied to an SVI. The dual-level policy map
contains two levels. The first level, the VLAN level, specifies the actions to be taken against a traffic
flow on the SVI. The second level, the interface level, specifies the actions to be taken against the traffic
on the physical ports that belong to the SVI. The interface-level actions are specified in the
interface-level policy map. You can also use Cisco IOS Release 12.2(35)SE to apply single-level output
policy maps and hierarchical input and output maps to EtherChannels consisting of ES ports.
For more information, see the “Ingress Policing and Marking” section on page 34-13. For configuration
information, see the “Configuring an Ingress QoS Policy” section on page 34-63.
Note All traffic, regardless of whether it is bridged or routed, is subjected to a configured policer. As a result,
bridged packets might be dropped or might have their DSCP or CoS fields modified when they are
policed and marked.
Note Input hierarchical service policies are applied to a traffic stream before any other services act on that
traffic. For example, an input hierarchical service policy applied to traffic could change the traffic rate
from above a storm-control threshold to below the threshold, preventing storm control from acting on
the traffic stream.
• Aggregate
QoS applies the bandwidth limits specified in an aggregate policer cumulatively to all matched
traffic flows. You configure this type of policer by specifying the aggregate policer name within a
policy map by using the police aggregate policy-map class configuration command. You specify the
bandwidth limits of the policer by using the mls qos aggregate-policer global configuration
command. In this way, the aggregate policer is shared by multiple classes of traffic within a policy
map.
Note You can only configure only individual policers on SVIs and only with Cisco IOS Release
12.2(25)EY or later.
A single-rate traffic policer decides on a packet-by-packet basis whether the packet is in or out of profile
and specifies the actions on the packet. These actions, carried out by the marker, include passing through
the packet without modification, dropping the packet, or modifying (marking down) the assigned DSCP
of the packet and allowing the packet to pass through. The configurable policed-DSCP map provides the
packet with a new DSCP-based QoS label. For information on the policed-DSCP map, see the “Mapping
Tables” section on page 34-17. Marked-down packets use the same queues as the original QoS label to
prevent packets in a flow from getting out of order.
Single-level policing uses a token-bucket algorithm. As each frame is received by the switch, a token is
added to the bucket. The bucket has a hole in it and leaks at a rate that you specify as the average traffic
rate in bps. Each time a token is added to the bucket, the switch verifies that there is enough room in the
bucket. If there is not enough room, the packet is marked as nonconforming, and the specified policer
action is taken (dropped or marked down).
How quickly the bucket fills is a function of the bucket depth (burst-byte), the rate at which the tokens
are removed (rate-bps), and the duration of the burst above the average rate. The size of the bucket
imposes an upper limit on the burst length and limits the number of frames that can be sent back-to-back.
If the burst is short, the bucket does not overflow, and no action is taken against the traffic flow. However,
if a burst is long and at a higher rate, the bucket overflows, and the policing actions are taken against the
frames in that burst.
You configure the bucket depth (the maximum burst that is tolerated before the bucket overflows) by
using the burst-byte option of the police policy-map class configuration command or the mls qos
aggregate-policer global configuration command. You configure how fast (the average rate) that the
tokens are removed from the bucket by using the rate-bps option of the police policy-map class
configuration command or the mls qos aggregate-policer global configuration command.
After you configure the policy map and policing actions, attach the ingress policy to a port by using the
service-policy input interface configuration command. For configuration information, see the
“Classifying, Policing, and Marking Ingress Traffic by Using Nonhierarchical Single-Level Policy
Maps” section on page 34-69 and the “Classifying, Policing, and Marking Ingress Traffic by Using
Aggregate Policers” section on page 34-79.
Figure 34-4 shows the policing and marking process when these types of policy maps are configured:
• A nonhierarchical single-level policy map.
• The interface level of a hierarchical dual-level policy map attached to an SVI. The physical ports are
specified in this secondary policy map.
Start
Is a policer configured No
for this packet?
Yes
Yes
Pass
through Check out-of-profile action Drop
Drop packet.
configured for this policer.
Mark
86835
Done
Note The VLAN level in a dual-level policy map is different than the VLAN level in a hierarchical
policy map that is applied on an ES port.
• Interface level—Create this secondary level by configuring class maps and classes that specify the
individual policers on physical ports the belong to the SVI. The interface-level policy map only
supports individual policers and does not support aggregate policers.
Note You cannot include ES ports in interface level class-map configuration for a policy attached to an SVI.
If you try to attach this type of service policy to an SVI, the command is rejected with an error message.
To configure enhanced per-port, per-VLAN policing for an ES port, you can attach a hierarchical policy
map to the port.
See the “Classifying, Policing, and Marking Traffic by Using Hierarchical Dual-Level Policy Maps”
section on page 34-73 for an example of a dual-level policy map.
Figure 34-5 shows the policing and marking process when hierarchical dual-level policy maps are
attached to an SVI.
Figure 34-5 Ingress Hierarchical Dual-Level Policing and Marking Flowchart on SVIs
Start
Is an interface-level policer No
configured for this packet?
Yes
Yes
Pass
through Verify the out-of-profile action Drop
Drop packet.
configured for this policer.
Mark
Done
Mapping Tables
During QoS ingress processing, the switch represents the priority of all traffic (including non-IP traffic)
with a QoS label based on the DSCP or CoS value from the classification stage:
• During ingress classification, QoS uses configurable mapping tables to derive a corresponding
DSCP or CoS value from a received CoS, DSCP, or IP precedence value. These maps include the
CoS-to-DSCP map and the IP-precedence-to-DSCP map. You configure these maps by using the mls
qos map cos-dscp and the mls qos map ip-prec-dscp global configuration commands.
On an ingress port configured in the DSCP-trusted state, if the DSCP values are different between
the QoS domains, you can apply the configurable DSCP-to-DSCP-mutation map to the port that is
on the boundary between the two QoS domains. You configure this map by using the mls qos map
dscp-mutation global configuration command.
• During ingress policing, QoS can assign another DSCP value to an IP or a non-IP packet (if the
packet is out of profile and the policer specifies a marked-down value). This configurable map is
called the policed-DSCP map. You configure this map by using the mls qos map policed-dscp
global configuration command.
• Before the traffic reaches the scheduling stage, QoS stores the packet in an ingress and an egress
queue according to the QoS label. The QoS label is based on the DSCP or the CoS value in the
inbound packet. The QoS label selects an ingress queue and an egress queue from the queue-set
through the DSCP input and output queue threshold maps or through the CoS input and output queue
threshold maps. In addition to an ingress or an egress queue, the QOS label also identifies the WTD
threshold value. You configure these maps by using the mls qos srr-queue {input | output}
dscp-map and the mls qos srr-queue {input | output} cos-map global configuration commands.
• When marking and queueing CPU-generated traffic:
– If you explicitly configure the output queue by entering the mls qos srr-queue output cpu-
queue global configuration command, the CPU traffic is sent to that queue, and the threshold
value applies to that queue.
– If you do not explicitly configure the output queue for CPU-generated traffic, the cpu marking
values and the dscp-map or cos-map values determine the output queue and the threshold for
the CPU-generated traffic.
The CoS-to-DSCP, DSCP-to-CoS, and the IP-precedence-to-DSCP maps have values that might or might
not be appropriate for your network.
The DSCP-to-DSCP-mutation map and the policed-DSCP map are null maps; they map an inbound
DSCP value to the same DSCP value. The DSCP-to-DSCP-mutation map is the only map that you apply
to a specific port. All other maps apply to the entire switch.
For configuration information, see the “Configuring DSCP Maps” section on page 34-80.
For information about the DSCP and CoS input queue threshold maps, see the “Queueing and
Scheduling of Ingress Queues” section on page 34-20. For information about the DSCP and CoS output
queue threshold maps, see the “Queueing and Scheduling of Egress Queue-Sets” section on page 34-22.
Traffic received
on an enhanced
services port Classify, Class-level CBWFQ, VLAN-level Physical-
police, queues LLQ, queues CBWFQ interface-
and mark or both level queue
Internal Egress
ring queue-set
Ingress
queues
Traffic sent to
Classify, a standard port
police, SRR SRR
Traffic received and mark
on a standard port
Traffic sent to
an enhanced
Classify, Class-level CBWFQ, VLAN-level Physical- services port
police, queues LLQ, queues CBWFQ interface-
and mark or both level queue
122039
Because the total ingress bandwidth of all ports can exceed the bandwidth of the internal ring, ingress
queues are located after the packet is classified, policed, and marked and before packets are forwarded
into the switch fabric. Because multiple ingress ports can simultaneously send packets to an egress port
and cause congestion, egress queue-sets are located after the internal ring.
Each port belongs to an egress queue-set, which defines all the characteristics of the four queues per port.
The ES ports also use a hierarchical queueing model in which each packet is assigned to a hierarchical
queue based on the physical interface, VLAN, or class. Traffic received from or destined for an ES port
passes through the queue-set. If congestion occurs in the hierarchical queues and backs up to the
queue-sets, the queue-set configuration controls how traffic is dropped.
Ingress queues use WTD for congestion management. The egress queue-sets also use WTD. For more
information, see the next section.
Ingress queues support SRR in shared mode for scheduling. The egress queue-sets also support SRR in
shared or shaped mode for scheduling. For more information, see the “SRR Shaping and Sharing”
section on page 34-19.
For information about ingress queueing and scheduling, see the “Queueing and Scheduling of Ingress
Queues” section on page 34-20. For information about egress queue-set queueing and scheduling, see
the “Queueing and Scheduling of Egress Queue-Sets” section on page 34-22.
The hierarchical queues for ES ports use tail drop or WRED for congestion management. These ports
also use CBWFQ or LLQ for scheduling. For more information, see the “Queueing and Scheduling of
Hierarchical Queues” section on page 34-37.
CoS 6-7
100% 1000
CoS 4-5
60% 600
CoS 0-3
40% 400
86692
For more information, see the “Mapping DSCP or CoS Values to an Ingress Queue and Setting WTD
Thresholds” section on page 34-87, the “Allocating Buffer Space to and Setting WTD Thresholds for an
Egress Queue-Set” section on page 34-91, and the “Mapping DSCP or CoS Values to an Egress
Queue-Set and to a Threshold ID” section on page 34-93.
In shared mode, the queues share the bandwidth among them according to the configured weights. The
bandwidth is guaranteed at this level but not limited to it. For example, if a queue is empty and no longer
requires a share of the link, the remaining queues can expand into the unused bandwidth and share it
among them. With sharing, the ratio of the weights controls the frequency of dequeuing; the absolute
values are meaningless. Shaping and sharing is configured per interface. Each interface can be uniquely
configured.
For more information, see the “Allocating Bandwidth Between the Ingress Queues” section on
page 34-89, the “Configuring SRR Shaped Weights on an Egress Queue-Set” section on page 34-95, and
the “Configuring SRR Shared Weights on an Egress Queue-Set” section on page 34-96.
Start
No Drop packet.
Queue the packet. Service
the queue according to
the SRR weights.
Send packet to
the internal ring.
90564
Note SRR services the priority queue for its configured share before servicing the other queue.
The switch supports two configurable ingress queues, which are serviced by SRR in shared mode only.
Table 34-2 describes the queues.
You assign each packet that flows through the switch to a queue and to a threshold. Specifically, you map
DSCP or CoS values to an ingress queue and map DSCP or CoS values to a threshold ID. You use the
mls qos srr-queue input dscp-map queue queue-id {dscp1...dscp8 | threshold threshold-id
dscp1...dscp8} or the mls qos srr-queue input cos-map queue queue-id {cos1...cos8 | threshold
threshold-id cos1...cos8} global configuration command. You can display the DSCP input queue
threshold map and the CoS input queue threshold map by using the show mls qos maps privileged EXEC
command. To specify the queue and threshold values for CPU-generated traffic, you use the mls qos
srr-queue output cpu queue id threshold id global configuration command.
WTD Thresholds
The queues use WTD to support distinct drop percentages for different traffic classes. Each queue has
three drop thresholds: two configurable (explicit) WTD thresholds and one nonconfigurable (implicit)
threshold preset to the queue-full state. You assign the two explicit WTD threshold percentages for
threshold ID 1 and ID 2 to the ingress queues by using the mls qos srr-queue input threshold queue-id
threshold-percentage1 threshold-percentage2 global configuration command. Each threshold value is a
percentage of the total number of allocated buffers for the queue. The drop threshold for threshold ID 3
is preset to the queue-full state, and you cannot modify it. For more information about how WTD works,
see the “Weighted Tail Drop” section on page 34-19.
You define the ratio (allocate the amount of space) with which to divide the ingress buffers between the
two queues by using the mls qos srr-queue input buffers percentage1 percentage2 global configuration
command. The buffer allocation together with the bandwidth allocation control how much data can be
buffered and sent before packets are dropped. You allocate bandwidth as a percentage by using the mls
qos srr-queue input bandwidth weight1 weight2 global configuration command. The ratio of the
weights is the ratio of the frequency in which the SRR scheduler sends packets from each queue to the
internal ring.
Priority Queueing
You can configure one ingress queue as the priority queue by using the mls qos srr-queue input
priority-queue queue-id bandwidth weight global configuration command. The priority queue should
be used for traffic (such as voice) that requires guaranteed delivery because this queue is guaranteed part
of the bandwidth regardless of the load on the internal ring.
SRR services the priority queue for its configured weight as specified by the bandwidth keyword in the
mls qos srr-queue input priority-queue queue-id bandwidth weight global configuration command.
Then, SRR shares the remaining bandwidth with both ingress queues and services them as specified by
the weights configured with the mls qos srr-queue input bandwidth weight1 weight2 global
configuration command.
You can combine the commands described in this section to prioritize traffic by placing packets with
particular DSCP or CoS values into certain queues, by allocating a large queue size or by servicing the
queue more frequently, and by adjusting queue thresholds so that packets with lower priorities are
dropped. For configuration information, see the “Configuring Ingress Queue Characteristics” section on
page 34-86.
Start
No
Drop packet.
Queue the packet. Service
the queue according to
the SRR weights.
Rewrite DSCP,
CoS, or both values,
as appropriate.
Done
Note If the egress priority queue is enabled on a port, SRR services it until it is empty. Then SRR services the
other queues.
Each port supports four egress queues, one (queue 1) of which can be the egress priority queue. These
queues are assigned to a queue-set. All traffic exiting the switch on a standard port flows through one of
these four queues and is subjected to a threshold based on the QoS label assigned to the packet. Traffic
destined for an ES port passes through the queue-set before reaching the hierarchical queues. If
congestion occurs in the hierarchical queues that backs up to the queue-sets, the queue-set configuration
controls how traffic is dropped.
Figure 34-10 shows the egress queue-set buffer. The buffer space is divided between the common pool
and the reserved pool. The switch uses a buffer allocation scheme to reserve a minimum amount of
buffers for each egress queue, to prevent any queue or port from consuming all the buffers and depriving
other queues, and to control whether to grant buffer space to a requesting queue. The switch detects
whether or not the target queue has consumed more buffers than its reserved amount (under-limit),
whether it has consumed all of its maximum buffers (over limit), and whether the common pool is empty
(no free buffers) or not empty (free buffers). If the queue is not over-limit, the switch can allocate buffer
space from the reserved pool or from the common pool (if it is not empty). If there are no free buffers in
the common pool or if the queue is over-limit, the switch drops the frame.
Common pool
Port 1 queue 1
Port 1 queue 2
Port 1 queue 3
Port 1 queue 4
Port 2 queue 1
Port 2 queue 2
Reserved pool
86695
Buffer and Memory Allocation
You guarantee the availability of buffers, set drop thresholds, and configure the maximum memory
allocation for a queue-set by using the mls qos queue-set output qset-id threshold queue-id
drop-threshold1 drop-threshold2 reserved-threshold maximum-threshold global configuration command.
Each threshold value is a percentage of the queue’s allocated memory, which you specify by using the
mls qos queue-set output qset-id buffers allocation1 ... allocation4 global configuration command.
The sum of all the allocated buffers represents the reserved pool, and the remaining buffers are part of
the common pool.
Through buffer allocation, you can ensure that high-priority traffic is buffered. For example, if the buffer
space is 400, you can allocate 70 percent of it to queue 1 and 10 percent to queues 2 through 4. Queue
1 then has 280 buffers allocated to it, and queues 2 through 4 each have 40 buffers allocated to them.
You can guarantee that the allocated buffers are reserved for a specific queue in a queue-set. For
example, if there are 100 buffers for a queue, you can reserve 50 percent (50 buffers). The switch returns
the remaining 50 buffers to the common pool. You also can enable a queue in the full condition to obtain
more buffers than are reserved for it by setting a maximum threshold. The switch can allocate the needed
buffers from the common pool if the common pool is not empty.
WTD Thresholds
You can assign each packet that flows through the switch to a queue and to a threshold. Specifically, you
map DSCP or CoS values to an egress queue-set and map DSCP or CoS values to a threshold ID. You
use the mls qos srr-queue output dscp-map queue queue-id {dscp1...dscp8 | threshold threshold-id
dscp1...dscp8} or the mls qos srr-queue output cos-map queue queue-id {cos1...cos8 | threshold
threshold-id cos1...cos8} global configuration command. You can display the DSCP output queue
threshold map and the CoS output queue threshold map by using the show mls qos maps privileged
EXEC command. To specify the queue and threshold values for CPU-generated traffic, you use the mls
qos srr-queue output cpu queue id threshold id global configuration command.
The queue-set uses WTD to support distinct drop percentages for different traffic classes. Each queue
has three drop thresholds: two configurable (explicit) WTD thresholds and one nonconfigurable
(implicit) threshold preset to the queue-full state. You assign the two WTD threshold percentages for
threshold ID 1 and ID 2. The drop threshold for threshold ID 3 is preset to the queue-full state, and you
cannot modify it. For more information about how WTD works, see the “Weighted Tail Drop” section
on page 34-19.
SRR services each queue-set in shared or shaped mode.You map a port to a queue-set by using the
queue-set qset-id interface configuration command. You assign shared or shaped weights to a standard
port by using the srr-queue bandwidth share weight1 weight2 weight3 weight4 or the srr-queue
bandwidth shape weight1 weight2 weight3 weight4 interface configuration command. You can assign
only shared weights to an ES port. For an explanation of the differences between shaping and sharing,
see the “SRR Shaping and Sharing” section on page 34-19.
The buffer allocation together with the SRR weight ratios control how much data can be buffered and
sent before packets are dropped. The weight ratio is the ratio of the frequency in which the SRR
scheduler sends packets from each queue.
All four queues participate in the SRR unless the egress priority queue is enabled, in which case the first
bandwidth weight is ignored and is not used in the ratio calculation. Before servicing the other queues,
SRR services the priority queue until it is empty. You enable the priority queue by using the
priority-queue out interface configuration command.
You can combine the commands described in this section to prioritize traffic by placing packets with
particular DSCP or CoS values into certain queues, by allocating a large queue size or by servicing the
queue more frequently, and by adjusting queue thresholds so that packets with lower priorities are
dropped. For configuration information, see the “Configuring Egress Queue-Set Characteristics” section
on page 34-91.
Note The egress queue-set settings are suitable for most situations. You should change them only when you
have a thorough understanding of the queues and only if these settings do not meet your QoS solution.
Cisco IP-SLAs
For information about Cisco IP service level agreements (IP SLAs), see the “Understanding Cisco IOS
IP SLAs” section on page 41-1.
Marking
By default, the class of service (CoS) marking of CFM traffic (including IP SLAs using CFM probes) is
not changed. This feature cannot change this behavior.
By default, the class of service (CoS) marking of all other Layer 2 non-IP traffic is not changed. The
QoS marking feature can change this behavior.
By default, IP traffic marking (including IP SLA and TWAMP probes) is not changed. The QoS marking
feature can change this behavior.
Queuing
The CFM traffic (including IP SLAs using CFM probes) is queued according to its CoS value and the
output policy map configured on the egress port, similar to normal traffic. This feature cannot change
this behavior.
By default, all other Layer 2 non-IP traffic is statically mapped to a queue on the egress port. However,
this feature can change the queuing behavior. This traffic can be queued according to the CoS markings
specified in the cpu traffic qos global configuration command and the global CoS-to-queue mapping.
By default, all IP traffic (including IP SLA and TWAMP probes) is statically mapped to a queue on the
egress port. However, this feature can change the queuing behavior. All IP traffic can be queued
according to the CoS or DSCP or precedence markings specified in the cpu traffic qos global
configuration command and the corresponding global CoS- or DSCP- or precedence-to-queue mapping.
Note This feature enhances the MLS QoS marking and queuing capability for CPU traffic. It does not affect
the marking and queuing capability availability through output MQC QoS policy-maps configured on
enhanced services (ES) ports.
Note To configure QoS marking, you must first enable multilayer switch (MLS) QoS by using the mls qos
global configuration command.
When MLS QoS is disabled, the default behavior applies for all CPU traffic; QoS marking commands
are accepted by the switch and become effective when MLS QoS is enabled.
You can specify and mark traffic CPU-generated traffic by using these global configuration commands:
• cpu traffic qos cos {cos_value | trust}
• cpu traffic qos dscp {dscp_value | trust | dscp-mutation mutation-map-name}
• cpu traffic qos precedence {precedence_value | trust | precedence-mutation
mutation-map-name}
For non-IP, non-CFM CPU traffic, you have these marking options:
• Use the cpu traffic qos cos global configuration command with the cos_value argument to configure
a CoS value.
• Use the cpu traffic qos cos global configuration command with the trust keyword to trust the CoS
value in the inbound frame and use the configurable CoS-to-DSCP map to generate a DSCP value
for the packet.
Note Configuring a DSCP or precedence value or trusting the DSCP or precedence value in the inbound frame
has no impact on non-IP traffic.
• Use the cpu traffic qos precedence global configuration command with the trust keyword to trust
the precedence value in the inbound frame, use the configurable IP-precedence-to-DSCP map to
generate a DSCP value, and use the configurable DSCP-to-CoS map to generate a CoS value for the
packet.
• Use the cpu traffic qos precedence global configuration command with the precedence-mutation
keyword and the mutation-map-name argument to change the precedence value of the inbound
frame. Use the IP-precedence-to-DSCP map to generate a DSCP value from the precedence value,
and then use the configured DSCP mutation-map to generate the changed DSCP value. Use the
configurable DSCP-to-CoS map to generate a CoS value for the packet.
• Use the cpu traffic qos dscp global configuration command with the trust keyword to trust the
DSCP value in the inbound frame. Then use the configurable DSCP-to-queue or DSCP-to-threshold
map to select the queue or threshold for the packet.
• Use the cpu traffic qos dscp global configuration command with the dscp-mutation keyword and
mutation-map-name argument to change the DSCP value of the inbound frame. Then use the
configurable DSCP-to-queue or DSCP-to-threshold map to select the queue or threshold for the
packet.
• Use the cpu traffic qos precedence global configuration command with the precedence_value
argument to configure the precedence value. Then use the configurable DSCP-to-queue or
DSCP-to-threshold map to select the queue or threshold for the packet.
• Use the cpu traffic qos precedence global configuration command with the trust keyword to trust
the precedence value in the inbound frame. Then use the configurable IP-precedence-to-DSCP map
to generate a DSCP value. Use the configurable DSCP-to-queue or DSCP-to-threshold map to select
the queue or threshold for the packet.
• Use the cpu traffic qos precedence global configuration command with the precedence-mutation
keyword and the mutation-map-name argument to change the precedence value of the inbound
frame. Use the IP-precedence-to-DSCP map to generate a DSCP value from the precedence value.
Then use the configured DSCP mutation-map to generate the changed DSCP value. Then use the
configurable DSCP-to-queue or DSCP-to-threshold map to select the queue or threshold for the
packet.
Configuration Guidelines
• This feature must be configured globally for a switch; it cannot be configured per-port or
per-protocol.
• Enter each cpu traffic qos marking action on a separate line.
• The trust keyword configures the switch to trust the incoming CoS, DSCP, or precedence value and
marks the packet according to the global map configuration.
• The mutation keyword configures the switch to change the incoming value according to the global
mutation-map configuration.
• When you configure the switch to trust CoS, the configuration applies to both IP and non-IP traffic.
• When you configure the switch to trust or change DSCP or precedence but not CoS, the
configuration applies only to IP traffic.
• When you configure the switch to trust CoS and trust or change DSCP or precedence, trust CoS
applies to non-IP traffic and trust or change DSCP or precedence applies to IP traffic.
• The cpu traffic qos cos global configuration command configures CoS marking for CPU-generated
traffic by either trusting CoS or specifying a CoS value, but not both. A new configuration
overwrites the existing configuration.
• The cpu traffic qos dscp global configuration command configures DSCP marking for
CPU-generated traffic by trusting DSCP, mutating DSCP, or specifying a DSCP value. A new
configuration overwrites the existing configuration.
• The cpu traffic qos precedence global configuration command configures precedence marking for
CPU-generated traffic by trusting precedence, mutating precedence, or specifying a precedence
value. A new configuration overwrites the existing configuration.
• The cpu traffic qos dscp and cpu traffic qos precedence global configuration commands are
mutually exclusive. A new configuration overwrites the existing configuration.
Note The mls qos srr-queue output cpu-queue global configuration command overrides all of the above
queue mapping configuration options.
Hierarchical Levels
Hierarchical QoS configuration involves traffic classification, policing, queueing, and scheduling. You
can create a hierarchy by associating a class-level policy map with a VLAN-level policy map, by
associating that VLAN-level policy map with a physical-level policy map, and by attaching the
physical-level policy map to an ES port. You can omit hierarchical levels, but the order of the levels
(class level, VLAN level, and then the physical level) must be preserved.
You can configure these three QoS levels in the hierarchy:
• Class level—You configure this level of the hierarchy by matching CoS, DSCP, IP precedence, or
MPLS EXP bits in the outbound packet through the match {cos [inner] cos-list | dscp dscp-list | ip
precedence ip-precedence-list | mpls experimental exp-list} class-map configuration command. At
the class level, you can:
– Configure policer drops by using the police cir or police cir percent policy-map class
configuration command.
– Configure tail drop or WRED drop policies by using the queue-limit or the random-detect
policy-map class configuration command.
– Modify the traffic class by setting Layer 2 and Layer 3 QoS fields through the set {cos new-cos
| dscp new-dscp | precedence new-precedence | mpls experimental exp-number} policy-map
class configuration command.
– Configure CBWFQ or LLQ scheduling by using the bandwidth or the priority policy-map
class configuration command.
– Configure traffic shaping by using the shape policy-map class configuration command.
The switch supports eight classes (including the class) per policy map at this level. The class is
reserved for packets that do not meet any of the matching criteria.
This is an example of a class-level classification and its naming convention:
Switch(config)# class-map match-any class-level-class-map-name
Switch(config-cmap)# match ip dscp 10 11 12
• VLAN level—You start configuration of per-VLAN QoS by entering the match vlan vlan-id
class-map configuration command on one or more VLANs or by entering the match vlan vlan-id
and the match vlan inner vlan-id class-map configuration command on one or more 802.1Q
tunnels. At this level, you can configure the VLANs or 802.1Q tunnels to police, to share the
available port bandwidth and to enable CBWFQ, and to shape the traffic. You configure these
features by using the police cir, police cir percent, bandwidth, and shape policy-map class
configuration commands.
For a finer level of control, you can associate a previously defined child policy at the class level with
a new service policy by using the service-policy policy-map class configuration command. In the
class-level child policy, you can configure tail drop or WRED drop policies, set Layer 2 and Layer
3 QoS fields, or enable the strict-priority queue. These features are available only at the class level.
By using a child policy, you apply a class-level policy only to traffic that matches the VLAN class.
You cannot mix VLAN-level and class-level matches within a class map.
You can attach up to 2045 user-created VLAN-level classes. This means that you can have 1022
unique classes and can associate them with the two ES ports (and have one left over), or you can add
more classes to one ES port and can subtract from the other one. You can shape every class that you
configure. You can create up to 4093 class maps.
This is an example of a VLAN-level classification and its naming convention:
Switch(config)# class-map match-all vlan-level-class-map-name
Switch(config-cmap)# match vlan 5
Switch(config-cmap)# match vlan inner 3 - 8
This is an example of a VLAN-level policy map and its naming convention when a previously
defined child policy is associated at the class level:
Switch(config)# policy-map vlan-level-policy-map-name
Switch(config-pmap)# class vlan-level-class-name
Switch(config-pmap-c)# bandwidth percent 30
Switch(config-pmap-c)# service-policy class-level-policy-map-name
This is an example of a VLAN-level policy map that combines a VLAN-level classification with a
VLAN-level policy map and associates a previously defined child policy at the class level:
Switch(config)# class-map cls-class
Switch(config-cmap)# match mpls experimental 2
Switch(config-cmap)# exit
Switch(config)# class-map log-class
Switch(config-cmap)# match vlan 203
Switch(config-cmap)# exit
Switch(config)# policy-map cls-policy
Switch(config-pmap)# class cls-class
Switch(config-pmap-c)# set mpls experimental 5
Switch(config-pmap-c)# exit
Switch(config-pmap)# exit
Switch(config)# policy-map log-policy
Switch(config-pmap)# class log-class
Switch(config-pmap-c)# service-policy cls-policy
Switch(config-pmap-c)# exit
Switch(config-pmap)# exit
Switch(config)# interface gigabitethernet1/1/2
Switch(config-if)# switchport trunk encapsulation dot1q
Switch(config-if)# switchport mode trunk
Switch(config-if)# service-policy output log-policy
• Physical level—You can shape or police only the class-default class at the physical level of the
hierarchy by using the shape, police cir, or police cir percent policy-map class configuration
command.
Within a policy map, the class-default applies to all traffic that is not explicitly matched within the
policy map but does match the parent policy. If no parent policy is configured, the parent policy
represents the physical port. In a physical-level policy map, class-default is the only class that you
can configure.
You use the service-policy {input | output} policy-map-name interface configuration command to
attach a hierarchical policy to an ES port.
This is an example of a physical-level configuration. All hierarchical levels exist, and the order is
preserved. The class level at the bottom, the VLAN level in the middle, and the physical level at the
top.
you specify class-default as the class name in the class policy-map configuration command, packets that
fail to meet any of the matching criteria are classified as members of the traffic class. You can manipulate
this class (for example, police it and mark it) just like any traffic class, but you cannot delete it.
Within a policy map, the class-default designates all traffic that is not explicitly matched within the
policy map but does match the policy map of the parent policy. If no parent policy is configured, the
parent policy represents the physical port. In the physical-level policy map, class-default is the only class
that can be configured.
After you name the traffic class with the class command, the switch enters policy-map class
configuration mode, and you can specify the actions to take on this traffic class.
You attach a hierarchical policy map to an ES port by using the service-policy [input | output]
policy-map-name interface configuration command. The policy map can include the bandwidth, police
cir, police cir percent, priority, queue-limit, random-detect, shape, or set policy-map class
configuration commands. If the policy map contains the class-default class, you can configure settings
only through the police cir, police cir percent, and shape commands.
For more information, see the “Hierarchical Policies and Marking” section on page 34-34 and the
“Queueing and Scheduling of Hierarchical Queues” section on page 34-37.
PIR CIR
Is packet Is packet
size of B larger No size of B larger No
than number of tokens than number of tokens
Packet of size B available in PIR available in CIR
bucket? bucket?
Yes Yes
98723
Action Action Action
You configure the CIR and PIR rates in bps (or as a percentage of the bandwidth available on an ES port),
and these rates control how fast the bucket fills (is updated) with tokens. The conform burst size (bc) and
the peak burst size (be) represent the depth of the CIR and PIR buckets in bytes. This depth limits the
number of tokens that the bucket can accumulate. If the bucket fills to capacity, newly arriving tokens
are discarded.
Each token is permission for the source to send a certain number of bits into the network. To send a
packet, the number of tokens equal to the packet size must be drained from the bucket. If there are
enough tokens in the bucket, the packet conforms and can pass to the next stage. Otherwise, the exceed
action associated with the bucket is applied to the packet. The packet might be dropped, or its priority
value might be marked down.
In this token-bucket example, if the CIR rate is 2 kb/s, 2000 tokens are added to the bucket every second
(for this example, consider each token to represent a single bit of information). If a 1500-byte packet
arrives, 12000 tokens (1500 bytes x 8 bits per byte) must be in the bucket for the packet to pass to the
next state without triggering the exceed action. If enough tokens are in the bucket, they are drained, and
the packet conforms and passes to the next stage. If there are less than 12000 tokens in the bucket, the
exceed action is applied to the packet. The deeper the bucket, the more data can burst through at a rate
greater than the rate at which the bucket is filling. For example, if the CIR bucket holds 6000 tokens, 750
bytes of traffic can instantaneously burst without draining the bucket (and without triggering an exceed
action), even though the instantaneous burst is at a greater rate than the CIR rate of 2000 bps.
If the burst sizes approach the system maximum transmission unit (MTU), the policer strictly enforces the
CIR and PIR. Normal traffic jitter can cause some percentage of inbound traffic to be flagged as
nonconforming even if the average inbound rate appears to conform. If the burst size is very large, on the other
hand, large traffic bursts at nonconforming data rates can be passed through the policer and flagged as
conforming. Setting the burst sizes too low can result in less traffic than expected and setting them too
high can result in more traffic than expected.
For packet marking actions, if the CIR is 100 kb/s, the PIR is 200 kb/s, and a data stream with a rate of
250 kb/s arrives at the two-rate policer:
• 100 kb/s is marked as conforming to the rate.
• 100 kb/s is marked as exceeding the rate.
• 50 kb/s is marked as violating the rate.
If you set the CIR equal to the PIR, a traffic rate that is less than the CIR or that meets the CIR is in the
conform range. Traffic that exceeds the CIR rate is in the violate range.
If you set the PIR greater than the CIR, a traffic rate less than the CIR is in the conform range. A traffic
rate that exceeds the CIR but is less than or equal to the PIR is in the exceed range. A traffic rate that
exceeds the PIR is in the violate range.
After you configure the policy map and policing actions, attach the policy to an ES port by using the
service-policy {input | output} policy-map-name interface configuration command. For configuration
information, see the “Configuring Hierarchical QoS” section on page 34-103.
An input hierarchical service policy can contain the same configuration options as an output hierarchical
service policy (policing, shaping, CBWFQ), but cannot include configurations such as ACLs or
aggregate policers. Access group matches are allowed on ES ports if the policy is non-hierarchical.
Violating this rule prevents the policy from being attached to an interface.
Start
No
Drop packet.
Queue the packet.
Service the queue
according to the
CBWFQ, LLQ, or both.
Continue ingress
processing or send
packet out the ES port.
122040
Done
Hierarchical Queues
The switch uses a hierarchical queueing model for traffic received on or sent from an ES port. Each
packet is assigned a queue based on its physical interface, VLAN, or class:
• At the class level, a packet is queued to one of four queues according to its CoS, DSCP, IP
precedence, or MPLS EXP classification. Packets can be classified by any combination of these
values, but if a packet matches more than one, the classification occurs in the order listed. The last
queue in each set of four queues is reserved as the default queue. Packets that are not classified into
one of the other three queues are assigned to the default queue. You can configure traffic in the queue
with congestion-avoidance features and scheduling congestion-management features as described in
the “Queueing and Scheduling of Hierarchical Queues” section on page 34-37.
• At the VLAN level, the switch supports 2045 VLAN classes divided between the two ES ports. One
queue is reserved as the default queue. Packets that are not classified into one of the other VLAN
queues are assigned to the default queue. You can configure traffic in the default queue with
congestion-avoidance features and scheduling congestion-management features as described in the
“Queueing and Scheduling of Hierarchical Queues” section on page 34-37.
• At the physical level, the switch reserves one queue per port.
The switch creates the queue and uses it to send all traffic when a service policy is not attached to an ES
port. User traffic on a physical port without an attached service policy bypasses the QoS classification
and is queued to the default queue. The minimum and maximum bandwidth for the default queue is the
same as the port bandwidth.
Under congested conditions, the switch discards packets for all classes configured for the same sending
queue with equal probability. To achieve the full queueing capacity, there must be an equal division of
traffic among the classes for each sending queue.
Tail Drop
With tail drop, packets are queued for the class until the maximum threshold is exceeded, and then all
the packets destined for the class queue are dropped. You enable tail drop at the class level by using the
queue-limit policy-map class configuration command. For configuration information, see the
“Configuring a Hierarchical QoS Policy” section on page 34-107.
WRED
Cisco Systems implements a version of Random Early Detection (RED), called WRED, differently from
other congestion-avoidance techniques. WRED attempts to anticipate and avoid congestion, rather than
controlling congestion when it occurs. WRED takes advantage of the TCP congestion control to try to
control the average queue size by signaling end hosts when they should temporarily stop sending
packets. By randomly dropping packets before periods of high congestion, it tells the packet source to
decrease its sending rate. Assuming the packet source is using TCP, WRED tells it to decrease its sending
rate until all the packets reach their destination, meaning that the congestion is cleared. By dropping
some packets early rather than waiting until the queue is full, WRED avoids dropping large numbers of
packets at once.
When a packet arrives and WRED is enabled, these events occur:
• The average queue size is calculated based on the previous average and the current size of the queue.
The average queue-size calculation is affected by the exponential weight constant setting in the
random-detect exponential-weight-constant policy-map class configuration command.
• If the average queue size is less than the minimum queue threshold, the arriving packet is queued.
The minimum queue threshold is configured through the min-threshold option in the random-detect
{dscp | precedence} policy-map class configuration command.
• If the average queue size is between the minimum queue threshold and the maximum queue
threshold, the packet is either dropped or queued, depending on the packet-drop probability. The
packet-drop probability is based on the minimum threshold, the maximum threshold, and the
mark-probability denominator. The maximum queue threshold is configured through the
max-threshold option, and the mark-probability denominator is configured through the
mark-prob-denominator option in the random-detect dscp {dscp | precedence} policy-map class
configuration command.
• If the average queue size is greater than the maximum queue threshold, the packet is automatically
dropped.
You enable WRED by using the random-detect policy-map class configuration command at the class
level. This command allows for preferential drop treatment among packets with different IP precedence
or DSCP values. The WRED algorithm discards or marks packets destined for a queue when that queue
is congested. It discards packets fairly and before the queue is full. Packets with high IP-precedence
values are preferred over packets with low IP-precedence values. For configuration information, see the
“Configuring a Hierarchical QoS Policy” section on page 34-107.
CBWFQ
CBWFQ provides guaranteed bandwidth to particular traffic classes, such as voice, that are delay
sensitive, while still fairly serving all other traffic in the network. You define traffic classes based on
match criteria. Packets satisfying the match criteria for a class constitute the traffic for that class. A
queue is reserved for each class, and traffic belonging to a class is directed to the queue for that class.
The bandwidth assigned to a class is the minimum bandwidth that is delivered to the class during
congestion. CBWFQ uses the bandwidth weight to ensure that the queue for the class is serviced fairly.
You enable CBWFQ and specify the minimum bandwidth as a rate in kb/s or as a percentage of the
available bandwidth by using the bandwidth policy-map class configuration command at the class level
or at the VLAN level. During periods of congestion, the classes are serviced in proportion to their
configured bandwidth. The amount of bandwidth available to a class is dependent on the amount of
bandwidth reserved by the parent class. For configuration information, see the “Configuring a
Hierarchical QoS Policy” section on page 34-107.
LLQ
LLQ provides strict-priority queueing for a traffic class. It enables delay-sensitive data, such as voice,
to be sent before packets in other queues are sent. The priority queue is serviced first until it is empty.
Only one traffic stream can be destined for the priority queue per class-level policy. The priority queue
restricts all traffic streams in the same hierarchy, and you should use care when configuring this feature.
You enable the priority queue for a traffic class by using the priority policy-map class configuration
command at the class level. For configuration information, see the “Configuring a Hierarchical QoS
Policy” section on page 34-107.
With Cisco IOS Release 12.1(14)AX2, you can use LLQ and the egress priority queue (enabled with the
priority-queue out interface configuration command) to give priority to a class of traffic and to avoid a
loss of traffic when the switch is congested. In previous releases (before the egress priority queue was
supported), you could put a traffic class into the strict-priority queue, but congestion at the egress
queue-sets could result in the dropping of that priority traffic. You can use the priority-queue out
interface configuration command to prioritize the same traffic class at the egress queue-sets, ensuring
that priority traffic reaches the hierarchical queues and is processed with priority.
Shaping
Shaping provides a process for delaying out-of-profile packets in queues so that they conform to a
specified profile. Shaping is distinct from policing. Policing drops packets that exceed a configured
threshold, but shaping buffers packets so that traffic remains within a threshold. Shaping offers greater
smoothness in handling traffic than policing. You enable average-rate traffic shaping on a traffic class
by using the shape policy-map class configuration command at the class level or at the VLAN level. At
the physical level of the hierarchy, you can shape only the class-default class by using the shape
policy-map class configuration command in a policy attached to an ES port. For configuration
information, see the “Configuring a Hierarchical QoS Policy” section on page 34-107.
Configuring Auto-QoS
You can use the auto-QoS feature to simplify the deployment of existing QoS features. Auto-QoS makes
assumptions about the network design, and as a result, the switch can prioritize different traffic flows
and appropriately use the ingress and egress queues instead of using the QoS behavior. The default is
that QoS is disabled. The switch then offers best-effort service to each packet, regardless of the packet
contents or size, and sends it from a single queue.)
When you enable auto-QoS, it automatically classifies traffic based on the traffic type and ingress packet
label. The switch uses the resulting classification to choose the appropriate egress queue.
You use auto-QoS commands to identify ports connected to Cisco IP Phones and to devices running the
Cisco SoftPhone application. You also use the commands to identify ports that receive trusted traffic
through an uplink. Auto-QoS then performs these functions:
• Detects the presence or absence of IP phones
• Configures QoS classification
• Configures egress queues
These sections describe how to configure auto-QoS on your switch:
• Generated Auto-QoS Configuration, page 34-41
• Effects of Auto-QoS on the Configuration, page 34-45
• Auto-QoS Configuration Guidelines, page 34-45
• Upgrading from a Previous Software Release, page 34-46
• Enabling Auto-QoS for VoIP, page 34-46
• Auto-QoS Configuration Example, page 34-48
Table 34-4 shows the generated auto-QoS configuration for the ingress queues.
Table 34-5 shows the generated auto-QoS configuration for the egress queue-set.
Queue Number
in the Queue Weight Queue (Buffer)
Egress Queue Queue-Set CoS-to-Queue Map (Bandwidth) Size
Priority (shaped) 1 5 10 percent 10 percent
SRR shared 2 3, 6, 7 10 percent 10 percent
SRR shared 3 2, 4 60 percent 26 percent
SRR shared 4 0, 1 20 percent 54 percent
Note You must enable QoS by entering the mls qos global configuration command before configuring the QoS
parameters for CPU-generated traffic. Otherwise, the CPU traffic QoS command configurations are not
applied. To configure the QoS parameters, use the cpu traffic qos global configuration command.
When you enable the auto-QoS feature on the first port, these automatic actions occur:
• QoS is globally enabled (mls qos global configuration command), and other global configuration
commands are added.
• When you enter the auto qos voip cisco-phone interface configuration command on a port at the
edge of the network that is connected to a Cisco IP phone, the switch enables the trusted boundary
feature. The switch uses the Cisco Discovery Protocol (CDP) to detect the presence or absence of a
Cisco IP Phone. When a Cisco IP Phone is detected, the ingress classification on the port is set to
trust the QoS label received in the packet. When a Cisco IP Phone is absent, the ingress classification
is set to not trust the QoS label in the packet. The switch configures ingress queues and the egress
queue-set on the port according to the settings in Table 34-4 and Table 34-5.
• When you enter the auto qos voip cisco-softphone interface configuration command on a port at
the edge of the network that is connected to a device running the Cisco SoftPhone, the switch uses
policing to determine whether a packet is in or out of profile and to specify the action on the packet.
If the packet does not have a DSCP value of 24, 26, or 46 or is out of profile, the switch changes the
DSCP value to 0. The switch configures ingress and egress queues on the port according to the
settings in Table 34-4 and Table 34-5.
• When you enter the auto qos voip trust interface configuration command on a port connected to the
interior of the network, the switch trusts the CoS value for nonrouted ports or the DSCP value for
routed ports in ingress packets (the assumption is that traffic has already been classified by other
edge devices). The switch configures the ingress queues and the egress queue-set on the port
according to the settings in Table 34-4 and Table 34-5.
For information about the trusted boundary feature, see the “Configuring a Trusted Boundary to
Ensure Port Security” section on page 34-60.
When you enable auto-QoS by using the auto qos voip cisco-phone, the auto qos voip cisco-softphone,
or the auto qos voip trust interface configuration command, the switch automatically generates a QoS
configuration based on the traffic type and the ingress packet label and applies the commands listed in
Table 34-6 to the port.
Note On an ES port, the srr-queue bandwidth shape interface configuration command is not part of the
generated auto qos voip command list.
Note When a device running Cisco SoftPhone is connected to a nonrouted or routed port, the
switch supports only one Cisco SoftPhone application per port.
• To take advantage of the auto-QoS s, you should enable auto-QoS before you configure other QoS
commands. If necessary, you can fine-tune the QoS configuration, but we recommend that you do
so only after the auto-QoS configuration is completed. For more information, see the “Effects of
Auto-QoS on the Configuration” section on page 34-45.
• After auto-QoS is enabled, do not modify a policy map or aggregate policer that includes AutoQoS
in its name. If you need to modify the policy map or aggregate policer, make a copy of it, and change
the copied policy map or policer. To use this new policy map instead of the generated one, remove
the generated policy map from the interface, and apply the new policy map to the interface.
• You can enable auto-QoS on static, dynamic-access, voice VLAN access, and trunk ports.
• By default, the CDP is enabled on all ports. For auto-QoS to function properly, do not disable the
CDP.
• When enabling auto-QoS with a Cisco IP Phone on a routed port, you must assign a static IP address
to the IP phone.
• This release supports only Cisco IP SoftPhone Version 1.3(3) or later.
• Connected devices must use Cisco Call Manager Version 4 or later.
• You can manually enable policing, as described in the “Configuring an Ingress QoS Policy” section
on page 34-63.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the port that is connected to a Cisco IP Phone or the uplink
port that is connected to another switch or router in the interior of the
network, and enter interface configuration mode.
Command Purpose
Step 3 auto qos voip {cisco-phone | Enable auto-QoS.
cisco-softphone | trust}
The keywords have these meanings:
• cisco-phone—If the port is connected to a Cisco IP Phone, the
QoS labels of inbound packets are trusted only when the
telephone is detected.
• cisco-softphone—The port is connected to device running the
Cisco SoftPhone feature.
• trust—The uplink port is connected to a trusted switch or router,
and the VoIP traffic classification in the ingress packet is trusted.
Step 4 end Return to privileged EXEC mode.
Step 5 show auto qos interface interface-id Verify your entries.
This command displays the initial auto-QoS configuration that was
applied; it does not display any user changes to the configuration that
might be in effect. You can use the show running-config privileged
EXEC command to display the auto-QoS configuration and the user
modifications.
To display the QoS commands that are automatically generated when auto-QoS is enabled or disabled,
enter the debug autoqos privileged EXEC command before enabling auto-QoS. For more information,
see the “debug autoqos” command in the command reference for this release.
To disable auto-QoS on a port, use the no auto qos voip interface configuration command. Only the
auto-QoS-generated interface configuration commands for this port are removed. If this is the last port
on which auto-QoS is enabled and you enter the no auto qos voip command, auto-QoS is considered
disabled even though the auto-QoS-generated global configuration commands remain (to avoid
disrupting traffic on other ports affected by the global configuration). You can use the no mls qos global
configuration command to disable the auto-QoS-generated global configuration commands. With QoS
disabled, there is no concept of trusted or untrusted ports because the packets are not modified (the CoS,
DSCP, and IP precedence values in the packet are not changed). Traffic is switched in pass-through mode
(packets are switched without any rewrites and classified as best effort without any policing).
This example shows how to enable auto-QoS on a port and to trust the QoS labels received in inbound
packets when the switch or router connected to a port is a trusted device:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# auto qos voip trust
Cisco router
To Internet
Trunk Trunk
link link Video server
172.20.10.16
End stations
IP IP
Figure 34-13 shows a network in which the VoIP traffic is prioritized over all other traffic. Auto-QoS is
enabled on the switches in the wiring closets at the edge of the QoS domains.
Note You should not configure any standard QoS commands before entering the auto-QoS commands. You
can fine-tune the QoS configuration, but we recommend that you do so only after the auto-QoS
configuration is completed.
Beginning in privileged EXEC mode, follow these steps to configure the switch at the edge of the QoS
domain to prioritize the VoIP traffic over all other traffic:
Command Purpose
Step 1 debug auto qos Enable debugging for auto-QoS. When debugging is enabled, the
switch displays the QoS configuration that is automatically
generated when auto-QoS is enabled.
Step 2 configure terminal Enter global configuration mode.
Step 3 cdp enable Enable CDP globally. By default, it is enabled.
Step 4 interface interface-id Specify the switch port connected to the Cisco IP Phone, and enter
interface configuration mode.
Step 5 auto qos voip cisco-phone Enable auto-QoS on the port, and specify that the port is connected
to a Cisco IP Phone.
The QoS labels of inbound packets are trusted only when the Cisco
IP Phone is detected.
Step 6 exit Return to global configuration mode.
Step 7 Repeat Steps 4 to 6 for as many ports as are connected to the Cisco
IP Phone.
Step 8 auto qos voip cisco-phone Enable auto-QoS on the port, and specify that the port is connected
to a Cisco IP Phone.
Step 9 exit Return to global configuration mode.
Step 10 interface interface-id Specify the port identified as connected to a trusted switch or
router. See Figure 34-13. Enter interface configuration mode.
Step 11 auto qos voip trust Enable auto-QoS on the port, and specify that the port is connected
to a trusted router or switch.
Step 12 end Return to privileged EXEC mode.
Step 13 show auto qos Verify your entries.
This command displays the auto-QoS configuration that is initially
applied; it does not display any user changes to the configuration
that might be in effect.
For information about the QoS configuration that might be
affected by auto-QoS, see the “Displaying Auto-QoS Information”
section on page 26-12.
Step 14 copy running-config Save the auto qos voip interface configuration commands and the
startup-config generated auto-QoS configuration in the configuration file.
To display information about the QoS configuration that might be affected by auto-QoS, use one of these
commands:
• show cpu traffic qos
• show mls qos
• show mls qos maps cos-dscp
• show mls qos interface [interface-id] [buffers | queueing]
• show mls qos maps [cos-dscp | cos-input-q | cos-output-q | dscp-cos | dscp-input-q |
dscp-output-q]
• show mls qos input-queue
• show running-config
For more information about these commands, see the command reference for this release.
When QoS is enabled with the mls qos global configuration command and all other QoS settings are at
their s, traffic is classified as best effort (the DSCP and CoS value is set to 0) without any policing. No
policy maps are configured. The port trust state on all ports is untrusted. The ingress queues and egress
queue-set settings are described in the “Ingress Queue Configuration” section on page 34-51 and the
“Egress Queue-Set Configuration” section on page 34-52. For traffic on an ES port, see the “Hierarchical
QoS Configuration” section on page 34-103.
Table 34-8 shows the CoS input queue threshold map when QoS is enabled.
Table 34-9 shows the DSCP input queue threshold map when QoS is enabled.
Table 34-11 shows the CoS output queue threshold map when QoS is enabled.
Table 34-12 shows the DSCP output queue threshold map when QoS is enabled.
mapping, and queueing on the individual physical ports that comprise the EtherChannel. Beginning
with Cisco IOS Release 12.2(35)SE, the switch supports EtherChannels made of ES ports for
single-level output policy maps and hierarchical policy maps in both directions.
• Control traffic (such as spanning-tree bridge protocol data units [BPDUs] and routing update
packets) received by the switch are subject to all ingress QoS processing.
• You are likely to lose data when you change queue settings; therefore, try to make changes when
traffic is at a minimum.
• Follow these guidelines when the egress priority queue is enabled on a port; otherwise, the egress
queues are serviced based on their SRR weights:
– If the egress priority queue is enabled, it overrides the SRR shaped and shared weights for
queue 1.
– If the egress priority queue is disabled and the SRR shaped and shared weights are configured,
the shaped mode overrides the shared mode for queue 1, and SRR services this queue in shaped
mode.
– If the egress priority queue is disabled and the SRR shaped weights are not configured, SRR
services this queue in shared mode.
• In Cisco IOS Release 12.2(44)SE or later, if the mls qos global configuration command is disabled
and you do not explicitly configure the cpu traffic qos global configuration command, the switch
uses the default behavior. The default is no marking for CPU-generated traffic and all packets
queued to queue 1.
• In Cisco IOS Release 12.2(25)EY or later, follow these guidelines when configuring policy maps on
physical ports or SVIs:
– You cannot apply the same policy map to a physical port and to an SVI.
– If VLAN-based QoS is configured on a physical port, the switch removes all the port-based
policy maps on the port. The traffic on this physical port is now affected by the policy map
attached to the SVI to which the physical port belongs.
– In a dual-level policy map attached to an SVI, you can only configure an individual policer at
the interface level on a physical port to specify the bandwidth limits for the traffic on the port.
The ingress port must be configured as a trunk or as a static-access port. You cannot configure
policers at the VLAN level of the dual-level policy map.
– The switch does not support aggregate policers in dual-level policy maps.
– After the dual-level policy map is attached to an SVI, the interface-level policy map cannot be
modified or removed from the dual-level policy map. A new interface-level policy map also
cannot be added to the dual-level policy map. You also cannot add or remove a class map
specified in the dual-level policy map. If you want these changes to occur, the hierarchical
policy map must first be removed from the SVI.
For outbound traffic on an ES port, see the “Hierarchical QoS Configuration Guidelines” section on
page 34-104.
Packet Modification
A packet is classified, policed, and queued to provide QoS. Packet modifications can occur during this
process:
• For IP and non-IP packets, ingress classification involves assigning a QoS label to a packet based
on the DSCP or CoS of the received packet. However, the packet is not modified at this stage; only
an indication of the assigned DSCP or CoS value is carried along. The reason for this is that QoS
classification and forwarding lookups occur in parallel, and it is possible that the packet is forwarded
with its original DSCP to the CPU where it is again processed through software.
When the ES ports classify traffic at egress, this classification can be used for queuing or for
marking the CoS, DSCP, IP precedence, or MPLS EXP bits. Any packet modifications that result
from ingress classification are applied before the packet reaches the egress classification stage. For
example, if the switch receives traffic with a CoS value of 2 and an ingress action resets the CoS to
4, the packet will have a CoS of 4 (instead of a CoS of 2 and an indicator that the CoS should be set
to 4) when it moves to the egress classification stage.
• During ingress policing, IP and non-IP packets can have another DSCP assigned to them (if they are
out of profile and the policer specifies a markdown DSCP). Once again, the DSCP in the packet is
not modified, but an indication of the marked-down value is carried along. For IP packets, the packet
modification occurs at a later stage; for non-IP packets the DSCP is converted to CoS and used for
queueing and scheduling decisions.
During egress policing on the ES ports, marking actions can set the CoS, DSCP, IP precedence, or
the MPLS EXP bits. Any markings performed by an ingress policer are applied before the packet
reaches the egress classification stage.
• Depending on the QoS label assigned to a frame and the mutation chosen, the DSCP and CoS values
of the frame are rewritten. If you do not configure the mutation map and if you configure the port to
trust the DSCP of the inbound frame, the DSCP value in the frame is not changed, but the CoS is
rewritten according to the DSCP-to-CoS map. If you configure the port to trust the CoS of the
inbound frame and it is an IP packet, the CoS value in the frame is not changed, but the DSCP might
be changed according to the CoS-to-DSCP map.
The input mutation causes the DSCP to be rewritten depending on the new value of DSCP chosen.
The set action in a policy map also causes the DSCP to be rewritten.
This information applies to both standard and ES ports. On the ES ports, the switch also applies trust
policies to IEEE 802.1Q tunneling frames at egress.
• If you apply an ingress hierarchical policy to an ES port, packets can be queued, dropped, and
changed because of the marking process that occurs before the standard ingress actions.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 mls qos Enable QoS globally.
QoS runs from the settings described in the “Standard QoS
Configuration” section on page 34-50 and the “Hierarchical
QoS Configuration” section on page 34-103.
Step 3 end Return to privileged EXEC mode.
Step 4 show mls qos Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
Trusted interface
Trunk
Traffic classification
performed here
P3 P1
101236
IP
Trusted boundary
Beginning in privileged EXEC mode, follow these steps to configure the port to trust the classification
of the traffic that it receives:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the port to be trusted, and enter interface configuration mode.
Valid interfaces include physical ports.
Command Purpose
Step 3 mls qos trust [cos | dscp | Configure the port trust state.
ip-precedence]
By default, the port is not trusted. If no keyword is specified, the default is dscp.
For 802.1Q tunnels, the switch processes inbound traffic on a standard port
according to the trusted setting applied to this port. The switch configures the
inner and outer tags for packets sent over the ES trunk port.
The keywords have these meanings:
• cos—Classifies an ingress packet by using the packet CoS value. For an
untagged packet, the port CoS value is used. The port CoS value is 0.
For IEEE 802.1Q tunnels, the switch copies the inner CoS value to the
outer CoS value and sends the packet out an ES port.
• dscp—Classifies an ingress packet by using the packet DSCP value if the
packet is an IP packet. For a non-IP packet, the packet CoS value is used if
the packet is tagged; for an untagged packet, the port CoS is used.
Internally, the switch maps the CoS value to a DSCP value by using the
CoS-to-DSCP map.
For IEEE 802.1Q tunnels, for a non-IP packet that is untagged, the switch
configures the outer CoS value from the DSCP-to-CoS map, does not
modify the inner CoS value, and sends the packet out an ES port. For an IP
packet, the switch modifies the DSCP value in the packet if there is a
DSCP-to-DSCP mutation map configured on the standard port. The switch
uses the mutated DSCP value to configure the outer CoS value from the
DSCP-to-CoS map and sends the packet out an ES port.
• ip-precedence—Classifies an ingress packet by using the packet
IP-precedence value. For a non-IP packet, the packet CoS value is used if
the packet is tagged; for an untagged packet, the port CoS is used.
Internally, the switch maps the CoS value to a DSCP value through the
CoS-to-DSCP map.
For 802.1Q tunnels, the switch converts the generated DSCP value from the
DSCP-to-CoS map and uses it as the outer CoS value in the packet. The
switch does not modify the inner CoS value in the packet and sends the
packet out an ES port.
Note When port trust policies are used with IEEE 802.1Q tunneling, all ports
sharing the same tunnel VLAN must be configured with the same trust
policy, and the ports involved must use the same DSCP-to-DSCP
mutation map. For more information, see the “Configuring the
DSCP-to-DSCP-Mutation Map” section on page 34-85.
Step 4 end Return to privileged EXEC mode.
Step 5 show mls qos interface Verify your entries.
Step 6 copy running-config (Optional) Save your entries in the configuration file.
startup-config
To return a port to its untrusted state, use the no mls qos trust interface configuration command.
For information on how to change the CoS value, see the “Configuring the CoS Value for an Interface”
section on page 34-59. For information on how to configure the CoS-to-DSCP map, see the “Configuring
the CoS-to-DSCP Map” section on page 34-81.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the port to be configured, and enter interface configuration mode.
Valid interfaces include physical ports.
Step 3 mls qos cos {-cos | override} Configure the default CoS value for the port.
For IEEE 802.1Q tunnels, the switch processes inbound traffic on a standard
port according to the trusted setting applied to this port. The switch
configures the inner and outer tags for packets sent over the ES trunk port.
• For -cos, specify a CoS value to be assigned to a port. If the packet is
untagged, the CoS value becomes the packet CoS value. The CoS range
is 0 to 7. The default is 0.
• Use the override keyword to override the previously configured trust
state of the inbound packet and to apply the port CoS value to the port
on all inbound packets. By default, CoS override is disabled.
Use the override keyword when all inbound packets on specified ports
deserve higher or lower priority than packets entering from other ports.
Even if a port was previously set to trust DSCP, CoS, or IP precedence,
this command overrides the previously configured trust state, and all
the inbound CoS values are assigned the CoS value configured with this
command. If an inbound packet is tagged, the CoS value of the packet
is modified with the default CoS of the port at the ingress port.
When an incoming packet is received on an interface acting as an IEEE
802.1Q tunnel and is sent out an ES port, the switch modifies the outer
CoS value and does not modify the inner CoS value.
Step 4 end Return to privileged EXEC mode.
Step 5 show mls qos interface Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default setting, use the no mls qos cos {-cos | override} interface configuration
command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 cdp run Enable CDP globally. By default, CDP is enabled.
Step 3 interface interface-id Specify the port connected to the IP phone, and enter interface configuration
mode.
Valid interfaces include physical ports.
Step 4 cdp enable Enable CDP on the port. By default, CDP is enabled.
Step 5 mls qos trust cos Configure the port to trust the CoS value in traffic received from the Cisco
IP Phone. By default, the port is not trusted.
Step 6 mls qos trust device cisco-phone Specify that the Cisco IP Phone is a trusted device.
You cannot enable both trusted boundary and auto-QoS (auto qos voip
interface configuration command) at the same time; they are mutually
exclusive.
Step 7 end Return to privileged EXEC mode.
Step 8 show mls qos interface Verify your entries.
Step 9 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable the trusted boundary feature, use the no mls qos trust device interface configuration
command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 mls qos Enable QoS globally.
Step 3 no mls qos rewrite ip dscp Enable DSCP transparency. The switch is configured to not modify the
DSCP field of the IP packet.
Step 4 end Return to privileged EXEC mode.
Step 5 show mls qos interface [interface-id] Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To configure the switch to modify the DSCP value based on the trust setting or on an ACL by disabling
DSCP transparency, use the mls qos rewrite ip dscp global configuration command.
If you disable QoS by using the no mls qos global configuration command, the CoS and DSCP values
are not changed (the default QoS setting).
If you enter the no mls qos rewrite ip dscp global configuration command to enable DSCP transparency
and then enter the mls qos trust [cos | dscp] interface configuration command, DSCP transparency is
still enabled.
Configuring the DSCP Trust State on a Port Bordering Another QoS Domain
If you are administering two separate QoS domains between which you want to implement QoS features
for IP traffic, you can configure the switch ports bordering the domains to a DSCP-trusted state as shown
in Figure 34-15. Then the receiving port accepts the DSCP-trusted value and avoids the classification
stage of QoS. If the two domains use different DSCP values, you can configure the
DSCP-to-DSCP-mutation map to translate a set of DSCP values to match the definition in the other
domain.
IP traffic
101235
Set interface to the DSCP-trusted state.
Configure the DSCP-to-DSCP-mutation map.
Beginning in privileged EXEC mode, follow these steps to configure the DSCP-trusted state on a port
and modify the DSCP-to-DSCP-mutation map. To ensure a consistent mapping strategy across both QoS
domains, you must perform this procedure on the ports in both domains:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 mls qos map dscp-mutation Modify the DSCP-to-DSCP-mutation map.
dscp-mutation-name in-dscp to out-dscp
The DSCP-to-DSCP-mutation map is a null map, which maps an
inbound DSCP value to the same DSCP value.
• For dscp-mutation-name, enter the mutation map name. You can
create more than one map by specifying a new name.
• For in-dscp, enter up to eight DSCP values separated by spaces.
Then enter the to keyword.
• For out-dscp, enter a single DSCP value.
The DSCP range is 0 to 63.
Step 3 interface interface-id Specify the port to be trusted, and enter interface configuration mode.
Valid interfaces include physical ports.
Step 4 mls qos trust dscp Configure the ingress port as a DSCP-trusted port. By default, the port
is not trusted.
Step 5 mls qos dscp-mutation Apply the map to the specified ingress DSCP-trusted port.
dscp-mutation-name
For dscp-mutation-name, specify the mutation map name created in
Step 2.
You can configure multiple DSCP-to-DSCP-mutation maps on an
ingress port.
Step 6 end Return to privileged EXEC mode.
Command Purpose
Step 7 show mls qos maps dscp-mutation Verify your entries.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return a port to its nontrusted state, use the no mls qos trust interface configuration command. To
return to the default DSCP-to-DSCP-mutation map values, use the no mls qos map dscp-mutation
dscp-mutation-name global configuration command.
This example shows how to configure a port to the DSCP-trusted state and to modify the
DSCP-to-DSCP-mutation map (named gi1/1/1-mutation) so that inbound DSCP values 10 to 13 are
mapped to DSCP 30:
Switch(config)# mls qos map dscp-mutation gi1/1/1-mutation 10 11 12 13 to 30
Switch(config)# interface gigabitethernet1/1/1
Switch(config-if)# mls qos trust dscp
Switch(config-if)# mls qos dscp-mutation gi1/1/1-mutation
Switch(config-if)# end
Beginning in privileged EXEC mode, follow these steps to create an IP standard ACL for inbound IP
traffic:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 access-list access-list-number {deny | Create an IP standard ACL, repeating the command as many times as
permit} source [source-wildcard] necessary.
• For access-list-number, enter the access list number. The range is
1 to 99 and 1300 to 1999.
• Use the permit keyword to permit a certain type of traffic if the
conditions are matched. Use the deny keyword to deny a certain
type of traffic if conditions are matched.
• For source, enter the network or host from which the packet is
being sent. You can use the any keyword as an abbreviation for
0.0.0.0 255.255.255.255.
• (Optional) For source-wildcard, enter the wildcard bits in dotted
decimal notation to be applied to the source. Place ones in the bit
positions that you want to ignore.
Note When creating an access list, remember that, by default, the end
of the access list contains an implicit deny statement for
everything if it did not find a match before reaching the end.
Step 3 end Return to privileged EXEC mode.
Step 4 show access-lists Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To delete an access list, use the no access-list access-list-number global configuration command.
This example shows how to allow access for only those hosts on the three specified networks. The
wildcard bits apply to the host portions of the network addresses. Any host with a source address that
does not match the access list statements is rejected.
Switch(config)# access-list 1 permit 192.5.255.0 0.0.0.255
Switch(config)# access-list 1 permit 128.88.0.0 0.0.255.255
Switch(config)# access-list 1 permit 36.0.0.0 0.0.0.255
! (Note: all other access implicitly denied)
Beginning in privileged EXEC mode, follow these steps to create an IP extended ACL for inbound IP
traffic:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 access-list access-list-number {deny | Create an IP extended ACL, repeating the command as many times as
permit} protocol source source-wildcard necessary.
destination destination-wildcard
• For access-list-number, enter the access list number. The range is
100 to 199 and 2000 to 2699.
• Use the permit keyword to permit a certain type of traffic if the
conditions are matched. Use the deny keyword to deny a certain
type of traffic if conditions are matched.
• For protocol, enter the name or number of an IP protocol. Use the
question mark (?) to see a list of available protocol keywords.
• For source, enter the network or host from which the packet is
being sent. You specify this by using dotted decimal notation, by
using the any keyword as an abbreviation for source 0.0.0.0
source-wildcard 255.255.255.255, or by using the host keyword
for source 0.0.0.0.
• For source-wildcard, enter the wildcard bits by placing ones in the
bit positions that you want to ignore. You specify the wildcard by
using dotted decimal notation, by using the any keyword as an
abbreviation for source 0.0.0.0 source-wildcard 255.255.255.255,
or by using the host keyword for source 0.0.0.0.
• For destination, enter the network or host to which the packet is
being sent. You have the same options for specifying the
destination and destination-wildcard as those described by source
and source-wildcard.
Note When creating an access list, remember that, by default, the end
of the access list contains an implicit deny statement for
everything if it did not find a match before reaching the end.
Step 3 end Return to privileged EXEC mode.
Step 4 show access-lists Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To delete an access list, use the no access-list access-list-number global configuration command.
This example shows how to create an ACL that permits IP traffic from any source to any destination that
has the DSCP value set to 32:
Switch(config)# access-list 100 permit ip any any dscp 32
This example shows how to create an ACL that permits IP traffic from a source host at 10.1.1.1 to a
destination host at 10.1.1.2 with a precedence value of 5:
Switch(config)# access-list 100 permit ip host 10.1.1.1 host 10.1.1.2 precedence 5
This example shows how to create an ACL that permits PIM traffic from any source to a destination
group address of 224.0.0.2 with a DSCP set to 32:
Switch(config)# access-list 102 permit pim any 224.0.0.2 dscp 32
Beginning in privileged EXEC mode, follow these steps to create a Layer 2 MAC ACL for inbound
non-IP traffic:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 mac access-list extended name Create a Layer 2 MAC ACL by specifying the name of the list. When you
enter this command, the mode changes to extended MAC ACL configuration.
Step 3 {permit | deny} {host Specify the type of traffic to permit or deny if the conditions are matched,
src-MAC-addr mask | any | host entering the command as many times as necessary.
dst-MAC-addr | dst-MAC-addr
• For src-MAC-addr, enter the MAC address of the host from which the
mask} [type mask]
packet is being sent. You specify this by using the hexadecimal format
(H.H.H), by using the any keyword as an abbreviation for source 0.0.0,
source-wildcard ffff.ffff.ffff, or by using the host keyword for source
0.0.0.
• For mask, enter the wildcard bits by placing ones in the bit positions that
you want to ignore.
• For dst-MAC-addr, enter the MAC address of the host to which the packet
is being sent. You specify this by using the hexadecimal format (H.H.H),
by using the any keyword as an abbreviation for source 0.0.0, source-
wildcard ffff.ffff.ffff, or by using the host keyword for source 0.0.0.
• (Optional) For type mask, specify the Ethertype number of a packet with
Ethernet II or SNAP encapsulation to identify the protocol of the packet.
For type, the range is from 0 to 65535, typically specified in hexadecimal.
For mask, enter the don’t care bits applied to the Ethertype before testing
for a match.
Note When creating an access list, remember that, by default, the end of the
access list contains an implicit deny statement for everything if it did
not find a match before reaching the end.
Step 4 end Return to privileged EXEC mode.
Step 5 show access-lists Verify your entries.
[access-list-number |
access-list-name]
Step 6 copy running-config (Optional) Save your entries in the configuration file.
startup-config
To delete an access list, use the no mac access-list extended access-list-name global configuration
command.
This example shows how to create a Layer 2 MAC ACL with two permit statements. The first statement
allows traffic from the host with MAC address 0001.0000.0001 to the host with MAC
address 0002.0000.0001. The second statement allows only Ethertype XNS-IDP traffic from the host
with MAC address 0001.0000.0002 to the host with MAC address 0002.0000.0002.
Switch(config)# mac access-list extended maclist1
Switch(config-ext-macl)# permit 0001.0000.0001 0.0.0 0002.0000.0001 0.0.0
Switch(config-ext-macl)# permit 0001.0000.0002 0.0.0 0002.0000.0002 0.0.0 xns-idp
! (Note: all other access implicitly denied)
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 access-list access-list-number {deny | Create an IP standard or extended ACL for IP traffic or a Layer 2 MAC
permit} source [source-wildcard] ACL for non-IP traffic, repeating the command as many times as
necessary.
or
For more information, see the “Classifying Ingress Traffic by Using
access-list access-list-number {deny |
ACLs” section on page 34-63.
permit} protocol source [source-wildcard]
destination [destination-wildcard] Note When creating an access list, remember that, by default, the
or end of the access list contains an implicit deny statement for
everything if it did not find a match before reaching the end.
mac access-list extended name
{permit | deny} {host src-MAC-addr mask
| any | host dst-MAC-addr | dst-MAC-addr
mask} [type mask]
Step 3 class-map [match-all | match-any] Create a class map, and enter class-map configuration mode.
class-map-name
By default, no class maps are defined.
• (Optional) Use the match-all keyword to perform a logical-AND
of all matching statements under this class map. All criteria in the
class map must be matched.
• (Optional) Use the match-any keyword to perform a logical-OR
of all matching statements under this class map. One or more
criteria must be matched.
• For class-map-name, specify the name of the class map.
If neither the match-all nor the match-any keyword is specified, the
default is match-all.
Note Because only one match command per class map is supported,
the match-all and match-any keywords function the same.
Command Purpose
Step 4 match {access-group acl-index-or-name | Define the match criterion to classify traffic.
ip dscp dscp-list | ip precedence
By default, no match criterion is defined.
ip-precedence-list}
Only one ACL per class map is supported.
• For access-group acl-index-or-name, specify the number or name
of the ACL created in Step 2.
• For ip dscp dscp-list, enter a list of up to eight IP DSCP values to
match against inbound packets. Separate each value with a space.
The range is 0 to 63.
• For ip precedence ip-precedence-list, enter a list of up to eight
IP-precedence values to match against inbound packets. Separate
each value with a space. The range is 0 to 7.
Step 5 end Return to privileged EXEC mode.
Step 6 show class-map Verify your entries.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
To delete an existing class map, use the no class-map [match-all | match-any] class-map-name global
configuration command. To remove a match criterion, use the no match {access-group
acl-index-or-name | ip dscp | ip precedence} class-map configuration command.
This example shows how to configure the class map called class1. The class1 has one match criterion,
which is access list 103. It permits traffic from any host to any destination that matches a DSCP value
of 10.
Switch(config)# access-list 103 permit ip any any dscp 10
Switch(config)# class-map class1
Switch(config-cmap)# match access-group 103
Switch(config-cmap)# exit
This example shows how to create a class map called class2, which matches inbound traffic with DSCP
values of 10, 11, and 12:
Switch(config)# class-map class2
Switch(config-cmap)# match ip dscp 10 11 12
Switch(config-cmap)# exit
This example shows how to create a class map called class3, which matches inbound traffic with
IP-precedence values of 5, 6, and 7:
Switch(config)# class-map class3
Switch(config-cmap)# match ip precedence 5 6 7
Switch(config-cmap)# exit
control-plane traffic is marked with these values except for Connectivity Fault Management (CFM) traffic.
Cisco IOS IP Service Level Agreements (SLAs) traffic that uses the CFM layer for transacting the messages
is not affected. However, IP SLAs traffic that uses UDP or other networking layer protocols is affected by this
feature.
To use the cpu traffic qos feature, you must globally enable the mls qos global configuration command
on the switch. You can also mark native VLAN traffic and tag it by entering the vlan dot1q tag native
global configuration command.
Use the mls qos srr-queue output cpu-queue global configuration command to specify an egress queue
and a threshold value for CPU-generated traffic. The default egress queue value is 2. You can assign each
packet that flows through the switch to a queue and to a threshold. Specifically, you map DSCP or CoS
values to an egress queue-set and map DSCP or CoS values to a threshold ID. You use the mls qos
srr-queue output dscp-map queue queue-id {dscp1...dscp8 | threshold threshold-iddscp1...dscp8} or
the mls qos srr-queue output cos-map queue queue-id {cos1...cos8 | thresholdthreshold-id
cos1...cos8} global configuration command.
Classifying, Policing, and Marking Ingress Traffic by Using Nonhierarchical Single-Level Policy
Maps
On a physical port, a nonhierarchical single-level policy map specifies which inbound traffic class to act
on. You can specify which CoS, DSCP, or IP precedence values in the traffic class to trust. You can
specify which DSCP or IP precedence values in the traffic class to set. You can specify the traffic
bandwidth limitations for each matched traffic class (policer) and the action to take when the traffic is
out of profile (marking).
A policy map also has these characteristics:
• A policy map can contain multiple class statements, each with different match criteria and policers.
• A policy map can contain a predefined default traffic class explicitly placed at the end of the map.
• A separate policy-map class can exist for each type of traffic received through a port.
• A policy-map trust state and a port trust state are mutually exclusive. The last one configured takes
effect.
Follow these guidelines when configuring single-level policy maps:
• You can attach only one policy map per ingress port.
• If you configure the IP-precedence-to-DSCP map by using the mls qos map ip-prec-dscp
dscp1...dscp8 global configuration command, the settings only affect packets on ingress interfaces
that are configured to trust the IP precedence value. In a policy map, if you set the packet IP
precedence value to a new value by using the set precedence new-precedence policy-map class
configuration command, the egress DSCP value is not affected by the IP-precedence-to-DSCP map.
If you want the egress DSCP value to be different than the ingress value, use the set dscp new-dscp
policy-map class configuration command.
• When you configure a default traffic class by using the class class-default policy-map configuration
command, unclassified traffic (traffic that does not meet the match criteria specified in the traffic
classes) is treated as the default traffic class (class-default).
Before beginning this procedure, make sure that you have created the class map to isolate traffic. For
more information, see the “Classifying Ingress Traffic by Using ACLs” section on page 34-63 and the
“Classifying Ingress Traffic by Using Class Maps” section on page 34-67.
For information about configuring a policy map for an ES port, see the “Configuring a Hierarchical
Two-Rate Traffic Policer” section on page 34-110 and the “Configuring Class-Based Packet Marking in
a Hierarchical Traffic Policy” section on page 34-114.
Beginning in privileged EXEC mode, follow these steps to create an ingress single-level policy map:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 policy-map policy-map-name Create a policy map by entering the policy-map name, and enter
policy-map configuration mode.
By default, no policy maps are defined.
The behavior of a policy map is to set the DSCP to 0 if the packet is an
IP packet and to set the CoS to 0 if the packet is tagged. No policing is
performed.
Step 3 class [class-map-name | class-default] Defines a traffic classification, and enter policy-map class
configuration mode.
By default, no policy map class-maps are defined.
If a traffic class has already been defined by using the class-map global
configuration command, specify its name for class-map-name in this
command.
A class-default traffic class is pre-defined and can be added to any
policy. It is always placed at the end of a policy map. With an implied
match any included in the class-default class, all packets that have not
already matched the other traffic classes will match class-default.
Step 4 trust [cos | dscp | ip-precedence] Configure the trust state, which QoS uses to generate a CoS-based or
DSCP-based QoS label.
By default, the port is not trusted. If no keyword is specified when the
command is entered, the default is dscp.
The keywords have these meanings:
• cos—QoS derives the DSCP value by using the received or port
CoS value and the CoS-to-DSCP map.
• dscp—QoS derives the DSCP value by using the DSCP value from
the ingress packet. For non-IP packets that are tagged, QoS derives
the DSCP value by using the received CoS value; for non-IP
packets that are untagged, QoS derives the DSCP value by using
the port CoS value. In either case, the DSCP value is derived from
the CoS-to-DSCP map.
• ip-precedence—QoS derives the DSCP value by using the IP
precedence value from the ingress packet and the
IP-precedence-to-DSCP map. For non-IP packets that are tagged,
QoS derives the DSCP value by using the received CoS value; for
non-IP packets that are untagged, QoS derives the DSCP value by
using the port CoS value. In either case, the DSCP value is derived
from the CoS-to-DSCP map.
For more information, see the “Configuring the CoS-to-DSCP Map”
section on page 34-81.
Command Purpose
Step 5 set {dscp new-dscp | precedence Mark IP traffic by setting a new value in the packet:
new-precedence}
• For dscp new-dscp, enter a new DSCP value to be assigned to the
classified traffic. The range is 0 to 63.
• For precedence new-precedence, enter a new IP-precedence value
to be assigned to the classified traffic. The range is 0 to 7.
Note The set dscp new-dscp and the set precedence new-precedence
commands are the same as the set ip dscp new-dscp and the set
ip precedence new-precedence commands.
Step 6 police rate-bps burst-byte [exceed-action Define a policer for the classified traffic.
{drop | policed-dscp-transmit}]
By default, no policer is defined. For information on the number of
policers supported, see the “Standard QoS Configuration Guidelines”
section on page 34-53.
• For rate-bps, specify average traffic rate in bps. The range is 8000
to 1000000000.
• For burst-byte, specify the normal burst size in bytes. The range is
8000 to 1000000.
• (Optional) Specify the action to take when the rates are exceeded.
Use the exceed-action drop keywords to drop the packet. Use the
exceed-action policed-dscp-transmit keywords to mark down the
DSCP value (through the policed-DSCP map) and send the packet.
For more information, see the “Configuring the Policed-DSCP
Map” section on page 34-83.
Step 7 exit Return to policy-map configuration mode.
Step 8 exit Return to global configuration mode.
Step 9 interface interface-id Specify the port to attach to the policy map, and enter interface
configuration mode.
Valid interfaces include physical ports.
Step 10 service-policy input policy-map-name Specify the ingress policy-map name, and apply it to a port.
Step 11 end Return to privileged EXEC mode.
Step 12 show policy-map [policy-map-name [class Verify your entries.
class-map-name]]
Step 13 copy running-config startup-config (Optional) Save your entries in the configuration file.
To delete an existing policy map, use the no policy-map policy-map-name global configuration
command. To delete an existing class, use the no class class-name policy-map configuration command.
To return to the default untrusted state, use the no trust policy-map class configuration command. To
remove an assigned DSCP or IP precedence value, use the no set {dscp new-dscp | precedence
new-precedence} policy-map class configuration command. To remove an existing policer, use the no
police rate-bps burst-byte [exceed-action {drop | policed-dscp-transmit}] policy-map class
configuration command. To remove the policy map and interface association, use the no service-policy
input policy-map-name interface configuration command.
This example shows how to create an ingress policy map and attach it to a port. In the configuration, the
IP standard ACL permits traffic from network 10.1.0.0. For traffic matching this classification, the DSCP
value in the inbound packet is trusted. If the matched traffic exceeds an average traffic rate of 48000 bps
and a normal burst size of 8000 bytes, its DSCP is marked down (based on the policed-DSCP map) and
sent.
Switch(config)# access-list 1 permit 10.1.0.0 0.0.255.255
Switch(config)# class-map ipclass1
Switch(config-cmap)# match access-group 1
Switch(config-cmap)# exit
Switch(config)# policy-map flow1t
Switch(config-pmap)# class ipclass1
Switch(config-pmap-c)# trust dscp
Switch(config-pmap-c)# police 48000 8000 exceed-action policed-dscp-transmit
Switch(config-pmap-c)# exit
Switch(config-pmap)# exit
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# service-policy input flow1t
This example shows how to create a Layer 2 MAC ACL with two permit statements and attach it to a
port. The first permit statement allows traffic from the host with MAC address 0001.0000.0001 destined
for the host with MAC address 0002.0000.0001. The second permit statement allows only Ethertype
XNS-IDP traffic from the host with MAC address 0001.0000.0002 destined for the host with MAC
address 0002.0000.0002.
Switch(config)# mac access-list extended maclist1
Switch(config-ext-mac)# permit 0001.0000.0001 0.0.0 0002.0000.0001 0.0.0
Switch(config-ext-mac)# permit 0001.0000.0002 0.0.0 0002.0000.0002 0.0.0 xns-idp
Switch(config-ext-mac)# exit
Switch(config)# mac access-list extended maclist2
Switch(config-ext-mac)# permit 0001.0000.0003 0.0.0 0002.0000.0003 0.0.0
Switch(config-ext-mac)# permit 0001.0000.0004 0.0.0 0002.0000.0004 0.0.0 aarp
Switch(config-ext-mac)# exit
Switch(config)# class-map macclass1
Switch(config-cmap)# match access-group maclist1
Switch(config-cmap)# exit
Switch(config)# policy-map macpolicy1
Switch(config-pmap)# class macclass1
Switch(config-pmap-c)# set dscp 63
Switch(config-pmap-c)# exit
Switch(config-pmap)# class macclass2 maclist2
Switch(config-pmap-c)# set dscp 45
Switch(config-pmap-c)# exit
Switch(config-pmap)# exit
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# mls qos trust cos
Switch(config-if)# service-policy input macpolicy1
This example shows how to create a class map that applies to both IPv4 and IPv6 traffic with the default
class applied to unclassified traffic:
Switch(config)# ip access-list 101 permit ip any any
Switch(config)# ipv6 access-list ipv6-any permit ip any any
Switch(config)# class-map cm-1
Switch(config-cmap)# match access-group 101
Switch(config-cmap)# exit
Switch(config)# class-map cm-2
Switch(config-cmap)# match access-group name ipv6-any
Switch(config-cmap)# exit
Switch(config)# policy-map pm1
Switch(config-pmap)# class cm-1
Switch(config-pmap-c)# set dscp 4
Switch(config-pmap-c)# exit
Classifying, Policing, and Marking Traffic by Using Hierarchical Dual-Level Policy Maps
In Cisco IOS Release 12.2(25)EY or later, you can configure hierarchical dual-level policy maps on
SVIs, but not on other types of interfaces. Dual-level policing combines the VLAN- and interface-level
policy maps to create a single policy map. For more information, see the “Hierarchical Dual-Level
Policing on SVIs” section on page 34-15.
On an SVI, the VLAN-level policy map specifies which traffic class to act on. Actions can include
trusting the CoS, DSCP, or IP precedence values or setting a specific DSCP or IP precedence value in
the traffic class. Use the interface-level policy map to specify the physical ports that are affected by
individual policers.
Follow these guidelines when configuring hierarchical dual-level policy maps:
• Before configuring a dual-level policy map, you must enable VLAN-based QoS on the physical
ports that are to be specified at the interface level of the policy map.
• You can attach only one policy map per ingress port or SVI.
• A policy map can contain multiple class statements, each with different match criteria and actions.
• A separate policy-map class can exist for each type of traffic received on the SVI.
• A policy map can contain a predefined default traffic class explicitly placed at the end of the map.
• A policy-map trust state and a port trust state are mutually exclusive, and whichever is configured
last takes effect.
• If you configure the IP-precedence-to-DSCP map by using the mls qos map ip-prec-dscp
dscp1...dscp8 global configuration command, the settings only affect packets on ingress interfaces
that are configured to trust the IP precedence value. In a policy map, if you set the packet IP
precedence value to a new value by using the set precedence new-precedence policy-map class
configuration command, the egress DSCP value is not affected by the IP-precedence-to-DSCP map.
If you want the egress DSCP value to be different from the ingress value, use the set dscp new-dscp
policy-map class configuration command.
• If VLAN-based QoS is enabled, the dual-level policy map supersedes the previously configured
port-based policy map.
• The dual-level policy map is attached to the SVI and affects all traffic belonging to the VLAN. The
individual policer in the interface-level traffic classification only affects the traffic on the physical
ports specified in that classification. The actions specified in the VLAN-level policy map affects the
traffic belonging to the SVI.
• When configuring a dual-level policy map on trunk ports, the VLAN ranges must not overlap. If the
ranges overlap, the actions specified in the policy map affect the incoming and outgoing traffic on
the overlapped VLANs, and the policy map is not applied properly at ingress and egress.
• Aggregate policers are not supported in dual-level policy maps.
• When VLAN-based QoS is enabled, the switch supports VLAN-based features, such as the VLAN
map.
• You can configure a dual-level policy map only on the primary VLAN of a private VLAN.
Beginning in privileged EXEC mode, follow these steps to create a hierarchical dual-level policy map:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 class-map [match-all | match-any] Create a VLAN-level class map, and enter class-map configuration
class-map-name mode. For information about creating a class map, see the “Classifying
Ingress Traffic by Using Class Maps” section on page 34-67.
By default, no class maps are defined.
• (Optional) Use the match-all keyword to perform a logical-AND
of all matching statements under this class map. All match criteria
in the class map must be matched.
• (Optional) Use the match-any keyword to perform a logical-OR of
all matching statements under this class map. One or more match
criteria must be matched.
• For class-map-name, specify the name of the class map.
If neither the match-all or match-any keyword is specified, the default
is match-all.
Note Because only one match command per class map is supported,
the match-all and match-any keywords function the same.
Step 3 match {access-group acl-index-or-name | Define the match criterion to classify traffic.
ip dscp dscp-list | ip precedence
By default, no match criterion is defined.
ip-precedence-list}
Only one match criterion per class map is supported, and only one ACL
per class map is supported.
• For access-group acl-index-or-name, specify the number or name
of the ACL.
• For ip dscp dscp-list, enter a list of up to eight IP DSCP values to
match against incoming packets. Separate each value with a space.
The range is 0 to 63.
• For ip precedence ip-precedence-list, enter a list of up to eight
IP-precedence values to match against incoming packets. Separate
each value with a space. The range is 0 to 7.
Step 4 exit Return to class-map configuration mode.
Step 5 exit Return to global configuration mode.
Command Purpose
Step 6 class-map [match-all | match-any] Create an interface-level class map, and enter class-map configuration
class-map-name mode.
By default, no class maps are defined.
• (Optional) Use the match-all keyword to perform a logical-AND
of all matching statements under this class map. All match criteria
in the class map must be matched.
• (Optional) Use the match-any keyword to perform a logical-OR of
all matching statements under this class map. One or more match
criteria must be matched.
• For class-map-name, specify the name of the class map.
If neither the match-all or match-any keyword is specified, the default
is match-all.
Note Because only one match command per class map is supported,
the match-all and match-any keywords function the same.
Step 7 match input-interface interface-id-list Specify the physical ports on which the interface-level class map acts.
You can specify up to six ports as follows:
• A single port (counts as one entry)
• A list of ports separated by a space (each port counts as an entry)
• A range of ports separated by a hyphen (counts as two entries)
This command can only be used in the child-level policy map and must
be the only match condition in the child-level policy map.
Step 8 exit Return to class-map configuration mode.
Step 9 exit Return to global configuration mode.
Step 10 policy-map policy-map-name Create an interface-level policy map by entering the policy-map name,
and enter policy-map configuration mode.
By default, no policy maps are defined, and no policing is performed.
Step 11 class [class-map-name | class-default] Defines a traffic classification, and enter policy-map class
configuration mode.
By default, no policy map class-maps are defined.
If a traffic class has already been defined by using the class-map global
configuration command, specify its name for class-map-name in this
command.
A class-default traffic class is pre-defined and can be added to any
policy. It is always placed at the end of a policy map. With an implied
match any included in the class-default class, all packets that have not
already matched the other traffic classes will match class-default.
Command Purpose
Step 12 police rate-bps burst-byte [exceed-action Define an individual policer for the classified traffic.
{drop | policed-dscp-transmit}]
By default, no policer is defined. For information on the number of
policers supported, see the “Standard QoS Configuration Guidelines”
section on page 34-53.
• For rate-bps, specify average traffic rate in bits per second (bps).
The range is 8000 to 1000000000.
• For burst-byte, specify the normal burst size in bytes. The range is
8000 to 1000000.
• (Optional) Specify the action to take when the rates are exceeded.
Use the exceed-action drop keywords to drop the packet. Use the
exceed-action policed-dscp-transmit keywords to mark down the
DSCP value (by using the policed-DSCP map) and send the packet.
For more information, see the “Configuring the Policed-DSCP
Map” section on page 34-83.
Step 13 exit Return to policy-map configuration mode.
Step 14 exit Return to global configuration mode.
Step 15 policy-map policy-map-name Create a VLAN-level policy map by entering the policy-map name, and
enter policy-map configuration mode.
By default, no policy maps are defined.
The behavior of a policy map is to set the DSCP to 0 if the packet is an
IP packet and to set the CoS to 0 if the packet is tagged. No policing is
performed.
Step 16 class class-map-name Define a VLAN-level traffic classification, and enter policy-map class
configuration mode.
By default, no policy-map class-maps are defined.
If a traffic class has already been defined by using the class-map global
configuration command, specify its name for class-map-name in this
command.
Command Purpose
Step 17 trust [cos | dscp | ip-precedence] Configure the trust state, which QoS uses to generate a CoS-based or
DSCP-based QoS label.
Note This command is mutually exclusive with the set command
within the same policy map. If you enter the trust command,
omit Step 18.
Command Purpose
Step 23 service-policy input policy-map-name Specify the VLAN-level policy-map name, and apply it to the SVI.
Repeat the previous step and this command to apply the policy map to
other SVIs.
If the dual-level VLAN-level policy map has more than one
interface-level policy map, all class maps must be configured to the
same VLAN-level policy map specified in the service-policy
policy-map-name command.
Step 24 end Return to privileged EXEC mode.
Step 25 show policy-map [policy-map-name [class Verify your entries.
class-map-name]]
or
show mls qos vlan-based
Step 26 copy running-config startup-config (Optional) Save your entries in the configuration file.
To delete an existing policy map, use the no policy-map policy-map-name global configuration
command. To delete an existing class map, use the no class class-map-name policy-map configuration
command.
To return to the default untrusted state in a policy map, use the no trust policy-map configuration
command. To remove an assigned DSCP or IP precedence value, use the no set {dscp new-dscp | ip
precedence new-precedence} policy-map configuration command.
To remove an existing policer in an interface-level policy map, use the no police rate-bps burst-byte
[exceed-action {drop | policed-dscp-transmit}] policy-map configuration command. To remove the
dual-level policy map and port associations, use the no service-policy input policy-map-name interface
configuration command.
This example shows how to create a hierarchical dual-level policy map and attach it to an SVI:
Switch(config)# access-list 101 permit ip any any
Switch(config)# class-map match-all cm-1
Switch(config-cmap)# match access-group 101
Switch(config-cmap)# exit
Switch(config)# exit
Switch(config)# class-map match-all cm-interface-1
Switch(config-cmap)# match input-interface gigabitethernet1/0/1 gigabitethernet1/0/2
Switch(config-cmap)# exit
Switch(config)# exit
Switch(config)# policy-map port-plcmap
Switch(config-pmap)# class cm-interface-1
Switch(config-pmap-c)# police 9000000 9000 exceed-action policed-dscp-transmit
Switch(config-pmap-c)# exit
Switch(config-pmap)# exit
Switch(config)# policy-map vlan-plcmap
Switch(config-pmap)# class cm-1
Switch(config-pmap-c)# set dscp 7
Switch(config-pmap-c)# service-policy port-plcmap
Switch(config-pmap-c)# exit
Switch(config-pmap)# exit
Switch(config)# interface vlan 10
Switch(config-if)# service-policy input vlan-plcmap
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 mls qos aggregate-policer Define the policer parameters that can be applied to multiple traffic
aggregate-policer-name rate-bps burst-byte classes within the same policy map.
exceed-action {drop |
By default, no aggregate policer is defined. For information on the
policed-dscp-transmit}
number of policers supported, see the “Standard QoS Configuration
Guidelines” section on page 34-53
• For aggregate-policer-name, specify the name of the aggregate
policer.
• For rate-bps, specify average traffic rate in bps. The range is
8000 to 1000000000.
• For burst-byte, specify the normal burst size in bytes. The range
is 8000 to 1000000.
• Specify the action to take when the rates are exceeded. Use the
exceed-action drop keywords to drop the packet. Use the
exceed-action policed-dscp-transmit keywords to mark down
the DSCP value (through the policed-DSCP map) and send the
packet. For more information, see the “Configuring the
Policed-DSCP Map” section on page 34-83.
Step 3 policy-map policy-map-name Create a policy map by entering the policy-map name, and enter
policy-map configuration mode.
For more information, see the “Classifying, Policing, and Marking
Ingress Traffic by Using Nonhierarchical Single-Level Policy
Maps” section on page 34-69.
Step 4 class class-name Specify the name of the class whose traffic policy you want to create
or change, and enter policy-map class configuration mode.
By default, no traffic classes are defined.
Step 5 police aggregate aggregate-policer-name Apply an aggregate policer to multiple classes in the same policy
map.
For aggregate-policer-name, enter the name specified in Step 2.
Step 6 exit Return to global configuration mode.
Step 7 interface interface-id Specify the port to attach to the policy map, and enter interface
configuration mode.
Command Purpose
Step 8 service-policy input policy-map-name Specify the ingress policy-map name, and apply it to a port.
Step 9 end Return to privileged EXEC mode.
Step 10 show mls qos aggregate-policer Verify your entries.
[aggregate-policer-name]
Step 11 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove the specified aggregate policer from a policy map, use the no police aggregate
aggregate-policer-name policy-map class configuration command. To delete an aggregate policer and its
parameters, use the no mls qos aggregate-policer aggregate-policer-name global configuration
command.
This example shows how to create an aggregate policer and attach it to multiple classes within a policy
map. In the configuration, the IP ACLs permit traffic from network 10.1.0.0 and from host 11.3.1.1. For
traffic coming from network 10.1.0.0, the DSCP in the inbound packets is trusted. For traffic coming
from host 11.3.1.1, the DSCP in the packet is changed to 56. The traffic rate from the 10.1.0.0 network
and from host 11.3.1.1 is policed. If the traffic exceeds an average rate of 48000 bps and a normal burst
size of 8000 bytes, its DSCP is marked down (based on the policed-DSCP map) and sent. The ingress
policy map is attached to a port.
Switch(config)# access-list 1 permit 10.1.0.0 0.0.255.255
Switch(config)# access-list 2 permit 11.3.1.1
Switch(config)# mls qos aggregate-police transmit1 48000 8000 exceed-action
policed-dscp-transmit
Switch(config)# class-map ipclass1
Switch(config-cmap)# match access-group 1
Switch(config-cmap)# exit
Switch(config)# class-map ipclass2
Switch(config-cmap)# match access-group 2
Switch(config-cmap)# exit
Switch(config)# policy-map aggflow1
Switch(config-pmap)# class ipclass1
Switch(config-pmap-c)# trust dscp
Switch(config-pmap-c)# police aggregate transmit1
Switch(config-pmap-c)# exit
Switch(config-pmap)# class ipclass2
Switch(config-pmap-c)# set dscp 56
Switch(config-pmap-c)# police aggregate transmit1
Switch(config-pmap-c)# exit
Switch(config-pmap)# class class-default
Switch(config-pmap-c)# set dscp 10
Switch(config-pmap-c)# exit
Switch(config-pmap)# exit
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# service-policy input aggflow1
Switch(config-if)# exit
If these values are not appropriate for your network, you need to modify them.
Beginning in privileged EXEC mode, follow these steps to modify the CoS-to-DSCP map. This
procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 mls qos map cos-dscp dscp1...dscp8 Modify the CoS-to-DSCP map.
For dscp1...dscp8, enter eight DSCP values that correspond to CoS values
0 to 7. Separate each DSCP value with a space.
The DSCP range is 0 to 63.
Step 3 end Return to privileged EXEC mode.
Step 4 show mls qos maps cos-dscp Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default map, use the no mls qos cos-dscp global configuration command.
This example shows how to modify and display the CoS-to-DSCP map:
Switch(config)# mls qos map cos-dscp 10 15 20 25 30 35 40 45
Switch(config)# end
Switch# show mls qos maps cos-dscp
Cos-dscp map:
cos: 0 1 2 3 4 5 6 7
--------------------------------
dscp: 10 15 20 25 30 35 40 45
If these values are not appropriate for your network, you need to modify them.
Beginning in privileged EXEC mode, follow these steps to modify the IP-precedence-to-DSCP map.
This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 mls qos map ip-prec-dscp Modify the IP-precedence-to-DSCP map.
dscp1...dscp8
For dscp1...dscp8, enter eight DSCP values that correspond to the IP
precedence values 0 to 7. Separate each DSCP value with a space.
The DSCP range is 0 to 63.
Step 3 end Return to privileged EXEC mode.
Step 4 show mls qos maps ip-prec-dscp Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default map, use the no mls qos ip-prec-dscp global configuration command.
This example shows how to modify and display the IP-precedence-to-DSCP map:
Switch(config)# mls qos map ip-prec-dscp 10 15 20 25 30 35 40 45
Switch(config)# end
Switch# show mls qos maps ip-prec-dscp
IpPrecedence-dscp map:
ipprec: 0 1 2 3 4 5 6 7
--------------------------------
dscp: 10 15 20 25 30 35 40 45
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 mls qos map policed-dscp dscp-list to Modify the policed-DSCP map.
mark-down-dscp
• For dscp-list, enter up to eight DSCP values separated by spaces.
Then enter the to keyword.
• For mark-down-dscp, enter the corresponding policed (marked down)
DSCP value.
Step 3 end Return to privileged EXEC mode.
Step 4 show mls qos maps policed-dscp Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default map, use the no mls qos policed-dscp global configuration command.
This example shows how to map DSCP 50 to 57 to a marked-down DSCP value of 0:
Switch(config)# mls qos map policed-dscp 50 51 52 53 54 55 56 57 to 0
Switch(config)# end
Switch# show mls qos maps policed-dscp
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 : 00 00 00 00 00 00 00 00 58 59
6 : 60 61 62 63
Note In this policed-DSCP map, the marked-down DSCP values are shown in the body of the matrix. The d1
column specifies the most-significant digit of the original DSCP; the d2 row specifies the
least-significant digit of the original DSCP. The intersection of the d1 and d2 values provides the
marked-down value. For example, an original DSCP value of 53 corresponds to a marked-down DSCP
value of 0.
If these values are not appropriate for your network, you need to modify them.
Beginning in privileged EXEC mode, follow these steps to modify the DSCP-to-CoS map. This
procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 mls qos map dscp-cos dscp-list to cos Modify the DSCP-to-CoS map.
• For dscp-list, enter up to eight DSCP values separated by spaces.
Then enter the to keyword.
• For cos, enter the CoS value to which the DSCP values correspond.
The DSCP range is 0 to 63; the CoS range is 0 to 7.
Step 3 end Return to privileged EXEC mode.
Step 4 show mls qos maps dscp-to-cos Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default map, use the no mls qos dscp-cos global configuration command.
This example shows how to map DSCP values 0, 8, 16, 24, 32, 40, 48, and 50 to CoS value 0 and to
display the map:
Switch(config)# mls qos map dscp-cos 0 8 16 24 32 40 48 50 to 0
Switch(config)# end
Switch# 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 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 : 00 06 06 06 06 06 07 07 07 07
6 : 07 07 07 07
Note In the above DSCP-to-CoS map, the CoS values are shown in the body of the matrix. The d1 column
specifies the most-significant digit of the DSCP; the d2 row specifies the least-significant digit of the
DSCP. The intersection of the d1 and d2 values provides the CoS value. For example, in the
DSCP-to-CoS map, a DSCP value of 08 corresponds to a CoS value of 0.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 mls qos map dscp-mutation Modify the DSCP-to-DSCP-mutation map.
dscp-mutation-name in-dscp to out-dscp
• For dscp-mutation-name, enter the mutation map name. You can
create more than one map by specifying a new name.
• For in-dscp, enter up to eight DSCP values separated by spaces.
Then enter the to keyword.
• For out-dscp, enter a single DSCP value.
The DSCP range is 0 to 63.
Step 3 interface interface-id Specify the port to which to attach the map, and enter interface
configuration mode.
Valid interfaces include physical ports.
Command Purpose
Step 4 mls qos trust dscp Configure the ingress port as a DSCP-trusted port. By default, the port
is not trusted.
Step 5 mls qos dscp-mutation Apply the map to the specified ingress DSCP-trusted port.
dscp-mutation-name
For dscp-mutation-name, enter the mutation map name specified in
Step 2.
Step 6 end Return to privileged EXEC mode.
Step 7 show mls qos maps dscp-mutation Verify your entries.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default map, use the no mls qos dscp-mutation dscp-mutation-name global
configuration command.
This example shows how to define the DSCP-to-DSCP-mutation map. All the entries that are not
explicitly configured are not modified (remains as specified in the null map).
Switch(config)# mls qos map dscp-mutation mutation1 1 2 3 4 5 6 7 to 0
Switch(config)# mls qos map dscp-mutation mutation1 8 9 10 11 12 13 to 10
Switch(config)# mls qos map dscp-mutation mutation1 20 21 22 to 20
Switch(config)# mls qos map dscp-mutation mutation1 30 31 32 33 34 to 30
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# mls qos trust dscp
Switch(config-if)# mls qos dscp-mutation mutation1
Switch(config-if)# end
Switch# show mls qos maps dscp-mutation mutation1
Dscp-dscp mutation map:
mutation1:
d1 : d2 0 1 2 3 4 5 6 7 8 9
---------------------------------------
0 : 00 00 00 00 00 00 00 00 10 10
1 : 10 10 10 10 14 15 16 17 18 19
2 : 20 20 20 23 24 25 26 27 28 29
3 : 30 30 30 30 30 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
Note In the above DSCP-to-DSCP-mutation map, the mutated values are shown in the body of the matrix. The
d1 column specifies the most-significant digit of the original DSCP; the d2 row specifies the
least-significant digit of the original DSCP. The intersection of the d1 and d2 values provides the mutated
value. For example, a DSCP value of 12 corresponds to a mutated value of 10.
Mapping DSCP or CoS Values to an Ingress Queue and Setting WTD Thresholds
You can prioritize inbound traffic by placing packets with particular DSCP or CoS values into certain
queues and by adjusting the queue thresholds so that packets with lower priorities are dropped.
Beginning in privileged EXEC mode, follow these steps to map DSCP or CoS values to an ingress queue
and to set WTD thresholds. This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 mls qos srr-queue input dscp-map Map DSCP or CoS values to an ingress queue and to a threshold ID.
queue queue-id threshold threshold-id By default, DSCP values 0–39 and 48–63 are mapped to queue 1 and
dscp1...dscp8 threshold 1. DSCP values 40–47 are mapped to queue 2 and threshold 1.
or By default, CoS values 0–4, 6, and 7 are mapped to queue 1 and threshold
mls qos srr-queue input cos-map 1. CoS value 5 is mapped to queue 2 and threshold 1.
queue queue-id threshold threshold-id
• For queue-id, the range is 1 to 2.
cos1...cos8
• For threshold-id, the range is 1 to 3. The drop-threshold percentage
for threshold 3 is predefined. It is set to the queue-full state.
• For dscp1...dscp8, enter up to eight values, and separate each value
with a space. The range is 0 to 63.
• For cos1...cos8, enter up to eight values, and separate each value with
a space. The range is 0 to 7.
Step 3 mls qos srr-queue input threshold Assign the two WTD threshold percentages for (threshold 1 and 2) to an
queue-id threshold-percentage1 ingress queue. The default, both thresholds are set to 100 percent.
threshold-percentage2
• For queue-id, the range is 1 to 2.
• For threshold-percentage1 threshold-percentage2, the range is 1 to
100. Separate each value with a space.
Each threshold value is a percentage of the total number of queue
descriptors allocated for the queue.
Step 4 end Return to privileged EXEC mode.
Command Purpose
Step 5 show mls qos maps Verify your entries.
The DSCP input queue threshold map appears as a matrix. The d1 column
specifies the most-significant digit of the DSCP number; the d2 row
specifies the least-significant digit in the DSCP number. The intersection
of the d1 and the d2 values provides the queue ID and threshold ID; for
example, queue 2 and threshold 1 (02-01).
The CoS input queue threshold map shows the CoS value in the top row
and the corresponding queue ID and threshold ID in the second row; for
example, queue 2 and threshold 2 (2-2).
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default CoS input queue threshold map or the DSCP input queue threshold map, use the
no mls qos srr-queue input cos-map or the no mls qos srr-queue input dscp-map global configuration
command. To return to the default WTD threshold percentages, use the no mls qos srr-queue input
threshold queue-id global configuration command.
This example shows how to map DSCP values 0 to 6 to ingress queue 1 and to threshold 1 with a drop
threshold of 50 percent. It maps DSCP values 20 to 26 to ingress queue 1 and to threshold 2 with a drop
threshold of 70 percent.
Switch(config)# mls qos srr-queue input dscp-map queue 1 threshold 1 0 1 2 3 4 5 6
Switch(config)# mls qos srr-queue input dscp-map queue 1 threshold 2 20 21 22 23 24 25 26
Switch(config)# mls qos srr-queue input threshold 1 50 70
In this example, the DSCP values (0 to 6) are assigned the WTD threshold of 50 percent and will be
dropped sooner than the DSCP values (20 to 26) assigned to the WTD threshold of 70 percent.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 mls qos srr-queue input buffers Allocate the buffers between the ingress queues
percentage1 percentage2
By default, 90 percent of the buffers are allocated to queue 1, and 10
percent of the buffers are allocated to queue 2.
For percentage1 percentage2, the range is 0 to 100. Separate each value
with a space.
You should allocate the buffers so that the queues can handle any inbound
bursty traffic.
Step 3 end Return to privileged EXEC mode.
Command Purpose
Step 4 show mls qos interface buffer Verify your entries.
or
show mls qos input-queue
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default setting, use the no mls qos srr-queue input buffers global configuration
command.
This example shows how to allocate 60 percent of the buffer space to ingress queue 1 and 40 percent of
the buffer space to ingress queue 2:
Switch(config)# mls qos srr-queue input buffers 60 40
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 mls qos srr-queue input bandwidth Assign shared round robin weights to the ingress queues.
weight1 weight2
The default setting for weight1 and weight2 is 4 (1/2 of the bandwidth is
equally shared between the two queues).
For weight1 and weight2, the range is 1 to 100. Separate each value with
a space.
SRR services the priority queue for its configured weight as specified by
the bandwidth keyword in the mls qos srr-queue input priority-queue
queue-id bandwidth weight global configuration command. Then, SRR
shares the remaining bandwidth with both ingress queues and services
them as specified by the weights configured with the mls qos srr-queue
input bandwidth weight1 weight2 global configuration command. For
more information, see the “Configuring the Ingress Priority Queue”
section on page 34-90.
Step 3 end Return to privileged EXEC mode.
Step 4 show mls qos interface queueing Verify your entries.
or
show mls qos input-queue
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default setting, use the no mls qos srr-queue input bandwidth global configuration
command.
This example shows how to assign the ingress bandwidth to the queues. Priority queueing is disabled,
and the shared bandwidth ratio allocated to queue 1 is 25/(25+75) and to queue 2 is 75/(25+75).
Switch(config)# mls qos srr-queue input priority-queue 2 bandwidth 0
Switch(config)# mls qos srr-queue input bandwidth 25 75
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 mls qos srr-queue input Assign a queue as the priority queue and guarantee bandwidth on the
priority-queue queue-id bandwidth internal ring if the ring is congested.
weight
By default, the priority queue is queue 2, and 10 percent of the bandwidth
is allocated to it.
• For queue-id, the range is 1 to 2.
• For bandwidth weight, assign the bandwidth percentage of the
internal ring. The range is 0 to 40. The amount of bandwidth that can
be guaranteed is restricted because a large value affects the entire ring
and can degrade performance.
Step 3 end Return to privileged EXEC mode.
Step 4 show mls qos interface queueing Verify your entries.
or
show mls qos input-queue
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default setting, use the no mls qos srr-queue input priority-queue queue-id global
configuration command. To disable priority queueing, set the bandwidth weight to 0, for example, mls
qos srr-queue input priority-queue queue-id bandwidth 0.
This example shows how to assign the ingress bandwidths to the queues. Queue 1 is the priority queue
with 10 percent of the bandwidth allocated to it. The bandwidth ratios allocated to queues 1 and 2 is
4/(4+4). SRR services queue 1 (the priority queue) first for its configured 10 percent bandwidth. Then
SRR equally shares the remaining 90 percent of the bandwidth between queues 1 and 2 by allocating 45
percent to each queue.
Switch(config)# mls qos srr-queue input priority-queue 1 bandwidth 10
Switch(config)# mls qos srr-queue input bandwidth 4 4
Allocating Buffer Space to and Setting WTD Thresholds for an Egress Queue-Set
You can guarantee the availability of buffers, set WTD thresholds, and configure the maximum memory
allocation for a queue-set by using the mls qos queue-set output qset-id threshold queue-id
drop-threshold1 drop-threshold2 reserved-threshold maximum-threshold global configuration command.
Each threshold value is a percentage of the queue’s allocated buffers, which you specify by using the mls
qos queue-set output qset-id buffers allocation1 ... allocation4 global configuration command. The
queues use WTD to support distinct drop percentages for different traffic classes.
Note The egress queue-set settings are suitable for most situations. You should change them only when you
have a thorough understanding of the queues and only if these settings do not meet your QoS solution.
Beginning in privileged EXEC mode, follow these steps to configure the memory allocation and drop
thresholds for a queue-set. This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 mls qos queue-set output qset-id Allocate buffers to a queue-set.
buffers allocation1 ... allocation4
By, all allocation values are equally mapped among the four queues (25,
25, 25, 25). Each queue has 1/4 of the buffer space.
• For qset-id, enter the ID of the queue-set. The range is 1 to 2. Each
port belongs to a queue-set, which defines all the characteristics of the
four egress queues per port.
• For allocation1, allocation3, and allocation4, the range is 0 to 99. For
allocation2, the range is 1 to 100 (including the CPU buffer).
Allocate buffers according to the importance of the traffic. For example,
give a larger percentage of the buffer to the queue with the highest-priority
traffic.
Step 3 mls qos queue-set output qset-id Configure the WTD thresholds, guarantee the availability of buffers, and
threshold queue-id drop-threshold1 configure the maximum memory allocation for the queue-set (four egress
drop-threshold2 reserved-threshold queues per port).
maximum-threshold
By default, the WTD thresholds for queues 1, 3, and 4 are set to 100
percent. The thresholds for queue 2 are set to 200 percent. The reserved
thresholds for queues 1, 2, 3, and 4 are set to 50 percent. The maximum
thresholds for all queues are set to 400 percent.
• For qset-id, enter the ID of the queue-set specified in Step 2. The
range is 1 to 2.
• For queue-id, enter the specific queue in the queue-set on which the
command is performed. The range is 1 to 4.
• For drop-threshold1 drop-threshold2, specify the two WTD
thresholds expressed as a percentage of the allocated queue memory.
The range is 1 to 3200 percent.
• For reserved-threshold, enter the amount of memory to be guaranteed
(reserved) for the queue expressed as a percentage of the allocated
memory. The range is 1 to 100 percent.
• For maximum-threshold, enable a full queue to obtain more buffers
than are reserved for it. This is the maximum memory the queue can
have before the packets are dropped if the common pool is not empty.
The range is 1 to 3200 percent.
Step 4 interface interface-id Specify the port, and enter interface configuration mode.
Step 5 queue-set qset-id Map the port to a queue-set.
For qset-id, enter the ID of the queue-set specified in Step 2. The range is
1 to 2. The default is 1.
Step 6 end Return to privileged EXEC mode.
Command Purpose
Step 7 show mls qos interface [interface-id] Verify your entries.
buffers
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default setting, use the no mls qos queue-set output qset-id buffers global configuration
command. To return to the default WTD threshold percentages, use the no mls qos queue-set output
qset-id threshold [queue-id] global configuration command.
This example shows how to map a port to queue-set 2. It allocates 40 percent of the buffer space to egress
queue 1 and 20 percent each to egress queues 2, 3, and 4. It configures the drop thresholds for queue 2
to 40 and 60 percent of the allocated memory, guarantees (reserves) 100 percent of the allocated memory,
and configures 200 percent as the maximum memory that this queue can have before packets are
dropped.
Switch(config)# mls qos queue-set output 2 buffers 40 20 20 20
Switch(config)# mls qos queue-set output 2 threshold 2 40 60 100 200
Switch(config)# interface fastethernet1/0/1
Switch(config-if)# queue-set 2
Note The egress queue-set settings are suitable for most situations. You should change them only when you
have a thorough understanding of the queues and only if these settings do not meet your QoS solution.
Beginning in privileged EXEC mode, follow these steps to map DSCP or CoS values to an egress queue
and to a threshold ID. This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 mls qos srr-queue output dscp-map Map DSCP or CoS values to an egress queue and to a threshold ID for a
queue queue-id threshold threshold-id port.
dscp1...dscp8 By default, DSCP values 0–15 are mapped to queue 2 and threshold 1.
or DSCP values 16–31 are mapped to queue 3 and threshold 1. DSCP values
32–39 and 48–63 are mapped to queue 4 and threshold 1. DSCP values
mls qos srr-queue output cos-map
40–47 are mapped to queue 1 and threshold 1.
queue queue-id threshold threshold-id
cos1...cos8 By default, CoS values 0 and 1 are mapped to queue 2 and threshold 1.
CoS values 2 and 3 are mapped to queue 3 and threshold 1. CoS values 4,
6, and 7 are mapped to queue 4 and threshold 1. CoS value 5 is mapped to
queue 1 and threshold 1.
• For queue-id, the range is 1 to 4.
• For threshold-id, the range is 1 to 3. The drop-threshold percentage
for threshold 3 is predefined. It is set to the queue-full state.
• For dscp1...dscp8, enter up to eight values, and separate each value
with a space. The range is 0 to 63.
• For cos1...cos8, enter up to eight values, and separate each value with
a space. The range is 0 to 7.
Step 3 end Return to privileged EXEC mode.
Step 4 show mls qos maps Verify your entries.
The DSCP output queue threshold map appears as a matrix. The d1
column specifies the most-significant digit of the DSCP number; the d2
row specifies the least-significant digit in the DSCP number. The
intersection of the d1 and the d2 values provides the queue ID and
threshold ID; for example, queue 2 and threshold 1 (02-01).
The CoS output queue threshold map shows the CoS value in the top row
and the corresponding queue ID and threshold ID in the second row; for
example, queue 2 and threshold 2 (2-2).
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default DSCP output queue threshold map or the CoS output queue threshold map, use
the no mls qos srr-queue output dscp-map or the no mls qos srr-queue output cos-map global
configuration command.
This example shows how to map DSCP values 10 and 11 to egress queue 1 and to threshold 2:
Switch(config)# mls qos srr-queue output dscp-map queue 1 threshold 2 10 11
Note SRR shaping is not supported on the ES ports; however, you can configure average-rate shaping. For
more information, see the “Configuring Shaping” section on page 34-129.
You can configure the egress queues for shaped weights, shared weights, or both. Use shaping to smooth
bursty traffic or to provide a smoother output over time. For conceptual information, see the “SRR
Shaping and Sharing” section on page 34-19. For configuration information, see the “Configuring SRR
Shared Weights on an Egress Queue-Set” section on page 34-96.
Note The egress queue-set settings are suitable for most situations. You should change them only when you
have a thorough understanding of the queues and only if these settings do not meet your QoS solution.
Beginning in privileged EXEC mode, follow these steps to assign the shaped weights and to enable
bandwidth shaping on a standard port mapped to the four egress queues. This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify a standard port, and enter interface configuration mode.
Step 3 srr-queue bandwidth shape weight1 Assign SRR weights to the egress queues. This command is not supported
weight2 weight3 weight4 on an ES port.
By default, weight1 is set to 25; weight2, weight3, and weight4 are set to 0,
and these queues are in shared mode.
For weight1 weight2 weight3 weight4, enter the weights to control the
percentage of the port that is shaped. The inverse ratio (1/weight) controls
the shaping bandwidth for this queue. Separate each value with a space.
The range is 0 to 65535.
If you configure a weight of 0, the corresponding queue operates in shared
mode. The weight specified with the srr-queue bandwidth shape
command is ignored, and the weights specified with the srr-queue
bandwidth share interface configuration command for a queue come into
effect. When configuring queues in the same queue-set for both shaping
and sharing, make sure that you configure the lowest number queue for
shaping.
The shaped mode overrides the shared mode.
Step 4 end Return to privileged EXEC mode.
Step 5 show mls qos interface interface-id Verify your entries.
queueing
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default setting, use the no srr-queue bandwidth shape interface configuration
command.
This example shows how to configure bandwidth shaping on queue 1. Because the weight ratios for
queues 2, 3, and 4 are set to 0, these queues operate in shared mode. The bandwidth weight for queue 1
is 1/8, which is 12.5 percent.
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# srr-queue bandwidth shape 8 0 0 0
Note The egress queue-set settings are suitable for most situations. You should change them only when you
have a thorough understanding of the queues and only if these settings do not meet your QoS solution.
Beginning in privileged EXEC mode, follow these steps to assign the shared weights and to enable
bandwidth sharing on a port mapped to the four egress queues. This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify a port, and enter interface configuration mode.
Step 3 srr-queue bandwidth share weight1 Assign SRR weights to the egress queues.
weight2 weight3 weight4
By default, all four weights are 25 (1/4 of the bandwidth is allocated to
each queue).
For weight1 weight2 weight3 weight4, enter the weights to control the
ratio of the frequency in which the SRR scheduler sends packets. Separate
each value with a space. The range is 1 to 255.
Step 4 end Return to privileged EXEC mode.
Step 5 show mls qos interface interface-id Verify your entries.
queueing
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default setting, use the no srr-queue bandwidth share interface configuration
command.
This example shows how to configure the weight ratio of the SRR scheduler running on an egress port.
Four queues are used, and the bandwidth ratio allocated for each queue in shared mode is 1/(1+2+3+4),
2/(1+2+3+4), 3/(1+2+3+4), and 4/(1+2+3+4), which is 10 percent, 20 percent, 30 percent, and 40
percent for queues 1, 2, 3, and 4. This means that queue 4 has four times the bandwidth of queue 1, twice
the bandwidth of queue 2, and one-and-a-third times the bandwidth of queue 3.
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# srr-queue bandwidth share 1 2 3 4
Command3 Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify a port, and enter interface configuration mode.
Step 3 priority-queue out Enable the egress priority queue, which is disabled by default.
When you configure this command, the SRR weight and queue size ratios
are affected because there is one fewer queue participating in SRR. This
means that weight1 in the srr-queue bandwidth shape or the srr-queue
bandwidth share command is not used in the ratio calculation.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable the egress priority queue, use the no priority-queue out interface configuration command.
This example shows how to enable the egress priority queue when the SRR weights are configured. The
egress expedite queue overrides the configured SRR weights.
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# srr-queue bandwidth shape 25 0 0 0
Switch(config-if)# srr-queue bandwidth share 30 20 25 25
Switch(config-if)# priority-queue out
Switch(config-if)# end
Note The egress queue-set settings are suitable for most situations. You should change them only when you
have a thorough understanding of the queues and only if these settings do not meet your QoS solution.
Beginning in privileged EXEC mode, follow these steps to limit the egress bandwidth on a standard port.
This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify a standard port to be rate-limited, and enter interface
configuration mode.
Step 3 srr-queue bandwidth limit weight1 Specify the percentage of the port speed to which the port should be
limited. The range is 10 to 90. This command is not supported on an ES
port.
By default, the port is not rate limited and is set to 100 percent.
Step 4 end Return to privileged EXEC mode.
Step 5 show mls qos interface [interface-id] Verify your entries.
queueing
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default setting, use the no srr-queue bandwidth limit interface configuration command.
This example shows how to limit the bandwidth on a standard port to 80 percent:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# srr-queue bandwidth limit 80
When you configure this command to 80 percent, the port is idle 20 percent of the time. The line rate
drops to 80 percent of the connected speed, which is 800 Mb/s. These values are not exact because the
hardware adjusts the line rate in increments of six.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 Configure CoS-to-DSCP, DSCP-to-CoS, Refer to the “Configuring DSCP Maps” section on page 34-80.
IP-precedence-to-DSCP, and
DSCP-mutation global maps
Step 3 cpu traffic qos cos {cos-value | trust} Mark the CoS value of CPU traffic.
• Use cos-value to enter a new CoS value. The range is from 0 to 7. If
no value is configured, the protocol-specific value for each packet
applies.
• Use the trust keyword to trust the incoming CoS value.
Command Purpose
Step 4 cpu traffic qos dscp {dscp_value | trust Mark the DSCP value of CPU traffic.
| dscp-mutation mutation-map-name}
• Use dscp_value to enter a new DSCP value. The range is from 0 to
63. If no value is configured, the protocol-specific value for each
packet applies.
• Use the trust keyword to trust the incoming DSCP value.
• Use the dscp-mutation keyword to mutate the incoming DSCP value
based on the configured mutation-map.
Step 5 cpu traffic qos precedence Mark the precedence value of CPU traffic.
{precedence_value | trust |
• Use precedence_value to enter a new IP-precedence value as a
precedence-mutation
number from 0 to 7 or by name: routine (0), priority (1), immediate
mutation-map-name}
(2), flash (3), flash-override (4), critical (5), internet (6), network
(7).
• If no value is configured, the protocol-specific value for each packet
applies.
• Use the trust keyword to trust the incoming precedence value.
• Use the precedence-mutation keyword to mutate the incoming
precedence value based on the configured mutation-map.
Step 6 end Return to privileged EXEC mode.
Step 7 Configure global maps to map QoS Refer to the“Mapping DSCP or CoS Values to an Egress Queue-Set and
markings to queue and threshold to a Threshold ID” section on page 34-93.
numbers.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
Step 9 show running-config Display the configured global maps and CPU traffic QoS settings.
Step 10 show cpu traffic qos Display the QoS marking values for CPU-generated traffic.
Step 11 show mls qos maps Display information for all global maps.
Example 1
This example shows how to mark the CoS of CPU-generated IP traffic (including IP-SLA and TWAMP)
based on the packet DSCP value and to configure egress queuing based on the DSCP value.
The example has these results:
• All CPU-generated IP traffic queues on the egress port based on the IP-DSCP value.
• All IP traffic with the DSCP value ef (46), which simulates voice traffic, is assigned the CoS value 5.
• All IP traffic with the DSCP values af41 (34), af42 (36) and af43 (38) is assigned the CoS value 4.
• All Internet Control Protocol traffic with the DSCP values 48 and 56 are assigned the CoS value 7.
• The rest of the IP and non-IP traffic is processed according to the default configuration.
• Queue the DSCP value 46 to queue 1 threshold 1.
• Queue the DSCP values 34 36 38 to queue 2 threshold 3.
• Queue the DSCP values 48 56 to queue 4 threshold 2.
• All other CPU traffic egresses through the default queue 2 and threshold 1.
Maps:
CPU QoS:
Queuing:
Example 2
This example shows how to mark the DSCP of CPU-generated IP traffic (including IP-SLA and
TWAMP) based on the DSCP value in the packet.
The example has these results:
• All IP traffic with the DSCP value 0 is assigned DSCP value 30.
• All IP traffic with the DSCP values af41 (34), af42 (36) and af43 (38) are assigned DSCP value 48.
• All other IP and non-IP traffic is processed by the default configuration.
Maps:
CPU QoS:
Example 3
This example shows how to mark the precedence of CPU-generated IP traffic (including IP-SLA and
TWAMP) based on the precedence value in the packet.
The example has these results:
• All CPU generated IP traffic with the precedence value 0 is assigned precedence value 3.
• All CPU generated IP traffic with the precedence values 2, 3 and 4 is assigned precedence value 6.
• All other IP and non-IP traffic is processed by the default configuration.
Maps:
CPU QoS:
Note IP-DSCP and IP-precedence are related. To mark the precedence value of an IP packet based on the
incoming packet precedence value, an equivalent DSCP-mutation map needs to be configured and used
with the cpu traffic qos precedence precedence-mutation command. Queuing is based on the IP-DSCP
value of the packet.
Example 4
This example shows how to mark the DSCP of CPU-generated IP traffic (including IP-SLA and
TWAMP) based on the CoS value in the packet and to configure egress queuing based on the CoS value.
The example has these results:
• All CPU-generated IP traffic is queued on the egress port based on the CoS value.
• All IP traffic with the CoS value 0 is assigned DSCP value 30.
• All IP traffic with the CoS values 6 and 7 is assigned DSCP value 56.
• All other IP and non-IP traffic is processed by the default configuration.
• Queues the CoS value 0 to queue 1 threshold 1.
• Queues the CoS values 6 and 7 to queue 2 threshold 3.
• All other CPU traffic egresses through the default queue 2 and threshold 1.
Maps:
CPU QoS:
Queuing:
Example 5
This example shows how to mark the CoS of CPU-generated IP traffic (including IP-SLA and TWAMP)
based on the precedence value in the packet and to configure egress queuing based on the DSCP value.
The example has these results:
• All CPU-generated IP traffic is queued on the egress port based on the IP-DSCP value.
• All IP traffic with the precedence value 3, which simulates voice traffic, is assigned CoS value 5.
• All IP traffic with the precedence values 4 and 5 are assigned CoS value 7.
• All other IP and non-IP traffic is processed by the default configuration.
• Queues the DSCP value 24 (equivalent to precedence value 3) to queue 1 threshold 1.
• Queues the DSCP values 32 and 40 (equivalent to precedence values 4 and 5) to queue 2 threshold 3.
• All other CPU traffic egresses through the default queue 2 and threshold 1.
Maps:
CPU QoS:
Queuing:
Command Purpose
show class-map [class-map-name] Display QoS class maps, which define the match criteria to
classify traffic.
show cpu traffic qos Display QoS parameters for control plane traffic.
show mls qos Display global QoS configuration information.
show mls qos aggregate-policer Display the aggregate policer configuration.
[aggregate-policer-name]
show mls qos input-queue Display QoS settings for the ingress queues.
show mls qos interface [interface-id] [buffers | policers | Display QoS information at the port level, including the buffer
queueing | statistics] allocation, which ports have policers, the queueing strategy, and
the ingress and egress statistics.
show mls qos maps [cos-dscp | cos-input-q | Display QoS mapping information.
cos-output-q | dscp-cos | dscp-input-q | dscp-mutation
dscp-mutation-name | dscp-output-q | ip-prec-dscp |
policed-dscp]
show mls qos queue-set [qset-id] Display the egress queue-set settings.
Command Purpose
show mls qos vlan vlan-id Display the policy maps attached to an SVI.
show policy-map [policy-map-name [class Display QoS policy maps, which define the traffic policy for a
class-map-name]] traffic class.
show policy-map interface interface-id [input] Display the ingress policy-map name applied to the specified
port.
Note The show policy-map interface command displays data
for hierarchical policy-maps attached to the ES
interfaces. This command does not show counters for
non-hierarchical policies on the ES interfaces, or any
policies attached to non-ES interfaces.
• In an ingress policy map, you cannot combine Layer 2 and Layer 3 set actions because the port can
trust only one value in the inbound packet. For example, the switch does not support this policy map:
policy-map p1
class cos1
police cir per 10 conform-action set-cos-transmit 3
set dscp af22
• On an ES port or EtherChannel, the only limit to the number of policers configured in a hierarchical
service-policy is the finite number of classes that can be configured. For more information, see the
“Hierarchical Levels” section on page 34-30.
• If you configure the conform-action, exceed-action, violate-action in a two-rate ingress policer
and set the CoS, DSCP, or IP precedence values of the packet by using the set-cos-transmit new-cos,
set-dscp-transmit new-dscp, or the set-prec-transmit new-prec options, the switch automatically
applies the port trust state to all traffic received on the ES port or EtherChannel, including traffic
that does not match the traffic class with the two-rate policer.
• You cannot combine Layer 2 (set-cos-transmit new-cos) and Layer 3 (set-dscp-transmit new-dscp,
or the set-prec-transmit new-prec) actions in a two-rate ingress policer because the port can trust
only one value in the inbound packet (CoS, DSCP, or IP precedence). For example, you cannot
configure the police cir percent 10 conform-action set-cos-transmit 3 exceed-action set
dscp-transmit af22 command. The conform-action sets the CoS value to 3, but the exceed-action
sets the DSCP value to af22.
• Use the configuration procedures in this section to configure hierarchical multiple-level policies on
ES ports or EtherChannels. Many of the configuration options are not supported in single-level
policy maps attached to ES ports.
• If you want to use a hierarchical ingress single-level service-policy (for example, a two-rate ingress
policer on an ES port or EtherChannel), you must create a second level in the hierarchy with only
the class-default in the policy map. For example, in the policy map, specify class-default as the class
name in the class policy-map configuration command.
• You can define a class policy to use either tail drop through the queue-limit policy-map class
configuration command or to use WRED packet drop through the random-detect policy-map class
configuration command. You cannot use the queue-limit and random-detect commands in the same
class policy, but they can be used in two class policies in the same policy map.
• You cannot use bandwidth, queue-limit, random-detect, and shape policy-map class
configuration commands with the priority policy-map class configuration command in the same
class within the same policy map. However, you can use these commands in different classes in the
same policy map. Within a policy map, you can give priority status to only one class.
• You must configure the bandwidth or the shape policy-map class configuration command before
you configure either the queue-limit or the random-detect policy-map class configuration
command in a class policy. You must configure the bandwidth or the shape command in the same
policy map as the queue-limit or the random-detect command if the policy is not using the traffic
class. If the policy is using the traffic class, you do not need to specify the bandwidth and shape
commands in the policy map.
• A policy map can have all the class bandwidths specified in either kb/s or in percentages, but not a
mix of both. You cannot specify bandwidth in kb/s in a child policy (configured through the
service-policy policy-map class configuration command) and then specify bandwidth as a
percentage in the parent policy.
• In a child policy map, the minimum bandwidth of each class map must be more than 0.01 percent
of the total bandwidth of the parent policy map. When class-default class is not configured in the
child policy map, this minimum bandwidth map is reserved for the class-default class.
• The total bandwidth configured in a child policy map cannot exceed the total bandwidth of the parent
policy map.
EtherChannel with both ES links, you should limit each policer to a maximum of 49 percent.
However, you can configure multiple policers in the same policy or across parent and child policies
with each configured to 49 percent maximum.
• When ES link states change hierarchical QoS parameters configured as absolute values or
percentages:
– If you configure parameters in absolute values, the total guaranteed bandwidth cannot be more
than 990,000,000 bits per second. If one link in the EtherChannel goes down, all traffic goes in
or out of the other physical interface instead of being distributed between the two ES ports. No
values are recalculated, and there are no changes to hierarchical QoS parameters or policy
enforcement.
– If you configure parameters in percentages and one link in the EtherChannel goes down, all
absolute parameters are reduced by half, although the configured percentage remains the same.
For bandwidth percentage configuration, all traffic is sent or received with the reduced
bandwidth parameters distributed fairly. For policing percentage configuration, packets are
dropped according to the reduced parameters so that other traffic is not affected.
• The switch does not support shaping percentages for hierarchical QoS for ES ports or
EtherChannels. Therefore, you cannot configure policing or bandwidth in percentages with any type
of shaping for policies applied to an EtherChannel.
• If you simultaneously attach both egress and ingress EtherChannel hierarchical policies, you must
configure both policies in either absolute values or in percentages. You cannot configure an ingress
policy with percentages and an egress policy with an absolute value or the reverse.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 class-map [match-all | match-any] Create a class map, and enter class-map configuration mode.
class-map-name
By default, no class maps are defined.
• (Optional) Use the match-all keyword to perform a logical-AND
of all matching statements under this class map. All criteria in the
class map must be matched.
• (Optional) Use the match-any keyword to perform a logical-OR
of all matching statements under this class map. One or more
criteria must be matched.
• For class-map-name, specify the name of the class map.
If neither the match-all nor the match-any keyword is specified, the
default is match-all. You must use the match-all keyword if you are
matching an IEEE 802.1Q tunneling pair (instead of matching a single
VLAN).
Command Purpose
Step 3 match {cos [inner] cos-list | ip dscp Define the match criterion to classify traffic.
dscp-list | ip precedence ip-precedence-list By default, no match criterion is defined.
| mpls experimental exp-list | vlan {vlan-id
| inner vlan-id}} • For cos [inner] cos-list, specify up to four Layer 2 CoS values to
match against the packet. Separate each value with a space. The
range is 0 to 7. Use the inner keyword to match the inner CoS
value in 802.1Q tunneling traffic (instead of matching the outer
CoS value).
• For ip dscp dscp-list |, specify up to eight IP DSCP values to match
against the packet. Separate each value with a space. The range is
0 to 63.
• For ip precedence ip-precedence-list, specify up to eight
IP-precedence values to match against the packet. Separate each
value with a space. The range is 0 to 7.
• For mpls experimental exp-list, specify up to eight MPLS EXP
values to match against the packet. Separate each value with a
space. The range is 0 to 7.
• For vlan {vlan-id | inner vlan-id}, specify packet match based on
the VLAN ID.
– For vlan vlan-id, match a packet based on the VLAN ID, or
match a packet based on the outer VLAN ID if an
IEEE 802.1Q tunnel is configured. You can specify a single
VLAN identified by a VLAN number or a range of VLANs
separated by a hyphen. The range is 1 to 4094.
– For vlan inner vlan-id, match a packet based on the inner
VLAN ID of an IEEE 802.1Q tunnel.You can specify a single
VLAN identified by a VLAN number or a range of VLANs
separated by a hyphen. The range is 1 to 4094.
When matching an IEEE 802.1Q tunneling pair (instead of
matching a single VLAN), you must enter the match vlan
command before the match vlan inner command.
Note You cannot mix VLAN-level and class-level matches within a
class map.
Step 4 end Return to privileged EXEC mode.
Step 5 show class-map Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To delete an existing class map, use the no class-map [match-all | match-any] class-map-name global
configuration command. To remove a match criterion, use the no match {cos [inner] cos-list | ip dscp
dscp-list | ip precedence ip-precedence-list | mpls experimental exp-list | vlan {vlan-id | inner
vlan-id}} class-map configuration command.
This example shows how to create a class-level class-map called class3, which matches traffic with
IP-precedence values of 5, 6, and 7:
Switch(config)# class-map class3
Switch(config-cmap)# match ip precedence 5 6 7
This example shows how to create a VLAN-level class-map for IEEE 802.1Q tunneling called dot1q,
which matches all traffic with an outer VLAN ID of 5 and an inner VLAN ID of 3 to 8:
Switch(config)# class-map match-all dot1q
Switch(config-cmap)# match vlan 5
Switch(config-cmap)# match vlan inner 3 - 8
This example shows how to create a VLAN-level class-map called vlan203, which matches traffic in
VLAN 203:
Switch(config)# class-map match-all vlan203
Switch(config-cmap)# match vlan 203
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 policy-map policy-map-name Create a policy map by entering the policy-map name, and enter
policy-map configuration mode.
By default, no policy maps are defined.
Step 3 class class-name Specify the name of the class whose traffic policy you want to create
or change, and enter policy-map class configuration mode.
By default, no traffic classes are defined.
Command Purpose
Step 4 police cir cir [bc conform-burst] pir pir Configure a traffic policer that uses two rates, the CIR and the peak
[be peak-burst] [conform-action action information rate PIR. By default, no policer is defined.
[exceed-action action [violate-action
• For cir cir, specify the CIR at which the first token bucket is
action]]]
updated. The range is 64000 to 990000000 b/s.
or
• (Optional) For bc conform-burst, specify the conform burst size
police cir percent percent [bc used by the first token bucket for policing. The range is 1536 to
conform-burst ms] | pir percent percent 16776960 bytes. The default is 8192.
[be peak-burst ms] [conform-action
• For pir pir, specify the PIR at which the second token bucket for
action [exceed-action action
policing is updated. The range is 64000 to 990000000 b/s.
[violate-action action]]]
• (Optional) For be peak-burst, specify the peak burst size used by
Note For the syntax description of the the second token bucket. The range is 1536 to 16776960 bytes. The
police cir percent command, see default is 8192.
the command reference for this
release. • (Optional) For conform-action, specify the action to perform on
packets that conform to the CIR and PIR.
• (Optional) For exceed-action, specify the action to perform on
packets that conform to the PIR but not the CIR.
• (Optional) For violate-action, specify the action to perform on
packets that exceed the PIR.
Note If you do not specify an action, the default conform-action is
transmit, the exceed-action is drop, and the default
violate-action is drop.
Command Purpose
Step 6 exit Return to global configuration mode.
Step 7 interface interface-id Specify an ES port or an EtherChannel port channel, and enter
interface configuration mode.
Step 8 service-policy {input | output} Specify the policy-map name, and apply it to the ES port or
policy-map-name EtherChannel.
Step 9 end Return to privileged EXEC mode.
Step 10 show policy-map policy-map-name Verify your entries.
or
show policy-map interface interface-id
Step 11 copy running-config startup-config (Optional) Save your entries in the configuration file.
To delete an existing policy map, use the no policy-map policy-map-name global configuration
command. To delete an existing class, use the no class class-name policy-map configuration command.
To remove the two-rate policer, use the no police cir cir [bc conform-burst] pir pir [be peak-burst]
[conform-action action [exceed-action action [violate-action action]]] policy-map class configuration
command. To remove the policy map and interface association, use the no service-policy output
policy-map-name interface configuration command.
Note If you apply the policy map to an EtherChannel with no ports and then add a standard port to the
EtherChannel, the policy is removed from the EtherChannel because standard ports do not support
hierarchical QoS.
This example shows how to configure a class-level, two-rate traffic policer to limit outbound traffic to
an average committed rate of 500 kb/s and a peak rate of 1 Mb/s. Traffic marked as conforming to the
average committed rate (500 kb/s) is sent as is. Traffic marked as exceeding 500 kb/s, but not exceeding
1 Mb/s, is marked with IP precedence 2 and then sent. All traffic marked as exceeding 1 Mb/s is dropped.
The burst parameters are set to 10000 bytes.
Switch(config)# class-map c1
Switch(config-cmap)# match ip precedence 4
Switch(config-cmap)# exit
Switch(config)# policy-map policy1
Switch(config-pmap)# class c1
Switch(config-pmap-c)# police cir 500000 bc 10000 pir 1000000 be 10000 conform-action
transmit exceed-action set-prec-transmit 2 violate-action drop
Switch(config-pmap-c)# exit
Switch(config-pmap)# exit
Switch(config)# interface gigabitethernet1/1/1
Switch(config-if)# service-policy output policy1
This example shows how to configure a class-level, two-rate traffic policer that uses a CIR and a PIR
based on a percentage of bandwidth. A CIR of 20 percent and a PIR of 40 percent are specified. The
optional bc and be values (300 ms and 400 ms, respectively) are specified.
Switch(config)# class-map c1
Switch(config-cmap)# match ip precedence 4
Switch(config-cmap)# exit
Switch(config)# policy-map policy1
Switch(config-pmap)# class class1
Switch(config-pmap-c)# police cir percent 20 bc 300 ms pir percent 40 be 400 ms
Switch(config-pmap-c)# exit
Switch(config-pmap)# exit
This example shows how to configure a VLAN-level, two-rate traffic policer to limit outbound traffic to
an average committed rate of 500 kb/s and a peak rate of 1 Mb/s. Traffic marked as conforming to the
average committed rate (500 kb/s) is sent as is. Traffic marked as exceeding 500 kb/s, but not exceeding
1 Mb/s, is marked with IP precedence 2 and then sent. All traffic marked as exceeding 1 Mb/s is dropped.
The burst parameters are set to 10000 bytes.
Switch(config)# class-map match-all vlan203
Switch(config-cmap)# match vlan 203
Switch(config-cmap)# match vlan inner 206
Switch(config-cmap)# exit
Switch(config)# policy-map vlan-policy
Switch(config-pmap)# class vlan203
Switch(config-pmap-c)# police cir 500000 bc 10000 pir 1000000 be 10000 conform-action
transmit exceed-action set-prec-transmit 2 violate-action drop
Switch(config-pmap-c)# exit
Switch(config-pmap)# exit
Switch(config)# interface gigabitethernet1/1/2
Switch(config-if)# switchport trunk encapsulation dot1q
Switch(config-if)# switchport mode trunk
Switch(config-if)# service-policy output vlan-policy
This example shows how to create a hierarchical service-policy in which all levels are present. This
configuration associates a class-level policy map with a VLAN-level policy map, associates the
VLAN-level policy map with a physical-level policy map, and attaches the physical-level policy map to
a physical port.
Within a policy map, the class-default applies to all traffic that is not explicitly matched within the policy
map but does match the parent policy. If no parent policy is configured, the parent policy represents the
physical port. In a physical-level policy map, class-default is the only class that can be configured.
Switch(config)# class-map my-class
Switch(config-cmap)# match ip precedence 1
Switch(config-cmap)# exit
Switch(config)# class-map my-logical-class
Switch(config-cmap)# match vlan 5
Switch(config-cmap)# exit
Switch(config)# policy-map my-class-policy
Switch(config-pmap)# class my-class
Switch(config-pmap-c)# set precedence 2
Switch(config-pmap-c)# exit
Switch(config-pmap)# exit
Switch(config)# policy-map my-logical-policy
Switch(config-pmap)# class my-logical-class
Switch(config-pmap-c)# service-policy my-class-policy
Switch(config-pmap-c)# exit
Switch(config-pmap)# exit
Switch(config)# policy-map my-physical-policy
Switch(config-pmap)# class class-default
Switch(config-pmap-c)# police cir 500000 bc 10000 pir 1000000 be 10000 conform-action
transmit exceed-action set-prec-transmit 2 violate-action drop
Switch(config-pmap-c)# service-policy my-logical-policy
Switch(config-pmap-c)# exit
Switch(config-pmap)# exit
Switch(config)# interface gigabitethernet1/1/1
Switch(config)# service-policy input my-physical-policy
This example shows how to configure a class-level, two-rate traffic policer that uses a CIR based on a
percentage of bandwidth. A CIR of 5 percent is specified. The switch sets the DSCP value to 16 in
packets that conform to the CIR. The port trust state is automatically set to trust CoS.
Switch(config)# class-map c1
Switch(config-cmap)# match 1p dscp 8 9 10 11
Switch(config-cmap)# exit
Switch(config)# policy-map policy1
Switch(config-pmap)# class class1
Switch(config-pmap-c)# police cir percent 5 conform action set-dscp-transmit 16
Switch(config-pmap-c)# exit
Switch(config-pmap)# exit
Switch(config)# interface gigabitethernet1/1/1
Switch(config-if)# service-policy output policy1
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 policy-map policy-map-name Create a policy map by entering the policy-map name, and enter
policy-map configuration mode.
By default, no policy maps are defined.
Step 3 class class-name Specify the name of the class whose traffic policy you want to create
or change, and enter policy-map class configuration mode.
By default, no traffic classes are defined.
Step 4 set {cos new-cos | dscp new-dscp | set Designate the value to set in the traffic class if the packets match the
precedence new-precedence | mpls criteria.
experimental exp-number}
• For cos new-cos, enter the new CoS value assigned to the
classified traffic. The range is 0 to 7.
• For dscp new-dscp, enter the new DSCP value assigned to the
classified traffic. The range is 0 to 63. The specified value sets the
ToS byte in the packet header.
• For precedence new-precedence, enter the new IP-precedence
value assigned to the classified traffic. The range is 0 to 7. The
specified value sets the precedence bit in the IP header.
• For mpls experimental exp-number, enter the new MPLS EXP
value assigned to the classified traffic. The range is 0 to 7. The
specified value sets the MPLS EXP 3-bit field in the packet
header.
Command Purpose
Step 5 exit Return to policy-map configuration mode.
Step 6 exit Return to global configuration mode.
Step 7 interface interface-id Specify an ES port or an EtherChannel port channel, and enter
interface configuration mode.
Step 8 service-policy {input | output} Specify the policy-map name, and apply it to the ES port or
policy-map-name EtherChannel.
Step 9 end Return to privileged EXEC mode.
Step 10 show policy-map [policy-map-name [class Verify your entries.
class-map-name]]
or
show policy-map interface interface-id
Step 11 copy running-config startup-config (Optional) Save your entries in the configuration file.
To delete an existing policy map, use the no policy-map policy-map-name global configuration
command. To delete an existing class, use the no class class-name policy-map configuration command.
To remove an assigned value, use the no set {cos new-cos | dscp new-dscp | precedence new-precedence
| mpls experimental exp-number} policy-map class configuration command. To remove the policy map
and interface association, use the no service-policy output policy-map-name interface configuration
command.
Note If you apply the policy map to an EtherChannel with no ports and then add a standard port to the
EtherChannel, the policy is removed from the EtherChannel because standard ports do not support
hierarchical QoS.
This example shows how to create a class-level policy map called out_pmap. When it is attached to the
ES port, it matches packets with MPLS EXP field 2 and resets this field to 3.
Switch(config)# class-map mpls_2
Switch(config-cmap)# match mpls experimental 2
Switch(config-cmap)# exit
Switch(config)# policy-map out-pmap
Switch(config-pmap)# class mpls_2
Switch(config-pmap-c)# set mpls experimental 3
Switch(config-pmap-c)# exit
Switch(config-pmap)# exit
Switch(config)# interface gigabitethernet1/1/1
Switch(config-if)# service-policy output out-pmap
This example shows how to create a VLAN-level policy map called log-policy. It matches packets with
VLAN 203 and associates a class-level child policy called cls-policy. The child policy matches packets
with MPLS EXP 2 and resets them to 5.
Switch(config)# class-map cls-class
Switch(config-cmap)# match mpls experimental 2
Switch(config-cmap)# exit
Switch(config)# class-map log-class
Switch(config-cmap)# match vlan 203
Switch(config-cmap)# exit
Switch(config)# policy-map cls-policy
Switch(config-pmap)# class cls-class
Switch(config-pmap-c)# set mpls experimental 5
Switch(config-pmap-c)# exit
Switch(config-pmap)# exit
Switch(config)# policy-map log-policy
Switch(config-pmap)# class log-class
Switch(config-pmap-c)# service-policy cls-policy
Switch(config-pmap-c)# exit
Switch(config-pmap)# exit
Switch(config)# interface gigabitethernet1/1/2
Switch(config-if)# switchport trunk encapsulation dot1q
Switch(config-if)# switchport mode trunk
Switch(config-if)# service-policy input log-policy
This example shows how to create a class-level policy map called p-set. When it is attached to the ES
port, it matches packets with CoS field 4 and resets this field to 3. The port trust state is automatically
set to trust CoS.
Switch(config)# class-map c2
Switch(config-cmap)# match cos inner 4
Switch(config-cmap)# exit
Switch(config)# policy-map p-set
Switch(config-pmap)# class c2
Switch(config-pmap-c)# set cos 3
Switch(config-pmap-c)# exit
Switch(config-pmap)# exit
Switch(config)# interface gigabitethernet1/1/1
Switch(config-if)# service-policy output p-set
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 policy-map policy-map-name Create a policy map by entering the policy-map name, and enter
policy-map configuration mode.
By default, no policy maps are defined.
Command Purpose
Step 3 class class-name Specify the name of the class whose traffic policy you want to create
or change, and enter policy-map class configuration mode.
By default, no traffic classes are defined.
Step 4 bandwidth {bandwidth-kbps | percent Specify the minimum bandwidth provided to a class belonging to the
percent} policy map when there is traffic congestion in the switch. If the switch
is not congested, the class receives more bandwidth than you specify
with the bandwidth command.
CBWFQ derives the weight for packets belonging to the class from the
bandwidth allocated to the class. CBWFQ then uses the weight to
ensure that the queue for the class is serviced fairly.
By default, no bandwidth is specified.
You can specify the bandwidth in kb/s or as a percentage:
• For bandwidth-kbps, specify the bandwidth amount in kb/s
assigned to the class. The range is 200 to 2000000. Allocate the
bandwidth in 100-kb/s increments; otherwise, the software rounds
down the bandwidth to the nearest 100-kb/s increment.
• For percent percent, specify the percentage of available
bandwidth assigned to the class. The range is 1 to 100. The sum of
the class bandwidth percentages within a single policy map cannot
exceed 99 percent. Percentage calculations are based on the
bandwidth available at the parent class (or the physical level if it
is the parent).
Specify all the class bandwidths in either kb/s or in percentages, but
not a mix of both. The amount of bandwidth configured should be large
enough to accommodate Layer 2 overhead.
Step 5 queue-limit limit Configure the maximum threshold for tail drop.
For limit, the range is 1 to 32768 packets. The default is 128 packets.
Step 6 exit Return to policy-map configuration mode.
Step 7 exit Return to global configuration mode.
Step 8 interface interface-id Specify an ES port or an EtherChannel port channel, and enter
interface configuration mode.
Step 9 service-policy {input | output} Specify the policy-map name, and apply it to the ES port or
policy-map-name EtherChannel.
Step 10 end Return to privileged EXEC mode.
Step 11 show policy-map [policy-map-name [class Verify your entries.
class-map-name]]
or
show policy-map interface interface-id
Step 12 copy running-config startup-config (Optional) Save your entries in the configuration file.
To delete an existing policy map, use the no policy-map policy-map-name global configuration
command. To delete an existing class, use the no class class-name policy-map configuration command.
To return to the default bandwidth, use the no bandwidth policy-map class configuration command. To
return to the default maximum threshold, use the no queue-limit policy-map class configuration
command.
Note If you apply the policy map to an EtherChannel with no ports and then add a standard port to the
EtherChannel, the policy is removed from the EtherChannel because standard ports do not support
hierarchical QoS.
This example shows how to create a class-level policy map called policy11 for three classes called prec1,
prec2, and prec3. In the policy for these classes, 30 percent of the available bandwidth is assigned to the
queue for the first class, 20 percent is assigned to the queue for the second class, and 10 percent is
assigned to the queue for the third class. Tail drop is enabled on each class queue, packets are queued
until the maximum threshold of 2000 packets is exceeded, and then all the packets are dropped.
Switch(config)# class-map prec1
Switch(config-cmap)# match ip precedence 1
Switch(config-cmap)# exit
Switch(config)# class-map prec2
Switch(config-cmap)# match ip precedence 2
Switch(config-cmap)# exit
Switch(config)# class-map prec3
Switch(config-cmap)# match ip precedence 3
Switch(config-cmap)# exit
Switch(config)# policy-map policy11
Switch(config-pmap)# class prec1
Switch(config-pmap-c)# bandwidth percent 30
Switch(config-pmap-c)# queue-limit 2000
Switch(config-pmap-c)# exit
Switch(config-pmap)# class prec2
Switch(config-pmap-c)# bandwidth percent 20
Switch(config-pmap-c)# queue-limit 2000
Switch(config-pmap-c)# exit
Switch(config-pmap)# class prec3
Switch(config-pmap-c)# bandwidth percent 10
Switch(config-pmap-c)# queue-limit 2000
Switch(config-pmap-c)# exit
Switch(config-pmap)# exit
Switch(config)# interface gigabitethernet1/1/1
Switch(config-if)# service-policy output policy11
This example shows how to create a VLAN-level policy map called vlan-policy for two classes called
vlan203 and vlan202. In the policy for these classes, the minimum bandwidth is set to 2000 kb/s.
Switch(config)# class-map match-all vlan203
Switch(config-cmap)# match vlan 203
Switch(config-cmap)# match vlan inner 206
Switch(config-cmap)# exit
Switch(config)# class-map match-all vlan202
Switch(config-cmap)# match vlan 202
Switch(config-cmap)# match vlan inner 204
Switch(config-cmap)# exit
Switch(config)# policy-map vlan-policy
Switch(config-pmap)# class vlan203
Switch(config-pmap-c)# bandwidth 2000
Switch(config-pmap-c)# exit
Switch(config-pmap)# class vlan202
Switch(config-pmap-c)# bandwidth 2000
Switch(config-pmap-c)# exit
Switch(config-pmap)# exit
Switch(config)# interface gigabitethernet1/1/2
Switch(config-if)# switchport trunk encapsulation dot1q
Switch(config-if)# switchport mode trunk
Switch(config-if)# service-policy output vlan-policy
This example shows how to create a VLAN-level policy map called log-policy. It matches packets with
VLAN 203 and associates a class-level child policy called cls-policy. The child policy matches packets
with a CoS value of 2, sets 50 percent as the available bandwidth for this class, and sets 2000 packets as
the maximum threshold for tail drop. Packets are queued until the maximum threshold is exceeded, and
then all the packets are dropped. Note that when you configure the bandwidth command in a class
policy, you also must configure the bandwidth or shape policy-map class configuration command in the
parent VLAN-level policy.
Switch(config)# class-map cls-class
Switch(config-cmap)# match cos 2
Switch(config-cmap)# exit
Switch(config)# class-map log-class
Switch(config-cmalp)# match vlan 203
Switch(config-cmap)# exit
Switch(config)# policy-map cls-policy
Switch(config-pmap)# class cls-class
Switch(config-pmap-c)# bandwidth percent 50
Switch(config-pmap-c)# queue-limit 2000
Switch(config-pmap-c)# exit
Switch(config-pmap)# exit
Switch(config)# policy-map log-policy
Switch(config-pmap)# class log-class
Switch(config-pmap-c)# bandwidth percent 50
Switch(config-pmap-c)# service-policy cls-policy
Switch(config-pmap-c)# exit
Switch(config-pmap)# exit
Switch(config)# interface gigabitethernet1/1/2
Switch(config-if)# switchport trunk encapsulation dot1q
Switch(config-if)# switchport mode trunk
Switch(config-if)# service-policy output log-policy
• If the average queue size is between the minimum queue threshold and the maximum queue
threshold, the packet is either dropped or queued, depending on the packet-drop probability. The
packet-drop probability is based on the minimum threshold, the maximum threshold, and the
mark-probability denominator. The maximum queue threshold is configured through the
max-threshold option, and the mark-probability denominator is configured through the
mark-prob-denominator option in the random-detect dscp policy-map class configuration
command.
• If the average queue size is greater than the maximum queue threshold, the packet is automatically
dropped.
You enable DSCP-based WRED by using the random-detect dscp-based policy-map class
configuration command in a policy map attached to an ES port or EtherChannel. This command allows
for preferential drop treatment among packets with different DSCP values. The WRED algorithm
discards or marks packets destined for a queue when that queue is congested. It discards packets fairly
and before the queue is full. If you want to enable IP precedence-based WRED instead of DSCP-based
WRED, see the “Configuring CBWFQ and IP Precedence-Based WRED” section on page 34-123.
Before beginning this procedure, make sure that you have reviewed the configuration guidelines and
have created the class map to isolate traffic. For more information, see the “Hierarchical QoS
Configuration Guidelines” section on page 34-104 and the “Classifying Traffic by Using Hierarchical
Class Maps” section on page 34-108. For information on how to configure tail drop, see the
“Configuring CBWFQ and Tail Drop” section on page 34-116.
Beginning in privileged EXEC mode, follow these steps to configure class-level CBWFQ and
DSCP-based WRED in a hierarchical service policy. This procedure is optional. The examples that
follow the procedure show how to configure class-level and VLAN-level CBWFQ and DSCP-based
WRED.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 policy-map policy-map-name Create a policy map by entering the policy-map name, and enter
policy-map configuration mode.
By default, no policy maps are defined.
Step 3 class class-name Specify the name of the class whose traffic policy you want to create
or change, and enter policy-map class configuration mode.
By default, no traffic classes are defined.
Command Purpose
Step 4 bandwidth {bandwidth-kbps | percent Specify the minimum bandwidth provided to a class belonging to the
percent} policy map when there is traffic congestion in the switch. If the switch
is not congested, the class receives more bandwidth than you specify
with the bandwidth command.
CBWFQ derives the weight for packets belonging to the class from the
bandwidth allocated to the class. CBWFQ then uses the weight to
ensure that the queue for the class is serviced fairly.
By default, no bandwidth is specified.
You can specify the bandwidth in kb/s or as a percentage:
• For bandwidth-kbps, specify the bandwidth amount in kb/s
assigned to the class. The range is 200 to 2000000. Allocate the
bandwidth in 100-kb/s increments; otherwise, the software rounds
down the bandwidth to the nearest 100-kb/s increment.
• For percent percent, specify the percentage of available
bandwidth assigned to the class. The range is 1 to 100. The sum of
the class bandwidth percentages within a single policy map cannot
exceed 99 percent. Percentage calculations are based on the
bandwidth available at the parent class (or the physical level if it
is the parent).
Specify all the class bandwidths in either kb/s or in percentages, but
not a mix of both. The amount of bandwidth configured should be large
enough to accommodate Layer 2 overhead.
Step 5 random-detect dscp-based Enable DSCP-based WRED as a drop policy. By default, WRED is
disabled.
Step 6 random-detect dscp dscp min-threshold Specify packet threshold and mark-probability values for a specific
max-threshold mark-prob-denominator DSCP value:
• For dscp, enter a DSCP value. The range is 0 to 63. You also can
enter a mnemonic name for a commonly used value.
• For min-threshold, enter the minimum threshold in packets. The
range is 1 to 32768. When the average queue size reaches the
minimum threshold, WRED randomly drops some packets with
the specified DSCP value.
• For max-threshold, enter the maximum threshold in packets. The
range is 1 to 32768. The default is 128. When the average queue
size exceeds the maximum threshold, WRED drops all packets
with the specified DSCP value.
• For mark-prob-denominator, enter the denominator for the
fraction of packets dropped when the average queue size is at the
maximum threshold. The range is 1 to 65535. The default is 10.
For example, if the denominator is 512, one out of every 512
packets is dropped when the queue is at the maximum threshold.
For a list of the default settings for a specified DSCP value, see the
command reference for this release.
Command Purpose
Step 7 random-detect (Optional) Configure the exponential weight factor for the average
exponential-weighting-constant weight queue-size calculation for WRED. The range is 1 to 16. The default
is 9.
Step 8 exit Return to policy-map configuration mode.
Step 9 exit Return to global configuration mode.
Step 10 interface interface-id Specify an ES port or an EtherChannel port channel, and enter
interface configuration mode.
Step 11 service-policy {input | output} Specify the policy-map name, and apply it to the ES port or
policy-map-name EtherChannel.
Step 12 end Return to privileged EXEC mode.
Step 13 show policy-map [policy-map-name [class Verify your entries.
class-map-name]]
or
show policy-map interface interface-id
Step 14 copy running-config startup-config (Optional) Save your entries in the configuration file.
To delete an existing policy map, use the no policy-map policy-map-name global configuration
command. To delete an existing class, use the no class class-name policy-map configuration command.
To return to the default bandwidth, use the no bandwidth policy-map class configuration command. To
disable DSCP-based WRED, use the no random-detect dscp-based policy-map class configuration
command. To return to the default WRED settings, use the no random-detect dscp dscp policy-map
class configuration command.
Note If you apply the policy map to an EtherChannel with no ports and then add a standard port to the
EtherChannel, the policy is removed from the EtherChannel because standard ports do not support
hierarchical QoS.
This example shows how to configure a class-level policy called policy10. Class c1 has these
characteristics: a minimum of 2000 kb/s of bandwidth is expected to be delivered to this class in the event
of congestion, and a weight factor of 10 is used to calculate the average queue size. To avoid congestion,
DSCP-based WRED packet drop is used instead of tail drop. The minimum threshold for DSCP value 8
is 24, the maximum threshold is 40, and the mark-probability denominator is 512.
Switch(config)# class-map c1
Switch(config-cmap)# match ip dscp 8
Switch(config-cmap)# exit
Switch(config)# policy-map policy10
Switch(config-pmap)# class c1
Switch(config-pmap-c)# bandwidth 2000
Switch(config-pmap-c)# random-detect dscp-based
Switch(config-pmap-c)# random-detect exponential-weighting-constant 10
Switch(config-pmap-c)# random-detect dscp 8 24 40 512
Switch(config-pmap-c)# exit
Switch(config-pmap)# exit
Switch(config)# interface gigabitethernet1/1/1
Switch(config-if)# switchport trunk encapsulation dot1q
Switch(config-if)# switchport mode trunk
Switch(config-if)# service-policy output policy10
This example shows how to configure a VLAN-level policy called parent. It matches packets with VLAN
101 and associates a class-level child policy called policy1. The child policy matches two DSCP values
in two classes. Thirty percentage of the available bandwidth is assigned to the gold class, 20 percent is
assigned to the silver class, and 20 percent is assigned to vlan101. DSCP-based WRED is used as the
drop policy. For the af11 value in the gold class, WRED randomly drops packets with this DSCP when
the minimum threshold reaches 30. When the average queue size exceeds the maximum threshold of 40,
WRED drops all packets with DSCP af11. The mark-probability denominator is set to 10, which means
that one out of every 10 packets is dropped when the average queue is at the maximum threshold. The
configuration has similar settings for af12 in the gold class and for af21 and af22 in the silver class. Note
that when you configure the bandwidth command in a class policy, you also must configure the
bandwidth or shape policy-map class configuration command in the parent VLAN-level policy.
Switch(config)# class-map gold
Switch(config-cmap)# match ip dscp af11 af12
Switch(config-cmap)# exit
Switch(config)# class-map silver
Switch(config-cmap)# match ip dscp af21 af22
Switch(config-cmap)# exit
Switch(config)# class-map vlan101
Switch(config-cmap)# match vlan 101
Switch(config-cmap)# exit
Switch(config)# policy-map policy1
Switch(config-pmap)# class gold
Switch(config-pmap-c)# bandwidth percent 30
Switch(config-pmap-c)# random-detect dscp-based
Switch(config-pmap-c)# random-detect dscp af11 30 40 10
Switch(config-pmap-c)# random-detect dscp af12 25 40 10
Switch(config-pmap-c)# exit
Switch(config-pmap)# class silver
Switch(config-pmap-c)# bandwidth percent 20
Switch(config-pmap-c)# random-detect dscp-based
Switch(config-pmap-c)# random-detect dscp af21 28 35 10
Switch(config-pmap-c)# random-detect dscp af22 26 35 10
Switch(config-pmap-c)# exit
Switch(config-pmap)# exit
Switch(config)# policy-map parent
Switch(config-pmap)# class vlan101
Switch(config-pmap-c)# bandwidth percent 30
Switch(config-pmap-c)# service-policy policy1
Switch(config-pmap-c)# exit
Switch(config-pmap)# exit
Switch(config)# interface gigabitethernet1/1/1
Switch(config-if)# service-policy output parent
algorithm discards or marks packets destined for a queue when that queue is congested. It discards
packets fairly and before the queue is full. Packets with high IP-precedence values are preferred over
packets with low IP-precedence values. If you want to enable DSCP-based WRED instead of IP
precedence-based WRED, see the “Configuring CBWFQ and DSCP-Based WRED” section on
page 34-119
Before beginning this procedure, make sure that you have reviewed the configuration guidelines and
have created the class map to isolate traffic. For more information, see the “Hierarchical QoS
Configuration Guidelines” section on page 34-104 and the “Classifying Traffic by Using Hierarchical
Class Maps” section on page 34-108. For information on how to configure tail drop, see the
“Configuring CBWFQ and Tail Drop” section on page 34-116.
Beginning in privileged EXEC mode, follow these steps to configure class-level CBWFQ and IP
precedence-based WRED in a hierarchical service policy. This procedure is optional. The examples that
follow the procedure show how to configure class-level and VLAN-level CBWFQ and IP
precedence-based WRED.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 policy-map policy-map-name Create a policy map by entering the policy-map name, and enter
policy-map configuration mode.
By default, no policy maps are defined.
Step 3 class class-name Specify the name of the class whose traffic policy you want to create
or change, and enter policy-map class configuration mode.
By default, no traffic classes are defined.
Step 4 bandwidth {bandwidth-kbps | percent Specify the minimum bandwidth provided to a class belonging to the
percent} policy map when there is traffic congestion in the switch. If the switch
is not congested, the class receives more bandwidth than you specify
with the bandwidth command.
CBWFQ derives the weight for packets belonging to the class from the
bandwidth allocated to the class. CBWFQ then uses the weight to
ensure that the queue for the class is serviced fairly.
By default, no bandwidth is specified.
You can specify the bandwidth in kb/s or as a percentage:
• For bandwidth-kbps, specify the bandwidth amount in kb/s
assigned to the class. The range is 200 to 2000000. Allocate the
bandwidth in 100-kb/s increments; otherwise, the software rounds
down the bandwidth to the nearest 100-kb/s increment.
• For percent percent, specify the percentage of available
bandwidth assigned to the class. The range is 1 to 100. The sum of
the class bandwidth percentages within a single policy map cannot
exceed 99 percent. Percentage calculations are based on the
bandwidth available at the parent class (or the physical level if it
is the parent).
Specify all the class bandwidths in either kb/s or in percentages, but
not a mix of both. The amount of bandwidth configured should be large
enough to accommodate Layer 2 overhead.
Command Purpose
Step 5 random-detect precedence-based Enable IP precedence-based WRED as a drop policy. By default,
WRED is disabled.
Step 6 random-detect precedence ip-precedence Specify packet threshold and mark-probability values for a specific IP
min-threshold max-threshold precedence value:
mark-prob-denominator
• For ip-precedence, specify an IP precedence value. The range is 0
to 7.
• For min-threshold, specify the minimum threshold in packets. The
range is 1 to 32768. When the average queue size reaches the
minimum threshold, WRED randomly drops some packets with
the specified precedence value.
• For max-threshold, specify the maximum threshold in packets.
The range is 1 to 32768. The default is 128. When the average
queue size exceeds the maximum threshold, WRED drops all
packets with the specified precedence value.
• For mark-prob-denominator, specify the denominator for the
fraction of packets dropped when the average queue size is at the
maximum threshold. The range is 1 to 65535. The default is 10.
For example, if the denominator is 512, one out of every 512
packets is dropped when the queue is at the maximum threshold.
For a list of the default settings for a specified IP precedence value, see
the command reference for this release.
Step 7 random-detect (Optional) Configure the exponential weight factor for the average
exponential-weighting-constant weight queue-size calculation for WRED. The range is 1 to 16. The default
is 9.
Step 8 exit Return to policy-map configuration mode.
Step 9 exit Return to global configuration mode.
Step 10 interface interface-id Specify an ES port or an EtherChannel port channel, and enter
interface configuration mode.
Step 11 service-policy {input | output} Specify the policy-map name, and apply it to the ES port or
policy-map-name EtherChannel.
Step 12 end Return to privileged EXEC mode.
Step 13 show policy-map [policy-map-name [class Verify your entries.
class-map-name]]
or
show policy-map interface interface-id
Step 14 copy running-config startup-config (Optional) Save your entries in the configuration file.
To delete an existing policy map, use the no policy-map policy-map-name global configuration
command. To delete an existing class, use the no class class-name policy-map configuration command.
To return to the default bandwidth, use the no bandwidth policy-map class configuration command. To
disable IP precedence-based WRED, use the no random-detect precedence-based policy-map class
configuration command. To return to the default WRED settings, use the no random-detect precedence
ip-precedence policy-map class configuration command.
Note If you apply the policy map to an EtherChannel with no ports and then add a standard port to the
EtherChannel, the policy is removed from the EtherChannel because standard ports do not support
hierarchical QoS.
This example shows how to configure a class-level policy called policy10. Class c1 has these
characteristics: a minimum of 2000 kb/s of bandwidth is expected to be delivered to this class in the event
of congestion, and a weight factor of 10 is used to calculate the average queue size. To avoid congestion,
WRED packet drop is used instead of tail drop. IP precedence is reset for levels 0 to 2. The minimum
threshold for IP precedence value 0 is 32, the maximum threshold is 256, and the mark-probability
denominator is 100. IP precedence values 1 and 2 have similar thresholds and probability denominators.
Switch(config)# class-map c1
Switch(config-cmap)# match ip precedence 0 1 2
Switch(config-cmap)# exit
Switch(config)# policy-map policy10
Switch(config-pmap)# class c1
Switch(config-pmap-c)# bandwidth 2000
Switch(config-pmap-c)# random-detect precedence-based
Switch(config-pmap-c)# random-detect exponential-weighting-constant 10
Switch(config-pmap-c)# random-detect precedence 0 32 256 100
Switch(config-pmap-c)# random-detect precedence 1 64 256 100
Switch(config-pmap-c)# random-detect precedence 2 96 256 100
Switch(config-pmap-c)# exit
Switch(config-pmap)# exit
Switch(config)# interface gigabitethernet1/1/1
Switch(config-if)# switchport trunk encapsulation dot1q
Switch(config-if)# switchport mode trunk
Switch(config-if)# service-policy output policy10
This example shows how to configure a VLAN-level policy called parent. It matches packets with VLAN
101 and associates a class-level child policy called policy1. The child policy matches two IP precedence
values in two classes. Thirty percentage of the available bandwidth is assigned to the gold class, 20
percent is assigned to the silver class, and 30 percent is assigned to vlan101. IP precedence-based WRED
is used as the drop policy. For the IP precedence 0 in the gold class, WRED randomly drops packets with
this IP precedence when the minimum threshold reaches 30. When the average queue size exceeds the
maximum threshold of 40, WRED drops all packets with IP precedence 0. The mark-probability
denominator is set to 10, which means that one out of every 10 packets is dropped when the average
queue is at the maximum threshold. The configuration has similar settings for IP precedence 3 in the
silver class. Note that when you configure the bandwidth command in a class policy, you also must
configure the bandwidth or shape policy-map class configuration command in the parent VLAN-level
policy.
Switch(config)# class-map gold
Switch(config-cmap)# match ip precedence 0
Switch(config-cmap)# exit
Switch(config)# class-map silver
Switch(config-cmap)# match ip precedence 3
Switch(config-cmap)# exit
Switch(config)# class-map vlan101
Switch(config-cmap)# match vlan 101
Switch(config-cmap)# exit
Switch(config)# policy-map policy1
Switch(config-pmap)# class gold
Switch(config-pmap-c)# bandwidth percent 30
Switch(config-pmap-c)# random-detect precedence-based
Switch(config-pmap-c)# random-detect precedence 0 30 40 10
Switch(config-pmap-c)# exit
Switch(config-pmap)# class silver
Enabling LLQ
LLQ provides strict-priority queueing for a traffic class. It enables delay-sensitive data, such as voice,
to be sent before packets in other queues are sent. The priority queue is serviced first until it is empty.
Only one traffic stream can be destined for the priority queue per class-level policy. The priority queue
restricts all traffic streams in the same hierarchy, and you should use care when configuring this feature.
You enable the priority queue for a traffic class by using the priority policy-map class configuration
command in a policy map attached to an ES port or EtherChannel.
Note To avoid losing priority traffic on an ES port when the switch is congested, you can use both
strict-priority queueing and egress priority queueing. Note that when you map certain traffic classes to
the egress priority queue, they are not automatically placed into the strict-priority queue. You must enter
both the priority policy-map class configuration and the priority-queue out interface configuration
commands. For more information, see the “Configuring the Egress Priority Queue” section on
page 34-97.
Before beginning this procedure, make sure that you have reviewed the configuration guidelines and
have created the class map to isolate traffic. For more information, see the “Hierarchical QoS
Configuration Guidelines” section on page 34-104 and the “Classifying Traffic by Using Hierarchical
Class Maps” section on page 34-108.
Beginning in privileged EXEC mode, follow these steps to enable class-level priority queueing in a
hierarchical service policy. This procedure is optional. The examples that follow the procedure show
how to enable class-level and VLAN-level priority queueing.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 policy-map policy-map-name Create a policy map by entering the policy-map name, and enter
policy-map configuration mode.
By default, no policy maps are defined.
Step 3 class class-name Specify the name of the class whose traffic policy you want to create
or change, and enter policy-map class configuration mode.
By default, no traffic classes are defined.
Step 4 priority Enable the strict-priority queue, and give priority to a class of traffic.
By default, strict-priority queueing is disabled.
Step 5 exit Return to policy-map configuration mode.
Command Purpose
Step 6 exit Return to global configuration mode.
Step 7 interface interface-id Specify an ES port or an EtherChannel port channel, and enter
interface configuration mode.
Step 8 service-policy {input | output} Specify the policy-map name, and apply it to the ES port or
policy-map-name EtherChannel.
Step 9 end Return to privileged EXEC mode.
Step 10 show policy-map [policy-map-name [class Verify your entries.
class-map-name]]
or
show policy-map interface interface-id
Step 11 copy running-config startup-config (Optional) Save your entries in the configuration file.
To delete an existing policy map, use the no policy-map policy-map-name global configuration
command. To delete an existing class, use the no class class-name policy-map configuration command.
To disable the priority queue, use the no priority policy-map class configuration command.
This example shows how to configure a class-level policy called policy1 that has two classes. Class 1 has
10 percent of the available bandwidth. Class 2 is configured as the priority queue, which is serviced first
until it is empty.
Switch(config)# class-map class1
Switch(config-cmap)# match mpls experimental 2 3 4
Switch(config-cmap)# exit
Switch(config)# class-map class2
Switch(config-cmap)# match mpls experimental 7
Switch(config-cmap)# exit
Switch(config)# policy-map policy1
Switch(config-pmap)# class class1
Switch(config-pmap-c)# bandwidth percent 10
Switch(config-pmap-c)# exit
Switch(config-pmap)# class class2
Switch(config-pmap-c)# priority
Switch(config-pmap-c)# exit
Switch(config-pmap)# exit
Switch(config)# interface gigabitethernet1/1/2
Switch(config-if)# service-policy output policy1
This example shows how to configure a VLAN-level policy called parent. It matches packets with VLAN
101 and associates a class-level child policy called policy1. The gold class is configured as the priority
queue, whereas the silver class and vlan101 class each have 20 percent of the available bandwidth
assigned to them. DSCP-based WRED is used as the drop policy. For the af21 value in the silver class,
WRED randomly drops packets with this DSCP when the minimum threshold reaches 28. When the
average queue size exceeds the maximum threshold of 35, WRED drops all packets with DSCP af21.
The mark-probability denominator is set to 10, which means that one out of every 10 packets is dropped
when the average queue is at the maximum threshold. The configuration has similar settings for af22 in
the silver class.
Switch(config)# class-map gold
Switch(config-cmap)# match ip dscp af11 af12
Switch(config-cmap)# exit
Switch(config)# class-map silver
Switch(config-cmap)# match ip dscp af21 af22
Switch(config-cmap)# exit
Switch(config)# class-map vlan101
Configuring Shaping
Shaping provides a process for delaying out-of-profile packets in queues so that they conform to a
specified profile. Shaping is distinct from policing. Policing drops packets that exceed a configured
threshold, but shaping buffers packets so that traffic remains within a threshold. Shaping offers greater
smoothness in handling traffic than policing. You can configure average-rate traffic shaping on a traffic
class within a policy map at the class level, at the VLAN level, and at the physical level by using the
shape policy-map class configuration command. At the physical level of the hierarchy, you can shape
only the class-default class in a policy attached to an ES port or EtherChannel.
Before beginning this procedure, make sure that you have reviewed the configuration guidelines and
have created the class map to isolate traffic. For more information, see the “Hierarchical QoS
Configuration Guidelines” section on page 34-104 and the “Classifying Traffic by Using Hierarchical
Class Maps” section on page 34-108.
Beginning in privileged EXEC mode, follow these steps to configure class-level shaping in a hierarchical
service policy. This procedure is optional. The examples that follow the procedure show how to
configure class-level, VLAN-level, and physical-level shaping.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 policy-map policy-map-name Create a policy map by entering the policy-map name, and enter
policy-map configuration mode.
By default, no policy maps are defined.
Step 3 class class-name Specify the name of the class whose traffic policy you want to create
or change, and enter policy-map class configuration mode.
By default, no traffic classes are defined.
Command Purpose
Step 4 shape average cir-bps Enable average-rate traffic shaping. Specify the committed
information rate, the bit rate that traffic is shaped to, in b/s. This is the
access bit rate that you have contracted for with your service provider
or the service levels that you intend to maintain. The range is 64000 to
2000000000 b/s.
Allocate the shaped rate in 100-kb/s increments; otherwise, the
software rounds down the bandwidth to the nearest 100-kb/s
increment.
By default, average-rate traffic shaping is disabled.
Step 5 exit Return to policy-map configuration mode.
Step 6 exit Return to global configuration mode.
Step 7 interface interface-id Specify an ES port or an EtherChannel port channel, and enter
interface configuration mode.
Step 8 service-policy {input | output} Specify the policy-map name, and apply it to the ES port or
policy-map-name EtherChannel.
Step 9 end Return to privileged EXEC mode.
Step 10 show policy-map [policy-map-name [class Verify your entries.
class-map-name]]
or
show policy-map interface interface-id
Step 11 copy running-config startup-config (Optional) Save your entries in the configuration file.
To delete an existing policy map, use the no policy-map policy-map-name global configuration
command. To delete an existing class, use the no class class-name policy-map configuration command.
To disable the average-rate traffic shaping, use the no shape average policy-map class configuration
command.
This example shows how to configure class-level, average-rate shaping. It limits traffic class class1 to a
data transmission rate of 256 kb/s.
Switch(config)# class-map class1
Switch(config-cmap)# match cos 0 1 2 3
Switch(config-cmap)# exit
Switch(config)# policy-map policy1
Switch(config-pmap)# class class1
Switch(config-pmap-c)# shape average 256000
Switch(config-pmap-c)# exit
Switch(config-pmap)# exit
Switch(config)# interface gigabitethernet1/1/1
Switch(config-if)# service-policy output policy1
This example shows how to configure VLAN-level, average-rate shaping. It limits each traffic class,
vlan101 and vlan102, to a data transmission rate of 400 Mb/s.
Switch(config)# class-map match-all vlan101
Switch(config-cmap)# match vlan 101
Switch(config-cmap)# exit
Switch(config)# class-map match-all vlan102
Switch(config-cmap)# match vlan 102
Switch(config-cmap)# exit
Switch(config)# policy-map vlan-policy
This example shows how to shape the class. This configuration associates a class-level policy map with
a VLAN-level policy map and then associates the VLAN-level policy map with a physical-level policy
map.
Switch(config)# class-map my-class
Switch(config-cmap)# match ip precedence 1
Switch(config-cmap)# exit
Switch(config)# class-map my-logical-class
Switch(config-cmap)# match vlan 5
Switch(config-cmap)# exit
Switch(config)# policy-map my-class-policy
Switch(config-pmap)# class my-class
Switch(config-pmap-c)# set precedence 2
Switch(config-pmap-c)# exit
Switch(config-pmap)# exit
Switch(config)# policy-map my-logical-policy
Switch(config-pmap)# class my-logical-class
Switch(config-pmap-c)# shape average 400000000
Switch(config-pmap-c)# service-policy my-class-policy
Switch(config-pmap-c)# exit
Switch(config-pmap)# exit
Switch(config)# policy-map my-physical-policy
Switch(config-pmap)# class class-default
Switch(config-pmap-c)# shape average 500000000
Switch(config-pmap-c)# service-policy my-logical-policy
Command Purpose
show class-map [class-map-name] Display QoS class maps, which define the match criteria to
classify traffic.
show mls qos Display global QoS configuration information.
show policy-map [policy-map-name [class Display QoS policy maps, which define the traffic policy for a
class-map-name]] traffic class.
show policy-map interface interface-id output [class Display QoS policy-map information for the specified ES port,
class-name]] and display statistics for an individual class.
This chapter describes how to configure EtherChannels on Layer 2 and Layer 3 ports on the
Catalyst 3750 Metro switch. EtherChannel provides fault-tolerant high-speed links between switches,
routers, and servers. You can use it to increase the bandwidth between the wiring closets and the data
center, and you can deploy it anywhere in the network where bottlenecks are likely to occur.
EtherChannel provides automatic recovery for the loss of a link by redistributing the load across the
remaining links. If a link fails, EtherChannel redirects traffic from the failed link to the remaining links
in the channel without intervention.
This chapter also describes how to configure link-state tracking.
Note For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
Understanding EtherChannels
These sections describe how EtherChannels work:
• EtherChannel Overview, page 35-2
• Port-Channel Interfaces, page 35-3
• Port Aggregation Protocol, page 35-4
• Link Aggregation Control Protocol, page 35-5
• EtherChannel On Mode, page 35-6
• Load Balancing and Forwarding Methods, page 35-6
EtherChannel Overview
An EtherChannel consists of individual Fast Ethernet or Gigabit Ethernet links bundled into a single
logical link as shown in Figure 35-1.
Catalyst 8500
series switch
Gigabit EtherChannel
1000BASE-X 1000BASE-X
10/100 10/100
Switched Switched
links links
101237
Workstations Workstations
The EtherChannel provides full-duplex bandwidth up to 800 Mbps (Fast EtherChannel) or 2 Gbps
(Gigabit EtherChannel) between your switch and another switch or host. You cannot bundle standard
Gigabit Ethernet ports with the enhanced-services (ES) Gigabit Ethernet ports.
Each EtherChannel can consist of up to eight compatibly configured Ethernet ports. All ports in each
EtherChannel must be configured as either Layer 2 or Layer 3 ports. For Catalyst 3750 Metro switches,
the number of EtherChannels is limited to 12. For more information, see the “EtherChannel
Configuration Guidelines” section on page 35-9. The EtherChannel Layer 3 ports are made up of routed
ports. Routed ports are physical ports configured to be in Layer 3 mode by using the no switchport
interface configuration command. For more information, see the Chapter 9, “Configuring Interface
Characteristics.”
You can configure an EtherChannel in one of these modes: Port Aggregation Protocol (PAgP), Link
Aggregation Control Protocol (LACP), or On mode. Configure both ends of the EtherChannel in the
same mode:
• When you configure one end of an EtherChannel in either PAgP or LACP mode, the system
negotiates with the other end of the channel to determine which ports should become active.
Incompatible ports are suspended.
• When you configure an EtherChannel in the on mode, no negotiations take place. The switch forces
all compatible ports to become active in the EtherChannel. The other end of the channel (on the other
switch) must also be configured in the on mode; otherwise, packet loss can occur.
Beginning with Cisco IOS Release 12.2(35)SE, instead of a suspended state, the local port is put
into an independent state and continues to carry data traffic as would any other single link. The port
configuration does not change, but the port does not participate in the EtherChannel.
If a link within an EtherChannel fails, traffic previously carried over that failed link moves to the
remaining links within the EtherChannel. If traps are enabled on the switch, a trap is sent for a failure
that identifies the switch, the EtherChannel, and the failed link. Inbound broadcast and multicast packets
on one link in an EtherChannel are blocked from returning on any other link of the EtherChannel.
Port-Channel Interfaces
When you create an EtherChannel, a port-channel logical interface is involved:
• With Layer 2 ports, use the channel-group interface configuration command to dynamically create
the port-channel logical interface.
You also can use the interface port-channel port-channel-number global configuration command
to manually create the port-channel logical interface, but then you must use the channel-group
channel-group-number command to bind the logical interface to a physical port. The
channel-group-number can be the same as the port-channel-number, or you can use a new number.
If you use a new number, the channel-group command dynamically creates a new port channel.
• With Layer 3 ports, you should manually create the logical interface by using the interface
port-channel global configuration command followed by the no switchport interface configuration
command. Then you manually assign an interface to the EtherChannel by using the channel-group
interface configuration command.
For both Layer 2 and Layer 3 ports, the channel-group command binds the physical port and the logical
interface together as shown in Figure 35-2.
Each EtherChannel has a port-channel logical interface numbered from 1 to 12. This port-channel
interface number corresponds to the one specified with the channel-group interface configuration
command.
Figure 35-2 Relationship of Physical Ports, Logical Port Channels, and Channel Groups
Logical
port-channel
Channel-group
binding
101238
Physical ports
After you configure an EtherChannel, configuration changes applied to the port-channel apply to all the
physical ports assigned to the port-channel. Configuration changes applied to the physical port affect
only the port where you apply the configuration. To change the parameters of all ports in an
EtherChannel, apply configuration commands to the port-channel interface, for example, spanning-tree
commands or commands to configure a Layer 2 EtherChannel as a trunk.
PAgP Modes
Table 35-1 shows the user-configurable EtherChannel PAgP modes for the channel-group interface
configuration command.
Mode Description
auto Places a port into a passive negotiating state, in which the port responds to PAgP packets
it receives but does not start PAgP packet negotiation. This setting minimizes the
transmission of PAgP packets.
desirable Places a port into an active negotiating state, in which the port starts negotiations with other
ports by sending PAgP packets.
Switch ports exchange PAgP packets only with partner ports configured in the auto or desirable modes.
Ports configured in the on mode do not exchange PAgP packets.
Both the auto and desirable modes enable ports to negotiate with partner ports to form an EtherChannel
based on criteria such as port speed and, for Layer 2 EtherChannels, trunking state and VLAN numbers.
Ports can form an EtherChannel when they are in different PAgP modes as long as the modes are
compatible. For example:
• A port in the desirable mode can form an EtherChannel with another port that is in the desirable or
auto mode.
• A port in the auto mode can form an EtherChannel with another port in the desirable mode.
A port in the auto mode cannot form an EtherChannel with another port that is also in the auto mode
because neither port starts PAgP negotiation.
If your switch is connected to a partner that is PAgP-capable, you can configure the switch port for
nonsilent operation by using the non-silent keyword. If you do not specify non-silent with the auto or
desirable mode, silent mode is assumed.
Use the silent mode when the switch is connected to a device that is not PAgP-capable and seldom, if
ever, sends packets. An example of a silent partner is a file server or a packet analyzer that is not
generating traffic. In this case, running PAgP on a physical port connected to a silent partner prevents
that switch port from ever becoming operational. However, the silent setting allows PAgP to operate, to
attach the port to a channel group, and to use the port for transmission.
LACP Modes
Table 35-2 shows the user-configurable EtherChannel LACP modes for the channel-group interface
configuration command.
Mode Description
active Places a port into an active negotiating state in which the port starts negotiations with other
ports by sending LACP packets.
passive Places a port into a passive negotiating state in which the port responds to LACP packets
that it receives, but does not start LACP packet negotiation. This setting minimizes the
transmission of LACP packets.
Both the active and passive LACP modes enable ports to negotiate with partner ports to form an
EtherChannel based on criteria such as port speed and, for Layer 2 EtherChannels, trunking state and
VLAN numbers.
Ports can form an EtherChannel when they are in different LACP modes as long as the modes are
compatible. For example:
• A port in the active mode can form an EtherChannel with another port that is in the active or passive
mode.
• A port in the passive mode cannot form an EtherChannel with another port that is also in the passive
mode because neither port starts LACP negotiation.
EtherChannel On Mode
EtherChannel on mode can be used to manually configure an EtherChannel. The on mode forces a port
to join an EtherChannel without negotiations. The on mode can be useful if the remote device does not
support PAgP or LACP. In the on mode, a usable EtherChannel exists only when the switches at both
ends of the link are configured in the on mode.
Ports that are configured in the on mode in the same channel group must have compatible port
characteristics, such as speed and duplex. Ports that are not compatible are suspended, even though they
are configured in the on mode.
Caution You should use care when using the on mode. This is a manual configuration, and ports on both ends of
the EtherChannel must have the same configuration. If the group is misconfigured, packet loss or
spanning-tree loops can occur.
With destination-MAC address forwarding, when packets are forwarded to an EtherChannel, they are
distributed across the ports in the channel based on the destination host’s MAC address of the incoming
packet. Therefore, packets to the same destination are forwarded over the same port, and packets to a
different destination are sent on a different port in the channel.
With source-and-destination MAC address forwarding, when packets are forwarded to an EtherChannel,
they are distributed across the ports in the channel based on both the source and destination MAC
addresses. This forwarding method, a combination source-MAC and destination-MAC address
forwarding methods of load distribution, can be used if it is not clear whether source-MAC or
destination-MAC address forwarding is better suited on a particular switch. With source-and-destination
MAC-address forwarding, packets sent from host A to host B, host A to host C, and host C to host B
could all use different ports in the channel.
With source-IP address-based forwarding, when packets are forwarded to an EtherChannel, they are
distributed across the ports in the EtherChannel based on the source-IP address of the incoming packet.
Therefore, to provide load-balancing, packets from different IP addresses use different ports in the
channel, but packets from the same IP address use the same port in the channel.
With destination-IP address-based forwarding, when packets are forwarded to an EtherChannel, they are
distributed across the ports in the EtherChannel based on the destination-IP address of the incoming
packet. Therefore, to provide load-balancing, packets from the same IP source address sent to different
IP destination addresses could be sent on different ports in the channel. But packets sent from different
source IP addresses to the same destination IP address are always sent on the same port in the channel.
With source-and-destination IP address-based forwarding, when packets are forwarded to an
EtherChannel, they are distributed across the ports in the EtherChannel based on both the source and
destination IP addresses of the incoming packet. This forwarding method, a combination of source-IP
and destination-IP address-based forwarding, can be used if it is not clear whether source-IP or
destination-IP address-based forwarding is better suited on a particular switch. In this method, packets
sent from the IP address A to IP address B, from IP address A to IP address C, and from IP address C to
IP address B could all use different ports in the channel.
Different load-balancing methods have different advantages, and the choice of a particular
load-balancing method should be based on the position of the switch in the network and the kind of
traffic that needs to be load-distributed. In Figure 35-3, an EtherChannel of four workstations
communicates with a router. Because the router is a single-MAC-address device, source-based
forwarding on the switch EtherChannel ensures that the switch uses all available bandwidth to the router.
The router is configured for destination-based forwarding because the large number of workstations
ensures that the traffic is evenly distributed from the router EtherChannel.
Use the option that provides the greatest variety in your configuration. For example, if the traffic on a
channel is going only to a single MAC address, using the destination-MAC address always chooses the
same link in the channel. Using source addresses or IP addresses might result in better load balancing.
Switch with
source-based
forwarding enabled
EtherChannel
Cisco router
with destination-based
forwarding enabled
101239
Configuring EtherChannels
These sections describe how to configure EtherChannel on Layer 2 and Layer 3 ports:
• Default EtherChannel Configuration, page 35-9
• EtherChannel Configuration Guidelines, page 35-9
• Configuring Layer 2 EtherChannels, page 35-10 (required)
• Configuring Layer 3 EtherChannels, page 35-13 (required)
• Configuring EtherChannel Load Balancing, page 35-16 (optional)
• Configuring the PAgP Learn Method and Priority, page 35-17 (optional)
• Configuring LACP Hot-Standby Ports, page 35-18 (optional)
Note Make sure that the ports are correctly configured. For more information, see the “EtherChannel
Configuration Guidelines” section on page 35-9.
Note After you configure an EtherChannel, configuration changes applied to the port-channel interface apply
to all the physical ports assigned to the port-channel interface, and configuration changes applied to the
physical port affect only the port where you apply the configuration.
Note In software releases earlier than Cisco IOS Release 12.2(25)EY, if 802.1x is enabled on a
not-yet-active port of an EtherChannel, the port does not join the EtherChannel.
Beginning in privileged EXEC mode, follow these steps to assign a Layer 2 Ethernet port to a Layer 2
EtherChannel. This procedure is required.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify a physical port to configure, and enter interface
configuration mode.
Valid interfaces include physical ports.
For a PAgP EtherChannel, you can configure up to eight ports of
the same type and speed for the same group.
For a LACP EtherChannel, you can configure up to 16 Ethernet
ports of the same type. Up to eight ports can be active, and up to
eight ports can be in standby mode.
Step 3 switchport mode {access | trunk} Assign all ports as static-access ports in the same VLAN, or
configure them as trunks.
switchport access vlan vlan-id
If you configure the port as a static-access port, assign it to only
one VLAN. The range is 1 to 4094.
Command Purpose
Step 4 channel-group channel-group-number mode Assign the port to a channel group, and specify the PAgP or the
{auto [non-silent] | desirable [non-silent] | on} | LACP mode.
{active | passive}
For channel-group-number, the range is 1 to 12.
For mode, select one of these keywords:
• auto—Enables PAgP only if a PAgP device is detected. It
places the port into a passive negotiating state, in which the
port responds to PAgP packets it receives but does not start
PAgP packet negotiation.
• desirable—Unconditionally enables PAgP. It places the port
into an active negotiating state, in which the port starts
negotiations with other ports by sending PAgP packets.
• on—Forces the port to channel without PAgP or LACP. With
the on mode, a usable EtherChannel exists only when a port
group in the on mode is connected to another port group in
the on mode.
• non-silent—(Optional) If your switch is connected to a
partner that is PAgP-capable, configure the switch port for
nonsilent operation when the port is in the auto or desirable
mode. If you do not specify non-silent, silent is assumed.
The silent setting is for connections to file servers or packet
analyzers. This setting allows PAgP to operate, to attach the
port to a channel group, and to use the port for transmission.
• active—Enables LACP only if a LACP device is detected.
It places the port into an active negotiating state in which
the port starts negotiations with other ports by sending
LACP packets.
• passive—Enables LACP on the port and places it into a
passive negotiating state in which the port responds to LACP
packets that it receives, but does not start LACP packet
negotiation.
For information on compatible modes for the switch and its
partner, see the “PAgP Modes” section on page 35-4 and the
“LACP Modes” section on page 35-5.
Step 5 end Return to privileged EXEC mode.
Step 6 show running-config Verify your entries.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove a port from the EtherChannel group, use the no channel-group interface configuration
command.
This example shows how to configure an EtherChannel. It assigns two ports as static-access ports in
VLAN 10 to channel 5 with the PAgP mode desirable:
Switch# configure terminal
Switch(config)# interface range fastethernet1/0/4 -5
Switch(config-if-range)# switchport mode access
Switch(config-if-range)# switchport access vlan 10
Switch(config-if-range)# channel-group 5 mode desirable non-silent
Switch(config-if-range)# end
This example shows how to configure an EtherChannel. It assigns two ports as static-access ports in
VLAN 10 to channel 5 with the LACP mode active:
Switch# configure terminal
Switch(config)# interface range gigabitethernet1/0/1 -2
Switch(config-if-range)# switchport mode access
Switch(config-if-range)# switchport access vlan 10
Switch(config-if-range)# channel-group 5 mode active
Switch(config-if-range)# end
Note To move an IP address from a physical port to an EtherChannel, you must delete the IP address from the
physical port before configuring it on the port-channel interface. Beginning in privileged EXEC mode,
follow these steps to create a port-channel interface for a Layer 3 EtherChannel. This procedure is
required.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface port-channel port-channel-number Create the port-channel logical interface, and enter interface
configuration mode.
For port-channel-number, the range is 1 to 12.
Step 3 no switchport Put the interface into Layer 3 mode.
Step 4 ip address ip-address mask Assign an IP address and subnet mask to the EtherChannel.
Step 5 end Return to privileged EXEC mode.
Step 6 show etherchannel channel-group-number detail Verify your entries.
Command Purpose
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
Step 8 Assign an Ethernet port to the Layer 3 EtherChannel. For
more information, see the “Configuring the Physical
Interfaces” section on page 35-14.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify a physical port to configure, and enter interface
configuration mode.
For a PAgP EtherChannel, you can configure up to eight ports of
the same type and speed for the same group.
For a LACP EtherChannel, you can configure up to 16 Ethernet
ports of the same type. Up to eight ports can be active, and up to
eight ports can be in standby mode.
Step 3 no ip address Ensure that there is no IP address assigned to the physical port.
Step 4 no switchport Put the port into Layer 3 mode.
Command Purpose
Step 5 channel-group channel-group-number mode Assign the port to a channel group, and specify the PAgP or the
{auto [non-silent] | desirable [non-silent] | on} | LACP mode.
{active | passive}
For channel-group-number, the range is 1 to 12. This number
must be the same as the port-channel-number (logical port)
configured in the “Creating Port-Channel Logical Interfaces”
section on page 35-13.
For mode, select one of these keywords:
• auto—Enables PAgP only if a PAgP device is detected. It
places the port into a passive negotiating state, in which the
port responds to PAgP packets it receives but does not start
PAgP packet negotiation.
• desirable—Unconditionally enables PAgP. It places the port
into an active negotiating state, in which the port starts
negotiations with other ports by sending PAgP packets.
• on—Forces the port to channel without PAgP or LACP. With
the on mode, a usable EtherChannel exists only when a port
group in the on mode is connected to another port group in
the on mode.
• non-silent—(Optional) If your switch is connected to a
partner that is PAgP capable, configure the switch port for
nonsilent operation when the port is in the auto or desirable
mode. If you do not specify non-silent, silent is assumed.
The silent setting is for connections to file servers or packet
analyzers. This setting allows PAgP to operate, to attach the
port to a channel group, and to use the port for transmission.
• active—Enables LACP only if a LACP device is detected.
It places the port into an active negotiating state in which
the port starts negotiations with other ports by sending
LACP packets.
• passive—Enables LACP on the port and places it into a
passive negotiating state in which the port responds to LACP
packets that it receives, but does not start LACP packet
negotiation.
For information on compatible modes for the switch and its
partner, see the “PAgP Modes” section on page 35-4 and the
“LACP Modes” section on page 35-5.
Step 6 end Return to privileged EXEC mode.
Step 7 show running-config Verify your entries.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
This example shows how to configure an EtherChannel. It assigns two ports to channel 5 with the LACP
mode active:
Switch# configure terminal
Switch(config)# interface range fastethernet1/0/4 -5
Switch(config-if-range)# no ip address
Switch(config-if-range)# no switchport
Switch(config-if-range)# channel-group 5 mode active
Switch(config-if-range)# end
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 port-channel load-balance {dst-ip | dst-mac | Configure an EtherChannel load-balancing method.
src-dst-ip | src-dst-mac | src-ip | src-mac}
The default is src-mac.
Select one of these load-distribution methods:
• dst-ip—Load distribution is based on the destination-host IP
address.
• dst-mac—Load distribution is based on the destination-host
MAC address of the incoming packet.
• src-dst-ip—Load distribution is based on the
source-and-destination host-IP address.
• src-dst-mac—Load distribution is based on the
source-and-destination host-MAC address.
• src-ip—Load distribution is based on the source-host IP
address.
• src-mac—Load distribution is based on the source-MAC
address of the incoming packet.
Step 3 end Return to privileged EXEC mode.
Step 4 show etherchannel load-balance Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return EtherChannel load balancing to the default configuration, use the no port-channel
load-balance global configuration command.
Note The switch supports address learning only on aggregate ports even though the physical-port keyword is
provided in the CLI. The pagp learn-method command and the pagp port-priority command have no
effect on the switch hardware, but they are required for PAgP interoperability with devices that only
support address learning by physical ports, such as the Catalyst 1900 switch.
When the link partner to the switch is a physical learner (such as a Catalyst 1900 series switch), we
recommend that you configure the switch as a physical-port learner by using the pagp learn-method
physical-port interface configuration command. Set the load-distribution method based on the source
MAC address by using the port-channel load-balance src-mac global configuration command. The
switch then sends packets to the Catalyst 1900 switch using the same port in the EtherChannel from
which it learned the source address. Use the pagp learn-method command only in this situation.
Beginning in privileged EXEC mode, follow these steps to configure your switch as a PAgP
physical-port learner and to adjust the priority so that the same port in the bundle is selected for sending
packets. This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the port for transmission, and enter interface
configuration mode.
Command Purpose
Step 3 pagp learn-method physical-port Select the PAgP learning method.
By default, aggregation-port learning is selected, which means
the switch sends packets to the source by using any of the ports
in the EtherChannel. With aggregate-port learning, it is not
important on which physical port the packet arrives.
Select physical-port to connect with another switch that is a
physical learner. Make sure to configure the port-channel
load-balance global configuration command to src-mac as
described in the “Configuring EtherChannel Load Balancing”
section on page 35-16.
The learning method must be configured the same at both ends
of the link.
Step 4 pagp port-priority priority Assign a priority so that the selected port is chosen for packet
transmission.
For priority, the range is 0 to 255. The default is 128. The higher
the priority, the more likely that the port will be used for PAgP
transmission.
Step 5 end Return to privileged EXEC mode.
Step 6 show running-config Verify your entries.
or
show pagp channel-group-number internal
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return the priority to its default setting, use the no pagp port-priority interface configuration
command. To return the learning method to its default setting, use the no pagp learn-method interface
configuration command.
Ports are considered for active use in aggregation in link-priority order starting with the port attached to
the highest priority link. Each port is selected for active use if the preceding higher priority selections
can also be maintained. Otherwise, the port is selected for standby mode.
You can change the default values of the LACP system priority and the LACP port priority to affect how
the software selects active and standby links. For more information, see the “Configuring the LACP
System Priority” section on page 35-19 and the “Configuring the LACP Port Priority” section on
page 35-19.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 lacp system-priority priority Configure the LACP system priority.
For priority, the range is 1 to 65535. The default is 32768.
The lower the value, the higher the system priority.
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify your entries.
or
show lacp sys-id
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return the LACP system priority to the default value, use the no lacp system-priority global
configuration command.
Note If LACP is not able to aggregate all the ports that are compatible (for example, the remote system might
have more restrictive hardware limitations), all the ports that cannot be actively included in the
EtherChannel are put in the hot-standby state and are used only if one of the channeled ports fails.
Beginning in privileged EXEC mode, follow these steps to configure the LACP port priority. This
procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the port to be configured, and enter interface configuration
mode.
Step 3 lacp port-priority priority Configure the LACP port priority.
For priority, the range is 1 to 65535. The is 32768. The lower the value,
the more likely that the port will be used for LACP transmission.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
or
show lacp [channel-group-number]
internal
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return the LACP port priority to the default value, use the no lacp port-priority interface
configuration command.
Table 35-4 Commands for Displaying EtherChannel, PAgP, and LACP Status
Command Description
show etherchannel [channel-group-number {detail | Displays EtherChannel information in a brief, detailed, and
port | port-channel | protocol | summary}] {detail | one-line summary form. Also displays the load-balance or
load-balance | port | port-channel | protocol | frame-distribution scheme, port, port-channel, and protocol
summary} information.
show pagp [channel-group-number] {counters | Displays PAgP information such as traffic information, the
internal | neighbor} internal PAgP configuration, and neighbor information.
show lacp [channel-group-number] {counters | Displays LACP information such as traffic information, the
internal | neighbor} internal LACP configuration, and neighbor information.
You can clear PAgP channel-group information and traffic counters by using the clear pagp
{channel-group-number counters | counters} privileged EXEC command.
You can clear LACP channel-group information and traffic counters by using the clear lacp
{channel-group-number counters | counters} privileged EXEC command.
For detailed information about the fields in the displays, see the command reference for this release.
PE A PE B
Link-state Link-state
group 1 group 2 Service
Provider
POP
Customer
Site
Port 3 Port 4 Port 3 Port 4
UPE A UPE B
Port 2 Port 1
Port 1 Port 2
Link-state Link-state
group 1 group 2
141683
CPE
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 link state track number Create a link-state group, and enable link-state tracking. The
group number can be 1 to 2; the default is 1.
Step 3 interface interface-id Specify a physical interface or range of interfaces to configure,
and enter interface configuration mode.
Valid interfaces include switch ports in access or trunk mode
(IEEE 802.1q), routed ports, or multiple ports bundled into an
upstream EtherChannel interface (static, PAgP, or LACP), also in
trunk mode.
Note Do not enable link-state tracking on individual interfaces
that will be part of a downstream Etherchannel interface.
Step 4 link state group [number] {upstream | Specify a link-state group, and configure the interface as either
downstream} an upstream or downstream interface in the group.The group
number can be 1 to 2; the default is 1.
Step 5 end Return to privileged EXEC mode.
Step 6 show running-config Verify your entries.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
This example shows how to create a link-state group and configure the interfaces:
Switch# configure terminal
Switch(config)# link state track 1
Switch(config)# interface range fastethernet1/0/9 -10
Switch(config-if)# link state group 1 upstream
Switch(config-if)# interface fastethernet1/0/1
Switch(config-if)# link state group 1 downstream
Switch(config-if)# interface fastethernet1/0/3
Switch(config-if)# link state group 1 downstream
Switch(config-if)# interface fastethernet1/0/5
Switch(config-if)# link state group 1 downstream
Switch(config-if)# end
To disable a link-state group, use the no link state track number global configuration command.
This is an example of output from the show link state group detail command:
Switch> show link state group detail
For detailed information about the fields in the display, see the command reference for this release.
This chapter describes how to configure IP unicast routing on the Catalyst 3750 Metro switch.
For more detailed IP unicast configuration information, see the Cisco IOS IP Configuration Guide,
Release 12.2. For complete syntax and usage information for the commands used in this chapter, see
these command references:
• Cisco IOS IP Command Reference, Volume 1 of 3: Addressing and Services, Release 12.2
• Cisco IOS IP Command Reference, Volume 2 of 3: Routing Protocols, Release 12.2
• Cisco IOS IP Command Reference, Volume 3 of 3: Multicast, Release 12.2
This chapter consists of these sections:
• Understanding IP Routing, page 36-2
• Steps for Configuring Routing, page 36-2
• Configuring IP Addressing, page 36-3
• Enabling IP Unicast Routing, page 36-17
• Configuring RIP, page 36-18
• Configuring OSPF, page 36-23
• Configuring EIGRP, page 36-34
• Configuring BGP, page 36-42
• Configuring ISO CLNS Routing, page 36-63
• Configuring BFD, page 36-72
• Configuring Multi-VRF CE, page 36-82
• Configuring Protocol-Independent Features, page 36-97
• Monitoring and Maintaining the IP Network, page 36-111
Note When configuring routing parameters on the switch and to allocate system resources to maximize the
number of unicast routes allowed, you can use the sdm prefer routing global configuration command
to set the Switch Database Management (SDM) feature to the routing template. For more information on
the SDM templates, see Chapter 6, “Configuring SDM Templates,” or see the sdm prefer command in
the command reference for this release.
Understanding IP Routing
In some network environments, VLANs are associated with individual networks or subnetworks. In an
IP network, each subnetwork is mapped to an individual VLAN. Configuring VLANs helps control the
size of the broadcast domain and keeps local traffic local. However, network devices in different VLANs
cannot communicate with one another without a Layer 3 device (router) to route traffic between the
VLAN, referred to as inter-VLAN routing. You configure one or more routers to route traffic to the
appropriate destination VLAN.
Figure 36-1 shows a basic routing topology. Switch A is in VLAN 10, and Switch B is in VLAN 20. The
router has an interface in each VLAN.
VLAN 10 VLAN 20
A Switch A Switch B
Host
C
B Host
Host
18071
ISL Trunks
When Host A in VLAN 10 needs to communicate with Host B in VLAN 10, it sends a packet addressed
to that host. Switch A forwards the packet directly to Host B, without sending it to the router.
When Host A sends a packet to Host C in VLAN 20, Switch A forwards the packet to the router, which
receives the traffic on the VLAN 10 interface. The router checks the routing table, determines the correct
outgoing interface, and forwards the packet on the VLAN 20 interface to Switch B. Switch B receives
the packet and forwards it to Host C.
Routers and Layer 3 switches can route packets in three different ways:
• By using default routing
• By using preprogrammed static routes for the traffic
Static unicast routing forwards packets from predetermined ports through a single path into and out
of a network. Static routing does not automatically respond to changes in the network and therefore,
might result in unreachable destinations.
• By dynamically calculating routes by using a routing protocol
Dynamic routing protocols are used by routers to dynamically calculate the best route for forwarding
traffic. Routing protocols supported by the switch are Routing Information Protocol (RIP), Border
Gateway Protocol (BGP), Open Shortest Path First (OSPF) protocol, Enhanced IGRP (EIGRP),
System-to-Intermediate System (IS-IS), and Bidirectional Forwarding Detection (BFD).
In the following procedures, the specified interface must be one of these Layer 3 interfaces:
• A routed port: a physical port configured as a Layer 3 port by using the no switchport interface
configuration command.
• A switch virtual interface (SVI): a VLAN interface created by using the interface vlan vlan_id
global configuration command and by default a Layer 3 interface.
• An EtherChannel port channel in Layer 3 mode: a port-channel logical interface created by using
the interface port-channel port-channel-number global configuration command and binding the
Ethernet interface into the channel group. For more information, see the “Configuring Layer 3
EtherChannels” section on page 35-13.
Note The switch does not support tunnel interfaces for unicast routed traffic.
All Layer 3 interfaces on which routing will occur must have IP addresses assigned to them. See the
“Assigning IP Addresses to Network Interfaces” section on page 36-4.
Note A Layer 3 switch can have an IP address assigned to each routed port and SVI. The number of routed
ports and SVIs that you can configure is not limited by software. However, the interrelationship between
this number and the number and volume of features being implemented might have an impact on CPU
utilization because of hardware limitations. To optimize system memory for routing, use the sdm prefer
routing global configuration command.
Configuring IP Addressing
A required task for configuring IP routing is to assign IP addresses to Layer 3 network interfaces to
enable the interfaces and allow communication with the hosts on those interfaces that use IP. These
sections describe how to configure various IP addressing features. Assigning IP addresses to the
interface is required; the other procedures are optional.
• Default Addressing Configuration, page 36-4
• Assigning IP Addresses to Network Interfaces, page 36-4
• Configuring Address Resolution Methods, page 36-7
• Routing Assistance When IP Routing is Disabled, page 36-10
• Configuring Broadcast Packet Handling, page 36-12
• Monitoring and Maintaining IP Addressing, page 36-16
An interface can have one primary IP address. A mask identifies the bits that denote the network number
in an IP address. When you use the mask to subnet a network, the mask is referred to as a subnet mask.
To receive an assigned network number, contact your Internet service provider.
Beginning in privileged EXEC mode, follow these steps to assign an IP address and a network mask to
a Layer 3 interface:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and specify the Layer 3
interface to configure.
Step 3 no switchport Remove the interface from Layer 2 configuration mode (if it is a
physical interface).
Step 4 ip address ip-address subnet-mask Configure the IP address and IP subnet mask.
Step 5 no shutdown Enable the interface.
Step 6 end Return to privileged EXEC mode.
Step 7 show interfaces [interface-id] Verify your entries.
show ip interface [interface-id]
show running-config interface [interface-id]
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip subnet-zero Enable the use of subnet zero for interface addresses and routing updates.
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify your entry.
Step 5 copy running-config startup-config (Optional) Save your entry in the configuration file.
Use the no ip subnet-zero global configuration command to restore the default and disable the use of
subnet zero.
Classless Routing
By default, classless routing behavior is enabled on the switch when it is configured to route. With
classless routing, if a router receives packets for a subnet of a network with no default route, the router
forwards the packet to the best supernet route. A supernet consists of contiguous blocks of Class C
address spaces used to simulate a single, larger address space and is designed to relieve the pressure on
the rapidly depleting Class B address space.
In Figure 36-2, classless routing is enabled. When the host sends a packet to 120.20.4.1, instead of
discarding the packet, the router forwards it to the best supernet route. If you disable classless routing
and a router receives packets destined for a subnet of a network with no network default route, the router
discards the packet.
128.0.0.0/8
128.20.4.1
128.20.0.0 IP classless
128.20.1.0 128.20.3.0
128.20.2.0 128.20.4.1
45749
Host
In Figure 36-3, the router in network 128.20.0.0 is connected to subnets 128.20.1.0, 128.20.2.0, and
128.20.3.0. If the host sends a packet to 120.20.4.1, because there is no network default route, the router
discards the packet.
128.0.0.0/8
128.20.4.1
128.20.0.0
Bit bucket
128.20.1.0 128.20.3.0
128.20.2.0 128.20.4.1
45748
Host
To prevent the switch from forwarding packets destined for unrecognized subnets to the best supernet
route possible, you can disable classless routing behavior.
Beginning in privileged EXEC mode, follow these steps to disable classless routing:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 no ip classless Disable classless routing behavior.
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify your entry.
Step 5 copy running-config startup-config (Optional) Save your entry in the configuration file.
To restore the default and have the switch forward packets destined for a subnet of a network with no
network default route to the best supernet route possible, use the ip classless global configuration
command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 arp ip-address hardware-address type Globally associate an IP address with a MAC (hardware) address
in the ARP cache, and specify encapsulation type as one of
these:
• arpa—ARP encapsulation for Ethernet interfaces
• snap—Subnetwork Address Protocol encapsulation for
Token Ring and FDDI interfaces
• sap—HP’s ARP type
Step 3 arp ip-address hardware-address type [alias] (Optional) Specify that the switch respond to ARP requests as if
it were the owner of the specified IP address.
Step 4 interface interface-id Enter interface configuration mode, and specify the interface to
configure.
Step 5 arp timeout seconds (Optional) Set the length of time an ARP cache entry will stay in
the cache. The default is 14400 seconds (4 hours). The range is
0 to 2147483 seconds.
Step 6 end Return to privileged EXEC mode.
Step 7 show interfaces [interface-id] Verify the type of ARP and the timeout value used on all
interfaces or a specific interface.
Step 8 show arp View the contents of the ARP cache.
or
show ip arp
Step 9 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove an entry from the ARP cache, use the no arp ip-address hardware-address type global
configuration command. To remove all nonstatic entries from the ARP cache, use the clear arp-cache
privileged EXEC command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and specify the Layer 3
interface to configure.
Step 3 arp {arpa | snap} Specify the ARP encapsulation method:
• arpa—Address Resolution Protocol
• snap—Subnetwork Address Protocol
Step 4 end Return to privileged EXEC mode.
Step 5 show interfaces [interface-id] Verify ARP encapsulation configuration on all interfaces or
the specified interface.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable an encapsulation type, use the no arp arpa or no arp snap interface configuration command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and specify the Layer 3
interface to configure.
Step 3 ip proxy-arp Enable proxy ARP on the interface.
Step 4 end Return to privileged EXEC mode.
Step 5 show ip interface [interface-id] Verify the configuration on the interface or all interfaces.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable proxy ARP on the interface, use the no ip proxy-arp interface configuration command.
Proxy ARP
Proxy ARP, the most common method for learning about other routes, enables an Ethernet host with no
routing information to communicate with hosts on other networks or subnets. The host assumes that all
hosts are on the same local Ethernet and that they can use ARP to determine their MAC addresses. If a
switch receives an ARP request for a host that is not on the same network as the sender, the switch
evaluates whether it has the best route to that host. If it does, it sends an ARP reply packet with its own
Ethernet MAC address, and the host that sent the request sends the packet to the switch, which forwards
it to the intended host. Proxy ARP treats all networks as if they are local and performs ARP requests for
every IP address.
Proxy ARP is enabled by default. To enable it after it has been disabled, see the “Enable Proxy ARP”
section on page 36-9. Proxy ARP works as long as other routers support it.
Default Gateway
Another method for locating routes is to define a default router or default gateway. All nonlocal packets
are sent to this router, which either routes them appropriately or sends an IP Control Message Protocol
(ICMP) redirect message back, defining which local router the host should use. The switch caches the
redirect messages and forwards each packet as efficiently as possible. A limitation of this method is that
there is no means of detecting when the default router has gone down or is unavailable.
Beginning in privileged EXEC mode, follow these steps to define a default gateway (router) when IP
routing is disabled:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip default-gateway ip-address Set up a default gateway (router).
Step 3 end Return to privileged EXEC mode.
Step 4 show ip redirects Display the address of the default gateway router to verify the
setting.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and specify the Layer 3 interface to
configure.
Step 3 ip irdp Enable IRDP processing on the interface.
Step 4 ip irdp multicast (Optional) Send IRDP advertisements to the multicast address
(224.0.0.1) instead of IP broadcasts.
Note This command allows for compatibility with Sun Microsystems
Solaris, which requires IRDP packets to be sent out as multicasts.
Many implementations cannot receive these multicasts; ensure
end-host ability before using this command.
Step 5 ip irdp holdtime seconds (Optional) Set the IRDP period for which advertisements are valid. The
default is three times the maxadvertinterval value. It must be greater
than maxadvertinterval and cannot be greater than 9000 seconds. If you
change the maxadvertinterval value, this value also changes.
Step 6 ip irdp maxadvertinterval seconds (Optional) Set the IRDP maximum interval between advertisements. The
default is 600 seconds.
Step 7 ip irdp minadvertinterval seconds (Optional) Set the IRDP minimum interval between advertisements. The
default is 0.75 times the maxadvertinterval. If you change the
maxadvertinterval, this value changes to the new default (0.75 of
maxadvertinterval).
Step 8 ip irdp preference number (Optional) Set a device IRDP preference level. The allowed range is –231
to 231. The default is 0. A higher value increases the router preference
level.
Step 9 ip irdp address address [number] (Optional) Specify an IRDP address and preference to proxy-advertise.
Step 10 end Return to privileged EXEC mode.
Step 11 show ip irdp Verify settings by displaying IRDP values.
Step 12 copy running-config startup-config (Optional) Save your entries in the configuration file.
If you change the maxadvertinterval value, the holdtime and minadvertinterval values also change,
so it is important to first change the maxadvertinterval value, before manually changing either the
holdtime or minadvertinterval values.
Use the no ip irdp interface configuration command to disable IRDP routing.
Note You can also limit broadcast, unicast, and multicast traffic on Layer 2 interfaces by using the
storm-control interface configuration command to set traffic suppression levels. For more information,
see Chapter 24, “Configuring Port-Based Traffic Control.”
Routers provide some protection from broadcast storms by limiting their extent to the local cable.
Bridges (including intelligent bridges), because they are Layer 2 devices, forward broadcasts to all
network segments, thus propagating broadcast storms. The best solution to the broadcast storm problem
is to use a single broadcast address scheme on a network. In most modern IP implementations, you can
set the address to be used as the broadcast address. Many implementations, including the one in the
Catalyst 3750 switch, support several addressing schemes for forwarding broadcast messages.
Perform the tasks in these sections to enable these schemes:
• Enabling Directed Broadcast-to-Physical Broadcast Translation, page 36-12
• Forwarding UDP Broadcast Packets and Protocols, page 36-13
• Establishing an IP Broadcast Address, page 36-14
• Flooding IP Broadcasts, page 36-15
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and specify the interface to
configure.
Step 3 ip directed-broadcast [access-list-number] Enable directed broadcast-to-physical broadcast translation on the
interface. You can include an access list to control which broadcasts
are forwarded. When you specify an access list, only IP packets
permitted by the access list can be translated.
Note The ip directed-broadcast interface configuration command
can be configured on a VPN routing/forwarding (VRF)
interface and is VRF aware. Directed broadcast traffic is
routed only within the VRF.
Step 4 exit Return to global configuration mode.
Step 5 ip forward-protocol {udp [port] | nd | sdns} Specify which protocols and ports the router forwards when
forwarding broadcast packets.
• udp—Forward UPD datagrams.
port: (Optional) Destination port that controls which UDP
services are forwarded.
• nd—Forward ND datagrams.
• sdns—Forward SDNS datagrams
Step 6 end Return to privileged EXEC mode.
Step 7 show ip interface [interface-id] Verify the configuration on the interface or all interfaces.
or
show running-config
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
By default, both UDP and ND forwarding are enabled if a helper address has been defined for an
interface. The description for the ip forward-protocol interface configuration command in the Cisco
IOS IP Command Reference, Volume 1 of 3: Addressing and Services, Release 12.2 lists the ports that
are forwarded by default if you do not specify any UDP ports.
If you do not specify any UDP ports when you configure the forwarding of UDP broadcasts, you are
configuring the router to act as a BOOTP forwarding agent. BOOTP packets carry DHCP information.
Beginning in privileged EXEC mode, follow these steps to enable forwarding UDP broadcast packets on
an interface and specify the destination address:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and specify the Layer 3 interface
to configure.
Step 3 ip helper-address address Enable forwarding and specify the destination address for forwarding
UDP broadcast packets, including BOOTP.
Step 4 exit Return to global configuration mode.
Step 5 ip forward-protocol {udp [port] | nd | sdns} Specify which protocols the router forwards when forwarding
broadcast packets.
Step 6 end Return to privileged EXEC mode.
Step 7 show ip interface [interface-id] Verify the configuration on the interface or all interfaces.
or
show running-config
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no ip helper-address interface configuration command to disable the forwarding of broadcast
packets to specific addresses. Use the no ip forward-protocol global configuration command to remove
a protocol or port.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and specify the interface to
configure.
Step 3 ip broadcast-address ip-address Enter a broadcast address different from the default, for example
128.1.255.255.
Step 4 end Return to privileged EXEC mode.
Step 5 show ip interface [interface-id] Verify the broadcast address on the interface or all interfaces.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To restore the default IP broadcast address, use the no ip broadcast-address interface configuration
command.
Flooding IP Broadcasts
You can allow IP broadcasts to be flooded throughout your internetwork in a controlled fashion by using
the database created by the bridging STP. Using this feature also prevents loops. To support this
capability, bridging must be configured on each interface that is to participate in the flooding. If bridging
is not configured on an interface, it still can receive broadcasts. However, the interface never forwards
broadcasts it receives, and the router never uses that interface to send broadcasts received on a
different interface.
Packets that are forwarded to a single network address using the IP helper-address mechanism can be
flooded. Only one copy of the packet is sent on each network segment.
To be considered for flooding, packets must meet these criteria. (Note that these are the same conditions
used to consider packet forwarding using IP helper addresses.)
• The packet must be a MAC-level broadcast.
• The packet must be an IP-level broadcast.
• The packet must be a TFTP, DNS, Time, NetBIOS, ND, or BOOTP packet, or a UDP specified by
the ip forward-protocol udp global configuration command.
• The time-to-live (TTL) value of the packet must be at least two.
A flooded UDP datagram is given the destination address specified with the ip broadcast-address
interface configuration command on the output interface. The destination address can be set to any
address. Thus, the destination address might change as the datagram propagates through the network.
The source address is never changed. The TTL value is decremented.
When a flooded UDP datagram is sent out an interface (and the destination address possibly changed),
the datagram is handed to the normal IP output routines and is, therefore, subject to access lists, if they
are present on the output interface.
Beginning in privileged EXEC mode, follow these steps to use the bridging spanning-tree database to
flood UDP datagrams:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip forward-protocol spanning-tree Use the bridging spanning-tree database to flood UDP datagrams.
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify your entry.
Step 5 copy running-config startup-config (Optional) Save your entry in the configuration file.
Use the no ip forward-protocol spanning-tree global configuration command to disable the flooding
of IP broadcasts.
In a Catalyst 3750 Metro switch, the majority of packets are forwarded in hardware; most packets do not
go through the switch CPU. For those packets that do go to the CPU, you can speed up spanning
tree-based UDP flooding by a factor of about four to five times by using turbo-flooding. This feature is
supported over Ethernet interfaces configured for ARP encapsulation.
Beginning in privileged EXEC mode, follow these steps to increase spanning-tree-based flooding:
Command Purpose
Step 1 configure terminal Enter global configuration mode
Step 2 ip forward-protocol turbo-flood Use the spanning-tree database to speed up flooding of UDP datagrams.
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify your entry.
Step 5 copy running-config startup-config (Optional) Save your entry in the configuration file.
To disable this feature, use the no ip forward-protocol turbo-flood global configuration command.
Command Purpose
clear arp-cache Clear the IP ARP cache and the fast-switching cache.
clear host {name | *} Remove one or all entries from the hostname and the address cache.
clear ip route {network [mask] |*} Remove one or more routes from the IP routing table.
You can display specific statistics, such as the contents of IP routing tables, caches, and databases; the
reachability of nodes; and the routing path that packets are taking through the network. Table 36-3 lists
the privileged EXEC commands for displaying IP statistics.
Command Purpose
show arp Display the entries in the ARP table.
show hosts Display the default domain name, style of lookup service, name server hosts,
and the cached list of hostnames and addresses.
show ip aliases Display IP addresses mapped to TCP ports (aliases).
show ip arp Display the IP ARP cache.
show ip interface [interface-id] Display the IP status of interfaces.
show ip irdp Display IRDP values.
show ip masks address Display the masks used for network addresses and the number of subnets
using each mask.
show ip redirects Display the address of a default gateway.
show ip route [address [mask]] | [protocol] Display the current state of the routing table.
show ip route summary Display the current state of the routing table in summary form.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip routing Enable IP routing.
Step 3 router ip_routing_protocol Specify an IP routing protocol. This step might include other
commands, such as specifying the networks to route with the
network (RIP) router configuration command. For information on
specific protocols, see sections later in this chapter and to the Cisco
IOS IP Configuration Guide, Release 12.2.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
You can now set up parameters for the selected routing protocols as described in these sections:
• Configuring RIP, page 36-18
• Configuring OSPF, page 36-23
• Configuring EIGRP, page 36-34
• Configuring BGP, page 36-42
• Configuring ISO CLNS Routing, page 36-63
• Configuring Multi-VRF CE, page 36-82
You can also configure nonprotocol-specific features:
• Configuring Protocol-Independent Features, page 36-97
Configuring RIP
The Routing Information Protocol (RIP) is an interior gateway protocol (IGP) created for use in small,
homogeneous networks. It is a distance-vector routing protocol that uses broadcast User Datagram
Protocol (UDP) data packets to exchange routing information. The protocol is documented in RFC 1058.
You can find detailed information about RIP in IP Routing Fundamentals, published by Cisco Press.
Using RIP, the switch sends routing information updates (advertisements) every 30 seconds. If a router
does not receive an update from another router for 180 seconds or more, it marks the routes served by
that router as unusable. If there is still no update after 240 seconds, the router removes all routing table
entries for the non-updating router.
RIP uses hop counts to rate the value of different routes. The hop count is the number of routers that can
be traversed in a route. A directly connected network has a hop count of zero; a network with a hop count
of 16 is unreachable. This small range (0 to 15) makes RIP unsuitable for large networks.
If the router has a default network path, RIP advertises a route that links the router to the pseudonetwork
0.0.0.0. The 0.0.0.0 network does not exist; it is treated by RIP as a network to implement the default
routing feature. The switch advertises the default network if a default was learned by RIP or if the router
has a gateway of last resort and RIP is configured with a default metric. RIP sends updates to the
interfaces in specified networks. If an interface’s network is not specified, it is not advertised in any
RIP update.
This section briefly describes how to configure RIP. It includes this information:
• Default RIP Configuration, page 36-18
• Configuring Basic RIP Parameters, page 36-19
• Configuring RIP Authentication, page 36-21
• Configuring Summary Addresses and Split Horizon, page 36-21
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip routing Enable IP routing. (Required only if IP routing is disabled.)
Step 3 router rip Enable a RIP routing process, and enter router configuration mode.
Step 4 network network number Associate a network with a RIP routing process. You can specify multiple
network commands. RIP routing updates are sent and received through
interfaces only on these networks.
Note You must configure a network number for RIP commands to take
effect.
Step 5 neighbor ip-address (Optional) Define a neighboring router with which to exchange routing
information. This step allows routing updates from RIP (normally a
broadcast protocol) to reach nonbroadcast networks.
Step 6 offset list [access-list number | name] (Optional) Apply an offset list to routing metrics to increase incoming
{in | out} offset [type number] and outgoing metrics to routes learned through RIP. You can limit the
offset list with an access list or an interface.
Command Purpose
Step 7 timers basic update invalid holddown (Optional) Adjust routing protocol timers. Valid ranges for all timers are
flush 0 to 4294967295 seconds.
• update—The time between sending routing updates. The default is
30 seconds.
• invalid—The timer after which a route is declared invalid. The
default is 180 seconds.
• holddown—The time before a route is removed from the routing
table. The default is 180 seconds.
• flush—The amount of time for which routing updates are postponed.
The default is 240 seconds.
Step 8 version {1 | 2} (Optional) Configure the switch to receive and send only RIP Version 1
or RIP Version 2 packets. By default, the switch receives Version 1 and 2
but sends only Version 1.
You can also use the interface commands ip rip {send | receive} version
1 | 2 | 1 2} to control what versions are used for sending and receiving on
interfaces.
Step 9 no auto summary (Optional) Disable automatic summarization. By default, the switch
summarizes subprefixes when crossing classful network boundaries.
Disable summarization (RIP Version 2 only) to advertise subnet and host
routing information to classful network boundaries.
Step 10 no validate-update-source (Optional) Disable validation of the source IP address of incoming RIP
routing updates. By default, the switch validates the source IP address of
incoming RIP routing updates and discards the update if the source
address is not valid. Under normal circumstances, disabling this feature
is not recommended. However, if you have a router that is off-network
and you want to receive its updates, you can use this command.
Step 11 output-delay delay (Optional) Add interpacket delay for RIP updates sent.
By default, packets in a multiple-packet RIP update have no delay added
between packets. If you are sending packets to a lower-speed device, you
can add an interpacket delay in the range of 8 to 50 milliseconds.
Step 12 end Return to privileged EXEC mode.
Step 13 show ip protocols Verify your entries.
Step 14 copy running-config startup-config (Optional) Save your entries in the configuration file.
To turn off the RIP routing process, use the no router rip global configuration command.
To display the parameters and current state of the active routing protocol process, use the show ip
protocols privileged EXEC command. Use the show ip rip database privileged EXEC command to
display summary address entries in the RIP database.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and specify the
interface to configure.
Step 3 ip rip authentication key-chain name-of-chain Enable RIP authentication.
Step 4 ip rip authentication mode [text | md5} Configure the interface to use plain text authentication (the
default) or MD5 digest authentication.
Step 5 end Return to privileged EXEC mode.
Step 6 show running-config interface [interface-id] Verify your entries.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
To restore clear text authentication, use the no ip rip authentication mode interface configuration
command. To prevent authentication, use the no ip rip authentication key-chain interface
configuration command.
Note In general, disabling split horizon is not recommended unless you are certain that your application
requires it to properly advertise routes.
If you want to configure an interface running RIP to advertise a summarized local IP address pool on a
network access server for dial-up clients, use the ip summary-address rip interface configuration
command.
Note If split horizon is enabled, neither autosummary nor interface IP summary addresses are advertised.
Beginning in privileged EXEC mode, follow these steps to set an interface to advertise a summarized
local IP address and to disable split horizon on the interface:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and specify the Layer 3
interface to configure.
Step 3 ip address ip-address subnet-mask Configure the IP address and IP subnet.
Step 4 ip summary-address rip ip address ip-network mask Configure the IP address to be summarized and the IP
network mask.
Step 5 no ip split horizon Disable split horizon on the interface.
Step 6 end Return to privileged EXEC mode.
Step 7 show ip interface interface-id Verify your entries.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
Note If split horizon is enabled, neither autosummary nor interface summary addresses (those configured with
the ip summary-address rip router configuration command) are advertised.
Note In general, we do not recommend disabling split horizon unless you are certain that your application
requires it to properly advertise routes.
Beginning in privileged EXEC mode, follow these steps to disable split horizon on the interface:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and specify the interface to
configure.
Step 3 ip address ip-address subnet-mask Configure the IP address and IP subnet.
Step 4 no ip split-horizon Disable split horizon on the interface.
Step 5 end Return to privileged EXEC mode.
Step 6 show ip interface interface-id Verify your entries.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
To enable the split horizon mechanism, use the ip split-horizon interface configuration command.
Configuring OSPF
This section briefly describes how to configure Open Shortest Path First (OSPF). For a complete
description of the OSPF commands, see the “OSPF Commands” chapter of the Cisco IOS IP Command
Reference, Volume 2 of 3: Routing Protocols, Release 12.2.
Note OSPF classifies different media into broadcast, nonbroadcast multiaccess (NBMA), or point-to-point
networks. Broadcast and nonbroadcast networks can also be configured as point-to-multipoint networks.
Starting with Cisco IOS release 12.2(25) SEE, the switch supports all these network types.
OSPF is an Interior Gateway Protocol (IGP) designed expressly for IP networks, supporting IP
subnetting and tagging of externally derived routing information. OSPF also allows packet
authentication and uses IP multicast when sending and receiving packets. The Cisco Systems
implementation supports RFC 1253, OSPF MIB.
The Cisco implementation conforms to the OSPF Version 2 specifications with these key features:
• Definition of stub areas is supported.
• Routes learned through any IP routing protocol can be redistributed into another IP routing protocol.
At the intradomain level, this means that OSPF can import routes learned through EIGRP and RIP.
OSPF routes can also be exported into RIP.
• Plain text and MD5 authentication among neighboring routers within an area is supported.
• Configurable routing interface parameters include interface output cost, retransmission interval,
interface transmit delay, router priority, router dead and hello intervals, and authentication key.
• Virtual links are supported.
• Not-so-stubby-areas (NSSAs) per RFC 1587are supported.
OSPF typically requires coordination among many internal routers, area border routers (ABRs)
connected to multiple areas, and autonomous system boundary routers (ASBRs). The minimum
configuration would use all default parameter values, no authentication, and interfaces assigned to areas.
If you customize your environment, you must ensure coordinated configuration of all routers.
This section briefly describes how to configure OSPF. It includes this information:
• Default OSPF Configuration, page 36-24
• Configuring Basic OSPF Parameters, page 36-25
• Configuring OSPF Interfaces, page 36-26
• Configuring OSPF Area Parameters, page 36-30
• Configuring Other OSPF Parameters, page 36-31
• Changing LSA Group Pacing, page 36-32
• Configuring a Loopback Interface, page 36-33
• Monitoring OSPF, page 36-33
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 router ospf process-id Enable OSPF routing, and enter router configuration mode. The
process ID is an internally used identification parameter that is
locally assigned and can be any positive integer. Each OSPF
routing process has a unique value.
Step 3 network address wildcard-mask area area-id Define an interface on which OSPF runs and the area ID for that
interface. You can use the wildcard-mask to use a single
command to define one or more multiple interfaces to be
associated with a specific OSPF area. The area ID can be a
decimal value or an IP address.
Step 4 end Return to privileged EXEC mode.
Step 5 show ip protocols Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To terminate an OSPF routing process, use the no router ospf process-id global configuration command.
This example shows how to configure an OSPF routing process and assign it a process number of 109:
Switch(config)# router ospf 109
Switch(config-router)# network 131.108.0.0 255.255.255.0 area 24
Beginning in privileged EXEC mode, follow these steps to modify OSPF interface parameters:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and specify the Layer 3 interface
to configure.
Step 3 ip ospf cost (Optional) Explicitly specify the cost of sending a packet on the
interface.
Step 4 ip ospf retransmit-interval seconds (Optional) Specify the number of seconds between link state
advertisement transmissions. The range is 1 to 65535 seconds. The
default is 5 seconds.
Step 5 ip ospf transmit-delay seconds (Optional) Set the estimated number of seconds to wait before
sending a link state update packet. The range is 1 to 65535 seconds.
The default is 1 second.
Command Purpose
Step 6 ip ospf priority number (Optional) Set priority to help determine the OSPF designated router
for a network. The range is from 0 to 255. The default is 1.
Step 7 ip ospf hello-interval seconds (Optional) Set the number of seconds between hello packets sent on
an OSPF interface. The value must be the same for all nodes on a
network. The range is 1 to 65535 seconds. The default is 10 seconds.
Step 8 ip ospf dead-interval seconds (Optional) Set the number of seconds after the last device hello
packet was seen before its neighbors declare the OSPF router to be
down. The value must be the same for all nodes on a network. The
range is 1 to 65535 seconds. The default is 4 times the hello interval.
Step 9 ip ospf authentication-key key (Optional) Assign a password to be used by neighboring OSPF
routers. The password can be any string of keyboard-entered
characters up to 8 bytes in length. All neighboring routers on the
same network must have the same password to exchange OSPF
information.
Step 10 ip ospf message digest-key keyid md5 key (Optional) Enable MDS authentication.
• keyid—An identifier from 1 to 255.
• key—An alphanumeric password of up to 16 bytes.
Step 11 ip ospf database-filter all out (Optional) Block flooding of OSPF LSA packets to the interface. By
default, OSPF floods new LSAs over all interfaces in the same area,
except the interface on which the LSA arrives.
Step 12 end Return to privileged EXEC mode.
Step 13 show ip ospf interface [interface-name] Display OSPF-related interface information.
Step 14 show ip ospf neighbor detail Display NSF awareness status of neighbor switch. The output
matches one of these examples:
• Options is 0x52
LLS Options is 0x1 (LR)
When both of these lines appear, the neighbor switch is NSF
aware.
• Options is 0x42—This means the neighbor switch is not NSF
aware.
Step 15 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no form of these commands to remove the configured parameter value or return to the
default value.
You can also configure network interfaces as either a broadcast or an NBMA network and as point-to
point or point-to-multipoint, regardless of the default media type.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 router ospf process-id Configure an OSPF routing process and enter router configuration
mode.
Step 3 neighbor ip-address [priority number] Specify an OSPF neighbor with neighbor parameters as required.
[poll-interval seconds]
• ip-address—Enter the interface IP address of the OSPF
neighbor.
• (Optional) priority number—Specify the router priority value
of the nonbroadcast neighbor associated with the IP address. The
range is 0 to 255; the default is 0.
• (Optional) poll-interval seconds—Specify a number that
represents the poll interval time (in seconds). This value should
be much larger than the hello interval. The range is
0-4294967295; the default is 120 seconds (2 minutes).
Step 4 end Return to privileged EXEC mode.
Step 5 show ip ospf [process-id] Display OSPF-related information.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
On point-to-multipoint, nonbroadcast networks, you then use the neighbor router configuration
command to identify neighbors. Assigning a cost to a neighbor is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and specify the Layer 3 interface
to configure.
Step 3 ip ospf network {broadcast | non-broadcast Configure the OSFP network type for the specified interface. Select
| {point-to-multipoint [non-broadcast] | one of these network types:
point-to-point}}
• broadcast—Specify an OSPF broadcast multi-access network.
• non-broadcast—Specify an OSPF NBMA network.
• point-to-multipoint—Specify an OSPF point-to-multipoint
network. If you do not enter another keyword, the interface is
point-to-multipoint for broadcast media.
• point-to-multipoint non-broadcast—Specify an OSPF
nonbroadcast point-to-multipoint network.
• point-to-point—Specify an OSPF point-to-point network.
Step 4 exit Return to global configuration mode.
Step 5 router ospf process-id (Optional for point-to-multipoint; required for point-to-multipoint
nonbroadcast) Configure an OSPF routing process and enter router
configuration mode.
Step 6 neighbor ip-address cost number (Optional for point-to-multipoint; required for point-to-multipoint
nonbroadcast). Specify a configured OSPF neighbor and assign a
cost to the neighbor.
• ip-address—Enter the interface IP address of the OSPF
neighbor.
• cost number—Specify a cost for the neighbor as an integer from
1 to 65535.
Note On point-to-multipoint broadcast networks, specifying a
neighbor is optional, but if you do specify a neighbor, you
must specify a cost for that neighbor.
On point-to-multipoint nonbroadcast neighbors, you must
specify a neighbor, but assigning a cost to the neighbor is
optional. If not specified, neighbors assume the cost of the
interface, based on the ip ospf cost interface configuration
command.
Step 7 end Return to privileged EXEC mode.
Step 8 show ip ospf interface [interface-id] Display OSPF-related interface information.
Step 9 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no form of the ip ospf network command to return to the default network type for the media.
Note The OSPF area router configuration commands are all optional.
Beginning in privileged EXEC mode, follow these steps to configure area parameters:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 router ospf process-id Enable OSPF routing, and enter router configuration mode.
Step 3 area area-id authentication (Optional) Allow password-based protection against unauthorized
access to the identified area. The identifier can be either a decimal
value or an IP address.
Step 4 area area-id authentication message-digest (Optional) Enable MD5 authentication on the area.
Step 5 area area-id stub [no-summary] (Optional) Define an area as a stub area. The no-summary keyword
prevents an ABR from sending summary link advertisements into the
stub area.
Step 6 area area-id nssa [no-redistribution] (Optional) Defines an area as a not-so-stubby-area. Every router
[default-information-originate] within the same area must agree that the area is NSSA. Select one of
[no-summary] these keywords:
• no-redistribution—Select when the router is an NSSA ABR and
you want the redistribute command to import routes into normal
areas, but not into the NSSA.
• default-information-originate—Select on an ABR to allow
importing type 7 LSAs into the NSSA.
• no-redistribution—Select to not send summary LSAs into the
NSSA.
Step 7 area area-id range address mask (Optional) Specify an address range for which a single route is
advertised. Use this command only with area border routers.
Step 8 end Return to privileged EXEC mode.
Step 9 show ip ospf [process-id] Display information about the OSPF routing process in general or for
a specific process ID to verify configuration.
show ip ospf [process-id [area-id]] database Display lists of information related to the OSPF database for a
specific router.
Step 10 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no form of these commands to remove the configured parameter value or to return to the
default value.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 router ospf process-id Enable OSPF routing, and enter router configuration mode.
Command Purpose
Step 3 summary-address address mask (Optional) Specify an address and IP subnet mask for redistributed
routes so that only one summary route is advertised.
Step 4 area area-id virtual-link router-id (Optional) Establish a virtual link and set its parameters. See the
[hello-interval seconds] “Configuring OSPF Interfaces” section on page 36-26 for parameter
[retransmit-interval seconds] [trans] definitions and Table 36-5 on page 36-24 for virtual link defaults.
[[authentication-key key] |
message-digest-key keyid md5 key]]
Step 5 default-information originate [always] (Optional) Force the ASBR to generate a default route into the OSPF
[metric metric-value] [metric-type routing domain. Parameters are all optional.
type-value] [route-map map-name]
Step 6 ip ospf name-lookup (Optional) Configure DNS name lookup. The default is disabled.
Step 7 ip auto-cost reference-bandwidth ref-bw (Optional) Specify an address range for which a single route will be
advertised. Use this command only with area border routers.
Step 8 distance ospf {[inter-area dist1] [inter-area (Optional) Change the OSPF distance values. The default distance
dist2] [external dist3]} for each type of route is 110. The range is 1 to 255.
Step 9 passive-interface type number (Optional) Suppress the sending of hello packets through the
specified interface.
Step 10 timers spf spf-delay spf-holdtime (Optional) Configure route calculation timers.
• spf-delay—Enter an integer from 0 to 65535. The default is 5
seconds; 0 means no delay.
• spf-holdtime—Enter an integer from 0 to 65535. The default is
10 seconds; 0 means no delay.
Step 11 ospf log-adj-changes (Optional) Send syslog message when a neighbor state changes.
Step 12 end Return to privileged EXEC mode.
Step 13 show ip ospf [process-id [area-id]] database Display lists of information related to the OSPF database for a
specific router. For some of the keyword options, see to the
“Monitoring OSPF” section on page 36-33.
Step 14 copy running-config startup-config (Optional) Save your entries in the configuration file.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 router ospf process-id Enable OSPF routing, and enter router configuration mode.
Command Purpose
Step 3 timers lsa-group-pacing seconds Change the group pacing of LSAs.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default value, use the no timers lsa-group-pacing router configuration command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface loopback 0 Create a loopback interface, and enter interface configuration mode.
Step 3 ip address address mask Assign an IP address to this interface.
Step 4 end Return to privileged EXEC mode.
Step 5 show ip interface Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no interface loopback 0 global configuration command to disable the loopback interface.
Monitoring OSPF
You can display specific statistics such as the contents of IP routing tables, caches, and databases.
Table 36-6 lists some of the privileged EXEC commands for displaying statistics. For more show ip ospf
database privileged EXEC command options and for explanations of fields in the resulting display, see
the Cisco IOS IP Command Reference, Volume 2 of 3: Routing Protocols, Release 12.2.
Command Purpose
show ip ospf [process-id] Display general information about OSPF routing
processes.
show ip ospf [process-id] database [router] [link-state-id] Display lists of information related to the OSPF
database.
show ip ospf [process-id] database [router] [self-originate]
show ip ospf [process-id] database [router] [adv-router [ip-address]]
show ip ospf [process-id] database [network] [link-state-id]
show ip ospf [process-id] database [summary] [link-state-id]
show ip ospf [process-id] database [asbr-summary] [link-state-id]
show ip ospf [process-id] database [external] [link-state-id]
show ip ospf [process-id area-id] database [database-summary]
show ip ospf border-routes Display the internal OSPF routing ABR and ASBR
table entries.
show ip ospf interface [interface-name] Display OSPF-related interface information.
show ip ospf neighbor [interface-name] [neighbor-id] detail Display OSPF interface neighbor information.
show ip ospf virtual-links Display OSPF-related virtual links information.
Configuring EIGRP
Enhanced IGRP (EIGRP) is a Cisco proprietary enhanced version of the IGRP. EIGRP uses the same
distance vector algorithm and distance information as IGRP; however, the convergence properties and
the operating efficiency of EIGRP are significantly improved.
The convergence technology employs an algorithm referred to as the Diffusing Update Algorithm
(DUAL), which guarantees loop-free operation at every instant throughout a route computation and
allows all devices involved in a topology change to synchronize at the same time. Routers that are not
affected by topology changes are not involved in recomputations.
IP EIGRP provides increased network width. With RIP, the largest possible width of your network is
15 hops. Because the EIGRP metric is large enough to support thousands of hops, the only barrier to
expanding the network is the transport-layer hop counter. EIGRP increments the transport control field
only when an IP packet has traversed 15 routers and the next hop to the destination was learned through
EIGRP. When a RIP route is used as the next hop to the destination, the transport control field is
incremented as usual.
EIGRP offers these features:
• Fast convergence.
• Incremental updates when the state of a destination changes, instead of sending the entire contents
of the routing table, minimizing the bandwidth required for EIGRP packets.
• Less CPU usage because full update packets need not be processed each time they are received.
• Protocol-independent neighbor discovery mechanism to learn about neighboring routers.
• Variable-length subnet masks (VLSMs).
• Arbitrary route summarization.
To create an EIGRP routing process, you must enable EIGRP and associate networks. EIGRP sends
updates to the interfaces in the specified networks. If you do not specify an interface network, it is not
advertised in any EIGRP update.
Note If you have routers on your network that are configured for IGRP, and you want to change to EIGRP, you
must designate transition routers that have both IGRP and EIGRP configured. In these cases, perform
Steps 1 through 3 in the next section and also see the “Configuring Split Horizon” section on page 36-22.
You must use the same AS number for routes to be automatically redistributed.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 router eigrp autonomous-system Enable an EIGRP routing process, and enter router configuration
mode. The AS number identifies the routes to other EIGRP routers
and is used to tag routing information.
Step 3 network network-number Associate networks with an EIGRP routing process. EIGRP sends
updates to the interfaces in the specified networks.
Step 4 eigrp log-neighbor-changes (Optional) Enable logging of EIGRP neighbor changes to monitor
routing system stability.
Step 5 metric weights tos k1 k2 k3 k4 k5 (Optional) Adjust the EIGRP metric. Although the defaults have
been carefully determined to provide excellent operation in most
networks, you can adjust them.
Command Purpose
Step 7 auto-summary (Optional) Enable automatic summarization of subnet routes into
network-level routes.
Step 8 ip summary-address eigrp (Optional) Configure a summary aggregate.
autonomous-system-number address mask
Step 9 end Return to privileged EXEC mode.
Step 10 show ip protocols Verify your entries.
Step 11 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no forms of these commands to disable the feature or return the setting to the default value.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and specify the Layer 3
interface to configure.
Step 3 ip bandwidth-percent eigrp percent (Optional) Configure the percentage of bandwidth that can
be used by EIGRP on an interface. The default is 50 percent.
Step 4 ip summary-address eigrp (Optional) Configure a summary aggregate address for a
autonomous-system-number address mask specified interface (not usually necessary if auto-summary is
enabled).
Step 5 ip hello-interval eigrp autonomous-system-number (Optional) Change the hello time interval for an EIGRP
seconds routing process. The range is 1 to 65535 seconds. The
default is 60 seconds for low-speed NBMA networks and 5
seconds for all other networks.
Step 6 ip hold-time eigrp autonomous-system-number (Optional) Change the hold time interval for an EIGRP
seconds routing process. The range is 1 to 65535 seconds. The
default is 180 seconds for low-speed NBMA networks and
15 seconds for all other networks.
Use the no forms of these commands to disable the feature or return the setting to the default value.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and specify the
Layer 3 interface to configure.
Step 3 ip authentication mode eigrp autonomous-system md5 Enable MD5 authentication in IP EIGRP packets.
Step 4 ip authentication key-chain eigrp autonomous-system Enable authentication of IP EIGRP packets.
key-chain
Step 5 exit Return to global configuration mode.
Step 6 key chain name-of-chain Identify a key chain and enter key-chain configuration
mode. Match the name configured in Step 4.
Step 7 key number In key-chain configuration mode, identify the key
number.
Step 8 key-string text In key-chain key configuration mode, identify the key
string.
Step 9 accept-lifetime start-time {infinite | end-time | duration (Optional) Specify the time period during which the key
seconds} can be received.
The start-time and end-time syntax can be either
hh:mm:ss Month date year or hh:mm:ss date Month
year. The default is forever with the default start-time
and the earliest acceptable date as January 1, 1993. The
default end-time and duration is infinite.
Step 10 send-lifetime start-time {infinite | end-time | duration (Optional) Specify the time period during which the key
seconds} can be sent.
The start-time and end-time syntax can be either
hh:mm:ss Month date year or hh:mm:ss date Month
year. The default is forever with the default start-time
and the earliest acceptable date as January 1, 1993. The
default end-time and duration is infinite.
Step 11 end Return to privileged EXEC mode.
Step 12 show key chain Display authentication key information.
Step 13 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no forms of these commands to disable the feature or to return the setting to the default value.
Note EIGRP stub routing only advertises connected or summary routes from the routing tables to other
switches in the network. The switch uses EIGRP stub routing at the access layer to eliminate the need
for other types of routing advertisements. if you try to configure multi-VRF-CE and EIGRP stub routing
at the same time, the configuration is not allowed.
In a network using EIGRP stub routing, the only allowable route for IP traffic to the user is through a
switch that is configured with EIGRP stub routing. The switch sends the routed traffic to interfaces that
are configured as user interfaces or are connected to other devices.
When using EIGRP stub routing, you need to configure the distribution and remote routers to use EIGRP
and to configure only the switch as a stub. Only specified routes are propagated from the switch. The
switch responds to all queries for summaries, connected routes, and routing updates.
Any neighbor that receives a packet informing it of the stub status does not query the stub router for any
routes, and a router that has a stub peer does not query that peer. The stub router depends on the
distribution router to send the proper updates to all peers.
In Figure 36-4, switch B is configured as an EIGRP stub router. Switches A and C are connected to the
rest of the WAN. Switch B advertises connected, static, redistribution, and summary routes to switch A
and C. Switch B does not advertise any routes learned from switch A (and the reverse).
For more information about EIGRP stub routing, see “Configuring EIGRP Stub Routing” part of the
Cisco IOS IP Configuration Guide, Volume 2 of 3: Routing Protocols, Release 12.2 from the Cisco.com
page under Documentation > Cisco IOS Software > 12.2 Mainline > Configuration Guides.
Beginning in privileged EXEC mode, follow these steps to configure a remote or spoke router for EIGRP
stub routing:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 router eigrp 1 Configure a remote or distribution router to run an EIGRP process and
enter router configuration mode.
Step 3 network network-number Associate networks with an EIGRP routing process.
Step 4 eigrp stub [receive-only | connected | Configure a remote router as an EIGRP stub router. The keywords have
static | summary] these meanings:
• Enter receive-only to set the router as a receive-only neighbor.
• Enter connected to advertise connected routes.
• Enter static to advertise static routes.
• Enter summary to advertise summary routes.
Step 5 end Return to privileged EXEC mode.
Step 6 show ip eigrp neighbor detail Verify that a remote router has been configured as a stub router with
EIGRP. The last line of the output shows the stub status of the remote or
spoke router.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
Enter the show ip eigrp neighbor detail privileged EXEC command from the distribution router to
verify the configuration.
Command Purpose
clear ip eigrp neighbors [if-address | interface] Delete neighbors from the neighbor table.
show ip eigrp interface [interface] [as number] Display information about interfaces configured for EIGRP.
show ip eigrp neighbors [type-number] Display EIGRP discovered neighbors.
show ip eigrp topology [autonomous-system-number] | Display the EIGRP topology table for a given process.
[[ip-address] mask]]
show ip eigrp traffic [autonomous-system-number] Display the number of packets sent and received for all or a
specified EIGRP process.
Configuring BGP
The Border Gateway Protocol (BGP) is an exterior gateway protocol used to set up an interdomain
routing system that guarantees the loop-free exchange of routing information between autonomous
systems. Autonomous systems are made up of routers that operate under the same administration and
that run Interior Gateway Protocols (IGPs), such as RIP or OSPF, within their boundaries and that
interconnect by using an Exterior Gateway Protocol (EGP). BGP Version 4 is the standard EGP for
interdomain routing in the Internet. The protocol is defined in RFCs 1163, 1267, and 1771. You can find
detailed information about BGP in Internet Routing Architectures, published by Cisco Press, and in the
“Configuring BGP” chapter in the Cisco IOS IP and IP Routing Configuration Guide.
Note For details about BGP commands and keywords, see the Cisco IOS IP Command Reference, Volume 2 of
3: Routing Protocols, Release 12.2. For a list of BGP commands that are visible but not supported by
the switch, see Appendix B, “Unsupported Commands in Cisco IOS Release12.2(58)SE.”
Routers that belong to the same autonomous system (AS) and that exchange BGP updates run internal
BGP (IBGP), and routers that belong to different autonomous systems and that exchange BGP updates
run external BGP (EBGP). Most configuration commands are the same for configuring EBGP and IBGP.
The difference is that the routing updates are exchanged either between autonomous systems (EBGP) or
within an AS (IBGP). Figure 36-5 shows a network that is running both EBGP and IBGP.
129.213.1.2 192.208.10.1
EBGP EBGP
129.213.1.1 192.208.10.2
175.220.212.1 175.220.1.2
74775
AS 200
Before exchanging information with an external AS, BGP ensures that networks within the AS can be
reached by defining internal BGP peering among routers within the AS and by redistributing BGP
routing information to IGPs that run within the AS, such as IGRP and OSPF.
Routers that run a BGP routing process are often referred to as BGP speakers. BGP uses the
Transmission Control Protocol (TCP) as its transport protocol (specifically port 179). Two BGP speakers
that have a TCP connection to each other for exchanging routing information are known as peers or
neighbors. In Figure 36-5, Routers A and B are BGP peers, as are Routers B and C and Routers C and
D. The routing information is a series of AS numbers that describe the full path to the destination
network. BGP uses this information to construct a loop-free map of autonomous systems.
For a list of BGP commands that are visible but not supported by the switch, see Appendix B,
“Unsupported Commands in Cisco IOS Release12.2(58)SE.”
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip routing Enable IP routing (required only if IP routing is disabled).
Step 3 router bgp autonomous-system Enable a BGP routing process, assign it an AS number, and
enter router configuration mode. The AS number can be from
1 to 65535, with 64512 to 65535 designated as private
autonomous numbers.
Step 4 network network-number [mask network-mask] Configure a network as local to this AS, and enter it in the BGP
[route-map route-map-name] table.
Step 5 neighbor {ip-address | peer-group-name} Add an entry to the BGP neighbor table specifying that the
remote-as number neighbor identified by the IP address belongs to the specified
AS.
For EBGP, neighbors are usually directly connected, and the IP
address is the address of the interface at the other end of the
connection.
For IBGP, the IP address can be the address of any of the router
interfaces.
Step 6 neighbor {ip-address | peer-group-name} (Optional) Remove private AS numbers from the AS-path in
remove-private-as outbound routing updates.
Step 7 no synchronization (Optional) Disable synchronization between BGP and an IGP.
Step 8 no auto-summary (Optional) Disable automatic network summarization. By
default, when a subnet is redistributed from an IGP into BGP,
only the network route is inserted into the BGP table.
Step 9 bgp fast-external-fallover (Optional) Automatically reset a BGP session when a link
between external neighbors goes down. By default, the session
is not immediately reset.
Step 10 bgp graceful-restart (Optional) Enable NSF awareness on switch. By default, NSF
awareness is disabled.
Step 11 end Return to privileged EXEC mode.
Step 12 show ip bgp network network-number Verify the configuration.
or
show ip bgp neighbor Verify that NSF awareness (Graceful Restart) is enabled on the
neighbor.
If NSF awareness is enabled on the switch and the neighbor,
this message appears:
Graceful Restart Capability: advertised and received
Use the no router bgp autonomous-system global configuration command to remove a BGP AS. Use the
no network network-number router configuration command to remove the network from the BGP table.
Use the no neighbor {ip-address | peer-group-name} remote-as number router configuration command
to remove a neighbor. Use the no neighbor {ip-address | peer-group-name} remove-private-as router
configuration command to include private AS numbers in updates to a neighbor. Use the
synchronization router configuration command to re-enable synchronization.
These examples show how to configure BGP on the routers in Figure 36-5.
Router A:
Switch(config)# router bgp 100
Switch(config-router)# neighbor 129.213.1.1 remote-as 200
Router B:
Switch(config)# router bgp 200
Switch(config-router)# neighbor 129.213.1.2 remote-as 100
Switch(config-router)# neighbor 175.220.1.2 remote-as 200
Router C:
Switch(config)# router bgp 200
Switch(config-router)# neighbor 175.220.212.1 remote-as 200
Switch(config-router)# neighbor 192.208.10.1 remote-as 300
Router D:
Switch(config)# router bgp 300
Switch(config-router)# neighbor 192.208.10.2 remote-as 200
To verify that BGP peers are running, use the show ip bgp neighbors privileged EXEC command. This
is the output of this command on Router A:
Switch# show ip bgp neighbors
Anything other than state = established means that the peers are not running. The remote router ID is
the highest IP address on that router (or the highest loopback interface). Each time the table is updated
with new information, the table version number increments. A table version number that continually
increments means that a route is flapping, causing continual routing updates.
For exterior protocols, a reference to an IP network from the network router configuration command
controls only which networks are advertised. This is in contrast to Interior Gateway Protocols (IGPs),
such as EIGRP, which also use the network command to determine where to send updates.
For detailed descriptions of BGP configuration, see the “IP Routing Protocols” chapter in the Cisco IOS
IP Configuration Guide, Release 12.2. For details about specific commands, see the Cisco IOS IP
Command Reference, Volume 2 of 3: Routing Protocols, Release 12.2. See Appendix B, “Unsupported
Commands in Cisco IOS Release12.2(58)SE,” for a list of BGP commands that are visible but not
supported by the switch.
Beginning in privileged EXEC mode, follow these steps to determine if a BGP peer supports the route
refresh capability and to reset the BGP session:
Command Purpose
Step 1 show ip bgp neighbors Display whether a neighbor supports the route refresh capability. When supported,
this message appears for the router:
Received route refresh capability from peer.
Step 2 clear ip bgp {* | address | Reset the routing table on the specified connection.
peer-group-name}
• Enter an asterisk (*) to specify that all connections be reset.
• Enter an IP address to specify the connection to be reset.
• Enter a peer group name to reset the peer group.
Command Purpose
Step 3 clear ip bgp {* | address | (Optional) Perform an outbound soft reset to reset the inbound routing table on the
peer-group-name} soft out specified connection. Use this command if route refresh is supported.
• Enter an asterisk (*) to specify that all connections be reset.
• Enter an IP address to specify the connection to be reset.
• Enter a peer group name to reset the peer group.
Step 4 show ip bgp Verify the reset by checking information about the routing table and about BGP
show ip bgp neighbors neighbors.
9. Prefer the route that can be reached through the closest IGP neighbor (the lowest IGP metric). This
means that the router will prefer the shortest internal path within the AS to reach the destination (the
shortest path to the BGP next-hop).
10. If the following conditions are all true, insert the route for this path into the IP routing table:
• Both the best route and this route are external.
• Both the best route and this route are from the same neighboring autonomous system.
• maximum-paths is enabled.
11. If multipath is not enabled, prefer the route with the lowest IP address value for the BGP router ID.
The router ID is usually the highest IP address on the router or the loopback (virtual) address, but
might be implementation-specific.
Beginning in privileged EXEC mode, follow these steps to configure some decision attributes:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 router bgp autonomous-system Enable a BGP routing process, assign it an AS number,
and enter router configuration mode.
Step 3 bgp best-path as-path ignore (Optional) Configure the router to ignore AS path length
in selecting a route.
Step 4 neighbor {ip-address | peer-group-name} next-hop-self (Optional) Disable next-hop processing on BGP updates
to a neighbor by entering a specific IP address to be used
instead of the next-hop address.
Step 5 neighbor {ip-address | peer-group-name} weight (Optional) Assign a weight to a neighbor connection.
weight Acceptable values are from 0 to 65535; the largest weight
is the preferred route. Routes learned through another
BGP peer have a default weight of 0; routes sourced by the
local router have a default weight of 32768.
Step 6 default-metric number (Optional) Set a MED metric to set preferred paths to
external neighbors. All routes without a MED will also be
set to this value. The range is 1 to 4294967295. The lowest
value is the most desirable.
Step 7 bgp bestpath med missing-as-worst (Optional) Configure the switch to consider a missing
MED as having a value of infinity, making the path
without a MED value the least desirable path.
Step 8 bgp always-compare med (Optional) Configure the switch to compare MEDs for
paths from neighbors in different autonomous systems. By
default, MED comparison is only done among paths in the
same AS.
Step 9 bgp bestpath med confed (Optional) Configure the switch to consider the MED in
choosing a path from among those advertised by different
subautonomous systems within a confederation.
Step 10 bgp deterministic med (Optional) Configure the switch to consider the MED
variable when choosing among routes advertised by
different peers in the same AS.
Command Purpose
Step 11 bgp default local-preference value (Optional) Change the default local preference value. The
range is 0 to 4294967295; the default value is 100. The
highest local preference value is preferred.
Step 12 maximum-paths number (Optional) Configure the number of paths to be added to
the IP routing table. The default is to only enter the best
path in the routing table. The range is from 1 to 8. Having
multiple paths allows load balancing among the paths.
Step 13 end Return to privileged EXEC mode.
Step 14 show ip bgp Verify the reset by checking information about the routing
show ip bgp neighbors table and about BGP neighbors.
Step 15 copy running-config startup-config (Optional) Save your entries in the configuration file.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 route-map map-tag [[permit | deny] | Create a route map, and enter route-map configuration mode.
sequence-number]]
Step 3 set ip next-hop ip-address [...ip-address] (Optional) Set a route map to disable next-hop processing
[peer-address]
• In an inbound route map, set the next hop of matching routes to
be the neighbor peering address, overriding third-party next hops.
• In an outbound route map of a BGP peer, set the next hop to the
peering address of the local router, disabling the next-hop
calculation.
Step 4 end Return to privileged EXEC mode.
Step 5 show route-map [map-name] Display all route maps configured or only the one specified to verify
configuration.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no route-map map-tag command to delete the route map. Use the no set ip next-hop ip-address
command to re-enable next-hop processing.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 router bgp autonomous-system Enable a BGP routing process, assign it an AS number, and enter
router configuration mode.
Step 3 neighbor {ip-address | peer-group name} (Optional) Filter BGP routing updates to or from neighbors as
distribute-list {access-list-number | name} specified in an access list.
{in | out}
Note You can also use the neighbor prefix-list router
configuration command to filter updates, but you cannot use
both commands to configure the same BGP peer.
Step 4 neighbor {ip-address | peer-group name} (Optional) Apply a route map to filter an incoming or outgoing
route-map map-tag {in | out} route.
Step 5 end Return to privileged EXEC mode.
Step 6 show ip bgp neighbors Verify the configuration.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no neighbor distribute-list command to remove the access list from the neighbor. Use the no
neighbor route-map map-tag router configuration command to remove the route map from the
neighbor.
Another method of filtering is to specify an access list filter on both incoming and outbound updates,
based on the BGP autonomous system paths. Each filter is an access list based on regular expressions.
(For more information on forming regular expressions, see the “Regular Expressions” appendix in the
Cisco IOS Dial Services Command Reference.) To use this method, define an autonomous system path
access list, and apply it to updates to and from particular neighbors.
Beginning in privileged EXEC mode, follow these steps to configure BGP path filtering:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip as-path access-list access-list-number Define a BGP-related access list.
{permit | deny} as-regular-expressions
Command Purpose
Step 3 router bgp autonomous-system Enter BGP router configuration mode.
Step 4 neighbor {ip-address | peer-group name} Establish a BGP filter based on an access list.
filter-list {access-list-number | name} {in |
out | weight weight}
Step 5 end Return to privileged EXEC mode.
Step 6 show ip bgp neighbors [paths Verify the configuration.
regular-expression]
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip prefix-list list-name [seq seq-value] deny | Create a prefix list with an optional sequence number to deny or
permit network/len [ge ge-value] [le le-value] permit access for matching conditions. You must enter at least one
permit or deny clause.
• network/len is the network number and length (in bits) of the
network mask.
• (Optional) ge and le values specify the range of the prefix length
to be matched.The specified ge-value and le-value must satisfy
this condition: len < ge-value < le-value < 32
Step 3 ip prefix-list list-name seq seq-value deny | (Optional) Add an entry to a prefix list, and assign a sequence
permit network/len [ge ge-value] [le le-value] number to the entry.
Command Purpose
Step 4 end Return to privileged EXEC mode.
Step 5 show ip prefix list [detail | summary] name Verify the configuration by displaying information about a prefix list
[network/len] [seq seq-num] [longer] or prefix list entries.
[first-match]
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To delete a prefix list and all of its entries, use the no ip prefix-list list-name global configuration
command. To delete an entry from a prefix list, use the no ip prefix-list seq seq-value global
configuration command. To disable automatic generation of sequence numbers, use the no ip prefix-list
sequence number command; to reenable automatic generation, use the ip prefix-list sequence number
command. To clear the hit-count table of prefix list entries, use the clear ip prefix-list privileged EXEC
command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip community-list community-list-number Create a community list, and assign it a number.
{permit | deny} community-number
• The community-list-number is an integer from 1 to 99 that
identifies one or more permit or deny groups of communities.
• The community-number is the number configured by a set
community route-map configuration command.
Step 3 router bgp autonomous-system Enter BGP router configuration mode.
Step 4 neighbor {ip-address | peer-group name} Specify that the COMMUNITIES attribute be sent to the neighbor at
send-community this IP address.
Step 5 set comm-list list-num delete (Optional) Remove communities from the community attribute of an
inbound or outbound update that match a standard or extended
community list specified by a route map.
Step 6 exit Return to global configuration mode.
Step 7 ip bgp-community new-format (Optional) Display and parse BGP communities in the format AA:NN.
A BGP community is displayed in a two-part format 2 bytes long. The
Cisco default community format is in the format NNAA. In the most
recent RFC for BGP, a community takes the form AA:NN, where the
first part is the AS number and the second part is a 2-byte number.
Step 8 end Return to privileged EXEC mode.
Step 9 show ip bgp community Verify the configuration.
Step 10 copy running-config startup-config (Optional) Save your entries in the configuration file.
Beginning in privileged EXEC mode, use these commands to configure BGP peers:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 router bgp autonomous-system Enter BGP router configuration mode.
Step 3 neighbor peer-group-name peer-group Create a BGP peer group.
Step 4 neighbor ip-address peer-group Make a BGP neighbor a member of the peer group.
peer-group-name
Step 5 neighbor {ip-address | peer-group-name} Specify a BGP neighbor. If a peer group is not configured with a
remote-as number remote-as number, use this command to create peer groups
containing EBGP neighbors. The range is 1 to 65535.
Step 6 neighbor {ip-address | peer-group-name} (Optional) Associate a description with a neighbor.
description text
Step 7 neighbor {ip-address | peer-group-name} (Optional) Allow a BGP speaker (the local router) to send the
default-originate [route-map map-name] default route 0.0.0.0 to a neighbor for use as a default route.
Step 8 neighbor {ip-address | peer-group-name} (Optional) Specify that the COMMUNITIES attribute be sent to
send-community the neighbor at this IP address.
Step 9 neighbor {ip-address | peer-group-name} (Optional) Allow internal BGP sessions to use any operational
update-source interface interface for TCP connections.
Step 10 neighbor {ip-address | peer-group-name} (Optional) Allow BGP sessions, even when the neighbor is not
ebgp-multihop on a directly connected segment. The multihop session is not
established if the only route to the multihop peer’s address is the
default route (0.0.0.0).
Step 11 neighbor {ip-address | peer-group-name} (Optional) Specify an AS number to use as the local AS. The
local-as number range is 1 to 65535.
Step 12 neighbor {ip-address | peer-group-name} (Optional) Set the minimum interval between sending BGP
advertisement-interval seconds routing updates.
Step 13 neighbor {ip-address | peer-group-name} (Optional) Control how many prefixes can be received from a
maximum-prefix maximum [threshold] neighbor. The range is 1 to 4294967295. The threshold
(optional) is the percentage of maximum at which a warning
message is generated. The default is 75 percent.
Step 14 neighbor {ip-address | peer-group-name} (Optional) Disable next-hop processing on the BGP updates to a
next-hop-self neighbor.
Step 15 neighbor {ip-address | peer-group-name} (Optional) Set MD5 authentication on a TCP connection to a
password string BGP peer. The same password must be configured on both BGP
peers, or the connection between them is not made.
Step 16 neighbor {ip-address | peer-group-name} (Optional) Apply a route map to incoming or outgoing routes.
route-map map-name {in | out}
Step 17 neighbor {ip-address | peer-group-name} (Optional) Specify that the COMMUNITIES attribute be sent to
send-community the neighbor at this IP address.
Command Purpose
Step 18 neighbor {ip-address | peer-group-name} timers (Optional) Set timers for the neighbor or peer group.
keepalive holdtime
• The keepalive interval is the time within which keepalive
messages are sent to peers. The range is 1 to 4294967295
seconds; the default is 60.
• The holdtime is the interval after which a peer is declared
inactive after not receiving a keepalive message from it. The
range is 1 to 4294967295 seconds; the default is 180.
Step 19 neighbor {ip-address | peer-group-name} weight (Optional) Specify a weight for all routes from a neighbor.
weight
Step 20 neighbor {ip-address | peer-group-name} (Optional) Filter BGP routing updates to or from neighbors, as
distribute-list {access-list-number | name} {in | specified in an access list.
out}
Step 21 neighbor {ip-address | peer-group-name} (Optional) Establish a BGP filter.
filter-list access-list-number {in | out | weight
weight}
Step 22 neighbor {ip-address | peer-group-name} (Optional) Specify the BGP version to use when communicating
version value with a neighbor.
Step 23 neighbor {ip-address | peer-group-name} (Optional) Configure the software to start storing received
soft-reconfiguration inbound updates.
Step 24 end Return to privileged EXEC mode.
Step 25 show ip bgp neighbors Verify the configuration.
Step 26 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable an existing BGP neighbor or neighbor peer group, use the neighbor shutdown router
configuration command. To enable a previously existing neighbor or neighbor peer group that had been
disabled, use the no neighbor shutdown router configuration command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 router bgp autonomous-system Enter BGP router configuration mode.
Step 3 aggregate-address address mask Create an aggregate entry in the BGP routing table. The aggregate
route is advertised as coming from the AS, and the atomic aggregate
attribute is set to indicate that information might be missing.
Command Purpose
Step 4 aggregate-address address mask as-set (Optional) Generate AS set path information. This command
creates an aggregate entry following the same rules as the previous
command, but the advertised path will be an AS_SET consisting of
all elements contained in all paths. Do not use this keyword when
aggregating many paths because this route must be continually
withdrawn and updated.
Step 5 aggregate-address address-mask (Optional) Advertise summary addresses only.
summary-only
Step 6 aggregate-address address mask (Optional) Suppress selected, more specific routes.
suppress-map map-name
Step 7 aggregate-address address mask (Optional) Generate an aggregate based on conditions specified by
advertise-map map-name the route map.
Step 8 aggregate-address address mask (Optional) Generate an aggregate with attributes specified in the
attribute-map map-name route map.
Step 9 end Return to privileged EXEC mode.
Step 10 show ip bgp neighbors [advertised-routes] Verify the configuration.
Step 11 copy running-config startup-config (Optional) Save your entries in the configuration file.
To delete an aggregate entry, use the no aggregate-address address mask router configuration
command. To return options to the default values, use the command with keywords.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 router bgp autonomous-system Enter BGP router configuration mode.
Step 3 bgp confederation identifier autonomous-system Configure a BGP confederation identifier.
Step 4 bgp confederation peers autonomous-system Specify the autonomous systems that belong to the
[autonomous-system ...] confederation and that will be treated as special EBGP peers.
Step 5 end Return to privileged EXEC mode.
Command Purpose
Step 6 show ip bgp neighbor Verify the configuration.
show ip bgp network
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 router bgp autonomous-system Enter BGP router configuration mode.
Step 3 neighbor ip-address | peer-group-name Configure the local router as a BGP route reflector and the
route-reflector-client specified neighbor as a client.
Step 4 bgp cluster-id cluster-id (Optional) Configure the cluster ID if the cluster has more than
one route reflector.
Step 5 no bgp client-to-client reflection (Optional) Disable client-to-client route reflection. By default,
the routes from a route reflector client are reflected to other
clients. However, if the clients are fully meshed, the route
reflector does not need to reflect routes to clients.
Command Purpose
Step 6 end Return to privileged EXEC mode.
Step 7 show ip bgp Verify the configuration. Display the originator ID and the
cluster-list attributes.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 router bgp autonomous-system Enter BGP router configuration mode.
Step 3 bgp dampening Enable BGP route dampening.
Step 4 bgp dampening half-life reuse suppress (Optional) Change the default values of route dampening
max-suppress [route-map map] factors.
Step 5 end Return to privileged EXEC mode.
Step 6 show ip bgp flap-statistics [{regexp regexp} | (Optional) Monitor the flaps of all paths that are flapping. The
{filter-list list} | {address mask [longer-prefix]}] statistics are deleted when the route is not suppressed and is
stable.
Step 7 show ip bgp dampened-paths (Optional) Display the dampened routes, including the time
remaining before they are suppressed.
Step 8 clear ip bgp flap-statistics [{regexp regexp} | (Optional) Clear BGP flap statistics to make it less likely that a
{filter-list list} | {address mask [longer-prefix]} route will be dampened.
Step 9 clear ip bgp dampening (Optional) Clear route dampening information, and unsuppress
the suppressed routes.
Step 10 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable flap dampening, use the no bgp dampening router configuration command without
keywords. To set dampening factors back to the default values, use the no bgp dampening router
configuration command with values.
Command Purpose
clear ip bgp address Reset a particular BGP connection.
clear ip bgp * Reset all BGP connections.
clear ip bgp peer-group tag Remove all members of a BGP peer group.
show ip bgp prefix Display peer groups and peers not in peer groups to which the
prefix has been advertised. Also display prefix attributes such as
the next hop and the local prefix.
show ip bgp cidr-only Display all BGP routes that contain subnet and supernet network
masks.
show ip bgp community [community-number] [exact] Display routes that belong to the specified communities.
show ip bgp community-list community-list-number Display routes that are permitted by the community list.
[exact-match]
show ip bgp filter-list access-list-number Display routes that are matched by the specified AS path access
list.
show ip bgp inconsistent-as Display the routes with inconsistent originating autonomous
systems.
show ip bgp regexp regular-expression Display the routes that have an AS path that matches the specified
regular expression entered on the command line.
show ip bgp Display the contents of the BGP routing table.
show ip bgp neighbors [address] Display detailed information on the BGP and TCP connections to
individual neighbors.
show ip bgp neighbors [address] [advertised-routes | Display routes learned from a particular BGP neighbor.
dampened-routes | flap-statistics | paths
regular-expression | received-routes | routes]
show ip bgp paths Display all BGP paths in the database.
show ip bgp peer-group [tag] [summary] Display information about BGP peer groups.
show ip bgp summary Display the status of all BGP connections.
You can also enable the logging of messages generated when a BGP neighbor resets, comes up, or goes
down by using the bgp log-neighbor changes router configuration command.
Note For more detailed information about ISO CLNS, see the Cisco IOS Apollo Domain, Banyan VINES,
DECnet, ISO CLNS and XNS Configuration Guide, Release 12.2. For complete syntax and usage
information for the commands used in this chapter, see the Cisco IOS Apollo Domain, Banyan VINES,
DECnet, ISO CLNS and XNS Command Reference, Release 12.2, use the IOS command reference master
index, or search online.
For IS-IS multiarea routing, you can configure only one process to perform Level 2 routing, although
you can define up to 29 Level 1 areas for each Cisco unit. If Level 2 routing is configured on any process,
all additional processes are automatically configured as Level 1. You can configure this process to
perform Level 1 routing at the same time. If Level 2 routing is not desired for a router instance, remove
the Level 2 capability using the is-type global configuration command. Use the is-type command also
to configure a different router instance as a Level 2 router.
Note For more detailed information about IS-IS, see the “IP Routing Protocols” chapter of the Cisco IOS IP
Configuration Guide, Release 12.2. For complete syntax and usage information for the commands used
in this section, see the Cisco IOS IP Command Reference, Release 12.2.
This section briefly describes how to configure IS-IS routing. It includes this information:
• Default IS-IS Configuration, page 36-64
• Enabling IS-IS Routing, page 36-65
• Configuring IS-IS Global Parameters, page 36-67
• Configuring IS-IS Interface Parameters, page 36-69
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 clns routing Enable ISO connectionless routing on the switch.
Step 3 router isis [area tag] Enable the IS-IS routing for the specified routing process and enter IS-IS
routing configuration mode.
(Optional) Use the area tag argument to identify the area to which the IS-IS
router is assigned. You must enter a value if you are configuring multiple
IS-IS areas.
The first IS-IS instance configured is Level 1-2 by default. Later instances
are automatically Level 1. You can change the level of routing by using the
is-type global configuration command.
Command Purpose
Step 4 net network-entity-title Configure the NETs for the routing process. If you are configuring
multiarea IS-IS, specify a NET for each routing process. You can specify a
name for a NET and for an address.
Step 5 is-type {level-1 | level-1-2 | (Optional) You can configure the router to act as a Level 1 (station) router,
level-2-only} a Level 2 (area) router for multi-area routing, or both (the default):
• level-1—act as a station router only
• level-1-2—act as both a station router and an area router
• level 2—act as an area router only
Step 6 exit Return to global configuration mode.
Step 7 interface interface-id Specify an interface to route IS-IS, and enter interface configuration mode.
If the interface is not already configured as a Layer 3 interface, enter the no
switchport command to put it into Layer 3 mode.
Step 8 ip router isis [area tag] Configure an IS-IS routing process for ISO CLNS on the interface and
attach an area designator to the routing process.
Step 9 clns router isis [area tag] Enable ISO CLNS on the interface.
Step 10 ip address ip-address-mask Define the IP address for the interface. An IP address is required on all
interfaces in an area enabled for IS-IS if any one interface is configured for
IS-IS routing.
Step 11 end Return to privileged EXEC mode.
Step 12 show isis [area tag] database detail Verify your entries.
Step 13 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable IS-IS routing, use the no router isis area-tag router configuration command.
This example shows how to configure three routers to run conventional IS-IS as an IP routing protocol.
In conventional IS-IS, all routers act as Level 1 and Level 2 routers (by default).
Router A
Switch(config)# clns routing
Switch(config)# router isis
Switch(config-router)# net 49.0001.0000.0000.000a.00
Switch(config-router)# exit
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# ip router isis
Switch(config-if)# clns router isis
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# ip router isis
Switch(config-if)# clns router isis
Switch(config-router)# exit
Router B
Switch(config)# clns routing
Switch(config)# router isis
Switch(config-router)# net 49.0001.0000.0000.000b.00
Switch(config-router)# exit
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# ip router isis
Switch(config-if)# clns router isis
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# ip router isis
Router C
Switch(config)# clns routing
Switch(config)# router isis
Switch(config-router)# net 49.0001.0000.0000.000c.00
Switch(config-router)# exit
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# ip router isis
Switch(config-if)# clns router isis
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# ip router isis
Switch(config-if)# clns router isis
Switch(config-router)# exit
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 clns routing Enable ISO connectionless routing on the switch.
Step 3 router isis Specify the IS-IS routing protocol and enter router configuration mode.
Command Purpose
Step 4 default-information originate (Optional) Force a default route into the IS-IS routing domain.If you enter
[route-map map-name] route-map map-name, the routing process generates the default route if the
route map is satisfied.
Step 5 ignore-lsp-errors (Optional) Configure the router to ignore LSPs with internal checksum
errors, instead of purging the LSPs. This command is enabled by default
(corrupted LSPs are dropped). To purge the corrupted LSPs, enter the no
ignore-lsp-errors router configuration command.
Step 6 area-password password (Optional Configure the area authentication password, which is inserted in
Level 1 (station router level) LSPs.
Step 7 domain-password password (Optional) Configure the routing domain authentication password, which is
inserted in Level 2 (area router level) LSPs.
Step 8 summary-address address mask (Optional) Create a summary of addresses for a given level.
[level-1 | level-1-2 | level-2]
Step 9 set-overload-bit [on-startup (Optional) Set an overload bit (a hippity bit) to allow other routers to ignore
{seconds | wait-for-bgp}] the router in their shortest path first (SPF) calculations if the router is
having problems.
• (Optional) on-startup—sets the overload bit only on startup. If
on-startup is not specified, the overload bit is set immediately and
remains set until you enter the no set-overload-bit command. If
on-startup is specified, you must enter a number of seconds or
wait-for-bgp.
• seconds—When the on-startup keyword is configured, causes the
overload bit to be set upon system startup and remain set for this
number of seconds. The range is from 5 to 86400 seconds.
• wait-for-bgp—When the on-startup keyword is configured, causes
the overload bit to be set upon system startup and remain set until BGP
has converged. If BGP does not signal IS-IS that it is converged, IS-IS
will turn off the overload bit after 10 minutes.
Step 10 lsp-refresh-interval seconds (Optional) Set an LSP refresh interval in seconds. The range is from 1 to
65535 seconds. The default is to send LSP refreshes every 900 seconds
(15 minutes).
Step 11 max-lsp-lifetime seconds (Optional) Set the maximum time that LSP packets remain in the router
database without being refreshed. The range is from 1 to 65535 seconds.
The default is 1200 seconds (20 minutes). After the specified time interval,
the LSP packet is deleted.
Step 12 lsp-gen-interval [level-1 | level-2] (Optional) Set the IS-IS LSP generation throttling timers:
lsp-max-wait [lsp-initial-wait
• lsp-max-wait—the maximum interval (in seconds) between two
lsp-second-wait]
consecutive occurrences of an LSP being generated. The range is 1 to
120, the default is 5.
• lsp-initial-wait—the initial LSP generation delay (in milliseconds).
The range is 1 to 10000; the default is 50.
• lsp-second-wait—the hold time between the first and second LSP
generation (in milliseconds). The range is 1 to 10000; the default is
5000.
Command Purpose
Step 13 spf-interval [level-1 | level-2] (Optional) Sets IS-IS shortest path first (SPF) throttling timers.
spf-max-wait [spf-initial-wait
• spf-max-wait—the maximum interval between consecutive SFPs (in
spf-second-wait]
seconds). The range is 1 to 120, the default is 10.
• spf-initial-wait—the initial SFP calculation after a topology change (in
milliseconds). The range is 1 to 10000; the default is 5500.
• spf-second-wait—the holdtime between the first and second SFP
calculation (in milliseconds). The range is 1 to 10000; the default is
5500.
Step 14 prc-interval prc-max-wait (Optional) Sets IS-IS partial route computation (PRC) throttling timers.
[prc-initial-wait prc-second-wait]
• prc-max-wait—the maximum interval (in seconds) between two
consecutive PRC calculations. The range is 1 to 120; the default is 5.
• prc-initial-wait—the initial PRC calculation delay (in milliseconds)
after a topology change. The range is 1 to 10,000; the default is 2000.
• prc-second-wait—the hold time between the first and second PRC
calculation (in milliseconds). The range is 1 to 10,000; the default is
5000.
Step 15 log-adjacency-changes [all] (Optional) Set the router to log IS-IS adjacency state changes. Enter all to
include all changes generated by events that are not related to the
Intermediate System-to-Intermediate System Hellos, including End
System-to-Intermediate System PDUs and link state packets (LSPs).
Step 16 lsp-mtu size (Optional) Specify the maximum LSP packet size in bytes. The range is 128
to 4352; the default is 1497 bytes.
Note If any link in the network has a reduced MTU size, you must change
the LSP MTU size on all routers in the network.
Step 17 partition avoidance (Optional) Causes an IS-IS Level 1-2 border router to stop advertising the
Level 1 area prefix into the Level 2 backbone when full connectivity is lost
among the border router, all adjacent level 1 routers, and end hosts.
Step 18 end Return to privileged EXEC mode.
Step 19 show clns Verify your entries.
Step 20 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable default route generation, use the no default-information originate router configuration
command. Use the no area-password or no domain-password router configuration command to disable
passwords. To disable LSP MTU settings, use the no lsp mtu router configuration command. To return
to the default conditions for summary addressing, LSP refresh interval, LSP lifetime, LSP timers, SFP
timers, and PRC timers, use the no form of the commands. Use the no partition avoidance router
configuration command to disable the output format.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface to be configured and enter interface configuration
mode. If the interface is not already configured as a Layer 3 interface, enter
the no switchport command to put it into Layer 3 mode.
Step 3 isis metric default-metric [level-1 | (Optional) Configure the metric (or cost) for the specified interface. The
level-2] range is from 0 to 63. The default is 10. If no level is entered, the default is
to apply to both Level 1 and Level 2 routers.
Step 4 isis hello-interval {seconds | (Optional) Specify the length of time between hello packets sent by the
minimal} [level-1 | level-2] switch. By default, a value three times the hello interval seconds is
advertised as the holdtime in the hello packets sent. With smaller hello
intervals, topological changes are detected faster, but there is more routing
traffic.
• minimal—causes the system to compute the hello interval based on the
hello multiplier so that the resulting hold time is 1 second.
• seconds—the range is from 1 to 65535. The default is 10 seconds.
Command Purpose
Step 5 isis hello-multiplier multiplier (Optional) Specify the number of IS-IS hello packets a neighbor must miss
[level-1 | level-2] before the router should declare the adjacency as down. The range is from
3 to 1000. The default is 3. Using a smaller hello-multiplier causes fast
convergence, but can result in more routing instability.
Step 6 isis csnp-interval seconds [level-1 | (Optional) Configure the IS-IS complete sequence number PDU (CSNP)
level-2] interval for the interface. The range is from 0 to 65535. The default is
10 seconds.
Step 7 isis retransmit-interval seconds (Optional) Configure the number of seconds between retransmission of
IS-IS LSPs for point-to-point links. The value you specify should be an
integer greater than the expected round-trip delay between any two routers
on the network. The range is from 0 to 65535. The default is 5 seconds.
Step 8 isis retransmit-throttle-interval (Optional) Configure the IS-IS LSP retransmission throttle interval, which
milliseconds is the maximum rate (number of milliseconds between packets) at which
IS-IS LSPs will be re-sent on point-to-point links. The range is from 0 to
65535. The default is determined by the isis lsp-interval command.
Step 9 isis priority value [level-1 | level-2] (Optional) Configure the priority to use for designated router election. The
range is from 0 to 127. The default is 64.
Step 10 isis circuit-type {level-1 | level-1-2 | (Optional) Configure the type of adjacency desired for neighbors on the
level-2-only} specified interface (specify the interface circuit type).
• level-1—a Level 1 adjacency is established if there is at least one area
address common to both this node and its neighbors.
• level-1-2—a Level 1 and 2 adjacency is established if the neighbor is
also configured as both Level 1 and Level 2 and there is at least one
area in common. If there is no area in common, a Level 2 adjacency is
established. This is the default.
• level 2—a Level 2 adjacency is established. If the neighbor router is a
Level 1 router, no adjacency is established.
Step 11 isis password password [level-1 | (Optional) Configure the authentication password for an interface. By
level-2] default, authentication is disabled. Specifying Level 1 or Level 2 enables
the password only for Level 1 or Level 2 routing, respectively. If you do not
specify a level, the default is Level 1 and Level 2.
Step 12 end Return to privileged EXEC mode.
Step 13 show clns interface interface-id Verify your entries.
Step 14 copy running-config startup-config (Optional) Save your entries in the configuration file.
Table 36-13 lists the privileged EXEC commands for clearing and displaying ISO CLNS and IS-IS
routing. For explanations of the display fields, see the Cisco IOS Apollo Domain, Banyan VINES,
DECnet, ISO CLNS and XNS Command Reference, Release 12.2, use the Cisco IOS command reference
master index, or search online.
Table 36-13 ISO CLNS and IS-IS Clear and Show Commands
Command Purpose
clear clns cache Clear and reinitialize the CLNS routing cache.
clear clns es-neighbors Remove end system (ES) neighbor information from the adjacency database.
clear clns is-neighbors Remove intermediate system (IS) neighbor information from the adjacency
database.
clear clns neighbors Remove CLNS neighbor information from the adjacency database.
clear clns route Remove dynamically derived CLNS routing information.
show clns Display information about the CLNS network.
show clns cache Display the entries in the CLNS routing cache.
show clns es-neighbors Display ES neighbor entries, including the associated areas.
show clns filter-expr Display filter expressions.
show clns filter-set Display filter sets.
show clns interface [interface-id] Display the CLNS-specific or ES-IS information about each interface.
show clns neighbor Display information about IS-IS neighbors.
show clns protocol List the protocol-specific information for each IS-IS or ISO IGRP routing
process in this router.
show clns route Display all the destinations to which this router knows how to route CLNS
packets.
show clns traffic Display information about the CLNS packets this router has seen.
show ip route isis Display the current state of the ISIS IP routing table.
show isis database Display the IS-IS link-state database.
show isis routes Display the IS-IS Level 1 routing table.
show isis spf-log Display a history of the shortest path first (SPF) calculations for IS-IS.
show isis topology Display a list of all connected routers in all areas.
show route-map Display all route maps configured or only the one specified.
trace clns destination Discover the paths taken to a specified destination by packets in the network.
which-route {nsap-address | clns-name} Display the routing table in which the specified CLNS destination is found.
Configuring BFD
The Bidirectional Forwarding Detection (BFD) Protocol quickly detects forwarding-path failures for a
variety of media types, encapsulations, topologies, and routing protocols. It operates in a unicast,
point-to-point mode on top of any data protocol being forwarded between two systems to track IPv4
connectivity between directly connected neighbors. BFD packets are encapsulated in UDP packets with
a destination port number of 3784 or 3785.
In EIGRP, IS-IS, and OSPF deployments, the closest alternative to BFD is the use of modified
failure-detection mechanisms. Although reducing the EIGRP, IS-IS, and OSPF timers can result in a
failure-detection rate of 1 to 2 seconds, BFD can provide failure detection in less than 1 second. BFD
can be less CPU-intensive than the reduced timers and, because it is not tied to any particular routing
protocol, it can be used as a generic and consistent failure detection mechanism for multiple routing
protocols.
To create a BFD session, you must configure BFD on both systems (BFD peers). Enabling BFD at the
interface and routing protocol level on BFD peers creates a BFD session. BFD timers are negotiated and
the BFD peers send control packets to each other at the negotiated intervals. If the neighbor is not
directly connected, BFD neighbor registration is rejected.
Figure 36-6 shows a simple network with two routers running OSPF and BFD. When OSPF discovers a
neighbor (1), it sends a request to the BFD process to initiate a BFD neighbor session with the neighbor
OSPF router (2), establishing the BFD neighbor session (3).
1
OSPF neighbors
OSPF OSPF
2 BFD neighbors 2
BFD 3 BFD
127844
172.16.10.2 172.16.10.1
172.18.0.1 Router A Router B 172.17.0.1
Figure 36-7 shows what happens when a failure occurs in the network (1). The BFD neighbor session
with the OSPF neighbor closes (2). BFD notifies the OSPF process that the BFD neighbor is no longer
reachable, and the OSPF process breaks the OSPF neighbor relationship (4). If an alternative path is
available, the routers start converging on it.
4
OSPF neighbors
OSPF X OSPF
3 BFD neighbors 3
X
BFD 2 BFD
1
127845
X
172.16.10.2 172.16.10.1
172.18.0.1 Router A Router B 172.17.0.1
BFD clients are routing protocols that register neighbors with BFD. The switch supports ISIS, OSPF v1
and v2, BGP, EIGRP, and HSRP clients. You can use one BFD session for multiple client protocols. For
example, if a network is running OSPF and EIGRP across the same link to the same peer, you need to
create only one BFD session, and information is shared with both routing protocols.
The switch supports BFD version 0 and version 1. BFD neighbors automatically negotiate the version
and the protocol always runs at the higher version. The default version is version 1.
By default, BFD neighbors exchange both control packets and echo packets for detecting forwarding
failures. The switch sends echo packets at the configured BFD interval rate (from 50 to 999 ms on ports
or from 600 to999 ms on switch virtual interfaces), and control packets at the BFD slow-timer rate (from
1000 to 3000 ms).
Failure-rate detection can be faster in BFD echo mode, which is enabled by default when you configure
BFD session. In this mode, the switch sends echo packets from the BFD software layer, and the BFD
neighbor responds to the echo packets through its fast-switching layer. The echo packets do not reach
the BFD neighbor software layer, but are reflected back over the forwarding path for failure detection.
You configure the rate at which each BFD interface sends BFD echo packets by entering the bfd interval
interface configuration command.
To reduce bandwidth consumption, you can disable the sending of echo packets by entering the no bfd
echo interface configuration command. When BFD echo is disabled at one end of a link, the other end
of the link also does not send echo packets and does not reflect back the echo packet. Control packets
are used to detect forwarding failures. When BFD echo is disabled, the BFD slow-timer configuration
does not apply. In a BFD session running in asynchronous mode, BFD packets are exchanged at a
negotiated duration when the session is up and at the BFD slow-timer value when the session is down.
To run BFD on a switch, you need to configure basic BFD interval parameters on BFD interfaces, enable
routing on the switch, and enable one or more one routing protocol clients for BFD. You also need to
confirm that Cisco Express Forwarding (CEF) is enabled (the default) on participating switches.
For more detailed configuration, see the Bidirectional Forwarding Detection feature module at this URL:
http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/fs_bfd.html
For details on the commands, use the Master Index to the Cisco IOS Command List for Release 12.4. at
this URL:
http://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html
These sections describe configuring BFD:
• Default BFD Configuration, page 36-74
• BFD Configuration Guidelines, page 36-75
• Configuring BFD Session Parameters on an Interface, page 36-76
• Enabling BFD Routing Protocol Clients, page 36-77
Note We recommend that you configure the BFD interval parameters on an interface before configuring the
routing protocol commands, especially when using EIGRP.
• Confirm that CEF is enabled on participating switches (the default) as well as IP routing.
• BFD is supported on physical interfaces that are configured as routing interfaces. Starting with
Cisco IOS release 12.2(55)SE, BFD is also supported on SVIs. As with physical interfaces, BFD
sessions do not operate on an SVI until you put the SVI into Layer 3 mode by assigning it an IP
address and enable routing on the switch.
Note Entering the bfd all-interfaces global configuration command to enable BFD on all interfaces
associated with a routing protocol enables BFD on all physical interfaces and SVIs associated
with that routing protocol.
Note Although you can configure BFD on Layer 2 interfaces, a BFD session cannot start until both interfaces
are in Layer 3 mode and routing is enabled on the switch.
Beginning in privileged EXEC mode, follow these steps to configure BFD parameters on any interface
participating in a BFD session:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify an interface for a BFD session, and enter interface configuration
mode. Physical interfaces and SVIs support BFD.
Step 3 no switchport Remove the interface from Layer 2 configuration mode (physical interfaces
only).
Step 4 ip address ip-address subnet-mask Configure the IP address and IP subnet mask.
Step 5 bfd interval milliseconds min_rx Set BFD parameters for echo packets on the interface.
milliseconds multiplier value
• interval—Specify the rate at which BFD echo packets are sent to BFD
peers. The range is from 50 to 999 milliseconds (ms) on physical
interfaces and from 600 to 999 ms on SVIs.
• min_rx—Specify the rate at which BFD echo packets are expected to
be received from BFD peers. The range is from 50 to 999 ms on
physical interfaces and from 600 to 999 ms on SVIs.
• multiplier—Specify the number of consecutive BFD echo packets that
must be missed from a BFD peer before BFD declares that it is
unavailable and informs the other BFD peer of the failure. The range is
from 3 to 50.
Note There are no baseline BFD parameter defaults.
Step 6 end Return to privileged EXEC mode.
Step 7 show running-config Verify your entries.
Step 8 show bfd neighbor detail (Optional) Display the final configured or negotiated values when the
session is created with a neighbor.
Step 9 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove the BFD parameter configuration, enter the no bfd interval interface configuration
command.
Beginning in privileged EXEC mode, follow these steps to configure OSFP BFD globally, and to
optionally disable it on specific interfaces:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 router ospf process- id Specify an OSPF process, and enter router configuration mode.
Step 3 bfd all-interfaces Enable BFD globally on all interfaces associated with the OSPF routing
process.
Step 4 exit (Optional) Return to global configuration mode if you want to disable BFD
on one or more OSPF interfaces.
Step 5 interface interface-id (Optional) Specify an interface, and enter interface configuration mode.
Step 6 ip ospf bfd disable (Optional) Disable BFD on the specified OSPF interface. Repeat Steps 5
and 6 for all OSPF interfaces on which you do not want to run BFD
sessions.
Step 7 end Return to privileged EXEC mode.
Step 8 show bfd neighbors [detail] Verify the configuration.
Step 9 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable OSPF BFD on all interfaces, enter the no bfd all-interfaces router configuration command.To
disable it on an interface, enter the no ip osfp bfd or the ip ospf bfd disable interface configuration
command on the interface.
If you want to run OSPF BFD on only one or a few interfaces, you can enter the ip ospf bfd interface
configuration command on those interfaces instead of enabling it globally. See the next procedure.
Note If you try to configure OSPF BFD on a Layer 2 interface, the configuration is not recognized.
Beginning in privileged EXEC mode, follow these steps to configure OSFP BFD on an individual
interface:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 router ospf process- id Specify an OSPF process, and enter router configuration mode.
Step 3 exit Return to global configuration mode.
Step 4 interface interface-id (Specify an interface, and enter interface configuration mode.
Step 5 ip ospf bfd Enable BFD on the specified OSPF interface. Repeat Steps 3 and 4 for all
OSPF interfaces on which you want to run BFD sessions.
Step 6 end Return to privileged EXEC mode.
Step 7 show bfd neighbors [detail] Verify the configuration.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable OSPF BFD on an interface, enter the no ip osfp bfd or the ip ospf bfd disable interface
configuration command on the interface.
This is an example of configuring BFD for OSPF on a single interface:
Switch(config)# router ospf 109
Switch(config-router)# exit
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# ip ospf bfd
Beginning in privileged EXEC mode, follow these steps to configure IS-IS BFD globally, and to
optionally disable it on specific interfaces:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 router is-is area-tag Specify an IS-IS process and enter router configuration mode.
Command Purpose
Step 3 bfd all-interfaces Enable BFD globally on all interfaces associated with the IS-IS routing
process.
Step 4 exit (Optional) Return to global configuration mode if you want to disable BFD
on one or more IS-IS interfaces.
Step 5 interface interface-id (Optional) Specify an interface and enter interface configuration mode.
Step 6 ip router isis (Optional) Enable IPv4 IS-IS routing on the interface.
Step 7 isis bfd disable (Optional) Disable BFD on the IS-IS interface. Repeat Steps 5 through 7
for all IS-IS interfaces on which you do not want to run BFD sessions.
Step 8 end Return to privileged EXEC mode.
Step 9 show bfd neighbors [detail] Verify the configuration.
Step 10 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable IS-IS BFD on all interfaces, enter the no bfd all-interfaces router configuration command.
To disable it on the specified interface, enter the no isis bfd or the isis bfd disable interface configuration
command on the interface.
If you only want to run IS-IS BFD on a few interfaces, instead of enabling it globally, you can enter the
isis bfd interface configuration command on those interfaces. See the next procedure.
Note Although IS-IS BFD operates only on Layer 3 interfaces, you can configure it on interfaces in Layer 2
or Layer 3 mode. When you enable it, you see this message:
%ISIS BFD is reverting to router mode configuration, and remains disabled.
This is an example of setting fast convergence and configuring BFD for IS-IS on all IS-IS interfaces:
Switch(config)# router is-is tag1
Switch(config-router)# bfd all-interfaces
Switch(config-router)# exit
Beginning in privileged EXEC mode, follow these steps to configure IS-IS BFD on an individual
interface:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 router is-is area-tag Specify an IS-IS process and enter router configuration mode.
Step 3 exit Return to global configuration mode.
Step 4 interface interface-id (Specify an interface, and enter interface configuration mode.
Step 5 isis bfd Enable BFD on the specified IS-IS interface. Repeat Steps 3 and 4 for all
IS-IS interfaces on which you want to run BFD sessions.
Step 6 end Return to privileged EXEC mode.
Step 7 show bfd neighbors [detail] Verify the configuration.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable IS-IS BFD on an interface, enter the no isis bfd or the isis bfd disable interface configuration
command on the interface.
This is an example of configuring BFD for IS-IS on a single interface:
Switch(config)# router is-is tag1
Switch(config-router)# exit
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# isis bfd
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 router bgp as-tag Specify a BGP autonomous system, and enter router configuration mode.
Step 3 neighbor ip-address fall-over bfd Enable BFD support for fallover on the BFD neighbor.
Step 4 end Return to privileged EXEC mode.
Step 5 show bfd neighbors [detail] Verify the configuration.
>
show ip bgp neighbor Display information about BGP connections to neighbors.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable BGP BFD, enter the no neighbor ip-address fall-over bfd router configuration command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 router eigrp as-number Specify an EIGRP autonomous system number, and enter router
configuration mode.
Step 3 log-adjacency changes [detail] Configure the switch to send a system logging message when an EIGRP
neighbor goes up or down.
Step 4 bfd {all-interfaces | interface Enable BFD for EIGRP.
interface-id}
• Enter all-interfaces to globally enable BFD on all interfaces
associated with the EIGRP routing process
• Enter interface interface-id to enable BFD on a per-interface basis for
one or more interfaces associated with the EIGRP routing process.
Command Purpose
Step 5 end Return to privileged EXEC mode.
Step 6 show bfd neighbors [detail] Verify the configuration.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable EIGRP BFD on all interfaces, enter the no bfd all-interfaces router configuration command.
To disable it on an interface, enter the no bfd interface interface-id router configuration command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify an interface for a BFD session, and enter interface configuration
mode. Only physical interfaces support BFD.
Step 3 ip address ip-address subnet-mask Configure the IP address and IP subnet mask for the interface.
Step 4 standby [group-number] ip Activate HSRP.
[ip-address] [secondary]]
Step 5 standby bfd (Optional) Enable HSRP support for BFD on the interface.
Step 6 exit Return to global configuration mode.
Step 7 standby bfd all-interfaces (Optional) Enable HSRP support for BFD on all interfaces.
Step 8 end Return to privileged EXEC mode.
Step 9 show standby neighbors Verify your entries.
Step 10 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable HSRP support for BFD on all interfaces, enter the no standby bfd all-interfaces global
configuration command. To disable it on an interface, enter the no standby bfd interface configuration
command.
Note If you disable standby BFD on an interface by entering the no standby bfd interface configuration
command, to activate BFD sessions on other interfaces, you must disable and reenable it globally by
entering the no standby bfd all-interfaces global configuration command followed by the standby bfd
all-interfaces global configuration command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter a BFD interface and enter interface configuration mode.
Step 3 no bfd echo Disable BFD echo mode on the interface. It is enabled by default, but can
be disabled independently on BFD neighbors.
Step 4 exit Return to global configuration mode.
Step 5 end Return to privileged EXEC mode.
Step 6 show bfd neighbors detail Verify your entries.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
To reenable echo mode on the interface, enter the bfd echo interface configuration command.To reenable
echo mode on the switch, enter the bfd echo global configuration command.
Configuring Multi-VRF CE
Virtual Private Networks (VPNs) provide a secure way for customers to share bandwidth over a
service-provider backbone network. A VPN is a collection of sites sharing a common routing table. A
customer site is connected to the service-provider network by one or more interfaces, and the service
provider associates each interface with a VPN routing table, called a VPN routing/forwarding (VRF)
table. In a multiprotocol label switching (MPLS) VPN deployment, all customers have their own
customer-edge (CE) device), and every CE has a dedicated line connected to a provider-edge (PE) router.
With multiple VPN routing/forwarding (multi-VRF), multiple customers can share one CE, and only one
physical link is needed between the CE and the PE. This is accomplished by extending some PE
functionality to the shared CE devices. The shared CE maintains separate VRF tables for each customer
and switches or routes packets for each customer based on the CE routing table. Multi-VRF CE allows
a service provider to support two or more VPNs with overlapping IP addresses.
This section includes these topics:
• Understanding Multi-VRF CE, page 36-83
• Default Multi-VRF CE Configuration, page 36-85
• Multi-VRF CE Configuration Guidelines, page 36-85
• Configuring VRFs, page 36-86
• Configuring VRF-Aware Services, page 36-87
• Configuring Multicast VRFs, page 36-90
Understanding Multi-VRF CE
Multi-VRF CE is a feature that allows a service provider to support two or more VPNs, where IP
addresses can be overlapped among the VPNs. Multi-VRF CE uses input interfaces to distinguish routes
for different VPNs and forms virtual packet-forwarding tables by associating one or more Layer 3
interfaces with each VRF. Interfaces in a VRF can be either physical, such as Ethernet ports, or logical,
such as VLAN SVIs, but an interface cannot belong to more than one VRF at any time.
Figure 36-8 Catalyst 3750 Metro Switches Acting as Multiple Virtual CEs
VPN 1 VPN 1
VPN 2 VPN 2
101385
CE = Customer-edge device
PE = Provider-edge device
When the CE switch receives a command to add a Layer 3 interface to a VRF, it sets up the appropriate
mapping between the VLAN ID and the policy label in multi-VRF-CE-related data structures and adds
the VLAN ID and policy label to the VLAN database.
When the multi-VRF CE is configured, the Layer 3 forwarding table is conceptually partitioned into two
sections:
• The multi-VRF CE routing section contains the routes from different VPNs.
• The global routing section contains routes to non-VPN networks, such as the Internet.
VLAN IDs from different VRFs are mapped into different policy labels, which are used to distinguish
the VRFs during processing. If no route is found in the multi-VRF CE section of the Layer 3 forwarding
table, the global routing section is used to determine the forwarding path. For each new VPN route
learned, the Layer 3 setup function retrieves the policy label by using the VLAN ID of the ingress port
and inserts the policy label and new route to the multi-VRF CE routing section. If the packet is received
from a routed port, the port internal VLAN ID number is used; if the packet is received from an SVI, the
VLAN number is used.
This is the packet-forwarding process in a multi-VRF-CE-enabled network:
• When the switch receives a packet from a VPN, the switch looks up the routing table, based on the
input policy label number. When a route is found, the switch forwards the packet to the PE.
• When the ingress PE receives a packet from the CE, it performs a VRF lookup. When a route is
found, the router adds a corresponding MPLS label to the packet and sends it to the MPLS network.
• When an egress PE receives a packet from the network, it removes the label and uses the label to
identify the correct VPN routing table. Then it performs the normal route lookup. When a route is
found, it forwards the packet to the correct adjacency.
• When a CE receives a packet from an egress PE, it uses the input policy label to look up the correct
VPN routing table. When a route is found, it forwards the packet within the VPN.
To configure VRF, you create a VRF table and specify the Layer 3 interface associated with the VRF.
Then configure the routing protocols in the VPN and between the CE and the PE. BGP is the preferred
routing protocol used to distribute VPN routing information across the provider’s backbone.
The multi-VRF CE network has three major components:
• VPN route target communities—lists of all other members of a VPN community. You need to
configure VPN route targets for each VPN community member.
– BGP does not require multiple algorithms to communicate with multiple CEs.
– BGP is designed for passing routing information between systems run by different
administrations.
– BGP makes it easy to pass attributes of the routes to the CE.
• Multi-VRF-CE does not support IGRP.
• Multi-VRF CE does not affect the packet switching rate.
• When multi-VRF CE is configured, you cannot assign the same Hot Standby Routing Protocol
(HSRP) standby address to two different VPNs.
Configuring VRFs
Beginning in privileged EXEC mode, follow these steps to configure one or more VRFs. For complete
syntax and usage information for the commands, see the switch command reference for this release and
the Cisco IOS Switching Services Command Reference, Release 12.2.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip routing Enable IP routing.
Step 3 ip vrf vrf-name Name the VRF, and enter VRF configuration mode.
Step 4 rd route-distinguisher Create a VRF table by specifying a route distinguisher. Enter either an
AS number and an arbitrary number (xxx:y) or an IP address and
arbitrary number (A.B.C.D:y)
Step 5 route-target {export | import | both} Create a list of import, export, or import and export route target
route-target-ext-community communities for the specified VRF. Enter either an AS system number
and an arbitrary number (xxx:y) or an IP address and an arbitrary
number (A.B.C.D:y). The route-target-ext-community should be the
same as the route-distinguisher entered in Step 4.
Step 6 import map route-map (Optional) Associate a route map with the VRF.
Step 7 interface interface-id Enter interface configuration mode and specify the Layer 3 interface to
be associated with the VRF. The interface can be a routed port or SVI.
Step 8 ip vrf forwarding vrf-name Associate the VRF with the Layer 3 interface.
Step 9 end Return to privileged EXEC mode.
Step 10 show ip vrf [brief | detail | interfaces] Verify the configuration. Display information about the configured
[vrf-name] VRFs.
Step 11 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no ip vrf vrf-name global configuration command to delete a VRF and to remove all interfaces
from it. Use the no ip vrf forwarding interface configuration command to remove an interface from the
VRF.
Note VRF-Aware services are not supported for Unicast Reverse Path Forwarding (uRPF).
Command Purpose
show ip arp vrf vrf-name Display the ARP table in the specified VRF.
Command Purpose
ping vrf vrf-name ip-host Display the ARP table in the specified VRF.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 snmp-server trap authentication vrf Enable SNMP traps for packets on a VRF.
Step 3 snmp-server engineID remote <host> Configure a name for the remote SNMP engine on a switch.
vrf <vpn instance> <engine-id string>
Step 4 snmp-server host <host> vrf <vpn Specify the recipient of an SNMP trap operation and specify the VRF
instance> traps <community> table to be used for sending SNMP traps.
Step 5 snmp-server host <host> vrf <vpn Specify the recipient of an SNMP inform operation and specify the VRF
instance> informs <community> table to be used for sending SNMP informs.
Step 6 snmp-server user <user> <group> Add a user to an SNMP group for a remote host on a VRF for SNMP
remote <host> vrf <vpn instance> access.
<security model>
Step 7 end Return to privileged EXEC mode.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and specify the Layer 3 interface to
configure.
Step 3 no switchport Remove the interface from Layer 2 configuration mode if it is a physical
interface.
Step 4 ip vrf forwarding <vrf-name> Configure VRF on the interface.
Step 5 ip address ip address Enter the IP address for the interface.
Step 6 standby 1 ip ip address Enable HSRP and configure the virtual IP address.
Step 7 end Return to privileged EXEC mode.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 logging on Enable or temporarily disable logging of storage router event message.
Step 3 logging host ip address vrf vrf name Specify the host address of the syslog server where logging messages
are to be sent.
Step 4 logging buffered logging buffered size Log messages to an internal buffer.
debugging
Step 5 logging trap debugging Limit the logging messages sent to the syslog server.
Step 6 logging facility facility Send system logging messages to a logging facility.
Step 7 end Return to privileged EXEC mode.
Command Purpose
traceroute vrf vrf-name ipaddress Specify the name of a VPN VRF in which to find the destination
address.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip ftp source-interface interface-type Specify the source IP address for FTP connections.
interface-number
Step 3 end Return to privileged EXEC mode.
To specify the IP address of an interface as the source address for TFTP connections, use the ip tftp
source-interface show mode command. To return to the default, use the no form of this command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip tftp source-interface interface-type Specify the source IP address for TFTP connections.
interface-number
Step 3 end Return to privileged EXEC mode.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip routing Enable IP routing mode.
Step 3 ip vrf vrf-name Name the VRF, and enter VRF configuration mode.
Step 4 rd route-distinguisher Create a VRF table by specifying a route distinguisher. Enter either an
AS number and an arbitrary number (xxx:y) or an IP address and an
arbitrary number (A.B.C.D:y)
Step 5 route-target {export | import | both} Create a list of import, export, or import and export route target
route-target-ext-community communities for the specified VRF. Enter either an AS system number
and an arbitrary number (xxx:y) or an IP address and an arbitrary
number (A.B.C.D:y). The route-target-ext-community should be the
same as the route-distinguisher entered in Step 4.
Step 6 import map route-map (Optional) Associate a route map with the VRF.
Step 7 ip multicast-routing vrf vrf-name (Optional) Enable global multicast routing for VRF table.
distributed
Step 8 interface interface-id Specify the Layer 3 interface to be associated with the VRF, and enter
interface configuration mode. The interface can be a routed port or an
SVI.
Step 9 ip vrf forwarding vrf-name Associate the VRF with the Layer 3 interface.
Step 10 ip address ip-address mask Configure IP address for the Layer 3 interface.
Step 11 ip pim sparse-dense mode Enable PIM on the VRF-associated Layer 3 interface.
Step 12 end Return to privileged EXEC mode.
Command Purpose
Step 13 show ip vrf [brief | detail | interfaces] Verify the configuration. Display information about the configured
[vrf-name] VRFs.
Step 14 copy running-config startup-config (Optional) Save your entries in the configuration file.
For more information about configuring a multicast within a Multi-VRF CE, see the Cisco IOS IP
Multicast Configuration Guide, Release 12.4.
Note To configure an EIGRP routing process to run within a VRF instance, you must configure an
autonomous-system number by entering the autonomous-system autonomous-system-number
address-family configuration mode command.
Beginning in privileged EXEC mode, follow these steps to configure OSPF in the VPN:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 router ospf process-id vrf vrf-name Enable OSPF routing, specify a VPN forwarding table, and enter router
configuration mode.
Step 3 log-adjacency-changes (Optional) Log changes in the adjacency state. This is the default state.
Step 4 redistribute bgp Set the switch to redistribute information from the BGP network to the
autonomous-system-number subnets OSPF network.
Step 5 network network-number area area-id Define a network address and mask on which OSPF runs and the area ID
for that network address.
Step 6 end Return to privileged EXEC mode.
Step 7 show ip ospf process-id Verify the configuration of the OSPF network.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no router ospf process-id vrf vrf-name global configuration command to disassociate the VPN
forwarding table from the OSPF routing process.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 router bgp autonomous-system-number Configure the BGP routing process with the AS number passed to other
BGP routers, and enter router configuration mode.
Step 3 network network-number mask Specify a network and mask to announce using BGP.
network-mask
Step 4 redistribute ospf process-id match Set the switch to redistribute OSPF internal routes.
internal
Step 5 network network-number area area-id Define a network address and mask on which OSPF runs and the area
ID for that network address.
Step 6 address-family ipv4 vrf vrf-name Define BGP parameters for PE to CE routing sessions, and enter VRF
address-family mode.
Step 7 neighbor address remote-as as-number Define a BGP session between PE and CE routers.
Step 8 neighbor address activate Activate the advertisement of the IPv4 address family.
Step 9 end Return to privileged EXEC mode.
Step 10 show ip bgp [ipv4] [neighbors] Verify BGP configuration.
Step 11 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no router bgp autonomous-system-number global configuration command to delete the BGP
routing process. Use the command with keywords to delete routing characteristics.
Switch D VPN1
208.0.0.0
Fast Switch H
Ethernet
8
Switch E
108.0.0.0
Fast
Ethernet VPN2
7
Switch J
CE1 PE CE2
VPN2
Gigabit
Switch F Ethernet
118.0.0.0 1
Fast
Ethernet Global network
11
Switch K
Global network
Switch G
168.0.0.0
Fast
Ethernet
101386
CE = Customer-edge device
3
PE = Provider-edge device
Configuring Switch A
Configure the loopback and physical interfaces on Switch A. Gigabit Ethernet port 1 is a trunk
connection to the PE. Fast Ethernet ports 8 and 11 connect to VPNs:
Switch(config)# interface loopback1
Switch(config-if)# ip vrf forwarding v11
Switch(config-if)# ip address 8.8.1.8 255.255.255.0
Switch(config-if)# exit
Configure the VLANs used on Switch A. VLAN 10 is used by VRF 11 between the CE and the PE.
VLAN 20 is used by VRF 12 between the CE and the PE. VLANs 118 and 208 are used for VRF for the
VPNs that include Switch F and Switch D, respectively:
Switch(config)# interface vlan10
Switch(config-if)# ip vrf forwarding v11
Switch(config-if)# ip address 38.0.0.8 255.255.255.0
Switch(config-if)# exit
Configuring Switch D
Configuring Switch F
On Switch B (the PE router), these commands configure the connections to the CE device, Switch A.
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# ip vrf v1
Router(config-vrf)# rd 100:1
Router(config-vrf)# route-target export 100:1
Router(config-vrf)# route-target import 100:1
Router(config-vrf)# exit
Router(config)# ip vrf v2
Router(config-vrf)# rd 100:2
Router(config-vrf)# route-target export 100:2
Router(config-vrf)# route-target import 100:2
Router(config-vrf)# exit
Router(config)# ip cef
Router(config)# interface Loopback1
Router(config-if)# ip vrf forwarding v1
Router(config-if)# ip address 3.3.1.3 255.255.255.0
Router(config-if)# exit
Command Purpose
show ip protocols vrf vrf-name Display routing protocol information associated
with a VRF.
show ip route vrf vrf-name [connected] [protocol [as-number]] [list] Display IP routing table information associated
[mobile] [odr] [profile] [static] [summary] [supernets-only] with a VRF.
show ip vrf [brief | detail | interfaces] [vrf-name] Display information about the defined VRF
instances.
For more information about the information in the displays, see the Cisco IOS Switching Services
Command Reference, Release 12.2.
Caution Although the no ip route-cache cef interface configuration command to disable CEF on an interface is
visible in the CLI, we strongly recommend that you do not disable CEF on interfaces except for
debugging purposes.
Beginning in privileged EXEC mode, follow these steps to enable CEF globally and on an interface in
case, if, for some reason, it has been disabled:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip cef Enable CEF operation.
Step 3 interface interface-id Enter interface configuration mode, and specify the Layer 3
interface to configure.
Step 4 ip route-cache cef Enable CEF on the interface for software-forwarded traffic.
Step 5 end Return to privileged EXEC mode.
Step 6 show ip cef Display the CEF status on all interfaces.
Step 7 show cef interface [interface-id] Display detailed CEF information for all interfaces or the
specified interface.
Step 8 show adjacency Display CEF adjacency table information.
Step 9 copy running-config startup-config (Optional) Save your entries in the configuration file.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 router {bgp | eigrp | isis | iso-igrp | ospf | Enter router configuration mode.
rip}
Step 3 maximum-paths maximum Set the maximum number of parallel paths for the protocol routing
table. The range is from 1 to 8; the default is 4 for most IP routing
protocols, but only 1 for BGP.
Step 4 end Return to privileged EXEC mode.
Step 5 show ip protocols Verify the setting in the Maximum path field.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no maximum-paths router configuration command to restore the default value.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip route prefix mask {address | interface} [distance] Establish a static route.
Step 3 end Return to privileged EXEC mode.
Step 4 show ip route Display the current state of the routing table to verify
the configuration.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no ip route prefix mask {address | interface} global configuration command to remove a static
route.
The switch retains static routes until you remove them. However, you can override static routes with
dynamic routing information by assigning administrative distance values. Each dynamic routing
protocol has a default administrative distance, as listed in Table 36-16. If you want a static route to be
overridden by information from a dynamic routing protocol, set the administrative distance of the static
route higher than that of the dynamic protocol.
Static routes that point to an interface are advertised through RIP, IGRP, and other dynamic routing
protocols, whether or not static redistribute router configuration commands were specified for those
routing protocols. These static routes are advertised because static routes that point to an interface are
considered in the routing table to be connected and hence lose their static nature. However, if you define
a static route to an interface that is not one of the networks defined in a network command, no dynamic
routing protocols advertise the route unless a redistribute static command is specified for these
protocols.
When an interface goes down, all static routes through that interface are removed from the IP routing
table. When the software can no longer find a valid next hop for the address specified as the forwarding
router's address in a static route, the static route is also removed from the IP routing table.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip default-network network number Specify a default network.
Step 3 end Return to privileged EXEC mode.
Step 4 show ip route Display the selected default route in the gateway of last resort
display.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no ip default-network network number global configuration command to remove the route.
When default information is passed through a dynamic routing protocol, no further configuration is
required. The system periodically scans its routing table to choose the optimal default network as its
default route. In IGRP networks, there might be several candidate networks for the system default. Cisco
routers use administrative distance and metric information to determine the default route or the gateway
of last resort.
If dynamic default information is not being passed to the system, candidates for the default route are
specified with the ip default-network global configuration command. If this network appears in the
routing table from any source, it is flagged as a possible choice for the default route. If the router has no
interface on the default network, but does have a path to it, the network is considered as a possible
candidate, and the gateway to the best default path becomes the gateway of last resort.
Note A route map with no set route-map configuration commands is sent to the CPU, which causes high CPU
utilization.
You can also identify route-map statements as permit or deny. If the statement is marked as a deny, the
packets meeting the match criteria are sent back through the normal forwarding channels
(destination-based routing). If the statement is marked as permit, set clauses are applied to packets
meeting the match criteria. Packets that do not meet the match criteria are forwarded through the normal
routing channel.
You can use the BGP route map continue clause to execute additional entries in a route map after an
entry is executed with successful match and set clauses. You can use the continue clause to configure
and organize more modular policy definitions so that specific policy configurations need not be repeated
within the same route map. Beginning in Cisco IOS Release 12.2(37)SE, the switch supports the
continue clause for outbound policies. For more information about using the route map continue clause,
see the BGP Route-Map Continue Support for an Outbound Policy feature guide for Cisco IOS Release
12.4(4)T at this URL:
http://www.cisco.com/en/US/products/ps6441/products_feature_guides_list.html
Note Although each of Steps 3 through 14 in the following section is optional, you must enter at least one
match route-map configuration command and one set route-map configuration command.
Beginning in privileged EXEC mode, follow these steps to configure a route map for redistribution:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 route-map map-tag [permit | deny] [sequence number] Define any route maps used to control redistribution and
enter route-map configuration mode.
map-tag—A meaningful name for the route map. The
redistribute router configuration command uses this
name to reference this route map. Multiple route maps
might share the same map tag name.
(Optional) If permit is specified and the match criteria
are met for this route map, the route is redistributed as
controlled by the set actions. If deny is specified, the
route is not redistributed.
sequence number (Optional)— Number that indicates the
position a new route map is to have in the list of route
maps already configured with the same name.
Step 3 match as-path path-list-number Match a BGP AS path access list.
Step 4 match community-list community-list-number [exact] Match a BGP community list.
Step 5 match ip address {access-list-number | Match a standard access list by specifying the name or
access-list-name} [...access-list-number | number. It can be an integer from 1 to 199.
...access-list-name]
Step 6 match metric metric-value Match the specified route metric. The metric-value can be
an EIGRP five-part metric with a specified value from 0
to 4294967295.
Step 7 match ip next-hop {access-list-number | Match a next-hop router address passed by one of the
access-list-name} [...access-list-number | access lists specified (numbered from 1 to 199).
...access-list-name]
Step 8 match tag tag value [...tag-value] Match the specified tag value in a list of one or more route
tag values. Each can be an integer from 0 to 4294967295.
Step 9 match interface type number [...type number] Match the specified next hop route out one of the
specified interfaces.
Step 10 match ip route-source {access-list-number | Match the address specified by the specified advertised
access-list-name} [...access-list-number | access lists.
...access-list-name]
Step 11 match route-type {local | internal | external [type-1 | Match the specified route-type:
type-2]}
• local—Locally generated BGP routes.
• internal—OSPF intra-area and interarea routes or
EIGRP internal routes.
• external—OSPF external routes (Type 1 or Type 2)
or EIGRP external routes.
Step 12 set dampening halflife reuse suppress Set BGP route dampening factors.
max-suppress-time
Step 13 set local-preference value Assign a value to a local BGP path.
Command Purpose
Step 14 set origin {igp | egp as | incomplete} Set the BGP origin code.
Step 15 set as-path {tag | prepend as-path-string} Modify the BGP autonomous system path.
Step 16 set level {level-1 | level-2 | level-1-2 | stub-area | Set the level for routes that are advertised into the
backbone} specified area of the routing domain. The stub-area and
backbone are OSPF NSSA and backbone areas.
Step 17 set metric metric value Set the metric value to give the redistributed routes (for
EIGRP only). The metric value is an integer from
-294967295 to 294967295.
Step 18 set metric bandwidth delay reliability loading mtu Set the metric value to give the redistributed routes (for
EIGRP only):
• bandwidth—Metric value or IGRP bandwidth of the
route in kilobits per second in the range 0 to
4294967295
• delay—Route delay in tens of microseconds in the
range 0 to 4294967295.
• reliability—Likelihood of successful packet
transmission expressed as a number between 0 and
255, where 255 means 100 percent reliability and 0
means no reliability.
• loading— Effective bandwidth of the route expressed
as a number from 0 to 255 (255 is 100 percent
loading).
• mtu—Minimum maximum transmission unit (MTU)
size of the route in bytes in the range 0 to
4294967295.
Step 19 set metric-type {type-1 | type-2} Set the OSPF external metric type for redistributed routes.
Step 20 set metric-type internal Set the multi-exit discriminator (MED) value on prefixes
advertised to external BGP neighbor to match the IGP
metric of the next hop.
Step 21 set weight Set the BGP weight for the routing table. The value can
be from 1 to 65535.
Step 22 end Return to privileged EXEC mode.
Step 23 show route-map Display all route maps configured or only the one
specified to verify configuration.
Step 24 copy running-config startup-config (Optional) Save your entries in the configuration file.
To delete an entry, use the no route-map map tag global configuration command or the no match or no
set route-map configuration commands.
You can distribute routes from one routing domain into another and control route distribution.
Beginning in privileged EXEC mode, follow these steps to control route redistribution. Note that the
keywords are the same as defined in the previous procedure.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 router {bgp | eigrp | isis | ospf | rip} Enter router configuration mode.
Step 3 redistribute protocol [process-id] {level-1 | level-1-2 | Redistribute routes from one routing protocol to
level-2} [metric metric-value] [metric-type type-value] another routing protocol. If no route-maps are
[match internal | external type-value] [tag tag-value] specified, all routes are redistributed. If the keyword
[route-map map-tag] [weight weight] [subnets] route-map is specified with no map-tag, no routes are
distributed.
Step 4 default-metric number Cause the current routing protocol to use the same
metric value for all redistributed routes (BGP, RIP and
OSPF).
Step 5 default-metric bandwidth delay reliability loading mtu Cause the EIGRP routing protocol to use the same
metric value for all non-EIGRP redistributed routes.
Step 6 no default-information {in | out} Disable the redistribution of default information
between EIGRP processes, which is enabled by
default.
Step 7 end Return to privileged EXEC mode.
Step 8 show route-map Display all route maps configured or only the one
specified to verify configuration.
Step 9 copy running-config startup-config (Optional) Save your entries in the configuration file.
You can use PBR to provide equal-access and source-sensitive routing, routing based on interactive
versus batch traffic, or routing based on dedicated links. For example, you could transfer stock records
to a corporate office on a high-bandwidth, high-cost link for a short time while transmitting routine
application data such as e-mail over a low-bandwidth, low-cost link.
With PBR, you classify traffic using access control lists (ACLs) and then make traffic go through a
different path. PBR is applied to incoming packets. All packets received on an interface with PBR
enabled are passed through route maps. Based on the criteria defined in the route maps, packets are
forwarded (routed) to the appropriate next hop.
• If packets do not match any route map statements, all set clauses are applied.
• If a statement is marked as permit and the packets do not match any route-map statements, the
packets are sent through the normal forwarding channels, and destination-based routing is
performed.
• For PBR, route-map statements marked as deny are not supported.
For more information about configuring route maps, see the “Using Route Maps to Redistribute Routing
Information” section on page 36-101.
You can use standard IP ACLs to specify match criteria for a source address or extended IP ACLs to
specify match criteria based on an application, a protocol type, or an end station. The process proceeds
through the route map until a match is found. If no match is found, normal destination-based routing
occurs. There is an implicit deny at the end of the list of match statements.
If match clauses are satisfied, you can use a set clause to specify the IP addresses identifying the next
hop router in the path.
Note For details about PBR commands and keywords, see the Cisco IOS IP Command Reference, Volume 2
of 3: Routing Protocols, Release 12.2. For a list of PBR commands that are visible but not supported by
the switch, see Appendix B, “Unsupported Commands in Cisco IOS Release12.2(58)SE.”
– Do not match ACLs with deny ACEs. Packets that match a deny ACE are sent to the CPU, which
could cause high CPU utilization.
• The number of TCAM entries used by PBR depends on the route map itself, the ACLs used, and the
order of the ACLs and route-map entries.
• Policy-based routing based on packet length, IP precedence and TOS, set interface, set default next
hop, or set default interface are not supported. Policy maps with no valid set actions or with set
action set to Don’t Fragment are not supported.
Enabling PBR
By default, PBR is disabled on the switch. To enable PBR, you must create a route map that specifies
the match criteria and the resulting action if all of the match clauses are met. Then, you must enable PBR
for that route map on an interface. All packets arriving on the specified interface matching the match
clauses are subject to PBR.
PBR can be fast-switched or implemented at speeds that do not slow down the switch. Fast-switched
PBR supports most match and set commands. PBR must be enabled before you enable fast-switched
PBR. Fast-switched PBR is disabled by default.
Packets that are generated by the switch, or local packets, are not normally policy-routed. When you
globally enable local PBR on the switch, all packets that originate on the switch are subject to local PBR.
Local PBR is disabled by default.
Beginning in privileged EXEC mode, follow these steps to configure PBR:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 route-map map-tag [permit] [sequence Define any route maps used to control where packets are output, and enter
number] route-map configuration mode.
• map-tag—A meaningful name for the route map. The ip policy
route-map interface configuration command uses this name to
reference the route map. Multiple route maps might share the same
map tag name.
• (Optional) If permit is specified and the match criteria are met for
this route map, the route is policy-routed as controlled by the set
actions.
Note The route-map deny statement is not supported in PBR route
maps to be applied to an interface.
If you do not specify a match command, the route map applies to all
packets.
Command Purpose
Step 4 set ip next-hop ip-address Specify the action to take on the packets that match the criteria. Set next
[...ip-address] hop to which to route the packet (the next hop must be adjacent).
Step 5 exit Return to global configuration mode.
Step 6 interface interface-id Enter interface configuration mode, and specify the interface to
configure.
Step 7 ip policy route-map map-tag Enable PBR on a Layer 3 interface, and identify the route map to use. You
can configure only one route map on an interface. However, you can have
multiple route map entries with different sequence numbers. These
entries are evaluated in sequence number order until the first match. If
there is no match, packets are routed as usual.
Step 8 ip route-cache policy (Optional) Enable fast-switching PBR. You must first enable PBR before
enabling fast-switching PBR.
Step 9 exit Return to global configuration mode.
Step 10 ip local policy route-map map-tag (Optional) Enable local PBR to perform policy-based routing on packets
originating at the switch. This applies to packets generated by the switch
and not to incoming packets.
Note If the IP policy route map contains a deny statement, the
configuration fails.
Step 11 end Return to privileged EXEC mode.
Step 12 show route-map [map-name] (Optional) Display all route maps configured or only the one specified to
verify configuration.
Step 13 show ip policy (Optional) Display policy route maps attached to interfaces.
Step 14 show ip local policy (Optional) Display whether or not local policy routing is enabled and, if
so, the route map being used.
Step 15 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no route-map map-tag global configuration command or the no match or no set route-map
configuration commands to delete an entry. Use the no ip policy route-map map-tag interface
configuration command to disable PBR on an interface. Use the no ip route-cache policy interface
configuration command to disable fast-switching PBR. Use the no ip local policy route-map map-tag
global configuration command to disable policy-based routing on packets originating on the switch.
Note When routes are redistributed between OSPF processes, no OSPF metrics are preserved.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 router {bgp | eigrp | isis | iso-igrp | ospf | Enter router configuration mode.
rip}
Step 3 passive-interface interface-id Suppress sending routing updates through the specified Layer 3
interface.
Step 4 passive-interface default (Optional) Set all interfaces as passive by default.
Step 5 no passive-interface interface type (Optional) Activate only those interfaces that need to have
adjacencies sent.
Step 6 network network-address (Optional) Specify the list of networks for the routing process. The
network-address is an IP address.
Step 7 end Return to privileged EXEC mode.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use a network monitoring privileged EXEC command such as show ip ospf interface to verify the
interfaces that you enabled as passive, or use the show ip interface privileged EXEC command to verify
the interfaces that you enabled as active.
To re-enable the sending of routing updates, use the no passive-interface interface-id router
configuration command. The default keyword sets all interfaces as passive by default. You can then
configure individual interfaces where you want adjacencies by using the no passive-interface router
configuration command. The default keyword is useful in Internet service provider and large enterprise
networks where many of the distribution routers have more than 200 interfaces.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 router {bgp | eigrp | isis | iso-igrp | ospf | rip} Enter router configuration mode.
Step 3 distribute-list {access-list-number | Permit or deny routes from being advertised in routing
access-list-name} out [interface-name | routing updates, depending upon the action listed in the access list.
process | autonomous-system-number]
Step 4 distribute-list {access-list-number | Suppress processing in routes listed in updates.
access-list-name} in [type-number]
Step 5 end Return to privileged EXEC mode.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no distribute-list in router configuration command to change or cancel a filter. To cancel
suppression of network advertisements in updates, use the no distribute-list out router configuration
command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 router {bgp | eigrp | isis | iso-igrp | ospf | rip} Enter router configuration mode.
Step 3 distance weight {ip-address {ip-address mask}} Define an administrative distance.
[ip access list] weight—The administrative distance as an integer from
10 to 255. Used alone, weight specifies a default
administrative distance that is used when no other
specification exists for a routing information source.
Routes with a distance of 255 are not installed in the
routing table.
(Optional) ip access list—An IP standard or extended
access list to be applied to incoming routing updates.
Step 4 end Return to privileged EXEC mode.
Step 5 show ip protocols Display the default administrative distance for a
specified routing process.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 key chain name-of-chain Identify a key chain, and enter key chain configuration
mode.
Step 3 key number Identify the key number. The range is 0 to 2147483647.
Step 4 key-string text Identify the key string. The string can contain from 1 to
80 uppercase and lowercase alphanumeric characters,
but the first character cannot be a number.
Step 5 accept-lifetime start-time {infinite | end-time | duration (Optional) Specify the time period during which the key
seconds} can be received.
The start-time and end-time syntax can be either
hh:mm:ss Month date year or hh:mm:ss date Month
year. The default is forever with the default start-time
and the earliest acceptable date as January 1, 1993. The
default end-time and duration is infinite.
Step 6 send-lifetime start-time {infinite | end-time | duration (Optional) Specify the time period during which the key
seconds} can be sent.
The start-time and end-time syntax can be either
hh:mm:ss Month date year or hh:mm:ss date Month
year. The default is forever with the default start-time
and the earliest acceptable date as January 1, 1993. The
default end-time and duration is infinite.
Step 7 end Return to privileged EXEC mode.
Step 8 show key chain Display authentication key information.
Step 9 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove the key chain, use the no key chain name-of-chain global configuration command.
Command Purpose
clear ip route {network [mask | *]} Clear one or more routes from the IP routing table.
show ip protocols Display the parameters and state of the active routing protocol
process.
show ip route [address [mask] [longer-prefixes]] | Display the current state of the routing table.
[protocol [process-id]]
show ip route summary Display the current state of the routing table in summary form.
show ip route supernets-only Display supernets.
show ip cache Display the routing table used to switch IP traffic.
show route-map [map-name] Display all route maps configured or only the one specified.
This chapter describes how to configure IPv6 unicast routing on the Catalyst 3750 Metro switch. Cisco
IOS Release 12.2(58)SE adds support for IPv6 unicast routing in VPN routing and forwarding (VRF)
and VRF-aware IPv6 DHCP server /client.
For information about configuring IPv6 Multicast Listener Discovery (MLD) snooping, see Chapter 38,
“Configuring IPv6 MLD Snooping.” For information on configuring IPv6 access control lists (ACLs),
see Chapter 39, “Configuring IPv6 ACLs.” For information about configuring IPv4 unicast routing, see
Chapter 36, “Configuring IP Unicast Routing.”
To enable IPv6 routing, you must configure the switch to use the a dual IPv4 and IPv6 switch database
management (SDM) template. To configure IPv6 VRF-aware routing, you must use the
dual-ipv4-and-ipv6 routing template or the dual-ipv4-and-ipv6 default template. The
dual-ipv4-and-ipv6 vlan template does not support VRF-aware routing. See the “Dual IPv4 and IPv6
Protocol Stacks” section on page 37-5.
This chapter consists of these sections:
• “Understanding IPv6” section on page 37-1
• “Configuring IPv6” section on page 37-10
• “Displaying IPv6” section on page 37-29
Understanding IPv6
IPv4 users can move to IPv6 and receive services such as end-to-end security, quality of service (QoS),
and globally unique addresses. The IPv6 address space reduces the need for private addresses and
Network Address Translation (NAT) processing by border routers at network edges.
For information about IPv6 and other features in this chapter, see these documents.
• For complete syntax and usage information for the commands used in this chapter, see the Cisco IOS
IPv6 Command Reference:
http://www.cisco.com/en/US/docs/ios/ipv6/command/reference/ipv6_book.html
• For all IPv6 configuration information, see the Cisco IOS IPv6 Configuration Guide, Release 12.4T
http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/12_4t/ipv6_12_4t_book.html
• You can also use the Search field to locate the Cisco IOS software documentation for a specific
topic. For example, if you want information about static routes, you can enter Implementing Static
Routes for IPv6 in the search field to get this document about static routes:
http://www.cisco.com/en/US/docs/ios-xml/ios/ipv6/configuration/12-4t/ip6-stat-routes.html
IPv6 Addresses
The switch supports only IPv6 unicast addresses. It does not support site-local unicast addresses, anycast
addresses, or multicast addresses.
The IPv6 128-bit addresses are represented as a series of eight 16-bit hexadecimal fields separated by
colons in the format: n:n:n:n:n:n:n:n. This is an example of an IPv6 address:
2031:0000:130F:0000:0000:09C0:080F:130B
For easier implementation, leading zeros in each field are optional. This is the same address without
leading zeros:
2031:0:130F:0:0:9C0:80F:130B
You can also use two colons (::) to represent successive hexadecimal fields of zeros, but you can use this
short version only once in each address:
2031:0:130F::09C0:080F:130B
For more information about IPv6 address formats, address types, and the IPv6 packet header, see the
“Implementing IPv6 Addressing and Basic Connectivity” chapter of Cisco IOS IPv6 Configuration
Guide on Cisco.com.
In the “Implementing Addressing and Basic Connectivity” chapter, these sections apply to the switch:
• IPv6 Address Formats
• IPv6 Address Type: Unicast
• IPv6 Address Output Display
• Simplified IPv6 Packet Header
ICMPv6
The Internet Control Message Protocol (ICMP) in IPv6 generates error messages, such as ICMP
destination unreachable messages, to report errors during processing and other diagnostic functions. In
IPv6, ICMP packets are also used in the neighbor discovery protocol and path MTU discovery.
Neighbor Discovery
The switch supports NDP for IPv6, a protocol running on top of ICMPv6, and static neighbor entries for
IPv6 stations that do not support NDP. The IPv6 neighbor discovery process uses ICMP messages and
solicited-node multicast addresses to determine the link-layer address of a neighbor on the same network
(local link), to verify the reachability of the neighbor, and to keep track of neighboring routers.
The switch supports ICMPv6 redirect for routes with mask lengths less than 64 bits. ICMP redirect is
not supported for host routes or for summarized routes with mask lengths greater than 64 bits.
Neighbor discovery throttling ensures that the switch CPU is not unnecessarily burdened while it is in
the process of obtaining the next hop forwarding information to route an IPv6 packet. The switch drops
any additional IPv6 packets whose next hop is the same neighbor that the switch is actively trying to
resolve. This drop avoids further load on the CPU.
For more information about autoconfiguration and duplicate address detection, see the “Implementing
IPv6 Addressing and Basic Connectivity” chapter of Cisco IOS IPv6 Configuration Guide on Cisco.com.
IPv6 Applications
The switch has IPv6 support for these applications:
• Ping, traceroute, Telnet, and TFTP
• Secure Shell (SSH) over an IPv6 transport
• HTTP server access over IPv6 transport
• DNS resolver for AAAA over IPv4 transport
• Cisco Discovery Protocol (CDP) support for IPv6 addresses
For more information about managing these applications, see the “Managing Cisco IOS Applications
over IPv6” chapter and the “Implementing IPv6 Addressing and Basic Connectivity” chapter in the
Cisco IOS IPv6 Configuration Guide on Cisco.com.
IPv4
10.1.1.1
122379
IPv6
3ffe:yyyy::1
Use the dual IPv4 and IPv6 SDM template to enable IPv6 routing. For more information about the dual
IPv4 and IPv6 SDM template, see Chapter 6, “Configuring SDM Templates.”
The dual IPv4 and IPv6 templates allow the switch to be used in dual stack environments.
• If you try to configure IPv6 without first selecting a dual IPv4 and IPv6 template, a warning message
appears.
• In IPv4-only environments, the switch routes IPv4 packets and applies IPv4 QoS and ACLs in
hardware. IPv6 packets are not supported.
• In dual IPv4 and IPv6 environments, the switch routes both IPv4 and IPv6 packets and applies IPv4
QoS in hardware.
• Full IPv6 QoS is not supported.
• If you do not plan to use IPv6, do not use the dual stack template because this template results in
less TCAM capacity for each resource.
For more information about IPv4 and IPv6 protocol stacks, see the “Implementing IPv6 Addressing and
Basic Connectivity” chapter of Cisco IOS IPv6 Configuration Guide on Cisco.com.
For support over IPv6, SNMP modifies the existing IP transport mapping to simultaneously support IPv4
and IPv6. These SNMP actions support IPv6 transport management:
• Opens User Datagram Protocol (UDP) SNMP socket with default settings
• Provides a new transport mechanism called SR_IPV6_TRANSPORT
• Sends SNMP notifications over IPv6 transport
• Supports SNMP-named access lists for IPv6 transport
• Supports SNMP proxy forwarding using IPv6 transport
• Verifies SNMP Manager feature works with IPv6 transport
For information on SNMP over IPv6, including configuration procedures, see the “Managing Cisco IOS
Applications over IPv6” chapter in the Cisco IOS IPv6 Configuration Guide on Cisco.com.
For information about syslog over IPv6, including configuration procedures, see the “Implementing IPv6
Addressing and Basic Connectivity” chapter in the Cisco IOS IPv6 Configuration Guide on Cisco.com.
• Up to 26 different VRFs. However, the total number of VRF routes supported might be less,
depending on the number of interfaces (SVIs or routed ports) per VRF.
The switch does not support these VFR-aware IPv6 protocols: iBGP, OSPFv3, ISIS, EIGRP, or RIP.
To support IPv6 VRF-Lite, the switch must be running either the IPv4-and-IPv6 default SDM template
or the IPv4-and-IPv6 routing template. For IPv6 VRF-Lite, the switch supports approximately 500
routes with the IPv4-and-IPv6 default template and 1800 routes with the IPv4-and-IPv6 routing
template. Routes that do not fit into the routing table are put in a retry queue. Enter the show platform
ipv6 unicast retry route privileged EXEC command to see any routes in the retry queue.
The IPv4 Multi-VRF-Lite commands apply only to IPv4 traffic. The IPv6 VRF-Lite commands work
with both IPv6 and IPv4 VRF. You can use the same VRF name for IPv4 and IPv6 traffic. If you
anticipate the need to add IPv6 traffic to your existing network, you can migrate your IPv4 VRFs to allow
IPv6traffic by using the vrf upgrade-cli multi-af-mode {common-policies | non-common policies}
[vrf vrf-name] global configuration command and configuring IPv6 address families.
Note Although you can continue to configure IPv4 VRFs by using the IPv4-specific commands described in
the “Configuring Multi-VRF CE” section on page 36-82, we recommend that you use the IPv6
commands to facilitate future compatibility.
See the “Configuring Multi-Protocol VRF for IPv6” section on page 37-26 for the configuring process.
Note The switch supports IPv6 VRF-Lite (Multi-VRF-CE), which is IPv6 VPN in a VRF environment
with limited VRF functionality.
Note The switch does not support IPv6-related features with ES-port specific features, such as MPLS,
EoMPLS, or QinQ trust.
Limitations
Because IPv6 is implemented in switch hardware, some limitations occur due to the IPv6 compressed
addresses in the TCAM. These hardware limitations result in some loss of functionality and limits some
features.
• ICMPv6 redirect functionality is not supported for IPv6 host routes (routes used to reach a specific
host) or for IPv6 routes with masks greater than 64 bits. The switch cannot redirect hosts to a better
first-hop router for a specific destination that is reachable through a host route or through a route
with masks greater than 64 bits.
• Load balancing using equal cost and unequal cost routes is not supported for IPv6 host routes or for
IPv6 routes with a mask greater than 64 bits.
• The switch cannot forward SNAP-encapsulated IPv6 packets.
Note There is a similar limitation for IPv4 SNAP-encapsulated packets, but the packets are
dropped at the switch and are not forwarded.
• The switch routes IPv6-to-IPv4 and IPv4-to-IPv6 packets in hardware, but the switch cannot be an
IPv6-to-IPv4 or IPv4-to-IPv6 tunnel endpoint.
• Bridged IPv6 packets with hop-by-hop extension headers are forwarded in software. In IPv4, these
packets are routed in software, but bridged in hardware.
• In addition to the normal SPAN and RSPAN limitations defined in the software configuration guide,
these limitations are specific to IPv6 packets:
– When you send RSPAN IPv6-routed packets, the source MAC address in the SPAN output
packet can be incorrect.
– When you send RSPAN IPv6-routed packets, the destination MAC address can be incorrect.
Normal traffic is not affected.
• The switch cannot apply QoS classification or policy-based routing on source-routed IPv6 packets
in hardware.
• The switch cannot generate ICMPv6 Packet Too Big messages for multicast packets.
• When using IPv6 VRF Lite, the switch supports approximately 500 routes with the IPv4-and-IPv6
default template and 1800 routes with the IPv4-and-IPv6 routing template. Routes that do not fit into
the routing table are put in a retry queue.
• IPv6 unicast routing and IPv6 VRF Lite share the same allocation region of TCAM for IPv6 route
entries. If IPv6 routing protocols in the IPv6 global table are enabled before IPv6 VRF-Lite, the
routing protocols can install so many route entries that IPv6 VRF Lite default routes no longer fit in
the TCAM. To ensure that IPv6 VRF Lite functions correctly, you should enter at least one IPv6 vrf
definition global configuration command with an IPv6 address family before configuring the IPv6
routing protocols and before configuring any IPv6 addresses on any interfaces.
Configuring IPv6
• Default IPv6 Configuration, page 37-11
• Configuring IPv6 Addressing and Enabling IPv6 Routing, page 37-11
• Configuring Default Router Preference, page 37-14
To forward IPv6 traffic on an interface, you must configure a global IPv6 address on that interface.
Configuring an IPv6 address on an interface automatically configures a link-local address and activates
IPv6 for the interface. The configured interface automatically joins these required multicast groups for
that link:
• solicited-node multicast group FF02:0:0:0:0:1:ff00::/104 for each unicast address assigned to the
interface (this address is used in the neighbor discovery process.)
• all-nodes link-local multicast group FF02::1
• all-routers link-local multicast group FF02::2
For more information about configuring IPv6 routing, see the “Implementing Addressing and Basic
Connectivity for IPv6” chapter in the Cisco IOS IPv6 Configuration Guide on Cisco.com.
Beginning in privileged EXEC mode, follow these steps to assign an IPv6 address to a Layer 3 interface
and enable IPv6 routing:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 sdm prefer dual-ipv4-and-ipv6 {default | Select an SDM template that supports IPv4 and IPv6.
routing | vlan}
• default—Set the switch to the default template to balance
system resources.
• routing—Set the switch to the routing template to support
IPv4 and IPv6 routing, including IPv4 policy-based routing.
• vlan—Maximize VLAN configuration on the switch with
no routing supported in hardware.
Step 3 end Return to privileged EXEC mode.
Step 4 reload Reload the operating system.
Step 5 configure terminal Enter global configuration mode after the switch reloads.
Step 6 interface interface-id Enter interface configuration mode, and specify the Layer 3
interface to configure. The interface can be a physical interface,
a switch virtual interface (SVI), or a Layer 3 EtherChannel.
Step 7 no switchport Remove the interface from Layer 2 configuration mode (if it is a
physical interface).
Command Purpose
Step 8 ipv6 address ipv6-prefix/prefix length eui-64 Specify a global IPv6 address with an extended unique identifier
(EUI) in the low-order 64 bits of the IPv6 address. Specify only
the network prefix; the last 64 bits are automatically computed
from the switch MAC address. This enables IPv6 processing on
or the interface.
ipv6 address ipv6-address/prefix length Manually configure an IPv6 address on the interface.
or
ipv6 address ipv6-address link-local Specify a link-local address on the interface to be used instead
of the link-local address that is automatically configured when
or IPv6 is enabled on the interface. This command enables IPv6
processing on the interface.
To remove an IPv6 address from an interface, use the no ipv6 address ipv6-prefix/prefix length eui-64
or no ipv6 address ipv6-address link-local interface configuration command. To remove all manually
configured IPv6 addresses from an interface, use the no ipv6 address interface configuration command
without arguments. To disable IPv6 processing on an interface that has not been explicitly configured
with an IPv6 address, use the no ipv6 enable interface configuration command. To globally disable IPv6
routing, use the no ipv6 unicast-routing global configuration command.
This example shows how to enable IPv6 with both a link-local address and a global address based on the
IPv6 prefix 2001:0DB8:c18:1::/64. The EUI-64 interface ID is used in the low-order 64 bits of both
addresses. Output from the show ipv6 interface EXEC command shows how the interface ID
(20B:46FF:FE2F:D940) is appended to the link-local prefix FE80::/64 of the interface.
Switch(config)# sdm prefer dual-ipv4-and-ipv6 default
Switch(config)# ipv6 unicast-routing
Switch(config)# interface gigabitethernet1/1/1
Switch(config-if)# no switchport
Switch(config-if)# ipv6 address 2001:0DB8:c18:1::/64 eui 64
Switch(config-if)# end
Switch# show ipv6 interface gigabitethernet1/1/1
GigabitEthernet1/1/1 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::20B:46FF:FE2F:D940
Global unicast address(es):
2001:0DB8:c18:1:20B:46FF:FE2F:D940, subnet is 2001:0DB8:c18:1::/64 [EUI]
Joined group address(es):
FF02::1
FF02::2
FF02::1:FF2F:D940
MTU is 1500 bytes
ICMP error messages limited to one every 100 milliseconds
ICMP redirects are enabled
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and enter the Layer 3 interface on
which you want to specify the DRP.
Step 3 ipv6 nd router-preference {high | Specify a DRP for the router on the switch interface.
medium | low}
Step 4 end Return to privileged EXEC mode.
Step 5 show ipv6 interface Verify the configuration.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no ipv6 nd router-preference interface configuration command to disable an IPv6 DRP.
This example shows how to configure a DRP of high for the router on an interface.
Switch# configure terminal
Switch(config)# interface gigabitethernet1/1/1
Switch(config-if)# ipv6 nd router-preference high
Switch(config-if)# end
For more information about configuring DRP for IPv6, see the “Implementing IPv6 Addresses and Basic
Connectivity” chapter in the Cisco IOS IPv6 Configuration Guide on Cisco.com.
Beginning in privileged EXEC mode, follow these steps to configure a Layer 3 interface to support both
IPv4 and IPv6 and to enable IPv6 routing.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 sdm prefer dual-ipv4-and-ipv6 {default | Select an SDM template that supports IPv4 and IPv6.
routing | vlan}
• default—Set the switch to the default template to balance
system resources.
• routing—Set the switch to the routing template to support
IPv4 and IPv6 routing, including IPv4 policy-based routing.
• vlan—Maximize VLAN configuration on the switch with
no routing supported in hardware.
Step 3 end Return to privileged EXEC mode.
Step 4 reload Reload the operating system.
Step 5 configure terminal Enter global configuration mode.
Step 6 ip routing Enable routing on the switch.
Step 7 ipv6 unicast-routing Enable forwarding of IPv6 data packets on the switch.
Step 8 interface interface-id Enter interface configuration mode, and specify the Layer 3
interface to configure.
Step 9 no switchport Remove the interface from Layer 2 configuration mode (if it is a
physical interface).
Step 10 ip address ip-address mask [secondary] Specify a primary or secondary IPv4 address for the interface.
Step 11 ipv6 address ipv6-prefix/prefix length eui-64 Specify a global IPv6 address with an extended unique identifier
(EUI) in the low-order 64 bits of the IPv6 address. Specify only
the network prefix; the last 64 bits are automatically computed
from the switch MAC address. This enables IPv6 processing on
or the interface.
ipv6 address ipv6-address/prefix length Manually configure an IPv6 address on the interface.
or
ipv6 address ipv6-address link-local Specify a link-local address on the interface to be used instead
of the link-local address that is automatically configured when
or IPv6 is enabled on the interface. This command enables IPv6
processing on the interface.
To disable IPv4 routing, use the no ip routing global configuration command. To disable IPv6 routing,
use the no ipv6 unicast-routing global configuration command. To remove an IPv4 address from an
interface, use the no ip address ip-address mask interface configuration command. To remove an IPv6
address from an interface, use the no ipv6 address ipv6-prefix/prefix length eui-64 or no ipv6 address
ipv6-address link-local interface configuration command. To remove all manually configured IPv6
addresses from an interface, use the no ipv6 address interface configuration command without
arguments. To disable IPv6 processing on an interface that has not been explicitly configured with an
IPv6 address, use the no ipv6 enable interface configuration command.
This example shows how to enable IPv4 and IPv6 routing on an interface.
Switch(config)# sdm prefer dual-ipv4-and-ipv6 default
Switch(config)# ip routing
Switch(config)# ipv6 unicast-routing
Switch(config)# interface gigabitethernet1/1/1
Switch(config-if)# no switchport
Switch(config-if)# ip address 192.168.99.1 244.244.244.0
Switch(config-if)# ipv6 address 2001:0DB8:c18:1::/64 eui 64
Switch(config-if)# end
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ipv6 dhcp pool poolname Enter DHCP pool configuration mode, and define the name
for the IPv6 DHCP pool. The pool name can be a symbolic
string (such as Engineering) or an integer (such as 0).
Step 3 address prefix IPv6-prefix lifetime {t1 t1 | infinite} (Optional) Specify an address prefix for address assignment.
This address must be in hexadecimal, using 16-bit values
between colons.
lifetime t1 t1—Specify a time interval (in seconds) that an
IPv6 address prefix remains in the valid state. The range is 5
to 4294967295 seconds. Specify infinite for no time interval.
Step 4 link-address IPv6-prefix (Optional) Specify a link-address IPv6 prefix.
When an address on the incoming interface or a link-address
in the packet matches the specified IPv6 prefix, the server
uses the configuration information pool.
This address must be in hexadecimal, using 16-bit values
between colons.
Step 5 vendor-specific vendor-id (Optional) Enter vendor-specific configuration mode and
enter a vendor-specific identification number. This number is
the vendor IANA Private Enterprise Number. The range is 1
to 4294967295.
Step 6 suboption number {address IPv6-address | ascii (Optional) Enter a vendor-specific suboption number. The
ASCII-string | hex hex-string} range is 1 to 65535. Enter an IPv6 address, ASCII text, or a
hex string as defined by the suboption parameters.
Step 7 exit Return to DHCP pool configuration mode.
Step 8 exit Return to global configuration mode.
Step 9 interface interface-id Enter interface configuration mode, and specify the interface
to configure.
Command Purpose
Step 10 ipv6 dhcp server [poolname | automatic] Enable DHCPv6 server function on an interface.
[rapid-commit] [preference value] [allow-hint]
• poolname—(Optional) User-defined name for the IPv6
DHCP pool. The pool name can be a symbolic string
(such as Engineering) or an integer (such as 0).
• automatic—(Optional) Enables the system to
automatically determine which pool to use when
allocating addresses for a client.
• rapid-commit—(Optional) Allow two-message
exchange method.
• preference value—(Optional) The preference value
carried in the preference option in the advertise message
sent by the server. The range is from 0 to 255. The
preference value default is 0.
• allow-hint—(Optional) Specifies whether the server
should consider client suggestions in the SOLICIT
message. By default, the server ignores client hints.
Step 11 end Return to privileged EXEC mode.
Step 12 show ipv6 dhcp pool Verify DHCPv6 pool configuration.
or
show ipv6 dhcp interface Verify that the DHCPv6 server function is enabled on an
interface.
Step 13 copy running-config startup-config (Optional) Save your entries in the configuration file.
To delete a DHCPv6 pool, use the no ipv6 dhcp pool poolname global configuration command. Use the
no form of the DHCP pool configuration mode commands to change the DHCPv6 pool characteristics.
To disable the DHCPv6 server function on an interface, use the no ipv6 dhcp server interface
configuration command.
This example shows how to configure a pool called engineering with an IPv6 address prefix:
Switch# configure terminal
Switch(config)# ipv6 dhcp pool engineering
Switch(config-dhcpv6)#address prefix 2001:1000::0/64
Switch(config-dhcpv6)# end
This example shows how to configure a pool called testgroup with three link-addresses and an IPv6
address prefix:
Switch# configure terminal
Switch(config)# ipv6 dhcp pool testgroup
Switch(config-dhcpv6)# link-address 2001:1001::0/64
Switch(config-dhcpv6)# link-address 2001:1002::0/64
Switch(config-dhcpv6)# link-address 2001:2000::0/48
Switch(config-dhcpv6)# address prefix 2001:1003::0/64
Switch(config-dhcpv6)# end
This example shows how to configure a pool called 350 with vendor-specific options:
Switch# configure terminal
Switch(config)# ipv6 dhcp pool 350
Switch(config-dhcpv6)# address prefix 2001:1005::0/48
Switch(config-dhcpv6)# vendor-specific 9
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and specify the interface
to configure.
Step 3 ipv6 address dhcp [rapid-commit] Enable the interface to acquire an IPv6 address from the
DHCPv6 server.
rapid-commit—(Optional) Allow two-message exchange
method for address assignment.
Step 4 ipv6 dhcp client request [vendor-specific] (Optional) Enable the interface to request the vendor-specific
option.
Step 5 end Return to privileged EXEC mode.
Step 6 show ipv6 dhcp interface Verify that the DHCPv6 client is enabled on an interface.
To disable the DHCPv6 client function, use the no ipv6 address dhcp interface configuration command.
To remove the DHCPv6 client request, use the no ipv6 address dhcp client request interface
configuration command.
This example shows how to acquire an IPv6 address and to enable the rapid-commit option:
Switch(config)# interface gigabitethernet 1/1/1
Switch(config-if)# ipv6 address dhcp rapid-commit
• When you configure this feature, you should perform VRF configuration before you configure
DHCPv6 client, server, and relay.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ipv6 icmp error-interval interval [bucketsize] Configure the interval and bucket size for IPv6 ICMP error
messages:
• interval—The interval (in milliseconds) between tokens
being added to the bucket. The range is from 0 to
2147483647 milliseconds.
• bucketsize—(Optional) The maximum number of tokens
stored in the bucket. The range is from 1 to 200.
Step 3 end Return to privileged EXEC mode.
Step 4 show ipv6 interface [interface-id] Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default configuration, use the no ipv6 icmp error-interval global configuration
command.
This example shows how to configure an IPv6 ICMP error message interval of 50 milliseconds and a
bucket size of 20 tokens.
Switch(config)#ipv6 icmp error-interval 50 20
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ipv6 route ipv6-prefix/prefix length Configure a static IPv6 route.
{ipv6-address | interface-id
• ipv6-prefix—The IPv6 network that is the destination of the static
[ipv6-address]} [administrative
route. It can also be a hostname when static host routes are configured.
distance]
• /prefix length—The length of the IPv6 prefix. A decimal value that
shows how many of the high-order contiguous bits of the address
comprise the prefix (the network portion of the address). A slash mark
must precede the decimal value.
• ipv6-address—The IPv6 address of the next hop that can be used to
reach the specified network. The IPv6 address of the next hop need not
be directly connected; recursion is done to find the IPv6 address of the
directly connected next hop. The address must be specified in
hexadecimal using 16-bit values between colons.
• interface-id—Specify direct static routes from point-to-point and
broadcast interfaces. With point-to-point interfaces, there is no need to
specify the IPv6 address of the next hop. With broadcast interfaces,
you should always specify the IPv6 address of the next hop, or ensure
that the specified prefix is assigned to the link, specifying a link-local
address as the next hop. You can optionally specify the IPv6 address
of the next hop to which packets are sent.
Note You must specify an interface-id when using a link-local address
as the next hop (the link-local next hop must also be an adjacent
router).
Command Purpose
Step 4 show ipv6 static [ipv6-address | Verify your entries by displaying the contents of the IPv6 routing table.
ipv6-prefix/prefix length] [interface
• interface interface-id—(Optional) Display only those static routes
interface-id] [recursive] [detail]
with the specified interface as an egress interface.
• recursive—(Optional) Display only recursive static routes. The
or recursive keyword is mutually exclusive with the interface keyword,
but it can be used with or without the IPv6 prefix included in the
command syntax.
show ipv6 route static [updated]
• detail—(Optional) Display this additional information:
– For valid recursive routes, the output path set, and maximum
resolution depth.
– For invalid routes, the reason why the route is not valid.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove a configured static route, use the no ipv6 route ipv6-prefix/prefix length {ipv6-address |
interface-id [ipv6-address]} [administrative distance] global configuration command.
This example shows how to configure a floating static route with an administrative distance of 130 to an
interface:
Switch(config)# ipv6 route 2001:0DB8::/32 gigabitethernet1/1/1 130
For more information about configuring static IPv6 routing, see the “Implementing Static Routes for
IPv6” chapter in the Cisco IOS IPv6 Configuration Guide on Cisco.com.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ipv6 router rip name Configure an IPv6 RIP routing process, and enter router
configuration mode for the process.
Step 3 maximum-paths number-paths (Optional) Define the maximum number of equal-cost routes
that IPv6 RIP can support. The range is from 1 to 64, and the
default is 4 routes.
Step 4 exit Return to global configuration mode.
Step 5 interface interface-id Enter interface configuration mode, and specify the Layer 3
interface to configure.
Step 6 ipv6 rip name enable Enable the specified IPv6 RIP routing process on the interface.
Command Purpose
Step 7 ipv6 rip name default-information {only | (Optional) Originate the IPv6 default route (::/0) into the RIP
originate} routing process updates sent from the specified interface.
Note To avoid routing loops after the IPv6 default route (::/0)
is originated from any interface, the routing process
ignores all default routes received on any interface.
To disable a RIP routing process, use the no ipv6 router rip name global configuration command. To
disable the RIP routing process for an interface, use the no ipv6 rip name interface configuration
command.
This example shows how to enable the RIP routing process cisco with a maximum of eight equal-cost
routes and to enable it on an interface:
Switch(config)# ipv6 router rip cisco
Switch(config-router)# maximum-paths 8
Switch(config)# exit
Switch(config)# interface gigabitthernet1/1/1
Switch(config-if)# ipv6 rip cisco enable
For more information about configuring RIP routing for IPv6, see the “Implementing RIP for IPv6”
chapter in the Cisco IOS IPv6 Configuration Guide on Cisco.com
Beginning in privileged EXEC mode, follow these required and optional steps to configure IPv6 OSPF:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ipv6 router ospf process-id Enable OSPF router configuration mode for the process. The
process ID is the number administratively assigned when
enabling the OSPF for IPv6 routing process. It is locally
assigned and can be a positive integer from 1 to 65535.
Step 3 area area-id range {ipv6-prefix/prefix length} (Optional) Consolidate and summarize routes at an area
[advertise | not-advertise] [cost cost] boundary.
• area-id—Identifier of the area about which routes are to be
summarized. It can be specified as either a decimal value or
as an IPv6 prefix.
• ipv6-prefix/prefix length—The destination IPv6 network and
a decimal value that shows how many of the high-order
contiguous bits of the address comprise the prefix (the
network portion of the address). A slash mark (/) must
precede the decimal value.
• advertise—(Optional) Set the address range status to
advertise and to generate a Type 3 summary link-state
advertisement (LSA).
• not-advertise—(Optional) Set the address range status to
DoNotAdvertise. The Type 3 summary LSA is suppressed,
and component networks remain hidden from other
networks.
• cost cost—(Optional) Metric or cost for this summary route,
which is used during OSPF SPF calculation to determine the
shortest paths to the destination. The value can be 0 to
16777215.
Step 4 maximum paths number-paths (Optional) Define the maximum number of equal-cost routes to
the same destination that IPv6 OSPF should enter in the routing
table. The range is from 1 to 64, and the default is 16.
Step 5 exit Return to global configuration mode.
Step 6 interface interface-id Enter interface configuration mode, and specify the Layer 3
interface to configure.
Step 7 ipv6 ospf process-id area area-id [instance Enable OSPF for IPv6 on the interface.
instance-id] instance instance-id—(Optional) Instance identifier.
Step 8 end Return to privileged EXEC mode.
Step 9 show ipv6 ospf [process-id] [area-id] interface Display information about OSPF interfaces.
[interface-id]
or
show ipv6 ospf [process-id] [area-id] Display general information about OSPF routing processes.
Step 10 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable an OSPF routing process, use the no ipv6 router ospf process-id global configuration
command. To disable the OSPF routing process for an interface, use the no ipv6 ospf process-id area
area-id interface configuration command.
For more information about configuring OSPF routing for IPv6, see the “Implementing OSPF for IPv6”
chapter in the Cisco IOS IPv6 Configuration Guide on Cisco.com.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 router bgp as-number Configure a BGP routing process, and enter BGP router
configuration mode for the autonomous system number.
Step 3 no bgp default ipv4-unicast Disable the IPv4 unicast address family for the BGP routing
process specified in the previous step.
Routing information for the IPv4 unicast address family is
advertised by default for each BGP routing session unless you
enter this command before configuring the neighbor remote-as
command.
Step 4 bgp router-id ip-address (Optional) Configure a fixed 32-bit router ID as the identifier of
the local router running BGP. By default, the router ID is the
IPv4 address of a router loopback interface. On a router enabled
only for IPv6 (no IPv4 address), you must manually configure
the BGP router ID.
Note Configuring a router ID by using this command resets all
active BGP peering sessions.
Command Purpose
Step 5 neighbor {ip-address | ipv6-address[%] Add the IPv6 address of the neighbor in the specified
interface-type interface-number | autonomous system to the IPv6 multiprotocol BGP neighbor
peer-group-name} remote-as as-number table of the local router.
Note The ipv6-address must be in hexadecimal, using 16-bit
values between colons.
Step 6 address-family ipv6 Specify the IPv6 address family and enter address family
configuration mode
Step 7 neighbor {ip-address | peer-group-name | Enable the neighbor to exchange prefixes for the IPv6 address
ipv6-address} activate family with the local router.
Step 8 end Return to privileged EXEC mode.
Step 9 show bgp ipv6 Display information about IPv6 BGP configuration.
Step 10 copy running-config startup-config (Optional) Save your entries in the configuration file.
For more configuration procedures, see the “Implementing Multiprotocol BGP for IPv6” chapter in the
Cisco IOS IPv6 Configuration Guide on Cisco.com.
http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/12_4/ipv6_12_4_book.html
The switch does not support multicast IPv6 BGP, nonstop forwarding (NSF) for IPv6 BGP, 6PE
multipath (EoMPLS), or IPv6 VRF.
Note Because some IPv6 indirect routes can use more than one TCAM entry, the total number of supported
indirect routes might be less than that shown in the template. If the limit of TCAM entries for IPv6 routes
is exceeded, an error message is generated.
For complete information about the commands in this section, see the Cisco IOS IPv6 Command
Reference at:
http://www.cisco.com/en/US/docs/ios/ipv6/command/reference/ipv6_book.html
The IPv4 Multi-VRF-Lite commands apply only to IPv4 traffic. The IPv6 VRF-Lite commands work
with both IPv6 and IPv4 VRF. You can use the same VRF name for IPv4 and IPv6 traffic. If you
anticipate the need to add IPv6 traffic to your existing network, you can migrate your IPv4 VRFs to allow
IPv6traffic by using the vrf upgrade-cli multi-af-mode {common-policies | non-common policies}
[vrf vrf-name] global configuration command and configuring IPv6 address families.
Note Although you can continue to use the IPv4-specific commands to configure IPv4 VRFs, using the IPv6
commands allows you to configure both IPv4 and IPv6 VRFs. We recommend that you use the IPv6
commands to facilitate future compatibility.
Beginning in privileged EXEC mode, follow these steps to configure one or more IPv6 VRFs.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 sdm prefer dual-ipv4-and-ipv6 {default Select an SDM template that supports IPv4 and IPv6 routing.
| routing}
• default—Set the switch to the default template to balance system
resources. This template supports approximately 500 IPv6 VRF
routes.
• routing—Set the switch to the routing template to support IPv4
and IPv6 routing, including IPv4 policy-based routing. This
template supports approximately 1800 IPv6 VRF routes.
Step 3 end Return to privileged EXEC mode.
Step 4 reload Reload the operating system.
Command Purpose
Step 12 exit Exit IPv4 address family configuration mode
Step 13 exit Exit VRF configuration mode
Step 14 interface interface-id Enter interface configuration mode and specify the Layer 3 interface to
be associated with the VRF. The interface can be a routed port or SVI.
Step 15 vrf forwarding vrf-name Associate the VRF with the Layer 3 interface.
Step 16 end Return to privileged EXEC mode.
Step 17 show vrf Verify the configuration. Display information about the configured
VRFs.
Step 18 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no vrf definition vrf-name global configuration command to delete a VRF and to remove all
interfaces from it. Use the no vrf forwarding interface configuration command to remove an interface
from the VRF.
This example shows the steps required for configuring IPv6 VRF Lite. It requires that the IPv4 and IPv6
default or routing template be configured.
Enable IPv6 VRF Lite:
Switch(config)# ip routing
Switch(config)# ipv6 unicast-routing
Switch(config)# vrf definition abc
Switch(config-vrf)# rd 100:2
Switch(config-vrf)# address-family ipv4
Switch(config-vrf-af)# exit
Switch(config-vrf)# address-family ipv6
Switch(config-vrf-af)# exit
Switch(config-vrf)# exit
Note The last command configures a static route pointing to the customer router.
Verify connectivity:
Switch# ping vrf abc 2000::2
Switch# telnet 2222::2 /vrf abc
Switch# traceroute vrf abc2222::2
Displaying IPv6
For complete syntax and usage information on these commands, see the Cisco IOS command reference
publications.
Command Purpose
show bgp ipv6 Display BGP IPv6 configuration and routing tables.
show ipv6 access-list Display a summary of access lists.
show ipv6 cef Display Cisco Express Forwarding for IPv6.
show ipv6 interface interface-id Display IPv6 interface status and configuration.
show ipv6 mtu Display IPv6 MTU per destination cache.
show ipv6 neighbors Display IPv6 neighbor cache entries.
show ipv6 ospf Display IPv6 OSPF information.
show ipv6 prefix-list Display a list of IPv6 prefix lists.
show ipv6 protocols Display IPv6 routing protocols on the switch.
show ipv6 rip Display IPv6 RIP routing protocol status.
show ipv6 route Display the IPv6 route table entries.
show ipv6 routers Display the local IPv6 routers.
show ipv6 static Display IPv6 static routes.
show ipv6 traffic Display IPv6 traffic statistics.
show vrf Display information about VRF configured on the switch.
Command Purpose
show ipv6 eigrp [as-number] interface Displays information about interfaces configured for EIGRP IPv6.
show ipv6 eigrp [as-number] neighbor Displays the neighbors discovered by EIGRP IPv6.
Command Purpose
show ipv6 eigrp [as-number] traffic Displays the number of EIGRP IPv6 packets sent and received.
show ipv6 eigrp topology [as-number | ipv6-address] Displays EIGRP entries in the IPv6 topology table.
[active | all-links | detail-links | pending | summary |
zero-successors]
Table 37-4 Commands for Displaying IPv4 and IPv6 Address Types
Command Purpose
show ip http server history Display the previous 20 connections to the HTTP server, including the IP
address accessed and the time when the connection was closed.
show ip http server connection Display the current connections to the HTTP server, including the local and
remote IP addresses being accessed.
show ip http client connection Display the configuration values for HTTP client connections to HTTP
servers.
show ip http client history Display a list of the last 20 requests made by the HTTP client to the server.
This is an example of the output from the show ipv6 interface privileged EXEC command:
Switch# show ipv6 interface
Vlan1 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::20B:46FF:FE2F:D940
Global unicast address(es):
3FFE:C000:0:1:20B:46FF:FE2F:D940, subnet is 3FFE:C000:0:1::/64 [EUI]
Joined group address(es):
FF02::1
FF02::2
FF02::1:FF2F:D940
MTU is 1500 bytes
ICMP error messages limited to one every 100 milliseconds
ICMP redirects are enabled
ND DAD is enabled, number of DAD attempts: 1
ND reachable time is 30000 milliseconds
ND advertised reachable time is 0 milliseconds
ND advertised retransmit interval is 0 milliseconds
ND router advertisements are sent every 200 seconds
ND router advertisements live for 1800 seconds
<output truncated>
This is an example of the output from the show ipv6 cef privileged EXEC command:
Switch# show ipv6 cef
::/0
nexthop 3FFE:C000:0:7::777 Vlan7
3FFE:C000:0:1::/64
attached to Vlan1
3FFE:C000:0:1:20B:46FF:FE2F:D940/128
receive
3FFE:C000:0:7::/64
attached to Vlan7
3FFE:C000:0:7::777/128
attached to Vlan7
3FFE:C000:0:7:20B:46FF:FE2F:D97F/128
receive
3FFE:C000:111:1::/64
attached to FastEthernet1/0/11
3FFE:C000:111:1:20B:46FF:FE2F:D945/128
receive
3FFE:C000:168:1::/64
attached to FastEthernet2/0/43
3FFE:C000:168:1:20B:46FF:FE2F:D94B/128
receive
3FFE:C000:16A:1::/64
attached to Loopback10
3FFE:C000:16A:1:20B:46FF:FE2F:D900/128
receive
<output truncated>
This is an example of the output from the show ipv6 protocols privileged EXEC command:
Switch# show ipv6 protocols
IPv6 Routing Protocol is “connected”
IPv6 Routing Protocol is “static”
IPv6 Routing Protocol is “rip fer”
Interfaces:
Vlan6
GigabitEthernet1/1/1
GigabitEthernet1/1/2
Redistribution:
None
This is an example of the output from the show ipv6 rip privileged EXEC command:
Switch# show ipv6 rip
RIP process "fer", port 521, multicast-group FF02::9, pid 190
Administrative distance is 120. Maximum paths is 16
Updates every 30 seconds, expire after 180
Holddown lasts 0 seconds, garbage collect after 120
Split horizon is on; poison reverse is off
Default routes are not generated
Periodic updates 9040, trigger updates 60
Interfaces:
Vlan6
FastEthernet2/0/4
FastEthernet2/0/11
FastEthernet1/0/12
Redistribution:
None
This is an example of the output from the show ipv6 static privileged EXEC command:
Switch# show ipv6 static
IPv6 Static routes
Code: * - installed in RIB
* ::/0 via nexthop 3FFE:C000:0:7::777, distance 1
This is an example of the output from the show ipv6 neighbor privileged EXEC command:
Switch# show ipv6 neighbors
IPv6 Address Age Link-layer Addr State Interface
3FFE:C000:0:7::777 - 0007.0007.0007 REACH Vl7
3FFE:C101:113:1::33 - 0000.0000.0033 REACH Fa1/0/13
This is an example of the output from the show ipv6 route privileged EXEC command:
Switch# show ipv6 route
IPv6 Routing Table - Default - 1 entries
This is an example of the output from the show ipv6 traffic privileged EXEC command.
Switch# show ipv6 traffic
IPv6 statistics:
Rcvd: 1 total, 1 local destination
0 source-routed, 0 truncated
0 format errors, 0 hop count exceeded
0 bad header, 0 unknown option, 0 bad source
0 unknown protocol, 0 not a router
0 fragments, 0 total reassembled
0 reassembly timeouts, 0 reassembly failures
Sent: 36861 generated, 0 forwarded
0 fragmented into 0 fragments, 0 failed
0 encapsulation failed, 0 no route, 0 too big
0 RPF drops, 0 RPF suppressed drops
Mcast: 1 received, 36861 sent
ICMP statistics:
Rcvd: 1 input, 0 checksum errors, 0 too short
0 unknown info type, 0 unknown error type
unreach: 0 routing, 0 admin, 0 neighbor, 0 address, 0 port
parameter: 0 error, 0 header, 0 option
0 hopcount expired, 0 reassembly timeout,0 too big
0 echo request, 0 echo reply
0 group query, 0 group report, 0 group reduce
1 router solicit, 0 router advert, 0 redirects
0 neighbor solicit, 0 neighbor advert
Sent: 10112 output, 0 rate-limited
unreach: 0 routing, 0 admin, 0 neighbor, 0 address, 0 port
parameter: 0 error, 0 header, 0 option
0 hopcount expired, 0 reassembly timeout,0 too big
0 echo request, 0 echo reply
0 group query, 0 group report, 0 group reduce
0 router solicit, 9944 router advert, 0 redirects
84 neighbor solicit, 84 neighbor advert
UDP statistics:
Rcvd: 0 input, 0 checksum errors, 0 length errors
0 no port, 0 dropped
Sent: 26749 output
TCP statistics:
Rcvd: 0 input, 0 checksum errors
Sent: 0 output, 0 retransmitted
This is an example of the output from the show vrf privileged EXEC command showing IPv4 and IPv6
VRFs:
Switch# show vrf brief
Name Default RD Protocols Interfaces
A 100:1 ipv4
Fa1/0/10
Vl200
ABC 100:2 ipv4,ipv6 Fa1/0/3
B 100:3 ipv4
You can use Multicast Listener Discovery (MLD) snooping on the Catalyst 3750 Metro switch to enable
efficient distribution of IP version 6 (IPv6) multicast data to clients and routers in a switched network.
Note To use IPv6, you must configure the dual IPv4 and IPv6 Switch Database Management (SDM) template
on the switch. You select the template by entering the sdm prefer dual-ipv4-and-ipv6 global
configuration command.
Note For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release or the Cisco IOS documentation referenced in the procedures.
Note The switch does not support MLDv2 enhanced snooping (MESS), which sets up IPv6 source and
destination multicast address-based forwarding.
MLD snooping can be enabled or disabled globally or per VLAN. When MLD snooping is enabled, a
per-VLAN IPv6 multicast MAC address table is constructed in software and a per-VLAN IPv6 multicast
address table is constructed in software and hardware. The switch then performs IPv6 multicast-address
based bridging in hardware.
These sections describe some parameters of IPv6 MLD snooping:
• MLD Messages, page 38-2
• MLD Queries, page 38-2
• Multicast Client Aging Robustness, page 38-3
• Multicast Router Discovery, page 38-3
• MLD Reports, page 38-4
• MLD Done Messages and Immediate-Leave, page 38-4
• Topology Change Notification Processing, page 38-4
MLD Messages
MLDv1 supports three types of messages:
• Listener Queries are the equivalent of IGMPv2 queries and are either General Queries or
Multicast-Address-Specific Queries (MASQs).
• Multicast Listener Reports are the equivalent of IGMPv2 reports.
• Multicast Listener Done messages are the equivalent of IGMPv2 leave messages.
MLDv2 supports MLDv2 queries and reports, as well as MLDv1 Report and Done messages.
Message timers and state transitions resulting from messages being sent or received are the same as those
of IGMPv2 messages. MLD messages that do not have valid link-local IPv6 source addresses are ignored
by MLD routers and switches.
MLD Queries
The switch sends out MLD queries, constructs an IPv6 multicast address database, and generates MLD
group-specific and MLD group-and-source-specific queries in response to MLD Done messages. The
switch also supports report suppression, report proxying, Immediate-Leave functionality, and static IPv6
multicast MAC-address configuration.
When MLD snooping is disabled, all MLD queries are flooded in the ingress VLAN.
When MLD snooping is enabled, received MLD queries are flooded in the ingress VLAN, and a copy of
the query is sent to the CPU for processing. From the received query, MLD snooping builds the IPv6
multicast address database. It detects multicast router ports, maintains timers, sets report response time,
learns the querier IP source address for the VLAN, learns the querier port in the VLAN, and maintains
multicast-address aging.
Note When the IPv6 multicast router is a Catalyst 6500 switch and you are using extended VLANs (in the
range 1006 to 4094), IPv6 MLD snooping must be enabled on the extended VLAN on the Catalyst 6500
switch in order for this switch to receive queries on the VLAN. For normal-range VLANs (1 to 1005),
it is not necessary to enable IPv6 MLD snooping on the VLAN on the Catalyst 6500 switch.
When a group exists in the MLD snooping database, the switch responds to a group-specific query by
sending an MLDv1 report. When the group is unknown, the group-specific query is flooded to the
ingress VLAN.
When a host wants to leave a multicast group, it can send out an MLD Done message (equivalent to
IGMP Leave message). When the switch receives an MLDv1 Done message, if Immediate- Leave is not
enabled, the switch sends an MASQ to the port from which the message was received to determine if
other devices connected to the port should remain in the multicast group.
MLD Reports
The processing of MLDv1 join messages is essentially the same as with IGMPv2. When no IPv6
multicast routers are detected in a VLAN, reports are not processed or forwarded from the switch. When
IPv6 multicast routers are detected and an MLDv1 report is received, an IPv6 multicast group address
and an IPv6 multicast MAC address are entered in the VLAN MLD database. Then all IPv6 multicast
traffic to the group within the VLAN is forwarded using this address. When MLD snooping is disabled,
reports are flooded in the ingress VLAN.
When MLD snooping is enabled, MLD report suppression, called listener message suppression, is
automatically enabled. With report suppression, the switch forwards the first MLDv1 report received by
a group to IPv6 multicast routers; subsequent reports for the group are not sent to the routers. When
MLD snooping is disabled, report suppression is disabled, and all MLDv1 reports are flooded to the
ingress VLAN.
The switch also supports MLDv1 proxy reporting. When an MLDv1 MASQ is received, the switch
responds with MLDv1 reports for the address on which the query arrived if the group exists in the switch
on another port and if the port on which the query arrived is not the last member port for the address.
configuration command. The default is to send two queries. The switch also generates MLDv1 global
Done messages with valid link-local IPv6 source addresses when the switch becomes the STP root in the
VLAN or when it is configured by the user. This is same as done in IGMP snooping.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ipv6 mld snooping Globally enable MLD snooping on the switch.
Step 3 end Return to privileged EXEC mode.
Step 4 copy running-config startup-config (Optional) Save your entries in the configuration file.
Step 5 reload Reload the operating system.
To globally disable MLD snooping on the switch, use the no ipv6 mld snooping global configuration
command.
Beginning in privileged EXEC mode, follow these steps to enable MLD snooping on a VLAN.
Note When the IPv6 multicast router is a Catalyst 6500 switch and you are using extended VLANs (in the
range 1006 to 4094), IPv6 MLD snooping must be enabled on the extended VLAN on the Catalyst 6500
switch in order for this switch to receive queries on the VLAN. For normal-range VLANs (1 to 1005),
it is not necessary to enable IPv6 MLD snooping on the VLAN on the Catalyst 6500 switch.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ipv6 mld snooping Globally enable MLD snooping on the switch.
Step 3 ipv6 mld snooping vlan vlan-id Enable MLD snooping on the VLAN.The VLAN ID range is 1 to
1001 and 1006 to 4094.
Note MLD snooping must be globally enabled for VLAN snooping
to be enabled.
Step 4 end Return to privileged EXEC mode.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable MLD snooping on a VLAN interface, use the no ipv6 mld snooping vlan vlan-id global
configuration command for the specified VLAN number.
Command Purpose
Step 1 configure terminal Enter global configuration mode
Step 2 ipv6 mld snooping vlan vlan-id static Statically configure a multicast group with a Layer 2 port as a
ipv6_multicast_address interface interface-id member of a multicast group:
• vlan-id is the multicast group VLAN ID. The VLAN ID
range is 1 to 1001 and 1006 to 4094.
• ipv6_multicast_address is the 128-bit group IPv6 address.
The address must be in the form specified in RFC 2373.
• interface-id is the member port. It can be a physical
interface or a port channel (1 to 48).
Step 3 end Return to privileged EXEC mode.
Step 4 show ipv6 mld snooping address user Verify the static member port and the IPv6 address.
or
show ipv6 mld snooping address vlan vlan-id
user
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove a Layer 2 port from the multicast group, use the no ipv6 mld snooping vlan vlan-id static
mac-address interface interface-id global configuration command. If all member ports are removed
from a group, the group is deleted.
Note Static connections to multicast routers are supported only on switch ports.
Beginning in privileged EXEC mode, follow these steps to add a multicast router port to a VLAN:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ipv6 mld snooping vlan vlan-id mrouter Specify the multicast router VLAN ID, and specify the interface
interface interface-id to the multicast router.
• The VLAN ID range is 1 to 1001 and 1006 to 4094.
• The interface can be a physical interface or a port channel.
The port-channel range is 1 to 48.
Step 3 end Return to privileged EXEC mode.
Step 4 show ipv6 mld snooping mrouter [vlan vlan-id] Verify that IPv6 MLD snooping is enabled on the VLAN
interface.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove a multicast router port from the VLAN, use the no ipv6 mld snooping vlan vlan-id mrouter
interface interface-id global configuration command.
This example shows how to add a multicast router port to VLAN 200:
Switch# configure terminal
Switch(config)# ipv6 mld snooping vlan 200 mrouter interface gigabitethernet1/1/2
Switch(config)# exit
Beginning in privileged EXEC mode, follow these steps to enable MLDv1 Immediate Leave:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ipv6 mld snooping vlan vlan-id Enable MLD Immediate Leave on the VLAN interface.
immediate-leave
Step 3 end Return to privileged EXEC mode.
Step 4 show ipv6 mld snooping vlan vlan-id Verify that Immediate Leave is enabled on the VLAN interface.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable MLD Immediate Leave on a VLAN, use the no ipv6 mld snooping vlan vlan-id
immediate-leave global configuration command.
This example shows how to enable MLD Immediate Leave on VLAN 130:
Switch# configure terminal
Switch(config)# ipv6 mld snooping vlan 130 immediate-leave
Switch(config)# exit
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ipv6 mld snooping robustness-variable (Optional) Set the number of queries that are sent before switch will
value deletes a listener (port) that does not respond to a general query. The
range is 1 to 3; the default is 2.
Step 3 ipv6 mld snooping vlan vlan-id (Optional) Set the robustness variable on a VLAN basis, which
robustness-variable value determines the number of general queries that MLD snooping sends
before aging out a multicast address when there is no MLD report
response. The range is 1 to 3; the default is 0. When set to 0, the number
used is the global robustness variable value.
Step 4 ipv6 mld snooping (Optional) Set the number of MASQs that the switch sends before
last-listener-query-count count aging out an MLD client. The range is 1 to 7; the default is 2. The
queries are sent 1 second apart.
Step 5 ipv6 mld snooping vlan vlan-id (Optional) Set the last-listener query count on a VLAN basis. This
last-listener-query-count count value overrides the value configured globally. The range is 1 to 7; the
default is 0. When set to 0, the global count value is used. Queries are
sent 1 second apart.
Command Purpose
Step 6 ipv6 mld snooping (Optional) Set the maximum response time that the switch waits after
last-listener-query-interval interval sending out a MASQ before deleting a port from the multicast group.
The range is 100 to 32,768 thousands of a second. The default is 1000
(1 second).
Step 7 ipv6 mld snooping vlan vlan-id (Optional) Set the last-listener query interval on a VLAN basis. This
last-listener-query-interval interval value overrides the value configured globally. The range is 0 to 32,768
thousands of a second. The default is 0. When set to 0, the global
last-listener query interval is used.
Step 8 ipv6 mld snooping tcn query solicit (Optional) Enable topology change notification (TCN) solicitation,
which means that VLANs flood all IPv6 multicast traffic for the
configured number of queries before sending multicast data to only
those ports requesting to receive it. The default is for TCN to be
disabled.
Step 9 ipv6 mld snooping tcn flood query count (Optional) When TCN is enabled, specify the number of TCN queries
count to be sent. The range is from 1 to 10; the default is 2.
Step 10 end Return to privileged EXEC mode.
Step 11 show ipv6 mld snooping querier [vlan (Optional) Verify that the MLD snooping querier information for the
vlan-id] switch or for the VLAN.
Step 12 copy running-config startup-config (Optional) Save your entries in the configuration file.
This example shows how to set the MLD snooping global robustness variable to 3:
Switch# configure terminal
Switch(config)# ipv6 mld snooping robustness-variable 3
Switch(config)# exit
This example shows how to set the MLD snooping last-listener query count for a VLAN to 3:
Switch# configure terminal
Switch(config)# ipv6 mld snooping vlan 200 last-listener-query-count 3
Switch(config)# exit
This example shows how to set the MLD snooping last-listener query interval (maximum response time)
to 2000 (2 seconds):
Switch# configure terminal
Switch(config)# ipv6 mld snooping last-listener-query-interval 2000
Switch(config)# exit
Beginning in privileged EXEC mode, follow these steps to disable MLD listener message suppression:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 no ipv6 mld snooping Disable MLD message suppression.
listener-message-suppression
Step 3 end Return to privileged EXEC mode.
Step 4 show ipv6 mld snooping Verify that IPv6 MLD snooping report suppression is
disabled.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To re-enable MLD message suppression, use the ipv6 mld snooping listener-message-suppression
global configuration command.
Command Purpose
show ipv6 mld snooping [vlan vlan-id] Display the MLD snooping configuration information for all VLANs on
the switch or for a specified VLAN.
(Optional) Enter vlan vlan-id to display information for a single VLAN.
The VLAN ID range is 1 to 1001 and 1006 to 4094.
show ipv6 mld snooping mrouter [vlan vlan-id] Display information on dynamically learned and manually configured
multicast router interfaces. When you enable MLD snooping, the switch
automatically learns the interface to which a multicast router is
connected. These are dynamically learned interfaces.
(Optional) Enter vlan vlan-id to display information for a single VLAN.
The VLAN ID range is 1 to 1001 and 1006 to 4094.
show ipv6 mld snooping querier [vlan vlan-id] Display information about the IPv6 address and incoming port for the
most-recently received MLD query messages in the VLAN.
(Optional) Enter vlan vlan-id to display information for a single
VLAN.The VLAN ID range is 1 to 1001 and 1006 to 4094.
Command Purpose
show ipv6 mld snooping address [vlan vlan-id] Display all IPv6 multicast address information or specific IPv6
[count | dynamic | user] multicast address information for the switch or a VLAN.
• Enter count to show the group count on the switch or in a VLAN.
• Enter dynamic to display MLD snooping learned group information
for the switch or for a VLAN.
• Enter user to display MLD snooping user-configured group
information for the switch or for a VLAN.
show ipv6 mld snooping address vlan vlan-id Display MLD snooping for the specified VLAN and IPv6 multicast
[ipv6-multicast-address] address.
This chapter includes information about configuring IPv6 ACLs on the Catalyst 3750 Metro switch. You
can filter IP version 6 (IPv6) traffic by creating IPv6 access control lists (ACLs) and applying them to
interfaces similarly to the way that you create and apply IP version 4(IPv4) named ACLs. You can also
create and apply input router ACLs to filter Layer 3 management traffic.
Note To use IPv6, you must configure the dual IPv4 and IPv6 Switch Database Management (SDM) template
on the switch. You select the template by entering the sdm prefer dual-ipv4-and-ipv6 global
configuration command.
Note For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release or the Cisco IOS documentation referenced in the procedures.
Note If you configure unsupported IPv6 ACLs, an error message appears and the configuration does not take
affect.
The switch does not support VLAN ACLs (VLAN maps) for IPv6 traffic.
Note For more information about ACL support on the switch, see Chapter 33, “Configuring Network Security
with ACLs.”
Note If any port ACL (IPv4, IPv6, or MAC) is applied to an interface, that port ACL is used to filter packets,
and any router ACLs attached to the SVI of the port VLAN are ignored.
Step 1 Create an IPv6 ACL, and enter IPv6 access list configuration mode.
Step 2 Configure the IPv6 ACL to block (deny) or pass (permit) traffic.
Step 3 Apply the IPv6 ACL to an interface. For router ACLs, you must also configure an IPv6 address on the
Layer 3 interface to which the ACL is applied.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ipv6 access-list access-list-name Define an IPv6 access list name, and enter IPv6 access-list configuration mode.
Command Purpose
Step 3a deny | permit protocol Enter deny or permit to specify whether to deny or permit the packet if
{source-ipv6-prefix/prefix-length conditions are matched. These are the conditions:
| any | host source-ipv6-address}
• For protocol, enter the name or number of an Internet protocol: ahp, esp,
[operator [port-number]]
icmp, ipv6, pcp, stcp, tcp, or udp, or an integer in the range 0 to 255
{destination-ipv6-prefix/
representing an IPv6 protocol number. For additional specific parameters for
prefix-length | any |
ICMP, TCP, and UDP, see Steps 3b through 3d.
host destination-ipv6-address}
[operator [port-number]] • The source-ipv6-prefix/prefix-length or destination-ipv6-prefix/
[dscp value] [fragments] [log] prefix-length is the source or destination IPv6 network or class of networks
[log-input] [sequence value] for which to set deny or permit conditions, specified in hexadecimal and
[time-range name] using 16-bit values between colons (see RFC 2373).
Note Although the CLI help shows a prefix-length range of /0 to /128, the
switch supports IPv6 address matching only for prefixes in the range of
/0 to /64 and EUI-based /128 prefixes for aggregatable global unicast and
link-local host addresses.
Command Purpose
Step deny | permit tcp (Optional) Define a TCP access list and the access conditions.
3b {source-ipv6-prefix/prefix-length Enter tcp for Transmission Control Protocol. The parameters are the same as
| any | host source-ipv6-address} those described in Step 3a, with these additional optional parameters:
[operator [port-number]]
{destination-ipv6- • ack—Acknowledgment bit set.
prefix/prefix-length | any | host • established—An established connection. A match occurs if the TCP
destination-ipv6-address} datagram has the ACK or RST bits set.
[operator [port-number]] [ack]
[dscp value] [established] [fin] • fin—Finished bit set; no more data from sender.
[log] [log-input] [neq {port | • neq {port | protocol}—Matches only packets that are not on a given port
protocol}] [psh] [range {port | number.
protocol}] [rst] [sequence value]
• psh—Push function bit set.
[syn] [time-range name] [urg]
• range {port | protocol}—Matches only packets in the port number range.
• rst—Reset bit set.
• syn—Synchronize bit set.
• urg—Urgent pointer bit set.
Step deny | permit udp (Optional) Define a UDP access list and the access conditions.
3c {source-ipv6-prefix/prefix-length Enter udp for the User Datagram Protocol. The UDP parameters are the same as
| any | host source-ipv6-address} those described for TCP, except that the [operator [port]] port number or name
[operator [port-number]] must be a UDP port number or name, and the established parameter is not valid
{destination-ipv6-prefix/prefix-le for UDP.
ngth | any | host
destination-ipv6-address}
[operator [port-number]] [dscp
value] [log] [log-input] [neq
{port | protocol}] [range {port |
protocol}] [sequence value]
[time-range name]
Step deny | permit icmp (Optional) Define an ICMP access list and the access conditions.
3d {source-ipv6-prefix/prefix-length
Enter icmp for Internet Control Message Protocol. The ICMP parameters are the
| any | host source-ipv6-address}
same as those described for most IP protocols in Step 3a, with the addition of the
[operator [port-number]]
ICMP message type and code parameters. These optional keywords have these
{destination-ipv6-prefix/prefix-le
meanings:
ngth | any | host
destination-ipv6-address} • icmp-type—Enter to filter by ICMP message type, a number from 0 to 255.
[operator [port-number]] • icmp-code—Enter to filter ICMP packets that are filtered by the ICMP
[icmp-type [icmp-code] | message code type, a number from 0 to 255.
icmp-message] [dscp value] [log]
[log-input] [sequence value] • icmp-message—Enter to filter ICMP packets by the ICMP message type
[time-range name] name or the ICMP message type and code name. To see a list of ICMP
message type names and code names, use the ? key or see command
reference for this release.
Step 4 end Return to privileged EXEC mode.
Step 5 show ipv6 access-list Verify the access list configuration.
Step 6 copy running-config (Optional) Save your entries in the configuration file.
startup-config
Use the no deny | permit IPv6 access-list configuration commands with keywords to remove the deny
or permit conditions from the specified access list.
This example configures the IPv6 access list named CISCO. The first deny entry in the list denies all
packets that have a destination TCP port number greater than 5000. The second deny entry denies
packets that have a source UDP port number less than 5000. The second deny also logs all matches to
the console. The first permit entry in the list permits all ICMP packets. The second permit entry in the
list permits all other traffic. The second permit entry is necessary because an implicit deny -all condition
is at the end of each IPv6 access list.
Switch(config)# ipv6 access-list CISCO
Switch(config-ipv6-acl)# deny tcp any any gt 5000
Switch config-ipv6-acl)# deny ::/0 lt 5000 ::/0 log
Switch(config-ipv6-acl)# permit icmp any any
Switch(config-ipv6-acl)# permit any any
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Identify a Layer 2 interface (for port ACLs) or Layer 3 interface (for router
ACLs) on which to apply an access list, and enter interface configuration mode.
Step 3 no switchport If applying a router ACL, change the interface from Layer 2 mode (the default)
to Layer 3 mode.
Step 4 ipv6 address ipv6-address Configure an IPv6 address on a Layer 3 interface (for router ACLs).
This command is not required on Layer 2 interfaces or if the interface has
already been configured with an explicit IPv6 address.
Step 5 ipv6 traffic-filter access-list-name Apply the access list to incoming or outgoing traffic on the interface.
{in | out}
The out keyword is not supported for Layer 2 interfaces (port ACLs).
Step 6 end Return to privileged EXEC mode.
Step 7 show running-config Verify the access list configuration.
Step 8 copy running-config (Optional) Save your entries in the configuration file.
startup-config
Use the no ipv6 traffic-filter access-list-name interface configuration command to remove an access list
from an interface.
This example shows how to apply the access list Cisco to outbound traffic on a Layer 3 interface:
Switch(config)# interface gigabitethernet1/1/1
Switch(config-if)# no switchport
Switch(config-if)# ipv6 address 2001::/64 eui-64
Switch(config-if)# ipv6 traffic-filter CISCO out
Command Purpose
show access-lists Display all access lists configured on the switch.
show ipv6 access-list [access-list-name] Display all configured IPv6 access list or the access list specified by
name.
This is an example of the output from the show access-lists privileged EXEC command. The output
shows all access lists that are configured on the switch.
Switch #show access-lists
Extended IP access list hello
10 permit ip any any
IPv6 access list ipv6
permit ipv6 any any sequence 10
This is an example of the output from the show ipv6 access-lists privileged EXEC command. The output
shows only IPv6 access lists configured on the switch.
Switch# show ipv6 access-list
IPv6 access list inbound
permit tcp any any eq bgp (8 matches) sequence 10
permit tcp any any eq telnet (15 matches) sequence 20
permit udp any any sequence 30
This chapter describes how to use Hot Standby Router Protocol (HSRP), Virtual Router Redundancy
Protocol (VRRP), and the Gateway Load Balancing Protocol (GLPB) on the Catalyst 3750 Metro
switch. HSRP provides routing redundancy for routing IP traffic without being dependent on the
availability of any single router. GLBP provides routing redundancy similar to HSRP and also provides
load balancing over multiple routers by using a single virtual IP address and multiple virtual MAC
addresses. Cisco IOS Release 12.2(58)SE adds support for GLBP and VRRP for IPv4 and IPv6.
For complete syntax and usage information for the commands used in this chapter and more information
on configuring HSRP and GLBP, see these documents:
• Switch command reference for this release
• Cisco IOS IP Command Reference, Volume 1 of 3: Addressing and Services, Release 12.2:
http://www.cisco.com/en/US/docs/ios/12_2/ipaddr/command/reference/fipras_r.html
• Hot Standby Router Protocol Version 2 feature module:
http://www.cisco.com/en/US/docs/ios/12_3t/12_3t4/feature/guide/gthsrpv2.html
• Configuring GLBP feature module:
http://www.cisco.com/en/US/docs/ios/ipapp/configuration/guide/ipapp_glbp.html
• Configuring VRRP feature module:
http://www.cisco.com/en/US/docs/ios/ipapp/configuration/guide/ipapp_vrrp.html
• Configuring First Hop Redundancy Protocols in IPv6
http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-fhrp.html
This chapter consists of these sections:
• Understanding HSRP, page 40-1
• Configuring HSRP, page 40-4
• Displaying HSRP Configurations, page 40-10
• Configuring VRRP, page 40-11
• Configuring GLBP, page 40-11
Understanding HSRP
HSRP is the Cisco standard method of providing high network availability by providing first-hop
redundancy for IP hosts on an IEEE 802 LAN configured with a default gateway IP address. HSRP routes
IP traffic without relying on the availability of any single router. It enables a set of router interfaces to
work together to present the appearance of a single virtual router or default gateway to the hosts on a
LAN. When HSRP is configured on a network or segment, it provides a virtual Media Access Control
(MAC) address and an IP address that is shared among a group of configured routers. HSRP allows two
or more HSRP-configured routers to use the MAC address and IP network address of a virtual router.
The virtual router does not exist; it represents the common target for routers that are configured to
provide backup to each other. One of the routers is selected to be the active router and another to be the
standby router, which assumes control of the group MAC address and IP address should the designated
active router fail.
Note Routers in an HSRP group can be any router interface that supports HSRP, including
Catalyst 3750 Metro switch routed ports and switch virtual interfaces (SVIs).
HSRP provides high network availability by providing redundancy for IP traffic from hosts on networks.
In a group of router interfaces, the active router is the router of choice for routing packets; the standby
router is the router that takes over the routing duties when an active router fails or when preset conditions
are met.
HSRP is useful for hosts that do not support a router discovery protocol and cannot switch to a new router
when their selected router reloads or loses power. When HSRP is configured on a network segment, it
provides a virtual MAC address and an IP address that is shared among router interfaces in a group of
router interfaces running HSRP. The router selected by the protocol to be the active router receives and
routes packets destined for the group’s MAC address. For n routers running HSRP, there are n +1 IP and
MAC addresses assigned.
HSRP detects when the designated active router fails, and a selected standby router assumes control of
the Hot Standby group’s MAC and IP addresses. A new standby router is also selected at that time.
Devices running HSRP send and receive multicast UDP-based hello packets to detect router failure and
to designate active and standby routers. When HSRP is configured on an interface, Internet Control
Message Protocol (ICMP) redirect messages are automatically enabled for the interface.
You can configure multiple Hot Standby groups among switches that are operating in Layer 3 to make
more use of the redundant routers. To do so, specify a group number for each Hot Standby command
group you configure for an interface. For example, you might configure an interface on switch 1 as an
active router and one on switch 2 as a standby router and also configure another interface on switch 2 as
an active router with another interface on switch 1 as its standby router.
Figure 40-1 shows a segment of a network configured for HSRP. Each router is configured with the MAC
address and IP network address of the virtual router. Instead of configuring hosts on the network with
the IP address of Router A, you configure them with the IP address of the virtual router as their default
router. When Host C sends packets to Host B, it sends them to the MAC address of the virtual router. If
for any reason, Router A stops transferring packets, Router B responds to the virtual IP address and
virtual MAC address and becomes the active router, assuming the active router duties. Host C continues
to use the IP address of the virtual router to address packets destined for Host B, which Router B now
receives and sends to Host B. Until Router A resumes operation, HSRP allows Router B to provide
uninterrupted service to users on Host C’s segment that need to communicate with users on Host B’s
segment and also continues to perform its normal function of handling packets between the Host A
segment and Host B.
Host B
172.20.130.5
Router A Router B
172.20.128.32 172.20.128.55
101361
Host C Host A
HSRP Versions
The switch supports these HSRP versions:
• HSRPv1—Version 1 of the HSRP, the default version of HSRP. It has these features:
– The HSRP group number can be from 0 to 255.
– HSRPv1 uses the multicast address 224.0.0.2 to send hello packets, which can conflict with
Cisco Group Management Protocol (CGMP) leave processing. You cannot enable HSRPv1 and
CGMP at the same time; they are mutually exclusive.
• HSRPv2—Version 2 of the HSRP has these features:
– To match the HSRP group number to the VLAN ID of a subinterface, HSRPv2 can use a group
number from 0 to 4095 and a MAC address from 0000.0C9F.F000 to 0000.0C9F.FFFF.
– HSRPv2 uses the multicast address 224.0.0.102 to send hello packets. HSRPv2 and CGMP
leave processing are no longer mutually exclusive, and both can be enabled at the same time.
– HSRPv2 has a different packet format than HRSPv1.
A switch running HSRPv1 cannot identify the physical router that sent a hello packet because
the source MAC address of the router is the virtual MAC address.
HSRPv2 has a different packet format than HSRPv1. A HSRPv2 packet uses the
type-length-value (TLV) format and has a 6-byte identifier field with the MAC address of the
physical router that sent the packet.
If an interface running HSRPv1 gets an HSRPv2 packet, the type field is ignored.
HSRPv2 and HSRPv1 are mutually exclusive. HSRPv2 is not interoperable with HSRPv1 on an interface
and the reverse.
Configuring HSRP
• Default HSRP Configuration, page 40-4
• HSRP Configuration Guidelines, page 40-4
• Enabling HSRP, page 40-5
• Configuring HSRP Group Attributes, page 40-6
• Enabling HSRP Support for ICMP Redirect Messages, page 40-10
– Etherchannel port channel in Layer 3 mode: a port-channel logical interface created by using
the interface port-channel port-channel-number global configuration command and binding
the Ethernet interface into the channel group. For more information, see the “Configuring
Layer 3 EtherChannels” section on page 35-13.
• All Layer 3 interfaces must have IP addresses assigned to them. See the “Configuring Layer 3
Interfaces” section on page 9-17.
• HSRPv2 and HSRPv1 can be configured on the same switch if HSRPv2 is configured on different
interfaces than those on which HSRPv1 is configured.
• The version of an HSRP group can be changed from HSRPv2 to HSRPv1 only if the group number
is less than 256.
• If you change the HSRP version on an interface, each HSRP group resets because it now has a new
virtual MAC address.
Enabling HSRP
The standby ip interface configuration command activates HSRP on the configured interface. If an IP
address is specified, that address is used as the designated address for the Hot Standby group. If no IP
address is specified, the address is learned through the standby function. You must configure at least one
Layer 3 port on the LAN with the designated address. Configuring an IP address always overrides
another designated address currently in use.
When the standby ip command is enabled on an interface and proxy ARP is enabled, if the interface’s
Hot Standby state is active, proxy ARP requests are answered using the Hot Standby group MAC
address. If the interface is in a different state, proxy ARP responses are suppressed.
Note When multi-VRF CE is configured, you cannot assign the same HSRP standby address to two different
VPNs.
Beginning in privileged EXEC mode, follow these steps to create or enable HSRP on a Layer 3 interface:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and enter the Layer 3 interface on
which you want to enable HSRP.
Step 3 standby version {1 | 2} (Optional) Configure the HSRP version on the interface.
• 1— Select HSRPv1.
• 2— Select HSRPv2.
If you do not enter this command or do not specify a keyword, the
interface runs the default HSRP version, HSRP v1.
Command Purpose
Step 4 standby [group-number] ip [ip-address Create (or enable) the HSRP group using its number and virtual IP
[secondary]] address.
• (Optional) group-number—The group number on the interface for
which HSRP is being enabled. The range is 0 to 255; the default is 0.
If there is only one HSRP group, you do not need to enter a group
number.
• (Optional on all but one interface) ip-address—The virtual IP address
of the hot standby router interface. You must enter the virtual IP
address for at least one of the interfaces; it can be learned on the other
interfaces.
• (Optional) secondary—The IP address is a secondary hot standby
router interface. If neither router is designated as a secondary or
standby router and no priorities are set, the primary IP addresses are
compared and the higher IP address is the active router, with the next
highest as the standby router.
Step 5 end Return to privileged EXEC mode.
Step 6 show standby [interface-id [group]] Verify the configuration.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no standby [group-number] ip [ip-address] interface configuration command to disable HSRP.
This example shows how to activate HSRP for group 1 on an interface. The IP address used by the hot
standby group is learned by using HSRP.
Note This procedure is the minimum number of steps required to enable HSRP.
• The highest number (1 to 255) represents the highest priority (most likely to become the active
router).
• When setting the priority, preempt, or both, you must specify at least one keyword (priority,
preempt, or both).
• The priority of the device can change dynamically if an interface is configured with the standby
track command and another interface on the router goes down.
• The standby track interface configuration command ties the router hot standby priority to the
availability of its interfaces and is useful for tracking interfaces that are not configured for HSRP.
When a tracked interface fails, the hot standby priority on the device on which tracking has been
configured decreases by 10. If an interface is not tracked, its state changes do not affect the hot
standby priority of the configured device. For each interface configured for hot standby, you can
configure a separate list of interfaces to be tracked.
• The standby track interface-priority interface configuration command specifies how much to
decrement the hot standby priority when a tracked interface goes down. When the interface comes
back up, the priority is incremented by the same amount.
• When multiple tracked interfaces are down and interface-priority values have been configured, the
configured priority decrements are cumulative. If tracked interfaces that were not configured with
priority values fail, the default decrement is 10, and it is noncumulative.
• When routing is first enabled for the interface, it does not have a complete routing table. If it is
configured to preempt, it becomes the active router, even though it is unable to provide adequate
routing services. To solve this problem, configure a delay time to allow the router to update its
routing table.
Beginning in privileged EXEC mode, use one or more of these steps to configure HSRP priority
characteristics on an interface:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and enter the HSRP interface on which you
want to set priority.
Step 3 standby [group-number] priority Set a priority value used in choosing the active router. The range is 1 to 255;
priority the default priority is 100. The highest number represents the highest priority.
• (Optional) group-number—The group number to which the command
applies.
Use the no form of the command to restore the default values.
Command Purpose
Step 4 standby [group-number] preempt Configure the router to preempt, which means that when the local router has
[delay [minimum seconds] [reload a higher priority than the active router, it becomes the active router.
seconds] [sync seconds]]
• (Optional) group-number—The group number to which the command
applies.
• (Optional) delay minimum—Set to cause the local router to postpone
taking over the active role for the number of seconds shown. The range is
0 to 36000 seconds (1 hour); the default is 0 (no delay before taking over).
• (Optional) delay reload—Set to cause the local router to postpone taking
over the active role after a reload for the number of seconds shown. The
range is 0 to 36000 seconds (1 hour); the default is 0 (no delay before
taking over after a reload).
• (Optional) delay sync—Set to cause the local router to postpone taking
over the active role so that IP redundancy clients can reply (either with an
ok or wait reply) for the number of seconds shown. The range is 0 to 36000
seconds (1 hour); the default is 0 (no delay before taking over).
Use the no form of the command to restore the default values.
Step 5 standby [group-number] track Configure an interface to track other interfaces so that if one of the other
type number [interface-priority] interfaces goes down, the device’s Hot Standby priority is lowered.
• (Optional) group-number—The group number to which the command
applies.
• type—Enter the interface type (combined with interface number) that is
tracked.
• number—Enter the interface number (combined with interface type) that is
tracked.
• (Optional) interface-priority—Enter the amount by which the hot standby
priority for the router is decremented or incremented when the interface
goes down or comes back up. The default value is 10.
Step 6 end Return to privileged EXEC mode.
Step 7 show running-config Verify the configuration of the standby groups.
Step 8 copy running-config (Optional) Save your entries in the configuration file.
startup-config
Use the no standby [group-number] priority priority [preempt [delay delay]] and no standby
[group-number] [priority priority] preempt [delay delay] interface configuration commands to restore
default priority, preempt, and delay values.
Use the no standby [group-number] track type number [interface-priority] interface configuration
command to remove the tracking.
This example activates a port, sets an IP address and a priority of 120 (higher than the default value),
and waits for 300 seconds (5 minutes) before attempting to become the active router:
Switch# configure terminal
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# no switchport
Switch(config-if)# standby ip 172.19.108.254
Switch(config-if)# standby priority 120 preempt delay 300
Switch(config-if)# end
Switch#
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and enter the HSRP
interface on which you want to set authentication.
Step 3 standby [group-number] authentication string (Optional) authentication string—Enter a string to be carried in
all HSRP messages. The authentication string can be up to eight
characters in length; the default string is cisco.
(Optional) group-number—The group number to which the
command applies.
Step 4 standby [group-number] timers hellotime (Optional) Configure the time between hello packets and the
holdtime time before other routers declare the active router to be down.
• group-number—The group number to which the command
applies.
• hellotime—The hello interval in seconds. The range is from
1 to 255; the default is 3 seconds.
• holdtime—The time in seconds before the active or standby
router is declared to be down. The range is from 1 to 255;
the default is 10 seconds.
Step 5 end Return to privileged EXEC mode.
Step 6 show running-config Verify the configuration of the standby groups.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no standby [group-number] authentication string interface configuration command to delete
an authentication string. Use the no standby [group-number] timers hellotime holdtime interface
configuration command to restore timers to their default values.
This example shows how to configure word as the authentication string required to allow Hot Standby
routers in group 1 to interoperate:
Switch# configure terminal
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# no switchport
Switch(config-if)# standby 1 authentication word
Switch(config-if)# end
Switch#
This example shows how to set the timers on standby group 1 with the time between hello packets at 5
seconds and the time after which a router is considered down to be 15 seconds:
Switch# configure terminal
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# no switchport
Switch(config-if)# standby 1 ip
Switch(config-if)# standby 1 timers 5 15
Switch(config-if)# end
Switch#
Configuring VRRP
VRRP is an election protocol that dynamically assigns responsibility for one or more virtual routers to
the VRRP routers on a LAN, allowing several routers on a multi-access link to use the same virtual IP
address. A VRRP router is configured to run VRRP in conjunction with one or more other routers
attached to a LAN. In a VRRP configuration, one router is elected as the virtual router master, and the
other routers act as backups in case it fails.
VRRP Limitations
• You can configure either HSRP or VRRP, but not both, on a switch.
• The VRRP implementation on the switch does not support the MIB specified in RFC 2787.
• The VRRP implementation on the switch supports only text-based authentication.
• The switch supports VRRP only for IPv4.
For more VRRP information and configuration instructions, see Configuring VRRP.
Configuring GLBP
GLBP provides automatic router backup for IP hosts configured with a single default gateway on a LAN.
Multiple first-hop routers on the LAN combine to offer a single virtual first-hop IP router while sharing
the IP packet forwarding load. Other routers on the LAN act as redundant GLBP routers that become
active if any of the existing forwarding routers fail.
GLBP provides load balancing over multiple routers by using a single virtual IP address and multiple
virtual MAC addresses. Each host is configured with the same virtual IP address, and all routers in the
virtual router group forward packets.
HSRP, GLBP, and VRRP are First Hop Redundancy Protocols (FHRP).
Note The switch supports only one FHRP at a time. If you enable one FHRP on the switch and try to enable
a second one, the command fails.
GLPB is VPN Routing and Forwarding (VRF) aware, supporting multiple routing instances. You can use
VRF-aware services to ping for hosts or to display ARP entries for a specific VRF. You can configure
GLBP so that traffic from LAN clients can be shared by multiple routers, thereby sharing the traffic load
among available routers.
This chapter describes how to use Cisco IOS IP Service Level Agreements (SLAs) and the IETF
Two-Way Active Measurement Protocol (TWAMP) on the Catalyst 3750 Metro switch. Cisco IP SLAs
is a part of Cisco IOS software that allows Cisco customers to analyze IP service levels for IP
applications and services by using active traffic monitoring—the generation of traffic in a continuous,
reliable, and predictable manner—for measuring network performance. With Cisco IOS IP SLAs,
service provider customers can measure and provide service level agreements, and enterprise customers
can verify service levels, verify outsourced service level agreements, and understand network
performance. Cisco IOS IP SLAs can perform network assessments, verify quality of service (QoS), ease
the deployment of new services, and assist with network troubleshooting.
TWAMP defines a standard for measuring round-trip network traffic between any two devices that
support the protocol. Beginning with Cisco IOS Release 12.2(52)SE, you can implement TWAMP on
Catalyst 3750 Metro switches.
For more information about IP SLAs, see the Cisco IOS IP SLAs Configuration Guide, Release 12.4T at
this URL:
http://www.cisco.com/en/US/docs/ios/ipsla/configuration/guide/12_4t/sla_12_4t_book.html
For command syntax information, see the command reference at this URL:
http://www.cisco.com/en/US/docs/ios/ipsla/command/reference/sla_book.html
This chapter consists of these sections:
• Understanding Cisco IOS IP SLAs, page 41-1
• Configuring IP SLAs Operations, page 41-6
• Monitoring IP SLAs Operations, page 41-13
• Understanding TWAMP, page 41-14
• Configuring TWAMP, page 41-15
Depending on the specific Cisco IOS IP SLAs operation, various network performance statistics are
monitored within the Cisco device and stored in both command-line interface (CLI) and Simple Network
Management Protocol (SNMP) MIBs. IP SLAs packets have configurable IP and application layer
options such as source and destination IP address, User Datagram Protocol (UDP)/TCP port numbers, a
type of service (ToS) byte (including Differentiated Services Code Point [DSCP] and IP Prefix bits),
Virtual Private Network (VPN) routing/forwarding instance (VRF), and URL web address.
Because Cisco IP SLAs is Layer 2 transport independent, you can configure end-to-end operations over
disparate networks to best reflect the metrics that an end user is likely to experience. IP SLAs collects a
unique subset of these performance metrics:
• Delay (both round-trip and one-way)
• Jitter (directional)
• Packet loss (directional)
• Packet sequencing (packet ordering)
• Path (per hop)
• Connectivity (directional)
• Server or website download time
Because Cisco IOS IP SLAs is SNMP-accessible, it can also be used by performance-monitoring
applications like CiscoWorks Internetwork Performance Monitor (IPM) and other third-party Cisco
partner performance management products. You can find more details about network management
products that use Cisco IOS IP SLAs at this URL:
http://www.cisco.com/go/ipsla
Using IP SLAs can provide these benefits:
• Service-level agreement monitoring, measurement, and verification.
• Network performance monitoring
– Measures the jitter, latency, or packet loss in the network.
– Provides continuous, reliable, and predictable measurements.
• IP service network health assessment to verify that the existing QoS is sufficient for new IP services.
• Edge-to-edge network availability monitoring for proactive verification and connectivity testing of
network resources (for example, shows the network availability of an NFS server used to store
business critical data from a remote site).
• Troubleshooting of network operation by providing consistent, reliable measurement that
immediately identifies problems and saves troubleshooting time.
• Multiprotocol Label Switching (MPLS) performance monitoring and network verification (if the
switch supports MPLS)
This section includes this information about IP SLAs functionality:
• Using Cisco IOS IP SLAs to Measure Network Performance, page 41-3
• IP SLAs Responder and IP SLAs Control Protocol, page 41-4
• Response Time Computation for IP SLAs, page 41-4
• IP SLAs Operation Scheduling, page 41-5
• IP SLAs Operation Threshold Monitoring, page 41-5
Performance
Any IP device management
application
IP SLA measurement
and IP SLA responder to
IP SLA Responder SNMP
IP SLA IP SLA
IP network
121381
IP SLA responder IP SLA source
IP SLA measurement
and IP SLA responder to
IP SLA Responder
To implement IP SLAs network performance measurement, you need to perform these tasks:
1. Enable the IP SLAs responder, if required.
2. Configure the required IP SLAs operation type.
3. Configure any options available for the specified operation type.
4. Configure threshold conditions, if required.
5. Schedule the operation to run, then let the operation run for a period of time to gather statistics.
6. Display and interpret the results of the operation using the Cisco IOS CLI or a network
management system (NMS) system with SNMP.
For more information about IP SLAs operations, see the operation-specific chapters in the Cisco IOS IP
SLAs Configuration Guide at this URL:
http://www.cisco.com/en/US/docs/ios/ipsla/configuration/guide/12_4t/sla_12_4t_book.html
Note The switch does not support Voice over IP (VoIP) service levels using the gatekeeper registration delay
operations measurements. Before configuring any IP SLAs application, you can use the show ip sla
application privileged EXEC command to verify that the operation type is supported on your software
image.
Note The IP SLAs responder can be a Cisco IOS Layer 2, responder-configurable switch, such as a
Catalyst 2960 or Cisco ME 2400 switch. The responder does not need to support full IP SLAs
functionality.
Figure 41-1 shows where the Cisco IOS IP SLAs responder fits in the IP network. The responder listens
on a specific port for control protocol messages sent by an IP SLAs operation. Upon receipt of the
control message, it enables the specified UDP or TCP port for the specified duration. During this time,
the responder accepts the requests and responds to them. It disables the port after it responds to the IP
SLAs packet, or when the specified time expires. MD5 authentication for control messages is available
for added security.
You do not need to enable the responder on the destination device for all IP SLAs operations. For
example, a responder is not required for services that are already provided by the destination router (such
as Telnet or HTTP). You cannot configure the IP SLAs responder on non-Cisco devices and Cisco IOS
IP SLAs can send operational packets only to services native to those devices.
121380
RTT (Round-trip time) = T4 (Time stamp 4) - T1 (Time stamp 1) -
An additional benefit of the two time stamps at the target device is the ability to track one-way delay,
jitter, and directional packet loss. Because much network behavior is asynchronous, it is critical to have
these statistics. However, to capture one-way delay measurements, you must configure both the source
router and target router with Network Time Protocol (NTP) so that the source and target are
synchronized to the same clock source. One-way jitter measurements do not require clock
synchronization.
• One-way latency
An IP SLAs threshold violation can also trigger another IP SLAs operation for further analysis. For
example, the frequency could be increased or an ICMP path echo or ICMP path jitter operation could be
initiated for troubleshooting.
Determining the type of threshold and the level to set can be complex, and depends on the type of IP
service being used in the network. For more details on using thresholds with Cisco IOS IP SLAs
operations, see the “IP SLAs—Proactive Threshold Monitoring” chapter of the Cisco IOS IP SLAs
Configuration Guide at this URL:
http://www.cisco.com/en/US/docs/ios/ipsla/configuration/guide/12_4t/sla_12_4t_book.html
Default Configuration
No IP SLAs operations are configured.
Configuration Guidelines
For information on the IP SLAs commands, see the Cisco IOS IP SLAs Command Reference, Release
12.4T command reference at this URL:
http://www.cisco.com/en/US/docs/ios/ipsla/command/reference/sla_book.html
For detailed descriptions and configuration procedures, see the Cisco IOS IP SLAs Configuration Guide,
Release 12.4T at this URL:
http://www.cisco.com/en/US/docs/ios/ipsla/configuration/guide/12_4t/sla_12_4t_book.html
Note that not all of the IP SLAs commands or operations described in this guide are supported on the
switch. The switch supports IP service level analysis by using UDP jitter, UDP echo, HTTP, TCP
connect, ICMP echo, ICMP path echo, ICMP path jitter, FTP, DNS, and DHCP, as well as multiple
operation scheduling and proactive threshold monitoring. It does not support VoIP service levels using
the gatekeeper registration delay operations measurements.
Before configuring any IP SLAs application, you can use the show ip sla application privileged EXEC
command to verify that the operation type is supported on your software image. This is an example of
the output from the command:
Switch# show ip sla application
IP SLAs
Version: 2.2.0 Round Trip Time MIB, Infrastructure Engine-II
Time of last change in whole IP SLAs: 22:17:39.117 UTC Fri Jun
Estimated system max number of entries: 15801
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip sla responder {tcp-connect | Configure the switch as an IP SLAs responder.
udp-echo} ipaddress ip-address port
The keywords have these meanings:
port-number
• tcp-connect—Enable the responder for TCP connect operations.
• udp-echo—Enable the responder for User Datagram Protocol (UDP)
echo or jitter operations.
• ipaddress ip-address—Enter the destination IP address.
• port port-number—Enter the destination port number.
Note The IP address and port number must match those configured on
the source device for the IP SLAs operation.
Step 3 end Return to privileged EXEC mode.
Command Purpose
Step 4 show ip sla responder Verify the IP SLAs responder configuration on the device.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable the IP SLAs responder, enter the no ip sla responder global configuration command. This
example shows how to configure the device as a responder for the UDP jitter IP SLAs operation in the
next procedure:
Switch(config)# ip sla responder udp-echo 172.29.139.134 5000
Note Before you configure a UDP jitter operation on the source device, you must enable the IP SLAs
responder on the target device (the operational target).
Beginning in privileged EXEC mode, follow these steps to configure UDP jitter operation on the source
device:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip sla operation-number Create an IP SLAs operation, and enter IP SLAs
configuration mode.
Step 3 udp-jitter {destination-ip-address | destination-hostname} Configure the IP SLAs operation as a UDP jitter
destination-port [source-ip {ip-address | hostname}] operation, and enter UDP jitter configuration mode.
[source-port port-number] [control {enable | disable}]
• destination-ip-address |
[num-packets number-of-packets] [interval
destination-hostname—Specify the destination
interpacket-interval]
IP address or hostname.
• destination-port—Specify the destination port
number in the range from 1 to 65535.
• (Optional) source-ip {ip-address |
hostname}—Specify the source IP address or
hostname. When a source IP address or
hostname is not specified, IP SLAs chooses the
IP address nearest to the destination
• (Optional) source-port port-number—Specify
the source port number in the range from 1 to
65535. When a port number is not specified, IP
SLAs chooses an available port.
• (Optional) control—Enable or disable sending
of IP SLAs control messages to the IP SLAs
responder. By default, IP SLAs control
messages are sent to the destination device to
establish a connection with the IP SLAs
responder
• (Optional) num-packets
number-of-packets—Enter the number of
packets to be generated. The range is 1 to 6000;
the default is 10.
• (Optional) interval
inter-packet-interval—Enter the interval
between sending packets in milliseconds. The
range is 1 to 6000; the default value is 20 ms.
Step 4 frequency seconds (Optional) Set the rate at which a specified IP SLAs
operation repeats. The range is from 1 to 604800
seconds; the default is 60 seconds.
Step 5 exit Exit UDP jitter configuration mode, and return to
global configuration mode.
Command Purpose
Step 6 ip sla monitor schedule operation-number [life {forever | Configure the scheduling parameters for an
seconds}] [start-time {hh:mm [:ss] [month day | day month] individual IP SLAs operation.
| pending | now | after hh:mm:ss] [ageout seconds]
• operation-number—Enter the RTR entry
[recurring]
number.
• (Optional) life—Set the operation to run
indefinitely (forever) or for a specific number
of seconds. The range is from 0 to 2147483647.
The default is 3600 seconds (1 hour).
• (Optional) start-time—Enter the time for the
operation to begin collecting information:
– To start at a specific time, enter the hour,
minute, second (in 24-hour notation), and
day of the month. If no month is entered,
the default is the current month.
– Enter pending to select no information
collection until a start time is selected.
– Enter now to start the operation
immediately.
– Enter after hh:mm:ss to show that the
operation should start after the entered time
has elapsed.
• (Optional) ageout seconds—Enter the number
of seconds to keep the operation in memory
when it is not actively collecting information.
The range is 0 to 2073600 seconds, the default
is 0 seconds (never ages out).
• (Optional) recurring—Set the operation to
automatically run every day.
Step 7 end Return to privileged EXEC mode.
Step 8 show ip sla configuration [operation-number] (Optional) Display configuration values, including
all defaults for all IP SLAs operations or a specified
operation.
Step 9 copy running-config startup-config (Optional) Save your entries in the configuration
file.
To disable the IP SLAs operation, enter the no ip sla operation-number global configuration command.
This example shows how to configure a UDP jitter IP SLAs operation:
Switch(config)# ip sla 10
Switch(config-ip-sla)# udp-jitter 172.29.139.134 5000
Switch(config-ip-sla-jitter)# frequency 30
Switch(config-ip-sla-jitter)# exit
Switch(config)# ip sla schedule 5 start-time now life forever
Switch(config)# end
Switch# show ip sla configuration 10
IP SLAs, Infrastructure Engine-II.
Entry number: 10
Owner:
Tag:
Type of operation to perform: udp-jitter
Target address/Source address: 1.1.1.1/0.0.0.0
Target port/Source port: 2/0
Request size (ARR data portion): 32
Operation timeout (milliseconds): 5000
Packet Interval (milliseconds)/Number of packets: 20/10
Type Of Service parameters: 0x0
Verify data: No
Vrf Name:
Control Packets: enabled
Schedule:
Operation frequency (seconds): 30
Next Scheduled Start Time: Pending trigger
Group Scheduled : FALSE
Randomly Scheduled : FALSE
Life (seconds): 3600
Entry Ageout (seconds): never
Recurring (Starting Everyday): FALSE
Status of entry (SNMP RowStatus): notInService
Threshold (milliseconds): 5000
Distribution Statistics:
Number of statistic hours kept: 2
Number of statistic distribution buckets kept: 1
Statistic distribution interval (milliseconds): 20
Enhanced History:
Note This operation does not require the IP SLAs responder to be enabled.
Beginning in privileged EXEC mode, follow these steps to configure an ICMP echo operation on the
source device:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip sla operation-number Create an IP SLAs operation and enter IP SLAs configuration mode.
Command Purpose
Step 3 icmp-echo {destination-ip-address Configure the IP SLAs operation as an ICMP Echo operation and enter ICMP
| destination-hostname} [source-ip echo configuration mode.
{ip-address | hostname} |
• destination-ip-address | destination-hostname—Specify the destination IP
source-interface interface-id]
address or hostname.
• (Optional) source-ip {ip-address | hostname}—Specify the source IP
address or hostname. When a source IP address or hostname is not
specified, IP SLAs chooses the IP address nearest to the destination
• (Optional) source-interface interface-id—Specify the source interface for
the operation.
Step 4 frequency seconds (Optional) Set the rate at which a specified IP SLAs operation repeats. The
range is from 1 to 604800 seconds; the default is 60 seconds.
Step 5 exit Exit UDP jitter configuration mode, and return to global configuration mode.
Step 6 ip sla schedule operation-number Configure the scheduling parameters for an individual IP SLAs operation.
[life {forever | seconds}]
• operation-number—Enter the RTR entry number.
[start-time {hh:mm [:ss] [month
day | day month] | pending | now | • (Optional) life—Set the operation to run indefinitely (forever) or for a
after hh:mm:ss] [ageout seconds] specific number of seconds. The range is from 0 to 2147483647. The
[recurring] default is 3600 seconds (1 hour)
• (Optional) start-time—Enter the time for the operation to begin collecting
information:
– To start at a specific time, enter the hour, minute, second (in 24-hour
notation), and day of the month. If no month is entered, the default is
the current month.
– Enter pending to select no information collection until a start time is
selected.
– Enter now to start the operation immediately.
– Enter after hh:mm:ss to indicate that the operation should start after
the entered time has elapsed.
• (Optional) ageout seconds—Enter the number of seconds to keep the
operation in memory when it is not actively collecting information. The
range is 0 to 2073600 seconds; the default is 0 seconds (never ages out).
• (Optional) recurring—Set the operation to automatically run every day.
Step 7 end Return to privileged EXEC mode.
Step 8 show ip sla configuration (Optional) Display configuration values including all defaults for all IP SLAs
[operation-number] operations or a specified operation.
Step 9 copy running-config (Optional) Save your entries in the configuration file.
startup-config
To disable the IP SLAs operation, enter the no ip sla operation-number global configuration command.
This example shows how to configure an ICMP echo IP SLAs operation:
Switch(config)# ip sla 12
Switch(config-ip-sla)# icmp-echo 172.29.139.134
Switch(config-ip-sla-echo)# frequency 30
Switch(config-ip-sla-echo)# exit
Switch(config)# ip sla schedule 5 start-time now life forever
Switch(config)# end
Switch# show ip sla configuration 22
IP SLAs, Infrastructure Engine-II.
Entry number: 12
Owner:
Tag:
Type of operation to perform: echo
Target address: 2.2.2.2
Source address: 0.0.0.0
Request size (ARR data portion): 28
Operation timeout (milliseconds): 5000
Type Of Service parameters: 0x0
Verify data: No
Vrf Name:
Schedule:
Operation frequency (seconds): 60
Next Scheduled Start Time: Pending trigger
Group Scheduled : FALSE
Randomly Scheduled : FALSE
Life (seconds): 3600
Entry Ageout (seconds): never
Recurring (Starting Everyday): FALSE
Status of entry (SNMP RowStatus): notInService
Threshold (milliseconds): 5000
Distribution Statistics:
Number of statistic hours kept: 2
Number of statistic distribution buckets kept: 1
Statistic distribution interval (milliseconds): 20
History Statistics:
Number of history Lives kept: 0
Number of history Buckets kept: 15
History Filter Type: None
Enhanced History:
Command Purpose
show ip sla application Display global information about Cisco IOS IP SLAs.
show ip sla authentication Display IP SLAs authentication information.
show ip sla configuration [entry-number] Display configuration values including all defaults for
all IP SLAs operations or a specific operation.
show ip sla enhanced-history {collection-statistics | distribution Display enhanced history statistics for collected history
statistics} [entry-number] buckets or distribution statistics for all IP SLAs
operations or a specific operation.
show ip sla ethernet-monitor configuration [entry-number] Display IP SLAs automatic Ethernet configuration.
show ip sla group schedule [schedule-entry-number] Display IP SLAs group scheduling configuration and
details.
show ip sla history [entry-number | full | tabular] Display history collected for all IP SLAs operations
Command Purpose
show ip sla mpls-lsp-monitor {collection-statistics | Display MPLS label switched path (LSP) Health
configuration | ldp operational-state | scan-queue | summary Monitor operations,
[entry-number] | neighbors}
show ip sla reaction-configuration [entry-number] Display the configured proactive threshold monitoring
settings for all IP SLAs operations or a specific
operation.
show ip sla reaction-trigger [entry-number] Display the reaction trigger information for all IP SLAs
operations or a specific operation.
show ip sla responder Display information about the IP SLAs responder.
show ip sla statistics [entry-number | aggregated | details] Display current or aggregated operational status and
statistics.
Understanding TWAMP
TWAMP consists of two related protocols. Use the TWAMP-Control protocol to start performance
measurement sessions. Use TWAMP-Test to send and receive performance-measurement probes. You
can deploy TWAMP in a simplified network architecture, with the control-client and the session-sender
on one device and the server and the session-reflector on another device.
The Cisco IOS software TWAMP implementation supports a basic configuration. Figure 41-3 shows a
sample deployment.
Figure 41-4 shows the four logical entities that comprise TWAMP.
Control-client
and sender
Client
251575
Vendor- Vendor-
specific specific
251576
Control-Client Server
TWAMP-Ctrl
Although each entity is separate, the protocol allows for logical merging of the roles on a single device.
Configuring TWAMP
• Configuring the TWAMP Server, page 41-15
• Configuring the TWAMP Reflector, page 41-16
• Troubleshooting TWAMP, page 41-16
Note The switch does not support the TWAMP sender and client roles.
Beginning in privileged EXEC mode, follow these steps to configure the TWAMP server:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip sla server twamp Configure the switch as a TWAMP server, and enter TWAMP
configuration mode.
Step 3 port port-number (Optional) Specify the port to be used by the TWAMP server to listen for
connection and control requests. The same port negotiates for the port to
which performance probes are sent. The configured port should not be an
IANA well-known port or any port used by other applications. The default
is port 862.
Step 4 timer inactivity seconds (Optional) Set the maximum time, in seconds, the session can be inactive
before the session ends. The range is 1–6000 seconds. The default is
900 seconds.
Step 5 end Return to privileged EXEC mode.
Step 6s show ip sla standards (Optional) Display the IP SLA standards supported on the switch.
Step 7 show ip sla twamp connection (Optional) Display the number and the source of TWAMP connections.
requests
Command Purpose
Step 8 show ip sla twamp connection detail (Optional) Display the connection ID, client IP address and port number,
mode and status of TWAMP connections, and the number of test requests.
Step 9 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable the IP SLA TWAMP server, enter the no ip sla server twamp global configuration command.
This example shows how to configure a switch as an IP SLA TWAMP server:
Switch(config)# ip sla server twamp
Switch(config-twamp-srvr)# port 9000
Switch(config-twamp-srvr)# timer inactivity 300
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip sla responder twamp Configure the switch as a TWAMP responder, and enter TWAMP
configuration mode.
Step 3 timeout seconds (Optional) Set the maximum time, in seconds, the session can be inactive
before the session ends. The range is 1–604800 seconds. The default is
900 seconds.
Step 4 end Return to privileged EXEC mode.
Step 5 show ip sla twamp session [source-ip (Optional) Display information about TWAMP test results for the
ip-address source-port port-number] specified client.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable the IP SLA TWAMP reflector, enter the no ip sla responder twamp global configuration
command. This example shows how to configure a switch as an IP SLA TWAMP reflector:
Switch(config)# ip sla responder twamp
Switch(config-twamp-srvr)# timeout 300
Troubleshooting TWAMP
Use these commands to troubleshoot TWAMP sessions:
debug ip sla error twamp [connection source-ip ip-address | control {reflector | server} | session
source-ip ip-address]
debug ip sla trace twamp [connection source-ip ip-address | control {reflector | server} | session
source-ip ip-address]
This chapter describes how to configure enhanced object tracking on the Catalyst 3750 Metro switch.
This feature provides a more complete alternative to the Hot Standby Routing Protocol (HSRP) tracking
mechanism. which allows you to track the line-protocol state of an interface. If the line protocol state of
an interface goes down, the HSRP priority of the interface is reduced and another HSRP device with a
higher priority becomes active. The enhanced object tracking feature separates the tracking mechanism
from HSRP and creates a separate, standalone tracking process that can be used by processes other than
HSRP. This allows tracking other objects in addition to the interface line-protocol state. A client process,
such as HSRP or Gateway Local Balancing Protocol (GLBP), can register an interest in tracking objects
and request notification when the tracked object changes state.This feature increases the availability and
speed of recovery of a routing system and decreases outages and outage duration.
For more information about enhanced object tracking and the commands used to configure it, see this
URL:
http://www.cisco.com/en/US/docs/ios/12_2t/12_2t15/feature/guide/fthsrptk.html
The chapter includes these sections:
• Understanding Enhanced Object Tracking, page 42-1
• Configuring Enhanced Object Tracking Features, page 42-2
• Monitoring Enhanced Object Tracking, page 42-13
Default Configuration
No type of object tracking is configured.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 track object-number interface (Optional) Create a tracking list to track the line-protocol state of an interface
interface-id line-protocol and enter tracking configuration mode.
• The object-number identifies the tracked object and can be from 1 to 500.
• The interface interface-id is the interface being tracked.
Step 3 delay {up seconds [down seconds] (Optional) Specify a period of time in seconds to delay communicating state
| [up seconds] down seconds} changes of a tracked object. The range is from 1 to 180 seconds.
Step 4 exit Return to global configuration mode.
Step 5 track object-number interface (Optional) Create a tracking list to track the IP routing state of an interface, and
interface-id ip routing enter tracking configuration mode. IP-route tracking tracks an IP route in the
routing table and the ability of an interface to route IP packets.
• The object-number identifies the tracked object and can be from 1 to 500.
• The interface interface-id is the interface being tracked.
Command Purpose
Step 6 delay {up seconds [down seconds] (Optional) Specify a period of time in seconds to delay communicating state
| [up seconds] down seconds} changes of a tracked object. The range is from 1 to 180 seconds.
Step 7 end Return to privileged EXEC mode.
Step 8 show track object-number Verify that the specified objects are being tracked.
Step 9 copy running-config (Optional) Save your entries in the configuration file.
startup-config
This example configures the tracking of an interface line-protocol state and verifies the configuration:
Switch(config)# track 33 interface gigabitethernet 1/0/1 line-protocol
Switch(config-track)# end
Switch# show track 33
Track 33
Interface GigabitEthernet1/0/1 line-protocol
Line protocol is Down (hw down)
1 change, last change 00:18:28
Beginning in privileged EXEC mode, follow these steps to configure a tracked list of objects with a
Boolean expression:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 track track-number list boolean Configure a tracked list object, and enter tracking configuration mode. The
{and | or} track-number can be from 1 to 500.
• boolean—Specify the state of the tracked list based on a Boolean
calculation.
• and—Specify that the list is up if all objects are up or down if one or
more objects are down.
• or—Specify that the list is up if one object is up or down if all objects
are down.
Step 3 object object-number [not] Specify the object to be tracked. The range is from 1 to 500. The keyword
not negates the state of the object, which means that when the object is up,
the tracked list detects the object as down.
Note An object must exist before you can add it to a tracked list.
Step 4 delay {up seconds [down seconds] | (Optional) Specify a period of time in seconds to delay communicating state
[up seconds] down seconds} changes of a tracked object. The range is from 1 to 180 seconds.
Step 5 end Return to privileged EXEC mode.
Step 6 show track object-number Verify that the specified objects are being tracked.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no track track-number global configuration command to delete the tracked list.
This example configures track list 4 with a Boolean AND expression that contains two objects with one
object state negated. If the list is up, the list detects that object 2 is down:
Switch(config)# track 4 list boolean and
Switch(config-track)# object 1
Switch(config-track)# object 2 not
Switch(config-track)# exit
Beginning in privileged EXEC mode, follow these steps to configure a tracked list of objects by using a
weight threshold and to configure a weight for each object:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 track track-number list threshold Configure a tracked list object and enter tracking configuration mode. The
weight track-number can be from 1 to 500.
• threshold—Specify the state of the tracked list based on a threshold.
• weight—Specify that the threshold is based on weight.
Step 3 object object-number [weight Specify the object to be tracked. The range is from 1 to 500. The optional
weight-number] weight weight-number specifies a threshold weight for the object. The range
is from 1 to 255.
Note An object must exist before you can add it to a tracked list.
Step 4 threshold weight {up number | Specify the threshold weight.
[down number]}
• up number—The valid range is from 1 to 255.
• down number—(Optional) The range depends on the number selected
for the up number. If you configure the up number as 25, the range
shown for the down number is 0 to 24.
Step 5 delay {up seconds [down seconds] | (Optional) Specify a period of time in seconds to delay communicating state
[up seconds] down seconds} changes of a tracked object. The range is from 1 to 180 seconds.
Step 6 end Return to privileged EXEC mode.
Step 7 show track object-number Verify that the specified objects are being tracked.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no track track-number global configuration command to delete the tracked list.
The example configures track list 4 to track by weight threshold. If object 1 and object 2 are down, then
track list 4 is up because object 3 satisfies the up threshold value of up 30. But if object 3 is down, both
objects 1 and 2 must be up in order to satisfy the threshold weight.
Switch(config)# track 4 list threshold weight
Switch(config-track)# object 1 weight 15
Switch(config-track)# object 2 weight 20
Switch(config-track)# object 3 weight 30
Switch(config-track)# threshold weight up 30 down 10
Switch(config-track)# exit
This configuration can be useful if object 1 and object 2 represent two small bandwidth connections and
object 3 represents one large bandwidth connection. The configured down 10 value means that once the
tracked object is up, it will not go down until the threshold value is equal to or lower than 10, which in
this example means that all connections are down.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 track track-number list threshold Configure a tracked list object and enter tracking configuration mode. The
percentage track-number can be from 1 to 500.
• threshold—Specify the state of the tracked list based on a threshold.
• percentage—Specify that the threshold is based on percentage.
Step 3 object object-number Specify the object to be tracked. The range is from 1 to 500.
Note An object must exist before you can add it to a tracked list.
Step 4 threshold percentage {up number | Specify the threshold percentage.
[down number]}
• up number—The valid range is from 1 to 100.
• down number]—(Optional) The range depends on the number selected
for the up number. If you configure the up number as 25, the range
shown for the down number is 0 to 24.
Step 5 delay {up seconds [down seconds] | (Optional) Specify a period of time in seconds to delay communicating state
[up seconds] down seconds} changes of a tracked object. The range is from 1 to 180 seconds.
Step 6 end Return to privileged EXEC mode.
Step 7 show track object-number Verify that the specified objects are being tracked.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no track track-number global configuration command to delete the tracked list.
This example configures tracked list 4 with three objects and a specified percentages to measure the state
of the list:
Switch(config)# track 4 list threshold percentage
Switch(config-track)# object 1
Switch(config-track)# object 2
Switch(config-track)# object 3
Switch(config-track)# threshold percentage up 51 down 10
Switch(config-track)# exit
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 track object-number {interface (Optional) Create a tracking list to track the configured state and enter
interface-id {line-protocol | ip tracking configuration mode.
routing} | ip route
• The object-number range is from 1 to 500.
ip-address/prefix-length {metric
threshold | reachability} | list • Enter interface interface-id to select an interface to track.
{boolean {and | or}} | {threshold • Enter line-protocol to track the interface line protocol state or enter ip
{weight | percentage}}} routing to track the interface IP routing state.
• Enter ip route ip-address/prefix-length to track the state of an IP route.
• Enter metric threshold to track the threshold metric or enter
reachability to track if the route is reachable.
The default up threshold is 254 and the default down threshold is 255.
• Enter list to track objects grouped in a list. Configure the list as
described on the previous pages.
– For boolean, see the “Configuring a Tracked List with a Boolean
Expression” section on page 42-3
– For threshold weight, see the “Configuring a Tracked List with a
Weight Threshold” section on page 42-4
– For threshold percentage, see the “Configuring a Tracked List with
a Percentage Threshold” section on page 42-6
Note Repeat this step for each interface to be tracked.
Step 3 exit Return to global configuration mode.
Step 4 interface interface-id Enter interface configuration mode.
Step 5 standby [group-number] ip Create (or enable) the HSRP group by using its number and virtual IP
[ip-address [secondary]] address.
• (Optional) group-number—Enter a group number on the interface for
which HSRP is being enabled. The range is 0 to 255; the default is 0. If
there is only one HSRP group, you do not need to enter a group number.
• (Optional on all but one interface) ip-address—Specify the virtual IP
address of the hot standby router interface. You must enter the virtual IP
address for at least one of the interfaces; it can be learned on the other
interfaces.
• (Optional) secondary—Specify that the IP address is a secondary hot
standby router interface. If this keyword is omitted, the configured
address is the primary IP address.
Command Purpose
Step 6 standby [group-number] track Configure HSRP to track an object and change the hot standby priority based
object-number [decrement on the state of the object.
[priority-decrement]]
• (Optional) group-number—Enter the group number to which the
tracking applies.
• object-number—Enter a number representing the object to be tracked.
The range is from 1 to 500; the default is 1.
• (Optional) decrement priority-decrement—Specify the amount by
which the hot standby priority for the router is decremented (or
incremented) when the tracked object goes down (or comes back up).
The range is from 1 to 255; the default is 10.
Step 7 end Return to privileged EXEC mode.
Step 8 show standby Verify the standby router IP address and tracking states.
Step 9 copy running-config startup-config (Optional) Save your entries in the configuration file.
aspects of IP SLAs operation: state and reachability. For state, if the return code is OK, the track state is
up; if the return code is not OK, the track state is down. For reachability, if the return code is OK or
OverThreshold, reachability is up; if not OK, reachability is down.
Beginning in privileged EXEC mode, follow these steps to track the state of an IP SLAs operation or the
reachability of an IP SLAs IP host:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 track object-number rtr Enter tracking configuration mode to track the state of an IP SLAs operation.
operation-number state
• The object-number range is from 1 to 500.
• The operation-number range is from 1 to 2147483647.
Step 3 delay {up seconds [down seconds] | (Optional) Specify a period of time in seconds to delay communicating state
[up seconds] down seconds} changes of a tracked object. The range is from 1 to 180 seconds.
Step 4 exit Return to global configuration mode.
Step 5 track object-number rtr Enter tracking configuration mode to track the reachability of an IP SLAs IP
operation-number reachability host.
• The object-number range is from 1 to 500.
• The operation-number range is from 1 to 2147483647.
Step 6 delay {up seconds [down seconds] | (Optional) Specify a period of time in seconds to delay communicating state
[up seconds] down seconds} changes of a tracked object. The range is from 1 to 180 seconds.
Step 7 end Return to privileged EXEC mode.
Step 8 show track object-number Display tracking information to verify the configuration.
Step 9 copy running-config startup-config (Optional) Save your entries in the configuration file.
This example shows how to configure and display IP SLAs state tracking:
Switch(config)# track 2 200 state
Switch(config)# end
Switch# show track 2
Track 2
Response Time Reporter 1 state
State is Down
1 change, last change 00:00:47
Latest operation return code: over threshold
Latest RTT (millisecs) 4
Tracked by:
HSRP Ethernet0/1 3
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Select a primary or secondary interface and enter interface
configuration mode.
Step 3 description string Add a description to the interface.
Step 4 ip address ip-address mask [secondary] Set the primary or secondary IP address for the interface.
Step 5 exit Return to global configuration mode.
Beginning in privileged EXEC mode, follow these steps to configure a primary interface for DHCP:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Select a primary or secondary interface and enter interface
configuration mode.
Step 3 description string Add a description to the interface.
Step 4 ip dhcp client route track number Configure the DCHP client to associate any added routes with the
specified track number. Valid numbers are from 1 to 500.
Command Purpose
Step 5 ip address dhcp Acquire an IP address on an Ethernet interface from DHCP.
Step 6 exit Return to global configuration mode.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip sla operation-number Begin configuring a Cisco IP SLAs operation and enter IP SLA
configuration mode.
Step 3 icmp-echo {destination-ip-address | Configure a Cisco IP SLAs end-to-end ICMP echo response time
destination hostname [source- ipaddr operation and enter IP SLAs ICMP echo configuration mode.
{ip-address | hostname source-interface
interface-id]
Step 4 timeout milliseconds Set the amount of time for which the operation waits for a response
from its request packet.
Step 5 frequency seconds Set the rate at which the operation is sent into the network.
Step 6 threshold milliseconds Set the rising threshold (hysteresis) that generates a reaction event
and stores history information for the operation.
Step 7 exit Exit IP SLAs ICMP echo configuration mode.
Step 8 ip sla schedule operation-number [life Configure the scheduling parameters for a single IP SLAs operation.
{forever | seconds}] start-time time |
pending | now | after time] [ageout
seconds] [recurring]
Step 9{ track object-number rtr operation-number Track the state of a Cisco IOS IP SLAs operation and enter tracking
{state | reachability} configuration mode.
Step 10 end Return to privileged EXEC mode.
Step 11 show track object-number Display tracking information to verify the configuration.
Step 12 copy running-config startup-config (Optional) Save your entries in the configuration file.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 access-list access-list-number Define an extended IP access list. Configure any optional
characteristics.
Step 3 route-map map-tag [permit | deny] Enter route-map configuration mode and define conditions for
[sequence-number] redistributing routes from one routing protocol to another.
Step 4 match ip address {access-list number | Distribute any routes that have a destination network number address
access-list name} that is permitted by a standard or extended access list or performs
policy routing on packets. You can enter multiple numbers or names.
Step 5 set ip next-hop dynamic dhcp For DHCP networks only. Set the next hop to the gateway that was
most recently learned by the DHCP client.
Step 6 set interface interface-id For static routing networks only. Indicate where to send output
packets that pass a match clause of a route map for policy routing.
Step 7 exit Exit route-map configuration mode.
Step 8 ip local policy route-map map-tag Identify a route map to use for local policy routing.
Step 9{ ip route prefix mask {ip-address | For static routing networks only. Establish static routes.
interface-id [ip-address]} [distance] [name] Entering track track-number specifies that the static route is installed
[permanent | track track-number] [tag tag] only if the configured track object is up.
Command Purpose
show ip route track table Display information about the IP route track table.
show track [object-number] Display information about the all tracking lists or
the specified list.
show track brief Display a single line of tracking information
output.
show track interface [brief] Display information about tracked interface
objects.
show track ip [object-number] [brief] route Display information about tracked IP-route
objects.
show track resolution Display the resolution of tracked parameters.
show track timers Display tracked polling interval timers.
Ethernet Operations, Administration, and Maintenance (OAM) is a protocol for installing, monitoring,
and troubleshooting Ethernet networks to increase management capability within the context of the
overall Ethernet infrastructure. The Catalyst 3750 Metro switch supports IEEE 802.1ag Connectivity
Fault Management (CFM), Ethernet Local Management Interface (E-LMI), and IEEE 802.3ah Ethernet
OAM discovery, link monitoring, remote fault detection, and remote loopback. It also supports IP
Service Level Agreements (SLAs) for CFM, and ITU-T Y.1731 fault management. Ethernet OAM
manager controls the interworking between any two of the protocols (CFM, E-LMI, and OAM).
This chapter provides information about configuring CFM, E-LMI, and the Ethernet OAM protocol. It
defines the differences between the ratified CFM 802.1ag standard (draft 8.1) and the previous version
supported on the switch in Cisco IOS (draft 1.0). It also includes configuration information for CFM
ITU-TY.1731 fault management support in this release.
For complete command and configuration information for Ethernet OAM,CFM, E-LMI, and Y.1731, see
the Cisco IOS Carrier Ethernet Configuration Guide at this URL:
http://www.cisco.com/en/US/products/ps6922/products_installation_and_configuration_guides_list.ht
ml
For complete syntax of the commands used in this chapter, see the command reference for this release
and the Cisco IOS Carrier Ethernet Command Reference at this URL:
http://www.cisco.com/en/US/docs/ios/cether/command/reference/ce_book.html
Note The Service Diagnostics 2.0 C FM diagnostic script is part of the 12.2(52)SE release. The script is
available for download at:
http://www.cisco.com/en/US/prod/iosswrel/ps6537/ps6555/ps9424/cisco_ios_service_diagnostics_scripts.html
CFM Domain
A CFM maintenance domain is a management space on a network that is owned and operated by a single
entity and defined by a set of ports internal to it, but at its boundary. You assign a unique maintenance
level (from 0 to 7) to define the hierarchical relationship between domains. The larger the domain, the
higher the level. For example, as shown in Figure 43-1, a service-provider domain would be larger than
an operator domain and might have a maintenance level of 6, while the operator domain maintenance
level is 3 or 4.
As shown in Figure 43-2, domains cannot intersect or overlap because that would require management
by more than one entity, which is not allowed. Domains can touch or nest (if the outer domain has a
higher maintenance level than the nested domain). Nesting domains is useful when a service provider
contract with one or more operators to provide Ethernet service. Each operator has its own maintenance
domain and the service provider domain is a superset of the operator domains. Maintenance levels of
nesting domains should be communicated among the administrating organizations. CFM exchanges
messages and performs operations on a per-domain basis.
Operator Domains
Operator 1 Operator 2
CE 1 PE 1 PE 2 PE 3 PE 4 CE 2
157281
Level 3
157282
Touching Domains OK Nested Domains OK Intersecting Domains
Not Allowed
Note CFM draft 1 referred to inward and outward-facing MEPs. CFM draft 8.1 refers to up and down MEPs,
respectively. This document uses the CFM 8.1 terminology for direction.
CFM draft 1 supported only up MEPs on a per-port or per-VLAN basis. CFM 802.1ag supports up
and down per-VLAN MEPs, as well as port MEPs, which are untagged down MEPs that are not
associated with a VLAN. Port MEPs are configured to protect a single hop and used to monitor link
state through CFM. If a port MEP is not receiving continuity check messages from its peer (static
remote MEP), for a specified interval, the port is put into an operational down state in which only
CFM and OAM packets pass through, and all other data and control packets are dropped.
– An up MEP sends and receives CFM frames through the relay function. It drops all CFM frames
at its level or lower that come from the wire side, except traffic going to the down MEP. For
CFM frames from the relay side, it processes the frames at its level and drops frames at a lower
level. The MEP transparently forwards all CFM frames at a higher level, regardless of whether
they are received from the relay or wire side. If the port on which MEP is configured is blocked
by STP, the MEP can still send or receive CFM messages through the relay function. CFM runs
at the provider maintenance level (UPE-to-UPE), specifically with up MEPs at the user network
interface (UNI).
– A down MEP sends and receives CFM frames through the wire connected to the port on which
the MEP is configured. It drops all CFM frames at its level or lower that come from the relay
side. For CFM frames from the wire side, it processes all CFM frames at its level and drops
CFM frames at lower levels except traffic going to the other lower-level down MEP. The MEP
transparently forwards all CFM frames at a higher level, regardless of whether they are received
from the relay or through the wire.
• Maintenance intermediate points (MIPs) are internal to a domain, not at the boundary, and respond
to CFM only when triggered by traceroute and loopback messages. They forward CFM frames
received from MEPs and other MIPs, drop all CFM frames at a lower level (unless MIP filtering is
enabled), and forward all CFM frames at a higher level and at a lower level and regardless of whether
they are received from the relay or wire side. When MIP filtering is enabled, the MIP drops CFM
frames at a lower level. MIPs also catalog and forward continuity check messages (CCMs), but do
not respond to them.
In the first draft of CFM, MIP filtering was always enabled. In draft 8.1, MIP filtering is disabled
by default, and you can configure it to be enabled or disabled. When MIP filtering is disabled, all
CFM frames are forwarded.
You can manually configure a MIP or configure the switch to automatically create a MIP. You can
configure a MEP without a MIP. In case of a configuration conflict, manually created MIPs take
precedence over automatically created MIPs.
If port on which the MEP is configured is blocked by Spanning-Tree Protocol (STP), the MIP can
receive and might respond to CFM messages from both the wire and relay side, but cannot forward
any CFM messages. This differs from CFM draft 1, where STP blocked ports could not send or
receive CFM messages.
CFM Messages
CFM uses standard Ethernet frames distinguished by EtherType or (for multicast messages) by MAC
address. All CFM messages are confined to a maintenance domain and to a service-provider VLAN
(S-VLAN). These CFM messages are supported:
• Continuity Check (CC) messages—multicast heartbeat messages exchanged periodically between
MEPs that allow MEPs to discover other MEPs within a domain and allow MIPs to discover MEPs.
CC messages are configured to a domain or VLAN. Enter the continuity-check Ethernet service
configuration command to enable CCM.
The default continuity check message (CCM) interval on the switch is 10 seconds. You can set it to
be 100 ms, 1 second, 1 minute, or 10 minutes by entering the continuity-check interval Ethernet
service mode command. Because faster CCM rates are more CPU intensive, we do not recommend
configuring a large number of MEPs running at 100 ms intervals.
• Loopback messages—unicast or multicast frames transmitted by a MEP at administrator request to
verify connectivity to a particular maintenance point, indicating if a destination is reachable. A
loopback message is similar to an Internet Control Message Protocol (ICMP) ping message. Refer
to the ping ethernet privileged EXEC command.
• Traceroute messages—multicast frames transmitted by a MEP at administrator request to track the
path (hop-by-hop) to a destination MEP. Traceroute messages are similar in concept to UDP
traceroute messages. Refer to the traceroute ethernet privileged EXEC command.
Note If you are running CFM draft 1 and upgrade to a software version that supports CFM 802.1ag, the switch
automatically transfers the draft 1 configuration to the standard.
You can manually configure individual Ethernet ping or jitter operations. You can also configure an IP
SLAs automatic Ethernet operation that queries the CFM database for all MEPs in a given maintenance
domain and VLAN. The operation then automatically creates individual Ethernet ping or jitter
operations based on the discovered MEPs.
Because IP SLAs is a Cisco proprietary feature, interoperability between CFM draft 1 and CFM 802.1ag
is handled automatically by the switch.
For more information about IP SLAs operation with CFM, see the IP SLAs for Metro-Ethernet feature
module at this URL:
http://www.cisco.com/en/US/docs/ios/12_2sr/12_2srb/feature/guide/sr_meth.html
Note You do not need to enter the ethernet cfm ieee global configuration command to configure the CFM
version as IEEE 802.1ag. If you are running Cisco IOS Release 12.2(52)SE or later, the CFM version is
always 802.1ag and the command is automatically generated when you enable CFM.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ethernet cfm global Globally enable Ethernet CFM on the switch.
Step 3 ethernet cfm traceroute cache [size entries | (Optional) Configure the CFM traceroute cache. You can
hold-time minutes] set a maximum cache size or hold time.
• (Optional) For size, enter the cache size in number of
entry lines. The range is from 1 to 4095; the default is
100 lines.
• (Optional) For hold-time, enter the maximum cache
hold time in minutes. The range is from 1 to 65535; the
default is 100 minutes.
Step 4 ethernet cfm mip auto-create level level-id vlan (Optional) Configure the switch to automatically create
vlan-id MIPs for VLAN IDS that are not associated with specific
maintenance associations at the specified level. The level
range is 0 to 7.
Note Configure MIP auto-creation only for VLANs that
MIPs should monitor. Configuring for all VLANs
can be CPU and memory-intensive.
Step 5 ethernet cfm mip filter (Optional) Enable MIP filtering, which means that all CFM
frames at a lower level are dropped. The default is disabled.
Step 6 ethernet cfm domain domain-name level level-id Define a CFM domain, set the domain level, and enter
ethernet-cfm configuration mode for the domain. The
maintenance level number range is 0 to 7.
Step 7 id {mac-address domain_number | dns name | null} (Optional) Assign a maintenance domain identifier.
• mac-address domain_number—Enter the MAC
address and a domain number. The number can be from
0 to 65535.
• dns name—Enter a DNS name string. The name can be
a maximum of 43 characters.
• null—Assign no domain name.
Command Purpose
Step 8 service {ma-name | ma-number | vpn-id vpn} {vlan Define a customer service maintenance association (MA)
vlan-id [direction down] | port} name or number or VPN ID to be associated with the
domain, a VLAN ID or port MEP, and enter
ethernet-cfm-service configuration mode.
• ma-name—a string of no more than 100 characters that
identifies the MAID.
• ma-number—a value from 0 to 65535.
• vpn-id vpn—enter a VPN ID as the ma-name.
• vlan vlan-id—VLAN range is from 1 to 4094. You
cannot use the same VLAN ID for more than one
domain at the same level.
• (Optional) direction down—specify the service
direction as down.
• port—Configure port MEP, a down MEP that is
untagged and not associated with a VLAN.
Step 9 continuity-check Enable sending and receiving of continuity check
messages.
Step 10 continuity-check interval value (Optional) Set the interval at which continuity check
messages are sent. The available values are 100 ms,
1 second, 10 seconds, 1 minute and 10 minutes. The default
is 10 seconds.
Note Because faster CCM rates are more CPU-intensive,
we do not recommend configuring a large number
of MEPs running at 100 ms intervals.
Step 11 continuity-check loss-threshold threshold-value (Optional) Set the number of continuity check messages to
be missed before declaring that an MEP is down. The range
is 2 to 255; the default is 3.
Step 12 maximum meps value (Optional) Configure the maximum number of MEPs
allowed across the network. The range is from 1 to 65535.
The default is 100.
Step 13 sender-id {chassis | none} (Optional) Include the sender ID TLVs, attributes
containing type, length, and values for neighbor devices.
• chassis—Send the chassis ID (host name).
• none—Do not include information in the sender ID.
Step 14 mip auto-create [lower-mep-only | none] (Optional) Configure auto creation of MIPs for the service.
• lower-mep-only—Create a MIP only if there is a MEP
for the service in another domain at the next lower
active level.
• none —No MIP auto-create.
Step 15 exit Return to ethernet-cfm configuration mode.
Command Purpose
Step 16 mip auto-create [lower-mep-only] (Optional) Configure auto creation of MIPs for the domain.
• lower-mep-only—Create a MIP only if there is a MEP
for the service in another domain at the next lower
active level.
Step 17 mep archive-hold-time minutes (Optional) Set the number of minutes that data from a
missing maintenance end point is kept before it is purged.
The range is 1 to 65535; the default is 100 minutes.
Step 18 exit Return to global configuration mode.
Step 19 interface interface-id Specify an interface to configure, and enter interface
configuration mode.
Step 20 switchport mode trunk (Optional) Configure the port as a trunk port.
Step 21 ethernet cfm mip level level-id (Optional) Configure a customer level or service-provider
level maintenance intermediate point (MIP) for the
interface. The MIP level range is 0 to 7.
Note This step is not required if you have entered the
ethernet cfm mip auto-create global
configuration command or the mip auto-create
ethernet-cfm or ethernet-cfm-srv configuration
mode.
Step 22 ethernet cfm mep domain domain-name mpid Configure maintenance end points for the domain, and
identifier {vlan vlan-id | port} enter ethernet cfm mep mode.
• domain domain-name—Specify the name of the
created domain.
• mpid identifier—Enter a maintenance end point
identifier. The identifier must be unique for each
VLAN (service instance). The range is 1 to 8191.
• vlan vlan-id—Enter the service provider VLAN ID or
IDs as a VLAN-ID (1 to 4094), a range of VLAN-IDs
separated by a hyphen, or a series of VLAN IDs
separated by comma.
• port—Configure port MEP.
Step 23 cos value (Optional) Specify the class of service (CoS) value to be
sent with the messages. The range is 0 to 7.
Step 24 end Return to privileged EXEC mode.
Step 25 show ethernet cfm maintenance-points {local | Verify the configuration.
remote}
Step 26 show ethernet cfm errors [configuration] (Optional) Display the configuration error list.
Step 27 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no versions of the commands to remove the configuration or return to the default configurations.
This is an example of the basic CFM configuration:
Switch(config)# ethernet cfm ieee
Switch(config)# ethernet cfm global
Switch(config)# ethernet cfm domain abc level 3
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ethernet cfm mep crosscheck start-delay delay Configure the number of seconds that the device waits for
remote MEPs to come up before the crosscheck is started.
The range is 1 to 65535; the default is 30 seconds.
Step 3 ethernet cfm domain domain-name level level-id Define a CFM domain, set the domain level, and enter
ethernet-cfm configuration mode for the domain. The
maintenance level number range is 0 to 7.
Step 4 service {ma-name | ma-number | vpn-id vpn} {vlan Define a customer service maintenance association name
vlan-id} or number or VPN ID to be associated with the domain, and
a VLAN ID, and enter ethernet-cfm-service configuration
mode.
• ma-name—a string of no more than 100 characters that
identifies the MAID.
• ma-number—a value from 0 to 65535.
• vpn-id vpn—enter a VPN ID as the ma-name.
• vlan vlan-id—VLAN range is from 1 to 4094. You
cannot use the same VLAN ID for more than one
domain at the same level.
Step 5 mep mpid identifier Define the MEP maintenance end point identifier in the
domain and service. The range is 1 to 8191
Step 6 end Return to privileged EXEC mode.
Step 7 ethernet cfm mep crosscheck {enable | disable} Enable or disable CFM crosscheck for one or more VLANs
domain domain-name {vlan {vlan-id | any} | port} or a port MEP in the domain.
• domain domain-name—Specify the name of the
created domain.
• vlan {vlan-id | any}—Enter the service provider
VLAN ID or IDs as a VLAN-ID (1 to 4094), a range of
VLAN-IDs separated by a hyphen, or a series of
VLAN IDs separated by comma. Enter any for any
VLAN.
• port—Identify a port MEP.
Step 8 show ethernet cfm maintenance-points remote Verify the configuration.
crosscheck
Command Purpose
Step 9 show ethernet cfm errors [configuration] Enter this command after you enable CFM crosscheck to
display the results of the crosscheck operation. Enter the
configuration keyword to display the configuration error
list.
Step 10 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no form of each command to remove a configuration or to return to the default settings.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ethernet cfm domain domain-name level level-id Define a CFM domain, set the domain level, and enter
ethernet-cfm configuration mode for the domain. The
maintenance level number range is 0 to 7.
Step 3 service {ma-name | ma-number | vpn-id vpn} {vlan Define a customer service maintenance association name
vlan-id [direction down] | port} or number or a VPN ID to be associated with the domain,
and a VLAN ID or peer MEP, and enter
ethernet-cfm-service configuration mode.
• ma-name—a string of no more than 100 characters that
identifies the MAID.
• ma-number—a value from 0 to 65535.
• vpn-id—enter a VPN ID as the ma-name.
• vlan vlan-id—VLAN range is from 1 to 4094. You
cannot use the same VLAN ID for more than one
domain at the same level.
• (Optional) direction down—specify the service
direction as down.
• port—Configure port MEP, a down MEP that is
untagged and not associated with a VLAN.
Step 4 continuity-check Enable sending and receiving of continuity check
messages.
Step 5 mep mpid identifier Define the static remote maintenance end point identifier.
The range is 1 to 8191
Step 6 continuity-check static rmep Enable checking of the incoming continuity check message
from a remote MEP that is configured in the MEP list.
Step 7 end Return to privileged EXEC mode.
Step 8 show ethernet cfm maintenance-points remote Verify the configuration.
static
Command Purpose
Step 9 show ethernet cfm errors [configuration] Enter this command after you enable CFM crosscheck to
display the results of the crosscheck operation. Enter the
configuration keyword to display the configuration error
list.
Step 10 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no form of each command to remove a configuration or to return to the default settings.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ethernet cfm domain domain-name level level-id Define a CFM domain, set the domain level, and enter
ethernet-cfm configuration mode for the domain. The
maintenance level number range is 0 to 7.
Step 3 service {ma-name | ma-number | vpn-id} port Define a customer service maintenance association name
or number or VPN ID to be associated with the domain,
define a port MEP, and enter ethernet-cfm-service
configuration mode.
• ma-name—a string of no more than 100 characters that
identifies the MAID.
• ma-number—a value from 0 to 65535.
• vpn-id vpn—enter a VPN ID as the ma-name.
Step 4 mep mpid identifier Define the static remote maintenance end point identifier in
the domain and service. The range is 1 to 8191
Step 5 continuity-check Enable sending and receiving of continuity check
messages.
Step 6 continuity-check interval value (Optional) Set the interval at which continuity check
messages are sent. The available values are 100 ms,
1 second, 10 seconds, 1 minute and 10 minutes. The default
is 10 seconds.
Note Because faster CCM rates are more CPU-intensive,
we do not recommend configuring a large number
of MEPs running at 100 ms intervals.
Step 7 continuity-check loss-threshold threshold-value (Optional) Set the number of continuity check messages to
be missed before declaring that an MEP is down. The range
is 2 to 255; the default is 3.
Command Purpose
Step 8 continuity-check static rmep Enable checking of the incoming continuity check message
from a remote MEP that is configured in the MEP list.
Step 9 exit Return to ethernet-cfm configuration mode.
Step 10 exit Return to global configuration mode.
Step 11 interface interface-id Identify the port MEP interface and enter interface
configuration mode.
Step 12 ethernet cfm mep domain domain-name mpid Configure the interface as a port MEP for the domain.
identifier port
• domain domain-name—Specify the name of the
created domain.
• mpid identifier—Enter a maintenance end point
identifier. The identifier must be unique for each
VLAN (service instance). The range is 1 to 8191.
Step 13 end Return to privileged EXEC mode.
Step 14 show ethernet cfm maintenance-points remote Verify the configuration.
static
Step 15 show ethernet cfm errors [configuration] Enter this command after you enable CFM crosscheck to
display the results of the crosscheck operation. Enter the
configuration keyword to display the configuration error
list.
Step 16 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no form of each command to remove a configuration or to return to the default settings.
This is a sample configuration for a port MEP:
Switch(config)# ethernet cfm domain abc level 3
Switch(config-ecfm)# service PORTMEP port
Switch(config-ecfm-srv)# mep mpid 222
Switch(config-ecfm-srv)# continuity-check
Switch(config-ecfm-srv)# continuity-check static rmep
Switch(config-ecfm-srv)# exit
Switch(config-ecfm)# exit
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# ethernet cfm mep domain abc mpid 111 port
Switch(config-if)# end
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 snmp-server enable traps ethernet cfm cc [mep-up] (Optional) Enable Ethernet CFM continuity check traps.
[mep-down] [config] [loop] [cross-connect]
Step 3 snmp-server enable traps ethernet cfm crosscheck (Optional) Enable Ethernet CFM crosscheck traps.
[mep-unknown] [mep-missing] [service-up]
Command Purpose
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no form of each command to remove a configuration or to return to the default settings.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ethernet cfm alarm notification {all | error-xcon | Globally enable Ethernet CFM fault alarm notification for
mac-remote-error-xcon | none | remote-error-xcon the specified defects:
| xcon}
• all—report all defects.
• error-xcon—Report only error and connection
defects.
• mac-remote-error-xcon—Report only MAC-address,
remote, error, and connection defects.
• none—Report no defects.
• remote-error-xcon—Report only remote, error, and
connection defects.
• xcon—Report only connection defects.
Step 3 ethernet cfm alarm delay value (Optional) Set a delay period before a CFM fault alarm is
sent. The range is 2500 to 10000 milliseconds (ms). The
default is 2500 ms.
Step 4 ethernet cfm alarm reset value (Optional) Specify the time period before the CFM fault
alarm is reset. The range is 2500 to 10000 milliseconds
(ms). The default is 10000 ms.
Step 5 ethernet cfm logging alarm ieee Configure the switch to generate system logging messages
for the alarms.
Step 6 interface interface-id (Optional) Specify an interface to configure, and enter
interface configuration mode.
Command Purpose
Step 7 ethernet cfm mep domain domain-name mpid Configure maintenance end points for the domain, and
identifier vlan vlan-id enter ethernet cfm interface mep mode.
• domain domain-name—Specify the name of the
created domain.
• mpid identifier—Enter a maintenance end point
identifier. The identifier must be unique for each
VLAN (service instance). The range is 1 to 8191.
• vlan vlan-id—Enter the service provider VLAN ID or
IDs as a VLAN-ID (1 to 4094), a range of VLAN-IDs
separated by a hyphen, or a series of VLAN IDs
separated by comma.
Step 8 ethernet cfm alarm notification {all | error-xcon | (Optional) Enable Ethernet CFM fault alarm notification
mac-remote-error-xcon | none | remote-error-xcon for the specified defects on the interface.
| xcon}
Note The Ethernet CFM interface MEP alarm
configuration takes precedence over the global
configuration.
Step 9 ethernet cfm alarm {delay value | reset value} (Optional) Set an alarm delay period or a reset period.
Note The Ethernet CFM interface MEP alarm
configuration takes precedence over the global
configuration.
Step 10 end Return to privileged EXEC mode.
Step 11 show running-config Verify your entries.
Step 12 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no form of each command to remove a configuration or to return to the default settings.
Note When you configure the Catalyst 3750 Metro switch for a class of service (CoS) probe, you must first
globally enable QoS by entering the mls qos global configuration command.
For detailed information about configuring IP SLAs operations, see the Cisco IOS IP SLAs
Configuration Guide, Release 12.4T at this URL:
http://www.cisco.com/en/US/docs/ios/ipsla/configuration/guide/12_4t/sla_12_4t_book.html
For detailed information about IP SLAs commands, see the command reference at this URL:
http://www.cisco.com/en/US/docs/ios/ipsla/command/reference/sla_book.html
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip sla operation-number Create an IP SLAs operation, and enter IP SLAs
configuration mode.
Step 3 ethernet echo mpid identifier domain domain-name Configure the IP SLAs operation as an echo (ping) or jitter
vlan vlan-id operation, and enter IP SLAs Ethernet echo configuration
mode.
• Enter echo for a ping operation or jitter for a jitter
operation.
or
• For mpid identifier, enter a maintenance endpoint
identifier. The identifier must be unique for each
VLAN (service instance). The range is 1 to 8191.
ethernet jitter mpid identifier domain domain-name • For domain domain-name, enter the CFM domain
vlan vlan-id [interval interpacket-interval] name.
[num-frames number-of frames transmitted] • For vlan vlan-id, the VLAN range is from 1 to 4095.
• (Optional—for jitter only) Enter the interval between
sending of jitter packets.
• (Optional—for jitter only) Enter the num-frames and
the number of frames to be sent.
Step 4 cos cos-value (Optional) Set a class of service value for the operation.
Before configuring the cos parameter on the Catalyst 3750
Metro switch, you must globally enable QoS by entering
the mls qos global configuration command.
Step 5 frequency seconds (Optional) Set the rate at which the IP SLAs operation
repeats. The range is from 1 to 604800 seconds; the default
is 60 seconds.
Step 6 history history-parameter (Optional) Specify parameters for gathering statistical
history information for the IP SLAs operation.
Step 7 owner owner-id (Optional) Configure the SNMP owner of the IP SLAs
operation.
Step 8 request-data-size bytes (Optional) Specify the protocol data size for an IP SLAs
request packet. The range is from 0 to the maximum size
allowed by the protocol being used; the default is 66 bytes.
Step 9 tag text (Optional) Create a user-specified identifier for an IP SLAs
operation.
Command Purpose
Step 10 threshold milliseconds (Optional) Specify the upper threshold value in
milliseconds (ms0 for calculating network monitoring
statistics. The range is 0 to 2147483647; the default is
5000.
Step 11 timeout milliseconds (Optional) Specify the amount of time in ms that the IP
SLAs operation waits for a response from its request
packet. The range is 0 to 604800000; the default value is
5000.
Step 12 exit Return to global configuration mode.
Step 13 ip sla schedule operation-number [ageout seconds] Schedule the time parameters for the IP SLAs operation.
[life {forever | seconds}] [recurring] [start-time
• operation-number—Enter the IP SLAs operation
{hh:mm {:ss} [month day | day month] | pending |
number.
now | after hh:mm:ss}]
• (Optional) ageout seconds—Enter the number of
seconds to keep the operation in memory when it is not
actively collecting information. The range is 0 to
2073600 seconds. The default is 0 seconds.
• (Optional) life—Set the operation to run indefinitely
(forever) or for a specific number of seconds. The
range is from 0 to 2147483647. The default is 3600
seconds (1 hour)
• (Optional) recurring—Set the probe to be
automatically scheduled every day.
• (Optional) start-time—Enter the time for the
operation to begin collecting information:
– To start at a specific time, enter the hour, minute,
second (in 24-hour notation), and day of the
month.
– Enter pending to select no information collection
until a start time is selected.
– Enter now to start the operation immediately.
– Enter after hh:mm:ss to show that the operation
should start after the entered time has elapsed.
Step 14 end Return to privileged EXEC mode.
Step 15 show ip sla configuration [operation-number] Show the configured IP SLAs operation.
Step 16 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove an IP SLAs operation, enter the no ip sla operation-number global configuration command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip sla ethernet-monitor operation-number Begin configuration of an IP SLAs automatic Ethernet
operation, and enter IP SLAs Ethernet monitor
configuration mode.
Step 3 type echo domain domain-name vlan vlan-id Configure the automatic Ethernet operation to create echo
[exclude-mpids mp-ids] (ping) or jitter operation and enter IP SLAs Ethernet echo
configuration mode.
• Enter type echo for a ping operation or type jitter for
a jitter operation.
or
• For mpid identifier, enter a maintenance endpoint
identifier. The range is 1 to 8191.
• For domain domain-name, enter the CFM domain
type jitter domain domain-name vlan vlan-id name.
[exclude-mpids mp-ids] [interval • For vlan vlan-id, the VLAN range is from 1 to 4095.
interpacket-interval] [num-frames number-of frames
transmitted] • (Optional) Enter exclude-mpids mp-ids to exclude the
specified maintenance endpoint identifiers.
• (Optional—for jitter only) Enter the interval between
sending of jitter packets.
• (Optional—for jitter only) Enter the num-frames and
the number of frames to be sent.
Step 4 cos cos-value (Optional) Set a class of service value for the operation.
Before configuring the cos parameter on the Catalyst 3750
Metro switch, you must globally enable QoS by entering
the mls qos global configuration command.
Step 5 owner owner-id (Optional) Configure the SNMP owner of the IP SLAs
operation.
Step 6 request-data-size bytes (Optional) Specify the protocol data size for an IP SLAs
request packet. The range is from 0 to the maximum size
allowed by the protocol being used; the default is 66 bytes.
Step 7 tag text (Optional) Create a user-specified identifier for an IP SLAs
operation.
Step 8 threshold milliseconds (Optional) Specify the upper threshold value in
milliseconds for calculating network monitoring statistics.
The range is 0 to 2147483647; the default is 5000.
Step 9 timeout milliseconds (Optional) Specify the amount of time in milliseconds that
the IP SLAs operation waits for a response from its request
packet. The range is 0 to 604800000; the default value is
5000.
Command Purpose
Step 10 exit Return to global configuration mode.
Step 11 ip sla schedule operation-number [ageout seconds] Schedule the time parameters for the IP SLAs operation.
[life {forever | seconds}] [recurring] [start-time
• operation-number—Enter the IP SLAs operation
{hh:mm {:ss} [month day | day month] | pending |
number.
now | after hh:mm:ss}]
• (Optional) ageout seconds—Enter the number of
seconds to keep the operation in memory when it is not
actively collecting information. The range is 0 to
2073600 seconds. The default is 0 seconds.
• (Optional) life—Set the operation to run indefinitely
(forever) or for a specific number of seconds. The
range is from 0 to 2147483647. The default is 3600
seconds (1 hour)
• (Optional) recurring—Set the probe to be
automatically scheduled every day.
• (Optional) start-time—Enter the time for the
operation to begin collecting information:
– To start at a specific time, enter the hour, minute,
second (in 24-hour notation), and day of the
month.
– Enter pending to select no information collection
until a start time is selected.
– Enter now to start the operation immediately.
– Enter after hh:mm:ss to show that the operation
should start after the entered time has elapsed.
Step 12 end Return to privileged EXEC mode.
Step 13 show ip sla configuration [operation-number] Show the configured IP SLAs operation.
Step 14 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove an IP SLAs operation, enter the no ip sla operation-number global configuration command.
Note The switch supports only manual configuration of MIPs. It does not support MIP autocreation on
C-VLANs.
Y.1731 Terminology
• Server MEP—the combination of the server layer termination function and server or Ethernet
adaptation layer termination function or server or Ethernet adaptation function, where the server
layer termination function is expected to run OAM mechanisms specific to the server layer. The
supported mechanisms are link up, link down, and 802.3ah.
• Server layer—a virtual MEP layer capable of detecting fault conditions.
• Defect conditions:
– Loss of continuity (LOC): the MEP stopped receiving CCM frames from a peer MEP
– Mismerge: the MEP received a CCM frame with a correct maintenance level (matching the MEP
level) but an incorrect maintenance ID.
– Unexpected MEP: the MEP received a CCM frame with the correct maintenance level
(matching the MEP’s level) and correct maintenance ID, but an unexpected MEP ID.
– Unexpected maintenance level: the MEP received a CCM frame with an incorrect maintenance
level.
– Unexpected period: the MEP received a CCM frame with a correct maintenance level, a correct
maintenance ID, a correct MEP ID, but a different transmission period field.
• Signal fail—the MEP declares a signal fail condition when it detects a defect condition.
Note Although the configuration is allowed, you should not configure AIS in networks running STP. An STP
configuration might cause AIS interruption or redirection.
When a MEP or a service MEP (SMEP) detects a connectivity fault at a specific maintenance association
level, it multicasts AIS frames in the direction away from the detected failure at the client maintenance
association level. The frequency of AIS frame transmission is based on the AIS transmission period. The
first AIS frame is always sent immediately following the detection of the defect condition. We
recommend a transition period of 1 second in a network of only a few VLANs to ensure that the first AIS
frame is sent immediately following error detection. We recommend a 60-second interval in a network
of multiple (up to 4094) VLANs to prevent stressing the network with 1-second transmissions.
A MEP that receives a frame with ETH-AIS information cannot determine the specific server with the
defect condition or the set of peer MEPs for which it should suppress alarms. Therefore, it suppresses
alarms for all peer MEPs, whether or not they are connected.
When a MEP receives an AIS frame, it examines it to be sure that the Maintenance Entity Group (MEG)
level matches its own MEG and then detects the AIS default condition. (A MEG is Y.1731 terminology
for maintenance association in 802.1ag.) After this detection, if no AIS frames are received for an
interval of 3.5 times the AIS transmission period, the MEP clears the AIS defect condition. For example,
if the AIS timer is set for 60 seconds, the AIS timer period expires after 3.5 times 60, or 210 seconds.
The AIS condition is terminated when a valid CCM is received with all error conditions cleared or when
the AIS period timer expires (the default time is 60 seconds).
When you configure ETH-AIS or ETH-LCK, you must configure CFM before ETH-AIS or ETH-LCK
is operational.
ETH-RDI is set automatically when continuity check messages are enabled.
Configuring ETH-AIS
Beginning in privileged EXEC mode, follow these steps to configure Ethernet AIS on a switch:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ethernet cfm ais link-status global Configure AIS-specific SMEP commands by entering
config-ais-link-cfm mode.
Step 3 level level-id Configure the maintenance level for sending AIS frames
transmitted by the SMEP. The range is 0 to 7.
or or
disable Disable generation of ETH-AIS frames.
Step 4 period value Configure the SMEP AIS transmission period interval.
Allowable values are 1 second or 60 seconds.
Step 5 exit Return to global configuration mode.
Step 6 ethernet cfm domain domain-name level level-id Define a CFM domain, set the domain level, and enter
ethernet-cfm configuration mode for the domain. The
maintenance level number range is 0 to 7.
Step 7 service {ma-name | ma-number | vpn-id vpn} {vlan Define a customer service maintenance association (MA)
vlan-id [direction down] | port} name or number to be associated with the domain, or a
VLAN ID or VPN-ID, and enter ethernet-cfm-service
configuration mode.
• ma-name—a string of no more than 100 characters that
identifies the MAID.
• ma-number—a value from 0 to 65535.
• vpn-id—enter a VPN ID as the ma-name.
• vlan vlan-id—VLAN range is from 1 to 4094. You
cannot use the same VLAN ID for more than one
domain at the same level.
• (Optional) direction down—specify the service
direction as down.
• port—Configure port MEP, a down MEP that is
untagged and not associated with a VLAN.
Step 8 ais level level-id (Optional) Configure the maintenance level for sending
AIS frames transmitted by the MEP. The range is 0 to 7.
Step 9 ais period value (Optional) Configure the MEP AIS transmission period
interval. Allowable values are 1 second or 60 seconds.
Step 10 ais expiry-threshold value (Optional) Set the expiring threshold for the MA as an
integer. The range is 2 to 255. The default is 3.5.
Command Purpose
Step 11 no ais suppress-alarms (Optional) Override the suppression of redundant alarms
when the MEP goes into an AIS defect condition after
receiving an AIS message.
Step 12 exit Return to ethernet-cfm configuration mode.
Step 13 exit Return to global configuration mode.
Step 14 interface interface-id Specify an interface ID, and enter interface configuration
mode.
Step 15 [no] ethernet cfm ais link-status Enable or disable sending AIS frames from the SMEP on
the interface.
Step 16 ethernet cfm ais link-status period value Configure the ETH-AIS transmission period generated by
the SMEP on the interface. Allowable values are 1 second
or 60 seconds.
Step 17 ethernet cfm ais link-status level level-id Configure the maintenance level for sending AIS frames
transmitted by the SMEP on the interface. The range is 0 to
7.
Step 18 end Return to privileged EXEC mode.
Step 19 show ethernet cfm smep [interface interface-id] Verify the configuration.
Step 20 show ethernet cfm error Display received ETH-AIS frames and other errors.
Step 21 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no form of the commands to return to the default configuration or to remove a configuration. To
disable the generation of ETH-AIS frames, enter the disable config-ais-link-cfm mode command.
This is an example of the output from the show ethernet cfm smep command when Ethernet AIS has
been enabled:
Switch# show ethernet cfm smep
SMEP Settings:
--------------
Interface: GigabitEthernet1/0/3
LCK-Status: Enabled
LCK Period: 60000 (ms)
Level to transmit LCK: Default
AIS-Status: Enabled
AIS Period: 60000 (ms)
Level to transmit AIS: Default
Defect Condition: AIS
Configuring ETH-LCK
Beginning in privileged EXEC mode, follow these steps to configure Ethernet locked signal on a switch:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ethernet cfm lck link-status global Configure SMEP LCK commands by entering
config-lck-link-cfm mode.
Command Purpose
Step 3 level level-id Configure the maintenance level for sending ETH-LCK
frames transmitted by the SMEP. The range is 0 to 7.
or or
disable Disable generation of ETH-LCK frames.
Step 4 period value Configure the SMEP ETH-LCK frame transmission period
interval. Allowable values are 1 second or 60 seconds.
Step 5 exit Return to global configuration mode.
Step 6 ethernet cfm domain domain-name level level-id Define a CFM domain, set the domain level, and enter
ethernet-cfm configuration mode for the domain. The
maintenance level number range is 0 to 7.
Step 7 service {ma-name | ma-number | vpn-id vpn} {vlan Define a customer service maintenance association name
vlan-id [direction down] | port} or number to be associated with the domain, or a VLAN ID
or VPN-ID, and enter ethernet-cfm-service configuration
mode.
• ma-name—a string of no more than 100 characters that
identifies the MAID.
• ma-number—a value from 0 to 65535.
• vpn-id—enter a VPN ID as the ma-name.
• vlan vlan-id—VLAN range is from 1 to 4094. You
cannot use the same VLAN ID for more than one
domain at the same level.
• (Optional) direction down—specify the service
direction as down.
• port—Configure port MEP, a down MEP that is
untagged and not associated with a VLAN.
Step 8 lck level level-id (Optional) Configure the maintenance level for sending
ETH-LCK frames sent by the MEP. The range is 0 to 7.
Step 9 lck period value (Optional) Configure the MEP ETH-LCK frame
transmission period interval. Allowable values are 1 second
or 60 seconds.
Step 10 lck expiry-threshold value (Optional) Set the expiring threshold for the MA. The
range is 2 to 255. The default is 3.5.
Step 11 exit Return to ethernet-cfm configuration mode.
Step 12 exit Return to global configuration mode.
Step 13 interface interface-id Specify an interface ID, and enter interface configuration
mode.
Step 14 [no] ethernet cfm lck link-status Enable or disable sending ETH-LCK frames from the
SMEP on the interface.
Step 15 ethernet cfm lck link-status period value Configure the ETH-LCK transmission period generated by
the SMEP on the interface. Allowable values are 1 second
or 60 seconds.
Command Purpose
Step 16 ethernet cfm lck link-status level level-id Configure the maintenance level for sending ETH-LCK
frames sent by the SMEP on the interface. The range is 0 to
7.
Step 17 end Return to privileged EXEC mode.
Step 18 ethernet cfm lck start mpid local-mpid domain (Optional) Put a MEP in LCK condition.
domain-name vlan vlan-id [drop l2-bpdu]
• The mpid local-mpid domain domain-name vlan
vlan-id identify the MEP.
• (Optional) drop l2-bpdu specifies that the switch
should drop all data frames, all Layer 3 control traffic,
and all Layer 2 BPDUs except CFM frames for that
MEP. If not entered, the switch drops only data frames
and Layer 3 control frames.
Step 19 ethernet cfm lck start interface interface-id (Optional) Put an interface in LCK condition.
direction {up | down} [drop l2-bpdu]
• interface interface-id—Specify the interface to be put
in LCK condition.
• direction inward—The LCK is in the direction toward
the relay; that is, within the switch.
• direction outward—The LCK is in the direction of
the wire.
• (Optional) drop l2-bpdu specifies that all Layer 2
BPDUs except CFM frames, all data frames, and all
Layer 3 control traffic are dropped for that MEP. If not
entered, only data frames and Layer 3 control frames
are dropped.
Step 20 show ethernet cfm smep [interface interface-id] Verify the configuration.
Step 21 show ethernet cfm error Display received ETH-LCK frames.
Step 22 copy running-config startup-config (Optional) Save your entries in the configuration file.
To put a MEP out of LCK condition, enter the ethernet cfm lck stop mpid local-mpid domain
domain-name vlan vlan-id privileged EXEC command. To put an interface out of LCK condition, enter
the ethernet cfm lck start interface interface-id direction {inward | outward} privileged EXEC
command.
This is an example of the output from the show ethernet cfm smep command when Ethernet LCK has
been enabled:
Switch# show ethernet cfm smep
SMEP Settings:
--------------
Interface: GigabitEthernet1/0/3
LCK-Status: Enabled
LCK Period: 60000 (ms)
Level to transmit LCK: Default
AIS-Status: Enabled
AIS Period: 60000 (ms)
Level to transmit AIS: Default
Defect Condition: AIS
Command Purpose
clear ethernet cfm ais domain domain-name Clear MEPs with matching domain and VLAN ID out of AIS defect
mpid id {vlan vlan-id | port} condition.
clear ethernet cfm ais link-status interface Clear a SMEP out of AIS defect condition.
interface-id
clear ethernet cfm error Clear all CFM error conditions, including AIS.
You can use the privileged EXEC commands in Table 43-1 to display Ethernet CFM information.
Command Purpose
show ethernet cfm domain [brief] Displays CFM domain information or brief domain information.
show ethernet cfm errors [configuration | Displays CFM continuity check error conditions logged on a device since
domain-id] it was last reset or the log was last cleared. When CFM crosscheck is
enabled, displays the results of the CFM crosscheck operation.
show ethernet cfm maintenance-points local Displays maintenance points configured on a device.
[detail | domain | interface | level | mep | mip]
show ethernet cfm maintenance-points remote Displays information about a remote maintenance point domains or levels or
[crosscheck | detail | domain | static] details in the CFM database.
show ethernet cfm mpdb Displays information about entries in the MIP continuity-check database.
show ethernet cfm smep [interface Displays Ethernet CFM SMEP information.
interface-id]
show ethernet cfm traceroute-cache Displays the contents of the traceroute cache.
show platform cfm Displays platform-independent CFM information.
This is an example of output from the show ethernet cfm domain brief command:
Switch# show ethernet cfm domain brief
Domain Name Index Level Services Archive(min)
level5 1 5 1 100
level3 2 3 1 100
test 3 3 3 100
name 4 3 1 100
test1 5 2 1 100
lck 6 1 1 100Total Services : 1
This is an example of output from the show ethernet cfm errors command:
Switch# show ethernet cfm errors
--------------------------------------------------------------------------------
MPID Domain Id Mac Address Type Id Lvl
MAName Reason Age
--------------------------------------------------------------------------------
6307 level3 0021.d7ee.fe80 Vlan 7 3
vlan7 Receive RDI 5s
This is an example of output from the show ethernet cfm maintenance-points local detail command:
Switch# show ethernet cfm maintenance-points local detail
Local MEPs:
----------
MPID: 7307
DomainName: level3
Level: 3
Direction: Up
Vlan: 7
Interface: Gi0/3
CC-Status: Enabled
CC Loss Threshold: 3
MAC: 0021.d7ef.0700
LCK-Status: Enabled
LCK Period: 60000(ms)
LCK Expiry Threshold: 3.5
Level to transmit LCK: Default
Defect Condition: No Defect
presentRDI: FALSE
AIS-Status: Enabled
AIS Period: 60000(ms)
AIS Expiry Threshold: 3.5
Level to transmit AIS: Default
Suppress Alarm configuration: Enabled
Suppressing Alarms: No
MIP Settings:
-------------
Local MIPs:
* = MIP Manually Configured
------------------------------------------------------------------------------
Level Port MacAddress SrvcInst Type Id
------------------------------------------------------------------------------
*5 Gi0/3 0021.d7ef.0700 N/A Vlan 2,7
This is an example of output from the show ethernet cfm traceroute command:
Switch# show ethernet cfm traceroute
Current Cache-size: 0 Hops
Max Cache-size: 100 Hops
Hold-time: 100 Minutes
You can use the privileged EXEC commands in Table 43-3 to display IP SLAs Ethernet CFM
information.
Command Purpose
show ip sla configuration [entry-number] Displays configuration values including all defaults for all IP SLAs
operations or a specific operation.
show ip sla ethernet-monitor configuration Displays the configuration of the IP SLAs automatic Ethernet operation.
[entry-number]
show ip sla statistics [entry-number | Display current or aggregated operational status and statistics.
aggregated | details]
OAM Features
These OAM features are defined by IEEE 802.3ah:
• Discovery identifies devices in the network and their OAM capabilities. It uses periodic OAM PDUs
to advertise OAM mode, configuration, and capabilities; PDU configuration; and platform identity.
An optional phase allows the local station to accept or reject the configuration of the peer OAM
entity.
• Link monitoring detects and indicates link faults under a variety of conditions and uses the event
notification OAM PDU to notify the remote OAM device when it detects problems on the link. Error
events include when the number of symbol errors, the number of frame errors, the number of frame
errors within a specified number of frames, or the number of error seconds within a specified period
exceed a configured threshold.
• Remote failure indication conveys a slowly deteriorating quality of an OAM entity to its peers by
communicating these conditions: Link Fault means a loss of signal, Dying Gasp means an
unrecoverable condition, and Critical Event means an unspecified vendor-specific critical event. The
switch can receive and process but not generate Link Fault or Critical Event OAM PDUs. It can
generate Dying Gasp OAM PDUs to show when Ethernet OAM is disabled, the interface is shut
down, the interface enters the error-disabled state, or the switch is reloading. It can respond to, but
not generate, Dying Gasp PDUs based on loss of power.
• Remote loopback mode to ensure link quality with a remote peer during installation or
troubleshooting. In this mode, when the switch receives a frame that is not an OAM PDU or a pause
frame, it sends it back on the same port. The link appears to the user to be in the up state. You can
use the returned loopback acknowledgement to test delay, jitter, and throughput.
OAM Messages
Ethernet OAM messages or PDUs are standard length, untagged Ethernet frames between 64 and 1518
bytes. They do not go beyond a single hop and have a maximum transmission rate of 10 OAM PDUs per
second. Message types are information, event notification, loopback control, or vendor-specific OAM
PDUs.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Define an interface to configure as an EOM interface, and
enter interface configuration mode.
Step 3 ethernet oam Enable Ethernet OAM on the interface.
Command Purpose
Step 4 ethernet oam [max-rate oampdus | min-rate seconds You can configure these optional OAM parameters:
| mode {active | passive} | timeout seconds]
• (Optional) Enter max-rate oampdus to configure the
maximum number of OAM PDUs sent per second. The
range is from 1 to 10.
• (Optional) Enter min-rate seconds to configure the
minimum transmission rate in seconds when one OAM
PDU is sent per second. The range is from 1 to 10.
• (Optional) Enter mode active to set OAM client mode
to active.
• (Optional) Enter mode passive to set OAM client
mode to passive.
Note When Ethernet OAM mode is enabled on two
interfaces passing traffic, at least one must be in the
active mode.
Enter the no ethernet oam interface configuration command to disable Ethernet OAM on the interface.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Define an interface to configure as an EOM interface, and
enter interface configuration mode.
Command Purpose
Step 3 ethernet oam remote-loopback {supported | Enable Ethernet remote loopback on the interface or set a
timeout seconds} loopback timeout period.
• Enter supported to enable remote loopback.
• Enter timeout seconds to set a remote loopback
timeout period. The range is from 1 to 10 seconds.
Step 4 end Return to privileged EXEC mode.
Step 5 ethernet oam remote-loopback {start | stop} Turn on or turn off Ethernet OAM remote loopback on an
{interface interface-id} interface.
Step 6 show ethernet oam status [interface interface-id] Verify the configuration.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no ethernet oam remote-loopback {supported | timeout} interface configuration command to
disable remote loopback support or remove the timeout setting.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Define an interface, and enter interface configuration
mode.
Step 3 ethernet oam link-monitor supported Enable the interface to support link monitoring. This is the
default.
You need to enter this command only if it has been disabled
by previously entering the no ethernet oam link-monitor
supported command.
Command Purpose
Step 4 ethernet oam link-monitor symbol-period (Optional) Configure high and low thresholds for an
{threshold {high {high symbols | none} | low error-symbol period that trigger an error-symbol period
{low-symbols}} | window symbols} link event.
Note Repeat this step to configure both high and • Enter threshold high high-symbols to set a high
low thresholds. threshold in number of symbols. The range is 1 to
65535. The default is none.
• Enter threshold high none to disable the high
threshold if it was set. This is the default.
• Enter threshold low low-symbols to set a low
threshold in number of symbols. The range is 0 to
65535. It must be lower than the high threshold.
• Enter window symbols to set the window size (in
number of symbols) of the polling period. The range is
1 to 65535 symbols.
Step 5 ethernet oam link-monitor frame {threshold {high (Optional) Configure high and low thresholds for error
{high-frames | none} | low {low-frames}} | window frames that trigger an error-frame link event.
milliseconds}
• Enter threshold high high-frames to set a high
Note Repeat this step to configure both high and threshold in number of frames. The range is 1 to
low thresholds. 65535. The default is none.
• Enter threshold high none to disable the high
threshold if it was set. This is the default.
• Enter threshold low low-frames to set a low threshold
in number of frames. The range is 0 to 65535. The
default is 1.
• Enter window milliseconds to set the a window and
period of time during which error frames are counted.
The range is 10 to 600 and represents the number of
milliseconds in multiples of 100. The default is 100.
Step 6 ethernet oam link-monitor frame-period (Optional) Configure high and low thresholds for the
{threshold {high {high-frames | none} | low error-frame period that triggers an error-frame-period link
{low-frames}} | window frames} event.
Note Repeat this step to configure both high and • Enter threshold high high-frames to set a high
low thresholds. threshold in number of frames. The range is 1 to
65535. The default is none.
• Enter threshold high none to disable the high
threshold if it was set. This is the default.
• Enter threshold low low-frames to set a low threshold
in number of frames. The range is 0 to 65535. The
default is 1.
• Enter window frames to set the a polling window size
in number of frames. The range is 1 to 65535; each
value is a multiple of 10000 frames. The default is
1000.
Command Purpose
Step 7 ethernet oam link-monitor frame-seconds (Optional) Configure high and low thresholds for the
{threshold {high {high-frames | none} | low frame-seconds error that triggers an error-frame-seconds
{low-frames}} | window milliseconds} link event.
Note Repeat this step to configure both high and • Enter threshold high high-frames to set a high error
low thresholds. frame-seconds threshold in number of seconds. The
range is 1 to 900. The default is none.
• Enter threshold high none to disable the high
threshold if it was set. This is the default.
• Enter threshold low low-frames to set a low threshold
in number of frames. The range is 1 to 900. The default
is 1.
• Enter window frames to set the a polling window size
in number of milliseconds. The range is 100 to 9000;
each value is a multiple of 100 milliseconds. The
default is 1000.
Step 8 ethernet oam link-monitor receive-crc {threshold (Optional) Configure thresholds for monitoring ingress
{high {high-frames | none} | low {low-frames}} | frames received with cyclic redundancy code (CRC) errors
window milliseconds} for a period of time.
Note Repeat this step to configure both high and • Enter threshold high high-frames to set a high
low thresholds. threshold for the number of frames received with CRC
errors. The range is 1 to 65535 frames.
• Enter threshold high none to disable the high
threshold.
• Enter threshold low low-frames to set a low threshold
in number of frames. The range is 0 to 65535. The
default is 1.
• Enter window milliseconds to set the a window and
period of time during which frames with CRC errors
are counted. The range is 10 to 1800 and represents the
number of milliseconds in multiples of 100. The
default is 100.
Step 9 [no] ethernet link-monitor on (Optional) Start or stop (when the no keyword is entered)
link-monitoring operations on the interface. Link
monitoring operations start automatically when support is
enabled.
Step 10 end Return to privileged EXEC mode.
Step 11 show ethernet oam status [interface interface-id] Verify the configuration.
Step 12 copy running-config startup-config (Optional) Save your entries in the configuration file.
The ethernet oam link-monitor transmit-crc {threshold {high {high-frames | none} | low
{low-frames}} | window milliseconds} command is visible on the switch and you are allowed to enter
it, but it is not supported.Enter the no form of the commands to disable the configuration. Use the no
form of each command to disable the threshold setting.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Define an interface, and enter interface configuration
mode.
Step 3 ethernet oam remote-failure {critical-event | Configure the Ethernet OAM remote-failure action on the
dying-gasp | link-fault} action interface. You can configure disabling the interface for one
error-disable-interface of these conditions:
• Select critical-event to shut down the interface when
an unspecified critical event has occurred.
• Select dying-gasp to shut down the interface when
Ethernet OAM is disabled or the interface enters the
error-disabled state.
• Select link-fault to shut down the interface when the
receiver detects a loss of signal.
Step 4 end Return to privileged EXEC mode.
Step 5 show ethernet oam status [interface interface-id] Verify the configuration.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
The switch does not generate Link Fault or Critical Event OAM PDUs. However, if these PDUs are
received from a link partner, they are processed. The switch supports sending and receiving Dying Gasp
OAM PDUs when Ethernet OAM is disabled, the interface is shut down, the interface enters the
error-disabled state, or the switch is reloading. It can respond to, but not generate, Dying Gasp PDUs
based on loss of power. Enter the no ethernet remote-failure {critical-event | dying-gasp | link-fault}
action command to disable the remote failure indication action.
Beginning in privileged EXEC mode, follow these steps to configure an Ethernet OAM template and to
associate it with an interface:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 template template-name Create a template, and enter template configuration mode.
Step 3 ethernet oam link-monitor receive-crc {threshold (Optional) Configure thresholds for monitoring ingress
{high {high-frames | none} | low {low-frames}} | frames received with cyclic redundancy code (CRC) errors
window milliseconds} for a period of time.
• Enter threshold high high-frames to set a high
threshold for the number of frames received with CRC
errors. The range is 1 to 65535 frames.
• Enter threshold high none to disable the high
threshold.
• Enter threshold low low-frames to set a low threshold
in number of frames. The range is 0 to 65535. The
default is 1.
• Enter window milliseconds to set the a window and
period of time during which frames with CRC errors
are counted. The range is 10 to 1800 and represents the
number of milliseconds in multiples of 100. The
default is 100.
Step 4 ethernet oam link-monitor symbol-period (Optional) Configure high and low thresholds for an
{threshold {high {high symbols | none} | low error-symbol period that triggers an error-symbol period
{low-symbols}} | window symbols} link event.
• Enter threshold high high-symbols to set a high
threshold in number of symbols. The range is 1 to
65535.
• Enter threshold high none to disable the high
threshold.
• Enter threshold low low-symbols to set a low
threshold in number of symbols. The range is 0 to
65535. It must be lower than the high threshold.
• Enter window symbols to set the window size (in
number of symbols) of the polling period. The range is
1 to 65535 symbols.
Command Purpose
Step 5 ethernet oam link-monitor frame {threshold {high (Optional) Configure high and low thresholds for error
{high-frames | none} | low {low-frames}} | window frames that trigger an error-frame link event.
milliseconds}
• Enter threshold high high-frames to set a high
threshold in number of frames. The range is 1 to
65535. You must enter a high threshold.
• Enter threshold high none to disable the high
threshold.
• Enter threshold low low-frames to set a low threshold
in number of frames. The range is 0 to 65535. The
default is 1.
• Enter window milliseconds to set the a window and
period of time during which error frames are counted.
The range is 10 to 600 and represents the number of
milliseconds in a multiple of 100. The default is 100.
Step 6 ethernet oam link-monitor frame-period (Optional) Configure high and low thresholds for the
{threshold {high {high-frames | none} | low error-frame period that triggers an error-frame-period link
{low-frames}} | window frames} event.
• Enter threshold high high-frames to set a high
threshold in number of frames. The range is 1 to
65535. You must enter a high threshold.
• Enter threshold high none to disable the high
threshold.
• Enter threshold low low-frames to set a low threshold
in number of frames. The range is 0 to 65535. The
default is 1.
• Enter window frames to set the a polling window size
in number of frames. The range is 1 to 65535; each
value is a multiple of 10000 frames. The default is
1000.
Step 7 ethernet oam link-monitor frame-seconds (Optional) Configure frame-seconds high and low
{threshold {high {high-seconds | none} | low thresholds for triggering an error-frame-seconds link event.
{low-seconds}} | window milliseconds}
• Enter threshold high high-seconds to set a high
threshold in number of seconds. The range is 1 to 900.
You must enter a high threshold.
• Enter threshold high none to disable the high
threshold.
• Enter threshold low low-frames to set a low threshold
in number of frames. The range is 1 to 900. The default
is 1.
• Enter window frames to set the a polling window size
in number of frames. The range is 100 to 9000; each
value is a multiple of 100 milliseconds. The default is
1000.
Command Purpose
Step 8 ethernet oam link-monitor high threshold action (Optional) Configure the switch to put an interface in an
error-disable-interface error disabled state when a high threshold for an error is
exceeded.
Step 9 exit Return to global configuration mode.
Step 10 interface interface-id Define an Ethernet OAM interface, and enter interface
configuration mode.
Step 11 source-template template-name Associate the template to apply the configured options to
the interface.
Step 12 end Return to privileged EXEC mode.
Step 13 show ethernet oam status [interface interface-id] Verify the configuration.
Step 14 copy running-config startup-config (Optional) Save your entries in the configuration file.
The switch does not support monitoring egress frames with CRC errors. The ethernet oam link-monitor
transmit-crc {threshold {high {high-frames | none} | low {low-frames}} | window milliseconds}
command is visible on the switch and you can enter it, but it is not supported. Use the no form of each
command to remove the option from the template. Use the no source-template template-name to remove
the source template association.
Command Purpose
show ethernet oam discovery [interface interface-id] Displays discovery information for all Ethernet OAM interfaces or
the specified interface.
show ethernet oam statistics [interface interface-id] Displays detailed information about Ethernet OAM packets.
show ethernet oam status [interface interface-id] Displays Ethernet OAM configuration for all interfaces or the
specified interface.
show ethernet oam summary Displays active Ethernet OAM sessions on the switch.
Understanding E-LMI
Ethernet Local Management Interface (E-LMI) is a protocol between the customer-edge (CE) device and
the provider-edge (PE) device. It runs only on the PE-to-CE UNI link and notifies the CE device of
connectivity status and configuration parameters of Ethernet services available on the CE port. E-LMI
interoperates with an OAM protocol, such as CFM, that runs within the provider network to collect OAM
status. CFM runs at the provider maintenance level (UPE to UPE with inward-facing MEPs at the UNI).
E-LMI relies on the OAM Ethernet Infrastructure to interwork with CFM for end-to-end status of
Ethernet virtual connections (EVCs) across CFM domains.
OAM manager, which streamlines interaction between any two OAM protocols, handles the interaction
between CFM and E-LMI. This interaction is unidirectional, running only from OAM manager to E-LMI
on the UPE side of the switch. Information is exchanged either as a result of a request from E-LMI or
triggered by OAM when it received notification of a change from the OAM protocol. This type of
information is relayed:
• EVC name and availability status
• Remote UNI name and status
• Remote UNI counts
You can configure Ethernet virtual connections (EVCs), service VLANs, UNI ids (for each CE-to-PE
link), and UNI count and attributes. You need to configure CFM to notify the OAM manager of any
change to the number of active UNIs and or the remote UNI ID for a given S-VLAN domain.
You can configure the switch as either the customer-edge device or the provider-edge device.
Note If crosscheck is disabled, no SNMP traps are sent when there is a change in the number of UNIs.
Configuring E-LMI
For E-LMI to work with CFM, you configure Ethernet virtual connections (EVCs), Ethernet service
instances (EFPs), and E-LMI customer VLAN mapping. Most of the configuration occurs on the PE
switch on the interfaces connected to the CE device. On the CE switch, you only need to enable E-LMI
on the connecting interface. Note that you must configure some OAM parameters, for example, EVC
definitions, on PE devices on both sides of a metro network.
This section includes this information:
• Default E-LMI Configuration, page 43-44
• E-LMI and OAM Manager Configuration Guidelines, page 43-44
• Configuring the OAM Manager, page 43-45
• Enabling E-LMI, page 43-47
• Ethernet OAM Manager Configuration Example, page 43-48
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ethernet cfm domain domain-name level level-id Define a CFM domain, set the domain level, and enter
ethernet-cfm configuration mode for the domain. The
maintenance level number range is 0 to 7.
Step 3 service csi-id vlan vlan-id Define a universally unique customer service instance
(CSI) and VLAN ID within the maintenance domain.
• csi-id—a string of no more than 100 characters that
identifies the CSI.
• vlan-id—VLAN range is from 1 to 4095. You cannot
use the same VLAN ID for more than one domain at
the same level.
Step 4 exit Return to global configuration mode.
Step 5 ethernet evc evc-id Define an Ethernet virtual connection (evc), and enter evc
configuration mode. The identifier can be up to 100
characters in length.
Step 6 oam protocol cfm svlan vlan-id domain Configure the EVC OAM protocol as CFM, and identify
domain-name the service provider VLAN-ID (S-VLAN-ID) for the CFM
domain maintenance level as configured in Steps 2 and 3.
Note If the CFM domain does not exist, the command is
rejected, and an error message appears.
Step 7 uni count value (Optional) Set the UNI count for the EVC. The range is 2
to 1024; the default is 2.
If the command is not entered, the service defaults to a
point-to-point service. If you enter a value of 2, you have
the option to select point-to-multipoint service. If you
configure a value of 3 or greater, the service is
point-to-multipoint.
Note You should know the correct number of
maintenance end points in the domain. If you enter
a value greater than the actual number of end
points, the UNI status will show as partially active
even if all end points are up; if you enter a uni count
less than the actual number of end points, status
might show as active, even if all end points are not
up.
Step 8 exit Return to global configuration mode.
Step 9 Repeat Steps 2 to 5 for other CFM domains that you want OAM manager to monitor.
Step 10 interface interface-id Specify a physical interface connected to the CE device,
and enter interface configuration mode.
Command Purpose
Step 11 service instance efp-identifier ethernet [evc-id] Configure an Ethernet service instance (EFP) on the
interface, and enter ethernet service configuration mode.
• The EFP identifier is a per-interface service identifier
that does not map to a VLAN. The EFP identifier range
is 1 to 4967295.
• (Optional) Enter an evc-id to attach an EVC to the EFP.
Step 12 ethernet lmi ce-vlan map {vlan-id | any | default | Configure an E-LMI customer VLAN-to-EVC map for a
untagged} particular UNI. The keywords have these meanings:
• For vlan vlan-id, enter the customer VLAN ID or IDs
to map to as single VLAN-ID (1 to 4094), a range of
VLAN-IDs separated by a hyphen, or a series of
VLAN IDs separated by commas.
• Enter any to map all VLANs (untagged or 1 to 4094).
• Enter default to map the default EFP. You can use
default keyword only if you have already mapped the
service instance to a VLAN or group of VLANs.
• Enter untagged to map untagged VLANs.
Step 13 exit Return to interface configuration mode.
Step 14 ethernet uni id name Configure an Ethernet UNI ID. The name should be unique
for all the UNIs that are part of a given customer service
instance and can be up to 64 characters in length. When a
UNI id is configured on a port, that ID is used as the default
name for all MEPs configured on the port, unless a name is
explicitly configured for a given MEP.
Note This command is required on all ports that are
directly connected to CE devices. If the specified
ID is not unique on the device, an error message
appears.
Step 15 ethernet uni {bundle [all-to-one] | multiplex} (Optional) Set UNI bundling attributes:
• If you enter bundle <cr>, the UNI supports bundling
without multiplexing (only one EVC with one or
multiple VLANs be mapped to it).
• If you enter bundle all-to-one, the UNI supports a
single EVC and all VLANs are mapped to that EVC.
• If you enter multiplex, the UNI supports multiplexing
without bundling (one or more EVCs with a single
VLAN mapped to each EVC).
If you do not configure bundling attributes, the default is
bundling with multiplexing (one or more EVCs with one or
more VLANs mapped to each EVC).
Step 16 end Return to privileged EXEC mode.
Step 17 show ethernet service evc {detail | id evc-id | Verify the configuration.
interface interface-id}
Step 18 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no forms of the commands to delete an EVC, EFP, or UNI ID, or to return to default
configurations.
Note If you configure, change, or remove a UNI service type, EVC, EFP, or CE-VLAN configuration, all
configurations are checked to make sure that the configurations match (UNI service type with EVC or
EFP and CE-VLAN configuration). The configuration is rejected if the configurations do not match.
Enabling E-LMI
You can enable E-LMI globally or on an interface and you can configure the switch as a PE or a CE
device. Beginning in privileged EXEC mode, follow these steps to enable for E-LMI on the switch or on
an interface. Note that the order of the global and interface commands determines the configuration. The
command that is entered last has precedence.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ethernet lmi global Globally enable E-LMI on all interfaces. By default, the
switch is a PE device.
Step 3 ethernet lmi ce (Optional) Configure the switch as an E-LMI CE device.
Step 4 interface interface-id Define an interface to configure as an E-LMI interface, and
enter interface configuration mode.
Step 5 ethernet lmi interface Configure Ethernet LMI on the interface. If E-LMI is
enabled globally, it is enabled on all interfaces unless you
disable it on specific interfaces. If E-LMI is disabled
globally, you can use this command to enable it on
specified interfaces.
Command Purpose
Step 6 ethernet lmi {n391 value | n393 value | t391 value| Configure E-LMI parameters for the UNI.
t392 value}
The keywords have these meanings:
• n391 value—Set the event counter on the customer
equipment. The counter polls the status of the UNI and
all Ethernet virtual connections (EVCs). The range is
from 1 to 65000; the default is 360.
• n393 value—Set the event counter for the metro
Ethernet network. The range is from 1 to 10; the
default is 4.
• t391 value—Set the polling timer on the customer
equipment. A polling timer sends status enquiries and
when status messages are not received, records errors.
The range is from 5 to 30 seconds; the default is 10
seconds.
• t392 value—Set the polling verification timer for the
metro Ethernet network or the timer to verify received
status inquiries. The range is from 5 to 30 seconds, or
enter 0 to disable the timer. The default is 15 seconds.
Note The t392 keyword is not supported when the switch
is in CE mode.
Step 7 end Return to privileged EXEC mode.
Step 8 show ethernet lmi evc Verify the configuration.
Step 9 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no ethernet lmi global configuration command to globally disable E-LMI. Use the no form of
the ethernet lmi interface configuration command with keywords to disable E-LMI on the interface or
to return the timers to the default settings.
Use the show ethernet lmi commands to display information that was sent to the CE from the status
request poll. Use the show ethernet service commands to show current status on the device.
Switch(config-ether-cfm)# exit
Switch(config)# ethernet cfm enable
Switch(config)# ethernet evc test1
Switch(config-evc)# oam protocol cfm svlan 101 domain Provider
Switch(config-evc)# exit
Switch(config)# ethernet evc 101
Switch(config-evc)# uni count 3
Switch(config-evc)# oam protocol cfm svlan 101 domain Operator
Switch(config-evc)# exit
Switch(config)# ethernet lmi global
Switch(config)# interface gigabitethernet 1/0/2
Switch(config-if)# ethernet cfm mip level 7
Switch(config-if)# ethernet cfm mep level 4 mpid 200 vlan 200
Switch(config-if)# service instance 101 ethernet test1
Switch(config-if-srv)# ethernet lmi ce-vlan map 101
Switch(config-if-srv)# exit
Switch(config-if)# exit
Switch(config)# ethernet cfm cc enable level 2-4 vlan 101
Switch(config)# exit
Note For E-LMI to work, any VLANs used on the PE device must also be created on the CE device. Create a
VLAN by entering the vlan vlan-id global configuration command on the CE device, where the vlan-ids
match those on the PE device and configure these VLANs as allowed VLANs by entering the switchport
trunk allowed vlan vlan-ids interface configuration command. Allowed VLANs can receive and send
traffic on the interface in tagged format when in trunking mode.
Command Purpose
show ethernet lmi evc [detail evc-id [interface Displays details sent to the CE from the status request poll about the
interface-id] | map interface type number] E-LMI EVC.
show ethernet lmi parameters interface interface-id Displays Ethernet LMI interface parameters sent to the CE from the
status request poll.
Command Purpose
show ethernet lmi statistics interface interface-id Displays Ethernet LMI interface statistics sent to the CE from the
status request poll.
show ethernet lmi uni map interface [interface-id] Displays information about the E-LMI UNI VLAN map sent to the CE
from the status request poll.
show ethernet service evc {detail | id evc-id | Displays information about the specified Ethernet virtual connection
interface interface-id} (EVC) customer-service instance or all configured service instances.
show ethernet service instance {detail | id Displays information relevant to the specified Ethernet service
efp-identifier interface interface-id | interface instances (EFPs).
interface-id}
show ethernet service interface [interface-id] Displays information about OAM manager interfaces.
[detail]
Note If you configure, change, or remove a UNI service type, EVC, Ethernet service instance, or CE-VLAN
configuration, all configurations are verified to ensure that the UNI service types match the EVC
configuration and that Ethernet service instances are matched with the CE-VLAN configuration.
Configurations are rejected if the pairs do not match.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ethernet cfm domain domain-name level level-id Define a CFM domain, set the domain level, and enter
ethernet-cfm configuration mode for the domain. The
maintenance level number range is 0 to 7.
Step 3 service csi-id vlan vlan-id Define a universally unique customer service instance
(CSI) and VLAN ID within the maintenance domain.
• csi-id—String of no more than 100 characters that
identifies the CSI.
• vlan-id—VLAN range is from 1 to 4095. You cannot
use the same VLAN ID for more than one domain at
the same level.
Step 4 exit Return to global configuration mode.
Step 5 ethernet evc evc-id Define an EVC, and enter EVC configuration mode
Step 6 oam protocol cfm svlan vlan-id domain Configure the EVC OAM protocol as CFM, and identify
domain-name the service provider VLAN-ID (S-VLAN-ID) for the CFM
domain maintenance level as configured in Steps 2 and 3.
Step 7 exit Return to global configuration mode.
Step 8 Repeat Steps 2 through 7 to define other CFM domains that you want OAM manager to monitor.
Step 9 ethernet cfm enable Globally enable CFM.
Step 10 end Return to privileged EXEC mode.
Step 11 copy running-config startup-config (Optional) Save your entries in the configuration file.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Define an interface to configure as an Ethernet OAM
interface and enter interface configuration mode.
Step 3 ethernet oam [max-rate oampdus | min-rate Enable Ethernet OAM on the interface
seconds | mode {active | passive} | timeout seconds]
• (Optional) Enter max-rate oampdus to set the
maximum rate (per second) to send OAM PDUs. The
range is 1 to 10 PDUs per second; the default is 10.
• (Optional) Enter min-rate seconds to set the minimum
rate in seconds.The range is 1 to 10 seconds.
• (Optional) Set the OAM client mode as active or
passive. The default is active.
• (Optional) Enter timeout seconds to set the time after
which a device declares the OAM peer to be
nonoperational and resets its state machine. The range
is 2 to 30 seconds; the default is 5 seconds.
Step 4 end Return to privileged EXEC mode.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
Step 6 show ethernet cfm maintenance points remote (Optional) Display the port states as reported by Ethernet
OAM.
These are examples of the output showing provider-edge switch port status of the configuration. Port
status shows as UP at both switches.
Switch PE1:
Switch# show ethernet cfm maintenance points remote
MPID Level Mac Address Vlan PortState InGressPort Age(sec) Service ID
101 * 4 0015.633f.6900 10 UP Gi1/1/1 27 blue
Switch PE2:
Switch# show ethernet cfm maintenance points remote
MPID Level Mac Address Vlan PortState InGressPort Age(sec) Service ID
100 * 4 0012.00a3.3780 10 UP Gi1/1/1 8 blue
Total Remote MEPs: 1
This example shows the outputs when you start remote loopback on CE1 (or PE1). The port state on the
remote PE switch shows as Test and the remote CE switch goes into error-disable mode.
Switch# ethernet oam remote-loopback start interface gigabitEthernet 0/1
This is a intrusive loopback.
Therefore, while you test Ethernet OAM MAC connectivity,
you will be unable to pass traffic across that link.
Proceed with Remote Loopback? [confirm]
Switch PE1:
Switch# show ethernet cfm maintenance points remote
MPID Level Mac Address Vlan PortState InGressPort Age(sec) Service ID
101 * 4 0015.633f.6900 10 UP Gi1/1/1 27 blue
Switch PE2:
Switch# show ethernet cfm maintenance points remote
MPID Level Mac Address Vlan PortState InGressPort Age(sec) Service ID
100 * 4 0012.00a3.3780 10 TEST Gi1/1/1 8 blue
Total Remote MEPs: 1
In addition, if you shut down the CE1 interface that connects to PE1, the remote PE2 port will show a
PortState of Down.
This chapter describes how to configure multiprotocol label switching (MPLS) and Ethernet over MPLS
(EoMPLS) on the Catalyst 3750 Metro switch. MPLS is a packet-switching technology that integrates
link layer (Layer 2) switching with network layer (Layer 3) routing. With MPLS, data is transferred over
any combination of Layer 2 technologies, using any Layer 3 protocol, with increased scalability. MPLS
supports different routes between a source and destination over a router-based Internet backbone.
• MPLS virtual private networks (VPNs) provides the capability to deploy and administer scalable
Layer 3 VPN backbone services to business customers. A VPN is a secure IP-based network that
shares resources on one or more physical networks.
• Cisco IOS Release 12.2(37)SE includes support for MPLS Operations, Administration, and
Maintenance (OAM) functionality to allow service providers to monitor label switched path (LSP)
integrity and to quickly isolate MPLS forwarding problems. Cisco IOS Release 12.2(40)SE adds
more functionality, including support for MPLS IP Service Level Agreements (IP SLAs).
• Cisco IOS Release 12.2(46)SE adds support for MPLS traffic engineering fast reroute link
protection. This feature provides link protection to label-switched paths (LSPs), enabling LSP
traffic that crosses a failed link to be rerouted around the failure.
• EoMPLS is a tunneling mechanism that transports Layer 2 Ethernet frames over an MPLS network.
You can connect two Layer 2 networks that are in different locations, without bridges, routers, or
switches at the locations. You enable the MPLS backbone to accept Layer 2 traffic by configuring
the label-edge routers (LERs) at both ends of the MPLS backbone.
MPLS functionality is supported only on the enhanced-services (ES) ports; EoMPLS is supported on
standard ports and on switch virtual interfaces (SVIs).
Note The switch does not support IPv6 features with any ES port features, such as MPLS. MPLS and EoMPLS
are mutually exclusive with IPv6.
For more information about MPLS, see the “Multiprotocol Label Switching” section of the Cisco IOS
Multiprotocol Label Switching Configuration Guide for Release 12.2 t this URL:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/12_2sr/mp_12_2sr_book.html
For complete syntax and usage information for the MPLS commands used in this chapter, see this URL:
http://www.cisco.com/en/US/docs/ios/mpls/command/reference/mp_book.html
and the router uses MPLS forwarding-table lookups for the label to make forwarding decisions. It is not
necessary to re-analyze the packet header. Because the label is a fixed length and unstructured, the MPLS
forwarding-table lookup process is straightforward and fast.
Each label-switching router (LSR) in the network makes an independent, local decision as to which label
value is used to represent which forwarding equivalence class. This association is known as a label
binding. Each LSR informs its neighbors of the label bindings that it has made. When a labeled packet
is sent from LSR A to neighboring LSR B, the label value carried by the packet is the label value that B
assigned to represent the packet's forwarding equivalence class. Thus, the label value changes as the IP
packet travels through the network.
Note Because the Catalyst 3750 Metro switch is used as service-provider edge (PE) device, rather than a
service-provider core router, it does not normally operate as an LSR. The switch only performs label
switching when it is connected to two different provider core routers over the ES ports to provide a
redundant path. In this case, the switch uses quality of service (QoS) policies to classify MPLS packets
on egress for label switching.
A label represents a forwarding-equivalence class, but it does not represent a particular path through the
network. In general, the path through the network continues to be chosen by the existing Layer 3 routing
protocols, such as Open Shortest Path First (OSPF), Enhanced Interior Gateway Protocol (EIGRP),
Intermediate-System-to-Intermediate-System (IS-IS), and Border Gateway Protocol (BGP). At each hop
when a label is looked up, the choice of the next hop is determined by the dynamic routing algorithm.
forwarded outside a VPN and prevents packets that are outside a VPN from being forwarded to a router
within the VPN. Based on the routing information stored in the VRF IP routing table and the VRF Cisco
Express Forwarding table, packets are forwarded to their destinations.
A provider-edge router binds a label to each customer prefix that is learned from a CE device and
includes the label in the network reachability information for the prefix that it advertises to other (PE)
routers. When a PE router forwards a packet that is received from a CE device across the provider
network, it labels the packet with the label learned from the destination PE router. When the destination
PE router receives the labeled packet, it examines the label and uses it to direct the packet to the correct
CE device.
A customer data-packet carries two levels of labels when traversing the backbone:
• The top label directs the packet to the correct PE router.
• The second label defines how that PE router should forward the packet to the CE device.
VPN Benefits
MPLS VPNs allow service providers to deploy scalable VPNs and build the foundation to deliver
value-added services, including:
• Connectionless service—MPLS VPNs are connectionless, which means that no prior action is
required to establish communication between hosts. A connectionless VPN does not require tunnels
and encryption for network privacy.
• Centralized service—MPLS VPNs are seen as private intranets, which allows delivery of targeted
IP services to a group of users represented by a VPN.
• Scalability— MPLS-based VPNs use the peer model and Layer 3 connectionless architecture to
leverage a highly scalable solution. The peer model requires a customer site to act as a peer to one
PE router as opposed to all other customer PE or CE devices that are members of the VPN. The PE
routers maintain VPN routes for those VPNs that are members. Routers in the core network do not
maintain any VPN routes.
• Security—MPLS VPNs offer the same level of security as connection-oriented VPNs. Packets from
one VPN do not inadvertently go to another VPN. Security provided at the edge of a provider
network ensures that packets received from a customer are placed on the correct VPN; security
provided at the backbone ensures that VPN traffic is kept separate.
• Easy to create—Because MPLS VPNs are connectionless, no specific point-to-point connection
maps or topologies are required, and you can add sites to intranets and extranets to form closed user
groups.
• Flexible addressing—Customers can continue to use their present address spaces without network
address translation (NAT) because the MPLS VPN provides a public and private view of the address.
A NAT is required only if two VPNs with overlapping address spaces want to communicate.
• Straightforward migration—You can build MPLS VPNs over multiple network architectures.
Migration for the end customer is simplified because the CE router is not required to support MPLS,
so no customer's intranet modifications are needed.
• MPLS VPN also provides increased BGP functionality.
Figure 44-1 shows an example of a VPN with a service-provider backbone network, provider-edge (PE)
CLE routers, and customer-edge (CE) devices.
Customer
Customer site 1 site 2
Service provider
VPN 1 VPN 1
backbone
P P
CE
CE PE-CLE
VPN 2
PE-CLE
PE-CLE
P P CE
Customer site 3
VPN 2
122010
CE
Each VPN contains customer devices attached to the customer-edge (CE) devices. The customer devices
use VPNs to exchange information between devices, and the provider routers (P) are not aware of the
VPNs.
Figure 44-2 shows five customer sites communicating within three VPNs. The VPNs can communicate
with these sites:
VPN1: Sites 2 and 4
VPN2: Sites 1, 3, and 4
VPN3: Sites 1, 3, and 5
VPN2
VPN1 VPN3
Site 2 Site 1
Site 4
Site 3 Site 5
17266
For an example of packet flow in an MPLS VPN, see the “Packet Flow in an MPLS VPN” section on
page 44-12.
Enabling MPLS
To use MPLS in a network, such as the one shown in Figure 44-1, MPLS must be globally enabled and
explicitly configured on the provider-edge routers.
Beginning in privileged EXEC mode, follow these steps to incrementally deploy MPLS through a
network, assuming that packets to all destination prefixes should be label-switched:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip routing Enable IP routing on the switch if it is disabled.
Step 3 ip cef distributed Enable CEF on the device if it has been disabled.
Command Purpose
Step 4 mpls ip Enable MPLS forwarding of IPv4 packets on normally routed paths if it
has been disabled.
Step 5 mpls label protocol ldp Set the label protocol on the switch to LDP. The default protocol is TDP.
Step 6 mpls ldp advertise-labels [for Enable MPLS label advertising on the switch. If no keywords are
prefix-access-list [to peer-access-list]] included, there are no restrictions on which labels are advertised.
• (Optional) for prefix-access-list—Specify which destinations should
have their labels advertised.
• (Optional) to peer-access-list—Specify which LDP neighbors should
receive label advertisements. A label switch router (LSR) is
identified by its router ID, which consists of the first 4 bytes of its
6-byte LDP identifier.
Step 7 interface interface-id Enter interface configuration mode, and specify the Layer 3 ES interface
connected to the MPLS network. Valid ES interfaces include
gigabitethernet1/1/1, gigabitethernet1/1/2, and VLANs.
Step 8 mpls ip Enable MPLS forwarding of IPv4 packets along normally routed paths for
the interface.
Step 9 end Return to privileged EXEC mode.
Step 10 show mpls forwarding-table Verify the configuration.
show mpls interfaces
Step 11 copy running-config startup-config (Optional) Save your entries in the configuration file.
Repeat these steps for every PE router in the network and the appropriate interfaces until all routers and
connected interfaces are enabled for MPLS.
Use the no mpls ip global configuration command to disable MPLS on the switch. Use the no mpls label
protocol ldp global configuration command to return to the default TDP.
Defining VPNs
Beginning in privileged EXEC mode, follow these steps to define VPN routing instances on the PE
router:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip routing Enable IP routing (required only if routing is disabled).
Step 3 ip vrf vrf-name Enter VRF configuration mode, and define the VPN routing instance by
assigning a VRF name.
Step 4 rd route-distinguisher Create a VRF table by specifying a route distinguisher. Enter either an AS
number and an arbitrary number (xxx:y) or an IP address and arbitrary
number (A.B.C.D:y).
Command Purpose
Step 5 route-target {export | import | both} Create a list of import, export, or import and export route target
route-target-ext-community communities for the specified VRF. Enter either an AS system number
and an arbitrary number (xxx:y) or an IP address and an arbitrary number
(A.B.C.D:y). The route-target-ext-community should be the same as the
route-distinguisher entered in Step 4.
Step 6 import map route-map (Optional) Associate the specified import route map with the VRF.
Step 7 export map route-map (Optional) Associate the specified export route map with the VRF.
Step 8 exit Return to global configuration mode.
Step 9 interface interface-id Enter interface configuration mode, and specify the Layer 3 ES or VLAN
interface to be associated with the VRF.
Step 10 ip vrf forwarding vrf-name Associate the Layer 3 interface with the VRF.
Step 11 end Return to privileged EXEC mode.
Step 12 show ip vrf Display the defined VRFs and interfaces.
Step 13 show ip route vrf Display the IP routing table for a VRF.
show ip cef vrf vrf-name Display the CEF forwarding table associated with a VRF.
Step 14 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no ip vrf vrf-name global configuration command to delete a VRF and remove interfaces from
it. Use the no ip vrf forwarding interface configuration command to remove an interface from a VRF.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip routing Enable IP routing (required only if routing is disabled).
Step 3 router bgp autonomous-system-number Enable a BGP routing process, assign it the AS number passed
to the other BGP routers, and enter router configuration mode.
The AS number can be from 1 to 65535, with 64512 to 65535
designated as private autonomous numbers.
Step 4 neighbor {ip-address | peer-group-name} Specify a neighbor IP address or BGP peer group that
remote-as as-number identifies it to the local autonomous system. The AS number
can be from 1 to 65535.
Step 5 neighbor ip-address activate Activate the advertisement of the IPv4 address family.
Step 6 end Return to privileged EXEC mode.
Step 7 show ip bgp neighbor Verify the configuration.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no router bgp autonomous-system global configuration command to delete the BGP routing
session.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 router bgp autonomous-system-number Enter router configuration mode.
Step 3 address-family vpnv4 [unicast] Enter address family configuration mode to configure routing
sessions that use standard VPNv4 address prefixes.
(Optional) unicast—Specify VPNv4 unicast address prefixes.
Step 4 neighbor ip-address remote-as as-number Define an IBGP session between the provider-edge routers.
Step 5 neighbor ip-address activate Activate the advertisement of the IPv4 address family.
Step 6 end Return to privileged EXEC mode.
Step 7 show ip bgp [ipv4] [neighbors] [vpnv4] Verify BGP configuration. Display information about all BGP
IPv4 prefixes.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no router bgp autonomous-system global configuration command to delete the BGP routing
session.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 router bgp autonomous-system-number Configure the BGP routing process with the AS number passed
to other BGP routers, and enter router configuration mode.
Step 3 address-family ipv4 [unicast] vrf vrf-name Define EGPG parameters for PE-to-CE routing sessions, and
enter VRF address-family configuration mode.
Note The default is off for auto-summary and synchronization
in the VRF address-family configuration mode.
Step 4 neighbor address remote-as as-number Define an EBGP session between PE and CE routers.
Step 5 neighbor address activate Activate the advertisement of the IPv4 address family.
Step 6 end Return to privileged EXEC mode.
Step 7 show ip bgp [ipv4] [neighbors] Verify BGP configuration. Display information about all BGP
IPv4 prefixes.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no router bgp as-number global configuration command to delete the BGP routing session.
Note You can also use the OSPF routing protocol for PE-to-CE routing sessions.
Beginning in privileged EXEC mode, follow these steps on the provider-edge router to configure RIP
PE-to-CE routing:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 router rip Enable RIP routing, and enter router configuration mode.
Step 3 address-family ipv4 [unicast] vrf -name Define RIP parameters for PE-to-CE routing sessions, and enter
VRF address-family configuration mode.
Note The default is off for auto-summary and synchronization
in the VRF address-family configuration mode.
Step 4 network prefix Enable RIP on the PE-to-CE link.
Step 5 end Return to privileged EXEC mode.
Step 6 show ip rip database [network-prefix] Verify the configuration.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no router rip global configuration command to disable RIP routing.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip route vrf vrf-name prefix mask Define the VRF static routing table to use for PE-to-CE sessions.
Step 3 router bgp autonomous-system-number Enter the BGP routing process AS number, and enter router
configuration mode.
Step 4 address-family ipv4 [unicast] vrf vrf-name Define static route parameters for every PE-to-CE routing session,
and enter VRF address-family configuration mode.
Note The default is off for auto-summary and synchronization in
the VRF address-family configuration mode.
Step 5 redistribute static Redistribute VRF static routes into the VRF BGP table.
Step 6 redistribute connected Redistribute directly connected networks into the VRF BGP table.
Step 7 end Return to privileged EXEC mode.
Step 8 show ip bgp [ipv4] Verify the configuration.
Step 9 copy running-config startup-config (Optional) Save your entries in the configuration file.
PE2 VPN-IPv4
Net RD:16.2/16
P2 Next hop:PE3
Label 42
BGP
PE3
CE1 P1
IP destination: IP destination:
16.2.1.1 Step 3 16.2.1.1
101099
16.2.1.1
A customer (Fast Ethernet) port on switch PE1 is configured for routed operation in a VPN. The port
uses static routing or a routing protocol (RIP, OSPF, EIGRP, or BGP) to forward packets. MP-BGP is
configured over the PE1 switch ES port with a route distinguisher that is associated with the customer’s
VPN. MP-BGP is configured to redistribute the routes and their associated VPN labels over the ES port
that is using this route distinguisher.
The packet flow follows these steps:
Step 1 Provider-edge switch PE1 (which could be a Catalyst 3750 Metro switch) receives a packet from the
customer switch at site 1. The switch determines from the lookup table that the VRF is a VLAN running
MPLS and uses the MPLS lookup table to determine what to do with the packet. The MPLS lookup table
contains the peer LSR as the destination MAC address and the local interface as the source MAC address.
Step 2 PE1 finds a BGP route with the appropriate next hop and labels, adds the appropriate labels to the packet,
and forwards the packet out of the ES port to the next hop router (P3).
Step 3 The P3 router receives the packet and forwards it over the MPLS-VPN network, based on the packet’s
top label—the interior gateway protocol (IGP) label—and then removes the top label.
Step 4 PE3 receives the packet, removes the MPLS encapsulation, and forwards the packet by using the VRF
interface associated with the VPN label contained in the packet that has the customer-edge switch CE2
as the destination.
MPLS TE
MPLS traffic engineering (TE) provides control over how traffic is routed through the network. This
increases the bandwidth efficiency by preventing over-use of some links while other links are under used.
TE overrides the shortest path selected by the Interior Gateway Protocol (IGP) to select the most efficient
path for traffic. Network resources are advertised by using a link-state routing protocol, such as
Intermediate System-to-Intermediate System (IS-IS) or Open Shortest Path First (OSPF). MPLS TE then
uses a unidirectional LSP or tunnel to forward traffic, calculating the tunnel paths based on required and
available resources.
Regular MPLS traffic engineering automatically establishes and maintains label-switched paths (LSPs)
across the backbone using Resource Reservation Protocol (RSVP). The path used by a given LSP is
based on the LSP resource requirements and available network resources such as bandwidth. Available
resources are flooded via extensions to the link-state based IGP.
For more information on MPLS TE, see this URL:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/12_4/mp_12_4_book.html
Paths for LSPs are calculated at the LSP headend, the first router in the LSP path. Under failure
conditions, the headend determines a new route for the LSP based on destination, bandwidth, link
attributes, and priority. RSVP-TE then establishes and maintains the TE tunnel across the MPLS
backbone network. Packets are switched inside the tunnel by using MPLS labels. Recovery at the
headend provides for the optimal use of resources.
The switch supports 250 tunnels in the TE headend and 2,000 tunnels at the midpoint.
The Catalyst 3750 Metro switch supports these MPLS TE features:
• OSPF, IS-IS, and RSVP extensions to support MPLS TE
• TE autotunnel primary and backup
• TE tunnel reoptimization to improve overall efficiency by rerouting some traffic trunks to new paths
• TE load sharing to a destination over paths with unequal costs. The switch supports up to 256
load-shared routes (load-shared routes for up to 256 destinations). Any additional load-balanced
routes are forwarded in one path in the hardware.
• TE IP explicit address exclusion to exclude a link or node from the path. You use the ip explicit-path
global configuration mode to enter explicit-path configuration mode and then use the
exclude-address command to specify addresses to exclude from the path.
• Support for LDP over TE tunnels for Layer 3 VPN traffic by entering the mpls ip interface
configuration command on the tunnel interface. The switch does not support LDP over TE tunnels
for Layer 2 VPN traffic.
• Traffic forwarding to the TE tunnel using static routing
• TE autoroute, which installs the routers announced by the tailend router and the downstream routers
into the routing table of the headend router. All traffic directed to prefixes beyond the tunnel end are
pushed into the tunnel.
The Catalyst 3750 Metro switch does not support these MPLS TE features:
• Interarea TE support for OSPF and IS-IS
• TE path protection
• Shared risk link group (SRLG)
• Traffic forwarding to the TE tunnel using policy routing
• Traffic forwarding to the TE tunnel using forwarding adjacency
• Auto bandwidth
• Autotunnel mesh group
Note Local reroute prevents any further packet loss caused by the failed link. If the tunnel is configured to be
dynamic, the headend of the tunnel then has time to reestablish the tunnel along a new, optimal route. If
the headend still cannot find another path to take, it continues to use the backup tunnel.
Fast link change detection (FLCD) and RSVP hello messages form the failure detection mechanism.
FLCD is notified when an interface encounters a link status change and RSVP hello enables the RSVP
nodes to detect when a neighboring node is not reachable. You can configure RSVP hello messages by
entering the ip rsvp signalling hello [fast reroute] refresh global configuration command.
Backup tunnels have these characteristics on the Catalyst 3750 Metro switch:
• A backup tunnel can protect multiple LSPs.
• When the primary tunnel restores, traffic changes from the backup tunnel back to the primary tunnel.
Configuring MPLS TE
For more information on MPLS TE, see this URL:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_te_diffserv_aw_ps6922_TSD_Pro
ducts_Configuration_Guide_Chapter.html
Beginning in privileged EXEC mode, follow these steps to configure MPLS TE and configure an
interface to support RSVP-based tunnel signalling and IGP flooding:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip cef distributed Enable CEF on the switch.
Step 3 mpls traffic-eng tunnels Enable MPLS traffic engineering tunnels on the switch.
Step 4 ip rsvp signalling hello Globally enable Hello signalling on the switch.
Step 5 interface interface-id Specify a physical interface and enter interface configuration mode.
Step 6 mpls traffic-eng tunnels Enable the MPLS traffic engineering tunnel feature on an interface.
Step 7 ip rsvp bandwidth bandwidth Enable RSVP for IP on an interface and the maximum amount of
bandwidth, in kb/s, that may be allocated by RSVP flows. The range
is from 1 to 10000000. The default is 75% of the link bandwidth.
Step 8 ip rsvp signalling hello Enable Hello signalling on the interface.
Step 9 end Return to privileged EXEC mode.
Step 10 show mpls traffic-eng tunnel Verify the configuration.
Step 11 copy running-config startup-config (Optional) Save your entries in the configuration file.
Enter no mpls traffic-eng tunnels to disable MPLS traffic engineering tunnels on the switch or
interface. Enter the no rsvp bandwidth interface configuration command to return to the default.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface tunnel tunnel-id Enter interface configuration mode for a tunnel interface.
Step 3 ip unnumbered loopback0 Configure the tunnel source address to be the IP address of the
loopback0 interface. The command is not effective until loopback0
is configured with an IP address.
Step 4 tunnel destination A.B.C.D Specify the destination for a tunnel.
Step 5 tunnel mode mpls traffic-eng Set the encapsulation mode of the tunnel to MPLS traffic
engineering.
Command Purpose
Step 6 tunnel mpls traffic-eng bandwidth Configure the bandwidth, in kb/s per second, set aside for the MPLS
bandwidth traffic engineering tunnel. The range is from 1 to 4294967295 kb/s.
The default is 0.
Step 7 tunnel mpls traffic-eng path-option 1 Configure a named IP explicit path.
explicit name name
Step 8 tunnel mpls traffic-eng path-option 2 Configure a backup path to be dynamically calculated from the
dynamic traffic engineering topology database.
Step 9 exit Return to global configuration mode.
Step 10 ip explicit-path name name Specify the IP explicit path name, and enter IP explicit path
configuration mode. An IP explicit path is a list of IP addresses, each
representing a node or link in the explicit path.
Step 11 next-address A.B.C.E Specify the next IP address in the explicit path.
Step 12 next-address A.B.C.F Specify the second IP address in the explicit path.
Step 13 exclude-address A.B.C.X (Optional) Exclude an address from the IP explicit path.
Step 14 end Return to privileged EXEC mode.
Step 15 show ip explicit-paths Verify the configuration.
Step 16 copy running-config startup-config (Optional) Save your entries in the configuration file.
Enter the no forms of the commands to remove the configured MPLS tunnels. Enter the no ip
explicit-path name global configuration command to disable IP explicit paths.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 router {isis | ospf} Enable IS-IS or OSPF routing, and enter router configuration mode.
Step 3 mpls traffic-eng level 1 Turn on MPLS traffic engineering for IS-IS level 1.
or
mpls traffic-eng area 0 Turn on MPLS traffic engineering for OSPF.
Step 4 mpls traffic-eng router-id loopback0 Specify the traffic engineering router identifier for the node to be the
IP address associated with interface loopback0.
Step 5 metric-style wide Configure a router to generate and accept only new-style stands for
type, length, and value objects (TLVs).
Note This command is for IS-IS routing only.
Step 6 end Return to privileged EXEC mode.
Step 7 show mpls traffic-eng Verify the configuration.
show ip ospf mpls traffic-eng
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove the traffic engineering router identifier, use the no mpls traffic-eng router-id command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface tunnel tunnel-number Create a tunnel interface, and enter interface configuration mode for
the tunnel interface.
Step 3 ip unnumbered interface-id Configure the tunnel source address. This is usually the IP address
of the loopback0 interface. The command is not effective until
loopback0 is configured with an IP address.
Step 4 tunnel destination A.B.C.D Specify the IP address of the device where the tunnel terminates.
This should be the router ID of the next-hop or next-next hop of the
LSP to be protected.
Step 5 tunnel mode mpls traffic-eng Set the mode of a tunnel to MPLS for traffic engineering.
Step 6 tunnel mpls traffic-eng path-option number Configure a path option for an MPLS TE tunnel. Keywords have
{dynamic | explicit {name path-name | these meanings:
path-number}} [lockdown]
• number—When multiple paths are configured, lower-numbered
options are preferred.
• dynamic—Specify that the LSP path is dynamically calculated.
• explicit—Specify that the LSP path is an explicit IP path.
• name path-name—Path name of the IP explicit path that the
tunnel uses with this option.
• name path-number—Path number of the IP explicit path that the
tunnel uses with this option.
• (Optional) lockdown—Specify that the LSP cannot be
reoptimized.
Step 7 tunnel mpls traffic-eng fast-reroute Enable the MPLS TE tunnel to use an established backup tunnel in
the event of a link or node failure
Step 8 ip explicit-path name path-name Specify the path of the tunnel, and enter IP explicit path command
mode to set up or modify the explicit path. An IP explicit path is a
list of IP addresses, each representing a node or link in the explicit
path.
Step 9 next-address A.B.C.E Specify the next IP address in the explicit path.
Step 10 Repeat Step 8 for additional IP addresses in the path.
Command Purpose
Step 11 end Return to privileged EXEC mode.
Step 12 show ip explicit-paths Verify the configuration.
Step 13 copy running-config startup-config (Optional) Save your entries in the configuration file.
Enter the no tunnel mode mpls traffic-eng global configuration command to disable MPLS traffic
engineering or the no ip explicit-path global configuration command to remove the IP explicit path
configuration.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface ID of the protected link and enter interface
configuration mode.
Step 3 mpls traffic-eng backup-path tunnel Configure the interface to use a backup tunnel in the event of a
tunnel-id detected failure on that interface. You can enter this command
multiple times to associate the protected interface with multiple
backup tunnels.
Step 4 end Return to privileged EXEC mode.
Step 5 show mpls traffic-eng fast-reroute Verify the that backup protection is configured. A ready status means
database that the tunnel is ready to switch to backup; an active status means
that tunnel traffic is on backup.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove the backup tunnel configuration, enter the no mpls traffic-eng backup-path tunnel interface
configuration command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip rsvp signalling hello Globally enable Hello signalling on the switch.
Step 3 interface interface-id Specify an interface ID, and enter interface configuration mode.
Step 4 ip rsvp signalling hello fast-reroute refresh Configure the number of consecutive RSVP TE hello
misses number acknowledgments a node can miss before the node communication
with its neighbor status is down. Valid values are from 4 to 10. The
default is 4.
Command Purpose
Step 5 ip rsvp signalling hello fast-reroute refresh Configure the frequency, in milliseconds, at which a node sends
interval interval-value hello messages to a neighbor. Valid values are from 10 to 30000 (.01
to 30 seconds). The default frequency is 1000 milliseconds (10
seconds).
Note To prevent false detection of a down neighbor and
unnecessarily triggering fast reroute, we recommend
configuring a minimum frequency of 200 ms.
Step 6 ip rsvp signalling hello Enable Hello signalling on the interface.
Step 7 end Return to privileged EXEC mode.
Step 8 show ip rsvp fast-reroute Verify the configuration.
show ip rsvp hello instance summary
Step 9 copy running-config startup-config (Optional) Save your entries in the configuration file.
Enter the no ip rsvp signalling hello global configuration command to disable Hello signalling on the
switch. Enter the no ip rsvp signalling hello fast-reroute refresh misses or the no ip rsvp signalling
hello fast-reroute refresh interval interface configuration command to set the misses or refresh interval
to the default.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 mpls traffic-eng auto-tunnel primary Configure the switch to automatically create primary MPLS tunnels
onehop to all next hops.
Step 3 mpls traffic-eng auto-tunnel primary Configure the range of tunnel interface numbers for primary
tunnel-num [min num] [max num] autotunnels.
• (Optional) [min num]—Specify the minimum number of the
primary tunnels. Valid values are from 0 to 65535. The default
is 65436.
• (Optional) [max num]—Specify the maximum number of the
primary tunnels. The max number is the minimum number plus
99. Valid values are from 0 to 65535.
Step 4 mpls traffic-eng auto-tunnel primary Configure how many seconds after a failure primary autotunnels are
timers removal rerouted sec removed. Valid values are 30 to 604800. The default is 0.
Step 5 mpls traffic-eng auto-tunnel primary Enable IP processing on the specified interface without an explicit
config unnumbered interface-id address.
Command Purpose
Step 6 mpls traffic-eng auto-tunnel primary Enable Label Distribution Protocol (LDP) on primary autotunnels.
config mpls ip
Step 7 end Return to privileged EXEC mode.
Step 8 show interface tunnel tunnel-num Verify the configuration.
Step 9 copy running-config startup-config (Optional) Save your entries in the configuration file.
Enter the no form of each command to delete the tunnel or disable the feature or capability. To remove
all primary auto tunnels, enter the clear mpls traffic-eng auto-tunnel primary privileged EXEC
command.
Beginning in privileged EXEC mode, follow these steps to establish MPLS backup auto tunnels:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 mpls traffic-eng auto-tunnel backup Configure the switch to automatically create next-hop (NHOP) and
next-next hop (NNHOP) backup tunnels.
Step 3 mpls traffic-eng auto-tunnel backup Configure the switch to automatically build only next-hop (NHOP)
nhop-only backup tunnels.
Step 4 mpls traffic-eng auto-tunnel backup timers Configure how frequently (in seconds) a timer scans the backup
removal unused sec autotunnels and removes tunnels that are not being used. Valid values
are 0 to 604800. The default is every 3600 seconds (60 minutes).
Step 5 mpls traffic-eng auto-tunnel backup config Enable IP processing without an explicit address.
unnumbered interface interface-id
interface interface-id is the interface on which IP processing will be
enabled without an explicit address. The default interface is
Loopback0.
Step 6 mpls traffic-eng auto-tunnel primary Enable Label Distribution Protocol (LDP) on primary autotunnels.
config mpls ip
Step 7 end Return to privileged EXEC mode.
Step 8 show interface tunnel tunnel-num Verify the configuration.
Step 9 copy running-config startup-config (Optional) Save your entries in the configuration file.
Enter the no form of each command to delete the tunnel or disable the feature or capability.
• IP Service Level Agreements (IP SLAs) to monitor MPLS LSP networks and IP SLAs Health
Monitor to automatically generate LSP ping and traceroute to BGP VPN neighbors.
Note In Cisco IOS Release 12.2(37)SE, IP SLAs support implemented nonstandard IP SLAs
command-line interface commands, using the rtr global configuration command to put the
switch into response time reporter (RTR) configuration mode. Beginning with Cisco IOS
Release 12.2(40)SE, the switch uses the standard IP SLAs configuration commands, using the
ip sla global configuration command to put the switch into IP SLAs configuration mode. See
Chapter 41, “Configuring Cisco IOS IP SLAs Operations,” for more information on configuring
IP SLAs.
For more information about MPLS OAM, see the MPLS LSP Ping/Traceroute for LDP/TE, and LSP Ping
for VCCV feature guide at this URL:
http://www.cisco.com/en/US/docs/ios/12_4t/12_4t11/ht_lspng.html
Note The switch does not support all of the commands referenced in the MPLS LSP Ping/Traceroute feature
module. For a list of commands that are visible in the CLI help, but not supported on the switch, see
Appendix B, “Unsupported Commands in Cisco IOS Release12.2(58)SE.”
Beginning with Cisco IOS Release 12.2(40)SE, the switch supports these additional keywords for the
ping mpls and traceroute mpls privileged EXEC commands to support RFC4379:
• Entering the dsmap keyword with the ttl keyword to the ping command allows you configure a
MPLS echo request from the source router to expire at a transit router with a wildcard downstream
map to obtain downstream information from the transit router.
• Entering the flags fec keyword configures the source router to force the transit router to validate the
target forwarding equivalence class (FEC).
• Entering the force-explicit-null keyword adds a Null label to the end of the label stack to allow the
destination provider-edge device to distinguish between traffic that has been rejected by the
destination provider router and traffic that arrives untagged.
• Entering the interval keyword allows you to specify the echo request packet send interval.
• Entering the output interface interface-id keywords provides path information as input to the LDP
IPv4 ping and traceroute configuration to force echo packets through the same paths for more
detailed analysis for LSP debugging.
• Entering the repeat keyword specifies the number of retries attempted if an echo request times out
before an echo reply is received.
• To allow interoperability between these IETF RFC 4379 drafts, the revision keyword was added to
enable Cisco IOS releases to support the existing draft changes and any changes from future versions
of the IETF LSP Ping draft. The switch supports revision 2 and RFC 4329 Compliant.
In addition, these other features have been added:
• Echo request return codes have been enhanced for better fault isolation.
• You can use the no mpls oam global configuration command to disable the MPLS OAM subsystem
when MPLS is running.
• You can configure the maximum number of labels in a label stack for load balancing.
• The switch now supports LSP tree trace, using the trace mpls multipath. privileged EXEC
command to trace all possible paths of an LSP network between the ingress and egress routers by
using downstream mapping.
Enhancements to the IP SLAs MPLS LSP Health Monitor include:
• Entering the auto ip sla mpls-lsp-monitor global configuration command automatically configures
ping and traceroute boundaries
• Entering the path-discover command in auto IP SLA MPLS parameter configuration mode
configures equal cost multipath (ECMP) tree trace. VPN end points are automatically discovered
and ping or traceroute actions are automatically generated for each provider edge router.
• For more information on configuring the LSP Health Monitor, go to this URL:
http://www.cisco.com/en/US/docs/ios/12_2sx/12_2sxh/feature/guide/sxh_hmon.html
LSP Ping
MPLS LSP ping uses MPLS echo request and reply packets, similar to Internet Control Message
Protocol (ICMP) echo request and reply messages, to validate an LSP. ICMP echo request and reply
messages validate IP networks; MPLS OAM echo and reply messages validate MPLS LDP networks.
The LSP ping and trace functions use IPv4 UDP packets with UDP port number 3503. You can use
MPLS LSP ping to validate IPv4 LDP or Forwarding Equivalence Classes (FECs) by using the ping
mpls privileged EXEC command. The MPLS echo request packet is sent to a target router by using the
label stack associated with the FEC to be validated.
The source address of the LSP echo request is the IP address of the LDP router generating the LSP
request. The destination IP address is a 127.x.y.z/8 address, which prevents the IP packet from being
switched to its destination if the LSP is broken. The 127.0.0.x destination address range prevents the
OAM packets from exiting the egress provider-edge router, which keeps them from leaking from the
service-provider network to the customer network.
In response to an MPLS echo request, an MPLS echo reply is forwarded as an IP packet by using IP,
MPLS, or a combination of both. The source address of the MPLS echo-reply packet is an address
obtained from the router generating the echo reply. The destination address is the source address of the
router that originated the MPLS echo-request packet. The MPLS echo-reply destination port is the
echo-request source port.
LSP Traceroute
MPLS LSP traceroute also uses MPLS echo request and reply packets to validate an LSP. You can use
MPLS LSP traceroute to validate LDP IPv4 by using the trace mpls privileged EXEC command. The
traceroute time-to-live (TTL) settings force expiration of the TTL along an LSP. MPLS LSP traceroute
incrementally increases the TTL value in its MPLS echo requests (TTL = 1, 2, 3, 4) to discover the
downstream mapping of each successive hop. The transit router processing the MPLS echo request
returns an MPLS echo reply containing information about the transit hop in response to the TTL-expired
MPLS packet. The MPLS echo reply destination port is sent to the echo request source port.
information that contains subsets of the bitmap in a downstream map in an echo reply. The source router
uses the information in the echo reply to interrogate the next router. It interrogates each successive router
until it finds one bitmap setting that is common to all routers along the path.
You can manually configure tree trace by using downsteam mapping Type Length Values (TLVs). You
can also use the ECMP tree trace feature in the IP SLAs LSP Health Monitor. When you enter the
path-discover command in auto IP SLA MPLS parameter configuration mode, VPN end points are
automatically discovered and ping or traceroute actions are automatically generated for each provider
edge router. You can also use the LSP Health Monitor to configure multioperation scheduling.
For more information about LSP multipath tree trace, see this URL:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_em_multipath_tree_ps6922_TSD_
Products_Configuration_Guide_Chapter.html
Note The switch does not support traffic engineering FEC in this release.
• Because MPLS OAM detects problems in the MPLS LSP network, it is a useful tool when there is
a discrepancy between the MPLS LSP and IP networks or between the MPLS control plane and data
plane.
• When the Catalyst 3750 Metro switch is used as a provider router in the core and ECMP tree trace
is configured, the switch can force the LSP packet down only one path, the actual data path. This
limitation applies only to the Catalyst 3750 Metro switch.
Command Purpose
Step 1 ping mpls ipv4 Configure LSP IPv4 ping. The keywords have these meanings:
destination-address
• destination-address destination-mask—Specify the address and network
destination-mask [destination
mask of the target FEC.
address-start address-end
increment] [exp exp-bits] [interval • (Optional) destination address-start address-end increment —Enter the
ms] [pad pattern] [repeat count] destination 127 network address range.
[reply dscp dscp-value] [reply • (Optional) exp exp-bits—Specify the MPLS experimental-field value in
mode {ipv4 | router-alert}] the MPLS header for an echo reply. The range is from 0 to 7. The default
[revision {1 | 2 | 3}] [size is 0.
packet-size | sweep minimum
maximum size-increment] [source • (Optional) interval ms—Specify the time in milliseconds between
source-address] [timeout seconds] successive MPLS echo requests. The range is 0 to 3600000 ms; the default
[ttl time-to-live] [verbose] is 0 (no interval is configured).
[revision tlv-revision-number] • (Optional) pad pattern—Specify to use the pad TLV to fill the datagram
[force-explicit-null] [output so that the MPLS echo request is the specified size.
interface interface-id [nexthop
• (Optional) repeat count—Specify the number of times to resend the
ip-address]] [dsmap [hashkey
packet. The range is from 1 to 2147483647. If you do not enter the repeat
{none | ipv4 bitmap bitmap-size}
keyword, the packet is sent 5 times.
[flags fec]
• (Optional) reply dscp dscp-value—Specify a specific class of service
(CoS) in an echo reply by providing a differentiated services code point
(DSCP) value.
Command Purpose
• (Optional) reply mode {ipv4 | router-alert}—Specify the reply mode for
the echo request packet. Enter ipv4 to reply with an IPv4 UDP packet (the
default) or router-alert to reply with an IPv4 UDP packet with router
alert.
• (Optional) revision—Enter the IEFT MPLS ping draft revision number as
3 (for revision 2) or 4 (for RFC 4329 complaint).
• (Optional) size packet-size—Specify the size of the packet with the label
stack imposed as the number of bytes in each ping. The range is from 100
to 18024. The default is 100.
• (Optional) source source-address—Specify the source address or the
name. This is the destination address in the MPLS echo response. The
default address is loopback0.
• (Optional) sweep minimum maximum size-increment —Set a range packet
sizes to be sent, ranging from a start size to an end size. The lower
boundary of the sweep range depends on the LSP type. The range for the
minimum and maximum is 100 to 18024; the increment range is 1 to 8993.
• (Optional) timeout seconds—Specify the timeout interval for an MPLS
request packet. The range is from 0 to 3600 seconds. The default is 2
seconds.
• (Optional) ttl time-to-live—Specify a time-to-live value. The range is from
1 to 255.
• (Optional) verbose —Display the MPLS echo reply sender address of the
packet and return codes.
• (Optional) revision number—Enter a Cisco-TLV-revision-number, 1
through 4.
• (Optional) force-explicit-null—Add an explicit NULL label to the end of
the label stack.
• (Optional) output interface interface-id—Specify the output interface for
the echo request.
• (Optional) nexthop ip-address—Force packets to go through the specified
next-hop address.
• (Optional) dsmap—Request downstream mapping information from the
replying router.
• (Optional) hashkey—Specify downstream map multipath settings as
either none or ipv4 bitmap size (0 to 256).
• (Optional) flags fec—Request FEC stack checking at the transit router.
Command Purpose
Step 1 traceroute mpls ipv4 Configure LSP IPv4 traceroute. The keywords have these meanings:
destination-address destination-mask
• destination-address destination-mask—Specify the address and
[destination address-start address-end
network mask of the target FEC.
increment] [exp exp-bits] [reply dscp
dscp-value] [reply mode {ipv4 | • (Optional) destination address-start address-end increment —Enter
router-alert}] [revision {1 | 2 | 3}] the destination 127 network address range.
[source source-address] [timeout • (Optional) exp exp-bits—Specify the MPLS experimental field value
seconds] [ttl time-to-live] [verbose] in the MPLS header for an echo reply. The range is from 0 to 7. The
[revision tlv-revision-number] default is 0.
[force-explicit-null] [output interface
interface-id [nexthop ip-address]] [flags • (Optional) reply dscp dscp-value—Specify a specific class of
fec] service (CoS) in an echo reply by providing a differentiated services
code point (DSCP) value.
• (Optional) reply mode {ipv4 | router-alert}—Specify the reply
mode for the echo request packet. Enter ipv4 to reply with an IPv4
UDP packet (the default) or router-alert to reply with an IPv4 UDP
packet with router alert.
• (Optional) revision —Enter the draft revision number as 1, 2, or 3.
• (Optional) source source-address—Specify the source address or the
name. This is the destination address in the MPLS echo response.
The default address is loopback0.
• (Optional) timeout seconds—Specify the timeout interval for an
MPLS request packet. The range is from 0 to 3600 seconds. The
default is 2 seconds.
• (Optional) ttl time-to-live—Specify a time-to-live value. The range
is from 1 to 255.
• (Optional) verbose—Display the MPLS echo reply sender address of
the packet and return codes.
• (Optional) revision number—Enter a Cisco-TLV-revision-number, 1
through 4.
• (Optional) force-explicit-null—Add an explicit NULL label to the
end of the label stack.
• (Optional) output interface interface-id—Specify the output
interface for the echo request.
• (Optional) nexthop ip-address—Force packets to go through the
specified next-hop address.
• (Optional) flags fec—Request FEC stack checking at the transit
router.
Command Purpose
Step 1 ping mpls pseudowire ipv4-address vc-id Configure LSP ping over pseudowire. The keywords have these
[destination start-address [end-address meanings:
[address-increment]] [exp exp-bits]
• ipv4-address—Specify the IPv4 address of the peer.
[interval ms] [pad pattern] [repeat
count] [reply dscp dscp-value] [reply • vc-id—Specify virtual-circuit identification number. The range is
mode {ipv4 | router-alert}] [revision {1 from 1 to 4294967295.
| 2 | 3}] [size packet-size] [source • (Optional) destination start-address [end-address
source-address] [sweep minimum [increment]]—Enter the destination 127 network address or address
maximum size-increment] [timeout range with increment.
seconds] [verbose] [dsmap [hashkey
{none | ipv4 bitmap bitmap-size} [flags • (Optional) exp exp-bits—Specify the MPLS experimental-field
fec] value in the MPLS header. The range is from 0 to 7. The default is 0.
• (Optional) interval ms—Specify the time in milliseconds between
successive MPLS echo requests. The range is from 0 to 3600000;
the default is 0.
• (Optional) pad pattern—Specify that the pad TLV is used to fill the
datagram so that the MPLS echo request is the specified size.
• (Optional) repeat count—Specify the number of times to resend the
packet. The range is from 1 to 2147483647. The default is 1. If you
do not enter the repeat keyword, the same packet is sent 5 times.
• (Optional) reply dscp dscp-value—Specify a specific class of
service (CoS) in an echo reply by providing a differentiated services
code point (DSCP) value.
• (Optional) reply mode {ipv4 | router-alert}—Specify the reply
mode for the echo request packet. Enter ipv4 to reply with an IPv4
packet (the default) or router-alert to reply with an IPv4 UPD
packet with router alert. Router alert is type 2 AToM VCCV.
• (Optional) revision—Enter the IEFT MPLS ping draft revision
number as 1, 2, or 3.
• (Optional) size packet-size—Specify the size of the packet with the
label stack imposed as the number of bytes in each ping. The range
is from 40 to 18024. The default is 100.
• (Optional) sweep minimum maximum size-increment —Send a
number of packets of different sizes.
Command Purpose
Step 1 • (Optional) timeout seconds—Specify the timeout interval for an
MPLS request packet. The range is from 0 to 3600 seconds. The
default is 2 seconds.
• (Optional) verbose—Display the MPLS echo reply sender address
of the packet and return codes.
• (Optional) flags fec—Request FEC stack checking at the transit
router.
• (Optional) dsmap—Request downstream mapping information
from the replying router.
• (Optional) hashkey—Specify downstream map multipath settings
as either none or ipv4 bitmap size (0 to 256).
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 auto ip sla mpls-lsp-monitor operation-number Specify an LSP Health Monitor operation number and enter auto
IP SLA MPLS configuration mode. The operation number range
is from 1 to 2147483647.
Step 3 type {echo | pathEcho} {ipsla-vrf-all | vrf Configure the parameters of the LSP Health Monitor by
vpn-name} selecting the operation and entering auto IP SLAs MPLS
parameters configuration mode.
• echo—Select an LSP monitor ping operation.
• pathEcho—Select an LSP monitor traceroute operation.
• ipsla-vrf-all—Configure IP SLAs MPSL LSP monitor for
all VPNs.
• vrf vpn-name—Configure the IP SLAs LSP monitor for the
specified VPN.
Step 4 access-list access-list-number (Optional) Specify an access list to apply to LSP Health Monitor
operation.
Step 5 delete-scan-factor factor (Optional) Specify the number of times the LSP Health Monitor
checks the scan queue before automatically deleting IP SLAs
operations for BGP next-hop neighbors that are no longer valid.
The factor range is 0 to 2147483647. The default scan factor
is 1.
Note You must use the scan-interval command with this
command.
Step 6 exp exp-bits (Optional) Specify the experimental field value in the echo
request packet header. The range is 0 to 7; the default value is 0.
Step 7 force-explicit-null (Optional) Add an explicit null label to all echo request packets
of an IP SLAs operation.
Step 8 lsp-selector ip-address (Optional) Specify the local host IP address used to select the IP
SLAs operation LSP. The default is 127.0.0.1.
Command Purpose
Step 9 reply-dscp-bits dscp-value (Optional) Specify the differentiated services codepoint (DSCP)
value for an echo reply packet of an IP SLAs operation. The
default value is 0.
Step 10 reply-mode {ipv4 | router-alert} (Optional) Specify the IP SLAs echo request reply mode as ipv4
or router-alert. The default is IPv4 UDP packet.
Step 11 request-data-size bytes (Optional) Specify the protocol data size for an IP SLAs request
packet. The range is 100 to 1500; the default is 100 bytes.
Step 12 scan-interval minutes (Optional) Specifies the time interval (in minutes) at which the
LSP Health Monitor checks the scan queue for BGP next hop
neighbor updates. The range is 1 to 70560; the default is 240
minutes.
Step 13 secondary-frequency {both | connection-loss | (Optional) Set the secondary frequency (faster measurement
timeout} frequency frequency) to which an IP SLAs operation should change when
a reaction condition occurs. The frequency range is 1 to 604800.
Step 14 tag text (Optional) Create a user-specified identifier for an IP SLAs
operation.
Step 15 threshold milliseconds (Optional) Specify the rising threshold (hysteresis) that
generates a reaction event and stores history information for an
IP SLAs operation. The range is 0 to 2147483647; the default
is 5000 ms.
Step 16 timeout milliseconds (Optional) Specify the amount of time that the IP SLAs
operation waits for a response from its request packet. The range
is 0 to 604800000; the default value is 5000 ms.
Step 17 ttl time-to-live (Optional) Specify the maximum hop count for an IP SLAs echo
request packet. The range is 1 to 255.
Step 18 exit Exit IP SLAs MPLS LSP monitor path discover configuration
mode and return to auto IP SLA MPLS parameter configuration
mode.
Step 19 exit Exit auto IP SLA MPLS parameter configuration mode and
returns to global configuration mode.
Command Purpose
Step 20 auto ip sla mpls-lsp-monitor (Optional) Configure other LSP Health Monitor actions:
reaction-configuration operation-number react
• operation-number—Enter the operation number.
monitored-element [action-type option]
[threshold-type {consecutive [occurrences] | • react monitored-element—Specify the element to be
immediate | never}] monitored for violations. For example, enter
connectionLoss to configure a reaction to a 1-way
connection loss for the operation.
• (Optional) action-type option—Specify the action to take
when the threshold event occurs. For example, enter none
for no action or trapOnly to send an SMNP logging trap.
• (Optional) threshold-type—Specify when the action-type
occurs. These are the options:
– consecutive [occurrences]—When reaction conditions
are met consecutively for a specified number of times.
The valid range is from 1 to 16; the default is 5.
– (Optional) threshold-type immediate—When the
reaction conditions are met.
– (Optional) threshold-type never—Never. This is the
default threshold type.
Step 21 auto ip sla mpls-lsp-monitor schedule Schedule time parameters for the LSP Health Monitor.
operation-number schedule-period seconds
• operation number—Enter the operation number.
[frequency seconds] [start-time {hh:mm {:ss}
[month day | day month] | pending | now | after • schedule-period seconds—Enter the schedule period in
hh:mm:ss}] seconds. The range is 1 to 604800 seconds.
• (Optional) frequency seconds—Enter the frequency for
LSP monitoring in seconds. The range is 1 to 604800
seconds.
• (Optional) start-time—Enter the time for the operation to
begin collecting information:
– To start at a specific time, enter the hour, minute,
second (in 24-hour notation) and day of the month. If
no month is entered, the default is the current month.
– Enter pending to select no information being collected
until a start time is selected.
– Enter now to start the operation immediately.
– Enter after hh:mm:ss to indicate that the operation
should start after the entered time has elapsed.
Step 22 auto ip sla mpls-lsp-monitor reset (Optional) Reset LDP monitor group statistics.
Step 23 end Return to privileged EXEC mode.
Step 24 show ip sla mpls-lsp-monitor configuration Show the configured LSP monitoring operations.
[operation-number]
Step 25 copy running-config startup-config (Optional) Save your entries in the configuration file.
Step 26 show ip sla mpls-lsp-monitor summary Display a summary of IP SLAs LSP MPLS status.
Enter the no auto ip sla mpls-lsp-monitor operation-number global configuration command to delete
the operation.
This is an example of configuring the MPLS LSP Health Monitor for all VPNs:
Switch# config t
Switch(config)# auto ip sla mpls-lsp-monitor 1
Switch(config-auto-ip-sla-mpls)# type echo ipsla-vrf-all
Switch(config-auto-ip-sla-mpls-params)# timeout 1000
Switch(config-auto-ip-sla-mpls-params)# scan-interval 1
Switch(config-auto-ip-sla-mpls-params)# secondary-frequency connection-loss 10
Switch(config-auto-ip-sla-mpls-params)# secondary-frequency timeout 10
Switch(config-auto-ip-sla-mpls-params)# exit
Switch(config-auto-ip-sla-mpls) exit
Switch(config)# auto ip sla mpls-lsp-monitor reaction-configuration 1 react connectionLoss
threshold-type consecutive 3 action-type trapOnly
Switch(config)# auto ip sla mpls-lsp-monitor schedule 1 schedule-period 60 start-time now
Switch(config)# end
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip sla operation-number Enter an IP SLAs operation number and enter IP SLAs
configuration mode. The range is from 1 to 2147483647.
Step 3 mpls lsp {ping | trace} ipv4 destination_address Manually configure the IP SLAs LSP monitor. and enter IP
destination_mask [force-explicit-null] SLAs monitor LSP ping or trace configuration mode.
[lsp-selector ip_address] [reply dscp] [reply
• ping—Select an LSP monitor ping operation.
mode {ipv4 | router-alert}] [source_ipaddr
source_address] • trace—Select an LSP monitor traceroute operation.
• destination_address destination_mask—Enter the address
and network mask of the target.
• (Optional) force-explicit-null —Add an explicit NULL
label to the end of the label stack.
• (Optional) lsp-selector ip_address—Specify the local host
address used to select the LSP.
• (Optional) reply dscp dscp-value—Specify a specific class
of service (CoS) in an echo reply by providing a
differentiated services code point (DSCP) value.
• (Optional) reply mode {ipv4 | router-alert} —Specify the
reply mode for the echo request packet as ipv4 to reply
with an IPv4 UDP packet (the default) or router-alert to
reply with an IPv4 UDP packet with router alert.
• (Optional) source_ipaddr source_address —Specify the
source IP address of the echo request originator.
Step 4 exp exp-bits (Optional) Specify the experimental field value in the echo
request packet header. The range is 0 to 7; the default value is 0.
Command Purpose
Step 5 request-data-size bytes (Optional) Specify the protocol data size for an IP SLAs request
packet. The range is 100 to 1500; the default is 100 bytes.
Step 6 secondary-frequency {both | connection-loss | (Optional) Set the secondary frequency (faster measurement
timeout} frequency frequency) to which an IP SLAs operation should change when
a reaction condition occurs. The frequency range is 1 to
604800.
Step 7 tag text (Optional) Create a user-specified identifier for an IP SLAs
operation.
Step 8 threshold milliseconds (Optional) Specify the rising threshold (hysteresis) that
generates a reaction event and stores history information for an
IP SLAs operation. The range is 0 to 2147483647; the default
is 5000 ms.
Step 9 timeout milliseconds (Optional) Specify the amount of time that the IP SLAs
operation waits for a response from its request packet. The
range is 0 to 604800000; the default value is 5000 ms.
Step 10 ttl time-to-live (Optional) Specify the maximum hop count for an IP SLAs
echo request packet. The range is 1 to 255.
Step 11 exit Return to global configuration mode.
Step 12 ip sla schedule operation-number [ageout Schedule the time parameters for MPLS LSP monitoring.
seconds] [life {forever | seconds}] [recurring]
• operation-number—Enter the IP SLAs operation number.
[start-time {hh:mm {:ss} [month day | day month]
| pending | now | after hh:mm:ss}] • (Optional) ageout seconds—Enter the number of seconds
to keep the operation in memory when it is not actively
collecting information. The default is 0 seconds (never
ages out). The range is 0 to 2073600 seconds.
• (Optional) life—Set the operation to run indefinitely
(forever) or for a specific number of seconds. The range is
from 0 to 2147483647. The default is 3600 seconds (1
hour)
• (Optional) recurring—Set the probe to be automatically
scheduled every day.
• (Optional) start-time—Enter the time for the operation to
begin collecting information:
– To start at a specific time, enter the hour, minute,
second (in 24-hour notation) and day of the month. If
no month is entered, the default is the current month.
– Enter pending to select no information being collected
until a start time is selected.
– Enter now to start the operation immediately.
– Enter after hh:mm:ss to indicate that the operation
should start after the entered time has elapsed.
Step 13 end Return to privileged EXEC mode.
Step 14 show ip sla configuration [operation-number] Show the configured LSP monitoring operations.
Command Purpose
Step 15 copy running-config startup-config (Optional) Save your entries in the configuration file.
Step 16 show ip sla statistics [operation-number] Display the statistics of a scheduled LSP monitoring operation.
To remove an IP SLAs operation, enter the no ip sla operation-number global configuration command.
This is an example of manually configuring an MPLS LSP ping operation:
Switch# config t
Switch(config)# ip sla 1
Switch(config-ip-sla)# mpls lsp ping ipv4 192.168.1.4 255.255.255.255 lsp-selector
127.1.1.1
Switch(config-ip-sla-lspPing)# secondary-frequency connection-loss 30
Switch(config-ip-sla-lspPing)# secondary-frequency timeout 30
Switch(config-ip-sla-lspPing)# exit
Switch(config)# ip sla schedule 1 start-time now life forever
Switch(config)# exit
Command Purpose
Step 1 traceroute mpls multipath ipv4 Configure LSP LDP IPv4 traceroute. The keywords have these meanings:
destination-address destination-mask
• destination-address destination-mask—Specify the address and
[destination address-start address-end
network mask of the target FEC.
increment] [exp exp-bits] [reply dscp
dscp-value] [reply mode {ipv4 | • (Optional) destination address-start address-end increment —Enter
router-alert}] [revision {1 | 2 | 3}] the destination 127 network address range.
[source source-address] [timeout • (Optional) exp exp-bits—Specify the MPLS experimental field value
seconds] [ttl time-to-live] [verbose] in the MPLS header for an echo reply. The range is from 0 to 7. The
[revision tlv-revision-number] default is 0.
[force-explicit-null] [output interface
interface-id [nexthop ip-address]] [flags • (Optional) reply dscp dscp-value—Specify a specific class of
fec] service (CoS) in an echo reply by providing a differentiated services
code point (DSCP) value.
Command Purpose
• (Optional) reply mode {ipv4 | router-alert}—Specify the reply
mode for the echo request packet. Enter ipv4 to reply with an IPv4
UDP packet (the default) or router-alert to reply with an IPv4 UDP
packet with router alert.
• (Optional) revision —Enter the draft revision number as 1, 2, or 3.
• (Optional) source source-address—Specify the source address or the
name. This is the destination address in the MPLS echo response.
The default address is loopback0.
• (Optional) timeout seconds—Specify the timeout interval for an
MPLS request packet. The range is from 0 to 3600 seconds. The
default is 2 seconds.
• (Optional) ttl time-to-live—Specify a time-to-live value. The range
is from 1 to 255.
• (Optional) verbose—Display the MPLS echo reply sender address of
the packet and return codes.
• (Optional) revision number—Enter a Cisco-TLV-revision-number, 1
through 4.
• (Optional) force-explicit-null—Add an explicit NULL label to the
end of the label stack.
• (Optional) output interface interface-id—Specify the output
interface for the echo request.
• (Optional) nexthop ip-address—Force packets to go through the
specified next-hop address.
• (Optional) flags fec—Request FEC stack checking at the transit
router.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 auto ip sla mpls-lsp-monitor operation-number Specify an LSP Health Monitor operation number and enter
auto IP SLAs MPLS configuration mode. The operation
number range is from 1 to 2147483647.
Step 3 path-discover Enter IP SLAs MPLS LSP monitor path discover
configuration mode to configure sending MPLS trace down
all multiple paths (tree trace).
Step 4 force-explicit-null (Optional) Add an explicit null label to all echo request
packets of an IP SLAs Health Monitor operation.
Step 5 hours-or-statistics kept hours (Optional) Set the number of hours for which LSP discovery
group statistics are maintained for an LSP Health Monitor
operation.
Command Purpose
Step 6 interval milliseconds (Optional) Specify the time interval between MPLS echo
requests that are sent as part of the LSP discovery process for
an LSP Health Monitor operation.
Step 7 lsp-selector-base ip-address Optional) Specifies the base IP address used to select the
LSPs belonging to the LSP discovery groups of an LSP
Health Monitor operation.
Step 8 maximum-sessions (Optional) Set the number of concurrent active tree trace
request to be submitted. This is the maximum number of
BGP next hop neighbors that can be concurrently undergo-
ing LSP discovery for a single LSP Health Monitor opera-
tion.
Note Use careful consideration when configuring this
parameter to avoid a negative impact on the switch
CPU.
Step 9 scan-period minutes (Optional) Set a time period in minutes for completing tree
trace discovery. This is the amount of time after which the
LSP discovery process can restart for an LSP Health Monitor
operation.
Step 10 session timeout seconds (Optional) Set a timeout value in seconds for tree trace
requests. This is the amount of time the LSP discovery
process for an LSP Health Monitor operation waits for a
response to its LSP discovery request for a particular BGP
next hop neighbor.
Step 11 timeout seconds (Optional) Set the amount of time the LSP discovery process
for an LSP Health Monitor operation waits for a response to
its echo request packets.
Note Use careful consideration when configuring this
parameter to avoid a negative impact on the switch
CPU.
Step 12 exit Exit IP SLAs MPLS LSP monitor path discover configuration
mode and return to auto IP SLA MPLS parameter
configuration mode.
Step 13 exit Exit auto IP SLA MPLS parameter configuration mode and
returns to global configuration mode.
Command Purpose
Step 14{ auto ip sla mpls-lsp-monitor (Optional) Configure LSP Health Monitor tree trace actions:
reaction-configuration operation-number react lpd
• operation-number—Enter the Health Monitor tree-trace
{lpd-group [retry number] | tree-trace}
operation number.
[action-type trapOnly]
• react lpd—Specify LPD as the element to be monitored
for violations.
• lpd-group— Enable monitoring of LSP discovery group
status changes.
• retry number—Specify the number of times the
equal-cost multipaths belonging to an LSP discovery
group are retested when a failure is detected. The value
of the number argument is zero by default.
• tree-trace—Enable monitoring of situations where LSP
discovery to a BGP next hop neighbor fails.
• (Optional) action-type trapOnly—Specify the action to
take when the threshold event occurs as trapOnly to
send an SMNP logging trap.
Step 15 ip sla monitor logging traps (Optional) Enable the generation of SNMP system logging
messages specific to IP SLAs trap notifications.
Step 16 auto ip sla mpls-lsp-monitor schedule Schedule the time parameters for the LSP Health Monitor.
operation-number schedule-period seconds
• operation number—Enter the IP SLAs MPLS LSP
[frequency seconds] [start-time {hh:mm {:ss}
monitor operation number.
[month day | day month] | pending | now | after
hh:mm:ss}] • schedule-period seconds—Enter the schedule period in
seconds. The range is 1 to 604800 seconds.
• (Optional) frequency seconds—Enter the frequency for
LSP monitoring. The range is 1 to 604800 seconds.
• (Optional) start-time—Enter the time for the operation
to begin collecting information:
– To start at a specific time, enter the hour, minute,
second and day of the month. If no month is entered,
the default is the current month.
– Enter pending to select no information being
collected until a start time is selected.
– Enter now to start the operation immediately.
– Enter after hh:mm:ss to indicate that the operation
should start after the entered time has elapsed.
Step 17 end Return to privileged EXEC mode.
Step 18 show ip sla mpls-lsp-monitor configuration Show the configured LSP monitoring operations.
[operation-number]
Command Purpose
Step 19 copy running-config startup-config (Optional) Save your entries in the configuration file.
Step 20 show ip sla monitor mpls-lsp-monitor (Optional) Displays the statistics for IP SLAs operations
collection-statistics [group-id] belonging to an LSP discovery group of an LSP Health
Monitor operation.
show ip sla mpls-lsp-monitor lpd
operational-state Optional) Displays the operational status of the LSP
discovery groups belonging to an LSP Health Monitor
operation.
Note These commands are applicable only if the LSP
discovery option is enabled.
Understanding EoMPLS
Any Transport over MPLS () is a solution for transporting Layer 2 packets over an MPLS network,
allowing service providers to use the MPLS network to provide connectivity between customer sites with
existing Layer 2 networks. Instead of separate networks with network management environments,
service providers can use the MPLS network to transport all types of traffic for different customers. The
Catalyst 3750 Metro switch supports EoMPLS, a subset of AToM that uses a tunneling mechanism to
carry Layer 2 Ethernet traffic.
EoMPLS encapsulates Ethernet frames in MPLS packets and forwards them across the MPLS network.
Each frame is sent as a single packet, and the provider-edge (PE) routers connected to the backbone add
and remove labels as appropriate for packet encapsulation:
• The ingress PE router receives an Ethernet frame and encapsulates the packet by removing the
preamble, the start of frame delimiter (SFD), and the frame check sequence (FCS). The rest of the
packet header is not changed.
• The ingress PE router adds a point-to-point virtual connection label and a label switched path (LSP)
tunnel label for normal MPLS routing through the MPLS backbone.
• The network core routers use the LSP tunnel label to move the packet through the MPLS backbone
and do not distinguish Ethernet traffic from any other types of packets in the MPLS backbone.
• At the other end of the MPLS backbone, the egress PE router receives the packet and
de-encapsulates the packet by removing the LSP tunnel label if one is present. The PE router also
removes the virtual-connection label from the packet.
• The provider-edge router updates the header, if necessary, and sends the packet out the appropriate
interface to the destination switch.
The MPLS backbone uses the tunnel labels to send the packet between the PE routers. The egress PE
router uses the virtual-connection label to select the outgoing interface for the Ethernet packet. EoMPLS
tunnels are unidirectional; for bidirectional EoMPLS, you need to configure one tunnel in each direction.
The point-to-point virtual connection requires you to configure virtual-connection endpoints at the two
PE routers. Only the provider-edge routers at the ingress and egress points of the MPLS backbone are
aware of the virtual connections dedicated to transporting Layer 2 traffic. Other routers do not have table
entries for these virtual connections.
This section includes additional information about these topics:
• Interaction with Other Features, page 44-41
• EoMPLS Limitations, page 44-42
802.1Q 802.1Q
tunnel port tunnel port
Trunk MPLS label MPLS label Trunk
port applied removed port
By entering the mpls l2transport route or the xconnect interface configuration command on either a
VLAN for VLAN-based EoMPLS or an Ethernet port for port-based EoMPLS, you can configure an
EoMPLS tunnel to forward traffic based on either the customer VLAN or the Ethernet port.
• To forward IEEE 802.1Q tunnel-encapsulated traffic through the MPLS core to a specific recipient
on the other side of the MPLS network, configure port-based EoMPLS.
• To forward IEEE 802.1Q tunnel-encapsulated traffic from an access device to a provider-edge
router, configure VLAN-based EoMPLS.
EoMPLS Limitations
These restrictions apply to EoMPLS:
• EoMPLS requires that at least one of the two ES ports be configured for MPLS.
• MTU—EoMPLS does not support packet fragmentation and reassembly. Therefore, the maximum
transmission unit (MTU) of all intermediate links between endpoints must be sufficient to carry the
largest Layer 2 VLAN received. The ingress and egress provider-edge routers must have the same
MTU value.
• Address Format—All loopback addresses on provider-edge routers must be configured with 32-bit
masks to ensure proper operation of MPLS forwarding. OSPF requires the use of loopback
addresses.
• Packet Format—EoMPLS supports VLAN packets that conform to the IEEE 802.1Q standard. ISL
encapsulation is not supported between provider-edge and customer-edge routers.
• The maximum number of VLANs using EoMPLS on a switch is 1005.
• Layer 2 connection restrictions:
– You cannot have a direct Layer 2 connection between provider-edge routers with EoMPLS.
– You cannot have more than one Layer 2 connection between routers if those routers are
configured to transport Ethernet VLANs over the MPLS backbone. Adding a second Layer 2
connection causes the spanning-tree state to constantly toggle if you disable spanning tree on
the peer router.
• STP— Do not enable per-VLAN spanning-tree (PVST) on the VLAN configured for an EoMPLS
session. STP instances are not supported on this VLAN. All PVST bridge protocol data units
(BPDUs) coming in on the EoMPLS VLAN from the customer side are tunneled transparently as
data packets over to the EoMPLS pseudowire and vice-versa.
• Trunking—The native VLAN of a trunk cannot be an EoMPLS VLAN.
• You can enable EoMPLS on IEEE 802.1Q interfaces by using the mpls l2transport route or the
xconnect interface configuration command. Use the xconnect command if you want to configure
pseudowire redundancy.
Enabling EoMPLS
This section includes this information about configuring EoMPLS on a switch used as a provider-edge
router:
• Default EoMPLS Configuration, page 44-43
• EoMPLS Configuration Guidelines, page 44-43
• Configuring EoMPLS, page 44-44
• Packet Flow in an EoMPLS Network, page 44-45
• Configuring L2VPN Pseudowire Redundancy, page 44-46
For more information about EoMPLS commands, see the command reference for this release.
Configuring EoMPLS
You configure VLAN-based EoMPLS on a VLAN interface. When VLAN-based EoMPLS is enabled,
the switch associates the tunnel and virtual-connection labels based on the VLAN ID.
Beginning in privileged EXEC mode, follow these steps on the provider-edge routers to configure
EoMPLS to transport Layer 2 packets between two endpoints:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 mpls label protocol ldp Enable LDP for all interfaces. By default, TDP is enabled. This command
causes all interfaces to use LDP.
Step 3 interface loopback0 Enter interface configuration mode for a loopback interface.
Step 4 ip address ip-address subnet mask Assign an IP address to the loopback interface.
Step 5 exit Return to global configuration mode.
Step 6 mpls ldp router-id loopback0 force (Optional) Force the IP address of loopback interface 0 to be used as the
router ID.
Step 7 mac address-table learning (Optional) For port-based EoMPLS, enable MAC address learning on the
interface interface-id Layer 3 interface.
Step 8 interface interface-id Enter a Layer 3 VLAN (for VLAN-based EoMPLS) or the interface ID of a
standard port (for port-based EoMPLS), and enter interface configuration
mode.
Step 9 mpls l2transport route destination Configure the interface to transport the Layer 2 VLAN packets over MPLS.
vc-id
• destination—IP address of the provider-edge router at the other end of
or the virtual connection.
xconnect destination vc-id • vc-id—Unique value defined for the virtual connection. The VC-ID
encapsulation mpls connects the end points of the virtual connection and must be the same
on both ends of the connection. The range is from 1 to 4294967295.
Note Use the xconnect command if pseudowire redundancy is required.
Step 10 end Return to privileged EXEC mode.
Step 11 show mpls l2transport vc Verify the configuration.
Step 12 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no mpls l2transport route destination vc-id or no xconnect destination vc-id encapsulation
mpls interface command to delete the EoMPLS tunnel.
This example shows how to configure an EoMPLS tunnel between switch PE1’s VLAN 3 interface and
PE2’s VLAN 4 interface.
PE1 has an IP address 10.0.0.1/32, and PE2 has IP address 20.0.01/32. Both provider-edge routers are
configured with an MPLS connection to the MPLS core. The VC ID is 123.
Enter these commands on the PE1 switch:
Switch(config)# interface loopback0
Switch(config-if)# ip address 10.10.10.10 255.255.255.255
Switch(config-if)# exit
Switch(config)# interface vlan 3
Switch(config-if)# mpls l2transport route 20.0.0.1 123
EoMPLS Tunnel
VC Label
Tunnel
Label Remote Site
VLAN 7 MPLS
Assume that Host A is connected to the customer switch on VLAN 3 that has a trunk port connected to
PE1 configured for IEEE 802.1Q tagging. Host A sends a packet to Host B, using the specific values of
MAC addresses, labels, and VLANs shown in the figure. The customer switch tags the host packet and
forwards it over the trunk port to PE1.
The tagged packet is received on the customer-edge port that is configured for per-port EoMPLS
tunneling. The PE1 switch examines the packet headers and looks at the tables stored in the switch to
determine what to do with the packet. Because the port is configured for per-port EoMPLS tunneling,
the switch does not remove any VLAN tags that are in the packet, but assigns the packet to an internal
VLAN. Only the customer port and the ES port are configured with that internal VLAN, which makes
the PE1 ES port the only possible destination for the packet.
The ES port encapsulates the packet header with the tunnel label and the virtual-connection label and
forwards the packet to the next hop, in this case Router A, to send it across the MPLS network.
The router receives the packet and forwards it over the MPLS network to the remote PE2 switch. PE2
removes the MPLS encapsulation and sends the packet out the port associated with the
virtual-connection label. Customer Switch B removes the final VLAN tag and forwards the packet to the
remote host B.
VLAN-based EoMPLS packet flow is basically the same as port-based EoMPLS, except that the
customer VLAN is used instead of an internal VLAN. The PE1 switch looks up the customer VLAN ID
to determine that the packet is forwarded to the ES port, where the packets is again examined and
encapsulated with the tunnel label and virtual-connection label based on the EoMPLS for that VLAN.
X2 X4
X1 X3
L2VPN pseudowire redundancy provides the ability to ensure that the CE2 router in Figure 44-6 can
always maintain network connectivity, even if one or all of the failures in the figure occur. You can
configure a backup pseudowire so that if the primary pseudowire fails, the provider-edge router switches
to the backup pseudowire. You can configure the primary pseudowire to resume operation after it
restarts. You can also configure the network with redundant pseudowires and redundant network
elements (routers).
Figure 44-7 shows a network with redundant pseudowires and redundant attachment circuits. You can
also optionally configure the network with redundant CE routers and redundant PE routers.
Figure 44-7 L2 VPN Network with Redundant Pseudowires and Attachment Circuits
Primary
pseudowire
Redundant
CE1 PE1 PE2 attachment CE2
135058
circuits
Backup
pseudowire
Configuration Guidelines
Follow these guidelines when configuring L2 VPN pseudowire redundancy:
• The default Label Distribution Protocol (LDP) session hold-down timer enables the software to
detect failures in about 180 seconds. You can use the mpls ldp holdtime global configuration
command to configure the switch to detect failures more quickly.
• The primary and backup pseudowires must run the same type of transport service. You must
configure Any Transport over MPLS (AToM) on both the primary and backup pseudowires.
• L2VPN pseudowire redundancy does not support different pseudowire encapsulation types on the
MPLS pseudowire.
• L2VPN pseudowire redundancy does support setting the experimental (EXP) bit on the MPLS
pseudowire.
• The switch does not support LDP MAC address withdrawal.
• The mpls l2transport route command is not supported. Use the xconnect command instead.
• The backup pseudowire cannot be operational at the same time that the primary pseudowire is
operational. The backup pseudowire becomes active only after the primary pseudowire fails.
• VCCV is supported only on the active pseudowire.
• The switch does not support more than one backup pseudowire.
This example shows the output of the show mpls l2transport vc command when the primary attachment
circuit is up and the backup attachment circuit is available, but not currently selected.
Switch# show mpls l2transport vc
For a more detailed configuration example, see the configuration example for “Ethernet to VLAN over
AToM (Bridged): Example” in the L2VPN Interworking feature module.
Step 3 xconnect peer-router-id vcid encapsulation mpls Bind the attachment circuit to a pseudowire virtual circuit
pw-class pw-class name (VC) and enter xconnect configuration mode.
Note You must specify MPLS encapsulation. If you omit
the encapsulation mpls command as part of the
xconnect command, you receive an Incomplete
command error message.
Step 4 backup peer peer-router-ip-address vcid [pw-class Specify a redundant peer for the pseudowire VC. If you do
pw-class name] not specify a pw-class name, the value is inherited from the
parent.
Step 5 backup delay enable-delay {disable-delay | never} Specify the delays before pseudowire takeovers.
• enable-delay— Specify how long (in seconds) the
backup pseudowire VC waits to take over after the
primary pseudowire VC goes down. The range is 0 to 180
seconds; the default is 0.
• disable-delay— Specify how long (in seconds) the
primary pseudowire waits after it becomes active to take
over from the backup pseudowire. The range is 0 to 180
seconds; the default is 0.
• If you enter never, the switchback to the primary
pseudowire never occurs.
Step 6 end Return to privileged EXEC mode.
Step 7 show xconnect all Verify the configuration.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
This example shows how to configure pseudowire redundancy as a switchover to the peer with the IP
address 10.1.1.12 immediately when a failure occurs and to not switch back to the primary VC when it
becomes available.
Switch# config t
Switch(config)# interface gigabitethernet1/1/1
Switch (config-if)# xconnect 10.1.1.4 33 encapsulation mpls
Switch(config-if-xconn)# backup peer 10.1.1.2 33
Switch(config-if-xconn)# backup delay 0 never
Command Purpose
Step 1 xconnect backup force-switchover {interface Specify that the router should switch to the backup or to the
interface-id | peer ip-address voiced} primary pseudowire when the command is entered.
This command forces a switchover to the peer with the IP address 10.1.1.4 and VCID 33.
Switch# xconnect backup force-switchover peer 10.1.1.4 33
Command Purpose
show xconnect {all | interface | peer | primp} Display xconnect entries, interfaces, peers, and so on.
show mpls l2transport vc [detail] [summary] Display detailed or summary information about the active virtual
connections that are enabled to route Layer 2 packets on a
provider-edge device.
You can also use the xconnect logging redundancy global configuration command to track the status
of the xconnect redundancy group. The command generates messages during switchover events.
Note The switch supports only DSCP and IP precedence classification for MPLS and EoMPLS.
A service provider might also want to set a QoS value for an MPLS packet to a different value. Instead
of overwriting the value in the IP precedence field that belongs to a customer, the service provider can
set the MPLS experimental field. The IP header remains available for the customer’s use, and the QoS
of an IP packet is not changed as the packet travels through the MPLS network.
By choosing different values for the MPLS experimental field, you can mark packets based on their
characteristics, such as rate or type, so that packets have the priority that they require during periods of
congestion.
Figure 44-8 shows an MPLS network that connects two sites of an IP network that belongs to a customer.
MPLS MPLS
network network
IP IP
network network
PE1 PE2
Host A Host B
CE1 PE-CLE P1 P2 PE-CLE CE2
122012
Owned by
service provider
PE1 and PE2 are customer-located routers at the boundaries between the MPLS network and the IP
network and are the ingress and egress provider-edge devices. CE1 and CE2 are customer edge devices.
P1 and P2 are service provider routers within the core of the service-provider network.
Packets arrive as IP packets at PE1, the ingress provider-edge router, and PE1 sends the packets to the
MPLS network as MPLS packets. Within the service-provider network, there is no IP precedence field
for the queuing mechanism to look at because the packets are MPLS packets. The packets remain as
MPLS packets until they arrive at PE2, the egress provider-edge router. PE2 removes the label from each
packet and forwards the packets as IP packets.
MPLS QoS enables service providers to classify packets according to their type, input interface, and
other factors by setting (marking) each packet within the MPLS experimental field without changing the
IP precedence or DSCP field. You can use the IP Precedence or DSCP bits to specify the QoS for an IP
packet and use the MPLS experimental bits to specify the QoS for an MPLS packet. In an MPLS
network, configure the MPLS experimental field value at PE1 (the ingress router) to set the QoS value
in the MPLS packet.
It is important to assign the correct priority to a packet. The priority of a packet affects how the packet
is treated during periods of congestion. For example, service providers have service-level agreements
with customers that specify how much traffic the service provider has agreed to deliver. To comply with
the agreement, the customer must not send more than the agreed-upon rate. Packets are considered to be
in-rate or out-of-rate. If there is congestion in the network, out-of-rate packets might be dropped more
aggressively.
Note For MPLS and EoMPLS QoS, you can match only Layer 3 parameters (IP or DCSP values), not Layer 2
(CoS values).
Note The switch supports only DSCP and IP precedence classification for MPLS and EoMPLS.
• Configure a policy map to mark MPLS packets (write their classification into the MPLS
experimental field).
• Configure the input interface to attach the service policy.
Beginning in privileged EXEC mode, follow these steps to set the experimental bits for EoMPLS or
MPLS QoS:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 mls qos Enable QoS globally.
QoS runs from the default settings described in Chapter 34, “Configuring
QoS.”
Step 3 class-map class-map-name Specify the name of the traffic class, and enter class-map configuration
mode.
Step 4 match {ip dscp dscp-list | ip Specify the matching criteria for IEEE 802.1Q packets.
precedence ip-precedence-list}
• ip dscp dscp-list—list of up to eight IP DSCP values to match against
incoming packets. The range is 0 to 63.
• ip precedence ip-precedence-list—list of up to eight IP-precedence
values to match against incoming packets. Separate each value with
a space. The range is 0 to 7.
Note The switch does not support the cos and vlan keywords for MPLS
and EoMPLS.
Step 5 exit Return to global configuration mode.
Step 6 policy-map policy-map-name Specify the name of the traffic policy to configure, and enter policy-map
configuration mode.
Step 7 class class-name Specify the name of the predefined traffic class configured with the
class-map command, and enter policy-map class configuration mode.
Step 8 set mpls experimental exp-number Specify the value to which the MPLS bits are set if the packets match the
specified policy map. The range is 0 to 7.
Step 9 exit Return to policy-map configuration mode.
Step 10 exit Return to global configuration mode.
Step 11 interface interface-id Enter the interface ID, and enter interface configuration mode. The
interface should be the ES egress port of the ingress router.
Step 12 service-policy output policy-map-name Attach the specified policy map to the output interface.
Step 13 end Return to privileged EXEC mode.
Step 14 show policy-map [policy-map-name Verify the configuration.
[class class-map-name]]
show policy-map interface interface-id
Step 15 copy running-config startup-config (Optional) Save your entries in the configuration file.
To delete an existing policy map, use the no policy-map policy-map-name global configuration
command. To delete an existing class, use the no class class-name policy-map configuration command.
This example shows how to use class and policy maps to configure different experimental bit settings
for DSCP and IP precedence for MPLS QoS.
Switch(config)# class-map match-all gold-class
Switch(config-cmap)# match ip dscp 1
Switch(config-cmap)# exit
Switch(config)# class-map match-all silver-class
Switch(config-cmap)# match ip precedence 2
Switch(config-cmap)# exit
Command Purpose
clear mpls counters Clear MPLS forwarding counters.
clear mpls traffic-eng autotunnel primary Remove all primary auto tunnels and recreate them.
show interface tunnel tunnel-number Display information about the specified tunnel interface.
show ip explicit paths Display the configured IP explicit paths.
show ip rsvp fast reroute [detail] Display specific information for RSVP categories, including fast reroute.
show ip rsvp host Display RSVP terminal point information for receivers or senders
show isis database verbose Display information about the IS-IS database.
show isis mpls traffic-eng Display information about IS-IS MPLS traffic engineering.
show mpls forwarding-table Display the contents of the MPLS label forwarding information base
(LFIB).
show mpls interfaces Display information about interfaces that have been configured for label
switching.
show mpls ip binding Display specified information about label bindings learned by LDP.
Table 44-2 Commands for Displaying MPLS and EoMPLS Information (continued)
Command Purpose
show mpls l2transport vc [detail] [summary] Display detailed or summary information about the EoMPLS virtual
connections that have been enabled to route Layer 2 packets on a
provider-edge device.
show mpls l2transport vc [vc-id] [vc-id-min - Display information about the specified virtual connection or range of
vc-id-max] virtual-connections. The range is from 1 to 4294967295.
show mpls label range Display the range of local labels available for use on packet interfaces.
show mpls ldp backoff Display information about the configured session setup backoff
parameters and any potential LDP peers with which session setup
attempts are being throttled.
show mpls ldp bindings Display the contents of the label information base (LIB).
show mpls ldp discovery Display the status of the LDP discovery process.
show mpls ldp neighbor Display the status of LDP sessions.
show mpls ldp parameters Display current LDP parameters.
show mpls prefix-map Show the prefix map used to assign a QoS map to network prefixes that
match a standard IP access list.
show mpls traffic-eng autoroute Display tunnels announced to the IGP, including interface, destination,
and bandwidth.
show mpls traffic-eng fast-reroute database Display the contents of the Fast Reroute (FRR) database.
show mpls traffic-eng link-management Display link information about MPLS traffic engineering link
management.
show mpls traffic-eng topology Display the MPLS traffic engineering global topology as currently known
at a node.
show mpls traffic-eng tunnel Display information about MPLS traffic-engineering tunnels.
This chapter describes how to configure IP multicast routing on the Catalyst 3750 Metro switch. IP
multicasting is a more efficient way to use network resources, especially for bandwidth-intensive
services such as audio and video. IP multicast routing enables a host (source) to send packets to a group
of hosts (receivers) anywhere within the IP network by using a special form of IP address called the IP
multicast group address. The sending host inserts the multicast group address into the IP destination
address field of the packet, and IP multicast routers and multilayer switches forward incoming IP
multicast packets out all interfaces that lead to members of the multicast group. Any host, regardless of
whether it is a member of a group, can sent to a group. However, only the members of a group receive
the message.
Note For complete syntax and usage information for the commands used in this chapter, see the Cisco IOS IP
Command Reference, Volume 3 of 3: Multicast, Release 12.2.
• Distance Vector Multicast Routing Protocol (DVMRP) is used on the multicast backbone of the
Internet (MBONE). The software supports PIM-to-DVMRP interaction.
• Cisco Group Management Protocol (CGMP) is used on Cisco routers and multilayer switches
connected to Layer 2 Catalyst switches to perform tasks similar to those performed by IGMP.
Figure 45-1 shows where these protocols operate within the IP multicast environment.
Internet
MBONE
Cisco Catalyst switch
(CGMP client) DVMRP
CGMP
Host
PIM
Host
44966
IGMP
According to IPv4 multicast standards, the MAC destination multicast address begins with 0100:5e and
is appended by the last 23 bits of the IP address. On the Catalyst 3750 Metro switch, if the multicast
packet does not match the switch multicast address, the packets are treated in this way:
• If the packet has a multicast IP address and a unicast MAC address, the packet is forwarded in
software. This can occur because some protocols on legacy devices use unicast MAC addresses with
multicast IP addresses.
• If the packet has a multicast IP address and an unmatched multicast MAC address, the packet is
dropped.
This section includes this information:
• Understanding IGMP, page 45-2
• Understanding PIM, page 45-3
• Understanding DVMRP, page 45-8
• Understanding CGMP, page 45-9
Understanding IGMP
To participate in IP multicasting, multicast hosts, routers, and multilayer switches must have the IGMP
operating. This protocol defines the querier and host roles:
• A querier is a network device that sends query messages to discover which network devices are
members of a given multicast group.
• A host is a receiver that sends report messages (in response to query messages) to inform a querier
of a host membership.
A set of queriers and hosts that receive multicast data streams from the same source is called a multicast
group. Queriers and hosts use IGMP messages to join and leave multicast groups.
Any host, regardless of whether it is a member of a group, can send to a group. However, only the
members of a group receive the message. Membership in a multicast group is dynamic; hosts can join
and leave at any time. There is no restriction on the location or number of members in a multicast group.
A host can be a member of more than one multicast group at a time. How active a multicast group is and
what members it has can vary from group to group and from time to time. A multicast group can be active
for a long time, or it can be very short-lived. Membership in a group can constantly change. A group that
has members can have no activity.
IP multicast traffic uses group addresses, which are class D addresses. The high-order bits of a Class D
address are 1110. Therefore, host group addresses can be in the range 224.0.0.0 through
239.255.255.255. Multicast addresses in the range 224.0.0.0 to 24.0.0.255 are reserved for use by
routing protocols and other network control traffic. The address 224.0.0.0 is guaranteed not to be
assigned to any group.
IGMP packets are sent using these IP multicast group addresses:
• IGMP general queries are destined to the address 224.0.0.1 (all systems on a subnet).
• IGMP group-specific queries are destined to the group IP address for which the switch is querying.
• IGMP group membership reports are destined to the group IP address for which the switch is
reporting.
• IGMP Version 2 (IGMPv2) leave messages are destined to the address 224.0.0.2
(all-multicast-routers on a subnet). In some old host IP stacks, leave messages might be destined to
the group IP address rather than to the all-routers address.
IGMP Version 1
IGMP Version 1 (IGMPv1) primarily uses a query-response model that enables the multicast router and
multilayer switch to find which multicast groups are active (have one or more hosts interested in a
multicast group) on the local subnet. IGMPv1 has other processes that enable a host to join and leave a
multicast group. For more information, see RFC 1112.
IGMP Version 2
IGMPv2 extends IGMP functionality by providing such features as the IGMP leave process to reduce
leave latency, group-specific queries, and an explicit maximum query response time. IGMPv2 also adds
the capability for routers to elect the IGMP querier without depending on the multicast protocol to
perform this task. For more information, see RFC 2236.
Understanding PIM
PIM is called protocol-independent: regardless of the unicast routing protocols used to populate the
unicast routing table, PIM uses this information to perform multicast forwarding instead of maintaining
a separate multicast routing table.
PIM is defined in RFC 2362, Protocol-Independent Multicast-Sparse Mode (PIM-SM): Protocol
Specification. PIM is defined in these Internet Engineering Task Force (IETF) Internet drafts:
• Protocol Independent Multicast (PIM): Motivation and Architecture
• Protocol Independent Multicast (PIM), Dense Mode Protocol Specification
PIM Versions
PIMv2 includes these improvements over PIMv1:
• A single, active rendezvous point (RP) exists per multicast group, with multiple backup RPs. This
single RP compares to multiple active RPs for the same group in PIMv1.
• A bootstrap router (BSR) provides a fault-tolerant, automated RP discovery and distribution
mechanism that enables routers and multilayer switches to dynamically learn the group-to-RP
mappings.
• Sparse mode and dense mode are properties of a group, as opposed to an interface. We strongly
recommend sparse-dense mode, as opposed to either sparse mode or dense mode only.
• PIM join and prune messages have more flexible encoding for multiple address families.
• A more flexible hello packet format replaces the query packet to encode current and future
capability options.
• Register messages to an RP specify whether they are sent by a border router or a designated router.
• PIM packets are no longer inside IGMP packets; they are standalone packets.
PIM Modes
PIM can operate in dense mode (DM), sparse mode (SM), or in sparse-dense mode (PIM DM-SM),
which handles both sparse groups and dense groups at the same time.
PIM DM
PIM DM builds source-based multicast distribution trees. In dense mode, a PIM DM router or multilayer
switch assumes that all other routers or multilayer switches forward multicast packets for a group. If a
PIM DM device receives a multicast packet and has no directly connected members or PIM neighbors
present, a prune message is sent back to the source to stop unwanted multicast traffic. Subsequent
multicast packets are not flooded to this router or switch on this pruned branch because branches without
receivers are pruned from the distribution tree, leaving only branches that contain receivers.
When a new receiver on a previously pruned branch of the tree joins a multicast group, the PIM DM
device detects the new receiver and immediately sends a graft message up the distribution tree toward
the source. When the upstream PIM DM device receives the graft message, it immediately puts the
interface on which the graft was received into the forwarding state so that the multicast traffic begins
flowing to the receiver.
PIM SM
PIM SM uses shared trees and shortest-path-trees (SPTs) to distribute multicast traffic to multicast
receivers in the network. In PIM SM, a router or multilayer switch assumes that other routers or switches
do not forward multicast packets for a group, unless there is an explicit request for the traffic (join
message). When a host joins a multicast group using IGMP, its directly connected PIM SM device sends
PIM join messages toward the root, also known as the RP. This join message travels router-by-router
toward the root, constructing a branch of the shared tree as it goes.
The RP keeps track of multicast receivers. It also registers sources through register messages received
from the source’s first-hop router (designated router [DR]) to complete the shared tree path from the
source to the receiver. When using a shared tree, sources must send their traffic to the RP so that the
traffic reaches all receivers.
Prune messages are sent up the distribution tree to prune multicast group traffic. This action permits
branches of the shared tree or SPT that were created with explicit join messages to be torn down when
they are no longer needed.
Switch
A
3.1.1.2.255.255.255.0
Port 25 Port 20
Source Router
200.1.1.3
202361
Host 1 Host 2
IGMP Helper
PIM stub routing moves routed traffic closer to the end user and reduces network traffic. You can also
reduce traffic by configuring a stub router (switch) with the IGMP helper feature.
You can configure a stub router (switch) with the igmp helper help-address interface configuration
command to enable the switch to send reports to the next-hop interface. Hosts that are not directly
connected to a downstream router can then join a multicast group sourced from an upstream network.
The IGMP packets from a host wanting to join a multicast stream are forwarded upstream to the next-hop
device when this feature is configured. When the upstream central router receives the helper IGMP
reports or leaves, it adds or removes the interfaces from its outgoing interface list for that group.
For complete syntax and usage information for the ip igmp helper-address command, see the Cisco IP
Multicast Command Reference:
http://www.cisco.com/en/US/docs/ios/ipmulti/command/reference/imc_book.html
Auto-RP
This proprietary feature eliminates the need to manually configure the RP information in every router
and multilayer switch in the network. For Auto-RP to work, you configure a Cisco router or multilayer
switch as the mapping agent. It uses IP multicast to learn which routers or switches in the network are
possible candidate RPs to receive candidate RP announcements. Candidate RPs periodically send
multicast RP-announce messages to a particular group or group range to announce their availability.
Mapping agents listen to these candidate RP announcements and use the information to create entries in
their Group-to-RP mapping caches. Only one mapping cache entry is created for any Group-to-RP range
received, even if multiple candidate RPs are sending RP announcements for the same range. As the
RP-announce messages arrive, the mapping agent selects the router or switch with the highest IP address
as the active RP and stores this RP address in the Group-to-RP mapping cache.
Mapping agents periodically multicast the contents of their Group-to-RP mapping cache. Thus, all
routers and switches automatically discover which RP to use for the groups they support. If a router or
switch fails to receive RP-discovery messages and the Group-to-RP mapping information expires, it
switches to a statically configured RP that was defined with the ip pim rp-address global configuration
command. If no statically configured RP exists, the router or switch changes the group to dense-mode
operation.
Multiple RPs serve different group ranges or serve as hot backups of each other.
Bootstrap Router
PIMv2 BSR is another method to distribute group-to-RP mapping information to all PIM routers and
multilayer switches in the network. It eliminates the need to manually configure RP information in every
router and switch in the network. However, instead of using IP multicast to distribute group-to-RP
mapping information, BSR uses hop-by-hop flooding of special BSR messages to distribute the mapping
information.
The BSR is elected from a set of candidate routers and switches in the domain that have been configured
to function as BSRs. The election mechanism is similar to the root-bridge election mechanism used in
bridged LANs. The BSR election is based on the BSR priority of the device contained in the BSR
messages that are sent hop-by-hop through the network. Each BSR device examines the message and
forwards out all interfaces only the message that has either a higher BSR priority than its BSR priority
or the same BSR priority, but with a higher BSR IP address. Using this method, the BSR is elected.
The elected BSR sends BSR messages with a TTL of 1. Neighboring PIMv2 routers or multilayer
switches receive the BSR message and multicast it out all other interfaces (except the one on which it
was received) with a TTL of 1. In this way, BSR messages travel hop-by-hop throughout the PIM
domain. Because BSR messages contain the IP address of the current BSR, the flooding mechanism
enables candidate RPs to automatically learn which device is the elected BSR.
Candidate RPs send candidate RP advertisements showing the group range for which they are
responsible to the BSR, which stores this information in its local candidate-RP cache. The BSR
periodically advertises the contents of this cache in BSR messages to all other PIM devices in the
domain. These messages travel hop-by-hop through the network to all routers and switches, which store
the RP information in the BSR message in their local RP cache. The routers and switches select the same
RP for a given group because they all use a common RP hashing algorithm.
Multicast Multicast
packet from packet from
source 151.10.3.21 source 151.10.3.21
is forwarded. packet is discarded.
101241
Table 45-1 Routing Table Example for an RPF Check
Network Port
151.10.0.0/16 Gigabit Ethernet 1/0/1
198.14.32.0/32 Gigabit Ethernet 1/1/1
204.1.16.0/24 Gigabit Ethernet 1/1/2
PIM uses both source trees and RP-rooted shared trees to forward datagrams (described in the “PIM
DM” section on page 45-4 and the “PIM SM” section on page 45-5). The RPF check is performed
differently for each:
• If a PIM router or multilayer switch has a source-tree state (that is, an (S,G) entry is present in the
multicast routing table), it performs the RPF check against the IP address of the source of the
multicast packet.
• If a PIM router or multilayer switch has a shared-tree state (and no explicit source-tree state), it
performs the RPF check on the RP address (which is known when members join the group).
Sparse-mode PIM uses the RPF lookup function to decide where it needs to send joins and prunes:
• (S,G) joins (which are source-tree states) are sent toward the source.
• (*,G) joins (which are shared-tree states) are sent toward the RP.
DVMRP and dense-mode PIM use only source trees and use RPF as previously described.
Understanding DVMRP
DVMRP is implemented in the equipment of many vendors and is based on the public-domain mrouted
program. This protocol has been deployed in the MBONE and in other intradomain multicast networks.
Cisco routers and multilayer switches run PIM and can forward multicast packets to and receive from a
DVMRP neighbor. It is also possible to propagate DVMRP routes into and through a PIM cloud. The
software propagates DVMRP routes and builds a separate database for these routes on each router and
multilayer switch, but PIM uses this routing information to make the packet-forwarding decision. The
software does not implement the complete DVMRP. However, it supports dynamic discovery of DVMRP
routers and can interoperate with them over traditional media (such as Ethernet and FDDI) or over
DVMRP-specific tunnels.
DVMRP neighbors build a route table by periodically exchanging source network routing information
in route-report messages. The routing information stored in the DVMRP routing table is separate from
the unicast routing table and is used to build a source distribution tree and to perform multicast forward
using RPF.
DVMRP is a dense-mode protocol and builds a parent-child database using a constrained multicast
model to build a forwarding tree rooted at the source of the multicast packets. Multicast packets are
initially flooded down this source tree. If redundant paths are on the source tree, packets are not
forwarded along those paths. Forwarding occurs until prune messages are received on those parent-child
links, which further constrain the broadcast of multicast packets.
Understanding CGMP
This software release provides CGMP-server support on your switch; no client-side functionality is
provided. The switch serves as a CGMP server for devices that do not support IGMP snooping but have
CGMP-client functionality.
CGMP is a protocol used on Cisco routers and multilayer switches connected to Layer 2 Catalyst
switches to perform tasks similar to those performed by IGMP. CGMP permits Layer 2 group
membership information to be communicated from the CGMP server to the switch. The switch can then
can learn on which interfaces multicast members reside instead of flooding multicast traffic to all switch
interfaces. (IGMP snooping is another method to constrain the flooding of multicast packets. For more
information, see Chapter 23, “Configuring IGMP Snooping and MVR.”)
CGMP is necessary because the Layer 2 switch cannot distinguish between IP multicast data packets and
IGMP report messages, which are both at the MAC-level and are addressed to the same group address.
CGMP is mutually exclusive with HSRPv1. You cannot enable CGMP leaving processing and HSRPv1
at the same time. However, you can enable CGMP and HSRPv2 at the same time. For more information,
see the “HSRP Versions” section on page 40-3.
Sparse-mode groups in a mixed PIMv1 and PIMv2 region are possible because the Auto-RP feature in
PIMv1 interoperates with the PIMv2 RP feature. Although all PIMv2 devices can also use PIMv1, we
recommend that the RPs be upgraded to PIMv2. To ease the transition to PIMv2, we have these
recommendations:
• Use Auto-RP throughout the region.
• Configure sparse-dense mode throughout the region.
If Auto-RP is not already configured in the PIMv1 regions, configure Auto-RP. For more information,
see the “Configuring Auto-RP” section on page 45-25.
Note If you enable PIM on multiple interfaces, when most of them are not on the outgoing interface list, and
IGMP snooping is disabled, the outgoing interface might not be able to sustain line rate for multicast
traffic because of the extra replication.
In populating the multicast routing table, dense-mode interfaces are always added to the table.
Sparse-mode interfaces are added to the table only when periodic join messages are received from
downstream devices or when there is a directly connected member on the interface. When forwarding
from a LAN, sparse-mode operation occurs if there is an RP known for the group. If so, the packets are
encapsulated and sent toward the RP. When no RP is known, the packet is flooded in a dense-mode
fashion. If the multicast traffic from a specific source is sufficient, the receiver’s first-hop router might
send join messages toward the source to build a source-based distribution tree.
By default, multicast routing is disabled, and there is no default mode setting. This procedure is required.
Beginning in privileged EXEC mode, follow these steps to enable IP multicasting, to configure a PIM
version, and to configure a PIM mode. This procedure is required.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip multicast-routing distributed Enable IP multicast distributed switching.
Step 3 interface interface-id Specify the Layer 3 interface on which you want to enable multicast
routing, and enter interface configuration mode.
The specified interface must be one of the following:
• A routed port: a physical port that has been configured as a Layer 3
port by entering the no switchport interface configuration
command.
• An SVI: a VLAN interface created by using the interface vlan
vlan-id global configuration command.
•
These interfaces must have IP addresses assigned to them. For more
information, see the “Configuring Layer 3 Interfaces” section on
page 9-17.
Step 4 ip pim version [1 | 2] Configure the PIM version on the interface.
By default, Version 2 is enabled and is the recommended setting.
An interface in PIMv2 mode automatically downgrades to PIMv1 mode
if that interface has a PIMv1 neighbor. The interface returns to Version 2
mode after all Version 1 neighbors are shut down or upgraded.
For more information, see the “PIMv1 and PIMv2 Interoperability”
section on page 45-10.
Step 5 ip pim {dense-mode | sparse-mode | Enable a PIM mode on the interface.
sparse-dense-mode}
By default, no mode is configured.
The keywords have these meanings:
• dense-mode—Enables dense mode of operation.
• sparse-mode—Enables sparse mode of operation. If you configure
sparse-mode, you must also configure an RP. For more information,
see the “Configuring a Rendezvous Point” section on page 45-23.
• sparse-dense-mode—Causes the interface to be treated in the mode
in which the group belongs. Sparse-dense-mode is the recommended
setting.
Command Purpose
Step 6 end Return to privileged EXEC mode.
Step 7 show running-config Verify your entries.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface on which you want to enable PIM stub routing, and
enter interface configuration mode.
Step 3 ip pim passive Configure the PIM stub feature on the interface.
Step 4 end Return to privileged EXEC mode.
Step 5 show ip pim interface Display the PIM stub that is enabled on each interface.
Step 6 show running-config Verify your entries.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable PIM stub routing on an interface, use the no ip pim passive interface configuration command.
In this example, IP multicast routing is enabled, Switch A PIM uplink port 25 is configured as a routed
uplink port with spare-dense-mode enabled. PIM stub routing is enabled on the VLAN 100 interfaces
and on Gigabit Ethernet port 20 in Figure 45-2:
Switch(config)# ip multicast-routing distributed
Switch(config)# interface GigabitEthernet1/0/25
Switch(config-if)# no switchport
Switch(config-if)# ip address 3.1.1.2 255.255.255.0
Switch(config-if)# ip pim sparse-dense-mode
Switch(config-if)# exit
Switch(config)# interface vlan100
Switch(config-if)# ip pim passive
Switch(config-if)# exit
Switch(config)# interface GigabitEthernet1/0/20
Switch(config-if)# ip pim passive
Switch(config-if)# exit
Switch(config)# interface vlan100
Switch(config-if)# ip address 100.1.1.1 255.255.255.0
Switch(config-if)# ip pim passive
Switch(config-if)# exit
Switch(config)# interface GigabitEthernet1/0/20
Switch(config-if)# no switchport
Switch(config-if)# ip address 10.1.1.1 255.255.255.0
Switch(config-if)# ip pim passive
Switch(config-if)# end
To verify that PIM stub is enabled for each interface, use the show ip pim interface privileged EXEC
command:
Switch# show ip pim interface
Address Interface Ver/ Nbr Query DR DR
Mode Count Intvl Prior
3.1.1.2 GigabitEthernet1/0/25 v2/SD 1 30 1 3.1.1.2
100.1.1.1 Vlan100 v2/P 0 30 1 100.1.1.1
10.1.1.1 GigabitEthernet1/0/20 v2/P 0 30 1 10.1.1.1
Use these privileged EXEC commands to display information about PIM stub configuration and status:
• show ip pim interface displays the PIM stub that is enabled on each interface.
• show ip igmp detail displays the interested clients that have joined the specific multicast source
group.
• show ip igmp mroute verifies that the multicast stream forwards from the source to the interested
clients.
SSM Operations
An established network, in which IP multicast service is based on PIM-SM, can support SSM services.
SSM can also be deployed alone in a network without the full range of protocols that are required for
interdomain PIM-SM (for example, MSDP, Auto-RP, or bootstrap router [BSR]) if only SSM service is
needed.
If SSM is deployed in a network already configured for PIM-SM, only the last-hop routers support SSM.
Routers that are not directly connected to receivers do not require support for SSM. In general, these
not-last-hop routers must only run PIM-SM in the SSM range and might need additional access control
configuration to suppress MSDP signalling, registering, or PIM-SM shared tree operations from
occurring within the SSM range.
Use the ip pim ssm global configuration command to configure the SSM range and to enable SSM. This
configuration has the following effects:
• For groups within the SSM range, (S, G) channel subscriptions are accepted through IGMPv3
include-mode membership reports.
• PIM operations within the SSM range of addresses change to PIM-SSM, a mode derived from
PIM-SM. In this mode, only PIM (S, G) join and prune messages are generated by the router, and
no (S, G) rendezvous point tree (RPT) or (*, G) RPT messages are generated. Incoming messages
related to RPT operations are ignored or rejected, and incoming PIM register messages are
immediately answered with register-stop messages. PIM-SSM is backward-compatible with
PIM-SM unless a router is a last-hop router. Therefore, routers that are not last-hop routers can run
PIM-SM for SSM groups (for example, if they do not yet support SSM).
• No MSDP source-active (SA) messages within the SSM range are accepted, generated, or
forwarded.
Configuration Guidelines
This section contains the guidelines for configuring SSM.
Existing applications in a network predating SSM do not work within the SSM range unless they are
modified to support (S, G) channel subscriptions. Therefore, enabling SSM in a network can cause
problems for existing applications if they use addresses within the designated SSM range.
Address management is still necessary to some degree when SSM is used with Layer 2 switching
mechanisms. Cisco Group Management Protocol (CGMP), IGMP snooping, or Router-Port Group
Management Protocol (RGMP) support only group-specific filtering, not (S, G) channel-specific
filtering. If different receivers in a switched network request different (S, G) channels sharing the same
group, they do not benefit from these existing mechanisms. Instead, both receivers receive all (S, G)
channel traffic and filter out the unwanted traffic on input. Because SSM can re-use the group addresses
in the SSM range for many independent applications, this situation can lead to decreased traffic filtering
in a switched network. For this reason, it is important to use random IP addresses from the SSM range
for an application to minimize the chance for re-use of a single address within the SSM range between
different applications. For example, an application service providing a set of television channels should,
even with SSM, use a different group for each television (S, G) channel. This setup guarantees that
multiple receivers to different channels within the same application service never experience traffic
aliasing in networks that include Layer 2 switches.
IGMPv3 uses new membership report messages that might not be correctly recognized by older IGMP
snooping switches.
For more information about switching issues related to IGMP (especially with CGMP), refer to the
“Configuring IGMP Version 3” section of the “Configuring IP Multicast Routing” chapter.
In PIM-SSM, the last hop router continues to periodically send (S, G) join messages if appropriate (S,
G) subscriptions are on the interfaces. Therefore, as long as receivers send (S, G) subscriptions, the
shortest path tree (SPT) state from the receivers to the source is maintained, even if the source does not
send traffic for longer periods of time (or even never).
This case is opposite to PIM-SM, where (S, G) state is maintained only if the source is sending traffic
and receivers are joining the group. If a source stops sending traffic for more than 3 minutes in PIM-SM,
the (S, G) state is deleted and only re-established after packets from the source arrive again through the
RPT. Because no mechanism in PIM-SSM notifies a receiver that a source is active, the network must
maintain the (S, G) state in PIM-SSM as long as receivers are requesting receipt of that channel.
Configuring SSM
Beginning in privileged EXEC mode, follow these steps to configure SSM:
Command Purpose
Step 1 ip pim ssm [default | range access-list] Define the SSM range of IP multicast addresses.
Step 2 interface type number Select an interface that is connected to hosts on which
IGMPv3 can be enabled, and enter the interface configuration
mode.
Step 3 ip pim {sparse-mode | sparse-dense-mode} Enable PIM on an interface. You must use either sparse mode
or sparse-dense mode.
Step 4 ip igmp version 3 Enable IGMPv3 on this interface. The default version of
IGMP is set to Version 2.
Monitoring SSM
Beginning in privileged EXEC mode, follow these steps to monitor SSM.
Command Purpose
Router# show ip igmp groups detail Display the (S, G) channel subscription through IGMPv3.
Router# show ip mroute Display whether a multicast group supports SSM service or
whether a source-specific host report was received.
Configuration Guidelines
These are the SSM mapping configuration guidelines:
• Before you configure SSM mapping, enable IP multicast routing, enable PIM sparse mode, and
configure SSM. For information on enabling IP multicast routing and PIM sparse mode, see the
“Default Multicast Routing Configuration” section on page 45-10.
• Before you configure static SSM mapping, you must configure access control lists (ACLs) that
define the group ranges to be mapped to source addresses. For information on configuring an ACL,
see Chapter 33, “Configuring Network Security with ACLs.”
• Before you can configure and use SSM mapping with DNS lookups, you must be able to add records
to a running DNS server. If you do not already have a DNS server running, you need to install one.
You can use a product such as Cisco Network Registrar. Go to this URL for more information:
http://www.cisco.com/en/US/products/sw/netmgtsw/ps1982/index.html
These are the SSM mapping restrictions:
• The SSM mapping feature does not have all the benefits of full SSM. Because SSM mapping takes
a group join from a host and identifies this group with an application associated with one or more
sources, it can only support one such application per group. Full SSM applications can still share
the same group as in SSM mapping.
• Enable IGMPv3 with care on the last hop router when you rely solely on SSM mapping as a
transition solution for full SSM. When you enable both SSM mapping and IGMPv3 and the hosts
already support IGMPv3 (but not SSM), the hosts send IGMPv3 group reports. SSM mapping does
not support these IGMPv3 group reports, and the router does not correctly associate sources with
these reports.
When the router receives an IGMPv1 or IGMPv2 membership report for a group, the router uses SSM
mapping to determine one or more source IP addresses for the group. SSM mapping then translates the
membership report as an IGMPv3 report and continues as if it had received an IGMPv3 report. The
router then sends PIM joins and continues to be joined to these groups as long as it continues to receive
the IGMPv1 or IGMPv2 membership reports, and the SSM mapping for the group remains the same.
SSM mapping enables the last hop router to determine the source addresses either by a statically
configured table on the router or through a DNS server. When the statically configured table or the DNS
mapping changes, the router leaves the current sources associated with the joined groups.
Go to this URL for additional information on SSM mapping:
http://www.cisco.com/en/US/docs/ios/12_3t/12_3t2/feature/guide/gtssmma.html
With static SSM mapping, you can configure the last hop router to use a static map to determine the
sources that are sending to groups. Static SSM mapping requires that you configure ACLs to define
group ranges. Then you can map the groups permitted by those ACLs to sources by using the ip igmp
static ssm-map global configuration command.
You can configure static SSM mapping in smaller networks when a DNS is not needed or to locally
override DNS mappings. When configured, static SSM mappings take precedence over DNS mappings.
You can use DNS-based SSM mapping to configure the last hop router to perform a reverse DNS lookup
to determine sources sending to groups. When DNS-based SSM mapping is configured, the router
constructs a domain name that includes the group address and performs a reverse lookup into the DNS.
The router looks up IP address resource records and uses them as the source addresses associated with
this group. SSM mapping supports up to 20 sources for each group. The router joins all sources
configured for a group (see Figure 45-4).
Source
(S, G) Join
(S, G) Join
DNS response DNS server
The SSM mapping mechanism that enables the last hop router to join multiple sources for a group can
provide source redundancy for a TV broadcast. In this context, the last hop router provides redundancy
using SSM mapping to simultaneously join two video sources for the same TV channel. However, to
prevent the last hop router from duplicating the video traffic, the video sources must use a server-side
switchover mechanism. One video source is active, and the other backup video source is passive. The
passive source waits until an active source failure is detected before sending the video traffic for the TV
channel. Thus, the server-side switchover mechanism ensures that only one of the servers is actively
sending video traffic for the TV channel.
To look up one or more source addresses for a group that includes G1, G2, G3, and G4, you must
configure these DNS records on the DNS server:
G4.G3.G2.G1 [multicast-domain] [timeout]IN A source-address-1
IN A source-address-2
IN A source-address-n
Refer to your DNS server documentation for more information about configuring DNS resource records,
and go to this URL for additional information on SSM mapping:
http://www.cisco.com/en/US/docs/ios/12_3t/12_3t2/feature/guide/gtssmma.html
Beginning in privileged EXEC mode, follow these steps to configure static SSM mapping:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip igmp ssm-map enable Enable SSM mapping for groups in the configured SSM range.
Note By default, this command enables DNS-based SSM mapping.
Step 3 no ip igmp ssm-map query dns (Optional) Disable DNS-based SSM mapping.
Note Disable DNS-based SSM mapping if you only want to rely on
static SSM mapping. By default, the ip igmp ssm-map global
configuration command enables DNS-based SSM mapping.
Command Purpose
Step 4 ip igmp ssm-map static access-list Configure static SSM mapping.
source-address
The ACL supplied for access-list defines the groups to be mapped to the
source IP address entered for the source-address.
Note You can configure additional static SSM mappings. If additional
SSM mappings are configured and the router receives an
IGMPv1 or IGMPv2 membership report for a group in the SSM
range, the switch determines the source addresses associated
with the group by using each configured ip igmp ssm-map
static command. The switch associates up to 20 sources per
group.
Step 5 Repeat Step 4 to configure additional —
static SSM mappings, if required.
Step 6 end Return to privileged EXEC mode.
Step 7 show running-config Verify your entries.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
To configure DNS-based SSM mapping, you need to create a DNS server zone or add records to an
existing zone. If the routers that are using DNS-based SSM mapping are also using DNS for other
purposes, you should use a normally configured DNS server. If DNS-based SSM mapping is the only
DNS implementation being used on the router, you can configure a false DNS setup with an empty root
zone or a root zone that points back to itself.
Beginning in privileged EXEC mode, follow these steps to configure DNS-based SSM mapping:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip igmp ssm-map enable Enable SSM mapping for groups in a configured SSM range.
Step 3 ip igmp ssm-map query dns (Optional) Enable DNS-based SSM mapping.
By default, the ip igmp ssm-map command enables DNS-based SSM
mapping. Only the no form of this command is saved to the running
configuration.
Note Use this command to re-enable DNS-based SSM mapping if
DNS-based SSM mapping is disabled.
Step 4 ip domain multicast domain-prefix (Optional) Change the domain prefix used by the switch for DNS-based
SSM mapping.
By default, the switch uses the ip-addr.arpa domain prefix.
Step 5 ip name-server server-address1 Specify the address of one or more name servers to use for name and
[server-address2... server-address6] address resolution.
Command Purpose
Step 6 Repeat Step 5 to configure additional —
DNS servers for redundancy, if required.
Step 7 end Return to privileged EXEC mode.
Step 8 show running-config Verify your entries.
Step 9 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use static traffic forwarding with SSM mapping to statically forward SSM traffic for certain groups.
Beginning in privileged EXEC mode, follow these steps to configure static traffic forwarding with SSM
mapping:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface type number Select an interface on which to statically forward traffic for a multicast
group using SSM mapping, and enter interface configuration mode.
Note Static forwarding of traffic with SSM mapping works with either
DNS-based SSM mapping or statically configured SSM
mapping.
Step 3 ip igmp static-group group-address Configure SSM mapping to statically forward a (S, G) channel from the
source ssm-map interface.
Use this command if you want to statically forward SSM traffic for
certain groups. Use DNS-based SSM mapping to determine the source
addresses of the channels.
Step 4 show running-config Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
Command Purpose
show ip igmp ssm-mapping Display information about SSM mapping.
show ip igmp ssm-mapping Display the sources that SSM mapping uses for a particular
group-address group.
show ip igmp groups [group-name | Display the multicast groups with receivers that are directly
group-address | interface-type connected to the router and that were learned through IGMP.
interface-number] [detail]
show host Display the default domain name, the style of name lookup
service, a list of name server hosts, and the cached list of
hostnames and addresses.
debug ip igmp group-address Display the IGMP packets received and sent and IGMP
host-related events.
Beginning in privileged EXEC mode, follow these steps to manually configure the address of the RP.
This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip pim rp-address ip-address Configure the address of a PIM RP.
[access-list-number] [override]
By default, no PIM RP address is configured. You must configure the IP
address of RPs on all routers and multilayer switches (including the RP).
If there is no RP configured for a group, the switch treats the group as
dense, using the dense-mode PIM techniques.
A PIM device can be an RP for more than one group. Only one RP address
can be used at a time within a PIM domain. The access-list conditions
specify for which groups the device is an RP.
• For ip-address, enter the unicast address of the RP in dotted-decimal
notation.
• (Optional) For access-list-number, enter an IP standard access list
number from 1 to 99. If no access list is configured, the RP is used for
all groups.
• (Optional) The override keyword means that if there is a conflict
between the RP configured with this command and one learned by
Auto-RP or BSR, the RP configured with this command prevails.
Step 3 access-list access-list-number {deny | Create a standard access list, repeating the command as many times as
permit} source [source-wildcard] necessary.
• For access-list-number, enter the access list number specified in
Step 2.
• The deny keyword denies access if the conditions are matched. The
permit keyword permits access if the conditions are matched.
• For source, enter the multicast group address for which the RP should
be used.
• (Optional) For source-wildcard, enter the wildcard bits in dotted
decimal notation to be applied to the source. Place ones in the bit
positions that you want to ignore.
Recall that the access list is always terminated by an implicit deny
statement for everything.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
Configuring Auto-RP
Auto-RP uses IP multicast to automate the distribution of group-to-RP mappings to all Cisco routers and
multilayer switches in a PIM network. It has these benefits:
• It is easy to use multiple RPs within a network to serve different group ranges.
• It provides load splitting among different RPs and arrangement of RPs according to the location of
group participants.
• It avoids inconsistent, manual RP configurations on every router and multilayer switch in a PIM
network, which can cause connectivity problems.
Note If you configure PIM in sparse mode or sparse-dense mode and do not configure Auto-RP, you must
manually configure an RP as described in the “Manually Assigning an RP to Multicast Groups” section
on page 45-23.
Note If routed ports are configured in sparse mode, Auto-RP can still be used if all devices are configured with
a manual RP address for the Auto-RP groups.
If you are setting up Auto-RP in a new internetwork, you do not need a default RP because you configure
all the interfaces for sparse-dense mode. Follow the process described in the next section “Adding
Auto-RP to an Existing Sparse-Mode Cloud” section on page 45-25. However, skip Step 3 to configure
a PIM router as the RP for the local group.
This section contains some suggestions for the initial deployment of Auto-RP into an existing
sparse-mode cloud to minimize disruption of the existing multicast infrastructure.
Beginning in privileged EXEC mode, follow these steps to deploy Auto-RP in an existing sparse-mode
cloud. This procedure is optional.
Command Purpose
Step 1 show running-config Verify that a default RP is already configured on all PIM devices and the
RP in the sparse-mode network. It was previously configured with the ip
pim rp-address global configuration command.
This step is not required for spare-dense-mode environments.
The selected RP should have good connectivity and be available across
the network. Use this RP for the global groups (for example 224.x.x.x
and other global groups). Do not reconfigure the group address range that
this RP serves. RPs dynamically discovered through Auto-RP take
precedence over statically configured RPs. Assume that it is desirable to
use a second RP for the local groups.
Step 2 configure terminal Enter global configuration mode.
Step 3 ip pim send-rp-announce interface-id Configure another PIM device to be the candidate RP for local groups.
scope ttl group-list access-list-number
• For interface-id, enter the interface type and number that identifies
interval seconds
the RP address. Valid interfaces include physical ports, port
channels, and VLANs.
• For scope ttl, specify the time-to-live value in hops. Enter a hop
count that is high enough so that the RP-announce messages reach
all mapping agents in the network. There is no default setting. The
range is 1 to 255.
• For group-list access-list-number, enter an IP standard access list
number from 1 to 99. If no access list is configured, the RP is used
for all groups.
• For interval seconds, specify how often the announcement messages
must be sent. The default is 60 seconds. The range is 1 to 16383.
Step 4 access-list access-list-number {deny | Create a standard access list, repeating the command as many times as
permit} source [source-wildcard] necessary.
• For access-list-number, enter the access list number specified in
Step 3.
• The deny keyword denies access if the conditions are matched. The
permit keyword permits access if the conditions are matched.
• For source, enter the multicast group address range for which the RP
should be used.
• (Optional) For source-wildcard, enter the wildcard bits in dotted
decimal notation to be applied to the source. Place ones in the bit
positions that you want to ignore.
Recall that the access list is always terminated by an implicit deny
statement for everything.
Command Purpose
Step 5 ip pim send-rp-discovery scope ttl Find a switch whose connectivity is not likely to be interrupted, and
assign it the role of RP-mapping agent.
For scope ttl, specify the time-to-live value in hops to limit the RP
discovery packets. All devices within the hop count from the source
device receive the Auto-RP discovery messages. These messages tell
other devices which group-to-RP mapping to use to avoid conflicts (such
as overlapping group-to-RP ranges). There is no default setting. The
range is 1 to 255.
Step 6 end Return to privileged EXEC mode.
Step 7 show running-config Verify your entries.
show ip pim rp mapping Display active RPs that are cached with associated multicast routing
entries.
show ip pim rp
Display the information cached in the routing table.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove the PIM device configured as the candidate RP, use the no ip pim send-rp-announce
interface-id global configuration command. To remove the switch as the RP-mapping agent, use the no
ip pim send-rp-discovery global configuration command.
This example shows how to send RP announcements out all PIM-enabled ports for a maximum of 31
hops. The IP address of port 1 is the RP. Access list 5 describes the group for which this switch serves
as RP:
Switch(config)# ip pim send-rp-announce gigabitethernet1/0/1 scope 31 group-list 5
Switch(config)# access-list 5 permit 224.0.0.0 15.255.255.255
Find whether the ip pim accept-rp command was previously configured throughout the network by
using the show running-config privileged EXEC command. If the ip pim accept-rp command is not
configured on any device, this problem can be addressed later. In those routers or multilayer switches
already configured with the ip pim accept-rp command, you must enter the command again to accept
the newly advertised RP.
To accept all RPs advertised with Auto-RP and reject all other RPs by default, use the ip pim accept-rp
auto-rp global configuration command. This procedure is optional.
If all ports are in sparse mode, use a default-configured RP to support the two well-known
groups 224.0.1.39 and 224.0.1.40. Auto-RP uses these two well-known groups to collect and distribute
RP-mapping information. When this is the case and the ip pim accept-rp auto-rp command is
configured, another ip pim accept-rp command accepting the RP must be configured as follows:
Switch(config)# ip pim accept-rp 172.10.20.1 1
Switch(config)# access-list 1 permit 224.0.1.39
Switch(config)# access-list 1 permit 224.0.1.40
You can add configuration commands to the mapping agents to prevent a maliciously configured router
from masquerading as a candidate RP and causing problems.
Beginning in privileged EXEC mode, follow these steps to filter incoming RP announcement messages.
This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip pim rp-announce-filter rp-list Filter incoming RP announcement messages.
access-list-number group-list
Enter this command on each mapping agent in the network. Without
access-list-number
this command, all incoming RP-announce messages are accepted by
default.
For rp-list access-list-number, configure an access list of candidate RP
addresses that, if permitted, is accepted for the group ranges supplied
in the group-list access-list-number variable. If this variable is
omitted, the filter applies to all multicast groups.
If more than one mapping agent is used, the filters must be consistent
across all mapping agents to ensure that no conflicts occur in the
Group-to-RP mapping information.
Step 3 access-list access-list-number {deny | Create a standard access list, repeating the command as many times as
permit} source [source-wildcard] necessary.
• For access-list-number, enter the access list number specified in
Step 2.
• The deny keyword denies access if the conditions are matched.
The permit keyword permits access if the conditions are matched.
• Create an access list that specifies from which routers and
multilayer switches the mapping agent accepts candidate RP
announcements (rp-list ACL).
• Create an access list that specifies the range of multicast groups
from which to accept or deny (group-list ACL).
• For source, enter the multicast group address range for which the
RP should be used.
• (Optional) For source-wildcard, enter the wildcard bits in dotted
decimal notation to be applied to the source. Place ones in the bit
positions that you want to ignore.
Recall that the access list is always terminated by an implicit deny
statement for everything.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
This example shows a sample configuration on an Auto-RP mapping agent that is used to prevent
candidate RP announcements from being accepted from unauthorized candidate RPs:
Switch(config)# ip pim rp-announce-filter rp-list 10 group-list 20
Switch(config)# access-list 10 permit host 172.16.5.1
Switch(config)# access-list 10 permit host 172.16.2.1
Switch(config)# access-list 20 deny 239.0.0.0 0.0.255.255
Switch(config)# access-list 20 permit 224.0.0.0 15.255.255.255
In this example, the mapping agent accepts candidate RP announcements from only two devices,
172.16.5.1 and 172.16.2.1. The mapping agent accepts candidate RP announcements from these two
devices only for multicast groups that fall in the group range of 224.0.0.0 to 239.255.255.255. The
mapping agent does not accept candidate RP announcements from any other devices in the network.
Furthermore, the mapping agent does not accept candidate RP announcements from 172.16.5.1
or 172.16.2.1 if the announcements are for any groups in the 239.0.0.0 through 239.255.255.255 range.
This range is the administratively scoped address range.
As IP multicast becomes more widespread, the chance of one PIMv2 domain bordering another PIMv2
domain is increasing. Because these two domains probably do not share the same set of RPs, BSR,
candidate RPs, and candidate BSRs, you need to constrain PIMv2 BSR messages from flowing into or
out of the domain. Allowing these messages to leak across the domain borders could adversely affect the
normal BSR election mechanism and elect a single BSR across all bordering domains and co-mingle
candidate RP advertisements, resulting in the election of RPs in the wrong domain.
Beginning in privileged EXEC mode, follow these steps to define the PIM domain border. This
procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface to be configured, and enter interface configuration
mode.
Step 3 ip pim bsr-border Define a PIM bootstrap message boundary for the PIM domain.
Enter this command on each interface that connects to other bordering
PIM domains. This command instructs the switch to neither send or
receive PIMv2 BSR messages on this interface as shown in Figure 45-5.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove the PIM border, use the no ip pim bsr-border interface configuration command.
PIMv2 sparse-mode
Configure the network Configure the
ip pim bsr-border ip pim bsr-border
command on BSR BSR command on
this interface. messages messages this interface.
Neighboring Neighboring
PIMv2 domain Layer 3 BSR Layer 3 PIMv2 domain
switch switch
101243
Defining the IP Multicast Boundary
You define a multicast boundary to prevent Auto-RP messages from entering the PIM domain. You
create an access list to deny packets destined for 224.0.1.39 and 224.0.1.40, which carry Auto-RP
information.
Beginning in privileged EXEC mode, follow these steps to define a multicast boundary. This procedure
is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 access-list access-list-number deny Create a standard access list, repeating the command as many times as
source [source-wildcard] necessary.
• For access-list-number, the range is 1 to 99.
• The deny keyword denies access if the conditions are matched.
• For source, enter multicast addresses 224.0.1.39 and 224.0.1.40,
which carry Auto-RP information.
• (Optional) For source-wildcard, enter the wildcard bits in dotted
decimal notation to be applied to the source. Place ones in the bit
positions that you want to ignore.
Recall that the access list is always terminated by an implicit deny
statement for everything.
Step 3 interface interface-id Specify the interface to be configured, and enter interface configuration
mode.
Step 4 ip multicast boundary Configure the boundary, specifying the access list you created in Step 2.
access-list-number
Step 5 end Return to privileged EXEC mode.
Step 6 show running-config Verify your entries.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove the boundary, use the no ip multicast boundary interface configuration command.
This example shows a portion of an IP multicast boundary configuration that denies Auto-RP
information:
Switch(config)# access-list 1 deny 224.0.1.39
Switch(config)# access-list 1 deny 224.0.1.40
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# ip multicast boundary 1
You can configure one or more candidate BSRs. The devices serving as candidate BSRs should have
good connectivity to other devices and be in the backbone portion of the network.
Beginning in privileged EXEC mode, follow these steps to configure your switch as a candidate BSR.
This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip pim bsr-candidate interface-id Configure your switch to be a candidate BSR.
hash-mask-length [priority]
• For interface-id, enter the interface on this switch from which the
BSR address is derived to make it a candidate. This interface must
be enabled with PIM. Valid interfaces include physical ports, port
channels, and VLANs.
• For hash-mask-length, specify the mask length (32 bits maximum)
that is to be ANDed with the group address before the hash function
is called. All groups with the same seed hash correspond to the same
RP. For example, if this value is 24, only the first 24 bits of the group
addresses matter.
• (Optional) For priority, enter a number from 0 to 255. The BSR with
the larger priority is preferred. If the priority values are the same,
the device with the highest IP address is selected as the BSR. The
default is 0.
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove this device as a candidate BSR, use the no ip pim bsr-candidate global configuration
command.
This example shows how to configure a candidate BSR, which uses the IP address 172.21.24.18 on a port
as the advertised BSR address, uses 30 bits as the hash-mask-length, and has a priority of 10.
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# ip address 172.21.24.18 255.255.255.0
Switch(config-if)# ip pim sparse-dense-mode
Switch(config-if)# ip pim bsr-candidate gigabitethernet1/0/2 30 10
You can configure one or more candidate RPs. Similar to BSRs, the RPs should also have good
connectivity to other devices and be in the backbone portion of the network. An RP can serve the entire
IP multicast address space or an interface on it. Candidate RPs send candidate RP advertisements to the
BSR. When deciding which devices should be RPs, consider these options:
• In a network of Cisco routers and multilayer switches where only Auto-RP is used, any device can
be configured as an RP.
• In a network that includes only Cisco PIMv2 routers and multilayer switches and with routers from
other vendors, any device can be used as an RP.
• In a network of Cisco PIMv1 routers, Cisco PIMv2 routers, and routers from other vendors,
configure only Cisco PIMv2 routers and multilayer switches as RPs.
Beginning in privileged EXEC mode, follow these steps to configure your switch to advertise itself as a
PIMv2 candidate RP to the BSR. This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip pim rp-candidate interface-id Configure your switch to be a candidate RP.
[group-list access-list-number]
• For interface-id, specify the interface whose associated IP address
is advertised as a candidate RP address. Valid interfaces include
physical ports, port channels, and VLANs.
• (Optional) For group-list access-list-number, enter an IP standard
access list number from 1 to 99. If no group-list is specified, the
switch is a candidate RP for all groups.
Step 3 access-list access-list-number {deny | Create a standard access list, repeating the command as many times as
permit} source [source-wildcard] necessary.
• For access-list-number, enter the access list number specified in
Step 2.
• The deny keyword denies access if the conditions are matched. The
permit keyword permits access if the conditions are matched.
• For source, enter the number of the network or host from which the
packet is being sent.
• (Optional) For source-wildcard, enter the wildcard bits in dotted
decimal notation to be applied to the source. Place ones in the bit
positions that you want to ignore.
Recall that the access list is always terminated by an implicit deny
statement for everything.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove this device as a candidate RP, use the no ip pim rp-candidate interface-id global
configuration command.
This example shows how to configure the switch to advertise itself as a candidate RP to the BSR in its
PIM domain. Standard access list number 4 specifies the group prefix associated with the RP that has
the address identified by a port. That RP is responsible for the groups with the prefix 239.
Switch(config)# ip pim rp-candidate gigabitethernet1/0/2 group-list 4
Switch(config)# access-list 4 permit 239.0.0.0 0.255.255.255
Command Purpose
Step 1 show ip pim rp [[group-name | On any Cisco device, display the available RP mappings.
group-address] | mapping]
• (Optional) For group-name, specify the name of the group about which to
display RPs.
• (Optional) For group-address, specify the address of the group about which
to display RPs.
• (Optional) Use the mapping keyword to display all group-to-RP mappings
of which the Cisco device is aware (either configured or learned from
Auto-RP).
Step 2 show ip pim rp-hash group On a PIMv2 router or multilayer switch, confirm that the same RP is the one that
a PIMv1 system chooses.
For group, enter the group address for which to display RP information.
Source
Router A Router B
Source tree
Shared tree
(shortest
from RP
path tree)
Router C RP
44967
Receiver
If the data rate warrants, leaf routers (routers without any downstream connections) on the shared tree
can use the data distribution tree rooted at the source. This type of distribution tree is called a
shortest-path tree or source tree. By default, the software switches to a source tree upon receiving the
first data packet from a source.
This process describes the move from a shared tree to a source tree:
1. A receiver joins a group; leaf Router C sends a join message toward the RP.
2. The RP puts a link to Router C in its outgoing interface list.
3. A source sends data; Router A encapsulates the data in a register message and sends it to the RP.
4. The RP forwards the data down the shared tree to Router C and sends a join message toward the
source. At this point, data might arrive twice at Router C, once encapsulated and once natively.
5. When data arrives natively (unencapsulated) at the RP, it sends a register-stop message to Router A.
6. By default, reception of the first data packet prompts Router C to send a join message toward the
source.
7. When Router C receives data on (S,G), it sends a prune message for the source up the shared tree.
8. The RP deletes the link to Router C from the outgoing interface of (S,G). The RP triggers a prune
message toward the source.
Join and prune messages are sent for sources and RPs. They are sent hop-by-hop and are processed by
each PIM device along the path to the source or RP. Register and register-stop messages are not sent
hop-by-hop. They are sent by the designated router that is directly connected to a source and are received
by the RP for the group.
Multiple sources sending to groups use the shared tree.
You can configure the PIM device to stay on the shared tree. For more information, see the “Delaying
the Use of PIM Shortest-Path Tree” section on page 45-36.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 access-list access-list-number {deny | Create a standard access list.
permit} source [source-wildcard]
• For access-list-number, the range is 1 to 99.
• The deny keyword denies access if the conditions are matched.
The permit keyword permits access if the conditions are
matched.
• For source, specify the multicast group to which the threshold
will apply.
• (Optional) For source-wildcard, enter the wildcard bits in dotted
decimal notation to be applied to the source. Place ones in the
bit positions that you want to ignore.
Recall that the access list is always terminated by an implicit deny
statement for everything.
Step 3 ip pim spt-threshold {kbps | infinity} Specify the threshold that must be reached before moving to
[group-list access-list-number] shortest-path tree (spt).
• For kbps, specify the traffic rate in kbps. The default is 0.
Note Because of Catalyst 3750 Metro switch hardware
limitations, 0 kbps is the only valid entry even though the
range is 0 to 4294967.
• Specify infinity if you want all sources for the specified group
to use the shared tree, never switching to the source tree.
• (Optional) For group-list access-list-number, specify the access
list created in Step 2. If the value is 0 or if the group-list is not
used, the threshold applies to all groups.
Command Purpose
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default setting, use the no ip pim spt-threshold {kbps | infinity} global configuration
command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface to be configured, and enter interface configuration
mode.
Step 3 ip pim query-interval seconds Configure the frequency at which the switch sends PIM router-query
messages.
The default is 30 seconds. The range is 1 to 65535.
Step 4 end Return to privileged EXEC mode.
Step 5 show ip igmp interface [interface-id] Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default setting, use the no ip pim query-interval [seconds] interface configuration
command.
Caution Performing this procedure might impact the CPU performance because the CPU will receive all data
traffic for the group address.
Beginning in privileged EXEC mode, follow these steps to configure the switch to be a member of a
group. This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface to be configured, and enter interface configuration
mode.
Step 3 ip igmp join-group group-address Configure the switch to join a multicast group.
By default, no group memberships are defined.
For group-address, specify the multicast IP address in dotted decimal
notation.
Step 4 end Return to privileged EXEC mode.
Step 5 show ip igmp interface [interface-id] Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To cancel membership in a group, use the no ip igmp join-group group-address interface configuration
command.
This example shows how to enable the switch to join multicast group 255.2.2.2:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# ip igmp join-group 255.2.2.2
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface to be configured, and enter interface
configuration mode.
Step 3 ip igmp access-group access-list-number Specify the multicast groups that hosts on the subnet serviced by an
interface can join.
By default, all groups are allowed on an interface.
For access-list-number, specify an IP standard access list number.
The range is 1 to 99.
Step 4 exit Return to global configuration mode.
Command Purpose
Step 5 access-list access-list-number {deny | Create a standard access list.
permit} source [source-wildcard]
• For access-list-number, specify the access list created in Step 3.
• The deny keyword denies access if the conditions are matched.
The permit keyword permits access if the conditions are
matched.
• For source, specify the multicast group that hosts on the subnet
can join.
• (Optional) For source-wildcard, enter the wildcard bits in dotted
decimal notation to be applied to the source. Place ones in the bit
positions that you want to ignore.
Recall that the access list is always terminated by an implicit deny
statement for everything.
Step 6 end Return to privileged EXEC mode.
Step 7 show ip igmp interface [interface-id] Verify your entries.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable groups on an interface, use the no ip igmp access-group interface configuration command.
This example shows how to configure hosts attached to a port as able to join only group 255.2.2.2:
Switch(config)# access-list 1 255.2.2.2 0.0.0.0
Switch(config-if)# interface gigabitethernet1/0/1
Switch(config-if)# ip igmp access-group 1
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface to be configured, and enter interface
configuration mode.
Step 3 ip igmp version {1 | 2} Specify the IGMP version that the switch uses.
Note If you change to Version 1, you cannot configure the ip igmp
query-interval or the ip igmp query-max-response-time
interface configuration commands.
Step 4 end Return to privileged EXEC mode.
Command Purpose
Step 5 show ip igmp interface [interface-id] Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default setting, use the no ip igmp version interface configuration command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface to be configured, and enter interface configuration
mode.
Step 3 ip igmp query-interval seconds Configure the frequency at which the designated router sends IGMP
host-query messages.
By default, the designated router sends IGMP host-query messages
every 60 seconds to keep the IGMP overhead very low on hosts and
networks. The range is 1 to 65535.
Step 4 end Return to privileged EXEC mode.
Step 5 show ip igmp interface [interface-id] Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default setting, use the no ip igmp query-interval interface configuration command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface to be configured, and enter interface configuration
mode.
Step 3 ip igmp querier-timeout seconds Specify the IGMP query timeout.
The default is 60 seconds (twice the query interval). The range is 60
to 300.
Step 4 end Return to privileged EXEC mode.
Step 5 show ip igmp interface [interface-id] Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default setting, use the no ip igmp querier-timeout interface configuration command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the port to be configured, and enter interface configuration
mode.
Step 3 ip igmp query-max-response-time Change the maximum query response time advertised in IGMP queries.
seconds The default is 10 seconds. The range is 1 to 25.
Step 4 end Return to privileged EXEC mode.
Step 5 show ip igmp interface [interface-id] Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default setting, use the no ip igmp query-max-response-time interface configuration
command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface to be configured, and enter interface configuration
mode.
Step 3 ip igmp static-group group-address Configure the switch as a statically connected member of a group.
By default, this feature is disabled.
Step 4 end Return to privileged EXEC mode.
Step 5 show ip igmp interface [interface-id] Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove the switch as a member of the group, use the no ip igmp static-group group-address interface
configuration command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface that is connected to the Layer 2 Catalyst switch, and
enter interface configuration mode.
Step 3 ip cgmp [proxy] Enable CGMP on the interface.
By default, CGMP is disabled on all interfaces.
Enabling CGMP triggers a CGMP join message. Enable CGMP only on
Layer 3 interfaces connected to Layer 2 Catalyst switches.
(Optional) When you enter the proxy keyword, the CGMP proxy function
is enabled. The proxy router advertises the existence of
non-CGMP-capable routers by sending a CGMP join message with the
non-CGMP-capable router MAC address and a group address
of 0000.0000.0000.
Note To perform CGMP proxy, the switch must be the IGMP querier. If
you configure the ip cgmp proxy command, you must manipulate
the IP addresses so that the switch is the IGMP querier, which
might be the highest or lowest IP address, depending on which
version of IGMP is running on the network. An IGMP Version 2
querier is selected based on the lowest IP address on the interface.
An IGMP Version 1 querier is selected based on the multicast
routing protocol used on the interface.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
Step 7 Verify the Layer 2 Catalyst switch CGMP-client configuration. For more
information, see the documentation that shipped with the product.
To disable CGMP on the interface, use the no ip cgmp interface configuration command.
When multiple Cisco CGMP-capable devices are connected to a switched network and the ip cgmp
proxy command is needed, we recommend that all devices be configured with the same CGMP option
and have precedence for becoming the IGMP querier over non-Cisco routers.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface to be enabled for sdr, and enter interface
configuration mode.
Step 3 ip sdr listen Enable sdr listener supinterface.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable sdr support, use the no ip sdr listen interface configuration command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip sdr cache-timeout minutes Limit how long an sdr cache entry stays active in the cache.
By default, entries are never deleted from the cache.
For minutes, the range is 1 to 4294967295.
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default setting, use the no ip sdr cache-timeout global configuration command. To
delete the entire cache, use the clear ip sdr privileged EXEC command.
To display the session directory cache, use the show ip sdr privileged EXEC command.
Note Multicast boundaries and TTL thresholds control the scoping of multicast domains; however, TTL
thresholds are not supported by the switch. You should use multicast boundaries instead of TTL
thresholds to limit the forwarding of multicast traffic outside of a domain or a subdomain.
Figure 45-7 shows that Company XYZ has an administratively-scoped boundary set for the multicast
address range 239.0.0.0/8 on all routed ports at the perimeter of its network. This boundary prevents any
multicast traffic in the range 239.0.0.0 through 239.255.255.255 from entering or leaving the network.
Similarly, the engineering and marketing departments have an administratively-scoped boundary of
239.128.0.0/16 around the perimeter of their networks. This boundary prevents multicast traffic in the
range of 239.128.0.0 through 239.128.255.255 from entering or leaving their respective networks.
Company XYZ
Engineering Marketing
45154
239.128.0.0/16
239.0.0.0/8
You can define an administratively-scoped boundary on a routed port for multicast group addresses. A
standard access list defines the range of addresses affected. When a boundary is defined, no multicast
data packets are allowed to flow across the boundary from either direction. The boundary allows the
same multicast group address to be reused in different administrative domains.
The IANA has designated the multicast address range 239.0.0.0 to 239.255.255.255 as the
administratively-scoped addresses. This range of addresses can then be reused in domains administered
by different organizations. The addresses would be considered local, not globally unique.
Beginning in privileged EXEC mode, follow these steps to set up an administratively-scoped boundary.
This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 access-list access-list-number {deny | Create a standard access list, repeating the command as many times as
permit} source [source-wildcard] necessary.
• For access-list-number, the range is 1 to 99.
• The deny keyword denies access if the conditions are matched. The
permit keyword permits access if the conditions are matched.
• For source, enter the number of the network or host from which the
packet is being sent.
• (Optional) For source-wildcard, enter the wildcard bits in dotted
decimal notation to be applied to the source. Place ones in the bit
positions that you want to ignore.
Recall that the access list is always terminated by an implicit deny
statement for everything.
Step 3 interface interface-id Specify the interface to be configured, and enter interface configuration
mode.
Step 4 ip multicast boundary Configure the boundary, specifying the access list you created in Step 2.
access-list-number
Step 5 end Return to privileged EXEC mode.
Step 6 show running-config Verify your entries.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove the boundary, use the no ip multicast boundary interface configuration command.
This example shows how to set up a boundary for all administratively-scoped addresses:
Switch(config)# access-list 1 deny 239.0.0.0 0.255.255.255
Switch(config)# access-list 1 permit 224.0.0.0 15.255.255.255
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# ip multicast boundary 1
Note The mrouted protocol is a public-domain implementation of DVMRP. You must use mrouted Version 3.8
(which implements a nonpruning version of DVMRP) when Cisco routers and multilayer switches are
directly connected to DVMRP routers or interoperate with DVMRP routers over an MBONE tunnel.
DVMRP advertisements produced by the Cisco IOS software can cause older versions of the mrouted
protocol to corrupt their routing tables and those of their neighbors.
You can configure what sources are advertised and what metrics are used by configuring the ip dvmrp
metric interface configuration command. You can also direct all sources learned through a particular
unicast routing process to be advertised into DVMRP.
Beginning in privileged EXEC mode, follow these steps to configure the sources that are advertised and
the metrics that are used when DVMRP route-report messages are sent. This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 access-list access-list-number {deny | Create a standard access list, repeating the command as many times as
permit} source [source-wildcard] necessary.
• For access-list-number, the range is 1 to 99.
• The deny keyword denies access if the conditions are matched. The
permit keyword permits access if the conditions are matched.
• For source, enter the number of the network or host from which the
packet is being sent.
• (Optional) For source-wildcard, enter the wildcard bits in dotted
decimal notation to be applied to the source. Place ones in the bit
positions that you want to ignore.
Recall that the access list is always terminated by an implicit deny
statement for everything.
Step 3 interface interface-id Specify the interface connected to the MBONE and enabled for
multicast routing, and enter interface configuration mode.
Step 4 ip dvmrp metric metric [list Configure the metric associated with a set of destinations for DVMRP
access-list-number] [[protocol process-id] reports.
| [dvmrp]]
• For metric, the range is 0 to 32. A value of 0 means that the route
is not advertised. A value of 32 is equivalent to infinity
(unreachable).
• (Optional) For list access-list-number, enter the access list number
created in Step 2. If specified, only the multicast destinations that
match the access list are reported with the configured metric.
• (Optional) For protocol process-id, enter the name of the unicast
routing protocol, such as eigrp, igrp, ospf, rip, static, or dvmrp,
and the process ID number of the routing protocol. If specified,
only routes learned by the specified routing protocol are advertised
in DVMRP report messages.
• (Optional) If specified, the dvmrp keyword allows routes from the
DVMRP routing table to be advertised with the configured metric
or filtered.
Step 5 end Return to privileged EXEC mode.
Step 6 show running-config Verify your entries.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable the metric or route map, use the no ip dvmrp metric metric [list access-list-number]
[[protocol process-id] | [dvmrp]] or the no ip dvmrp metric metric route-map map-name interface
configuration command.
A more sophisticated way to achieve the same results as the preceding command is to use a route map
(ip dvmrp metric metric route-map map-name interface configuration command) instead of an access
list. You subject unicast routes to route-map conditions before they are injected into DVMRP.
This example shows how to configure DVMRP interoperability when the PIM device and the DVMRP
router are on the same network segment. In this example, access list 1 advertises the networks
(198.92.35.0, 198.92.36.0, 198.92.37.0, 131.108.0.0, and 150.136.0.0) to the DVMRP router, and access
list 2 prevents all other networks from being advertised (ip dvmrp metric 0 interface configuration
command).
Switch(config-if)# interface gigabitethernet1/0/1
Switch(config-if)# ip address 131.119.244.244 255.255.255.0
Switch(config-if)# ip pim dense-mode
Switch(config-if)# ip dvmrp metric 1 list 1
Switch(config-if)# ip dvmrp metric 0 list 2
Switch(config-if)# exit
Switch(config)# access-list 1 permit 198.92.35.0 0.0.0.255
Switch(config)# access-list 1 permit 198.92.36.0 0.0.0.255
Switch(config)# access-list 1 permit 198.92.37.0 0.0.0.255
Switch(config)# access-list 1 permit 131.108.0.0 0.0.255.255
Switch(config)# access-list 1 permit 150.136.0.0 0.0.255.255
Switch(config)# access-list 1 deny 0.0.0.0 255.255.255.255
Switch(config)# access-list 2 permit 0.0.0.0 255.255.255.255
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 access-list access-list-number {deny | Create a standard access list, repeating the command as many times as
permit} source [source-wildcard] necessary.
• For access-list-number, the range is 1 to 99.
• The deny keyword denies access if the conditions are matched. The
permit keyword permits access if the conditions are matched.
• For source, enter the number of the network or host from which the
packet is being sent.
• (Optional) For source-wildcard, enter the wildcard bits in dotted
decimal notation to be applied to the source. Place ones in the bit
positions that you want to ignore.
Recall that the access list is always terminated by an implicit deny
statement for everything.
Step 3 interface tunnel number Specify a tunnel port, and enter interface configuration mode.
Step 4 tunnel source ip-address Specify the source address of the tunnel port. Enter the IP address of the
interface on the switch.
Step 5 tunnel destination ip-address Specify the destination address of the tunnel port. Enter the IP address
of the mrouted router.
Step 6 tunnel mode dvmrp Configure the encapsulation mode for the tunnel to DVMRP.
Step 7 ip address address mask Assign an IP address to the interface.
or or
ip unnumbered type number Configure the interface as unnumbered.
Step 8 ip pim [dense-mode | sparse-mode] Configure the PIM mode on the interface.
Step 9 ip dvmrp accept-filter Configure an acceptance filter for incoming DVMRP reports.
access-list-number [distance]
By default, all destination reports are accepted with a distance of 0.
neighbor-list access-list-number
Reports from all neighbors are accepted.
• For access-list-number, specify the access list number created in
Step 2. Any sources that match the access list are stored in the
DVMRP routing table with distance.
• (Optional) For distance, enter the administrative distance to the
destination. By default, the administrative distance for DVMRP
routes is 0 and take precedence over unicast routing table routes. If
you have two paths to a source, one through unicast routing (using
PIM as the multicast routing protocol) and another using DVMRP,
and if you want to use the PIM path, increase the administrative
distance for DVMRP routes. The range is 1 to 255.
• For neighbor-list access-list-number, enter the number of the
neighbor list created in Step 2. DVMRP reports are accepted only by
those neighbors on the list.
Step 10 end Return to privileged EXEC mode.
Command Purpose
Step 11 show running-config Verify your entries.
Step 12 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable the filter, use the no ip dvmrp accept-filter access-list-number [distance] neighbor-list
access-list-number interface configuration command.
This example shows how to configure a DVMRP tunnel. In this configuration, the IP address of the
tunnel on the Cisco switch is assigned unnumbered, which causes the tunnel to appear to have the same
IP address as port 1. The tunnel endpoint source address is 172.16.2.1, and the tunnel endpoint address
of the remote DVMRP router to which the tunnel is connected is 192.168.1.10. Any packets sent through
the tunnel are encapsulated in an outer IP header. The Cisco switch is configured to accept incoming
DVMRP reports with a distance of 100 from 198.92.37.0 through 198.92.37.255.
Switch(config)# ip multicast-routing
Switch(config)# interface tunnel 0
Switch(config-if)# ip unnumbered gigabitethernet1/0/1
Switch(config-if)# ip pim dense-mode
Switch(config-if)# tunnel source gigabitethernet1/0/1
Switch(config-if)# tunnel destination 192.168.1.10
Switch(config-if)# tunnel mode dvmrp
Switch(config-if)# ip dvmrp accept-filter 1 100
Switch(config-if)# interface gigabitethernet1/0/1
Switch(config-if)# ip address 172.16.2.1 255.255.255.0
Switch(config-if)# ip pim dense-mode
Switch(config)# exit
Switch(config)# access-list 1 permit 198.92.37.0 0.0.0.255
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface that is connected to the DVMRP router, and enter
interface configuration mode.
Step 3 ip dvmrp default-information Advertise network 0.0.0.0 to DVMRP neighbors.
{originate | only} Use this command only when the switch is a neighbor of mrouted version
3.6 machines.
The keywords have these meanings:
• originate—Specifies that other routes more specific than 0.0.0.0 can
also be advertised.
• only—Specifies that no DVMRP routes other than 0.0.0.0 are
advertised.
Command Purpose
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To prevent the default route advertisement, use the no ip dvmrp default-information interface
configuration command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface that is connected to the DVMRP router, and enter
interface configuration mode.
Step 3 ip dvmrp unicast-routing Enable DVMRP unicast routing (to send and receive DVMRP routes).
This feature is disabled by default.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable this feature, use the no ip dvmrp unicast-routing interface configuration command.
Source router or RP
Router A
Valid Router B
multicast
Receiver
traffic
Layer 3 switch
Unnecessary
multicast
traffic
Leaf nonpruning
DVMRP device
101244
You can prevent the switch from peering (communicating) with a DVMRP neighbor if that neighbor does
not support DVMRP pruning or grafting. To do so, configure the switch (which is a neighbor to the leaf,
nonpruning DVMRP machine) with the ip dvmrp reject-non-pruners interface configuration command
on the interface connected to the nonpruning machine as shown in Figure 45-9. In this case, when the
switch receives DVMRP probe or report message without the prune-capable flag set, the switch logs a
syslog message and discards the message.
Source router or RP
RP
Router A
Multicast
traffic gets Router B
to receiver, Receiver
not to leaf
DVMRP
device
Layer 3 switch
101245
Leaf nonpruning DVMRP device
Note that the ip dvmrp reject-non-pruners interface configuration command prevents peering with
neighbors only. If there are any nonpruning routers multiple hops away (downstream toward potential
receivers) that are not rejected, a nonpruning DVMRP network might still exist.
Beginning in privileged EXEC mode, follow these steps to prevent peering with nonpruning DVMRP
neighbors. This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface connected to the nonpruning DVMRP neighbor,
and enter interface configuration mode.
Step 3 ip dvmrp reject-non-pruners Prevent peering with nonpruning DVMRP neighbors.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable this function, use the no ip dvmrp reject-non-pruners interface configuration command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip dvmrp route-limit count Change the number of DVMRP routes advertised over an interface
enabled for DVMRP.
This command prevents misconfigured ip dvmrp metric interface
configuration commands from causing massive route injection into the
MBONE.
By default, 7000 routes are advertised. The range is 0 to 4294967295.
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To configure no route limit, use the no ip dvmrp route-limit global configuration command.
Beginning in privileged EXEC mode, follow these steps to change the threshold number of routes that
trigger the warning. This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip dvmrp routehog-notification Configure the number of routes that trigger a syslog message.
route-count
The default is 10,000 routes. The range is 1 to 4294967295.
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default setting use the no ip dvmrp routehog-notification global configuration
command.
Use the show ip igmp interface privileged EXEC command to display a running count of routes. When
the count is exceeded, *** ALERT *** is appended to the line.
Tunnel
86514
176.32.10.0/24 176.32.15.0/24
Beginning in privileged EXEC mode, follow these steps to customize the summarization of DVMRP
routes if the default classful autosummarization does not suit your needs. This procedure is optional.
Note At least one more-specific route must be present in the unicast routing table before a configured
summary address is advertised.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface that is connected to the DVMRP router, and enter
interface configuration mode.
Step 3 ip dvmrp summary-address address Specify a DVMRP summary address.
mask [metric value]
• For summary-address address mask, specify the summary IP
address and mask that is advertised instead of the more specific
route.
• (Optional) For metric value, specify the metric that is advertised
with the summary address. The default is 1. The range is 1 to 32.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove the summary address, use the no ip dvmrp summary-address address mask [metric value]
interface configuration command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface connected to the DVMRP router, and enter
interface configuration mode.
Step 3 no ip dvmrp auto-summary Disable DVMRP autosummarization.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To re-enable auto summarization, use the ip dvmrp auto-summary interface configuration command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the interface to be configured, and enter interface configuration
mode.
Command Purpose
Step 3 ip dvmrp metric-offset [in | out] Change the metric added to DVMRP routes advertised in incoming
increment interfaces.
The keywords have these meanings:
• (Optional) in—Specifies that the increment value is added to
incoming DVMRP reports and is reported in mrinfo replies.
• (Optional) out—Specifies that the increment value is added to
outgoing DVMRP reports for routes from the DVMRP routing
table.
If neither in nor out is specified, in is the default.
For increment, specify the value that is added to the metric of a DVMRP
router advertised in a report message. The range is 1 to 31.
If the ip dvmrp metric-offset command is not configured on an
interface, the default increment value for incoming routes is 1, and the
default for outgoing routes is 0.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default setting, use the no ip dvmrp metric-offset interface configuration command.
Command Purpose
clear ip cgmp Clear all group entries the Catalyst switches have
cached.
clear ip dvmrp route {* | route} Delete routes from the DVMRP routing table.
Table 45-5 Commands for Clearing Caches, Tables, and Databases (continued)
Command Purpose
clear ip igmp group [group-name | Delete entries from the IGMP cache.
group-address | interface]
clear ip mroute {* | group [source]} Delete entries from the IP multicast routing table.
clear ip pim auto-rp rp-address Clear the Auto-RP cache.
clear ip sdr [group-address | “session-name”] Delete the Session Directory Protocol Version 2
cache or an sdr cache entry.
You can display information to learn resource utilization and solve network problems. You can also
display information about node reachability and discover the routing path your device’s packets are
taking through the network.
You can use any of the privileged EXEC commands in Table 45-6 to display various routing statistics:
Command Purpose
ping [group-name | group-address] Send an ICMP Echo Request to a multicast group
address.
show ip dvmrp route [ip-address] Display the entries in the DVMRP routing table.
show ip igmp groups [group-name | Display the multicast groups that are directly
group-address | type number] connected to the switch and that were learned
through IGMP.
show ip igmp interface [type number] Display multicast-related information about an
interface.
show ip mcache [group [source]] Display the contents of the IP fast-switching
cache.
show ip mpacket [source-address | name] Display the contents of the circular cache-header
[group-address | name] [detail] buffer.
show ip mroute [group-name | group-address] Display the contents of the IP multicast routing
[source] [summary] [count] [active kbps] table.
show ip pim interface [type number] [count] Display information about interfaces configured
for PIM.
show ip pim neighbor [type number] List the PIM neighbors discovered by the switch.
show ip pim rp [group-name | group-address] Display the RP routers associated with a
sparse-mode multicast group.
Table 45-6 Commands for Displaying System and Network Statistics (continued)
Command Purpose
show ip rpf {source-address | name} Display how the switch is doing Reverse-Path
Forwarding (that is, from the unicast routing table,
DVMRP routing table, or static mroutes).
show ip sdr [group | “session-name” | detail] Display the Session Directory Protocol Version 2
cache.
Command Purpose
mrinfo [hostname | address] [source-address | Query a multicast router or multilayer switch about
interface] which neighboring multicast devices are peering
with it.
mstat source [destination] [group] Display IP multicast packet rate and loss
information.
mtrace source [destination] [group] Trace the path from a source to a destination
branch for a multicast distribution tree for a given
group.
This chapter describes how to configure the Multicast Source Discovery Protocol (MSDP) on the
Catalyst 3750 Metro switch. The MSDP connects multiple Protocol-Independent Multicast sparse-mode
(PIM-SM) domains.
MSDP is not fully supported in this software release because of a lack of support for Multicast Border
Gateway Protocol (MBGP), which works closely with MSDP. However, it is possible to create default
peers that MSDP can operate with if MBGP is not running.
Note For complete syntax and usage information for the commands used in this chapter, see the Cisco IOS IP
Command Reference, Volume 3 of 3: Multicast, Release 12.2.
Understanding MSDP
MSDP allows multicast sources for a group to be known to all rendezvous points (RPs) in different
domains. Each PIM-SM domain uses its own RPs and does not depend on RPs in other domains. An RP
runs MSDP over the TCP to discover multicast sources in other domains.
An RP in a PIM-SM domain has an MSDP peering relationship with MSDP-enabled devices in another
domain. The peering relationship occurs over a TCP connection, primarily exchanging a list of sources
sending to multicast groups. The TCP connections between RPs are achieved by the underlying routing
system. The receiving RP uses the source lists to establish a source path.
The purpose of this topology is to have domains discover multicast sources in other domains. If the
multicast sources are of interest to a domain that has receivers, multicast data is delivered over the
normal, source-tree building mechanism in PIM-SM. MSDP is also used to announce sources sending
to a group. These announcements must originate at the domain’s RP.
MSDP depends heavily on the Border Gateway Protocol (BGP) or MBGP for interdomain operation. We
recommend that you run MSDP in RPs in your domain that are RPs for sources sending to global groups
to be announced to the Internet.
MSDP Operation
Figure 46-1 shows MSDP operating between two MSDP peers. PIM uses MSDP as the standard
mechanism to register a source with the RP of a domain. When MSDP is configured, this sequence
occurs.
When a source sends its first multicast packet, the first-hop router (designated router or RP) directly
connected to the source sends a PIM register message to the RP. The RP uses the register message to
register the active source and to forward the multicast packet down the shared tree in the local domain.
With MSDP configured, the RP also forwards a source-active (SA) message to all MSDP peers. The SA
message identifies the source, the group the source is sending to, and the address of the RP or the
originator ID (the IP address of the interface used as the RP address), if configured.
Each MSDP peer receives and forwards the SA message away from the originating RP to achieve peer
reverse-path flooding (RPF). The MSDP device examines the BGP or MBGP routing table to discover
which peer is the next hop toward the originating RP of the SA message. Such a peer is called an RPF
peer (reverse-path forwarding peer). The MSDP device forwards the message to all MSDP peers other
than the RPF peer. For information on how to configure an MSDP peer when BGP and MBGP are not
supported, see the “Configuring a Default MSDP Peer” section on page 46-4.
If the MSDP peer receives the same SA message from a non-RPF peer toward the originating RP, it drops
the message. Otherwise, it forwards the message to all its MSDP peers.
The RP for a domain receives the SA message from an MSDP peer. If the RP has any join requests for
the group the SA message describes and if the (*,G) entry exists with a nonempty outgoing interface list,
the domain is interested in the group, and the RP triggers an (S,G) join toward the source. After the (S,G)
join reaches the source’s DR, a branch of the source tree has been built from the source to the RP in the
remote domain. Multicast traffic can now flow from the source across the source tree to the RP and then
down the shared tree in the remote domain to the receiver.
SA
P
SD
M
MSDP SA
TCP connection
BGP MSDP peer Receiver
Register
49885
Multicast
(S,G) Join
PIM
Source DR
PIM sparse-mode
domain
MSDP Benefits
MSDP has these benefits:
• It breaks up the shared multicast distribution tree. You can make the shared tree local to your
domain. Your local members join the local tree, and join messages for the shared tree never need to
leave your domain.
• PIM sparse-mode domains can rely only on their own RPs, decreasing reliance on RPs in another
domain. This increases security because you can prevent your sources from being known outside
your domain.
• Domains with only receivers can receive data without globally advertising group membership.
• Global source multicast routing table state is not required, saving memory.
Configuring MSDP
These sections describe how to configure MSDP:
• Default MSDP Configuration, page 46-4
• Configuring a Default MSDP Peer, page 46-4 (required)
• Caching Source-Active State, page 46-6 (optional)
• Requesting Source Information from an MSDP Peer, page 46-8 (optional)
• Controlling Source Information that Your Switch Originates, page 46-8 (optional)
• Controlling Source Information that Your Switch Forwards, page 46-11 (optional)
• Controlling Source Information that Your Switch Receives, page 46-13 (optional)
• Configuring an MSDP Mesh Group, page 46-15 (optional)
• Shutting Down an MSDP Peer, page 46-15 (optional)
• Including a Bordering PIM Dense-Mode Region in MSDP, page 46-16 (optional)
• Configuring an Originating Address other than the RP Address, page 46-17 (optional)
Router C
SA 10.1.1.1
SA
SA
Router A Switch B
86515
ISP A PIM domain Customer PIM domain
Beginning in privileged EXEC mode, follow these steps to specify a default MSDP peer. This procedure
is required.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip msdp default-peer ip-address | name Define a default peer from which to accept all MSDP SA messages.
[prefix-list list]
• For ip-address | name, enter the IP address or Domain Name
System (DNS) server name of the MSDP default peer.
• (Optional) For prefix-list list, enter the list name that specifies the
peer to be the default peer only for the listed prefixes. You can have
multiple active default peers when you have a prefix list associated
with each.
When you enter multiple ip msdp default-peer commands with the
prefix-list keyword, you use all the default peers at the same time
for different RP prefixes. This syntax is typically used in a service
provider cloud that connects stub site clouds.
When you enter multiple ip msdp default-peer commands without
the prefix-list keyword, a single active peer accepts all SA
messages. If that peer fails, the next configured default peer accepts
all SA messages. This syntax is typically used at a stub site.
Command Purpose
Step 3 ip prefix-list name [description string] | (Optional) Create a prefix list using the name specified in Step 2.
seq number {permit | deny} network
• (Optional) For description string, enter a description of up to 80
length
characters to describe this prefix list.
• For seq number, enter the sequence number of the entry. The range
is 1 to 4294967294.
• The deny keyword denies access to matching conditions.
• The permit keyword permits access to matching conditions.
• For network length, specify the network number and length (in bits)
of the network mask that is permitted or denied.
Step 4 ip msdp description {peer-name | (Optional) Configure a description for the specified peer to make it
peer-address} text easier to identify in a configuration or in show command output.
By default, no description is associated with an MSDP peer.
Step 5 end Return to privileged EXEC mode.
Step 6 show running-config Verify your entries.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove the default peer, use the no ip msdp default-peer ip-address | name global configuration
command.
This example shows a partial configuration of Router A and Router C in Figure 46-2. Each of these ISPs
have more than one customer (like the customer in Figure 46-2) who use default peering (no BGP or
MBGP). In that case, they might have similar configurations. That is, they accept SAs only from a default
peer if the SA is permitted by the corresponding prefix list.
Router A
Router(config)# ip msdp default-peer 10.1.1.1
Router(config)# ip msdp default-peer 10.1.1.1 prefix-list site-a
Router(config)# ip prefix-list site-b permit 10.0.0.0/8
Router C
Router(config)# ip msdp default-peer 10.1.1.1 prefix-list site-a
Router(config)# ip prefix-list site-b permit 10.0.0.0/8
Beginning in privileged EXEC mode, follow these steps to enable the caching of source/group pairs. This
procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip msdp cache-sa-state [list Enable the caching of source/group pairs (create an SA state). Those
access-list-number] pairs that pass the access list are cached.
For list access-list-number, the range is 100 to 199.
Step 3 access-list access-list-number {deny | Create an IP extended access list, repeating the command as many times
permit} protocol source source-wildcard as necessary.
destination destination-wildcard
• For access-list-number, the range is 100 to 199. Enter the same
number created in Step 2.
• The deny keyword denies access if the conditions are matched. The
permit keyword permits access if the conditions are matched.
• For protocol, enter ip as the protocol name.
• For source, enter the number of the network or host from which the
packet is being sent.
• For source-wildcard, enter the wildcard bits in dotted decimal
notation to be applied to the source. Place ones in the bit positions
that you want to ignore.
• For destination, enter the number of the network or host to which
the packet is being sent.
• For destination-wildcard, enter the wildcard bits in dotted decimal
notation to be applied to the destination. Place ones in the bit
positions that you want to ignore.
Recall that the access list is always terminated by an implicit deny
statement for everything.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
Note An alternative to this command is the ip msdp sa-request global configuration command, which causes
the switch to send an SA request message to the MSDP peer when a new member for a group becomes
active. For more information, see the next section.
To return to the default setting (no SA state is created), use the no ip msdp cache-sa-state global
configuration command.
This example shows how to enable the cache state for all sources in 171.69.0.0/16 sending to
groups 224.2.0.0/16:
Switch(config)# ip msdp cache-sa-state 100
Switch(config)# access-list 100 permit ip 171.69.0.0 0.0.255.255 224.2.0.0 0.0.255.255
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip msdp sa-request {ip-address | name} Configure the switch to send SA request messages to the specified
MSDP peer.
For ip-address | name, enter the IP address or name of the MSDP peer
from which the local switch requests SA messages when a new member
for a group becomes active.
Repeat the command for each MSDP peer that you want to supply with
SA messages.
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default setting, use the no ip msdp sa-request {ip-address | name} global configuration
command.
This example shows how to configure the switch to send SA request messages to the MSDP peer
at 171.69.1.1:
Switch(config)# ip msdp sa-request 171.69.1.1
Redistributing Sources
SA messages originate on RPs to which sources have registered. By default, any source that registers
with an RP is advertised. The A flag is set in the RP when a source is registered, which means the source
is advertised in an SA unless it is filtered.
Beginning in privileged EXEC mode, follow these steps to further restrict which registered sources are
advertised. This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip msdp redistribute [list Configure which (S,G) entries from the multicast routing table are
access-list-name] [asn advertised in SA messages.
aspath-access-list-number] [route-map By default, only sources within the local domain are advertised.
map]
• (Optional) For list access-list-name, enter the name or number of an
IP standard or extended access list. The range is 1 to 99 for standard
access lists and 100 to 199 for extended lists. The access list
controls which local sources are advertised and to which groups
they send.
• (Optional) For asn aspath-access-list-number, enter the IP standard
or extended access list number in the range 1 to 199. This access list
number must also be configured in the ip as-path access-list
command.
• (Optional) For route-map map, enter the IP standard or extended
access list number in the range 1 to 199. This access list number
must also be configured in the ip as-path access-list command.
The switch advertises (S,G) pairs according to the access list or
autonomous system path access list.
Command Purpose
Step 3 access-list access-list-number {deny | Create an IP standard access list, repeating the command as many times
permit} source [source-wildcard] as necessary.
or or
access-list access-list-number {deny | Create an IP extended access list, repeating the command as many times
permit} protocol source source-wildcard as necessary.
destination destination-wildcard
• For access-list-number, the range is 1 to 99 for standard access lists
and 100 to 199 for extended lists. Enter the same number created in
Step 2.
• The deny keyword denies access if the conditions are matched. The
permit keyword permits access if the conditions are matched.
• For protocol, enter ip as the protocol name.
• For source, enter the number of the network or host from which the
packet is being sent.
• For source-wildcard, enter the wildcard bits in dotted decimal
notation to be applied to the source. Place ones in the bit positions
that you want to ignore.
• For destination, enter the number of the network or host to which
the packet is being sent.
• For destination-wildcard, enter the wildcard bits in dotted decimal
notation to be applied to the destination. Place ones in the bit
positions that you want to ignore.
Recall that the access list is always terminated by an implicit deny
statement for everything.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove the filter, use the no ip msdp redistribute global configuration command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip msdp filter-sa-request ip-address | Filter all SA request messages from the specified MSDP peer.
name or
or Filter SA request messages from the specified MSDP peer for groups
ip msdp filter-sa-request {ip-address | that pass the standard access list. The access list describes a multicast
name} list access-list-number group address. The range for the access-list-number is 1 to 99.
Step 3 access-list access-list-number {deny | Create an IP standard access list, repeating the command as many times
permit} source [source-wildcard] as necessary.
• For access-list-number, the range is 1 to 99.
• The deny keyword denies access if the conditions are matched. The
permit keyword permits access if the conditions are matched.
• For source, enter the number of the network or host from which the
packet is being sent.
• (Optional) For source-wildcard, enter the wildcard bits in dotted
decimal notation to be applied to the source. Place ones in the bit
positions that you want to ignore.
Recall that the access list is always terminated by an implicit deny
statement for everything.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default setting, use the no ip msdp filter-sa-request {ip-address | name} global
configuration command.
This example shows how to configure the switch to filter SA request messages from the MSDP peer
at 171.69.2.2. SA request messages from sources on network 192.4.22.0 pass access list 1 and are
accepted; all others are ignored.
Switch(config)# ip msdp filter sa-request 171.69.2.2 list 1
Switch(config)# access-list 1 permit 192.4.22.0 0.0.0.255
Using a Filter
By creating a filter, you can perform one of these actions:
• Filter all source/group pairs
• Specify an IP extended access list to pass only certain source/group pairs
• Filter based on match criteria in a route map
Beginning in privileged EXEC mode, follow these steps to apply a filter. This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip msdp sa-filter out ip-address | name Filter all SA messages to the specified MSDP peer.
or or
ip msdp sa-filter out {ip-address | name} To the specified peer, pass only those SA messages that pass the IP
list access-list-number extended access list. The range for the extended access-list-number
is 100 to 199.
If both the list and the route-map keywords are used, all conditions
must be true to pass any (S,G) pair in outgoing SA messages.
or
or
To the specified MSDP peer, pass only those SA messages that meet the
ip msdp sa-filter out {ip-address | name} match criteria in the route map map-tag.
route-map map-tag
If all match criteria are true, a permit from the route map passes routes
through the filter. A deny filters routes.
Step 3 access-list access-list-number {deny | (Optional) Create an IP extended access list, repeating the command as
permit} protocol source source-wildcard many times as necessary.
destination destination-wildcard
• For access-list-number, enter the number specified in Step 2.
• The deny keyword denies access if the conditions are matched. The
permit keyword permits access if the conditions are matched.
• For protocol, enter ip as the protocol name.
• For source, enter the number of the network or host from which the
packet is being sent.
• For source-wildcard, enter the wildcard bits in dotted decimal
notation to be applied to the source. Place ones in the bit positions
that you want to ignore.
• For destination, enter the number of the network or host to which
the packet is being sent.
• For destination-wildcard, enter the wildcard bits in dotted decimal
notation to be applied to the destination. Place ones in the bit
positions that you want to ignore.
Recall that the access list is always terminated by an implicit deny
statement for everything.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove the filter, use the no ip msdp sa-filter out {ip-address | name} [list access-list-number]
[route-map map-tag] global configuration command.
This example shows how to allow only (S,G) pairs that pass access list 100 to be forwarded in an SA
message to the peer named switch.cisco.com:
Switch(config)# ip msdp peer switch.cisco.com connect-source gigabitethernet1/0/1
Switch(config)# ip msdp sa-filter out switch.cisco.com list 100
Switch(config)# access-list 100 permit ip 171.69.0.0 0.0.255.255 224.20 0 0.0.255.255
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip msdp ttl-threshold {ip-address | name} Limit which multicast data is encapsulated in the first SA message to
ttl the specified MSDP peer.
• For ip-address | name, enter the IP address or name of the MSDP
peer to which the TTL limitation applies.
• For ttl, enter the TTL value. The default is 0, which means all
multicast data packets are forwarded to the peer until the TTL is
exhausted. The range is 0 to 255.
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default setting, use the no ip msdp ttl-threshold {ip-address | name} global
configuration command.
Beginning in privileged EXEC mode, follow these steps to apply a filter. This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip msdp sa-filter in ip-address | name Filter all SA messages from the specified MSDP peer.
or or
ip msdp sa-filter in {ip-address | name} From the specified peer, pass only those SA messages that pass the IP
list access-list-number extended access list. The range for the extended access-list-number
is 100 to 199.
If both the list and the route-map keywords are used, all conditions
must be true to pass any (S,G) pair in incoming SA messages.
or or
ip msdp sa-filter in {ip-address | name} From the specified MSDP peer, pass only those SA messages that meet
route-map map-tag the match criteria in the route map map-tag.
If all match criteria are true, a permit from the route map passes routes
through the filter. A deny will filter routes.
Step 3 access-list access-list-number {deny | (Optional) Create an IP extended access list, repeating the command as
permit} protocol source source-wildcard many times as necessary.
destination destination-wildcard
• For access-list-number, enter the number specified in Step 2.
• The deny keyword denies access if the conditions are matched. The
permit keyword permits access if the conditions are matched.
• For protocol, enter ip as the protocol name.
• For source, enter the number of the network or host from which the
packet is being sent.
• For source-wildcard, enter the wildcard bits in dotted decimal
notation to be applied to the source. Place ones in the bit positions
that you want to ignore.
• For destination, enter the number of the network or host to which
the packet is being sent.
• For destination-wildcard, enter the wildcard bits in dotted decimal
notation to be applied to the destination. Place ones in the bit
positions that you want to ignore.
Recall that the access list is always terminated by an implicit deny
statement for everything.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove the filter, use the no ip msdp sa-filter in {ip-address | name} [list access-list-number]
[route-map map-tag] global configuration command.
This example shows how to filter all SA messages from the peer named switch.cisco.com:
Switch(config)# ip msdp peer switch.cisco.com connect-source gigabitethernet1/0/1
Switch(config)# ip msdp sa-filter in switch.cisco.com
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip msdp mesh-group name {ip-address | Configure an MSDP mesh group, and specify the MSDP peer belonging
name} to that mesh group.
By default, the MSDP peers do not belong to a mesh group.
• For name, enter the name of the mesh group.
• For ip-address | name, enter the IP address or name of the MSDP
peer to be a member of the mesh group.
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
Step 6 Repeat this procedure on each MSDP peer in the group.
To remove an MSDP peer from a mesh group, use the no ip msdp mesh-group name
{ip-address | name} global configuration command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip msdp shutdown {peer-name | peer Administratively shut down the specified MSDP peer without losing
address} configuration information.
For peer-name | peer address, enter the IP address or name of the MSDP
peer to shut down.
Step 3 end Return to privileged EXEC mode.
Command Purpose
Step 4 show running-config Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To bring the peer back up, use the no ip msdp shutdown {peer-name | peer address} global
configuration command. The TCP connection is reestablished
Note We do not recommend using the ip msdp border sa-address global configuration command. It is better
to configure the border router in the sparse-mode domain to proxy-register sources in the dense-mode
domain to the RP of the sparse-mode domain and have the sparse-mode domain use standard MSDP
procedures to advertise these sources.
Beginning in privileged EXEC mode, follow these steps to configure the border router to send SA
messages for sources active in the dense-mode region to the MSDP peers. This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip msdp border sa-address interface-id Configure the switch on the border between a dense-mode and
sparse-mode region to send SA messages about active sources in the
dense-mode region.
For interface-id, specify the interface from which the IP address is
derived and used as the RP address in SA messages.
The IP address of the interface is used as the Originator-ID, which is the
RP field in the SA message.
Step 3 ip msdp redistribute [list Configure which (S,G) entries from the multicast routing table are
access-list-name] [asn advertised in SA messages.
aspath-access-list-number] [route-map For more information, see the “Redistributing Sources” section on
map]
page 46-9.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entries.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
Note that the ip msdp originator-id global configuration command also identifies an interface to be
used as the RP address. If you configure both the ip msdp border sa-address and the ip msdp
originator-id global configuration commands, the address derived from the ip msdp originator-id
command determines the RP address.
To return to the default setting (active sources in the dense-mode region do not participate in MSDP),
use the no ip msdp border sa-address interface-id global configuration command.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip msdp originator-id interface-id Configures the RP address in SA messages to be the address of the
originating device interface.
For interface-id, specify the interface on the local switch.
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
If you configure both the ip msdp border sa-address and the ip msdp originator-id global
configuration commands, the address derived from the ip msdp originator-id command determines the
address of the RP.
To prevent the RP address from being derived in this way, use the no ip msdp originator-id interface-id
global configuration command.
Command Purpose
debug ip msdp [peer-address | name] [detail] [routes] Debugs an MSDP activity.
debug ip msdp resets Debugs MSDP peer reset reasons.
show ip msdp count [autonomous-system-number] Displays the number of sources and groups originated in SA
messages from each autonomous system. The ip msdp
cache-sa-state command must be configured for this command to
produce any output.
Command Purpose
show ip msdp peer [peer-address | name] Displays detailed information about an MSDP peer.
show ip msdp sa-cache [group-address | source-address | Displays (S,G) state learned from MSDP peers.
group-name | source-name] [autonomous-system-number]
show ip msdp summary Displays MSDP peer status and SA message counts.
To clear MSDP connections, statistics, or SA cache entries, use the privileged EXEC commands in
Table 46-2:
Table 46-2 Commands for Clearing MSDP Connections, Statistics, or SA Cache Entries
Command Purpose
clear ip msdp peer peer-address | name Clears the TCP connection to the specified MSDP peer, resetting all
MSDP message counters.
clear ip msdp statistics [peer-address | name] Clears statistics counters for one or all the MSDP peers without resetting
the sessions.
clear ip msdp sa-cache [group-address | name] Clears the SA cache entries for all entries, all sources for a specific group,
or all entries for a specific source/group pair.
This chapter describes how to configure fallback bridging (VLAN bridging) on the Catalyst 3750 Metro
switch. With fallback bridging, you can forward non-IP packets that the switch does not route between
VLAN bridge domains and routed ports.
Note For complete syntax and usage information for the commands used in this chapter, see the Cisco IOS
Bridging and IBM Networking Command Reference, Volume 1 of 2, Release 12.2.
The switch creates a VLAN-bridge spanning-tree instance when a bridge group is created. The switch
runs the bridge group and treats the SVIs and routed ports in the bridge group as its spanning-tree ports.
These are the reasons for placing network interfaces into a bridge group:
• To bridge all nonrouted traffic among the network interfaces making up the bridge group. If the
packet destination address is in the bridge table, the packet is forwarded on a single interface in the
bridge group. If the packet destination address is not in the bridge table, the packet is flooded on all
forwarding interfaces in the bridge group. A source MAC address is learned on a bridge group only
when the address is learned on a VLAN (the reverse is not true).
• To participate in the spanning-tree algorithm by receiving, and in some cases sending, BPDUs on
the LANs to which they are attached. A separate spanning-tree process runs for each configured
bridge group. Each bridge group participates in a separate spanning-tree instance. A bridge group
establishes a spanning-tree instance based on the BPDUs it receives on only its member ports. If the
bridge STP BPDU is received on a port whose VLAN does not belong to a bridge group, the BPDU
is flooded on all the forwarding ports of the VLAN.
Figure 47-1 shows a fallback bridging network example. The switch has two ports configured as SVIs
with different assigned IP addresses and attached to two different VLANs. Another port is configured as
a routed port with its own IP address. If all three of these ports are assigned to the same bridge group,
non-IP protocol frames can be forwarded among the end stations connected to the switch even though
they are on different networks and in different VLANs. IP addresses do not need to be assigned to routed
ports or SVIs for fallback bridging to work.
Routed port
Layer 3 switch
172.20.130.1
Host C
Host A Host B
101240
VLAN 20 VLAN 30
Note The protected port feature is not compatible with fallback bridging. When fallback bridging is enabled,
it is possible for packets to be forwarded from one protected port on a switch to another protected port
on the same switch if the ports are in different VLANs.
Beginning in privileged EXEC mode, follow these steps to create a bridge group and to assign an
interface to it. This procedure is required.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 bridge bridge-group protocol Assign a bridge group number, and specify the VLAN-bridge
vlan-bridge spanning-tree protocol to run in the bridge group. The ibm and dec
keywords are not supported.
For bridge-group, specify the bridge group number. The range is 1
to 255. You can create up to 32 bridge groups.
Frames are bridged only among interfaces in the same group.
Step 3 interface interface-id Specify the interface on which you want to assign the bridge group, and
enter interface configuration mode.
The specified interface must be one of these:
• A routed port: a physical port that you have configured as a Layer 3
port by entering the no switchport interface configuration
command.
• An SVI: a VLAN interface that you created by using the interface
vlan vlan-id global configuration command.
Note You can assign an IP address to the routed port or to the SVI,
but it is not required.
Step 4 bridge-group bridge-group Assign the interface to the bridge group created in Step 2.
By default, the interface is not assigned to any bridge group. An
interface can be assigned to only one bridge group.
Step 5 end Return to privileged EXEC mode.
Step 6 show running-config Verify your entries.
Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove a bridge group, use the no bridge bridge-group global configuration command. The no
bridge bridge-group command automatically removes all SVIs and routed ports from that bridge group.
To remove an interface from a bridge group and to remove the bridge group, use the no bridge-group
bridge-group interface configuration command.
This example shows how to create bridge group 10, to specify that the VLAN-bridge STP runs in the
bridge group, to define a port as a routed port, and to assign the port to the bridge group:
Switch(config)# bridge 10 protocol vlan-bridge
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# no switchport
Switch(config-if)# no shutdown
Switch(config-if)# bridge-group 10
This example shows how to create bridge group 10 and to specify that the VLAN-bridge STP runs in the
bridge group. It defines a port as an SVI and assigns this port to VLAN 2 and to the bridge group:
Switch(config)# bridge 10 protocol vlan-bridge
Switch(config)# vlan 2
Switch(config-vlan)# exit
Switch(config)# interface vlan 2
Switch(config-if)# bridge-group 10
Switch(config-if)# no shutdown
Switch(config-if)# exit
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# switchport mode access
Switch(config-if)# switchport access vlan 2
Switch(config-if)# no shutdown
Note Only network administrators with a good understanding of how switches and STP function should make
adjustments to spanning-tree parameters. Poorly planned adjustments can have a negative impact on
performance. A good source on switching is the IEEE 802.1D specification. For more information, see
the “References and Recommended Reading” appendix in the Cisco IOS Configuration Fundamentals
Command Reference.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 bridge bridge-group priority number Change the VLAN-bridge spanning-tree priority of the switch.
• For bridge-group, specify the bridge group number. The range is 1
to 255.
• For number, enter a number from 0 to 65535. The default is 32768.
The lower the number, the more likely the switch will be chosen as
the root.
Step 3 end Return to privileged EXEC mode.
Command Purpose
Step 4 show running-config Verify your entry.
Step 5 copy running-config startup-config (Optional) Save your entry in the configuration file.
To return to the default setting, use the no bridge bridge-group priority global configuration command.
To change the priority on a port, use the bridge-group priority interface configuration command
(described in the next section).
This example shows how to set the switch priority to 100 for bridge group 10:
Switch(config)# bridge 10 priority 100
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the port to set the priority, and enter interface configuration
mode.
Step 3 bridge-group bridge-group priority Change the priority of a port.
number
• For bridge-group, specify the bridge group number. The range is 1
to 255.
• For number, enter a number from 0 to 255 in increments of 4. The
lower the number, the more likely that the port on the switch will
be chosen as the root. The default is 128.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entry.
Step 6 copy running-config startup-config (Optional) Save your entry in the configuration file.
To return to the default setting, use the no bridge-group bridge-group priority interface configuration
command.
This example shows how to change the priority to 20 on a port in bridge group 10:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# bridge-group 10 priority 20
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the port to set the path cost, and enter interface configuration
mode.
Step 3 bridge-group bridge-group path-cost Assign the path cost of a port.
cost
• For bridge-group, specify the bridge group number. The range is 1
to 255.
• For cost, enter a number from 0 to 65535. The higher the value, the
higher the cost.
– For 10 Mbps, the default path cost is 100.
– For 100 Mbps, the default path cost is 19.
– For 1000 Mbps, the default path cost is 4.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entry.
Step 6 copy running-config startup-config (Optional) Save your entry in the configuration file.
To return to the default path cost, use the no bridge-group bridge-group path-cost interface
configuration command.
This example shows how to change the path cost to 20 on a port in bridge group 10:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# bridge-group 10 path-cost 20
Note Each switch in a spanning tree adopts the interval between hello BPDUs, the forward delay interval, and
the maximum idle interval parameters of the root switch, regardless of what its individual configuration
might be.
Beginning in privileged EXEC mode, follow these step to adjust the interval between hello BPDUs. This
procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 bridge bridge-group hello-time seconds Specify the interval between hello BPDUs.
• For bridge-group, specify the bridge group number. The range is 1
to 255.
• For seconds, enter a number from 1 to 10. The default is 2.
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify your entry.
Step 5 copy running-config startup-config (Optional) Save your entry in the configuration file.
To return to the default setting, use the no bridge bridge-group hello-time global configuration
command.
This example shows how to change the hello interval to 5 seconds in bridge group 10:
Switch(config)# bridge 10 hello-time 5
The forward-delay interval is the amount of time spent listening for topology change information after
a port has been activated for switching and before forwarding actually begins.
Beginning in privileged EXEC mode, follow these steps to change the forward-delay interval. This
procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 bridge bridge-group forward-time Specify the forward-delay interval.
seconds
• For bridge-group, specify the bridge group number. The range is 1
to 255.
• For seconds, enter a number from 4 to 200. The default is 20.
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify your entry.
Step 5 copy running-config startup-config (Optional) Save your entry in the configuration file.
To return to the default setting, use the no bridge bridge-group forward-time global configuration
command.
This example shows how to change the forward-delay interval to 10 seconds in bridge group 10:
Switch(config)# bridge 10 forward-time 10
If a switch does not receive BPDUs from the root switch within a specified interval, it recomputes the
spanning-tree topology.
Beginning in privileged EXEC mode, follow these steps to change the maximum-idle interval (maximum
aging time). This procedure is optional.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 bridge bridge-group max-age seconds Specify the interval that the switch waits to hear BPDUs from the root
switch.
• For bridge-group, specify the bridge group number. The range is 1
to 255.
• For seconds, enter a number from 6 to 200. The default is 30.
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify your entry.
Step 5 copy running-config startup-config (Optional) Save your entry in the configuration file.
To return to the default setting, use the no bridge bridge-group max-age global configuration command.
This example shows how to change the maximum-idle interval to 30 seconds in bridge group 10:
Switch(config)# bridge 10 max-age 30
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Specify the port, and enter interface configuration mode.
Step 3 bridge-group bridge-group Disable spanning tree on the port.
spanning-disabled
For bridge-group, specify the bridge group number. The range is 1
to 255.
Step 4 end Return to privileged EXEC mode.
Step 5 show running-config Verify your entry.
Step 6 copy running-config startup-config (Optional) Save your entry in the configuration file.
To re-enable spanning tree on the port, use the no bridge-group bridge-group spanning-disabled
interface configuration command.
This example shows how to disable spanning tree on a port in bridge group 10:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# bridge group 10 spanning-disabled
Command Purpose
clear bridge bridge-group Removes any learned entries from the forwarding
database.
show bridge [bridge-group] group Displays details about the bridge group.
show bridge [bridge-group] [interface-id | Displays MAC addresses learned in the bridge group.
mac-address | verbose]
For information about the fields in these displays, see the Cisco IOS Bridging and IBM Networking
Command Reference, Volume 1 of 2, Release 12.2
This chapter describes how to identify and resolve software problems related to the Cisco IOS software
on the Catalyst 3750 Metro switch.
Additional troubleshooting information is provided in the hardware installation guide.
Note For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release and the Cisco IOS Command Summary, Release 12.2.
Note Recovery procedures require that you have physical access to the switch.
Step 1 From your PC, download the software image tar file (image_filename.tar) from Cisco.com.
The Cisco IOS image is stored as a bin file in a directory in the tar file. For information about locating
the software image files on Cisco.com, see the release notes.
Step 2 Extract the bin file from the tar file.
• If you are using Windows, use a zip program that is capable of reading a tar file. Use the zip program
to navigate to and extract the bin file.
• If you are using UNIX, follow these steps:
1. Display the contents of the tar file by using the tar -tvf <image_filename.tar> UNIX command.
2. Locate the bin file name in the display and extract it by using the tar -xvf <image_filename.tar>
<image_filename.bin> UNIX command.
switch% tar -xvf image_filename.tar image_filename.bin
3. Verify that the bin file was extracted by using the ls -l <image_filename.bin> UNIX command.
The bin file name (image_filename.bin) should appear in the output.
switch% ls -l image_filename.bin
Step 3 Connect your PC with terminal-emulation software supporting the XMODEM Protocol to the switch
console port.
Step 4 Set the line speed on the emulation software to 9600 baud.
Step 5 Unplug the switch power cord.
Step 6 Press the Mode button, and at the same time, reconnect the power cord to the switch.
You can release the Mode button a second or two after the LED above port 1 goes off. Several lines of
information about the software appear along with instructions:
The system has been interrupted prior to initializing the flash file system. The following
commands will initialize the flash file system, and finish loading the operating system
software#
flash_init
load_helper
boot
Step 8 If you had set the console port speed to anything other than 9600, it has been reset to that particular
speed. Change the emulation software line speed to match that of the switch console port.
Step 11 After the XMODEM request appears, use the appropriate command on the terminal-emulation software
to start the transfer and to copy the software image into Flash memory.
Step 12 Boot the newly-downloaded Cisco IOS image.
switch:boot flash:image_filename.bin
Step 13 Use the archive download-sw privileged EXEC command to download the software image to the
switch.
Step 14 Use the reload privileged EXEC command to restart the switch and to verify that the new software image
is operating properly.
Step 15 Delete the flash:image_filename.bin file from the switch.
Note On these switches, a system administrator can disable some of the functionality of this feature by
allowing an end user to reset a password only by agreeing to return to the default configuration. If you
are an end user trying to reset a password when password recovery has been disabled, a status message
shows this during the recovery process.
This section describes how to recover a forgotten or lost switch password. It provides two solutions:
• Procedure with Password Recovery Enabled, page 48-4
• Procedure with Password Recovery Disabled, page 48-5
You enable or disable password recovery by using the service password-recovery global configuration
command.
Follow the steps in this procedure if you have forgotten or lost the switch password.
Step 1 Connect a terminal or PC with terminal-emulation software to the switch console port.
Step 2 Set the line speed on the emulation software to 9600 baud.
Step 3 Power off the switch.
Step 4 Press the Mode button, and at the same time, reconnect the power cord to the switch.
You can release the Mode button a second or two after the LED above port 1 turns off. Several lines of
information about the software appear with instructions, informing you if the password recovery
procedure has been disabled or not.
• If you see a message that begins with this:
The system has been interrupted prior to initializing the flash file system. The
following commands will initialize the flash file system
proceed to the “Procedure with Password Recovery Enabled” section on page 48-4, and follow the
steps.
• If you see a message that begins with this:
The password-recovery mechanism has been triggered, but is currently disabled.
proceed to the “Procedure with Password Recovery Disabled” section on page 48-5, and follow the
steps.
Step 5 After recovering the password, reload the switch:
Switch> reload
Proceed with reload? [confirm] y
flash_init
load_helper
boot
Step 2 If you had set the console port speed to anything other than 9600, it has been reset to that particular
speed. Change the emulation software line speed to match that of the switch console port.
Step 3 Load any helper files:
switch: load_helper
You are prompted to start the setup program. Enter N at the prompt:
Continue with the configuration dialog? [yes/no]: N
Switch> enable
The secret password can be from 1 to 25 alphanumeric characters, can start with a number, is case
sensitive, and allows spaces but ignores leading spaces.
Step 12 Return to privileged EXEC mode:
Switch (config)# exit
Switch#
Note This procedure is likely to leave your switch virtual interface in a shutdown state. You can see
which interface is in this state by entering the show running-config privileged EXEC command.
To re-enable the interface, enter the interface vlan vlan-id global configuration command, and
specify the VLAN ID of the shutdown interface. With the switch in interface configuration
mode, enter the no shutdown command.
Would you like to reset the system back to the default configuration (y/n)?
Caution Returning the switch to the default configuration results in the loss of all existing configurations. We
recommend that you contact your system administrator to verify if there are backup switch and VLAN
configuration files.
• If you enter n (no), the normal boot process continues as if the Mode button had not been pressed;
you cannot access the boot loader prompt, and you cannot enter a new password. You see the
message:
Press Enter to continue........
• If you enter y (yes), the configuration file in Flash memory and the VLAN database file are deleted.
When the default configuration loads, you can reset the password.
Step 1 Elect to continue with password recovery and lose the existing configuration:
Would you like to reset the system back to the default configuration (y/n)? Y
You are prompted to start the setup program. To continue with password recovery, enter N at the prompt:
Continue with the configuration dialog? [yes/no]: N
The secret password can be from 1 to 25 alphanumeric characters, can start with a number, is case
sensitive, and allows spaces but ignores leading spaces.
Step 8 Return to privileged EXEC mode:
Switch (config)# exit
Switch#
Note This procedure is likely to leave your switch virtual interface in a shutdown state. You can see
which interface is in this state by entering the show running-config privileged EXEC command.
To re-enable the interface, enter the interface vlan vlan-id global configuration command, and
specify the VLAN ID of the shutdown interface. With the switch in interface configuration
mode, enter the no shutdown command.
Step 10 You must now reconfigure the switch. If the system administrator has the backup switch and VLAN
configuration files available, you should use those.
Note If a remote device does not autonegotiate, configure the duplex settings on the two ports to match. The
speed parameter can adjust itself even if the connected port does not autonegotiate.
Note The security error message references the GBIC_SECURITY facility. The switch supports SFP modules
and does not support GBIC modules. Although the error message text refers to GBIC interfaces and
modules, the security messages actually refer to the SFP modules and module interfaces. For more
information about error messages, see the system message guide for this release.
If you are using a non-Cisco SFP module, remove the SFP module from the switch, and replace it with
a Cisco module. After inserting a Cisco SFP module, use the errdisable recovery cause gbic-invalid
global configuration command to verify the port status, and enter a time interval for recovering from the
error-disabled state. After the elapsed interval, the switch brings the interface out of the error-disabled
state and retries the operation. For more information about the errdisable recovery command, see the
command reference for this release.
If the module is identified as a Cisco SFP module, but the system is unable to read vendor-data
information to verify its accuracy, an SFP module error message is generated. In this case, you should
remove and re-insert the SFP module. If it continues to fail, the SFP module might be defective.
Using Ping
This section consists of this information:
• Understanding Ping, page 48-8
• Executing Ping, page 48-8
Understanding Ping
The switch supports IP ping, which you can use to test connectivity to remote hosts. Ping sends an echo
request packet to an address and waits for a reply. Ping returns one of these responses:
• Normal response—The normal response (hostname is alive) occurs in 1 to 10 seconds, depending
on network traffic.
• Destination does not respond—If the host does not respond, a no-answer message is returned.
• Unknown host—If the host does not exist, an unknown host message is returned.
• Destination unreachable—If the default gateway cannot reach the specified network, a
destination-unreachable message is returned.
• Network or host unreachable—If there is no entry in the route table for the host or network, a
network or host unreachable message is returned.
Executing Ping
If you attempt to ping a host in a different IP subnetwork, you must define a static route to the network
or have IP routing configured to route between those subnets. For more information, see Chapter 36,
“Configuring IP Unicast Routing.”
IP routing is disabled by default on all switches. If you need to enable or configure IP routing, see
Chapter 36, “Configuring IP Unicast Routing.”
Beginning in privileged EXEC mode, use this command to ping another device on the network from the
switch:
Command Purpose
ping ip host | address Ping a remote host through IP or by supplying the hostname or
network address.
Note Though other protocol keywords are available with the ping command, they are not supported in this
release.
Character Description
! Each exclamation point means receipt of a reply.
. Each period means the network server timed out while waiting for a reply.
U A destination unreachable error PDU was received.
C A congestion experienced packet was received.
I User interrupted test.
? Unknown packet type.
& Packet lifetime exceeded.
To terminate a ping session, enter the escape sequence (Ctrl-^ X by default). You enter the default by
simultaneously pressing and releasing the Ctrl, Shift, and 6 keys, and then pressing the X key.
Usage Guidelines
These are the Layer 2 traceroute usage guidelines:
• Cisco Discovery Protocol (CDP) must be enabled on all the devices in the network. For Layer 2
traceroute to function properly, do not disable CDP. If any devices in the physical path are
transparent to CDP, the switch cannot identify the path through these devices.
Note For more information about enabling CDP, see Chapter 25, “Configuring CDP.”
• A switch is reachable from another switch when you can test connectivity by using the ping
privileged EXEC command. All switches in the physical path must be reachable from each other.
• 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 physical path from the source device to the destination device. All switches 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 switch
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 switch uses the associated MAC address
and identifies the physical path.
– If an ARP entry does not exist, the switch 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 feature is not supported. When more than one CDP
neighbor is detected on a port, the Layer 2 path is not identified, and an error message appears.
• This feature is not supported in Token Ring VLANs.
Using IP Traceroute
This section consists of this information:
• Understanding IP Traceroute, page 48-11
• Executing IP Traceroute, page 48-12
Understanding IP Traceroute
You can use IP traceroute to identify the path that packets take through the network on a hop-by-hop
basis. The command output displays all network layer (Layer 3) devices, such as routers, that the traffic
passes through on the way to the destination.
Your switches can participate as the source or destination of the traceroute privileged EXEC command
and might or might not appear as a hop in the traceroute command output. If the switch is the destination
of the traceroute, it is displayed as the final destination in the traceroute output. Intermediate switches
do not show up in the traceroute output if they are only bridging the packet from one port to another
within the same VLAN. However, if the intermediate switch is a multilayer switch that is routing a
particular packet, this switch shows up as a hop in the traceroute output.
The traceroute privileged EXEC command uses the Time To Live (TTL) field in the IP header to cause
routers and servers to generate specific return messages. Traceroute starts by sending a User Datagram
Protocol (UDP) datagram to the destination host with the TTL field set to 1. If a router finds a TTL value
of 1 or 0, it drops the datagram and sends back an Internet Control Message Protocol (ICMP)
time-to-live-exceeded message to the sender. Traceroute determines the address of the first hop by
examining the source address field of the ICMP time-to-live-exceeded message.
To identify the next hop, traceroute sends a UDP packet with a TTL value of 2. The first router
decrements the TTL field by 1 and sends the datagram to the next router. The second router sees a TTL
value of 1, discards the datagram, and returns the time-to-live-exceeded message to the source. This
process continues until the TTL is incremented to a value large enough for the datagram to reach the
destination host (or until the maximum TTL is reached).
To determine when a datagram reaches its destination, traceroute sets the UDP destination port number
in the datagram to a very large value that the destination host is unlikely to be using. When a host
receives a datagram destined to itself containing a destination port number that is unused locally, it sends
an ICMP port unreachable error to the source. Because all errors except port unreachable errors come
from intermediate hops, the receipt of a port unreachable error means this message was sent by the
destination.
Executing IP Traceroute
Beginning in privileged EXEC mode, follow this step to trace the path packets take through the network:
Command Purpose
traceroute ip host Trace the path packets take through the network by using IP.
Note Though other protocol keywords are available with the traceroute privileged EXEC command, they are
not supported in this release.
The display shows the hop count, IP address of the router, and the round-trip time in milliseconds for
each of the three probes that are sent.
Character Description
* The probe timed out.
? Unknown packet type.
A Administratively unreachable. Usually, this output means that an access list is
blocking traffic.
H Host unreachable.
N Network unreachable.
P Protocol unreachable.
Q Source quench.
U Port unreachable.
To terminate a trace in progress, enter the escape sequence (Ctrl-^ X by default). You enter the default
by simultaneously pressing and releasing the Ctrl, Shift, and 6 keys, and then pressing the X key.
Caution Because debugging output is assigned high priority in the CPU process, it can render the system
unusable. For this reason, use debug commands only to troubleshoot specific problems or during
troubleshooting sessions with Cisco technical support staff. It is best to use debug commands during
periods of lower network traffic and fewer users. Debugging during these periods decreases the
likelihood that increased debug command processing overhead will affect system use.
Note For complete syntax and usage information for specific debug commands, see the command reference
for this release.
The switch continues to generate output until you enter the no form of the command.
If you enable a debug command and no output appears, consider these possibilities:
• The switch might not be properly configured to generate the type of traffic you want to monitor. Use
the show running-config command to check its configuration.
• Even if the switch is properly configured, it might not generate the type of traffic you want to
monitor during the particular period that debugging is enabled. Depending on the feature you are
debugging, you can use commands such as the TCP/IP ping command to generate network traffic.
To disable debugging of SPAN, enter this command in privileged EXEC mode:
Switch# no debug span-session
Alternately, in privileged EXEC mode, you can enter the undebug form of the command:
Switch# undebug span-session
To display the state of each debugging option, enter this command in privileged EXEC mode:
Switch# show debugging
Caution Because debugging output takes priority over other network traffic, and because the debug all privileged
EXEC command generates more output than any other debug command, it can severely diminish switch
performance or even render it unusable. In virtually all cases, it is best to use more specific debug
commands.
The no debug all privileged EXEC command disables all diagnostic output. Using the no debug all
command is a convenient way to ensure that you have not accidentally left any debug commands
enabled.
Note Be aware that the debugging destination you use affects system overhead. Logging messages to the
console produces very high overhead, whereas logging messages to a virtual terminal produces less
overhead. Logging messages to a syslog server produces even less, and logging to an internal buffer
produces the least overhead of any method.
For more information about system message logging, see Chapter 30, “Configuring System Message
Logging.”
Note For more syntax and usage information for the show platform forward command, see the switch
command reference for this release.
Most of the information in the output from the command is useful mainly for technical support
personnel, who have access to detailed information about the switch application-specific integrated
circuits (ASICs). However, packet forwarding information can also be helpful in troubleshooting.
This is an example of the output from the show platform forward command on enhanced-services (ES)
port 1 in VLAN 5 when the packet entering that port is addressed to unknown MAC addresses. The
packet should be flooded to all other ports in VLAN 5.
Switch: show platform forward gigabitethernet1/1/1 vlan 10 1.1.1 2.2.2 ip 172.18.18.3
172.18.18.1 udp 10 20
Global Port Number:472, Asic Number:1
Src Real Vlan Id:10, Mapped Vlan Id:2
Ingress:
Lookup Key-Used Index-Hit A-Data
InptACL 40_AC121201_AC121203-00_40000014_000A0000 01FFA 03000000
L2Local 80_00020002_00020002-00_00000000_00000000 01850 0000003A
Station Descriptor:02D30000, DestIndex:02D5, RewriteIndex:F002
==========================================
Egress:Asic 0, switch 1
Output Packets:
------------------------------------------
Packet 1
Lookup Key-Used Index-Hit A-Data
OutptACL 50_AC121201_AC121203-00_40000014_000A0000 01FFE 03000000
------------------------------------------
Packet 2
Lookup Key-Used Index-Hit A-Data
OutptACL 50_AC121201_AC121203-00_40000014_000A0000 01FFE 03000000
------------------------------------------
Packet 3
Lookup Key-Used Index-Hit A-Data
OutptACL 50_AC121201_AC121203-00_40000014_000A0000 01FFE 03000000
==========================================
Egress:Asic 1, switch 1
Output Packets:
------------------------------------------
Packet 4
Lookup Key-Used Index-Hit A-Data
OutptACL 50_AC121201_AC121203-00_40000014_000A0000 01FFE 03000000
Packet dropped due to failed DEJA_VU Check on Gi1/1/1
This is an example of the output when the packet coming in on ES port 1 in VLAN 5 is sent to an address
already learned on the VLAN on another port. It should be forwarded from the port on which the address
was learned.
Switch# show platform forward gigabitethernet1/1/1 vlan 5 1.1.1 0009.43a8.0145 ip 13.1.1.1
13.2.2.2 udp 10 20
Global Port Number:472, Asic Number:1
Src Real Vlan Id:5, Mapped Vlan Id:5
Ingress:
==========================================
Egress:Asic 3, switch 1
Output Packets:
------------------------------------------
Packet 1
Lookup Key-Used Index-Hit A-Data
OutptACL 50_0D020202_0D010101-00_40000014_000A0000 01FFE 03000000
This is an example of the output when the packet coming in on ES port 1 in VLAN 5 has a destination
MAC address set to the router MAC address in VLAN 5 and the destination IP address unknown. Since
there is no default route set, the packet should be dropped.
Switch# show platform forward gigabitethernet1/1/1 vlan 5 1.1.1 03.e319.ee44 ip 13.1.1.1
13.2.2.2 udp 10 20
Global Port Number:472, Asic Number:1
Src Real Vlan Id:5, Mapped Vlan Id:5
Ingress:
Lookup Key-Used Index-Hit A-Data
InptACL 40_0D020202_0D010101-00_41000014_000A0000 01FFA 03000000
L3Local 00_00000000_00000000-90_00001400_0D020202 010F0 01880290
L3Scndr 12_0D020202_0D010101-00_40000014_000A0000 034E0 000C001D_00000000
Lookup Used:Secondary
Station Descriptor:02260000, DestIndex:0226, RewriteIndex:0000
This is an example of the output when the packet coming in on ES port 1 in VLAN 5 has a destination
MAC address set to the router MAC address in VLAN 5 and the destination IP address set to an IP
address that is in the IP routing table. It should be forwarded as specified in the routing table.
Switch# show platform forward gigabitethernet1/1/1 vlan 5 1.1.1 03.e319.ee44 ip 110.1.5.5
16.1.10.5
Global Port Number:472, Asic Number:1
Src Real Vlan Id:5, Mapped Vlan Id:5
Ingress:
Lookup Key-Used Index-Hit A-Data
InptACL 40_10010A05_0A010505-00_41000014_000A0000 01FFA 03000000
L3Local 00_00000000_00000000-90_00001400_10010A05 010F0 01880290
L3Scndr 12_10010A05_0A010505-00_40000014_000A0000 01D28 30090001_00000000
Lookup Used:Secondary
Station Descriptor:F0070007, DestIndex:F007, RewriteIndex:0007
==========================================
Egress:Asic 3, switch 1e
Output Packets:
------------------------------------------
Packet 1
Lookup Key-Used Index-Hit A-Data
OutptACL 50_10010A05_0A010505-00_40000014_000A0000 01FFE 03000000
Layer 3 switches:
• Dropped packets or increased latency for packets routed in software
• BGP or OSPF routing topology changes
• HSRP flapping
This example shows normal CPU utilization. The output shows that utilization for the last 5 seconds is
8%/0%, which has this meaning:
• The total CPU utilization is 8 percent, including both time running Cisco IOS processes and time
spent handling interrupts
• The time spent handling interrupts is zero percent.
\
Table 48-3 Troubleshooting CPU Utilization Problems
For complete information about CPU utilization and how to troubleshoot utilization problems, see the
Troubleshooting High CPU Utilization document on Cisco.com.
This appendix describes how to manipulate the Catalyst 3750 Metro switch flash file system, how to
copy configuration files, and how to archive (upload and download) software images to a switch.
Note For complete syntax and usage information for the commands used in this chapter, see the switch
command reference for this release and the Cisco IOS Configuration Fundamentals Command
Reference, Release 12.2.
Field Value
Size(b) Amount of memory in the file system in bytes.
Free(b) Amount of free memory in the file system in bytes.
Type Type of file system.
flash—The file system is for a flash memory device.
nvram—The file system is for a NVRAM device.
opaque—The file system is a locally generated pseudo file system (for example, the system) or a download
interface, such as brimux.
unknown—The file system is an unknown type.
Flags Permission for file system.
ro—read-only.
rw—read/write.
wo—write-only.
Prefixes Alias for file system.
flash:—Flash file system.
nvram:—NVRAM.
null:—Null destination for copies. You can copy a remote file to null to find its size.
rcp:—Remote copy (RCP) network server.
system:—Contains the system memory, including the running configuration.
tftp:—TFTP network server.
xmodem:—Obtain the file from a network machine by using the Xmodem protocol.
ymodem:—Obtain the file from a network machine by using the Ymodem protocol.
Command Description
dir [/all] [filesystem:][filename] Display a list of files on a file system.
show file systems Display more information about each of the files on a file system.
show file information file-url Display information about a specific file.
show file descriptors Display a list of open file descriptors. File descriptors are the internal representations
of open files. You can use this command to see if another user has a file open.
Command Purpose
Step 1 dir filesystem: Display the directories on the specified file system.
For filesystem:, use flash: for the system board flash device.
Step 2 cd new_configs Change to the directory of interest.
The command example shows how to change to the directory named
new_configs.
Step 3 pwd Display the working directory.
Command Purpose
Step 1 dir filesystem: Display the directories on the specified file system.
For filesystem:, use flash: for the system board flash device.
Step 2 mkdir old_configs Create a new directory.
The command example shows how to create the directory named old_configs.
Directory names are case sensitive.
Directory names are limited to 45 characters between the slashes (/); the name
cannot contain control characters, spaces, deletes, slashes, quotes, semicolons,
or colons.
Step 3 dir filesystem: Verify your entry.
To delete a directory with all its files and subdirectories, use the delete /force /recursive
filesystem:/file-url privileged EXEC command.
Use the /recursive keyword to delete the named directory and all subdirectories and the files contained
in it. Use the /force keyword to suppress the prompting that confirms a deletion of each file in the
directory. You are prompted only once at the beginning of this deletion process. Use the /force and
/recursive keywords for deleting old software images that were installed by using the archive
download-sw command but are no longer needed.
For filesystem, use flash: for the system board flash device. For file-url, enter the name of the directory
to be deleted. All the files in the directory and the directory are removed.
Caution When files and directories are deleted, their contents cannot be recovered.
Copying Files
To copy a file from a source to a destination, use the copy source-url destination-url privileged EXEC
command. For the source and destination URLs, you can use running-config and startup-config
keyword shortcuts. For example, the copy running-config startup-config command saves the currently
running configuration file to the NVRAM section of flash memory to be used as the configuration during
system initialization.
You can also copy from special file systems (xmodem:, ymodem:) as the source for the file from a
network machine that uses the Xmodem or Ymodem protocol.
Network file system URLs include ftp:, rcp:, and tftp: and have these syntaxes:
• FTP—ftp:[[//username [:password]@location]/directory]/filename
• RCP—rcp:[[//username@location]/directory]/filename
• TFTP—tftp:[[//location]/directory]/filename
Local writable file systems include flash:.
Some invalid combinations of source and destination exist. Specifically, you cannot copy these
combinations:
• From a running configuration to a running configuration
• From a startup configuration to a startup configuration
• From a device to the same device (for example, the copy flash: flash: command is invalid)
For specific examples of using the copy command with configuration files, see the “Working with
Configuration Files” section on page A-7.
To copy software images either by downloading a new version or uploading the existing one, use the
archive download-sw or the archive upload-sw privileged EXEC command. For more information, see
the “Replacing and Rolling Back Configurations” section on page A-18.
Deleting Files
When you no longer need a file on a flash memory device, you can permanently delete it. To delete a file
or directory from a specified flash device, use the delete [/force] [/recursive] [filesystem:]/file-url
privileged EXEC command.
Use the /recursive keyword for deleting a directory and all subdirectories and the files contained in it.
Use the /force keyword to suppress the prompting that confirms a deletion of each file in the directory.
You are prompted only once at the beginning of this deletion process. Use the /force and /recursive
keywords for deleting old software images that were installed by using the archive download-sw
command but are no longer needed.
If you omit the filesystem: option, the switch uses the default device specified by the cd command. For
file-url, you specify the path (directory) and the name of the file to be deleted.
When you attempt to delete any files, the system prompts you to confirm the deletion.
This example shows how to delete the file myconfig from the default flash memory device:
Switch# delete myconfig
Note Instead of using the copy privileged EXEC command or the archive tar privileged EXEC command, we
recommend using the archive download-sw and archive upload-sw privileged EXEC commands to
download and upload software image files.
For destination-url, specify the destination URL alias for the local or network file system and the name
of the tar file to create. These options are supported:
• For the local flash file system, the syntax is
flash:
• For the FTP, the syntax is ftp:[[//username[:password]@location]/directory]/tar-filename.tar
• For the RCP, the syntax is rcp:[[//username@location]/directory]/tar-filename.tar
• For the TFTP, the syntax is tftp:[[//location]/directory]/tar-filename.tar
The tar-filename.tar is the tar file to be created.
For flash:/file-url, specify the location on the local flash file system from which the new tar file is
created. You can also specify an optional list of files or directories within the source directory to write
to the new tar file. If none are specified, all files and directories at this level are written to the newly
created tar file.
This example shows how to create a tar file. This command writes the contents of the new-configs
directory on the local flash device to a file named saved.tar on the TFTP server at 172.20.10.30:
Switch# archive tar /create tftp:172.20.10.30/saved.tar flash:/new-configs
This example shows how to display only the image-tv0-mz-121/html directory and its contents:
Switch# archive tar /table flash:image-tv0-m.tar image-tv0-mz-121/html
image-tv0-mz-121/html/ (directory)
image-tv0-mz-121/html/foo.html (0 bytes)
<output truncated>
You can copy (download) configuration files from a TFTP, FTP, or RCP server to the running
configuration or startup configuration of the switch. You might want to perform this for one of these
reasons:
• To restore a backed-up configuration file.
• To use the configuration file for another switch. For example, you might add another switch to your
network and want it to have a configuration similar to the original switch. By copying the file to the
new switch, you can change the relevant parts rather than recreating the whole file.
• To load the same configuration commands on all the switches in your network so that all the
switches have similar configurations.
You can copy (upload) configuration files from the switch to a file server by using TFTP, FTP, or RCP.
You might perform this task to back up a current configuration file to a server before changing its
contents so that you can later restore the original configuration file from the server.
The protocol you use depends on which type of server you are using. The FTP and RCP transport
mechanisms provide faster performance and more reliable delivery of data than TFTP. These
improvements are possible because FTP and RCP are built on and use the TCP/IP stack, which is
connection-oriented.
This section includes this information:
• Guidelines for Creating and Using Configuration Files, page A-8
• Configuration File Types and Location, page A-9
• Creating a Configuration File By Using a Text Editor, page A-9
• Copying Configuration Files By Using TFTP, page A-9
• Copying Configuration Files By Using FTP, page A-11
• Copying Configuration Files By Using RCP, page A-14
• Clearing Configuration Information, page A-17
• Replacing and Rolling Back Configurations, page A-18
Note The copy {ftp: | rcp: | tftp:} system:running-config privileged EXEC command loads the
configuration files on the switch as if you were entering the commands at the command line. The switch
does not erase the existing running configuration before adding the commands. If a command in the
copied configuration file replaces a command in the existing configuration file, the existing command is
erased. For example, if the copied configuration file contains a different IP address in a particular
command than the existing configuration, the IP address in the copied configuration is used. However,
some commands in the existing configuration might not be replaced or negated. In this case, the resulting
configuration file is a mixture of the existing configuration file and the copied configuration file, with
the copied configuration file having precedence.
To restore a configuration file to an exact copy of a file stored on a server, copy the configuration file
directly to the startup configuration (by using the copy {ftp: | rcp: | tftp:} nvram:startup-config
privileged EXEC command), and reload the switch.
Note You must restart the inetd daemon after modifying the /etc/inetd.conf and /etc/services files.
To restart the daemon, either stop the inetd process and restart it, or enter a fastboot
command (on the SunOS 4.x) or a reboot command (on Solaris 2.x or SunOS 5.x). For more
information on the TFTP daemon, see the documentation for your workstation.
• Ensure that the switch has a route to the TFTP server. The switch and the TFTP server must be in
the same subnetwork if you do not have a router to route traffic between subnets. Check connectivity
to the TFTP server by using the ping command.
• Ensure that the configuration file to be downloaded is in the correct directory on the TFTP server
(usually /tftpboot on a UNIX workstation).
• For download operations, ensure that the permissions on the file are set correctly. The permission
on the file should be world-read.
• Before uploading the configuration file, you might need to create an empty file on the TFTP server.
To create an empty file, enter the touch filename command, where filename is the name of the file
you will use when uploading it to the server.
• During upload operations, if you are overwriting an existing file (including an empty file, if you had
to create one) on the server, ensure that the permissions on the file are set correctly. Permissions on
the file should be world-write.
Step 1 Copy the configuration file to the appropriate TFTP directory on the workstation.
Step 2 Verify that the TFTP server is properly configured by referring to the “Preparing to Download or Upload
a Configuration File By Using TFTP” section on page A-10.
Step 3 Log into the switch through the console port or a Telnet session.
Step 4 Download the configuration file from the TFTP server to configure the switch.
Specify the IP address or hostname of the TFTP server and the name of the file to download.
Use one of these privileged EXEC commands:
• copy tftp:[[[//location]/directory]/filename] system:running-config
• copy tftp:[[[//location]/directory]/filename] nvram:startup-config
The configuration file downloads, and the commands are executed as the file is parsed line-by-line.
This example shows how to configure the software from the file tokyo-confg at IP address 172.16.2.155:
Switch# copy tftp://172.16.2.155/tokyo-confg system:running-config
Configure using tokyo-confg from 172.16.2.155? [confirm] y
Booting tokyo-confg from 172.16.2.155:!!! [OK - 874/16000 bytes]
Step 1 Verify that the TFTP server is properly configured by referring to the “Preparing to Download or Upload
a Configuration File By Using TFTP” section on page A-10.
Step 2 Log into the switch through the console port or a Telnet session.
Step 3 Upload the switch configuration to the TFTP server. Specify the IP address or hostname of the TFTP
server and the destination filename.
Use one of these privileged EXEC commands:
• copy system:running-config tftp:[[[//location]/directory]/filename]
• copy nvram:startup-config tftp:[[[//location]/directory]/filename]
The file is uploaded to the TFTP server.
This example shows how to upload a configuration file from a switch to a TFTP server:
Switch# copy system:running-config tftp://172.16.2.155/tokyo-confg
Write file tokyo-confg on host 172.16.2.155? [confirm] y
#
Writing tokyo-confg!!! [OK]
The username and password must be associated with an account on the FTP server. If you are writing to
the server, the FTP server must be properly configured to accept your FTP write request.
Use the ip ftp username and ip ftp password commands to specify a username and password for all
copies. Include the username in the copy command if you want to specify only a username for that copy
operation.
If the server has a directory structure, the configuration file is written to or copied from the directory
associated with the username on the server. For example, if the configuration file resides in the home
directory of a user on the server, specify that user's name as the remote username.
For more information, see the documentation for your FTP server.
This section includes this information:
• Preparing to Download or Upload a Configuration File By Using FTP, page A-12
• Downloading a Configuration File By Using FTP, page A-12
• Uploading a Configuration File By Using FTP, page A-13
Command Purpose
Step 1 Verify that the FTP server is properly configured by referring
to the “Preparing to Download or Upload a Configuration
File By Using FTP” section on page A-12.
Step 2 Log into the switch through the console port or a Telnet
session.
Step 3 configure terminal Enter global configuration mode on the switch.
This step is required only if you override the default remote
username or password (see Steps 4, 5, and 6).
Command Purpose
Step 4 ip ftp username username (Optional) Change the default remote username.
Step 5 ip ftp password password (Optional) Change the default password.
Step 6 end Return to privileged EXEC mode.
Step 7 copy Using FTP, copy the configuration file from a network server
ftp:[[[//[username[:password]@]location]/directory] to the running configuration or to the startup configuration
/filename] system:running-config file.
or
copy
ftp:[[[//[username[:password]@]location]/directory]
/filename] nvram:startup-config
This example shows how to copy a configuration file named host1-confg from the netadmin1 directory
on the remote server with an IP address of 172.16.101.101 and to load and run those commands on the
switch:
Switch# copy ftp://netadmin1:mypass@172.16.101.101/host1-confg system:running-config
Configure using host1-confg from 172.16.101.101? [confirm]
Connected to 172.16.101.101
Loading 1112 byte file host1-confg:![OK]
Switch#
%SYS-5-CONFIG: Configured from host1-config by ftp from 172.16.101.101
This example shows how to specify a remote username of netadmin1. The software copies the
configuration file host2-confg from the netadmin1 directory on the remote server with an IP address
of 172.16.101.101 to the switch startup configuration.
Switch# configure terminal
Switch(config)# ip ftp username netadmin1
Switch(config)# ip ftp password mypass
Switch(config)# end
Switch# copy ftp: nvram:startup-config
Address of remote host [255.255.255.255]? 172.16.101.101
Name of configuration file[rtr2-confg]? host2-confg
Configure using host2-confg from 172.16.101.101?[confirm]
Connected to 172.16.101.101
Loading 1112 byte file host2-confg:![OK]
[OK]
Switch#
%SYS-5-CONFIG_NV:Non-volatile store configured from host2-config by ftp from
172.16.101.101
Command Purpose
Step 1 Verify that the FTP server is properly configured by referring
to the “Preparing to Download or Upload a Configuration
File By Using FTP” section on page A-12.
Step 2 Log into the switch through the console port or a Telnet
session.
Command Purpose
Step 3 configure terminal Enter global configuration mode.
This step is required only if you override the default remote
username or password (see Steps 4, 5, and 6).
Step 4 ip ftp username username (Optional) Change the default remote username.
Step 5 ip ftp password password (Optional) Change the default password.
Step 6 end Return to privileged EXEC mode.
Step 7 copy system:running-config Using FTP, store the switch running or startup configuration
ftp:[[[//[username[:password]@]location]/directory] file to the specified location.
/filename]
or
copy nvram:startup-config
ftp:[[[//[username[:password]@]location]/directory]
/filename]
This example shows how to copy the running configuration file named switch2-confg to the netadmin1
directory on the remote host with an IP address of 172.16.101.101:
Switch# copy system:running-config ftp://netadmin1:mypass@172.16.101.101/switch2-confg
Write file switch2-confg on host 172.16.101.101?[confirm]
Building configuration...[OK]
Connected to 172.16.101.101
Switch#
This example shows how to store a startup configuration file on a server by using FTP to copy the file:
Switch# configure terminal
Switch(config)# ip ftp username netadmin2
Switch(config)# ip ftp password mypass
Switch(config)# end
Switch# copy nvram:startup-config ftp:
Remote host[]? 172.16.101.101
Name of configuration file to write [switch2-confg]?
Write file switch2-confg on host 172.16.101.101?[confirm]
![OK]
The RCP requires a client to send a remote username with each RCP request to a server. When you copy
a configuration file from the switch to a server, the Cisco IOS software sends the first valid username in
this list:
• The username specified in the copy command if a username is specified.
• The username set by the ip rcmd remote-username username global configuration command if the
command is configured.
• The remote username associated with the current TTY (terminal) process. For example, if the user
is connected to the router through Telnet and was authenticated through the username command,
the switch software sends the Telnet username as the remote username.
• The switch hostname.
For a successful RCP copy request, you must define an account on the network server for the remote
username. If the server has a directory structure, the configuration file is written to or copied from the
directory associated with the remote username on the server. For example, if the configuration file is in
the home directory of a user on the server, specify that user's name as the remote username.
This section includes this information:
• Preparing to Download or Upload a Configuration File By Using RCP, page A-15
• Downloading a Configuration File By Using RCP, page A-16
• Uploading a Configuration File By Using RCP, page A-17
If the switch IP address translates to Switch1.company.com, the .rhosts file for User0 on the RCP
server should contain this line:
Switch1.company.com Switch1
For more information, see the documentation for your RCP server.
Command Purpose
Step 1 Verify that the RCP server is properly configured by
referring to the “Preparing to Download or Upload a
Configuration File By Using RCP” section on page A-15.
Step 2 Log into the switch through the console port or a Telnet
session.
Step 3 configure terminal Enter global configuration mode.
This step is required only if you override the default remote
username (see Steps 4 and 5).
Step 4 ip rcmd remote-username username (Optional) Specify the remote username.
Step 5 end Return to privileged EXEC mode.
Step 6 copy Using RCP, copy the configuration file from a network
rcp:[[[//[username@]location]/directory]/filename] server to the running configuration or to the startup
system:running-config configuration file.
or
copy
rcp:[[[//[username@]location]/directory]/filename]
nvram:startup-config
This example shows how to copy a configuration file named host1-confg from the netadmin1 directory
on the remote server with an IP address of 172.16.101.101 and load and run those commands on the
switch:
Switch# copy rcp://netadmin1@172.16.101.101/host1-confg system:running-config
Configure using host1-confg from 172.16.101.101? [confirm]
Connected to 172.16.101.101
Loading 1112 byte file host1-confg:![OK]
Switch#
%SYS-5-CONFIG: Configured from host1-config by rcp from 172.16.101.101
This example shows how to specify a remote username of netadmin1. Then it copies the configuration
file host2-confg from the netadmin1 directory on the remote server with an IP address of 172.16.101.101
to the startup configuration:
Switch# configure terminal
Switch(config)# ip rcmd remote-username netadmin1
Switch(config)# end
Switch# copy rcp: nvram:startup-config
Address of remote host [255.255.255.255]? 172.16.101.101
Name of configuration file[rtr2-confg]? host2-confg
Configure using host2-confg from 172.16.101.101?[confirm]
Connected to 172.16.101.101
Loading 1112 byte file host2-confg:![OK]
[OK]
Switch#
%SYS-5-CONFIG_NV:Non-volatile store configured from host2-config by rcp from
172.16.101.101
Command Purpose
Step 1 Verify that the RCP server is properly configured by
referring to the “Preparing to Download or Upload a
Configuration File By Using RCP” section on page A-15.
Step 2 Log into the switch through the console port or a Telnet
session.
Step 3 configure terminal Enter global configuration mode.
This step is required only if you override the default remote
username (see Steps 4 and 5).
Step 4 ip rcmd remote-username username (Optional) Specify the remote username.
Step 5 end Return to privileged EXEC mode.
Step 6 copy system:running-config Using RCP, copy the configuration file from a switch running
rcp:[[[//[username@]location]/directory]/filename] or startup configuration file to a network server.
or
copy nvram:startup-config
rcp:[[[//[username@]location]/directory]/filename]
This example shows how to copy the running configuration file named switch2-confg to the netadmin1
directory on the remote host with an IP address of 172.16.101.101:
Switch# copy system:running-config rcp://netadmin1@172.16.101.101/switch2-confg
Write file switch-confg on host 172.16.101.101?[confirm]
Building configuration...[OK]
Connected to 172.16.101.101
Switch#
Caution You cannot restore the startup configuration file after it has been deleted.
Archiving a Configuration
The configuration archive provides a mechanism to store, organize, and manage an archive of
configuration files. The configure replace privileged EXEC command increases the configuration
rollback capability. As an alternative, you can save copies of the running configuration by using the copy
running-config destination-url privileged EXEC command, storing the replacement file either locally
or remotely. However, this method lacks any automated file management. The configuration replacement
and rollback feature can automatically save copies of the running configuration to the configuration
archive.
You use the archive config privileged EXEC command to save configurations in the configuration
archive by using a standard location and filename prefix that is automatically appended with an
incremental version number (and optional timestamp) as each consecutive file is saved. You can specify
how many versions of the running configuration are kept in the archive. After the maximum number of
files are saved, the oldest file is automatically deleted when the next, most recent file is saved. The show
archive privileged EXEC command displays information for all the configuration files saved in the
configuration archive.
The Cisco IOS configuration archive, in which the configuration files are stored and available for use
with the configure replace command, is in any of these file systems: FTP, HTTP, RCP, TFTP.
Replacing a Configuration
The configure replace privileged EXEC command replaces the running configuration with any saved
configuration file. When you enter the configure replace command, the running configuration is
compared with the specified replacement configuration, and a set of configuration differences is
generated. The resulting differences are used to replace the configuration. The configuration
replacement operation is usually completed in no more than three passes. To prevent looping behavior
no more than five passes are performed.
You can use the copy source-url running-config privileged EXEC command to copy a stored
configuration file to the running configuration. When using this command as an alternative to the
configure replace target-url privileged EXEC command, note these major differences:
• The copy source-url running-config command is a merge operation and preserves all the commands
from both the source file and the running configuration. This command does not remove commands
from the running configuration that are not present in the source file. In contrast, the configure
replace target-url command removes commands from the running configuration that are not present
in the replacement file and adds commands to the running configuration that are not present.
• You can use a partial configuration file as the source file for the copy source-url running-config
command. You must use a complete configuration file as the replacement file for the configure
replace target-url command.
You can also use the configure replace command to roll back changes that were made since the previous
configuration was saved. Instead of basing the rollback operation on a specific set of changes that were
applied, the configuration rollback capability reverts to a specific configuration based on a saved
configuration file.
If you want the configuration rollback capability, you must first save the running configuration before
making any configuration changes. Then, after entering configuration changes, you can use that saved
configuration file to roll back the changes by using the configure replace target-url command.
You can specify any saved configuration file as the rollback configuration. You are not limited to a fixed
number of rollbacks, as is the case in some rollback models.
Configuration Guidelines
Follow these guidelines when configuring and performing configuration replacement and rollback:
• Make sure that the switch has free memory larger than the combined size of the two configuration
files (the running configuration and the saved replacement configuration). Otherwise, the
configuration replacement operation fails.
• Make sure that the switch also has sufficient free memory to execute the configuration replacement
or rollback configuration commands.
• Certain configuration commands, such as those pertaining to physical components of a networking
device (for example, physical interfaces), cannot be added or removed from the running
configuration.
– A configuration replacement operation cannot remove the interface interface-id command line
from the running configuration if that interface is physically present on the device.
– The interface interface-id command line cannot be added to the running configuration if no
such interface is physically present on the device.
• When using the configure replace command, you must specify a saved configuration as the
replacement configuration file for the running configuration. The replacement file must be a
complete configuration generated by a Cisco IOS device (for example, a configuration generated by
the copy running-config destination-url command).
Note If you generate the replacement configuration file externally, it must comply with the format of files
generated by Cisco IOS devices.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 archive Enter archive configuration mode.
Step 3 path url Specify the location and filename prefix for the files in the configuration
archive.
Step 4 maximum number (Optional) Set the maximum number of archive files of the running
configuration to be saved in the configuration archive.
number—Maximum files of the running configuration file in the configuration
archive. Valid values are from 1 to 14. The default is 10.
Note Before using this command, you must first enter the path archive
configuration command to specify the location and filename prefix for
the files in the configuration archive.
Step 5 time-period minutes (Optional) Set the time increment for automatically saving an archive file of
the running configuration in the configuration archive.
minutes—Specify how often, in minutes, to automatically save an archive file
of the running configuration in the configuration archive.
Step 6 end Return to privileged EXEC mode.
Step 7 show running-config Verify the configuration.
Step 8 copy running-config (Optional) Save your entries in the configuration file.
startup-config
Command Purpose
Step 1 archive config (Optional) Save the running configuration file to the configuration archive.
Note Enter the path archive configuration command before using this
command.
Step 2 configure terminal Enter global configuration mode.
Step 3 Make necessary changes to the running configuration.
Step 4 exit Return to privileged EXEC mode.
Step 5 configure replace target-url [list] Replace the running configuration file with a saved configuration file.
[force] [time seconds] [nolock]
target-url—URL (accessible by the file system) of the saved configuration file
that is to replace the running configuration, such as the configuration file
created in Step 2 by using the archive config privileged EXEC command.
list—Display a list of the command entries applied by the software parser
during each pass of the configuration replacement operation. The total number
of passes also appears.
force— Replace the running configuration file with the specified saved
configuration file without prompting you for confirmation.
time seconds—Specify the time (in seconds) within which you must enter the
configure confirm command to confirm replacement of the running
configuration file. If you do not enter the configure confirm command within
the specified time limit, the configuration replacement operation is
automatically stopped. (In other words, the running configuration file is
restored to the configuration that existed before you entered the configure
replace command).
Note You must first enable the configuration archive before you can use the
time seconds command line option.
Note Instead of using the copy privileged EXEC command or the archive tar privileged EXEC command, we
recommend using the archive download-sw and archive upload-sw privileged EXEC commands to
download and upload software image files.
You download a switch image file from a TFTP, FTP, or RCP server to upgrade the switch software. If
you do not have access to a TFTP server, you can download a software image file directly to your PC or
workstation by using a web browser (HTTP). You can replace the current image with the new one or keep
the current image in flash memory after a download.
You upload a switch image file to a TFTP, FTP, or RCP server for backup purposes. You can use this
uploaded image for future downloads to the same switch or another of the same type.
The protocol you use depends on which type of server you are using. The FTP and RCP transport
mechanisms provide faster performance and more reliable delivery of data than TFTP. These
improvements are possible because FTP and RCP are built on and use the TCP/IP stack, which is
connection-oriented.
This section includes this information:
• Image Location on the Switch, page A-22
• tar File Format of Images on a Server or Cisco.com, page A-23
• Copying Image Files By Using TFTP, page A-23
• Copying Image Files By Using FTP, page A-26
• Copying Image Files By Using RCP, page A-31
Note For a list of software images and the supported upgrade paths, see the release notes that shipped with
your switch.
Note Disregard the stacking_number field. It does not apply to the switch.
Field Description
version_suffix Specifies the Cisco IOS image version string suffix
version_directory Specifies the directory where the Cisco IOS image is installed
image_name Specifies the name of the Cisco IOS image within the tar file
ios_image_file_size Specifies the Cisco IOS image size in the tar file, which is an approximate measure of how
much flash memory is required to hold just the Cisco IOS image
total_image_file_size Specifies the size of all the images (the Cisco IOS image files) in the tar file, which is an
approximate measure of how much flash memory is required to hold them
image_feature Describes the core functionality of the image
image_family Describes the family of products on which the software can be installed
Note Instead of using the copy privileged EXEC command or the archive tar privileged EXEC command, we
recommend using the archive download-sw and archive upload-sw privileged EXEC commands to
download and upload software image files.
Note You must restart the inetd daemon after modifying the /etc/inetd.conf and /etc/services files.
To restart the daemon, either stop the inetd process and restart it, or enter a fastboot
command (on the SunOS 4.x) or a reboot command (on Solaris 2.x or SunOS 5.x). For more
information on the TFTP daemon, see the documentation for your workstation.
• Ensure that the switch has a route to the TFTP server. The switch and the TFTP server must be in
the same subnetwork if you do not have a router to route traffic between subnets. Check connectivity
to the TFTP server by using the ping command.
• Ensure that the image to be downloaded is in the correct directory on the TFTP server (usually
/tftpboot on a UNIX workstation).
• For download operations, ensure that the permissions on the file are set correctly. The permission
on the file should be world-read.
• Before uploading the image file, you might need to create an empty file on the TFTP server. To
create an empty file, enter the touch filename command, where filename is the name of the file you
will use when uploading the image to the server.
• During upload operations, if you are overwriting an existing file (including an empty file, if you had
to create one) on the server, ensure that the permissions on the file are set correctly. Permissions on
the file should be world-write.
Command Purpose
Step 1 Copy the image to the appropriate TFTP directory on the
workstation. Make sure the TFTP server is properly configured; see
the “Preparing to Download or Upload an Image File By Using
TFTP” section on page A-24.
Step 2 Log into the switch through the console port or a Telnet session.
Step 3 archive download-sw /overwrite /reload Download the image file from the TFTP server to the switch, and
tftp:[[//location]/directory]/image-name.tar overwrite the current image.
• The /overwrite option overwrites the software image in flash
memory with the downloaded image.
• The /reload option reloads the system after downloading the
image unless the configuration has been changed and not been
saved.
• For //location, specify the IP address of the TFTP server.
• For /directory/image-name.tar, specify the directory
(optional) and the image to download. Directory and image
names are case sensitive.
Step 4 archive download-sw /leave-old-sw /reload Download the image file from the TFTP server to the switch, and
tftp:[[//location]/directory]/image-name.tar keep the current image.
• The /leave-old-sw option keeps the old software version after
a download.
• The /reload option reloads the system after downloading the
image unless the configuration has been changed and not been
saved.
• For //location, specify the IP address of the TFTP server.
• For /directory/image-name.tar, specify the directory
(optional) and the image to download. Directory and image
names are case sensitive.
The download algorithm verifies that the image is appropriate for the switch model and that enough
DRAM is present, or it aborts the process and reports an error. If you specify the /overwrite option, the
download algorithm removes the existing image on the flash device whether or not it is the same as the
new one, downloads the new image, and then reloads the software.
Note If the flash device has sufficient space to hold two images and you want to overwrite one of these images
with the same version, you must specify the /overwrite option.
If you specify the /leave-old-sw, the existing files are not removed. If there is not enough space to install
the new image and keep the current running image, the download process stops, and an error message
appears.
The algorithm installs the downloaded image on the system board flash device (flash:). The image is
placed into a new directory named with the software version string, and the BOOT environment variable
is updated to point to the newly installed image.
If you kept the old image during the download process (you specified the /leave-old-sw keyword), you
can remove it by entering the delete /force /recursive filesystem:/file-url privileged EXEC command.
For filesystem, use flash: for the system board flash device. For file-url, enter the directory name of the
old image. All the files in the directory and the directory are removed.
Caution For the download and upload algorithms to operate properly, do not rename image names.
Command Purpose
Step 1 Make sure the TFTP server is properly configured; see the
“Preparing to Download or Upload an Image File By Using TFTP”
section on page A-24.
Step 2 Log into the switch through the console port or a Telnet session.
Step 3 archive upload-sw Upload the currently running switch image to the TFTP server.
tftp:[[//location]/directory]/image-name.tar
• For //location, specify the IP address of the TFTP server.
• For /directory/image-name.tar, specify the directory (optional)
and the name of the software image to be uploaded. Directory
and image names are case sensitive. The image-name.tar is the
name of the software image to be stored on the server.
The archive upload-sw privileged EXEC command builds an image file on the server by uploading the
the info file and the Cisco IOS image file. After these files are uploaded, the upload algorithm creates
the tar file format.
Caution For the download and upload algorithms to operate properly, do not rename image names.
You upload a switch image file to a server for backup purposes. You can use this uploaded image for
future downloads to the switch or another switch of the same type.
Note Instead of using the copy privileged EXEC command or the archive tar privileged EXEC command, we
recommend using the archive download-sw and archive upload-sw privileged EXEC commands to
download and upload software image files.
• If you are accessing the switch through the console or a Telnet session and you do not have a valid
username, make sure that the current FTP username is the one that you want to use for the FTP
download. You can enter the show users privileged EXEC command to view the valid username. If
you do not want to use this username, create a new FTP username by using the ip ftp username
username global configuration command. This new name will be used during all archive operations.
The new username is stored in NVRAM. If you are accessing the switch through a Telnet session
and you have a valid username, this username is used, and you do not need to set the FTP username.
Include the username in the archive download-sw or archive upload-sw privileged EXEC
command if you want to specify a username for that operation only.
• When you upload an image file to the FTP server, it must be properly configured to accept the write
request from the user on the switch.
For more information, see the documentation for your FTP server.
Command Purpose
Step 1 Verify that the FTP server is properly configured by referring
to the “Preparing to Download or Upload an Image File By
Using FTP” section on page A-27.
Step 2 Log into the switch through the console port or a Telnet
session.
Step 3 configure terminal Enter global configuration mode.
This step is required only if you override the default remote
username or password (see Steps 4, 5, and 6).
Step 4 ip ftp username username (Optional) Change the default remote username.
Step 5 ip ftp password password (Optional) Change the default password.
Step 6 end Return to privileged EXEC mode.
Command Purpose
Step 7 archive download-sw /overwrite /reload Download the image file from the FTP server to the switch,
ftp:[[//username[:password]@location]/directory] and overwrite the current image.
/image-name.tar
• The /overwrite option overwrites the software image in
flash memory with the downloaded image.
• The /reload option reloads the system after downloading
the image unless the configuration has been changed and
not been saved.
• For //username[:password], specify the username and
password; these must be associated with an account on the
FTP server. For more information, see the “Preparing to
Download or Upload an Image File By Using FTP”
section on page A-27.
• For @location, specify the IP address of the FTP server.
• For directory/image-name.tar, specify the directory
(optional) and the image to download. Directory and
image names are case sensitive.
Step 8 archive download-sw /leave-old-sw /reload Download the image file from the FTP server to the switch,
ftp:[[//username[:password]@location]/directory] and keep the current image.
/image-name.tar
• The /leave-old-sw option keeps the old software version
after a download.
• The /reload option reloads the system after downloading
the image unless the configuration has been changed and
not been saved.
• For //username[:password], specify the username and
password. These must be associated with an account on
the FTP server. For more information, see the “Preparing
to Download or Upload an Image File By Using FTP”
section on page A-27.
• For @location, specify the IP address of the FTP server.
• For directory/image-name.tar, specify the directory
(optional) and the image to download. Directory and
image names are case sensitive.
The download algorithm verifies that the image is appropriate for the switch model and that enough
DRAM is present, or it aborts the process and reports an error. If you specify the /overwrite option, the
download algorithm removes the existing image on the flash device, whether or not it is the same as the
new one, downloads the new image, and then reloads the software.
Note If the flash device has sufficient space to hold two images and you want to overwrite one of these images
with the same version, you must specify the /overwrite option.
If you specify the /leave-old-sw, the existing files are not removed. If there is not enough space to install
the new image and keep the running image, the download process stops, and an error message appears.
The algorithm installs the downloaded image onto the system board flash device (flash:). The image is
placed into a new directory named with the software version string, and the BOOT environment variable
is updated to point to the newly installed image.
If you kept the old image during the download process (you specified the /leave-old-sw keyword), you
can remove it by entering the delete /force /recursive filesystem:/file-url privileged EXEC command.
For filesystem, use flash: for the system board flash device. For file-url, enter the directory name of the
old software image. All the files in the directory and the directory are removed.
Caution For the download and upload algorithms to operate properly, do not rename image names.
Command Purpose
Step 1 Verify that the FTP server is properly configured by referring
to the “Preparing to Download or Upload a Configuration
File By Using FTP” section on page A-12.
Step 2 Log into the switch through the console port or a Telnet
session.
Step 3 configure terminal Enter global configuration mode.
This step is required only if you override the default remote
username or password (see Steps 4, 5, and 6).
Step 4 ip ftp username username (Optional) Change the default remote username.
Step 5 ip ftp password password (Optional) Change the default password.
Step 6 end Return to privileged EXEC mode.
Step 7 archive upload-sw Upload the currently running switch image to the FTP server.
ftp:[[//[username[:password]@]location]/directory]/
• For //username:password, specify the username and
image-name.tar
password. These must be associated with an account on
the FTP server. For more information, see the “Preparing
to Download or Upload an Image File By Using FTP”
section on page A-27.
• For @location, specify the IP address of the FTP server.
• For /directory/image-name.tar, specify the directory
(optional) and the name of the software image to be
uploaded. Directory and image names are case sensitive.
The image-name.tar is the name of the software image
to be stored on the server.
The archive upload-sw command builds an image file on the server by uploading the info file and the
Cisco IOS image file. After these files are uploaded, the upload algorithm creates the tar file format.
Caution For the download and upload algorithms to operate properly, do not rename image names.
Note Instead of using the copy privileged EXEC command or the archive tar privileged EXEC command, we
recommend using the archive download-sw and archive upload-sw privileged EXEC commands to
download and upload software image files.
For the RCP copy request to execute successfully, an account must be defined on the network server for
the remote username. If the server has a directory structure, the image file is written to or copied from
the directory associated with the remote username on the server. For example, if the image file resides
in the home directory of a user on the server, specify that user’s name as the remote username.
Before you begin downloading or uploading an image file by using RCP, do these tasks:
• Ensure that the workstation acting as the RCP server supports the remote shell (rsh).
• Ensure that the switch has a route to the RCP server. The switch and the server must be in the same
subnetwork if you do not have a router to route traffic between subnets. Check connectivity to the
RCP server by using the ping command.
• If you are accessing the switch through the console or a Telnet session and you do not have a valid
username, make sure that the current RCP username is the one that you want to use for the RCP
download. You can enter the show users privileged EXEC command to view the valid username. If
you do not want to use this username, create a new RCP username by using the ip rcmd
remote-username username global configuration command to be used during all archive
operations. The new username is stored in NVRAM. If you are accessing the switch through a Telnet
session and you have a valid username, this username is used, and there is no need to set the RCP
username. Include the username in the archive download-sw or archive upload-sw privileged
EXEC command if you want to specify a username only for that operation.
• When you upload an image to the RCP to the server, it must be properly configured to accept the
RCP write request from the user on the switch. For UNIX systems, you must add an entry to the
.rhosts file for the remote user on the RCP server. For example, suppose the switch contains these
configuration lines:
hostname Switch1
ip rcmd remote-username User0
If the switch IP address translates to Switch1.company.com, the .rhosts file for User0 on the RCP
server should contain this line:
Switch1.company.com Switch1
For more information, see the documentation for your RCP server.
Command Purpose
Step 1 Verify that the RCP server is properly configured by
referring to the “Preparing to Download or Upload an Image
File By Using RCP” section on page A-31.
Step 2 Log into the switch through the console port or a Telnet
session.
Step 3 configure terminal Enter global configuration mode.
This step is required only if you override the default remote
username (see Steps 4 and 5).
Step 4 ip rcmd remote-username username (Optional) Specify the remote username.
Command Purpose
Step 5 end Return to privileged EXEC mode.
Step 6 archive download-sw /overwrite /reload Download the image file from the RCP server to the switch,
rcp:[[[//[username@]location]/directory]/image-na and overwrite the current image.
me.tar]
• The /overwrite option overwrites the software image in
flash memory with the downloaded image.
• The /reload option reloads the system after downloading
the image unless the configuration has been changed and
not been saved.
• For //username, specify the username. For the RCP copy
request to execute successfully, an account must be
defined on the network server for the remote username.
For more information, see the “Preparing to Download
or Upload an Image File By Using RCP” section on
page A-31.
• For @location, specify the IP address of the RCP server.
• For /directory/image-name.tar, specify the directory
(optional) and the image to download. Directory and
image names are case sensitive.
Step 7 archive download-sw /leave-old-sw /reload Download the image file from the RCP server to the switch,
rcp:[[[//[username@]location]/directory]/image-na and keep the current image.
me.tar]
• The /leave-old-sw option keeps the old software version
after a download.
• The /reload option reloads the system after downloading
the image unless the configuration has been changed and
not been saved.
• For //username, specify the username. For the RCP copy
request to execute, an account must be defined on the
network server for the remote username. For more
information, see the “Preparing to Download or Upload
an Image File By Using RCP” section on page A-31.
• For @location, specify the IP address of the RCP server.
• For /directory]/image-name.tar, specify the directory
(optional) and the image to download. Directory and
image names are case sensitive.
The download algorithm verifies that the image is appropriate for the switch model and that enough
DRAM is present, or it aborts the process and reports an error. If you specify the /overwrite option, the
download algorithm removes the existing image on the flash device whether or not it is the same as the
new one, downloads the new image, and then reloads the software.
Note If the flash device has sufficient space to hold two images and you want to overwrite one of these images
with the same version, you must specify the /overwrite option.
If you specify the /leave-old-sw, the existing files are not removed. If there is not enough room to install
the new image an keep the running image, the download process stops, and an error message appears.
The algorithm installs the downloaded image onto the system board flash device (flash:). The image is
placed into a new directory named with the software version string, and the BOOT environment variable
is updated to point to the newly installed image.
If you kept the old software during the download process (you specified the /leave-old-sw keyword), you
can remove it by entering the delete /force /recursive filesystem:/file-url privileged EXEC command.
For filesystem, use flash: for the system board flash device. For file-url, enter the directory name of the
old software image. All the files in the directory and the directory are removed.
Caution For the download and upload algorithms to operate properly, do not rename image names.
Command Purpose
Step 1 Verify that the RCP server is properly configured by referring to
the “Preparing to Download or Upload an Image File By Using
RCP” section on page A-31.
Step 2 Log into the switch through the console port or a Telnet session.
Step 3 configure terminal Enter global configuration mode.
This step is required only if you override the default remote
username (see Steps 4 and 5).
Step 4 ip rcmd remote-username username (Optional) Specify the remote username.
Step 5 end Return to privileged EXEC mode.
Step 6 archive upload-sw Upload the currently running switch image to the RCP server.
rcp:[[[//[username@]location]/directory]/image-
• For //username, specify the username; for the RCP copy
name.tar]
request to execute, an account must be defined on the
network server for the remote username. For more
information, see the “Preparing to Download or Upload an
Image File By Using RCP” section on page A-31.
• For @location, specify the IP address of the RCP server.
• For /directory]/image-name.tar, specify the directory
(optional) and the name of the software image to be
uploaded. Directory and image names are case sensitive.
• The image-name.tar is the name of software image to be
stored on the server.
The archive upload-sw privileged EXEC command builds an image file on the server by uploading the
info file and the Cisco IOS image file. After these files are uploaded, the upload algorithm creates the
tar file format.
Caution For the download and upload algorithms to operate properly, do not rename image names.
This appendix lists some of the command-line interface (CLI) commands that are displayed when you
enter the question mark (?) at the Catalyst 3750 Metro switch prompt but are not supported in this
release, either because they are not tested, or because of Catalyst 3750 Metro switch hardware
limitations. This is not a complete list. The unsupported commands are listed by software feature and
command mode.
ARP
CGMP
Debug
FallBack Bridging
HSRP
IEEE 802.1ad
IEEE 802.1x
Note Entering this command can put the port in error-disabled state.
Note The switch does not support IEEE 802.1x MAC authentication bypass.
dot1x pae
dot1x host-mode multi-domain
IGMP Snooping
Interfaces
Note The switchport broadcast, switchport multicast, and switchport unicast commands have been
replaced by the storm-control {broadcast | multicast | unicast} level level [.level] interface
configuration command.
IP Multicast Routing
IP Unicast Routing
Miscellaneous
MPLS
Physical Interfaces
ip rsvp bandwidth {mam | rdm}
ip rsvp signalling hello [bfd | dscp | fast-reroute | graceful-restart | refresh | reroute]
mpls traffic-eng srlg
Tunnel Interfaces
tunnel mpls traffic-eng auto-bw
tunnel mpls traffic-eng backup-bw
tunnel mpls traffic-eng exp
tunnel mpls traffic-eng exp-bundle
tunnel mpls traffic-eng forwarding-adjacency
tunnel mpls traffic-eng path-option dynamic attributes
tunnel mpls traffic-eng path-option explicit name attributes
tunnel mpls traffic-eng path-selection
MSDP
QoS
RADIUS
SNMP
Spanning Tree
VLAN
VTP
Note This command has been replaced by the vtp global configuration command.
RSPAN 28-9
DHCP for IPv6
See DHCPv6
SNMP 31-7
enabling
SPAN 28-9
relay agent 21-10
SSL 7-44
standard QoS 34-50
server 21-10
STP 16-11
DHCP-based autoconfiguration
client request message exchange 3-4
system message logging 30-3
system name and prompt 5-8
configuring
client side 3-3
TACACS+ 7-13
UDLD 27-4
DNS 3-7
VLANs 11-7
server-side 21-10
VMPS 11-29
TFTP server 3-7
example 3-9
voice VLAN 14-3
lease options
VTP 12-6
for IP address information 3-6
Y.1731 43-25
for receiving the configuration file 3-6
default gateway 3-14, 36-10
overview 3-3
default networks 36-100
relationship to BOOTP 3-3
default router preference
See DRP DHCP-based autoconfiguration and image update
configuring 34-73
described 34-15
I
hierarchical QoS
See QoS IBGP 36-42, 44-6
Hierarchical QoS, and EtherChannels 34-104 ICMP
history IPv6 37-4
changing the buffer size 2-5 redirect messages 36-10
described 2-4 time exceeded messages 48-11
disabling 2-5 traceroute and 48-11
recalling commands 2-5 unreachable messages 33-19
history table, level and number of syslog messages 30-9 unreachable messages and IPv6 39-4
host ports unreachables and ACLs 33-21
configuring 13-11 ICMP Echo operation
kinds of 13-2 configuring 41-11
hosts, limit on dynamic ports 11-33 IP SLAs 41-11
Hot Standby Router Protocol ICMP ping
executing 48-8
benefits of 45-25
monitoring
packet rate loss 45-63
clearing the cache 45-62
peering devices 45-63
configuration guidelines 45-11
tracing a path 45-63
filtering incoming RP announcement
messages 45-28 multicast forwarding, described 45-7
overview 45-6 PIMv1 and PIMv2 interoperability 45-10
preventing candidate RP spoofing 45-28 protocol interaction 45-2
preventing join messages to false RPs 45-27 reverse path check (RPF) 45-7
setting up in a new internetwork 45-25 routing table
using with BSR 45-33 deleting 45-62
bootstrap router displaying 45-62
configuration guidelines 45-11 RP
configuring candidate BSRs 45-31 assigning manually 45-23
configuring candidate RPs 45-32 configuring Auto-RP 45-25
described
MAC address learning, disabling on a VLAN 5-23
hierarchical 34-6, 34-34
MAC address-table move update
ingress 34-6, 34-14
configuration guidelines 20-8
matching
configuring 20-12
IPv6 ACLs 39-3
default configuration 20-8
matching, ACLs 33-7
description 20-6
maximum aging time
monitoring 20-14
MSTP 17-23
MAC address-to-VLAN mapping 11-28
STP 16-21
MAC extended access lists
maximum hop count, MSTP 17-24
applying to Layer 2 interfaces 33-28
maximum number of allowed devices, port-based
configuring for QoS 34-66
authentication 8-16
creating 33-27
maximum-paths command 36-50, 36-98
defined 33-27
membership mode, VLAN port 11-3
for QoS classification 34-9
MEPs
macros
and STP 43-4
See Smartports macros
defined 43-3
Maintenance end points
messages
See MEPs
logging ACL violations 33-15
Maintenance intermediate points
to users through banners 5-10
See MIPs
messages, Ethernet OAM 43-33
manageability features 1-3
metrics, in BGP 36-50
management options
metric translations, between routing protocols 36-104
CLI 2-1
metro tags 15-2
CNS 1-3, 4-1
MIBs
SNMP 31-1
overview 31-1
manual preemption, REP, configuring 19-14
SNMP interaction with 31-5
mapping tables for QoS
MIPs
configuring
and STP 43-4
CoS-to-DSCP 34-81
defined 43-4
DSCP 34-80
mirroring traffic for analysis 28-1
DSCP-to-CoS 34-84
mismatches, autonegotiation 48-7
DSCP-to-DSCP-mutation 34-85
module number 9-7
IP-precedence-to-DSCP 34-82
monitoring
policed-DSCP 34-83
802.1Q tunneling 15-27
described 34-17
access groups 33-42
marking
ACL configuration 33-42
action in
BGP 36-62
hierarchical policy map 34-111, 34-114
cables for unidirectional links 27-1
ingress policy map 34-69, 34-79
CDP 25-4