3110 SCG
Uploaded by
dubravko_akmacic3110 SCG
Uploaded by
dubravko_akmacicCisco Catalyst Switch Module 3110
and 3012 for IBM BladeCenter Software
Configuration Guide
Cisco IOS Release 12.2(40)EX2
April 2008
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
Text Part Number: OL-12189-01
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL
STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCBs public
domain version of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco StadiumVision, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work,
Live, Play, and Learn is a service mark; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP,
CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity,
Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone,
iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MGX, Networkers,
Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to
Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain
other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship
between Cisco and any other company. (0804R)
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
2008 Cisco Systems, Inc. All rights reserved.
CONTENTS
Preface
xliii
Audience
Purpose
xliii
xliii
Conventions
xliv
Related Publications
xliv
Obtaining Documentation and Submitting a Service Request
CHAPTER
Overview
xlv
1-1
Features 1-1
Deployment Features 1-3
Performance Features 1-4
Management Options 1-5
Manageability Features 1-6
Availability and Redundancy Features
VLAN Features 1-8
Security Features 1-9
QoS and CoS Features 1-10
Layer 3 Features 1-12
Monitoring Features 1-13
1-7
Default Settings After Initial Switch Configuration
1-14
Network Configuration Examples 1-16
Design Concepts for Using the Switch 1-16
Small to Medium-Sized Network 1-19
Where to Go Next
CHAPTER
1-20
Using the Command-Line Interface
Understanding Command Modes
Understanding the Help System
2-1
2-1
2-3
Understanding Abbreviated Commands
2-4
Understanding no and default Forms of Commands
Understanding CLI Error Messages
Using Configuration Logging
Using Command History
2-4
2-5
2-5
2-6
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
iii
Contents
Changing the Command History Buffer Size 2-6
Recalling Commands 2-6
Disabling the Command History Feature 2-7
Using Editing Features 2-7
Enabling and Disabling Editing Features 2-7
Editing Commands through Keystrokes 2-8
Editing Command Lines that Wrap 2-9
Searching and Filtering Output of show and more Commands
2-10
Accessing the CLI 2-10
Accessing the CLI through a Console Connection or through Telnet
CHAPTER
Assigning the Switch IP Address and Default Gateway
Understanding the Boot Process
2-11
3-1
3-1
Assigning Switch Information 3-2
Default Switch Information 3-3
Understanding DHCP-Based Autoconfiguration 3-3
DHCP Client Request Process 3-4
Configuring DHCP-Based Autoconfiguration 3-5
DHCP Server Configuration Guidelines 3-5
Configuring the TFTP Server 3-6
Configuring the DNS 3-6
Configuring the Relay Device 3-7
Obtaining Configuration Files 3-7
Example Configuration 3-8
Understanding DHCP-based Autoconfiguration and Image Update 3-10
DHCP Autoconfiguration 3-10
DHCP Auto-Image Update 3-10
Limitations and Restrictions 3-10
Configuring the DHCP Auto Configuration and Image Update Features 3-11
Configuring DHCP Autoconfiguration (Only Configuration File) 3-11
Configuring DHCP Auto-Image Update (Configuration File and Image) 3-12
Configuring the Client 3-13
Manually Assigning IP Information 3-14
Configuring Protected Mode 3-15
Understanding Protected Mode 3-15
Configuration Guidelines and Restrictions
Enabling Protected Mode 3-16
Checking and Saving the Running Configuration
Modifying the Startup Configuration
3-16
3-17
3-18
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
iv
OL-12189-01
Contents
Default Boot Configuration 3-18
Automatically Downloading a Configuration File 3-18
Specifying the Filename to Read and Write the System Configuration
Booting Manually 3-19
Booting a Specific Software Image 3-20
Controlling Environment Variables 3-21
3-18
Scheduling a Reload of the Software Image 3-23
Configuring a Scheduled Reload 3-23
Displaying Scheduled Reload Information 3-24
CHAPTER
Configuring Cisco IOS CNS Agents
4-1
Understanding Cisco Configuration Engine Software 4-1
Configuration Service 4-2
Event Service 4-3
NameSpace Mapper 4-3
What You Should Know About the CNS IDs and Device Hostnames
ConfigID 4-3
DeviceID 4-4
Hostname and DeviceID 4-4
Using Hostname, DeviceID, and ConfigID 4-4
Understanding Cisco IOS Agents 4-5
Initial Configuration 4-5
Incremental (Partial) Configuration
Synchronized Configuration 4-6
4-3
4-6
Configuring Cisco IOS Agents 4-6
Enabling Automated CNS Configuration 4-6
Enabling the CNS Event Agent 4-7
Enabling the Cisco IOS CNS Agent 4-9
Enabling an Initial Configuration 4-9
Enabling a Partial Configuration 4-13
Displaying CNS Configuration
CHAPTER
Managing Switch Stacks
4-14
5-1
Understanding Switch Stacks 5-1
Switch Stack Membership 5-3
Stack Master Election and Re-Election 5-6
Switch Stack Bridge ID and Router MAC Address
Stack Member Numbers 5-8
Stack Member Priority Values 5-9
5-8
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
Contents
Switch Stack Offline Configuration 5-9
Effects of Adding a Provisioned Switch to a Switch Stack 5-10
Effects of Replacing a Provisioned Switch in a Switch Stack 5-11
Effects of Removing a Provisioned Switch from a Switch Stack 5-11
Hardware Compatibility and SDM Mismatch Mode in Switch Stacks 5-11
Switch Stack Software Compatibility Recommendations 5-12
Stack Protocol Version Compatibility 5-12
Major Version Number Incompatibility Among Switches 5-12
Minor Version Number Incompatibility Among Switches 5-12
Understanding Auto-Upgrade and Auto-Advise 5-13
Auto-Upgrade and Auto-Advise Example Messages 5-14
Incompatible Software and Stack Member Image Upgrades 5-16
Switch Stack Configuration Files 5-16
Additional Considerations for System-Wide Configuration on Switch Stacks 5-17
Switch Stack Management Connectivity 5-17
Connectivity to the Switch Stack Through an IP Address 5-18
Connectivity to the Switch Stack Through an SSH Session 5-18
Connectivity to the Switch Stack Through Console Ports or Ethernet Management Ports
Connectivity to Specific Stack Members 5-18
Switch Stack Configuration Scenarios 5-19
Configuring the Switch Stack 5-21
Default Switch Stack Configuration 5-21
Configuration Guidelines 5-21
Enabling Persistent MAC Address 5-22
Assigning Stack Member Information 5-24
Assigning a Stack Member Number 5-24
Setting the Stack Member Priority Value 5-25
Provisioning a New Member for a Switch Stack
Accessing the CLI of a Specific Stack Member
Displaying Switch Stack Information
CHAPTER
Administering the Switch
5-18
5-25
5-26
5-27
6-1
Managing the System Time and Date 6-1
Understanding the System Clock 6-1
Understanding Network Time Protocol 6-2
Configuring NTP 6-3
Default NTP Configuration 6-4
Configuring NTP Authentication 6-4
Configuring NTP Associations 6-5
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
vi
OL-12189-01
Contents
Configuring NTP Broadcast Service 6-6
Configuring NTP Access Restrictions 6-8
Configuring the Source IP Address for NTP Packets 6-10
Displaying the NTP Configuration 6-11
Configuring Time and Date Manually 6-11
Setting the System Clock 6-11
Displaying the Time and Date Configuration 6-12
Configuring the Time Zone 6-12
Configuring Summer Time (Daylight Saving Time) 6-13
Configuring a System Name and Prompt 6-14
Default System Name and Prompt Configuration
Configuring a System Name 6-15
Understanding DNS 6-15
Default DNS Configuration 6-16
Setting Up DNS 6-16
Displaying the DNS Configuration 6-17
Creating a Banner 6-17
Default Banner Configuration 6-17
Configuring a Message-of-the-Day Login Banner
Configuring a Login Banner 6-18
6-15
6-18
Managing the MAC Address Table 6-19
Building the Address Table 6-20
MAC Addresses and VLANs 6-20
MAC Addresses and Switch Stacks 6-20
Default MAC Address Table Configuration 6-21
Changing the Address Aging Time 6-21
Removing Dynamic Address Entries 6-22
Configuring MAC Address Notification Traps 6-22
Adding and Removing Static Address Entries 6-24
Configuring Unicast MAC Address Filtering 6-25
Displaying Address Table Entries 6-26
Managing the ARP Table
CHAPTER
6-26
Configuring Switch-Based Authentication
7-1
Preventing Unauthorized Access to Your Switch
7-1
Protecting Access to Privileged EXEC Commands 7-2
Default Password and Privilege Level Configuration 7-2
Setting or Changing a Static Enable Password 7-3
Protecting Enable and Enable Secret Passwords with Encryption
7-3
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
vii
Contents
Disabling Password Recovery 7-5
Setting a Telnet Password for a Terminal Line 7-6
Configuring Username and Password Pairs 7-6
Configuring Multiple Privilege Levels 7-7
Setting the Privilege Level for a Command 7-8
Changing the Default Privilege Level for Lines 7-9
Logging into and Exiting a Privilege Level 7-9
Controlling Switch Access with TACACS+ 7-10
Understanding TACACS+ 7-10
TACACS+ Operation 7-12
Configuring TACACS+ 7-12
Default TACACS+ Configuration 7-13
Identifying the TACACS+ Server Host and Setting the Authentication Key 7-13
Configuring TACACS+ Login Authentication 7-14
Configuring TACACS+ Authorization for Privileged EXEC Access and Network Services
Starting TACACS+ Accounting 7-17
Displaying the TACACS+ Configuration 7-17
7-16
Controlling Switch Access with RADIUS 7-17
Understanding RADIUS 7-18
RADIUS Operation 7-19
Configuring RADIUS 7-19
Default RADIUS Configuration 7-20
Identifying the RADIUS Server Host 7-20
Configuring RADIUS Login Authentication 7-23
Defining AAA Server Groups 7-25
Configuring RADIUS Authorization for User Privileged Access and Network Services 7-27
Starting RADIUS Accounting 7-28
Configuring Settings for All RADIUS Servers 7-29
Configuring the Switch to Use Vendor-Specific RADIUS Attributes 7-29
Configuring the Switch for Vendor-Proprietary RADIUS Server Communication 7-31
Displaying the RADIUS Configuration 7-31
Controlling Switch Access with Kerberos 7-32
Understanding Kerberos 7-32
Kerberos Operation 7-34
Authenticating to a Boundary Switch 7-34
Obtaining a TGT from a KDC 7-35
Authenticating to Network Services 7-35
Configuring Kerberos 7-35
Configuring the Switch for Local Authentication and Authorization
7-36
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
viii
OL-12189-01
Contents
Configuring the Switch for Secure Shell 7-37
Understanding SSH 7-37
SSH Servers, Integrated Clients, and Supported Versions
Limitations 7-38
Configuring SSH 7-39
Configuration Guidelines 7-39
Setting Up the Switch to Run SSH 7-39
Configuring the SSH Server 7-40
Displaying the SSH Configuration and Status 7-41
7-38
Configuring the Switch for Secure Socket Layer HTTP 7-41
Understanding Secure HTTP Servers and Clients 7-42
Certificate Authority Trustpoints 7-42
CipherSuites 7-43
Configuring Secure HTTP Servers and Clients 7-44
Default SSL Configuration 7-44
SSL Configuration Guidelines 7-44
Configuring a CA Trustpoint 7-45
Configuring the Secure HTTP Server 7-45
Configuring the Secure HTTP Client 7-47
Displaying Secure HTTP Server and Client Status 7-48
Configuring the Switch for Secure Copy Protocol
Information About Secure Copy 7-48
CHAPTER
Configuring SDM Templates
7-48
8-1
Understanding the SDM Templates 8-1
Dual IPv4 and IPv6 SDM Templates 8-2
SDM Templates and Switch Stacks 8-3
Configuring the Switch SDM Template 8-4
Default SDM Template 8-4
SDM Template Configuration Guidelines
Setting the SDM Template 8-5
Displaying the SDM Templates
CHAPTER
8-4
8-6
Configuring IEEE 802.1x Port-Based Authentication
9-1
Understanding IEEE 802.1x Port-Based Authentication 9-1
Device Roles 9-2
Authentication Process 9-3
Authentication Initiation and Message Exchange 9-5
Ports in Authorized and Unauthorized States 9-7
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
ix
Contents
IEEE 802.1x Authentication and Switch Stacks 9-8
IEEE 802.1x Host Mode 9-8
IEEE 802.1x Accounting 9-9
IEEE 802.1x Accounting Attribute-Value Pairs 9-9
Using IEEE 802.1x Authentication with VLAN Assignment 9-10
Using IEEE 802.1x Authentication with Per-User ACLs 9-12
Using IEEE 802.1x Authentication with Guest VLAN 9-13
Using IEEE 802.1x Authentication with Restricted VLAN 9-14
Using IEEE 802.1x Authentication with Inaccessible Authentication Bypass
Using IEEE 802.1x Authentication with Voice VLAN Ports 9-16
Using IEEE 802.1x Authentication with Port Security 9-17
Using IEEE 802.1x Authentication with Wake-on-LAN 9-18
Using IEEE 802.1x Authentication with MAC Authentication Bypass 9-18
Network Admission Control Layer 2 IEEE 802.1x Validation 9-20
Using Multidomain Authentication 9-20
Using Web Authentication 9-21
Web Authentication with Automatic MAC Check 9-22
9-15
Configuring IEEE 802.1x Authentication 9-22
Default IEEE 802.1x Authentication Configuration 9-23
IEEE 802.1x Authentication Configuration Guidelines 9-24
IEEE 802.1x Authentication 9-24
VLAN Assignment, Guest VLAN, Restricted VLAN, and Inaccessible Authentication
Bypass 9-25
MAC Authentication Bypass 9-26
Configuring IEEE 802.1x Authentication 9-26
Configuring the Switch-to-RADIUS-Server Communication 9-28
Configuring the Host Mode 9-29
Configuring Periodic Re-Authentication 9-30
Manually Re-Authenticating a Client Connected to a Port 9-30
Changing the Quiet Period 9-31
Changing the Switch-to-Client Retransmission Time 9-31
Setting the Switch-to-Client Frame-Retransmission Number 9-32
Setting the Re-Authentication Number 9-32
Configuring IEEE 802.1x Accounting 9-33
Configuring a Guest VLAN 9-34
Configuring a Restricted VLAN 9-35
Configuring the Inaccessible Authentication Bypass Feature 9-37
Configuring IEEE 802.1x Authentication with WoL 9-39
Configuring MAC Authentication Bypass 9-40
Configuring NAC Layer 2 IEEE 802.1x Validation 9-41
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
Contents
Configuring Web Authentication 9-42
Disabling IEEE 802.1x Authentication on the Port 9-44
Resetting the IEEE 802.1x Authentication Configuration to the Default Values
Displaying IEEE 802.1x Statistics and Status
CHAPTER
10
Configuring Interface Characteristics
9-45
9-45
10-1
Understanding Interface Types 10-1
Port-Based VLANs 10-2
Switch Ports 10-2
Access Ports 10-3
Trunk Ports 10-3
Tunnel Ports 10-4
Routed Ports 10-4
Switch Virtual Interfaces 10-5
EtherChannel Port Groups 10-5
10-Gigabit Ethernet Interfaces 10-6
Connecting Interfaces 10-6
Using Interface Configuration Mode 10-7
Procedures for Configuring Interfaces 10-8
Configuring a Range of Interfaces 10-9
Configuring and Using Interface Range Macros
10-10
Using the Internal Ethernet Management Port 10-12
Understanding the Internal Ethernet Management Port
Supported Features on the Ethernet Management Port
Layer 3 Routing Configuration Guidelines 10-14
Monitoring the Ethernet Management Port 10-14
Configuring Ethernet Interfaces 10-14
Default Ethernet Interface Configuration 10-15
Configuring Interface Speed and Duplex Mode 10-16
Speed and Duplex Configuration Guidelines 10-16
Setting the Interface Speed and Duplex Parameters
Configuring IEEE 802.3x Flow Control 10-18
Configuring Auto-MDIX on an Interface 10-19
Adding a Description for an Interface 10-20
Configuring Layer 3 Interfaces
Configuring the System MTU
10-12
10-13
10-17
10-20
10-22
Monitoring and Maintaining the Interfaces 10-24
Monitoring Interface Status 10-24
Clearing and Resetting Interfaces and Counters
10-25
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
xi
Contents
Shutting Down and Restarting the Interface
CHAPTER
11
Configuring Smartports Macros
10-25
11-1
Understanding Smartports Macros
11-1
Configuring Smartports Macros 11-2
Default Smartports Macro Configuration 11-2
Smartports Macro Configuration Guidelines 11-3
Creating Smartports Macros 11-4
Applying Smartports Macros 11-5
Applying Cisco-Default Smartports Macros 11-6
Displaying Smartports Macros
CHAPTER
12
Configuring VLANs
11-8
12-1
Understanding VLANs 12-1
Supported VLANs 12-2
VLAN Port Membership Modes
12-3
Configuring Normal-Range VLANs 12-4
Token Ring VLANs 12-6
Normal-Range VLAN Configuration Guidelines 12-6
VLAN Configuration Mode Options 12-7
VLAN Configuration in config-vlan Mode 12-7
VLAN Configuration in VLAN Database Configuration Mode
Saving VLAN Configuration 12-7
Default Ethernet VLAN Configuration 12-8
Creating or Modifying an Ethernet VLAN 12-9
Deleting a VLAN 12-10
Assigning Static-Access Ports to a VLAN 12-11
Configuring Extended-Range VLANs 12-12
Default VLAN Configuration 12-12
Extended-Range VLAN Configuration Guidelines 12-13
Creating an Extended-Range VLAN 12-14
Creating an Extended-Range VLAN with an Internal VLAN ID
Displaying VLANs
12-7
12-15
12-16
Configuring VLAN Trunks 12-16
Trunking Overview 12-16
Encapsulation Types 12-19
IEEE 802.1Q Configuration Considerations 12-19
Default Layer 2 Ethernet Interface VLAN Configuration 12-20
Configuring an Ethernet Interface as a Trunk Port 12-20
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
xii
OL-12189-01
Contents
Interaction with Other Features 12-20
Configuring a Trunk Port 12-21
Defining the Allowed VLANs on a Trunk 12-22
Changing the Pruning-Eligible List 12-23
Configuring the Native VLAN for Untagged Traffic
Configuring Trunk Ports for Load Sharing 12-24
Load Sharing Using STP Port Priorities 12-25
Load Sharing Using STP Path Cost 12-27
12-24
Configuring VMPS 12-28
Understanding VMPS 12-28
Dynamic-Access Port VLAN Membership 12-29
Default VMPS Client Configuration 12-30
VMPS Configuration Guidelines 12-30
Configuring the VMPS Client 12-30
Entering the IP Address of the VMPS 12-31
Configuring Dynamic-Access Ports on VMPS Clients 12-31
Reconfirming VLAN Memberships 12-32
Changing the Reconfirmation Interval 12-32
Changing the Retry Count 12-32
Monitoring the VMPS 12-33
Troubleshooting Dynamic-Access Port VLAN Membership 12-33
VMPS Configuration Example 12-34
CHAPTER
13
Configuring VTP
13-1
Understanding VTP 13-1
The VTP Domain 13-2
VTP Modes 13-3
VTP Advertisements 13-3
VTP Version 2 13-4
VTP Pruning 13-4
VTP and Switch Stacks 13-6
Configuring VTP 13-6
Default VTP Configuration 13-7
VTP Configuration Options 13-7
VTP Configuration in Global Configuration Mode 13-7
VTP Configuration in VLAN Database Configuration Mode
VTP Configuration Guidelines 13-8
Domain Names 13-8
Passwords 13-8
13-8
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
xiii
Contents
VTP Version 13-9
Configuration Requirements 13-9
Configuring a VTP Server 13-9
Configuring a VTP Client 13-11
Disabling VTP (VTP Transparent Mode) 13-12
Enabling VTP Version 2 13-13
Enabling VTP Pruning 13-14
Adding a VTP Client Switch to a VTP Domain 13-14
Monitoring VTP
CHAPTER
14
13-16
Configuring Voice VLAN
14-1
Understanding Voice VLAN 14-1
Cisco IP Phone Voice Traffic 14-2
Cisco IP Phone Data Traffic 14-2
Configuring Voice VLAN 14-3
Default Voice VLAN Configuration 14-3
Voice VLAN Configuration Guidelines 14-3
Configuring a Port Connected to a Cisco 7960 IP Phone 14-4
Configuring Cisco IP Phone Voice Traffic 14-5
Configuring the Priority of Incoming Data Frames 14-6
Displaying Voice VLAN
CHAPTER
15
Configuring Private VLANs
14-7
15-1
Understanding Private VLANs 15-1
IP Addressing Scheme with Private VLANs 15-3
Private VLANs across Multiple Switches 15-4
Private-VLAN Interaction with Other Features 15-4
Private VLANs and Unicast, Broadcast, and Multicast Traffic
Private VLANs and SVIs 15-5
Private VLANs and Switch Stacks 15-5
15-5
Configuring Private VLANs 15-6
Tasks for Configuring Private VLANs 15-6
Default Private-VLAN Configuration 15-6
Private-VLAN Configuration Guidelines 15-7
Secondary and Primary VLAN Configuration 15-7
Private-VLAN Port Configuration 15-8
Limitations with Other Features 15-9
Configuring and Associating VLANs in a Private VLAN 15-10
Configuring a Layer 2 Interface as a Private-VLAN Host Port 15-11
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
xiv
OL-12189-01
Contents
Configuring a Layer 2 Interface as a Private-VLAN Promiscuous Port 15-13
Mapping Secondary VLANs to a Primary VLAN Layer 3 VLAN Interface 15-14
Monitoring Private VLANs
CHAPTER
16
15-15
Configuring IEEE 802.1Q and Layer 2 Protocol Tunneling
Understanding IEEE 802.1Q Tunneling
16-1
16-1
Configuring IEEE 802.1Q Tunneling 16-4
Default IEEE 802.1Q Tunneling Configuration 16-4
IEEE 802.1Q Tunneling Configuration Guidelines 16-4
Native VLANs 16-4
System MTU 16-5
IEEE 802.1Q Tunneling and Other Features 16-6
Configuring an IEEE 802.1Q Tunneling Port 16-6
Understanding Layer 2 Protocol Tunneling
16-7
Configuring Layer 2 Protocol Tunneling 16-10
Default Layer 2 Protocol Tunneling Configuration 16-11
Layer 2 Protocol Tunneling Configuration Guidelines 16-12
Configuring Layer 2 Protocol Tunneling 16-13
Configuring Layer 2 Tunneling for EtherChannels 16-14
Configuring the SP Edge Switch 16-14
Configuring the Customer Switch 16-16
Monitoring and Maintaining Tunneling Status
CHAPTER
17
Configuring STP
16-18
17-1
Understanding Spanning-Tree Features 17-1
STP Overview 17-2
Spanning-Tree Topology and BPDUs 17-3
Bridge ID, Switch Priority, and Extended System ID 17-4
Spanning-Tree Interface States 17-5
Blocking State 17-6
Listening State 17-7
Learning State 17-7
Forwarding State 17-7
Disabled State 17-7
How a Switch or Port Becomes the Root Switch or Root Port
Spanning Tree and Redundant Connectivity 17-8
Spanning-Tree Address Management 17-9
Accelerated Aging to Retain Connectivity 17-9
Spanning-Tree Modes and Protocols 17-10
17-8
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
xv
Contents
Supported Spanning-Tree Instances 17-10
Spanning-Tree Interoperability and Backward Compatibility
STP and IEEE 802.1Q Trunks 17-11
VLAN-Bridge Spanning Tree 17-11
Spanning Tree and Switch Stacks 17-12
17-11
Configuring Spanning-Tree Features 17-12
Default Spanning-Tree Configuration 17-13
Spanning-Tree Configuration Guidelines 17-13
Changing the Spanning-Tree Mode. 17-15
Disabling Spanning Tree 17-16
Configuring the Root Switch 17-16
Configuring a Secondary Root Switch 17-18
Configuring Port Priority 17-18
Configuring Path Cost 17-20
Configuring the Switch Priority of a VLAN 17-21
Configuring Spanning-Tree Timers 17-22
Configuring the Hello Time 17-22
Configuring the Forwarding-Delay Time for a VLAN 17-23
Configuring the Maximum-Aging Time for a VLAN 17-23
Configuring the Transmit Hold-Count 17-24
Displaying the Spanning-Tree Status
CHAPTER
18
Configuring MSTP
17-24
18-1
Understanding MSTP 18-2
Multiple Spanning-Tree Regions 18-2
IST, CIST, and CST 18-3
Operations Within an MST Region 18-3
Operations Between MST Regions 18-4
IEEE 802.1s Terminology 18-5
Hop Count 18-5
Boundary Ports 18-6
IEEE 802.1s Implementation 18-6
Port Role Naming Change 18-7
Interoperation Between Legacy and Standard Switches
Detecting Unidirectional Link Failure 18-8
MSTP and Switch Stacks 18-8
Interoperability with IEEE 802.1D STP 18-9
Understanding RSTP 18-9
Port Roles and the Active Topology
18-7
18-9
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
xvi
OL-12189-01
Contents
Rapid Convergence 18-10
Synchronization of Port Roles 18-11
Bridge Protocol Data Unit Format and Processing 18-12
Processing Superior BPDU Information 18-13
Processing Inferior BPDU Information 18-13
Topology Changes 18-13
Configuring MSTP Features 18-14
Default MSTP Configuration 18-15
MSTP Configuration Guidelines 18-15
Specifying the MST Region Configuration and Enabling MSTP
Configuring the Root Switch 18-17
Configuring a Secondary Root Switch 18-19
Configuring Port Priority 18-20
Configuring Path Cost 18-21
Configuring the Switch Priority 18-22
Configuring the Hello Time 18-22
Configuring the Forwarding-Delay Time 18-23
Configuring the Maximum-Aging Time 18-24
Configuring the Maximum-Hop Count 18-24
Specifying the Link Type to Ensure Rapid Transitions 18-24
Designating the Neighbor Type 18-25
Restarting the Protocol Migration Process 18-26
Displaying the MST Configuration and Status
CHAPTER
19
Configuring Optional Spanning-Tree Features
18-16
18-26
19-1
Understanding Optional Spanning-Tree Features 19-1
Understanding Port Fast 19-2
Understanding BPDU Guard 19-2
Understanding BPDU Filtering 19-3
Understanding UplinkFast 19-3
Understanding Cross-Stack UplinkFast 19-5
How CSUF Works 19-6
Events that Cause Fast Convergence 19-7
Understanding BackboneFast 19-7
Understanding EtherChannel Guard 19-10
Understanding Root Guard 19-10
Understanding Loop Guard 19-11
Configuring Optional Spanning-Tree Features 19-11
Default Optional Spanning-Tree Configuration 19-12
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
xvii
Contents
Optional Spanning-Tree Configuration Guidelines 19-12
Enabling Port Fast 19-12
Enabling BPDU Guard 19-13
Enabling BPDU Filtering 19-14
Enabling UplinkFast for Use with Redundant Links 19-15
Enabling Cross-Stack UplinkFast 19-16
Enabling BackboneFast 19-16
Enabling EtherChannel Guard 19-17
Enabling Root Guard 19-18
Enabling Loop Guard 19-18
Displaying the Spanning-Tree Status
CHAPTER
20
19-19
Configuring Flex Links and the MAC Address-Table Move Update Feature
Understanding Flex Links and the MAC Address-Table Move Update
Flex Links 20-1
VLAN Flex Link Load Balancing and Support 20-2
MAC Address-Table Move Update 20-3
20-1
20-1
Configuring Flex Links and MAC Address-Table Move Update 20-4
Configuration Guidelines 20-5
Default Configuration 20-5
Configuring Flex Links 20-6
Configuring VLAN Load Balancing on Flex Links 20-8
Configuring the MAC Address-Table Move Update Feature 20-9
Monitoring Flex Links and the MAC Address-Table Move Update Information
CHAPTER
21
Configuring DHCP Features and IP Source Guard
20-11
21-1
Understanding DHCP Features 21-1
DHCP Server 21-2
DHCP Relay Agent 21-2
DHCP Snooping 21-2
Option-82 Data Insertion 21-3
Cisco IOS DHCP Server Database 21-6
DHCP Snooping Binding Database 21-6
DHCP Snooping and Switch Stacks 21-8
Configuring DHCP Features 21-8
Default DHCP Configuration 21-8
DHCP Snooping Configuration Guidelines
Configuring the DHCP Server 21-10
DHCP Server and Switch Stacks 21-10
21-9
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
xviii
OL-12189-01
Contents
Configuring the DHCP Relay Agent 21-11
Specifying the Packet Forwarding Address 21-11
Enabling DHCP Snooping and Option 82 21-12
Enabling DHCP Snooping on Private VLANs 21-14
Enabling the Cisco IOS DHCP Server Database 21-14
Enabling the DHCP Snooping Binding Database Agent 21-14
Displaying DHCP Snooping Information
21-15
Understanding IP Source Guard 21-16
Source IP Address Filtering 21-16
Source IP and MAC Address Filtering
21-17
Configuring IP Source Guard 21-17
Default IP Source Guard Configuration 21-17
IP Source Guard Configuration Guidelines 21-17
Enabling IP Source Guard 21-18
Displaying IP Source Guard Information
CHAPTER
22
Configuring Dynamic ARP Inspection
21-19
22-1
Understanding Dynamic ARP Inspection 22-1
Interface Trust States and Network Security 22-3
Rate Limiting of ARP Packets 22-4
Relative Priority of ARP ACLs and DHCP Snooping Entries
Logging of Dropped Packets 22-5
Configuring Dynamic ARP Inspection 22-5
Default Dynamic ARP Inspection Configuration 22-5
Dynamic ARP Inspection Configuration Guidelines 22-6
Configuring Dynamic ARP Inspection in DHCP Environments
Configuring ARP ACLs for Non-DHCP Environments 22-8
Limiting the Rate of Incoming ARP Packets 22-10
Performing Validation Checks 22-11
Configuring the Log Buffer 22-12
Displaying Dynamic ARP Inspection Information
CHAPTER
23
Configuring IGMP Snooping and MVR
22-4
22-7
22-14
23-1
Understanding IGMP Snooping 23-2
IGMP Versions 23-3
Joining a Multicast Group 23-3
Leaving a Multicast Group 23-5
Immediate Leave 23-6
IGMP Configurable-Leave Timer 23-6
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
xix
Contents
IGMP Report Suppression 23-6
IGMP Snooping and Switch Stacks
23-7
Configuring IGMP Snooping 23-7
Default IGMP Snooping Configuration 23-7
Enabling or Disabling IGMP Snooping 23-8
Setting the Snooping Method 23-9
Configuring a Multicast Router Port 23-10
Configuring a Blade Server Statically to Join a Group 23-10
Enabling IGMP Immediate Leave 23-11
Configuring the IGMP Leave Timer 23-12
Configuring TCN-Related Commands 23-12
Controlling the Multicast Flooding Time After a TCN Event
Recovering from Flood Mode 23-13
Disabling Multicast Flooding During a TCN Event 23-14
Configuring the IGMP Snooping Querier 23-14
Disabling IGMP Report Suppression 23-16
Displaying IGMP Snooping Information
23-16
Understanding Multicast VLAN Registration 23-18
Using MVR in a Multicast Television Application
Configuring MVR 23-20
Default MVR Configuration 23-20
MVR Configuration Guidelines and Limitations
Configuring MVR Global Parameters 23-21
Configuring MVR Interfaces 23-22
Displaying MVR Information
23-13
23-18
23-20
23-24
Configuring IGMP Filtering and Throttling 23-24
Default IGMP Filtering and Throttling Configuration 23-25
Configuring IGMP Profiles 23-25
Applying IGMP Profiles 23-27
Setting the Maximum Number of IGMP Groups 23-27
Configuring the IGMP Throttling Action 23-28
Displaying IGMP Filtering and Throttling Configuration
CHAPTER
24
Configuring IPv6 MLD Snooping
23-29
24-1
Understanding MLD Snooping 24-1
MLD Messages 24-2
MLD Queries 24-3
Multicast Client Aging Robustness
Multicast Router Discovery 24-4
24-3
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
xx
OL-12189-01
Contents
MLD Reports 24-4
MLD Done Messages and Immediate-Leave 24-4
Topology Change Notification Processing 24-5
MLD Snooping in Switch Stacks 24-5
Configuring IPv6 MLD Snooping 24-5
Default MLD Snooping Configuration 24-6
MLD Snooping Configuration Guidelines 24-6
Enabling or Disabling MLD Snooping 24-7
Configuring a Static Multicast Group 24-8
Configuring a Multicast Router Port 24-9
Enabling MLD Immediate Leave 24-9
Configuring MLD Snooping Queries 24-10
Disabling MLD Listener Message Suppression 24-11
CHAPTER
25
Displaying MLD Snooping Information
24-12
Configuring Port-Based Traffic Control
25-1
Configuring Storm Control 25-1
Understanding Storm Control 25-1
Default Storm Control Configuration 25-3
Configuring Storm Control and Threshold Levels
25-3
Configuring Protected Ports 25-5
Default Protected Port Configuration 25-5
Protected Port Configuration Guidelines 25-6
Configuring a Protected Port 25-6
Configuring Port Blocking 25-6
Default Port Blocking Configuration 25-7
Blocking Flooded Traffic on an Interface 25-7
Configuring Port Security 25-7
Understanding Port Security 25-8
Secure MAC Addresses 25-8
Security Violations 25-9
Default Port Security Configuration 25-10
Port Security Configuration Guidelines 25-10
Enabling and Configuring Port Security 25-12
Enabling and Configuring Port Security Aging 25-16
Port Security and Switch Stacks 25-17
Port Security and Private VLANs 25-17
Displaying Port-Based Traffic Control Settings
25-18
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
xxi
Contents
CHAPTER
26
Configuring CDP
26-1
Understanding CDP 26-1
CDP and Switch Stacks
26-2
Configuring CDP 26-2
Default CDP Configuration 26-2
Configuring the CDP Characteristics 26-2
Disabling and Enabling CDP 26-3
Disabling and Enabling CDP on an Interface
CHAPTER
27
Monitoring and Maintaining CDP
26-5
Configuring LLDP and LLDP-MED
27-1
26-4
Understanding LLDP and LLDP-MED 27-1
Understanding LLDP 27-1
Understanding LLDP-MED 27-2
Configuring LLDP and LLDP-MED 27-3
Default LLDP Configuration 27-3
Configuring LLDP Characteristics 27-4
Disabling and Enabling LLDP Globally 27-4
Disabling and Enabling LLDP on an Interface
Configuring LLDP-MED TLVs 27-6
27-5
Monitoring and Maintaining LLDP and LLDP-MED
CHAPTER
28
Configuring UDLD
28-1
Understanding UDLD 28-1
Modes of Operation 28-1
Methods to Detect Unidirectional Links
Configuring UDLD 28-3
Default UDLD Configuration 28-4
Configuration Guidelines 28-4
Enabling UDLD Globally 28-5
Enabling UDLD on an Interface 28-6
Resetting an Interface Disabled by UDLD
Displaying UDLD Status
CHAPTER
29
27-7
28-2
28-6
28-7
Configuring SPAN and RSPAN
29-1
Understanding SPAN and RSPAN
Local SPAN 29-2
Remote SPAN 29-3
29-1
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
xxii
OL-12189-01
Contents
SPAN and RSPAN Concepts and Terminology 29-4
SPAN Sessions 29-4
Monitored Traffic 29-5
Source Ports 29-6
Source VLANs 29-7
VLAN Filtering 29-7
Destination Port 29-8
RSPAN VLAN 29-9
SPAN and RSPAN Interaction with Other Features 29-9
SPAN and RSPAN and Switch Stacks 29-10
Configuring SPAN and RSPAN 29-10
Default SPAN and RSPAN Configuration 29-11
Configuring Local SPAN 29-11
SPAN Configuration Guidelines 29-11
Creating a Local SPAN Session 29-12
Creating a Local SPAN Session and Configuring Incoming Traffic 29-14
Specifying VLANs to Filter 29-15
Configuring RSPAN 29-16
RSPAN Configuration Guidelines 29-16
Configuring a VLAN as an RSPAN VLAN 29-17
Creating an RSPAN Source Session 29-18
Specifying VLANs to Filter 29-19
Creating an RSPAN Destination Session 29-20
Creating an RSPAN Destination Session and Configuring Incoming Traffic
Displaying SPAN and RSPAN Status
CHAPTER
30
Configuring RMON
29-21
29-23
30-1
Understanding RMON
30-1
Configuring RMON 30-2
Default RMON Configuration 30-3
Configuring RMON Alarms and Events 30-3
Collecting Group History Statistics on an Interface 30-5
Collecting Group Ethernet Statistics on an Interface 30-5
Displaying RMON Status
CHAPTER
31
30-6
Configuring System Message Logging
31-1
Understanding System Message Logging
31-1
Configuring System Message Logging 31-2
System Log Message Format 31-2
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
xxiii
Contents
Default System Message Logging Configuration 31-4
Disabling Message Logging 31-4
Setting the Message Display Destination Device 31-5
Synchronizing Log Messages 31-6
Enabling and Disabling Time Stamps on Log Messages 31-8
Enabling and Disabling Sequence Numbers in Log Messages 31-8
Defining the Message Severity Level 31-9
Limiting Syslog Messages Sent to the History Table and to SNMP 31-10
Enabling the Configuration-Change Logger 31-11
Configuring UNIX Syslog Servers 31-12
Logging Messages to a UNIX Syslog Daemon 31-12
Configuring the UNIX System Logging Facility 31-13
Displaying the Logging Configuration
CHAPTER
32
Configuring SNMP
31-14
32-1
Understanding SNMP 32-1
SNMP Versions 32-2
SNMP Manager Functions 32-3
SNMP Agent Functions 32-4
SNMP Community Strings 32-4
Using SNMP to Access MIB Variables 32-4
SNMP Notifications 32-5
SNMP ifIndex MIB Object Values 32-5
Configuring SNMP 32-6
Default SNMP Configuration 32-6
SNMP Configuration Guidelines 32-6
Disabling the SNMP Agent 32-7
Configuring Community Strings 32-8
Configuring SNMP Groups and Users 32-9
Configuring SNMP Notifications 32-11
Setting the Agent Contact and Location Information
Limiting TFTP Servers Used Through SNMP 32-15
SNMP Examples 32-16
Displaying SNMP Status
CHAPTER
34
32-15
32-17
Configuring Network Security with ACLs
34-1
Understanding ACLs 34-1
Supported ACLs 34-2
Port ACLs 34-3
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
xxiv
OL-12189-01
Contents
Router ACLs 34-4
VLAN Maps 34-5
Handling Fragmented and Unfragmented Traffic
ACLs and Switch Stacks 34-6
34-5
Configuring IPv4 ACLs 34-7
Creating Standard and Extended IPv4 ACLs 34-7
Access List Numbers 34-8
ACL Logging 34-9
Creating a Numbered Standard ACL 34-10
Creating a Numbered Extended ACL 34-11
Resequencing ACEs in an ACL 34-15
Creating Named Standard and Extended ACLs 34-15
Using Time Ranges with ACLs 34-17
Including Comments in ACLs 34-19
Applying an IPv4 ACL to a Terminal Line 34-19
Applying an IPv4 ACL to an Interface 34-20
Hardware and Software Treatment of IP ACLs 34-22
IPv4 ACL Configuration Examples 34-22
Numbered ACLs 34-24
Extended ACLs 34-24
Named ACLs 34-25
Time Range Applied to an IP ACL 34-25
Commented IP ACL Entries 34-25
ACL Logging 34-26
Creating Named MAC Extended ACLs 34-27
Applying a MAC ACL to a Layer 2 Interface
34-28
Configuring VLAN Maps 34-29
VLAN Map Configuration Guidelines 34-30
Creating a VLAN Map 34-31
Examples of ACLs and VLAN Maps 34-32
Applying a VLAN Map to a VLAN 34-34
Using VLAN Maps in Your Network 34-34
Denying Access to a Server on Another VLAN
34-34
Using VLAN Maps with Router ACLs 34-35
VLAN Maps and Router ACL Configuration Guidelines 34-35
Examples of Router ACLs and VLAN Maps Applied to VLANs 34-36
ACLs and Switched Packets 34-36
ACLs and Bridged Packets 34-37
ACLs and Routed Packets 34-38
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
xxv
Contents
ACLs and Multicast Packets
Displaying IPv4 ACL Configuration
CHAPTER
35
Configuring IPv6 ACLs
35-1
Supported IPv6 ACLs
35-2
34-38
34-39
Understanding IPv6 ACLs 35-2
Supported ACL Features 35-2
IPv6 ACL Limitations 35-3
IPv6 ACLs and Switch Stacks 35-4
Configuring IPv6 ACLs 35-4
Default IPv6 ACL Configuration 35-5
Interaction with Other Features and Switches
Creating IPv6 ACLs 35-5
Applying an IPv6 ACL to an Interface 35-8
Displaying IPv6 ACLs
CHAPTER
36
Configuring QoS
35-5
35-9
36-1
Understanding QoS 36-2
Basic QoS Model 36-3
Classification 36-5
Classification Based on QoS ACLs 36-7
Classification Based on Class Maps and Policy Maps
Policing and Marking 36-8
Policing on Physical Ports 36-9
Policing on SVIs 36-10
Mapping Tables 36-12
Queueing and Scheduling Overview 36-13
Weighted Tail Drop 36-13
SRR Shaping and Sharing 36-14
Queueing and Scheduling on Ingress Queues 36-15
Queueing and Scheduling on Egress Queues 36-17
Packet Modification 36-19
36-7
Configuring Auto-QoS 36-20
Generated Auto-QoS Configuration 36-21
Effects of Auto-QoS on the Configuration 36-25
Auto-QoS Configuration Guidelines 36-25
Enabling Auto-QoS for VoIP 36-26
Auto-QoS Configuration Example 36-27
Displaying Auto-QoS Information
36-29
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
xxvi
OL-12189-01
Contents
Configuring Standard QoS 36-29
Default Standard QoS Configuration 36-30
Default Ingress Queue Configuration 36-30
Default Egress Queue Configuration 36-31
Default Mapping Table Configuration 36-32
Standard QoS Configuration Guidelines 36-32
QoS ACL Guidelines 36-32
Applying QoS on Interfaces 36-32
Policing Guidelines 36-33
General QoS Guidelines 36-33
Enabling QoS Globally 36-34
Enabling VLAN-Based QoS on Physical Ports 36-34
Configuring Classification Using Port Trust States 36-35
Configuring the Trust State on Ports within the QoS Domain 36-35
Configuring the CoS Value for an Interface 36-37
Configuring a Trusted Boundary to Ensure Port Security 36-38
Enabling DSCP Transparency Mode 36-39
Configuring the DSCP Trust State on a Port Bordering Another QoS Domain 36-40
Configuring a QoS Policy 36-42
Classifying Traffic by Using ACLs 36-43
Classifying Traffic by Using Class Maps 36-46
Classifying, Policing, and Marking Traffic on Physical Ports by Using Policy Maps 36-48
Classifying, Policing, and Marking Traffic on SVIs by Using Hierarchical Policy Maps 36-52
Classifying, Policing, and Marking Traffic by Using Aggregate Policers 36-58
Configuring DSCP Maps 36-60
Configuring the CoS-to-DSCP Map 36-60
Configuring the IP-Precedence-to-DSCP Map 36-61
Configuring the Policed-DSCP Map 36-62
Configuring the DSCP-to-CoS Map 36-63
Configuring the DSCP-to-DSCP-Mutation Map 36-64
Configuring Ingress Queue Characteristics 36-66
Mapping DSCP or CoS Values to an Ingress Queue and Setting WTD Thresholds 36-67
Allocating Buffer Space Between the Ingress Queues 36-68
Allocating Bandwidth Between the Ingress Queues 36-68
Configuring the Ingress Priority Queue 36-69
Configuring Egress Queue Characteristics 36-70
Configuration Guidelines 36-71
Allocating Buffer Space to and Setting WTD Thresholds for an Egress Queue-Set 36-71
Mapping DSCP or CoS Values to an Egress Queue and to a Threshold ID 36-73
Configuring SRR Shaped Weights on Egress Queues 36-75
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
xxvii
Contents
Configuring SRR Shared Weights on Egress Queues 36-76
Configuring the Egress Expedite Queue 36-76
Limiting the Bandwidth on an Egress Interface 36-77
Displaying Standard QoS Information
CHAPTER
37
36-78
Configuring EtherChannels and Link-State Tracking
37-1
Understanding EtherChannels 37-1
EtherChannel Overview 37-2
Port-Channel Interfaces 37-4
Port Aggregation Protocol 37-5
PAgP Modes 37-5
PAgP Interaction with Other Features 37-6
Link Aggregation Control Protocol 37-6
LACP Modes 37-6
LACP Interaction with Other Features 37-7
EtherChannel On Mode 37-7
Load-Balancing and Forwarding Methods 37-7
EtherChannel and Switch Stacks 37-9
Configuring EtherChannels 37-10
Default EtherChannel Configuration 37-10
EtherChannel Configuration Guidelines 37-11
Configuring Layer 2 EtherChannels 37-12
Configuring Layer 3 EtherChannels 37-14
Creating Port-Channel Logical Interfaces 37-14
Configuring the Physical Interfaces 37-15
Configuring EtherChannel Load-Balancing 37-17
Configuring the PAgP Learn Method and Priority 37-18
Configuring LACP Hot-Standby Ports 37-19
Configuring the LACP System Priority 37-20
Configuring the LACP Port Priority 37-21
Displaying EtherChannel, PAgP, and LACP Status
Understanding Link-State Tracking
37-22
37-22
Configuring Link-State Tracking 37-24
Default Link-State Tracking Configuration 37-24
Link-State Tracking Configuration Guidelines 37-24
Configuring Link-State Tracking 37-25
Displaying Link-State Tracking Status 37-26
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
xxviii
OL-12189-01
Contents
CHAPTER
38
Configuring IP Unicast Routing
Supported IPv4 Features
38-1
38-2
Understanding IP Routing 38-3
Types of Routing 38-3
IP Routing and Switch Stacks
Steps for Configuring Routing
38-4
38-6
Configuring IP Addressing 38-6
Default Addressing Configuration 38-7
Assigning IP Addresses to Network Interfaces 38-8
Use of Subnet Zero 38-8
Classless Routing 38-9
Configuring Address Resolution Methods 38-10
Define a Static ARP Cache 38-11
Set ARP Encapsulation 38-12
Enable Proxy ARP 38-13
Routing Assistance When IP Routing is Disabled 38-13
Proxy ARP 38-13
Default Gateway 38-13
ICMP Router Discovery Protocol (IRDP) 38-14
Configuring Broadcast Packet Handling 38-15
Enabling Directed Broadcast-to-Physical Broadcast Translation
Forwarding UDP Broadcast Packets and Protocols 38-17
Establishing an IP Broadcast Address 38-17
Flooding IP Broadcasts 38-18
Monitoring and Maintaining IP Addressing 38-19
Enabling IP Unicast Routing
38-16
38-20
Configuring RIP 38-21
Default RIP Configuration 38-22
Configuring Basic RIP Parameters 38-22
Configuring RIP Authentication 38-24
Configuring Summary Addresses and Split Horizon
Configuring Split Horizon 38-26
Configuring Stub Routing 38-26
Understanding PIM Stub Routing 38-26
Configuring PIM Stub Routing 38-27
PIM Stub Routing Configuration Guidelines
Enabling PIM Stub Routing 38-28
Understanding EIGRP Stub Routing 38-29
Configuring EIGRP Stub Routing 38-30
38-24
38-28
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
xxix
Contents
Configuring OSPF 38-31
Default OSPF Configuration 38-32
OSPF Nonstop Forwarding 38-33
Configuring Basic OSPF Parameters 38-35
Configuring OSPF Interfaces 38-35
Configuring OSPF Area Parameters 38-36
Configuring Other OSPF Parameters 38-38
Changing LSA Group Pacing 38-39
Configuring a Loopback Interface 38-40
Monitoring OSPF 38-40
Configuring EIGRP 38-41
Default EIGRP Configuration 38-43
EIGRP Nonstop Forwarding 38-44
Configuring Basic EIGRP Parameters 38-45
Configuring EIGRP Interfaces 38-46
Configuring EIGRP Route Authentication 38-47
Monitoring and Maintaining EIGRP 38-48
Configuring BGP 38-49
Default BGP Configuration 38-51
Nonstop Forwarding Awareness 38-53
Enabling BGP Routing 38-53
Managing Routing Policy Changes 38-56
Configuring BGP Decision Attributes 38-57
Configuring BGP Filtering with Route Maps 38-59
Configuring BGP Filtering by Neighbor 38-60
Configuring Prefix Lists for BGP Filtering 38-61
Configuring BGP Community Filtering 38-62
Configuring BGP Neighbors and Peer Groups 38-64
Configuring Aggregate Addresses 38-66
Configuring Routing Domain Confederations 38-66
Configuring BGP Route Reflectors 38-67
Configuring Route Dampening 38-68
Monitoring and Maintaining BGP 38-69
Configuring Multi-VRF CE 38-70
Understanding Multi-VRF CE 38-71
Default Multi-VRF CE Configuration 38-73
Multi-VRF CE Configuration Guidelines 38-73
Configuring VRFs 38-74
Configuring VRF-Aware Services 38-75
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
xxx
OL-12189-01
Contents
User Interface for ARP 38-75
User Interface for PING 38-75
User Interface for SNMP 38-76
User Interface for HSRP 38-76
User Interface for uRPF 38-76
User Interface for Syslog 38-77
User Interface for Traceroute 38-77
User Interface for FTP and TFTP 38-78
Configuring Multicast VRFs 38-78
Configuring a VPN Routing Session 38-79
Configuring BGP PE to CE Routing Sessions 38-80
Multi-VRF CE Configuration Example 38-80
Displaying Multi-VRF CE Status 38-84
Configuring Unicast Reverse Path Forwarding
38-85
Configuring Protocol-Independent Features 38-85
Configuring Cisco Express Forwarding and Distributed Cisco Express Forwarding
Configuring the Number of Equal-Cost Routing Paths 38-87
Configuring Static Unicast Routes 38-88
Specifying Default Routes and Networks 38-89
Using Route Maps to Redistribute Routing Information 38-89
Configuring Policy-Based Routing 38-93
PBR Configuration Guidelines 38-94
Enabling PBR 38-95
Filtering Routing Information 38-97
Setting Passive Interfaces 38-97
Controlling Advertising and Processing in Routing Updates 38-98
Filtering Sources of Routing Information 38-99
Managing Authentication Keys 38-99
Monitoring and Maintaining the IP Network
CHAPTER
39
38-85
38-101
Configuring IPv6 Host Functions and Unicast Routing
39-1
Supported IPv6 Host Functions and Unicast Routing Features
39-2
Understanding IPv6 39-2
IPv6 Addresses 39-3
Supported IPv6 Host Functions and Unicast Routing Features
128-Bit Wide Unicast Addresses 39-4
DNS for IPv6 39-5
Path MTU Discovery for IPv6 Unicast 39-5
ICMPv6 39-5
39-4
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
xxxi
Contents
Neighbor Discovery 39-5
IPv6 Stateless Autoconfiguration and Duplicate Address Detection
IPv6 Applications 39-7
Dual IPv4 and IPv6 Protocol Stacks 39-7
EIGRP IPv6 39-8
Unsupported IPv6 Host Functions and Unicast Routing Features 39-11
Limitations 39-12
IPv6 and Switch Stacks 39-12
SDM Templates 39-13
Dual IPv4-and IPv6 SDM Templates 39-14
39-6
Configuring IPv6 39-15
Default IPv6 Configuration 39-15
Configuring IPv6 Addressing and Enabling IPv6 Host Functions or Routing 39-16
Configuring IPv4 and IPv6 Protocol Stacks and Enabling IPv6 Routing 39-18
Configuring IPv6 ICMP Rate Limiting 39-19
Configuring CEF and dCEF for IPv6 39-20
Configuring Static Routes for IPv6 39-21
Configuring RIP for IPv6 39-23
Configuring OSPF for IPv6 39-25
Displaying IPv6
CHAPTER
40
Configuring HSRP
39-27
40-1
Understanding HSRP 40-1
Multiple HSRP 40-3
HSRP and Switch Stacks
40-4
Configuring HSRP 40-4
Default HSRP Configuration 40-5
HSRP Configuration Guidelines 40-5
Enabling HSRP 40-5
Configuring HSRP Priority 40-7
Configuring MHSRP 40-9
Configuring HSRP Authentication and Timers 40-10
Enabling HSRP Support for ICMP Redirect Messages
Displaying HSRP Configurations
CHAPTER
41
40-11
40-11
Configuring Cisco IOS IP SLAs Operations
41-1
Understanding Cisco IOS IP SLAs 41-1
Using Cisco IOS IP SLAs to Measure Network Performance
IP SLAs Responder and IP SLAs Control Protocol 41-4
41-3
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
xxxii
OL-12189-01
Contents
Response Time Computation for IP SLAs
IP SLAs Operation Scheduling 41-5
IP SLAs Operation Threshold Monitoring
41-4
41-5
Configuring IP SLAs Operations 41-6
Default Configuration 41-6
Configuration Guidelines 41-6
Configuring the IP SLAs Responder 41-8
Analyzing IP Service Levels by Using the UDP Jitter Operation 41-8
Analyzing IP Service Levels by Using the ICMP Echo Operation 41-11
Monitoring IP SLAs Operations
CHAPTER
42
41-14
Configuring Enhanced Object Tracking
42-1
Understanding Enhanced Object Tracking
42-1
Configuring Enhanced Object Tracking Features 42-2
Default Configuration 42-2
Tracking Interface Line-Protocol or IP Routing State 42-2
Configuring a Tracked List 42-3
Configuring a Tracked List with a Boolean Expression 42-3
Configuring a Tracked List with a Weight Threshold 42-4
Configuring a Tracked List with a Percentage Threshold 42-5
Configuring HSRP Object Tracking 42-7
Configuring Other Tracking Characteristics 42-8
Configuring IP SLAs Object Tracking 42-9
Monitoring Enhanced Object Tracking
CHAPTER
43
42-10
Configuring Web Cache Services By Using WCCP
Understanding WCCP 43-1
WCCP Message Exchange 43-2
WCCP Negotiation 43-3
MD5 Security 43-3
Packet Redirection and Service Groups
WCCP and Switch Stacks 43-4
Unsupported WCCP Features 43-5
43-1
43-3
Configuring WCCP 43-5
Default WCCP Configuration 43-5
WCCP Configuration Guidelines 43-5
Enabling the Web Cache Service 43-6
Monitoring and Maintaining WCCP
43-10
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
xxxiii
Contents
CHAPTER
44
Configuring IP Multicast Routing
44-1
Understanding Ciscos Implementation of IP Multicast Routing
Understanding IGMP 44-3
IGMP Version 1 44-3
IGMP Version 2 44-3
Understanding PIM 44-4
PIM Versions 44-4
PIM Modes 44-4
PIM Stub Routing 44-5
IGMP Helper 44-6
Auto-RP 44-7
Bootstrap Router 44-7
Multicast Forwarding and Reverse Path Check 44-8
Understanding DVMRP 44-9
Understanding CGMP 44-9
Multicast Routing and Switch Stacks
44-2
44-10
Configuring IP Multicast Routing 44-10
Default Multicast Routing Configuration 44-11
Multicast Routing Configuration Guidelines 44-11
PIMv1 and PIMv2 Interoperability 44-11
Auto-RP and BSR Configuration Guidelines 44-12
Configuring Basic Multicast Routing 44-12
Enabling PIM Stub Routing 44-14
Configuring a Rendezvous Point 44-15
Manually Assigning an RP to Multicast Groups 44-16
Configuring Auto-RP 44-17
Configuring PIMv2 BSR 44-21
Using Auto-RP and a BSR 44-25
Monitoring the RP Mapping Information 44-26
Troubleshooting PIMv1 and PIMv2 Interoperability Problems
44-26
Configuring Advanced PIM Features 44-26
Understanding PIM Shared Tree and Source Tree 44-26
Delaying the Use of PIM Shortest-Path Tree 44-28
Modifying the PIM Router-Query Message Interval 44-29
Configuring Optional IGMP Features 44-29
Default IGMP Configuration 44-30
Configuring the Switch as a Member of a Group 44-30
Controlling Access to IP Multicast Groups 44-31
Changing the IGMP Version 44-32
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
xxxiv
OL-12189-01
Contents
Modifying the IGMP Host-Query Message Interval 44-32
Changing the IGMP Query Timeout for IGMPv2 44-33
Changing the Maximum Query Response Time for IGMPv2
Configuring the Switch as a Statically Connected Member
44-34
44-34
Configuring Optional Multicast Routing Features 44-35
Enabling CGMP Server Support 44-35
Configuring sdr Listener Support 44-36
Enabling sdr Listener Support 44-37
Limiting How Long an sdr Cache Entry Exists 44-37
Configuring an IP Multicast Boundary 44-37
Configuring Basic DVMRP Interoperability Features 44-39
Configuring DVMRP Interoperability 44-40
Configuring a DVMRP Tunnel 44-42
Advertising Network 0.0.0.0 to DVMRP Neighbors 44-43
Responding to mrinfo Requests 44-44
Configuring Advanced DVMRP Interoperability Features 44-44
Enabling DVMRP Unicast Routing 44-45
Rejecting a DVMRP Nonpruning Neighbor 44-46
Controlling Route Exchanges 44-47
Limiting the Number of DVMRP Routes Advertised 44-48
Changing the DVMRP Route Threshold 44-48
Configuring a DVMRP Summary Address 44-49
Disabling DVMRP Autosummarization 44-51
Adding a Metric Offset to the DVMRP Route 44-51
Monitoring and Maintaining IP Multicast Routing 44-52
Clearing Caches, Tables, and Databases 44-52
Displaying System and Network Statistics 44-53
Monitoring IP Multicast Routing 44-54
CHAPTER
45
Configuring MSDP
45-1
Understanding MSDP 45-1
MSDP Operation 45-2
MSDP Benefits 45-3
Configuring MSDP 45-3
Default MSDP Configuration 45-4
Configuring a Default MSDP Peer 45-4
Caching Source-Active State 45-6
Requesting Source Information from an MSDP Peer 45-8
Controlling Source Information that Your Switch Originates
45-8
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
xxxv
Contents
Redistributing Sources 45-9
Filtering Source-Active Request Messages 45-10
Controlling Source Information that Your Switch Forwards 45-11
Using a Filter 45-12
Using TTL to Limit the Multicast Data Sent in SA Messages 45-13
Controlling Source Information that Your Switch Receives 45-13
Configuring an MSDP Mesh Group 45-15
Shutting Down an MSDP Peer 45-15
Including a Bordering PIM Dense-Mode Region in MSDP 45-16
Configuring an Originating Address other than the RP Address 45-17
Monitoring and Maintaining MSDP
CHAPTER
46
Configuring Fallback Bridging
45-18
46-1
Understanding Fallback Bridging 46-1
Fallback Bridging Overview 46-1
Fallback Bridging and Switch Stacks
46-3
Configuring Fallback Bridging 46-3
Default Fallback Bridging Configuration 46-4
Fallback Bridging Configuration Guidelines 46-4
Creating a Bridge Group 46-4
Adjusting Spanning-Tree Parameters 46-6
Changing the VLAN-Bridge Spanning-Tree Priority 46-6
Changing the Interface Priority 46-7
Assigning a Path Cost 46-7
Adjusting BPDU Intervals 46-8
Disabling the Spanning Tree on an Interface 46-10
Monitoring and Maintaining Fallback Bridging
CHAPTER
47
Troubleshooting
46-11
47-1
Recovering from a Software Failure
47-2
Recovering from a Lost or Forgotten Password 47-3
Procedure with Password Recovery Enabled 47-5
Procedure with Password Recovery Disabled 47-6
Preventing Switch Stack Problems
47-8
Preventing Autonegotiation Mismatches
Monitoring Temperature
47-9
Using Ping 47-10
Understanding Ping
47-10
47-9
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
xxxvi
OL-12189-01
Contents
Executing Ping
47-10
Using Layer 2 Traceroute 47-11
Understanding Layer 2 Traceroute 47-11
Usage Guidelines 47-12
Displaying the Physical Path 47-13
Using IP Traceroute 47-13
Understanding IP Traceroute 47-13
Executing IP Traceroute 47-14
Using TDR 47-15
Understanding TDR 47-15
Running TDR and Displaying the Results
47-15
Using Debug Commands 47-16
Enabling Debugging on a Specific Feature 47-16
Enabling All-System Diagnostics 47-17
Redirecting Debug and Error Message Output 47-17
Using the show platform forward Command
47-17
Using the crashinfo Files 47-20
Basic crashinfo Files 47-20
Extended crashinfo Files 47-20
Using On-Board Failure Logging 47-21
Understanding OBFL 47-21
Configuring OBFL 47-21
Displaying OBFL Information 47-22
CHAPTER
48
Configuring Online Diagnostics
48-1
Understanding Online Diagnostics
48-1
Configuring Online Diagnostics 48-2
Scheduling Online Diagnostics 48-2
Configuring Health-Monitoring Diagnostics
48-3
Running Online Diagnostic Tests 48-5
Starting Online Diagnostic Tests 48-5
Displaying Online Diagnostic Tests and Test Results
APPENDIX
Supported MIBs
MIB List
48-6
A-1
A-1
Using FTP to Access the MIB Files
A-4
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
xxxvii
Contents
APPENDIX
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with the Flash File System B-1
Displaying Available File Systems B-2
Setting the Default File System B-3
Displaying Information about Files on a File System B-3
Changing Directories and Displaying the Working Directory
Creating and Removing Directories B-5
Copying Files B-5
Deleting Files B-6
Creating, Displaying, and Extracting Files B-6
B-1
B-4
Working with Configuration Files B-9
Guidelines for Creating and Using Configuration Files B-10
Configuration File Types and Location B-10
Creating a Configuration File By Using a Text Editor B-11
Copying Configuration Files By Using TFTP B-11
Preparing to Download or Upload a Configuration File By Using TFTP B-11
Downloading the Configuration File By Using TFTP B-12
Uploading the Configuration File By Using TFTP B-12
Copying Configuration Files By Using FTP B-13
Preparing to Download or Upload a Configuration File By Using FTP B-14
Downloading a Configuration File By Using FTP B-14
Uploading a Configuration File By Using FTP B-15
Copying Configuration Files By Using RCP B-16
Preparing to Download or Upload a Configuration File By Using RCP B-17
Downloading a Configuration File By Using RCP B-18
Uploading a Configuration File By Using RCP B-19
Clearing Configuration Information B-19
Clearing the Startup Configuration File B-20
Deleting a Stored Configuration File B-20
Replacing and Rolling Back Configurations B-20
Understanding Configuration Replacement and Rollback B-20
Configuration Guidelines B-21
Configuring the Configuration Archive B-22
Performing a Configuration Replacement or Rollback Operation B-23
Working with Software Images B-23
Image Location on the Switch B-25
File Format of Images on a Server or Cisco.com B-25
Copying Image Files By Using TFTP B-26
Preparing to Download or Upload an Image File By Using TFTP
B-26
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
xxxviii
OL-12189-01
Contents
Downloading an Image File By Using TFTP B-27
Uploading an Image File By Using TFTP B-29
Copying Image Files By Using FTP B-29
Preparing to Download or Upload an Image File By Using FTP B-30
Downloading an Image File By Using FTP B-31
Uploading an Image File By Using FTP B-33
Copying Image Files By Using RCP B-34
Preparing to Download or Upload an Image File By Using RCP B-35
Downloading an Image File By Using RCP B-36
Uploading an Image File By Using RCP B-38
Copying an Image File from One Stack Member to Another B-39
APPENDIX
Unsupported Commands in Cisco IOS Release 12.2(40)EX2
C-1
Access Control Lists C-1
Unsupported Privileged EXEC Commands C-1
Unsupported Global Configuration Commands C-1
Unsupported Route-Map Configuration Commands C-1
Archive Commands C-2
Unsupported Privileged EXEC Commands
C-2
ARP Commands C-2
Unsupported Global Configuration Commands C-2
Unsupported Interface Configuration Commands C-2
Boot Loader Commands C-2
Unsupported User EXEC Commands C-2
Unsupported Global Configuration Commands
Debug Commands C-2
Unsupported Privileged EXEC Commands
C-2
C-3
Embedded Event Manager C-3
Unsupported Privileged EXEC Commands C-3
Unsupported Global Configuration Commands C-3
Unsupported Commands in Applet Configuration Mode
C-3
Fallback Bridging C-3
Unsupported Privileged EXEC Commands C-3
Unsupported Global Configuration Commands C-4
Unsupported Interface Configuration Commands C-4
HSRP C-5
Unsupported Global Configuration Commands C-5
Unsupported Interface Configuration Commands C-5
IGMP Snooping Commands
C-6
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
xxxix
Contents
Unsupported Global Configuration Commands
C-6
Interface Commands C-6
Unsupported Privileged EXEC Commands C-6
Unsupported Global Configuration Commands C-6
Unsupported Interface Configuration Commands C-6
IP Multicast Routing C-6
Unsupported Privileged EXEC Commands C-6
Unsupported Global Configuration Commands C-7
Unsupported Interface Configuration Commands C-7
IP Unicast Routing C-8
Unsupported Privileged EXEC or User EXEC Commands C-8
Unsupported Global Configuration Commands C-8
Unsupported Interface Configuration Commands C-9
Unsupported BGP Router Configuration Commands C-9
Unsupported VPN Configuration Commands C-9
Unsupported Route Map Commands C-9
MAC Address Commands C-10
Unsupported Privileged EXEC Commands C-10
Unsupported Global Configuration Commands C-10
Miscellaneous C-10
Unsupported Privileged EXEC Commands C-10
Unsupported Global Configuration Commands C-11
MSDP C-11
Unsupported Privileged EXEC Commands C-11
Unsupported Global Configuration Commands C-11
NetFlow Commands C-11
Unsupported Global Configuration Commands
C-11
Network Address Translation (NAT) Commands C-12
Unsupported Privileged EXEC Commands C-12
QoS
C-12
Unsupported Global Configuration Command C-12
Unsupported Interface Configuration Commands C-12
Unsupported Policy-Map Configuration Command C-12
RADIUS C-12
Unsupported Global Configuration Commands
C-12
SNMP C-13
Unsupported Global Configuration Commands
C-13
Spanning Tree
C-13
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
xl
OL-12189-01
Contents
Unsupported Global Configuration Command C-13
Unsupported Interface Configuration Command C-13
VLAN C-13
Unsupported Global Configuration Command
Unsupported User EXEC Commands C-13
VTP
C-13
C-13
Unsupported Privileged EXEC Command
C-13
INDEX
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
xli
Contents
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
xlii
OL-12189-01
Preface
Audience
This guide is for the networking professional using the Cisco IOS command-line interface (CLI) to
manage the standalone Cisco Catalyst Switch Module 3110 for IBM BladeCenter, the switch stack, or
the Cisco Catalyst Switch Module 3012 for IBM BladeCenter, referred to as the switch. Before using
this guide, you should have experience working with the Cisco IOS commands and the switch software
features. Before using this guide, you should have experience working with the concepts and
terminology of Ethernet and local area networking.
The Catalyst Switch Module 3110 is also referred to as a stacking-capable switch, and the Catalyst
Switch Module 3012 is referred to as a nonstacking-capable switch.
You install the switch in the IBM BladeCenter server chassis, referred to as the enclosure. For
information about the supported IBM BladeCenter server chassises, see your chassis documentation.
Purpose
This guide provides procedures for using the commands that have been created or changed for use with
the switches. It does not provide detailed information about these commands. For detailed information
about these commands, see the 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 Products & Services > Technical Support & Documentation > See Documentation >
Cisco IOS Software.
This guide does not provide detailed information on the GUIs for the embedded device manager or for
Cisco Network Assistant (hereafter referred to as Network Assistant) that you can use to manage the
switch. However, the concepts in this guide are applicable to the GUI user. For information about the
device manager, see the switch online help. For information about Network Assistant, see Getting
Started with Cisco Network Assistant, available on Cisco.com.
This guide does not describe system messages you might encounter or how to install your switch. For
more information, see the system message guide for this release and the hardware installation guide.
For documentation updates, see the release notes for this release.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
xliii
Preface
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
Caution
Means reader take note. Notes contain helpful suggestions or references to materials not contained in
this manual.
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/ps8741/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 section in the getting started
guide or the Configuring the Switch with the CLI-Based Setup Program appendix in the hardware
installation guide.
For device manager requirements, see the System Requirements section in the release notes (not
orderable but available on Cisco.com).
For Network Assistant requirements, see the Getting Started with Cisco Network Assistant (not
orderable but available on Cisco.com).
For upgrading information, see the Downloading Software section in the release notes.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
xliv
OL-12189-01
Preface
Release Notes for the Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Command Reference
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide
Cisco Software Activation Document for IBM
Device manager online help (available on the switch)
Cisco Catalyst Switch Module 3110G, 3110X, and 3012 for IBM BladeCenter Hardware Installation
Guide
Cisco Catalyst Switch Module 3110G, 3110X, and 3012 for IBM BladeCenter Getting Started Guide
Regulatory Compliance and Safety Information for the Cisco Catalyst Switch Module 3110G,
3110X, and 3012 for IBM BladeCenter
For information about the Network Admission Control (NAC) features, see the Network Admission
Control Software Configuration Guide
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional
information, see the monthly Whats New in Cisco Product Documentation, which also lists all new and
revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the Whats New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed
and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free
service and Cisco currently supports RSS version 2.0.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
xlv
OL-12189-01
Preface
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
xlvi
OL-12189-01
CH A P T E R
Overview
This chapter provides these topics about the switch software:
Features, page 1-1
Default Settings After Initial Switch Configuration, page 1-14
Network Configuration Examples, page 1-16
Where to Go Next, page 1-20
The term switch refers to a standalone switch and to a switch stack.
In this document, IP refers to IP Version 4 (IPv4) unless there is a specific reference to IP Version 6
(IPv6).
Note
The examples in this document are for a stacking-capable switch. When you specify an interface in a
command-line interface (CLI) command, the interface is on the stacking-capable switch, for example,
gigabitethernet 1/0/5.
The examples also apply to the nonstacking-capable switch. In the previous example, the specified
interface on a nonstacking-capable switch is gigabitethernet0/5 (without the stack member number
of 1/).
Features
The Catalyst Switch Module 3110 and Catalyst Switch Module 3012 support either the cryptographic
(supports encryption) universal software image or the noncryptographic universal software image. The
Catalyst Switch Module 3110 supports multiple feature sets . The Catalyst Switch Module 3012 supports
only the IP base feature set.
On the Catalyst Switch Module 3110, the cryptographic universal software image supports the IP base,
IP services, and advanced IP services feature sets. The noncryptographic universal software image
supports only the IP base and IP services feature sets. To enable a specific feature set, you must have a
Cisco IOS software license for that feature set. For more information about the software license, see the
Cisco Software Activation for IBM document on Cisco.com.
On the Catalyst Switch Module 3012, you do not need a software license.
Some features described in this chapter are only available on the cryptographic software image. You
must obtain authorization to use these features and to download the cryptographic software from
Cisco.com. For more information, see the release notes for this release.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
1-1
Chapter 1
Overview
Features
The switch can support one of these feature sets:
IP base feature set, which provides Layer 2+ features (enterprise-class intelligent services). These
features include access control lists (ACLs), quality of service (QoS), static routing, EIGRP stub
routing, PIM stub routing, the Hot Standby Router Protocol (HSRP), Routing Information Protocol
(RIP), and basic IPv6 management. Switches with the IP base feature set can be upgraded to the IP
services feature set.
IP services feature set, which provides a richer set of enterprise-class intelligent services. It includes
all IP base features plus full Layer 3 routing (IP unicast routing, IP multicast routing, and fallback
bridging). The IP services feature set includes protocols such as the Enhanced Interior Gateway
Routing Protocol (EIGRP) and the Open Shortest Path First (OSPF) Protocol. This feature set also
supports IPv6 access control lists (ACLs) and Multicast Listener Discovery (MLD) snooping.
Switches with the IP services feature set can be upgraded to the advanced IP services feature set.
IP services-only Layer 3 features are described in the Layer 3 Features section on page 1-12.
For more information, see Chapter 24, Configuring IPv6 MLD Snooping, and Chapter 35,
Configuring IPv6 ACLs.
Note
Advanced IP services feature set, which provides full IPv6 support. It includes all IP service features
with IPv6 routing and IPv6 ACLs. For more information on IPv6 routing, see Chapter 39,
Configuring IPv6 Host Functions and Unicast Routing. For more information about IPv6 ACLs,
see Chapter 35, Configuring IPv6 ACLs.
Unless otherwise noted, all features described in this chapter and in this guide are supported on
both the IP base and IP services feature sets.
The switch has these features:
Deployment Features, page 1-3
Performance Features, page 1-4
Management Options, page 1-5
Manageability Features, page 1-6 (includes a feature requiring the cryptographic universal software
image)
Availability and Redundancy Features, page 1-7
VLAN Features, page 1-8
Security Features, page 1-9 (includes a feature requiring the cryptographic universal software
image)
QoS and CoS Features, page 1-10
Layer 3 Features, page 1-12 (includes features requiring the IP services feature set)
Monitoring Features, page 1-13
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
1-2
OL-12189-01
Chapter 1
Overview
Features
Deployment Features
The switch ships with these features:
Express Setup for quickly configuring a switch for the first time with basic IP information, contact
information, switch and Telnet passwords, and Simple Network Management Protocol (SNMP)
information through a browser-based program only in switch stacks. For more information about
Express Setup, see the getting started guide.
User-defined and Cisco-default Smartports macros for creating custom switch configurations for
simplified deployment across the network.
An embedded device manager GUI for configuring and monitoring a single switch through a web
browser. For information about starting the device manager, see the getting started guide. For more
information about the device manager, see the switch online help.
Cisco Network Assistant (referred to as Network Assistant) for
Managing communities, which are device groups like clusters, except that they can contain
routers and access points and can be made more secure.
Simplifying and minimizing switch and switch stack management from anywhere in your
intranet.
Accomplishing multiple configuration tasks from a single graphical interface without needing
to remember command-line interface (CLI) commands to accomplish specific tasks.
Interactive guide mode that guides you in configuring complex features such as VLANs, ACLs,
and quality of service (QoS).
Configuration wizards that prompt you to provide only the minimum required information to
configure complex features such as QoS priorities for video traffic, priority levels for data
applications, and security.
Downloading an image to a switch.
Applying actions to multiple ports and multiple switches at the same time, such as VLAN and
QoS settings, inventory and statistic reports, link- and switch-level monitoring and
troubleshooting, and multiple switch software upgrades.
Viewing a topology of interconnected devices to identify existing switch clusters and eligible
switches that can join a cluster and to identify link information between switches.
Monitoring real-time status of a switch or multiple switches from the LEDs on the front-panel
images. The system and port LED colors on the images are similar to those used on the physical
LEDs.
Cisco StackWise Plus technology on stacking-capable switches for
Connecting up to nine switches through their StackWise Plus ports that operate as a single
switch or switch-router in the network.
Creating a bidirectional 32-Gb/s switching fabric across the switch stack, with all stack
members having full access to the system bandwidth.
Using a single IP address and configuration file to manage the entire switch stack.
Automatic Cisco IOS version-check of new stack members with the option to automatically load
images from the stack master or from a TFTP server.
Adding, removing, and replacing switches in the stack without disrupting the operation of the
stack.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
1-3
Chapter 1
Overview
Features
Provisioning a new member for a switch stack with the offline configuration feature. You can
configure in advance the interface configuration for a specific stack member number and for a
specific switch type of a new switch that is not part of the stack. The switch stack retains this
information across stack reloads whether or not the provisioned switch is part of the stack.
Displaying stack-ring activity statistics (the number of frames sent by each stack member to the
ring).
Performance Features
The switch ships with these 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- and
10/100/1000-Mb/s interfaces that enables the interface to automatically detect the required cable
connection type (straight-through or crossover) and to configure the connection appropriately
Support for the maximum packet size or maximum transmission unit (MTU) size for these types of
frames:
Up to 9216 bytes for routed frames
Up to 9216 bytes for frames that are bridged in hardware and software through Gigabit Ethernet
ports and 10-Gigabit Ethernet ports
IEEE 802.3x flow control on all ports (the switch does not send pause frames)
Up to 64 Gb/s of throughput in a switch stack
EtherChannel for enhanced fault tolerance and for providing up to 8 Gb/s (Gigabit EtherChannel)
or 80 Gb/s (10-Gigabit EtherChannel) full-duplex bandwidth among switches, routers, and servers
Port Aggregation Protocol (PAgP) and Link Aggregation Control Protocol (LACP) for automatic
creation of EtherChannel links
Forwarding of Layer 2 and Layer 3 packets at Gigabit line rate
Forwarding of Layer 2 and Layer 3 packets at Gigabit line rate across the switches in the stack
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
IGMP report suppression for sending only one IGMP report per multicast router query to the
multicast devices (supported only for IGMPv1 or IGMPv2 queries)
IGMP snooping querier support to configure switch to generate periodic IGMP General Query
messages
IGMP Helper to allow the switch to forward a host request to join a multicast stream to a specific
IP destination address
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
1-4
OL-12189-01
Chapter 1
Overview
Features
Multicast Listener Discovery (MLD) snooping to enable efficient distribution of IP Version 6 (IPv6)
multicast data to clients and routers in a switched network.
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
IGMP filtering for controlling the set of multicast groups to which hosts on a switch port can belong
IGMP throttling for configuring the action when the maximum number of entries is in the IGMP
forwarding table
IGMP leave timer for configuring the leave latency for the network
Switch Database Management (SDM) templates for allocating system resources to maximize
support for user-selected features
Web Cache Communication Protocol (WCCP) for redirecting traffic to wide-area application
engines, for enabling content requests to be fulfilled locally, and for localizing web-traffic patterns
in the network (only the Catalyst Switch Module 3110 running the IP services feature set)
Management Options
These are the options for configuring and managing the switch:
An embedded device managerThe device manager is a GUI that is integrated in the universal
software image. You use it to configure and to monitor a single switch. For information about starting
the device manager, see the getting started guide. For more information about the device manager, see
the switch online help.
Network AssistantNetwork Assistant is a network management application that can be
downloaded from Cisco.com. You use it to manage a single switch, a cluster of switches, or a
community of devices. For more information about Network Assistant, see Getting Started with
Cisco Network Assistant, available on Cisco.com.
CLIThe Cisco IOS software supports desktop- and multilayer-switching features. You can access
the CLI by connecting your management station directly to the switch console port, by connecting
your PC directly to the Ethernet management port, or by using Telnet from a remote management
station or PC. You can manage the switch stack by connecting to the console port or Ethernet
management port of any stack member. For more information about the CLI, see Chapter 2, Using
the Command-Line Interface.
SNMPSNMP management applications such as CiscoWorks2000 LAN Management Suite (LMS)
and HP OpenView. You can manage from an SNMP-compatible management station or a PC 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. For more information about
using SNMP, see Chapter 32, Configuring SNMP.
CNSCisco Networking Services 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 CNS Agents.
Advanced Management Module (AMM) GUIThe internal Ethernet management port (also
referred to as the Fa0 or fastethernet0 port) on the switch sends and receives only management
traffic between the switch and the AMM. The port is connected to the AMM through the backplane
connector.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
1-5
Chapter 1
Overview
Features
Manageability Features
These are the manageability features:
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 for forwarding User Datagram Protocol (UDP) broadcasts, including IP address
requests, from DHCP clients
DHCP server for automatic assignment of IP addresses and other DHCP options to IP hosts
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
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
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
Support for the LLDP-MED location TLV that provides location information from the switch to the
endpoint device
Network Time Protocol (NTP) for providing a consistent time stamp to all switches from an external
source
Cisco IOS File System (IFS) for providing a single interface to all file systems that the switch uses
Configuration logging to log and to view changes to the switch configuration
Configuration replacement and rollback to replace the running configuration on a switch with any
saved Cisco IOS configuration file
Unique device identifier to provide product identification information through a show inventory
user EXEC command display
In-band management access through the device manager over a Netscape Navigator or Microsoft
Internet Explorer browser session
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 Secure Shell (SSH) connections
for multiple CLI-based sessions over the network (requires the cryptographic universal software
image)
In-band management access through SNMP Versions 1, 2c, 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
Secure Copy Protocol (SCP) feature to provide a secure and authenticated method for copying
switch configuration or switch image files (requires the cryptographic universal software image)
The HTTP client in Cisco IOS supports can send requests to both IPv4 and IPv6 HTTP servers, and
the HTTP server in Cisco IOS can service HTTP requests from both IPv4 and IPv6 HTTP clients.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
1-6
OL-12189-01
Chapter 1
Overview
Features
Note
SNMP can be configured over IPv6 transport so that an IPv6 host can send SNMP queries and
receive SNMP notifications from a device running IPv6.
IPv6 supports stateless autoconfiguration to manage link, subnet, and site addressing changes, such
as management of host and mobile IP addresses.
For additional descriptions of the management interfaces, see the Network Configuration Examples
section on page 1-16.
Availability and Redundancy Features
These are the availability and redundancy features:
HSRP for command switch and Layer 3 router redundancy
Automatic stack master re-election (failover support) for replacing stack masters that become
unavailable (only the Catalyst Switch Module 3110)
The newly elected stack master begins accepting Layer 2 traffic in less than 1 second and Layer 3
traffic between 3 to 5 seconds.
Cross-stack EtherChannel for providing redundant links across the switch stack (only the Catalyst
Switch Module 3110)
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 load-balancing across VLANs
Rapid PVST+ for load-balancing across VLANs and providing rapid convergence of
spanning-tree instances
UplinkFast, cross-stack UplinkFast (only the Catalyst Switch Module 3110), and BackboneFast
for fast convergence after a spanning-tree topology change and for achieving load-balancing
between redundant uplinks, including Gigabit uplinks and cross-stack Gigabit uplinks (only the
Catalyst Switch Module 3110)
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 changing 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 change 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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
1-7
Chapter 1
Overview
Features
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
Link-state tracking to mirror the state of the ports that carry upstream traffic from connected hosts
and servers and to allow the failover of the server traffic to an operational link on another Cisco
Ethernet switch
VLAN Features
These are the 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 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 (IEEE 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
Dynamic voice virtual LAN (VLAN) for multidomain authentication (MDA) to allow a dynamic
voice VLAN on an MDA-enabled port
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. 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
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
1-8
OL-12189-01
Chapter 1
Overview
Features
Security Features
The switch ships with these security features:
Web authentication to allow a supplicant (client) that does not support IEEE 802.1x functionality to
be authenticated using a web browser.
Password-protected access (read-only and read-write access) to management interfaces (device
manager, Network Assistant, and the CLI) for protection against unauthorized configuration
changes
Multilevel security for a choice of security level, notification, and resulting actions
Static MAC addressing for ensuring security
Protected port option for restricting the forwarding of traffic to designated ports on the same switch
Port security option for limiting and identifying MAC addresses of the stations allowed to access
the port
VLAN aware port security option to shut down the VLAN on the port when a violation occurs,
instead of shutting down the entire port
Port security aging to set the aging time for secure addresses on a port
BPDU guard for shutting down a Port Fast-configured port when an invalid configuration occurs
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/UDP headers
Source and destination MAC-based ACLs for filtering non-IP traffic
IPv6 ACLs to be applied to interfaces to filter IPv6 traffic
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
IEEE 802.1Q tunneling so that customers with users at remote sites across a service-provider
network can keep VLANs segregated from other customers and Layer 2 protocol tunneling to ensure
that the customers network has complete STP, CDP, and VTP information about all users
Layer 2 point-to-point tunneling to facilitate the automatic creation of EtherChannels
Layer 2 protocol tunneling bypass feature to provide interoperability with third-party vendors
IEEE 802.1x port-based authentication to prevent unauthorized devices (clients) from gaining
access to the network. These features are supported:
Multidomain authentication (MDA) to allow both a data device and a voice device, such as an
IP phone (Cisco or non-Cisco), to independently authenticate on the same IEEE 802.1x-enabled
switch port
VLAN assignment for restricting IEEE 802.1x-authenticated users to a specified VLAN
Port security for controlling access to IEEE 802.1x ports
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
1-9
Chapter 1
Overview
Features
Voice VLAN to permit a Cisco IP Phone to access the voice VLAN regardless of the authorized
or unauthorized state of the port
IP phone detection enhancement to detect and recognize a Cisco IP phone
Guest VLAN to provide limited services to non-IEEE 802.1x-compliant users
Restricted VLAN to provide limited services to users who are IEEE 802.1x compliant, but do
not have the credentials to authenticate via the standard IEEE 802.1x processes
IEEE 802.1x accounting to track network usage
IEEE 802.1x with wake-on-LAN to allow dormant PCs to be powered on based on the receipt
of a specific Ethernet frame
MAC authentication bypass to authorize clients based on the client MAC address.
Network Admission Control (NAC) features:
NAC Layer 2 IEEE 802.1x validation of the antivirus condition or posture of endpoint systems
or clients before granting the devices network access.
For information about configuring NAC Layer 2 IEEE 802.1x validation, see the Configuring
NAC Layer 2 IEEE 802.1x Validation section on page 9-41.
NAC Layer 2 IP validation of the posture of endpoint systems or clients before granting the
devices network access.
For information about configuring NAC Layer 2 IP validation, see the Network Admission
Control Software Configuration Guide.
IEEE 802.1x inaccessible authentication bypass.
For information about configuring this feature, see the Configuring the Inaccessible
Authentication Bypass Feature section on page 9-37.
Authentication, authorization, and accounting (AAA) down policy for a NAC Layer 2 IP
validation of a host if the AAA server is not available when the posture validation occurs.
For information about this feature, see the Network Admission Control Software Configuration
Guide.
TACACS+, a proprietary feature for managing network security through a TACACS server
RADIUS for verifying the identity of, granting access to, and tracking the actions of remote users
through AAA services
Kerberos security system to authenticate requests for network resources by using a trusted third
party (requires the cryptographic universal software image)
Secure Socket Layer (SSL) 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 the cryptographic software image)
QoS and CoS Features
These are the QoS and CoS features:
Automatic QoS (auto-QoS) to simplify the deployment of existing QoS features by classifying
traffic and configuring egress queues
Cross-stack QoS for configuring QoS features to all switches in a switch stack rather than on an
individual-switch basis (only the Catalyst Switch Module 3110)
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
1-10
OL-12189-01
Chapter 1
Overview
Features
Classification
IP type-of-service/Differentiated Services Code Point (IP ToS/DSCP) and IEEE 802.1p CoS
marking priorities on a per-port basis for protecting the performance of mission-critical
applications
IP ToS/DSCP and IEEE 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
Policing
Traffic-policing policies on the switch port for managing how much of the port bandwidth
should be allocated to a specific traffic flow
If you configure multiple class maps for a hierarchical policy map, each class map can be
associated with its own port-level (second-level) policy map. Each second-level policy map can
have a different policer.
Aggregate policing for policing traffic flows in aggregate to restrict specific applications or
traffic flows to metered, predefined rates
Out-of-Profile
Out-of-profile markdown for packets that exceed bandwidth utilization limits
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 specifying the rate at which packets are
sent to the stack or internal ring (sharing is the only supported mode on ingress queues)
Egress queues and scheduling
Four egress queues per port
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 specifying 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.
Automatic quality of service (QoS) voice over IP (VoIP) enhancement for port -based trust of DSCP
and priority queuing for egress traffic
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
1-11
Chapter 1
Overview
Features
Layer 3 Features
These are the Layer 3 features:
Note
Some features noted in this section are available only in the IP services feature set.
HSRP for Layer 3 router redundancy
IP routing protocols for load balancing and for constructing scalable, routed backbones:
RIP Versions 1 and 2
OSPF (only the Catalyst Switch Module 3110 running the IP services feature set)
Enhanced IGRP (EIGRP) (only the Catalyst Switch Module 3110 running the IP services
feature set)
Border Gateway Protocol (BGP) Version 4 (only the Catalyst Switch Module 3110 running the
IP services feature set)
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 (only the Catalyst
Switch Module 3110)
Multiple VPN routing/forwarding (multi-VRF) instances in customer edge devices to allow service
providers to support multiple virtual private networks (VPNs) and overlap IP addresses between
VPNs (only the Catalyst Switch Module 3110 running the IP services feature set)
VRF Lite for configuring multiple private routing domains for network virtualization and virtual
private multicast networks (only the Catalyst Switch Module 3110)
Support for these IP services, making them VRF aware so that they can operate on multiple routing
instances: HSRP, uRPF, ARP, SNMP, IP SLA, TFTP, FTP, syslog, traceroute, and ping
Fallback bridging for forwarding non-IP traffic between two or more VLANs (only the Catalyst
Switch Module 3110 running the IP services feature set)
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 (only the Catalyst Switch Module 3110 running the IP
services feature set)
Multicast Source Discovery Protocol (MSDP) for connecting multiple PIM-SM domains (only the
Catalyst Switch Module 3110 running the IP services feature set)
Distance Vector Multicast Routing Protocol (DVMRP) tunneling for interconnecting two
multicast-enabled networks across nonmulticast networks (only the Catalyst Switch Module 3110
running the IP services feature set)
DHCP relay for forwarding UDP broadcasts, including IP address requests, from DHCP clients
IPv6 unicast host management
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
1-12
OL-12189-01
Chapter 1
Overview
Features
IPv6 unicast routing capability for forwarding IPv6 traffic through configured interfaces (only the
Catalyst Switch Module 3110 running the advanced IP services feature set)
Support for EIGRP IPv6, which utilizes IPv6 transport, communicates with IPv6 peers, and
advertises IPv6 routes (only the Catalyst Switch Module 3110)
IP unicast reverse path forwarding (unicast RPF) for confirming source packet IP addresses (only
the Catalyst Switch Module 3110)
Nonstop forwarding (NSF) awareness to enable the Layer 3 switch to continue forwarding packets
from an NSF-capable neighboring router when the primary route processor (RP) is failing and the
backup RP is taking over, or when the primary RP is manually reloaded for a nondisruptive software
upgrade (only the Catalyst Switch Module 3110 running the IP services feature set)
NSF-capable routing for OSPF and EIGRP that allows the switch to rebuild routing tables based on
information from NSF-aware and NSF-capable neighbors (only the Catalyst Switch Module 3110)
Monitoring Features
These are the monitoring features:
Switch LEDs that provide port- and switch-level status on the Catalyst Switch Module 3012
Switch LEDs that provide port-, switch-, and stack-level status on the Catalyst Switch Module 3110
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 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
Layer 2 traceroute to identify the physical path that a packet takes from a source device to a
destination device
Time Domain Reflector (TDR) to diagnose and resolve cabling problems on 10/100 and
10/100/1000 copper Ethernet ports
Online diagnostics to test the hardware functionality of the supervisor engine, modules, and switch
while the switch is connected to a live network
On-board failure logging (OBFL) to collect information about the switch and the power supplies
connected to it
Enhanced object tracking (EOT) for HSRP to determine the proportion of hosts in a LAN by tracking
the routing table state or to trigger the standby router failover (only the Catalyst Switch Module
3110)
IP Service Level Agreements (IP SLAs) support to measure network performance by using active
traffic monitoring
IP SLAs EOT to use the output from IP SLAs tracking operations triggered by an action such as
latency, jitter, or packet loss for a standby router failover takeover
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
1-13
Chapter 1
Overview
Default Settings After Initial Switch Configuration
Default Settings After Initial Switch Configuration
The switch is designed for plug-and-play operation, requiring only that you assign basic IP information
to the switch and connect it to the other devices in your network. If you have specific network needs,
you can change the interface-specific and system- and stack-wide settings.
Note
For information about assigning an IP address by using the browser-based Express Setup program, see
the getting started guide. For information about assigning an IP address by using the CLI-based setup
program, see the hardware installation guide.
If you do not configure the switch at all, the switch operates with these default settings:
Default switch IP address, subnet mask, and default gateway is 0.0.0.0. For more information, see
Chapter 3, Assigning the Switch IP Address and Default Gateway, and Chapter 21, Configuring
DHCP Features and IP Source Guard.
Default domain name is not configured. For more information, see Chapter 3, Assigning the Switch
IP Address and Default Gateway.
DHCP client is enabled, the DHCP server is enabled (only if the device acting as a DHCP server is
configured and is enabled), and the DHCP relay agent is enabled (only if the device is acting as a
DHCP relay agent is configured and is enabled). For more information, see Chapter 3, Assigning
the Switch IP Address and Default Gateway, and Chapter 21, Configuring DHCP Features and IP
Source Guard.
Switch stack is enabled (not configurable). For more information, see Chapter 5, Managing Switch
Stacks.
No passwords are defined. For more information, see Chapter 6, Administering the Switch.
System name and prompt is Switch. For more information, see Chapter 6, Administering the
Switch.
NTP is enabled. For more information, see Chapter 6, Administering the Switch.
DNS is enabled. For more information, see Chapter 6, Administering the Switch.
TACACS+ is disabled. For more information, see Chapter 7, Configuring Switch-Based
Authentication.
RADIUS is disabled. For more information, see Chapter 7, Configuring Switch-Based
Authentication.
The standard HTTP server and Secure Socket Layer (SSL) HTTPS server are both enabled. For more
information, see Chapter 7, Configuring Switch-Based Authentication.
IEEE 802.1x is disabled. For more information, see Chapter 9, Configuring IEEE 802.1x
Port-Based Authentication.
Port parameters
Operating mode is Layer 2 (switchport). For more information, see Chapter 10, Configuring
Interface Characteristics.
Interface speed and duplex mode is autonegotiate. For more information, see Chapter 10,
Configuring Interface Characteristics.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
1-14
OL-12189-01
Chapter 1
Overview
Default Settings After Initial Switch Configuration
Auto-MDIX is enabled. For more information, see Chapter 10, Configuring Interface
Characteristics.
Flow control is off. For more information, see Chapter 10, Configuring Interface
Characteristics.
No Smartports macros are defined. For more information, see Chapter 11, Configuring Smartports
Macros.
VLANs
Default VLAN is VLAN 1. For more information, see Chapter 12, Configuring VLANs.
VLAN trunking setting is dynamic auto (DTP). For more information, see Chapter 12,
Configuring VLANs.
Trunk encapsulation is negotiate. For more information, see Chapter 12, Configuring VLANs.
VTP mode is server. For more information, see Chapter 13, Configuring VTP.
VTP version is Version 1. For more information, see Chapter 13, Configuring VTP.
No private VLANs are configured. For more information, see Chapter 15, Configuring Private
VLANs.
Voice VLAN is disabled. For more information, see Chapter 14, Configuring Voice VLAN.
IEEE 802.1Q tunneling and Layer 2 protocol tunneling are disabled. For more information, see
Chapter 16, Configuring IEEE 802.1Q and Layer 2 Protocol Tunneling.
STP, PVST+ is enabled on VLAN 1. For more information, see Chapter 17, Configuring STP.
MSTP is disabled. For more information, see Chapter 18, Configuring MSTP.
Optional spanning-tree features are disabled. For more information, see Chapter 19, Configuring
Optional Spanning-Tree Features.
Flex Links are not configured. For more information, see Chapter 20, Configuring Flex Links and
the MAC Address-Table Move Update Feature.
DHCP snooping is disabled. The DHCP snooping information option is enabled. For more
information, see Chapter 21, Configuring DHCP Features and IP Source Guard.
IP source guard is disabled. For more information, see Chapter 21, Configuring DHCP Features
and IP Source Guard.
Dynamic ARP inspection is disabled on all VLANs. For more information, see Chapter 22,
Configuring Dynamic ARP Inspection.
IGMP snooping is enabled. No IGMP filters are applied. For more information, see Chapter 23,
Configuring IGMP Snooping and MVR.
IGMP throttling setting is deny. For more information, see Chapter 23, Configuring IGMP
Snooping and MVR.
The IGMP snooping querier feature is disabled. For more information, see Chapter 23, Configuring
IGMP Snooping and MVR.
MVR is disabled. For more information, see Chapter 23, Configuring IGMP Snooping and MVR.
Port-based traffic
Broadcast, multicast, and unicast storm control is disabled. For more information, see
Chapter 25, Configuring Port-Based Traffic Control.
No protected ports are defined. For more information, see Chapter 25, Configuring Port-Based
Traffic Control.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
1-15
Chapter 1
Overview
Network Configuration Examples
Unicast and multicast traffic flooding is not blocked. For more information, see Chapter 25,
Configuring Port-Based Traffic Control.
No secure ports are configured. For more information, see Chapter 25, Configuring Port-Based
Traffic Control.
CDP is enabled. For more information, see Chapter 26, Configuring CDP.
UDLD is disabled. For more information, see Chapter 28, Configuring UDLD.
SPAN and RSPAN are disabled. For more information, see Chapter 29, Configuring SPAN and
RSPAN.
RMON is disabled. For more information, see Chapter 30, Configuring RMON.
Syslog messages are enabled and appear on the console. For more information, see Chapter 31,
Configuring System Message Logging.
SNMP is enabled (Version 1). For more information, see Chapter 32, Configuring SNMP.
No ACLs are configured. For more information, see Chapter 34, Configuring Network Security
with ACLs.
QoS is disabled. For more information, see Chapter 36, Configuring QoS.
No EtherChannels are configured. For more information, see Chapter 37, Configuring
EtherChannels and Link-State Tracking.
IP unicast routing is disabled. For more information, see Chapter 38, Configuring IP Unicast
Routing.
No HSRP groups are configured. For more information, see Chapter 40, Configuring HSRP.
IP multicast routing is disabled on all interfaces (only the Catalyst Switch Module 3110). For more
information, see Chapter 44, Configuring IP Multicast Routing.
MSDP is disabled (only the Catalyst Switch Module 3110). For more information, see Chapter 45,
Configuring MSDP.
Fallback bridging is not configured (only the Catalyst Switch Module 3110). For more information,
see Chapter 46, Configuring Fallback Bridging.
Network Configuration Examples
This section provides network configuration concepts and includes examples of using the switch to
create dedicated network segments and interconnecting the segments through Gigabit Ethernet and
10-Gigabit Ethernet connections.
Design Concepts for Using the Switch section on page 1-16
Small to Medium-Sized Network section on page 1-19
Design Concepts for Using the Switch
As your network users compete for network bandwidth, it takes longer to send and receive data. When
you configure your network, consider the bandwidth required by your network users and the relative
priority of the network applications that they use.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
1-16
OL-12189-01
Chapter 1
Overview
Network Configuration Examples
Table 1-1 describes what can cause network performance to degrade and how you can configure your
network to increase the bandwidth available to your network users.
Table 1-1
Increasing Network Performance
Network Demands
Suggested Design Methods
Too many users on a single network
segment and a growing number of
users accessing the Internet
Increased power of new PCs,
workstations, and servers
High bandwidth demand from
networked applications (such as
e-mail with large attached files)
and from bandwidth-intensive
applications (such as
multimedia)
Create smaller network segments so that fewer users share the bandwidth, and use
VLANs and IP subnets to place the network resources in the same logical network
as the users who access those resources most.
Use full-duplex operation between the switch and its connected workstations.
Connect global resourcessuch as servers and routers to which the network users
require equal accessdirectly to the high-speed switch ports so that they have
their own high-speed segment.
Use the EtherChannel feature between the switch and its connected servers and
routers.
Bandwidth alone is not the only consideration when designing your network. As your network traffic
profiles evolve, consider providing network services that can support applications for voice and data
integration, multimedia integration, application prioritization, and security. Table 1-2 describes some
network demands and how you can meet them.
Table 1-2
Providing Network Services
Network Demands
Suggested Design Methods
Efficient bandwidth usage for
multimedia applications and
guaranteed bandwidth for critical
applications
High demand on network redundancy
and availability to provide always on
mission-critical applications
Use IGMP snooping to efficiently forward multimedia and multicast traffic.
Use other QoS mechanisms such as packet classification, marking, scheduling,
and congestion avoidance to classify traffic with the appropriate priority level,
thereby providing maximum flexibility and support for mission-critical, unicast,
and multicast, and multimedia applications.
Use optional IP multicast routing to design networks better suited for multicast
traffic.
Use MVR to continuously send multicast streams in a multicast VLAN but to
isolate the streams from subscriber VLANs for bandwidth and security reasons.
Use switch stacks, where all stack members are eligible stack masters in case of
stack-master failure. All stack members have synchronized copies of the saved
and running configuration files of the switch stack.
Use cross-stack EtherChannels for providing redundant links across the switch
stack.
Use Hot Standby Router Protocol (HSRP) for cluster command switch and router
redundancy.
Use VLAN trunks, cross-stack UplinkFast, and BackboneFast for traffic-load
balancing on the uplink ports so that the uplink port with a lower relative port cost
is selected to carry the VLAN traffic.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
1-17
Chapter 1
Overview
Network Configuration Examples
Table 1-2
Providing Network Services (continued)
Network Demands
Suggested Design Methods
An evolving demand for IP telephony
Use QoS to prioritize applications such as IP telephony during congestion and to
help control both delay and jitter within the network.
Use switches that support at least two queues per port to prioritize voice and data
traffic as either high- or low-priority, based on IEEE 802.1p/Q. The switch
supports at least four queues per port.
Use voice VLAN IDs (VVIDs) to provide separate VLANs for voice traffic.
A growing demand for using existing Use the Catalyst Long-Reach Ethernet (LRE) switches to provide up to 15 Mb of IP
connectivity over existing infrastructure, such as existing telephone lines.
infrastructure to transport data and
voice from a home or office to the
Note
LRE is the technology used in the Catalyst 2950 LRE switch. See the
Internet or an intranet at higher
documentation sets specific to this switch for LRE information.
speeds
You can use the switches and switch stacks to create the following:
Data center (Figure 1-1)For high-speed access to network resources, you can use switches and
switch stacks in the access layer to provide Gigabit Ethernet access to the blade servers. To prevent
congestion, use QoS DSCP marking priorities on these switches. For high-speed IP forwarding at
the distribution layer, connect the switches in the access layer to a Gigabit multilayer switch in the
backbone, such as a Catalyst 4500 Gigabit switch or Catalyst 6500 Gigabit switch.
Figure 1-1
Data Center
Core
Distribution layer
Catalyst
4500 or 6500
multilayer switch
Si
Blade switch
Layer 3 StackWise Plus
switch stack
Blade servers
201756
Access layer
Expanded data center (Figure 1-2)You can use standalone switches and switch stacks to
interconnect groups of servers, centralizing physical security and administration of your network.
For high-speed IP forwarding at the distribution layer, connect the switches in the access layer to
multilayer switches with routing capability. The Gigabit interconnections minimize latency in the
data flow.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
1-18
OL-12189-01
Chapter 1
Overview
Network Configuration Examples
QoS and policing on the switches provide preferential treatment for certain data streams. They
segment traffic streams into different paths for processing. Security features on the switch ensure
rapid handling of packets.
Fault tolerance from the server racks to the core is achieved through dual homing of servers
connected to dual switch stacks or the switches, which have redundant Gigabit EtherChannels and
cross-stack EtherChannels.
Using 10-Gigabit Ethernet uplinks from the switches provides redundant uplinks to the network
core.
The various lengths of stack cable available, ranging from 0.5 meter to 3 meters, provide extended
connections to the switch stacks across multiple server racks, for multiple stack aggregation.
Figure 1-2
Expanded Data Center
Campus
core
Catalyst
6500 switches
Si
Si
Si
Si
Si
Si
Catalyst 6500
multilayer switches
Blade server
enclosures
201757
Blade switch
StackWise
switch stacks
Small to Medium-Sized Network
Figure 1-3 shows a configuration for a network of up to 500 employees. This network uses a Layer 3
switch stack with high-speed connections to two routers. For network reliability and load-balancing, this
network has HSRP enabled on the routers and on the switches. This ensures connectivity to the Internet,
WAN, and mission-critical network resources in case one of the routers or switches fails. The switches
are using routed uplinks for faster failover. They are also configured with equal-cost routing for load
sharing and redundancy. A Layer 2 switch stack can use cross-stack EtherChannel for load sharing.
The switches are connected to local servers. The server farm includes a call-processing server running
Cisco CallManager software. Cisco CallManager controls call processing and routing. The switches are
interconnected through Gigabit interfaces.
This network uses VLANs to logically segment the network into well-defined broadcast groups and for
security management. Data and multimedia traffic are configured on the same VLAN. Voice traffic is
configured on separate VVIDs. If data, multimedia, and voice traffic are assigned to the same VLAN,
only one VLAN can be configured per wiring closet.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
1-19
Chapter 1
Overview
Where to Go Next
When an end station in one VLAN needs to communicate with an end station in another VLAN, a router
or Layer 3 switch routes the traffic to the destination VLAN. In this network, the switch stack is
providing inter-VLAN routing. VLAN access control lists (VLAN maps) on the switch stack or switch
provide intra-VLAN security and prevent unauthorized users from accessing critical areas of the
network.
In addition to inter-VLAN routing, the multilayer switches provide QoS mechanisms such as DSCP
priorities to prioritize the different types of network traffic and to deliver high-priority traffic. If
congestion occurs, QoS drops low-priority traffic to allow delivery of high-priority traffic.
Cisco CallManager controls call processing and routing. Users with workstations running Cisco
SoftPhone software can place, receive, and control calls from their PCs. Using Cisco CallManager
software and Cisco SoftPhone software integrates telephony and IP networks, and the IP network
supports both voice and data.
With the multilayer switches providing inter-VLAN routing and other network services, the routers
focus on firewall services, Network Address Translation (NAT) services, voice-over-IP (VoIP) gateway
services, and WAN and Internet access.
Figure 1-3
Switch Stack in a Collapsed Backbone
Campus
core
Catalyst
6500 switches
Blade server
enclosures
201914
Blade switch
StackWise
switch stacks
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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
1-20
OL-12189-01
CH A P T E R
Using the Command-Line Interface
This chapter describes the Cisco IOS command-line interface (CLI) and how to use it to configure your
standalone switch or a switch stack, referred to as the switch. It contains these sections:
Understanding Command Modes, page 2-1
Understanding the Help System, page 2-3
Understanding Abbreviated Commands, page 2-4
Understanding no and default Forms of Commands, page 2-4
Understanding CLI Error Messages, page 2-5
Using Configuration Logging, page 2-5
Using Command History, page 2-6
Using Editing Features, page 2-7
Searching and Filtering Output of show and more Commands, page 2-10
Accessing the CLI, page 2-10
Understanding Command Modes
The Cisco IOS user interface is divided into many different modes. The commands available to you
depend on which mode you are currently in. Enter a question mark (?) at the system prompt to obtain a
list of commands available for each command mode.
When you start a session on the switch, you begin in user mode, often called user EXEC mode. Only a
limited subset of the commands are available in user EXEC mode. For example, most of the user EXEC
commands are one-time commands, such as show commands, which show the current configuration
status, and clear commands, which clear counters or interfaces. The user EXEC commands are not saved
when the switch reboots.
To have access to all commands, you must enter privileged EXEC mode. Normally, you must enter a
password to enter privileged EXEC mode. From this mode, you can enter any privileged EXEC
command or enter global configuration mode.
Using the configuration modes (global, interface, and line), you can make changes to the running
configuration. If you save the configuration, these commands are stored and used when the switch
reboots. To access the various configuration modes, you must start at global configuration mode. From
global configuration mode, you can enter interface configuration mode and line configuration mode.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
2-1
Chapter 2
Using the Command-Line Interface
Understanding Command Modes
Table 2-1 describes the main command modes, how to access each one, the prompt you see in that mode,
and how to exit the mode. The examples in the table use the hostname Switch.
Table 2-1
Command Mode Summary
Mode
Access Method
Prompt
User EXEC
Begin a session with Switch>
your switch.
Exit Method
About This Mode
Enter logout or
quit.
Use this mode to
Change terminal settings.
Perform basic tests.
Display system
information.
Privileged EXEC
While in user EXEC Switch#
mode, enter the
enable command.
Enter disable to
exit.
Global configuration
While in privileged
EXEC mode, enter
the configure
command.
Switch(config)#
To exit to privileged Use this mode to configure
EXEC mode, enter parameters that apply to the
exit or end, or press entire switch.
Ctrl-Z.
Config-vlan
While in global
configuration mode,
enter the
vlan vlan-id
command.
Switch(config-vlan)#
To exit to global
configuration mode,
enter the exit
command.
While in privileged
EXEC mode, enter
the vlan database
command.
Switch(vlan)#
VLAN configuration
To return to
privileged EXEC
mode, press Ctrl-Z
or enter end.
Use this mode to verify
commands that you have
entered. Use a password to
protect access to this mode.
Use this mode to configure
VLAN parameters. When VTP
mode is transparent, you can
create extended-range VLANs
(VLAN IDs greater than 1005)
and save configurations in the
switch startup configuration
file.
To exit to privileged Use this mode to configure
EXEC mode, enter VLAN parameters for VLANs
exit.
1 to 1005 in the VLAN
database.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
2-2
OL-12189-01
Chapter 2
Using the Command-Line Interface
Understanding the Help System
Table 2-1
Command Mode Summary (continued)
Mode
Access Method
Prompt
Exit Method
Interface
configuration
While in global
configuration mode,
enter the interface
command (with a
specific interface).
Switch(config-if)#
Use this mode to configure
To exit to global
configuration mode, parameters for the Ethernet
ports.
enter exit.
To return to
privileged EXEC
mode, press Ctrl-Z
or enter end.
About This Mode
For information about defining
interfaces, see the Using
Interface Configuration Mode
section on page 10-7.
To configure multiple
interfaces with the same
parameters, see the
Configuring a Range of
Interfaces section on
page 10-9.
Line configuration
While in global
configuration mode,
specify a line with
the line vty or line
console command.
Switch(config-line)#
Use this mode to configure
To exit to global
configuration mode, parameters for the terminal
line.
enter exit.
To return to
privileged EXEC
mode, press Ctrl-Z
or enter end.
For more detailed information on the command modes, see the command reference guide for this release.
Understanding the Help System
You can enter a question mark (?) at the system prompt to display a list of commands available for each
command mode. You can also obtain a list of associated keywords and arguments for any command, as
shown in Table 2-2.
Table 2-2
Help Summary
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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
2-3
Chapter 2
Using the Command-Line Interface
Understanding Abbreviated Commands
Table 2-2
Help Summary (continued)
Command
Purpose
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
Understanding Abbreviated Commands
You need to enter only enough characters for the switch to recognize the command as unique.
This example shows how to enter the show configuration privileged EXEC command in an abbreviated
form:
Switch# show conf
Understanding no and default Forms of Commands
Almost every configuration command also has a no form. In general, use the no form to disable a feature
or function or reverse the action of a command. For example, the no shutdown interface configuration
command reverses the shutdown of an interface. Use the command without the keyword no to re-enable
a disabled feature or to enable a feature that is disabled by default.
Configuration commands can also have a default form. The default form of a command returns the
command setting to its default. Most commands are disabled by default, so the default form is the same
as the no form. However, some commands are enabled by default and have variables set to certain default
values. In these cases, the default command enables the command and sets variables to their default
values.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
2-4
OL-12189-01
Chapter 2
Using the Command-Line Interface
Understanding CLI Error Messages
Understanding CLI Error Messages
Table 2-3 lists some error messages that you might encounter while using the CLI to configure your
switch.
Table 2-3
Common CLI Error Messages
Error Message
Meaning
How to Get Help
% Ambiguous command:
"show con"
You did not enter enough characters
for your switch to recognize the
command.
Re-enter the command followed by a question mark (?)
with a space between the command and the question
mark.
The possible keywords that you can enter with the
command appear.
% Incomplete command.
You did not enter all the keywords or Re-enter the command followed by a question mark (?)
values required by this command.
with a space between the command and the question
mark.
The possible keywords that you can enter with the
command appear.
% Invalid input detected
at ^ marker.
You entered the command
incorrectly. The caret (^) marks the
point of the error.
Enter a question mark (?) to display all the commands
that are available in this command mode.
The possible keywords that you can enter with the
command appear.
Using Configuration Logging
You can log and view changes to the switch configuration. You can use the Configuration Change
Logging and Notification feature to track changes on a per-session and per-user basis. The logger tracks
each configuration command that is applied, the user who entered the command, the time that the
command was entered, and the parser return code for the command. This feature includes a mechanism
for asynchronous notification to registered applications whenever the configuration changes. You can
choose to have the notifications sent to the syslog.
For more information, see the Configuration Change Notification and Logging section of the Cisco
IOS Configuration Fundamentals Configuration Guide, Release 12.4 at this URL:
http://www.cisco.com/en/US/products/ps6350/products_configuration_guide_chapter09186a0080454f
73.html
Note
Only CLI or HTTP changes are logged.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
2-5
Chapter 2
Using the Command-Line Interface
Using Command History
Using Command History
The software provides a history or record of commands that you have entered. The command history
feature is particularly useful for recalling long or complex commands or entries, including access lists.
You can customize this feature to suit your needs as described in these sections:
Changing the Command History Buffer Size, page 2-6 (optional)
Recalling Commands, page 2-6 (optional)
Disabling the Command History Feature, page 2-7 (optional)
Changing the Command History Buffer Size
By default, the switch records ten command lines in its history buffer. You can alter this number for a
current terminal session or for all sessions on a particular line. These procedures are optional.
Beginning in privileged EXEC mode, enter this command to change the number of command lines that
the switch records during the current terminal session:
Switch# terminal history
[size number-of-lines]
The range is from 0 to 256.
Beginning in line configuration mode, enter this command to configure the number of command lines
the switch records for all sessions on a particular line:
Switch(config-line)# history
[size number-of-lines]
The range is from 0 to 256.
Recalling Commands
To recall commands from the history buffer, perform one of the actions listed in Table 2-4. These actions
are optional.
Table 2-4
Recalling Commands
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 appear is controlled by the setting of the
terminal history global configuration command and the history line configuration
command.
1. The arrow keys function only on ANSI-compatible terminals such as VT100s.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
2-6
OL-12189-01
Chapter 2
Using the Command-Line Interface
Using Editing Features
Disabling the Command History Feature
The command history feature is automatically enabled. You can disable it for the current terminal session
or for the command line. These procedures are optional.
To disable the feature during the current terminal session, enter the terminal no history privileged
EXEC command.
To disable command history for the line, enter the no history line configuration command.
Using Editing Features
This section describes the editing features that can help you manipulate the command line. It contains
these sections:
Enabling and Disabling Editing Features, page 2-7 (optional)
Editing Commands through Keystrokes, page 2-8 (optional)
Editing Command Lines that Wrap, page 2-9 (optional)
Enabling and Disabling Editing Features
Although enhanced editing mode is automatically enabled, you can disable it, re-enable it, or configure
a specific line to have enhanced editing. These procedures are optional.
To globally disable enhanced editing mode, enter this command in line configuration mode:
Switch (config-line)# no editing
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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
2-7
Chapter 2
Using the Command-Line Interface
Using Editing Features
Editing Commands through Keystrokes
Table 2-5 shows the keystrokes that you need to edit command lines. These keystrokes are optional.
Table 2-5
Editing Commands through Keystrokes
Capability
Keystroke1
Move around the command line to
make changes or corrections.
Press Ctrl-B, or press the Move the cursor back one character.
left arrow key.
Purpose
Press Ctrl-F, or press the
right arrow key.
Move the cursor forward one character.
Press Ctrl-A.
Move the cursor to the beginning of the command line.
Press Ctrl-E.
Move the cursor to the end of the command line.
Press Esc B.
Move the cursor back one word.
Press Esc F.
Move the cursor forward one word.
Press Ctrl-T.
Transpose the character to the left of the cursor with the
character located at the cursor.
Recall commands from the buffer and Press Ctrl-Y.
paste them in the command line. The
switch provides a buffer with the last
ten items that you deleted.
Press Esc Y.
Recall the most recent entry in the buffer.
Recall the next buffer entry.
The buffer contains only the last 10 items that you have
deleted or cut. If you press Esc Y more than ten times, you
cycle to the first buffer entry.
Delete entries if you make a mistake Press the Delete or
or change your mind.
Backspace key.
Capitalize or lowercase words or
capitalize a set of letters.
Erase the character to the left of the cursor.
Press Ctrl-D.
Delete the character at the cursor.
Press Ctrl-K.
Delete all characters from the cursor to the end of the
command line.
Press Ctrl-U or Ctrl-X.
Delete all characters from the cursor to the beginning of
the command line.
Press Ctrl-W.
Delete the word to the left of the cursor.
Press Esc D.
Delete from the cursor to the end of the word.
Press Esc C.
Capitalize at the cursor.
Press Esc L.
Change the word at the cursor to lowercase.
Press Esc U.
Capitalize letters from the cursor to the end of the word.
Designate a particular keystroke as
Press Ctrl-V or Esc Q.
an executable command, perhaps as a
shortcut.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
2-8
OL-12189-01
Chapter 2
Using the Command-Line Interface
Using Editing Features
Table 2-5
Editing Commands through Keystrokes (continued)
Capability
Keystroke1
Purpose
Scroll down a line or screen on
displays that are longer than the
terminal screen can display.
Press the Return key.
Scroll down one line.
Press the Space bar.
Scroll down one screen.
Press Ctrl-L or Ctrl-R.
Redisplay the current command line.
Note
The More prompt is used for
any output that has more
lines than can be displayed
on the terminal screen,
including show command
output. You can use the
Return and Space bar
keystrokes whenever you see
the More prompt.
Redisplay the current command line
if the switch suddenly sends a
message to your screen.
1. The arrow keys function only on ANSI-compatible terminals such as VT100s.
Editing Command Lines that Wrap
You can use a wraparound feature for commands that extend beyond a single line on the screen. When
the cursor reaches the right margin, the command line shifts ten spaces to the left. You cannot see the
first ten characters of the line, but you can scroll back and check the syntax at the beginning of the
command. The keystroke actions are optional.
To scroll back to the beginning of the command entry, press Ctrl-B or the left arrow key repeatedly. You
can also press Ctrl-A to immediately move to the beginning of the line.
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)#
Switch(config)#
Switch(config)#
Switch(config)#
access-list 101 permit tcp 131.108.2.5 255.255.255.0 131.108.1
$ 101 permit tcp 131.108.2.5 255.255.255.0 131.108.1.20 255.25
$t tcp 131.108.2.5 255.255.255.0 131.108.1.20 255.255.255.0 eq
$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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
2-9
Chapter 2
Using the Command-Line Interface
Searching and Filtering Output of show and more Commands
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-8.
Searching and Filtering Output of show and more Commands
You can search and filter the output for show and more commands. This is useful when you need to sort
through large amounts of output or if you want to exclude output that you do not need to see. Using these
commands is optional.
To use this functionality, enter a show or more command followed by the pipe character (|), one of the
keywords begin, include, or exclude, and an expression that you want to search for or filter out:
command | {begin | include | exclude} regular-expression
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output appear.
This example shows how to include in the output display only lines where the expression protocol
appears:
Switch# show interfaces | include protocol
Vlan1 is up, line protocol is up
Vlan10 is up, line protocol is down
GigabitEthernet1/0/1 is up, line protocol is down
GigabitEthernet1/0/2 is up, line protocol is up
Accessing the CLI
You can access the CLI through a console connection, through Telnet, or by using the browser.
You manage the switch stack and the stack member interfaces through the stack master. You cannot
manage stack members on an individual switch basis. You can connect to the stack master through the
console port or the Ethernet management port of one or more stack members. Be careful with using
multiple CLI sessions to the stack master. Commands you enter in one session are not displayed in the
other sessions. Therefore, it is possible to lose track of the session from which you entered commands.
Note
We recommend using one CLI session when managing the switch stack.
If you want to configure a specific stack member port, you must include the stack member number in the
CLI command interface notation. For more information about interface notations, see the Using
Interface Configuration Mode section on page 10-7.
To debug a specific stack member, you can access it from the stack master by using the session
stack-member-number privileged EXEC command. The stack member number is appended to the system
prompt. For example, Switch-2# is the prompt in privileged EXEC mode for stack member 2, and where
the system prompt for the stack master is Switch. Only the show and debug commands are available in
a CLI session to a specific stack member.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
2-10
OL-12189-01
Chapter 2
Using the Command-Line Interface
Accessing the CLI
Accessing the CLI through a Console Connection or through Telnet
Before you can access the CLI, you must connect a terminal or a PC to the switch console or connect a
PC to the Ethernet management port and then power on the switch, as described in the hardware
installation guide that shipped with your switch. Then, to understand the boot up process and the options
available for assigning IP information, see Chapter 3, Assigning the Switch IP Address and Default
Gateway.
If your switch is already configured, you can access the CLI through a local console connection or
through a remote Telnet session, but your switch must first be configured for this type of access. For
more information, see the Setting a Telnet Password for a Terminal Line section on page 7-6.
You can use one of these methods to establish a connection with the switch:
Connect the switch console port to a management station or dial-up modem, or connect the Ethernet
management port to a PC. For information about connecting to the console or Ethernet management
port, see the switch hardware installation guide.
Use any Telnet TCP/IP or encrypted Secure Shell (SSH) package from a remote management
station. The switch must have network connectivity with the Telnet or SSH client, and the switch
must have an enable secret password configured.
For information about configuring the switch for Telnet access, see the Setting a Telnet Password
for a Terminal Line section on page 7-6. The switch supports up to 16 simultaneous Telnet sessions.
Changes made by one Telnet user are reflected in all other Telnet sessions.
For information about configuring the switch for SSH, see the Configuring the Switch for Secure
Shell section on page 7-37. The switch supports up to five simultaneous secure SSH sessions.
After you connect through the console port, through the Ethernet management port, through a Telnet
session or through an SSH session, the user EXEC prompt appears on the management station.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
2-11
Chapter 2
Using the Command-Line Interface
Accessing the CLI
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
2-12
OL-12189-01
CH A P T E R
Assigning the Switch IP Address and Default
Gateway
This chapter describes how to create the initial switch configuration (for example, assigning the IP
address and default gateway information) by using a variety of automatic and manual methods. It also
describes how to modify the switch startup configuration. Unless otherwise noted, the term switch refers
to a standalone switch and to a switch stack.
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 IP Command Reference, Volume 1 of 3: Addressing and
Services, Release 12.2.
This chapter consists of these sections:
Note
Understanding the Boot Process, page 3-1
Assigning Switch Information, page 3-2
Configuring Protected Mode, page 3-15
Checking and Saving the Running Configuration, page 3-17
Modifying the Startup Configuration, page 3-18
Scheduling a Reload of the Software Image, page 3-23
Information in this chapter about configuring IP addresses and DHCP is specific to IP Version 4 (IPv4).
If you plan to enable IP Version 6 (IPv6) forwarding on your switch, see Chapter 39, Configuring IPv6
Host Functions and Unicast Routing for information specific to IPv6 address format and configuration.
To enable IPv6, the stack or switch must be running the advanced IP services feature set.
Understanding the Boot Process
To start your switch, you need to follow the procedures in the hardware installation guide for installing
and powering on the switch and setting up the initial switch configuration (IP address, subnet mask,
default gateway, secret and Telnet passwords, and so forth).
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
3-1
Chapter 3
Assigning the Switch IP Address and Default Gateway
Assigning Switch Information
The normal boot process involves the operation of the boot loader software, which performs these
activities:
Performs low-level CPU initialization. It initializes the CPU registers, which control where physical
memory is mapped, its quantity, its speed, and so forth.
Performs power-on self-test (POST) for the CPU subsystem. It tests the CPU DRAM and the portion
of the flash device that makes up the flash file system.
Initializes the flash file system on the system board.
Loads a default operating system software image into memory and boots up the switch.
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 start 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 a Software Failure section on
page 47-2 and the Recovering from a Lost or Forgotten Password section on page 47-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 or a PC to the Ethernet management port, and make sure you have 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.
Stop bits default is 1.
Parity settings default is none.
Assigning Switch Information
You can assign IP information through the Advanced Management Module (AMM) GUI or manually.
If the switch reboots, it uses the IP address, subnet mask, and gateway in the saved configuration file.
The switch stack is managed through a single IP address. The IP address is a system-level setting and is
not specific to the stack master or to any other stack member. You can still manage the stack through the
same IP address even if you remove the stack master or any other stack member from the stack, provided
there is IP connectivity.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
3-2
OL-12189-01
Chapter 3
Assigning the Switch IP Address and Default Gateway
Assigning Switch Information
Note
Stack members retain their IP address when you remove them from a switch stack. To avoid a conflict
by having two devices with the same IP address in your network, change the IP address of the switch
that you removed from the switch stack.
Use a DHCP server for centralized control and automatic assignment of IP information after the server
is configured.
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.
These sections contain this configuration information:
Default Switch Information, page 3-3
Understanding DHCP-Based Autoconfiguration, page 3-3
Configuring DHCP-Based Autoconfiguration, page 3-5
Understanding DHCP-based Autoconfiguration and Image Update, page 3-10
Configuring the DHCP Auto Configuration and Image Update Features, page 3-11
Manually Assigning IP Information, page 3-14
Default Switch Information
Table 3-1 shows the default switch information.
Table 3-1
Default Switch Information
Feature
Default Setting
DCHP client
Disabled.
IP address and subnet mask
No IP address or subnet mask are defined.
Default gateway
No default gateway is defined.
Enable secret password
No password is defined.
Hostname
The factory-assigned default hostname is Switch.
Telnet password
No password is defined.
Understanding DHCP-Based Autoconfiguration
DHCP provides configuration information to Internet hosts and internetworking devices. This protocol
consists of two components: one for delivering configuration parameters from a DHCP server to a device
and a mechanism for allocating network addresses to devices. DHCP is built on a client-server model,
in which designated DHCP servers allocate network addresses and deliver configuration parameters to
dynamically configured devices. The switch can act as both a DHCP client and a DHCP server.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
3-3
Chapter 3
Assigning the Switch IP Address and Default Gateway
Assigning Switch Information
During DHCP-based autoconfiguration, your switch (DHCP client) is automatically configured at
startup with IP address information and a configuration file.
With DHCP-based autoconfiguration, no DHCP client-side configuration is needed on your switch.
However, you need to configure the DHCP server for various lease options associated with IP addresses.
If you are using DHCP to relay the configuration file location on the network, you might also need to
configure a Trivial File Transfer Protocol (TFTP) server and a Domain Name System (DNS) server.
Note
We recommend a redundant connection between a switch stack and the DHCP, DNS, and TFTP servers.
This is to help ensure that these servers remain accessible in case one of the connected stack members
is removed from the switch stack.
The DHCP server for your switch can be on the same LAN or on a different LAN than the switch. If the
DHCP server is running on a different LAN, you should configure a DHCP relay device between your
switch and the DHCP server. A relay device forwards broadcast traffic between two directly connected
LANs. A router does not forward broadcast packets, but it forwards packets based on the destination IP
address in the received packet.
DHCP-based autoconfiguration replaces the BOOTP client functionality on your switch.
DHCP Client Request Process
When you boot up your switch, the DHCP client is invoked and requests configuration information from
a DHCP server when the configuration file is not present on the switch. If the configuration file is present
and the configuration includes the ip address dhcp interface configuration command on specific routed
interfaces, the DHCP client is invoked and requests the IP address information for those interfaces.
Figure 3-1 shows the sequence of messages that are exchanged between the DHCP client and the DHCP
server.
Figure 3-1
DHCP Client and Server Message Exchange
DHCPDISCOVER (broadcast)
Switch A
DHCPOFFER (unicast)
DHCP server
DHCPACK (unicast)
51807
DHCPREQUEST (broadcast)
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 TFTP
Server section on page 3-6.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
3-4
OL-12189-01
Chapter 3
Assigning the Switch IP Address and Default Gateway
Assigning Switch Information
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.
Configuring DHCP-Based Autoconfiguration
These sections contain this configuration information:
DHCP Server Configuration Guidelines, page 3-5
Configuring the TFTP Server, page 3-6
Configuring the DNS, page 3-6
Configuring the Relay Device, page 3-7
Obtaining Configuration Files, page 3-7
Example Configuration, page 3-8
If your DHCP server is a Cisco device, see the Configuring DHCP section of the IP Addressing and
Services section of the Cisco IOS IP Configuration Guide, Release 12.2 for additional information
about configuring DHCP.
DHCP Server Configuration Guidelines
Follow these guidelines if you are configuring a device as a DHCP server:
You should configure the DHCP server with reserved leases that are bound to each switch by the switch
hardware address.
If you want the switch to receive IP address information, you must configure the DHCP server with these
lease options:
IP address of the client (required)
Subnet mask of the client (required)
DNS server IP address (optional)
Router IP address (default gateway address to be used by the switch) (required)
If you want the switch to receive the configuration file from a TFTP server, you must configure the
DHCP server with these lease options:
TFTP server name (required)
Boot filename (the name of the configuration file that the client needs) (recommended)
Hostname (optional)
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
3-5
Chapter 3
Assigning the Switch IP Address and Default Gateway
Assigning Switch Information
Depending on the settings of the DHCP server, the switch can receive IP address information, the
configuration file, or both.
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.
Configuring the TFTP Server
Based on the DHCP server configuration, the switch attempts to download one or more configuration
files from the TFTP server. If you configured the DHCP server to respond to the switch with all the
options required for IP connectivity to the TFTP server, and if you configured the DHCP server with a
TFTP server name, address, and configuration filename, the switch attempts to download the specified
configuration file from the specified TFTP server.
If you did not specify the configuration filename, the TFTP server, or if the configuration file could not
be downloaded, the switch attempts to download a configuration file by using various combinations of
filenames and TFTP server addresses. The files include the specified configuration filename (if any) and
these files: network-config, cisconet.cfg, hostname.config, or hostname.cfg, where hostname is the
switchs current hostname. The TFTP server addresses used include the specified TFTP server address
(if any) and the broadcast address (255.255.255.255).
For the switch to successfully download a configuration file, the TFTP server must contain one or more
configuration files in its base directory. The files can include these files:
The configuration file named in the DHCP reply (the actual switch configuration file).
The network-confg or the cisconet.cfg file (known as the default configuration files).
The router-confg or the ciscortr.cfg file (These files contain commands common to all switches.
Normally, if the DHCP and TFTP servers are properly configured, these files are not accessed.)
If you specify the TFTP server name in the DHCP server-lease database, you must also configure the
TFTP server name-to-IP-address mapping in the DNS-server database.
If the TFTP server to be used is on a different LAN from the switch, or if it is to be accessed by the switch
through the broadcast address (which occurs if the DHCP server response does not contain all the
required information described previously), a relay must be configured to forward the TFTP packets to
the TFTP server. For more information, see the Configuring the Relay Device section on page 3-7. The
preferred solution is to configure the DHCP server with all the required information.
Configuring the DNS
The DHCP server uses the DNS server to resolve the TFTP server name to an IP address. You must
configure the TFTP server name-to-IP address map on the DNS server. The TFTP server contains the
configuration files for the switch.
You can configure the IP addresses of the DNS servers in the lease database of the DHCP server from
where the DHCP replies will retrieve them. You can enter up to two DNS server IP addresses in the lease
database.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
3-6
OL-12189-01
Chapter 3
Assigning the Switch IP Address and Default Gateway
Assigning Switch Information
Configuring the Relay Device
You must configure a relay device, also referred to as a relay agent, when a switch sends broadcast
packets that require a response from a host on a different LAN. Examples of broadcast packets that the
switch might send are DHCP, DNS, and in some cases, TFTP packets. You must configure this relay
device to forward received broadcast packets on an interface to the destination host.
If the relay device is a Cisco router, enable IP routing (ip routing global configuration command), and
configure helper addresses by using the ip helper-address interface configuration command.
For example, in Figure 3-2, configure the router interfaces as follows:
On interface 10.0.0.2:
router(config-if)# ip helper-address 20.0.0.2
router(config-if)# ip helper-address 20.0.0.3
router(config-if)# ip helper-address 20.0.0.4
On interface 20.0.0.1
router(config-if)# ip helper-address 10.0.0.1
Note
If the switch is acting as the relay device, configure the interface as a routed port. For more information,
see the Routed Ports section on page 10-4 and the Configuring Layer 3 Interfaces section on
page 10-20.
Figure 3-2
Relay Device Used in Autoconfiguration
Switch
(DHCP client)
Cisco router
(Relay)
10.0.0.2
10.0.0.1
DHCP server
20.0.0.3
TFTP server
20.0.0.4
DNS server
49068
20.0.0.2
20.0.0.1
Obtaining Configuration Files
Depending on the availability of the IP address and the configuration filename in the DHCP reserved
lease, the switch obtains its configuration information in these ways:
The IP address and the configuration filename is reserved for the switch and provided in the DHCP
reply (one-file read method).
The switch receives its IP address, subnet mask, TFTP server address, and the configuration
filename from the DHCP server. The switch sends a unicast message to the TFTP server to retrieve
the named configuration file from the base directory of the server and upon receipt, it completes its
boot up process.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
3-7
Chapter 3
Assigning the Switch IP Address and Default Gateway
Assigning Switch Information
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, it 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.
Figure 3-3
DHCP-Based Autoconfiguration Network Example
Switch 1
Switch 2
Switch 3
Switch 4
00e0.9f1e.2001 00e0.9f1e.2002 00e0.9f1e.2003 00e0.9f1e.2004
Cisco router
10.0.0.10
DHCP server
10.0.0.2
DNS server
10.0.0.3
TFTP server
(tftpserver)
111394
10.0.0.1
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
3-8
OL-12189-01
Chapter 3
Assigning the Switch IP Address and Default Gateway
Assigning Switch Information
Table 3-2 shows the configuration of the reserved leases on the DHCP server.
Table 3-2
DHCP Server Configuration
Switch A
Switch B
Switch C
Switch D
Binding key (hardware address)
00e0.9f1e.2001
00e0.9f1e.2002
00e0.9f1e.2003
00e0.9f1e.2004
IP address
10.0.0.21
10.0.0.22
10.0.0.23
10.0.0.24
Subnet mask
255.255.255.0
255.255.255.0
255.255.255.0
255.255.255.0
Router address
10.0.0.10
10.0.0.10
10.0.0.10
10.0.0.10
DNS server address
10.0.0.2
10.0.0.2
10.0.0.2
10.0.0.2
TFTP server name
tftpserver or
10.0.0.3
tftpserver or
10.0.0.3
tftpserver or
10.0.0.3
tftpserver or
10.0.0.3
Boot filename (configuration file)
(optional)
switcha-confg
switchb-confg
switchc-confg
switchd-confg
Hostname (optional)
switcha
switchb
switchc
switchd
DNS Server Configuration
The DNS server maps the TFTP server name tftpserver to IP address 10.0.0.3.
TFTP Server Configuration (on UNIX)
The TFTP server base directory is set to /tftpserver/work/. This directory contains the network-confg file
used in the two-file read method. This file contains the hostname to be assigned to the switch based on
its IP address. The base directory also contains a configuration file for each switch (switcha-confg,
switchb-confg, and so forth) as shown in this display:
prompt> cd /tftpserver/work/
prompt> ls
network-confg
switcha-confg
switchb-confg
switchc-confg
switchd-confg
prompt> cat network-confg
ip host switcha 10.0.0.21
ip host switchb 10.0.0.22
ip host switchc 10.0.0.23
ip host switchd 10.0.0.24
DHCP Client Configuration
No configuration file is present on Switch A through Switch D.
Configuration Explanation
In Figure 3-3, Switch A reads its configuration file as follows:
It obtains its IP address 10.0.0.21 from the DHCP server.
If no configuration filename is given in the DHCP server reply, Switch A reads the network-confg
file from the base directory of the TFTP server.
It adds the contents of the network-confg file to its host table.
It reads its host table by indexing its IP address 10.0.0.21 to its hostname (switcha).
It reads the configuration file that corresponds to its hostname; for example, it reads switch1-confg
from the TFTP server.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
3-9
Chapter 3
Assigning the Switch IP Address and Default Gateway
Assigning Switch Information
Switches B through D retrieve their configuration files and IP addresses in the same way.
Understanding DHCP-based Autoconfiguration and Image Update
You can use the DHCP image upgrade features to configure a DHCP server to download both a new
image and a new configuration file to one or more switches in a network. This helps ensure that each
new switch added to a network receives the same image and configuration.
There are two types of DHCP image upgrades: DHCP autoconfiguration and DHCP auto-image update.
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.
DHCP Auto-Image Update
You can use DHCP auto-image upgrade with DHCP autoconfiguration to download both a configuration
and a new image to one or more switches in your network. The switch (or switches) downloading the
new configuration and the new image can be blank (or only have a default factory configuration loaded).
If the new configuration is downloaded to a switch that already has a configuration, the downloaded
configuration is appended to the configuration file stored on the switch. (Any existing configuration is
not overwritten by the downloaded one.)
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-5 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.
Limitations and Restrictions
These are the limitations:
The DHCP-based autoconfiguration with a saved configuration process stops if there is not at least
one Layer 3 interface in an up state without an assigned IP address in the network.
Unless you configure a timeout, the DHCP-based autoconfiguration with a saved configuration
feature tries indefinitely to download an IP address.
The auto-install process stops if a configuration file cannot be downloaded or it the configuration
file is corrupted.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
3-10
OL-12189-01
Chapter 3
Assigning the Switch IP Address and Default Gateway
Assigning Switch Information
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.
Configuring the DHCP Auto Configuration and Image Update Features
When using DHCP to download a new image and a new configuration to a switch, you need to configure
at least two switches:
One switch acts as a DHCP and TFTP server.
The client switch is configured to download either a new configuration file or a new configuration
file and a new image file.
Configuring DHCP Autoconfiguration (Only Configuration File)
Beginning in privileged EXEC mode, follow these steps to configure DHCP autoconfiguration of the
TFTP and DHCP settings on a switch to download a new configuration file.
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
prefix-length
Specify the subnet network number and mask of the DHCP address
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
3-11
Chapter 3
Assigning the Switch IP Address and Default Gateway
Assigning Switch Information
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/17
Switch(config-if)# no switchport
Switch(config-if)# ip address 10.10.10.1 255.255.255.0
Switch(config-if)# end
Configuring DHCP Auto-Image Update (Configuration File and Image)
Beginning in privileged EXEC mode, follow these steps to configure DHCP autoconfiguration to
configure TFTP and DHCP settings on a switch to download a new image and a new configuration file.
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, cbs31x0-universal-tar.122-40.EX2.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
prefix-length
Specify the subnet network number and mask of the DHCP address pool.
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 tarfile 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 imagename 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.
Step 15
no switchport
Put the interface into Layer 3 mode.
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 (/).
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
3-12
OL-12189-01
Chapter 3
Assigning the Switch IP Address and Default Gateway
Assigning Switch Information
Command
Purpose
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# 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)# 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:cbs31x0-universal-mz.122-40.EX2.tar
Switch(config)# tftp-server flash:boot-config.text
Switch(config)# tftp-server flash: autoinstall_dhcp
Switch(config)# interface gigabitethernet1/0/17
Switch(config-if)# no switchport
Switch(config-if)# ip address 10.10.10.1 255.255.255.0
Switch(config-if)# end
Configuring the Client
Beginning in privileged EXEC mode, follow these steps to configure a switch to download a
configuration file and new image from a DHCP server:
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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
3-13
Chapter 3
Assigning the Switch IP Address and Default Gateway
Assigning Switch Information
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.
Manually Assigning IP Information
Before manually assigning the IP address, you need to remember that the AMM acts as the IP proxy for
the switch if the switch IP address and the internal Ethernet management port are in the same subnet as
the AMM. The AMM handles the management traffic.
Beginning in privileged EXEC mode, follow these steps to manually assign IP information to multiple
switched virtual interfaces (SVIs):
Note
If the switch is running the IP services feature set, you can also manually assign IP information to a port
if you first put the port into Layer 3 mode by using the no switchport interface configuration command.
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.
Step 3
ip address dhcp [client-id
interface-name] [hostname host-name]
Get an IP address for the VLAN interface from the DHCP server.
Step 4
ip address ip-address subnet-mask
Enter the IP address and subnet mask.
Step 5
exit
Return to global configuration mode.
Step 6
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
3-14
OL-12189-01
Chapter 3
Assigning the Switch IP Address and Default Gateway
Configuring Protected Mode
Command
Purpose
Step 7
end
Return to privileged EXEC mode.
Step 8
show interfaces vlan vlan-id
Verify the configured IP address.
Step 9
show ip redirects
Verify the configured default gateway.
Step 10
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.
All VLAN interfaces have assigned MAC addresses that are derived from the base MAC address. The
base MAC address is the hardware address that is on the switch label. It also appears when you enter the
show version privileged EXEC command.
On the first VLAN interface (VLAN 1), the MAC address is the base MAC address + 0 x 40. On the next
VLAN interface that you configure, the MAC address is the base MAC address + 0 x 40 +1, and so on
for other VLAN interfaces.
You can enter the show interfaces vlan vlan-id privileged EXEC command to show the MAC and
IP addresses. The MAC addresses that appear in the show interfaces vlan vlan-id command output are
not the same as the MAC address that is printed on the switch label (the base MAC address).
By default, VLAN 1 is the interface that connects to the management network. When the switch boots
up, the DHCP client (switch) requests an IP address from a DHCP server by using the MAC address of
VLAN 1.
For information on setting the switch system name, protecting access to privileged EXEC commands,
and setting time and calendar services, see Chapter 6, Administering the Switch.
Configuring Protected Mode
This section contains this information:
Understanding Protected Mode, page 3-15
Configuration Guidelines and Restrictions, page 3-16
Enabling Protected Mode, page 3-16
Understanding Protected Mode
You can use the protected-mode feature to prevent the Advanced Management Module (AMM) from
controlling the standalone switch. By default, this feature is disabled, and the AMM controls the switch.
When protected mode is enabled, server administrators cannot manage or configure the switch by using
the AMM, and the AMM cannot manage configure these features and functions:
IP addresses
Administration of the external ports
Management of traffic received on the external ports
Prevention of reversion to the manufacturing-default configuration
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
3-15
Chapter 3
Assigning the Switch IP Address and Default Gateway
Configuring Protected Mode
Although you cannot enable protected mode on a stack member, if protected mode is enabled on the
stack master, this feature is enabled on all stack members. Before using protected mode on a switch
stack, consider the feature interactions.
Caution
To prevent physical damage to the switch, if protected mode is enabled and the AMM detects an
overtemperature or overcurrent condition, the AMM can still reboot or power off the switch.
Configuration Guidelines and Restrictions
Follow these guidelines and restrictions when enabling and disabling protected mode:
Before you enter the platform chassis-management protected-mode global configuration
command on the switch, you must enable protected mode on the AMM . For information about
enabling protected mode on the AMM, see the AMM documentation at this URL:
http://www-304.ibm.com/jct01004c/systems/support/supportsite.wss/brandmain?brandind=50000
20
After entering the platform chassis-management protected-mode global configuration command
on the switch, you must reboot the switch so that protected mode is operational.
Protected mode is still enabled on a switch even when it is moved to another enclosure.
Recovering from a lost password requires direct access to the switch through the external serial port.
Enabling Protected Mode
Beginning in privileged EXEC mode, follow these steps to enable protected mode on the switch:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
platform chassis-management
protected-mode
Enable the switch to prevent the AMM from controlling the switch.
Step 3
end
Return to privileged EXEC mode.
Step 4
show platform summary
Verify that protected mode is enabled.
After you reboot the switch, protected mode is operational on the switch.
Step 5
copy running-config startup-config
Step 6
Step 7
Step 8
Save your entries in the configuration file.
(Optional) Reboot the switch.
show platform summary
(Optional) Verify that protected mode is operational.
or
or
show platform chassis {manager
{registers | version | vpd mac-address
length} | summary}
(Optional) Verify the AMM information.
copy running-config startup-config
(Optional) Save your entries in the configuration file.
To disable protected mode, enter the no platform chassis-management protected-mode global
configuration command.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
3-16
OL-12189-01
Chapter 3
Assigning the Switch IP Address and Default Gateway
Checking and Saving the Running Configuration
Checking and Saving the Running Configuration
You can check the configuration settings you entered or changes you made by entering this privileged
EXEC command:
Switch# show running-config
Building configuration...
Current configuration: 1363 bytes
!
version 12.2
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname Stack1
!
enable secret 5 $1$ej9.$DMUvAUnZOAmvmgqBEzIxE0
!
.
<output truncated>
.
interface gigabitethernet6/0/17
no switchport
ip address 172.20.137.50 255.255.255.0
!
interface gigabitethernet6/0/18
mvr type source
<output truncated>
...!
interface VLAN1
ip address 172.20.137.50 255.255.255.0
no ip directed-broadcast
!
ip default-gateway 172.20.137.1 !
!
snmp-server community private RW
snmp-server community public RO
snmp-server community private@es0 RW
snmp-server community public@es0 RO
snmp-server chassis-id 0x12
!
end
To store the configuration or changes you have made to your startup configuration in flash memory, enter
this privileged EXEC command:
Switch# copy running-config startup-config
Destination filename [startup-config]?
Building configuration...
This command saves the configuration settings that you made. If you fail to do this, your configuration
will be lost the next time you reload the system. To display information stored in the NVRAM section
of flash memory, use the show startup-config or more startup-config privileged EXEC command.
For more information about alternative locations from which to copy the configuration file, see
Appendix B, Working with the Cisco IOS File System, Configuration Files, and Software Images.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
3-17
Chapter 3
Assigning the Switch IP Address and Default Gateway
Modifying the Startup Configuration
Modifying the Startup Configuration
These sections describe how to modify the switch startup configuration:
Default Boot Configuration, page 3-18
Automatically Downloading a Configuration File, page 3-18
Booting Manually, page 3-19
Booting a Specific Software Image, page 3-20
Controlling Environment Variables, page 3-21
See also Appendix B, Working with the Cisco IOS File System, Configuration Files, and Software
Images, for information about switch configuration files. See the Switch Stack Configuration Files
section on page 5-16 for information about switch stack configuration files.
Default Boot Configuration
Table 3-3 shows the default boot configuration.
Table 3-3
Default Boot Configuration
Feature
Default Setting
Operating system software image
The switch attempts to automatically boot up the system using information in the
BOOT environment variable. If the variable is not set, the switch attempts to load and
execute the first executable image it can by performing a recursive, depth-first search
throughout the flash file system.
The Cisco IOS image is stored in a directory that has the same name as the image file
(excluding the .bin extension).
In a depth-first search of a directory, each encountered subdirectory is completely
searched before continuing the search in the original directory.
Configuration file
Configured switches use the config.text file stored on the system board in flash
memory.
A new switch has no configuration file.
Automatically Downloading a Configuration File
You can automatically download a configuration file to your switch by using the DHCP-based
autoconfiguration feature. For more information, see the Understanding DHCP-Based
Autoconfiguration section on page 3-3.
Specifying the Filename to Read and Write the System Configuration
By default, the Cisco IOS software uses the file config.text to read and write a nonvolatile copy of the
system configuration. However, you can specify a different filename, which will be loaded during the
next boot cycle.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
3-18
OL-12189-01
Chapter 3
Assigning the Switch IP Address and Default Gateway
Modifying the Startup Configuration
Note
This command only works properly from a standalone switch.
Beginning in privileged EXEC mode, follow these steps to specify a different configuration filename:
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 up; however, you can configure it to manually boot up.
Note
This command only works properly from a standalone switch.
Beginning in privileged EXEC mode, follow these steps to configure the switch to manually boot up
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 up during the next boot cycle.
Step 3
end
Return to privileged EXEC mode.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
3-19
Chapter 3
Assigning the Switch IP Address and Default Gateway
Modifying the Startup Configuration
Step 4
Command
Purpose
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 up 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.
Booting a Specific Software Image
By default, the switch attempts to automatically boot up the system using information in the BOOT
environment variable. If this variable is not set, the switch attempts to load and execute the first
executable image it can by performing a recursive, depth-first search throughout the flash file system. In
a depth-first search of a directory, each encountered subdirectory is completely searched before
continuing the search in the original directory. However, you can specify a specific image to boot up.
Beginning in privileged EXEC mode, follow these steps to configure the switch to boot up a specific
image during the next boot cycle:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
boot system filesystem:/file-url
Configure the switch to boot up 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.
If you enter this command on a stack master, the specified software image
is loaded only on the stack master during the next boot cycle.
Filenames and directory names are case sensitive.
Step 3
Step 4
boot system switch {number | all}
end
(Optional) Specify the switch members on which the system image is
loaded during the next boot cycle:
Use number to specify a stack member.
Use all to specify all stack members.
Return to privileged EXEC mode.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
3-20
OL-12189-01
Chapter 3
Assigning the Switch IP Address and Default Gateway
Modifying the Startup Configuration
Step 5
Command
Purpose
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 up the
system using information in the BOOT environment variable.
Step 6
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.
Controlling Environment Variables
With a normally operating switch, you enter the boot loader mode only through a switch console
connection configured for 9600 b/s by performing these tasks:
1.
Power off the switch by using the Advanced Management Module (AMM) GUI or by removing the
switch from the enclosure.
2.
Power on the switch by using the GUI or re-inserting the switch in the enclosure.
3.
Press the switch Mode button while powering on the switch.
You can release the Mode button a second or two after the LED above port 1 turns off. Then the boot
loader switch: prompt appears.
The switch boot loader software provides support for nonvolatile environment variables, which can be
used to control how the boot loader, or any other software running on the system, behaves. Boot loader
environment variables are similar to environment variables that can be set on UNIX or DOS systems.
Environment variables that have values are stored in flash memory outside of the flash file system.
Each line in these files contains an environment variable name and an equal sign followed by the value
of the variable. A variable has no value if it is not listed in this file; it has a value if it is listed in the file
even if the value is a null string. A variable that is set to a null string (for example, ) is a variable with
a value. Many environment variables are predefined and have default values.
Environment variables store two kinds of data:
Data that controls code, which does not read the Cisco IOS configuration file. For example, the name
of a boot loader helper file, which extends or patches the functionality of the boot loader can be
stored as an environment variable.
Data that controls code, which is responsible for reading the Cisco IOS configuration file. For
example, the name of the Cisco IOS configuration file can be stored as an environment variable.
You can change the settings of the environment variables by accessing the boot loader or by using Cisco
IOS commands. Under normal circumstances, it is not necessary to alter the setting of the environment
variables.
Note
For complete syntax and usage information for the boot loader commands and environment variables,
see the command reference for this release.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
3-21
Chapter 3
Assigning the Switch IP Address and Default Gateway
Modifying the Startup Configuration
Table 3-4 describes the function of the most common environment variables.
Table 3-4
Environment Variables
Variable
Boot Loader Command
Cisco IOS Global Configuration Command
BOOT
set BOOT filesystem:/file-url ...
boot system {filesystem:/file-url ...| switch
{number | all}}
A semicolon-separated list of executable files
to try to load and execute when automatically
booting. If the BOOT environment variable is
not set, the system attempts to load and execute
the first executable image it can find by using a
recursive, depth-first search through the flash
file system. If the BOOT variable is set but the
specified images cannot be loaded, the system
attempts to boot up the first bootable file that it
can find in the flash file system.
MANUAL_BOOT
set MANUAL_BOOT yes
boot manual
Decides whether the switch automatically or
manually boots.
Enables manually booting the switch during the
next boot cycle and changes the setting of the
MANUAL_BOOT environment variable.
Valid values are 1, yes, 0, and no. If it is set to
no or 0, the boot loader attempts to
automatically boot up the system. If it is set to
anything else, you must manually boot up the
switch from the boot loader mode.
CONFIG_FILE
Specifies the Cisco IOS image to load during the
next boot cycle and the stack members on which
the image is loaded. This command changes the
setting of the BOOT environment variable.
set CONFIG_FILE flash:/file-url
The next time you reboot the system, the switch is
in boot loader mode. To boot up the system, use
the boot flash:filesystem:/file-url boot loader
command, and specify the name of the bootable
image.
boot config-file flash:/file-url
Specifies the filename that Cisco IOS uses to read
Changes the filename that Cisco IOS uses to
read and write a nonvolatile copy of the system and write a nonvolatile copy of the system
configuration. This command changes the
configuration.
CONFIG_FILE environment variable.
SWITCH_NUMBER
set SWITCH_NUMBER
stack-member-number
switch current-stack-member-number renumber
new-stack-member-number
Changes the member number of a stack
member.
Note
SWITCH_PRIORITY set SWITCH_PRIORITY
stack-member-number
Changes the priority value of a stack member.
Changes the member number of a stack
member.
switch stack-member-number priority
priority-number
Note
Changes the priority value of a stack
member.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
3-22
OL-12189-01
Chapter 3
Assigning the Switch IP Address and Default Gateway
Scheduling a Reload of the Software Image
When the switch is connected to a PC through the internal Ethernet management port, you can download
or upload a configuration file to the boot loader by using TFTP. Make sure the environment variables in
Table 3-5 are configured.
Table 3-5
Environment Variables for TFTP
Variable
Description
MAC_ADDR
Specifies the MAC address of the switch.
Note
We recommend that you do not modify this variable.
However, if you modify this variable after the boot loader is up or the value
is different than the saved value, enter this command before using TFTP.
IP_ADDR
Specifies the IP address and the subnet mask for the associated IP subnet of
the switch.
DEFAULT_ROUTER
Specifies the IP address and subnet mask of the default gateway.
Scheduling a Reload of the Software Image
You can schedule a reload of the software image to occur on the switch at a later time (for example, late
at night or during the weekend when the switch is used less), or you can synchronize a reload
network-wide (for example, to perform a software upgrade on all switches in the network).
Note
A scheduled reload must take place within approximately 24 days.
Configuring a Scheduled Reload
To configure your switch to reload the software image at a later time, use one of these commands in
privileged EXEC mode:
reload in [hh:]mm [text]
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.
To reload a specific switch in a switch stack, use the reload slot stack-member-number privileged
EXEC command.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
3-23
Chapter 3
Assigning the Switch IP Address and Default Gateway
Scheduling a Reload of the Software Image
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 bootup, 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 users
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 1996 (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 1996 (in 344 hours and 53 minutes)
Proceed with reload? [confirm]
To cancel a previously scheduled reload, use the reload cancel privileged EXEC command.
Displaying Scheduled Reload Information
To display information about a previously scheduled reload or to find out if a reload has been scheduled
on the switch, use the show reload privileged EXEC command.
It displays reload information including the time the reload is scheduled to occur and the reason for the
reload (if it was specified when the reload was scheduled).
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
3-24
OL-12189-01
CH A P T E R
Configuring Cisco IOS CNS Agents
This chapter describes how to configure the Cisco IOS Cisco Network Services (CNS) agents on the
switch. Unless otherwise noted, the term switch refers to a standalone switch and to a switch stack.
Note
For complete configuration information for the Cisco Configuration Engine, see this URL on Cisco.com
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, see the Cisco IOS
Network Management Command Reference, Release 12.4 at this URL on Cisco.com:
http://www.cisco.com/en/US/products/ps6350/products_command_reference_book09186a008042df72.
html
This chapter consists of these sections:
Understanding Cisco Configuration Engine Software, page 4-1
Understanding Cisco IOS Agents, page 4-5
Configuring Cisco IOS Agents, page 4-6
Displaying CNS Configuration, page 4-14
Understanding Cisco Configuration Engine Software
The Cisco Configuration Engine is network management software that acts as a configuration service
for automating the deployment and management of network devices and services (see Figure 4-1). Each
Configuration Engine manages a group of Cisco devices (switches and routers) and the services that they
deliver, storing their configurations and delivering them as needed. The Configuration Engine automates
initial configurations and configuration updates by generating device-specific configuration changes,
sending them to the device, executing the configuration change, and logging the results.
The Configuration Engine supports standalone and server modes and has these CNS components:
Configuration service (web server, file manager, and namespace mapping server)
Event service (event gateway)
Data service directory (data models and schema)
In standalone mode, the Configuration Engine supports an embedded Directory Service. In this mode,
no external directory or other data store is required. In server mode, the Configuration Engine supports
the use of a user-defined external directory.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
4-1
Chapter 4
Configuring Cisco IOS CNS Agents
Understanding Cisco Configuration Engine Software
Figure 4-1
Configuration Engine Architectural Overview
Service provider network
Configuration
engine
Data service
directory
Configuration server
Event service
141327
Web-based
user interface
Order entry
configuration management
These sections contain this conceptual information:
Configuration Service, page 4-2
Event Service, page 4-3
What You Should Know About the CNS IDs and Device Hostnames, page 4-3
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
4-2
OL-12189-01
Chapter 4
Configuring Cisco IOS CNS Agents
Understanding Cisco Configuration Engine Software
Event Service
The 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
4-3
Chapter 4
Configuring Cisco IOS CNS Agents
Understanding Cisco Configuration Engine Software
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.
Hostname and DeviceID
The DeviceID is fixed at the time of the connection to the event gateway and does not change even when
the switch hostname is reconfigured.
When changing the switch hostname on the switch, the only way to refresh the DeviceID is to break the
connection between the switch and the event gateway. Enter the no cns event global configuration
command followed by the cns event global configuration command.
When the connection is re-established, the switch sends its modified hostname to the event gateway. The
event gateway redefines the DeviceID to the new value.
Caution
When using the Configuration Engine user interface, you must first set the DeviceID field to the
hostname value that the switch acquires afternot beforeyou use the cns config initial global
configuration command at the switch. Otherwise, subsequent cns config partial global configuration
command operations malfunction.
Using Hostname, DeviceID, and ConfigID
In standalone mode, when a hostname value is set for a switch, the configuration server uses the
hostname as the DeviceID when an event is sent on hostname. If the hostname has not been set, the event
is sent on the cn=<value> of the device.
In server mode, the hostname is not used. In this mode, the unique DeviceID attribute is always used for
sending an event on the bus. If this attribute is not set, you cannot update the switch.
These and other associated attributes (tag value pairs) are set when you run Setup on the Configuration
Engine.
Note
For more information about running the setup program on the Configuration Engine, see the
Configuration Engine setup and configuration guide at this URL on Cisco.com:
http://www.cisco.com/en/US/products/sw/netmgtsw/ps4617/prod_installation_guides_list.html
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
4-4
OL-12189-01
Chapter 4
Configuring Cisco IOS CNS Agents
Understanding Cisco IOS Agents
Understanding Cisco IOS Agents
The CNS event agent feature allows the switch to publish and subscribe to events on the event bus and
works with the Cisco IOS agent. The Cisco IOS agent feature supports the switch by providing these
features:
Initial Configuration, page 4-5
Incremental (Partial) Configuration, page 4-6
Synchronized Configuration, page 4-6
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.
Figure 4-2
Initial Configuration Overview
TFTP
server
Configuration
Engine
WAN
DHCP
server
Access layer
switches
DHCP relay agent
default gateway
141328
Distribution layer
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
4-5
Chapter 4
Configuring Cisco IOS CNS Agents
Configuring Cisco IOS Agents
Incremental (Partial) Configuration
After the network is running, new services can be added by using the Cisco IOS agent. Incremental
(partial) configurations can be sent to the switch. The actual configuration can be sent as an event
payload by way of the event gateway (push operation) or as a signal event that triggers the switch to
initiate a pull operation.
The switch can check the syntax of the configuration before applying it. If the syntax is correct, the
switch applies the incremental configuration and publishes an event that signals success to the
configuration server. If the switch does not apply the incremental configuration, it publishes an event
showing an error status. When the switch has applied the incremental configuration, it can write it to
NVRAM or wait until signaled to do so.
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.
Configuring Cisco IOS Agents
The Cisco IOS agents embedded in the switch Cisco IOS software allow the switch to be connected and
automatically configured as described in the Enabling Automated CNS Configuration section on
page 4-6. If you want to change the configuration or install a custom configuration, see these sections
for instructions:
Enabling the CNS Event Agent, page 4-7
Enabling the Cisco IOS CNS Agent, page 4-9
Enabling Automated CNS Configuration
To enable automated CNS configuration of the switch, you must first complete the prerequisites in
Table 4-1. When you complete them, power on the switch. At the setup prompt, do nothing: The switch
begins the initial configuration as described in the Initial Configuration section on page 4-5. When the
full configuration file is loaded on your switch, you need to do nothing else.
Table 4-1
Prerequisites for Enabling Automatic Configuration
Device
Required Configuration
Access switch
Factory default (no configuration file)
Distribution switch
IP helper address
Enable DHCP relay agent
IP routing (if used as default gateway)
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
4-6
OL-12189-01
Chapter 4
Configuring Cisco IOS CNS Agents
Configuring Cisco IOS Agents
Table 4-1
Prerequisites for Enabling Automatic Configuration (continued)
Device
Required Configuration
DHCP server
TFTP server
CNS Configuration Engine
Note
IP address assignment
TFTP server IP address
Path to bootstrap configuration file on the TFTP server
Default gateway IP address
A bootstrap configuration file that includes the CNS
configuration commands that enable the switch to
communicate with the Configuration Engine
The switch configured to use either the switch MAC address
or the serial number (instead of the default hostname) to
generate the ConfigID and EventID
The CNS event agent configured to push the configuration file
to the switch
One or more templates for each type of device, with the ConfigID
of the device mapped to the template.
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 this URL:
http://www.cisco.com/en/US/products/sw/netmgtsw/ps4617/products_installation_and_configuration_
guide_book09186a00803b59db.html
Enabling the CNS Event Agent
Note
You must enable the CNS event agent on the switch before you enable the CNS configuration agent.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
4-7
Chapter 4
Configuring Cisco IOS CNS Agents
Configuring Cisco IOS Agents
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]
[backup] [failover-time seconds] [keepalive seconds
retry-count] [reconnect time] [source ip-address]
Enable the event agent, and enter the gateway parameters.
For {hostname | ip-address}, enter either the
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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
4-8
OL-12189-01
Chapter 4
Configuring Cisco IOS CNS Agents
Configuring Cisco IOS Agents
Enabling the Cisco IOS CNS Agent
After enabling the CNS event agent, start the Cisco IOS CNS agent on the switch. You can enable the
Cisco IOS agent with these commands:
The cns config initial global configuration command enables the Cisco IOS agent and initiates an
initial configuration on the switch.
The cns config partial global configuration command enables the Cisco IOS agent and initiates a
partial configuration on the switch. You can then use the Configuration Engine to remotely send
incremental configurations to the switch.
Enabling an Initial Configuration
Beginning in privileged EXEC mode, follow these steps to enable the CNS configuration agent and
initiate an initial configuration on the switch:
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
seconds] [sleep seconds] [timeout seconds]
Enter CNS connect configuration mode, specify the name
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 0 to tbd seconds. The default is 120.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
4-9
Chapter 4
Configuring Cisco IOS CNS Agents
Configuring Cisco IOS Agents
Step 7
Command
Purpose
discover {controller controller-type | dlci
[subinterface subinterface-number] | interface
[interface-type] | line line-type}
Specify the interface parameters in the CNS connect
profile.
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.
Step 8
template name [ ... name]
Step 9
For interface [interface-type], enter the type of
interface.
For line line-type, enter the line type.
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.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
4-10
OL-12189-01
Chapter 4
Configuring Cisco IOS CNS Agents
Configuring Cisco IOS Agents
Step 13
Command
Purpose
cns id interface num {dns-reverse | ipaddress |
mac-address} [event] [image]
(Optional) Set the unique EventID or ConfigID used by the
Configuration Engine.
or
For interface num, enter the type of interfacefor
example, ethernet, group-async, loopback, or
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.
cns id {hardware-serial | hostname | string string |
udi} [event] [image]
Note
If both the event and image keywords are omitted,
the image-id value is used to identify the switch.
For {hardware-serial | hostname| string string |
udi}, enter hardware-serial to set the switch serial
number as the unique ID, enter hostname (the default)
to select the switch hostname as the unique ID, enter
an arbitrary text string for string string as the unique
ID, or enter udi to set the unique device identifier
(UDI) as the unique ID.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
4-11
Chapter 4
Configuring Cisco IOS CNS Agents
Configuring Cisco IOS Agents
Step 14
Command
Purpose
cns config initial {hostname | ip-address}
[port-number] [event] [no-persist] [page page]
[source ip-address] [syntax-check]
Enable the Cisco IOS agent, and initiate an initial
configuration.
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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
4-12
OL-12189-01
Chapter 4
Configuring Cisco IOS CNS Agents
Configuring Cisco IOS Agents
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
Enabling a Partial Configuration
Beginning in privileged EXEC mode, follow these steps to enable the Cisco IOS agent and to initiate a
partial configuration on the switch:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
cns config partial {ip-address | hostname}
[port-number] [source ip-address]
Enable the configuration agent, and initiate a partial
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
or
show cns config outstanding
Verify information about the configuration 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 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
4-13
Chapter 4
Configuring Cisco IOS CNS Agents
Displaying CNS Configuration
Displaying CNS Configuration
You can use the privileged EXEC commands in Table 4-2 to display CNS configuration information.
Table 4-2
Displaying CNS Configuration
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
4-14
OL-12189-01
CH A P T E R
Managing Switch Stacks
This chapter provides the concepts and procedures to manage switch stacks.
Note
For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
This chapter consists of these sections:
Understanding Switch Stacks, page 5-1
Configuring the Switch Stack, page 5-21
Accessing the CLI of a Specific Stack Member, page 5-26
Displaying Switch Stack Information, page 5-27
For other switch stack-related information, such as cabling the switches through their StackWise Plus
ports and using the LEDs to display switch stack status, see the hardware installation guide.
Caution
TheCatalyst Switch Module 3110 does not support switch stacks with different types of blade switches
as members. Combining the Catalyst Switch Module 3110 with other types of blade switches in a switch
stack might cause the switch to work improperly or to fail.
Understanding Switch Stacks
A switch stack is a set of up to nine stacking-capable switches connected through their StackWise Plus
ports.
One of the switches controls the operation of the stack and is called the stack master. The stack master
and the other switches in the stack are all stack members. The stack members use the Cisco StackWise
Plus technology to work together as a unified system. Layer 2 and Layer 3 protocols present the entire
switch stack as a single entity to the network. The stack members can be in different enclosures.
The stack master is the single point of stack-wide management. From the stack master, you configure:
System-level (global) features that apply to all stack members
Interface-level features for each stack member
A switch stack is identified in the network by its bridge ID and, if it is operating as a Layer 3 device, its
router MAC address. The bridge ID and router MAC address are determined by the MAC address of the
stack master. Every stack member is identified by its own stack member number.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
5-1
Chapter 5
Managing Switch Stacks
Understanding Switch Stacks
All stack members are eligible to be stack masters. If the stack master becomes unavailable, the
remaining stack members elect a new stack master from among themselves. The switch with the highest
stack member priority value becomes the new stack master.
The system-level features supported on the stack master are supported on the entire switch stack. If a
switch in the stack is running the IP base or IP services feature set and the cryptographic (that is,
supporting encryption) universal software image, we recommend that this switch be the stack master.
Encryption features are unavailable if the stack master is running the IP base or IP services feature set
and the noncryptographic software image.
The stack master contains the saved and running configuration files for the switch stack. The
configuration files include the system-level settings for the switch stack and the interface-level settings
for each stack member. Each stack member has a current copy of these files for back-up purposes.
You manage the switch stack through a single IP address. The IP address is a system-level setting and is
not specific to the stack master or to any other stack member. You can manage the stack through the same
IP address even if you remove the stack master or any other stack member from the stack.
You can use these methods to manage switch stacks:
Network Assistant (available on Cisco.com)
Command-line interface (CLI) over a serial connection to the console port of any stack member or
the Ethernet management port of a stack member
A network management application through the Simple Network Management Protocol (SNMP)
Use SNMP to manage network features across the switch stack that are defined by supported MIBs.
The switch does not support MIBs to manage stacking-specific features such as stack membership
and election.
CiscoWorks network management software
To manage switch stacks, you should understand:
These concepts on how switch stacks are formed:
Switch Stack Membership, page 5-3
Stack Master Election and Re-Election, page 5-6
These concepts on how switch stacks and stack members are configured:
Switch Stack Bridge ID and Router MAC Address, page 5-8
Stack Member Numbers, page 5-8
Stack Member Priority Values, page 5-9
Switch Stack Offline Configuration, page 5-9
Hardware Compatibility and SDM Mismatch Mode in Switch Stacks, page 5-11
Switch Stack Software Compatibility Recommendations, page 5-12
Stack Protocol Version Compatibility, page 5-12
Major Version Number Incompatibility Among Switches, page 5-12
Minor Version Number Incompatibility Among Switches, page 5-12
Incompatible Software and Stack Member Image Upgrades, page 5-16
Switch Stack Configuration Files, page 5-16
Additional Considerations for System-Wide Configuration on Switch Stacks, page 5-17
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
5-2
OL-12189-01
Chapter 5
Managing Switch Stacks
Understanding Switch Stacks
Switch Stack Management Connectivity, page 5-17
Switch Stack Configuration Scenarios, page 5-19
Switch Stack Membership
A switch stack has up to nine stack members connected through their StackWise Plus ports. A switch
stack always has one stack master.
A standalone switch is a switch stack with one stack member that also operates as the stack master. You
can connect one standalone switch to another (Figure 5-1 on page 5-4 and Figure 5-2 on page 5-5) to
create a switch stack containing two stack members, with one of them as the stack master. You can
connect standalone switches to an existing switch stack (Figure 5-3 on page 5-6) to increase the stack
membership.
If you replace a stack member with an identical model, the new switch functions with exactly the same
configuration as the replaced switch, assuming that the new switch is using the same member number as
the replaced switch. For information about the benefits of provisioning a switch stack, see the Switch
Stack Offline Configuration section on page 5-9. For information about replacing a failed switch, see
the Troubleshooting chapter in the hardware installation guide.
The operation of the switch stack continues uninterrupted during membership changes unless you
remove the stack master or you add powered-on standalone switches or switch stacks.
Note
You can power off the switches that you add to or remove from the switch stack.
After adding or removing stack members, make sure that the switch stack is operating at full bandwidth
(64 Gb/s). Press the Mode button on a stack member until the Stack mode LED is on. The last two right
port LEDs on all switches in the stack should be green. Depending on the switch model, the last two
ports are either 10/100/1000 ports or the 10-Gigabit Ethernet port. The stack is not operating at full
bandwidth if
On the Catalyst Switch Module 3110X, one or both of the two LEDs for the 10-Gigabit Ethernet port are
not green. The Stack mode LEDs are the 10-Gigabit Ethernet port LEDs.
On the Catalyst Switch Module 3110G, the LEDs for ports 17 and 18 are not green.
Adding powered-on switches (merging) causes the stack masters of the merging switch stacks to
elect a stack master from among themselves. The re-elected stack master retains its role and
configuration and so do its stack members. All remaining switches, including the former stack
masters, reload and join the switch stack as stack members. They change their stack member
numbers to the lowest available numbers and use the stack configuration of the re-elected stack
master.
Removing powered-on stack members causes the switch stack to divide (partition) into two or more
switch stacks, each with the same configuration. This can cause an IP address configuration conflict
in your network. If you want the switch stacks to remain separate, change the IP address or addresses
of the newly created switch stacks. If you did not intend to partition the switch stack:
a. Power off the switches in the newly created switch stacks.
b. Reconnect them to the original switch stack through their StackWise Plus ports.
c. Power on the switches.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
5-3
Chapter 5
Managing Switch Stacks
Understanding Switch Stacks
For more information about cabling and powering switch stacks, see the Switch Installation chapter in
the hardware installation guide.
Figure 5-1
Creating a Switch Stack from Two Standalone Switches in Two Enclosures
Enclosure 1
Blade switch
Enclosure 2
Blade switch
Stack member 1
Blade switch
Blade switch
Stack member 1
Blade switch
Blade switch
Enclosure 1
Blade switch
Stack member 1
Blade switch
Blade switch
Enclosure 2
Blade switch
Blade switch
Stack member 2
and stack master
202007
Blade switch
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
5-4
OL-12189-01
Chapter 5
Managing Switch Stacks
Understanding Switch Stacks
Figure 5-2
Creating a Switch Stack from Two Standalone Switches in the Same Enclosures
Enclosure
Stack member 1
Blade switch
2
1
Blade switch
Stack member 1
Blade switch
Enclosure
Stack member 1
Blade switch
Blade switch
Stack member 2
and stack master
202008
Blade switch
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
5-5
Chapter 5
Managing Switch Stacks
Understanding Switch Stacks
Figure 5-3
Adding a Standalone Switch to a Switch Stack
Enclosure 1
Stack member 1
and stack master
Blade switch
Blade switch
Enclosure 2
Blade switch
Stack member 2
Blade switch
Blade switch
Stack member 1
Stack member 3
Blade switch
Blade switch
Stack member 1
and stack master
Enclosure 1
Blade switch
Stack member 2
Blade switch
Stack member 3
Blade switch
Enclosure 2
Blade switch
Blade switch
Stack member 4
Advanced Management Module (AMM)
Note
202009
Blade switch
All of the AMMs in the enclosures lose connectivity to the stack members. Only network
administrators can manage the switch.
Internal Ethernet management port
Stack Master Election and Re-Election
The stack master is elected or re-elected based on one of these factors and in the order listed:
1.
The switch that is currently the stack master.
2.
The switch with the highest stack member priority value.
Note
We recommend assigning the highest priority value to the switch that you prefer to be the
stack master. This ensures that the switch is re-elected as stack master if a re-election occurs.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
5-6
OL-12189-01
Chapter 5
Managing Switch Stacks
Understanding Switch Stacks
3.
The switch that is not using the default interface-level configuration.
4.
The switch with the higher priority feature set and software image combination. These combinations
are listed from highest to lowest priority:
Advanced IP services feature set and the cryptographic universal software image
Advanced IP services feature set and the noncryptographic software image
IP services feature set and the cryptographic software image
IP services feature set and the noncryptographic software image
IP base feature set and the cryptographic software image
IP base feature set and the noncryptographic software image
During the stack master switch election, differences in start-up times between the feature sets
determine the stack master. The switch with the shorter start-up time becomes the stack master.
For example, a switch running the IP services feature set and the cryptographic software image has
a higher priority than the switch running the IP base feature set and the noncryptographic image, but
the switch running the IP base feature set becomes the stack master because the other switch takes
10 seconds longer to start. To avoid this problem, upgrade the switch running the IP base feature set
to same feature set and software image as the other switch, or manually start the master switch and
wait at least 8 seconds before starting the new member switch that running the IP base feature set.
5.
The switch with the lowest MAC address.
A stack master retains its role unless one of these events occurs:
The switch stack is reset.*
The stack master is removed from the switch stack.
The stack master is reset or powered off.
The stack master fails.
The switch stack membership is increased by adding powered-on standalone switches or switch
stacks.*
In the events marked by an asterisk (*), the current stack master might be re-elected based on the listed
factors.
When you power on or reset an entire switch stack, some stack members might not participate in the
stack master election. Stack members that are powered on within the same 20-second time frame
participate in the stack master election and have a chance to become the stack master. Stack members
that are powered on after the 20-second time frame do not participate in this initial election and become
stack members. All stack members participate in re-elections. For all powering considerations that affect
stack-master elections, see the Switch Installation chapter in the hardware installation guide.
The new stack master becomes available after a few seconds. In the meantime, the switch stack uses the
forwarding tables in memory to minimize network disruption. The physical interfaces on the other
available stack members are not affected during a new stack master election and reset.
After a new stack master is elected and the previous stack master becomes available, the previous stack
master does not resume its role as stack master.
As described in the hardware installation guide, you can use the Stack Master LED on the switch to see
if the switch is the stack master.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
5-7
Chapter 5
Managing Switch Stacks
Understanding Switch Stacks
Switch Stack Bridge ID and Router MAC Address
The bridge ID and router MAC address identify the switch stack in the network. When the switch stack
initializes, the MAC address of the stack master determines the bridge ID and router MAC address.
If the stack master changes, the MAC address of the new stack master determines the new bridge ID and
router MAC address. However, when the persistent MAC address feature is enabled, the stack MAC
address changes in approximately 4 minutes. During this time period, if the previous stack master rejoins
the stack, the stack continues to use its MAC address as the stack MAC address, even if the switch is
now a stack member and not a stack master. If the previous stack master does not rejoin the stack during
this period, the switch stack takes the MAC address of the new stack master as the stack MAC address.
See Enabling Persistent MAC Address, page 5-22 for more information.
Stack Member Numbers
The stack member number (1 to 9) identifies each member in the switch stack. The member number also
determines the interface-level configuration that a stack member uses. You can display the stack member
number by using the show switch user EXEC command.
A new, out-of-the-box switch (one that has not joined a switch stack or has not been manually assigned
a stack member number) ships with a default stack member number of 1. When it joins a switch stack,
its default stack member number changes to the lowest available member number in the stack.
Stack members in the same switch stack cannot have the same stack member number. Every stack
member, including a standalone switch, retains its member number until you manually change the
number or unless the number is already being used by another member in the stack.
If you manually change the stack member number by using the switch
current-stack-member-number renumber new-stack-member-number global configuration
command, the new number goes into effect after that stack member resets (or after you use the
reload slot stack-member-number privileged EXEC command) and only if that number is not
already assigned to any other members in the stack. For more information, see the Assigning a
Stack Member Number section on page 5-24. Another way to change the stack member number is
by changing the SWITCH_NUMBER environment variable, as explained in the Controlling
Environment Variables section on page 3-21.
If the number is being used by another member in the stack, the switch selects the lowest available
number in the stack.
If you manually change the number of a stack member and no interface-level configuration is
associated with that new member number, that stack member resets to its default configuration. For
more information about stack member numbers and configurations, see the Switch Stack
Configuration Files section on page 5-16.
You cannot use the switch current-stack-member-number renumber new-stack-member-number
global configuration command on a provisioned switch. If you do, the command is rejected.
If you move a stack member to a different switch stack, the stack member retains its number only if
the number is not being used by another member in the stack. If it is being used, the switch selects
the lowest available number in the stack.
If you merge switch stacks, the switches that join the switch stack of a new stack master select the
the lowest available numbers in the stack. For more information about merging switch stacks, see
the Switch Stack Membership section on page 5-3.
As described in the hardware installation guide, you can press Mode button on a stack member and use
the MBR LED to visually determine the stack member number of each stack member.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
5-8
OL-12189-01
Chapter 5
Managing Switch Stacks
Understanding Switch Stacks
Stack Member Priority Values
A higher priority value for a stack member increases its likelihood of being elected stack master and
retaining its stack member number. The priority value can be 1 to 15. The default priority value is 1. You
can display the stack member priority value by using the show switch user EXEC command.
Note
We recommend assigning the highest priority value to the switch that you prefer to be the stack master.
This ensures that the switch is re-elected as stack master.
You can change the priority value for a stack member by using the switch stack-member-number
priority new-priority-value global configuration command. For more information, see the Setting the
Stack Member Priority Value section on page 5-25. Another way to change the member priority value
is by changing the SWITCH_PRIORITY environment variable, as explained in the Controlling
Environment Variables section on page 3-21.
The new priority value takes effect immediately but does not affect the current stack master. The new
priority value helps determine which stack member is elected as the new stack master when the current
stack master or the switch stack resets.
Switch Stack Offline Configuration
You can use the offline configuration feature to provision (to supply a configuration to) a new switch
before it joins the switch stack. You can configure in advance the stack member number, the switch type,
and the interfaces associated with a switch that is not currently part of the stack. The configuration that
you create on the switch stack is called the provisioned configuration. The switch that is added to the
switch stack and that receives this configuration is called the provisioned switch.
You manually create the provisioned configuration through the switch stack-member-number provision
type global configuration command. The provisioned configuration is automatically created when a
switch is added to a switch stack and when no provisioned configuration exists.
When you configure the interfaces associated with a provisioned switch (for example, as part of a
VLAN), the switch stack accepts the configuration, and the information appears in the running
configuration. The interface associated with the provisioned switch is not active, operates as if it is
administratively shut down, and the no shutdown interface configuration command does not return it to
active service. The interface associated with the provisioned switch does not appear in the display of the
specific feature; for example, it does not appear in the show vlan user EXEC command output.
The switch stack retains the provisioned configuration in the running configuration whether or not the
provisioned switch is part of the stack. You can save the provisioned configuration to the startup
configuration file by entering the copy running-config startup-config privileged EXEC command. The
startup configuration file ensures that the switch stack can reload and can use the saved information
whether or not the provisioned switch is part of the switch stack.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
5-9
Chapter 5
Managing Switch Stacks
Understanding Switch Stacks
Effects of Adding a Provisioned Switch to a Switch Stack
When you add a provisioned switch to the switch stack, the stack applies either the provisioned
configuration or the default configuration. Table 5-1 lists the events that occur when the switch stack
compares the provisioned configuration with the provisioned switch.
Table 5-1
Results of Comparing the Provisioned Configuration with the Provisioned Switch
Scenario
Result
The stack member numbers and
the switch types match.
The stack member numbers
match but the switch types do
not match.
1.
If the stack member number of the
provisioned switch matches the stack
member number in the provisioned
configuration on the stack, and
2.
If the switch type of the provisioned switch
matches the switch type in the provisioned
configuration on the stack.
1.
If the stack member number of the
provisioned switch matches the stack
member number in the provisioned
configuration on the stack, but
2.
The switch type of the provisioned switch
does not match the switch type in the
provisioned configuration on the stack.
The stack member number is
not found in the provisioned
configuration.
The switch stack applies the provisioned
configuration to the provisioned switch
and adds it to the stack.
The switch stack applies the default
configuration to the provisioned switch
and adds it to the stack.
The provisioned configuration is changed
to reflect the new information.
The switch stack applies the default
configuration to the provisioned switch
and adds it to the stack.
The provisioned configuration is changed
to reflect the new information.
The stack member number of
the provisioned switch is in
conflict with an existing stack
member.
The stack master assigns a new stack member
number to the provisioned switch.
The switch stack applies the provisioned
configuration to the provisioned switch
The stack member numbers and the switch types and adds it to the stack.
match:
The provisioned configuration is changed
to reflect the new information.
1. If the new stack member number of the
provisioned switch matches the stack
member number in the provisioned
configuration on the stack, and
2.
If the switch type of the provisioned switch
matches the switch type in the provisioned
configuration on the stack.
The stack member numbers match, but the
switch types do not match:
1.
2.
If the stack member number of the
provisioned switch matches the stack
member number in the provisioned
configuration on the stack, but
The switch stack applies the default
configuration to the provisioned switch
and adds it to the stack.
The provisioned configuration is changed
to reflect the new information.
The switch type of the provisioned switch
does not match the switch type in the
provisioned configuration on the stack.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
5-10
OL-12189-01
Chapter 5
Managing Switch Stacks
Understanding Switch Stacks
Table 5-1
Results of Comparing the Provisioned Configuration with the Provisioned Switch (continued)
Scenario
Result
The stack member number of
the provisioned switch is not
found in the provisioned
configuration.
The switch stack applies the default
configuration to the provisioned switch
and adds it to the stack.
If you add a provisioned switch that is a different type than specified in the provisioned configuration to
a powered-down switch stack and then apply power, the switch stack rejects the (now incorrect) switch
stack-member-number provision type global configuration command in the startup configuration file.
However, during stack initialization, the nondefault interface configuration information in the startup
configuration file for the provisioned interfaces (potentially of the wrong type) is executed. Depending
on the differences between the actual switch type and the previously provisioned switch type, some
commands are rejected, and some commands are accepted.
For example, suppose the switch stack is provisioned for a 18-port switch with 14 internal Gigabit
Ethernet 1000BASE-X downlink ports and 4 external 10/100/1000BASE-T Gigabit Ethernet uplink
ports, the configuration is saved, and the stack is powered down. Then a 15-port switch with 14 internal
Gigabit Ethernet 1000BASE-X downlink ports and one external 10-Gigabit Ethernet uplink port is
connected to the switch stack, and the stack is powered up. In this situation, the configuration for
ports 15 to 18 is rejected, and error messages appear during initialization. In addition, any configured
commands that are valid only on the Gigabit Ethernet interfaces are rejects, even for ports 1 to 14.
Note
If the switch stack does not contain a provisioned configuration for a new switch, the switch joins the
stack with the default interface configuration. The switch stack then adds to its running configuration a
switch stack-member-number provision type global configuration command that matches the new
switch.
For configuration information, see the Provisioning a New Member for a Switch Stack section on
page 5-25.
Effects of Replacing a Provisioned Switch in a Switch Stack
When a provisioned switch in a switch stack fails, is removed from the stack, and is replaced with
another switch, the stack applies either the provisioned configuration or the default configuration to it.
The events that occur when the switch stack compares the provisioned configuration with the
provisioned switch are the same as those described in the Effects of Adding a Provisioned Switch to a
Switch Stack section on page 5-10.
Effects of Removing a Provisioned Switch from a Switch Stack
If you remove a provisioned switch from the switch stack, the configuration associated with the removed
stack member remains in the running configuration as provisioned information. To completely remove
the configuration, use the no switch stack-member-number provision global configuration command.
Hardware Compatibility and SDM Mismatch Mode in Switch Stacks
The switch supports only the desktop Switch Database Management (SDM) templates.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
5-11
Chapter 5
Managing Switch Stacks
Understanding Switch Stacks
All stack members use the SDM template configured on the stack master.
Version-mismatch (VM) mode has priority over SDM-mismatch mode. If a VM-mode condition and an
SDM-mismatch mode exist, the switch stack first attempts to resolve the VM-mode condition.
You can use the show switch privileged EXEC command to see if any stack members are in
SDM-mismatch mode.
For more information about SDM templates and SDM-mismatch mode, see Chapter 8, Configuring
SDM Templates.
Switch Stack Software Compatibility Recommendations
To ensure complete compatibility between stack members, use the information in this section and also
in the Hardware Compatibility and SDM Mismatch Mode in Switch Stacks section on page 5-11.
All stack members must run the same Cisco IOS software image and feature set to ensure compatibility
between stack members. For example, all stack members should run the cryptographic universal
software image and have the IP services feature set enabled for Cisco IOS Release 12.2(40)xx or later.
For more information, see the Stack Protocol Version Compatibility section on page 5-12.
Stack Protocol Version Compatibility
Each software image includes a stack protocol version. The stack protocol version has a major version
number and a minor version number (for example 1.4, where 1 is the major version number and 4 is the
minor version number). Both version numbers determine the level of compatibility among the stack
members. You can display the stack protocol version by using the show platform stack-manager all
privileged EXEC command.
Switches with the same Cisco IOS software version have the same stack protocol version. Such switches
are fully compatible, and all features function properly across the switch stack. Switches with the same
Cisco IOS software version as the stack master immediately join the switch stack.
If an incompatibility exists, the fully functional stack members generate a system message that describes
the cause of the incompatibility on the specific stack members. The stack master sends the message to
all stack members. For more information, see the Major Version Number Incompatibility Among
Switches procedure on page 5-12 and the Minor Version Number Incompatibility Among Switches
procedure on page 5-12.
Major Version Number Incompatibility Among Switches
Switches with different major Cisco IOS software versions usually have different stack protocol
versions. Switches with different major version numbers are incompatible and cannot exist in the same
switch stack.
Minor Version Number Incompatibility Among Switches
Switches with the same major version number but with a different minor version number are considered
partially compatible. When connected to a switch stack, a partially compatible switch enters
version-mismatch (VM) mode and cannot join the stack as a fully functioning member. The software
detects the mismatched software and tries to upgrade (or downgrade) the switch in VM mode with the
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
5-12
OL-12189-01
Chapter 5
Managing Switch Stacks
Understanding Switch Stacks
switch stack image or with a tar file image from the switch stack flash memory. The software uses the
automatic upgrade (auto-upgrade) and the automatic advise (auto-advise) features. For more
information, see the Understanding Auto-Upgrade and Auto-Advise section on page 5-13.
To see if there are switches in VM mode, use the show switch user EXEC command. The port LEDs on
switches in VM mode stay off. Pressing the Mode button does not change the LED mode.
You can use the boot auto-download-sw global configuration command to specify a URL pathname for
the master switch to use to get an image in case of version mismatch.
Understanding Auto-Upgrade and Auto-Advise
When the software detects mismatched software and tries to upgrade the switch in VM mode, two
software processes are involved: automatic upgrade and automatic advise.
The automatic upgrade (auto-upgrade) process includes an auto-copy process and an auto-extract
process. By default, auto-upgrade is enabled (the boot auto-copy-sw global configuration command
is enabled). You can disable auto-upgrade by using the no boot auto-copy-sw global configuration
command on the stack master. You can check the status of auto-upgrade by using the show boot
privileged EXEC command and by checking the Auto upgrade line in the display.
Auto-copy automatically copies the software image running on any stack member to the switch
in VM mode to upgrade (auto-upgrade) it. Auto-copy occurs if auto-upgrade is enabled, if there
is enough flash memory in the switch in VM mode, and if the software image running on the
switch stack is suitable for the switch in VM mode.
Note
A switch in VM mode might not run all released software. For example, new switch
hardware is not recognized in earlier versions of software.
Automatic extraction (auto-extract) occurs when the auto-upgrade process cannot find the
appropriate software in the stack to copy to the switch in VM mode. In that case, the auto-extract
process searches all switches in the stack, whether they are in VM mode or not, for the tar file
needed to upgrade the switch stack or the switch in VM mode. The tar file can be in any flash
file system in the switch stack (including the switch in VM mode). If a tar file suitable for the
switch in VM mode is found, the process extracts the file and automatically upgrades that
switch.
The auto-upgrade (auto-copy and auto-extract) processes wait for a few minutes after the
mismatched software is detected before starting.
When the auto-upgrade process is complete, the switch that was in VM mode reloads and joins the
stack as a fully functioning member. If you have both StackWise Plus cables connected during the
reload, network downtime does not occur because the switch stack operates on two rings.
Note
Auto-upgrade performs the upgrade only when the two feature sets are the same type. For
example, it does not automatically upgrade a switch in VM mode from IP services feature set to
IP base feature set (or the reverse) or from cryptographic universal software image to
noncryptographic universal software image (or the reverse).
Automatic advise (auto-advise) occurs when the auto-upgrade process cannot find appropriate stack
member software to copy to the switch in VM mode. This process tells you the command (archive
copy-sw or archive download-sw privileged EXEC command) and the image name (tar filename)
needed to manually upgrade the switch stack or the switch in VM mode. The recommended image
can be the running switch stack image or a tar file in any flash file system in the switch stack
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
5-13
Chapter 5
Managing Switch Stacks
Understanding Switch Stacks
(including the switch in VM mode). If an appropriate image is not found in the stack flash file
systems, the auto-advise process tells you to install new software on the switch stack. Auto-advise
cannot be disabled, and there is no command to check its status.
The auto-advise software does not give suggestions when the switch stack software and the software
of the switch in VM mode do not contain the same feature sets. For example, if the switch stack is
running the IP base image and you add a switch that is running the IP services image, the auto-advise
software does not provide a recommendation. The same events occur when cryptographic and
noncryptographic images are running.
You can use the archive-download-sw /allow-feature-upgrade privileged EXEC command to
allow installing an different software image.
Auto-Upgrade and Auto-Advise Example Messages
When you add a switch that has a different minor version number to the switch stack, the software
displays messages in sequence (assuming that there are no other system messages generated by the
switch).
This example shows that the switch stack detected a new switch that is running a different minor version
number than the switch stack. Auto-copy starts, finds suitable software to copy from a stack member to
the switch in VM mode, upgrades the switch in VM mode, and then reloads it:
*Mar 11 20:31:19.247:%STACKMGR-6-STACK_LINK_CHANGE:Stack Port 2 Switch 2 has changed to
state UP
*Mar 11 20:31:23.232:%STACKMGR-6-SWITCH_ADDED_VM:Switch 1 has been ADDED to the stack
(VERSION_MISMATCH)
*Mar 11 20:31:23.291:%STACKMGR-6-SWITCH_ADDED_VM:Switch 1 has been ADDED to the stack
(VERSION_MISMATCH) (Stack_1-3)
*Mar 11 20:33:23.248:%IMAGEMGR-6-AUTO_COPY_SW_INITIATED:Auto-copy-software process
initiated for switch number(s) 1
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:Searching for stack member to act
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:as software donor...
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:Found donor (system #2) for
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:member(s) 1
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:System software to be uploaded:
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:System Type:
0x00000000
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:archiving
cbs31x0-universal-mz.122-40.xx(directory)
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:archiving
cbs31x0-universal-mz.122-40.xx/cbs31x0-universal-mz.122-40.xx.bin (4945851 bytes)
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:archiving
cbs31x0-universal-mz.122-40.xx/info (450 bytes)
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:archiving info (104 bytes)
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:examining image...
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:extracting info (104 bytes)
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:extracting
cbs31x0-universal-mz.122-40.xxc/info (450 bytes)
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:extracting info (104 bytes)
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:Stacking Version Number:1.4
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:System Type:
0x00000000
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW: Ios Image File Size: 0x004BA200
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW: Total Image File Size:0x00818A00
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW: Minimum Dram required:0x08000000
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW: Image Suffix:ipservices-122-40.xx
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW: Image
Directory:cbs31x0-universal-mz.122-40.xx
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW: Image Name:cbs31x0-universal-mz.122-40.xx
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
5-14
OL-12189-01
Chapter 5
Managing Switch Stacks
Understanding Switch Stacks
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW: Image
Feature:IP|LAYER_3|PLUS|MIN_DRAM_MEG=128
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:Old image for switch
1:flash1:cbs31x0-universal-mz.122-40.xx
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW: Old image will be deleted after download.
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:Extracting images from archive into flash on
switch 1...
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW: cbs31x0-universal-mz.122-0.0.313.xx
(directory)
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:extracting
cbs31x0-universal-mz.122-0.0.313.xx/cbs31x0-universal-mz.122-40.xx (4945851 bytes)
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:extracting
cbs31x0-universal-mz.122-40.xx/info (450 bytes)
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:extracting info (104 bytes)
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:Installing
(renaming):`flash1:update/cbs31x0-universal-mz.122-0.0.313.xx' ->
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:
`flash1:cbs31x0-universal-mz.122-40.xx'
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:New software image installed in
flash1:cbs31x0-i5-mz.122-40.xx
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:Removing old
image:flash1:cbs31x0-universal-mz.122-40.xx
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:All software images installed.
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:Requested system reload in progress...
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:Software successfully copied to
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:system(s) 1
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:Done copying software
*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:Reloading system(s) 1
This example shows that the switch stack detected a new switch that is running a different minor version
number than the switch stack. Auto-copy starts but cannot find software in the switch stack to copy to
the VM-mode switch to make it compatible with the switch stack. The auto-advise process starts and
recommends that you download a tar file from the network to the switch in VM mode:
*Mar 1 00:01:11.319:%STACKMGR-6-STACK_LINK_CHANGE:Stack Port 2 Switch 2 has changed to
state UP
*Mar 1 00:01:15.547:%STACKMGR-6-SWITCH_ADDED_VM:Switch 1 has been ADDED to the stack
(VERSION_MISMATCH)
stack_2#
*Mar 1 00:03:15.554:%IMAGEMGR-6-AUTO_COPY_SW_INITIATED:Auto-copy-software process
initiated for switch number(s) 1
*Mar 1 00:03:15.554:%IMAGEMGR-6-AUTO_COPY_SW:
*Mar 1 00:03:15.554:%IMAGEMGR-6-AUTO_COPY_SW:Searching for stack member to act
*Mar 1 00:03:15.554:%IMAGEMGR-6-AUTO_COPY_SW:as software donor...
*Mar 1 00:03:15.554:%IMAGEMGR-6-AUTO_COPY_SW:Software was not copied
*Mar 1 00:03:15.562:%IMAGEMGR-6-AUTO_ADVISE_SW_INITIATED:Auto-advise-software process
initiated for switch number(s) 1
*Mar 1 00:04:22.537:%IMAGEMGR-6-AUTO_ADVISE_SW:
*Mar 1 00:04:22.537:%IMAGEMGR-6-AUTO_ADVISE_SW:
*Mar 1 00:04:22.537:%IMAGEMGR-6-AUTO_ADVISE_SW:Systems with incompatible software
*Mar 1 00:04:22.537:%IMAGEMGR-6-AUTO_ADVISE_SW:have been added to the stack. The
*Mar 1 00:04:22.537:%IMAGEMGR-6-AUTO_ADVISE_SW:storage devices on all of the stack
*Mar 1 00:04:22.537:%IMAGEMGR-6-AUTO_ADVISE_SW:members have been scanned, and it has
*Mar 1 00:04:22.537:%IMAGEMGR-6-AUTO_ADVISE_SW:been determined that the stack can be
*Mar 1 00:04:22.537:%IMAGEMGR-6-AUTO_ADVISE_SW:repaired by issuing the following
*Mar 1 00:04:22.537:%IMAGEMGR-6-AUTO_ADVISE_SW:command(s):
*Mar 1 00:04:22.537:%IMAGEMGR-6-AUTO_ADVISE_SW:
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
5-15
Chapter 5
Managing Switch Stacks
Understanding Switch Stacks
*Mar 1 00:04:22.537:%IMAGEMGR-6-AUTO_ADVISE_SW:
archive download-sw /force-reload
/overwrite /dest 1 flash1:cbs31x0-universal-mz.122-40.xx.tar
*Mar 1 00:04:22.537:%IMAGEMGR-6-AUTO_ADVISE_SW:
For information about using the archive download-sw privileged EXEC command, see the Working
with Software Images section on page B-23.
Note
Auto-advise and auto-copy identify which images are running by examining the info file and by
searching the directory structure on the switch stack. If you download your image by using the copy tftp:
boot loader command instead of the archive download-sw privileged EXEC command, the proper
directory structure is not created. For more information about the info file, see the File Format of
Images on a Server or Cisco.com section on page B-25.
Incompatible Software and Stack Member Image Upgrades
You can upgrade a switch that has an incompatible universal software image by using the archive
copy-sw privileged EXEC command. It copies the software image from an existing stack member to the
one with incompatible software. That switch automatically reloads and joins the stack as a fully
functioning member. For more information, see the Copying an Image File from One Stack Member to
Another section on page B-39.
Switch Stack Configuration Files
The configuration files record these settings:
System-level (global) configuration settingssuch as IP, STP, VLAN, and SNMP settingsthat
apply to all stack members
Stack member interface-specific configuration settings that are specific for each stack member
The stack master has the saved and running configuration files for the switch stack. All stack members
periodically receive synchronized copies of the configuration files from the stack master. If the stack
master becomes unavailable, any stack member assuming the role of stack master has the latest
configuration files.
Note
We recommend that all stack members run Cisco IOS Release 12.2(40)xx or later. The interface-specific
settings of the stack master are saved if the stack master is replaced without saving the running
configuration to the startup configuration.
When a new, out-of-box switch joins a switch stack, it uses the system-level settings of that switch stack.
If a switch is moved to a different switch stack, that switch loses its saved configuration file and uses the
system-level configuration of the new switch stack.
The interface-specific configuration of each stack member is associated with the stack member number.
As mentioned in the Stack Member Numbers section on page 5-8, stack members retain their numbers
unless they are manually changed or they are already used by another member in the same switch stack.
If an interface-specific configuration does not exist for that member number, the stack member uses
its default interface-specific configuration.
If an interface-specific configuration exists for that member number, the stack member uses the
interface-specific configuration associated with that member number.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
5-16
OL-12189-01
Chapter 5
Managing Switch Stacks
Understanding Switch Stacks
If a stack member fails and you replace with it with an identical model, the replacement switch
automatically uses the same interface-specific configuration as the failed switch. Hence, you do not need
to reconfigure the interface settings. The replacement switch must have the same stack member number
as the failed switch. For information about the benefits of provisioning a switch stack, see the Switch
Stack Offline Configuration section on page 5-9.
You back up and restore the stack configuration in the same way as you would for a standalone switch
configuration. For more information about file systems and configuration files, see Appendix B,
Working with the Cisco IOS File System, Configuration Files, and Software Images.
Additional Considerations for System-Wide Configuration on Switch Stacks
These sections provide additional considerations for configuring system-wide features on switch stacks:
Planning and Creating Clusters chapter in the Getting Started with Cisco Network Assistant,
available on Cisco.com
MAC Addresses and Switch Stacks section on page 6-20
Setting the SDM Template section on page 8-5
IEEE 802.1x Authentication and Switch Stacks section on page 9-8
VTP and Switch Stacks section on page 13-6
Private VLANs and Switch Stacks section on page 15-5
Spanning Tree and Switch Stacks section on page 17-12
MSTP and Switch Stacks section on page 18-8
DHCP Snooping and Switch Stacks section on page 21-8
IGMP Snooping and Switch Stacks section on page 23-7
Port Security and Switch Stacks section on page 25-17
CDP and Switch Stacks section on page 26-2
SPAN and RSPAN and Switch Stacks section on page 29-10
ACLs and Switch Stacks section on page 34-6
EtherChannel and Switch Stacks section on page 37-9
IP Routing and Switch Stacks section on page 38-4
IPv6 and Switch Stacks section on page 39-12
HSRP and Switch Stacks section on page 40-4
Multicast Routing and Switch Stacks section on page 44-10
Fallback Bridging and Switch Stacks section on page 46-3
Switch Stack Management Connectivity
You manage the switch stack and the stack member interfaces through the stack master. You can use the
CLI, SNMP, Network Assistant, and CiscoWorks network management applications. You cannot manage
stack members on an individual switch basis.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
5-17
Chapter 5
Managing Switch Stacks
Understanding Switch Stacks
These sections provide switch stack connectivity information:
Connectivity to the Switch Stack Through an IP Address, page 5-18
Connectivity to the Switch Stack Through an SSH Session, page 5-18
Connectivity to the Switch Stack Through Console Ports or Ethernet Management Ports, page 5-18
Connectivity to Specific Stack Members, page 5-18
Connectivity to the Switch Stack Through an IP Address
The switch stack is managed through a single IP address. The IP address is a system-level setting and is
not specific to the stack master or to any other stack member. You can still manage the stack through the
same IP address even if you remove the stack master or any other stack member from the stack, provided
there is IP connectivity.
Note
Stack members retain their IP addresses when you remove them from a switch stack. To avoid a conflict
by having two devices with the same IP address in your network, change the IP addresses of any switches
that you remove from the switch stack.
For related information about switch stack configurations, see the Switch Stack Configuration Files
section on page 5-16.
Connectivity to the Switch Stack Through an SSH Session
The Secure Shell (SSH) connectivity to the switch stack can be lost if a stack master running the
cryptographic software image and the IP base or IP services feature set fails and is replaced by a switch
that is running the noncryptographic image and the same feature set. We recommend that a switch
running the cryptographic software image and the IP base or IP services feature set be the stack master.
Encryption features are unavailable if the stack master is running the noncryptographic software image.
Connectivity to the Switch Stack Through Console Ports or Ethernet Management Ports
You can connect to the stack master by using one of these methods:
You can connect a terminal or a PC to the stack master through the console port of one or more stack
members.
You can connect a PC to the stack master through the Ethernet management ports of one or more
stack members. For more information about connecting to the switch stack through Ethernet
management ports, see the Using the Internal Ethernet Management Port section on page 10-12.
Be careful when using multiple CLI sessions to the stack master. Commands that you enter in one session
are not displayed in the other sessions. Therefore, it is possible that you might not be able to identify the
session from which you entered a command.
We recommend using only one CLI session when managing the switch stack.
Connectivity to Specific Stack Members
If you want to configure a specific stack member port, you must include the stack member number in the
CLI command interface notation. For more information, see the Using Interface Configuration Mode
section on page 10-7.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
5-18
OL-12189-01
Chapter 5
Managing Switch Stacks
Understanding Switch Stacks
To debug a specific stack member, you can access it from the stack master by using the session
stack-member-number privileged EXEC command. The stack member number is appended to the system
prompt. For example, Switch-2# is the prompt in privileged EXEC mode for stack member 2, and the
system prompt for the stack master is Switch. Only the show and debug commands are available in a
CLI session to a specific stack member.
Switch Stack Configuration Scenarios
Table 5-2 provides switch stack configuration scenarios. Most of the scenarios assume that at least two
switches are connected through their StackWise Plus ports.
Table 5-2
Switch Stack Configuration Scenarios
Scenario
Result
Stack master election
Connect two powered-on switch stacks
specifically determined
through the StackWise Plus ports.
by existing stack masters
Only one of the two stack masters becomes the new
stack master. None of the other stack members
become the stack master.
Stack master election
specifically determined
by the stack member
priority value
The stack member with the higher priority value is
elected stack master.
Stack master election
specifically determined
by the configuration file
1.
Connect two switches through their
StackWise Plus ports.
2.
Use the switch stack-member-number
priority new-priority-number global
configuration command to set one stack
member with a higher member priority
value.
3.
Restart both stack members at the same
time.
Assuming that both stack members have the The stack member with the saved configuration file
is elected stack master.
same priority value:
1.
Make sure that one stack member has a
default configuration and that the other
stack member has a saved (nondefault)
configuration file.
2.
Restart both stack members at the same
time.
Assuming that all stack members have the
Stack master election
same priority value:
specifically determined
by the cryptographic
1. Make sure that one stack member has
software image and the IP
the cryptographic image installed and
services feature set and
the IP services feature set enabled and
the IP services feature set
that the other stack member has the
noncryptographic image installed and
the IP services feature set enabled.
2.
The stack member with the cryptographic image and
the IP services feature set is elected stack master.
Restart both stack members at the same
time.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
5-19
Chapter 5
Managing Switch Stacks
Understanding Switch Stacks
Table 5-2
Switch Stack Configuration Scenarios (continued)
Scenario
Result
Assuming that all stack members have the The stack member with the cryptographic image and
Stack master election
same priority value:
the IP base feature set is elected stack master.
specifically determined
by the cryptographic
1. Make sure that one stack member has
software image and the IP
the cryptographic image installed and
base feature set
the IP base feature set enabled and that
the other stack member has the
noncryptographic image installed and
the IP base feature set enabled.
2.
Restart both stack members at the same
time.
Stack master election
specifically determined
by the MAC address
Assuming that both stack members have the The stack member with the lower MAC address is
same priority value, configuration file, and elected stack master.
feature set, restart both stack members at
the same time.
Stack member number
conflict
Assuming that one stack member has a
higher priority value than the other stack
member:
Add a stack member
Stack master failure
Add more than nine stack
members
1.
Ensure that both stack members have
the same stack member number. If
necessary, use the switch
current-stack-member-number
renumber new-stack-member-number
global configuration command.
2.
Restart both stack members at the same
time.
1.
Power off the new switch.
2.
Through their StackWise Plus ports,
connect the new switch to a powered-on
switch stack.
3.
Power on the new switch.
Remove (or power off) the stack master.
1.
Through their StackWise Plus ports,
connect ten switches.
2.
Power on all switches.
The stack member with the higher priority value
retains its stack member number. The other stack
member has a new stack member number.
The stack master is retained. The new switch is
added to the switch stack.
Based on the factors described in the Stack Master
Election and Re-Election section on page 5-6, one
of the remaining stack members becomes the new
stack master. All other stack members in the stack
remain as stack members and do not reboot.
Two switches become stack masters. One stack
master has nine stack members. The other stack
master remains as a standalone switch.
Use the Stack Master LED and the Stack Member
LED to identify which switches are stack masters
and which switches belong to each stack master. For
information about using the Stack Master and Stack
Members LEDs, see the hardware installation guide.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
5-20
OL-12189-01
Chapter 5
Managing Switch Stacks
Configuring the Switch Stack
Configuring the Switch Stack
These sections contain this configuration information:
Default Switch Stack Configuration, page 5-21
Configuration Guidelines, page 5-21
Enabling Persistent MAC Address, page 5-22
Assigning Stack Member Information, page 5-24
Default Switch Stack Configuration
Table 5-3 shows the default switch stack configuration.
Table 5-3
Default Switch Stack Configuration
Feature
Default Setting
Stack MAC address timer
Disabled.
Stack member number
Stack member priority value
Offline configuration
The switch stack is not provisioned.
Configuration Guidelines
Follow these guidelines when creating and configuring switch stacks:
AMM version incompatibilityIn a switch stack with members in more than one enclosure, all of
the enclosures might not support stacking. If this occurs, all of the stack members do not join the
stack. The stack members in the enclosure with the AMM that supports stacking can power up and
can join stack. However, members with the enclosure that do not support stacking only power on as
standalone switches and do not join the stack.
To resolve this problem, upgrade the AMM software to a version that supports stacking, and then
reboot the stack members.
Protected modeThe protected-mode feature is supported only on a standalone switch. For
information about using protected mode, see the Configuring Protected Mode section on
page 3-15.
If protected mode is enabled on the stack master and a member leaves the stack, protected mode is
still enabled on the switch.
If protected mode is disabled on the stack master and the member leaves the stack, protected mode
is disabled on the switch.
If a stack member leaves the stack, the AMM resumes control of the switch. The internal Ethernet
management port on the switch and the previously configured default gateway are now active.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
5-21
Chapter 5
Managing Switch Stacks
Configuring the Switch Stack
Enabling Persistent MAC Address
The switch stack MAC address is determined by the MAC address of the stack master. When a stack
master is removed from the stack and a new stack master takes over, the default is for the MAC address
of the new stack master to immediately become the new stack MAC router address. However, you can
enable the persistent MAC address feature to allow a time delay before the stack MAC address changes.
During this time period, if the previous stack master rejoins the stack, the stack continues to use its MAC
address as the stack MAC address, even if the switch is now a stack member and not a stack master. If
the previous stack master does not rejoin the stack during this period, the switch stack takes the MAC
address of the new stack master as the stack MAC address.You can also configure stack MAC persistency
so that the stack never switches to the MAC address of the new stack master.
Note
When you enter the command to configure this feature, a warning message appears containing the
consequences of your configuration. You should use this feature cautiously. Using the old stack master
MAC address elsewhere in the same domain could result in lost traffic.
You can configure the time period as 0 to 60 minutes.
Note
If you enter the command with no value, the default delay is 4 minutes. We recommend that you
always enter a value. If the command is entered without a value, the time delay appears in the
running-config file with an explicit timer value of 4 minutes.
If you enter 0, the stack MAC address of the previous stack master is used until you enter the no
stack-mac persistent timer command, which immediately changes the stack MAC address to that
of the current stack master. If you do not enter the no stack-mac persistent timer command, the
stack MAC address never changes.
If you enter a time delay of 1 to 60 minutes, the stack MAC address of the previous stack master is
used until the configured time period expires or until you enter the no stack-mac persistent timer
command.
If the entire switch stack reloads, it uses with the MAC address of the stack master as the stack MAC
address.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
5-22
OL-12189-01
Chapter 5
Managing Switch Stacks
Configuring the Switch Stack
Beginning in privileged EXEC mode, follow these steps to enable persistent MAC address. This
procedure is optional.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
stack-mac persistent timer [0 |
time-value]
Enable a time delay after a stack-master change before the stack MAC
address changes to that of the new stack master. If the previous stack
master rejoins the stack during this period, the stack uses that MAC
address as the stack MAC address.
Enter the command with no value to set the default delay of
approximately 4 minutes. We recommend that you always configure
a value.
Enter 0 to continue using the MAC address of the current stack
master indefinitely.
Enter a time-value from 1 to 60 minutes to configure the time period
before the stack MAC address changes to the new stack master.
Note
When you enter this command, a warning states that traffic
might be lost if the old master MAC address appears elsewhere
in the network domain.
If you enter the no stack-mac persistent timer command after a new
stack master takes over, before the time expires, the switch stack moves
to the current stack master MAC address.
Step 3
end
Return to privileged EXEC mode.
Step 4
show running-config
or
Verify that the stack MAC address timer is enabled. If enabled, the
output shows stack-mac persistent timer and the time in minutes.
show switch
If enabled, the display includes:
Step 5
Mac persistency wait time, the number of minutes configured, and
the current stack MAC address.
Step 6
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Use the no stack-mac persistent timer global configuration command to disable the persistent MAC
address feature.
This example shows how to configure the persistent MAC address feature for a 7-minute time delay and
to verify the configuration:
Switch(config)# stack-mac persistent timer 7
WARNING: The stack continues to use the base MAC of the old Master
WARNING: as the stack MAC after a master switchover until the MAC
WARNING: persistency timer expires. During this time the Network
WARNING: Administrators must make sure that the old stack-mac does
WARNING: not appear elsewhere in this network domain. If it does,
WARNING: user traffic may be blackholed.
Switch(config)# end
Switch# show switch
Switch/Stack Mac Address : 0016.4727.a900
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
5-23
Chapter 5
Managing Switch Stacks
Configuring the Switch Stack
Mac persistency wait time: 7 mins
H/W
Current
Switch# Role
Mac Address
Priority Version State
---------------------------------------------------------*1
Master 0016.4727.a900
1
0
Ready
Assigning Stack Member Information
These sections describe how to assign stack member information:
Assigning a Stack Member Number, page 5-24 (optional)
Setting the Stack Member Priority Value, page 5-25 (optional)
Provisioning a New Member for a Switch Stack, page 5-25 (optional)
Assigning a Stack Member Number
Note
This task is available only from the stack master.
Beginning in privileged EXEC mode, follow these steps to assign a member number to a stack member.
This procedure is optional.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
switch current-stack-member-number
renumber new-stack-member-number
Specify the current stack member number and the new stack member
number for the stack member. The range is 1 to 9.
You can display the current stack member number by using the show
switch user EXEC command.
Step 3
end
Return to privileged EXEC mode.
Step 4
reload slot stack-member-number
Reset the stack member.
Step 5
show switch
Verify the stack member number.
Step 6
copy running-config startup-config
Save your entries in the configuration file.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
5-24
OL-12189-01
Chapter 5
Managing Switch Stacks
Configuring the Switch Stack
Setting the Stack Member Priority Value
Note
This task is available only from the stack master.
Beginning in privileged EXEC mode, follow these steps to assign a priority value to a stack member:
This procedure is optional.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
switch stack-member-number priority
new-priority-number
Specify the stack member number and the new priority for the stack
member. The stack member number range is 1 to 9. The priority value
range is 1 to 15.
You can display the current priority value by using the show switch user
EXEC command.
The new priority value takes effect immediately but does not affect the
current stack master. The new priority value helps determine which stack
member is elected as the new stack master when the current stack master
or switch stack resets.
Step 3
end
Return to privileged EXEC mode.
Step 4
reload slot stack-member-number
Reset the stack member, and apply this configuration change.
Step 5
show switch stack-member-number
Verify the stack member priority value.
Step 6
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Provisioning a New Member for a Switch Stack
Note
This task is available only from the stack master.
Beginning in privileged EXEC mode, follow these steps to provision a new member for a switch stack.
This procedure is optional.
Command
Purpose
Step 1
show switch
Display summary information about the switch stack.
Step 2
configure terminal
Enter global configuration mode.
Step 3
switch stack-member-number provision
type
Specify the stack member number for the preconfigured switch. By
default, no switches are provisioned.
For stack-member-number, the range is 1 to 9. Specify a stack member
number that is not already used in the switch stack. See Step 1.
For type, enter the model number of a supported switch that is listed in
the command-line help strings.
Step 4
end
Return to privileged EXEC mode.
Step 5
show running-config
Verify the correct numbering of interfaces in the running configuration
file.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
5-25
Chapter 5
Managing Switch Stacks
Accessing the CLI of a Specific Stack Member
Command
Purpose
Step 6
show switch stack-member-number
Verify the status of the provisioned switch. For stack-member-number,
enter the same number as in Step 1.
Step 7
copy running-config startup-config
(Optional) Save your entries in the configuration file.
To remove provisioned information and to avoid receiving an error message, remove the specified switch
from the stack before you use the no form of this command.
For example, if you are removing a provisioned switch in a stack with this configuration:
The stack has four members
Stack member 1 is the master
Stack member 3 is a provisioned switch
and want to remove the provisioned information and to avoid receiving an error message, you can remove
power from stack member 3, disconnect the StackWise Plus cables between the stack member 3 and
switches to which it is connected, reconnect the cables between the remaining stack members, and enter
the no switch stack-member-number provision global configuration command.
This example shows how to provision a switch with a stack member number of 2 for the switch stack.
The show running-config command output shows the interfaces associated with the provisioned switch:
Switch(config)# switch 2 provision WS-CBS3110G
Switch(config)# end
Switch# show running-config | include switch 2
!
interface GigabitEthernet2/0/1
!
interface GigabitEthernet2/0/2
!
interface GigabitEthernet2/0/3
<output truncated>
Accessing the CLI of a Specific Stack Member
Note
This task is available only from the stack master. This task is only for debugging purposes.
You can access all or specific stack members by using the remote command {all |
stack-member-number} privileged EXEC command. The stack member number range is 1 to 9.
You can access specific stack members by using the session stack-member-number privileged EXEC
command. The stack member number range is 1 to 9. The stack member number is appended to the
system prompt. For example, Switch-2# is the prompt in privileged EXEC mode for stack member 2,
and the system prompt for the stack master is Switch. Enter exit to return to the CLI session on the stack
master. Only the show and debug commands are available in a CLI session to a specific stack member.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
5-26
OL-12189-01
Chapter 5
Managing Switch Stacks
Displaying Switch Stack Information
Displaying Switch Stack Information
To display configuration changes that you save after you reset a specific stack member or the switch
stack, use the privileged EXEC commands listed in Table 5-4.
Table 5-4
Commands for Displaying Switch Stack Information
Command
Description
show platform stack-manager all
Displays all switch stack information.
show switch
Displays summary information about the switch stack,
including the status of provisioned switches.
show switch stack-member-number
Displays information about a specific member.
show switch detail
Displays detailed information about the stack ring.
show switch neighbors
Display the neighbors for the entire switch stack.
show switch stack-ports
Displays port information for the entire switch stack.
show switch stack-ring activity
[detail]
Displays the number of frames per stack member that are sent
to the stack ring. Use the detail keyword to display the ASIC,
the receive queues, and the number of frames per stack
member that are sent to the stack ring.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
5-27
Chapter 5
Managing Switch Stacks
Displaying Switch Stack Information
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
5-28
OL-12189-01
CH A P T E R
Administering the Switch
This chapter describes how to perform one-time operations to administer the switch. Unless otherwise
noted, the term switch refers to a standalone switch and to a switch stack.
This chapter consists of these sections:
Managing the System Time and Date, page 6-1
Configuring a System Name and Prompt, page 6-14
Creating a Banner, page 6-17
Managing the MAC Address Table, page 6-19
Managing the ARP Table, page 6-26
Managing the System Time and Date
You can manage the system time and date on your switch using automatic configuration, such as the
Network Time Protocol (NTP), or manual configuration methods.
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.
These sections contain this configuration information:
Understanding the System Clock, page 6-1
Understanding Network Time Protocol, page 6-2
Configuring NTP, page 6-3
Configuring Time and Date Manually, page 6-11
Understanding the System Clock
The heart of the time service is the system clock. This clock runs from the moment the system starts up
and keeps track of the date and time.
The system clock can then be set from these sources:
NTP
Manual configuration
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
6-1
Chapter 6
Administering the Switch
Managing the System Time and Date
The system clock can provide time to these services:
User show commands
Logging and debugging messages
The system clock keeps track of time internally based on Universal Time Coordinated (UTC), also
known as Greenwich Mean Time (GMT). You can configure information about the local time zone and
summer time (daylight saving time) so that the time appears correctly for the local time zone.
The system clock keeps track of whether the time is authoritative or not (that is, whether it has been set
by a time source considered to be authoritative). If it is not authoritative, the time is available only for
display purposes and is not redistributed. For configuration information, see the Configuring Time and
Date Manually section on page 6-11.
Understanding Network Time Protocol
The NTP is designed to time-synchronize a network of devices. NTP runs over User Datagram Protocol
(UDP), which runs over IP. NTP is documented in RFC 1305.
An NTP network usually gets its time from an authoritative time source, such as a radio clock or an
atomic clock attached to a time server. NTP then distributes this time across the network. NTP is
extremely efficient; no more than one packet per minute is necessary to synchronize two devices to
within a millisecond of one another.
NTP uses the concept of a stratum to describe how many NTP hops away a device is from an
authoritative time source. A stratum 1 time server has a radio or atomic clock directly attached, a
stratum 2 time server receives its time through NTP from a stratum 1 time server, and so on. A device
running NTP automatically chooses as its time source the device with the lowest stratum number with
which it communicates through NTP. This strategy effectively builds a self-organizing tree of NTP
speakers.
NTP avoids synchronizing to a device whose time might not be accurate by never synchronizing to a
device that is not synchronized. NTP also compares the time reported by several devices and does not
synchronize to a device whose time is significantly different than the others, even if its stratum is lower.
The communications between devices running NTP (known as associations) are usually statically
configured; each device is given the IP address of all devices with which it should form associations.
Accurate timekeeping is possible by exchanging NTP messages between each pair of devices with an
association. However, in a LAN environment, NTP can be configured to use IP broadcast messages
instead. This alternative reduces configuration complexity because each device can simply be configured
to send or receive broadcast messages. However, in that case, information flow is one-way only.
The time kept on a device is a critical resource; you should use the security features of NTP to avoid the
accidental or malicious setting of an incorrect time. Two mechanisms are available: an access list-based
restriction scheme and an encrypted authentication mechanism.
Ciscos implementation of NTP does not support stratum 1 service; it is not possible to connect to a radio
or atomic clock. We recommend that the time service for your network be derived from the public NTP
servers available on the IP Internet.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
6-2
OL-12189-01
Chapter 6
Administering the Switch
Managing the System Time and Date
Figure 6-1 shows a typical network example using NTP. Switch A is the NTP master, with the Switch E,
Switch B, and Switch C configured in NTP server mode, in server association with Switch A. Switch D
is configured as an NTP peer to the upstream and downstream switches, Switch E and the blade switch,
respectively.
Figure 6-1
Typical NTP Network Configuration
Switch A
Switch E
Switch B
Switch C
Workstations
Switch D
Workstations
Blade
servers
201758
Blade
switch
If the network is isolated from the Internet, Ciscos implementation of NTP allows a device to act as if
it is synchronized through NTP, when in fact it has learned 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.
Configuring NTP
The switch does not have a hardware-supported clock and cannot function as an NTP master clock to
which peers synchronize themselves when an external NTP source is not available. The switch also has
no hardware support for a calendar. As a result, the ntp update-calendar and the ntp master global
configuration commands are not available.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
6-3
Chapter 6
Administering the Switch
Managing the System Time and Date
These sections contain this configuration information:
Default NTP Configuration, page 6-4
Configuring NTP Authentication, page 6-4
Configuring NTP Associations, page 6-5
Configuring NTP Broadcast Service, page 6-6
Configuring NTP Access Restrictions, page 6-8
Configuring the Source IP Address for NTP Packets, page 6-10
Displaying the NTP Configuration, page 6-11
Default NTP Configuration
Table 6-1 shows the default NTP configuration.
Table 6-1
Default NTP Configuration
Feature
Default Setting
NTP authentication
Disabled. No authentication key is specified.
NTP peer or server associations
None configured.
NTP broadcast service
Disabled; no interface sends or receives NTP broadcast packets.
NTP access restrictions
No access control is specified.
NTP packet source IP address
The source address is set by the outgoing interface.
NTP is enabled on all interfaces by default. All interfaces receive NTP packets.
Configuring NTP Authentication
This procedure must be coordinated with the administrator of the NTP server; the information you
configure in this procedure must be matched by the servers used by the switch to synchronize its time to
the NTP server.
Beginning in privileged EXEC mode, follow these steps to authenticate the associations (communications
between devices running NTP that provide for accurate timekeeping) with other devices for security
purposes:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ntp authenticate
Enable the NTP authentication feature, which is disabled by
default.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
6-4
OL-12189-01
Chapter 6
Administering the Switch
Managing the System Time and Date
Step 3
Command
Purpose
ntp authentication-key number md5 value
Define the authentication keys. By default, none are defined.
For number, specify a key number. The range is 1 to
4294967295.
md5 specifies that message authentication support is provided
by using the message digest algorithm 5 (MD5).
For value, enter an arbitrary string of up to eight characters for
the key.
The switch does not synchronize to a device unless both have one
of these authentication keys, and the key number is specified by the
ntp trusted-key key-number command.
Step 4
ntp trusted-key key-number
Specify one or more key numbers (defined in Step 3) that a peer
NTP device must provide in its NTP packets for this switch to
synchronize to it.
By default, no trusted keys are defined.
For key-number, specify the key defined in Step 3.
This command provides protection against accidentally
synchronizing the switch to a device that is not trusted.
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 NTP authentication, use the no ntp authenticate global configuration command. To remove
an authentication key, use the no ntp authentication-key number global configuration command. To
disable authentication of the identity of a device, use the no ntp trusted-key key-number global
configuration command.
This example shows how to configure the switch to synchronize only to devices providing authentication
key 42 in the devices NTP packets:
Switch(config)# ntp authenticate
Switch(config)# ntp authentication-key 42 md5 aNiceKey
Switch(config)# ntp trusted-key 42
Configuring NTP Associations
An NTP association can be a peer association (this switch can either synchronize to the other device or
allow the other device to synchronize to it), or it can be a server association (meaning that only this
switch synchronizes to the other device, and not the other way around).
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
6-5
Chapter 6
Administering the Switch
Managing the System Time and Date
Beginning in privileged EXEC mode, follow these steps to form an NTP association with another device:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ntp peer ip-address [version number]
[key keyid] [source interface] [prefer]
Configure the switch system clock to synchronize a peer or to be
synchronized by a peer (peer association).
or
or
ntp server ip-address [version number] Configure the switch system clock to be synchronized by a time server
[key keyid] [source interface] [prefer] (server association).
No peer or server associations are defined by default.
For ip-address in a peer association, specify either the IP address of
the peer providing, or being provided, the clock synchronization. For
a server association, specify the IP address of the time server
providing the clock synchronization.
(Optional) For number, specify the NTP version number. The range is
1 to 3. By default, Version 3 is selected.
(Optional) For keyid, enter the authentication key defined with the
ntp authentication-key global configuration command.
(Optional) For interface, specify the interface from which to pick the
IP source address. By default, the source IP address is taken from the
outgoing interface.
(Optional) Enter the prefer keyword to make this peer or server the
preferred one that provides synchronization. This keyword reduces
switching back and forth between peers and servers.
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.
You need to configure only one end of an association; the other device can automatically establish the
association. If you are using the default NTP version (Version 3) and NTP synchronization does not
occur, try using NTP Version 2. Many NTP servers on the Internet run Version 2.
To remove a peer or server association, use the no ntp peer ip-address or the no ntp server ip-address
global configuration command.
This example shows how to configure the switch to synchronize its system clock with the clock of the
peer at IP address 172.16.22.44 using NTP Version 2:
Switch(config)# ntp server 172.16.22.44 version 2
Configuring NTP Broadcast Service
The communications between devices running NTP (known as associations) are usually statically
configured; each device is given the IP addresses of all devices with which it should form associations.
Accurate timekeeping is possible by exchanging NTP messages between each pair of devices with an
association. However, in a LAN environment, NTP can be configured to use IP broadcast messages
instead. This alternative reduces configuration complexity because each device can simply be configured
to send or receive broadcast messages. However, the information flow is one-way only.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
6-6
OL-12189-01
Chapter 6
Administering the Switch
Managing the System Time and Date
The switch can send or receive NTP broadcast packets on an interface-by-interface basis if there is an
NTP broadcast server, such as a router, broadcasting time information on the network. The switch can
send NTP broadcast packets to a peer so that the peer can synchronize to it. The switch can also receive
NTP broadcast packets to synchronize its own clock. This section provides procedures for both sending
and receiving NTP broadcast packets.
Beginning in privileged EXEC mode, follow these steps to configure the switch to send NTP broadcast
packets to peers so that they can synchronize their clock to the switch:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
interface interface-id
Specify the interface to send NTP broadcast packets, and enter
interface configuration mode.
Step 3
ntp broadcast [version number] [key keyid] Enable the interface to send NTP broadcast packets to a peer.
[destination-address]
By default, this feature is disabled on all interfaces.
(Optional) For number, specify the NTP version number. The
range is 1 to 3. If you do not specify a version, Version 3 is used.
(Optional) For keyid, specify the authentication key to use when
sending packets to the peer.
(Optional) For destination-address, specify the IP address of the
peer that is synchronizing its clock to this switch.
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
Configure the connected peers to receive NTP broadcast packets as
described in the next procedure.
To disable the interface from sending NTP broadcast packets, use the no ntp broadcast interface
configuration command.
This example shows how to configure a port to send NTP Version 2 packets:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# ntp broadcast version 2
Beginning in privileged EXEC mode, follow these steps to configure the switch to receive NTP broadcast
packets from connected peers:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
interface interface-id
Specify the interface to receive NTP broadcast packets, and enter interface
configuration mode.
Step 3
ntp broadcast client
Enable the interface to receive NTP broadcast packets.
By default, no interfaces receive NTP broadcast packets.
Step 4
exit
Return to global configuration mode.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
6-7
Chapter 6
Administering the Switch
Managing the System Time and Date
Step 5
Command
Purpose
ntp broadcastdelay microseconds
(Optional) Change the estimated round-trip delay between the switch and
the NTP broadcast server.
The default is 3000 microseconds; the range is 1 to 999999.
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 an interface from receiving NTP broadcast packets, use the no ntp broadcast client interface
configuration command. To change the estimated round-trip delay to the default, use the no ntp
broadcastdelay global configuration command.
This example shows how to configure a port to receive NTP broadcast packets:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# ntp broadcast client
Configuring NTP Access Restrictions
You can control NTP access on two levels as described in these sections:
Creating an Access Group and Assigning a Basic IP Access List, page 6-8
Disabling NTP Services on a Specific Interface, page 6-10
Creating an Access Group and Assigning a Basic IP Access List
Beginning in privileged EXEC mode, follow these steps to control access to NTP services by using
access lists:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ntp access-group {query-only |
serve-only | serve | peer}
access-list-number
Create an access group, and apply a basic IP access list.
The keywords have these meanings:
query-onlyAllows only NTP control queries.
serve-onlyAllows only time requests.
serveAllows time requests and NTP control queries, but does not
allow the switch to synchronize to the remote device.
peerAllows time requests and NTP control queries and allows the
switch to synchronize to the remote device.
For access-list-number, enter a standard IP access list number from 1
to 99.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
6-8
OL-12189-01
Chapter 6
Administering the Switch
Managing the System Time and Date
Step 3
Command
Purpose
access-list access-list-number permit
source [source-wildcard]
Create the access list.
For access-list-number, enter the number specified in Step 2.
Enter the permit keyword to permit access if the conditions are
matched.
For source, enter the IP address of the device that is permitted access
to the switch.
(Optional) For source-wildcard, enter the wildcard bits to be applied
to the source.
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 running-config
Verify your entries.
Step 6
copy running-config startup-config
(Optional) Save your entries in the configuration file.
The access group keywords are scanned in this order, from least restrictive to most restrictive:
1.
peerAllows time requests and NTP control queries and allows the switch to synchronize itself to
a device whose address passes the access list criteria.
2.
serveAllows time requests and NTP control queries, but does not allow the switch to synchronize
itself to a device whose address passes the access list criteria.
3.
serve-onlyAllows only time requests from a device whose address passes the access list criteria.
4.
query-onlyAllows only NTP control queries from a device whose address passes the access list
criteria.
If the source IP address matches the access lists for more than one access type, the first type is granted.
If no access groups are specified, all access types are granted to all devices. If any access groups are
specified, only the specified access types are granted.
To remove access control to the switch NTP services, use the no ntp access-group {query-only |
serve-only | serve | peer} global configuration command.
This example shows how to configure the switch to allow itself to synchronize to a peer from access
list 99. However, the switch restricts access to allow only time requests from access list 42:
Switch# configure terminal
Switch(config)# ntp access-group peer 99
Switch(config)# ntp access-group serve-only 42
Switch(config)# access-list 99 permit 172.20.130.5
Switch(config)# access list 42 permit 172.20.130.6
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
6-9
Chapter 6
Administering the Switch
Managing the System Time and Date
Disabling NTP Services on a Specific Interface
NTP services are enabled on all interfaces by default.
Beginning in privileged EXEC mode, follow these steps to disable NTP packets from being received on
an 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 disable.
Step 3
ntp disable
Disable NTP packets from being received on the interface.
By default, all interfaces receive NTP packets.
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 receipt of NTP packets on an interface, use the no ntp disable interface configuration
command.
Configuring the Source IP Address for NTP Packets
When the switch sends an NTP packet, the source IP address is normally set to the address of the
interface through which the NTP packet is sent. Use the ntp source global configuration command when
you want to use a particular source IP address for all NTP packets. The address is taken from the
specified interface. This command is useful if the address on an interface cannot be used as the
destination for reply packets.
Beginning in privileged EXEC mode, follow these steps to configure a specific interface from which the
IP source address is to be taken:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ntp source type number
Specify the interface type and number from which the IP source address
is taken.
By default, the source address is set by the outgoing interface.
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 specified interface is used for the source address for all packets sent to all destinations. If a source
address is to be used for a specific association, use the source keyword in the ntp peer or ntp server
global configuration command as described in the Configuring NTP Associations section on page 6-5.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
6-10
OL-12189-01
Chapter 6
Administering the Switch
Managing the System Time and Date
Displaying the NTP Configuration
You can use two privileged EXEC commands to display NTP information:
show ntp associations [detail]
show ntp status
For detailed information about the fields in these displays, see the Cisco IOS Configuration
Fundamentals Command Reference, Release 12.2.
Configuring Time and Date Manually
If no other source of time is available, you can manually configure the time and date after the system is
restarted. The time remains accurate until the next system restart. We recommend that you use manual
configuration only as a last resort. If you have an outside source to which the switch can synchronize,
you do not need to manually set the system clock.
Note
You must reset this setting if you have manually set the system clock and the stack master fails and
different stack member resumes the role of stack master.
These sections contain this configuration information:
Setting the System Clock, page 6-11
Displaying the Time and Date Configuration, page 6-12
Configuring the Time Zone, page 6-12
Configuring Summer Time (Daylight Saving Time), page 6-13
Setting the System Clock
If you have an outside source on the network that provides time services, such as an NTP server, you do
not need to manually set the system clock.
Beginning in privileged EXEC mode, follow these steps to set the system clock:
Step 1
Command
Purpose
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,
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).
clock set hh:mm:ss month day year
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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
6-11
Chapter 6
Administering the Switch
Managing the System Time and Date
Displaying the Time and Date Configuration
To display the time and date configuration, use the show clock [detail] privileged EXEC command.
The system clock keeps an authoritative flag that shows whether the time is authoritative (believed to be
accurate). If the system clock has been set by a timing source such as NTP, the flag is set. If the time is
not authoritative, it is used only for display purposes. Until the clock is authoritative and the
authoritative flag is set, the flag prevents peers from synchronizing to the clock when the peers time is
invalid.
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.
Configuring the Time Zone
Beginning in privileged EXEC mode, follow these steps to manually configure the time zone:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
clock timezone zone hours-offset
[minutes-offset]
Set the time zone.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
6-12
OL-12189-01
Chapter 6
Administering the Switch
Managing the System Time and Date
Configuring Summer Time (Daylight Saving Time)
Beginning in privileged EXEC mode, follow these steps to configure summer time (daylight saving time)
in areas where it starts and ends on a particular day of the week each year:
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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
6-13
Chapter 6
Administering the Switch
Configuring a System Name and Prompt
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
Configure summer time to start on the first date and end on the second
clock summer-time zone date [month
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, 2000, at 02:00, and end on
April 26, 2001, at 02:00:
Switch(config)# clock summer-time pdt date 12 October 2000 2:00 26 April 2001 2:00
Configuring a System Name and Prompt
You configure the system name on the switch to identify it. By default, the system name and prompt are
Switch.
If you have not configured a system prompt, the first 20 characters of the system name are used as the
system prompt. A greater-than symbol [>] is appended. The prompt is updated whenever the system
name changes.
If you are accessing a stack member through the stack master, you must use the session
stack-member-number privileged EXEC command. The stack member number range is from 1 through
9. When you use this command, the stack member number is appended to the system prompt. For
example, Switch-2# is the prompt in privileged EXEC mode for stack member 2, and the system prompt
for the switch stack is Switch.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
6-14
OL-12189-01
Chapter 6
Administering the Switch
Configuring a System Name and Prompt
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.
These sections contain this configuration information:
Default System Name and Prompt Configuration, page 6-15
Configuring a System Name, page 6-15
Understanding DNS, page 6-15
Default System Name and Prompt Configuration
The default switch system name and prompt is Switch.
Configuring a System Name
Beginning in privileged EXEC mode, follow these steps to manually configure a system name:
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 File Transfer Protocol (FTP) system is
identified as ftp.cisco.com.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
6-15
Chapter 6
Administering the Switch
Configuring a System Name and Prompt
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.
These sections contain this configuration information:
Default DNS Configuration, page 6-16
Setting Up DNS, page 6-16
Displaying the DNS Configuration, page 6-17
Default DNS Configuration
Table 6-2 shows the default DNS configuration.
Table 6-2
Default DNS Configuration
Feature
Default Setting
DNS enable state
Enabled.
DNS default domain name
None configured.
DNS servers
No name server addresses are configured.
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 bootup time, no domain name is configured; however, if the switch
configuration comes from a BOOTP or Dynamic Host Configuration Protocol
(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
Step 4
ip name-server server-address1
[server-address2 ...
server-address6]
ip domain-lookup
Specify the address of one or more name servers to use for name and address
resolution.
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.
(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).
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
6-16
OL-12189-01
Chapter 6
Administering the Switch
Creating a Banner
Command
Purpose
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.
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.
Displaying the DNS Configuration
To display the DNS configuration information, use the show running-config privileged EXEC
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 appears 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.
These sections contain this configuration information:
Default Banner Configuration, page 6-17
Configuring a Message-of-the-Day Login Banner, page 6-18
Configuring a Login Banner, page 6-18
Default Banner Configuration
The MOTD and login banners are not configured.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
6-17
Chapter 6
Administering the Switch
Creating a Banner
Configuring a Message-of-the-Day Login Banner
You can create a single or multiline message banner that appears on the screen when someone logs in to
the switch.
Beginning in privileged EXEC mode, follow these steps to configure a MOTD login banner:
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 that appears from the previous configuration:
Unix> telnet 172.2.5.4
Trying 172.2.5.4...
Connected to 172.2.5.4.
Escape character is '^]'.
This is a secure site. Only authorized users are allowed.
For access, contact technical support.
User Access Verification
Password:
Configuring a Login Banner
You can configure a login banner to be displayed on all connected terminals. This banner appears after
the MOTD banner and before the login prompt.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
6-18
OL-12189-01
Chapter 6
Administering the Switch
Managing the MAC Address Table
Beginning in privileged EXEC mode, follow these steps to configure a login banner:
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)#
Managing the MAC Address Table
The MAC address table contains address information that the switch uses to forward traffic between
ports. All MAC addresses in the address table are associated with one or more ports. The address table
includes these types of addresses:
Dynamic address: a source MAC address that the switch learns and then ages when it is not in use.
Static address: a manually entered unicast address that does not age and that is not lost when the
switch resets.
The address table lists the destination MAC address, the associated VLAN ID, and port number
associated with the address and the type (static or dynamic).
Note
For complete syntax and usage information for the commands used in this section, see the command
reference for this release.
These sections contain this configuration information:
Building the Address Table, page 6-20
MAC Addresses and VLANs, page 6-20
MAC Addresses and Switch Stacks, page 6-20
Default MAC Address Table Configuration, page 6-21
Changing the Address Aging Time, page 6-21
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
6-19
Chapter 6
Administering the Switch
Managing the MAC Address Table
Removing Dynamic Address Entries, page 6-22
Configuring MAC Address Notification Traps, page 6-22
Adding and Removing Static Address Entries, page 6-24
Configuring Unicast MAC Address Filtering, page 6-25
Displaying Address Table Entries, page 6-26
Building the Address Table
With multiple MAC addresses supported on all ports, you can connect any port on the switch to
individual workstations, repeaters, switches, routers, or other network devices. The switch provides
dynamic addressing by learning the source address of packets it receives on each port and adding the
address and its associated port number to the address table. As stations are added or removed from the
network, the switch updates the address table, adding new dynamic addresses and aging out those that
are not in use.
The aging interval is globally configured on a standalone switch or on the switch stack. However, the
switch maintains an address table for each VLAN, and STP can accelerate the aging interval on a
per-VLAN basis.
The switch sends packets between any combination of ports, based on the destination address of the
received packet. Using the MAC address table, the switch forwards the packet only to the port associated
with the destination address. If the destination address is on the port that sent the packet, the packet is
filtered and not forwarded. The switch always uses the store-and-forward method: complete packets are
stored and checked for errors before transmission.
MAC Addresses and VLANs
All addresses are associated with a VLAN. An address can exist in more than one VLAN and have
different destinations in each. Unicast addresses, for example, could be forwarded to port 1 in VLAN 1
and ports 9, 10, and 1 in VLAN 5.
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 15, Configuring Private VLANs.
MAC Addresses and Switch Stacks
The MAC address tables on all stack members are synchronized. At any given time, each stack member
has the same copy of the address tables for each VLAN. When an address ages out, the address is
removed from the address tables on all stack members. When a switch joins a switch stack, that switch
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
6-20
OL-12189-01
Chapter 6
Administering the Switch
Managing the MAC Address Table
receives the addresses for each VLAN learned on the other stack members. When a stack member leaves
the switch stack, the remaining stack members age out or remove all addresses learned by the former
stack member.
Default MAC Address Table Configuration
Table 6-3 shows the default MAC address table configuration.
Table 6-3
Default MAC Address Table Configuration
Feature
Default Setting
Aging time
300 seconds
Dynamic addresses
Automatically learned
Static addresses
None configured
Changing the Address Aging Time
Dynamic addresses are source MAC addresses that the switch learns and then ages when they are not in
use. You can change the aging time setting for all VLANs or for a specified VLAN.
Setting too short an aging time can cause addresses to be prematurely removed from the table. Then
when the switch receives a packet for an unknown destination, it floods the packet to all ports in the same
VLAN as the receiving port. This unnecessary flooding can impact performance. Setting too long an
aging time can cause the address table to be filled with unused addresses, which prevents new addresses
from being learned. Flooding results, which can impact switch performance.
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 |
10-1000000] [vlan vlan-id]
Set the length of time that a dynamic entry remains in the MAC
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, valid IDs are 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
6-21
Chapter 6
Administering the Switch
Managing the MAC Address Table
Removing Dynamic Address Entries
To remove all dynamic entries, use the clear mac address-table dynamic command in privileged EXEC
mode. You can also remove a specific MAC address (clear mac address-table dynamic address
mac-address), remove all addresses on the specified physical port or port channel (clear mac
address-table dynamic interface interface-id), or remove all addresses on a specified VLAN (clear
mac address-table dynamic vlan vlan-id).
To verify that dynamic entries have been removed, use the show mac address-table dynamic privileged
EXEC command.
Configuring MAC Address Notification Traps
MAC address notification enables you to track users on a network by storing the MAC address activity
on the switch. Whenever the switch learns or removes a MAC address, an SNMP notification can be
generated and sent to the NMS. If you have many users coming and going from the network, you can set
a trap interval time to bundle the notification traps and reduce network traffic. The MAC notification
history table stores the MAC address activity for each hardware port for which the trap is enabled. MAC
address notifications are generated for dynamic and secure MAC addresses; events are not generated for
self addresses, multicast addresses, or other static addresses.
Beginning in privileged EXEC mode, follow these steps to configure the switch to send MAC address
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
Enable the switch to send MAC address traps to the
NMS.
Step 4
mac address-table notification
Enable the MAC address notification feature.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
6-22
OL-12189-01
Chapter 6
Administering the Switch
Managing the MAC Address Table
Step 5
Command
Purpose
mac address-table notification [interval value] |
[history-size value]
Enter the trap interval time and the history table size.
(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 {added | removed}
Enable the MAC address notification trap.
Enable the MAC notification trap whenever a
MAC address is added on this interface.
Enable the MAC notification trap whenever a
MAC address is removed from this interface.
Step 8
end
Return to privileged EXEC mode.
Step 9
show mac address-table notification interface
Verify your entries.
show running-config
Step 10
copy running-config startup-config
(Optional) Save your entries in the configuration file.
To disable the switch from sending MAC address notification traps, use the no snmp-server enable
traps mac-notification global configuration command. To disable the MAC address notification traps
on a specific interface, use the no snmp trap mac-notification {added | removed} interface
configuration command. To disable the MAC address notification feature, use the no mac address-table
notification 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 notification feature, set the interval time to
60 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
Switch(config)# snmp-server enable traps mac-notification
Switch(config)# mac address-table notification
Switch(config)# mac address-table notification interval 60
Switch(config)# mac address-table notification history-size 100
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# snmp trap mac-notification added
You can verify the previous commands by entering the show mac address-table notification interface
and the show mac address-table notification privileged EXEC commands.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
6-23
Chapter 6
Administering the Switch
Managing the MAC Address Table
Adding and Removing Static Address Entries
A static address has these characteristics:
It is manually entered in the address table and must be manually removed.
It can be a unicast or multicast address.
It does not age and is retained when the switch restarts.
You can add and remove static addresses and define the forwarding behavior for them. The forwarding
behavior defines how a port that receives a packet forwards it to another port for transmission. Because
all ports are associated with at least one VLAN, the switch acquires the VLAN ID for the address from
the ports that you specify. You can specify a different list of destination ports for each source port.
A packet with a static address that arrives on a VLAN where it has not been statically entered is flooded
to all ports and not learned.
You add a static address to the address table by specifying the destination MAC unicast address and the
VLAN from which it is received. Packets received with this destination address are forwarded to the
interface specified with the interface-id option.
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. Static MAC addresses configured
in a private-VLAN primary or secondary VLAN are not replicated in the associated VLAN. For more
information about private VLANs, see Chapter 15, Configuring Private VLANs.
Beginning in privileged EXEC mode, follow these steps to add a static address:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
mac address-table static mac-addr
vlan vlan-id interface interface-id
Add a static address to the MAC address table.
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. Valid VLAN IDs are 1 to 4094.
For interface-id, specify the interface to which the received packet is
forwarded. Valid interfaces include physical ports or port channels.
For static multicast addresses, you can enter multiple interface IDs.
For static unicast addresses, you can enter only one interface at a
time, but you can enter the command multiple times with the same
MAC address and VLAN ID.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
6-24
OL-12189-01
Chapter 6
Administering the Switch
Managing the MAC Address Table
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 port:
Switch(config)# mac address-table static c2f3.220a.12f4 vlan 4 interface
gigabitethernet1/0/1
Configuring Unicast MAC Address Filtering
When unicast MAC address filtering is enabled, the switch drops packets with specific source or
destination MAC addresses. This feature is disabled by default and only supports unicast static
addresses.
Follow these guidelines when using this feature:
Multicast MAC addresses, broadcast MAC addresses, and router MAC addresses are not supported.
If you specify one of these addresses when entering the mac address-table static mac-addr vlan
vlan-id drop global configuration command, one of these messages appears:
% Only unicast addresses can be configured to be dropped
% CPU destined address cannot be configured as drop address
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
vlan vlan-id drop
Enable unicast MAC address filtering and configure the switch to drop a
packet with the specified source or destination unicast static address.
Step 3
end
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.
Return to privileged EXEC mode.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
6-25
Chapter 6
Administering the Switch
Managing the ARP Table
Command
Purpose
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
Displaying Address Table Entries
You can display the MAC address table by using one or more of the privileged EXEC commands
described in Table 6-4:
Table 6-4
Commands for Displaying the MAC Address Table
Command
Description
show ip igmp snooping groups
Displays the Layer 2 multicast entries for all VLANs or the specified VLAN.
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.
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 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.
Managing the ARP Table
To communicate with a device (over Ethernet, for example), the software first must learn the 48-bit MAC
address or the local data link address of that device. The process of learning the local data link address
from an IP address is called address resolution.
The Address Resolution Protocol (ARP) associates a host IP address with the corresponding media or
MAC addresses and the VLAN ID. Using an IP address, ARP finds the associated MAC address. When
a MAC address is found, the IP-MAC address association is stored in an ARP cache for rapid retrieval.
Then the IP datagram is encapsulated in a link-layer frame and sent over the network. Encapsulation of
IP datagrams and ARP requests and replies on IEEE 802 networks other than Ethernet is specified by
the Subnetwork Access Protocol (SNAP). By default, standard Ethernet-style ARP encapsulation
(represented by the arpa keyword) is enabled on the IP interface.
ARP entries added manually to the table do not age and must be manually removed.
For CLI procedures, see the Cisco IOS Release 12.2 documentation on Cisco.com.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
6-26
OL-12189-01
CH A P T E R
Configuring Switch-Based Authentication
This chapter describes how to configure switch-based authentication on the switch. Unless otherwise
noted, the term switch refers to a standalone switch and to a switch stack.
This chapter 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-10
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
Preventing Unauthorized Access to Your Switch
You can prevent unauthorized users from reconfiguring your switch and viewing configuration
information. Typically, you want network administrators to have access to your switch while you restrict
access to users who dial from outside the network through an asynchronous port, connect from outside
the network through a serial port, or connect through a terminal or workstation from within the local
network.
To prevent unauthorized access into your switch, you should configure one or more of these security
features:
At a minimum, you should configure passwords and privileges at each switch port. These passwords
are locally stored on the switch. When users attempt to access the switch through a port or line, they
must enter the password specified for the port or line before they can access the switch. For more
information, see the Protecting Access to Privileged EXEC Commands section on page 7-2.
For an additional layer of security, you can also configure username and password pairs, which are
locally stored on the switch. These pairs are assigned to lines or ports and authenticate each user
before that user can access the switch. If you have defined privilege levels, you can also assign a
specific privilege level (with associated rights and privileges) to each username and password pair.
For more information, see the Configuring Username and Password Pairs section on page 7-6.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
7-1
Chapter 7
Configuring Switch-Based Authentication
Protecting Access to Privileged EXEC Commands
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-10.
Protecting Access to Privileged EXEC Commands
A simple way of providing terminal access control in your network is to use passwords and assign
privilege levels. Password protection restricts access to a network or network device. Privilege levels
define what commands users can enter after they have logged into a network device.
Note
For complete syntax and usage information for the commands used in this section, see the Cisco IOS
Security Command Reference, Release 12.2.
These sections contain 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
Default Password and Privilege Level Configuration
Table 7-1 shows the default password and privilege level configuration.
Table 7-1
Default Password and Privilege Levels
Feature
Default Setting
Enable password and privilege level
No password is defined. The default is level 15 (privileged EXEC level).
The password is not encrypted in the configuration file.
Enable secret password and privilege level
No password is defined. The default is level 15 (privileged EXEC level).
The password is encrypted before it is written to the configuration file.
Line password
No password is defined.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
7-2
OL-12189-01
Chapter 7
Configuring Switch-Based Authentication
Protecting Access to Privileged EXEC Commands
Setting or Changing a Static Enable Password
The enable password controls access to the privileged EXEC mode. Beginning in privileged EXEC
mode, follow these steps to set or change a static enable password:
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
Protecting Enable and Enable Secret Passwords with Encryption
To provide an additional layer of security, particularly for passwords that cross the network or that are
stored on a Trivial File Transfer Protocol (TFTP) server, you can use either the enable password or
enable secret global configuration commands. Both commands accomplish the same thing; that is, you
can establish an encrypted password that users must enter to access privileged EXEC mode (the default)
or any privilege level you specify.
We recommend that you use the enable secret command because it uses an improved encryption
algorithm.
If you configure the enable secret command, it takes precedence over the enable password command;
the two commands cannot be in effect simultaneously.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
7-3
Chapter 7
Configuring Switch-Based Authentication
Protecting Access to Privileged EXEC Commands
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 |
encryption-type encrypted-password}
Define a new password or change an existing password for
access to privileged EXEC mode.
or
or
enable secret [level level] {password |
encryption-type encrypted-password}
Define a secret password, which is saved using a
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 passwordan encrypted password that you
copy from another switch configuration.
Note
Step 3
service password-encryption
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.
(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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
7-4
OL-12189-01
Chapter 7
Configuring Switch-Based Authentication
Protecting Access to Privileged EXEC Commands
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
Disabling Password Recovery
By default, any end user with physical access to the switch can recover from a lost password by
interrupting the bootup process while the switch is powering on and then by entering a new password.
The password-recovery disable feature protects access to the switch password by disabling part of this
functionality. When this feature is enabled, the end user can interrupt the bootup process only by
agreeing to set the system back to the default configuration. With password recovery disabled, you can
still interrupt the bootup process and change the password, but the configuration file (config.text) and
the VLAN database file (vlan.dat) are deleted.
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 bootup 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 47-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 bootloader 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 command
output.
To re-enable password recovery, use the service password-recovery global configuration command.
Note
Disabling password recovery will not work if you have set the switch to boot up manually by using the
boot manual global configuration command. This command produces the bootloader prompt (switch:)
after the switch is power cycled.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
7-5
Chapter 7
Configuring Switch-Based Authentication
Protecting Access to Privileged EXEC Commands
Setting a Telnet Password for a Terminal Line
When you power-up your switch for the first time, an automatic setup program runs to assign IP
information and to create a default configuration for continued use. The setup program also prompts you
to configure your switch for Telnet access through a password. If you did not configure this password
during the setup program, you can configure it now through the command-line interface (CLI).
Beginning in privileged EXEC mode, follow these steps to configure your switch for Telnet access:
Command
Purpose
Step 1
Attach a PC or workstation with emulation software to the switch console
port, or attach a PC to the Ethernet management 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.
To remove the password, use the no password global configuration command.
This example shows how to set the Telnet password to let45me67in89:
Switch(config)# line vty 10
Switch(config-line)# password let45me67in89
Configuring Username and Password Pairs
You can configure username and password pairs, which are locally stored on the switch. These pairs are
assigned to lines or ports and authenticate each user before that user can access the switch. If you have
defined privilege levels, you can also assign a specific privilege level (with associated rights and
privileges) to each username and password pair.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
7-6
OL-12189-01
Chapter 7
Configuring Switch-Based Authentication
Protecting Access to Privileged EXEC Commands
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]
{password encryption-type password}
Enter the username, privilege level, and password for each user.
Step 3
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.
Enter line configuration mode, and configure the console port (line 0) or
the VTY lines (line 0 to 15).
line console 0
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.
Configuring Multiple Privilege Levels
By default, the Cisco IOS software has two modes of password security: user EXEC and privileged
EXEC. You can configure up to 16 hierarchical levels of commands for each mode. By configuring
multiple passwords, you can allow different sets of users to have access to specified commands.
For example, if you want many users to have access to the clear line command, you can assign it
level 2 security and distribute the level 2 password fairly widely. But if you want more restricted access
to the configure command, you can assign it level 3 security and distribute that password to a more
restricted group of users.
These sections contain this configuration information:
Setting the Privilege Level for a Command, page 7-8
Changing the Default Privilege Level for Lines, page 7-9
Logging into and Exiting a Privilege Level, page 7-9
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
7-7
Chapter 7
Configuring Switch-Based Authentication
Protecting Access to Privileged EXEC Commands
Setting the Privilege Level for a Command
Beginning in privileged EXEC mode, follow these steps to set the privilege level for a command mode:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
privilege mode level level command
Set the privilege level for a command.
Step 3
enable password level level password
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.
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
show privilege
The first command shows the password and access level configuration.
The second command shows the privilege level configuration.
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Step 6
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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
7-8
OL-12189-01
Chapter 7
Configuring Switch-Based Authentication
Protecting Access to Privileged EXEC Commands
Changing the Default Privilege Level for Lines
Beginning in privileged EXEC mode, follow these steps to change the default privilege level for a line:
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
show privilege
The first command shows the password and access level configuration.
The second command shows the privilege level configuration.
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Step 6
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.
Logging into and Exiting a Privilege Level
Beginning in privileged EXEC mode, follow these steps to log in to a specified privilege level and to exit
to a specified privilege level:
Step 1
Command
Purpose
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
7-9
Chapter 7
Configuring Switch-Based Authentication
Controlling Switch Access with TACACS+
Controlling Switch Access with TACACS+
This section describes how to enable and configure Terminal Access Controller Access Control System
Plus (TACACS+), which provides detailed accounting information and flexible administrative control
over authentication and authorization processes. TACACS+ is facilitated through authentication,
authorization, accounting (AAA) and can be enabled only through AAA commands.
Note
For complete syntax and usage information for the commands used in this section, see the Cisco IOS
Security Command Reference, Release 12.2.
These sections contain this configuration information:
Understanding TACACS+, page 7-10
TACACS+ Operation, page 7-12
Configuring TACACS+, page 7-12
Displaying the TACACS+ Configuration, page 7-17
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.
Note
We recommend a redundant connection between a switch stack and the TACACS+ server. This is to help
ensure that the TACACS+ server remains accessible in case one of the connected stack members is
removed from the switch stack.
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
serviceauthentication, authorization, and accountingindependently. 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
7-10
OL-12189-01
Chapter 7
Configuring Switch-Based Authentication
Controlling Switch Access with TACACS+
Figure 7-1
Typical TACACS+ Network Configuration
UNIX workstation
(TACACS+
server 1)
Catalyst 6500
series switch
171.20.10.7
UNIX workstation
(TACACS+
server 2)
Servers
Configure the blade switches with the
TACACS+ server addresses.
Set an authentication key
(also configure the same key on
the TACACS+ servers).
Enable AAA.
Create a login authentication method list.
Apply the list to the terminal lines.
Create an authorization and accounting
method list as required.
201759
171.20.10.8
Servers
TACACS+, administered through the AAA security services, can provide these services:
AuthenticationProvides 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, mothers
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 companys password aging policy.
AuthorizationProvides fine-grained control over user capabilities for the duration of the users
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.
AccountingCollects 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
7-11
Chapter 7
Configuring Switch-Based Authentication
Controlling Switch Access with TACACS+
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 to show 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 dialog 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 users mothers maiden name.
2.
The switch eventually receives one of these responses from the TACACS+ daemon:
ACCEPTThe user is authenticated and service can begin. If the switch is configured to
require authorization, authorization begins at this time.
REJECTThe user is not authenticated. The user can be denied access or is prompted to retry
the login sequence, depending on the TACACS+ daemon.
ERRORAn 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.
CONTINUEThe 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.
These sections contain 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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
7-12
OL-12189-01
Chapter 7
Configuring Switch-Based Authentication
Controlling Switch Access with TACACS+
Configuring TACACS+ Authorization for Privileged EXEC Access and Network Services,
page 7-16
Starting TACACS+ Accounting, page 7-17
Default TACACS+ Configuration
TACACS+ and AAA are disabled by default.
To prevent a lapse in security, you cannot configure TACACS+ through a network management
application. When enabled, TACACS+ can authenticate users accessing the switch through the CLI.
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
integer] [timeout integer] [key string]
Identify the IP host or hosts maintaining a TACACS+ server. Enter this
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
7-13
Chapter 7
Configuring Switch-Based Authentication
Controlling Switch Access with TACACS+
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.
Configuring TACACS+ Login Authentication
To configure AAA authentication, you define a named list of authentication methods and then apply that
list to various ports. The method list defines the types of authentication to be performed and the sequence
in which they are performed; it must be applied to a specific port before any of the defined authentication
methods are performed. The only exception is the default method list (which, by coincidence, is named
default). The default method list is automatically applied to all ports except those that have a named
method list explicitly defined. A defined method list overrides the default method list.
A method list describes the sequence and authentication methods to be queried to authenticate a user.
You can designate one or more security protocols to be used for authentication, thus ensuring a backup
system for authentication in case the initial method fails. The software uses the first method listed to
authenticate users; if that method fails to respond, the software selects the next authentication method in
the method list. This process continues until there is successful communication with a listed
authentication method or until all defined methods are exhausted. If authentication fails at any point in
this cyclemeaning that the security server or local username database responds by denying the user
accessthe authentication process stops, and no other authentication methods are attempted.
Beginning in privileged EXEC mode, follow these steps to configure login authentication:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
aaa new-model
Enable AAA.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
7-14
OL-12189-01
Chapter 7
Configuring Switch-Based Authentication
Controlling Switch Access with TACACS+
Step 3
Command
Purpose
aaa authentication login {default |
list-name} method1 [method2...]
Create a login authentication method list.
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:
enableUse 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.
lineUse 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.
localUse the local username database for authentication. You must
enter username information in the database. Use the username
password global configuration command.
local-caseUse 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.
noneDo not use any authentication for login.
Step 4
line [console | tty | vty] line-number
[ending-line-number]
Enter line configuration mode, and configure the lines to which you want
to apply the authentication list.
Step 5
login authentication {default |
list-name}
Apply the authentication list to a line or set of lines.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
7-15
Chapter 7
Configuring Switch-Based Authentication
Controlling Switch Access with TACACS+
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.
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 users profile, which is located either in the local user
database or on the security server, to configure the users 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 users network access to privileged EXEC mode.
The aaa authorization exec tacacs+ local command sets these authorization parameters:
Note
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+.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
7-16
OL-12189-01
Chapter 7
Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
Starting TACACS+ Accounting
The AAA accounting feature tracks the services that users are accessing and the amount of network
resources that they are consuming. When AAA accounting is enabled, the switch reports user activity to
the TACACS+ security server in the form of accounting records. Each accounting record contains
accounting attribute-value (AV) pairs and is stored on the security server. This data can then be analyzed
for network management, client billing, or auditing.
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
tacacs+
Enable TACACS+ accounting for all network-related service requests.
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.
Displaying the TACACS+ Configuration
To display TACACS+ server statistics, use the show tacacs privileged EXEC command.
Controlling Switch Access with RADIUS
This section describes how to enable and configure the RADIUS, which provides detailed accounting
information and flexible administrative control over authentication and authorization processes.
RADIUS is facilitated through AAA and can be enabled only through AAA commands.
Note
For complete syntax and usage information for the commands used in this section, see the Cisco IOS
Security Command Reference, Release 12.2.
These sections contain this configuration information:
Understanding RADIUS, page 7-18
RADIUS Operation, page 7-19
Configuring RADIUS, page 7-19
Displaying the RADIUS Configuration, page 7-31
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
7-17
Chapter 7
Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
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.
Note
We recommend a redundant connection between a switch stack and the RADIUS server. This is to help
ensure that the RADIUS server remains accessible in case one of the connected stack members is
removed from the switch stack.
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 Enigmas 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 9, 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
7-18
OL-12189-01
Chapter 7
Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
Transitioning from RADIUS to TACACS+ Services
Remote
PC
R1
RADIUS
server
R2
RADIUS
server
T1
TACACS+
server
T2
TACACS+
server
Workstation
86891
Figure 7-2
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. ACCEPTThe user is authenticated.
b. REJECTThe user is either not authenticated and is prompted to re-enter the username and
password, or access is denied.
c. CHALLENGEA challenge requires additional data from the user.
d. CHALLENGE PASSWORDA 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
7-19
Chapter 7
Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
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.
These sections contain 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-31
(optional)
Default RADIUS Configuration
RADIUS and AAA are disabled by default.
To prevent a lapse in security, you cannot configure RADIUS through a network management
application. When enabled, RADIUS can authenticate users accessing the switch through the CLI.
Identifying the RADIUS Server Host
Switch-to-RADIUS-server communication involves several components:
Hostname or IP address
Authentication destination port
Accounting destination port
Key string
Timeout period
Retransmission value
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
7-20
OL-12189-01
Chapter 7
Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
If two different host entries on the same RADIUS server are configured for the same servicefor
example, accountingthe 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 %RADIUS-4-RADIUS_DEAD
message appears, and then 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 settings 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
7-21
Chapter 7
Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
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 |
ip-address} [auth-port port-number]
[acct-port port-number] [timeout
seconds] [retransmit retries] [key
string]
Specify the IP address or hostname of the remote RADIUS server host.
(Optional) For auth-port port-number, specify the UDP destination
port for authentication requests.
(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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
7-22
OL-12189-01
Chapter 7
Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
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.
Configuring RADIUS Login Authentication
To configure AAA authentication, you define a named list of authentication methods and then apply that
list to various ports. The method list defines the types of authentication to be performed and the sequence
in which they are performed; it must be applied to a specific port before any of the defined authentication
methods are performed. The only exception is the default method list (which, by coincidence, is named
default). The default method list is automatically applied to all ports except those that have a named
method list explicitly defined.
A method list describes the sequence and authentication methods to be queried to authenticate a user.
You can designate one or more security protocols to be used for authentication, thus ensuring a backup
system for authentication in case the initial method fails. The software uses the first method listed to
authenticate users; if that method fails to respond, the software selects the next authentication method in
the method list. This process continues until there is successful communication with a listed
authentication method or until all defined methods are exhausted. If authentication fails at any point in
this cyclemeaning that the security server or local username database responds by denying the user
accessthe authentication process stops, and no other authentication methods are attempted.
Beginning in privileged EXEC mode, follow these steps to configure login authentication. This
procedure is required.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
aaa new-model
Enable AAA.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
7-23
Chapter 7
Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
Step 3
Command
Purpose
aaa authentication login {default |
list-name} method1 [method2...]
Create a login authentication method list.
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:
enableUse 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 radiusUse 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.
lineUse 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.
localUse the local username database for authentication. You
must enter username information in the database. Use the
username name password global configuration command.
local-caseUse a case-sensitive local username database for
authentication. You must enter username information in the
database by using the username password global configuration
command.
noneDo not use any authentication for login.
Step 4
line [console | tty | vty] line-number
[ending-line-number]
Enter line configuration mode, and configure the lines to which you want
to apply the authentication list.
Step 5
login authentication {default |
list-name}
Apply the authentication list to a line or set of lines.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
7-24
OL-12189-01
Chapter 7
Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
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.
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.
Defining AAA Server Groups
You can configure the switch to use AAA server groups to group existing server hosts for authentication.
You 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, which lists the IP addresses of the selected server hosts.
Server groups also can include multiple host entries for the same server if each entry has a unique
identifier (the combination of the IP address and UDP port number), allowing different ports to be
individually defined as RADIUS hosts providing a specific AAA service. If you configure two different
host entries on the same RADIUS server for the same service, (for example, accounting), the second
configured host entry acts as a fail-over backup to the first one.
You use the server group server configuration command to associate a particular server with a defined
group server. You can either identify the server by its IP address or identify multiple host instances or
entries by using the optional auth-port and acct-port keywords.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
7-25
Chapter 7
Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
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 |
ip-address} [auth-port port-number]
[acct-port port-number] [timeout
seconds] [retransmit retries] [key
string]
Specify the IP address or hostname of the remote RADIUS server host.
(Optional) For auth-port port-number, specify the UDP destination
port for authentication requests.
(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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
7-26
OL-12189-01
Chapter 7
Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
Step 8
Command
Purpose
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 users profile, which is in the local user database or on the
security server, to configure the users 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 users network access to privileged EXEC mode.
The aaa authorization exec radius local command sets these authorization parameters:
Note
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.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
7-27
Chapter 7
Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
Step 3
Command
Purpose
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.
Starting RADIUS Accounting
The AAA accounting feature tracks the services that users are accessing and the amount of network
resources that they are consuming. When AAA accounting is enabled, the switch reports user activity to
the RADIUS security server in the form of accounting records. Each accounting record contains
accounting attribute-value (AV) pairs and is stored on the security server. This data can then be analyzed
for network management, client billing, or auditing.
Beginning in privileged EXEC mode, follow these steps to enable RADIUS 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
radius
Enable RADIUS accounting for all network-related service requests.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
7-28
OL-12189-01
Chapter 7
Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
Configuring Settings for All RADIUS Servers
Beginning in privileged EXEC mode, follow these steps to configure global communication settings
between the switch and all RADIUS servers:
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.
Configuring the Switch to Use Vendor-Specific RADIUS Attributes
The Internet Engineering Task Force (IETF) draft standard specifies a method for communicating
vendor-specific information between the switch and the RADIUS server by using the vendor-specific
attribute (attribute 26). Vendor-specific attributes (VSAs) allow vendors to support their own extended
attributes not suitable for general use. The Cisco RADIUS implementation supports one vendor-specific
option by using the format recommended in the specification. Ciscos vendor-ID is 9, and the supported
option has vendor-type 1, which is named cisco-avpair. The value is a string with this format:
protocol : attribute sep value *
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
7-29
Chapter 7
Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
For example, this AV pair activates Ciscos 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 an interface 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 an interface 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, see 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 |
authentication]
Enable the switch to recognize and use VSAs as defined by RADIUS IETF
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, see the
RADIUS Attributes appendix in the Cisco IOS Security Configuration Guide, Release 12.2.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
7-30
OL-12189-01
Chapter 7
Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
Configuring the Switch for Vendor-Proprietary RADIUS Server Communication
Although an IETF draft standard for RADIUS specifies a method for communicating vendor-proprietary
information between the switch and the RADIUS server, some vendors have extended the RADIUS
attribute set in a unique way. Cisco IOS software supports a subset of vendor-proprietary RADIUS
attributes.
As mentioned earlier, to configure RADIUS (whether vendor-proprietary or IETF draft-compliant), you
must specify the host running the RADIUS server daemon and the secret text string it shares with the
switch. You specify the RADIUS host and secret text string by using the radius-server global
configuration commands.
Beginning in privileged EXEC mode, follow these steps to specify a vendor-proprietary RADIUS server
host and a shared secret text string:
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
Displaying the RADIUS Configuration
To display the RADIUS configuration, use the show running-config privileged EXEC command.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
7-31
Chapter 7
Configuring Switch-Based Authentication
Controlling Switch Access with Kerberos
Controlling Switch Access with Kerberos
This section describes how to enable and configure the Kerberos security system, which authenticates
requests for network resources by using a trusted third party. To use this feature, the cryptographic (that
is, supports encryption) versions of the switch software must be installed on your switch.
You can download the cryptographic software image from www.ibm.com/support. For more
information, see the release notes for this release.
These sections contain this information:
Understanding Kerberos, page 7-32
Kerberos Operation, page 7-34
Configuring Kerberos, page 7-35
For Kerberos configuration examples, see the Kerberos Configuration Examples section in the
Security Server Protocols chapter of the Cisco IOS Security Configuration Guide, Release 12.2, at this
URL:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuration_guide_book09186a
0080087df1.html
For complete syntax and usage information for the commands used in this section, see the Kerberos
Commands section in the Security Server Protocols chapter of the Cisco IOS Security Command
Reference, Release 12.2, at this URL:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_command_reference_book09186a
0080087e33.html
Note
In the Kerberos configuration examples and in the Cisco IOS Security Command Reference,
Release 12.2, the trusted third party can be a 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 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
7-32
OL-12189-01
Chapter 7
Configuring Switch-Based Authentication
Controlling Switch Access with Kerberos
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).
In this software release, Kerberos supports these network services:
Telnet
rlogin
rsh (Remote Shell Protocol)
Table 7-2 lists the common Kerberos-related terms and definitions:
Table 7-2
Kerberos Terms
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 TGTs1 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 eight hours.
Instance
An authorization level label for Kerberos principals. Most Kerberos
principals are of the form user@REALM (for example,
[email protected]). A Kerberos principal with a Kerberos
instance has the form user/instance@REALM (for example,
smith/[email protected]). 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.
KDC2
Key distribution center 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
Kerberos server
The Kerberos realm name must be in all uppercase characters.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
7-33
Chapter 7
Configuring Switch-Based Authentication
Controlling Switch Access with Kerberos
Table 7-2
Kerberos Terms (continued)
Term
KEYTAB
Definition
3
Principal
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 KEYTAB to decrypt it. In
Kerberos versions earlier than Kerberos 5, KEYTAB is referred to as
SRVTAB4.
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.
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.
1. TGT = ticket granting ticket
2. KDC = key distribution center
3. KEYTAB = key table
4. SRVTAB = server table
Kerberos Operation
A Kerberos server can be a 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 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
Authenticating to a Boundary Switch
This section describes the first layer of security through which a remote user must pass. The user must
first authenticate to the boundary switch. This process then occurs:
1.
The user opens an un-Kerberized Telnet connection to the boundary switch.
2.
The switch prompts the user for a username and password.
3.
The switch requests a TGT from the KDC for this user.
4.
The KDC sends an encrypted TGT that includes the user identity to the switch.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
7-34
OL-12189-01
Chapter 7
Configuring Switch-Based Authentication
Controlling Switch Access with Kerberos
The switch attempts to decrypt the TGT by using the password that the user entered.
If the decryption is successful, the user is authenticated to the switch.
If the decryption is not successful, the user repeats Step 2 either by re-entering the username
and password (noting if Caps Lock or Num Lock is on or off) or by entering a different username
and password.
A remote user who initiates a un-Kerberized Telnet session and authenticates to a boundary switch is
inside the firewall, but the user must still authenticate directly to the KDC before getting access to the
network services. The user must authenticate to the KDC because the TGT that the KDC issues is stored
on the switch and cannot be used for additional authentication until the user logs on to the switch.
Obtaining a TGT from a KDC
This section describes the second layer of security through which a remote user must pass. The user must
now authenticate to a KDC and obtain a TGT from the KDC to access network services.
For instructions about how to authenticate to a KDC, see the Obtaining a TGT from a KDC section in
the Security Server Protocols chapter of the Cisco IOS Security Configuration Guide, Release 12.2, at
this URL:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuration_guide_book09186a
0080087df1.html
Authenticating to Network Services
This section describes the third layer of security through which a remote user must pass. The user with
a TGT must now authenticate to the network services in a Kerberos realm.
For instructions about how to authenticate to a network service, see the Authenticating to Network
Services section in the Security Server Protocols chapter of the Cisco IOS Security Configuration
Guide, Release 12.2, at this URL:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuration_guide_book09186a
0080087df1.html
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:
Note
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.
A Kerberos server can be a switch that is configured as a network security server and that can
authenticate users by using the Kerberos protocol.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
7-35
Chapter 7
Configuring Switch-Based Authentication
Configuring the Switch for Local Authentication and Authorization
To set up a Kerberos-authenticated server-client system, follow these steps:
Configure the KDC by using Kerberos commands.
Configure the switch to use the Kerberos protocol.
For instructions, see the Kerberos Configuration Task List section in the Security Server Protocols
chapter of the Cisco IOS Security Configuration Guide, Release 12.2, at this URL:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuration_guide_chapter0918
6a00800ca7ad.html
Configuring the Switch for Local Authentication and
Authorization
You can configure AAA to operate without a server by setting the switch to implement AAA in local
mode. The switch then handles authentication and authorization. No accounting is available in this
configuration.
Beginning in privileged EXEC mode, follow these steps to configure the switch for local AAA:
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]
{password encryption-type password}
Enter the local database, and establish a username-based authentication
system.
Repeat this command for each user.
Step 7
end
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.
Return to privileged EXEC mode.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
7-36
OL-12189-01
Chapter 7
Configuring Switch-Based Authentication
Configuring the Switch for Secure Shell
Command
Purpose
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.
Configuring the Switch for Secure Shell
This section describes how to configure the Secure Shell (SSH) feature. To use this feature, you must
install the cryptographic (encrypted) software image on your switch.You can download the
cryptographic software image from www.ibm.com/support. For more information, see the release notes
for this release.
These sections contain this information:
Understanding SSH, page 7-37
Configuring SSH, page 7-39
Displaying the SSH Configuration and Status, page 7-41
For SSH configuration examples, see the SSH Configuration Examples section in the Configuring
Secure Shell chapter of the Cisco IOS Security Configuration Guide, Cisco IOS Release 12.2, at
this URL:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuration_guide_chapter0918
6a00800ca7d5.html
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/products/sw/iosswrel/ps1835/products_command_reference_book09186a
0080087e33.html
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).
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
7-37
Chapter 7
Configuring Switch-Based Authentication
Configuring the Switch for Secure Shell
This section consists of these topics:
Note
SSH Servers, Integrated Clients, and Supported Versions, page 7-38
Limitations, page 7-38
The SSH connection to the stack can be lost if a stack master running the cryptographic software image
and the IP base or the IP services feature set fails and is replaced by a switch that is running a
noncryptographic image and the same feature set. We recommend that a switch running the
cryptographic software image and the IP base or IP services feature set be the stack master. Encryption
features are unavailable if the stack master is running the noncryptographic software image and the
feature set.
SSH Servers, Integrated Clients, and Supported Versions
The SSH feature has an SSH server and an SSH integrated client, which are applications that run on the
switch. You can use an SSH client to connect to a switch running the SSH server. The SSH server works
with the SSH client supported in this release and with non-Cisco SSH clients. The SSH client also works
with the SSH server supported in this release and with non-Cisco SSH servers.
The switch supports an SSHv1 or an SSHv2 server.
The switch supports an SSHv1 client.
SSH supports the Data Encryption Standard (DES) encryption algorithm, the Triple DES (3DES)
encryption algorithm, and password-based user authentication.
SSH also supports these user authentication methods:
Note
TACACS+ (for more information, see the Controlling Switch Access with TACACS+ section on
page 7-10)
RADIUS (for more information, see the Controlling Switch Access with RADIUS section on
page 7-17)
Local authentication and authorization (for more information, see the Configuring the Switch for
Local Authentication and Authorization section on page 7-36)
This software release does not support IP Security (IPSec).
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 does not support the Advanced Encryption Standard (AES) symmetric encryption
algorithm.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
7-38
OL-12189-01
Chapter 7
Configuring Switch-Based Authentication
Configuring the Switch for Secure Shell
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 the SSH server is running on a stack master and the stack master fails, the new stack master uses
the RSA key pair generated by the previous stack master.
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.
Setting Up the Switch to Run SSH
Follow these steps to set up your switch to run SSH:
1.
Download the cryptographic software image from www.ibm.com/support. This step is required. For
more information, see the release notes for this release.
2.
Configure a hostname and IP domain name for the switch. Follow this procedure only if you are
configuring the switch as an SSH server.
3.
Generate an RSA key pair for the switch, which automatically enables SSH. Follow this procedure
only if you are configuring the switch as an SSH server.
4.
Configure user authentication for local or remote access. This step is required. For more
information, see the Configuring the Switch for Local Authentication and Authorization section
on page 7-36.
Beginning in privileged EXEC mode, follow these steps to configure a hostname and an IP domain name
and to generate an RSA key pair. This procedure is required if you are configuring the switch as an SSH
server.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
hostname hostname
Configure a hostname for your switch.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
7-39
Chapter 7
Configuring Switch-Based Authentication
Configuring the Switch for Secure Shell
Command
Purpose
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.
Step 6
show ip ssh
Show the version and configuration information for your SSH server.
or
Step 7
show ssh
Show the status of the SSH server on the switch.
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.
Configuring the SSH Server
Beginning in privileged EXEC mode, follow these steps to configure the SSH server:
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.
1Configure the switch to run SSH Version 1.
2Configure 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 |
authentication-retries number}
Configure the SSH control parameters:
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
7-40
OL-12189-01
Chapter 7
Configuring Switch-Based Authentication
Configuring the Switch for Secure Socket Layer HTTP
Step 4
Command
Purpose
line vty line_number
[ending_line_number]
(Optional) Configure the virtual terminal line settings.
Enter line configuration mode to configure the virtual terminal line
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.
transport input ssh
Step 5
end
Return to privileged EXEC mode.
Step 6
show ip ssh
Show the version and configuration information for your SSH server.
or
Step 7
show ssh
Show the status of the SSH server connections on the switch.
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.
Displaying the SSH Configuration and Status
To display the SSH server configuration and status, use one or more of the privileged EXEC commands
in Table 7-3:
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/products/sw/iosswrel/ps1835/products_command_reference_book09186a
0080087e33.html
Configuring the Switch for Secure Socket Layer HTTP
This section describes how to configure Secure Socket Layer (SSL) Version 3.0 support for the
HTTP 1.1 server and client. SSL provides server authentication, encryption, and message integrity, as
well as HTTP client authentication, to allow secure HTTP communications.To use this feature, the
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
7-41
Chapter 7
Configuring Switch-Based Authentication
Configuring the Switch for Secure Socket Layer HTTP
cryptographic (encrypted) software image must be installed on your switch. You can download the
cryptographic software image from www.ibm.com/support. For more information about the
cryptographic image, see the release notes for this release.
These sections contain this information:
Understanding Secure HTTP Servers and Clients, page 7-42
Configuring Secure HTTP Servers and Clients, page 7-44
Displaying Secure HTTP Server and Client Status, page 7-48
For configuration examples and complete syntax and usage information for the commands used in this
section, see the HTTPS - HTTP Server and Client with SSL 3.0 feature description for Cisco IOS
Release 12.2(15)T at this URL:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1839/products_feature_guide09186a008015a4c6.
html
Understanding Secure HTTP Servers and Clients
On a secure HTTP connection, data to and from an HTTP server is encrypted before being sent over the
Internet. HTTP with SSL encryption provides a secure connection to allow such functions as configuring
a switch from a Web browser. Cisco's implementation of the secure HTTP server and secure HTTP client
uses an implementation of SSL Version 3.0 with application-layer encryption. HTTP over SSL is
abbreviated as HTTPS; the URL of a secure connection begins with https:// instead of http://.
The primary role of the HTTP secure server (the switch) is to listen for HTTPS requests on a designated
port (the default HTTPS port is 443) and pass the request to the HTTP 1.1 Web server. The HTTP 1.1
server processes requests and passes responses (pages) back to the HTTP secure server, which, in turn,
responds to the original request.
The primary role of the HTTP secure client (the web browser) is to respond to Cisco IOS application
requests for HTTPS User Agent services, perform HTTPS User Agent services for the application, and
pass the response back to the application.
Certificate Authority Trustpoints
Certificate authorities (CAs) manage certificate requests and issue certificates to participating network
devices. These services provide centralized security key and certificate management for the participating
devices. Specific CA servers are referred to as trustpoints.
When a connection attempt is made, the HTTPS server provides a secure connection by issuing a
certified X.509v3 certificate, obtained from a specified CA trustpoint, to the client. The client (usually
a Web browser), in turn, has a public key that allows it to authenticate the certificate.
For secure HTTP connections, we highly recommend that you configure a CA trustpoint. If a CA
trustpoint is not configured for the device running the HTTPS server, the server certifies itself and
generates the needed RSA key pair. Because a self-certified (self-signed) certificate does not provide
adequate security, the connecting client generates a notification that the certificate is self-certified, and
the user has the opportunity to accept or reject the connection. This option is useful for internal network
topologies (such as testing).
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
7-42
OL-12189-01
Chapter 7
Configuring Switch-Based Authentication
Configuring the Switch for Secure Socket Layer HTTP
If you do not configure a CA trustpoint, when you enable a secure HTTP connection, either a temporary
or a persistent self-signed certificate for the secure HTTP server (or client) is automatically generated.
If the switch is not configured with a hostname and a domain name, a temporary self-signed
certificate is generated. If the switch reboots, any temporary self-signed certificate is lost, and a new
temporary new self-signed certificate is assigned.
If the switch has been configured with a host and domain name, a persistent self-signed certificate
is generated. This certificate remains active if you reboot the switch or if you disable the secure
HTTP server so that it will be there the next time you re-enable a secure HTTP connection.
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>
crypto pki trustpoint TP-self-signed-3080755072
enrollment selfsigned
subject-name cn=IOS-Self-Signed-Certificate-3080755072
revocation-check none
rsakeypair TP-self-signed-3080755072
!
!
crypto ca certificate chain TP-self-signed-3080755072
certificate self-signed 01
3082029F 30820208 A0030201 02020101 300D0609 2A864886
59312F30 2D060355 04031326 494F532D 53656C66 2D536967
69666963 6174652D 33303830 37353530 37323126 30240609
02161743 45322D33 3535302D 31332E73 756D6D30 342D3335
30333031 30303030 35395A17 0D323030 31303130 30303030
F70D0101
6E65642D
2A864886
3530301E
305A3059
04050030
43657274
F70D0109
170D3933
312F302D
<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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
7-43
Chapter 7
Configuring Switch-Based Authentication
Configuring the Switch for Secure Socket Layer HTTP
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_SHARSA key exchange (RSA Public Key Cryptography) with
DES-CBC for message encryption and SHA for message digest
2.
SSL_RSA_WITH_RC4_128_MD5RSA key exchange with RC4 128-bit encryption and MD5 for
message digest
3.
SSL_RSA_WITH_RC4_128_SHARSA key exchange with RC4 128-bit encryption and SHA for
message digest
4.
SSL_RSA_WITH_3DES_EDE_CBC_SHARSA key exchange with 3DES and DES-EDE3-CBC
for message encryption and SHA for message digest
RSA (in conjunction with the specified encryption and digest algorithm combinations) is used for both
key generation and authentication on SSL connections. This usage is independent of whether or not a
CA trustpoint is configured.
Configuring Secure HTTP Servers and Clients
These sections contain this configuration information:
Default SSL Configuration, page 7-44
SSL Configuration Guidelines, page 7-44
Configuring a CA Trustpoint, page 7-45
Configuring the Secure HTTP Server, page 7-45
Configuring the Secure HTTP Client, page 7-47
Default SSL Configuration
The standard HTTP server is enabled.
SSL is enabled.
No CA trustpoints are configured.
No self-signed certificates are generated.
SSL Configuration Guidelines
Before you configure a CA trustpoint, you should ensure that the system clock is set. If the clock is not
set, the certificate is rejected due to an incorrect date.
In a switch stack, the SSL session terminates at the stack master.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
7-44
OL-12189-01
Chapter 7
Configuring Switch-Based Authentication
Configuring the Switch for Secure Socket Layer HTTP
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.
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
port-number
(Optional) Configure the switch to obtain certificates from the CA
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.
Configuring the Secure HTTP Server
If you are using a certificate authority for certification, you should use the previous procedure to
configure the CA trustpoint on the switch before enabling the HTTP server. If you have not configured
a CA trustpoint, a self-signed certificate is generated the first time that you enable the secure HTTP
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
7-45
Chapter 7
Configuring Switch-Based Authentication
Configuring the Switch for Secure Socket Layer HTTP
server. After you have configured the server, you can configure options (path, access list to apply,
maximum number of connections, or timeout policy) that apply to both standard and secure HTTP
servers.
Beginning in privileged EXEC mode, follow these steps to configure a secure HTTP server:
Step 1
Command
Purpose
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.
ip http secure-ciphersuite
{[3des-ede-cbc-sha] [rc4-128-md5]
[rc4-128-sha] [des-cbc-sha]}
(Optional) Specify the CipherSuites (encryption algorithms) to be used
for encryption over the HTTPS connection. If you do not have a reason to
specify a particularly CipherSuite, you should allow the server and client
to negotiate a CipherSuite that they both support. This is the default.
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.
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.
Step 5
Step 6
Step 7
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:
idlethe 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).
lifethe 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.
requeststhe maximum number of requests processed on a
persistent connection. The maximum value is 86400. The default is 1.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
7-46
OL-12189-01
Chapter 7
Configuring Switch-Based Authentication
Configuring the Switch for Secure Socket Layer HTTP
Command
Purpose
Step 12
end
Return to privileged EXEC mode.
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
Configuring the Secure HTTP Client
The standard HTTP client and secure HTTP client are always enabled. A certificate authority is required
for secure HTTP client certification. This procedure assumes that you have previously configured a CA
trustpoint on the switch. If a CA trustpoint is not configured and the remote HTTPS server requires client
authentication, connections to the secure HTTP client fail.
Beginning in privileged EXEC mode, follow these steps to configure a secure HTTP client:
Command
Purpose
configure terminal
Enter global configuration mode.
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
{[3des-ede-cbc-sha] [rc4-128-md5]
[rc4-128-sha] [des-cbc-sha]}
(Optional) Specify the CipherSuites (encryption algorithms) to be used
for encryption over the HTTPS connection. If you do not have a reason to
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.
Step 1
Step 2
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
7-47
Chapter 7
Configuring Switch-Based Authentication
Configuring the Switch for Secure Copy Protocol
Displaying Secure HTTP Server and Client Status
To display the SSL secure server and client status, use the privileged EXEC commands in Table 7-4:
Table 7-4
Commands for Displaying the SSL Secure Server and Client Status
Command
Purpose
show ip http client
secure status
Shows the HTTP secure client configuration.
show ip http server
secure status
Shows the HTTP secure server configuration.
show running-config
Shows the generated self-signed certificate for secure HTTP connections.
Configuring the Switch for Secure Copy Protocol
The Secure Copy Protocol (SCP) feature provides a secure and authenticated method for copying switch
configurations or switch image files. SCP relies on Secure Shell (SSH), an application and a protocol
that provides a secure replacement for the Berkeley r-tools.
For SSH to work, the switch needs an RSA public/private key pair. This is the same with SCP, which
relies on SSH for its secure transport.
Because SSH also relies on AAA authentication, and SCP relies further on AAA authorization, correct
configuration is necessary.
Note
Before enabling SCP, you must correctly configure SSH, authentication, and authorization on the
switch.
Because SCP relies on SSH for its secure transport, the router must have an Rivest, Shamir, and
Adelman (RSA) key pair.
When using SCP, you cannot enter the password into the copy command. You must enter the password
when prompted.
Information About Secure Copy
To configure Secure Copy feature, you should understand these concepts.
The behavior of SCP is similar to that of remote copy (rcp), which comes from the Berkeley r-tools suite,
except that SCP relies on SSH for security. SCP also requires that authentication, authorization, and
accounting (AAA) authorization be configured so the router can determine whether the user has the
correct privilege level.
A user who has appropriate authorization can use SCP to copy any file in the Cisco IOS File System
(IFS) to and from a switch by using the copy command. An authorized administrator can also do this
from a workstation.
For more information on how to configure and verify SCP, see the Secure Copy Protocol chapter of
the Feature Guides, Cisco IOS Software Releases 12.2T, at this URL:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1839/products_feature_guide09186a0080087b18
.html
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
7-48
OL-12189-01
CH A P T E R
Configuring SDM Templates
This chapter describes how to configure the Switch Database Management (SDM) templates on the
switch. Unless otherwise noted, the term switch refers to a standalone switch and to a switch stack.
Note
For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
This chapter consists of these sections:
Understanding the SDM Templates, page 8-1
Configuring the Switch SDM Template, page 8-4
Displaying the SDM Templates, page 8-6
Understanding the SDM Templates
You can use SDM templates to configure system resources in the switch to optimize support for specific
features, depending on how the switch is used in the network. You can select a template to provide
maximum system usage for some functions; for example, use the default template to balance resources,
and use access template to obtain maximum ACL usage.
To allocate hardware resources for different usages, the switch SDM templates prioritize system
resources to optimize support for certain features. You can select SDM templates for IP Version 4 (IPv4)
to optimize these features:
RoutingThe routing template maximizes system resources for unicast routing, typically required
for a router in the center of a network.
VLANsThe VLAN template disables routing and supports the maximum number of unicast MAC
addresses. It would typically be selected for a Layer 2 switch.
DefaultThe default template gives balance to all functions.
AccessThe access template maximizes system resources for access control lists (ACLs) to
accommodate a large number of ACLs.
On the Catalyst Switch Module 3012, you can also select a dual IPv4 and IPv6 template to support a a
dual-stack environment. See the Dual IPv4 and IPv6 SDM Templates section on page 8-2. You must
enable a dual-stack template to configure IPv6 host or IPv6 Multicast Listener Discovery (MLD)
snooping.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
8-1
Chapter 8
Configuring SDM Templates
Understanding the SDM Templates
Table 8-1 lists the approximate numbers of each resource supported in each of the four templates.
Table 8-1
Approximate Number of Feature Resources Allowed by Each Template
Resource
Access
Default
Routing
VLAN
Unicast MAC addresses
4K
6K
3K
12 K
IGMP groups and multicast routes
1K
1K
1K
1K
Unicast routes
6K
8K
11 K
Directly connected hosts
4K
6K
3K
Indirect routes
2K
2K
8K
0.5 K
0.5 K
QoS classification ACEs
0.5 K
0.5 K
0.5 K
0.5 K
Security ACEs
2K
1K
1K
1K
VLANs
1K
1K
1K
1K
Policy-based routing ACEs
1. Policy-based routing is not supported on the Catalyst Switch Module 3012.
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.
Dual IPv4 and IPv6 SDM Templates
You can select SDM templates to support IP Version 6 (IPv6). For more information about IPv6 and how
to configure IPv6 host functions and unicast routing, see Chapter 39, Configuring IPv6 Host Functions
and Unicast Routing.
This software release does not support IPv6 multicast routing and QoS on the Catalyst Switch
Module 3110.
This software release does not support policy-based routing (PBR) when forwarding IPv6 traffic on the
Catalyst Switch Module 3110. The software supports IPv4 PBR only when the dual-ipv4-and-ipv6
routing template is configured.
The Catalyst Switch Module 3012 supports IPv6 host functions and MLD snooping.
The dual IPv4 and IPv6 templates allow the switch to be used in dual stack environments (supporting
both IPv4 and IPv6). Using the dual stack templates results in less hardware capacity allowed for each
resource. Do not use them if you plan to forward only IPv4 traffic. These SDM templates support IPv4
and IPv6 environments:
Dual IPv4 and IPv6 default templatesupports Layer 2, multicast, routing, QoS, and ACLs for
IPv4; and Layer 2, routing, and ACLs for IPv6 on the switch.
Dual IPv4 and IPv6 routing templatesupports Layer 2, multicast, routing (including policy-based
routing), QoS, and ACLs for IPv4; and Layer 2, routing, and ACLs for IPv6 on the switch.
Dual IPv4 and IPv6 VLAN templatesupports basic Layer 2, multicast, QoS, and ACLs for IPv4,
and basic Layer 2 and ACLs for IPv6 on the switch.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
8-2
OL-12189-01
Chapter 8
Configuring SDM Templates
Understanding the SDM Templates
Table 8-2 defines the approximate feature resources allocated by each dual IPv4 and IPv6 template.
Template estimations are based on a switch with 8 routed interfaces and 1024 VLANs.
Table 8-2
Approximate Feature Resources Allowed by Dual IPv4-IPv6 Templates
Resource
IPv4-and-IPv6
Default
IPv4-and-IPv6
Routing
IPv4-and-IPv6
VLAN
Unicast MAC addresses
2K
1.5 K
8K
IPv4 IGMP groups and multicast routes
1K
1K
1 K for IGMP
groups
0 for multicast
routes
Total IPv4 unicast routes:
3K
2.75 K
Directly connected IPv4 hosts
2K
1.5 K
Indirect IPv4 routes
1K
1.25 K
IPv6 multicast groups
1K
1K
1K
Directly connected IPv6 addresses
2K
1.5 K
Indirect IPv6 unicast routes
1K
1.25 K
IPv4 policy-based routing ACEs1
0.25 K
IPv4 or MAC QoS ACEs (total)
0.5 K
0.5 K
0.5 K
IPv4 or MAC security ACEs (total)
1K
0.5 K
1K
IPv6 security ACEs
0.5 K
0.5 K
0.5 K
1. Policy-based routing is not supported on the Catalyst Switch Module 3012.
SDM Templates and Switch Stacks
All stack members must use the same SDM desktop template that is stored on the stack master. When a
new switch is added to a stack, the SDM configuration that is stored on the stack master overrides the
template configured on an individual switch. For more information about stacking, see Chapter 5,
Managing Switch Stacks.
You can use the show switch privileged EXEC command to see if any stack members are in SDM
mismatch mode. This example shows the output from the show switch privileged EXEC command when
an SDM mismatch exists:
Switch# show switch
Current
Switch# Role
Mac Address
Priority
State
-----------------------------------------------------------*2
Master
000a.fdfd.0100
5
Ready
4
Member
0003.fd63.9c00
SDM Mismatch
This is an example of a syslog message notifying the stack master that a stack member is in SDM
mismatch mode:
2d23h:%STACKMGR-6-SWITCH_ADDED_SDM:Switch 2 has been ADDED to the stack (SDM_MISMATCH)
2d23h:%SDM-6-MISMATCH_ADVISE:
2d23h:%SDM-6-MISMATCH_ADVISE:
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
8-3
Chapter 8
Configuring SDM Templates
Configuring the Switch SDM Template
2d23h:%SDM-6-MISMATCH_ADVISE:System (#2) is incompatible with the SDM
2d23h:%SDM-6-MISMATCH_ADVISE:template currently running on the stack and
2d23h:%SDM-6-MISMATCH_ADVISE:will not function unless the stack is
2d23h:%SDM-6-MISMATCH_ADVISE:downgraded. Issuing the following commands
2d23h:%SDM-6-MISMATCH_ADVISE:will downgrade the stack to use a smaller
2d23h:%SDM-6-MISMATCH_ADVISE:compatible desktop SDM template:
2d23h:%SDM-6-MISMATCH_ADVISE:
2d23h:%SDM-6-MISMATCH_ADVISE:
"sdm prefer vlan desktop"
2d23h:%SDM-6-MISMATCH_ADVISE:
"reload"
Configuring the Switch SDM Template
These sections contain this configuration information:
Default SDM Template, page 8-4
SDM Template Configuration Guidelines, page 8-4
Setting the SDM Template, page 8-5
Default SDM Template
The default template is the default Switch Database Management (SDM) desktop template.
SDM Template Configuration Guidelines
Follow these guidelines when selecting and configuring SDM templates:
You must reload the switch for the configuration to take effect.
Use the sdm prefer vlan global configuration command only on switches intended for Layer 2
switching with no routing.
When you use the VLAN template, no system resources are reserved for routing entries, and any
routing is done through software. This overloads the CPU and severely degrades routing
performance.
Do not use the routing template if you do not have routing enabled on your switch. To prevent other
features from using the memory allocated to unicast routing in the routing template, use the sdm
prefer routing global configuration command.
If you try to configure IPv6 without first selecting a dual IPv4 and IPv6 template, a warning message
appears.
Using the dual stack template results in less hardware capacity allowed for each resource, so do not
use it if you plan to forward only IPv4 traffic.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
8-4
OL-12189-01
Chapter 8
Configuring SDM Templates
Configuring the Switch SDM Template
Setting the SDM Template
Beginning in privileged EXEC mode, follow these steps to use the SDM template to maximize feature
usage:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
sdm prefer {access | default |
dual-ipv4-and-ipv6 {default | routing |
vlan} | routing | vlan}
Specify the SDM template to be used on the switch:
The keywords have these meanings:
accessMaximize system resources for ACLs.
defaultGive balance to all functions.
dual-ipv4-and-ipv6Select a template that supports both IPv4
and IPv6 routing.
defaultBalance IPv4 and IPv6 Layer 2 and Layer 3
functionality.
routingProvide maximum usage for IPv4 and IPv6
routing, including IPv4 policy-based routing.
vlanProvide maximum usage for IPv4 and IPv6 VLANs.
routingMaximize routing on the switch.
vlanMaximize VLAN configuration on the switch with no
routing supported in hardware.
Use the no sdm prefer command to reset the switch to the default
desktop template. The default template balances the use of system
resources.
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.
number of unicast mac addresses:
number of igmp groups + multicast routes:
number of unicast routes:
number of directly connected hosts:
number of indirect routes:
number of qos aces:
number of security aces:
3K
1K
11K
3K
8K
0.5K
1K
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
8-5
Chapter 8
Configuring SDM Templates
Displaying the SDM Templates
On next reload, template will be desktop vlan template.
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 example shows how to configure the IPv4-and-IPv6 default template:
Switch(config)# sdm prefer dual-ipv4-and-ipv6 default
Switch(config)# exit
Switch# reload
Proceed with reload? [confirm]
Displaying the SDM Templates
Use the show sdm prefer privileged EXEC command with no parameters to display the active template.
To display the resource numbers supported by the specified template, use the show sdm prefer [access
| default | dual-ipv4-and-ipv6 {default | vlan} |routing | vlan] privileged EXEC command.
This is an example of output from the show sdm prefer command that displays the template in use.
Switch# show sdm prefer
The current template is "desktop default" template.
The selected template optimizes the resources in
the switch to support this level of features for
8 routed interfaces and 1024 VLANs.
number of unicast mac addresses:
number of igmp groups + multicast routes:
number of unicast routes:
number of directly connected hosts:
number of indirect routes:
number of policy based routing aces:
number of qos aces:
number of security aces:
6K
1K
8K
6K
2K
0
0.5K
1K
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.
number of unicast mac addresses:
number of igmp groups + multicast routes:
number of unicast routes:
number of directly connected hosts:
number of indirect routes:
number of policy based routing aces:
number of qos aces:
number of security aces:
3K
1K
11K
3K
8K
0.5K
0.5K
1K
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
8-6
OL-12189-01
Chapter 8
Configuring SDM Templates
Displaying the SDM Templates
This is an example of output from the show sdm prefer dual-ipv4-and-ipv6 routing command:
Switch# show sdm prefer dual-ipv4-and-ipv6 routing
The current template is "desktop IPv4 and IPv6 routing" template.
The selected template optimizes the resources in the switch to support this level of
features for 8 routed interfaces and 1024 VLANs.
number of unicast mac addresses:
number of IPv4 IGMP groups + multicast routes:
number of IPv4 unicast routes:
number of directly-connected IPv4 hosts:
number of indirect IPv4 routes:
number of IPv6 multicast groups:
number of directly-connected IPv6 addresses:
number of indirect IPv6 unicast routes:
number of IPv4 policy based routing aces:
number of IPv4/MAC qos aces:
number of IPv4/MAC security aces:
number of IPv6 policy based routing aces:
number of IPv6 qos aces:
number of IPv6 security aces:
1.5K
1K
2.75K
1.5K
1.25K
1K
1.5K
1.25K
0.25K
0.5K
0.5K
0.25K
0.5K
0.5K
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
8-7
Chapter 8
Configuring SDM Templates
Displaying the SDM Templates
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
8-8
OL-12189-01
CH A P T E R
Configuring IEEE 802.1x Port-Based
Authentication
This chapter describes how to configure IEEE 802.1x port-based authentication on the switch.
IEEE 802.1x authentication prevents unauthorized devices (clients) from gaining access to the
network.Unless otherwise noted, the term switch refers to a standalone switch and to a switch stack.
Note
For complete syntax and usage information for the commands used in this chapter, see the RADIUS
Commands section in the Cisco IOS Security Command Reference, Release 12.2 and the command
reference or this release.
This chapter consists of these sections:
Understanding IEEE 802.1x Port-Based Authentication, page 9-1
Configuring IEEE 802.1x Authentication, page 9-22
Displaying IEEE 802.1x Statistics and Status, page 9-45
Understanding IEEE 802.1x Port-Based Authentication
The IEEE 802.1x standard defines a client-server-based access control and authentication protocol that
prevents unauthorized clients from connecting to a LAN through publicly accessible ports unless they
are properly authenticated. The authentication server authenticates each client connected to a switch port
before making available any services offered by the switch or the LAN.
Until the client is authenticated, IEEE 802.1x access control allows only Extensible Authentication
Protocol over LAN (EAPOL), Cisco Discovery Protocol (CDP), and Spanning Tree Protocol (STP)
traffic through the port to which the client is connected. After authentication is successful, normal traffic
can pass through the port.
These sections describe IEEE 802.1x port-based authentication:
Device Roles, page 9-2
Authentication Process, page 9-3
Authentication Initiation and Message Exchange, page 9-5
Ports in Authorized and Unauthorized States, page 9-7
IEEE 802.1x Authentication and Switch Stacks, page 9-8
IEEE 802.1x Host Mode, page 9-8
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
9-1
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
IEEE 802.1x Accounting, page 9-9
IEEE 802.1x Accounting Attribute-Value Pairs, page 9-9
Using IEEE 802.1x Authentication with VLAN Assignment, page 9-10
Using IEEE 802.1x Authentication with Per-User ACLs, page 9-12
Using IEEE 802.1x Authentication with Guest VLAN, page 9-13
Using IEEE 802.1x Authentication with Restricted VLAN, page 9-14
Using IEEE 802.1x Authentication with Inaccessible Authentication Bypass, page 9-15
Using IEEE 802.1x Authentication with Voice VLAN Ports, page 9-16
Using IEEE 802.1x Authentication with Port Security, page 9-17
Using IEEE 802.1x Authentication with Wake-on-LAN, page 9-18
Using IEEE 802.1x Authentication with MAC Authentication Bypass, page 9-18
Network Admission Control Layer 2 IEEE 802.1x Validation, page 9-20
Using Multidomain Authentication, page 9-20
Using Web Authentication, page 9-21
Device Roles
With IEEE 802.1x port-based authentication, the devices in the network have specific roles as shown in
Figure 9-1.
Figure 9-1
IEEE 802.1x Device Roles
Blade
switch
Authentication
server
(RADIUS)
201760
Servers
Clientthe 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 standard.)
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 serverperforms the actual authentication of the client. The authentication server
validates the identity of the client and notifies the switch whether or not the client is authorized to
access the LAN and switch services. Because the switch acts as the proxy, the authentication service
is transparent to the client. In this release, the RADIUS security system with Extensible
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
9-2
OL-12189-01
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
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. (The switch is the authenticator in the IEEE 802.1x
standard.)
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 during encapsulation, and the authentication server must support EAP
within the native frame format. When the switch receives frames from the authentication server, the
servers frame header is removed, leaving the EAP frame, which is then encapsulated for Ethernet
and sent to the client.
The devices that can act as intermediaries include the Catalyst 3750-E, Catalyst 3750,
Catalyst 3560-E, Catalyst 3560, Catalyst 3550, Catalyst 2970, Catalyst 2960, 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 authentication.
Authentication Process
When IEEE 802.1x port-based authentication is enabled and the client supports IEEE 802.1x-compliant
client software, these events occur:
If the client identity is valid and the IEEE 802.1x authentication succeeds, the switch grants the
client access to the network.
If IEEE 802.1x authentication times out while waiting for an EAPOL message exchange and MAC
authentication bypass is enabled, the switch can use the client MAC address for authorization. If the
client MAC address is valid and the authorization succeeds, the switch grants the client access to the
network. If the client MAC address is invalid and the authorization fails, the switch assigns the client
to a guest VLAN that provides limited services if a guest VLAN is configured.
If the switch gets an invalid identity from an IEEE 802.1x-capable client and a restricted VLAN is
specified, the switch can assign the client to a restricted VLAN that provides limited services.
If the RADIUS authentication server is unavailable (down) and inaccessible authentication bypass
is enabled, the switch grants the client access to the network by putting the port in the
critical-authentication state in the RADIUS-configured or the user-specified access VLAN.
Note
Inaccessible authentication bypass is also referred to as critical authentication or the AAA fail
policy.
Figure 9-2 shows the authentication process.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
9-3
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
If Multi Domain Authentication (MDA) is enabled on a port, this flow can be used with some exceptions
that are applicable to voice authorization. For more information on MDA, see the Using Multidomain
Authentication section on page 9-20.
Figure 9-2
Authentication Flowchart
Start
IEEE 802.1x authentication
process times out.
Is MAC authentication
bypass enabled? 1
Yes
Yes
Start IEEE 802.1x port-based
authentication.
Client
identity is
invalid
The switch gets an
EAPOL message,
and the EAPOL
message
exchange begins.
Client
identity is
valid
No
Use MAC authentication
bypass. 1
Client MAC
address
identity
is valid.
Client MAC
address
identity
is invalid.
Assign the port to
a restricted VLAN.
Assign the port to
a VLAN.
Assign the port to
a VLAN.
Assign the port to
a guest VLAN. 1
Done
Done
Done
Done
All authentication
servers are down.
141679
No
Is the client IEEE
802.1x capable?
All authentication
servers are down.
Use inaccessible
authentication bypass
(critical authentication)
to assign the critical
port to a VLAN.
Done
1 = This occurs if the switch does not detect EAPOL packets from the client.
The switch re-authenticates a client when one of these situations occurs:
Periodic re-authentication is enabled, and the re-authentication timer expires.
You can configure the re-authentication timer to use a switch-specific value or to be based on values
from the RADIUS server.
After IEEE 802.1x authentication using a RADIUS server is configured, the switch uses timers
based on the Session-Timeout RADIUS attribute (Attribute[27]) and the Termination-Action
RADIUS attribute (Attribute [29]).
The Session-Timeout RADIUS attribute (Attribute[27]) specifies the time after which
re-authentication occurs.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
9-4
OL-12189-01
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
The Termination-Action RADIUS attribute (Attribute [29]) specifies the action to take during
re-authentication. The actions are Initialize and ReAuthenticate. When the Initialize action is set (the
attribute value is DEFAULT), the IEEE 802.1x session ends, and connectivity is lost during
re-authentication. When the ReAuthenticate action is set (the attribute value is RADIUS-Request),
the session is not affected during re-authentication.
You manually re-authenticate the client by entering the dot1x re-authenticate interface
interface-id privileged EXEC command.
Authentication Initiation and Message Exchange
During IEEE 802.1x authentication, the switch or the client can initiate authentication. If you enable
authentication on a port by using the dot1x port-control auto interface configuration command, the
switch initiates authentication when the link state changes from down to up or periodically as long as
the port remains up and unauthenticated. The switch sends an EAP-request/identity frame to the client
to request its identity. Upon receipt of the frame, the client responds with an EAP-response/identity
frame.
However, if during bootup, the client does not receive an EAP-request/identity frame from the switch,
the client can initiate authentication by sending an EAPOL-start frame, which prompts the switch to
request the clients identity.
Note
If IEEE 802.1x authentication 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 9-7.
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. If the authentication fails, authentication
can be retried, the port might be assigned to a VLAN that provides limited services, or network access
is not granted. For more information, see the Ports in Authorized and Unauthorized States section on
page 9-7.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
9-5
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
The specific exchange of EAP frames depends on the authentication method being used. Figure 9-3
shows a message exchange initiated by the client when the client uses the One-Time-Password (OTP)
authentication method with a RADIUS server.
Figure 9-3
Message Exchange
Authentication
server
(RADIUS)
Client
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
Port Unauthorized
201761
EAPOL-Logoff
If IEEE 802.1x authentication times out while waiting for an EAPOL message exchange and MAC
authentication bypass is enabled, the switch can authorize the client when the switch detects an Ethernet
packet from the client. The switch uses the MAC address of the client as its identity and includes this
information in the RADIUS-access/request frame that is sent to the RADIUS server. After the server
sends the switch the RADIUS-access/accept frame (authorization is successful), the port becomes
authorized. If authorization fails and a guest VLAN is specified, the switch assigns the port to the guest
VLAN. If the switch detects an EAPOL packet while waiting for an Ethernet packet, the switch stops
the MAC authentication bypass process and stops IEEE 802.1x authentication.
Figure 9-4 shows the message exchange during MAC authentication bypass.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
9-6
OL-12189-01
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
Figure 9-4
Message Exchange During MAC Authentication Bypass
Client
Authentication
server
(RADIUS)
Switch
EAPOL Request/Identity
EAPOL Request/Identity
EAPOL Request/Identity
RADIUS Access/Request
RADIUS Access/Accept
201762
Ethernet packet
Ports in Authorized and Unauthorized States
During IEEE 802.1x authentication, depending on the switch port state, the switch can grant a client
access to the network. The port starts in the unauthorized state. While in this state, the port that is not
configured as a voice VLAN port disallows all ingress and egress traffic except for IEEE 802.1x
authentication, CDP, and STP packets. When a client is successfully authenticated, the port changes to
the authorized state, allowing all traffic for the client to flow normally. If the port is configured as a voice
VLAN port, the port allows VoIP traffic and IEEE 802.1x protocol packets before the client is
successfully authenticated.
If a client that does not support IEEE 802.1x authentication connects to an unauthorized IEEE 802.1x
port, the switch requests the clients identity. In this situation, the client does not respond to the request,
the port remains in the unauthorized state, and the client is not granted access to the network.
In contrast, when an IEEE 802.1x-enabled client connects to a port that is not running the IEEE 802.1x
standard, the client initiates the authentication process by sending the EAPOL-start frame. When no
response is received, the client sends the request for a fixed number of times. Because no response is
received, the client begins sending frames as if the port is in the authorized state.
You control the port authorization state by using the dot1x port-control interface configuration
command and these keywords:
force-authorizeddisables IEEE 802.1x authentication and causes the port to change to the
authorized state without any authentication exchange required. The port sends and receives normal
traffic without IEEE 802.1x-based authentication of the client. This is the default setting.
force-unauthorizedcauses the port to remain in the unauthorized state, ignoring all attempts by
the client to authenticate. The switch cannot provide authentication services to the client through the
port.
autoenables IEEE 802.1x authentication and causes the port to begin in the unauthorized state,
allowing only EAPOL frames to be sent and received through the port. The authentication process
begins when the link state of the port changes from down to up or when an EAPOL-start frame is
received. The switch requests the identity of the client and begins relaying authentication messages
between the client and the authentication server. Each client attempting to access the network is
uniquely identified by the switch by using the client MAC address.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
9-7
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
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 change to the
unauthorized state.
If the link state of a port changes from up to down, or if an EAPOL-logoff frame is received, the port
returns to the unauthorized state.
IEEE 802.1x Authentication and Switch Stacks
If a switch is added to or removed from a switch stack, IEEE 802.1x authentication is not affected as
long as the IP connectivity between the RADIUS server and the stack remains intact. This statement also
applies if the stack master is removed from the switch stack. Note that if the stack master fails, a stack
member becomes the new stack master by using the election process described in Chapter 5, Managing
Switch Stacks, and the IEEE 802.1x authentication process continues as usual.
If IP connectivity to the RADIUS server is interrupted because the switch that was connected to the
server is removed or fails, these events occur:
Ports that are already authenticated and that do not have periodic re-authentication enabled remain
in the authenticated state. Communication with the RADIUS server is not required.
Ports that are already authenticated and that have periodic re-authentication enabled (with the dot1x
re-authentication global configuration command) fail the authentication process when the
re-authentication occurs. Ports return to the unauthenticated state during the re-authentication
process. Communication with the RADIUS server is required.
For an ongoing authentication, the authentication fails immediately because there is no server
connectivity.
If the switch that failed comes up and rejoins the switch stack, the authentications might or might not
fail depending on the boot-up time and whether the connectivity to the RADIUS server is re-established
by the time the authentication is attempted.
To avoid loss of connectivity to the RADIUS server, you should ensure that there is a redundant
connection to it. For example, you can have a redundant connection to the stack master and another to a
stack member, and if the stack master fails, the switch stack still has connectivity to the RADIUS server.
IEEE 802.1x Host Mode
Note
The switch is usually not configured in the network configuration shown in Figure 9-5.
You can configure an IEEE 802.1x port for single-host or for multiple-hosts mode. In single-host mode
(see Figure 9-1 on page 9-2), only one client can be connected to the IEEE 802.1x-enabled switch port.
The switch detects the client by sending an EAPOL frame when the port link state changes to the up
state. If a client leaves or is replaced with another client, the switch changes the port link state to down,
and the port returns to the unauthorized state.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
9-8
OL-12189-01
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
In multiple-hosts mode, you can attach multiple hosts to a single IEEE 802.1x-enabled port. Figure 9-5
on page 9-9 shows IEEE 802.1x port-based authentication in a wireless LAN. In this mode, only one of
the attached clients must be authorized for all clients to be granted network access. If the port becomes
unauthorized (re-authentication fails or an EAPOL-logoff message is received), the switch denies
network access to all of the attached clients. In this topology, the wireless access point is responsible for
authenticating the clients attached to it, and it also acts as a client to the switch.
With the multiple-hosts mode enabled, you can use IEEE 802.1x authentication to authenticate the port
and port security to manage network access for all MAC addresses, including that of the client.
Figure 9-5
Multiple Host Mode Example
Access point
Authentication
server
(RADIUS)
101227
Wireless clients
IEEE 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.
IEEE 802.1x Accounting Attribute-Value Pairs
The information sent to the RADIUS server is represented in the form of Attribute-Value (AV) pairs.
These AV pairs provide data for different applications. (For example, a billing application might require
information that is in the Acct-Input-Octets or the Acct-Output-Octets attributes of a RADIUS packet.)
AV pairs are automatically sent by a switch that is configured for IEEE 802.1x accounting. Three types
of RADIUS accounting packets are sent by a switch:
STARTsent when a new user session starts
INTERIMsent during an existing session for updates
STOPsent when a session terminates
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
9-9
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
Table 9-1 lists the AV pairs and when they are sent are sent by the switch:
Table 9-1
Accounting AV Pairs
Attribute Number
AV Pair Name
START
INTERIM
STOP
Attribute[1]
User-Name
Always
Always
Always
Attribute[4]
NAS-IP-Address
Always
Always
Always
Attribute[5]
NAS-Port
Always
Always
Always
1
Sometimes1
Attribute[8]
Framed-IP-Address
Never
Sometimes
Attribute[25]
Class
Always
Always
Always
Attribute[30]
Called-Station-ID
Always
Always
Always
Attribute[31]
Calling-Station-ID
Always
Always
Always
Attribute[40]
Acct-Status-Type
Always
Always
Always
Attribute[41]
Acct-Delay-Time
Always
Always
Always
Attribute[42]
Acct-Input-Octets
Never
Never
Always
Attribute[43]
Acct-Output-Octets
Never
Never
Always
Attribute[44]
Acct-Session-ID
Always
Always
Always
Attribute[45]
Acct-Authentic
Always
Always
Always
Attribute[46]
Acct-Session-Time
Never
Never
Always
Attribute[49]
Acct-Terminate-Cause
Never
Never
Always
Attribute[61]
NAS-Port-Type
Always
Always
Always
1. The Framed-IP-Address AV pair is sent only if a valid Dynamic Host Control Protocol (DHCP) binding
exists for the host in the DHCP snooping bindings table.
You can view the AV pairs that are being sent by the switch by entering the debug radius accounting
privileged EXEC command. For more information about this command, see the Cisco IOS Debug
Command Reference, Release 12.2 at this URL:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_command_reference_book09186a
00800872ce.html
For more information about AV pairs, see RFC 3580, IEEE 802.1X Remote Authentication Dial In User
Service (RADIUS) Usage Guidelines.
Using IEEE 802.1x Authentication with VLAN Assignment
The switch supports IEEE 802.1x authentication with VLAN assignment. After successful IEEE 802.1x
authentication of a port, the RADIUS server sends the VLAN assignment to configure the switch port.
The RADIUS server database maintains the username-to-VLAN mappings, assigning the VLAN based
on the username of the client connected to the switch port. You can use this feature to limit network
access for certain users.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
9-10
OL-12189-01
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
Voice device authentication is supported. When a voice device is authorized and the RADIUS server
returned an authorized VLAN, the voice VLAN on the port is configured to send and receive packets on
the assigned voice VLAN. Voice VLAN assignment behaves the same as data VLAN assignment on
multidomain authentication (MDA)-enabled ports. For more information, see the Using Multidomain
Authentication section on page 9-20.
When configured on the switch and the RADIUS server, IEEE 802.1x authentication with VLAN
assignment has these characteristics:
If no VLAN is supplied by the RADIUS server or if IEEE 802.1x authentication is disabled, the port
is configured in its access VLAN after successful authentication. Recall that an access VLAN is a
VLAN assigned to an access port. All packets sent from or received on this port belong to this
VLAN.
If IEEE 802.1x authentication is enabled but the VLAN information from the RADIUS server is not
valid, authorization fails and configured VLAN remains in use. This prevents ports from appearing
unexpectedly in an inappropriate VLAN because of a configuration error.
Configuration errors could include specifying a VLAN for a routed port, a malformed VLAN ID, a
nonexistent or internal (routed port) VLAN ID, an RSPAN VLAN, a shut down or suspended VLAN.
In the case of a mutlidomain host port, configuration errors can also be due to an attempted
assignment of a data VLAN that matches the configured or assigned voice VLAN ID (or the
reverse).
If IEEE 802.1x authentication is enabled and all information from the RADIUS server is valid, the
authorized device is placed in the specified VLAN after authentication.
If the multiple-hosts mode is enabled on an IEEE 802.1x port, all hosts are placed in the same VLAN
(specified by the RADIUS server) as the first authenticated host.
Enabling port security does not impact the RADIUS server-assigned VLAN behavior.
If IEEE 802.1x authentication is disabled on the port, it is returned to the configured access VLAN
and configured voice VLAN.
When the port is in the force authorized, force unauthorized, unauthorized, or shutdown state, it is put
into the configured access VLAN.
If an IEEE 802.1x port is authenticated and put in the RADIUS server-assigned VLAN, any change to
the port access VLAN configuration does not take effect. In the case of a multidomain host, the same
applies to voice devices when the port is fully authorized with these exceptions:
If the VLAN configuration change of one device results in matching the other device configured or
assigned VLAN, authorization of all devices on the port is terminated and multidomain host mode
is disabled until a valid configuration is restored where data and voice device configured VLANs no
longer match.
If a voice device is authorized and is using a downloaded voice VLAN, the removal of the voice
VLAN configuration, or modifying the configuration value to dot1p or untagged results in voice
device un-authorization and the disablement of multi-domain host mode.
The IEEE 802.1x authentication with VLAN assignment feature is not supported on trunk ports, dynamic
ports, or with dynamic-access port assignment through a VLAN Membership Policy Server (VMPS).
To configure VLAN assignment you need to perform these tasks:
Enable AAA authorization by using the network keyword to allow interface configuration from the
RADIUS server.
Enable IEEE 802.1x authentication. (The VLAN assignment feature is automatically enabled when
you configure IEEE 802.1x authentication on an access port).
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
9-11
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
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.
Using IEEE 802.1x Authentication with Per-User ACLs
You can enable per-user access control lists (ACLs) to provide different levels of network access and
service to an IEEE 802.1x-authenticated user. When the RADIUS server authenticates a user connected
to an IEEE 802.1x port, it retrieves the ACL attributes based on the user identity and sends them to the
switch. The switch applies the attributes to the IEEE 802.1x port for the duration of the user session. The
switch removes the per-user ACL configuration when the session is over, if authentication fails, or if a
link-down condition occurs. The switch does not save RADIUS-specified ACLs in the running
configuration. When the port is unauthorized, the switch removes the ACL from the port.
You can configure router ACLs and input port ACLs on the same switch. However, a port ACL takes
precedence over a router ACL. If you apply input port ACL to an interface that belongs to a VLAN, the
port ACL takes precedence over an input router ACL applied to the VLAN interface. Incoming packets
received on the port to which a port ACL is applied are filtered by the port ACL. Incoming routed packets
received on other ports are filtered by the router ACL. Outgoing routed packets are filtered by the router
ACL. To avoid configuration conflicts, you should carefully plan the user profiles stored on the RADIUS
server.
RADIUS supports per-user attributes, including vendor-specific attributes. These vendor-specific
attributes (VSAs) are in octet-string format and are passed to the switch during the authentication
process. The VSAs used for per-user ACLs are inacl#<n> for the ingress direction and outacl#<n> for
the egress direction. MAC ACLs are supported only in the ingress direction. The switch supports VSAs
only in the ingress direction. It does not support port ACLs in the egress direction on Layer 2 ports. For
more information, see Chapter 34, Configuring Network Security with ACLs.
Use only the extended ACL syntax style to define the per-user configuration stored on the RADIUS
server. When the definitions are passed from the RADIUS server, they are created by using the extended
naming convention. However, if you use the Filter-Id attribute, it can point to a standard ACL.
You can use the Filter-Id attribute to specify an inbound or outbound ACL that is already configured on
the switch. The attribute contains the ACL number followed by .in for ingress filtering or .out for egress
filtering. If the RADIUS server does not allow the .in or .out syntax, the access list is applied to the
outbound ACL by default. Because of limited support of Cisco IOS access lists on the switch, the
Filter-Id attribute is supported only for IP ACLs numbered 1 to 199 and 1300 to 2699 (IP standard and
IP extended ACLs).
Per-user ACLs are supported only in single-host mode.
The maximum size of the per-user ACL is 4000 ASCII characters but is limited by the maximum size of
RADIUS-server per-user ACLs.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
9-12
OL-12189-01
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
For examples of vendor-specific attributes, see the Configuring the Switch to Use Vendor-Specific
RADIUS Attributes section on page 7-29. For more information about configuring ACLs, see
Chapter 34, Configuring Network Security with ACLs.
To configure per-user ACLs, you need to perform these tasks:
Enable AAA authentication.
Enable AAA authorization by using the network keyword to allow interface configuration from the
RADIUS server.
Enable IEEE 802.1x authentication.
Configure the user profile and VSAs on the RADIUS server.
Configure the IEEE 802.1x port for single-host mode.
Using IEEE 802.1x Authentication with Guest VLAN
You can configure a guest VLAN for each IEEE 802.1x port on the switch to provide limited services to
clients, such as downloading the IEEE 802.1x client. These clients might be upgrading their system for
IEEE 802.1x authentication, and some hosts, such as Windows 98 systems, might not be
IEEE 802.1x-capable.
When you enable a guest VLAN on an IEEE 802.1x port, the switch assigns clients to a guest VLAN
when the switch does not receive a response to its EAP request/identity frame or when EAPOL packets
are not sent by the client.
The switch maintains the EAPOL packet history. If an EAPOL packet is detected on the interface during
the lifetime of the link, the switch determines that the device connected to that interface is an
IEEE 802.1x-capable supplicant, and the interface does not change to the guest VLAN state. EAPOL
history is cleared if the interface link status goes down. If no EAPOL packet is detected on the interface,
the interface changes to the guest VLAN state.
If the switch is trying to authorize an IEEE 802.1x-capable voice device and the AAA server is
unavailable, the authorization attempt fails, but the detection of the EAPOL packet is saved in the
EAPOL history. When the AAA server becomes available, the switch authorizes the voice device.
However, the switch no longer allows other devices access to the guest VLAN. To prevent this situation,
use one of these command sequences:
Enter the dot1x guest-vlan supplicant global configuration command to allow access to the guest
VLAN.
Enter the shutdown interface configuration command followed by the no shutdown interface
configuration command to restart the port.
Use a restricted VLAN to allow clients that failed authentication access to the network by entering the
dot1x auth-fail vlan vlan-id interface configuration command.
If devices send EAPOL packets to the switch during the lifetime of the link, the switch no longer allows
clients that fail authentication access to the guest VLAN.
Note
If an EAPOL packet is detected after the interface has changed to the guest VLAN, the interface reverts
to an unauthorized state, and IEEE 802.1x authentication restarts.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
9-13
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
Any number of IEEE 802.1x-incapable clients are allowed access when the switch port is moved to the
guest VLAN. If an IEEE 802.1x-capable client joins the same port on which the guest VLAN is
configured, the port is put into the unauthorized state in the user-configured access VLAN, and
authentication is restarted.
Guest VLANs are supported on IEEE 802.1x ports in single-host or multiple-hosts mode.
You can configure any active VLAN except an RSPAN VLAN, a private 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.
The switch supports MAC authentication bypass. When MAC authentication bypass is enabled on an
IEEE 802.1x port, the switch can authorize clients based on the client MAC address when IEEE 802.1x
authentication times out while waiting for an EAPOL message exchange. After detecting a client on an
IEEE 802.1x port, the switch waits for an Ethernet packet from the client. The switch sends the
authentication server a RADIUS-access/request frame with a username and password based on the MAC
address. If authorization succeeds, the switch grants the client access to the network. If authorization
fails, the switch assigns the port to the guest VLAN if one is specified. For more information, see
theUsing IEEE 802.1x Authentication with MAC Authentication Bypass section on page 9-18.
For more information, see the Configuring a Guest VLAN section on page 9-34.
Using IEEE 802.1x Authentication with Restricted VLAN
You can configure a restricted VLAN (also referred to as an authentication failed VLAN) for each
IEEE 802.1x port on a switch stack or a switch to provide limited services to clients that cannot access
the guest VLAN. These clients are IEEE 802.1x-compliant and cannot access another VLAN because
they fail the authentication process. A restricted VLAN allows users without valid credentials in an
authentication server (typically, visitors to an enterprise) to access a limited set of services. The
administrator can control the services available to the restricted VLAN.
Note
You can configure a VLAN to be both the guest VLAN and the restricted VLAN if you want to provide
the same services to both types of users.
Without this feature, the client attempts and fails authentication indefinitely, and the 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 number of 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 restart the authentication process 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
9-14
OL-12189-01
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
After a port moves to the restricted VLAN, a simulated EAP success message is sent to the client. 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.
This feature works with port security. As soon as the port is authorized, a MAC address is provided to
port security. If port security does not permit the MAC address or if the maximum secure address count
is reached, the port becomes unauthorized and error disabled.
Other port security features such as dynamic ARP Inspection, DHCP snooping, and IP source guard can
be configured independently on a restricted VLAN.
For more information, see the Configuring a Restricted VLAN section on page 9-35.
Using IEEE 802.1x Authentication with Inaccessible Authentication Bypass
When the switch cannot reach the configured RADIUS servers and hosts cannot be authenticated, you
can configure the switch to allow network access to the hosts connected to critical ports. A critical port
is enabled for the inaccessible authentication bypass feature, also referred to as critical authentication
or the AAA fail policy.
When this feature is enabled, the switch checks the status of the configured RADIUS servers whenever
the switch tries to authenticate a host connected to a critical port. If a server is available, the switch can
authenticate the host. However, if all the RADIUS servers are unavailable, the switch grants network
access to the host and puts the port in the critical-authentication state, which is a special case of the
authentication state.
The behavior of the inaccessible authentication bypass feature depends on the authorization state of the
port:
If the port is unauthorized when a host connected to a critical port tries to authenticate and all servers
are unavailable, the switch puts the port in the critical-authentication state in the
RADIUS-configured or user-specified access VLAN.
If the port is already authorized and re-authentication occurs, the switch puts the critical port in the
critical-authentication state in the current VLAN, which might be the one previously assigned by
the RADIUS server.
If the RADIUS server becomes unavailable during an authentication exchange, the current
exchanges times out, and the switch puts the critical port in the critical-authentication state during
the next authentication attempt.
When a RADIUS server that can authenticate the host is available, all critical ports in the
critical-authentication state are automatically re-authenticated.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
9-15
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
Inaccessible authentication bypass interacts with these features:
Guest VLANInaccessible authentication bypass is compatible with guest VLAN. When a guest
VLAN is enabled on IEEE 8021.x port, the features interact as follows:
If at least one RADIUS server is available, the switch assigns a client to a guest VLAN when
the switch does not receive a response to its EAP request/identity frame or when EAPOL
packets are not sent by the client.
If all the RADIUS servers are not available and the client is connected to a critical port, the
switch authenticates the client and puts the critical port in the critical-authentication state in the
RADIUS-configured or user-specified access VLAN.
If all the RADIUS servers are not available and the client is not connected to a critical port, the
switch might not assign clients to the guest VLAN if one is configured.
If all the RADIUS servers are not available and if a client is connected to a critical port and was
previously assigned to a guest VLAN, the switch keeps the port in the guest VLAN.
Restricted VLANIf the port is already authorized in a restricted VLAN and the RADIUS servers
are unavailable, the switch puts the critical port in the critical-authentication state in the restricted
VLAN.
IEEE 802.1x accountingAccounting is not affected if the RADIUS servers are unavailable.
Private VLANYou can configure inaccessible authentication bypass on a private VLAN host port.
The access VLAN must be a secondary private VLAN.
Voice VLANInaccessible authentication bypass is compatible with voice VLAN, but the
RADIUS-configured or user-specified access VLAN and the voice VLAN must be different.
Remote Switched Port Analyzer (RSPAN)Do not configure an RSPAN VLAN as the
RADIUS-configured or user-specified access VLAN for inaccessible authentication bypass.
In a switch stack, the stack master checks the status of the RADIUS servers by sending keepalive
packets. When the status of a RADIUS server changes, the stack master sends the information to the
stack members. The stack members can then check the status of RADIUS servers when re-authenticating
critical ports.
If the new stack master is elected, the link between the switch stack and RADIUS server might change,
and the new stack immediately sends keepalive packets to update the status of the RADIUS servers. If
the server status changes from dead to alive, the switch re-authenticates all switch ports in the
critical-authentication state.
When a member is added to the stack, the stack master sends the member the server status.
Using IEEE 802.1x Authentication with Voice VLAN Ports
A voice VLAN port is a special access port associated with two VLAN identifiers:
VVID to carry voice traffic to and from the IP phone. The VVID is used to configure the IP phone
connected to the port.
PVID to carry the data traffic to and from the workstation connected to the switch through the IP
phone. The PVID is the native VLAN of the port.
The IP phone uses the VVID for its voice traffic, regardless of the authorization state of the port. This
allows the phone to work independently of IEEE 802.1x authentication.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
9-16
OL-12189-01
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
In single-host mode, only the IP phone is allowed on the voice VLAN. In multiple-hosts mode,
additional clients can send traffic on the voice VLAN after a supplicant is authenticated on the PVID.
When multiple-hosts mode is enabled, the supplicant authentication affects both the PVID and the
VVID.
A voice VLAN port becomes active when there is a link, and the device MAC address appears after the
first CDP message from the IP phone. Cisco IP phones do not relay CDP messages from other devices.
As a result, if several IP phones are connected in series, the switch recognizes only the one directly
connected to it. When IEEE 802.1x authentication is enabled on a voice VLAN port, the switch drops
packets from unrecognized IP phones more than one hop away.
When IEEE 802.1x authentication is enabled on a port, you cannot configure a port VLAN that is equal
to a voice VLAN.
Note
If you enable IEEE 802.1x authentication on an access port on which a voice VLAN is configured and
to which a Cisco IP Phone is connected, the Cisco IP phone loses connectivity to the switch for up to 30
seconds.
For more information about voice VLANs, see Chapter 14, Configuring Voice VLAN.
Using IEEE 802.1x Authentication with Port Security
You can configure an IEEE 802.1x port with port security in either single-host or multiple-hosts mode.
(You also must configure port security on the port by using the switchport port-security interface
configuration command.) When you enable port security and IEEE 802.1x authentication on a port, IEEE
802.1x authentication authenticates the port, and port security manages network access for all MAC
addresses, including that of the client. You can then limit the number or group of clients that can access
the network through an IEEE 802.1x port.
These are some examples of the interaction between IEEE 802.1x authentication and port security on the
switch:
When a client is authenticated, and the port security table is not full, the client MAC address is added
to the port security list of secure hosts. The port then proceeds to come up normally.
When a client is authenticated and manually configured for port security, it is guaranteed an entry
in the secure host table (unless port security static aging has been enabled).
A security violation occurs if the client is authenticated, but the port security table is full. This can
happen if the maximum number of secure hosts has been statically configured or if the client ages
out of the secure host table. If the client address is aged, its place in the secure host table can be
taken by another host.
If the security violation is caused by the first authenticated host, the port becomes error-disabled and
immediately shuts down.
The port security violation modes determine the action for security violations. For more
information, see the Security Violations section on page 25-9.
When you manually remove an IEEE 802.1x client address from the port security table by using the
no switchport port-security mac-address mac-address interface configuration command, you
should re-authenticate the IEEE 802.1x client by using the dot1x re-authenticate interface
interface-id privileged EXEC command.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
9-17
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
When an IEEE 802.1x client logs off, the port changes to an unauthenticated state, and all dynamic
entries in the secure host table are cleared, including the entry for the client. Normal authentication
then takes place.
If the port is administratively shut down, the port becomes unauthenticated, and all dynamic entries
are removed from the secure host table.
Port security and a voice VLAN can be configured simultaneously on an IEEE 802.1x port that is in
either single-host or multiple-hosts mode. Port security applies to both the voice VLAN identifier
(VVID) and the port VLAN identifier (PVID).
For more information about enabling port security on your switch, see the Configuring Port Security
section on page 25-7.
Using IEEE 802.1x Authentication with Wake-on-LAN
The IEEE 802.1x authentication with wake-on-LAN (WoL) feature allows dormant PCs to be powered
when the switch receives a specific Ethernet frame, known as the magic packet. You can use this feature
in environments where administrators need to connect to systems that have been powered down.
When a host that uses WoL is attached through an IEEE 802.1x port and the host powers off, the
IEEE 802.1x port becomes unauthorized. The port can only receive and send EAPOL packets, and WoL
magic packets cannot reach the host. When the PC is powered off, it is not authorized, and the switch
port is not opened.
When the switch uses IEEE 802.1x authentication with WoL, the switch forwards traffic to unauthorized
IEEE 802.1x ports, including magic packets. While the port is unauthorized, the switch continues to
block ingress traffic other than EAPOL packets. The host can receive packets but cannot send packets to
other devices in the network.
Note
If PortFast is not enabled on the port, the port is forced to the bidirectional state.
When you configure a port as unidirectional by using the dot1x control-direction in interface
configuration command, the port changes to the spanning-tree forwarding state. The port can send
packets to the host but cannot receive packets from the host.
When you configure a port as bidirectional by using the dot1x control-direction both interface
configuration command, the port is access-controlled in both directions. The port does not receive
packets from or send packets to the host.
Using IEEE 802.1x Authentication with MAC Authentication Bypass
You can configure the switch to authorize clients based on the client MAC address (see Figure 9-2 on
page 9-4) by using the MAC authentication bypass feature. For example, you can enable this feature on
IEEE 802.1x ports connected to devices such as printers.
If IEEE 802.1x authentication times out while waiting for an EAPOL response from the client, the switch
tries to authorize the client by using MAC authentication bypass.
When the MAC authentication bypass feature is enabled on an IEEE 802.1x port, the switch uses the
MAC address as the client identity. The authentication server has a database of client MAC addresses
that are allowed network access. After detecting a client on an IEEE 802.1x port, the switch waits for an
Ethernet packet from the client. The switch sends the authentication server a RADIUS-access/request
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
9-18
OL-12189-01
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
frame with a username and password based on the MAC address. If authorization succeeds, the switch
grants the client access to the network. If authorization fails, the switch assigns the port to the guest
VLAN if one is configured.
If an EAPOL packet is detected on the interface during the lifetime of the link, the switch determines
that the device connected to that interface is an IEEE 802.1x-capable supplicant and uses IEEE 802.1x
authentication (not MAC authentication bypass) to authorize the interface. EAPOL history is cleared if
the interface link status goes down.
If the switch already authorized a port by using MAC authentication bypass and detects an IEEE 802.1x
supplicant, the switch does not unauthorize the client connected to the port. When re-authentication
occurs, the switch uses IEEE 802.1x authentication as the preferred re-authentication process if the
previous session ended because the Termination-Action RADIUS attribute value is DEFAULT.
Clients that were authorized with MAC authentication bypass can be re-authenticated. The
re-authentication process is the same as that for clients that were authenticated with IEEE 802.1x.
During re-authentication, the port remains in the previously assigned VLAN. If re-authentication is
successful, the switch keeps the port in the same VLAN. If re-authentication fails, the switch assigns the
port to the guest VLAN, if one is configured.
If re-authentication is based on the Session-Timeout RADIUS attribute (Attribute[27]) and the
Termination-Action RADIUS attribute (Attribute [29]) and if the Termination-Action RADIUS attribute
(Attribute [29]) action is Initialize, (the attribute value is DEFAULT), the MAC authentication bypass
session ends, and connectivity is lost during re-authentication. If MAC authentication bypass is enabled
and the IEEE 802.1x authentication times out, the switch uses the MAC authentication bypass feature to
initiate re-authorization. For more information about these AV pairs, see RFC 3580, IEEE 802.1X
Remote Authentication Dial In User Service (RADIUS) Usage Guidelines.
MAC authentication bypass interacts with the features:
IEEE 802.1x authenticationYou can enable MAC authentication bypass only if IEEE 802.1x
authentication is enabled on the port.
Guest VLANIf a client has an invalid MAC address identity, the switch assigns the client to a
guest VLAN if one is configured.
Restricted VLANThis feature is not supported when the client connected to an IEEE 802.lx port
is authenticated with MAC authentication bypass.
Port securitySee the Using IEEE 802.1x Authentication with Port Security section on
page 9-17.
Voice VLANSee the Using IEEE 802.1x Authentication with Voice VLAN Ports section on
page 9-16.
VLAN Membership Policy Server (VMPS)IEEE802.1x and VMPS are mutually exclusive.
Private VLANYou can assign a client to a private VLAN.
Network admission control (NAC) Layer 2 IP validationThis feature takes effect after an
IEEE 802.1x port is authenticated with MAC authentication bypass, including hosts in the exception
list.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
9-19
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
Network Admission Control Layer 2 IEEE 802.1x Validation
The switch supports the Network Admission Control (NAC) Layer 2 IEEE 802.1x validation, which
checks the antivirus condition or posture of endpoint systems or clients before granting the devices
network access. With NAC Layer 2 IEEE 802.1x validation, you can do these tasks:
Download the Session-Timeout RADIUS attribute (Attribute[27]) and the Termination-Action
RADIUS attribute (Attribute[29]) from the authentication server.
Set the number of seconds between re-authentication attempts as the value of the Session-Timeout
RADIUS attribute (Attribute[27]) and get an access policy against the client from the RADIUS
server.
Set the action to be taken when the switch tries to re-authenticate the client by using the
Termination-Action RADIUS attribute (Attribute[29]). If the value is the DEFAULT or is not set, the
session ends. If the value is RADIUS-Request, the re-authentication process starts.
View the NAC posture token, which shows the posture of the client, by using the show dot1x
privileged EXEC command.
Configure secondary private VLANs as guest VLANs.
Configuring NAC Layer 2 IEEE 802.1x validation is similar to configuring IEEE 802.1x port-based
authentication except that you must configure a posture token on the RADIUS server. For information
about configuring NAC Layer 2 IEEE 802.1x validation, see the Configuring NAC Layer 2 IEEE 802.1x
Validation section on page 9-41 and the Configuring Periodic Re-Authentication section on
page 9-30.
For more information about NAC, see the Network Admission Control Software Configuration Guide.
Using Multidomain Authentication
The switch supports multidomain authentication (MDA), which allows both a data device and voice
device, such as an IP phone (Cisco or non-Cisco), to authenticate on the same switch port. The port is
divided into a data domain and a voice domain.
MDA does not enforce the order of device authentication. However, for best results, we recommend that
a voice device is authenticated before a data device on an MDA-enabled port.
Follow these guidelines for configuring MDA:
To configure a switch port for MDA, see the Configuring the Host Mode section on page 9-29.
You must configure the voice VLAN for the IP phone when the host mode is set to multidomain. For
more information, see Chapter 14, Configuring Voice VLAN.
Voice VLAN assignment on an MDA-enabled port is supported.
Note
If you use a dynamic VLAN to assign a voice VLAN on an MDA-enabled switch port, the voice
device fails authorization.
To authorize a voice device, the AAA server must be configured to send a Cisco Attribute-Value
(AV) pair attribute with a value of device-traffic-class=voice. Without this value, the switch
treats the voice device as a data device.
The guest VLAN and restricted VLAN features only apply to the data devices on an MDA-enabled
port. The switch treats a voice device that fails authorization as a data device.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
9-20
OL-12189-01
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
If more than one device attempts authorization on either the voice or the data domain of a port, it is
error disabled.
Until a device is authorized, the port drops its traffic. Non-Cisco IP phones or voice devices are
allowed into both the data and voice VLANs. The data VLAN allows the voice device to contact a
DHCP server to obtain an IP address and acquire the voice VLAN information. After the voice
device starts sending on the voice VLAN, its access to the data VLAN is blocked.
A voice device MAC address that is binding on the data VLAN is not counted towards the port
security MAC address limit.
You can use dynamic VLAN assignment from a RADIUS server only for data devices.
MDA can use MAC authentication bypass as a fallback mechanism to allow the switch port to
connect to devices that do not support IEEE 802.1x authentication. For more information, see the
MAC Authentication Bypass section on page 9-26.
When a data or a voice device is detected on a port, its MAC address is blocked until authorization
succeeds. If the authorization fails, the MAC address remains blocked for 5 minutes.
If more than five devices are detected on the data VLAN or more than one voice device is detected
on the voice VLAN while a port is unauthorized, the port is error disabled.
When a port host mode is changed from single- or multihost to multidomain mode, an authorized
data device remains authorized on the port. However, a Cisco IP phone that has been allowed on the
port voice VLAN is automatically removed and must be reauthenticated on that port.
Active fallback mechanisms such as guest VLAN and restricted VLAN remain configured after a
port changes from single- or multihost mode to multidomain mode.
Switching a port host mode from multidomain to single- or multihost mode removes all authorized
devices from the port.
If a data domain is authorized first and placed in the guest VLAN, non-IEEE 802.1x-capable voice
devices need to tag their packets on the voice VLAN to trigger authentication.
We do not recommend per-user ACLs with an MDA-enabled port. An authorized device with a
per-user ACL policy might impact traffic on both the voice and data VLANs of the port. If used,
only one device on the port should enforce per-user ACLs.
Using Web Authentication
You can use a web browser to authenticate a client that does not support IEEE 802.1x functionality. This
feature can authenticate up to eight users on the same shared port and apply the appropriate policies for
each end host on a shared port.
You can configure a port to use only web authentication. You can also configure the port to first try and
use IEEE 802.1x authentication and then to use web authorization if the client does not support
IEEE 802.1x authentication.
Web authentication requires two Cisco Attribute-Value (AV) pair attributes:
The first attribute, priv-lvl=15, must always be set to 15. This sets the privilege level of the user
who is logging into the switch.
The second attribute is an access list to be applied for web authenticated hosts. The syntax is similar
to IEEE 802.1X per-user ACLs. However, instead of ip:inacl, this attribute must begin with
proxyacl, and the source field in each entry must be any. (After authentication, the client IP
address replaces the any field when the ACL is applied.)
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
9-21
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Configuring IEEE 802.1x Authentication
For example:
proxyacl#
proxyacl#
proxyacl#
proxyacl#
Note
10=permit
20=permit
30=permit
40=permit
ip any 10.0.0.0 255.0.0.0
ip any 11.1.0.0 255.255.0.0
udp any any eq syslog
udp any any eq tftp
The proxyacl entry determines the type of allowed network access.
For more information, see the Configuring Web Authentication section on page 9-42.
Web Authentication with Automatic MAC Check
You can use web authentication with automatic MAC check to authenticate a client that does not support
IEEE 802.1x or web browser functionality. This allows end hosts, such as printers, to automatically
authenticate by using the MAC address without any additional required configuration.
Web authentication with automatic MAC check only works in web authentication standalone mode. You
cannot use this if web authentication is configured as a fallback to IEEE 802.1x authentication.
The MAC address of the device must be configured in the Access Control Server (ACS) for the automatic
MAC check to succeed. The automatic MAC check allows managed devices, such as printers, to skip
web authentication.
Note
The interoperability of web authentication (with automatic MAC check) and IEEE 802.1x MAC
authentication configured on different ports of the same switch is not supported.
Configuring IEEE 802.1x Authentication
These sections contain this configuration information:
Default IEEE 802.1x Authentication Configuration, page 9-23
IEEE 802.1x Authentication Configuration Guidelines, page 9-24
Configuring IEEE 802.1x Authentication, page 9-26 (required)
Configuring the Switch-to-RADIUS-Server Communication, page 9-28 (required)
Configuring the Host Mode, page 9-29 (optional)
Configuring Periodic Re-Authentication, page 9-30 (optional)
Manually Re-Authenticating a Client Connected to a Port, page 9-30 (optional)
Changing the Quiet Period, page 9-31 (optional)
Changing the Switch-to-Client Retransmission Time, page 9-31 (optional)
Setting the Switch-to-Client Frame-Retransmission Number, page 9-32 (optional)
Setting the Re-Authentication Number, page 9-32 (optional)
Configuring IEEE 802.1x Accounting, page 9-33 (optional)
Configuring a Guest VLAN, page 9-34 (optional)
Configuring a Restricted VLAN, page 9-35 (optional)
Configuring the Inaccessible Authentication Bypass Feature, page 9-37 (optional)
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
9-22
OL-12189-01
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Configuring IEEE 802.1x Authentication
Configuring IEEE 802.1x Authentication with WoL, page 9-39 (optional)
Configuring MAC Authentication Bypass, page 9-40 (optional)
Configuring NAC Layer 2 IEEE 802.1x Validation, page 9-41 (optional)
Configuring Web Authentication, page 9-42
Disabling IEEE 802.1x Authentication on the Port, page 9-44 (optional)
Resetting the IEEE 802.1x Authentication Configuration to the Default Values, page 9-45 (optional)
Default IEEE 802.1x Authentication Configuration
Table 9-2 shows the default IEEE 802.1x authentication configuration.
Table 9-2
Default IEEE 802.1x Authentication Configuration
Feature
Default Setting
Switch IEEE 802.1x enable state
Disabled.
Per-port IEEE 802.1x enable state
Disabled (force-authorized).
The port sends and receives normal traffic without IEEE
802.1x-based authentication of the client.
AAA
Disabled.
RADIUS server
IP address
None specified.
UDP authentication port
1812.
Key
None specified.
Host mode
Single-host mode.
Control direction
Bidirectional control.
Periodic re-authentication
Disabled.
Number of seconds between
re-authentication attempts
3600 seconds.
Re-authentication number
2 times (number of times that the switch restarts the
authentication process before the port changes to the
unauthorized state).
Quiet period
60 seconds (number of seconds that the switch remains in
the quiet state following a failed authentication exchange
with the client).
Retransmission time
30 seconds (number of seconds that the switch should
wait for a response to an EAP request/identity frame
from the client before resending the request).
Maximum retransmission number
2 times (number of times that the switch will send an
EAP-request/identity frame before restarting the
authentication process).
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
9-23
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Configuring IEEE 802.1x Authentication
Table 9-2
Default IEEE 802.1x Authentication Configuration (continued)
Feature
Default Setting
Client timeout period
30 seconds (when relaying a request from the
authentication server to the client, the amount of time the
switch waits for a response before resending the request
to the client.)
Authentication server timeout period
30 seconds (when relaying a response from the client to
the authentication server, the amount of time the switch
waits for a reply before resending the response to the
server. This setting is not configurable.)
Guest VLAN
None specified.
Inaccessible authentication bypass
Disabled.
Restricted VLAN
None specified.
Authenticator (switch) mode
None specified.
MAC authentication bypass
Disabled.
IEEE 802.1x Authentication Configuration Guidelines
This section has configuration guidelines for these features:
IEEE 802.1x Authentication, page 9-24
VLAN Assignment, Guest VLAN, Restricted VLAN, and Inaccessible Authentication Bypass,
page 9-25
MAC Authentication Bypass, page 9-26
IEEE 802.1x Authentication
These are the IEEE 802.1x authentication configuration guidelines:
When IEEE 802.1x authentication is enabled, ports are authenticated before any other Layer 2 or
Layer 3 features are enabled.
If you try to change the mode of an IEEE 802.1x-enabled port (for example, from access to trunk),
an error message appears, and the port mode is not changed.
If the VLAN to which an IEEE 802.1x-enabled port is assigned changes, this change is transparent
and does not affect the switch. For example, this change occurs if a port is assigned to a RADIUS
server-assigned VLAN and is then assigned to a different VLAN after re-authentication.
If the VLAN to which an IEEE 802.1x port is assigned to shut down, disabled, or removed, the port
becomes unauthorized. For example, the port is unauthorized after the access VLAN to which a port
is assigned shuts down or is removed.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
9-24
OL-12189-01
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Configuring IEEE 802.1x Authentication
The IEEE 802.1x protocol is supported on Layer 2 static-access ports, voice VLAN ports, and
Layer 3 routed ports, but it is not supported on these port types:
Trunk portIf you try to enable IEEE 802.1x authentication on a trunk port, an error message
appears, and IEEE 802.1x authentication is not enabled. If you try to change the mode of an
IEEE 802.1x-enabled port to trunk, an error message appears, and the port mode is not changed.
Dynamic portsA port in dynamic mode can negotiate with its neighbor to become a trunk
port. If you try to enable IEEE 802.1x authentication on a dynamic port, an error message
appears, and IEEE 802.1x authentication is not enabled. If you try to change the mode of an
IEEE 802.1x-enabled port to dynamic, an error message appears, and the port mode is not
changed.
Dynamic-access portsIf you try to enable IEEE 802.1x authentication on a dynamic-access
(VLAN Query Protocol [VQP]) port, an error message appears, and IEEE 802.1x authentication
is not enabled. If you try to change an IEEE 802.1x-enabled port to dynamic VLAN assignment,
an error message appears, and the VLAN configuration is not changed.
EtherChannel portDo not configure a port that is an active or a not-yet-active member of an
EtherChannel as an IEEE 802.1x port. If you try to enable IEEE 802.1x authentication on an
EtherChannel port, an error message appears, and IEEE 802.1x authentication is not enabled.
Switched Port Analyzer (SPAN) and Remote SPAN (RSPAN) destination portsYou can
enable IEEE 802.1x authentication on a port that is a SPAN or RSPAN destination port.
However, IEEE 802.1x authentication is disabled until the port is removed as a SPAN or RSPAN
destination port. You can enable IEEE 802.1x authentication on a SPAN or RSPAN source port.
Before globally enabling IEEE 802.1x authentication on a switch by entering the dot1x
system-auth-control global configuration command, remove the EtherChannel configuration from
the interfaces on which IEEE 802.1x authentication and EtherChannel are configured.
If you are using a device running the Cisco Access Control Server (ACS) application for
IEEE 802.1x authentication with EAP-Transparent LAN Services (TLS) and EAP-MD5, make sure
that the device is running ACS Version 3.2.1 or later.
VLAN Assignment, Guest VLAN, Restricted VLAN, and Inaccessible Authentication Bypass
These are the configuration guidelines for VLAN assignment, guest VLAN, restricted VLAN, and
inaccessible authentication bypass:
When IEEE 802.1x authentication is enabled on a port, you cannot configure a port VLAN that is
equal to a voice VLAN.
The IEEE 802.1x authentication with VLAN assignment feature is not supported on trunk ports,
dynamic ports, or with dynamic-access port assignment through a VMPS.
You can configure IEEE 802.1x authentication on a private-VLAN port, but do not configure
IEEE 802.1x authentication with port security, a voice VLAN, a guest VLAN, a restricted VLAN,
or a per-user ACL on private-VLAN ports.
You can configure any VLAN except an RSPAN VLAN, private 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.
After you configure a guest VLAN for an IEEE 802.1x port to which a DHCP client is connected,
you might need to get a host IP address from a DHCP server. You can change the settings for
restarting the IEEE 802.1x authentication process on the switch before the DHCP process on the
client times out and tries to get a host IP address from the DHCP server. Decrease the settings for
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
9-25
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Configuring IEEE 802.1x Authentication
the IEEE 802.1x authentication process (dot1x timeout quiet-period and dot1x timeout tx-period
interface configuration commands). The amount to decrease the settings depends on the connected
IEEE 802.1x client type.
When configuring the inaccessible authentication bypass feature, follow these guidelines:
The feature is supported on IEEE 802.1x port in single-host mode and multihosts mode.
If the client is running Windows XP and the port to which the client is connected is in the
critical-authentication state, Windows XP might report that the interface is not authenticated.
If the Windows XP client is configured for DHCP and has an IP address from the DHCP server,
receiving an EAP-Success message on a critical port might not re-initiate the DHCP
configuration process.
You can configure the inaccessible authentication bypass feature and the restricted VLAN on
an IEEE 802.1x port. If the switch tries to re-authenticate a critical port in a restricted VLAN
and all the RADIUS servers are unavailable, switch changes the port state to the critical
authentication state and remains in the restricted VLAN.
You can configure the inaccessible bypass feature and port security on the same switch port.
You can configure any VLAN except an RSPAN 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.
MAC Authentication Bypass
These are the MAC authentication bypass configuration guidelines:
Unless otherwise stated, the MAC authentication bypass guidelines are the same as the IEEE 802.1x
authentication guidelines. For more information, see the IEEE 802.1x Authentication section on
page 9-24.
If you disable MAC authentication bypass from a port after the port has been authorized with its
MAC address, the port state is not affected.
If the port is in the unauthorized state and the client MAC address is not the authentication-server
database, the port remains in the unauthorized state. However, if the client MAC address is added to
the database, the switch can use MAC authentication bypass to re-authorize the port.
If the port is in the authorized state, the port remains in this state until re-authorization occurs.
Configuring IEEE 802.1x Authentication
To configure IEEE 802.1x port-based authentication, you must enable authentication, authorization, and
accounting (AAA) and specify the authentication method list. A method list describes the sequence and
authentication method to be queried to authenticate a user.
To allow per-user ACLs or VLAN assignment, you must enable AAA authorization to configure the
switch for all network-related service requests.
This is the IEEE 802.1x AAA process:
Step 1
A user connects to a port on the switch.
Step 2
Authentication is performed.
Step 3
VLAN assignment is enabled, as appropriate, based on the RADIUS server configuration.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
9-26
OL-12189-01
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Configuring IEEE 802.1x Authentication
Step 4
The switch sends a start message to an accounting server.
Step 5
Re-authentication is performed, as necessary.
Step 6
The switch sends an interim accounting update to the accounting server that is based on the result of
re-authentication.
Step 7
The user disconnects from the port.
Step 8
The switch sends a stop message to the accounting server.
Beginning in privileged EXEC mode, follow these steps to configure IEEE 802.1x port-based
authentication:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
aaa new-model
Enable AAA.
Step 3
aaa authentication dot1x {default}
method1
Create an IEEE 802.1x authentication method list.
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.
Step 4
dot1x system-auth-control
Enable IEEE 802.1x authentication globally on the switch.
Step 5
aaa authorization network {default}
group radius
(Optional) Configure the switch to use user-RADIUS authorization for all
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
radius-server host ip-address
(Optional) Specify the IP address of the RADIUS server.
Step 7
radius-server key string
(Optional) Specify the authentication and encryption key used between
the switch and the RADIUS daemon running on the RADIUS server.
Step 8
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 9
switchport mode access
(Optional) Set the port to access mode only if you configured the RADIUS
server in Step 6 and Step 7.
Step 10
dot1x port-control auto
Enable IEEE 802.1x authentication on the port.
For feature interaction information, see the IEEE 802.1x Authentication
Configuration Guidelines section on page 9-24.
Step 11
end
Return to privileged EXEC mode.
Step 12
show dot1x
Verify your entries.
Step 13
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
9-27
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Configuring IEEE 802.1x Authentication
Configuring the Switch-to-RADIUS-Server Communication
RADIUS security servers are identified by their hostname or IP address, hostname and specific UDP port
numbers, or IP address and specific UDP port numbers. The combination of the IP address and UDP port
number creates a unique identifier, which enables RADIUS requests to be sent to multiple UDP ports on
a server at the same IP address. If two different host entries on the same RADIUS server are configured
for the same servicefor example, authenticationthe second host entry configured acts as the fail-over
backup to the first one. The RADIUS host entries are tried in the order that they were configured.
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.
If you want to use multiple RADIUS servers, re-enter this command.
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 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
9-28
OL-12189-01
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Configuring IEEE 802.1x Authentication
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.
Configuring the Host Mode
Beginning in privileged EXEC mode, follow these steps to allow multiple hosts (clients) on an
IEEE 802.1x-authorized port that has the dot1x port-control interface configuration command set to
auto. Use the multi-domain keyword to configure and enable multidomain authentication (MDA),
which allows both a host and a voice device, such as an IP phone (Cisco or non-Cisco), on the same
switch port. 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
dot1x host-mode {multi-host |
multi-domain}
Allow multiple hosts (clients) on an IEEE 802.1x-authorized port.
The keywords have these meanings:
multi-hostAllow multiple hosts on an IEEE 802.1x-authorized port
after a single host has been authenticated.
multi-domainAllow both a host and a voice device, such as an IP
phone (Cisco or non-Cisco), to be authenticated on an
IEEE 802.1x-authorized port.
Note
You must configure the voice VLAN for the IP phone when the
host mode is set to multi-domain. For more information, see
Chapter 14, Configuring Voice VLAN.
Make sure that the dot1x port-control interface configuration command
set is set to auto for the specified interface.
Step 4
end
Return to privileged EXEC mode.
Step 5
show dot1x interface interface-id
Verify your entries.
Step 6
copy running-config startup-config
(Optional) Save your entries in the configuration file.
To disable multiple hosts on the port, use the no dot1x host-mode multi-host interface configuration
command.
This example shows how to enable IEEE 802.1x authentication and to allow multiple hosts:
Switch(config)# interface gigabitethernet2/0/1
Switch(config-if)# dot1x port-control auto
Switch(config-if)# dot1x host-mode multi-host
This example shows how to enable MDA and to allow both a host and a voice device on the port:
Switch(config)# interface gigabitethernet3/0/1
Switch(config-if)# dot1x port-control auto
Switch(config-if)# dot1x host-mode multi-domain
Switch(config-if)# switchport voice vlan 101
Switch(config-if)# end
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
9-29
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Configuring IEEE 802.1x Authentication
Configuring Periodic Re-Authentication
You can enable periodic IEEE 802.1x client re-authentication and specify how often it occurs. If you do
not specify a time period before enabling re-authentication, the number of seconds between attempts is
3600.
Beginning in privileged EXEC mode, follow these steps to enable periodic re-authentication of the client
and to configure the number of seconds between re-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.
Step 3
dot1x reauthentication
Enable periodic re-authentication of the client, which is disabled by
default.
Step 4
dot1x timeout reauth-period {seconds | Set the number of seconds between re-authentication attempts.
server}
The keywords have these meanings:
secondsSets the number of seconds from 1 to 65535; the default is
3600 seconds.
serverSets the number of seconds based on the value of the
Session-Timeout RADIUS attribute (Attribute[27]) and the
Termination-Action RADIUS attribute (Attribute [29]).
This command affects the behavior of the switch only if periodic
re-authentication is enabled.
Step 5
end
Return to privileged EXEC mode.
Step 6
show dot1x interface interface-id
Verify your entries.
Step 7
copy running-config startup-config
(Optional) Save your entries in the configuration file.
To disable periodic re-authentication, use the no dot1x reauthentication interface configuration
command. To return to the default number of seconds between re-authentication attempts, use the no
dot1x timeout reauth-period interface configuration command.
This example shows how to enable periodic re-authentication and set the number of seconds between
re-authentication attempts to 4000:
Switch(config-if)# dot1x reauthentication
Switch(config-if)# dot1x timeout reauth-period 4000
Manually Re-Authenticating a Client Connected to a Port
You can manually re-authenticate the client connected to a specific port at any time by entering the dot1x
re-authenticate interface interface-id privileged EXEC command. This step is optional. If you want to
enable or disable periodic re-authentication, see the Configuring Periodic Re-Authentication section
on page 9-30.
This example shows how to manually re-authenticate the client connected to a port:
Switch# dot1x re-authenticate interface gigabitethernet2/0/1
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
9-30
OL-12189-01
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Configuring IEEE 802.1x Authentication
Changing the Quiet Period
When the switch cannot authenticate the client, the switch remains idle for a set period of time and then
tries again. The dot1x timeout quiet-period interface configuration command controls the idle period.
A failed authentication of the client might occur because the client provided an invalid password. You
can provide a faster response time to the user by entering a number smaller than the default.
Beginning in privileged EXEC mode, follow these steps to change the quiet period. 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 timeout quiet-period 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 dot1x 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 quiet time, use the no dot1x timeout quiet-period interface configuration
command.
This example shows how to set the quiet time on the switch to 30 seconds:
Switch(config-if)# dot1x timeout quiet-period 30
Changing the Switch-to-Client Retransmission Time
The client responds to the EAP-request/identity frame from the switch with an EAP-response/identity
frame. If the switch does not receive this response, it waits a set period of time (known as the
retransmission time) and then resends the frame.
Note
You should change the default value of this command only to adjust for unusual circumstances such as
unreliable links or specific behavioral problems with certain clients and authentication servers.
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
dot1x timeout tx-period seconds
Set the number of seconds that the switch waits for a response to an
EAP-request/identity frame from the client before resending the request.
The range is 1 to 65535 seconds; the default is 5.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
9-31
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Configuring IEEE 802.1x Authentication
Command
Purpose
Step 4
end
Return to privileged EXEC mode.
Step 5
show dot1xinterface 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 retransmission time, use the no dot1x timeout tx-period 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)# dot1x timeout tx-period 60
Setting the Switch-to-Client Frame-Retransmission Number
In addition to changing the switch-to-client retransmission time, you can change the number of times
that the switch sends an EAP-request/identity frame (assuming no response is received) to the client
before restarting the authentication process.
Note
You should change the default value of this command only to adjust for unusual circumstances such as
unreliable links or specific behavioral problems with certain clients and authentication servers.
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 dot1x 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 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-req 5
Setting the Re-Authentication Number
You can also change the number of times that the switch restarts the authentication process before the
port changes to the unauthorized state.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
9-32
OL-12189-01
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Configuring IEEE 802.1x Authentication
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-reauth-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 0 to 10; the
default is 2.
Step 4
end
Return to privileged EXEC mode.
Step 5
show dot1x 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 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
Configuring IEEE 802.1x Accounting
Enabling AAA system accounting with IEEE 802.1x accounting allows system reload events to be sent
to the accounting RADIUS server for logging. The server can then infer that all active IEEE 802.1x
sessions are closed.
Because RADIUS uses the unreliable UDP transport protocol, accounting messages might be lost due to
poor network conditions. If the switch does not receive the accounting response message from the
RADIUS server after a configurable number of retransmissions of an accounting request, this system
message appears:
Accounting message %s for session %s failed to receive Accounting Response.
When the stop message is not sent successfully, this message appears:
00:09:55: %RADIUS-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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
9-33
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Configuring IEEE 802.1x Authentication
Beginning in privileged EXEC mode, follow these steps to configure IEEE 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
interface interface-id
Specify the port to be configured, and enter interface configuration mode.
Step 3
aaa accounting dot1x default
start-stop group radius
Enable IEEE 802.1x accounting using the list of all RADIUS servers.
Step 4
aaa accounting system default
start-stop group radius
(Optional) Enables system accounting (using the list of all RADIUS
servers) and generates system accounting reload event messages when the
switch reloads.
Step 5
end
Return to privileged EXEc mode.
Step 6
show running-config
Verify your entries.
Step 7
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 IEEE 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
Configuring a Guest VLAN
When you configure a guest VLAN, clients that are not IEEE 802.1x-capable are put into the guest
VLAN when the server does not receive a response to its EAP request/identity frame. Clients that are
IEEE 802.1x-capable but that fail authentication are not granted network access. The switch supports
guest VLANs in single-host or multiple-hosts mode.
Beginning in privileged EXEC mode, follow these steps to configure a guest VLAN. 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 IEEE 802.1x Authentication
Configuration Guidelines section on page 9-24.
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.
dot1x port-control auto
Enable IEEE 802.1x authentication on the port.
Step 4
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
9-34
OL-12189-01
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Configuring IEEE 802.1x Authentication
Step 5
Command
Purpose
dot1x guest-vlan vlan-id
Specify an active VLAN as an IEEE 802.1x guest VLAN. The range is 1
to 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 IEEE 802.1x guest VLAN.
Step 6
end
Return to privileged EXEC mode.
Step 7
show dot1x interface interface-id
Verify your entries.
Step 8
copy running-config startup-config
(Optional) Save your entries in the configuration file.
To disable and remove the guest VLAN, use the no dot1x guest-vlan interface configuration command.
The port returns to the unauthorized state.
This example shows how to enable VLAN 2 as an IEEE 802.1x guest VLAN:
Switch(config)# interface gigabitethernet2/0/2
Switch(config-if)# dot1x guest-vlan 2
This example shows how to set 3 as the quiet time on the switch, to set 15 as the number of seconds that
the switch waits for a response to an EAP-request/identity frame from the client before re-sending the
request, and to enable VLAN 2 as an IEEE 802.1x guest VLAN when an IEEE 802.1x port is connected
to a DHCP client:
Switch(config-if)# dot1x timeout quiet-period 3
Switch(config-if)# dot1x timeout tx-period 15
Switch(config-if)# dot1x guest-vlan 2
Configuring a Restricted VLAN
When you configure a restricted VLAN on a switch stack or a switch, clients that are
IEEE 802.1x-compliant are moved into the restricted VLAN when the authentication server does not
receive a valid username and password. The switch supports restricted VLANs only in single-host mode.
Beginning in privileged EXEC mode, follow these steps to configure a restricted VLAN. 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 IEEE 802.1x Authentication
Configuration Guidelines section on page 9-24.
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.
dot1x port-control auto
Enable IEEE 802.1x authentication on the port.
Step 4
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
9-35
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Configuring IEEE 802.1x Authentication
Step 5
Command
Purpose
dot1x auth-fail vlan vlan-id
Specify an active VLAN as an IEEE 802.1x restricted VLAN. The range
is 1 to 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 IEEE 802.1x restricted VLAN.
Step 6
end
Return to privileged EXEC mode.
Step 7
show dot1x interface interface-id
(Optional) Verify your entries.
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 IEEE 802.1x restricted VLAN:
Switch(config)# interface gigabitethernet2/0/2
Switch(config-if)# dot1x auth-fail vlan 2
You can configure the maximum number of authentication attempts allowed before a user is assigned to
the restricted VLAN by using the dot1x auth-fail max-attempts interface configuration command. 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 IEEE 802.1x Authentication
Configuration Guidelines section on page 9-24.
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
dot1x port-control auto
Enable IEEE 802.1x authentication on the port.
Step 5
dot1x auth-fail vlan vlan-id
Specify an active VLAN as an IEEE 802.1x restricted VLAN. The range
is 1 to 4094.
You can configure any active VLAN except an internal VLAN (routed
port), an RSPAN VLAN or a voice VLAN as an IEEE 802.1x restricted
VLAN.
Step 6
dot1x auth-fail max-attempts max
attempts
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.
Step 7
end
Return to privileged EXEC mode.
Step 8
show dot1x interface interface-id
(Optional) Verify your entries.
Step 9
copy running-config startup-config
(Optional) Save your entries in the configuration file.
To return to the default value, use the no dot1x auth-fail max-attempts interface configuration
command.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
9-36
OL-12189-01
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Configuring IEEE 802.1x Authentication
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)# dot1x auth-fail max-attempts 2
Configuring the Inaccessible Authentication Bypass Feature
You can configure the inaccessible bypass feature, also referred to as critical authentication or the AAA
fail policy.
Beginning in privileged EXEC mode, follow these steps to configure the port as a critical port and enable
the inaccessible authentication bypass feature. This procedure is optional.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
radius-server dead-criteria time time
tries tries
(Optional) Set the conditions that are used to decide when a RADIUS
server is considered unavailable or dead.
The range for time is from 1 to 120 seconds. The switch dynamically
determines the default seconds value that is 10 to 60 seconds.
The range for tries is from 1 to 100. The switch dynamically determines
the default tries parameter that is 10 to 100.
Step 3
radius-server deadtime minutes
(Optional) Set the number of minutes that a RADIUS server is not sent
requests. The range is from 0 to 1440 minutes (24 hours). The default is
0 minutes.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
9-37
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Configuring IEEE 802.1x Authentication
Step 4
Command
Purpose
radius-server host ip-address
[acct-port udp-port] [auth-port
udp-port][test username name
[idle-time time] [ignore-acct-port]
[ignore-auth-port]] [key string]
(Optional) Configure the RADIUS server parameters by using these
keywords:
acct-port udp-portSpecify the UDP port for the RADIUS
accounting server. The range for the UDP port number is from 0 to
65536. The default is 1646.
auth-port udp-portSpecify the UDP port for the RADIUS
authentication server. The range for the UDP port number is from 0
to 65536. The default is 1645.
Note
You should configure the UDP port for the RADIUS accounting
server and the UDP port for the RADIUS authentication server to
nondefault values.
test username nameEnable automated testing of the RADIUS
server status, and specify the username to be used.
idle-time timeSet the interval of time in minutes after which the
switch sends test packets to the server. The range is from 1 to
35791 minutes. The default is 60 minutes (1 hour).
ignore-acct-portDisable testing on the RADIUS-server
accounting port.
ignore-auth-portDisable testing on the RADIUS-server
authentication port.
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.
You can also configure the authentication and encryption key by
using the radius-server key {0 string | 7 string | string} global
configuration command.
Step 5
dot1x critical {eapol | recovery delay
milliseconds}
(Optional) Configure the parameters for inaccessible authentication
bypass:
eapolSpecify that the switch sends an EAPOL-Success message when
the switch successfully authenticates the critical port.
recovery delay millisecondsSet the recovery delay period during
which the switch waits to re-initialize a critical port when a RADIUS
server that was unavailable becomes available. The range is from 1 to
10000 milliseconds. The default is 1000 milliseconds (a port can be
re-initialized every second).
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
9-38
OL-12189-01
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Configuring IEEE 802.1x Authentication
Command
Purpose
Step 6
interface interface-id
Specify the port to be configured, and enter interface configuration mode.
For the supported port types, see the IEEE 802.1x Authentication
Configuration Guidelines section on page 9-24.
Step 7
dot1x critical [recovery action
reinitialize | vlan vlan-id]
Enable the inaccessible authentication bypass feature, and use these
keywords to configure the feature:
recovery action reinitializeEnable the recovery feature, and
specify that the recovery action is to authenticate the port when an
authentication server is available.
vlan vlan-idSpecify the access VLAN to which the switch can
assign a critical port. The range is from 1 to 4094.
Step 8
end
Return to privileged EXEC mode.
Step 9
show dot1x [interface interface-id]
(Optional) Verify your entries.
Step 10
copy running-config startup-config
(Optional) Save your entries in the configuration file.
To return to the RADIUS server default settings, use the no radius-server dead-criteria, the no
radius-server deadtime, and the no radius-server host global configuration commands. To return to
the default settings of inaccessible authentication bypass, use the no dot1x critical {eapol | recovery
delay} global configuration command. To disable inaccessible authentication bypass, use the no dot1x
critical interface configuration command.
This example shows how to configure the inaccessible authentication bypass feature:
Switch(config)# radius-server dead-criteria time 30 tries 20
Switch(config)# radius-server deadtime 60
Switch(config)# radius-server host 1.1.1.2 acct-port 1550 auth-port 1560 test username
user1 idle-time 30 key abc1234
Switch(config)# dot1x critical eapol
Switch(config)# dot1x critical recovery delay 2000
Switch(config)# interface gigabitethernet 1/0/1
Switch(config)# radius-server deadtime 60
Switch(config-if)# dot1x critical
Switch(config-if)# dot1x critical recovery action reinitialize
Switch(config-if)# dot1x critical vlan 20
Switch(config-if)# end
Configuring IEEE 802.1x Authentication with WoL
Beginning in privileged EXEC mode, follow these steps to enable IEEE 802.1x authentication with WoL.
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 IEEE 802.1x Authentication
Configuration Guidelines section on page 9-24.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
9-39
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Configuring IEEE 802.1x Authentication
Step 3
Command
Purpose
dot1x control-direction {both | in}
Enable IEEE 802.1x authentication with WoL on the port, and use these
keywords to configure the port as bidirectional or unidirectional.
bothSets the port as bidirectional. The port cannot receive packets
from or send packets to the host. By default, the port is bidirectional.
inSets the port as unidirectional. The port can send packets to the
host but cannot receive packets from the host.
Step 4
end
Return to privileged EXEC mode.
Step 5
show dot1x interface interface-id
Verify your entries.
Step 6
copy running-config startup-config
(Optional) Save your entries in the configuration file.
To disable IEEE 802.1x authentication with WoL, use the no dot1x control-direction interface
configuration command.
This example shows how to enable IEEE 802.1x authentication with WoL and set the port as
bidirectional:
Switch(config-if)# dot1x control-direction both
Configuring MAC Authentication Bypass
Beginning in privileged EXEC mode, follow these steps to enable MAC authentication bypass. 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 IEEE 802.1x Authentication
Configuration Guidelines section on page 9-24.
Step 3
dot1x port-control auto
Enable IEEE 802.1x authentication on the port.
Step 4
dot1x mac-auth-bypass [eap]
Enable MAC authentication bypass.
(Optional) Use the eap keyword to configure the switch to use EAP for
authorization.
Step 5
end
Return to privileged EXEC mode.
Step 6
show dot1x interface interface-id
Verify your entries.
Step 7
copy running-config startup-config
(Optional) Save your entries in the configuration file.
To disable MAC authentication bypass, use the no dot1x mac-auth-bypass interface configuration
command.
This example shows how to enable MAC authentication bypass:
Switch(config-if)# dot1x mac-auth-bypass
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
9-40
OL-12189-01
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Configuring IEEE 802.1x Authentication
Configuring NAC Layer 2 IEEE 802.1x Validation
You can configure NAC Layer 2 IEEE 802.1x validation, which is also referred to as IEEE 802.1x
authentication with a RADIUS server.
Beginning in privileged EXEC mode, follow these steps to configure NAC Layer 2 IEEE 802.1x
validation. The 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 guest-vlan vlan-id
Specify an active VLAN as an IEEE 802.1x guest VLAN. The range is 1
to 4094.
You can configure any active VLAN except an internal VLAN (routed
port), an RSPAN VLAN, or a voice VLAN as an IEEE 802.1x guest
VLAN.
Step 4
dot1x reauthentication
Step 5
dot1x timeout reauth-period {seconds | Set the number of seconds between re-authentication attempts.
server}
The keywords have these meanings:
Enable periodic re-authentication of the client, which is disabled by
default.
secondsSets the number of seconds from 1 to 65535; the default is
3600 seconds.
serverSets the number of seconds based on the value of the
Session-Timeout RADIUS attribute (Attribute[27]) and the
Termination-Action RADIUS attribute (Attribute [29]).
This command affects the behavior of the switch only if periodic
re-authentication is enabled.
Step 6
end
Return to privileged EXEC mode.
Step 7
show dot1x interface interface-id
Verify your IEEE 802.1x authentication configuration.
Step 8
copy running-config startup-config
(Optional) Save your entries in the configuration file.
This example shows how to configure NAC Layer 2 IEEE 802.1x validation:
Switch# configure terminal
Switch(config)# interface gigabitethernet2/0/1
Switch(config-if)# dot1x reauthentication
Switch(config-if)# dot1x timeout reauth-period server
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
9-41
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Configuring IEEE 802.1x Authentication
Configuring Web Authentication
Beginning in privileged EXEC mode, follow these steps to configure authentication, authorization,
accounting (AAA) and RADIUS on a switch before configuring web authentication. The steps enable
AAA by using RADIUS authentication and enable device tracking.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
aaa new-model
Enable AAA.
Step 3
aaa authentication login default group
radius
Use RADIUS authentication. Before you can use this authentication
method, you must configure the RADIUS server. For more
information, see Chapter 7, Configuring Switch-Based
Authentication.
The console prompts you for a username and password on future
attempts to access the switch console after entering the aaa
authentication login command. If you do not want to be prompted for
a username and password, configure a second login authentication
list:
Switch# configure terminal
Switch(config)# aaa authentication login line-console none
Switch(config)# line console 0
Switch(config-line)# login authentication line-console
Switch(config-line)# end
Step 4
aaa authorization auth-proxy default
group radius
Use RADIUS for authentication-proxy (auth-proxy) authorization.
Step 5
radius-server host key radius-key
Specify the authentication and encryption key for RADIUS
communication between the switch and the RADIUS daemon.
Step 6
radius-server attribute 8
include-in-access-req
Configure the switch to send the Framed-IP-Address RADIUS
attribute (Attribute[8]) in access-request or accounting-request
packets.
Step 7
radius-server vsa send authentication
Configure the network access server to recognize and use
vendor-specific attributes (VSAs).
Step 8
ip device tracking
Enable the IP device tracking table.
To disable the IP device tracking table, use the no ip device tracking
global configuration commands.
Step 9
end
Return to privileged EXEC mode.
This example shows how to enable AAA, use RADIUS authentication and enable device tracking:
Switch(config) configure terminal
Switch(config)# aaa new-model
Switch(config)# aaa authentication login default group radius
Switch(config)# aaa authorization auth-proxy default group radius
Switch(config)# radius-server host 1.1.1.2 key key1
Switch(config)# radius-server attribute 8 include-in-access-req
Switch(config)# radius-server vsa send authentication
Switch(config)# ip device tracking
Switch(config) end
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
9-42
OL-12189-01
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Configuring IEEE 802.1x Authentication
Beginning in privileged EXEC mode, follow these steps to configure a port to use web authentication:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ip admission name rule proxy http
Define a web authentication rule.
Note
The same rule cannot be used for both web authentication and
NAC Layer 2 IP validation. For more information, see the
Network Admission Control Software Configuration Guide on
Cisco.com.
Step 3
interface interface-id
Specify the port to be configured, and enter interface configuration
mode.
Step 4
switchport mode access
Set the port to access mode.
Step 5
ip access-group access-list in
Specify the default access control list to be applied to network traffic
before web authentication.
Step 6
ip admission rule
Apply an IP admission rule to the interface.
Step 7
end
Return to privileged EXEC mode.
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.
This example shows how to configure only web authentication on a switch port:
Switch# configure terminal
Switch(config)# ip admission name rule1 proxy http
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# switchport mode access
Switch(config-if)# ip access-group policy1 in
Switch(config-if)# ip admission rule1
Switch(config-if)# end
Beginning in privileged EXEC mode, follow these steps to configure a switch port for IEEE 802.1x
authentication with web authentication as a fallback method:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ip admission name rule proxy http
Define a web authentication rule.
Step 3
fallback profile fallback-profile
Define a fallback profile to allow an IEEE 802.1x port to
authenticate a client by using web authentication.
Step 4
ip access-group policy in
Specify the default access control list to apply to network traffic
before web authentication.
Step 5
ip admission rule
Associate an IP admission rule with the profile, and specify that
a client connecting by web authentication uses this rule.
Step 6
end
Return to privileged EXEC mode.
Step 7
interface interface-id
Specify the port to be configured, and enter interface
configuration mode.
Step 8
switchport mode access
Set the port to access mode.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
9-43
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Configuring IEEE 802.1x Authentication
Command
Purpose
Step 9
dot1x port-control auto
Enable IEEE 802.1x authentication on the interface.
Step 10
dot1x fallback fallback-profile
Configure the port to authenticate a client by using web
authentication when no IEEE 802.1x supplicant is detected on the
port. Any change to the fallback-profile global configuration takes
effect the next time IEEE 802.1x fallback is invoked on the interface.
Note
Web authorization cannot be used as a fallback method for
IEEE 802.1x if the port is configured for multidomain
authentication.
Step 11
exit
Return to privileged EXEC mode.
Step 12
show dot1x interface interface-id
Verify your configuration.
Step 13
copy running-config startup-config
(Optional) Save your entries in the configuration file.
This example shows how to configure IEEE 802.1x authentication with web authentication as a fallback
method.
Switch(config) configure terminal
Switch(config)# ip admission name rule1 proxy http
Switch(config)# fallback profile fallback1
Switch(config-fallback-profile)# ip access-group default-policy in
Switch(config-fallback-profile)# ip admission rule1
Switch(config-fallback-profile)# exit
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# switchport mode access
Switch(config-if)# dot1x port-control auto
Switch(config-if)# dot1x fallback fallback1
Switch(config-if)# end
For more information about the ip admission name and dot1x fallback commands, see the command
reference for this release. For more information about the ip admission name and ip access-group
commands, see the Network Admission Control Software Configuration Guide on Cisco.com.
Disabling IEEE 802.1x Authentication on the Port
You can disable IEEE 802.1x authentication on the port by using the no dot1x pae interface
configuration command.
Beginning in privileged EXEC mode, follow these steps to disable IEEE 802.1x authentication on the
port. 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
no dot1x pae
Disable IEEE 802.1x authentication on the port.
Step 4
end
Return to privileged EXEC mode.
Step 5
show dot1x interface interface-id
Verify your entries.
Step 6
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
9-44
OL-12189-01
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Displaying IEEE 802.1x Statistics and Status
To configure the port as an IEEE 802.1x port access entity (PAE) authenticator, which enables
IEEE 802.1x on the port but does not allow clients connected to the port to be authorized, use the dot1x
pae authenticator interface configuration command.
This example shows how to disable IEEE 802.1x authentication on the port:
Switch(config)# interface gigabitethernet2/0/1
Switch(config-if)# no dot1x pae authenticator
Resetting the IEEE 802.1x Authentication Configuration to the Default Values
Beginning in privileged EXEC mode, follow these steps to reset the IEEE 802.1x authentication
configuration to the default values. This procedure is optional.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
interface interface-id
Enter interface configuration mode, and specify the port to be configured.
Step 3
dot1x default
Reset the IEEE 802.1x parameters to the default values.
Step 4
end
Return to privileged EXEC mode.
Step 5
show dot1x interface interface-id
Verify your entries.
Step 6
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Displaying IEEE 802.1x Statistics and Status
To display IEEE 802.1x statistics for all ports, use the show dot1x all statistics privileged EXEC
command. To display IEEE 802.1x statistics for a specific port, use the show dot1x statistics interface
interface-id privileged EXEC command.
To display the IEEE 802.1x administrative and operational status for the switch, use the show dot1x all
[details | statistics | summary] privileged EXEC command. To display the IEEE 802.1x administrative
and operational status for a specific port, use the show dot1x interface interface-id privileged EXEC
command.
For detailed information about the fields in these displays, see the command reference for this release.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
9-45
Chapter 9
Configuring IEEE 802.1x Port-Based Authentication
Displaying IEEE 802.1x Statistics and Status
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
9-46
OL-12189-01
CH A P T E R
10
Configuring Interface Characteristics
This chapter defines the types of interfaces on the switch and describes how to configure them. Unless
otherwise noted, the term switch refers to a standalone switch and to a switch stack.
The chapter consists of these sections:
Note
Understanding Interface Types, page 10-1
Using Interface Configuration Mode, page 10-7
Using the Internal Ethernet Management Port, page 10-12
Configuring Ethernet Interfaces, page 10-14
Configuring Layer 3 Interfaces, page 10-20
Configuring the System MTU, page 10-22
Monitoring and Maintaining the Interfaces, page 10-24
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.
Understanding Interface Types
This section describes the different types of interfaces supported by the switch with references to
chapters that contain more detailed information about configuring these interface types. The rest of the
chapter describes configuration procedures for physical interface characteristics.
Note
The stack ports on the front of the switch are not Ethernet ports and cannot be configured.
These sections describe the interface types:
Port-Based VLANs, page 10-2
Switch Ports, page 10-2
Routed Ports, page 10-4
Switch Virtual Interfaces, page 10-5
EtherChannel Port Groups, page 10-5
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
10-1
Chapter 10
Configuring Interface Characteristics
Understanding Interface Types
10-Gigabit Ethernet Interfaces, page 10-6
Connecting Interfaces, page 10-6
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 12,
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. VLANs can be formed with ports across the stack.
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. In a switch stack, the VLAN database is downloaded to all switches in a stack, and all switches
in the stack build the same 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. In a switch stack, the running configuration and the saved
configuration are the same for all switches in a stack.
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 16,
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 set the 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 IEEE 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. Use the switchport
command with no keywords to put an interface that is in Layer 3 mode into Layer 2 mode.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
10-2
OL-12189-01
Chapter 10
Configuring Interface Characteristics
Understanding Interface Types
Note
When you put an interface that is in Layer 3 mode into Layer 2 mode, the previous configuration
information related to the affected interface might be lost, and the interface is returned to its default
configuration.
For detailed information about configuring access port and trunk port characteristics, see Chapter 12,
Configuring VLANs. For more information about tunnel ports, see Chapter 16, 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 IEEE 802.1Q tagged), the packet is dropped, and the source address
is not learned.
Two types of access ports are supported:
Static access ports are manually assigned to a VLAN (or through a RADIUS server for use with
IEEE 802.1x. For more information, see the Using IEEE 802.1x Authentication with VLAN
Assignment section on page 9-10.)
VLAN membership of dynamic access ports is learned through incoming packets. By default, a
dynamic access port is not a member of any VLAN, and forwarding to and from the port is enabled
only when the VLAN membership of the port is discovered. Dynamic access ports on the switch are
assigned to a VLAN by a VLAN Membership Policy Server (VMPS). The VMPS can be a
Catalyst 6500 series switch; the switch cannot be a VMPS server.
You can also 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. For more information about voice
VLAN ports, see Chapter 14, Configuring Voice VLAN.
Trunk Ports
A trunk port carries the traffic of multiple VLANs and by default is a member of all VLANs in the VLAN
database. These trunk port types are supported:
In an ISL trunk port, all received packets are expected to be encapsulated with an ISL header, and
all transmitted packets are sent with an ISL header. Native (non-tagged) frames received from an
ISL trunk port are dropped.
An IEEE 802.1Q trunk port supports simultaneous tagged and untagged traffic. An IEEE 802.1Q
trunk port is assigned a default port VLAN ID (PVID), and all untagged traffic travels on the port
default PVID. All untagged traffic and tagged traffic with a NULL VLAN ID are assumed to belong
to the port default PVID. A packet with a VLAN ID equal to the outgoing port default PVID is sent
untagged. All other traffic is sent with a VLAN tag.
Although by default, a trunk port is a member of every VLAN known to the VTP, you can limit VLAN
membership by configuring an allowed list of VLANs for each trunk port. The list of allowed VLANs
does not affect any other port but the associated trunk port. By default, all possible VLANs (VLAN ID 1
to 4094) are in the allowed list. A trunk port can become a member of a VLAN only if VTP knows of
the VLAN and if the VLAN is in the enabled state. If VTP learns of a new, enabled VLAN and the VLAN
is in the allowed list for a trunk port, the trunk port automatically becomes a member of that VLAN and
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
10-3
Chapter 10
Configuring Interface Characteristics
Understanding Interface Types
traffic is forwarded to and from the trunk port for that VLAN. If VTP learns of a new, enabled VLAN
that is not in the allowed list for a trunk port, the port does not become a member of the VLAN, and no
traffic for the VLAN is forwarded to or from the port.
For more information about trunk ports, see Chapter 12, Configuring VLANs.
Tunnel Ports
Tunnel ports are used in IEEE 802.1Q tunneling to segregate the traffic of customers in a
service-provider network from other customers who are using the same VLAN number. You configure
an asymmetric link from a tunnel port on a service-provider edge switch to an IEEE 802.1Q trunk port
on the customer switch. Packets entering the tunnel port on the edge switch, already
IEEE 802.1Q-tagged with the customer VLANs, are encapsulated with another layer of an IEEE 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 to each customer.
For more information about tunnel ports, see Chapter 16, 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.
Note
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. When you put an
interface that is in Layer 2 mode into Layer 3 mode, the previous configuration information related to
the affected interface might be lost.
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 10-20 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 38,
Configuring IP Unicast Routing and Chapter 44, Configuring IP Multicast Routing.
Note
The IP base feature set supports static routing and the Routing Information Protocol (RIP). For full
Layer 3 routing or for fallback bridging, you must enable the IP services feature set on the standalone
switch or the stack master.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
10-4
OL-12189-01
Chapter 10
Configuring Interface Characteristics
Understanding Interface Types
Switch Virtual Interfaces
A switch virtual interface (SVI) represents a VLAN of switch ports as one interface to the routing or
bridging function in the system. Only one SVI can be associated with a VLAN, but you need to configure
an SVI for a VLAN only when you wish to route between VLANs, to fallback-bridge nonroutable
protocols between VLANs, or to provide IP host connectivity to the switch. By default, an SVI is created
for the default VLAN (VLAN 1) to permit remote switch administration. Additional SVIs must be
explicitly configured.
Note
You cannot delete interface VLAN 1.
SVIs provide IP host connectivity only to the system; in Layer 3 mode, you can configure routing across
SVIs.
Although the switch stack or switch supports a total of 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 10-20 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
IEEE 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 38, Configuring IP Unicast Routing, Chapter 44, Configuring IP Multicast
Routing,and Chapter 46, Configuring Fallback Bridging.
Note
The IP base feature set supports static routing and RIP. For more advanced routing or for fallback
bridging, enable the IP services feature set on standalone switch, or the stack master.
EtherChannel Port Groups
EtherChannel port groups treat multiple switch ports as one switch port. These port groups act as a single
logical port for high-bandwidth connections between switches or between switches and servers. An
EtherChannel balances the traffic load across the links in the channel. If a link within the EtherChannel
fails, traffic previously carried over the failed link changes to the remaining links. You can group
multiple trunk ports into one logical trunk port, group multiple access ports into one logical access port,
group multiple tunnel ports into one logical tunnel port, or group multiple routed ports into one logical
routed port. Most protocols operate over either single ports or aggregated switch ports and do not
recognize the physical ports within the port group. Exceptions are the DTP, the Cisco Discovery Protocol
(CDP), and the Port Aggregation Protocol (PAgP), which operate only on physical ports.
When you configure an EtherChannel, you create a port-channel logical interface and assign an interface
to the EtherChannel. For Layer 3 interfaces, you manually create the logical interface by using the
interface port-channel global configuration command. Then you manually assign an interface to the
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
10-5
Chapter 10
Configuring Interface Characteristics
Understanding Interface Types
EtherChannel by using the channel-group interface configuration command. For Layer 2 interfaces, use
the channel-group interface configuration command to dynamically create the port-channel logical
interface. This command binds the physical and logical ports together. For more information, see
Chapter 37, Configuring EtherChannels and Link-State Tracking.
10-Gigabit Ethernet Interfaces
The switch has one 10-Gigabit Ethernet module slot.
A 10-Gigabit Ethernet interface operates only in full-duplex mode. The interface can be configured as a
switched or routed port.
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.
By using the switch with routing enabled, when you configure both VLAN 20 and VLAN 30 with an
SVI to which an IP address is assigned, packets can be sent from Blade Server A to Blade Server B
directly through the switch with no need for an external router (Figure 10-1).
Figure 10-1
Connecting VLANs with the Blade Switch
Layer 3 switch
with routing enabled
SVI 1
SVI 2
Blade
server A
172.20.129.1
Blade
server B
VLAN 20
VLAN 30
201763
172.20.128.1
When the IP services feature set is running on the switch or the stack master, the switch uses two
methods to forward traffic between interfaces: routing and fallback bridging. If the IP base feature set is
on the switch or the stack master, only basic routing (static routing and RIP) is supported. Whenever
possible, to maintain high performance, forwarding is done by the switch hardware. However, only IPv4
packets with Ethernet II encapsulation are routed in hardware. Non-IP traffic and traffic with other
encapsulation methods are 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 38,
Configuring IP Unicast Routing, Chapter 44, Configuring IP Multicast Routing, and
Chapter 45, Configuring MSDP.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
10-6
OL-12189-01
Chapter 10
Configuring Interface Characteristics
Using Interface Configuration Mode
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 46, Configuring Fallback Bridging.
Using Interface Configuration Mode
The switch supports these interface types:
Physical portsswitch ports and routed ports
VLANsswitch virtual interfaces
Port channelsEtherChannel interfaces
You can also configure a range of interfaces (see the Configuring a Range of Interfaces section on
page 10-9).
To configure a physical interface (port), specify the interface type, stack member number, module number,
and switch port number, and enter interface configuration mode.
TypeGigabit Ethernet (gigabitethernet or gi) for 10/100/1000 Mb/s Ethernet ports or 10-Gigabit
Ethernet (tengigabitethernet or te) for 10,000 Mb/s.
Stack member numberThe number that identifies the switch within the stack. The switch number
range is 1 to 9 and is assigned the first time the switch initializes. The default switch number, before
it is integrated into a switch stack, is 1. When a switch has been assigned a stack member number,
it keeps that number until another is assigned to it.
You can use the switch port LEDs in Stack mode to identify the stack member number of a switch.
For information about stack member numbers, see the Stack Member Numbers section on
page 5-8.
Module numberThe module or slot number on the switch that is always 0.
Port numberThe interface number on the switch.
These are the port numbers on the Catalyst Module Switch 3110X:
The internal 1000 Mb/s ports are numbered consecutively from 1 to 14; for example,
gigabitethernet 1/0/1.
When a Cisco X2 transceiver module is in the 10-Gigabit Ethernet module slot, the port
numberis 1; for example, tengigabitethernet1/0/1.
These are the port numbers on the Catalyst Switch Module 3110G:
The internal 1000 Mb/s ports are numbered consecutively from 1 to 14; for example,
gigabitethernet 1/0/1.
On a switch with four external 10/100/1000 ports, the external 10/100/1000 port numbers are
numbered from 15 to 18; for example, gigabitethernet1/0/16.
These are the port numbers on a Catalyst Switch Module 3012 with 12 internal 1000 Mb/s ports and
4 external 10/100/1000 ports:
The internal ports are numbered consecutively from 1 to 12; for example, gigabitethernet 0/3.
The external ports are numbered consecutively from 13 to 16; for example, gigabitethernet0/15.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
10-7
Chapter 10
Configuring Interface Characteristics
Using Interface Configuration Mode
You can identify physical interfaces by physically checking the interface location on the switch. You can
also use the show privileged EXEC commands to display information about a specific interface or all
the interfaces on the switch. The remainder of this chapter primarily provides physical interface
configuration procedures.
These are examples of how to identify interfaces:
To configure 10/100/1000 port 4 on a standalone switch, enter this command:
Switch(config)# interface gigabitethernet1/0/4
To configure 10-Gigabit Ethernet port 1 on a standalone switch, enter this command:
Switch(config)# interface tengigabitethernet1/0/1
To configure 10-Gigabit Ethernet port on stack member 3, enter this command:
Switch(config)# interface tengigabitethernet3/0/1
Procedures for Configuring Interfaces
These general instructions apply to all interface configuration processes.
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, the switch number, and
the number of the connector. In this example, Gigabit Ethernet port 1 on switch 1 is selected:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)#
Note
Step 3
You do not need to add a space between the interface type and the interface number. For example,
in the preceding line, you can specify either gigabitethernet 1/0/1, gigabitethernet1/0/1,
gi 1/0/1, or gi1/0/1.
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 10-24.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
10-8
OL-12189-01
Chapter 10
Configuring Interface Characteristics
Using Interface Configuration Mode
Configuring a Range of Interfaces
You can use the interface range global configuration command to configure multiple interfaces with the
same configuration parameters. When you enter the interface-range configuration mode, all command
parameters that you enter are attributed to all interfaces within that range until you exit this mode.
Beginning in privileged EXEC mode, follow these steps to configure a range of interfaces with the
same parameters:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
interface range {port-range | macro
macro_name}
Specify the range of interfaces (VLANs or physical ports) to be
configured, and enter interface-range configuration mode.
Step 3
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 10-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.
Use the normal configuration commands to apply the configuration
parameters to all interfaces in the range. Each command is executed
as it is entered.
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 the VLAN ID is 1 to 4094
gigabitethernet stack member/module/{first port} - {last port}, where the module is always 0
tengigabitethernet stack member/module/{first port} - {last port}, where the module is
always 0
port-channel port-channel-number - port-channel-number, where the port-channel-number
is 1 to 48
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 gigabitethernet1/0/1 - 4 is
a valid range; the command interface range gigabitethernet1/0/1-4 is not a valid range.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
10-9
Chapter 10
Configuring Interface Characteristics
Using Interface Configuration Mode
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 in a range must be the same type (all Gigabit Ethernet ports, all 10-Gigabit
Ethernet 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
to 100 Mb/s on ports 1 to 4 on switch 1:
Switch# configure terminal
Switch(config)# interface range gigabitethernet1/0/19 - 20
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
Gigabit Ethernet ports 1 to 3 and 10-Gigabit Ethernet ports 1 and 2 to receive flow-control pause frames:
Switch# configure terminal
Switch(config)# interface range gigabitethernet1/0/1 - 3 , tengigabitethernet1/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 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.
Configuring and Using Interface Range Macros
You can create an interface range macro to automatically select a range of interfaces for configuration.
Before you can use the macro keyword in the interface range macro global configuration command
string, you must use the define interface-range global configuration command to define the macro.
Beginning in privileged EXEC mode, follow these steps to define an interface range macro:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
define interface-range macro_name
interface-range
Define the interface-range macro, and save it in NVRAM.
Step 3
interface range macro macro_name
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.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
10-10
OL-12189-01
Chapter 10
Configuring Interface Characteristics
Using Interface Configuration Mode
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 the VLAN ID is 1 to 4094
gigabitethernet stack member/module/{first port} - {last port}, where the module is always 0
tengigabitethernet stack member/module/{first port} - {last port}, where the module is
always 0
port-channel port-channel-number - port-channel-number, where the port-channel-number
is 1 to 48.
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, gigabitethernet1/0/1 - 4 is a valid range; gigabitethernet1/0/1-4 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 Gigabit Ethernet ports, all 10-Gigabit
Ethernet 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 named enet_list to include ports 1 and 2 on
switch 1 and to verify the macro configuration:
Switch# configure terminal
Switch(config)# define interface-range enet_list gigabitethernet1/0/1 - 2
Switch(config)# end
Switch# show running-config | include define
define interface-range enet_list GigabitEthernet1/0/1 - 2
This example shows how to create a multiple-interface macro named macro1:
Switch# configure terminal
Switch(config)# define interface-range macro1 gigabitethernet1/0/1 - 2,
gigabitethernet1/0/5 - 7, tengigabitethernet1/0/1 -2
Switch(config)# end
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#
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
10-11
Chapter 10
Configuring Interface Characteristics
Using the Internal Ethernet Management Port
Using the Internal Ethernet Management Port
This section has this information:
Understanding the Internal Ethernet Management Port, page 10-12
Supported Features on the Ethernet Management Port, page 10-13
Layer 3 Routing Configuration Guidelines, page 10-14
Monitoring the Ethernet Management Port, page 10-14
Understanding the Internal Ethernet Management Port
The internal Ethernet management port, also referred to as the Fa0 or fastethernet0 port, is an internal
Layer 3 port connected to the Advanced Managment Module (AMM) (see Figure 10-2). You assign the
IP addresses to the internal Ethernet management port through the AMM of a standalone switch. You
can manage the switch through this IP address.
On a standalone switch, the internal Ethernet management port is always enabled (up) and cannot be shut
down. The port is always disabled when the switch is a stack member.
You cannot change the IP address of a stack member by using the AMM. For a nonstacking-capable
switch or a standalone stacking-capable switch, connect the AMM Ethernet management port to the PC
as shown in Figure 10-2.
Connecting a Switch to a PC
Uplink
ports
Network
Blade switch
PC
2
Blade switch
Blade switch
AMM
Internal Ethernet management port
201764
Figure 10-2
Figure 10-3 shows how to connect a switch stack to the PC. The PC does not have to be connected to the
stack master.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
10-12
OL-12189-01
Chapter 10
Configuring Interface Characteristics
Using the Internal Ethernet Management Port
Figure 10-3
Connecting a Switch Stack to a PC
Enclosure 1
PC
Blade switch
Blade switch
2
2
Stack member 1
Blade switch
Blade switch
Stack member 2
Enclosure 2
Stack member 3
2
Blade switch
1
Blade switch
Stack member 4
Blade switch
Blade switch
Stack member 5
Stack member 6
Blade switch
2
1
Blade switch
Blade switch
Advanced Management Module (AMM)
Note
202006
Stack member 7
All of the AMMs in the enclosures lose connectivity to the stack members. Only
network administrators can manage the switch.
Internal Ethernet management port
By default, the Ethernet management port is enabled on a standalone switch. The switch cannot route
packets from the Ethernet management port to a network port and the reverse.
Supported Features on the Ethernet Management Port
On a standalone switch, the Ethernet management port is enabled and supports only these features:
Network Assistant
Telnet with passwords
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
10-13
Chapter 10
Configuring Interface Characteristics
Configuring Ethernet Interfaces
TFTP
Secure Shell (SSH)
DHCP-based autoconfiguration
SMNP (only the ENTITY-MIB and the IF-MIB)
IP ping
Interface features
Speed100 Mb/s (nonconfigurable)
Duplex modeFull (nonconfigurable)
Loopback detection
Caution
IPv4 and IPv6 access control lists (ACLs)
Before enabling a feature on the Ethernet management port, make sure that the feature is supported. If
you try to configure an unsupported feature, such as Cisco Discovery Protocol (CDP), DHCP relay
agent, or routing protocols, on the Ethernet Management port, the feature might not work properly, and
the switch might fail.
Layer 3 Routing Configuration Guidelines
When Layer 3 routing is enabled, you should be aware of these guidelines:
If Routing Information Protocol (RIP) or Open Shortest Path First (OSPF) is enabled, RIP or OSPF
advertises routes with the internal Ethernet management port. By default, RIP and OSPF are
disabled.
Virtual private network routing and forwarding (VRF) can be used to separate the routing domains
for the Ethernet management port and for data packets.
The default gateway is not available. It is available when IP routing is disabled. You can configure
a default route to replace the default gateway.
Monitoring the Ethernet Management Port
To display the link status, use the show interfaces fastethernet 0 privileged EXEC command.
Configuring Ethernet Interfaces
These sections contain this configuration information:
Default Ethernet Interface Configuration, page 10-15
Configuring Interface Speed and Duplex Mode, page 10-16
Configuring IEEE 802.3x Flow Control, page 10-18
Configuring Auto-MDIX on an Interface, page 10-19
Adding a Description for an Interface, page 10-20
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
10-14
OL-12189-01
Chapter 10
Configuring Interface Characteristics
Configuring Ethernet Interfaces
Default Ethernet Interface Configuration
Table 10-1 shows the Ethernet interface default configuration, including some features that apply only
to Layer 2 interfaces. For more details on the VLAN parameters listed in the table, see Chapter 12,
Configuring VLANs. For details on controlling traffic to the port, see Chapter 25, Configuring
Port-Based Traffic Control.
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. When you put an interface that is in Layer 3 mode into Layer 2 mode, the
previous configuration information related to the affected interface might be lost, and the interface is
returned to its default configuration.
Table 10-1
Default Layer 2 Ethernet Interface Configuration
Feature
Default Setting
Operating mode
Layer 2 or switching mode (switchport command).
Allowed VLAN range
VLANs 1 4094.
Default VLAN (for access ports)
VLAN 1 (Layer 2 interfaces only).
Native VLAN (for IEEE 802.1Q
trunks)
VLAN 1 (Layer 2 interfaces only).
VLAN trunking
Switchport mode dynamic auto (supports DTP) (Layer 2 interfaces
only).
Port enable state
All ports are enabled.
Port description
None defined.
Speed
1000 Mb/s for the internal ports (nonconfigurable)
Autonegotiate for the external 10/100/1000-Mb/s ports. (Not
supported on the 10-Gigabit interfaces.)
Duplex mode
Full duplex for the internal ports (nonconfigurable)
Autonegotiate for the external 10/100/1000-Mb/s ports. (Not
supported on the 10-Gigabit interfaces.)
Flow control
Flow control is set to receive: off. It is always off for sent packets.
EtherChannel (PAgP)
Disabled on all Ethernet ports. See Chapter 37, Configuring
EtherChannels and Link-State Tracking.
Port blocking (unknown multicast Disabled (not blocked) (Layer 2 interfaces only). See the
and unknown unicast traffic)
Configuring Port Blocking section on page 25-6.
Broadcast, multicast, and unicast
storm control
Disabled. See the Default Storm Control Configuration section
on page 25-3.
Protected port
Disabled (Layer 2 interfaces only). See the Configuring Protected
Ports section on page 25-5.
Port security
Disabled (Layer 2 interfaces only). See the Default Port Security
Configuration section on page 25-10.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
10-15
Chapter 10
Configuring Interface Characteristics
Configuring Ethernet Interfaces
Table 10-1
Default Layer 2 Ethernet Interface Configuration (continued)
Feature
Default Setting
Port Fast
Disabled. See the Default Optional Spanning-Tree
Configuration section on page 19-12.
Auto-MDIX
Note
Enabled.
Configuring Interface Speed and Duplex Mode
Ethernet interfaces on the switch operate at 10, 100, 1000, or 10,000 Mb/s and in either full- or
half-duplex mode. In full-duplex mode, two stations can send and receive traffic at the same time.
Normally, 10-Mb/s ports operate in half-duplex mode, which means that stations can either receive or
send traffic.
Switch models include external Gigabit Ethernet (10/100/1000-Mb/s) ports, 10-Gigabit Ethernet ports,
and internal 1000 Mb/s ports.
These sections describe how to configure the interface speed and duplex mode:
Speed and Duplex Configuration Guidelines, page 10-16
Setting the Interface Speed and Duplex Parameters, page 10-17
Speed and Duplex Configuration Guidelines
When configuring an interface speed and duplex mode, note these guidelines:
Caution
The 10-Gigabit Ethernet ports do not support the speed and duplex features. These ports operate
only at 10,000 Mb/s and in full-duplex mode.
The external Gigabit Ethernet (10/100/1000-Mb/s) ports support all speed options and all duplex
options (auto, half, and full). However, Gigabit Ethernet ports operating at 1000 Mb/s do not support
half-duplex mode.
The internal Ethernet management ports do not support the speed and duplex features. These ports
operate only at 1000 Mb/s and in full-duplex mode.
If both ends of the line support autonegotiation, we highly recommend the default setting of auto
negotiation.
If one interface supports autonegotiation and the other end does not, configure duplex and speed on
both interfaces; do not use the auto setting on the supported side.
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.
Changing the interface speed and duplex mode configuration might shut down and re-enable the
interface during the reconfiguration.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
10-16
OL-12189-01
Chapter 10
Configuring Interface Characteristics
Configuring Ethernet Interfaces
Setting the Interface Speed and Duplex Parameters
Beginning in privileged EXEC mode, follow these steps to set the speed and duplex mode for a physical
interface:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
interface interface-id
Specify the physical interface to be configured, and enter interface
configuration mode.
Step 3
speed {10 | 100 | 1000 | auto [10 | 100 |
1000] | nonegotiate}
This command is not available on a 10-Gigabit Ethernet interface or
an internal 1000 Mb/s port.
Enter the appropriate speed parameter for the interface:
Enter 10, 100, or 1000 to set a specific speed for the interface.
The 1000 keyword is available only for 10/100/1000 Mb/s ports.
Enter auto to enable the interface to autonegotiate speed with the
connected device. If you use the 10, 100, or the 1000 keywords
with the auto keyword, the port autonegotiates only at the
specified speeds.
For more information about speed settings, see the Speed and Duplex
Configuration Guidelines section on page 10-16.
Step 4
duplex {auto | full | half}
This command is not available on a 10-Gigabit Ethernet interface or
an internal 1000 Mb/s port.
Enter the duplex parameter for the interface.
Enable half-duplex mode (for interfaces operating only at 10 or
100 Mb/s). You cannot configure half-duplex mode for interfaces
operating at 1000 Mb/s.
You can configure the duplex setting when the speed is set to auto.
For more information about duplex settings, see the Speed and
Duplex Configuration Guidelines section on page 10-16.
Step 5
Step 6
Step 7
end
Return to privileged EXEC mode.
show interfaces interface-id
Display the interface speed and duplex mode configuration.
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 interface speed to 100 Mb/s and the duplex mode to half on an
external 10/100/1000 Mb/s port:
Switch# configure terminal
Switch(config)# interface gigabitethernet1/0/17
Switch(config-if)# speed 10
Switch(config-if)# duplex half
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
10-17
Chapter 10
Configuring Interface Characteristics
Configuring Ethernet Interfaces
This example shows how to set the interface speed to 100 Mb/s on an external 10/100/1000 Mb/s port:
Switch# configure terminal
Switch(config)# interface gigabitethernet1/0/17
Switch(config-if)# speed 100
Configuring IEEE 802.3x Flow Control
Flow control enables connected Ethernet ports to control traffic rates during congestion by allowing
congested nodes to pause link operation at the other end. If one port experiences congestion and cannot
receive any more traffic, it notifies the other port by sending a pause frame to stop sending until the
condition clears. Upon receipt of a pause frame, the sending device stops sending any data packets,
which prevents any loss of data packets during the congestion period.
Note
Switch ports can receive, but not send, pause frames.
You use the flowcontrol interface configuration command to set the interfaces 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:
Note
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.
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
Specify the physical interface to be configured, and enter
interface configuration mode.
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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
10-18
OL-12189-01
Chapter 10
Configuring Interface Characteristics
Configuring Ethernet Interfaces
Switch(config-if)# flowcontrol receive on
Switch(config-if)# end
Configuring Auto-MDIX on an Interface
When automatic medium-dependent interface crossover (auto-MDIX) is enabled on an interface, the
interface automatically detects the required cable connection type (straight through or crossover) and
configures the connection appropriately. When connecting switches without the auto-MDIX feature, you
must use straight-through cables to connect to devices such as servers, workstations, or routers and
crossover cables to connect to other switches or repeaters. With auto-MDIX enabled, you can use either
type of cable to connect to other devices, and the interface automatically corrects for any incorrect
cabling. For more information about cabling requirements, see the hardware installation guide.
Auto-MDIX is enabled by default. When you enable auto-MDIX, you must also set the interface speed
and duplex to auto so that the feature operates correctly. Auto-MDIX is supported on all
10/100/1000-Mb/s interfaces.
Table 10-2 shows the link states that result from auto-MDIX settings and correct and incorrect cabling.
Table 10-2
Link Conditions and Auto-MDIX Settings
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 an interface:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode
Step 2
interface interface-id
Specify the physical interface to be configured, and enter interface
configuration mode.
Step 3
speed auto
Configure the interface to autonegotiate speed with the connected device.
Step 4
duplex auto
Configure the interface to autonegotiate duplex mode with the connected
device.
Step 5
mdix auto
Enable auto-MDIX on the interface.
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.
To disable auto-MDIX, use the no mdix auto interface configuration command.
This example shows how to enable auto-MDIX on a port:
Switch# configure terminal
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# speed auto
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
10-19
Chapter 10
Configuring Interface Characteristics
Configuring Layer 3 Interfaces
Switch(config-if)# duplex auto
Switch(config-if)# mdix auto
Switch(config-if)# end
Adding a Description for an Interface
You can add a description about an interface to help you remember its function. The description appears
in the output of these privileged EXEC commands: show configuration, show running-config, and
show interfaces.
Beginning in privileged EXEC mode, follow these steps to add a description for an interface:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
interface interface-id
Specify the interface for which you are adding a description, and enter
interface configuration mode.
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.
Use the no description interface configuration command to delete the description.
This example shows how to add a description on a port and how to verify the description:
Switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# description Connects to Marketing
Switch(config-if)# end
Switch# show interfaces gigabitethernet1/0/2 description
Interface Status
Protocol Description
Gi1/0/2
admin down
down
Connects to Marketing
Configuring Layer 3 Interfaces
The switch supports these types of Layer 3 interfaces:
SVIs: You should configure SVIs for any VLANs for which you want to route traffic. SVIs are
created when you enter a VLAN ID following the interface vlan global configuration command. To
delete an SVI, use the no interface vlan global configuration command. You cannot delete interface
VLAN 1.
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 12, Configuring
VLANs.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
10-20
OL-12189-01
Chapter 10
Configuring Interface Characteristics
Configuring Layer 3 Interfaces
Routed ports: Routed ports are physical ports configured to be in Layer 3 mode by using the no
switchport interface configuration command.
Layer 3 EtherChannel ports: EtherChannel interfaces made up of routed ports.
EtherChannel port interfaces are described in Chapter 37, Configuring EtherChannels and
Link-State Tracking.
A Layer 3 switch can have an IP address assigned to each routed port and SVI.
There is no defined limit to the number of SVIs and routed ports that can be configured in a switch or in
a switch stack. However, the interrelationship between the number of SVIs and routed ports and the
number of other features being configured might have an impact on CPU usage because of hardware
limitations. If the switch is using its maximum hardware resources, attempts to create a routed port or
SVI have these results:
If you try to create a new routed port, the switch generates a message that there are not enough
resources to convert the interface to a routed port, and the interface remains as a switchport.
If you try to create an extended-range VLAN, an error message is generated, and the extended-range
VLAN is rejected.
If the switch is notified by VLAN Trunking Protocol (VTP) of a new VLAN, 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.
If the switch attempts to boot up with a configuration that has more VLANs and routed ports than
hardware can support, the VLANs are created, but the routed ports are shut down, and the switch
sends a message that this was due to insufficient hardware resources.
All Layer 3 interfaces require an IP address to route traffic. This procedure shows how to configure an
interface as a Layer 3 interface and how to assign an IP address to an interface.
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. Furthermore, when you put an interface that is in Layer 2 mode into Layer 3
mode, the previous configuration information related to the affected interface might be lost, and the
interface is returned to its default configuration
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 {gigabitethernet interface-id} | {vlan vlan-id} Specify the interface to be configured as a Layer 3
| {port-channel port-channel-number}
interface, and enter interface configuration mode.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
10-21
Chapter 10
Configuring Interface Characteristics
Configuring the System MTU
Step 7
Command
Purpose
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
Enter configuration commands, one per line. End with CNTL/Z.
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
Configuring the System MTU
The default maximum transmission unit (MTU) size for frames received and sent on all interfaces on the
switch or switch stack is 1500 bytes. You can change the MTU size to support switched jumbo frames
on all Gigabit Ethernet and 10-Gigabit Ethernet interfaces and to support routed frames on all routed
ports.
The system jumbo MTU value applies to switched packets on the Gigabit Ethernet and 10-Gigabit
Ethernet ports of the switch or switch stack. Use the system mtu jumbo bytes global configuration
command to specify the system jumbo MTU value.
The system routing MTU value applies only to routed packets on all routed ports of the switch or
switch stack. Use the system mtu routing bytes global configuration command to specify the
system routing MTU value.
When configuring the system MTU values, follow these guidelines:
The switch does not support the MTU on a per-interface basis.
You can enter the system mtu bytes global configuration command on a switch, but the command
does not take effect on the switch.
The system mtu jumbo global configuration commands do not take effect when you enter the
system mtu routing command on a switch on which only Layer 2 ports are configured.
When you use the system mtu bytes or system mtu jumbo bytes command to change the system
MTU or system jumbo 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.
The system MTU jumbo 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 Cisco IOS 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
10-22
OL-12189-01
Chapter 10
Configuring Interface Characteristics
Configuring the System MTU
The upper limit of the system routing MTU value is based on the switch or switch stack configuration
and refers to either the currently applied system MTU or the system jumbo MTU value. For more
information about setting the MTU sizes, see the system mtu global configuration command in the
command reference for this release.
Beginning in privileged EXEC mode, follow these steps to change the MTU size for switched and routed
packets:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
system mtu jumbo bytes
(Optional) Change the MTU size for all Gigabit
Ethernet and 10-Gigabit Ethernet interfaces on the
switch or the switch stack. The range is from 1500 to
9198 bytes.
Step 3
system mtu routing bytes
(Optional) Change the system MTU for routed ports.
You can also set the maximum MTU to be advertised by
the routing protocols that support the configured MTU
size. The system routing MTU is the maximum MTU
for routed packets and is also the maximum MTU that
the switch advertises in routing updates for protocols
such as OSPF.
The range is from 1500 to the system jumbo MTU value
(in bytes).
Step 4
system mtu bytes
(Optional) Change the MTU size for all interfaces.
Note
The range is 1500 to 1998 bytes; the default is
1500 bytes.
Step 5
end
Return to privileged EXEC mode.
Step 6
copy running-config startup-config
Save your entries in the configuration file.
Step 7
reload
Reload the operating system.
Step 8
show system mtu
Verify your settings.
If you enter a value that is outside the allowed range for the specific type of interface, the value is not
accepted.
This example shows how to set the maximum packet size for a Gigabit Ethernet port to 7500 bytes:
Switch(config)# system jumbo mtu 7500
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 25000
^
% Invalid input detected at '^' marker.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
10-23
Chapter 10
Configuring Interface Characteristics
Monitoring and Maintaining the Interfaces
Monitoring and Maintaining the Interfaces
These sections contain interface monitoring and maintenance information:
Monitoring Interface Status, page 10-24
Clearing and Resetting Interfaces and Counters, page 10-25
Shutting Down and Restarting the Interface, page 10-25
Monitoring Interface Status
Commands entered at the privileged EXEC prompt display information about the interface, including
the versions of the software and the hardware, the configuration, and statistics about the interfaces.
Table 10-3 lists some of these interface monitoring commands. (You can display the full list of show
commands by using the show ? command at the privileged EXEC prompt.) These commands are fully
described in the Cisco IOS Interface Command Reference, Release 12.2.
Table 10-3
Show Commands for Interfaces
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 the error-disabled
state.
show interfaces [interface-id] switchport
Display administrative and operational status of switching
(nonrouting) ports. You can use this command to find out if a port is in
routing or in switching mode.
show interfaces [interface-id] description
Display the description configured on an interface or all interfaces and
the interface status.
show ip interface [interface-id]
Display the usability status of all interfaces configured for IP routing
or the specified interface.
show interface [interface-id] stats
Display the input and output packets by the switching path for the
interface.
show interfaces interface-id
(Optional) Display speed and duplex on the interface.
show interfaces transceiver properties
(Optional) Display temperature, voltage, or amount of current on the
interface.
show running-config interface [interface-id]
Display the running configuration in RAM for the interface.
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
phy
Display the operational state of the auto-MDIX feature on the
interface.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
10-24
OL-12189-01
Chapter 10
Configuring Interface Characteristics
Monitoring and Maintaining the Interfaces
Clearing and Resetting Interfaces and Counters
Table 10-4 lists the privileged EXEC mode clear commands that you can use to clear counters and reset
interfaces.
Table 10-4
Clear Commands for Interfaces
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 you specify optional arguments that 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.
Shutting Down and Restarting the Interface
Shutting down an interface disables all functions on the specified interface and marks the interface as
unavailable on all monitoring command displays. This information is communicated to other network
servers through all dynamic routing protocols. The interface is not mentioned in any routing updates.
Beginning in privileged EXEC mode, follow these steps to shut down an interface:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
interface {vlan vlan-id} | {gigabitethernet interface-id} |
{port-channel port-channel-number}
Select the interface to be configured.
Step 3
shutdown
Shut down an interface.
Step 4
end
Return to privileged EXEC mode.
Step 5
show running-config
Verify your entry.
Use the no shutdown interface configuration command to restart the interface.
To verify that an interface is disabled, enter the show interfaces privileged EXEC command. A disabled
interface is shown as administratively down in the display.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
10-25
Chapter 10
Configuring Interface Characteristics
Monitoring and Maintaining the Interfaces
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
10-26
OL-12189-01
CH A P T E R
11
Configuring Smartports Macros
This chapter describes how to configure and apply Smartports macros on the switch.
Note
For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
This chapter consists of these sections:
Understanding Smartports Macros, page 11-1
Configuring Smartports Macros, page 11-2
Displaying Smartports Macros, page 11-8
Understanding Smartports Macros
Smartports macros provide a convenient way to save and share common configurations. You can use
Smartports macros to enable features and settings based on the location of a switch in the network and
for mass configuration deployments across the network.
Each Smartports macro is a set of command-line interface (CLI) commands that you define. Smartports
macros do not contain new CLI commands; they are simply a group of existing CLI commands.
When you apply a Smartports macro on an interface, the CLI commands within the macro are configured
on the interface. When the macro is applied to an interface, the existing interface configurations are not
lost. The new commands are added to the interface and are saved in the running configuration file.
There are Cisco-default Smartports macros embedded in the switch software (see Table 11-1). You can
display these macros and the commands they contain by using the show parser macro user EXEC
command.
Table 11-1
Cisco-Default Smartports Macros
Macro Name1
Description
cisco-global
Use this global configuration macro to enable rapid PVST+, loop guard, and dynamic
port error recovery for link state failures.
cisco-desktop
Use this interface configuration macro for increased network security and reliability
when connecting a desktop device, such as a PC, to a switch port.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
11-1
Chapter 11
Configuring Smartports Macros
Configuring Smartports Macros
Table 11-1
Cisco-Default Smartports Macros (continued)
Macro Name1
Description
cisco-phone
Use this interface configuration macro when connecting a desktop device such as a
PC with a Cisco IP Phone to a switch port. This macro is an extension of the
cisco-desktop macro and provides the same security and resiliency features, but with
the addition of dedicated voice VLANs to ensure proper treatment of delay-sensitive
voice traffic.
cisco-switch
Use this interface configuration macro when connecting an access switch and a
distribution switch.
cisco-router
Use this interface configuration macro when connecting the switch and a WAN
router.
cisco-wireless
Use this interface configuration macro when connecting the switch and a wireless
access point.
1. Cisco-default Smartports macros vary depending on the software version running on your switch.
Cisco also provides a collection of pretested, Cisco-recommended baseline configuration templates for
Catalyst switches. The online reference guide templates provide the CLI commands that you can use to
create Smartports macros based on the usage of the port. You can use the configuration templates to
create Smartports macros to build and deploy Cisco-recommended network designs and configurations.
For more information about Cisco-recommended configuration templates, see this Smartports website:
http://www.cisco.com/go/smartports
Configuring Smartports Macros
You can create a new Smartports macro or use an existing macro as a template to create a new macro
that is specific to your application. After you create the macro, you can apply it globally to a switch or
to a switch interface or range of interfaces.
These sections contain this configuration information:
Default Smartports Macro Configuration, page 11-2
Smartports Macro Configuration Guidelines, page 11-3
Creating Smartports Macros, page 11-4
Applying Smartports Macros, page 11-5
Applying Cisco-Default Smartports Macros, page 11-6
Default Smartports Macro Configuration
There are no Smartports macros enabled.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
11-2
OL-12189-01
Chapter 11
Configuring Smartports Macros
Configuring Smartports Macros
Smartports Macro Configuration Guidelines
Follow these guidelines when configuring macros on your switch:
When creating a macro, do not use the exit or end commands or change the command mode by using
interface interface-id. This could cause commands that follow exit, end, or interface interface-id
to execute in a different command mode.
When creating a macro, all CLI commands should be in the same configuration mode.
When creating a macro that requires the assignment of unique values, use the parameter value
keywords to designate values specific to the interface. Keyword matching is case sensitive. All
matching occurrences of the keyword are replaced with the corresponding value. Any full match of
a keyword, even if it is part of a larger string, is considered a match and is replaced by the
corresponding value.
Macro names are case sensitive. For example, the commands macro name Sample-Macro and
macro name sample-macro will result in two separate macros.
Some macros might contain keywords that require a parameter value. You can use the macro global
apply macro-name ? global configuration command or the macro apply macro-name ? interface
configuration command to display a list of any required values in the macro. If you apply a macro
without entering the keyword values, the commands are invalid and are not applied.
When a macro is applied globally to a switch or to a switch interface, 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 11-1). You can
display these macros and the commands they contain by using the show parser macro user EXEC
command.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
11-3
Chapter 11
Configuring Smartports Macros
Configuring Smartports Macros
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.
Creating Smartports Macros
Beginning in privileged EXEC mode, follow these steps to create a Smartports 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
@
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
11-4
OL-12189-01
Chapter 11
Configuring Smartports Macros
Configuring Smartports Macros
Applying Smartports Macros
Beginning in privileged EXEC mode, follow these steps to apply a Smartports macro:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
macro global {apply | trace}
macro-name [parameter {value}]
[parameter {value}] [parameter
{value}]
Apply each individual command defined in the macro to the switch by
entering macro global apply macro-name. Specify macro global trace
macro-name to apply and debug a macro to find any syntax or
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
[parameter {value}] [parameter
{value}] [parameter {value}]
Apply each individual command defined in the macro to the interface by
entering macro apply macro-name. Specify macro trace macro-name
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 interface-id]
Verify that the macro is applied to the interface.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
11-5
Chapter 11
Configuring Smartports Macros
Configuring Smartports Macros
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 gigabitethernet0/2
Switch(config-if)# macro apply desktop-config
Switch(config-if)# end
Switch# show parser macro description
Interface
Macro Description
-------------------------------------------------------------Gi0/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
Applying Cisco-Default Smartports Macros
Beginning in privileged EXEC mode, follow these steps to apply a Smartports macro:
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}
macro-name [parameter {value}]
[parameter {value}] [parameter
{value}]
Append the Cisco-default macro with the required values by using the
parameter value keywords and apply the macro to the switch.
Keywords that begin with $ mean that a unique parameter value is
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
11-6
OL-12189-01
Chapter 11
Configuring Smartports Macros
Configuring Smartports Macros
Step 7
Command
Purpose
macro {apply | trace} macro-name
[parameter {value}] [parameter
{value}] [parameter {value}]
Append the Cisco-default macro with the required values by using the
parameter value keywords, and apply the macro to the interface.
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
interface-id
Verify that the macro is applied to an interface.
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
# Basic interface - Enable data VLAN only
# Recommended value for access vlan (AVID) should not be 1
switchport access vlan $AVID
switchport mode access
# Enable port security limiting port to a single
# MAC address -- that of desktop
switchport port-security
switchport port-security maximum 1
# Ensure port-security age is greater than one minute
# and use inactivity timer
switchport port-security violation restrict
switchport port-security aging time 2
switchport port-security aging type inactivity
# Configure port as an edge network port
spanning-tree portfast
spanning-tree bpduguard enable
-------------------------------------------------------------Switch#
Switch# configure terminal
Switch(config)# gigabitethernet1/0/4
Switch(config-if)# macro apply cisco-desktop $AVID 25
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
11-7
Chapter 11
Configuring Smartports Macros
Displaying Smartports Macros
Displaying Smartports Macros
To display the Smartports macros, use one or more of the privileged EXEC commands in Table 11-2.
Table 11-2
Commands for Displaying Smartports Macros
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
interface-id]
Displays the macro description for all interfaces or for a specified
interface.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
11-8
OL-12189-01
CH A P T E R
12
Configuring VLANs
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 switch. It includes information about VLAN
membership modes, VLAN configuration modes, VLAN trunks, and dynamic VLAN assignment from
a VLAN Membership Policy Server (VMPS). Unless otherwise noted, the term switch refers to a
standalone switch and to a switch stack.
Note
For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
The chapter consists of these sections:
Understanding VLANs, page 12-1
Configuring Normal-Range VLANs, page 12-4
Configuring Extended-Range VLANs, page 12-12
Displaying VLANs, page 12-16
Configuring VLAN Trunks, page 12-16
Configuring VMPS, page 12-28
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 12-1. In a switch stack, VLANs can be formed with
ports across the stack. Because a VLAN is considered a separate logical network, it contains its own
bridge Management Information Base (MIB) information and can support its own implementation of
spanning tree. See Chapter 17, 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 13,
Configuring VTP.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
12-1
Chapter 12
Configuring VLANs
Understanding VLANs
Figure 12-1 shows an example of VLANs segmented into logically defined networks.
Figure 12-1
VLANs as Logically Defined Networks
Engineering
VLAN
Marketing
VLAN
Accounting
VLAN
Cisco router
Enclosure 3
Gigabit
Ethernet
Enclosure 1
201766
Enclosure 2
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 10-5 and the Configuring Layer 3 Interfaces section on page 10-20.
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 8, Configuring SDM Templates,
or see the sdm prefer command in the command reference for this release.
Supported VLANs
The switch supports VLANs in VTP client, server, and transparent modes. VLANs are identified by 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
12-2
OL-12189-01
Chapter 12
Configuring VLANs
Understanding VLANs
Although the switch or switch stack 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 12-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.
VLAN Port Membership Modes
You configure a port to belong to a VLAN by assigning a membership mode that specifies the kind of
traffic the port carries and the number of VLANs to which it can belong. Table 12-1 lists the membership
modes and membership and VTP characteristics.
Table 12-1
Port Membership Modes and Characteristics
Membership Mode
VLAN Membership Characteristics
Static-access
A static-access port can belong to one VLAN and is
manually assigned to that VLAN.
Trunk (ISL or
IEEE 802.1Q)
A trunk port is a member of all VLANs by default,
including extended-range VLANs, but membership can
be limited by configuring the allowed-VLAN list. You
can also modify the pruning-eligible list to block flooded
traffic to VLANs on trunk ports that are included in the
list.
VTP Characteristics
VTP is not required. If you do not want VTP
to globally propagate information, set the
VTP mode to transparent. To participate in
For more information, see the Assigning Static-Access
VTP, there must be at least one trunk port on
Ports to a VLAN section on page 12-11.
the switch or the switch stack connected to
a trunk port of a second switch or switch
stack.
For information about configuring trunk ports, see the
Configuring an Ethernet Interface as a Trunk Port
section on page 12-20.
VTP is recommended but not required. VTP
maintains VLAN configuration consistency
by managing the addition, deletion, and
renaming of VLANs on a network-wide
basis. VTP exchanges VLAN configuration
messages with other switches over trunk
links.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
12-3
Chapter 12
Configuring VLANs
Configuring Normal-Range VLANs
Table 12-1
Port Membership Modes and Characteristics (continued)
Membership Mode
VLAN Membership Characteristics
VTP Characteristics
Dynamic access
A dynamic-access port can belong to one VLAN (VLAN
ID 1 to 4094) and is dynamically assigned by a VMPS.
The VMPS can be a Catalyst 5000 or Catalyst 6500
series switch, for example, but never a blade switch. The
switch is a VMPS client.
VTP is required.
You can have dynamic-access ports and trunk ports on
the same switch, but you must connect the
dynamic-access port to an end station or hub and not to
another switch.
Configure the VMPS and the client with the
same VTP domain name.
To participate in VTP, at least one trunk port
on the switch or a switch stack must be
connected to a trunk port of a second switch
or switch stack.
For configuration information, see the Configuring
Dynamic-Access Ports on VMPS Clients section on
page 12-31.
A voice VLAN port is an access port attached to a Cisco VTP is not required; it has no effect on a
IP Phone, configured to use one VLAN for voice traffic voice VLAN.
and another VLAN for data traffic from a device attached
to the phone.
Voice VLAN
For more information about voice VLAN ports, see
Chapter 14, Configuring Voice VLAN.
For more detailed definitions of access and trunk modes and their functions, see Table 12-4 on
page 12-18.
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 6-19.
Configuring Normal-Range VLANs
Normal-range VLANs are VLANs with VLAN IDs 1 to 1005. If the switch is in VTP server or
VTP transparent mode, you can add, modify or remove configurations for VLANs 2 to 1001 in the
VLAN database. (VLAN IDs 1 and 1002 to 1005 are automatically created and cannot be removed.)
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 12-12.
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 flash
memory. Thevlan.dat file is stored in flash memory on the stack master. Stack members have a vlan.dat
file that is consistent with the stack master.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
12-4
OL-12189-01
Chapter 12
Configuring VLANs
Configuring Normal-Range VLANs
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 13, 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:
Note
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
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.
These sections contain normal-range VLAN configuration information:
Token Ring VLANs, page 12-6
Normal-Range VLAN Configuration Guidelines, page 12-6
VLAN Configuration Mode Options, page 12-7
Saving VLAN Configuration, page 12-7
Default Ethernet VLAN Configuration, page 12-8
Creating or Modifying an Ethernet VLAN, page 12-9
Deleting a VLAN, page 12-10
Assigning Static-Access Ports to a VLAN, page 12-11
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
12-5
Chapter 12
Configuring VLANs
Configuring Normal-Range VLANs
Token Ring VLANs
Although the switch does not support Token Ring connections, a remote device such as a Catalyst 5000
series switch with Token Ring connections could be managed from one of the supported switches.
Switches running VTP Version 2 advertise information about these Token Ring VLANs:
Token Ring TrBRF VLANs
Token Ring TrCRF VLANs
For more information on configuring Token Ring VLANs, see the Catalyst 5000 Series Software
Configuration Guide.
Normal-Range VLAN Configuration Guidelines
Follow these guidelines when creating and modifying normal-range VLANs in your network:
The switch supports 1005 VLANs in VTP client, server, and transparent modes.
Normal-range VLANs are identified with a number between 1 and 1001. VLAN numbers 1002
through 1005 are reserved for Token Ring and FDDI VLANs.
VLAN configuration for VLANs 1 to 1005 are always saved in the VLAN database. If the VTP mode
is transparent, VTP and VLAN configuration are also saved in the switch running configuration file.
The switch also supports VLAN IDs 1006 through 4094 in VTP transparent mode (VTP disabled).
These are extended-range VLANs and configuration options are limited. Extended-range VLANs
are not saved in the VLAN database. See the Configuring Extended-Range VLANs section on
page 12-12.
Before you can create a VLAN, the switch must be in VTP server mode or VTP transparent mode.
If the switch is a VTP server, you must define a VTP domain or VTP will not function.
The switch does not support Token Ring or FDDI media. The switch does not forward FDDI,
FDDI-Net, TrCRF, or TrBRF traffic, but it does propagate the VLAN configuration through VTP.
The switch supports 128 spanning-tree instances. If a switch has more active VLANs than supported
spanning-tree instances, spanning tree can be enabled on 128 VLANs and is disabled on the
remaining VLANs. If you have already used all available spanning-tree instances on a switch,
adding another VLAN anywhere in the VTP domain creates a VLAN on that switch that is not
running spanning-tree. If you have the default allowed list on the trunk ports of that switch (which
is to allow all VLANs), 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 would not be broken, particularly if there
are several adjacent switches that all have run out of spanning-tree instances. You can prevent this
possibility by setting allowed lists on the trunk ports of switches that have used up their allocation
of spanning-tree instances.
If the number of VLANs on the switch exceeds the number of supported 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 spanning-tree instance. For more information about MSTP, see
Chapter 18, Configuring MSTP.
When a switch in a stack learns a new VLAN or deletes or modifies an existing VLAN (either
through VTP over network ports or through the CLI), the VLAN information is communicated to all
stack members.
When a switch joins a stack or when stacks merge, VTP information (the vlan.dat file) on the new
switches will be consistent with the stack master.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
12-6
OL-12189-01
Chapter 12
Configuring VLANs
Configuring Normal-Range VLANs
VLAN Configuration Mode Options
You can configure normal-range VLANs (with VLAN IDs 1 to 1005) by using these two configuration
modes:
VLAN Configuration in config-vlan Mode, page 12-7
You access config-vlan mode by entering the vlan vlan-id global configuration command.
VLAN Configuration in VLAN Database Configuration Mode, page 12-7
You access VLAN database configuration mode by entering the vlan database privileged EXEC
command.
VLAN Configuration in config-vlan Mode
To access config-vlan mode, enter the vlan global configuration command with a VLAN ID. Enter a new
VLAN ID to create a VLAN, or enter an existing VLAN ID to modify that VLAN. You can use the
default VLAN configuration (Table 12-2) or enter multiple commands to configure the VLAN. For more
information about commands available in this mode, see the vlan global configuration command
description in the command reference for this release. When you have finished the configuration, you
must exit config-vlan mode for the configuration to take effect. To display the VLAN configuration,
enter the show vlan privileged EXEC command.
You must use this config-vlan mode when creating extended-range VLANs (VLAN IDs greater than
1005). See the Configuring Extended-Range VLANs section on page 12-12.
VLAN Configuration in VLAN Database Configuration Mode
To access VLAN database configuration mode, enter the vlan database privileged EXEC command.
Then enter the vlan command with a new VLAN ID to create a VLAN, or enter an existing VLAN ID
to modify the VLAN. You can use the default VLAN configuration (Table 12-2) or enter multiple
commands to configure the VLAN. For more information about keywords available in this mode, see the
vlan VLAN database configuration command description in the command reference for this release.
When you have finished the configuration, you must enter apply or exit for the configuration to take
effect. When you enter the exit command, it applies all commands and updates the VLAN database. VTP
messages are sent to other switches in the VTP domain, and the privileged EXEC mode prompt appears.
Saving VLAN Configuration
The configurations of VLAN IDs 1 to 1005 are always saved in the VLAN database (vlan.dat file). If the
VTP mode is transparent, they are also saved in the switch running configuration file. You can enter the
copy running-config startup-config privileged EXEC command to save the configuration in the startup
configuration file. In a switch stack, the whole stack uses the same vlan.dat file and running
configuration. To display the VLAN configuration, enter the show vlan privileged EXEC command.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
12-7
Chapter 12
Configuring VLANs
Configuring Normal-Range VLANs
When you save VLAN and VTP information (including extended-range VLAN configuration
information) in the startup configuration file and reboot the switch, the switch configuration is selected
as follows:
Caution
If the VTP mode is transparent in the startup configuration, and the VLAN database and the VTP
domain name from the VLAN database matches that in the startup configuration file, the VLAN
database is ignored (cleared), and the VTP and VLAN configurations in the startup configuration
file are used. The VLAN database revision number remains unchanged in the VLAN database.
If the VTP mode or domain name in the startup configuration does not match the VLAN database,
the domain name and VTP mode and configuration for the first 1005 VLANs use the VLAN
database information.
If VTP mode is server, the domain name and VLAN configuration for the first 1005 VLANs use the
VLAN database information
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.
Default Ethernet VLAN Configuration
Table 12-2 shows the default configuration for Ethernet VLANs.
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.
Table 12-2
Ethernet VLAN Defaults and Ranges
Parameter
Default
Range
VLAN ID
1 to 4094.
Note
Extended-range VLANs (VLAN
IDs 1006 to 4094) are not saved in
the VLAN database.
VLAN name
No range
VLANxxxx, where xxxx
represents four numeric digits
(including leading zeros) equal
to the VLAN ID number
IEEE 802.10 SAID
100001 (100000 plus the
VLAN ID)
1 to 4294967294
MTU size
1500
1500 to 18190
Translational bridge 1
0 to 1005
Translational bridge 2
0 to 1005
VLAN state
active
active, suspend
Remote SPAN
disabled
enabled, disabled
Private VLANs
none configured
2 to 1001, 1006 to 4094.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
12-8
OL-12189-01
Chapter 12
Configuring VLANs
Configuring Normal-Range VLANs
Creating or Modifying an Ethernet VLAN
Each Ethernet VLAN in the VLAN database has a unique, 4-digit ID that can be a number from 1 to
1001. VLAN IDs 1002 to 1005 are reserved for Token Ring and FDDI VLANs. To create a normal-range
VLAN to be added to the VLAN database, assign a number and name to the VLAN.
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 12-12.
For the list of default parameters that are assigned when you add a VLAN, see the Configuring
Normal-Range VLANs section on page 12-4.
Beginning in privileged EXEC mode, follow these steps to use config-vlan mode 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 config-vlan mode. Enter a new VLAN ID
to create a VLAN, or enter an existing VLAN ID to modify that 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 12-12.
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 29,
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
config-vlan commands.
This example shows how to use config-vlan mode 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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
12-9
Chapter 12
Configuring VLANs
Configuring Normal-Range VLANs
You can also create or modify Ethernet VLANs by using the VLAN database configuration mode.
Note
VLAN database configuration mode does not support RSPAN VLAN configuration or extended-range
VLANs.
Beginning in privileged EXEC mode, follow these steps to use VLAN database configuration mode to
create or modify an Ethernet VLAN:
Command
Purpose
Step 1
vlan database
Enter VLAN database configuration mode.
Step 2
vlan vlan-id name vlan-name
Add an Ethernet VLAN by assigning a number to it. The range is 1 to
1001. You can create or modify a range of consecutive VLANs by
entering vlan first-vlan-id end last-vlan-id.
Note
When entering a VLAN ID in VLAN database configuration
mode, do not enter leading zeros.
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 3
vlan vlan-id mtu mtu-size
(Optional) To modify a VLAN, identify the VLAN and change a
characteristic, such as the MTU size.
Step 4
exit
Update the VLAN database, propagate it throughout the administrative
domain, and return to privileged EXEC mode.
Step 5
show vlan {name vlan-name | id vlan-id}
Verify your entries.
Step 6
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 vlan vlan-id name or no vlan vlan-id mtu
VLAN database configuration command.
This example shows how to use VLAN configuration mode to create Ethernet VLAN 20, name it test20,
and add it to the VLAN database:
Switch# vlan database
Switch(vlan)# vlan 20 name test20
Switch(vlan)# exit
APPLY completed.
Exiting....
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 or a switch stack.
You cannot delete the default VLANs for the different media types: Ethernet VLAN 1 and FDDI or
Token Ring VLANs 1002 to 1005.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
12-10
OL-12189-01
Chapter 12
Configuring VLANs
Configuring Normal-Range VLANs
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:
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.
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.
To delete a VLAN by using VLAN database configuration mode, use the vlan database privileged
EXEC command to enter VLAN database configuration mode and the no vlan vlan-id VLAN database
configuration command.
Assigning Static-Access Ports to a VLAN
You can assign a static-access port to a VLAN without having VTP globally propagate VLAN
configuration information by disabling VTP (VTP transparent mode).
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 12-9.)
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
12-11
Chapter 12
Configuring VLANs
Configuring Extended-Range VLANs
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 gigabitethernet2/0/1
Switch(config-if)# switchport mode access
Switch(config-if)# switchport access vlan 2
Switch(config-if)# end
Configuring Extended-Range VLANs
When the switch is in VTP transparent mode (VTP disabled), you can create extended-range VLANs (in
the range 1006 to 4094). Extended-range VLANs enable service providers to extend their infrastructure
to a greater number of customers. The extended-range VLAN IDs are allowed for any switchport
commands that allow VLAN IDs. You always use config-vlan mode (accessed by entering the vlan
vlan-id global configuration command) to configure extended-range VLANs. The extended range is not
supported in VLAN database configuration mode (accessed by entering the vlan database privileged
EXEC command).
Extended-range VLAN configurations are not stored in the VLAN database, but because VTP mode is
transparent, they are stored in the switch running configuration file, and you can save the configuration
in the startup configuration file by using the copy running-config startup-config privileged EXEC
command.
Note
Although the switch supports 4094 VLAN IDs, see the Supported VLANs section on page 12-2 for
the actual number of VLANs supported.
These sections contain extended-range VLAN configuration information:
Default VLAN Configuration, page 12-12
Extended-Range VLAN Configuration Guidelines, page 12-13
Creating an Extended-Range VLAN, page 12-14
Creating an Extended-Range VLAN with an Internal VLAN ID, page 12-15
Default VLAN Configuration
See Table 12-2 on page 12-8 for the default configuration for Ethernet VLANs. You can change only the
MTU size, private VLAN, and the remote SPAN configuration state on extended-range VLANs; all other
characteristics must remain at the default state.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
12-12
OL-12189-01
Chapter 12
Configuring VLANs
Configuring Extended-Range VLANs
Extended-Range VLAN Configuration Guidelines
Follow these guidelines when creating extended-range VLANs:
To add an extended-range VLAN, you must use the vlan vlan-id global configuration command and
access config-vlan mode. You cannot add extended-range VLANs in VLAN database configuration
mode (accessed by entering the vlan database privileged EXEC command).
VLAN IDs in the extended range are not saved in the VLAN database and are not recognized by
VTP.
You cannot include extended-range VLANs in the pruning eligible range.
The switch must be in VTP transparent mode when you create extended-range VLANs. If VTP mode
is server or client, an error message is generated, and the extended-range VLAN is rejected.
You can set the VTP mode to transparent in global configuration mode or in VLAN database
configuration mode. See the Disabling VTP (VTP Transparent Mode) section on page 13-12. You
should 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.
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 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 spanning-tree instance. For more information about MSTP, see
Chapter 18, 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 12-15.
Although the switch or switch stack 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.
In a switch stack, the whole stack uses the same running configuration and saved configuration, and
extended-range VLAN information is shared across the stack.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
12-13
Chapter 12
Configuring VLANs
Configuring Extended-Range VLANs
Creating an Extended-Range VLAN
You create an extended-range VLAN in global configuration mode by entering the vlan global
configuration command with a VLAN ID from 1006 to 4094. This command accesses the config-vlan
mode. The extended-range VLAN has the default Ethernet VLAN characteristics (see Table 12-2) and
the MTU size, private VLAN, and RSPAN configuration are the only parameters you can change. See
the description of the vlan global configuration command in the command reference for the default
settings of all parameters. If you enter an extended-range VLAN ID when the switch is not in VTP
transparent mode, an error message is generated when you exit from config-vlan mode, and the
extended-range VLAN is not created.
Extended-range VLANs are not saved in the VLAN database; they are saved in the switch running
configuration file. You can save the extended-range VLAN configuration in the switch startup
configuration file by using the copy running-config startup-config privileged EXEC command.
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 theCreating an Extended-Range VLAN with an Internal VLAN ID
section on page 12-15 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 config-vlan 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
config-vlan mode, only the mtu mtu-size, private-vlan, 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 29-17.
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 12-11.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
12-14
OL-12189-01
Chapter 12
Configuring VLANs
Configuring Extended-Range VLANs
This example shows how to create a new extended-range VLAN with all default characteristics, enter
config-vlan 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
Creating an Extended-Range VLAN with an Internal VLAN ID
If you enter an extended-range VLAN ID that is already assigned to an internal VLAN, an error message
is generated, and the extended-range VLAN is rejected. To manually free an internal VLAN ID, you
must temporarily shut down the routed port that is using the internal VLAN ID.
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
Specify the interface ID for the routed port that is using the VLAN ID,
and enter interface configuration mode.
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 config-vlan mode.
Step 8
exit
Exit from config-vlan mode, and return to global configuration mode.
Step 9
interface interface-id
Specify the interface ID for the routed port that you shut down in Step 4,
and enter interface configuration mode.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
12-15
Chapter 12
Configuring VLANs
Displaying VLANs
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. To
view normal-range VLANs in the VLAN database (1 to 1005), use the show VLAN database
configuration command (accessed by entering the vlan database privileged EXEC command).
Table 12-3 lists the commands for monitoring VLANs.
Table 12-3
VLAN Monitoring Commands
Command
Command Mode
Purpose
show
VLAN database
configuration
Display status of VLANs in the VLAN database.
show current [vlan-id]
VLAN database
configuration
Display status of all or the specified VLAN in the
VLAN database.
show interfaces [vlan
vlan-id]
Privileged EXEC
Display characteristics for all interfaces or for
the specified VLAN configured on the switch.
show vlan [id vlan-id]
Privileged EXEC
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.
Configuring VLAN Trunks
These sections contain this conceptual information:
Trunking Overview, page 12-16
Encapsulation Types, page 12-19
Default Layer 2 Ethernet Interface VLAN Configuration, page 12-20
Configuring an Ethernet Interface as a Trunk Port, page 12-20
Configuring Trunk Ports for Load Sharing, page 12-24
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.
Two trunking encapsulations are available on all Ethernet interfaces:
Inter-Switch Link (ISL)Cisco-proprietary trunking encapsulation.
IEEE 802.1Q industry-standard trunking encapsulation.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
12-16
OL-12189-01
Chapter 12
Configuring VLANs
Configuring VLAN Trunks
Figure 12-2 shows a network of switches that are connected by ISL trunks.
Figure 12-2
Switches in an ISL Trunking Environment
Catalyst 6500 series
switch
ISL
trunk
ISL
trunk
ISL
trunk
ISL
trunk
Blade
switch
Blade
switch
Blade
switch
VLAN1
VLAN3
VLAN2
VLAN2
VLAN1
VLAN3
119945
Blade
switch
Figure 12-3 shows a network of switches that are connected by IEEE 802.1Q trunks.
Figure 12-3
Switches in an IEEE 802.1Q Trunking Environment
Catalyst 6500 series
switch
IEEE
802.1Q
trunk
IEEE
802.1Q
trunk
IEEE
802.1Q
trunk
IEEE
802.1Q
trunk
Blade
switch
Blade
switch
VLAN1
Blade
switch
VLAN3
VLAN2
VLAN2
VLAN1
VLAN3
202005
Blade
switch
You can configure a trunk on a single Ethernet interface or on an EtherChannel bundle. For more
information about EtherChannel, see Chapter 37, Configuring EtherChannels and Link-State
Tracking.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
12-17
Chapter 12
Configuring VLANs
Configuring VLAN Trunks
Ethernet trunk interfaces support different trunking modes (see Table 12-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 isl or switchport trunk
encapsulation dot1q interface to select the encapsulation type on the trunk port.
You can also specify on DTP interfaces whether the trunk uses ISL or IEEE 802.1Q encapsulation or if
the encapsulation type is autonegotiated. The DTP supports autonegotiation of both ISL and
IEEE 802.1Q trunks.
Note
Table 12-4
DTP is not supported on private-VLAN ports or tunnel ports.
Layer 2 Interface Modes
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
desirable
Makes the interface actively attempt to convert the link to a trunk link. The interface
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 IEEE 802.1Q trunk port. The IEEE 802.1Q tunneling is used to maintain
customer VLAN integrity across a service provider network. See Chapter 16,
Configuring IEEE 802.1Q and Layer 2 Protocol Tunneling, for more information on
tunnel ports.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
12-18
OL-12189-01
Chapter 12
Configuring VLANs
Configuring VLAN Trunks
Encapsulation Types
Table 12-5 lists the Ethernet trunk encapsulation types and keywords.
Table 12-5
Ethernet Trunk Encapsulation Types
Encapsulation
Function
switchport trunk encapsulation isl
Specifies ISL encapsulation on the trunk link.
switchport trunk encapsulation dot1q
Specifies IEEE 802.1Q encapsulation on the trunk link.
switchport trunk encapsulation negotiate Specifies that the interface negotiate with the neighboring interface to become
an ISL (preferred) or IEEE 802.1Q trunk, depending on the configuration and
capabilities of the neighboring interface. This is the default for the switch.
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.
The trunking mode, the trunk encapsulation type, and the hardware capabilities of the two connected
interfaces decide whether a link becomes an ISL or IEEE 802.1Q trunk.
IEEE 802.1Q Configuration Considerations
The IEEE 802.1Q trunks impose these limitations on the trunking strategy for a network:
In a network of Cisco switches connected through IEEE 802.1Q trunks, the switches maintain one
spanning-tree instance 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 IEEE 802.1Q switch. However, spanning-tree information for each VLAN
is maintained by Cisco switches separated by a cloud of non-Cisco IEEE 802.1Q switches. The
non-Cisco IEEE 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 IEEE 802.1Q trunk or disable spanning
tree on every VLAN in the network. Make sure your network is loop-free before disabling spanning
tree.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
12-19
Chapter 12
Configuring VLANs
Configuring VLAN Trunks
Default Layer 2 Ethernet Interface VLAN Configuration
Table 12-6 shows the default Layer 2 Ethernet interface VLAN configuration.
Table 12-6
Default Layer 2 Ethernet Interface VLAN Configuration
Feature
Default Setting
Interface mode
switchport mode dynamic auto
Trunk encapsulation
switchport trunk encapsulation negotiate
Allowed VLAN range
VLANs 1 to 4094
VLAN range eligible for pruning
VLANs 2 to 1001
Default VLAN (for access ports)
VLAN 1
Native VLAN (for IEEE 802.1Q trunks) VLAN 1
Configuring an Ethernet Interface as a Trunk Port
Because trunk ports send and receive VTP advertisements, to use VTP 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 a second
switch. Otherwise, the switch cannot receive any VTP advertisements.
These sections contain this configuration information:
Note
Interaction with Other Features, page 12-20
Defining the Allowed VLANs on a Trunk, page 12-22
Changing the Pruning-Eligible List, page 12-23
Configuring the Native VLAN for Untagged Traffic, page 12-24
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, trunks negotiate encapsulation. If the
neighboring interface supports ISL and IEEE 802.1Q encapsulation and both interfaces are set to
negotiate the encapsulation type, the trunk uses ISL encapsulation.
Interaction with Other Features
Trunking interacts with other features in these ways:
A trunk port cannot be a secure port.
A trunk port cannot be a tunnel port.
Trunk ports can be grouped into EtherChannel port groups, but all trunks in the group must have the
same configuration. When a group is first created, all ports follow the parameters set for the first
port to be added to the group. If you change the configuration of one of these parameters, the switch
propagates the setting you entered to all ports in the group:
allowed-VLAN list.
STP port priority for each VLAN.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
12-20
OL-12189-01
Chapter 12
Configuring VLANs
Configuring VLAN Trunks
STP Port Fast setting.
trunk status: if one port in a port group ceases to be a trunk, all ports cease to be trunks.
We recommend that you configure no more than 24 trunk ports in PVST mode and no more than 40
trunk ports in MST mode.
If you try to enable IEEE 802.1x on a trunk port, an error message appears, and IEEE 802.1x is not
enabled. If you try to change the mode of an IEEE 802.1x-enabled port to trunk, the port mode is
not changed.
A port in dynamic mode can negotiate with its neighbor to become a trunk port. If you try to enable
IEEE 802.1x on a dynamic port, an error message appears, and IEEE 802.1x is not enabled. If you
try to change the mode of an IEEE 802.1x-enabled port to dynamic, the port mode is not changed.
Configuring a Trunk Port
Beginning in privileged EXEC mode, follow these steps to configure a port as a trunk port:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
interface interface-id
Specify the port to be configured for trunking, and enter interface
configuration mode.
Step 3
switchport trunk encapsulation {isl |
dot1q | negotiate}
Configure the port to support ISL or IEEE 802.1Q encapsulation or to
negotiate (the default) with the neighboring interface for encapsulation
type.
You must configure each end of the link with the same encapsulation type.
Step 4
switchport mode {dynamic {auto |
desirable} | trunk}
Configure the interface as a Layer 2 trunk (required only if the interface
is a Layer 2 access port or tunnel port or to specify the trunking mode).
dynamic autoSet the interface to a trunk link if the neighboring
interface is set to trunk or desirable mode. This is the default.
dynamic desirableSet the interface to a trunk link if the
neighboring interface is set to trunk, desirable, or auto mode.
trunkSet 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 IEEE 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
12-21
Chapter 12
Configuring VLANs
Configuring VLAN Trunks
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 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
Defining the Allowed VLANs on a Trunk
By default, a trunk port sends traffic to and receives traffic from all VLANs. All VLAN IDs, 1 to 4094,
are allowed on each trunk. However, you can remove VLANs from the allowed list, preventing traffic
from those VLANs from passing over the trunk. To restrict the traffic a trunk carries, use the switchport
trunk allowed vlan remove vlan-list interface configuration command to remove specific VLANs from
the allowed list.
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), DTP, and 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 a trunk:
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
switchport mode trunk
Configure the interface as a VLAN trunk port.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
12-22
OL-12189-01
Chapter 12
Configuring VLANs
Configuring VLAN Trunks
Step 4
Command
Purpose
switchport trunk allowed vlan {add |
all | except | remove} vlan-list
(Optional) Configure the list of VLANs allowed on the trunk.
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
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
Return to privileged EXEC mode.
(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
Changing the Pruning-Eligible List
The pruning-eligible list applies only to trunk ports. Each trunk port has its own eligibility list. VTP
pruning must be enabled for this procedure to take effect. The Enabling VTP Pruning section on
page 13-14 describes how to enable VTP pruning.
Beginning in privileged EXEC mode, follow these steps to remove VLANs from the pruning-eligible list
on a trunk port:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
interface interface-id
Select the trunk port for which VLANs should be pruned, and enter
interface configuration mode.
Step 3
switchport trunk pruning vlan {add |
except | none | remove} vlan-list
[,vlan[,vlan[,,,]]
Configure the list of VLANs allowed to be pruned from the trunk. (See
the VTP Pruning section on page 13-4).
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 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
12-23
Chapter 12
Configuring VLANs
Configuring VLAN Trunks
Command
Purpose
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.
Configuring the Native VLAN for Untagged Traffic
A trunk port configured with IEEE 802.1Q tagging can receive both tagged and untagged traffic. By
default, the switch forwards untagged traffic in the native VLAN configured for the port. The native
VLAN is VLAN 1 by default.
Note
The native VLAN can be assigned any VLAN ID.
For information about IEEE 802.1Q configuration issues, see the IEEE 802.1Q Configuration
Considerations section on page 12-19.
Beginning in privileged EXEC mode, follow these steps to configure the native VLAN on an
IEEE 802.1Q trunk:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
interface interface-id
Define the interface that is configured as the IEEE 802.1Q trunk, and
enter interface configuration mode.
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.
Configuring Trunk Ports for Load Sharing
Load sharing divides the bandwidth supplied by parallel trunks connecting switches. To avoid loops,
STP normally blocks all but one parallel link between switches. Using load sharing, you divide the traffic
between the links according to which VLAN the traffic belongs.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
12-24
OL-12189-01
Chapter 12
Configuring VLANs
Configuring VLAN Trunks
You configure load sharing on trunk ports by using STP port priorities or STP path costs. For load
sharing using STP port priorities, both load-sharing links must be connected to the same switch. For load
sharing using STP path costs, each load-sharing link can be connected to the same switch or to two
different switches. For more information about STP, see Chapter 17, Configuring STP.
Load Sharing Using STP Port Priorities
When two ports on the same switch form a loop, the switch uses the STP port priority to decide which
port is enabled and which port is in a blocking state. You can set the priorities on a parallel trunk port so
that the port carries all the traffic for a given VLAN. The trunk port with the higher priority (lower
values) for a VLAN is forwarding traffic for that VLAN. The trunk port with the lower priority (higher
values) for the same VLAN remains in a blocking state for that VLAN. One trunk port sends or receives
all traffic for the VLAN.
Figure 12-4 shows two trunks connecting supported switches. In this example, the switches are
configured as follows:
VLANs 8 through 10 are assigned a port priority of 16 on Trunk 1.
VLANs 3 through 6 retain the default port priority of 128 on Trunk 1.
VLANs 3 through 6 are assigned a port priority of 16 on Trunk 2.
VLANs 8 through 10 retain the default port priority of 128 on Trunk 2.
In this way, Trunk 1 carries traffic for VLANs 8 through 10, and Trunk 2 carries traffic for VLANs 3
through 6. If the active trunk fails, the trunk with the lower priority takes over and carries the traffic for
all of the VLANs. No duplication of traffic occurs over any trunk port.
Figure 12-4
Load Sharing by Using STP Port Priorities
Switch A
Switch B
Note
93370
Trunk 2
VLANs 3 6 (priority 16)
VLANs 8 10 (priority 128)
Trunk 1
VLANs 8 10 (priority 16)
VLANs 3 6 (priority 128)
If your switch is a member of a switch stack, you must use the spanning-tree [vlan vlan-id] cost cost
interface configuration command instead of the spanning-tree [vlan vlan-id] port-priority priority
interface configuration command to select an interface to put in the forwarding state. Assign lower cost
values to interfaces that you want selected first and higher cost values that you want selected last. For
more information, see the Load Sharing Using STP Path Cost section on page 12-27.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
12-25
Chapter 12
Configuring VLANs
Configuring VLAN Trunks
Beginning in privileged EXEC mode, follow these steps to configure the network shown in Figure 12-4.
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 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
Define the interface to be configured as a trunk, and enter interface
configuration mode.
Step 9
switchport trunk encapsulation {isl |
dot1q | negotiate}
Configure the port to support ISL or IEEE 802.1Q encapsulation or to
negotiate with the neighboring interface. You must configure each end
of the link with the same encapsulation type.
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
switchport
Verify the VLAN configuration.
Step 13
Repeat Steps 7 through 11 on Switch A for a second port in the switch
or switch stack.
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
Define the interface to set the STP port priority, and enter interface
configuration mode.
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
Define the interface to set the STP port priority, and enter interface
configuration mode.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
12-26
OL-12189-01
Chapter 12
Configuring VLANs
Configuring VLAN Trunks
Load Sharing Using STP Path Cost
You can configure parallel trunks to share VLAN traffic by setting different path costs on a trunk and
associating the path costs with different sets of VLANs, blocking different ports for different VLANs.
The VLANs keep the traffic separate and maintain redundancy in the event of a lost link.
In Figure 12-5, Trunk ports 1 and 2 are configured as 100BASE-T ports. These VLAN path costs are
assigned:
VLANs 2 through 4 are assigned a path cost of 30 on Trunk port 1.
VLANs 8 through 10 retain the default 100BASE-T path cost on Trunk port 1 of 19.
VLANs 8 through 10 are assigned a path cost of 30 on Trunk port 2.
VLANs 2 through 4 retain the default 100BASE-T path cost on Trunk port 2 of 19.
Figure 12-5
Load-Sharing Trunks with Traffic Distributed by Path Cost
Switch A
Trunk port 2
VLANs 8 10 (path cost 30)
VLANs 2 4 (path cost 19)
90573
Trunk port 1
VLANs 2 4 (path cost 30)
VLANs 8 10 (path cost 19)
Switch B
Beginning in privileged EXEC mode, follow these steps to configure the network shown in Figure 12-5:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode on Switch A.
Step 2
interface gigabitethernet1/0/1
Define the interface to be configured as a trunk, and enter interface
configuration mode.
Step 3
switchport trunk encapsulation
{isl | dot1q | negotiate}
Configure the port to support ISL or IEEE 802.1Q encapsulation. You
must configure each end of the link with the same encapsulation type.
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 5 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 are
configured as trunk ports.
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
Define the interface on which to set the STP cost, and enter interface
configuration mode.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
12-27
Chapter 12
Configuring VLANs
Configuring VMPS
Command
Purpose
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 13 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 give 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.
These sections contain this information:
Understanding VMPS section on page 12-28
Default VMPS Client Configuration section on page 12-30
VMPS Configuration Guidelines section on page 12-30
Configuring the VMPS Client section on page 12-30
Monitoring the VMPS section on page 12-33
Troubleshooting Dynamic-Access Port VLAN Membership section on page 12-33
VMPS Configuration Example section on page 12-34
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
12-28
OL-12189-01
Chapter 12
Configuring VLANs
Configuring VMPS
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 Network Assistant, the
CLI, or SNMP.
Dynamic-Access Port VLAN Membership
A dynamic-access port can belong to only one VLAN with an ID from 1 to 4094. When the link comes
up, the switch does not forward traffic to or from this port until the VMPS provides the VLAN
assignment. The VMPS receives the source MAC address from the first packet of a new host connected
to the dynamic-access port and attempts to match the MAC address to a VLAN in the VMPS database.
If there is a match, the VMPS sends the VLAN number for that port. If the client switch was not
previously configured, it uses the domain name from the first VTP packet it receives on its trunk port
from the VMPS. If the client switch was previously configured, it includes its domain name in the query
packet to the VMPS to obtain its VLAN number. The VMPS verifies that the domain name in the packet
matches its own domain name before accepting the request and responds to the client with the assigned
VLAN number for the client. If there is no match, the VMPS either denies the request or shuts down the
port (depending on the VMPS secure mode setting).
Multiple hosts (MAC addresses) can be active on a dynamic-access port if they are all in the same
VLAN; however, the VMPS shuts down a dynamic-access port if more than 20 hosts are active on the
port.
If the link goes down on a dynamic-access port, the port returns to an isolated state and does not belong
to a VLAN. Any hosts that come online through the port are checked again through the VQP with the
VMPS before the port is assigned to a VLAN.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
12-29
Chapter 12
Configuring VLANs
Configuring VMPS
Default VMPS Client Configuration
Table 12-7 shows the default VMPS and dynamic-access port configuration on client switches.
Table 12-7
Default VMPS Client and Dynamic-Access Port Configuration
Feature
Default Setting
VMPS domain server
None
VMPS reconfirm interval
60 minutes
VMPS server retry count
Dynamic-access ports
None configured
VMPS Configuration Guidelines
These guidelines and restrictions apply to dynamic-access port VLAN membership:
You should configure the VMPS before you configure ports as dynamic-access ports.
When you configure a port as a dynamic-access port, the spanning-tree Port Fast feature is
automatically enabled for that port. The Port Fast mode accelerates the process of bringing the port
into the forwarding state.
IEEE 802.1x ports cannot be configured as dynamic-access ports. If you try to enable IEEE 802.1x
on a dynamic-access (VQP) port, an error message appears, and IEEE 802.1x is not enabled. If you
try to change an IEEE 802.1x-enabled port to dynamic VLAN assignment, an error message appears,
and the VLAN configuration is not changed.
Trunk ports cannot be dynamic-access ports, but you can enter the switchport access vlan dynamic
interface configuration command for a trunk port. In this case, the switch retains the setting and
applies it if the port is later configured as an access port.
You must turn off trunking on the port before the dynamic-access setting takes effect.
Dynamic-access ports cannot be monitor ports.
Secure ports cannot be dynamic-access ports. You must disable port security on a port before it
becomes dynamic.
Private VLAN ports cannot be dynamic-access ports.
Dynamic-access ports cannot be members of an EtherChannel group.
Port channels cannot be configured as dynamic-access ports.
A dynamic-access port can participate in fallback bridging on a Catalyst Switch Module 3110.
The VTP management domain of the VMPS client and the VMPS server must be the same.
The VLAN configured on the VMPS server should not be a voice VLAN.
Configuring the VMPS Client
You configure dynamic VLANs by using the VMPS (server). The switch can be a VMPS client; it cannot
be a VMPS server.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
12-30
OL-12189-01
Chapter 12
Configuring VLANs
Configuring VMPS
Entering the IP Address of the VMPS
You must first enter the IP address of the server to configure the switch as a client.
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.
Configuring Dynamic-Access Ports on VMPS Clients
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
Specify the switch port that is connected to the end station, and enter
interface configuration mode.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
12-31
Chapter 12
Configuring VLANs
Configuring VMPS
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.
Reconfirming VLAN Memberships
Beginning in privileged EXEC mode, follow these steps to confirm the dynamic-access port VLAN
membership assignments that the switch has received from the VMPS:
Command
Purpose
Step 1
vmps reconfirm
Reconfirm dynamic-access port VLAN membership.
Step 2
show vmps
Verify the dynamic VLAN reconfirmation status.
Changing the Reconfirmation Interval
VMPS clients periodically reconfirm the VLAN membership information received from the VMPS.You
can set the number of minutes after which reconfirmation occurs.
Beginning in privileged EXEC mode, follow these steps to change the reconfirmation interval:
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 1 to 120. The default is 60 minutes.
Step 3
end
Return to privileged EXEC mode.
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.
Changing the Retry Count
Beginning in privileged EXEC mode, follow these steps to change the number of times that the switch
attempts to contact the VMPS before querying the next server:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
vmps retry count
Change the retry count. The retry range is 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
12-32
OL-12189-01
Chapter 12
Configuring VLANs
Configuring VMPS
To return the switch to its default setting, use the no vmps retry global configuration command.
Monitoring the VMPS
You can display information about the VMPS by using the show vmps privileged EXEC command. The
switch displays this information about the VMPS:
VMPS VQP Versionthe version of VQP used to communicate with the VMPS. The switch queries
the VMPS that is using VQP Version 1.
Reconfirm Intervalthe number of minutes the switch waits before reconfirming the
VLAN-to-MAC-address assignments.
Server Retry Countthe number of times VQP resends a query to the VMPS. If no response is
received after this many tries, the switch starts to query the secondary VMPS.
VMPS domain serverthe IP address of the configured VLAN membership policy servers. The
switch sends queries to the one marked current. The one marked primary is the primary server.
VMPS Actionthe result of the most recent reconfirmation attempt. A reconfirmation attempt can
occur automatically when the reconfirmation interval expires, or you can force it by entering the
vmps reconfirm privileged EXEC command or its Network Assistant or SNMP equivalent.
This is an example of output for the show vmps privileged EXEC command:
Switch# show vmps
VQP Client Status:
-------------------VMPS VQP Version:
1
Reconfirm Interval: 60 min
Server Retry Count: 3
VMPS domain server: 172.20.128.86 (primary, current)
172.20.128.87
Reconfirmation status
--------------------VMPS Action:
other
Troubleshooting Dynamic-Access Port VLAN Membership
The VMPS shuts down a dynamic-access port under these conditions:
The VMPS is in secure mode, and it does not allow the host to connect to the port. The VMPS shuts
down the port to prevent the host from connecting to the network.
More than 20 active hosts reside on a dynamic-access port.
To re-enable a disabled dynamic-access port, enter the shutdown interface configuration command
followed by the no shutdown interface configuration command.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
12-33
Chapter 12
Configuring VLANs
Configuring VMPS
VMPS Configuration Example
Figure 12-6 shows a network with a VMPS server switch and VMPS client switches with
dynamic-access ports. In this example, these assumptions apply:
The VMPS server and the VMPS client are separate switches.
The Catalyst 6500 series Switch A is the primary VMPS server.
The Catalyst 6500 series Switch C and Switch J are secondary VMPS servers.
End stations are connected to the clients, Switch B and Switch I.
The database configuration file is stored on the TFTP server with the IP address 172.20.22.7.
Figure 12-6
Dynamic Port VLAN Membership Configuration
TFTP server
Catalyst 6500 series switch A
Primary VMPS
Server 1
Router
172.20.26.150
172.20.22.7
Client switch B
Server 1
Dynamic-access port
172.20.26.151
Trunk port
Switch C
172.20.26.152
Switch D
172.20.26.153
Switch E
172.20.26.154
Switch F
172.20.26.155
Switch G
172.20.26.156
Switch H
172.20.26.157
Dynamic-access port
Server 2
Ethernet segment
(Trunk link)
Catalyst 6500 series
Secondary VMPS
Server 2
Client switch I
172.20.26.158
172.20.26.159
Catalyst 6500 series
Secondary VMPS
Server 3
201767
Trunk port
Switch J
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
12-34
OL-12189-01
CH A P T E R
13
Configuring VTP
This chapter describes how to use the VLAN Trunking Protocol (VTP) and the VLAN database for
managing VLANs with the switch. Unless otherwise noted, the term switch refers to a standalone switch
and to a switch stack.
Note
For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
The chapter consists of these sections:
Understanding VTP, page 13-1
Configuring VTP, page 13-6
Monitoring VTP, page 13-16
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.
VTP functionality is supported across the stack, and all switches in the stack maintain the same VLAN
and VTP configuration inherited from the stack master. When a switch learns of a new VLAN through
VTP messages or when a new VLAN is configured by the user, the new VLAN information is
communicated to all switches in the stack.
When a switch joins the stack or when stacks merge, the new switches get VTP information from the
stack master.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
13-1
Chapter 13
Configuring VTP
Understanding VTP
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.
These sections contain this conceptual information:
The VTP Domain, page 13-2
VTP Modes, page 13-3
VTP Advertisements, page 13-3
VTP Version 2, page 13-4
VTP Pruning, page 13-4
VTP and Switch Stacks, page 13-6
The VTP Domain
A VTP domain (also called a VLAN management domain) consists of one switch or several
interconnected switches or switch stacks under the same administrative responsibility sharing the same
VTP domain name. A switch can be in only one VTP domain. You make global VLAN configuration
changes for the domain.
By default, the switch is in the VTP no-management-domain state until it receives an advertisement for
a domain over a trunk link (a link that carries the traffic of multiple VLANs) or until you configure a
domain name. Until the management domain name is specified or learned, you cannot create or modify
VLANs on a VTP server, and VLAN information is not propagated over the network.
If the switch receives a VTP advertisement over a trunk link, it inherits the management domain name
and the VTP configuration revision number. The switch then ignores advertisements with a different
domain name or an earlier configuration revision number.
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 13-14 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
13-2
OL-12189-01
Chapter 13
Configuring VTP
Understanding VTP
For domain name and password configuration guidelines, see the VTP Configuration Guidelines
section on page 13-8.
VTP Modes
You can configure a supported switch or switch stack to be in one of the VTP modes listed in Table 13-1.
Table 13-1
VTP Modes
VTP Mode
Description
VTP server
In VTP server mode, you can create, modify, and delete VLANs, and specify other configuration
parameters (such as the VTP version) for the entire VTP domain. VTP servers advertise their VLAN
configurations to other switches in the same VTP domain and synchronize their VLAN configurations with
other switches based on advertisements received over trunk links.
In VTP server mode, VLAN configurations are saved in NVRAM. VTP server is the default mode.
VTP client
A VTP client behaves like a VTP server and transmits and receives VTP updates on its trunks, but you
cannot create, change, or delete VLANs on a VTP client. VLANs are configured on another switch in the
domain that is in server mode.
In VTP client mode, VLAN configurations are not saved in NVRAM.
VTP transparent VTP transparent switches do not participate in VTP. A VTP transparent switch does not advertise its VLAN
configuration and does not synchronize its VLAN configuration based on received advertisements.
However, in VTP Version 2, transparent switches do forward VTP advertisements that they receive from
other switches through their trunk interfaces. You can create, modify, and delete VLANs on a switch in
VTP transparent mode.
The switch must be in VTP transparent mode when you create extended-range VLANs. See the
Configuring Extended-Range VLANs section on page 12-12.
The switch must be in VTP transparent mode when you create private VLANs. See Chapter 15,
Configuring Private VLANs. When private VLANs are configured, do not change the VTP mode from
transparent to client or server mode.
When the switch is in VTP transparent mode, the VTP and VLAN configurations are saved in NVRAM,
but they are not advertised to other switches. In this mode, VTP mode and domain name are saved in the
switch running configuration, and you can save this information in the switch startup configuration file by
using the copy running-config startup-config privileged EXEC command. On stacking-capable switches,
the running configuration and the saved configuration are the same for all switches in a stack.
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 or switch stack 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 12-16.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
13-3
Chapter 13
Configuring VTP
Understanding VTP
VTP advertisements distribute this global domain information:
VTP domain name
VTP configuration revision number
Update identity and update timestamp
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 IEEE 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 that are not supported in Version 1:
Token Ring supportVTP 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 12-4.
Unrecognized Type-Length-Value (TLV) supportA VTP server or client propagates configuration
changes to its other trunks, even for TLVs it is not able to parse. The unrecognized TLV is saved in
NVRAM when the switch is operating in VTP server mode.
Version-Dependent Transparent ModeIn 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. Because VTP Version 2 supports only one domain, it forwards VTP messages in
transparent mode without inspecting the version and domain name.
Consistency ChecksIn VTP Version 2, VLAN consistency checks (such as VLAN names and
values) are performed only when you enter new information through the CLI or SNMP. Consistency
checks are not performed when new information is obtained from a VTP message or when
information is read from NVRAM. If the 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
13-4
OL-12189-01
Chapter 13
Configuring VTP
Understanding VTP
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 13-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.
Figure 13-1
Flooding Traffic without VTP Pruning
Switch D
Port 2
Switch E
Switch B
Red
VLAN
Switch F
Switch C
89240
Port 1
Switch A
Figure 13-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).
Figure 13-2
Optimized Flooded Traffic with VTP Pruning
Switch D
Port 2
Flooded traffic
is pruned.
Port
4
Switch B
Red
VLAN
Switch E
Flooded traffic
is pruned.
Port
5
Switch F
Switch C
Switch A
89241
Port 1
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
13-5
Chapter 13
Configuring VTP
Configuring VTP
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 13-14. 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 12-23). 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.
VTP and Switch Stacks
VTP configuration is the same in all members of a switch stack. When the switch stack is in VTP server
or client mode, all switches in the stack carry the same VTP configuration. When VTP mode is
transparent, the stack is not taking part in VTP.
When a switch joins the stack, it inherits the VTP and VLAN properties of the stack master.
All VTP updates are carried across the stack.
When VTP mode is changed in a switch in the stack, the other switches in the stack also change VTP
mode, and the switch VLAN database remains consistent.
For more information about the switch stack, see Chapter 5, Managing Switch Stacks.
Configuring VTP
These sections contain this configuration information:
Default VTP Configuration, page 13-7
VTP Configuration Options, page 13-7
VTP Configuration Guidelines, page 13-8
Configuring a VTP Server, page 13-9
Configuring a VTP Client, page 13-11
Disabling VTP (VTP Transparent Mode), page 13-12
Enabling VTP Version 2, page 13-13
Enabling VTP Pruning, page 13-14
Adding a VTP Client Switch to a VTP Domain, page 13-14
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
13-6
OL-12189-01
Chapter 13
Configuring VTP
Configuring VTP
Default VTP Configuration
Table 13-2 shows the default VTP configuration.
Table 13-2
Default VTP Configuration
Feature
Default Setting
VTP domain name
Null.
VTP mode
Server.
VTP version
Version 1 (Version 2 is disabled).
VTP password
None.
VTP pruning
Disabled.
VTP Configuration Options
You can configure VTP by using these configuration modes.
VTP Configuration in Global Configuration Mode, page 13-7
VTP Configuration in VLAN Database Configuration Mode, page 13-8
You access VLAN database configuration mode by entering the vlan database privileged EXEC
command.
For detailed information about vtp commands, see the command reference for this release.
VTP Configuration in Global Configuration Mode
You can use the vtp global configuration command to set the VTP password, the version, the VTP file
name, the interface providing updated VTP information, the domain name, and the mode, and to disable
or enable pruning. For more information about available keywords, see the command descriptions in the
command reference for this release. The VTP information is saved in the VTP VLAN database. When
VTP mode is transparent, the VTP domain name and mode are also saved in the switch running
configuration file, and you can save it in the switch startup configuration file by entering the copy
running-config startup-config privileged EXEC command. You must use this command if you want to
save VTP mode as transparent, even if the switch resets.
When you save VTP information in the switch startup configuration file and reboot the switch, the switch
configuration is selected as follows:
If the VTP mode is transparent in the startup configuration and the VLAN database and the VTP
domain name from the VLAN database matches that in the startup configuration file, the VLAN
database is ignored (cleared), and the VTP and VLAN configurations in the startup configuration
file are used. The VLAN database revision number remains unchanged in the VLAN database.
If the VTP mode or domain name in the startup configuration do not match the VLAN database, the
domain name and VTP mode and configuration for the first 1005 VLANs use the VLAN database
information.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
13-7
Chapter 13
Configuring VTP
Configuring VTP
VTP Configuration in VLAN Database Configuration Mode
You can configure all VTP parameters in VLAN database configuration mode, which you access by
entering the vlan database privileged EXEC command. For more information about available keywords,
see the vtp VLAN database configuration command description in the command reference for this
release. When you enter the exit command in VLAN database configuration mode, it applies all the
commands that you entered and updates the VLAN database. VTP messages are sent to other switches
in the VTP domain, and the privileged EXEC mode prompt appears.
If VTP mode is transparent, the domain name and the mode (transparent) are saved in the switch running
configuration, and you can save this information in the switch startup configuration file by entering the
copy running-config startup-config privileged EXEC command.
VTP Configuration Guidelines
These sections describe guidelines you should follow when implementing VTP in your network.
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
Caution
If NVRAM and DRAM storage is sufficient, all switches in a VTP domain should be in VTP server
mode.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
13-8
OL-12189-01
Chapter 13
Configuring VTP
Configuring VTP
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 that have 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 on the switch or switch stack 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 12-16.
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.
Configuring a VTP Server
When a switch is in VTP server mode, you can change the VLAN configuration and have it propagated
throughout the network.
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 mode server
Configure the switch for VTP server mode (the default).
Step 3
vtp domain domain-name
Configure the VTP administrative-domain name. The name can be 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
13-9
Chapter 13
Configuring VTP
Configuring VTP
Step 4
Command
Purpose
vtp password password
(Optional) Set the password for the VTP domain. The password can be 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# configure terminal
Switch(config)# vtp mode server
Switch(config)# vtp domain eng_group
Switch(config)# vtp password mypassword
Switch(config)# end
You can also use VLAN database configuration mode to configure VTP parameters.
Beginning in privileged EXEC mode, follow these steps to use VLAN database configuration mode to
configure the switch as a VTP server:
Command
Purpose
Step 1
vlan database
Enter VLAN database configuration mode.
Step 2
vtp server
Configure the switch for VTP server mode (the default).
Step 3
vtp domain domain-name
Configure a VTP administrative-domain name. The name can be 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 4
vtp password password
(Optional) Set a password for the VTP domain. The password can be 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
exit
Update the VLAN database, propagate it throughout the administrative
domain, and 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 VLAN database configuration
command.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
13-10
OL-12189-01
Chapter 13
Configuring VTP
Configuring VTP
This example shows how to use VLAN database configuration mode to configure the switch as a VTP
server with the domain name eng_group and the password mypassword:
Switch# vlan database
Switch(vlan)# vtp server
Switch(vlan)# vtp domain eng_group
Switch(vlan)# vtp password mypassword
Switch(vlan)# exit
APPLY completed.
Exiting....
Switch#
Configuring a VTP Client
When a switch is in VTP client mode, you cannot change its VLAN configuration. The client switch
receives VTP updates from a VTP server in the VTP domain and then modifies its configuration
accordingly.
Follow these guidelines:
Caution
If extended-range VLANs are configured on the switch or switch stack, you cannot change VTP
mode to client. You receive an error message, and the configuration is not allowed.
If you configure the switch for VTP client mode, the switch does not create the VLAN database file
(vlan.dat). If the switch is then powered off, it resets the VTP configuration to the default. To keep
the VTP configuration with VTP client mode after the switch restarts, you must first configure the
VTP domain name before the VTP mode.
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 mode client
Configure the switch for VTP client mode. The default setting is VTP
server.
Step 3
vtp domain domain-name
(Optional) Enter the VTP administrative-domain name. The name can be 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 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
13-11
Chapter 13
Configuring VTP
Configuring VTP
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
You can also configure a VTP client by using the vlan database privileged EXEC command to enter
VLAN database configuration mode and entering the vtp client command, similar to the second
procedure under Configuring a VTP Server section on page 13-9. Use the no vtp client VLAN
database configuration command to return the switch to VTP server mode or the no vtp password
VLAN database configuration command to return the switch to a no-password state. When you configure
a domain name, it cannot be removed; you can only reassign a switch to a different domain.
Disabling VTP (VTP Transparent Mode)
When you configure the switch for VTP transparent mode, VTP is disabled on the switch. The switch
does not send VTP updates and does not act on VTP updates received from other switches. However, a
VTP transparent switch running VTP Version 2 does forward received VTP advertisements on its trunk
links.
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 or switch stack, you cannot change the VTP
mode to server. You receive an error message, and the configuration is not allowed.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
13-12
OL-12189-01
Chapter 13
Configuring VTP
Configuring VTP
Note
You can also configure VTP transparent mode by using the vlan database privileged EXEC command
to enter VLAN database configuration mode and by entering the vtp transparent command, similar to
the second procedure under the Configuring a VTP Server section on page 13-9. Use the no vtp
transparent VLAN database configuration command to return the switch to VTP server mode. 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.
Enabling VTP Version 2
VTP Version 2 is disabled by default on VTP Version 2-capable switches. When you enable VTP
Version 2 on a switch, every VTP Version 2-capable switch in the VTP domain enables Version 2. You
can only configure the version when the switches are in VTP server or transparent mode.
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 13-9.
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.
Step 3
end
Return to privileged EXEC mode.
Step 4
show vtp status
In the VTP V2 Mode field of the display, verify that VTP Version 2 is enabled.
To disable VTP Version 2, use the no vtp version global configuration command.
Note
You can also enable VTP Version 2 by using the vlan database privileged EXEC command to enter
VLAN database configuration mode and by entering the vtp v2-mode VLAN database configuration
command. To disable VTP Version 2, use the no vtp v2-mode VLAN database configuration command.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
13-13
Chapter 13
Configuring VTP
Configuring VTP
Enabling VTP Pruning
Pruning increases available bandwidth by restricting flooded traffic to those trunk links that the traffic
must use to access the destination devices. You can only enable VTP pruning on a switch in VTP server
mode.
Beginning in privileged EXEC mode, follow these steps to enable VTP pruning in the VTP domain:
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.
Note
You can also enable VTP pruning by using the vlan database privileged EXEC command to enter VLAN
database configuration mode and entering the vtp pruning VLAN database configuration command. To
disable VTP pruning, use the no vtp pruning VLAN database configuration command. You can also
enable VTP Version 2 by using the vtp pruning privileged EXEC 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 12-23.
Adding a VTP Client Switch to a VTP Domain
Before adding a VTP client 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
13-14
OL-12189-01
Chapter 13
Configuring VTP
Configuring VTP
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:
Step 1
Command
Purpose
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.
You can also change the VTP domain name by entering the vlan database privileged EXEC command
to enter VLAN database configuration mode and by entering the vtp domain domain-name command.
In this mode, you must enter the exit command to update VLAN information and return to privileged
EXEC mode.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
13-15
Chapter 13
Configuring VTP
Monitoring VTP
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 13-3 shows the privileged EXEC commands for monitoring VTP activity.
Table 13-3
VTP Monitoring Commands
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
13-16
OL-12189-01
CH A P T E R
14
Configuring Voice VLAN
This chapter describes how to configure the voice VLAN feature on the switch. Unless otherwise noted,
the term switch refers to a standalone switch and to a switch stack. Voice VLAN is 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.
This chapter consists of these sections:
Understanding Voice VLAN, page 14-1
Configuring Voice VLAN, page 14-3
Displaying Voice VLAN, page 14-7
Understanding Voice VLAN
The voice VLAN feature enables access ports to carry IP voice traffic from an IP phone. When the switch
is connected to a Cisco 7960 IP Phone, the phone sends voice traffic with Layer 3 IP precedence and
Layer 2 class of service (CoS) values, which are both set to 5 by default. Because the sound quality of
an IP phone call can deteriorate if the data is unevenly sent, the switch supports quality of service (QoS)
based on IEEE 802.1p CoS. QoS uses classification and scheduling to send network traffic from the
switch in a predictable manner. For more information on QoS, see Chapter 36, Configuring QoS.
The Cisco 7960 IP Phone is a configurable device, and you can configure it to forward traffic with an
IEEE 802.1p priority. You can configure the switch to trust or override the traffic priority assigned by a
Cisco IP Phone.
The Cisco IP Phone contains an integrated three-port 10/100 switch as shown in Figure 14-1. The ports
provide dedicated connections to these devices:
Port 1 connects to the switch or other voice-over-IP (VoIP) device.
Port 2 is an internal 10/100 interface that carries the IP Phone traffic.
Port 3 (access port) connects to a PC or other device.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
14-1
Chapter 14
Configuring Voice VLAN
Understanding Voice VLAN
Figure 14-1 shows one way to connect a Cisco 7960 IP Phone.
Figure 14-1
Cisco 7960 IP Phone Connected to a Switch
Cisco IP Phone 7960
Phone
ASIC
P2
3-port
switch
P3
Access
port
101351
P1
PC
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 phone to send voice
traffic to the switch in any of these ways:
Note
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)
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).
Cisco IP Phone Data Traffic
The switch can also process tagged data traffic (traffic in IEEE 802.1Q or IEEE 802.1p frame types) from
the device attached to the access port on the Cisco IP Phone (see Figure 14-1). You can configure Layer 2
access ports on the switch to send CDP packets that instruct the attached phone to configure the phone
access port in one of these modes:
In trusted mode, all traffic received through the access port on the Cisco IP Phone passes through
the phone unchanged.
In untrusted mode, all traffic in IEEE 802.1Q or IEEE 802.1p frames received through the access
port on the Cisco IP Phone receive a configured Layer 2 CoS value. The default Layer 2 CoS value
is 0. Untrusted mode is the default.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
14-2
OL-12189-01
Chapter 14
Configuring Voice VLAN
Configuring Voice VLAN
Note
Untagged traffic from the device attached to the Cisco IP Phone passes through the phone unchanged,
regardless of the trust state of the access port on the phone.
Configuring Voice VLAN
These sections contain this configuration information:
Default Voice VLAN Configuration, page 14-3
Voice VLAN Configuration Guidelines, page 14-3
Configuring a Port Connected to a Cisco 7960 IP Phone, page 14-4
Default Voice VLAN Configuration
The voice VLAN feature is disabled by default.
When the voice VLAN feature is enabled, all untagged traffic is sent according to the default CoS
priority of the port.
The CoS value is not trusted for IEEE 802.1p or IEEE 802.1Q tagged traffic.
Voice VLAN Configuration Guidelines
These are the voice VLAN configuration guidelines:
You should configure voice VLAN on switch access ports; voice VLAN is not supported on
trunk ports. You can configure a voice VLAN only on Layer 2 ports.
Note
Voice VLAN is only supported on access ports and not on trunk ports, even though the
configuration is allowed.
The voice VLAN should be present and active on the switch for the IP phone to correctly
communicate on the voice VLAN. Use the show vlan privileged EXEC command to see if the
VLAN is present (listed in the display). If the VLAN is not listed, see Chapter 12, Configuring
VLANs, for information on how to create the voice VLAN.
Do not configure voice VLAN on private VLAN ports.
Before you enable voice VLAN, we recommend that you enable QoS on the switch by entering the
mls qos global configuration command and configure the port trust state to trust by entering the mls
qos trust cos interface configuration command. If you use the auto-QoS feature, these settings are
automatically configured. For more information, see Chapter 36, Configuring QoS.
You must enable CDP on the switch port connected to the Cisco IP Phone to send the configuration
to the phone. (CDP is globally enabled by default on all switch interfaces.)
The Port Fast feature is automatically enabled when voice VLAN is configured. When you disable
voice VLAN, the Port Fast feature is not automatically disabled.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
14-3
Chapter 14
Configuring Voice VLAN
Configuring Voice VLAN
If the Cisco IP Phone and a device attached to the phone are in the same VLAN, they must be in the
same IP subnet. These conditions indicate that they are in the same VLAN:
They both use IEEE 802.1p or untagged frames.
The Cisco IP Phone uses IEEE 802.1p frames, and the device uses untagged frames.
The Cisco IP Phone uses untagged frames, and the device uses IEEE 802.1p frames.
The Cisco IP Phone uses IEEE 802.1Q frames, and the voice VLAN is the same as the access
VLAN.
The Cisco IP Phone and a device attached to the phone cannot communicate if they are in the same
VLAN and subnet but use different frame types because traffic in the same subnet is not routed
(routing would eliminate the frame type difference).
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 12-31 for more information.
IEEE 802.1x authenticated port. See the Configuring IEEE 802.1x Authentication section on
page 9-26 for more information.
Note
If you enable IEEE 802.1x on an access port on which a voice VLAN is configured and
to which a Cisco IP Phone is connected, the phone loses connectivity to the switch for
up to 30 seconds.
Protected port. See the Configuring Protected Ports section on page 25-5 for more
information.
A source or destination port for a SPAN or RSPAN session.
Secure port. See the Configuring Port Security section on page 25-7 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 phone requires up to two MAC addresses. The phone
address is learned on the voice VLAN and might also be learned on the access VLAN.
Connecting a PC to the phone requires additional MAC addresses.
Configuring a Port Connected to a Cisco 7960 IP Phone
Because a Cisco 7960 IP Phone also supports a connection to a PC or other device, a port connecting the
switch to a Cisco IP Phone can carry mixed traffic. You can configure a port to decide how the Cisco IP
Phone carries voice traffic and data traffic.
These sections contain this configuration information:
Configuring Cisco IP Phone Voice Traffic, page 14-5
Configuring the Priority of Incoming Data Frames, page 14-6
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
14-4
OL-12189-01
Chapter 14
Configuring Voice VLAN
Configuring Voice VLAN
Configuring Cisco IP Phone Voice Traffic
You can configure a port connected to the Cisco IP Phone to send CDP packets to the phone to configure
the way in which the phone sends voice traffic. The phone can carry voice traffic in IEEE 802.1Q frames
for a specified voice VLAN with a Layer 2 CoS value. It can use IEEE 802.1p priority tagging to give
voice traffic a higher priority and forward all voice traffic through the native (access) VLAN. The Cisco
IP Phone can also send untagged voice traffic or use its own configuration to send voice traffic in the
access VLAN. In all configurations, the voice traffic carries a Layer 3 IP precedence value (the default
is 5).
Beginning in privileged EXEC mode, follow these steps to configure voice traffic on a port:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
interface interface-id
Specify the interface connected to the phone, and enter interface
configuration mode.
Step 3
mls qos trust cos
Configure the interface to classify incoming traffic packets by using the
packet CoS value. For untagged packets, the port default CoS value is used.
Note
Step 4
Before configuring the port trust state, you must first globally enable
QoS by using the mls qos global configuration command.
switchport voice {detect
Configure how the Cisco IP Phone carries voice traffic:
cisco-phone [full-duplex] | vlan
detectConfigure the interface to detect and recognize a Cisco IP
{vlan-id | dot1p | none | untagged}}
phone.
cisco-phoneWhen you initially implement the switchport voice detect
command, this is the only allowed option. The default is no switchport
voice detect cisco-phone [full-duplex].
full-duplex(Optional) Configure the switch to only accept a
full-duplex Cisco IP phone.
vlan-idConfigure the phone to forward all voice traffic through the
specified VLAN. By default, the Cisco IP Phone forwards the voice
traffic with an IEEE 802.1Q priority of 5. Valid VLAN IDs are 1 to
4094.
dot1pConfigure the phone to use IEEE 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
IEEE 802.1p priority of 5.
noneAllow the phone to use its own configuration to send untagged
voice traffic.
untaggedConfigure the phone to send untagged voice traffic.
Step 5
end
Return to privileged EXEC mode.
Step 6
show interfaces interface-id
switchport or
Verify your voice VLAN entries.
show running-config interface
interface-id
Verify your QoS and voice VLAN entries.
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Step 7
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
14-5
Chapter 14
Configuring Voice VLAN
Configuring Voice VLAN
This example shows how to configure a port connected to a Cisco IP Phone to use the CoS value to
classify incoming traffic, to use IEEE 802.1p priority tagging for voice traffic, and to use 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.
This example shows how to enable switchport voice detect on a Cisco IP Phone:
Switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# interface gigabitethernet 1/0/1
Switch(config-if)# switchport voice?
detect
detection enhancement keyword
vlan
VLAN for voice traffic
Switch(config-if)# switchport voice detect?
cisco-phone
Cisco IP Phone
Switch(config-if)# switchport voice detect cisco-phone?
full-duplex
Cisco IP Phone
Switch(config-if)# switchport voice detect cisco-phone full-duplex
full-duplex
full duplex keyword
Switch(config-if)# end
This example shows how to disable switchport voice detect on a Cisco IP Phone:
Switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# interface gigabitethernet 1/0/1
Switch(config-if)# no switchport voice detect cisco-phone
Switch(config-if)# no switchport voice detect cisco-phone full-duplex
Configuring the Priority of Incoming Data Frames
You can connect a PC or other data device to a Cisco IP Phone port. To process tagged data traffic (in
IEEE 802.1Q or IEEE 802.1p frames), you can configure the switch to send CDP packets to instruct the
phone how to send data packets from the device attached to the access port on the Cisco IP Phone. The
PC can generate packets with an assigned CoS value. You can configure the phone to not change (trust)
or to override (not trust) the priority of frames arriving on the phone port from connected devices.
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
Specify the interface connected to the Cisco IP Phone, and enter interface
configuration mode.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
14-6
OL-12189-01
Chapter 14
Configuring Voice VLAN
Displaying Voice VLAN
Step 3
Command
Purpose
switchport priority extend
{cos value | trust}
Set the priority of data traffic received from the Cisco IP Phone access port:
cos valueConfigure the 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.
trustConfigure the 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
switchport
Verify your entries.
Step 6
copy running-config
startup-config
(Optional) Save your entries in the configuration file.
This example shows how to configure a port connected to a Cisco 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.
Displaying Voice VLAN
To display voice VLAN configuration for an interface, use the show interfaces interface-id switchport
privileged EXEC command.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
14-7
Chapter 14
Configuring Voice VLAN
Displaying Voice VLAN
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
14-8
OL-12189-01
CH A P T E R
15
Configuring Private VLANs
This chapter describes how to configure private VLANs on the switch. Unless otherwise noted, the term
switch refers to a standalone switch and to a switch stack.
Note
For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
The chapter consists of these sections:
Note
Understanding Private VLANs, page 15-1
Configuring Private VLANs, page 15-6
Monitoring Private VLANs, page 15-15
When you configure private VLANs, the switch must be in VTP transparent mode. See Chapter 13,
Configuring VTP.
Understanding Private VLANs
The private-VLAN feature addresses two problems that service providers face when using VLANs:
Scalability: The switch supports up to 1005 active VLANs. If a service provider assigns one VLAN
per customer, this limits the numbers of customers the service provider can support.
To enable IP routing, each VLAN is assigned a subnet address space or a block of addresses, which
can result in wasting the unused IP addresses, and cause IP address management problems.
Using private VLANs addresses the scalability problem and provides IP address management benefits
for service providers and Layer 2 security for customers. Private VLANs partition a regular VLAN
domain into subdomains. A subdomain is represented by a pair of VLANs: a primary VLAN and a
secondary VLAN. A private VLAN can have multiple VLAN pairs, one pair for each subdomain. All
VLAN pairs in a private VLAN share the same primary VLAN. The secondary VLAN ID differentiates
one subdomain from another. See Figure 15-1.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
15-1
Chapter 15
Configuring Private VLANs
Understanding Private VLANs
Figure 15-1
Private-VLAN Domain
Private
VLAN
domain
Subdomain
Subdomain
Secondary
isolated VLAN
201784
Secondary
community VLAN
Primary
VLAN
There are two types of secondary VLANs:
Isolated VLANsPorts within an isolated VLAN cannot communicate with each other at the
Layer 2 level.
Community VLANsPorts within a community VLAN can communicate with each other but
cannot communicate with ports in other communities at the Layer 2 level.
Private VLANs provide Layer 2 isolation between ports within the same private VLAN. Private-VLAN
ports are access ports that are one of these types:
Note
PromiscuousA promiscuous port belongs to the primary VLAN and can communicate with all
interfaces, including the community and isolated host ports that belong to the secondary VLANs
associated with the primary VLAN.
IsolatedAn isolated port is a host port that belongs to an isolated secondary VLAN. It has
complete Layer 2 separation from other ports within the same private VLAN, except for the
promiscuous ports. Private VLANs block all traffic to isolated ports except traffic from promiscuous
ports. Traffic received from an isolated port is forwarded only to promiscuous ports.
CommunityA community port is a host port that belongs to a community secondary VLAN.
Community ports communicate with other ports in the same community VLAN and with
promiscuous ports. These interfaces are isolated at Layer 2 from all other interfaces in other
communities and from isolated ports within their private VLAN.
Trunk ports carry traffic from regular VLANs and also from primary, isolated, and community VLANs.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
15-2
OL-12189-01
Chapter 15
Configuring Private VLANs
Understanding Private VLANs
Primary and secondary VLANs have these characteristics:
Primary VLANA private VLAN has only one primary VLAN. Every port in a private VLAN is a
member of the primary VLAN. The primary VLAN carries unidirectional traffic downstream from
the promiscuous ports to the (isolated and community) host ports and to other promiscuous ports.
Isolated VLAN A private VLAN has only one isolated VLAN. An isolated VLAN is a secondary
VLAN that carries unidirectional traffic upstream from the hosts toward the promiscuous ports and
the gateway.
Community VLANA community VLAN is a secondary VLAN that carries upstream traffic from
the community ports to the promiscuous port gateways and to other host ports in the same
community. You can configure multiple community VLANs in a private VLAN.
A promiscuous port can serve only one primary VLAN, one isolated VLAN, and multiple community
VLANs. Layer 3 gateways are typically connected to the switch through a promiscuous port. With a
promiscuous port, you can connect a wide range of devices as access points to a private VLAN. For
example, you can use a promiscuous port to monitor or back up all the private-VLAN servers from an
administration workstation.
In a switched environment, you can assign an individual private VLAN and associated IP subnet to each
individual or common group of end stations. The end stations need to communicate only with a default
gateway to communicate outside the private VLAN.
You can use private VLANs to control access to end stations in these ways:
Configure selected interfaces connected to end stations as isolated ports to prevent any
communication at Layer 2. For example, if the end stations are servers, this configuration prevents
Layer 2 communication between the servers.
Configure interfaces connected to default gateways and selected end stations (for example, backup
servers) as promiscuous ports to allow all end stations access to a default gateway.
You can extend private VLANs across multiple devices by trunking the primary, isolated, and
community VLANs to other devices that support private VLANs. To maintain the security of your
private-VLAN configuration and to avoid other use of the VLANs configured as private VLANs,
configure private VLANs on all intermediate devices, including devices that have no private-VLAN
ports.
IP Addressing Scheme with Private VLANs
Assigning a separate VLAN to each customer creates an inefficient IP addressing scheme:
Assigning a block of addresses to a customer VLAN can result in unused IP addresses.
If the number of devices in the VLAN increases, the number of assigned address might not be large
enough to accommodate them.
These problems are reduced by using private VLANs, where all members in the private VLAN share a
common address space, which is allocated to the primary VLAN. Hosts are connected to secondary
VLANs, and the DHCP server assigns them IP addresses from the block of addresses allocated to the
primary VLAN. Subsequent IP addresses can be assigned to customer devices in different secondary
VLANs, but in the same primary VLAN. When new devices are added, the DHCP server assigns them
the next available address from a large pool of subnet addresses.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
15-3
Chapter 15
Configuring Private VLANs
Understanding Private VLANs
Private VLANs across Multiple Switches
As with regular VLANs, private VLANs can span multiple switches. A trunk port carries the primary
VLAN and secondary VLANs to a neighboring switch. The trunk port treats the private VLAN as any
other VLAN. A feature of private VLANs across multiple switches is that traffic from an isolated port
in switch A does not reach an isolated port on Switch B. See Figure 15-2.
Figure 15-2
Private VLANs across Switches
Trunk ports
VLAN 100
VLAN 100
Switch B
VLAN 201
VLAN 201
VLAN 202
VLAN 202
Carries VLAN 100,
201, and 202 traffic
201785
Switch A
VLAN 100 = Primary VLAN
VLAN 201 = Secondary isolated VLAN
VLAN 202 = Secondary community VLAN
Because VTP does not support private VLANs, you must manually configure private VLANs on all
switches in the Layer 2 network. If you do not configure the primary and secondary VLAN association
in some switches in the network, the Layer 2 databases in these switches are not merged. This 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 8, Configuring SDM Templates.
Private-VLAN Interaction with Other Features
Private VLANs have specific interaction with some other features, described in these sections:
Private VLANs and Unicast, Broadcast, and Multicast Traffic, page 15-5
Private VLANs and SVIs, page 15-5
Private VLANs and Switch Stacks, page 15-5
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
15-4
OL-12189-01
Chapter 15
Configuring Private VLANs
Understanding Private VLANs
You should also see the Secondary and Primary VLAN Configuration section on page 15-7 under the
Private-VLAN Configuration Guidelines section.
Private VLANs and Unicast, Broadcast, and Multicast Traffic
In regular VLANs, devices in the same VLAN can communicate with each other at the Layer 2 level, but
devices connected to interfaces in different VLANs must communicate at the Layer 3 level. In private
VLANs, the promiscuous ports are members of the primary VLAN, while the host ports belong to
secondary VLANs. Because the secondary VLAN is associated to the primary VLAN, members of the
these VLANs can communicate with each other at the Layer 2 level.
In a regular VLAN, broadcasts are forwarded to all ports in that VLAN. Private VLAN broadcast
forwarding depends on the port sending the broadcast:
An isolated port sends a broadcast only to the promiscuous ports or trunk ports.
A community port sends a broadcast to all promiscuous ports, trunk ports, and ports in the same
community VLAN.
A promiscuous port sends a broadcast to all ports in the private VLAN (other promiscuous ports,
trunk ports, isolated ports, and community ports).
Multicast traffic is routed or bridged across private-VLAN boundaries and within a single community
VLAN. Multicast traffic is not forwarded between ports in the same isolated VLAN or between ports in
different secondary VLANs.
Private VLANs and SVIs
In a Layer 3 switch, a switch virtual interface (SVI) represents the Layer 3 interface of a VLAN. Layer 3
devices communicate with a private VLAN only through the primary VLAN and not through secondary
VLANs. Configure Layer 3 VLAN interfaces (SVIs) only for primary VLANs. You cannot configure
Layer 3 VLAN interfaces for secondary VLANs. SVIs for secondary VLANs are inactive while the
VLAN is configured as a secondary VLAN.
If you try to configure a VLAN with an active SVI as a secondary VLAN, the configuration is not
allowed until you disable the SVI.
If you try to create an SVI on a VLAN that is configured as a secondary VLAN and the secondary
VLAN is already mapped at Layer 3, the SVI is not created, and an error is returned. If the SVI is
not mapped at Layer 3, the SVI is created, but it is automatically shut down.
When the primary VLAN is associated with and mapped to the secondary VLAN, any configuration on
the primary VLAN is propagated to the secondary VLAN SVIs. For example, if you assign an IP subnet
to the primary VLAN SVI, this subnet is the IP subnet address of the entire private VLAN.
Private VLANs and Switch Stacks
Private VLANs can operate within the switch stack, and private-VLAN ports can reside on different
stack members. However, some changes to the switch stack can impact private-VLAN operation:
If a stack contains only one private-VLAN promiscuous port and the stack member that contains that
port is removed from the stack, host ports in that private VLAN lose connectivity outside the private
VLAN.
If a stack master stack that contains the only private-VLAN promiscuous port in the stack fails or
leaves the stack and a new stack master is elected, host ports in a private VLAN that had its
promiscuous port on the old stack master lose connectivity outside of the private VLAN.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
15-5
Chapter 15
Configuring Private VLANs
Configuring Private VLANs
If two stacks merge, private VLANs on the winning stack are not affected, but private-VLAN
configuration on the losing switch is lost when that switch reboots.
For more information about switch stacks, see Chapter 5, Managing Switch Stacks.
Configuring Private VLANs
These sections contain this configuration information:
Tasks for Configuring Private VLANs, page 15-6
Default Private-VLAN Configuration, page 15-6
Private-VLAN Configuration Guidelines, page 15-7
Configuring and Associating VLANs in a Private VLAN, page 15-10
Configuring a Layer 2 Interface as a Private-VLAN Host Port, page 15-11
Configuring a Layer 2 Interface as a Private-VLAN Promiscuous Port, page 15-13
Mapping Secondary VLANs to a Primary VLAN Layer 3 VLAN Interface, page 15-14
Tasks for Configuring Private VLANs
To configure a private VLAN, perform these steps:
Step 1
Set VTP mode to transparent.
Step 2
Create the primary and secondary VLANs and associate them. See the Configuring and Associating
VLANs in a Private VLAN section on page 15-10.
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 15-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 15-13.
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 15-14.
Step 6
Verify private-VLAN configuration.
Default Private-VLAN Configuration
No private VLANs are configured.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
15-6
OL-12189-01
Chapter 15
Configuring Private VLANs
Configuring Private VLANs
Private-VLAN Configuration Guidelines
Guidelines for configuring private VLANs fall into these categories:
Secondary and Primary VLAN Configuration, page 15-7
Private-VLAN Port Configuration, page 15-8
Limitations with Other Features, page 15-9
Secondary and Primary VLAN Configuration
Follow these guidelines when configuring private VLANs:
Set VTP to transparent mode. After you configure a private VLAN, you should not change the VTP
mode to client or server. For information about VTP, see Chapter 13, Configuring VTP.
You must use VLAN configuration (config-vlan) mode to configure private VLANs. You cannot
configure private VLANs in VLAN database configuration mode. For more information about
VLAN configuration, see the VLAN Configuration Mode Options section on page 12-7.
After you have configured private VLANs, use the copy running-config startup config privileged
EXEC command to save the VTP transparent mode configuration and private-VLAN configuration
in the switch startup configuration file. Otherwise, if the switch resets, it defaults to VTP server
mode, which does not support private VLANs.
VTP does not propagate private-VLAN configuration. You must configure private VLANs on each
device where you want private-VLAN ports.
You cannot configure VLAN 1 or VLANs 1002 to 1005 as primary or secondary VLANs. Extended
VLANs (VLAN IDs 1006 to 4094) can belong to private VLANs
A primary VLAN can have one isolated VLAN and multiple community VLANs associated with it.
An isolated or community VLAN can have only one primary VLAN associated with it.
Although a private VLAN contains more than one VLAN, only one Spanning Tree Protocol (STP)
instance runs for the entire private VLAN. When a secondary VLAN is associated with the primary
VLAN, the STP parameters of the primary VLAN are propagated to the secondary VLAN.
You can enable DHCP snooping on private VLANs. When you enable DHCP snooping on the
primary VLAN, it is propagated to the secondary VLANs. If you configure DHCP on a secondary
VLAN, the configuration does not take effect if the primary VLAN is already configured.
When you enable IP source guard on private-VLAN ports, you must enable DHCP snooping on the
primary VLAN.
We recommend that you prune the private VLANs from the trunks on devices that carry no traffic
in the private VLANs.
You can apply different quality of service (QoS) configurations to primary, isolated, and community
VLANs.
When you configure private VLANs, sticky Address Resolution Protocol (ARP) is enabled by
default, and ARP entries learned on Layer 3 private VLAN interfaces are sticky ARP entries. For
security reasons, private VLAN port sticky ARP entries do not age out.
Note
We recommend that you display and verify private-VLAN interface ARP entries.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
15-7
Chapter 15
Configuring Private VLANs
Configuring Private VLANs
Connecting a device with a different MAC address but with the same IP address generates a
message, and the ARP entry is not created. You must manually remove private-VLAN port ARP
entries if a MAC address changes.
You can remove a private-VLAN ARP entry by using the no arp ip-address global configuration
command.
You can add a private-VLAN ARP entry by using the arp ip-address hardware-address type
global configuration command.
You can configure VLAN maps on primary and secondary VLANs (see the Configuring VLAN
Maps section on page 34-29). However, we recommend that you configure the same VLAN maps
on private-VLAN primary and secondary VLANs.
When a frame is Layer-2 forwarded within a private VLAN, the same VLAN map is applied at the
ingress side and at the egress side. When a frame is routed from inside a private VLAN to an external
port, the private-VLAN map is applied at the ingress side.
For frames going upstream from a host port to a promiscuous port, the VLAN map configured
on the secondary VLAN is applied.
For frames going downstream from a promiscuous port to a host port, the VLAN map
configured on the primary VLAN is applied.
To filter out specific IP traffic for a private VLAN, you should apply the VLAN map to both the
primary and secondary VLANs.
You can apply router ACLs only on the primary-VLAN SVIs. The ACL is applied to both primary
and secondary VLAN Layer 3 traffic.
Although private VLANs provide host isolation at Layer 2, hosts can communicate with each other
at Layer 3.
Private VLANs support these Switched Port Analyzer (SPAN) features:
You can configure a private-VLAN port as a SPAN source port.
You can use VLAN-based SPAN (VSPAN) on primary, isolated, and community VLANs or use
SPAN on only one VLAN to separately monitor egress or ingress traffic.
Private-VLAN Port Configuration
Follow these guidelines when configuring private-VLAN ports:
Use only the private-VLAN configuration commands to assign ports to primary, isolated, or
community VLANs. Layer 2 access ports assigned to the VLANs that you configure as primary,
isolated, or community VLANs are inactive while the VLAN is part of the private-VLAN
configuration. Layer 2 trunk interfaces remain in the STP forwarding state.
Do not configure ports that belong to a PAgP or LACP EtherChannel as private-VLAN ports. While
a port is part of the private-VLAN configuration, any EtherChannel configuration for it is inactive.
Enable Port Fast and BPDU guard on isolated and community host ports to prevent STP loops due
to misconfigurations and to speed up STP convergence (see Chapter 19, Configuring Optional
Spanning-Tree Features). When enabled, STP applies the BPDU guard feature to all Port
Fast-configured Layer 2 LAN ports. Do not enable Port Fast and BPDU guard on promiscuous ports.
If you delete a VLAN used in the private-VLAN configuration, the private-VLAN ports associated
with the VLAN become inactive.
Private-VLAN ports can be on different network devices if the devices are trunk-connected and the
primary and secondary VLANs have not been removed from the trunk.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
15-8
OL-12189-01
Chapter 15
Configuring Private VLANs
Configuring Private VLANs
Limitations with Other Features
When configuring private VLANs, remember these limitations with other features:
Note
In some cases, the configuration is accepted with no error messages, but the commands have no effect.
Do not configure fallback bridging on switches with private VLANs.
When IGMP snooping is enabled on the switch (the default), the switch or switch stack supports no
more than 20 private-VLAN domains.
Do not configure a remote SPAN (RSPAN) VLAN as a private-VLAN primary or secondary VLAN.
For more information about SPAN, see Chapter 29, Configuring SPAN and RSPAN.
Do not configure private-VLAN ports on interfaces configured for these other features:
dynamic-access port VLAN membership
Dynamic Trunking Protocol (DTP)
Port Aggregation Protocol (PAgP)
Link Aggregation Control Protocol (LACP)
Multicast VLAN Registration (MVR)
voice VLAN
Web Cache Communication Protocol (WCCP)
You can configure IEEE 802.1x port-based authentication on a private-VLAN port, but do not
configure 802.1x with port security, voice VLAN, or per-user ACL on private-VLAN ports.
A private-VLAN host or promiscuous port cannot be a SPAN destination port. If you configure a
SPAN destination port as a private-VLAN port, the port becomes inactive.
If you configure a static MAC address on a promiscuous port in the primary VLAN, you must add
the same static address to all associated secondary VLANs. If you configure a static MAC address
on a host port in a secondary VLAN, you must add the same static MAC address to the associated
primary VLAN. When you delete a static MAC address from a private-VLAN port, you must remove
all instances of the configured MAC address from the private VLAN.
Note
Dynamic MAC addresses learned in one VLAN of a private VLAN are replicated in the
associated VLANs. For example, a MAC address learned in a secondary VLAN is replicated
in the primary VLAN. When the original dynamic MAC address is deleted or aged out, the
replicated addresses are removed from the MAC address table.
Configure Layer 3 VLAN interfaces (SVIs) only for primary VLANs.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
15-9
Chapter 15
Configuring Private VLANs
Configuring Private VLANs
Configuring and Associating VLANs in a Private VLAN
Beginning in privileged EXEC mode, follow these steps to configure a private VLAN:
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
15-10
OL-12189-01
Chapter 15
Configuring Private VLANs
Configuring 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
Configuring a Layer 2 Interface as a Private-VLAN Host Port
Beginning in privileged EXEC mode, follow these steps to configure a Layer 2 interface as a
private-VLAN host port and to associate it with primary and secondary VLANs:
Note
Isolated and community VLANs are both secondary VLANs.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
15-11
Chapter 15
Configuring Private VLANs
Configuring Private VLANs
Command
Purpose
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
primary_vlan_id secondary_vlan_id
Associate the Layer 2 port with a private VLAN.
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.
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 gigabitethernet1/0/2
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 gigabitethernet1/0/2 switchport
Name: Gi1/0/2
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>
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
15-12
OL-12189-01
Chapter 15
Configuring Private VLANs
Configuring Private VLANs
Configuring a Layer 2 Interface as a Private-VLAN Promiscuous Port
Beginning in privileged EXEC mode, follow these steps to configure a Layer 2 interface as a
private-VLAN promiscuous port and map it to primary and secondary VLANs:
Note
Isolated and community VLANs are both secondary VLANs.
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.
Step 4
switchport private-vlan mapping primary_vlan_id
{add | remove} secondary_vlan_list
Map the private-VLAN promiscuous port to a primary
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 gigabitethernet1/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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
15-13
Chapter 15
Configuring Private VLANs
Configuring Private VLANs
Mapping Secondary VLANs to a Primary VLAN Layer 3 VLAN Interface
If the private VLAN will be used for inter-VLAN routing, you configure an SVI for the primary VLAN
and map secondary VLANs to the SVI.
Note
Isolated and community VLANs are both secondary VLANs.
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.
Step 3
private-vlan mapping [add | remove]
secondary_vlan_list
Map the secondary VLANs to the Layer 3 VLAN
interface of a primary VLAN to allow Layer 3 switching
of private-VLAN ingress traffic.
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.
Step 4
Note
The private-vlan mapping interface configuration command only affects private-VLAN traffic that is
Layer 3 switched.
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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
15-14
OL-12189-01
Chapter 15
Configuring Private VLANs
Monitoring Private VLANs
Monitoring Private VLANs
Table 15-1 shows the privileged EXEC commands for monitoring private-VLAN activity.
Table 15-1
Private VLAN Monitoring Commands
Command
Purpose
show interfaces status
Displays the status of interfaces, including the VLANs to which they
belongs.
show vlan private-vlan
[type]
Display the private-VLAN information for the switch.
show interface switchport
Display private-VLAN configuration on interfaces.
show interface
private-vlan mapping
Display information about the private-VLAN mapping for VLAN SVIs.
This is an example of the output from the show vlan private-vlan command:
Switch(config)# show vlan private-vlan
Primary Secondary Type
Ports
------- --------- ----------------- -----------------------------------------10
501
isolated
Gi2/0/1, Gi3/0/1, Gi3/0/2
10
502
community
Gi2/0/11, Gi3/0/1, Gi3/0/4
10
503
non-operational
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
15-15
Chapter 15
Configuring Private VLANs
Monitoring Private VLANs
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
15-16
OL-12189-01
CH A P T E R
16
Configuring IEEE 802.1Q and Layer 2 Protocol
Tunneling
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 switch supports
IEEE 802.1Q tunneling and Layer 2 protocol tunneling. Unless otherwise noted, the term switch refers
to a standalone switch and to a switch stack.
Note
For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
This chapter contains these sections:
Understanding IEEE 802.1Q Tunneling, page 16-1
Configuring IEEE 802.1Q Tunneling, page 16-4
Understanding Layer 2 Protocol Tunneling, page 16-7
Configuring Layer 2 Protocol Tunneling, page 16-10
Monitoring and Maintaining Tunneling Status, page 16-18
Understanding IEEE 802.1Q Tunneling
Business customers of service providers often have specific requirements for VLAN IDs and the number
of VLANs to be supported. The VLAN ranges required by different customers in the same
service-provider network might overlap, and traffic of customers through the infrastructure might be
mixed. Assigning a unique range of VLAN IDs to each customer would restrict customer configurations
and could easily exceed the VLAN limit (4096) of the IEEE 802.1Q specification.
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 network, even when they appear to be in the same VLAN. Using
IEEE 802.1Q tunneling expands VLAN space by using a VLAN-in-VLAN hierarchy and retagging 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 ID that is dedicated to tunneling. Each customer
requires a separate service-provider VLAN ID, but that VLAN ID supports all of the customers VLANs.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
16-1
Chapter 16
Configuring IEEE 802.1Q and Layer 2 Protocol Tunneling
Understanding IEEE 802.1Q Tunneling
Customer traffic tagged in the normal way with appropriate VLAN IDs comes 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 asymmetric 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 16-1.
Figure 16-1
IEEE 802.1Q Tunnel Ports in a Service-Provider Network
Customer A
VLANs 1 to 100
Customer A
VLANs 1 to 100
Service
provider
Tunnel port
VLAN 30
Tunnel port
VLAN 30
Trunk
ports
Tunnel port
VLAN 30
Trunk
ports
Tunnel port
VLAN 40
74016
Tunnel port
VLAN 40
Customer B
VLANs 1 to 200
Trunk
Asymmetric link
Customer B
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 the tagged packets remain intact
inside the switch and when they exit the trunk port into the service-provider network, they 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 customer IEEE 802.1Q tag is preserved in the
encapsulated packet. Therefore, packets entering the service-provider network are double-tagged, with
the outer (metro) tag containing the customers access VLAN ID, and the inner VLAN ID being that 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 switch processes the packet. When the packet exits another trunk port on the same core
switch, the same metro tag is again added to the packet. Figure 16-2 shows the tag structures of the
double-tagged packets.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
16-2
OL-12189-01
Chapter 16
Configuring IEEE 802.1Q and Layer 2 Protocol Tunneling
Understanding IEEE 802.1Q Tunneling
Original (Normal), IEEE 802.1Q, and Double-Tagged Ethernet Packet Formats
Source
address
Destination
Length/
address
EtherType
DA
SA
Len/Etype
DA
SA
Etype
DA
SA
Etype
Frame Check
Sequence
Data
Tag
Tag
FCS
Len/Etype
Etype
Tag
Original Ethernet frame
Data
Len/Etype
FCS
IEE 802.1Q frame from
customer network
Data
FCS
74072
Figure 16-2
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 switch internally processes the packet. However, the metro tag is not added when the
packet is sent out the tunnel port on the edge switch into the customer network. The packet is sent as a
normal IEEE 802.1Q-tagged frame to preserve the original VLAN numbers in the customer network.
In Figure 16-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. 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 customers 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 traffic coming from a customer network is not tagged (native VLAN frames), these packets are bridged
or routed as 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.)
Because 802.1Q tunneling is configured on a per-port basis, it does not matter whether the switch is a
standalone switch or a stack member. All configuration is done on the stack master.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
16-3
Chapter 16
Configuring IEEE 802.1Q and Layer 2 Protocol Tunneling
Configuring IEEE 802.1Q Tunneling
Configuring IEEE 802.1Q Tunneling
These sections contain this configuration information:
Default IEEE 802.1Q Tunneling Configuration, page 16-4
IEEE 802.1Q Tunneling Configuration Guidelines, page 16-4
IEEE 802.1Q Tunneling and Other Features, page 16-6
Configuring an IEEE 802.1Q Tunneling Port, page 16-6
Default IEEE 802.1Q Tunneling Configuration
By default, IEEE 802.1Q tunneling is disabled because the default switchport mode is dynamic auto.
Tagging of IEEE 802.1Q native VLAN packets on all IEEE 802.1Q trunk ports is also disabled.
IEEE 802.1Q Tunneling Configuration Guidelines
When you configure IEEE 802.1Q tunneling, you should always use an asymmetrical link between the
customer device and the edge switch, with the customer device port configured as an IEEE 802.1Q trunk
port and the edge switch port configured as a tunnel port.
Assign tunnel ports only to VLANs that are used for tunneling.
Configuration requirements for native VLANs and for and maximum transmission units (MTUs) are
explained in these next sections.
Native VLANs
When configuring IEEE 802.1Q tunneling on an edge switch, you must use IEEE 802.1Q trunk ports for
sending packets into the service-provider network. However, packets going through the core of the
service-provider network can 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 sending trunk port.
See Figure 16-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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
16-4
OL-12189-01
Chapter 16
Configuring IEEE 802.1Q and Layer 2 Protocol Tunneling
Configuring IEEE 802.1Q Tunneling
These are some ways to solve this problem:
Use ISL trunks between core switches in the service-provider network. Although customer
interfaces connected to edge switches must be IEEE 802.1Q trunks, we recommend using ISL trunks
for connecting switches in the core layer.
Use the vlan dot1q tag native global configuration command to configure the edge switch so that
all packets going out an IEEE 802.1Q trunk, including the native VLAN, are tagged. If the switch
is configured to tag native VLAN packets on all IEEE 802.1Q trunks, the switch accepts untagged
packets, but sends only tagged packets.
Ensure that the native VLAN ID on the edge-switch trunk port is not within the customer VLAN
range. For example, if the trunk port carries traffic of VLANs 100 to 200, assign the native VLAN
a number outside that range.
Figure 16-3
Potential Problem with IEEE 802.1Q Tunneling and Native VLANs
Tag not added
for VLAN 40
Tag
removed
Switch D
Customer X
VLANs 30-40
Native VLAN 40
Service
provider
Tunnel port
Packet tagged
for VLAN 30
Switch A
Customer X
Q
Tunnel port
Access VLAN 40
VLANs 5-50
Native
VLAN 40
Switch C VLAN 40
Q
Tunnel port
Access VLAN 30
802.1Q
trunk port
VLANs 30-40
Native VLAN 40
Trunk
Asymmetric link
Correct path for traffic
Incorrect path for traffic due to
misconfiguration of native VLAN
by sending port on Switch B
Q = 802.1Q trunk ports
Switch E
Customer Y
101820
Switch B
System MTU
The default system MTU for traffic on the switch is 1500 bytes.
You can configure 10-Gigabit and Gigabit Ethernet ports to support frames larger than 1500 bytes by
using the system mtu jumbo global configuration command.
The system jumbo MTU values do not include the IEEE 802.1Q header. 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 adding 4 bytes to
the system MTU and system jumbo MTU sizes.
For example, the switch supports a maximum frame size of 1496 bytes with this configuration:
The switch has a system jumbo MTU value of 1500 bytes, and the switchport mode dot1q tunnel
interface configuration command is configured on a 10-Gigabit or Gigabit Ethernet switch port.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
16-5
Chapter 16
Configuring IEEE 802.1Q and Layer 2 Protocol Tunneling
Configuring IEEE 802.1Q Tunneling
IEEE 802.1Q Tunneling and Other Features
Although IEEE 802.1Q tunneling works well for Layer 2 packet switching, there are incompatibilities
between some Layer 2 features and Layer 3 switching.
A tunnel port cannot be a routed port.
IP routing is not supported on a VLAN that includes IEEE 802.1Q ports. Packets received from a
tunnel port are forwarded based only on Layer 2 information. If routing is enabled on a switch
virtual interface (SVI) that includes tunnel ports, untagged IP packets received from the tunnel port
are recognized and routed by the switch. Customer can access the internet through its native VLAN.
If this access is not needed, you should not configure SVIs on VLANs that include tunnel ports.
Fallback bridging is not supported on tunnel ports. Because all IEEE 802.1Q-tagged packets
received from a tunnel port are treated as non-IP packets, if fallback bridging is enabled on VLANs
that have tunnel ports configured, IP packets would be improperly bridged across VLANs.
Therefore, you must not enable fallback bridging on VLANs with tunnel ports.
Tunnel ports do not support IP access control lists (ACLs).
Layer 3 quality of service (QoS) ACLs and other QoS features related to Layer 3 information are
not supported on tunnel ports. MAC-based QoS is supported on tunnel ports.
EtherChannel port groups are compatible with tunnel ports as long as the IEEE 802.1Q
configuration is consistent within an EtherChannel port group.
Port Aggregation Protocol (PAgP), Link Aggregation Control Protocol (LACP), and UniDirectional
Link Detection (UDLD) are supported on IEEE 802.1Q tunnel ports.
Dynamic Trunking Protocol (DTP) is not compatible with IEEE 802.1Q tunneling because you must
manually configure asymmetric links with tunnel ports and trunk ports.
VLAN Trunking Protocol (VTP) does not work between devices that are connected by an
asymmetrical link or devices that communicate through a tunnel.
Loopback detection is supported on IEEE 802.1Q tunnel ports.
When a port is configured as an IEEE 802.1Q tunnel port, spanning-tree bridge protocol data unit
(BPDU) filtering is automatically enabled on the interface. Cisco Discovery Protocol (CDP) and the
Layer Link Discovery Protocol (LLDP) are automatically disabled on the interface.
Configuring an IEEE 802.1Q Tunneling Port
Beginning in privileged EXEC mode, follow these steps to configure a port as an IEEE 802.1Q tunnel
port:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
interface interface-id
Enter interface configuration mode for 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 48).
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.
Step 4
switchport mode dot1q-tunnel
Set the interface as an IEEE 802.1Q tunnel port.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
16-6
OL-12189-01
Chapter 16
Configuring IEEE 802.1Q and Layer 2 Protocol Tunneling
Understanding Layer 2 Protocol Tunneling
Command
Purpose
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, and a customer VLAN ID is the
same as the native VLAN, the trunk port does not apply a metro tag, and
packets could be sent to the wrong destination.
Step 7
end
Return to privileged EXEC mode.
Step 8
show running-config
Display the ports configured for IEEE 802.1Q tunneling.
show dot1q-tunnel
Display the ports that are in tunnel mode.
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 desirable. Use the no vlan dot1q tag native global configuration command to
disable tagging of native VLAN packets.
This example shows how to configure an interface 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
Gigabit Ethernet interface 7 on stack member 1 is VLAN 22.
Switch(config)# interface gigabitethernet1/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 gigabitethernet1/0/7
Port
----Gi1/0/1Port
----Switch# show vlan dot1q tag native
dot1q native vlan tagging is enabled
Understanding Layer 2 Protocol Tunneling
Customers at different sites connected across a service-provider network need to use various Layer 2
protocols to scale their topologies to include all remote sites, as well as the local sites. STP must run
properly, and every VLAN should build a proper spanning tree that includes the local site and all remote
sites across the service-provider network. Cisco Discovery Protocol (CDP) must discover neighboring
Cisco devices from local and remote sites. VLAN Trunking Protocol (VTP) must provide consistent
VLAN configuration throughout all sites in the customer network.
When protocol tunneling is enabled, edge switches on the inbound side of the service-provider network
encapsulate Layer 2 protocol packets with a special MAC address and send them across the
service-provider network. Core switches in the network do not process these packets but forward them
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
16-7
Chapter 16
Configuring IEEE 802.1Q and Layer 2 Protocol Tunneling
Understanding Layer 2 Protocol Tunneling
as normal packets. Layer 2 protocol data units (PDUs) for CDP, STP, or VTP cross the service-provider
network and are delivered to customer switches on the outbound side of the service-provider network.
Identical packets are received by all customer ports on the same VLANs with these results:
Note
Users on each of a customers sites can properly run STP, and every VLAN can build a correct
spanning tree based on parameters from all sites and not just from the local site.
CDP discovers and shows information about the other Cisco devices connected through the
service-provider network.
VTP provides consistent VLAN configuration throughout the customer network, propagating to all
switches through the service provider.
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 customers 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 customers 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 and by enabling tunneling on the
service-provider access port.
For example, in Figure 16-4, 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, Site 1, will build a spanning tree on the switches at that site without considering
convergence parameters based on Customer Xs switch in Site 2. This could result in the topology shown
in Figure 16-5.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
16-8
OL-12189-01
Chapter 16
Configuring IEEE 802.1Q and Layer 2 Protocol Tunneling
Understanding Layer 2 Protocol Tunneling
Figure 16-4
Layer 2 Protocol Tunneling
Customer X Site 1
VLANs 1 to 100
Customer X Site 2
VLANs 1 to 100
Service
provider
VLAN 30
VLAN 30
VLAN 30
Trunk
ports
Trunk
ports
Switch A
Switch C
Switch B
Switch D
Trunk
ports
VLAN 40
Trunk
Asymmetric link
Customer Y Site 1
VLANs 1 to 200
Figure 16-5
VLAN 40
101822
Trunk
ports
Customer Y Site 2
VLANs 1 to 200
Layer 2 Network Topology without Proper Convergence
101821
Customer X
virtual network
VLANs 1 to 100
In an SP 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 SP switch, remote customer switches receive the PDUs and can negotiate the automatic creation of
EtherChannels.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
16-9
Chapter 16
Configuring IEEE 802.1Q and Layer 2 Protocol Tunneling
Configuring Layer 2 Protocol Tunneling
For example, in Figure 16-6, 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 16-14 for instructions.
Layer 2 Protocol Tunneling for EtherChannels
Service
Provider
EtherChannel 1
Customer A
Site 1
VLAN 17
VLAN 17
VLAN 18
Switch A
Switch C
VLAN 18
Customer A
Site 2
VLAN 19
VLAN 19
VLAN 20
EtherChannel 1
Switch B
Switch D
101844
Figure 16-6
VLAN 20
Trunk
Asymmetric link
Configuring Layer 2 Protocol Tunneling
You can enable Layer 2 protocol tunneling (by protocol) on the ports that are connected to the customer
in the edge switches of the service-provider network. The service-provider edge switches connected to
the customer switch perform the tunneling process. Edge-switch tunnel ports are connected to customer
IEEE 802.1Q trunk ports. Edge-switch access ports are connected to customer access ports. The edge
switches connected to the customer switch perform the tunneling process.
You can enable Layer 2 protocol tunneling on ports that are configured as access ports or tunnel ports.
You cannot enable Layer 2 protocol tunneling on ports configured in either switchport mode dynamic
auto (the default mode) or switchport mode dynamic desirable.
The switch supports Layer 2 protocol tunneling for CDP, STP, and VTP. For emulated point-to-point
network topologies, it also supports PAgP, LACP, and UDLD protocols. The switch does not support
Layer 2 protocol tunneling for LLDP.
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 service-provider inbound edge switch through a Layer 2
protocol-enabled port exit 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 customers 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 or access ports in the same metro VLAN. Therefore, the Layer 2 PDUs
remain intact and are delivered across the service-provider infrastructure to the other side of the
customer network.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
16-10
OL-12189-01
Chapter 16
Configuring IEEE 802.1Q and Layer 2 Protocol Tunneling
Configuring Layer 2 Protocol Tunneling
See Figure 16-4, 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 metro VLAN tag of 40, as well as an inner VLAN tag
(for example, VLAN 100). When the double-tagged packets enter 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 ports on the edge switch connected to access
or trunk ports on the customer switch. In this case, the encapsulation and decapsulation process 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.
In switch stacks, Layer 2 protocol tunneling configuration is distributed among all stack members. Each
stack member that receives an ingress packet on a local port encapsulates or decapsulates the packet and
forwards it to the appropriate destination port. On a single switch, ingress Layer 2 protocol-tunneled
traffic is sent across all local ports in the same VLAN on which Layer 2 protocol tunneling is enabled.
In a stack, packets received by a Layer 2 protocol-tunneled port are distributed to all ports in the stack
that are configured for Layer 2 protocol tunneling and are in the same VLAN. All Layer 2 protocol
tunneling configuration is handled by the stack master and distributed to all stack members.
These sections contain this configuration information:
Default Layer 2 Protocol Tunneling Configuration, page 16-11
Layer 2 Protocol Tunneling Configuration Guidelines, page 16-12
Configuring Layer 2 Protocol Tunneling, page 16-13
Configuring Layer 2 Tunneling for EtherChannels, page 16-14
Default Layer 2 Protocol Tunneling Configuration
Table 16-1 shows the default Layer 2 protocol tunneling configuration.
Table 16-1
Default Layer 2 Ethernet Interface VLAN Configuration
Feature
Default Setting
Layer 2 protocol tunneling
Disabled.
Shutdown threshold
None set.
Drop threshold
None set.
CoS value
If a CoS value is configured on the interface for data packets, that
value is the default used for Layer 2 PDUs. If none is configured,
the default is 5.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
16-11
Chapter 16
Configuring IEEE 802.1Q and Layer 2 Protocol Tunneling
Configuring Layer 2 Protocol Tunneling
Layer 2 Protocol Tunneling Configuration Guidelines
These are some configuration guidelines and operating characteristics of Layer 2 protocol tunneling:
The switch supports tunneling of CDP, STP, including multiple STP (MSTP), and VTP. Protocol
tunneling is disabled by default but can be enabled for the individual protocols on IEEE 802.1Q
tunnel ports or access ports.
The switch does not support Layer 2 protocol tunneling on ports with switchport mode dynamic
auto or dynamic desirable.
DTP is not compatible with layer 2 protocol tunneling.
The edge switches on the outbound side of the service-provider network restore the proper Layer 2
protocol and MAC address information and forward the packets to all tunnel and access 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.
The switch supports PAgP, LACP, and UDLD tunneling for emulated point-to-point network
topologies. Protocol tunneling is disabled by default but can be enabled for the individual protocols
on IEEE 802.1Q tunnel ports or on access ports.
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.
EtherChannel port groups are compatible with tunnel ports when 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 an access port with Layer 2 tunneling enabled, the tunnel 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 a no shutdown command sequence). 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. CDP packets are
not 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 limit BPDU rate 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 it receives them is below the drop threshold.
Because tunneled PDUs (especially STP BPDUs) must be delivered to all remote sites so that the
customer virtual network operates 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
16-12
OL-12189-01
Chapter 16
Configuring IEEE 802.1Q and Layer 2 Protocol Tunneling
Configuring Layer 2 Protocol Tunneling
Configuring Layer 2 Protocol Tunneling
Beginning in privileged EXEC mode, follow these steps to configure a port for Layer 2 protocol
tunneling:
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 can be
physical interfaces and port-channel logical interfaces (port channels 1 to
48).
Step 3
switchport mode access
or
switchport mode dot1q-tunnel
Configure the interface as an access port or an IEEE 802.1Q tunnel port.
Step 4
l2protocol-tunnel [cdp | stp | vtp]
Enable protocol tunneling for the desired protocol. If no keyword is entered,
tunneling is enabled for all three Layer 2 protocols.
Step 5
l2protocol-tunnel
shutdown-threshold [cdp | stp | vtp]
value
(Optional) Configure the threshold for packets-per-second accepted for
encapsulation. The interface is disabled if the configured threshold is
exceeded. If no protocol option is specified, the threshold applies to each of
the tunneled Layer 2 protocol types. The range is 1 to 4096. The default is
to have no threshold configured.
Note
Step 6
l2protocol-tunnel drop-threshold
[cdp | stp | vtp] value
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.
(Optional) Configure the threshold for packets-per-second accepted for
encapsulation. The interface drops packets if the configured threshold is
exceeded. If no protocol option is specified, the threshold applies to each of
the tunneled Layer 2 protocol types. The range is 1 to 4096. The default is
to have no threshold configured.
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
Step 8
errdisable recovery cause l2ptguard (Optional) Configure the recovery mechanism from a Layer 2
maximum-rate error so that the interface is re-enabled and can try again.
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.
Step 11
show l2protocol
Display the Layer 2 tunnel ports on the switch, including the protocols
configured, the thresholds, and the counters.
Step 12
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Return to global configuration mode.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
16-13
Chapter 16
Configuring IEEE 802.1Q and Layer 2 Protocol Tunneling
Configuring Layer 2 Protocol Tunneling
Use the no l2protocol-tunnel [cdp | stp | vtp] interface configuration command to disable protocol
tunneling for one of the Layer 2 protocols or for all three. Use the no l2protocol-tunnel
shutdown-threshold [cdp | stp | vtp] and the no l2protocol-tunnel drop-threshold [cdp | 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/11
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
Port
Protocol Shutdown Drop
Encapsulation Decapsulation
Threshold Threshold Counter
Counter
-------------- --------- --------- ------------- ------------Gi0/11 cdp
1500
1000 2288
2282
0
stp
1500
1000 116
13
vtp
1500
1000 3
67
pagp
------- 0
0
lacp
------- 0
0
udld
------- 0
0
Drop
Counter
------------0
0
0
0
0
Configuring Layer 2 Tunneling for EtherChannels
To configure Layer 2 point-to-point tunneling to facilitate the automatic creation of EtherChannels, you
need to configure both the SP edge switch and the customer switch.
Configuring the SP Edge Switch
Beginning in privileged EXEC mode, follow these steps to configure a SP edge switch for Layer 2
protocol tunneling for EtherChannels:
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 SP 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.
Step 4
l2protocol-tunnel point-to-point
[pagp | lacp | udld]
(Optional) Enable point-to-point protocol tunneling for the desired
protocol. If no keyword is entered, tunneling is enabled for all three
protocols.
Caution
To avoid a network failure, make sure that the network is a
point-to-point topology before you enable tunneling for PAgP,
LACP, or UDLD packets.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
16-14
OL-12189-01
Chapter 16
Configuring IEEE 802.1Q and Layer 2 Protocol Tunneling
Configuring Layer 2 Protocol Tunneling
Step 5
Command
Purpose
l2protocol-tunnel
shutdown-threshold [point-to-point
[pagp | lacp | udld]] value
(Optional) Configure the threshold for packets-per-second accepted for
encapsulation. The interface is disabled if the configured threshold is
exceeded. If no protocol option is specified, the threshold applies to each of
the tunneled Layer 2 protocol types. The range is 1 to 4096. The default is
to have no threshold configured.
Note
Step 6
l2protocol-tunnel drop-threshold
[point-to-point [pagp | lacp | udld]]
value
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.
(Optional) Configure the threshold for packets-per-second accepted for
encapsulation. The interface drops packets if the configured threshold is
exceeded. If no protocol option is specified, the threshold applies 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
no cdp enable
Disable CDP on the interface.
Step 8
spanning-tree bpdufilter enable
Enable BPDU filtering on the interface.
Step 9
exit
Return to global configuration mode.
Step 10
errdisable recovery cause l2ptguard (Optional) Configure the recovery mechanism from a Layer 2
maximum-rate error so that the interface is re-enabled and can try again.
Errdisable recovery is disabled by default; when enabled, the default time
interval is 300 seconds.
Step 11
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 12
end
Return to privileged EXEC mode.
Step 13
show l2protocol
Display the Layer 2 tunnel ports on the switch, including the protocols
configured, the thresholds, and the counters.
Step 14
copy running-config startup-config
(Optional) Save your entries in the configuration file.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
16-15
Chapter 16
Configuring IEEE 802.1Q and Layer 2 Protocol Tunneling
Configuring Layer 2 Protocol Tunneling
Configuring the Customer Switch
After configuring the SP edge switch, begin in privileged EXEC mode and follow these steps to
configure a customer switch for Layer 2 protocol tunneling for EtherChannels:
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
dot1q
Set the trunking encapsulation format to IEEE 802.1Q.
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 37, Configuring EtherChannels and Link-State Tracking.
Step 7
exit
Return to global configuration mode.
Step 8
interface port-channel port-channel
number
Enter port-channel interface mode.
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 Layer 2 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 SP edge switches and the customer switches for
Layer 2 protocol tunneling. (See Figure 16-6 on page 16-10.)
This example shows how to configure the SP edge switch 1 and edge switch 2. VLANs 17, 18, 19, and 20
are the access VLANs, Fast Ethernet interfaces 1 and 2 are point-to-point tunnel ports with PAgP and
UDLD enabled, the drop threshold is 1000, and Fast Ethernet interface 3 is a trunk port.
SP edge switch 1 configuration:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# switchport access vlan 17
Switch(config-if)# switchport mode dot1q-tunnel
Switch(config-if)# l2protocol-tunnel point-to-point
Switch(config-if)# l2protocol-tunnel point-to-point
Switch(config-if)# l2protocol-tunnel drop-threshold
Switch(config-if)# exit
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# switchport access vlan 18
Switch(config-if)# switchport mode dot1q-tunnel
Switch(config-if)# l2protocol-tunnel point-to-point
Switch(config-if)# l2protocol-tunnel point-to-point
pagp
udld
point-to-point pagp 1000
pagp
udld
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
16-16
OL-12189-01
Chapter 16
Configuring IEEE 802.1Q and Layer 2 Protocol Tunneling
Configuring Layer 2 Protocol Tunneling
Switch(config-if)# l2protocol-tunnel drop-threshold point-to-point pagp 1000
Switch(config-if)# exit
Switch(config)# interface gigabitethernet1/0/3
Switch(config-if)# switchport trunk encapsulation isl
Switch(config-if)# switchport mode trunk
SP edge switch 2 configuration:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# switchport access vlan 19
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 gigabitethernet1/0/2
Switch(config-if)# switchport access vlan 20
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 gigabitethernet1/0/3
Switch(config-if)# switchport trunk encapsulation isl
Switch(config-if)# switchport mode trunk
This example shows how to configure the customer switch at Site 1. Fast Ethernet interfaces 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 gigabitethernet1/0/1
Switch(config-if)# switchport trunk encapsulation
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 gigabitethernet1/0/2
Switch(config-if)# switchport trunk encapsulation
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 gigabitethernet1/0/3
Switch(config-if)# switchport trunk encapsulation
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 gigabitethernet1/0/4
Switch(config-if)# switchport trunk encapsulation
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
dot1q
dot1q
dot1q
dot1q
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
16-17
Chapter 16
Configuring IEEE 802.1Q and Layer 2 Protocol Tunneling
Monitoring and Maintaining Tunneling Status
Monitoring and Maintaining Tunneling Status
Table 16-2 shows the privileged EXEC commands for monitoring and maintaining IEEE 802.1Q and
Layer 2 protocol tunneling.
Table 16-2
Commands for Monitoring and Maintaining Tunneling
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 l2protocol-tunnel interface interface-id
Display information about a specific Layer 2 protocol tunneling port.
show l2protocol-tunnel summary
Display only Layer 2 protocol summary information.
show vlan dot1q tag native
Display the status of native VLAN tagging on the switch.
For detailed information about these displays, see the command reference for this release.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
16-18
OL-12189-01
CH A P T E R
17
Configuring STP
This chapter describes how to configure the Spanning Tree Protocol (STP) on port-based VLANs on the
switch. The switch can use either the per-VLAN spanning-tree plus (PVST+) protocol based on the
IEEE 802.1D standard and Cisco proprietary extensions, or the rapid per-VLAN spanning-tree plus
(rapid-PVST+) protocol based on the IEEE 802.1w standard. A switch stack appears as a single
spanning-tree node to the rest of the network, and all stack members use the same bridge ID. Unless
otherwise noted, the term switch refers to a standalone switch and to a switch stack.
For information about the Multiple Spanning Tree Protocol (MSTP) and how to map multiple VLANs
to the same spanning-tree instance, see Chapter 18, Configuring MSTP. For information about other
spanning-tree features such as Port Fast, UplinkFast, root guard, and so forth, see Chapter 19,
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.
This chapter consists of these sections:
Understanding Spanning-Tree Features, page 17-1
Configuring Spanning-Tree Features, page 17-12
Displaying the Spanning-Tree Status, page 17-24
Understanding Spanning-Tree Features
These sections contain this conceptual information:
STP Overview, page 17-2
Spanning-Tree Topology and BPDUs, page 17-3
Bridge ID, Switch Priority, and Extended System ID, page 17-4
Spanning-Tree Interface States, page 17-5
How a Switch or Port Becomes the Root Switch or Root Port, page 17-8
Spanning Tree and Redundant Connectivity, page 17-8
Spanning-Tree Address Management, page 17-9
Accelerated Aging to Retain Connectivity, page 17-9
Spanning-Tree Modes and Protocols, page 17-10
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
17-1
Chapter 17
Configuring STP
Understanding Spanning-Tree Features
Supported Spanning-Tree Instances, page 17-10
Spanning-Tree Interoperability and Backward Compatibility, page 17-11
STP and IEEE 802.1Q Trunks, page 17-11
VLAN-Bridge Spanning Tree, page 17-11 (only the Catalyst Switch Module 3110)
Spanning Tree and Switch Stacks, page 17-12 (only the Catalyst Switch Module 3110)
For configuration information, see the Configuring Spanning-Tree Features section on page 17-12.
For information about optional spanning-tree features, see Chapter 19, Configuring Optional
Spanning-Tree Features.
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:
RootA forwarding port elected for the spanning-tree topology
DesignatedA forwarding port elected for every switched LAN segment
AlternateA blocked port providing an alternate path to the root bridge in the spanning tree
BackupA 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
You can change the default for an interface by entering the [no] keepalive interface configuration
command with no keywords.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
17-2
OL-12189-01
Chapter 17
Configuring STP
Understanding Spanning-Tree Features
Spanning-Tree Topology and BPDUs
The stable, active spanning-tree topology of a switched network is controlled by these elements:
The unique bridge ID (switch priority and MAC address) associated with each VLAN on each
switch. In a switch stack, all switches use the same bridge ID for a given spanning-tree instance.
The spanning-tree path cost to the root switch.
The port identifier (port priority and MAC address) associated with each Layer 2 interface.
When the switches in a network are powered up, each functions as the root switch. Each switch sends a
configuration BPDU through all of its ports. The BPDUs communicate and compute the spanning-tree
topology. Each configuration BPDU contains this information:
The unique bridge ID of the switch that the sending switch identifies as the root switch
The spanning-tree path cost to the root
The bridge ID of the sending switch
Message age
The identifier of the sending interface
Values for the hello, forward delay, and max-age protocol timers
When a switch receives a configuration BPDU that contains superior information (lower bridge ID,
lower path cost, and so forth), it stores the information for that port. If this BPDU is received on the root
port of the switch, the switch also forwards it with an updated message to all attached LANs for which
it is the designated switch.
If a switch receives a configuration BPDU that contains inferior information to that currently stored for
that port, it discards the BPDU. If the switch is a designated switch for the LAN from which the inferior
BPDU was received, it sends that LAN a BPDU containing the up-to-date information stored for that
port. In this way, inferior information is discarded, and superior information is propagated on the
network.
A BPDU exchange results in these actions:
One switch in the network is elected as the root switch (the logical center of the spanning-tree
topology in a switched network). In a switch stack, one stack member is elected as the stack root
switch. The stack root switch contains the outgoing root port (Switch 1), as shown in Figure 17-1
on page 17-4.
For each VLAN, the switch with the highest switch priority (the lowest numerical priority value) is
elected as the root switch. If all switches are configured with the default priority (32768), the switch
with the lowest MAC address in the VLAN becomes the root switch. The switch priority value
occupies the most significant bits of the bridge ID, as shown in Table 17-1 on page 17-5.
A root port is selected for each switch (except the root switch). This port provides the best path
(lowest cost) when the switch forwards packets to the root switch.
When selecting the root port on a switch stack, spanning tree follows this sequence:
Selects the lowest root bridge ID
Selects the lowest path cost to the root switch
Selects the lowest designated bridge ID
Selects the lowest designated path cost
Selects the lowest port ID
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
17-3
Chapter 17
Configuring STP
Understanding Spanning-Tree Features
Only one outgoing port on the stack root switch is selected as the root port. The remaining switches
in the stack become its designated switches (Switch 2 and Switch 3) as shown in Figure 17-1.
The shortest distance to the root switch is calculated for each switch based on the path cost.
A designated switch for each LAN segment is selected. The designated switch incurs the lowest path
cost when forwarding packets from that LAN to the root switch. The port through which the
designated switch is attached to the LAN is called the designated port.
Figure 17-1
Spanning-Tree Port States in a Switch Stack
Blade switch stack
Outgoing RP
Switch 1
DP
BP
DP
Spanning-tree root
Switch A
Switch 2
DP
RP
Switch 3
RP = root port
DP = designated port
BP = blocked port
Switch B
201768
StackWise Plus
port
connections
All paths that are not needed to reach the root switch from anywhere in the switched network are placed
in the spanning-tree blocking mode.
Bridge ID, Switch Priority, and Extended System ID
The IEEE 802.1D standard requires that each switch has an unique bridge identifier (bridge ID), which
controls the selection of the root switch. Because each VLAN is considered as a different logical bridge
with PVST+ and rapid PVST+, the same switch must have a different bridge IDs for each configured
VLAN. Each VLAN on the switch has a unique 8-byte bridge ID. The 2 most-significant bytes are used
for the switch priority, and the remaining 6 bytes are derived from the switch MAC address.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
17-4
OL-12189-01
Chapter 17
Configuring STP
Understanding Spanning-Tree Features
The switch supports the IEEE 802.1t spanning-tree extensions, and some of the bits previously used for
the switch priority are now used as the VLAN identifier. The result is that fewer MAC addresses are
reserved for the switch, and a larger range of VLAN IDs can be supported, all while maintaining the
uniqueness of the bridge ID. As shown in Table 17-1, the 2 bytes previously used for the switch priority
are reallocated into a 4-bit priority value and a 12-bit extended system ID value equal to the VLAN ID.
Table 17-1
Switch Priority Value and Extended System ID
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
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. Because the switch stack appears as a single
switch to the rest of the network, all switches in the stack use the same bridge ID for a given spanning
tree. If the stack master fails, the stack members recalculate their bridge IDs of all running spanning trees
based on the new MAC address of the new stack master.
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 17-16, the Configuring a Secondary Root Switch
section on page 17-18, and the Configuring the Switch Priority of a VLAN section on page 17-21.
Spanning-Tree Interface States
Propagation delays can occur when protocol information passes through a switched LAN. As a result,
topology changes can take place at different times and at different places in a switched network. When
an interface transitions directly from nonparticipation in the spanning-tree topology to the forwarding
state, it can create temporary data loops. Interfaces must wait for new topology information to propagate
through the switched LAN before starting to forward frames. They must allow the frame lifetime to
expire for forwarded frames that have used the old topology.
Each Layer 2 interface on a switch using spanning tree exists in one of these states:
BlockingThe interface does not participate in frame forwarding.
ListeningThe first transitional state after the blocking state when the spanning tree decides that
the interface should participate in frame forwarding.
LearningThe interface prepares to participate in frame forwarding.
ForwardingThe interface forwards frames.
DisabledThe interface is not participating in spanning tree because of a shutdown port, no link on
the port, or no spanning-tree instance running on the port.
An interface moves through these states:
From initialization to blocking
From blocking to listening or to disabled
From listening to learning or to disabled
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
17-5
Chapter 17
Configuring STP
Understanding Spanning-Tree Features
From learning to forwarding or to disabled
From forwarding to disabled
Figure 17-2 illustrates how an interface moves through the states.
Figure 17-2
Spanning-Tree Interface States
Power-on
initialization
Blocking
state
Listening
state
Disabled
state
Forwarding
state
43569
Learning
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 move 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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
17-6
OL-12189-01
Chapter 17
Configuring STP
Understanding Spanning-Tree Features
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 decides 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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
17-7
Chapter 17
Configuring STP
Understanding Spanning-Tree Features
How a Switch or Port Becomes the Root Switch or Root Port
If all switches in a network are enabled with default spanning-tree settings, the switch with the lowest
MAC address becomes the root switch. In Figure 17-3, Switch A is elected as the root switch because
the switch priority of all the switches is set to the default (32768) and Switch A has the lowest MAC
address. However, because of traffic patterns, number of forwarding interfaces, or link types, Switch A
might not be the ideal root switch. By increasing the priority (lowering the numerical value) of the ideal
switch so that it becomes the root switch, you force a spanning-tree recalculation to form a new topology
with the ideal switch as the root.
Figure 17-3
Spanning-Tree Topology
DP
A
DP
D
RP
DP
RP
B
DP
RP
C
86475
DP
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.
Spanning Tree and Redundant Connectivity
You can create a redundant backbone with spanning tree by connecting two switch interfaces to another
device or to two different devices, as shown in Figure 17-4. Spanning tree automatically disables one
interface but enables it if the other one fails. If one link is high-speed and the other is low-speed, the
low-speed link is always disabled. If the speeds are the same, the port priority and port ID are added
together, and spanning tree disables the link with the lowest value.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
17-8
OL-12189-01
Chapter 17
Configuring STP
Understanding Spanning-Tree Features
Spanning Tree and Redundant Connectivity
Active link
Blocked link
Blade servers
201769
Figure 17-4
You can also create redundant links between switches by using EtherChannel groups. For more
information, see Chapter 37, Configuring EtherChannels and Link-State Tracking.
Spanning-Tree Address Management
IEEE 802.1D specifies 17 multicast addresses, ranging from 0x00180C2000000 to 0x0180C2000010, to
be used by different bridge protocols. These addresses are static addresses that cannot be removed.
Regardless of the spanning-tree state, each switch in the stack receives but does not forward packets
destined for addresses between 0x0180C2000000 and 0x0180C200000F.
If spanning tree is enabled, the CPU on the switch or on each switch in the stack receives packets
destined for 0x0180C2000000 and 0x0180C2000010. If spanning tree is disabled, the switch or each
switch in the stack forwards those packets as unknown multicast addresses.
Accelerated Aging to Retain Connectivity
The default for aging dynamic addresses is 5 minutes, the default setting of the mac address-table
aging-time global configuration command. However, a spanning-tree reconfiguration can cause many
station locations to change. Because these stations could be unreachable for 5 minutes or more during a
reconfiguration, the address-aging time is accelerated so that station addresses can be dropped from the
address table and then relearned. The accelerated aging is the same as the forward-delay parameter value
(spanning-tree vlan vlan-id forward-time seconds global configuration command) when the spanning
tree reconfigures.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
17-9
Chapter 17
Configuring STP
Understanding Spanning-Tree Features
Spanning-Tree Modes and Protocols
The switch supports these spanning-tree modes and protocols:
PVST+This spanning-tree mode is based on the IEEE 802.1D standard and Cisco proprietary
extensions. It is the default spanning-tree mode used on all Ethernet port-based VLANs. The PVST+
runs on each VLAN on the switch up to the maximum supported, ensuring that each has a loop-free
path through the network.
The PVST+ provides Layer 2 load-balancing for the VLAN on which it runs. You can create
different logical topologies by using the VLANs on your network to ensure that all of your links are
used but that no one link is oversubscribed. Each instance of PVST+ on a VLAN has a single root
switch. This root switch propagates the spanning-tree information associated with that VLAN to all
other switches in the network. Because each switch has the same information about the network, this
process ensures that the network topology is maintained.
Rapid PVST+This spanning-tree mode is the same as PVST+ except that is uses a rapid
convergence based on the IEEE 802.1w standard. To provide rapid convergence, the rapid PVST+
immediately deletes dynamically learned MAC address entries on a per-port basis upon receiving a
topology change. By contrast, PVST+ uses a short aging time for dynamically learned MAC address
entries.
The rapid PVST+ uses the same configuration as PVST+ (except where noted), and the switch needs
only minimal extra configuration. The benefit of rapid PVST+ is that you can migrate a large PVST+
install base to rapid PVST+ without having to learn the complexities of the MSTP configuration and
without having to reprovision your network. In rapid-PVST+ mode, each VLAN runs its own
spanning-tree instance up to the maximum supported.
MSTPThis spanning-tree mode is based on the IEEE 802.1s standard. You can map multiple
VLANs to the same spanning-tree instance, which reduces the number of spanning-tree instances
required to support a large number of VLANs. The MSTP runs on top of the RSTP (based on
IEEE 802.1w), which provides for rapid convergence of the spanning tree by eliminating the
forward delay and by quickly transitioning root ports and designated ports to the forwarding state.
In a switch stack, the cross-stack rapid transition (CSRT) feature performs the same function as
RSTP. You cannot run MSTP without RSTP or CSRT.
The most common initial deployment of MSTP is in the backbone and distribution layers of a
Layer 2 switched network. For more information, see Chapter 18, Configuring MSTP.
For information about the number of supported spanning-tree instances, see the next section.
Supported Spanning-Tree Instances
In PVST+ or rapid-PVST+ mode, the switch or switch stack supports up to 128 spanning-tree instances.
In MSTP mode, the switch or switch stack supports up to 65 MST instances. The number of VLANs that
can be mapped to a particular MST instance is unlimited.
For information about how spanning tree interoperates with the VLAN Trunking Protocol (VTP), see the
Spanning-Tree Configuration Guidelines section on page 17-13.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
17-10
OL-12189-01
Chapter 17
Configuring STP
Understanding Spanning-Tree Features
Spanning-Tree Interoperability and Backward Compatibility
Table 17-2 lists the interoperability and compatibility among the supported spanning-tree modes in a
network.
Table 17-2
PVST+, MSTP, and Rapid-PVST+ Interoperability
PVST+
MSTP
Rapid PVST+
PVST+
Yes
Yes (with restrictions)
Yes (reverts to PVST+)
MSTP
Yes (with restrictions)
Yes
Yes (reverts to PVST+)
Rapid PVST+
Yes (reverts to PVST+)
Yes (reverts to PVST+)
Yes
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.
All stack members run the same version of spanning tree (all PVST+, all rapid PVST+, or all MSTP).
STP and IEEE 802.1Q Trunks
The IEEE 802.1Q standard for VLAN trunks imposes some limitations on the spanning-tree strategy for
a network. The standard requires only one spanning-tree instance for all VLANs allowed on the trunks.
However, in a network of Cisco switches connected through IEEE 802.1Q trunks, the switches maintain
one spanning-tree instance for each VLAN allowed on the trunks.
When you connect a Cisco switch to a non-Cisco device through an IEEE 802.1Q trunk, the Cisco switch
uses PVST+ to provide spanning-tree interoperability. If rapid PVST+ is enabled, the switch uses it
instead of PVST+. The switch combines the spanning-tree instance of the IEEE 802.1Q VLAN of the
trunk with the spanning-tree instance of the non-Cisco IEEE 802.1Q switch.
However, all PVST+ or rapid-PVST+ information is maintained by Cisco switches separated by a cloud
of non-Cisco IEEE 802.1Q switches. The non-Cisco IEEE 802.1Q cloud separating the Cisco switches
is treated as a single trunk link between the switches.
PVST+ is automatically enabled on IEEE 802.1Q trunks, and no user configuration is required. The
external spanning-tree behavior on access ports and Inter-Switch Link (ISL) trunk ports is not affected
by PVST+.
For more information on IEEE 802.1Q trunks, see Chapter 12, Configuring VLANs.
VLAN-Bridge Spanning Tree
This feature is only supported on the Catalyst Switch Module 3110.
Cisco VLAN-bridge spanning tree is used with the fallback bridging feature (bridge groups), which
forwards non-IP protocols such as DECnet between two or more VLAN bridge domains or routed ports.
The VLAN-bridge spanning tree allows the bridge groups to form a spanning tree on top of the individual
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
17-11
Chapter 17
Configuring STP
Configuring Spanning-Tree Features
VLAN spanning trees to prevent loops from forming if there are multiple connections among VLANs.
It also prevents the individual spanning trees from the VLANs being bridged from collapsing into a
single spanning tree.
To support VLAN-bridge spanning tree, some of the spanning-tree timers are increased. To use the
fallback bridging feature, you must have the IP services feature set enabled on your switch. For more
information, see Chapter 46, Configuring Fallback Bridging.
Spanning Tree and Switch Stacks
This feature is only supported on the Catalyst Switch Module 3110.
These statements are true when the switch stack is operating in PVST+ or rapid-PVST+ mode:
A switch stack appears as a single spanning-tree node to the rest of the network, and all stack
members use the same bridge ID for a given spanning tree. The bridge ID is derived from the MAC
address of the stack master.
When a new switch joins the stack, it sets its bridge ID to the stack-master bridge ID. If the newly
added switch has the lowest ID and if the root path cost is the same among all stack members, the
newly added switch becomes the stack root.
When a stack member leaves the stack, spanning-tree reconvergence occurs within the stack (and
possibly outside the stack). The remaining stack member with the lowest stack port ID becomes the
stack root.
If the stack master fails or leaves the stack, the stack members elect a new stack master, and all stack
members change their bridge IDs of the spanning trees to the new master bridge ID.
If the switch stack is the spanning-tree root and the stack master fails or leaves the stack, the stack
members elect a new stack master, and a spanning-tree reconvergence occurs.
If a neighboring switch external to the switch stack fails or is powered down, normal spanning-tree
processing occurs. Spanning-tree reconvergence might occur as a result of losing a switch in the
active topology.
If a new switch external to the switch stack is added to the network, normal spanning-tree processing
occurs. Spanning-tree reconvergence might occur as a result of adding a switch in the network.
For more information about switch stacks, see Chapter 5, Managing Switch Stacks.
Configuring Spanning-Tree Features
These sections contain this configuration information:
Default Spanning-Tree Configuration, page 17-13
Spanning-Tree Configuration Guidelines, page 17-13
Changing the Spanning-Tree Mode., page 17-15 (required)
Disabling Spanning Tree, page 17-16 (optional)
Configuring the Root Switch, page 17-16 (optional)
Configuring a Secondary Root Switch, page 17-18 (optional)
Configuring Port Priority, page 17-18 (optional)
Configuring Path Cost, page 17-20 (optional)
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
17-12
OL-12189-01
Chapter 17
Configuring STP
Configuring Spanning-Tree Features
Configuring the Switch Priority of a VLAN, page 17-21 (optional)
Configuring Spanning-Tree Timers, page 17-22 (optional)
Default Spanning-Tree Configuration
Table 17-3 shows the default spanning-tree configuration.
Table 17-3
Default Spanning-Tree Configuration
Feature
Default Setting
Enable state
Enabled on VLAN 1.
For more information, see the Supported
Spanning-Tree Instances section on
page 17-10.
Spanning-tree mode
PVST+. (Rapid PVST+ and MSTP are
disabled.)
Switch priority
32768.
Spanning-tree port priority (configurable on a per-interface basis)
128.
Spanning-tree port cost (configurable on a per-interface basis)
1000 Mb/s: 4.
100 Mb/s: 19.
10 Mb/s: 100.
Spanning-tree VLAN port priority (configurable on a per-VLAN basis)
128.
Spanning-tree VLAN port cost (configurable on a per-VLAN basis)
1000 Mb/s: 4.
100 Mb/s: 19.
10 Mb/s: 100.
Spanning-tree timers
Hello time: 2 seconds.
Forward-delay time: 15 seconds.
Maximum-aging time: 20 seconds.
Transmit hold count: 6 BPDUs
Spanning-Tree Configuration Guidelines
Each stack member runs its own spanning tree, and the entire stack appears as a single switch to the rest
of the network.
If more VLANs are defined in the VTP than there are spanning-tree instances, you can enable PVST+
or rapid PVST+ on only 128 VLANs on the switch or each switch stack. The remaining VLANs operate
with spanning tree disabled. However, you can map multiple VLANs to the same spanning-tree instances
by using MSTP. For more information, see Chapter 18, Configuring MSTP.
If 128 instances of spanning tree are already in use, you can disable spanning tree on one of the VLANs
and then enable it on the VLAN where you want it to run. Use the no spanning-tree vlan vlan-id global
configuration command to disable spanning tree on a specific VLAN, and use the spanning-tree vlan
vlan-id global configuration command to enable spanning tree on the desired VLAN.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
17-13
Chapter 17
Configuring STP
Configuring Spanning-Tree Features
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 17-11.
For configuration guidelines about UplinkFast, BackboneFast, and cross-stack UplinkFast, see the
Optional Spanning-Tree Configuration Guidelines section on page 19-12.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
17-14
OL-12189-01
Chapter 17
Configuring STP
Configuring Spanning-Tree Features
Changing the Spanning-Tree Mode.
The switch supports three spanning-tree modes: PVST+, rapid PVST+, or MSTP. By default, the switch
runs the PVST+ protocol.
Beginning in privileged EXEC mode, follow these steps to change the spanning-tree mode. If you want
to enable a mode that is different from the default mode, this procedure is required.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
spanning-tree mode {pvst | mst |
rapid-pvst}
Configure a spanning-tree mode. All stack members run the same
version of spanning-tree.
Select pvst to enable PVST+ (the default setting).
Select mst to enable MSTP (and RSTP). For more configuration
steps, see Chapter 18, 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 48.
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 changes 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 IEEE 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
17-15
Chapter 17
Configuring STP
Configuring Spanning-Tree Features
Disabling Spanning Tree
Spanning tree is enabled by default on VLAN 1 and on all newly created VLANs up to the spanning-tree
limit specified in the Supported Spanning-Tree Instances section on page 17-10. Disable spanning tree
only if you are sure there are no loops in the network topology.
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.
Configuring the Root Switch
The switch maintains a separate spanning-tree instance for each active VLAN configured on it. A bridge
ID, consisting of the switch priority and the switch MAC address, is associated with each instance. For
each VLAN, the switch with the lowest bridge ID becomes the root switch for that VLAN.
To configure a switch to become the root for the specified VLAN, use the spanning-tree vlan vlan-id
root global configuration command to modify the switch priority from the default value (32768) to a
significantly lower value. When you enter this command, the software checks the switch priority of the
root switches for each VLAN. Because of the extended system ID support, the switch sets its own
priority for the specified VLAN to 24576 if this value will cause this switch to become the root for the
specified VLAN.
If any root switch for the specified VLAN has a switch priority lower than 24576, the switch sets its own
priority for the specified VLAN to 4096 less than the lowest switch priority. (4096 is the value of the
least-significant bit of a 4-bit switch priority value as shown in Table 17-1 on page 17-5.)
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
17-16
OL-12189-01
Chapter 17
Configuring STP
Configuring Spanning-Tree Features
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
[diameter net-diameter [hello-time seconds]]
Configure a switch to become the root for the specified 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.
(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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
17-17
Chapter 17
Configuring STP
Configuring Spanning-Tree Features
Configuring a Secondary Root Switch
When you configure a switch as the secondary root, the switch priority is modified from the default value
(32768) to 28672. The switch is then likely to become the root switch for the specified VLAN if the
primary root switch fails. This is assuming that the other network switches use the default switch priority
of 32768 and therefore are unlikely to become the root switch.
You can execute this command on more than one switch to configure multiple backup root switches. Use
the same network diameter and hello-time values that you used when you configured the primary root
switch with the spanning-tree vlan vlan-id root primary global configuration command.
Beginning in privileged EXEC mode, follow these steps to configure a switch to become the secondary
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 secondary
[diameter net-diameter [hello-time
seconds]]
Configure a switch to become the secondary root for the specified
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.
(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 17-16.
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.
Configuring Port Priority
If a loop occurs, spanning tree uses the port priority when selecting an interface to put into the
forwarding state. You can assign higher priority values (lower numerical values) to interfaces that you
want selected first and lower priority values (higher numerical values) that you want selected last. If all
interfaces have the same priority value, spanning tree puts the interface with the lowest interface number
in the forwarding state and blocks the other interfaces.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
17-18
OL-12189-01
Chapter 17
Configuring STP
Configuring Spanning-Tree Features
Note
If your switch is a member of a switch stack, you must use the spanning-tree [vlan vlan-id] cost cost
interface configuration command instead of the spanning-tree [vlan vlan-id] port-priority priority
interface configuration command to select an interface to put in the forwarding state. Assign lower cost
values to interfaces that you want selected first and higher cost values that you want selected last. For
more information, see the Configuring Path Cost section on page 17-20.
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
Note
(Optional) Save your entries in the configuration file.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
17-19
Chapter 17
Configuring STP
Configuring Spanning-Tree Features
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 12-24.
Configuring Path Cost
The spanning-tree path cost default value is derived from the media speed of an interface. If a loop
occurs, spanning tree uses cost when selecting an interface to put in the forwarding state. You can assign
lower cost values to interfaces that you want selected first and higher cost values that you want selected
last. If all interfaces have the same cost value, spanning tree puts the interface with the lowest interface
number in the forwarding state and blocks the other interfaces.
Beginning in privileged EXEC mode, follow these steps to configure the cost 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 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
17-20
OL-12189-01
Chapter 17
Configuring STP
Configuring Spanning-Tree Features
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 12-24.
Configuring the Switch Priority of a VLAN
You can configure the switch priority and make it more likely that a standalone switch or a switch in the
stack will be chosen as the root switch.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
17-21
Chapter 17
Configuring STP
Configuring Spanning-Tree Features
Configuring Spanning-Tree Timers
Table 17-4 describes the timers that affect the entire spanning-tree performance.
Table 17-4
Spanning-Tree Timers
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.
Transmit hold count
Controls the number of BPDUs that can be sent before pausing for 1 second.
The sections that follow provide the configuration steps.
Configuring the Hello Time
You can configure the interval between the generation of configuration messages by the root switch by
changing the hello time.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
17-22
OL-12189-01
Chapter 17
Configuring STP
Configuring Spanning-Tree Features
Configuring the Forwarding-Delay Time for a VLAN
Beginning in privileged EXEC mode, follow these steps to configure the forwarding-delay time for a
VLAN. This procedure is optional.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
spanning-tree vlan vlan-id forward-time
seconds
Configure the forward time of a VLAN. The forward delay is the
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.
Configuring the Maximum-Aging Time for a VLAN
Beginning in privileged EXEC mode, follow these steps to configure the maximum-aging time for a
VLAN. This procedure is optional.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
17-23
Chapter 17
Configuring STP
Displaying the Spanning-Tree Status
Configuring the Transmit Hold-Count
You can configure the BPDU burst size by changing the transmit hold count value.
Note
Changing this parameter to a higher value can have a significant impact on CPU utilization, especially
in Rapid-PVST mode. Lowering this value can slow down convergence in certain scenarios. We
recommend that you maintain the default setting.
Beginning in privileged EXEC mode, follow these steps to configure the transmit hold-count. This
procedure is optional.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
spanning-tree transmit hold-count value
Configure the number of BPDUs that can be sent before pausing
for 1 second.
For value, the range is 1 to 20; the default is 6.
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 transmit hold-count value global
configuration command.
Displaying the Spanning-Tree Status
To display the spanning-tree status, use one or more of the privileged EXEC commands in Table 17-5:
Table 17-5
Commands for Displaying Spanning-Tree Status
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
17-24
OL-12189-01
CH A P T E R
18
Configuring MSTP
This chapter describes how to configure the Cisco implementation of the IEEE 802.1s
Multiple STP (MSTP) on the switch.
Note
The multiple spanning-tree (MST) implementation is based on the IEEE 802.1s standard.
The MSTP enables multiple VLANs to be mapped to the same spanning-tree instance, 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 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) IEEE 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 17, Configuring STP. For information about other spanning-tree features such as Port Fast,
UplinkFast, root guard, and so forth, see Chapter 19, Configuring Optional Spanning-Tree Features.
A switch stack appears as a single spanning-tree node to the rest of the network, and all stack members
use the same switch ID. Unless otherwise noted, the term switch refers to a standalone switch and to a
switch stack.
Note
For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
This chapter consists of these sections:
Understanding MSTP, page 18-2
Understanding RSTP, page 18-9
Configuring MSTP Features, page 18-14
Displaying the MST Configuration and Status, page 18-26
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
18-1
Chapter 18
Configuring MSTP
Understanding MSTP
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 18-2
IST, CIST, and CST, page 18-2
Hop Count, page 18-5
Boundary Ports, page 18-6
IEEE 802.1s Implementation, page 18-6
MSTP and Switch Stacks, page 18-8
Interoperability with IEEE 802.1D STP, page 18-8
For configuration information, see the Configuring MSTP Features section on page 18-14.
Multiple Spanning-Tree Regions
For switches to participate in multiple spanning-tree (MST) instances, you must consistently configure
the switches with the same MST configuration information. A collection of interconnected switches that
have the same MST configuration comprises an MST region as shown in Figure 18-1 on page 18-4.
The MST configuration controls to which MST region each switch belongs. The configuration includes
the name of the region, the revision number, and the MST VLAN-to-instance assignment map. You
configure the switch for a region by using the spanning-tree mst configuration global configuration
command, after which the switch enters the MST configuration mode. From this mode, you can map
VLANs to an MST instance by using the instance MST configuration command, specify the region name
by using the name MST configuration command, and set the revision number by using the revision MST
configuration command.
A region can have one or multiple members with the same MST configuration. Each member must be
capable of processing RSTP bridge protocol data units (BPDUs). There is no limit to the number of MST
regions in a network, but each region can support up to 65 spanning-tree instances. Instances can be
identified by any number in the range from 0 to 4094. You can assign a VLAN to only one spanning-tree
instance at a time.
IST, CIST, and CST
Unlike PVST+ and rapid PVST+ in which all the spanning-tree instances are independent, the MSTP
establishes and maintains two types of spanning trees:
An internal spanning tree (IST), which is the spanning tree that runs in an MST region.
Within each MST region, the MSTP maintains multiple spanning-tree instances. Instance 0 is a
special instance for a region, known as the internal spanning tree (IST). All other MST instances are
numbered from 1 to 4094.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
18-2
OL-12189-01
Chapter 18
Configuring MSTP
Understanding MSTP
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 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 by the spanning-tree algorithm running among switches that
support the IEEE 802.1w, IEEE 802.1s, and IEEE 802.1D standards. 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 18-3 and the
Operations Between MST Regions section on page 18-3.
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.
Operations Within an MST Region
The IST connects all the MSTP switches in a region. When the IST converges, the root of the IST
becomes the CIST regional root (called the IST master before the implementation of the IEEE 802.1s
standard) as shown in Figure 18-1 on page 18-4. It is the switch within the region with the lowest switch
ID and path cost to the CIST root. The CIST regional root is also the CIST root if there is only one region
in the network. If the CIST root is outside the region, one of the MSTP switches at the boundary of the
region is selected as the CIST regional root.
When an MSTP switch initializes, it sends BPDUs claiming itself as the root of the CIST and the CIST
regional root, with both of the path costs to the CIST root and to the CIST regional root set to zero. The
switch also initializes all of its MST instances and claims to be the root for all of them. If the switch
receives superior MST root information (lower switch ID, lower path cost, and so forth) than currently
stored for the port, it relinquishes its claim as the CIST regional root.
During initialization, a region might have many subregions, each with its own CIST regional root. As
switches receive superior IST information, they leave their old subregions and join the new subregion
that contains the true CIST regional root. Thus all subregions shrink, except for the one that contains the
true CIST regional root.
For correct operation, all switches in the MST region must agree on the same CIST regional root.
Therefore, any two switches in the region only synchronize their port roles for an MST instance if they
converge to a common CIST regional root.
Operations Between MST Regions
If there are multiple regions or legacy IEEE 802.1D switches within the network, MSTP establishes and
maintains the CST, which includes all MST regions and all legacy STP switches in the network. The
MST instances combine with the IST at the boundary of the region to become the CST.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
18-3
Chapter 18
Configuring MSTP
Understanding MSTP
The IST connects all the MSTP switches in the region and appears as a subtree in the CIST that
encompasses the entire switched domain. The root of the subtree is the CIST regional root. The MST
region appears as a virtual switch to adjacent STP switches and MST regions.
Figure 18-1 shows a network with three MST regions and a legacy IEEE 802.1D switch (D). The CIST
regional root for region 1 (A) is also the CIST root. The CIST regional root for region 2 (B) and the CIST
regional root for region 3 (C) are the roots for their respective subtrees within the CIST. The RSTP runs
in all regions.
Figure 18-1
MST Regions, CIST Masters, and CST Root
A IST master
and CST root
D
Legacy IEEE 802.1D
MST Region 1
IST master
MST Region 2
IST master
MST Region 3
92983
Only the CST instance sends and receives BPDUs, and MST instances add their spanning-tree
information into the BPDUs to interact with neighboring switches and compute the final spanning-tree
topology. Because of this, the spanning-tree parameters related to BPDU transmission (for example,
hello time, forward time, max-age, and max-hops) are configured only on the CST instance but affect all
MST instances. Parameters related to the spanning-tree topology (for example, switch priority, port
VLAN cost, and port VLAN priority) can be configured on both the CST instance and the MST instance.
MSTP switches use Version 3 RSTP BPDUs or IEEE 802.1D STP BPDUs to communicate with legacy
IEEE 802.1D switches. MSTP switches use MSTP BPDUs to communicate with MSTP switches.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
18-4
OL-12189-01
Chapter 18
Configuring MSTP
Understanding MSTP
IEEE 802.1s Terminology
Some MST naming conventions used in Ciscos prestandard implementation have been changed to
identify some internal or regional parameters. These parameters are significant only within an MST
region, as opposed to external parameters that are relevant to the whole network. Because the CIST is
the only spanning-tree instance that spans the whole network, only the CIST parameters require the
external rather than the internal or regional qualifiers.
The CIST root is the root switch for the unique instance that spans the whole network, the CIST.
The CIST external root path cost is the cost to the CIST root. This cost is left unchanged within an
MST region. Remember that an MST region looks like a single switch for the CIST. The CIST
external root path cost is the root path cost calculated between these virtual switches and switches
that do not belong to any region.
The CIST regional root was called the IST master in the prestandard implementation. If the CIST
root is in the region, the CIST regional root is the CIST root. Otherwise, the CIST regional root is
the closest switch to the CIST root in the region. The CIST regional root acts as a root switch for
the IST.
The CIST internal root path cost is the cost to the CIST regional root in a region. This cost is only
relevant to the IST, instance 0.
Table 18-1 compares the IEEE standard and the Cisco prestandard terminology.
Table 18-1
Prestandard and Standard Terminology
IEEE Standard
Cisco Prestandard
Cisco Standard
CIST regional root
IST master
CIST regional root
CIST internal root path cost
IST master path cost
CIST internal path cost
CIST external root path cost
Root path cost
Root path cost
MSTI regional root
Instance root
Instance root
MSTI internal root path cost
Root path cost
Root path cost
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 (triggers 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 designated ports at the
boundary.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
18-5
Chapter 18
Configuring MSTP
Understanding MSTP
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.
IEEE 802.1s Implementation
The Cisco implementation of the IEEE MST standard includes features required to meet the standard, as
well as some of the desirable prestandard functionality that is not yet incorporated into the published
standard.
Port Role Naming Change
The boundary role is no longer in the final MST standard, but this boundary concept is maintained in
Ciscos implementation. However, an MST instance port at a boundary of the region might not follow
the state of the corresponding CIST port. Two cases exist now:
The boundary port is the root port of the CIST regional rootWhen the CIST instance port is
proposed and is in sync, it can send back an agreement and move to the forwarding state only after
all the corresponding MSTI ports are in sync (and thus forwarding). The MSTI ports now have a
special master role.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
18-6
OL-12189-01
Chapter 18
Configuring MSTP
Understanding MSTP
The boundary port is not the root port of the CIST regional rootThe MSTI ports follow the state
and role of the CIST port. The standard provides less information, and it might be difficult to
understand why an MSTI port can be alternately blocking when it receives no BPDUs (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.
Interoperation Between Legacy and Standard Switches
Because automatic detection of prestandard switches can fail, you can use an interface configuration
command to identify prestandard ports. A region cannot be formed between a standard and a prestandard
switch, but they can interoperate by using the CIST. Only the capability of load-balancing over different
instances is lost in that particular case. The CLI displays different flags depending on the port
configuration when a port receives prestandard BPDUs. A syslog message also appears the first time a
switch receives a prestandard BPDU on a port that has not been configured for prestandard BPDU
transmission.
Figure 18-2 illustrates this scenario. Assume that A is a standard switch and B a prestandard switch, both
configured to be in the same region. A is the root switch for the CIST, and thus B has a root port (BX)
on segment X and an alternate port (BY) on segment Y. If segment Y flaps, and the port on BY becomes
the alternate before sending out a single prestandard BPDU, AY cannot detect that a prestandard switch
is connected to Y and continues to send standard BPDUs. The port BY is thus fixed in a boundary, and
no load-balancing is possible between A and B. The same problem exists on segment X, but B might
transmit topology changes.
Figure 18-2
Standard and Prestandard Switch Interoperation
Segment X
MST
Region
Switch A
Segment Y
Note
92721
Switch B
We recommend that you minimize the interaction between standard and prestandard MST
implementations.
Detecting Unidirectional Link Failure
This feature is not yet present in the IEEE MST standard, but it is included in this Cisco IOS release.
The software checks the consistency of the port role and state in the received BPDUs to detect
unidirectional link failures that could cause bridging loops.
When a designated port detects a conflict, it keeps its role, but reverts to discarding state because
disrupting connectivity in case of inconsistency is preferable to opening a bridging loop.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
18-7
Chapter 18
Configuring MSTP
Understanding MSTP
Figure 18-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.
Switch
A
Detecting Unidirectional Link Failure
Superior
BPDU
Inferior BPDU,
Designated + Learning bit set
Switch
B
92722
Figure 18-3
MSTP and Switch Stacks
A switch stack appears as a single spanning-tree node to the rest of the network, and all stack members
use the same switch ID for a given spanning tree. The switch ID is derived from the MAC address of the
stack master.
If a switch that does not support MSTP is added to a switch stack that does support MSTP or the reverse,
the switch is put into a version mismatch state. If possible, the switch is automatically upgraded or
downgraded to the same version of software that is running on the switch stack.
When a new switch joins the stack, it sets its switch ID to the stack master switch ID. If the newly added
switch has the lowest ID and if the root path cost is the same among all stack members, the newly added
switch becomes the stack root. A topology change occurs if the newly added switch contains a better
root port for the switch stack or a better designated port for the LAN connected to the stack. The newly
added switch causes a topology change in the network if another switch connected to the newly added
switch changes its root port or designated ports.
When a stack member leaves the stack, spanning-tree reconvergence occurs within the stack (and
possibly outside the stack). The remaining stack member with the lowest stack port ID becomes the stack
root.
If the stack master fails or leaves the stack, the stack members elect a new stack master, and all stack
members change their switch IDs of the spanning trees to the new master switch ID.
For more information about switch stacks, see Chapter 5, Managing Switch Stacks.
Interoperability with IEEE 802.1D STP
A switch running MSTP supports a built-in protocol migration mechanism that enables it to interoperate
with legacy IEEE 802.1D switches. If this switch receives a legacy IEEE 802.1D configuration BPDU
(a BPDU with the protocol version set to 0), it sends only IEEE 802.1D BPDUs on that port. An MSTP
switch also can detect that a port is at the boundary of a region when it receives a legacy BPDU, an MSTP
BPDU (Version 3) associated with a different region, or an RSTP BPDU (Version 2).
However, the switch does not automatically revert to the MSTP mode if it no longer receives
IEEE 802.1D BPDUs because it cannot detect whether the legacy switch has been removed from the link
unless the legacy switch is the designated switch. A switch might also continue to assign a boundary role
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
18-8
OL-12189-01
Chapter 18
Configuring MSTP
Understanding RSTP
to a port when the switch to which this switch is connected has joined the region. To restart the protocol
migration process (force the renegotiation with neighboring switches), use the clear spanning-tree
detected-protocols privileged EXEC command.
If all the legacy switches on the link are RSTP switches, they can process MSTP BPDUs as if they are
RSTP BPDUs. Therefore, MSTP switches send either a Version 0 configuration and TCN BPDUs or
Version 3 MSTP BPDUs on a boundary port. A boundary port connects to a LAN, the designated switch
of which is either a single spanning-tree switch or a switch with a different MST configuration.
Understanding RSTP
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 IEEE 802.1D spanning tree).
These sections describe how the RSTP works:
Port Roles and the Active Topology, page 18-9
Rapid Convergence, page 18-10
Synchronization of Port Roles, page 18-11
Bridge Protocol Data Unit Format and Processing, page 18-12
For configuration information, see the Configuring MSTP Features section on page 18-14.
Port Roles and the Active Topology
The RSTP provides rapid convergence of the spanning tree by assigning port roles and by learning the
active topology. The RSTP builds upon the IEEE 802.1D STP to select the switch with the highest switch
priority (lowest numerical priority value) as the root switch as described in the Spanning-Tree Topology
and BPDUs section on page 17-3. Then the RSTP assigns one of these port roles to individual ports:
Root portProvides the best path (lowest cost) when the switch forwards packets to the root switch.
Designated portConnects to the designated switch, which incurs the lowest path cost when
forwarding packets from that LAN to the root switch. The port through which the designated switch
is attached to the LAN is called the designated port.
Alternate portOffers an alternate path toward the root switch to that provided by the current root
port.
Backup portActs as a backup for the path provided by a designated port toward the leaves of the
spanning tree. A backup port can exist only when two ports are connected in a loopback by a
point-to-point link or when a switch has two or more connections to a shared LAN segment.
Disabled portHas no role within the operation of the spanning tree.
A port with the root or a designated port role is included in the active topology. A port with the alternate
or backup port role is excluded from the active topology.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
18-9
Chapter 18
Configuring MSTP
Understanding RSTP
In a stable topology with consistent port roles throughout the network, the RSTP ensures that every root
port and designated port immediately transition to the forwarding state while all alternate and backup
ports are always in the discarding state (equivalent to blocking in IEEE 802.1D). The port state controls
the operation of the forwarding and learning processes. Table 18-2 provides a comparison of
IEEE 802.1D and RSTP port states.
Table 18-2
Port State Comparison
Operational Status
STP Port State
(IEEE 802.1D)
RSTP Port State
Is Port Included in the
Active Topology?
Enabled
Blocking
Discarding
No
Enabled
Listening
Discarding
No
Enabled
Learning
Learning
Yes
Enabled
Forwarding
Forwarding
Yes
Disabled
Disabled
Discarding
No
To be consistent with Cisco STP implementations, this guide defines the port state as blocking instead
of discarding. Designated ports start in the listening state.
Rapid Convergence
The RSTP provides for rapid recovery of connectivity following the failure of a switch, a switch port, or
a LAN. It provides rapid convergence for edge ports, new root ports, and ports connected through
point-to-point links as follows:
Edge portsIf you configure a port as an edge port on an RSTP switch by using the spanning-tree
portfast interface configuration command, the edge port immediately transitions to the forwarding
state. An edge port is the same as a Port Fast-enabled port, and you should enable it only on ports
that connect to a single end station.
Root portsIf the RSTP selects a new root port, it blocks the old root port and immediately
transitions the new root port to the forwarding state.
Point-to-point linksIf you connect a port to another port through a point-to-point link and the local
port becomes a designated port, it negotiates a rapid transition with the other port by using the
proposal-agreement handshake to ensure a loop-free topology.
As shown in Figure 18-4, Switch A is connected to Switch B through a point-to-point link, and all
of the ports are in the blocking state. Assume that the priority of Switch A is a smaller numerical
value than the priority of Switch B. Switch A sends a proposal message (a configuration BPDU with
the proposal flag set) to Switch B, proposing itself as the designated switch.
After receiving the proposal message, Switch B selects as its new root port the port from which the
proposal message was received, forces all nonedge ports to the blocking state, and sends an
agreement message (a BPDU with the agreement flag set) through its new root port.
After receiving Switch Bs agreement message, Switch A also immediately transitions its designated
port to the forwarding state. No loops in the network are formed because Switch B blocked all of its
nonedge ports and because there is a point-to-point link between Switches A and B.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
18-10
OL-12189-01
Chapter 18
Configuring MSTP
Understanding RSTP
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.
In a switch stack, the cross-stack rapid transition (CSRT) feature ensures that a stack member
receives acknowledgments from all stack members during the proposal-agreement handshaking
before moving the port to the forwarding state. CSRT is automatically enabled when the switch is
in MST mode.
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.
Proposal and Agreement Handshaking for Rapid Convergence
Switch A
Proposal
Switch B
Root
Agreement
Designated
switch
F
DP
F
RP
Root
F
DP
Designated
switch
Proposal
Designated
switch
Agreement
F
RP
Root
F
DP
F
RP
F
DP
Switch C
F
RP
DP = designated port
RP = root port
F = forwarding
88760
Figure 18-4
Synchronization of Port Roles
When the switch receives a proposal message on one of its ports and that port is selected as the new root
port, the RSTP forces all other ports to synchronize with the new root information.
The switch is synchronized with superior root information received on the root port if all other ports are
synchronized. An individual port on the switch is synchronized if
That port is in the blocking state.
It is an edge port (a port configured to be at the edge of the network).
If a designated port is in the forwarding state and is not configured as an edge port, it transitions to the
blocking state when the RSTP forces it to synchronize with new root information. In general, when the
RSTP forces a port to synchronize with root information and the port does not satisfy any of the above
conditions, its port state is set to blocking.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
18-11
Chapter 18
Configuring MSTP
Understanding RSTP
After ensuring that all of the ports are synchronized, the switch sends an agreement message to the
designated switch corresponding to its root port. When the switches connected by a point-to-point link
are in agreement about their port roles, the RSTP immediately transitions the port states to forwarding.
The sequence of events is shown in Figure 18-5.
Figure 18-5
Sequence of Events During Rapid Convergence
4. Agreement
1. Proposal
5. Forward
Edge port
3. Block
11. Forward
8. Agreement
7. Proposal
6. Proposal
10. Agreement
Root port
Designated port
88761
2. Block
9. Forward
Bridge Protocol Data Unit Format and Processing
The RSTP BPDU format is the same as the IEEE 802.1D BPDU format except that the protocol version
is set to 2. A new 1-byte Version 1 Length field is set to zero, which means that no version 1 protocol
information is present. Table 18-3 shows the RSTP flag fields.
Table 18-3
RSTP BPDU Flags
Bit
Function
Topology change (TC)
Proposal
23:
Port role:
00
Unknown
01
Alternate port
10
Root port
11
Designated port
Learning
Forwarding
Agreement
Topology change acknowledgement (TCA)
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
18-12
OL-12189-01
Chapter 18
Configuring MSTP
Understanding RSTP
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 IEEE 802.1D
switches, the RSTP switch processes and generates TCN BPDUs.
The learning and forwarding flags are set according to the state of the sending port.
Processing Superior BPDU Information
If a port receives superior root information (lower switch ID, lower path cost, and so forth) than currently
stored for the port, the RSTP triggers a reconfiguration. If the port is proposed and is selected as the new
root port, RSTP forces all the other ports to synchronize.
If the BPDU received is an RSTP BPDU with the proposal flag set, the switch sends an agreement
message after all of the other ports are synchronized. If the BPDU is an IEEE 802.1D BPDU, the switch
does not set the proposal flag and starts the forward-delay timer for the port. The new root port requires
twice the forward-delay time to transition to the forwarding state.
If the superior information received on the port causes the port to become a backup or alternate port,
RSTP sets the port to the blocking state but does not send the agreement message. The designated port
continues sending BPDUs with the proposal flag set until the forward-delay timer expires, at which time
the port transitions to the forwarding state.
Processing Inferior BPDU Information
If a designated port receives an inferior BPDU (higher switch ID, higher path cost, and so forth than
currently stored for the port) with a designated port role, it immediately replies with its own information.
Topology Changes
This section describes the differences between the RSTP and the IEEE 802.1D in handling spanning-tree
topology changes.
DetectionUnlike IEEE 802.1D in which any transition between the blocking and the forwarding
state causes a topology change, only transitions from the blocking to the forwarding state cause a
topology change with RSTP (only an increase in connectivity is considered a topology change).
State changes on an edge port do not cause a topology change. When an RSTP switch detects a
topology change, it deletes the learned information on all of its nonedge ports except on those from
which it received the TC notification.
NotificationUnlike IEEE 802.1D, which uses TCN BPDUs, the RSTP does not use them.
However, for IEEE 802.1D interoperability, an RSTP switch processes and generates TCN BPDUs.
AcknowledgementWhen an RSTP switch receives a TCN message on a designated port from an
IEEE 802.1D switch, it replies with an IEEE 802.1D configuration BPDU with the TCA bit set.
However, if the TC-while timer (the same as the topology-change timer in IEEE 802.1D) is active
on a root port connected to an IEEE 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 IEEE 802.1D switches. The RSTP BPDUs never have the
TCA bit set.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
18-13
Chapter 18
Configuring MSTP
Configuring MSTP Features
PropagationWhen an RSTP switch receives a TC message from another switch through a
designated or root port, it propagates the change to all of its nonedge, designated ports and to the
root port (excluding the port on which it is received). The switch starts the TC-while timer for all
such ports and flushes the information learned on them.
Protocol migrationFor backward compatibility with IEEE 802.1D switches, RSTP selectively
sends IEEE 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 IEEE 802.1D BPDU after the port migration-delay timer has expired, it
assumes that it is connected to an IEEE 802.1D switch and starts using only IEEE 802.1D BPDUs.
However, if the RSTP switch is using IEEE 802.1D BPDUs on a port and receives an RSTP BPDU
after the timer has expired, it restarts the timer and starts using RSTP BPDUs on that port.
Configuring MSTP Features
These sections contain this configuration information:
Default MSTP Configuration, page 18-14
MSTP Configuration Guidelines, page 18-15
Specifying the MST Region Configuration and Enabling MSTP, page 18-16 (required)
Configuring the Root Switch, page 18-17 (optional)
Configuring a Secondary Root Switch, page 18-19 (optional)
Configuring Port Priority, page 18-19 (optional)
Configuring Path Cost, page 18-21 (optional)
Configuring the Switch Priority, page 18-21 (optional)
Configuring the Hello Time, page 18-22 (optional)
Configuring the Forwarding-Delay Time, page 18-23 (optional)
Configuring the Maximum-Aging Time, page 18-23 (optional)
Configuring the Maximum-Hop Count, page 18-24 (optional)
Specifying the Link Type to Ensure Rapid Transitions, page 18-24 (optional)
Designating the Neighbor Type, page 18-25 (optional)
Restarting the Protocol Migration Process, page 18-25 (optional)
Default MSTP Configuration
Table 18-4 shows the default MSTP configuration.
Table 18-4
Default MSTP Configuration
Feature
Default Setting
Spanning-tree mode
PVST+ (Rapid PVST+ and MSTP are disabled).
Switch priority (configurable on a per-CIST port basis)
32768.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
18-14
OL-12189-01
Chapter 18
Configuring MSTP
Configuring MSTP Features
Table 18-4
Default MSTP Configuration (continued)
Feature
Default Setting
Spanning-tree port priority (configurable on a per-CIST port basis)
128.
Spanning-tree port cost (configurable on a per-CIST port basis)
1000 Mb/s: 4.
100 Mb/s: 19.
10 Mb/s: 100.
Hello time
2 seconds.
Forward-delay time
15 seconds.
Maximum-aging time
20 seconds.
Maximum hop count
20 hops.
For information about the supported number of spanning-tree instances, see the Supported
Spanning-Tree Instances section on page 17-10.
MSTP Configuration Guidelines
These are the configuration guidelines for MSTP:
When you enable MST by using the spanning-tree mode mst global configuration command, RSTP
is automatically enabled.
For two or more nonstacking-capable switches to be in the same MST region, they must have the
same VLAN-to-instance map, the same configuration revision number, and the same name.
For two or more stacked switches to be in the same MST region, they must have the same
VLAN-to-instance map, the same configuration revision number, and the same name.
The nonstacking-capable switch supports up to 65 MST instances. The number of VLANs that can
be mapped to a particular MST instance is unlimited.
The switch stack supports up to 65 MST instances. The number of VLANs that can be mapped to a
particular MST instance is unlimited.
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 17-11. For information on the recommended trunk port configuration, see the Interaction with
Other Features section on page 12-20.
All stack members run the same version of spanning tree (all PVST+, rapid PVST+, or MSTP). For
more information, see the Spanning-Tree Interoperability and Backward Compatibility section on
page 17-11.
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. You can achieve
load-balancing across a switch stack by manually configuring the path cost.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
18-15
Chapter 18
Configuring MSTP
Configuring MSTP Features
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, BackboneFast, and cross-stack UplinkFast, see the
Optional Spanning-Tree Configuration Guidelines section on page 19-12.
Specifying the MST Region Configuration and Enabling MSTP
For two or more switches to be in the same MST region, they must have the same VLAN-to-instance
mapping, the same configuration revision number, and the same name.
A region can have one member or multiple members with the same MST configuration; each member
must be capable of processing RSTP BPDUs. There is no limit to the number of MST regions in a
network, but each region can only support up to 65 spanning-tree instances. You can assign a VLAN to
only one spanning-tree instance at a time.
Beginning in privileged EXEC mode, follow these steps to specify the MST region configuration and
enable MSTP. This procedure is required.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
spanning-tree mst configuration
Enter MST configuration mode.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
18-16
OL-12189-01
Chapter 18
Configuring MSTP
Configuring MSTP Features
Step 8
Command
Purpose
spanning-tree mode mst
Enable MSTP. RSTP is also enabled.
Caution
Changing spanning-tree modes can disrupt traffic because all
spanning-tree instances are stopped for the previous mode and
restarted in the new mode.
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
Instance Vlans Mapped
-------- --------------------0
1-9,21-4094
1
10-20
------------------------------Switch(config-mst)# exit
Switch(config)#
Configuring the Root Switch
The switch maintains a spanning-tree instance for the group of VLANs mapped to it. A switch ID,
consisting of the switch priority and the switch MAC address, is associated with each instance. For a
group of VLANs, the switch with the lowest switch ID becomes the root switch.
To configure a switch to become the root, use the spanning-tree mst instance-id root global
configuration command to modify the switch priority from the default value (32768) to a significantly
lower value so that the switch becomes the root switch for the specified spanning-tree instance. When
you enter this command, the switch checks the switch priorities of the root switches. Because of the
extended system ID support, the switch sets its own priority for the specified instance to 24576 if this
value will cause this switch to become the root for the specified spanning-tree instance.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
18-17
Chapter 18
Configuring MSTP
Configuring MSTP Features
If any root switch for the specified instance has a switch priority lower than 24576, the switch sets its
own priority to 4096 less than the lowest switch priority. (4096 is the value of the least-significant bit of
a 4-bit switch priority value as shown in Table 17-1 on page 17-5.)
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.
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, which is available only for MST instance 0, 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 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
[diameter net-diameter [hello-time seconds]]
Configure a switch as the root switch.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
18-18
OL-12189-01
Chapter 18
Configuring MSTP
Configuring MSTP Features
Configuring a Secondary Root Switch
When you configure a switch with the extended system ID support as the secondary root, the switch
priority is modified from the default value (32768) to 28672. The switch is then likely to become the root
switch for the specified instance if the primary root switch fails. This is assuming that the other network
switches use the default switch priority of 32768 and therefore are unlikely to become the root switch.
You can execute this command on more than one switch to configure multiple backup root switches. Use
the same network diameter and hello-time values that you used when you configured the primary root
switch with the spanning-tree mst instance-id root primary 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
secondary [diameter net-diameter
[hello-time seconds]]
Configure a switch as the secondary root switch.
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.
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 18-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.
Configuring Port Priority
If a loop occurs, the MSTP uses the port priority when selecting an interface to put into the forwarding
state. You can assign higher priority values (lower numerical values) to interfaces that you want selected
first and lower priority values (higher numerical values) that you want selected last. If all interfaces have
the same priority value, the MSTP puts the interface with the lowest interface number in the forwarding
state and blocks the other interfaces.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
18-19
Chapter 18
Configuring MSTP
Configuring MSTP Features
Note
If your switch is a member of a switch stack, you must use the spanning-tree mst [instance-id] cost cost
interface configuration command instead of the spanning-tree mst [instance-id] port-priority priority
interface configuration command to select a port to put in the forwarding state. Assign lower cost values
to ports that you want selected first and higher cost values to ports that you want selected last. For more
information, see the Configuring Path Cost section on page 18-21.
Beginning in privileged EXEC mode, follow these steps to configure the MSTP 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. The port-channel range is 1 to 48.
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
Note
(Optional) Save your entries in the configuration file.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
18-20
OL-12189-01
Chapter 18
Configuring MSTP
Configuring MSTP Features
Configuring Path Cost
The MSTP path cost default value is derived from the media speed of an interface. If a loop occurs, the
MSTP uses cost when selecting an interface to put in the forwarding state. You can assign lower cost
values to interfaces that you want selected first and higher cost values that you want selected last. If all
interfaces have the same cost value, the MSTP puts the interface with the lowest interface number in the
forwarding state and blocks the other interfaces.
Beginning in privileged EXEC mode, follow these steps to configure the MSTP cost 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. The port-channel range is 1 to 48.
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
Note
(Optional) Save your entries in the configuration file.
The show spanning-tree mst interface interface-id privileged EXEC command displays information
only for ports that are in a link-up operative state. Otherwise, you can use the show running-config
privileged EXEC command to confirm the configuration.
To return the interface to its default setting, use the no spanning-tree mst instance-id cost interface
configuration command.
Configuring the Switch Priority
You can configure the switch priority and make it more likely that a standalone switch or a switch in the
stack will be chosen as the root switch.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
18-21
Chapter 18
Configuring MSTP
Configuring MSTP Features
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.
Configuring the Hello Time
You can configure the interval between the generation of configuration messages by the root switch by
changing 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
18-22
OL-12189-01
Chapter 18
Configuring MSTP
Configuring MSTP Features
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.
Configuring the Forwarding-Delay Time
Beginning in privileged EXEC mode, follow these steps to configure the forwarding-delay time for all
MST instances. This procedure is optional.
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.
Configuring the Maximum-Aging Time
Beginning in privileged EXEC mode, follow these steps to configure the maximum-aging time for all
MST instances. This procedure is optional.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
18-23
Chapter 18
Configuring MSTP
Configuring MSTP Features
To return the switch to its default setting, use the no spanning-tree mst max-age global configuration
command.
Configuring the Maximum-Hop Count
Beginning in privileged EXEC mode, follow these steps to configure the maximum-hop count for all
MST instances. This procedure is optional.
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.
Specifying the Link Type to Ensure Rapid Transitions
If you connect a port to another port through a point-to-point link and the local port becomes a
designated port, the RSTP negotiates a rapid transition with the other port by using the
proposal-agreement handshake to ensure a loop-free topology as described in the Rapid Convergence
section on page 18-10.
By default, the link type is controlled from the duplex mode of the interface: a full-duplex port is
considered to have a point-to-point connection; a half-duplex port is considered to have a shared
connection. If you have a half-duplex link physically connected point-to-point to a single port on a
remote switch running MSTP, you can override the default setting of the link type and enable rapid
transitions to the forwarding state.
Beginning in privileged EXEC mode, follow these steps to override the default link-type setting. 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,
VLANs, and port-channel logical interfaces. The VLAN ID
range is 1 to 4094. The port-channel range is 1 to 48.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
18-24
OL-12189-01
Chapter 18
Configuring MSTP
Configuring MSTP Features
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.
Designating the Neighbor Type
A topology could contain both prestandard and IEEE 802.1s standard compliant devices. By default,
ports can automatically detect prestandard devices, but they can still receive both standard and
prestandard BPDUs. When there is a mismatch between a device and its neighbor, only the CIST runs
on the interface.
You can choose to set a port to send only prestandard BPDUs. The prestandard flag appears in all the
show commands, even if the port is in STP compatibility mode.
Beginning in privileged EXEC mode, follow these steps to override the default link-type setting. 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.
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.
Restarting the Protocol Migration Process
A switch running MSTP supports a built-in protocol migration mechanism that enables it to interoperate
with legacy IEEE 802.1D switches. If this switch receives a legacy IEEE 802.1D configuration BPDU
(a BPDU with the protocol version set to 0), it sends only IEEE 802.1D BPDUs on that port. An MSTP
switch also can detect that a port is at the boundary of a region when it receives a legacy BPDU, an MST
BPDU (Version 3) associated with a different region, or an RST BPDU (Version 2).
However, the switch does not automatically revert to the MSTP mode if it no longer receives
IEEE 802.1D BPDUs because it cannot detect whether the legacy switch has been removed from the link
unless the legacy switch is the designated switch. A switch also might continue to assign a boundary role
to a port when the switch to which it is connected has joined the region.
To restart the protocol migration process (force the renegotiation with neighboring switches) on the
switch, use the clear spanning-tree detected-protocols privileged EXEC command.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
18-25
Chapter 18
Configuring MSTP
Displaying the MST Configuration and Status
To restart the protocol migration process on a specific interface, use the clear spanning-tree
detected-protocols interface interface-id privileged EXEC command.
Displaying the MST Configuration and Status
To display the spanning-tree status, use one or more of the privileged EXEC commands in Table 18-5:
Table 18-5
Commands for Displaying MST Status
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
18-26
OL-12189-01
CH A P T E R
19
Configuring Optional Spanning-Tree Features
This chapter describes how to configure optional spanning-tree features on the 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 or switch stack is running the Multiple Spanning
Tree Protocol (MSTP) or the rapid per-VLAN spanning-tree plus (rapid-PVST+) protocol. Unless
otherwise noted, the term switch refers to a standalone switch and to a witch stack.
For information on configuring the PVST+ and rapid PVST+, see Chapter 17, 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 18, Configuring MSTP.
Note
For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
This chapter consists of these sections:
Understanding Optional Spanning-Tree Features, page 19-1
Configuring Optional Spanning-Tree Features, page 19-11
Displaying the Spanning-Tree Status, page 19-19
Understanding Optional Spanning-Tree Features
These sections contain this conceptual information:
Understanding Port Fast, page 19-2
Understanding BPDU Guard, page 19-2
Understanding BPDU Filtering, page 19-3
Understanding UplinkFast, page 19-3
Understanding Cross-Stack UplinkFast, page 19-5 (only the Catalyst Switch Module 3110)
Understanding BackboneFast, page 19-7
Understanding EtherChannel Guard, page 19-10
Understanding Root Guard, page 19-10
Understanding Loop Guard, page 19-11
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
19-1
Chapter 19
Configuring Optional Spanning-Tree Features
Understanding Optional Spanning-Tree Features
Understanding Port Fast
Port Fast immediately brings an interface configured as an access or trunk port to the forwarding state
from a blocking state, bypassing the listening and learning states. You can use Port Fast on interfaces
connected to a single workstation or server, as shown in Figure 19-1, to allow those devices to
immediately connect to the network, rather than waiting for the spanning tree to converge.
Interfaces connected to a blade server should not receive bridge protocol data units (BPDUs). An
interface with Port Fast enabled goes through the normal cycle of spanning-tree status changes when the
switch is restarted.
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.
Figure 19-1
Port Fast-Enabled Interfaces
Blade Switch
Blade Servers
Blade Servers
119646
Port
Fast-enabled
ports
Understanding BPDU Guard
The BPDU guard feature can be globally enabled on the switch or can be enabled per port, but the feature
operates with some differences.
At the global level, you enable BPDU guard on Port Fast-enabled ports by using the spanning-tree
portfast bpduguard default global configuration command. Spanning tree shuts down ports that are in
a Port Fast-operational state if any BPDU is received on them. In a valid configuration, Port Fast-enabled
ports do not receive BPDUs. Receiving a BPDU on a Port Fast-enabled port means an invalid
configuration, such as the connection of an unauthorized device, and the BPDU guard feature puts the
port in the error-disabled state. When this happens, the switch shuts down the entire port on which the
violation occurred.
To prevent the port from shutting down, you can use the errdisable detect cause bpduguard shutdown
vlan global configuration command to shut down just the offending VLAN on the port where the
violation occurred.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
19-2
OL-12189-01
Chapter 19
Configuring Optional Spanning-Tree Features
Understanding Optional Spanning-Tree Features
At the interface level, you enable BPDU guard on any port by using the spanning-tree bpduguard
enable interface configuration command without also enabling the Port Fast feature. When the port
receives a BPDU, it is put in the error-disabled state.
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.
Understanding BPDU Filtering
The BPDU filtering feature can be globally enabled on the switch or can be enabled per interface, but
the feature operates with some differences.
At the global level, you can enable BPDU filtering on Port Fast-enabled interfaces by using the
spanning-tree portfast bpdufilter default global configuration command. This command prevents
interfaces that are in a Port Fast-operational state from sending or receiving BPDUs. The interfaces still
send a few BPDUs at link-up before the switch begins to filter outbound BPDUs. You should globally
enable BPDU filtering on a switch so that hosts connected to these interfaces do not receive BPDUs. If
a BPDU is received on a Port Fast-enabled interface, the interface loses its Port Fast-operational status,
and BPDU filtering is disabled.
At the interface level, you can enable BPDU filtering on any interface by using the spanning-tree
bpdufilter enable interface configuration command 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 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 19-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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
19-3
Chapter 19
Configuring Optional Spanning-Tree Features
Understanding Optional Spanning-Tree Features
Figure 19-2
Switches in a Hierarchical Network
Backbone switches
Root bridge
126763
Distribution switches
Active link
Blocked link
Blade switches
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 interfaces (per VLAN),
only one of which is forwarding at any given time. Specifically, an uplink group consists of the root port
(which is forwarding) and a set of blocked ports, except for self-looping ports. The uplink group provides
an alternate path in case the currently forwarding link fails.
Figure 19-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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
19-4
OL-12189-01
Chapter 19
Configuring Optional Spanning-Tree Features
Understanding Optional Spanning-Tree Features
Figure 19-3
UplinkFast Example Before Direct Link Failure
Switch A
(Root)
Switch B
L1
L2
L3
43575
Blocked port
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 19-4. This change takes
approximately 1 to 5 seconds.
Figure 19-4
UplinkFast Example After Direct Link Failure
Switch A
(Root)
Switch B
L1
L2
L3
Link failure
Switch C
43576
UplinkFast transitions port
directly to forwarding state.
Understanding Cross-Stack UplinkFast
For the Catalyst Switch Module 3110, the UplinkFast feature is the cross-stack UplinkFast feature.
Cross-stack UplinkFast (CSUF) provides a fast spanning-tree transition (fast convergence in less than
1 second under normal network conditions) across a switch stack. During the fast transition, an alternate
redundant link on the switch stack is placed in the forwarding state without causing temporary
spanning-tree loops or loss of connectivity to the backbone. With this feature, you can have a redundant
and resilient network in some configurations. CSUF is automatically enabled when you enable the
UplinkFast feature by using the spanning-tree uplinkfast global configuration command.
CSUF might not provide a fast transition all the time; in these cases, the normal spanning-tree transition
occurs, completing in 30 to 40 seconds. For more information, see the Events that Cause Fast
Convergence section on page 19-7.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
19-5
Chapter 19
Configuring Optional Spanning-Tree Features
Understanding Optional Spanning-Tree Features
How CSUF Works
CSUF ensures that one link in the stack is elected as the path to the root. As shown in Figure 19-5, the
stack-root port on Switch 1 provides the path to the root of the spanning tree. The alternate stack-root
ports on Switches 2 and 3 can provide an alternate path to the spanning-tree root if the current stack-root
switch fails or if its link to the spanning-tree root fails.
Link 1, the root link, is in the spanning-tree forwarding state. Links 2 and 3 are alternate redundant links
that are in the spanning-tree blocking state. If Switch 1 fails, if its stack-root port fails, or if Link 1 fails,
CSUF selects either the alternate stack-root port on Switch 2 or Switch 3 and puts it into the forwarding
state in less than 1 second.
Figure 19-5
Cross-Stack UplinkFast Topology
Backbone
Spanningtree root
Forward
Forward
Link 1
(Root link)
Link 2
(Alternate
redundant
link)
Link 3
(Alternate
redundant
link)
100 or 1000 Mbps
100 or 1000 Mbps
100 or 1000 Mbps
Stack-root port
Alternate stackroot port
Alternate stackroot port
StackWise Plus
port connections
Switch 2 StackWise Plus
port connections
Switch 3 StackWise Plus
port connections
201790
Switch 1
Forward
Blade switch stack
When certain link loss or spanning-tree events occur (described in the Events that Cause Fast
Convergence section on page 19-7), the Fast Uplink Transition Protocol uses the neighbor list to send
fast-transition requests to stack members.
The switch sending the fast-transition request needs to do a fast transition to the forwarding state of a
port that it has chosen as the root port, and it must obtain an acknowledgement from each stack switch
before performing the fast transition.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
19-6
OL-12189-01
Chapter 19
Configuring Optional Spanning-Tree Features
Understanding Optional Spanning-Tree Features
Each switch in the stack decides if the sending switch is a better choice than itself to be the stack root
of this spanning-tree instance by comparing the root, cost, and bridge ID. If the sending switch is the
best choice as the stack root, each switch in the stack returns an acknowledgement; otherwise, it sends
a fast-transition request. The sending switch then has not received acknowledgements from all stack
switches.
When acknowledgements are received from all stack switches, the Fast Uplink Transition Protocol on
the sending switch immediately transitions its alternate stack-root port to the forwarding state. If
acknowledgements from all stack switches are not obtained by the sending switch, the normal
spanning-tree transitions (blocking, listening, learning, and forwarding) take place, and the
spanning-tree topology converges at its normal rate (2 * forward-delay time + max-age time).
The Fast Uplink Transition Protocol is implemented on a per-VLAN basis and affects only one
spanning-tree instance at a time.
Events that Cause Fast Convergence
Depending on the network event or failure, the CSUF fast convergence might or might not occur.
Fast convergence (less than 1 second under normal network conditions) occurs under these
circumstances:
The stack-root port link fails.
If two switches in the stack have alternate paths to the root, only one of the switches performs the
fast transition.
Note
The failed link, which connects the stack root to the spanning-tree root, recovers.
A network reconfiguration causes a new stack-root switch to be selected.
A network reconfiguration causes a new port on the current stack-root switch to be chosen as the
stack-root port.
The fast transition might not occur if multiple events occur simultaneously. For example, if a stack
member is powered off, and at the same time, the link connecting the stack root to the spanning-tree root
comes back up, the normal spanning-tree convergence occurs.
Normal spanning-tree convergence (30 to 40 seconds) occurs under these conditions:
The stack-root switch is powered off, or the software failed.
The stack-root switch, which was powered off or failed, is powered on.
A new switch, which might become the stack root, is added to the stack.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
19-7
Chapter 19
Configuring Optional Spanning-Tree Features
Understanding Optional Spanning-Tree Features
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 find 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 stacking-capable switch sends the RLQ request on all alternate paths to learn if any
stack member has an alternate root to the root switch and waits for an RLQ reply from other switches in
the network and in the stack.The nonstacking-capable switch sends the RLQ request on all alternate
paths and waits for an RLQ reply from other switches in the network.
When a stack member receives an RLQ reply from a nonstack member on a blocked interface and the
reply is destined for another nonstacked switch, it forwards the reply packet, regardless of the
spanning-tree interface state.
When a stack member receives an RLQ reply from a nonstack member and the response is destined for
the stack, the stack member forwards the reply so that all the other stack members receive it.
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 19-6 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.
Figure 19-6
BackboneFast Example Before Indirect Link Failure
Switch A
(Root)
Switch B
L1
L2
L3
Switch C
44963
Blocked port
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
19-8
OL-12189-01
Chapter 19
Configuring Optional Spanning-Tree Features
Understanding Optional Spanning-Tree Features
If link L1 fails as shown in Figure 19-7, 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 19-7 shows how BackboneFast
reconfigures the topology to account for the failure of link L1.
Figure 19-7
BackboneFast Example After Indirect Link Failure
Switch A
(Root)
Switch B
L1
Link failure
L3
BackboneFast changes port
through listening and learning
states to forwarding state.
Switch C
44964
L2
If a new switch is introduced into a shared-medium topology as shown in Figure 19-8, 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.
Figure 19-8
Adding a Switch in a Shared-Medium Topology
Switch A
(Root)
Switch B
(Designated bridge)
Switch C
Blocked port
44965
Added switch
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
19-9
Chapter 19
Configuring Optional Spanning-Tree Features
Understanding Optional Spanning-Tree Features
Understanding EtherChannel Guard
You can use EtherChannel guard to detect an EtherChannel misconfiguration between the switch and a
connected device. A misconfiguration can occur if the switch interfaces are configured in an
EtherChannel, but the interfaces on the other device are not. A misconfiguration can also occur if the
channel parameters are not the same at both ends of the EtherChannel. For EtherChannel configuration
guidelines, see the EtherChannel Configuration Guidelines section on page 37-11.
If the switch detects a misconfiguration on the other device, EtherChannel guard places the switch
interfaces in the error-disabled state, and displays an error message.
You can enable this feature by using the spanning-tree etherchannel guard misconfig global
configuration command.
Understanding Root Guard
The Layer 2 network of a data center can include many connections to switches that are not owned by
the data center. In such a topology, the spanning tree can reconfigure itself and select a customer switch
as the root switch, as shown in Figure 19-9. You can avoid this situation by enabling root guard on data
center switch interfaces that connect to switches in your customers network. If spanning-tree
calculations cause an interface in the customer network to be selected as the root port, root guard then
places the interface in the root-inconsistent (blocked) state to prevent the customers switch from
becoming the root switch or being in the path to the root.
If a switch outside the data center network becomes the root switch, the interface is blocked
(root-inconsistent state), and spanning tree selects a new root switch. The customers switch does not
become the root switch and is not in the path to the root.
If the switch is operating in multiple spanning-tree (MST) mode, root guard forces the interface to be a
designated port. If a boundary port is blocked in an internal spanning-tree (IST) instance because of root
guard, the interface also is blocked in all MST instances. A boundary port is an interface that connects
to a LAN, the designated switch of which is either an IEEE 802.1D switch or a switch with a different
MST region configuration.
Root guard enabled on an interface applies to all the VLANs to which the interface belongs. VLANs can
be grouped and mapped to an MST instance.
You can enable this feature by using the spanning-tree guard root interface configuration command.
Caution
Misuse of the root-guard feature can cause a loss of connectivity.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
19-10
OL-12189-01
Chapter 19
Configuring Optional Spanning-Tree Features
Configuring Optional Spanning-Tree Features
Figure 19-9
Root Guard in a Data-Center Network
Data-center network
Customer network
Potential
spanning-tree root without
root guard enabled
Desired
root switch
201771
Enable the root-guard feature
on these interfaces to prevent
switches in the customer
network from becoming
the root switch or being
in the path to the root.
Understanding Loop Guard
You can use loop guard to prevent alternate or root ports from becoming designated ports because of a
failure that leads to a unidirectional link. This feature is most effective when it is enabled on the entire
switched network. Loop guard prevents alternate and root ports from becoming designated ports, and
spanning tree does not send BPDUs on root or alternate ports.
You can enable this feature by using the spanning-tree loopguard default global configuration
command.
When the switch is operating in PVST+ or rapid-PVST+ mode, loop guard prevents alternate and root
ports from becoming designated ports, and spanning tree does not send BPDUs on root or alternate ports.
When the switch is operating in MST mode, BPDUs are not sent on nonboundary ports only if the
interface is blocked by loop guard in all MST instances. On a boundary port, loop guard blocks the
interface in all MST instances.
Configuring Optional Spanning-Tree Features
These sections contain this configuration information:
Default Optional Spanning-Tree Configuration, page 19-12
Optional Spanning-Tree Configuration Guidelines, page 19-12
Enabling Port Fast, page 19-12 (optional)
Enabling BPDU Guard, page 19-13 (optional)
Enabling BPDU Filtering, page 19-14 (optional)
Enabling UplinkFast for Use with Redundant Links, page 19-15 (optional)
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
19-11
Chapter 19
Configuring Optional Spanning-Tree Features
Configuring Optional Spanning-Tree Features
Enabling Cross-Stack UplinkFast, page 19-16 (optional and only on the Catalyst Switch
Module 3110)
Enabling BackboneFast, page 19-16 (optional)
Enabling EtherChannel Guard, page 19-17 (optional)
Enabling Root Guard, page 19-18 (optional)
Enabling Loop Guard, page 19-18 (optional)
Default Optional Spanning-Tree Configuration
Table 19-1 shows the default optional spanning-tree configuration.
Table 19-1
Default Optional Spanning-Tree Configuration
Feature
Default Setting
Port Fast, BPDU filtering, BPDU guard
Globally disabled (unless they are individually configured
per interface).
UplinkFast
Globally disabled. (On the Catalyst Switch Module 3110, the
UplinkFast feature is the CSUF feature.)
BackboneFast
Globally disabled.
EtherChannel guard
Globally enabled.
Root guard
Disabled on all interfaces.
Loop guard
Disabled on all interfaces.
Optional Spanning-Tree Configuration Guidelines
You can configure PortFast, BPDU guard, BPDU filtering, EtherChannel guard, root guard, or loop
guard if your switch is running PVST+, rapid PVST+, or MSTP.
On a Catalyst Switch Module 3110, you can configure the UplinkFast, the BackboneFast, or the
cross-stack UplinkFast feature for rapid PVST+ or for the MSTP, but the feature remains disabled
(inactive) until you change the spanning-tree mode to PVST+.
On a Catalyst Switch Module 3012, you can configure the UplinkFast or the BackboneFast feature for
rapid PVST+ or for the MSTP, but the feature remains disabled (inactive) until you change the
spanning-tree mode to PVST+.
Enabling Port Fast
An interface with the Port Fast feature enabled is moved directly to the spanning-tree forwarding state
without waiting for the standard forward-time delay.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
19-12
OL-12189-01
Chapter 19
Configuring Optional Spanning-Tree Features
Configuring Optional Spanning-Tree Features
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
Caution
To enable Port Fast on trunk ports, you must use the
spanning-tree portfast trunk interface configuration
command. The spanning-tree portfast command will
not work on trunk ports.
Make sure that there are no loops in the network
between the trunk port and the workstation or server
before you enable Port Fast on a trunk port.
By default, Port Fast is disabled on all interfaces.
Step 4
end
Return to privileged EXEC mode.
Step 5
show spanning-tree interface interface-id
portfast
Verify your entries.
Step 6
copy running-config startup-config
(Optional) Save your entries in the configuration file.
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.
Enabling BPDU Guard
When you globally enable BPDU guard on ports that are Port Fast-enabled (the ports are in a Port
Fast-operational state), spanning tree continues to run on the ports. They remain up unless they receive
a BPDU.
In a valid configuration, Port Fast-enabled ports do not receive BPDUs. Receiving a BPDU on a Port
Fast-enabled port means an invalid configuration, such as the connection of an unauthorized device, and
the BPDU guard feature puts the port in the error-disabled state. When this happens, the switch shuts
down the entire port on which the violation occurred.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
19-13
Chapter 19
Configuring Optional Spanning-Tree Features
Configuring Optional Spanning-Tree Features
To prevent the port from shutting down, you can use the errdisable detect cause bpduguard shutdown
vlan global configuration command to shut down just the offending VLAN on the port where the
violation occurred.
The BPDU guard feature provides a secure response to invalid configurations because you must
manually put the port back in service. Use the BPDU guard feature in a service-provider network to
prevent an access port from participating in the spanning tree.
Caution
Configure Port Fast only on ports 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 port without also enabling the Port Fast feature. When the port receives a BPDU, it
is put it 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.
Enabling BPDU Filtering
When you globally enable BPDU filtering on Port Fast-enabled interfaces, it prevents interfaces that are
in a Port Fast-operational state from sending or receiving BPDUs. The interfaces still send a few BPDUs
at link-up before the switch begins to filter outbound BPDUs. You should globally enable BPDU filtering
on a switch so that hosts connected to these interfaces do not receive BPDUs. If a BPDU is received on
a Port Fast-enabled interface, the interface loses its Port Fast-operational status, and BPDU filtering is
disabled.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
19-14
OL-12189-01
Chapter 19
Configuring Optional Spanning-Tree Features
Configuring Optional Spanning-Tree Features
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.
Enabling UplinkFast for Use with Redundant Links
UplinkFast cannot be enabled on VLANs that have been configured with a switch priority. To enable
UplinkFast on a VLAN with switch priority configured, first restore the switch priority on the VLAN to
the default value by using the no spanning-tree vlan vlan-id priority global configuration command.
Note
When you enable UplinkFast, it affects all VLANs on the switch or switch stack. You cannot configure
UplinkFast on an individual VLAN.
You can configure the UplinkFast or the CSUF feature for rapid PVST+ or for the MSTP, but the feature
remains disabled (inactive) until you change the spanning-tree mode to PVST+.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
19-15
Chapter 19
Configuring Optional Spanning-Tree Features
Configuring Optional Spanning-Tree Features
Beginning in privileged EXEC mode, follow these steps to enable UplinkFast and CSUF. 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.
When you enter this command, CSUF also is enabled on all
nonstack port interfaces.
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 Cross-Stack UplinkFast
This feature is supported only on the Catalyst Switch Module 3110.
When you enable or disable the UplinkFast feature by using the spanning-tree uplinkfast global
configuration command, CSUF is automatically globally enabled or disabled on nonstack port
interfaces.
For more information, see the Enabling UplinkFast for Use with Redundant Links section on
page 19-15.
To disable UplinkFast on the switch and all its VLANs, use the no spanning-tree uplinkfast global
configuration command.
Enabling BackboneFast
You can enable BackboneFast to detect indirect link failures and to start the spanning-tree
reconfiguration sooner.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
19-16
OL-12189-01
Chapter 19
Configuring Optional Spanning-Tree Features
Configuring Optional Spanning-Tree Features
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 the 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.
Enabling EtherChannel Guard
You can enable EtherChannel guard to detect an EtherChannel misconfiguration if your switch is
running PVST+, rapid PVST+, or MSTP.
Beginning in privileged EXEC mode, follow these steps to enable EtherChannel guard. This procedure
is optional.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
spanning-tree etherchannel guard
misconfig
Enable EtherChannel guard.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
19-17
Chapter 19
Configuring Optional Spanning-Tree Features
Configuring Optional Spanning-Tree Features
Enabling Root Guard
Root guard enabled on an interface applies to all the VLANs to which the interface belongs. Do not
enable the root guard on interfaces to be used by the UplinkFast feature. With UplinkFast, the backup
interfaces (in the blocked state) replace the root port in the case of a failure. However, if root guard is
also enabled, all the backup interfaces used by the UplinkFast feature are placed in the root-inconsistent
state (blocked) and are prevented from reaching the forwarding state.
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.
Enabling Loop Guard
You can use loop guard to prevent alternate or root ports from becoming designated ports because of a
failure that leads to a unidirectional link. This feature is most effective when it is configured on the entire
switched network. Loop guard operates only on interfaces that are considered point-to-point by the
spanning tree.
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.
Step 1
Command
Purpose
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
19-18
OL-12189-01
Chapter 19
Configuring Optional Spanning-Tree Features
Displaying the Spanning-Tree Status
Step 3
Command
Purpose
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.
Displaying the Spanning-Tree Status
To display the spanning-tree status, use one or more of the privileged EXEC commands in Table 19-2:
Table 19-2
Commands for Displaying the Spanning-Tree Status
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
19-19
Chapter 19
Configuring Optional Spanning-Tree Features
Displaying the Spanning-Tree Status
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
19-20
OL-12189-01
CH A P T E R
20
Configuring Flex Links and the MAC
Address-Table Move Update Feature
This chapter describes how to configure Flex Links, a pair of interfaces on the 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. Unless otherwise noted, the term
switch refers to a standalone switch and to a switch stack.
Note
For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
The chapter consists of these sections:
Understanding Flex Links and the MAC Address-Table Move Update, page 20-1
Configuring Flex Links and MAC Address-Table Move Update, page 20-4
Monitoring Flex Links and the MAC Address-Table Move Update Information, page 20-11
Understanding Flex Links and the MAC Address-Table Move
Update
This section contains this information:
Flex Links, page 20-1
VLAN Flex Link Load Balancing and Support, page 20-2
MAC Address-Table Move Update, page 20-3
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
20-1
Chapter 20
Understanding Flex Links and the MAC Address-Table Move Update
Configuring Flex Links and the MAC Address-Table Move Update Feature
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. On stacking-capable switches, the Flex Link can be on the
same switch or on another switch in the stack. 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. For example, in the example in Figure 20-1, you can configure the Flex Links pair with
preemption mode. In the scenario shown, when port 1 comes back up and has more bandwidth than
port 2, port 1 begins forwarding traffic after 60 seconds. Port 2 becomes the standby port. You do this
by entering the interface configuration switchport backup interface preemption mode bandwidth and
switchport backup interface preemption delay commands.
Flex Links Configuration Example
Uplink
switch B
Uplink
switch C
Port 1
Port 2
Switch A
116082
Figure 20-1
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.
VLAN Flex Link Load Balancing and Support
VLAN Flex Link load-balancing allows users to configure a Flex Link pair so that both ports
simultaneously forward the traffic for some mutually exclusive VLANs. For example, if Flex Link ports
are configured for 1-100 VLANs, the traffic of the first 50 VLANs can be forwarded on one port and the
rest on the other port. If one of the ports fail, the other active port forwards all the traffic. When the failed
port comes back up, it resumes forwarding traffic in the preferred VLANs. This way, apart from
providing the redundancy, this Flex Link pair can be used for load balancing. Also, Flex Link VLAN
load-balancing does not impose any restrictions on uplink switches.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
20-2
OL-12189-01
Configuring Flex Links and the MAC Address-Table Move Update Feature
Understanding Flex Links and the MAC Address-Table Move Update
Figure 20-2
VLAN Flex Links Load Balancing Configuration Example
Uplink
switch B
Uplink
switch C
Forwarding
Not Forwarding
gi2/0/6
gi2/0/8
Switch A
201398
Chapter 20
MAC Address-Table Move Update
The MAC address-table move update feature allows the switch to provide rapid bidirectional
convergence when a primary (forwarding) link goes down and the standby link begins forwarding traffic.
In Figure 20-3, switch A is an access switch, and ports 1 and 2 on switch A are connected to uplink
switches B and D through a Flex Link pair. Port 1 is forwarding traffic, and port 2 is in the backup state.
Traffic from the PC to the server is forwarded from port 1 to port 3. The MAC address of the PC has
been learned on port 3 of switch C. Traffic from the server to the PC is forwarded from port 3 to port 1.
If the MAC address-table move update feature is not configured and port 1 goes down, port 2 starts
forwarding traffic. However, for a short time, switch C keeps forwarding traffic from the server to the
PC through port 3, and the PC does not get the traffic because port 1 is down. If switch C removes the
MAC address of the PC on port 3 and relearns it on port 4, traffic can then be forwarded from the server
to the PC through port 2.
If the MAC address-table move update feature is configured and enabled on the switches in Figure 20-3
and port 1 goes down, port 2 starts forwarding traffic from the PC to the server. The switch sends a MAC
address-table move update packet from port 2. Switch C gets this packet on port 4 and immediately
learns the MAC address of the PC on port 4, which reduces the reconvergence time.
You can configure the access switch, switch A, to send MAC address-table move update messages. You
can also configure the uplink switches B, C, and D to get and process the MAC address-table move
update messages. When switch C gets a MAC address-table move update message from switch A,
switch C learns the MAC address of the PC on port 4. Switch C updates the MAC address table,
including the forwarding table entry for the PC.
Switch A does not need to wait for the MAC address-table update. The switch detects a failure on port 1
and immediately starts forwarding server traffic from port 2, the new forwarding port. This change
occurs in 100 milliseconds (ms). The PC is directly connected to switch A, and the connection status
does not change. Switch A does not need to update the PC entry in the MAC address table.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
20-3
Chapter 20
Configuring Flex Links and the MAC Address-Table Move Update Feature
Configuring Flex Links and MAC Address-Table Move Update
Figure 20-3
MAC Address-Table Move Update Example
Server
Switch C
Port 4
Port 3
Switch B
Switch D
Port 1
Port 2
141223
Switch A
PC
Configuring Flex Links and MAC Address-Table Move Update
These sections contain this information:
Configuration Guidelines, page 20-5
Default Configuration, page 20-5
Configuring Flex Links, page 20-6
Configuring VLAN Load Balancing on Flex Links, page 20-8
Configuring the MAC Address-Table Move Update Feature, page 20-9
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
20-4
OL-12189-01
Chapter 20
Configuring Flex Links and the MAC Address-Table Move Update Feature
Configuring Flex Links and MAC Address-Table Move Update
Configuration Guidelines
Follow these guidelines to configure Flex 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 (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 guideline 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.
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.
The MAC address-table move update feature is not configured on the switch.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
20-5
Chapter 20
Configuring Flex Links and the MAC Address-Table Move Update Feature
Configuring Flex Links and MAC Address-Table Move Update
Configuring Flex Links
Beginning in privileged EXEC mode, follow these steps to configure 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.
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 gigabitethernet1/0/1
Switch(conf-if)# switchport backup interface gigabitethernet1/0/2
Switch(conf-if)# end
Switch# show interface switchport backup
Switch Backup Interface Pairs:
Active Interface Backup Interface State
-----------------------------------------------------------------------GigabitEthernet1/0/1 GigabitEthernet1/0/2 Active Up/Backup Standby
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.
Step 3
switchport backup interface interface-id
Configure a physical Layer 2 interface (or port channel)
as part of a Flex Links pair with the interface. When one
link is forwarding traffic, the other interface is in standby
mode.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
20-6
OL-12189-01
Chapter 20
Configuring Flex Links and the MAC Address-Table Move Update Feature
Configuring Flex Links and MAC Address-Table Move Update
Step 4
Step 5
Command
Purpose
switchport backup interface interface-id preemption
mode [forced | bandwidth | off]
Configure a preemption mechanism and delay for a Flex
Link interface pair. You can configure the preemption as:
switchport backup interface interface-id preemption
delay delay-time
Forcedthe active interface always preempts the
backup.
Bandwidththe interface with the higher bandwidth
always acts as the active interface.
Offno preemption happens from active to backup.
Configure the time delay until a port preempts another
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 the preemption mode as forced 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 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/1 GigabitEthernet1/0/2 Active Up/Backup Standby
Interface Pair : Gi1/0/1, Gi1/0/2
Preemption Mode : forced
Preemption Delay : 50 seconds
Bandwidth : 100000 Kbit (Gi1/0/1), 100000 Kbit (Gi1/0/2)
Mac Address Move Update Vlan : auto
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
20-7
Chapter 20
Configuring Flex Links and the MAC Address-Table Move Update Feature
Configuring Flex Links and MAC Address-Table Move Update
Configuring VLAN Load Balancing on Flex Links
Beginning in privileged EXEC mode, follow these steps to configure VLAN load balancing on 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.
Step 3
switchport backup interface interface-id prefer vlan
vlan-range
Configure a physical Layer 2 interface (or port channel)
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 the following example, VLANs 1 to 50, 60, and 100 to 120 are configured on the switch:
Switch(config)#interface gigabitethernet 2/0/6
Switch(config-if)#switchport backup interface gigabitethernet 2/0/8 prefer vlan 60,100-120
When both interfaces are up, Gi2/0/8 forwards traffic for VLANs 60 and 100 to 120 and Gi2/0/6
forwards traffic for VLANs 1 to 50.
Switch# show interfaces switchport backup
Switch Backup Interface Pairs:
Active Interface
Backup Interface
State
-----------------------------------------------------------------------GigabitEthernet2/0/6
GigabitEthernet2/0/8
Active Up/Backup Standby
Vlans Preferred on Active Interface: 1-50
Vlans Preferred on Backup Interface: 60, 100-120
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 Gi2/0/6 goes down, Gi2/0/8 carries
all VLANs of the Flex Link pair.
Switch# show interfaces switchport backup
Switch Backup Interface Pairs:
Active Interface
Backup Interface
State
-----------------------------------------------------------------------GigabitEthernet2/0/6
GigabitEthernet2/0/8
Active Down/Backup Up
Vlans Preferred on Active Interface: 1-50
Vlans Preferred on Backup Interface: 60, 100-120
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
20-8
OL-12189-01
Chapter 20
Configuring Flex Links and the MAC Address-Table Move Update Feature
Configuring Flex Links and MAC Address-Table Move Update
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 Gi2/0/6 comes up, VLANs preferred on this interface are blocked on the peer interface Gi2/0/8
and forwarded on Gi2/0/6.
Switch# show interfaces switchport backup
Switch Backup Interface Pairs:
Active Interface
Backup Interface
State
-----------------------------------------------------------------------GigabitEthernet2/0/6
GigabitEthernet2/0/8
Active Up/Backup Standby
Vlans Preferred on Active Interface: 1-50
Vlans Preferred on Backup Interface: 60, 100-120
Switch# show interfaces switchport backup detail
Switch Backup Interface Pairs:
Active Interface
Backup Interface
State
-----------------------------------------------------------------------FastEthernet1/0/3
FastEthernet1/0/4
Active Down/Backup Up
Vlans Preferred on Active Interface: 1-2,5-4094
Vlans Preferred on Backup Interface: 3-4
Preemption Mode : off
Bandwidth : 10000 Kbit (Fa1/0/3), 100000 Kbit (Fa1/0/4)
Mac Address Move Update Vlan : auto
Configuring the MAC Address-Table Move Update Feature
This section contains this information:
Configuring a switch to send MAC address-table move updates
Configuring a switch to get MAC address-table move updates
Beginning in privileged EXEC mode, follow these steps to configure an access switch to send 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. The MAC
address-table move update VLAN is the lowest VLAN ID
on the interface.
or
switchport backup interface interface-id mmu
primary vlan vlan-id
Configure a physical Layer 2 interface (or port channel)
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
20-9
Chapter 20
Configuring Flex Links and the MAC Address-Table Move Update Feature
Configuring Flex Links and MAC Address-Table Move Update
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, 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:
Switch# configure terminal
Switch(conf)# interface gigabitethernet1/0/1
Switch(conf-if)# switchport backup interface gigabitethernet0/2 mmu primary vlan 2
Switch(conf-if)# exit
Switch(conf)# mac address-table move update transmit
Switch(conf)# end
This example shows how to verify the configuration:
Switch# show mac-address-table move update
Switch-ID : 010b.4630.1780
Dst mac-address : 0180.c200.0010
Vlans/Macs supported : 1023/8320
Default/Current settings: Rcv Off/On, Xmt Off/On
Max packets per min : Rcv 40, Xmt 60
Rcv packet count : 5
Rcv conforming packet count : 5
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 : Po2
Rcv last src-mac-address : 000b.462d.c502
Rcv last switch-ID : 0403.fd6a.8700
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
20-10
OL-12189-01
Chapter 20
Configuring Flex Links and the MAC Address-Table Move Update Feature
Monitoring Flex Links and the MAC Address-Table Move Update Information
Command
Purpose
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, 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
Monitoring Flex Links and the MAC Address-Table Move
Update Information
Table 20-1 shows the privileged EXEC commands for monitoring the Flex Links configuration and the
MAC address-table move update information.
Table 20-1
Flex Links and MAC Address-Table Move Update Monitoring Commands
Command
Purpose
show interface
[interface-id] switchport
backup
Displays the Flex Link backup interface configured for an interface or
all the 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
20-11
Chapter 20
Monitoring Flex Links and the MAC Address-Table Move Update Information
Configuring Flex Links and the MAC Address-Table Move Update Feature
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
20-12
OL-12189-01
CH A P T E R
21
Configuring DHCP Features and IP Source Guard
This chapter describes how to configure DHCP snooping and the option-82 data insertion features on the
switch. It also describes how to configure the IP source guard feature.Unless otherwise noted, the term
switch refers to a standalone switch and to a switch stack.
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.
This chapter consists of these sections:
Understanding DHCP Features, page 21-1
Configuring DHCP Features, page 21-8
Displaying DHCP Snooping Information, page 21-15
Understanding IP Source Guard, page 21-16
Configuring IP Source Guard, page 21-17
Displaying IP Source Guard Information, page 21-19
Understanding DHCP Features
DHCP is widely used in LAN environments to dynamically assign host IP addresses from a centralized
server, which significantly reduces the overhead of administration of IP addresses. DHCP also helps
conserve the limited IP address space because IP addresses no longer need to be permanently assigned
to hosts; only those hosts that are connected to the network consume IP addresses.
These sections contain this information:
DHCP Server, page 21-2
DHCP Relay Agent, page 21-2
DHCP Snooping, page 21-2
Option-82 Data Insertion, page 21-3
DHCP Snooping and Switch Stacks, page 21-8
Cisco IOS DHCP Server Database, page 21-6
DHCP Snooping Binding Database, page 21-6
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
21-1
Chapter 21
Configuring DHCP Features and IP Source Guard
Understanding DHCP Features
For information about the DHCP client, see the Configuring DHCP section of the IP Addressing and
Services section of the Cisco IOS IP Configuration Guide, 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 Relay Agent
A DHCP relay agent is a Layer 3 device that forwards DHCP packets between clients and servers. Relay
agents forward requests and replies between clients and servers when they are not on the same physical
subnet. Relay agent forwarding is different from the normal Layer 2 forwarding, in which IP datagrams
are switched transparently between networks. Relay agents receive DHCP messages and generate new
DHCP messages to send on output interfaces.
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 customers 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
21-2
OL-12189-01
Chapter 21
Configuring DHCP Features and IP Source Guard
Understanding DHCP Features
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 an aggregation switch can be connected to an edge switch through an untrusted interface and you
enter the ip dhcp snooping information option allow-untrusted 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 inspection or IP source guard, can still be enabled on the aggregation
switch while the switch receives packets with option-82 information on untrusted input 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.
Option-82 Data Insertion
In residential, metropolitan Ethernet-access environments, DHCP can centrally manage the IP address
assignments for a large number of subscribers. When the DHCP option-82 feature is enabled on the
switch, a subscriber device is identified by the switch port through which it connects to the network (in
addition to its MAC address). Multiple hosts on the subscriber LAN can be connected to the same port
on the access switch and are uniquely identified.
Note
The DHCP option-82 feature is supported only when DHCP snooping is globally enabled and on the
VLANs to which subscriber devices using this feature are assigned.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
21-3
Chapter 21
Configuring DHCP Features and IP Source Guard
Understanding DHCP Features
Figure 21-1 is an example of a blade switch in an enclosure 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
blade switch) is configured with a helper address to enable broadcast forwarding and to transfer DHCP
messages between the clients and the server.
Figure 21-1
DHCP Relay Agent in a Metropolitan Ethernet Network
DHCP
server
Enclosure
Blade switch
(DHCP relay agent)
Access layer
VLAN 10
Subscribers
Blade Server B
(DHCP client)
201812
Blade Server A
(DHCP client)
When you enable the DHCP snooping information option 82 on the switch, this sequence of
events occurs:
The Blade Server (DHCP client) generates a DHCP request and broadcasts it on the network.
When the blade 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.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-12.
If the IP address of the relay agent is configured, the switch adds this IP address in the DHCP packet.
The blade 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 blade 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 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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
21-4
OL-12189-01
Chapter 21
Configuring DHCP Features and IP Source Guard
Understanding DHCP Features
Remote-ID suboption fields
Suboption type
Length of the suboption type
Remote-ID type
Length of the remote-ID type
In the port field of the circuit ID suboption, the port numbers start at 1. For example, on a Catalyst Switch
Module 3110X, which has 15 ports, port 1 is the internal Gigabit Ethernet 1/0/1 port, port 2 is the internal
Gigabit Ethernet 1/0/2 port, and so on. Port 15 is the 10-Gigabit Ethernet 1/0/15 port.
Figure 21-2 shows the packet formats for the remote-ID suboption and the circuit-ID suboption when
the default suboption configuration is used. For the circuit-ID suboption, the module number
corresponds to the switch number in the stack. The switch uses the packet formats when you globally
enable DHCP snooping and enter the ip dhcp snooping information option global configuration
command.
Figure 21-2
Suboption Packet Formats
Circuit ID Suboption Frame Format
Suboption
Circuit
type
ID type
Length
Length
1
1 byte 1 byte 1 byte 1 byte
VLAN
Module Port
2 bytes
1 byte 1 byte
Remote ID Suboption Frame Format
Suboption
Remote
type
ID type
Length
Length
8
1 byte 1 byte 1 byte 1 byte
MAC address
6 bytes
116300
Figure 21-3 shows the packet formats for user-configured remote-ID and circuit-ID suboptions The
switch uses these packet formats when DHCP snooping is globally enabled and when 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 are
entered.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
21-5
Chapter 21
Configuring DHCP Features and IP Source Guard
Understanding DHCP Features
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.
Remote-ID suboption fields
The remote-ID type is 1.
The length values are variable, depending on the length of the string that you configure.
Figure 21-3
User-Configured Suboption Packet Formats
Circuit ID Suboption Frame Format (for user-configured string):
Suboption
Circuit
type
ID type
Length
Length
1
N+2
1 byte 1 byte 1 byte 1 byte
ASCII Circuit ID string
N bytes (N = 3-63)
Remote ID Suboption Frame Format (for user-configured string):
N+2
1 byte 1 byte 1 byte 1 byte
ASCII Remote ID string or hostname
145774
Suboption
Remote
type
ID type
Length
Length
N bytes (N = 1-63)
Cisco IOS DHCP Server Database
During the DHCP-based autoconfiguration process, the designated DHCP server uses the Cisco IOS
DHCP server database. It has IP addresses, address bindings, and configuration parameters, such as the
boot file.
An address binding is a mapping between an IP address and a MAC address of a host in the Cisco IOS
DHCP server database. You can manually assign the client IP address, or the DHCP server can allocate
an IP address from a DHCP address pool. For more information about manual and automatic address
bindings, see the Configuring DHCP chapter of the Cisco IOS IP Configuration Guide,
Release 12.2.
DHCP Snooping Binding Database
When DHCP snooping is enabled, the switch uses the DHCP snooping binding database to store
information about untrusted interfaces. The database can have up to 8192 bindings.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
21-6
OL-12189-01
Chapter 21
Configuring DHCP Features and IP Source Guard
Understanding DHCP Features
Each database entry (binding) has an IP address, an associated MAC address, the lease time (in
hexadecimal format), the interface to which the binding applies, and the VLAN to which the interface
belongs. The database agent stores the bindings in a file at a configured location. At the end of each entry
is a checksum that accounts for all the bytes from the start of the file through all the bytes associated
with the entry. Each entry is 72 bytes, followed by a space and then the checksum value.
To keep the bindings when the switch reloads, you must use the DHCP snooping database agent. If the
agent is disabled, dynamic ARP inspection 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 DHCP 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 with 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 Gi1/0/4 21ae5fbb
192.1.168.3 3 0003.44d6.c52f 2BB648EB Gi1/0/4 1bdb223f
192.1.168.2 3 0003.47d9.c8f1 2BB648AB Gi1/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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
21-7
Chapter 21
Configuring DHCP Features and IP Source Guard
Configuring DHCP Features
DHCP Snooping and Switch Stacks
DHCP snooping is managed on the stack master. When a new switch joins the stack, the switch receives
the DHCP snooping configuration from the stack master. When a member leaves the stack, all DHCP
snooping address bindings associated with the switch age out.
All snooping statistics are generated on the stack master. If a new stack master is elected, the statistics
counters reset.
When a stack merge occurs, all DHCP snooping bindings in the stack master are lost if it is no longer
the stack master. With a stack partition, the existing stack master is unchanged, and the bindings
belonging to the partitioned switches age out. The new master of the partitioned stack begins processing
the new incoming DHCP packets. For more information about switch stacks, see Chapter 5, Managing
Switch Stacks.
Configuring DHCP Features
These sections contain this configuration information:
Default DHCP Configuration, page 21-8
DHCP Snooping Configuration Guidelines, page 21-9
Configuring the DHCP Server, page 21-10
DHCP Server and Switch Stacks, page 21-10
Configuring the DHCP Relay Agent, page 21-11
Specifying the Packet Forwarding Address, page 21-11
Enabling DHCP Snooping and Option 82, page 21-12
Enabling DHCP Snooping on Private VLANs, page 21-14
Enabling the Cisco IOS DHCP Server Database, page 21-14
Enabling the DHCP Snooping Binding Database Agent, page 21-14
Default DHCP Configuration
Table 21-1 shows the default DHCP configuration.
Table 21-1
Default DHCP Configuration
Feature
Default Setting
DHCP server
Enabled in Cisco IOS software, requires
configuration1
DHCP relay agent
Enabled2
DHCP packet forwarding address
None configured
Checking the relay agent information
Enabled (invalid messages are dropped)2
DHCP relay agent forwarding policy
Replace the existing relay agent information2
DHCP snooping enabled globally
Disabled
DHCP snooping information option
Enabled
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
21-8
OL-12189-01
Chapter 21
Configuring DHCP Features and IP Source Guard
Configuring DHCP Features
Table 21-1
Default DHCP Configuration (continued)
Feature
Default Setting
DHCP snooping option to accept packets on
untrusted input interfaces3
Disabled
DHCP snooping limit rate
None configured
DHCP snooping trust
Untrusted
DHCP snooping VLAN
Disabled
DHCP snooping MAC address verification
Enabled
Cisco IOS DHCP server binding database
Enabled in Cisco IOS software, requires
configuration.
Note
DHCP snooping binding database agent
The switch gets network addresses and
configuration parameters only from a
device configured as a DHCP server.
Enabled in Cisco IOS software, requires
configuration. This feature is operational only
when a destination is configured.
1. The switch responds to DHCP requests only if it is configured as a DHCP server.
2. The switch relays DHCP packets only if the IP address of the DHCP server is configured on the SVI of the DHCP client.
3. Use this feature when the switch is an aggregation switch that receives packets with option-82 information from an edge
switch.
DHCP Snooping Configuration Guidelines
These are the configuration guidelines for DHCP snooping.
You must globally enable DHCP snooping on the switch.
DHCP snooping is not active until DHCP snooping is enabled on a VLAN.
Before globally enabling DHCP snooping on the switch, make sure that the devices acting as the
DHCP server and the DHCP relay agent are configured and enabled.
When you globally enable DHCP snooping on the switch, these Cisco IOS commands are not
available until snooping is disabled. If you enter these commands, the switch returns an error
message, and the configuration is not applied.
ip dhcp relay information check global configuration command
ip dhcp relay information policy global configuration command
ip dhcp relay information trust-all global configuration command
ip dhcp relay information trusted interface configuration command
Before configuring the DHCP snooping information option on your switch, be 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, or you must configure DHCP options for these devices.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
21-9
Chapter 21
Configuring DHCP Features and IP Source Guard
Configuring DHCP Features
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 Configuring NTP section on page 6-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 allow-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.
Configuring the DHCP Server
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.
For procedures to configure the switch as a DHCP server, see the Configuring DHCP section of the
IP addressing and Services section of the Cisco IOS IP Configuration Guide, Release 12.2.
DHCP Server and Switch Stacks
The DHCP binding database is managed on the stack master. When a new stack master is assigned, the
new master downloads the saved binding database from the TFTP server. If the stack master fails, all
unsaved bindings are lost. The IP addresses associated with the lost bindings are released. You should
configure an automatic backup by using the ip dhcp database url [timeout seconds | write-delay
seconds] global configuration command.
When a stack merge occurs, the stack master that becomes a stack member loses all of the DHCP lease
bindings. With a stack partition, the new master in the partition acts as a new DHCP server without any
of the existing DHCP lease bindings.
For more information about the switch stack, see Chapter 5, Managing Switch Stacks.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
21-10
OL-12189-01
Chapter 21
Configuring DHCP Features and IP Source Guard
Configuring DHCP Features
Configuring the DHCP Relay Agent
Beginning in privileged EXEC mode, follow these steps to enable the DHCP relay agent on the switch:
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
Specifying the Packet Forwarding Address
If the DHCP server and the DHCP clients are on different networks or subnets, you must configure the
switch with the ip helper-address address interface configuration command. The general rule is to
configure the command on the Layer 3 interface closest to the client. The address used in the ip
helper-address command can be a specific DHCP server IP address, or it can be the network address if
other DHCP servers are on the destination network segment. Using the network address enables any
DHCP server to respond to requests.
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
Create a switch virtual interface by entering a VLAN
ID, and enter interface configuration mode.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
21-11
Chapter 21
Configuring DHCP Features and IP Source Guard
Configuring DHCP Features
Command
Purpose
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.
Step 6
To remove the DHCP packet forwarding address, use the no ip helper-address address interface
configuration command.
Enabling DHCP Snooping and Option 82
Beginning in privileged EXEC mode, follow these steps to enable DHCP snooping on the switch:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ip dhcp snooping
Enable DHCP snooping globally.
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
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)
Enable the switch to insert and remove DHCP relay information
(option-82 field) in forwarded DHCP request messages to the DHCP
server. This is the default setting.
Note
Configured hostname for the switch
If the hostname is longer than 63 characters, it is truncated to 63
characters in the remote-ID configuration.
The default remote ID is the switch MAC address.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
21-12
OL-12189-01
Chapter 21
Configuring DHCP Features and IP Source Guard
Configuring DHCP Features
Step 6
Command
Purpose
ip dhcp snooping information option
allow-untrusted
(Optional) If the switch is an aggregation switch connected to an edge
switch, enable the switch to accept incoming DHCP snooping packets
with option-82 information from the edge switch.
The default setting is disabled.
Note
Enter this command only on aggregation switches that are
connected to trusted devices.
Step 7
interface interface-id
Step 8
ip dhcp snooping vlan vlan information (Optional) Configure the circuit-ID suboption for the specified interface.
option format-type circuit-id string
Specify the VLAN and port identifier, using a VLAN ID in the range of 1
ASCII-string
to 4094. The default circuit ID is the port identifier, in the format
vlan-mod-port.
Specify the interface to be configured, and enter interface configuration
mode.
You can configure the circuit ID to be a string of 3 to 63 ASCII characters
(no spaces).
Step 9
ip dhcp snooping trust
(Optional) Configure the interface as trusted or untrusted. You can use the
no keyword to configure an interface to receive messages from an
untrusted client. The default setting is untrusted.
Step 10
ip dhcp snooping limit rate rate
(Optional) Configure the number of DHCP packets per second that an
interface can receive. The range is 1 to 2048. By default, no rate limit is
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 on which DHCP
snooping is enabled.
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 allow-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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
21-13
Chapter 21
Configuring DHCP Features and IP Source Guard
Configuring DHCP Features
Switch(config)# interface gigabitethernet2/0/1
Switch(config-if)# ip dhcp snooping limit rate 100
Enabling DHCP Snooping on Private VLANs
You can enable DHCP snooping on private VLANs. If DHCP snooping is enabled, the configuration is
propagated to both a primary VLAN and its associated secondary VLANs. If DHCP snooping is enabled
on the primary VLAN, it is also configured on the secondary VLANs.
If DHCP snooping is already configured on the primary VLAN and you configure DHCP snooping with
different settings on a secondary VLAN, the configuration for the secondary VLAN does not take effect.
You must configure DHCP snooping on the primary VLAN. If DHCP snooping is not configured on the
primary VLAN, this message appears when you are configuring DHCP snooping on the secondary
VLAN, such as VLAN 200:
2w5d:%DHCP_SNOOPING-4-DHCP_SNOOPING_PVLAN_WARNING:DHCP Snooping configuration may not take
effect on secondary vlan 200. DHCP Snooping configuration on secondary vlan is derived
from its primary vlan.
The show ip dhcp snooping privileged EXEC command output shows all VLANs, including primary
and secondary private VLANs, on which DHCP snooping is enabled.
Enabling the Cisco IOS DHCP Server Database
For procedures to enable and configure the Cisco IOS DHCP server database, see the DHCP
Configuration Task List section in the Configuring DHCP chapter of the Cisco IOS IP Configuration
Guide, Release 12.2.
Enabling the DHCP Snooping Binding Database Agent
Beginning in privileged EXEC mode, follow these steps to enable and configure the DHCP snooping
binding database agent on the switch:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ip dhcp snooping database
{flash[number]:/filename |
ftp://user:password@host/filename |
http://[[username:password]@]{hostna
me | host-ip}[/directory]
/image-name.tar |
rcp://user@host/filename}|
tftp://host/filename
Specify the URL for the database agent or the binding file by using one
of these forms:
flash[number]:/filename
(Optional) Use the number parameter to specify the stack member
number of the stack master. The range for number is 1 to 9.
ftp://user:password@host/filename
http://[[username:password]@]{hostname | host-ip}[/directory]
/image-name.tar
rcp://user@host/filename
tftp://host/filename
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
21-14
OL-12189-01
Chapter 21
Configuring DHCP Features and IP Source Guard
Displaying DHCP Snooping Information
Step 3
Command
Purpose
ip dhcp snooping database timeout
seconds
Specify (in seconds) how long to wait for the database transfer process to
finish before stopping the process.
The default is 300 seconds. The range is 0 to 86400. Use 0 to define an
infinite duration, which means to continue trying the transfer indefinitely.
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
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.
Return to privileged EXEC mode.
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
[detail]
Display the status and statistics of the DHCP snooping binding database
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.
Displaying DHCP Snooping Information
To display the DHCP snooping information, use one or more of the privileged EXEC commands in
Table 21-2:
Table 21-2
Commands for Displaying DHCP Information
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.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
21-15
Chapter 21
Configuring DHCP Features and IP Source Guard
Understanding IP Source Guard
Note
If DHCP snooping is enabled and an interface changes to the down state, the switch does not delete the
statically configured bindings.
Understanding IP Source Guard
IP source guard is a security feature that restricts IP traffic on nonrouted, Layer 2 interfaces by filtering
traffic based on the DHCP snooping binding database and on manually configured IP source bindings.
You can use IP source guard to prevent traffic attacks caused when a host tries to use the IP address of
its neighbor.
You can enable IP source guard when DHCP snooping is enabled on an untrusted interface. After IP
source guard is enabled on an interface, the switch blocks all IP traffic received on the interface, except
for DHCP packets allowed by DHCP snooping. A port access control list (ACL) is applied to the
interface. The port ACL allows only IP traffic with a source IP address in the IP source binding table and
denies all other traffic.
Note
As with all port ACLs, this port ACL takes precedence over any router ACLs or VLAN maps that affect
the same interface.
The IP source binding table has bindings that are learned by DHCP snooping or are manually configured
(static IP source bindings). An entry in this table has an IP address, its associated MAC address, and its
associated VLAN number. The switch uses the IP source binding table only when IP source guard is
enabled.
IP source guard is supported only on Layer 2 ports, including access and trunk ports.You can configure
IP source guard with source IP address filtering or with source IP and MAC address filtering.
These sections contain this information:
Source IP Address Filtering, page 21-16
Source IP and MAC Address Filtering, page 21-17
Source IP Address Filtering
When IP source guard is enabled with this option, IP traffic is filtered based on the source IP address.
The switch forwards IP traffic when the source IP address matches an entry in the DHCP snooping
binding database or a binding in the IP source binding table.
When a DHCP snooping binding or static IP source binding is added, changed, or deleted on an interface,
the switch modifies the port ACL using the IP source binding changes, and re-applies the port ACL to
the interface.
If you enable IP source guard on an interface on which IP source bindings (dynamically learned by
DHCP snooping or manually configured) are not configured, the switch creates and applies a port ACL
that denies all IP traffic on the interface. If you disable IP source guard, the switch removes the port ACL
from the interface.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
21-16
OL-12189-01
Chapter 21
Configuring DHCP Features and IP Source Guard
Configuring IP Source Guard
Source IP and MAC Address Filtering
When IP source guard is enabled with this option, IP traffic is filtered based on the source IP and MAC
addresses. The switch forwards traffic only when the source IP and MAC addresses match an entry in
the IP source binding table.
When IP source guard with source IP and MAC address filtering is enabled, the switch filters IP and
non-IP traffic. If the source MAC address of an IP or non-IP packet matches a valid IP source binding,
the switch forwards the packet. The switch drops all other types of packets except DHCP packets.
The switch uses port security to filter source MAC addresses. The interface can shut down when a
port-security violation occurs.
Configuring IP Source Guard
These sections contain this configuration information:
Default IP Source Guard Configuration, page 21-17
IP Source Guard Configuration Guidelines, page 21-17
Enabling IP Source Guard, page 21-18
Default IP Source Guard Configuration
By default, IP source guard is disabled.
IP Source Guard Configuration Guidelines
These are the configuration guides for IP source guard:
You can configure static IP bindings only on nonrouted ports. If you enter the ip source binding
mac-address vlan vlan-id ip-address interface interface-id global configuration command on a
routed interface, this error message appears:
Static IP source binding can only be configured on switch port.
When IP source guard with source IP filtering is enabled on an interface, DHCP snooping must be
enabled on the access VLAN to which the interface belongs.
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.
When IP source guard with source IP and MAC address filtering is enabled, 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 the option-82 data to identify the host port.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
21-17
Chapter 21
Configuring DHCP Features and IP Source Guard
Configuring IP Source Guard
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 hardware entries exceeds the maximum available, the CPU usage increases.
In a switch stack, if IP source guard is configured on a stack member interface and you remove the
the configuration of that switch by entering the no switch stack-member-number provision global
configuration command, the interface static bindings are removed from the binding table, but they
are not removed from the running configuration. If you again provision the switch by entering the
switch stack-member-number provision command, the binding is restored.
To remove the binding from the running configuration, you must disable IP source guard before
entering the no switch provision command. The configuration is also removed if the switch reloads
while the interface is removed from the binding table. For more information about provisioned
switches, see the Chapter 5, Managing Switch Stacks.
Enabling IP Source Guard
Beginning in privileged EXEC mode, follow these steps to enable and configure IP source guard on an
interface.
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 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.
When you enable both IP Source Guard and Port Security by
using the ip verify source port-security interface configuration
command, there are two caveats:
Note
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
vlan-id ip-address inteface interface-id
Add a static IP source binding.
Step 6
end
Return to privileged EXEC mode.
Step 7
show ip verify source [interface
interface-id]
Display the IP source guard configuration for all interfaces or for a
specific interface.
Enter this command for each static binding.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
21-18
OL-12189-01
Chapter 21
Configuring DHCP Features and IP Source Guard
Displaying IP Source Guard Information
Command
Purpose
Step 8
show ip source binding [ip-address]
[mac-address] [dhcp-snooping | static]
[inteface interface-id] [vlan vlan-id]
Display the IP source bindings on the switch, on a specific VLAN, or on
a specific interface.
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
Displaying IP Source Guard Information
To display the IP source guard information, use one or more of the privileged EXEC commands in
Table 21-3:
Table 21-3
Commands for Displaying IP Source Guard Information
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
21-19
Chapter 21
Configuring DHCP Features and IP Source Guard
Displaying IP Source Guard Information
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
21-20
OL-12189-01
CH A P T E R
22
Configuring Dynamic ARP Inspection
This chapter describes how to configure dynamic Address Resolution Protocol inspection (dynamic ARP
inspection) on the 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. Unless otherwise noted, the term
switch refers to a standalone switch and to a switch stack.
Note
For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
This chapter consists of these sections:
Understanding Dynamic ARP Inspection, page 22-1
Configuring Dynamic ARP Inspection, page 22-5
Displaying Dynamic ARP Inspection Information, page 22-14
Understanding Dynamic ARP Inspection
ARP provides IP communication within a Layer 2 broadcast domain by mapping an IP address to a MAC
address. For example, Host B wants to send information to Host A but does not have the MAC address
of Host A in its ARP cache. Host B generates a broadcast message for all hosts within the broadcast
domain to obtain the MAC address associated with the IP address of Host A. All hosts within the
broadcast domain receive the ARP request, and Host A responds with its MAC address. However,
because ARP allows a gratuitous reply from a host even if an ARP request was not received, an ARP
spoofing attack and the poisoning of ARP caches can occur. After the attack, all traffic from the device
under attack flows through the attackers computer and then to the router, switch, or host.
A malicious user can attack hosts, switches, and routers connected to your Layer 2 network by poisoning
the ARP caches of systems connected to the subnet and by intercepting traffic intended for other hosts
on the subnet. Figure 22-1 shows an example of ARP cache poisoning.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
22-1
Chapter 22
Configuring Dynamic ARP Inspection
Understanding Dynamic ARP Inspection
Figure 22-1
Host A
(IA, MA)
ARP Cache Poisoning
Host B
(IB, MB)
Host C (man-in-the-middle)
(IC, MC)
111750
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-5.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
22-2
OL-12189-01
Chapter 22
Configuring Dynamic ARP Inspection
Understanding Dynamic ARP Inspection
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.
Interface Trust States and Network Security
Dynamic ARP inspection associates a trust state with each interface on the switch. Packets arriving on
trusted interfaces bypass all dynamic ARP inspection validation checks, and those arriving on untrusted
interfaces undergo the dynamic ARP inspection validation process.
In a typical network configuration, you configure all switch ports connected to host ports as untrusted
and configure all switch ports connected to switches as trusted. With this configuration, all ARP packets
entering the network from a given switch bypass the security check. No other validation is needed at any
other place in the VLAN or in the network. You configure the trust setting by using the ip arp inspection
trust interface configuration command.
Caution
Use the trust state configuration carefully. Configuring interfaces as untrusted when they should be
trusted can result in a loss of connectivity.
In Figure 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
Host 1
Switch B
Port 3
Host 2
111751
Switch A
Port 1
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
22-3
Chapter 22
Configuring Dynamic ARP Inspection
Understanding 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.
Rate Limiting of ARP Packets
The switch CPU performs dynamic ARP inspection validation checks; therefore, the number of
incoming ARP packets is rate-limited to prevent a denial-of-service attack. By default, the rate for
untrusted interfaces is 15 packets per second (pps). Trusted interfaces are not rate-limited. You can
change this setting by using the ip arp inspection limit interface configuration command.
When the rate of incoming ARP packets exceeds the configured limit, the switch places the port in the
error-disabled state. The port remains in that state until you intervene. You can use the errdisable
recovery global configuration command to enable error disable recovery so that ports automatically
emerge from this state after a specified timeout period.
Note
The rate limit for an EtherChannel is applied separately to each switch in a stack. For example, if a limit
of 20 pps is configured on the EtherChannel, each switch with ports in the EtherChannel can carry up to
20 pps. If any switch exceeds the limit, the entire EtherChannel is placed into the error-disabled state.
For configuration information, see the Limiting the Rate of Incoming ARP Packets section on
page 22-10.
Relative Priority of ARP ACLs and DHCP Snooping Entries
Dynamic ARP inspection uses the DHCP snooping binding database for the list of valid IP-to-MAC
address bindings.
ARP ACLs take precedence over entries in the DHCP snooping binding database. The switch uses ACLs
only if you configure them by using the ip arp inspection filter vlan global configuration command.
The switch first compares ARP packets to user-configured ARP ACLs. If the ARP ACL denies the ARP
packet, the switch also denies the packet even if a valid binding exists in the database populated by
DHCP snooping.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
22-4
OL-12189-01
Chapter 22
Configuring Dynamic ARP Inspection
Configuring Dynamic ARP Inspection
Logging of Dropped Packets
When the switch drops a packet, it places an entry in the log buffer and then generates system messages
on a rate-controlled basis. After the message is generated, the switch clears the entry from the log buffer.
Each log entry contains flow information, such as the receiving VLAN, the port number, the source and
destination IP addresses, and the source and destination MAC addresses.
You use the ip arp inspection log-buffer global configuration command to configure the number of
entries in the buffer and the number of entries needed in the specified interval to generate system
messages. You specify the type of packets that are logged by using the ip arp inspection vlan logging
global configuration command. For configuration information, see the Configuring the Log Buffer
section on page 22-12.
Configuring Dynamic ARP Inspection
These sections contain this configuration information:
Default Dynamic ARP Inspection Configuration, page 22-5
Dynamic ARP Inspection Configuration Guidelines, page 22-6
Configuring Dynamic ARP Inspection in DHCP Environments, page 22-7 (required in DHCP
environments)
Configuring ARP ACLs for Non-DHCP Environments, page 22-8 (required in non-DHCP
environments)
Limiting the Rate of Incoming ARP Packets, page 22-10 (optional)
Performing Validation Checks, page 22-11 (optional)
Configuring the Log Buffer, page 22-12 (optional)
Default Dynamic ARP Inspection Configuration
Table 22-1 shows the default dynamic ARP inspection configuration.
Table 22-1
Default Dynamic ARP Inspection Configuration
Feature
Default Setting
Dynamic ARP inspection
Disabled on all VLANs.
Interface trust state
All interfaces are untrusted.
Rate limit of incoming ARP packets
The rate is 15 pps on untrusted interfaces, assuming that
the network is a switched network with a host
connecting to as many as 15 new hosts per second.
The rate is unlimited on all trusted interfaces.
The burst interval is 1 second.
ARP ACLs for non-DHCP environments
No ARP ACLs are defined.
Validation checks
No checks are performed.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
22-5
Chapter 22
Configuring Dynamic ARP Inspection
Configuring Dynamic ARP Inspection
Table 22-1
Default Dynamic ARP Inspection Configuration (continued)
Feature
Default Setting
Log buffer
When dynamic ARP inspection is enabled, all denied or
dropped ARP packets are logged.
The number of entries in the log is 32.
The number of system messages is limited to 5 per
second.
The logging-rate interval is 1 second.
Per-VLAN logging
All denied or dropped ARP packets are logged.
Dynamic ARP Inspection Configuration Guidelines
These are the dynamic ARP inspection configuration guidelines:
Dynamic ARP inspection is an ingress security feature; it does not perform any egress checking.
Dynamic ARP inspection is not effective for hosts connected to switches that do not support
dynamic ARP inspection or that do not have this feature enabled. Because man-in-the-middle
attacks are limited to a single Layer 2 broadcast domain, separate the domain with dynamic ARP
inspection checks from the one with no checking. This action secures the ARP caches of hosts in the
domain enabled for dynamic ARP inspection.
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.
When DHCP snooping is disabled or in non-DHCP environments, use ARP ACLs to permit or to
deny packets.
Dynamic ARP inspection is supported on access ports, trunk ports, EtherChannel ports, and private
VLAN ports.
A physical port can join an EtherChannel port channel only when the trust state of the physical port
and the channel port match. Otherwise, the physical port remains suspended in the port channel. A
port channel inherits its trust state from the first physical port that joins the channel. Consequently,
the trust state of the first physical port need not match the trust state of the channel.
Conversely, when you change the trust state on the port channel, the switch configures a new trust
state on all the physical ports that comprise the channel.
The rate limit is calculated separately on each switch in a switch stack. 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
22-6
OL-12189-01
Chapter 22
Configuring Dynamic ARP Inspection
Configuring Dynamic ARP Inspection
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.
Configuring Dynamic ARP Inspection in DHCP Environments
This procedure shows how to configure dynamic ARP inspection when two switches support this feature.
Host 1 is connected to Switch A, and Host 2 is connected to Switch B as shown in Figure 22-2 on
page 22-3. Both switches are running dynamic ARP inspection on VLAN 1 where the hosts are located.
A DHCP server is connected to Switch A. Both hosts acquire their IP addresses from the same DHCP
server. Therefore, Switch A has the bindings for Host 1 and Host 2, and Switch B has the binding for
Host 2.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
22-7
Chapter 22
Configuring Dynamic ARP Inspection
Configuring Dynamic ARP Inspection
Step 5
Command
Purpose
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
vlan-range
Check the dynamic ARP inspection statistics.
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
Configuring ARP ACLs for Non-DHCP Environments
This procedure shows how to configure dynamic ARP inspection when Switch B shown in Figure 22-2
on page 22-3 does not support dynamic ARP inspection or DHCP snooping.
If you configure port 1 on Switch A as trusted, a security hole is created because both Switch A and
Host 1 could be attacked by either Switch B or Host 2. To prevent this possibility, you must configure
port 1 on Switch A as untrusted. To permit ARP packets from Host 2, you must set up an ARP ACL and
apply it to VLAN 1. If the IP address of Host 2 is not static (it is impossible to apply the ACL
configuration on Switch A) you must separate Switch A from Switch B at Layer 3 and use a router to
route packets between them.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
22-8
OL-12189-01
Chapter 22
Configuring Dynamic ARP Inspection
Configuring Dynamic ARP Inspection
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
Step 3
permit ip host sender-ip mac host sender-mac [log]
At the end of the ARP access list, there is an
implicit deny ip any mac any command.
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
[static]
Apply the ARP ACL to the VLAN. By default, no
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
22-9
Chapter 22
Configuring Dynamic ARP Inspection
Configuring Dynamic ARP Inspection
Step 7
Command
Purpose
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
Limiting the Rate of Incoming ARP Packets
The switch CPU performs dynamic ARP inspection validation checks; therefore, the number of
incoming ARP packets is rate-limited to prevent a denial-of-service attack.
When the rate of incoming ARP packets exceeds the configured limit, the switch places the port in the
error-disabled state. The port remains in that state until you enable error-disabled recovery so that ports
automatically emerge from this state after a specified timeout period.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
22-10
OL-12189-01
Chapter 22
Configuring Dynamic ARP Inspection
Configuring Dynamic ARP Inspection
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
interval seconds] | none}
Limit the rate of incoming ARP requests and responses on the interface.
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 detect cause arp-inspection
(Optional) Enable error recovery from the dynamic ARP inspection
error-disabled state, and configure the dynamic ARP inspection recover
mechanism variables
and
errdisable recovery cause
arp-inspection
By default, recovery is disabled, and the recovery interval is 300
seconds.
and
errdisable recovery interval interval
For interval interval, specify the time in seconds to recover from the
error-disabled 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.
Performing Validation Checks
Dynamic ARP inspection intercepts, logs, and discards ARP packets with invalid IP-to-MAC address
bindings. You can configure the switch to perform additional checks on the destination MAC address,
the sender and target IP addresses, and the source MAC address.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
22-11
Chapter 22
Configuring Dynamic ARP Inspection
Configuring Dynamic ARP Inspection
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
{[src-mac] [dst-mac] [ip]}
Perform a specific check on incoming ARP packets. By default, no checks
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
vlan-range
Verify your settings.
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.
Configuring the Log Buffer
When the switch drops a packet, it places an entry in the log buffer and then generates system messages
on a rate-controlled basis. After the message is generated, the switch clears the entry from the log buffer.
Each log entry contains flow information, such as the receiving VLAN, the port number, the source and
destination IP addresses, and the source and destination MAC addresses.
A log-buffer entry can represent more than one packet. For example, if an interface receives many
packets on the same VLAN with the same ARP parameters, the switch combines the packets as one entry
in the log buffer and generates a single system message for the entry.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
22-12
OL-12189-01
Chapter 22
Configuring Dynamic ARP Inspection
Configuring Dynamic ARP Inspection
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.
The log buffer configuration applies to each stack member in a switch stack. Each stack member has the
specified logs number entries and generates system messages at the configured rate. For example, if the
interval (rate) is one entry per second, up to five system messages are generated per second in a
five-member switch stack.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
22-13
Chapter 22
Configuring Dynamic ARP Inspection
Displaying Dynamic ARP Inspection Information
Step 3
Command
Purpose
ip arp inspection vlan vlan-range
logging {acl-match {matchlog |
none} | dhcp-bindings {all | none |
permit}}
Control the type of packets that are logged per VLAN. By default, all denied
or all dropped packets are logged. The term logged means the entry is placed
in the log buffer and a system message is generated.
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.
Displaying Dynamic ARP Inspection Information
To display dynamic ARP inspection information, use the privileged EXEC commands in Table 22-2:
Table 22-2
Commands for Displaying Dynamic ARP Inspection Information
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).
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
22-14
OL-12189-01
Chapter 22
Configuring Dynamic ARP Inspection
Displaying Dynamic ARP Inspection Information
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
vlan-range]
Displays statistics for forwarded, dropped, MAC
validation failure, IP validation failure, ACL
permitted and denied, and DHCP permitted and
denied packets for the specified VLAN. If no
VLANs are specified or if a range is specified,
displays information only for VLANs with
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
22-15
Chapter 22
Configuring Dynamic ARP Inspection
Displaying Dynamic ARP Inspection Information
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
22-16
OL-12189-01
CH A P T E R
23
Configuring IGMP Snooping and MVR
This chapter describes how to configure Internet Group Management Protocol (IGMP) snooping on the
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 and procedures
for configuring the IGMP throttling action. Unless otherwise noted, the term switch refers to a
standalone switch and to a switch stack.
Note
For IP Version 6 (IPv6) traffic, Multicast Listener Discovery (MLD) snooping performs the same
function as IGMP snooping for IPv4 traffic. For information about MLD snooping, see Chapter 24,
Configuring IPv6 MLD Snooping.
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.
This chapter consists of these sections:
Note
Understanding IGMP Snooping, page 23-2
Configuring IGMP Snooping, page 23-7
Displaying IGMP Snooping Information, page 23-16
Understanding Multicast VLAN Registration, page 23-18
Configuring MVR, page 23-20
Displaying MVR Information, page 23-24
Configuring IGMP Filtering and Throttling, page 23-24
Displaying IGMP Filtering and Throttling Configuration, page 23-29
You can either manage IP multicast group addresses through features such as IGMP snooping and MVR,
or you can use static IP addresses.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
23-1
Chapter 23
Configuring IGMP Snooping and MVR
Understanding IGMP Snooping
Understanding IGMP Snooping
Layer 2 switches can use IGMP snooping to constrain the flooding of multicast traffic by dynamically
configuring Layer 2 interfaces so that multicast traffic is forwarded to only those interfaces associated
with IP multicast devices. As the name implies, IGMP snooping requires the LAN switch to snoop on
the IGMP transmissions between the host and the router and to keep track of multicast groups and
member ports. When the switch receives an IGMP report from a host for a particular multicast group,
the switch adds the host port number to the forwarding table entry; when it receives an IGMP Leave
Group message from a host, it removes the host port from the table entry. It also periodically deletes
entries if it does not receive IGMP membership reports from the multicast clients.
Note
For more information on IP multicast and IGMP, see RFC 1112 and RFC 2236.
The multicast router (which could be a switch with the IP services feature set on the stack master) 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-14.
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 IGMP snooping characteristics:
IGMP Versions, page 23-3
Joining a Multicast Group, page 23-3
Leaving a Multicast Group, page 23-5
Immediate Leave, page 23-6
IGMP Configurable-Leave Timer, page 23-6
IGMP Report Suppression, page 23-6
IGMP Snooping and Switch Stacks, page 23-7
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
23-2
OL-12189-01
Chapter 23
Configuring IGMP Snooping and MVR
Understanding IGMP Snooping
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/products/sw/iosswrel/ps1834/products_feature_guide09186a008008048a.
html
Joining a Multicast Group
When a blade server connected to the switch wants to join an IP multicast group and it is an IGMP
Version 2 client, it sends an unsolicited IGMP join message, specifying the IP multicast group to join.
Alternatively, when the switch receives a general query from the router, it forwards the query to all ports
in the VLAN. IGMP Version 1 or Version 2 blade servers wanting to join the multicast group respond
by sending a join message to the switch. The switch CPU creates a multicast forwarding-table entry for
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
23-3
Chapter 23
Configuring IGMP Snooping and MVR
Understanding IGMP Snooping
the group if it is not already present. The CPU also adds the interface where the join message was
received to the forwarding-table entry. The blade server associated with that interface receives multicast
traffic for that multicast group. See Figure 23-1.
Figure 23-1
Initial IGMP Join Message
Router A
19
IGMP report 224.1.2.3
VLAN
Switching engine
CPU
0
201772
Forwarding
table
1
Blade
Blade
Blade
Blade
Server 1 Server 2 Server 3 Server 4
Router A sends a general query to the switch, which forwards the query to ports 3,5, and 7, which are
all members of the same VLAN. Blade Server 1 wants to join multicast group 224.1.2.3 and multicasts
an IGMP membership report (IGMP join message) to the group. The switch CPU uses the information
in the IGMP report to set up a forwarding-table entry, as shown in Table 23-1, that includes the port
numbers of Blade Server 1 and the router.
Table 23-1
IGMP Snooping Forwarding Table
Destination Address
Type of Packet
Ports
224.1.2.3
IGMP
19, 1
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
23-4
OL-12189-01
Chapter 23
Configuring IGMP Snooping and MVR
Understanding IGMP Snooping
If another blade server (for example, Blade Server 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 Blade Server 4 to
the forwarding table as shown in Table 23-2. Note that because the forwarding table directs IGMP
messages only to the 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.
Figure 23-2
Second Host Joining a Multicast Group
Router A
19
VLAN
Switching engine
CPU
201773
Forwarding
table
1
Blade
Blade
Blade
Blade
Server 1 Server 2 Server 3 Server 4
Table 23-2
Updated IGMP Snooping Forwarding Table
Destination Address
Type of Packet
Ports
224.1.2.3
IGMP
19, 1, 7
Leaving a Multicast Group
The router sends periodic multicast general queries, and the switch forwards these queries through all
ports in the VLAN. Interested blade servers respond to the queries. If at least one blade server in the
VLAN wishes to receive multicast traffic, the router continues forwarding the multicast traffic to the
VLAN. The switch forwards multicast group traffic only to those blade servers listed in the forwarding
table for that IP multicast group maintained by IGMP snooping.
When blade servers want to leave a multicast group, they can silently leave, or they can send a leave
message. When the switch receives a leave message from a blade server, it sends a group-specific query
to learn if any other devices connected to that interface are interested in traffic for the specific multicast
group. The switch then updates the forwarding table for that MAC group so that only those blade servers
interested in receiving multicast traffic for the group are listed in the forwarding table. If the router
receives no reports from a VLAN, it removes the group for the VLAN from its IGMP cache.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
23-5
Chapter 23
Configuring IGMP Snooping and MVR
Understanding IGMP Snooping
Immediate Leave
Immediate Leave is only supported on IGMP Version 2 hosts.
The switch uses IGMP snooping Immediate Leave 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 ensures optimal bandwidth management for all blade servers on a switched network,
even when multiple multicast groups are simultaneously in use.
Note
You should only use the Immediate Leave feature on VLANs where a single blade server is connected
to each port. If Immediate Leave is enabled in VLANs where more than one blade server is connected
to a port, some blade servers might inadvertently be dropped.
For configuration steps, see the Enabling IGMP Immediate Leave section on page 23-11.
IGMP Configurable-Leave Timer
You can configure the time that the switch waits after sending a group-specific query to determine if
hosts are still interested in a specific multicast group. The IGMP leave response time can be configured
from 100 to 5000 milliseconds. The timer can be set either globally or on a per-VLAN basis. The VLAN
configuration of the leave time overrides the global configuration.
For configuration steps, see the Configuring the IGMP Leave Timer section on page 23-12.
IGMP Report Suppression
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 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 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-16.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
23-6
OL-12189-01
Chapter 23
Configuring IGMP Snooping and MVR
Configuring IGMP Snooping
IGMP Snooping and Switch Stacks
IGMP snooping functions across the switch stack; that is, IGMP control information from one switch is
distributed to all switches in the stack. (See Chapter 5, Managing Switch Stacks, for more information
about switch stacks.) Regardless of the stack member through which IGMP multicast data enters the
stack, the data reaches the hosts that have registered for that group.
If a switch in the stack fails or is removed from the stack, only the members of the multicast group that
are on that switch will not receive the multicast data. All other members of a multicast group on other
switches in the stack continue to receive multicast data streams. However, multicast groups that are
common for both Layer 2 and Layer 3 (IP multicast routing) might take longer to converge if the stack
master is removed.
Configuring IGMP Snooping
IGMP snooping allows switches to examine IGMP packets and make forwarding decisions based on their
content. These sections contain this configuration information:
Default IGMP Snooping Configuration, page 23-7
Enabling or Disabling IGMP Snooping, page 23-8
Setting the Snooping Method, page 23-9
Configuring a Multicast Router Port, page 23-10
Configuring a Blade Server Statically to Join a Group, page 23-10
Enabling IGMP Immediate Leave, page 23-11
Configuring the IGMP Leave Timer, page 23-12
Configuring TCN-Related Commands, page 23-12
Configuring the IGMP Snooping Querier, page 23-14
Disabling IGMP Report Suppression, page 23-16
Default IGMP Snooping Configuration
Table 23-3 shows the default IGMP snooping configuration.
Table 23-3
Default IGMP Snooping Configuration
Feature
Default Setting
IGMP snooping
Enabled globally and per VLAN
Multicast routers
None configured
Multicast router learning (snooping) method
PIM-DVMRP
IGMP snooping Immediate Leave
Disabled
Static groups
None configured
TCN flood query count
TCN query solicitation
Disabled
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
23-7
Chapter 23
Configuring IGMP Snooping and MVR
Configuring IGMP Snooping
Table 23-3
Default IGMP Snooping Configuration (continued)
Feature
Default Setting
IGMP snooping querier
Disabled
IGMP report suppression
Enabled
1. TCN = Topology Change Notification
Enabling or Disabling IGMP Snooping
By default, IGMP snooping is globally enabled on the switch. When globally enabled or disabled, it is
also enabled or disabled in all existing VLAN interfaces. IGMP snooping is by default enabled on all
VLANs, but can be enabled and disabled on a per-VLAN basis.
Global IGMP snooping overrides the VLAN IGMP snooping. If global snooping is disabled, you cannot
enable VLAN snooping. If global snooping is enabled, you can enable or disable VLAN snooping.
Beginning in privileged EXEC mode, follow these steps to globally enable IGMP snooping on the
switch:
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
23-8
OL-12189-01
Chapter 23
Configuring IGMP Snooping and MVR
Configuring IGMP Snooping
Setting the Snooping Method
Multicast-capable router ports are added to the forwarding table for every Layer 2 multicast entry. The
switch learns of such ports through one of these methods:
Snooping on IGMP queries, Protocol-Independent Multicast (PIM) packets, and Distance Vector
Multicast Routing Protocol (DVMRP) packets
Listening to Cisco Group Management Protocol (CGMP) packets from other routers
Statically connecting to a multicast router port with the ip igmp snooping mrouter global
configuration command
You can configure the switch either to snoop on IGMP queries and PIM/DVMRP packets or to listen to
CGMP self-join or proxy-join packets. By default, the switch snoops on PIM/DVMRP packets on all
VLANs. To learn of multicast router ports through only CGMP packets, use the ip igmp snooping vlan
vlan-id mrouter learn cgmp global configuration command. When this command is entered, the router
listens to only CGMP self-join and CGMP proxy-join packets and to no other CGMP packets. To learn
of multicast router ports through only PIM-DVMRP packets, use the ip igmp snooping vlan vlan-id
mrouter learn pim-dvmrp global configuration command.
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 44, 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
learn {cgmp | pim-dvmrp}
Enable IGMP snooping on a VLAN. The VLAN ID range is 1 to 1001
and 1006 to 4094.
Specify the multicast router learning method:
cgmpListen for CGMP packets. This method is useful for
reducing control traffic.
pim-dvmrpSnoop 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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
23-9
Chapter 23
Configuring IGMP Snooping and MVR
Configuring IGMP Snooping
Configuring a Multicast Router Port
To add a multicast router port (add a static connection to a multicast router), use the ip igmp snooping
vlan mrouter global configuration command on the switch.
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
interface interface-id
Specify the multicast router VLAN ID and the interface 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
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
Return to privileged EXEC mode.
(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 gigabitethernet0/2
Switch(config)# end
Configuring a Blade Server Statically to Join a Group
Blade servers that are connected to Layer 2 ports normally join multicast groups dynamically. You can
also statically configure a Layer 2 port, to which a blade server is connected, so that the port joins a
multicast group.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
23-10
OL-12189-01
Chapter 23
Configuring IGMP Snooping and MVR
Configuring IGMP Snooping
Beginning in privileged EXEC mode, follow these steps to add a Layer 2 port as a member of a multicast
group:
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 a port channel (1 to 48).
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 blade server on a port:
Switch# configure terminal
Switch(config)# ip igmp snooping vlan 105 static 224.2.4.12 interface gigabitethernet1/0/1
Switch(config)# end
Enabling IGMP Immediate Leave
When you enable IGMP Immediate Leave, the switch immediately removes a port when it detects an
IGMP Version 2 leave message on that port. You should only use the Immediate-Leave feature when
there is a single receiver present on every port in the VLAN.
Note
Immediate Leave is supported only on IGMP Version 2 blade servers.
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
immediate-leave
Enable IGMP Immediate Leave on the VLAN interface.
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 interface.
Step 5
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
23-11
Chapter 23
Configuring IGMP Snooping and MVR
Configuring IGMP Snooping
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
Configuring the IGMP Leave Timer
Follows these guidelines when configuring the IGMP leave timer:
You can configure the leave time globally or on a per-VLAN basis.
Configuring the leave time on a VLAN overrides the global setting.
The default leave time is 1000 milliseconds.
The IGMP configurable leave time is only supported on hosts running IGMP Version 2.
The actual leave latency in the network is usually the configured leave time. However, the leave time
might vary around the configured time, depending on real-time CPU load conditions, network delays
and the amount of traffic sent through the interface.
Beginning in privileged EXEC mode, follow these steps to enable the IGMP configurable-leave timer:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ip igmp snooping
last-member-query-interval time
Configure the IGMP leave timer globally. The range is 100 to 5000
milliseconds. The default is 1000 seconds.
Step 3
ip igmp snooping vlan vlan-id
last-member-query-interval time
(Optional) Configure the IGMP leave time on the VLAN interface. The
range is 100 to 5000 milliseconds.
Note
Configuring the leave time on a VLAN overrides the globally
configured timer.
Step 4
end
Return to privileged EXEC mode.
Step 5
show ip igmp snooping
(Optional) Display the configured IGMP leave time.
Step 6
copy running-config startup-config
(Optional) Save your entries in the configuration file.
To globally reset the IGMP leave timer to the default setting, use the no ip igmp snooping
last-member-query-interval global configuration command.
To remove the configured IGMP leave-time setting from the specified VLAN, use the no ip igmp
snooping vlan vlan-id last-member-query-interval global configuration command.
Configuring TCN-Related Commands
These sections describe how to control flooded multicast traffic during a TCN event:
Controlling the Multicast Flooding Time After a TCN Event, page 23-13
Recovering from Flood Mode, page 23-13
Disabling Multicast Flooding During a TCN Event, page 23-14
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
23-12
OL-12189-01
Chapter 23
Configuring IGMP Snooping and MVR
Configuring IGMP Snooping
Controlling the Multicast Flooding Time After a TCN Event
You can control the time that multicast traffic is flooded after a TCN event by using the ip igmp
snooping tcn flood query count global configuration command. This command configures the number
of general queries for which multicast data traffic is flooded after a TCN event. Some examples of TCN
events are when the client changed its location and the receiver is on same port that was blocked but is
now forwarding, and when a port went down without sending a leave message.
If you set the TCN flood query count to 1 by using the ip igmp snooping tcn flood query count
command, the flooding stops after receiving 1 general query. If you set the count to 7, the flooding until
7 general queries are received. Groups are relearned based on the general queries received during the
TCN event.
Beginning in privileged EXEC mode, follow these steps to configure the TCN flood query count:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ip igmp snooping tcn flood query count
count
Specify the number of IGMP general queries for which the multicast
traffic is flooded. The range is 1 to 10. By default, the flooding query
count is 2.
Step 3
end
Return to privileged EXEC mode.
Step 4
show ip igmp snooping
Verify the TCN settings.
Step 5
copy running-config startup-config
(Optional) Save your entries in the configuration file.
To return to the default flooding query count, use the no ip igmp snooping tcn flood query count global
configuration command.
Recovering from Flood Mode
When a topology change occurs, the spanning-tree root sends a special IGMP leave message (also known
as global leave) with the group multicast address 0.0.0.0. However, when you enable the ip igmp
snooping tcn query solicit global configuration command, the switch sends the global leave message
whether or not it is the spanning-tree root. When the router receives this special leave, it immediately
sends general queries, which expedite the process of recovering from the flood mode during the TCN
event. Leaves are always sent if the switch is the spanning-tree root regardless of this configuration
command. By default, query solicitation is disabled.
Beginning in privileged EXEC mode, follow these steps to enable the switch to send the global leave
message whether or not it is the spanning-tree root:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ip igmp snooping tcn query solicit
Send an IGMP leave message (global leave) to speed the process of
recovering from the flood mode caused during a TCN event. By
default, query solicitation is disabled.
Step 3
end
Return to privileged EXEC mode.
Step 4
show ip igmp snooping
Verify the TCN settings.
Step 5
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
23-13
Chapter 23
Configuring IGMP Snooping and MVR
Configuring IGMP Snooping
To return to the default query solicitation, use the no ip igmp snooping tcn query solicit global
configuration command.
Disabling Multicast Flooding During a TCN Event
When the switch receives a TCN, multicast traffic is flooded to all the ports until 2 general queries are
received. If the switch has many ports with attached hosts that are subscribed to different multicast
groups, this flooding might exceed the capacity of the link and cause packet loss. You can use the ip
igmp snooping tcn flood interface configuration command to control this behavior.
Beginning in privileged EXEC mode, follow these steps to disable multicast flooding on an interface:
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
no ip igmp snooping tcn flood
Disable the flooding of multicast traffic during a spanning-tree TCN
event.
By default, multicast flooding is enabled on an interface.
Step 4
exit
Return to privileged EXEC mode.
Step 5
show ip igmp snooping
Verify the TCN settings.
Step 6
copy running-config startup-config
(Optional) Save your entries in the configuration file.
To re-enable multicast flooding on an interface, use the ip igmp snooping tcn flood interface
configuration command.
Configuring the IGMP Snooping Querier
Follow these guidelines when configuring the IGMP snooping querier:
Configure the VLAN in global configuration mode.
Configure an IP address on the VLAN interface. When enabled, the IGMP snooping querier uses the
IP address as the query source address.
If there is no IP address configured on the VLAN interface, the IGMP snooping querier tries to use
the configured global IP address for the IGMP querier. If there is no global IP address specified, the
IGMP querier tries to use the VLAN switch virtual interface (SVI) IP address (if one exists). If there
is no SVI IP address, the switch uses the first available IP address configured on the switch. The first
IP address available appears in the output of the show ip interface privileged EXEC command. The
IGMP snooping querier does not generate an IGMP general query if it cannot find an available IP
address on the switch.
The IGMP snooping querier supports IGMP Versions 1 and 2.
When administratively enabled, the IGMP snooping querier moves to the nonquerier state if it
detects the presence of a multicast router in the network.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
23-14
OL-12189-01
Chapter 23
Configuring IGMP Snooping and MVR
Configuring IGMP Snooping
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
ip_address
(Optional) Specify an IP address for the IGMP snooping querier. If
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
interval-count
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
timeout
(Optional) Set the length of time until the IGMP querier expires.The
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.
(Optional) Set the interval between IGMP queriers. The range is 1 to
18000 seconds.
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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
23-15
Chapter 23
Configuring IGMP Snooping and MVR
Displaying IGMP Snooping Information
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
Disabling IGMP Report Suppression
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.
Displaying IGMP Snooping Information
You can display IGMP snooping information for dynamically learned and statically configured router
ports and VLAN interfaces. You can also display MAC address multicast entries for a VLAN configured
for IGMP snooping.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
23-16
OL-12189-01
Chapter 23
Configuring IGMP Snooping and MVR
Displaying IGMP Snooping Information
To display IGMP snooping information, use one or more of the privileged EXEC commands in
Table 23-4.
Table 23-4
Commands for Displaying IGMP Snooping Information
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
[count] | user [count]]
show ip igmp snooping groups vlan vlan-id
[ip_address | count | dynamic [count] |
user[count]]
show ip igmp snooping mrouter [vlan vlan-id]
Display multicast table information for the switch or about a specific
parameter:
countDisplay the total number of entries for the specified
command options instead of the actual entries.
dynamicDisplay entries learned through IGMP snooping.
userDisplay only the user-configured multicast entries.
Display multicast table information for a multicast VLAN or about a
specific parameter for the VLAN:
vlan-idThe VLAN ID range is 1 to 1001 and 1006 to 4094.
countDisplay the total number of entries for the specified
command options instead of the actual entries.
dynamicDisplay entries learned through IGMP snooping.
ip_addressDisplay characteristics of the multicast group with the
specified group IP address.
userDisplay only the user-configured multicast entries.
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.
(Optional) Enter vlan vlan-id to display information for a single VLAN.
show ip igmp snooping querier [vlan vlan-id]
Display information about the IP address and receiving port for the
most-recently received IGMP query messages in the VLAN.
(Optional) Enter vlan vlan-id to display information for a single VLAN.
show ip igmp snooping querier [vlan vlan-id]
detail
Display information about the IP address and receiving port of the
most-recently received IGMP query message in the VLAN and the
configuration and operational state of the IGMP snooping querier in the
VLAN.
For more information about the keywords and options in these commands, see the command reference
for this release.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
23-17
Chapter 23
Configuring IGMP Snooping and MVR
Understanding Multicast VLAN Registration
Understanding Multicast VLAN Registration
Multicast VLAN Registration (MVR) is designed for applications using wide-scale deployment of
multicast traffic across an Ethernet ring-based service-provider network (for example, the broadcast of
multiple television channels over a service-provider network). MVR allows a subscriber on a port to
subscribe and unsubscribe to a multicast stream on the network-wide multicast VLAN. It allows the
single multicast VLAN to be shared in the network while subscribers remain in separate VLANs. MVR
provides the ability to continuously send multicast streams in the multicast VLAN, but to isolate the
streams from the subscriber VLANs for bandwidth and security reasons.
MVR assumes that subscriber ports subscribe and unsubscribe (join and leave) these multicast streams
by sending out IGMP join and leave messages. These messages can originate from an IGMP
Version-2-compatible blade server with an Ethernet connection. Although MVR operates on the
underlying mechanism of IGMP snooping, the two features operate independently of each other. One
can be enabled or disabled without affecting the behavior of the other feature. However, if IGMP
snooping and MVR are both enabled, MVR reacts only to join and leave messages from multicast groups
configured under MVR. Join and leave messages from all other multicast groups are managed by IGMP
snooping.
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 blade servers is forwarded to all MVR data
ports, regardless of MVR blade server membership on those ports. The multicast data is forwarded
only to those receiver ports that MVR blade servers have joined, either by IGMP reports or by MVR
static configuration. IGMP reports received from MVR blade servers are never forwarded from
MVR data ports that were configured in the blade server.
In dynamic mode, multicast data received by MVR blade servers on the switch is forwarded from
only those MVR data and client ports that the MVR blade servers have joined, either by IGMP
reports or by MVR static configuration. Any IGMP reports received from MVR blade servers are
also forwarded from all the MVR data ports in the blade server. This eliminates using unnecessary
bandwidth on MVR data port links, which occurs when the blade server 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 or switch stack is supported.
Receiver ports and source ports can be on different switches in a switch stack. Multicast data sent on the
multicast VLAN is forwarded to all MVR receiver ports across the stack. When a new switch is added
to a stack, by default it has no receiver ports.
If a switch fails or is removed from the stack, only those receiver ports belonging to that switch will not
receive the multicast data. All other receiver ports on other switches continue to receive the multicast
data.
Using MVR in a Multicast Television Application
In a multicast television application, a server connected to a blade switch can receive the multicast
stream. Multiple devices can be connected to one subscriber port, which is a switch port configured as
an MVR receiver port. Figure 23-3 is an example configuration. DHCP assigns an IP address to the
server. When a subscriber on the server selects a channel, the server sends an IGMP report to the blade
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
23-18
OL-12189-01
Chapter 23
Configuring IGMP Snooping and MVR
Understanding Multicast VLAN Registration
switch to join the appropriate multicast. If the IGMP report matches one of the configured IP multicast
group addresses, the switch CPU modifies the hardware address table to include this receiver port and
VLAN as a forwarding destination of the specified multicast stream when it is received from the
multicast VLAN. Uplink ports that send and receive multicast data to and from the multicast VLAN are
called MVR source ports.
Figure 23-3
Multicast VLAN Registration Example
Multicast VLAN
Cisco router
Multicast
server
SP
Switch
SP
SP
Switch
Switch
SP
SP
Blade Switch
Server
RP2
Server
RP = Receiver Port
SP = Source Port
RP3
Server
RP4
Server
RP5
Server
201915
RP1
Note: All source ports belong to
the multicast VLAN.
When the subscriber changes channels or stops the multicast stream, the server 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 device in the VLAN still subscribing to this group, that device
must respond within the maximum response time specified in the query. If the CPU does not receive a
response, it eliminates the receiver ports 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 multicast traffic for subscribers in each VLAN. Multicast traffic
for all channels is only sent around the VLAN trunk onceonly on the multicast VLAN. The IGMP
leave and join messages are in the VLAN to which the subscriber port is assigned. These messages
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
23-19
Chapter 23
Configuring IGMP Snooping and MVR
Configuring MVR
dynamically register for streams of multicast traffic in the multicast VLAN on the Layer 3 device. The
access layer blade switch 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 blade switch
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 contain this configuration information:
Default MVR Configuration, page 23-20
MVR Configuration Guidelines and Limitations, page 23-20
Configuring MVR Global Parameters, page 23-21
Configuring MVR Interfaces, page 23-22
Default MVR Configuration
Table 23-5 shows the default MVR configuration.
Table 23-5
Default MVR Configuration
Feature
Default Setting
MVR
Disabled globally and per interface
Multicast addresses
None configured
Query response time
0.5 second
Multicast VLAN
VLAN 1
Mode
Compatible
Interface (per port) default
Neither a receiver nor a source port
Immediate Leave
Disabled on all ports
MVR Configuration Guidelines and Limitations
Follow these guidelines when configuring MVR:
Receiver ports can only be access ports; they cannot be trunk ports. Receiver ports on a switch can
be in different VLANs, but should not belong to the multicast VLAN.
The maximum number of multicast entries (MVR group addresses) that can be configured on a
switch (that is, the maximum number of television channels that can be received) is 256.
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).
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
23-20
OL-12189-01
Chapter 23
Configuring IGMP Snooping and MVR
Configuring MVR
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.
Configuring MVR Global Parameters
You do not need to set the optional MVR parameters if you choose to use the default settings. If you do
want to change the default parameters (except for the MVR VLAN), you must first enable MVR.
Note
For complete syntax and usage information for the commands used in this section, see the 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 256; the default is 1). Any multicast data sent to this address is sent to all
source ports on the switch and all receiver ports that have elected to receive
data on that multicast address. Each multicast address would correspond to
one television channel.
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 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:
dynamicAllows dynamic MVR membership on source ports.
compatibleIs 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
end
Return to privileged EXEC mode.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
23-21
Chapter 23
Configuring IGMP Snooping and MVR
Configuring MVR
Command
Purpose
Step 8
show mvr or show mvr members
Verify the configuration.
Step 9
copy running-config
startup-config
(Optional) Save your entries in the configuration file.
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)#
Switch(config)#
Switch(config)#
Switch(config)#
Switch(config)#
Switch(config)#
mvr
mvr
mvr
mvr
mvr
end
group 228.1.23.4
querytime 10
vlan 22
mode dynamic
You can use the show mvr members privileged EXEC command to verify the MVR multicast group
addresses on the switch.
Configuring MVR Interfaces
Beginning in privileged EXEC mode, follow these steps to configure Layer 2 MVR interfaces:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
mvr
Enable MVR on the switch.
Step 3
interface interface-id
Specify the Layer 2 port to configure, and enter interface configuration
mode.
Step 4
mvr type {source | receiver}
Configure an MVR port as one of these:
sourceConfigure 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.
receiverConfigure 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
23-22
OL-12189-01
Chapter 23
Configuring IGMP Snooping and MVR
Configuring MVR
Command
Step 5
Purpose
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
Verify the configuration.
show mvr interface
or
show mvr members
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 a port as a receiver port, statically configure the port to receive
multicast traffic sent to the multicast group address, configure Immediate Leave on the port, 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
Status
Immediate Leave
--------------------------Gi1/0/2 RECEIVER
ACTIVE/DOWN
ENABLED
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
23-23
Chapter 23
Configuring IGMP Snooping and MVR
Displaying MVR Information
Displaying MVR Information
You can display MVR information for the switch or for a specified interface. Beginning in privileged
EXEC mode, use the commands in Table 23-6 to display MVR configuration:
Table 23-6
Commands for Displaying MVR Information
Command
Purpose
show mvr
Displays MVR status and values for the switchwhether MVR is enabled or disabled,
the multicast VLAN, the maximum (256) and current (0 through 256) 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:
TypeReceiver or Source
StatusOne 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 LeaveEnabled 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.
Configuring IGMP Filtering and Throttling
In some environments, for example, metropolitan or multiple-dwelling unit (MDU) installations, you
might want to control the set of multicast groups to which a user on a switch port can belong. You can
control the distribution of multicast services, such as IP/TV, based on some type of subscription or
service plan. You might also want to limit the number of multicast groups to which a user on a switch
port can belong.
With the IGMP filtering feature, you can filter multicast joins on a per-port basis by configuring IP
multicast profiles and associating them with individual switch ports. An IGMP profile can contain one
or more multicast groups and specifies whether access to the group is permitted or denied. If an IGMP
profile denying access to a multicast group is applied to a switch port, the IGMP join report requesting
the stream of IP multicast traffic is dropped, and the port is not allowed to receive IP multicast traffic
from that group. If the filtering action permits access to the multicast group, the IGMP report from the
port is forwarded for normal processing. You can also set the maximum number of IGMP groups that a
Layer 2 interface can join.
IGMP filtering controls only group-specific query and membership reports, including join and leave
reports. It does not control general IGMP queries. IGMP filtering has no relationship with the function
that directs the forwarding of IP multicast traffic. The filtering feature operates in the same manner
whether CGMP or MVR is used to forward the multicast traffic.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
23-24
OL-12189-01
Chapter 23
Configuring IGMP Snooping and MVR
Configuring IGMP Filtering and Throttling
IGMP filtering is applicable only to the dynamic learning of IP multicast group addresses, not static
configuration.
With the IGMP throttling feature, you can 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.
These sections contain this configuration information:
Default IGMP Filtering and Throttling Configuration, page 23-25
Configuring IGMP Profiles, page 23-25 (optional)
Applying IGMP Profiles, page 23-27 (optional)
Setting the Maximum Number of IGMP Groups, page 23-27 (optional)
Configuring the IGMP Throttling Action, page 23-28 (optional)
Default IGMP Filtering and Throttling Configuration
Table 23-7 shows the default IGMP filtering configuration.
Table 23-7
Default IGMP Filtering Configuration
Feature
Default Setting
IGMP filters
None applied
IGMP maximum number of IGMP groups
No maximum set
IGMP profiles
None defined
IGMP profile action
Deny the range addresses
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
section on page 23-28.
Configuring IGMP Profiles
To configure an IGMP profile, use the ip igmp profile global configuration command with a profile
number to create an IGMP profile and to enter IGMP profile configuration mode. From this mode, you
can specify the parameters of the IGMP profile to be used for filtering IGMP join requests from a port.
When you are in IGMP profile configuration mode, you can create the profile by using these commands:
deny: Specifies that matching addresses are denied; this is the default.
exit: Exits from igmp-profile configuration mode.
no: Negates a command or returns to its defaults.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
23-25
Chapter 23
Configuring IGMP Snooping and MVR
Configuring IGMP Filtering and Throttling
permit: Specifies that matching addresses are permitted.
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
Assign a number to the profile you are configuring, and enter IGMP
profile configuration mode. The profile number 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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
23-26
OL-12189-01
Chapter 23
Configuring IGMP Snooping and MVR
Configuring IGMP Filtering and Throttling
Applying IGMP Profiles
To control access as defined in an IGMP profile, use the ip igmp filter interface configuration command
to apply the profile to the appropriate interfaces. You can apply IGMP profiles only to Layer 2 access
ports; you cannot apply IGMP profiles to routed ports or SVIs. You cannot apply profiles to ports that
belong to an EtherChannel port group. You can apply a profile to multiple interfaces, but each interface
can have only one profile applied to it.
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
Specify the physical interface, and enter interface configuration mode.
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 range is 1 to
4294967295.
Step 4
end
Return to privileged EXEC mode.
Step 5
show running-config interface
interface-id
Verify the configuration.
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/2
Switch(config-if)# ip igmp filter 4
Switch(config-if)# end
Setting the Maximum Number of IGMP Groups
You can set the maximum number of IGMP groups that a Layer 2 interface can join by using the ip igmp
max-groups interface configuration command. Use the no form of this command to set the maximum
back to the default, which is no limit.
This restriction can be applied to Layer 2 ports only; you cannot set a maximum number of IGMP groups
on routed ports or SVIs. You also can use this command on a logical EtherChannel interface but cannot
use it on ports that belong to an EtherChannel port group.
Beginning in privileged EXEC mode, follow these steps to set the maximum number of IGMP groups in
the forwarding table:
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. The interface can be a Layer 2 port that does not belong to an
EtherChannel group or a EtherChannel interface.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
23-27
Chapter 23
Configuring IGMP Snooping and MVR
Configuring IGMP Filtering and Throttling
Command
Purpose
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
interface-id
Verify the configuration.
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 to 25 the number of IGMP groups that a port can join.
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# ip igmp max-groups 25
Switch(config-if)# end
Configuring the IGMP Throttling Action
After you set the maximum number of IGMP groups that a Layer 2 interface can join, you can configure
an interface to replace the existing group with the new group for which the IGMP report was received
by using the ip igmp max-groups action replace interface configuration command. Use the no form of
this command to return to the default, which is to drop the IGMP join report.
Follow these guidelines when configuring the IGMP throttling action:
This restriction can be applied only to Layer 2 ports. You can use this command on a logical
EtherChannel interface but cannot use it on ports that belong to an EtherChannel port group.
When the maximum group limitation is set to the default (no maximum), entering the ip igmp
max-groups action {deny | replace} command has no effect.
If you configure the throttling action and set the maximum group limitation after an interface has
added multicast entries to the forwarding table, the forwarding-table entries are either aged out or
removed, depending on the throttling action.
If you configure the throttling action as deny, the entries that were previously in the forwarding
table are not removed but are aged out. After these entries are aged out and the maximum
number of entries is in the forwarding table, the switch drops the next IGMP report received on
the interface.
If you configure the throttling action as replace, the entries that were previously in the
forwarding table are removed. When the maximum number of entries is in the forwarding table,
the switch replaces a randomly selected entry with the received IGMP report.
To prevent the switch from removing the forwarding-table entries, you can configure the IGMP
throttling action before an interface adds entries to the forwarding table.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
23-28
OL-12189-01
Chapter 23
Configuring IGMP Snooping and MVR
Displaying IGMP Filtering and Throttling Configuration
Beginning in privileged EXEC mode, follow these steps to configure the throttling action when the
maximum number of entries is in the forwarding table:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
interface interface-id
Specify the physical interface to be configured, and enter interface
configuration mode. 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 |
replace}
When an interface receives an IGMP report and the maximum number
of entries is in the forwarding table, specify the action that the interface
takes:
denyDrop the report.
replaceReplace the existing group with the new group for which
the IGMP report was received.
Step 4
end
Return to privileged EXEC mode.
Step 5
show running-config interface
interface-id
Verify the configuration.
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.
Displaying IGMP Filtering and Throttling Configuration
You can display IGMP profile characteristics, and you can display the IGMP profile and maximum group
configuration for all interfaces on the switch or for a specified interface. You can also display the IGMP
throttling configuration for all interfaces on the switch or for a specified interface.
Use the privileged EXEC commands in Table 23-8 to display IGMP filtering and throttling
configuration:
Table 23-8
Commands for Displaying IGMP Filtering and Throttling Configuration
Command
Purpose
show ip igmp profile [profile
number]
Displays the specified IGMP profile or all the IGMP profiles defined on the switch.
show running-config [interface
interface-id]
Displays the configuration of the specified interface or the configuration of all interfaces
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
23-29
Chapter 23
Configuring IGMP Snooping and MVR
Displaying IGMP Filtering and Throttling Configuration
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
23-30
OL-12189-01
CH A P T E R
24
Configuring IPv6 MLD Snooping
You can use Multicast Listener Discovery (MLD) snooping to enable efficient distribution of IP
Version 6 (IPv6) multicast data to clients and routers in a switched network on the switch. Unless
otherwise noted, the term switch refers to a standalone switch and to a switch stack.
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 {default |
routing | vlan} global configuration command.
For related information, see these chapters:
Note
For more information about SDM templates, see Chapter 8, Configuring SDM Templates.
For information about IPv6 on the switch, see Chapter 39, Configuring IPv6 Host Functions and
Unicast Routing.
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.
This chapter includes these sections:
Understanding MLD Snooping section on page 24-1
Configuring IPv6 MLD Snooping section on page 24-5
Displaying MLD Snooping Information section on page 24-12
Understanding MLD Snooping
In IP Version 4 (IPv4), Layer 2 switches can use Internet Group Management Protocol (IGMP) snooping
to limit the flooding of multicast traffic by dynamically configuring Layer 2 interfaces so that multicast
traffic is forwarded to only those interfaces associated with IP multicast devices. In IPv6, MLD snooping
performs a similar function. With MLD snooping, IPv6 multicast data is selectively forwarded to a list
of ports that want to receive the data, instead of being flooded to all ports in a VLAN. This list is
constructed by snooping IPv6 multicast control packets.
MLD is a protocol used by IPv6 multicast routers to discover the presence of multicast listeners (nodes
wishing to receive IPv6 multicast packets) on the links that are directly attached to the routers and to
discover which multicast packets are of interest to neighboring nodes. MLD is derived from IGMP; MLD
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
24-1
Chapter 24
Configuring IPv6 MLD Snooping
Understanding MLD Snooping
Version 1 (MLDv1) is equivalent to IGMPv2, and MLD Version 2 (MLDv2) is equivalent to IGMPv3.
MLD is a subprotocol of Internet Control Message Protocol Version 6 (ICMPv6), and MLD messages
are a subset of ICMPv6 messages, identified in IPv6 packets by a preceding Next Header value of 58.
The switch supports two versions of MLD snooping:
MLDv1 snooping detects MLDv1 control packets and sets up traffic bridging based on IPv6
destination multicast addresses.
MLDv2 basic snooping (MBSS) uses MLDv2 control packets to set up traffic forwarding based on
IPv6 destination multicast addresses.
The switch can snoop on both MLDv1 and MLDv2 protocol packets and bridge IPv6 multicast data
based on destination IPv6 multicast addresses.
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.
According to IPv6 multicast standards, the Catalyst Switch Module 3110 derives the MAC multicast
address by performing a logical-OR of the four low-order octets of the switch MAC address with the
MAC address of 33:33:00:00:00:00. For example, the IPv6 MAC address of FF02:DEAD:BEEF:1:3
maps to the Ethernet MAC address of 33:33:00:01:00:03.
On the Catalyst Switch Module 3110, a multicast packet is unmatched when the destination IPv6 address
does not match the destination MAC address. The switch forwards the unmatched packet in hardware
based the MAC address table. If the destination MAC address is not in the MAC address table, the switch
floods the packet to all ports in the same VLAN as the receiving port.
These sections describe some parameters of IPv6 MLD snooping:
MLD Messages, page 24-2
MLD Queries, page 24-3
Multicast Client Aging Robustness, page 24-3
Multicast Router Discovery, page 24-4
MLD Reports, page 24-4
MLD Done Messages and Immediate-Leave, page 24-4
Topology Change Notification Processing, page 24-5
MLD Snooping in Switch Stacks, page 24-5
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
24-2
OL-12189-01
Chapter 24
Configuring IPv6 MLD Snooping
Understanding MLD Snooping
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
For a Catalyst Switch Module 3110, 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 the 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.
For a Catalyst Switch Module 3012, when the IPv6 multicast router is a Catalyst 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 IPv6 multicast router in order for the 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 IPv6 multicast router.
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.
Multicast Client Aging Robustness
You can configure port membership removal from addresses based on the number of queries. A port is
removed from membership to an address only when there are no reports to the address on the port for
the configured number of queries. The default number is 2.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
24-3
Chapter 24
Configuring IPv6 MLD Snooping
Understanding MLD Snooping
Multicast Router Discovery
Like IGMP snooping, MLD snooping performs multicast router discovery, with these characteristics:
Ports configured by a user never age out.
Dynamic port learning results from MLDv1 snooping queries and IPv6 PIMv2 packets.
If there are multiple routers on the same Layer 2 interface, MLD snooping tracks a single multicast
router on the port (the router that most recently sent a router control packet).
Dynamic multicast router port aging is based on a default timer of 5 minutes; the multicast router is
deleted from the router port list if no control packet is received on the port for 5 minutes.
IPv6 multicast router discovery only takes place when MLD snooping is enabled on the switch.
Received IPv6 multicast router control packets are always flooded to the ingress VLAN, whether or
not MLD snooping is enabled on the switch.
After the discovery of the first IPv6 multicast router port, unknown IPv6 multicast data is forwarded
only to the discovered router ports (before that time, all IPv6 multicast data is flooded to the ingress
VLAN).
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.
MLD Done Messages and Immediate-Leave
When the Immediate-Leave feature is enabled and a host sends an MLDv1 Done message (equivalent to
an IGMP leave message), the port on which the Done message was received is immediately deleted from
the group.You enable Immediate-Leave on VLANs and (as with IGMP snooping), you should only use
the feature on VLANs where a single host is connected to the port. If the port was the last member of a
group, the group is also deleted, and the leave information is forwarded to the detected IPv6 multicast
routers.
When Immediate Leave is not enabled in a VLAN (which would be the case when there are multiple
clients for a group on the same port) and a Done message is received on a port, an MASQ is generated
on that port. The user can control when a port membership is removed for an existing address in terms
of the number of MASQs. A port is removed from membership to an address when there are no MLDv1
reports to the address on the port for the configured number of queries.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
24-4
OL-12189-01
Chapter 24
Configuring IPv6 MLD Snooping
Configuring IPv6 MLD Snooping
The number of MASQs generated is configured by using the ipv6 mld snooping last-listener-query
count global configuration command. The default number is 2.
The MASQ is sent to the IPv6 multicast address for which the Done message was sent. If there are no
reports sent to the IPv6 multicast address specified in the MASQ during the switch maximum response
time, the port on which the MASQ was sent is deleted from the IPv6 multicast address database. The
maximum response time is the time configured by using the ipv6 mld snooping
last-listener-query-interval global configuration command. If the deleted port is the last member of the
multicast address, the multicast address is also deleted, and the switch sends the address leave
information to all detected multicast routers.
Topology Change Notification Processing
When topology change notification (TCN) solicitation is enabled by using the ipv6 mld snooping tcn
query solicit global configuration command, MLDv1 snooping sets the VLAN to flood all IPv6
multicast traffic with a configured number of MLDv1 queries before it begins sending multicast data
only to selected ports. You set this value by using the ipv6 mld snooping tcn flood query count global
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.
MLD Snooping in Switch Stacks
The MLD IPv6 group and MAC address databases are maintained on all switches in the stack, regardless
of which switch learns of an IPv6 multicast group. Report suppression and proxy reporting are done
stack-wide. During the maximum response time, only one received report for a group is forwarded to the
multicast routers, regardless of which switch the report arrives on.
The election of a new stack master does not affect the learning or bridging of IPv6 multicast data;
bridging of IPv6 multicast data does not stop during a stack master re-election. When a new switch is
added to the stack, it synchronizes the learned IPv6 multicast information from the stack master. Until
the synchronization is complete, data ingressing on the newly added switch is treated as unknown
multicast data.
Configuring IPv6 MLD Snooping
These sections describe how to configure IPv6 MLD snooping:
Default MLD Snooping Configuration, page 24-6
MLD Snooping Configuration Guidelines, page 24-6
Enabling or Disabling MLD Snooping, page 24-7
Configuring a Static Multicast Group, page 24-8
Configuring a Multicast Router Port, page 24-9
Enabling MLD Immediate Leave, page 24-9
Configuring MLD Snooping Queries, page 24-10
Disabling MLD Listener Message Suppression, page 24-11
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
24-5
Chapter 24
Configuring IPv6 MLD Snooping
Configuring IPv6 MLD Snooping
Default MLD Snooping Configuration
Table 24-1 shows the default MLD snooping configuration.
Table 24-1
Default MLD Snooping Configuration
Feature
Default Setting
MLD snooping (Global)
Disabled.
MLD snooping (per VLAN)
Enabled. MLD snooping must be globally enabled for VLAN
MLD snooping to take place.
IPv6 Multicast addresses
None configured.
IPv6 Multicast router ports
None configured.
MLD snooping Immediate Leave
Disabled.
MLD snooping robustness variable
Global: 2; Per VLAN: 0.
Note
Last listener query count
Global: 2; Per VLAN: 0.
Note
Last listener query interval
The VLAN value overrides the global setting. When the
VLAN value is 0, the VLAN uses the global count.
The VLAN value overrides the global setting. When the
VLAN value is 0, the VLAN uses the global count.
Global: 1000 (1 second); VLAN: 0.
Note
The VLAN value overrides the global setting. When the
VLAN value is 0, the VLAN uses the global interval.
TCN query solicit
Disabled.
TCN query count
2.
MLD listener suppression
Disabled.
MLD Snooping Configuration Guidelines
When configuring MLD snooping, consider these guidelines:
You can configure MLD snooping characteristics at any time, but you must globally enable MLD
snooping by using the ipv6 mld snooping global configuration command for the configuration to
take effect.
On a Catalyst Switch Module 3110, 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 the 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.
On a Catalyst Switch Module 3012, when the IPv6 multicast router is a Catalyst 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 switch in order for the 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 multicast router.
MLD snooping and IGMP snooping act independently of each other. You can enable both features
at the same time on the switch.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
24-6
OL-12189-01
Chapter 24
Configuring IPv6 MLD Snooping
Configuring IPv6 MLD Snooping
The maximum number of multicast entries allowed on the switch or switch stack is determined by
the configured SDM template.
The maximum number of address entries allowed for the switch or switch stack is 1000.
Enabling or Disabling MLD Snooping
By default, IPv6 MLD snooping is globally disabled on the switch and enabled on all VLANs. When
MLD snooping is globally disabled, it is also disabled on all VLANs. When you globally enable MLD
snooping, the VLAN configuration overrides the global configuration. That is, MLD snooping is enabled
only on VLAN interfaces in the default state (enabled).
You can enable and disable MLD snooping on a per-VLAN basis or for a range of VLANs, but if you
globally disable MLD snooping, it is disabled in all VLANs. If global snooping is enabled, you can
enable or disable VLAN snooping.
Beginning in privileged EXEC mode, follow these steps to globally enable MLD snooping on the 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
end
Return to privileged EXEC mode.
Step 4
copy running-config startup-config
(Optional) Save your entries in the configuration file.
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
On a Catalyst Switch Module 3110, 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 the 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.
On a Catalyst Switch Module 3012, when the IPv6 multicast router is a Catalyst 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 switch in order for the 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
switch.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ipv6 mld snooping
Globally enable MLD snooping on the switch.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
24-7
Chapter 24
Configuring IPv6 MLD Snooping
Configuring IPv6 MLD Snooping
Step 3
Command
Purpose
ipv6 mld snooping vlan vlan-id
Enable MLD snooping on the VLAN.The VLAN ID range is 1 to
1001 and 1006 to 4094.
MLD snooping must be globally enabled for VLAN snooping
to be enabled.
Note
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.
Configuring a Static Multicast Group
Hosts or Layer 2 ports normally join multicast groups dynamically, but you can also statically configure
an IPv6 multicast address and member ports for a VLAN.
Beginning in privileged EXEC mode, follow these steps to add a Layer 2 port as a member of a multicast
group:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode
Step 2
ipv6 mld snooping vlan vlan-id static
ipv6_multicast_address interface interface-id
Statically configure a multicast group with a Layer 2 port as a
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
Step 4
show ipv6 mld snooping multicast-address user Verify the static member port and the IPv6 address.
or
show ipv6 mld snooping multicast-address vlan
vlan-id user
Step 5
copy running-config startup-config
Return to privileged EXEC mode.
(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.
This example shows how to statically configure an IPv6 multicast group:
Switch# configure terminal
Switch(config)# ipv6 mld snooping vlan 2 static FF12::3 interface gigabitethernet1/0/1
Switch(config)# end
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
24-8
OL-12189-01
Chapter 24
Configuring IPv6 MLD Snooping
Configuring IPv6 MLD Snooping
Configuring a Multicast Router Port
Although MLD snooping learns about router ports through MLD queries and PIMv6 queries, you can
also use the command-line interface (CLI) to add a multicast router port to a VLAN. To add a multicast
router port (add a static connection to a multicast router), use the ipv6 mld snooping vlan mrouter
global configuration command on the switch.
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
interface interface-id
Specify the multicast router VLAN ID, and specify the interface
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
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
Return to privileged EXEC mode.
(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/0/2
Switch(config)# exit
Enabling MLD Immediate Leave
When you enable MLDv1 Immediate Leave, the switch immediately removes a port from a multicast
group when it detects an MLD Done message on that port. You should only use the Immediate-Leave
feature when there is a single receiver present on every port in the VLAN. When there are multiple
clients for a multicast group on the same port, you should not enable Immediate-Leave in a VLAN.
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
immediate-leave
Enable MLD Immediate Leave on the VLAN interface.
Step 3
end
Return to privileged EXEC mode.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
24-9
Chapter 24
Configuring IPv6 MLD Snooping
Configuring IPv6 MLD Snooping
Command
Purpose
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
Configuring MLD Snooping Queries
When Immediate Leave is not enabled and a port receives an MLD Done message, the switch generates
MASQs on the port and sends them to the IPv6 multicast address for which the Done message was sent.
You can optionally configure the number of MASQs that are sent and the length of time the switch waits
for a response before deleting the port from the multicast group.
Beginning in privileged EXEC mode, follow these steps to configure MLD snooping query
characteristics for the switch or for a VLAN:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ipv6 mld snooping robustness-variable
value
(Optional) Set the number of queries that are sent before switch will
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
robustness-variable value
(Optional) Set the robustness variable on a VLAN basis, which
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
last-listener-query-count count
(Optional) Set the number of MASQs that the switch sends before
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
last-listener-query-count count
(Optional) Set the last-listener query count on a VLAN basis. This
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.
Step 6
ipv6 mld snooping
last-listener-query-interval interval
(Optional) Set the maximum response time that the switch waits after
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
last-listener-query-interval interval
(Optional) Set the last-listener query interval on a VLAN basis. This
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
24-10
OL-12189-01
Chapter 24
Configuring IPv6 MLD Snooping
Configuring IPv6 MLD Snooping
Command
Purpose
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
vlan-id]
(Optional) Verify that the MLD snooping querier information for the
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
Disabling MLD Listener Message Suppression
MLD snooping listener message suppression is enabled by default. When it is enabled, the switch
forwards only one MLD report per multicast router query. When message suppression is disabled,
multiple MLD reports could be forwarded to the multicast routers.
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
listener-message-suppression
Disable MLD 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
24-11
Chapter 24
Configuring IPv6 MLD Snooping
Displaying MLD Snooping Information
To re-enable MLD message suppression, use the ipv6 mld snooping listener-message-suppression
global configuration command.
Displaying MLD Snooping Information
You can display MLD snooping information for dynamically learned and statically configured router
ports and VLAN interfaces. You can also display MAC address multicast entries for a VLAN configured
for MLD snooping.
To display MLD snooping information, use one or more of the privileged EXEC commands in
Table 24-2.
Table 24-2
Commands for Displaying MLD Snooping Information
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.
show ipv6 mld snooping multicast-address [vlan Display all IPv6 multicast address information or specific IPv6
vlan-id] [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 multicast-address vlan Display MLD snooping for the specified VLAN and IPv6 multicast
vlan-id [ipv6-multicast-address]
address.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
24-12
OL-12189-01
CH A P T E R
25
Configuring Port-Based Traffic Control
This chapter describes how to configure the port-based traffic control features on the switch. Unless
otherwise noted, the term switch refers to a standalone switch and to a switch stack.
Note
For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
This chapter consists of these sections:
Configuring Storm Control, page 25-1
Configuring Protected Ports, page 25-5
Configuring Port Blocking, page 25-6
Configuring Port Security, page 25-7
Displaying Port-Based Traffic Control Settings, page 25-18
Configuring Storm Control
These sections contain this conceptual and configuration information:
Understanding Storm Control, page 25-1
Default Storm Control Configuration, page 25-3
Configuring Storm Control and Threshold Levels, page 25-3
Understanding Storm Control
Storm control prevents traffic on a LAN from being disrupted by a broadcast, multicast, or unicast storm
on one of the physical interfaces. A LAN storm occurs when packets flood the LAN, creating excessive
traffic and degrading network performance. Errors in the protocol-stack implementation, mistakes in
network configurations, or users issuing a denial-of-service attack can cause a storm.
Storm control (or traffic suppression) monitors packets passing from an interface to the switching bus
and determines if the packet is unicast, multicast, or broadcast. The switch counts the number of packets
of a specified type received within the 1-second time interval and compares the measurement with a
predefined suppression-level threshold.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
25-1
Chapter 25
Configuring Port-Based Traffic Control
Configuring Storm Control
Storm control uses one of these methods to measure traffic activity:
Bandwidth as a percentage of the total available bandwidth of the port that can be used by the
broadcast, multicast, or unicast traffic
Traffic rate in packets per second at which broadcast, multicast, or unicast packets are received
Traffic rate in bits per second at which broadcast, multicast, or unicast packets are received
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.
The graph in Figure 25-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.
Figure 25-1
Broadcast Storm Control Example
Forwarded traffic
Blocked traffic
Total
number of
broadcast
packets
or bytes
T1
T2
T3
T4
T5
Time
46651
Threshold
The combination of the storm-control suppression level and the 1-second time interval controls 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 1-second time interval during which traffic
activity is measured can affect the behavior of storm control.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
25-2
OL-12189-01
Chapter 25
Configuring Port-Based Traffic Control
Configuring Storm Control
You use the storm-control interface configuration commands to set the threshold value for each traffic
type.
Default Storm Control Configuration
By default, unicast, broadcast, and multicast storm control are disabled on the switch interfaces; that is,
the suppression level is 100 percent.
Configuring Storm Control and Threshold Levels
You configure storm control on a port and enter the threshold level that you want to be used for a
particular type of traffic.
However, because of hardware limitations and the way in which packets of different sizes are counted,
threshold percentages are approximations. Depending on the sizes of the packets making up the
incoming traffic, the actual enforced threshold might differ from the configured level by several
percentage points.
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 storm control and threshold levels:
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
25-3
Chapter 25
Configuring Port-Based Traffic Control
Configuring Storm Control
Step 3
Command
Purpose
storm-control {broadcast | multicast |
unicast} level {level [level-low] | bps bps
[bps-low] | pps pps [pps-low]}
Configure broadcast, multicast, or unicast storm control. By
default, storm control is disabled.
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
Step 5
storm-control action {shutdown | trap}
end
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.
Return to privileged EXEC mode.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
25-4
OL-12189-01
Chapter 25
Configuring Port-Based Traffic Control
Configuring Protected Ports
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
Configuring Protected Ports
Some applications require that no traffic be forwarded at Layer 2 between ports on the same switch so
that one neighbor does not see the traffic generated by another neighbor. In such an environment, the use
of protected ports ensures that there is no exchange of unicast, broadcast, or multicast traffic between
these ports on the switch.
Protected ports have these features:
A protected port does not forward any traffic (unicast, multicast, or broadcast) to any other port that
is also a protected port. Data traffic cannot be forwarded between protected ports at Layer 2; only
control traffic, such as PIM packets, is forwarded because these packets are processed by the CPU
and forwarded in software. All data traffic passing between protected ports must be forwarded
through a Layer 3 device.
Forwarding behavior between a protected port and a nonprotected port proceeds as usual.
Because a switch stack represents a single logical switch, Layer 2 traffic is not forwarded between any
protected ports in the switch stack, whether they are on the same or different switches in the stack.
These sections contain this configuration information:
Default Protected Port Configuration, page 25-5
Protected Port Configuration Guidelines, page 25-6
Configuring a Protected Port, page 25-6
Default Protected Port Configuration
The default is to have no protected ports defined.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
25-5
Chapter 25
Configuring Port-Based Traffic Control
Configuring Port Blocking
Protected Port Configuration Guidelines
You can configure protected ports on a physical interface (for example, Gigabit Ethernet port 1) or an
EtherChannel group (for example, port-channel 5). When you enable protected ports for a port channel,
it is enabled for all ports in the port-channel group.
Do not configure a private-VLAN port as a protected port. Do not configure a protected port as a
private-VLAN port. A private-VLAN isolated port does not forward traffic to other isolated ports or
community ports. For more information about private VLANs, see Chapter 15, Configuring Private
VLANs.
Configuring a Protected Port
Beginning in privileged EXEC mode, follow these steps to define a port as a protected port:
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 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 a port as a protected port:
Switch# configure terminal
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# switchport protected
Switch(config-if)# end
Configuring Port Blocking
By default, the switch floods packets with unknown destination MAC addresses out of all ports. If
unknown unicast and multicast traffic is forwarded to a protected port, there could be security issues. To
prevent unknown unicast or multicast traffic from being forwarded from one port to another, you can
block a port (protected or nonprotected) from flooding unknown unicast or multicast packets to other
ports.
These sections contain this configuration information:
Default Port Blocking Configuration, page 25-7
Blocking Flooded Traffic on an Interface, page 25-7
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
25-6
OL-12189-01
Chapter 25
Configuring Port-Based Traffic Control
Configuring Port Security
Default Port Blocking Configuration
The default is to not block flooding of unknown multicast and unicast traffic out of a port, but to flood
these packets to all ports.
Blocking Flooded Traffic on an Interface
Note
The interface can be a physical interface or an EtherChannel group. 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 multicast and unicast
packets out of an interface:
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 block multicast
Block unknown multicast forwarding out of the port.
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 multicast flooding on a port:
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
Configuring Port Security
You can use the port security feature to restrict input to an uplink interface by limiting and identifying
MAC addresses of the stations allowed to access the uplink port. When you assign secure MAC
addresses to a secure port, the port does not forward packets with source addresses outside the group of
defined addresses. If you limit the number of secure MAC addresses to one and assign a single secure
MAC address, the workstation attached to that port is assured the full bandwidth of the port.
If a uplink port is configured as a secure port and the maximum number of secure MAC addresses is
reached, when the MAC address of a station attempting to access the port is different from any of the
identified secure MAC addresses, a security violation occurs. Also, if a station with a secure MAC
address configured or learned on one secure port attempts to access another secure port, a violation is
flagged.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
25-7
Chapter 25
Configuring Port-Based Traffic Control
Configuring Port Security
These sections contain this conceptual and configuration information:
Understanding Port Security, page 25-8
Default Port Security Configuration, page 25-10
Port Security Configuration Guidelines, page 25-10
Enabling and Configuring Port Security, page 25-12
Enabling and Configuring Port Security Aging, page 25-16
Port Security and Switch Stacks, page 25-17
Port Security and Private VLANs, page 25-17
Understanding Port Security
These sections contain this conceptual information:
Secure MAC Addresses, page 25-8
Security Violations, page 25-9
Secure MAC Addresses
You configure the maximum number of secure addresses allowed on an uplink port by using the
switchport port-security maximum value interface configuration command.
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 switch supports these types of secure MAC addresses:
Static secure MAC addressesThese are manually configured by using the switchport
port-security mac-address mac-address interface configuration command, stored in the address
table, and added to the switch running configuration.
Dynamic secure MAC addressesThese are dynamically configured, stored only in the address
table, and removed when the switch restarts.
Sticky secure MAC addressesThese can be dynamically learned or manually configured, stored in
the address table, and added to the running configuration. If these addresses are saved in the
configuration file, when the switch restarts, the interface does not need to dynamically reconfigure
them.
You can configure an interface to convert the dynamic MAC addresses to sticky secure MAC addresses
and to add them to the running configuration by enabling sticky learning. To enable sticky learning, enter
the switchport port-security mac-address sticky interface configuration command. When you enter
this command, the interface converts all the dynamic secure MAC addresses, including those that were
dynamically learned before sticky learning was enabled, to sticky secure MAC addresses. All sticky
secure MAC addresses are added to the running configuration.
The sticky secure MAC addresses do not automatically become part of the configuration file, which is
the startup configuration used each time the switch restarts. If you save the sticky secure MAC addresses
in the configuration file, when the switch restarts, the interface does not need to relearn these addresses.
If you do not save the sticky secure addresses, they are lost.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
25-8
OL-12189-01
Chapter 25
Configuring Port-Based Traffic Control
Configuring Port Security
If sticky learning is disabled, the sticky secure MAC addresses are converted to dynamic secure
addresses and are removed from the running configuration.
The maximum number of secure MAC addresses that you can configure on a switch or switch stack is
set 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 8, Configuring
SDM Templates. This number is 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:
protectwhen 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.
restrictwhen 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.
shutdowna 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.
shutdown vlanUse to set the security violation mode per-VLAN. In this mode, the VLAN is error
disabled instead of the entire port when a violation occurs
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
25-9
Chapter 25
Configuring Port-Based Traffic Control
Configuring Port Security
Table 25-1 shows the violation mode and the actions taken when you configure an interface for port
security.
Table 25-1
Security Violation Mode Actions
Violation Mode
Traffic is
forwarded1
Sends SNMP
trap
Sends syslog
message
Displays error
message2
Violation
counter
increments
Shuts down port
protect
No
No
No
No
No
No
restrict
No
Yes
Yes
No
Yes
No
shutdown
No
Yes
Yes
No
Yes
Yes
shutdown vlan
No
Yes
Yes
No
Yes
No3
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.
3. Shuts down only the VLAN on which the violation occurred.
Default Port Security Configuration
Table 25-2 shows the default port security configuration for an interface.
Table 25-2
Default Port Security Configuration
Feature
Default Setting
Port security
Disabled on a port.
Sticky address learning
Disabled.
Maximum number of secure
MAC addresses per port
1.
Violation mode
Shutdown. The port shuts down when the maximum number of
secure MAC addresses is exceeded.
Port security aging
Disabled. Aging time is 0.
Static aging is disabled.
Type is absolute.
Port Security Configuration Guidelines
Follow these guidelines when configuring port security:
Port security can only be configured on static access ports or trunk 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 Gigabit EtherChannel port group.
Note
Voice VLAN is only supported on access ports and not on trunk ports, even though the
configuration is allowed.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
25-10
OL-12189-01
Chapter 25
Configuring Port-Based Traffic Control
Configuring Port Security
A secure port cannot be a private-VLAN port.
When you enable port security on an interface that is also configured with a voice VLAN, set the
maximum allowed secure addresses on the port to two. When the port is connected to a Cisco IP
phone, the IP phone requires one MAC address. The Cisco IP phone address is learned on the voice
VLAN, but is not learned on the access VLAN. If you connect a single PC to the Cisco IP phone,
no additional MAC addresses are required. If you connect more than one PC to the Cisco IP phone,
you must configure enough secure addresses to allow one for each PC and one for the phone.
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.
Table 25-3 summarizes port security compatibility with other port-based features.
Table 25-3
Port Security Compatibility with Other Switch Features
Type of Port or Feature on Port
1
DTP port
Compatible with Port Security
No
Trunk port
Yes
Dynamic-access port3
No
Routed port
No
SPAN source port
Yes
SPAN destination port
No
EtherChannel
No
Tunneling port
Yes
Protected port
Yes
IEEE 802.1x port
Yes
Voice VLAN port4
Yes
Private VLAN port
No
IP source guard
Yes
Dynamic Address Resolution Protocol (ARP) inspection
Yes
Flex Links
Yes
1. DTP = Dynamic Trunking Protocol
2. A port configured with the switchport mode dynamic interface configuration command.
3. A VLAN Query Protocol (VQP) port configured with the switchport access vlan dynamic interface configuration command.
4. 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
25-11
Chapter 25
Configuring Port-Based Traffic Control
Configuring Port Security
Enabling and Configuring Port Security
Beginning in privileged EXEC mode, follow these steps to restrict input to an interface by limiting and
identifying MAC addresses of the stations allowed to access the port:
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 {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 voice vlan vlan-id
Enable voice VLAN on a port.
vlan-idSpecify the VLAN to be used for voice traffic.
Step 5
switchport port-security
Enable port security on the interface.
Step 6
switchport port-security
[maximum value [vlan {vlan-list |
{access | voice}}]]
(Optional) Set the maximum number of secure MAC addresses for the
interface. The maximum number of secure MAC addresses that you can
configure on a switch or switch stack is set by the maximum number of
available MAC addresses allowed in the system. This number is set by the
active Switch Database Management (SDM) template. See Chapter 8,
Configuring the Switch SDM Template. This number is the total of
available MAC addresses, including those used for other Layer 2 functions
and any other secure MAC addresses configured on interfaces.
(Optional) vlanset a per-VLAN maximum value
Enter one of these options after you enter the vlan keyword:
vlan-listOn a trunk port, you can set a per-VLAN maximum value on
a range of VLANs separated by a hyphen or a series of VLANs separated
by commas. For nonspecified VLANs, the per-VLAN maximum value is
used.
accessOn an access port, specify the VLAN as an access VLAN.
voiceOn an access port, specify the VLAN as a voice VLAN.
Note
The voice keyword is available only if a voice VLAN is configured on
a port and if that port is not the access VLAN. If an interface is
configured for voice VLAN, configure a maximum of two secure
MAC addresses.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
25-12
OL-12189-01
Chapter 25
Configuring Port-Based Traffic Control
Configuring Port Security
Step 7
Command
Purpose
switchport port-security violation
{protect | restrict | shutdown |
shutdown vlan}
(Optional) Set the violation mode, the action to be taken when a security
violation is detected, as one of these:
Note
protectWhen 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.
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.
restrictWhen the number of secure MAC addresses reaches the limit
allowed on the port, packets with unknown source addresses are dropped
until you remove a sufficient number of secure MAC addresses or
increase the number of maximum allowable addresses. An SNMP trap is
sent, a syslog message is logged, and the violation counter increments.
shutdownThe interface is error-disabled when a violation occurs, and
the port LED turns off. An SNMP trap is sent, a syslog message is logged,
and the violation counter increments.
shutdown vlanUse to set the security violation mode per VLAN. In
this mode, the VLAN is error disabled instead of the entire port when a
violation occurs.
Note
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. You can manually
re-enable it by entering the shutdown and no shutdown interface
configuration commands or by using the clear errdisable interface
vlan privileged EXEC command.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
25-13
Chapter 25
Configuring Port-Based Traffic Control
Configuring Port Security
Step 8
Command
Purpose
switchport port-security
[mac-address mac-address [vlan
{vlan-id | {access | voice}}]
(Optional) Enter a secure MAC address for the interface. You can use this
command to enter the maximum number of secure MAC addresses. If you
configure fewer secure MAC addresses than the maximum, the remaining
MAC addresses are dynamically learned.
Note
If you enable sticky learning after you enter this command, the secure
addresses that were dynamically learned are converted to sticky
secure MAC addresses and are added to the running configuration.
(Optional) vlanset a per-VLAN maximum value.
Enter one of these options after you enter the vlan keyword:
vlan-idOn a trunk port, you can specify the VLAN ID and the MAC
address. If you do not specify a VLAN ID, the native VLAN is used.
accessOn an access port, specify the VLAN as an access VLAN.
voiceOn an access port, specify the VLAN as a voice VLAN.
Note
The voice keyword is available only if a voice VLAN is configured on
a port and if that port is not the access VLAN. If an interface is
configured for voice VLAN, configure a maximum of two secure
MAC addresses.
Step 9
switchport port-security
mac-address sticky
(Optional) Enable sticky learning on the interface.
Step 10
switchport port-security
mac-address sticky [mac-address |
vlan {vlan-id | {access | voice}}]
(Optional) Enter a sticky secure MAC address, repeating the command as
many times as necessary. If you configure fewer secure MAC addresses than
the maximum, the remaining MAC addresses are dynamically learned, are
converted to sticky secure MAC addresses, and are added to the running
configuration.
Note
If you do not enable sticky learning before this command is entered,
an error message appears, and you cannot enter a sticky secure MAC
address.
(Optional) vlanset a per-VLAN maximum value.
Enter one of these options after you enter the vlan keyword:
vlan-idOn a trunk port, you can specify the VLAN ID and the MAC
address. If you do not specify a VLAN ID, the native VLAN is used.
accessOn an access port, specify the VLAN as an access VLAN.
voiceOn an access port, specify the VLAN as a voice VLAN.
Note
The voice keyword is available only if a voice VLAN is configured on
a port and if that port is not the access VLAN.
Step 11
end
Return to privileged EXEC mode.
Step 12
show port-security
Verify your entries.
Step 13
copy running-config
startup-config
(Optional) Save your entries in the configuration file.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
25-14
OL-12189-01
Chapter 25
Configuring Port-Based Traffic Control
Configuring Port Security
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.
Use the clear port-security {all | configured | dynamic | sticky} privileged EXEC command to delete
from the MAC address table all secure addresses or all secure addresses of a specific type (configured,
dynamic, or sticky) on the switch or on an interface.
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 a port 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 a port:
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
This example shows how to enable sticky port security on a port, to manually configure MAC addresses
for data VLAN and voice VLAN, and to set the total maximum number of secure addresses to 20 (10 for
data VLAN and 10 for voice VLAN).
Switch(config)# interface tengigabitethernet1/0/1
Switch(config-if)# switchport access vlan 21
Switch(config-if)# switchport mode access
Switch(config-if)# switchport voice vlan 22
Switch(config-if)# switchport port-security
Switch(config-if)# switchport port-security maximum 20
Switch(config-if)# switchport port-security violation restrict
Switch(config-if)# switchport port-security mac-address sticky
Switch(config-if)# switchport port-security mac-address sticky 0000.0000.0002
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
25-15
Chapter 25
Configuring Port-Based Traffic Control
Configuring Port Security
Switch(config-if)#
Switch(config-if)#
Switch(config-if)#
Switch(config-if)#
Switch(config-if)#
switchport
switchport
switchport
switchport
switchport
port-security
port-security
port-security
port-security
port-security
mac-address 0000.0000.0003
mac-address sticky 0000.0000.0001 vlan voice
mac-address 0000.0000.0004 vlan voice
maximum 10 vlan access
maximum 10 vlan voice
Enabling and Configuring Port Security Aging
You can use port security aging to set the aging time for all secure addresses on a port. Two types of
aging are supported per port:
AbsoluteThe secure addresses on the port are deleted after the specified aging time.
InactivityThe secure addresses on the port are deleted only if the secure addresses are inactive for
the specified aging time.
Use this feature to remove and add devices on a secure port without manually deleting the existing secure
MAC addresses and to still limit the number of secure addresses on a port. You can enable or disable the
aging of secure addresses on a per-port basis.
Beginning in privileged EXEC mode, follow these steps to configure port security aging:
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 port-security aging {static | time time |
type {absolute | inactivity}}
Enable or disable static aging for the secure port, or set the
aging time or type.
Note
The switch does not support port security aging of
sticky secure addresses.
Enter static to enable aging for statically configured secure
addresses on this port.
For time, specify the aging time for this port. The valid range is
from 0 to 1440 minutes.
For type, select one of these keywords:
absoluteSets the aging type as absolute aging. All the
secure addresses on this port age out exactly after the time
(minutes) specified lapses and are removed from the secure
address list.
inactivitySets the aging type as inactivity aging. The
secure addresses on this port age out only if there is no data
traffic from the secure source addresses for the specified
time period.
Step 4
end
Return to privileged EXEC mode.
Step 5
show port-security [interface interface-id]
[address]
Verify your entries.
Step 6
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
25-16
OL-12189-01
Chapter 25
Configuring Port-Based Traffic Control
Configuring Port Security
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 a port:
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.
Port Security and Switch Stacks
When a switch joins a stack, the new switch will get the configured secure addresses. All dynamic secure
addresses are downloaded by the new stack member from the other stack members.
When a switch (either the stack master or a stack member) leaves the stack, the remaining stack members
are notified, and the secure MAC addresses configured or learned by that switch are deleted from the
secure MAC address table. For more information about switch stacks, see Chapter 5, Managing Switch
Stacks.
Port Security and Private VLANs
Port security allows an administrator to limit the number of MAC addresses learned on a port or to define
which MAC addresses can be learned on a port.
Beginning in privileged EXEC mode, follow these steps to configure port security on a PVLAN host and
promiscuous ports:
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]
[address]
Verify your entries.
Step 7
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
25-17
Chapter 25
Configuring Port-Based Traffic Control
Displaying Port-Based Traffic Control Settings
This example shows how to configure port security on a PVLAN host and promiscuous ports
Switch(config)# interface gigabitethernet 1/0/8
Switch(config-if)# switchport private-vlan mapping 2061 2201-2206,3101
Switch(config-if)# switchport mode private-vlan promiscuous
Switch(config-if)# switchport port-security maximum 288
Switch(config-if)# switchport port-security
Switch(config-if)# switchport port-security violation restrict
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
unsecure 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 storm control and port security settings.
To display traffic control information, use one or more of the privileged EXEC commands in Table 25-4.
Table 25-4
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 |
multicast | unicast]
Displays storm control suppression levels set on all interfaces or the
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
25-18
OL-12189-01
CH A P T E R
26
Configuring CDP
This chapter describes how to configure Cisco Discovery Protocol (CDP) on the switch. Unless
otherwise noted, the term switch refers to a standalone switch and to a switch stack.
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.
This chapter consists of these sections:
Understanding CDP, page 26-1
Configuring CDP, page 26-2
Monitoring and Maintaining CDP, page 26-5
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.
On the switch, CDP enables SNMP management applications to display a graphical view of the network.
The switch supports CDP Version 2.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
26-1
Chapter 26
Configuring CDP
Configuring CDP
CDP and Switch Stacks
A switch stack appears as a single switch in the network. Therefore, CDP discovers the switch stack, not
the individual stack members. The switch stack sends CDP messages to neighboring network devices
when there are changes to the switch stack membership, such as stack members being added or removed.
Configuring CDP
These sections contain this configuration information:
Default CDP Configuration, page 26-2
Configuring the CDP Characteristics, page 26-2
Disabling and Enabling CDP, page 26-3
Disabling and Enabling CDP on an Interface, page 26-4
Default CDP Configuration
Table 26-1 shows the default CDP configuration.
Table 26-1
Default CDP Configuration
Feature
Default Setting
CDP global state
Enabled
CDP interface state
Enabled
CDP timer (packet update frequency)
60 seconds
CDP holdtime (before discarding)
180 seconds
CDP Version-2 advertisements
Enabled
Configuring the CDP Characteristics
You can configure the frequency of CDP updates, the amount of time to hold the information before
discarding it, and whether or not to send Version-2 advertisements.
Beginning in privileged EXEC mode, follow these steps to configure the CDP timer, holdtime, and
advertisement type.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
26-2
OL-12189-01
Chapter 26
Configuring CDP
Configuring CDP
Step 3
Command
Purpose
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 your settings.
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 CDP characteristics.
Switch# configure terminal
Switch(config)# cdp timer 50
Switch(config)# cdp holdtime 120
Switch(config)# cdp advertise-v2
Switch(config)# end
For additional CDP show commands, see the Monitoring and Maintaining CDP section on page 26-5.
Disabling and Enabling CDP
CDP is enabled by default.
Beginning in privileged EXEC mode, follow these steps to disable the CDP device discovery capability:
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.
This example shows how to enable CDP if it has been disabled.
Switch# configure terminal
Switch(config)# cdp run
Switch(config)# end
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
26-3
Chapter 26
Configuring CDP
Configuring CDP
Disabling and Enabling CDP on an Interface
CDP is enabled by default on all supported interfaces to send and to receive CDP information.
Beginning in privileged EXEC mode, follow these steps to disable CDP on a port:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
interface interface-id
Specify the interface on which you are disabling CDP, and enter
interface configuration mode.
Step 3
no cdp enable
Disable CDP on the 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 a port 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 CDP, and enter
interface configuration mode.
Step 3
cdp enable
Enable CDP on the 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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
26-4
OL-12189-01
Chapter 26
Configuring CDP
Monitoring and Maintaining CDP
Monitoring and Maintaining CDP
To monitor and maintain CDP on your device, use one or more of the privileged EXEC commands in
Table 26-2.
Table 26-2
Commands for Displaying CDP Information
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
[protocol | version]
Display information about a specific neighbor.
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.
You can limit the display to the interface about which you want information.
show cdp neighbors [interface-id]
[detail]
Display information about neighbors, including device type, interface type and
number, holdtime settings, capabilities, platform, and port ID.
You can limit the display to neighbors of 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
26-5
Chapter 26
Configuring CDP
Monitoring and Maintaining CDP
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
26-6
OL-12189-01
CH A P T E R
27
Configuring LLDP and LLDP-MED
This chapter describes how to configure the Link Layer Discovery Protocol (LLDP) and LLDP Media
Endpoint Discovery (LLDP-MED) on the switch. Unless otherwise noted, the term switch refers to a
standalone switch and to a switch stack.
Note
For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release and the Carrier Ethernet s Command Reference at this URL:
http://www.cisco.com/en/US/docs/ios/cether/command/reference/ce_02.html
This chapter consists of these sections:
Understanding LLDP and LLDP-MED, page 27-1
Configuring LLDP and LLDP-MED, page 27-3
Monitoring and Maintaining LLDP and LLDP-MED, page 27-7
Understanding LLDP and LLDP-MED
This section contains this conceptual information:
Understanding LLDP, page 27-1
Understanding LLDP-MED, page 27-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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
27-1
Chapter 27
Configuring LLDP and LLDP-MED
Understanding LLDP and LLDP-MED
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.
Note
Port VLAN ID TLV ((IEEE 802.1 organizationally specific TLVs)
MAC/PHY configuration/status TLV(IEEE 802.3 organizationally specific TLVs)
A switch stack appears as a single switch in the network. Therefore, LLDP discovers the switch stack,
not the individual stack members.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
27-2
OL-12189-01
Chapter 27
Configuring LLDP and LLDP-MED
Configuring LLDP and LLDP-MED
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.
ELIN location information
Provides the location information of a caller. The location is determined by the Emergency
location identifier number (ELIN), which is a phone number that routes an emergency call to
the local public safety answering point (PSAP) and which the PSAP can use to call back the
emergency caller.
Note
LLDP and LLDP-MED cannot operate simultaneously in a network. By default, a network device sends
only LLDP packets until it receives LLDP-MED packets from an endpoint device. The network device
then sends LLDP-MED packets until it receives only LLDP packets.
Configuring LLDP and LLDP-MED
This section contains this configuration information:
Default LLDP Configuration, page 27-3
Configuring LLDP Characteristics, page 27-4
Disabling and Enabling LLDP Globally, page 27-4
Disabling and Enabling LLDP on an Interface, page 27-5
Configuring LLDP-MED TLVs, page 27-6
Default LLDP Configuration
Table 27-1 shows the default LLDP configuration. To change the default settings, use the LLDP global
configuration and LLDP interface configuration commands.
Table 27-1
Default LLDP Configuration
Feature
Default Setting
LLDP global state
Enabled
LLDP holdtime (before discarding)
120 seconds
LLDP timer (packet update frequency)
30 seconds
LLDP reinitialization delay
2 seconds
LLDP tlv-select
Enabled to send and receive all TLVs.
LLDP interface state
Enabled
LLDP receive
Enabled
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
27-3
Chapter 27
Configuring LLDP and LLDP-MED
Configuring LLDP and LLDP-MED
Table 27-1
Default LLDP Configuration (continued)
Feature
Default Setting
LLDP transmit
Enabled
LLDP med-tlv-select
Enabled to send all LLDP-MED TLVs
Configuring LLDP Characteristics
You can configure the frequency of LLDP updates, the amount of time to hold the information before
discarding it, and the initialization delay time. You can also select the LLDP and LLDP-MED TLVs to
be sent and received.
Beginning in privileged EXEC mode, follow these steps to configure these characteristics:
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
lldp med-tlv-select
(Optional) Specify the LLDP-MED TLVs to send or receive.
Step 7
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 27-7.
Disabling and Enabling LLDP Globally
LLDP is enabled by default.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
27-4
OL-12189-01
Chapter 27
Configuring LLDP and LLDP-MED
Configuring LLDP and LLDP-MED
Beginning in privileged EXEC mode, follow these steps to globally disable LLDP:
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 globally 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.
This example shows how to globally disable LLDP.
Switch# configure terminal
Switch(config)# no lldp run
Switch(config)# end
This example shows how to globally enable LLDP.
Switch# configure terminal
Switch(config)# lldp run
Switch(config)# end
Disabling and Enabling LLDP on an Interface
LLDP is enabled by default on all supported interfaces to send and to receive LLDP information.
Note
If the interface is configured as a tunnel port, LLDP is automatically disabled.
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.
Step 5
end
Return to privileged EXEC mode.
Step 6
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
27-5
Chapter 27
Configuring LLDP and LLDP-MED
Configuring LLDP and LLDP-MED
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.
This example shows how to enable LLDP on an interface.
Switch# configure terminal
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# lldp transmit
Switch(config-if)# lldp receive
Switch(config-if)# end
Configuring LLDP-MED TLVs
By default, the switch only sends LLDP packets until it receives LLDP-MED packets from the end
device. The device continues to send LLDP-MED packets until it only receives LLDP packets.
Using the lldp interface configuration command, you can configure the interface not to send these TLVs:
Table 27-2
LLDP-MED TLVs
LLDP-MED TLV
Description
inventory-management
LLDP-MED inventory management TLV
location
LLDP-MED location TLV
network-policy
LLDP-MED network policy TLV
power-management
LLDP-MED power management TLV
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
27-6
OL-12189-01
Chapter 27
Configuring LLDP and LLDP-MED
Monitoring and Maintaining LLDP and LLDP-MED
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
Monitoring and Maintaining LLDP and LLDP-MED
To monitor and maintain LLDP and LLDP-MED on your device, perform one or more of these tasks,
beginning in privileged EXEC mode.
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.
show lldp neighbors [interface-id]
[detail]
Display information about neighbors, including device type, interface type and
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
27-7
Chapter 27
Configuring LLDP and LLDP-MED
Monitoring and Maintaining LLDP and LLDP-MED
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
27-8
OL-12189-01
CH A P T E R
28
Configuring UDLD
This chapter describes how to configure the UniDirectional Link Detection (UDLD) protocol on the
switch. Unless otherwise noted, the term switch refers to a standalone switch and to a switch stack.
Note
For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
This chapter consists of these sections:
Understanding UDLD, page 28-1
Configuring UDLD, page 28-3
Displaying UDLD Status, page 28-7
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 disables the affected port 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 can also detect unidirectional links due to one-way traffic on fiber-optic and twisted-pair links
and to misconnected ports on fiber-optic links.
In normal and aggressive modes, 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 ports. 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
28-1
Chapter 28
Configuring UDLD
Understanding UDLD
In normal mode, UDLD detects 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 port.
When UDLD is in normal mode, if one of the fiber strands in a pair is disconnected and autonegotiation
is active, the link does not stay up because the Layer 1 mechanisms did not detect 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 detects a unidirectional link by using the previous detection methods. UDLD
in aggressive mode can also detect a unidirectional link on a point-to-point link on which no failure
between the two devices is allowed. It can also detect a unidirectional link when one of these problems
exists:
On fiber-optic or twisted-pair links, one of the ports cannot send or receive traffic.
On fiber-optic or twisted-pair links, one of the ports is down while the other is up.
One of the fiber strands in the cable is disconnected.
In these cases, UDLD disables the affected port.
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 fiber strands in a cable are working normally from a Layer 1 perspective, UDLD in aggressive
mode detects whether those fiber strands 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.
Methods to Detect Unidirectional Links
UDLD operates by using two mechanisms:
Neighbor database maintenance
UDLD learns about other UDLD-capable neighbors by periodically sending a hello packet (also
called an advertisement or probe) on every active port to keep each device informed about its
neighbors.
When the switch receives a hello message, it caches the information until the age time (hold time or
time-to-live) expires. If the switch receives a new hello message before an older cache entry ages,
the switch replaces the older entry with the new one.
Whenever a port is disabled and UDLD is running, whenever UDLD is disabled on a port, or
whenever the switch is reset, UDLD clears all existing cache entries for the ports affected by the
configuration change. UDLD sends at least one message to inform the neighbors to flush the part of
their caches affected by the status change. The message is intended to keep the caches synchronized.
Event-driven detection and echoing
UDLD relies on echoing as its detection mechanism. Whenever a UDLD device learns about a new
neighbor or receives a resynchronization request from an out-of-sync neighbor, it restarts the
detection window on its side of the connection and sends echo messages in reply. Because this
behavior is the same on all UDLD neighbors, the sender of the echoes expects to receive an echo in
reply.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
28-2
OL-12189-01
Chapter 28
Configuring UDLD
Configuring UDLD
If the detection window ends and no valid reply message is received, the link might shut down,
depending on the UDLD mode. When UDLD is in normal mode, the link might be considered
undetermined and might not be shut down. When UDLD is in aggressive mode, the link is
considered unidirectional, and the port is disabled.
If UDLD in normal mode is in the advertisement or in the detection phase and all the neighbor cache
entries are aged out, UDLD restarts the link-up sequence to resynchronize with any potentially
out-of-sync neighbors.
If you enable aggressive mode when all the neighbors of a port have aged out either in the advertisement
or in the detection phase, UDLD restarts the link-up sequence to resynchronize with any potentially
out-of-sync neighbor. UDLD shuts down the port if, after the fast train of messages, the link state is still
undetermined.
Figure 28-1 shows an example of a unidirectional link condition.
Figure 28-1
UDLD Detection of a Unidirectional Link
Switch A
RX
Switch B successfully
receives traffic from
Switch A on this port.
TX
RX
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.
Switch B
98648
TX
Configuring UDLD
These sections contain this configuration information:
Default UDLD Configuration, page 28-4
Configuration Guidelines, page 28-4
Enabling UDLD Globally, page 28-5
Enabling UDLD on an Interface, page 28-6
Resetting an Interface Disabled by UDLD, page 28-6
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
28-3
Chapter 28
Configuring UDLD
Configuring UDLD
Default UDLD Configuration
Table 28-1 shows the default UDLD configuration.
Table 28-1
Default UDLD Configuration
Feature
Default Setting
UDLD global enable state
Globally disabled
UDLD per-port enable state for fiber-optic media
Disabled on all Ethernet fiber-optic ports
UDLD per-port enable state for twisted-pair (copper) media
Disabled on all Ethernet 10/100 and 1000BASE-TX ports
UDLD aggressive mode
Disabled
Configuration Guidelines
These are the UDLD configuration guidelines:
Caution
UDLD is not supported on ATM ports.
A UDLD-capable port cannot detect a unidirectional link if it is connected to a UDLD-incapable
port of another switch.
When configuring the mode (normal or aggressive), make sure that the same mode is configured on
both sides of the link.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
28-4
OL-12189-01
Chapter 28
Configuring UDLD
Configuring UDLD
Enabling UDLD Globally
Beginning in privileged EXEC mode, follow these steps to enable UDLD in the aggressive or normal
mode and to set the configurable message timer on all fiber-optic ports on the switch and all members
in the switch stack:
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}
aggressiveEnables UDLD in aggressive mode on all fiber-optic
ports.
enableEnables 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 28-1.
message time message-timer-intervalConfigures the period of
time between UDLD probe messages on ports that are in the
advertisement phase and are detected to be bidirectional. The range
is from 1 to 90 seconds.
Note
The global UDLD setting is automatically applied to switches
that join the switch stack.
Note
This command affects fiber-optic ports only. Use the udld
interface configuration command to enable UDLD on other port
types. For more information, see the Enabling UDLD on an
Interface section on page 28-6.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
28-5
Chapter 28
Configuring UDLD
Configuring UDLD
Enabling UDLD on an Interface
Beginning in privileged EXEC mode, follow these steps either to enable UDLD in the aggressive or
normal mode or to disable UDLD on a port:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
interface interface-id
Specify the port to be enabled for UDLD, and enter interface
configuration mode.
Step 3
udld port [aggressive]
UDLD is disabled by default.
Note
When a switch joins a switch stack, it retains its
interface-specific UDLD settings.
udld portEnables UDLD in normal mode on the specified port.
udld port aggressiveEnables UDLD in aggressive mode on the
specified port.
Note
Use the no udld port interface configuration command to
disable UDLD on a specified fiber-optic port.
For more information about aggressive and normal modes, see the
Modes of Operation section on page 28-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.
Resetting an Interface Disabled by UDLD
Beginning in privileged EXEC mode, follow these steps to reset all ports disabled by UDLD:
Command
Purpose
Step 1
udld reset
Reset all ports disabled by UDLD.
Step 2
show udld
Verify your entries.
You can also bring up the port by using these commands:
The shutdown interface configuration command followed by the no shutdown interface
configuration command restarts the disabled port.
The no udld {aggressive | enable} global configuration command followed by the udld
{aggressive | enable} global configuration command re-enables the disabled ports.
The no udld port interface configuration command followed by the udld port [aggressive]
interface configuration command re-enables the disabled fiber-optic port.
The errdisable recovery cause udld global configuration command enables the timer to
automatically recover from the UDLD error-disabled state, and the errdisable recovery interval
interval global configuration command specifies the time to recover from the UDLD error-disabled
state.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
28-6
OL-12189-01
Chapter 28
Configuring UDLD
Displaying UDLD Status
Displaying UDLD Status
To display the UDLD status for the specified port or for all ports, use the show udld [interface-id]
privileged EXEC command.
For detailed information about the fields in the command output, see the command reference for this
release.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
28-7
Chapter 28
Configuring UDLD
Displaying UDLD Status
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
28-8
OL-12189-01
CH A P T E R
29
Configuring SPAN and RSPAN
This chapter describes how to configure Switched Port Analyzer (SPAN) and Remote SPAN (RSPAN)
on the switch. Unless otherwise noted, the term switch refers to a standalone switch and to a switch stack.
Note
For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
This chapter consists of these sections:
Understanding SPAN and RSPAN, page 29-1
Configuring SPAN and RSPAN, page 29-10
Displaying SPAN and RSPAN Status, page 29-23
Understanding SPAN and RSPAN
You can analyze network traffic passing through ports or VLANs by using SPAN or RSPAN to send a
copy of the traffic to another port on the switch or on another switch that has been connected to a network
analyzer or other monitoring or security device. SPAN copies (or mirrors) traffic received or sent (or
both) on source ports or source VLANs to a destination port for analysis. SPAN does not affect the
switching of network traffic on the source ports or VLANs. You must dedicate the destination port for
SPAN use. Except for traffic that is required for the SPAN or RSPAN session, destination ports do not
receive or forward traffic.
Only traffic that enters or leaves source ports or traffic that enters or leaves source VLANs can be
monitored by using SPAN; traffic routed to a source VLAN cannot be monitored. For example, if
incoming traffic is being monitored, traffic that gets routed from another VLAN to the source VLAN
cannot be monitored; however, traffic that is received on the source VLAN and routed to another VLAN
can be monitored.
You can use the SPAN or RSPAN destination port to inject traffic from a network security device. For
example, if you connect a Cisco Intrusion Detection System (IDS) sensor appliance to a destination port,
the IDS device can send TCP reset packets to close down the TCP session of a suspected attacker.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
29-1
Chapter 29
Configuring SPAN and RSPAN
Understanding SPAN and RSPAN
These sections contain this conceptual information:
Local SPAN, page 29-2
Remote SPAN, page 29-3
SPAN and RSPAN Concepts and Terminology, page 29-4
SPAN and RSPAN Interaction with Other Features, page 29-9
SPAN and RSPAN and Switch Stacks, page 29-10
Local SPAN
Local SPAN supports a SPAN session entirely within one switch; all source ports or source VLANs and
destination ports are in the same switch or switch stack. 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 29-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.
Figure 29-1
Example of Local SPAN Configuration on a Single Switch
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
6 7 8 9
10
11 12 13 14
15
16
148958
Port 5 traffic mirrored
on Port 10
Network analyzer
Figure 29-2 is an example of a local SPAN in a switch stack, where the source and destination ports
reside on different stack members.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
29-2
OL-12189-01
Chapter 29
Configuring SPAN and RSPAN
Understanding SPAN and RSPAN
Figure 29-2
Example of Local SPAN Configuration on a Switch Stack
Blade switch stack
Switch 1
1/0/4
Port 4 on switch 1 in the stack
mirrored on port 15 on switch 2
2/0/15
Network
analyzer
Switch 2
Switch 3
202310
Stackwise Plus
port
connections
Remote SPAN
RSPAN supports source ports, source VLANs, and destination ports on different switches (or different
switch stacks), enabling remote monitoring of multiple switches across your network. Figure 29-3 shows
source ports on Switch A and Switch B. 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, as shown on Switch C in the figure.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
29-3
Chapter 29
Configuring SPAN and RSPAN
Understanding SPAN and RSPAN
Figure 29-3
Example of RSPAN Configuration
RSPAN
destination ports
RSPAN
destination
session
Switch C
Intermediate switches
must support RSPAN VLAN
RSPAN
VLAN
RSPAN
source
session A
RSPAN
source ports
Switch B
RSPAN
source
session B
RSPAN
source ports
101366
Switch A
SPAN and RSPAN Concepts and Terminology
This section describes concepts and terminology associated with SPAN and RSPAN configuration.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
29-4
OL-12189-01
Chapter 29
Configuring SPAN and RSPAN
Understanding SPAN and RSPAN
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 respond to the
requirements of the RSPAN VLAN (see the RSPAN VLAN section on page 29-9).
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 local SPAN or RSPAN source sessions.
You can run both a local SPAN and an RSPAN source session in the same switch or switch stack.
The switch or switch stack supports a total of 66 source and RSPAN destination sessions.
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.
You can have multiple destination ports in a SPAN session, but no more than 64 destination ports
per switch stack.
SPAN sessions do not interfere with the normal operation of the switch. However, an oversubscribed
SPAN destination, for example, a 10-Mb/s port monitoring a 100-Mb/s port, can result in dropped
or lost packets.
When SPAN or RSPAN is enabled, each packet being monitored is sent 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.
An RSPAN source session cannot have a local destination port.
An RSPAN destination session cannot have a local source port.
An RSPAN destination session and an RSPAN source session that are using the same RSPAN
VLAN cannot run on the same switch or switch stack.
Monitored Traffic
SPAN sessions can monitor these traffic types:
Receive (Rx) SPANThe 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
29-5
Chapter 29
Configuring SPAN and RSPAN
Understanding SPAN and RSPAN
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) SPANThe 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 routingfor example, with modified time-to-live (TTL),
MAC-address, or QoS valuesare 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.
BothIn 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 encapsulationuntagged, Inter-Switch Link
(ISL), or IEEE 802.1Qthat 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,
ISL, and IEEE 802.1Q 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. You cannot mix ports and VLANs in a single session.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
29-6
OL-12189-01
Chapter 29
Configuring SPAN and RSPAN
Understanding SPAN and RSPAN
A source port has these characteristics:
It can be monitored in multiple SPAN sessions.
Each source port can be configured with a direction (ingress, egress, or both) to monitor.
It can be any port type (for example, EtherChannel, Gigabit Ethernet, and so forth).
For EtherChannel sources, you can monitor traffic for the entire EtherChannel or individually on a
physical port as it participates in the port channel.
It can be an access port, trunk port, routed port, or voice VLAN port.
It cannot be a destination port.
Source ports can be in the same or different VLANs.
You can monitor multiple source ports 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 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
29-7
Chapter 29
Configuring SPAN and RSPAN
Understanding SPAN and RSPAN
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 or switch stack 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 or switch stack 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.
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 or switch stack 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, ISL, or IEEE
802.1Q-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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
29-8
OL-12189-01
Chapter 29
Configuring SPAN and RSPAN
Understanding SPAN and RSPAN
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.
SPAN and RSPAN Interaction with Other Features
SPAN interacts with these features:
RoutingSPAN does not monitor routed traffic. VSPAN only monitors traffic that enters or exits
the switch, not traffic that is routed between VLANs. For example, if a VLAN is being
Rx-monitored and the switch routes traffic from another VLAN to the monitored VLAN, that traffic
is not monitored and not received on the SPAN destination port.
STPA destination port does not participate in STP while its SPAN or RSPAN session is active.
The destination port can participate in STP after the SPAN or RSPAN session is disabled. On a
source port, SPAN does not affect the STP status. STP can be active on trunk ports carrying an
RSPAN VLAN.
CDPA SPAN destination port does not participate in CDP while the SPAN session is active. After
the SPAN session is disabled, the port again participates in CDP.
VTPYou can use VTP to prune an RSPAN VLAN between switches.
VLAN and trunkingYou can modify VLAN membership or trunk settings for source or
destination ports at any time. However, changes in VLAN membership or trunk settings for a
destination port do not take effect until you remove the SPAN destination configuration. Changes in
VLAN membership or trunk settings for a source port immediately take effect, and the respective
SPAN sessions automatically adjust accordingly.
EtherChannelYou can configure an EtherChannel group as a source port but not as a SPAN
destination port. When a group is configured as a SPAN source, the entire group is monitored.
If a physical port is added to a monitored EtherChannel group, the new port is added to the SPAN
source port list. If a port is removed from a monitored EtherChannel group, it is automatically
removed from the source port list.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
29-9
Chapter 29
Configuring SPAN and RSPAN
Configuring SPAN and RSPAN
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.
SPAN and RSPAN and Switch Stacks
Because the stack of switches is treated as one logical switch, local SPAN source ports and destination
ports can be in different switches in the stack. Therefore, the addition or deletion of switches in the stack
can affect a local SPAN session, as well as an RSPAN source or destination session. An active session
can become inactive when a switch is removed from the stack or an inactive session can become active
when a switch is added to the stack.
For more information about switch stacks, see Chapter 5, Managing Switch Stacks.
Configuring SPAN and RSPAN
These sections contain this configuration information:
Default SPAN and RSPAN Configuration, page 29-11
Configuring Local SPAN, page 29-11
Configuring RSPAN, page 29-16
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
29-10
OL-12189-01
Chapter 29
Configuring SPAN and RSPAN
Configuring SPAN and RSPAN
Default SPAN and RSPAN Configuration
Table 29-1 shows the default SPAN and RSPAN configuration.
Table 29-1
Default SPAN and RSPAN Configuration
Feature
Default Setting
SPAN state (SPAN and RSPAN)
Disabled.
Source port traffic to monitor
Both received and sent traffic (both).
Encapsulation type (destination port)
Native form (untagged packets).
Ingress forwarding (destination port)
Disabled
VLAN filtering
On a trunk interface used as a source port, all VLANs are
monitored.
RSPAN VLANs
None configured.
Configuring Local SPAN
These sections contain this configuration information:
SPAN Configuration Guidelines, page 29-11
Creating a Local SPAN Session, page 29-12
Creating a Local SPAN Session and Configuring Incoming Traffic, page 29-14
Specifying VLANs to Filter, page 29-15
SPAN Configuration Guidelines
Follow these guidelines when configuring SPAN:
On each switch stack, you can configure a maximum of 2 source sessions and 64 RSPAN destination
sessions. A source session is either a local SPAN session or an RSPAN source session.
For SPAN sources, you can monitor traffic for a single port or VLAN or a series or range of ports
or VLANs for each session. You cannot mix source ports and source VLANs within a single SPAN
session.
The destination port cannot be a source port; a source port cannot be a destination port.
You cannot have two SPAN sessions using the same destination port.
When you configure a switch port as a SPAN destination port, it is no longer a normal switch port;
only monitored traffic passes through the SPAN destination port.
Entering SPAN configuration commands does not remove previously configured SPAN parameters.
You must enter the no monitor session {session_number | all | local | remote} global configuration
command to delete configured SPAN parameters.
For local SPAN, outgoing packets through the SPAN destination port carry the original
encapsulation headersuntagged, ISL, or IEEE 802.1Qif the encapsulation replicate keywords
are specified. If the keywords are not specified, the packets are sent in native form. For RSPAN
destination ports, outgoing packets are not tagged.
You can configure a disabled port to be a source or destination port, but the SPAN function does not
start until the destination port and at least one source port or source VLAN are enabled.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
29-11
Chapter 29
Configuring SPAN and RSPAN
Configuring SPAN and RSPAN
You can limit SPAN traffic to specific VLANs by using the filter vlan keyword. If a trunk port is
being monitored, only traffic on the VLANs specified with this keyword is monitored. By default,
all VLANs are monitored on a trunk port.
You cannot mix source VLANs and filter VLANs within a single SPAN session.
Creating a Local SPAN Session
Beginning in privileged EXEC mode, follow these steps to create a SPAN session and specify the source
(monitored) ports or VLANs and the destination (monitoring) ports:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
no monitor session {session_number | all |
local | remote}
Remove any existing SPAN configuration for the session.
For session_number, the range is 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
{interface interface-id | vlan vlan-id} [, | -]
[both | rx | tx]
Specify the SPAN session and the source port (monitored port).
For session_number, the range is 1 to 66.
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 48.
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.
(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) Specify the direction of traffic to monitor. If you do not
specify a traffic direction, the SPAN monitors both sent and received
traffic.
bothMonitor both received and sent traffic. This is the default.
rxMonitor received traffic.
txMonitor sent traffic.
Note
You can use the monitor session session_number source
command multiple times to configure multiple source ports.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
29-12
OL-12189-01
Chapter 29
Configuring SPAN and RSPAN
Configuring SPAN and RSPAN
Step 4
Command
Purpose
monitor session session_number
destination {interface interface-id [, | -]
[encapsulation replicate]}
Specify the SPAN session and the destination port (monitoring port).
For session_number, specify the session number entered in step 3.
Note
For local SPAN, you must use the same session number for
the source and destination interfaces.
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).
Note
You can use monitor session session_number destination
command multiple times to configure multiple destination
ports.
Step 5
end
Return to privileged EXEC mode.
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 options are ignored with the no form of the command.
This example shows how to set up 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 port 1 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 received traffic monitoring on port 1, which was configured for
bidirectional monitoring:
Switch(config)# no monitor session 1 source interface gigabitethernet1/0/1 rx
The monitoring of traffic received on port 1 is disabled, but traffic sent from this port continues to be
monitored.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
29-13
Chapter 29
Configuring SPAN and RSPAN
Configuring SPAN and RSPAN
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
destination Gigabit Ethernet port 2. The configuration is then modified to also monitor all traffic on all
ports belonging to VLAN 10.
Switch(config)#
Switch(config)#
Switch(config)#
Switch(config)#
Switch(config)#
no monitor session 2
monitor session 2 source vlan 1 - 3 rx
monitor session 2 destination interface gigabitethernet1/0/2
monitor session 2 source vlan 10
end
Creating a Local SPAN Session and Configuring Incoming Traffic
Beginning in privileged EXEC mode, follow these steps to create a SPAN session, to specify the source
ports or VLANs and the destination ports, and to enable incoming traffic on the destination port for a
network security device (such as a Cisco IDS Sensor Appliance).
For details about the keywords not related to incoming traffic, see the Creating a Local SPAN Session
section on page 29-12.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
no monitor session {session_number | all |
local | remote}
Remove any existing SPAN configuration for the session.
Step 3
monitor session session_number source
{interface interface-id | vlan vlan-id} [, | -]
[both | rx | tx]
Specify the SPAN session and the source port (monitored port).
Step 4
monitor session session_number
destination {interface interface-id [, | -]
[encapsulation replicate] [ingress {dot1q
vlan vlan-id | isl | untagged vlan vlan-id |
vlan vlan-id}]}
Specify the SPAN session, the destination port, the packet
encapsulation, and the ingress VLAN and encapsulation.
For session_number, specify the session number entered in Step 3.
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 forwarding of incoming
traffic on the destination port and to specify the encapsulation type:
dot1q vlan vlan-idAccept incoming packets with IEEE
802.1Q encapsulation with the specified VLAN as the default
VLAN.
islForward ingress packets with ISL encapsulation.
untagged vlan vlan-id or vlan vlan-idAccept incoming
packets with untagged encapsulation type with the specified
VLAN as the default VLAN.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
29-14
OL-12189-01
Chapter 29
Configuring SPAN and RSPAN
Configuring SPAN and RSPAN
Command
Purpose
Step 5
end
Return to privileged EXEC mode.
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 to 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
Specifying VLANs to Filter
Beginning in privileged EXEC mode, follow these steps to limit SPAN source traffic to specific VLANs:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
no monitor session {session_number | all |
local | remote}
Remove any existing SPAN configuration for the session.
For session_number, the range is 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
interface interface-id
Specify the characteristics of the source port (monitored port) and
SPAN session.
For session_number, the range is 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
29-15
Chapter 29
Configuring SPAN and RSPAN
Configuring SPAN and RSPAN
Step 5
Command
Purpose
monitor session session_number
destination {interface interface-id [, | -]
[encapsulation replicate]}
Specify the SPAN session and the destination port (monitoring port).
For session_number, specify the session number entered in Step 3.
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 VLAN 9 to destination Gigabit Ethernet port 1.
Switch(config)#
Switch(config)#
Switch(config)#
Switch(config)#
Switch(config)#
no monitor session 2
monitor session 2 source interface gigabitethernet1/0/2 rx
monitor session 2 filter vlan 1 - 5 , 9
monitor session 2 destination interface gigabitethernet1/0/1
end
Configuring RSPAN
These sections contain this configuration information:
RSPAN Configuration Guidelines, page 29-16
Configuring a VLAN as an RSPAN VLAN, page 29-17
Creating an RSPAN Source Session, page 29-18
Specifying VLANs to Filter, page 29-19
Creating an RSPAN Destination Session, page 29-20
Creating an RSPAN Destination Session and Configuring Incoming Traffic, page 29-21
RSPAN Configuration Guidelines
Follow these guidelines when configuring RSPAN:
All the items in the SPAN Configuration Guidelines section on page 29-11 apply to RSPAN.
As RSPAN VLANs have special properties, you should reserve a few VLANs across your network
for use as RSPAN VLANs; do not assign access ports to these VLANs.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
29-16
OL-12189-01
Chapter 29
Configuring SPAN and RSPAN
Configuring SPAN and RSPAN
You can apply an output ACL to RSPAN traffic to selectively filter or monitor specific packets.
Specify these ACLs on the RSPAN VLAN in the RSPAN source switches.
For RSPAN configuration, you can distribute the source ports and the destination ports across
multiple switches in your network.
RSPAN does not support BPDU packet monitoring or other Layer 2 switch protocols.
The RSPAN VLAN is configured only on trunk ports and not on access ports. To avoid unwanted
traffic in RSPAN VLANs, make sure that the VLAN remote-span feature is supported in all the
participating switches.
Access ports (including voice VLAN ports) on the RSPAN VLAN are put in the inactive state.
RSPAN VLANs are included as sources for port-based RSPAN sessions when source trunk ports
have active RSPAN VLANs. RSPAN VLANs can also be sources in SPAN sessions. However, since
the switch does not monitor spanned traffic, it does not support egress spanning of packets on any
RSPAN VLAN identified as the destination of an RSPAN source session on the switch.
You can configure any VLAN as an RSPAN VLAN as long as these conditions are met:
The same RSPAN VLAN is used for an RSPAN session in all the switches.
All participating switches support RSPAN.
We recommend that you configure an RSPAN VLAN before you configure an RSPAN source or a
destination session.
If you enable VTP and VTP pruning, RSPAN traffic is pruned in the trunks to prevent the unwanted
flooding of RSPAN traffic across the network for VLAN IDs that are lower than 1005.
Configuring a VLAN as an RSPAN VLAN
First create a new VLAN to be the RSPAN VLAN for the RSPAN session. You must create the RSPAN
VLAN in all switches that will participate in RSPAN. If the RSPAN VLAN-ID is in the normal range
(lower than 1005) and VTP is enabled in the network, you can create the RSPAN VLAN in one switch,
and VTP propagates it to the other switches in the VTP domain. For extended-range VLANs (greater
than 1005), you must configure RSPAN VLAN on both source and destination switches and any
intermediate switches.
Use VTP pruning to get an efficient flow of RSPAN traffic, or manually delete the RSPAN VLAN from
all trunks that do not need to carry the RSPAN traffic.
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
2 to 1001 and 1006 to 4094.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
29-17
Chapter 29
Configuring SPAN and RSPAN
Configuring SPAN and RSPAN
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
Creating an RSPAN Source Session
Beginning in privileged EXEC mode, follow these steps to start an RSPAN source session and to specify
the monitored source and the destination RSPAN VLAN:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
no monitor session {session_number | all |
local | remote}
Remove any existing RSPAN configuration for the session.
For session_number, the range is 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 3
monitor session session_number source
{interface interface-id | vlan vlan-id} [, | -]
[both | rx | tx]
Specify the RSPAN session and the source port (monitored port).
For session_number, the range is 1 to 66.
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 48.
For vlan-id, specify the source VLAN to monitor. The range is 1
to 4094 (excluding the RSPAN VLAN).
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.
(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) Specify the direction of traffic to monitor. If you do not
specify a traffic direction, the source interface sends both sent and
received traffic.
Step 4
monitor session session_number
destination remote vlan vlan-id
bothMonitor both received and sent traffic.
rxMonitor received traffic.
txMonitor sent traffic.
Specify the RSPAN session and the destination RSPAN VLAN.
For session_number, enter the number defined in Step 3.
For vlan-id, specify the source RSPAN VLAN to monitor.
Step 5
end
Return to privileged EXEC mode.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
29-18
OL-12189-01
Chapter 29
Configuring SPAN and RSPAN
Configuring SPAN and RSPAN
Step 6
Command
Purpose
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 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)#
Switch(config)#
Switch(config)#
Switch(config)#
Switch(config)#
Switch(config)#
no monitor session 1
monitor session 1 source interface gigabitethernet1/0/1 tx
monitor session 1 source interface gigabitethernet1/0/2 rx
monitor session 1 source interface port-channel 2
monitor session 1 destination remote vlan 901
end
Specifying VLANs to Filter
Beginning in privileged EXEC mode, follow these steps to configure the RSPAN source session to limit
RSPAN source traffic to specific VLANs:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
no monitor session {session_number | all |
local | remote}
Remove any existing SPAN configuration for the session.
For session_number, the range is 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
interface interface-id
Specify the characteristics of the source port (monitored port) and
SPAN session.
For session_number, the range is 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
29-19
Chapter 29
Configuring SPAN and RSPAN
Configuring SPAN and RSPAN
Step 5
Command
Purpose
monitor session session_number
destination remote vlan vlan-id
Specify the RSPAN session and the destination remote VLAN
(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 trunk port 2, and send traffic for only VLANs 1 through 5 and 9
to destination RSPAN VLAN 902.
Switch(config)#
Switch(config)#
Switch(config)#
Switch(config)#
Switch(config)#
no monitor session 2
monitor session 2 source interface gigabitethernet1/0/2 rx
monitor session 2 filter vlan 1 - 5 , 9
monitor session 2 destination remote vlan 902
end
Creating an RSPAN Destination Session
You configure the RSPAN destination session on a different switch or switch stack; that is, not the switch
or switch stack on which the source session was configured.
Beginning in privileged EXEC mode, follow these steps to define the RSPAN VLAN on that switch, to
create an RSPAN destination session, and to specify the source RSPAN VLAN and the destination port:
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.
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 |
local | remote}
Remove any existing RSPAN configuration for the session.
For session_number, the range is 1 to 66.
Specify all to remove all RSPAN sessions, local to remove all local
sessions, or remote to remove all remote SPAN sessions.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
29-20
OL-12189-01
Chapter 29
Configuring SPAN and RSPAN
Configuring SPAN and RSPAN
Step 6
Command
Purpose
monitor session session_number source
remote vlan vlan-id
Specify the RSPAN session and the source RSPAN VLAN.
For session_number, the range is 1 to 66.
For vlan-id, specify the source RSPAN VLAN to monitor.
Step 7
monitor session session_number
destination interface interface-id
Specify the RSPAN session and the destination interface.
For session_number, enter the number defined in Step 6.
In an RSPAN destination session, you must use the same session
number for the source RSPAN VLAN and the destination port.
For interface-id, specify the destination interface. The destination
interface must be a physical interface.
Though visible in the command-line help string, encapsulation
replicate is not supported for RSPAN. The original VLAN ID is
overwritten by the RSPAN VLAN ID, and all packets appear on the
destination port as untagged.
Step 8
end
Return to privileged EXEC mode.
Step 9
show monitor [session session_number]
Verify the configuration.
show running-config
Step 10
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 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 port 1 as the
destination interface:
Switch(config)# monitor session 1 source remote vlan 901
Switch(config)# monitor session 1 destination interface gigabitethernet2/0/1
Switch(config)# end
Creating an RSPAN Destination Session and Configuring Incoming Traffic
Beginning in privileged EXEC mode, follow these steps to create an RSPAN destination session, to
specify the source RSPAN VLAN and the destination port, and to enable incoming traffic on the
destination port for a network security device (such as a Cisco IDS Sensor Appliance).
For details about the keywords not related to incoming traffic, see the Creating an RSPAN Destination
Session section on page 29-20. This procedure assumes that the RSPAN VLAN has already
been configured.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
no monitor session {session_number | all |
local | remote}
Remove any existing SPAN configuration for the session.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
29-21
Chapter 29
Configuring SPAN and RSPAN
Configuring SPAN and RSPAN
Step 3
Command
Purpose
monitor session session_number source
remote vlan vlan-id
Specify the RSPAN session and the source RSPAN VLAN.
For session_number, the range is 1 to 66.
For vlan-id, specify the source RSPAN VLAN to monitor.
Step 4
Specify the SPAN session, the destination port, the packet
monitor session session_number
encapsulation, and the incoming VLAN and encapsulation.
destination {interface interface-id [, | -]
[ingress {dot1q vlan vlan-id | isl | untagged
For session_number, enter the number defined in Step 4.
vlan vlan-id | vlan vlan-id}]}
In an RSPAN destination session, you must use the same session
number for the source RSPAN VLAN and the destination port.
For interface-id, specify the destination interface. The destination
interface must be a physical interface.
Though visible in the command-line help string, encapsulation
replicate is not supported for RSPAN. The original VLAN ID is
overwritten by the RSPAN VLAN ID, and all packets appear on the
destination port as untagged.
(Optional) [, | -] Specify a series or range of interfaces. Enter a space
before and after the comma; enter a space before and after the
hyphen.
Enter ingress with additional keywords to enable forwarding of
incoming traffic on the destination port and to specify the
encapsulation type:
dot1q vlan vlan-idForward incoming packets with IEEE
802.1Q encapsulation with the specified VLAN as the default
VLAN.
islForward ingress packets with ISL encapsulation.
untagged vlan vlan-id or vlan vlan-idForward incoming
packets with untagged encapsulation type with the specified
VLAN as the default VLAN.
Step 5
end
Return to privileged EXEC mode.
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 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 forwarding of
incoming traffic 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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
29-22
OL-12189-01
Chapter 29
Configuring SPAN and RSPAN
Displaying SPAN and RSPAN Status
Displaying SPAN and RSPAN Status
To display the current SPAN or RSPAN configuration, use the show monitor user EXEC command. You
can also use the show running-config privileged EXEC command to display configured SPAN or
RSPAN sessions.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
29-23
Chapter 29
Configuring SPAN and RSPAN
Displaying SPAN and RSPAN Status
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
29-24
OL-12189-01
CH A P T E R
30
Configuring RMON
This chapter describes how to configure Remote Network Monitoring (RMON) on the switch. Unless
otherwise noted, the term switch refers to a standalone switch and to a switch stack.
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 from the Cisco.com page under Documentation > Cisco IOS Software > 12.2 Mainline
> Command References.
This chapter consists of these sections:
Understanding RMON, page 30-1
Configuring RMON, page 30-2
Displaying RMON Status, page 30-6
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 as shown in Figure 30-1.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
30-1
Chapter 30
Configuring RMON
Configuring RMON
Figure 30-1
Remote Monitoring Example
Network management station with
generic RMON console application
RMON history
and statistic
collection enabled.
Blade Servers
RMON alarms and
events configured.
SNMP configured.
Blade
switch
Blade Servers
119650
Blade
switch
The switch supports these RMON groups (defined in RFC 1757):
Statistics (RMON group 1)Collects Ethernet statistics (including Fast Ethernet and Gigabit
Ethernet statistics, depending on the switch type and supported interfaces) on an interface.
History (RMON group 2)Collects a history group of statistics on Ethernet ports (including Fast
Ethernet and Gigabit Ethernet statistics, depending on the switch type and supported interfaces) for
a specified polling interval.
Alarm (RMON group 3)Monitors a specific management information base (MIB) object for a
specified interval, triggers an alarm at a specified value (rising threshold), and resets the alarm at
another value (falling threshold). Alarms can be used with events; the alarm triggers an event, which
can generate a log entry or an SNMP trap.
Event (RMON group 9)Specifies the action to take when an event is triggered by an alarm. The
action can be to generate a log entry or an SNMP trap.
Because switches supported by this software release use hardware counters for RMON data processing,
the monitoring is more efficient, and little processing power is required.
Configuring RMON
These sections contain this configuration information:
Default RMON Configuration, page 30-3
Configuring RMON Alarms and Events, page 30-3 (required)
Collecting Group History Statistics on an Interface, page 30-5 (optional)
Collecting Group Ethernet Statistics on an Interface, page 30-5 (optional)
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
30-2
OL-12189-01
Chapter 30
Configuring RMON
Configuring RMON
Default RMON Configuration
RMON is disabled by default; no alarms or events are configured.
Configuring RMON Alarms and Events
You can configure your switch for RMON by using the command-line interface (CLI) or an
SNMP-compatible network management station. We recommend that you use a generic RMON console
application on the network management station (NMS) to take advantage of the RMON network
management capabilities. You must also configure SNMP on the switch to access RMON MIB objects.
For more information, see Chapter 32, Configuring SNMP.
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}
rising-threshold value [event-number]
falling-threshold value [event-number]
[owner string]
Set an alarm on a MIB object.
For number, specify the alarm number. The
range is 1 to 65535.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
30-3
Chapter 30
Configuring RMON
Configuring RMON
Command
Step 3
Purpose
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 variables 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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
30-4
OL-12189-01
Chapter 30
Configuring RMON
Configuring RMON
Collecting Group History Statistics on an Interface
You must first configure RMON alarms and events to display collection information.
Beginning in privileged EXEC mode, follow these steps to collect group history statistics on an interface.
This procedure is optional.
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
[buckets bucket-number] [interval seconds]
[owner ownername]
Enable history collection for the specified number of buckets and
time period.
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.
Collecting Group Ethernet Statistics on an Interface
Beginning in privileged EXEC mode, follow these steps to collect group Ethernet statistics on an
interface. This procedure is optional.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
30-5
Chapter 30
Configuring RMON
Displaying RMON Status
Command
Step 3
Purpose
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 gigabitethernet2/0/1
Switch(config-if)# rmon collection stats 2 owner root
Displaying RMON Status
To display the RMON status, use one or more of the privileged EXEC commands in Table 30-1:
Table 30-1
Commands for Displaying RMON Status
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 from the Cisco.com page
under Documentation > Cisco IOS Software > 12.2 Mainline > Command References.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
30-6
OL-12189-01
CH A P T E R
31
Configuring System Message Logging
This chapter describes how to configure system message logging on the switch. Unless otherwise noted,
the term switch refers to a standalone switch and to a switch stack.
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 from the Cisco.com page under
Documentation > Cisco IOS Software > 12.2 Mainline > Command References.
This chapter consists of these sections:
Caution
Understanding System Message Logging, page 31-1
Configuring System Message Logging, page 31-2
Displaying the Logging Configuration, page 31-14
Logging messages to the console at a high rate can cause high CPU utilization and adversely affect how
the switch operates.
Understanding System Message Logging
By default, a switch sends the output from system messages and debug privileged EXEC commands to
a logging process. Stack members can trigger system messages. A stack member that generates a system
message appends its hostname in the form of hostname-n, where n is a switch number from 1 to 9, and
redirects the output to the logging process on the stack master. Though the stack master is a stack
member, it does not append its hostname to system messages. The logging process controls the
distribution of logging messages to various destinations, such as the logging buffer, terminal lines, or a
UNIX syslog server, depending on your configuration. The process also sends messages to the console.
Note
The syslog format is compatible with 4.3 BSD UNIX.
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. On stacking-capable switches, messages appear on the active consoles after the process that
generated them has finished. On non-stacking switches, messages appear on the console after the process
that generated them has finished.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
31-1
Chapter 31
Configuring System Message Logging
Configuring System Message Logging
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 a standalone switch, and in the case of a switch stack, on the stack master. If a standalone
switch or the stack master 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, through the console port, or through the Ethernet management port. In a switch
stack, all stack member consoles provide the same console output.
Configuring System Message Logging
These sections contain this configuration information:
System Log Message Format, page 31-2
Default System Message Logging Configuration, page 31-4
Disabling Message Logging, page 31-4 (optional)
Setting the Message Display Destination Device, page 31-5 (optional)
Synchronizing Log Messages, page 31-6 (optional)
Enabling and Disabling Time Stamps on Log Messages, page 31-8 (optional)
Enabling and Disabling Sequence Numbers in Log Messages, page 31-8 (optional)
Defining the Message Severity Level, page 31-9 (optional)
Limiting Syslog Messages Sent to the History Table and to SNMP, page 31-10 (optional)
Enabling the Configuration-Change Logger, page 31-11 (optional)
Configuring UNIX Syslog Servers, page 31-12 (optional)
System Log Message Format
System log messages can contain up to 80 characters and a percent sign (%), which follows the optional
sequence number or time-stamp information, if configured. Messages appear in this format:
For stacking-capable switches, seq no:timestamp: %facility-severity-MNEMONIC:description
(hostname-n)
For nonstacking-capable switches, seq no:timestamp: %facility-severity-MNEMONIC:description
The part of the message preceding the percent sign depends on the setting of the service
sequence-numbers, service timestamps log datetime, service timestamps log datetime [localtime]
[msec] [show-timezone], or service timestamps log uptime global configuration command.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
31-2
OL-12189-01
Chapter 31
Configuring System Message Logging
Configuring System Message Logging
Table 31-1 describes the elements of syslog messages.
Table 31-1
System Log Message Elements
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 31-8.
Date and time of the message or event. This information appears only if the service timestamps
log [datetime | log] global configuration command is configured.
timestamp formats:
mm/dd hh:mm:ss
For more information, see the Enabling and Disabling Time Stamps on Log Messages section
on page 31-8.
or
hh:mm:ss (short uptime)
or
d h (long uptime)
facility
The facility to which the message refers (for example, SNMP, SYS, and so forth). For a list of
supported facilities, see Table 31-4 on page 31-14.
severity
Single-digit code from 0 to 7 that is the severity of the message. For a description of the severity
levels, see Table 31-3 on page 31-10.
MNEMONIC
Text string that uniquely describes the message.
description
Text string containing detailed information about the event being reported.
hostname-n
Hostname of a stack member and its switch number in the stack. Though the stack master is a stack
member, it does not append its hostname to system messages.
This example shows a partial switch system message for a stack master and a stack member (hostname
Switch-2):
00:00:46: %LINK-3-UPDOWN: Interface Port-channel1, changed state to up
00:00:47: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to up
00:00:47: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/2, changed state to up
00:00:48: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
00:00:48: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/1, changed
state to down 2
*Mar 1 18:46:11: %SYS-5-CONFIG_I: Configured from console by vty2 (10.34.195.36)
18:47:02: %SYS-5-CONFIG_I: Configured from console by vty2 (10.34.195.36)
*Mar 1 18:48:50.483 UTC: %SYS-5-CONFIG_I: Configured from console by vty2 (10.34.195.36)
00:00:46: %LINK-3-UPDOWN: Interface
00:00:47: %LINK-3-UPDOWN: Interface
00:00:47: %LINK-3-UPDOWN: Interface
00:00:48: %LINEPROTO-5-UPDOWN: Line
(Switch-2)
00:00:48: %LINEPROTO-5-UPDOWN: Line
state to down 2 (Switch-2)
Port-channel1, changed state to up (Switch-2)
GigabitEthernet2/0/1, changed state to up (Switch-2)
GigabitEthernet2/0/2, changed state to up (Switch-2)
protocol on Interface Vlan1, changed state to down
protocol on Interface GigabitEthernet2/0/1, changed
This example shows a partial switch system message on a nonstacking-capable switch:
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
31-3
Chapter 31
Configuring System Message Logging
Configuring System Message Logging
Default System Message Logging Configuration
Table 31-2 shows the default system message logging configuration.
Table 31-2
Default System Message Logging Configuration
Feature
Default Setting
System message logging to the console
Enabled.
Console severity
Debugging (and numerically lower levels; see
Table 31-3 on page 31-10).
Logging file configuration
No filename specified.
Logging buffer size
4096 bytes.
Logging history size
1 message.
Time stamps
Disabled.
Synchronous logging
Disabled.
Logging server
Disabled.
Syslog server IP address
None configured.
Server facility
Local7 (see Table 31-4 on page 31-14).
Server severity
Informational (and numerically lower levels; see
Table 31-3 on page 31-10).
Disabling Message Logging
Message logging is enabled by default. It must be enabled to send messages to any destination other than
the console. When enabled, log messages are sent to a logging process, which logs messages to
designated locations asynchronously to the processes that generated the messages.
Beginning in privileged EXEC mode, follow these steps to disable message logging. This procedure is
optional.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
no logging console
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 appear on
the console as soon as they are produced, often appearing in the middle of command output.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
31-4
OL-12189-01
Chapter 31
Configuring System Message Logging
Configuring System Message Logging
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 31-6.
To re-enable message logging after it has been disabled, use the logging on global configuration
command.
Setting the Message Display Destination Device
If message logging is enabled, you can send messages to specific locations in addition to the console.
Beginning in privileged EXEC mode, use one or more of the following commands to specify the
locations that receive messages. This procedure is optional.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
logging buffered [size]
Log messages to an internal buffer on the switch or on a standalone switch
or, in the case of a switch stack, on the stack master. The range is 4096 to
2147483647 bytes. The default buffer size is 4096 bytes.
If the standalone switch or the stack master fails, the log file is lost unless
you previously saved it to flash memory. See Step 4.
If the nonstacking-capable switch fails, the log file is lost unless you had
previously saved it to flash memory. See Step 4.
Note
Step 3
logging host
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.
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 31-12.
Step 4
logging file flash:filename
[max-file-size [min-file-size]]
[severity-level-number | type]
Store log messages in a file in flash memory on a standalone switch or, in
the case of a switch stack, on the stack master.
For filename, enter the log message filename.
(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 31-3 on page 31-10. By
default, the log file receives debugging messages and numerically
lower levels.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
31-5
Chapter 31
Configuring System Message Logging
Configuring System Message Logging
Command
Purpose
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.
Use the logging event power-inline-status interface configuration command to enable and to disable
logging of Power over Ethernet (PoE) events on specific PoE-capable ports. Logging on these ports is
enabled by default.
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.
Synchronizing Log Messages
You can synchronize unsolicited messages and debug privileged EXEC command output with solicited
device output and prompts for a specific console port line or virtual terminal line. You can identify the
types of messages to be output asynchronously based on the level of severity. You can also configure the
maximum number of buffers for storing asynchronous messages for the terminal after which messages
are dropped.
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 is 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 appear, the console again displays
the user prompt.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
31-6
OL-12189-01
Chapter 31
Configuring System Message Logging
Configuring System Message Logging
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
[ending-line-number]
Specify the line to be configured for synchronous logging of
messages.
Use the console keyword for configurations that occur through
the switch console port or the Ethernet management 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 |
all] | limit number-of-buffers]
Enable synchronous logging of messages.
(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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
31-7
Chapter 31
Configuring System Message Logging
Configuring System Message Logging
Enabling and Disabling Time Stamps on Log Messages
By default, log messages are not time-stamped.
Beginning in privileged EXEC mode, follow these steps to enable time-stamping of log messages. This
procedure is optional.
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]
The second command enables time stamps on log messages.
[show-timezone]
Depending on the options selected, the time stamp 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)
(Switch-2)
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
Enabling and Disabling Sequence Numbers in Log Messages
Because there is a chance that more than one log message can have the same time stamp, you can display
messages with sequence numbers so that you can unambiguously see a single message. By default,
sequence numbers in log messages are not displayed.
Beginning in privileged EXEC mode, follow these steps to enable sequence numbers in log messages.
This procedure is optional.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
31-8
OL-12189-01
Chapter 31
Configuring System Message Logging
Configuring System Message Logging
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 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) (Switch-2)
Defining the Message Severity Level
You can limit messages displayed to the selected device by specifying the severity level of the message,
which are described in Table 31-3.
Beginning in privileged EXEC mode, follow these steps to define the message severity level. This
procedure is optional.
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 31-3 on page 31-10).
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 31-3 on page 31-10).
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 31-3 on page 31-10).
For complete syslog server configuration steps, see the Configuring
UNIX Syslog Servers section on page 31-12.
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
Note
(Optional) Save your entries in the configuration file.
Specifying a level causes messages at that level and numerically lower levels to appear 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
31-9
Chapter 31
Configuring System Message Logging
Configuring System Message Logging
Table 31-3 describes the level keywords. It also lists the corresponding UNIX syslog definitions from
the most severe level to the least severe level.
Table 31-3
Message Logging Level Keywords
Level Keyword
Level
Description
Syslog Definition
emergencies
System unstable
LOG_EMERG
alerts
Immediate action needed
LOG_ALERT
critical
Critical conditions
LOG_CRIT
errors
Error conditions
LOG_ERR
warnings
Warning conditions
LOG_WARNING
notifications
Normal but significant condition
LOG_NOTICE
informational
Informational messages only
LOG_INFO
debugging
Debugging messages
LOG_DEBUG
The software generates four other categories of messages:
Error messages about software or hardware malfunctions, displayed at levels warnings through
emergencies. These types of messages mean that the functionality of the switch is affected. For
information on how to recover from these malfunctions, see the system message guide for this
release.
Output from the debug commands, displayed at the debugging level. Debug commands are
typically used only by the Technical Assistance Center.
Interface up or down transitions and system restart messages, displayed at the notifications level.
This message is only for information; switch functionality is not affected.
Reload requests and low-process stack messages, displayed at the informational level. This
message is only for information; switch functionality is not affected.
Limiting Syslog Messages Sent to the History Table and to SNMP
If you enabled syslog message traps to be sent to an SNMP network management station by using the
snmp-server enable trap global configuration command, you can change the level of messages sent and
stored in the switch history table. You also can change the number of messages that are stored in the
history table.
Messages are stored in the history table because SNMP traps are not guaranteed to reach their
destination. By default, one message of the level warning and numerically lower levels (see Table 31-3
on page 31-10) are stored in the history table even if syslog traps are not enabled.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
31-10
OL-12189-01
Chapter 31
Configuring System Message Logging
Configuring System Message Logging
Beginning in privileged EXEC mode, follow these steps to change the level and history table size
defaults. This procedure is optional.
Command
Step 1
Step 2
Purpose
configure terminal
logging history level
Enter global configuration mode.
1
Change the default level of syslog messages stored in the history file and
sent to the SNMP server.
See Table 31-3 on page 31-10 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 31-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.
Enabling the Configuration-Change Logger
You can enable a configuration logger to keep track of configuration changes made with the
command-line interface (CLI). When you enter the logging enable configuration-change logger
configuration command, the log records the session, the user, and the command that was entered to
change the configuration. You can configure the size of the configuration log from 1 to 1000 entries (the
default is 100). You can clear the log at any time by entering the no logging enable command followed
by the logging enable command to disable and re-enable logging.
Use the show archive log config {all | number [end-number] | user username [session number] number
[end-number] | statistics} [provisioning] privileged EXEC command to display the complete
configuration log or the log for specified parameters.
The default is that configuration logging is disabled.
For information about the commands, see the Cisco IOS Configuration Fundamentals and Network
Management Command Reference, Release 12.3 T at this URL:
http://www.cisco.com/en/US/products/sw/iosswrel/ps5207/products_command_reference_chapter0918
6a00801a8086.html#wp1114989
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
31-11
Chapter 31
Configuring System Message Logging
Configuring System Message Logging
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
This is an example of output for the configuration log:
Switch# show archive log config all
idx
sess
user@line
Logged command
38
11
unknown user@vty3
|no aaa authorization config-commands
39
12
unknown user@vty3
|no aaa authorization network default group radius
40
12
unknown user@vty3
|no aaa accounting dot1x default start-stop group
radius
41
13
unknown user@vty3
|no aaa accounting system default
42
14
temi@vty4
|interface GigabitEthernet4/0/1
43
14
temi@vty4
| switchport mode trunk
44
14
temi@vty4
| exit
45
16
temi@vty5
|interface GigabitEthernet5/0/1
46
16
temi@vty5
| switchport mode trunk
47
16
temi@vty5
| exit
Configuring UNIX Syslog Servers
The next sections describe how to configure the UNIX server syslog daemon and how to define the UNIX
system logging facility.
Logging Messages to a UNIX Syslog Daemon
Before you can send system log messages to a UNIX syslog server, you must configure the syslog
daemon on a UNIX server. This procedure is optional.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
31-12
OL-12189-01
Chapter 31
Configuring System Message Logging
Configuring System Message Logging
Log in as root, and perform these steps:
Note
Step 1
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.
Add a line such as the following to the file /etc/syslog.conf:
local7.debug /usr/adm/logs/cisco.log
The local7 keyword specifies the logging facility to be used; see Table 31-4 on page 31-14 for
information on the facilities. The debug keyword specifies the syslog level; see Table 31-3 on
page 31-10 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.
Configuring the UNIX System Logging Facility
When sending system log messages to an external device, you can cause the switch to identify its
messages as originating from any of the UNIX syslog facilities.
Beginning in privileged EXEC mode, follow these steps to configure UNIX system facility message
logging. This procedure is optional.
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 31-3 on page 31-10 for level keywords.
Step 4
logging facility facility-type
Configure the syslog facility. See Table 31-4 on page 31-14 for
facility-type keywords.
The default is local7.
Step 5
end
Return to privileged EXEC mode.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
31-13
Chapter 31
Configuring System Message Logging
Displaying the Logging Configuration
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 31-4 lists the UNIX system facilities supported by the software. For more information about these
facilities, consult the operators manual for your UNIX operating system.
Table 31-4
Logging Facility-Type Keywords
Facility Type Keyword
Description
auth
Authorization system
cron
Cron facility
daemon
System daemon
kern
Kernel
local0-7
Locally defined messages
lpr
Line printer system
Mail system
news
USENET news
sys9-14
System use
syslog
System log
user
User process
uucp
UNIX-to-UNIX copy system
Displaying the Logging Configuration
To display the logging configuration and the contents of the log buffer, use the show logging privileged
EXEC command. For information about the fields in this display, see the Cisco IOS Configuration
Fundamentals Command Reference, Release 12. 12.2 from the Cisco.com page under Documentation
> Cisco IOS Software > 12.2 Mainline > Command References.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
31-14
OL-12189-01
CH A P T E R
32
Configuring SNMP
This chapter describes how to configure the Simple Network Management Protocol (SNMP) on the
switch. Unless otherwise noted, the term switch refers to a standalone switch and to a switch stack.
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 Configuration Fundamentals Command Reference,
Release 12.2 from the Cisco.com page under Documentation > Cisco IOS Software > 12.2 Mainline
> Command References.
This chapter consists of these sections:
Understanding SNMP, page 32-1
Configuring SNMP, page 32-6
Displaying SNMP Status, page 32-17
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 managers 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 TCP connection, loss of connection to a neighbor, or other
significant events.
The stack master handles the SNMP requests and traps for the whole switch stack. The stack master
transparently manages any requests or traps that are related to all stack members. When a new stack
master is elected, the new master continues to handle SNMP requests and traps as configured on the
previous stack master, assuming that IP connectivity to the SNMP management stations is still in place
after the new master has taken control.
For more information about switch stacks, see Chapter 5, Managing Switch Stacks.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
32-1
Chapter 32
Configuring SNMP
Understanding SNMP
These sections contain this conceptual information:
SNMP Versions, page 32-2
SNMP Manager Functions, page 32-3
SNMP Agent Functions, page 32-4
SNMP Community Strings, page 32-4
Using SNMP to Access MIB Variables, page 32-4
SNMP Notifications, page 32-5
SNMP ifIndex MIB Object Values, page 32-5
SNMP Versions
This software release supports these SNMP versions:
SNMPv1The 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:
SNMPv2Version 2 of the Simple Network Management Protocol, a Draft Internet Standard,
defined in RFCs 1902 through 1907.
SNMPv2CThe community-string-based Administrative Framework for SNMPv2, an
Experimental Internet Protocol defined in RFC 1901.
SNMPv3Version 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 integrityensuring that a packet was not tampered with in transit
Authenticationdetermining that the message is from a valid source
Encryptionmixing 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
cryptographic (encrypted) universal software image is installed.
Both SNMPv1 and SNMPv2C use a community-based form of security. The community of managers
able to access the agents 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
32-2
OL-12189-01
Chapter 32
Configuring SNMP
Understanding SNMP
Table 32-1 identifies the characteristics of the different combinations of security models and levels.
Table 32-1
SNMP Security Models and Levels
Model
Level
Authentication
Encryption
Result
SNMPv1
noAuthNoPriv
Community string
No
Uses a community string match for authentication.
SNMPv2C
noAuthNoPriv
Community string
No
Uses a community string match for authentication.
SNMPv3
noAuthNoPriv
Username
No
Uses a username match for authentication.
SNMPv3
authNoPriv
MD5 or SHA
No
Provides authentication based on the HMAC-MD5
or HMAC-SHA algorithms.
SNMPv3
MD5 or SHA
authPriv
(requires the
cryptographic universal
software image)
DES
Provides authentication based on the HMAC-MD5
or HMAC-SHA algorithms.
Provides DES 56-bit encryption in addition to
authentication based on the CBC-DES (DES-56)
standard.
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, SNMPv2C, or SNMPv3.
SNMP Manager Functions
The SNMP manager uses information in the MIB to perform the operations described in Table 32-2.
Table 32-2
SNMP Operations
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
32-3
Chapter 32
Configuring SNMP
Understanding SNMP
SNMP Agent Functions
The SNMP agent responds to SNMP manager requests as follows:
Get a MIB variableThe SNMP agent begins this function in response to a request from the NMS.
The agent retrieves the value of the requested MIB variable and responds to the NMS with that value.
Set a MIB variableThe SNMP agent begins this function in response to a message from the NMS.
The SNMP agent changes the value of the MIB variable to the value requested by the NMS.
The SNMP agent also sends unsolicited trap messages to notify an NMS that a significant event has
occurred on the agent. Examples of trap conditions include, but are not limited to, when a port or module
goes up or down, when spanning-tree topology changes occur, and when authentication failures occur.
SNMP Community Strings
SNMP community strings authenticate access to MIB objects and function as embedded passwords. In
order for the NMS to access the switch, the community string definitions on the NMS must match at least
one of the three community string definitions on the switch.
A community string can have one of these attributes:
Read-only (RO)Gives read access to authorized management stations to all objects in the MIB
except the community strings, but does not allow write access
Read-write (RW)Gives read and write access to authorized management stations to all objects in
the MIB, but does not allow access to the community strings
Using SNMP to Access MIB Variables
An example of an NMS is the CiscoWorks network management software. CiscoWorks 2000 software
uses the switch MIB variables to set device variables and to poll devices on the network for specific
information. The results of a poll can be displayed as a graph and analyzed to troubleshoot
internetworking problems, increase network performance, verify the configuration of devices, monitor
traffic loads, and more.
As shown in Figure 32-1, the SNMP agent gathers data from the MIB. The agent can send traps, or
notification of certain events, to the SNMP manager, which receives and processes the traps. Traps alert
the SNMP manager to a condition on the network such as improper user authentication, restarts, link
status (up or down), MAC address tracking, and so forth. The SNMP agent also responds to MIB-related
queries sent by the SNMP manager in get-request, get-next-request, and set-request format.
NMS
SNMP Manager
SNMP Network
Get-request, Get-next-request,
Get-bulk, Set-request
Get-response, traps
Network device
MIB
SNMP Agent
43581
Figure 32-1
For information on supported MIBs and how to access them, see Appendix A, Supported MIBs.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
32-4
OL-12189-01
Chapter 32
Configuring SNMP
Understanding SNMP
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.
Note
SNMPv1 does not support 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.
SNMP ifIndex MIB Object Values
In an NMS, the IF-MIB generates and assigns an interface index (ifIndex) object value that is a unique
number greater than zero to identify a physical or a logical interface. When the switch reboots or the
switch software is upgraded, the switch uses this same value for the interface. For example, if the switch
assigns a port 2 an ifIndex value of 10003, this value is the same after the switch reboots.
The switch uses one of the values in Table 32-3 to assign an ifIndex value to an interface:
Table 32-3
ifIndex Values
Interface Type
SVI
ifIndex Range
14999
EtherChannel
50005012
Loopback
50135077
Tunnel
50785142
Physical (such as Gigabit Ethernet or module interfaces)
1000014500
Null
14501
1. SVI = switch virtual interface
Note
The switch might not use sequential values within a range.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
32-5
Chapter 32
Configuring SNMP
Configuring SNMP
Configuring SNMP
These sections contain this configuration information:
Default SNMP Configuration, page 32-6
SNMP Configuration Guidelines, page 32-6
Disabling the SNMP Agent, page 32-7
Configuring Community Strings, page 32-8
Configuring SNMP Groups and Users, page 32-9
Configuring SNMP Notifications, page 32-11
Setting the Agent Contact and Location Information, page 32-15
Limiting TFTP Servers Used Through SNMP, page 32-15
SNMP Examples, page 32-16
Default SNMP Configuration
Table 32-4 shows the default SNMP configuration.
Table 32-4
Default SNMP Configuration
Feature
Default Setting
SNMP agent
Disabled1.
SNMP trap receiver
None configured.
SNMP traps
None enabled except the trap for TCP connections (tty).
SNMP version
If no version keyword is present, the default is Version 1.
SNMPv3 authentication
If no keyword is entered, the default is the noauth (noAuthNoPriv)
security level.
SNMP notification type
If no type is specified, all notifications are sent.
1. This is the default when the switch starts and the startup configuration does not have any snmp-server global configuration
commands.
SNMP Configuration Guidelines
If the switch starts and the switch startup configuration has at least one snmp-server global
configuration command, the SNMP agent is enabled.
An SNMP group is a table that maps SNMP users to SNMP views. An SNMP user is a member of an
SNMP group. An SNMP host is the recipient of an SNMP trap operation. An SNMP engine ID is a name
for the local or remote SNMP engine.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
32-6
OL-12189-01
Chapter 32
Configuring SNMP
Configuring SNMP
When configuring SNMP, follow these guidelines:
When configuring an SNMP group, do not specify a notify view. The snmp-server host global
configuration command autogenerates a notify view for the user and then adds it to the group
associated with that user. Modifying the group's notify view affects all users associated with that
group. See the Cisco IOS Configuration Fundamentals Command Reference, Release 12.2 for
information about when you should configure notify views.
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.
Disabling the SNMP Agent
Beginning in privileged EXEC mode, follow these steps to disable the SNMP agent:
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 Cisco IOS command exists to enable SNMP. The
first snmp-server global configuration command that you enter enables all versions of SNMP.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
32-7
Chapter 32
Configuring SNMP
Configuring SNMP
Configuring Community Strings
You use the SNMP community string to define the relationship between the SNMP manager and the
agent. The community string acts like a password to permit access to the agent on the switch. Optionally,
you can specify one or more of these characteristics associated with the string:
An access list of IP addresses of the SNMP managers that are permitted to use the community string
to gain access to the agent
A MIB view, which defines the subset of all MIB objects accessible to the given community
Read and write or read-only permission for the MIB objects accessible to the community
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
view-name] [ro | rw] [access-list-number]
Configure the community string.
Step 3
access-list access-list-number {deny |
permit} source [source-wildcard]
For string, specify a string that acts like a password and
permits access to the SNMP protocol. You can configure one
or more community strings of any length.
(Optional) For view, specify the view record accessible to the
community.
(Optional) Specify either read-only (ro) if you want
authorized management stations to retrieve MIB objects, or
specify read-write (rw) if you want authorized management
stations to retrieve and modify MIB objects. By default, the
community string permits read-only access to all objects.
(Optional) For access-list-number, enter an IP standard access
list numbered from 1 to 99 and 1300 to 1999.
(Optional) If you specified an IP standard access list number in
Step 2, then create the list, repeating the command as many times
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 SNMP managers that
are permitted to use the community string to gain access to the
agent.
(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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
32-8
OL-12189-01
Chapter 32
Configuring SNMP
Configuring SNMP
Command
Purpose
Step 5
show running-config
Verify your entries.
Step 6
copy running-config startup-config
(Optional) Save your entries in the configuration file.
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
Configuring SNMP Groups and Users
You can specify an identification name (engine ID) for the local or remote SNMP server engine on the
switch. You can configure an SNMP server group that maps SNMP users to SNMP views, and you can
add new users to the SNMP group.
Beginning in privileged EXEC mode, follow these steps to configure SNMP on the switch:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
snmp-server engineID {local engineid-string Configure a name for either the local or remote copy of SNMP.
| remote ip-address [udp-port port-number]
The engineid-string is a 24-character ID string with the name
engineid-string}
of 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 User
Datagram Protocol (UDP) port on the remote device. The
default is 162.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
32-9
Chapter 32
Configuring SNMP
Configuring SNMP
Command
Step 3
Purpose
snmp-server group groupname {v1 | v2c | v3 Configure a new SNMP group on the remote device.
{auth | noauth | priv}} [read readview]
For groupname, specify the name of the group.
[write writeview] [notify notifyview] [access
Specify a security model:
access-list]
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:
authEnables the Message Digest 5 (MD5) and the
Secure Hash Algorithm (SHA) packet authentication.
noauthEnables the noAuthNoPriv security level. This
is the default if no keyword is specified.
privEnables Data Encryption Standard (DES) packet
encryption (also called privacy).
Note
The priv keyword is available only when the cryptographic
universal software image is installed.
(Optional) Enter read readview with a string (not to exceed 64
characters) that is the name of the view in which you can only
view the contents of the agent.
(Optional) Enter write writeview with a string (not to exceed
64 characters) that is the name of the view in which you enter
data and configure the contents of the agent.
(Optional) Enter notify notifyview with a string (not to exceed
64 characters) that is the name of the view in which you
specify a notify, inform, or trap.
(Optional) Enter access access-list with a string (not to exceed
64 characters) that is the name of the access list.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
32-10
OL-12189-01
Chapter 32
Configuring SNMP
Configuring SNMP
Command
Step 4
Purpose
Add a new user for an SNMP group.
snmp-server user username groupname
{remote host [udp-port port]} {v1 [access
The username is the name of the user on the host that connects
access-list] | v2c [access access-list] | v3
to the agent.
[encrypted] [access access-list] [auth {md5 |
The groupname is the name of the group to which the user is
sha} auth-password]}
associated.
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
(not to exceed 64 characters).
(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.
Step 7
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Configuring SNMP Notifications
A trap manager is a management station that receives and processes traps. Traps are system alerts that
the switch generates when certain events occur. By default, no trap manager is defined, and no traps are
sent. Switches running this Cisco IOS release can have an unlimited number of trap managers.
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 either traps, informs, or both. Use the
snmp-server host global configuration command to specify whether to send SNMP notifications as
traps or informs.
Table 32-5 describes the supported switch traps (notification types). You can enable any or all of these
traps and configure a trap manager to receive them.
Table 32-5
Switch Notification Types
Notification Type
Keyword
Description
bgp
Generates Border Gateway Protocol (BGP) state change traps. This option is
only available when the IP services feature set is enabled.
bridge
Generates STP bridge MIB traps.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
32-11
Chapter 32
Configuring SNMP
Configuring SNMP
Table 32-5
Switch Notification Types (continued)
Notification Type
Keyword
Description
cluster
Generates a trap when the cluster configuration changes.
config
Generates a trap for SNMP configuration changes.
copy-config
Generates a trap for SNMP copy configuration changes.
entity
Generates a trap for SNMP entity changes.
envmon
Generates environmental monitor traps. You can enable any or all of these
environmental traps: fan, shutdown, status, supply, temperature.
errdisable
Generates a trap for a port VLAN errdisabled. You can also set a maximum
trap rate per minute. The range is from 0 to 10000; the default is 0, which
means there is no rate limit.
flash
Generates SNMP FLASH notifications. In a switch stack, you can optionally
enable notification for flash insertion or removal, which would cause a trap to
be issued whenever a switch in the stack is removed or inserted (physical
removal, power cycle, or reload).
fru-ctrl
Generates entity field-replaceable unit (FRU) control traps. In the switch
stack, this trap refers to the insertion or removal of a switch in the stack.
hsrp
Generates a trap for Hot Standby Router Protocol (HSRP) changes.
ipmulticast
Generates a trap for IP multicast routing changes.
mac-notification
Generates a trap for MAC address notifications.
msdp
Generates a trap for Multicast Source Discovery Protocol (MSDP) changes.
ospf
Generates a trap for Open Shortest Path First (OSPF) changes. You can enable
any or all of these traps: Cisco specific, errors, link-state advertisement, rate
limit, retransmit, and state changes.
pim
Generates a trap for Protocol-Independent Multicast (PIM) changes. You can
enable any or all of these traps: invalid PIM messages, neighbor changes, and
rendezvous point (RP)-mapping changes.
port-security
Generates SNMP port security traps. You can also set a maximum trap rate
per second. The range is from 0 to 1000; the default is 0, which means that
there is no rate limit.
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:
snmp-server enable traps port-security
snmp-server enable traps port-security trap-rate rate
rtr
Generates a trap for the SNMP Response Time Reporter (RTR).
snmp
Generates a trap for SNMP-type notifications for authentication, cold start,
warm start, link up or link down.
storm-control
Generates a trap for SNMP storm-control. You can also set a maximum trap
rate per minute. The range is from 0 to 1000; the default is 0 (no limit is
imposed; a trap is sent at every occurrence).
stpx
Generates SNMP STP Extended MIB traps.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
32-12
OL-12189-01
Chapter 32
Configuring SNMP
Configuring SNMP
Table 32-5
Note
Switch Notification Types (continued)
Notification Type
Keyword
Description
syslog
Generates SNMP syslog traps.
tty
Generates a trap for TCP connections. This trap is enabled by default.
vlan-membership
Generates a trap for SNMP VLAN membership changes.
vlancreate
Generates SNMP VLAN created traps.
vlandelete
Generates SNMP VLAN deleted traps.
vtp
Generates a trap for VLAN Trunking Protocol (VTP) changes.
Though visible in the command-line help strings, the cpu [threshold] keyword is not supported on the
Catalyst Switch Module 3110. Though visible in the command-line help strings, the cpu [threshold],
fru-ctrl, insertion, msdp, ospf, pim, and removal keywords are not supported on the Catalyst Switch
Module 3012. To enable the sending of SNMP inform notifications, use the snmp-server enable traps
global configuration command combined with the snmp-server host host-addr informs global
configuration command.
You can use the snmp-server host global configuration command to a specific host to receive the
notification types listed in Table 32-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
ip-address engineid-string
Specify the engine ID for the remote host.
Step 3
snmp-server user username
groupname {remote host [udp-port
port]} {v1 [access access-list] | v2c
[access access-list] | v3 [encrypted]
[access access-list] [auth {md5 | sha}
auth-password]}
Configure an SNMP user to be associated with the remote host created in
Step 2.
snmp-server group groupname {v1 |
v2c | v3 {auth | noauth | priv}} [read
readview] [write writeview] [notify
notifyview] [access access-list]
Configure an SNMP group.
Step 4
Note
You cannot configure a remote user for an address without first
configuring the engine ID for the remote host. Otherwise, you
receive an error message, and the command is not executed.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
32-13
Chapter 32
Configuring SNMP
Configuring SNMP
Step 5
Command
Purpose
snmp-server host host-addr
[informs | traps] [version {1 | 2c | 3
{auth | noauth | priv}}]
community-string [notification-type]
Specify the recipient of an SNMP trap operation.
For host-addr, specify the name or Internet address of the host (the
targeted recipient).
(Optional) Enter informs to send SNMP informs to the host.
(Optional) Enter traps (the default) to send SNMP traps 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
Step 6
snmp-server enable traps
notification-types
The priv keyword is available only when the cryptographic
universal software image is installed.
For community-string, when version 1 or version 2c is specified,
enter the password-like community string sent with the notification
operation. When version 3 is specified, enter the SNMPv3 username.
(Optional) For notification-type, use the keywords listed in
Table 32-5 on page 32-11. If no type is specified, all notifications are
sent.
Enable the switch to send traps or informs and specify the type of
notifications to be sent. For a list of notification types, see Table 32-5 on
page 32-11, or enter 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:
snmp-server enable traps port-security
snmp-server enable traps port-security trap-rate rate
Step 7
snmp-server trap-source interface-id
(Optional) Specify the source interface, which provides the IP address for
the trap message. This command also sets the source IP address for
informs.
Step 8
snmp-server queue-length length
(Optional) Establish the message queue length for each trap host. The
range is 1 to 1000; the default is 10.
Step 9
snmp-server trap-timeout seconds
(Optional) Define how often to resend trap messages. The range is 1 to
1000; the default is 30 seconds.
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.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
32-14
OL-12189-01
Chapter 32
Configuring SNMP
Configuring SNMP
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.
Setting the Agent Contact and Location Information
Beginning in privileged EXEC mode, follow these steps to set the system contact and location of the
SNMP agent so that these descriptions can be accessed through the configuration file:
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.
Limiting TFTP Servers Used Through SNMP
Beginning in privileged EXEC mode, follow these steps to limit the TFTP servers used for saving and
loading configuration files through SNMP to the servers specified in an access list:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
snmp-server tftp-server-list
access-list-number
Limit TFTP servers used for configuration file copies through
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
32-15
Chapter 32
Configuring SNMP
Configuring SNMP
Step 3
Command
Purpose
access-list access-list-number {deny |
permit} source [source-wildcard]
Create a standard access list, repeating the command as many times
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.
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)#
Switch(config)#
Switch(config)#
Switch(config)#
Switch(config)#
snmp-server
snmp-server
snmp-server
snmp-server
snmp-server
community public
enable traps vtp
host 192.180.1.27 version 2c public
host 192.180.1.111 version 1 public
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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
32-16
OL-12189-01
Chapter 32
Configuring SNMP
Displaying SNMP Status
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
Switch(config)# snmp-server host cisco.com restricted 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)#
Switch(config)#
Switch(config)#
mypassword
Switch(config)#
Switch(config)#
Switch(config)#
Switch(config)#
snmp-server engineID remote 192.180.1.27 00000063000100a1c0b4011b
snmp-server group authgroup v3 auth
snmp-server user authuser authgroup remote 192.180.1.27 v3 auth md5
snmp-server
snmp-server
snmp-server
snmp-server
user authuser authgroup v3 auth md5 mypassword
host 192.180.1.27 informs version 3 auth authuser config
enable traps
inform retries 0
Displaying SNMP Status
To display SNMP input and output statistics, including the number of illegal community string entries,
errors, and requested variables, use the show snmp privileged EXEC command. You also can use the
other privileged EXEC commands in Table 32-6 to display SNMP information. For information about
the fields in the displays, see the Cisco IOS Configuration Fundamentals Command Reference,
Release 12.2.
Table 32-6
Commands for Displaying SNMP Information
Feature
Default Setting
show snmp
Displays SNMP statistics.
show snmp engineID [local | remote]
Displays information on the local SNMP engine and all
remote engines that have been configured on the device.
show snmp group
Displays information on each SNMP group on the network.
show snmp pending
Displays information on pending SNMP requests.
show snmp sessions
Displays information on the current SNMP sessions.
show snmp user
Displays information on each SNMP user name in the
SNMP users table.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
32-17
Chapter 32
Configuring SNMP
Displaying SNMP Status
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
32-18
OL-12189-01
CH A P T E R
34
Configuring Network Security with ACLs
This chapter describes how to configure network security on the switch by using access control lists
(ACLs), which in commands and tables are also referred to as access lists.Unless otherwise noted, the
term switch refers to a standalone switch and to a switch stack.
Note
Information in this chapter about IP ACLs is specific to IP Version 4 (IPv4). For information about IPv6
ACLs, see Chapter 35, Configuring IPv6 ACLs.
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 the Cisco IOS IP Command
Reference, Volume 1 of 3: Addressing and Services, Release 12.2.
This chapter consists of these sections:
Understanding ACLs, page 34-1
Configuring IPv4 ACLs, page 34-7
Creating Named MAC Extended ACLs, page 34-27
Configuring VLAN Maps, page 34-29
Using VLAN Maps with Router ACLs, page 34-35
Displaying IPv4 ACL Configuration, page 34-39
Understanding ACLs
Packet filtering can help limit network traffic and restrict network use by certain users or devices. ACLs
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. One by one, it tests packets against the conditions in an access list.
The first match decides whether the switch accepts or rejects the packets. Because the switch stops
testing after the first match, the order of conditions in the list is critical. If no conditions match, the
switch rejects the packet. If there are no restrictions, the switch forwards the packet; otherwise, the
switch drops the packet. The switch can use ACLs on all packets it forwards, including packets bridged
within a VLAN.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
34-1
Chapter 34
Configuring Network Security with ACLs
Understanding ACLs
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 IPv4 traffic, including TCP, User Datagram Protocol (UDP), Internet Group
Management Protocol (IGMP), and Internet Control Message Protocol (ICMP).
Ethernet ACLs filter non-IP traffic.
This switch also supports quality of service (QoS) classification ACLs. For more information, see the
Classification Based on QoS ACLs section on page 36-7.
These sections contain this conceptual information:
Supported ACLs, page 34-2
Handling Fragmented and Unfragmented Traffic, page 34-5
ACLs and Switch Stacks, page 34-6
Supported ACLs
The switch supports three applications of ACLs to filter traffic:
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. For more information, see the Port ACLs section on page 34-3.
Router ACLs access-control routed traffic between VLANs and are applied to Layer 3 interfaces in
a specific direction (inbound or outbound). For more information, see the Router ACLs section on
page 34-4.
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 IPv4. 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. For more information,
see the VLAN Maps section on page 34-5.
You can use input port ACLs, router 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
34-2
OL-12189-01
Chapter 34
Configuring Network Security with ACLs
Understanding ACLs
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.
If IEEE 802.1Q tunneling is configured on an interface, any IEEE 802.1Q encapsulated IP packets
received on the tunnel port can be filtered by MAC ACLs, but not by IP ACLs. This is because the switch
does not recognize the protocol inside the IEEE 802.1Q header. This restriction applies to router ACLs,
port ACLs, and VLAN maps. For more information about IEEE 802.1Q tunneling, see Chapter 16,
Configuring IEEE 802.1Q and Layer 2 Protocol Tunneling
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 and can be applied only on interfaces in the
inbound direction. These access lists are supported:
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
The switch examines ACLs associated with all inbound features configured on a given interface and
permits or denies packet forwarding based on how the packet matches the entries in the ACL. In this way,
ACLs control access to a network or to part of a network. Figure 34-1 is an example of using port ACLs
to control access to a network when all servers are in the same VLAN. ACLs applied at the Layer 2 input
would allow Blade Server A to access the Human Resources network, but prevent Blade Server B from
accessing the same network. Port ACLs can only be applied to Layer 2 interfaces in the inbound
direction.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
34-3
Chapter 34
Configuring Network Security with ACLs
Understanding ACLs
Figure 34-1
Using ACLs to Control Traffic to a Network
Blade Server A
Blade Server B
Research &
Development
network
= ACL denying traffic from Blade Server B
and permitting traffic from Blade Server A
= Packet
119651
Human
Resources
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 IP traffic by using IP access lists and non-IP 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.
Router ACLs
You can apply router ACLs on switch virtual interfaces (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.
The switch supports these access lists for IPv4 traffic:
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
34-4
OL-12189-01
Chapter 34
Configuring Network Security with ACLs
Understanding ACLs
As with port ACLs, the switch examines ACLs associated with features configured on a given interface.
However, router ACLs are supported in both directions. 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 34-1, ACLs applied at the
router input allow Host A to access the Human Resources network, but prevent Host B from accessing
the same network.
VLAN Maps
Use VLAN ACLs or VLAN maps to 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 in the switch or switch stack.
Use VLAN maps 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 IPv4 traffic.
All non-IP 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 34-2 shows how a VLAN map is applied to prevent a specific type of traffic from Host A in
VLAN 10 from being forwarded. You can apply only one VLAN map to a VLAN.
Host A
(VLAN 10)
Using VLAN Maps to Control Traffic
Blade
switch
Host B
(VLAN 10)
= VLAN map denying specific type
of traffic from Host A
= Packet
201774
Figure 34-2
Handling Fragmented and Unfragmented Traffic
IP packets can be fragmented as they cross the network. When this happens, only the fragment
containing the beginning of the packet contains the Layer 4 information, such as TCP or UDP port
numbers, ICMP type and code, and so on. All other fragments are missing this information.
Some ACEs do not check Layer 4 information and therefore can be applied to all packet fragments. ACEs
that do test Layer 4 information cannot be applied in the standard manner to most of the fragments in a
fragmented IP packet. When the fragment contains no Layer 4 information and the ACE tests some
Layer 4 information, the matching rules are modified:
Permit ACEs that check the Layer 3 information in the fragment (including protocol type, such as
TCP, UDP, and so on) are considered to match the fragment regardless of what the missing Layer 4
information might have been.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
34-5
Chapter 34
Configuring Network Security with ACLs
Understanding ACLs
Deny ACEs that check Layer 4 information never match a fragment unless the fragment contains
Layer 4 information.
Consider access list 102, configured with these commands, applied to three fragmented packets:
Switch(config)#
Switch(config)#
Switch(config)#
Switch(config)#
Note
access-list
access-list
access-list
access-list
102
102
102
102
permit tcp any host 10.1.1.1 eq smtp
deny tcp any host 10.1.1.2 eq telnet
permit tcp any host 10.1.1.2
deny tcp any any
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.
ACLs and Switch Stacks
ACL support is the same for a switch stack as for a standalone switch. ACL configuration information
is propagated to all switches in the stack. All switches in the stack, including the stack master, process
the information and program their hardware. (For more information about switch stacks, see Chapter 5,
Configuring the Switch Stack.)
The stack master performs these ACL functions:
It processes the ACL configuration and propagates the information to all stack members.
It distributes the ACL information to any switch that joins the stack.
If packets must be forwarded by software for any reason (for example, not enough hardware
resources), the master switch forwards the packets only after applying ACLs on the packets.
It programs its hardware with the ACL information it processes.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
34-6
OL-12189-01
Chapter 34
Configuring Network Security with ACLs
Configuring IPv4 ACLs
Stack members perform these ACL functions:
They receive the ACL information from the master switch and program their hardware.
They act as standby switches, ready to take over the role of the stack master if the existing master
were to fail and they were to be elected as the new stack master.
When a stack master fails and a new stack master is elected, the newly elected master reparses the backed
up running configuration. (See Chapter 5, Configuring the Switch Stack.) The ACL configuration that
is part of the running configuration is also reparsed during this step. The new stack master distributes
the ACL information to all switches in the stack.
Configuring IPv4 ACLs
Configuring IP v4ACLs on the switch is the same as configuring IPv4 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 the Cisco IOS IP
Command Reference, Volume 1 of 3: Addressing and Services, Release 12.2.
The switch does not support these Cisco IOS router ACL-related features:
Non-IP protocol ACLs (see Table 34-1 on page 34-8) 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 the access conditions.
Step 2
Apply the ACL to interfaces or terminal lines. You can also apply standard and extended IP ACLs to
VLAN maps.
These sections contain this configuration information:
Creating Standard and Extended IPv4 ACLs, page 34-7
Applying an IPv4 ACL to a Terminal Line, page 34-19
Applying an IPv4 ACL to an Interface, page 34-20
Hardware and Software Treatment of IP ACLs, page 34-22
IPv4 ACL Configuration Examples, page 34-22
Creating Standard and Extended IPv4 ACLs
This section describes IP ACLs. An ACL is a sequential collection of permit and deny conditions. One
by one, the switch tests packets against the conditions in an access list. The first match determines
whether the switch accepts or rejects the packet. Because the switch stops testing after the first match,
the order of the conditions is critical. If no conditions match, the switch denies the packet.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
34-7
Chapter 34
Configuring Network Security with ACLs
Configuring IPv4 ACLs
The software supports these types of ACLs or access lists for IPv4:
Standard IP access lists use source addresses for matching operations.
Extended IP access lists use source and destination addresses for matching operations and optional
protocol-type information for finer granularity of control.
These sections describe access lists and how to create them:
Access List Numbers, page 34-8
ACL Logging, page 34-9
Creating a Numbered Standard ACL, page 34-10
Creating a Numbered Extended ACL, page 34-11
Resequencing ACEs in an ACL, page 34-15
Creating Named Standard and Extended ACLs, page 34-15
Using Time Ranges with ACLs, page 34-17
Including Comments in ACLs, page 34-19
Access List Numbers
The number you use to denote your ACL shows the type of access list that you are creating. Table 34-1
lists the access-list number and corresponding access list type and shows whether or not they are
supported in the switch. The switch supports IPv4 standard and extended access lists, numbers 1 to 199
and 1300 to 2699.
Table 34-1
Access List Numbers
Access List Number
Type
Supported
199
IP standard access list
Yes
100199
IP extended access list
Yes
200299
Protocol type-code access list
No
300399
DECnet access list
No
400499
XNS standard access list
No
500599
XNS extended access list
No
600699
AppleTalk access list
No
700799
48-bit MAC address access list
No
800899
IPX standard access list
No
900999
IPX extended access list
No
10001099
IPX SAP access list
No
11001199
Extended 48-bit MAC address access list
No
12001299
IPX summary address access list
No
13001999
IP standard access list (expanded range)
Yes
20002699
IP extended access list (expanded range)
Yes
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
34-8
OL-12189-01
Chapter 34
Configuring Network Security with ACLs
Configuring IPv4 ACLs
Note
In addition to numbered standard and extended ACLs, you can also create standard and extended named
IP ACLs by 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.
ACL Logging
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 appear 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
34-9
Chapter 34
Configuring Network Security with ACLs
Configuring IPv4 ACLs
Creating a Numbered Standard ACL
Beginning in privileged EXEC mode, follow these steps to create a numbered standard ACL:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
access-list access-list-number {deny | permit} Define a standard IPv4 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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
34-10
OL-12189-01
Chapter 34
Configuring Network Security with ACLs
Configuring IPv4 ACLs
The switch always rewrites the order of standard access lists so that entries with host matches and entries
with matches having a dont care mask of 0.0.0.0 are moved to the top of the list, above any entries with
non-zero dont 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.
After creating a numbered standard IPv4 ACL, you can apply it to terminal lines (see the Applying an
IPv4 ACL to a Terminal Line section on page 34-19), to interfaces (see the Applying an IPv4 ACL to
an Interface section on page 34-20), or to VLANs (see the Configuring VLAN Maps section on
page 34-29).
Creating a Numbered Extended ACL
Although standard ACLs use only source addresses for matching, you can use extended ACL source and
destination addresses for matching operations and optional protocol type information for finer
granularity of control. When you are creating ACEs in numbered extended access lists, remember that
after you create the ACL, any additions are placed at the end of the list. You cannot reorder the list or
selectively add or remove ACEs from a numbered list.
Some protocols also have specific parameters and keywords that apply to that protocol.
These IP protocols are supported (protocol keywords are in parentheses in bold):
Authentication Header Protocol (ahp), Enhanced Interior Gateway Routing Protocol (eigrp),
Encapsulation Security Payload (esp), generic routing encapsulation (gre), Internet Control Message
Protocol (icmp), Internet Group Management Protocol (igmp), 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 command references:
Note
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 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
34-11
Chapter 34
Configuring Network Security with ACLs
Configuring IPv4 ACLs
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
{deny | permit} protocol
source source-wildcard
destination destination-wildcard
[precedence precedence] [tos tos]
[fragments] [log] [log-input]
[time-range time-range-name]
[dscp dscp]
Define an extended IPv4 access list and the access conditions.
Note
The access-list-number is a decimal number from 100 to 199 or 2000 to 2699.
Enter deny or permit to specify whether to deny or permit the packet if
conditions are matched.
For protocol, enter the name or number of an IP protocol: ahp, eigrp, esp, gre,
icmp, igmp, igrp, ip, ipinip, nos, ospf, pcp, pim, tcp, or udp, or an integer in
the range 0 to 255 representing an IP protocol number. To match any Internet
protocol (including ICMP, TCP, and UDP), use the keyword ip.
If you enter a dscp value,
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:
precedenceEnter 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).
fragmentsEnter to check non-initial fragments.
tosEnter 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).
logEnter 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-rangeFor an explanation of this keyword, see the Using Time
Ranges with ACLs section on page 34-17.
dscpEnter 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
34-12
OL-12189-01
Chapter 34
Configuring Network Security with ACLs
Configuring IPv4 ACLs
or
or
Step
2b
Command
Purpose
access-list access-list-number
{deny | permit} protocol any any
[precedence precedence] [tos tos]
[fragments] [log] [log-input]
[time-range time-range-name]
[dscp dscp]
In access-list configuration mode, define an extended IP access list using an
abbreviation for a source and source wildcard of 0.0.0.0 255.255.255.255 and
an abbreviation for a destination and destination wildcard of 0.0.0.0
255.255.255.255.
access-list access-list-number
{deny | permit} protocol
host source host destination
[precedence precedence] [tos tos]
[fragments] [log] [log-input]
[time-range time-range-name]
[dscp dscp]
Define an extended IP access list by using an abbreviation for a source and a
source wildcard of source 0.0.0.0 and an abbreviation for a destination and
destination wildcard of destination 0.0.0.0.
access-list access-list-number
{deny | permit} tcp source
source-wildcard [operator port]
destination destination-wildcard
[operator port] [established]
[precedence precedence] [tos tos]
[fragments] [log] [log-input]
[time-range time-range-name]
[dscp dscp] [flag]
You can use the any keyword in place of source and destination address and
wildcard.
You can use the host keyword in place of the source and destination wildcard
or mask.
(Optional) Define an extended TCP access list and the access conditions.
Enter tcp for Transmission Control Protocol.
The parameters are the same as those described in Step 2a, with these
exceptions:
(Optional) Enter an operator and port to compare source (if positioned after
source source-wildcard) or destination (if positioned after destination
destination-wildcard) port. Possible operators include eq (equal), gt (greater
than), lt (less than), neq (not equal), and range (inclusive range). Operators
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 other optional keywords have these meanings:
Step
2c
access-list access-list-number
{deny | permit} udp
source source-wildcard [operator
port] destination
destination-wildcard [operator
port] [precedence precedence]
[tos tos] [fragments] [log]
[log-input] [time-range
time-range-name] [dscp dscp]
establishedEnter to match an established connection. This has the same
function as matching on the ack or rst flag.
flagEnter 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).
(Optional) Define an extended UDP access list and the access conditions.
Enter udp for the User Datagram Protocol.
The UDP parameters are the same as those described for TCP except that the
[operator [port]] port number or name must be a UDP port number or name, and
the flag and established parameters are not valid for UDP.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
34-13
Chapter 34
Configuring Network Security with ACLs
Configuring IPv4 ACLs
Step
2d
Step
2e
Command
Purpose
access-list access-list-number
{deny | permit} icmp source
source-wildcard destination
destination-wildcard [icmp-type |
[[icmp-type icmp-code] |
[icmp-message]] [precedence
precedence] [tos tos] [fragments]
[log] [log-input] [time-range
time-range-name] [dscp dscp]
(Optional) Define an extended ICMP access list and the access conditions.
Enter icmp for Internet Control Message Protocol.
The ICMP parameters are the same as those described for most IP protocols in
Step 2a, with the addition of the ICMP message type and code parameters.
These optional keywords have these meanings:
icmp-typeEnter to filter by ICMP message type, a number from 0 to 255.
icmp-codeEnter to filter ICMP packets that are filtered by the ICMP
message code type, a number from 0 to 255.
icmp-messageEnter to filter ICMP packets by the ICMP message type
name or the ICMP message type and code name. To see a list of ICMP
message type names and code names, use the ?, or see the Configuring IP
Services section of the Cisco IOS IP Configuration Guide, Release 12.2.
access-list access-list-number
{deny | permit} igmp source
source-wildcard destination
destination-wildcard [igmp-type]
[precedence precedence] [tos tos]
[fragments] [log] [log-input]
[time-range time-range-name]
[dscp dscp]
(Optional) Define an extended IGMP access list and the access conditions.
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
startup-config
Enter igmp for Internet Group Management Protocol.
The IGMP parameters are the same as those described for most IP protocols in
Step 2a, with this optional parameter.
igmp-typeTo match IGMP message type, enter a number from 0 to 15, or enter
the message name (dvmrp, host-query, host-report, pim, or trace).
(Optional) Save your entries in the configuration file.
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 to 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
34-14
OL-12189-01
Chapter 34
Configuring Network Security with ACLs
Configuring IPv4 ACLs
After creating a numbered extended ACL, you can apply it to terminal lines (see the Applying an IPv4
ACL to a Terminal Line section on page 34-19), to interfaces (see the Applying an IPv4 ACL to an
Interface section on page 34-20), or to VLANs (see the Configuring VLAN Maps section on
page 34-29).
Resequencing ACEs in an ACL
Sequence numbers for the entries in an access list are automatically generated when you create a new
ACL. You can use the ip access-list resequence global configuration command to edit the sequence
numbers in an ACL and change the order in which ACEs are applied. For example, if you add a new ACE
to an ACL, it is placed at the bottom of the list. By changing the sequence number, you can move the
ACE to a different position in the ACL.
For more information about the ip access-list resequence command, see this URL:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1838/products_feature_guide09186a0080134a60.
html
Creating Named Standard and Extended ACLs
You can identify IPv4 ACLs with an alphanumeric string (a name) rather than a number. You can use
named ACLs to configure more IPv4 access lists in a router than if you were to use numbered access
lists. If you identify your access list with a name rather than a number, the mode and command syntax
are slightly different. However, not all commands that use IP access lists accept a named access list.
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.
Consider these guidelines and limitations before configuring named ACLs:
Not all commands that accept a numbered ACL accept a named ACL. ACLs for packet filters and
route filters on interfaces can use a name. VLAN maps also accept a name.
A standard ACL and an extended ACL cannot have the same name.
Numbered ACLs are also available, as described in the Creating Standard and Extended IPv4
ACLs section on page 34-7.
You can use standard and extended ACLs (named or numbered) in VLAN maps.
With IPv4 QoS ACLs, if you enter the class-map {match-all | match-any} class-map-name global
configuration command, you can enter these match commands:
match access-group acl-name
Note
The ACL must be an extended named ACL.
match input-interface interface-id-list
match ip dscp dscp-list
match ip precedence ip-precedence-list
You cannot enter the match access-group acl-index command.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
34-15
Chapter 34
Configuring Network Security with ACLs
Configuring IPv4 ACLs
Beginning in privileged EXEC mode, follow these steps to create a standard ACL using names:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ip access-list standard name
Define a standard IPv4 access list using a name, and enter
access-list configuration mode.
The name can be a number from 1 to 99.
Step 3
deny {source [source-wildcard] | host source |
any} [log]
In access-list configuration mode, specify one or more conditions
denied or permitted to decide if the packet is forwarded or dropped.
or
host sourceA source and source wildcard of source 0.0.0.0.
permit {source [source-wildcard] | host source
| any} [log]
anyA 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 IPv4 access list using a name, and enter
access-list configuration mode.
The name can be a number from 100 to 199.
Step 3
{deny | permit} protocol {source
[source-wildcard] | host source | any}
{destination [destination-wildcard] | host
destination | any} [precedence precedence]
[tos tos] [established] [log] [time-range
time-range-name]
In access-list configuration mode, specify the conditions allowed
or denied. Use the log keyword to get access list logging messages,
including violations.
See the Creating a Numbered Extended ACL section on
page 34-11 for definitions of protocols and other keywords.
host sourceA source and source wildcard of source 0.0.0.0.
host destinationA destination and destination wildcard of
destination 0.0.0.0.
anyA 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
34-16
OL-12189-01
Chapter 34
Configuring Network Security with ACLs
Configuring IPv4 ACLs
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 IPv4 ACL to an
Interface section on page 34-20) or to VLANs (see the Configuring VLAN Maps section on
page 34-29).
Using Time Ranges with ACLs
You can selectively apply extended ACLs based on the time of day and the week by using the time-range
global configuration command. First, define a time-range name and set the times and the dates or the
days of the week in the time range. Then enter the time-range name when applying an ACL to set
restrictions to the access list. You can use the time range to define when the permit or deny statements
in the ACL are in effect, for example, during a specified time period or on specified days of the week.
The time-range keyword and argument are referenced in the named and numbered extended ACL task
tables in the previous sections, the Creating Standard and Extended IPv4 ACLs section on page 34-7,
and the Creating Named Standard and Extended ACLs section on page 34-15.
These are some of the many possible benefits of using time ranges:
You have more control over permitting or denying a user access to resources, such as an application
(identified by an IP address/mask pair and a port number).
You can control logging messages. ACL entries can be set to log traffic only at certain times of the
day. Therefore, you can simply deny access without needing to analyze many logs generated during
peak hours.
Time-based access lists trigger CPU activity because the new configuration of the access list must be
merged with other features and the combined configuration loaded into the hardware memory. For this
reason, you should be careful not to have several access lists configured to take affect in close succession
(within a small number of minutes of each other.)
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 6-1.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
34-17
Chapter 34
Configuring Network Security with ACLs
Configuring IPv4 ACLs
Beginning in privileged EXEC mode, follow these steps to configure a 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.
Step 3
absolute [start time date]
[end time date]
Specify when the function it will be applied to is operational.
or
periodic day-of-the-week hh:mm to
[day-of-the-week] hh:mm
or
periodic {weekdays | weekend | daily}
hh:mm to hh:mm
You can use only one absolute statement in the time range. If you
configure more than one absolute statement, only the one configured
last is executed.
You can enter multiple periodic statements. For example, you could
configure different hours for weekdays and weekends.
See the example configurations.
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 to configure January 1, 2006, as a
company 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_2006
Switch(config-time-range)# absolute start 00:00 1 Jan 2006 end 23:59 1 Jan 2006
Switch(config-time-range)# end
Switch# show time-range
time-range entry: new_year_day_2003 (inactive)
absolute start 00:00 01 January 2006 end 23:59 01 January 2006
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_2006
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_2006 (inactive)
20 permit tcp any any time-range workhours (inactive)
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
34-18
OL-12189-01
Chapter 34
Configuring Network Security with ACLs
Configuring IPv4 ACLs
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_2006
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 lpip_default
10 permit ip any any
Extended IP access list deny_access
10 deny tcp any any time-range new_year_day_2006 (inactive)
Extended IP access list may_access
10 permit tcp any any time-range workhours (inactive)
Including Comments in ACLs
You can use the remark keyword to include comments (remarks) about entries in any IP standard or
extended ACL. The remarks make the ACL easier for you to understand and scan. Each remark line is
limited to 100 characters.
The remark can go before or after a permit or deny statement. You should be consistent about where you
put the remark so that it is clear which remark describes which permit or deny statement. For example,
it would be confusing to have some remarks before the associated permit or deny statements and some
remarks after the associated statements.
To include a comment for IP numbered standard or extended ACLs, use the access-list access-list
number remark remark global configuration command. To remove the remark, use the no form of this
command.
In this example, the server that belongs to Jones is allowed access, and the workstation that belongs to
Smith is not allowed access:
Switch(config)#
Switch(config)#
Switch(config)#
Switch(config)#
access-list
access-list
access-list
access-list
1
1
1
1
remark Permit only Jones server through
permit 171.69.2.88
remark Do not allow Smith server through
deny 171.69.3.13
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
Applying an IPv4 ACL to a Terminal Line
You can use numbered ACLs to control access to one or more terminal lines. You cannot apply named
ACLs to lines. You must set identical restrictions on all the virtual terminal lines because a user can
attempt to connect to any of them.
For procedures for applying ACLs to interfaces, see the Applying an IPv4 ACL to an Interface section
on page 34-20. For applying ACLs to VLANs, see the Configuring VLAN Maps section on
page 34-29.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
34-19
Chapter 34
Configuring Network Security with ACLs
Configuring IPv4 ACLs
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.
consoleSpecify the console terminal line. The console port is DCE.
vtySpecify 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
{in | out}
Restrict incoming and outgoing connections between a particular virtual
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.
Applying an IPv4 ACL to an Interface
This section describes how to apply IPv4 ACLs to network interfaces. Note these guidelines:
Note
Apply an ACL only to inbound Layer 2 interfaces. Apply an ACL to either outbound or inbound
Layer 3 interfaces.
When controlling access to an interface, you can use a named or numbered ACL.
If you apply an ACL to a Layer 2 interface that is a member of a VLAN, the Layer 2 (port) ACL
takes precedence over a VLAN map applied to the VLAN. Incoming packets received on the Layer 2
port are always filtered by the port ACL.
If you apply an ACL to a Layer 2 interface that is a member of a VLAN, the Layer 2 (port) ACL
takes precedence over an input Layer 3 ACL applied to the VLAN interface or a VLAN map applied
to the VLAN. Incoming packets received on the Layer 2 port are always filtered by the port ACL.
If you apply an ACL to a Layer 3 interface and routing is not enabled on the switch, the ACL only
filters packets that are intended for the CPU, such as SNMP, Telnet, or web traffic. You do not have
to enable routing to apply ACLs to Layer 2 interfaces.
When private VLANs are configured, you can apply router ACLs only on the primary-VLAN SVIs.
The ACL is applied to both primary and secondary VLAN Layer 3 traffic.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
34-20
OL-12189-01
Chapter 34
Configuring Network Security with ACLs
Configuring IPv4 ACLs
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 to a port to filter packets entering the port:
Switch(config)# interface gigabitethernet1/0/1
Router(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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
34-21
Chapter 34
Configuring Network Security with ACLs
Configuring IPv4 ACLs
Hardware and Software Treatment of IP ACLs
ACL processing is primarily accomplished in hardware, but requires forwarding of some traffic flows to
the CPU for software processing. If the hardware reaches its capacity to store ACL configurations,
packets are sent to the CPU for forwarding. The forwarding rate for software-forwarded traffic is
substantially less than for hardware-forwarded traffic.
Note
If an ACL configuration cannot be implemented in hardware due to an out-of-resource condition on a
switch or stack member, then only the traffic in that VLAN arriving on that switch is affected (forwarded
in software). Software forwarding of packets might adversely impact the performance of the switch or
switch stack, depending on the number of CPU cycles that this consumes.
For router ACLs, other factors can cause packets to be sent to the CPU:
Using the log keyword
Generating ICMP unreachable messages
When traffic flows are both logged and forwarded, forwarding is done by hardware, but logging must be
done by software. Because of the difference in packet handling capacity between hardware and software,
if the sum of all flows being logged (both permitted flows and denied flows) is of great enough
bandwidth, not all of the packets that are forwarded can be logged.
If router ACL configuration cannot be applied in hardware, packets arriving in a VLAN that must be
routed are routed in software, but are bridged in hardware. If ACLs cause large numbers of packets to be
sent to the CPU, the switch performance can be negatively affected.
When you enter the show ip access-lists privileged EXEC command, the match count displayed does
not account for packets that are access controlled in hardware. Use the show access-lists hardware
counters privileged EXEC command to obtain some basic hardware ACL statistics for switched and
routed packets.
Router ACLs function as follows:
The hardware controls permit and deny actions of standard and extended ACLs (input and output)
for security access control.
If log has not been specified, the flows that match a deny statement in a security ACL are dropped
by the hardware if ip unreachables is disabled. The flows matching a permit statement are switched
in hardware.
Adding the log keyword to an ACE in a router ACL causes a copy of the packet to be sent to the
CPU for logging only. If the ACE is a permit statement, the packet is still switched and routed
in hardware.
IPv4 ACL Configuration Examples
This section provides examples of configuring and applying IPv4 ACLs. For detailed information about
compiling ACLs, see the Cisco IOS Security Configuration Guide, Release 12.2 and to the Configuring
IP Services section in the IP Addressing and Services chapter of the Cisco IOS IP Configuration
Guide, Release 12.2.
Figure 34-3 shows a small networked office environment with routed Port 2 connected to blade server A,
containing benefits and other information that all employees can access, and routed Port 1 connected to
blade server B, containing confidential payroll data. All users can access blade server A, but Blade
server B has restricted access.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
34-22
OL-12189-01
Chapter 34
Configuring Network Security with ACLs
Configuring IPv4 ACLs
Use router ACLs to do this in one of two ways:
Create a standard ACL, and filter traffic coming to the server from port 1.
Create an extended ACL, and filter traffic coming from the server into port 1.
Figure 34-3
Using Router ACLs to Control Traffic
Blade
server B
Port 2
Port 1
Accounting
172.20.128.64-95
201775
Human Resources
172.20.128.0-31
Blade
server A
This example uses a standard ACL to filter traffic coming into blade server B from a port, permitting
traffic only from Accountings 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 blade server B into a port, 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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
34-23
Chapter 34
Configuring Network Security with ACLs
Configuring IPv4 ACLs
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 applied to packets entering a port.
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 gigabitethernet2/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 gigabitethernet2/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.
Switch(config)# access-list 102 permit tcp any 128.88.0.0 0.0.255.255 eq 23
Switch(config)# access-list 102 permit tcp any 128.88.0.0 0.0.255.255 eq 25
Switch(config)# interface gigabitethernet0/1
Switch(config-if)# ip access-group 102 in
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. Gigabit Ethernet interface 1 on stack member 1 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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
34-24
OL-12189-01
Chapter 34
Configuring Network Security with ACLs
Configuring IPv4 ACLs
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 any other IP 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 Internet_filter ACL is applied to outgoing traffic and the marketing_group ACL is applied to
incoming traffic on a Layer 3 port.
Switch(config)# interface gigabitethernet3/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
Time Range Applied to an IP ACL
This example denies HTTP traffic on IP on Monday through Friday between the hours of 8:00 a.m. and
6:00 p.m (18:00). The example allows UDP traffic only on Saturday and Sunday from noon to 8:00 p.m.
(20:00).
Switch(config)# time-range no-http
Switch(config)# periodic weekdays 8:00 to 18:00
!
Switch(config)# time-range udp-yes
Switch(config)# periodic weekend 12:00 to 20:00
!
Switch(config)# ip access-list extended strict
Switch(config-ext-nacl)# deny tcp any any eq www time-range no-http
Switch(config-ext-nacl)# permit udp any any time-range udp-yes
!
Switch(config-ext-nacl)# exit
Switch(config)# interface gigabitethernet2/0/1
Switch(config-if)# ip access-group strict in
Commented IP ACL Entries
In this example of a numbered ACL, the server that belongs to Jones is allowed access, and the
workstation that belongs to Smith is not allowed access:
Switch(config)# access-list 1 remark Permit only Jones server through
Switch(config)# access-list 1 permit 171.69.2.88
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
34-25
Chapter 34
Configuring Network Security with ACLs
Configuring IPv4 ACLs
Switch(config)# access-list 1 remark Do not allow Smith server through
Switch(config)# access-list 1 deny 171.69.3.13
In this example of a numbered ACL, the Winter and Smith servers are not allowed to browse the web:
Switch(config)#
Switch(config)#
Switch(config)#
Switch(config)#
access-list
access-list
access-list
access-list
100
100
100
100
remark Do
deny host
remark Do
deny host
not allow Winter to browse the web
171.69.3.85 any eq www
not allow Smith to browse the web
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
Log Buffer (4096 bytes):
00:00:48: NTP: authentication delay calculation problems
<output truncated>
00:09:34:%SEC-6-IPACCESSLOGS:list stan1 permitted 0.0.0.0 1 packet
00:09:59:%SEC-6-IPACCESSLOGS:list stan1 denied 10.1.1.15 1 packet
00:10:11:%SEC-6-IPACCESSLOGS:list stan1 permitted 0.0.0.0 1 packet
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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
34-26
OL-12189-01
Chapter 34
Configuring Network Security with ACLs
Creating Named MAC Extended ACLs
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# ip access-group ext1 in
This is a an example of a log for an extended ACL:
01:24:23:%SEC-6-IPACCESSLOGDP:list ext1 permitted
packet
01:25:14:%SEC-6-IPACCESSLOGDP:list ext1 permitted
packets
01:26:12:%SEC-6-IPACCESSLOGP:list ext1 denied udp
packet
01:31:33:%SEC-6-IPACCESSLOGP:list ext1 denied udp
packets
icmp 10.1.1.15 -> 10.1.1.61 (0/0), 1
icmp 10.1.1.15 -> 10.1.1.61 (0/0), 7
0.0.0.0(0) -> 255.255.255.255(0), 1
0.0.0.0(0) -> 255.255.255.255(0), 8
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
Creating Named MAC Extended ACLs
You can filter non-IPv4 traffic on a VLAN or on a Layer 2 interface by using MAC addresses and named
MAC extended ACLs. The procedure is similar to that of configuring other extended named ACLs.
Note
You cannot apply named MAC extended ACLs to Layer 3 interfaces.
For more information about the supported non-IP 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
34-27
Chapter 34
Configuring Network Security with ACLs
Creating Named MAC Extended ACLs
Step 3
Command
Purpose
{deny | permit} {any | host source MAC
address | source MAC address mask} {any |
host destination MAC address | destination
MAC address mask} [type mask | lsap lsap mask
| 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 | 0-65535] [cos cos]
In extended MAC access-list configuration mode, specify to
permit or deny any source MAC address, a source MAC address
with a mask, or a specific host source MAC address and any
destination MAC address, destination MAC address with a mask,
or a specific destination MAC address.
(Optional) You can also enter these options:
type maskAn arbitrary EtherType number of a packet with
Ethernet II or SNAP encapsulation in decimal, hexadecimal,
or octal with optional mask of dont care bits applied to the
EtherType before testing for a match.
lsap lsap maskAn LSAP number of a packet with
IEEE 802.2 encapsulation in decimal, hexadecimal, or octal
with optional mask of dont 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-idpA non-IP protocol.
cos cosAn IEEE 802.1Q 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
Applying a MAC ACL to a Layer 2 Interface
After you create a MAC ACL, you can apply it to a Layer 2 interface to filter non-IP traffic coming in
that interface. When you apply the MAC ACL, consider these guidelines:
If you apply an ACL to a Layer 2 interface that is a member of a VLAN, the Layer 2 (port) ACL
takes precedence over a VLAN map applied to the VLAN. Incoming packets received on the Layer
2 port are always filtered by the port ACL.
If you apply an ACL to a Layer 2 interface that is a member of a VLAN, the Layer 2 (port) ACL
takes precedence over an input Layer 3 ACL applied to the VLAN interface or a VLAN map applied
to the VLAN. Incoming packets received on the Layer 2 port are always filtered by the port ACL.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
34-28
OL-12189-01
Chapter 34
Configuring Network Security with ACLs
Configuring VLAN Maps
You can apply no more than one IP access list and one MAC access list to the same Layer 2 interface.
The IP access list filters only IP packets, and the MAC access list filters non-IP packets.
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.
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 to a port to filter packets entering the port:
Switch(config)# interface gigabitethernet1/0/2
Router(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.
Configuring VLAN Maps
This section describes how to configure VLAN maps, which is the only way to control filtering within
a VLAN. VLAN maps have no direction. To filter traffic in a specific direction by using a VLAN map,
you need to include an ACL with specific source or destination addresses. If there is a match clause for
that type of packet (IP or MAC) in the VLAN map, the default action is to drop the packet if the packet
does not match any of the entries within the map. If there is no match clause for that type of packet, the
default is to forward the packet.
For complete syntax and usage information for the commands used in this section, see the command
reference for this release.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
34-29
Chapter 34
Configuring Network Security with ACLs
Configuring VLAN Maps
To create a VLAN map and apply it to one or more VLANs, perform these steps:
Step 1
Create the standard or extended IPv4 ACLs or named MAC extended ACLs that you want to apply to the
VLAN. See the Creating Standard and Extended IPv4 ACLs section on page 34-7 and the Creating a
VLAN Map section on page 34-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 actionforward (the default) or dropand
enter the match command to specify an IP packet or a non-IP 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, 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.
These sections contain this configuration information:
VLAN Map Configuration Guidelines, page 34-30
Creating a VLAN Map, page 34-31
Applying a VLAN Map to a VLAN, page 34-34
Using VLAN Maps in Your Network, page 34-34
VLAN Map Configuration Guidelines
Follow these guidelines when configuring VLAN maps:
If there is no ACL configured to deny traffic on an interface and no VLAN map is configured, all
traffic is permitted.
Each VLAN map consists of a series of entries. The order of entries in an VLAN map is important.
A packet that comes into the switch is tested against the first entry in the VLAN map. If it matches,
the action specified for that part of the VLAN map is taken. If there is no match, the packet is tested
against the next entry in the map.
If the VLAN map has at least one match clause for the type of packet (IP or MAC) and the packet
does not match any of these match clauses, the default is to drop the packet. If there is no match
clause for that type of packet in the VLAN map, the default is to forward the packet.
The system might take longer to boot up if you have configured a very large number of ACLs.
Logging is not supported for VLAN maps.
If VLAN map configuration cannot be applied in hardware, all packets in that VLAN must be
forwarded by software.
When a switch has an IP access list or MAC access list applied to a Layer 2 interface, and you apply
a VLAN map to a VLAN that the port belongs to, the port ACL takes precedence over the VLAN
map.
On a Catalyst Switch Module 3110, if VLAN map configuration cannot be applied in hardware, all
packets in that VLAN must be bridged and routed by software.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
34-30
OL-12189-01
Chapter 34
Configuring Network Security with ACLs
Configuring VLAN Maps
On a Catalyst Switch Module 3012, if VLAN map configuration cannot be applied in hardware, all
packets in that VLAN must be routed by software.
You can configure VLAN maps on primary and secondary VLANs. However, we recommend that
you configure the same VLAN maps on private-VLAN primary and secondary VLANs.
When a frame is Layer-2 forwarded within a private VLAN, the same VLAN map is applied at the
ingress side and at the egress side. When a frame is routed from inside a private VLAN to an external
port, the private-VLAN map is applied at the ingress side.
For frames going upstream from a host port to a promiscuous port, the VLAN map configured
on the secondary VLAN is applied.
For frames going downstream from a promiscuous port to a host port, the VLAN map
configured on the primary VLAN is applied.
To filter out specific IP traffic for a private VLAN, you should apply the VLAN map to both the
primary and secondary VLANs. For more information about private VLANs, see Chapter 15,
Configuring Private VLANs.
For configuration examples, see the Using VLAN Maps in Your Network section on page 34-34.
For information about using both router ACLs and VLAN maps, see the VLAN Maps and Router ACL
Configuration Guidelines section on page 34-35.
Creating a VLAN Map
Each VLAN map consists of an ordered series of entries. Beginning in privileged EXEC mode, follow
these steps to create, add to, or delete a VLAN map entry:
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 |
number} [name | number]
Match the packet (using either the IP or MAC address) against one or more
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-IP 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
34-31
Chapter 34
Configuring Network Security with ACLs
Configuring VLAN Maps
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.
Examples of ACLs and VLAN Maps
These examples show how to create ACLs and VLAN maps that for specific purposes.
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-IP 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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
34-32
OL-12189-01
Chapter 34
Configuring Network Security with ACLs
Configuring VLAN Maps
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-IP 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 (IP and non-IP). 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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
34-33
Chapter 34
Configuring Network Security with ACLs
Configuring VLAN Maps
Applying a VLAN Map to a VLAN
Beginning in privileged EXEC mode, follow these steps to apply a VLAN map to one or more VLANs:
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
Using VLAN Maps in Your Network
These sections describes how to deny access to a server on another VLAN (see the Denying Access to
a Server on Another VLAN section on page 34-34).
Denying Access to a Server on Another VLAN
You can restrict access to a server on another VLAN. For example, server 10.1.1.100 in VLAN 10 needs
to have access denied to these hosts (see Figure 34-4):
Hosts in subnet 10.1.2.0/8 in VLAN 20 should not have access.
Hosts 10.1.1.4 and 10.1.1.8 in VLAN 10 should not have access.
Figure 34-4
Deny Access to a Server on Another VLAN
VLAN map
10.1.1.100
Subnet
10.1.2.0/8
Server (VLAN 10)
10.1.1.4
Host (VLAN 10)
Layer 3 switch
Host (VLAN 20)
Host (VLAN 10)
Packet
101356
10.1.1.8
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
34-34
OL-12189-01
Chapter 34
Configuring Network Security with ACLs
Using VLAN Maps with Router ACLs
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
Step 3
Apply the VLAN map to VLAN 10.
Switch(config)# vlan filter SERVER1_MAP vlan-list 10.
Using VLAN Maps with Router ACLs
To access control both bridged and routed traffic, you can use VLAN maps only or a combination of
router ACLs and VLAN maps. You can define router ACLs on both input and output routed VLAN
interfaces, and you can define a VLAN map to access control the bridged traffic.
If a packet flow matches a VLAN-map deny clause in the ACL, regardless of the router ACL
configuration, the packet flow is denied.
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.
These sections contain information about using VLAN maps with router ACLs:
VLAN Maps and Router ACL Configuration Guidelines, page 34-35
Examples of Router ACLs and VLAN Maps Applied to VLANs, page 34-36
VLAN Maps and Router ACL Configuration 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
34-35
Chapter 34
Configuring Network Security with ACLs
Using VLAN Maps with Router ACLs
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 dont 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.
Examples of Router ACLs and VLAN Maps Applied to VLANs
This section gives examples of applying router ACLs and VLAN maps to a VLAN for switched, bridged,
routed, and multicast packets. Although the following illustrations show packets being forwarded to their
destination, each time the packets path crosses a line indicating a VLAN map or an ACL, it is also
possible that the packet might be dropped, rather than forwarded.
ACLs and Switched Packets
Figure 34-5 shows how an ACL is applied on packets that are switched within a VLAN. Packets switched
within the VLAN without being routed or forwarded by fallback bridging are only subject to the VLAN
map of the input VLAN.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
34-36
OL-12189-01
Chapter 34
Configuring Network Security with ACLs
Using VLAN Maps with Router ACLs
Figure 34-5
Applying ACLs on Switched Packets
VLAN 10
map
Input
router
ACL
Output
router
ACL
VLAN 20
map
Frame
Blade
server A
(VLAN 10)
Routing function or
fallback bridge
VLAN 10
Packet
VLAN 20
201776
Blade
server B
(VLAN 10)
ACLs and Bridged Packets
Figure 34-6 shows how an ACL is applied on fallback-bridged packets. For bridged packets, only
Layer 2 ACLs are applied to the input VLAN. Only non-IP, non-ARP packets can be fallback-bridged.
Figure 34-6
Applying ACLs on Bridged Packets
VLAN 10
map
VLAN 20
map
Frame
Blade server A
(VLAN 10)
Blade server B
(VLAN 20)
VLAN 10
Packet
VLAN 20
201777
Fallback bridge
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
34-37
Chapter 34
Configuring Network Security with ACLs
Using VLAN Maps with Router ACLs
ACLs and Routed Packets
Figure 34-7 shows how ACLs are applied on routed packets. For routed packets, the ACLs are applied
in this order:
1.
VLAN map for input VLAN
2.
Input router ACL
3.
Output router ACL
4.
VLAN map for output VLAN
Figure 34-7
Applying ACLs on Routed Packets
VLAN 10
map
Input
router
ACL
Output
router
ACL
VLAN 20
map
Frame
Blade server A
(VLAN 10)
Blade server B
(VLAN 20)
VLAN 10
Packet
VLAN 20
201778
Routing function
ACLs and Multicast Packets
Figure 34-8 shows how ACLs are applied on packets that are replicated for IP multicasting. A multicast
packet being routed has two different kinds of filters applied: one for destinations that are other ports in
the input VLAN and another for each of the destinations that are in other VLANs to which the packet
has been routed. The packet might be routed to more than one output VLAN, in which case a different
router output ACL and VLAN map would apply for each destination VLAN.
The final result is that the packet might be permitted in some of the output VLANs and not in others. A
copy of the packet is forwarded to those destinations where it is permitted. However, if the input VLAN
map (VLAN 10 map in Figure 34-8) drops the packet, no destination receives a copy of the packet.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
34-38
OL-12189-01
Chapter 34
Configuring Network Security with ACLs
Displaying IPv4 ACL Configuration
Figure 34-8
Applying ACLs on Multicast Packets
VLAN 10
map
Input
router
ACL
Output
router
ACL
VLAN 20
map
Frame
Blade server A
(VLAN 10)
Blade server B
(VLAN 20)
Routing function
VLAN 10
Packet
VLAN 20
201779
Blade server C
(VLAN 10)
Displaying IPv4 ACL Configuration
You can display the ACLs that are configured on the switch, and you can display the ACLs that have
been applied to interfaces and VLANs.
When you use the ip access-group interface configuration command to apply ACLs to a Layer 2
interface, you can display the access groups on the interface. You can also display the MAC ACLs
applied to a Layer 2 interface. You can use the privileged EXEC commands as described in Table 34-2
to display this information.
Table 34-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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
34-39
Chapter 34
Configuring Network Security with ACLs
Displaying IPv4 ACL Configuration
You can also display information about VLAN access maps or VLAN filters. Use the privileged EXEC
commands in Table 34-3 to display VLAN map information.
Table 34-3
Commands for Displaying 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
34-40
OL-12189-01
CH A P T E R
35
Configuring IPv6 ACLs
When the switch is running the advanced IP services feature set, you can filter IP Version 6 (IPv6) traffic
by creating IPv6 access control lists (ACLs) and applying them to interfaces as you would create and
apply IP Version 4 (IPv4) named ACLs. You can also create and apply input router ACLs to filter Layer
3 management traffic when the switch is running the IP services or IP base feature set. This chapter
includes information about configuring IPv6 ACLs on the switch. Unless otherwise noted, the term
switch refers to a standalone switch and to a switch stack.
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 {default | vlan}
global configuration command.
For related information, see these chapters:
Note
For more information about SDM templates, see Chapter 8, Configuring SDM Templates.
For information about IPv6 on the switch, see Chapter 39, Configuring IPv6 Host Functions and
Unicast Routing.
For information about ACLs on the switch, see Chapter 34, Configuring Network Security with
ACLs.
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.
This chapter contains these sections:
Supported IPv6 ACLs, page 35-2
Understanding IPv6 ACLs, page 35-2
Configuring IPv6 ACLs, page 35-4
Displaying IPv6 ACLs, page 35-9
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
35-1
Chapter 35
Configuring IPv6 ACLs
Supported IPv6 ACLs
Supported IPv6 ACLs
Table 35-1 shows the supported IPv6 ACLs on each switch.
Table 35-1
Supported IPv6 ACL Features
Feature
Catalyst Switch Module 3110
Catalyst Switch Module 3012
Input router IPv6 ACLs
Yes
Yes
Output router IPv6 ACLs
Yes
No
Input port IPv6 ACLs
Yes
No
Output port IPv6 ACLs
No
No
MAC ACLs
No
No
VLAN ACLs (VLAN maps)
No
No
Understanding IPv6 ACLs
This section has this information:
Supported ACL Features, page 35-2
IPv6 ACL Limitations, page 35-3
IPv6 ACLs and Switch Stacks, page 35-4
Supported ACL Features
IPv6 ACLs on a Catalyst Switch Module 3110 or 3012 have these characteristics:
Fragmented frames (the fragments keyword as in IPv4) are supported.
The same statistics supported in IPv4 are supported for IPv6 ACLs.
If the switch runs out of hardware memory, packets associated with the ACL are forwarded to the
CPU, and the ACLs are applied in software.
IPv6 ACLs on the Catalyst Switch Module 3110 have these characteristics:
A switch running the advanced IP services feature set supports these IPv6 ACLs:
IPv6 router ACLs are supported on outbound or inbound traffic on Layer 3 interfaces, which
can be routed ports, switch virtual interfaces (SVIs), or Layer 3 EtherChannels. IPv6 router
ACLs apply only to IPv6 packets that are routed.
IPv6 port ACLs are supportedonly on inbound traffic on Layer 2 interfaces. IPv6 port ACLs are
applied to all IPv6 packets entering the interface.
Note
A switch running the IP services or IP base feature set supports only input router IPv6 ACLs. It does
not support port ACLs or output IPv6 router ACLs.
If you configure unsupported IPv6 ACLs, an error message appears, and the configuration does
not take affect.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
35-2
OL-12189-01
Chapter 35
Configuring IPv6 ACLs
Understanding IPv6 ACLs
If you create or apply an output router ACL or an input port ACL on a switch running the IP base or
IP services feature set, the ACL is added to the switch configuration but does not take effect; an error
message appears. If you want to use the output router ACL or input port ACL, save the switch
configuration and enable the advanced IP services feature set, which supports the ACL.
The switch does not support VLAN ACLs (VLAN maps) for IPv6 traffic.
Note
For more information about ACL support on the switch, see Chapter 34, Configuring Network
Security with ACLs.
You can apply both IPv4 and IPv6 ACLs to an interface.
As with IPv4 ACLs, IPv6 port ACLs take precedence over router ACLs:
When an input router ACL and input port ACL are in an SVI, packets received on ports to which
a port ACL is applied are filtered by the port ACL. 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, packets received on the ports
to which a port ACL is applied are filtered by the port ACL. Outgoing routed IPv6 packets are
filtered by the router ACL. Other packets are not filtered.
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.
Routed or bridged packets with hop-by-hop options have IPv6 ACLs applied in software.
Logging is supported for router ACLs, but not for port ACLs.
The switch supports IPv6 address-matching for a full range of prefix lengths.
IPv6 ACLs on the Catalyst Switch Module 3012 have these characteristics:
The switch supports only input router IPv6 ACLs applied to all IPv6 management packets entering
the Layer 3 interface.
The switch does not support IPv6 port ACLs, output IPv6 router ACLs, or VLAN ACLs (VLAN
maps) for IPv6 traffic.
IPv6 ACL Limitations
With IPv4, you can configure standard and extended numbered IP ACLs, named IP ACLs, and MAC
ACLs. IPv6 supports only named ACLs.
The switch supports most Cisco IOS-supported IPv6 ACLs with these exceptions:
IPv6 source and destination addressesACL matching is supported only on prefixes from /0 to /64
and host addresses (/128) that are in the extended universal identifier (EUI)-64 format. The Catalyst
Switch Module 3012 supports only these host addresses:
aggregatable global unicast addresses
link local addresses
The switch does not support matching on these keywords: flowlabel, routing header, and
undetermined-transport.
The switch does not support reflexive ACLs (the reflect keyword).
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
35-3
Chapter 35
Configuring IPv6 ACLs
Configuring IPv6 ACLs
The switch does not apply MAC-based ACLs on IPv6 frames.
You cannot apply IPv6 port ACLs to Layer 2 EtherChannels.
Output router ACLs and input port ACLs for IPv6 are supported only when the Catalyst Switch
Module 3110 is running the advanced IP services feature set. A switch running the IP services or IP
base feature set supports only input router ACLs for IPv6 management traffic.
When configuring an ACL, there is no restriction on keywords entered in the ACL, whether or not
they are supported on the platform. When you apply the ACL to an interface that requires hardware
forwarding (physical ports or SVIs), the switch determines whether or not the ACL can besupported
on the interface. If not, ACL attachment is rejected.
If an ACL is applied to an interface and you attempt to add an access control entry (ACE) with an
unsupported keyword, the switch rejects the ACE addition to the ACL.
IPv6 ACLs and Switch Stacks
The stack master supports IPv6 ACLs in hardware and distributes the IPv6 ACLs to the stack members.
Note
For full IPv6 functionality in a switch stack, all stack members must be running the advanced IP services
feature set. Switches running the IP services or IP base feature set support only input router IPv6 ACLs
for IPv6 management traffic.
If a new switch takes over as stack master, it distributes the ACL configuration to all stack members. The
member switches sync up the configuration distributed by the new stack master and flush out entries that
are not required.
When an ACL is modified, attached to, or detached from an interface, the stack master distributes the
change to all stack members.
Configuring IPv6 ACLs
Before configuring IPv6 ACLs, you must select one of the dual IPv4 and IPv6 SDM templates.
To filter IPv6 traffic, you perform these steps:
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.
These sections describe how to configure and apply IPv6 ACLs:
Default IPv6 ACL Configuration, page 35-5
Interaction with Other Features and Switches, page 35-5
Creating IPv6 ACLs, page 35-5
Applying an IPv6 ACL to an Interface, page 35-8
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
35-4
OL-12189-01
Chapter 35
Configuring IPv6 ACLs
Configuring IPv6 ACLs
Default IPv6 ACL Configuration
No IPv6 ACLs are configured or applied.
Interaction with Other Features and Switches
Configuring IPv6 ACLs causes these interactions with other features or switch characteristics:
If an IPv6 router ACL is configured to deny a packet, the packet is not routed. A copy of the packet
is sent to the Internet Control Message Protocol (ICMP) queue to generate an ICMP unreachable
message for the frame.
If a bridged frame is to be dropped due to a port ACL, the frame is not bridged.
You can create both IPv4 and IPv6 ACLs on a switch or switch stack, and you can apply both IPv4
and IPv6 ACLs to the same interface. Each ACL must have a unique name; an error message appears
if you try to use a name that is already configured.
You use different commands to create IPv4 and IPv6 ACLs and to attach them to the same Layer 2
or Layer 3 interface. If you use the wrong command to attach an ACL (for example, an IPv4
command to attach an IPv6 ACL), you receive an error message.
You cannot use MAC ACLs to filter IPv6 frames. MAC ACLs can filter only non-IP frames.
If the hardware memory is full, any additional configured ACLs packets are forwarded to the CPU,
and the ACLs are applied in software.
Creating IPv6 ACLs
Beginning in privileged EXEC mode, follow these steps to create an IPv6 ACL:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ipv6 access-list access-list-name
Define an IPv6 access list using a name, and enter IPv6 access-list
configuration mode.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
35-5
Chapter 35
Configuring IPv6 ACLs
Configuring IPv6 ACLs
Command
Step 3a
Purpose
Enter deny or permit to specify whether to deny or permit the packet if
{deny | permit} protocol
{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.
prefix-length | any |
Note
For additional specific parameters for ICMP, TCP, and UDP, see
host destination-ipv6-address}
Steps 3b through 3d.
[operator [port-number]]
[dscp value] [fragments] [log]
The source-ipv6-prefix/prefix-length or destination-ipv6-prefix/
[log-input] [routing] [sequence
prefix-length is the source or destination IPv6 network or class of networks
value] [time-range name]
for which to set deny or permit conditions, specified in hexadecimal and
using 16-bit values between colons (see RFC 2373).
Enter any as an abbreviation for the IPv6 prefix ::/0.
For host source-ipv6-address or destination-ipv6-address, enter the source
or destination IPv6 host address for which to set deny or permit conditions,
specified in hexadecimal using 16-bit values between colons.
(Optional) For operator, specify an operand that compares the source or
destination ports of the specified protocol. Operands are lt (less than), gt
(greater than), eq (equal), neq (not equal), and range.
If the operator follows the source-ipv6-prefix/prefix-length argument, it
must match the source port. If the operator follows the destination-ipv6prefix/prefix-length argument, it must match the destination port.
(Optional) The port-number is a decimal number from 0 to 65535 or the
name of a TCP or UDP port. You can use TCP port names only when
filtering TCP. You can use UDP port names only when filtering UDP.
(Optional) Enter dscp value to match a differentiated services code point
value against the traffic class value in the Traffic Class field of each IPv6
packet header. The range is from 0 to 63.
(Optional) Enter fragments to check noninitial fragments. This keyword is
visible only if the protocol is ipv6.
(Optional) Enter log to cause an logging message to be sent to the console
about the packet that matches the entry. Enter log-input to include the input
interface in the log entry. Logging is supported only for router ACLs.
(Optional) Enter routing to specify that IPv6 packets be routed.
(Optional) Enter sequence value to specify the sequence number for the
access list statement. The range is from 1 to 4294967295.
(Optional) Enter time-range name to specify the time range that applies to
the deny or permit statement.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
35-6
OL-12189-01
Chapter 35
Configuring IPv6 ACLs
Configuring IPv6 ACLs
Command
Step 3b
Step 3c
Step 3d
Purpose
(Optional) Define a TCP access list and the access conditions.
{deny | permit} tcp
{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]]
ackAcknowledgment bit set.
{destination-ipv6prefix/prefix-length | any | host
establishedAn established connection. A match occurs if the TCP
destination-ipv6-address}
datagram has the ACK or RST bits set.
[operator [port-number]] [ack]
finFinished bit set; no more data from sender.
[dscp value] [established] [fin]
[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] [routing]
pshPush function bit set.
[sequence value] [syn]
range {port | protocol}Matches only packets in the port number range.
[time-range name] [urg]
{deny | permit} udp
{source-ipv6-prefix/prefix-length |
any | host source-ipv6-address}
[operator [port-number]]
{destination-ipv6-prefix/prefixlength | any | host
destination-ipv6-address}
[operator [port-number]] [dscp
value] [log] [log-input] [neq {port
| protocol}] [range {port |
protocol}] [routing] [sequence
value] [time-range name]
{deny | permit} icmp
{source-ipv6-prefix/prefix-length |
any | host source-ipv6-address}
[operator [port-number]]
{destination-ipv6-prefix/prefixlength | any | host
destination-ipv6-address}
[operator [port-number]]
[icmp-type [icmp-code] |
icmp-message] [dscp value] [log]
[log-input] [routing] [sequence
value] [time-range name]
rstReset bit set.
synSynchronize bit set.
urgUrgent pointer bit set.
(Optional) Define a UDP access list and the access conditions.
Enter udp for the User Datagram Protocol. The UDP parameters are the same
as those described for TCP, but the [operator [port]] port number or name must
be a UDP port number or name, and the established parameter is not valid for
UDP.
(Optional) Define an ICMP access list and the access conditions.
Enter icmp for Internet Control Message Protocol. The ICMP parameters are
the same as those described for most IP protocols in Step 3a, with the addition
of the ICMP message type and code parameters. These optional keywords have
these meanings:
icmp-typeFilter by ICMP message type. The range is from 0 to 255, .
icmp-codeFilter ICMP packets that are filtered by the ICMP message
code type. The range is from 0 to 255.
icmp-messageEnter to filter ICMP packets by the ICMP message type
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
startup-config
(Optional) Save your entries in the configuration file.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
35-7
Chapter 35
Configuring IPv6 ACLs
Configuring IPv6 ACLs
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
Applying an IPv6 ACL to an Interface
This section describes how to apply IPv6 ACLs to network interfaces. If the switch is running the
advanced IP services feature set, you can apply an ACL to outbound or inbound traffic on Layer 3
interfaces or to inbound traffic on Layer 2 interfaces. If the switch is running the IP services or IP base
feature set, you can apply ACLs only to inbound management traffic on Layer 3 interfaces.
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 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.
Note
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}
Note
The out keyword is not supported for Layer 2 interfaces (port ACLs).
If the switch is running the IP services or IP base feature set, the out
keyword is not supported for Layer 3 interfaces.
Step 6
end
Return to privileged EXEC mode.
Step 7
show running-config
Verify the access list configuration.
Step 8
copy running-config
startup-config
(Optional) Save your entries in the configuration file.
Use the no ipv6 traffic-filter access-list-name interface configuration command to remove an access list
from an interface.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
35-8
OL-12189-01
Chapter 35
Configuring IPv6 ACLs
Displaying IPv6 ACLs
This example shows how to apply the access list Cisco to outbound traffic on a Layer 3 interface:
Switch(config)# interface gigabitethernet 1/0/3
Switch(config-if)# no switchport
Switch(config-if)# ipv6 address 2001::/64 eui-64
Switch(config-if)# ipv6 traffic-filter CISCO out
Displaying IPv6 ACLs
You can display information about all configured access lists, all IPv6 access lists, or a specific access
list by using either or both of the privileged EXEC commands in Table 35-2.
Table 35-2
Commands for Displaying IPv6 Access List Information
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 lists 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 or switch stack.
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 input and output access lists configured on the switch or switch stack.
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
IPv6 access list outbound
deny udp any any sequence 10
deny tcp any any eq telnet sequence 20
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
35-9
Chapter 35
Configuring IPv6 ACLs
Displaying IPv6 ACLs
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
35-10
OL-12189-01
CH A P T E R
36
Configuring QoS
This chapter describes how to configure quality of service (QoS) by using automatic QoS (auto-QoS)
commands or by using standard QoS commands on the switch. With QoS, you can provide preferential
treatment to certain types of 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. Unless otherwise noted, the term switch refers to
a standalone switch and to a switch stack.
You can configure QoS on physical ports and on switch virtual interfaces (SVIs). Other than to apply
policy maps, you configure the QoS settings, such as classification, queueing, and scheduling, the same
way on physical ports and SVIs. When configuring QoS on a physical port, you apply a nonhierarchical
policy map. When configuring QoS on an SVI, you apply a nonhierarchical or a hierarchical policy map.
Note
For complete syntax and usage information for the commands used in this chapter, see the command
reference this release.
This chapter consists of these sections:
Understanding QoS, page 36-2
Configuring Auto-QoS, page 36-20
Displaying Auto-QoS Information, page 36-29
Configuring Standard QoS, page 36-29
Displaying Standard QoS Information, page 36-78
The switch supports some of the modular QoS CLI (MQC) commands. For more information about the
MQC commands, see the Modular Quality of Service Command-Line Interface Overview at this site:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuration_guide_chapter0918
6a00800bd908.html9
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-1
Chapter 36
Configuring QoS
Understanding QoS
Understanding QoS
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 can also be carried in the
Layer 2 frame. These special bits in the Layer 2 frame or a Layer 3 packet are described here and shown
in Figure 36-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
class of service (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 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 Differentiated Services Code Point
(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.
Note
IPv6 QoS is not supported in this release.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-2
OL-12189-01
Chapter 36
Configuring QoS
Understanding QoS
Figure 36-1
QoS Classification Layers in Frames and Packets
Encapsulated Packet
Layer 2
header
IP header
Data
Layer 2 ISL Frame
ISL header
(26 bytes)
Encapsulated frame 1...
(24.5 KB)
FCS
(4 bytes)
3 bits used for CoS
Layer 2 802.1Q and 802.1p Frame
Preamble
Start frame
delimiter
DA
SA
Tag
PT
Data
FCS
3 bits used for CoS (user priority)
Version
length
ToS
(1 byte)
Len
ID
Offset TTL
Proto FCS IP-SA IP-DA Data
46974
Layer 3 IPv4 Packet
IP precedence or DSCP
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
granularity of control that you need over incoming and outgoing traffic.
Basic QoS Model
To implement QoS, the switch must distinguish packets or flow from one another (classify), 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 traffic sent from it meets a specific traffic profile (shape).
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-3
Chapter 36
Configuring QoS
Understanding QoS
Figure 36-2 shows the basic QoS model. Actions at the ingress port include classifying traffic, policing,
marking, queueing, and scheduling:
Classifying 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 Classification section on page 36-5.
Policing determines whether a packet is in or out of profile by comparing the rate of the incoming
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 Policing and Marking section on
page 36-8.
Marking evaluates the policer and configuration information for the action to be taken when a packet
is out of profile and determines what to do with the packet (pass through a packet without
modification, mark down the QoS label in the packet, or drop the packet). For more information, see
the Policing and Marking section on page 36-8.
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 weighted tail-drop (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 36-13.
Scheduling services the queues based on their configured shaped round robin (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 36-14.
Actions at the egress port include queueing and scheduling:
Figure 36-2
Queueing evaluates the QoS packet label and the corresponding DSCP or CoS value before selecting
which of the four egress queues to use. Because congestion can occur when multiple ingress ports
simultaneously send data to an egress port, WTD differentiates traffic classes and subjects 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 36-13.
Scheduling services the four egress queues based on their configured SRR shared or shaped weights.
One of the queues (queue 1) can be the expedited queue, which is serviced until empty before the
other queues are serviced.
Basic QoS Model
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-4
OL-12189-01
Chapter 36
Configuring QoS
Understanding QoS
Classification
Classification is the process of distinguishing one kind of traffic from another by examining the fields
in the packet. Classification is enabled only if QoS is globally enabled on the switch. By default, QoS is
globally disabled, so no classification occurs.
During 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 decides 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 36-3 on page 36-6.
You specify which fields in the frame or packet that you want to use to classify incoming traffic. For
non-IP traffic, you have these classification options as shown in Figure 36-3:
Trust the CoS value in the incoming 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 3 least-significant bits of the 1-byte User field. Layer 2 802.1Q frame
headers carry the CoS value in the 3 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 incoming 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 access control list (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 as the DSCP and CoS values, which means best-effort traffic.
Otherwise, the policy-map action specifies a DSCP or CoS value to assign to the incoming frame.
For IP traffic, you have these classification options as shown in Figure 36-3:
Trust the DSCP value in the incoming packet (configure the port to trust DSCP), and assign the same
DSCP value to the packet. The IETF defines the 6 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 by using the configurable DSCP-to-DSCP-mutation map.
Trust the IP precedence value in the incoming packet (configure the port to trust IP precedence), and
generate a DSCP value for the packet by using the configurable IP-precedence-to-DSCP map. The
IP Version 4 specification defines the 3 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 incoming packet, and generate a DSCP value for the packet by
using the CoS-to-DSCP map. If the CoS value is not present, use the default 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
CoS value to assign to the incoming frame.
For information on the maps described in this section, see the Mapping Tables section on page 36-12.
For configuration information on port trust states, see the Configuring Classification Using Port Trust
States section on page 36-35.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-5
Chapter 36
Configuring QoS
Understanding QoS
After classification, the packet is sent to the policing, marking, and the ingress queueing and scheduling
stages.
Figure 36-3
Classification Flowchart
Start
Trust CoS (IP and non-IP traffic).
Read ingress interface
configuration for classification. Trust DSCP (IP traffic).
IP and
non-IP
traffic
Trust DSCP or
IP precedence
(non-IP traffic).
Trust IP
precedence
(IP traffic).
Assign DSCP identical
to DSCP in packet.
Check if packet came
with CoS label (tag).
Yes
(Optional) Modify the
DSCP by using the
DSCP-to-DSCP-mutation
map. Use the DSCP
value to generate
the QoS label.
No
Assign default
port CoS.
Use CoS
from frame.
Generate the DSCP based on
IP precedence in packet. Use
the IP-precedence-to-DSCP
map. Use the DSCP value to
generate the QoS label.
Generate DSCP from
CoS-to-DSCP map.
Use the DSCP value to
generate the QoS label.
Done
Done
Check if packet came
with CoS label (tag).
No
Are there any (more) QoS ACLs
configured for this interface?
Yes
No
Yes
Read next ACL. Is there
a match with a "permit" action?
No
Use the CoS value to
generate the QoS label.
Assign the default port
CoS and generate a
DSCP from the
CoS-to-DSCP map.
Yes
Assign the default
DSCP (0).
Generate the DSCP by using
the CoS-to-DSCP map.
Done
Done
86834
Assign the DSCP or CoS as specified
by ACL action to generate the QoS label.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-6
OL-12189-01
Chapter 36
Configuring QoS
Understanding QoS
Classification Based on QoS ACLs
You can use IP standard, IP extended, or Layer 2 MAC ACLs to define a group of packets with the same
characteristics (class). In the QoS context, the permit and deny actions in the access control entries
(ACEs) have different meanings than with security ACLs:
Note
If a match with a permit action is encountered (first-match principle), the specified QoS-related
action is taken.
If a match with a deny action is encountered, the ACL being processed is skipped, 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.
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.
After a traffic class has been 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 rate-limit the class. This
policy is then attached to a particular port on which it becomes effective.
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 a QoS Policy
section on page 36-42.
Classification Based on Class Maps and Policy Maps
A class map is a mechanism that you use to name a specific traffic flow (or class) and to isolate it from
all other traffic. The class map defines the criteria used to match against a specific traffic flow to further
classify it. The criteria can include matching the access group defined by the ACL or matching a specific
list of DSCP or IP precedence values. If you have more than one type of traffic that you want to classify,
you can create another class map and use a different name. After a packet is matched against the
class-map criteria, you further classify it through the use of a policy map.
A policy map specifies which traffic class to act on. Actions can include trusting the CoS, DSCP, or IP
precedence values in the traffic class; setting a specific DSCP or IP precedence value in the traffic class;
or specifying the traffic bandwidth limitations and the action to take when the traffic is out of profile.
Before a policy map can be effective, you must attach it to a port.
You create a class map by using the class-map global configuration command or the class policy-map
configuration command. You should use the class-map command when the map is shared among many
ports. When you enter the class-map command, the switch enters the class-map configuration mode. In
this mode, you define the match criterion for the traffic by using the match class-map configuration
command.
You create and name a policy map by using the policy-map global configuration command. When you
enter this command, the switch enters the policy-map configuration mode. In this mode, you specify the
actions to take on a specific traffic class by using the class, trust, or set policy-map configuration and
policy-map class configuration commands.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-7
Chapter 36
Configuring QoS
Understanding QoS
The policy map can contain the police and police aggregate policy-map class configuration commands,
which define the policer, the bandwidth limitations of the traffic, and the action to take if the limits are
exceeded.
To enable the policy map, you attach it to a port by using the service-policy interface configuration
command.
You can apply a nonhierarchical policy map to a physical port or an SVI. However, a hierarchical policy
map can only be applied to an SVI. A hierarchical 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.
For more information, see the Policing and Marking section on page 36-8. For configuration
information, see the Configuring a QoS Policy section on page 36-42.
Policing and Marking
After a packet is classified and has a DSCP-based or CoS-based QoS label assigned to it, the policing
and marking process can begin as shown in Figure 36-4.
Policing involves creating a policer that specifies the bandwidth limits for the traffic. Packets that exceed
the limits are out of profile or nonconforming. Each 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 36-12. Marked-down packets use
the same queues as the original QoS label to prevent packets in a flow from getting out of order.
Note
All traffic, regardless of whether it is bridged or routed, is subjected to a policer, if one is configured.
As a result, bridged packets might be dropped or might have their DSCP or CoS fields modified when
they are policed and marked.
You can configure policing on a physical port or an SVI. For more information about configuring
policing on physical ports, see the Policing on Physical Ports section on page 36-9. When configuring
policy maps on an SVI, you can create a hierarchical policy map and can define an individual policer
only in the secondary interface-level policy map. For more information, see the Policing on SVIs
section on page 36-10.
After you configure the policy map and policing actions, attach the policy to an ingress port or SVI by
using the service-policy interface configuration command. For configuration information, see the
Classifying, Policing, and Marking Traffic on Physical Ports by Using Policy Maps section on
page 36-48, the Classifying, Policing, and Marking Traffic on SVIs by Using Hierarchical Policy
Maps section on page 36-52, and the Classifying, Policing, and Marking Traffic by Using Aggregate
Policers section on page 36-58.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-8
OL-12189-01
Chapter 36
Configuring QoS
Understanding QoS
Policing on Physical Ports
In policy maps on physical ports, you can create these types of policers:
IndividualQoS applies the bandwidth limits specified in the policer separately to each matched
traffic class. You configure this type of policer within a policy map by using the police policy-map
class configuration command.
AggregateQoS 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.
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 bits
per second. 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 transmitted
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.
Figure 36-4 shows the policing and marking process when these types of policy maps are configured:
A nonhierarchical policy map on a physical port.
The interface level of a hierarchical policy map attached to an SVI. The physical ports are specified
in this secondary policy map.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-9
Chapter 36
Configuring QoS
Understanding QoS
Figure 36-4
Policing and Marking Flowchart on Physical Ports
Start
Get the clasification
result for the packet.
No
Is a policer configured
for this packet?
Yes
Check if the packet is in
profile by querying the policer.
No
Yes
Pass
through
Check out-of-profile action
configured for this policer.
Drop
Drop packet.
Mark
Done
86835
Modify DSCP according to the
policed-DSCP map. Generate
a new QoS label.
Policing on SVIs
Note
Before configuring a hierarchical policy map with individual policers on an SVI, you must enable
VLAN-based QoS on the physical ports that belong to the SVI. Though a policy map is attached to the
SVI, the individual policers only affect traffic on the physical ports specified in the secondary interface
level of the hierarchical policy map.
A hierarchical policy map has two levels. The first level, the VLAN level, specifies the actions to be
taken against a traffic flow on an 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 and are specified in the
interface-level policy map.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-10
OL-12189-01
Chapter 36
Configuring QoS
Understanding QoS
When configuring policing on an SVI, you can create and configure a hierarchical policy map with these
two levels:
VLAN levelCreate this primary level by configuring class maps and classes that specify the port
trust state or set a new DSCP or IP precedence value in the packet. The VLAN-level policy map
applies only to the VLAN in an SVI and does not support policers.
Interface levelCreate 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. You can configure different
interface-level policy maps for each class defined in the VLAN-level policy map.
See the Classifying, Policing, and Marking Traffic on SVIs by Using Hierarchical Policy Maps section
on page 36-52 for an example of a hierarchical policy map.
Figure 36-5 shows the policing and marking process when hierarchical policy maps on an SVI.
Figure 36-5
Policing and Marking Flowchart on SVIs
Start
Get the VLAN and
interface-level classification
results for the packet.
Is an interface-level policer
configured for this packet?
No
Yes
Verify if the packet is in the
profile by querying the policer.
No
Yes
Pass
through
Verify the out-of-profile action
configured for this policer.
Drop
Drop packet.
Mark
Done
92355
Modify DSCP according to the
policed-DSCP map. Generate
a new QoS label.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-11
Chapter 36
Configuring QoS
Understanding QoS
Mapping Tables
During QoS processing, the switch represents the priority of all traffic (including non-IP traffic) with an
QoS label based on the DSCP or CoS value from the classification stage:
During 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 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 packet
and selects the queue 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.
The CoS-to-DSCP, DSCP-to-CoS, and the IP-precedence-to-DSCP maps have default values that might
or might not be appropriate for your network.
The default DSCP-to-DSCP-mutation map and the default policed-DSCP map are null maps; they map
an incoming DSCP value to the same DSCP value. The DSCP-to-DSCP-mutation map is the only map
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 36-60.
For information about the DSCP and CoS input queue threshold maps, see the Queueing and
Scheduling on Ingress Queues section on page 36-15. For information about the DSCP and CoS output
queue threshold maps, see the Queueing and Scheduling on Egress Queues section on page 36-17.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-12
OL-12189-01
Chapter 36
Configuring QoS
Understanding QoS
Queueing and Scheduling Overview
The switch has queues at specific points to help prevent congestion as shown in Figure 36-6.
Figure 36-6
Ingress and Egress Queue Location
Policer
Policer
Marker
Stack ring
Marker
Egress
queues
Ingress
queues
Classify
SRR
Policer
Marker
Policer
Marker
SRR
86691
Traffic
Because the total inbound bandwidth of all ports can exceed the bandwidth of the stack or 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, outbound queues are located after the stack or internal ring.
Weighted Tail Drop
Both the ingress and egress queues use an enhanced version of the tail-drop congestion-avoidance
mechanism called weighted tail drop (WTD). WTD is implemented on queues to manage the queue
lengths and to provide drop precedences for different traffic classifications.
As a frame is enqueued to a particular queue, WTD uses the frames assigned QoS label to subject it to
different thresholds. If the threshold is exceeded for that QoS label (the space available in the destination
queue is less than the size of the frame), the switch drops the frame.
Each queue has three threshold values. The QOS label is determines which of the three threshold values
is subjected to the frame. Of the three thresholds, two are configurable (explicit) and one is not (implicit).
Figure 36-7 shows an example of WTD operating on a queue whose size is 1000 frames. Three drop
percentages are configured: 40 percent (400 frames), 60 percent (600 frames), and 100 percent (1000
frames). These percentages mean that up to 400 frames can be queued at the 40-percent threshold, up to
600 frames at the 60-percent threshold, and up to 1000 frames at the 100-percent threshold.
In this example, CoS values 6 and 7 have a greater importance than the other CoS values, and they are
assigned to the 100-percent drop threshold (queue-full state). CoS values 4 and 5 are assigned to the
60-percent threshold, and CoS values 0 to 3 are assigned to the 40-percent threshold.
Suppose the queue is already filled with 600 frames, and a new frame arrives. It contains CoS values 4
and 5 and is subjected to the 60-percent threshold. If this frame is added to the queue, the threshold will
be exceeded, so the switch drops it.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-13
Chapter 36
Configuring QoS
Understanding QoS
CoS 6-7
CoS 4-5
CoS 0-3
WTD and Queue Operation
100%
1000
60%
600
40%
400
0
86692
Figure 36-7
For more information, see the Mapping DSCP or CoS Values to an Ingress Queue and Setting WTD
Thresholds section on page 36-67, the Allocating Buffer Space to and Setting WTD Thresholds for an
Egress Queue-Set section on page 36-71, and the Mapping DSCP or CoS Values to an Egress Queue
and to a Threshold ID section on page 36-73.
SRR Shaping and Sharing
Both the ingress and egress queues are serviced by SRR, which controls the rate at which packets are
sent. On the ingress queues, SRR sends packets to the stack or internal ring. On the egress queues, SRR
sends packets to the egress port.
You can configure SRR on egress queues for sharing or for shaping. However, for ingress queues, sharing
is the default mode, and it is the only mode supported.
In shaped mode, the egress queues are guaranteed a percentage of the bandwidth, and they are
rate-limited to that amount. Shaped traffic does not use more than the allocated bandwidth even if the
link is idle. Shaping provides a more even flow of traffic over time and reduces the peaks and valleys of
bursty traffic. With shaping, the absolute value of each weight is used to compute the bandwidth
available for the queues.
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 36-68, the Configuring SRR Shaped Weights on Egress Queues section on page 36-75, and the
Configuring SRR Shared Weights on Egress Queues section on page 36-76.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-14
OL-12189-01
Chapter 36
Configuring QoS
Understanding QoS
Queueing and Scheduling on Ingress Queues
Figure 36-8 shows the queueing and scheduling flowchart for ingress ports.
Figure 36-8
Queueing and Scheduling Flowchart for Ingress Ports
Start
Read QoS label
(DSCP or CoS value).
Determine ingress queue
number, buffer allocation,
and WTD thresholds.
Are thresholds
being exceeded?
Yes
No
Drop packet.
Send packet to
the stack ring.
Note
86693
Queue the packet. Service
the queue according to
the SRR weights.
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 36-1 describes the queues.
Table 36-1
Ingress Queue Types
Queue Type1
Function
Normal
User traffic that is considered to be normal priority. You can configure three different
thresholds to differentiate among the flows. You can use the mls qos srr-queue input
threshold, the mls qos srr-queue input dscp-map, and the mls qos srr-queue input
cos-map global configuration commands.
Expedite
High-priority user traffic such as differentiated services (DF) expedited forwarding or
voice traffic. You can configure the bandwidth required for this traffic as a percentage
of the total traffic or total stack traffic by using the mls qos srr-queue input
priority-queue global configuration command. The expedite queue has guaranteed
bandwidth.
1. The switch uses two nonconfigurable queues for traffic that is essential for proper network and stack operation.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-15
Chapter 36
Configuring QoS
Understanding QoS
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.
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 36-13.
Buffer and Bandwidth Allocation
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.
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 stack or 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 DSCPs or CoSs 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 36-66.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-16
OL-12189-01
Chapter 36
Configuring QoS
Understanding QoS
Queueing and Scheduling on Egress Queues
Figure 36-9 shows the queueing and scheduling flowchart for egress ports.
Note
If the expedite queue is enabled, SRR services it until it is empty before servicing the other three queues.
Figure 36-9
Queueing and Scheduling Flowchart for Egress Ports
Start
Receive packet from
the stack ring.
Read QoS label
(DSCP or CoS value).
Determine egress queue
number and threshold
based on the label.
Are thresholds
being exceeded?
No
Yes
Drop packet.
Queue the packet. Service
the queue according to
the SRR weights.
Rewrite DSCP and/or
CoS value as
appropriate.
Done
86694
Send the packet
out the port.
Each port supports four egress queues, one of which (queue 1) can be the egress expedite queue. These
queues are assigned to a queue-set. All traffic exiting the switch flows through one of these four queues
and is subjected to a threshold based on the QoS label assigned to the packet.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-17
Chapter 36
Configuring QoS
Understanding QoS
Figure 36-10 shows the egress queue 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
the target queue has not 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.
Figure 36-10
Egress Queue Buffer Allocation
Reserved pool
86695
Port 2 queue 2
Port 2 queue 1
Port 1 queue 4
Port 1 queue 3
Port 1 queue 2
Port 1 queue 1
Common pool
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 queues 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-18
OL-12189-01
Chapter 36
Configuring QoS
Understanding QoS
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 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.
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 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. You map a port to queue-set by using the queue-set qset-id interface configuration command.
Modify the queue-set configuration to change the WTD threshold percentages. For more information
about how WTD works, see the Weighted Tail Drop section on page 36-13.
Shaped or Shared Mode
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 the 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. For an explanation of the
differences between shaping and sharing, see the SRR Shaping and Sharing section on page 36-14.
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 expedite queue is enabled, in which case the first
bandwidth weight is ignored and is not used in the ratio calculation. The expedite queue is a priority
queue, and it is serviced until empty before the other queues are serviced. You enable the expedite 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 DSCPs or CoSs 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 Characteristics section on page 36-70.
Note
The egress queue default settings are suitable for most situations. You should change them only when
you have a thorough understanding of the egress queues and if these settings do not meet your QoS
solution.
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, 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-19
Chapter 36
Configuring QoS
Configuring Auto-QoS
During 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.
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 incoming 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
incoming 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.
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 default 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 Cisco IP Phones
Configures QoS classification
Configures egress queues
These sections contain this configuration information:
Generated Auto-QoS Configuration, page 36-21
Effects of Auto-QoS on the Configuration, page 36-25
Auto-QoS Configuration Guidelines, page 36-25
Enabling Auto-QoS for VoIP, page 36-26
Auto-QoS Configuration Example, page 36-27
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-20
OL-12189-01
Chapter 36
Configuring QoS
Configuring Auto-QoS
Generated Auto-QoS Configuration
By default, auto-QoS is disabled on all ports.
When auto-QoS is enabled, it uses the ingress packet label to categorize traffic, to assign packet labels,
and to configure the ingress and egress queues as shown in Table 36-2.
Table 36-2
Traffic Types, Packet Labels, and Queues
VoIP1 Data
Traffic
VoIP Control
Traffic
Routing Protocol
Traffic
STP BPDU
Traffic
Real-Time
Video Traffic
All Other Traffic
DSCP
46
24, 26
48
56
34
CoS
CoS-to-Ingress
Queue Map
2, 3, 4, 5, 6, 7 (queue 2)
CoS-to-Egress
Queue Map
5 (queue 1)
0, 1 (queue 1)
3, 6, 7 (queue 2)
4 (queue 3)
2 (queue 3)
0, 1
(queue 4)
1. VoIP = voice over IP
Table 36-3 shows the generated auto-QoS configuration for the ingress queues.
Table 36-3
Auto-QoS Configuration for the Ingress Queues
Ingress Queue
Queue Number
CoS-to-Queue Map
Queue Weight
(Bandwidth)
Queue (Buffer)
Size
SRR shared
0, 1
81 percent
67 percent
Priority
2, 3, 4, 5, 6, 7
19 percent
33 percent
Table 36-4 shows the generated auto-QoS configuration for the egress queues.
Table 36-4
Auto-QoS Configuration for the Egress Queues
Queue (Buffer) Size Queue (Buffer)
for Gigabit-Capable Size for 10/100
Ports
Ethernet Ports
Egress Queue
Queue Number
CoS-to-Queue Map
Queue Weight
(Bandwidth)
SRR shared
3, 6, 7
10 percent
6 percent
10 percent
SRR shared
2, 4
60 percent
17 percent
26 percent
SRR shared
0, 1
20 percent
61 percent
54 percent
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-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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-21
Chapter 36
Configuring QoS
Configuring Auto-QoS
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 36-3 and Table 36-4.
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 and egress queues on the port according to the
settings in Table 36-3 and Table 36-4.
For information about the trusted boundary feature, see the Configuring a Trusted Boundary to
Ensure Port Security section on page 36-38.
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 ingress packet label and applies the commands listed in
Table 36-5 to the port.
Table 36-5
Description
Generated Auto-QoS Configuration
Automatically Generated Command
The switch automatically enables standard QoS and configures Switch(config)# mls qos
the CoS-to-DSCP map (maps CoS values in incoming packets Switch(config)# mls qos map cos-dscp 0 8 16 26 32 46
48 56
to a DSCP value).
The switch automatically maps CoS values to an ingress queue Switch(config)# no mls qos srr-queue input cos-map
Switch(config)# mls qos srr-queue input cos-map
and to a threshold ID.
queue 1 threshold 3
Switch(config)# mls
queue 1 threshold 2
Switch(config)# mls
queue 2 threshold 1
Switch(config)# mls
queue 2 threshold 2
Switch(config)# mls
queue 2 threshold 3
0
qos
1
qos
2
qos
4 6
qos
3 5
srr-queue input cos-map
srr-queue input cos-map
srr-queue input cos-map
7
srr-queue input cos-map
The switch automatically maps CoS values to an egress queue Switch(config)# no mls qos srr-queue output cos-map
Switch(config)# mls qos srr-queue output cos-map
and to a threshold ID.
queue 1 threshold 3
Switch(config)# mls
queue 2 threshold 3
Switch(config)# mls
queue 3 threshold 3
Switch(config)# mls
queue 4 threshold 2
Switch(config)# mls
queue 4 threshold 3
5
qos
3 6
qos
2 4
qos
1
qos
0
srr-queue output cos-map
7
srr-queue output cos-map
srr-queue output cos-map
srr-queue output cos-map
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-22
OL-12189-01
Chapter 36
Configuring QoS
Configuring Auto-QoS
Table 36-5
Generated Auto-QoS Configuration (continued)
Description
Automatically Generated Command
The switch automatically maps DSCP values to an ingress
queue and to a threshold ID.
Switch(config)# no mls qos srr-queue input dscp-map
Switch(config)# mls qos srr-queue input dscp-map
queue 1 threshold 2 9 10 11 12 13 14 15
Switch(config)# mls qos srr-queue input dscp-map
queue 1 threshold 3 0 1 2 3 4 5 6 7
Switch(config)# mls qos srr-queue input dscp-map
queue 1 threshold 3 32
Switch(config)# mls qos srr-queue input dscp-map
queue 2 threshold 1 16 17 18 19 20 21 22 23
Switch(config)# mls qos srr-queue input dscp-map
queue 2 threshold 2 33 34 35 36 37 38 39 48
Switch(config)# mls qos srr-queue input dscp-map
queue 2 threshold 2 49 50 51 52 53 54 55 56
Switch(config)# mls qos srr-queue input dscp-map
queue 2 threshold 2 57 58 59 60 61 62 63
Switch(config)# mls qos srr-queue input dscp-map
queue 2 threshold 3 24 25 26 27 28 29 30 31
Switch(config)# mls qos srr-queue input dscp-map
queue 2 threshold 3 40 41 42 43 44 45 46 47
The switch automatically maps DSCP values to an egress
queue and to a threshold ID.
Switch(config)# no mls qos srr-queue output dscp-map
Switch(config)# mls qos srr-queue output dscp-map
queue 1 threshold 3 40 41 42 43 44 45 46 47
Switch(config)# mls qos srr-queue output dscp-map
queue 2 threshold 3 24 25 26 27 28 29 30 31
Switch(config)# mls qos srr-queue output dscp-map
queue 2 threshold 3 48 49 50 51 52 53 54 55
Switch(config)# mls qos srr-queue output dscp-map
queue 2 threshold 3 56 57 58 59 60 61 62 63
Switch(config)# mls qos srr-queue output dscp-map
queue 3 threshold 3 16 17 18 19 20 21 22 23
Switch(config)# mls qos srr-queue output dscp-map
queue 3 threshold 3 32 33 34 35 36 37 38 39
Switch(config)# mls qos srr-queue output dscp-map
queue 4 threshold 1 8
Switch(config)# mls qos srr-queue output dscp-map
queue 4 threshold 2 9 10 11 12 13 14 15
Switch(config)# mls qos srr-queue output dscp-map
queue 4 threshold 3 0 1 2 3 4 5 6 7
The switch automatically sets up the ingress queues, with
queue 2 as the priority queue and queue 1 in shared mode. The
switch also configures the bandwidth and buffer size for the
ingress queues.
Switch(config)# no mls qos srr-queue input
priority-queue 1
Switch(config)# no mls qos srr-queue input
priority-queue 2
Switch(config)# mls qos srr-queue input bandwidth 90
10
Switch(config)# mls qos srr-queue input threshold 1
8 16
Switch(config)# mls qos srr-queue input threshold 2
34 66
Switch(config)# mls qos srr-queue input buffers 67
33
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-23
Chapter 36
Configuring QoS
Configuring Auto-QoS
Table 36-5
Generated Auto-QoS Configuration (continued)
Description
Automatically Generated Command
The switch automatically configures the egress queue buffer
sizes. It configures the bandwidth and the SRR mode (shaped
or shared) on the egress queues mapped to the port.
Switch(config)# mls
1 138 138 92 138
Switch(config)# mls
2 138 138 92 400
Switch(config)# mls
3 36 77 100 318
Switch(config)# mls
4 20 50 67 400
Switch(config)# mls
1 149 149 100 149
Switch(config)# mls
2 118 118 100 235
Switch(config)# mls
3 41 68 100 272
Switch(config)# mls
4 42 72 100 242
Switch(config)# mls
10 10 26 54
Switch(config)# mls
16 6 17 61
qos queue-set output 1 threshold
qos queue-set output 1 threshold
qos queue-set output 1 threshold
qos queue-set output 1 threshold
qos queue-set output 2 threshold
qos queue-set output 2 threshold
qos queue-set output 2 threshold
qos queue-set output 2 threshold
qos queue-set output 1 buffers
qos queue-set output 2 buffers
Switch(config-if)# srr-queue bandwidth share 10 10
60 20
If you entered the auto qos voip trust command, the switch
automatically sets the ingress classification to trust the CoS
value received in the packet on a nonrouted port by using the
mls qos trust cos command or to trust the DSCP value
received in the packet on a routed port by using the mls qos
trust dscp command.
Switch(config-if)# mls qos trust cos
Switch(config-if)# mls qos trust dscp
If you entered the auto qos voip cisco-phone command, the
switch automatically enables the trusted boundary feature,
which uses the CDP to detect the presence or absence of a
Cisco IP Phone.
Switch(config-if)# mls qos trust device cisco-phone
If you entered the auto qos voip cisco-softphone command,
the switch automatically creates class maps and policy maps.
Switch(config)# mls qos map policed-dscp 24 26 46 to
0
Switch(config)# class-map match-all
AutoQoS-VoIP-RTP-Trust
Switch(config-cmap)# match ip dscp ef
Switch(config)# class-map match-all
AutoQoS-VoIP-Control-Trust
Switch(config-cmap)# match ip dscp cs3 af31
Switch(config)# policy-map AutoQoS-Police-SoftPhone
Switch(config-pmap)# class AutoQoS-VoIP-RTP-Trust
Switch(config-pmap-c)# set dscp ef
Switch(config-pmap-c)# police 320000 8000
exceed-action policed-dscp-transmit
Switch(config-pmap)# class
AutoQoS-VoIP-Control-Trust
Switch(config-pmap-c)# set dscp cs3
Switch(config-pmap-c)# police 32000 8000
exceed-action policed-dscp-transmit
After creating the class maps and policy maps, the switch
automatically applies the policy map called
AutoQoS-Police-SoftPhone to an ingress interface on which
auto-QoS with the Cisco SoftPhone feature is enabled.
Switch(config-if)# service-policy input
AutoQoS-Police-SoftPhone
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-24
OL-12189-01
Chapter 36
Configuring QoS
Configuring Auto-QoS
Effects of Auto-QoS on the Configuration
When auto-QoS is enabled, the auto qos voip interface configuration command and the generated
configuration are added to the running configuration.
The switch applies the auto-QoS-generated commands as if the commands were entered from the CLI.
An existing user configuration can cause the application of the generated commands to fail or to be
overridden by the generated commands. These actions occur without warning. If all the generated
commands are successfully applied, any user-entered configuration that was not overridden remains in
the running configuration. Any user-entered configuration that was overridden can be retrieved by
reloading the switch without saving the current configuration to memory. If the generated commands fail
to be applied, the previous running configuration is restored.
Auto-QoS Configuration Guidelines
Before configuring auto-QoS, you should be aware of this information:
Auto-QoS configures the switch for VoIP with Cisco IP Phones on nonrouted and routed ports.
Auto-QoS also configures the switch for VoIP with devices running the Cisco SoftPhone
application.
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 defaults, 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 36-25.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-25
Chapter 36
Configuring QoS
Configuring Auto-QoS
Enabling Auto-QoS for VoIP
Beginning in privileged EXEC mode, follow these steps to enable auto-QoS for VoIP within a QoS
domain:
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, the port that is
connected to a device running the Cisco SoftPhone feature, or the
uplink port that is connected to another trusted switch or router in the
interior of the network, and enter interface configuration mode.
Step 3
auto qos voip {cisco-phone |
cisco-softphone | trust}
Enable auto-QoS.
The keywords have these meanings:
cisco-phoneIf the port is connected to a Cisco IP Phone, the
QoS labels of incoming packets are trusted only when the
telephone is detected.
cisco-softphoneThe port is connected to device running the
Cisco SoftPhone feature.
trustThe 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 auto-QoS command on the interface on
which auto-QoS was enabled. 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 auto qos 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 and to trust the QoS labels received in incoming packets
when the switch or router connected to a port is a trusted device:
Switch(config)# interface gigabitethernet2/0/1
Switch(config-if)# auto qos voip trust
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-26
OL-12189-01
Chapter 36
Configuring QoS
Configuring Auto-QoS
Auto-QoS Configuration Example
This section describes how you could implement auto-QoS in a network, as shown in Figure 36-11. For
optimum QoS performance, enable auto-QoS on all the devices in the network.
Figure 36-11
Auto-QoS Configuration Example Network
Cisco router
To Internet
Trunk
link
Trunk
link
Video server
172.20.10.16
Cisco
Blade
switch
Blade servers
Identify this interface
as connected to a
trusted switch or router
Identify this interface
as connected to a
trusted switch or router
IP
Cisco IP phones
IP
Identify these
interfaces as
connected to
IP phones
Identify these
interfaces as
connected to
IP phones
IP
Cisco IP phones
201780
IP
Figure 36-11 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 domain.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-27
Chapter 36
Configuring QoS
Configuring Auto-QoS
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 incoming packets are trusted only when the
Cisco IP Phone is detected.
Step 6
exit
Step 7
Return to global configuration mode.
Repeat Steps 4 to 6 for as many ports as are connected to the Cisco
IP Phone.
Step 8
interface interface-id
Specify the switch port identified as connected to a trusted switch
or router, and enter interface configuration mode. See
Figure 36-11.
Step 9
auto qos voip trust
Enable auto-QoS on the port, and specify that the port is connected
to a trusted router or switch.
Step 10
end
Return to privileged EXEC mode.
Step 11
show auto qos
Verify your entries.
This command displays the auto-QoS command on the interface
on which auto-QoS was enabled. You can use the show
running-config privileged EXEC command to display the
auto-QoS configuration and the user modifications.
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 12
copy running-config
startup-config
Save the auto qos voip interface configuration commands and the
generated auto-QoS configuration in the configuration file.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-28
OL-12189-01
Chapter 36
Configuring QoS
Displaying Auto-QoS Information
Displaying Auto-QoS Information
To display the initial auto-QoS configuration, use the show auto qos [interface [interface-id]]
privileged EXEC command. To display any user changes to that configuration, use the show
running-config privileged EXEC command. You can compare the show auto qos and the show
running-config command output to identify the user-defined QoS settings.
To display information about the QoS configuration that might be affected by auto-QoS, use one of these
commands:
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.
Configuring Standard QoS
Before configuring standard QoS, you must have a thorough understanding of these items:
The types of applications used and the traffic patterns on your network.
Traffic characteristics and needs of your network. Is the traffic bursty? Do you need to reserve
bandwidth for voice and video streams?
Bandwidth requirements and speed of the network.
Location of congestion points in the network.
These sections contain this configuration information:
Default Standard QoS Configuration, page 36-30
Standard QoS Configuration Guidelines, page 36-32
Enabling QoS Globally, page 36-34 (required)
Enabling VLAN-Based QoS on Physical Ports, page 36-34 (optional)
Configuring Classification Using Port Trust States, page 36-35 (required
Configuring a QoS Policy, page 36-42 (required)
Configuring DSCP Maps, page 36-60 (optional, unless you need to use the
DSCP-to-DSCP-mutation map or the policed-DSCP map)
Configuring Ingress Queue Characteristics, page 36-66 (optional)
Configuring Egress Queue Characteristics, page 36-70 (optional)
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-29
Chapter 36
Configuring QoS
Configuring Standard QoS
Default Standard QoS Configuration
QoS is 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).
When QoS is enabled with the mls qos global configuration command and all other QoS settings are at
their defaults, traffic is classified as best effort (the DSCP and CoS value is set to 0) without any policing.
No policy maps are configured. The default port trust state on all ports is untrusted. The default ingress
and egress queue settings are described in the Default Ingress Queue Configuration section on
page 36-30 and the Default Egress Queue Configuration section on page 36-31.
Default Ingress Queue Configuration
Table 36-6 shows the default ingress queue configuration when QoS is enabled.
Table 36-6
Default Ingress Queue Configuration
Feature
Queue 1
Queue 2
Buffer allocation
90 percent
10 percent
10
WTD drop threshold 1
100 percent
100 percent
WTD drop threshold 2
100 percent
100 percent
Bandwidth allocation 1
Priority queue bandwidth
1. The bandwidth is equally shared between the queues. SRR sends packets in shared mode only.
2. Queue 2 is the priority queue. SRR services the priority queue for its configured share before servicing the other queue.
Table 36-7 shows the default CoS input queue threshold map when QoS is enabled.
Table 36-7
Default CoS Input Queue Threshold Map
CoS Value
Queue IDThreshold ID
04
11
21
6, 7
11
Table 36-8 shows the default DSCP input queue threshold map when QoS is enabled.
Table 36-8
Default DSCP Input Queue Threshold Map
DSCP Value
Queue IDThreshold ID
039
11
4047
21
4863
11
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-30
OL-12189-01
Chapter 36
Configuring QoS
Configuring Standard QoS
Default Egress Queue Configuration
Table 36-9 shows the default egress queue configuration for each queue-set when QoS is enabled. All
ports are mapped to queue-set 1. The port bandwidth limit is set to 100 percent and rate unlimited.
Table 36-9
Default Egress Queue Configuration
Feature
Queue 1
Queue 2
Queue 3
Queue 4
Buffer allocation
25 percent
25 percent
25 percent
25 percent
WTD drop threshold 1
100 percent
200 percent
100 percent
100 percent
WTD drop threshold 2
100 percent
200 percent
100 percent
100 percent
Reserved threshold
50 percent
50 percent
50 percent
50 percent
Maximum threshold
400 percent
400 percent
400 percent
400 percent
SRR shaped weights
(absolute) 1
25
SRR shared weights 2
25
25
25
25
1. A shaped weight of zero means that this queue is operating in shared mode.
2. One quarter of the bandwidth is allocated to each queue.
Table 36-10 shows the default CoS output queue threshold map when QoS is enabled.
Table 36-10
Default CoS Output Queue Threshold Map
CoS Value
Queue IDThreshold ID
0, 1
21
2, 3
31
41
11
6, 7
41
Table 36-11 shows the default DSCP output queue threshold map when QoS is enabled.
Table 36-11
Default DSCP Output Queue Threshold Map
DSCP Value
Queue IDThreshold ID
015
21
1631
31
3239
41
4047
11
4863
41
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-31
Chapter 36
Configuring QoS
Configuring Standard QoS
Default Mapping Table Configuration
The default CoS-to-DSCP map is shown in Table 36-12 on page 36-60.
The default IP-precedence-to-DSCP map is shown in Table 36-13 on page 36-61.
The default DSCP-to-CoS map is shown in Table 36-14 on page 36-63.
The default DSCP-to-DSCP-mutation map is a null map, which maps an incoming DSCP value to the
same DSCP value.
The default policed-DSCP map is a null map, which maps an incoming DSCP value to the same DSCP
value (no markdown).
Standard QoS Configuration Guidelines
Before beginning the QoS configuration, you should be aware of this information in these sections:
QoS ACL Guidelines section on page 36-32
Applying QoS on Interfaces section on page 36-32
Policing Guidelines section on page 36-33
General QoS Guidelines section on page 36-33
QoS ACL Guidelines
These are the guidelines with for configuring QoS with access control lists (ACLs):
It is not possible to match IP fragments against configured IP extended ACLs to enforce QoS. IP
fragments are sent as best-effort. IP fragments are denoted by fields in the IP header.
Only one ACL per class map and only one match class-map configuration command per class map
are supported. The ACL can have multiple ACEs, which match fields against the contents of the
packet.
A trust statement in a policy map requires multiple hardware entries per ACL line. If an input service
policy map contains a trust statement in an ACL, the access list might be too large to fit into the
available QoS hardware memory, and an error can occur when you apply the policy map to a port.
Whenever possible, you should minimize the number of lines is a QoS ACL.
Applying QoS on Interfaces
These are the guidelines with for configuring QoS on physical ports. This section also applies to SVIs
(Layer 3 interfaces):
You can configure QoS on physical ports and SVIs. When configuring QoS on physical ports, you
create and apply nonhierarchical policy maps. When configuring QoS on SVIs, you can create and
apply nonhierarchical and hierarchical policy maps.
Incoming traffic is classified, policed, and marked down (if configured) regardless of whether the
traffic is bridged, routed, or sent to the CPU. It is possible for bridged frames to be dropped or to
have their DSCP and CoS values modified.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-32
OL-12189-01
Chapter 36
Configuring QoS
Configuring Standard QoS
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 hierarchical 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 hierarchical policy map.
The switch does not support aggregate policers in hierarchical policy maps.
After the hierarchical policy map is attached to an SVI, the interface-level policy map cannot
be modified or removed from the hierarchical policy map. A new interface-level policy map also
cannot be added to the hierarchical policy map. If you want these changes to occur, the
hierarchical policy map must first be removed from the SVI. You also cannot add or remove a
class map specified in the hierarchical policy map.
Policing Guidelines
These are the policing guidelines:
The port ASIC device, which controls more than one physical port, supports 256 policers
(255 user-configurable e policers plus 1 policer reserved for system internal use). The maximum
number of user-configurable policers supported per port is 63. For example, you could configure 32
policers on a Gigabit Ethernet port and 7 policers on a 10-Gigabit Ethernet port, or you could
configure 64 policers on a Gigabit Ethernet port and 4 policers on a 10-Gigabit Ethernet port.
Policers are allocated on demand by the software and are constrained by the hardware and ASIC
boundaries. You cannot reserve policers per port; there is no guarantee that a port will be assigned
to any policer.
Only one policer is applied to a packet on an ingress port. Only the average rate and committed burst
parameters are configurable.
You can create an aggregate policer that is shared by multiple traffic classes within the same
nonhierarchical policy map. However, you cannot use the aggregate policer across different policy
maps.
On a port configured for QoS, all traffic received through the port is classified, policed, and marked
according to the policy map attached to the port. On a trunk port configured for QoS, traffic in all
VLANs received through the port is classified, policed, and marked according to the policy map
attached to the port.
If you have EtherChannel ports configured on your switch, you must configure QoS classification,
policing, mapping, and queueing on the individual physical ports that comprise the EtherChannel.
You must decide whether the QoS configuration should match on all ports in the EtherChannel.
General QoS Guidelines
These are general QoS guidelines:
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-33
Chapter 36
Configuring QoS
Configuring Standard QoS
A switch that is running the IP services feature set supports QoS DSCP and IP precedence matching
in policy-based routing (PBR) route maps with these limitations:
You cannot apply QoS DSCP mutation maps and PBR route maps to the same interface.
You cannot configure DSCP transparency and PBR DSCP route maps on the same switch.
Enabling QoS Globally
By default, QoS is disabled on the switch.
Beginning in privileged EXEC mode, follow these steps to enable QoS. This procedure is required.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
mls qos
Enable QoS globally.
QoS runs with the default settings described in the Default
Standard QoS Configuration section on page 36-30, the
Queueing and Scheduling on Ingress Queues section on
page 36-15, and the Queueing and Scheduling on Egress
Queues section on page 36-17.
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.
To disable QoS, use the no mls qos global configuration command.
Enabling VLAN-Based QoS on Physical Ports
By default, VLAN-based QoS is disabled on all physical switch ports. The switch applies QoS, including
class maps and policy maps, only on a physical-port basis. In Cisco IOS Release 12.2(25)SE or later,
yYou can enable VLAN-based QoS on a switch port.
Beginning in privileged EXEC mode, follow these steps to enable VLAN-based QoS. This procedure is
required on physical ports that are specified in the interface level of a hierarchical policy map on an SVI.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
interface interface-id
Specify the physical port, and enter interface configuration
mode.
Step 3
mls qos vlan-based
Enable VLAN-based QoS on the port.
Step 4
end
Return to privileged EXEC mode.
Step 5
show mls qos interface interface-id
Verify if VLAN-based QoS is enabled on the physical port.
Step 6
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-34
OL-12189-01
Chapter 36
Configuring QoS
Configuring Standard QoS
Use the no mls qos vlan-based interface configuration command to disable VLAN-based QoS on the
physical port.
Configuring Classification Using Port Trust States
These sections describe how to classify incoming traffic by using port trust states. Depending on your
network configuration, you must perform one or more of these tasks or one or more of the tasks in the
Configuring a QoS Policy section on page 36-42:
Configuring the Trust State on Ports within the QoS Domain, page 36-35
Configuring the CoS Value for an Interface, page 36-37
Configuring a Trusted Boundary to Ensure Port Security, page 36-38
Enabling DSCP Transparency Mode, page 36-39
Configuring the DSCP Trust State on a Port Bordering Another QoS Domain, page 36-40
Configuring the Trust State on Ports within the QoS Domain
Packets entering a QoS domain are classified at the edge of the QoS domain. When the packets are
classified at the edge, the switch port within the QoS domain can be configured to one of the trusted
states because there is no need to classify the packets at every switch within the QoS domain.
Figure 36-12 shows a sample network topology.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-35
Chapter 36
Configuring QoS
Configuring Standard QoS
Figure 36-12
Port Trusted States within the QoS Domain
Trusted interface
Trunk
Traffic classification
performed here
P1
201781
P3
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-36
OL-12189-01
Chapter 36
Configuring QoS
Configuring Standard QoS
Step 3
Command
Purpose
mls qos trust [cos | dscp | ip-precedence]
Configure the port trust state.
By default, the port is not trusted. If no keyword is specified, the
default is dscp.
The keywords have these meanings:
cosClassifies an ingress packet by using the packet CoS value.
For an untagged packet, the port default CoS value is used. The
default port CoS value is 0.
dscpClassifies an ingress packet by using the packet DSCP
value. For a non-IP packet, the packet CoS value is used if the
packet is tagged; for an untagged packet, the default port CoS is
used. Internally, the switch maps the CoS value to a DSCP value
by using the CoS-to-DSCP map.
ip-precedenceClassifies 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 default
port CoS is used. Internally, the switch maps the CoS value to a
DSCP value by using the CoS-to-DSCP map.
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 a port to its untrusted state, use the no mls qos trust interface configuration command.
For information on how to change the default CoS value, see the Configuring the CoS Value for an
Interface section on page 36-37. For information on how to configure the CoS-to-DSCP map, see the
Configuring the CoS-to-DSCP Map section on page 36-60.
Configuring the CoS Value for an Interface
QoS assigns the CoS value specified with the mls qos cos interface configuration command to untagged
frames received on trusted and untrusted ports.
Beginning in privileged EXEC mode, follow these steps to define the default CoS value of a port or to
assign the default CoS to all incoming packets on the port:
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-37
Chapter 36
Configuring QoS
Configuring Standard QoS
Step 3
Command
Purpose
mls qos cos {default-cos | override}
Configure the default CoS value for the port.
For default-cos, specify a default CoS value to be assigned to a port. If
the packet is untagged, the default 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 incoming packet and to apply the default port CoS value to
the port on all incoming packets. By default, CoS override is disabled.
Use the override keyword when all incoming 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 incoming CoS values are assigned the default CoS value configured
with this command. If an incoming packet is tagged, the CoS value of
the packet is modified with the default CoS of the port at the ingress
port.
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 {default-cos | override} interface configuration
command.
Configuring a Trusted Boundary to Ensure Port Security
In a typical network, you connect a Cisco IP Phone to a switch port, as shown in Figure 36-12 on
page 36-36, and cascade devices that generate data packets from the back of the telephone. The Cisco IP
Phone guarantees the voice quality through a shared data link by marking the CoS level of the voice
packets as high priority (CoS = 5) and by marking the data packets as low priority (CoS = 0). Traffic sent
from the telephone to the switch is typically marked with a tag that uses the 802.1Q header. The header
contains the VLAN information and the class of service (CoS) 3-bit field, which is the priority of the
packet.
For most Cisco IP Phone configurations, the traffic sent from the telephone to the switch should be
trusted to ensure that voice traffic is properly prioritized over other types of traffic in the network. By
using the mls qos trust cos interface configuration command, you configure the switch port to which
the telephone is connected to trust the CoS labels of all traffic received on that port. Use the mls qos
trust dscp interface configuration command to configure a routed port to which the telephone is
connected to trust the DSCP labels of all traffic received on that port.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-38
OL-12189-01
Chapter 36
Configuring QoS
Configuring Standard QoS
With the trusted setting, you also can use the trusted boundary feature to prevent misuse of a
high-priority queue if a user bypasses the telephone and connects the PC directly to the switch. Without
trusted boundary, the CoS labels generated by the PC are trusted by the switch (because of the trusted
CoS setting). By contrast, trusted boundary uses CDP to detect the presence of a Cisco IP Phone (such
as the Cisco IP Phone 7910, 7935, 7940, and 7960) on a switch port. If the telephone is not detected, the
trusted boundary feature disables the trusted setting on the switch port and prevents misuse of a
high-priority queue. Note that the trusted boundary feature is not effective if the PC and Cisco IP Phone
are connected to a hub that is connected to the switch.
In some situations, you can prevent a PC connected to the Cisco IP Phone from taking advantage of a
high-priority data queue. You can use the switchport priority extend cos interface configuration
command to configure the telephone through the switch CLI to override the priority of the traffic
received from the PC.
Beginning in privileged EXEC mode, follow these steps to enable trusted boundary on a port:
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 Cisco 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 switch port to trust the CoS value in traffic received from the
Cisco IP Phone.
or
Configure the routed port to trust the DSCP value in traffic received from
the Cisco IP Phone.
mls qos trust dscp
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.
Enabling DSCP Transparency Mode
The switch supports the DSCP transparency feature. It affects only the DSCP field of a packet at egress.
By default, DSCP transparency is disabled. The switch modifies the DSCP field in an incoming packet,
and the DSCP field in the outgoing packet is based on the quality of service (QoS) configuration,
including the port trust setting, policing and marking, and the DSCP-to-DSCP mutation map.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-39
Chapter 36
Configuring QoS
Configuring Standard QoS
If DSCP transparency is enabled by using the no mls qos rewrite ip dscp command, the switch does not
modify the DSCP field in the incoming packet, and the DSCP field in the outgoing packet is the same as
that in the incoming packet.
Note
Enabling DSCP transparency does not affect the port trust settings on IEEE 802.1Q tunneling ports.
Regardless of the DSCP transparency configuration, the switch modifies the internal DSCP value of the
packet, which the switch uses to generate a class of service (CoS) value that represents the priority of
the traffic. The switch also uses the internal DSCP value to select an egress queue and threshold.
Beginning in privileged EXEC mode, follow these steps to enable DSCP transparency on a switch:
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 36-13. 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-40
OL-12189-01
Chapter 36
Configuring QoS
Configuring Standard QoS
Figure 36-13
DSCP-Trusted State on a Port Bordering Another QoS Domain
QoS Domain 1
QoS Domain 2
Set interface to the DSCP-trusted state.
Configure the DSCP-to-DSCP-mutation map.
101235
IP traffic
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
dscp-mutation-name in-dscp to out-dscp
Modify the DSCP-to-DSCP-mutation map.
The default DSCP-to-DSCP-mutation map is a null map, which maps
an incoming 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
dscp-mutation-name
Apply the map to the specified ingress DSCP-trusted port.
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.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-41
Chapter 36
Configuring QoS
Configuring Standard QoS
To return a port to its non-trusted 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/0/2-mutation) so that incoming DSCP values 10 to 13 are
mapped to DSCP 30:
Switch(config)# mls qos map dscp-mutation gigabitethernet1/0/2-mutation 10 11 12 13 to 30
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# mls qos trust dscp
Switch(config-if)# mls qos dscp-mutation gigabitethernet1/0/2-mutation
Switch(config-if)# end
Configuring a QoS Policy
Configuring a QoS policy typically requires classifying traffic into classes, configuring policies applied
to those traffic classes, and attaching policies to ports.
For background information, see the Classification section on page 36-5 and the Policing and
Marking section on page 36-8. For configuration guidelines, see the Standard QoS Configuration
Guidelines section on page 36-32.
These sections describe how to classify, police, and mark traffic. Depending on your network
configuration, you must perform one or more of these tasks:
Classifying Traffic by Using ACLs, page 36-43
Classifying Traffic by Using Class Maps, page 36-46
Classifying, Policing, and Marking Traffic on Physical Ports by Using Policy Maps, page 36-48
Classifying, Policing, and Marking Traffic on SVIs by Using Hierarchical Policy Maps, page 36-52
Classifying, Policing, and Marking Traffic by Using Aggregate Policers, page 36-58
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-42
OL-12189-01
Chapter 36
Configuring QoS
Configuring Standard QoS
Classifying Traffic by Using ACLs
You can classify IP traffic by using IP standard or IP extended ACLs; you can classify non-IP traffic by
using Layer 2 MAC ACLs.
Beginning in privileged EXEC mode, follow these steps to create an IP standard ACL for IP traffic:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
access-list access-list-number {deny |
permit} source [source-wildcard]
Create an IP standard ACL, repeating the command as many times as
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
Switch(config)# access-list 1 permit
Switch(config)# access-list 1 permit
! (Note: all other access implicitly
192.5.255.0 0.0.0.255
128.88.0.0 0.0.255.255
36.0.0.0 0.0.0.255
denied)
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-43
Chapter 36
Configuring QoS
Configuring Standard QoS
Beginning in privileged EXEC mode, follow these steps to create an IP extended ACL for IP traffic:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
access-list access-list-number {deny |
permit} protocol source source-wildcard
destination destination-wildcard
Create an IP extended ACL, repeating the command as many times as
necessary.
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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-44
OL-12189-01
Chapter 36
Configuring QoS
Configuring Standard QoS
Beginning in privileged EXEC mode, follow these steps to create a Layer 2 MAC ACL for 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.
After entering this command, the mode changes to extended MAC
ACL configuration.
Step 3
{permit | deny} {host src-MAC-addr mask | Specify the type of traffic to permit or deny if the conditions are
any | host dst-MAC-addr | dst-MAC-addr
matched, entering the command as many times as necessary.
mask} [type mask]
For src-MAC-addr, enter the MAC address of the host from
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.
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 dont
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 [access-list-number |
access-list-name]
Verify your entries.
Step 6
copy running-config startup-config
(Optional) Save your entries in the configuration file.
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)
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-45
Chapter 36
Configuring QoS
Configuring Standard QoS
Classifying Traffic by Using Class Maps
You use the class-map global configuration command to name and to isolate a specific traffic flow (or
class) from all other traffic. The class map defines the criteria to use to match against a specific traffic
flow to further classify it. Match statements can include criteria such as an ACL, IP precedence values,
or DSCP values. The match criterion is defined with one match statement entered within the class-map
configuration mode.
Note
You can also create class-maps during policy map creation by using the class policy-map configuration
command. For more information, see the Classifying, Policing, and Marking Traffic on Physical Ports
by Using Policy Maps section on page 36-48 and the Classifying, Policing, and Marking Traffic on
SVIs by Using Hierarchical Policy Maps section on page 36-52.
Beginning in privileged EXEC mode, follow these steps to create a class map and to define the match
criterion to classify traffic:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
access-list access-list-number {deny |
permit} source [source-wildcard]
Create an IP standard or extended ACL for IP traffic or a Layer 2 MAC
ACL for non-IP traffic, repeating the command as many times as
necessary.
or
For more information, see the Classifying Traffic by Using ACLs
access-list access-list-number {deny |
section on page 36-43.
permit} protocol source [source-wildcard]
destination [destination-wildcard]
Note
When creating an access list, remember that, by default, the
end of the access list contains an implicit deny statement for
or
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]
class-map-name
Create a class map, and enter class-map configuration 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. See
the Creating Named Standard and Extended ACLs section on
page 34-15 for limitations when using the match-all and the
match-any keywords.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-46
OL-12189-01
Chapter 36
Configuring QoS
Configuring Standard QoS
Command
Step 4
Purpose
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 created in Step 2.
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 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 policy map, use the no policy-map policy-map-name global configuration
command. 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)# end
Switch#
This example shows how to create a class map called class2, which matches incoming 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)# end
Switch#
This example shows how to create a class map called class3, which matches incoming 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)# end
Switch#
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-47
Chapter 36
Configuring QoS
Configuring Standard QoS
Classifying, Policing, and Marking Traffic on Physical Ports by Using Policy Maps
You can configure a nonhierarchical policy map on a physical port that specifies which traffic class to
act on. Actions can include trusting the CoS, DSCP, or IP precedence values in the traffic class; setting
a specific DSCP or IP precedence value in the traffic class; and specifying 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 separate policy-map class can exist for each type of traffic received through a port.
Follow these guidelines when configuring policy maps on physical ports:
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 ip 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.
If you enter or have used the set ip dscp command, the switch changes this command to set dscp in
its configuration.
You can use the set ip precedence or the set precedence policy-map class configuration command
to change the packet IP precedence value. This setting appears as set ip precedence in the switch
configuration.
You can configure a separate second-level policy map for each class defined for the port. The
second-level policy map specifies the police action to take for each traffic class. For information on
configuring a hierarchical policy map, see Classifying, Policing, and Marking Traffic on SVIs by
Using Hierarchical Policy Maps, page 36-52.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-48
OL-12189-01
Chapter 36
Configuring QoS
Configuring Standard QoS
Beginning in privileged EXEC mode, follow these steps to create a nonhierarchical policy map:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
class-map [match-all | match-any]
class-map-name
Create a class map, and enter class-map configuration 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
Step 3
policy-map policy-map-name
Because only one match command per class map is supported,
the match-all and match-any keywords function the same. See
the Creating Named Standard and Extended ACLs section on
page 34-15 for limitations when using the match-all and the
match-any keywords.
Create a policy map by entering the policy map name, and enter
policy-map configuration mode.
By default, no policy maps are defined.
The default 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 4
class class-map-name
Define 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-49
Chapter 36
Configuring QoS
Configuring Standard QoS
Step 5
Command
Purpose
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,
go to Step 6.
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:
cosQoS derives the DSCP value by using the received or default
port CoS value and the CoS-to-DSCP map.
dscpQoS 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 default port CoS value. In either case, the DSCP value is
derived from the CoS-to-DSCP map.
ip-precedenceQoS 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 default 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 36-60.
Step 6
Step 7
set {dscp new-dscp | ip precedence
new-precedence}
police rate-bps burst-byte [exceed-action
{drop | policed-dscp-transmit}]
Classify IP traffic by setting a new value in the packet.
For dscp new-dscp, enter a new DSCP value to be assigned to the
classified traffic. The range is 0 to 63.
For ip precedence new-precedence, enter a new IP-precedence
value to be assigned to the classified traffic. The range is 0 to 7.
Define a policer for the classified traffic.
By default, no policer is defined. For information on the number of
policers supported, see the Standard QoS Configuration Guidelines
section on page 36-32.
For rate-bps, specify average traffic rate in bits per second (b/s).
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 to send the
packet. For more information, see the Configuring the
Policed-DSCP Map section on page 36-62.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-50
OL-12189-01
Chapter 36
Configuring QoS
Configuring Standard QoS
Command
Purpose
Step 8
exit
Return to policy map configuration mode.
Step 9
exit
Return to global configuration mode.
Step 10
interface interface-id
Specify the port to attach to the policy map, and enter interface
configuration mode.
Valid interfaces include physical ports.
Step 11
service-policy input policy-map-name
Specify the policy-map name, and apply it to an ingress port.
Only one policy map per ingress port is supported.
Step 12
end
Step 13
show policy-map [policy-map-name [class Verify your entries.
class-map-name]]
Step 14
copy running-config startup-config
Return to privileged EXEC mode.
(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 untrusted state, 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, use the no police
rate-bps burst-byte [exceed-action {drop | policed-dscp-transmit}] policy-map configuration
command. To remove the policy map and port association, use the no service-policy input
policy-map-name interface configuration command.
This example shows how to create a policy map and attach it to an ingress 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 incoming packet is trusted. If the matched traffic exceeds an average traffic rate of 48000
b/s 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 1000000 8000 exceed-action policed-dscp-transmit
Switch(config-pmap-c)# exit
Switch(config-pmap)# exit
Switch(config)# interface gigabitethernet2/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 an
ingress 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
Switch(config-ext-mac)# permit 0001.0000.0002 0.0.0
Switch(config-ext-mac)# exit
Switch(config)# mac access-list extended maclist2
Switch(config-ext-mac)# permit 0001.0000.0003 0.0.0
Switch(config-ext-mac)# permit 0001.0000.0004 0.0.0
0002.0000.0001 0.0.0
0002.0000.0002 0.0.0 xns-idp
0002.0000.0003 0.0.0
0002.0000.0004 0.0.0 aarp
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-51
Chapter 36
Configuring QoS
Configuring Standard QoS
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
Classifying, Policing, and Marking Traffic on SVIs by Using Hierarchical Policy Maps
You can configure hierarchical policy maps on SVIs, but not on other types of interfaces. Hierarchical
policing combines the VLAN- and interface-level policy maps to create a single policy map.
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 policy maps:
Before configuring a hierarchical 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.
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 ip 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.
If you enter or have used the set ip dscp command, the switch changes this command to set dscp in
its configuration. If you enter the set ip dscp command, this setting appears as set dscp in the switch
configuration.
You can use the set ip precedence or the set precedence policy-map class configuration command
to change the packet IP precedence value. This setting appears as set ip precedence in the switch
configuration.
If VLAN-based QoS is enabled, the hierarchical policy map supersedes the previously configured
port-based policy map.
The hierarchical policy map is attached to the SVI and affects all traffic belonging to the VLAN.
The actions specified in the VLAN-level policy map affect the traffic belonging to the SVI. The
police action on the port-level policy map affects the ingress traffic on the affected physical
interfaces.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-52
OL-12189-01
Chapter 36
Configuring QoS
Configuring Standard QoS
When configuring a hierarchical 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.
Aggregate policers are not supported in hierarchical policy maps.
When VLAN-based QoS is enabled, the switch supports VLAN-based features, such as the VLAN
map.
You can configure a hierarchical policy map only on the primary VLAN of a private VLAN.
When you enable VLAN-based QoS and configure a hierarchical policy map in a switch stack, these
automatic actions occur when the stack configuration changes:
When a new stack master is selected, the stack master re-enables and reconfigures these features
on all applicable interfaces on the stack master.
When a stack member is added, the stack master re-enables and reconfigures these features on
all applicable ports on the stack member.
When you merge switch stacks, the new stack master re-enables and reconfigures these features
on the switches in the new stack.
When the switch stack divides into two or more switch stacks, the stack master in each switch
stack re-enables and reconfigures these features on all applicable interfaces on the stack
members, including the stack master.
Beginning in privileged EXEC mode, follow these steps to create a hierarchical policy map:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
class-map [match-all | match-any]
class-map-name
Create a VLAN-level class map, and enter class-map configuration
mode. For information about creating a class map, see the Classifying
Traffic by Using Class Maps section on page 36-46.
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. See
the Creating Named Standard and Extended ACLs section on
page 34-15 for limitations when using the match-all and the
match-any keywords.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-53
Chapter 36
Configuring QoS
Configuring Standard QoS
Command
Step 3
Purpose
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.
Step 6
class-map [match-all | match-any]
class-map-name
Create an interface-level class map, and enter class-map configuration
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
Step 7
match input-interface interface-id-list
Because only one match command per class map is supported,
the match-all and match-any keywords function the same. See
the Creating Named Standard and Extended ACLs section on
page 34-15 for limitations when using the match-all and the
match-any keywords.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-54
OL-12189-01
Chapter 36
Configuring QoS
Configuring Standard QoS
Step 10
Command
Purpose
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-map class-map-name
Define an interface-level traffic classification, and enter policy-map
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.
Step 12
police rate-bps burst-byte [exceed-action
{drop | policed-dscp-transmit}]
Define an individual policer for the classified traffic.
By default, no policer is defined. For information on the number of
policers supported, see the Standard QoS Configuration Guidelines
section on page 36-32.
For rate-bps, specify average traffic rate in bits per second (b/s).
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 to send the
packet. For more information, see the Configuring the
Policed-DSCP Map section on page 36-62.
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 default 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-55
Chapter 36
Configuring QoS
Configuring Standard QoS
Step 17
Command
Purpose
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.
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:
cosQoS derives the DSCP value by using the received or default
port CoS value and the CoS-to-DSCP map.
dscpQoS 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 default port CoS value. In either case, the DSCP value is
derived from the CoS-to-DSCP map.
ip-precedenceQoS 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 default 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 36-60.
Step 18
Step 19
set {dscp new-dscp | ip precedence
new-precedence}
service-policy policy-map-name
Classify IP traffic by setting a new value in the packet.
For dscp new-dscp, enter a new DSCP value to be assigned to the
classified traffic. The range is 0 to 63.
For ip precedence new-precedence, enter a new IP-precedence
value to be assigned to the classified traffic. The range is 0 to 7.
Specify the interface-level policy-map name (from Step 10) and
associate it with the VLAN-level policy map.
If the VLAN-level policy map specifies more than one class, each class
can have a different service-policy policy-map-name command.
Step 20
exit
Return to policy-map configuration mode.
Step 21
exit
Return to global configuration mode.
Step 22
interface interface-id
Specify the SVI to which to attach the hierarchical policy map, and
enter interface configuration mode.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-56
OL-12189-01
Chapter 36
Configuring QoS
Configuring Standard QoS
Step 23
Command
Purpose
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 hierarchical 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
Step 25
show policy-map [policy-map-name [class Verify your entries.
class-map-name]]
Return to privileged EXEC mode.
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 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
hierarchical 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 policy map:
Switch> enable
Switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# access-list 101 permit ip any any
Switch(config)# class-map cm-1
Switch(config-cmap)# match access 101
Switch(config-cmap)# exit
Switch(config)# exit
Switch#
Switch#
This example shows how to attach the new map to an SVI:
Switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# class-map cm-interface-1
Switch(config-cmap)# match input gigabitethernet3/0/1 - gigabitethernet3/0/2
Switch(config-cmap)# exit
Switch(config)# policy-map port-plcmap
Switch(config-pmap)# class-map cm-interface-1
Switch(config-pmap-c)# police 900000 9000 exc policed-dscp-transmit
Switch(config-pmap-c)# exit
Switch(config-pmap)# exit
Switch(config)# policy-map vlan-plcmap
Switch(config-pmap)# class-map cm-1
Switch(config-pmap-c)# set dscp 7
Switch(config-pmap-c)# service-policy port-plcmap-1
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-57
Chapter 36
Configuring QoS
Configuring Standard QoS
Switch(config-pmap-c)# exit
Switch(config-pmap)# class-map cm-2
Switch(config-pmap-c)# match ip dscp 2
Switch(config-pmap-c)# service-policy port-plcmap-1
Switch(config-pmap)# exit
Switch(config-pmap)# class-map cm-3
Switch(config-pmap-c)# match ip dscp 3
Switch(config-pmap-c)# service-policy port-plcmap-2
Switch(config-pmap)# exit
Switch(config-pmap)# class-map cm-4
Switch(config-pmap-c)# trust dscp
Switch(config-pmap)# exit
Switch(config)# interface vlan 10
Switch(config-if)#
Switch(config-if)# service input vlan-plcmap
Switch(config-if)# exit
Switch(config)# exit
Switch#
Classifying, Policing, and Marking Traffic by Using Aggregate Policers
By using an aggregate policer, you can create a policer that is shared by multiple traffic classes within
the same policy map. However, you cannot use the aggregate policer across different policy maps or
ports.
You can configure aggregate policers only in nonhierarchical policy maps on physical ports.
Beginning in privileged EXEC mode, follow these steps to create an aggregate policer:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
mls qos aggregate-policer
aggregate-policer-name rate-bps burst-byte
exceed-action {drop |
policed-dscp-transmit}
Define the policer parameters that can be applied to multiple traffic
classes within the same policy map.
Step 3
class-map [match-all | match-any]
class-map-name
By default, no aggregate policer is defined. For information on the
number of policers supported, see the Standard QoS Configuration
Guidelines section on page 36-32.
For aggregate-policer-name, specify the name of the aggregate
policer.
For rate-bps, specify average traffic rate in bits per second
(b/s). 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 (by using the policed-DSCP map) and to send
the packet. For more information, see the Configuring the
Policed-DSCP Map section on page 36-62.
Create a class map to classify traffic as necessary. For more
information, see the Classifying Traffic by Using Class Maps
section on page 36-46 and the Creating Named Standard and
Extended ACLs section on page 34-15.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-58
OL-12189-01
Chapter 36
Configuring QoS
Configuring Standard QoS
Step 4
Command
Purpose
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
Traffic on Physical Ports by Using Policy Maps section on
page 36-48.
Step 5
class class-map-name
Define a traffic classification, and enter policy-map class
configuration mode.
For more information, see the Classifying, Policing, and Marking
Traffic on Physical Ports by Using Policy Maps section on
page 36-48.
Step 6
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 7
exit
Return to global configuration mode.
Step 8
interface interface-id
Specify the port to attach to the policy map, and enter interface
configuration mode.
Valid interfaces include physical ports.
Step 9
service-policy input policy-map-name
Specify the policy-map name, and apply it to an ingress port.
Only one policy map per ingress port is supported.
Step 10
end
Return to privileged EXEC mode.
Step 11
show mls qos aggregate-policer
[aggregate-policer-name]
Verify your entries.
Step 12
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 configuration mode. 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 incoming 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 b/s and a normal burst
size of 8000 bytes, its DSCP is marked down (based on the policed-DSCP map) and sent. The policy
map is attached to an ingress 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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-59
Chapter 36
Configuring QoS
Configuring Standard QoS
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)# exit
Switch(config)# interface gigabitethernet2/0/1
Switch(config-if)# service-policy input aggflow1
Switch(config-if)# exit
Configuring DSCP Maps
These sections contain this configuration information:
Configuring the CoS-to-DSCP Map, page 36-60 (optional)
Configuring the IP-Precedence-to-DSCP Map, page 36-61 (optional)
Configuring the Policed-DSCP Map, page 36-62 (optional, unless the null settings in the map are
not appropriate)
Configuring the DSCP-to-CoS Map, page 36-63 (optional)
Configuring the DSCP-to-DSCP-Mutation Map, page 36-64 (optional, unless the null settings in the
map are not appropriate)
All the maps, except the DSCP-to-DSCP-mutation map, are globally defined and are applied to all ports.
Configuring the CoS-to-DSCP Map
You use the CoS-to-DSCP map to map CoS values in incoming packets to a DSCP value that QoS uses
internally to represent the priority of the traffic.
Table 36-12 shows the default CoS-to-DSCP map.
Table 36-12
Default CoS-to-DSCP Map
CoS Value
DSCP Value
16
24
32
40
48
56
If these values are not appropriate for your network, you need to modify them.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-60
OL-12189-01
Chapter 36
Configuring QoS
Configuring Standard QoS
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
Configuring the IP-Precedence-to-DSCP Map
You use the IP-precedence-to-DSCP map to map IP precedence values in incoming packets to a DSCP
value that QoS uses internally to represent the priority of the traffic.
Table 36-13 shows the default IP-precedence-to-DSCP map:
Table 36-13
Default IP-Precedence-to-DSCP Map
IP Precedence Value
DSCP Value
16
24
32
40
48
56
If these values are not appropriate for your network, you need to modify them.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-61
Chapter 36
Configuring QoS
Configuring Standard QoS
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
dscp1...dscp8
Modify the IP-precedence-to-DSCP map.
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
Configuring the Policed-DSCP Map
You use the policed-DSCP map to mark down a DSCP value to a new value as the result of a policing
and marking action.
The default policed-DSCP map is a null map, which maps an incoming DSCP value to the same DSCP
value.
Beginning in privileged EXEC mode, follow these steps to modify the policed-DSCP map. This
procedure is optional.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
mls qos map policed-dscp dscp-list to
mark-down-dscp
Modify the policed-DSCP map.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-62
OL-12189-01
Chapter 36
Configuring QoS
Configuring Standard QoS
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.
Configuring the DSCP-to-CoS Map
You use the DSCP-to-CoS map to generate a CoS value, which is used to select one of the four egress
queues.
Table 36-14 shows the default DSCP-to-CoS map.
Table 36-14
Default DSCP-to-CoS Map
DSCP Value
CoS Value
07
815
1623
2431
3239
4047
4855
5663
If these values are not appropriate for your network, you need to modify them.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-63
Chapter 36
Configuring QoS
Configuring Standard QoS
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.
Configuring the DSCP-to-DSCP-Mutation Map
If two QoS domains have different DSCP definitions, use the DSCP-to-DSCP-mutation map to translate
one set of DSCP values to match the definition of another domain. You apply the
DSCP-to-DSCP-mutation map to the receiving port (ingress mutation) at the boundary of a QoS
administrative domain.
With ingress mutation, the new DSCP value overwrites the one in the packet, and QoS treats the packet
with this new value. The switch sends the packet out the port with the new DSCP value.
You can configure multiple DSCP-to-DSCP-mutation maps on an ingress port. The default
DSCP-to-DSCP-mutation map is a null map, which maps an incoming DSCP value to the same DSCP
value.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-64
OL-12189-01
Chapter 36
Configuring QoS
Configuring Standard QoS
Beginning in privileged EXEC mode, follow these steps to modify the DSCP-to-DSCP-mutation map.
This procedure is optional.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
mls qos map dscp-mutation
dscp-mutation-name in-dscp to out-dscp
Modify the DSCP-to-DSCP-mutation map.
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.
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
dscp-mutation-name
Apply the map to the specified ingress DSCP-trusted port.
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.
For dscp-mutation-name, enter the mutation map name specified in
Step 2.
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
Switch(config)# mls qos map dscp-mutation mutation1
Switch(config)# mls qos map dscp-mutation mutation1
Switch(config)# mls qos map dscp-mutation mutation1
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
1 2 3 4 5 6 7 to 0
8 9 10 11 12 13 to 10
20 21 22 to 20
30 31 32 33 34 to 30
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-65
Chapter 36
Configuring QoS
Configuring Standard QoS
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.
Configuring Ingress Queue Characteristics
Depending on the complexity of your network and your QoS solution, you might need to perform all of
the tasks in the next sections. You will need to make decisions about these characteristics:
Which packets are assigned (by DSCP or CoS value) to each queue?
What drop percentage thresholds apply to each queue, and which CoS or DSCP values map to each
threshold?
How much of the available buffer space is allocated between the queues?
How much of the available bandwidth is allocated between the queues?
Is there traffic (such as voice) that should be given high priority?
These sections contain this configuration information:
Mapping DSCP or CoS Values to an Ingress Queue and Setting WTD Thresholds, page 36-67
(optional)
Allocating Buffer Space Between the Ingress Queues, page 36-68 (optional)
Allocating Bandwidth Between the Ingress Queues, page 36-68 (optional)
Configuring the Ingress Priority Queue, page 36-69 (optional)
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-66
OL-12189-01
Chapter 36
Configuring QoS
Configuring Standard QoS
Mapping DSCP or CoS Values to an Ingress Queue and Setting WTD Thresholds
You can prioritize traffic by placing packets with particular DSCPs or CoSs into certain queues and
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
queue queue-id threshold threshold-id
dscp1...dscp8
Map DSCP or CoS values to an ingress queue and to a threshold ID.
or
By default, CoS values 04, 6, and 7 are mapped to queue 1 and threshold
1. CoS value 5 is mapped to queue 2 and threshold 1.
mls qos srr-queue input cos-map
queue queue-id threshold threshold-id
cos1...cos8
Step 3
mls qos srr-queue input threshold
queue-id threshold-percentage1
threshold-percentage2
By default, DSCP values 039 and 4863 are mapped to queue 1 and
threshold 1. DSCP values 4047 are mapped to queue 2 and threshold 1.
For queue-id, the range is 1 to 2.
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.
Assign the two WTD threshold percentages for (threshold 1 and 2) to an
ingress queue. The default, both thresholds are set to 100 percent.
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.
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 default 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-67
Chapter 36
Configuring QoS
Configuring Standard QoS
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.
Allocating Buffer Space Between the Ingress Queues
You define the ratio (allocate the amount of space) with which to divide the ingress buffers between the
two queues. The buffer and the bandwidth allocation control how much data can be buffered before
packets are dropped.
Beginning in privileged EXEC mode, follow these steps to allocate the buffers between the ingress
queues. This procedure is optional.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
mls qos srr-queue input buffers
percentage1 percentage2
Allocate the buffers between the ingress queues
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
incoming bursty traffic.
Step 3
end
Return to privileged EXEC mode.
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
Allocating Bandwidth Between the Ingress Queues
You need to specify how much of the available bandwidth is allocated between the ingress queues. The
ratio of the weights is the ratio of the frequency in which the SRR scheduler sends packets from each
queue. The bandwidth and the buffer allocation control how much data can be buffered before packets
are dropped. On ingress queues, SRR operates only in shared mode.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-68
OL-12189-01
Chapter 36
Configuring QoS
Configuring Standard QoS
Beginning in privileged EXEC mode, follow these steps to allocate bandwidth between the ingress
queues. This procedure is optional.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
mls qos srr-queue input bandwidth
weight1 weight2
Assign shared round robin weights to the ingress queues.
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 36-69.
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
Configuring the Ingress Priority Queue
You should use the priority queue only for traffic that needs to be expedited (for example, voice traffic,
which needs minimum delay and jitter).
The priority queue is guaranteed part of the bandwidth to reduce the delay and jitter under heavy network
traffic on an oversubscribed ring (when there is more traffic than the backplane can carry, and the queues
are full and dropping frames).
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-69
Chapter 36
Configuring QoS
Configuring Standard QoS
Beginning in privileged EXEC mode, follow these steps to configure the priority queue. This procedure
is optional.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
mls qos srr-queue input
priority-queue queue-id bandwidth
weight
Assign a queue as the priority queue and guarantee bandwidth on the stack
or internal ring if the ring is congested.
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 stack
or 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 the switch or stack 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
Configuring Egress Queue Characteristics
Depending on the complexity of your network and your QoS solution, you might need to perform all of
the tasks in the next sections. You will need to make decisions about these characteristics:
Which packets are mapped by DSCP or CoS value to each queue and threshold ID?
What drop percentage thresholds apply to the queue-set (four egress queues per port), and how much
reserved and maximum memory is needed for the traffic type?
How much of the fixed buffer space is allocated to the queue-set?
Does the bandwidth of the port need to be rate limited?
How often should the egress queues be serviced and which technique (shaped, shared, or both)
should be used?
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-70
OL-12189-01
Chapter 36
Configuring QoS
Configuring Standard QoS
These sections contain this configuration information:
Configuration Guidelines, page 36-71
Allocating Buffer Space to and Setting WTD Thresholds for an Egress Queue-Set, page 36-71
(optional)
Mapping DSCP or CoS Values to an Egress Queue and to a Threshold ID, page 36-73 (optional)
Configuring SRR Shaped Weights on Egress Queues, page 36-75 (optional)
Configuring SRR Shared Weights on Egress Queues, page 36-76 (optional)
Configuring the Egress Expedite Queue, page 36-76 (optional)
Limiting the Bandwidth on an Egress Interface, page 36-77 (optional)
Configuration Guidelines
Follow these guidelines when the expedite queue is enabled or the egress queues are serviced based on
their SRR weights:
If the egress expedite queue is enabled, it overrides the SRR shaped and shared weights for queue 1.
If the egress expedite 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 expedite queue is disabled and the SRR shaped weights are not configured, SRR
services this queue in shared mode.
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
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 queues allocated memory, 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 default settings are suitable for most situations. You should change them only when
you have a thorough understanding of the egress queues and if these settings do not meet your QoS
solution.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-71
Chapter 36
Configuring QoS
Configuring Standard QoS
Beginning in privileged EXEC mode, follow these steps to configure the memory allocation and to 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
buffers allocation1 ... allocation4
Allocate buffers to a queue-set.
By default, 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 ... allocation4, specify four percentages, one for each
queue in the queue-set. 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 large percentage of the buffer to the queue with the highest-priority
traffic.
Step 3
mls qos queue-set output qset-id
threshold queue-id drop-threshold1
drop-threshold2 reserved-threshold
maximum-threshold
Configure the WTD thresholds, guarantee the availability of buffers, and
configure the maximum memory allocation for the queue-set (four egress
queues per port).
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 queues allocated
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 queue in the full condition 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 of the outbound traffic, 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-72
OL-12189-01
Chapter 36
Configuring QoS
Configuring Standard QoS
Command
Purpose
Step 7
show mls qos interface [interface-id]
buffers
Verify your entries.
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 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 gigabitethernet1/0/1
Switch(config-if)# queue-set 2
Mapping DSCP or CoS Values to an Egress Queue and to a Threshold ID
You can prioritize traffic by placing packets with particular DSCPs or costs of service into certain queues
and adjusting the queue thresholds so that packets with lower priorities are dropped.
Note
The egress queue default settings are suitable for most situations. You should change them only when
you have a thorough understanding of the egress queues and if these settings do not meet your QoS
solution.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-73
Chapter 36
Configuring QoS
Configuring Standard QoS
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
queue queue-id threshold threshold-id
dscp1...dscp8
Map DSCP or CoS values to an egress queue and to a threshold ID.
or
mls qos srr-queue output cos-map
queue queue-id threshold threshold-id
cos1...cos8
By default, DSCP values 015 are mapped to queue 2 and threshold 1.
DSCP values 1631 are mapped to queue 3 and threshold 1. DSCP values
3239 and 4863 are mapped to queue 4 and threshold 1. DSCP values
4047 are mapped to queue 1 and threshold 1.
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 default 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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-74
OL-12189-01
Chapter 36
Configuring QoS
Configuring Standard QoS
Configuring SRR Shaped Weights on Egress Queues
You can specify how much of the available bandwidth is allocated to each queue. The ratio of the weights
is the ratio of frequency in which the SRR scheduler sends packets from each queue.
You can configure the egress queues for shaped or shared weights, or both. Use shaping to smooth bursty
traffic or to provide a smoother output over time. For information about shaped weights, see the SRR
Shaping and Sharing section on page 36-14. For information about shared weights, see the
Configuring SRR Shared Weights on Egress Queues section on page 36-76.
Beginning in privileged EXEC mode, follow these steps to assign the shaped weights and to enable
bandwidth shaping on the four egress queues mapped to a port. This procedure is optional.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
interface interface-id
Specify the port of the outbound traffic, and enter interface configuration
mode.
Step 3
srr-queue bandwidth shape weight1
weight2 weight3 weight4
Assign SRR weights to the egress queues.
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
queueing
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 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 gigabitethernet2/0/1
Switch(config-if)# srr-queue bandwidth shape 8 0 0 0
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-75
Chapter 36
Configuring QoS
Configuring Standard QoS
Configuring SRR Shared Weights on Egress Queues
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 empties and does not
require 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.
Note
The egress queue default settings are suitable for most situations. You should change them only when
you have a thorough understanding of the egress queues and 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 the four egress queues mapped to a port. This procedure is optional.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
interface interface-id
Specify the port of the outbound traffic, and enter interface configuration
mode.
Step 3
srr-queue bandwidth share weight1
weight2 weight3 weight4
Assign SRR weights to the egress queues.
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
queueing
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 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 gigabitethernet2/0/1
Switch(config-if)# srr-queue bandwidth share 1 2 3 4
Configuring the Egress Expedite Queue
You can ensure that certain packets have priority over all others by queuing them in the egress expedite
queue. SRR services this queue until it is empty before servicing the other queues.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-76
OL-12189-01
Chapter 36
Configuring QoS
Configuring Standard QoS
Beginning in privileged EXEC mode, follow these steps to enable the egress expedite queue. This
procedure is optional.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
mls qos
Enable QoS on a switch.
Step 3
interface interface-id
Specify the egress port, and enter interface configuration mode.
Step 4
priority-queue out
Enable the egress expedite 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 ignored (not used in the ratio calculation).
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 egress expedite queue, use the no priority-queue out interface configuration command.
This example shows how to enable the egress expedite 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
Limiting the Bandwidth on an Egress Interface
You can limit the bandwidth on an egress port. For example, if a customer pays only for a small
percentage of a high-speed link, you can limit the bandwidth to that amount.
Note
The egress queue default settings are suitable for most situations. You should change them only when
you have a thorough understanding of the egress queues and if these settings do not meet your QoS
solution.
Beginning in privileged EXEC mode, follow these steps to limit the bandwidth on an egress port. This
procedure is optional.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
interface interface-id
Specify the 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.
By default, the port is not rate limited and is set to 100 percent.
Step 4
end
Return to privileged EXEC mode.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
36-77
Chapter 36
Configuring QoS
Displaying Standard QoS Information
Command
Purpose
Step 5
show mls qos interface [interface-id]
queueing
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 srr-queue bandwidth limit interface configuration command.
This example shows how to limit the bandwidth on a port to 80 percent:
Switch(config)# interface gigabitethernet2/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.
Displaying Standard QoS Information
To display standard QoS information, use one or more of the privileged EXEC commands in
Table 36-15:
Table 36-15
Commands for Displaying Standard QoS Information
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 mls qos aggregate-policer
[aggregate-policer-name]
Display the aggregate policer configuration.
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 configured policers, the queueing
strategy, and the ingress and egress statistics.
show mls qos maps [cos-dscp | cos-input-q |
cos-output-q | dscp-cos | dscp-input-q | dscp-mutation
dscp-mutation-name | dscp-output-q | ip-prec-dscp |
policed-dscp]
Display QoS mapping information.
show mls qos queue-set [qset-id]
Display QoS settings for the egress queues.
show mls qos vlan vlan-id
Display the policy maps attached to the specified SVI.
show policy-map [policy-map-name [class
class-map-name]]
Display QoS policy maps, which define classification criteria for
incoming traffic.
Note
show running-config | include rewrite
Do not use the show policy-map interface privileged
EXEC command to display classification information
for incoming traffic. The control-plane and interface
keywords are not supported, and the statistics shown in
the display should be ignored.
Display the DSCP transparency setting.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
36-78
OL-12189-01
CH A P T E R
37
Configuring EtherChannels and Link-State
Tracking
This chapter describes how to configure EtherChannels on Layer 2 and Layer 3 ports on the 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. Unless otherwise noted,
the term switch refers to a standalone switch and to a switch stack.
Note
For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
This chapter consists of these sections:
Understanding EtherChannels, page 37-1
Configuring EtherChannels, page 37-10
Displaying EtherChannel, PAgP, and LACP Status, page 37-22
Understanding Link-State Tracking, page 37-22
Configuring Link-State Tracking, page 37-24
Understanding EtherChannels
These sections describe how EtherChannels work:
EtherChannel Overview, page 37-2
Port-Channel Interfaces, page 37-4
Port Aggregation Protocol, page 37-5
Link Aggregation Control Protocol, page 37-6
EtherChannel On Mode, page 37-7
Load-Balancing and Forwarding Methods, page 37-7
EtherChannel and Switch Stacks, page 37-9
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
37-1
Chapter 37
Configuring EtherChannels and Link-State Tracking
Understanding EtherChannels
EtherChannel Overview
An EtherChannel consists of individual Gigabit Ethernet links bundled into a single logical link as shown
in Figure 37-1.
Figure 37-1
Typical EtherChannel Configuration
Catalyst 6500
series switch
Gigabit EtherChannel
Blade
Server 1
Blade
Server 16
119704
Blade
Switch
The EtherChannel provides full-duplex bandwidth up to 8 Gb/s (Gigabit EtherChannel) or 80 Gb/s
(10-Gigabit EtherChannel) between your switch and another switch or host.
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. The number of EtherChannels is
limited to 48. For more information, see the EtherChannel Configuration Guidelines section on
page 37-11. 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 10, Configuring Interface Characteristics.
You can configure an EtherChannel in one of these modes: Port Aggregation Protocol (PAgP), Link
Aggregation Control Protocol (LACP), or On. 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. If the
remote port cannot negotiate an EtherChannel, 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.
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.
You can create an EtherChannel on a standalone switch, on a single switch in the stack, or on multiple
switches in the stack (known as cross-stack EtherChannel). See Figure 37-2 and Figure 37-3.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
37-2
OL-12189-01
Chapter 37
Configuring EtherChannels and Link-State Tracking
Understanding EtherChannels
Figure 37-2
Single-Switch EtherChannel
Blade switch stack
Switch 1
Channel
group 1
StackWise Plus
port
connections
Switch A
Channel
group 2
201782
Switch 2
Switch 3
Figure 37-3
Cross-Stack EtherChannel
Blade switch stack
Switch 1
StackWise Plus
port
connections
Switch A
Switch 2
Switch 3
201783
Channel
group 1
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
37-3
Chapter 37
Configuring EtherChannels and Link-State Tracking
Understanding EtherChannels
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 37-4.
Each EtherChannel has a port-channel logical interface numbered from 1 to 48. This port-channel
interface number corresponds to the one specified with the channel-group interface configuration
command.
Figure 37-4
Relationship of Physical Ports, Logical Port Channels, and Channel Groups
Logical
port-channel
Physical ports
101238
Channel-group
binding
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. 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
37-4
OL-12189-01
Chapter 37
Configuring EtherChannels and Link-State Tracking
Understanding EtherChannels
Port Aggregation Protocol
The Port Aggregation Protocol (PAgP) is a Cisco-proprietary protocol that can be run only on Cisco
switches and on those switches licensed by vendors to support PAgP. PAgP facilitates the automatic
creation of EtherChannels by exchanging PAgP packets between Ethernet ports. You can use PAgP only
in single-switch EtherChannel configurations; PAgP cannot be enabled on cross-stack EtherChannels.
For more information, see the EtherChannel Configuration Guidelines section on page 37-11.
By using PAgP, the switch or switch stack learns the identity of partners capable of supporting PAgP and
the capabilities of each port. It then dynamically groups similarly configured ports (on a single switch
in the stack) into a single logical link (channel or aggregate port). Similarly configured ports are grouped
based on hardware, administrative, and port parameter constraints. For example, PAgP groups the ports
with the same speed, duplex mode, native VLAN, VLAN range, and trunking status and type. After
grouping the links into an EtherChannel, PAgP adds the group to the spanning tree as a single switch
port.
PAgP Modes
Table 37-1 shows the user-configurable EtherChannel PAgP modes for the channel-group interface
configuration command.
Table 37-1
EtherChannel PAgP Modes
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. This mode is not supported when the EtherChannel
members are from different switches in the switch stack (cross-stack EtherChannel).
desirable Places a port into an active negotiating state, in which the port starts negotiations with other
ports by sending PAgP packets. This mode is not supported when the EtherChannel
members are from different switches in the switch stack (cross-stack EtherChannel).
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
37-5
Chapter 37
Configuring EtherChannels and Link-State Tracking
Understanding EtherChannels
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.
PAgP Interaction with Other Features
The Dynamic Trunking Protocol (DTP) and the Cisco Discovery Protocol (CDP) send and receive
packets over the physical ports in the EtherChannel. Trunk ports send and receive PAgP protocol data
units (PDUs) on the lowest numbered VLAN.
In Layer 2 EtherChannels, the first port in the channel that comes up provides its MAC address to the
EtherChannel. If this port is removed from the bundle, one of the remaining ports in the bundle provides
its MAC address to the EtherChannel. For Layer 3 EtherChannels, the MAC address is allocated by the
stack master as soon as the interface is created (through the interface port-channel global configuration
command).
PAgP sends and receives PAgP PDUs only from ports that are up and have PAgP enabled for the auto or
desirable mode.
Link Aggregation Control Protocol
The LACP is defined in IEEE 802.3ad and enables Cisco switches to manage Ethernet channels between
switches that conform to the IEEE 802.3ad protocol. LACP facilitates the automatic creation of
EtherChannels by exchanging LACP packets between Ethernet ports.
By using LACP, the switch or switch stack learns the identity of partners capable of supporting LACP
and the capabilities of each port. It then dynamically groups similarly configured ports into a single
logical link (channel or aggregate port). Similarly configured ports are grouped based on hardware,
administrative, and port parameter constraints. For example, LACP groups the ports with the same speed,
duplex mode, native VLAN, VLAN range, and trunking status and type. After grouping the links into an
EtherChannel, LACP adds the group to the spanning tree as a single switch port.
LACP Modes
Table 37-2 shows the user-configurable EtherChannel LACP modes for the channel-group interface
configuration command.
Table 37-2
EtherChannel LACP Modes
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 an
EtherChannel based on criteria such as port speed and, for Layer 2 EtherChannels, trunking state and
VLAN numbers.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
37-6
OL-12189-01
Chapter 37
Configuring EtherChannels and Link-State Tracking
Understanding EtherChannels
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.
LACP Interaction with Other Features
The DTP and the CDP send and receive packets over the physical ports in the EtherChannel. Trunk ports
send and receive LACP PDUs on the lowest numbered VLAN.
In Layer 2 EtherChannels, the first port in the channel that comes up provides its MAC address to the
EtherChannel. If this port is removed from the bundle, one of the remaining ports in the bundle provides
its MAC address to the EtherChannel. For Layer 3 EtherChannels, the MAC address is allocated by the
stack master as soon as the interface is created through the interface port-channel global configuration
command.
LACP sends and receives LACP PDUs only from ports that are up and have LACP enabled for the active
or passive mode.
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.
Load-Balancing and Forwarding Methods
EtherChannel balances the traffic load across the links in a channel by reducing part of the binary pattern
formed from the addresses in the frame to a numerical value that selects one of the links in the channel.
EtherChannel load-balancing can use MAC addresses or IP addresses, source or destination addresses,
or both source and destination addresses. The selected mode applies to all EtherChannels configured on
the switch. You configure the load-balancing and forwarding method by using the port-channel
load-balance global configuration command.
With source-MAC address forwarding, when packets are forwarded to an EtherChannel, they are
distributed across the ports in the channel based on the source-MAC address of the incoming packet.
Therefore, to provide load-balancing, packets from different hosts use different ports in the channel, but
packets from the same host use the same port in the channel.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
37-7
Chapter 37
Configuring EtherChannels and Link-State Tracking
Understanding EtherChannels
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 hosts 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 37-5, an EtherChannel of sixteen blade servers
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
37-8
OL-12189-01
Chapter 37
Configuring EtherChannels and Link-State Tracking
Understanding EtherChannels
Figure 37-5
Blade
Server 1
Load Distribution and Forwarding Methods
Blade
Server 16
Blade Switch with
source-based
forwarding enabled
EtherChannel
119705
Cisco router
with destination-based
forwarding enabled
Client
Client
EtherChannel and Switch Stacks
If a stack member that has ports participating in an EtherChannel fails or leaves the stack, the stack
master removes the failed stack member switch ports from the EtherChannel. The remaining ports of the
EtherChannel, if any, continue to provide connectivity.
When a switch is added to an existing stack, the new switch receives the running configuration from the
stack master and updates itself with the EtherChannel-related stack configuration. The stack member
also receives the operational information (the list of ports that are up and are members of a channel).
When two stacks merge that have EtherChannels configured between them, self-looped ports result.
Spanning tree detects this condition and acts accordingly. Any PAgP or LACP configuration on a
winning switch stack is not affected, but the PAgP or LACP configuration on the losing switch stack is
lost after the stack reboots.
With PAgP, if the stack master fails or leaves the stack, a new stack master is elected. A spanning-tree
reconvergence is not triggered unless there is a change in the EtherChannel bandwidth. The new stack
master synchronizes the configuration of the stack members to that of the stack master. The PAgP
configuration is not affected after a stack master change unless the EtherChannel has ports residing on
the old stack master.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
37-9
Chapter 37
Configuring EtherChannels and Link-State Tracking
Configuring EtherChannels
With LACP, the system-id uses the stack MAC address from the stack master, and if the stack master
changes, the LACP system-id can change. If the LACP system-id changes, the entire EtherChannel will
flap, and there will be an STP reconvergence. Use the stack-mac persistent timer command to control
whether or not the stack MAC address changes during a master failover.
For more information about switch stacks, see Chapter 5, Managing Switch Stacks.
Configuring EtherChannels
These sections contain this configuration information:
Default EtherChannel Configuration, page 37-10
EtherChannel Configuration Guidelines, page 37-11
Configuring Layer 2 EtherChannels, page 37-12 (required)
Configuring Layer 3 EtherChannels, page 37-14 (required)
Configuring EtherChannel Load-Balancing, page 37-17 (optional)
Configuring the PAgP Learn Method and Priority, page 37-18 (optional)
Configuring LACP Hot-Standby Ports, page 37-19 (optional)
Note
Make sure that the ports are correctly configured. For more information, see the EtherChannel
Configuration Guidelines section on page 37-11.
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.
Default EtherChannel Configuration
Table 37-3 shows the default EtherChannel configuration.
Table 37-3
Default EtherChannel Configuration
Feature
Default Setting
Channel groups
None assigned.
Port-channel logical interface
None defined.
PAgP mode
No default.
PAgP learn method
Aggregate-port learning on all ports.
PAgP priority
128 on all ports.
LACP mode
No default.
LACP learn method
Aggregate-port learning on all ports.
LACP port priority
32768 on all ports.
LACP system priority
32768.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
37-10
OL-12189-01
Chapter 37
Configuring EtherChannels and Link-State Tracking
Configuring EtherChannels
Table 37-3
Default EtherChannel Configuration (continued)
Feature
Default Setting
LACP system ID
LACP system priority and the switch MAC address.
Load-balancing
Load distribution on the switch is based on the
source-MAC address of the incoming packet.
EtherChannel Configuration Guidelines
If improperly configured, some EtherChannel ports are automatically disabled to avoid network loops
and other problems. Follow these guidelines to avoid configuration problems:
Do not try to configure more than 48 EtherChannels on the switch.
Configure a PAgP EtherChannel with up to eight Ethernet ports of the same type.
Configure a LACP EtherChannel with up to16 Ethernet ports of the same type. Up to eight ports can
be active, and up to eight ports can be in standby mode.
Configure all ports in an EtherChannel to operate at the same speeds and duplex modes.
Enable all ports in an EtherChannel. A port in an EtherChannel that is disabled by using the
shutdown interface configuration command is treated as a link failure, and its traffic is transferred
to one of the remaining ports in the EtherChannel.
When a group is first created, all ports follow the parameters set for the first port to be added to the
group. If you change the configuration of one of these parameters, you must also make the changes
to all ports in the group:
Allowed-VLAN list
Spanning-tree path cost for each VLAN
Spanning-tree port priority for each VLAN
Spanning-tree Port Fast setting
Do not configure a port to be a member of more than one EtherChannel group.
Do not configure an EtherChannel in both the PAgP and LACP modes. EtherChannel groups running
PAgP and LACP can coexist on the same switch or on different switches in the stack. Individual
EtherChannel groups can run either PAgP or LACP, but they cannot interoperate.
Do not configure a Switched Port Analyzer (SPAN) destination port as part of an EtherChannel.
Do not configure a secure port as part of an EtherChannel or the reverse.
Do not configure a private-VLAN port as part of an EtherChannel.
Do not configure a port that is an active or a not-yet-active member of an EtherChannel as an
IEEE 802.1x port. If you try to enable IEEE 802.1x on an EtherChannel port, an error message
appears, and IEEE 802.1x is not enabled.
If EtherChannels are configured on switch interfaces, remove the EtherChannel configuration from
the interfaces before globally enabling IEEE 802.1x on a switch by using the dot1x
system-auth-control global configuration command.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
37-11
Chapter 37
Configuring EtherChannels and Link-State Tracking
Configuring EtherChannels
For Layer 2 EtherChannels:
Assign all ports in the EtherChannel to the same VLAN, or configure them as trunks. Ports with
different native VLANs cannot form an EtherChannel.
If you configure an EtherChannel from trunk ports, verify that the trunking mode (ISL or
IEEE 802.1Q) is the same on all the trunks. Inconsistent trunk modes on EtherChannel ports can
have unexpected results.
An EtherChannel supports the same allowed range of VLANs on all the ports in a trunking
Layer 2 EtherChannel. If the allowed range of VLANs is not the same, the ports do not form an
EtherChannel even when PAgP is set to the auto or desirable mode.
Ports with different spanning-tree path costs can form an EtherChannel if they are otherwise
compatibly configured. Setting different spanning-tree path costs does not, by itself, make ports
incompatible for the formation of an EtherChannel.
For Layer 3 EtherChannels, assign the Layer 3 address to the port-channel logical interface, not to
the physical ports in the channel.
For cross-stack EtherChannel configurations, ensure that all ports targeted for the EtherChannel are
either configured for LACP or are manually configured to be in the channel group using the
channel-group channel-group-number mode on interface configuration command. The PAgP
protocol is not supported on cross- stack EtherChannels.
If cross-stack EtherChannel is configured and the switch stack partitions, loops and forwarding
misbehaviors can occur.
Configuring Layer 2 EtherChannels
You configure Layer 2 EtherChannels by assigning ports to a channel group with the channel-group
interface configuration command. This command automatically creates the port-channel logical
interface.
If you enabled PAgP on a port in the auto or desirable mode, you must reconfigure it for either the on
mode or the LACP mode before adding this port to a cross-stack EtherChannel. PAgP does not support
cross-stack EtherChannels.
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, 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
37-12
OL-12189-01
Chapter 37
Configuring EtherChannels and Link-State Tracking
Configuring EtherChannels
Step 3
Command
Purpose
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.
Step 4
channel-group channel-group-number mode
{auto [non-silent] | desirable [non-silent] | on} |
{active | passive}
Assign the port to a channel group, and specify the PAgP or the
LACP mode.
For channel-group-number, the range is 1 to 48.
For mode, select one of these keywords:
autoEnables 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. This keyword is not supported
when EtherChannel members are from different switches in
the switch stack.
desirableUnconditionally enables PAgP. It places the port
into an active negotiating state, in which the port starts
negotiations with other ports by sending PAgP packets. This
keyword is not supported when EtherChannel members are
from different switches in the switch stack.
onForces the port to channel without PAgP or LACP. In
the on mode, an 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.
activeEnables 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.
passiveEnables 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 37-5 and the
LACP Modes section on page 37-6.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
37-13
Chapter 37
Configuring EtherChannels and Link-State Tracking
Configuring EtherChannels
To remove a port from the EtherChannel group, use the no channel-group interface configuration
command.
This example shows how to configure an EtherChannel on a single switch in the stack. 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 gigabitethernet2/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 desirable non-silent
Switch(config-if-range)# end
This example shows how to configure an EtherChannel on a single switch in the stack. 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 gigabitethernet2/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
This example shows how to configure a cross-stack EtherChannel. It uses LACP passive mode and
assigns two ports on stack member 2 and one port on stack member 3 as static-access ports in VLAN 10
to channel 5:
Switch# configure terminal
Switch(config)# interface range gigabitethernet2/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 active
Switch(config-if-range)# exit
Switch(config)# interface gigabitethernet3/0/3
Switch(config-if)# switchport mode access
Switch(config-if)# switchport access vlan 10
Switch(config-if)# channel-group 5 mode active
Switch(config-if)# exit
Configuring Layer 3 EtherChannels
To configure Layer 3 EtherChannels, you create the port-channel logical interface and then put the
Ethernet ports into the port-channel as described in the next two sections.
Creating Port-Channel Logical Interfaces
When configuring Layer 3 EtherChannels, you should first manually create the port-channel logical
interface by using the interface port-channel global configuration command. Then you put the logical
interface into the channel group by using the channel-group interface configuration command.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
37-14
OL-12189-01
Chapter 37
Configuring EtherChannels and Link-State Tracking
Configuring EtherChannels
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
Specify the port-channel logical interface, and enter interface
configuration mode.
For port-channel-number, the range is 1 to 48.
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.
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 37-15.
To remove the port-channel, use the no interface port-channel port-channel-number global
configuration command.
This example shows how to create the logical port channel 5 and assign 172.10.20.10 as its IP address:
Switch# configure terminal
Switch(config)# interface port-channel 5
Switch(config-if)# no switchport
Switch(config-if)# ip address 172.10.20.10 255.255.255.0
Switch(config-if)# end
Configuring the Physical Interfaces
Beginning in privileged EXEC mode, follow these steps to assign an Ethernet port to a Layer 3
EtherChannel. This procedure is required.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
interface interface-id
Specify a physical port, 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
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
37-15
Chapter 37
Configuring EtherChannels and Link-State Tracking
Configuring EtherChannels
Step 5
Command
Purpose
channel-group channel-group-number mode
{auto [non-silent] | desirable [non-silent] | on} |
{active | passive}
Assign the port to a channel group, and specify the PAgP or the
LACP mode.
For channel-group-number, the range is 1 to 48. This number
must be the same as the port-channel-number (logical port)
configured in the Creating Port-Channel Logical Interfaces
section on page 37-14.
For mode, select one of these keywords:
autoEnables 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. This keyword is not supported
when EtherChannel members are from different switches in
the switch stack.
desirableUnconditionally enables PAgP. It places the port
into an active negotiating state, in which the port starts
negotiations with other ports by sending PAgP packets. This
keyword is not supported when EtherChannel members are
from different switches in the switch stack.
onForces the port to channel without PAgP or LACP. In
the on mode, an 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.
activeEnables 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.
passiveEnables 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 37-5 and the
LACP Modes section on page 37-6.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
37-16
OL-12189-01
Chapter 37
Configuring EtherChannels and Link-State Tracking
Configuring EtherChannels
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 gigabitethernet2/0/1 -2
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
This example shows how to configure a cross-stack EtherChannel. It assigns two ports on stack
member 2 and one port on stack member 3 to channel 7 using LACP active mode:
Switch# configure terminal
Switch(config)# interface range gigabitethernet2/0/4 -5
Switch(config-if-range)# no ip address
Switch(config-if-range)# no switchport
Switch(config-if-range)# channel-group 7 mode active
Switch(config-if-range)# exit
Switch(config)# interface gigabitethernet3/0/3
Switch(config-if)# no ip address
Switch(config-if)# no switchport
Switch(config-if)# channel-group 7 mode active
Switch(config-if)# exit
Configuring EtherChannel Load-Balancing
This section describes how to configure EtherChannel load-balancing by using source-based or
destination-based forwarding methods. For more information, see the Load-Balancing and Forwarding
Methods section on page 37-7.
Beginning in privileged EXEC mode, follow these steps to configure EtherChannel load-balancing. This
procedure is optional.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
port-channel load-balance {dst-ip | dst-mac |
src-dst-ip | src-dst-mac | src-ip | src-mac}
Configure an EtherChannel load-balancing method.
The default is src-mac.
Select one of these load-distribution methods:
dst-ipLoad distribution is based on the destination-host IP
address.
dst-macLoad distribution is based on the destination-host
MAC address of the incoming packet.
src-dst-ipLoad distribution is based on the
source-and-destination host-IP address.
src-dst-macLoad distribution is based on the
source-and-destination host-MAC address.
src-ipLoad distribution is based on the source-host IP
address.
src-macLoad distribution is based on the source-MAC
address of the incoming packet.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
37-17
Chapter 37
Configuring EtherChannels and Link-State Tracking
Configuring EtherChannels
Command
Purpose
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.
Configuring the PAgP Learn Method and Priority
Network devices are classified as PAgP physical learners or aggregate-port learners. A device is a
physical learner if it learns addresses by physical ports and directs transmissions based on that
knowledge. A device is an aggregate-port learner if it learns addresses by aggregate (logical) ports. The
learn method must be configured the same at both ends of the link.
When a device and its partner are both aggregate-port learners, they learn the address on the logical
port-channel. The device 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.
PAgP cannot automatically detect when the partner device is a physical learner and when the local device
is an aggregate-port learner. Therefore, you must manually set the learning method on the local device
to learn addresses by physical ports. You also must set the load-distribution method to source-based
distribution, so that any given source MAC address is always sent on the same physical port.
You also can configure a single port within the group for all transmissions and use other ports for hot
standby. The unused ports in the group can be swapped into operation in just a few seconds if the selected
single port loses hardware-signal detection. You can configure which port is always selected for packet
transmission by changing its priority with the pagp port-priority interface configuration command. The
higher the priority, the more likely that the port will be selected.
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 of 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. Only use the pagp learn-method command in this situation.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
37-18
OL-12189-01
Chapter 37
Configuring EtherChannels and Link-State Tracking
Configuring EtherChannels
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.
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 37-17.
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.
Configuring LACP Hot-Standby Ports
When enabled, LACP tries to configure the maximum number of LACP-compatible ports in a channel,
up to a maximum of 16 ports. Only eight LACP links can be active at one time. The software places any
additional links in a hot-standby mode. If one of the active links becomes inactive, a link that is in the
hot-standby mode becomes active in its place.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
37-19
Chapter 37
Configuring EtherChannels and Link-State Tracking
Configuring EtherChannels
If you configure more than eight links for an EtherChannel group, the software automatically decides
which of the hot-standby ports to make active based on the LACP priority. To every link between systems
that operate LACP, the software assigns a unique priority made up of these elements (in priority order):
LACP system priority
System ID (the switch MAC address)
LACP port priority
Port number
In priority comparisons, numerically lower values have higher priority. The priority decides which ports
should be put in standby mode when there is a hardware limitation that prevents all compatible ports
from aggregating.
Determining which ports are active and which are hot standby is a two-step procedure. First the system
with a numerically lower system priority and system-id is placed in charge of the decision. Next, that
system decides which ports are active and which are hot standby, based on its values for port priority and
port number. The port-priority and port-number values for the other system are not used.
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 37-20 and the Configuring the LACP Port Priority section on
page 37-21.
Configuring the LACP System Priority
You can configure the system priority for all the EtherChannels that are enabled for LACP by using the
lacp system-priority global configuration command. You cannot configure a system priority for each
LACP-configured channel. By changing this value from the default, you can affect how the software
selects active and standby links.
You can use the show etherchannel summary privileged EXEC command to see which ports are in the
hot-standby mode (denoted with an H port-state flag).
Beginning in privileged EXEC mode, follow these steps to configure the LACP system priority. This
procedure is optional.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
37-20
OL-12189-01
Chapter 37
Configuring EtherChannels and Link-State Tracking
Configuring EtherChannels
Configuring the LACP Port Priority
By default, all ports use the same port priority. If the local system has a lower value for the system
priority and the system ID than the remote system, you can affect which of the hot-standby links become
active first by changing the port priority of LACP EtherChannel ports to a lower value than the default.
The hot-standby ports that have lower port numbers become active in the channel first. You can use the
show etherchannel summary privileged EXEC command to see which ports are in the hot-standby
mode (denoted with an H port-state flag).
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 default 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
37-21
Chapter 37
Configuring EtherChannels and Link-State Tracking
Displaying EtherChannel, PAgP, and LACP Status
Displaying EtherChannel, PAgP, and LACP Status
To display EtherChannel, PAgP, and LACP status information, use the privileged EXEC commands
described in Table 37-4:
Table 37-4
Commands for Displaying EtherChannel, PAgP, and LACP Status
Command
Description
show etherchannel [channel-group-number {detail |
port | port-channel | protocol | summary}] {detail |
load-balance | port | port-channel | protocol |
summary}
Displays EtherChannel information in a brief, detailed, and
one-line summary form. Also displays the load-balance or
frame-distribution scheme, port, port-channel, and protocol
information.
show pagp [channel-group-number] {counters |
internal | neighbor}
Displays PAgP information such as traffic information, the
internal PAgP configuration, and neighbor information.
show lacp [channel-group-number] {counters |
internal | neighbor}
Displays LACP information such as traffic information, the
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.
Understanding Link-State Tracking
Link-state tracking, also known as trunk failover, is a feature that binds the link state of multiple
interfaces. Link-state tracking provides redundancy in the network when used with server network
interface card (NIC) adapter teaming. When the server network adapters are configured in a primary or
secondary relationship known as teaming and the link is lost on the primary interface, connectivity
transparently changes to the secondary interface.
Figure 37-6 on page 37-23 shows a network configured with link-state tracking. To enable link-state
tracking, create a link-state group, and specify the interfaces that are assigned to the link-state group. An
interface can be an aggregation of ports (an EtherChannel), a single physical port in access or trunk
mode, or a routed port. In a link-state group, these interfaces are bundled together. The downstream
interfaces are bound to the upstream interfaces. Interfaces connected to servers are referred to as
downstream interfaces, and interfaces connected to distribution switches and network devices are
referred to as upstream interfaces.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
37-22
OL-12189-01
Chapter 37
Configuring EtherChannels and Link-State Tracking
Understanding Link-State Tracking
Figure 37-6
Typical Link-State Tracking Configuration
Layer 3 link
Distribution
switch 1
Distribution
switch 2
Link-state
group 1
(Port-channel 1)
Link-state
group 2
(Port-channel 2)
Enclosure
Blade
switch 1
Link-state
group 2
201917
Link-state
group 1
Blade
switch 2
Blade
server
1
Blade
server
2
Blade
server
n1
Blade
server
n
The configuration in Figure 37-6 ensures that when server NIC adapter teaming is used, the traffic flow
continues uninterrupted when the uplink connection to a distribution switch is lost.
The blade switches in the enclosure are connected to distribution switch 1 and distribution switch 2
through port channels.
Link-state group 1 is the primary link from all the blade servers in the enclosure (blade server 1
through blade server n) to distribution switch 1 through port channel 1.
Link-state group 2 is the secondary (backup) links from all the blade servers to distribution switch 2
through port channel 2.
The blade servers can choose which Ethernet server interfaces are active. To balance the network traffic
flow, some Ethernet interfaces in link-state group 1 and some Ethernet interfaces in link-state group 2
are active. For example, when half of the Ethernet server interfaces connected to blade switch 1 are active
and the remaining interfaces connected to blade server 2 are active. the traffic flow can be divided as
follows:
Traffic from half of the active Ethernet interfaces flows through blade switch 1 to distribution
switch 1.
Traffic from the remaining active Ethernet interfaces flows through blade switch 2 to distribution
switch 2.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
37-23
Chapter 37
Configuring EtherChannels and Link-State Tracking
Configuring Link-State Tracking
In a link-state group, the upstream ports can become unavailable or lose connectivity because the
distribution switch or router fails, the cables are disconnected, or the link is lost. These are the
interactions between the downstream and upstream interfaces when link-state tracking is enabled:
If any of the upstream interfaces are in the link-up state, the downstream interfaces can change to or
remain in the link-up state.
If all of the upstream interfaces become unavailable, link-state tracking automatically puts the
downstream interfaces in the error-disabled state. Connectivity to and from the servers is
automatically changed from the primary server interface to the secondary server interface.
As an example of a connectivity change from link-state group 1 to link-state group 2, when the
primary link from blade switch 1 to distribution switch 1 is lost, blade server 1 connects through its
secondary Ethernet server interface to blade switch 2 in link-state group 2.
If the link-state group is configured, link-state tracking is disabled, and the upstream interfaces lose
connectivity, the link states of the downstream interfaces remain unchanged. The server does not
recognize that upstream connectivity has been lost and does not failover to the secondary interface.
You can recover a downstream interface link-down condition by removing the failed downstream port
from the link-state group. To recover from multiple downstream interfaces, disable the link-state group.
Configuring Link-State Tracking
These sections describe how to configure link-state tracking ports:
Default Link-State Tracking Configuration, page 37-24
Link-State Tracking Configuration Guidelines, page 37-24
Configuring Link-State Tracking, page 37-25
Displaying Link-State Tracking Status, page 37-26
Default Link-State Tracking Configuration
There are no link-state groups defined, and link-state tracking is not enabled for any group.
Link-State Tracking Configuration Guidelines
Follow these guidelines to avoid configuration problems:
An interface that is defined as an upstream interface cannot also be defined as a downstream
interface in the same or a different link-state group. The reverse is also true.
An interface cannot be a member of more than one link-state group.
You can configure only two link-state groups per nonstacking-capable switch.
You can configure only ten link-state groups per stacking-capable switch.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
37-24
OL-12189-01
Chapter 37
Configuring EtherChannels and Link-State Tracking
Configuring Link-State Tracking
Do not configure an EtherChannel as a downstream interface.
Only interfaces gigabitethernetn/0/1 through gigabitethernetn/0/14, where n is the stack member
number from 1 to 9, can be configured as downstream ports in a specific link-state group.
Only these interfaces can be configured as upstream ports in a specific link-state group:
Gigabitethernetn/0/15 through gigabitethernetn/0/18, where n is the stack member number
from 1 to 9
Tengigabitethernetn/0/1, where n is the stack member number from 1 to 9
Configuring Link-State Tracking
Beginning in privileged EXEC mode, follow these steps to configure a link-state group and to assign an
interface to a group:
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 10. 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
EtherChannel interface (static or LACP), that is also in trunk
mode.
Step 4
link state group [number] {upstream |
downstream}
Specify a link-state group, and configure the interface as either
an upstream or downstream interface in the group. The group
number can be 1 to 10. 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 to configure the interface:
Switch# configure terminal
Switch(config)# link state track 1
Switch(config)# interface port-channel 1
Switch(config-if)# link state group 1 upstream
Switch(config-if)# end
Note
If the interfaces are part of an EtherChannel, you must specify the port channel name as part of the
link-state group, not the individual port members.
To disable a link-state group, use the no link state track number global configuration command.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
37-25
Chapter 37
Configuring EtherChannels and Link-State Tracking
Configuring Link-State Tracking
Displaying Link-State Tracking Status
Use the show link state group command to display the link-state group information. Enter this
command without keywords to display information about all link-state groups. Enter the group number
to display information specific to the group. Enter the detail keyword to display detailed information
about the group.
This is an example of output from the show link state group 1 command:
Switch> show link state group 1
Link State Group: 1
Status: Enabled, Down
This is an example of output from the show link state group detail command:
Switch> show link state group detail
(Up):Interface up
(Dwn):Interface Down
(Dis):Interface disabled
Link State Group: 1
Status: Enabled, Up
Upstream Interfaces
: Po1(Up)
Downstream Interfaces : Gi0/3(Up) Gi0/4(Up)
(Up):Interface up
(Dwn):Interface Down
(Dis):Interface disabled
For detailed information about the fields in the display, see the command reference for this release.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
37-26
OL-12189-01
CH A P T E R
38
Configuring IP Unicast Routing
This chapter describes how to configure IP Version 4 (IPv4) unicast routing on the switch. Unless
otherwise noted, the term switch refers to a standalone switch and to a switch stack. A switch stack
operates and appears as a single router to the rest of the routers in the network.
Basic routing functions, including static routing and the Routing Information Protocol (RIP), are
available with both the IP base feature set and the IP services feature set. To use advanced routing
features and other routing protocols, you must have the IP services feature set enabled on the standalone
switch or on the stack master.
Note
If the switch or switch stack is running the advanced IP services feature set on the Catalyst Switch
Module 3110, you can also enable IP Version 6 (IPv6) unicast routing and configure interfaces to
forward IPv6 traffic in addition to IPv4 traffic. For information about configuring IPv6 on the switch,
see Chapter 39, Configuring IPv6 Host Functions and Unicast Routing.
For more detailed IP unicast configuration information, see the Cisco IOS IP Configuration Guide,
Release 12.2 from the Cisco.com page under Documentation > Cisco IOS Software > 12.2 Mainline
> Configuration Guides. For complete syntax and usage information for the commands used in this
chapter, see these command references from the Cisco.com page under Documentation > Cisco IOS
Software > 12.2 Mainline > 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:
Supported IPv4 Features, page 38-2
Understanding IP Routing, page 38-3
Steps for Configuring Routing, page 38-6
Configuring IP Addressing, page 38-6
Enabling IP Unicast Routing, page 38-20
Configuring RIP, page 38-21
Configuring Stub Routing, page 38-26
Configuring OSPF, page 38-31 (only the Catalyst Switch Module 3110)
Configuring EIGRP, page 38-41 (only the Catalyst Switch Module 3110)
Configuring BGP, page 38-49 (only the Catalyst Switch Module 3110)
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-1
Chapter 38
Configuring IP Unicast Routing
Supported IPv4 Features
Note
Configuring Multi-VRF CE, page 38-70 (only the Catalyst Switch Module 3110)
Configuring Protocol-Independent Features, page 38-85
Monitoring and Maintaining the IP Network, page 38-101
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 8, Configuring SDM Templates, or see the sdm prefer command in
the command reference for this release.
Supported IPv4 Features
Table 38-1 shows the supported IPv4 features on each switch.
Table 38-1
Supported IPv4 Features
Feature
Catalyst Switch Module 3110
Catalyst Switch Module 3012
Default routing
Yes
Yes
Static routing
Yes
Yes
Distance-vector protocols for
dynamic routing
Yes
Yes
Link-state protocols for dynamic Yes
routing
No
ARP1, proxy ARP, and RARP2
Yes
Yes
Broadcast packets
Yes
Yes
IPv4 routing
Yes
Yes
Yes
Yes
Yes
No
Yes
No
Yes
No
Yes
No
Stub routing
Yes
Yes
Unicast Reverse Path
Forwarding
Yes
No
CEF9
Yes
Yes
Yes
No
Yes
No
RIP
OSPF
EIGRP5
BGP
6
7
Multi-VRF CE
dCEF
PBR
10
11
1. ARP = Address Resolution Protocol.
2. RARP = Reverse Address Resolution Protocol.
3. RIP = Routing Information Protocol.
4. OSPF = Open Shortest Path First.
5. EIGRP = Enhanced Interior Gateway Routing Protocol.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-2
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Understanding IP Routing
6. BGP = Border Gateway Protocol.
7. VRF = Virtual Private Networks routing/forwarding.
8. CE = customer edge.
9. CEF = Cisco Express Forwarding.
10. dCEF = distributed CEF.
11. PBR = policy-based routing.
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 38-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.
Routing Topology Example
VLAN 10
A
Host
VLAN 20
Switch A
Switch B
C
Host
B
Host
ISL Trunks
18071
Figure 38-1
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 surveys the routing table, finds 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.
This section contains information on these routing topics:
Types of Routing, page 38-3
IP Routing and Switch Stacks, page 38-4
Types of Routing
Routers and Layer 3 switches can route packets in these ways:
By using default routing
By using preprogrammed static routes for the traffic
By dynamically calculating routes by using a routing protocol
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-3
Chapter 38
Configuring IP Unicast Routing
Understanding IP Routing
Default routing refers to sending traffic with a destination unknown to the router to a default outlet
or destination.
Static unicast routing forwards packets from predetermined ports through a single path into and out of a
network. Static routing is secure and uses little bandwidth, but it does not automatically respond to
changes in the network, such as link failures. Therefore, network changes might result in unreachable
destinations. As networks grow, static routing becomes a labor-intensive liability.
Routers use these dynamic routing protocols to dynamically calculate the best route for forwarding
traffic:
Routers that use distance-vector protocols maintain routing tables with distance values of networked
resources and periodically pass these tables to their neighbors. Distance-vector protocols use one or
a series of metrics for calculating the best routes.
(Only on the Catalyst Switch Module 3110) Routers using link-state protocols maintain a complex
database of network topology based on the exchange of link-state advertisements (LSAs) between
routers. LSAs are triggered by an event in the network, which speeds up the convergence time or
time required to respond to these changes. Link-state protocols respond quickly to topology changes
but require greater bandwidth and more resources than distance-vector protocols.
Distance-vector protocols supported by the Catalyst Switch Module 3110 use Routing Information
Protocol (RIP), a single-distance metric (cost) that determines the best path, and Border Gateway
Protocol (BGP), which adds a path vector mechanism. The switch also supports the Open Shortest Path
First (OSPF) link-state protocol and Enhanced IGRP (EIGRP), which adds some link-state routing
features to traditional Interior Gateway Routing Protocol (IGRP) to improve efficiency.
The Catalyst Switch Module 3012 supports only RIP.
Note
On a switch or switch stack, the supported protocols are determined by the software running on the
switch or stack master. If the switch or stack master is running the IP base feature set, only default
routing, static routing and RIP are supported. All other routing protocols require the IP services feature
set.
IP Routing and Switch Stacks
A switch stack appears to the network as a single router, regardless of which switch in the stack is
connected to a routing peer. For additional information about switch stack operation, see Chapter 5,
Managing Switch Stacks.
The stack master performs these functions:
It initializes and configures the routing protocols.
It sends routing protocol messages and updates to other routers.
It processes routing protocol messages and updates received from peer routers.
It generates, maintains, and distributes the distributed Cisco Express Forwarding (dCEF) database
to all stack members. The routes are programmed on all switches in the stack bases on this database.
The MAC address of the stack master is used as the router MAC address for the whole stack, and all
outside devices use this address to send IP packets to the stack.
All IP packets that require software forwarding or processing go through the CPU of the stack
master.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-4
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Understanding IP Routing
Stack members perform these functions:
They act as routing standby switches, ready to take over in case they are elected as the new stack
master if the stack master fails.
They program the routes into hardware. The routes programmed by the stack members are the same
that are downloaded by the stack master as part of the dCEF database.
If a stack master fails, the stack detects that the stack master is down and elects one of the stack members
to be the new stack master. During this period, except for a momentary interruption, the hardware
continues to forward packets with no active protocols.
However, even though the switch stack maintains the hardware identification after a failure, the routing
protocols on the router neighbors might flap during the brief interruption before the stack master restarts.
Routing protocols such as OSPF and EIGRP need to recognize neighbor transitions. The router uses two
levels of nonstop forwarding (NSF) to detect a change-over, to continue forwarding network traffic, and
to recover route information from peer devices:
NSF-aware routers tolerate neighboring router failures. After the neighbor router restarts, an
NSF-aware router supplies information about its state and route adjacencies on request.
NSF-capable routers support NSF. When they detect a stack master change, they rebuild routing
information from NSF-aware or NSF-capable neighbors and do not wait for a restart.
The switch stack supports NSF-capable routing for OSPF and EIGRP. For more information, see the
OSPF NSF Capability section on page 38-34 and the EIGRP NSF Capability section on page 38-45.
Upon election, the new stack master performs these functions:
It starts generating, receiving, and processing routing updates.
It builds routing tables, generates the CEF database, and distributes it to stack members.
It uses its MAC address as the router MAC address. To notify its network peers of the new MAC
address, it periodically (every few seconds for 5 minutes) sends a gratuitous ARP reply with the new
router MAC address.
Note
Note
Caution
If you configure the persistent MAC address feature on the stack and the stack master
changes, the stack MAC address does not change for the configured time period. If the
previous stack master rejoins the stack as a member switch during that time period, the stack
MAC address remains the MAC address of the previous stack master. See the Enabling
Persistent MAC Address section on page 5-22.
It attempts to determine the reachability of every proxy ARP entry by sending an ARP request to the
proxy ARP IP address and receiving an ARP reply. For each reachable proxy ARP IP address, it
generates a gratuitous ARP reply with the new router MAC address. This process is repeated for
5 minutes after a new stack master election.
When a stack master is running the IP services feature set, the stack can run all supported protocols,
including Open Shortest Path First (OSPF), Enhanced IGRP (EIGRP), and Border Gateway Protocol
(BGP). If the stack master fails and the new elected stack master is running the IP base feature set, these
protocols no longer run on the stack.
Partitioning on the switch stack into two or more stacks might lead to undesirable behavior in the
network.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-5
Chapter 38
Configuring IP Unicast Routing
Steps for Configuring Routing
Steps for Configuring Routing
By default, IP routing is disabled on the switch, and you must enable it before routing can take place.
For detailed IP routing configuration information, see the Cisco IOS IP Configuration Guide,
Release 12.2 from the Cisco.com page under Documentation > Cisco IOS Software > 12.2 Mainline
> Configuration Guides.
In the following procedures, the specified interface must be one of these Layer 3 interfaces:
Note
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 37-14.
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 38-8.
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 routing consists of several main procedures:
To support VLAN interfaces, create and configure VLANs on the switch or switch stack, and assign
VLAN membership to Layer 2 interfaces. For more information, see Chapter 12, Configuring
VLANs.
Configure Layer 3 interfaces.
Enable IP routing on the switch.
Assign IP addresses to the Layer 3 interfaces.
Enable selected routing protocols on the switch.
Configure routing protocol parameters (optional).
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 to 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 38-7
Assigning IP Addresses to Network Interfaces, page 38-8
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-6
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring IP Addressing
Configuring Address Resolution Methods, page 38-10
Routing Assistance When IP Routing is Disabled, page 38-13
Configuring Broadcast Packet Handling, page 38-15
Monitoring and Maintaining IP Addressing, page 38-19
Default Addressing Configuration
Table 38-2 shows the default addressing configuration.
Table 38-2
Default Addressing Configuration
Feature
Default Setting
IP address
None defined.
ARP
No permanent entries in the Address Resolution Protocol (ARP) cache.
Encapsulation: Standard Ethernet-style ARP.
Timeout: 14400 seconds (4 hours).
IP broadcast address
255.255.255.255 (all ones).
IP classless routing
Enabled.
IP default gateway
Disabled.
IP directed broadcast
Disabled (all IP directed broadcasts are dropped).
IP domain
Domain list: No domain names defined.
Domain lookup: Enabled.
Domain name: Enabled.
IP forward-protocol
If a helper address is defined or User Datagram Protocol (UDP) flooding is
configured, UDP forwarding is enabled on default ports.
Any-local-broadcast: Disabled.
Spanning Tree Protocol (STP): Disabled.
Turbo-flood: Disabled.
IP helper address
Disabled.
IP host
Disabled.
IRDP
Disabled.
Defaults when enabled:
Broadcast IRDP advertisements.
Maximum interval between advertisements: 600 seconds.
Minimum interval between advertisements: 0.75 times maximum
interval
Preference: 0.
IP proxy ARP
Enabled.
IP routing
Disabled.
IP subnet-zero
Disabled.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-7
Chapter 38
Configuring IP Unicast Routing
Configuring IP Addressing
Assigning IP Addresses to Network Interfaces
An IP address identifies a location to which IP packets can be sent. Some IP addresses are reserved for
special uses and cannot be used for host, subnet, or network addresses. RFC 1166, Internet Numbers,
contains the official description of IP addresses.
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]
show ip interface [interface-id]
show running-config interface [interface-id]
Verify your entries.
Step 8
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Use of Subnet Zero
We strongly discourage subnetting with a subnet address of zero because of the problems that can arise
if a network and a subnet have the same addresses. For example, if network 131.108.0.0 is subnetted as
255.255.255.0, subnet zero would be written as 131.108.0.0, which is the same as the network address.
You can use the all ones subnet (131.108.255.0) and, even though we discourage this practice, you can
enable the subnet zero if you need the entire subnet space for your IP address.
Beginning in privileged EXEC mode, follow these steps to enable subnet zero:
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 to disable the use of
subnet zero.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-8
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring IP Addressing
Classless Routing
By default, classless routing is enabled when the switch 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 is contiguous blocks of Class C address spaces simulating a single,
larger address space and is designed to relieve the pressure on the rapidly depleting Class B address
space.
In Figure 38-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.
Figure 38-2
IP Classless Routing
128.0.0.0/8
128.20.4.1
128.20.0.0
128.20.1.0
IP classless
128.20.3.0
128.20.4.1
Host
45749
128.20.2.0
In Figure 38-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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-9
Chapter 38
Configuring IP Unicast Routing
Configuring IP Addressing
Figure 38-3
No IP Classless Routing
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.4.1
Host
45748
128.20.2.0
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 so that the switch forwards packets destined for a subnet of a network without a
network default route to the best possible supernet route, use the ip classless global configuration
command.
Configuring Address Resolution Methods
You can control interface-specific handling of IP by using address resolution. A device using IP can have
both a local address or a MAC address, which uniquely defines the device on its local segment or LAN,
and a network address, which identifies the network to which the device belongs.
Note
In a switch stack, network communication uses a single MAC address and the IP address of the stack.
The local address or the MAC address is known as a data-link address because it is contained in the
data-link layer (Layer 2) section of the packet header and is read by data-link (Layer 2) devices. To
communicate with an Ethernet device, the software must learn the MAC address of the device. The
process of learning the MAC address from an IP address is called address resolution. The process of
learning the IP address from the MAC address is called reverse address resolution.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-10
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring IP Addressing
The switch uses these types of address resolution:
Address Resolution Protocol (ARP) associates IP address with MAC addresses. Using an IP address
as input, ARP learns the associated MAC address and then stores the IP address/MAC address
association in an ARP cache for rapid retrieval. Then the IP datagram is encapsulated in a link-layer
frame and sent over the network. Encapsulation of IP datagrams and ARP requests or replies on
IEEE 802 networks other than Ethernet is specified by the Subnetwork Access Protocol (SNAP).
Proxy ARP helps hosts with no routing tables learn the MAC addresses of hosts on other networks
or subnets. If the switch (router) receives an ARP request for a host that is not on the same interface
as the ARP request sender, and if the router has all of its routes to the host through other interfaces,
it generates a proxy ARP packet giving its own local data-link address. The host that sent the ARP
request then sends its packets to the router, which forwards them to the intended host.
The switch also uses the Reverse Address Resolution Protocol (RARP), which functions the same as
ARP does, except that the RARP packets request an IP address instead of a local MAC address. Using
RARP requires a RARP server on the same network segment as the router interface. Use the ip
rarp-server address interface configuration command to identify the server.
For more information on RARP, see the Cisco IOS Configuration Fundamentals Configuration Guide,
Release 12.2 under Documentation > Cisco IOS Software > 12.2 Mainline > Configuration Guides
from the Cisco.com page.
You can perform these tasks to configure address resolution:
Define a Static ARP Cache, page 38-11
Set ARP Encapsulation, page 38-12
Enable Proxy ARP, page 38-13
Define a Static ARP Cache
ARP and other address resolution protocols provide dynamic mapping between IP addresses and MAC
addresses. Because most hosts support dynamic address resolution, you usually do not need to specify
static ARP cache entries. If you must define a static ARP cache entry, you can do so globally, which
installs a permanent entry in the ARP cache that the switch uses to translate IP addresses into MAC
addresses. You can also specify that the switch respond to ARP requests as if it were the owner of the
specified IP address. If you do not want the ARP entry to be permanent, you can specify a timeout period
for the ARP entry.
Beginning in privileged EXEC mode, follow these steps to provide static mapping between IP addresses
and MAC addresses:
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:
arpaARP encapsulation for Ethernet interfaces
snapSubnetwork Address Protocol encapsulation for
Token Ring and FDDI interfaces
sapHPs ARP type
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-11
Chapter 38
Configuring IP Unicast Routing
Configuring IP Addressing
Command
Purpose
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 that an ARP cache entry stays
in the cache. The range is 0 to 2147483 seconds. The default is
14400 seconds (4 hours).
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 on 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.
Set ARP Encapsulation
By default, Ethernet ARP encapsulation (represented by the arpa keyword) is enabled on an IP interface.
You can change the encapsulation method to SNAP if required by your network.
Beginning in privileged EXEC mode, follow these steps to specify the ARP encapsulation type:
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:
arpaAddress Resolution Protocol
snapSubnetwork 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-12
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring IP Addressing
Enable Proxy ARP
By default, the switch uses proxy ARP to help hosts learn MAC addresses of hosts on other networks or
subnets.
Beginning in privileged EXEC mode, follow these steps to enable proxy ARP if it has been disabled:
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.
Routing Assistance When IP Routing is Disabled
These mechanisms allow the switch to learn about routes to other networks when it does not have IP
routing enabled:
Proxy ARP, page 38-13
Default Gateway, page 38-13
ICMP Router Discovery Protocol (IRDP), page 38-14
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 learn 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. The host that sent the request then 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 38-13. 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 returns an IP Control Message Protocol
(ICMP) redirect message, identifying the local router that the host should use. The switch caches the
redirect messages and forwards each packet as efficiently as possible. This method cannot detect when
the default router has failed or is unavailable.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-13
Chapter 38
Configuring IP Unicast Routing
Configuring IP Addressing
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.
Use the no ip default-gateway global configuration command to disable this function.
ICMP Router Discovery Protocol (IRDP)
Router discovery allows the switch to dynamically learn about routes to other networks by using ICMP
Router Discovery Protocol (IRDP). Hosts use IRDP to locate routers. When operating as a client, the
switch generates router discovery packets. When operating as a host, the switch receives router discovery
packets. The switch can also receive Routing Information Protocol (RIP) routing updates and use this
information to infer locations of routers. The switch does not actually store the routing tables sent by
routing devices; it merely keeps track of which systems are sending the data. The advantage of using
IRDP is that it allows each router to specify both a priority and the time after which a device is assumed
to be down if no more packets are received.
Each device discovered becomes a candidate for the default router, and a new highest-priority router is
selected when a higher priority router is discovered, when the current default router is declared down,
or when a TCP connection is about to time out because of excessive retransmissions.
The only required task for IRDP routing on an interface is to enable IRDP processing on that interface.
When enabled, the default parameters apply. You can change any of these parameters.
Beginning in privileged EXEC mode, follow these steps to enable and configure IRDP on an 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 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
Step 5
ip irdp holdtime seconds
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.
(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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-14
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring IP Addressing
Command
Purpose
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.
It is important that you 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.
Configuring Broadcast Packet Handling
After configuring an IP interface address, you can enable routing and configure one or more routing
protocols, or you can configure the way the switch responds to network broadcasts. A broadcast is a data
packet destined for all hosts on a physical network. The switch supports these kinds of broadcasting:
Note
A directed broadcast packet sent to a specific network or series of networks. A directed broadcast
address includes the network or subnet fields.
A flooded broadcast packet sent to every network.
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 25, Configuring Port-Based Traffic Control.
Routers provide some protection from broadcast storms by limiting the 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 IP implementations, you can set the broadcast
address. Many implementations, including the one in the 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 38-16
Forwarding UDP Broadcast Packets and Protocols, page 38-17
Establishing an IP Broadcast Address, page 38-17
Flooding IP Broadcasts, page 38-18
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-15
Chapter 38
Configuring IP Unicast Routing
Configuring IP Addressing
Enabling Directed Broadcast-to-Physical Broadcast Translation
By default, IP directed broadcasts are dropped; they are not forwarded. Dropping IP-directed broadcasts
makes routers less susceptible to denial-of-service attacks.
You can enable forwarding of IP-directed broadcasts on an interface when the broadcast becomes a
physical (MAC-layer) broadcast. Only those protocols configured by using the ip forward-protocol
global configuration command are forwarded.
You can specify an access control list (ACL) to control which broadcasts are forwarded. When an ACL
is specified, only those IP packets permitted by the ACL can be translated from directed broadcasts to
physical broadcasts. For more information on access lists, see Chapter 34, Configuring Network
Security with ACLs.
Beginning in privileged EXEC mode, follow these steps to enable forwarding of IP-directed broadcasts
on an 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 directed-broadcast [access-list-number]
Enable directed broadcast-to-physical broadcast translation on the
interface. You can include an ACL to control which broadcasts are
forwarded. When 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
Step 5
ip forward-protocol {udp [port] | nd | sdns} Specify the protocols and ports the router uses when forwarding
broadcast packets.
Return to global configuration mode.
udpForward UPD datagrams.
port: (Optional) Destination port that controls which UDP
services are forwarded.
ndForward Network Disk datagrams.
sdnsForward Secure Data Network Service (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.
Use the no ip directed-broadcast interface configuration command to disable translation of directed
broadcasts to physical broadcasts. Use the no ip forward-protocol global configuration command to
remove a protocol or a port.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-16
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring IP Addressing
Forwarding UDP Broadcast Packets and Protocols
User Datagram Protocol (UDP) is an IP host-to-host layer protocol. UDP provides a connectionless
session between two end systems and does not acknowledge received datagrams. Network hosts can use
UDP broadcasts to find address, configuration, and name information. If such a host is on a network
segment that does not include a server, UDP broadcasts might not be forwarded. However, you can
configure an interface on a router to forward certain broadcast classes to a helper address. You can use
more than one helper address per interface.
You can specify a UDP destination port to control which UDP services are forwarded. You can specify
multiple UDP protocols. You can also specify the Network Disk Protocol (NDP), which is used by older
diskless Sun workstations and the network security protocol SDNS.
By default, both UDP and NDP 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 of UDP broadcast packets
on an interface and to 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.
Establishing an IP Broadcast Address
The IP broadcast address (and the default) is an address consisting of all ones (255.255.255.255).
However, the switch can be configured to generate any form of IP broadcast address.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-17
Chapter 38
Configuring IP Unicast Routing
Configuring IP Addressing
Beginning in privileged EXEC mode, follow these steps to set the IP broadcast address on an 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 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, you must configure bridging 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
to be met for packet forwarding when 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, Network Disk, 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 2.
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 never changed. The TTL value decrements.
When a flooded UDP datagram is sent on an interface (and the destination address is possibly changed),
the datagram is processed by the normal IP output routines and is, therefore, subject to ACLs, if they are
present on the output interface.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-18
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring IP Addressing
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 the 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.
Monitoring and Maintaining IP Addressing
When the contents of a particular cache, table, or database have become or are suspected to be invalid,
you can remove all its contents by using the clear privileged EXEC commands. Table 38-3 lists the
commands for clearing contents.
Table 38-3
Commands to Clear Caches, Tables, and Databases
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-19
Chapter 38
Configuring IP Unicast Routing
Enabling IP Unicast Routing
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 38-4 lists
the privileged EXEC commands for displaying IP statistics.
Table 38-4
Commands to Display Caches, Tables, and Databases
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.
Enabling IP Unicast Routing
By default, the switch is in Layer 2 switching mode, and IP routing is disabled. To use the Layer 3
capabilities of the switch, you must enable IP routing.
Beginning in privileged EXEC mode, follow these steps to enable IP routing:
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.
Note
The IP base feature set supports only RIP as a routing
protocol.
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 ip routing global configuration command to disable routing.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-20
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring RIP
This example shows how to enable IP routing by using RIP as the routing protocol:
Switch# configure terminal
Enter configuration commands, one per line.
Switch(config)# ip routing
Switch(config)# router rip
Switch(config-router)# network 10.0.0.0
Switch(config-router)# end
End with CNTL/Z.
You can now set parameters for the selected routing protocols as described in these sections:
Configuring RIP, page 38-21
Configuring Stub Routing, page 38-26
Configuring OSPF, page 38-31 (only the Catalyst Switch Module 3110)
Configuring EIGRP, page 38-41 (only the Catalyst Switch Module 3110)
Configuring BGP, page 38-49 (only the Catalyst Switch Module 3110)
Configuring Unicast Reverse Path Forwarding, page 38-85
Configuring Protocol-Independent Features, page 38-85 (optional)
Configuring RIP
The Routing Information Protocol (RIP) is an interior gateway protocol (IGP) 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. You can find detailed information about
RIP in IP Routing Fundamentals, published by Cisco Press.
Note
RIP is the only routing protocol supported by the IP base feature set; other routing protocols require the
switch or the stack master to be running the IP services feature set.
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 that 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. The hop count range is 0 to 15. A directly connected network has a hop count of
zero; a network with a hop count of 16 is unreachable. The small range 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 interfaces network is not specified, it is not advertised in any
RIP update.
These sections contain this configuration information:
Default RIP Configuration, page 38-22
Configuring Basic RIP Parameters, page 38-22
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-21
Chapter 38
Configuring IP Unicast Routing
Configuring RIP
Configuring RIP Authentication, page 38-24
Configuring Summary Addresses and Split Horizon, page 38-24
Default RIP Configuration
Table 38-5 shows the default RIP configuration.
Table 38-5
Default RIP Configuration
Feature
Default Setting
Auto summary
Enabled.
Default-information originate
Disabled.
Default metric
Built-in; automatic metric translations.
IP RIP authentication key-chain No authentication.
Authentication mode: clear text.
IP RIP receive version
According to the version router configuration command.
IP RIP send version
According to the version router configuration command.
IP RIP triggered
According to the version router configuration command.
IP split horizon
Varies with media.
Neighbor
None defined.
Network
None specified.
Offset list
Disabled.
Output delay
0 milliseconds.
Timers basic
Update: 30 seconds.
Invalid: 180 seconds.
Hold-down: 180 seconds.
Flush: 240 seconds.
Validate-update-source
Enabled.
Version
Receives RIP Version 1 and 2 packets; sends Version 1 packets.
Configuring Basic RIP Parameters
To configure RIP, you enable RIP routing for a network and optionally configure other parameters. RIP
configuration commands are ignored on the switch until you configure the network number.
Beginning in privileged EXEC mode, follow these steps to enable and configure RIP:
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-22
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring RIP
Step 4
Command
Purpose
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]
{in | out} offset [type number]
(Optional) Apply an offset list to routing metrics to increase incoming
and outgoing metrics to routes learned through RIP. You can limit the
offset list with an access list or an interface.
Step 7
timers basic update invalid holddown
flush
(Optional) Adjust routing protocol timers. Valid ranges for all timers are
0 to 4294967295 seconds.
updateThe time between sending routing updates. The default is
30 seconds.
invalidThe time after which a route is declared invalid. The default
is 180 seconds.
holddownThe time until a route is removed from the routing table.
The default is 180 seconds.
flushThe 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
Version 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 (only RIP Version 2) 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, we do not recommend
that you disable this feature. 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 time
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-23
Chapter 38
Configuring IP Unicast Routing
Configuring RIP
Command
Purpose
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. To display summary address entries in the RIP database, use the
show ip rip database privileged EXEC command.
Configuring RIP Authentication
RIP Version 1 does not support authentication. If you are sending and receiving RIP Version 2 packets,
you can enable RIP authentication on an interface. The key chain specifies the set of keys that can be
used on the interface. If a key chain is not configured, no authentication is performed, not even the
default. Therefore, you must also perform the tasks in the Managing Authentication Keys section on
page 38-99.
The switch supports these modes of authentication on interfaces for which RIP authentication is enabled:
plain text and MD5. The default is plain text.
Beginning in privileged EXEC mode, follow these steps to configure RIP authentication on an 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 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.
Configuring Summary Addresses and Split Horizon
Routers connected to broadcast-type IP networks and using distance-vector routing protocols normally
use the split-horizon mechanism to reduce the possibility of routing loops. Split horizon blocks
information about routes from being advertised by a router on any interface from which that information
originated. This feature usually optimizes communication among multiple routers, especially when links
are broken.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-24
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring RIP
Note
In general, we do not recommend disabling split horizon 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.
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 the 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.
To disable IP summarization, use the no ip summary-address rip router configuration command.
In this example, the major net is 10.0.0.0. The summary address of 10.2.0.0 overrides the autosummary
address of 10.0.0.0 so that 10.2.0.0 is advertised from interface Gigabit Ethernet port 2, and 10.0.0.0 is
not advertised. In the example, if the interface is still in Layer 2 mode (the default), you must enter the
no switchport interface configuration command before entering the ip address interface configuration
command.
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.
Switch(config)# router rip
Switch(config-router)# interface gigabitethernet1/0/2
Switch(config-if)# ip address 10.1.5.1 255.255.255.0
Switch(config-if)# ip summary-address rip 10.2.0.0 255.255.0.0
Switch(config-if)# no ip split-horizon
Switch(config-if)# exit
Switch(config)# router rip
Switch(config-router)# network 10.0.0.0
Switch(config-router)# neighbor 2.2.2.2 peer-group mygroup
Switch(config-router)# end
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-25
Chapter 38
Configuring IP Unicast Routing
Configuring Stub Routing
Configuring Split Horizon
Routers connected to broadcast-type IP networks and using distance-vector routing protocols normally
use the split-horizon mechanism to reduce the possibility of routing loops. Split horizon blocks
information about routes from being advertised by a router on any interface from which that information
originated. This feature can optimize communication among multiple routers, especially when links are
broken.
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 the 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 Stub Routing
The stub routing feature reduces resource usage by moving routed traffic closer to the end user. The
switch supports Protocol-Independent Multicast (PIM) stub routing and Enhanced Interior Gateway
Routing Protocol (EIGRP) stub routing.
Stub routing is explained in these sections:
Understanding PIM Stub Routing, page 38-26
Configuring PIM Stub Routing, page 38-27
Understanding EIGRP Stub Routing, page 38-29
Configuring EIGRP Stub Routing, page 38-30
Understanding PIM Stub Routing
In a network using PIM stub routing, the only allowable route for IP traffic to the user is through a switch
that is configured with PIM stub routing. PIM passive interfaces are connected to Layer 2 access
domains, such as VLANs, or to interfaces that are connected to other Layer 2 devices. Only directly
connected multicast (IGMP) receivers and sources are allowed in the Layer 2 access domains. The PIM
passive interfaces do not send or process any received PIM control packets.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-26
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring Stub Routing
When using PIM stub routing, you should configure the distribution and remote routers to use IP
multicast routing and configure only the switch as a PIM stub router. The switch does not route transit
traffic between distribution routers. You also need to configure a routed uplink port on the switch. The
switch uplink port cannot be used with SVIs.
You must also configure EIGRP stub routing when configuring PIM stub routing on the switch. For more
information, see the Understanding EIGRP Stub Routing section on page 38-29 and the Configuring
EIGRP Stub Routing section on page 38-30.
The redundant PIM stub router topology is not supported. The redundant topology exists when there is
more than one PIM router forwarding multicast traffic to a single access domain. PIM messages are
blocked, and the PIM assert and designated router election mechanisms are not supported on the PIM
passive interfaces. Only the nonredundant access router topology is supported by the PIM stub feature.
By using a nonredundant topology, the PIM passive interface assumes that it is the only interface and
designated router on that access domain.
In Figure 38-4, Switch A routed uplink port 25 is connected to the router, and PIM stub routing is
enabled on the VLAN 100 interfaces and on Host 3. This configuration allows the directly connected
hosts to receive traffic from multicast source 200.1.1.3. See the Configuring PIM Stub Routing section
on page 38-27 for more information.
PIM Stub Router Configuration
Switch
A
3.1.1.2.255.255.255.0
Port 15
Source
200.1.1.3
Port 3
Router
VLAN 100
Host 1
Host 2
Host 3
203883
Figure 38-4
Configuring PIM Stub Routing
The PIM stub routing feature supports multicast routing between the distribution layer and the access
layer. It supports both uplink PIM interfaces and PIM passive interfaces. A routed interface configured
with the PIM passive mode does not forward PIM control traffic, it only passes and forwards IGMP
traffic.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-27
Chapter 38
Configuring IP Unicast Routing
Configuring Stub Routing
PIM Stub Routing Configuration Guidelines
Follow these guidelines when enabling PIM stub routing on an interface:
Before configuring PIM stub routing, you must have IP multicast routing configured on both the stub
router and the central router. You must also have PIM mode (dense-mode, sparse-mode, or
dense-sparse-mode) configured on the uplink interface of the stub router.
The PIM stub router does not route traffic between the distribution routers. Unicast (EIGRP) stub
routing manages this behavior. You must configure unicast stub routing to assist the PIM stub router
behavior. For more information, see the Configuring EIGRP Stub Routing section on page 38-30.
Only directly connected multicast (IGMP) receivers and sources are allowed in the Layer 2 access
domains. The PIM protocol is not supported in access domains.
The redundant PIM stub router topology is not supported.
Enabling PIM Stub Routing
Beginning in privileged EXEC mode, follow these steps to enable PIM stub routing on an interface. This
procedure is optional.
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. The PIM uplink port 25 on Switch A 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 38-4:
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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-28
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring Stub Routing
Switch(config-if)#
Switch(config-if)#
Switch(config-if)#
Switch(config-if)#
no switchport
ip address 10.1.1.1 255.255.255.0
ip pim passive
end
To verify that PIM stub is enabled, 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 information.
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.
Understanding EIGRP Stub Routing
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.
Note
The IP base feature set contains EIGRP stub routing capability, which 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. For enhanced
capability and complete EIGRP routing, the switch must be running the IP services feature set.
On a switch running the IP base feature set, if you try to configure multi-VRF-CE and EIGRP stub
routing at the same time, the configuration is not allowed.
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 38-5, 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
Switches A and C. Switch B does not advertise any routes learned from Switch A (and the reverse).
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-29
Chapter 38
Configuring IP Unicast Routing
Configuring Stub Routing
Figure 38-5
EIGRP Stub Router Configuration
Routed to WAN
Switch B
Switch C
145776
Switch A
Host A
Host B
Host C
When configuring the distribution router to send only a default route to the remote router, you must use
the ip classless global configuration command on the remote router. By default, the ip classless
command is enabled in all Cisco IOS images that support the EIGRP stub routing feature.
Without the stub feature, even after the routes that are sent from the distribution router to the remote
router have been filtered or summarized, a problem might occur. If a route is lost in the corporate
network, EIGRP sends a query to the distribution router, which in turn sends a query to the remote router
even if routes are being summarized. The EIGRP stub routing feature allows a network administrator to
prevent queries from being sent to the remote router.
Note
You should configure EIGRP stub routing only on stub routers. A stub router is a router connected to the
network core or the distribution layer through which core traffic should not flow. A stub router should
not have any EIGRP neighbors other than distribution routers. Ignoring this restriction causes
undesirable behavior.
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.
Configuring EIGRP Stub Routing
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-30
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring OSPF
Step 4
Command
Purpose
eigrp stub [receive-only | connected |
static | summary]
Configure a remote router as an EIGRP stub router. The keywords have
these meanings:
receive-only to set the router as a receive-only neighbor.
connected to advertise connected routes.
static to advertise static routes.
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.
Configuring OSPF
This section applies only to the Catalyst Switch Module 3110.
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, and point-to-point networks. The switch
supports broadcast (Ethernet, Token Ring, and FDDI) and point-to-point networks (Ethernet interfaces
configured as point-to-point links).
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 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, 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-31
Chapter 38
Configuring IP Unicast Routing
Configuring OSPF
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.
These sections contain this configuration information:
Note
Default OSPF Configuration, page 38-32
Configuring Basic OSPF Parameters, page 38-35
Configuring OSPF Interfaces, page 38-35
Configuring OSPF Area Parameters, page 38-36
Configuring Other OSPF Parameters, page 38-38
Changing LSA Group Pacing, page 38-39
Configuring a Loopback Interface, page 38-40
Monitoring OSPF, page 38-40
To enable OSPF, the switch or stack master must be running the IP services feature set.
Default OSPF Configuration
Table 38-6 shows the default OSPF configuration.
Table 38-6
Default OSPF Configuration
Feature
Default Setting
Interface parameters
Cost: No default cost predefined.
Resend interval: 5 seconds.
Send delay: 1 second.
Priority: 1.
Hello interval: 10 seconds.
Dead interval: 4 times the hello interval.
No authentication.
No password specified.
MD5 authentication disabled.
Area
Authentication type: 0 (no authentication).
Default cost: 1.
Range: Disabled.
Stub: No stub area defined.
NSSA: No NSSA area defined.
Auto cost
100 Mb/s.
Default-information originate
Disabled. When enabled, the default metric setting is 10, and the
external route type default is Type 2.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-32
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring OSPF
Table 38-6
Default OSPF Configuration (continued)
Feature
Default Setting
Default metric
Built-in, automatic metric translation, as appropriate for each
routing protocol.
Distance OSPF
dist1 (all routes within an area): 110.
dist2 (all routes from one area to another): 110.
dist3 (routes from other routing domains): 110.
OSPF database filter
Disabled. All outgoing link-state advertisements (LSAs) are
flooded to the interface.
IP OSPF name lookup
Disabled.
Log adjacency changes
Enabled.
Neighbor
None specified.
Neighbor database filter
Disabled. All outgoing LSAs are flooded to the neighbor.
Network area
Disabled.
NSF awareness
Enabled2. Allows Layer 3 switches to continue forwarding
packets from a neighboring NSF-capable router during hardware
or software changes.
NSF capability
Disabled.
Note
The switch stack supports OSPF NSF-capable routing
for IPv4.
Router ID
No OSPF routing process defined.
Summary address
Disabled.
Timers LSA group pacing
240 seconds.
Timers shortest path first (spf)
spf delay: 5 seconds.
spf-holdtime: 10 seconds.
Virtual link
No area ID or router ID defined.
Hello interval: 10 seconds.
Resend interval: 5 seconds.
Send delay: 1 second.
Dead interval: 40 seconds.
Authentication key: no key predefined.
Message-digest key (MD5): no key predefined.
1. NSF = nonstop forwarding.
2. OSPF NSF awareness is enabled for IPv4 on switches running the IP services feature set.
OSPF Nonstop Forwarding
The switch or switch stack supports two levels of nonstop forwarding (NSF):
OSPF NSF Awareness, page 38-34
OSPF NSF Capability, page 38-34
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-33
Chapter 38
Configuring IP Unicast Routing
Configuring OSPF
OSPF NSF Awareness
The IP-services feature set supports OSPF NSF awareness for IPv4. When the neighboring router is
NSF-capable, the Layer 3 switch continues to forward packets from the neighboring router during the
interval between the primary route processor in a router failure and the take-over of the backup route
processor, or while the primary route processor is manually reloaded for a nondisruptive software
upgrade.
This feature cannot be disabled. For more information on this feature, see the OSPF Nonstop
Forwarding (NSF) Awareness section of the Cisco IOS IP Routing Protocols Configuration Guide,
Release 12.4 at this URL:
http://www.cisco.com/en/US/products/ps6350/products_configuration_guide_chapter09186a00804557
a8.html
OSPF NSF Capability
The IP-services feature set also supports OSPF NSF-capable routing for IPv4 for better convergence and
lower traffic loss following a stack-master change. When a stack-master change occurs in an OSPF
NSF-capable stack, the new stack master must do two things to resynchronize its link-state database with
its OSFP neighbors:
Release the available OSPF neighbors on the network without resetting the neighbor relationship.
Re-acquire the contents of the link-state database for the network.
After a stack-master change, the new master sends an OSPF NSF signal to neighboring NSF-aware
devices. A device recognizes this signal to mean that it should not reset the neighbor relationship with
the stack. As the NSF-capable stack master receives signals from other routes on the network, it begins
to rebuild its neighbor list.
When the neighbor relationships are reestablished, the NSF-capable stack master resynchronizes its
database with its NSF-aware neighbors, and routing information is exchanged between the OSPF
neighbors. The new stack master uses this routing information to remove stale routes, to update the
routing information database (RIB), and to update the forwarding information base (FIB) with the new
information. The OSPF protocols then fully converge.
Note
OSPF NSF requires that all neighbor networking devices be NSF-aware. If an NSF-capable router
discovers non-NSF-aware neighbors on a network segment, it disables NSF capabilities for that segment.
Other network segments where all devices are NSF-aware or NSF-capable continue to provide NSF
capabilities.
Use the nsf OSPF routing configuration command to enable OSPF NSF routing. Use the show ip ospf
privileged EXEC command to verify that it is enabled.
For more information about this feature, see the Cisco Nonstop Forwarding Feature Overview at this
URL:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1829/products_feature_guide09186a00800ab7fc.
html
Note
NSF is not supported on interfaces configured for Hot Standby Router Protocol (HSRP).
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-34
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring OSPF
Configuring Basic OSPF Parameters
Enabling OSPF requires that you create an OSPF routing process, specify the range of IP addresses to
be associated with the routing process, and assign area IDs to be associated with that range.
Beginning in privileged EXEC mode, follow these steps to enable OSPF:
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 internal identification parameter that is locally
assigned and can be any positive integer. Each OSPF routing
process has a unique value.
Step 3
nsf
(Optional) Enable NSF operations for OSPF on a Catalyst
Switch Module 3110.
Step 4
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 more than one interface to be associated with
a specific OSPF area. The area ID can be a decimal value or an
IP address.
Step 5
end
Return to privileged EXEC mode.
Step 6
show ip protocols
Verify your entries.
Step 7
copy running-config startup-config
(Optional) Save your entries in the configuration file.
To end 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 ID of 109:
Switch(config)# router ospf 109
Switch(config-router)# network 131.108.0.0 255.255.255.0 area 24
Configuring OSPF Interfaces
You can use the ip ospf interface configuration commands to modify interface-specific OSPF
parameters. You are not required to modify any of these parameters, but some interface parameters (hello
interval, dead interval, and authentication key) must be consistent across all routers in an attached
network. If you modify these parameters, be sure all routers in the network have compatible values.
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) 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-35
Chapter 38
Configuring IP Unicast Routing
Configuring OSPF
Command
Purpose
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.
Step 6
ip ospf priority number
(Optional) Set priority to help find 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.
keyidAn identifier from 1 to 255.
keyAn 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 to all interfaces in the same area
except to 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.
Step 15
copy running-config startup-config
Options is 0x42This means the neighbor switch is not
NSF-aware.
(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.
Configuring OSPF Area Parameters
You can optionally configure several OSPF area parameters. These parameters include authentication for
password-based protection against unauthorized access to an area, stub areas, and not-so-stubby-areas
(NSSAs). Stub areas are areas into which information on external routes is not sent. Instead, the area
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-36
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring OSPF
border router (ABR) generates a default external route into the stub area for destinations outside the
autonomous system. An NSSA does not flood all LSAs from the core into the area, but can import
autonomous-system external routes within the area by redistribution.
Route summarization consolidates advertised addresses into a single summary route to be advertised by
other areas. If network numbers are contiguous, you can use the area range router configuration
command to configure the ABR to advertise a summary route that covers all networks in the range.
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]
[default-information-originate]
[no-summary]
(Optional) Defines an area as a NSSA. Every router within the same
area must agree that the area is an NSSA. Select one of these
keywords:
no-redistributionSelect 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-originateSelect an ABR to allow
importing type 7 LSAs into the NSSA.
no-redistributionSelect 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-37
Chapter 38
Configuring IP Unicast Routing
Configuring OSPF
Configuring Other OSPF Parameters
You can optionally configure other OSPF parameters from router configuration mode.
Route summarization: When redistributing routes from other protocols, as described in the Using
Route Maps to Redistribute Routing Information section on page 38-89, each route is advertised
individually in an external LSA. To help decrease the size of the OSPF link state database, you can
use the summary-address router configuration command to advertise a single router for all the
redistributed routes included in a specified network address and mask.
Virtual links: In OSPF, all areas must be connected to a backbone area. You can establish a virtual
link in case of a backbone-continuity break by configuring two ABRs as endpoints of a virtual link.
Configuration information includes the identity of the other virtual endpoint (the other ABR) and
the nonbackbone link that the two routers have in common (the transit area). Virtual links cannot be
configured through a stub area.
Default route: When you specifically configure redistribution of routes into an OSPF routing
domain, the route automatically becomes an autonomous system boundary router (ASBR). You can
force the ASBR to generate a default route into the OSPF routing domain.
Domain name server (DNS) names for use in all OSPF show privileged EXEC command displays
makes it easier to identify a router than displaying it by router ID or neighbor ID.
Default metrics: OSPF calculates the OSPF metric for an interface according to the bandwidth of
the interface. The metric is calculated as ref-bw divided by bandwidth, where ref is 10 by default,
and bandwidth (bw) is specified by the bandwidth interface configuration command. For multiple
links with high bandwidth, you can specify a larger number to differentiate the cost on those links.
Administrative distance is a rating of the trustworthiness of a routing information source, an integer
between 0 and 255, with a higher value meaning a lower trust rating. An administrative distance of
255 means the routing information source cannot be trusted at all and should be ignored. OSPF uses
three different administrative distances: routes within an area (intra-area), routes to another area
(interarea), and routes from another routing domain learned through redistribution (external). You
can change any of the distance values.
Passive interfaces: Because interfaces between two devices on an Ethernet represent only one
network segment, to prevent OSPF from sending hello packets for the sending interface, you must
configure the sending device to be a passive interface. Both devices can identify each other through
the hello packet for the receiving interface.
Route calculation timers: You can configure the delay time between when OSPF receives a topology
change and when it starts the shortest path first (SPF) calculation and the hold time between two
SPF calculations.
Log neighbor changes: You can configure the router to send a syslog message when an OSPF
neighbor state changes, providing a high-level view of changes in the router.
Beginning in privileged EXEC mode, follow these steps to configure these OSPF 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
summary-address address mask
(Optional) Specify an address and IP subnet mask for redistributed
routes so that only one summary route is advertised.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-38
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring OSPF
Command
Purpose
Step 4
area area-id virtual-link router-id
[hello-interval seconds]
[retransmit-interval seconds] [trans]
[[authentication-key key] |
message-digest-key keyid md5 key]]
(Optional) Establish a virtual link, and set its parameters. See the
Configuring OSPF Interfaces section on page 38-35 for parameter
definitions and Table 38-6 on page 38-32 for virtual link defaults.
Step 5
default-information originate [always]
[metric metric-value] [metric-type
type-value] [route-map map-name]
(Optional) Force the ASBR to generate a default route into the OSPF
routing domain. Parameters are all optional.
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 is
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 range is 1 to 255.
dist2] [external dist3]}
The default distance for each type of route is 110.
Step 9
passive-interface type number
(Optional) Suppress the sending of hello packets through the
specified interface.
Step 10
timers throttle spf spf-delay spf-holdtime
spf-wait
(Optional) Configure route calculation timers.
spf-delayDelay between receiving a change to SPF
calculation. The range is from 1 to 600000 miliseconds.
spf-holdtimeDelay between first and second SPF calculation.
The range is from 1 to 600000 in milliseconds.
spf-waitMaximum wait time in milliseconds for SPF
calculations. The range is from 1 to 600000 in milliseconds.
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 the Monitoring
OSPF section on page 38-40.
Step 14
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Changing LSA Group Pacing
The OSPF LSA group pacing feature allows the router to group OSPF LSAs and pace the refreshing,
check-summing, and aging functions for more efficient router use. This feature is enabled by default with
a 4-minute default pacing interval, and you will not usually need to modify this parameter. The optimum
group pacing interval is inversely proportional to the number of LSAs that the router is refreshing,
check-summing, and aging. For example, if you have approximately 10,000 LSAs in the database,
decreasing the pacing interval would benefit you. If you have a very small database (40 to 100 LSAs),
increasing the pacing interval to 10 to 20 minutes might benefit you slightly.
Beginning in privileged EXEC mode, follow these steps to configure OSPF LSA pacing:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
router ospf process-id
Enable OSPF routing, and enter router configuration mode.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-39
Chapter 38
Configuring IP Unicast Routing
Configuring OSPF
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.
Configuring a Loopback Interface
OSPF uses the highest IP address configured on the interfaces as its router ID. If this interface is down
or removed, the OSPF process must recalculate a new router ID and resend all its routing information
through its interfaces. If a loopback interface is configured with an IP address, OSPF uses this IP address
as its router ID, even if other interfaces have higher IP addresses. Loopback interfaces never fail, which
provides greater stability. OSPF automatically prefers a loopback interface over other interfaces, and it
chooses the highest IP address among all loopback interfaces.
Beginning in privileged EXEC mode, follow these steps to configure a loopback interface:
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-40
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring EIGRP
Table 38-7 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.
Table 38-7
Show IP OSPF Statistics Commands
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
This section applies only to the Catalyst Switch Module 3110.
Note
If the switch is running the IP base image, you can configure complete EIGRP routing. However, the
configuration is not implemented because the IP base image supports only EIGRP stub routing.
After you have entered the eigrp stub router configuration command, only the eigrp stub connected
summary command takes effect. Although the CLI help might show the receive-only and static
keywords, and you can enter these keywords, the switch running the IP base image always behaves as if
the connected and summary keywords were configured.
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. All
devices involved in a topology change can synchronize at the same time. Routers that are not affected by
topology changes are not involved in recomputations.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-41
Chapter 38
Configuring IP Unicast Routing
Configuring EIGRP
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
network expansion 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 increments
as usual.
EIGRP offers these features:
Fast convergence.
Incremental updates when the state of a destination changes rather than 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.
Scalable for large networks.
EIGRP has these four basic components:
Neighbor discovery and recovery is the process that routers use to dynamically learn of other routers
on their directly attached networks. Routers must also discover when their neighbors become
unreachable or inoperative. Neighbor discovery and recovery is achieved by periodically sending
small hello packets. As long as hello packets are received, the Cisco IOS software learns that a
neighbor is alive and functioning. When this status is determined, the neighboring routers can
exchange routing information.
The reliable transport protocol is responsible for guaranteed, ordered delivery of EIGRP packets to
all neighbors. It supports intermixed transmission of multicast and unicast packets. Some EIGRP
packets must be sent reliably, and others need not be. For efficiency, reliability is provided only
when necessary. For example, on a multi-access network with multicast capabilities (such as
Ethernet), it is not necessary to send hellos reliably to all neighbors individually. Therefore, EIGRP
sends a single multicast hello with an indication in the packet informing the receivers that the packet
need not be acknowledged. Other types of packets (such as updates) require acknowledgment, which
is shown in the packet. The reliable transport has a provision to send multicast packets quickly when
there are unacknowledged packets pending. Doing so helps ensure that convergence time remains
low in the presence of varying speed links.
The DUAL finite state machine embodies the decision process for all route computations. It tracks
all routes advertised by all neighbors. DUAL uses the distance information (known as a metric) to
select efficient, loop-free paths. DUAL selects routes to be inserted into a routing table based on
feasible successors. A successor is a neighboring router used for packet forwarding that has a
least-cost path to a destination that is guaranteed not to be part of a routing loop. When there are no
feasible successors, but there are neighbors advertising the destination, a recomputation occurs. This
is the process whereby a new successor is determined. The amount of time it takes to recompute the
route affects the convergence time. Recomputation is processor-intensive; it is advantageous to
avoid recomputation if it is not necessary. When a topology change occurs, DUAL tests for feasible
successors. If there are feasible successors, it uses any it finds to avoid unnecessary recomputation.
The protocol-dependent modules are responsible for network layer protocol-specific tasks. An
example is the IP EIGRP module, which is responsible for sending and receiving EIGRP packets
that are encapsulated in IP. It is also responsible for parsing EIGRP packets and informing DUAL
of the new information received. EIGRP uses DUAL for routing decisions, but the results are stored
in the IP routing table. EIGRP is also responsible for redistributing routes learned by other IP
routing protocols.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-42
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring EIGRP
These sections contain this configuration information:
Default EIGRP Configuration, page 38-43
Configuring Basic EIGRP Parameters, page 38-45
Configuring EIGRP Interfaces, page 38-46
Configuring EIGRP Route Authentication, page 38-47
Monitoring and Maintaining EIGRP, page 38-48
For information about EIGRP stub routing, see the Understanding EIGRP Stub Routing section on
page 38-29 and the Configuring EIGRP Stub Routing section on page 38-30.
Note
To enable EIGRP, the switch or stack master must be running the IP services feature set.
Default EIGRP Configuration
Table 38-8 shows the default EIGRP configuration.
Table 38-8
Default EIGRP Configuration
Feature
Default Setting
Auto summary
Enabled. Subprefixes are summarized to the classful network
boundary when crossing classful network boundaries.
Default-information
Exterior routes are accepted, and default information is passed
between EIGRP processes during redistribution.
Default metric
Only connected routes and interface static routes can be redistributed
without a default metric. The metric includes:
Distance
Bandwidth: 0 or greater kb/s.
Delay (tens of microseconds): 0 or any positive number that is a
multiple of 39.1 nanoseconds.
Reliability: any number between 0 and 255 (255 means
100 percent reliability).
Loading: effective bandwidth as a number between 0 and 255
(255 is 100 percent loading).
MTU: maximum transmission unit size of the route in bytes. 0 or
any positive integer.
Internal distance: 90.
External distance: 170.
EIGRP log-neighbor changes
Disabled. No adjacency changes logged.
IP authentication key-chain
No authentication provided.
IP authentication mode
No authentication provided.
IP bandwidth-percent
50 percent.
IP hello interval
For low-speed nonbroadcast multiaccess (NBMA) networks:
60 seconds; all other networks: 5 seconds.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-43
Chapter 38
Configuring IP Unicast Routing
Configuring EIGRP
Table 38-8
Default EIGRP Configuration (continued)
Feature
Default Setting
IP hold-time
For low-speed NBMA networks: 180 seconds; all other networks:
15 seconds.
IP split-horizon
Enabled.
IP summary address
No summary aggregate addresses are predefined.
Metric weights
tos: 0; k1 and k3: 1; k2, k4, and k5: 0
Network
None specified.
NSF awareness
Enabled2. Allows Layer 3 switches to continue forwarding packets
from a neighboring NSF-capable router during hardware or software
changes.
NSF capability
Disabled.
Note
The switch supports EIGRP NSF-capable routing for IPv4.
Offset-list
Disabled.
Router EIGRP
Disabled.
Set metric
No metric set in the route map.
Traffic-share
Distributed proportionately to the ratios of the metrics.
Variance
1 (equal-cost load-balancing).
1. NSF = nonstop forwarding
2. EIGRP NSF awareness is enabled for IPv4 on switches running the IP services feature set.
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.
If you have routers on your network that are configured for IGRP, and you want to change to EIGRP, you
must designate transition routers configured with both IGRP and EIGRP. In these cases, perform Steps
1 through 3 in the next section and also see the Configuring Split Horizon section on page 38-26. You
must use the same autonomous-system number for routes so that they are automatically redistributed.
EIGRP Nonstop Forwarding
The switch stack supports two levels of EIGRP nonstop forwarding:
EIGRP NSF Awareness, page 38-44
EIGRP NSF Capability, page 38-45
EIGRP NSF Awareness
The IP-services feature set supports EIGRP NSF awareness for IPv4. When the neighboring router is
NSF-capable, the Layer 3 switch continues to forward packets from the neighboring router during the
interval between the primary route processor in a router failure and the backup RP take-over, or while
you manually reload the primary route processor for a nondisruptive software upgrade.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-44
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring EIGRP
This feature cannot be disabled. For more information on this feature, see the EIGRP Nonstop
Forwarding (NSF) Awareness section of the Cisco IOS IP Routing Protocols Configuration Guide,
Release 12.4 at this URL:
http://www.cisco.com/en/US/products/ps6350/products_configuration_guide_chapter09186a00804529
72.html
EIGRP NSF Capability
The IP-services feature set also supports EIGRP NSF-capable routing for IPv4 for better convergence
and lower traffic loss following a stack-master change. When an EIGRP NSF-capable stack master
restarts or a new stack master starts and NSF restarts, the switch has no neighbors, and the topology table
is empty. The switch must bring up the interfaces, re-acquire neighbors, and rebuild the topology and
routing tables without interrupting the traffic directed to the switch stack. EIGRP peer routers maintain
the routes learned from the new stack master and continue to forward traffic through the NSF restart
process.
To prevent an adjacency reset by the neighbors, the new stack master uses a new restart bit in the EIGRP
packet header. When the neighbor receives it, it synchronizes the stack in its peer list and maintains the
adjacency with the stack. The neighbor then sends its topology table to the stack master with the restart
bit set to show that it is NSF-aware and is aiding the new stack master.
If at least one of the stack peer neighbors is NSF-aware, the stack master receives updates and rebuilds
its database. Each NSF-aware neighbor sends an end-of-table (EOT) marker in the last update packet to
mark the end of the table content. The stack master recognizes the convergence when it receives the EOT
marker and begins sending updates. When the stack master has received all EOT markers from its
neighbors or when the NSF converge timer expires, EIGRP notifies the routing information database
(RIB) of convergence and floods its topology table to all NSF-aware peers.
Note
NSF is not supported on interfaces configured for Hot Standby Router Protocol (HSRP).
Use the nsf EIGRP routing configuration command to enable EIGRP NSF routing. Use the show ip
protocols privileged EXEC command to verify that NSF is enabled. See the command reference for this
release for information about the nsf command.
Configuring Basic EIGRP Parameters
Beginning in privileged EXEC mode, follow these steps to configure EIGRP. Configuring the routing
process is required; other steps are optional:
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 autonomous-system number identifies the routes to
other EIGRP routers and tags routing information.
Step 3
nsf
(Optional) Enable EIGRP NSF. Enter this command on the stack
master and on all of its peers.
Step 4
network network-number
Associate networks with an EIGRP routing process. EIGRP sends
updates to the interfaces in the specified networks.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-45
Chapter 38
Configuring IP Unicast Routing
Configuring EIGRP
Command
Purpose
Step 5
eigrp log-neighbor-changes
(Optional) Enable logging of EIGRP neighbor changes to monitor
routing system stability.
Step 6
metric weights tos k1 k2 k3 k4 k5
(Optional) Adjust the EIGRP metric. Although the defaults have
been carefully set to provide excellent operation in most networks,
you can adjust them.
Caution
Setting metrics is complex, and we do not recommend
doing without guidance from an experienced network
designer.
Step 7
offset list [access-list number | name] {in | out} (Optional) Apply an offset list to routing metrics to increase
offset [type number]
incoming and outgoing metrics to routes learned through EIGRP.
You can limit the offset list with an access list or an interface.
Step 8
no auto-summary
(Optional) Disable automatic summarization of subnet routes into
network-level routes.
Step 9
ip summary-address eigrp
autonomous-system-number address mask
(Optional) Configure a summary aggregate.
Step 10
end
Return to privileged EXEC mode.
Step 11
show ip protocols
Verify your entries.
Step 12
show ip protocols
Verify your entries.
For NSF awareness, the output shows:
*** IP Routing is NSF aware ***
EIGRP NSF enabled
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.
Configuring EIGRP Interfaces
Other optional EIGRP parameters can be configured on an interface basis.
Beginning in privileged EXEC mode, follow these steps to configure EIGRP interfaces:
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
autonomous-system-number address mask
(Optional) Configure a summary aggregate address for a
specified interface (not usually necessary if auto-summary is
enabled).
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-46
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring EIGRP
Command
Purpose
Step 5
ip hello-interval eigrp autonomous-system-number
seconds
(Optional) Change the hello-time interval for an EIGRP
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
seconds
(Optional) Change the hold-time interval for an EIGRP
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.
Caution
Do not adjust the hold time without consulting
Cisco technical support.
Step 7
no ip split-horizon eigrp autonomous-system-number (Optional) Disable split horizon to allow route information
to be advertised by a router from any interface that
originated that information.
Step 8
end
Return to privileged EXEC mode.
Step 9
show ip eigrp interface
Display which interfaces EIGRP is active on and
information about EIGRP relating to those interfaces.
Step 10
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.
Configuring EIGRP Route Authentication
EIGRP route authentication provides MD5 authentication of routing updates from the EIGRP routing
protocol to prevent the introduction of unauthorized or false routing messages from unapproved sources.
Beginning in privileged EXEC mode, follow these steps to enable authentication:
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
key-chain
Enable authentication of IP EIGRP packets.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-47
Chapter 38
Configuring IP Unicast Routing
Configuring EIGRP
Command
Step 9
Purpose
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
seconds}
(Optional) Specify the time period during which the key
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.
Monitoring and Maintaining EIGRP
You can delete neighbors from the neighbor table. You can also display various EIGRP routing statistics.
Table 38-9 lists the privileged EXEC commands for deleting neighbors and displaying statistics. For
explanations of fields in the resulting display, see the Cisco IOS IP Command Reference, Volume 2 of 3:
Routing Protocols, Release 12.2.
Table 38-9
IP EIGRP Clear and Show Commands
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] |
[[ip-address] mask]]
Display the EIGRP topology table for a given process.
show ip eigrp traffic [autonomous-system-number]
Display the number of packets sent and received for all or a
specified EIGRP process.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-48
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring BGP
Configuring BGP
This section applies only to the Catalyst Switch Module 3110.
The Border Gateway Protocol (BGP) is an exterior gateway protocol for an interdomain routing system
that guarantees the loop-free exchange of routing information between autonomous systems.
Autonomous systems are made up of routers operating under the same administration and run Interior
Gateway Protocols (IGPs), such as RIP or OSPF, within their boundaries and interconnecting by using
an Exterior Gateway Protocol (EGP). BGP Version 4 is the standard EGP for interdomain routing in the
Internet. You can find detailed information about BGP in Internet Routing Architectures, published by
Cisco Press, and in the Configuring BGP chapter in the Cisco IP and IP Routing Configuration Guide.
For details about BGP commands and keywords, see the IP Routing Protocols part of 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 C, Unsupported Commands in
Cisco IOS Release 12.2(40)EX2.
Routers belonging to the same autonomous system and exchanging BGP updates run internal BGP
(IBGP). Routers belonging to different autonomous systems and exchanging 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 autonomous system (IBGP). Figure 38-6 shows a network that is running both EBGP and
IBGP.
AS 100
EBGP, IBGP, and Multiple Autonomous Systems
Router A
129.213.1.2
192.208.10.1
EBGP
EBGP
129.213.1.1
Router B
175.220.212.1
AS 300
Router D
192.208.10.2
IBGP
Router C
175.220.1.2
AS 200
74775
Figure 38-6
Before exchanging information with an external autonomous system, BGP ensures that networks in the
autonomous system can be reached by defining internal BGP peering among routers and by
redistributing BGP routing information to IGPs that run in the autonomous system, 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 are known as peers or neighbors. In Figure 38-6, 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 autonomous-system numbers that describe the full path to the destination network. BGP uses this
information to construct a loop-free map of autonomous systems.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-49
Chapter 38
Configuring IP Unicast Routing
Configuring BGP
The network has these characteristics:
Routers A and B are running EBGP, and Routers B and C are running IBGP. Note that the EBGP
peers are directly connected and that the IBGP peers are not. As long as an IGP allows the two
neighbors to reach one another, IBGP peers do not have to be directly connected.
All BGP speakers within an autonomous system must establish a peer relationship. That is, the BGP
speakers within an autonomous system must have a logical full mesh. However, BGP4 provides
techniques to reduce the requirement for a logical full mesh: confederations and route reflectors.
Autonomous system AS 200 is a transit autonomous system for AS 100 and AS 300that is, AS 200
transfers packets between AS 100 and AS 300.
BGP peers first exchange their full BGP routing tables and then send only incremental updates. BGP
peers also exchange keepalive messages (to ensure that the connection is up) and notification messages
(in response to errors or special conditions).
In BGP, each route consists of a network number, a list of autonomous systems that information has
passed through (the autonomous system path), and a list of other path attributes. The primary function
of a BGP system is to exchange network reachability information, including information about the list
of autonomous-system paths, with other BGP systems. This information determines autonomous-system
connectivity, to prune routing loops, and to enforce autonomous-system-level policy decisions.
A router or switch running Cisco IOS does not select or use an IBGP route unless it has a route available
to the next-hop router and it has received synchronization from an IGP (unless IGP synchronization is
disabled). When multiple routes are available, BGP bases its path selection on attribute values. See the
Configuring BGP Decision Attributes section on page 38-57 for information about BGP attributes.
BGP Version 4 supports classless interdomain routing (CIDR), so you can reduce the size of your routing
tables by creating aggregate routes, resulting in supernets. CIDR eliminates the network classes within
BGP and supports the advertising of IP prefixes.
These sections contain this configuration information:
Default BGP Configuration, page 38-51
Enabling BGP Routing, page 38-53
Managing Routing Policy Changes, page 38-56
Configuring BGP Decision Attributes, page 38-57
Configuring BGP Filtering with Route Maps, page 38-59
Configuring BGP Filtering by Neighbor, page 38-60
Configuring Prefix Lists for BGP Filtering, page 38-61
Configuring BGP Community Filtering, page 38-62
Configuring BGP Neighbors and Peer Groups, page 38-64
Configuring Aggregate Addresses, page 38-66
Configuring Routing Domain Confederations, page 38-66
Configuring BGP Route Reflectors, page 38-67
Configuring Route Dampening, page 38-68
Monitoring and Maintaining BGP, page 38-69
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-50
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring BGP
For detailed descriptions of BGP configuration, see the Configuring BGP chapter in the IP Routing
Protocols part of 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.
For a list of BGP commands that are visible but not supported by the switch, see Appendix C,
Unsupported Commands in Cisco IOS Release 12.2(40)EX2.
Default BGP Configuration
Table 38-10 shows the default BGP configuration. For the defaults for all characteristics, see the specific
commands in the Cisco IOS IP Command Reference, Volume 2 of 3: Routing Protocols, Release 12.2.
Table 38-10
Default BGP Configuration
Feature
Default Setting
Aggregate address
Disabled: None defined.
Autonomous-system path access
list
None defined.
Auto summary
Enabled.
Best path
BGP community list
BGP confederation identifier/peers
The router considers as-path in choosing a route and does not compare similar
routes from external BGP peers.
Compare router ID: Disabled.
Number: None defined. When you permit a value for the community number, the
list defaults to an implicit deny for everything else that has not been permitted.
Format: Cisco IOS default format (32-bit number).
Identifier: None configured.
Peers: None identified.
BGP fast external fallover
Enabled.
BGP local preference
100. The range is 0 to 4294967295 with the higher value preferred.
BGP network
None specified; no backdoor route advertised.
BGP route dampening
Disabled by default. When enabled:
BGP router ID
Half-life is 15 minutes.
Re-use is 750 (10-second increments).
Suppress is 2000 (10-second increments).
Max-suppress-time is 4 times half-life; 60 minutes.
The IP address of a loopback interface if one is configured or the highest IP address
configured for a physical interface on the router.
Default information originate
Disabled.
(protocol or network redistribution)
Default metric
Distance
Built-in, automatic metric translations.
External route administrative distance: 20 (acceptable values are from 1 to 255).
Internal route administrative distance: 200 (acceptable values are from 1 to 255).
Local route administrative distance: 200 (acceptable values are from 1 to 255).
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-51
Chapter 38
Configuring IP Unicast Routing
Configuring BGP
Table 38-10
Default BGP Configuration (continued)
Feature
Default Setting
Distribute list
In (filter networks received in updates): Disabled.
Out (suppress networks from being advertised in updates): Disabled.
Internal route redistribution
Disabled.
IP prefix list
None defined.
Multi-exit discriminator (MED)
Neighbor
Always compare: Disabled. Does not compare MEDs for paths from neighbors in
different autonomous systems.
Best-path compare: Disabled.
MED missing as worst path: Disabled.
Deterministic MED comparison is disabled.
Advertisement interval: 30 seconds for external peers; 5 seconds for internal peers.
Change logging: Enabled.
Conditional advertisement: Disabled.
Default originate: No default route is sent to the neighbor.
Description: None.
Distribute list: None defined.
External BGP multihop: Only directly connected neighbors are allowed.
Filter list: None used.
Maximum number of prefixes received: No limit.
Next hop (router as next hop for BGP neighbor): Disabled.
Password: Disabled.
Peer group: None defined; no members assigned.
Prefix list: None specified.
Remote autonomous system (add entry to neighbor BGP table): No peers defined.
Private autonomous system number removal: Disabled.
Route maps: None applied to a peer.
Send community attributes: None sent to neighbors.
Shutdown or soft reconfiguration: Not enabled.
Timers: keepalive: 60 seconds; holdtime: 180 seconds.
Update source: Best local address.
Version: BGP Version 4.
Weight: Routes learned through BGP peer: 0; routes sourced by the local router:
32768.
NSF1 awareness
Disabled2. Allows Layer 3 switches to continue forwarding packets from a neighboring
NSF-capable router during hardware or software changes.
Route reflector
None configured.
Synchronization (BGP and IGP)
Enabled.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-52
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring BGP
Table 38-10
Default BGP Configuration (continued)
Feature
Default Setting
Table map update
Disabled.
Timers
Keepalive: 60 seconds; holdtime: 180 seconds.
1. NSF = nonstop forwarding.
2. NSF awareness can be enabled for IPv4 on switches with the IP services feature set by enabling graceful restart.
Nonstop Forwarding Awareness
The BGP NSF awareness feature is supported for IPv4 in the IP services feature set. To enable this
feature with BGP routing, you need to enable graceful restart. When the neighboring router is
NSF-capable, and this feature is enabled, the Layer 3 switch continues to forward packets from the
neighboring router during the interval between the primary route processor in a router failure and the
backup route processor take-over, or while you manually reload the primary route processor for a
nondisruptive software upgrade.
For more information, see the BGP Nonstop Forwarding (NSF) Awareness section of the Cisco IOS
IP Routing Protocols Configuration Guide, Release 12.4 at this URL:
http://www.cisco.com/en/US/products/ps6350/products_configuration_guide_chapter09186a00804556
8e.html
Enabling BGP Routing
To enable BGP routing, you establish a BGP routing process and define the local network. Because BGP
must fully recognize the relationships with its neighbors, you must also specify a BGP neighbor.
BGP supports two kinds of neighbors: internal and external. Internal neighbors are in the same
autonomous system; external neighbors are in different autonomous systems. External neighbors are
usually adjacent to each other and share a subnet, but internal neighbors can be anywhere in the same
autonomous system.
The switch supports the use of private autonomous-system numbers, usually assigned by service
providers and given to systems whose routes are not advertised to external neighbors. The private
autonomous-system numbers are from 64512 to 65535. You can configure external neighbors to remove
private autonomous-system numbers from the autonomous-system path by using the neighbor
remove-private-as router configuration command. Then when an update is passed to an external
neighbor, if the autonomous-system path includes any private autonomous-system numbers, these
numbers are dropped.
If your autonomous system will be passing traffic through it from another autonomous system to a third
autonomous system, it is important to be consistent about the routes it advertises. If BGP advertised a
route before all routers in the network learned about the route through the IGP, the autonomous system
might receive traffic that some routers could not yet route. Therefore, BGP must wait until the IGP has
propagated information across the autonomous system so that BGP synchronizes with the IGP.
Synchronization is enabled by default. If your autonomous system does not pass traffic from one
autonomous system to another autonomous system, or if all routers in your autonomous systems are
running BGP, you can disable synchronization, which allows your network to carry fewer routes in the
IGP and allows BGP to converge more quickly.
Note
To enable BGP, the switch or stack master must be running the IP services feature set.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-53
Chapter 38
Configuring IP Unicast Routing
Configuring BGP
Beginning in privileged EXEC mode, follow these steps to enable BGP routing, establish a BGP routing
process, and specify a neighbor:
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
autonomous-system number, and enter router configuration
mode. The autonomous-system number can be from 1 to
65535, with 64512 to 65535 designated as private autonomous
numbers.
Step 4
network network-number [mask network-mask]
[route-map route-map-name]
Configure a network as local to this autonomous system, and
enter it in the BGP table.
Step 5
neighbor {ip-address | peer-group-name}
remote-as number
Add an entry to the BGP neighbor table specifying that the
neighbor identified by the IP address belongs to the specified
autonomous system.
EBGP neighbors are usually directly connected, and the IP
address is the interface address 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}
remove-private-as
(Optional) Remove private autonomous-system numbers from
the autonomous-system path in 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-54
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring BGP
Step 12
Command
Purpose
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
If NSF awareness is enabled on the switch, but not on the
neighbor, this message appears:
Graceful Restart Capability: advertised
Step 13
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Use the no router bgp autonomous-system global configuration command to remove a BGP autonomous
system. 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 autonomous-system 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 38-6.
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
BGP neighbor is 129.213.1.1, remote AS 200, external link
BGP version 4, remote router ID 175.220.212.1
BGP state = established, table version = 3, up for 0:10:59
Last read 0:00:29, hold time is 180, keepalive interval is 60 seconds
Minimum time between advertisement runs is 30 seconds
Received 2828 messages, 0 notifications, 0 in queue
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-55
Chapter 38
Configuring IP Unicast Routing
Configuring BGP
Sent 2826 messages, 0 notifications, 0 in queue
Connections established 11; dropped 10
Anything other than BGP 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 specify where to send updates.
For detailed descriptions of BGP configuration, see the IP Routing Protocols part of 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 C, Unsupported
Commands in Cisco IOS Release 12.2(40)EX2, for a list of BGP commands that are visible but not
supported by the switch.
Managing Routing Policy Changes
Routing policies for a peer include all the configurations that might affect inbound or outbound routing
table updates. When you have defined two routers as BGP neighbors, they form a BGP connection and
exchange routing information. If you later change a BGP filter, weight, distance, version, or timer, or
make a similar configuration change, you must reset the BGP sessions so that the configuration changes
take effect.
There are two types of reset, hard reset and soft reset. Cisco IOS Releases 12.1 and later support a soft
reset without any prior configuration. To use a soft reset without preconfiguration, both BGP peers must
support the soft-route refresh capability, which is advertised in the OPEN message sent when the peers
establish a TCP session. A soft reset allows the dynamic exchange of route refresh requests and routing
information between BGP routers and the subsequent re-advertisement of the respective outbound
routing table.
When soft reset generates inbound updates from a neighbor, it is called dynamic inbound soft reset.
When soft reset sends a set of updates to a neighbor, it is called outbound soft reset.
A soft inbound reset causes the new inbound policy to take effect. A soft outbound reset causes the new
local outbound policy to take effect without resetting the BGP session. As a new set of updates is sent
during outbound policy reset, a new inbound policy can also take effect.
Table 38-11 lists the advantages and disadvantages hard reset and soft reset.
Table 38-11
Advantages and Disadvantages of Hard and Soft Resets
Type of Reset
Advantages
Disadvantages
Hard reset
No memory overhead
The prefixes in the BGP, IP, and FIB tables
provided by the neighbor are lost. Not
recommended.
Outbound soft reset
No configuration, no storing of routing table
updates
Does not reset inbound routing table updates.
Dynamic inbound soft reset Does not clear the BGP session and cache
Both BGP routers must support the route
Does not require storing of routing table updates refresh capability (in Cisco IOS Release 12.1
and later).
and has no memory overhead
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-56
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring BGP
Beginning in privileged EXEC mode, follow these steps to learn if a BGP peer supports the route-refresh
capability and to reset the BGP session:
Step 1
Command
Purpose
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
Step 3
Step 4
clear ip bgp {* | address |
peer-group-name}
clear ip bgp {* | address |
peer-group-name} soft out
show ip bgp
show ip bgp neighbors
Reset the routing table on the specified connection.
Enter an asterisk (*) to reset all connections.
Enter an IP address to reset a specific connection.
Enter a peer group name to reset the peer group.
(Optional) Perform an outbound soft reset to reset the inbound routing table on the
specified connection. Use this command if route refresh is supported.
Enter an asterisk (*) to reset all connections.
Enter an IP address to reset a specific connection.
Enter a peer group name to reset the peer group.
Verify the reset by reviewing the routing table information and BGP neighbor
information.
Configuring BGP Decision Attributes
When a BGP speaker receives updates from multiple autonomous systems that describe different paths
to the same destination, it must choose the single best path for reaching that destination. The selected
path is then entered in the BGP routing table and propagated to its neighbors. The decision is based on
the value of attributes that the update contains and other BGP-configurable factors.
When a BGP peer learns two EBGP paths for a prefix from a neighboring autonomous system, it chooses
the best path and inserts that path in the IP routing table. If BGP multipath support is enabled and the
EBGP paths are learned from the same neighboring autonomous systems, instead of a single best path,
multiple paths are entered in the IP routing table. Then, during packet switching, per-packet or
per-destination load-balancing is performed among the multiple paths. The maximum-paths router
configuration command controls the number of paths allowed.
These factors summarize the order in which BGP evaluates the attributes for choosing the best path:
1.
If the path specifies a next hop that is inaccessible, drop the update. The BGP next-hop attribute,
automatically determined by the software, is the IP address of the next hop to be used to reach a
destination. For EBGP, this is usually the IP address of the neighbor specified by the neighbor
remote-as router configuration command. You can disable next-hop processing by using route maps
or the neighbor next-hop-self router configuration command.
2.
Prefer the path with the largest weight (a Cisco-proprietary parameter). The weight attribute is local
to the router and not propagated in routing updates. By default, the weight attribute is 32768 for
paths that the router originates and zero for other paths. Routes with the largest weight are preferred.
You can use access lists, route maps, or the neighbor weight router configuration command to set
weights.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-57
Chapter 38
Configuring IP Unicast Routing
Configuring BGP
3.
Prefer the route with the highest local preference. Local preference is part of the routing update and
is exchanged among routers in the same autonomous system. The default value of the local
preference attribute is 100. You can set local preference by using the bgp default local-preference
router configuration command or by using a route map.
4.
Prefer the route that was originated by BGP running on the local router.
5.
Prefer the route with the shortest autonomous-system path.
6.
Prefer the route with the lowest origin type. An interior route or IGP is lower than a route learned
by EGP, and an EGP-learned route is lower than one of unknown origin or learned in another way.
7.
Prefer the route with the lowest multi-exit discriminator (MED) metric attribute if the neighboring
autonomous system is the same for all routes considered. You can configure the MED by using route
maps or by using the default-metric router configuration command. When an update is sent to an
IBGP peer, the MED is included.
8.
Prefer the external (EBGP) path over the internal (IBGP) path.
9.
Prefer the route that can be reached through the closest IGP neighbor (the lowest IGP metric). This
means that the router prefers the shortest internal path within the autonomous system to reach the
destination (the shortest path to the BGP next hop).
10. If these 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
autonomous-system number, and enter router
configuration mode.
Step 3
bgp best-path as-path ignore
(Optional) Configure the router to ignore
autonomous-system 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
weight
(Optional) Assign a weight to a neighbor connection.
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 are also set
to this value. The range is 1 to 4294967295. The lowest
value is the most desirable.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-58
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring BGP
Command
Purpose
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 autonomous system.
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 autonomous system.
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 16. Having
multiple paths allows load-balancing among the paths.
(Although the switch software allows a maximum of
32 equal-cost routes, the switch hardware never uses more
than 16 paths per route.)
Step 13
end
Return to privileged EXEC mode.
Step 14
show ip bgp
show ip bgp neighbors
Verify the reset by reviewing routing table information
and BGP neighbor information.
Step 15
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Use the no form of each command to return to the default state.
Configuring BGP Filtering with Route Maps
Within BGP, route maps can control and modify routing information and t define the conditions by which
routes are redistributed between routing domains. See the Using Route Maps to Redistribute Routing
Information section on page 38-89 for more information about route maps. Each route map has a name
that identifies the it (map tag) and an optional sequence number.
Beginning in privileged EXEC mode, follow these steps to use a route map to disable next-hop
processing:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
route-map map-tag [[permit | deny] |
sequence-number]]
Create a route map, and enter route-map configuration mode.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-59
Chapter 38
Configuring IP Unicast Routing
Configuring BGP
Step 3
Command
Purpose
set ip next-hop ip-address [...ip-address]
[peer-address]
(Optional) Set a route map to disable next-hop processing
In an inbound route map, set the next hop of matching routes as
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.
Configuring BGP Filtering by Neighbor
You can filter BGP advertisements by using autonomous-system-path filters, such as the as-path
access-list global configuration command and the neighbor filter-list router configuration command.
You can also use access lists with the neighbor distribute-list router configuration command.
Distribute-list filters are applied to network numbers. See the Controlling Advertising and Processing
in Routing Updates section on page 38-98 for information about the distribute-list command.
You can use route maps on a per-neighbor basis to filter updates and to modify various attributes. You
can apply a route map to either inbound or outbound updates. Only the routes that pass the route map
are sent or accepted in updates. On both inbound and outbound updates, matching is supported based on
autonomous-system path, community, and network numbers. Autonomous-system-path matching
requires the match as-path access-list route-map command, community-based matching requires the
match community-list route-map command, and network-based matching requires the ip access-list
global configuration command.
Beginning in privileged EXEC mode, follow these steps to apply a per-neighbor route map:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
router bgp autonomous-system
Enable a BGP routing process, assign it an autonomous-system
number, and enter router configuration mode.
Step 3
neighbor {ip-address | peer-group name}
distribute-list {access-list-number | name}
{in | out}
(Optional) Filter BGP routing updates to or from neighbors as
specified in an access list.
Step 4
neighbor {ip-address | peer-group name}
route-map map-tag {in | out}
(Optional) Apply a route map to filter an incoming or outgoing
route.
Step 5
end
Return to privileged EXEC mode.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-60
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring BGP
Command
Purpose
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 filtering method 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. (See the
Regular Expressions appendix in the Cisco IOS Dial Technologies Command Reference, Release 12.2
for more information on forming regular expressions.) 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 autonomous-system-path
filtering:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ip as-path access-list access-list-number
{permit | deny} as-regular-expressions
Define a BGP-related access list.
Step 3
router bgp autonomous-system
Enter BGP router configuration mode.
Step 4
neighbor {ip-address | peer-group name}
filter-list {access-list-number | name} {in |
out | weight weight}
Establish a BGP filter based on an access list.
Step 5
end
Return to privileged EXEC mode.
Step 6
show ip bgp neighbors [paths
regular-expression]
Verify the configuration.
Step 7
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Configuring Prefix Lists for BGP Filtering
You can use prefix lists as an alternative to access lists in many BGP route filtering commands, including
the neighbor distribute-list router configuration command. The advantages of using prefix lists include
performance improvements in loading and lookup of large lists, incremental update support, easier CLI
configuration, and greater flexibility.
Prefix-list filtering matches the prefixes of routes with those listed in the prefix list, as when matching
access lists. When there is a match, the route is used. Whether a prefix is permitted or denied is based
upon these rules:
An empty prefix list permits all prefixes.
An implicit deny is assumed if a prefix does not match any entries in a prefix list.
When multiple entries of a prefix list match a prefix, the sequence number of a prefix-list entry
identifies the entry with the lowest sequence number.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-61
Chapter 38
Configuring IP Unicast Routing
Configuring BGP
By default, sequence numbers are generated automatically and incremented in units of five. If you
disable the automatic generation of sequence numbers, you must specify the sequence number for each
entry. You can specify sequence values in any increment. If you specify increments of one, you cannot
insert additional entries into the list. If you choose very large increments, you might run out of values.
You do not need to specify a sequence number when removing a configuration entry. Show commands
include the sequence numbers in their output.
Before using a prefix list in a command, you must set up the prefix list. Beginning in privileged EXEC
mode, follow these steps to create a prefix list or to add an entry to a prefix list:
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.
Step 4
end
Return to privileged EXEC mode.
Step 5
show ip prefix list [detail | summary] name
[network/len] [seq seq-num] [longer]
[first-match]
Verify the configuration by displaying information about a prefix list
or prefix-list entries.
Step 6
copy running-config startup-config
(Optional) Save your entries in the configuration file.
To delete a prefix list and all 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.
Configuring BGP Community Filtering
One way that BGP controls the distribution of routing information is based on the value of the
COMMUNITIES attribute. The attribute groups destinations into communities and applies routing
decisions based on the communities. This method simplifies the configuration of a BGP speaker to
control distribution of routing information.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-62
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring BGP
A community is a group of destinations that share some common attribute. Each destination can belong
to multiple communities. Autonomous-system administrators can define to which communities a
destination belongs. By default, all destinations belong to the general Internet community. The
community is identified by the COMMUNITIES attribute, an optional, transitive, global attribute in the
numerical range from 1 to 4294967200. These are some predefined, well-known communities:
internetAdvertise this route to the Internet community. All routers belong to it.
no-exportDo not advertise this route to EBGP peers.
no-advertiseDo not advertise this route to any peer (internal or external).
local-asDo not advertise this route to peers outside the local autonomous system.
Based on the community, you can control the routing information to accept, prefer, or distribute to other
neighbors. A BGP speaker can set, append, or modify the community of a route when learning,
advertising, or redistributing routes. When routes are aggregated, the resulting aggregate has a
COMMUNITIES attribute that contains all communities from all the initial routes.
You can use community lists to create groups of communities to use in a match clause of a route map.
As with an access list, a series of community lists can be created. Statements are evaluated until a match
is found. As soon as one statement is met, the test stops.
To set the COMMUNITIES attribute and match clauses based on communities, see the match
community-list and set community route-map configuration commands in the Using Route Maps to
Redistribute Routing Information section on page 38-89.
By default, no COMMUNITIES attribute is sent to a neighbor. You can specify that the COMMUNITIES
attribute be sent to the neighbor at an IP address by using the neighbor send-community router
configuration command.
Beginning in privileged EXEC mode, follow these steps to create and to apply a community list:
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}
send-community
Specify that the COMMUNITIES attribute is sent to the neighbor at 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 appears in a two-part format 2 bytes long. The
Cisco-default community format is NNAA. In the most recent RFC for
BGP, a community takes the form AA:NN, where the first part is the
autonomous-system number and the second part is a 2-byte number.
Step 8
end
Return to privileged EXEC mode.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-63
Chapter 38
Configuring IP Unicast Routing
Configuring BGP
Step 9
Step 10
Command
Purpose
show ip bgp community
Verify the configuration.
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Configuring BGP Neighbors and Peer Groups
Often many BGP neighbors are configured with the same update policies (that is, the same outbound
route maps, distribute lists, filter lists, update source, and so on). You can group neighbors with the same
update policies into peer groups to simplify configuration and to make updating more efficient. When
you have configured many peers, we recommend this approach.
To configure a BGP peer group, you create the peer group, assign options to the peer group, and add
neighbors as peer group members. You configure the peer group by using the neighbor router
configuration commands. By default, peer group members inherit all the configuration options of the
peer group, including the remote-as (if configured), version, update-source, out-route-map,
out-filter-list, out-dist-list, minimum-advertisement-interval, and next-hop-self. All peer group members
also inherit changes made to the peer group. You can also configure members to override the options that
do not affect outbound updates.
To assign configuration options to an individual neighbor, specify any of these router configuration
commands by using the neighbor IP address. To assign the options to a peer group, specify any of the
commands by using the peer-group name. You can disable a BGP peer or peer group without removing
all the configuration information by using the neighbor shutdown router configuration command.
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
peer-group-name
Make a BGP neighbor a member of the peer group.
Step 5
neighbor {ip-address | peer-group-name}
remote-as number
Specify a BGP neighbor. If a peer group does not have a
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}
description text
(Optional) Associate a description with a neighbor.
Step 7
neighbor {ip-address | peer-group-name}
default-originate [route-map map-name]
(Optional) Allow a BGP speaker (the local router) to send the
default route 0.0.0.0 to a neighbor for use as a default route.
Step 8
neighbor {ip-address | peer-group-name}
send-community
(Optional) Specify that the COMMUNITIES attribute is sent to
the neighbor at this IP address.
Step 9
neighbor {ip-address | peer-group-name}
update-source interface
(Optional) Allow internal BGP sessions to use any operational
interface for TCP connections.
Step 10
neighbor {ip-address | peer-group-name}
ebgp-multihop
(Optional) Allow BGP sessions, even when the neighbor is not
on a directly connected segment. The multihop session is not
established if the only route to the multihop-peer address is the
default route (0.0.0.0).
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-64
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring BGP
Command
Purpose
Step 11
neighbor {ip-address | peer-group-name}
local-as number
(Optional) Specify an autonomous-system number to use as the
local autonomous system. The range is 1 to 65535.
Step 12
neighbor {ip-address | peer-group-name}
advertisement-interval seconds
(Optional) Set the minimum interval between sending BGP
routing updates.
Step 13
neighbor {ip-address | peer-group-name}
maximum-prefix maximum [threshold]
(Optional) Control how many prefixes can be received from a
neighbor. The range is 1 to 4294967295. The threshold
(optional) is the percentage of the maximum at which a warning
message is generated. The default is 75 percent.
Step 14
neighbor {ip-address | peer-group-name}
next-hop-self
(Optional) Disable next-hop processing on the BGP updates to a
neighbor.
Step 15
neighbor {ip-address | peer-group-name}
password string
(Optional) Set MD5 authentication on a TCP connection to a
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}
route-map map-name {in | out}
(Optional) Apply a route map to incoming or outgoing routes.
Step 17
neighbor {ip-address | peer-group-name}
send-community
(Optional) Specify that the COMMUNITIES attribute is sent to
the neighbor at this IP address.
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}
distribute-list {access-list-number | name} {in |
out}
(Optional) Filter BGP routing updates to or from neighbors, as
specified in an access list.
Step 21
neighbor {ip-address | peer-group-name}
filter-list access-list-number {in | out | weight
weight}
(Optional) Establish a BGP filter.
Step 22
neighbor {ip-address | peer-group-name}
version value
(Optional) Specify the BGP version to use when communicating
with a neighbor.
Step 23
neighbor {ip-address | peer-group-name}
soft-reconfiguration inbound
(Optional) Configure the software to store received 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-65
Chapter 38
Configuring IP Unicast Routing
Configuring BGP
Configuring Aggregate Addresses
Classless interdomain routing (CIDR) creates aggregate routes (or supernets) to minimize the size of
routing tables. You can configure aggregate routes in BGP either by redistributing an aggregate route
into BGP or by creating an aggregate entry in the BGP routing table. An aggregate address is added to
the BGP table when there is at least one more specific entry in the BGP table.
Beginning in privileged EXEC mode, use these commands to create an aggregate address in the routing
table:
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 autonomous system, and the
atomic aggregate attribute is set to show that information might be
missing.
Step 4
aggregate-address address mask as-set
(Optional) Generate autonomous-system set path information. The
command creates an aggregate entry following the same rules as the
previous command, but the advertised path is 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
summary-only
(Optional) Advertise only summary addresses.
Step 6
aggregate-address address mask
suppress-map map-name
(Optional) Suppress selected, more specific routes.
Step 7
aggregate-address address mask
advertise-map map-name
(Optional) Generate an aggregate based on conditions specified by
the route map.
Step 8
aggregate-address address mask
attribute-map map-name
(Optional) Generate an aggregate with attributes specified in the
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.
Configuring Routing Domain Confederations
You can reduce the IBGP mesh is to divide an autonomous system into multiple subautonomous systems
and to group them into a single confederation that appears as a single autonomous system. Each
autonomous system is fully meshed within itself and has a few connections to other autonomous systems
in the same confederation. Even though the peers in different autonomous systems have EBGP sessions,
they exchange routing information as if they were IBGP peers. Specifically, the next hop, MED, and
local-preference information is preserved. You can then use a single IGP for all of the autonomous
systems.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-66
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring BGP
To configure a BGP confederation, you must specify a confederation identifier that acts as the
autonomous-system number for the autonomous-system group.
Beginning in privileged EXEC mode, use these commands to configure a BGP confederation:
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
[autonomous-system autonomous-system ...]
Specify the autonomous systems that belong to the
confederation and that are treated as special EBGP peers.
Step 5
end
Return to privileged EXEC mode.
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.
Configuring BGP Route Reflectors
BGP requires that all of the IBGP speakers be fully meshed. When a router receives a route from an
external neighbor, it must advertise it to all internal neighbors. To prevent a routing information loop,
all IBPG speakers must be connected. The internal neighbors do not send routes learned from internal
neighbors to other internal neighbors.
With route reflectors, all IBGP speakers do not need to be fully meshed. When you configure an internal
BGP peer as a route reflector, it passes IBGP learned routes to a set of IBGP neighbors. The internal
peers of the route reflector are divided into client peers and nonclient peers (all the other routers in the
autonomous system). A route reflector reflects routes between these two groups. The route reflector and
its client peers form a cluster. The nonclient peers must be fully meshed with each other, but the client
peers need not be fully meshed. The clients in the cluster do not communicate with IBGP speakers
outside their cluster.
When the route reflector receives an advertised route, it takes one of these actions, depending on the
neighbor:
A route from an external BGP speaker is advertised to all clients and nonclient peers.
A route from a nonclient peer is advertised to all clients.
A route from a client is advertised to all clients and nonclient peers. Hence, the clients need not be
fully meshed.
Usually, a cluster of clients have a single route reflector, and the cluster is identified by the route reflector
router ID. To increase redundancy and to avoid a single point of failure, a cluster can have more than one
route reflector. In this case, you must configure all route reflectors in the cluster with the same 4-byte
cluster ID so that a route reflector recognizes updates from route reflectors in the same cluster. All the
route reflectors serving a cluster should be fully meshed and should have identical sets of client and
nonclient peers.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-67
Chapter 38
Configuring IP Unicast Routing
Configuring BGP
Beginning in privileged EXEC mode, use these commands to configure a route reflector and clients:
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}
route-reflector-client
Configure the local router as a BGP route reflector and the
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.
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.
Configuring Route Dampening
Route flap dampening is a BGP feature to minimize the propagation of flapping routes across an
internetwork. A route is flapping when it is repeatedly available, then unavailable, then available, then
unavailable, and so on. When route dampening is enabled, a numeric penalty value is assigned to a route
when it flaps. When the accumulated penalties for a route reach the configured limit, BGP suppresses
advertisements of the route, even if the route is running. The reuse limit is a configurable value that is
compared with the penalty. If the penalty is less than the reuse limit, a suppressed route that is up is
advertised again.
Dampening is not applied to routes that are learned by IBGP. This policy prevents the IBGP peers from
having a higher penalty for routes external to the autonomous system.
Beginning in privileged EXEC mode, use these commands to configure BGP route dampening:
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
max-suppress [route-map map]
(Optional) Change the default values of route dampening
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-68
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring BGP
Command
Purpose
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 is 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.
Monitoring and Maintaining BGP
You can remove all contents of a particular cache, table, or database. This might be necessary when the
contents have become or are suspected to be invalid.
You can display specific statistics, such as the contents of BGP routing tables, caches, and databases.
You can use the information to get resource usage and to solve network problems. You can also display
information about node reachability and discover the routing path the packets of your device are taking
through the network.
Table 38-9 lists the privileged EXEC commands for clearing and displaying BGP. For explanations of
the display fields, see the Cisco IOS IP Command Reference, Volume 2 of 3: Routing Protocols,
Release 12.2.
Table 38-12
IP BGP Clear and Show Commands
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
[exact-match]
Display routes that are permitted by the community list.
show ip bgp filter-list access-list-number
Display routes that are matched by the specified
autonomous-system 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 autonomous-system path that
matches the specified regular expression entered on the command
line.
show ip bgp
Display the contents of the BGP routing table.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-69
Chapter 38
Configuring IP Unicast Routing
Configuring Multi-VRF CE
Table 38-12
IP BGP Clear and Show Commands (continued)
Command
Purpose
show ip bgp neighbors [address]
Display detailed information on the BGP and TCP connections to
individual neighbors.
show ip bgp neighbors [address] [advertised-routes |
dampened-routes | flap-statistics | paths
regular-expression | received-routes | routes]
Display routes learned from a particular BGP neighbor.
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.
Configuring Multi-VRF CE
This section applies only to the Catalyst Switch Module 3110.
Virtual Private Networks (VPNs) provide a secure way for customers to share bandwidth over an
ISP-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 known as a VPN routing/forwarding (VRF) table.
The Catalyst Switch Module 3110 supports multiple VPN routing/forwarding (multi-VRF) instances in
customer-edge (CE) devices (multi-VRF CE) when the switch is running the IP services or advanced IP
services feature set. A service provider uses multi-VRF CE allows to support two or more VPNs with
overlapping IP addresses.
Note
The switch does not use Multiprotocol Label Switching (MPLS) to support VPNs. For information about
MPLS VRF, see the Cisco IOS Switching Services Configuration Guide, Release 12.2.
These sections contain this information:
Understanding Multi-VRF CE, page 38-71
Default Multi-VRF CE Configuration, page 38-73
Multi-VRF CE Configuration Guidelines, page 38-73
Configuring VRFs, page 38-74
Configuring VRF-Aware Services, page 38-75
Configuring Multicast VRFs, page 38-78
Configuring a VPN Routing Session, page 38-79
Configuring BGP PE to CE Routing Sessions, page 38-80
Multi-VRF CE Configuration Example, page 38-80
Displaying Multi-VRF CE Status, page 38-84
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-70
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring Multi-VRF CE
Understanding Multi-VRF CE
Multi-VRF CE is a feature that allows a service provider to support two or more VPNs overlapping IP
addresses 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 switch
virtual interfaces (SVIs), but an interface cannot belong to more than one VRF at any time.
Note
Multi-VRF CE interfaces must be Layer 3 interfaces.
Multi-VRF CE includes these devices:
Customer-edge (CE) devices provide customers access to the service-provider network over a data
link to one or more provider edge routers. The CE device advertises the site local routes to the router
and learns the remote VPN routes from it. A switch can be a CE.
Provider-edge (PE) routers exchange routing information with CE devices by using static routing or
a routing protocol such as BGP, RIPv2, OSPF, or EIGRP. The PE is only required to maintain VPN
routes for those VPNs to which it is directly attached. The PE only needs to maintain all of the
service-provider VPN routes. Each PE router maintains a VRF for each of its directly connected
sites. Multiple interfaces on a PE router can be associated with a single VRF if all of these sites
participate in the same VPN. Each VPN is mapped to a specified VRF. After learning local VPN
routes from CEs, a PE router exchanges VPN routing information with other PE routers by using
internal BGP (IBPG).
Provider routers or core routers are any routers in the service provider network that are not attached
to CE devices.
With multi-VRF CE, multiple customers can share one CE, and only one physical link is used between
the CE and the PE. The shared CE maintains separate VRF tables for each customer and switches or
routes packets for each customer based on its own routing table. Multi-VRF CE extends limited PE
functionality to a CE device. It can then maintain separate VRF tables to extend the privacy and security
of a VPN to the branch office.
Figure 38-7 is an example of switches as multiple virtual CEs. This scenario is suited for customers who
have low bandwidth requirements for their VPN service, for example, small companies. In this case,
multi-VRF CE support is required in the switches. Because multi-VRF CE is a Layer 3 feature, each
interface in a VRF must be a Layer 3 interface.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-71
Chapter 38
Configuring IP Unicast Routing
Configuring Multi-VRF CE
Figure 38-7
Switches Acting as Multiple Virtual CEs
VPN 1
VPN 1
CE1
PE1
PE2
CE2
Service
provider
VPN 2
101385
VPN 2
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 mapping
between the VLAN ID and the policy label (PL) in multi-VRF-CE-related data structures and adds the
VLAN ID and PL to the VLAN database.
When multi-VRF CE is configured, the Layer 3 forwarding table is virtually 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 to different policy labels, which are used to distinguish the
VRFs during processing. 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 the 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 strips 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. If a route is found, the PE 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 you 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 providers backbone.
The multi-VRF CE network has these major components:
VPN route target communitieslists of all other members of a VPN community. You need to
configure VPN route targets for each VPN community member.
Multiprotocol BGP peering of VPN community PE routerspropagates VRF reachability
information to all members of a VPN community. You need to configure BGP peering in all PE
routers within a VPN community.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-72
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring Multi-VRF CE
VPN forwardingtransports all traffic between all VPN community members across a VPN
service-provider network.
Default Multi-VRF CE Configuration
Table 38-13 shows the default multi-VRF CE configuration.
Table 38-13
Default Multi-VRF CE Configuration
Feature
Default Setting
VRF
Disabled. No VRFs are defined.
Maps
No import maps, export maps, or route maps are defined.
VRF maximum routes
Fast Ethernet switches: 8000
Gigabit Ethernet switches: 12,000.
Forwarding table
The default for an interface is the global routing table.
Multi-VRF CE Configuration Guidelines
To use multi-VRF CE, you must have the IP services or advanced IP services feature set enabled on your
switch.
These are considerations when configuring multi-VRF CE in your network:
A switch with multi-VRF CE is shared by multiple customers, and each customer has its own routing
table.
Because customers use different VRF tables, the same IP addresses can be reused. Overlapped IP
addresses are allowed in different VPNs.
Multi-VRF CE lets multiple customers share the same physical link between the PE and the CE.
Trunk ports with multiple VLANs separate packets among customers. Each customer has its own
VLAN.
Multi-VRF CE does not support all MPLS-VRF functionality. It does not support label exchange,
LDP adjacency, or labeled packets.
The PE router does not recognize a difference between using multi-VRF CE or using multiple CEs.
In Figure 38-7, multiple virtual Layer 3 interfaces are connected to the multi-VRF CE device.
The switch supports VRF over physical ports, VLAN SVIs, or a combination of both. The SVIs can
be connected through an access port or a trunk port.
A customer can use multiple VLANs if they do not overlap with those of other customers. A
customers VLANs are mapped to a specific routing table ID that identifies the appropriate routing
tables stored on the switch.
A switch supports 1 global network and up to 26 VRFs.
Most routing protocols (BGP, OSPF, RIP, and static routing) can be used between the CE and the
PE. However, we recommend using external BGP (EBGP) for these reasons:
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 simplifies the passing of attributes of the routes to the CE.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-73
Chapter 38
Configuring IP Unicast Routing
Configuring Multi-VRF CE
Multi-VRF CE does not affect the packet switching rate.
VPN multicast is not supported.
You can configure 104 policies whether or not VRFs are configured on the switch or the switch
stack.
You can enable VRF on a private VLAN and the reverse.
You cannot enable VRF when policy-based routing (PBR) is enabled on an interface and the reverse.
You cannot enable VRF when Web Cache Communication Protocol (WCCP) is enabled on an
interface and the reverse.
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 autonomous-system number and an
arbitrary number (nnn:y) or an IP address and arbitrary
number (A.B.C.D:y)
Step 5
route-target {export | import | both}
route-target-ext-community
Create a list of import, export, or import and export
route-target communities for the specified VRF. Enter
either an autonomous-system number and an arbitrary
number (nnn: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
Specify the Layer 3 interface to associate with the VRF,
and enter interface configuration mode. The interface can
be a routed port or an 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]
[vrf-name]
Verify the configuration. Display information about the
configured 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 a specific interface
from the VRF.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-74
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring Multi-VRF CE
Configuring VRF-Aware Services
IP services can be configured on global interfaces that run within the global routing instance. IP services
are enhanced to run on multiple routing instances; they are VRF-aware. Any configured VRF in the
system can be specified for a VRF-aware service.
VRF-aware services are implemented in platform-independent modules. VRF means multiple routing
instances in Cisco IOS. Each platform has its own limit on the number of VRFs it supports.
VRF-aware services have the following characteristics:
The user can ping a host in a user-specified VRF.
ARP entries are learned in separate VRFs. The user can display Address Resolution Protocol (ARP)
entries for specific VRFs.
These services are VRF-aware:
ARP
Ping
Simple Network Management Protocol (SNMP)
Hot Standby Router Protocol (HSRP)
Unicast Reverse Path Forwarding (uRPF)
Syslog
Traceroute
FTP and TFTP
User Interface for ARP
Beginning in privileged EXEC mode, follow these steps to configure VRF-aware services for ARP. For
complete syntax and usage information for the commands, refer to the switch command reference for
this release and the Cisco IOS Switching Services Command Reference, Release 12.2.
Command
Purpose
show ip arp vrf vrf-name
Display the ARP table in the specified VRF.
User Interface for PING
Beginning in privileged EXEC mode, follow these steps to configure VRF-aware services for ping. For
complete syntax and usage information for the commands, refer to the switch command reference for
this release and the Cisco IOS Switching Services Command Reference, Release 12.2.
Command
Purpose
ping vrf vrf-name ip-host
Display the ARP table in the specified VRF.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-75
Chapter 38
Configuring IP Unicast Routing
Configuring Multi-VRF CE
User Interface for SNMP
Beginning in privileged EXEC mode, follow these steps to configure VRF-aware services for SNMP. For
complete syntax and usage information for the commands, refer to 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
snmp-server trap authentication vrf
Enable SNMP traps for packets on a VRF.
Step 3
snmp-server engineID remote host vrf
vpn-instance engine-id string
Configure a name for the remote SNMP engine on a switch.
Step 4
snmp-server host host vrf vpn-instance
traps community
Specify the recipient of an SNMP trap operation, and specify the VRF
table used for sending SNMP traps.
Step 5
snmp-server host host vrf vpn-instance
informs community
Specify the recipient of an SNMP inform operation, and specify the
VRF table used for sending SNMP informs.
Step 6
snmp-server user user group remote host Add a user to an SNMP group for a remote host on a VRF for SNMP
vrf vpn-instance security model
access.
Step 7
end
Return to privileged EXEC mode.
User Interface for HSRP
HSRP support for VRFs ensures that HSRP virtual IP addresses are added to the correct IP routing table.
Beginning in privileged EXEC mode, follow these steps to configure VRF-aware services for HSRP. For
complete syntax and usage information for the commands, refer to 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
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.
User Interface for uRPF
uRPF can be configured on an interface assigned to a VRF, and source lookup occurs in the VRF table.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-76
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring Multi-VRF CE
Beginning in privileged EXEC mode, follow these steps to configure VRF-aware services for uRPF. For
complete syntax and usage information for the commands, refer to 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
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
ip verify unicast reverse-path
Enable uRPF on the interface.
Step 7
end
Return to privileged EXEC mode.
User Interface for Syslog
Beginning in privileged EXEC mode, follow these steps to configure VRF-aware services for syslog. For
complete syntax and usage information for the commands, refer to 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
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
debugging
Log messages to an internal buffer.
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.
User Interface for Traceroute
Beginning in privileged EXEC mode, follow these steps to configure VRF-aware services for traceroute.
For complete syntax and usage information for the commands, refer to the switch command reference
for this release and the Cisco IOS Switching Services Command Reference, Release 12.2.
Command
Purpose
traceroute vrf vrf-name ipaddress
Specify the name of a VPN VRF in which to find the destination
address.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-77
Chapter 38
Configuring IP Unicast Routing
Configuring Multi-VRF CE
User Interface for FTP and TFTP
So that FTP and TFTP are VRF-aware, you must configure command-line interface (CLI) commands for
FTP/TFTP. For example, if you want to use a VRF table that is attached to an interface, say E1/0, you
need to configure the CLI ip [t]ftp source-interface E1/0 to inform [t]ftp to use a specific routing table.
In this example, the VRF table looks up the destination IP address. These changes are
backward-compatible and do not affect existing behavior. That is, you can use the source-interface CLI
to send packets out a particular interface even if no VRF is configured on that interface.
To specify the source IP address for FTP connections, use the ip ftp source-interface show mode
command. To use the address of the interface where the connection is made, use the no form of this
command.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ip ftp source-interface interface-type
interface-number
Specify the source IP address for FTP connections.
Step 3
end
Return to privileged EXEC mode.
To specify an interface IP address 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
interface-number
Specify the source IP address for TFTP connections.
Step 3
end
Return to privileged EXEC mode.
Configuring Multicast VRFs
Beginning in privileged EXEC mode, follow these steps to configure a multicast within a VRF table. 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 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
autonomous-system number and an arbitrary number (nnn:y) or an IP
address and an arbitrary number (A.B.C.D:y)
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-78
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring Multi-VRF CE
Command
Purpose
Step 5
route-target {export | import | both}
route-target-ext-community
Create a list of import, export, or import and export route target
communities for the specified VRF. Enter either an autonomous-system
number and an arbitrary number (nnn: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
distributed
(Optional) Enable global multicast routing for VRF table.
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 the 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.
Step 13
show ip vrf [brief | detail | interfaces]
[vrf-name]
Verify the configuration. Display information about the configured
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.
Configuring a VPN Routing Session
Routing within the VPN can be configured with any supported routing protocol (RIP, OSPF, EIGRP, or
BGP) or with static routing. The configuration shown here is for OSPF, but the process is the same for
other protocols.
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
autonomous-system-number subnets
Set the switch to redistribute information from the BGP
network to the 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-79
Chapter 38
Configuring IP Unicast Routing
Configuring Multi-VRF CE
Use the no router ospf process-id vrf vrf-name global configuration command to disassociate the VPN
forwarding table from the OSPF routing process.
Configuring BGP PE to CE Routing Sessions
Beginning in privileged EXEC mode, follow these steps to configure a BGP PE to CE 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
autonomous-system number passed to other BGP routers,
and enter router configuration mode.
Step 3
network network-number mask
network-mask
Specify a network and mask to advertise through BGP.
Step 4
redistribute ospf process-id match
internal
Set the switch to redistribute OSPF internal routes.
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.
Multi-VRF CE Configuration Example
Figure 38-8 is a simplified example of the physical connections in a network similar to that in
Figure 38-7. OSPF is the protocol used in VPN1, VPN2, and the global network. BGP is used in the
CE-to-PE connections. The examples following the illustration show how to configure a switch as a CE
Switch A, and the VRF configuration for customer switches D and F. Commands for configuring CE
Switch C and the other customer switches are not included but would be similar. The example also
includes commands for configuring traffic to Switch A for a Catalyst 6000 or Catalyst 6500 switch acting
as a PE router.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-80
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring Multi-VRF CE
Figure 38-8
Multi-VRF CE Configuration Example
Switch A
Switch B
Switch C
VPN1
Switch D
VPN1
208.0.0.0
Fast
Ethernet
8
Switch H
Switch E
108.0.0.0
VPN2
Fast
Ethernet
7
CE1
Switch F
118.0.0.0
Fast
Ethernet
11
VPN2
PE
CE2
Switch J
Gigabit
Ethernet
1
Global network
Switch K
Global network
168.0.0.0
Fast
Ethernet
3
CE = Customer-edge device
PE = Provider-edge device
101386
Switch G
Configuring Switch A
On Switch A, enable routing, and configure VRF.
Switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# ip routing
Switch(config)# ip vrf v11
Switch(config-vrf)# rd 800:1
Switch(config-vrf)# route-target export 800:1
Switch(config-vrf)# route-target import 800:1
Switch(config-vrf)# exit
Switch(config)# ip vrf v12
Switch(config-vrf)# rd 800:2
Switch(config-vrf)# route-target export 800:2
Switch(config-vrf)# route-target import 800:2
Switch(config-vrf)# exit
Configure the loopback and physical interfaces on Switch A. Gigabit Ethernet port 1 is a trunk
connection to the PE. Gigabit 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
Switch(config)# interface loopback2
Switch(config-if)# ip vrf forwarding v12
Switch(config-if)# ip address 8.8.2.8 255.255.255.0
Switch(config-if)# exit
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-81
Chapter 38
Configuring IP Unicast Routing
Configuring Multi-VRF CE
Switch(config)# interface gigabitethernet1/0/5
Switch(config-if)# switchport trunk encapsulation dot1q
Switch(config-if)# switchport mode trunk
Switch(config-if)# no ip address
Switch(config-if)# exit
Switch(config)# interface gigabitethernet1/0/8
Switch(config-if)# switchport access vlan 208
Switch(config-if)# no ip address
Switch(config-if)# exit
Switch(config)# interface gigabitethernet1/0/11
Switch(config-if)# switchport trunk encapsulation dot1q
Switch(config-if)# switchport mode trunk
Switch(config-if)# no ip address
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 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
Switch(config)# interface vlan20
Switch(config-if)# ip vrf forwarding v12
Switch(config-if)# ip address 83.0.0.8 255.255.255.0
Switch(config-if)# exit
Switch(config)# interface vlan118
Switch(config-if)# ip vrf forwarding v12
Switch(config-if)# ip address 118.0.0.8 255.255.255.0
Switch(config-if)# exit
Switch(config)# interface vlan208
Switch(config-if)# ip vrf forwarding v11
Switch(config-if)# ip address 208.0.0.8 255.255.255.0
Switch(config-if)# exit
Configure OSPF routing in VPN1 and VPN2.
Switch(config)# router
Switch(config-router)#
Switch(config-router)#
Switch(config-router)#
Switch(config)# router
Switch(config-router)#
Switch(config-router)#
Switch(config-router)#
ospf 1 vrf vl1
redistribute bgp 800 subnets
network 208.0.0.0 0.0.0.255 area 0
exit
ospf 2 vrf vl2
redistribute bgp 800 subnets
network 118.0.0.0 0.0.0.255 area 0
exit
Configure BGP for CE-to-PE routing.
Switch(config)# router bgp 800
Switch(config-router)# address-family ipv4 vrf vl2
Switch(config-router-af)# redistribute ospf 2 match internal
Switch(config-router-af)# neighbor 83.0.0.3 remote-as 100
Switch(config-router-af)# neighbor 83.0.0.3 activate
Switch(config-router-af)# network 8.8.2.0 mask 255.255.255.0
Switch(config-router-af)# exit
Switch(config-router)# address-family ipv4 vrf vl1
Switch(config-router-af)# redistribute ospf 1 match internal
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-82
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring Multi-VRF CE
Switch(config-router-af)#
Switch(config-router-af)#
Switch(config-router-af)#
Switch(config-router-af)#
neighbor 38.0.0.3 remote-as 100
neighbor 38.0.0.3 activate
network 8.8.1.0 mask 255.255.255.0
end
Configuring Switch D
Switch D belongs to VPN 1. Configure the connection to Switch A by using these commands.
Switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# ip routing
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# no switchport
Switch(config-if)# ip address 208.0.0.20 255.255.255.0
Switch(config-if)# exit
Switch(config)# router ospf 101
Switch(config-router)# network 208.0.0.0 0.0.0.255 area 0
Switch(config-router)# end
Configuring Switch F
Switch F belongs to VPN 2. Configure the connection to Switch A by using these commands.
Switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# ip routing
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# switchport trunk encapsulation dot1q
Switch(config-if)# switchport mode trunk
Switch(config-if)# no ip address
Switch(config-if)# exit
Switch(config)# interface vlan118
Switch(config-if)# ip address 118.0.0.11 255.255.255.0
Switch(config-if)# exit
Switch(config)# router ospf 101
Switch(config-router)# network 118.0.0.0 0.0.0.255 area 0
Switch(config-router)# end
Configuring PE Switch B
When used on switch B (the PE router), these commands configure only 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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-83
Chapter 38
Configuring IP Unicast Routing
Configuring Multi-VRF CE
Router(config-if)# ip vrf forwarding v1
Router(config-if)# ip address 3.3.1.3 255.255.255.0
Router(config-if)# exit
Router(config)# interface loopback2
Router(config-if)# ip vrf forwarding v2
Router(config-if)# ip address 3.3.2.3 255.255.255.0
Router(config-if)# exit
Router(config)# interface gigabitethernet1/1/0.10
Router(config-if)# encapsulation dot1q 10
Router(config-if)# ip vrf forwarding v1
Router(config-if)# ip address 38.0.0.3 255.255.255.0
Router(config-if)# exit
Router(config)# interface gigabitethernet1/1/0.20
Router(config-if)# encapsulation dot1q 20
Router(config-if)# ip vrf forwarding v2
Router(config-if)# ip address 83.0.0.3 255.255.255.0
Router(config-if)# exit
Router(config)# router bgp 100
Router(config-router)# address-family ipv4 vrf v2
Router(config-router-af)# neighbor 83.0.0.8 remote-as 800
Router(config-router-af)# neighbor 83.0.0.8 activate
Router(config-router-af)# network 3.3.2.0 mask 255.255.255.0
Router(config-router-af)# exit
Router(config-router)# address-family ipv4 vrf vl
Router(config-router-af)# neighbor 38.0.0.8 remote-as 800
Router(config-router-af)# neighbor 38.0.0.8 activate
Router(config-router-af)# network 3.3.1.0 mask 255.255.255.0
Router(config-router-af)# end
Displaying Multi-VRF CE Status
You can use the privileged EXEC commands in Table 38-14 to display information about multi-VRF CE
configuration and status.
Table 38-14
Commands for Displaying Multi-VRF CE Information
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]
[mobile] [odr] [profile] [static] [summary] [supernets-only]
Display IP routing table information associated
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-84
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring Unicast Reverse Path Forwarding
Configuring Unicast Reverse Path Forwarding
The unicast reverse path forwarding (uRPF) feature helps to mitigate problems that are caused by the
introduction of malformed or forged (spoofed) IP source addresses into a network. uRPF discards IP
packets without a verifiable IP source address. For example, a number of common denial-of-service
(DoS) attacks, including Smurf and Tribal Flood Network (TFN), take advantage of forged or rapidly
changing source-IP addresses to allow attackers to avoid efforts to locate or to filter the attacks. For
Internet service providers (ISPs) that provide public access, uRPF deflects such attacks by forwarding
only packets with valid source addresses and that are consistent with the IP routing table. This action
protects the network of the ISP, its customer, and the rest of the Internet.
For detailed IP uRPF configuration information, see the Other Security Features chapter in the Cisco
IOS Security Configuration Guide, Release 12.2 at this URL:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuration_guide_book09186a
0080087df1.html
Configuring Protocol-Independent Features
This section describes how to configure IP routing protocol-independent features. These features are
available on switches running the IP base or the IP services feature set. However, on the IP base feature
set, protocol-related features are available only for RIP. For a complete description of the IP routing
protocol-independent commands in this chapter, see the IP Routing Protocol-Independent Commands
chapter of the Cisco IOS IP Command Reference, Volume 2 of 3: Routing Protocols, Release 12.2 from
the Cisco.com page under Documentation > Cisco IOS Software > 12.2 Mainline > Command
References.
These sections contain this configuration information:
Configuring Cisco Express Forwarding and Distributed Cisco Express Forwarding, page 38-85
Configuring the Number of Equal-Cost Routing Paths, page 38-87
Configuring Static Unicast Routes, page 38-88
Specifying Default Routes and Networks, page 38-89
Using Route Maps to Redistribute Routing Information, page 38-89
Configuring Policy-Based Routing, page 38-93 (only the Catalyst Switch Module 3110)
Filtering Routing Information, page 38-97
Managing Authentication Keys, page 38-99
Configuring Cisco Express Forwarding and Distributed Cisco Express
Forwarding
Cisco Express Forwarding (CEF) is a Layer 3 IP switching technology used to optimize network
performance. CEF implements an advanced IP look-up and forwarding algorithm to deliver maximum
Layer 3 switching performance. CEF is less CPU-intensive than fast-switching route-caching, providing
more CPU processing power dedicated to packet forwarding. In a Catalyst Switch Module 3110 switch
stack, a stack member uses distributed CEF (dCEF) in the stack. On a standalone switch (a Catalyst
Switch Module 3012 or standalone Catalyst Switch Module 3110), the switch uses CEF. In dynamic
networks, fast-switching cache entries are frequently invalidated because of routing changes, which
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-85
Chapter 38
Configuring IP Unicast Routing
Configuring Protocol-Independent Features
causes traffic to be process-switched using the routing table, instead of fast-switched using the route
cache. CEF and dCEF use the Forwarding Information Base (FIB) lookup table for destination-based
switching of IP packets.
The two main components in CEF and dCEF are the distributed FIB and the distributed adjacency tables.
The FIB is similar to a routing table or information base and maintains a mirror image of the
forwarding information in the IP routing table. When routing or topology changes occur in the
network, the IP routing table is updated, and those changes are reflected in the FIB. The FIB
maintains next-hop address information based on the information in the IP routing table. Because
the FIB contains all known routes in the routing table, CEF eliminates route cache maintenance, is
more efficient for switching traffic, and is not affected by traffic patterns.
Nodes in the network are said to be adjacent if they can reach each other with a single hop across a
link layer. CEF uses adjacency tables to prepend Layer 2 addressing information. The adjacency
table maintains Layer 2 next-hop addresses for all FIB entries.
Because the switch or switch stack uses ASICs to achieve Gigabit-speed line rate IP traffic, CEF or dCEF
forwarding applies only to the software-forwarding path, that is, traffic that is forwarded by the CPU.
The default configuration is CEF or dCEF enabled on all Layer 3 interfaces. Entering the no ip
route-cache cef interface configuration command disables CEF for traffic that is being forwarded by
software. This command does not affect the hardware forwarding path. You can re-enable CEF or dCEF
by using the ip cef or ip cef distributed global configuration command. To enable CEF on an interface
for the software-forwarding path, use the ip route-cache cef interface configuration command.
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 or dCEF on interfaces except
for debugging purposes.
Beginning in privileged EXEC mode, follow these steps to enable CEF or dCEF globally and on an
interface if it has been disabled:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ip cef
Enable CEF operation on a standalone switch,
or
or
ip cef distributed
enable dCEF operation on a switch stack.
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.
Step 5
end
Return to privileged EXEC mode.
Step 6
show ip cef
Display the CEF status on all interfaces.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-86
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring Protocol-Independent Features
Step 7
Command
Purpose
show cef linecard [detail]
Display CEF-related interface information on a standalone
switch,
or
or
show cef linecard [stack-member-number]
[detail]
display dCEF-related interface information for all switches in
the stack or for the specified stack member.
(Optional) For stack-member-number, specify the stack
member.
Step 8
show cef interface [interface-id]
Display detailed CEF information for all interfaces or the
specified interface.
Step 9
show adjacency
Display CEF adjacency table information.
Step 10
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Configuring the Number of Equal-Cost Routing Paths
When a router has two or more routes to the same network with the same metrics, these routes can be
thought of as having an equal cost. A parallel path provides another way to see occurrences of equal-cost
routes in an IP routing table. A router with two or more equal-cost paths to a network can use them
concurrently. Parallel paths provide redundancy in case of a circuit failure and also enable a router to
load balance packets for more efficient use of available bandwidth. Equal-cost routes are supported
across switches in a stack.
The router automatically learns about and configures equal-cost routes, but you can control the
maximum number of parallel paths supported by an IP routing protocol in its routing table. Although the
switch software allows a maximum of 32 equal-cost routes, the switch never uses more than 16 paths per
route.
Beginning in privileged EXEC mode, follow these steps to change the maximum number of parallel
paths in a routing table from the default:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
router {bgp | rip | ospf | eigrp}
Enter router configuration mode.
A switch running the IP base feature set (for example, the Catalyst
Switch Module 3012) supports only the rip keyword.
Step 3
maximum-paths maximum
Set the maximum number of parallel paths for the protocol routing
table. The range is from 1 to 16.
The default is 4 for most IP routing protocols, but is only 1 for BGP on
the Catalyst Switch Module 3110.
The default is 4 on the Catalyst Switch Module 3012.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-87
Chapter 38
Configuring IP Unicast Routing
Configuring Protocol-Independent Features
Configuring Static Unicast Routes
Static unicast routes are user-defined routes that cause packets moving between a source and a
destination to take a specified path. Static routes can be important if the router cannot dynamically build
a route to a particular destination and are useful for specifying a gateway of last resort to which all
unroutable packets are sent.
Beginning in privileged EXEC mode, follow these steps to configure a static route:
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 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 38-15. 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.
Table 38-15
Dynamic Routing Protocol Default Administrative Distances
Route Source
Default Distance
Connected interface
Static route
Enhanced IRGP summary route
External BGP
Internal Enhanced IGRP1
IGRP
OSPF
Unknown
5
20
90
100
Internal BGP
110
1
200
225
1. Only the Catalyst Switch Module 3110 supports the administrative
distance for this route source.
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 as connected in the routing table 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-88
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring Protocol-Independent Features
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 address in a static route, the static route is also removed from the IP routing table.
Specifying Default Routes and Networks
A router might not be able to learn the routes to all other networks. To provide complete routing
capability, you can use some routers as smart routers and give the remaining routers default routes to the
smart router. (Smart routers have routing table information for the entire internetwork.) These default
routes can be dynamically learned or can be configured in the individual routers. Most dynamic interior
routing protocols can cause a smart router to generate dynamic default information that is then forwarded
to other routers.
If a router has a directly connected interface to the specified default network, the dynamic routing
protocols running on that device generate a default route. In RIP, it advertises the pseudonetwork 0.0.0.0.
A router that is generating the default route for a network also might need a default route of its own. One
way a router can generate its own default router is to specify a static route to the network 0.0.0.0 through
the appropriate device.
Beginning in privileged EXEC mode, follow these steps to define a default static route to a network:
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 output.
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 passes through a dynamic routing protocol, no further configuration is
required. The system periodically scans its routing table to choose the best default network as its default
route. IGRP networks might have several candidate networks for the system default. Cisco routers use
administrative distance and metric information to set the default route or the gateway of last resort.
If dynamic default information is not being passed to the system, you can specify candidates for the
default route 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.
Using Route Maps to Redistribute Routing Information
The switch can run multiple routing protocols simultaneously, and it can redistribute information from
one routing protocol to another. Information redistribution from one routing protocol to another applies
to all supported IP-based routing protocols.
You can also conditionally control the redistribution of routes between routing domains by defining
enhanced packet filters or route maps between the two domains. The match and set route-map
configuration commands define the condition portion of a route map. The match command specifies that
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-89
Chapter 38
Configuring IP Unicast Routing
Configuring Protocol-Independent Features
a criterion must be matched. The set command specifies an action to be taken if the routing update meets
the conditions defined by the match command. Although redistribution is a protocol-independent
feature, some of the match and set route-map configuration commands are specific to a particular
protocol.
One or more match commands and one or more set commands follow a route-map command. If there
are no match commands, everything matches. If there are no set commands, only the match action
occurs. Therefore, you need at least one match or set command.
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 a 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 on the Catalyst Switch Module 3110. You can
use the continue clause to configure and organize more modular policy definitions so that specific policy
configurations are not repeated within the same route map. 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-tagA meaningful name for the route map. The
redistribute router configuration command uses this
name to reference this route map. Multiple route maps
can share the same map tag name.
[permit | deny] (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 defines 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 autonomous-system path access list only on
a Catalyst Switch Module 3110.
Step 4
match community-list community-list-number [exact]
Match a BGP community list only on a Catalyst Switch
Module 3110.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-90
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring Protocol-Independent Features
Command
Purpose
Step 5
match ip address {access-list-number |
access-list-name} [...access-list-number |
...access-list-name]
Match a standard access list by specifying the name or
number. It can be an integer from 1 to 199.
Step 6
match metric metric-value
Match the specified route metric. The metric-value can be
an EIGRP metric with a specified value from 0
to 4294967295.
Step 7
match ip next-hop {access-list-number |
access-list-name} [...access-list-number |
...access-list-name]
Match a next-hop router address passed by one of the
access lists specified (numbered from 1 to 199).
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 |
access-list-name} [...access-list-number |
...access-list-name]
Match the address specified by the specified advertised
access lists.
Step 11
match route-type {local | internal | external [type-1 |
type-2]}
Match the specified route-type only on a Catalyst Switch
Module 3110:
localLocally generated BGP routes.
internalOSPF intra-area and interarea routes or
EIGRP internal routes.
externalOSPF external routes (Type 1 or Type 2)
or EIGRP external routes.
Step 12
set dampening halflife reuse suppress
max-suppress-time
Set BGP route dampening factors only on a Catalyst
Switch Module 3110.
Step 13
set local-preference value
Assign a value to a local BGP path only on a Catalyst
Switch Module 3110.
Step 14
set origin {igp | egp as | incomplete}
Set the BGP origin code only on a Catalyst Switch
Module 3110.
Step 15
set as-path {tag | prepend as-path-string}
Modify the BGP autonomous system path only on a
Catalyst Switch Module 3110.
Step 16
set level {level-1 | level-2 | level-1-2 | stub-area |
backbone}
Set the level for routes that are advertised into the
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 (only
for EIGRP) only on a Catalyst Switch Module 3110. The
metric value is an integer from 294967295 to
294967295.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-91
Chapter 38
Configuring IP Unicast Routing
Configuring Protocol-Independent Features
Step 18
Command
Purpose
set metric bandwidth delay reliability loading mtu
Set the metric value to give the redistributed routes (only
for EIGRP) only on a Catalyst Switch Module 3110:
bandwidthMetric value or IGRP bandwidth of the
route in Kb/s in the range 0 to 4294967295
delayRoute delay in tens of microseconds in the
range 0 to 4294967295.
reliabilityLikelihood 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).
mtuMinimum 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
only on a Catalyst Switch Module 3110.
Step 20
set metric-type internal
Set the multi-exit discriminator (MED) value on prefixes
advertised to an external BGP neighbor to match the IGP
metric of the next hop only on a Catalyst Switch
Module 3110.
Step 21
set weight
Set the BGP weight for the routing table only on a
Catalyst Switch Module 3110. The value is from 1 to
65535.
Step 22
end
Return to privileged EXEC mode.
Step 23
show route-map
Display all configured route maps 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 | rip | ospf | eigrp}
Enter router configuration mode.
A switch running the IP base feature set (for example,
the Catalyst Switch Module 3012) supports only the
rip keyword.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-92
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring Protocol-Independent Features
Command
Purpose
Step 3
redistribute protocol [process-id] {level-1 | level-1-2 |
level-2} [metric metric-value] [metric-type type-value]
[match internal | external type-value] [tag tag-value]
[route-map map-tag] [weight weight] [subnets]
Redistribute routes from one routing protocol to
another routing protocol. If no route maps are
specified, all routes are redistributed. If the keyword
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:
RIP on the Catalyst Switch Module 3012.
BGP, RIP, or OSPF on the Catalyst Switch
Module 3110.
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
end
Return to privileged EXEC mode.
Step 7
show route-map
Display all configured route maps or only the one
specified to verify configuration.
Step 8
copy running-config startup-config
(Optional) Save your entries in the configuration file.
To disable redistribution, use the no form of the commands.
The metrics of one routing protocol do not necessarily translate into the metrics of another. For example,
the RIP metric is a hop count, and the IGRP metric is a combination of five qualities. In these situations,
an artificial metric is assigned to the redistributed route. Uncontrolled exchanging of routing information
between different routing protocols can create routing loops and seriously degrade network operation.
If you have not defined a default redistribution metric that replaces metric conversion, some automatic
metric translations occur between routing protocols:
RIP can automatically redistribute static routes. It assigns static routes a metric of 1 (directly
connected).
Any protocol can redistribute other routing protocols if a default mode is in effect.
Configuring Policy-Based Routing
This section applies only to the Catalyst Switch Module 3110.
You can use policy-based routing (PBR) to configure a defined policy for traffic flows. By using PBR,
you have more control over routing by reducing the reliance on routes derived from routing protocols.
PBR can specify and implement routing policies that allow or deny paths based on:
Identity of a particular end system
Application
Protocol
You can use PBR to provide equal-access and source-sensitive routing, routing based on interactive
instead of 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 sending routine
application data such as e-mail over a low-bandwidth, low-cost link.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-93
Chapter 38
Configuring IP Unicast Routing
Configuring Protocol-Independent Features
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 38-89.
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 that identify the next
hop router in the path.
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 C, Unsupported Commands in Cisco IOS Release 12.2(40)EX2.
PBR configuration is applied to the whole stack, and all switches use the stack-master configuration.
Note
This software release does not support Policy-Based Routing (PBR) when processing IPv4 and IPv6
traffic.
PBR Configuration Guidelines
Before configuring PBR, you should be aware of this information:
To use PBR, you must have the IP services feature set enabled on the switch or the stack master.
Multicast traffic is not policy routed. PBR applies to only to unicast traffic.
You can enable PBR on a routed port or on an SVI.
The switch does not support route-map deny statements for PBR.
You can apply a policy route map to an EtherChannel port channel in Layer 3 mode, but you cannot
apply a policy route map to a physical interface that is a member of the EtherChannel. If you try to
do so, the command is rejected. When a policy route map is applied to a physical interface, that
interface cannot become a member of an EtherChannel.
You can define a maximum of 246 IP policy route maps on the switch or the switch stack.
You can define a maximum of 512 access control entries (ACEs) for PBR on the switch or the switch
stack.
When configuring match criteria in a route map, follow these guidelines:
Do not match ACLs that permit packets destined for a local address. PBR would forward these
packets, which could cause ping or Telnet failure or route protocol flappping.
Do not match ACLs with deny ACEs. Packets that match a deny ACE are sent to the CPU, which
could cause high CPU utilization.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-94
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring Protocol-Independent Features
To use PBR, you must first enable the routing template by using the sdm prefer routing global
configuration command. PBR is not supported with the VLAN and default templates. For more
information on the SDM templates, see Chapter 8, Configuring SDM Templates.
VRF and PBR are mutually exclusive on a switch interface. You cannot enable VRF when PBR is
enabled on an interface. The reverse is also true; you cannot enable PBR when VRF is enabled on
an interface.
Web Cache Communication Protocol (WCCP) and PBR are mutually exclusive on a switch
interface. You cannot enable WCCP when PBR is enabled on an interface. The reverse is also true;
you cannot enable PBR when WCCP is enabled on an interface.
The number of hardware 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, ToS, set interface, set default next hop, or set default
interface are not supported. Policy maps with no valid set actions or with a set action set to Dont
Fragment are not supported.
The switch supports QoS DSCP and IP precedence matching in PBR route maps, with these
limitations:
You cannot apply QoS DSCP mutation maps and PBR route maps to the same interface.
You cannot configure DSCP transparency and PBR DSCP route maps on the same switch.
When you configure PBR with QoS DSCP, you can set QoS as enabled (by entering the mls qos
global configuration command) or disabled (by entering the no mls qos command). When QoS
is enabled, to ensure that the DSCP value of the traffic is unchanged, you should configure the
DSCP trust state on the port where traffic enters the switch by entering the mls qos trust dscp
interface configuration command. If the trust state is not DSCP, by default, all nontrusted traffic
has the DSCP value marked as 0.
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
on an interface for that route map. All packets arriving on that interface that match 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. You must first enable PBR before you enable fast-switched
PBR. By default, fast-switched PBR is disabled.
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.
Note
To enable PBR, the switch or stack master must be running the IP services feature set.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-95
Chapter 38
Configuring IP Unicast Routing
Configuring Protocol-Independent Features
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 number]
Define any route maps used to control from where packets are
sent, and enter route-map configuration mode.
map-tagA 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
Step 3
match ip address {access-list-number |
access-list-name} [...access-list-number |
...access-list-name]
The route-map deny statement is not supported in
PBR route maps to be applied to an interface.
sequence number (Optional)Number that shows the
position of a new route map in the list of route maps
already configured with the same name.
Match the source and destination IP addresses that are
permitted by one or more standard or extended access lists.
Note
Do not enter an ACL with a deny ACE or an ACL that
permits a packet destined for a local address.
If you do not specify a match command, the route map applies
to all packets.
Step 4
set ip next-hop ip-address [...ip-address]
Specify the action to take on the packets that match the
criteria. Set the next 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.
Note
If the IP policy route map contains a deny statement,
the configuration fails.
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 for policy-based routing on
packets originating at the switch. This applies to packets
generated by the switch and not to incoming packets.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-96
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring Protocol-Independent Features
Command
Purpose
Step 11
end
Return to privileged EXEC mode.
Step 12
show route-map [map-name]
(Optional) Display all configured route maps 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.
Filtering Routing Information
You can filter routing protocol information by performing the tasks described in this section.
Note
When routes are redistributed between OSPF processes, no OSPF metrics are preserved on the Catalyst
Switch Module 3110.
Setting Passive Interfaces
To prevent other routers on a local network from dynamically learning about routes, you can use the
passive-interface router configuration command. Then routing update messages are not being sent
through a router interface. When you use this command in the OSPF protocol on a Catalyst Switch
Module 3110, the interface address that you specify as passive appears as a stub network in the OSPF
domain. OSPF routing information is neither sent nor received through that interface.
In networks with many interfaces, you do not need to manually set them as passive. You can set all
interfaces to be passive by default by using the passive-interface default router configuration command.
You can then manually setting interfaces where adjacencies are desired.
Beginning in privileged EXEC mode, follow these steps to configure passive interfaces:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
router {bgp | rip | ospf | eigrp}
Enter router configuration mode.
A switch running the IP base feature set (for example, the Catalyst
Switch Module 3012) supports only the rip keyword.
Step 3
passive-interface interface-id
Suppress sending of routing updates through the specified Layer 3
interface.
Step 4
passive-interface default
(Optional) Set all interfaces as passive by default.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-97
Chapter 38
Configuring IP Unicast Routing
Configuring Protocol-Independent Features
Command
Purpose
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 on a Catalyst Switch Module 3110 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.
Controlling Advertising and Processing in Routing Updates
You can use the distribute-list router configuration command with access control lists to suppress routes
from being advertised in routing updates and to prevent other routers from learning one or more routes.
When used in OSPF, this feature applies only to external routes, and you cannot specify an interface
name.
You can also use a distribute-list router configuration command to avoid processing certain routes listed
in incoming updates. (This feature does not apply to OSPF.)
Beginning in privileged EXEC mode, follow these steps to control the advertising or processing of
routing updates:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
router {bgp | rip | ospf | eigrp}
Enter router configuration mode.
A switch running the IP base feature set (for example, the
Catalyst Switch Module 3012) supports only the rip
keyword.
Step 3
distribute-list {access-list-number |
access-list-name} out [interface-name | routing
process | autonomous-system-number]
Permit or deny routes from being advertised in routing
updates, depending upon the action listed in the access list.
Step 4
distribute-list {access-list-number |
access-list-name} in [type-number]
Suppress processing in routes listed in updates.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-98
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Configuring Protocol-Independent Features
Filtering Sources of Routing Information
Because some routing information might be more accurate than others, you can use filtering to prioritize
information coming from different sources. An administrative distance is a rating of the trustworthiness
of a routing information source, such as a router or group of routers. In a large network, some routing
protocols can be more reliable than others. By specifying administrative distance values, you enable the
router to intelligently discriminate between sources of routing information. The router always picks the
route whose routing protocol has the lowest administrative distance. Table 38-15 on page 38-88 shows
the default administrative distances for various routing information sources.
Because each network has its own requirements, there are no general guidelines for assigning
administrative distances.
Beginning in privileged EXEC mode, follow these steps to filter sources of routing information:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
router {bgp | rip | ospf | eigrp}
Enter router configuration mode.
A switch running the IP base feature set (for example,
the Catalyst Switch Module 3012) supports only the rip
keyword.
Step 3
distance weight {ip-address {ip-address mask}}
[ip access list]
Define an administrative distance.
weightThe 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 listAn 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.
To remove a distance definition, use the no distance router configuration command.
Managing Authentication Keys
Key management is a method of controlling authentication keys used by routing protocols. Not all
protocols can use key management. Authentication keys are available for EIGRP (only on the Catalyst
Switch Module 3110) and RIP Version 2.
Before you manage authentication keys, you must enable authentication. See the appropriate protocol
section to see how to enable authentication for that protocol. To manage authentication keys, define a
key chain, identify the keys that belong to the key chain, and specify how long each key is valid. Each
key has its own key identifier (specified with the key number key chain configuration command), which
is stored locally. The combination of the key identifier and the interface associated with the message
uniquely identifies the authentication algorithm and Message Digest 5 (MD5) authentication key in use.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-99
Chapter 38
Configuring IP Unicast Routing
Configuring Protocol-Independent Features
You can configure multiple keys with life times. Only one authentication packet is sent, regardless of
how many valid keys exist. The software examines the key numbers in order from lowest to highest and
uses the first valid key it encounters. The lifetimes allow for overlap during key changes. Note that the
router must know these lifetimes.
Beginning in privileged EXEC mode, follow these steps to manage authentication keys:
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
seconds}
(Optional) Specify the time period during which the key
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
seconds}
(Optional) Specify the time period during which the key
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-100
OL-12189-01
Chapter 38
Configuring IP Unicast Routing
Monitoring and Maintaining the IP Network
Monitoring and Maintaining the IP Network
You can remove all contents of a particular cache, table, or database. You can also display specific
statistics. Use the privileged EXEC commands in Table 38-16 to clear routes or display status:
Table 38-16
Commands to Clear IP Routes or Display Route Status
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]] |
[protocol [process-id]]
Display the state of the routing table.
show ip route summary
Display the 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 configured route maps or only the one specified.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
38-101
Chapter 38
Configuring IP Unicast Routing
Monitoring and Maintaining the IP Network
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
38-102
OL-12189-01
CH A P T E R
39
Configuring IPv6 Host Functions and Unicast
Routing
Internet Protocol Version 6 (IPv6) is the network-layer Internet Protocol intended to replace Version 4
(IPv4) in the TCP/IP suite of protocols. This chapter describes how to configure IPv6 host functions and
unicast routing on the switch.
For information about configuring IPv4 unicast routing, see Chapter 38, Configuring IP Unicast
Routing. For information about configuring IPv6 Multicast Listener Discovery (MLD) snooping, see
Chapter 24, Configuring IPv6 MLD Snooping. For information on configuring IPv6 access control
lists (ACLs) see Chapter 35, Configuring IPv6 ACLs.
To use IPv6 unicast routing only on the Catalyst Switch Module 3110, the switch or the stack master
must be running the advanced IP services feature set. This feature set includes all IP services features
plus IPv6 host and unicast routing support.
The Catalyst Switch Module 3012 does not support IPv6 unicast routing.
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 {default | vlan}
global configuration command.
Unless otherwise noted, the term switch refers to a standalone switch and to a switch stack.
Note
For complete syntax and usage information for the commands used in this chapter, see the Cisco IOS
documentation referenced in the procedures
This chapter consists of these sections:
Supported IPv6 Host Functions and Unicast Routing Features section on page 39-2
Understanding IPv6 section on page 39-2
Configuring IPv6 section on page 39-15
Displaying IPv6 section on page 39-27
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
39-1
Chapter 39
Configuring IPv6 Host Functions and Unicast Routing
Supported IPv6 Host Functions and Unicast Routing Features
Supported IPv6 Host Functions and Unicast Routing Features
Table 39-1 shows the supported IPv6 features on each switch.
Table 39-1
Supported IPv6 Features
Feature
Catalyst Switch Module 3110
Catalyst Switch Module 3012
128-bit unicast addresses
Yes
Yes
DNS for IPv6
Yes
Yes
Path MTU discovery for IPv6
unicast
Yes
No
ICMPv6
Yes
Yes
Neighbor discovery
Yes
Yes
IPv6 stateless autoconfiguration Yes
and duplicate address detection
Yes
IPv6 applications
Ping, traceroute, Telnet, TFTP,
and FTP
Yes
Yes
SSH2 over IPv6 transport
Yes
Yes
HTTP server access over IPv6
transport
Yes
Yes
CDP3 support for IPv6 addresses Yes
Yes
Dual IPv4 and IPv6 protocol
stacks
Yes
Yes
EIGRPv64
Yes
No
Yes
Yes
Yes
No
Yes
No
IPv4 CEF
dCEFv6
7
RIP and OSPF
1. MTU = maximum transmission unit.
2. SSH = Secure Shell.
3. CDP = Cisco Discovery Protocol.
4. EIGRPv6 = Enhanced Gateway Routing Protocol Version 6.
5. CEF = Cisco Express Forwarding.
6. dCEFv6 = distributed Cisco Express Forwarding Version 6.
7. RIP = Routing Information Protocol.
8. OSPF = Open Shortest Path First.
Understanding IPv6
The IPv6 architecture allows existing IPv4 users to move to IPv6 and provides 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 the use of Network Address Translation (NAT) processing by
border routers at the edge of networks. IPv6 provides newer unicast methods, introduces hexadecimal
values into the IP address, and uses colons (:) instead of periods (.) as delimiters.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
39-2
OL-12189-01
Chapter 39
Configuring IPv6 Host Functions and Unicast Routing
Understanding IPv6
IPv6 also provides these advantages over IPv4:
Address management and delegation
Address autoconfiguration with stateless autoconfiguration, which is similar to DHCP but does not
require a specified DHCP application or server
Embedded IPsec (encrypted security)
Routing optimized for mobile devices
Duplicate Address Detection (DAD) feature
For information about how Cisco Systems implements IPv6, go to this URL:
http://www.cisco.com//warp/public/732/Tech/ipv6/
This section describes IPv6 implementation on the switch. These sections are included:
IPv6 Addresses, page 39-3
Supported IPv6 Host Functions and Unicast Routing Features, page 39-4
Unsupported IPv6 Host Functions and Unicast Routing Features, page 39-11
Limitations, page 39-12
IPv6 and Switch Stacks, page 39-12
SDM Templates, page 39-13
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: x:x:x:x:x:x:x:x. 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, go to the
Implementing Addressing and Basic Connectivity section of The Cisco IOS IPv6 Configuration
Library at this URL:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1839/products_feature_guide09186a00807fcf4b.
html
In the Information About Implementing Basic Connectivity for IPv6 section, these sections apply to
the switch:
IPv6 Address Formats
IPv6 Address Type: Unicast
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
39-3
Chapter 39
Configuring IPv6 Host Functions and Unicast Routing
Understanding IPv6
IPv6 Address Output Display
Simplified IPv6 Packet Header
Supported IPv6 Host Functions and Unicast Routing Features
These sections describe the IPv6 protocol features supported by the switch:
128-Bit Wide Unicast Addresses, page 39-4
DNS for IPv6, page 39-5
Path MTU Discovery for IPv6 Unicast, page 39-5 (only the Catalyst Switch Module 3110)
ICMPv6, page 39-5
Neighbor Discovery, page 39-5
IPv6 Stateless Autoconfiguration and Duplicate Address Detection, page 39-6
IPv6 Applications, page 39-7
Dual IPv4 and IPv6 Protocol Stacks, page 39-7
EIGRP IPv6, page 39-8 (only the Catalyst Switch Module 3110)
Support on the switch includes expanded address capability, header format simplification, improved
support of extensions and options, and hardware parsing of the extension header. The switch supports
hop-by-hop extension header packets, which are routed or bridged in software.
The Catalyst Switch Module 3110 provides IPv6 routing capability over native Ethernet Inter-Switch
Link (ISL) or 802.1Q trunk ports for static routes, Routing Information Protocol (RIP) for IPv6, and
Open Shortest Path First (OSPF) Version 3 protocol. It supports up to 16 equal-cost routes and can
forward IPv4 and IPv6 frames simultaneously at line rate.
128-Bit Wide Unicast Addresses
The switch supports aggregatable global unicast addresses and link-local unicast addresses. It does not
support site-local unicast addresses.
Aggregatable global unicast addresses are IPv6 addresses from the aggregatable global unicast
prefix. The address structure enables strict aggregation of routing prefixes and limits the number of
routing table entries in the global routing table. These addresses are used on links that are aggregated
through organizations and eventually to the Internet service provider.
These addresses are defined by a global routing prefix, a subnet ID, and an interface ID. Current
global unicast address allocation uses the range of addresses that start with binary value 001
(2000::/3). Addresses with a prefix of 2000::/3(001) through E000::/3(111) must have 64-bit
interface identifiers in the extended universal identifier (EUI)-64 format.
Link local unicast addresses can be automatically configured on any interface by using the link-local
prefix FE80::/10(1111 1110 10) and the interface identifier in the modified EUI format. Link-local
addresses are used in the neighbor discovery protocol and the stateless autoconfiguration process.
Nodes on a local link use link-local addresses and do not require globally unique addresses to
communicate. IPv6 routers do not forward packets with link-local source or destination addresses
to other links.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
39-4
OL-12189-01
Chapter 39
Configuring IPv6 Host Functions and Unicast Routing
Understanding IPv6
See the section on IPv6 Unicast Addresses in the Implementing Addressing and Basic Connectivity for
IPv6 chapter in the Cisco IOS IPv6 Configuration Library at this URL:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1839/products_feature_guide09186a00807fcf4b.
html
Each IPv6 host interface can support up to three addresses in hardware (one aggregatable global unicast
address, one link-local unicast address, and zero or more privacy addresses).
DNS for IPv6
IPv6 introduces new Domain Name System (DNS) record types that are supported in the DNS
name-to-address and address-to-name lookup processes. The new DNS AAAA resource record types
support IPv6 addresses and are equivalent to an A address record in IPv4. The switch supports DNS
resolution for IPv4 and IPv6.
Path MTU Discovery for IPv6 Unicast
The Catalyst Switch Module 3110 supports advertising the system MTU to IPv6 nodes and path MTU
discovery. Path MTU discovery allows a host to dynamically discover and adjust to differences in the
MTU size of every link along a given data path. In IPv6, if a link along the path is not large enough to
accommodate the packet size, the source of the packet handles the fragmentation. The switch does not
support path MTU discovery for multicast packets.
ICMPv6
The Internet Control Message Protocol (ICMP) in IPv6 functions the same as in IPv4. ICMP 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. A value of 58 in the Next Header field of the basic IPv6 packet header identifies
an IPv6 ICMP packet.
Neighbor Discovery
The switch supports Neighbor Discovery Protocol (NDP) for IPv6, a protocol running on top of ICMPv6,
and Static Neighbor Discovery 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.
A value of 135 in the Type field of the ICMP packet header identifies a neighbor solicitation message.
These messages are sent on the local link when a node needs to determine the link-layer address of
another node on the same local link. When a destination node receives a neighbor solicitation message,
it replies by sending a neighbor advertisement message, which has a value of 136 in the ICMP packet
header Type field.
A value of 137 in the ICMP packet header Type field identifies an IPv6 neighbor redirect message.
Routers send neighbor-redirect messages to inform hosts of better first-hop nodes on the path to a
destination. A router does not update its routing tables after receiving a neighbor-redirect message, and
hosts do not originate neighbor-redirect messages.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
39-5
Chapter 39
Configuring IPv6 Host Functions and Unicast Routing
Understanding IPv6
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 the CPU is actively resolving. This
drop avoids adding further load on the CPU.
IPv6 Stateless Autoconfiguration and Duplicate Address Detection
IPv6 supports two types of autoconfiguration:
Stateless autoconfiguration, where a host autonomously configures its own link-local address, and
booting nodes send router solicitations to request router advertisements for configuring interfaces.
Stateful autoconfiguration using Dynamic Host Configuration Protocol Version 6 (DHCPv6).
The switch supports stateless autoconfiguration to manage link, subnet, and site addressing changes,
such as management of host and mobile IP addresses.
Every interface on IPv6 nodes must have a link-local address that is automatically configured from the
identifier (router MAC address) for an interface and the link-local prefix FE80::/10. A link-local address
enables a node to communicate with other nodes on the link and can be used to further configure the
node. Nodes can connect to a network and automatically generate global IPv6 addresses without the need
for manual configuration or the help of a server, such as a DHCP server.
With IPv6, a router on the link uses router advertisement messages to advertise global prefixes and its
ability to act as a default router for the link. A node on the link can automatically configure global IPv6
addresses by appending its interface identifier (64 bits) to the prefixes (64 bits) included in the router
advertisement messages.
The 128-bit IPv6 addresses configured by a node are then subjected to duplicate-address detection to
ensure their uniqueness on the link. If the advertised prefixes are globally unique, the IPv6 addresses
configured by the node are guaranteed to be globally unique. Router solicitation messages, which have
a value of 133 in the ICMP packet header Type field, are sent by hosts at system startup so that the host
is immediately autoconfigured without waiting for the next scheduled router advertisement message.
IPv6 duplicate-address detection is performed on unicast addresses before they are assigned to an
interface. The switch does not support automatically generated site-local IPv6 addresses.
IPv6 Stateless Autoconfiguration
When an IPv6 host (nonrouter) autoconfigures its interfaces, the process includes generating a
link-local, a site-local, and a global address through stateless address autoconfiguration.
IPv6 nodes (routers and hosts) begin the autoconfiguration process by generating a link-local address for
the interface. Link-local address autoconfiguration is started by:
Enabling IPv6 on an interface by entering the ipv6 enable interface configuration command
Manually configuring the IPv6 address
Autoconfiguring by entering the ipv6 address autoconfig command
A link-local address is formed by appending the interface identifier to the well-known link-local prefix
(FE80::/10). The IPv6 node verifies that the generated tentative address is not used by another node on
the link before the address can be assigned to the interface. To verify this, the IPv6 node sends a neighbor
solicitation with the tentative address as the target address. If another node is detected to be using that
address or is attempting to use that address (duplicate address detection), the node sends a neighbor
solicitation for the target as well. If the tentative link-local address is not available, autoconfiguration
stops and you must manually configure the interface.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
39-6
OL-12189-01
Chapter 39
Configuring IPv6 Host Functions and Unicast Routing
Understanding IPv6
IPv6 nodes with a 48-bit MAC address generate an identifier for the autoconfigured address by
inserting 0xFF and 0xFE in the MAC address and reversing the universal/local bit. For example, if an
interface MAC address is 000b.462e.9047, the identifier would be 020b:46ff:fe2e:9047, and the
autogenerated IPv6 ink address would be FE80::20B:46FF:FE2E:9047.
Only IPv6 hosts can autoconfigure stateless addresses of site-local and global addresses that are started
by using ipv6 address autoconfig on an interface. An IPv6 host sends router solicitations to the
all-routers multicast group to obtain router advertisements.
IPv6 routers also periodically send router advertisements, but the delay between successive
advertisements is generally a longer duration than for what a host performing autoconfiguration will
wait. Router advertisements contain zero or more prefix information options that contain information
that the stateless address autoconfiguration uses to generate site-local and global addresses.
Prefix information options specify the prefixes that are on-link and are used for address
autoconfiguration. A router includes all of its on-link prefixes (except the link-local prefix) so that
multihome hosts have complete prefix information about on-link destinations for the links to which they
attach.
The autogenerated address is obtained by appending the interface IEEE EUI-64 to the prefix in the prefix
information option in the router advertisement. If the sum of the prefix length and interface identifier
length does not equal 128 bits, the prefix information option is ignored.
IPv6 Applications
The switch has IPv6 support for these applications:
Ping, traceroute, Telnet, TFTP, and FTP
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 with Cisco IOS, see the Managing Cisco IOS
Applications over IPv6 section in the Cisco IOS IPv6 Configuration Library at this URL:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1839/products_feature_guide09186a00807fcf4b.
html
Dual IPv4 and IPv6 Protocol Stacks
One technique for transitioning to IPv6 is by using dual IPv4 and IPv6 protocol stacks. Using dual stacks
enables gradual, one-by-one upgrades to applications running on nodes. Applications that are upgraded
to IPv6 use the IPv6 protocol stack, and applications that are not upgraded and support only IPv4 can
coexist with upgraded applications on the same node. New and upgraded applications can use both IPv4
and IPv6 protocol stacks.
The Cisco IOS software supports the dual IPv4 and IPv6 protocol stack technique. When both IPv4 and
IPv6 routing are enabled and an interface is configured with both an IPv4 and IPv6 address, the interface
forwards both IPv4 and IPv6 traffic.
Figure 39-1 shows a router forwarding both IPv4 and IPv6 traffic through the same interface, based on
the IP packet and destination addresses.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
39-7
Chapter 39
Configuring IPv6 Host Functions and Unicast Routing
Understanding IPv6
Figure 39-1
Dual IPv4 and IPv6 Support on an Interface
IPv4
201786
10.1.1.1
IPv6
3ffe:yyyy::1
The switch uses hardware memory to store unicast routes, MAC addresses, access control lists (ACLs),
and other features, and provides the switch database management (SDM) templates to allocate memory
resources depending on how the switch is used. You must use the dual IPv4 and IPv6 template templates
to allocate hardware memory usage to both IPv4and IPv6 protocols. See the SDM Templates section
on page 39-13.
EIGRP IPv6
This section applies only to the Catalyst Switch Module 3110.
Enhanced Interior Gateway Routing Protocol (EIGRP) IPv6 is supported. The IPv6 commands duplicate
the functionality of their counterpart commands for IPv4. EIGRP IPv6 can be configured directly on the
interfaces on which it runs and therefore does not require a global IPv6 address.
This example shows the minimum configuration required for EIGRP IPv6:
!
ipv6 unicast-routing
!
interface e0
ipv6 enable
ipv6 eigrp 1
no shutdown
!
ipv6 router eigrp 1
router-id 1.1.1.1
no shutdown
enable IPv6 packet forwarding
enable IPv6 on the interface (or configure global address)
enable EIGRP IPv6 for AS 1 (Nvgens router process)
router process for AS 1
A explicit router id on this IPv6-only node
process is not shutdown
You can use this configuration allows you to send hellos to establish adjacencies (on Ethernet 0).
However, to do so, it must also meet the these conditions:
IPv6 unicast packet forwarding is enabled.
IPv6 is enabled by entering the ipv6 enable command on the interface or on a global IPv6 address.
The interface has its line protocol running.
The router process is running.
The router process has a router ID.
EIGRP IPv6 can be configured on an interface. However, after being configured on an interface, it can
start running before any of the EIGRP IPv6 router-mode commands have been executed. This is
undesired, so, by default, EIGRP IPv6 is in a shutdown state. After you configure the router and interface
for EIGRP IPv6, then you can enter the no shutdown command to start the protocol. This ensures that
all router-mode configurations are executed before the protocol starts.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
39-8
OL-12189-01
Chapter 39
Configuring IPv6 Host Functions and Unicast Routing
Understanding IPv6
Prefix Lists
Use the distribute-list prefix-list command to define which networks running EIGRP IPv6 are to
receive routing updates. The route-map command is not supported for route filtering with a distributed
list.
Router ID
An instance of EIGRP IPv6 requires that you have a router ID before it can run. As with IPv4, EIGRP
IPv6 supports implicit and explicit router IDs. An implicit router ID is derived from a local IPv4 address,
so any IPv4 node always has an available router ID. However, EIGRP IPv6 might be running in a network
with only IPv6 nodes and therefore might not have an available IPv4 router ID. You can use the show
ipv6 eigrp command to see whether a router ID has been configured, and you can use the router-id
command to set an explicit router ID.
Passive Interfaces
As with EIGRP IPv4, you can use EIGRP IPv6 to specify your EIGRP IPv4 interfaces and to select a
subset of those to be passive interfaces. Use the passive-interface default command to make all
interfaces passive, and then use the no passive-interface command on selected interfaces to make them
active. EIGRP IPv6 does not need to be configured on a passive interface.
EIGRP IPv6 Commands
Table 39-2 shows the supported interface commands for EIGRP IPv6 on the switch.
Table 39-2
EIGRP IPv6 Interface Commands for EIGRP IPv6
Command
Purpose
ipv6 eigrp as-number
Enables EIGRP IPv6 on a specified interface.
ipv6 authentication key-chain eigrp 1 name
Enables authentication of EIGRP IPv6 packets.
ipv6 authentication mode eigrp as-number md5
Specifies the type of authentication used in EIGRP IPv6 packets.
ipv6 bandwidth-percent eigrp as-number percent
Configures the percentage of bandwidth that can be used by EIGRP
IPv6 on an interface.
ipv6 hello-interval eigrp as-number seconds
Configures the hello interval for the EIGRP IPv6 routing process
designated by an autonomous system number.
ipv6 hold-time eigrp as-number seconds
Configures the hold time for a particular EIGRP IPv6 routing process
designated by the autonomous system number.
ipv6 next-hop-self eigrp as-number
Informs the EIGRP IPv6 router that the IPv6 next hop is itself.
ipv6 split-horizon eigrp as-number
Enables EIGRP IPv6 split horizon.
ipv6 summary-address eigrp as-number ipv6-prefix
[admin-distance]
Configures a summary aggregate address for a specified interface.
For more complete syntax and usage information on these commands, see the Cisco IOS command
references.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
39-9
Chapter 39
Configuring IPv6 Host Functions and Unicast Routing
Understanding IPv6
Table 39-3 shows the supported EIGRP IPv6 router configuration commands.
Table 39-3
EIGRP IPv6 Router-mode Commands
Command
Purpose
ipv6 router eigrp as-number
Specifies the EIGRP IPv6 routing process to be configured.
default-metric bandwidth delay reliability loading mtu Sets metrics for EIGRP IPv6.
distance internal-distance external-distance
Allows the use of the best route to a nodeeither the internal or
external distance.
distribute-list prefix-list list-name
Applies a prefix list to EIGRP IPv6 routing updates that are received
or sent on an interface.
log-neighbor-changes
Enables the logging of changes in EIGRP IPv6 neighbor
adjacencies.
log-neighbor-warnings seconds
Enables the logging of EIGRP neighbor warning messages.
maximum-paths number-paths
Controls the maximum number of equal-cost routes that is
supported by a routing process for EIGRP IPv6.
metric weights tos k1 k2 k3 k4 k5
Tunes EIGRP metric calculations.
neighbor n:n:n:n::n interface-name
Defines a neighboring router with which to exchange routing
information on a router that is running EIGRP.
passive-interface [interface-name | default]
Disables sending routing updates on an interface.
redistribute source-protocol [process-id]
[include-connected] [target-protocol-options]
[source-protocol-options]
Redistributes IPv6 routes from one routing domain into another
routing domain.
router-id {ip-address | ipv6-address}
Uses a fixed router ID.
shutdown
Allows the user to shut down the EIGRP protocol. The no version
of this command starts EIGRP IPv6 without changing any
per-interface configuration.
stub [connected | receive-only | static | summary |
redstributed]
Configures a router as a stub that uses EIGRP.
timers active-time [time-limit | disabled]
Adjusts routing wait time.
variance multiplier
Controls load balancing in an internetwork based on EIGRP.
For more complete syntax and usage information on these commands, see the Cisco IOS command
references.
EIPRP IPv6 supports the existing protocol-independent debug and show commands. Table 39-4 shows
the supported show, debug, and clear commands for EIGRP IPv6.
Table 39-4
EIGRP IPv6 Show and Debug Commands
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.
show ipv6 eigrp [as-number] traffic
Displays the number of EIGRP IPv6 packets sent and received.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
39-10
OL-12189-01
Chapter 39
Configuring IPv6 Host Functions and Unicast Routing
Understanding IPv6
Table 39-4
EIGRP IPv6 Show and Debug Commands (continued)
Command
Purpose
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]
debug ipv6 eigrp [as-number] [neighbor ipv6-address Displays information about EIGRP IPv6.
| notification | summary]
debug eigrp fsm
Displays debugging information about EIGRP feasible successor
metrics (FSMs).
debug eigrp neighbors
Displays neighbors discovered by EIGRP.
debug eigrp packet
Displays debugging information for EIGRP IPv6 packets.
debug eigrp transmit
Displays messages sent by EIGRP.
debug eigrp nsf
Displays NSF notifications and information about NSF events in an
EIGRP network.
clear ipv6 eigrp [as-number] [neighbor ipv6-address] Deletes entries from EIGRP IPv6 routing tables.
For complete syntax and usage information on these commands, see the Cisco IOS command references.
Unsupported IPv6 Host Functions and Unicast Routing Features
The Catalyst Switch Module 3110 does not support these IPv6 features:
IPv6 policy-based routing
IPv6 virtual private network (VPN) routing and forwarding (VRF) table support
Support for these IPv6 routing protocols: Multiprotocol Border Gateway Protocol (BGP),
Intermediate System-to-Intermediate System (IS-IS) routing
Simple Network Management Protocol (SNMP) over IPv6 transport
IPv6 Hot Standby Router Protocol (HSRP)
DHCPv6
IPv6 packets destined to site-local addresses
Tunneling protocols, such as IPv4-to-IPv6 or IPv6-to-IPv4
The switch as a tunnel endpoint supporting IPv4-to-IPv6 or IPv6-to-IPv4 tunneling protocols
IPv6 unicast reverse-path forwarding
IPv6 general prefixes
The Catalyst Switch Module 3012 does not support these IPv6 host functions:
IPv6 unicast routing
IPv6 multicast routing
IPv6 QoS
Most IPv6 ACLs
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
39-11
Chapter 39
Configuring IPv6 Host Functions and Unicast Routing
Understanding IPv6
Limitations
This section applies only to the Catalyst Switch Module 3110.
Because IPv6 is implemented in hardware in the switch, some limitations occur due to the use of IPv6
compressed addresses in the hardware memory. These hardware limitations result in some loss of
functionality and limits some features.
These are feature limitations.
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. These packets are corrupted before
being forwarded (bridged or routed) and reach the network as corrupted packets.
Note
There is a similar limitation for IPv4 SNAP-encapsulated packets, but the packets are
dropped at the switch and are not forwarded as corrupted packets.
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 egress RSPAN IPv6-routed packets, the source MAC address in the SPAN output
packet can be corrupted.
When you egress RSPAN IPv6-routed packets, the destination MAC address can be corrupted.
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.
IPv6 and Switch Stacks
This section applies only to the Catalyst Switch Module 3110.
The switch supports IPv6 forwarding across the stack much as it does with IPv4 unicast routing. The
stack master runs the IPv6 unicast routing protocols and computes the routing tables. Using distributed
CEF (dCEF), the stack master downloads the routing table to the stack member switches. The member
switches receive the tables and install IPv6 routes into hardware for hardware forwarding.
Note
To route IPv6 packets in a stack, all switches in the stack must be running the advanced IP services
feature set.
If a new switch becomes the stack master, the new master recomputes the IPv6 routing tables and
distributes them to the member switches. While the new stack master is being elected and is resetting,
the switch stack does not forward IPv6 packets. The stack MAC address also changes. When the IPv6
address of the stack is specified with an extended universal identifier (EUI) by using the ipv6 address
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
39-12
OL-12189-01
Chapter 39
Configuring IPv6 Host Functions and Unicast Routing
Understanding IPv6
ipv6-prefix/prefix length eui-64 interface configuration command, the address is based on the interface
MAC address. Changing the MAC address also changes the IPv6 address. See the Configuring IPv6
Addressing and Enabling IPv6 Host Functions or Routing section on page 39-16.
Note
If you configure the persistent MAC address feature on the stack and the stack master changes, the stack
MAC address does not change for approximately 4 minutes. If the previous stack master rejoins the stack
as a member switch during that time, the stack MAC address remains the same MAC address of the
previous stack master. See the Enabling Persistent MAC Address section on page 5-22 in Chapter 5,
Managing Switch Stacks.
These are the functions of IPv6 stack master and members:
Stack master:
runs IPv6 routing protocols
generates routing tables
distributes CEFv6 routing tables to stack members that use dCEFv6
runs IPv6 host functionality and IPv6 applications
Stack member (must be running the advanced IP services feature set):
receives CEFv6 routing tables from the stack master
programs the routes into hardware
Note
IPv6 packets are routed in hardware across the stack if the packet does not have exceptions
(IPv6Options) and the switches in the stack have not run out of hardware resources.
flushes the CEFv6 tables on master re-election
With IPv4 unicast routing, if the stack detects that the stack master is down and elects one of the stack
members the new stack master, except for a momentary interruption, the hardware continues to forward
packets with no active protocols. With IPv6, the switch does not continue forwarding packets. On
election of a new stack master, the stack might need up to 60 seconds to recover all routes and resume
forwarding traffic.
IPv6 host functionality is supported on the stack master, and all IPv6 applications run on the stack
master.
SDM Templates
To allocate system resources for unicast routes, MAC addresses, ACLs and other features, the switch
SDM templates prioritize system resources to optimize support for certain features. You select the
template that best suits the switch environment by entering the sdm prefer global configuration
command. For more information about SDM templates, see Chapter 8, Configuring SDM Templates.
You can select SDM templates to support IPv6. The dual IPv4 and IPv6 templates allow the switch to be
used in dual stack environments (supporting both IPv4 and IPv6).
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
security and QoS ACLs. The switch also routes IPv6 security ACLs in hardware.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
39-13
Chapter 39
Configuring IPv6 Host Functions and Unicast Routing
Understanding IPv6
If you try to configure IPv6 without first selecting a dual IPv4 and IPv6 template, a warning message
appears.
Note
Using the dual stack templates allows less hardware memory capacity for each resource, so do not use
if you plan to forward only IPv4 traffic.
Dual IPv4-and IPv6 SDM Templates
These SDM templates support IPv4 and IPv6 environments:
Note
Note
IPv6 Multicast Listener Discovery (MLD) snooping is supported, but IPv6 multicast routing or QoS is
not supported.
Dual IPv4 and IPv6 default templatesupports Layer 2, multicast, routing, QoS, and ACLs for
IPv4; and Layer 2, routing, and ACLs for IPv6 on the switch.
Dual IPv4 and IPv6 routing templatesupports Layer 2, multicast, routing (including policy-based
routing), QoS, and ACLs for IPv4; and Layer 2, routing, and ACLs for IPv6 on the switch.
Dual IPv4 and IPv6 VLAN templatesupports basic Layer 2, multicast, QoS, and ACLs for IPv4;
and basic Layer 2 and ACLs for IPv6 on the switch.
An IPv4 route requires only one hardware entry. Because of the hardware compression scheme used for
IPv6, an IPv6 route can take more than one hardware entry, reducing the number of entries forwarded in
hardware. For example, for IPv6 directly connected IP addresses, the desktop template might allow less
than two thousand entries.
Table 39-5 defines the approximate feature resources allocated by each new template. Template
estimations are based on a switch with eight routed interfaces and approximately one thousand VLANs.
Table 39-5
Approximate Feature Resources Allowed by Dual IPv4-IPv6 Templates
Resource
IPv4-and-IPv6
Default
IPv4-and-IPv6
Routing
IPv4-and-IPv6
VLAN
Unicast MAC addresses
2K
1.5 K
8K
IPv4 IGMP groups and multicast routes
1K
1K
1 K for IGMP
groups
0 for multicast
routes
Total IPv4 unicast routes:
3K
2.75 K
Directly connected IPv4 hosts
2K
1.5 K
Indirect IPv4 routes
1K
1.25 K
IPv6 multicast groups
1K
1K
1K
Directly connected IPv6 addresses
2K
1.5 K
Indirect IPv6 unicast routes
1K
1.25 K
0.25 K
IPv4 policy-based routing ACEs
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
39-14
OL-12189-01
Chapter 39
Configuring IPv6 Host Functions and Unicast Routing
Configuring IPv6
Table 39-5
Approximate Feature Resources Allowed by Dual IPv4-IPv6 Templates (continued)
Resource
IPv4-and-IPv6
Default
IPv4-and-IPv6
Routing
IPv4-and-IPv6
VLAN
IPv4 or MAC QoS ACEs (total)
0.5 K
0.5 K
0.5 K
IPv4 or MAC security ACEs (total)
1K
0.5 K
1K
IPv6 security ACEs
1K
1K
1K
1. IPv6 policy-based routing is not supported on the Catalyst Switch Module 3012.
Configuring IPv6
These sections contain this IPv6 forwarding configuration information:
Default IPv6 Configuration, page 39-15
Configuring IPv6 Addressing and Enabling IPv6 Host Functions or Routing, page 39-16
Configuring IPv4 and IPv6 Protocol Stacks and Enabling IPv6 Routing, page 39-18 (only the
Catalyst Switch Module 3110)
Configuring IPv6 ICMP Rate Limiting, page 39-19
Configuring CEF and dCEF for IPv6, page 39-20 (only the Catalyst Switch Module 3110)
Configuring Static Routes for IPv6, page 39-21
Configuring RIP for IPv6, page 39-23 (only the Catalyst Switch Module 3110)
Configuring OSPF for IPv6, page 39-25 (only the Catalyst Switch Module 3110)
Default IPv6 Configuration
Table 39-6 shows the default IPv6 configuration.
Table 39-6
Default IPv6 Configuration
Feature
Default Setting
SDM template
IPv6 routing
Default desktop.
Disabled globally and on all interfaces.
CEFv6 or dCEFv6
Disabled (IPv4 CEF and dCEF are enabled by default).
Note
IPv6 addresses
When IPv6 routing is enabled, CEFv6 and dCEFv6 are automatically
enabled.
None configured.
1. This feature is supported only on the Catalyst Switch Module 3110.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
39-15
Chapter 39
Configuring IPv6 Host Functions and Unicast Routing
Configuring IPv6
Configuring IPv6 Addressing and Enabling IPv6 Host Functions or Routing
This section describes how to assign IPv6 addresses to a Layer 3 interface and to enable the forwarding
of IPv6 traffic globally on the switch.
Note
In the ipv6 address interface configuration command, you must enter the ipv6-address and ipv6-prefix
variables with the address specified in hexadecimal using 16-bit values between colons. The
prefix-length variable (preceded by a slash [/]) is 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).
For an interface to forward IPv6 traffic, you must configure an IPv6 address on the interface.
Configuring a global 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:
Note
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
Before configuring IPv6 on the switch, be sure to select a dual IPv4 and IPv6 SDM template.
For more information about configuring IPv6 routing, see the Implementing Addressing and Basic
Connectivity for IPv6 chapter in the Cisco IOS IPv6 Configuration Library at this URL:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1839/products_feature_guide09186a00807fcf4b.
html
Note
Not all features discussed in this chapter are supported by the switch. See the Unsupported IPv6
Host Functions and Unicast Routing Features section on page 39-11.
Beginning in privileged EXEC mode, follow these steps to assign an IPv6 address to a Layer 3 interface
and enable IPv6 forwarding:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
sdm prefer dual-ipv4-and-ipv6 {default |
routing | vlan}
Select an SDM template that supports IPv4 and IPv6.
defaultSet the switch to the default template to balance
system resources.
routingSet the switch to the routing template to support
IPv4 and IPv6 routing, including IPv4 policy-based routing.
vlanMaximize 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 has reloaded.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
39-16
OL-12189-01
Chapter 39
Configuring IPv6 Host Functions and Unicast Routing
Configuring IPv6
Command
Purpose
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).
Step 8
ipv6 address ipv6-prefix/prefix length eui-64
Specify a global IPv6 address with an extended universal
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 the interface.
or
ipv6 address ipv6-address link-local
or
Specify a link-local address on the interface to be used instead
of the link-local address that is automatically configured when
IPv6 is enabled on the interface. This command enables IPv6
processing on the interface.
ipv6 enable
Automatically configure an IPv6 link-local address on the
interface, and enable the interface for IPv6 processing. The
link-local address can only be used to communicate with nodes
on the same link.
Step 9
exit
Return to global configuration mode.
Step 10
ip routing
Enable IP routing on the switch.
Step 11
ipv6 unicast-routing
This step applies only to the Catalyst Switch Module 3110.
Enable forwarding of IPv6 unicast data packets.
Step 12
end
Return to privileged EXEC mode.
Step 13
show ip v6 interface interface-id
Verify your entries.
Step 14
copy running-config startup-config
(Optional) Save your entries in the configuration file.
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 on the Catalyst Switch Module 3110, use the no ipv6 unicast-routing global configuration
command.
This example shows how to enable an IPv6 host on an interface:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# no switchport
Switch(config-if)# ipv6 enable
Switch(config-if)# exit
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/0/1
Switch(config-if)# no switchport
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
39-17
Chapter 39
Configuring IPv6 Host Functions and Unicast Routing
Configuring IPv6
Switch(config-if)# ipv6 address 2001:0DB8:c18:1::/64 eui 64
Switch(config-if)# end
Switch# show ipv6 interface gigabitethernet1/0/1
GigabitEthernet1/0/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
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
Hosts use stateless autoconfig for addresses.
Configuring IPv4 and IPv6 Protocol Stacks and Enabling IPv6 Routing
This section applies only to the Catalyst Switch Module 3110.
When you configure an interface with both an IPv4 and IPv6 address, the interface forwards both IPv4
and IPv6 traffic and can send and receive data on both IPv4 and IPv6 networks.
Note
Before configuring IPv6 routing, you must select an SDM template that supports IPv4 and IPv6. If not
already configured, use the sdm prefer dual-ipv4-and-ipv6 {default | routing | vlan} global
configuration command to configure a template that supports IPv6. When you select a new template, you
must reload the switch by using the reload privileged EXEC command so that the template takes effect.
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
ip routing
Enable routing on the switch.
Step 3
ipv6 unicast-routing
Enable forwarding of IPv6 data packets on the switch.
Step 4
interface interface-id
Enter interface configuration mode, and specify the Layer 3
interface to configure.
Step 5
no switchport
Remove the interface from Layer 2 configuration mode (if it is a
physical interface).
Step 6
ip address ip-address mask [secondary]
Specify a primary or secondary IPv4 address for the interface.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
39-18
OL-12189-01
Chapter 39
Configuring IPv6 Host Functions and Unicast Routing
Configuring IPv6
Step 7
Command
Purpose
ipv6 address ipv6-prefix/prefix length eui-64
Specify a global IPv6 address with an interface identifier 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 the
interface.
or
ipv6 address ipv6-address link-local
or
Specify a link-local address on the interface to be used instead
of the link-local address that is automatically configured when
IPv6 is enabled on the interface. This command enables IPv6
processing on the interface.
ipv6 enable
Automatically configure an IPv6 link-local address on the
interface, and enable the interface for IPv6 processing. The
link-local address can only be used to communicate with nodes
on the same link.
Step 8
end
Return to privileged EXEC mode.
Step 9
show interface interface-id
Verify your entries.
show ip interface interface-id
show ip v6 interface interface-id
Step 10
copy running-config startup-config
(Optional) Save your entries in the configuration file.
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/0/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
Configuring IPv6 ICMP Rate Limiting
IPv6 ICMP rate limiting uses a token-bucket algorithm for limiting the rate at which IPv6 ICMP error
messages are sent to the network. The interval between error messages is specified in a time interval and
a bucket size. Because some applications, such as traceroute, sometimes require replies to a group of
requests to be sent in rapid succession, specifying only the interval between error messages can cause
the application to fail. The token bucket allows a number of tokens, each representing the ability to send
one error message, to be stored in virtual buckets. For every message to be sent, one token is removed
from the bucket. If a series of error messages is generated, error messages can be sent until the bucket is
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
39-19
Chapter 39
Configuring IPv6 Host Functions and Unicast Routing
Configuring IPv6
empty. When the bucket is empty, IPv6 ICMP error messages are not sent until a new token is placed in
the bucket. This method does not increase the average rate-limiting time interval, but it provides more
flexibility than fixed-time intervals.
ICMP rate limiting is enabled by default with a default interval between error messages of 100
milliseconds and a bucket size (maximum number of tokens to be stored in a bucket) of 10.
Beginning in privileged EXEC mode, follow these steps to change the ICMP rate-limiting parameters:
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:
intervalThe 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
Configuring CEF and dCEF for IPv6
This section applies only to the Catalyst Switch Module 3110.
Cisco Express Forwarding (CEF) is a Layer 3 IP switching technology that optimizes network
performance. CEF implements an advanced IP look-up and forwarding algorithm to deliver maximum
Layer 3 switching performance. It is less CPU-intensive than fast-switching route-caching, dedicating
more CPU processing power to packet forwarding. In a switch stack, the switch uses distributed CEF
(dCEF) in the stack. IPv4 CEF and dCEF are enabled by default. IPv6 CEF and dCEF are disabled by
default, but are automatically enabled when you configure IPv6 routing.
To route IPv6 unicast packets, you must first globally configure IPv6 unicast packet forwarding by using
the ipv6 unicast-routing global configuration command. You must configure an IPv6 address and IPv6
processing on an interface by using the ipv6 address interface configuration command.
To disable IPv6 CEF or distributed CEF, use the no ipv6 cef or no ipv6 cef distributed global
configuration command. To reenable IPv6 CEF or dCEF if it has been disabled, use the ipv6 cef or ipv6
cef distributed global configuration command. You can verify the IPv6 state by entering the show ipv6
cef privileged EXEC command.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
39-20
OL-12189-01
Chapter 39
Configuring IPv6 Host Functions and Unicast Routing
Configuring IPv6
Configuring Static Routes for IPv6
Static routes are manually configured and define an explicit route between two networking devices. The
benefits of static routes include security and resource efficiency. Static routes use less bandwidth than
dynamic routing protocols because routes are not calculated and communicated. The main disadvantage
of using static routes is that they are not automatically updated, as with a dynamic routing protocol, and
must be manually reconfigured if the network topology changes. Static routes are useful for smaller
networks with only one path to an outside network or to provide security for a larger network for certain
types of traffic.
There are types of static routes:
Note
Directly attached static routesOnly the output interface is specified because the destination is
assumed to be directly attached to this interface. The packet destination is used as the next hop
address. A directly attached static route is valid only when the specified interface is IPv6-enabled
and is up.
Recursive static routesOnly the next hop is specified, and the output interface is derived from the
next hop. A recursive static route is valid only when the specified next hop results in a valid IPv6
output interface, the route does not self-recur, and the recursion depth does not exceed the maximum
IPv6 forwarding recursion depth.
Fully specified static routesBoth the output interface and the next hop are specified. The next hop
is assumed to be directly attached to the specified output interface. A fully specified route is valid
when the specified IPv6 interface is IPv6-enabled and up.
Floating static routesAny of the three types of static routes can be floating static routes, used to
back up dynamic routes learned through configured routing protocols. A floating static route is
configured with a less efficient administrative distance than the routing protocol it backs up.
Therefore, the dynamic route is always used for routing traffic in preference to the floating static
route. If the dynamic route is lost, the floating static route is used.
Before configuring a static IPv6 route on a Catalyst Switch Module 3110, you must enable routing by
using the ip routing global configuration command, enable the forwarding of IPv6 packets by using the
ipv6 unicast-routing global configuration command, and enable IPv6 on at least one Layer 3 interface
by configuring an IPv6 address on the interface.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
39-21
Chapter 39
Configuring IPv6 Host Functions and Unicast Routing
Configuring IPv6
Beginning in privileged EXEC mode, follow these steps to configure an IPv6 static route:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ipv6 route ipv6-prefix/prefix length
{ipv6-address | interface-id [ipv6-address]}
[administrative distance]
Configure a static IPv6 route.
ipv6-prefixThe IPv6 network that is the destination of the
static route. It can also be a hostname when static host routes are
configured.
/prefix lengthThe 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-addressThe 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-idSpecify 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
Step 3
end
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).
administrative distance(Optional) An administrative distance.
The range is 1 to 254; the default value is 1, which gives static
routes precedence over any other type of route except connected
routes. To configure a floating static route, use an administrative
distance greater than that of the dynamic routing protocol.
Return to privileged EXEC mode.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
39-22
OL-12189-01
Chapter 39
Configuring IPv6 Host Functions and Unicast Routing
Configuring IPv6
Step 4
Command
Purpose
show ipv6 static [ipv6-address |
ipv6-prefix/prefix length] [interface
interface-id] [recursive] [detail]
Verify your entries by displaying the contents of the IPv6 routing
table.
or
interface interface-id(Optional) Display only those static
routes with the specified interface as an egress interface.
recursive(Optional) Display only recursive static routes. The
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.
detail(Optional) Display this additional information:
show ipv6 route static [updated]
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 gigabitethernet2/0/1 130
For more information about configuring static IPv6 routing, see the Implementing Static Routes for
IPv6 chapter in the Cisco IOS IPv6 Configuration Library at this URL:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1839/products_feature_guide09186a00807fcf4b.
html
Configuring RIP for IPv6
This section applies only to the Catalyst Switch Module 3110.
Routing Information Protocol (RIP) for IPv6 is a distance-vector protocol that uses hop count as a
routing metric. IPv6 RIP functions the same and offers the same benefits as RIP in IPv4. IPv6 RIP
enhancements include support for IPv6 addresses and prefixes and the use of the all-RIP-routers
multicast group address FF02::9 as the destination address for RIP update messages.
Each IPv6 RIP process maintains a local routing table, referred to as a Routing Information Database
(RIB), that contains a set of best-cost IPv6 routes learned from all its neighboring networking devices.
If IPv6 RIP learns the same route from two different neighbors, but with different costs, it stores only
the lowest-cost route in the local RIB. The RIB also stores any expired routes that the RIP process is
advertising to its neighbors that are running RIP. If the same route is learned from a different routing
protocol with a better administrative distance than IPv6 RIP, the RIP route is not added to the IPv6 RIB,
but the route still exists in the IPv6 RIP RIB.
Note
Before configuring the switch to run IPv6 RIP, you must enable routing by using the ip routing global
configuration command, enable the forwarding of IPv6 packets by using the ipv6 unicast-routing global
configuration command, and enable IPv6 on any Layer 3 interfaces on which IPv6 RIP is to be enabled.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
39-23
Chapter 39
Configuring IPv6 Host Functions and Unicast Routing
Configuring IPv6
Beginning in privileged EXEC mode, follow these required and optional steps to configure IPv6 RIP:
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 paths.
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.
Step 7
ipv6 rip name default-information {only |
originate}
(Optional) Originate the IPv6 default route (::/0) in the RIP
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.
onlySelect to originate the default route, but suppress all
other routes in the updates sent on this interface.
originateSelect to originate the default route in addition
to all other routes in the updates sent on this interface.
Step 8
end
Return to privileged EXEC mode.
Step 9
show ipv6 rip [name] [interface interface-id]
[database] [next-hops]
Display information about IPv6 RIP processes.
or
Step 10
show ipv6 route rip [updated]
Display the contents of the IPv6 routing table.
copy running-config startup-config
(Optional) Save your entries in the configuration file.
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 enable it on an interface:
Switch(config)# ipv6 router rip cisco
Switch(config-router)# maximum-paths 8
Switch(config)# exit
Switch(config)# interface gigabitethernet2/0/11
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 Library at this URL:
http://www.cisco.com/en/US/products/sw/iosswrel/ps5187/products_configuration_guide_chapter0918
6a00801d6601.html
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
39-24
OL-12189-01
Chapter 39
Configuring IPv6 Host Functions and Unicast Routing
Configuring IPv6
Configuring OSPF for IPv6
This section applies only to the Catalyst Switch Module 3110.
Open Shortest Path First (OSPF) is a link-state protocol for IP, which means that routing decisions are
based on the states of the links that connect the source and destination devices. The state of a link is a
description of the interface and its relationship to its neighboring networking devices. Interface
information, which is propagated in link-state advertisements (LSAs), includes the IPv6 prefix of the
interface, the network mask, the type of network it is connected to, the routers connected to that network,
and so on. LSA data is stored in a link-state database, which is used to create the OSPF routing table.
While the database contains a collection of raw data, the routing table contains a list of shortest paths to
known destinations that use specific Layer 3 ports. OSPF Version 2 (RFC 2740) supports IPv6.
OSPF for IPv6 is largely the same as OSPF Version 2 (for IPv4), expanded to provide support for IPv6
routing prefixes and the larger size of IPv6 addresses. However, there are these differences:
Enabling OSPF for IPv6 on an interface automatically creates a routing process and its associated
configuration; you do not need to explicitly create a routing process as in IPv4.
In OSPF for IPv6, you must enable OSPF on each interface by using commands in interface
configuration mode. In OSPF Version 2, interfaces are indirectly enabled by using router
configuration mode.
In IPv6, you can configure many address prefixes on an interface. All address prefixes configured
on an interface are included by default; you cannot select a subset of address prefixes to import.
Unlike OSPF Version 2, multiple instances of IPv6 can run on a link.
OSPF Version 2 uses the 32-bit IPv4 address configured on the interface to chose an IPv4 address
to use as the router ID. When you enable OSPF for IPv6 on an interface, if an IPv4 address is
configured on the interface that IP address is used for the IPv6 router ID. If no IPv4 address is
configured on the interface, you must use the router-id router configuration command to configure
a router ID before the OSFP process is started.
OSPF automatically chooses a loopback interface over other interfaces and chooses the highest IP
address among all loopback interfaces. If no loopback interfaces are present, OSPF selects the highest
IP address in the router. You cannot configure OSPF to use any particular interface.
You can customize OSPF for IPv6 for your network, but you will likely not need to. The defaults for
OSPF in IPv6 are set to meet the requirements of most customers and features.
Note
Be careful when changing the defaults for IPv6 commands. Changing the defaults might adversely affect
OSPF for the IPv6 network.
Before you enable IPv6 OSPF on an interface, you must enable routing by using the ip routing global
configuration command, enable the forwarding of IPv6 packets by using the ipv6 unicast-routing global
configuration command, and enable IPv6 on Layer 3 interfaces on which you are enabling IPv6 OSPF.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
39-25
Chapter 39
Configuring IPv6 Host Functions and Unicast Routing
Configuring IPv6
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}
[advertise | not-advertise] [cost cost]
(Optional) Consolidate and summarize routes at an area
boundary.
area-idIdentifier 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 lengthThe 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
instance-id]
Enable OSPF for IPv6 on the interface.
Step 8
end
Return to privileged EXEC mode.
Step 9
show ipv6 ospf [process-id] [area-id] interface
[interface-id]
Display information about OSPF interfaces.
instance instance-id(Optional) Instance identifier.
or
Step 10
show ipv6 ospf [process-id] [area-id]
Display general information about OSPF routing processes.
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
39-26
OL-12189-01
Chapter 39
Configuring IPv6 Host Functions and Unicast Routing
Displaying IPv6
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 Library at this URL:
http://www.cisco.com/en/US/products/sw/iosswrel/ps5187/products_configuration_guide_chapter0918
6a00801d660d.html
Displaying IPv6
Table 39-7 shows the privileged EXEC commands for monitoring IPv6 on the switch.
Table 39-7
Commands for Monitoring IPv6
Command
Purpose
show ipv6 access-list
show ipv6 cef
Display a summary of access lists.
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
show ipv6 ospf
Display IPv6 neighbor cache entries.
Display IPv6 OSPF information.
show ipv6 prefix-list
show ipv6 protocols
show ipv6 rip
Display a list of IPv6 prefix lists.
Display IPv6 routing protocols on the switch.
Display IPv6 RIP routing protocol status.
show ipv6 route
show ipv6 routers
Display the IPv6 route table entries.
1
Display the local IPv6 routers.
show ipv6 static
Display IPv6 static routes.
show ipv6 traffic
Display IPv6 traffic statistics.
1. This command is not supported on the Catalyst Switch Module 3012.
Table 39-8 shows the privileged EXEC commands for showing IPv4 and IPv6 address types on the switch.
Table 39-8
Commands for Monitoring IPv6
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
39-27
Chapter 39
Configuring IPv6 Host Functions and Unicast Routing
Displaying IPv6
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 on a Catalyst Switch
Module 3110:
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 GigabitEthernet1/0/11
3FFE:C000:111:1:20B:46FF:FE2F:D945/128
receive
3FFE:C000:168:1::/64
attached to GigabitEthernet2/0/13
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
GigabitEthernet2/0/4
GigabitEthernet2/0/11
GigabitEthernet1/0/12
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
39-28
OL-12189-01
Chapter 39
Configuring IPv6 Host Functions and Unicast Routing
Displaying IPv6
Redistribution:
None
This is an example of the output from the show ipv6 rip privileged EXEC command on a Catalyst Switch
Module 3110:
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
GigabitEthernet2/0/4
GigabitEthernet2/0/11
GigabitEthernet1/0/12
Redistribution:
None
This is an example of the output from the show ipv6 neighbor privileged EXEC command:
Switch# show ipv6 neighbors
IPv6 Address
3FFE:C000:0:7::777
3FFE:C101:113:1::33
Age Link-layer Addr State Interface
- 0007.0007.0007 REACH Vl7
- 0000.0000.0033 REACH Fa1/0/13
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 route privileged EXEC command on a Catalyst
Switch Module 3110:
Switch# show ipv6 route
IPv6 Routing Table - 21 entries
Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
U - Per-user Static route
I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary
O - OSPF intra, OI - OSPF inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
S
::/0 [1/0]
via 3FFE:C000:0:7::777
C
3FFE:C000:0:1::/64 [0/0]
via ::, Vlan1
L
3FFE:C000:0:1:20B:46FF:FE2F:D940/128 [0/0]
via ::, Vlan1
C
3FFE:C000:0:7::/64 [0/0]
via ::, Vlan7
L
3FFE:C000:0:7:20B:46FF:FE2F:D97F/128 [0/0]
via ::, Vlan7
C
3FFE:C000:111:1::/64 [0/0]
via ::, GigabitEthernet1/0/11
L
3FFE:C000:111:1:20B:46FF:FE2F:D945/128 [0/0]
C
3FFE:C000:168:1::/64 [0/0]
via ::, GigabitEthernet2/0/4
L
3FFE:C000:168:1:20B:46FF:FE2F:D94B/128 [0/0]
via ::, GigabitEthernet2/0/4
C
3FFE:C000:16A:1::/64 [0/0]
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
39-29
Chapter 39
Configuring IPv6 Host Functions and Unicast Routing
Displaying IPv6
via ::, Loopback10
3FFE:C000:16A:1:20B:46FF:FE2F:D900/128 [0/0]
via ::, Loopback10
<output truncated>
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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
39-30
OL-12189-01
CH A P T E R
40
Configuring HSRP
This chapter describes how to use Hot Standby Router Protocol (HSRP) on the switch to provide routing
redundancy for routing IP traffic without being dependent on the availability of any single router.Unless
otherwise noted, the term switch refers to a standalone switch and to a switch stack.
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 IP Command Reference, Volume 1 of 3:
Addressing and Services, Release 12.2.
This chapter consists of these sections:
Understanding HSRP, page 40-1
Configuring HSRP, page 40-4
Displaying HSRP Configurations, page 40-11
Understanding HSRP
HSRP is Ciscos 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 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
40-1
Chapter 40
Configuring HSRP
Understanding HSRP
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 groups 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 groups 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 disabled by default for the interface.
You can configure multiple Hot Standby groups among switches and switch stacks 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 blade servers 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 blade server C sends packets to blade server 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. Blade server C continues to use the IP address of the virtual router to address packets destined
for blade server B, which Router B now receives and sends to blade server B. Until Router A resumes
operation, HSRP allows Router B to provide uninterrupted service to users on blade server Cs segment
that need to communicate with users on blade server Bs segment and also continues to perform its
normal function of handling packets between the blade server A segment and blade server B.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
40-2
OL-12189-01
Chapter 40
Configuring HSRP
Understanding HSRP
Figure 40-1
Typical HSRP Configuration
Blade
server B
172.20.130.5
Virtual
router
172.20.128.1
Router A
Standby
router
172.20.128.3
172.20.128.2
Router B
172.20.128.55
172.20.128.32
Blade
server C
Blade
server A
201787
Active
router
Multiple HSRP
The switch supports Multiple HSRP (MHSRP), an extension of HSRP that allows load sharing between
two or more HSRP groups. You can configure MHSRP to achieve load-balancing and to use two or more
standby groups (and paths) from a blade server network to a server network.
In Figure 40-2, one enclosure with blade servers is configured for Router A, and the other enclosure with
blade servers is configured for Router B. Together, the configuration for Routers A and B establish two
HSRP groups. For group 1, Router A is the default active router because it has the assigned highest
priority, and Router B is the standby router. For group 2, Router B is the default active router because it
has the assigned highest priority, and Router A is the standby router. During normal operation, the two
routers share the IP traffic load. When either router becomes unavailable, the other router becomes active
and assumes the packet-transfer functions of the router that is unavailable.
See the Configuring MHSRP section on page 40-9 for the example configuration steps.
Note
For MHSRP, you need to enter the standby preempt interface configuration command on the HSRP
interfaces so that if a router fails and then comes back up, preemption occurs and restores load sharing
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
40-3
Chapter 40
Configuring HSRP
Configuring HSRP
Figure 40-2
MHSRP Load Sharing
Active router for group 1
Standby router for group 2
Active router for group 2
Standby router for group 1
Router A
Router B
10.0.0.1
10.0.0.2
Active link
Active link
Standby link
Blade switch
enclosure
with a
management
module
201791
Blade switch
enclosure
with a
management
module
Standby link
HSRP and Switch Stacks
HSRP hello messages are generated by the stack master. If an HSRP-active stack master fails, a flap in
the HSRP active state might occur. This is because HSRP hello messages are not generated while a new
stack master is elected and initialized, and the standby router might become active after the stack master
fails.
Configuring HSRP
These sections contain this configuration information:
Default HSRP Configuration, page 40-5
HSRP Configuration Guidelines, page 40-5
Enabling HSRP, page 40-5
Configuring HSRP Priority, page 40-7
Configuring MHSRP, page 40-9
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
40-4
OL-12189-01
Chapter 40
Configuring HSRP
Configuring HSRP
Configuring HSRP Authentication and Timers, page 40-10
Enabling HSRP Support for ICMP Redirect Messages, page 40-11
Default HSRP Configuration
Table 40-1 shows the default HSRP configuration.
Table 40-1
Default HSRP Configuration
Feature
Default Setting
HSRP groups
None configured
Standby group number
Standby MAC address
System assigned as: 0000.0c07.acXX, where XX is the HSRP
group number
Standby priority
100
Standby delay
0 (no delay)
Standby track interface priority
10
Standby hello time
3 seconds
Standby holdtime
10 seconds
HSRP Configuration Guidelines
Follow these guidelines when configuring HSRP:
HSRP can be configured on a maximum of 32 VLAN or routing interfaces.
In the procedures, the specified interface must be one of these Layer 3 interfaces:
Routed port: a physical port configured as a Layer 3 port by entering the no switchport
interface configuration command.
SVI: a VLAN interface created by using the interface vlan vlan_id global configuration
command and by default a Layer 3 interface.
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 37-14.
All Layer 3 interfaces must have IP addresses assigned to them. See the Configuring Layer 3
Interfaces section on page 10-20.
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
routing port on the cable with the designated address. Configuring an IP address always overrides
another designated address currently in use.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
40-5
Chapter 40
Configuring HSRP
Configuring HSRP
When the standby ip command is enabled on an interface and proxy ARP is enabled, if the interfaces
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.
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 [group-number] ip [ip-address
[secondary]]
Create (or enable) the HSRP group using its number and virtual IP
address.
(Optional) group-numberThe 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-addressThe 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) secondaryThe 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 4
end
Return to privileged EXEC mode.
Step 5
show standby [interface-id [group]]
Verify the configuration.
Step 6
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 a port. 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. Other configuration is
optional.
Switch# configure terminal
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# no switchport
Switch(config-if)# standby 1 ip
Switch(config-if)# end
Switch# show standby
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
40-6
OL-12189-01
Chapter 40
Configuring HSRP
Configuring HSRP
Configuring HSRP Priority
The standby priority, standby preempt, and standby track interface configuration commands are all
used to set characteristics for finding active and standby routers and behavior regarding when a new
active router takes over.
When configuring HSRP priority, follow these guidelines:
Assigning a priority allows you to select the active and standby routers. If preemption is enabled,
the router with the highest priority becomes the active router. If priorities are equal, the current
active router does not change. helps select the active and standby routers.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
40-7
Chapter 40
Configuring HSRP
Configuring HSRP
Step 3
Command
Purpose
standby [group-number] priority
priority [preempt [delay delay]]
Set a priority value used in choosing the active router. The range is 1 to 255;
the default priority is 100. The highest number represents the highest priority.
(Optional) group-numberThe group number to which the command
applies.
(Optional) preemptSelect so that when the local router has a higher
priority than the active router, it assumes control as the active router.
(Optional) delaySet to cause the local router to postpone taking over the
active role for the shown number of seconds. The range is 0 to
3600(1 hour); the default is 0 (no delay before taking over).
Use the no form of the command to restore the default values.
Step 4
standby [group-number] [priority Configure the router to preempt, which means that when the local router has
priority] preempt [delay delay]
a higher priority than the active router, it assumes control as the active router.
(Optional) group-numberThe group number to which the command
applies.
(Optional) priorityEnter to set or change the group priority. The range
is 1 to 255; the default is 100.
(Optional) delaySet to cause the local router to postpone taking over the
active role for the number of seconds shown. The range is 0 to 3600
(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
type number [interface-priority]
Configure an interface to track other interfaces so that if one of the other
interfaces goes down, the devices Hot Standby priority is lowered.
(Optional) group-numberThe group number to which the command
applies.
typeEnter the interface type (combined with interface number) that is
tracked.
numberEnter the interface number (combined with interface type) that is
tracked.
(Optional) interface-priorityEnter 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
startup-config
(Optional) Save your entries in the configuration file.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
40-8
OL-12189-01
Chapter 40
Configuring HSRP
Configuring HSRP
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.20.128.3
Switch(config-if)# standby priority 120 preempt delay 300
Switch(config-if)# end
Configuring MHSRP
To enable MHSRP and load-balancing, you configure two routers as active routers for their groups, with
virtual routers as standby routers. This example shows how to enable the MHSRP configuration shown
in Figure 40-2 on page 40-4. You need to enter the standby preempt interface configuration command
on each HSRP interface so that if a router fails and comes back up, the preemption occurs and restores
load-balancing.
Router A is configured as the active router for group 1, and Router B is configured as the active router
for group 2. The HSRP interface for Router A has an IP address of 10.0.0.1 with a group 1 standby
priority of 110 (the default is 100). The HSRP interface for Router B has an IP address of 10.0.0.2 with
a group 2 standby priority of 110.
Group 1 uses a virtual IP address of 10.0.0.3 and group 2 uses a virtual IP address of 10.0.0.4.
Router A Configuration
Switch# configure terminal
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# no switchport
Switch(config-if)# ip address 10.0.0.1 255.255.255.0
Switch(config-if)# standby 1 ip 10.0.0.3
Switch(config-if)# standby 1 priority 110
Switch(config-if)# standby 1 preempt
Switch(config-if)# standby 2 ip 10.0.0.4
Switch(config-if)# standby 2 preempt
Switch(config-if)# end
Router B Configuration
Switch# configure terminal
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# no switchport
Switch(config-if)# ip address 10.0.0.2 255.255.255.0
Switch(config-if)# standby 1 ip 10.0.0.3
Switch(config-if)# standby 1 preempt
Switch(config-if)# standby 2 ip 10.0.0.4
Switch(config-if)# standby 2 priority 110
Switch(config-if)# standby 2 preempt
Switch(config-if)# end
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
40-9
Chapter 40
Configuring HSRP
Configuring HSRP
Configuring HSRP Authentication and Timers
You can optionally configure an HSRP authentication string or change the hello-time interval and
holdtime.
When configuring these attributes, follow these guidelines:
The authentication string is sent unencrypted in all HSRP messages. You must configure the same
authentication string on all routers and access servers on a cable to ensure interoperation.
Authentication mismatch prevents a device from learning the designated Hot Standby IP address and
timer values from other routers configured with HSRP.
Routers or access servers on which standby timer values are not configured can learn timer values
from the active or standby router. The timers configured on an active router always override any
other timer settings.
All routers in a Hot Standby group should use the same timer values. Normally, the holdtime is
greater than or equal to 3 times the hellotime.
Beginning in privileged EXEC mode, use one or more of these steps to configure HSRP authentication
and timers 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 authentication.
Step 3
standby [group-number] authentication string
(Optional) authentication stringEnter 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-numberThe group number to which the
command applies.
Step 4
standby [group-number] timers hellotime
holdtime
(Optional) Configure the time between hello packets and the
time before other routers declare the active router to be down.
group-numberThe group number to which the command
applies.
hellotimeThe hello interval in seconds. The range is from
1 to 255; the default is 3 seconds.
holdtimeThe 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
40-10
OL-12189-01
Chapter 40
Configuring HSRP
Displaying HSRP Configurations
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
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
Enabling HSRP Support for ICMP Redirect Messages
ICMP redirect messages are automatically enabled on interfaces configured with HSRP. ICMP is a
network layer Internet protocol that provides message packets to report errors and other information
relevant to IP processing. ICMP provides diagnostic functions, such as sending and directing error packets
to the host. This feature filters outgoing ICMP redirect messages through HSRP, in which the next hop
IP address might be changed to an HSRP virtual IP address. For more information, see the Cisco IOS IP
Configuration Guide, Release 12.2.
Displaying HSRP Configurations
From privileged EXEC mode, use this command to display HSRP settings:
show standby [interface-id [group]] [brief] [detail]
You can display HSRP information for the whole switch, for a specific interface, for an HSRP group, or
for an HSRP group on an interface. You can also specify whether to display a concise overview of HSRP
information or detailed HSRP information. The default display is detail. If there are a large number of
HSRP groups, using the show standby command without qualifiers can result in an unwieldy display.
This is a an example of output from the show standby privileged EXEC command, displaying HSRP
information for two standby groups (group 1 and group 100):
Switch# show standby
VLAN1 - Group 1
Local state is Standby, priority 105, may preempt
Hellotime 3 holdtime 10
Next hello sent in 00:00:02.182
Hot standby IP address is 172.20.128.3 configured
Active router is 172.20.128.1 expires in 00:00:09
Standby router is local
Standby virtual mac address is 0000.0c07.ac01
Name is bbb
VLAN1 - Group 100
Local state is Active, priority 105, may preempt
Hellotime 3 holdtime 10
Next hello sent in 00:00:02.262
Hot standby IP address is 172.20.138.51 configured
Active router is local
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
40-11
Chapter 40
Configuring HSRP
Displaying HSRP Configurations
Standby router is unknown expired
Standby virtual mac address is 0000.0c07.ac64
Name is test
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
40-12
OL-12189-01
CH A P T E R
41
Configuring Cisco IOS IP SLAs Operations
This chapter describes how to use Cisco IOS IP Service Level Agreements (SLAs) on the 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 monitoringthe generation of traffic in a continuous,
reliable, and predictable mannerfor 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.
Unless otherwise noted, the term switch refers to a standalone switch and to a switch stack.
Note
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/products/ps6441/products_configuration_guide_book09186a0080707055
.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-14
Understanding Cisco IOS IP SLAs
Cisco IOS IP SLAs sends data across the network to measure performance between multiple network
locations or across multiple network paths. It simulates network data and IP services and collects
network performance information in real time. Cisco IOS IP SLAs generates and analyzes traffic either
between Cisco IOS devices or from a Cisco IOS device to a remote IP device such as a network
application server. Measurements provided by the various Cisco IOS IP SLAs operations can be used for
troubleshooting, for problem analysis, and for designing network topologies.
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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
41-1
Chapter 41
Configuring Cisco IOS IP SLAs Operations
Understanding Cisco IOS IP SLAs
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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
41-2
OL-12189-01
Chapter 41
Configuring Cisco IOS IP SLAs Operations
Understanding Cisco IOS IP SLAs
Using Cisco IOS IP SLAs to Measure Network Performance
You can use IP SLAs to monitor the performance between any area in the networkcore, distribution,
and edgewithout deploying a physical probe. It uses generated traffic to measure network performance
between two networking devices. Figure 41-1 shows how IP SLAs begins when the source device sends
a generated packet to the destination device. After the destination device receives the packet, depending
on the type of IP SLAs operation, it responds with time-stamp information for the source to make the
calculation on performance metrics. An IP SLAs operation performs a network measurement from the
source device to a destination in the network using a specific protocol such as UDP.
Figure 41-1
Cisco IOS IP SLAs Operation
Performance
management
application
Any IP device
IP SLA measurement
and IP SLA responder to
IP SLA Responder
IP network
IP SLA responder
IP SLA
121381
IP SLA
SNMP
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/products/ps6441/products_configuration_guide_book09186a0080707055
.html
Note
The switch does not support Voice over IP (VoIP) service level analysis or IP service level analysis using
DLSw+ operation. 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
41-3
Chapter 41
Configuring Cisco IOS IP SLAs Operations
Understanding Cisco IOS IP SLAs
IP SLAs Responder and IP SLAs Control Protocol
The IP SLAs responder is a component embedded in the destination Cisco device that allows the system
to anticipate and respond to IP SLAs request packets. The responder provides accurate measurements
without the need for dedicated probes. The responder uses the Cisco IOS IP SLAs Control Protocol to
provide a mechanism through which it can be notified on which port it should listen and respond. Only
a Cisco IOS device can be a source for a destination IP SLAs Responder.
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.
Response Time Computation for IP SLAs
Switches and routers can take tens of milliseconds to process incoming packets due to other high priority
processes. This delay affects the response times because the test-packet reply might be in a queue while
waiting to be processed. In this situation, the response times would not accurately represent true network
delays. IP SLAs minimizes these processing delays on the source device as well as on the target device
(if the responder is being used) to determine true round-trip times. IP SLAs test packets use time
stamping to minimize the processing delays.
When the IP SLAs responder is enabled, it allows the target device to take time stamps when the packet
arrives on the interface at interrupt level and again just as it is leaving, eliminating the processing time.
This time stamping is made with a granularity of sub-milliseconds (ms).
Figure 41-2 demonstrates how the responder works. Four time stamps are taken to make the calculation
for round-trip time. At the target router, with the responder functionality enabled, time stamp 2 (TS2) is
subtracted from time stamp 3 (TS3) to produce the time spent processing the test packet as represented
by delta. This delta value is then subtracted from the overall round-trip time. Notice that the same
principle is applied by IP SLAs on the source router where the incoming time stamp 4 (TS4) is also taken
at the interrupt level to allow for greater accuracy.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
41-4
OL-12189-01
Chapter 41
Configuring Cisco IOS IP SLAs Operations
Understanding Cisco IOS IP SLAs
Figure 41-2
Cisco IOS IP SLAs Responder Time Stamping
Source router
T2
T1
Target router
Responder
=T3-T2
RTT (Round-trip time) = T4 (Time stamp 4) - T1 (Time stamp 1) -
121380
T3
T4
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.
IP SLAs Operation Scheduling
When you configure an IP SLAs operation, you must schedule the operation to begin capturing statistics
and collecting error information. You can schedule an operation to start immediately or to start at a
certain month, day, and hour. You can use the pending option to set the operation to start at a later time.
The pending option is an internal state of the operation that is visible through SNMP. The pending state
is also used when an operation is a reaction (threshold) operation waiting to be triggered. You can
schedule a single IP SLAs operation or a group of operations at one time.
You can schedule several IP SLAs operations by using a single command through the Cisco IOS CLI or
the CISCO RTTMON-MIB. Scheduling the operations to run at evenly distributed times allows you to
control the amount of IP SLAs monitoring traffic. This distribution of IP SLAs operations helps
minimize the CPU utilization and thus improves network scalability.
For more details about the IP SLAs multioperations scheduling functionality, see the IP
SLAsMultiple Operation Scheduling chapter of the Cisco IOS IP SLAs Configuration Guide at this
URL:
http://www.cisco.com/en/US/products/ps6441/products_configuration_guide_book09186a0080707055
.html
IP SLAs Operation Threshold Monitoring
To support successful service level agreement monitoring, you must have mechanisms that notify you
immediately of any possible violation. IP SLAs can send SNMP traps that are triggered by events such
as these:
Connection loss
Timeout
Round-trip time threshold
Average jitter threshold
One-way packet loss
One-way jitter
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
41-5
Chapter 41
Configuring Cisco IOS IP SLAs Operations
Configuring IP SLAs Operations
One-way mean opinion score (MOS)
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 SLAsProactive Threshold Monitoring chapter of the Cisco IOS IP SLAs
Configuration Guide at this URL:
http://www.cisco.com/en/US/products/ps6441/products_configuration_guide_book09186a0080707055
.html
Configuring IP SLAs Operations
This section does not include configuration information for all available operations as the configuration
information details are included in the Cisco IOS IP SLAs Configuration Guide. It does include several
operations as examples, including configuring the responder, configuring UDP jitter operation, which
requires a responder, and configuring ICMP echo operation, which does not require a responder. For
details about configuring other operations, see he Cisco IOS IP SLAs Configuration Guide at this URL:
http://www.cisco.com/en/US/products/ps6441/products_configuration_guide_book09186a0080707055
.html
This section includes this information:
Default Configuration, page 41-6
Configuration Guidelines, page 41-6
Configuring the IP SLAs Responder, page 41-8
Analyzing IP Service Levels by Using the UDP Jitter Operation, page 41-8
Analyzing IP Service Levels by Using the ICMP Echo Operation, page 41-11
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/products/ps6441/products_configuration_guide_book09186a0080707055
.html
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
41-6
OL-12189-01
Chapter 41
Configuring Cisco IOS IP SLAs Operations
Configuring IP SLAs Operations
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 analysis or IP
service level analysis by using DLSw+ operation.
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
Estimated
Number of
Number of
Number of
Number of
Type
Type
Type
Type
Type
Type
Type
Type
Type
Type
Type
Type
of
of
of
of
of
of
of
of
of
of
of
of
number of configurable operations: 15801
Entries configured : 0
active Entries
: 0
pending Entries
: 0
inactive Entries
: 0
Supported
Operation
Operation
Operation
Operation
Operation
Operation
Operation
Operation
Operation
Operation
Operation
Operation
Operation Types
to Perform: 802.1agEcho
to Perform: 802.1agJitter
to Perform: dhcp
to Perform: dns
to Perform: echo
to Perform: ftp
to Perform: http
to Perform: jitter
to Perform: pathEcho
to Perform: pathJitter
to Perform: tcpConnect
to Perform: udpEcho
IP SLAs low memory water mark: 21741224
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
41-7
Chapter 41
Configuring Cisco IOS IP SLAs Operations
Configuring IP SLAs Operations
Configuring the IP SLAs Responder
The IP SLAs responder is available only on Cisco IOS software-based devices, including some Layer 2
switches that do not support full IP SLAs functionality, such as the Catalyst 2960 switch, the Cisco
ME 2400 switch, or the Catalyst Switch Module 3012. Beginning in privileged EXEC mode, follow
these steps to configure the IP SLAs responder on the target device (the operational target):
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ip sla responder {tcp-connect |
udp-echo} ipaddress ip-address port
port-number
Configure the switch as an IP SLAs responder.
The keywords have these meanings:
tcp-connectEnable the responder for TCP connect operations.
udp-echoEnable the responder for User Datagram Protocol (UDP)
echo or jitter operations.
ipaddress ip-addressEnter the destination IP address.
port port-numberEnter 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.
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
Analyzing IP Service Levels by Using the UDP Jitter Operation
Jitter means interpacket delay variance. When multiple packets are sent consecutively 10 ms apart from
source to destination, if the network is behaving correctly, the destination should receive them 10 ms
apart. But if there are delays in the network (like queuing, arriving through alternate routes, and so on)
the arrival delay between packets might be more than or less than 10 ms with a positive jitter value
meaning that the packets arrived more than 10 ms apart. If the packets arrive 12 ms apart, positive jitter
is 2 ms; if the packets arrive 8 ms apart, negative jitter is 2 ms. For delay-sensitive networks, positive
jitter values are undesirable, and a jitter value of 0 is ideal.
In addition to monitoring jitter, the IP SLAs UDP jitter operation can be used as a multipurpose data
gathering operation. The packets IP SLAs generates carry packet sending and receiving sequence
information and sending and receiving time stamps from the source and the operational target. Based on
these, UDP jitter operations measure this data:
Per-direction jitter (source to destination and destination to source)
Per-direction packet-loss
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
41-8
OL-12189-01
Chapter 41
Configuring Cisco IOS IP SLAs Operations
Configuring IP SLAs Operations
Per-direction delay (one-way delay)
Round-trip delay (average round-trip time)
Because the paths for the sending and receiving of data can be different (asymmetric), you can use the
per-direction data to more readily identify where congestion or other problems are occurring in the
network.
The UDP jitter operation generates synthetic (simulated) UDP traffic and sends a number of UDP
packets, each of a specified size, sent a specified number of milliseconds apart, from a source router to
a target router, at a given frequency. By default, ten packet-frames, each with a payload size of 10 bytes
are generated every 10 ms, and the operation is repeated every 60 seconds. You can configure each of
these parameters to best simulate the IP service you want to provide.
To provide accurate one-way delay (latency) measurements, time synchronization, such as that provided
by NTP, is required between the source and the target device. Time synchronization is not required for
the one-way jitter and packet loss measurements. If the time is not synchronized between the source and
target devices, one-way jitter and packet loss data is returned, but values of 0 are returned for the
one-way delay measurements provided by the UDP jitter operation
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
41-9
Chapter 41
Configuring Cisco IOS IP SLAs Operations
Configuring IP SLAs Operations
Command
Step 3
Purpose
udp-jitter {destination-ip-address Configure the IP SLAs operation as a UDP jitter operation, and enter UDP
jitter configuration mode.
| destination-hostname}
destination-port [source-ip
destination-ip-address | destination-hostnameSpecify the destination IP
{ip-address | hostname}]
address or hostname.
[source-port port-number]
destination-portSpecify the destination port number in the range from 1
[control {enable | disable}]
to 65535.
[num-packets number-of-packets]
[interval interpacket-interval]
(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-numberSpecify 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) controlEnable 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-packetsEnter the number of
packets to be generated. The range is 1 to 6000; the default is 10.
(Optional) interval inter-packet-intervalEnter 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.
Step 6
Configure the scheduling parameters for an individual IP SLAs operation.
ip sla monitor schedule
operation-number [life {forever |
operation-numberEnter the RTR entry number.
seconds}] [start-time {hh:mm [:ss]
[month day | day month] | pending (Optional) lifeSet the operation to run indefinitely (forever) or for a
specific number of seconds. The range is from 0 to 2147483647. The
| now | after hh:mm:ss] [ageout
default is 3600 seconds (1 hour).
seconds] [recurring]
(Optional) start-timeEnter 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 secondsEnter 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) recurringSet the operation to automatically run every day.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
41-10
OL-12189-01
Chapter 41
Configuring Cisco IOS IP SLAs Operations
Configuring IP SLAs Operations
Command
Purpose
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:
Analyzing IP Service Levels by Using the ICMP Echo Operation
The ICMP echo operation measures end-to-end response time between a Cisco device and any devices
using IP. Response time is computed by measuring the time taken between sending an ICMP echo
request message to the destination and receiving an ICMP echo reply. Many customers use IP SLAs
ICMP-based operations, in-house ping testing, or ping-based dedicated probes for response time
measurements between the source IP SLAs device and the destination IP device. The IP SLAs ICMP
echo operation conforms to the same specifications as ICMP ping testing, and the two methods result in
the same response times.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
41-11
Chapter 41
Configuring Cisco IOS IP SLAs Operations
Configuring IP SLAs Operations
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.
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-hostnameSpecify 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-idSpecify 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
[life {forever | seconds}]
[start-time {hh:mm [:ss] [month
day | day month] | pending | now |
after hh:mm:ss] [ageout seconds]
[recurring]
Configure the scheduling parameters for an individual IP SLAs operation.
operation-numberEnter the RTR entry number.
(Optional) lifeSet 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-timeEnter 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.
Step 7
end
(Optional) ageout secondsEnter 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) recurringSet the operation to automatically run every day.
Return to privileged EXEC mode.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
41-12
OL-12189-01
Chapter 41
Configuring Cisco IOS IP SLAs Operations
Configuring IP SLAs Operations
Command
Purpose
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 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:
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
41-13
Chapter 41
Configuring Cisco IOS IP SLAs Operations
Monitoring IP SLAs Operations
Monitoring IP SLAs Operations
Use the user EXEC or privileged EXEC commands in Table 41-1 to display IP SLAs operations
configuration and results.
Table 41-1
Monitoring IP SLAs Operations
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
show ip sla mpls-lsp-monitor {collection-statistics |
configuration | ldp operational-state | scan-queue | summary
[entry-number] | neighbors}
Display MPLS label switched path (LSP) Health
Monitor operations,
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
41-14
OL-12189-01
CH A P T E R
42
Configuring Enhanced Object Tracking
This chapter describes how to configure enhanced object tracking on the Catalyst Switch Module 3110.
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, 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.
Unless otherwise noted, the term switch refers to a standalone switch and to a switch stack.
For more information about enhanced object tracking and the commands used to configure it, see this
URL:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1839/products_feature_guide09186a00801541be.
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-10
Understanding Enhanced Object Tracking
Each tracked object has a unique number that is specified in the tracking command-line interface (CLI).
Client processes use this number to track a specific object. The tracking process periodically polls the
tracked object for value changes and sends any changes (as up or down values) to interested client
processes, either immediately or after a specified delay. Several clients can track the same object, and
can take different actions when the object changes state.
You can also track a combination of objects in a list by using either a weight threshold or a percentage
threshold to measure the state of the list. You can combine objects using Boolean logic. A tracked list
with a Boolean AND function requires that each object in the list be in an up state for the tracked object
to be up. A tracked list with a Boolean OR function needs only one object in the list to be in the up
state for the tracked object to be up.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
42-1
Chapter 42
Configuring Enhanced Object Tracking
Configuring Enhanced Object Tracking Features
Configuring Enhanced Object Tracking Features
These sections describe configuring enhanced object tracking:
Default Configuration, page 42-2
Tracking Interface Line-Protocol or IP Routing State, page 42-2
Configuring a Tracked List, page 42-3
Configuring HSRP Object Tracking, page 42-7
Configuring Other Tracking Characteristics, page 42-8
Configuring IP SLAs Object Tracking, page 42-9
Default Configuration
No type of object tracking is configured.
Tracking Interface Line-Protocol or IP Routing State
You can track either the interface line protocol state or the interface IP routing state. When you track the
IP routing state, these three conditions are required for the object to be up:
IP routing must be enabled and active on the interface.
The interface line-protocol state must be up.
The interface IP address must be known.
If all three of these conditions are not met, the IP routing state is down.
Beginning in privileged EXEC mode, follow these steps to track the line-protocol state or IP routing state
of an interface:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
track object-number interface
interface-id line-protocol
(Optional) Create a tracking list to track the line-protocol state of an interface
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
interface-id ip routing
(Optional) Create a tracking list to track the IP routing state of an interface, and
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
42-2
OL-12189-01
Chapter 42
Configuring Enhanced Object Tracking
Configuring Enhanced Object Tracking Features
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
startup-config
(Optional) Save your entries in the configuration file.
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
Configuring a Tracked List
You can configure a tracked list of objects with a Boolean expression, a weight threshold, or a percentage
threshold. A tracked list contains one or more objects. An object must exist before it can be added to the
tracked list.
You configure a Boolean expression to specify calculation by using either AND or OR
operators.
When you measure the tracked list state by a weight threshold, you assign a weight number to each
object in the tracked list. The state of the tracked list is determined by whether or not the threshold
was met. The state of each object is determined by comparing the total weight of all objects against
a threshold weight for each object.
When you measure the tracked list by a percentage threshold, you assign a percentage threshold to
all objects in the tracked list. The state of each object is determined by comparing the assigned
percentages of each object to the list.
Configuring a Tracked List with a Boolean Expression
Configuring a tracked list with a Boolean expression enables calculation by using either AND or OR
operators. For example, when tracking two interfaces using the AND operator, up means that both
interfaces are up, and down means that either interface is down.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
42-3
Chapter 42
Configuring Enhanced Object Tracking
Configuring Enhanced Object Tracking Features
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
{and | or}
Configure a tracked list object, and enter tracking configuration mode. The
track-number can be from 1 to 500.
Step 3
object object-number [not]
booleanSpecify the state of the tracked list based on a Boolean
calculation.
andSpecify that the list is up if all objects are up or down if one or
more objects are down.
orSpecify that the list is up if one object is up or down if all objects
are down.
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] |
[up seconds] down seconds}
(Optional) Specify a period of time in seconds to delay communicating state
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
Switch(config-track)#
Switch(config-track)#
Switch(config-track)#
4 list boolean and
object 1
object 2 not
exit
Configuring a Tracked List with a Weight Threshold
To track by weight threshold, configure a tracked list of objects, specify that weight is used as the
threshold, and configure a weight for each of its objects. The state of each object is determined by
comparing the total weight of all objects that are up against a threshold weight for each object.
You cannot use the Boolean NOT operator in a weight threshold list.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
42-4
OL-12189-01
Chapter 42
Configuring Enhanced Object Tracking
Configuring Enhanced Object Tracking Features
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
weight
Configure a tracked list object and enter tracking configuration mode. The
track-number can be from 1 to 500.
Step 3
object object-number [weight
weight-number]
thresholdSpecify the state of the tracked list based on a threshold.
weightSpecify that the threshold is based on weight.
Specify the object to be tracked. The range is from 1 to 500. The optional
weight weight-number specifies a threshold weight for the object. The range
is from 1 to 255.
Note
Step 4
threshold weight {up number |
[down number]}
An object must exist before you can add it to a tracked list.
Specify the threshold weight.
up numberThe 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] |
[up seconds] down seconds}
(Optional) Specify a period of time in seconds to delay communicating state
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
Switch(config-track)#
Switch(config-track)#
Switch(config-track)#
Switch(config-track)#
Switch(config-track)#
4 list threshold weight
object 1 weight 15
object 2 weight 20
object 3 weight 30
threshold weight up 30 down 10
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.
Configuring a Tracked List with a Percentage Threshold
To track by percentage threshold, configure a tracked list of objects, specify that a percentage will be
used as the threshold, and specify a percentage for all objects in the list. The state of the list is determined
by comparing the assigned percentage of each object to the list.
You cannot use the Boolean NOT operator in a percentage threshold list.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
42-5
Chapter 42
Configuring Enhanced Object Tracking
Configuring Enhanced Object Tracking Features
Beginning in privileged EXEC mode, follow these steps to configure a tracked list of objects by using a
percentage threshold:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
track track-number list threshold
percentage
Configure a tracked list object and enter tracking configuration mode. The
track-number can be from 1 to 500.
Step 3
object object-number
thresholdSpecify the state of the tracked list based on a threshold.
percentageSpecify that the threshold is based on percentage.
Specify the object to be tracked. The range is from 1 to 500.
Note
Step 4
threshold percentage {up number |
[down number]}
An object must exist before you can add it to a tracked list.
Specify the threshold percentage.
up numberThe 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] |
[up seconds] down seconds}
(Optional) Specify a period of time in seconds to delay communicating state
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
Switch(config-track)#
Switch(config-track)#
Switch(config-track)#
Switch(config-track)#
Switch(config-track)#
4 list threshold percentage
object 1
object 2
object 3
threshold percentage up 51 down 10
exit
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
42-6
OL-12189-01
Chapter 42
Configuring Enhanced Object Tracking
Configuring Enhanced Object Tracking Features
Configuring HSRP Object Tracking
Beginning in privileged EXEC mode, follow these steps to configure a standby HSRP group to track an
object and change the HSRP priority based on the object state:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
track object-number {interface
interface-id {line-protocol | ip
routing} | ip route
ip-address/prefix-length {metric
threshold | reachability} | list
{boolean {and | or}} | {threshold
{weight | percentage}}}
(Optional) Create a tracking list to track the configured state and enter
tracking configuration mode.
The object-number range is from 1 to 500.
Enter interface interface-id to select an interface to track.
Enter line-protocol to track the interface line protocol state or enter ip
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-5
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
[ip-address [secondary]]
Create (or enable) the HSRP group by using its number and virtual IP
address.
(Optional) group-numberEnter 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-addressSpecify 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) secondarySpecify that the IP address is a secondary hot
standby router interface. If this keyword is omitted, the configured
address is the primary IP address.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
42-7
Chapter 42
Configuring Enhanced Object Tracking
Configuring Enhanced Object Tracking Features
Step 6
Command
Purpose
standby [group-number] track
object-number [decrement
[priority-decrement]]
Configure HSRP to track an object and change the hot standby priority based
on the state of the object.
(Optional) group-numberEnter the group number to which the
tracking applies.
object-numberEnter a number representing the object to be tracked.
The range is from 1 to 500; the default is 1.
(Optional) decrement priority-decrementSpecify 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.
Configuring Other Tracking Characteristics
You can also use the enhanced object tracking for tracking other characteristics.
You can track the reachability of an IP route by using the track ip route reachability global
configuration command.
You can use the track ip route metric threshold global configuration command to determine if a
route is above or below threshold.
You can use the track resolution global configuration command to change the metric resolution
default values for routing protocols.
You can use the track timer tracking configuration command to configure the tracking process to
periodically poll tracked objects.
Use the show track privileged EXEC command to verify enhanced object tracking configuration.
For more information about enhanced object tracking and the commands used to configure it, see this
URL:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1839/products_feature_guide09186a00801541be.
html
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
42-8
OL-12189-01
Chapter 42
Configuring Enhanced Object Tracking
Configuring Enhanced Object Tracking Features
Configuring IP SLAs Object Tracking
Cisco IOS IP Service Level Agreements (IP SLAs) is a network performance measurement and
diagnostics tool that uses active monitoring by generating traffic to measure network performance. Cisco
IP SLAs operations collects real-time metrics that you can use for network troubleshooting, design, and
analysis.
For more information about Cisco IP SLAs on the switch, see Chapter 41, Configuring Cisco IOS IP
SLAs Operations. For IP SLAs command information see the Cisco IOS IP SLAs Command Reference,
Release 12.4T at this URL:
http://www.cisco.com/en/US/products/ps6441/products_command_reference_book09186a008049739b
.html
Object tracking of IP SLAs operations allows clients to track the output from IP SLAs objects and use
this information to trigger an action. Every IP SLAs operation maintains an SNMP operation return-code
value, such as OK or OverThreshold, that can be interpreted by the tracking process. You can track two
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
operation-number state
Enter tracking configuration mode to track the state of an IP SLAs operation.
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] |
[up seconds] down seconds}
(Optional) Specify a period of time in seconds to delay communicating state
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
operation-number reachability
Enter tracking configuration mode to track the reachability of an IP SLAs IP
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] |
[up seconds] down seconds}
(Optional) Specify a period of time in seconds to delay communicating state
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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
42-9
Chapter 42
Configuring Enhanced Object Tracking
Monitoring Enhanced Object Tracking
Latest operation return code: over threshold
Latest RTT (millisecs) 4
Tracked by:
HSRP Ethernet0/1 3
This example output shows whether a route is reachable:
Switch(config)# track 3 500 reachability
Switch(config)# end
Switch# show track 3
Track 3
Response Time Reporter 1 reachability
Reachability is Up
1 change, last change 00:00:47
Latest operation return code: over threshold
Latest RTT (millisecs) 4
Tracked by:
HSRP Ethernet0/1 3
Monitoring Enhanced Object Tracking
Use the privileged EXEC or user EXEC commands in Table 42-1 to display enhanced object tracking
information.
Table 42-1
Commands for Displaying Tracking Information
Command
Purpose
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
42-10
OL-12189-01
CH A P T E R
43
Configuring Web Cache Services By Using
WCCP
This chapter describes how to configure your Catalyst Switch Module 3110 to redirect traffic to
wide-area application engines (such as the Cisco Cache Engine 550) by using the Web Cache
Communication Protocol (WCCP). This software release supports only WCCP version 2 (WCCPv2).
Note
The Catalyst Switch Module 3012 does not support WCCP.
WCCP is a Cisco-developed content-routing technology that you can use to integrate wide-area
application enginesreferred to as application enginesinto your network infrastructure. The
application engines transparently store frequently accessed content and then fulfill successive requests
for the same content, eliminating repetitive transmissions of identical content from web servers.
Application engines accelerate content delivery and ensure maximum scalability and availability of
content. In a service-provider network, you can deploy the WCCP and application engine solution at the
points of presence (POPs). In an enterprise network, you can deploy the WCCP and application engine
solution at the regional site and the small branch office. To use this feature, the switch or the stack master
must be running the IP services feature set.
Unless otherwise noted, the term switch refers to a standalone switch and to a switch stack.
Note
For complete syntax and usage information for the commands used in this chapter, see the WCCP
Router Configuration Commands section in the System Management Commands part of the Cisco
IOS Configuration Fundamentals Command Reference, Release 12.2.
This chapter consists of these sections:
Understanding WCCP, page 43-1
Configuring WCCP, page 43-5
Monitoring and Maintaining WCCP, page 43-10
Understanding WCCP
The WCCP and Cisco cache engines (or other application engines running WCCP) localize traffic
patterns in the network, enabling content requests to be fulfilled locally.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
43-1
Chapter 43
Configuring Web Cache Services By Using WCCP
Understanding WCCP
WCCP enables supported Cisco routers and switches to transparently redirect content requests. With
transparent redirection, users do not have to configure their browsers to use a web proxy. Instead, they
can use the target URL to request content, and their requests are automatically redirected to an
application engine. The word transparent means that the end user does not know that a requested file
(such as a web page) came from the application engine instead of from the originally specified server.
When an application engine receives a request, it attempts to service it from its own local cache. If the
requested information is not present, the application engine sends a separate request to the end server to
retrieve the requested information. After receiving the requested information, the application engine
forwards it to the requesting client and also caches it to fulfill future requests.
With WCCP, the application-engine cluster (a series of application engines) can service multiple routers
or switches, as shown Figure 43-1.
Figure 43-1
Cisco Cache Engine and WCCP Network Configuration
Source
Source tree
(shortest
path tree)
Router A
Router B
Shared tree
from RP
RP
44967
Router C
Receiver
WCCP Message Exchange
This sequence of events describes the WCCP message exchange:
1.
The application engines send their IP addresses to the WCCP-enabled switch by using WCCP,
signaling their presence through a Here I am message. The switch and application engines
communicate to each other through a control channel based on UDP port 2048.
2.
The WCCP-enabled switch uses the application engine IP information to create a cluster view (a list
of application engines in the cluster). This view is sent through an I see you message to each
application engine in the cluster, essentially making all the application engines aware of each other.
A stable view is established after the membership of the cluster remains the same for a certain
amount of time.
3.
When a stable view is established, the application engine in the cluster with the lowest IP address is
elected as the designated application engine.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
43-2
OL-12189-01
Chapter 43
Configuring Web Cache Services By Using WCCP
Understanding WCCP
WCCP Negotiation
In the exchange of WCCP protocol messages, the designated application engine and the WCCP-enabled
switch negotiate these items:
Forwarding method (the method by which the switch forwards packets to the application engine).
The switch rewrites the Layer 2 header by replacing the packet destination MAC address with the
target application engine MAC address. It then forwards the packet to the application engine. This
forwarding method requires the target application engine to be directly connected to the switch at
Layer 2.
Assignment method (the method by which packets are distributed among the application engines in
the cluster). The switch uses some bits of the destination IP address, the source IP address, the
destination Layer 4 port, and the source Layer 4 port to determine which application engine receives
the redirected packets.
Packet-return method (the method by which packets are returned from the application engine to the
switch for normal forwarding). These are the typical reasons why an application engine rejects
packets and starts the packet-return feature:
The application engine is overloaded and has no room to service the packets.
The application engine receives an error message (such as a protocol or authentication error)
from the web server and uses the dynamic client bypass feature. The bypass enables clients to
bypass the application engines and to connect directly to the web server.
The application engine returns a packet to the WCCP-enabled switch to forward to the web server
as if the application engine is not present. The application engine does not intercept the reconnection
attempt. In this way, the application engine effectively cancels the redirection of a packet to the
application engine and creates a bypass flow. If the return method is generic-route encapsulation
(GRE), the switch receives the returned packet through a GRE tunnel that is configured in the
application engine. The switch CPU uses Cisco express forwarding to send these packets to the
target web server. If the return method is Layer 2 rewrite, the packets are forwarded in hardware to
the target web server. When the server responds with the requested information, the switch uses
normal Layer 3 forwarding to return the information to the requesting client.
MD5 Security
WCCP provides an optional security component in each protocol message to enable the switch to use
MD5 authentication on messages between the switch and the application engine. Messages that do not
authenticate by MD5 (when authentication of the switch is enabled) are discarded by the switch. The
password string is combined with the MD5 value to create security for the connection between the switch
and the application engine. You must configure the same password on each application engine.
Packet Redirection and Service Groups
You can configure WCCP to classify traffic for redirection, such as FTP, proxy-web-cache handling, and
audio and video applications. This classification, known as a service group, is based on the protocol type
(TCP or UDP) and the Layer 4 source destination port numbers. The service groups are identified either
by well-known names such as web-cache, which means TCP port 80, or a service number, 0 to 99.
Service groups are configured to map to a protocol and Layer 4 port numbers and are established and
maintained independently. WCCP allows dynamic service groups, where the classification criteria are
provided dynamically by a participating application engine.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
43-3
Chapter 43
Configuring Web Cache Services By Using WCCP
Understanding WCCP
You can configure up to 8 service groups on a switch and up to 32 clients per service group. WCCP
maintains the priority of the service group in the group definition. WCCP uses the priority to configure
the service groups in the switch hardware. For example, if service group 1 has a priority of 100 and looks
for destination port 80, and service group 2 has a priority of 50 and looks for source port 80, the incoming
packet with source and destination port 80 is forwarded by using service group 1 because it has the
higher priority.
WCCP supports a cluster of application engines for every service group. Redirected traffic can be sent
to any one of the application engines. The switch supports the mask assignment method of load
balancing the traffic among the application engines in the cluster for a service group.
After WCCP is configured on the switch, the switch forwards all service group packets received from
clients to the application engines. However, these packets are not redirected:
Packets originating from the application engine and targeted to the web server.
Packets originating from the application engine and targeted to the client.
Packets returned or rejected by the application engine. These packets are sent to the web server.
You can configure a single multicast address per service group for sending and receiving protocol
messages. When there is a single multicast address, the application engine sends a notification to one
address, which provides coverage for all routers in the service group, for example, 225.0.0.0. If you add
and remove routers dynamically, using a single multicast address provides easier configuration because
you do not need to specifically enter the addresses of all devices in the WCCP network.
You can use a router group list to validate the protocol packets received from the application engine.
Packets matching the address in the group list are processed, packets not matching the group list address
are dropped.
To disable caching for specific clients, servers, or client/server pairs, you can use a WCCP redirect
access control list (ACL). Packets that match the redirect ACL bypass the cache and are forwarded
normally.
Before WCCP packets are redirected, the switch examines ACLs associated with all inbound features
configured on the interface and permits or denies packet forwarding based on how the packet matches
the entries in the ACL.
When packets are redirected, the output ACLs associated with the redirected interface are applied to the
packets. Any ACLs associated with the original port are not applied unless you specifically configure
the required output ACLs on the redirected interfaces.
WCCP and Switch Stacks
WCCP support is the same for a switch stack as for a standalone switch. WCCP configuration
information is propagated to all switches in the stack. All switches in the stack, including the stack
master, process the information and program their hardware. For more information about switch stacks,
see Chapter 5, Managing Switch Stacks.
The stack master performs these WCCP functions:
It receives protocol packets from any WCCP-enabled interface and sends them out any
WCCP-enabled interface in the stack.
It processes the WCCP configuration and propagates the information to all stack members.
It distributes the WCCP information to any switch that joins the stack.
It programs its hardware with the WCCP information it processes.
Stack members receive the WCCP information from the master switch and program their hardware.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
43-4
OL-12189-01
Chapter 43
Configuring Web Cache Services By Using WCCP
Configuring WCCP
Unsupported WCCP Features
These WCCP features are not supported in this software release:
Packet redirection on an outbound interface that is configured by using the ip wccp redirect out
interface configuration command. This command is not supported.
The GRE forwarding method for packet redirection is not supported.
The hash assignment method for load balancing is not supported.
There is no SNMP support for WCCP.
Configuring WCCP
These sections describe how to configure WCCP on your switch:
Default WCCP Configuration, page 43-5
WCCP Configuration Guidelines, page 43-5
Enabling the Web Cache Service, page 43-6 (required)
Default WCCP Configuration
Table 43-1 shows the default WCCP configuration.
Table 43-1
Default WCCP Configuration
Feature
Default Setting
WCCP enable state
WCCP services are disabled.
Protocol version
WCCPv2.
Redirecting traffic received on an interface
Disabled.
WCCP Configuration Guidelines
Before configuring WCCP on your switch, make sure to follow these configuration guidelines:
The application engines and switches in the same service group must be in the same subnetwork
directly connected to the switch that has WCCP enabled.
Configure the switch interfaces that are connected to the web clients, the application engines, and
the web server as Layer 3 interfaces (routed ports and switch virtual interfaces [SVIs]). For WCCP
packet redirection to work, the servers, application engines, and clients must be on different subnets.
Use only nonreserved multicast addresses when configuring a single multicast address for each
application engine.
WCCP entries and PBR entries use the same TCAM region. WCCP is supported only on the
templates that support PBR: access, routing, and dual IPv4/v6 routing.
When TCAM entries are not available to add WCCP entries, packets are not redirected and are
forwarded by using the standard routing tables.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
43-5
Chapter 43
Configuring Web Cache Services By Using WCCP
Configuring WCCP
The number of available policy-based routing (PBR) labels are reduced as more interfaces are
enabled for WCCP ingress redirection. For every interface that supports service groups, one label is
consumed. The WCCP labels are taken from the PBR labels. You need to monitor and manage the
labels that are available between PBR and WCCP. When labels are not available, the switch cannot
add service groups. However, if another interface has the same sequence of service groups, a new
label is not needed, and the group can be added to the interface.
The routing maximum transmission unit (MTU) size configured on the stack member switches
should be larger than the client MTU size. The MAC-layer MTU size configured on ports connected
to application engines should take into account the GRE tunnel header bytes.
You cannot configure WCCP and VPN routing/forwarding (VRF) on the same switch interface.
You cannot configure WCCP and PBR on the same switch interface.
You cannot configure WCCP and a private VLAN (PVLAN) on the same switch interface.
Enabling the Web Cache Service
For WCCP packet redirection to operate, you must configure the switch interface connected to the client
to redirect inbound packets.
This procedure shows how to configure these features on routed ports. To configure these features on
SVIs, see the configuration examples that follow the procedure.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
43-6
OL-12189-01
Chapter 43
Configuring Web Cache Services By Using WCCP
Configuring WCCP
Beginning in privileged EXEC mode, follow these steps to enable the web cache service, to set a
multicast group address or group list, to configure routed interfaces, to redirect inbound packets received
from a client to the application engine, enable an interface to listen for a multicast address, and to set a
password. This procedure is required.
Note
Before configuring WCCP commands, configure the SDM template, and reboot the switch. For more
information, see Chapter 8, Configuring SDM Templates.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ip wccp {web-cache | service-number}
[group-address groupaddress]
[group-list access-list] [redirect-list
access-list] [password
encryption-number password]
Enable the web cache service, and specify the service number which
corresponds to a dynamic service that is defined by the application
engine. By default, this feature is disabled.
(Optional) For group-address groupaddress, specify the multicast group
address used by the switches and the application engines to participate in
the service group.
(Optional) For group-list access-list, if a multicast group address is not
used, specify a list of valid IP addresses that correspond to the application
engines that are participating in the service group.
(Optional) For redirect-list access-list, specify the redirect service for
specific hosts or specific packets from hosts.
(Optional) For password encryption-number password, specify an
encryption number. The range is 0 to 7. Use 0 for not encrypted, and use
7 for proprietary. Specify a password name up to seven characters in
length. The switch combines the password with the MD5 authentication
value to create security for the connection between the switch and the
application engine. By default, no password is configured, and no
authentication is performed.
You must configure the same password on each application engine.
When authentication is enabled, the switch discards messages that are not
authenticated.
Step 3
interface interface-id
Specify the interface connected to the application engine or the web
server, and enter interface configuration mode.
Step 4
no switchport
Enter Layer 3 mode.
Step 5
ip address ip-address subnet-mask
Configure the IP address and subnet mask.
Step 6
no shutdown
Enable the interface.
Step 7
exit
Return to global configuration mode. Repeat Steps 3 through 7 for each
application engine and web server.
Step 8
interface interface-id
Specify the interface connected to the client, and enter interface
configuration mode.
Step 9
no switchport
Enter Layer 3 mode.
Step 10
ip address ip-address subnet-mask
Configure the IP address and subnet mask.
Step 11
no shutdown
Enable the interface.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
43-7
Chapter 43
Configuring Web Cache Services By Using WCCP
Configuring WCCP
Command
Purpose
Step 12
ip wccp {web-cache | service-number}
redirect in
Redirect packets received from the client to the application engine.
Enable this on the interface connected to the client.
Step 13
ip wccp {web-cache | service-number}
group-listen
(Optional) When using a multicast group address, group-listen enables
the interface to listen for the multicast address. Enable this on the
interface connected to the application engine.
Step 14
exit
Return to global configuration mode. Repeat Steps 8 through 13 for each
client.
Step 15
end
Return to privileged EXEC mode.
Step 16
show ip wccp web-cache
Verify your entries.
and
show running-config
Step 17
copy running-config startup-config
(Optional) Save your entries in the configuration file.
To disable the web cache service, use the no ip wccp web-cache global configuration command. To
disable inbound packet redirection, use the no ip wccp web-cache redirect in interface configuration
command. After completing this procedure, you should configure the application engines in the network.
This example shows how to configure routed interfaces and to enable the web cache service with a
multicast group address and a redirect access list. Gigabit Ethernet port 1 is connected to the application
engine, is configured as a routed port with an IP address of 172.20.10.30, and is re-enabled. Gigabit
Ethernet port 2 is connected through the Internet to the web server, is configured as a routed port with
an IP address of 175.20.20.10, and is re-enabled. Gigabit Ethernet ports 3 to 6 are connected to the
clients and are configured as routed ports with IP addresses 175.20.30.20, 175.20.40.30, 175.20.50.40,
and 175.20.60.50. The switch listens for multicast traffic and redirects packets received from the client
interfaces to the application engine.
Switch# configure terminal
Switch(config)# ip wccp web-cache 80 group-address 224.1.1.100 redirect list 12
Switch(config)# access-list 12 permit host 10.1.1.1
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# no switchport
Switch(config-if)# ip address 172.20.10.30 255.255.255.0
Switch(config-if)# no shutdown
Switch(config-if)# ip wccp web-cache group-listen
Switch(config-if)# exit
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# no switchport
Switch(config-if)# ip address 175.20.20.10 255.255.255.0
Switch(config-if)# no shutdown
Switch(config-if)# exit
Switch(config)# interface gigabitethernet1/0/3
Switch(config-if)# no switchport
Switch(config-if)# ip address 175.20.30.20 255.255.255.0
Switch(config-if)# no shutdown
Switch(config-if)# ip wccp web-cache redirect in
Switch(config-if)# exit
Switch(config)# interface gigabitethernet1/0/4
Switch(config-if)# no switchport
Switch(config-if)# ip address 175.20.40.30 255.255.255.0
Switch(config-if)# no shutdown
Switch(config-if)# ip wccp web-cache redirect in
Switch(config-if)# exit
Switch(config)# interface gigabitethernet1/0/5
Switch(config-if)# no switchport
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
43-8
OL-12189-01
Chapter 43
Configuring Web Cache Services By Using WCCP
Configuring WCCP
Switch(config-if)# ip address 175.20.50.40 255.255.255.0
Switch(config-if)# no shutdown
Switch(config-if)# ip wccp web-cache redirect in
Switch(config-if)# exit
Switch(config)# interface gigabitethernet1/0/6
Switch(config-if)# no switchport
Switch(config-if)# ip address 175.20.60.50 255.255.255.0
Switch(config-if)# no shutdown
Switch(config-if)# ip wccp web-cache redirect in
Switch(config-if)# exit
This example shows how to configure SVIs and how to enable the web cache service with a multicast
group list. VLAN 299 is created and configured with an IP address of 175.20.20.10. Gigabit Ethernet
port 1 is connected through the Internet to the web server and is configured as an access port in
VLAN 299. VLAN 300 is created and configured with an IP address of 172.20.10.30. Gigabit Ethernet
port 2 is connected to the application engine and is configured as an access port in VLAN 300.
VLAN 301 is created and configured with an IP address of 175.20.30.50. Fast Ethernet ports 3 to 6,
which are connected to the clients, are configured as access ports in VLAN 301. The switch redirects
packets received from the client interfaces to the application engine.
Switch# configure terminal
Switch(config)# ip wccp web-cache 80 group-list 15
Switch(config)# access-list 15 permit host 171.69.198.102
Switch(config)# access-list 15 permit host 171.69.198.104
Switch(config)# access-list 15 permit host 171.69.198.106
Switch(config)# vlan 299
Switch(config-vlan)# exit
Switch(config)# interface vlan 299
Switch(config-if)# ip address 175.20.20.10 255.255.255.0
Switch(config-if)# exit
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# switchport mode access
Switch(config-if)# switchport access vlan 299
Switch(config)# vlan 300
Switch(config-vlan)# exit
Switch(config)# interface vlan 300
Switch(config-if)# ip address 172.20.10.30 255.255.255.0
Switch(config-if)# exit
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# switchport mode access
Switch(config-if)# switchport access vlan 300
Switch(config-if)# exit
Switch(config)# vlan 301
Switch(config-vlan)# exit
Switch(config)# interface vlan 301
Switch(config-if)# ip address 175.20.30.20 255.255.255.0
Switch(config-if)# ip wccp web-cache redirect in
Switch(config-if)# exit
Switch(config)# interface range gigabitethernet1/0/3 - 6
Switch(config-if-range)# switchport mode access
Switch(config-if-range)# switchport access vlan 301
Switch(config-if-range)# exit
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
43-9
Chapter 43
Configuring Web Cache Services By Using WCCP
Monitoring and Maintaining WCCP
Monitoring and Maintaining WCCP
To monitor and maintain WCCP, use one or more of the privileged EXEC commands in Table 43-2:
Table 43-2
Commands for Monitoring and Maintaining WCCP
Command
Purpose
clear ip wccp web-cache
Removes statistics for the web-cache service.
show ip wccp web-cache
Displays global information related to WCCP.
show ip wccp web-cache detail
Displays information for the switch and all application engines in the
WCCP cluster.
show ip interface
Displays status about any IP WCCP redirection commands that are
configured on an interface; for example, Web Cache Redirect is
enabled / disabled.
show ip wccp web-cache view
Displays which other members have or have not been detected.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
43-10
OL-12189-01
CH A P T E R
44
Configuring IP Multicast Routing
This chapter describes how to configure IP multicast routing on the Catalyst Switch Module 3110.
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 send to a group. However, only the members of a group receive
the message.
To use this feature, the switch or stack master must be running the IP services feature set. To use the PIM
stub routing feature, the switch or stack master can be running the IP base image.
Unless otherwise noted, the term switch refers to a standalone switch and to a switch stack.
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.
This chapter consists of these sections:
Understanding Ciscos Implementation of IP Multicast Routing, page 44-2
Multicast Routing and Switch Stacks, page 44-10
Configuring IP Multicast Routing, page 44-10
Configuring Advanced PIM Features, page 44-26
Configuring Optional IGMP Features, page 44-29
Configuring Optional Multicast Routing Features, page 44-35
Configuring Basic DVMRP Interoperability Features, page 44-39
Configuring Advanced DVMRP Interoperability Features, page 44-44
Monitoring and Maintaining IP Multicast Routing, page 44-52
For information on configuring the Multicast Source Discovery Protocol (MSDP), see Chapter 45,
Configuring MSDP.
Note
The Catalyst Switch Module 3012 does not support IP multicast routing.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
44-1
Chapter 44
Configuring IP Multicast Routing
Understanding Ciscos Implementation of IP Multicast Routing
Understanding Ciscos Implementation of IP Multicast Routing
The Cisco IOS software supports these protocols to implement IP multicast routing:
Internet Group Management Protocol (IGMP) is used among hosts on a LAN and the routers (and
multilayer switches) on that LAN to track the multicast groups of which hosts are members.
Protocol-Independent Multicast (PIM) protocol is used among routers and multilayer switches to
track which multicast packets to forward to each other and to their directly connected LANs.
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 44-1 shows where these protocols operate within the IP multicast environment.
Figure 44-1
IP Multicast Routing Protocols
Internet
MBONE
Cisco Catalyst switch
(CGMP client)
Host
DVMRP
CGMP
PIM
IGMP
44966
Host
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. For example, if the IP destination address is 239.1.1.39,
the MAC destination address is 0100:5e01:0127.
A multicast packet is unmatched when the destination IPv4 address does not match the destination MAC
address. The switch forwards the unmatched packet in hardware based the MAC address table. If the
destination MAC address is not in the MAC address table, the switch floods the packet to the all port in
the same VLAN as the receiving port.
This section includes information about these topics:
Understanding IGMP, page 44-3
Understanding PIM, page 44-4
Understanding DVMRP, page 44-9
Understanding CGMP, page 44-9
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
44-2
OL-12189-01
Chapter 44
Configuring IP Multicast Routing
Understanding Ciscos Implementation of IP Multicast Routing
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 224.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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
44-3
Chapter 44
Configuring IP Multicast Routing
Understanding Ciscos Implementation of IP Multicast Routing
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
Protocol Independent Multicast (PIM), Sparse Mode Protocol Specification
draft-ietf-idmr-igmp-v2-06.txt, Internet Group Management Protocol, Version 2
draft-ietf-pim-v2-dm-03.txt, PIM Version 2 Dense Mode
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
44-4
OL-12189-01
Chapter 44
Configuring IP Multicast Routing
Understanding Ciscos Implementation of IP Multicast Routing
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 sources 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.
When the number of PIM-enabled interfaces exceeds the hardware capacity and PIM-SM is enabled with
the SPT threshold is set to infinity, the switch does not create (S,G) entries in the multicast routing table
for the some directly connected interfaces if they are not already in the table. The switch might not
correctly forward traffic from these interfaces.
PIM Stub Routing
The PIM stub routing feature, available in all software images, reduces resource usage by moving routed
traffic closer to the end user.
Note
The IP base image contains only PIM stub routing. The IP services image contains complete multicast
routing. On a switch running the IP base image, if you try to configure a VLAN interface with PIM
dense-mode, sparse-mode, or dense-sparse-mode, the configuration is not allowed.
In a network using PIM stub routing, the only allowable route for IP traffic to the user is through a switch
that is configured with PIM stub routing. PIM passive interfaces are connected to Layer 2 access
domains, such as VLANs, or to interfaces that are connected to other Layer 2 devices. Only directly
connected multicast (IGMP) receivers and sources are allowed in the Layer 2 access domains. The PIM
passive interfaces do not send or process any received PIM control packets.
When using PIM stub routing, you should configure the distribution and remote routers to use IP
multicast routing and configure only the switch as a PIM stub router. The switch does not route transit
traffic between distribution routers. You also need to configure a routed uplink port on the switch. The
switch uplink port cannot be used with SVIs. If you need PIM for an SVI uplink port, you should upgrade
to the IP services feature set.
You must also configure EIGRP stub routing when configuring PIM stub routing on the switch. For more
information, see the EIGRP Stub Routing section on page 38-43.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
44-5
Chapter 44
Configuring IP Multicast Routing
Understanding Ciscos Implementation of IP Multicast Routing
The redundant PIM stub router topology is not supported. The redundant topology exists when there is
more than one PIM router forwarding multicast traffic to a single access domain. PIM messages are
blocked, and the PIM asset and designated router election mechanisms are not supported on the PIM
passive interfaces. Only the nonredundant access router topology is supported by the PIM stub feature.
By using a nonredundant topology, the PIM passive interface assumes that it is the only interface and
designated router on that access domain.
The PIM stub feature is enforced in the IP base image. If you upgrade to a higher software version, the
PIM stub configuration remains until you reconfigure the interfaces.
In Figure 44-2, Switch A routed uplink port 25 is connected to the router and PIM stub routing is enabled
on the VLAN 100 interfaces and on Host 3. This configuration allows the directly connected hosts to
receive traffic from multicast source 200.1.1.3. See the Enabling PIM Stub Routing section on
page 44-14 for more information.
Figure 44-2
PIM Stub Router Configuration
Routed network
Switch A
Host B
VLAN 20
Host C
201331
Host A
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 IOS
IP and IP Routing Command Reference, Release 12.1.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
44-6
OL-12189-01
Chapter 44
Configuring IP Multicast Routing
Understanding Ciscos Implementation of IP Multicast Routing
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 caches. Thus, all
routers and switches automatically discover which RP to use for the groups that they support. If a router
or switch fails to receive RP-discovery messages and the Group-to-RP mapping information expires, it
changes 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
44-7
Chapter 44
Configuring IP Multicast Routing
Understanding Ciscos Implementation of IP Multicast Routing
Multicast Forwarding and Reverse Path Check
With unicast routing, routers and multilayer switches forward traffic through the network along a single
path from the source to the destination host whose IP address appears in the destination address field of
the IP packet. Each router and switch along the way makes a unicast forwarding decision, using the
destination IP address in the packet, by looking up the destination address in the unicast routing table
and forwarding the packet through the specified interface to the next hop toward the destination.
With multicasting, the source is sending traffic to an arbitrary group of hosts represented by a multicast
group address in the destination address field of the IP packet. To decide whether to forward or drop an
incoming multicast packet, the router or multilayer switch uses a reverse path forwarding (RPF) check
on the packet as follows and shown in Figure 44-3:
1.
The router or multilayer switch examines the source address of the arriving multicast packet to
decide whether the packet arrived on an interface that is on the reverse path back to the source.
2.
If the packet arrives on the interface leading back to the source, the RPF check is successful and the
packet is forwarded to all interfaces in the outgoing interface list (which might not be all interfaces
on the router).
3.
If the RPF check fails, the packet is discarded.
Some multicast routing protocols, such as DVMRP, maintain a separate multicast routing table and use
it for the RPF check. However, PIM uses the unicast routing table to perform the RPF check.
Figure 44-3 shows port 2 receiving a multicast packet from source 151.10.3.21. Table 44-1 shows that
the port on the reverse path to the source is port 1, not port 2. Because the RPF check fails, the multilayer
switch discards the packet. Another multicast packet from source 151.10.3.21 is received on port 1, and
the routing table shows this port is on the reverse path to the source. Because the RPF check passes, the
switch forwards the packet to all port in the outgoing port list.
Figure 44-3
RPF Check
Multicast
packet from
source 151.10.3.21
is forwarded.
Gigabit Ethernet 0/1
Multicast
packet from
source 151.10.3.21
packet is discarded.
Gigabit Ethernet 0/2
Gigabit Ethernet 0/3
Table 44-1
Gigabit Ethernet 0/4
101242
Layer 3 switch
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/0/3
204.1.16.0/24
Gigabit Ethernet 1/0/4
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
44-8
OL-12189-01
Chapter 44
Configuring IP Multicast Routing
Understanding Ciscos Implementation of IP Multicast Routing
PIM uses both source trees and RP-rooted shared trees to forward datagrams (described in the PIM
DM section on page 44-4 and the PIM-SM section on page 44-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.)
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
44-9
Chapter 44
Configuring IP Multicast Routing
Multicast Routing and Switch Stacks
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.
Multicast Routing and Switch Stacks
For all multicast routing protocols, the entire stack appears as a single router to the network and operates
as a single multicast router.
In a switch stack, the routing master (stack master) performs these functions:
It is responsible for completing the IP multicast routing functions of the stack. It fully initializes and
runs the IP multicast routing protocols.
It builds and maintains the multicast routing table for the entire stack.
It is responsible for distributing the multicast routing table to all stack members.
The stack members perform these functions:
They act as multicast routing standby devices and are ready to take over if there is a stack master
failure.
If the stack master fails, all stack members delete their multicast routing tables. The newly elected
stack master starts building the routing tables and distributes them to the stack members.
Note
If a stack master running the IP services feature set fails and if the newly elected stack master
is running the IP base feature set, the switch stack loses its multicast routing capability.
For information about the stack master election process, see Chapter 5, Managing Switch Stacks.
They do not build multicast routing tables. Instead, they use the multicast routing table that is
distributed by the stack master.
Configuring IP Multicast Routing
These sections contain this configuration information:
Default Multicast Routing Configuration, page 44-11
Multicast Routing Configuration Guidelines, page 44-11
Configuring Basic Multicast Routing, page 44-12 (required)
Enabling PIM Stub Routing, page 44-14
Enabling PIM Stub Routing, page 44-14 (optional)
Configuring a Rendezvous Point, page 44-15 (required if the interface is in sparse-dense mode, and
you want to treat the group as a sparse group)
Using Auto-RP and a BSR, page 44-25 (required for non-Cisco PIMv2 devices to interoperate with
Cisco PIM v1 devices))
Monitoring the RP Mapping Information, page 44-26 (optional)
Troubleshooting PIMv1 and PIMv2 Interoperability Problems, page 44-26 (optional)
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
44-10
OL-12189-01
Chapter 44
Configuring IP Multicast Routing
Configuring IP Multicast Routing
Default Multicast Routing Configuration
Table 44-2 shows the default multicast routing configuration.
Table 44-2
Default Multicast Routing Configuration
Feature
Default Setting
Multicast routing
Disabled on all interfaces.
PIM version
Version 2.
PIM mode
No mode is defined.
PIM stub routing
None configured.
PIM RP address
None configured.
PIM domain border
Disabled.
PIM multicast boundary
None.
Candidate BSRs
Disabled.
Candidate RPs
Disabled.
Shortest-path tree threshold rate
0 kb/s.
PIM router query message interval
30 seconds.
Multicast Routing Configuration Guidelines
To avoid misconfiguring multicast routing on your switch, review the information in these sections:
PIMv1 and PIMv2 Interoperability, page 44-11
Auto-RP and BSR Configuration Guidelines, page 44-12
PIMv1 and PIMv2 Interoperability
The Cisco PIMv2 implementation provides interoperability and transition between Version 1 and
Version 2, although there might be some minor problems.
You can upgrade to PIMv2 incrementally. PIM Versions 1 and 2 can be configured on different routers
and multilayer switches within one network. Internally, all routers and multilayer switches on a shared
media network must run the same PIM version. Therefore, if a PIMv2 device detects a PIMv1 device,
the Version 2 device downgrades itself to Version 1 until all Version 1 devices have been shut down or
upgraded.
PIMv2 uses the BSR to discover and announce RP-set information for each group prefix to all the routers
and multilayer switches in a PIM domain. PIMv1, together with the Auto-RP feature, can perform the
same tasks as the PIMv2 BSR. However, Auto-RP is a standalone protocol, separate from PIMv1, and is
a proprietary Cisco protocol. PIMv2 is a standards track protocol in the IETF. We recommend that you
use PIMv2. The BSR mechanism interoperates with Auto-RP on Cisco routers and multilayer switches.
For more information, see the Auto-RP and BSR Configuration Guidelines section on page 44-12.
When PIMv2 devices interoperate with PIMv1 devices, Auto-RP should have already been deployed. A
PIMv2 BSR that is also an Auto-RP mapping agent automatically advertises the RP elected by Auto-RP.
That is, Auto-RP sets its single RP on every router or multilayer switch in the group. Not all routers and
switches in the domain use the PIMv2 hash function to select multiple RPs.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
44-11
Chapter 44
Configuring IP Multicast Routing
Configuring IP Multicast Routing
Dense-mode groups in a mixed PIMv1 and PIMv2 region need no special configuration; they
automatically interoperate.
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 44-17.
Auto-RP and BSR Configuration Guidelines
There are two approaches to using PIMv2. You can use Version 2 exclusively in your network or migrate
to Version 2 by employing a mixed PIM version environment.
If your network is all Cisco routers and multilayer switches, you can use either Auto-RP or BSR.
If you have non-Cisco routers in your network, you must use BSR.
If you have Cisco PIMv1 and PIMv2 routers and multilayer switches and non-Cisco routers, you
must use both Auto-RP and BSR. If your network includes routers from other vendors, configure the
Auto-RP mapping agent and the BSR on a Cisco PIMv2 device. Ensure that no PIMv1 device is
located in the path a between the BSR and a non-Cisco PIMv2 device.
Because bootstrap messages are sent hop-by-hop, a PIMv1 device prevents these messages from
reaching all routers and multilayer switches in your network. Therefore, if your network has a
PIMv1 device in it and only Cisco routers and multilayer switches, it is best to use Auto-RP.
If you have a network that includes non-Cisco routers, configure the Auto-RP mapping agent and
the BSR on a Cisco PIMv2 router or multilayer switch. Ensure that no PIMv1 device is on the path
between the BSR and a non-Cisco PIMv2 router.
If you have non-Cisco PIMv2 routers that need to interoperate with Cisco PIMv1 routers and
multilayer switches, both Auto-RP and a BSR are required. We recommend that a Cisco PIMv2
device be both the Auto-RP mapping agent and the BSR. For more information, see the Using
Auto-RP and a BSR section on page 44-25.
Configuring Basic Multicast Routing
You must enable IP multicast routing and configure the PIM version and the PIM mode. Then the
software can forward multicast packets, and the switch can populate its multicast routing table.
You can configure an interface to be in PIM dense mode, sparse mode, or sparse-dense mode. The switch
populates its multicast routing table and forwards multicast packets it receives from its directly
connected LANs according to the mode setting. You must enable PIM in one of these modes for an
interface to perform IP multicast routing. Enabling PIM on an interface also enables IGMP operation on
that interface.
Note
If you enable PIM on multiple interfaces, when most of these interfaces 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
44-12
OL-12189-01
Chapter 44
Configuring IP Multicast Routing
Configuring IP Multicast Routing
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 receivers 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 10-20.
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 44-11.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
44-13
Chapter 44
Configuring IP Multicast Routing
Configuring IP Multicast Routing
Step 5
Command
Purpose
ip pim {dense-mode | sparse-mode |
sparse-dense-mode}
Enable a PIM mode on the interface.
By default, no mode is configured.
The keywords have these meanings:
dense-modeEnables dense mode of operation.
sparse-modeEnables 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 44-15.
sparse-dense-modeCauses the interface to be treated in the mode
in which the group belongs. Sparse-dense mode is the recommended
setting.
Note
After you enable a PIM mode on the interface, the ip
mroute-cache distributed interface configuration command is
automatically entered for the interface and appears in the running
configuration.
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 multicasting, use the no ip multicast-routing distributed global configuration command. To
return to the default PIM version, use the no ip pim version interface configuration command. To
disable PIM on an interface, use the no ip pim interface configuration command.
Enabling PIM Stub Routing
Beginning in privileged EXEC mode, follow these steps to enable PIM stub routing on an interface. This
procedure is optional.
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.
For switches running the IP Base image, the specified interface must be
an SVI that is a VLAN interface created by using the interface vlan
vlan-id global configuration command. For all other software images, the
specified interface can be any routed interface.
Step 3
ip pim passive
Configure the PIM stub feature 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.
To disable PIM stub routing on an interface, use the no ip pim passive interface configuration command.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
44-14
OL-12189-01
Chapter 44
Configuring IP Multicast Routing
Configuring IP Multicast Routing
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 44-2:
Switch(config)# ip multicast-routing distributed
Switch(config)# interface GigabitEthernet3/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 GigabitEthernet3/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 GigabitEthernet3/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 GigabitEthernet3/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 GigabitEthernet3/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.
Configuring a Rendezvous Point
You must have an RP if the interface is in sparse-dense mode and if you want to treat the group as a sparse
group. You can use several methods, as described in these sections:
Manually Assigning an RP to Multicast Groups, page 44-16
Configuring Auto-RP, page 44-17 (a standalone, Cisco-proprietary protocol separate from PIMv1)
Configuring PIMv2 BSR, page 44-21 (a standards track protocol in the Internet Engineering Task
Force [IETF])
You can use auto-RP, BSR, or a combination of both, depending on the PIM version that you are running
and the types of routers in your network. For more information, see the PIMv1 and PIMv2
Interoperability section on page 44-11 and the Auto-RP and BSR Configuration Guidelines section
on page 44-12.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
44-15
Chapter 44
Configuring IP Multicast Routing
Configuring IP Multicast Routing
Manually Assigning an RP to Multicast Groups
This section explains how to manually configure an RP. If the RP for a group is learned through a
dynamic mechanism (such as auto-RP or BSR), you need not perform this task for that RP.
Senders of multicast traffic announce their existence through register messages received from the source
first-hop router (designated router) and forwarded to the RP. Receivers of multicast packets use RPs to
join a multicast group by using explicit join messages. RPs are not members of the multicast group;
rather, they serve as a meeting place for multicast sources and group members.
You can configure a single RP for multiple groups defined by an access list. If there is no RP configured
for a group, the multilayer switch treats the group as dense and uses the dense-mode PIM techniques.
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
[access-list-number] [override]
Configure the address of a PIM RP.
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.
Step 3
access-list access-list-number {deny |
permit} source [source-wildcard]
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.
Create a standard access list, repeating the command as many times 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 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
44-16
OL-12189-01
Chapter 44
Configuring IP Multicast Routing
Configuring IP Multicast Routing
Command
Purpose
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 an RP address, use the no ip pim rp-address ip-address [access-list-number] [override]
global configuration command.
This example shows how to configure the address of the RP to 147.106.6.22 for multicast
group 225.2.2.2 only:
Switch(config)# access-list 1 permit 225.2.2.2 0.0.0.0
Switch(config)# ip pim rp-address 147.106.6.22 1
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.
Follow these guidelines when configuring Auto-RP:
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 44-16.
If routed interfaces 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 routed interfaces are configured in sparse mode and you enter the ip pim autorp listener global
configuration command, Auto-RP can still be used even if all devices are not configured with a
manual RP address for the Auto-RP groups.
These sections describe how to configure Auto-RP:
Setting up Auto-RP in a New Internetwork, page 44-17 (optional)
Adding Auto-RP to an Existing Sparse-Mode Cloud, page 44-18 (optional)
Preventing Join Messages to False RPs, page 44-19 (optional)
Filtering Incoming RP Announcement Messages, page 44-19 (optional)
For overview information, see the Auto-RP section on page 44-7.
Setting up Auto-RP in a New Internetwork
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 Adding Auto-RP to an
Existing Sparse-Mode Cloud section on page 44-18. However, omit Step 3 if you want to configure a
PIM router as the RP for the local group.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
44-17
Chapter 44
Configuring IP Multicast Routing
Configuring IP Multicast Routing
Adding Auto-RP to an Existing Sparse-Mode Cloud
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.
Step 1
Command
Purpose
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
scope ttl group-list access-list-number
interval seconds
Configure another PIM device to be the candidate RP for local groups.
Step 4
access-list access-list-number {deny |
permit} source [source-wildcard]
For interface-id, enter the interface type and number that identifies
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.
Create a standard access list, repeating the command as many times as
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
44-18
OL-12189-01
Chapter 44
Configuring IP Multicast Routing
Configuring IP Multicast Routing
Step 5
Command
Purpose
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 interfaces 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 gigabitethernet0/1 scope 31 group-list 5
Switch(config)# access-list 5 permit 224.0.0.0 15.255.255.255
Preventing Join Messages to False RPs
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 interfaces 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
Filtering Incoming RP Announcement Messages
You can add configuration commands to the mapping agents to prevent a maliciously configured router
from masquerading as a candidate RP and causing problems.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
44-19
Chapter 44
Configuring IP Multicast Routing
Configuring IP Multicast Routing
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
access-list-number group-list
access-list-number
Filter incoming RP announcement messages.
Enter this command on each mapping agent in the network. Without
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 |
permit} source [source-wildcard]
Create a standard access list, repeating the command as many times 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.
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.
To remove a filter on incoming RP announcement messages, use the no ip pim rp-announce-filter
rp-list access-list-number [group-list access-list-number] global configuration command.
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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
44-20
OL-12189-01
Chapter 44
Configuring IP Multicast Routing
Configuring IP Multicast Routing
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.
Configuring PIMv2 BSR
These sections describe how to set up BSR in your PIMv2 network:
Defining the PIM Domain Border, page 44-21 (optional)
Defining the IP Multicast Boundary, page 44-22 (optional)
Configuring Candidate BSRs, page 44-23 (optional)
Configuring Candidate RPs, page 44-24 (optional)
For overview information, see the Bootstrap Router section on page 44-7.
Defining the PIM Domain Border
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 44-4.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
44-21
Chapter 44
Configuring IP Multicast Routing
Configuring IP Multicast Routing
Figure 44-4
Constraining PIMv2 BSR Messages
PIMv2 sparse-mode
network
Configure the
ip pim bsr-border
command on
this interface.
Layer 3
switch
BSR
messages
BSR
Layer 3
switch
Neighboring
PIMv2 domain
101243
Neighboring
PIMv2 domain
BSR
messages
Configure the
ip pim bsr-border
command on
this interface.
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
source [source-wildcard]
Create a standard access list, repeating the command as many times as
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
access-list-number
Configure the boundary, specifying the access list you created 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 remove the boundary, use the no ip multicast boundary interface configuration command.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
44-22
OL-12189-01
Chapter 44
Configuring IP Multicast Routing
Configuring IP Multicast Routing
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)# access-list 1 permit all
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# ip multicast boundary 1
Configuring Candidate BSRs
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
hash-mask-length [priority]
Configure your switch to be a candidate BSR.
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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
44-23
Chapter 44
Configuring IP Multicast Routing
Configuring IP Multicast Routing
Configuring Candidate RPs
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 a portion of 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
[group-list access-list-number]
Configure your switch to be a candidate RP.
Step 3
access-list access-list-number {deny |
permit} source [source-wildcard]
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.
Create a standard access list, repeating the command as many times 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 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
44-24
OL-12189-01
Chapter 44
Configuring IP Multicast Routing
Configuring IP Multicast Routing
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
Using Auto-RP and a BSR
If there are only Cisco devices in you network (no routers from other vendors), there is no need to
configure a BSR. Configure Auto-RP in a network that is running both PIMv1 and PIMv2.
If you have non-Cisco PIMv2 routers that need to interoperate with Cisco PIMv1 routers and multilayer
switches, both Auto-RP and a BSR are required. We recommend that a Cisco PIMv2 router or multilayer
switch be both the Auto-RP mapping agent and the BSR.
If you must have one or more BSRs, we have these recommendations:
Configure the candidate BSRs as the RP-mapping agents for Auto-RP. For more information, see
the Configuring Auto-RP section on page 44-17 and the Configuring Candidate BSRs section
on page 44-23.
For group prefixes advertised through Auto-RP, the PIMv2 BSR mechanism should not advertise a
subrange of these group prefixes served by a different set of RPs. In a mixed PIMv1 and PIMv2
domain, have backup RPs serve the same group prefixes. This prevents the PIMv2 DRs from
selecting a different RP from those PIMv1 DRs, due to the longest match lookup in the RP-mapping
database.
Beginning in privileged EXEC mode, follow these steps to verify the consistency of group-to-RP
mappings. This procedure is optional.
Step 1
Step 2
Command
Purpose
show ip pim rp [[group-name |
group-address] | mapping]
On any Cisco device, display the available RP mappings.
show ip pim rp-hash group
(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).
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
44-25
Chapter 44
Configuring IP Multicast Routing
Configuring Advanced PIM Features
Monitoring the RP Mapping Information
To monitor the RP mapping information, use these commands in privileged EXEC mode:
show ip pim bsr displays information about the elected BSR.
show ip pim rp-hash group displays the RP that was selected for the specified group.
show ip pim rp [group-name | group-address | mapping] displays how the switch learns of the RP
(through the BSR or the Auto-RP mechanism).
Troubleshooting PIMv1 and PIMv2 Interoperability Problems
When debugging interoperability problems between PIMv1 and PIMv2, check these in the order shown:
1.
Verify RP mapping with the show ip pim rp-hash privileged EXEC command, making sure that all
systems agree on the same RP for the same group.
2.
Verify interoperability between different versions of DRs and RPs. Make sure the RPs are
interacting with the DRs properly (by responding with register-stops and forwarding decapsulated
data packets from registers).
Configuring Advanced PIM Features
These sections describe the optional advanced PIM features:
Understanding PIM Shared Tree and Source Tree, page 44-26
Delaying the Use of PIM Shortest-Path Tree, page 44-28 (optional)
Modifying the PIM Router-Query Message Interval, page 44-29 (optional)
Understanding PIM Shared Tree and Source Tree
By default, members of a group receive data from senders to the group across a single data-distribution
tree rooted at the RP. Figure 44-5 shows this type of shared-distribution tree. Data from senders is
delivered to the RP for distribution to group members joined to the shared tree.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
44-26
OL-12189-01
Chapter 44
Configuring IP Multicast Routing
Configuring Advanced PIM Features
Figure 44-5
Shared Tree and Source Tree (Shortest-Path Tree)
Source
Source tree
(shortest
path tree)
Router A
Router B
Shared tree
from RP
RP
44967
Router C
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 44-28.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
44-27
Chapter 44
Configuring IP Multicast Routing
Configuring Advanced PIM Features
Delaying the Use of PIM Shortest-Path Tree
The change from shared to source tree happens when the first data packet arrives at the last-hop router
(Router C in Figure 44-5). This change occurs because the ip pim spt-threshold global configuration
command controls that timing.
The shortest-path tree requires more memory than the shared tree but reduces delay. You might want to
postpone its use. Instead of allowing the leaf router to immediately move to the shortest-path tree, you
can specify that the traffic must first reach a threshold.
You can configure when a PIM leaf router should join the shortest-path tree for a specified group. If a
source sends at a rate greater than or equal to the specified kbps rate, the multilayer switch triggers a
PIM join message toward the source to construct a source tree (shortest-path tree). If the traffic rate from
the source drops below the threshold value, the leaf router switches back to the shared tree and sends a
prune message toward the source.
You can specify to which groups the shortest-path tree threshold applies by using a group list (a standard
access list). If a value of 0 is specified or if the group list is not used, the threshold applies to all groups.
Beginning in privileged EXEC mode, follow these steps to configure a traffic rate threshold that must be
reached before multicast routing is switched from the source tree to the shortest-path tree. This
procedure is optional.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
access-list access-list-number {deny |
permit} source [source-wildcard]
Create a standard access list.
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}
[group-list access-list-number]
Specify the threshold that must be reached before moving to
shortest-path tree (spt).
Note
For kbps, specify the traffic rate in kilobits per second. The
default is 0 kbps.
Because of 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
44-28
OL-12189-01
Chapter 44
Configuring IP Multicast Routing
Configuring Optional IGMP Features
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.
Modifying the PIM Router-Query Message Interval
PIM routers and multilayer switches send PIM router-query messages to find which device will be the
DR for each LAN segment (subnet). The DR is responsible for sending IGMP host-query messages to
all hosts on the directly connected LAN.
With PIM DM operation, the DR has meaning only if IGMPv1 is in use. IGMPv1 does not have an IGMP
querier election process, so the elected DR functions as the IGMP querier. With PIM-SM operation, the
DR is the device that is directly connected to the multicast source. It sends PIM register messages to
notify the RP that multicast traffic from a source needs to be forwarded down the shared tree. In this
case, the DR is the device with the highest IP address.
Beginning in privileged EXEC mode, follow these steps to modify the router-query message interval.
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 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.
Configuring Optional IGMP Features
These sections contain this configuration information:
Default IGMP Configuration, page 44-30
Configuring the Switch as a Member of a Group, page 44-30 (optional)
Controlling Access to IP Multicast Groups, page 44-31 (optional)
Changing the IGMP Version, page 44-32 (optional)
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
44-29
Chapter 44
Configuring IP Multicast Routing
Configuring Optional IGMP Features
Modifying the IGMP Host-Query Message Interval, page 44-32 (optional)
Changing the IGMP Query Timeout for IGMPv2, page 44-33 (optional)
Changing the Maximum Query Response Time for IGMPv2, page 44-34 (optional)
Configuring the Switch as a Statically Connected Member, page 44-34 (optional)
Default IGMP Configuration
Table 44-3 shows the default IGMP configuration.
Table 44-3
Default IGMP Configuration
Feature
Default Setting
Multilayer switch as a member of a multicast group
No group memberships are defined.
Access to multicast groups
All groups are allowed on an interface.
IGMP version
Version 2 on all interfaces.
IGMP host-query message interval
60 seconds on all interfaces.
IGMP query timeout
60 seconds on all interfaces.
IGMP maximum query response time
10 seconds on all interfaces.
Multilayer switch as a statically connected member
Disabled.
Configuring the Switch as a Member of a Group
You can configure the switch as a member of a multicast group and discover multicast reachability in a
network. If all the multicast-capable routers and multilayer switches that you administer are members of
a multicast group, pinging that group causes all these devices to respond. The devices respond to ICMP
echo-request packets addressed to a group of which they are members. Another example is the multicast
trace-route tools provided in the software.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
44-30
OL-12189-01
Chapter 44
Configuring IP Multicast Routing
Configuring Optional IGMP Features
Command
Purpose
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
Controlling Access to IP Multicast Groups
The switch sends IGMP host-query messages to find which multicast groups have members on attached
local networks. The switch then forwards to these group members all packets addressed to the multicast
group. You can place a filter on each interface to restrict the multicast groups that hosts on the subnet
serviced by the interface can join.
Beginning in privileged EXEC mode, follow these steps to filter multicast groups allowed on an
interface. 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 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.
Step 5
access-list access-list-number {deny |
permit} source [source-wildcard]
Create a standard access list.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
44-31
Chapter 44
Configuring IP Multicast Routing
Configuring Optional IGMP Features
Command
Purpose
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
Changing the IGMP Version
By default, the switch uses IGMP Version 2, which provides features such as the IGMP query timeout
and the maximum query response time.
All systems on the subnet must support the same version. The switch does not automatically detect
Version 1 systems and switch to Version 1. You can mix Version 1 and Version 2 hosts on the subnet
because Version 2 routers or switches always work correctly with IGMPv1 hosts.
Configure the switch for Version 1 if your hosts do not support Version 2.
Beginning in privileged EXEC mode, follow these steps to change the IGMP version. 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 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.
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.
Modifying the IGMP Host-Query Message Interval
The switch periodically sends IGMP host-query messages to discover which multicast groups are present
on attached networks. These messages are sent to the all-hosts multicast group (224.0.0.1) with a
time-to-live (TTL) of 1. The switch sends host-query messages to refresh its knowledge of memberships
present on the network. If, after some number of queries, the software discovers that no local hosts are
members of a multicast group, the software stops forwarding multicast packets to the local network from
remote origins for that group and sends a prune message upstream toward the source.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
44-32
OL-12189-01
Chapter 44
Configuring IP Multicast Routing
Configuring Optional IGMP Features
The switch elects a PIM designated router (DR) for the LAN (subnet). The DR is the router or multilayer
switch with the highest IP address for IGMPv2. For IGMPv1, the DR is elected according to the
multicast routing protocol that runs on the LAN. The designated router is responsible for sending IGMP
host-query messages to all hosts on the LAN. In sparse mode, the designated router also sends PIM
register and PIM join messages toward the RP router.
Beginning in privileged EXEC mode, follow these steps to modify the host-query interval. 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 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.
Changing the IGMP Query Timeout for IGMPv2
If you are using IGMPv2, you can specify the period of time before the switch takes over as the querier
for the interface. By default, the switch waits twice the query interval controlled by the ip igmp
query-interval interface configuration command. After that time, if the switch has received no queries,
it becomes the querier.
You can configure the query interval by entering the show ip igmp interface interface-id privileged
EXEC command.
Beginning in privileged EXEC mode, follow these steps to change the IGMP query timeout. 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 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
44-33
Chapter 44
Configuring IP Multicast Routing
Configuring Optional IGMP Features
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 querier-timeout interface configuration command.
Changing the Maximum Query Response Time for IGMPv2
If you are using IGMPv2, you can change the maximum query response time advertised in IGMP
queries. The maximum query response time enables the switch to quickly detect that there are no more
directly connected group members on a LAN. Decreasing the value enables the switch to prune groups
faster.
Beginning in privileged EXEC mode, follow these steps to change the maximum query response time.
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 query-max-response-time
seconds
Change the maximum query response time advertised in IGMP queries.
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.
The default is 10 seconds. The range is 1 to 25.
To return to the default setting, use the no ip igmp query-max-response-time interface configuration
command.
Configuring the Switch as a Statically Connected Member
Sometimes there is either no group member on a network segment or a host cannot report its group
membership by using IGMP. However, you might want multicast traffic to go to that network segment.
These are ways to pull multicast traffic down to a network segment:
Use the ip igmp join-group interface configuration command. With this method, the switch accepts
the multicast packets in addition to forwarding them. Accepting the multicast packets prevents the
switch from fast switching.
Use the ip igmp static-group interface configuration command. With this method, the switch does
not accept the packets itself, but only forwards them. This method enables fast switching. The
outgoing interface appears in the IGMP cache, but the switch itself is not a member, as evidenced
by lack of an L (local) flag in the multicast route entry.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
44-34
OL-12189-01
Chapter 44
Configuring IP Multicast Routing
Configuring Optional Multicast Routing Features
Beginning in privileged EXEC mode, follow these steps to configure the switch itself to be a statically
connected member of a group (and enable fast switching). 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 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.
Configuring Optional Multicast Routing Features
These sections describe how to configure optional multicast routing features:
Features for Layer 2 connectivity and MBONE multimedia conference session and set up:
Enabling CGMP Server Support, page 44-35 (optional)
Configuring sdr Listener Support, page 44-36 (optional)
Features that control bandwidth utilization:
Configuring an IP Multicast Boundary, page 44-37 (optional)
Procedure for configuring a multicast within a VPN routing/forwarding(VRF) table:
Configuring Multicast VRFs, page 38-78 (optional)
Enabling CGMP Server Support
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 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.
Beginning in privileged EXEC mode, follow these steps to enable the CGMP server on the switch
interface. This procedure is optional.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
44-35
Chapter 44
Configuring IP Multicast Routing
Configuring Optional Multicast Routing Features
Step 3
Command
Purpose
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.
Configuring sdr Listener Support
The MBONE is the small subset of Internet routers and hosts that are interconnected and capable of
forwarding IP multicast traffic. Other multimedia content is often broadcast over the MBONE. Before
you can join a multimedia session, you need to know what multicast group address and port are being
used for the session, when the session is going to be active, and what sort of applications (audio, video,
and so forth) are required on your workstation. The MBONE Session Directory Version 2 (sdr) tool
provides this information. This freeware application can be downloaded from several sites on the World
Wide Web, one of which is http://www.video.ja.net/mice/index.html.
SDR is a multicast application that listens to a well-known multicast group address and port for Session
Announcement Protocol (SAP) multicast packets from SAP clients, which announce their conference
sessions. These SAP packets contain a session description, the time the session is active, its IP multicast
group addresses, media format, contact person, and other information about the advertised multimedia
session. The information in the SAP packet is displayed in the SDR Session Announcement window.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
44-36
OL-12189-01
Chapter 44
Configuring IP Multicast Routing
Configuring Optional Multicast Routing Features
Enabling sdr Listener Support
By default, the switch does not listen to session directory advertisements.
Beginning in privileged EXEC mode, follow these steps to enable the switch to join the default session
directory group (224.2.127.254) on the interface and listen to session directory advertisements. This
procedure is optional.
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 support.
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.
Limiting How Long an sdr Cache Entry Exists
By default, entries are never deleted from the sdr cache. You can limit how long the entry remains active
so that if a source stops advertising SAP information, old advertisements are not needlessly kept.
Beginning in privileged EXEC mode, follow these steps to limit how long an sdr cache entry stays active
in the cache. This procedure is optional.
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.
Configuring an IP Multicast Boundary
Administratively-scoped boundaries can be used to limit the forwarding of multicast traffic outside of a
domain or subdomain. This approach uses a special range of multicast addresses, called
administratively-scoped addresses, as the boundary mechanism. If you configure an
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
44-37
Chapter 44
Configuring IP Multicast Routing
Configuring Optional Multicast Routing Features
administratively-scoped boundary on a routed interface, multicast traffic whose multicast group
addresses fall in this range can not enter or exit this interface, thereby providing a firewall for multicast
traffic in this address range.
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 44-6 shows that Company XYZ has an administratively-scoped boundary set for the multicast
address range 239.0.0.0/8 on all routed interfaces 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.
Figure 44-6
Administratively-Scoped Boundaries
Company XYZ
239.128.0.0/16
45154
Marketing
Engineering
239.0.0.0/8
You can define an administratively-scoped boundary on a routed interface 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
44-38
OL-12189-01
Chapter 44
Configuring IP Multicast Routing
Configuring Basic DVMRP Interoperability Features
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 |
permit} source [source-wildcard]
Create a standard access list, repeating the command as many times 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 3
interface interface-id
Specify the interface to be configured, and enter interface configuration
mode.
Step 4
ip multicast boundary
access-list-number
Configure the boundary, specifying the access list you created 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 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
Configuring Basic DVMRP Interoperability Features
These sections contain this configuration information:
Configuring DVMRP Interoperability, page 44-40 (optional)
Configuring a DVMRP Tunnel, page 44-42 (optional)
Advertising Network 0.0.0.0 to DVMRP Neighbors, page 44-43 (optional)
Responding to mrinfo Requests, page 44-44 (optional)
For more advanced DVMRP features, see the Configuring Advanced DVMRP Interoperability
Features section on page 44-44.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
44-39
Chapter 44
Configuring IP Multicast Routing
Configuring Basic DVMRP Interoperability Features
Configuring DVMRP Interoperability
Cisco multicast routers and multilayer switches using PIM can interoperate with non-Cisco multicast
routers that use the DVMRP.
PIM devices dynamically discover DVMRP multicast routers on attached networks by listening to
DVMR probe messages. When a DVMRP neighbor has been discovered, the PIM device periodically
sends DVMRP report messages advertising the unicast sources reachable in the PIM domain. By default,
directly connected subnets and networks are advertised. The device forwards multicast packets that have
been forwarded by DVMRP routers and, in turn, forwards multicast packets to DVMRP routers.
You can configure an access list on the PIM routed interface connected to the MBONE to limit the
number of unicast routes that are advertised in DVMRP route reports. Otherwise, all routes in the unicast
routing table are advertised.
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 |
permit} source [source-wildcard]
Create a standard access list, repeating the command as many times 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 3
interface interface-id
Specify the interface connected to the MBONE and enabled for
multicast routing, and enter interface configuration mode.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
44-40
OL-12189-01
Chapter 44
Configuring IP Multicast Routing
Configuring Basic DVMRP Interoperability Features
Command
Step 4
Purpose
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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
44-41
Chapter 44
Configuring IP Multicast Routing
Configuring Basic DVMRP Interoperability Features
Configuring a DVMRP Tunnel
The software supports DVMRP tunnels to the MBONE. You can configure a DVMRP tunnel on a router
or multilayer switch if the other end is running DVMRP. The software then sends and receives multicast
packets through the tunnel. This strategy enables a PIM domain to connect to the DVMRP router when
all routers on the path do not support multicast routing. You cannot configure a DVMRP tunnel between
two routers.
When a Cisco router or multilayer switch runs DVMRP through a tunnel, it advertises sources in
DVMRP report messages, much as it does on real networks. The software also caches DVMRP report
messages it receives and uses them in its RPF calculation. This behavior enables the software to forward
multicast packets received through the tunnel.
When you configure a DVMRP tunnel, you should assign an IP address to a tunnel in these cases:
To send IP packets through the tunnel
To configure the software to perform DVMRP summarization
The software does not advertise subnets through the tunnel if the tunnel has a different network number
from the subnet. In this case, the software advertises only the network number through the tunnel.
Beginning in privileged EXEC mode, follow these steps to configure a DVMRP tunnel. This procedure
is optional.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
access-list access-list-number {deny |
permit} source [source-wildcard]
Create a standard access list, repeating the command as many times 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 3
interface tunnel number
Specify a tunnel interface, and enter interface configuration mode.
Step 4
tunnel source ip-address
Specify the source address of the tunnel interface. Enter the IP address
of the interface on the switch.
Step 5
tunnel destination ip-address
Specify the destination address of the tunnel interface. 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.
ip pim [dense-mode | sparse-mode]
Configure the PIM mode on the interface.
Step 8
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
44-42
OL-12189-01
Chapter 44
Configuring IP Multicast Routing
Configuring Basic DVMRP Interoperability Features
Step 9
Command
Purpose
ip dvmrp accept-filter
access-list-number [distance]
neighbor-list access-list-number
Configure an acceptance filter for incoming DVMRP reports.
By default, all destination reports are accepted with a distance of 0.
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.
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
Advertising Network 0.0.0.0 to DVMRP Neighbors
If your switch is a neighbor of an mrouted Version 3.6 device, you can configure the software to advertise
network 0.0.0.0 (the default route) to the DVMRP neighbor. The DVMRP default route computes the
RPF information for any multicast sources that do not match a more specific route.
Do not advertise the DVMRP default into the MBONE.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
44-43
Chapter 44
Configuring IP Multicast Routing
Configuring Advanced DVMRP Interoperability Features
Beginning in privileged EXEC mode, follow these steps to advertise network 0.0.0.0 to DVMRP
neighbors on an interface. This procedure is optional.
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
{originate | only}
Advertise network 0.0.0.0 to DVMRP neighbors.
Use this command only when the switch is a neighbor of mrouted
Version 3.6 machines.
The keywords have these meanings:
originateSpecifies that other routes more specific than 0.0.0.0 can
also be advertised.
onlySpecifies that no DVMRP routes other than 0.0.0.0 are
advertised.
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.
Responding to mrinfo Requests
The software answers mrinfo requests sent by mrouted systems and Cisco routers and multilayer
switches. The software returns information about neighbors through DVMRP tunnels and all the routed
interfaces. This information includes the metric (always set to 1), the configured TTL threshold, the
status of the interface, and various flags. You can also use the mrinfo privileged EXEC command to
query the router or switch itself, as in this example:
Switch# mrinfo
171.69.214.27 (mm1-7kd.cisco.com) [version cisco 11.1] [flags: PMS]:
171.69.214.27 -> 171.69.214.26 (mm1-r7kb.cisco.com) [1/0/pim/querier]
171.69.214.27 -> 171.69.214.25 (mm1-45a.cisco.com) [1/0/pim/querier]
171.69.214.33 -> 171.69.214.34 (mm1-45c.cisco.com) [1/0/pim]
171.69.214.137 -> 0.0.0.0 [1/0/pim/querier/down/leaf]
171.69.214.203 -> 0.0.0.0 [1/0/pim/querier/down/leaf]
171.69.214.18 -> 171.69.214.20 (mm1-45e.cisco.com) [1/0/pim]
171.69.214.18 -> 171.69.214.19 (mm1-45c.cisco.com) [1/0/pim]
171.69.214.18 -> 171.69.214.17 (mm1-45a.cisco.com) [1/0/pim]
Configuring Advanced DVMRP Interoperability Features
Cisco routers and multilayer switches run PIM to forward multicast packets to receivers and receive
multicast packets from senders. It is also possible to propagate DVMRP routes into and through a PIM
cloud. PIM uses this information; however, Cisco routers and multilayer switches do not implement
DVMRP to forward multicast packets.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
44-44
OL-12189-01
Chapter 44
Configuring IP Multicast Routing
Configuring Advanced DVMRP Interoperability Features
These sections contain this configuration information:
Enabling DVMRP Unicast Routing, page 44-45 (optional)
Rejecting a DVMRP Nonpruning Neighbor, page 44-46 (optional)
Controlling Route Exchanges, page 44-47 (optional)
For information on basic DVMRP features, see the Configuring Basic DVMRP Interoperability
Features section on page 44-39.
Enabling DVMRP Unicast Routing
Because multicast routing and unicast routing require separate topologies, PIM must follow the
multicast topology to build loopless distribution trees. Using DVMRP unicast routing, Cisco routers,
multilayer switches, and mrouted-based machines exchange DVMRP unicast routes, to which PIM can
then reverse-path forward.
Cisco devices do not perform DVMRP multicast routing among each other, but they can exchange
DVMRP routes. The DVMRP routes provide a multicast topology that might differ from the unicast
topology. This enables PIM to run over the multicast topology, thereby enabling sparse-mode PIM over
the MBONE topology.
When DVMRP unicast routing is enabled, the router or switch caches routes learned in DVMRP report
messages in a DVMRP routing table. When PIM is running, these routes might be preferred over routes
in the unicast routing table, enabling PIM to run on the MBONE topology when it is different from the
unicast topology.
DVMRP unicast routing can run on all interfaces. For DVMRP tunnels, it uses DVMRP multicast
routing. This feature does not enable DVMRP multicast routing among Cisco routers and multilayer
switches. However, if there is a DVMRP-capable multicast router, the Cisco device can do PIM/DVMRP
multicast routing.
Beginning in privileged EXEC mode, follow these steps to enable DVMRP unicast routing. This
procedure is optional.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
44-45
Chapter 44
Configuring IP Multicast Routing
Configuring Advanced DVMRP Interoperability Features
Rejecting a DVMRP Nonpruning Neighbor
By default, Cisco devices accept all DVMRP neighbors as peers, regardless of their DVMRP capability.
However, some non-Cisco devices run old versions of DVMRP that cannot prune, so they continuously
receive forwarded packets, wasting bandwidth. Figure 44-7 shows this scenario.
Figure 44-7
Leaf Nonpruning DVMRP Neighbor
Source router or RP
RP
PIM dense mode
Router A
Valid
multicast
traffic
Router B
Receiver
Layer 3 switch
Leaf nonpruning
DVMRP device
Stub LAN with no members
101244
Unnecessary
multicast
traffic
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 44-8. 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
44-46
OL-12189-01
Chapter 44
Configuring IP Multicast Routing
Configuring Advanced DVMRP Interoperability Features
Figure 44-8
Router Rejects Nonpruning DVMRP Neighbor
Source router or RP
RP
Router A
Multicast
traffic gets
to receiver,
not to leaf
DVMRP
device
Router B
Receiver
Layer 3 switch
Leaf nonpruning DVMRP device
101245
Configure the ip dvmrp
reject-non-pruners command
on this interface.
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.
Controlling Route Exchanges
These sections describe how to tune the Cisco device advertisements of DVMRP routes:
Limiting the Number of DVMRP Routes Advertised, page 44-48 (optional)
Changing the DVMRP Route Threshold, page 44-48 (optional)
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
44-47
Chapter 44
Configuring IP Multicast Routing
Configuring Advanced DVMRP Interoperability Features
Configuring a DVMRP Summary Address, page 44-49 (optional)
Disabling DVMRP Autosummarization, page 44-51 (optional)
Adding a Metric Offset to the DVMRP Route, page 44-51 (optional)
Limiting the Number of DVMRP Routes Advertised
By default, only 7000 DVMRP routes are advertised over an interface enabled to run DVMRP (that is,
a DVMRP tunnel, an interface where a DVMRP neighbor has been discovered, or an interface configured
to run the ip dvmrp unicast-routing interface configuration command).
Beginning in privileged EXEC mode, follow these steps to change the DVMRP route limit. This
procedure is optional.
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.
Changing the DVMRP Route Threshold
By default, 10,000 DVMRP routes can be received per interface within a 1-minute interval. When that
rate is exceeded, a syslog message is issued, warning that there might be a route surge occurring. The
warning is typically used to quickly detect when devices have been misconfigured to inject a large
number of routes into the MBONE.
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
route-count
Configure the number of routes that trigger a syslog 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.
The default is 10,000 routes. The range is 1 to 4294967295.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
44-48
OL-12189-01
Chapter 44
Configuring IP Multicast Routing
Configuring Advanced DVMRP Interoperability Features
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.
Configuring a DVMRP Summary Address
By default, a Cisco device advertises in DVMRP route-report messages only connected unicast routes
(that is, only routes to subnets that are directly connected to the router) from its unicast routing table.
These routes undergo normal DVMRP classful route summarization. This process depends on whether
the route being advertised is in the same classful network as the interface over which it is being
advertised.
Figure 44-9 shows an example of the default behavior. This example shows that the DVMRP report sent
by the Cisco router contains the three original routes received from the DVMRP router that have been
poison-reversed by adding 32 to the DVMRP metric. Listed after these routes are two routes that are
advertisements for the two directly connected networks (176.32.10.0/24 and 176.32.15.0/24) that were
taken from the unicast routing table. Because the DVMRP tunnel shares the same IP address as Fast
Ethernet port 1 and falls into the same Class B network as the two directly connected subnets, classful
summarization of these routes was not performed. As a result, the DVMRP router is able to
poison-reverse only these two routes to the directly connected subnets and is able to only RPF properly
for multicast traffic sent by sources on these two Ethernet segments. Any other multicast source in the
network behind the Cisco router that is not on these two Ethernet segments does not properly RPF-check
on the DVMRP router and is discarded.
You can force the Cisco router to advertise the summary address (specified by the address and mask pair
in the ip dvmrp summary-address address mask interface configuration command) in place of any
route that falls in this address range. The summary address is sent in a DVMRP route report if the unicast
routing table contains at least one route in this range; otherwise, the summary address is not advertised.
In Figure 44-9, you configure the ip dvmrp summary-address command on the Cisco router tunnel
interface. As a result, the Cisco router sends only a single summarized Class B advertisement for
network 176.32.0.0.16 from the unicast routing table.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
44-49
Chapter 44
Configuring IP Multicast Routing
Configuring Advanced DVMRP Interoperability Features
Figure 44-9
On Connected Unicast Routes Are Advertised by Default
interface tunnel 0
ip unnumbered gigabitethernet1/0/1
DVMRP Report
151.16.0.0/16
m = 39
172.34.15.0/24
m = 42
202.13.3.0/24
m = 40
176.32.10.0/24
m=1
176.32.15.0/24
m=1
interface gigabitethernet1/0/1
ip addr 176.32.10.1 255.255.255.0
ip pim dense-mode
DVMRP router
interface gigabitethernet1/0/2
ip addr 176.32.15.1 255.255.255.0
ip pim dense-mode
Tunnel
Cisco
router
Src Network
151.16.0/16
172.34.15.0/24
202.13.3.0/24
Intf
Gi1/0/1
Gi1/0/1
Gi1/0/1
Metric
7
10
8
Dist
0
0
Gigabit
0
Ethernet
1/0/1
176.32.10.0/24
Unicast Routing Table (10,000 Routes)
Network
176.13.10.0/24
Gigabit 176.32.15.0/24
Ethernet 176.32.20.0/24
1/0/2
Intf
Gi1/0/1
Gi1/0/2
Gi1/0/2
Metric
10514432
10512012
45106372
Dist
90
90
90
159888
DVMRP Route Table
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 command.
Step 3
ip dvmrp summary-address address
mask [metric value]
Specify a DVMRP summary address.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
44-50
OL-12189-01
Chapter 44
Configuring IP Multicast Routing
Configuring Advanced DVMRP Interoperability Features
Disabling DVMRP Autosummarization
By default, the software automatically performs some level of DVMRP summarization. Disable this
function if you want to advertise all routes, not just a summary. In some special cases, you can use the
neighboring DVMRP router with all subnet information to better control the flow of multicast traffic in
the DVMRP network. One such case might occur if the PIM network is connected to the DVMRP cloud
at several points and more specific (unsummarized) routes are being injected into the DVMRP network
to advertise better paths to individual subnets inside the PIM cloud.
If you configure the ip dvmrp summary-address interface configuration command and did not
configure no ip dvmrp auto-summary, you get both custom and autosummaries.
Beginning in privileged EXEC mode, follow these steps to disable DVMRP autosummarization. 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 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.
Adding a Metric Offset to the DVMRP Route
By default, the switch increments by one the metric (hop count) of a DVMRP route advertised in
incoming DVMRP reports. You can change the metric if you want to favor or not favor a certain route.
For example, a route is learned by multilayer switch A, and the same route is learned by multilayer
switch B with a higher metric. If you want to use the path through switch B because it is a faster path,
you can apply a metric offset to the route learned by switch A to make it larger than the metric learned
by switch B, and you can choose the path through switch B.
Beginning in privileged EXEC mode, follow these steps to change the default metric. 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
44-51
Chapter 44
Configuring IP Multicast Routing
Monitoring and Maintaining IP Multicast Routing
Step 3
Command
Purpose
ip dvmrp metric-offset [in | out]
increment
Change the metric added to DVMRP routes advertised in incoming
reports.
The keywords have these meanings:
(Optional) inSpecifies that the increment value is added to
incoming DVMRP reports and is reported in mrinfo replies.
(Optional) outSpecifies 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.
Monitoring and Maintaining IP Multicast Routing
These sections describe how to monitor and maintain IP multicast routing:
Clearing Caches, Tables, and Databases, page 44-52
Displaying System and Network Statistics, page 44-53
Monitoring IP Multicast Routing, page 44-54
Clearing Caches, Tables, and Databases
You can remove all contents of a particular cache, table, or database. Clearing a cache, table, or database
might be necessary when the contents of the particular structure are or suspected to be invalid.
You can use any of the privileged EXEC commands in Table 44-4 to clear IP multicast caches, tables,
and databases:
Table 44-4
Commands for Clearing Caches, Tables, and Databases
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
44-52
OL-12189-01
Chapter 44
Configuring IP Multicast Routing
Monitoring and Maintaining IP Multicast Routing
Table 44-4
Commands for Clearing Caches, Tables, and Databases (continued)
Command
Purpose
clear ip igmp group [group-name |
group-address | interface]
Delete entries from the IGMP cache.
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.
Displaying System and Network Statistics
You can display specific statistics, such as the contents of IP routing tables, caches, and databases.
Note
This release does not support per-route statistics.
You can display information to learn resource usage and solve network problems. You can also display
information about node reachability and discover the routing path that packets of your device are taking
through the network.
You can use any of the privileged EXEC commands in Table 44-5 to display various routing statistics:
Table 44-5
Commands for Displaying System and Network 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 |
group-address | type number]
Display the multicast groups that are directly
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]
[group-address | name] [detail]
Display the contents of the circular cache-header
buffer.
show ip mroute [group-name | group-address]
[source] [summary] [count] [active kbps]
Display the contents of the IP multicast routing
table.
show ip pim interface [type number] [count]
[detail]
Display information about interfaces configured
for PIM. This command is available in all software
images.
show ip pim neighbor [type number]
List the PIM neighbors discovered by the switch.
This command is available in all software images.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
44-53
Chapter 44
Configuring IP Multicast Routing
Monitoring and Maintaining IP Multicast Routing
Table 44-5
Commands for Displaying System and Network Statistics (continued)
Command
Purpose
show ip pim rp [group-name | group-address]
Display the RP routers associated with a
sparse-mode multicast group. This command is
available in all software images.
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.
Monitoring IP Multicast Routing
You can use the privileged EXEC commands in Table 44-6 to monitor IP multicast routers, packets, and
paths:
Table 44-6
Commands for Monitoring IP Multicast Routing
Command
Purpose
mrinfo [hostname | address] [source-address |
interface]
Query a multicast router or multilayer switch about
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
44-54
OL-12189-01
CH A P T E R
45
Configuring MSDP
This chapter describes how to configure the Multicast Source Discovery Protocol (MSDP) on the
Catalyst Switch Module 3110. 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.
To use this feature, the switch or stack master must be running the IP services feature set. Unless
otherwise noted, the term switch refers to a standalone switch and to a switch stack.
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.
This chapter consists of these sections:
Note
Understanding MSDP, page 45-1
Configuring MSDP, page 45-3
Monitoring and Maintaining MSDP, page 45-18
The Catalyst Switch Module 3012 does not support MDSP.
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 Transmission Control Protocol (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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
45-1
Chapter 45
Configuring MSDP
Understanding MSDP
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 domains 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 45-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 45-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 sources 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
45-2
OL-12189-01
Chapter 45
Configuring MSDP
Configuring MSDP
Figure 45-1
MSDP Running Between RP Peers
MSDP peer
RP + MSDP peer
MSDP SA
SD
SA
Peer RPF flooding
MSDP SA
TCP connection
BGP
Receiver
MSDP peer
201788
Register
Multicast
(S,G) Join
PIM
DR
Source
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 contain this configuration information:
Default MSDP Configuration, page 45-4
Configuring a Default MSDP Peer, page 45-4 (required)
Caching Source-Active State, page 45-6 (optional)
Requesting Source Information from an MSDP Peer, page 45-8 (optional)
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
45-3
Chapter 45
Configuring MSDP
Configuring MSDP
Controlling Source Information that Your Switch Originates, page 45-8 (optional)
Controlling Source Information that Your Switch Forwards, page 45-11 (optional)
Controlling Source Information that Your Switch Receives, page 45-13 (optional)
Configuring an MSDP Mesh Group, page 45-15 (optional)
Shutting Down an MSDP Peer, page 45-15 (optional)
Including a Bordering PIM Dense-Mode Region in MSDP, page 45-16 (optional)
Configuring an Originating Address other than the RP Address, page 45-17 (optional)
Default MSDP Configuration
MSDP is not enabled, and no default MSDP peer exists.
Configuring a Default MSDP Peer
In this software release, because BGP and MBGP are not supported, you cannot configure an MSDP peer
on the local switch by using the ip msdp peer global configuration command. Instead, you define a
default MSDP peer (by using the ip msdp default-peer global configuration command) from which to
accept all SA messages for the switch. The default MSDP peer must be a previously configured MSDP
peer. Configure a default MSDP peer when the switch is not BGP- or MBGP-peering with an MSDP
peer. If a single MSDP peer is configured, the switch always accepts all SA messages from that peer.
Figure 45-2 shows a network in which default MSDP peers might be used. In Figure 45-2, a customer
who owns Switch B is connected to the Internet through two Internet service providers (ISPs), one
owning Router A and the other owning Router C. They are not running BGP or MBGP between them.
To learn about sources in the ISPs domain or in other domains, Switch B at the customer site identifies
Router A as its default MSDP peer. Switch B advertises SA messages to both Router A and Router C but
accepts SA messages only from Router A or only from Router C. If Router A is first in the configuration
file, it is used if it is running. If Router A is not running, only then does Switch B accept SA messages
from Router C. This is the default behavior without a prefix list.
If you specify a prefix list, the peer is a default peer only for the prefixes in the list. You can have multiple
active default peers when you have a prefix list associated with each. When you do not have any prefix
lists, you can configure multiple default peers, but only the first one is the active default peer as long as
the router has connectivity to this peer and the peer is alive. If the first configured peer fails or the
connectivity to this peer fails, the second configured peer becomes the active default, and so on.
The ISP probably uses a prefix list to define which prefixes it accepts from the customers router.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
45-4
OL-12189-01
Chapter 45
Configuring MSDP
Configuring MSDP
Figure 45-2
Default MSDP Peer Network
Router C
Default MSDP peer
ISP C PIM domain
SA
SA
SA
10.1.1.1
Default MSDP peer
Default MSDP peer
ISP A PIM domain
Customer PIM domain
86515
Switch B
Router A
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
[prefix-list list]
Define a default peer from which to accept all MSDP SA messages.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
45-5
Chapter 45
Configuring MSDP
Configuring MSDP
Step 3
Step 4
Command
Purpose
ip prefix-list name [description string] |
seq number {permit | deny} network
length
(Optional) Create a prefix list using the name specified in Step 2.
ip msdp description {peer-name |
peer-address} text
(Optional) For description string, enter a description of up to 80
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.
(Optional) Configure a description for the specified peer to make it
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 45-2. Each of these ISPs
have more than one customer (like the customer in Figure 45-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/1
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/1
Caching Source-Active State
By default, the switch does not cache source/group pairs from received SA messages. When the switch
forwards the MSDP SA information, it does not store it in memory. Therefore, if a member joins a group
soon after a SA message is received by the local RP, that member needs to wait until the next SA message
to hear about the source. This delay is known as join latency.
If you want to sacrifice some memory in exchange for reducing the latency of the source information,
you can configure the switch to cache SA messages.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
45-6
OL-12189-01
Chapter 45
Configuring MSDP
Configuring MSDP
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
access-list-number]
Enable the caching of source/group pairs (create an SA state). Those
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 |
permit} protocol source source-wildcard
destination destination-wildcard
Create an IP extended access list, repeating the command as many times
as necessary.
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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
45-7
Chapter 45
Configuring MSDP
Configuring MSDP
Requesting Source Information from an MSDP Peer
Local RPs can send SA requests and get immediate responses for all active sources for a given group.
By default, the switch does not send any SA request messages to its MSDP peers when a new member
joins a group and wants to receive multicast traffic. The new member waits to receive the next periodic
SA message.
If you want a new member of a group to learn the active multicast sources in a connected PIM
sparse-mode domain that are sending to a group, configure the switch to send SA request messages to
the specified MSDP peer when a new member joins a group. The peer replies with the information in its
SA cache. If the peer does not have a cache configured, this command has no result. Configuring this
feature reduces join latency but sacrifices memory.
Beginning in privileged EXEC mode, follow these steps to configure the switch to send SA request
messages to the MSDP peer when a new member joins a group and wants to receive multicast traffic.
This procedure is optional.
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
Controlling Source Information that Your Switch Originates
You can control the multicast source information that originates with your switch:
Sources you advertise (based on your sources)
Receivers of source information (based on knowing the requestor)
For more information, see the Redistributing Sources section on page 45-9 and the Filtering
Source-Active Request Messages section on page 45-10.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
45-8
OL-12189-01
Chapter 45
Configuring MSDP
Configuring MSDP
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
access-list-name] [asn
aspath-access-list-number] [route-map
map]
Configure which (S,G) entries from the multicast routing table are
advertised in SA messages.
By default, only sources within the local domain are advertised.
(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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
45-9
Chapter 45
Configuring MSDP
Configuring MSDP
Step 3
Command
Purpose
access-list access-list-number {deny |
permit} source [source-wildcard]
Create an IP standard access list, repeating the command as many times
as necessary.
or
or
access-list access-list-number {deny |
permit} protocol source source-wildcard
destination destination-wildcard
Create an IP extended access list, repeating the command as many times
as necessary.
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.
Filtering Source-Active Request Messages
By default, only switches that are caching SA information can respond to SA requests. By default, such
a switch honors all SA request messages from its MSDP peers and supplies the IP addresses of the active
sources.
However, you can configure the switch to ignore all SA requests from an MSDP peer. You can also honor
only those SA request messages from a peer for groups described by a standard access list. If the groups
in the access list pass, SA request messages are accepted. All other such messages from the peer for other
groups are ignored.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
45-10
OL-12189-01
Chapter 45
Configuring MSDP
Configuring MSDP
Beginning in privileged EXEC mode, follow these steps to configure one of these options. This
procedure is optional.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ip msdp filter-sa-request ip-address |
name
Filter all SA request messages from the specified MSDP peer.
or
Step 3
or
ip msdp filter-sa-request {ip-address |
name} list access-list-number
Filter SA request messages from the specified MSDP peer for groups
that pass the standard access list. The access list describes a multicast
group address. The range for the access-list-number is 1 to 99.
access-list access-list-number {deny |
permit} source [source-wildcard]
Create an IP standard access list, repeating the command as many times
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
Controlling Source Information that Your Switch Forwards
By default, the switch forwards all SA messages it receives to all its MSDP peers. However, you can
prevent outgoing messages from being forwarded to a peer by using a filter or by setting a time-to-live
(TTL) value. These methods are described in the next sections.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
45-11
Chapter 45
Configuring MSDP
Configuring MSDP
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
extended access list. The range for the extended access-list-number
list 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 |
permit} protocol source source-wildcard
destination destination-wildcard
(Optional) Create an IP extended access list, repeating the command as
many times as necessary.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
45-12
OL-12189-01
Chapter 45
Configuring MSDP
Configuring MSDP
Command
Purpose
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 gigabitethernet0/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
Using TTL to Limit the Multicast Data Sent in SA Messages
You can use a TTL value to control what data is encapsulated in the first SA message for every source.
Only multicast packets with an IP-header TTL greater than or equal to the ttl argument are sent to the
specified MSDP peer. For example, you can limit internal traffic to a TTL of 8. If you want other groups
to go to external locations, you must send those packets with a TTL greater than 8.
Beginning in privileged EXEC mode, follow these steps to establish a TTL threshold. This procedure is
optional.
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.
Controlling Source Information that Your Switch Receives
By default, the switch receives all SA messages that its MSDP RPF peers send to it. However, you can
control the source information that you receive from MSDP peers by filtering incoming SA messages.
In other words, you can configure the switch to not accept them.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
45-13
Chapter 45
Configuring MSDP
Configuring MSDP
You can perform one of these actions:
Filter all incoming SA messages from an MSDP peer
Specify an IP extended access list to pass 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 in ip-address | name
Filter all SA messages from the specified MSDP peer.
or
or
ip msdp sa-filter in {ip-address | name}
list access-list-number
From the specified peer, pass only those SA messages that pass the IP
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}
route-map map-tag
From the specified MSDP peer, pass only those SA messages that meet
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 |
permit} protocol source source-wildcard
destination destination-wildcard
(Optional) Create an IP extended access list, repeating the command as
many times as necessary.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
45-14
OL-12189-01
Chapter 45
Configuring MSDP
Configuring MSDP
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
Configuring an MSDP Mesh Group
An MSDP mesh group is a group of MSDP speakers that have fully meshed MSDP connectivity among
one another. Any SA messages received from a peer in a mesh group are not forwarded to other peers in
the same mesh group. Thus, you reduce SA message flooding and simplify peer-RPF flooding. Use the
ip msdp mesh-group global configuration command when there are multiple RPs within a domain. It is
especially used to send SA messages across a domain. You can configure multiple mesh groups (with
different names) in a single switch.
Beginning in privileged EXEC mode, follow these steps to create a mesh group. This procedure is
optional.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ip msdp mesh-group name {ip-address |
name}
Configure an MSDP mesh group, and specify the MSDP peer belonging
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.
Shutting Down an MSDP Peer
If you want to configure many MSDP commands for the same peer and you do not want the peer to
become active, you can shut down the peer, configure it, and later bring it up. When a peer is shut down,
the TCP connection is terminated and is not restarted. You can also shut down an MSDP session without
losing configuration information for the peer.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
45-15
Chapter 45
Configuring MSDP
Configuring MSDP
Beginning in privileged EXEC mode, follow these steps to shut down a peer. This procedure is optional.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ip msdp shutdown {peer-name | peer
address}
Administratively shut down the specified MSDP peer without losing
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.
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
Including a Bordering PIM Dense-Mode Region in MSDP
You can configure MSDP on a switch that borders a PIM sparse-mode region with a dense-mode region.
By default, active sources in the dense-mode region do not participate in MSDP.
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
Step 4
ip msdp redistribute [list
access-list-name] [asn
aspath-access-list-number] [route-map
map]
Configure which (S,G) entries from the multicast routing table are
advertised in SA messages.
end
Return to privileged EXEC mode.
For more information, see the Redistributing Sources section on
page 45-9.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
45-16
OL-12189-01
Chapter 45
Configuring MSDP
Configuring MSDP
Command
Purpose
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 both the ip msdp border sa-address and the ip msdp originator-id global
configuration commands are configured, the address derived from the ip msdp originator-id command
specifies 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.
Configuring an Originating Address other than the RP Address
You can allow an MSDP speaker that originates an SA message to use the IP address of the interface as
the RP address in the SA message by changing the Originator ID. You might change the Originator ID
in one of these cases:
If you configure a logical RP on multiple switches in an MSDP mesh group.
If you have a switch that borders a PIM sparse-mode domain and a dense-mode domain. If a switch
borders a dense-mode domain for a site, and sparse-mode is being used externally, you might want
dense-mode sources to be known to the outside world. Because this switch is not an RP, it would not
have an RP address to use in an SA message. Therefore, this command provides the RP address by
specifying the address of the interface.
Beginning in privileged EXEC mode, follow these steps to allow an MSDP speaker that originates an
SA message to use the IP address on the interface as the RP address in the SA message. This procedure
is optional.
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 both the ip msdp border sa-address and the ip msdp originator-id global configuration commands
are configured, the address derived from the ip msdp originator-id command specifies 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
45-17
Chapter 45
Configuring MSDP
Monitoring and Maintaining MSDP
Monitoring and Maintaining MSDP
To monitor MSDP SA messages, peers, state, or peer status, use one or more of the privileged EXEC
commands in Table 45-1:
Table 45-1
Commands for Monitoring and Maintaining MSDP
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.
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 45-2:
Table 45-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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
45-18
OL-12189-01
CH A P T E R
46
Configuring Fallback Bridging
This chapter describes how to configure fallback bridging (VLAN bridging) on the Catalyst Switch
Module 3110. With fallback bridging, you can forward non-IP packets that the switch does not route
between VLAN bridge domains and routed ports.
To use this feature, the switch or stack master must be running the IP services feature set. Unless
otherwise noted, the term switch refers to a standalone switch and to a switch stack.
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.
This chapter consists of these sections:
Understanding Fallback Bridging, page 46-1
Configuring Fallback Bridging, page 46-3
Monitoring and Maintaining Fallback Bridging, page 46-11
Understanding Fallback Bridging
These sections describe how fallback bridging works:
Fallback Bridging Overview, page 46-1
Fallback Bridging and Switch Stacks, page 46-3
Fallback Bridging Overview
With fallback bridging, the switch bridges together two or more VLANs or routed ports, essentially
connecting multiple VLANs within one bridge domain. Fallback bridging forwards traffic that the switch
does not route and forwards traffic belonging to a nonroutable protocol such as DECnet.
A VLAN bridge domain is represented with switch virtual interfaces (SVIs). A set of SVIs and routed
ports (which do not have any VLANs associated with them) can be configured (grouped together) to
form a bridge group. Recall that an SVI represents a VLAN of switch ports as one interface to the routing
or bridging function in the system. You associate only one SVI with a VLAN, and you configure an SVI
for a VLAN only when you want to route between VLANs, to fallback-bridge nonroutable protocols
between VLANs, or to provide IP host connectivity to the switch. A routed port is a physical port that
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
46-1
Chapter 46
Configuring Fallback Bridging
Understanding Fallback Bridging
acts like a port on a router, but it is not connected to a router. A routed port is not associated with a
particular VLAN, does not support VLAN subinterfaces, but behaves like a normal routed port. For more
information about SVIs and routed ports, see Chapter 10, Configuring Interface Characteristics.
A bridge group is an internal organization of network interfaces on a switch. You cannot use bridge
groups to identify traffic switched within the bridge group outside the switch on which they are defined.
Bridge groups on the switch function as distinct bridges; that is, bridged traffic and bridge protocol data
units (BPDUs) are not exchanged between different bridge groups on a switch.
Fallback bridging does not allow the spanning trees from the VLANs being bridged to collapse. Each
VLAN has its own spanning-tree instance and a separate spanning tree, called the VLAN-bridge
spanning tree, which runs on top of the bridge group to prevent loops.
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). Any address that is learned on a
stack member is learned by all switches in the stack.
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 interfaces.
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 46-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.
Figure 46-1
Fallback Bridging Network Example
Layer 3 switch
Routed port
172.20.130.1
Host C
SVI 1
SVI 2
172.20.129.1
Blade
server B
Blade
server A
VLAN 20
VLAN 30
201789
172.20.128.1
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
46-2
OL-12189-01
Chapter 46
Configuring Fallback Bridging
Configuring Fallback Bridging
Fallback Bridging and Switch Stacks
When the stack master fails, a stack member becomes the new stack master by using the election process
described in Chapter 5, Managing Switch Stacks. The new stack master creates new VLAN-bridge
spanning-tree instance, which temporarily puts the spanning-tree ports used for fallback bridging into a
nonforwarding state. A momentary traffic disruption occurs until the spanning-tree states transition to
the forwarding state. All MAC addresses must be relearned in the bridge group.
Note
If a stack master running the IP services feature set fails and if the newly elected stack master is running
the IP base feature set, the switch stack loses its fallback bridging capability.
If stacks merge or if a switch is added to the stack, any new VLANs that are part of a bridge group and
become active are included in the VLAN-bridge STP.
When a stack member fails, the addresses learned from this member are deleted from the bridge group
MAC address table.
For more information about switch stacks, see Chapter 5, Managing Switch Stacks.
Configuring Fallback Bridging
These sections contain this configuration information:
Default Fallback Bridging Configuration, page 46-4
Fallback Bridging Configuration Guidelines, page 46-4
Creating a Bridge Group, page 46-4 (required)
Adjusting Spanning-Tree Parameters, page 46-6 (optional)
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
46-3
Chapter 46
Configuring Fallback Bridging
Configuring Fallback Bridging
Default Fallback Bridging Configuration
Table 46-1 shows the default fallback bridging configuration.
Table 46-1
Default Fallback Bridging Configuration
Feature
Default Setting
Bridge groups
None are defined or assigned to a port. No
VLAN-bridge STP is defined.
Switch forwards frames for stations that it has
dynamically learned
Enabled.
Spanning tree parameters:
Switch priority
32768.
Port priority
128.
Port path cost
10 Mb/s: 100.
100 Mb/s: 19.
1000 Mb/s: 4.
Hello BPDU interval
2 seconds.
Forward-delay interval
20 seconds.
Maximum idle interval
30 seconds.
Fallback Bridging Configuration Guidelines
Up to 32 bridge groups can be configured on the switch.
An interface (an SVI or routed port) can be a member of only one bridge group.
Use a bridge group for each separately bridged (topologically distinct) network connected to the switch.
Do not configure fallback bridging on a switch configured with private VLANs.
All protocols except IP (Version 4 and Version 6), Address Resolution Protocol (ARP), reverse ARP
(RARP), LOOPBACK, and Frame Relay ARP are fallback bridged.
Creating a Bridge Group
To configure fallback bridging for a set of SVIs or routed ports, these interfaces must be assigned to
bridge groups. All interfaces in the same group belong to the same bridge domain. Each SVI or routed
port can be assigned to only one bridge group.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
46-4
OL-12189-01
Chapter 46
Configuring Fallback Bridging
Configuring Fallback Bridging
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
vlan-bridge
Assign a bridge group number, and specify the 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
Step 4
bridge-group bridge-group
You can assign an IP address to the routed port or to the SVI,
but it is not required.
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 routes 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 gigabitethernet3/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 an SVI for VLAN 2 and assigns it to the bridge group:
Switch(config)# bridge 10 protocol vlan-bridge
Switch(config)# vlan 2
Switch(config-vlan)# exit
Switch(config)# interface vlan2
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
46-5
Chapter 46
Configuring Fallback Bridging
Configuring Fallback Bridging
Switch(config-if)# bridge-group 10
Switch(config-if)# exit
Adjusting Spanning-Tree Parameters
You might need to adjust certain spanning-tree parameters if the default values are not suitable. You
configure parameters affecting the entire spanning tree by using variations of the bridge global
configuration command. You configure interface-specific parameters by using variations of the
bridge-group interface configuration command.
You can adjust spanning-tree parameters by performing any of the tasks in these sections:
Note
Changing the VLAN-Bridge Spanning-Tree Priority, page 46-6 (optional)
Changing the Interface Priority, page 46-7 (optional)
Assigning a Path Cost, page 46-7 (optional)
Adjusting BPDU Intervals, page 46-8 (optional)
Disabling the Spanning Tree on an Interface, page 46-10 (optional)
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.
Changing the VLAN-Bridge Spanning-Tree Priority
You can globally configure the VLAN-bridge spanning-tree priority of a switch when it ties with another
switch for the position as the root switch. You also can configure the likelihood that the switch will be
selected as the root switch.
Beginning in privileged EXEC mode, follow these steps to change the switch priority. This procedure is
optional.
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.
Step 4
show running-config
Verify your entry.
Step 5
copy running-config startup-config
(Optional) Save your entry in the configuration file.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
46-6
OL-12189-01
Chapter 46
Configuring Fallback Bridging
Configuring Fallback Bridging
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
Changing the Interface Priority
You can change the priority for a port. When two switches tie for position as the root switch, you
configure a port priority to break the tie. The switch with the lowest interface value is elected.
Beginning in privileged EXEC mode, follow these steps to change the interface priority. This procedure
is optional.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
interface interface-id
Specify the interface to set the priority, and enter interface
configuration mode.
Step 3
bridge-group bridge-group priority
number
Change the priority of a port.
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 gigabitethernet2/0/1
Switch(config-if)# bridge-group 10 priority 20
Assigning a Path Cost
Each port has a path cost associated with it. By convention, the path cost is 1000/data rate of the attached
LAN, in Mb/s.
Beginning in privileged EXEC mode, follow these steps to assign a path cost. This procedure is optional.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
46-7
Chapter 46
Configuring Fallback Bridging
Configuring Fallback Bridging
Step 3
Command
Purpose
bridge-group bridge-group path-cost
cost
Assign the path cost of a port.
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 Mb/s, the default path cost is 100.
For 100 Mb/s, the default path cost is 19.
For 1000 Mb/s, 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 gigabitethernet2/0/1
Switch(config-if)# bridge-group 10 path-cost 20
Adjusting BPDU Intervals
You can adjust BPDU intervals as described in these sections:
Note
Adjusting the Interval between Hello BPDUs, page 46-8 (optional)
Changing the Forward-Delay Interval, page 46-9 (optional)
Changing the Maximum-Idle Interval, page 46-9 (optional)
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.
Adjusting the Interval between Hello BPDUs
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.
Step 3
end
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.
Return to privileged EXEC mode.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
46-8
OL-12189-01
Chapter 46
Configuring Fallback Bridging
Configuring Fallback Bridging
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 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
Changing the Forward-Delay Interval
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
seconds
Specify the forward-delay interval.
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
Changing the Maximum-Idle Interval
If a switch does not receive BPDUs from the root switch within a specified interval, it recomputes the
spanning-tree topology.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
46-9
Chapter 46
Configuring Fallback Bridging
Configuring Fallback Bridging
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
Disabling the Spanning Tree on an Interface
When a loop-free path exists between any two switched subnetworks, you can prevent BPDUs generated
in one switching subnetwork from impacting devices in the other switching subnetwork, yet still permit
switching throughout the network as a whole. For example, when switched LAN subnetworks are
separated by a WAN, BPDUs can be prevented from traveling across the WAN link.
Beginning in privileged EXEC mode, follow these steps to disable spanning tree on a port. This
procedure is optional.
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
spanning-disabled
Disable spanning tree on the port.
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 gigabitethernet2/0/1
Switch(config-if)# bridge group 10 spanning-disabled
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
46-10
OL-12189-01
Chapter 46
Configuring Fallback Bridging
Monitoring and Maintaining Fallback Bridging
Monitoring and Maintaining Fallback Bridging
To monitor and maintain the network, use one or more of the privileged EXEC commands in Table 46-2:
Table 46-2
Commands for Monitoring and Maintaining Fallback Bridging
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]
To display the bridge-group MAC address table on a stack member, start a session from the stack master
to the stack member by using the session stack-member-number global configuration command. Enter
the show bridge [bridge-group] [interface-id | mac-address | verbose] privileged EXEC command at the
stack member prompt.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
46-11
Chapter 46
Configuring Fallback Bridging
Monitoring and Maintaining Fallback Bridging
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
46-12
OL-12189-01
CH A P T E R
47
Troubleshooting
This chapter describes how to identify and resolve software problems related to the Cisco IOS software
on the switch. Depending on the nature of the problem, you can use the command-line interface (CLI),
the device manager, or Network Assistant to identify and solve problems.
Unless otherwise noted, the term switch refers to a standalone switch and to a switch stack.
Additional troubleshooting information, such as LED descriptions, 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.
This chapter consists of these sections:
Recovering from a Software Failure, page 47-2
Recovering from a Lost or Forgotten Password, page 47-3
Preventing Switch Stack Problems, page 47-8 (only the Catalyst Switch Module 3110)
Note
Recovery procedures require that you have physical access to the switch.
Preventing Autonegotiation Mismatches, page 47-9
Monitoring Temperature, page 47-9
Using Ping, page 47-10
Using Layer 2 Traceroute, page 47-11
Using IP Traceroute, page 47-13
Using TDR, page 47-15
Using Debug Commands, page 47-16
Using the show platform forward Command, page 47-17
Using the crashinfo Files, page 47-20
Using On-Board Failure Logging, page 47-21 (only the Catalyst Switch Module 3110)
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
47-1
Chapter 47
Troubleshooting
Recovering from a Software Failure
Recovering from a Software Failure
Switch software can be corrupted during an upgrade, by downloading the wrong file to the switch, and
by deleting the image file. In all of these cases, the switch does not pass the power-on self-test (POST),
and there is no connectivity.
This procedure uses the Xmodem Protocol to recover from a corrupt or wrong image file. There are many
software packages that support the Xmodem Protocol, and this procedure is largely dependent on the
emulation software that you are using.
You can also connect a terminal or PC to the switch to the Advanced Managment Module (AMM)
through an Ethernet connection. For details about using the internal Ethernet management port, see the
Using the Internal Ethernet Management Port section on page 10-19 and the hardware installation
guide.
This recovery procedure requires that you have physical access to the switch.
Step 1
From your PC, download the software image tar file (image_filename.tar) from ibm.com or 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 ibm.com or 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 can read 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.
switch% tar -tvf image_filename.tar
2.
Locate the bin file, 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
x cbs31x0-universal-mz.122-40.EX2/cbs31x0-universal-mz.122-40.EX2.bin, 3970586
bytes, 7756 tape blocks
3.
Verify that the bin file was extracted by using the ls -l image_filename.bin UNIX command.
switch% ls -l image_filename.bin
-rw-r--r-1 boba
3970586 Apr 21 12:00
cbs31x0-universal-mz.122-40.EX2/cbs31x0-universal-mz.122-40.EX2.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
On a stacking-capable switch, power off the switch by using one of these methods:
Power off the standalone switch or the entire switch stack by using the AMM GUI.
Remove the switch or stack members from the enclosure.
On a nonstacking-capable switch, power off the switch by using the AMM GUI or remove the switch
from the enclosure.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
47-2
OL-12189-01
Chapter 47
Troubleshooting
Recovering from a Lost or Forgotten Password
Step 6
Press the Mode button, and at the same time, power on the switch by using one of these methods:
If you powered off the switch by using the AMM GUI, use the GUI to power on the switch or the
stack.
If you powered off the switch by removing the switch or stack members from the enclosure, re-insert
the standalone switch or the stack members in the enclosure.
You can release the Mode button after the system LED stops blinking and is solid green. 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 7
Initialize the flash file system:
switch: flash_init
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 9
Load any helper files:
switch: load_helper
Step 10
Start the file transfer by using the Xmodem Protocol.
switch: copy xmodem: flash:image_filename.bin
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 up 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
or to the switch stack.
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.
Recovering from a Lost or Forgotten Password
The default configuration for the switch allows an end user with physical access to the switch to recover
from a lost password by interrupting the bootup process during power-on and by entering a new
password. These recovery procedures require that you have physical access to 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
47-3
Chapter 47
Troubleshooting
Recovering from a Lost or Forgotten Password
These sections describes how to recover a forgotten or lost switch password:
Procedure with Password Recovery Enabled, page 47-5
Procedure with Password Recovery Disabled, page 47-6
You enable or disable password recovery by using the service password-recovery global configuration
command. When you enter the service password-recovery or no service password-recovery command
on the stack master, it is propagated throughout the stack and applied to all switches in the stack.
Follow the steps in this procedure if you have forgotten or lost the switch password.
Step 1
Connect a terminal or a PC with terminal-emulation software to the switch console port. If you are
recovering the password for a switch stack, connect to the console port of the stack master.
Step 2
Set the line speed on the emulation software to 9600 baud.
Step 3
On a stacking-capable switch, power off the switch by using one of these methods:
Power off the standalone switch or the entire switch stack by using the AMM GUI.
Remove the switch or stack members from the enclosure.
On a nonstacking-capable switch, power off the switch by using the AMM GUI or remove the switch
from the enclosure.
Step 4
Power on the switch by using one of these methods:
If you powered off the standalone switch or switch stack, it should automatically power on. If this
does not occur, use the AMM GUI to power on the switch or the stack.
If you powered off the switch by using the AMM GUI, use the GUI to power on the switch or the
stack.
If you powered off the switch by removing the switch or stack members from the enclosure, re-insert
the standalone switch or the stack members in the enclosure.
Within 15 seconds, press the Mode button while the System LED is still blinking green. Continue
pressing the Mode button until the System LED turns briefly amber and then solid green; then release
the Mode button.
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
go to the Procedure with Password Recovery Enabled section on page 47-5, and follow the steps.
If you see a message that begins with this:
The password-recovery mechanism has been triggered, but is currently disabled.
go to the Procedure with Password Recovery Disabled section on page 47-6, and follow the steps.
Step 5
After recovering the password, reload the nonstacking-capable switch, the standalone switch, or the
stack master.
On a nonstacking-capable switch:
Switch> reload
Proceed with reload? [confirm] y
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
47-4
OL-12189-01
Chapter 47
Troubleshooting
Recovering from a Lost or Forgotten Password
On a stacking-capable switch:
Switch> reload
slot <stack-master-member-number>
Proceed with reload? [confirm] y
Step 6
For stacking-capable switches, power on the rest of the switch stack.
Procedure with Password Recovery Enabled
If the password-recovery mechanism is enabled, this message appears:
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 1
Initialize the flash file system:
switch: flash_init
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
Step 4
Display the contents of flash memory:
switch: dir flash:
The switch file system appears:
Directory of flash:
2 -rwx
5752
3 -rwx
24
4 -rwx
9995193
6 -rwx
1147
9 -rwx
1155
10 -rwx
1161
8 -rwx
8016
Mar
Mar
Mar
Mar
Mar
Mar
Mar
1
1
1
1
1
1
1
1993
1993
1993
1993
1993
1993
1993
00:06:02
00:06:02
00:04:31
00:40:29
23:55:57
23:56:21
00:00:51
+00:00
+00:00
+00:00
+00:00
+00:00
+00:00
+00:00
config.text
private-config.text
cbs31x0-universal-mz.122-40.EX2
FHH105002F6_IPBase.lic
FHH105002F6_IPServ.lic
FHH105002F6_AdvIPServ.lic
vlan.dat
16128000 bytes total (10003456 bytes free)
Step 5
Rename the configuration file to config.text.old.
This file contains the password definition.
switch: rename flash:config.text flash:config.text.old
Step 6
Boot up the system:
switch: boot
Step 7
At the switch prompt, enter privileged EXEC mode:
Switch> enable
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
47-5
Chapter 47
Troubleshooting
Recovering from a Lost or Forgotten Password
Step 8
Rename the configuration file to its original name:
Switch# rename flash:config.text.old flash:config.text
Note
Step 9
Before continuing to Step 9, power on any connected stack members and wait until they have
completely initialized. Failure to follow this step can result in a lost configuration depending on
how your switch is set up.
Copy the configuration file into memory:
Switch# copy flash:config.text system:running-config
Source filename [config.text]?
Destination filename [running-config]?
Press Return in response to the confirmation prompts.
The configuration file is now reloaded, and you can change the password.
Step 10
Enter global configuration mode:
Switch# configure terminal
Step 11
Change the password:
Switch (config)# enable secret password
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#
Step 13
Write the running configuration to the startup configuration file:
Switch# copy running-config startup-config
The new password is now in the startup configuration.
Note
Step 14
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.
Reload the switch or switch stack:
Switch# reload
Procedure with Password Recovery Disabled
If the password-recovery mechanism is disabled, this message appears:
The password-recovery mechanism has been triggered, but
is currently disabled. Access to the boot loader prompt
through the password-recovery mechanism is disallowed at
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
47-6
OL-12189-01
Chapter 47
Troubleshooting
Recovering from a Lost or Forgotten Password
this point. However, if you agree to let the system be
reset back to the default system configuration, access
to the boot loader prompt can still be allowed.
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 bootup 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........
Step 1
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.
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
Step 2
Load any helper files:
Switch: load_helper
Step 3
Display the contents of flash memory:
switch: dir flash:
The switch file system appears:
Directory of flash:
4 -rwx
9995193
Mar 1 1993 00:04:31 +00:00
57931776 bytes total (35725824 bytes free)
Step 4
cbs31x0-universal-mz.122-40.EX2
Boot up the system:
Switch: boot
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
Step 5
At the switch prompt, enter privileged EXEC mode:
Switch> enable
Step 6
Enter global configuration mode:
Switch# configure terminal
Step 7
Change the password:
Switch (config)# enable secret password
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#
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
47-7
Chapter 47
Troubleshooting
Preventing Switch Stack Problems
Note
Step 9
Before continuing to Step 9, power on any connected stack members and wait until they have
completely initialized.
Write the running configuration to the startup configuration file:
Switch# copy running-config startup-config
The new password is now in the startup configuration.
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.
Step 11
Reload the switch:
Switch# reload
Preventing Switch Stack Problems
Note
Make sure that the switches that you add to or remove from the switch stack are powered off. For
all powering considerations in switch stacks, see the Switch Installation chapter in the hardware
installation guide.
After adding or removing stack members, make sure that the switch stack is operating at full
bandwidth (32 Gb/s). Press the Mode button on a stack member until the MBR LED is on. The last
two port LEDs on the switch should be green. Depending on the switch model, the last two ports are
either 10/100/1000 ports or 10-Gigabit Ethernet port. The stack is not operating at full bandwidth if
On the Catalyst Switch Module 3110X, one or both of the two LEDs for the 10-Gigabit Ethernet
port are not green. The Stack mode LEDs are the 10-Gigabit Ethernet port LEDs.
On the Catalyst Switch Module 3110G, the LEDs for ports 17 and 18 are not green.
We recommend using only one CLI session when managing the switch stack. Be careful when using
multiple CLI sessions to the stack master. Commands that you enter in one session do not appear in
the other sessions. Therefore, you might not be able to identify the session from which you entered
a command.
Manually assigning stack member numbers according to the placement of the switches in the stack
can make it easier to remotely troubleshoot the switch stack. However, if you add, remove, or
rearrange switches later, you need to remember that the switches have manually assigned numbers.
Use the switch current-stack-member-number renumber new-stack-member-number global
configuration command to manually assign a stack member number. For more information about
stack member numbers, see the Stack Member Numbers section on page 5-8.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
47-8
OL-12189-01
Chapter 47
Troubleshooting
Preventing Autonegotiation Mismatches
If you replace a stack member with an identical model, the new switch functions with the exact same
configuration as the replaced switch. This is also assuming the new switch is using the same member
number as the replaced switch.
Removing powered-on stack members causes the switch stack to divide (partition) into two or more
switch stacks, each with the same configuration. If you want the switch stacks to remain separate, change
the IP address or addresses of the newly created switch stacks. To recover from a partitioned switch
stack:
1.
Power off the newly created switch stacks.
2.
Reconnect them to the original switch stack through their StackWise Plus ports.
3.
Power on the switches.
For the commands that you can use to monitor the switch stack and its members, see the Displaying
Switch Stack Information section on page 5-27.
Preventing Autonegotiation Mismatches
The IEEE 802.3ab autonegotiation protocol manages the switch settings for speed (10 Mb/s, 100 Mb/s,
and 1000 Mb/s) and duplex (half or full). There are situations when this protocol can incorrectly align
these settings, reducing performance. A mismatch occurs under these circumstances:
A manually set speed or duplex parameter is different from the manually set speed or duplex
parameter on the connected port.
A port is set to autonegotiate, and the connected port is set to full duplex with no autonegotiation.
To maximize switch performance and ensure a link, follow one of these guidelines when changing the
settings for duplex and speed:
Note
Let both ports autonegotiate both speed and duplex.
Manually set the speed and duplex parameters for the ports on both ends of the connection.
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.
Monitoring Temperature
The switch monitors the temperature conditions and uses the temperature information to control the fans.
Use the show env temperature status privileged EXEC command to display the temperature value,
state, and thresholds. The temperature value is the temperature in the switch (not the external
temperature).You can configure only the yellow threshold level (in Celsius) by using the system env
temperature threshold yellow value global configuration command to set the difference between the
yellow and red thresholds. You cannot configure the green or red thresholds. For more information, see
the command reference for this release.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
47-9
Chapter 47
Troubleshooting
Using Ping
Using Ping
These sections contain this information:
Understanding Ping, page 47-10
Executing Ping, page 47-10
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 responseThe normal response (hostname is alive) occurs in 1 to 10 seconds, depending
on network traffic.
Destination does not respondIf the host does not respond, a no-answer message is returned.
Unknown hostIf the host does not exist, an unknown host message is returned.
Destination unreachableIf the default gateway cannot reach the specified network, a
destination-unreachable message is returned.
Network or host unreachableIf 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 38,
Configuring IP Unicast Routing.
IP routing is disabled by default on all switches. If you need to enable or configure IP routing, see
Chapter 38, Configuring IP Unicast Routing.
Beginning in privileged EXEC mode, use this command to ping another device on the network from the
switch:
Note
Command
Purpose
ping ip host | address
Ping a remote host through IP or by supplying the hostname or
network address.
Though other protocol keywords are available with the ping command, they are not supported in this
release.
This example shows how to ping an IP host:
Switch# ping 172.20.52.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echoes to 172.20.52.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
47-10
OL-12189-01
Chapter 47
Troubleshooting
Using Layer 2 Traceroute
Switch#
Table 47-1 describes the possible ping character output.
Table 47-1
Ping Output Display Characters
Character
Description
Each exclamation point means receipt of a reply.
Each period means the network server timed out while waiting for a reply.
A destination unreachable error PDU was received.
A congestion experienced packet was received.
User interrupted test.
Unknown packet type.
&
Packet lifetime exceeded.
To end a ping session, enter the escape sequence (Ctrl-^ X by default). Simultaneously press and release
the Ctrl, Shift, and 6 keys and then press the X key.
Using Layer 2 Traceroute
These sections contain this information:
Understanding Layer 2 Traceroute, page 47-11
Usage Guidelines, page 47-12
Displaying the Physical Path, page 47-13
Understanding Layer 2 Traceroute
The Layer 2 traceroute feature allows the switch to identify the physical path that a packet takes from a
source device to a destination device. Layer 2 traceroute supports only unicast source and destination
MAC addresses. It finds the path by using the MAC address tables of the switches in the path. When the
switch detects a device in the path that does not support Layer 2 traceroute, the switch continues to send
Layer 2 trace queries and lets them time out.
The switch can only identify the path from the source device to the destination device. It cannot identify
the path that a packet takes from source host to the source device or from the destination device to the
destination host.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
47-11
Chapter 47
Troubleshooting
Using Layer 2 Traceroute
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.
For a list of switches that support Layer 2 traceroute, see the Usage Guidelines section on
page 47-12. If any devices in the physical path are transparent to CDP, the switch cannot identify
the path through these devices. For more information about enabling CDP, see Chapter 26,
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
47-12
OL-12189-01
Chapter 47
Troubleshooting
Using IP Traceroute
Displaying the Physical Path
You can display physical path that a packet takes from a source device to a destination device by using
one of these privileged EXEC commands:
tracetroute mac [interface interface-id] {source-mac-address} [interface interface-id]
{destination-mac-address} [vlan vlan-id] [detail]
tracetroute mac ip {source-ip-address | source-hostname}{destination-ip-address |
destination-hostname} [detail]
For more information, see the command reference for this release.
Using IP Traceroute
These sections contain this information:
Understanding IP Traceroute, page 47-13
Executing IP Traceroute, page 47-14
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 an Internet Control Message Protocol (ICMP)
time-to-live-exceeded message to the sender. Traceroute finds 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 learn 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 that this message was sent by the
destination port.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
47-13
Chapter 47
Troubleshooting
Using IP Traceroute
Executing IP Traceroute
Beginning in privileged EXEC mode, follow this step to trace the path that packets take through the
network:
Note
Command
Purpose
traceroute ip host
Trace the path that packets take through the network.
Though other protocol keywords are available with the traceroute privileged EXEC command, they are
not supported in this release.
This example shows how to perform a traceroute to an IP host:
Switch# traceroute ip 171.9.15.10
Type escape sequence to abort.
Tracing the route to 171.69.115.10
1 172.2.52.1 0 msec 0 msec 4 msec
2 172.2.1.203 12 msec 8 msec 0 msec
3 171.9.16.6 4 msec 0 msec 0 msec
4 171.9.4.5 0 msec 4 msec 0 msec
5 171.9.121.34 0 msec 4 msec 4 msec
6 171.9.15.9 120 msec 132 msec 128 msec
7 171.9.15.10 132 msec 128 msec 128 msec
Switch#
The display shows the hop count, the IP address of the router, and the round-trip time in milliseconds
for each of the three probes that are sent.
Table 47-2
Traceroute Output Display Characters
Character
Description
The probe timed out.
Unknown packet type.
Administratively unreachable. Usually, this output means that an access list is
blocking traffic.
Host unreachable.
Network unreachable.
Protocol unreachable.
Source quench.
Port unreachable.
To end a trace in progress, enter the escape sequence (Ctrl-^ X by default). Simultaneously press and
release the Ctrl, Shift, and 6 keys and then press the X key.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
47-14
OL-12189-01
Chapter 47
Troubleshooting
Using TDR
Using TDR
These sections contain this information:
Understanding TDR, page 47-15
Running TDR and Displaying the Results, page 47-15
Understanding TDR
You can use the Time Domain Reflector (TDR) feature to diagnose and resolve cabling problems. When
running TDR, a local device sends a signal through a cable and compares the reflected signal to the initial
signal.
TDR is supported only on 10/100/1000 copper Ethernet ports. It is not supported on 10-Gigabit Ethernet
ports.
TDR can detect these cabling problems:
Open, broken, or cut twisted-pair wiresThe wires are not connected to the wires from the remote
device.
Shorted twisted-pair wiresThe wires are touching each other or the wires from the remote device.
For example, a shorted twisted pair can occur if one wire of the twisted pair is soldered to the other
wire.
If one of the twisted-pair wires is open, TDR can find the length at which the wire is open.
Use TDR to diagnose and resolve cabling problems in these situations:
Replacing a switch
Setting up a wiring closet
Troubleshooting a connection between two devices when a link cannot be established or when it is
not operating properly
When you run TDR, the switch reports accurate information if
The cable for the Gigabit link is a solid-core cable.
The open-ended cable is not terminated.
When you run TDR, the switch does not report accurate information if
The cable for the Gigabit link is a twisted-pair cable or is in series with a solid-core cable.
The link is a 10-Megabit or a 100-Megabit link.
The cable is a stranded cable.
The link partner is a Cisco IP Phone.
The link partner is not IEEE 802.3 compliant.
Running TDR and Displaying the Results
When you run TDR on an interface, you can run it on the stack master or a stack member.
To run TDR, enter the test cable-diagnostics tdr interface interface-id privileged EXEC command:
To display the results, enter the show cable-diagnostics tdr interface interface-id privileged EXEC
command. For a description of the fields in the display, see the command reference for this release.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
47-15
Chapter 47
Troubleshooting
Using Debug Commands
Using Debug Commands
These sections explains how you use debug commands to diagnose and resolve internetworking
problems:
Caution
Note
Enabling Debugging on a Specific Feature, page 47-16
Enabling All-System Diagnostics, page 47-17
Redirecting Debug and Error Message Output, page 47-17
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.
For complete syntax and usage information for specific debug commands, see the command reference
for this release.
Enabling Debugging on a Specific Feature
In a switch stack, when you enable debugging, it is enabled only on the stack master. To enable
debugging on a stack member, you must start a session from the stack master by using the session
switch-number privileged EXEC command. Then, enter the debug command at the command-line
prompt of the stack member.
All debug commands are entered in privileged EXEC mode, and most debug commands take no
arguments. For example, beginning in privileged EXEC mode, enter this command to enable the
debugging for Switched Port Analyzer (SPAN):
Switch# debug span-session
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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
47-16
OL-12189-01
Chapter 47
Troubleshooting
Using the show platform forward Command
Enabling All-System Diagnostics
Beginning in privileged EXEC mode, enter this command to enable all-system diagnostics:
Switch# debug all
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.
Redirecting Debug and Error Message Output
By default, the network server sends the output from debug commands and system error messages to the
console. If you use this default, you can use a virtual terminal connection to monitor debug output
instead of connecting to the console port or the Ethernet management port.
Possible destinations include the console, virtual terminals, internal buffer, and UNIX hosts running a
syslog server. The syslog format is compatible with 4.3 Berkeley Standard Distribution (BSD) UNIX
and its derivatives.
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.
When stack members generate a system error message, the stack master displays the error message to
all stack members. The syslog resides on the stack master.
Note
Make sure to save the syslog to flash memory so that the syslog is not lost if the stack master fails.
For more information about system message logging, see Chapter 31, Configuring System Message
Logging.
Using the show platform forward Command
The output from the show platform forward privileged EXEC command provides some useful
information about the forwarding results if a packet entering an interface is sent through the system.
Depending upon the parameters entered about the packet, the output provides lookup table results and
port maps used to calculate forwarding destinations, bitmaps, and egress information.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
47-17
Chapter 47
Troubleshooting
Using the show platform forward Command
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 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/0/1 vlan 5 1.1.1 2.2.2 ip 13.1.1.1 13.2.2.2
udp 10 20
Global Port Number:24, Asic Number:5
Src Real Vlan Id:5, Mapped Vlan Id:5
Ingress:
Lookup
Key-Used
Index-Hit A-Data
InptACL 40_0D020202_0D010101-00_40000014_000A0000
01FFA
03000000
L2Local 80_00050002_00020002-00_00000000_00000000
00C71
0000002B
Station Descriptor:02340000, DestIndex:0239, RewriteIndex:F005
==========================================
Egress:Asic 2, switch 1
Output Packets:
-----------------------------------------Packet 1
Lookup
Key-Used
OutptACL 50_0D020202_0D010101-00_40000014_000A0000
Port
Gi1/0/1
Vlan
SrcMac
0005 0001.0001.0001
DstMac
Cos
0002.0002.0002
-----------------------------------------Packet 2
Lookup
Key-Used
OutptACL 50_0D020202_0D010101-00_40000014_000A0000
Port
Gi1/0/2
Vlan
SrcMac
0005 0001.0001.0001
DstMac
Cos
0002.0002.0002
Index-Hit A-Data
01FFE
03000000
Dscpv
Index-Hit A-Data
01FFE
03000000
Dscpv
-----------------------------------------<output truncated>
-----------------------------------------Packet 10
Lookup
Key-Used
Index-Hit A-Data
OutptACL 50_0D020202_0D010101-00_40000014_000A0000
01FFE
03000000
Packet dropped due to failed DEJA_VU Check on Gi1/0/2
This is an example of the output when the packet coming in on 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/0/1 vlan 5 1.1.1 0009.43a8.0145 ip 13.1.1.1
13.2.2.2 udp 10 20
Global Port Number:24, Asic Number:5
Src Real Vlan Id:5, Mapped Vlan Id:5
Ingress:
Lookup
Key-Used
Index-Hit
A-Data
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
47-18
OL-12189-01
Chapter 47
Troubleshooting
Using the show platform forward Command
InptACL 40_0D020202_0D010101-00_40000014_000A0000
01FFA
03000000
L2Local 80_00050009_43A80145-00_00000000_00000000
00086
02010197
Station Descriptor:F0050003, DestIndex:F005, RewriteIndex:0003
==========================================
Egress:Asic 3, switch 1
Output Packets:
-----------------------------------------Packet 1
Lookup
Key-Used
OutptACL 50_0D020202_0D010101-00_40000014_000A0000
Port
Gi1/0/2
Vlan
SrcMac
0005 0001.0001.0001
DstMac
Cos
0009.43A8.0145
Index-Hit A-Data
01FFE
03000000
Dscpv
This is an example of the output when the packet coming in on 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. Because there
is no default route set, the packet should be dropped.
Switch# show platform forward gigabitethernet1/0/1 vlan 5 1.1.1 03.e319.ee44 ip 13.1.1.1
13.2.2.2 udp 10 20
Global Port Number:24, Asic Number:5
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 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/0/1 vlan 5 1.1.1 03.e319.ee44 ip 110.1.5.5
16.1.10.5
Global Port Number:24, Asic Number:5
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 1
Output Packets:
-----------------------------------------Packet 1
Lookup
Key-Used
OutptACL 50_10010A05_0A010505-00_40000014_000A0000
Port
Gi1/0/2
Vlan
SrcMac
0007 XXXX.XXXX.0246
DstMac
Cos
0009.43A8.0147
Index-Hit A-Data
01FFE
03000000
Dscpv
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
47-19
Chapter 47
Troubleshooting
Using the crashinfo Files
Using the crashinfo Files
The crashinfo files save information that helps Cisco technical support representatives to debug
problems that caused the Cisco IOS image to fail (crash). The switch writes the crash information to the
console at the time of the failure. The switch creates two types of crashinfo files:
Basic crashinfo fileThe switch automatically creates this file the next time you boot up the Cisco
IOS image after the failure.
Extended crashinfo fileThe switch automatically creates this file when the system is failing.
Basic crashinfo Files
The information in the basic file includes the Cisco IOS image name and version that failed, a list of the
processor registers, and a stack trace. You can provide this information to the Cisco technical support
representative by using the show tech-support privileged EXEC command.
Basic crashinfo files are kept in this directory on the flash file system:
flash:/crashinfo/.
The filenames are crashinfo_n where n is a sequence number.
Each new crashinfo file that is created uses a sequence number that is larger than any previously existing
sequence number, so the file with the largest sequence number describes the most recent failure. Version
numbers are used instead of a timestamp because the switches do not include a real-time clock. You
cannot change the name of the file that the system will use when it creates the file. However, after the
file is created, you can use the rename privileged EXEC command to rename it, but the contents of the
renamed file will not be displayed by the show stacks or the show tech-support privileged EXEC
command. You can delete crashinfo files by using the delete privileged EXEC command.
You can display the most recent basic crashinfo file (that is, the file with the highest sequence number
at the end of its filename) by entering the show stacks or the show tech-support privileged EXEC
command. You also can access the file by using any command that can copy or display files, such as the
more or the copy privileged EXEC command.
Extended crashinfo Files
The switch creates the extended crashinfo file when the system is failing. The information in the
extended file includes additional information that can help determine the cause of the switch failure. You
provide this information to the Cisco technical support representative by manually accessing the file and
using the more or the copy privileged EXEC command.
Extended crashinfo files are kept in this directory on the flash file system:
flash:/crashinfo_ext/.
The filenames are crashinfo_ext_n where n is a sequence number.
You can configure the switch to not create the extended creashinfo file by using the no exception
crashinfo global configuration command.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
47-20
OL-12189-01
Chapter 47
Troubleshooting
Using On-Board Failure Logging
Using On-Board Failure Logging
You can use the on-board-failure logging (OBFL) feature to collect information about the switch. The
information includes uptime, temperature, and voltage information and helps Cisco technical support
representatives to troubleshoot switch problems. We recommend that you keep OBFL enabled and do
not erase the data stored in the flash memory.
This section has this information:
Understanding OBFL, page 47-21
Configuring OBFL, page 47-21
Displaying OBFL Information, page 47-22
Understanding OBFL
By default, OBFL is enabled. It collects information about the switch. The switch stores this information
in the flash memory:
CLI commandsRecord of the OBFL CLI commands that are entered on a standalone switch or a
switch stack member
Environment dataUnique device identifier (UDI) information for a standalone switch or a stack
member and for all the connected FRU devices: the product identification (PID), the version
identification (VID), and the serial number
MessageRecord of the hardware-related system messages generated by a standalone switch or a
stack member
TemperatureTemperature of a standalone switch or a stack member
Uptime dataTime when a standalone switch or a stack member starts, the reason the switch
restarts, and the length of time the switch has been running since it last restarted
VoltageSystem voltages of a standalone switch or a stack member
You should manually set the system clock or configure it by using Network Time Protocol (NTP).
When the switch is running, you can retrieve the OBFL data by using the show logging onboard
privileged EXEC commands. If the switch fails, contact your Cisco technical support representative to
find out how to retrieve the data.
Configuring OBFL
To enable OBFL, use the hw-module module [switch-number] logging onboard [message level level]
global configuration command. On stacking-capable switches, the range for switch-number is from 1
to 9. On nonstacking-capable switches, the switch number is always 1. Use the message level level
parameter to specify the severity of the hardware-related messages that the switch generates and stores
in the flash memory.
To copy the OBFL data to the local network or a specific file system, use the copy logging onboard
module stack-member destination privileged EXEC command.
Caution
We recommend that you do not disable OBFL and that you do not remove the data stored in the flash
memory.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
47-21
Chapter 47
Troubleshooting
Using On-Board Failure Logging
To disable OBFL, use the no hw-module module [switch-number] logging onboard [message level]
global configuration command.
To clear all the OBFL data in the flash memory except for the uptime and CLI command information,
use the clear logging onboard privileged EXEC command.
In a switch stack, you can enable OBFL on a standalone switch or on all stack members by using the
hw-module module logging onboard [message level level] global configuration command.
For more information about the commands in this section, see the command reference for this release.
Displaying OBFL Information
To display the OBFL information, use one or more of the privileged EXEC commands in Table 47-3:
Table 47-3
Commands for Displaying OBFL Information
Command
Purpose
show logging onboard [module
[switch-number]] clilog
Displays the OBFL CLI commands that were entered on a standalone
switch or the specified stack members.
show logging onboard [module
[switch-number]] environment
Display the UDI information for a standalone switch or the specified
stack members and for all the connected FRU devices: the PID, the VID,
and the serial number.
show logging onboard [module
[switch-number]] message
Display the hardware-related messages generated by a standalone switch
or the specified stack members.
show logging onboard [module
[switch-number]] poe
Display the power consumption of PoE ports on a standalone switch or
the specified stack members.
show logging onboard [module
[switch-number]] temperature
Display the temperature of a standalone switch or the specified switch
stack members.
show logging onboard [module
[switch-number]] uptime
Display the time when a standalone switch or the specified stack members
start, the reason the standalone switch or specified stack members restart,
and the length of time that the standalone switch or specified stack
members have been running since they last restarted.
show logging onboard [module
[switch-number]] voltage
Display the system voltages of a standalone switch or the specified stack
members.
For more information about using the commands in Table 47-3 and for examples of OBFL data, see the
command reference for this release.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
47-22
OL-12189-01
CH A P T E R
48
Configuring Online Diagnostics
This chapter describes how to configure the online diagnostics on the switch.
Note
For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release.
This chapter consists of these sections:
Understanding Online Diagnostics, page 48-1
Configuring Online Diagnostics, page 48-2
Running Online Diagnostic Tests, page 48-5
Understanding Online Diagnostics
With online diagnostics, you can test and verify the hardware functionality of the switch while the switch
is connected to a live network.
The online diagnostics contain packet switching tests that check different hardware components and
verify the data path and the control signals.
The online diagnostics detect problems in these areas:
Hardware components
Interfaces (Ethernet ports and so forth)
Solder joints
Online diagnostics are categorized as on-demand, scheduled, or health-monitoring diagnostics.
On-demand diagnostics run from the CLI; scheduled diagnostics run at user-designated intervals or at
specified times when the switch is connected to a live network; and health-monitoring runs in the
background.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
48-1
Chapter 48
Configuring Online Diagnostics
Configuring Online Diagnostics
Configuring Online Diagnostics
You must configure the failure threshold and the interval between tests before enabling diagnostic
monitoring.
This section has this information:
Scheduling Online Diagnostics, page 48-2
Configuring Health-Monitoring Diagnostics, page 48-3
Scheduling Online Diagnostics
You can schedule online diagnostics to run at a designated time of day or on a daily, weekly, or monthly
basis for a switch. Use the no form of this command to remove the scheduling.
Use this global configuration command to schedule online diagnostics:
Command
Purpose
diagnostic schedule switch
number test {name | test-id |
test-id-range | all | basic |
non-disruptive} {daily hh:mm |
on mm dd yyyy hh:mm | weekly
day-of-week hh:mm}
Schedule on-demand diagnostic tests for a specific day and time.
The switch number keyword is supported only on stacking-capable switches. The range
is from 1 to 9.
When specifying the tests to be scheduled, use these options:
nameName of the test that appears in the show diagnostic content command
output.
test-idID number of the test that appears in the show diagnostic content command
output.
test-id-rangeID numbers of the tests that appear in the show diagnostic content
command output.
allAll of the diagnostic tests.
basicBasic on-demand diagnostic tests.
non-disruptiveNondisruptive health-monitoring tests.
You can schedule the tests as follows:
DailyUse the daily hh:mm parameter.
Specific day and timeUse the on mm dd yyyy hh:mm parameter.
WeeklyUse the weekly day-of-week hh:mm parameter.
For detailed information about this command, see the command reference for this release.
Use the no diagnostic schedule switch number test {name | test-id | test-id-range | all | basic |
non-disruptive} {daily hh:mm | on mm dd yyyy hh:mm | weekly day-of-week hh:mm} global
configuration command to remove the scheduled tests.
This example shows how to schedule diagnostic testing for a specific day and time on a standalone switch:
Switch(config)# diagnostic schedule test TestPortAsicCam on december 3 2006 22:25
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
48-2
OL-12189-01
Chapter 48
Configuring Online Diagnostics
Configuring Online Diagnostics
This example shows how to schedule diagnostic testing to occur weekly at a specific time on member
switch 6 when this command is entered on a stack master:
Switch(config)# diagnostic schedule switch 6 test 1-4,7 weekly saturday 10:30
For more examples, see the Examples section of the diagnostic schedule command in the command
reference for this release.
Configuring Health-Monitoring Diagnostics
You can configure health-monitoring diagnostic testing on a switch while it is connected to a live
network. You can configure the execution interval for each health-monitoring test, enable the switch to
generate a syslog message because of a test failure, and enable a specific test.
By default, health monitoring is disabled, but the switch generates a syslog message when a test fails.
Beginning in privileged EXEC mode, follow these steps to configure and enable the health-monitoring
diagnostic tests:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
diagnostic monitor interval switch
number test {name | test-id |
test-id-range | all} hh:mm:ss
milliseconds day
Configure the health-monitoring interval of the specified tests.
The switch number keyword is supported only on stacking-capable
switches. The range is from 1 to 9.
When specifying the tests, use one of these parameters:
nameName of the test that appears in the show diagnostic content
command output.
test-idID number of the test that appears in the show diagnostic
content command output.
test-id-rangeID numbers of the tests that appear in the show
diagnostic content command output.
allAll of the diagnostic tests.
When specifying the interval, set these parameters:
Step 3
diagnostic monitor syslog
hh:mm:ssMonitoring interval in hours, minutes, and seconds. The
range for hh is 0 to 24, and the range for mm and ss is 0 to 60.
millisecondsMonitoring interval in milliseconds (ms). The range is
from 0 to 999.
dayMonitoring interval in the number of days. The range is from 0
to 20.
(Optional) Configure the switch to generate a syslog message when a
health-monitoring test fails.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
48-3
Chapter 48
Configuring Online Diagnostics
Configuring Online Diagnostics
Step 4
Command
Purpose
diagnostic monitor threshold switch
number test {name | test-id |
test-id-range | all} failure count count
(Optional) Set the failure threshold for the health-monitoring tests.
The switch number keyword is supported only on stacking-capable
switches. The range is from 1 to 9.
When specifying the tests, use one of these parameters:
nameName of the test that appears in the show diagnostic content
command output.
test-idID number of the test that appears in the show diagnostic
content command output.
test-id-rangeID numbers of the tests that appear in the show
diagnostic content command output.
allAll of the diagnostic tests.
The range for the failure threshold count is 0 to 99.
Step 5
diagnostic monitor switch number test Enable the specified health-monitoring tests.
{name | test-id | test-id-range | all}
The switch number keyword is supported only on stacking-capable
switches. The range is from 1 to 9.
When specifying the tests, use one of these parameters:
nameName of the test that appears in the show diagnostic content
command output.
test-idID number of the test that appears in the show diagnostic
content command output.
test-id-rangeID numbers of the tests that appear in the show
diagnostic content command output.
allAll of the diagnostic tests.
Step 6
end
Step 7
show diagnostic {content | post | result Display the online diagnostic test results and the supported test suites. See
| schedule | status | switch}
the Displaying Online Diagnostic Tests and Test Results section on
page 48-6 for more information.
Step 8
show running-config
Verify your entries.
Step 9
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Return to privileged EXEC mode.
To disable diagnostic testing and return to the default settings, use these commands:
Note
The switch number option is supported only on stacking-capable switches.
To disable online diagnostic testing, use the no diagnostic monitor switch number test {name |
test-id | test-id-range | all} global configuration command.
To return to the default health-monitoring interval, use the no diagnostic monitor interval switch
number test {name | test-id | test-id-range | all} global configuration command.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
48-4
OL-12189-01
Chapter 48
Configuring Online Diagnostics
Running Online Diagnostic Tests
To configure the switch to not generate a syslog message when the health-monitoring test fails, use
the no diagnostic monitor syslog global configuration command.
To return to the default failure threshold, use the no diagnostic monitor threshold switch number
test {name | test-id | test-id-range | all} failure count count global configuration command.
This example shows how to configure a health-monitoring test:
Switch(config)# diagnostic monitor threshold switch 3 test 1 failure count 50
Switch(config)# diagnostic monitor interval switch 3 test TestPortAsicRingLoopback
Running Online Diagnostic Tests
After you configure online diagnostics, you can manually start diagnostic tests or display the test results.
You can also see which tests are configured for the switch or switch stack and the diagnostic tests that
have already run.
These sections describe how to run online diagnostic tests:
Starting Online Diagnostic Tests, page 48-5
Displaying Online Diagnostic Tests and Test Results, page 48-6
Starting Online Diagnostic Tests
After you configure diagnostic tests to run on the switch, use the diagnostic start privileged EXEC
command to begin diagnostic testing.
Use this privileged EXEC command to manually start online diagnostic testing:
Command
Purpose
diagnostic start switch number Start the diagnostic tests.
test {name | test-id | test-id-range The switch number keyword is supported only on stacking-capable switches. The range
| all | basic | non-disruptive}
is from 1 to 9.
You can specify the tests by using one of these options:
nameEnter the name of the test. Use the show diagnostic content privileged EXEC
command to display the test ID list.
test-idEnter the ID number of the test. Use the show diagnostic content privileged
EXEC command to display the test ID list.
test-id-rangeEnter the range of test IDs by using integers separated by a comma
and a hyphen. For more information, see the diagnostic start command in the
command reference for this release.
allUse this keyword when you want to run all of the tests.
basicUse this keyword when you want to run the basic test suite.
non-disruptiveUse this keyword when you want to run the non-disruptive test
suite.
After starting the tests, you cannot stop the testing process.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
48-5
Chapter 48
Configuring Online Diagnostics
Running Online Diagnostic Tests
This example shows how to start a diagnostic test by using the test name:
Switch# diagnostic start switch 2 test TestInlinePwrCtlr
This example shows how to start all of the basic diagnostic tests:
Switch# diagnostic start switch 1 test all
Displaying Online Diagnostic Tests and Test Results
You can display the online diagnostic tests that are configured for the switch or switch stack and check
the test results by using the privileged EXEC show commands in Table 48-1:
Table 48-1
Commands for Diagnostic Test Configuration and Results
Command
Purpose
show diagnostic content switch [number | all]
Display the online diagnostics configured for a switch.
show diagnostic status
Display the currently running diagnostic tests.
show diagnostic result switch [number | all] [detail |
test {name | test-id | test-id-range | all} [detail]]
Display the online diagnostics test results.
show diagnostic switch [number | all] [detail]
Display the online diagnostics test results.
show diagnostic schedule switch [number | all]
Display the online diagnostics test schedule.
show diagnostic post
Display the POST results. (The output is the same as the show post
command output.)
For examples of the show diagnostic command output, see the Examples section of the show
diagnostic command in the command reference for this release.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
48-6
OL-12189-01
A P P E N D I X
Supported MIBs
This appendix lists the supported management information base (MIBs) for this release on theswitch. It
contains these sections:
MIB List, page A-1
Using FTP to Access the MIB Files, page A-4
BRIDGE-MIB
MIB List
Note
The BRIDGE-MIB supports the context of a single VLAN. By default, SNMP messages
using the configured community string always provide information for VLAN 1. To obtain
the BRIDGE-MIB information for other VLANs, for example VLAN x, use this community
string in the SNMP message: configured community string @x.
CISCO-CABLE-DIAG-MIB
CISCO-CDP-MIB
CISCO-CONFIG-COPY-MIB
CISCO-CONFIG-MAN-MIB
CISCO-DHCP-SNOOPING-MIB
CISCO-ENTITY-FRU-CONTROL-MIB
CISCO-ENTITY-VENDORTYPE-OID-MIB
CISCO-ENVMON-MIB
CISCO-ERR-DISABLE-MIB
CISCO-FLASH-MIB (Flash memory on all switches is modeled as removable flash memory.)
CISCO-FTP-CLIENT-MIB
CISCO-HSRP-MIB
CISCO-HSRP-EXT-MIB (partial support)
CISCO-IETF-IP-MIB (only the Catalyst Switch Module 3110)
CISCO-IETF-IP-FORWARDING-MIB (only the Catalyst Switch Module 3110)
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
A-1
Appendix A
Supported MIBs
MIB List
CISCO-IETF-ISIS-MIB (Only with the IP services and advanced IP services feature sets)
CISCO-IF-EXTENSIONS-MIB
CISCO-IGMP-FILTER-MIB
CISCO-IMAGE-MIB (Only stack master feature set details are shown.)
CISCO IP-STAT-MIB
CISCO-L2L3-INTERFACE-CONFIG-MIB
CISCO-LAG-MIB
CISCO-MAC-NOTIFICATION-MIB
CISCO-MEMORY-POOL-MIB (Only stack master feature set details are shown.)
CISCO-PAE-MIB
CISCO-PAGP-MIB
CISCO-PING-MIB
CISCO-PORT-QOS-MIB (the cportQosStats Table returns the values from the octets and packet
counters, depending on switch configuration)
CISCO-PORT-STORM-CONTROL-MIB
CISCO-PRIVATE-VLAN-MIB
CISCO-POWER-ETHERNET-EXT-MIB
CISCO-PROCESS-MIB (Only stack master details are shown.)
CISCO-PRODUCTS-MIB
CISCO-RTTMON-MIB
CISCO-SLB-MIB (Only with the advanced IP services feature sets)
CISCO-SMI-MIB
CISCO-STACK-MIB (Partial support on stacking-capable switches: for some objects, only stack
master information is supported. ENTITY MIB is a better alternative.)
CISCO-STACKMAKER-MIB (stacking-capable switches only)
CISCO-STACKWISE PLUS MIB (stacking-capable switches only)
CISCO-STP-EXTENSIONS-MIB
CISCO-SYSLOG-MIB
CISCO-TC-MIB
CISCO-TCP-MIB
CISCO-UDLDP-MIB
CISCO-VLAN-IFTABLE-RELATIONSHIP-MIB
CISCO-VLAN-MEMBERSHIP-MIB
CISCO-VTP-MIB
ENTITY-MIB (The redundant power system [RPS] is represented as an entry in the entPhysical
table of this MIB.)
ETHERLIKE-MIB
IEEE8021-PAE-MIB
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
A-2
OL-12189-01
Appendix A
Supported MIBs
MIB List
Note
IEEE8023-LAG-MIB
IF-MIB (In and out counters for VLANs are not supported.)
IGMP-MIB
INET-ADDRESS-MIB
IPMROUTE-MIB
OLD-CISCO-CHASSIS-MIB (Partial support on stacking-capable switches; some objects reflect
only the stack master.)
OLD-CISCO-CPU-MIB
OLD-CISCO-FLASH-MIB (Supports only the stack master in a switch stack. Use
CISCO-FLASH_MIB.)
OLD-CISCO-INTERFACES-MIB
OLD-CISCO-IP-MIB
OLD-CISCO-SYS-MIB
OLD-CISCO-TCP-MIB
OLD-CISCO-TS-MIB
PIM-MIB
RFC1213-MIB (Functionality is as per the agent capabilities specified in the
CISCO-RFC1213-CAPABILITY.my.)
RFC1253-MIB (OSPF-MIB)
RMON-MIB
RMON2-MIB
SNMP-FRAMEWORK-MIB
SNMP-MPD-MIB
SNMP-NOTIFICATION-MIB
SNMP-TARGET-MIB
SNMPv2-MIB
TCP-MIB
UDP-MIB
You can also use this URL for a list of supported MIBs for these switches
ftp://ftp.cisco.com/pub/mibs/supportlists/cat3750e/cat3750e-supportlist.html
You can access other information about MIBs and Cisco products on the Cisco web site:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
A-3
Appendix A
Supported MIBs
Using FTP to Access the MIB Files
Using FTP to Access the MIB Files
You can get each MIB file by using this procedure:
Step 1
Make sure that your FTP client is in passive mode.
Note
Some FTP clients do not support passive mode.
Step 2
Use FTP to access the server ftp.cisco.com.
Step 3
Log in with the username anonymous.
Step 4
Enter your e-mail username when prompted for the password.
Step 5
At the ftp> prompt, change directories to /pub/mibs/v1 and /pub/mibs/v2.
Step 6
Use the get MIB_filename command to obtain a copy of the MIB file.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
A-4
OL-12189-01
A P P E N D I X
Working with the Cisco IOS File System,
Configuration Files, and Software Images
This appendix describes how to manipulate the switch flash file system, how to copy configuration files,
and how to archive (upload and download) software images to a switch or to a switch stack.
Unless otherwise noted, the term switch refers to a standalone switch and to a switch stack.
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.
This appendix consists of these sections:
Note
Working with the Flash File System, page B-1
Working with Configuration Files, page B-9
Working with Software Images, page B-23
The Catalyst Switch Module 3110 and 3012 use the cryptographic and noncryptographic universal
software images. The Catalyst Switch Module 3110 supports multiple feature sets, but the Catalyst
Switch Module 3012 supports only the IP base feature set.
For information about using the software activation feature with the universal software image, see the
Cisco Software Activation for IBM on Cisco.com
Working with the Flash File System
The flash file system is a single flash device on which you can store files. It also provides several
commands to help you manage software image and configuration files. The default flash file system on
the switch is named flash:.
As viewed from the stack master, or any stack member, flash: refers to the local flash device, which is
attached to the same switch on which the file system is being viewed. In a switch stack, each of the flash
devices of the various stack members can be viewed from the stack master. The names of these flash file
systems include the corresponding switch member numbers. For example, flash3:, as viewed from the
stack master, refers to the same file system as does flash: on stack member 3. Use the show file systems
privileged EXEC command to list all file systems, including the flash file systems in the switch stack.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
B-1
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with the Flash File System
No more than one user at a time can manage the software images and configuration files for a switch
stack.
These sections contain this configuration information:
Displaying Available File Systems, page B-2
Setting the Default File System, page B-3
Displaying Information about Files on a File System, page B-3
Changing Directories and Displaying the Working Directory, page B-4
Creating and Removing Directories, page B-5
Copying Files, page B-5
Deleting Files, page B-6
Creating, Displaying, and Extracting Files, page B-6
Displaying Available File Systems
To display the available file systems on your switch, use the show file systems privileged EXEC
command as shown in this example for a stacking-capable switch. In this example, the stack master is
stack member 2; therefore flash2: is aliased to flash:. The file system on stack member 5 is displayed
as flash5 on the stack master.
Switch# show file systems
File Systems:
Table B-1
Size(b)
57409536
524288
57409536
Free(b)
25664000
512375
27306496
Type
opaque
flash
opaque
nvram
opaque
opaque
opaque
opaque
network
network
network
network
opaque
flash
Flags
ro
rw
rw
rw
ro
ro
rw
ro
rw
rw
rw
rw
ro
rw
Prefixes
bs:
flash: flash2:
system:
nvram:
xmodem:
ymodem:
null:
tar:
tftp:
rcp:
http:
ftp:
cns:
flash5:
show file systems Field Descriptions
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
B-2
OL-12189-01
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with the Flash File System
Table B-1
show file systems Field Descriptions (continued)
Field
Value
Type
Type of file system.
flashThe file system is for a flash memory device.
nvramThe file system is for a NVRAM device.
opaqueThe file system is a locally generated pseudo file system (for example, the system) or a download
interface, such as brimux.
unknownThe file system is an unknown type.
Flags
Permission for file system.
roread-only.
rwread/write.\
wowrite-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 Protocol (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.
Setting the Default File System
You can specify the file system or directory that the system uses as the default file system by using the
cd filesystem: privileged EXEC command. You can set the default file system to omit the filesystem:
argument from related commands. For example, for all privileged EXEC commands that have the
optional filesystem: argument, the system uses the file system specified by the cd command.
By default, the default file system is flash:.
You can display the current default file system as specified by the cd command by using the pwd
privileged EXEC command.
Displaying Information about Files on a File System
You can view a list of the contents of a file system before manipulating its contents. For example, before
copying a new configuration file to flash memory, you might want to verify that the file system does not
already contain a configuration file with the same name. Similarly, before copying a flash configuration
file to another location, you might want to verify its filename for use in another command.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
B-3
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with the Flash File System
To display information about files on a file system, use one of the privileged EXEC commands in
Table B-2:
Table B-2
Commands for Displaying Information About Files
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.
To display information about the driver text object in the CISCO-MEMORY-POOL-MIB, use the show
memory privileged EXEC command:
Switch# show memory
Head
Processor
2BF1A9C
I/O
F000000
Driver te
1800000
Total(b)
205661540
16769024
4194304
Used(b)
43619116
10503052
44
Free(b)
162042424
6265972
4194260
Lowest(b)
160085888
6132844
4194260
Largest(b)
159736648
6127744
4194260
Changing Directories and Displaying the Working Directory
Beginning in privileged EXEC mode, follow these steps to change directories and to display the working
directory.
Step 1
Command
Purpose
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
B-4
OL-12189-01
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with the Flash File System
Creating and Removing Directories
Beginning in privileged EXEC mode, follow these steps to create and remove a directory:
Step 1
Command
Purpose
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:
FTPftp:[[//username [:password]@location]/directory]/filename
RCPrcp:[[//username@location]/directory]/filename
TFTPtftp:[[//location]/directory]/filename
Local writable file systems include flash:.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
B-5
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with the Flash File System
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 B-9.
To copy software images either by downloading a new version or by uploading the existing one, use the
archive download-sw or the archive upload-sw privileged EXEC command. For more information, see
the Working with Software Images section on page B-23.
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.
Caution
When files are deleted, their contents cannot be recovered.
This example shows how to delete the file myconfig from the default flash memory device:
Switch# delete myconfig
Creating, Displaying, and Extracting Files
You can create a file and write files into it, list the files in a file, and extract the files from a file as
described in the next sections.
Note
Instead of using the copy privileged EXEC command or the archive 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 switch stacks, the archive download-sw and archive
upload-sw privileged EXEC commands can only be used through the stack master. Software images
downloaded to the stack master are automatically downloaded to the rest of the stack members.
To upgrade a switch with an incompatible software image, use the archive copy-sw privileged EXEC
command to copy the software image from an existing stack member to the incompatible switch. That
switch automatically reloads and joins the stack as a fully functioning member.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
B-6
OL-12189-01
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with the Flash File System
Beginning in privileged EXEC mode, follow these steps to create a file, display the contents, and
extract it.
Step 1
Command
Purpose
archive /create destination-url
flash:/file-url
Create a file and add files to it.
For destination-url, specify the destination URL alias for the local or network
file system and the name of the file to create. The -filename. is the file to be
created. These options are supported:
Local flash file system syntax:
flash:
FTP syntax:
ftp:[[//username[:password]@location]/directory]/-filename.
RCP syntax:
rcp:[[//username@location]/directory]/-filename.
TFTP syntax:
tftp:[[//location]/directory]/-filename.
For flash:/file-url, specify the location on the local flash file system in which
the new file is created. You can also specify an optional list of files or directories
within the source directory to add to the new file. If none are specified, all files
and directories at this level are written to the newly created file.
Step 2
archive /table source-url
Display the contents of a file.
For source-url, specify the source URL alias for the local or network file
system. The -filename. is the file to display. These options are supported:
Local flash file system syntax:
flash:
FTP syntax:
ftp:[[//username[:password]@location]/directory]/-filename.
RCP syntax:
rcp:[[//username@location]/directory]/-filename.
TFTP syntax:
tftp:[[//location]/directory]/-filename.
You can also limit the file displays by specifying a list of files or directories after
the file. Only those files appear. If none are specified, all files and directories
appear.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
B-7
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with the Flash File System
Step 3
Command
Purpose
archive /xtract source-url
flash:/file-url [dir/file...]
Extract a file into a directory on the flash file system.
For source-url, specify the source URL alias for the local file system. The
-filename. is the file from which to extract files. These options are supported:
local flash file system syntax:
flash:
FTP syntax:
ftp:[[//username[:password]@location]/directory]/-filename.
RCP syntax:
rcp:[[//username@location]/directory]/-filename.
TFTP syntax:
tftp:[[//location]/directory]/-filename.
For flash:/file-url [dir/file...], specify the location on the local flash file system
from which the file is extracted. Use the dir/file... option to specify a list of files
or directories within the file to be extracted. If none are specified, all files and
directories are extracted.
Step 4
more [/ascii | /binary | /ebcdic]
file-url
Display the contents of any readable file, including a file on a remote file
system.
This example shows how to create a file. This command writes the contents of the new-configs directory
on the local flash device to a file named saved. on the TFTP server at 172.20.10.30:
Switch# archive /create tftp:172.20.10.30/saved. flash:/new-configs
This example shows how to display the contents of a switch file that is in flash memory:
Switch# archive /table flash:cbs31x0-universal-mz.122-40.xx.
info (219 bytes)
cbs31x0-universal-mz.122-40.xx/ (directory)
cbs31x0-universal-mz.122-40.xx/html/ (directory)
cbs31x0-universal-mz.122-40.xx/html/foo.html (0 bytes)
cbs31x0-universal-mz.122-40.xx/cbs31x0-universal-mz.122-40.xx.bin (610856 bytes)
cbs31x0-universal-mz.122-40.xx/info (219 bytes)
This example shows how to display only the /html directory and its contents:
Switch# archive /table flash: cbs31x0-universal-mz.122-40/html
cbs31x0-universal-mz.122-40.xx/html
cbs31x0-universal-mz.122-40.xx/html/ (directory)
cbs31x0-universal-mz.122-40.xx/html/const.htm (556 bytes)
cbs31x0-universal-mz.122-40.xx/html/xhome.htm (9373 bytes)
cbs31x0-universal-mz.122-40.xx/html/menu.css (1654 bytes)
<output truncated>
This example shows how to extract the contents of a file located on the TFTP server at 172.20.10.30.
Switch# archive /xtract tftp:/172.20.10.30/saved. flash:/new-configs
This example shows how to display the contents of a configuration file on a TFTP server:
Switch#
!
! Saved
!
version
service
more tftp://serverA/hampton/savedconfig
configuration on server
12.2
timestamps log datetime localtime
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
B-8
OL-12189-01
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Configuration Files
service
service
service
!
<output
linenumber
udp-small-servers
pt-vty-logging
truncated>
Working with Configuration Files
This section describes how to create, load, and maintain configuration files.
Note
For information about configuration files in switch stacks, see the Switch Stack Configuration Files
section on page 5-16.
Configuration files contain commands entered to customize the function of the Cisco IOS software. A
way to create a basic configuration file is to use the setup program or to enter the setup privileged EXEC
command. For more information, see Chapter 3, Assigning the Switch IP Address and Default
Gateway.
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.
These sections contain this configuration information:
Guidelines for Creating and Using Configuration Files, page B-10
Configuration File Types and Location, page B-10
Creating a Configuration File By Using a Text Editor, page B-11
Copying Configuration Files By Using TFTP, page B-11
Copying Configuration Files By Using FTP, page B-13
Copying Configuration Files By Using RCP, page B-16
Clearing Configuration Information, page B-19
Replacing and Rolling Back Configurations, page B-20
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
B-9
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Configuration Files
Guidelines for Creating and Using Configuration Files
Creating configuration files can aid in your switch configuration. Configuration files can contain some
or all of the commands needed to configure one or more switches. For example, you might want to
download the same configuration file to several switches that have the same hardware configuration.
Use these guidelines when creating a configuration file:
Note
We recommend that you connect through the console port or Ethernet management port for the
initial configuration of the switch. If you are accessing the switch through a network connection
instead of through a direct connection to the console port or Ethernet management port, keep in mind
that some configuration changes (such as changing the switch IP address or disabling ports) can
cause a loss of connectivity to the switch.
If no password has been set on the switch, we recommend that you set one by using the enable secret
secret-password global configuration command.
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.
Configuration File Types and Location
Startup configuration files are used during system startup to configure the software. Running
configuration files contain the current configuration of the software. The two configuration files can be
different. For example, you might want to change the configuration for a short time period rather than
permanently. In this case, you would change the running configuration but not save the configuration by
using the copy running-config startup-config privileged EXEC command.
The running configuration is saved in DRAM; the startup configuration is stored in the NVRAM section
of flash memory.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
B-10
OL-12189-01
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Configuration Files
Creating a Configuration File By Using a Text Editor
When creating a configuration file, you must list commands logically so that the system can respond
appropriately. This is one method of creating a configuration file:
Step 1
Copy an existing configuration from a switch to a server.
For more information, see the Downloading the Configuration File By Using TFTP section on
page B-12, the Downloading a Configuration File By Using FTP section on page B-14, or the
Downloading a Configuration File By Using RCP section on page B-18.
Step 2
Open the configuration file in a text editor, such as vi or emacs on UNIX or Notepad on a PC.
Step 3
Extract the portion of the configuration file with the desired commands, and save it in a new file.
Step 4
Copy the configuration file to the appropriate server location. For example, copy the file to the TFTP
directory on the workstation (usually /tftpboot on a UNIX workstation).
Step 5
Make sure the permissions on the file are set to world-read.
Copying Configuration Files By Using TFTP
You can configure the switch by using configuration files you create, download from another switch, or
download from a TFTP server. You can copy (upload) configuration files to a TFTP server for storage.
These sections contain this configuration information:
Preparing to Download or Upload a Configuration File By Using TFTP, page B-11
Downloading the Configuration File By Using TFTP, page B-12
Uploading the Configuration File By Using TFTP, page B-12
Preparing to Download or Upload a Configuration File By Using TFTP
Before you begin downloading or uploading a configuration file by using TFTP, do these tasks:
Ensure that the workstation acting as the TFTP server is properly configured. On a Sun workstation,
make sure that the /etc/inetd.conf file contains this line:
tftp dgram udp wait root /usr/etc/in.tftpd in.tftpd -p -s /tftpboot
Make sure that the /etc/services file contains this line:
tftp 69/udp
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
B-11
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Configuration Files
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.
Downloading the Configuration File By Using TFTP
To configure the switch by using a configuration file downloaded from a TFTP server, follow these steps:
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 B-11.
Step 3
Log into the switch through the console port, the Ethernet management 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
copy tftp:[[[//location]/directory]/filename] flash[n]:/directory/startup-config
Note
You can only enter the flashn parameter (for example, flash3) on stacking-capable switches.
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]
Uploading the Configuration File By Using TFTP
To upload a configuration file from a switch to a TFTP server for storage, follow these steps:
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 B-11.
Step 2
Log into the switch through the console port, the Ethernet management port, or a Telnet session.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
B-12
OL-12189-01
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Configuration Files
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]
copy flash[n]:/directory/startup-config tftp:[[[//location]/directory]/filename]
Note
You can only enter the flashn parameter (for example, flash3) on Catalyst 3750-E switches.
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]
Copying Configuration Files By Using FTP
You can copy configuration files to or from an FTP server.
The FTP protocol requires a client to send a remote username and password on each FTP request to a
server. When you copy a configuration file from the switch to a server by using FTP, 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 ftp username username global configuration command if the command
is configured.
Anonymous.
The switch sends the first valid password in this list:
The password specified in the copy command if a password is specified.
The password set by the ip ftp password password global configuration command if the command
is configured.
The switch forms a password named [email protected]. The variable username is the
username associated with the current session, switchname is the configured hostname, and domain
is the domain of the switch.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
B-13
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Configuration Files
These sections contain this configuration information:
Preparing to Download or Upload a Configuration File By Using FTP, page B-14
Downloading a Configuration File By Using FTP, page B-14
Uploading a Configuration File By Using FTP, page B-15
Preparing to Download or Upload a Configuration File By Using FTP
Before you begin downloading or uploading a configuration file by using FTP, do these tasks:
Ensure that the switch has a route to the FTP server. The switch and the FTP server must be in the
same subnetwork if you do not have a router to route traffic between subnets. Check connectivity to
the FTP 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 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 during all copy 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
copy command if you want to specify a username for only that copy operation.
When you upload a configuration 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.
Downloading a Configuration File By Using FTP
Beginning in privileged EXEC mode, follow these steps to download a configuration file by using FTP:
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 B-14.
Step 2
Log into the switch through the console port, the Ethernet
management 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).
Step 4
ip ftp username username
(Optional) Change the default remote username.
Step 5
ip ftp password password
(Optional) Change the default password.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
B-14
OL-12189-01
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Configuration Files
Command
Purpose
Step 6
end
Return to privileged EXEC mode.
Step 7
Using FTP, copy the configuration file from a network server
copy
ftp:[[[//[username[:password]@]location]/directory] to the running configuration or to the startup configuration
file.
/filename] system:running-config
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:[email protected]/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
Uploading a Configuration File By Using FTP
Beginning in privileged EXEC mode, follow these steps to upload a configuration file by using FTP:
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 B-14.
Step 2
Log into the switch through the console port, the Ethernet
management port, or a Telnet session.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
B-15
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Configuration Files
Step 3
Command
Purpose
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
Using FTP, store the switch running or startup configuration
copy system:running-config
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:[email protected]/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]
Copying Configuration Files By Using RCP
The RCP provides another method of downloading, uploading, and copying configuration files between
remote hosts and the switch. Unlike TFTP, which uses User Datagram Protocol (UDP), a connectionless
protocol, RCP uses TCP, which is connection-oriented.
To use RCP to copy files, the server from or to which you will be copying files must support RCP. The
RCP copy commands rely on the rsh server (or daemon) on the remote system. To copy files by using
RCP, you do not need to create a server for file distribution as you do with TFTP. You only need to have
access to a server that supports the remote shell (rsh). (Most UNIX systems support rsh.) Because you
are copying a file from one place to another, you must have read permission on the source file and write
permission on the destination file. If the destination file does not exist, RCP creates it for you.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
B-16
OL-12189-01
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Configuration Files
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.
These sections contain this configuration information:
Preparing to Download or Upload a Configuration File By Using RCP, page B-17
Downloading a Configuration File By Using RCP, page B-18
Uploading a Configuration File By Using RCP, page B-19
Preparing to Download or Upload a Configuration File By Using RCP
Before you begin downloading or uploading a configuration 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 copy 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 RCP username.
Include the username in the copy command if you want to specify a username for only that copy
operation.
When you upload a file to the RCP 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 that 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
B-17
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Configuration Files
Downloading a Configuration File By Using RCP
Beginning in privileged EXEC mode, follow these steps to download a configuration file by using RCP:
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 B-17.
Step 2
Log into the switch through the console port, the Ethernet
management 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
rcp:[[[//[username@]location]/directory]/filename]
system:running-config
Using RCP, copy the configuration file from a network
server to the running configuration or to the startup
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://[email protected]/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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
B-18
OL-12189-01
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Configuration Files
Uploading a Configuration File By Using RCP
Beginning in privileged EXEC mode, follow these steps to upload a configuration file by using RCP:
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 B-17.
Step 2
Log into the switch through the console port, the Ethernet
management 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
rcp:[[[//[username@]location]/directory]/filename]
Using RCP, copy the configuration file from a switch running
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://[email protected]/switch2-confg
Write file switch-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:
Switch# configure terminal
Switch(config)# ip rcmd remote-username netadmin2
Switch(config)# end
Switch# copy nvram:startup-config rcp:
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]
Clearing Configuration Information
You can clear the configuration information from the startup configuration. If you reboot the switch with
no startup configuration, the switch enters the setup program so that you can reconfigure the switch with
all new settings.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
B-19
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Configuration Files
Clearing the Startup Configuration File
To clear the contents of your startup configuration, use the erase nvram: or the erase startup-config
privileged EXEC command.
Caution
You cannot restore the startup configuration file after it has been deleted.
Deleting a Stored Configuration File
To delete a saved configuration from flash memory, use the delete flash:filename privileged EXEC
command. Depending on the setting of the file prompt global configuration command, you might be
prompted for confirmation before you delete a file. By default, the switch prompts for confirmation on
destructive file operations. For more information about the file prompt command, see the Cisco IOS
Command Reference for Release 12.2.
Caution
You cannot restore a file after it has been deleted.
Replacing and Rolling Back Configurations
The configuration replacement and rollback feature replaces the running configuration with any saved
Cisco IOS configuration file. You can use the rollback function to roll back to a previous configuration.
These sections contain this information:
Understanding Configuration Replacement and Rollback, page B-20
Configuration Guidelines, page B-21
Configuring the Configuration Archive, page B-22
Performing a Configuration Replacement or Rollback Operation, page B-23
Understanding Configuration Replacement and Rollback
To use the configuration replacement and rollback feature, you should understand these concepts:
Archiving a Configuration, page B-20
Replacing a Configuration, page B-21
Rolling Back a Configuration, page B-21
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
B-20
OL-12189-01
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Configuration Files
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.
Rolling Back a Configuration
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
B-21
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Configuration Files
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.
Note
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).
If you generate the replacement configuration file externally, it must comply with the format of files
generated by Cisco IOS devices.
Configuring the Configuration Archive
Using the configure replace command with the configuration archive and with the archive config
command is optional but offers significant benefit for configuration rollback scenarios. Before using the
archive config command, you must first configure the configuration archive. Starting in privileged
EXEC mode, follow these steps to configure the configuration archive:
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.
numberMaximum files of the running configuration file in the configuration
archive. Valid values are from 1 to 14. The default is 10.
Note
Step 5
time-period minutes
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.
(Optional) Set the time increment for automatically saving an archive file of
the running configuration in the configuration archive.
minutesSpecify 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
startup-config
(Optional) Save your entries in the configuration file.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
B-22
OL-12189-01
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Software Images
Performing a Configuration Replacement or Rollback Operation
Starting in privileged EXEC mode, follow these steps to replace the running configuration file with a
saved configuration file:
Step 1
Command
Purpose
archive config
(Optional) Save the running configuration file to the configuration archive.
Note
Step 2
configure terminal
Enter the path archive configuration command before using this
command.
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]
[force] [time seconds] [nolock]
Replace the running configuration file with a saved configuration file.
target-urlURL (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.
listDisplay 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 secondsSpecify 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.
nolockDisable the locking of the running configuration file that prevents
other users from changing the running configuration during a configuration
replacement operation.
Step 6
configure confirm
(Optional) Confirm replacement of the running configuration with a saved
configuration file.
Note
Step 7
copy running-config
startup-config
Use this command only if the time seconds keyword and argument of
the configure replace command are specified.
(Optional) Save your entries in the configuration file.
Working with Software Images
This section describes how to archive (download and upload) software image files, which contain the
system software, the Cisco IOS code, and the embedded device manager software.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
B-23
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Software Images
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 switch stacks, the archive download-sw and archive
upload-sw privileged EXEC commands can only be used through the stack master. Software images
downloaded to the stack master are automatically downloaded to the rest of the stack members.
To upgrade a switch with an incompatible software image, use the archive copy-sw privileged EXEC
command to copy the software image from an existing stack member to the incompatible switch. That
switch automatically reloads and joins the stack as a fully functioning member.
You can 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) and then by using the device manager or Cisco Network
Assistant to upgrade your switch. For information about upgrading your switch by using a TFTP server
or a web browser (HTTP), see the release notes.
You can replace the current image with the new one or keep the current image in flash memory after a
download.
You can use the archive download-sw /allow-feature-upgrade privileged EXEC command to allow
installation of an image with a different feature set, for example, upgrading from the noncryptographic
universal image with the IP services feature set to the cryptographic universal image with the advanced
IP services feature set. You can also use the boot auto-download-sw global configuration command to
specify a URL to use to get an image for automatic software upgrades. When you enter this command,
the master switch uses this URL in case of a version mismatch.
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 to another of the same type.
The protocol that 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.
These sections contain this configuration information:
Note
Image Location on the Switch, page B-25
File Format of Images on a Server or Cisco.com, page B-25
Copying Image Files By Using TFTP, page B-26
Copying Image Files By Using FTP, page B-29
Copying Image Files By Using RCP, page B-34
Copying an Image File from One Stack Member to Another, page B-39
For a list of software images and the supported upgrade paths, see the release notes.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
B-24
OL-12189-01
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Software Images
Image Location on the Switch
The Cisco IOS image is stored as a .bin file in a directory that shows the version number. A subdirectory
contains the files needed for web management. The image is stored on the system board flash memory
(flash:).
You can use the show version privileged EXEC command to see the software version that is currently
running on your switch. In the display, check the line that begins with System image file is... . It
shows the directory name in flash memory where the image is stored.
You can also use the dir filesystem: privileged EXEC command to see the directory names of other
software images that you might have stored in flash memory. You can use the archive download-sw
/directory privileged EXEC command to specify a directory once followed by a tar file or list of tar files
to be downloaded instead of specifying complete paths with each tar file. .
File Format of Images on a Server or Cisco.com
Software images on a server or downloaded from Cisco.com are in a file format, which contains these
files:
An info file, which serves as a table of contents for the file
One or more subdirectories containing other images and files, such as Cisco IOS images and web
management files
This example shows some of the information contained in the info file. Table B-3 provides additional
details about this information:
system_type:0x00000000:cbs31x0-universal-mz.122-40.xx
image_family:CBS31x0
stacking_number:1.9
info_end:
version_suffix:universal-mz.122-40.xx
version_directory:cbs31x0-universal-mz.122-40.xx
image_system_type_id:0x00000000
image_name:cbs31x0-universal-mz.122-40.xx.bin
ios_image_file_size:6398464
total_image_file_size:8133632
image_feature:IP|LAYER_3|PLUS|MIN_DRAM_MEG=128
image_family:CBS31x0
stacking_number:1.9
board_ids:0x401100c4 0x00000000 0x00000001 0x00000003 0x00000002 0x00008000 0x00008002
0x40110000
info_end:
Note
Table B-3
On nonstacking-capable switches, the stacking_number field does not apply to the switch.
info File Description
Field
Description
version_suffix
Specifies the Cisco IOS image version string suffix
version_directory
Specifies the directory where the Cisco IOS image and the HTML subdirectory are installed
image_name
Specifies the name of the Cisco IOS image in the file
ios_image_file_size
Specifies the Cisco IOS image size in the file, which is an approximate measure of the flash
memory that the Cisco IOS image needs.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
B-25
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Software Images
Table B-3
info File Description (continued)
Field
Description
total_image_file_size
Specifies the size of all the images (the Cisco IOS image and the web management files) in the
file, which is an approximate measure of the flash memory needed.
image_feature
Describes the core functionality of the image
image_min_dram
Specifies the minimum amount of DRAM needed to run this image
image_family
Describes the family of products on which the software can be installed
Copying Image Files By Using TFTP
You can download a switch image from a TFTP server or upload the image from the switch to a TFTP
server.
You download a switch image file from a server to upgrade the switch software. You can overwrite the
current image with the new one or keep the current image after a download.
You upload a switch image file to a server for backup purposes; this uploaded image can be used for
future downloads to the same 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. For switch stacks, the archive download-sw and archive
upload-sw privileged EXEC commands can only be used through the stack master. Software images
downloaded to the stack master are automatically downloaded to the rest of the stack members.
To upgrade a switch with an incompatible software image, use the archive copy-sw privileged EXEC
command to copy the software image from an existing stack member to the incompatible switch. That
switch automatically reloads and joins the stack as a fully functioning member.
These sections contain this configuration information:
Preparing to Download or Upload an Image File By Using TFTP, page B-26
Downloading an Image File By Using TFTP, page B-27
Uploading an Image File By Using TFTP, page B-29
Preparing to Download or Upload an Image File By Using TFTP
Before you begin downloading or uploading an image file by using TFTP, do these tasks:
Ensure that the workstation acting as the TFTP server is properly configured. On a Sun workstation,
make sure that the /etc/inetd.conf file contains this line:
tftp dgram udp wait root /usr/etc/in.tftpd in.tftpd -p -s /tftpboot
Make sure that the /etc/services file contains this line:
tftp 69/udp
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
B-26
OL-12189-01
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Software Images
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.
Downloading an Image File By Using TFTP
You can download a new image file and replace the current image or keep the current image.
Beginning in privileged EXEC mode, follow Steps 1 through 3 to download a new image from a TFTP
server and to overwrite the existing image. To keep the current image, follow Steps 1, 2, and 4.
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 B-26.
Step 2
Log into the switch through the console port, the Ethernet
management port, or a Telnet session.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
B-27
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Software Images
Step 3
Step 4
Step 5
Command
Purpose
archive download-sw
/allow-feature-upgrade [/directory]
/overwrite /reload
tftp:[[//location]/directory]/image-name1.tar
[image-name2.tar image-name3.tar
image-name4.tar]
(Optional) Download the image files from the TFTP server to the
switch, and overwrite the current image.
archive download-sw [/directory]
/leave-old-sw /reload
tftp:[[//location]/directory]/image-name1.tar
[image-name2.tar image-name3.tar
image-name4.tar]
dir flash:
The /allow-feature-upgrade option allows installation of a
software images with different feature sets.
(Optional) The /directory option specifies a directory for the
images.
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-name1.tar [/directory/image-name2.tar
image-name3.tar image-name4.tar], specify the directory
(optional) and the images to download. Directory and image
names are case sensitive.
(Optional) Download the images file from the TFTP server to the
switch, and keep the current image.
(Optional) The /directory option specifies a directory for the
images.
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-name1.tar [/directory/image-name2.tar
image-name3.tar image-name4.tar], specify the directory
(optional) and the images to download. Directory and image
names are case sensitive.
Verify that the image is successfully copied into the flash device.
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 is
displayed.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
B-28
OL-12189-01
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Software Images
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.
Uploading an Image File By Using TFTP
You can upload an image from the switch to a TFTP server. You can later download this image to the
switch or to another switch of the same type.
Use the upload feature only if the web management pages associated with the embedded device manager
have been installed with the existing image.
Beginning in privileged EXEC mode, follow these steps to upload an image to a TFTP server:
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 B-26.
Step 2
Log into the switch through the console port, the Ethernet
management port, or a Telnet session.
Step 3
archive upload-sw
tftp:[[//location]/directory]/image-name.tar
Upload the currently running switch image to the TFTP server.
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 these
files in order: info, the Cisco IOS image, and the web management files. After these files are uploaded,
the upload algorithm creates the file format.
Caution
For the download and upload algorithms to operate properly, do not rename image names.
Copying Image Files By Using FTP
You can download a switch image from an FTP server or upload the image from the switch to an FTP
server.
You download a switch image file from a server to upgrade the switch software. You can overwrite the
current image with the new one or keep the current image after a download.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
B-29
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Software Images
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. For switch stacks, the archive download-sw and archive
upload-sw privileged EXEC commands can only be used through the stack master. Software images
downloaded to the stack master are automatically downloaded to the rest of the stack members.
To upgrade a switch with an incompatible software image, use the archive copy-sw privileged EXEC
command to copy the software image from an existing stack member to the incompatible switch. That
switch automatically reloads and joins the stack as a fully functioning member.
These sections contain this configuration information:
Preparing to Download or Upload an Image File By Using FTP, page B-30
Downloading an Image File By Using FTP, page B-31
Uploading an Image File By Using FTP, page B-33
Preparing to Download or Upload an Image File By Using FTP
You can copy images files to or from an FTP server.
The FTP protocol requires a client to send a remote username and password on each FTP request to a
server. When you copy an image file from the switch to a server by using FTP, the Cisco IOS software
sends the first valid username in this list:
The username specified in the archive download-sw or archive upload-sw privileged EXEC
command if a username is specified.
The username set by the ip ftp username username global configuration command if the command
is configured.
Anonymous.
The switch sends the first valid password in this list:
The password specified in the archive download-sw or archive upload-sw privileged EXEC
command if a password is specified.
The password set by the ip ftp password password global configuration command if the command
is configured.
The switch forms a password named [email protected]. The variable username is the
username associated with the current session, switchname is the configured hostname, and domain
is the domain of the switch.
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 the FTP write request from you.
Use the ip ftp username and ip ftp password commands to specify a username and password for all
copies. 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.
If the server has a directory structure, the image file is written to or copied from the directory associated
with the 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
B-30
OL-12189-01
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Software Images
Before you begin downloading or uploading an image file by using FTP, do these tasks:
Ensure that the switch has a route to the FTP server. The switch and the FTP server must be in the
same subnetwork if you do not have a router to route traffic between subnets. Check connectivity to
the FTP 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 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.
Downloading an Image File By Using FTP
You can download a new image file and overwrite the current image or keep the current image.
Beginning in privileged EXEC mode, follow Steps 1 through 7 to download a new image from an FTP
server and to overwrite the existing image. To keep the current image, follow Steps 1 to 6 and Step 8.
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 B-30.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
B-31
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Software Images
Step 7
Step 8
Step 9
Command
Purpose
archive download-sw /allow-feature-upgrade
[/directory] /overwrite /reload
tftp:[[//location]/directory]/image-name1.tar
[image-name2.tar image-name3.tar
image-name4.tar]
(Optional) Download the image files from the FTP server to
the switch, and overwrite the current image.
archive download-sw [/directory] /leave-old-sw
/reload
tftp:[[//location]/directory]/image-name1.tar
[image-name2.tar image-name3.tar
image-name4.tar]
dir flash:
The /allow-feature-upgrade option allows installation of
a software image with a different feature set.
(Optional) The /directory option specifies a directory for
the images.
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 B-30.
For @location, specify the IP address of the FTP server.
For /directory/image-name1.tar
[/directory/image-name2.tar image-name3.tar
image-name4.tar], specify the directory (optional) and the
images to download. Directory and image names are case
sensitive.
(Optional) Download the image files from the FTP server to
the switch, and keep the current image.
(Optional) The /directory option specifies a directory for
the images.
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 B-30.
For @location, specify the IP address of the FTP server.
For directory/image-name.tar, specify the directory and
the image to download. Directory and image names are
case sensitive.
Verify that the image is successfully copied into the flash
device.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
B-32
OL-12189-01
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Software Images
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 is
displayed.
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.
Uploading an Image File By Using FTP
You can upload an image from the switch to an FTP server. You can later download this image to the
same switch or to another switch of the same type.
Use the upload feature only if the web management pages associated with the embedded device manager
have been installed with the existing image.
Beginning in privileged EXEC mode, follow these steps to upload an image to an FTP server:
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 B-14.
Step 2
Log into the switch through the console port, the Ethernet
management port, or remotely through a Telnet session by
using the IP address of the Ethernet management port.
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
B-33
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Software Images
Command
Purpose
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 B-30.
For @location, specify the IP address of the FTP server.
For /directory/image-name.tar, specify the directory
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 these files in order:
info, the Cisco IOS image, and the web management files. After these files are uploaded, the upload
algorithm creates the file format.
Caution
For the download and upload algorithms to operate properly, do not rename image names.
Copying Image Files By Using RCP
You can download a switch image from an RCP server or upload the image from the switch to an RCP
server.
You download a switch image file from a server to upgrade the switch software. You can overwrite the
current image with the new one or keep the current image after a download.
You upload a switch image file to a server for backup purposes. You can use this uploaded image for
future downloads to the same switch or another 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. For switch stacks, the archive download-sw and archive
upload-sw privileged EXEC commands can only be used through the stack master. Software images
downloaded to the stack master are automatically downloaded to the rest of the stack members.
To upgrade a switch with an incompatible software image, use the archive copy-sw privileged EXEC
command to copy the software image from an existing stack member to the incompatible switch. That
switch automatically reloads and joins the stack as a fully functioning member.
These sections contain this configuration information:
Preparing to Download or Upload an Image File By Using RCP, page B-35
Downloading an Image File By Using RCP, page B-36
Uploading an Image File By Using RCP, page B-38
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
B-34
OL-12189-01
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Software Images
Preparing to Download or Upload an Image File By Using RCP
RCP provides another method of downloading and uploading image files between remote hosts and the
switch. Unlike TFTP, which uses User Datagram Protocol (UDP), a connectionless protocol, RCP uses
TCP, which is connection-oriented.
To use RCP to copy files, the server from or to which you will be copying files must support RCP. The
RCP copy commands rely on the rsh server (or daemon) on the remote system. To copy files by using
RCP, you do not need to create a server for file distribution as you do with TFTP. You only need to have
access to a server that supports the remote shell (rsh). (Most UNIX systems support rsh.) Because you
are copying a file from one place to another, you must have read permission on the source file and write
permission on the destination file. If the destination file does not exist, RCP creates it for you.
RCP requires a client to send a remote username on each RCP request to a server. When you copy an
image from the switch to a server by using RCP, the Cisco IOS software sends the first valid username
in this list:
The username specified in the archive download-sw or archive upload-sw privileged EXEC
command if a username is specified.
The username set by the ip rcmd remote-username username global configuration command if the
command is entered.
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 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 users 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
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
B-35
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Software Images
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.
Downloading an Image File By Using RCP
You can download a new image file and replace or keep the current image.
Beginning in privileged EXEC mode, follow Steps 1 through 6 to download a new image from an RCP
server and overwrite the existing image. To keep the current image, go to Step 6.
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 B-35.
Step 2
Log into the switch through the console port, the Ethernet
management 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
B-36
OL-12189-01
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Software Images
Step 6
Step 7
Step 8
Command
Purpose
archive download-sw /allow-feature-upgrade
[/directory] /overwrite /reload
tftp:[[//location]/directory]/image-name1.tar
[image-name2.tar image-name3.tar
image-name4.tar]
Download the images file from the RCP server to the switch
and overwrite the current image.
archive download-sw [/directory] /leave-old-sw
/reload
tftp:[[//location]/directory]/image-name1.tar
[image-name2.tar image-name3.tar
image-name4.tar]
dir flash:
The /allow-feature-upgrade allows installation of a
software image with a different feature set.
(Optional) The /directory option specifies a directory
for the images.
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 B-35.
For @location, specify the IP address of the RCP server.
For /directory/image-name1.tar
[/directory/image-name2.tar image-name3.tar
image-name4.tar], specify the directory (optional) and
the images to download. Directory and image names are
case sensitive.
Download the images file from the RCP server to the switch
and keep the current image.
(Optional) The /directory option specifies a directory
for the images.
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 B-35.
For @location, specify the IP address of the RCP server.
For /directory/image-name1.tar
[/directory/image-name2.tar image-name3.tar
image-name4.tar], specify the directory (optional) and
the images to download. Directory and image names are
case sensitive.
Verify that the image is successfully copied into the flash
device.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
B-37
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Software Images
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 is
displayed.
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.
Uploading an Image File By Using RCP
You can upload an image from the switch to an RCP server. You can later download this image to the
same switch or to another switch of the same type.
The upload feature should be used only if the web management pages associated with the embedded
device manager have been installed with the existing image.
Beginning in privileged EXEC mode, follow these steps to upload an image to an 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 B-35.
Step 2
Log into the switch through the console port, the Ethernet
management 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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
B-38
OL-12189-01
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Software Images
Command
Purpose
Step 5
end
Return to privileged EXEC mode.
Step 6
archive upload-sw
rcp:[[[//[username@]location]/directory]/image-na
me.tar]
Upload the currently running switch image to the RCP
server.
For //username, specify the username; for the RCP copy
request to execute, define an account 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 B-35.
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 these
files in order: info, the Cisco IOS image, and the web management files. After these files are uploaded,
the upload algorithm creates the file format.
Caution
For the download and upload algorithms to operate properly, do not rename image names.
Copying an Image File from One Stack Member to Another
For switch stacks, the archive download-sw and archive upload-sw privileged EXEC commands can
be used only through the stack master. Software images downloaded to the stack master are
automatically downloaded to the rest of the stack members.
To upgrade a switch that has an incompatible software image, use the archive copy-sw privileged EXEC
command to copy the software image from an existing stack member to the one that has incompatible
software. That switch automatically reloads and joins the stack as a fully functioning member.
Note
To use the archive copy-sw privileged EXEC command, you must have downloaded from a TFTP server
the images for both the stack member switch being added and the stack master. You use the archive
download-sw privileged EXEC command to perform the download.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
B-39
Appendix B
Working with the Cisco IOS File System, Configuration Files, and Software Images
Working with Software Images
Beginning in privileged EXEC mode from the stack member that you want to upgrade, follow these steps
to copy the running image file from the flash memory of a different stack member:
Step 1
Command
Purpose
archive copy-sw /destination-system
destination-stack-member-number /force-reload
source-stack-member-number
Copy the running image file from a stack member, and then
unconditionally reload the updated stack member.
Note
At least one stack member must be running the
image that is to be copied to the switch that is
running the incompatible software.
For /destination-system destination-stack-member-number,
specify the number of the stack member (the destination) to
which to copy the source running image file. If you do not
specify this stack member number, the default is to copy the
running image file to all stack members.
Specify /force-reload to unconditionally force a system
reload after the software image downloads.
For source-stack-member-number, specify the number of the
stack member (the source) from which to copy the running
image file. The stack member number range is 1 to 9.
Step 2
reload slot stack-member-number
Reset the updated stack member, and put this configuration
change into effect.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
B-40
OL-12189-01
A P P E N D I X
Unsupported Commands in
Cisco IOS Release 12.2(40)EX2
This appendix lists some of the command-line interface (CLI) commands that appear when you enter the
question mark (?) at the switch prompt but are not supported in this release, either because they are not
tested or because of switch hardware limitations. This is not a complete list. The unsupported commands
are listed by software feature and command mode.
Access Control Lists
Unsupported Privileged EXEC Commands
access-enable [host] [timeout minutes]
access-template [access-list-number | name] [dynamic-name] [source] [destination] [timeout minutes]
clear access-template [access-list-number | name] [dynamic-name] [source] [destination].
show access-lists rate-limit [destination]
show accounting
show ip accounting [checkpoint] [output-packets | access violations]
show ip cache [prefix-mask] [type number]
Unsupported Global Configuration Commands
access-list rate-limit acl-index {precedence | mask prec-mask}
access-list dynamic extended
Unsupported Route-Map Configuration Commands
match ip address prefix-list prefix-list-name [prefix-list-name...]
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
C-1
Appendix C
Unsupported Commands in Cisco IOS Release 12.2(40)EX2
Archive Commands
Archive Commands
Unsupported Privileged EXEC Commands
archive config
show archive config
show archive log
ARP Commands
Unsupported Global Configuration Commands
arp ip-address hardware-address smds
arp ip-address hardware-address srp-a
arp ip-address hardware-address srp-b
Unsupported Interface Configuration Commands
arp probe
ip probe proxy
Boot Loader Commands
Unsupported User EXEC Commands
verify
Unsupported Global Configuration Commands
boot buffersize
boot enable-break
Debug Commands
Note
This section applies only to the Catalyst Switch Module 3110.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
C-2
OL-12189-01
Appendix C
Unsupported Commands in Cisco IOS Release 12.2(40)EX2
Embedded Event Manager
Unsupported Privileged EXEC Commands
debug platform cli-redirection main
debug platform configuration
Embedded Event Manager
Note
This section applies only to the Catalyst Switch Module 3110.
Unsupported Privileged EXEC Commands
event manager update user policy [policy-filename | group [group name expression] ] | repository [url
location]
Parameters are not supported for this command:
event manager run [policy name] |<paramater1>|... <paramater15>|
Unsupported Global Configuration Commands
no event manager directory user repository [url location ]
event manager applet [applet-name] maxrun
Unsupported Commands in Applet Configuration Mode
no event interface name [interface-name ] parameter [counter-name] entry-val [entry counter value]
entry-op {gt|ge|eq|ne|lt|le} [entry-type {increment | rate | value] [exit-val [exit value] exit-op
{gt|ge|eq|ne|lt|le} exit-type { increment | rate | value}][average-factor <average-factor-value>]
no trigger
tag
Fallback Bridging
Note
This section applies only to the Catalyst Switch Module 3110.
Unsupported Privileged EXEC Commands
clear bridge [bridge-group] multicast [router-ports | groups | counts] [group-address] [interface-unit]
[counts]
clear vlan statistics
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
C-3
Appendix C
Unsupported Commands in Cisco IOS Release 12.2(40)EX2
Fallback Bridging
show bridge [bridge-group] circuit-group [circuit-group] [src-mac-address] [dst-mac-address]
show bridge [bridge-group] multicast [router-ports | groups] [group-address]
show bridge vlan
show interfaces crb
show interfaces {ethernet | fastethernet} [interface | slot/port] irb
show subscriber-policy range
Unsupported Global Configuration Commands
bridge bridge-group acquire
bridge bridge-group address mac-address {forward | discard} [interface-id]
bridge bridge-group aging-time seconds
bridge bridge-group bitswap_l3_addresses
bridge bridge-group bridge ip
bridge bridge-group circuit-group circuit-group pause milliseconds
bridge bridge-group circuit-group circuit-group source-based
bridge cmf
bridge crb
bridge bridge-group domain domain-name
bridge irb
bridge bridge-group mac-address-table limit number
bridge bridge-group multicast-source
bridge bridge-group protocol dec
bridge bridge-group route protocol
bridge bridge-group subscriber policy policy
subscriber-policy policy [[no | default] packet [permit | deny]]
Unsupported Interface Configuration Commands
bridge-group bridge-group cbus-bridging
bridge-group bridge-group circuit-group circuit-number
bridge-group bridge-group input-address-list access-list-number
bridge-group bridge-group input-lat-service-deny group-list
bridge-group bridge-group input-lat-service-permit group-list
bridge-group bridge-group input-lsap-list access-list-number
bridge-group bridge-group input-pattern-list access-list-number
bridge-group bridge-group input-type-list access-list-number
bridge-group bridge-group lat-compression
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
C-4
OL-12189-01
Appendix C
Unsupported Commands in Cisco IOS Release 12.2(40)EX2
HSRP
bridge-group bridge-group output-address-list access-list-number
bridge-group bridge-group output-lat-service-deny group-list
bridge-group bridge-group output-lat-service-permit group-list
bridge-group bridge-group output-lsap-list access-list-number
bridge-group bridge-group output-pattern-list access-list-number
bridge-group bridge-group output-type-list access-list-number
bridge-group bridge-group sse
bridge-group bridge-group subscriber-loop-control
bridge-group bridge-group subscriber-trunk
bridge bridge-group lat-service-filtering
frame-relay map bridge dlci broadcast
interface bvi bridge-group
x25 map bridge x.121-address broadcast [options-keywords]
HSRP
Unsupported Global Configuration Commands
interface Async
interface BVI
interface Dialer
interface Group-Async
interface Lex
interface Multilink
interface Virtual-Template
interface Virtual-Tokenring
Unsupported Interface Configuration Commands
mtu
standby mac-refresh seconds
standby use-bia
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
C-5
Appendix C
Unsupported Commands in Cisco IOS Release 12.2(40)EX2
IGMP Snooping Commands
IGMP Snooping Commands
Unsupported Global Configuration Commands
ip igmp snooping tcn
Interface Commands
Unsupported Privileged EXEC Commands
show interfaces [interface-id | vlan vlan-id] [crb | fair-queue | irb | mac-accounting | precedence | irb
| random-detect | rate-limit | shape]
Unsupported Global Configuration Commands
interface tunnel
Unsupported Interface Configuration Commands
transmit-interface type number
IP Multicast Routing
Note
This section applies only to the Catalyst Switch Module 3110.
Unsupported Privileged EXEC Commands
clear ip rtp header-compression [type number]
The debug ip packet command displays packets received by the switch CPU. It does not display packets
that are hardware-switched.
The debug ip mcache command affects packets received by the switch CPU. It does not display packets
that are hardware-switched.
The debug ip mpacket [detail] [access-list-number [group-name-or-address] command affects only
packets received by the switch CPU. Because most multicast packets are hardware-switched, use this
command only when you know that the route will forward the packet to the CPU.
debug ip pim atm
show frame-relay ip rtp header-compression [interface type number]
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
C-6
OL-12189-01
Appendix C
Unsupported Commands in Cisco IOS Release 12.2(40)EX2
IP Multicast Routing
The show ip mcache command displays entries in the cache for those packets that are sent to the switch
CPU. Because most multicast packets are switched in hardware without CPU involvement, you can use
this command, but multicast packet information is not displayed.
The show ip mpacket commands are supported but are only useful for packets received at the switch
CPU. If the route is hardware-switched, the command has no effect because the CPU does not receive
the packet and cannot display it.
show ip pim vc [group-address | name] [type number]
show ip rtp header-compression [type number] [detail]
Unsupported Global Configuration Commands
ip multicast-routing vrf vrf-name
ip pim accept-rp {address | auto-rp} [group-access-list-number]
ip pim message-interval seconds
Unsupported Interface Configuration Commands
frame-relay ip rtp header-compression [active | passive]
frame-relay map ip ip-address dlci [broadcast] compress
frame-relay map ip ip-address dlci rtp header-compression [active | passive]
ip igmp helper-address ip-address
ip multicast helper-map {group-address | broadcast} {broadcast-address | multicast-address}
extended-access-list-number
ip multicast rate-limit {in | out} [video | whiteboard] [group-list access-list] [source-list access-list]
kbps
ip multicast ttl-threshold ttl-value (instead, use the ip multicast boundary access-list-number
interface configuration command)
ip multicast use-functional
ip pim minimum-vc-rate pps
ip pim multipoint-signalling
ip pim nbma-mode
ip pim vc-count number
ip rtp compression-connections number
ip rtp header-compression [passive]
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
C-7
Appendix C
Unsupported Commands in Cisco IOS Release 12.2(40)EX2
IP Unicast Routing
IP Unicast Routing
Unsupported Privileged EXEC or User EXEC Commands
clear ip accounting [checkpoint]
clear ip bgp address flap-statistics
clear ip bgp prefix-list
debug ip cef stats
show cef [drop | not-cef-switched]
show ip accounting [checkpoint] [output-packets | access-violations]
show ip bgp dampened-paths
show ip bgp inconsistent-as
show ip bgp regexp regular expression
show ip prefix-list regular expression
Unsupported Global Configuration Commands
ip accounting precedence {input | output}
ip accounting-list ip-address wildcard
ip as-path access-list
ip accounting-transits count
ip cef accounting [per-prefix] [non-recursive]
ip cef traffic-statistics [load-interval seconds] [update-rate seconds]]
ip flow-aggregation
ip flow-cache
ip flow-export
ip gratuitous-arps
ip local
ip prefix-list
ip reflexive-list
router egp
router-isis
router iso-igrp
router mobile
router odr
router static
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
C-8
OL-12189-01
Appendix C
Unsupported Commands in Cisco IOS Release 12.2(40)EX2
IP Unicast Routing
Unsupported Interface Configuration Commands
ip accounting
ip load-sharing [per-packet]
ip mtu bytes
ip verify
ip unnumbered type number
All ip security commands
Unsupported BGP Router Configuration Commands
address-family vpnv4
default-information originate
neighbor advertise-map
neighbor allowas-in
neighbor default-originate
neighbor description
network backdoor
table-map
Unsupported VPN Configuration Commands
All
Unsupported Route Map Commands
match route-type for policy-based routing (PBR)
set as-path {tag | prepend as-path-string}
set automatic-tag
set dampening half-life reuse suppress max-suppress-time
set default interface interface-id [interface-id.....]
set interface interface-id [interface-id.....]
set ip default next-hop ip-address [ip-address.....]
set ip destination ip-address mask
set ip next-hop verify-availability
set ip precedence value
set ip qos-group
set metric-type internal
set origin
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
C-9
Appendix C
Unsupported Commands in Cisco IOS Release 12.2(40)EX2
MAC Address Commands
set metric-type internal
set tag tag-value
MAC Address Commands
Unsupported Privileged EXEC Commands
show mac-address-table
show mac-address-table address
show mac-address-table aging-time
show mac-address-table count
show mac-address-table dynamic
show mac-address-table interface
show mac-address-table multicast
show mac-address-table notification
show mac-address-table static
show mac-address-table vlan
show mac address-table multicast
Note
Use the show ip igmp snooping groups privileged EXEC command to display Layer 2 multicast
address-table entries for a VLAN.
Unsupported Global Configuration Commands
mac-address-table aging-time
mac-address-table notification
mac-address-table static
Miscellaneous
Unsupported Privileged EXEC Commands
file verify auto
remote command (only on the Catalyst Switch Module 3110)
show cable-diagnostics prbs
test cable-diagnostics prbs
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
C-10
OL-12189-01
Appendix C
Unsupported Commands in Cisco IOS Release 12.2(40)EX2
MSDP
Unsupported Global Configuration Commands
errdisable recovery cause unicast flood
l2protocol-tunnel global drop-threshold
service compress-config
stack-mac persistent timer (only on the Catalyst Switch Module 3110)
track object-number rtr
MSDP
Note
This section applies only to the Catalyst Switch Module 3110.
Unsupported Privileged EXEC Commands
show access-expression
show exception
show location
show pm LINE
show smf [interface-id]
show subscriber-policy [policy-number]
show template [template-name]
Unsupported Global Configuration Commands
ip msdp default-peer ip-address | name [prefix-list list] (Because BGP/MBGP is not supported, use the
ip msdp peer command instead of this command.)
NetFlow Commands
Unsupported Global Configuration Commands
ip flow-aggregation cache
ip flow-cache entries
ip flow-export
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
C-11
Appendix C
Unsupported Commands in Cisco IOS Release 12.2(40)EX2
Network Address Translation (NAT) Commands
Network Address Translation (NAT) Commands
Unsupported Privileged EXEC Commands
show ip nat statistics
show ip nat translations
QoS
Unsupported Global Configuration Command
priority-list
Unsupported Interface Configuration Commands
priority-group
rate-limit
Unsupported Policy-Map Configuration Command
class class-default where class-default is the class-map-name.
RADIUS
Unsupported Global Configuration Commands
aaa nas port extended
aaa authentication feature default enable
aaa authentication feature default line
radius-server attribute nas-port
radius-server configure
radius-server extended-portnames
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
C-12
OL-12189-01
Appendix C
Unsupported Commands in Cisco IOS Release 12.2(40)EX2
SNMP
SNMP
Unsupported Global Configuration Commands
snmp-server enable informs
snmp-server ifindex persist
Spanning Tree
Unsupported Global Configuration Command
spanning-tree pathcost method {long | short}
Unsupported Interface Configuration Command
spanning-tree stack-port
VLAN
Unsupported Global Configuration Command
vlan internal allocation policy {ascending | descending}
Unsupported User EXEC Commands
show running-config vlan
show vlan ifindex
VTP
Unsupported Privileged EXEC Command
vtp {password password | pruning | version number}
Note
This command has been replaced by the vtp global configuration command.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
C-13
Appendix C
Unsupported Commands in Cisco IOS Release 12.2(40)EX2
VTP
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
C-14
OL-12189-01
INDEX
ACEs
Numerics
and QoS
10-Gigabit Ethernet interfaces
10-6
defined
36-7
34-2
Ethernet
IP
34-2
34-2
ACLs
AAA down policy, NAC Layer 2 IP validation
abbreviating commands
ABRs
1-10
ACEs
34-2
any keyword
2-4
34-13
applying
38-32
on bridged packets
access
templates
34-37
on multicast packets
8-1
access-class command
on routed packets
34-20
34-38
on switched packets
access control entries
See ACEs
access-denied response, VMPS
12-29
applying IPv4 ACLs to interfaces
34-17
to an interface
34-20, 35-8
to QoS
34-21
34-36
time ranges to
to IPv6 interfaces
access groups
35-8
36-7
Layer 2
34-21
classifying traffic for QoS
Layer 3
34-21
comments in
access groups, applying IPv4 ACLs to interfaces
accessing stack members
compiling
defined
5-26
36-43
34-19
34-22
34-1, 34-7
examples of
access lists
34-22, 36-43
extended IP, configuring for QoS classification
See ACLs
36-44
extended IPv4
access ports
and Layer 2 protocol tunneling
defined
34-21
34-38
creating
16-11
matching criteria
10-3
access template
34-11
hardware and software handling
8-1
host keyword
accounting
with 802.1x
with IEEE 802.1x
with TACACS+
34-22
34-13
IP
9-33
with RADIUS
34-8
9-9
7-28
7-11, 7-17
creating
34-7
fragments and QoS guidelines
implicit deny
implicit masks
36-32
34-10, 34-14, 34-17
34-10
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
IN-1
Index
ACLs (continued)
ACLs (continued)
IP (continued)
matching criteria
undefined
router ACLs and VLAN map configuration
guidelines 34-35
34-8
standard IP, configuring for QoS classification
34-21
standard IPv4
IPv4
applying to interfaces
creating
named
creating
34-20
support for
34-8
time ranges
34-8
terminal lines, setting on
unsupported features
35-4
applying to interfaces
configuring
matching criteria
logging messages
35-3
34-36
35-3
displaying the MAC address table
learning
removing
36-32
resequencing entries
34-2, 35-2
6-21
17-9
3-15, 6-20
6-22
6-26
multicast
44-3
STP address management
34-2
17-9
static
36-7, 36-43
ACLs (continued)
17-9
group address range
34-2, 35-2
6-26
6-19
MAC, discovering
35-5
precedence of
23-2
default aging
number per QoS class map
41-1
addresses
defined
IPv6
router
40-1
changing the aging time
34-39, 35-9
34-15
QoS
20-2
accelerated aging
34-27, 36-45
34-7, 34-21
IPv4
34-29
dynamic
34-9
named
port
configuring
address aliasing
35-3
Layer 4 information in
34-35
34-30
active traffic monitoring, IP SLAs
unsupported features
monitoring
35-5
active router
35-3
35-3
precedence of
matching
35-3
active links
35-3
MAC extended
IPv6
configuration guidelines
interactions with other features
named
34-7
VLAN maps
35-9
limitations
IPv4
using router ACLs with VLAN maps
35-8
35-4, 35-5
displaying
34-2
unsupported features
34-7
IPv6
and stacking
34-22
34-17
types supported
34-19
34-8
1-9
support in hardware
34-15
numbers
34-10
matching criteria
34-7
matching criteria
names
36-43
34-15
adding and removing
defined
address resolution
6-24
6-19
6-26, 38-10
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
IN-2
OL-12189-01
Index
Address Resolution Protocol
ARP (continued)
See ARP
table
adjacency tables, with CEF
address resolution
38-86
administrative distances
defined
OSPF
managing
ASBRs
38-99
routing protocol defaults
RIP
vendor-proprietary
vendor-specific
26-1
EIGRP
HSRP
12-20, 13-3
aggregatable global unicast addresses
aggregate addresses, BGP
39-4
38-47
40-10
local mode with AAA
7-36
6-4
RADIUS
See EtherChannel
aggregate policers
36-58
aggregate policing
1-11
aging, accelerating
17-9
key
7-21
login
7-23
TACACS+
defined
aging time
key
accelerated
for STP
7-14
See also port-based authentication
18-23
authentication failed VLAN
17-9, 17-23
MAC address table
7-11
7-13
login
for MSTP
See restricted VLAN
6-21
maximum
authentication keys, and routing protocols
for MSTP
for STP
authoritative time source, described
18-24
38-99
6-2
authorization
17-23, 17-24
with RADIUS
30-3
allowed-VLAN list
7-27
with TACACS+
12-22
application engines, redirecting traffic to
area border routers
43-1
7-11, 7-16
authorized ports with IEEE 802.1x
autoconfiguration
See ABRs
9-7
3-3
automatic advise (auto-advise) in switch stacks
ARP
automatic copy (auto-copy) in switch stacks
configuring
defined
7-31
7-29
NTP associations
38-66
aggregated ports
alarms, RMON
16-4
authentication
27-2
38-21
VTP
38-60
attributes, RADIUS
1-2
advertisements
LLDP
38-32
asymmetrical links, and IEEE 802.1Q tunneling
38-88
advanced IP services feature set
CDP
6-26
AS-path filters, BGP
38-38
6-26
5-13
automatic QoS
See QoS
38-12
static cache configuration
5-13
automatic extraction (auto-extract) in switch stacks
38-11
1-6, 6-26, 38-11
encapsulation
5-13
38-11
automatic upgrades (auto-upgrade) in switch stacks
5-13
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
IN-3
Index
auto-MDIX
BGP (continued)
configuring
default configuration
10-19
described
described
10-19
autonegotiation
enabling
duplex mode
interface configuration guidelines
mismatches
38-50
38-53
monitoring
1-4
10-16
38-69
multipath support
38-57
neighbors, types of
47-9
autonomous system boundary routers
See ASBRs
path selection
38-53
38-57
peers, configuring
autonomous systems, in BGP
Auto-RP, described
prefix filtering
38-53
autosensing, port speed
38-61
38-56
route dampening
1-4
auxiliary VLAN
route maps
See voice VLAN
availability, features
38-64
resetting sessions
44-7
38-51
38-68
38-59
route reflectors
38-67
routing domain confederation
1-7
38-66
routing session with multi-VRF CE
show commands
supernets
described
19-7
disabling
19-17
enabling
19-16
support for
Version 4
1-12
38-50
binding database
address, DHCP server
See DHCP, Cisco IOS server database
1-7
DHCP snooping
backup interfaces
See DHCP snooping binding database
See Flex Links
backup links
38-69
38-66
support for
BackboneFast
bindings
20-2
address, Cisco IOS DHCP server
banners
DHCP snooping database
configuring
login
IP source guard
6-18
message-of-the-day login
default configuration
when displayed
6-18
21-7
21-16
binding table, DHCP snooping
blocking packets
6-17
25-6
Boolean expressions in tracked lists
aggregate addresses
clear commands
38-66
boot loader, function of
boot process
38-66
manually
38-69
community filtering
configuring neighbors
38-62
42-4
booting
38-66
aggregate routes, configuring
21-6
See DHCP snooping binding database
6-17
BGP
CIDR
38-80
3-2
3-2
3-19
specific image
3-20
38-64
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
IN-4
OL-12189-01
Index
boot loader
accessing
3-21
described
3-2
cables, monitoring for unidirectional links
environment variables
prompt
CA trustpoint
3-21
configuring
3-21
trap-door mechanism
defined
3-2
bootstrap router (BSR), described
44-7
7-42
CDP
configuring
See BGP
36-39
26-2
default configuration
BPDU
filtering
7-45
and trusted boundary
Border Gateway Protocol
error-disabled state
26-2
defined with LLDP
19-2
described
19-3
RSTP format
28-1
27-1
26-1
disabling for routing device
18-12
26-3 to 26-4
enabling and disabling
BPDU filtering
described
19-3
on an interface
disabling
19-15
on a switch
enabling
19-14
support for
26-4
26-3
Layer 2 protocol tunneling
monitoring
1-7
overview
BPDU guard
16-8
26-5
26-1
described
19-2
support for
disabling
19-14
switch stack considerations
enabling
19-13
transmission timer and holdtime, setting
support for
updates
1-7
bridged packets, ACLs on
1-6
26-2
26-2
CEF
34-37
defined
bridge groups
38-85
distributed
See fallback bridging
IPv6
bridge protocol data unit
38-86
39-20
CGMP
See BPDU
broadcast flooding
as IGMP snooping learning method
38-18
clearing cached group entries
broadcast packets
directed
38-15
enabling server support
44-35
flooded
38-15
joining multicast group
23-3
broadcast storm-control command
broadcast storms
26-2
25-1, 38-15
25-4
overview
44-52
44-9
server support only
switch support of
CIDR
23-9
44-9
1-4
38-66
CipherSuites
7-43
Cisco 7960 IP Phone
14-1
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
IN-5
Index
Cisco Discovery Protocol
CLI (continued)
See CDP
filtering command output
Cisco Express Forwarding
getting help
See CEF
2-10
2-3
history
Cisco Group Management Protocol
changing the buffer size
See CGMP
Cisco IOS DHCP server
See DHCP, Cisco IOS DHCP server
Cisco IOS File System
described
2-6
disabling
2-7
recalling commands
client mode, VTP
1-3
See also stacks, switch
42-1
clock
See system clock
CNS
1-5, 32-4
CIST regional root
Configuration Engine
See MSTP
configID, deviceID, hostname
CIST root
configuration service
See MSTP
civic location
described
described
class maps for QoS
displaying
4-5
enabling configuration agent
enabling event agent
36-46
management functions
36-7
4-6
4-9
4-7
1-5
command-line interface
36-78
class of service
See CLI
See CoS
command modes
clearing interfaces
2-1
commands
10-25
CLI
abbreviating
abbreviating commands
command modes
2-4
commands, setting privilege levels
community list, BGP
2-5
community ports
1-5
editing features
7-8
38-63
15-2
community strings
enabling and disabling
keystroke editing
wrapped lines
error messages
2-4
no and default
2-4
2-1
configuration logging
described
4-3
enabling automated configuration
38-9
configuring
4-2
embedded agents
See CIDR
classless routing
4-3
4-1
event service
27-3
classless interdomain routing
described
2-4
13-3
client processes, tracking
41-1
Cisco StackWise Plus technology
CiscoWorks 2000
2-6
no and default forms of commands
See IFS
Cisco IOS IP SLAs
2-6
2-5
2-9
2-8
2-7
configuring
overview
32-8
32-4
community VLANs
compatibility, feature
15-2, 15-3
25-11
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
IN-6
OL-12189-01
Index
compatibility, software
configuration guidelines, multi-VRF CE
See stacks, switch
config.text
configuration logging
configurable leave timer, IGMP
configuration rollback
23-6
configuration, initial
defaults
B-20
B-20
configuration settings, saving
1-14
Express Setup
1-3
configuration examples, network
10-8
configuring multicast VRFs
38-78
2-2, 12-7
connections, secure remote
connectivity problems
B-20
3-17
configure terminal command
config-vlan mode
1-16
configuration files
archiving
2-5
configuration replacement
3-18
7-37
47-10, 47-11, 47-13
clearing the startup configuration
B-20
consistency checks in VTP Version 2
creating and using, guidelines for
B-10
console port, connecting to
creating using a text editor
default name
2-11
See WCCP
3-18
control protocol, IP SLAs
B-20
41-4
corrupted software, recovery steps with Xmodem
B-9
downloading
in Layer 2 frames
3-18
override priority
B-11, B-14, B-17
14-6
B-9
using FTP
B-14
CoS input queue threshold map for QoS
using RCP
B-18
CoS output queue threshold map for QoS
using TFTP
trust priority
36-2
reasons for
B-12
invalid combinations when copying
limiting TFTP server access
obtaining with DHCP
B-6
7-5
replacing and rolling back, guidelines for
B-21
replacing a running configuration
B-20, B-21
rolling back a running configuration
B-20, B-21
B-10
uploading
B-11, B-14, B-17
counters, clearing interface
10-25
32-15
configuration guidelines
9-37
37-12
configuring
on Layer 2 interfaces
described
37-12
37-15
37-2
illustration
37-3
support for
1-7
cross-stack UplinkFast, STP
B-9
described
19-5
using FTP
B-15
disabling
19-16
using RCP
B-19
enabling
19-16
B-12
36-19
cross-stack EtherChannel
reasons for
using TFTP
36-16
47-20
on Layer 3 physical interfaces
3-18
system contact and location information
types and location
36-60
critical authentication, IEEE 802.1x
3-7
specifying the filename
14-6
CoS-to-DSCP map for QoS
crashinfo file
32-15
password recovery disable considerations
preparing
47-2
CoS
automatically
preparing
13-4
content-routing technology
B-11
deleting a stored configuration
described
38-73
fast-convergence events
19-7
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
IN-7
Index
cross-stack Uplink Fast, STP (continued)
default configuration (continued)
Fast Uplink Transition Protocol
IEEE 802.1Q tunneling
normal-convergence events
support for
19-6
IGMP
19-7
cryptographic software image
Kerberos
SSL
44-30
IGMP filtering
1-7
7-32
7-42
switch stack considerations
customer edge devices
5-2, 5-18, 7-38
23-25
IGMP snooping
23-7, 24-6
IGMP throttling
23-25
initial switch information
3-3
IP addressing, IP routing
38-7
IP multicast routing
38-71
IP SLAs
IPv6
daylight saving time
dCEF in the switch stack
LLDP
enabling all system diagnostics
enabling for a specific feature
47-17
47-16
redirecting error message output
default commands
47-17
47-16
802.1x
banners
CDP
DHCP
MSDP
45-4
MSTP
18-15
OSPF
6-17
PIM
RADIUS
21-8
DHCP snooping
21-8
RMON
30-3
RSPAN
29-11
38-43
fallback bridging
20-5
22-5
SNMP
32-6
SPAN
29-11
SSL
37-10
Ethernet interfaces
40-5
38-22
SDM template
6-16
dynamic ARP inspection
HSRP
21-9
15-6
7-20
RIP
DHCP snooping binding database
10-15
46-4
8-4
7-44
standard QoS
STP
7-2
44-11
private VLANs
26-2
19-12
38-32
password and privilege level
3-18
Flex Links
38-73
optional spanning-tree configuration
36-21
EtherChannel
20-5
6-4
21-8
EIGRP
6-21
23-20
DHCP option 82
DNS
16-11
MAC address-table move update
NTP
38-51
booting
MAC address table
MVR
9-23
auto-QoS
10-15
27-3
multi-VRF CE
2-4
default configuration
BGP
39-15
Layer 2 protocol tunneling
38-85
debugging
using commands
21-17
Layer 2 interfaces
6-13
44-11
41-6
IP source guard
16-4
36-30
17-13
switch stacks
5-21
system message logging
31-4
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
IN-8
OL-12189-01
Index
default configuration (continued)
system name and prompt
TACACS+
UDLD
DHCP-based autoconfiguration
client request message exchange
6-15
configuring
7-13
client side
28-4
VLAN, Layer 2 Ethernet interfaces
VLANs
12-8
VMPS
12-30
VTP
DNS
12-20
14-3
3-6
3-7
server side
3-5
server-side
21-10
TFTP server
13-7
WCCP
3-4
relay device
voice VLAN
example
43-5
default gateway
38-89
default routing
38-4
deleting VLANs
overview
description command
relay support
25-1
support for
10-20
designing your network, examples
1-6, 1-12
1-6
configuring
3-11 to 3-14
destination addresses
understanding
in IPv4 ACLs
34-12
DHCP binding database
in IPv6 ACLs
35-6
3-10
See DHCP snooping binding database
destination-IP address-based forwarding,
EtherChannel 37-8
destination-MAC address forwarding, EtherChannel
detecting indirect link failures, STP
26-1, 27-1
device manager
described
19-8
DHCP binding table
See DHCP snooping binding database
37-8
DHCP option 82
circuit ID suboption
displaying
1-3, 1-5
21-9
21-8
21-15
forwarding address, specifying
in-band management
1-6
helper address
DHCP
overview
Cisco IOS server database
21-6
21-11
21-11
21-3
packet format, suboption
21-14
default configuration
described
21-5
configuration guidelines
default configuration
1-3
configuring
3-4
DHCP-based autoconfiguration and image update
1-16
5-11
device discovery protocol
3-5
3-3
relationship to BOOTP
denial-of-service attack
benefits
3-5
for receiving the configuration file
12-10
desktop template
3-8
for IP address information
38-89
default routes
3-6
lease options
3-14, 38-13
default networks
3-4
21-9
circuit ID
21-5
remote ID
21-5
remote ID suboption
21-5
enabling
relay agent
server
21-11
21-10
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
IN-9
Index
DHCP snooping
DHCP snooping binding database (continued)
accepting untrusted packets form edge switch
21-3,
resetting
21-13
delay value
and private VLANs
21-14
timeout value
binding database
configuration guidelines
default configuration
21-9
option 82 data insertion
trusted interface
Differentiated Services Code Point
21-4
directed unicast requests
21-2
untrusted messages
21-2
changing
DHCP snooping binding database
21-14
21-15
binding file
B-5
displaying the working
B-4
See DVMRP
configuring
38-98
and DHCP-based autoconfiguration
21-15
default configuration
21-10
in IPv6
default configuration
21-8, 21-9
deleting
binding file
21-15
database agent
21-15
6-15
setting up
6-16
1-6
DNS
6-15
VTP
13-8
Domain Name System
21-15
status and statistics
21-14
See DNS
21-15
displaying status and statistics
dot1q-tunnel switchport mode
21-15
12-18
double-tagged packets
IEEE 802.1Q tunneling
21-7
renewing database
overview
domain names
21-15
21-6
binding entries
6-17
39-5
support for
21-15
3-6
6-16
displaying the configuration
21-14
bindings
38-4
DNS
21-7
configuration guidelines
entry
creating and removing
distribute-list command
21-7
clearing agent statistics
enabling
B-4
distance-vector protocols
21-7
displaying
1-6
Distance Vector Multicast Routing Protocol
binding entries, displaying
location
38-41
directories
untrusted interface
format
36-2
36-2
Diffusing Update Algorithm (DUAL)
21-3
21-2
adding bindings
48-2
Differentiated Services architecture, QoS
21-15
message exchange process
See DHCP snooping binding database
diagnostic schedule command
21-8
displaying binding tables
described
21-15
DHCP snooping binding table
See DHCP snooping binding database
bindings
21-15
16-2
Layer 2 protocol tunneling
16-10
21-15
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
IN-10
OL-12189-01
Index
downloading
DVMRP (continued)
configuration files
preparing
interoperability
with Cisco devices
B-11, B-14, B-17
reasons for
B-9
using FTP
B-14
mrinfo requests, responding to
using RCP
B-18
neighbors
using TFTP
with Cisco IOS software
B-12
image files
deleting old image
preparing
reasons for
B-24
using CMS
1-3
using FTP
B-31
using RCP
advertising all
44-46
44-51
44-51
advertising the default route to neighbors
B-27
DSCP input queue threshold map for QoS
16-11
changing the threshold for syslog messages
36-19
44-53
favoring one over another
44-51
limiting the number injected into MBONE
DSCP-to-DSCP-mutation map for QoS
limiting unicast route advertisements
36-64
routing table
36-39
dual IPv4 and IPv6 templates
support for
38-42
44-40
44-9
1-12
tunnels
8-2, 39-14
dual protocol stacks
configuring
44-42
displaying neighbor information
39-18
44-44
dynamic access ports
39-13
SDM templates supporting
characteristics
39-14
DVMRP
configuring
autosummarization
defined
configuring a summary address
12-4
12-31
10-3
dynamic addresses
44-49
See addresses
44-51
connecting PIM domain to DVMRP router
enabling unicast routing
44-48
44-9
source distribution tree, building
1-8, 12-18
44-48
44-52
displaying
36-63
DUAL finite state machine, EIGRP
44-43
caching DVMRP routes learned in report
messages 44-45
36-16
DSCP output queue threshold map for QoS
IPv4 and IPv6
44-47
44-9
deleting
DSCP transparency
44-44
adding a metric offset
1-11, 36-2
disabling
44-40
routes
drop threshold for Layer 2 protocol packets
configuring
discovery with Probe messages
overview
using the device manager or Network
Assistant B-24
DTP
44-43
rejecting nonpruning
1-3, B-24
DSCP-to-CoS map for QoS
44-44
prevent peering with nonpruning
B-36
using TFTP
44-9
advertising the default route to
displaying information
B-29
B-26, B-30, B-35
using HTTP
DSCP
44-40
44-45
44-42
dynamic ARP inspection
ARP cache poisoning
22-1
ARP requests, described
22-1
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
IN-11
Index
dynamic ARP inspection (continued)
ARP spoofing attack
dynamic ARP inspection (continued)
statistics
22-1
clearing
clearing
log buffer
statistics
displaying
22-15
22-15
validation checks, performing
22-15
configuration guidelines
dynamic auto trunking mode
22-6
configuring
in DHCP environments
log buffer
12-18
Dynamic Host Configuration Protocol
22-8
See DHCP-based autoconfiguration
22-7
dynamic port VLAN membership
22-12
rate limit for incoming ARP packets
default configuration
described
22-4, 22-10
12-29
reconfirming
22-5
denial-of-service attacks, preventing
12-32
troubleshooting
22-10
12-33
types of connections
22-1
DHCP snooping binding database
dynamic routing
22-2
displaying
12-31
38-4
Dynamic Trunking Protocol
ARP ACLs
See DTP
22-14
configuration and operating state
log buffer
statistics
22-14
22-15
22-15
trust state and rate limit
22-14
EBGP
error-disabled state for exceeding rate limit
function of
22-11
12-18
dynamic desirable trunking mode
ACLs for non-DHCP environments
described
22-15
22-4
editing features
22-2
enabling and disabling
interface trust states
22-3
keystrokes used
log buffer
clearing
wrapped lines
22-15
configuring
displaying
22-12
22-15
22-5
22-2
network security issues and interface trust states
priority of ARP ACLs and DHCP snooping
entries 22-4
rate limiting of ARP packets
22-10
2-9
38-47
components
38-42
configuring
38-45
default configuration
22-3
definition
38-41
monitoring
38-48
support for
1-12
38-46
39-8
EIGRP stub routing
22-4
38-43
interface parameters, configuring
EIGRP IPv6
22-4
error-disabled state
2-8
authentication
man-in-the middle attack, described
configuring
2-7
EIGRP
logging of dropped packets, described
described
38-49
38-29
elections
See stack master
ELIN location
27-3
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
IN-12
OL-12189-01
Index
enable password
EtherChannel (continued)
7-3
enable secret password
LACP
7-3
encryption, CipherSuite
described
7-44
encryption for passwords
displaying status
7-3
Enhanced IGRP
commands
modes
Layer 3 interface
IP routing state
load balancing
42-2
line-protocol state
37-7, 37-17
aggregate-port learners
environment variables, function of
37-4
described
37-22
interaction with other features
2-5
EtherChannel
37-18
37-5
displaying status
19-2
error messages during command entry
37-18
compatibility with Catalyst 1900
3-22
1-12, 38-87
error-disabled state, BPDU
37-6
learn method and priority configuration
automatic creation of
modes
37-5, 37-6
channel groups
numbering of
37-4
configuration guidelines
port groups
37-10
37-2
displaying status
37-22
forwarding methods
37-7, 37-17
IEEE 802.3ad, described
interaction
with STP
37-11
with VLANs
37-12
37-6
support for
37-15
Layer 3 port-channel logical interfaces
default configuration
37-4
10-5
stack changes, effects of
37-12
Layer 3 physical interfaces
37-4
numbering of
37-11
configuring
Layer 2 interfaces
1-4
port-channel interfaces
described
37-4
37-14
37-18
37-5
support for
binding physical and logical interfaces
described
38-6
PAgP
42-2
42-3
equal-cost routing
37-20
logical interfaces, described
42-9
tracked lists
37-21
system priority
42-7
37-7
37-6
port priority
42-1
42-1
IP SLAs
37-19
interaction with other features
enhanced object tracking
HSRP
37-22
hot-standby ports
See EIGRP
defined
37-6
37-9
1-4
EtherChannel guard
described
19-10
disabling
19-17
enabling
19-17
Ethernet management port, internal
and routing
10-13
configuring
10-14
default setting
described
10-13
10-12
Layer 3 routing guidelines
supported features
unsupported features
10-14
10-13
10-14
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
IN-13
Index
Ethernet VLANs
adding
fallback bridging
and protected ports
12-9
defaults and ranges
modifying
EUI
bridge groups
12-8
creating
12-9
30-3
examples
network configuration
expedite queue for QoS
Express Setup
46-5
46-5
46-11
46-11
configuration guidelines
46-4
connecting interfaces with
12-13
default configuration
12-12
described
creating with an internal VLAN ID
10-7
46-4
46-1
frame forwarding
12-15
flooding packets
12-1
extended system ID
MSTP
46-2
displaying
12-14
defined
function of
clearing
47-20
configuration guidelines
creating
46-11
bridge table
extended-range VLANs
configuring
displaying
removing
36-76
1-3
extended crashinfo file
46-2
number supported
1-16
See also getting started guide
STP
46-4
described
39-4
events, RMON
46-4
46-2
forwarding packets
overview
18-18
46-2
46-1
protocol, unsupported
17-4, 17-16
extended universal identifier
46-4
stack changes, effects of
See EUI
46-3
STP
Extensible Authentication Protocol over LAN
external BGP
9-1
disabling on an interface
forward-delay interval
See EBGP
hello BPDU interval
external neighbors, BGP
38-53
interface priority
46-10
46-9
46-8
46-7
keepalive messages
17-2
maximum-idle interval
path cost
46-9
46-7
VLAN-bridge spanning-tree priority
Fa0 port
See Ethernet management port, internal
failover support
1-7
VLAN-bridge STP
support for
46-6
46-2
1-12
SVIs and routed ports
46-1
unsupported protocols
46-4
VLAN-bridge STP
17-11
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
IN-14
OL-12189-01
Index
fastethernet0 port
Flex Links
See Ethernet management port, internal
Fast Uplink Transition Protocol
features, incompatible
FIB
configuration guidelines
configuring
19-6
20-6
configuring preferred VLAN
25-11
fiber-optic, detecting unidirectional links
default configuration
28-1
files
description
basic crashinfo
location
monitoring
47-20
VLANs
47-20
crashinfo, description
20-5
20-2
20-11
20-2
flooded traffic, blocking
B-5
25-7
flow-based packet classification
47-20
20-8
20-1
link load balancing
description
deleting
20-9
configuring VLAN load balancing
38-86
copying
20-5
1-11
flowcharts
B-6
displaying the contents of
QoS classification
B-8
36-6
extended crashinfo
QoS egress queueing and scheduling
description
QoS ingress queueing and scheduling
location
47-20
QoS policing and marking
47-20
tar
36-17
36-15
36-10
flowcontrol
creating
configuring
B-7
displaying the contents of
extracting
described
B-7
10-18
forward-delay time
B-8
image file format
MSTP
B-25
file system
STP
displaying available file systems
displaying file information
local file system names
18-23
17-23
Forwarding Information Base
B-2
See FIB
B-3
forwarding nonroutable protocols
B-1
network file system names
setting the default
10-18
FTP
B-5
accessing MIB files
B-3
filtering
A-4
configuration files
in a VLAN
34-29
downloading
IPv6 traffic
35-4, 35-8
overview
non-IP traffic
46-1
B-13
preparing the server
34-27
show and more command output
filters, IP
uploading
2-10
filtering show and more command output
2-10
image files
downloading
B-1
B-14
B-15
deleting old image
See ACLs, IP
flash device, number of
B-14
B-31
preparing the server
uploading
B-33
B-30
B-33
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
IN-15
Index
HSRP
authentication string
40-10
get-bulk-request operation
32-3
command-switch redundancy
get-next-request operation
32-3, 32-4
configuring
get-request operation
32-3, 32-4
get-response operation
global configuration mode
global leave, IGMP
2-2
23-13
definition
40-1
guidelines
40-5
monitoring
guest VLAN and IEEE 802.1x
guide mode
40-4
default configuration
32-3
9-13
overview
GUIs
priority
See device manager and Network Assistant
40-5
40-11
object tracking
1-3
1-2, 1-7
42-7
40-1
40-7
routing redundancy
1-12
support for ICMP redirect messages
switch stack considerations
timers
hardware limitations and Layer 3 interfaces
40-7
HTTP over SSL
hello time
MSTP
STP
40-4
40-10
tracking
10-21
40-11
see HTTPS
18-22
HTTPS
17-22
help, for the command line
hierarchical policy maps
described
described
36-8
configuration guidelines
configuring
configuring
2-3
7-42
self-signed certificate
36-32
HTTP secure server
36-52
changing the buffer size
7-42
2-6
described
2-6
IBPG
disabling
2-7
ICMP
recalling commands
2-6
38-49
IPv6
history table, level and number of syslog messages
host ports
31-10
39-5
redirect messages
support for
configuring
15-11
hosts, limit on dynamic ports
Hot Standby Router Protocol
See HSRP
38-13
1-12
time-exceeded messages
15-2
HP OpenView
7-43
36-11
history
kinds of
7-45
traceroute and
12-33
47-13
unreachable messages
34-20
unreachable messages and IPv6
unreachables and ACLs
1-5
47-13
35-5
34-22
ICMP Echo operation
configuring
IP SLAs
41-12
41-11
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
IN-16
OL-12189-01
Index
ICMP ping
IGMP
executing
47-10
overview
47-10
configurable leave timer
ICMP Router Discovery Protocol
See IRDP
ICMPv6
23-12
44-30
statically connected member
and ingress RSPAN
and ingress SPAN
controlling access to groups
29-21
29-14
IEEE 802.1D
See STP
default configuration
44-30
deleting cache entries
44-53
displaying groups
fast switching
14-1
IEEE 802.1Q
44-35
global leave
12-16
12-24
tunneling
23-13
query solicitation
23-13
host-query interval, modifying
joining multicast group
16-4
join messages
16-1
tunnel ports with other features
IEEE 802.1s
16-6
leave processing, enabling
overview
See RSTP
queries
IEEE 802.1x
44-32
23-3
multicast reachability
IEEE 802.1w
23-13
23-3
leaving multicast group
See MSTP
23-11, 24-9
23-5
44-30
44-3
23-4
report suppression
See port-based authentication
IEEE 802.3ad
See EtherChannel
described
23-6
disabling
23-16, 24-11
supported versions
IEEE 802.3x flow control
ifIndex values, SNMP
16-6
23-13
23-14
recovering from flood mode
compatibility with other features
described
44-53
disabling on an interface
12-19
native VLAN for untagged traffic
defaults
44-31
controlling the length of time
10-3
configuration limitations
encapsulation
44-34
flooded multicast traffic
and trunk ports
1-6
enabling
as a member of a group
IDS appliances
IFS
23-6
configuring the switch
39-5
IEEE 802.1p
described
10-18
32-5
support for
23-3
1-4
Version 1
changing to Version 2
described
44-32
44-3
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
IN-17
Index
IGMP (continued)
IGMP snooping (continued)
Version 2
querier
changing to Version 1
described
configuring
44-3
maximum query response time value
pruning groups
support for
23-3
1-4
VLAN configuration
44-33
IGMP filtering
23-14
23-14
supported versions
44-34
44-34
query timeout value
23-8
IGMP throttling
configuring
configuring
23-25
default configuration
described
23-29
support for
1-5
23-28
default configuration
23-25
described
23-24
monitoring
IGP
23-25
23-25
displaying action
IGMP groups
23-29
38-31
Immediate Leave, IGMP
configuring filtering
IGMP helper
described
23-28
setting the maximum number
23-27
23-6
enabling
23-11
enabling
23-12
defaults
configuration mode
23-25
10-10
interface command
10-7 to 10-8
interface configuration mode
23-26
IGMP snooping
2-3
interfaces
and address aliasing
and stack changes
configuring
23-2
IPv4 and IPv6
23-7
23-7, 24-6
enabling and disabling
global configuration
in the switch stack
procedure
23-8, 24-7
23-8
23-6
23-7
23-9
23-16, 24-12
10-19
39-18
10-8
counters, clearing
23-2
Immediate Leave
auto-MDIX, configuring
configuring
23-7
default configuration
monitoring
10-7
range macros
23-27
definition
1-3
interface
number
configuring
9-15
1-14
Express Setup
IGMP profile
applying
24-9
initial configuration
configuration guidelines
described
23-6
inaccessible authentication bypass
44-6
IGMP Immediate Leave
method
configuration guidelines
44-32
10-25
default configuration
described
10-15
10-20
descriptive name, adding
10-20
displaying information about
10-24
duplex and speed configuration guidelines
flow control
10-18
management
1-5
monitoring
10-16
10-24
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
IN-18
OL-12189-01
Index
interfaces (continued)
naming
IP addresses
128-bit
10-20
physical, identifying
range of
discovering
10-25
10-17
10-10
1-2
IP broadcast address
38-17
ip cef distributed command
10-7
Interior Gateway Protocol
IP directed broadcasts
See IGP
38-86
38-16
ip igmp profile command
internal BGP
38-10
38-19
IP base feature set
interfaces range macro command
23-25
IP information
See IBGP
assigned
internal neighbors, BGP
manually
38-53
Internet Control Message Protocol
3-14
through DHCP-based autoconfiguration
See ICMP
default configuration
Internet Group Management Protocol
See IGMP
3-3
3-3
IP multicast routing
addresses
Internet Protocol version 6
all-hosts
See IPv6
44-3
all-multicast-routers
Inter-Switch Link
44-3
host group address range
See ISL
44-3
administratively-scoped boundaries, described
inter-VLAN routing
1-12, 38-3
Intrusion Detection System
and IGMP snooping
27-6
IP ACLs
benefits of
34-10, 34-14
implicit masks
34-15
undefined
36-7
34-21
34-10
44-18
44-17
clearing the cache
implicit deny
23-2
adding to an existing sparse-mode cloud
inventory management TLV
for QoS classification
44-37
Auto-RP
See IDS appliances
named
39-3
monitoring
10-7
10-1
interface types
38-6
MAC address association
10-24
types of
IPv6
38-7
6-26
for IP routing
10-25
speed and duplex, configuring
supported
38-8
default configuration
shutting down
status
classes of
10-7
10-9
restarting
39-3
44-53
configuration guidelines
44-12
filtering incoming RP announcement
messages 44-19
overview
44-7
preventing candidate RP spoofing
44-19
preventing join messages to false RPs
setting up in a new internetwork
using with BSR
44-19
44-17
44-25
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
IN-19
Index
IP multicast routing (continued)
IP multicast routing (continued)
bootstrap router
routing table
configuration guidelines
deleting
44-12
configuring candidate BSRs
configuring candidate RPs
44-53
RP
44-24
defining the IP multicast boundary
overview
displaying
44-23
defining the PIM domain border
44-53
44-22
assigning manually
44-16
configuring Auto-RP
44-21
44-17
configuring PIMv2 BSR
44-7
using with Auto-RP
Cisco implementation
44-21
monitoring mapping information
44-25
using Auto-RP and BSR
44-2
configuring
44-26
44-25
stacking
basic multicast routing
IP multicast boundary
default configuration
stack master functions
44-12
44-10
stack member functions
44-37
44-10
statistics, displaying system and network
44-11
enabling
44-53
See also CGMP
multicast forwarding
PIM mode
See also DVMRP
44-13
See also IGMP
44-14
group-to-RP mappings
Auto-RP
BSR
See also PIM
IP phones
44-7
and QoS
44-7
MBONE
14-1
automatic classification and queueing
deleting sdr cache entries
described
configuring
44-53
displaying sdr cache
trusted boundary for QoS
44-54
enabling sdr listener support
IP precedence
44-37
limiting DVMRP routes advertised
limiting sdr cache entry lifetime
44-48
Session Directory (sdr) tool, described
monitoring
packet rate loss
44-54
peering devices
44-54
36-2
IP-precedence-to-DSCP map for QoS
in ACLs
36-61
routing
44-36
34-12
1-12
IP protocols in ACLs
34-12
IP routes, monitoring
38-101
connecting interfaces with
44-54
44-8
PIMv1 and PIMv2 interoperability
44-2
reverse path check (RPF)
36-38
IP routing
multicast forwarding, described
protocol interaction
36-38
IP protocols
44-37
SAP packets for conference session
announcement 44-36
tracing a path
14-4
ensuring port security with QoS
44-36
36-20
44-11
disabling
38-20
enabling
38-20
10-6
IP Service Level Agreements
See IP SLAs
44-8
IP service levels, analyzing
IP services feature set
41-1
1-2
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
IN-20
OL-12189-01
Index
IP SLAs
IP source guard (continued)
benefits
default configuration
41-2
configuration guidelines
41-6
configuring object tracking
Control Protocol
21-19
enabling
41-11
measuring network performance
41-3
object tracking
41-5
21-18
filtering
source IP and MAC address
adding
described
response time
21-19
IP traceroute
41-4
41-5
SNMP support
supported metrics
executing
47-14
overview
47-13
IP unicast routing
41-2
address resolution
41-2
threshold monitoring
41-6
UDP jitter operation
38-10
administrative distances
ARP
42-9
38-11
authentication keys
and DHCP snooping
and EtherChannels
21-16
21-18
21-18
packets
and port security
21-17
storms
21-17
binding configuration
binding table
38-15
38-9
38-88
default
addressing configuration
21-18
manual
38-15
configuring static routes
21-17
and trunk interfaces
38-18
classless routing
21-18
38-99
38-17
flooding
and IEEE 802.1x
and private VLANs
21-16
21-16
21-16
configuration guidelines
21-17
38-8
broadcast
address
21-18
and hardware entries
38-88, 38-99
assigning IP addresses to Layer 3 interfaces
41-8
IP source guard
and routed ports
21-17
21-18
deleting
41-4
41-8
automatic
21-16
static bindings
42-9
responder
track state
21-17
source IP and MAC address filtering
reachability tracking
scheduling
21-16
source IP address filtering
42-9
41-3
enabling
21-19
source IP address
41-14
multioperations scheduling
and VRF
21-19
configuration
ICMP echo operation
operation
disabling
bindings
41-6
41-1
monitoring
21-16
displaying
41-4
default configuration
definition
42-9
described
21-17
gateways
38-13
networks
38-89
routes
38-89
routing
38-4
directed broadcasts
38-7
38-16
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
IN-21
Index
IP unicast routing (continued)
disabling
IPv4 ACLs
applying to interfaces
38-20
dynamic routing
enabling
extended, creating
38-4
named
38-20
EtherChannel Layer 3 interface
IGP
38-6
inter-VLAN
classes
39-18
39-2
39-7
IPv6
38-6
ACLs
39-4
38-14
38-6
MAC address and IP address
passive interfaces
38-10
displaying
35-9
limitations
35-3
matching criteria
port
38-97
protocols
dynamic
reverse address resolution
38-10
38-6
subnet mask
39-16
autoconfiguration
39-6
39-20
default configuration
defined
38-9
See also BGP
See also EIGRP
See also OSPF
See also RIP
1-13, 38-85
39-21
39-15
39-1
enabling
38-17
unicast reverse path forwarding
39-7
configuring static routes
38-8
38-6
39-7
assigning address
CEFv6
38-6
38-8
subnet zero
39-12
autogenerated address
38-4
steps to configure
39-3
applications
38-89
static routing
39-3
and switch stacks
38-11
routed ports
35-2
advantages
38-4
redistribution
35-3
address formats
38-4
link-state
proxy ARP
router
38-4
35-3
35-2
precedence
distance-vector
with SVIs
34-10
dual protocol stacks
38-8
Layer 3 interfaces
UDP
standard, creating
differences
configuring
supernet
34-15
configuring on an interface
38-3
IP addressing
IRDP
34-11
IPv4 and IPv6
38-31
IPv6
34-20
39-16
Enhanced Interior Gateway Routing Protocol (EIGRP)
IPv6
described
39-8
EIGRP IPv6 commands
passive interfaces
prefix lists
router ID
39-9
39-9
39-9
feature limitations
39-12
features not supported
ICMP
39-9
39-11
39-5
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
IN-22
OL-12189-01
Index
IPv6 (continued)
Kerberos
ICMP rate limiting
link-local address
monitoring
KDC
39-27
7-34
configuration examples
39-25
configuring
39-5
router advertisements
SDM templates
described
8-2, 24-1, 35-1, 39-1, 39-13
7-32
KDC
39-13
7-32
39-4
operation
switch limitations
39-12
realm
7-33
server
7-33
35-4
IRDP
terms
TGT
1-12
ISL
7-34
See KDC
10-3
1-8, 12-16
trunking with IEEE 802.1 tunneling
15-2
isolated VLANs
7-32
key distribution center
39-4
and trunk ports
isolated port
7-32
7-33
tickets
encapsulation
1-10
switch as trusted third party
38-14
38-14
support for
and IPv6
7-34
support for
configuring
7-32
7-32
supported features
IPv6 traffic, filtering
7-32
cryptographic software image
39-7
stack master functions
7-35
7-35
credentials
39-23
definition
7-34
network services
39-5
path MTU discovery
RIP
boundary switch
39-6
neighbor discovery
OSPF
authenticating to
39-19
15-2, 15-3
16-5
L
l2protocol-tunnel command
16-13
LACP
Layer 2 protocol tunneling
16-9
See EtherChannel
join messages, IGMP
23-3
Layer 2 frames, classification with CoS
Layer 2 interfaces, default configuration
36-2
10-15
Layer 2 protocol tunneling
configuring
configuring for EtherChannels
KDC
described
16-10
default configuration
7-32
See also Kerberos
keepalive messages
17-2
defined
16-14
16-11
16-8
guidelines
16-12
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
IN-23
Index
Layer 2 traceroute
LLDP
and ARP
47-12
and CDP
47-12
configuring
characteristics
broadcast traffic
described
default configuration
47-11
globally
47-11
IP addresses and subnets
unicast traffic
globally
Layer 3 features
overview
47-12
27-2
switch stack considerations
assigning IPv4 and IPv6 addresses to
39-18
38-8, 38-76, 38-77
27-3
configuring TLVs
Layer 3 packets, classification methods
36-2
overview
LEDs, switch
27-2
LLDP Media Endpoint Discovery
See hardware installation guide
See LLDP-MED
Lightweight Directory Access Protocol
load balancing
See LDAP
local SPAN
line configuration mode
40-3
29-2
location TLV
2-3
Link Aggregation Control Protocol
27-3, 27-6
logging messages, ACL
See EtherChannel
34-9
login authentication
Link Failure, detecting unidirectional
Link Layer Discovery Protocol
18-8
with RADIUS
login banners
link local unicast addresses
7-23
with TACACS+
See CDP
7-14
6-17
log messages
39-4
link redundancy
See system message logging
See Flex Links
links, unidirectional
Long-Reach Ethernet (LRE) technology
link-state protocols
38-4
link-state tracking
1-18
loop guard
28-1
link state advertisements (LSAs)
described
27-7
27-1, 27-2
supported TLVs
4-2
configuring
27-6
monitoring and maintaining
38-6
27-4
LLDP-MED
configuring
39-16
changing from Layer 2 mode
27-2
transmission timer and holdtime, setting
38-8
assigning IPv6 addresses to
27-7
27-1
supported TLVs
1-12
assigning IP addresses to
LDAP
27-5
monitoring and maintaining
Layer 3 interfaces
types of
27-4
on an interface
47-12
47-11
usage guidelines
27-5
disabling and enabling
47-12
47-12
multiple devices on a port
27-3
27-4
on an interface
47-12
MAC addresses and VLANs
multicast traffic
27-4
38-37
described
enabling
support for
19-11
19-18
1-8
37-24
37-22
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
IN-24
OL-12189-01
Index
manageability features
1-6
management access
MAC addresses
in-band
aging time
6-21
browser session
and VLAN association
6-20
building the address table
default configuration
discovering
displaying
CLI session
6-20
6-21
SNMP
1-6
dynamic
21-19
CLI
2-1
CNS
6-20
4-1
Network Assistant
6-22
overview
34-27
38-10
manually assigning IP address
1-3
1-5
switch stacks
IP address association
1-3
mapping tables for QoS
3-15
configuring
static
CoS-to-DSCP
adding
6-24
allowing
DSCP
6-26
36-60
36-60
DSCP-to-CoS
characteristics of
6-24
36-63
DSCP-to-DSCP-mutation
dropping
6-25
IP-precedence-to-DSCP
removing
6-24
policed-DSCP
MAC address notification, support for
1-13
MAC address-table move update
configuration guidelines
configuring
described
action in policy map
20-5
described
matching IPv4 ACLs
monitoring
20-11
maximum aging time
MAC address-to-VLAN mapping
12-28
MAC extended access lists
36-45
for QoS classification
macros
34-28
36-58
34-7
18-24
17-23
maximum hop count, MSTP
maximum-paths command
18-24
38-57, 38-87
MDA
configuration guidelines
36-5
described
9-20 to 9-21
1-9, 9-20
exceptions with authentication process
See Smartports macros
magic packet
MSTP
STP
applying to Layer 2 interfaces
34-27
36-48
36-4, 36-8
20-3
defined
36-62
36-12
description
34-27
36-61
action with aggregate policers
default configuration
creating
36-64
marking
20-5
20-9
configuring for QoS
1-6
management options
displaying in the IP source binding table
in ACLs
1-6
out-of-band console port connection
6-26
removing
1-6
device manager
6-26
learning
1-6
9-18
membership mode, VLAN port
9-4
12-3
messages, to users through banners
6-17
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
IN-25
Index
metrics, in BGP
monitoring (continued)
38-58
metric translations, between routing protocols
metro tags
MHSRP
38-93
MSDP peers
multicast router interfaces
16-2
multi-VRF CE
40-3
MIBs
MVR
accessing files with FTP
location of files
overview
mismatches, autonegotiation
47-9
34-39
45-18
speed and duplex mode
10-17
traffic flowing among switches
28-1
traffic suppression
26-5
tunneling
CEF
38-86
VLAN
fallback bridging
VLANs
1-13
VMPS
20-11
VTP
40-11
IEEE 802.1Q tunneling
12-16
12-33
13-16
benefits of
interfaces
10-24
routes
45-11
originated by switch
45-8
default configuration
44-52
45-13
45-4
dense-mode regions
38-101
IP SLAs operations
forwarded by switch
received by switch
38-19
multicast routing
45-18
controlling source information
23-16, 24-12
address tables
45-3
clearing MSDP connections and statistics
23-29
IP
sending SA messages to
41-14
IPv4 ACL configuration
IPv6
34-40
MSDP
16-18
IGMP
snooping
25-18
34-40
maps
46-11
30-1
16-18
filters
38-48
filters
44-26
source-active messages
CDP
HSRP
15-15
RP mapping information
10-7
cables for unidirectional links
Flex Links
25-18
private VLANs
38-69
features
25-18
protection
monitoring
EIGRP
42-10
38-40
blocking
29-1
29-2
port
32-4
mirroring traffic for analysis
access groups
23-24
OSPF
A-1
module number
38-84
object tracking
32-1
supported
23-17, 24-12
network traffic for analysis with probe
A-4
A-4
SNMP interaction with
BGP
45-18
specifying the originating address
34-39
Layer 2 protocol tunneling
45-17
filtering
39-27
IPv6 ACL configuration
45-16
incoming SA messages
35-9
SA messages to a peer
16-18
MAC address-table move update
20-11
SA requests from a peer
45-14
45-12
45-10
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
IN-26
OL-12189-01
Index
MSDP (continued)
MSTP (continued)
join latency, defined
configuring
45-6
meshed groups
forward-delay time
configuring
defined
hello time
45-15
18-22
link type for rapid convergence
45-15
originating address, changing
overview
maximum aging time
45-17
maximum hop count
45-1
peer-RPF flooding
MST region
45-2
peers
configuring a default
monitoring
path cost
45-4
peering relationship, overview
requesting source information from
shutting down
18-17
secondary root switch
defined
clearing cache entries
18-22
18-3
default configuration
filtering from a peer
filtering incoming
filtering to a peer
18-4
18-15
default optional feature configuration
45-10
displaying status
45-14
18-16
EtherChannel guard
45-13
described
45-18
restricting advertised sources
45-9
enabling
19-10
19-17
extended system ID
1-12
MSTP
effects on root switch
boundary ports
18-18
effects on secondary root switch
configuration guidelines
described
18-16
unexpected behavior
BPDU filtering
implementation
described
19-3
enabling
19-14
terminology
enabling
19-13
18-7
17-10
interface state, blocking to forwarding
interoperability with IEEE 802.1D
18-3
described
18-5
configuration guidelines
19-2
interoperability and compatibility among
modes 17-11
18-3
CIST regional root
18-6
18-5
instances supported
19-2
18-18
port role naming change
BPDU guard
described
18-19
IEEE 802.1s
18-6
CIST, described
19-12
18-26
enabling the mode
45-12
limiting data with TTL
CIST root
18-19
operations between regions
45-18
45-2
support for
18-20
CST
45-6
monitoring
45-8
18-24
18-25
switch priority
45-15
source-active messages
defined
root switch
45-1
18-24
18-21
port priority
45-18
18-24
18-16
neighbor type
caching
18-23
18-15, 19-12
18-9
restarting migration process
18-26
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
IN-27
Index
MSTP (continued)
multicast groups
IST
Immediate Leave
defined
18-3
master
18-3
operations within a region
enabling
19-11
19-18
mapping VLANs to MST instance
18-16
MST region
23-10, 24-8
ACLs on
34-38
blocking
25-7
multicast router interfaces, monitoring
described
23-17, 24-12
23-10, 24-9
Multicast Source Discovery Protocol
configuring
See MSDP
18-16
multicast storm
18-2
hop-count mechanism
25-1
multicast storm-control command
18-5
multicast television application
18-3
supported spanning-tree instances
optional features supported
18-2
multicast VLAN
25-4
23-18
23-18
Multicast VLAN Registration
1-7
See MVR
18-2
Port Fast
multidomain authentication
described
19-2
enabling
19-12
See MDA
multioperations scheduling, IP SLAs
preventing root switch selection
19-10
root guard
enabling
Multiple HSRP
multiple VPN routing/forwarding in customer edge
devices
19-10
19-18
See multi-VRF CE
root switch
configuring
multi-VRF CE
18-18
effects of extended system ID
unexpected behavior
stack changes, effects of
status, displaying
18-26
18-18
18-8
configuration example
19-2
configuring
defined
system routing
10-22
10-22
38-73
38-70
monitoring
10-22
38-73
38-72
default configuration
displaying
MTU
38-80
configuration guidelines
18-18
shutdown Port Fast-enabled port
system jumbo
41-5
See MHSRP
described
system
23-5
multicast router ports, adding
18-3
overview
leaving
multicast packets
described
IST
23-3
static joins
18-3
loop guard
CIST
joining
23-6
38-84
38-84
network components
38-72
packet-forwarding process
support for
38-72
1-12
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
IN-28
OL-12189-01
Index
MVR
Network Assistant
and address aliasing
and IGMPv3
configuring interfaces
default configuration
guide mode
23-22
upgrading a switch
wizards
23-20
5-2, 5-17
B-24
1-3
network configuration examples
23-21
data center
23-24
multicast television application
setting global parameters
support for
1-3
managing switch stacks
23-18
1-3
1-3
management options
23-18
in the switch stack
monitoring
1-5
downloading image files
23-20
23-20
example application
modes
1-3
described
23-21
configuration guidelines
described
benefits
23-20
1-18
expanded data center
23-18
1-18
increasing network performance
23-21
providing network services
1-5
1-17
1-17
small to medium-sized network
1-19
network design
performance
services
NAC
AAA down policy
CDP
9-15, 9-37
IEEE 802.1x validation using RADIUS server
inaccessible authentication bypass
Layer 2 IEEE 802.1x validation
1-10, 9-37
1-10, 9-41
1-10
26-1
RMON
IEEE 802.1x authentication using a RADIUS
server 9-41
Layer 2 IP validation
1-17
network management
1-10
critical authentication
1-17
SNMP
9-41
30-1
32-1
network performance, measuring with IP SLAs
network policy TLV
27-6
Network Time Protocol
See NTP
named IPv4 ACLs
34-15
no commands
named IPv6 ACLs
35-3
nonhierarchical policy maps
NameSpace Mapper
configuring
native VLAN
described
configuring
default
16-4
38-64
Network Admission Control
34-27
12-18
normal-range VLANs
39-5
neighbor discovery/recovery, EIGRP
neighbors, BGP
36-9
nontrunking mode
12-24
12-4
configuration guidelines
38-42
configuration modes
configuring
defined
36-32
36-48
non-IP traffic filtering
12-24
neighbor discovery, IPv6
See NAC
2-4
configuration guidelines
See NSM
and IEEE 802.1Q tunneling
41-3
12-6
12-7
12-4
12-1
no switchport command
10-4
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
IN-29
Index
not-so-stubby areas
online diagnostics
See NSSA
described
48-1
overview
48-1
NSM
4-3
NSSA, OSPF
running tests
38-37
NTP
48-5
Open Shortest Path First
associations
See OSPF
authenticating
defined
optimizing system resources
6-4
options, management
6-2
enabling broadcast messages
peer
area parameters, configuring
configuring
6-5
default configuration
route
restricting access
source IP address, configuring
38-38
described
6-8
for IPv6
6-10
38-32
38-31
39-25
interface parameters, configuring
6-10
LSA group pacing
6-2
support for
38-38
settings
disabling NTP services per interface
stratum
38-35
metrics
6-11
6-2
creating an access group
monitoring
1-6
synchronizing devices
router IDs
6-5
time
synchronizing
virtual links
6-2
38-39
38-40
support for
6-2
38-35
38-40
route summarization
services
38-36
default configuration
6-4
displaying the configuration
overview
1-5
OSPF
6-6
6-5
server
8-1
38-38
1-12
38-38
out-of-profile markdown
1-11
O
P
OBFL
configuring
described
packet modification, with QoS
47-21
PAgP
47-21
displaying
Layer 2 protocol tunneling
47-22
object tracking
HSRP
16-9
See EtherChannel
parallel paths, in routing tables
42-7
IP SLAs
36-19
passive interfaces
42-9
IP SLAs, configuring
monitoring
38-87
configuring
42-9
OSPF
42-10
offline configuration for switch stacks
38-97
38-38
5-9
on-board failure logging
See OBFL
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
IN-30
OL-12189-01
Index
passwords
PIM (continued)
default configuration
7-2
overview
disabling recovery of
7-5
router-query message interval, modifying
encrypting
7-3
for security
overview
1-9
shared tree and source tree, overview
44-26
shortest path tree, delaying the use of
44-28
join messages and shared tree
47-3
setting
overview
enable
enable secret
RPF lookups
7-3
with usernames
STP
44-9
configuration guidelines
7-6
enabling
13-8
path cost
44-5
understanding
18-21
support for
17-20
path MTU discovery
38-26
1-12
versions
39-5
PBR
interoperability
defined
v2 improvements
38-95
fast-switched policy-based routing
local policy-based routing
peers, BGP
38-96
performance, network design
performance features
42-6
1-17
PIM-DVMRP, as snooping method
executing
47-10
overview
47-10
policed-DSCP map for QoS
1-4
persistent self-signed certificate
38-80
PIM
44-11
dense mode
36-48
for more than one traffic class
36-58
36-78
number of
36-33
36-9
policing
44-4
rendezvous point (RP), described
44-5
described
36-4
hierarchical
44-9
displaying neighbors
enabling a mode
36-4
displaying
types of
RPF lookups
36-62
for each matched traffic class
described
10-2
default configuration
47-11
configuring
See PVST+
PE to CE routing, configuring
23-9
policers
7-43
per-VLAN spanning-tree plus
overview
44-4
character output description
percentage thresholds in tracked lists
44-26
ping
38-96
38-64
physical ports
44-11
troubleshooting interoperability problems
38-93
enabling
38-28
38-28, 44-14
overview
MSTP
44-5
stub routing
7-6
VTP domain
44-5
44-5
prune messages
7-3
Telnet
44-29
sparse mode
7-1
recovery of
44-4
44-53
44-14
See hierarchical policy maps
token-bucket algorithm
36-9
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
IN-31
Index
policy-based routing
port-based authentication (continued)
See PBR
configuring (continued)
policy maps for QoS
characteristics of
described
switch-to-client frame-retransmission
number 9-32
36-48
switch-to-client retransmission time
36-7
displaying
default configuration
36-78
hierarchical
described
36-8
configuration guidelines
configuring
described
36-32
36-52
displaying statistics
9-45
EAPOL-start frame
9-5
configuration guidelines
encapsulation
36-32
9-3
configuration guidelines
36-9
described
34-2
types of
34-3
host mode
9-13
9-8
configuring
See EtherChannel
described
port-based authentication
guidelines
9-9
per-user ACLs
9-2
9-24
configuring
802.1x authentication
guest VLAN
9-5
9-26
multiple-hosts mode, described
9-3
configuration guidelines
configuration tasks
9-13
9-12
9-12
ports
9-29
manual re-authentication of a client
periodic re-authentication
authorization state and dot1x port-control
command 9-7
9-37
9-30
authorized and unauthorized
9-30
critical
9-31
9-7
9-15
voice VLAN
9-16
9-29
RADIUS server parameters on the switch
restricted VLAN
9-26
RADIUS server attributes
9-34
RADIUS server
AAA authorization
described
9-26
inaccessible authentication bypass
quiet period
9-26
9-18
method lists
RADIUS server
host mode
9-15
magic packet
9-2
client, defined
9-37
initiation and message exchange
9-9
authentication server
defined
9-14, 9-15
inaccessible authentication bypass
Port Aggregation Protocol
accounting
9-5
guest VLAN
36-48
port ACLs
defined
9-5
EAP-response/identity frame
nonhierarchical on physical ports
described
9-2
EAP-request/identity frame
36-11
configuring
9-23
9-1
device roles
hierarchical on SVIs
9-31
9-28
9-35
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
IN-32
OL-12189-01
Index
port-based authentication (continued)
port security
ports (continued)
protected
and voice VLAN
described
9-18
9-17
interactions
routed
10-4
secure
25-7
static-access
9-17
multiple-hosts mode
9-9
resetting to default values
9-45
stack changes, effects of
statistics, displaying
switch
10-2
trunks
12-3, 12-16
25-16
and private VLANs
9-3
RADIUS client
and stacking
AAA authorization
characteristics
25-12
default configuration
described
9-11
voice VLAN
enabling
9-16
25-18
25-17
on trunk ports
25-13
25-8
PVID
9-16
sticky learning
VVID
9-16
violations
wake-on-LAN, described
port blocking
25-10
port-shutdown response, VMPS
1-4, 25-6
port-channel
power management TLV
See EtherChannel
12-29
27-6
preemption, default configuration
Port Fast
20-5
preemption delay, default configuration
described
19-2
enabling
19-12
support for
See QoS
12-3
primary links
15-1, 15-3
priority
HSRP
17-18
ports
40-7
overriding CoS
10-Gigabit Ethernet
10-6
trusting CoS
14-6
14-6
private VLAN edge ports
10-3
See protected ports
25-6
dynamic access
7-1
20-2
primary VLANs
18-20
blocking
38-61
preventing unauthorized access
1-7
port priority
access
prefix lists, BGP
12-30
port membership modes, VLAN
MSTP
20-5
preferential treatment of traffic
mode, spanning tree
STP
25-9
with other features
9-18
25-10
25-7
displaying
9-10
36-38
25-17
configuring
9-26
9-11
configuration tasks
25-17
and QoS trusted boundary
9-3
VLAN assignment
described
12-11
port security
9-45
aging
described
12-3, 12-11
VLAN assignments
9-8
switch
as proxy
25-5
12-4
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
IN-33
Index
private VLANs
promiscuous ports
across multiple switches
and SDM template
and SVIs
configuring
15-4
defined
15-4
and switch stacks
15-5
15-1
community ports
15-2
community VLANs
configuration tasks
end station access to
15-3
mapping
enabling
3-16
3-16
1-9, 25-5
38-42
See PIM
provider edge devices
38-71
provisioning new members for a switch stack
15-3
5-9
proxy ARP
15-2
configuring
15-2, 15-3
definition
15-14
monitoring
3-16
Protocol-Independent Multicast Protocol
15-6
isolated VLANs
disabling
protocol-dependent modules, EIGRP
15-6
default configuration
isolated port
3-15
protected ports
15-7, 15-8
15-10
IP addressing
described
guidelines and restrictions
15-2, 15-3
configuration guidelines
configuring
15-2
protected mode
15-5
benefits of
15-13
38-13
38-11
with IP routing disabled
15-15
ports
38-13
pruning, VTP
community
disabling
15-2
configuration guidelines
configuring host ports
on a port
15-11
configuring promiscuous ports
isolated
in VTP domain
15-8
15-13
primary VLANs
in VTP domain
on a port
15-2
15-1, 15-3
examples
13-5
promiscuous ports
15-2
overview
13-4
secondary VLANs
15-2
subdomains
traffic in
changing
15-1
privileged EXEC mode
12-23
12-23
for VTP pruning
VLANs
2-2
privilege levels
13-5
13-14
PVST+
changing the default for lines
logging into
7-9
described
17-10
IEEE 802.1Q trunking interoperability
7-9
overview
13-14
pruning-eligible list
15-5
exiting
12-24
enabling
15-2
promiscuous
13-14
instances supported
7-9
17-11
17-10
7-2, 7-7
setting a command with
7-8
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
IN-34
OL-12189-01
Index
QoS (continued)
configuration guidelines
QoS
auto-QoS
and MQC commands
36-1
36-25
standard QoS
auto-QoS
36-32
configuring
categorizing traffic
36-21
aggregate policers
configuration and defaults display
configuration guidelines
36-29
36-25
auto-QoS
36-58
36-20
default port CoS value
described
36-20
DSCP maps
disabling
36-26
DSCP transparency
displaying generated commands
36-26
displaying the initial configuration
effects on running configuration
egress queue defaults
enabling for VoIP
36-29
36-25
36-60
egress queue characteristics
36-70
ingress queue characteristics
36-21
36-26
IP extended ACLs
36-44
36-43
36-27
IP standard ACLs
ingress queue defaults
36-21
MAC ACLs
list of generated commands
36-22
36-66
36-45
policy maps, hierarchical
36-52
policy maps on physical ports
36-4
36-48
port trust states within the domain
classification
class maps, described
defined
36-39
DSCP trust states bordering another
domain 36-40
example configuration
basic model
36-37
trusted boundary
36-7
DSCP transparency, described
flowchart
36-38
default auto configuration
36-4
36-39
36-6
displaying statistics
36-78
36-39
36-3
DSCP transparency
in frames and packets
36-3
egress queues
IP ACLs, described
allocating buffer space
36-5, 36-7
MAC ACLs, described
options for IP traffic
36-5, 36-7
36-5
options for non-IP traffic
policy maps, described
36-5
36-30
36-71
buffer allocation scheme, described
36-75
configuring shared weights for SRR
36-76
36-4
trust DSCP, described
36-5
displaying the threshold map
trusted CoS, described
36-5
flowchart
trust IP precedence, described
displaying
36-46
36-78
36-74
36-17
mapping DSCP or CoS values
scheduling, described
class maps
configuring
36-5
36-18
configuring shaped weights for SRR
described
36-7
36-21
default standard configuration
forwarding treatment
36-35
setting WTD thresholds
WTD, described
enabling globally
36-73
36-4
36-71
36-19
36-34
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
IN-35
Index
QoS (continued)
QoS (continued)
flowcharts
policers
classification
configuring
36-6
egress queueing and scheduling
ingress queueing and scheduling
policing and marking
implicit deny
described
36-17
36-15
36-10
ingress queues
36-78
number of
36-33
36-9
policies, attaching to an interface
allocating bandwidth
described
36-68
buffer and bandwidth allocation, described
configuring shared weights for SRR
configuring the priority queue
described
36-68
36-16
36-4, 36-8
token bucket algorithm
displaying
displaying the threshold map
36-48
36-78
hierarchical
36-67
36-8
hierarchical on SVIs
36-15
mapping DSCP or CoS values
priority queue, described
scheduling, described
WTD, described
36-52
nonhierarchical on physical ports
36-67
QoS label, defined
36-16
36-4
configuring egress characteristics
36-67
high priority (expedite)
automatic classification and queueing
detection and trusted settings
mapping tables
36-77
location of
DSCP-to-DSCP-mutation
IP-precedence-to-DSCP
36-64
36-61
36-62
36-50, 36-55
36-4, 36-8
described
36-40
36-5
trusted device
36-38
within the domain
36-35
See QoS
queries, IGMP
23-4
query solicitation, IGMP
36-2
packet modification
1-10
quality of service
36-12
marking, described
36-19
bordering another domain
36-63
marked-down actions
36-13
trust states
36-78
policed-DSCP
36-19, 36-76
36-14
WTD, described
support for
36-60
36-66
36-13
SRR, described
rewrites
DSCP-to-CoS
types of
36-20
36-20, 36-38
limiting bandwidth on egress interface
displaying
36-70
configuring ingress characteristics
36-16
IP phones
CoS-to-DSCP
36-48
queues
36-4
setting WTD thresholds
36-9
policy maps
characteristics of
36-69
36-4
flowchart
36-8
policing
36-68
allocating buffer space
overview
36-8
displaying
types of
36-7
36-50, 36-55, 36-58
23-13
36-19
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
IN-36
OL-12189-01
Index
RCP
configuration files
RADIUS
downloading
attributes
overview
vendor-proprietary
vendor-specific
7-31
B-16
preparing the server
7-29
uploading
configuring
7-28
authentication
authorization
B-19
deleting old image
7-23
downloading
7-27
7-21, 7-29
communication, per-server
multiple UDP ports
default configuration
uploading
7-20, 7-21
7-20
7-20
7-31
redundancy
7-20
limiting the services to the user
EtherChannel
7-27
HSRP
7-20
7-19
47-1
37-2
40-1
backbone
7-18
17-8
multidrop backbone
7-18
path cost
1-10
7-28
19-5
12-27
port priority
tracking services accessed by user
12-25
redundant links and UplinkFast
range
19-15
reliable transport protocol, EIGRP
10-10
of interfaces
rapid convergence
reloading software
10-9
18-10
Remote Copy Protocol
See RCP
rapid PVST+
Remote Network Monitoring
17-10
See RMON
IEEE 802.1Q trunking interoperability
instances supported
17-10
Rapid Spanning Tree Protocol
38-11
3-23
See RADIUS
See rapid PVST+
See RSTP
38-42
Remote Authentication Dial-In User Service
rapid per-VLAN spanning-tree plus
described
12-32
STP
suggested network environments
macro
12-32
reconfirming dynamic VLAN membership
displaying the configuration
support for
42-9
reconfirmation interval, VMPS, changing
recovery procedures
operation of
B-35
reachability, tracking IP SLAs IP host
7-25
method list, defined
B-36
B-38
defining AAA server groups
identifying the server
B-38
preparing the server
communication, global
RARP
B-17
image files
accounting
overview
B-18
17-11
Remote SPAN
See RSPAN
remote SPAN
29-3
report suppression, IGMP
described
23-6
disabling
23-16, 24-11
resequencing ACL entries
34-15
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
IN-37
Index
resets, in BGP
RIP (continued)
38-56
resetting a UDLD-shutdown interface
28-6
responder, IP SLAs
described
support for
response time, measuring with IP SLAs
restricted VLAN
41-4
default configuration
overview
9-14
restricting access
30-2
30-1
collecting group Ethernet
6-8
collecting group history
7-1
passwords and privilege levels
7-2
TACACS+
support for
reverse address resolution
12-32
See RARP
enabling
RFC
STP
1157, SNMPv1
23-2
1-8
18-17
17-16
route calculation timers, OSPF
route dampening, BGP
32-2
1166, IP addresses
19-18
root switch
MSTP
1112, IP multicast and IGMP
19-10
support for
38-10
Reverse Address Resolution Protocol
34-38
routed ports
6-2
38-31
configuring
1757, RMON
30-2
defined
1901, SNMPv2C
10-4
route-map command
32-2
2236, IP multicast and IGMP
2273-2275, SNMPv3
38-6
IP addresses on
32-2
1902 to 1907, SNMPv2
32-2
RIP
23-2
10-21, 38-6
38-96
route maps
BGP
38-59
policy-based routing
advertisements
authentication
38-24
38-22
38-21
39-23
38-21
38-94
router ACLs
38-21
default configuration
hop counts
38-38
38-68
routed packets, ACLs on
38-8
1587, NSSAs
for IPv6
30-5
1-13
described
7-10
retry count, VMPS, changing
described
30-5
root guard
7-17
configuring
30-3
statistics
NTP services
1305, NTP
30-6
groups supported
using with IEEE 802.1x
RADIUS
30-3
enabling alarms and events
9-35
9-14
overview
1-12
displaying status
configuring
38-25
RMON
41-8
described
38-25
summary addresses
41-4
enabling
split horizon
38-22
defined
34-2
types of
34-4
route reflectors, BGP
router ID, OSPF
38-67
38-40
route selection, BGP
38-57
route summarization, OSPF
38-38
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
IN-38
OL-12189-01
Index
route targets, VPN
RSTP (continued)
38-72
routing
designated switch, defined
default
interoperability with IEEE 802.1D
38-4
dynamic
described
38-4
redistribution of information
static
18-9
restarting migration process
38-89
topology changes
38-4
routing domain confederation, BGP
overview
38-66
Routing Information Protocol
18-9
synchronized
38-88
18-11
proposal-agreement handshake process
29-3
and stack changes
characteristics
cross-stack rapid convergence
29-9
default configuration
described
29-16
edge ports and Port Fast
29-11
29-8
point-to-point links
displaying status
29-23
root ports
in a switch stack
29-2
root port, defined
interaction with other features
session limits
replacing
29-8
18-10
18-9
B-20, B-21
rolling back
saving
29-5
B-20, B-21
3-17
29-11
sessions
creating
29-17
defined
29-4
S
scheduled reloads
limiting source traffic to specific VLANs
specifying monitored ports
29-17
with ingress traffic enabled
29-21
source ports
18-10, 18-24
running configuration
1-13, 29-1
received traffic
18-10
See also MSTP
29-9
29-6
monitoring ports
18-11
18-10
destination ports
monitored ports
18-10
rapid convergence
29-10
configuration guidelines
29-6
transmitted traffic
VLAN-based
29-19
3-23
scheduling, IP SLAs operations
29-6
described
8-1
configuring
8-5
number of
18-10
configuring
18-12
8-4
dual IPv4 and IPv6
18-13
designated port, defined
8-1
SDM template
BPDU
processing
5-11
templates
29-7
active topology
41-5
SDM
switch stack consideration
RSTP
format
18-13
18-9
described
routing protocol administrative distances
overview
18-26
port roles
See RIP
RSPAN
18-9
types of
18-9
8-2
8-1
secondary VLANs
15-2
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
IN-39
Index
secure HTTP client
show l2protocol command
16-13, 16-15, 16-16
configuring
show lldp traffic command
27-7
displaying
7-47
show platform forward command
7-48
secure HTTP server
configuring
displaying
show running-config command
displaying ACLs
7-46
See SNMP
25-9
Smartports macros
25-8
secure ports
applying Cisco-default macros
and switch stacks
applying macros
25-7
configuration guidelines
See SSH
creating
Secure Socket Layer
defined
tracing
1-9
sequence numbers in log messages
SNAP
13-3
service-provider network, MSTP and RSTP
11-8
11-2
26-1
SNMP
18-1
service-provider networks
accessing MIB variables with
and customer VLANs
Layer 2 protocols across
16-1
16-8
Layer 2 protocol tunneling for EtherChannels
16-9
described
32-4
disabling
32-7
and IP SLAs
41-2
authentication level
32-4
severity levels, defining in system messages
31-9
configuring
See SRR
overview
show access-lists hw-summary command
34-22
show and more command output, filtering
2-10
26-5
show configuration command
show forward command
show interfaces command
10-20
47-17
10-17, 10-20
32-10
community strings
shaped round robin
show cdp traffic command
32-4
agent
16-2
and IEEE 802.1Q tunneling
set-request operation
11-2
11-3
website
31-8
11-3
11-1
displaying
25-7
11-5, 11-7
11-4
default configuration
See SSL
11-5, 11-6
11-5
applying parameter values
7-37
Secure Shell
server mode, VTP
11-6
applying global parameter values
25-17
secure remote connections
security features
16-11
Simple Network Management Protocol
25-15
configuring
10-25
shutdown threshold for Layer 2 protocol packets
25-17
maximum number of
security, port
10-20
shutdown command on interfaces
and switch stacks
types of
34-20, 34-21, 34-31, 34-34
interface description in
7-48
secure MAC addresses
deleting
47-17
32-8
32-4
configuration examples
default configuration
engine ID
groups
host
32-16
32-6
32-7
32-6, 32-9
32-6
ifIndex values
32-5
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
IN-40
OL-12189-01
Index
SNMP (continued)
software images
in-band management
location in flash
1-6
informs
recovery procedures
and trap keyword
described
32-15
enabling
32-14
source addresses
32-15
limiting system log messages to NMS
31-10
1-5, 32-3
location of
A-4
supported
notifications
overview
in IPv6 ACLs
35-6
source-and-destination-IP address based forwarding,
EtherChannel 37-8
source-MAC address forwarding, EtherChannel
32-5
and stack changes
32-3
trap manager, configuring
default configuration
32-15
32-13
traps
29-11
29-11
destination ports
29-8
displaying status
29-23
interaction with other features
32-3, 32-5
differences from informs
disabling
32-15
enabling
32-11
monitored ports
32-5
types of
32-1, 32-4
32-11
32-2
32-2
received traffic
session limits
25-11
29-5
29-11
configuring ingress forwarding
32-2
creating
29-12
defined
29-4
29-15, 29-22
limiting source traffic to specific VLANs
32-2
snooping, IGMP
1-13, 29-1
sessions
32-6, 32-9
versions supported
29-8
ports, restrictions
6-22
29-9
29-6
monitoring ports
overview
enabling MAC address notification
overview
removing destination (monitoring) ports
23-2
software compatibility
See stacks, switch
37-7
29-10
configuration guidelines
32-17
system contact and location
described
37-8
SPAN
32-1, 32-4
status, displaying
SNMPv3
34-12
source-IP address based forwarding, EtherChannel
A-1
security levels
SNMPv2C
in IPv4 ACLs
source-and-destination MAC address forwarding,
EtherChannel 37-8
MIBs
SNMPv1
B-25
See also downloading and uploading
32-5
limiting access by TFTP servers
manager functions
3-23
tar file format, described
32-5
disabling
47-2
scheduling reloads
32-11
differences from traps
users
B-25
specifying monitored ports
29-12
with ingress traffic enabled
29-14
source ports
29-13
29-6
transmitted traffic
VLAN-based
29-15
29-6
29-7
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
IN-41
Index
spanning tree and native VLANs
stack changes, effects on (continued)
12-19
Spanning Tree Protocol
MAC address tables
See STP
MSTP
SPAN traffic
18-8
multicast routing
29-5
split horizon, RIP
MVR
38-25
SRR
25-17
SDM template selection
shaped weights on egress queues
36-75
SNMP
shared weights on egress queues
36-76
SPAN and RSPAN
shared weights on ingress queues
described
44-10
23-18
port security
configuring
6-20
36-68
STP
32-1
17-12
shaped mode
36-14
VLANs
shared mode
36-14
VTP
support for
29-10
system message log
36-14
8-3
31-2
12-6
13-6
stack master
1-11
SSH
bridge ID (MAC address)
configuring
described
7-39
defined
5-1
1-6, 7-37
election
5-6
encryption methods
IPv6
7-38
switch stack considerations
user authentication methods, supported
39-13
re-election
5-18, 7-38
7-38
SSL
5-8
5-6
See also stacks, switch
stack member
configuration guidelines
accessing CLI of specific member
7-44
configuring a secure HTTP client
7-47
configuring a secure HTTP server
7-45
cryptographic software image
described
configuring
member number
priority value
7-42
defined
7-41
monitoring
stack changes, effects on
CDP
IPv6
cross-stack EtherChannel
HSRP
replacing
37-9
IGMP snooping
IPv6 ACLs
IPv6 routing
5-9
5-25
5-17
See also stacks, switch
46-3
IEEE 802.1x port-based authentication
5-27
5-8
provisioning a new member
37-12
40-4
IP routing
5-1
priority value
fallback bridging
5-25
39-13
number
34-7
26-2
EtherChannel
5-24
displaying information of
7-48
ACL configuration
5-26
9-8
stack member number
10-7
stack protocol version
5-12
23-7
38-5
35-4
39-12
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
IN-42
OL-12189-01
Index
stacks, switch
stacks, switch (continued)
accessing CLI of specific member
offline configuration
5-26
assigning information
described
member number
priority value
effects of adding a provisioned switch
5-24
5-25
provisioning a new member
auto-advise
5-13
auto-upgrade
5-11
effects of replacing a provisioned switch
5-11
provisioned switch, defined
5-9
provisioning a new member
5-25
partitioned
5-13
CDP considerations
5-3, 47-9
configuration file
adding
26-2
compatibility, software
5-12
5-16
configuration guidelines
configuration scenarios
5-10
removing
5-11
replacing
5-11
replacing a failed member
5-21
software compatibility
5-19
copying an image file from one member to
another B-39
software image version
default configuration
STP
stack protocol version
5-21
5-1
bridge ID
displaying information of
5-27
5-22
HSRP considerations
6-20
17-3
hostnames in the display
17-3
31-1
31-2
system prompt consideration
upgrading
5-17
6-14
5-17
B-39
version-mismatch (VM) mode
5-1
automatic upgrades with auto-upgrade
5-3
5-3
MSTP instances supported
17-10
system-wide configuration considerations
5-22
management connectivity
merged
5-16, B-39
remotely monitoring
MAC address considerations
membership
17-3
system messages
39-12
managing
5-12
stack root switch election
40-4
incompatible software and image upgrades
MAC address of
5-12
root port selection
hardware compatibility and SDM mismatch
mode 5-11
5-17
5-12
instances supported
enabling persistent MAC address timer
IPv6 on
5-9
provisioned switch
5-8
description of
5-10
effects of removing a provisioned switch
provisioned configuration, defined
5-13
auto-extract
bridge ID
5-25
5-13
auto-copy
5-9
17-10
multicast routing, stack master and member
roles 44-10
described
5-12
examples
5-14
manual upgrades with auto-advise
upgrades with auto-extract
5-13
5-13
5-13
See also stack master and stack member
StackWise Plus technology, Cisco
1-3
See also stacks, switch
standby ip command
40-5
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
IN-43
Index
standby links
storm control
20-2
standby router
configuring
40-1
standby timers, HSRP
40-10
startup configuration
booting
manually
3-19
specific image
clearing
3-20
configuration file
specifying the filename
default boot configuration
stateless autoconfiguration
3-18
3-18
39-6
static access ports
12-11
10-3, 12-3
static addresses
See addresses
1-12
1-9
static routes
39-21
12-2
statistics
1-4
thresholds
25-1
3-18
described
19-7
disabling
19-17
enabling
19-16
described
19-3
disabling
19-15
enabling
19-14
described
19-2
disabling
19-14
enabling
19-13
IP multicast routing
forward-delay time
17-13, 19-12
17-23
17-22
44-53
17-23
17-20
port priority
root switch
17-18
17-16
secondary root switch
27-7
spanning-tree mode
27-7
switch priority
38-40
QoS ingress and egress
36-78
RMON group Ethernet
30-5
RMON group history
SNMP input and output
13-16
sticky learning
17-3
configuration guidelines
path cost
9-45
10-24
LLDP-MED
19-4
BackboneFast
maximum aging time
26-5
interface
VTP
support for
hello time
IEEE 802.1x
OSPF
25-18
configuring
38-4
static VLAN membership
LLDP
displaying
BPDU message exchange
38-88
configuring for IPv6
CDP
25-5
BPDU guard
static MAC addressing
static routing
disabling
BPDU filtering
assigning to VLAN
configuring
25-1
accelerating root port selection
automatically downloading
static IP routing
described
STP
B-20
defined
25-3
25-8
30-5
32-17
17-15
17-21
transmit hold-count
counters, clearing
17-18
17-24
17-24
cross-stack UplinkFast
described
19-5
enabling
19-16
default configuration
17-13
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
IN-44
OL-12189-01
Index
STP (continued)
STP (continued)
default optional feature configuration
designated port, defined
load sharing
overview
17-4
designated switch, defined
12-24
using path costs
17-4
detecting indirect link failures
disabling
19-12
12-27
using port priorities
19-8
12-25
loop guard
17-16
displaying status
described
17-24
EtherChannel guard
19-11
enabling
19-18
described
19-10
modes supported
disabling
19-17
multicast addresses, effect of
enabling
19-17
optional features supported
extended system ID
overview
effects on root switch
effects on the secondary root switch
overview
17-18
17-4
unexpected behavior
features supported
17-16
IEEE 802.1D and bridge ID
IEEE 802.1D and multicast addresses
inferior BPDU
17-9
described
19-2
enabling
19-12
12-26
protocols supported
19-10
17-10
redundant connectivity
17-5
17-8
root guard
17-3
instances supported
Port Fast
preventing root switch selection
17-4
IEEE 802.1t and VLAN identifier
1-7
12-27
port priorities
1-7
17-9
17-2
path costs
17-16
17-10
described
17-10
interface state, blocking to forwarding
19-2
interface states
19-10
enabling
19-18
root port, defined
17-3
blocking
17-6
root port selection on a switch stack
disabled
17-7
root switch
forwarding
configuring
17-6, 17-7
17-16
learning
17-7
effects of extended system ID
listening
17-7
election
overview
17-5
unexpected behavior
interoperability and compatibility among
modes 17-11
keepalive messages
17-2
Layer 2 protocol tunneling
17-11
17-16
shutdown Port Fast-enabled port
stack changes, effects of
superior BPDU
limitations with IEEE 802.1Q trunks
17-4, 17-16
17-3
status, displaying
16-8
17-3
19-2
17-12
17-24
17-3
timers, described
17-22
UplinkFast
described
19-3
enabling
19-15
VLAN-bridge
17-11
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
IN-45
Index
stratum, NTP
system clock
6-2
stub areas, OSPF
configuring
38-36
stub routing
daylight saving time
EIGRP
PIM
manually
38-29
subdomains, private VLAN
subnet mask
overview
38-8
summer time
and IP unicast routing
and router ACLs
enabling
switch console port
31-5
level keywords, described
10-5
routing between VLANs
31-14
facility keywords, described
10-6
limiting messages
12-2
message format
1-6
Switch Database Management
overview
See SDM
31-9
31-4
displaying the configuration
38-6
34-4
connecting VLANs
31-14
31-10
31-10
31-2
31-1
sequence numbers, enabling and disabling
switched packets, ACLs on
setting the display destination device
34-36
Switched Port Analyzer
stack changes, effects of
See SPAN
syslog facility
10-2
switchport block unicast command
switchport command
25-7
switch priority
1-13
time stamps, enabling and disabling
25-6
31-8
16-6
31-12
configuring the logging facility
facilities supported
31-13
31-14
system MTU and IEEE 802.1Q tunneling
16-5
system name
18-22
default configuration
17-21
switch software features
31-6
configuring the daemon
10-15
switchport protected command
31-5
UNIX syslog servers
25-7
switchport mode dot1q-tunnel command
31-8
31-2
synchronizing log messages
switchport block multicast command
STP
31-4
defining error message severity levels
disabling
MSTP
6-1
default configuration
1-5
SVIs
switched ports
6-12
system message logging
38-9
defined
6-12
See also NTP
12-29
6-13
SunNet Manager
6-13
displaying the time and date
success response, VMPS
supernet
time zones
15-1
38-8
subnet zero
6-11
summer time
38-27
6-13
1-1
switch virtual interface
default setting
6-15
manual configuration
See SVI
6-15
6-15
See also DNS
synchronization, BGP
38-53
syslog
system prompt, default setting
system resources, optimizing
6-14, 6-15
8-1
See system message logging
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
IN-46
OL-12189-01
Index
TFTP
configuration files
TACACS+
downloading
accounting, defined
7-11
authentication, defined
preparing the server
7-11
authorization, defined
uploading
7-11
7-17
authorization
7-13
deleting
7-16
7-14
identifying the server
uploading
7-17
B-26
B-29
limiting access by servers
7-13
TFTP server
limiting the services to the user
7-16
7-12
32-15
1-6
threshold, traffic level
25-2
threshold monitoring, IP SLAs
7-10
support for
B-27
preparing the server
7-13
displaying the configuration
operation of
3-6
B-29
downloading
login authentication
default configuration
3-6
image files
authentication key
41-6
time
1-10
See NTP and system clock
tracking services accessed by user
7-17
Time Domain Reflector
tagged packets
See TDR
IEEE 802.1Q
16-3
Layer 2 protocol
16-7
tar files
time-range command
34-17
time ranges in ACLs
34-17
time stamps in log messages
B-7
time zones
displaying the contents of
extracting
B-7
6-12
defined
B-25
LLDP
1-13
27-2
27-2
LLDP-MED
Telnet
27-2
Token Ring VLANs
accessing management interfaces
number of connections
setting a password
templates, SDM
31-8
TLVs
B-8
image file format
TDR
B-12
configuring for autoconfiguration
accounting
creating
B-11
configuration files in base directory
configuring
overview
B-12
2-11
support for
1-6
VTP support
7-6
ToS
8-2
temporary self-signed certificate
13-4
1-11
traceroute, Layer 2
7-43
Terminal Access Controller Access Control System Plus
See TACACS+
terminal lines, setting a password
12-6
and ARP
47-12
and CDP
47-12
broadcast traffic
7-6
described
47-11
47-11
IP addresses and subnets
47-12
MAC addresses and VLANs
47-12
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
IN-47
Index
traceroute, Layer 2 (continued)
multicast traffic
connectivity problems
47-12
multiple devices on a port
unicast traffic
troubleshooting
47-12
47-11
47-10, 47-11, 47-13
detecting unidirectional links
28-1
displaying crash information
47-20
usage guidelines
47-12
PIMv1 and PIMv2 interoperability problems
traceroute command
47-14
setting packet forwarding
See also IP traceroute
show forward command
tracked lists
with CiscoWorks
configuring
types
with ping
42-3
tracked objects
47-17
47-17
32-4
with debug commands
42-3
47-16
47-10
with system message logging
by Boolean expression
by threshold percentage
by threshold weight
with traceroute
42-4
47-13
See link-state tracking
tracking interface line-protocol state
trunking encapsulation
42-2
1-8
trunk ports
42-2
tracking objects
42-1
configuring
tracking process
42-1
defined
track state, tracking IP SLAs
31-1
trunk failover
42-6
42-5
tracking IP routing state
44-26
12-21
10-3, 12-3
encapsulation
42-9
traffic
12-21, 12-26, 12-27
trunks
blocking flooded
fragmented
configuring
34-5
fragmented IPv6
unfragmented
traffic policing
allowed-VLAN list
25-7
ISL
35-2
12-16
setting STP path costs
transmit hold-count
parallel
transparent mode, VTP
to non-DTP device
3-2
12-23
12-18
trusted boundary for QoS
configuring MAC address notification
configuring managers
32-11
6-22, 32-11
overview
32-11
32-1, 32-4
36-38
trusted port states
between QoS domains
classification options
32-3
notification types
6-22
12-24
12-27
pruning-eligible list
13-3, 13-12
traps
enabling
12-25, 12-26
native VLAN for untagged traffic
see STP
defined
12-27
using STP port priorities
25-1
trap-door mechanism
12-21, 12-26, 12-27
load sharing
34-5
1-11
traffic suppression
12-22
36-40
36-5
ensuring port security for IP phones
support for
1-11
within a QoS domain
trustpoints, CA
36-38
36-35
7-42
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
IN-48
OL-12189-01
Index
tunneling
defined
unicast MAC address filtering
and adding static addresses
16-1
IEEE 802.1Q
6-25
and broadcast MAC addresses
16-1
Layer 2 protocol
and CPU packets
16-8
tunnel ports
described
1-6
6-25
and multicast addresses
6-25
and router MAC addresses
10-4, 16-1
IEEE 802.1Q, configuring
configuration guidelines
16-6
incompatibilities with other features
16-6
twisted-pair Ethernet, detecting unidirectional links
type of service
28-1
described
6-25
unicast storm
25-1
6-25
6-25
unicast storm control command
See ToS
6-25
unicast traffic, blocking
25-4
25-7
UniDirectional Link Detection protocol
See UDLD
universal software image
cryptographic
UDLD
configuration guidelines
default configuration
feature set
28-4
advanced IP services
28-4
IP base
disabling
globally
on fiber-optic interfaces
1-1
UNIX syslog servers
28-6
echoing detection mechanism
28-2
daemon configuration
facilities supported
enabling
globally
link-detection mechanism
support for
UDP, configuring
UplinkFast
28-6
28-7
described
19-3
disabling
19-16
enabling
19-15
support for
1-7
1-7
uploading
38-17
UDP jitter, configuring
13-4
See downloading
28-1
28-2
resetting an interface
31-13
upgrading software images
16-10
28-1
status, displaying
31-14
unrecognized Type-Length-Value (TLV) support
28-6
Layer 2 protocol tunneling
neighbor database
31-12
message logging configuration
28-5
per interface
overview
1-2
noncryptographic
28-5
1-2
1-2
IP services
28-5
per interface
1-1
configuration files
41-9
UDP jitter operation, IP SLAs
preparing
41-8
unauthorized ports with IEEE 802.1x
9-7
B-11, B-14, B-17
reasons for
B-9
using FTP
B-15
using RCP
B-19
using TFTP
B-12
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
IN-49
Index
uploading (continued)
VLAN database
image files
and startup configuration file
preparing
and VTP
B-26, B-30, B-35
reasons for
B-33
using RCP
B-38
using TFTP
13-1
VLAN configuration saved in
B-24
using FTP
VLANs saved in
12-7
vlan dot1q tag native command
B-29
VLAN filtering and SPAN
See UDP
VLAN ID, discovering
2-2
username-based authentication
described
version-dependent transparent mode
13-2
VLAN Management Policy Server
13-4
See VMPS
version-mismatch (VM) mode
automatic upgrades with auto-upgrade
5-13
VLAN map entries, order of
34-30
VLAN maps
5-12
displaying
20-5
20-2
VLAN management domain
described
applying
5-13
manual upgrades with auto-advise
upgrades with auto-extract
5-13
5-13
34-34
common uses for
See VPN
40-1, 40-2
34-34
configuration guidelines
configuring
Virtual Private Network
34-30
34-29
creating
34-31
defined
34-2
denying access to a server example
12-5
denying and permitting packets
VLAN 1
disabling on a trunk port
minimization
displaying
12-22
removing
vlan-assignment response, VMPS
12-29
1-9
VLAN membership
modes
12-8
34-32
34-34
confirming
VLAN configuration
12-32
12-3
VLAN Query Protocol
12-8
VLAN configuration mode
34-40
support for
See VLAN maps
34-34
34-32
examples of ACLs and VLAN maps
12-22
VLAN ACLs
at bootup
12-7
VLAN load balancing on flex links
7-6
saving
29-7
6-26
configuration guidelines
vlan.dat file
16-5
vlan global configuration command
user EXEC mode
12-7
12-4
vlan database command
User Datagram Protocol
virtual router
12-8
2-2, 12-7
See VQP
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
IN-50
OL-12189-01
Index
VLANs
adding
VLANs (continued)
traffic between
12-9
adding to VLAN database
allowed on trunk
VLAN-bridge STP
12-9
aging dynamic addresses
VTP modes
17-9
and spanning-tree instances
configuration guidelines, normal-range VLANs
12-7
12-13
default configuration
12-32
12-33
voice-over-IP
12-28
12-33
12-32
12-32
12-32
14-1
voice VLAN
in the switch stack
Cisco 7960 phone, port connections
12-6
limiting source traffic with RSPAN
limiting source traffic with SPAN
29-19
29-15
IEEE 802.1Q frames
1-8
connecting to an IP phone
port membership modes
12-6
default configuration
12-3
described
12-11
STP and IEEE 802.1Q trunks
12-2
14-6
IEEE 802.1p priority tagged frames
12-5
static-access ports
configuring IP phones for data traffic
14-6
configuring ports for voice traffic in
12-24
12-1, 12-4
number supported
14-3
trust CoS priority of incoming frame
23-18
native, configuring
configuration guidelines
14-1
override CoS of incoming frame
12-9
Token Ring
reconfirming
retry count, changing
12-13
supported
12-29
reconfirming membership
12-1, 12-12
12-2
parameters
12-30
reconfirmation interval, changing
1-8
normal-range
described
monitoring
12-16
multicast
12-30
mapping MAC addresses to VLANs
10-2, 12-1
modifying
12-34
12-28
troubleshooting
12-8
12-10
extended-range
internal
12-33
dynamic port membership
12-10
customer numbering in service-provider
networks 16-3
illustrated
administering
description
12-9
creating in VLAN configuration mode
features
VMPS
12-6
default configuration
10-6
creating in config-vlan mode
displaying
12-16
configuration guidelines
connecting through SVIs
described
VLAN trunks
configuration example
12-1
configuring IDs 1006 to 4094
deleting
13-3
See VTP
12-3, 12-6, 12-13
configuration guidelines, extended-range
VLANs 12-13
configuring
17-11, 46-2
VLAN Trunking Protocol
12-22
configuration options
12-2
17-11
displaying
14-5
14-5
14-4
14-3
14-1
14-7
IP phone data traffic, described
IP phone voice traffic, described
14-2
14-2
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
IN-51
Index
VPN
VTP (continued)
configuring routing in
forwarding
configuration revision number
38-79
guideline
38-73
in service provider networks
routes
38-70
resetting
13-15
configuring
38-71
VPN routing and forwarding table
See VRF
VQP
13-14
client mode
13-11
server mode
13-9
transparent mode
1-8, 12-28
VRF
consistency checks
defining
tables
VRF-aware services
ftp
ping
13-1
disabling
13-12
domains
38-75
38-75
client
13-3, 13-11
13-3, 13-9
38-76
server
syslog
38-77
transitions
monitoring
38-77
VRFs, configuring multicast
VTP
advertisements
13-14
12-20, 13-3
and extended-range VLANs
and normal-range VLANs
client mode, configuring
13-2
disabling
13-14
enabling
13-14
examples
13-5
overview
13-4
support for
13-2
1-8
pruning-eligible list, changing
13-11
configuration
server mode, configuring
global configuration mode
guidelines
13-8
pruning
38-78
adding a client to a domain
13-3, 13-12
13-16
passwords
38-76
13-7
requirements
statistics
13-9
1-8
Token Ring support
13-7
13-4
transparent mode, configuring
13-9
using
13-7
VLAN configuration mode
configuration mode options
13-7
configuration requirements
13-9
13-8
12-23
13-16
support for
13-8
privileged EXEC mode
saving
13-3
transparent
38-78
uRPF
16-8
modes
38-76
traceroute
13-8
13-2
SNMP
tftp
13-7
Layer 2 protocol tunneling
38-78
HSRP
described
domain names
38-75
configuring
13-4
default configuration
38-72
38-70
ARP
13-12
13-12
13-1
version, guidelines
Version 1
13-9
13-4
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
IN-52
OL-12189-01
Index
VTP (continued)
WTD
Version 2
described
configuration guidelines
36-13
setting thresholds
13-9
disabling
13-13
egress queue-sets
enabling
13-13
ingress queues
overview
13-4
support for
WCCP
Xmodem protocol
default configuration
43-5
43-5
43-1
displaying
43-10
dynamic service groups
enabling
47-2
43-3
configuration guidelines
described
36-67
1-11
authentication
36-71
43-3
43-6
features unsupported
43-5
forwarding method
43-3
Layer-2 header rewrite
MD5 security
43-3
43-3
message exchange
43-2
monitoring and maintaining
negotiation
43-10
43-3
packet redirection
43-3
packet-return method
43-3
redirecting traffic received from a client
setting the password
43-6
43-7
unsupported WCCPv2 features
43-5
web authentication
configuring
described
9-42 to 9-44
1-9, 9-21
fallback for IEEE 802.1x
9-43
Web Cache Communication Protocol
See WCCP
weighted tail drop
See WTD
weight thresholds in tracked lists
wizards
42-5
1-3
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
IN-53
Index
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
IN-54
OL-12189-01
You might also like
- Failing Function Codes, Failing Items, and Symbolic FRUsNo ratings yetFailing Function Codes, Failing Items, and Symbolic FRUs420 pages
- Cisco Catalyst Switch Module 3110 and 3012 For Ibm Bladecenter Software Configuration GuideNo ratings yetCisco Catalyst Switch Module 3110 and 3012 For Ibm Bladecenter Software Configuration Guide1,384 pages
- Modeling and Control of Plate Mill Processes: Pedersen, Lars MalcolmNo ratings yetModeling and Control of Plate Mill Processes: Pedersen, Lars Malcolm200 pages
- Cisco Catalyst Blade Switch 3130 For Dell Software Configuration GuideNo ratings yetCisco Catalyst Blade Switch 3130 For Dell Software Configuration Guide1,226 pages
- Cisco IE 3000 Switch Software Configuration Guide: Cisco IOS Release 12.2 (50) SE March 2009No ratings yetCisco IE 3000 Switch Software Configuration Guide: Cisco IOS Release 12.2 (50) SE March 2009874 pages
- Steel Mill Scale: Safety Data Sheet 768No ratings yetSteel Mill Scale: Safety Data Sheet 76817 pages
- Annex 12 - Cisco C2960X Configuration GuideNo ratings yetAnnex 12 - Cisco C2960X Configuration Guide2,198 pages
- Catalyst 4500 Series Switch Software Configuration Guide, 12.2 (53) SGNo ratings yetCatalyst 4500 Series Switch Software Configuration Guide, 12.2 (53) SG1,358 pages
- Cisco IOS Switching Services Configuration Guide: Release 12.2No ratings yetCisco IOS Switching Services Configuration Guide: Release 12.2514 pages
- Catalyst 3750 Switch Software Configuration Guide: Cisco IOS Release 12.1 (14) EA1 July 2003No ratings yetCatalyst 3750 Switch Software Configuration Guide: Cisco IOS Release 12.1 (14) EA1 July 2003942 pages
- Catalyst 3750 Switch Software Configuration GuideNo ratings yetCatalyst 3750 Switch Software Configuration Guide1,088 pages
- Catalyst 3560 Switch Software Configuration Guide: Cisco IOS Release 12.2 (25) SEC July 2005No ratings yetCatalyst 3560 Switch Software Configuration Guide: Cisco IOS Release 12.2 (25) SEC July 20051,034 pages
- Beach Volleyball California E-Drillbook: 7 Great Beach Volleyball Drills To Get You StartedNo ratings yetBeach Volleyball California E-Drillbook: 7 Great Beach Volleyball Drills To Get You Started19 pages
- Catalyst 3560 Switch Software Configuration Guide: Cisco IOS Release 12.2 (25) SEC July 2005No ratings yetCatalyst 3560 Switch Software Configuration Guide: Cisco IOS Release 12.2 (25) SEC July 20051,034 pages
- Catalyst 3560 Switch Software Configuration Guide: Cisco IOS Release 12.2 (44) SE January 2008No ratings yetCatalyst 3560 Switch Software Configuration Guide: Cisco IOS Release 12.2 (44) SE January 20081,206 pages
- Catalyst 3750 Switch Software Configuration Guide: Cisco IOS Release 12.2 (40) SE August 2007No ratings yetCatalyst 3750 Switch Software Configuration Guide: Cisco IOS Release 12.2 (40) SE August 20071,256 pages
- Bladecenter Hs21: Installation and User'S GuideNo ratings yetBladecenter Hs21: Installation and User'S Guide80 pages
- Catalyst 3560 Switch Software Configuration GuideNo ratings yetCatalyst 3560 Switch Software Configuration Guide1,288 pages
- Catalyst 4500 Series Switch Cisco IOS Software Configuration GuideNo ratings yetCatalyst 4500 Series Switch Cisco IOS Software Configuration Guide608 pages
- Catalyst 2900 XL and Catalyst 3500 XL Software Configuration Guide, 12.0 (5) WC4 and 12.0 (5) WC5No ratings yetCatalyst 2900 XL and Catalyst 3500 XL Software Configuration Guide, 12.0 (5) WC4 and 12.0 (5) WC5368 pages
- Bladecenter Hs21 XM Memory Configurations: Positioning Information (Withdrawn Product)No ratings yetBladecenter Hs21 XM Memory Configurations: Positioning Information (Withdrawn Product)8 pages
- Catalyst 2960 Switch Software Configuration GuideNo ratings yetCatalyst 2960 Switch Software Configuration Guide714 pages
- Catalyst 2940 Switch Software Configuration Guide: Cisco IOS Release 12.1 (22) EA2 November 2004No ratings yetCatalyst 2940 Switch Software Configuration Guide: Cisco IOS Release 12.1 (22) EA2 November 2004454 pages
- Cisco Catalyst Blade Switch 3020 For HP Command Reference: Cisco IOS Release 12.2 (25) SEF June 2006No ratings yetCisco Catalyst Blade Switch 3020 For HP Command Reference: Cisco IOS Release 12.2 (25) SEF June 2006744 pages
- Cisco 800 Series Software Configuration GuideNo ratings yetCisco 800 Series Software Configuration Guide600 pages
- User Guide For The Catalyst Express 520 Switches: Cisco IOS Release Number 12.2 (37) EXNo ratings yetUser Guide For The Catalyst Express 520 Switches: Cisco IOS Release Number 12.2 (37) EX114 pages
- Switch 3750 Cisco Smart Install Configuration Guide IOS 12.2 53No ratings yetSwitch 3750 Cisco Smart Install Configuration Guide IOS 12.2 5376 pages
- 4500 Switch Cisco Ios Software Configuration GuideNo ratings yet4500 Switch Cisco Ios Software Configuration Guide438 pages
- Catalyst 4500 Series Switch Cisco IOS Software Config GuideNo ratings yetCatalyst 4500 Series Switch Cisco IOS Software Config Guide570 pages
- Catalyst 3750 Switch Software Configuration Guide: Cisco IOS Release 12.2 (46) SE August 2008No ratings yetCatalyst 3750 Switch Software Configuration Guide: Cisco IOS Release 12.2 (46) SE August 20081,298 pages
- Cisco Catalyst Blade Switch 3130 3032 Hardware Installation GuideNo ratings yetCisco Catalyst Blade Switch 3130 3032 Hardware Installation Guide72 pages
- Cisco Catalyst Switch Module 3110G, 3110X, and 3012 For Ibm Bladecenter Hardware Installation GuideNo ratings yetCisco Catalyst Switch Module 3110G, 3110X, and 3012 For Ibm Bladecenter Hardware Installation Guide50 pages
- Cisco Catalyst Blade Switch 3020 For HP Software Configuration Guide, Rel. 12.2 (25) SEF1 - Emr - Na-C01009086-1No ratings yetCisco Catalyst Blade Switch 3020 For HP Software Configuration Guide, Rel. 12.2 (25) SEF1 - Emr - Na-C01009086-1712 pages
- CompTIA A+ Complete Review Guide: Core 1 Exam 220-1201 and Core 2 Exam 220-1202From EverandCompTIA A+ Complete Review Guide: Core 1 Exam 220-1201 and Core 2 Exam 220-1202No ratings yet
- Study Guide 300-435 ENAUTO: Automating and Programming Cisco Enterprise Solutions Certification ExamFrom EverandStudy Guide 300-435 ENAUTO: Automating and Programming Cisco Enterprise Solutions Certification ExamNo ratings yet
- CompTIA A+ Complete Review Guide: Core 1 Exam 220-1101 and Core 2 Exam 220-1102From EverandCompTIA A+ Complete Review Guide: Core 1 Exam 220-1101 and Core 2 Exam 220-11025/5 (2)
- Cisco CCNA Command Guide: An Introductory Guide for CCNA & Computer Networking Beginners: Computer Networking, #3From EverandCisco CCNA Command Guide: An Introductory Guide for CCNA & Computer Networking Beginners: Computer Networking, #34.5/5 (2)
- Next-Generation switching OS configuration and management: Troubleshooting NX-OS in Enterprise EnvironmentsFrom EverandNext-Generation switching OS configuration and management: Troubleshooting NX-OS in Enterprise EnvironmentsNo ratings yet
- WAN TECHNOLOGY FRAME-RELAY: An Expert's Handbook of Navigating Frame Relay NetworksFrom EverandWAN TECHNOLOGY FRAME-RELAY: An Expert's Handbook of Navigating Frame Relay NetworksNo ratings yet
