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 .

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.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 .

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 .

It includes descriptions of the management interface options and the features supported by the switch software.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. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 xv . hereafter referred to as the switches. This guide also provides information about configuring the Cisco 575 Long-Reach Ethernet (LRE) customer premises equipment (CPE). • Start up information—This guide assumes you have assigned switch IP information and passwords by using the setup program. which is described in the release notes. as described in the release notes. you should be familiar with the concepts and terminology of Ethernet and local area networking. 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. Purpose This guide provides information about configuring and troubleshooting a switch or switch clusters. Before using this guide.

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

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

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

See the “Ordering Documentation” section on page xxi. Cisco IOS Release 12.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) (not orderable but is available on Cisco.Preface Related Publications Related Publications You can order printed copies of documents with a DOC-xxxxxx= number. which contains the documentation for all Cisco products and is shipped with all Cisco products.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. Cisco IOS Release 12. 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. This CD is not the same as the Cisco Documentation CD-ROM.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.

cisco.cisco. which contains only the Catalyst 2900 XL and Catalyst 3500 XL switch documents and related hardware documents. The CD-ROM package is available as a single unit or as an annual subscription.Preface Obtaining Documentation – 1000BASE-T Gigabit Interface Converter Installation Note (not orderable but is available on Cisco. This CD is not the same as the Catalyst 2900 XL and Catalyst 3500 XL Documentation CD.com • http://www-europe. Note This CD contains the documentation for all Cisco products and is shipped with all Cisco products. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide xx 78-6511-05 . The Cisco Documentation CD-ROM is updated monthly and may be more current than printed documentation.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. which ships with your product.com • http://www-china. World Wide Web You can access the most current Cisco documentation on the World Wide Web at the following sites: • http://www.cisco.com Cisco Documentation CD-ROM Cisco documentation and additional literature are available in a CD-ROM package.

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

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

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

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

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 1-1 .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. Note Table 4-2 on page 4-9 lists the defaults for all key features. This software also supports the Cisco 575 Long-Reach Ethernet (LRE) customer premises equipment (CPE). Table 1-1 describes the features supported in this release. It also includes references to where you can find additional information about each feature.0(5)WC(1).

software. such as Netscape Communicator or Microsoft Internet Explorer. • Note Hot Standby Router Protocol (HSRP) for command-switch redundancy See the “Advantages of Using CMS and Clustering Switches” section on page 1-8.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.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 browser requirements. monitoring. for – Unified configuration. Performance • Autosensing of speed on the 10/100 ports and autonegotiation of duplex mode on all switch ports for optimizing bandwidth • IEEE 802. 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. Refer to the release notes for the CMS and cluster hardware. – Automatic discovery of candidate switches and creation of clusters of up to 16 switches that can be managed through a single IP address. from anywhere in your intranet • Switch clustering technology. and software upgrade of multiple switches (refer to the release notes for a list of eligible cluster members). authentication. 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 . – Extended discovery of cluster candidates that are not directly connected to the command switch. routers. in conjunction with CMS.

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. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 1-3 . BOOTP is available in earlier software releases for this switch. see the “Management Options” section on page 1-7. • 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.

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. 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. adds. • Inter-Switch Link (ISL) and IEEE 802. Cross-Stack UplinkFast. VLAN Support • Note Depending on the switch model. traffic patterns. see the Table 8-1 on page 8-3.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. a switch can support up to 64 or 250 instances of STP (see Table 8-1 on page 8-3). 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 . and BackboneFast for fast convergence after a spanning-tree topology change and for achieving load balancing between redundant uplinks.1Q trunking protocol on all ports for simplified network moves. up to 64 or 250 port-based VLANs are supported for assigning users to VLANs associated with appropriate network resources. better management and control of broadcast and multicast traffic.1d Spanning Tree Protocol (STP) for redundant backbone connections and loop-free networks. and changes. and bandwidth For information about the maximum number of VLANs supported on each Catalyst 2900 XL and Catalyst 3500 XL switch.

notification.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. statistics. 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 events) of embedded remote monitoring (RMON) agents for network monitoring and traffic analysis • Syslog facility for logging system messages about authentication or authorization errors.and switch-level status • Switch Port Analyzer (SPAN) for complete traffic monitoring on any port • Four groups (history. voice. alarm. a proprietary feature for managing network security through a TACACS server Monitoring • Switch LEDs that provide visual management of port. 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. resource issues.Chapter 1 Overview Features Table 1-1 Features (continued) Quality of Service and Class of Service • IEEE 802. and time-out events Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 1-5 .

• CPE Ethernet ports and remote Ethernet devices. and digital telephone networks. such as a PC. – Configuration and monitoring of connections between • Switch LRE ports and the Ethernet ports on remote LRE customer premises equipment (CPE) devices. 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 . – Up to 15 Mbps of bandwidth to remote Ethernet devices at distances of up to 4921 ft (1500 m) on each switch LRE port. refer to the Cisco LRE 48 POTS Splitter Installation Note. such as the Cisco 575 LRE CPE. For information about the nonhomologated Cisco LRE 48 POTS Splitter (PS-1M-LRE-48). For information about the Cisco 575 LRE CPE. – 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). – Compliance with American National Standards Institute (ANSI) and European Telecommunication Standards Institute (ETSI) standards for spectral-mode compatibility with asymmetric digital subscriber line (ADSL). Integrated Services Digital Network (ISDN). refer to the Cisco 575 LRE CPE Hardware Installation Guide.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.

see Chapter 3. You can fully configure and monitor the switch and switch cluster members from the CLI.” • CLI—The switch IOS CLI software is enhanced to support desktop-switching features. Using CMS. For more information about CMS. see Chapter 2. you can fully configure and monitor a standalone switch.” Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 1-7 . “Getting Started with CMS. For more information about the CLI. a specific cluster member. 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. “Getting Started with the CLI. If you have specific network needs.and port-level settings. You can also display network topologies to gather link information and to display switch images to modify switch.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. CMS is already installed on the switch. or an entire switch cluster. 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. you can configure and monitor the switch—on an individual basis or as part of a switch cluster—through its various management interfaces.

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

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. see Chapter 5. and quality of service (QoS) configuration – Inventory and statistic reporting and link.” Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 1-9 .” For more information about switch clusters. “Getting Started with CMS. “Clustering Switches.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. and port LED colors on the images are similar to those used on the physical LEDs themselves. 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. STP. VLAN. The system. • Monitor real-time status of a switch or multiple switches from the LEDs on the front-panel images. For more information about CMS. see Chapter 2. redundant power system (RPS). You can also use the topology to quickly identify link information between switches.

• Use full-duplex operation between the switch and its connected workstations. it takes longer to send and receive data.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. • 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. 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. When you configure your network. workstations. consider the bandwidth required by your network users and the relative priority of the network applications they use. 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. and use VLANs and IP subnets to place the network resources in the same logical network as the users who access those resources most. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 1-10 78-6511-05 . • Use the Fast EtherChannel or Gigabit EtherChannel feature between the switch and its connected servers and routers. 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.

As your network traffic profiles evolve. • Use the Catalyst 2900 LRE XL switches to provide up to 15 Mb of IP connectivity over existing infrastructure (existing telephone lines). • Use VVIDs to provide a separate VLAN for voice traffic. High demand for protecting mission-critical applications • Use VLANs and protected ports to provide security and port isolation.Chapter 1 Overview Network Configuration Examples Bandwidth alone is not the only consideration when designing your network. 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.or low-priority. • Use switches that support at least two queues per port to prioritize voice and data traffic as either high. • Use VLAN trunks. Table 1-3 describes some network demands and how you can meet those demands. based on 802.1p/Q. consider providing network services that can support applications such as voice and data integration and security. 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 . Cross-Stack UplinkFast. • Use QoS to prioritize applications such as IP telephony during congestion and to help control both delay and jitter within the network. 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.

Using Gigabit modules on two of the switches. you can create backup paths between Catalyst 4908G-L3 switches. or Gigabit EtherChannel links. you can connect up to 432 users. the other can serve as a backup path. where the 1-Gbps connection is shared among the switches. Gigabit. Compare this with the switches in a GigaStack configuration. connect the bottom switch to the top switch to create a GigaStack loopback and enable Cross-Stack UplinkFast on the cross-stack Gigabit uplinks. use Gigabit modules to connect the switches directly to a backbone switch in a star configuration. You can configure the stack members and the Catalyst 3508G XL switch as a switch cluster to manage them through a single IP address. Each switch in this configuration provides users a dedicated 1-Gbps connection to network resources in the backbone. To enhance network reliability and load balancing for different VLANs and subnets. You can create backup paths by using Fast Ethernet. If one of the redundant connections fails. To preserve switch connectivity if one switch in the stack fails.808 ft (10 km) – 1000BASE-ZX GBIC: fiber connections of up to 328. 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. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 1-12 78-6511-05 .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. you can connect the Catalyst 2900 XL and Catalyst 3500 XL switches. again in a star configuration. you can have redundant uplink connections to a Gigabit backbone switch such as the Catalyst 3508G XL switch. When you use a stack of Catalyst 3548 XL switches.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. the second backbone switch preserves connectivity between the switches and network resources. • High-performance workgroup—For users who require high-speed access to network resources. If one of the backbone switches fails. or Fast EtherChannel. to two backbone switches.

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 .

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

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 .

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

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 . The IP phone can receive redundant power when it also is connected to an AC power source. 1900. 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. IP phones not connected to the Catalyst 3524-PWR XL switches receive power from an AC power source.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.

Because it can aggregate up to 130 Gigabit connections. and IP phone features and configuration. Cisco CallManager controls call processing. • Server farm that includes a call-processing server running Cisco CallManager software. 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. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 1-18 78-6511-05 . You can use the workgroup configurations shown in previous examples to create workgroups with Gigabit uplinks to the Catalyst 6500 switch. • 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. a Catalyst 6500 multilayer switch is used as the backbone switch. you can use switch clusters that have a mix of Catalyst 2900 XL and Catalyst 3500 XL switches. routing. For example.Chapter 1 Overview Network Configuration Examples Large Campus Configuration Figure 1-4 shows a configuration for a network of more than 1000 users.

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 .

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

• A router that provides Internet access to the premises. For example. and provisioning servers. The LRE ports support the same software features as the 10/100 ports. The aggregation switch can connect to • Accounting. Each switch also has a 10/100 connection to an aggregation switch. 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.Chapter 1 Overview Network Configuration Examples The Catalyst 2900 LRE XL switches are cascaded through the 10/100 switch ports. such as a Catalyst 3524 XL switch. You can also manage and monitor the individual CPEs through the Catalyst 2900 LRE XL switches to which they are connected. You can manage the switches through CMS as one or more switch clusters. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 1-21 .

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 .

All ports have CGMP enabled for multicast traffic management. 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 . ensuring that subscribers cannot view packets destined for other subscribers. STP root guard prevents unauthorized devices from becoming the STP root switch. The Catalyst 2900 LRE XL switches can then connect to another residential switch through a 10/100 connection. The protected port option provides security and isolation between ports on the switch. These switches are connected through 1000BASE-X GBIC ports.1Q trunks with the protected port and STP root guard options enabled. All ports on the residential switches are configured as 802.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). Catalyst 2900 LRE XL switches can also be used as residential switches for customers requiring connectivity through existing telephone lines. Higher VLAN and VLAN ID (4096) support is ideal for more security flexibility. 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. The resident switches can be Catalyst 2900 XL and Catalyst 3500 XL switches.

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. 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 .

For field-level descriptions of the CMS windows and for procedures for using CMS. and Catalyst 2820 switches. Catalyst 1900. Refer to the appropriate switch documentation for descriptions of the web-based management software used on other Catalyst desktop switches.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. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 2-1 . refer to the release notes. such as the Catalyst 2950. refer to the online help. Note This chapter describes the CMS interface used on the Catalyst 2900 XL and Catalyst 3500 XL switches.

cluster members. For more information about accessing CMS. VSM is the application for configuring and monitoring a standalone switch or a specific switch in a cluster. edge devices. When launched. You can toggle between Cluster Builder and Cluster View by selecting View > Toggle Views. The CMS windows use a consistent set of components (such as tabs. it displays a topology (network map) of the cluster command switch. cluster candidates. When launched. and so on). • Cluster Builder and Cluster View—Cluster Builder is the application from which you can create and modify a specific switch cluster. drop-down lists. When launched. 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. Each CMS window also includes comprehensive online help.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. which provides procedures for performing tasks from the window and high-level concepts. see the “Accessing CMS” section on page 2-35. regardless of the CMS application you use. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 2-2 78-6511-05 . Cluster View is the application from which you can display connected switch clusters and neighboring edge devices in your network. buttons. and the link speeds between all cluster members. You cannot display VSM from Cluster Manager. it displays a front-panel view of all switches in the cluster. it displays a front-panel view of a specific switch. It is also the application used to enable a cluster command switch.

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

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

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

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

Amber System is receiving power but is not functioning properly. making them as useful as the LEDs on the actual switches themselves.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. Table 2-2 System LED Color System Status Black (off) System is not powered up. 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. select System > User Settings from VSM or Cluster > User Settings from Cluster Manager. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 2-7 . To change the polling intervals. System LED The system LED shows whether the switch is receiving power and functioning properly. Table 2-2 lists the LED colors and their meanings. The LEDs on these images are updated at user-configurable polling intervals. Green System is operating normally.

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

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

100BASE-FX. Note SPEED or SPD When the LRE mode is active. (Catalyst 3524-PWR XL only) Default setting is auto. this LED shows the link speed between the remote CPE and Ethernet device. • 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. • Default setting is half-duplex on the LRE ports on the Catalyst 2900 LRE XL switches. 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. or 1000BASE-X switch ports. Note FDUP or DUPLX Duplex setting on the ports. Speed setting on the ports. Note On the Catalyst 2900 LRE XL switches. Default mode on these switches only. Default setting is auto. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 2-10 78-6511-05 .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. this LED shows the duplex mode used on the Ethernet link between the remote customer premises equipment (CPE) and Ethernet device. or the Ethernet link status on the remote CPE. LINE PWR Inline power setting on the Catalyst 3524-PWR XL 10/100 ports.

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

CRC errors. 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. 2. The Ethernet link default settings on the LRE ports are different than those on the 10/100 ports. Port was disabled by management. the 10/100 port LEDs continue to reflect Ethernet link status. Note DUPLX SPEED After a port is reconfigured. STAT 10/100 switch port or remote CPE Ethernet port is not forwarding. Refer to the “Troubleshooting LRE Port Configuration” section on page 9-4. Cyan (off) 10/100 switch port or remote CPE Ethernet port is operating at 10 Mbps. the LRE ports reflect the Ethernet link between the remote CPE and Ethernet device. Green Ethernet link present on the 10/100 switch port or on the remote CPE Ethernet port. or was blocked by STP. 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 in full-duplex mode. 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. Green 10/100 switch port or remote CPE Ethernet port is operating at 100 Mbps. Brown No link and port is administratively shut down. and alignment and jabber errors are monitored for a link-fault indication. Amber Link fault. Port LED turns green in approximately 10 seconds after the LRE port detects a connection to a Cisco 575 LRE CPE. by an address violation. such as a PC. In STAT mode. Blinking green Activity on the 10/100 switch port or on the remote CPE Ethernet port. In LRE mode. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 2-12 78-6511-05 . 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. 1. Port is transmitting or receiving data. Green LRE link present on the LRE port. See Table 2-5. Error frames can affect connectivity.

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

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

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

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

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

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

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

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

and leave the window open. After completing the form. buttons. and close the window. We appreciate and value your comments. • Dialog-specific help. When you close the pop-up. and close the window. available from the Help button on the VSM and Cluster Manager windows. the original window appears. available from all menu bars by selecting Help > Contents. click Submit to send your comments to Cisco. select Help > Contents. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 2-33 . You usually select an item from a list or table and click Modify. and so on) and procedures on performing tasks from the window. provides background information and concepts on the features. • Feature help. Modify Display the pop-up for changing information on the selected item or items.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. provides descriptions of all window components (fields. Apply Save any changes made in the window. and click Feedback to display a simple online form. 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). You can send us feedback about the information provided in the online help. • Index of help topics. Cancel Do not save any changes made in the window. From the menu bar.

Dialog-specific 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. Click Feedback to send us your comments about the online help. Feature 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 . Enter the first letters of the topic.

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

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

The configuration is saved on the command and member switches.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. which is the startup configuration used each time the switch restarts. If you do not save your changes to Flash memory. make sure you periodically save the configuration. 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. When you make a configuration change to a switch or switch cluster. Note Catalyst 1900 and Catalyst 2820 switches automatically save configuration changes to Flash memory as they occur.txt file in Flash memory. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 2-37 . 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. the change becomes part of the running configuration.

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

• 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 commands. This guide provides procedures for using only the commands that have been created or changed for these switches. refer to the Cisco IOS Release 12. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 3-1 . The Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference provides complete descriptions of these commands. take a few minutes to read this chapter before reading the rest of this guide.0(5). If you have never used IOS software or if you need a refresher. It has been enhanced to support a set of features for the Catalyst 2900 XL and Catalyst 3500 XL switches.0 documentation on Cisco.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).com. For information about the standard Cisco IOS Release 12.

often called user EXEC mode. The commands available to you at any given time depend on which mode you are in. you begin in user mode. such as show commands. which show the current configuration status. To access all commands and modes. you must first enter privileged EXEC mode. From privileged mode. and clear commands. To access the various configuration modes. which has only a limited subset of the commands. a password is required to enter privileged EXEC mode. Normally. Entering a question mark (?) at the system prompt provides a list of commands for each command mode. You can use the virtual LAN (VLAN) database and the various configuration modes to make changes to the running configuration.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. you can enter interface and line configuration modes. which clear counters or interfaces. you must start at 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. you can enter any EXEC command or enter global configuration mode. From global configuration mode. Most of the EXEC commands are one-time commands. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 3-2 78-6511-05 .

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

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

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

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

% Invalid input detected at ‘^’ marker. % Incomplete command. You entered the command incorrectly.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. 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. 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 . The possible keywords that you can enter with the command appear. Reenter the command followed by a space and a question mark (?). You did not enter all of the keywords or values required by this command. Enter a question mark (?) to display all of the commands that are available in this command mode. The caret (^) marks the point of the error. Reenter the command followed by a space and a question mark (?).

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

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

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

com. refer to the Cisco IOS Release 12. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 4-1 .0 commands. For information about the standard Cisco IOS Release 12.0 documentation on Cisco.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.

For information about running the setup program and assigning basic information to the switch. Knowing the software version is also important for compatibility reasons.com on the World Wide Web and are available through authorized resellers. IP information is • Switch IP address • Subnet mask (IP netmask) • Default gateway (router) Once IP information is assigned. 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. you can run the switch on its default settings or configure any settings to meet your network requirements. or by using the show version command. especially for switch clusters.com. it runs a setup program that prompts you enter this information. refer to the release notes. The switch also requires a secret password. Switch Software Releases The switch software is regularly updated with new features and bug fixes. first find out the version of the software that the switch is running. Before upgrading a switch. The first time that you access the switch. You can do this by using the Software Upgrade window.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. You need it if you plan to use the CMS to configure and manage the switch. Cisco also supplies a TFTP server that you can download from Cisco. New software releases are posted on Cisco. and you might want to upgrade your Catalyst 2900 XL and Catalyst 3500 XL with the latest software release.

Be sure that the switch console port settings match the settings of the terminal or PC. set the parity option to None. For information about saving changes from CMS. refer to the switch hardware installation guide. • Parity settings default is None. Make sure that you save any changes you make to the switch console port settings to Flash memory.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. Note If the data bits option is set to 8. For information about connecting to the switch console port. These are the default settings of the switch console port: • Baud rate default is 9600. • Stop bits default is 1. see the “Saving Configuration Changes” section on page 2-37. • Data bits default is 8. For information about saving changes from the CLI. 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 .

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

Note If you change the HTTP port. CMS requires that your switch uses HTTP port 80. You might want to write down the port number to which you are connected. which is the default HTTP port. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 4-5 . For information about connecting to a switch port. you cannot use CMS. 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. Refer to the following topics in the release notes for information about accessing CMS: • System requirements • Running the setup program. 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. Changes to the switch IP information should be done with care. refer to the switch hardware installation guide.Chapter 4 General Switch Administration HTTP Access to CMS HTTP Access to CMS CMS uses Hypertext Transfer Protocol (HTTP). Do not disable or otherwise misconfigure the port through which your management station is communicating with the switch.

and four Remote Monitoring (RMON) groups. You can configure these groups by using an SNMP application or by using the CLI. the IEEE 802. the command switch manages communication between the SNMP management station and all switches in the cluster. note that certain combinations of port features create configuration conflicts.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. For information about managing cluster switches through SNMP.1D bridge MIB. which this IOS software release supports. and troubleshoot Catalyst 2900 XL and Catalyst 3500 XL switches. CiscoWorks2000 and CiscoView 5. 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. This section describes how to access MIB objects to configure and manage your switch. When configuring your switch by using SNMP. see the “Using SNMP to Manage Switch Clusters” section on page 5-22. monitor.0 are network-management applications you can use to configure. see the “Avoiding Configuration Conflicts” section on page 9-2. history. The four supported groups are alarms. events. The switch supports a comprehensive set of Management Information Base (MIB) extensions and MIB II. For more information. and statistics. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 4-6 78-6511-05 .

Step 4 At the ftp> prompt. which resides on the network management system (NMS) • The SNMP agent. 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. 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 3 Enter your e-mail username when prompted for the password.com Use the mouse to navigate to the folders listed above. Using SNMP to Access MIB Variables The switch MIB variables are accessible through SNMP.cisco. The SNMP system consists of three parts: • The SNMP manager. change directories to /pub/mibs/supportlists. Step 2 Log in with the username anonymous. an application-layer protocol facilitating the exchange of management information between network devices.com. 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.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.

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

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

0 on Cisco.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. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 4-10 78-6511-05 . subnet mask.0 on Cisco. and default gateway 0.com.0 on Cisco.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. Cluster Manager System > IP Management – Documentation set for Cisco IOS Release 12. Cluster Manager Release notes on Cisco.com.com.0. Management VLAN VLAN 1 “Management VLANs” section on page 8-4. Cisco Discovery Protocol (CDP) Enabled “Configuring CDP” section on page 6-22. Dynamic Host DHCP Configuration Protocol client is (DHCP) enabled “Using DHCP-Based Autoconfiguration” section on page 6-4.0 on Cisco.0 “Changing IP Information” section on page 6-2. Management Device Management Switch IP address.0. Documentation set for Cisco IOS Release 12. Cluster Manager Cluster > Management VLAN Domain name None “Configuring the Domain Name and Cluster Manager the DNS” section on page 6-8. System > IP Documentation set for Cisco IOS Management Release 12. – Documentation set for Cisco IOS Release 12.com.

com. Cluster Manager “Configuring VTP” section on page 8-20.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.com. Static address assignment None assigned “Adding Static Addresses” section on Cluster Manager page 6-59. Cluster > System Time Documentation set for Cisco IOS Management Release 12. Cluster Manager Security > Address Management Voice configuration – “Configuring Voice Ports” section on – page 7-17. Security > Address Documentation set for Cisco IOS Management Release 12. 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 . Dynamic address management Enabled “Managing the MAC Address Tables” section on page 6-56. VLAN > VLAN Membership VMPS Configuration – “How the VMPS Works” section on page 8-52. Documentation set for Cisco IOS Release 12.0 on Cisco.com.0 on Cisco. VLAN membership Staticaccess ports in VLAN 1 “Assigning VLAN Port Membership Cluster Manager Modes” section on page 8-7. Cluster Manager System > ARP Table Documentation set for Cisco IOS Release 12.0 on Cisco.0 on Cisco.com.

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 . LRE link speed and LRE port profiles LRE-10 “Configuring the LRE Ports” section Cluster Manager on page 7-22. “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.” 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. 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 the Switch Ports.

Cluster Manager Unidirectional link detection Disabled “Configuring UniDirectional Link Detection” section on page 7-9. Port > Flooding Control Cisco Group Enabled Management Protocol (CGMP) “Controlling IP Multicast Packets through CGMP” section on page 6-46. – Network Port Disabled “Enabling a Network Port” section on – page 7-7. – Spanning Tree Protocol Enabled “Configuring STP” section on page 6-24. 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 . 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. – Port grouping None assigned “Creating EtherChannel Port Groups” Cluster Manager section on page 7-10.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. Cluster Manager Multicast VLAN Registration (MVR) Disabled “Configuring MVR” section on page 6-49. Hot Standby Router Protocol Disabled “Designating and Enabling Standby Command Switches” section on page 5-17.

Addressing security Disabled “Managing the MAC Address Tables” section on page 6-56. Trap manager 0. Cluster Manager – – Port > Switch Port Analyzer (SPAN) Documentation set for Cisco IOS Release 12.0. “SNMP Network Management Platforms” section on page 4-6. and file logging Disabled Remote monitoring (RMON) Disabled “Enabling SPAN” section on page 7-16.com.0 on Cisco.0 Cluster Manager Security > Address Management “Adding Trap Managers” section on Cluster Manager page 6-19.com. 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.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. Security Password None “Passwords” section on page 5-8 and – “Changing the Password” section on page 6-15. buffer.0 on Cisco. – Documentation set for Cisco IOS Release 12. System > SNMP Management Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 4-14 78-6511-05 .0.

Cluster Manager Security > Port Security Terminal Access Controller Access Control System Plus (TACACS+) Disabled “Configuring TACACS+” section on – page 6-61. Documentation set for Cisco IOS Release 12.com.0 on Cisco. Port security Disabled “Enabling Port Security” section on page 7-14. Protected port Disabled “Configuring Protected Ports” section on page 7-13. – 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.

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

For the cluster commands. including which ones can be command switches and which ones can only be member switches.” for additional information about switch clusters and the clustering options. refer to the online help. information in this chapter focuses on using CMS. Note Refer to the release notes for the list of Catalyst switches enabled for switch clustering. refer to the Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference. and for the the required software versions and browser and Java plug-in configurations. Therefore. For complete procedures on using CMS to configure switch clusters.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 . See Chapter 2. “Getting Started with CMS.

or they can be distributed across a contiguous Layer 2 network. • It has an IP address. manage. and monitor the member switches. The command switch is the single point of access used to configure. You can designate one or more switches as standby command switches to avoid losing contact with cluster members if the command switch fails. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 5-2 78-6511-05 .0(5)XP or later.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. • No access lists have been defined for the switch because access lists can restrict access to a switch. 1 switch must be designated as the command switch and up to 15 switches can be member switches. • It is not a command or member switch of another cluster. It identifies and controls all member switches in a cluster. • It belongs to the same management VLAN as the cluster member switches. 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. • 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. except for the access class 199 that is created when a device is configured as the command switch. Access lists are not usually used in configuring the Catalyst 2900 XL and Catalyst 3500 XL switches. including which ones can be command switches and which ones can only be member switches. All communication with cluster switches is through one IP address. In a switch cluster. and the required software versions. The switches can be in the same location.

a switch must meet the following requirements: • It is running cluster-capable software. • It has CDP version 2 enabled. To join a cluster. we also recommend that each standby command switch is cabled so that connectivity to cluster members is maintained. but it is not required. Member switches are switches that have actually been added to a switch cluster. a switch must meet the following requirements: • It is running Cisco IOS Release 12. It can also have its own enable or enable secret password. A candidate or member switch can have its own IP address. • It is in the same management VLAN as the active command switch.0(5)XP or later. • It has its own IP address. For redundancy. you must know its enable or enable secret password. • It is not an active member or the command switch of another cluster. To be eligible for a standby group. There is no limit to the number of switches you assign to a standby group. • 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). Note Before adding a candidate switch to the cluster. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 5-3 . • 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. • It is not a command or member switch of another cluster. Candidate and Cluster Member Characteristics Candidate switches are cluster-capable switches that have not yet been added to a cluster. • It is a member of the cluster.

When an edge device that does not support CDP is connected to the command switch. For example. For more information about CDP. This section describes the following considerations. cluster candidates. and neighboring edge devices. select Cluster > User Settings. requirements.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. or to disable the automatic display of suggested candidates. CDP must be enabled for the switch to discover and display the switch cluster and connected switch clusters. CDP can still discover the candidate switches that are attached to it. When a switch that does support CDP but does not support clustering is connected to the command switch. Note Do not disable CDP. the cluster is unable to discover candidates that are attached to that switch. 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. 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. 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. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 5-4 78-6511-05 . The default is three hops. Refer to the release notes for software compatibility considerations and requirements on cluster-capable switches. You can configure the command switch to discover switches up to seven cluster-enabled devices away. To set the number of hops the command switch searches for candidate and member switches. and caveats that you should understand before you create the cluster. By using CDP.

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

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 .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.20.20.20.128.128.222 Active command switch 172. Spanning Tree Protocol (STP) prevents the loops in such a configuration from reducing performance.223 172. Figure 5-2 Redundant Cabling to Support HSRP Virtual IP: 172.

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

When a switch joins a cluster. Passwords If you plan to create switch clusters. It is not necessary to assign passwords to an individual switch if it will be a cluster member. you must enter that password to add the switch to the cluster. Caution Changing the command-switch IP address ends your CMS session. you must assign IP information to a command switch.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). the member switch inherits a null password. provides the highest level of security. If you plan to create switch clusters. You can assign an IP address to the candidate or member switch. If a candidate switch has a password. you should assign an enable secret password to the command switch. Through the command-switch IP address. but it is not necessary. 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. An enable secret password with privilege level 15 is required to access to the switch or switch cluster through CMS and TACACS+ authentication. If no command-switch password is configured. 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). When a member switch has its own IP address. When the switch joins the cluster. it inherits the command-switch password and retains it when it leaves the cluster. You can assign a privilege level (1 to 15) to the password. it remains manageable if it leaves the cluster and becomes a standalone switch. Restart your CMS session by entering the new IP address in the browser Location field (Netscape Communicator) or Address field (Microsoft Internet Explorer). the default. where level 15. as described in the release notes. you can manage and monitor up to 16 switches.

– 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. To prevent unauthorized access to CMS and the CLI. If a Catalyst 1900 or Catalyst 2820 switch joins the cluster. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 5-9 . the length is only checked when the password is configured from the menu console or with the CLI. 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. You can access the CLI by clicking Web Console . – If the command-switch enable password is between one and eight characters inclusive. its passwords and privilege levels are altered. exit your browser to end the browser session. the member-switch enable password is the same as the command switch password. including the Cisco Systems Access page.) – Both the command switch and member switch support up to 25 characters (52 characters encrypted) in the enable secret password.Chapter 5 Clustering Switches Planning a Switch Cluster If you change the member-switch password. A password is not required to redisplay these pages. • Privilege level The command switch supports up to 15 privilege levels. Note Copies of the CMS pages you display are saved in your browser memory cache until you exit the browser session. (Though the password length for Catalyst 1900 and Catalyst 2820 switches is from four to eight characters. the member-switch enable password is truncated to eight characters.HTML access to the command line interface from a cached copy of the Cisco Systems Access page. Catalyst 1900 and Catalyst 2820 member switches support only levels 1 and 15. 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 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. The default host name for any Catalyst 2900 XL and Catalyst 3500 XL switch is Switch. However. When these switches join the cluster. It retains that host name even after it leaves the cluster. its old host name (such as eng-cluster-5) is overwritten with the host name of the command switch in the new cluster. a host name assigned to the command switch can help to more easily identify the switch cluster. eng-cluster-5. The Catalyst 1900 and Catalyst 2820 switches support up to four read-only and four read-write community strings. a command switch named eng-cluster could name cluster member number 5. The Catalyst 2900 XL and Catalyst 3500 XL switches support an unlimited number of community strings and string lengths. 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. it retains that name when it joins a cluster.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. 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. and was then was added to a new cluster. only the first read-only and read-write strings are propagated to the member switch. If a switch has a host name. For example. SNMP Community Strings The Cluster Management software appends the member switch number (@esN. To support the Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 5-10 78-6511-05 . each string contains up to 32 characters. If a switch joins a cluster and it does not have a host name. If a switch received its host name from the command switch. was removed from the cluster.

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

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

However. Creating a Switch Cluster You create a cluster by performing these tasks: 1. A cluster can have a mix of LRE switches using different private profiles. Starting Cluster Builder to add candidate and standby command switches to the cluster After the cluster is formed.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. all LRE switches in that cluster must have that same public profile. Before you add an LRE switch to a cluster. Assigning basic information to one switch (the command switch) 3. Device > LRE Profile appears in the Cluster Manager menu bar when at least one Catalyst 2900 LRE XL switch is in the cluster. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 5-13 . see the “Configuring the LRE Ports” section on page 7-22. 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). these options are only available when the appropriate switch is selected from the Host Name drop-down list. Cabling together switches running clustering software 2. If one LRE switch in a cluster is assigned a public profile. For example. the CMS menu bars display the configuration options of those features. For more information about LRE port profiles. 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. make sure that you assign it the same public profile used by other LRE switches in the cluster. Starting VSM to designate and enable a command switch 4.

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

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

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

the active command switch has the highest priority and is always at the top of the list. followed by the other standby switches according to their priority. and select Cluster > Standby Command Configuration to display the Standby Command Configuration window (Figure 5-5). Candidate switches are ranked first by the number of links they have and second by the switch speed. The last switch has the lowest priority. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 5-17 . If the primary command switch fails. the standby command switch becomes the primary command switch. In the Selected list. The standby switch with the next highest priority then becomes the standby command switch. If the switches have the same number of links and speed. The standby switch with the next highest priority becomes the standby command switch. Eligible switches are listed in the Candidates list according to an eligibility ranking. display Cluster Manager. they are listed alphabetically.Chapter 5 Clustering Switches Creating a Switch Cluster Designating and Enabling Standby Command Switches To create a standby group. The standby command switch is listed after 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. If you use this window to create the HSRP group. Must be valid IP address in the same subnet as the active command switch. all switches in the group have the preempt command enabled. nms-lab1 (CC) Switch201 Switch207 Standby command switches are listed below the active command switch. Candidates are listed in order of the eligibility. 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. It can be from 0 to 255.cisco. this number cannot be changed. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 5-18 78-6511-05 . and the default is 0.Chapter 5 Clustering Switches Creating a Switch Cluster Figure 5-5 Standby Command Configuration Switch205 Switch202. and the group number must be unique within the IP subnet. and the name for the group is clustername_standby. 54509 Once entered.com Active command switch is at the top.

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

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

After this. the Telnet session accesses the management console (a menu-driven interface) if the command switch is at privilege level 15. If the command switch is at privilege level 14. enter the show cluster members user EXEC command on the command switch. For instructions on configuring the Catalyst 2900 XL or Catalyst 3500 XL switch for a Telnet session. you are prompted for the password before being able to access the menu console. see the “Accessing the CLI” section on page 3-8. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 5-21 . refer to the Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference. 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. • If the command-switch privilege level is 15. 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 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.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. the member switch is accessed at privilege level 1. The IOS commands then operate as usual. Enter the exit privileged EXEC command on the member switch to return to the command-switch CLI. For Catalyst 1900 and Catalyst 2820 switches running standard edition software. For more information about the rcommand command. For Catalyst 2900 XL and Catalyst 3500 XL switches. the member switch is accessed at privilege level 15. the Telnet session accesses the member-switch CLI at the same privilege level as on the command switch. The Catalyst 1900 and Catalyst 2820 CLI is available only on switches running Enterprise Edition Software. the command mode changes and IOS commands operate as usual.

see the “SNMP Community Strings” section on page 5-10 and the “Configuring SNMP” section on page 6-18. When you first power on the switch. the command switch passes traps from the member switch to the management station. sets. as shown in Figure 5-7. SNMP is enabled if you enter the IP information by using the setup program and accept its proposed configuration. If the member switch does not have an IP address. the command switch can change without your knowledge.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. If a member switch has its own IP address and community strings. they can be used in addition to the access provided by the command switch. If you did not use the setup program to enter the IP information and SNMP was not enabled. 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 Cluster Management software appends the member switch number (@esN. The command switch uses this community string to control the forwarding of gets. 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. When you create a cluster. the command switch manages the exchange of messages between member switches and an SNMP application. and get-next messages between the SNMP management station and the member switches. Note When a standby group is configured. SNMP is enabled by default. For more information. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 5-22 78-6511-05 . you can enable it on the SNMP Configuration page described in the “Configuring SNMP” section on page 6-18. On Catalyst 1900 and Catalyst 2820 switches.

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 . Trap 2.

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 .

C H A P T E R 6 Configuring the System This chapter provides information about changing switch-wide configuration settings. This chapter does not repeat the concepts and CLI procedures provided in the standard Cisco IOS Release 12. refer to the Cisco IOS Release 12. refer to the online help. 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.0 documentation.0 documentation on Cisco. Note Some features can be implemented only by using the CLI.com for additional information and CLI procedures. For complete syntax and usage information for the commands used in this chapter.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. 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).

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

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

a Domain Name System (DNS) server. You might also need to configure a TFTP server. Note DHCP replaces the Bootstrap Protocol (BOOTP) feature autoconfiguration to ensure retrieval of configuration files by unicast TFTP messages. BOOTP is available in earlier software releases for this switch. A relay device forwards broadcast traffic between two directly connected LANs. where designated DHCP servers allocate network addresses and deliver configuration parameters to dynamically configured devices. Understanding DHCP-Based Autoconfiguration The DHCP provides configuration information to internet hosts and internetworking devices. No DHCP client-side configuration is required on your switch. However. you need to configure the DHCP server for various lease options. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-4 78-6511-05 . DHCP is built on a client-server model. A router does not forward broadcast packets. With DHCP-based autoconfiguration.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. 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. With DHCP-based autoconfiguration. 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. DHCP-based autoconfiguration replaces the BOOTP client functionality on your switch. but it forwards packets based on the destination IP address in the received packet. and possibly a relay device if the servers are on a different LAN than your switch. 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.

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

the server usually reserves the address until the client has had a chance to formally request the address. 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. the client returns a DHCPDECLINE broadcast message to the DHCP server. The offer from the DHCP server is not a guarantee that the IP address will be allocated to the client. If the DHCP server does not support reserved leases. If the switch accepts replies from a BOOTP server and configures itself. the client usually accepts the first offer it receives. instead of unicast. which means the offered configuration parameters have not been assigned. TFTP requests to obtain the switch configuration file.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). A DHCP client might receive offers from multiple DHCP or BOOTP servers and can accept any one of the offers. The DHCP server sends the client a DHCPNAK denial broadcast message. however. Configuring the DHCP Server You should configure the DHCP servers with reserved leases that are bound to each switch by the switch hardware address. however. the switch can obtain different IP addresses and configuration files at different boot instances. an error has occurred during the negotiation of the parameters. 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 . the switch will broadcast.

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

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

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

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

If the switch cannot read the router-confg file. If the host name is not specified in the DHCP reply. the switch reads the configuration file that has the same name as its host name (hostname-confg or hostname. If the switch cannot read the network-confg.cfg. or the host-name file. If the cisconet.cfg file is read. The switch sends a DNS request to the DNS server. the filename of the host is truncated to eight characters. depending on whether network-confg or cisconet. it reads the router-confg file.cfg file. It also receives a DNS server IP address and a TFTP server name. The switch fills its host table with the information in the file and obtains its host name. if all attempts to read the configuration file through unicast transmissions fail.cfg default configuration file.cfg was read earlier) from the TFTP server. Note The switch broadcasts TFTP server requests if the TFTP server name is not obtained from the DHCP replies. the switch uses the default “Switch” as its host name.cfg file. or if the TFTP server name cannot be resolved to an IP address. After obtaining its host name from the default configuration file or the DHCP reply. cisconet. The configuration filename is not provided (two-file read method). it reads the ciscortr. the switch reads the cisconet. 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. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-11 . The switch sends a unicast message to the TFTP server to retrieve the network-confg or cisconet. (If the network-confg file cannot be read. The switch receives its IP address and subnet mask from the DHCP server.Chapter 6 Configuring the System Changing IP Information • Only the IP address is reserved for the switch and provided in the DHCP reply. to obtain the TFTP server address. specifying the TFTP server name. If the host name is not found in the file.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.0.2002 00e0.0.2 DNS server 10.0.3 TFTP server (maritsu) 47571 10.2003 00e0.9f1e.9f1e.0.0. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-12 78-6511-05 .0.10 DHCP server 10.0.2001 00e0.9f1e. Figure 6-3 DHCP-Based Autoconfiguration Network Example Switch 1 Switch 2 Switch 3 Switch 4 00e0.9f1e.2004 Cisco router 10.1 Table 6-1 shows the configuration of the reserved leases on the DHCP server.0.

24 Subnet mask 255.10 10.22 ip host switch3 10.0.0. This file contains the host name to be assigned to the switch based on its IP address.0.0.2 TFTP server name maritsu or 10. TFTP Server Configuration (on UNIX) The TFTP server base directory is set to /tftpserver/work/.255.0.2002 00e0.10 10.0.0.21 ip host switch2 10.0.0.24 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-13 .3.23 10.0.0.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.255.0.23 ip host switch4 10.2 10.0.0.2003 00e0. switch2-confg.0. This directory contains the network-confg file used in the two-file read method.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.3 maritsu or 10.0.2 10.0.0.22 10.0.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.10 10.255.21 10.0.255.0 255.255.0.0 255.0.0 Router address 10.0.0.0. The base directory also contains a configuration file for each switch (switch1-confg.2 DNS server address 10.255.9f1e.9f1e.0.0.0.2004 IP address 10.0.10 10.0.3 maritsu or 10.0.2001 00e0.0.9f1e.0.0.0.0.9f1e.0.0.0.255.0.0.

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

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

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

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

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

When you configure a trap manager. refer to the Cisco IOS Release 12. TTY Generate traps when the switch starts a management console CLI session. You can enter community strings with the following characteristics: Read-only (RO)—Requests accompanied by the string can display MIB-object information. These traps are in the private enterprise-specific Management Information Base (MIB). C2900/C3500 Generate the switch-specific traps. Table 6-2 describes the Catalyst 2900 XL and Catalyst 3500 XL switch traps. 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. the management station accesses the switch by using that IP address. no trap manager is defined. the community strings for each member switch must be unique. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-19 . If you are entering community strings for a cluster member. VTP Generate a trap for each VLAN Trunk Protocol (VTP) change. and no traps are issued.0 documentation on Cisco.com for additional information and CLI procedures. Read-write (RW)—Requests accompanied by the string can display MIB-object information and set MIB objects. 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. If a member switch has an assigned IP address. Adding Trap Managers A trap manager is a management station that receives and processes traps. For CLI procedures. 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. By default.

When you configure community strings for these switches. 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. When configuring traps on these switches.Chapter 6 Configuring the System Configuring SNMP Catalyst 1900 and Catalyst 2820 switches support up to four trap managers. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-20 78-6511-05 . you cannot configure individual trap managers to receive specific traps. but these traps are received by all configured trap managers. BSC Generates a trap when the broadcast threshold is exceeded. 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. Authentication Generates a trap when an SNMP request is not accompanied by a valid community string. limit the string length to 32 characters. Table 6-3 describes the Catalyst 1900 and Catalyst 2820 switch traps. You can enable any or all of these traps.

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

and the command switch cannot learn about connected candidate switches connected to it. set global CDP parameters. and display information about neighboring Cisco devices. Note Creating and maintaining switch clusters is based on the regular exchange of CDP messages. If necessary. you can configure CDP to discover switches running the Cluster Management Suite up to seven devices away from the command switch. 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. Disabling CDP can interrupt cluster discovery. For more information about the role that CDP plays in clustering. Although the Catalyst 5000 supports CDP.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. even if they are running CMS. 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. and CDP cannot discover any device connected to them. For example. Devices that do not run clustering software display as edge devices. Figure 6-4 shows a command switch that can discover candidates and cluster members up to seven devices away from it. it does not support clustering. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-22 78-6511-05 . see the “Automatic Discovery of Cluster Candidates” section on page 5-4. CDP enables the Cluster Management Suite to display a graphical view of the network.

Command Purpose Step 1 configure terminal Enter global configuration mode. The hop count is displayed in the file. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-23 . 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 2 cluster discovery hop-count number Enter the number of hops that you want CDP to search for cluster candidates and cluster members. Step 4 show running-config Verify the change by displaying the running configuration file.

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. All Catalyst 3500 XL switches and most Catalyst 2900 XL switches support 250 VLANs. you can enable STP on those 250 VLANs. The STP instance is removed when the last interface is moved to another VLAN. You can change all VLANs on a switch by using the stp-list parameter when you enter STP commands through the CLI. The remaining VLANs must operate with STP disabled. at least one switch on each loop in the VLAN must be running spanning tree. 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. If you have already used up all available STP instances on a switch. 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 Catalyst 2924C XL support only 64 VLANs. Catalyst 2924 XL. if 250 VLANs are defined in the VTP domain. The Catalyst 2912 XL. For more information about VLANs. For example. see Chapter 8. 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. You can disable STP on one of the VLANs where it is running. “Configuring VLANs. STP calculates the best loop-free path throughout the network. Only one active path can exist between any two stations. Supported STP Instances You create an STP instance when you assign an interface to a VLAN. Therefore. refer to the Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference. adding another VLAN anywhere in the VLAN Trunk Protocol (VTP) domain creates a VLAN that is not running STP on that switch. For more information. These parameters are applied when the STP instance is created. Use the no spanning-tree vlan vlan-id global configuration command to disable STP on a specific VLAN. and then enable it on the VLAN where you want it to run.” Each VLAN is a separate STP instance.

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

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

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 .

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

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 .

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

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. The switches in the stack use their stack ports to communicate with each other and to connect to the stack backbone. see the “Events that Cause Fast Convergence” section on page 6-33. the normal STP transition occurs. you can have a redundant and resilient network in some configurations. if its stack root port fails. and C are cascaded through the Gigastack GBIC to form a multidrop backbone. which communicates control and data traffic across the switches at the access layer. If Switch A fails. Links B and C are alternate redundant links that are in the STP blocking state. 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. is in the STP forwarding state. B. The stack root port on Switch A provides the path to the root of the spanning tree. How CSUF Works CSUF ensures that one link in the stack is elected as the path to the root. As shown in Figure 6-7. 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. With this feature. For more information. or if Link A fails. which completes in 30 to 40 seconds. the root link. Link A. CSUF might not provide a fast transition all the time. Switches A. in these cases.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). 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. During the fast transition.

When certain link loss or STP events occur (described in the “Events that Cause Fast Convergence” section on page 6-33). the Fast Uplink Transition Protocol uses the neighbor list to send fast-transition requests on the stack port to stack members. all stack switches build a neighbor list of stack members through the receipt of discovery hello packets.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 . Using the Stack Membership Discovery Protocol.

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

the normal STP convergence occurs. The fast transition might not occur if multiple events occur simultaneously. a link connecting the stack root to the STP root comes back up. the normal STP convergence then occurs. heavy network traffic might prevent the fast transition from occurring within this time frame. which was powered down or failed. Because the Fast Uplink Transition Protocol only waits 2 seconds to receive acknowledgements from all stack switches. if a stack member switch is powered down. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-34 78-6511-05 . which might become the stack root. • A switch other than the stack root is powered down or failed.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. Instead of a fast transition. is added to the stack. • 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. is powered up. • The stack root switch. The fast transition of CSUF depends on the amount of network traffic and how you connect the GigaStack GBICs across the stack switches. For example. • A new switch.

In addition. follow these guidelines: • Do not connect alternate stack root ports to stack ports. • Each stack switch can be connected to the STP backbone through one uplink. • All stack ports on the stack of switches must be connected to the multidrop backbone.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. • Up to nine stack switches can be connected through their stack ports to the multidrop backbone. • Only one stack port is supported per switch. • 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 . 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. Only one stack port per switch is supported. • Up to 64 VLANs are supported.

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 .

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

Switches not acting as the root use the root-switch Max age parameter. Hello Time Number of seconds (1 to 10) between the transmission of hello messages. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-38 78-6511-05 . 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. Max age Number of seconds (6 to 200) a switch waits without receiving STP configuration messages before attempting a reconfiguration. This parameter takes effect when a switch is operating as the root switch. which indicate that the switch is active. Forward Delay Number of seconds (4 to 200) a port waits before changing from its STP learning and listening states to the forwarding state.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. Switches not acting as a root switch use the root-switch Hello-time value. The default is IEEE. You can change the root parameters for the VLANs on a selected switch. 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 following options define how your switch responds when STP reconfigures itself. Protocol Implementation of STP to use: IBM or IEEE.

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

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

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

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

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

as shown in Figure 6-9. STP can reconfigure itself and select a customer switch as the STP root switch.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. In such a topology. 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. and STP selects a new root switch. 43578 Desired root switch Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-44 78-6511-05 . 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. 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. 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. Caution Figure 6-9 Misuse of this feature can cause a loss of connectivity.

ARP determines the associated MAC address. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-45 . 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 2 interface interface Enter interface configuration mode. Taking an IP address as input. standard Ethernet-style ARP encapsulation (represented by the arpa keyword) is enabled on the IP interface. the IP-MAC address association is stored in an ARP cache for rapid retrieval. Each VLAN has its own instance of STP. Once a MAC address is determined. The process of determining the local data link address from an IP address is called address resolution. ARP entries added manually to the table do not age and must be manually removed. 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. Beginning in privileged EXEC mode. Step 4 end Return to privileged EXEC mode. The Address Resolution Protocol (ARP) associates a host IP address with the corresponding media or MAC addresses and the VLAN ID. Use the no version of the spanning-tree rootguard command to disable the root guard feature. By default.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. Then the IP datagram is encapsulated in a link-layer frame and sent over the network. follow these steps to set root guard on a port: Command Purpose Step 1 configure terminal Enter global configuration mode. and enter the port to be configured. for example). Step 3 spanning-tree rootguard Enable root guard on the port. Step 5 show running-config Verify that the port is configured for root guard.

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

the switch removes the port from the group. Step 2 no cgmp leave-processing Disable CGMP and CGMP Fast Leave. Step 4 show running-config Verify your entry. The client must be running IGMP version 2 for the Fast Leave feature to function properly. the group remains enabled for that VLAN until all members have requested to leave. Disabling the CGMP Fast Leave Feature Beginning in privileged EXEC mode. Beginning in privileged EXEC mode. With the Fast Leave feature enabled. Step 4 show running-config Verify your entry. Step 2 cgmp leave-processing Enable CGMP and CGMP Fast Leave. Step 3 end Return to privileged EXEC mode. the switch immediately verifies if there are other group members attached to its ports. 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. If there are no other members. When an end station requests to leave a CGMP group. follow these steps to disable the CGMP Fast Leave feature: Command Purpose Step 1 configure terminal Enter global configuration mode. The Fast Leave feature functions only if CGMP is enabled. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-47 . follow these steps to enable the CGMP Fast Leave feature: Command Purpose Step 1 configure terminal Enter global configuration mode. 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.

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

intercepts the IGMP messages. the set-top box or PC sends an IGMP report to the access layer switch (S1 switch) to join the appropriate multicast. but to isolate the streams from the subscriber VLANs for bandwidth and security reasons. The switch CPU sends an IGMP group-specific query through the receiver port VLAN. (See Figure 6-10. Multiple set-top boxes or PCs can be connected to one subscriber port. the set-top box sends an IGMP leave message for the multicast stream. The switch CPU identifies IP multicast streams and their associated MAC addresses in the switch forwarding table. It allows the single multicast VLAN to be shared in the network while subscribers remain in separate VLANs.) 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 . This forwarding behavior selectively allows traffic to cross between the two VLANs. Using MVR in a Multicast Television Application In a multicast television application. When a subscriber changes channels or turns off the television. 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. This provides the ability to continuously send multicast streams in the multicast VLAN. MVR allows a subscriber on a port to subscribe and unsubscribe to a multicast stream on the network-wide multicast VLAN. 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. Because MVR does not support IGMP dynamic joins. When a subscriber selects a channel. a PC or a television with a set-top box can receive the multicast stream. If the IGMP report matches one of the configured multicast MAC addresses. broadcast of multiple television channels) across an Ethernet ring-based service provider network. 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. the user or administrator must configure static multicast addresses on the router.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.

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. that set-top box must respond within the maximum response time.Chapter 6 Configuring the System Configuring MVR set-top box in the VLAN still subscribing to this group. 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.

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

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

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

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

Step 9 copy running-config startup-config Save your configuration changes to NVRAM. 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. Step 8 show mvr show mvr interface show mvr members Verify the configuration. Note This command applies only to receiver ports and should only be enabled on receiver ports to which a single receiver device is connected.

10. module. 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. Secure addresses do not age. • Secure address: a manually entered unicast address that is usually associated with a secured port. Figure 6-11 Contents of the Address Table MAC Addresses and VLANs All addresses are associated with a VLAN. A known address in one VLAN is unknown in another until it is learned or statically associated with a port in the other VLAN. 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. An address can be secure in one VLAN and dynamic in another. could be forwarded to port 1 in VLAN 1 and ports 9. Figure 6-11 shows an example list of addresses as they would appear in the dynamic. or static address table. An address can exist in more than one VLAN and have different destinations in each. and port number associated with the address. for example. secure. All MAC addresses in the address tables are associated with one or more ports. and 11 in VLAN 5. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-56 78-6511-05 . Multicast addresses. Each VLAN maintains its own logical address table. • Static address: a manually entered unicast or multicast address that does not age and that is not lost when the switch resets.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.

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. Step 4 show mac-address-table aging-time Verify your entry. This unnecessary flooding can impact performance. it floods the packet to all ports in the same VLAN as the receiving port. 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. Beginning in privileged EXEC mode. Step 3 end Return to privileged EXEC mode. Then when the switch receives a packet for an unknown destination. Command Purpose Step 1 configure terminal Enter global configuration 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.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. Setting too long an aging time can cause the address table to be filled with unused addresses. This parameter applies to all VLANs. You can enter a number from 10 to 1000000. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 6-57 .

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

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

the input port. the ports to which it can be forwarded. the ports to which it can be forwarded. Step 3 end Return to privileged EXEC mode. you can omit the VLAN ID.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. follow these steps to add a static address: Command Purpose Step 1 configure terminal Enter global configuration mode. Step 3 end Return to privileged EXEC mode. follow these steps to remove a static address: Command Purpose Step 1 configure terminal Enter global configuration mode. Beginning in privileged EXEC mode. Removing Static Addresses Beginning in privileged EXEC mode. Step 2 mac-address-table static hw-addr in-port out-port-list vlan vlan-id Enter the MAC address. the input port. 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. Step 4 show mac-address-table static Verify your entry. In this case. the switch recognizes the VLAN as that associated with the in-port VLAN. Otherwise. and the VLAN ID to be removed. Step 4 show mac-address-table static Verify your entry. and the VLAN ID of those ports. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 6-60 78-6511-05 . You can remove all secure addresses by using the clear mac-address-table static command in privileged EXEC mode. you must supply 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 information about configuring these settings from Cluster Management Suite (CMS). Note Some features can be implemented only by using the CLI. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 7-1 . refer to the online help. For complete syntax and usage information for the commands used in this chapter.C H A P T E R 7 Configuring the Switch Ports This chapter provides information about changing port configuration settings.0 documentation. refer to the Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference.0 commands. refer to the Cisco IOS Release 12. 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 documentation on Cisco. Review the “Avoiding Configuration Conflicts” section on page 9-2 before you change the port settings. 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. Note Certain port features can conflict with one another.

and set the duplex and flow control parameters to be compatible with the other device. but the duplex setting must be explicitly set. • Gigabit Ethernet ports that do not match the settings of an attached device lose connectivity and do not generate statistics. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 7-2 78-6511-05 . Autonegotiation for the speed setting selects the correct speed even if the attached device does not autonegotiate. and GigaStack-to-GigaStack point-to-point connections operate in full-duplex mode. The Ethernet link settings on the Long-Reach Ethernet (LRE) ports have special considerations and different default settings than from the 10/100 ports. the switch can take up to 30 seconds to check for loops when a port is reconfigured. a Spanning Tree Protocol (STP) reconfiguration could cause a temporary loss of connectivity. and set the speed setting to Auto. 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. The port LED is amber while STP reconfigures. 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. • If STP is enabled.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. disable autonegotiation on the local device. For this information. • GigaStack-to-GigaStack stack connections operate in half-duplex mode. To connect to a remote Gigabit Ethernet device that does not autonegotiate. Connecting to Devices That Do Not Autonegotiate To connect to a remote 100BASE-T device that does not autonegotiate. set the duplex setting to Full or Half.

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

The maximum half-duplex transmission on a 100BASE-T link is 148. 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. By default. multicast. unicast. unicast. or multicast packets are received on a port.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. The rising threshold is the number of packets that a switch port can receive before forwarding is blocked. 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. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 7-4 78-6511-05 . Storm control uses high and low thresholds to block and then restore the forwarding of broadcast. or multicast packets. Forwarding these packets can cause the network to slow down or to time out. Storm control is configured for the switch as a whole but operates on a per-port basis. the higher the threshold. In general.000 packets per second. but you can enter a threshold of up to 4294967295 broadcast packets per second. You can also set the switch to shut down the port when the rising threshold is reached.

Disabling Storm Control Beginning in privileged EXEC mode. Step 6 show port storm-control [interface] Verify your entries. 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. and enter the port to configure. Step 3 no port storm-control broadcast Disable port storm control. Step 5 show port storm-control [interface] Verify your entries. Step 5 end Return to privileged EXEC mode. follow these steps to enable broadcast-storm control. and enter the port to configure. Step 4 end Return to privileged EXEC mode. Step 3 port storm-control broadcast [threshold {rising rising-number falling falling-number}] Enter the rising and falling thresholds for broadcast packets. follow these steps to disable broadcast-storm control. 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. Step 2 interface interface Enter interface configuration mode. Make sure the rising threshold is greater than the falling threshold. the following procedure could also be used to enable storm control for unicast or multicast packets. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 7-5 . Step 2 interface interface Enter interface configuration mode. Command Purpose Step 1 configure terminal Enter global configuration mode.

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

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

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

Beginning in privileged EXEC mode. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 7-9 . Use the udld reset command to reset all ports that have been shut down by UDLD. You can configure UDLD on the entire switch or on an individual port.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. Use the udld interface configuration command to enable UDLD on a specific port. follow these steps to configure UDLD on a switch: Command Purpose Step 1 configure terminal Enter global configuration mode. Step 4 show running-config Verify the entry by displaying the running configuration. Step 3 end Return to privileged EXEC mode. Step 2 udld enable Enable UDLD on all switch ports.

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. Source-based forwarding is enabled by default. logical ports for high-bandwidth connections between switches or between switches and servers. but you cannot create a port group that has both port speeds. Destination-based port groups distribute packets forwarded to the group based on the destination address of incoming packets. for example. Source-based forwarding port groups distribute packets forwarded to the group based on the source address of incoming packets. they must be all source-based or all destination-based. For the restrictions that apply to port groups. You can have source-based port groups and destination-based source groups. You can configure up to eight ports in a source-based forwarding port group. All ports in each group must be of the same type. but you must consistently configure both ends of a port group. see the “Avoiding Configuration Conflicts” section on page 9-2. You can independently configure port groups that link switches. 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. You can create up to 12 port groups. Note You can create port groups of either Gigabit Ethernet ports or 100BASE-TX ports. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 7-10 78-6511-05 .

configure the static address to forward to all ports in the group.Chapter 7 Configuring the Switch Ports Creating EtherChannel Port Groups In Figure 7-1. configure the static address to forward to only one port in the port group. Because the router is a single-MAC-address device. broadcast. changing STP or VLAN membership parameters for one port in the group automatically changes the parameters for all ports. 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. the switch uses the configuration of the first port for all ports added to the group. For more information. After the group is created. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 7-11 . This method avoids the possible transmission of duplicate packets. 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). Each port group has one port that carries all unknown multicast. source-based forwarding ensures that the switch uses all available bandwidth to the router. If you add a port and change the forwarding method. therefore. and STP packets. This method eliminates the chance of lost packets. 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. a port group of two workstations communicates with a router. see the “Adding Static Addresses” section on page 6-59. when you create a port group. • If the port group forwards based on the destination address.

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

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

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

Step 2 interface interface Enter interface configuration mode for the port you want to secure. Step 5 show port security Verify the entry. Disabling Port Security Beginning in privileged EXEC mode. Step 6 show port security Verify the entry. follow these steps to disable port security. Command Purpose Step 1 configure terminal Enter global configuration mode. Step 3 port security max-mac-count 1 Secure the port and set the address table to one address. Step 2 interface interface Enter interface configuration mode for the port you want to unsecure. Step 3 no port security Disable port security. follow these steps to enable port security. 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 .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 port security action shutdown Set the port to shutdown when a security violation occurs. Step 5 end Return to privileged EXEC mode. Enabling Port Security Beginning in privileged EXEC mode. Step 4 end Return to privileged EXEC mode. Setting one address in the MAC address table for the port ensures that the attached device has the full bandwidth of the port.

see the “Avoiding Configuration Conflicts” section on page 9-2. and any combination of ports can be monitored. Step 4 end Return to privileged EXEC mode. and enter the port number of the monitor port. A SPAN port cannot monitor ports in a different VLAN. Step 3 no port monitor interface Disable port monitoring on the port. Step 4 end Return to privileged EXEC mode. Disabling SPAN Beginning in privileged EXEC mode. and a SPAN port must be a static-access port. Step 3 port monitor interface Enable port monitoring on the port. follow these steps to enable SPAN: Command Purpose Step 1 configure terminal Enter global configuration mode. and enter the port that acts as the monitor port.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. For the restrictions that apply to SPAN ports. Step 2 interface interface Enter interface configuration mode. Beginning in privileged EXEC mode. 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. follow these steps to disable SPAN: Command Purpose Step 1 configure terminal Enter global configuration mode. Step 2 interface interface Enter interface configuration mode. Step 5 show running-config Verify your entries. You can define any number of ports as SPAN ports.

Because the sound quality of an IP telephone call can deteriorate if the data is unevenly transmitted. 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. • Port 2 is an internal 10/100 interface that carries the phone traffic.1Q trunk 33048 IP Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 7-17 . The Cisco 7960 IP Phone contains an integrated three-port 10/100 switch. The Cisco 7960 IP Phone itself is also a configurable device. • Port 3 connects to a PC or other device. 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.1p priority.1p class of service (CoS).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. 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. QoS uses classification and scheduling to transmit network traffic from the switch in a predictable manner. If necessary. the Catalyst 3524-PWR XL can supply electrical power to the circuit connecting it to the Cisco 7960 IP Phone. this release of IOS supports quality of service (QoS) based on IEEE 802. Figure 7-2 shows one way to configure a Cisco 7960 IP Phone. and you can configure it to forward traffic with an 802.

Step 2 interface interface Enter interface configuration mode.1p priority tagging for voice traffic and to use VLAN 0 (default native VLAN) to carry all traffic. and voice traffic always has a CoS priority of 5. See the “Configuring a Trunk Port” section on page 8-38 for instructions. Command Purpose Step 1 configure terminal Enter global configuration mode. • Beginning in privileged EXEC mode. 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. This is the default. configure the port as an 802. Step 4 end Return to privileged EXEC mode. and all traffic is in the same VLAN. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 7-18 78-6511-05 .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. and enter the port to be configured.1Q trunk and as a member of the voice VLAN (VVID). a port connecting a Catalyst 3524-PWR XL switch to a Cisco 7960 IP Phone can carry mixed traffic. • Voice traffic is given a higher priority by the phone. Step 3 switchport voice vlan dot1p Instruct the switch to use 802. 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. • Voice and data traffic are carried on separate VLANs. Step 5 show interface interface switchport Verify the port configuration.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.

If you want. Use the no switchport priority extend command to return the port to its default setting. Beginning in privileged EXEC mode. You can also set the phone port to accept (trust) the priority of frames arriving on the port. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 7-19 . Step 4 end Return to privileged EXEC mode. you can use the Catalyst 3524-PWR XL CLI to override the priority of frames arriving on the phone port from connected devices. 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.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 2 interface interface Enter interface configuration mode. The PC can generate packets with an assigned CoS value. 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 5 show interface interface switchport Verify the change.

you must connect all Cisco IP Phones and other voice-related devices to switch ports that belong to VLAN 2. The Cisco IP Phone forwards the traffic with an 802. VLAN 1 carries data traffic. In the following configuration. and VLAN 2 carries voice traffic. Step 6 show interface interface switchport Verify the configuration. Step 5 end Return to privileged EXEC mode. and enter the port to be configured. Beginning in privileged EXEC mode. Step 4 switchport voice vlan (2) Instruct the Cisco IP Phone to forward all voice traffic through VLAN 2. In this configuration.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. VLAN 1. 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. The Cisco IP Phone forwards this traffic through the native VLAN.1p priority to untagged traffic that is received on the switch port. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 7-20 78-6511-05 . Step 2 interface interface Enter interface configuration mode.1p priority of 5. Step 3 switchport priority default (0) Assign an IEEE 802.

if necessary. Command Purpose Step 1 configure terminal Enter global configuration mode. Step 4 end Return to privileged EXEC mode. use the power inline auto command. any Catalyst 2900 XL or Catalyst 3500 XL can forward IP voice traffic to and from the phone. When the Cisco 7960 IP Phone supplies its own power. Step 3 power inline never Permanently disable inline power on the port. You can configure the switch to never supply power to the Cisco 7960 IP Phone and to disable the detection mechanism. The Catalyst 3524-PWR XL senses if it is connected to a Cisco 7960 IP Phone. If there is power on the circuit. 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. 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.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 supplies the power. The Cisco 7960 IP Phone can also be connected to an AC power source and supply its own power to the voice circuit. Step 2 interface interface Enter interface configuration mode. Step 5 show power inline interface configured Verify the change. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 7-21 . Beginning in privileged EXEC mode. To enable inline power when a Cisco 7960 IP Phone is detected. and enter the port to be configured.

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 7-22 78-6511-05 .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. • Ethernet link—This is the connection between the 10/100 Ethernet port on the CPE and an Ethernet device. depends on the active profile for the LRE port and the Ethernet link speed. The actual link rate between an LRE port and a remote Ethernet device. Conversely. Asymmetrical transmission is when the downstream and the upstream bandwidth differ. Symmetrical transmission is when the downstream and upstream bandwidth are the same. This connection is through standard Category 5 cabling and can extend to distances of up to 328 ft (100 m). if the PC Ethernet port is configured to 10 Mbps and the LRE port is configured with an upstream link rate of 17. in either direction. Downstream transmission refers to the data traveling from the LRE port to the CPE. 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.69 Mbps. 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). the actual upload rate provided to the PC user is 17. The LRE link provides symmetric and asymmetric bandwidth for voice and data traffic.06 Mbps.06 Mbps.69 Mbps. Upstream transmission refers to the data traveling from the CPE to the LRE port. if a PC Ethernet port is configured to 100 Mbps and the LRE port is configured with an upstream link rate of 5. 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). For example. the actual upload rate provided to the PC user is 5. not 100 Mbps. such as a PC.

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

38 4101 ft (1250 m) LRE-15 Private 15. the LRE port uses its private profile. the change immediately takes effect. the change immediately takes effect.27 4101 ft (1250 m) PUBLIC-ETSI Public 11. If you assign a different public profile. keep the following considerations in mind: • An LRE port always has a private profile assigned to it. the switch ignores the private profile settings and uses the public profile settings on all LRE ports.69 5.27 4101 ft (1250 m) LRE-5 Private 5.Chapter 7 Configuring the Switch Ports Configuring the LRE Ports Note Use the rates and distances in Table 7-1 as guidelines only.06 3445 ft (1050 m) When assigning a profile to an LRE port. If no public profile is configured on the switch.17 17. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 7-24 78-6511-05 . Factors such as the type of cable you use. However.38 4. 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.17 4. If you assign a different private profile to the LRE port. you must first disable the public profile by using CMS or by using the no lre profile global global configuration command. public profiles have priority over private profiles. how it is bundled. If a public profile is configured on the switch and you want the LRE ports to use private profiles. and the interference and noise on the LRE link can affect the actual LRE link performance.69 4921 ft (1500 m) LRE-10 (default) Private 11. If you assign a public profile to the switch. Contact Cisco Systems for information about limitations and optimization of LRE link performance.38 11. 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.

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

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. and the statistics collected by the CPE LRE chipset. For information about this command. • The switch 10/100 port defaults are not the same as the defaults for the Ethernet link on the LRE ports. Use the show controllers ethernet-controller privileged EXEC command to display the internal switch statistics.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. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 7-26 78-6511-05 . This prevents access to the LRE port and prevents the power emitted from the port from affecting other ports. the statistics collected by the switch LRE chipset. refer to the Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference.

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

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

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. Note Some features can be implemented only by using the CLI.com for additional information and CLI procedures.0 documentation. For complete syntax and usage information for the commands used in this chapter.C H A P T E R 8 Configuring VLANs This chapter provides information about configuring virtual LANs (VLANs). refer to the online help. Note Certain port features can conflict with one another. refer to the Cisco IOS Release 12. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-1 .0 commands. Review the “Avoiding Configuration Conflicts” section on page 9-2 before you change the port settings.0 documentation on Cisco. For information about configuring these settings from Cluster Management Suite (CMS). 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. refer to the Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference.

and unicast. 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. Any switch port can belong to a VLAN. it contains its own bridge Management Information Base (MIB) information and can support its own implementation of the Spanning Tree Protocol (STP). Each VLAN is considered a logical network. without regard to the physical locations of the users. For information about managing VLAN STP instances. or application. broadcast. Because a VLAN is considered a separate logical network. 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 . 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. VLANs are identified with a number of 1 to 1001. project team. see the “Supported STP Instances” section on page 6-24.

Catalyst 2924 XL. Trunking is not supported on all switches and modules.Chapter 8 Configuring VLANs Overview Table 8-1 lists the number of supported VLANs on the switches. The GigaStack GBIC also supports both trunking methods. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-3 . For the list of products that support trunking. refer to the release notes. For more information on these commands. Table 8-1 Maximum Number of Supported VLANs Number of Supported VLANs Trunking Supported? Catalyst 2912 XL. 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. 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.1Q trunking methods for transmitting VLAN traffic over 100BASE-T and Gigabit Ethernet ports. refer to the Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference. 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.

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

Before a new switch can be added to a cluster. the new switch can exchange CDP messages with the command switch and be proposed as a cluster candidate. there must have been no changes to the new switch configuration. In this way. the command switch changes the management VLAN for new switches when they are connected to the cluster. its management VLAN is changed to the cluster management VLAN when it is first added to the cluster. For information about the role management VLANs play in switch clusters. and there must be no config. This automatic change of the VLAN only occurs for new.text file. out-of-box switches that do not have a config. The command switch issues commands to change the management VLAN on the new switch to match the one in use by the cluster.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. If the cluster is configured with a management VLAN other than the default.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. Because the switch is new and unconfigured. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-5 . 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. it must be connected to a port that belongs to the cluster management VLAN. see the “Management VLAN” section on page 5-11.

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

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

Chapter 8 Configuring VLANs Assigning VLAN Port Membership Modes When a port belongs to a VLAN. For more information. “Assigning Static-Access Ports to a VLAN” section on page 8-10 The switch automatically transitions to VTP transparent mode (VTP is disabled). For more information. the switch learns and manages the addresses associated with the port on a per-VLAN basis. No VTP configuration is required. 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. VLAN Membership Combinations You can configure your switch ports in various VLAN membership combinations as listed in Table 8-3. 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. see the “Avoiding Configuration Conflicts” section on page 9-2. Some restrictions apply to multi-VLAN ports. 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. you can assign a static-access port to a VLAN and set the VTP mode to transparent to disable VTP.

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. Add. For more information. and configure the native VLAN for untagged traffic on the trunk port.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. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-9 . change the pruning-eligible list. change the pruning-eligible list. “Configuring Dynamic Ports on VMPS Clients” section on page 8-58 Configure the VMPS and the client with the same VTP domain name. modify. and configure the native VLAN for untagged traffic on the trunk port. You can define the allowed-VLAN list. “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. 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. You can change the VTP version on the switch and enable VTP pruning. “Configuring a Trunk You can define the allowed-VLAN Port” section on page 8-38 list. see the “Trunks Interacting with Other Features” section on page 8-37.

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

Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-11 . Multi-VLAN ports also respond to the STP messages generated by the different instances of STP in each VLAN. see the “Avoiding Configuration Conflicts” section on page 9-2. Intra-VLAN traffic stays within the boundaries of the respective VLANs as shown in Figure 8-2. A multi-VLAN port performs normal switching functions in all its assigned VLANs. For the restrictions that apply to multi-VLAN ports.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. all the VLANs to which the port belongs learn the address. when a multi-VLAN port receives an unknown Media Access Control (MAC) address. Connectivity between VLANs is through the router connected to the multi-VLAN port. 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. do not connect multi-VLAN ports to hubs or switches. For example. Connect multi-VLAN ports to routers or servers.

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

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

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

• When a multi-VLAN port is configured on a supported switch in VTP server mode or client mode. the switch cannot receive any VTP advertisements. the switch automatically changes to 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. the switch automatically changes from VTP server or client mode to VTP transparent mode. The switch then operates with the VLAN configuration that preceded the one that sent it into transparent mode. Otherwise. 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.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 “VTP Configuration Guidelines” section on page 8-18 provides tips and caveats for configuring VTP. VTP Advertisements Each switch in the VTP domain sends periodic global configuration advertisements from each trunk port to a reserved multicast address.

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

The broadcast traffic from Switch 1 is not forwarded to Switches 3. Figure 8-3 shows a switched network with VTP pruning enabled. VTP pruning blocks unneeded flooded traffic to VLANs on trunk ports that are included in the pruning-eligible list. VTP pruning is also supported with VTP version 1 and version 2. and unknown unicast traffic across all trunk links within a VTP domain even though receiving switches might discard them. Only VLANs included in the pruning-eligible list can be pruned. 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 .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. Without VTP pruning. Switch 5 Port 4 Flooded traffic is pruned. 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). 5. a switch floods broadcast. By default. VLANs 2 through 1001 are pruning eligible on Catalyst 2900 XL and Catalyst 3500 XL trunk ports. 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. the flooding continues. multicast.

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

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

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

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

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

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

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

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

Token Ring VLANs Although the Catalyst 2900 XL and Catalyst 3500 XL switches do not support Token Ring connections. TrBRF or TrCRF. FDDI network entity title [NET]. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-27 . Fiber Distributed Data Interface [FDDI]. 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.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. Token Ring. 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 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. For information on configuring VTP. • Before you can create a VLAN. The switch does not forward FDDI. Default VLAN Configuration Table 8-6 through Table 8-10 shows the default configuration for the different VLAN media types. FDDI-Net. 4 of the active VLANs (1002 to 1005) are reserved for Token Ring and FDDI. Note Catalyst 2900 XL and Catalyst 3500 XL switches support Ethernet interfaces exclusively. If VTP reports that there are 254 active VLANs. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-28 78-6511-05 . the switch must be in VTP server mode or VTP transparent mode. or TrBRF traffic. Because FDDI and Token Ring VLANs are not locally supported. TrCRF. but it does propagate the VLAN configuration through VTP. but some models only support 64 VLANs. you configure FDDI and Token Ring media-specific characteristics only for VTP global advertisements to other switches. • Switches running this IOS release do not support Token Ring or FDDI media. see the “Configuring VTP” section on page 8-20.

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

VTPv2 user-specified 1–4095 Parent VLAN VTPv1 default 0.10 SAID 100000+VLAN ID 1–4294967294 Ring Number VTPv1 default 0.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 default 4472 1500–18190 Translational bridge 1 0 0–1005 Translational bridge 2 0 0–1005 VLAN state active active. where xxxx is the VLAN ID No range 802. srt ARE max hops 7 0–13 STE max hops 7 0–13 Backup CRF disabled disable. suspend Bridge mode srb srb. enable Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-31 . VTPv2 user-specified 0–1005 MTU size VTPv1 default 1500.

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

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

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

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

or industry-standard IEEE 802. Figure 8-4 shows a network of switches that are connected by ISL trunks. the default protocol. 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 . 100BASE-T and Gigabit Ethernet trunks use Cisco Inter-Switch Link (ISL). Trunks carry the traffic of multiple VLANs and can extend VLANs across an entire network.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.1Q to carry traffic for multiple VLANs over a single link.

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

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

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

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

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

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

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

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

Frames with a priority value of 4 through 7 are sent to a high-priority queue. Gigabit Ethernet modules (802. CoS configures each transmit port (the egress port) with a normal-priority transmit queue and a high-priority transmit queue. You assign this value by using the CLI or CMS software. 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. 1. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-45 . Frames with a priority value of 0 through 3 are Catalyst 2900 XL Ethernet sent to a normal-priority queue.1p Class of Service Port Scheduling Each port on the switch has a single receive queue buffer (the ingress port) for incoming traffic. Table 8-12 shows the two categories of switch transmit queues. When an untagged frame arrives.1p user priority) Frames with a priority value of 0 through 3 are sent to a normal-priority queue.Chapter 8 Configuring VLANs Configuring 802. depending on the frame tag or the port information. Catalyst 3500 XL switches. Table 8-12 Transmit Queue Information Transmit Queue Category1 Transmit Queues Catalyst 2900 XL switches. it is assigned the value of the port as its port default priority. 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. modules (802.1p user priority) Frames with a priority value of 4 through 7 are sent to a high-priority queue.

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

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

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

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

• VLANs 8 through 10 are assigned a path cost of 30 on trunk port 2. In Figure 8-6. • VLANs 2 through 4 retain the default 100BASE-T path cost on trunk port 2 of 19. • VLANs 8 through 10 retain the default 100BASE-T path cost on trunk port 1 of 19. trunk ports 1 and 2 are 100BASE-T ports. and redundancy is maintained in the event of a lost link. because no loops exist.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. The VLANs keep the traffic separate. 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. STP does not disable the ports. 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 .

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

You can also use an explicit entry in the configuration table to deny access to specific MAC addresses for security reasons. When the VMPS receives a VQP request from a client switch. the VMPS verifies the requesting port against this group and responds as follows: – If the VLAN is allowed on the port. the VMPS sends a port-shutdown response. If the switch receives an access-denied response from the VMPS. 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. or SNMP. the VMPS takes one of the following actions: • If the assigned VLAN is restricted to a group of ports. • If the VLAN in the database does not match the current VLAN on the port and active hosts exist on the port. If the switch receives a port-shutdown response from the VMPS. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-52 78-6511-05 .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). If you enter the none keyword for the VLAN name. the VMPS sends an access-denied response. In response to a request. and the VMPS is in secure mode. Cluster Management software. the VMPS sends an access-denied or a port-shutdown response. it disables the port. and the VMPS is not in secure mode. it searches its database for a MAC-address-to-VLAN mapping. The port must be manually reenabled by using the CLI. the VMPS sends an access-denied or port-shutdown response. – If the VLAN is not allowed on the port. depending on the secure mode of the VMPS. The server response is based on this mapping and whether or not the server is in secure mode. it continues to block traffic from the MAC address to or from the port. the VMPS sends the VLAN name to the client in response. – If the VLAN is not allowed on the port. 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 either denies the request or shuts down the port (depending on the VMPS secure mode setting).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. it includes its domain name in the query packet to the VMPS to obtain its VLAN number. the port returns to an isolated state and does not belong to a VLAN. Any hosts that come online through the port are checked again with the VMPS before the port is assigned to a VLAN. however. 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. the switch does not forward traffic to or from this port until the VMPS provides the VLAN assignment. the VMPS sends the VLAN number for that port. If there is no match. 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. When the link comes up. If the client switch was previously configured. see the “How the VMPS Works” section on page 8-52. If the client switch was not previously configured. If the link goes down on a dynamic port. the VMPS shuts down a dynamic port if more than 20 hosts are active on the port. If there is a match. Multiple hosts (MAC addresses) can be active on a dynamic port if they are all in the same VLAN. For more information on possible VMPS responses. 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 file contains VMPS information. Use a Catalyst 5000 series switch as the VMPS. es3%Fa02 refers to fixed 10/100 port 2 on member switch 3. This ASCII text file is stored on a switch-accessible TFTP server that functions as a VMPS server. These naming conventions must be used in the VMPS database configuration file when it is configured to support a cluster. The following example shows a sample VMPS database configuration file as it appears on a Catalyst 5000 series switch. !vmps mode { open | secure } ! The default mode is open. For example. such as the domain name. and the MAC address-to-VLAN mapping. The VMPS database configuration file on the server must use the Catalyst 2900 XL and Catalyst 3500 XL convention for naming ports. !vmps fallback <vlan-name> !vmps no-domain-req { allow | deny } ! ! The default value is allow. If you do not configure a fallback VLAN and the MAC address does not exist in the database. !vmps domain <domain-name> ! The VMPS domain must be defined. Fa0/5 is fixed-port number 5. You can configure a fallback VLAN name. the VMPS sends an access-denied response. the command switch adds the name of the switch before the Fa.Chapter 8 Configuring VLANs How the VMPS Works VMPS Database Configuration File The VMPS contains a database configuration file that you create. If the switch is a cluster member. the fall-back VLAN name. it sends a port-shutdown response. If you connect a device with a MAC address that is not in the database. For example. 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 the VMPS is in secure mode. the VMPS sends the fallback VLAN name to the client. A Catalyst 2900 XL or Catalyst 3500 XL switch running this software release cannot act as the VMPS.

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.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 .eeff vlan-name Green address 1223.2.2.1.ccdd.6509.168.4455 vlan-name hardware address 0000.168.168.1 port Fa0/9 vmps-port-policies vlan-name Purple device 192.ba98.2233.2 port es5%Fa0/1 device 192.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.168.168.168.2.ba23.1 port Fa1/4 vmps-port-group “Executive Row” device 192.Chapter 8 Configuring VLANs How the VMPS Works ! address <addr> vlan-name <vlan_name> ! address 0012.1 port Fa1/3 device 172.2 port es5%Fa0/2 device 192.16.9abc vlan-name ExecStaff address fedc.5678.2.1.7654 vlan-name --NONE-address fedc.a080 vlan-name hardware address aabb.1.

You must disable port security on the port before it becomes dynamic. • The VTP management domain of the VMPS client and the VMPS server must be the same. the spanning-tree Port Fast feature is automatically enabled for that port. • Trunk ports cannot be dynamic ports. see the “VMPS Database Configuration File” section on page 8-54. For the cluster-based port-naming conventions. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-56 78-6511-05 . You must turn off trunking on the port before the dynamic access setting takes effect. • 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. • When you configure a port as dynamic. In this case. • Dynamic ports cannot be network ports or monitor ports. the switch retains the setting and applies it if the port is later configured as an access 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. • Secure ports cannot be dynamic ports. You can disable Port Fast mode on a dynamic port. The Port Fast mode accelerates the process of bringing the port into the forwarding state. but it is possible to enter the switchport access vlan dynamic interface configuration command for a trunk port.

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. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-57 . 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.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. In the display. Beginning in privileged EXEC mode. Step 2 vmps server ipaddress primary Enter the IP address of the switch acting as the primary VMPS server. check the VMPS Domain Server field. enter the address on the command switch. Step 4 end Return to privileged EXEC mode. 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.

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

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

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

22. Dynamic Port VLAN Membership Configuration Example Figure 8-7 shows a network with a VMPS server switch and VMPS client switches with dynamic ports. The VMPS shuts down the port to prevent the host from connecting to the network. • The Catalyst 5000 series Switch 3 and Switch 10 are secondary VMPS servers.20.db and is stored on the TFTP server with the IP address 172.7. • More than 20 active hosts reside on a dynamic port. In this example.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. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 8-61 . To reenable a shut-down dynamic port. these assumptions apply: • The VMPS server and the VMPS client are separate switches. and it will not allow the host to connect to the port. • The Catalyst 5000 series Switch 1 is the primary VMPS server. enter the interface configuration no shutdown command. • 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.

152 172.26.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.26.20.20.156 172.26.7 Client 172.157 Client Switch 9 172.153 Ethernet segment (Trunk link) Switch 4 172.150 172.26.26.159 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 8-62 78-6511-05 .151 Trunk port Secondary VMPS Server 2 Switch 3 Switch 5 Switch 6 Switch 7 Switch 8 Dynamic-access port 172.26.20.154 172.26.155 172.26.20.22.158 Trunk port Secondary VMPS Server 3 Switch 10 30769 End station 2 172.20.20.20.26.20.26.20.20.

refer to the switch hardware installation guide. • 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 .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.

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

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

Change to a profile using a lower QAM rate. 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. LRE link quality reduced in Cross-talk between the LRE links is causing all links to degrade. • The LRE link length and quality are close to the limit of operation. • The LRE link length and quality are close to the limit of operation. Ensure that the interleaver is set to maximum protection (the interleaver trades latency for noise immunity). Disable installations with bundled unused LRE ports by using the lre shutdown interface configuration cables command.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. Change to a profile using a lower QAM rate. Change to a profile using a lower QAM rate. If necessary. 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. Ensure that the interleaver is set to maximum protection (the interleaver trades latency for noise immunity). This situation means that the system is on the verge of generating CRC errors. • Interleaver is helping Reed-Solomon error correction to function correctly in a noisy environment. change to a profile using a lower QAM rate. Change to a profile using a lower quadrature amplitude modulation (QAM) rate. Interleaver introduces extra latency to increase noise margin. Reduce the effect of stubs or bridge taps by terminating them with 300-Ohm microfilters. Change to a profile using a lower QAM rate. which increases the noise margin. which increases the noise margin. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 9-4 78-6511-05 . 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 interleaver setting while ensuring the noise margin is adequate.

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

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

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

Cluster View displays the cluster as a double-switch icon and shows connections to devices outside the cluster (Figure 9-1). 54506 mcluster Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 9-8 78-6511-05 .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. Figure 9-1 Cluster View Right-click a device with a yellow label to display the device pop-up menu. and select Disqualification Code to display the reason it could not join the cluster. Right-click the device (yellow label). and select Disqualification Code. you can learn why by selecting Views > Toggle View from the menu bar in Cluster Builder.

This could be useful if you wanted to save configuration files on an external server in case a switch fails. You can then copy the configuration file to a replacement switch and avoid having to reconfigure the switch.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 .text flash:config.text from the host arno to the switch Flash memory: switch# copy tftp://arno//2900/config.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.8-SA html env_vars config. The following example uses the TFTP protocol to copy the file config.text 1728000 bytes total (456704 bytes free) The file system uses a URL-based file specification. 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.

This error message appears when a 4-MB Catalyst 2900 XL switch is upgraded to an image that is not supported on this hardware. as the file present on the Flash memory could be corrupted or invalid.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. perform an X-Modem upgrade. This also happens in cases when a 4-MB Catalyst 2900 XL switch is upgraded to an IOS 12. If setting the BOOT parameters to the correct file name does not resolve the issue. The switch in this case tries to load the image.. Getting “No Such File or Directory” error message during bootup. Download the IOS Image File by using X-Modem. After it has been saved. It might take a minute or two to save the configuration to Flash memory. Go to Setting BOOT Parameters at ROMMON (Switch: Prompt) to verify and set the BOOT parameters correctly.0 image. This example shows how to use this command to save your changes: switch# copy running-config startup-config Building configuration.. during or after the upgrade. but because this switch is not capable of loading this image. This usually happens due to a mistyped file name when setting the boot parameters. 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. 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. the bootup process fails.

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

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

• Member switches connected to the command switch through a secured port can lose connectivity if the port is disabled due to a security violation. see the “Management VLAN” section on page 5-11. Secured ports are described in the “Enabling Port Security” section on page 7-15. and the member switch is forwarding packets normally. 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. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 9-13 . see the “Enabling a Network Port” section on page 7-7. For information on the network port feature. For more information. If you are unable to maintain management contact with a member. • Member switches must connect to the command switch through a port that belongs to the same management VLAN.Chapter 9 Troubleshooting Recovery Procedures Recovery Procedures The recovery procedures in this section require that you have physical access to the switch. 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.

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

and physically remove it from the cluster. Step 7 End with CNTL/Z. refer to the switch installation guide. one per line. Step 6 From privileged EXEC mode. by using Telnet. For details about using the console port. Step 2 Use a member switch in place of the failed command switch. Step 4 At the switch prompt. change to privileged EXEC mode: Switch> enable Switch# Step 5 Enter the password of the failed command switch. enter global configuration 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 . You can access the CLI by using the console port or. From global configuration mode. if an IP address has been assigned to the switch. and duplicate its connections to the cluster members. Switch(config)# no cluster commander-address Step 8 Return to privileged EXEC mode. remove previous command-switch information from the switch.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. Switch# config terminal Enter configuration commands.

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

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

Step 25 Click Cluster Management. and select Enabled from the Command Switch drop-down list. and you should enter it when candidate switches are proposed for cluster membership. and press Return.153. and enter the switch IP address that you entered in Step 11.20. and begin again at Step 1. press Return. The password of the failed command switch is still valid for the cluster. Step 24 Display the VSM Home page for the switch. CMS prompts you to add candidate switches. enter N at the prompt.Chapter 9 Troubleshooting Recovery Procedures ip default-gateway 172. • If the information is not correct. enter Y at the prompt. and display Cluster Builder. • If the information is correct. Use this configuration? [yes/no]: y Step 23 Start your browser. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 9-18 78-6511-05 .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.

default gateway. Default settings are in square brackets ’[]’. by using Telnet. From privileged EXEC mode. 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 . For details about using the console port. and press Return: Enter IP address: ip_address Step 8 Enter the subnet mask. subnet mask. and password. Continue with configuration dialog? [yes/no]: Step 6 Enter Y at the first prompt. change to privileged EXEC mode: Switch> enable Switch# Step 4 Enter the password of the failed command switch. Step 3 At the switch prompt. Switch# setup --. and press Return. Step 2 Start a CLI session on the new command switch. Use ctrl-c to abort configuration dialog at any prompt. if an IP address has been assigned to the switch. enter setup. Step 5 Use the setup program to configure the switch IP information.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. You can access the CLI by using the console port or. Continue with configuration dialog? [yes/no]: y Step 7 Enter the switch IP address.System Configuration Dialog --At any point you may enter a question mark ’?’ for help. refer to the switch hardware installation guide. and duplicate its connections to the cluster members. This program prompts you for an IP address.

If you enter N. 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 . 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. Enter a host name: host_name Step 12 Note Enter the password of the failed command switch.Chapter 9 Troubleshooting Recovery Procedures Step 10 Enter the IP address of the default gateway. IP address of the default gateway: ip_address Step 11 Note Enter a host name for the switch. The password can be from 1 to 25 alphanumeric characters. and press Return: Enter Telnet password: telnet_password Step 15 Note Enter Y to configure the switch as the cluster command switch. is case sensitive. but ignores leading spaces. Enter N to configure it as a member switch or as a standalone switch. the host name is limited to 28 characters. allows spaces. on a member switch to 31 characters. Do not use -n. allows spaces. but ignores leading spaces. In this case. the switch appears as a candidate switch in Cluster Builder. can start with a number. where n is a number. and press Return. as the last character in a host name for any switch. and press Return. the message in Step 20 is not displayed. is case sensitive. and press Return. On a command switch. Enter the Telnet password.

Enter cluster name: cls_name Note Step 17 The cluster name can be 1 to 31 alphanumeric characters.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. Enter it when candidate switches are proposed for cluster membership. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 9-21 . • If the information is correct. Use this configuration? [yes/no]: y Step 19 Start your browser. and click OK. Step 20 Click Cluster Manager Suite or Visual Switch Manager. enter N at the prompt. and enter the switch IP address that you entered in Step 7. dashes. press Return.153. The password of the failed command switch is still valid for the cluster. and display Cluster Builder.255.20. and press Return. and press Return.255. It prompts you to add the candidate switches. The initial configuration is displayed: The following configuration command script was created: ip subnet-zero interface VLAN1 ip address 172.36 255.20. • If the information is not correct.153. and begin again at Step 1. or underscores. enter Y at the prompt.0 ip default-gateway 172.Chapter 9 Troubleshooting Recovery Procedures Step 16 Assign a name to the cluster.

For more information. You can configure member switches through the console-port CLI. and Telnet after you assign an IP address to them. 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.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. The password you enter when you log in to the command switch gives you access to member switches. You can release the Mode button a second or two after the LED above port 1X goes off. Step 1 Connect a terminal or PC with terminal emulation software to the console port. For more information. you can use the command-switch password to recover. If the command switch fails and there is no standby command switch. see the “Recovering from a Command Switch Failure” section on page 9-14. Several lines of information about the software appear. Step 3 Unplug the switch power cord. and they can still be managed through normal standalone means. The following commands will initialize the flash file system. Step 4 Press the Mode button. Recovering from a Lost or Forgotten Password Follow the steps in this procedure if you have forgotten or lost the switch password. refer to the switch installation guide. Step 2 Set the line speed on the emulation software to 9600 baud. and at the same time. reconnect the power cord to the switch. 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 . as do instructions: The system has been interrupted prior to initializing the flash file system. member switches continue forwarding among themselves. HTML.

This file contains the password definition.old Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 9-23 .old. 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.text flash:config.text. Change the emulation software line speed to match that of the switch console port.text.text 1728000 bytes total (456704 bytes free) Step 9 Rename the configuration file to config. it has been reset to that particular speed.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.8-SA 01:23:24 html 00:01:19 env_vars 06:55:51 config. switch: rename flash:config.

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

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

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

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

a protocol. Table A-1 lists the system facility codes. 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 .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. or a module of the system software. . A facility can be a hardware device.

Table A-2 lists the message severity levels. is represented as [dec]. Table A-3 lists the variable fields in messages. Because the information in these variable fields changes from message to message. 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 . 7 – debugging Message that appears during debugging only. The lower the number. 1 – alert Immediate action required. • MNEMONIC is a code that uniquely identifies the error message. network addresses. 6 – informational Informational message only. 2 – critical Critical condition.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. it is represented here by short strings enclosed in square brackets ([ ]). the more serious the situation. This portion of the message sometimes contains detailed information about the event. A decimal number. 3 – error Error condition. Table A-2 Message Severity Levels Severity Level Description 0 – emergency System is unusable. for example. 5 – notification Normal but significant condition. including terminal port numbers. • Message-text is a text string describing the condition. 4 – warning Warning condition. or addresses that correspond to locations in the system memory address space.

Appendix A System Error Messages Error Message Traceback Reports The following is a sample system error message: %LINK-2-BADVCALL: Interface [chars]. SLOT5. The following sample message includes traceback information: -Process= "Exec".) Error Message Traceback Reports Some messages describe internal errors and contain traceback information. (For example. This information is very important and should be included when you report a problem to your technical support representative. It is always shown as MSG. MSG is a mnemonic that means that this is a message. 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 . level= 0. undefined entry point Some error messages also indicate the card and slot reporting the error. It is shown as SLOT followed by a number. 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. SLOT means that the slot number of the card reporting the error.

Action No action is required. Within each facility. and [inet] is the Internet address of the command switch. Each message is followed by an explanation and a recommended action. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 A-5 . Action Extract the module. CHASSIS-5-BLADE_EXTRACT Explanation The message means that the hot-swap switch has been pressed. CMP Messages This section contains the Cluster Membership Protocol (CMP) error messages. Chassis Message This section contains the Chassis error message. 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.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-5-ADD: The Device is added to the cluster (Cluster Name:[chars]. and 7 is the lowest severity level. CMDR IP Address [inet]) Explanation The message means that the device is added to the cluster: [chars] is the cluster name. Action No action is required.

Action No action is required. replace the switch. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide A-6 78-6511-05 . Environment Messages This section contains the Environment error messages. Replace the switch at your convenience. The Catalyst 3524-PWR XL switch can operate normally with one failed fan. • Make sure fan intake and exhaust areas are clear.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. or use the show env privileged EXEC command to check if a fan on the switch has failed. If it does: • Place the switch in an environment that is within 32 to 113°F (0 to 45°C). Action Use the show env command to check if an overtemperature condition exists. This message is available only on the Catalyst 3524-PWR XL switch. If a multiple-fan failure is causing the switch to overheat. ENVIRONMENT-2-OVER_TEMP Explanation This message means that an overtemperature condition is detected. Action Either check the switch itself. This message is available only on the Catalyst 3524-PWR XL switch. ENVIRONMENT-2-FAN_FAULT Explanation This message means that an internal fan fault is detected.

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

or by someone disconnecting the CPE LRE cable or cycling its power. it could mean a physical disconnection at the switch or CPE or a loss of power to the CPE. However. profile failure Explanation When the switch reloads or when the LRE link is lost. It might also be caused by any substantial interruption of the signal or cabling between the LRE port and the CPE. if the LRE link does not go back up within a minute or so.Appendix A System Error Messages Error Message and Recovery Procedures Link Message This section contains the Link error message. 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. LINK-4-ERROR [chars] is experiencing errors. the LRE port first attempts to briefly establish link with the CPE in a common. 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 . LINK-3-ERROR messages are more severe and are logged at the Error level. LRE Link Messages This section contains the LRE Link error messages. ignore this message. reconfiguring a profile in use by this port. which is logged at the Warning level. This could be the result of reconfiguring the port. Explanation This messages means that excessive errors have occurred on this interface: [char] is the interface. Action Check for duplex mismatches between both ends of the link. Note The previous error is a LINK-4-ERROR message. Action If someone is reconfiguring the port or the profile in use. a physical disconnection or reconnection of the LRE connector on the switch. reduced rate mode. LRE_LINK-3-PROFILE_FAILURE: Interface.

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

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

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. Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 A-11 . re-enable the port by using port-configuration commands.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 .

I N D E X member switches 8-35 Numerics MIB files 4-7 1000BASE-T module. secure 7-15 char. variable field A-3 chars. 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 . 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. variable field A-3 dec. variable field A-3 hex. 6-67 address abbreviations count. Catalyst 2900 XL 1-12 MIB objects 4-6. 4-7 MIBs files 4-7 A objects 4-6 aaa (authentication. variable field A-3 inet. authorization.

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. configuring 6-57 trunks and other features 8-37 dynamic addresses. displaying 5-19 NTP 6-18 TACACS+ 6-61 authorization. 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.Index described 6-56 ADSL 1-6 removing 6-58 advertisements. 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. in RMON 4-6 discovering 6-45. TACACS+ 6-61 automatic discovery. accelerating 6-26 adding secure 6-58 aging time. changing address 6-57 aging time 6-57 alarms group. 6-56 allowed-VLAN list 8-40 tables. managing 6-56 American National Standards Institute secure see ANSI adding 6-58 described 6-56. 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 . VTP 8-15 MAC aging.

4-8 characteristics 5-3 Class of service suggested 5-14 see CoS why not added 9-8 cascaded configuration. 4-1. graphing 2-9.com xxii buttons. configuring 6-18 discovering candidates with 5-4 broadcast messages. 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. 1-18 Cisco Discovery Protocol cabling. 2-35. UplinkFast 6-26 Catalyst 3524-PWR XL 7-17 cautions xviii Cisco LRE 48 POTS Splitter (PS-1M-LRE-48) 1-6. 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. 5-1 Cisco. 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 . 7-22 Cisco Access Analog Trunk Gateway 1-18 Cisco Access Digital Trunk Gateway 1-18 C Cisco CallManager software 1-16. 2-20 CDP 1-3 BPDU message interval 6-40 configuring 6-22 broadcast client mode.Index caveats B password and privilege level 5-9 bandwidth. CMS window 2-33 Cisco 575-LRE CPE 1-6.

switch see also candidates. 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. command switch. 2-21 polling interval 2-26 pop-up menus 2-29. 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.Index IOS Release 12. changing 8-4 managing 5-21. displaying 5-19 LRE profile considerations 5-13. 3-1 menu bar 2-14 managing cluster members with 5-21 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. 2-7 toolbar icons 2-17 cluster member characteristics 5-3 Cluster Membership Protocol see CMP system error messages A-5 clusters.0 documentation xvi. member switches. 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 . illustrated 6-27 inventory. 7-25 management VLAN. 2-19 saving changes 3-10 port pop-up menu 2-18 using 3-1 toolbar 2-17 client mode. 2-3 overview 3-1 pop-up menus 2-18.

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. 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. 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.

9-13 and management 4-6 default VLAN 8-28 and managing with SNMP 5-22 file. 9-14. default 8-20 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide IN-6 78-6511-05 . 5-17 no 3-5 see also candidates. 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. 3-6 requirements 5-2 name 5-18 standby 5-5. 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. 6-19 redisplaying 3-5 SNMP 5-10. listing 3-6 preempt 5-18 community strings rcommand 5-21 configuring 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.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. member switches port block 8-38 command variables. VMPS database 8-54 characteristics 5-2 files.

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. 6-45 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 IN-7 .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. 7-3 CLI 3-10 dynamic ports on VMPS clients 8-58 CMS 2-37 dynamic VLAN membership 8-57 configuration examples. saving duplex 7-2. 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. DHCP 6-10 passwords 6-15 configuring ports 802. 7-3 clusters 5-13 standby command groups 5-17 community strings 5-10.Index configuration changes.

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-32 customer premises equipment VTP 8-18. configuration 9-2.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. VTP 8-27. 7-10 device pop-up menu 2-19 configuring 8-44 priority 7-19 CPE 1-6. 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. 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 . 8-32 consistency checks in VTP version 2 8-16 date. resetting to 3-5 for examples xviii default settings. 8-20 see CPE VTP client mode 8-22 VTP server mode 8-21 VTP transparent mode 8-10. 9-13 database. 8-23 D conflicts. 1-20.

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. 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. 6-4 documentation. configuring 8-58 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 IN-9 .0 xvi. 7-3 SNMP 6-18 settings.Index DHCP 1-3. 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. IOS Release 12. 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. 3-1 configuring relay device 6-9 documentation.

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 .Index dynamic port VLAN membership port security 7-14. 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. 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. 7-25 egress port scheduling 8-45 Ethernet MANs 1-23 eligible switches 5-17 Ethernet VLAN.

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. accessing MIB files Gigabit Ethernet Flash memory.Index port groups 7-10 F restrictions 7-11 facility codes A-2 resuming 7-7 description A-2 source-based. illustrated 6-27 flooded traffic. configuring flow control on 7-3 flooding controls. configuring 7-3 settings 7-2 forwarding trunks 8-36 controlling (SNMP) 5-22 delay 6-38. 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. web xxi get-request operation 4-8 File Transfer Protocol get-response operation 4-8 see FTP. 9-10 clusters. reducing 7-6 ports. 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. static address 6-59 Fast EtherChannel port groups. files in 9-9. 6-41 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 IN-11 . configuring 7-4 port settings 7-2 flow control. illustrated 7-11 table A-2 see also broadcast storm control fan fault indication 2-6 forwarding.

8-4 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide IN-12 78-6511-05 . 2-20 interaction with other features 8-37 poll result 4-8 native VLAN for untagged traffic 8-43 overview 8-36 IEEE 802.Index Gigabit Interface Converter I see GBICs GigaStack system error messages A-7 IEEE 802. 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. 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. in RMON 4-6 interface configuration mode 3-4 hold-time.0 documentation xvi.1p 7-17 global configuration mode 3-4 IEEE 802. modifying 6-48 interfaces hops.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. 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.1Q configuration considerations 8-37 graphs bandwidth 2-9. 3-5 see ISDN history group. limit on dynamic ports 8-61 IOS Release 12. getting 2-17.

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. displaying 5-20 link pop-up menu Cluster Builder 2-30 J link system error messages A-8 Java plug-in configuration 2-1. 2-12. 2-11. 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. 5-1 lists 2-32 load sharing STP. 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. 4-1.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. 2-35.

6-56 LRE ports MAC address tables. 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. 8-4 LRE link switch clusters 5-11 description 7-22 MANs. 7-25 CLI 3-1 CMS 2-1 management VLAN duplex mode 7-25 changes. 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.Index location of switches. understanding 8-4 flow control 7-25 changing 5-12. 8-4. 8-5 speed 7-25 configuring 8-6 statistics 7-26 IP address 5-11. 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 . displaying 5-19 lre profile command 7-28 login authentication. configuring 6-64 lre profile global command 7-27 Long-Reach Ethernet lre shutdown command 7-26 see LRE technology LRE technology 1-6.

autonegotiation 9-3 member switches mnemonic code A-3 accessing 8-35 Mode button 2-9 adding model numbers. 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. 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. 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 . VLAN port 8-7 mismatches. 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.Index membership mode. inherited 5-8 Modify button 2-33 recovering from lost connectivity 9-13 modules. phone 1-20 assigning to VLANs 8-10.

switch 2-6 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide IN-16 78-6511-05 . 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.Index MVR 4-13.

8-38 TACACS+ server 6-61 port-connection information. 8-50 STP parameter 8-56 PBX 1-20 port groups plain old telephone service see POTS splitters planning considerations. switch clusters 5-4 and trunks 8-38 configuring static addresses (EtherChannel) 6-61 host names 5-10 creating EtherChannel 7-10. 7-10 network port 5-12 see also ports port membership modes. 6-43. displaying 5-20 VTP domain 8-18 Port Fast patch panel 1-20 enabling 6-42 path cost 6-42. 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.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. 7-12 IP addresses 5-8 destination-based 6-61. 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. 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 .

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. 8-44.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. 8-12 Cluster Manager 2-18 network 8-37 VSM 2-18 priority 6-43. conflicting 9-2 homologated 1-20 flooded traffic 7-6 nonhomologated 1-20 forwarding. 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. 8-8. 8-36 hosts on 8-61 VLAN assignments 8-10. 8-11. resuming 7-7 power. setting and checking 7-2 protected 7-13 static-access 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 . 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-10.

displaying switch 5-19 see PBX private mode profiles 7-23 LRE-10 7-24 protected ports 1-2. 1-18. 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. 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.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. 5-21 PUBLIC-ETSI 7-24 setting 6-15 specifying 6-15 Public Switched Telephone Network see PSTN profiles. related xix command switch 5-21 public mode profiles 7-23 inherited 5-8 PUBLIC-ANSI 7-24 mapping on member switches 5-9. 1-20. 8-46 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 IN-19 . LRE 7-22 considerations 7-24 default 7-24 assigning 7-28 Q QoS egress port scheduling 8-45 ingress port scheduling 8-45. 7-23 privilege levels publications.

switch software 4-2 removing 6-59 remote devices without autonegotiation. configuring 6-9 described 6-58 releases. displaying 5-19 server. 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. 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. 6-60 retry count.Index RPS LED 2-8 R RPS 300 2-9 rcommand 5-21 RPS 600 2-8 reconfirmation interval. domain name 6-8 router hold-time. address 7-14 Serial Line Internet Protocol see SLIP serial numbers. supported groups 4-6 root guard 6-44. 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. 6-45 security port 7-14 TACACS+ 6-61 violations. modifying 6-48 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide IN-20 78-6511-05 . changing 8-60 RMON.

6-4 set-request operation 4-8 enabling and disabling 6-18 settings management. using 4-6 default. 6-20 STP default 6-26 SNMP Configuration window 2-17 set-top box. changing 4-9 managing clusters with 5-22 duplex 7-2. 7-3 network management platforms 4-6 Gigabit Ethernet port 7-2 RMON groups 4-6 speed 7-3 trap managers. BOOTP 1-3. 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. displaying 5-19 SPAN 7-16 SLIP 6-65 configuring 6-19 joining standby groups 5-3 source-based port groups 6-61. 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 . VTP 8-14 configuring for single switches 6-18 servers.Index server mode. configuring 6-19 STP 6-27 trap types 6-19. 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. 7-10 see SNMP community strings software enabling 7-16 ports. 7-27.

in RMON 4-6 STAT mode LED 2-10 port grouping parameters 7-11. 6-27 STP implementation. 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. 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. unpredictable 8-11 UplinkFast 6-28. 8-2 STP switch priority 6-39 behavior. 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. 8-48 port states 6-41 redundant connectivity 6-25 redundant links with UplinkFast 6-28 root guard 6-44.Index spanning-tree rootguard command 6-45 configuring 6-24. 6-45 settings 6-26. VTP 8-26 statistics group. 5-17 implementation type 6-39 priority. changing 6-39 storm control system error messages A-11 supported number of spanning-tree instances 6-24. 6-59 removing 6-60 see also static address static address forwarding 6-59 static address forwarding restrictions 7-11 statistics. setting 7-2. 8-38 port priority 6-43. 6-26 speed. 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 .

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.

VTP 8-14. creating 6-62 blocking flooded 7-6 starting accounting 6-66 forwarding. 6-67 reducing flooded 7-4. 7-7 tacacs-server timeout command 6-63 transmit queue 8-45 Telnet transparent mode. 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. 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-63 monitoring 7-16 tacacs-server retransmit command 6-63. 6-19 TFTP server.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. 8-30 configuring 8-38 TrCRF 8-16. 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. CMS 2-24 configuring 6-61 traceback reports A-4 initializing 6-64 traffic server.

1Q 8-36. 6-56 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-05 IN-25 . overview 8-36 VLAN database mode 3-3 VLAN ID. 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.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. 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. 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. discovering 6-45. 8-37 enabling 6-30 interacting with other features 8-37 redundant links 6-28 ISL 8-36 URLs.

Index VLAN Management Policy Server see VMPS native. 8-12 reconfirmation interval. 8-35 confirming 8-59 STP parameters. 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.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. 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 8-59 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide IN-26 78-6511-05 . 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. 8-34.

2-3 Token Ring support 8-16 port pop-up menu 2-18 transparent mode. 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. 2-7 overview 8-17 home page 2-4 pruning-eligible list. 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. configuring 7-17 configuring 8-22 voice traffic 7-21 server 8-14.Index reconfirming membership 8-59 described 8-12 retry count. 8-14. changing 8-42 menu bar 2-14 statistics 8-26 overview 2-2. 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. configuring 8-23 privilege level 6-16 traps 6-19 toolbar 2-17 using 8-12 toolbar icons 2-17 version. 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 . changing 8-60 disabling 8-23 server address.

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.Index VVID 1-5.