You are on page 1of 360

Catalyst 2900 Series XL and

Catalyst 3500 Series XL
Software Configuration Guide
Cisco IOS Release 12.0(5)WC(1)
April 2001

Corporate Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 526-4100
Customer Order Number: DOC-786511=
Text Part Number: 78-6511-05

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 UCB’s 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.
AccessPath, AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, CiscoLink, the Cisco NetWorks logo, the
Cisco Powered Network logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, Fast Step, Follow Me Browsing,
FormShare, FrameShare, GigaStack, IGX, Internet Quotient, IP/VC, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness
Scorecard, MGX, the Networkers logo, Packet, PIX, RateMUX, ScriptBuilder, ScriptShare, SlideCast, SMARTnet, TransPath, Unity, Voice LAN,
Wavelength Router, and WebViewer are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That’s
Possible, and Empowering the Internet Generation, are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, Cisco, the Cisco
Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo,
Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastSwitch, IOS, IP/TV, LightStream, MICA, Network Registrar, Post-Routing,
Pre-Routing, Registrar, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. or its affiliates
in the U.S. and certain other countries.
All other brands, names, or trademarks mentioned in this document or Web site 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. (0102R)
Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide
Copyright © 1998–2001, Cisco Systems, Inc.
All rights reserved.

C O N T E N T S

Preface xv
Audience xv
Purpose xv
Organization xvii
Conventions xviii
Related Publications xix
Obtaining Documentation xx
World Wide Web xx
Cisco Documentation CD-ROM xx
Ordering Documentation xxi
Documentation Feedback xxi
Obtaining Technical Assistance xxii
Cisco.com xxii
Technical Assistance Center xxii
Contacting TAC by Using the Cisco TAC Website xxiii
Contacting TAC by Telephone xxiii

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide
78-6511-05

iii

Contents

CHAPTER

1

Overview 1-1
Features 1-1
Management Options 1-7
Management Interface Options 1-7
Advantages of Using CMS and Clustering Switches 1-8
Network Configuration Examples 1-10
Design Concepts for Using the Switch 1-10
Small to Medium-Sized Network Configuration 1-14
Collapsed Backbone and Switch Cluster Configuration 1-16
Large Campus Configuration 1-18
Hotel Network Configuration 1-20
Multidwelling Configuration 1-23

CHAPTER

2

Getting Started with CMS 2-1
Features 2-2
Cluster Manager and VSM 2-3
Cluster Tree 2-6
Switch Images 2-7
System LED 2-7
Redundant Power System LED 2-8
Port Modes and LEDs 2-9
Menu Bars 2-14
Toolbar 2-17
Port Pop-Up Menu 2-18
Device Pop-Up Menu 2-19
Cluster View and Cluster Builder 2-21
Topology 2-24
Menu Bar 2-26
Toolbar 2-27

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide

iv

78-6511-05

Contents

Device Pop-Up Menu 2-28
Candidate, Member, and Link Pop-Up Menus 2-29
CMS Window Components 2-31
Host Name List 2-32
Tabs 2-32
Lists 2-32
Buttons 2-33
Online Help 2-33
Accessing CMS 2-35
Saving Configuration Changes 2-37
Using Different Versions of Web-Based Switch Management Software 2-38
Where to Go Next 2-38

CHAPTER

3

Getting Started with the CLI 3-1
Command Usage Basics 3-2
Accessing Command Modes 3-2
Abbreviating Commands 3-4
Using the No and Default Forms of Commands 3-5
Redisplaying a Command 3-5
Getting Help 3-5
Command-Line Error Messages 3-7
Accessing the CLI 3-8
Accessing the CLI from a Browser 3-9
Saving Configuration Changes 3-10
Where to Go Next 3-10

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide
78-6511-05

v

Contents

CHAPTER

4

General Switch Administration 4-1
Basic IP Connectivity to the Switch 4-2
Switch Software Releases 4-2
Console Port Access 4-3
Telnet Access to the CLI 4-4
HTTP Access to CMS 4-5
SNMP Network Management Platforms 4-6
Using FTP to Access the MIB Files 4-7
Using SNMP to Access MIB Variables 4-7
Default Settings 4-9

CHAPTER

5

Clustering Switches 5-1
Understanding Switch Clusters 5-2
Command Switch Characteristics 5-2
Standby Command Switch Characteristics 5-3
Candidate and Cluster Member Characteristics 5-3
Planning a Switch Cluster 5-4
Automatic Discovery of Cluster Candidates 5-4
Standby Command Switches 5-5
IP Addresses 5-8
Passwords 5-8
Host Names 5-10
SNMP Community Strings 5-10
Management VLAN 5-11
Network Port 5-12
NAT Commands 5-12
LRE Profiles 5-13
Availability of Switch-Specific Features in Switch Clusters 5-13

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide

vi

78-6511-05

Contents

Creating a Switch Cluster 5-13
Designating and Enabling a Command Switch 5-14
Adding and Removing Cluster Members 5-14
Designating and Enabling Standby Command Switches 5-17
Verifying a Switch Cluster 5-19
Displaying an Inventory of the Clustered Switches 5-19
Displaying Link Information 5-20
Using the CLI to Manage Switch Clusters 5-21
Using SNMP to Manage Switch Clusters 5-22

CHAPTER

6

Configuring the System 6-1
Changing IP Information 6-2
Manually Assigning and Removing Switch IP Information 6-2
Using DHCP-Based Autoconfiguration 6-4
Understanding DHCP-Based Autoconfiguration 6-4
DHCP Client Request Process 6-5
Configuring the DHCP Server 6-6
Configuring the TFTP Server 6-7
Configuring the Domain Name and the DNS 6-8
Configuring the Relay Device 6-9
Obtaining Configuration Files 6-10
Example Configuration 6-12
Changing the Password 6-15
Setting the System Date and Time 6-17
Configuring Daylight Saving Time 6-17
Configuring the Network Time Protocol 6-17
Configuring the Switch as an NTP Client 6-17
Enabling NTP Authentication 6-18
Configuring the Switch for NTP Broadcast-Client Mode 6-18

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide
78-6511-05

vii

Contents Configuring SNMP 6-18 Disabling and Enabling SNMP 6-18 Entering Community Strings 6-19 Adding Trap Managers 6-19 Configuring CDP 6-22 Configuring CDP for Extended Discovery 6-22 Configuring STP 6-24 Supported STP Instances 6-24 Using STP to Support Redundant Connectivity 6-25 Disabling STP 6-25 Accelerating Aging to Retain Connectivity 6-26 Configuring STP and UplinkFast in a Cascaded Cluster 6-26 Configuring Redundant Links By Using STP UplinkFast 6-28 Enabling STP UplinkFast 6-30 Configuring Cross-Stack UplinkFast 6-31 How CSUF Works 6-31 Events that Cause Fast Convergence 6-33 Limitations 6-35 Connecting the Stack Ports 6-35 Configuring Cross-Stack UplinkFast 6-37 Changing the STP Parameters for a VLAN 6-38 Changing the STP Implementation 6-39 Changing the Switch Priority 6-39 Changing the BPDU Message Interval 6-40 Changing the Hello BPDU Interval 6-40 Changing the Forwarding Delay Time 6-41 STP Port States 6-41 Enabling the Port Fast Feature 6-42 Changing the Path Cost 6-43 Changing the Port Priority 6-43 Configuring STP Root Guard 6-44 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide viii 78-6511-05 .

Contents Managing the ARP Table 6-45 Controlling IP Multicast Packets through CGMP 6-46 Enabling the Fast Leave Feature 6-47 Disabling the CGMP Fast Leave Feature 6-47 Changing the CGMP Router Hold-Time 6-48 Removing Multicast Groups 6-48 Configuring MVR 6-49 Using MVR in a Multicast Television Application 6-49 Configuration Guidelines and Limitations 6-51 Setting MVR Parameters 6-53 Configuring MVR 6-54 Managing the MAC Address Tables 6-56 MAC Addresses and VLANs 6-56 Changing the Address Aging Time 6-57 Removing Dynamic Address Entries 6-58 Adding Secure Addresses 6-58 Removing Secure Addresses 6-59 Adding Static Addresses 6-59 Removing Static Addresses 6-60 Configuring Static Addresses for EtherChannel Port Groups 6-61 Configuring TACACS+ 6-61 Configuring the TACACS+ Server Host 6-62 Configuring Login Authentication 6-64 Specifying TACACS+ Authorization for EXEC Access and Network Services 6-65 Starting TACACS+ Accounting 6-66 Configuring a Switch for Local AAA 6-67 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 ix .

Contents CHAPTER 7 Configuring the Switch Ports 7-1 Changing the Port Speed and Duplex Mode 7-2 Connecting to Devices That Do Not Autonegotiate 7-2 Setting Speed and Duplex Parameters 7-3 Configuring Flow Control on Gigabit Ethernet Ports 7-3 Configuring Flooding Controls 7-4 Enabling Storm Control 7-4 Disabling Storm Control 7-5 Blocking Flooded Traffic on a Port 7-6 Resuming Normal Forwarding on a Port 7-7 Enabling a Network Port 7-7 Disabling a Network Port 7-8 Configuring UniDirectional Link Detection 7-9 Creating EtherChannel Port Groups 7-10 Understanding EtherChannel Port Grouping 7-10 Port Group Restrictions on Static-Address Forwarding 7-11 Creating EtherChannel Port Groups 7-12 Configuring Protected Ports 7-13 Enabling Port Security 7-14 Defining the Maximum Secure Address Count 7-15 Enabling Port Security 7-15 Disabling Port Security 7-15 Enabling SPAN 7-16 Disabling SPAN 7-16 Configuring Voice Ports 7-17 Preparing a Port for a Cisco 7960 IP Phone Connection 7-18 Configuring a Port to Connect to a Cisco 7960 IP Phone 7-18 Overriding the CoS Priority of Incoming Frames 7-19 Configuring Voice Ports to Carry Voice and Data Traffic on Different VLANs 7-20 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide x 78-6511-05 .

Contents Configuring Inline Power on the Catalyst 3524-PWR Ports 7-21 Configuring the LRE Ports 7-22 LRE Links and LRE Profiles 7-22 LRE Ethernet Links 7-25 Assigning a Public Profile to All LRE Ports 7-27 Assigning a Private Profile to an LRE Port 7-28 CHAPTER 8 Configuring VLANs 8-1 Overview 8-2 Management VLANs 8-4 Changing the Management VLAN for a New Switch 8-5 Changing the Management VLAN Through a Telnet Connection 8-6 Assigning VLAN Port Membership Modes 8-7 VLAN Membership Combinations 8-8 Assigning Static-Access Ports to a VLAN 8-10 Overlapping VLANs and Multi-VLAN Ports 8-11 Using VTP 8-12 The VTP Domain 8-13 VTP Modes and Mode Transitions 8-14 VTP Advertisements 8-15 VTP Version 2 8-16 VTP Pruning 8-17 VTP Configuration Guidelines 8-18 Domain Names 8-18 Passwords 8-18 Upgrading from Previous Software Releases 8-19 VTP Version 8-19 Default VTP Configuration 8-20 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 xi .

1p Class of Service 8-44 How Class of Service Works 8-44 Port Priority 8-44 Port Scheduling 8-45 Configuring the CoS Port Priorities 8-46 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide xii 78-6511-05 .1Q Configuration Considerations 8-37 Trunks Interacting with Other Features 8-37 Configuring a Trunk Port 8-38 Disabling a Trunk Port 8-40 Defining the Allowed VLANs on a Trunk 8-40 Changing the Pruning-Eligible List 8-42 Configuring the Native VLAN for Untagged Traffic 8-43 Configuring 802.Contents Configuring VTP 8-20 Configuring VTP Server Mode 8-21 Configuring VTP Client Mode 8-22 Disabling VTP (VTP Transparent Mode) 8-23 Enabling VTP Version 2 8-24 Disabling VTP Version 2 8-25 Enabling VTP Pruning 8-25 Monitoring VTP 8-26 VLANs in the VTP Database 8-27 Token Ring VLANs 8-27 VLAN Configuration Guidelines 8-28 Default VLAN Configuration 8-28 Configuring VLANs in the VTP Database 8-32 Adding a VLAN 8-33 Modifying a VLAN 8-34 Deleting a VLAN from the Database 8-34 Assigning Static-Access Ports to a VLAN 8-35 How VLAN Trunks Work 8-36 IEEE 802.

Contents Load Sharing Using STP 8-46 Load Sharing Using STP Port Priorities 8-47 Configuring STP Port Priorities and Load Sharing 8-48 Load Sharing Using STP Path Cost 8-50 How the VMPS Works 8-52 Dynamic Port VLAN Membership 8-53 VMPS Database Configuration File 8-54 VMPS Configuration Guidelines 8-56 Default VMPS Configuration 8-57 Configuring Dynamic VLAN Membership 8-57 Configuring Dynamic Ports on VMPS Clients 8-58 Reconfirming VLAN Memberships 8-59 Changing the Reconfirmation Interval 8-59 Changing the Retry Count 8-60 Administering and Monitoring the VMPS 8-60 Troubleshooting Dynamic Port VLAN Membership 8-61 Dynamic Port VLAN Membership Configuration Example 8-61 CHAPTER 9 Troubleshooting 9-1 Avoiding Configuration Conflicts 9-2 Avoiding Autonegotiation Mismatches 9-3 Troubleshooting LRE Port Configuration 9-4 Troubleshooting CMS Sessions 9-5 Determining Why a Switch Is Not Added to a Cluster 9-8 Copying Configuration Files to Troubleshoot Configuration Problems 9-9 Troubleshooting Switch Upgrades 9-10 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 xiii .

Contents Recovery Procedures 9-13 Recovering from Lost Member Connectivity 9-13 Recovering from a Command Switch Failure 9-14 Replacing a Failed Command Switch with a Cluster Member 9-15 Replacing a Failed Command Switch with Another Switch 9-19 Recovering from a Failed Command Switch Without HSRP 9-22 Recovering from a Lost or Forgotten Password 9-22 Recovering from Corrupted Software 9-25 APPENDIX A System Error Messages A-1 How to Read System Error Messages A-2 Error Message Traceback Reports A-4 Error Message and Recovery Procedures A-5 Chassis Message A-5 CMP Messages A-5 Environment Messages A-6 GigaStack Messages A-7 Link Message A-8 LRE Link Messages A-8 Module Message A-9 Port Security Messages A-9 RTD Messages A-10 Storm Control Messages A-11 INDEX Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide xiv 78-6511-05 .

Before using this guide. hereafter referred to as the switches. Use this guide in conjunction with other documents for the following topics: • Requirements—This guide assumes you have met the hardware and software requirements and cluster compatibility requirements. • Start up information—This guide assumes you have assigned switch IP information and passwords by using the setup program. It includes descriptions of the management interface options and the features supported by the switch software. you should be familiar with the concepts and terminology of Ethernet and local area networking.Preface Audience The Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide is for the network manager responsible for configuring the Catalyst 2900 series XL and Catalyst 3500 series XL switches. which is described in the release notes. as described in the release notes. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 xv . Purpose This guide provides information about configuring and troubleshooting a switch or switch clusters. This guide also provides information about configuring the Cisco 575 Long-Reach Ethernet (LRE) customer premises equipment (CPE).

Note This guide does not repeat the concepts and CLI procedures provided in the standard Cisco IOS Release 12. For information about CMS requirements and the procedures for browser and plug-in configuration and accessing CMS. For complete syntax and usage information about the commands that have been specifically created or changed for the Catalyst 2900 XL or Catalyst 3500 XL switches. refer to the Cisco IOS Release 12. For CMS field-level window descriptions and procedures. creating. switch management interface.Preface Purpose • Cluster Management Suite (CMS) information—This guide provides an overview of the CMS web-based.0 commands. For the cluster commands. refer to the release notes. Because configuring switch clusters is most easily performed through CMS.0 documentation. refer to the CMS online help.0 documentation on Cisco. For switch features that use standard Cisco IOS Release 12.com for additional information and CLI procedures. refer to the Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference. • Cluster configuration—This guide provides information about planning for. refer to the Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference. • CLI command information—This guide provides an overview for using the CLI. and maintaining switch clusters. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide xvi 78-6511-05 . this guide does not provide the command-line interface (CLI) procedures.

Chapter 7. “Configuring VLANs. The online help provides the CMS procedures for configuring the switch ports. The online help provides the CMS procedures for configuring switch-wide settings. “Getting Started with CMS. Chapter 8. “Troubleshooting.” describes the basics for using the Cisco IOS CLI. Chapter 9.” describes switch clusters and the considerations for creating and maintaining them.” includes the switch-configuration default settings and information about software releases. Chapter 4.Preface Organization Organization The organization of this guide is as follows: Chapter 1. “System Error Messages.” provides the considerations and CLI procedures for configuring switch-wide settings.” lists the software features of this release and provides examples of how the switch can be deployed in a network. “Getting Started with the CLI. The online help provides the CMS procedures for configuring VLANs. Chapter 2. “General Switch Administration. Chapter 3. “Configuring the System. “Configuring the Switch Ports. Chapter 5. Chapter 6. and using Simple Network Management Protocol (SNMP). “Overview. switch management interface. “Clustering Switches. The online help provides the CMS procedures for configuring switch clusters. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 xvii . Refer to the release notes for the procedures for configuring your web browser and accessing CMS.” lists the IOS system error messages for the switch. Refer to the online help for field-level descriptions of all CMS windows and procedures for using the CMS windows.” provides the considerations and CLI procedures for configuring the switch ports. Appendix A. accessing the management interfaces.” describes the Cluster Management Suite (CMS) web-based.” provides the considerations and CLI procedures for configuring VLANs.” provides information about avoiding and resolving problems that might arise when you configure and maintain the switch. Cluster commands are described in the Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference.

• Information you enter is in boldface • Nonprinting characters. • Braces ({ }) group required choices. • Braces and vertical bars within square brackets ([{ | }]) indicate a required choice within an optional element. are in angle brackets (< >).Preface Conventions Conventions This guide uses the following conventions to convey instructions and information: Command descriptions use these conventions: • Commands and keywords are in boldface text. Notes. cautions. but could be useful information. In this situation. Caution Means reader be careful. such as passwords or tabs. • Square brackets ([ ]) indicate optional elements. Notes contain helpful suggestions or references to materials not contained in this manual. • Arguments for which you supply values are in italic. The tips information might not be troubleshooting or even an action. Interactive examples use these conventions: • Terminal sessions and system displays are in screen font. Tips Means the following will help you solve a problem. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide xviii 78-6511-05 . and tips use the following conventions and symbols: Note Means reader take note. screen font. you might do something that could result in equipment damage or loss of data. and vertical bars ( | ) separate the alternative elements.

See the “Ordering Documentation” section on page xxi. The following publications provide more information about the switches: • Release Notes for the Catalyst 2900 Series XL and Catalyst 3500 Series XL Cisco IOS Release 12.0(5)WC(1) (not orderable but is available on Cisco.0(5)WC(1) (order number DOC-7812155=) – Catalyst 2900 Series XL Hardware Installation Guide (order number DOC-786461=) – Catalyst 3500 Series XL Hardware Installation Guide (order number DOC-786456=) – Catalyst 2900 Series XL Modules Installation Guide (order number DOC-CAT2900-IG=) – Catalyst 2900 Series XL ATM Modules Installation and Configuration Guide (order number DOC-785472=) Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 xix .0(5)WC(1) (order number DOC-786511=) – Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference. The Catalyst 2900 XL and Catalyst 3500 XL Documentation CD is shipped with the switch and has the following publications: – This Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide.com) • Cluster Management Suite (CMS) online help • Catalyst 2900 XL and Catalyst 3500 XL Documentation CD (not orderable) Note This product-specific CD contains only the Catalyst 2900 XL and Catalyst 3500 XL switch documents and related hardware documents. which contains the documentation for all Cisco products and is shipped with all Cisco products.Preface Related Publications Related Publications You can order printed copies of documents with a DOC-xxxxxx= number. Cisco IOS Release 12. Cisco IOS Release 12. This CD is not the same as the Cisco Documentation CD-ROM.

The CD-ROM package is available as a single unit or as an annual subscription. The Cisco Documentation CD-ROM is updated monthly and may be more current than printed documentation.cisco.cisco. Note This CD contains the documentation for all Cisco products and is shipped with all Cisco products.com • http://www-europe.com • http://www-china. which ships with your product. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide xx 78-6511-05 . This CD is not the same as the Catalyst 2900 XL and Catalyst 3500 XL Documentation CD.cisco. which contains only the Catalyst 2900 XL and Catalyst 3500 XL switch documents and related hardware documents.Preface Obtaining Documentation – 1000BASE-T Gigabit Interface Converter Installation Note (not orderable but is available on Cisco.com Cisco Documentation CD-ROM Cisco documentation and additional literature are available in a CD-ROM package.com) – Catalyst GigaStack Gigabit Interface Converter Hardware Installation Guide (order number DOC-786460=) – Cisco 575 LRE CPE Hardware Installation Guide (order number DOC-7811469=) Obtaining Documentation The following sections provide sources for obtaining documentation from Cisco Systems. World Wide Web You can access the most current Cisco documentation on the World Wide Web at the following sites: • http://www.

com.com/go/subscription • Nonregistered CCO users can order documentation through a local account representative by calling Cisco corporate headquarters (California. If you are using the product-specific CD and you are connected to the Internet. Document Resource Connection 170 West Tasman Drive San Jose. Click Submit to send your comments to the Cisco documentation group.Preface Obtaining Documentation Ordering Documentation Cisco documentation is available in the following ways: • Registered Cisco Direct Customers can order Cisco Product documentation from the Networking Products MarketPlace: http://www. Otherwise. When you display the document listing for this platform. select the manual that you wish to comment on.pl • Registered Cisco.cisco.com/cgi-bin/order/order_root. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 xxi . To submit your comments by mail.cisco.com users can order the Documentation CD-ROM through the online Subscription Store: http://www. you can mail your comments to the following address: Cisco Systems. you can send us your comments by completing the online survey. in North America. CA 95134-9883 We appreciate your comments. by calling 800 553-NETS(6387). Inc. click Give Us Your Feedback. USA) at 408 526-7208 or. You can e-mail your comments to bug-doc@cisco. Documentation Feedback If you are reading Cisco product documentation on the World Wide Web. click the pencil-and-paper icon in the toolbar to display the survey. After you display the survey. for your convenience many documents contain a response card behind the front cover.

go to the following website: http://www. Through Cisco. and sample configurations from online tools.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. download and test software packages.com. Cisco.Preface Obtaining Technical Assistance Obtaining Technical Assistance Cisco provides Cisco. Registered users can order products.com is the foundation of a suite of interactive. In addition. easy-to-use tool for doing business with Cisco. and programs.com as a starting point for all technical assistance. networked services that provides immediate. you can find information about Cisco and our networking solutions. To access Cisco. Valuable online skill assessment. you can resolve technical issues with online technical support. open access to Cisco information and resources at anytime. check on the status of an order. additional troubleshooting tools are available from the TAC website. This highly integrated Internet application is a powerful. and view benefits specific to their relationships with Cisco. and order Cisco learning materials and merchandise.cisco.com Cisco. training. access technical support. services. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide xxii 78-6511-05 .com registered users. troubleshooting tips.com to obtain additional personalized information and services. Customers and partners can self-register on Cisco.com.com Technical Assistance Center The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract. Customers and partners can obtain documentation. For Cisco. and certification programs are also available. Cisco. from anywhere in the world.

No workaround is available. causing a critical impact to business operations if service is not restored quickly. No workaround is available.shtml P1 and P2 level problems are defined as follows: • P1—Your production network is down. • P4—You need information or assistance on Cisco product capabilities. or basic product configuration. use the Cisco TAC website to quickly find answers to your questions. but most business operations continue.com. contact TAC by telephone and immediately open a case. go to the following website: http://www.com/register/ If you cannot resolve your technical issue by using the TAC online resources. product installation. In each of the above cases.cisco.com registered users can open a case online by using the TAC Case Open tool at the following website: http://www. Network functionality is noticeably impaired.cisco. To register for Cisco. To obtain a directory of toll-free numbers for your country.com/tac P3 and P4 level problems are defined as follows: • P3—Your network performance is degraded. • P2—Your production network is severely degraded. contact TAC by going to the TAC website: http://www. affecting significant aspects of your business operations.cisco.com/tac/caseopen Contacting TAC by Telephone If you have a priority level 1 (P1) or priority level 2 (P2) problem.Preface Obtaining Technical Assistance Contacting TAC by Using the Cisco TAC Website If you have a priority level 3 (P3) or priority level 4 (P4) problem.com/warp/public/687/Directory/DirTAC. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 xxiii .cisco. go to the following website: http://www. Cisco.

Preface Obtaining Technical Assistance Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide xxiv 78-6511-05 .

It also includes references to where you can find additional information about each feature.0(5)WC(1). Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 1-1 . This software also supports the Cisco 575 Long-Reach Ethernet (LRE) customer premises equipment (CPE). Note Table 4-2 on page 4-9 lists the defaults for all key features. Table 1-1 describes the features supported in this release.1 C H A P T E R Overview This chapter provides the following topics about the Catalyst 2900 XL and Catalyst 3500 XL switch software: • Features • Management options • Examples of the Catalyst 2900 XL and Catalyst 3500 XL switches in different network topologies Features The Catalyst 2900 XL and Catalyst 3500 XL software supports the switches and modules listed in the Release Notes for the Catalyst 2900 Series XL and Catalyst 3500 Series XL Cisco IOS Release 12.

and browser requirements. authentication. in conjunction with CMS.3x flow control on 100-Mbps and Gigabit ports operating in full-duplex mode • Fast EtherChannel and Gigabit EtherChannel for enhanced fault tolerance and for providing up to 4 Gbps of bandwidth between switches. such as Netscape Communicator or Microsoft Internet Explorer. monitoring. Performance • Autosensing of speed on the 10/100 ports and autonegotiation of duplex mode on all switch ports for optimizing bandwidth • IEEE 802. – Automatic discovery of candidate switches and creation of clusters of up to 16 switches that can be managed through a single IP address. but to isolate the streams from subscriber VLANs for bandwidth and security reasons • Protected port (private VLAN edge port) option for restricting the forwarding of traffic to designated ports on the same switch Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 1-2 78-6511-05 . for – Unified configuration. software. routers. Refer to the release notes for the CMS and cluster hardware.Chapter 1 Overview Features Table 1-1 Features Ease of Use and Ease of Deployment • Cluster Management Suite (CMS) software for simplified switch and switch cluster management through a web browser. and servers • Per-port broadcast storm control for preventing faulty end stations from degrading overall system performance with broadcast storms • Cisco Group Management Protocol (CGMP) for limiting multicast traffic to specified end stations and reducing overall network traffic • CGMP Fast Leave for accelerating the removal of unused CGMP groups to reduce superfluous traffic on the network • Multicast VLAN registration (MVR) to continuously send multicast streams in a multicast VLAN. • Note Hot Standby Router Protocol (HSRP) for command-switch redundancy See the “Advantages of Using CMS and Clustering Switches” section on page 1-8. – Extended discovery of cluster candidates that are not directly connected to the command switch. and software upgrade of multiple switches (refer to the release notes for a list of eligible cluster members). from anywhere in your intranet • Switch clustering technology.

BOOTP is available in earlier software releases for this switch.Chapter 1 Overview Features Table 1-1 Features (continued) Manageability • Dynamic Host Configuration Protocol (DHCP)-based autoconfiguration for automatically configuring the switch during startup with IP address information and a configuration file that it receives during DHCP-based autoconfiguration Note DHCP replaces the Bootstrap Protocol (BOOTP) feature autoconfiguration to ensure retrieval of configuration files by unicast TFTP messages. • Directed unicast requests to a Domain Name System (DNS) server for identifying a switch through its IP address and its corresponding host name • Address Resolution Protocol (ARP) for identifying a switch through its IP address and its corresponding MAC address • Cisco Discovery Protocol (CDP) versions 1 and 2 for network topology discovery and mapping between the switch and other Cisco devices on the network • Network Time Protocol (NTP) for providing a consistent timestamp to all switches from an external source • Directed unicast requests to a Trivial File Transfer Protocol (TFTP) server for administering software upgrades from a TFTP server • Default configuration stored in Flash memory to ensure that the switch can be connected to a network and can forward traffic with minimal user intervention • In-band management access through a CMS web-based session • In-band management access through up to 16 simultaneous Telnet connections for multiple command-line interface (CLI)-based sessions over the network • In-band management access through Simple Network Management Protocol (SNMP) set and get 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 and a modem Note For additional descriptions of the management interfaces. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 1-3 . see the “Management Options” section on page 1-7.

1d Spanning Tree Protocol (STP) for redundant backbone connections and loop-free networks. • Inter-Switch Link (ISL) and IEEE 802.Chapter 1 Overview Features Table 1-1 Features (continued) Redundancy • HSRP for command switch redundancy • UniDirectional link detection (UDLD) on all Ethernet ports for detecting and disabling unidirectional links on fiber-optic interfaces caused by incorrect fiber-optic wiring or port faults • IEEE 802. better management and control of broadcast and multicast traffic. traffic patterns. and bandwidth For information about the maximum number of VLANs supported on each Catalyst 2900 XL and Catalyst 3500 XL switch. a switch can support up to 64 or 250 instances of STP (see Table 8-1 on page 8-3). including Gigabit uplinks and cross-stack Gigabit uplinks – STP root guard for preventing switches outside the core of the network from becoming the STP root Note Depending on the model. Cross-Stack UplinkFast.1Q trunking protocol on all ports for simplified network moves. VLAN Support • Note Depending on the switch model. STP has these features – Per-VLAN Spanning Tree (PVST) for balancing load across virtual LANs (VLANs) – Port Fast mode for eliminating forward delay by enabling a port to immediately change from a blocking state to a forwarding state – UplinkFast. up to 64 or 250 port-based VLANs are supported for assigning users to VLANs associated with appropriate network resources. and improved network security by establishing VLAN groups for high-security users and network resources • VLAN Membership Policy Server (VMPS) for dynamic VLAN membership • VLAN Trunk Protocol (VTP) pruning for reducing network traffic by restricting flooded traffic to links destined for stations receiving the traffic Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 1-4 78-6511-05 . adds. and changes. see the Table 8-1 on page 8-3. and BackboneFast for fast convergence after a spanning-tree topology change and for achieving load balancing between redundant uplinks.

and events) of embedded remote monitoring (RMON) agents for network monitoring and traffic analysis • Syslog facility for logging system messages about authentication or authorization errors. statistics. alarm.1p class of service (CoS) with two priority queues on the 10/100 and LRE switch ports and eight priority queues on the Gigabit ports for prioritizing mission-critical and time-sensitive traffic from data.Chapter 1 Overview Features Table 1-1 Features (continued) Quality of Service and Class of Service • IEEE 802. voice. notification. and resulting actions • Dynamic address learning for enhanced security • MAC-based port-level security for restricting the use of a switch port to a specific group of source addresses and preventing switch access from unauthorized stations • Terminal Access Controller Access Control System Plus (TACACS+). and time-out events Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 1-5 . a proprietary feature for managing network security through a TACACS server Monitoring • Switch LEDs that provide visual management of port.and switch-level status • Switch Port Analyzer (SPAN) for complete traffic monitoring on any port • Four groups (history. resource issues. and telephony applications • Voice VLAN (VVID) for creating subnets for voice traffic from Cisco IP Phones Security • Password-protected access (read-only and read-write access) to management interfaces (CMS and CLI) for protection against unauthorized configuration changes • Multilevel security for a choice of security level.

For information about the Cisco 575 LRE CPE. Catalyst 3524-PWR XL Switch-Specific Support • Ability to provide inline power to Cisco IP Phones from all 24 10/100 Ethernet ports • Autodetection and control of inline phone power on a per-port basis on all 10/100 ports • Fan-fault and over-temperature detection through Visual Switch Manager (VSM) Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 1-6 78-6511-05 . – Compliance with American National Standards Institute (ANSI) and European Telecommunication Standards Institute (ETSI) standards for spectral-mode compatibility with asymmetric digital subscriber line (ADSL). and digital telephone networks. – Support for connecting to the Public Switched Telephone Network (PSTN) through plain old telephone service (POTS) splitters such as the Cisco LRE 48 POTS Splitter (PS-1M-LRE-48). refer to the Cisco 575 LRE CPE Hardware Installation Guide. • CPE Ethernet ports and remote Ethernet devices. For information about the nonhomologated Cisco LRE 48 POTS Splitter (PS-1M-LRE-48). such as the Cisco 575 LRE CPE.Chapter 1 Overview Features Table 1-1 Features (continued) Catalyst 2912 LRE and Catalyst 2924 LRE XL Switch-Specific Support • Long-Reach Ethernet (LRE) technology for – Data and voice transmission through existing telephone lines (categorized and noncategorized unshielded twisted-pair cable) in multidwelling or tenant buildings. Integrated Services Digital Network (ISDN). such as a PC. refer to the Cisco LRE 48 POTS Splitter Installation Note. – Configuration and monitoring of connections between • Switch LRE ports and the Ethernet ports on remote LRE customer premises equipment (CPE) devices. – Up to 15 Mbps of bandwidth to remote Ethernet devices at distances of up to 4921 ft (1500 m) on each switch LRE port.

You can fully configure and monitor the switch and switch cluster members from the CLI. For more information about CMS. “Getting Started with CMS.Chapter 1 Overview Management Options Management Options The Catalyst 2900 XL and Catalyst 3500 XL switches are designed for plug-and-play operation: you only need to assign basic IP information to the switch and connect it to the other devices in your network. see Chapter 2. You can also display network topologies to gather link information and to display switch images to modify switch. see Chapter 3. you can fully configure and monitor a standalone switch.” • CLI—The switch IOS CLI software is enhanced to support desktop-switching features. “Getting Started with the CLI. If you have specific network needs. CMS is already installed on the switch. For more information about the CLI. a specific cluster member. or an entire switch cluster. you can configure and monitor the switch—on an individual basis or as part of a switch cluster—through its various management interfaces. This section discusses these topics: • Interface options for managing the switches • Advantages of clustering switches and using CMS Management Interface Options You can configure and monitor individual switches and switch clusters by using the following interfaces: • CMS—CMS is a graphical user interface that can be launched from anywhere in your network through a web browser such as Netscape Communicator or Microsoft Internet Explorer. Using CMS.and port-level settings.” Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 1-7 . You can access the CLI either by connecting your management station directly to the switch console port or by using Telnet from a remote management station.

and collect statistics by using SNMP management applications such as CiscoWorks2000 LAN Management Suite (LMS) and HP OpenView. Advantages of Using CMS and Clustering Switches Using CMS and switch clusters can simplify and minimize your configuration and monitoring tasks. security. you can • Manage and monitor interconnected Catalyst switches (refer to the release notes for a list of supported switches). You can use Cisco switch clustering technology to manage up to 16 interconnected supported Catalyst switches through one IP address as if they were a single entity. You can manage the switch from an SNMP-compatible management station that is running platforms such as HP OpenView or SunNet Manager. Gigabit Ethernet. including Ethernet. regardless of their geographic proximity and interconnection media. Fast EtherChannel. The switch supports a comprehensive set of MIB extensions and four RMON groups. and Gigabit EtherChannel connections. performance. • Accomplish multiple configuration tasks from a single CMS window without needing to remember CLI commands to accomplish specific tasks.Chapter 1 Overview Management Options • SNMP—SNMP provides a means to monitor and control the switch and switch cluster members. Fast Ethernet. Cisco GigaStack Gigabit Interface Converter (GBIC). CMS is the easiest interface to use and makes switch and switch cluster management accessible to authorized users from any PC on your network. see the “SNMP Network Management Platforms” section on page 4-6. For more information about using SNMP. You can manage switch configuration settings. This can conserve IP addresses if you have a limited number of them. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 1-8 78-6511-05 . By using switch clusters and CMS.

and port LED colors on the images are similar to those used on the physical LEDs themselves. You can also use the topology to quickly identify link information between switches. see Chapter 5. see Chapter 2. • Monitor real-time status of a switch or multiple switches from the LEDs on the front-panel images. and quality of service (QoS) configuration – Inventory and statistic reporting and link.and switch-level monitoring and troubleshooting – Group software upgrade • View a topology of interconnected devices to identify existing switch clusters and eligible switches that can join a cluster.” Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 1-9 . For more information about CMS. “Clustering Switches. The system. Here are some examples of globally setting and managing multiple ports and switches: – Port configuration such as speed and duplex settings – Port and console port security – NTP. redundant power system (RPS). STP.Chapter 1 Overview Management Options • Apply actions from CMS to multiple ports and multiple switches at the same time to avoid re-entering the same commands for each individual port or switch. VLAN. “Getting Started with CMS.” For more information about switch clusters.

workstations. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 1-10 78-6511-05 . consider the bandwidth required by your network users and the relative priority of the network applications they use. • Connect global resources—such as servers and routers to which network users require equal access—directly to the Fast Ethernet or Gigabit Ethernet switch ports so that they have their own Fast Ethernet or Gigabit Ethernet segment.Chapter 1 Overview Network Configuration Examples 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 Fast Ethernet and Gigabit Ethernet connections. and use VLANs and IP subnets to place the network resources in the same logical network as the users who access those resources most. When you configure your network. • Use full-duplex operation between the switch and its connected workstations. Table 1-2 describes what can cause network performance to degrade and describes how you can configure your network to increase the bandwidth available to your network users. Design Concepts for Using the Switch As your network users compete for network bandwidth. • Use the Fast EtherChannel or Gigabit EtherChannel feature between the switch and its connected servers and routers. Table 1-2 Increasing Network Performance Network Demands Too many users on a single network segment and a growing number of users accessing the Internet • Increased power of new PCs. and servers • High demand from networked applications (such as e-mail with large attached files) and from bandwidth-intensive applications (such as multimedia) Suggested Design Methods • Create smaller network segments so that fewer users share the bandwidth. it takes longer to send and receive data.

or low-priority. • Use VVIDs to provide a separate VLAN for voice traffic. based on 802. • Use VLAN trunks. 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.Chapter 1 Overview Network Configuration Examples Bandwidth alone is not the only consideration when designing your network.1p/Q. • Use the Catalyst 2900 LRE XL switches to provide up to 15 Mb of IP connectivity over existing infrastructure (existing telephone lines). • Use switches that support at least two queues per port to prioritize voice and data traffic as either high. Table 1-3 Providing Network Services Network Demands Suggested Design Methods High demand for multimedia support • Use CGMP and MVR to efficiently forward multicast traffic. High demand for protecting mission-critical applications • Use VLANs and protected ports to provide security and port isolation. Table 1-3 describes some network demands and how you can meet those demands. An evolving demand for IP telephony A growing demand for using existing infrastructure to transport data and voice from a home or office to the Internet or an intranet at higher speeds Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 1-11 . • Use QoS to prioritize applications such as IP telephony during congestion and to help control both delay and jitter within the network. consider providing network services that can support applications such as voice and data integration and security. As your network traffic profiles evolve. Cross-Stack UplinkFast.

to two backbone switches. Using the following Gigabit modules also provides flexibility in media and distance options: – 1000BASE-SX GBIC: fiber connections of up to 1804 ft (550 m) – 1000BASE-LX/LH GBIC: fiber connections of up to 32. If one of the redundant connections fails. you can connect up to 432 users. the second backbone switch preserves connectivity between the switches and network resources. or Fast EtherChannel.084 ft (100 km) – 1000BASE-T GBIC: copper connections of up to 328 ft (100 m) – Catalyst 2900 XL 1000BASE-T: copper connections of up to 328 ft (100 m) • Redundant Gigabit backbone—Using HSRP. You can create backup paths by using Fast Ethernet. again in a star configuration. When you use a stack of Catalyst 3548 XL switches. you can connect the Catalyst 2900 XL and Catalyst 3500 XL switches.Chapter 1 Overview Network Configuration Examples Figure 1-1 shows three configuration examples for using the Catalyst 2900 XL and Catalyst 3500 XL switches to create the following: • Cost-effective wiring closet—A cost-effective way to connect many users to the wiring closet is to connect up to nine Catalyst 2900 and Catalyst 3500 XL switches through GigaStack GBIC connections. To enhance network reliability and load balancing for different VLANs and subnets.808 ft (10 km) – 1000BASE-ZX GBIC: fiber connections of up to 328. you can create backup paths between Catalyst 4908G-L3 switches. Using Gigabit modules on two of the switches. the other can serve as a backup path. To preserve switch connectivity if one switch in the stack fails. Each switch in this configuration provides users a dedicated 1-Gbps connection to network resources in the backbone. Gigabit. connect the bottom switch to the top switch to create a GigaStack loopback and enable Cross-Stack UplinkFast on the cross-stack Gigabit uplinks. If one of the backbone switches fails. or Gigabit EtherChannel links. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 1-12 78-6511-05 . use Gigabit modules to connect the switches directly to a backbone switch in a star configuration. where the 1-Gbps connection is shared among the switches. Compare this with the switches in a GigaStack configuration. you can have redundant uplink connections to a Gigabit backbone switch such as the Catalyst 3508G XL switch. • High-performance workgroup—For users who require high-speed access to network resources. You can configure the stack members and the Catalyst 3508G XL switch as a switch cluster to manage them through a single IP address.

Chapter 1 Overview Network Configuration Examples Figure 1-1 Example Configurations Catalyst 3548 XL switch Catalyst 2900 XL and Catalyst 3500 XL GigaStack cluster Cost-Effective Wiring Closet Catalyst 3508 XL or 4908G-L3 switch High-Performance Workgroup Catalyst 2900 XL and Catalyst 3500 XL cluster Catalyst 4908G-L3 switch Catalyst 4908G-L3 switch 1-Gbps HSRP Catalyst 2900 XL and Catalyst 3500 XL cluster 54568 Redundant Gigabit Backbone Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 1-13 .

This GigaStack can also be configured as a switch cluster. Connecting a router to a Fast Ethernet switch port provides multiple. When a workstation is configured for full-duplex operation. You optimize network performance by placing workstations on the same logical segment as the servers they access most often. and Internet access. For networks that do not require Gigabit performance from a server. with primary and secondary command switches for redundant cluster management. connect the server to a Fast Ethernet or Fast EtherChannel switch port. Users in this network require e-mail.Chapter 1 Overview Network Configuration Examples Small to Medium-Sized Network Configuration Figure 1-2 shows a configuration for a network that has up to 250 users. database. Workstations are connected directly to the 10/100 switch ports for their own 10. it receives up to 200 Mbps of dedicated bandwidth from the switch. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 1-14 78-6511-05 . This divides the network into smaller segments (or workgroups) and reduces the amount of traffic that travels over a network backbone. It is required if numerous segments require access to the servers.or 100-Mbps access to network resources (such as web and mail servers). When the switch and server ports are configured for full-duplex operation. The Catalyst 2900 XL and Catalyst 3500 XL switches in this network are connected through a GigaStack GBIC on each switch to form a 1-Gbps network backbone. simultaneous access to the Internet through one line. A network backbone is a high-bandwidth connection (such as Fast Ethernet or Gigabit Ethernet) that interconnects segments and network resources. thereby increasing the bandwidth available to each user and improving server response time. allowing 1-Gbps throughput to users when needed. file-sharing. Servers are connected to the Gigabit module ports on the switches. the links provide 2 Gbps of bandwidth.

Chapter 1 Overview Network Configuration Examples Figure 1-2 Small to Medium-Sized Network Configuration Cisco 2600 router 100 Mbps (200 Mbps full duplex) Gigabit server 1 Gbps (2 Gbps full duplex) Catalyst 2900 XL and Catalyst 3500 XL GigaStack cluster Gigabit server Single workstations 54569 10/100 Mbps (20/200 Mbps full duplex) Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 1-15 .

1p/Q QoS gives forwarding priority to voice traffic over data traffic. A collapsed backbone has high-bandwidth uplinks from all segments and subnetworks to a single device. Cisco CallManager controls call processing. Voice traffic from the Cisco IP Phones are configured on separate VVIDs. and control calls from their PCs. and Cisco SoftPhone software integrates telephony and IP networks. If data. These multiservice switch ports automatically detect if an IP phone is connected. A Catalyst 4908G-L3 backbone switch provides the benefits of inter-VLAN routing and allows the router to focus on WAN access. such as a Gigabit switch. This network uses VLANs to segment the network logically into well-defined broadcast groups and for security management. you can group the switches into multiple clusters. only one VLAN can be configured per wiring closet. or into a single cluster. routing. as shown. This network uses a collapsed backbone and switch clusters. Using Cisco IP Phones. or an IP/TV multicast server). or a Catalyst 3508G XL switch to create a Gigabit backbone. multimedia. You can have up to four VVIDs per wiring closet. For any switch port connected to Cisco IP Phones. Users with workstations running Cisco SoftPhone software can place. and IP phone features and configuration. 802. Cisco CallManager software. Data and multimedia traffic are configured on the same VLAN. twisted-pair cable with RJ-45 connectors—to the 10/100 inline-power ports on the Catalyst 3524-PWR XL switches and to the 10/100 ports on the Catalyst 2900 XL and Catalyst 3500 XL switches. where the IP network supports both voice and data. a DHCP server. Cisco IP Phones are connected—using standard straight-through. The workgroups are created by clustering all the Catalyst switches except the Catalyst 4908G-L3 switch. You can manage a cluster through the IP address of its active and standby command switches. receive. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 1-16 78-6511-05 . You can use a Catalyst 4908G-L3 switch. The Gigabit connections to a server farm provide the workgroups full access to the network resources (such as a call-processing server running Cisco CallManager software. regardless of the geographic location of the cluster members.Chapter 1 Overview Network Configuration Examples Collapsed Backbone and Switch Cluster Configuration Figure 1-3 shows a configuration for a network of approximately 500 employees. Using CMS and Cisco switch clustering technology. as shown. and voice traffic are assigned to the same VLAN. which serves as a single point for monitoring and controlling the network. Grouping servers in a centralized location provides benefits such as security and easier maintenance.

The IP phone can receive redundant power when it also is connected to an AC power source. IP phones not connected to the Catalyst 3524-PWR XL switches receive power from an AC power source. Figure 1-3 Collapsed Backbone and Switch Cluster Configuration Gigabit servers Cisco CallManager Catalyst 4908G-L3 switch Cisco 2600 router 200 Mbps Fast EtherChannel (400 Mbps full duplex Fast EtherChannel) 1 Gbps (2 Gbps full duplex) Catalyst 2900 XL and 3500 XL GigaStack cluster Catalyst 2900 XL.Chapter 1 Overview Network Configuration Examples Each 10/100 inline-power port on the Catalyst 3524-PWR XL switches provides –48 VDC power to the Cisco IP Phone. and 2820 cluster Catalyst 3524-PWR XL GigaStack cluster IP IP IP IP IP AC power source Workstations running Cisco SoftPhone software IP IP Cisco IP Phones 54570 Cisco IP Phones Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 1-17 . 1900.

Chapter 1 Overview Network Configuration Examples Large Campus Configuration Figure 1-4 shows a configuration for a network of more than 1000 users. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 1-18 78-6511-05 . you can use switch clusters that have a mix of Catalyst 2900 XL and Catalyst 3500 XL switches. and IP phone features and configuration. The Catalyst 6500 switch provides the workgroups with Gigabit access to core resources: • Cisco 7000 series router for access to the WAN and the Internet. Cisco CallManager controls call processing. a Catalyst 6500 multilayer switch is used as the backbone switch. routing. Because it can aggregate up to 130 Gigabit connections. • Cisco Access gateway (such as Cisco Access Digital Trunk Gateway or Cisco Access Analog Trunk Gateway) that connects the IP network to the PSTN or to users in an IP telephony network. You can use the workgroup configurations shown in previous examples to create workgroups with Gigabit uplinks to the Catalyst 6500 switch. • Server farm that includes a call-processing server running Cisco CallManager software. For example.

Chapter 1 Overview Network Configuration Examples Figure 1-4 Large Campus Configuration IP telephony network or PSTN WAN Cisco CallManager Cisco 7200 Cisco access or 7500 router gateway Servers Catalyst 6500 switch Catalyst 2900 XL and 3500 XL GigaStack cluster 1 Gbps (2 Gbps full duplex) Catalyst 3524-PWR XL GigaStack cluster IP IP IP Cisco IP Phones IP IP Workstations running Cisco SoftPhone software IP Cisco IP Phones 54571 AC power source IP Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 1-19 .

Chapter 1 Overview Network Configuration Examples Hotel Network Configuration Figure 1-5 shows the Catalyst 2900 LRE XL switches in a hotel network environment with approximately 200 rooms. Data to and from the laptop and IP multicast traffic for the television are transferred through the LRE link. If the Catalyst 2900 LRE XL switches were connected to the PSTN through a homologated POTS splitter. share the same telephone line. all LRE ports would use an ANSI-compliant LRE profile named PUBLIC-ANSI. The splitter routes data (high-frequency) and voice (low-frequency) traffic from the telephone line to the switch and PBX. Microfilters improve voice call quality when voice and data equipment are using the same telephone line. Connected to the telephone line in each hotel room is a Cisco 575 LRE CPE. Through a patch panel. If a connection to a phone network is not required at all. and high-speed servers. a homologated POTS splitter is required to connect to the PSTN. If a PBX is not available. The hotel customer would connect a laptop or the television set-top box to the CPE Ethernet port. a router. the telephone line from each room connects to a nonhomologated POTS splitter. which provides both telephone and Ethernet connections. The laptop and telephone. The PBX routes voice traffic to the PSTN. which is established between the CPE wall port and the LRE port on a Catalyst 2900 LRE XL switch. connected to the CPE. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 1-20 78-6511-05 . The upstream and downstream rates on the LRE link are controlled by a profile configured on each LRE port. They also prevent nonfiltered telephone rings and nonfiltered telephone transitions (such as on-hook to off-hook) from interrupting the Ethernet connection. a splitter is not needed. such as the Cisco LRE 48 POTS Splitter (PS-1M-LRE-48). This network includes a private branch exchange (PBX) switchboard. A room telephone connects to the CPE phone port. and the switch can connect directly to the patch panel. Note All telephones not directly connected to the hotel room CPE require microfilters with a 300-Ohm termination.

you can configure port-based VLANs on the LRE ports to provide individual port security and protected ports to further prevent unwanted broadcasts within the VLANs. billing. The LRE ports support the same software features as the 10/100 ports. You can also manage and monitor the individual CPEs through the Catalyst 2900 LRE XL switches to which they are connected. For example. You can manage the switches through CMS as one or more switch clusters. such as a Catalyst 3524 XL switch. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 1-21 . The aggregation switch can connect to • Accounting. and provisioning servers. Each switch also has a 10/100 connection to an aggregation switch.Chapter 1 Overview Network Configuration Examples The Catalyst 2900 LRE XL switches are cascaded through the 10/100 switch ports. • A router that provides Internet access to the premises.

Chapter 1 Overview Network Configuration Examples Figure 1-5 Hotel Network Configuration Set-top box PC Telephones Telephones TV Rooms and users Required microfilter Cisco LRE CPE Cisco LRE CPE Required microfilter Floor 2 Set-top box PC Telephones Telephones TV Rooms and users Cisco LRE CPE Required microfilter Required microfilter Cisco LRE CPE Floor 1 Patch panel Cisco LRE 48 POTS splitters Catalyst 2900 LRE XL switches Servers PBX Catalyst 2900 XL or Catalyst 3500 XL switch Cisco 2600 router 54573 PSTN Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 1-22 78-6511-05 .

providing customers with either Fast Ethernet or Gigabit Ethernet connections to the MAN. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 1-23 . These switches are connected through 1000BASE-X GBIC ports. Figure 1-6 shows a configuration for a Gigabit Ethernet MAN ring using Catalyst 6500 switches as aggregation switches in the mini-point-of-presence (POP) location. All ports have CGMP enabled for multicast traffic management. ensuring that subscribers cannot view packets destined for other subscribers. All ports on the residential switches are configured as 802. The resident switches can be Catalyst 2900 XL and Catalyst 3500 XL switches.Chapter 1 Overview Network Configuration Examples Multidwelling Configuration A growing segment of residential and commercial customers are requiring high-speed access to Ethernet metropolitan-area networks (MANs).1Q trunks with the protected port and STP root guard options enabled. The protected port option provides security and isolation between ports on the switch. Catalyst 2900 LRE XL switches can also be used as residential switches for customers requiring connectivity through existing telephone lines. The Catalyst 2900 LRE XL switches can then connect to another residential switch through a 10/100 connection. Higher VLAN and VLAN ID (4096) support is ideal for more security flexibility. STP root guard prevents unauthorized devices from becoming the STP root switch.

including Catalyst 2900 LRE XL switches Residential location Set-top box Residential gateway (hub) Set-top box 54572 TV PC TV Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 1-24 78-6511-05 .Chapter 1 Overview Network Configuration Examples Figure 1-6 Multi-Dwelling Configuration Cisco 12000 Gigabit switch routers Service Provider POP Catalyst 6500 switches Catalyst 6500 multilayer switches Si Si Si Si Mini-POP Gigabit MAN Si Si Si Si Catalyst 2900 XL and Catalyst 3500 XL switches.

Note This chapter describes the CMS interface used on the Catalyst 2900 XL and Catalyst 3500 XL switches. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 2-1 . For field-level descriptions of the CMS windows and for procedures for using CMS. Catalyst 1900. such as the Catalyst 2950. Refer to the appropriate switch documentation for descriptions of the web-based management software used on other Catalyst desktop switches. refer to the online help.C H A P T E R 2 Getting Started with CMS This chapter describes the following features and interface components of the Cluster Management Suite (CMS) software: • Visual Switch Manager (VSM) and Cluster Manager • Cluster Builder and Cluster View • CMS window components This chapter also includes the following topics: • Accessing CMS • Saving changes on CMS • Using different versions of CMS For system requirements and for browser and Java plug-in configurations. and Catalyst 2820 switches. refer to the release notes.

it displays a front-panel view of a specific switch. For more information about accessing CMS.Chapter 2 Getting Started with CMS Features Features CMS consists of the following integrated set of Java-based applications for managing switch clusters and individual switches from a standard Web browser such as Netscape Communicator or Microsoft Internet Explorer: • Cluster Manager and Visual Switch Manager (VSM)—Cluster Manager is the application for configuring and monitoring the switches in a specific cluster. You cannot display VSM from Cluster Manager. Each CMS window also includes comprehensive online help. buttons. VSM is the application for configuring and monitoring a standalone switch or a specific switch in a cluster. cluster candidates. and so on). Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 2-2 78-6511-05 . When launched. cluster members. Cluster View is the application from which you can display connected switch clusters and neighboring edge devices in your network. • Cluster Builder and Cluster View—Cluster Builder is the application from which you can create and modify a specific switch cluster. When launched. it displays a topology (network map) of the cluster command switch. regardless of the CMS application you use. drop-down lists. It is also the application used to enable a cluster command switch. edge devices. which provides procedures for performing tasks from the window and high-level concepts. see the “Accessing CMS” section on page 2-35. and the link speeds between all cluster members. it displays a front-panel view of all switches in the cluster. You can toggle between Cluster Builder and Cluster View by selecting View > Toggle Views. Note You can display VSM for a specific switch from Cluster Builder or Cluster View by selecting Device > Launch Switch Manager. see the “Accessing CMS” section on page 2-35. For more information about accessing CMS. When launched. The CMS windows use a consistent set of components (such as tabs.

and port-level settings for a single switch. • A toolbar that provides buttons for displaying commonly used. switch. To assist in your configuration and monitoring tasks. The toolbar and pop-up menus provide quick ways to access the configuration and monitoring options available from the menu bar. VSM is the application for configuring switch. This menu bar is described in the “Menu Bars” section on page 2-14.Chapter 2 Getting Started with CMS Cluster Manager and VSM Cluster Manager and VSM Cluster Manager is the CMS application for configuring the port-. • A port-level pop-up menu for displaying windows specific for configuring and monitoring switch ports. • A device-level pop-up menu for displaying the configuration and monitoring windows also available from the menu bar. and cluster-level settings of the switches in a cluster. For information about using the switch images. This pop-up menu is described in the “Device Pop-Up Menu” section on page 2-19. This toolbar is described in the “Toolbar” section on page 2-17. • A menu bar that. switch-. both applications provide the following features: • A display of switch images (Figure 2-1 and Figure 2-2) for visual monitoring of the switches and switch ports. This pop-up menu is described in the “Port Pop-Up Menu” section on page 2-18.and cluster-level configuration windows and for displaying the legends and online help. see the “Switch Images” section on page 2-7. except for a few options. provides the same options for managing a single switch and clustered switches. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 2-3 .

1.126. Left-click Mode to change the meaning of the port LEDs.126.45 54513 10.Chapter 2 Getting Started with CMS Cluster Manager and VSM Figure 2-1 Visual Switch Manager 10. Press Ctrl. LEDs display the current port mode and the status of the switch and connected RPS. and select an option to change port-related settings.45 Right-click a port to display the port pop-up menu.1. The color of the port reflects port or link status. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 2-4 78-6511-05 . and then left-click ports to select multiple ports.

Right-click a switch to display the device pop-up menu. and select an option to change system-related settings.126.45 Cluster tree Select a switch from the cluster tree.1.Chapter 2 Getting Started with CMS Cluster Manager and VSM Figure 2-2 Cluster Manager 54504 10. The color of the switch icon reflects switch status. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 2-5 .

Select a cluster-tree icon to select the corresponding switch image. Yellow A system fault exists. Figure 2-3 shows the device icons as they appear in the cluster tree. It displays a list of the switches in a specific cluster. you can configure switch-wide settings from either the Cluster Manager menu bar options or the device pop-up menu. Complete descriptions of the icons and icon colors are available by selecting Help > Legend. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 2-6 78-6511-05 . For example. After you select a switch. Table 2-1 Cluster Tree Icon Colors Color Switch Status Green Switch is operating normally. The cluster tree uses a subset of the same icons used in the topology displayed in Cluster View and Cluster Builder. has lost power.Chapter 2 Getting Started with CMS Cluster Manager and VSM Cluster Tree The cluster tree appears in the Cluster Manager left frame (Figure 2-2). Red Switch is not powered up. such as the internal fan is not operating. or the command switch is unable to communicate with the member switch. Figure 2-3 Cluster Tree Icons The cluster tree displays the cluster name and the names and the status of cluster members (Table 2-1). The sequence of the cluster tree icons mirrors the sequence of the switch front-panel images. a yellow switch icon in the cluster tree means that particular switch is overheating or the fan is broken.

Amber System is receiving power but is not functioning properly. Table 2-2 lists the LED colors and their meanings. Table 2-2 System LED Color System Status Black (off) System is not powered up. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 2-7 .Chapter 2 Getting Started with CMS Cluster Manager and VSM Switch Images Use the front-panel images for visual switch management from a remote station. select System > User Settings from VSM or Cluster > User Settings from Cluster Manager. The following sections provide complete descriptions of the Catalyst 2900 XL and Catalyst 3500 XL LED images: • System LED • RPS LED • Port LEDs Summarized descriptions of the LED images are available from the VSM and Cluster Manager menu bar by choosing Help > Legend. making them as useful as the LEDs on the actual switches themselves. The LEDs on these images are updated at user-configurable polling intervals. To change the polling intervals. Green System is operating normally. System LED The system LED shows whether the switch is receiving power and functioning properly.

One of the power supplies in the RPS could be powered down. All other Catalyst 2900 XL and Catalyst 3500 XL switches use the Cisco RPS 600 (model PWR600-AC-RPS). the switch powers down and after 15 seconds restarts. Green RPS is operational. Refer to the appropriate switch documentation for RPS descriptions specific for the switch. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 2-8 78-6511-05 . Catalyst 2924 LRE XL. using power from the RPS. Note Table 2-3 The Catalyst 2912 LRE XL. If the switch power supply fails. RPS is connected but not functioning properly. and 3524-PWR XL Switches Color RPS Status Black (off) RPS is off or is not installed. Table 2-3 and Table 2-4 list the LED colors and their meanings. or a fan on the RPS could have failed. The switch goes through its normal boot sequence when it restarts. and Catalyst 3524-PWR XL switches use the Cisco RPS 300 (model PWR300-AC-RPS-N1). 2924-LRE.Chapter 2 Getting Started with CMS Cluster Manager and VSM Redundant Power System LED The Redundant Power System (RPS) LED shows the RPS status. Note Amber This is not a recommended configuration. Cisco RPS 600 LED on the Catalyst 2900 XL and Catalyst 3500 XL Switches Except the Catalyst 2912 LRE. Blinking green RPS and the switch AC power supply are both powered up.

Internal power supply of the switch is down. To select or change a mode. If it does not. Note The bandwidth utilization mode (UTIL LED) is not displayed on the VSM or Cluster Manager switch images. one of these other two conditions could exist. The switch is operating on the RPS. • The RPS fan could have failed. Contact Cisco Systems. Refer to the switch hardware installation guide for information about using the UTIL LED. and 3524-PWR XL Switches Color RPS Status Black (off) RPS is off or is not installed. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 2-9 . To put the RPS in Active mode. Contact Cisco Systems. and the LED should turn green. The following conditions could exist: Blinking amber • The RPS could be in standby mode. When you change port modes. the meaning of the port LED colors also changes. Green RPS is connected and operational. • One of the RPS power supplies could be down. click Mode until the desired mode LED is green. Select Monitoring > Bandwidth Graph to display the total bandwidth in use by the switch. 2924-LRE. Blinking green RPS is backing up another switch in the stack.Chapter 2 Getting Started with CMS Cluster Manager and VSM Table 2-4 Cisco RPS 300 LED on the Catalyst 2912 LRE. and redundancy is lost. Amber RPS is connected but not functioning. Port Modes and LEDs The port modes (Table 2-5) determine the type of information displayed through the port LEDs. press the Standby/Active button on the RPS.

Note FDUP or DUPLX Duplex setting on the ports. • Default setting is auto on all Catalyst 2900 XL and Catalyst 3500 XL switches and on the 10/100 ports on the Catalyst 2900 LRE XL switches. 100BASE-FX. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 2-10 78-6511-05 . or the Ethernet link status on the remote CPE. • Default setting is half-duplex on the LRE ports on the Catalyst 2900 LRE XL switches. this LED shows the link speed between the remote CPE and Ethernet device. or 1000BASE-X switch ports. LINE PWR Inline power setting on the Catalyst 3524-PWR XL 10/100 ports. On the Catalyst 2900 LRE XL switches.Chapter 2 Getting Started with CMS Cluster Manager and VSM Table 2-5 Port Modes Mode LED Description STAT Ethernet link status of the 10/100. Default mode on all Catalyst 2900 XL and Catalyst 3500 XL switches except the Catalyst 2900 LRE XL switches. the 10/100 switch ports on the Catalyst 2900 LRE XL continue to show Ethernet link status. Note SPEED or SPD When the LRE mode is active. this LED shows the duplex mode used on the Ethernet link between the remote customer premises equipment (CPE) and Ethernet device. Speed setting on the ports. Default setting is auto. Default mode on these switches only. Note On the Catalyst 2900 LRE XL switches. LRE (Catalyst 2900 LRE XL only) Long-Reach Ethernet (LRE) link status of the LRE ports on the Catalyst 2900 LRE XL switches. (Catalyst 3524-PWR XL only) Default setting is auto.

Brown No link and port is administratively shut down. or was blocked by Spanning Tree Protocol (STP). Green Port is operating in full-duplex mode. Port is transmitting or receiving data. CRC errors. and alignment and jabber errors are monitored for a link-fault indication. Note FDUP SPD After a port is reconfigured. Table 2-6 Port LEDs on the Catalyst 2912. Port was disabled by management. Refer to the module documentation for complete information. On the modular switches. and errors such as excessive collisions. the port LED can remain amber for up to 30 seconds as STP checks the switch for possible loops. Cyan (off) Port is operating in half-duplex mode. the 1 or 2 LED is green when a module is installed. Table 2-7. or by an address violation. and 2924M XL Switches Port Mode Port LED Color Description STAT Cyan (off) No link. Error frames can affect connectivity. and Table 2-8 explain how to interpret the port LED colors after you change the port mode. 2924. Green Link present. 2912MF. Amber Link fault. Blinking green Activity on the port. Port is not forwarding. Cyan (off) Port is operating at 10 Mbps. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 2-11 . 2924C. Green Port is operating at 100 Mbps.Chapter 2 Getting Started with CMS Cluster Manager and VSM Table 2-6.

Refer to the “Troubleshooting LRE Port Configuration” section on page 9-4. by an address violation. the 10/100 port LEDs continue to reflect Ethernet link status. In LRE mode. Green Ethernet link present on the 10/100 switch port or on the remote CPE Ethernet port. the LRE ports reflect the Ethernet link between the remote CPE and Ethernet device. Port was disabled by management. Brown No link and port is administratively shut down. Cyan (off) 10/100 switch port or remote CPE Ethernet port is operating in half-duplex mode. Green 10/100 switch port or remote CPE Ethernet port is operating at 100 Mbps. Port is transmitting or receiving data. STAT 10/100 switch port or remote CPE Ethernet port is not forwarding. or was blocked by STP. 2. and alignment and jabber errors are monitored for a link-fault indication. the port LED can remain amber for up to 30 seconds as STP checks the switch for possible loops.Chapter 2 Getting Started with CMS Cluster Manager and VSM Table 2-7 LRE Port LEDs on the Catalyst 2900 LRE XL Switches1 Port Mode Port LED Color Description LRE2 Cyan (off) No LRE link present on the LRE port. Amber Link fault. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 2-12 78-6511-05 . The Ethernet link default settings on the LRE ports are different than those on the 10/100 ports. Cyan (off) 10/100 switch port or remote CPE Ethernet port is operating at 10 Mbps. and errors such as excessive collisions. Cyan (off) No Ethernet link present on the 10/100 switch port or on the remote CPE Ethernet port. CRC errors. Amber LRE port on the switch and WALL port on the Cisco 575 LRE CPE unable to establish the rate defined by the assigned profile. Error frames can affect connectivity. Blinking green Activity on the 10/100 switch port or on the remote CPE Ethernet port. In STAT mode. such as a PC. 1. Port LED turns green in approximately 10 seconds after the LRE port detects a connection to a Cisco 575 LRE CPE. Note DUPLX SPEED After a port is reconfigured. Green LRE link present on the LRE port. See Table 2-5. Green 10/100 switch port or remote CPE Ethernet port is operating in full-duplex mode.

or was blocked by STP. Note DUPLEX SPEED After a port is reconfigured. Port is not forwarding. The LED turns green only when the switch port is providing power. the port LED can remain amber for up to 30 seconds as STP checks the switch for possible loops. by an address violation. Green Link present. Blinking green Activity on the port. CRC errors.Chapter 2 Getting Started with CMS Cluster Manager and VSM Table 2-8 Port LEDs on the Catalyst 3500 XL Switches Port Mode Port LED Color Description STATUS Cyan (off) No link. 1000BASE-X Ports Cyan (off) Port is not operating. Green Port is operating at 1000 Mbps. Amber Link fault. Inline power is on. Green Port is operating in full-duplex mode. Port is transmitting or receiving data. the port LED is off even if the IP phone is connected to the switch port. 10/100 Ports Cyan (off) Port is operating at 10 Mbps. and errors such as excessive collisions. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 2-13 . LINE PWR Cyan (off) (Catalyst 3524-PWR XL Green only) Inline power is off. Cyan (off) Port is operating in half-duplex mode. Green Port is operating at 100 Mbps. Port was disabled by management. Error frames can affect connectivity. and alignment and jabber errors are monitored for a link-fault indication. Brown No link and port is administratively shut down. If the Cisco IP Phone is receiving power from an AC power source.

Chapter 2 Getting Started with CMS Cluster Manager and VSM Menu Bars The VSM menu bar provides the options for configuring and monitoring a single switch. are arranged slightly differently in VSM and Cluster Manager. but with the following exceptions: • Some configuration options. Table 2-9 describes the VSM and Cluster Manager menu bar options and their function and shows where the two menu bars differ. • The option for designating a standby group of command switches is available only from Cluster Manager. • The option for rearranging the switch images is available only from Cluster Manager. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 2-14 78-6511-05 . such as some system and VLAN options. • The option for enabling a command switch is available only from VSM. The menu bars (Figure 2-1 and Figure 2-2) are similar. The Cluster Manager menu bar provides the options for configuring and monitoring a switch or a switch cluster.

Standby Command Configuration Create an Hot Standby Router Protocol (HSRP) standby group to provide command-switch redundancy. System Reload Reboot the software on a switch. and configure end stations as trap managers. Cluster (Cluster Manager-specific) Management VLAN Change the management VLAN for a cluster. User Settings Set the polling interval for Cluster Manager. software version. Software Upgrade Upgrade the software for the cluster or a switch. Cluster Builder. Set the application to display by default. and enable the display of the splash page when VSM starts. System Time Management Configure the system time or configure the Network Time Protocol (NTP). Device Position Rearrange the order in which switches appear in Cluster Manager. IP address. and other information about a switch or a cluster of switches. Cluster Builder Display Cluster Builder. ARP Table Display the device Address Resolution Protocol (ARP) table. Save Configuration Save the configuration. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 2-15 . SNMP Management Enter Simple Network Management Protocol (SNMP) community strings. and the performance graphs. IP Management Configure IP information for a switch.Chapter 2 Getting Started with CMS Cluster Manager and VSM Table 2-9 VSM and Cluster Manager Menu Bars Menu Bar Options Task Cluster (VSM-specific) Cluster Command Configuration Enable a switch to act as the cluster command switch. Console Baud Rate Change the baud rate for a switch. System Time Management (VSM-specific) Configure the system time or the NTP. VMPS Configuration Configure the VLAN Membership Policy Server. System Inventory Display the device type. User Settings (VSM-specific) Change the polling intervals for clustering and graphing. Cluster Management Display Cluster Manager or Cluster Builder.

Port Security Enable port security on a port. Port Port Configuration Display and configure port parameters on a switch. secure.1Q trunks. Legend Display the legend that describes the icons. Port Search Search for a port through its description. Switch Port Analyzer (SPAN) Enable SPAN port monitoring. labels. LRE Profile Display the LRE profile settings for the Catalyst 2900 LRE XL switches. VLAN VLAN Membership Display VLAN membership. Management VLAN (VSM-specific) Change the management VLAN on the switch. Flooding Control Enable broadcast storm control and block unicast and multicast flooding on a per-port basis. and configure Inter-Switch Link (ISL) and 802. VMPS Configuration (VSM-specific) Configure the VLAN Membership Policy Server (VMPS). assign ports to VLANs. and configure the speed of the LRE link. VTP Management Display and configure the VLAN Trunk Protocol (VTP) for interswitch VLAN membership. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 2-16 78-6511-05 . Port Statistics Display the Ethernet and LRE link statistics. Spanning-Tree Protocol (STP) Display and configure STP parameters for a switch. About Display the version number of VSM or Cluster Manager. Security Address Management Enter dynamic. You can also define the static addresses forwarding behavior.Chapter 2 Getting Started with CMS Cluster Manager and VSM Table 2-9 VSM and Cluster Manager Menu Bars (continued) Menu Bar Options Task Device Cisco Group Management Protocol (CGMP) Enable and disable the CGMP and the CGMP Fast Leave feature on a switch. and links. Help Contents List all of the available online help topics. Port Grouping (EtherChannel) Group ports into logical units for high-speed links between switches. and static addresses into a switch address table.

the ? button displays Help Contents. this button is not applicable and is therefore disabled. and links • Online help table of contents Cluster Manager Toolbar 54511 10. For example. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 2-17 . labels. Hover the cursor over a button to display a pop-up description.126.45 Move the cursor over the icon to display the tool tip.1.) • Software Upgrade window • SNMP Management window • VLAN Membership window • Spanning Tree Protocol window • Save Configuration window • User Settings window • Legend that describes the icons.Chapter 2 Getting Started with CMS Cluster Manager and VSM Toolbar The VSM and Cluster Manager toolbar (Figure 2-4) buttons display some switchand cluster-level configuration windows. From left to right on the toolbar. the following windows can be displayed: Figure 2-4 • Cluster Builder (On VSM.

you can configure a single port or configure multiple ports to run with the same settings. Table 2-10 VSM and Cluster Manager Port Pop-up Menu Pop-up Menu Option Task Port Configuration Display and configure port parameters on a switch. The port pop-up menu provides options for displaying commonly used port configuration windows (Table 2-10). • Press the Ctrl key. From the port pop-up menu. Flooding Controls Block the normal flooding of unicast and multicast packets. To display the port pop-up menu from VSM or Cluster Manager. Port Security Enable port security on a port. and errors recorded on the link.Chapter 2 Getting Started with CMS Cluster Manager and VSM Port Pop-Up Menu You can display all port configuration windows from the Port menu on the menu bar. VLAN Membership Define the VLAN mode for a port or ports. and enable the switch to block packet storms. refer to the online help. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 2-18 78-6511-05 . bytes. click the port images on a single switch or on different switches. Note This feature is only available when selecting an individual port. You can plot the link utilization percentage and the total packets. Not available for Catalyst 1900 or Catalyst 2820 switches. and right-click. and right-click. This feature is not available on Catalyst 1900 and Catalyst 2820 switches. Link Graph Right-click a port that is green to display the performance graph for the link. Not available for Catalyst 1900 or Catalyst 2820 switches. or you can display a subset of the port configuration windows from the VSM and Cluster Manager port pop-up menu. and add ports to VLANs. you can either • Click a specific port image. For more information about link graphs. Not available for Catalyst 1900 or Catalyst 2820 switches.

software version. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 2-19 . you can either • Click a specific switch icon from the Cluster Tree. Console Baud Rate Change the baud rate for one or more switches. ARP Table Manage the Address Resolution Protocol (ARP) table. Spanning Tree Protocol (STP) Change STP parameters to prevent network loops. and other information about a switch or cluster of switches. and right-click. and right-click. click the switch icons from the Cluster Tree. and configure end stations as trap managers. • Press the Ctrl key. click the switch image. IP address. and right-click. System Reload Reboot the software on a switch or a cluster. Table 2-11 VSM and Cluster Manager Device Pop-up Menu Pop-up Menu Options Task System Inventory Display the device type. the VSM and Cluster Manager device pop-up menu displays all of the configuration and monitoring windows (Table 2-11) available from the VSM and Cluster Manager menu bar. SNMP Management Enter SNMP community strings. LRE Profile Display the LRE profile parameters for the Catalyst 2912 LRE and Catalyst 2924 LRE XL switches. Software Upgrade Upgrade the software for a cluster or a switch. Device Cisco Group Management Protocol (CGMP) Enable and disable CGMP and the CGMP Fast Leave feature on a switch.Chapter 2 Getting Started with CMS Cluster Manager and VSM Device Pop-Up Menu With the exception of the Cluster menu bar options. To display the device pop-up menu from Cluster Manager. and configure the speed of the LRE link between an LRE port and a remote CPE. To display the device pop-up menu from VSM. IP Management Configure IP information for a switch. Save Configuration Save the configuration on one or all of the cluster switches.

Chapter 2

Getting Started with CMS

Cluster Manager and VSM

Table 2-11 VSM and Cluster Manager Device Pop-up Menu (continued)

Pop-up Menu Options

Task

Port

Port Configuration

Display and configure port parameters on a switch.

Port Statistics

Display the Ethernet and LRE link statistics.

Port Search

Search for a port through its description.

Port Grouping (EC)

Group ports into logical units for high-speed links between
switches.

Switch Port Analyzer (SPAN)

Enable SPAN port monitoring.

Flooding Control

Enable broadcast storm control, and block unicast and multicast
flooding on a per-port basis.

VLAN

VLAN Membership

Display VLAN membership, assign ports to VLANs, and
configure ISL and IEEE 802.1Q trunks.

VTP Management

Display and configure the VLAN Trunk Protocol (VTP) for
interswitch VLAN membership.

Security

Address Management

Enter dynamic, secure, and static addresses into a switch address
table, and define the forwarding behavior of static addresses.

Port Security

Enable port security on a port.

Monitoring

Bandwidth Graph

Display a graph that plots the total bandwidth in use by the switch.
This feature is not available on the Catalyst 1900 and
Catalyst 2820 switches. For more information about bandwidth
graphs, refer to the online help.

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide

2-20

78-6511-05

Chapter 2

Getting Started with CMS
Cluster View and Cluster Builder

Cluster View and Cluster Builder
Cluster View (Figure 2-5) and Cluster Builder (Figure 2-6) are the CMS
applications for displaying, creating, and modifying switch clusters.
To assist in your cluster configuration and monitoring tasks, both applications
provide the following features:

Cluster View displays a high-level topology where clusters are collapsed and
represented as double-switch icons with links to candidate switches, other
switch clusters, and edge devices.
Cluster Builder displays the topology of a specific switch cluster, where
switches and cluster- and command-capable devices connected to the
command switch display as cluster members or candidates.
The components used in a topology are described in the “Topology” section
on page 2-24.

A menu bar that provides the options for creating, modifying, monitoring, and
displaying switch clusters. This menu bar is further described in the “Menu
Bar” section on page 2-26.

A toolbar that provides buttons for displaying commonly used cluster
configuration windows and for displaying the legends and online help. This
toolbar is described in the “Toolbar” section on page 2-27.

A device-level pop-up menu in Cluster View. This pop-up menu is described
in the “Device Pop-Up Menu” section on page 2-28

Device- and link-level pop-up menus in Cluster Builder. These pop-up menus
are described in the “Candidate, Member, and Link Pop-Up Menus” section
on page 2-29.

The toolbar and pop-up menus provide quick ways to access the configuration and
monitoring options available from the menu bar.

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide
78-6511-05

2-21

Chapter 2

Getting Started with CMS

Cluster View and Cluster Builder

Figure 2-5

Cluster View

Cluster is collapsed to a
double-switch icon.

Connected cluster.

54505

mcluster

Status bar shows that
Cluster View is displayed.

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide

2-22

78-6511-05

Chapter 2

Getting Started with CMS
Cluster View and Cluster Builder

Figure 2-6

Cluster Builder

A switch icon with a
crown indicates the
command switch.

Lines indicate the type
of connection between
two devices, such as
lightning bolts are
Gigastack GBIC
connections.

Switch202

Right-click a line to
display the link pop-up
menu, and select an
option to display link
information.

54503

Device label identifies
the switch.

Status bar shows that
Cluster Builder is
displayed.

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide
78-6511-05

2-23

Chapter 2

Getting Started with CMS

Cluster View and Cluster Builder

Topology
The topology appears when you launch use Cluster View and Cluster Builder. It
displays connected clusters, command switches, cluster members, candidate
switches, and edge devices. From the topology, you can:

Double-click a cluster icon (double-switch icon) to display cluster members.

Select a command-switch icon to configure cluster-wide settings.

Select a switch icon to configure switch-wide settings.

The topology in Cluster View (Figure 2-5) and Cluster Builder (Figure 2-6) uses
the same icons used in the Cluster Manager cluster tree (Figure 2-2). It also uses
an icon unique to the topology. This icon is the unknown device icon. Figure 2-7
shows the device icons as they appear in the topology. Table 2-12 describes the
meanings of the icon colors.
Figure 2-7

Cluster View and Cluster Builder Device Icons

Table 2-12 Icon Colors

Icon Color

Color Meaning

Green

Device is up.

Red

Device is down.

Yellow

Fault indication.

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide

2-24

78-6511-05

Chapter 2

Getting Started with CMS
Cluster View and Cluster Builder

The topology includes device labels, which are the switch cluster names, cluster
member names, and MAC addresses (Figure 2-6). Table 2-13 describes the
meanings of the label colors. You can toggle device labels by selecting
View > Toggle Labels.
Table 2-13 Device Label Colors

Label Color

Color Meaning

Green

A cluster member, either a member switch or the command switch.

Cyan

A cluster candidate that is fully qualified to become a cluster member. Add these
candidates with Cluster Builder.

White

A standby command switch.

Yellow

An unknown edge device that cannot become a member.
The link icons in the topology describe the link type and status between two
devices. Figure 2-8 shows the device icons as they appear in the topology.
Table 2-14 describes the meanings of the link colors. When you point your cursor
at a link and right-click, you can display additional link information from the link
pop-up menu (Figure 2-6). Complete descriptions of the icons and icon colors are
available from Help > Legend.

Figure 2-8

Red

Blue
Red
and
and
yellow yellow

Gray
and
black

54566

Blue

Cluster View and Cluster Builder Link Icons

Table 2-14 Link Colors

Link Color

Color Meaning

Blue

Active link

Red

Blocked link

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide
78-6511-05

2-25

Chapter 2

Getting Started with CMS

Cluster View and Cluster Builder

Menu Bar
The Cluster View and Cluster Builder menu bar provides the options for
configuring and monitoring a switch cluster. Table 2-15 describes the Cluster
View and Cluster Builder menu bar options and their function.
Table 2-15 Cluster View and Cluster Builder Menu

Menu Bar Options

Task

Cluster

Add to cluster

Add candidates to cluster.

Remove from cluster

Remove members from cluster.

User Settings

Change the default settings for the number of hops to discover and the
polling interval for Cluster Builder and the link graphs.

Goto Cluster Manager

Start Cluster Manager.

Views

Toggle Views

Toggle between Cluster Builder and Cluster View.

Toggle Labels

Toggle between switch names and IP or MAC addresses and connected
port numbers.

Device

Launch Switch
Manager

Start Switch Manager for a selected switch.

Bandwidth Graph

Display a graph showing the current bandwidth in use by a selected switch.
Not supported on Catalyst 1900 and Catalyst 2820 switches.

Show/Hide Candidates

Expand or collapse image of all candidates connected to a cluster member.

Host Name
Configuration

Change the host name for a selected device.

Link

Link Graph

Display a graph showing the bandwidth being used for the selected link.

Link Report

Display the Link Report for two connected devices. If one device is an
unknown device, candidate switch, or Catalyst 1900 or Catalyst 2820
switch, only the cluster member side of the link is displayed.

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide

2-26

78-6511-05

Chapter 2

Getting Started with CMS
Cluster View and Cluster Builder

Table 2-15 Cluster View and Cluster Builder Menu (continued)

Menu Bar Options

Task

Options

Save Layout

Save the current arrangement in the topology.

Save Configuration

Save the current configuration of cluster members to Flash memory.

Help

Contents

List all of the available online help topics.

Legend

Display descriptions of the icons used in the topology.

About

Display the version number for Cluster Builder and Cluster View.

Toolbar
The Cluster Builder and Cluster View toolbar (Figure 2-9) buttons display some
cluster-level configuration windows. Hover the cursor over a button to display a
pop-up description. From left to right on the toolbar, the following windows can
be displayed:

Launch Cluster Manager.

Toggle between Cluster Builder and Cluster View—You can also use Cluster
Builder and Cluster View to manage your cluster. When you are using Cluster
Builder, click the double-switch icon on the toolbar (Figure 2-9) to toggle
back to Cluster Manager.

Toggle between switch names and IP or MAC addresses and connected port
numbers.

Save the arrangement of the cluster icons as you have arranged them.

Save the current configuration for all cluster members to Flash memory.

Set the user settings for Cluster Builder and Cluster View.

Display the legend that describes the icons, labels, and links that are used in
Cluster Builder and Cluster View.

List the online help topics for Cluster Builder and Cluster View.

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide
78-6511-05

2-27

Chapter 2

Getting Started with CMS

Cluster View and Cluster Builder

Figure 2-9

Cluster Builder and Cluster View Toolbar

Move the cursor over
the icon to display the
tool tip. For example,
the ? button displays
Help Contents.

54512

Switch202

Device Pop-Up Menu
Table 2-16 describes the menu options available when you right-click an icon in
Cluster View.
Table 2-16 Cluster View Device Menu

Menu Option

Action

Device Web Page

Displays the web management page for the device.

Disqualification Code

Describes why the switch is not a cluster member or
candidate.

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide

2-28

78-6511-05

Chapter 2

Getting Started with CMS
Cluster View and Cluster Builder

Candidate, Member, and Link Pop-Up Menus
Table 2-17 describes the menu options available when you right-click a
candidate-switch icon in Cluster Builder.
Table 2-17 Cluster Builder Candidate Pop-up Menu

Menu Option

Action

Device Web Page Displays the device-management page for the device.
Add to Cluster

Adds the selected candidate or candidates to the cluster.

Table 2-18 describes the menu options available when you right-click a
member-switch icon in Cluster Builder. For more information about configuring
cluster members, see Chapter 5, “Clustering Switches.”
Table 2-18 Cluster Builder Member Pop-up Menu

Menu Option

Action

Switch Manager

Display the VSM Home page for the selected device.

Bandwidth Graph

Display a graph that plots the total bandwidth used by
the switch. This feature is not available on
Catalyst 1900 or Catalyst 2820 switches.

Host Name Config

Change the name of the switch. For more information,
see the “Host Names” section on page 5-10.

Remove from Cluster

Remove the selected switch from the cluster.

Show or hide
Candidates

Toggle between displaying candidate switches and not
displaying them.

Clear State

Return switches that were down but are now up to the
green (up) state. Switches that are yellow are down or
were previously down. Applicable only to yellow
member switches.

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide
78-6511-05

2-29

Chapter 2

Getting Started with CMS

Cluster View and Cluster Builder

Table 2-19 describes the menu options available when you right-click a link in
Cluster Builder. For more information about displaying link information, refer to
the online help.
Table 2-19 Cluster Builder Link Pop-up Menu

Menu Option

Action

Link Graph

Display the performance graph for the link. One end of the
link must be connected to a port on a cluster member that is a
Catalyst 2900 XL or Catalyst 3500 XL switch. Links
between any mix of Catalyst 1900 and Catalyst 2820
switches cannot be graphed.

Link Report

Display information about the link between two members. If
one end of the link is a candidate, the report only displays
information about the member switch.

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide

2-30

78-6511-05

Chapter 2

Getting Started with CMS
CMS Window Components

CMS Window Components
CMS windows use consistent techniques to present configuration information.
Figure 2-10 shows the components of a typical CMS window.
Figure 2-10 CMS Window Components

Click a tab to display more
information.
Cluster members are listed
in the device list.
Click in a row to select it.
OK saves the changes you
have made and closes the
window.
Apply saves the changes
you have made and leaves
the window open.
Modify displays a pop-up
for the selected row.

32676

Cancel closes the window
without saving the changes.
Help displays help for the
current window and the
menu of Help topics.

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide
78-6511-05

2-31

Chapter 2

Getting Started with CMS

CMS Window Components

Host Name List
The Host Name drop-down list (also referred to as the Device list) shows a list of
cluster member names. To display or change the configuration of a specific switch
in a cluster, select the switch name. The current configuration settings of that
switch appear.
In some cases, switch-specific features (such as the LRE profiles on the
Catalyst 2900 LRE XL switches) are available only when the appropriate switch
is a member of the cluster. Otherwise, switch-specific features either are
grayed-out or are not shown in the CMS menu bar and pop-up menus.
In other cases, depending on the menu option selected, certain cluster members
names are not included in the Host Name list. For example, the VLAN
Membership window would not display Catalyst 1900 and Catalyst 2820
switches, even though they are part of the cluster.

Tabs
Some CMS windows have multiple tabs that present different kinds of
information. Tabs are arranged like folder headings across the top of the window.
Click the tab to display a new screen, and click Apply to save information on all
tabs but without closing the window.

Lists
Listed information can often be changed by selecting an item from a list. To
change the information, select one or more items, and click Modify. Changing
multiple items is limited to those items that apply to at least one of the selections.
For example, when you select multiple ports, a parameter such as flow control is
grayed out if the ports are not Gigabit Ethernet ports.

Tips

If you try to select a port or device in Cluster Manager while another CMS
window is open, the computer issues a ringing bell sound. Rearrange the
windows that are displayed to find the open window, and close it to proceed.

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide

2-32

78-6511-05

When you close the pop-up. Online Help CMS provides comprehensive online help to assist you in understanding and performing configuration and monitoring tasks from the CMS windows (Figure 2-11). provides descriptions of all window components (fields. and so on) and procedures on performing tasks from the window. provides background information and concepts on the features. and leave the window open. We appreciate and value your comments. From the menu bar. buttons. available from the Help button on the VSM and Cluster Manager windows. You can send us feedback about the information provided in the online help. You usually select an item from a list or table and click Modify. click Submit to send your comments to Cisco. • Feature help. • Index of help topics. and close the window. available from all menu bars by selecting Help > Contents. select Help > Contents. and click Feedback to display a simple online form. Cancel Do not save any changes made in the window. and close the window. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 2-33 . Modify Display the pop-up for changing information on the selected item or items. After completing the form. Apply Save any changes made in the window. • Dialog-specific help.Chapter 2 Getting Started with CMS CMS Window Components Buttons Table 2-20 describes the most common buttons that you use to change the information in a CMS window: Table 2-20 Common CMS Buttons Button Description OK Save any changes made in the window. the original window appears.

Feature help. Click Feedback to send us your comments about the online help. and click Find.Chapter 2 Getting Started with CMS CMS Window Components Figure 2-11 Help Contents Click Back and Forward to redisplay previously displayed pages. Enter the first letters of the topic. Dialog-specific help. 4567 Click a topic under the Contents or Index tab. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 2-34 78-6511-05 .

You can assign this information to the switch in the following ways: • Using the setup program. including browser and Java plug-in configurations. Accessing CMS also requires meeting the software requirements.HTML access to the command line interface from a cached copy of the Cisco Systems Access page.Chapter 2 Getting Started with CMS Accessing CMS Accessing CMS You must know the IP address and password of the specific switch or command switch to access CMS. A password is not required to redisplay these pages. To prevent unauthorized access to CMS and the CLI. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 2-35 . You can access the CLI by clicking Web Console . described in the release notes. Considerations for assigning this information to a command switch and cluster members are described in the “IP Addresses” section on page 5-8 and “Passwords” section on page 5-8. as described in the “Changing IP Information” section on page 6-2 and “Changing the Password” section on page 6-15. Note Copies of the CMS pages you display are saved in your browser memory cache until you exit the browser session. including the Cisco Systems Access page. exit your browser to end the browser session. as described in the release notes • Manually assigning an IP address and password.

follow these steps: Step 1 Enter the IP address in the browser Location field (Netscape Communicator) or Address field (Microsoft Internet Explorer). To access CMS. If you access CMS from a standalone or cluster member switch. Step 3 Click Cluster Management Suite or Visual Switch Manager. VSM appears. you cannot access CMS.Chapter 2 Getting Started with CMS Accessing CMS The following procedure assumes you have met the software requirements. If you access CMS from a command switch. see the “HTTP Access to CMS” section on page 4-5. (including browser and Java plug-in configurations) and have assigned IP information and a password to the switch or command switch. as described in the release notes. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 2-36 78-6511-05 . which is the default HTTP port. You can select Cluster Manager to launch by default by selecting Cluster > User Settings. If you change the HTTP port. CMS requires that your switch uses Hypertext Transfer Protocol (HTTP) port 80. You can toggle between Cluster Builder and Cluster View by selecting View > Toggle Views. Step 2 Enter your userid and the password at the prompt. For information about managing passwords in switch clusters. You can display VSM for a specific cluster member from either Cluster Builder or Cluster View by selecting Device > Launch Switch Manager. see the “Passwords” section on page 5-8. For more information about the HTTP port. Cluster Builder launches by default. The Cisco Systems Access page appears. You cannot display VSM from Cluster Manager.

Chapter 2 Getting Started with CMS Saving Configuration Changes Saving Configuration Changes The front-panel images and CMS windows always display the running configuration of the switch. The change does not automatically become part of the config. you must select System > Save Configuration in the Cluster Manager menu bar or Options > Save Configuration in the Cluster Builder or Cluster View menu bar. To save all configuration changes to Flash memory. If you do not save your changes to Flash memory. Note As you make cluster configuration changes (except for changes to the topology and in the User Settings window). they are lost when the switch restarts. which is the startup configuration used each time the switch restarts. the change becomes part of the running configuration. make sure you periodically save the configuration.txt file in Flash memory. The configuration is saved on the command and member switches. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 2-37 . Note Catalyst 1900 and Catalyst 2820 switches automatically save configuration changes to Flash memory as they occur. When you make a configuration change to a switch or switch cluster.

Other CMS features such as Cluster Manager. which is referred to as Switch Manager on these switches. a new CMS session is launched. including required browser versions. and Catalyst 2950 switches use the same version of the CMS interface. and accessing CMS. the interfaces can differ. and the name of the CMS window from which you can configure the feature. • The Catalyst 1900 and Catalyst 2820 switches use an older interface version of VSM. thus. and the web-based management software specific to that switch appears. such as the Catalyst 2950. and Catalyst 2820 switches. Cluster Builder. Refer to the release notes for hardware and software requirements. Refer to the release notes for the list of Catalyst desktop switches that are cluster-compatible and their software versions. Catalyst 3500 XL. gives the page number in this guide where the feature is described. and for procedures for installing the required Java plug-in. Catalyst 1900. Refer to the online help for CMS procedures and window descriptions. configuring your browser. certain models of the Catalyst desktop switches support different versions of web-based management software. and Cluster View are not available on these switches. Where to Go Next The rest of this guide provides descriptions of the software features and general switch administration.Chapter 2 Getting Started with CMS Using Different Versions of Web-Based Switch Management Software Using Different Versions of Web-Based Switch Management Software Cluster command switches can manage a mixture of Catalyst desktop switches. However. Keep in mind that when you select a switch image or switch icon and then select Device > Launch Switch Manager from the menu bar. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 2-38 78-6511-05 . Refer to the appropriate switch documentation for descriptions of the web-based management software used on other Catalyst desktop switches. • The Catalyst 2900 XL. Table 4-2 on page 4-9 lists the defaults for all key features.

It has been enhanced to support a set of features for the Catalyst 2900 XL and Catalyst 3500 XL switches. If you have never used IOS software or if you need a refresher. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 3-1 . take a few minutes to read this chapter before reading the rest of this guide.C H A P T E R 3 Getting Started with the CLI This chapter provides information that you should know before using the Cisco IOS command-line interface (CLI). The Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference provides complete descriptions of these commands. This guide provides procedures for using only the commands that have been created or changed for these switches.0(5). • Command usage basics • Command-line error messages • Accessing the CLI • Saving configuration changes This switch software release is based on Cisco IOS Release 12.0 documentation on Cisco. For information about the standard Cisco IOS Release 12. refer to the Cisco IOS Release 12.0 commands.com.

Normally. The commands available to you at any given time depend on which mode you are in. To access all commands and modes. you can enter interface and line configuration modes. From privileged mode. From global configuration mode. The switch supports the following command modes: • User EXEC • Privileged EXEC • VLAN database • Global configuration • Interface configuration • Line configuration When you start a session on the switch. which clear counters or interfaces. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 3-2 78-6511-05 . You can use the virtual LAN (VLAN) database and the various configuration modes to make changes to the running configuration. such as show commands. Most of the EXEC commands are one-time commands. which show the current configuration status. you must start at global configuration mode. you begin in user mode. you must first enter privileged EXEC mode. often called user EXEC mode. a password is required to enter privileged EXEC mode. Entering a question mark (?) at the system prompt provides a list of commands for each command mode.Chapter 3 Getting Started with the CLI Command Usage Basics Command Usage Basics This section provides the following topics: • Accessing command modes • Abbreviating commands • Using the No and Default forms of commands • Redisplaying a command • Getting help Accessing Command Modes The CLI is divided into different modes. To access the various configuration modes. you can enter any EXEC command or enter global configuration mode. which has only a limited subset of the commands. and clear commands.

• Perform basic tests. switch# Enter disable to exit. • Display system information. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 3-3 . VLAN database Enter the vlan database command while in privileged EXEC mode. For example. Use a password to protect access to this mode. Use this mode to • Change terminal settings. the prompt you see in that mode. Use this mode to configure VLAN-specific parameters. Table 3-1 Command Modes Summary Modes Access Method Prompt Exit Method About This Mode1 User EXEC Begin a session with your switch. Privileged EXEC Enter the enable command while in user EXEC mode. the interface command is used only from global configuration mode. switch> Enter logout or quit.Chapter 3 Getting Started with the CLI Command Usage Basics Each command mode supports specific Cisco IOS commands. Use this mode to verify commands you have entered. enter exit. and how to exit the mode. switch(vlan)# To exit to privileged EXEC mode. Table 3-1 describes how to access each mode. The examples in the table use the host name switch.

Abbreviating Commands You can abbreviate commands and keywords to the number of characters that allow a unique abbreviation. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 3-4 78-6511-05 . Use this mode to configure parameters that apply to your switch as a whole. For any of the modes. you can abbreviate the show command to sh or the show configuration command to show conf. enter exit or end. Interface Enter the interface configuration command (with a specific interface) while in global configuration mode. For example. Line Specify a line with configuration the line vty or line console command while in global configuration mode. To exit to privileged EXEC mode. or press Ctrl-Z. switch(config-if)# To exit to global configuration mode. switch(config)# To exit to privileged EXEC mode. enter exit. Use this mode to configure parameters for the terminal line. enter Ctrl-Z or end. Use this mode to configure parameters for the Ethernet interfaces. enter Ctrl-Z or end. you can see a comprehensive list of the available commands by entering a question mark (?) at the prompt. enter exit.Chapter 3 Getting Started with the CLI Command Usage Basics Table 3-1 Command Modes Summary (continued) Prompt Exit Method About This Mode1 Global Enter the configure configuration command while in privileged EXEC mode. 1. To exit to global configuration mode. switch(config-line)# Modes Access Method To exist to privileged EXEC mode.

the no shutdown command reverses the shutdown of an interface.Chapter 3 Getting Started with the CLI Command Usage Basics Using the No and Default Forms of Commands Almost every configuration command has a no form. You can continue to press the up-arrow key for more commands. Redisplaying a Command To redisplay a command you previously entered. a command. a keyword. • Reset a command to its default values. switch> help • abbreviated-command-entry?—Obtain a list of commands that begin with a particular character string. use the no form to • Disable a feature or function. Configuration commands can also have a default form. Use the command without the no form to reenable a disabled feature or to reverse the action of a no command. For example. switch> dis? switch> disable disconnect Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 3-5 . or an argument: • help—Obtain a brief description of the help system in any command mode. The following are the commands to get help specific to a command mode. The default form of a command returns the command setting to its default. Getting Help Entering a question mark (?) at the system prompt displays a list of commands for each command mode. In general. You can also get a list of any command’s associated keywords and arguments with the context-sensitive help feature. • Reverse the action of a command. press the up-arrow key.

switch> ? • command ?—List of command keywords. switch> show udld ? FastEthernet FastEthernet IEEE 802. switch# sh conf<tab> switch# sh configuration • ? — List all commands available for a particular command mode. keywords.Chapter 3 Getting Started with the CLI Command Usage Basics • Note abbreviated-command-entry<Tab>—Complete a partial command name. enter those characters followed immediately by the question mark (?). No space before tabbing. To obtain a list of commands that begin with a particular character sequence. enter a question mark (?) in place of a keyword or argument. To list keywords or arguments. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 3-6 78-6511-05 . the space (or lack of a space) before the question mark (?) is significant. because it completes a word for you. and arguments you already have entered. Include a space before the ?. This form of help is called command syntax help. Do not include a space. switch> show ? • command keyword ?— List of command keyword arguments. because it reminds you which keywords or arguments are applicable based on the command. This form of help is called word help.3 Null Null interface VLAN Switch VLAN Virtual Interface When using context-sensitive help.

Reenter the command followed by a space and a question mark (?). You entered the command incorrectly. Reenter the command followed by a space and a question mark (?). The possible keywords that you can enter with the command appear. % Invalid input detected at ‘^’ marker. Enter a question mark (?) to display all of the commands that are available in this command mode. The possible keywords that you can enter with the command appear. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 3-7 . % Incomplete command. The caret (^) marks the point of the error. The possible keywords that you can enter with the command appear. Table 3-2 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.Chapter 3 Getting Started with the CLI Command-Line Error Messages Command-Line Error Messages Table 3-2 lists some error messages that you might encounter while using the CLI. You did not enter all of the keywords or values required by this command.

and the switch must have an enable secret password configured. see the “SNMP Network Management Platforms” section on page 4-6. tip. the User EXEC prompt appears on the management station. or minicom) on the management station. For information about connecting to the console port. as described in the release notes • Manually assigning an IP address and password. • Using any Telnet TCP/IP package from a remote management station. follow these steps: Step 1 Start up the emulation software (such as ProComm. 8 data bits. as described in the “Changing IP Information” section on page 6-2 and “Changing the Password” section on page 6-15. Step 3 Establish a connection with the switch by either • Connecting the switch console port to a management station or dial-up modem. reconfigure the terminal-emulation software to match the switch console port settings (default settings are 9600 baud. You can assign this information to the switch in the following ways: • Using the setup program. For information about configuring the switch for Telnet access. and 1 stop bit). After you connect through the console port or through a Telnet session.Chapter 3 Getting Started with the CLI Accessing the CLI Accessing the CLI The following procedure assumes you have already assigned IP information and password to the switch or command switch. The switch supports up to seven simultaneous Telnet sessions. no parity. Considerations for assigning this information to a command switch and cluster members are described in the “IP Addresses” section on page 5-8 and “Passwords” section on page 5-8. refer to the switch hardware installation guide. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 3-8 78-6511-05 . Changes made by one Telnet user are reflected in all other Telnet sessions. To access the CLI. Step 2 If necessary. HyperTerminal. The switch must have network connectivity with the Telnet client.

You can also access the CLI by clicking Web Console . Step 2 In the URL field. as described in the release notes. A password is not required to redisplay these pages. including the Cisco Systems Access page. exit your browser to end the browser session. follow these steps: Step 1 Start one of the supported browsers. Note Copies of the CMS pages you display are saved in your browser memory cache until you exit the browser session.HTML access to the command line interface from the Cisco Systems Access page. click Telnet to start a Telnet session. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 3-9 . You can access the CLI by clicking Web Console .HTML access to the command line interface from a cached copy of the Cisco Systems Access page.Chapter 3 Getting Started with the CLI Accessing the CLI Accessing the CLI from a Browser The following procedure assumes you have met the software requirements. To access the CLI from a web browser. Step 3 When the Cisco Systems Access page appears. For information about the Cisco Systems Access page. enter the IP address of the command switch. see the “Accessing CMS” section on page 2-35 and the release notes. The User EXEC prompt appears on the management station. (including browser and Java plug-in configurations) and have assigned IP information and a Telnet password to the switch or command switch. To prevent unauthorized access to CMS and the CLI. Step 4 Enter the switch password.

Note The write memory command does not apply to the Catalyst 1900 and Catalyst 2820 switches. Refer to the Cisco IOS Release 12. which automatically save configuration changes to Flash memory as they occur. When you make a configuration change to a switch or switch cluster.txt file in Flash memory. Table 4-2 on page 4-9 lists the defaults for all key features and gives the page numbers in this guide where the feature is described and CLI procedures are provided. Tips As you make cluster configuration changes. make sure you periodically save the configuration. The configuration is saved on the command and member switches. To save all configuration changes to Flash memory. they are lost when the switch restarts. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 3-10 78-6511-05 .0 commands.Chapter 3 Getting Started with the CLI Saving Configuration Changes Saving Configuration Changes The show command always displays the running configuration of the switch. Where to Go Next The rest of this guide provides descriptions of the software features and general switch administration. you must enter the write memory command in privileged EXEC mode. which is the startup configuration used each time the switch restarts.com for information about the standard Cisco IOS Release 12. If you do not save your changes to Flash memory. The change does not automatically become part of the config. Refer to the Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference for complete descriptions of the switch commands.0 documentation on Cisco. the change becomes part of the running configuration.

C H A P T E R 4 General Switch Administration This chapter provides the following switch administration topics: • Basic IP connectivity to the switch • Switch software releases • Console port access • Hypertext Transfer Protocol (HTTP) access • Telnet access • Simple Network Management Protocol (SNMP) network management platforms • Default settings of key software features Refer to the release notes for information about starting up the switch: • Software and hardware requirements and compatibility • Browser and Java plug-in configurations • Setup program Also refer to the release notes about switch upgrades.com.0 commands. refer to the Cisco IOS Release 12.0 documentation on Cisco. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 4-1 . For information about the standard Cisco IOS Release 12.

Before upgrading a switch. For information about running the setup program and assigning basic information to the switch. you can run the switch on its default settings or configure any settings to meet your network requirements. refer to the release notes. Switch Software Releases The switch software is regularly updated with new features and bug fixes. Knowing the software version is also important for compatibility reasons. You can do this by using the Software Upgrade window. Cisco also supplies a TFTP server that you can download from Cisco. or by using the show version command.Chapter 4 General Switch Administration Basic IP Connectivity to the Switch Basic IP Connectivity to the Switch The switch uses IP address information to communicate with the local routers and the Internet. first find out the version of the software that the switch is running.com. Refer to the release notes for the following information: • Compatibility requirements • Upgrade guidelines and procedures and software reload information Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 4-2 78-6511-05 . by selecting Help > About. New software releases are posted on Cisco. IP information is • Switch IP address • Subnet mask (IP netmask) • Default gateway (router) Once IP information is assigned. especially for switch clusters. and you might want to upgrade your Catalyst 2900 XL and Catalyst 3500 XL with the latest software release. it runs a setup program that prompts you enter this information. You need it if you plan to use the CMS to configure and manage the switch. The first time that you access the switch. The switch also requires a secret password.com on the World Wide Web and are available through authorized resellers.

• Stop bits default is 1. These are the default settings of the switch console port: • Baud rate default is 9600. • Data bits default is 8. see the “Saving Configuration Changes” section on page 3-10. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 4-3 . see the “Saving Configuration Changes” section on page 2-37. Make sure that you save any changes you make to the switch console port settings to Flash memory. For information about saving changes from the CLI. Be sure that the switch console port settings match the settings of the terminal or PC. For information about connecting to the switch console port.Chapter 4 General Switch Administration Console Port Access Console Port Access The switch console port provides switch access to a directly-attached terminal or PC or to a remote terminal or PC through a serial connection and a modem. • Parity settings default is None. Note If the data bits option is set to 8. refer to the switch hardware installation guide. For information about saving changes from CMS. set the parity option to None.

The 0 and 15 mean that you are configuring all 16 possible Telnet sessions. Information about accessing the CLI through a Telnet session is provided in the “Accessing the CLI” section on page 3-8. follow these steps: Command Step 1 Purpose Attach a PC or workstation with emulation software to the switch console port. The default data characteristics of the switch console port are 9600. 1. The password is listed under the command line vty 0 15 Step 8 copy running-config startup-config (Optional) Save the running configuration to the startup configuration. 8. Step 5 password <password> Enter a enable secret password. When the command line appears. no parity. Step 7 show running-config Display the running configuration. go to Step 2. Step 4 line vty 0 15 Enter the interface configuration mode for the Telnet interface. Step 6 end Return to privileged EXEC mode so that you can verify the entry.Chapter 4 General Switch Administration Telnet Access to the CLI Telnet Access to the CLI The following procedure assumes you have assigned IP information and a Telnet password to the switch or command switch. Step 3 config terminal Enter global configuration mode. Step 2 enable Enter privileged EXEC mode. To configure the switch for Telnet access. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 4-4 78-6511-05 . as described in the release notes. There are 16 possible sessions on a command-capable switch.

You might want to write down the port number to which you are connected. For information about connecting to a switch port. you cannot use CMS. refer to the switch hardware installation guide. CMS requires that your switch uses HTTP port 80. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 4-5 . which is an in-band form of communication with the switch through any one of its Ethernet ports and that allows switch management from a standard web browser.Chapter 4 General Switch Administration HTTP Access to CMS HTTP Access to CMS CMS uses Hypertext Transfer Protocol (HTTP). which is the default HTTP port. Do not disable or otherwise misconfigure the port through which your management station is communicating with the switch. which includes assigning a privilege-level 15 password for accessing CMS • Installing the required Java plug-in • Configuring your web browser • Displaying the Cisco Systems Access page You can also refer to the “Accessing CMS” section on page 2-35. Note If you change the HTTP port. Refer to the following topics in the release notes for information about accessing CMS: • System requirements • Running the setup program. Changes to the switch IP information should be done with care.

the IEEE 802.0 are network-management applications you can use to configure. For more information. and four Remote Monitoring (RMON) groups. the command switch manages communication between the SNMP management station and all switches in the cluster. and statistics.1D bridge MIB. CiscoWorks2000 and CiscoView 5. which this IOS software release supports. see the “Using SNMP to Manage Switch Clusters” section on page 5-22.Chapter 4 General Switch Administration SNMP Network Management Platforms SNMP Network Management Platforms You can manage switches by using an Simple Network Management Protocol (SNMP)-compatible management station running such platforms as HP OpenView or SunNet Manager. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 4-6 78-6511-05 . The four supported groups are alarms. history. and troubleshoot Catalyst 2900 XL and Catalyst 3500 XL switches. note that certain combinations of port features create configuration conflicts. This section describes how to access MIB objects to configure and manage your switch. monitor. For information about managing cluster switches through SNMP. It provides the following information: • Using File Transfer Protocol (FTP) to access the MIB files • Using SNMP to access the MIB variables In a cluster configuration. The switch supports a comprehensive set of Management Information Base (MIB) extensions and MIB II. events. When configuring your switch by using SNMP. You can configure these groups by using an SNMP application or by using the CLI. see the “Avoiding Configuration Conflicts” section on page 9-2.

Chapter 4 General Switch Administration SNMP Network Management Platforms Using FTP to Access the MIB Files You can obtain each MIB file with the following procedure: Step 1 Use FTP to access the server ftp.com. Step 2 Log in with the username anonymous. an application-layer protocol facilitating the exchange of management information between network devices. Step 4 At the ftp> prompt. The SNMP system consists of three parts: • The SNMP manager. Using SNMP to Access MIB Variables The switch MIB variables are accessible through SNMP. which resides on the switch • The MIBs that reside on the switch but that can be compiled with your network management software Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 4-7 . Step 5 Change directories to one of the following: Step 6 • wsc2900xl for a list of Catalyst 2900 XL MIBs • wsc3500xl for a list of Catalyst 3500 XL MIBs Use the get MIB_filename command to obtain a copy of the MIB file.cisco.cisco. change directories to /pub/mibs/supportlists. You can also access this server from your browser by entering the following URL in the Location field of your Netscape browser (the Address field in Internet Explorer): ftp://ftp.com Use the mouse to navigate to the folders listed above. Step 3 Enter your e-mail username when prompted for the password. which resides on the network management system (NMS) • The SNMP agent.

which receives and processes the traps. get-next-request. As shown in Figure 4-1. Set-request NMS Get-response. and set-request sent by an NMS. the SNMP agent gathers data from the MIB.1 get-response Replies to a get-request. or notification of certain events. and set-request format. SNMP Network Get-request. Get-bulk. get-next-request Retrieves a value from a variable within a table. Traps are messages alerting the SNMP manager to a condition on the network such as improper user authentication.Chapter 4 General Switch Administration SNMP Network Management Platforms An example of an NMS is the CiscoWorks network management software. verify the configuration of devices. A sequential search is performed to find the needed variable from within a table. trap An unsolicited message sent by an SNMP agent to an SNMP manager indicating that some event has occurred. The agent can send traps. traps SNMP Manager Table 4-1 Network device MIB SNMP Agent S1203a Figure 4-1 SNMP Operations Operation Description get-request Retrieves a value from a specific variable. 1. With this operation. get-next-request. The results of a poll can be displayed as a graph and analyzed to troubleshoot internetworking problems. In addition. an SNMP manager does not need to know the exact variable name. and more. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 4-8 78-6511-05 . which is the repository for information about device parameters and network data. increase network performance. Get-next-request. restarts. set-request Stores a value in a specific variable. CiscoWorks2000 software uses the switch MIB variables to set device variables and to poll devices on the network for specific information. monitor traffic loads. The SNMP manager uses information in the MIB to perform the operations described in Table 4-1. link status (up or down). the SNMP agent responds to MIB-related queries sent by the SNMP manager in get-request. and so forth. to the SNMP manager.

Creating a cluster None “Creating a Switch Cluster” section on page 5-13. Adding and removing None cluster members “Adding and Removing Cluster Members” section on page 5-14. you can configure the switch through its various management interfaces. If you have specific network needs. VSM Cluster Management Enabling a command switch None Cluster > Cluster Command Configuration No CLI procedure provided. Cluster Builder No CLI procedure provided. No CLI procedure provided. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 4-9 . and where you can configure them from the command-line interface (CLI) and Cluster Management Suite (CMS). requiring only that you assign basic IP information to the switch and connect it to the other devices in your network. Table 4-2 Default Settings and Where To Change Them Feature Default Setting Concepts and CLI Procedures CMS Option “Designating and Enabling a Command Switch” section on page 5-14. see the “Basic IP Connectivity to the Switch” section on page 4-2 and the release notes. For information about assigning basic IP information to the switch.Chapter 4 General Switch Administration Default Settings Default Settings The switch is designed for plug-and-play operation. their defaults. their page numbers in this guide. Creating a standby command switch group None “Designating and Enabling Standby Command Switches” section on page 5-17. Cluster Builder Cluster > Add to Cluster and Cluster > Remove from Cluster Cluster Manager: Cluster > Standby Command Configuration No CLI procedure provided. Table 4-2 lists the key software features.

Documentation set for Cisco IOS Release 12. Cisco Discovery Protocol (CDP) Enabled “Configuring CDP” section on page 6-22.Chapter 4 General Switch Administration Default Settings Table 4-2 Default Settings and Where To Change Them (continued) Default Setting Feature Upgrading cluster software Enabled Concepts and CLI Procedures CMS Option “Switch Software Releases” section on page 4-2.0 on Cisco.0 on Cisco. – Documentation set for Cisco IOS Release 12. Management Device Management Switch IP address. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 4-10 78-6511-05 .0. Management VLAN VLAN 1 “Management VLANs” section on page 8-4.com.0.0 “Changing IP Information” section on page 6-2. Dynamic Host DHCP Configuration Protocol client is (DHCP) enabled “Using DHCP-Based Autoconfiguration” section on page 6-4. Cluster Manager Cluster > Management VLAN Domain name None “Configuring the Domain Name and Cluster Manager the DNS” section on page 6-8.0 on Cisco. subnet mask.com. Cluster Manager System > IP Management – Documentation set for Cisco IOS Release 12.0 on Cisco.com.com Configuring SNMP None community strings and trap managers System > Software Upgrade “SNMP Community Strings” section Cluster Manager on page 5-10 and “Configuring System > SNMP SNMP” section on page 6-18. System > IP Documentation set for Cisco IOS Management Release 12. and default gateway 0.com. Cluster Manager Release notes on Cisco.

com. Cluster Manager VTP Management VTP server mode Cluster > VMPS Configuration VLAN > VTP Management Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 4-11 . Security > Address Documentation set for Cisco IOS Management Release 12.0 on Cisco. Cluster Manager Security > Address Management Voice configuration – “Configuring Voice Ports” section on – page 7-17. Cluster > System Time Documentation set for Cisco IOS Management Release 12. Documentation set for Cisco IOS Release 12.Chapter 4 General Switch Administration Default Settings Table 4-2 Default Settings and Where To Change Them (continued) Feature Address Resolution Protocol (ARP) Default Setting Enabled Concepts and CLI Procedures CMS Option “Managing the ARP Table” section on page 6-45. System Time Management None “Setting the System Date and Time” Cluster Manager section on page 6-17. Dynamic address management Enabled “Managing the MAC Address Tables” section on page 6-56. Cluster Manager “Configuring VTP” section on page 8-20. VLAN membership Staticaccess ports in VLAN 1 “Assigning VLAN Port Membership Cluster Manager Modes” section on page 8-7.0 on Cisco. Static address assignment None assigned “Adding Static Addresses” section on Cluster Manager page 6-59. VLAN > VLAN Membership VMPS Configuration – “How the VMPS Works” section on page 8-52.0 on Cisco.com.0 on Cisco. Cluster Manager System > ARP Table Documentation set for Cisco IOS Release 12.com.com.

” Cluster Manager Performance Configuring a port Duplex mode None • Auto on all 10/100 ports • Half duplex on all LRE ports Cluster Manager Port > Port “Changing the Port Speed and Duplex Configuration Mode” section on page 7-2. “Configuring the Switch Ports. LRE link speed and LRE port profiles LRE-10 “Configuring the LRE Ports” section Cluster Manager on page 7-22. Speed on 10/100 ports Auto Gigabit Ethernet flow control Port > Port Configuration and Device > LRE Profile (for LRE ports only) “Changing the Port Speed and Duplex Cluster Manager Mode” section on page 7-2 Port > Port Configuration Cluster Manager • Any on all Gigabit ports • Disabled on LRE ports in half-duplex mode. Port > Port enabled on LRE ports in full-duplex mode Configuration Note This option is configurable only on the Gigabit ports. “Configuring Flow Control on Gigabit Ethernet Ports” section on page 7-3.Chapter 4 General Switch Administration Default Settings Table 4-2 Default Settings and Where To Change Them (continued) Default Setting Feature Concepts and CLI Procedures CMS Option Chapter 7. Device > LRE Profile Configuration Inline power Auto “Configuring Inline Power on the – Catalyst 3524-PWR Ports” section on page 7-21 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 4-12 78-6511-05 .

– Network Port Disabled “Enabling a Network Port” section on – page 7-7. Cluster Manager Flooding Control Storm control Flooding unknown unicast and multicast packets Disabled Enabled Port > Flooding Control “Blocking Flooded Traffic on a Port” Cluster Manager section on page 7-6. Cluster Manager Multicast VLAN Registration (MVR) Disabled “Configuring MVR” section on page 6-49. – Spanning Tree Protocol Enabled “Configuring STP” section on page 6-24. Cluster Manager Unidirectional link detection Disabled “Configuring UniDirectional Link Detection” section on page 7-9. Hot Standby Router Protocol Disabled “Designating and Enabling Standby Command Switches” section on page 5-17.Chapter 4 General Switch Administration Default Settings Table 4-2 Default Settings and Where To Change Them (continued) Feature Default Setting Concepts and CLI Procedures CMS Option “Configuring Flooding Controls” section on page 7-4. – Port grouping None assigned “Creating EtherChannel Port Groups” Cluster Manager section on page 7-10. Port > Flooding Control Cisco Group Enabled Management Protocol (CGMP) “Controlling IP Multicast Packets through CGMP” section on page 6-46. Port > Port Grouping (EC) Device > Cisco Group Management Protocol (CGMP) Network Redundancy Device > Spanning Tree Protocol (STP) Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 4-13 .

0 Cluster Manager Security > Address Management “Adding Trap Managers” section on Cluster Manager page 6-19. – Documentation set for Cisco IOS Release 12.0.0.0 on Cisco.com. Trap manager 0.Chapter 4 General Switch Administration Default Settings Table 4-2 Default Settings and Where To Change Them (continued) Default Setting Feature Concepts and CLI Procedures CMS Option “Displaying an Inventory of the Clustered Switches” section on page 5-19 and “Displaying Link Information” section on page 5-20.0 on Cisco.com. Security Password None “Passwords” section on page 5-8 and – “Changing the Password” section on page 6-15. Cluster Manager Diagnostics Displaying graphs and Enabled statistics Port > Port Statistics and Port > Port Configuration > Runtime Status Cluster Builder Link > Link Graph and Link > Link Report Switch Port Analyzer (SPAN) port monitoring Disabled Console. and file logging Disabled Remote monitoring (RMON) Disabled “Enabling SPAN” section on page 7-16. “SNMP Network Management Platforms” section on page 4-6. buffer. Addressing security Disabled “Managing the MAC Address Tables” section on page 6-56. System > SNMP Management Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 4-14 78-6511-05 . Cluster Manager – – Port > Switch Port Analyzer (SPAN) Documentation set for Cisco IOS Release 12.

Documentation set for Cisco IOS Release 12. – Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 4-15 .Chapter 4 General Switch Administration Default Settings Table 4-2 Default Settings and Where To Change Them (continued) Feature Community strings Default Setting public Concepts and CLI Procedures CMS Option “SNMP Community Strings” section Cluster Manager on page 5-10 and “Entering System > SNMP Community Strings” section on Configuration page 6-19. Cluster Manager Security > Port Security Terminal Access Controller Access Control System Plus (TACACS+) Disabled “Configuring TACACS+” section on – page 6-61. Port security Disabled “Enabling Port Security” section on page 7-14. Protected port Disabled “Configuring Protected Ports” section on page 7-13.0 on Cisco.com.

Chapter 4 General Switch Administration Default Settings Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 4-16 78-6511-05 .

C H A P T E R 5 Clustering Switches This chapter provides the following topics to help you get started with switch clustering: • Switch cluster overview • Planning a switch cluster • Creating a switch cluster • Verifying a switch cluster • Using the command-line interface (CLI) to manage switch clusters • Using Simple Network Management Protocol (SNMP) to manage switch clusters Configuring switch clusters is more easily done from the Cluster Management Suite (CMS) web-based interface than through the CLI. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 5-1 . and for the the required software versions and browser and Java plug-in configurations. information in this chapter focuses on using CMS. For complete procedures on using CMS to configure switch clusters. Note Refer to the release notes for the list of Catalyst switches enabled for switch clustering. including which ones can be command switches and which ones can only be member switches. refer to the online help. “Getting Started with CMS.” for additional information about switch clusters and the clustering options. See Chapter 2. For the cluster commands. Therefore. refer to the Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference.

and the required software versions. • It is not a command or member switch of another cluster. Access lists are not usually used in configuring the Catalyst 2900 XL and Catalyst 3500 XL switches. • It belongs to the same management VLAN as the cluster member switches.0(5)XP or later. • No access lists have been defined for the switch because access lists can restrict access to a switch. The following sections list the requirements for the following cluster members: Note • Command switch • Standby command switches • Candidate and member switches Refer to the release notes for the list of Catalyst switches enabled for switch clustering. The switches can be in the same location.Chapter 5 Clustering Switches Understanding Switch Clusters Understanding Switch Clusters A switch cluster is a group of connected Catalyst desktop switches that are managed as a single entity. regardless of where they are located and how they are connected. or they can be distributed across a contiguous Layer 2 network. including which ones can be command switches and which ones can only be member switches. • It has an IP address. It identifies and controls all member switches in a cluster. 1 switch must be designated as the command switch and up to 15 switches can be member switches. In a switch cluster. The command switch is the single point of access used to configure. except for the access class 199 that is created when a device is configured as the command switch. All communication with cluster switches is through one IP address. You can designate one or more switches as standby command switches to avoid losing contact with cluster members if the command switch fails. • It has Cisco Discovery Protocol (CDP) version 2 enabled (the default). Command Switch Characteristics The command switch must meet the following requirements: • It is running Cisco IOS Release 12. manage. and monitor the member switches. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 5-2 78-6511-05 .

a switch must meet the following requirements: • It is running Cisco IOS Release 12. There is no limit to the number of switches you assign to a standby group. It can also have its own enable or enable secret password. • It is a member of the cluster. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 5-3 . but it is not required. Member switches are switches that have actually been added to a switch cluster. • It is in the same management VLAN as the active command switch. Note Before adding a candidate switch to the cluster.0(5)XP or later. • It has CDP version 2 enabled. • It is not an active member or the command switch of another cluster. • It is connected to a command switch through ports that belong to the same management VLAN (see the “Management VLAN” section on page 5-11). To be eligible for a standby group. a switch must meet the following requirements: • It is running cluster-capable software. • It is not a command or member switch of another cluster. For redundancy. To join a cluster. • It has CDP version 2 enabled.Chapter 5 Clustering Switches Understanding Switch Clusters Standby Command Switch Characteristics You can assign one or more switches to a standby group of command switches. you must know its enable or enable secret password. we also recommend that each standby command switch is cabled so that connectivity to cluster members is maintained. Candidate and Cluster Member Characteristics Candidate switches are cluster-capable switches that have not yet been added to a cluster. • It has its own IP address. A candidate or member switch can have its own IP address.

For example. cluster candidates.Chapter 5 Clustering Switches Planning a Switch Cluster Planning a Switch Cluster Anticipating conflicts and compatibility issues is a high priority when you manage several switches through a cluster. Cluster Builder cannot create a cluster that includes candidates that are connected to a Catalyst 5000 series or Catalyst 6000 switch connected to the command switch. The default is three hops. This section describes the following considerations. Refer to the release notes for software compatibility considerations and requirements on cluster-capable switches. the cluster is unable to discover candidates that are attached to that switch. and caveats that you should understand before you create the cluster. CDP must be enabled for the switch to discover and display the switch cluster and connected switch clusters. see the “Configuring CDP” section on page 6-22. a switch can automatically discover switches in star or cascaded topologies that are up to three cluster-enabled devices away from the edge of the cluster. or to disable the automatic display of suggested candidates. By using CDP. and neighboring edge devices. requirements. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 5-4 78-6511-05 . Automatic Discovery of Cluster Candidates The switch uses Cisco Discovery Protocol (CDP) to discover and display candidate switches that can be added to a cluster. When a switch that does support CDP but does not support clustering is connected to the command switch. You can configure the command switch to discover switches up to seven cluster-enabled devices away. CDP can still discover the candidate switches that are attached to it. To set the number of hops the command switch searches for candidate and member switches. When an edge device that does not support CDP is connected to the command switch. Note Do not disable CDP. For more information about CDP. select Cluster > User Settings.

The primary command switch receives member traffic destined for the virtual IP address.0(5)XU and higher supports a version of the Hot Standby Router Protocol (HSRP) so that you can configure a standby group of command switches. If HSRP is enabled and you use the command-switch IP address. but they cannot belong to a standby group. not through the command-switch IP address. You assign a unique virtual IP address to the standby group. The standby group of command switches are ranked according to a set of user-defined priorities. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 5-5 . To manage the standby group.0(5)XU can belong to clusters supported by standby command switches. The standby group is bound to the switch cluster so that the standby command switch becomes active if the primary command switch fails. IOS Release 12. you must access the primary command switch through the virtual IP address. A standby group is a group of switches that meet the requirements described in the “Standby Command Switch Characteristics” section on page 5-3. we strongly recommend that you configure a standby command switch to take over if the command switch fails. The member switch with the highest priority in the group is the standby command switch. Figure 5-1 shows a group of switches with a standby command switch. you will be prompted a second time for a password when you move between Cluster Builder and VSM. Switches are ranked first by the number of links they have and second by the switch speed. they are listed alphabetically. Note Catalyst 2900 XL and Catalyst 3500 XL switches running releases earlier than IOS Release 12. We also recommend redundant cabling from the standby command switch to the switch cluster. If switches have the same number of links and speed.Chapter 5 Clustering Switches Planning a Switch Cluster Standby Command Switches Because a command switch manages the forwarding of all communication and configuration information to all the cluster members.

Chapter 5 Clustering Switches Planning a Switch Cluster Figure 5-1 A Cluster with a Standby Command Switch Command switch Standby command switch Cluster Management Suite 1900/2820 member switches 33950 HTTP Catalyst 2900 and 3500 XL member switches Figure 5-2 shows a network cabled to allow the standby switch to maintain management contact with the member switches if the cluster command switch fails. Spanning Tree Protocol (STP) prevents the loops in such a configuration from reducing performance.20. Figure 5-2 Redundant Cabling to Support HSRP Virtual IP: 172.20.20.223 172.128.128.221 Standby command switch Member 1 33018 Member 3 Member 2 Member 4 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 5-6 78-6511-05 .222 Active command switch 172.128.

Chapter 5 Clustering Switches Planning a Switch Cluster To ensure that the standby command switch can take over the cluster if the primary command switch fails. the standby command switch assumes ownership of the virtual IP address and MAC address and begins acting as the command switch. If the primary command switch fails. The remaining switches in the standby group compare their assigned priorities to determine the new standby command switch. the primary command switch continually forwards cluster configuration information to the standby command switch. An automatic recovery procedure adds cluster members that were added to the cluster while the primary command switch was down. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 5-7 . When the primary command switch becomes active again. The standby command switch is informed of new cluster members but not the configuration of any given switch. the command switch resumes its role as the active command switch. see the “Designating and Enabling Standby Command Switches” section on page 5-17. Note The command switch forwards cluster configuration information to the standby switch but not device-configuration information. To configure an HSRP standby command group.

If no command-switch password is configured. If you plan to create switch clusters. it remains manageable if it leaves the cluster and becomes a standalone switch. it inherits the command-switch password and retains it when it leaves the cluster. you should assign an enable secret password to the command switch. the default. You can assign a privilege level (1 to 15) to the password. Passwords If you plan to create switch clusters. When the switch joins the cluster. Through the command-switch IP address. Restart your CMS session by entering the new IP address in the browser Location field (Netscape Communicator) or Address field (Microsoft Internet Explorer). provides the highest level of security. but it is not necessary. An enable secret password with privilege level 15 is required to access to the switch or switch cluster through CMS and TACACS+ authentication. you must enter that password to add the switch to the cluster. where level 15. the member switch inherits a null password.Chapter 5 Clustering Switches Planning a Switch Cluster IP Addresses Clustering switches conserves IP addresses if you have a limited number of them. You can assign IP information by using the setup program (refer to the release notes) or by manually assigning it (see the “Changing IP Information” section on page 6-2). When a member switch has its own IP address. as described in the release notes. You can assign this password by using the setup program (refer to the release notes) or by manually assigning it (see the “Changing the Password” section on page 6-15). It is not necessary to assign passwords to an individual switch if it will be a cluster member. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 5-8 78-6511-05 . it is managed and communicates with other member switches through the command-switch IP address. Caution Changing the command-switch IP address ends your CMS session. you can manage and monitor up to 16 switches. If a candidate switch has a password. You can assign an IP address to the candidate or member switch. you must assign IP information to a command switch. When a switch joins a cluster.

its passwords and privilege levels are altered.HTML access to the command line interface from a cached copy of the Cisco Systems Access page. it is not manageable by the command switch until you change the member-switch password to match the command-switch password or until you reboot the member switch. the length is only checked when the password is configured from the menu console or with the CLI. Catalyst 1900 and Catalyst 2820 member switches support only levels 1 and 15. – Command-switch privilege levels 1 to 14 map to level 1 on the member switch. – Command-switch privilege level 15 maps to level 15 on the member switch. A password is not required to redisplay these pages. Keep in mind the following caveats if your cluster has Catalyst 1900 and Catalyst 2820 member switches: • Password length – If the command-switch enable password is longer than eight characters. exit your browser to end the browser session. – If the command-switch enable password is between one and eight characters inclusive. the member-switch enable password is the same as the command switch password. the member-switch enable password is truncated to eight characters. Note Copies of the CMS pages you display are saved in your browser memory cache until you exit the browser session.) – Both the command switch and member switch support up to 25 characters (52 characters encrypted) in the enable secret password. To prevent unauthorized access to CMS and the CLI. • Privilege level The command switch supports up to 15 privilege levels. If a Catalyst 1900 or Catalyst 2820 switch joins the cluster. You can access the CLI by clicking Web Console . Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 5-9 . including the Cisco Systems Access page. (Though the password length for Catalyst 1900 and Catalyst 2820 switches is from four to eight characters.Chapter 5 Clustering Switches Planning a Switch Cluster If you change the member-switch password.

only the first read-only and read-write strings are propagated to the member switch. eng-cluster-5.Chapter 5 Clustering Switches Planning a Switch Cluster Host Names You do not need to assign a host name to either a command switch or an eligible cluster member. the first read-only and read-write community string on the command switch is propagated and overwrites the fourth read-only and read-write community string on the member switches. However. it retains that name when it joins a cluster. The Catalyst 2900 XL and Catalyst 3500 XL switches support an unlimited number of community strings and string lengths. If a switch has a host name. SNMP Community Strings The Cluster Management software appends the member switch number (@esN. where N is the switch number) to the first configured RO and RW community strings on the command switch and propagates them to the member switch: • commander-readonly-community-string@esN • commander-readwrite-community-string@esN If the command switch has multiple read-only or read-write community strings. The default host name for any Catalyst 2900 XL and Catalyst 3500 XL switch is Switch. The number indicates the member number of the switch. the command switch appends a unique member number to its own host name and assigns it sequentially as each switch joins the cluster. was removed from the cluster. To support the Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 5-10 78-6511-05 . When these switches join the cluster. If a switch joins a cluster and it does not have a host name. its old host name (such as eng-cluster-5) is overwritten with the host name of the command switch in the new cluster. a command switch named eng-cluster could name cluster member number 5. The Catalyst 1900 and Catalyst 2820 switches support up to four read-only and four read-write community strings. each string contains up to 32 characters. For example. If a switch received its host name from the command switch. a host name assigned to the command switch can help to more easily identify the switch cluster. It retains that host name even after it leaves the cluster. and was then was added to a new cluster.

0(5)XU and higher. see the “Using SNMP to Manage Switch Clusters” section on page 5-22. To manage switches in a cluster. The IP address is associated with the management VLAN. For more information about using SNMP to manage clusters. member. Management VLAN Communication with the switch management interfaces is through the switch IP address. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 5-11 .0(5)XP. and candidate switches must be connected through ports that belong to the management VLAN. Any VLAN can serve as the management VLAN as long as there are links between the command switch and the member switches for both the old and the new management VLAN. For more information about configuring community strings through Cluster Manager. the command-switch community strings are truncated to 27 characters when propagating them to these switches. If your cluster includes members that are running a software release earlier than Cisco IOS Release 12. the port connections among the command. and the @esN (where N refers to the member switch number and can be up to two digits) is appended to them. those members need to have the VLAN changed before using the Management VLAN window. see the “Configuring SNMP” section on page 6-18. Note Activity synchronization is only valid for IOS Release 12. If your cluster includes member switches that are running Cisco IOS Release 12.Chapter 5 Clustering Switches Planning a Switch Cluster 32-character string-length limitation on the Catalyst 1900 and Catalyst 2820 switches. the command switch synchronizes activities with member switches to ensure that no loss of management connectivity occurs. Previous releases of the software require that switches be upgraded one at a time. When you change the management VLAN on an existing cluster. you cannot change the management VLAN of the cluster. which by default is VLAN 1.0(5)XP.

For more information about the network port.Chapter 5 Clustering Switches Planning a Switch Cluster Caution You can change the management VLAN through a console connection without interrupting the console connection. Do not remove these commands. out-of-box switches that do not have a config. see the “Changing the Management VLAN for a New Switch” section on page 8-5. This automatic change of the VLAN only occurs for new. To change the management VLAN on an existing cluster. the command switch automatically senses that the new switch has a different management VLAN and has not been configured. However. Restart your CMS session by entering the new IP address in the browser Location field (Netscape Communicator) or Address field (Microsoft Internet Explorer). NAT Commands When a cluster is created. see the “Enabling a Network Port” section on page 7-7. Network Address Translation (NAT) commands are added to the configuration file of the command switch. changing the management VLAN ends your CMS session. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 5-12 78-6511-05 . If you add a new switch to an existing cluster and the cluster is using a management VLAN other than the default VLAN 1. The command switch issues commands to change the management VLAN on the new switch to match the one in use by the cluster. Network Port A network port cannot link cluster members. as described in the release notes.text file and for which there have been no changes to the running configuration.

For example. Starting Cluster Builder to add candidate and standby command switches to the cluster After the cluster is formed. these options are only available when the appropriate switch is selected from the Host Name drop-down list. A cluster can have a mix of LRE switches using different private profiles. Starting VSM to designate and enable a command switch 4. However. Availability of Switch-Specific Features in Switch Clusters When a switch has features specific to it and the switch is part of a switch cluster. Cabling together switches running clustering software 2. all LRE switches in that cluster must have that same public profile. make sure that you assign it the same public profile used by other LRE switches in the cluster. Device > LRE Profile appears in the Cluster Manager menu bar when at least one Catalyst 2900 LRE XL switch is in the cluster. see the “Configuring the LRE Ports” section on page 7-22. Assigning basic information to one switch (the command switch) 3. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 5-13 . you can access all switches in the cluster by entering the IP address of the command switch into the browser Location field (Netscape Communicator) or Address field (Microsoft Internet Explorer). If one LRE switch in a cluster is assigned a public profile. For more information about LRE port profiles. the CMS menu bars display the configuration options of those features. Creating a Switch Cluster You create a cluster by performing these tasks: 1.Chapter 5 Clustering Switches Creating a Switch Cluster LRE Profiles A configuration conflict occurs if a switch cluster has LRE switches using both private and public profiles. Before you add an LRE switch to a cluster.

This window lists the cluster candidates discovered by the switch. the suggested candidates are highlighted in the Suggested Candidates window. After enabling a command switch. To enable a command switch. For information about how to change the management VLAN. When you add new cluster-eligible switches to the network. see the “Management VLAN” section on page 5-11. Adding and Removing Cluster Members Each time you launch CMS. The Suggested Candidate window lists each candidate switch with its device type. Designating and Enabling a Command Switch Before you enable a switch as a command switch.Chapter 5 Clustering Switches Creating a Switch Cluster This section provides procedures for enabling a command switch and building a cluster. select Cluster > Cluster Command Configuration. display VSM. By default. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 5-14 78-6511-05 . This window does not appear after the number of switches in the cluster reaches the maximum of 16. but you can select 1 or more switches as long as the number of switches selected does not exceed 16. MAC address. Only candidates that you accept are added to the cluster. it prompts you with an updated Suggested Candidates window. For procedures on assigning basic information to the command switch. For procedures on connecting switches together. select Enable. refer to the release notes. Note The Suggested Candidates window displays prequalified candidates whether or not they are in the same management VLAN as the command switch. It appears as a candidate switch in Cluster Builder. select Cluster > Cluster Builder to begin building your cluster. and in the Command Switch Status field. CMS discovers those new switches and the next time you launch Cluster Builder. If you enter the password for a candidate in a different management VLAN than the cluster and click OK. this switch is not added to the cluster. refer to the release notes for command-switch requirements. and the switch through which it is connected to the cluster. it displays the Suggested Candidates window (Figure 5-3) and prompts you to create a cluster by adding qualified candidates. refer to the switch hardware installation guide. You can use up to 31 characters to name your cluster.

right-click the candidate icon. Cluster members have green labels. To add several switches to a cluster.d 54510 Candidate switch information. you can also add a candidate switch to a cluster. e. Cluster Builder displays a message that states which candidates were not added and why. Figure 5-3 Suggested Candidate Window Enter the password of the candidate switch. and from the pop-up menu.Chapter 5 Clustering Switches Creating a Switch Cluster From the Cluster Builder topology. Display Cluster Builder. and left-click the candidates you want to add. The Add to Cluster option is disabled when the number of cluster members reaches 16. You can add a switch to a cluster if the cluster has no more than 16 members. If no password exists for the switch. leave this field blank for the switch to join the cluster. otherwise. select Add to Cluster (Figure 5-4). If any of the candidates cannot be added. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 5-15 . and candidates have blue labels. press Ctrl. you must remove a member before adding a new one.

and select an option to display the Switch Manager. To remove a member switch. Right-click a candidate switch to display the device pop-up menu. 54502 Thin line indicates a connection to a candidate switch. You can add multiple candidates at the same time if they have the same password. the candidate is not added to the cluster. display switch information.Chapter 5 Clustering Switches Creating a Switch Cluster Figure 5-4 Cluster Builder Right-click a member switch to display the device pop-up menu. or remove the switch from the cluster. For more information about setting passwords. you are prompted to enter it and your username. If you enter a password that does not match the password defined for the candidate or if you enter a password for a candidate that does not have a password. and select Add to Cluster to add the switch to a cluster. and you will not be able to add it to the cluster. In all cases. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 5-16 78-6511-05 . If the candidate is in a different management VLAN than the command switch. right-click it. For more information about management VLAN considerations. once a candidate switch joins a cluster. see the “Management VLAN” section on page 5-11. it inherits the command-switch password. If a password has been configured on the candidate switch. a message states that this candidate is unreachable. For information about how to remove Catalyst 1900 or Catalyst 2820 member switches. refer to the Catalyst 1900 Series Installation and Configuration Guide or the Catalyst 2820 Series Installation and Configuration Guide. select Remove from Cluster. and from the pop-up menu. The switch retains its configured password when it leaves the cluster. see the “Passwords” section on page 5-8.

Chapter 5 Clustering Switches Creating a Switch Cluster Designating and Enabling Standby Command Switches To create a standby group. In the Selected list. display Cluster Manager. If the primary command switch fails. If the switches have the same number of links and speed. Candidate switches are ranked first by the number of links they have and second by the switch speed. the standby command switch becomes the primary command switch. the active command switch has the highest priority and is always at the top of the list. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 5-17 . Eligible switches are listed in the Candidates list according to an eligibility ranking. The standby command switch is listed after the active command switch. The last switch has the lowest priority. and select Cluster > Standby Command Configuration to display the Standby Command Configuration window (Figure 5-5). The standby switch with the next highest priority then becomes the standby command switch. followed by the other standby switches according to their priority. The standby switch with the next highest priority becomes the standby command switch. they are listed alphabetically.

nms-lab1 (CC) Switch201 Switch207 Standby command switches are listed below the active command switch. The Standby Command Configuration window uses the default values for the preempt and name commands that you have set by using the CLI. and the group number must be unique within the IP subnet. and the name for the group is clustername_standby. If you use this window to create the HSRP group. and the default is 0. The following abbreviations are appended to the switch host names in the Selected list to show their status in the standby group: • AC—Active command switch • SC—Standby command switch • PC—Member of the standby group but not the standby command switch • CC—Command switch when HSRP is disabled The virtual IP address must be in the same subnet as the IP addresses of the switches. this number cannot be changed.cisco.com Active command switch is at the top. It can be from 0 to 255. Candidates are listed in order of the eligibility. 54509 Once entered.Chapter 5 Clustering Switches Creating a Switch Cluster Figure 5-5 Standby Command Configuration Switch205 Switch202. all switches in the group have the preempt command enabled. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 5-18 78-6511-05 . Must be valid IP address in the same subnet as the active command switch.

serial numbers. location. The inventory summary of the cluster members includes information such as switch model numbers.Chapter 5 Clustering Switches Verifying a Switch Cluster Verifying a Switch Cluster You can display the switch cluster you have built by • Displaying an inventory of the switches in the cluster. see Chapter 9. right-click it. IP information. display VSM or Cluster Manager. “Troubleshooting. software versions. and select System > Inventory to display the Inventory window (Figure 5-6).” Displaying an Inventory of the Clustered Switches To display an inventory of the switch cluster. and select System > Inventory. You can also display port and switch statistics from Port > Port Statistics and Port > Port Configuration > Runtime Status. To display this information for a single switch. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 5-19 . • Displaying the topology of the switch cluster and viewing link information. select the switch image. For information about troubleshooting switch clusters. and any installed modules.

It shows how the switches are connected and the type of connection between each device. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 5-20 78-6511-05 . links. 54507 2 Displaying Link Information You can see how the cluster members are interconnected from Cluster Builder. IP addresses of cluster members. and colors used in Cluster Builder. To display port-connection information such as port numbers for each end of the link. To display a legend describing the icons.Chapter 5 Clustering Switches Verifying a Switch Cluster Figure 5-6 Inventory Select column borders to widen column. select Views > Toggle Labels. Software versions for cluster members. select Help > Legend.

Enter the rcommand user EXEC command and the member switch number to start a Telnet session (through a console or Telnet connection) and to access the member switch CLI. the member switch is accessed at privilege level 15. For instructions on configuring the Catalyst 2900 XL or Catalyst 3500 XL switch for a Telnet session. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 5-21 . For more information about the rcommand command.Chapter 5 Clustering Switches Using the CLI to Manage Switch Clusters Using the CLI to Manage Switch Clusters You can configure member switches from the CLI by first logging in to the command switch. you are prompted for the password before being able to access the menu console. After this. enter the show cluster members user EXEC command on the command switch. The Catalyst 1900 and Catalyst 2820 CLI is available only on switches running Enterprise Edition Software. For Catalyst 1900 and Catalyst 2820 switches running standard edition software. • If the command-switch privilege level is 15. If the command switch is at privilege level 14. the Telnet session accesses the member-switch CLI at the same privilege level as on the command switch. refer to the Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference. see the “Accessing the CLI” section on page 3-8. Enter the exit privileged EXEC command on the member switch to return to the command-switch CLI. The IOS commands then operate as usual. Command-switch privilege levels map to the Catalyst 1900 and Catalyst 2820 member switches running standard and Enterprise Edition Software as follows: Note • If the command-switch privilege level is 1 to 14. The following example shows how to log into member-switch 3 from the command-switch CLI: switch# rcommand 3 If you do not know the member-switch number. the member switch is accessed at privilege level 1. the Telnet session accesses the management console (a menu-driven interface) if the command switch is at privilege level 15. the command mode changes and IOS commands operate as usual. For Catalyst 2900 XL and Catalyst 3500 XL switches.

The command switch uses this community string to control the forwarding of gets. If a member switch has its own IP address and community strings. Use the first read-write and read-only community strings to communicate with the command switch if there is a standby group configured for the cluster. the command switch passes traps from the member switch to the management station. the command switch can change without your knowledge. For more information. The Cluster Management software appends the member switch number (@esN. sets. the command switch manages the exchange of messages between member switches and an SNMP application. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 5-22 78-6511-05 . Note When a standby group is configured. where N is the switch number) to the first configured RW and RO community strings on the command switch and propagates them to the member switch.Chapter 5 Clustering Switches Using SNMP to Manage Switch Clusters Using SNMP to Manage Switch Clusters You must enable SNMP for the Cluster Management reporting and graphing features to function properly. SNMP is enabled by default. SNMP is enabled if you enter the IP information by using the setup program and accept its proposed configuration. When you first power on the switch. they can be used in addition to the access provided by the command switch. When you create a cluster. If the member switch does not have an IP address. as shown in Figure 5-7. If you did not use the setup program to enter the IP information and SNMP was not enabled. you can enable it on the SNMP Configuration page described in the “Configuring SNMP” section on page 6-18. and get-next messages between the SNMP management station and the member switches. see the “SNMP Community Strings” section on page 5-10 and the “Configuring SNMP” section on page 6-18. On Catalyst 1900 and Catalyst 2820 switches.

Trap 2.Chapter 5 Clustering Switches Using SNMP to Manage Switch Clusters Figure 5-7 SNMP Management for a Cluster SNMP Manager Command switch Trap 1. Trap 3 33020 Trap Tr ap ap Tr Member 1 Member 2 Member 3 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 5-23 .

Chapter 5 Clustering Switches Using SNMP to Manage Switch Clusters Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 5-24 78-6511-05 .

It includes command-line interface (CLI) procedures for using commands that have been specifically created or changed for the Catalyst 2900 XL or Catalyst 3500 XL switches. This chapter does not repeat the concepts and CLI procedures provided in the standard Cisco IOS Release 12.0 documentation. refer to the online help. Note Some features can be implemented only by using the CLI. For complete syntax and usage information for the commands used in this chapter. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-1 . For information about configuring these settings from Cluster Management Suite (CMS).0 commands. For switch features that use standard Cisco IOS Release 12. refer to the Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference.C H A P T E R 6 Configuring the System This chapter provides information about changing switch-wide configuration settings.com for additional information and CLI procedures. refer to the Cisco IOS Release 12.0 documentation on Cisco.

Note If you enabled the DHCP feature. Manually Assigning and Removing Switch IP Information You can manually assign an IP address. Telnet. mask.Chapter 6 Configuring the System Changing IP Information Changing IP Information You can assign and change the IP information of your switch in the following ways: • Using the setup program. The mask identifies the bits that denote the network number in the IP address. The CPU sends traffic to an unknown IP address through the default gateway. any values you manually enter (from the CMS or from the ip address command) are ignored. as described in the release notes • Manually assigning an IP address. The broadcast address is reserved for sending messages to all hosts. enter the new IP address in the browser Location field (Netscape Communicator) or Address field (Internet Explorer). as described in this section Caution Changing the switch IP address ends any CMS. as described in this section • Using Dynamic Host Configuration Protocol (DHCP)-based autoconfiguration. the mask is then referred to as a subnet mask. the switch assumes you are using an external server for IP address allocation. To restart your CMS session. follow the steps described in the “Accessing the CLI” section on page 3-8. or Simple Network Management Protocol (SNMP) session. While this feature is enabled. and default gateway to the switch. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-2 78-6511-05 . When you use the mask to subnet a network. To restart your CLI session through Telnet.

VLAN 1 is the default management VLAN. follow these steps to remove an IP address: Command Purpose Step 1 clear ip address vlan 1 ip_address subnet_mask Remove the IP address and subnet mask. Note Using the no ip address command in configuration mode disables the IP protocol stack as well as removes the IP information. but you can configure any VLAN from IDs 1 to 1001.Chapter 6 Configuring the System Changing IP Information Beginning in privileged EXEC mode. follow these steps to enter the IP information: Command Purpose Step 1 configure terminal Enter global configuration mode. repeat the procedure. Step 4 exit Return to global configuration mode. Step 2 interface vlan 1 Enter interface configuration mode. Step 7 show running-config Verify that the information was entered correctly by displaying the running configuration. and enter the VLAN to which the IP information is assigned. Cluster members without IP addresses rely on the IP protocol stack being enabled. Step 2 end Return to privileged EXEC mode. Step 6 end Return to privileged EXEC mode. Use the following procedure to remove the IP information from a switch. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-3 . Step 3 show running-config Verify that the information was removed by displaying the running configuration. Beginning in privileged EXEC mode. Step 3 ip address ip_address subnet_mask Enter the IP address and subnet mask. Step 5 ip default-gateway ip_address Enter the IP address of the default router. If the information is incorrect.

Note DHCP replaces the Bootstrap Protocol (BOOTP) feature autoconfiguration to ensure retrieval of configuration files by unicast TFTP messages. With DHCP-based autoconfiguration. DHCP-based autoconfiguration replaces the BOOTP client functionality on your switch. your switch (DHCP client) can be automatically configured during bootup with IP address information and a configuration file that it receives during DHCP-based autoconfiguration. A router does not forward broadcast packets. This protocol consists of two components: one for delivering configuration parameters from a DHCP server to a device and one for allocating network addresses to devices. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-4 78-6511-05 . but it forwards packets based on the destination IP address in the received packet. a Domain Name System (DNS) server.Chapter 6 Configuring the System Changing IP Information Using DHCP-Based Autoconfiguration The Dynamic Host Configuration Protocol (DHCP) provides configuration information to Internet hosts and internetworking devices. However. No DHCP client-side configuration is required on your switch. You might also need to configure a TFTP server. A relay device forwards broadcast traffic between two directly connected LANs. Understanding DHCP-Based Autoconfiguration The DHCP provides configuration information to internet hosts and internetworking devices. your switch (DHCP client) can be automatically configured at startup with IP address information and a configuration file that it receives during DHCP-based autoconfiguration. BOOTP is available in earlier software releases for this switch. you need to configure the DHCP server for various lease options. With DHCP-based autoconfiguration. and possibly a relay device if the servers are on a different LAN than your switch. where designated DHCP servers allocate network addresses and deliver configuration parameters to dynamically configured devices. DHCP is built on a client-server model.

a lease for the IP address. • The configuration file is present. broadcasts a DHCPDISCOVER message to locate a DHCP server. The DHCP server offers configuration parameters (such as an IP address. subnet mask. With this message. This command enables the autoloading of a configuration file from a network server. but the IP address is not specified in it. DNS IP address. • The configuration file is present. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-5 . and the service config global configuration command is included. The amount of information the switch receives depends on how you configure the DHCP server. Figure 6-1 DHCP Request for IP Information from a DHCP Server DHCPDISCOVER (broadcast) Switch A DHCPOFFER (unicast) DHCP server DHCPACK (unicast) 47570 DHCPREQUEST (broadcast) 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. For more information. The 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 client returns a request for the offered configuration information to the DHCP server. see the “Configuring the DHCP Server” section on page 6-6. Figure 6-1 shows the sequence of messages that are exchanged between the DHCP client and the DHCP server. gateway IP address. the DHCP client can be invoked and automatically request configuration information from a DHCP server under the following conditions: • The configuration file is not present on the switch.Chapter 6 Configuring the System Changing IP Information DHCP Client Request Process When you boot your switch. and so forth) to the client in a DHCPOFFER unicast message. the IP address is not specified in it. the client and server are bound. In a DHCPREQUEST broadcast message. and the client uses configuration information received from the server. Switch A.

the client usually accepts the first offer it receives. the switch will broadcast. or the client has been slow in responding to the DHCPOFFER message (the DHCP server assigned the parameters to another client) of the DHCP server. an error has occurred during the negotiation of the parameters. the client returns a DHCPDECLINE broadcast message to the DHCP server. however. which means the offered configuration parameters have not been assigned.Chapter 6 Configuring the System Changing IP Information If the configuration parameters sent to the client in the DHCPOFFER unicast message by the DHCP server are invalid (a configuration error exists). The offer from the DHCP server is not a guarantee that the IP address will be allocated to the client. the switch can obtain different IP addresses and configuration files at different boot instances. however. You should configure the DHCP server with the following lease options: • IP address of the client (required) • Subnet mask of the client (required) • DNS server IP address (required) • Router IP address (default gateway address to be used by the switch) (required) • TFTP server name (required) • Boot filename (the name of the configuration file that the client needs) (recommended) • Host name (optional) Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-6 78-6511-05 . instead of unicast. the server usually reserves the address until the client has had a chance to formally request the address. A DHCP client might receive offers from multiple DHCP or BOOTP servers and can accept any one of the offers. TFTP requests to obtain the switch configuration file. Configuring the DHCP Server You should configure the DHCP servers with reserved leases that are bound to each switch by the switch hardware address. If the DHCP server does not support reserved leases. If the switch accepts replies from a BOOTP server and configures itself. The DHCP server sends the client a DHCPNAK denial broadcast message.

mask. You must also set up the TFTP server with the switch configuration files. If it is on a different LAN. however. the switch is not configured. the switch might broadcast TFTP requests. The DHCP server can be running on a UNIX or Linux operating system. The DHCP server can be on the same or a different LAN as the switch.0 documentation on Cisco. For CLI procedures. For more information. The files can include the following: • The configuration file named in the DHCP reply (the actual switch configuration file) • The network-confg or the cisconet. Unavailability of other lease options does not affect autoconfiguration. Configuring the TFTP Server The TFTP server must contain one or more configuration files in its base directory. DHCP is not used.com for additional information and CLI procedures. and the switch obtains the default configuration file by broadcasting TFTP requests. refer to the Cisco IOS Release 12. If the service config global configuration command and the IP address are both present in the configuration file. see the next section. Normally. the switch receives the configuration file through TFTP requests. If the service config global configuration command is specified in the configuration file.) Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-7 . if the DHCP and TFTP servers are properly configured. router IP address. these files are not accessed. the Windows NT operating system is not supported in this release. the switch must be able to access it through a relay device.cfg file (known as the default configuration files) • The router-confg or the ciscortr. for more information. the switch obtains its address. Note If the configuration file on the switch does not contain the IP address. or TFTP server name are not found.Chapter 6 Configuring the System Changing IP Information If you do not configure the DHCP server with the lease options described earlier. gateway IP address. and host name from DHCP.cfg file (These files contain commands common to all switches. see the “Configuring the Relay Device” section on page 6-9. If the IP address and subnet mask are not in the reply. then it replies to client requests with only those parameters that have available values. If the DNS server IP address.

then the configuration files must reside on a single TFTP server.com. To keep track of domain names. For more information. if the configuration filename is not provided.0 documentation on Cisco. The IOS software maintains a cache of host name-to-address mappings for use by the EXEC mode connect. you must first identify the host names and then specify a name server and enable the DNS. telnet. To map domain names to IP addresses. For example. so its domain name is cisco. IP has defined the concept of a Domain Name Server (DNS). Cisco Systems is a commercial organization that IP identifies by a com domain name. refer to the Cisco IOS Release 12. If the configuration filename is provided in the DHCP server reply.cisco. Configuring the Domain Name and the DNS Each unique IP address can have a host name associated with it. is identified as ftp. IP defines a hierarchical naming scheme that allows a device to be identified by its location or domain. A specific device in this domain. However. If it is on a different LAN.) as the delimiting characters. see the “Configuring the Relay Device” section on page 6-9. and related Telnet support operations. the configuration files for a switch can be spread over multiple TFTP servers. and ping commands. This cache speeds the process of converting names to addresses. any IP host name without a domain name will have that domain name appended to it before being added to the host table. You can specify a default domain name that the software uses to complete domain name requests. the Internet’s global naming scheme that uniquely identifies network devices. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-8 78-6511-05 . the switch must be able to access it through a relay device or a router. the File Transfer Protocol (FTP) system for example. You can specify either a single domain name or a list of domain names. For CLI procedures. Domain names are pieced together with periods (. The TFTP server can be on the same or a different LAN as the switch. which holds a cache (or database) of names mapped to IP addresses. When you specify a domain name.com for additional information and CLI procedures. You must also specify the TFTP server name-to-IP-address mapping in the DNS server database.com.Chapter 6 Configuring the System Changing IP Information You must specify the TFTP server name in the DHCP server lease database.

0.0.0. For example.4 On interface 20.0. For CLI procedures. The Internet’s global naming scheme. accomplishes this task. The DNS server can be on the same or a different LAN as the switch.3 router(config-if)# ip helper-address 20.0. You can enter up to two DNS server IP addresses in the lease database. refer to the Cisco IOS Release 12.0.0. and TFTP servers and that broadcasts from the servers can reach the DHCP client. You must configure this relay device to forward received broadcast packets on an interface to the destination host. If it is on a different LAN. you enable IP routing (ip routing global configuration command) and configure it with helper addresses by using the ip helper-address interface configuration command. If the relay device is a Cisco router.0. The TFTP server contains the configuration files for the switch.2 router(config-if)# ip helper-address 20.0.0 documentation on Cisco. DNS. the switch must be able to access it through a relay device or router.Chapter 6 Configuring the System Changing IP Information If your network devices require connectivity with devices in networks for which you do not control name assignment.2: router(config-if)# ip helper-address 20.0. or TFTP servers are on a different LAN than the switch. DNS. see the “Configuring the Relay Device” section on page 6-9. For more information. you can assign device names that uniquely identify your devices within the entire internetwork. in Figure 6-2. This service is enabled by default. Configuring the Relay Device You need to use a relay device if the DHCP. You must configure the IP addresses of the DNS servers in the lease database of the DHCP server from where the DHCP replies will retrieve them.0. you configure the router interfaces as follows: On interface 10. You must configure the TFTP server name-to-IP address map on the DNS server.com for additional information and CLI procedures.1 router(config-if)# ip helper-address 10. The switch uses the DNS server to resolve the TFTP server name to a TFTP server IP address. the DNS.1 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-9 . This configuration ensures that broadcasts from the DHCP client can reach the DHCP.0.

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-10 78-6511-05 . • Only the configuration filename is reserved for the switch. and upon receipt. the switch obtains its configuration information in the following ways: • The IP address and the configuration filename is reserved for the switch and provided in the DHCP reply (one-file read method).0. specifying the TFTP server name.0.Chapter 6 Configuring the System Changing IP Information Figure 6-2 Relay Device Used in Autoconfiguration Switch (DHCP client) Cisco router (Relay) 10.0.0. Obtaining Configuration Files Depending on the availability of the IP address and the configuration filename in the DHCP reserved lease. and configuration filename from the DHCP server.1 DHCP server 20. The switch follows the same configuration process described above.0. refer to the Cisco IOS Release 12.4 DNS server 47573 20.1 For CLI procedures.0.0.0.2 10. The switch receives its IP address.0 documentation on Cisco.0. subnet mask.0.3 TFTP server 20.0. The switch sends a DNS request to the DNS server. It also receives a DNS server IP address and a TFTP server name. The IP address is dynamically allocated to the switch by the DHCP server (one-file read method).com for additional information and CLI procedures. completes its boot-up process.0.2 20. to obtain the TFTP server address. Then the switch sends a unicast message to the TFTP server to retrieve the named configuration file from the base directory of the server.

the switch uses the host name in the DHCP reply.) The default configuration file contains the host names-to-IP-address mapping for the switch. the switch reads the cisconet. to obtain the TFTP server address. If the switch cannot read the network-confg. If the host name is not specified in the DHCP reply. It also receives a DNS server IP address and a TFTP server name. it reads the router-confg file.cfg was read earlier) from the TFTP server.Chapter 6 Configuring the System Changing IP Information • Only the IP address is reserved for the switch and provided in the DHCP reply.cfg default configuration file. If the cisconet. The switch sends a DNS request to the DNS server. The switch fills its host table with the information in the file and obtains its host name. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-11 . The switch receives its IP address and subnet mask from the DHCP server. If the switch cannot read the router-confg file. Note The switch broadcasts TFTP server requests if the TFTP server name is not obtained from the DHCP replies.cfg. depending on whether network-confg or cisconet.cfg file. the switch reads the configuration file that has the same name as its host name (hostname-confg or hostname. If the host name is not found in the file. or if the TFTP server name cannot be resolved to an IP address. if all attempts to read the configuration file through unicast transmissions fail. The configuration filename is not provided (two-file read method). the switch uses the default “Switch” as its host name. cisconet. or the host-name file. After obtaining its host name from the default configuration file or the DHCP reply.cfg file. it reads the ciscortr. (If the network-confg file cannot be read.cfg file is read. specifying the TFTP server name. the filename of the host is truncated to eight characters. The switch sends a unicast message to the TFTP server to retrieve the network-confg or cisconet.cfg.

Chapter 6 Configuring the System Changing IP Information Example Configuration Figure 6-3 shows a sample network for retrieving IP information using DHCP-based autoconfiguration.9f1e.10 DHCP server 10.0.1 Table 6-1 shows the configuration of the reserved leases on the DHCP server.9f1e.0.2002 00e0.2001 00e0.2 DNS server 10.0.2004 Cisco router 10.3 TFTP server (maritsu) 47571 10.9f1e.0.0.2003 00e0.0.9f1e. Figure 6-3 DHCP-Based Autoconfiguration Network Example Switch 1 Switch 2 Switch 3 Switch 4 00e0. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-12 78-6511-05 .0.0.

255.21 ip host switch2 10.2004 IP address 10.10 10.255.2001 00e0.0.0.0.0.22 ip host switch3 10.24 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-13 .2 DNS server address 10.21 10.0.0.23 ip host switch4 10.10 10.0.0 255.2 TFTP server name maritsu or 10.9f1e.0.22 10.0.0.23 10.3 Boot filename (configuration file) (optional) switch1-confg switch2-confg switch3-confg switch4-confg Host name (optional) switch1 switch2 switch3 switch4 DNS Server Configuration The DNS server maps the TFTP server name maritsu to IP address 10.0.255.2003 00e0. The base directory also contains a configuration file for each switch (switch1-confg.0.255.0.255.0.2 10.0.0.9f1e.10 10. switch2-confg.0.2002 00e0.Chapter 6 Configuring the System Changing IP Information Table 6-1 DHCP Server Configuration Switch-1 Switch-2 Switch-3 Switch-4 Binding key (hardware address) 00e0.255.0 255.3 maritsu or 10. and so forth) as shown in this display: prompt> cd /tftpserver/work/ prompt> ls network-confg switch1-confg switch2-confg switch3-confg switch4-confg prompt> cat network-confg ip host switch1 10.0 255.255.9f1e.0.2 10.0.10 10.9f1e.0. This directory contains the network-confg file used in the two-file read method.24 Subnet mask 255.0.3 maritsu or 10.0.0.0.0.0.0.0.0.0.0.0. TFTP Server Configuration (on UNIX) The TFTP server base directory is set to /tftpserver/work/.0.0.0.3.0.0.3 maritsu or 10.0.255.0 Router address 10.0.0. This file contains the host name to be assigned to the switch based on its IP address.0.0.

Chapter 6 Configuring the System Changing IP Information DHCP Client Configuration No configuration file is present on Switch 1 through Switch 4.21 to its host name (switch1). • It reads its host table by indexing its IP address 10. Switch 1 reads its configuration file as follows: • It obtains its IP address 10.0. • It reads the configuration file that corresponds to its host name. • If no configuration filename is given in the DHCP server reply.0. for example. Switches 2 through 4 retrieve their configuration files and IP addresses in the same way. • It adds the contents of the network-confg file to its host table.0.0. it reads switch1-confg from the TFTP server.21 from the DHCP server. Switch 1 reads the network-confg file from the base directory of the TFTP server. Configuration Explanation In Figure 6-3. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-14 78-6511-05 .

Level 1 is EXEC-mode user privileges. Catalyst 2900 XL and Catalyst 3500 XL switches have two commands for setting passwords: • enable secret password (a very secure. unencrypted password) You must enter one of these passwords to gain access to privileged EXEC mode. You can also specify up to 15 privilege levels and define passwords for them by using the enable password [level level] {password} or the enable secret [level level] {password} command. Your connection with the switch ends when you change the enable secret password. If you enter the enable secret command. We recommend that you use the enable secret password. see the “Recovering from a Lost or Forgotten Password” section on page 9-22. the privilege level defaults to 15 (privileged EXEC-mode privileges). Because many privileged EXEC commands are used to set operating parameters.text file where you can read it. Note When set. and the enable password serves no purpose. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-15 . If you do not specify a level. as described in the release notes • Manually assigning a password. the text is encrypted before it is written to the config.Chapter 6 Configuring the System Changing the Password Changing the Password You can assign the password of your switch in the following ways: Note • Using the setup program. encrypted password) • enable password password (a less secure. If you have forgotten your password. the enable secret password takes precedence. and it is unreadable. you should password-protect these commands to prevent unauthorized use. the text is written as entered to the config. You will then need to reopen the session with the new password. as described in this section You can change a password only by using the CLI.text file. If you enter the enable password command.

refer to the Cisco IOS Release 12. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-16 78-6511-05 .Chapter 6 Configuring the System Changing the Password You can specify a level. The Telnet password must be an enable secret password. for example. and both can start with a number. set a password. Note You need an enable secret password with a privilege level 15 to access CMS. and give the password only to users who need to have access at this level. use the no version of the commands: no enable secret or no enable password. To remove a password. Both types of passwords can contain from 1 to 25 uppercase and lowercase alphanumeric characters.0 documentation on Cisco. You must also use this password if you configure the Terminal Access Controller Access Control System Plus (TACACS+) protocol from the CLI so that all your HTTP connections are authenticated through the TACACS+ server. For CLI procedures. two words is a valid password. Use the privilege level global configuration command to specify commands accessible at various levels. see the “Recovering from a Lost or Forgotten Password” section on page 9-22. If you lose or forget your enable password. see the “Passwords” section on page 5-8. The password is case sensitive. Leading spaces are ignored. For information about managing passwords in switch clusters. Spaces are also valid password characters.com for additional information and CLI procedures. trailing spaces are recognized.

Chapter 6 Configuring the System Setting the System Date and Time Setting the System Date and Time You can change the date and a 24-hour clock time setting on the switch. Configuring Daylight Saving Time You can configure the switch to change to daylight saving time on a particular day every year. California is eight time zones west of Greenwich.0 documentation on Cisco. For CLI procedures. You then must enter a negative or positive number as an offset to indicate the number of time zones between the switch and Greenwich. For CLI procedures.0 documentation on Cisco. You can also enter negative and positive numbers for minutes. it is often prudent to distribute time information from a central server. on a day that you enter. If you are entering the time for an American time zone. Configuring the Switch as an NTP Client You configure the switch as an NTP client by entering the IP addresses of up to ten NTP servers and specifying which server should be used first. You can also enter an authentication key to be used as a password when requests for time information are sent to the server. If you are identifying the time zone by referring to Greenwich mean time. Configuring the Network Time Protocol In complex networks. so you would enter –8. Enter a negative number if the switch is west of Greenwich. and east of the international date line. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-17 . England. The Network Time Protocol (NTP) can distribute time information by responding to requests from clients or by broadcasting time information. For example. enter the three-letter abbreviation for the time zone. enter UTC (universal coordinated time). refer to the Cisco IOS Release 12. or not at all. refer to the Cisco IOS Release 12. Enter a positive number if the switch is east of Greenwich.com for additional information and CLI procedures. such as PST for Pacific standard time. England.com for additional information and CLI procedures.

the clustering software can change Simple Network Management Protocol (SNMP) parameters (such as host names) when the cluster is created. Disabling and Enabling SNMP SNMP is enabled by default and must be enabled for Cluster Management features to work properly.com for additional information and CLI procedures. broadcasting time information on the network. you can authenticate NTP messages with public-key encryption. For CLI procedures. such as a router. Configuring the Switch for NTP Broadcast-Client Mode You can configure the switch to receive NTP broadcast messages if there is an NTP broadcast server. Configuring SNMP If your switch is part of a cluster. refer to the Cisco IOS Release 12. SNMP is always enabled for Catalyst 1900 and Catalyst 2820 switches.0 documentation on Cisco. see the “SNMP Community Strings” section on page 5-10. You can also enter a value to account for any round-trip delay between the client and the NTP broadcast server. If you are configuring a cluster for SNMP. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-18 78-6511-05 . This procedure must be coordinated with the administrator of the NTP servers: the information you enter will be matched by the servers to authenticate it.Chapter 6 Configuring the System Configuring SNMP Enabling NTP Authentication To ensure the validity of information received from NTP servers.

If a member switch has an assigned IP address. When you configure a trap manager. no trap manager is defined. By default. Table 6-2 describes the Catalyst 2900 XL and Catalyst 3500 XL switch traps. the management station accesses the switch by using that IP address. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-19 . TTY Generate traps when the switch starts a management console CLI session. the community strings for each member switch must be unique. and no traps are issued. see the “SNMP Community Strings” section on page 5-10.Chapter 6 Configuring the System Configuring SNMP Entering Community Strings Community strings serve as passwords for SNMP messages. VTP Generate a trap for each VLAN Trunk Protocol (VTP) change. Adding Trap Managers A trap manager is a management station that receives and processes traps.0 documentation on Cisco. VLAN membership Generate a trap for each VLAN Membership Policy Server (VMPS) change. SNMP Generate the supported SNMP traps. permitting access to the agent on the switch.com for additional information and CLI procedures. You can enter community strings with the following characteristics: Read-only (RO)—Requests accompanied by the string can display MIB-object information. refer to the Cisco IOS Release 12. C2900/C3500 Generate the switch-specific traps. Read-write (RW)—Requests accompanied by the string can display MIB-object information and set MIB objects. For CLI procedures. If you are entering community strings for a cluster member. Table 6-2 Catalyst 2900 XL and Catalyst 3500 XL Switch Traps Config Generate traps whenever the switch configuration changes. You can enable any or all of these traps and configure a trap manager on these switches to receive them. These traps are in the private enterprise-specific Management Information Base (MIB).

but these traps are received by all configured trap managers. you cannot configure individual trap managers to receive specific traps. BSC Generates a trap when the broadcast threshold is exceeded. You can enable any or all of these traps. Link-up-down Generates a link-down trap when a port is suspended or disabled for any of these reasons: • Secure address violation (address mismatch or duplication) • Network connection error (loss of linkbeat or jabber error) • User disabling the port Generates a link-up trap when a port is enabled for any of these reasons: VTP • Presence of linkbeat • Management intervention • Recovery from an address violation or any other error • STP action Generates a trap when VTP changes occur. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-20 78-6511-05 . When configuring traps on these switches. Table 6-3 Catalyst 1900 and Catalyst 2820 Switch Traps Trap Type Description Address-violation Generates a trap when the address violation threshold is exceeded. When you configure community strings for these switches. Authentication Generates a trap when an SNMP request is not accompanied by a valid community string. Table 6-3 describes the Catalyst 1900 and Catalyst 2820 switch traps.Chapter 6 Configuring the System Configuring SNMP Catalyst 1900 and Catalyst 2820 switches support up to four trap managers. limit the string length to 32 characters.

2. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-21 .Chapter 6 Configuring the System Configuring SNMP Beginning in privileged EXEC mode. Step 2 snmp-server host 172.263 traps1 snmp vlan-membership Enter the trap manager IP address. and the traps to generate.128. follow these steps to add a trap manager and a community string: Command Purpose Step 1 config terminal Enter global configuration mode. Step 4 show running-config Verify that the information was entered correctly by displaying the running configuration. Step 3 end Return to privileged EXEC mode. the community string.

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-22 78-6511-05 . Disabling CDP can interrupt cluster discovery. and display information about neighboring Cisco devices. Figure 6-4 shows a command switch that can discover candidates and cluster members up to seven devices away from it. Although the Catalyst 5000 supports CDP. For example. set global CDP parameters. and the command switch cannot learn about connected candidate switches connected to it. the switch uses CDP to find cluster candidates and to maintain information about cluster members and other devices up to three cluster-enabled devices away from the command switch. Figure 6-4 also shows the command switch connected to a Catalyst 5000 series switch. Note Creating and maintaining switch clusters is based on the regular exchange of CDP messages. For more information about the role that CDP plays in clustering. see the “Automatic Discovery of Cluster Candidates” section on page 5-4. you can configure CDP to discover switches running the Cluster Management Suite up to seven devices away from the command switch. and CDP cannot discover any device connected to them. even if they are running CMS. CDP enables the Cluster Management Suite to display a graphical view of the network. Devices that do not run clustering software display as edge devices. Configuring CDP for Extended Discovery You can change the default configuration of CDP on the command switch to continue discovering devices up to seven hops away. If necessary. it does not support clustering.Chapter 6 Configuring the System Configuring CDP Configuring CDP Use the Cisco IOS CLI and Cisco Discovery Protocol (CDP) to enable CDP for the switch.

The hop count is displayed in the file. Command Purpose Step 1 configure terminal Enter global configuration mode. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-23 . Step 2 cluster discovery hop-count number Enter the number of hops that you want CDP to search for cluster candidates and cluster members. follow these steps to configure the number of hops that CDP uses to discover candidate switches and cluster members.Chapter 6 Configuring the System Configuring CDP Figure 6-4 Discovering Cluster Candidates through CDP Undisclosed device displays as edge device Cluster command switch Catalyst 5000 series (CDP device that does not support clustering) Up to 7 hops from command switch 33019 3 hops from command switch Beginning in privileged EXEC mode. Step 3 end Return to privileged EXEC mode. Step 4 show running-config Verify the change by displaying the running configuration file.

These parameters are applied when the STP instance is created. at least one switch on each loop in the VLAN must be running spanning tree. adding another VLAN anywhere in the VLAN Trunk Protocol (VTP) domain creates a VLAN that is not running STP on that switch. The remaining VLANs must operate with STP disabled. For more information about VLANs. spanning tree must be running on enough switches so that it can break all the loops in the network. Caution Switches that are not running spanning tree still forward Bridge Protocol Data Units (BPDUs) that they receive so that the other switches on the VLAN that have a running STP instance can break loops. For example. You can change all VLANs on a switch by using the stp-list parameter when you enter STP commands through the CLI. STP calculates the best loop-free path throughout the network. and Catalyst 2924C XL support only 64 VLANs. Use the no spanning-tree vlan vlan-id global configuration command to disable STP on a specific VLAN. Therefore. “Configuring VLANs. It is not absolutely necessary to run spanning tree on all Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-24 78-6511-05 . and use the spanning-tree vlan vlan-id global configuration command to enable STP on the desired VLAN. You can configure switch and port parameters before an STP instance is created. The Catalyst 2912 XL.Chapter 6 Configuring the System Configuring STP Configuring STP Spanning Tree Protocol (STP) provides path redundancy while preventing undesirable loops in the network. For example. Only one active path can exist between any two stations. If you have already used up all available STP instances on a switch. see Chapter 8. refer to the Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference. you can enable STP on those 250 VLANs.” Each VLAN is a separate STP instance. and then enable it on the VLAN where you want it to run. All Catalyst 3500 XL switches and most Catalyst 2900 XL switches support 250 VLANs. if 250 VLANs are defined in the VTP domain. For more information. Catalyst 2924 XL. The STP instance is removed when the last interface is moved to another VLAN. Supported STP Instances You create an STP instance when you assign an interface to a VLAN. You can disable STP on one of the VLANs where it is running.

the low-speed link is originally disabled. You can also create redundant links between switches by using EtherChannel port groups. excessive traffic and indefinite packet duplication can severely reduce network performance. Disabling STP STP is enabled by default. Using STP to Support Redundant Connectivity You can create a redundant backbone with STP by connecting two of the switch ports to another device or to two different devices. an incautious change to the network that introduces another loop into the VLAN can result in a broadcast storm. Setting up allowed lists is not necessary in many cases and makes it more labor-intensive to add another VLAN to the network. the new VLAN is carried on all trunk ports. Caution When STP is disabled and loops are present in the topology. however.Chapter 6 Configuring the System Configuring STP switches in the VLAN. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-25 . If the two link speeds are the same. this could create a loop in the new VLAN that will not be broken. and STP disables the link with the lowest value. Disable STP only if you are sure there are no loops in the network topology. You can prevent this by setting allowed lists on the trunk ports of switches that have used up their allocation of STP instances. Note If you have the default allowed list on the trunk ports of that switch. see the “Creating EtherChannel Port Groups” section on page 7-10. STP automatically disables one port but enables it if the other port is lost. Depending on the topology of the network. For more information about creating port groups. particularly if there are several adjacent switches that all have run out of STP instances. If one link is high-speed and the other low-speed. the port priority and the port ID are added together. if you are running STP only on a minimal set of switches.

a reconfiguration of the spanning tree can cause many station locations to change. Step 4 show spanning-tree Verify your entry. The accelerated aging is the same as the forward-delay parameter value when STP reconfigures. Because these stations could be unreachable for 5 minutes or more during a reconfiguration. Dynamic addresses on other VLANs can be unaffected and remain subject to the aging interval entered for the switch. Figure 6-5 shows modular Catalyst 2900 XL and Catalyst 3500 XL switches in three cascaded clusters that use the GigaStack GBIC. Because each VLAN is a separate instance of STP. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-26 78-6511-05 . Table 6-4 shows the default STP settings and those that are acceptable for these configurations. A reconfiguration of STP on one VLAN can cause the dynamic addresses learned on that VLAN to be subject to accelerated aging. follow these steps to disable STP: Command Purpose Step 1 configure terminal Enter global configuration mode. Accelerating Aging to Retain Connectivity The default for aging dynamic addresses is 5 minutes. Step 3 end Return to privileged EXEC mode. However. If an STP root switch is part of a cluster that is one switch from a cascaded stack. the switch accelerates aging on a per-VLAN basis. the address-aging time is accelerated so that station addresses can be dropped from the address table and then relearned. you can customize STP to reconverge more quickly after a switch failure. Step 2 no spanning-tree vlan stp-list Disable STP on a VLAN. Configuring STP and UplinkFast in a Cascaded Cluster STP uses default values that can be reduced when configuring Catalyst 2900 XL and Catalyst 3500 XL switches in cascaded configurations.Chapter 6 Configuring the System Configuring STP Beginning in privileged EXEC mode.

Chapter 6 Configuring the System Configuring STP Table 6-4 Figure 6-5 Default and Acceptable STP Parameter Settings (in Seconds) STP Parameter STP Default (IEEE) Acceptable for Option 1 Acceptable for Option 2 Acceptable for Option 3 Hello Time 2 1 1 1 Max Age 20 6 10 6 Forwarding delay 15 4 7 4 Gigabit Ethernet Clusters Catalyst 5000 series switch Catalyst 2900 and 3500 XL switches Catalyst 2900 and 3500 XL switches Catalyst 5000 series/ 6000 backbone Layer 3 backbone Cisco 7000 router 33021 Catalyst 6000 switch Catalyst 2900 Cisco 7000 and 3500 XL router switches Option 1: standalone cascaded cluster Option 2: cascaded cluster connected to a Layer 2 backbone Option 3: cascaded cluster connected to a Layer 3 backbone Enabling UplinkFast on all cluster switches can further reduce the time it takes cluster switches to begin forwarding after a new root switch is selected. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-27 .

the switch begins using the alternate paths as soon as STP selects a new root port. If a switch looses connectivity. other ports flood the network with multicast packets.Chapter 6 Configuring the System Configuring STP Configuring Redundant Links By Using STP UplinkFast Switches in hierarchical networks can be grouped into backbone switches. as it would with normal STP procedures. When STP reconfigures the new root port. station-learning frames are not generated. The default for this parameter is 150 packets per second. You can limit these bursts of multicast traffic by reducing the max-update-rate parameter. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-28 78-6511-05 . one for each address that was learned on the port. UplinkFast is most useful in edge or access switches and might not be appropriate for backbone devices. so the STP topology converges more slowly after a loss of connectivity. if you enter zero. The root port transitions to the forwarding state immediately without going through the listening and learning states. Figure 6-6 shows a complex network where distribution switches and access switches each have at least one redundant link that STP blocks to prevent loops. STP UplinkFast is a Cisco enhancement that accelerates the choice of a new root port when a link or switch fails or when STP reconfigures itself. distribution switches. and access switches. However.

Chapter 6 Configuring the System Configuring STP Figure 6-6 Switches in a Hierarchical Network Backbone switches Root bridge 3500 XL 3500 XL Distribution switches 2900 XL Active link 2900 XL 2900 XL 2900 XL 2900 XL 2900 XL 22037 2900 XL Access switches Blocked link Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-29 .

When UplinkFast is disabled. Beginning in privileged EXEC mode. station-learning frames are not generated.Chapter 6 Configuring the System Configuring STP Enabling STP UplinkFast When you enable UplinkFast. so the STP topology converges more slowly after a loss of connectivity. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-30 78-6511-05 . This change reduces the chance that the switch will become the root switch. If you set the rate to 0. the bridge priorities of all VLANs and path costs of all ports are set to default values. The range is from 0 to 1000 packets per second. Step 4 show spanning-tree Verify your entries. The default is 150. and the path cost of all ports and VLAN trunks is increased by 3000. the bridge priority of all VLANs is set to 49152. When UplinkFast is enabled. follow these steps to configure UplinkFast: Command Purpose Step 1 configure terminal Enter global configuration mode. it is enabled for the entire switch and cannot be enabled for individual VLANs. Step 2 spanning-tree uplinkfast max-update-rate pkts-per-second Enable UplinkFast on the switch. Step 3 exit Return to privileged EXEC mode.

As shown in Figure 6-7. which completes in 30 to 40 seconds. see the “Events that Cause Fast Convergence” section on page 6-33. If Switch A fails. With this feature. the normal STP transition occurs. if its stack root port fails.Chapter 6 Configuring the System Configuring STP Configuring Cross-Stack UplinkFast Cross-stack UplinkFast (CSUF) provides a fast spanning-tree transition (fast convergence in less than 2 seconds under normal network conditions) across a stack of switches that use the GigaStack GBICs connected in a shared cascaded configuration (multidrop backbone). The switches in the stack use their stack ports to communicate with each other and to connect to the stack backbone. you can have a redundant and resilient network in some configurations. or if Link A fails. During the fast transition. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-31 . stack ports are always in the STP forwarding state. in these cases. How CSUF Works CSUF ensures that one link in the stack is elected as the path to the root. The stack root port on Switch A provides the path to the root of the spanning tree. an alternate redundant link on the stack of switches is placed into the forwarding state without causing temporary spanning-tree loops or loss of connectivity to the backbone. which communicates control and data traffic across the switches at the access layer. Link A. Links B and C are alternate redundant links that are in the STP blocking state. the root link. the alternate stack root ports on Switches B and C can provide an alternate path to the spanning-tree root if the current stack root switch fails or its link to the spanning-tree root fails. and C are cascaded through the Gigastack GBIC to form a multidrop backbone. CSUF might not provide a fast transition all the time. CSUF selects either the Switch B or Switch C alternate stack root port and puts it into the forwarding state in less than 1 second. Switches A. For more information. is in the STP forwarding state. B.

the Fast Uplink Transition Protocol uses the neighbor list to send fast-transition requests on the stack port to stack members. Using the Stack Membership Discovery Protocol. When certain link loss or STP events occur (described in the “Events that Cause Fast Convergence” section on page 6-33).Chapter 6 Configuring the System Configuring STP Figure 6-7 Cross-Stack UplinkFast Topology Backbone Spanning tree root Fwd Fwd Link A (Root link) Link B (Alternate redundant link) Link C (Alternate redundant link) 100 or 1000 Mbps 100 or 1000 Mbps 100 or 1000 Mbps Stack root port Alternate stack root port Alternate stack root port Stack port Switch B Stack port Switch C Stack port 47572 Switch A Fwd Multidrop backbone (GigaStack GBIC connections) CSUF implements the Stack Membership Discovery Protocol and the Fast Uplink Transition Protocol. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-32 78-6511-05 . all stack switches build a neighbor list of stack members through the receipt of discovery hello packets.

which connected the stack root to the STP root. and the spanning-tree topology converges at its normal rate (2 * forward-delay time + max-age time). If acknowledgements from all stack switches are not obtained by the sending switch. learning. the normal STP transitions (blocking. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-33 . and it must obtain an acknowledgement from each stack switch before performing the fast transition. it does not respond to the sending switch (drops the packet) and prevents the sending switch from receiving acknowledgements from all stack switches. listening.Chapter 6 Configuring the System Configuring STP 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. the switch in the stack returns an acknowledgement. If two switches in the stack have alternate paths to the root. When acknowledgements are received from all stack switches. If the sending switch is the best choice as the stack root. The Fast Uplink Transition Protocol is implemented on a per-VLAN basis and affects only one STP instance at a time. comes back up. only one of the switches performs the fast transition. • A network reconfiguration causes a new stack root switch to be selected. the Fast Uplink Transition Protocol on the sending switch immediately transitions its alternate stack root port to the forwarding state. cost. Events that Cause Fast Convergence Depending on the network event or failure. • The failed link. and bridge ID. Each switch in the stack determines if the sending switch is a better choice than itself to be the stack root of this STP instance by comparing STP root. Fast convergence (within 2 seconds under normal network conditions) occurs under these circumstances: • The stack root port link goes down. forwarding) take place. otherwise. fast convergence provided by CSUF might or might not occur.

is added to the stack. the normal STP convergence then occurs. the normal STP convergence occurs. • The stack root switch. a link connecting the stack root to the STP root comes back up. Because the Fast Uplink Transition Protocol only waits 2 seconds to receive acknowledgements from all stack switches. The fast transition might not occur if multiple events occur simultaneously. which was powered down or failed. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-34 78-6511-05 . • A link fails between stack ports on the multidrop backbone. Normal STP convergence (30 to 40 seconds) occurs under these conditions: Note • The stack root switch is powered down or the software failed. The fast transition of CSUF depends on the amount of network traffic and how you connect the GigaStack GBICs across the stack switches. • A new switch. • A switch other than the stack root is powered down or failed. if a stack member switch is powered down. Instead of a fast transition. is powered up. heavy network traffic might prevent the fast transition from occurring within this time frame. For example. which might become the stack root.Chapter 6 Configuring the System Configuring STP • Note A network reconfiguration causes a new port on the current stack root switch to be chosen as the stack root port. and at the same time.

• You can connect the open ports on the top and bottom GigaStack GBICs within the same stack to form a redundant link. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-35 . In addition.Chapter 6 Configuring the System Configuring STP Limitations The following limitations apply to CSUF: • CSUF uses the Gigastack GBIC and runs on all Catalyst 3500 XL switches but only on modular Catalyst 2900 XL switches. • Only one stack port is supported per switch. • Each stack switch can be connected to the STP backbone through one uplink. follow these guidelines: • Do not connect alternate stack root ports to stack ports. Connecting the Stack Ports A fast transition occurs across the stack of switches if the multidrop backbone connections are a continuous link from one GigaStack GBIC to another as shown in Figure 6-8. • Up to 64 VLANs are supported. Only one stack port per switch is supported. • Up to nine stack switches can be connected through their stack ports to the multidrop backbone. • All stack ports on the stack of switches must be connected to the multidrop backbone.

Chapter 6 Configuring the System Configuring STP Figure 6-8 GigaStack GBIC Connections and STP Convergence GigaStack GBIC connection for fast convergence Catalyst 3524 XL 1 2 3 4 5 6 7 8 9 10 11 12 1X Catalyst 3508G XL 13 14 11X 15 16 17 18 19 20 21 22 Catalyst 3500 23 24 13X Catalyst 3500 XL 1 UTIL 3 2 1 2 5 4 7 6 8 SYSTEM RPS RPS MODE XL 15X SYSTEM STATUS STATUS MODE 2X 12X 14X 16X UTIL 2 1 DUPLX SPEED Catalyst 2924M XL Catalyst 3508G XL Catalyst 2900 Catalyst 3500 3 2 1 2 1 DUPLX SPEED 5 4 XL 7 6 2 1 8 SYSTEM RPS MODE STATUS UTIL 2 1 DUPLX SPEED 1x 2x 3x 4x 5x 6x 7x 8x 9x 10x 11x 12x 13x 14x 15x 17x 16x 18x 19x 20x 21x 22x 23x 24x MODE Catalyst 3512 XL Catalyst 3524 XL 1 2 3 4 5 6 7 8 9 1X 10 11 12 13 14 11X 15 16 17 18 19 20 21 22 Catalyst 3500 23 24 13X 1 XL 2 3 4 5 6 7 8 9 10 Catalyst 3500 11 12 1X 11X 2X 12X XL 15X 1 1 2 2 SYSTEM SYSTEM RPS RPS MODE STATUS MODE STATUS UTIL UTIL 2X 12X 14X 16X SPEED Catalyst 3524 XL Catalyst 3508G XL Catalyst 3500 1 2 3 4 5 7 6 XL 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 Catalyst 3500 23 24 1X 11X 13X 15X 2X 12X 14X 16X 8 XL 2 1 SYSTEM SYSTEM RPS MODE 2 1 DUPLX 2 1 DUPLX SPEED RPS STATUS STATUS MODE UTIL UTIL 2 1 DUPLX SPEED DUPLX SPEED 1 2 GigaStack GBIC connection for normal convergence Catalyst 3512 XL 1 2 3 4 5 6 7 8 9 10 Catalyst 3500 11 12 1X 11X 2X 12X XL 1 2 SYSTEM RPS MODE STATUS UTIL 2 1 DUPLX SPEED Catalyst 2924M XL Catalyst 2900 2 1 1x 2x 3x 4x 5x 6x 7x 8x 9x 10x 11x 12x 13x 14x 15x 16x 17x 18x 19x 20x 21x 22x 23x 24x MODE Catalyst 3512 XL 1 2 3 4 5 6 7 8 9 10 Catalyst 3500 11 12 1X 11X 2X 12X 1 XL 2 SYSTEM RPS MODE STATUS UTIL 2 1 DUPLX SPEED 2 1 Catalyst 2924M XL Catalyst 2900 1x MODE 2x 3x 4x 5x 6x 7x 8x 9x 10x 11x 12x 13x 14x 15x 16x 17x 18x 19x 20x 21x 22x 23x 24x 49069 2 1 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-36 78-6511-05 .

Step 3 end Return to privileged EXEC mode. (Optional) For max-update-rate pkts-per-second. You must disable CSUF on the first interface before enabling it on a new interface. Step 1 interface interface-id Enter interface configuration mode. Step 2 spanning-tree stack-port Enable CSUF on only one stack-port GBIC interface. If you try to enable CSUF on a Fast Ethernet or a copper-based Gigabit Ethernet port. specify the number of packets per second at which update packets are sent. the default is 150 packets per second. Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file. The range is 0 to 65535. Step 4 show spanning-tree Verify your entries. To disable CSUF on an interface. you receive an error message. see the “Connecting the Stack Ports” section on page 6-35. The stack port connects to GigaStack GBIC multidrop backbone. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-37 . follow these steps to enable CSUF: Command Purpose Step 1 configure terminal Enter global configuration mode.Chapter 6 Configuring the System Configuring STP Configuring Cross-Stack UplinkFast Before enabling CSUF. you receive an error message. Use this command only on access switches. use the no spanning-tree stack-port interface configuration command. Step 2 spanning-tree uplinkfast [max-update-rate pkts-per-second] Enable UplinkFast on the switch. For more information. Beginning in privileged EXEC mode. and specify the GBIC interface on which to enable CSUF. If CSUF is already enabled on an interface and you try to enable it on another interface. make sure your stack switches are properly connected. To disable UplinkFast on the switch. use the no spanning-tree uplinkfast global configuration command.

This wait is necessary so that other switches on the network ensure that no loop is formed before they allow the port to forward packets. You can change the root parameters for the VLANs on a selected switch. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-38 78-6511-05 . Switches not acting as the root use the root-switch Max age parameter.Chapter 6 Configuring the System Configuring STP Changing the STP Parameters for a VLAN The root switch for each VLAN is the switch with the highest priority and transmits topology frames to other switches in the spanning tree. This parameter takes effect when a switch is operating as the root switch. Max age Number of seconds (6 to 200) a switch waits without receiving STP configuration messages before attempting a reconfiguration. Forward Delay Number of seconds (4 to 200) a port waits before changing from its STP learning and listening states to the forwarding state. Switches not acting as a root switch use the root-switch Hello-time value. Hello Time Number of seconds (1 to 10) between the transmission of hello messages. The switch with the lowest value has the highest priority and is selected as the root. Priority Value (0 to 65535) used to identify the root switch. The default is IEEE. which indicate that the switch is active. Protocol Implementation of STP to use: IBM or IEEE. The following options define how your switch responds when STP reconfigures itself.

Changing the Switch Priority Beginning in privileged EXEC mode. Command Purpose Step 1 configure terminal Enter global configuration mode. Command Purpose Step 1 configure terminal Enter global configuration mode. Step 3 end Return to privileged EXEC mode. follow these steps to change the STP implementation. follow these steps to change the switch priority and affect which switch is the root switch. Step 4 show spanning-tree Verify your entry. Step 2 spanning-tree [vlan stp-list] protocol {ieee | ibm} Specify the STP implementation to be used for a spanning-tree instance. The stp-list is the list of VLANs to which the STP command applies. the more likely the switch will be chosen as the root switch. Step 2 spanning-tree [vlan stp-list] priority bridge-priority Configure the switch priority for the specified spanning-tree instance. the lower the number. The stp-list is the list of VLANs to which the STP command applies.Chapter 6 Configuring the System Configuring STP Changing the STP Implementation Beginning in privileged EXEC mode. Step 3 end Return to privileged EXEC mode. Step 4 show spanning-tree Verify your entry. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-39 . Enter a number from 0 to 65535.

The stp-list is the list of VLANs to which the STP command applies. Step 4 show spanning-tree Verify your entry. Step 2 spanning-tree [vlan stp-list] hello-time seconds Specify the interval between hello BPDUs. follow these steps to change the hello BPDU interval (hello time). Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-40 78-6511-05 . Step 3 end Return to privileged EXEC mode. follow these steps to change the BPDU message interval (max age time). Command Purpose Step 1 configure terminal Enter global configuration mode. The maximum age is the number of seconds a switch waits without receiving STP configuration messages before attempting a reconfiguration. Enter a number from 6 to 200. Hello messages indicate that the switch is active. Step 2 spanning-tree [vlan stp-list] max-age seconds Specify the interval between messages the spanning tree receives from the root switch. Command Purpose Step 1 configure terminal Enter global configuration mode. Step 4 show spanning-tree Verify your entry. The stp-list is the list of VLANs to which the STP command applies.Chapter 6 Configuring the System Configuring STP Changing the BPDU Message Interval Beginning in privileged EXEC mode. Changing the Hello BPDU Interval Beginning in privileged EXEC mode. Enter a number from 1 to 10. Step 3 end Return to privileged EXEC mode.

Step 4 show spanning-tree Verify your entry. • Down—Port has no physical link. The default for IEEE is 15 seconds. • Broken—One end of the link is configured as an access port. • Forwarding—Port is forwarding frames and learning addresses.Chapter 6 Configuring the System Configuring STP Changing the Forwarding Delay Time Beginning in privileged EXEC mode. or both ends of the link are configured as 802.1Q trunk port. • Disabled—Port has been removed from STP operation. follow these steps to change the forwarding delay time. • Learning—Port is not forwarding frames but is learning addresses. it can be in one of these states: • Blocking—Port is not participating in the frame-forwarding process and is not learning new addresses. Command Purpose Step 1 configure terminal Enter global configuration mode. • Listening—Port is not participating in the frame-forwarding process. STP Port States When a port is not forwarding due to STP. The forward delay is the number of seconds a port waits before changing from its STP learning and listening states to the forwarding state. Step 3 end Return to privileged EXEC mode. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-41 . Enter a number from 4 to 200. Step 2 spanning-tree [vlan stp-list] forward-time seconds Specify the forwarding time for the specified spanning-tree instance. The port is not learning addresses.1Q trunk ports but have different native VLAN IDs. The stp-list is the list of VLANs to which the STP command applies. and the other end is configured as an 802. the default for IBM is 4 seconds. but is progressing towards a forwarding state.

2 for 10 Gbps. follow these steps to enable the Port Fast feature: Command Purpose Step 1 configure terminal Enter global configuration mode. and 1 for interfaces with speeds greater than 10 Gbps. Enter a number from 1 to 65535. Enter a number from 0 to 65535. This feature is useful when a connected server or workstation times out because its port is going through the normal cycle of STP status changes. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-42 78-6511-05 . Step 5 show running-config Verify your entry. Caution Enabling this feature on a port connected to a switch or hub could prevent STP from detecting and disabling loops in your network. • Path Cost —A lower path cost represents higher-speed transmission. Step 3 spanning-tree portfast Enable the Port Fast feature for the port. A port with Port Fast enabled only goes through the normal cycle of STP status changes when the switch is restarted. A higher number has higher priority. The default is 100 for 10 Mbps. You can modify the following Port Fast parameters: • Port Fast—Enable to bring the port more quickly to an STP forwarding state. 14 for 155 Mbps (ATM). Enabling this feature on a port connected to a switch or hub could prevent STP from detecting and disabling loops in your network.Chapter 6 Configuring the System Configuring STP Enabling the Port Fast Feature The Port Fast feature brings a port directly from a blocking state into a forwarding state. This can affect which port remains enabled in the event of a loop. and enter the port to be configured. Step 2 interface interface Enter interface configuration mode. 19 for 100 Mbps. Step 4 end Return to privileged EXEC mode. • Priority —Number used to set the priority for a port. Beginning in privileged EXEC mode. and this could cause broadcast storms and address-learning problems. 4 for 1 Gbps.

Step 4 end Return to privileged EXEC mode. follow these steps to change the port priority. The STP command applies to the stp-list. follow these steps to change the path cost for STP calculations. Enter a number from 1 to 65535. Command Purpose Step 1 configure terminal Enter global configuration mode. Step 5 show running-config Verify your entry.Chapter 6 Configuring the System Configuring STP Changing the Path Cost Beginning in privileged EXEC mode. Step 4 end Return to privileged EXEC mode. Step 5 show running-config Verify your entry. Step 2 interface interface Enter interface configuration mode. Step 2 interface interface Enter interface configuration mode. The lower the number. Step 3 spanning-tree [vlan stp-list] cost cost Configure the path cost for the specified spanning-tree instance. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-43 . Changing the Port Priority Beginning in privileged EXEC mode. and enter the port to be configured. The stp-list is the list of VLANs to which the STP command applies. and enter the port to be configured. Step 3 spanning-tree [vlan stp-list] port-priority port-priority Configure the port priority for a specified instance of STP. which is used when two switches tie for position as the root switch. Command Purpose Step 1 configure terminal Enter global configuration mode. Enter a number from 0 to 255. the higher the priority.

and STP selects a new root switch. In such a topology. The customer switch does not become the root switch and is not in the path to the root. If a switch outside the network becomes the root switch. If STP calculations cause an interface in the customer network to be selected as the root port. 43578 Desired root switch Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-44 78-6511-05 . STP in a Service Provider Network Customer network Service-provider network Potential STP root without root guard enabled 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. as shown in Figure 6-9. root guard then places the interface into the root-inconsistent (blocked) state to prevent the customer switch from becoming the root switch or being in the path to the root.Chapter 6 Configuring the System Configuring STP Configuring STP Root Guard The Layer 2 network of a service provider (SP) can include many connections to switches that are not owned by the SP. the interface is blocked (root-inconsistent state). You can avoid this situation by configuring the root-guard feature on interfaces that connect to switches outside of your customer’s network. Caution Figure 6-9 Misuse of this feature can cause a loss of connectivity. STP can reconfigure itself and select a customer switch as the STP root switch.

follow these steps to set root guard on a port: Command Purpose Step 1 configure terminal Enter global configuration mode. Then the IP datagram is encapsulated in a link-layer frame and sent over the network. the IP-MAC address association is stored in an ARP cache for rapid retrieval. and enter the port to be configured. Encapsulation of IP datagrams and ARP requests and replies on IEEE 802 networks other than Ethernet is specified by the Subnetwork Access Protocol (SNAP). Step 4 end Return to privileged EXEC mode. standard Ethernet-style ARP encapsulation (represented by the arpa keyword) is enabled on the IP interface. The process of determining the local data link address from an IP address is called address resolution. Use the no version of the spanning-tree rootguard command to disable the root guard feature. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-45 . The Address Resolution Protocol (ARP) associates a host IP address with the corresponding media or MAC addresses and the VLAN ID. Step 5 show running-config Verify that the port is configured for root guard. ARP entries added manually to the table do not age and must be manually removed. ARP determines the associated MAC address. Taking an IP address as input. Each VLAN has its own instance of STP. Beginning in privileged EXEC mode. for example).Chapter 6 Configuring the System Managing the ARP Table Root guard enabled on a port applies to all the VLANs that the port belongs to. Managing the ARP Table To communicate with a device (over Ethernet. the software first must determine the 48-bit MAC or the local data link address of that device. Step 2 interface interface Enter interface configuration mode. By default. Step 3 spanning-tree rootguard Enable root guard on the port. Once a MAC address is determined.

When a CGMP group is removed. CGMP is enabled. CGMP does not dynamically learn addresses that are MVR group members. If you want CGMP to learn an address that is already an MVR group member. Conversely. remove the address from the CGMP group.Chapter 6 Configuring the System Controlling IP Multicast Packets through CGMP For CLI procedures. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-46 78-6511-05 . When a CGMP group is added. you cannot add an address to an MVR group if it is already a CGMP group member.com for additional information and CLI procedures. If you want an address that is already a CGMP group member to be an MVR group member.0 documentation on Cisco. it is added on a per-VLAN. see the “Configuring MVR” section on page 6-49. and the Fast Leave feature is disabled. Note The same multicast MAC addresses cannot belong to both CGMP and Multicast VLAN Registration (MVR) groups. Controlling IP Multicast Packets through CGMP CGMP reduces the unnecessary flooding of IP multicast packets by limiting the transmission of these packets to CGMP clients that request them. End stations issue join messages to become part of a CGMP group and issue leave messages to leave the group. and then statically add it to the MVR group. it is only removed in a given VLAN. per-group basis. The Fast Leave feature accelerates the removal of unused CGMP groups. By default. refer to the Cisco IOS Release 12. For information about MVR. The membership of these groups is managed by the switch and by connected routers through the further exchange of CGMP messages. CGMP groups are maintained on a per-VLAN basis: a multicast IP address packet can be forwarded to one list of ports in one VLAN and to a different list of ports in another VLAN. remove the address from the MVR group.

Step 4 show running-config Verify your entry. The client must be running IGMP version 2 for the Fast Leave feature to function properly. Beginning in privileged EXEC mode. Step 2 cgmp leave-processing Enable CGMP and CGMP Fast Leave. With the Fast Leave feature enabled. follow these steps to disable the CGMP Fast Leave feature: Command Purpose Step 1 configure terminal Enter global configuration mode. Step 4 show running-config Verify your entry. Step 3 end Return to privileged EXEC mode.Chapter 6 Configuring the System Controlling IP Multicast Packets through CGMP Enabling the Fast Leave Feature The CGMP Fast Leave feature reduces the delay when group members leave groups. Disabling the CGMP Fast Leave Feature Beginning in privileged EXEC mode. If there are no other members. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-47 . the group remains enabled for that VLAN until all members have requested to leave. Step 3 end Return to privileged EXEC mode. the switch immediately verifies if there are other group members attached to its ports. Step 2 no cgmp leave-processing Disable CGMP and CGMP Fast Leave. The Fast Leave feature functions only if CGMP is enabled. If there are no other ports in the group. the switch sends a message to routers connected to the VLAN to delete the entire group. the switch removes the port from the group. follow these steps to enable the CGMP Fast Leave feature: Command Purpose Step 1 configure terminal Enter global configuration mode. When an end station requests to leave a CGMP group.

their ports. If it is the last router entry in a VLAN. Step 3 end Return to privileged EXEC mode. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-48 78-6511-05 . follow these steps to change the router hold-time. follow these steps to remove all multicast groups. Beginning in privileged EXEC mode. Note You can remove router ports before the router hold-time has expired. Step 2 show cgmp Verify your entry by displaying CGMP information. and their expiration times. Command Purpose Step 1 configure terminal Enter global configuration mode. Step 4 show running-config Verify your entry. You can thus enter a lower router hold-time to accelerate the removal of CGMP groups. Removing Multicast Groups You can reduce the forwarding of IP multicast packets by removing groups from the Current Multicast Groups table. Command Purpose Step 1 clear cgmp group Clear all CGMP groups on all VLANs on the switch. Beginning in privileged EXEC mode. and ports. or all routers.Chapter 6 Configuring the System Controlling IP Multicast Packets through CGMP Changing the CGMP Router Hold-Time The router hold-time is the number of seconds the switch waits before removing (aging) a router entry and ceasing to exchange messages with the router. Each entry in the table consists of the VLAN. all CGMP groups on that VLAN are removed. Step 2 cgmp holdtime 400 Configure the number of seconds the switch waits before dropping a router entry. IGMP multicast address. You can use the CLI to clear all CGMP groups. all CGMP groups in a VLAN.

Multiple set-top boxes or PCs can be connected to one subscriber port. The switch CPU sends an IGMP group-specific query through the receiver port VLAN.Chapter 6 Configuring the System Configuring MVR Configuring MVR Multicast VLAN Registration (MVR) is designed for applications using wide-scale deployment of multicast traffic (for example. but to isolate the streams from the subscriber VLANs for bandwidth and security reasons. Because MVR does not support IGMP dynamic joins. MVR assumes that subscriber ports subscribe and unsubscribe (join and leave) these multicast streams by sending out Internet Group Management Protocol (IGMP) join and leave messages. and modifies the forwarding table to include or remove the subscriber as a receiver of the multicast stream. the user or administrator must configure static multicast addresses on the router.) DHCP assigns an IP address to the set-top box or the PC. If there is another Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-49 . The switch CPU identifies IP multicast streams and their associated MAC addresses in the switch forwarding table. MVR allows a subscriber on a port to subscribe and unsubscribe to a multicast stream on the network-wide multicast VLAN. broadcast of multiple television channels) across an Ethernet ring-based service provider network. the set-top box sends an IGMP leave message for the multicast stream. intercepts the IGMP messages. This provides the ability to continuously send multicast streams in the multicast VLAN. When a subscriber changes channels or turns off the television. the set-top box or PC sends an IGMP report to the access layer switch (S1 switch) to join the appropriate multicast. (See Figure 6-10. It allows the single multicast VLAN to be shared in the network while subscribers remain in separate VLANs. 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 over the source port. If the IGMP report matches one of the configured multicast MAC addresses. a PC or a television with a set-top box can receive the multicast stream. When a subscriber selects a channel. Using MVR in a Multicast Television Application In a multicast television application. This forwarding behavior selectively allows traffic to cross between the two VLANs. These messages can originate from an IGMP version-2-compatible set-top box with an Ethernet connection or from a PC capable of generating IGMP version-2 messages.

Chapter 6 Configuring the System Configuring MVR set-top box in the VLAN still subscribing to this group. that set-top box must respond within the maximum response time. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-50 78-6511-05 . If the CPU does not receive a response. it eliminates the receiver port as a forwarding destination for this group. Figure 6-10 Multicast VLAN Registration Example Cisco router Catalyst 2900/3500 XL switch Catalyst 2900/3500 XL switch Multicast server SP SP Catalyst 2900/3500 XL switch SP SP Catalyst 2900/3500 XL switch SP SP1 SP SP2 Multicast data Multicast data S1 RP1 RP2 RP3 RP4 RP5 RP6 RP7 Customer premises Hub IGMP join Set-top box Set-top box TV data TV RP = Receiver Port SP = Source Port TV 47849 PC Note: All source ports belong to the multicast VLAN.

configure all MVR parameters. • Before configuring MVR groups. – Enable port blocking on all receiver ports to prevent unknown unicast and multicast packets. follow these steps: a. Enter the mvr vlan <vlan-id> command to change the multicast VLAN. IGMP reports are sent to the same MAC addresses as the multicast data. Enter the no mvr command to disable MVR. These messages dynamically register for streams of multicast traffic in the multicast VLAN on the switch. all packets from subscriber ports destined for the configured multicast MAC addresses are forwarded to the switch CPU. they appear to be initiated by a port in the multicast VLAN rather than in the VLAN to which the subscriber port is assigned. b. including the multicast VLAN. Multicast traffic for all channels is sent only once around the VLAN trunk—only on the multicast VLAN.Chapter 6 Configuring the System Configuring MVR MVR eliminates the need to duplicate television-channel multicast traffic for subscribers in each VLAN. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-51 . The access layer switch (S1 switch) modifies the forwarding behavior to allow the traffic to be forwarded from the multicast VLAN to the subscriber port in a different VLAN. If you want to change the MVR parameters after MVR groups have been configured. Configuration Guidelines and Limitations Follow these guidelines when configuring MVR: • All receiver ports on a switch must belong to the same VLAN and must not be trunk ports. Because the Catalyst 2900 and Catalyst 3500 hardware cannot distinguish IP multicast data packets from IP multicast packets carrying IGMP protocol data. we recommend configuring receiver ports as follows: – Enable protected port on all receiver ports to isolate the ports from one another. which distinguishes IGMP packets from regular multicast traffic. • In applications where the receiver ports represent subscribers to a service. selectively allowing traffic to cross between two VLANs. The S1 CPU must capture all IGMP join and leave messages from subscriber ports. Although the IGMP leave and join messages originate with a subscriber.

The receiver VLAN is reset whenever there are no remaining receiver ports on the switch (active or inactive). remove the address from the CGMP group. The maximum number of mvr entries is determined by the switch hardware. The switch uses the MVR groups when you re-enable MVR. which means that the receiver VLAN might change every time the first receiver port is configured. d. In MVR. MVR implementation has the following limitations: • MVR is supported on only modular Catalyst 2900 XL switches. • MVR does not support IP-address aliasing and therefore requires that each IP multicast address maps to only one Layer 2 MAC address. Each MVR group represents a TV channel. • Make sure the router is statically configured to forward multicast traffic for the MVR groups to the switch. Conversely. • The same multicast MAC addresses cannot belong to both CGMP and MVR groups. If you want CGMP to learn an address that is already an MVR group member. • The receiver VLAN is the VLAN to which the first configured receiver port belongs. CGMP does not dynamically learn addresses that are MVR group members. see the “Controlling IP Multicast Packets through CGMP” section on page 6-46. and then statically add it to the MVR group. it becomes an inactive receiver port and does not take part in MVR unless it is assigned to the receiver VLAN. Enter the mvr command to enable MVR. The router should not depend on IGMP join requests from hosts (forwarded by the switch) to forward multicast traffic to the switch. you cannot configure multiple IP addresses that map to the same MAC address. If you want an address that is already a CGMP group member to be an MVR group member. remove the address from the MVR group. You do not need to reconfigure the MVR groups. If the first receiver port is a dynamic port with an unassigned VLAN. you cannot add an address to an MVR group if it is already a CGMP group member. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-52 78-6511-05 . For information about CGMP.Chapter 6 Configuring the System Configuring MVR c. • Each channel is one multicast stream destined for a unique IP multicast address. • Unknown multicast packets. unknown unicast packets. and broadcast packets are leaked from the multicast VLAN to the receiver ports.

Step 8 copy running-config startup-config Save your configuration changes to nonvolatile RAM (NVRAM). Step 2 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. and enter the type and number of the port to configure. Beginning in privileged EXEC mode. fastethernet 0/1. Step 7 show mvr show mvr interface Verify the configuration. for example. you must do so before enabling MVR. Step 5 mvr threshold value (Optional) Define the maximum of multicast data packets received on a receiver port before it is administratively shut down. If you do want to change the default parameters. all source ports must belong to this VLAN. The value is in units of tenths of a second. The default is VLAN 1. Step 3 mvr vlan vlan-id (Optional) Specify the VLAN in which multicast data will be received. follow these steps to configure MVR parameters: Command Purpose Step 1 configure terminal Enter global configuration mode. The default is 5 tenths or one-half second. The default is 20. Step 6 end Exit configuration mode. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-53 .Chapter 6 Configuring the System Configuring MVR Setting MVR Parameters You do not need to set MVR parameters if you choose to use the default settings. Step 4 interface interface Enter interface configuration mode.

the command fails. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-54 78-6511-05 . and enter the type and number of the port to configure. • Configure a port as a receiver port if it is a subscriber port and should only receive multicast data. 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. All source ports on a switch belong to the single multicast VLAN. you should configure receiver ports as protected ports with port blocking enabled. for example. Step 5 mvr type value Configure the port as either an MVR receiver port or an MVR source port. Note Each IP address translates to a multicast 48-bit MAC address. follow these steps to configure MVR: Command Purpose Step 1 configure terminal Enter global configuration mode. • Configure uplink ports that receive and send multicast data as source ports. It does not receive data unless it becomes a member of the multicast group by using IGMP leave and join messages. 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 IP addresses. fastethernet 0/1.Chapter 6 Configuring the System Configuring MVR Configuring MVR Beginning in privileged EXEC mode. Each multicast address would correspond to one television channel. In most cases. All receiver ports on a switch must belong to the same VLAN. Step 4 interface interface Enter interface configuration mode. If an IP address being configured translates (aliases) to a previously configured MAC address. Step 2 mvr Enable MVR on the switch.

Note This command applies only to receiver ports and should only be enabled on receiver ports to which a single receiver device is connected. Step 9 copy running-config startup-config Save your configuration changes to NVRAM. Step 8 show mvr show mvr interface show mvr members Verify the configuration. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-55 . Step 7 end Exit configuration mode.Chapter 6 Configuring the System Configuring MVR Step 6 Command Purpose mvr immediate (Optional) Enables the Immediate Leave feature of MVR on the port.

These MAC tables include the following types of addresses: • Dynamic address: a source MAC address that the switch learns and then drops when it is not in use. A known address in one VLAN is unknown in another until it is learned or statically associated with a port in the other VLAN. All MAC addresses in the address tables are associated with one or more ports. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-56 78-6511-05 . Secure addresses do not age.Chapter 6 Configuring the System Managing the MAC Address Tables Managing the MAC Address Tables You can manage the MAC address tables that the switch uses to forward traffic between ports. The address tables list the destination MAC address and the VLAN ID. Addresses that are statically entered in one VLAN must be static addresses in all other VLANs. Figure 6-11 shows an example list of addresses as they would appear in the dynamic. and 11 in VLAN 5. Multicast addresses. and port number associated with the address. secure. for example. module. Each VLAN maintains its own logical address table. • Secure address: a manually entered unicast address that is usually associated with a secured port. • Static address: a manually entered unicast or multicast address that does not age and that is not lost when the switch resets. An address can be secure in one VLAN and dynamic in another. or static address table. Figure 6-11 Contents of the Address Table MAC Addresses and VLANs All addresses are associated with a VLAN. could be forwarded to port 1 in VLAN 1 and ports 9. 10. An address can exist in more than one VLAN and have different destinations in each.

This unnecessary flooding can impact performance. Then when the switch receives a packet for an unknown destination. Step 4 show mac-address-table aging-time Verify your entry. Setting too long an aging time can cause the address table to be filled with unused addresses. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-57 .Chapter 6 Configuring the System Managing the MAC Address Tables Changing the Address Aging Time Dynamic addresses are source MAC addresses that the switch learns and then drops when they are not in use. This parameter applies to all VLANs. Step 3 end Return to privileged EXEC mode. Step 2 mac-address-table aging-time seconds Enter the number of seconds that dynamic addresses are to be retained in the address table. it floods the packet to all ports in the same VLAN as the receiving port. follow these steps to configure the dynamic address table aging time. Setting too short an aging time can cause addresses to be prematurely removed from the table. Command Purpose Step 1 configure terminal Enter global configuration mode. Beginning in privileged EXEC mode. You can enter a number from 10 to 1000000. it can cause delays in establishing connectivity when a workstation is moved to a new port. The aging time parameter defines how long the switch retains unseen addresses in the table.

the switch reassigns the secure address to the new port. You can remove all dynamic entries by using the clear mac-address-table dynamic command in privileged EXEC mode. packets destined for that address are forwarded to the port. Step 2 mac-address-table secure hw-addr interface vlan vlan-id Enter the MAC address. A secure address is a manually entered unicast address that is forwarded to only one port per VLAN. Adding Secure Addresses The secure address table contains secure MAC addresses and their associated ports and VLANs. Step 3 end Return to privileged EXEC mode. Beginning in privileged EXEC mode. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-58 78-6511-05 . Step 3 end Return to privileged EXEC mode. follow these steps to remove a dynamic address entry: Command Purpose Step 1 configure terminal Enter global configuration mode. its associated port. When the port is later assigned to a VLAN. Step 4 show mac-address-table Verify your entry.Chapter 6 Configuring the System Managing the MAC Address Tables Removing Dynamic Address Entries Beginning in privileged EXEC mode. Step 2 no mac-address-table dynamic Enter the MAC address to be removed from dynamic MAC hw-addr address table. and the VLAN ID. follow these steps to add a secure address: Command Purpose Step 1 configure terminal Enter global configuration mode. You can enter a secure port address even when the port does not yet belong to a VLAN. If you enter an address that is already assigned to another port. Step 4 show mac-address-table secure Verify your entry.

Chapter 6 Configuring the System Managing the MAC Address Tables Removing Secure Addresses Beginning in privileged EXEC mode. an out-port-list. Step 4 show mac-address-table secure Verify your entry. • It can be a unicast or multicast address. follow these steps to remove a secure address: Command Purpose Step 1 configure terminal Enter global configuration mode. Because all ports are associated with at least one VLAN. A static address in one VLAN must be a static address in other VLANs. Packets received from the in-port list are forwarded to ports listed in the out-port-list. and the VLAN ID to be removed. You can determine how a port that receives a packet forwards it to another port for transmission. 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. and a VLAN ID. its associated port. Static addresses are entered in the address table with an in-port-list. • It does not age and is retained when the switch restarts. the switch acquires the VLAN ID for the address from the ports that you select on the forwarding map. Adding Static Addresses A static address has the following characteristics: • It is manually entered in the address table and must be manually removed. Step 3 end Return to privileged EXEC mode. Step 2 no mac-address-table secure hw-addr vlan vlan-id Enter the secure MAC address. if needed. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-59 . You can remove all secure addresses by using the clear mac-address-table secure command in privileged EXEC mode.

follow these steps to add a static address: Command Purpose Step 1 configure terminal Enter global configuration mode. Beginning in privileged EXEC mode. You can remove all secure addresses by using the clear mac-address-table static command in privileged EXEC mode. and the VLAN ID of those ports. Step 3 end Return to privileged EXEC mode. Step 4 show mac-address-table static Verify your entry. and the VLAN ID to be removed. Step 3 end Return to privileged EXEC mode. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-60 78-6511-05 . Step 4 show mac-address-table static Verify your entry. the ports to which it can be forwarded. the input port. the ports to which it can be forwarded. you must supply the VLAN ID. Step 2 mac-address-table static hw-addr in-port out-port-list vlan vlan-id Enter the MAC address. the switch recognizes the VLAN as that associated with the in-port VLAN. the input port. In this case. Step 2 no mac-address-table static hw-addr in-port in-port out-port-list out-port-list vlan vlan-id Enter the static MAC address. follow these steps to remove a static address: Command Purpose Step 1 configure terminal Enter global configuration mode.Chapter 6 Configuring the System Managing the MAC Address Tables Note If the in-port-list and out-port-list parameters are all access ports in a single VLAN. Otherwise. Removing Static Addresses Beginning in privileged EXEC mode. you can omit the VLAN ID.

Chapter 6

Configuring the System
Configuring TACACS+

Configuring Static Addresses for EtherChannel Port Groups
Follow these rules if you are configuring a static address to forward to ports in an
EtherChannel port group:

For default source-based port groups, configure the static address to forward
to all ports in the port group to eliminate lost packets.

For destination-based port groups, configure the address to forward to only
one port in the port group to avoid the transmission of duplicate packets.

Configuring TACACS+
The Terminal Access Controller Access Control System Plus (TACACS+)
provides the means to manage network security (authentication, authorization,
and accounting [AAA]) from a server. This section describes how TACACS+
works and how you can configure it. For complete syntax and usage information
for the commands described in this chapter, refer to the Cisco IOS Release 12.0
Security Command Reference.
You can only configure this feature by using the CLI; you cannot configure it
through the Cluster Management Suite.
In large enterprise networks, the task of administering passwords on each device
can be simplified by centralizing user authentication on a server. TACACS+ is an
access-control protocol that allows a switch to authenticate all login attempts
through a central server. The network administrator configures the switch with the
address of the TACACS+ server, and the switch and the server exchange messages
to authenticate each user before allowing access to the management console.
TACACS+ consists of three services: authentication, authorization, and
accounting. Authentication determines who the user is and whether or not the user
is allowed access to the switch. Authorization is the action of determining what
the user is allowed to do on the system. Accounting is the action of collecting data
related to resource usage.

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide
78-6511-05

6-61

Chapter 6

Configuring the System

Configuring TACACS+

The TACACS+ feature is disabled by default. However, you can enable and
configure it by using the CLI. You can access the CLI through the console port or
through Telnet. 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 the TACACS+ configuration is performed through the CLI, the
TACACS+ server authenticates HTTP connections that have been configured
with a privilege level of 15.

Configuring the TACACS+ Server Host
Use the tacacs-server host command to specify the names of the IP host or hosts
maintaining an AAA/TACACS+ server. On TACACS+ servers, you can configure
the following additional options:

Number of seconds that the switch waits while trying to contact the server
before timing out.

Encryption key to encrypt and decrypt all traffic between the router and the
daemon.

Number of attempts that a user can make when entering a command that is
being authenticated by TACACS+.

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide

6-62

78-6511-05

Chapter 6

Configuring the System
Configuring TACACS+

Beginning in privileged EXEC mode, follow these steps to configure the
TACACS+ server:

Step 1

Step 2

Command

Purpose

tacacs-server host name
[timeout integer] [key string]

Define a TACACS+ host.

tacacs-server retransmit
retries

Enter the number of times the server searches the list of
TACACS+ servers before stopping.

Entering the timeout and key parameters with this
command overrides the global values that you can enter
with the tacacs-server timeout (Step 3) and the
tacacs-server key commands (Step 5).

The default is two.
Step 3

tacacs-server timeout seconds

Set the interval that the server waits for a TACACS+ server
host to reply.
The default is 5 seconds.

Step 4

tacacs-server attempts count

Set the number of login attempts that can be made on the
line.

Step 5

tacacs-server key key

Define a set of encryption keys for all of TACACS+ and
communication between the access server and the
TACACS daemon.
Repeat the command for each encryption key.

Step 6

exit

Return to privileged EXEC mode.

Step 7

show tacacs

Verify your entries.

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide
78-6511-05

6-63

Chapter 6

Configuring the System

Configuring TACACS+

Configuring Login Authentication
Beginning in privileged EXEC mode, follow these steps to configure login
authentication by using AAA/TACACS+:
Command

Purpose

Step 1

configure terminal

Enter global configuration mode.

Step 2

aaa new-model

Enable AAA/TACACS+.

Step 3

aaa authentication login
{default | list-name} method1
[method2...]

Enable authentication at login, and create one or more lists
of authentication methods.

Step 4

line [aux | 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.

Step 6

exit

Return to privileged EXEC mode.

Step 7

show running-config

Verify your entries.

The variable list-name is any character string used to name the list you are
creating. The method variable refers to the actual methods the authentication
algorithm tries, in the sequence entered. You can choose one of these methods:

line—Uses the line password for authentication. You must define a line
password before you can use this authentication method. Use the password
password line configuration command.

local—Uses the local username database for authentication. You must enter
username information into the database. Use the username password global
configuration command.

tacacs+—Uses TACACS+ authentication. You must configure the
TACACS+ server before you can use this authentication method. For more
information, see the “Configuring the TACACS+ Server Host” section on
page 6-62.

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide

6-64

78-6511-05

Chapter 6

Configuring the System
Configuring TACACS+

To create a default list that is used if no list is specified in the login
authentication line configuration command, use the default keyword followed
by the methods you want used in default situations.
The additional methods of authentication are used only if the previous method
returns an error, not if it fails. To specify that the authentication succeed even if
all methods return an error, specify none as the final method in the command line.

Specifying TACACS+ Authorization for EXEC Access and
Network Services
You can use the aaa authorization global configuration command with the
tacacs+ keyword to set parameters that restrict a user’s network access to Cisco
IOS privilege mode (EXEC access) and to network services such as Serial Line
Internet Protocol (SLIP), Point-to-Point Protocol (PPP) with Network Control
Protocols (NCPs), and AppleTalk Remote Access (ARA).
The aaa authorization exec tacacs+ local command sets the following
authorization parameters:

Note

Uses TACACS+ for EXEC access authorization if authentication was done
using TACACS+.

Uses the local database if authentication was not done using TACACS+.

Authorization is bypassed for authenticated users who login through the CLI
even if authorization has been configured.

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide
78-6511-05

6-65

Chapter 6

Configuring the System

Configuring TACACS+

Beginning in privileged EXEC mode, follow these steps to specify TACACS+
authorization for 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, including SLIP, PPP
NCPs, and ARA protocols.

Step 3

aaa authorization exec tacacs+ Configure the switch for user TACACS+ authorization to
determine if the user is allowed EXEC access.
The exec keyword might return user profile information
(such as autocommand information).

Step 4

exit

Return to privileged EXEC mode.

Starting TACACS+ Accounting
You use the aaa accounting command with the tacacs+ keyword to turn on
TACACS+ accounting for each Cisco IOS privilege level and for network
services.
Beginning in privileged EXEC mode, follow these steps to enable TACACS+
accounting:
Command

Purpose

Step 1

configure terminal

Enter global configuration mode.

Step 2

aaa accounting exec start-stop Enable TACACS+ accounting to send a start-record
tacacs+
accounting notice at the beginning of an EXEC process and
a stop-record at the end.

Step 3

aaa accounting network
start-stop tacacs+

Enable TACACS+ accounting for all network-related
service requests, including SLIP, PPP, and PPP NCPs.

Step 4

exit

Return to privileged EXEC mode.

Note

These commands are documented in the “Accounting and Billing Commands”
chapter of the Cisco IOS Release 12.0 Security Command Reference.

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide

6-66

78-6511-05

Chapter 6

Configuring the System
Configuring TACACS+

Configuring a Switch for Local AAA
You can configure AAA to operate without a server by setting the switch to
implement AAA in local mode. The switch then verifies 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 authorization to default to local.

Step 4

aaa authorization exec local

Configure user AAA authorization for all network-related
service requests, including SLIP, PPP NCPs, and ARA
protocols.

Step 5

aaa authorization network
local

Configure user AAA authorization to determine if the user
is allowed to run an EXEC shell.

Step 6

username name password
password privilege level

Enter the local database.
Repeat this command for each user.

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide
78-6511-05

6-67

Chapter 6 Configuring the System Configuring TACACS+ Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-68 78-6511-05 .

For switch features that use standard Cisco IOS Release 12. This chapter does not repeat the concepts and CLI procedures provided in the standard Cisco IOS Release 12.0 commands. Review the “Avoiding Configuration Conflicts” section on page 9-2 before you change the port settings. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 7-1 . Note Certain port features can conflict with one another.0 documentation.C H A P T E R 7 Configuring the Switch Ports This chapter provides information about changing port configuration settings. Note Some features can be implemented only by using the CLI. For information about configuring these settings from Cluster Management Suite (CMS). refer to the online help. For complete syntax and usage information for the commands used in this chapter.0 documentation on Cisco. It includes command-line interface (CLI) procedures for using commands that have been specifically created or changed for the Catalyst 2900 XL or Catalyst 3500 XL switches.com for additional information and CLI procedures. refer to the Cisco IOS Release 12. refer to the Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference.

the switch can take up to 30 seconds to check for loops when a port is reconfigured. • GigaStack-to-GigaStack stack connections operate in half-duplex mode. • Gigabit Ethernet ports that do not match the settings of an attached device lose connectivity and do not generate statistics. To connect to a remote Gigabit Ethernet device that does not autonegotiate. disable autonegotiation on the local device. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 7-2 78-6511-05 . The Ethernet link settings on the Long-Reach Ethernet (LRE) ports have special considerations and different default settings than from the 10/100 ports. and set the duplex and flow control parameters to be compatible with the other device. see the “LRE Ethernet Links” section on page 7-25. • Asynchronous Transfer Mode (ATM) ports are always set to full duplex and do not autonegotiate duplex or speed settings.Chapter 7 Configuring the Switch Ports Changing the Port Speed and Duplex Mode Changing the Port Speed and Duplex Mode Caution Note If you reconfigure the port through which you are managing the switch. but the duplex setting must be explicitly set. Follow these guidelines when configuring the duplex and speed settings: • Gigabit Ethernet ports are always set to 1000 Mbps but can negotiate full or half duplex with the attached device. set the duplex setting to Full or Half. and set the speed setting to Auto. a Spanning Tree Protocol (STP) reconfiguration could cause a temporary loss of connectivity. Autonegotiation for the speed setting selects the correct speed even if the attached device does not autonegotiate. Connecting to Devices That Do Not Autonegotiate To connect to a remote 100BASE-T device that does not autonegotiate. • If STP is enabled. The port LED is amber while STP reconfigures. and GigaStack-to-GigaStack point-to-point connections operate in full-duplex mode. For this information.

and enter the port to be configured. Step 4 end Return to privileged EXEC mode. and enter the port to be configured. Step 2 interface interface Enter interface configuration mode. Command Purpose Step 1 configure terminal Enter global configuration mode. Step 5 show running-config Verify your entries. Step 3 speed {10 | 100 | auto} Enter the speed parameter for the port. Step 2 interface interface Enter interface configuration mode. You cannot enter the speed on Gigabit Ethernet or ATM ports. Step 6 copy running-config startup-config (Optional) Save your entry in the configuration file. This retains the configuration when the switch restarts. Step 7 copy running-config startup-config (Optional) Save your entry in the configuration file. This retains the configuration when the switch restarts. follow these steps to configure flow control on a Gigabit Ethernet port.Chapter 7 Configuring the Switch Ports Changing the Port Speed and Duplex Mode Setting Speed and Duplex Parameters Beginning in privileged EXEC mode. Step 4 duplex {full | half | auto} Enter the duplex parameter for the port. follow these steps to set the speed and duplex parameters on a port: Command Purpose Step 1 configure terminal Enter global configuration mode. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 7-3 . Step 5 end Return to privileged EXEC mode. Step 6 show running-config Verify your entries. Step 3 flowcontrol [asymmetric | symmetric] Configure flow control for the port. Configuring Flow Control on Gigabit Ethernet Ports Beginning in privileged EXEC mode.

The rising threshold is the number of packets that a switch port can receive before forwarding is blocked. Storm control uses high and low thresholds to block and then restore the forwarding of broadcast. You can also set the switch to shut down the port when the rising threshold is reached. By default.Chapter 7 Configuring the Switch Ports Configuring Flooding Controls Configuring Flooding Controls You can use the following flooding techniques to block the forwarding of unnecessary flooded traffic: • Enable storm control for unicast. or multicast packets are received on a port. or multicast packets. the less effective the protection against broadcast storms. The falling threshold is the number of packets below which the switch resumes normal forwarding. storm control is disabled. In general.000 packets per second. The maximum half-duplex transmission on a 100BASE-T link is 148. Forwarding these packets can cause the network to slow down or to time out. but you can enter a threshold of up to 4294967295 broadcast packets per second. or broadcast packets • Block the forwarding of unicast and broadcast packets on a per-port basis • Flood all unknown packets to a network port (configured only by using CLI) Enabling Storm Control A packet storm occurs when a large number of broadcast. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 7-4 78-6511-05 . Storm control is configured for the switch as a whole but operates on a per-port basis. unicast. the higher the threshold. multicast. unicast.

Command Purpose Step 1 configure terminal Enter global configuration mode.Chapter 7 Configuring the Switch Ports Configuring Flooding Controls With the exception of the broadcast keyword. follow these steps to enable broadcast-storm control. Step 5 end Return to privileged EXEC mode. Step 4 end Return to privileged EXEC mode. follow these steps to disable broadcast-storm control. and enter the port to configure. and enter the port to configure. Beginning in privileged EXEC mode. Step 4 port storm-control trap Generate an SNMP trap when the traffic on the port crosses the rising or falling threshold. Command Purpose Step 1 configure terminal Enter global configuration mode. the following procedure could also be used to enable storm control for unicast or multicast packets. Step 2 interface interface Enter interface configuration mode. Step 3 no port storm-control broadcast Disable port storm control. Step 3 port storm-control broadcast [threshold {rising rising-number falling falling-number}] Enter the rising and falling thresholds for broadcast packets. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 7-5 . Make sure the rising threshold is greater than the falling threshold. Step 2 interface interface Enter interface configuration mode. Step 5 show port storm-control [interface] Verify your entries. Step 6 show port storm-control [interface] Verify your entries. Disabling Storm Control Beginning in privileged EXEC mode.

and enter the port to configure. Step 4 port block unicast Block unknown unicast flooding to the port. Step 6 show port block {multicast | unicast} interface Verify your entries. Step 2 interface interface Enter interface configuration mode. flooded traffic does not cross VLAN boundaries. the switch floods packets with unknown destination MAC addresses to all ports. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 7-6 78-6511-05 . Some configurations do not require flooding. Step 3 port block multicast Block unknown multicast forwarding to the port. and flooding serves no purpose. Step 5 end Return to privileged EXEC mode. Ordinarily. Beginning in privileged EXEC mode. entering the appropriate command once for the multicast option and once for the unicast option. For example.Chapter 7 Configuring the Switch Ports Configuring Flooding Controls Blocking Flooded Traffic on a Port By default. a port that has only manually assigned addresses has no unknown destinations. you can disable the flooding of unicast and multicast packets on a per-port basis. but multi-VLAN ports flood traffic to all VLANs they belong to. follow these steps to disable the flooding of multicast and unicast packets to a port: Command Purpose Step 1 configure terminal Enter global configuration mode. Therefore.

Caution A network port cannot link cluster members. see the “Changing the Password” section on page 6-15. follow these steps to resume normal forwarding on a port: Command Purpose Step 1 configure terminal Enter global configuration mode.Chapter 7 Configuring the Switch Ports Configuring Flooding Controls Resuming Normal Forwarding on a Port Beginning in privileged EXEC mode. The switch forwards all traffic with unknown destination addresses to the network port instead of flooding the traffic to all ports in the VLAN. If you configure other ports in the VLAN as secure ports. You can assign only one network port per VLAN. Enabling a Network Port Network ports are assigned per VLAN and can reduce flooded traffic on your network. For the restrictions that apply to a network port. the addresses on those ports are not aged. Step 5 end Return to privileged EXEC mode Step 6 show port block {multicast | unicast} interface Verify your entries. it becomes the network port for the new VLAN. and enter the port to configure. Step 4 no port block unicast Enable unknown unicast flooding to the port. When you configure a port as the network port. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 7-7 . Step 2 interface interface Enter interface configuration mode. entering the appropriate command once for the multicast option and once for the unicast option. Step 3 no port block multicast Enable unknown multicast forwarding to the port. If you move a network port to a VLAN without a network port. You cannot change the settings for unicast and multicast flooding on a network port. the switch deletes all associated addresses from the address table and disables learning on the port.

and enter the port to be configured. Disabling a Network Port Beginning in privileged EXEC mode. Step 2 interface interface Enter interface configuration mode. Step 5 show running-config Verify your entry. Step 2 interface interface Enter interface configuration mode.Chapter 7 Configuring the Switch Ports Configuring Flooding Controls Beginning in privileged EXEC mode. Step 3 no port network Disable the port as the network port. Step 4 end Return to privileged EXEC mode. Step 5 show running-config Verify your entry. follow these steps to define a network port: Command Purpose Step 1 configure terminal Enter global configuration mode. follow these steps to disable a network port: Command Purpose Step 1 configure terminal Enter global configuration mode. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 7-8 78-6511-05 . and enter the port to be configured. Step 3 port network Define the port as the network port. Step 4 end Return to privileged EXEC mode.

Chapter 7 Configuring the Switch Ports Configuring UniDirectional Link Detection Configuring UniDirectional Link Detection UniDirectional Link Detection (UDLD) is a Layer 2 protocol that detects and shuts down unidirectional links. Step 2 udld enable Enable UDLD on all switch ports. Use the udld interface configuration command to enable UDLD on a specific port. Step 4 show running-config Verify the entry by displaying the running configuration. Step 3 end Return to privileged EXEC mode. You can configure UDLD on the entire switch or on an individual port. Use the udld reset command to reset all ports that have been shut down by UDLD. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 7-9 . Beginning in privileged EXEC mode. follow these steps to configure UDLD on a switch: Command Purpose Step 1 configure terminal Enter global configuration mode.

You can create up to 12 port groups. Note You can create port groups of either Gigabit Ethernet ports or 100BASE-TX ports. Source-based forwarding is enabled by default. Destination-based port groups distribute packets forwarded to the group based on the destination address of incoming packets. You can configure an unlimited number of ports in a destination-based port group. Understanding EtherChannel Port Grouping This software release supports two different types of port groups: source-based forwarding port groups and destination-based forwarding port groups. they must be all source-based or all destination-based. You can configure up to eight ports in a source-based forwarding port group. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 7-10 78-6511-05 . see the “Avoiding Configuration Conflicts” section on page 9-2. for example. Source-based forwarding port groups distribute packets forwarded to the group based on the source address of incoming packets. but you cannot create a port group that has both port speeds. For the restrictions that apply to port groups. All ports in each group must be of the same type. You can independently configure port groups that link switches. You can have source-based port groups and destination-based source groups.Chapter 7 Configuring the Switch Ports Creating EtherChannel Port Groups Creating EtherChannel Port Groups Fast EtherChannel (FEC) and Gigabit EtherChannel port groups act as single. logical ports for high-bandwidth connections between switches or between switches and servers. but you must consistently configure both ends of a port group.

when you create a port group. Because the router is a single-MAC-address device. configure the static address to forward to only one port in the port group. For more information. the switch uses the configuration of the first port for all ports added to the group. configure the static address to forward to all ports in the group. The router is configured for destination-based forwarding because the large number of stations ensures that the traffic is evenly distributed through the port-group ports on the router. Each port group has one port that carries all unknown multicast. see the “Adding Static Addresses” section on page 6-59.Chapter 7 Configuring the Switch Ports Creating EtherChannel Port Groups In Figure 7-1. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 7-11 . This method eliminates the chance of lost packets. This method avoids the possible transmission of duplicate packets. Figure 7-1 Source-Based Forwarding Source-based forwarding Destination-based forwarding Catalyst 2900 XL or Catalyst 3500 XL switch Cisco router 12650 FEC port group The switch treats the port group as a single logical port. If you add a port and change the forwarding method. • If the port group forwards based on the destination address. After the group is created. changing STP or VLAN membership parameters for one port in the group automatically changes the parameters for all ports. therefore. broadcast. source-based forwarding ensures that the switch uses all available bandwidth to the router. it changes the forwarding for all ports in the group. Port Group Restrictions on Static-Address Forwarding The following restrictions apply to entering static addresses that are forwarded to port groups: • If the port group forwards based on the source MAC address (the default). and STP packets. a port group of two workstations communicates with a router.

follow these steps to create a two-port group: Command Purpose Step 1 configure terminal Enter global configuration mode. Step 5 port group 1 distribution destination Assign the port to group 1 with destination-based forwarding.Chapter 7 Configuring the Switch Ports Creating EtherChannel Port Groups Creating EtherChannel Port Groups Beginning in privileged EXEC mode. Step 4 interface interface Enter the second port to be added to the group. Step 2 interface interface Enter interface configuration mode. Step 7 show running-config Verify your entries. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 7-12 78-6511-05 . Step 3 port group 1 distribution destination Assign the port to group 1 with destination-based forwarding. Step 6 end Return to privileged EXEC mode. and enter the port of the first port to be added to the group.

Use the no version of the port protected interface configuration command to disable the protected port option. Step 3 port protected Enable protected port on the port. Step 2 interface interface Enter interface configuration mode. Step 5 show port protected Verify that the protected port option is enabled. you can configure Catalyst 2900 XL and Catalyst 3500 XL ports as protected ports (also referred to as private VLAN edge ports). and traffic between ports on the same switch is forwarded through a Layer 3 device such as a router. Note Sometimes unknown unicast traffic from a nonprotected port is flooded to a protected port because a MAC address has timed out or has not been learned by the switch. or multicast traffic between ports on the switch. Step 4 end Return to privileged EXEC mode. This means that all traffic passing between protected ports—unicast. Protected ports can forward any type of traffic to nonprotected ports. See the “Configuring Flooding Controls” section on page 7-4 for more information. and they forward as usual to all ports on other switches. and multicast—must be forwarded through a Layer 3 device. follow these steps to define a port as a protected port: Command Purpose Step 1 configure terminal Enter global configuration mode. In such an environment. broadcast.Chapter 7 Configuring the Switch Ports Configuring Protected Ports Configuring Protected Ports Some applications require that no traffic be forwarded by the Layer 2 protocol between ports on the same switch. Protected ports do not forward any traffic to protected ports on the same switch. Use the port block command to guarantee that in such a case no unicast and multicast traffic is flooded to the port. To meet this requirement. Beginning in privileged EXEC mode. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 7-13 . there is no exchange of unicast. broadcast. and enter the port to be configured.

The following options validate port security or indicate security violations: Interface Port to secure. the switch does not forward any packets with source addresses outside the group of addresses you have defined. Secure ports have at least one address.Chapter 7 Configuring the Switch Ports Enabling Port Security Enabling Port Security Secured ports restrict a port to a user-defined group of stations. Secured ports generate address-security violations under the following conditions: • The address table of a secured port is full and the address of an incoming packet is not found in the table. Secure Addresses Number of addresses in the address table for this port. Limiting the number of devices that can connect to a secure port has the following advantages: • Dedicated bandwidth—If the size of the address table is set to 1. Max Addresses Number of addresses that the address table for the port can contain. Trap Issue a trap when an address-security violation occurs. Security Rejects The number of unauthorized addresses seen on the port. see the “Avoiding Configuration Conflicts” section on page 9-2. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 7-14 78-6511-05 . As part of securing the port. Security Enable port security on the port. the workstation or server attached to that port is guaranteed the full bandwidth of the port. the attached device is guaranteed the full bandwidth of the port. • An incoming packet has a source address assigned as a secure address on another port. Shutdown Port Disable the port when an address-security violation occurs. • Added security—Unknown devices cannot connect to the port. you can also define the size of the address table for the port. When you assign secure addresses to a secure port. For the restrictions that apply to secure ports. If you define the address table of a secure port to contain only one address.

Setting one address in the MAC address table for the port ensures that the attached device has the full bandwidth of the port. Step 5 show port security Verify the entry. Step 6 show port security Verify the entry. follow these steps to disable port security. Disabling Port Security Beginning in privileged EXEC mode. Command Purpose Step 1 configure terminal Enter global configuration mode. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 7-15 . Enabling Port Security Beginning in privileged EXEC mode. Step 3 no port security Disable port security. follow these steps to enable port security. Step 2 interface interface Enter interface configuration mode for the port you want to unsecure. Step 5 end Return to privileged EXEC mode. Step 2 interface interface Enter interface configuration mode for the port you want to secure.Chapter 7 Configuring the Switch Ports Enabling Port Security Defining the Maximum Secure Address Count A secure port can have from 1 to 132 associated secure addresses. Step 4 end Return to privileged EXEC mode. Step 3 port security max-mac-count 1 Secure the port and set the address table to one address. Command Purpose Step 1 configure terminal Enter global configuration mode. Step 4 port security action shutdown Set the port to shutdown when a security violation occurs.

Step 3 no port monitor interface Disable port monitoring on the port. and any combination of ports can be monitored.Chapter 7 Configuring the Switch Ports Enabling Port Security Enabling SPAN You can use Switch Port Analyzer (SPAN) to monitor traffic on a given port by forwarding incoming and outgoing traffic on the port to another port in the same VLAN. Step 4 end Return to privileged EXEC mode. You can define any number of ports as SPAN ports. follow these steps to disable SPAN: Command Purpose Step 1 configure terminal Enter global configuration mode. Step 3 port monitor interface Enable port monitoring on the port. Disabling SPAN Beginning in privileged EXEC mode. Beginning in privileged EXEC mode. Step 2 interface interface Enter interface configuration mode. Step 5 show running-config Verify your entries. follow these steps to enable SPAN: Command Purpose Step 1 configure terminal Enter global configuration mode. Step 4 end Return to privileged EXEC mode. see the “Avoiding Configuration Conflicts” section on page 9-2. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 7-16 78-6511-05 . Step 5 show running-config Verify your entries. Step 2 interface interface Enter interface configuration mode. A SPAN port cannot monitor ports in a different VLAN. and enter the port number of the monitor port. and enter the port that acts as the monitor port. and a SPAN port must be a static-access port. For the restrictions that apply to SPAN ports.

1p class of service (CoS).1Q trunk 33048 IP Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 7-17 . If necessary. The ports are dedicated connections to the following devices: • Port 1 connects to the Catalyst 3524-PWR XL switch or other voice-over-IP device. QoS uses classification and scheduling to transmit network traffic from the switch in a predictable manner. You can use the CLI to configure the Catalyst 3524-PWR XL to honor or ignore a traffic priority assigned by a Cisco 7960 IP Phone. • Port 2 is an internal 10/100 interface that carries the phone traffic. • Port 3 connects to a PC or other device. Figure 7-2 shows one way to configure a Cisco 7960 IP Phone. the Catalyst 3524-PWR XL can supply electrical power to the circuit connecting it to the Cisco 7960 IP Phone. The Cisco 7960 IP Phone contains an integrated three-port 10/100 switch. Figure 7-2 Cisco 7960 IP Phone Connected to a Catalyst 3524-PWR XL Switch Catalyst 3524-PWR XL Cisco 7960 IP Phone PC 802. Because the sound quality of an IP telephone call can deteriorate if the data is unevenly transmitted. and you can configure it to forward traffic with an 802.Chapter 7 Configuring the Switch Ports Configuring Voice Ports Configuring Voice Ports The Catalyst 2900 XL and Catalyst 3500 XL switches can connect to a Cisco 7960 IP Phone and carry IP voice traffic. this release of IOS supports quality of service (QoS) based on IEEE 802.1p priority. The Cisco 7960 IP Phone itself is also a configurable device.

• Voice and data traffic are carried on separate VLANs. and voice traffic always has a CoS priority of 5.1Q native VLAN. follow these steps to configure a port to instruct the phone to give voice traffic a higher priority and to forward all traffic through the 802.1Q trunk and as a member of the voice VLAN (VVID). Configuring a Port to Connect to a Cisco 7960 IP Phone Because a Cisco 7960 IP Phone also supports connection to a PC or other device.1p priority tagging for voice traffic and to use VLAN 0 (default native VLAN) to carry all traffic. • Beginning in privileged EXEC mode. See the “Configuring a Trunk Port” section on page 8-38 for instructions. Step 3 switchport voice vlan dot1p Instruct the switch to use 802. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 7-18 78-6511-05 . and enter the port to be configured. • Voice traffic is given a higher priority by the phone. configure the port as an 802. a port connecting a Catalyst 3524-PWR XL switch to a Cisco 7960 IP Phone can carry mixed traffic. This is the default. Step 2 interface interface Enter interface configuration mode. Command Purpose Step 1 configure terminal Enter global configuration mode. and all traffic is in the same VLAN. There are three configurations for a port connected to a Cisco 7960 IP Phone: All traffic is transmitted according to the default COS priority of the port.Chapter 7 Configuring the Switch Ports Configuring Voice Ports Preparing a Port for a Cisco 7960 IP Phone Connection Before you configure a Catalyst 3524-PWR XL port to carry IP voice traffic. Step 4 end Return to privileged EXEC mode. Step 5 show interface interface switchport Verify the port configuration.

If you want. Beginning in privileged EXEC mode. Use the no switchport priority extend command to return the port to its default setting. you can use the Catalyst 3524-PWR XL CLI to override the priority of frames arriving on the phone port from connected devices. The PC can generate packets with an assigned CoS value. Step 4 end Return to privileged EXEC mode. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 7-19 . follow these steps to override the CoS priority setting received from the non-voice port on the Cisco 7960 IP Phone: Command Purpose Step 1 configure terminal Enter global configuration mode. and enter the switch port to be configured. Step 2 interface interface Enter interface configuration mode. You can also set the phone port to accept (trust) the priority of frames arriving on the port. Step 5 show interface interface switchport Verify the change.Chapter 7 Configuring the Switch Ports Configuring Voice Ports Overriding the CoS Priority of Incoming Frames A PC or other data device can connect to a Cisco 7960 IP Phone port. Step 3 switchport priority extend cos 3 Set the phone port to override the priority received from the PC or the attached device and forward the received data with a priority of 3.

1p priority of 5. VLAN 1. Step 2 interface interface Enter interface configuration mode. Beginning in privileged EXEC mode. In the following configuration. Step 4 switchport voice vlan (2) Instruct the Cisco IP Phone to forward all voice traffic through VLAN 2. Step 3 switchport priority default (0) Assign an IEEE 802.1p priority to untagged traffic that is received on the switch port. you must connect all Cisco IP Phones and other voice-related devices to switch ports that belong to VLAN 2. VLAN 1 carries data traffic. In this configuration. You can configure a switch port to instruct the phone to forward voice and data traffic on different virtual LANs (VLANs). follow these steps to configure a port to receive voice and data from a Cisco IP Phone in different VLANs: Command Purpose Step 1 configure terminal Enter global configuration mode. and VLAN 2 carries voice traffic. and enter the port to be configured.Chapter 7 Configuring the Switch Ports Configuring Voice Ports Configuring Voice Ports to Carry Voice and Data Traffic on Different VLANs The Cisco 7960 IP Phone has an integrated three-port 10/100 switch that can connect to a PC or other device. The Cisco IP Phone forwards this traffic through the native VLAN. The Cisco IP Phone forwards the traffic with an 802. Step 6 show interface interface switchport Verify the configuration. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 7-20 78-6511-05 . Step 5 end Return to privileged EXEC mode.

the switch supplies the power. Step 4 end Return to privileged EXEC mode. Step 2 interface interface Enter interface configuration mode. When the Cisco 7960 IP Phone supplies its own power. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 7-21 . any Catalyst 2900 XL or Catalyst 3500 XL can forward IP voice traffic to and from the phone. Command Purpose Step 1 configure terminal Enter global configuration mode. The Cisco 7960 IP Phone can also be connected to an AC power source and supply its own power to the voice circuit. Step 5 show power inline interface configured Verify the change. You can configure the switch to never supply power to the Cisco 7960 IP Phone and to disable the detection mechanism. Step 3 power inline never Permanently disable inline power on the port. If there is power on the circuit. Beginning in privileged EXEC mode. To enable inline power when a Cisco 7960 IP Phone is detected. See the “Configuring Voice Ports” section on page 7-17 for the CLI commands that you use to supply inline power to a Cisco 7960 IP Phone. and enter the port to be configured.Chapter 7 Configuring the Switch Ports Configuring Inline Power on the Catalyst 3524-PWR Ports Configuring Inline Power on the Catalyst 3524-PWR Ports The Catalyst 3524-PWR XL can supply inline power to the Cisco 7960 IP Phone. the switch does not supply it. If there is no power on the circuit. follow these steps to configure a port to never supply power to Cisco 7960 IP Phones. The Catalyst 3524-PWR XL senses if it is connected to a Cisco 7960 IP Phone. use the power inline auto command. if necessary.

Downstream transmission refers to the data traveling from the LRE port to the CPE. Upstream transmission refers to the data traveling from the CPE to the LRE port. such as a PC. not 100 Mbps. the actual upload rate provided to the PC user is 5. in either direction. • Ethernet link—This is the connection between the 10/100 Ethernet port on the CPE and an Ethernet device. Asymmetrical transmission is when the downstream and the upstream bandwidth differ. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 7-22 78-6511-05 . For example. LRE Links and LRE Profiles The LRE link settings on the LRE ports define the connection between the switch LRE port and the WALL port on the Cisco 575 LRE CPE. depends on the active profile for the LRE port and the Ethernet link speed. Symmetrical transmission is when the downstream and upstream bandwidth are the same. This connection can be through a standard telephone line (categorized and noncategorized unshielded twisted-pair cable) and can extend to distances of up to 4921 ft (1500 m).69 Mbps. Connecting a switch LRE switch port to a remote Ethernet device requires two types of connections: • LRE link—This is the connection between the switch LRE port and the WALL port on the Cisco 575 LRE customer premises equipment (CPE). if a PC Ethernet port is configured to 100 Mbps and the LRE port is configured with an upstream link rate of 5.Chapter 7 Configuring the Switch Ports Configuring the LRE Ports Configuring the LRE Ports The Catalyst 2900 LRE XL switches use Long-Reach Ethernet (LRE) technology to transfer data and voice traffic over existing standard telephone lines. This connection is through standard Category 5 cabling and can extend to distances of up to 328 ft (100 m).69 Mbps. The LRE link provides symmetric and asymmetric bandwidth for voice and data traffic.06 Mbps. Conversely. the actual upload rate provided to the PC user is 17. The actual link rate between an LRE port and a remote Ethernet device.06 Mbps. if the PC Ethernet port is configured to 10 Mbps and the LRE port is configured with an upstream link rate of 17.

the upstream and downstream bands on an LRE link can be approximately 5. all LRE ports use the same configuration to prevent the switch from causing interference with the other lines on the PSTN. 10. You can assign profiles on a per-port or switch-wide basis. the switch downloads its profile settings to the CPE port so that both ports on both devices operate with the same configuration. The PUBLIC-ANSI profile corresponds to ANSI Plan 998. • Private—You can use a private profile if the LRE switch is not used with equipment connected to a PSTN. • Public—We strongly recommend using a public profile if the switch is used with equipment connected to a Public Switched Telephone Network (PSTN). By default. When the LRE port establishes a link with the CPE. In general. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 7-23 . all LRE ports on the switch are enabled with the LRE-10 private profile in effect. the higher the link speed. or 15 Mbps. When the switch is configured with a public profile. Both plans are draft standards. Contact Cisco Systems for the latest information about standards ratification or for updates to the public profiles. The PUBLIC-ETSI profile corresponds to ETSI Plan 997. Depending on the profile. Private profiles are assigned on a per-port basis. The standards for spectral profiles have not yet been ratified. An LRE profile configures the upstream and downstream rates on the LRE link.Chapter 7 Configuring the Switch Ports Configuring the LRE Ports Bandwidth within the LRE link is controlled by the switch by using configurations called profiles. the shorter the maximum distance. The Catalyst 2900 LRE XL switches are shipped with predefined profiles (Table 7-1) categorized as public (global) mode and private (per-port) mode profiles. Three private profiles offer different link speeds and maximum distances. The ports on an LRE switch can be assigned the same or different private profiles.

If you assign a public profile to the switch.27 4101 ft (1250 m) LRE-5 Private 5. the change immediately takes effect. how it is bundled.17 4. and the interference and noise on the LRE link can affect the actual LRE link performance. If a public profile is configured on the switch and you want the LRE ports to use private profiles. Contact Cisco Systems for information about limitations and optimization of LRE link performance. If no public profile is configured on the switch. the LRE port uses its private profile. public profiles have priority over private profiles.69 5. the switch ignores the private profile settings and uses the public profile settings on all LRE ports. you must first disable the public profile by using CMS or by using the no lre profile global global configuration command.27 4101 ft (1250 m) PUBLIC-ETSI Public 11.69 4921 ft (1500 m) LRE-10 (default) Private 11. keep the following considerations in mind: • An LRE port always has a private profile assigned to it.06 3445 ft (1050 m) When assigning a profile to an LRE port.17 17. However.38 4. the change immediately takes effect. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 7-24 78-6511-05 .Chapter 7 Configuring the Switch Ports Configuring the LRE Ports Note Use the rates and distances in Table 7-1 as guidelines only. The net data rates in Table 7-1 are slightly less than the gross data rates displayed by the show controllers lre profile names privileged EXEC command. If you assign a different private profile to the LRE port.38 4101 ft (1250 m) LRE-15 Private 15.38 11. Table 7-1 LRE Profiles Profile Name Profile Type LRE Link Downstream Rate (Mbps) LRE Link Upstream Rate (Mbps) Maximum Distance between the LRE Port and the CPE PUBLIC-ANSI Public 15. Factors such as the type of cable you use. If you assign a different public profile.

see Chapter 5. You can set the CPE Ethernet port to operate at 10 or 100 Mbps and at halfor full-duplex mode. depending on the capability of the remote Ethernet device. The flow control setting on the remote CPE Ethernet port is automatically disabled on LRE ports in half-duplex mode.” Use the show controllers lre privileged EXEC commands to display the LRE link statistics and profile information on the LRE ports. Before you add an LRE switch to a cluster.1x full-duplex flow control. Autonegotiation for port speed and duplex mode is supported. to prevent the possible loss of data when the LRE link is configured to be slower than the Ethernet link. “Clustering Switches. the default duplex mode is half duplex. The default speed for the CPE Ethernet port is auto. keep in mind the following guidelines: The speeds on the LRE and Ethernet links do not need to match. all LRE switches in that cluster must have that same public profile. make sure that you assign it the same public profile used by other LRE switches in the cluster. When configuring the Ethernet link on the LRE ports. refer to the Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference. LRE Ethernet Links The Ethernet link settings on the LRE ports are for configuring the remote CPE Ethernet port.Chapter 7 Configuring the Switch Ports Configuring the LRE Ports A configuration conflict occurs if a switch cluster has LRE switches using both private and public profiles. • A cluster can have a mix of LRE switches using different private profiles. However. and is automatically enabled on LRE ports in full-duplex mode. which is the default. choose one of the following: • – Configure the LRE port to use half-duplex mode. The PC user should notice no significant difference in performance between 100-Mbps half duplex and 100-Mbps full duplex. – Use duplex autonegotiation or full-duplex mode only if the remote device supports 802. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 7-25 . For more information about clusters. If one LRE switch in a cluster is assigned a public profile. Note You cannot configure the flow control setting on the LRE ports. For information about these commands. and they define the connection between the Ethernet port on the Cisco 575 LRE CPE and an Ethernet device such as a PC or a television set-top box.

This prevents access to the LRE port and prevents the power emitted from the port from affecting other ports. and the statistics collected by the CPE LRE chipset. Use the show controllers ethernet-controller privileged EXEC command to display the internal switch statistics. For information about this command.Chapter 7 Configuring the Switch Ports Configuring the LRE Ports Note • Enable CDP either globally on the LRE switch or on the specific LRE ports. refer to the Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference. the statistics collected by the switch LRE chipset. We recommend that you use the lre shutdown interface configuration command to disable the LRE chipset transmitter on any LRE ports that are not connected to a CPE. • The switch 10/100 port defaults are not the same as the defaults for the Ethernet link on the LRE ports. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 7-26 78-6511-05 .

use the no lre profile global global configuration command. To disable the public profile on the switch. follow these steps to assign a public profile to the LRE ports: Command Purpose Step 1 configure terminal Enter global configuration mode. the switch ignores the private profile settings and uses the public profile settings on all LRE ports. and the public mode automatically becomes the active mode. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 7-27 . The public profile you select should be compatible with the PSTN to which the LRE switch is connected. Changes to the public profile settings are immediately put in effect. Step 2 lre profile global profile_name Enter the public profile name: PUBLIC-ANSI or PUBLIC-ETSI. For information about these commands.Chapter 7 Configuring the Switch Ports Configuring the LRE Ports Assigning a Public Profile to All LRE Ports Public profiles are set on a switch-wide (global) basis. refer to the Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference. Step 4 show controllers lre profile mapping Verify the change. If you assign a public profile to the switch. Beginning in privileged EXEC mode. Public profiles have priority over private profiles. Step 3 end Return to privileged EXEC mode. Use the show controllers lre commands to display the LRE link statistics and profile information on the LRE ports.

LRE-10. follow these steps to assign a private profile to an LRE port: Command Purpose Step 1 configure terminal Enter global configuration mode. or LRE-15. Beginning in privileged EXEC mode. The switch resets the ports with the updated profile settings. Step 4 end Return to privileged EXEC mode. For information about these commands. and enter the number of the LRE port to be configured.Chapter 7 Configuring the Switch Ports Configuring the LRE Ports Assigning a Private Profile to an LRE Port Private profiles are set on a per-port basis. refer to the Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 7-28 78-6511-05 . Step 2 interface LRE-interface Enter interface configuration mode. Step 3 lre profile profile_name Enter the private profile name: LRE-5. Step 5 show controllers lre profile mapping Verify the change. Use the show controllers lre commands to display the LRE link statistics and profile information on the LRE ports. The default active private profile on all LRE ports is LRE-10. The default profile is LRE-10. You can assign the same private profile or different private profiles to the LRE ports on the switch.

Note Certain port features can conflict with one another. Note Some features can be implemented only by using the CLI.0 documentation on Cisco.C H A P T E R 8 Configuring VLANs This chapter provides information about configuring virtual LANs (VLANs). This chapter does not repeat the concepts and CLI procedures provided in the standard Cisco IOS Release 12. For information about configuring these settings from Cluster Management Suite (CMS). Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-1 . refer to the online help.0 documentation. It includes command-line interface (CLI) procedures for using commands that have been specifically created or changed for the Catalyst 2900 XL or Catalyst 3500 XL switches. Review the “Avoiding Configuration Conflicts” section on page 9-2 before you change the port settings. For switch features that use standard Cisco IOS Release 12.0 commands. For complete syntax and usage information for the commands used in this chapter. refer to the Cisco IOS Release 12. refer to the Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference.com for additional information and CLI procedures.

without regard to the physical locations of the users. Because a VLAN is considered a separate logical network. Any switch port can belong to a VLAN. VLANs are identified with a number of 1 to 1001. project team. it contains its own bridge Management Information Base (MIB) information and can support its own implementation of the Spanning Tree Protocol (STP). or application. and packets destined for stations that do not belong to the VLAN must be forwarded through a router or bridge as shown in Figure 8-1. Figure 8-1 VLANs as Logically Defined Networks Catalyst 3500 series XL Engineering VLAN Marketing VLAN Accounting VLAN Cisco router Floor 3 Catalyst 2900 series XL Fast Ethernet Floor 2 Catalyst 2900 series XL 15933 Floor 1 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-2 78-6511-05 . see the “Supported STP Instances” section on page 6-24. Each VLAN is considered a logical network. and multicast packets are forwarded and flooded only to stations in the VLAN.Chapter 8 Configuring VLANs Overview Overview A virtual LAN (VLAN) is a switched network that is logically segmented by function. and unicast. broadcast. For information about managing VLAN STP instances.

The GigaStack GBIC also supports both trunking methods. Catalyst 2924 XL. Trunking is not supported on all switches and modules. refer to the release notes. Table 8-1 Maximum Number of Supported VLANs Number of Supported VLANs Trunking Supported? Catalyst 2912 XL.1Q trunking methods for transmitting VLAN traffic over 100BASE-T and Gigabit Ethernet ports. For the list of products that support trunking. and Catalyst 2924C XL switches 64 Yes Catalyst 2900 LRE XL switches 250 Yes Catalyst 2912M and Catalyst 2924M modular switches 250 Yes Catalyst 3500 XL switches 250 Yes Switch The switches in Table 8-1 support both Inter-Switch Link (ISL) and IEEE 802. refer to the Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-3 . When you are configuring a cascaded stack of Catalyst 3500 XL switches using the GigaStack GBIC and want to include more than one VLAN in the stack. For more information on these commands. be sure to configure all of the GigaStack GBIC interfaces as trunk ports by using the switchport mode trunk interface configuration command and to use the same encapsulation method by using the switchport encapsulation {isl | dot1q} interface configuration command.Chapter 8 Configuring VLANs Overview Table 8-1 lists the number of supported VLANs on the switches.

You cannot create or remove the management VLAN through Simple Network Management Protocol (SNMP). • With the exception of VLAN 1. • When created.0(5)XP should be upgraded to the current software release as described in the release notes. • You must be able to move your network management station to a switch port assigned to the same VLAN as the new management VLAN. • Only one management VLAN can be administratively active at a time. For information about the role management VLANs play in switch clusters.Chapter 8 Configuring VLANs Management VLANs Management VLANs Communication with the switch management interfaces is through the switch IP address. make sure you follow these guidelines: • The new management VLAN should not have an Hot Standby Router Protocol (HSRP) standby group configured on it. • Switches running Cisco IOS 12. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-4 78-6511-05 . see the “Management VLAN” section on page 5-11. the management VLAN can be deleted. ensure that the port through which you are connected to a switch is in the management VLAN.0(5)XP cannot change the management VLAN. the management VLAN is administratively down. Before changing the management VLAN on your switch network. The IP address is associated with the management VLAN. • Connectivity through the network must exist from the network management station to all switches involved in the management VLAN change. The management VLAN has the following characteristics: • It is created from CMS or through the CLI on static-access. If you are using SNMP or CMS to manage the switch. multi-VLAN. and dynamic-access and trunk ports. • Switches running a version of IOS software that is earlier than Cisco IOS 12. which by default is VLAN 1.

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-5 .text file and for which there have been no changes to the running configuration. All ports that have an active link at the time of this change become members of the new management VLAN.text file. If the cluster is configured with a management VLAN other than the default. the command switch changes the management VLAN for new switches when they are connected to the cluster. In this way. The command switch issues commands to change the management VLAN on the new switch to match the one in use by the cluster. its management VLAN is changed to the cluster management VLAN when it is first added to the cluster. the new switch can exchange CDP messages with the command switch and be proposed as a cluster candidate. it must be connected to a port that belongs to the cluster management VLAN. Note For the command switch to change the management VLAN on a new switch. the command switch automatically senses that the new switch has a different management VLAN and has not been configured. and there must be no config. there must have been no changes to the new switch configuration. Because the switch is new and unconfigured. Before a new switch can be added to a cluster. out-of-box switches that do not have a config. This automatic change of the VLAN only occurs for new.Chapter 8 Configuring VLANs Management VLANs Changing the Management VLAN for a New Switch If you add a new switch to an existing cluster and the cluster is using a management VLAN other than the default VLAN 1. For information about the role management VLANs play in switch clusters. see the “Management VLAN” section on page 5-11.

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-6 78-6511-05 . follow these steps to configure the management VLAN interface through a Telnet connection: Command Purpose Step 1 configure terminal Enter global configuration mode. Move the port through which you are connected to the switch to a port in the new management VLAN. Step 3 show running-config Verify the change. Beginning in privileged EXEC mode on the command switch. This ends your Telnet session. review the “Management VLANs” section on page 8-4.Chapter 8 Configuring VLANs Management VLANs Changing the Management VLAN Through a Telnet Connection Before you start. Step 2 cluster management-vlan vlanid Change the management VLAN for the cluster.

all ports are static-access ports assigned to VLAN 1. but or membership can be limited by configuring the allowed-VLAN list. VLAN Trunk Protocol (VTP) maintains VLAN configuration consistency by managing the addition. For more information. A dynamic-access port can belong to one VLAN and is dynamically assigned by a VLAN Membership Policy Server (VMPS). you can map the LAN emulation (LANE) client to a VLAN or bind one or more permanent virtual connections (PVCs) to a VLAN. Multi-VLAN A multi-VLAN port can belong to up to 250 VLANs (some models only support 64 VLANs) and is manually assigned.Chapter 8 Configuring VLANs Assigning VLAN Port Membership Modes Assigning VLAN Port Membership Modes You configure a port to belong to a VLAN by assigning a membership mode that determines the kind of traffic the port carries and the number of VLANs it can belong to. You can also IEEE 802. Table 8-2 lists the membership modes and characteristics. ATM.1Q) modify the pruning-eligible list to block flooded traffic to VLANs on trunk ports that are included in the list. VLAN traffic on the multi-VLAN port is not encapsulated. A trunk is a member of all VLANs in the VLAN database by default. The VMPS can be a Catalyst 5000 series switch but never a Catalyst 2900 XL or Catalyst 3500 XL switch. deletion. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-7 . By default. Trunk (ISL. and renaming of VLANs on a network-wide basis. Note Dynamic access By using the Asynchronous Transfer Mode (ATM) module CLI. refer to the Catalyst 2900 Series XL ATM Modules Installation and Configuration Guide. The VLAN ID is then displayed in the Assigned VLANs column of the VLAN Membership window. VTP exchanges VLAN configuration messages with other switches over trunk links. You cannot configure a multi-VLAN port when a trunk is configured on the switch. Table 8-2 Port Membership Modes Membership Mode VLAN Membership Characteristics Static-access A static-access port can belong to one VLAN and is manually assigned. An ATM port can only be a trunk port.

Some restrictions apply to multi-VLAN ports. see the “Avoiding Configuration Conflicts” section on page 9-2. VLAN Membership Combinations You can configure your switch ports in various VLAN membership combinations as listed in Table 8-3.Chapter 8 Configuring VLANs Assigning VLAN Port Membership Modes When a port belongs to a VLAN. you can assign a static-access port to a VLAN and set the VTP mode to transparent to disable VTP. For more information. Static-access and No multi-VLAN ports “Overlapping VLANs and Multi-VLAN Ports” section on page 8-11 You must connect the multi-VLAN port to a router or server. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-8 78-6511-05 . see the “Managing the MAC Address Tables” section on page 6-56. “Assigning Static-Access Ports to a VLAN” section on page 8-10 The switch automatically transitions to VTP transparent mode (VTP is disabled). Table 8-3 Port Mode VLAN Combinations VTP Required? Configuration Procedure Comments Static-access ports No “Assigning Static-Access Ports to a VLAN” section on page 8-10 If you do not want to use VTP to globally propagate the VLAN configuration information. the switch learns and manages the addresses associated with the port on a per-VLAN basis. No VTP configuration is required. For more information.

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-9 . or remove VLANs in the database as described in the “Configuring VLANs in the VTP Database” section on page 8-32 “Assigning Static-Access Ports to a VLAN” section on page 8-35 Some restrictions apply to trunk ports. “Configuring a Trunk You can define the allowed-VLAN Port” section on page 8-38 list. and configure the native VLAN for untagged traffic on the trunk port. change the pruning-eligible list. Dynamic-access and trunk ports Yes “Configuring Dynamic VLAN Membership” section on page 8-57 You must connect the dynamic-access port to an end station and not to another switch. For more information.Chapter 8 Configuring VLANs Assigning VLAN Port Membership Modes Table 8-3 VLAN Combinations (continued) Port Mode VTP Required? Configuration Procedure Comments Static-access and trunk ports Recommended “Configuring VTP Server Mode” section on page 8-21 You can configure at least one trunk port on the switch and make sure that this trunk port is connected to the trunk port of a second switch. You can change the VTP version on the switch and enable VTP pruning. see the “Trunks Interacting with Other Features” section on page 8-37. Add. and configure the native VLAN for untagged traffic on the trunk port. You can define the allowed-VLAN list. change the pruning-eligible list. modify. “Configuring a Trunk Port” section on page 8-38 so that the VMPS client can receive VTP information from the VMPS You can change the reconfirmation interval and the retry count on the VMPS client switch. “Configuring Dynamic Ports on VMPS Clients” section on page 8-58 Configure the VMPS and the client with the same VTP domain name.

Configuring a switch port for multi-VLAN mode causes VTP to transition to transparent mode. Step 2 interface interface Enter interface configuration mode. which disables VTP. all ports are static-access ports assigned to the management VLAN. VLAN 1. Step 4 switchport multi vlan vlan-list Assign the port to more than one VLAN. You can assign a static-access port to a VLAN without having VTP globally propagate VLAN configuration information (VTP is disabled). and enter the port to be added to the VLAN. Separate nonconsecutive VLAN IDs with a comma. use a hyphen to designate a range of IDs. Step 5 end Return to privileged EXEC mode. Step 3 switchport mode multi Enter the VLAN membership mode for multi-VLAN ports. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-10 78-6511-05 . Beginning in privileged EXEC mode.Chapter 8 Configuring VLANs Assigning Static-Access Ports to a VLAN Assigning Static-Access Ports to a VLAN By default. Step 6 show interface interface-id switchport Verify your entries. Configuring the switch for VTP transparent mode disables VTP. follow these steps to assign ports for multi-VLAN membership: Command Purpose Step 1 configure terminal Enter global configuration mode.

Multi-VLAN ports also respond to the STP messages generated by the different instances of STP in each VLAN. For the restrictions that apply to multi-VLAN ports. For example. Figure 8-2 Two VLANs Sharing a Port Connected to a Router VLAN 77 Cisco router VLAN 42 12516 Ports in static-access mode Port in multi-VLAN mode Caution To avoid unpredictable STP behavior and a loss of connectivity. Connectivity between VLANs is through the router connected to the multi-VLAN port. A multi-VLAN port performs normal switching functions in all its assigned VLANs. when a multi-VLAN port receives an unknown Media Access Control (MAC) address. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-11 . all the VLANs to which the port belongs learn the address. do not connect multi-VLAN ports to hubs or switches. Connect multi-VLAN ports to routers or servers.Chapter 8 Configuring VLANs Overlapping VLANs and Multi-VLAN Ports Overlapping VLANs and Multi-VLAN Ports A multi-VLAN port connected to a router can link two or more VLANs. Intra-VLAN traffic stays within the boundaries of the respective VLANs as shown in Figure 8-2. see the “Avoiding Configuration Conflicts” section on page 9-2.

Configuring a switch port for multi-VLAN mode causes VTP to transition to transparent mode. you must decide whether to use VTP in your network.Chapter 8 Configuring VLANs Using VTP Beginning in privileged EXEC mode. you cannot send information about VLANs to other switches. Without VTP. such as a Catalyst 2900 XL or Catalyst 3500 XL switch. incorrect VLAN-type specifications. Separate nonconsecutive VLAN IDs with a comma. Using VTP. Before you create VLANs. which disables VTP. VTP minimizes misconfigurations and configuration inconsistencies that can cause several problems. and have those changes automatically communicated to all the other switches in the network. Step 2 interface interface Enter interface configuration mode. use a hyphen to designate a range of IDs. and renaming of VLANs on a network-wide basis. and security violations. Step 3 switchport mode multi Enter the VLAN membership mode for multi-VLAN ports. such as duplicate VLAN names. Step 4 switchport multi vlan vlan-list Assign the port to more than one VLAN. and enter the port to be added to the VLAN. deletion. you can make configuration changes centrally on a single switch. follow these steps to assign ports for multi-VLAN membership: Command Purpose Step 1 configure terminal Enter global configuration mode. Step 5 end Return to privileged EXEC mode. Using VTP VTP is a Layer 2 messaging protocol that maintains VLAN configuration consistency by managing the addition. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-12 78-6511-05 . Step 6 show interface interface-id switchport Verify your entries.

and ATM LANE. The default VTP mode is server mode. IEEE 802.10. or SNMP. a Catalyst 2900 XL or Catalyst 3500 XL switch is in the 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. You make global VLAN configuration changes for the domain by using the CLI. the change is propagated to all switches in the VTP domain. see the “Domain Names” section on page 8-18. it inherits the domain name and configuration revision number. IEEE 802. The switch then ignores advertisements with a different domain name or an earlier configuration revision number.Chapter 8 Configuring VLANs Using VTP The VTP Domain A VTP domain (also called a VLAN management domain) consists of one switch or several interconnected switches under the same administrative responsibility. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-13 . Cluster Management software. If the switch receives a VTP advertisement over a trunk link. but VLAN information is not propagated over the network until a domain name is specified or learned. but the changes are not transmitted to other switches in the domain. VTP advertisements are sent over all trunk connections. If you configure a switch for VTP transparent mode. For domain name and password configuration guidelines. When you make a change to the VLAN configuration on a VTP server.1Q. A switch can be in only one VTP domain. By default. including Inter-Switch Link (ISL). and they affect only the individual switch. you can create and modify VLANs.

but you cannot create. VLAN configurations are saved in nonvolatile RAM. VTP transparent switches do not participate in VTP. change. VLAN configurations are saved in nonvolatile RAM. VTP server is the default mode. transparent switches do forward VTP advertisements that they receive from other switches. but they are not advertised to other switches. you can create. In VTP transparent mode. However. A VTP transparent switch does not advertise its VLAN configuration and does not synchronize its VLAN configuration based on received advertisements. and delete VLANs and specify other configuration parameters (such as VTP version) for the entire VTP domain. VTP client In this mode. a VTP client behaves like a VTP server. modify. Table 8-4 VTP Modes VTP Mode Description VTP server In this mode. 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.Chapter 8 Configuring VLANs Using VTP VTP Modes and Mode Transitions You can configure a supported switch to be in one of the VTP modes listed in Table 8-4. and delete VLANs on a switch in VTP transparent mode. or delete VLANs on a VTP client. VLAN configurations are saved in nonvolatile RAM. You can create. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-14 78-6511-05 . In VTP client mode. In VTP server mode. VTP transparent In this mode. modify.

VTP advertisements distribute the following global domain information in VTP advertisements: • VTP domain name • VTP configuration revision number • Update identity and update timestamp • MD5 digest Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-15 . Note Because trunk ports send and receive VTP advertisements. Neighboring switches receive these advertisements and update their VTP and VLAN configurations as necessary. Otherwise. VTP Advertisements Each switch in the VTP domain sends periodic global configuration advertisements from each trunk port to a reserved multicast address.Chapter 8 Configuring VLANs Using VTP Two configurations can cause a switch to automatically change its VTP mode: • When the network is configured with more than the maximum 250 VLANs (some models support a maximum of 64 VLANs). the switch cannot receive any VTP advertisements. The “VTP Configuration Guidelines” section on page 8-18 provides tips and caveats for configuring VTP. The switch then operates with the VLAN configuration that preceded the one that sent it into transparent mode. 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. • When a multi-VLAN port is configured on a supported switch in VTP server mode or client mode. the switch automatically changes from VTP server or client mode to VTP transparent mode. the switch automatically changes to transparent mode.

its information is accepted without consistency checks. see the “VLANs in the VTP Database” section on page 8-27. • Unrecognized Type-Length-Value (TLV) support—A VTP server or client propagates configuration changes to its other trunks. Consistency checks are not performed when new information is obtained from a VTP message or when information is read from nonvolatile RAM.Chapter 8 Configuring VLANs Using VTP VTP advertisements distribute the following VLAN information for each configured VLAN: • VLAN ID • VLAN name • VLAN type • VLAN state • Additional VLAN configuration information specific to the VLAN type VTP Version 2 VTP version 2 supports the following features not supported in version 1: • Token Ring support—VTP version 2 supports Token Ring LAN switching and VLANs (Token Ring Bridge Relay Function [TrBRF] and Token Ring Concentrator Relay Function [TrCRF]). For more information about Token Ring VLANs. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-16 78-6511-05 . or SNMP. • Version-Dependent Transparent Mode—In VTP version 1. Because only one domain is supported. • Consistency Checks—In VTP version 2. 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. The unrecognized TLV is saved in nonvolatile RAM when the switch is operating in VTP server mode. VTP version 2 forwards VTP messages in transparent mode without checking the version and domain name. If the digest on a received VTP message is correct. the Cluster Management software. even for TLVs it is not able to parse. VLAN consistency checks (such as VLAN names and values) are performed only when you enter new information through the CLI.

5. VTP pruning blocks unneeded flooded traffic to VLANs on trunk ports that are included in the pruning-eligible list. multicast. the flooding continues. and 6 because traffic for the Red VLAN has been pruned on the links indicated (port 5 on Switch 2 and port 4 on Switch 4). VLANs 2 through 1001 are pruning eligible on Catalyst 2900 XL and Catalyst 3500 XL trunk ports. Catalyst 2900 XL or Catalyst 3500 XL Switch 2 Red VLAN Port 5 Switch 6 Switch 3 Switch 1 30768 Port 1 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-17 . VTP pruning is also supported with VTP version 1 and version 2.Chapter 8 Configuring VLANs Using VTP VTP Pruning Pruning increases available bandwidth by restricting flooded traffic to those trunk links that the traffic must use to reach the destination devices. Only VLANs included in the pruning-eligible list can be pruned. Figure 8-3 Optimized Flooded Traffic with VTP Pruning Switch 4 Port 2 Flooded traffic is pruned. If the VLANs are configured as pruning-ineligible. a switch floods broadcast. By default. and unknown unicast traffic across all trunk links within a VTP domain even though receiving switches might discard them. Switch 5 Port 4 Flooded traffic is pruned. Figure 8-3 shows a switched network with VTP pruning enabled. Without VTP pruning. The broadcast traffic from Switch 1 is not forwarded to Switches 3.

and you do not need to configure a VTP domain name for them. Switches without a password or with the wrong password reject VTP advertisements. If you configure a VTP password for a domain. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-18 78-6511-05 . Switches in VTP transparent mode do not exchange VTP messages with other switches. you must always assign a domain name. it is impossible to make changes to the VLAN configuration of that domain.Chapter 8 Configuring VLANs Using VTP VTP Configuration Guidelines The following sections describe the guidelines you should follow when configuring the VTP domain name and password and the VTP version number. If you configure the domain. Therefore. Caution Do not configure a VTP domain if all switches are operating in VTP client mode. After the configuration. Passwords You can configure a password for the VTP domain. Domain Names When configuring VTP for the first time. the switch accepts the next VTP advertisement that uses the same password and domain name in the advertisement. All switches in the VTP domain must also be configured with the same domain name. the new switch learns the domain name only after the applicable password has been configured on the switch. If you are adding a new switch to an existing network that has VTP capability. Caution The domain does not function properly if you do not assign the same password to each switch in the domain. make sure you configure at least one switch in the VTP domain for VTP server mode. a Catalyst 2900 XL or Catalyst 3500 XL switch that is booted without a VTP configuration does not accept VTP advertisements until you configure it with the correct password. but it is not required. All domain switches must share the same password.

you must configure the switch with the correct domain name. and VTP does not propagate the VLAN configuration to other switches. it will not exchange VTP information with switches with version 2 enabled. When you enable version 2 on a switch. such as Cisco IOS Release 11. all of the version-2-capable switches in the domain enable version 2.2(8)SA3. and VTP enters transparent mode. disable VTP version 2. If you want the switch to propagate VLAN configuration information to other switches and to learn the VLANs enabled on the network. • 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. VTP Version Follow these guidelines when deciding which VTP version to implement: • All switches in a VTP domain must run the same VTP version. you must enable VTP version 2 for Token Ring VLAN switching to function properly. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-19 . ports that belong to a VLAN retain their VLAN membership. • Do not enable VTP version 2 on a switch unless all of the switches in the same VTP domain are version-2-capable.Chapter 8 Configuring VLANs Using VTP Upgrading from Previous Software Releases When you upgrade from a software version that supports VLANs but does not support VTP. to a version that does support VTP. the domain password. • Enabling or disabling VTP pruning on a VTP server enables or disables VTP pruning for the entire VTP domain. • If there are Token Ring networks in your environment (TrBRF and TrCRF). To run Token Ring and Token Ring-Net. and change the VTP mode to VTP server. Version 2 is disabled by default. If there is a version 1-only switch. The domain name becomes UPGRADE.

If you are configuring VTP on a cluster member switch to a VLAN. and you enter privileged EXEC mode. see the “How VLAN Trunks Work” section on page 8-36. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-20 78-6511-05 . When you enter the exit command in VLAN database mode. Table 8-5 VTP Default Configuration Feature Default Value VTP domain name Null. you must configure a trunk port so that the switch can send and receive VTP advertisements. Configuring VTP You can configure VTP through the CLI by entering commands in the VLAN database command mode. VTP mode Server. VTP version 2 enable state Version 2 is disabled. After you configure VTP. For more information on how to use this command. refer to the Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference. VTP password None. For more information. it applies all the commands that you entered. VTP pruning Disabled. VTP messages are sent to other switches in the VTP domain.Chapter 8 Configuring VLANs Using VTP Default VTP Configuration Table 8-5 shows the default VTP configuration. Note The Cisco IOS end and Ctrl-Z commands are not supported in VLAN database mode. first log in to the member switch by using the privileged EXEC rcommand command.

follow these steps to configure the switch for VTP server mode: Command Purpose Step 1 vlan database Enter VLAN database mode. the VTP domain does not function properly if you do not assign the same password to each switch in the domain.Chapter 8 Configuring VLANs Using VTP Configuring VTP Server Mode When a switch is in VTP server mode. you can change the VLAN configuration and have it propagated throughout the network. Beginning in privileged EXEC mode. In the display. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-21 . Step 4 vtp server Configure the switch for VTP server mode (the default). check the VTP Operating Mode and the VTP Domain Name fields. If you configure a VTP password. Step 2 vtp domain domain-name Configure a VTP administrative-domain name. Step 3 vtp password password-value (Optional) Set a password for the VTP domain. The name can be from 1 to 32 characters. The password can be from 8 to 64 characters. All switches operating in VTP server or client mode under the same administrative responsibility must be configured with the same domain name. Step 5 exit Return to privileged EXEC mode. Step 6 show vtp status Verify the VTP configuration.

Step 6 show vtp status Verify the VTP configuration. and return to privileged EXEC mode. All switches operating in VTP server or client mode under the same administrative responsibility must be configured with the same domain name. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-22 78-6511-05 . In the display. propagate it throughout the administrative domain. Step 3 vtp domain domain-name Configure a VTP administrative-domain name. If you do so. make sure you configure at least one switch as the VTP server. Step 2 vtp client Configure the switch for VTP client mode. Therefore. you cannot change its VLAN configuration. Caution Do not configure a VTP domain name if all switches are operating in VTP client mode. The name can be from 1 to 32 characters. The default setting is VTP server. it is impossible to make changes to the VLAN configuration of that domain. Step 4 vtp password password-value (Optional) Set a password for the VTP domain. The client switch receives VTP updates from a VTP server in the VTP domain and then modifies its configuration accordingly. check the VTP Operating Mode field. follow these steps to configure the switch for VTP client mode: Command Purpose Step 1 vlan database Enter VLAN database mode. Step 5 exit Update the VLAN database. The password can be from 8 to 64 characters. the VTP domain does not function properly if you do not assign the same password to each switch in the domain. Beginning in privileged EXEC mode.Chapter 8 Configuring VLANs Using VTP Configuring VTP Client Mode When a switch is in VTP client mode. If you configure a VTP password.

Step 2 vtp transparent Configure the switch for VTP transparent mode. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-23 . Step 3 exit Return to privileged EXEC mode. you disable VTP on the switch. follow these steps to configure the switch for VTP transparent mode: Command Purpose Step 1 vlan database Enter VLAN database mode. The default setting is VTP server. In the display. Step 4 show vtp status Verify the VTP configuration. However. The switch then does not send VTP updates and does not act on VTP updates received from other switches. Beginning in privileged EXEC mode. This step disables VTP on the switch.Chapter 8 Configuring VLANs Using VTP Disabling VTP (VTP Transparent Mode) When you configure the switch for VTP transparent mode. check the VTP Operating Mode field. a VTP transparent switch does forward received VTP advertisements on all of its trunk links.

see the “VTP Version” section on page 8-19. every VTP version 2-capable switch in the VTP domain enables version 2. For more information on VTP version configuration guidelines. propagate it throughout the administrative domain. Step 3 exit Update the VLAN database.Chapter 8 Configuring VLANs Using VTP Enabling VTP Version 2 VTP version 2 is disabled by default on VTP version 2-capable switches. check the VTP V2 Mode field. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-24 78-6511-05 . Every switch in the VTP domain must use the same VTP version. Caution VTP version 1 and VTP version 2 are not interoperable on switches in the same VTP domain. Step 4 show vtp status Verify that VTP version 2 is enabled. follow these steps to enable VTP version 2: Command Purpose Step 1 vlan database Enter VLAN configuration mode. VTP version 2 is disabled by default on VTP version 2-capable switches. Step 2 vtp v2-mode Enable VTP version 2 on the switch. Beginning in privileged EXEC mode. Do not enable VTP version 2 unless every switch in the VTP domain supports version 2. you must enable VTP version 2 for Token Ring VLAN switching to function properly. When you enable VTP version 2 on a switch. In the display. and return to privileged EXEC mode. Note In a Token Ring environment.

see the “Changing the Pruning-Eligible List” section on page 8-42. it is enabled for the entire VTP domain. Step 2 no vtp v2-mode Disable VTP version 2. 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. Step 4 show vtp status Verify that VTP version 2 is disabled. VLANs 2 through 1001 are pruning eligible on Catalyst 2900 XL and Catalyst 3500 XL trunk ports. Pruning is supported with VTP version 1 and version 2. By default. propagate it throughout the administrative domain. In the display. check the VTP V2 Mode field. You enable VTP pruning on a switch in VTP server mode. Only VLANs included in the pruning-eligible list can be pruned. Step 3 exit Update the VLAN database. If you enable pruning on the VTP server. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-25 . and return to privileged EXEC mode. For information. follow these steps to disable VTP version 2: Command Purpose Step 1 vlan database Enter VLAN configuration mode.Chapter 8 Configuring VLANs Using VTP Disabling VTP Version 2 Beginning in privileged EXEC mode.

follow these steps to enable VTP pruning: Command Purpose Step 1 vlan database Enter VLAN configuration mode. pruning is disabled. Step 4 show vtp status Verify your entries. the current VTP revision. Beginning in privileged EXEC mode. By default. check the VTP Pruning Mode field. Step 2 vtp pruning Enable pruning in the VTP administrative domain. In the display. Step 2 show vtp counters Display counters about VTP messages being sent and received. propagate it throughout the administrative domain. You only need to enable pruning on one switch in VTP server mode. and the number of VLANs. Monitoring VTP You monitor VTP by displaying its configuration information: the domain name. follow these steps to monitor VTP activity: Command Purpose Step 1 show vtp status Display the VTP switch configuration information. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-26 78-6511-05 .Chapter 8 Configuring VLANs Using VTP Beginning in privileged EXEC mode. Step 3 exit Update the VLAN database. You can also display statistics about the advertisements sent and received by the switch. and return to privileged EXEC mode.

Switches running this IOS release advertise information about the following Token Ring VLANs when running VTP version 2: • Token Ring TrBRF VLANs • Token Ring TrCRF VLANs For more information on configuring Token Ring VLANs. refer to the Catalyst 5000 Series Software Configuration Guide.Chapter 8 Configuring VLANs VLANs in the VTP Database VLANs in the VTP Database You can set the following parameters when you add a new VLAN to or modify an existing VLAN in the VTP database: • VLAN ID • VLAN name • VLAN type (Ethernet. a remote device such as a Catalyst 5000 series switch with Token Ring connections could be managed from one of the supported switches. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-27 . 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 • STP type for TrCRF VLANs • VLAN number to use when translating from one VLAN type to another The “Default VLAN Configuration” section on page 8-28 lists the default values and possible ranges for each VLAN media type. FDDI network entity title [NET]. Fiber Distributed Data Interface [FDDI]. TrBRF or TrCRF. Token Ring VLANs Although the Catalyst 2900 XL and Catalyst 3500 XL switches do not support Token Ring connections.

or TrBRF traffic. For information on configuring VTP.Chapter 8 Configuring VLANs VLANs in the VTP Database VLAN Configuration Guidelines Follow these guidelines when creating and modifying VLANs in your network: • A maximum of 250 VLANs can be active on supported switches. Note Catalyst 2900 XL and Catalyst 3500 XL switches support Ethernet interfaces exclusively. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-28 78-6511-05 . but it does propagate the VLAN configuration through VTP. but some models only support 64 VLANs. Default VLAN Configuration Table 8-6 through Table 8-10 shows the default configuration for the different VLAN media types. see the “Configuring VTP” section on page 8-20. Because FDDI and Token Ring VLANs are not locally supported. FDDI-Net. 4 of the active VLANs (1002 to 1005) are reserved for Token Ring and FDDI. • Switches running this IOS release do not support Token Ring or FDDI media. the switch must be in VTP server mode or VTP transparent mode. you configure FDDI and Token Ring media-specific characteristics only for VTP global advertisements to other switches. If VTP reports that there are 254 active VLANs. • Before you can create a VLAN. TrCRF. The switch does not forward FDDI.

suspend Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-29 . where xxxx is the VLAN ID No range 802.10 SAID 100000+VLAN ID 1–4294967294 MTU size 1500 1500–18190 Ring number None 1–4095 Parent VLAN 0 0–1005 Translational bridge 1 0 0–1005 Translational bridge 2 0 0–1005 VLAN state active active.Chapter 8 Configuring VLANs VLANs in the VTP Database Table 8-6 Ethernet VLAN Defaults and Ranges Parameter Default Range VLAN ID 1 1–1005 VLAN name VLANxxxx.10 SAID 100000+VLAN ID 1–4294967294 MTU size 1500 1500–18190 Translational bridge 1 0 0–1005 Translational bridge 2 0 0–1005 VLAN state active active. suspend Table 8-7 FDDI VLAN Defaults and Ranges Parameter Default Range VLAN ID 1002 1–1005 VLAN name VLANxxxx. where xxxx is the VLAN ID No range 802.

VTPv2 4472 1500–18190 Bridge number VTPv1 0. where xxxx is the VLAN ID No range 802.Chapter 8 Configuring VLANs VLANs in the VTP Database Table 8-8 FDDI-Net VLAN Defaults and Ranges Parameter Default Range VLAN ID 1004 1–1005 VLAN name VLANxxxx. where xxxx is the VLAN ID No range 802. suspend Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-30 78-6511-05 .10 SAID 100000+VLAN ID 1–4294967294 MTU size 1500 1500–18190 Bridge number 0 0–15 STP type ieee auto. ieee Translational bridge 1 0 0–1005 Translational bridge 2 0 0–1005 VLAN state active active. ieee Translational bridge 1 0 0–1005 Translational bridge 2 0 0–1005 VLAN state active active. VTPv2 user-specified 0–15 STP type ibm auto.10 SAID 100000+VLAN ID 1–4294967294 MTU size VTPv1 1500. ibm. suspend Table 8-9 Token Ring (TrBRF) VLAN Defaults and Ranges Parameter Default Range VLAN ID 1005 1–1005 VLAN name VLANxxxx. ibm.

Chapter 8 Configuring VLANs VLANs in the VTP Database Table 8-10 Token Ring (TrCRF) VLAN Defaults and Ranges Parameter Default Range VLAN ID 1003 1–1005 VLAN name VLANxxxx. VTPv2 user-specified 0–1005 MTU size VTPv1 default 1500. VTPv2 user-specified 1–4095 Parent VLAN VTPv1 default 0. VTPv2 default 4472 1500–18190 Translational bridge 1 0 0–1005 Translational bridge 2 0 0–1005 VLAN state active active.10 SAID 100000+VLAN ID 1–4294967294 Ring Number VTPv1 default 0. where xxxx is the VLAN ID No range 802. suspend Bridge mode srb srb. enable Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-31 . srt ARE max hops 7 0–13 STE max hops 7 0–13 Backup CRF disabled disable.

dat file is stored in nonvolatile memory. use the VLAN database commands described in the Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference. refer to the Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference.dat file. and delete VLANs are written to the file vlan. change. change. For complete information on the commands and parameters that control VLAN configuration. but you cannot return to an earlier version of Cisco IOS after you upgrade to this release. Caution You can cause inconsistency in the VLAN database if you attempt to manually delete the vlan.dat. In VTP server or transparent mode. The vlan. If you want to modify the VLAN configuration or VTP. The results of these commands are written to the running-configuration file. You use the interface configuration command mode to define the port membership mode and add and remove ports from VLANs.dat file is upgraded automatically. The vlan.Chapter 8 Configuring VLANs VLANs in the VTP Database Configuring VLANs in the VTP Database You use the CLI vlan database VLAN database command to add. Note VLANs can be configured to support a number of parameters that are not discussed in detail in this section. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-32 78-6511-05 . and delete VLANs. and you can display the file by entering the privileged EXEC show running-config command. commands to add. and you can display them by entering the privileged EXEC show vlan command.

and return to privileged EXEC mode. Step 3 exit Update the VLAN database.Chapter 8 Configuring VLANs VLANs in the VTP Database Adding a VLAN Each VLAN has a unique. 4-digit ID that can be a number from 1 to 1001. If you do not specify the VLAN media type. For the list of default parameters that are assigned when you add a VLAN. follow these steps to add an Ethernet VLAN: Command Purpose Step 1 vlan database Enter VLAN database mode. VLAN0004 could be a default VLAN name. Step 4 show vlan name vlan-name Verify the VLAN configuration. see the “Default VLAN Configuration” section on page 8-28. For example. the VLAN is an Ethernet VLAN. If no name is entered for the VLAN. Beginning in privileged EXEC mode. assign a number and name to the VLAN. If you do not specify the VLAN media type. To add a VLAN to the VLAN database. the VLAN is an Ethernet VLAN. Step 2 vlan vlan-id name vlan-name Add an Ethernet VLAN by assigning a number to it. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-33 . the default is to append the vlan-id to the word VLAN. propagate it throughout the administrative domain.

Step 4 show vlan vlan-id Verify the VLAN configuration.Chapter 8 Configuring VLANs VLANs in the VTP Database Modifying a VLAN Beginning in privileged EXEC mode. the VLAN is deleted only on that specific switch. and return to privileged EXEC mode. Deleting a VLAN from the Database When you delete a VLAN from a switch that is in VTP server mode. any ports assigned to that VLAN become inactive. Step 3 exit Update the VLAN database. propagate it throughout the administrative domain. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-34 78-6511-05 . They remain associated with the VLAN (and thus inactive) until you assign them to a new VLAN. When you delete a VLAN from a switch that is in VTP transparent mode. and change the MTU size. the VLAN is removed from all switches in the VTP domain. Step 2 vlan vlan-id mtu mtu-size Identify the VLAN. You cannot delete the default VLANs for the different media types: Ethernet VLAN 1 and FDDI or Token Ring VLANs 1002 to 1005. follow these steps to modify an Ethernet VLAN: Command Purpose Step 1 vlan database Enter VLAN configuration mode. Caution When you delete a VLAN.

If you are assigning a port on a cluster member switch to a VLAN. Step 2 interface interface Enter interface configuration mode. follow these steps to assign a port to a VLAN in the VTP database: Command Purpose Step 1 configure terminal Enter global configuration mode. check the Operation Mode. and the Priority for Untagged Frames fields. In the display. refer to the Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference. follow these steps to delete a VLAN on the switch: Command Purpose Step 1 vlan database Enter VLAN configuration mode.Chapter 8 Configuring VLANs VLANs in the VTP Database Beginning in privileged EXEC mode. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-35 . Step 5 exit Return to privileged EXEC mode. Beginning in privileged EXEC mode. first log in to the member switch by using the privileged EXEC rcommand command. and define the interface to be added to the VLAN. and return to privileged EXEC mode. Step 2 no vlan vlan-id Remove the VLAN by using the VLAN ID. Step 6 show interface interface-id switchport Verify the VLAN configuration. Step 3 switchport mode access Define the VLAN membership mode for this port. which is the default management VLAN. Access Mode VLAN. Step 4 show vlan brief Verify the VLAN removal. Assigning Static-Access Ports to a VLAN By default. all ports are static-access ports assigned to VLAN 1. Step 4 switchport access vlan 3 Assign the port to the VLAN. propagate it throughout the administrative domain. For more information on how to use this command. Step 3 exit Update the VLAN database.

or industry-standard IEEE 802. Trunks carry the traffic of multiple VLANs and can extend VLANs across an entire network.1Q to carry traffic for multiple VLANs over a single link. Figure 8-4 shows a network of switches that are connected by ISL trunks. 100BASE-T and Gigabit Ethernet trunks use Cisco Inter-Switch Link (ISL).Chapter 8 Configuring VLANs How VLAN Trunks Work How VLAN Trunks Work A trunk is a point-to-point link that transmits and receives traffic between switches or between switches and routers. Figure 8-4 Catalyst 2900 XL and Catalyst 3500 XL Switches in an ISL Trunking Environment Catalyst 5000 series switch ISL trunk Catalyst 2900 XL switch ISL trunk Catalyst 3500 XL switch VLAN1 ISL trunk Catalyst 2900 XL switch VLAN3 Catalyst 3500 XL switch VLAN2 VLAN1 VLAN3 15929 VLAN2 ISL trunk Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-36 78-6511-05 . the default protocol.

1Q trunk is the same on both ends of the trunk link. We recommend that you leave STP enabled on the native VLAN of an 802.1Q.1Q trunk without disabling STP on every VLAN in the network can potentially cause STP loops. IEEE 802. Trunks Interacting with Other Features ISL. Network port When configured as a network port. The following restrictions apply when using 802. If the native VLAN on one end of the trunk is different from the native VLAN on the other end.1Q trunks impose some limitations on the trunking strategy for a network. a trunk port serves as the network port for all VLANs associated with the port.1Q trunk or disable STP on every VLAN in the network. Make sure your network is loop-free before disabling STP. and ATM trunking interacts with other switch features as described in Table 8-11. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-37 . Secure ports A trunk port cannot be a secure port.1Q Configuration Considerations IEEE 802. A static-access port can monitor the traffic of its VLAN on a trunk port.1Q trunks: • Make sure the native VLAN for an 802. A network port receives all unknown unicast traffic on a VLAN. • Disabling STP on the native VLAN of an 802. spanning-tree loops might result.Chapter 8 Configuring VLANs How VLAN Trunks Work IEEE 802. Table 8-11 Trunks Interacting with Other Features Switch Feature Trunk Port Interaction Port monitoring A trunk port cannot be a monitor port.

For information on trunk port interactions with other features. see the “Trunks Interacting with Other Features” section on page 8-37. • Trunk status: if one port in a port group ceases to be a trunk. • STP path cost for each VLAN. 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. ATM ports are always trunk ports but cannot be part of an EtherChannel port group. unknown unicast packets cannot be blocked. Otherwise. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-38 78-6511-05 . When a group is first created. Note Because trunk ports send and receive VTP advertisements. all ports follow the parameters set for the first port to be added to the group. • STP port priority for each VLAN. if the trunk port is acting as a network port. Port grouping ISL and 802. but all trunks in the group must have the same configuration. the switch propagates the setting you entered to all ports in the group: • Allowed-VLAN list.Chapter 8 Configuring VLANs How VLAN Trunks Work Table 8-11 Trunks Interacting with Other Features (continued) Switch Feature Trunk Port Interaction Blocking unicast The port block interface configuration command can be and multicast used to block the forwarding of unknown unicast and packets on a trunk multicast packets to VLANs on a trunk. • STP Port Fast setting. all ports cease to be trunks. However. the switch cannot receive any VTP advertisements. If you change the configuration of one of the following parameters. Configuring a Trunk Port You cannot have multi-VLAN and trunk ports configured on the same switch.1Q trunks can be grouped into EtherChannel port groups.

Step 6 show interface interface-id switchport Verify your entries. Step 3 switchport mode trunk Configure the port as a VLAN trunk. This software release does not support trunk negotiation through the Dynamic Trunk Protocol (DTP). copy running-config startup-config Save the configuration. check the Operational Mode and the Operational Trunking Encapsulation fields.1Q trunk port: Command Purpose Step 1 configure terminal Enter global configuration mode.Chapter 8 Configuring VLANs How VLAN Trunks Work Beginning in privileged EXEC mode. formerly known as Dynamic ISL (DISL). If you are connecting a trunk port to a Catalyst 5000 switch or other DTP device.1Q encapsulation. use the non-negotiate option on the DTP-capable device so that the switch port does not generate DTP frames. Step 5 end Return to privileged EXEC mode. In the display. Step 2 interface interface_id Enter the interface configuration mode and the port to be configured for trunking. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-39 . Step 7 Note You must configure each end of the link with the same encapsulation type. follow these steps to configure a port as an ISL or 802. Step 4 switchport trunk encapsulation {isl | dot1q} Configure the port to support ISL or 802.

and if the VLAN is in the allowed list for the port. you can remove VLANs from the allowed list. preventing traffic from those VLANs from passing over the trunk. if VTP knows of the VLAN. a trunk port sends to and receives traffic from all VLANs in the VLAN database. 1 to 1005. Step 3 no switchport mode Return the port to its default static-access mode.Chapter 8 Configuring VLANs How VLAN Trunks Work Disabling a Trunk Port You can disable trunking on a port by returning it to its default static-access mode. When VTP detects a newly enabled VLAN and the VLAN is in the allowed list for a trunk port. When VTP detects a new VLAN and the VLAN is not in the allowed list for a trunk port. Step 4 end Return to privileged EXEC. All VLANs. Step 5 show interface interface-id switchport Verify your entries. To restrict the traffic a trunk carries. Beginning in privileged EXEC mode. the trunk port automatically becomes a member of the enabled VLAN. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-40 78-6511-05 . However. use the remove vlan-list parameter to remove specific VLANs from the allowed list. are allowed on each trunk. A trunk port can become a member of a VLAN if the VLAN is enabled. the trunk port does not become a member of the new VLAN. follow these steps to disable trunking on a port: Command Purpose Step 1 configure terminal Enter global configuration mode. Step 2 interface interface_id Enter the interface configuration mode and the port to be added to the VLAN. Defining the Allowed VLANs on a Trunk By default. In the display. check the Negotiation of Trunking field.

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-41 . Step 2 interface interface_id Enter interface configuration mode and the port to be added to the VLAN. Step 4 switchport trunk allowed vlan Define the VLANs that are not allowed to transmit and remove vlan-list receive on the port. Step 7 copy running-config startup-config Save the configuration. Step 3 switchport mode trunk Configure VLAN membership mode for trunks. use a hyphen to designate a range of IDs. follow these steps to modify the allowed list of a ISL or 802. Step 5 end Return to privileged EXEC. The vlan-list parameter is a range of VLAN IDs Separate nonconsecutive VLAN IDs with a comma and no spaces. Valid IDs are from 2 to 1001.Chapter 8 Configuring VLANs How VLAN Trunks Work Beginning in privileged EXEC mode. Step 6 show interface interface-id switchport allowed-vlan Verify your entries.1Q trunk: Command Purpose Step 1 configure terminal Enter global configuration mode.

Beginning in privileged EXEC mode. Step 2 interface interface-id Enter interface configuration mode.Chapter 8 Configuring VLANs How VLAN Trunks Work Changing the Pruning-Eligible List The pruning-eligible list applies only to trunk ports. Each trunk port has its own eligibility list. Separate nonconsecutive VLAN IDs with a comma and no spaces. Step 5 show interface interface-id switchport Verify your settings. 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. The “Enabling VTP Pruning” section on page 8-25 describes how to enable VTP pruning. VLANs that are pruning-ineligible receive flooded traffic. and select the trunk port for which VLANs should be pruned. VTP Pruning must be enabled for the following procedure to take effect. Valid IDs are from 2 to 1001. Step 4 exit Return to privileged EXEC mode. use a hyphen to designate a range of IDs. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-42 78-6511-05 . Step 3 switchport trunk pruning vlan Enter the VLANs to be removed from the pruning-eligible remove vlan-id list.

the switch forwards untagged traffic with the native VLAN configured for the port.1Q tagging can receive both tagged and untagged traffic. If a packet has a VLAN ID the same as the outgoing port native VLAN ID. Beginning in privileged EXEC mode. The native VLAN is VLAN 1 by default. the switch transmits the packet with a tag.1Q trunk.Chapter 8 Configuring VLANs How VLAN Trunks Work Configuring the Native VLAN for Untagged Traffic A trunk port configured with 802. the packet is transmitted untagged.1Q trunk: Command Purpose Step 1 configure terminal Enter global configuration mode. For information about 802. By default. otherwise. follow these steps to configure the native VLAN on an 802.1Q configuration issues. Note The native VLAN can be assigned any VLAN ID. Step 4 show interface interface-id switchport Verify your settings. see the “IEEE 802.1Q Configuration Considerations” section on page 8-37. Step 3 switchport trunk native vlan vlan-id Configure the VLAN that is sending and receiving untagged traffic on the trunk port. Valid IDs are from 1 to 1001. and define the interface that is configured as the 802. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-43 . Step 2 interface interface-id Enter interface configuration mode. and it is not dependent on the management VLAN.

For native frames. the priority value from the header frame is used. the default priority of the input port is used. How Class of Service Works Before you set up 802. routers.1p Class of Service Configuring 802. VLANs that are assigned on trunk or access ports without identification or a tag are called native or untagged frames. or end stations. refer to the Catalyst 6000 documentation.1Q frames with tag information.1p CoS on a Catalyst 2900 XL or Catalyst 3500 XL switch that operates with the Catalyst 6000 family of switches.1p Class of Service The Catalyst 2900 XL and Catalyst 3500 XL switches provide quality of service (QoS)-based IEEE 802. There are differences in the 802. and they should be understood to ensure compatibility. the tag is removed before the frame is transmitted to the target end station. QoS classifies frames by assigning priority-indexed CoS values to them and gives preference to higher-priority traffic such as telephone calls. Based on rules you define. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-44 78-6511-05 . a unique identifier (the tag) is inserted in each frame header before it is forwarded. QoS uses classification and scheduling to transmit network traffic from the switch in a predictable manner. For ISL or IEEE 802.1p class of service (CoS) values. Port Priority Frames received from users in the administratively-defined VLANs are classified or tagged for transmission to other devices. The tag is examined and understood by each device before any broadcasts or transmissions to other switches.1p implementation.Chapter 8 Configuring VLANs Configuring 802. When the frame reaches the last switch or router.

Chapter 8 Configuring VLANs Configuring 802. 1. Catalyst 2900 XL switches with 4 MB of DRAM and the WS-X2914-XL and the WS-X2922-XL modules only have one transmit queue and do not support QoS. depending on the frame tag or the port information. Frames with a priority value of 4 through 7 are sent to a high-priority queue.1p user priority) Frames with a priority value of 4 through 7 are sent to a high-priority queue. When an untagged frame arrives. Catalyst 3500 XL switches.1p user priority) Frames with a priority value of 0 through 3 are sent to a normal-priority queue. Frames with a priority value of 0 through 3 are Catalyst 2900 XL Ethernet sent to a normal-priority queue. Frames in the normal-priority queue are forwarded only after frames in the high-priority queue are forwarded. A tagged frame continues to use its assigned CoS value when it passes through the ingress port. it is assigned the value of the port as its port default priority. CoS configures each transmit port (the egress port) with a normal-priority transmit queue and a high-priority transmit queue. Gigabit Ethernet modules (802. Table 8-12 shows the two categories of switch transmit queues. Table 8-12 Transmit Queue Information Transmit Queue Category1 Transmit Queues Catalyst 2900 XL switches. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-45 .1p Class of Service Port Scheduling Each port on the switch has a single receive queue buffer (the ingress port) for incoming traffic. modules (802. You assign this value by using the CLI or CMS software.

Step 4 end Return to privileged EXEC mode. To avoid loops. you divide the traffic between the links according to which VLAN the traffic belongs. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-46 78-6511-05 . If you assign a priority level from 0 to 3. see the “Configuring STP” section on page 6-24. Step 5 show interface interface-id switchport Verify your entries. In the display. STP normally blocks all but one parallel link between switches. frames are forwarded to the normal priority queue of the output port.Chapter 8 Configuring VLANs Load Sharing Using STP Configuring the CoS Port Priorities Beginning in privileged EXEC mode. If you assign a priority level from 4 to 7. each load-sharing link can be connected to the same switch or to two different switches. For more information about STP. frames are forwarded to the high-priority queue of the output port. Step 2 interface interface Enter the interface to be configured. Step 3 switchport priority default default-priority-id Set the port priority on the interface. Load Sharing Using STP Load sharing divides the bandwidth supplied by parallel trunks connecting switches. For load sharing using STP port priorities. check the Priority for Untagged Frames field. both load-sharing links must be connected to the same switch. You configure load sharing on trunk ports by using STP port priorities or STP path costs. With load sharing. follow these steps to set the port priority for untagged (native) Ethernet frames: Command Purpose Step 1 configure terminal Enter global configuration mode. For load sharing using STP path costs.

Chapter 8 Configuring VLANs Load Sharing Using STP Load Sharing Using STP Port Priorities When two ports on the same switch form a loop. In this example. If the active trunk fails. • VLANs 3 through 6 retain the default port priority of 128 on trunk 1. Figure 8-5 shows two trunks connecting supported switches. • VLANs 8 through 10 retain the default port priority of 128 on trunk 2. Figure 8-5 Load Sharing by Using STP Port Priorities Switch 1 Switch 2 15932 Trunk 2 VLANs 3-6 (priority 10) VLANs 8-10 (priority 128) Trunk 1 VLANs 8-10 (priority 10) VLANs 3-6 (priority 128) Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-47 . The trunk port with the higher priority (lower values) for a VLAN is forwarding traffic for that VLAN. • VLANs 3 through 6 are assigned a port priority of 10 on trunk 2. the trunk with the lower priority takes over and carries the traffic for all of the VLANs. and trunk 2 carries traffic for VLANs 3 through 6. trunk 1 carries traffic for VLANs 8 through 10. One trunk port transmits or receives all traffic for the VLAN. No duplication of traffic occurs over any trunk port. 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 lower priority (higher values) for the same VLAN remains in a blocking state for that VLAN. the STP port priority setting determines which port is enabled and which port is in standby mode. In this way. the switches are configured as follows: • VLANs 8 through 10 are assigned a port priority of 10 on trunk 1.

Step 11 show interface fa0/1 switchport Verify the VLAN configuration. Step 9 switchport mode trunk Configure the port as a trunk port. Step 15 configure terminal Enter global configuration mode on Switch 1. Step 6 show vlan Verify that the VLANs exist in the database on Switch 1. Verify the Switch 2 has learned the VLAN configuration. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-48 78-6511-05 . Step 2 vtp domain domain-name Configure a VTP administrative domain. Step 4 exit Return to privileged EXEC mode. VTP passes the VTP and VLAN information to Switch 2. Step 7 configure terminal Enter global configuration mode. The domain name can be from 1 to 32 characters. The trunk defaults to ISL trunking. Step 3 vtp server Configure Switch 1 as the VTP server. check the VTP Operating Mode and the VTP Domain Name fields. follow these steps to configure the network shown in Figure 8-5: Command Purpose Step 1 vlan database On Switch 1. Step 12 Repeat Steps 7 through 11 on Switch 1 for interface Fa0/2. Step 8 interface fa0/1 Enter interface configuration mode. and define Fa0/1 as the interface to be configured as a trunk.Chapter 8 Configuring VLANs Load Sharing Using STP Configuring STP Port Priorities and Load Sharing Beginning in privileged EXEC mode. Step 13 Repeat Steps 7 through 11 on Switch 2 to configure the trunk ports on interface Fa0/1 and Fa0/2. Step 10 end Return to privileged EXEC mode. Step 5 show vtp status Verify the VTP configuration on both Switch 1 and Switch 2. Step 14 show vlan When the trunk links come up. enter VLAN configuration mode. In the display.

Step 22 show running-config Verify your entries. and define the interface to set the STP port priority. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-49 .Chapter 8 Configuring VLANs Load Sharing Using STP Command Purpose Step 16 interface fa0/1 Enter interface configuration mode. Step 20 spanning-tree vlan 3 4 5 6 port Assign the port priority of 10 for VLANs 3. Step 19 interface fa0/2 Enter interface configuration mode. Step 18 end Return to global configuration mode. and 6. 5. priority 10 Step 21 exit Return to privileged EXEC mode. and define the interface to set the STP port priority. and 10. 4. Step 17 spanning-tree vlan 8 9 10 port-priority 10 Assign the port priority of 10 for VLANs 8. 9.

The path costs for the VLANs are assigned as follows: • VLANs 2 through 4 are assigned a path cost of 30 on trunk port 1. • VLANs 2 through 4 retain the default 100BASE-T path cost on trunk port 2 of 19. The VLANs keep the traffic separate. • VLANs 8 through 10 retain the default 100BASE-T path cost on trunk port 1 of 19. In Figure 8-6. • VLANs 8 through 10 are assigned a path cost of 30 on trunk port 2. Figure 8-6 Load-Sharing Trunks with Traffic Distributed by Path Cost Switch 1 Trunk port 2 VLANs 8-10 (path cost 30) VLANs 2-4 (path cost 19) 16591 Trunk port 1 VLANs 2-4 (path cost 30) VLANs 8-10 (path cost 19) Switch 2 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-50 78-6511-05 . because no loops exist. and redundancy is maintained in the event of a lost link. STP does not disable the ports.Chapter 8 Configuring VLANs Load Sharing Using STP 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. trunk ports 1 and 2 are 100BASE-T ports.

and define Fa0/1 as the interface to be configured as a trunk. Step 5 Step 6 Repeat Steps 2 through 4 on Switch 1 interface Fa0/2. and set the spanning-tree path cost to 30 for VLANs 8. Step 9 interface fa0/1 Enter interface configuration mode. The trunk defaults to ISL trunking. verify that the path costs are set correctly for interface Fa0/1 and Fa0/2. In the display. Step 14 show running-config Verify your entries. Step 8 configure terminal Enter global configuration mode. Step 7 show vlan When the trunk links come up.Chapter 8 Configuring VLANs Load Sharing Using STP Beginning in privileged EXEC mode. and define Fa0/1 as the interface to set the STP cost. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-51 . and 4. Switch 1 receives the VTP information from the other switches. 9. Verify that Switch 1 has learned the VLAN configuration. and 10. 3. Step 3 switchport mode trunk Configure the port as a trunk port. Step 10 spanning-tree vlan 2 3 4 cost 30 Set the spanning-tree path cost to 30 for VLANs 2. Step 4 end Return to global configuration mode. make sure that interface Fa0/1 and Fa0/2 are configured as trunk ports. Step 11 end Return to global configuration mode. Step 2 interface fa0/1 Enter interface configuration mode. follow these steps to configure the network shown in Figure 8-6: Command Purpose Step 1 configure terminal Enter global configuration mode on Switch 1. Step 12 Repeat Steps 9 through 11 on Switch 1 interface Fa0/2. Step 13 exit Return to privileged EXEC mode. In the display. show running-config Verify your entries.

If the switch receives an access-denied response from the VMPS. The port must be manually reenabled by using the CLI. Cluster Management software. the VMPS sends an access-denied or a port-shutdown response. • If the VLAN in the database does not match the current VLAN on the port and active hosts exist on the port. You can also use an explicit entry in the configuration table to deny access to specific MAC addresses for security reasons. If you enter the none keyword for the VLAN name. – If the VLAN is not allowed on the port. If the switch receives a port-shutdown response from the VMPS. – If the VLAN is not allowed on the port. the VMPS sends a port-shutdown response. the VMPS sends an access-denied response. it disables the port. or SNMP. depending on the secure mode of the VMPS. When the VMPS receives a VQP request from a client switch.Chapter 8 Configuring VLANs How the VMPS Works How the VMPS Works A switch running this software release acts as a client to the VLAN Membership Policy Server (VMPS) and communicates with it through the VLAN Query Protocol (VQP). it searches its database for a MAC-address-to-VLAN mapping. The switch continues to monitor the packets directed to the port and sends a query to the VMPS when it identifies a new address. the VMPS verifies the requesting port against this group and responds as follows: – If the VLAN is allowed on the port. the VMPS sends the VLAN name to the client in response. and the VMPS is in secure mode. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-52 78-6511-05 . the VMPS takes one of the following actions: • If the assigned VLAN is restricted to a group of ports. the VMPS sends an access-denied or port-shutdown response. In response to a request. and the VMPS is not in secure mode. The server response is based on this mapping and whether or not the server is in secure mode. Secure mode determines whether the server shuts down the port when a VLAN is not allowed on it or just denies the port access to the VLAN. it continues to block traffic from the MAC address to or from the port.

For more information on possible VMPS responses. the port returns to an isolated state and does not belong to a VLAN. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-53 . it uses the domain name from the first VTP packet it receives on its trunk port from the VMPS. the VMPS either denies the request or shuts down the port (depending on the VMPS secure mode setting). The VMPS receives the source MAC address from the first packet of a new host connected to the dynamic port and attempts to match the MAC address to a VLAN in the VMPS database. the switch does not forward traffic to or from this port until the VMPS provides the VLAN assignment. If the client switch was not previously configured. the VMPS shuts down a dynamic port if more than 20 hosts are active on the port. If there is no match. the VMPS sends the VLAN number for that port. it includes its domain name in the query packet to the VMPS to obtain its VLAN number. Any hosts that come online through the port are checked again with the VMPS before the port is assigned to a VLAN. however.Chapter 8 Configuring VLANs How the VMPS Works Dynamic Port VLAN Membership A dynamic (nontrunking) port on the switch can belong to only one VLAN. When the link comes up. If the client switch was previously configured. If the link goes down on a dynamic port. If there is a match. 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. Multiple hosts (MAC addresses) can be active on a dynamic port if they are all in the same VLAN. see the “How the VMPS Works” section on page 8-52.

such as the domain name. These naming conventions must be used in the VMPS database configuration file when it is configured to support a cluster. !vmps domain <domain-name> ! The VMPS domain must be defined. This ASCII text file is stored on a switch-accessible TFTP server that functions as a VMPS server. The VMPS database configuration file on the server must use the Catalyst 2900 XL and Catalyst 3500 XL convention for naming ports.Chapter 8 Configuring VLANs How the VMPS Works VMPS Database Configuration File The VMPS contains a database configuration file that you create. If you do not configure a fallback VLAN and the MAC address does not exist in the database. The following example shows a sample VMPS database configuration file as it appears on a Catalyst 5000 series switch. Use a Catalyst 5000 series switch as the VMPS. !vmps mode { open | secure } ! The default mode is open. the VMPS sends the fallback VLAN name to the client. the fall-back VLAN name. the command switch adds the name of the switch before the Fa. es3%Fa02 refers to fixed 10/100 port 2 on member switch 3. vmps domain WBU vmps mode open vmps fallback default vmps no-domain-req deny ! ! !MAC Addresses ! vmps-mac-addrs ! Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-54 78-6511-05 . If you connect a device with a MAC address that is not in the database. it sends a port-shutdown response. the VMPS sends an access-denied response. You can configure a fallback VLAN name. and the MAC address-to-VLAN mapping. For example. The file contains VMPS information. !vmps fallback <vlan-name> !vmps no-domain-req { allow | deny } ! ! The default value is allow. Fa0/5 is fixed-port number 5. If the switch is a cluster member. A Catalyst 2900 XL or Catalyst 3500 XL switch running this software release cannot act as the VMPS. For example. If the VMPS is in secure mode.

168.168.eeff vlan-name Green address 1223.7654 vlan-name --NONE-address fedc.168.5678.16.1 port Fa0/9 vmps-port-policies vlan-name Purple device 192.1.2.3 all-ports ! !VLAN groups ! !vmps-vlan-group <group-name> ! vlan-name <vlan-name> ! vmps-vlan-group Engineering vlan-name hardware vlan-name software ! !VLAN port Policies ! !vmps-port-policies {vlan-name <vlan_name> | vlan-group <group-name> } ! { port-group <group-name> | device <device-id> port <port-name> } ! vmps-port-policies vlan-group Engineering port-group WiringCloset1 vmps-port-policies vlan-name Green device 192.a080 vlan-name hardware address aabb.ba98.1 port Fa1/3 device 172.1.2 port Fa0/10 port-group “Executive Row” Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-55 .2 port es5%Fa0/2 device 192.168.1.6509.168.1245 vlan-name Purple ! !Port Groups ! !vmps-port-group <group-name> ! device <device-id> { port <port-name> | all-ports } ! vmps-port-group WiringCloset1 device 192.2233.2.ba23.168.Chapter 8 Configuring VLANs How the VMPS Works ! address <addr> vlan-name <vlan_name> ! address 0012.1 port Fa1/4 vmps-port-group “Executive Row” device 192.ccdd.2.2.9abc vlan-name ExecStaff address fedc.4455 vlan-name hardware address 0000.2 port es5%Fa0/1 device 192.

the spanning-tree Port Fast feature is automatically enabled for that port. but it is possible to enter the switchport access vlan dynamic interface configuration command for a trunk port. • Dynamic ports cannot be network ports or monitor ports. You can disable Port Fast mode on a dynamic port.Chapter 8 Configuring VLANs How the VMPS Works VMPS Configuration Guidelines The following guidelines and restrictions apply to dynamic port VLAN membership: • You must configure the VMPS before you configure ports as dynamic. 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. For the cluster-based port-naming conventions. see the “VMPS Database Configuration File” section on page 8-54. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-56 78-6511-05 . You must disable port security on the port before it becomes dynamic. • When you configure a port as dynamic. • The communication between a cluster of switches and VMPS is managed by the command switch and includes port-naming conventions that are different from standard port names. The Port Fast mode accelerates the process of bringing the port into the forwarding state. • Secure ports cannot be dynamic ports. • The VTP management domain of the VMPS client and the VMPS server must be the same. • Trunk ports cannot be dynamic ports.

Table 8-13 Default VMPS Client and Dynamic Port Configuration Feature Default Configuration VMPS domain server None VMPS reconfirm interval 60 minutes VMPS server retry count 3 Dynamic ports None configured Configuring Dynamic VLAN Membership You must enter the IP address of the Catalyst 5000 switch or the other device acting as the VMPS to configure the Catalyst 2900 XL or Catalyst 3500 XL switch as a client. Step 2 vmps server ipaddress primary Enter the IP address of the switch acting as the primary VMPS server. Step 4 end Return to privileged EXEC mode. enter the address on the command switch. In the display. Beginning in privileged EXEC mode. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-57 . If the VMPS is being defined for a cluster of switches. Step 3 vmps server ipaddress Enter the IP address for the switch acting as a secondary VMPS server.Chapter 8 Configuring VLANs How the VMPS Works Default VMPS Configuration Table 8-13 shows the default VMPS and dynamic port configuration on client switches. Step 5 show vmps Verify the VMPS server entry. You can enter up to three secondary server addresses. follow these steps to enter the IP address of the VMPS: Command Purpose Step 1 configure terminal Enter global configuration mode. check the VMPS Domain Server field.

The dynamic-access port must be connected to an end station. check the Operational Mode field. see the “Configuring a Trunk Port” section on page 8-38. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-58 78-6511-05 .Chapter 8 Configuring VLANs How the VMPS Works Configuring Dynamic Ports on VMPS Clients If you are configuring a port on a member switch as a dynamic port. refer to the Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference. For more information on how to use this command. Step 4 switchport access vlan dynamic Configure the port as eligible for dynamic VLAN membership. follow these steps to configure a dynamic port on the VMPS client switches: Command Purpose Step 1 configure terminal Enter global configuration mode. first log into the member switch by using the privileged EXEC rcommand command. Connecting dynamic ports to other switches can cause a loss of connectivity. Caution Dynamic port VLAN membership is for end stations. Step 2 interface interface Enter interface configuration mode and the switch port that is connected to the end station. The switch port that is connected to the VMPS server should be configured as a trunk. In the display. Step 3 switchport mode access Set the port to access mode. For more information. Step 5 end Return to privileged EXEC mode. Step 6 show interface interface switchport Verify the entry. Beginning in privileged EXEC mode.

follow these steps to change the reconfirmation interval: Command Purpose Step 1 configure terminal Enter global configuration mode. this parameter must be equal to or greater than the reconfirmation setting on the command switch. Enter a number from 1 to 120. In addition. Step 3 end Return to privileged EXEC mode. For more information about this command. Step 2 show vmps Verify the dynamic VLAN reconfirmation status. Step 4 show vmps Verify the dynamic VLAN reconfirmation status. follow these steps to confirm the dynamic port VLAN membership assignments that the switch has received from the VMPS: Command Purpose Step 1 vmps reconfirm Reconfirm dynamic port VLAN membership. If you are configuring a member switch in a cluster. check the Reconfirm Interval field. Step 2 vmps reconfirm minutes Enter the number of minutes between reconfirmations of the dynamic VLAN membership. Beginning in privileged EXEC mode. The default is 60 minutes. You can set the number of minutes after which reconfirmation occurs. you must first log into the member switch by using the privileged EXEC rcommand command. refer to the Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-59 . In the display. Changing the Reconfirmation Interval VMPS clients periodically reconfirm the VLAN membership information received from the VMPS.Chapter 8 Configuring VLANs How the VMPS Works Reconfirming VLAN Memberships Beginning in privileged EXEC mode.

In the display. The switch displays the following information about the VMPS: VMPS VQP Version The version of VQP used to communicate with the VMPS. VMPS Action The result of the most recent reconfirmation attempt. The retry range is from 1 to 10. This can happen automatically when the reconfirmation interval expired. The one marked primary is the primary server. Reconfirm Interval The number of minutes the switch waits before reconfirming the VLAN-to-MAC-address assignments. 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. The switch queries the VMPS using version 1 of VQP. If no response is received after this many tries. the default is 3. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-60 78-6511-05 . or you can force it by entering the privileged EXEC vmps reconfirm command or its Cluster Management software or SNMP equivalent. Step 2 vmps retry count Change the retry count. the switch starts to query the secondary VMPS. Step 3 exit Return to privileged EXEC mode. VMPS domain server The IP address of the configured VLAN membership policy servers. Server Retry Count The number of times VQP resends a query to the VMPS.Chapter 8 Configuring VLANs How the VMPS Works Changing the Retry Count Beginning in privileged EXEC mode. check the Server Retry Count field. Administering and Monitoring the VMPS You can display information about the VMPS by using the privileged EXEC show vmps command. The switch sends queries to the one marked current. Step 4 show vmps Verify your entry.

enter the interface configuration no shutdown command. • The Catalyst 5000 series Switch 3 and Switch 10 are secondary VMPS servers.22. these assumptions apply: • The VMPS server and the VMPS client are separate switches.db and is stored on the TFTP server with the IP address 172. The VMPS shuts down the port to prevent the host from connecting to the network. • More than 20 active hosts reside on a dynamic port. In this example. • The Catalyst 5000 series Switch 1 is the primary VMPS server. and it will not allow the host to connect to the port. • End stations are connected to these clients: – Catalyst 2900 XL Switch 2 – Catalyst 3500 XL Switch 9 • The database configuration file is called Bldg-G.7.20.Chapter 8 Configuring VLANs How the VMPS Works Troubleshooting Dynamic Port VLAN Membership The VMPS shuts down a dynamic port under these conditions: • The VMPS is in secure mode. To reenable a shut-down dynamic port. Dynamic Port VLAN Membership Configuration Example Figure 8-7 shows a network with a VMPS server switch and VMPS client switches with dynamic ports. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-61 .

20.158 Trunk port Secondary VMPS Server 3 Switch 10 30769 End station 2 172.20.20.20.Chapter 8 Configuring VLANs How the VMPS Works Figure 8-7 Dynamic Port VLAN Membership Configuration TFTP server Catalyst 5000 series Primary VMPS Server 1 Switch 1 End station 1 Dynamic-access port Switch 2 Router 172.20.152 172.157 Client Switch 9 172.26.26.150 172.154 172.26.26.20.156 172.26.26.7 Client 172.26.20.155 172.20.26.20.20.22.153 Ethernet segment (Trunk link) Switch 4 172.26.151 Trunk port Secondary VMPS Server 2 Switch 3 Switch 5 Switch 6 Switch 7 Switch 8 Dynamic-access port 172.20.26.159 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-62 78-6511-05 .

• Avoiding configuration conflicts • Avoiding autonegotiation mismatches • Copying configuration files to troubleshooting configuration problems • Troubleshooting the Long-Reach Ethernet port configuration • Troubleshooting Cluster Management Suite (CMS) sessions • Troubleshooting switch upgrades • Recovering from corrupted software • Recovering from a lost or forgotten password For additional troubleshooting information. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 9-1 . refer to the switch hardware installation guide.9 C H A P T E R Troubleshooting This chapter provides the following information about avoiding and resolving problems related to the switch software.

Switch Port Analyzer (SPAN) can operate only if the monitor port or the port being monitored is not a protected port. Cannot be in a destination-based port group. if you define a port as the network port for a VLAN. You could not enable port security on the network port because a secure port limits the traffic allowed on it. 2. An Asynchronous Transfer Mode (ATM) port cannot be a monitor port but can be monitored. In Table 9-1. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 9-2 78-6511-05 . If you try to enable incompatible features by using CMS. and the switch does not save the change. 5. Catalyst 2900 XL switches only. 4. no means that the two features are incompatible and that both should not be enabled. yes means that both can be enabled at the same time and will not cause an incompatibility conflict. 3. all unknown unicast and multicast traffic is flooded to the port. Table 9-1 Conflicting Features ATM Port Protected Port Yes No Yes Yes ATM Port1 Port Group Port Security SPAN Port Connect Multi-VLAN Network to Port Port Cluster? N/A No No No No Port Group No Port Security No SPAN Port No Multi-VLAN Port No 3 No 2 – No No Yes Yes No – No No No Yes Yes No No – No No Yes Yes Yes No No – Yes Yes Yes 4 Yes Network Port No Yes No (sourcebased only) No Yes – No Connect to Cluster Yes Yes Yes Yes Yes No – Yes Protected Port No Yes Yes Yes5 Yes No Yes – 1. CMS issues a warning message that you are configuring a setting that is incompatible with another setting.Chapter 9 Troubleshooting Avoiding Configuration Conflicts Avoiding Configuration Conflicts Certain combinations of port features conflict with one another. For example. Cannot connect cluster members to the command switch.

configure the duplex settings on the two ports to match. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 9-3 . To maximize switch performance and ensure a link. • A port is set to autonegotiate. disable autonegotiation on the local device. Sometimes this protocol can incorrectly align these settings. 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. To connect to a remote Gigabit Ethernet device that does not autonegotiate.Chapter 9 Troubleshooting Avoiding Autonegotiation Mismatches Avoiding Autonegotiation Mismatches The IEEE 802.3u autonegotiation protocol manages the switch settings for speed (10 Mbps or 100 Mbps) and duplex (half or full). The speed parameter can adjust itself even if the connected port does not autonegotiate. If a remote Fast Ethernet device does not autonegotiate. follow one of these guidelines when changing the settings for duplex and speed: Note • Let both ports autonegotiate both speed and duplex. and the connected port is set to full duplex with no autonegotiation. • Manually set the speed and duplex parameters for the ports on both ends of the connection. reducing performance. and set the duplex and flow control parameters to be compatible with the remote device.

This situation means that the system is on the verge of generating CRC errors. Reduce the interleaver setting while ensuring the noise margin is adequate. Ensure that the interleaver is set to maximum protection (the interleaver trades latency for noise immunity). Excessive CRC errors on a LRE link High Reed-Solomon error count without CRC errors Ethernet performance degradation due to excessive network latency • A noisy environment (such as motors and power surges) is causing interference with the LRE link. Reduce the effect of stubs or bridge taps by terminating them with 300-Ohm microfilters. Reduce the effect of stubs or bridge taps by terminating them with 300-Ohm microfilters. Change to a profile using a lower QAM rate. Interleaver introduces extra latency to increase noise margin. If necessary. Change to a profile using a lower QAM rate. Disable installations with bundled unused LRE ports by using the lre shutdown interface configuration cables command. • The LRE link length and quality are close to the limit of operation. Change to a profile using a lower QAM rate. • Interleaver is helping Reed-Solomon error correction to function correctly in a noisy environment. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 9-4 78-6511-05 . • The LRE link length and quality are close to the limit of operation. change to a profile using a lower QAM rate. Change to a profile using a lower QAM rate. which increases the noise margin. Reduce the effect of stubs or bridge taps by terminating them with 300-Ohm microfilters. LRE link quality reduced in Cross-talk between the LRE links is causing all links to degrade.Chapter 9 Troubleshooting Troubleshooting LRE Port Configuration Troubleshooting LRE Port Configuration Table 9-2 lists problems you might encounter when configuring and monitoring the Long-Reach Ethernet (LRE) ports on the Catalyst 2900 LRE XL switches. Ensure that the interleaver is set to maximum protection (the interleaver trades latency for noise immunity). Table 9-2 LRE Port Problems Problem Suggested Solution LRE port LED is amber The switch and CPE are unable to establish a LRE link using the selected profile. Change to a profile using a lower quadrature amplitude modulation (QAM) rate. which increases the noise margin.

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 9-5 . Refer to the release notes for the required Java plug-ins. verify that Use browser settings is checked and that no proxies are enabled. see the “Management VLANs” section on page 8-4. Each time you start CMS. This notification does not occur if your PC is directly connected to the switch and has no internet connection. The Applet notinited message appears at the bottom of the browser window. A missing browser Java plug-in or incorrect settings could cause this problem. • CMS requires a Java plug-in to function correctly. which is the default HTTP port number. In the Proxies tab. – Make sure that the HTTP port number is 80. Delete the jar files from the location where the browser keeps the temporary files on your computer. CMS only works with port 80. – Make sure the port that connects the PC to the switch belongs to the same VLAN as the management VLAN. the browser notifies you that the Java plug-in is required if the plug-in is not installed. • If the plug-in is installed but the Java applet does not initialize. For more information about management VLANs. For instructions on downloading and installing the plug-in. the Java plug-in saves a copy of all the jar files to the disk.Chapter 9 Troubleshooting Troubleshooting CMS Sessions Troubleshooting CMS Sessions Table 9-3 lists problems commonly encountered when using CMS: Table 9-3 Common CMS Session Problems Problem Suggested Solution A blank screen appears when you click Cluster Management Suite or Visual Switch Manager from the Cisco Systems Access page. refer to the release notes. do the following: – Select Start > Programs > Java Plug-in Control Panel. Note If your PC is connected to the Internet when you attempt to access CMS. You might not have enough disk space.

which Internet Explorer uses to launch the Java plug-in. 3. from running. Deselect Require server verification. Move the Security Level for this Zone slider from High to Medium (the default). Configuration changes are Microsoft Internet Explorer 5.) 1. follow these steps: (For switches running software earlier than Cisco IOS Release 12. click Security.0(5)WC(1). select Tools > Internet Options. If it does not. 4. and click Sites. you receive a message stating that the CMS page might not display correctly because your security settings prohibit running ActiveX controls. 4. and click OK.0 for every configuration change.Chapter 9 Troubleshooting Troubleshooting CMS Sessions Table 9-3 Common CMS Session Problems (continued) Problem Suggested Solution In an Internet Explorer browser session. In the Temporary Internet Files section. select Tools > Internet Options. 7. Start Internet Explorer. 5. A high security level prohibits ActiveX controls. Select the Java logging enabled and JIT compiler for virtual machine enabled check boxes.0 browser. 1. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 9-6 78-6511-05 . From the menu bar. 8. Click the Security tab. 2. 6. In the Internet Options window. 6. Click the indicated Zone. have a green circle with a checkmark. the lower right corner of your browser screen should Explorer 5. If your browser security information in an Internet settings are correct. click Advanced. From the menu bar. browser session. click Settings. Start Internet Explorer. and click Apply. click Every visit to the page. click General. Make sure you click the browser Refresh button Internet Explorer 5. Link graphs do not display Your browser security settings could be incorrect. Click Custom Level and verify that the four ActiveX settings are set to prompt or enabled. From the Internet Options window. 3.0 does not automatically reflect the latest not always reflected in an configuration changes. 5. click Trusted Sites. In the Internet Options window. 2.

15. Click Add to add each switch. To display the console. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 9-7 . click OK. If you do not see Java > Java permissions. click OK. select Start > Programs > Java Plug-in Control Panel.36 10. click OK. you might enter: http://172. While still in the Security tab of the Internet Options window. 13. In the Security Settings window. Under Run Unsigned Content. click Enable. Click Custom. When you reinstall this browser. make sure to click the Microsoft Virtual Machine check box to display applets written in Java. and select Java Console. In the Internet Options window. you can use the Java plug-in console to display the current status and actions of CMS. For example. In the Security Settings window. After you have finished entering the URLs for your switches.20. and click Java Custom Settings. Add the switches you want to manage by entering their URLs in the Add this web site to the zone field. Then. 12. click Custom Level. select Java > Java permissions.153. make sure to select the Install Minimal or Customize Your Browser check box. from the Component Options window in the Internet Explorer 5 section. In the Trusted Sites window. click Edit Permissions. you need to reinstall the browser.Chapter 9 Troubleshooting Troubleshooting CMS Sessions Table 9-3 Problem Common CMS Session Problems (continued) Suggested Solution 9. 14. For further debugging information. 11. and click OK. A URL is the switch IP address preceded by http://. 16. 17.

Figure 9-1 Cluster View Right-click a device with a yellow label to display the device pop-up menu. and select Disqualification Code. you can learn why by selecting Views > Toggle View from the menu bar in Cluster Builder. 54506 mcluster Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 9-8 78-6511-05 . Cluster View displays the cluster as a double-switch icon and shows connections to devices outside the cluster (Figure 9-1). and select Disqualification Code to display the reason it could not join the cluster. Right-click the device (yellow label).Chapter 9 Troubleshooting Determining Why a Switch Is Not Added to a Cluster Determining Why a Switch Is Not Added to a Cluster If a switch does not become part of the cluster.

text 1728000 bytes total (456704 bytes free) The file system uses a URL-based file specification. You can then copy the configuration file to a replacement switch and avoid having to reconfigure the switch. Step 1 Enter the privileged EXEC dir flash: command to display the contents of Flash memory: switch# dir flash: Directory of flash: 2 4 66 68 -rwx drwx -rwx -rwx 843947 3776 130 1296 Mar Mar Jan Mar 01 01 01 01 1993 1993 1970 1993 00:02:18 01:23:24 00:01:19 06:55:51 C2900XL-h-mz-112. The following example uses the TFTP protocol to copy the file config.8-SA html env_vars config.text flash:config.text from the host arno to the switch Flash memory: switch# copy tftp://arno//2900/config.text You can enter the following parameters as part of a filename: • TFTP • Flash • RCP • XMODEM Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 9-9 . This could be useful if you wanted to save configuration files on an external server in case a switch fails.Chapter 9 Troubleshooting Copying Configuration Files to Troubleshoot Configuration Problems Copying Configuration Files to Troubleshoot Configuration Problems You can use the file system in Flash memory to copy files and to troubleshoot configuration problems.

the bootup process fails. It might take a minute or two to save the configuration to Flash memory..0 image. as the file present on the Flash memory could be corrupted or invalid. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 9-10 78-6511-05 . This error message appears when the names of the bootable file and the actual file in the Flash differ. This usually happens due to a mistyped file name when setting the boot parameters.Chapter 9 Troubleshooting Troubleshooting Switch Upgrades Step 2 Enter the copy running-config startup-config privileged EXEC command to save your configuration changes to Flash memory so that they are not lost if there is a system reload or power outage. This error message appears when a 4-MB Catalyst 2900 XL switch is upgraded to an image that is not supported on this hardware. perform an X-Modem upgrade. After it has been saved.. but because this switch is not capable of loading this image. during or after the upgrade. The switch in this case tries to load the image. Go to Setting BOOT Parameters at ROMMON (Switch: Prompt) to verify and set the BOOT parameters correctly. If setting the BOOT parameters to the correct file name does not resolve the issue. Getting “No Such File or Directory” error message during bootup. This also happens in cases when a 4-MB Catalyst 2900 XL switch is upgraded to an IOS 12. Download the IOS Image File by using X-Modem. the following message appears: [OK] switch# Troubleshooting Switch Upgrades Table 9-4 lists problems commonly encountered when upgrading the switch: Table 9-4 Problems Encountered When Upgrading the Switch Problem Suggested Solution Getting “Address Range” error message and boot up is failing. This example shows how to use this command to save your changes: switch# copy running-config startup-config Building configuration.

the word flash: is mistyped or completely missed. Enter the dir flash: command to verify if there is any bootable image on the Flash. If you do not see any bootable image in the Flash. 1. In most of the cases. when setting the boot parameters during or after the upgrade. perform an X-Modem upgrade. Enter the set BOOT flash: name of IOS file command to set the boot variable to the file name displayed in Step 1. download the IOS Image File by using X-Modem. The file with . Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 9-11 . BOOT must be capitalized and make sure to include flash: before the file name. Note 4. Go to Setting BOOT Parameters at ROMMON (Switch: Prompt) to verify and set the BOOT parameters correctly. If the switch fails to boot properly. If setting the BOOT parameters to the correct file name does not resolve the issue. or the image in Flash memory could be missing. the system will load the boot helper and bring up a switch prompt. The error loading Flash message means that there is a problem loading the current image in Flash memory. The image could be corrupt or incorrect. and proceed to Step 4. This error message appears when the boot parameters are not set correctly.bin extension is the bootable image on the Flash. reload the switch by entering the reload privileged EXEC command. 2. Enter the boot command. The switch boots up automatically with the correct image.Chapter 9 Troubleshooting Troubleshooting Switch Upgrades Table 9-4 Problems Encountered When Upgrading the Switch (continued) Problem Suggested Solution Getting “Permission Denied” error message during the bootup. If the switch boots properly. continue to Step 2. After setting the BOOT parameters. Note 3. download the IOS Image File using X-Modem. If the system is unable to load a software image in Flash memory. Getting “Error Loading Flash” error messages. as the file present on the Flash memory could be corrupted or invalid. enter the setting boot parameters global configuration command to verify and set the BOOT parameters (if needed). If you see a bootable image on the Flash.

(switch: prompt). needs a manual 1. Switch not booting The switch boot parameters might be set for manual boot. 1. Press the Enter key a few times. Verify the boot parameters by entering show boot. Enter the privileged EXEC mode by entering the enable command at the ROMMON switch> prompt. 4. and plug the power cord back in. go to Step 4. This might be due to a corrupt or incorrect image. and correct them if needed. boot at the 2. All LEDs above all ports should come on green. Enter the global configuration mode by entering configure terminal at the Switch# prompt. or connect the PC to the switch console port. 6. Otherwise. 2. 4. Connect the PC to the switch console port. the switch still boots up with the old image. download the IOS Image File using X-Modem. Download the IOS Image File using X-Modem. • If the BOOT parameters are correct. Enter no boot manual to tell the switch to boot automatically. prompt? If not. Enter end to return to privileged EXEC mode. and then release the mode button. This happens when either the BOOT parameters are not correct and the switch is still set to boot from the old image or the upgrade did not go through properly. download the IOS Image File using TFTP. Verify the BOOT parameters. Hold down the mode button on the front of the switch. Use Telnet to access the switch. Disconnect the power cord. Verify that Manual Boot is set to no. 5. 3. Following these steps to recover if the switch is in a reset loop after or during the upgrade. Continue to hold down the mode button until the light above port 1 goes out. The switch can be set to boot automatically by following these steps: automatically. • If the switch still boots with the old image.Chapter 9 Troubleshooting Troubleshooting Switch Upgrades Table 9-4 Problems Encountered When Upgrading the Switch (continued) Problem Suggested Solution Failed software upgrade. The prompt should be switch:. or the image in Flash might be missing. and save the configuration by entering the write memory command. After the upgrade. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 9-12 78-6511-05 . 3. Are you seeing a switch: go to Step 3. switch is resetting continuously.

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 9-13 . Secured ports are described in the “Enabling Port Security” section on page 7-15. see the “Management VLAN” section on page 5-11. If you are unable to maintain management contact with a member.Chapter 9 Troubleshooting Recovery Procedures Recovery Procedures The recovery procedures in this section require that you have physical access to the switch. see the “Enabling a Network Port” section on page 7-7. check for the following port-configuration conflicts: • Member switches cannot connect to the command switch through a port that is defined as a network port. Recovery procedures include the following topics: • Recovering from lost member connectivity • Recovering from a command-switch failure • Recovering from a lost or forgotten password • Recovering from corrupted software Recovering from Lost Member Connectivity Some configurations can prevent the command switch from maintaining contact with member switches. For information on the network port feature. For more information. • Member switches must connect to the command switch through a port that belongs to the same management VLAN. • Member switches connected to the command switch through a secured port can lose connectivity if the port is disabled due to a security violation. and the member switch is forwarding packets normally.

making a note of the command-switch password. you can configure a redundant command switch group by using the Hot Standby Router Protocol (HSRP). For more information. If you have not configured a standby command switch. management contact with the member switches is lost. You can manage the members as standalone switches through the console port or. You can prepare for a command switch failure by assigning an IP address to a member switch or another switch that is command-capable. see the “Designating and Enabling Standby Command Switches” section on page 5-17. and cabling your cluster to provide redundant connectivity between the member switches and the replacement command switch. Note HSRP is the preferred method for supplying redundancy to a cluster. and a new command switch must be installed.Chapter 9 Troubleshooting Recovery Procedures Recovering from a Command Switch Failure This section describes how to recover from a failed command switch. If you are running IOS Release 12. see the release notes. through the other management interfaces. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 9-14 78-6511-05 .0(5)XU. and the member switches forward packets as usual. and your command switch loses power or fails in some other way. However. This section describes two solutions for replacing a failed command switch: • Replacing a failed command switch with a cluster member • Replacing a failed command switch with another switch For a list of command-capable Catalyst desktop switches. if they have IP addresses. connectivity between switches that are still connected is not affected.

enter global configuration mode. Step 7 End with CNTL/Z. if an IP address has been assigned to the switch. Switch# config terminal Enter configuration commands.Chapter 9 Troubleshooting Recovery Procedures Replacing a Failed Command Switch with a Cluster Member Follow these steps to replace a failed command switch with a command-capable member of the same cluster: Step 1 Disconnect the command switch from the member switches. and physically remove it from the cluster. refer to the switch installation guide. remove previous command-switch information from the switch. Step 4 At the switch prompt. Step 6 From privileged EXEC mode. Step 3 Start a command-line interface (CLI) session on the new command switch. Switch(config)# exit Switch# Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 9-15 . For details about using the console port. Step 2 Use a member switch in place of the failed command switch. Switch(config)# no cluster commander-address Step 8 Return to privileged EXEC mode. by using Telnet. and duplicate its connections to the cluster members. change to privileged EXEC mode: Switch> enable Switch# Step 5 Enter the password of the failed command switch. From global configuration mode. one per line. You can access the CLI by using the console port or.

and press Return: Enter IP netmask: ip_netmask Step 13 Enter Y at the next prompt to specify a default gateway (router): Would you like to enter a default gateway address? [yes]: y Step 14 Enter the IP address of the default gateway.System Configuration Dialog --At any point you may enter a question mark ’?’ for help. Use Ctrl-c to abort configuration dialog at any prompt. Continue with configuration dialog? [yes/no]: Step 10 Enter Y at the first prompt. and press Return: Enter IP address: ip_address Step 12 Enter the subnet mask. and press Return. On a command switch.Chapter 9 Troubleshooting Recovery Procedures Step 9 Use the setup program to configure the switch IP information. and press Return. Continue with configuration dialog? [yes/no]: y Step 11 Enter the switch IP address. Do not use -n. IP address of the default gateway: ip_address Step 15 Note Enter a host name for the switch. enter setup. as the last character in a host name for any switch. where n is a number. subnet mask. This program prompts you for an IP address. Switch# setup --. and password. and press Return. default gateway. Enter a host name: host_name Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 9-16 78-6511-05 . on a member switch to 31 characters. From privileged EXEC mode. Default settings are in square brackets ’[]’. the host name is limited to 28 characters.

dashes.Chapter 9 Troubleshooting Recovery Procedures Step 16 Note Enter the password of the failed command switch.255.36 255. The initial configuration is displayed: The following configuration command script was created: ip subnet-zero interface VLAN1 ip address 172.0 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 9-17 . Enter the Telnet password. Enter enable secret: secret_password Step 17 Enter Y to enter a Telnet password: Would you like to configure a Telnet password? [yes] y Note Step 18 The password can be from 1 to 25 alphanumeric characters. is case sensitive.20. In this case. but ignores leading spaces.255. allows spaces. allows spaces. If you enter N. and press Return. The password can be from 1 to 25 alphanumeric characters. and press Return. or underscores. Enter cluster name: cls_name Note Step 21 The cluster name can be 1 to 31 alphanumeric characters. is case sensitive. can start with a number. the message in Step 20 is not displayed. Would you like to enable as a cluster command switch? y Step 20 Assign a name to the cluster. but ignores leading spaces. and press Return: Enter Telnet password: telnet_password Step 19 Note Enter Y to configure the switch as the cluster command switch.153. the switch appears as a candidate switch in Cluster Builder. Enter N to configure it as a member switch or as a standalone switch.

CMS prompts you to add candidate switches. and select Enabled from the Command Switch drop-down list. • If the information is correct. enter Y at the prompt. and you should enter it when candidate switches are proposed for cluster membership.20. Step 25 Click Cluster Management.153. and enter the switch IP address that you entered in Step 11. The password of the failed command switch is still valid for the cluster. Step 24 Display the VSM Home page for the switch.Chapter 9 Troubleshooting Recovery Procedures ip default-gateway 172. • If the information is not correct. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 9-18 78-6511-05 . and begin again at Step 1. Use this configuration? [yes/no]: y Step 23 Start your browser. and display Cluster Builder. press Return. and press Return. enter N at the prompt.01 hostname host_name enable secret 5 $1$M3pS$cXtAlkyR3/6Cn8/ line vty 0 15 password telnet_password snmp community private rw snmp community public ro cluster enable cls_name end Step 22 Verify that the information is correct.

and press Return: Enter IP netmask: ip_netmask Step 9 Enter Y at the next prompt to specify a default gateway (router): Would you like to enter a default gateway address? [yes]: y Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 9-19 .System Configuration Dialog --At any point you may enter a question mark ’?’ for help. and password. and press Return: Enter IP address: ip_address Step 8 Enter the subnet mask. Continue with configuration dialog? [yes/no]: y Step 7 Enter the switch IP address. Switch# setup --. Continue with configuration dialog? [yes/no]: Step 6 Enter Y at the first prompt. and press Return. Step 5 Use the setup program to configure the switch IP information. if an IP address has been assigned to the switch. From privileged EXEC mode. refer to the switch hardware installation guide.Chapter 9 Troubleshooting Recovery Procedures Replacing a Failed Command Switch with Another Switch Follow these steps when you are replacing a failed command switch with a switch that is command-capable but not part of the cluster: Step 1 Insert the new switch in place of the failed command switch. Default settings are in square brackets ’[]’. For details about using the console port. Use ctrl-c to abort configuration dialog at any prompt. This program prompts you for an IP address. by using Telnet. enter setup. You can access the CLI by using the console port or. Step 3 At the switch prompt. Step 2 Start a CLI session on the new command switch. and duplicate its connections to the cluster members. subnet mask. default gateway. change to privileged EXEC mode: Switch> enable Switch# Step 4 Enter the password of the failed command switch.

IP address of the default gateway: ip_address Step 11 Note Enter a host name for the switch. Enter a host name: host_name Step 12 Note Enter the password of the failed command switch. Enter the Telnet password. and press Return. Enter enable secret: secret_password Step 13 Enter Y to enter a Telnet password: Would you like to configure a Telnet password? [yes] y Note Step 14 The password can be from 1 to 25 alphanumeric characters. but ignores leading spaces. on a member switch to 31 characters. Enter N to configure it as a member switch or as a standalone switch. allows spaces. where n is a number. In this case. allows spaces. The password can be from 1 to 25 alphanumeric characters. the switch appears as a candidate switch in Cluster Builder. Do not use -n. as the last character in a host name for any switch. and press Return. is case sensitive. is case sensitive. and press Return. but ignores leading spaces. the message in Step 20 is not displayed. and press Return: Enter Telnet password: telnet_password Step 15 Note Enter Y to configure the switch as the cluster command switch.Chapter 9 Troubleshooting Recovery Procedures Step 10 Enter the IP address of the default gateway. the host name is limited to 28 characters. On a command switch. can start with a number. Would you like to enable as a cluster command switch? y Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 9-20 78-6511-05 . If you enter N.

The initial configuration is displayed: The following configuration command script was created: ip subnet-zero interface VLAN1 ip address 172. and begin again at Step 1.255. Enter it when candidate switches are proposed for cluster membership.01 hostname host_name enable secret 5 $1$M3pS$cXtAlkyR3/6Cn8/ line vty 0 15 password telnet_password snmp community private rw snmp community public ro cluster enable cls_name end Step 18 Verify that the information is correct. • If the information is not correct.36 255. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 9-21 . The password of the failed command switch is still valid for the cluster.20.20. and enter the switch IP address that you entered in Step 7. press Return.0 ip default-gateway 172. or underscores.Chapter 9 Troubleshooting Recovery Procedures Step 16 Assign a name to the cluster.153. and press Return. and click OK.255.153. enter N at the prompt. and display Cluster Builder. dashes. Use this configuration? [yes/no]: y Step 19 Start your browser. enter Y at the prompt. Enter cluster name: cls_name Note Step 17 The cluster name can be 1 to 31 alphanumeric characters. • If the information is correct. and press Return. It prompts you to add the candidate switches. Step 20 Click Cluster Manager Suite or Visual Switch Manager.

and at the same time. reconnect the power cord to the switch. If the command switch fails and there is no standby command switch. Step 3 Unplug the switch power cord. Step 2 Set the line speed on the emulation software to 9600 baud. you can use the command-switch password to recover. The following commands will initialize the flash file system. For more information. as do instructions: The system has been interrupted prior to initializing the flash file system. Several lines of information about the software appear. You can configure member switches through the console-port CLI. For more information. The password you enter when you log in to the command switch gives you access to member switches. refer to the switch installation guide. and Telnet after you assign an IP address to them. Recovering from a Lost or Forgotten Password Follow the steps in this procedure if you have forgotten or lost the switch password. HTML. and finish loading the operating system software: flash_init Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 9-22 78-6511-05 . and they can still be managed through normal standalone means. Step 1 Connect a terminal or PC with terminal emulation software to the console port.Chapter 9 Troubleshooting Recovery Procedures Recovering from a Failed Command Switch Without HSRP If a command switch fails and there is no standby command switch configured. see the “Recovering from a Command Switch Failure” section on page 9-14. You can release the Mode button a second or two after the LED above port 1X goes off. Step 4 Press the Mode button. and they can be managed through SNMP. Note You can configure your switch for Telnet by following the procedure in the “Accessing the CLI” section on page 3-8. member switches continue forwarding among themselves.

8-SA 01:23:24 html 00:01:19 env_vars 06:55:51 config. Step 7 Load any helper files: switch: load_helper Step 8 Display the contents of Flash memory: switch: dir flash: The switch file system is displayed: Directory of flash: 2 4 66 68 -rwx drwx -rwx -rwx 843947 3776 130 1296 Mar Mar Jan Mar 01 01 01 01 1993 1993 1970 1993 00:02:18 C2900XL-h-mz-112.Chapter 9 Troubleshooting Recovery Procedures load_helper boot Step 5 Initialize the Flash file system: switch: flash_init Step 6 If you had set the console port speed to anything other than 9600. This file contains the password definition.text.text.old Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 9-23 . switch: rename flash:config. Change the emulation software line speed to match that of the switch console port.text flash:config.text 1728000 bytes total (456704 bytes free) Step 9 Rename the configuration file to config. it has been reset to that particular speed.old.

text. The configuration file is now reloaded.old flash:config. Step 14 Enter global configuration mode: switch# config terminal Step 15 Change the password: switch(config)# enable secret <password> or switch(config)# enable password <password> Step 16 Return to privileged EXEC mode: switch(config)# exit switch# Step 17 Write the running configuration to the startup configuration file: switch# copy running-config startup-config The new password is now included in the startup configuration. and you can use the following normal commands to change the password. change to privileged EXEC mode: switch> enable Step 12 Rename the configuration file to its original name: switch# rename flash:config.Chapter 9 Troubleshooting Recovery Procedures Step 10 Boot the system: switch: boot You are prompted to start the setup program. Enter N at the prompt: Continue with the configuration dialog? [yes/no]: N Step 11 At the switch prompt.text Step 13 Copy the configuration file into memory: switch# copy flash:config.text]? Destination filename [running-config]? Press Return in response to the confirmation prompts. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 9-24 78-6511-05 .text system:running-config Source filename [config.

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 9-25 . which is indicated by the switch: prompt. and this procedure is largely dependent on the emulation software you are using. The software image does not load. by downloading the wrong file to the switch. Step 3 Unplug the switch power cord. and by deleting the image file.Chapter 9 Troubleshooting Recovery Procedures Recovering from Corrupted Software Switch software can be corrupted during an upgrade. the switch does not pass the power-on self-test (POST). Step 1 Connect a PC with terminal-emulation software supporting the XMODEM Protocol to the switch console port. switch: copy xmodem: flash:image_filename. Step 5 Use the boot loader to enter commands. and start the transfer. and there is no connectivity. Step 2 Set the line speed on the emulation software to 9600 baud. use the appropriate command on the terminal-emulation software to start the transfer and to copy the software image to Flash memory. Step 4 Reconnect the power cord to the switch. There are many software packages that support the XMODEM protocol. The following procedure uses the XMODEM Protocol to recover from a corrupt or wrong image file. The switch starts in boot loader mode.bin Step 6 When the XMODEM request appears. In all these cases.

Chapter 9 Troubleshooting Recovery Procedures Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 9-26 78-6511-05 .

while others can help diagnose problems with communications lines. The system software sends these error messages to the console (and. page A-4 • Error Message and Recovery Procedures. or the system software. Some messages are purely informational. optionally. This appendix contains the following sections: • How to Read System Error Messages. internal hardware. to a logging server on another system) during operation. page A-2 • Error Message Traceback Reports. page A-5 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 A-1 . Not all system error messages indicate problems with your system.A P P E N D I X A System Error Messages This appendix describes the IOS system error messages for the switch.

A facility can be a hardware device. .Appendix A System Error Messages How to Read System Error Messages How to Read System Error Messages System error messages begin with a percent sign (%) and are structured as follows: %FACILITY-SUBFACILITY-SEVERITY-MNEMONIC: Message-text • FACILITY is a code consisting of two or more uppercase letters that indicate the facility to which the message refers. a protocol. Table A-1 Facility Codes Code Facility CHASSIS Chassis CMP Cluster Membership Protocol ENVIRONMENT Environment GIGASTACK GigaStack GBIC LINK Link LRE_LINK LRE Link MODULE Module PORT SECURITY Port Security RTD Runtime Diagnostic STORM CONTROL Storm Control Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide A-2 78-6511-05 . Table A-1 lists the system facility codes. or a module of the system software.

The lower the number. Table A-3 Representation of Variable Fields in Messages Representation Type of Information [dec] Decimal [char] Single character [chars] Character string [hex] Hexadecimal integer [inet] Internet address Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 A-3 . network addresses. 7 – debugging Message that appears during debugging only. or addresses that correspond to locations in the system memory address space. • MNEMONIC is a code that uniquely identifies the error message.Appendix A System Error Messages How to Read System Error Messages • SEVERITY is a single-digit code from 0 to 7 that reflects the severity of the condition. 3 – error Error condition. Table A-3 lists the variable fields in messages. 4 – warning Warning condition. • Message-text is a text string describing the condition. including terminal port numbers. Because the information in these variable fields changes from message to message. 2 – critical Critical condition. is represented as [dec]. for example. 5 – notification Normal but significant condition. Table A-2 lists the message severity levels. Table A-2 Message Severity Levels Severity Level Description 0 – emergency System is unusable. 6 – informational Informational message only. 1 – alert Immediate action required. This portion of the message sometimes contains detailed information about the event. A decimal number. the more serious the situation. it is represented here by short strings enclosed in square brackets ([ ]).

Appendix A System Error Messages Error Message Traceback Reports The following is a sample system error message: %LINK-2-BADVCALL: Interface [chars].) Error Message Traceback Reports Some messages describe internal errors and contain traceback information. undefined entry point Some error messages also indicate the card and slot reporting the error. It is always shown as MSG. SLOT means that the slot number of the card reporting the error. (For example. SLOT5. It is shown as SLOT followed by a number. The following sample message includes traceback information: -Process= "Exec". MSG is a mnemonic that means that this is a message. This information is very important and should be included when you report a problem to your technical support representative. level= 0. pid= 17 -Traceback= 1A82 1AB4 6378 A072 1054 1860 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide A-4 78-6511-05 . These error messages begin with a percent sign (%) and are structured as follows: %CARD-SEVERITY-MSG:SLOT %FACILITY-SEVERITY-MNEMONIC: Message-text CARD is a code that describes the type of card reporting the error.

and [inet] is the Internet address of the command switch. CHASSIS-5-BLADE_EXTRACT Explanation The message means that the hot-swap switch has been pressed. CMDR IP Address [inet]) Explanation The message means that the device is added to the cluster: [chars] is the cluster name. Chassis Message This section contains the Chassis error message.Appendix A System Error Messages Error Message and Recovery Procedures Error Message and Recovery Procedures This section lists the switch system messages by facility. the messages are listed by severity levels 0 to 7: 0 is the highest severity level. CMP Messages This section contains the Cluster Membership Protocol (CMP) error messages. Action No action is required. CMP-5-ADD: The Device is added to the cluster (Cluster Name:[chars]. and 7 is the lowest severity level. Within each facility. Each message is followed by an explanation and a recommended action. Action No action is required. Action Extract the module. CMP-5-MEMBER_CONFIG_UPDATE: Received member configuration from member [dec] Explanation This message means that the command switch received a member configuration: [dec] is the member number. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 A-5 .

Action No action is required. Action Use the show env command to check if an overtemperature condition exists. If a multiple-fan failure is causing the switch to overheat. Action Either check the switch itself. ENVIRONMENT-2-FAN_FAULT Explanation This message means that an internal fan fault is detected. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide A-6 78-6511-05 . If it does: • Place the switch in an environment that is within 32 to 113°F (0 to 45°C). This message is available only on the Catalyst 3524-PWR XL switch. This message is available only on the Catalyst 3524-PWR XL switch. Replace the switch at your convenience. or use the show env privileged EXEC command to check if a fan on the switch has failed. The Catalyst 3524-PWR XL switch can operate normally with one failed fan.Appendix A System Error Messages Error Message and Recovery Procedures CMP-5-REMOVE The Device is removed from the cluster (Cluster Name:[chars]) Explanation The message means that the device is removed from the cluster: [chars] is the cluster name. ENVIRONMENT-2-OVER_TEMP Explanation This message means that an overtemperature condition is detected. replace the switch. • Make sure fan intake and exhaust areas are clear. Environment Messages This section contains the Environment error messages.

Link 2 of the Master Loop Breaker is re-enabled to replace the broken line. Action If loop topology is used in the GigaStack. or the link between the two GigaStack GBICs is broken. GIGASTACK-6-LOOP_BROKEN Explanation This message means that a loop formed by GigaStack modules is broken because of link loss. GIGASTACK-6-NO_LOOP_DETECT Explanation This message means that no acknowledgement for GigaStack loop detection request is received from one of the links on a GigaStack GBIC.Appendix A System Error Messages Error Message and Recovery Procedures GigaStack Messages This section contains the GigaStack error messages. Action No action is required. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 A-7 . make sure the latest software is running on all switches in the stack. a GigaStack loop topology is not automatically detected. Either the neighboring switch does not support the GigaStack Loop breaking algorithm. Under this condition. GIGASTACK-6-LOOP_DETECTED Explanation This message means that a loop has been detected in the GigaStack. Link 2 of this GigaStack GBIC is disabled to break the loop. and this GigaStack GBIC is selected as the Master Loop Breaker. and the connectivity between switches in the stack could be lost. Check the GigaStack GBICs involved to make sure they are functioning. Action No action is required.

reduced rate mode. the LRE port first attempts to briefly establish link with the CPE in a common. LRE_LINK-3-PROFILE_FAILURE: Interface. It might also be caused by any substantial interruption of the signal or cabling between the LRE port and the CPE. Explanation This messages means that excessive errors have occurred on this interface: [char] is the interface. profile failure Explanation When the switch reloads or when the LRE link is lost. it could mean a physical disconnection at the switch or CPE or a loss of power to the CPE. reconfiguring a profile in use by this port. Note The previous error is a LINK-4-ERROR message. This could be the result of reconfiguring the port. LRE_LINK-3-UPDOWN: Interface changed state to up or down Explanation This message means that the link between the LRE port and the CPE device has been lost and that no Ethernet traffic is being transferred. Action If someone is reconfiguring the port or the profile in use. Action Check for duplex mismatches between both ends of the link.Appendix A System Error Messages Error Message and Recovery Procedures Link Message This section contains the Link error message. LINK-4-ERROR [chars] is experiencing errors. ignore this message. However. LRE Link Messages This section contains the LRE Link error messages. a physical disconnection or reconnection of the LRE connector on the switch. if the LRE link does not go back up within a minute or so. which is logged at the Warning level. LINK-3-ERROR messages are more severe and are logged at the Error level. or by someone disconnecting the CPE LRE cable or cycling its power. This is so that the switch can exchange configuration information Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide A-8 78-6511-05 .

MODULES-3-MAC_TBL_SIZE Explanation This messages means that dynamic module insertion supports less MAC addresses. after a time (typically 30 seconds). Action Reboot system to use the module.Appendix A System Error Messages Error Message and Recovery Procedures with the CPE to achieve the link rate of the profile configured for the port. or add the MAC address to the secure address table of the secure port. When the reduced rate is achieved. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 A-9 . no LRE link is established. Port Security Messages This section contains the Port Security error message. starting from the reduced rate. this message appears. The port continues to attempt to establish link. and the LRE and CPE ports attempt to establish the profile link rate. This message could also mean that the switch or CPE is faulty. Action Change the profile on the port to one that has a lower rate or has a longer reach. Action Remove the station with the unexpected MAC address from the secure port. Module Message This section contains the Module error message. contact Cisco Systems. There might be too many impairments on the connection between the switch and the CPE for the ports to sustain the profile rate. and the port LED is amber. PORT_SECURITY-2-SECURITYREJECT Explanation This message means that a packet with an unexpected source address is received on a secure port. link is dropped briefly. If you suspect the switch or CPE is faulty. If.

and [dec] is the number of times the link goes up and down. Go to the switch attached to that port. RTD-1-ADDR_FLAP [chars] relearning [dec] addrs per min Explanation Normally. or it might indicate a faulty device at the other end of the connection. due to either manual or STP reconfiguration. However. ignore this message. Occasionally. Use debug ethernet-controller addr to see the alternate path-port on which the address is being learned. and remove that port from the network. Action Determine the real path (port) to the MAC address.Appendix A System Error Messages Error Message and Recovery Procedures RTD Messages This section contains the Runtime Diagnostic (RTD) error messages. Action If someone is reconfiguring the interface or device at the other side of the interface. if there is a port anywhere in the switched domain that is looped back to itself. [chars] is the interface. if no one is manipulating the interface or device at the other end of the interface. Note that the show cdp neighbors command is useful in determining the next switch. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide A-10 78-6511-05 . when a switched network reconfigures. Repeat this procedure until the port is found that is receiving what it is transmitting. addresses learned on one port are relearned on a different port. This might be the result of reconfiguring the port. and [dec] is the number of addresses being learnt. MAC addresses are learned once on a port. RTD-1-LINK_FLAP [chars] link down/up [dec] times per min Explanation This message means that an excessive number of link down-up events has been noticed on this interface: [chars] is the interface. addresses will jump back and forth between the real port and the port that is in the path to the looped back port. it is likely that the Ethernet transceiver at one end of the link is faulty and should be replaced. However. In this message.

STORM_CONTROL-2-SHUTDOWN Explanation This messages means that excessive traffic has been detected on a port that has been configured to be shut down if a storm event is detected Action Once the source of the packet storm has been fixed. re-enable the port by using port-configuration commands. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 A-11 .Appendix A System Error Messages Error Message and Recovery Procedures Storm Control Messages This section contains the Storm Control error message.

Appendix A System Error Messages Error Message and Recovery Procedures Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide A-12 78-6511-05 .

4-7 MIBs files 4-7 A objects 4-6 aaa (authentication. variable field A-3 hex. 6-67 address abbreviations count. variable field A-3 chars. secure 7-15 char. Catalyst 2900 XL 1-12 MIB objects 4-6. authorization. variable field A-3 inet. variable field A-3 accessing CMS 2-35 command modes 3-3 console port access 4-3 VLAN to database 8-33 resolution 6-45 security violations 7-14 see also addresses addresses dynamic accelerated aging 6-26 aging time 6-57 default aging 6-26 HTTP access 4-5 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 IN-1 .I N D E X member switches 8-35 Numerics MIB files 4-7 1000BASE-T module. variable field A-3 dec. and accounting) variables 4-7 Telnet access 4-4 configuring 6-67 accounting in TACACS+ 6-61 managing 6-61 adding aaa accounting command 6-66 secure addresses 6-58 aaa authorization command 6-65 static addresses 6-59 aaa authorization exec tacacs+ local command 6-65 switches to cluster 5-14 aaa new-model command 6-64.

6-59 managing 6-45 removing 6-60 Address Resolution Protocol (ARP) see ARP table asymmetric digital subscriber line see ADSL ATM ports duplex and speed 7-2 address table aging time. VTP 8-15 MAC aging. configuring 6-57 trunks and other features 8-37 dynamic addresses. accelerating 6-26 adding secure 6-58 aging time. in RMON 4-6 discovering 6-45. managing 6-56 American National Standards Institute secure see ANSI adding 6-58 described 6-56. TACACS+ 6-61 automatic discovery.Index described 6-56 ADSL 1-6 removing 6-58 advertisements. 6-56 allowed-VLAN list 8-40 tables. cluster candidates 5-4 autonegotiation connecting to devices without 7-2 mismatches 9-3 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide IN-2 78-6511-05 . changing address 6-57 aging time 6-57 alarms group. removing 6-58 VLAN membership 8-7 MAC 6-56 authentication secure addresses adding 6-58 removing 6-59 static addresses adding 6-59 removing 6-60 administrative information. displaying 5-19 NTP 6-18 TACACS+ 6-61 authorization. 6-58 removing 6-59 static ANSI 1-6 Plan 998 7-23 AppleTalk Remote Access (ARA) 6-65 Apply button 2-33 adding 6-59 ARP table configuring (EtherChannel) 6-61 address resolution 6-45 described 6-56.

4-1. 7-22 Cisco Access Analog Trunk Gateway 1-18 Cisco Access Digital Trunk Gateway 1-18 C Cisco CallManager software 1-16. UplinkFast 6-26 Catalyst 3524-PWR XL 7-17 cautions xviii Cisco LRE 48 POTS Splitter (PS-1M-LRE-48) 1-6. configuring 6-18 discovering candidates with 5-4 broadcast messages. 2-35. 4-8 characteristics 5-3 Class of service suggested 5-14 see CoS why not added 9-8 cascaded configuration. 5-1 Cisco. redundant 5-5 see CDP Cancel button 2-33 Cisco Group Management Protocol candidate pop-up menu see CGMP Cluster Builder 2-29 Cisco IP Phones 1-16 candidates adding 5-15 automatically discovering 5-4 changing management VLAN for 8-5 Cisco SoftPhone software 1-16 CiscoWorks 2000 1-8. 1-20 CLI 1-7 accessing 3-8 command modes 3-2 error messages 3-7 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 IN-3 .Index caveats B password and privilege level 5-9 bandwidth. graphing 2-9. CMS window 2-33 Cisco 575-LRE CPE 1-6. configuring for 6-18 broadcast storm control CGMP 1-2 controlling management packets with 6-46 disabling 7-5 removing router ports 6-48 enabling 7-4 see also Fast Leave broadcast traffic and protected ports 7-13 chassis system error messages A-5 browser configuration 2-1.com xxii buttons. 2-20 CDP 1-3 BPDU message interval 6-40 configuring 6-22 broadcast client mode. 1-18 Cisco Discovery Protocol cabling.

VTP 8-14 Cluster Builder candidate pop-up menu 2-29 illustrated 5-16 link pop-up menu 2-30 member pop-up menu 2-29 menu bar 2-26 overview 2-2. standby groups accessing 5-13 adding switches to 5-14 automatic discovery 5-4 candidate and cluster member 5-3 command switch characteristics 5-2 configuring 5-13 described 5-2 disqualification code 9-8 Gigabit Ethernet. illustrated 6-27 inventory. displaying 5-19 LRE profile considerations 5-13. 7-25 management VLAN. 2-3 overview 3-1 pop-up menus 2-18. 2-7 toolbar icons 2-17 cluster member characteristics 5-3 Cluster Membership Protocol see CMP system error messages A-5 clusters.Index IOS Release 12. 2-19 saving changes 3-10 port pop-up menu 2-18 using 3-1 toolbar 2-17 client mode.0 documentation xvi. 3-1 menu bar 2-14 managing cluster members with 5-21 overview 2-2. 2-21 polling interval 2-26 pop-up menus 2-29. changing 8-4 managing 5-21. member switches. switch see also candidates. command switch. 5-22 overview 5-1 planning considerations 5-4 host names 5-10 IP addresses 5-8 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide IN-4 78-6511-05 . 2-30 starting 2-17 toolbar 2-27 toolbar icons 2-27 topology 2-24 device icon colors 2-24 device icons 2-24 device labels 2-25 link icons 2-25 Cluster Management Suite 1-7 see CMS 2-1 Cluster Manager cluster tree 2-6 device pop-up menu 2-19 front-panel image 2-5.

3-3 toolbar icons 2-27 commands topology 2-24 aaa accounting 6-66 device icon colors 2-24 device icons 2-24 aaa authorization 6-65 aaa authorization exec tacacs+ local 6-65 device labels 2-25 abbreviating 3-4 link icons 2-25 copy running-config startup-config 9-10 CMP system error messages A-5 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 IN-5 . 2-21 see CLI toolbar 2-27 command modes 3-2.Index LRE profiles 5-13 CMS management VLAN 5-11 accessing 2-35 NAT commands 5-12 device labels 2-25 network port 5-12 features 2-2 passwords 5-8 link icons 2-25 SNMP community strings 5-10 overview standby command switches 5-5 privilege level 6-16 planning considerations. switch-specific features 5-13 redundancy 5-17 requirements 2-35 saving configuration changes 2-37 topology 2-24 removing switches from 5-14 requirements 5-2 device icon colors 2-24 device icons 2-24 standby command-switch characteristics 5-3 cluster tree 2-6 troubleshooting CMS session 9-5 window components 2-31 icon colors 2-6 buttons 2-33 icons 2-6 host name list 2-32 Cluster View lists 2-32 device pop-up menu 2-28 displaying 9-8 online help 2-33 tabs 2-32 interface 2-21 command-line error messages 3-7 menu bar 2-26 command-line interface overview 2-2.

5-17 no 3-5 see also candidates. 9-22 VTP version 8-19 from failure without HSRP 9-22 saving to Flash memory 9-10 from lost member connectivity 9-13 VTP. member switches port block 8-38 command variables. 5-22 resetting to defaults 3-5 switch clusters 5-10 show cluster members 5-21 compatibility spanning-tree root guard 6-45 cluster 5-4 stp-list 6-24 feature 9-2 undoing 3-5 config trap 6-19 usage basics 3-2 configuration command switch conflicts. VMPS database 8-54 characteristics 5-2 files. listing 3-6 preempt 5-18 community strings rcommand 5-21 configuring 5-10. 3-6 requirements 5-2 name 5-18 standby 5-5.Index default 3-5 redundant (standby) 5-17 dir flash 9-9 replacing getting help (?) 3-5 with another switch 9-19 help 3-5 with cluster member 9-15 list of available 3-4. 6-19 redisplaying 3-5 SNMP 5-10. managing 9-2. saving to an external server 9-9 configuration conflicts 9-13 guidelines defined 5-2 port 7-2 enabling 5-14 VLANs 8-28 privilege levels 5-21 VMPS 8-56 recovery VTP 8-18 from failure 5-7. default 8-20 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide IN-6 78-6511-05 . 9-14. 9-13 and management 4-6 default VLAN 8-28 and managing with SNMP 5-22 file.

6-19 static addresses (EtherChannel) 6-61 Cross-stack UplinkFast 6-31 STP 6-24 date and time 6-17 Cross-stack UplinkFast 6-31 daylight saving time 6-17 port priorities 8-48 DNS 6-8 root guard 6-44. saving duplex 7-2.Index configuration changes. 7-3 clusters 5-13 standby command groups 5-17 community strings 5-10. DHCP 6-10 passwords 6-15 configuring ports 802. 7-3 CLI 3-10 dynamic ports on VMPS clients 8-58 CMS 2-37 dynamic VLAN membership 8-57 configuration examples. network 1-10 flooding controls 7-4 collapsed backbone and switch cluster 1-16 flow control 7-3 design concepts hello time 6-40 cost-effective wiring closet 1-12 hops 6-23 high-performance workgroup 1-12 inline power 7-21 network performance 1-10 IP information 6-2 network services 1-11 IP Phone 7-18 redundant Gigabit backbone 1-12 load sharing 8-48 hotel network 1-20 login authentication 6-64 large campus 1-18 management VLAN 8-6 multidwelling configuration 1-23 native VLANs 8-43 small to medium-sized network 1-14 NTP 6-17 configuration files.1p class of service 8-44 protected 7-13 AAA 6-67 privilege levels 6-15 aging time 6-57 redundant clusters 5-17 broadcast messages 6-18 RMON groups 4-6 broadcast storm control 7-4 SNMP 6-18 CDP 6-22 speed 7-2. 6-45 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 IN-7 .

7-10 device pop-up menu 2-19 configuring 8-44 priority 7-19 CPE 1-6. 9-13 database. 8-28. changing 4-9 text xviii deleting VLAN from database 8-34 copy running-config startup-config command 9-10 CoS destination-based forwarding 7-11 destination-based port groups 6-61. configuration 9-2. 8-20 see CPE VTP client mode 8-22 VTP server mode 8-21 VTP transparent mode 8-10.Index UplinkFast 6-26 switches CSUF 6-31 configuring 6-37 member 5-21 connecting stack ports 6-35 TACACS+ 6-61 fast convergence causes 6-33 trap managers 6-19 limitations 6-35 trunk port 8-38 overview 6-31 trunks 8-37. 8-32 customer premises equipment VTP 8-18. VTP 8-27. 1-20. resetting to 3-5 for examples xviii default settings. 8-32 consistency checks in VTP version 2 8-16 date. setting 6-17 console port daylight saving time 6-17 access 4-3 default configuration connecting to 3-8 VLANs 8-28 default settings 4-3 VMPS 8-57 conventions VTP 8-20 command xviii defaults. 8-23 D conflicts. 8-39 Current Multicast Groups table 6-48 VLANs 8-1. 7-22 Cluster Manager 2-19 Cluster View 2-28 VSM 2-19 Cross-stack UplinkFast see CSUF Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide IN-8 78-6511-05 .

3-1 configuring relay device 6-9 documentation. 8-18 digital telephone networks 1-6 Domain Name System server see DNS dir flash command 9-9 domains for VLAN management 8-13 disabling broadcast storm control 7-5 DTP 8-39 CGMP Fast Leave 6-47 duplex network port 7-8 configuration guidelines 7-2 port security 7-15 configuring 7-2. 7-3 SNMP 6-18 settings. CD-ROM Client Request Process 6-5 Catalyst 2900 XL and Catalyst 3500 XL xix configuring DHCP server 6-6 Cisco xx configuring domain name and DNS 6-8 documentation. 6-4 documentation. ATM port 7-2 STP 6-25 duplex mode LED 2-10 Switch Port Analyzer (SPAN) 7-16 dynamic-access ports trunking on a port 8-40 described 8-7 trunk port 8-40 limit on number of hosts 8-61 VTP 8-23 VLAN membership combinations 8-9 VTP version 2 8-25 DISL 8-39 disqualification code 9-8 DNS configuring 6-8 described 6-8 enabling 6-8 dynamic addresses see addresses Dynamic Host Configuration Protocol see DHCP Dynamic ISL see DISL dynamic ports. IOS Release 12.Index DHCP 1-3.0 xvi. related xix configuring TFTP server 6-7 domain name example configuration 6-12 configuring 6-8 obtaining configuration files 6-10 described 6-8 overview 6-4 specifying 6-8. configuring 8-58 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 IN-9 .

Index dynamic port VLAN membership port security 7-14. 7-15 configuration example 8-61 SNMP 6-18 configuring 8-58 SPAN 7-16 example 8-61 STP Port Fast 6-42 overview 8-53 UplinkFast 6-30 reconfirming 8-59 VTP pruning 8-25 troubleshooting 8-61 VTP version 2 8-24 VMPS database configuration file 8-54 Dynamic Trunk Protocol encapsulation 8-44 environment system error messages A-6 error messages 3-7 see DTP dynamic VLAN membership 8-57 EtherChannel port groups 7-10 configuring static address for 6-61 creating 7-12 E Ethernet link. in RMON 4-6 examples conventions for xviii network configuration 1-10 DNS 6-8 Fast Leave 6-47 extended discovery 6-22 network port 7-7 NTP authentication 6-18 Port Fast 6-42 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide IN-10 78-6511-05 . 7-25 egress port scheduling 8-45 Ethernet MANs 1-23 eligible switches 5-17 Ethernet VLAN. LRE ports 7-22. defaults and ranges 8-29 enable password ETSI 1-6 see passwords enable secret password see passwords Plan 997 7-23 European Telecommunication Standards Institute see ETSI enabling broadcast storm control 7-4 CGMP Fast Leave 6-47 command switch 5-14 events group.

illustrated 6-27 flooded traffic. creating 7-10 front-panel images 2-7 Fast Ethernet trunks 8-36 Cluster Manager 2-5 Fast Leave VSM 2-4 defined 6-46 FTP. 8-1 1000BASE-SX module 1-12 conflicting port 9-2 1000BASE-T module 1-12 default settings 4-9 1000BASE-ZX module 1-12 incompatible 9-2 GigaStack 1-12 IOS 1-1 get-next-request operation 4-8 feedback to Cisco Systems.Index port groups 7-10 F restrictions 7-11 facility codes A-2 resuming 7-7 description A-2 source-based. illustrated 7-11 table A-2 see also broadcast storm control fan fault indication 2-6 forwarding. accessing MIB files Gigabit Ethernet Flash memory. accessing MIB files 4-7 disabling 6-47 enabling 6-47 FDDI-Net VLAN defaults and ranges 8-30 G FDDI VLAN defaults and ranges 8-29 GBICs features 1000BASE-LX/LH module 1-12 configuration conflicts between 7-1. configuring 7-3 settings 7-2 forwarding trunks 8-36 controlling (SNMP) 5-22 delay 6-38. reducing 7-6 ports. 9-10 clusters. configuring flow control on 7-3 flooding controls. web xxi get-request operation 4-8 File Transfer Protocol get-response operation 4-8 see FTP. configuring 7-4 port settings 7-2 flow control. static address 6-59 Fast EtherChannel port groups. 6-41 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 IN-11 . files in 9-9.

getting 2-17.0 documentation xvi. 3-5 see ISDN history group. configuring 6-23 host name list 2-32 IOS supported 1-7 Inter-Switch Link see ISL host names abbreviations appended to 5-18 inventory. 3-1 Hot Standby Router Protocol IP addresses and admittance to standby groups 5-3 see HSRP HP OpenView 1-8 candidate 5-3 HSRP 5-5 discovering 6-45 HTTP access 4-5 management VLAN 5-11. 2-20 interaction with other features 8-37 poll result 4-8 native VLAN for untagged traffic 8-43 overview 8-36 IEEE 802.1p 7-17 global configuration mode 3-4 IEEE 802.1Q trunks 8-37 H ingress port scheduling 8-45 hello BPDU interval 6-40 inline power. displaying 5-19 switch clusters 5-10 IOS command-line interface to address mappings 6-8 see CLI hosts.1Q configuration considerations 8-37 graphs bandwidth 2-9. configuring 7-21 hello time inline power LED 2-13 changing 6-40 inline power port mode LED 2-10 defined 6-38 Integrated Services Digital Network help. 8-4 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide IN-12 78-6511-05 .Index Gigabit Interface Converter I see GBICs GigaStack system error messages A-7 IEEE 802. in RMON 4-6 interface configuration mode 3-4 hold-time. limit on dynamic ports 8-61 IOS Release 12. modifying 6-48 interfaces hops.

2-12. controlling 6-46 RPS 600 2-8 speed mode 2-10 IP Phone calls 7-17 STAT mode 2-10 configuring 7-18 System 2-7 legend 2-17 sound quality 7-17 IPX server time-out. 5-1 lists 2-32 load sharing STP. displaying 5-20 link pop-up menu Cluster Builder 2-30 J link system error messages A-8 Java plug-in configuration 2-1. described 8-46 using STP path cost 8-50 using STP port priorities 8-47 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 IN-13 . 2-13 configuring 6-2 redundant power system 2-8 displaying 5-19 RPS 2-8 RPS 300 2-9 removing 6-2 IP management packets. 2-35.Index point of access 5-2 L in redundant clusters 5-5 LEDs removing 6-2 switch clusters 5-8 duplex mode 2-10 see also IP information front-panel images 2-7 IP connectivity to the switch 4-2 LINE PWR mode 2-10 IP information LRE mode 2-10 assigning 6-2 port 2-9. and Port Fast 6-42 Cluster Builder and Cluster View 2-27 ISDN 1-6 VSM and Cluster Manager 2-16 line configuration mode 3-4 ISL 1-4 interaction with other features 8-37 LINE PWR mode LED 2-13 overview 8-36 link information. 4-1. 2-11.

6-56 LRE ports MAC address tables. 8-4 LRE link switch clusters 5-11 description 7-22 MANs. managing 6-56 assigning a private profile 7-28 assigning a public profile 7-27 management options 1-7 benefits assigning the default profile 7-28 clustering 1-8 description 7-22 CMS 1-8 Ethernet link CDP enabled 7-26 description 7-22. configuring 6-64 lre profile global command 7-27 Long-Reach Ethernet lre shutdown command 7-26 see LRE technology LRE technology 1-6. understanding 8-4 flow control 7-25 changing 5-12. displaying 5-19 lre profile command 7-28 login authentication.Index location of switches. 8-4. 7-25 CLI 3-1 CMS 2-1 management VLAN duplex mode 7-25 changes. 8-5 speed 7-25 configuring 8-6 statistics 7-26 IP address 5-11. 7-22 LRE-10 private profile 7-24 LRE-15 private profile 7-24 LRE-5 private profile 7-24 LRE link M MAC addresses see LRE ports adding secure 6-58 LRE link system error messages A-8 aging time 6-57 LRE mode LED 2-10 discovering 6-45. Ethernet 1-23 statistics 7-25 map preventing loss of data 7-25 profiles 7-22 switch clusters 5-13 see topology member pop-up menu Cluster Builder 2-29 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide IN-14 78-6511-05 .

8-12 mini-point-of-presence described 8-11 see POP VLAN membership combinations 8-8 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 IN-15 .Index membership mode. accessing files 4-7 objects 4-6 variables 4-7 VTP 8-26 multicast groups described 6-46 removing 6-48 multicast packets see flooding controls multicast traffic and protected ports 7-13 Multicast VLAN Registration see MVR multi-VLAN ports microfilters. phone 1-20 assigning to VLANs 8-10. autonegotiation 9-3 member switches mnemonic code A-3 accessing 8-35 Mode button 2-9 adding model numbers. displaying 5-19 with Cluster Builder 5-14 modes assigning host names to 5-10 command 3-3 defined 5-2 VLAN port membership 8-7 displaying inventory of 5-19 VTP see VTP modes managing 5-21 passwords. inherited 5-8 Modify button 2-33 recovering from lost connectivity 9-13 modules. displaying 5-19 menu bar Cluster Builder 2-26 module system error messages A-9 monitoring Cluster Manager 2-14 ports 7-16 Cluster View 2-26 traffic 7-16 VSM 2-14 VMPS 8-60 messages CLI error 3-7 system error A-1 message severity levels description A-3 table A-3 MIBs. VLAN port 8-7 mismatches.

Index MVR 4-13. 6-49 configuring 6-54 parameters 6-53 multidwelling configuration 1-23 small to medium-sized network 1-14 Network Management System guidelines 6-51 see NMS limitations 6-52 network ports overview 6-49 disabling 7-8 enabling 7-7 switch clusters 5-12 N and trunks 8-37 name command 5-18 NAT commands cluster considerations 5-12 Network Time Protocol see NTP NMS 4-7 native VLANs 8-43 no commands. using 3-5 NCPs 6-65 no lre profile global command 7-27 Network Address Translation nonhomologated POTS splitter see NAT network configuration examples 1-10 Network Control Protocols (NCPs) 6-65 network examples 1-10 collapsed backbone and switch cluster 1-16 design concepts cost-effective wiring closet 1-12 high-performance workgroup 1-12 see Cisco LRE POTS Splitter (PS-1M-LRE-48) NTP authentication 6-18 broadcast-client mode 6-18 client 6-17 configuring 6-17 described 6-17 network performance 1-10 network services 1-11 O redundant Gigabit backbone 1-12 hotel network 1-20 large campus 1-18 OK button 2-33 online help 2-33 overheating indication. switch 2-6 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide IN-16 78-6511-05 .

7-10 LRE profiles 5-13 forwarding 7-10 management VLAN 5-11 restrictions on forwarding 7-11 NAT commands 5-12 source-based 6-61. 7-10 network port 5-12 see also ports port membership modes. 8-38 TACACS+ server 6-61 port-connection information. switch clusters 5-4 and trunks 8-38 configuring static addresses (EtherChannel) 6-61 host names 5-10 creating EtherChannel 7-10. VLAN 8-7 passwords 5-8 SNMP community strings 5-10 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 IN-17 . 6-43. 7-12 IP addresses 5-8 destination-based 6-61. graphing 4-8 passwords POP 1-23 candidate switch 5-16 pop-up menus changing 6-15 Cluster Builder link 2-30 community strings 6-19 Cluster Builder member 2-29 recovery of 9-22 Cluster Manager device 2-19 setting 6-15 Cluster Manager port 2-18 switch clusters 5-8 port block command 7-13. displaying 5-20 VTP domain 8-18 Port Fast patch panel 1-20 enabling 6-42 path cost 6-42.Index standby command switches 5-5 P switch-specific features 5-13 packets 7-6 polling interval controlling management (CGMP) 6-46 Cluster Builder 2-26 see also traffic switch image 2-15 parallel links 8-46 poll results. 8-50 STP parameter 8-56 PBX 1-20 port groups plain old telephone service see POTS splitters planning considerations.

8-8. resuming 7-7 power. 8-47 ports protected 7-13 ATM secure 7-15. 8-35 trunk 8-38 STP states 6-41 dynamic trunk configuring 8-58 configuring 8-38 see also dynamic port VLAN membership disabling 8-40 dynamic access trunks 8-7. inline 7-21 Gigabit Ethernet power detection on the Catalyst 3524-PWR 7-21 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide IN-18 78-6511-05 .Index port modes 2-9 changing 2-9 LEDs 2-10 configuring flow control on 7-3 settings 7-2 LRE 7-22 port-monitoring conflicts with trunks 8-37 monitoring 8-37 port pop-up menu 2-18 multi-VLAN 8-7. 8-10. conflicting 9-2 homologated 1-20 flooded traffic 7-6 nonhomologated 1-20 forwarding. 8-37 duplex and speed 7-2 security trunks and other features 8-37 described 7-14 VLAN membership 8-7 disabling 7-15 configuration guidelines 7-2 enabling 7-15 configuring speed. 8-36 hosts on 8-61 VLAN assignments 8-10. 8-10. 8-12 Cluster Manager 2-18 network 8-37 VSM 2-18 priority 6-43. setting and checking 7-2 protected 7-13 static-access 8-7. 8-11. 8-44. 8-35 mode 8-7 see also port groups and VLAN combinations 8-9 dynamic VLAN membership reconfirming 8-59 port scheduling 8-45 port security system error messages A-9 POTS splitters 1-6 features.

LRE 7-22 considerations 7-24 default 7-24 assigning 7-28 Q QoS egress port scheduling 8-45 ingress port scheduling 8-45. displaying switch 5-19 see PBX private mode profiles 7-23 LRE-10 7-24 protected ports 1-2. 7-23 privilege levels publications. 1-18.Index preempt command 5-18 private 7-23 priority assigning 7-28 modifying switch 6-39 LRE-10 7-24 overriding 7-19 LRE-15 7-24 port LRE-5 7-24 described 8-44 public 7-23 modifying 6-42. 7-13 pruning LRE-15 7-24 enabling on a port 8-42 LRE-5 7-24 enabling on the switch 8-25 private VLAN edge ports overview 8-17 pruning-eligible list 8-42 see protected ports privileged EXEC mode 3-3 PSTN 1-6. 5-21 PUBLIC-ETSI 7-24 setting 6-15 specifying 6-15 Public Switched Telephone Network see PSTN profiles. 1-20. 8-46 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 IN-19 . 6-43 assigning a public profile 7-27 standby group member 5-17 PUBLIC-ANSI 7-24 private branch exchange PUBLIC-ETSI 7-24 properties. related xix command switch 5-21 public mode profiles 7-23 inherited 5-8 PUBLIC-ANSI 7-24 mapping on member switches 5-9.

6-60 retry count. displaying 5-19 server. 7-15 maximum secure address count 7-15 and trunks 8-37 dynamic address entries 6-58 IP information 6-2 multicast groups 6-48 secure addresses 6-59 static addresses 6-59. switch software 4-2 removing 6-59 remote devices without autonegotiation. connecting to 7-2 remote monitoring see RMON remove vlan-list parameter 8-40 removing secure ports address-security violations 7-14 disabling 7-15 enabling 7-14. address 7-14 Serial Line Internet Protocol see SLIP serial numbers. modifying 6-48 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide IN-20 78-6511-05 . changing 8-59 RTD error messages A-10 recovery procedures 9-13 Runtime Diagnostic redisplaying commands 3-5 see RTD error messages redundancy cluster 5-17 STP 6-25 S path cost 8-50 Save Configuration window 2-17 port priority 8-47 secure address count 7-15 UplinkFast 6-28 secure addresses redundant power system 2-8 adding 6-58 relay device. domain name 6-8 router hold-time. changing 8-60 RMON. supported groups 4-6 root guard 6-44. configuring 6-9 described 6-58 releases. 6-45 security port 7-14 TACACS+ 6-61 violations.Index RPS LED 2-8 R RPS 300 2-9 rcommand 5-21 RPS 600 2-8 reconfirmation interval.

VTP 8-14 configuring for single switches 6-18 servers. 6-4 set-request operation 4-8 enabling and disabling 6-18 settings management. BOOTP 1-3. 7-28 show controllers lre profile mapping 7-28 show controllers lre profile mapping command 7-27 Simple Network Management Protocol VLAN considerations 8-19 see also upgrading software releases 4-2 Software Upgrade window 2-17 source-based forwarding 7-11 disabling 7-16 SNMP accessing MIB variables with 4-7 switch clusters 5-10 version numbers. displaying 5-19 SPAN 7-16 SLIP 6-65 configuring 6-19 joining standby groups 5-3 source-based port groups 6-61.Index server mode. 7-10 see SNMP community strings software enabling 7-16 ports. 7-27. configuring 6-19 STP 6-27 trap types 6-19. television 1-20 severity levels recovery procedures 9-25 description A-3 requirements for table A-3 changing management VLAN 5-11 show cluster members command 5-21 show controllers ethernet-controller command 7-26 show controllers lre commands 7-25. 6-20 STP default 6-26 SNMP Configuration window 2-17 set-top box. 7-3 network management platforms 4-6 Gigabit Ethernet port 7-2 RMON groups 4-6 speed 7-3 trap managers. changing 4-9 managing clusters with 5-22 duplex 7-2. restrictions 9-2 Spanning Tree Protocol see STP Spanning Tree Protocol window 2-17 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 IN-21 . using 4-6 default.

unpredictable 8-11 UplinkFast 6-28.Index spanning-tree rootguard command 6-45 configuring 6-24. in RMON 4-6 STAT mode LED 2-10 port grouping parameters 7-11. 5-17 implementation type 6-39 priority. configuring 5-17 load sharing standby command switches overview 8-46 characteristics 5-3 using path costs 8-50 planning considerations 5-5 using port priorities 8-47 static-access ports assigning to VLAN 8-10. 8-48 port states 6-41 redundant connectivity 6-25 redundant links with UplinkFast 6-28 root guard 6-44. 6-30 BPDU message interval 6-40 VLAN parameters described 6-38 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide IN-22 78-6511-05 . VTP 8-26 statistics group. 8-38 port priority 6-43. 7-3 considerations for using STP instances 6-24 speed mode LED 2-10 disabling 6-25 Standby Command Configuration window 5-18 forwarding delay timer 6-41 standby command group hello BPDU interval 6-40 configuring 5-5. setting 7-2. 8-35 parameters 6-24 path cost described 8-10 changing 6-43 VLAN membership combinations 8-8 configuring 8-50 static addresses Port Fast adding 6-59 enabling 6-42 configuring for EtherChannel port groups 6-61 mode 8-56 described 6-56. 6-27 STP implementation. changing 6-39 storm control system error messages A-11 supported number of spanning-tree instances 6-24. 8-2 STP switch priority 6-39 behavior. 6-59 removing 6-60 see also static address static address forwarding 6-59 static address forwarding restrictions 7-11 statistics. 6-45 settings 6-26. 6-26 speed.

troubleshooting 9-10 candidate and cluster member characteristics 5-3 system date and time 6-17 system error messages A-1 command switch characteristics 5-2 chassis A-5 displaying inventory 5-19 CMP A-5 displaying link information 5-20 environment A-6 overview 5-1 GigaStack A-7 planning considerations 5-4 how to read A-2 host names 5-10 link A-8 IP addresses 5-8 list of A-5 LRE profiles 5-13 LRE link A-8 management VLAN 5-11 module A-9 NAT commands 5-12 port security A-9 network port 5-12 recovery procedures A-5 passwords 5-8 RTD A-10 SNMP community strings 5-10 storm control A-11 standby command switches 5-5 switch-specific features 5-13 traceback reports A-4 System LED 2-7 standby command switch characteristics 5-3 troubleshooting 9-8 verifying 5-19 switch images 2-7 LEDs 2-7 polling interval 2-15 Switch Port Analyzer T tables message severity levels A-3 variable fields A-3 tabs 2-32 see SPAN switchport command 8-39 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 IN-23 . configuring 7-1 STP port states 6-41 switch software releases 4-2 SunNet Manager 1-8 switch-specific features in switch clusters 5-13 switch clusters switch upgrades.Index stp-list parameter 6-24 switch ports.

8-31 disabling 8-40 toolbar trunks Cluster Builder 2-27 allowed-VLAN list 8-40 Cluster Manager 2-17 ATM 8-37 blocking unknown packets on 8-38 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide IN-24 78-6511-05 . 6-67 reducing flooded 7-4. 8-23 trap managers access 4-4 accessing management interfaces 3-8 adding 6-19 accessing the CLI 1-7 configuring 6-19 from a browser 3-9 traps 4-8. VTP 8-14. 7-7 tacacs-server timeout command 6-63 transmit queue 8-45 Telnet transparent mode.Index TACACS+ Cluster View 2-27 AAA accounting commands 6-66 VSM 2-17 AAA authorization commands 6-65 topology. and protected ports 7-13 tacacs-server host command 6-62. configuring 6-7 TrBRF VLAN defaults and ranges 8-30 time TrCRF VLAN defaults and ranges 8-31 daylight saving 6-17 troubleshooting 9-1 setting 6-17 CMS sessions 9-5 zones 6-17 switch clusters 9-8 TLV support 8-16 switch upgrades 9-10 Token Ring VLANs with CiscoWorks2000 4-8 overview 8-27 trunk ports TrBRF 8-16. 6-63 monitoring 7-16 tacacs-server retransmit command 6-63. 8-30 configuring 8-38 TrCRF 8-16. CMS 2-24 configuring 6-61 traceback reports A-4 initializing 6-64 traffic server. 6-19 TFTP server. creating 6-62 blocking flooded 7-6 starting accounting 6-66 forwarding.

unknown see VSM VLAN see flooding controls unicast traffic and protected ports 7-13 adding to database 8-33 UniDirectional Link Detection modifying 8-34 see UDLD port membership modes 8-7 Unrecognized Type-Length-Value see TLV support 8-16 trunks. 8-37 enabling 6-30 interacting with other features 8-37 redundant links 6-28 ISL 8-36 URLs. 6-56 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 IN-25 .1Q 8-36.Index configuration conflicts 8-37 configuring 8-39 upgrading software 4-1 VLAN considerations 8-19 disabling 8-40 UplinkFast Gigabit Ethernet 8-36 configuring 6-26 IEEE 802. discovering 6-45. Cisco xx load sharing using user EXEC mode 3-3 STP path costs 8-50 User Settings window 2-17 STP port priorities 8-47 native VLAN for untagged traffic 8-43 overview 8-36 parallel 8-50 V variable fields pruning-eligible list 8-42 definition A-3 VLAN. overview 8-36 table A-3 VLAN membership combinations 8-9 TTY traps 6-19 version-dependent transparent mode 8-16 virtual IP address HSRP 5-5 standby group member 5-18 U see also IP addresses UDLD 7-9 Visual Switch Manager unicast and multicast packets. overview 8-36 VLAN database mode 3-3 VLAN ID.

1Q considerations 8-37 VMPS adding to database 8-33 administering 8-60 aging dynamic addresses 6-26 configuration guidelines 8-56 allowed on trunk 8-40 database configuration file example 8-54 changing 8-34 default configuration 8-57 configuration guidelines 8-28 dynamic port membership configuring 8-1. configuring 8-43 number supported 8-3 VLAN membership overlapping 8-11 ATM port 8-7 overview 8-2 combinations 8-8 static-access ports 8-10. 8-35 confirming 8-59 STP parameters. 8-32 configuring 8-58 default configuration 8-28 example 8-61 deleting from database 8-34 overview 8-53 described 8-2 reconfirming 8-59 illustrated 8-2 troubleshooting 8-61 ISL 8-36 mapping MAC addresses to VLANs 8-52 MAC addresses 6-56 monitoring 8-60 modifying 8-34 overview 8-52 multi-VLAN ports 8-10. changing 6-38 modes 8-7 supported VLANs 8-3 port group parameters 7-11 Token Ring 8-27 traps 6-19 trunking 8-3 see also dynamic VLAN membership trunks configured with other features 8-37 VLAN Membership window 2-17 VLAN Query Protocol see VQP see also trunks VTP database and 8-27 VTP modes 8-14 VLANs see also management VLAN 802. changing 8-59 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide IN-26 78-6511-05 . 8-34. 8-12 reconfirmation interval.Index VLAN Management Policy Server see VMPS native.

8-21 voice VLAN transitions 8-14 transparent 8-10. 8-23 see VVID VQP 8-52 monitoring 8-26 VSM pruning device pop-up menu 2-19 enabling 8-25 front-panel image 2-4. changing 8-42 menu bar 2-14 statistics 8-26 overview 2-2. configuring 7-17 configuring 8-22 voice traffic 7-21 server 8-14. determining 8-19 version 1 8-16 VTP version 2 advertisements 8-15 configuration guidelines 8-18 configuration guidelines 8-19 configuring 8-20 disabling 8-25 consistency checks 8-16 enabling 8-24 database 8-27.Index reconfirming membership 8-59 described 8-12 retry count. 8-32 overview 8-16 default configuration 8-20 VLAN parameters 8-27 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 IN-27 . entering on client 8-57 domain names 8-18 Voice over IP domains 8-13 configuring 7-17 modes port configuration 7-18 client 8-14 voice ports configurations affecting mode changes 8-15 configuring VVID 7-20 voice ports. 8-14. 2-3 Token Ring support 8-16 port pop-up menu 2-18 transparent mode. configuring 8-23 privilege level 6-16 traps 6-19 toolbar 2-17 using 8-12 toolbar icons 2-17 version. 2-7 overview 8-17 home page 2-4 pruning-eligible list. changing 8-60 disabling 8-23 server address.

Index VVID 1-5. CMS 2-31 buttons 2-33 host name list 2-32 lists 2-32 online help 2-33 tabs 2-32 X Xmodem protocol 9-25 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide IN-28 78-6511-05 . 7-18 configuring 7-20 W warnings xviii window components.