Cisco WS-C2960-24LC-S, WS-C2960S-24TD-L, WS-C2960S-48LPD-L, Catalyst 2960 Software Configuration Manual

Americas Headquarters

Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: [phone]

800 553-NETS (6387)

Fax: [phone]

Catalyst 2960 Switch
Software Configuration Guide

Cisco IOS Release 12.2(40)SE
Revised September 2007

Text Part Number: OL-8603-04

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.

CCVP, the Cisco logo, and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of
Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo,
Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step,
Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study,
LightStream, Linksys, MeetingPlace, MGX, Networking Academy, Network Registrar, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase
Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship
between Cisco and any other company. (0708R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the
document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

Catalyst 2960 Switch Software Configuration Guide

© 2006-2007 Cisco Systems, Inc. All rights reserved.

iii

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

CONTENTS

Preface xxix

Audience xxix

Purpose xxix

Conventions xxx

Related Publications xxx

Obtaining Documentation, Obtaining Support, and Security Guidelines xxxii

CHAPTER

1 Overview 1-1

Features 1-1

Ease-of-Deployment and Ease-of-Use Features 1-1
Performance Features 1-2
Management Options 1-3
Manageability Features 1-4
Availability and Redundancy Features 1-6
VLAN Features 1-7
Security Features 1-7
QoS and CoS Features 1-9
Monitoring Features 1-10

Default Settings After Initial Switch Configuration 1-10

Network Configuration Examples 1-12

Design Concepts for Using the Switch 1-12
Small to Medium-Sized Network Using Catalyst 2960 Switches 1-16
Long-Distance, High-Bandwidth Transport Configuration 1-17

Where to Go Next 1-18

CHAPTER

2 Using the Command-Line Interface 2-1

Understanding Command Modes 2-1

Understanding the Help System 2-3

Understanding Abbreviated Commands 2-4

Understanding no and default Forms of Commands 2-4

Understanding CLI Error Messages 2-5

Using Configuration Logging 2-5

Contents

iv

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Using Command History 2-6

Changing the Command History Buffer Size 2-6
Recalling Commands 2-6
Disabling the Command History Feature 2-7

Using Editing Features 2-7

Enabling and Disabling Editing Features 2-7
Editing Commands through Keystrokes 2-7
Editing Command Lines that Wrap 2-9

Searching and Filtering Output of show and more Commands 2-10

Accessing the CLI 2-10

Accessing the CLI through a Console Connection or through Telnet 2-10

CHAPTER

3 Assigning the Switch IP Address and Default Gateway 3-1

Understanding the Boot Process 3-1

Assigning Switch Information 3-2

Default Switch Information 3-3
Understanding DHCP-Based Autoconfiguration 3-3

DHCP Client Request Process 3-4

Configuring DHCP-Based Autoconfiguration 3-5

DHCP Server Configuration Guidelines 3-5
Configuring the TFTP Server 3-6
Configuring the DNS 3-6
Configuring the Relay Device 3-6
Obtaining Configuration Files 3-7
Example Configuration 3-8

Manually Assigning IP Information 3-10

Checking and Saving the Running Configuration 3-10

Modifying the Startup Configuration 3-11

Default Boot Configuration 3-12
Automatically Downloading a Configuration File 3-12
Specifying the Filename to Read and Write the System Configuration 3-12
Booting Manually 3-13
Booting a Specific Software Image 3-14
Controlling Environment Variables 3-14

Scheduling a Reload of the Software Image 3-16

Configuring a Scheduled Reload 3-16
Displaying Scheduled Reload Information 3-17

Contents

v

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

CHAPTER

4 Configuring Cisco IOS CNS Agents 4-1

Understanding Cisco Configuration Engine Software 4-1

Configuration Service 4-2
Event Service 4-3

NameSpace Mapper 4-3

What You Should Know About the CNS IDs and Device Hostnames 4-3

ConfigID 4-3
DeviceID 4-4
Hostname and DeviceID 4-4
Using Hostname, DeviceID, and ConfigID 4-4

Understanding Cisco IOS Agents 4-5

Initial Configuration 4-5
Incremental (Partial) Configuration 4-6
Synchronized Configuration 4-6

Configuring Cisco IOS Agents 4-6

Enabling Automated CNS Configuration 4-6
Enabling the CNS Event Agent 4-8
Enabling the Cisco IOS CNS Agent 4-9

Enabling an Initial Configuration 4-9
Enabling a Partial Configuration 4-11

Displaying CNS Configuration 4-12

CHAPTER

5 Clustering Switches 5-1

Understanding Switch Clusters 5-1

Cluster Command Switch Characteristics 5-3
Standby Cluster Command Switch Characteristics 5-3
Candidate Switch and Cluster Member Switch Characteristics 5-3

Planning a Switch Cluster 5-4

Automatic Discovery of Cluster Candidates and Members 5-4

Discovery Through CDP Hops 5-5
Discovery Through Non-CDP-Capable and Noncluster-Capable Devices 5-6
Discovery Through Different VLANs 5-6
Discovery Through Different Management VLANs 5-7
Discovery of Newly Installed Switches 5-8

HSRP and Standby Cluster Command Switches 5-9

Virtual IP Addresses 5-10
Other Considerations for Cluster Standby Groups 5-10
Automatic Recovery of Cluster Configuration 5-11

IP Addresses 5-12

Contents

vi

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Hostnames 5-12
Passwords 5-13
SNMP Community Strings 5-13
TACACS+ and RADIUS 5-14
LRE Profiles 5-14

Using the CLI to Manage Switch Clusters 5-14

Catalyst 1900 and Catalyst 2820 CLI Considerations 5-14

Using SNMP to Manage Switch Clusters 5-15

CHAPTER

6 Administering the Switch 6-1

Managing the System Time and Date 6-1

Understanding the System Clock 6-1
Understanding Network Time Protocol 6-2
Configuring NTP 6-3

Default NTP Configuration 6-4
Configuring NTP Authentication 6-4
Configuring NTP Associations 6-5
Configuring NTP Broadcast Service 6-6
Configuring NTP Access Restrictions 6-8
Configuring the Source IP Address for NTP Packets 6-10
Displaying the NTP Configuration 6-11

Configuring Time and Date Manually 6-11

Setting the System Clock 6-11
Displaying the Time and Date Configuration 6-12
Configuring the Time Zone 6-12
Configuring Summer Time (Daylight Saving Time) 6-13

Configuring a System Name and Prompt 6-14

Default System Name and Prompt Configuration 6-15
Configuring a System Name 6-15
Understanding DNS 6-15

Default DNS Configuration 6-16
Setting Up DNS 6-16
Displaying the DNS Configuration 6-17

Creating a Banner 6-17

Default Banner Configuration 6-17
Configuring a Message-of-the-Day Login Banner 6-18
Configuring a Login Banner 6-19

Managing the MAC Address Table 6-19

Building the Address Table 6-20

Contents

vii

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

MAC Addresses and VLANs 6-20
Default MAC Address Table Configuration 6-21
Changing the Address Aging Time 6-21
Removing Dynamic Address Entries 6-22
Configuring MAC Address Notification Traps 6-22
Adding and Removing Static Address Entries 6-24
Configuring Unicast MAC Address Filtering 6-25
Displaying Address Table Entries 6-26

Managing the ARP Table 6-26

CHAPTER

7 Configuring SDM Templates 7-1

Understanding the SDM Templates 7-1

Configuring the Switch SDM Template 7-2

Default SDM Template 7-2
SDM Template Configuration Guidelines 7-2
Setting the SDM Template 7-2

.Displaying the SDM Templates 7-3

CHAPTER

8 Configuring Switch-Based Authentication 8-1

Preventing Unauthorized Access to Your Switch 8-1

Protecting Access to Privileged EXEC Commands 8-2

Default Password and Privilege Level Configuration 8-2
Setting or Changing a Static Enable Password 8-3
Protecting Enable and Enable Secret Passwords with Encryption 8-3
Disabling Password Recovery 8-5
Setting a Telnet Password for a Terminal Line 8-6
Configuring Username and Password Pairs 8-6
Configuring Multiple Privilege Levels 8-7

Setting the Privilege Level for a Command 8-8
Changing the Default Privilege Level for Lines 8-9
Logging into and Exiting a Privilege Level 8-9

Controlling Switch Access with TACACS+ 8-10

Understanding TACACS+ 8-10
TACACS+ Operation 8-12
Configuring TACACS+ 8-12

Default TACACS+ Configuration 8-13
Identifying the TACACS+ Server Host and Setting the Authentication Key 8-13
Configuring TACACS+ Login Authentication 8-14
Configuring TACACS+ Authorization for Privileged EXEC Access and Network Services 8-16

Contents

viii

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Starting TACACS+ Accounting 8-17

Displaying the TACACS+ Configuration 8-17

Controlling Switch Access with RADIUS 8-17

Understanding RADIUS 8-18
RADIUS Operation 8-19
Configuring RADIUS 8-19

Default RADIUS Configuration 8-20
Identifying the RADIUS Server Host 8-20
Configuring RADIUS Login Authentication 8-23
Defining AAA Server Groups 8-25
Configuring RADIUS Authorization for User Privileged Access and Network Services 8-27
Starting RADIUS Accounting 8-28
Configuring Settings for All RADIUS Servers 8-29
Configuring the Switch to Use Vendor-Specific RADIUS Attributes 8-29
Configuring the Switch for Vendor-Proprietary RADIUS Server Communication 8-31

Displaying the RADIUS Configuration 8-31

Configuring the Switch for Local Authentication and Authorization 8-32

Configuring the Switch for Secure Shell 8-33

Understanding SSH 8-33

SSH Servers, Integrated Clients, and Supported Versions 8-33
Limitations 8-34

Configuring SSH 8-34

Configuration Guidelines 8-34
Setting Up the Switch to Run SSH 8-35
Configuring the SSH Server 8-36

Displaying the SSH Configuration and Status 8-37

Configuring the Switch for Secure Socket Layer HTTP 8-37

Understanding Secure HTTP Servers and Clients 8-37

Certificate Authority Trustpoints 8-38
CipherSuites 8-39

Configuring Secure HTTP Servers and Clients 8-40

Default SSL Configuration 8-40
SSL Configuration Guidelines 8-40
Configuring a CA Trustpoint 8-40
Configuring the Secure HTTP Server 8-41
Configuring the Secure HTTP Client 8-43

Displaying Secure HTTP Server and Client Status 8-43

Configuring the Switch for Secure Copy Protocol 8-43

Information About Secure Copy 8-44

Contents

ix

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

CHAPTER

9 Configuring IEEE 802.1x Port-Based Authentication 9-1

Understanding IEEE 802.1x Port-Based Authentication 9-1

Device Roles 9-2
Authentication Process 9-3
Authentication Initiation and Message Exchange 9-5
Ports in Authorized and Unauthorized States 9-7
IEEE 802.1x Host Mode 9-7
IEEE 802.1x Accounting 9-8
IEEE 802.1x Accounting Attribute-Value Pairs 9-8
Using IEEE 802.1x Authentication with VLAN Assignment 9-9
Using IEEE 802.1x Authentication with Guest VLAN 9-11
Using IEEE 802.1x Authentication with Restricted VLAN 9-12
Using IEEE 802.1x Authentication with Inaccessible Authentication Bypass 9-13
Using IEEE 802.1x Authentication with Voice VLAN Ports 9-14
Using IEEE 802.1x Authentication with Port Security 9-14
Using IEEE 802.1x Authentication with Wake-on-LAN 9-15
Using IEEE 802.1x Authentication with MAC Authentication Bypass 9-16
Using Network Admission Control Layer 2 IEEE 802.1x Validation 9-17
Using Web Authentication 9-17

Web Authentication with Automatic MAC Check 9-18

Configuring IEEE 802.1x Authentication 9-18

Default IEEE 802.1x Authentication Configuration 9-19
IEEE 802.1x Authentication Configuration Guidelines 9-20

IEEE 802.1x Authentication 9-20
VLAN Assignment, Guest VLAN, Restricted VLAN, and Inaccessible Authentication

Bypass

9-21

MAC Authentication Bypass 9-22
Upgrading from a Previous Software Release 9-22
Configuring IEEE 802.1x Authentication 9-22
Configuring the Switch-to-RADIUS-Server Communication 9-24
Configuring the Host Mode 9-25
Configuring Periodic Re-Authentication 9-25
Manually Re-Authenticating a Client Connected to a Port 9-26
Changing the Quiet Period 9-26
Changing the Switch-to-Client Retransmission Time 9-27
Setting the Switch-to-Client Frame-Retransmission Number 9-28
Setting the Re-Authentication Number 9-28
Configuring IEEE 802.1x Accounting 9-29
Configuring a Guest VLAN 9-30
Configuring a Restricted VLAN 9-31

Contents

x

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Configuring the Inaccessible Authentication Bypass Feature 9-33
Configuring IEEE 802.1x Authentication with WoL 9-35
Configuring MAC Authentication Bypass 9-36
Configuring NAC Layer 2 IEEE 802.1x Validation 9-37
Configuring Web Authentication 9-38
Disabling IEEE 802.1x Authentication on the Port 9-40
Resetting the IEEE 802.1x Authentication Configuration to the Default Values 9-41

Displaying IEEE 802.1x Statistics and Status 9-41

CHAPTER

10 Configuring Interface Characteristics 10-1

Understanding Interface Types 10-1

Port-Based VLANs 10-2
Switch Ports 10-2

Access Ports 10-2

Trunk Ports 10-3
EtherChannel Port Groups 10-3
Dual-Purpose Uplink Ports 10-4
Connecting Interfaces 10-4

Using Interface Configuration Mode 10-4

Procedures for Configuring Interfaces 10-5
Configuring a Range of Interfaces 10-6
Configuring and Using Interface Range Macros 10-7

Configuring Ethernet Interfaces 10-9

Default Ethernet Interface Configuration 10-9
Setting the Type of a Dual-Purpose Uplink Port 10-10
Configuring Interface Speed and Duplex Mode 10-12

Speed and Duplex Configuration Guidelines 10-12

Setting the Interface Speed and Duplex Parameters 10-13
Configuring IEEE 802.3x Flow Control 10-14
Configuring Auto-MDIX on an Interface 10-15
Adding a Description for an Interface 10-16

Configuring the System MTU 10-16

Monitoring and Maintaining the Interfaces 10-18

Monitoring Interface Status 10-18
Clearing and Resetting Interfaces and Counters 10-19
Shutting Down and Restarting the Interface 10-19

CHAPTER

11 Configuring Smartports Macros 11-1

Understanding Smartports Macros 11-1

Contents

xi

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Configuring Smartports Macros 11-2

Default Smartports Macro Configuration 11-2
Smartports Macro Configuration Guidelines 11-2
Creating Smartports Macros 11-4
Applying Smartports Macros 11-5
Applying Cisco-Default Smartports Macros 11-6

Displaying Smartports Macros 11-8

CHAPTER

12 Configuring VLANs 12-1

Understanding VLANs 12-1

Supported VLANs 12-2
VLAN Port Membership Modes 12-3

Configuring Normal-Range VLANs 12-4

Token Ring VLANs 12-5
Normal-Range VLAN Configuration Guidelines 12-5
VLAN Configuration Mode Options 12-6

VLAN Configuration in config-vlan Mode 12-6

VLAN Configuration in VLAN Database Configuration Mode 12-6
Saving VLAN Configuration 12-6
Default Ethernet VLAN Configuration 12-7
Creating or Modifying an Ethernet VLAN 12-8
Deleting a VLAN 12-9
Assigning Static-Access Ports to a VLAN 12-10

Configuring Extended-Range VLANs 12-11

Default VLAN Configuration 12-11
Extended-Range VLAN Configuration Guidelines 12-12
Creating an Extended-Range VLAN 12-12

Displaying VLANs 12-13

Configuring VLAN Trunks 12-14

Trunking Overview 12-14

IEEE 802.1Q Configuration Considerations 12-15
Default Layer 2 Ethernet Interface VLAN Configuration 12-16
Configuring an Ethernet Interface as a Trunk Port 12-16

Interaction with Other Features 12-16

Configuring a Trunk Port 12-17

Defining the Allowed VLANs on a Trunk 12-18

Changing the Pruning-Eligible List 12-19

Configuring the Native VLAN for Untagged Traffic 12-19
Configuring Trunk Ports for Load Sharing 12-20

Contents

xii

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Load Sharing Using STP Port Priorities 12-20
Load Sharing Using STP Path Cost 12-22

Configuring VMPS 12-23

Understanding VMPS 12-24

Dynamic-Access Port VLAN Membership 12-24
Default VMPS Client Configuration 12-25
VMPS Configuration Guidelines 12-25
Configuring the VMPS Client 12-25

Entering the IP Address of the VMPS 12-26

Configuring Dynamic-Access Ports on VMPS Clients 12-26

Reconfirming VLAN Memberships 12-27

Changing the Reconfirmation Interval 12-27

Changing the Retry Count 12-28
Monitoring the VMPS 12-28
Troubleshooting Dynamic-Access Port VLAN Membership 12-29
VMPS Configuration Example 12-29

CHAPTER

13 Configuring VTP 13-1

Understanding VTP 13-1

The VTP Domain 13-2
VTP Modes 13-3
VTP Advertisements 13-3
VTP Version 2 13-4
VTP Pruning 13-4

Configuring VTP 13-6

Default VTP Configuration 13-6
VTP Configuration Options 13-7

VTP Configuration in Global Configuration Mode 13-7

VTP Configuration in VLAN Database Configuration Mode 13-7
VTP Configuration Guidelines 13-8

Domain Names 13-8

Passwords 13-8

VTP Version 13-8

Configuration Requirements 13-9
Configuring a VTP Server 13-9
Configuring a VTP Client 13-11
Disabling VTP (VTP Transparent Mode) 13-12
Enabling VTP Version 2 13-13
Enabling VTP Pruning 13-14

Contents

xiii

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Adding a VTP Client Switch to a VTP Domain 13-14

Monitoring VTP 13-16

CHAPTER

14 Configuring Voice VLAN 14-1

Understanding Voice VLAN 14-1

Cisco IP Phone Voice Traffic 14-2
Cisco IP Phone Data Traffic 14-2

Configuring Voice VLAN 14-3

Default Voice VLAN Configuration 14-3
Voice VLAN Configuration Guidelines 14-3
Configuring a Port Connected to a Cisco 7960 IP Phone 14-4

Configuring Cisco IP Phone Voice Traffic 14-4
Configuring the Priority of Incoming Data Frames 14-6

Displaying Voice VLAN 14-6

CHAPTER

15 Configuring STP 15-1

Understanding Spanning-Tree Features 15-1

STP Overview 15-2
Spanning-Tree Topology and BPDUs 15-3
Bridge ID, Switch Priority, and Extended System ID 15-4
Spanning-Tree Interface States 15-4

Blocking State 15-6
Listening State 15-6
Learning State 15-6
Forwarding State 15-6

Disabled State 15-7
How a Switch or Port Becomes the Root Switch or Root Port 15-7
Spanning Tree and Redundant Connectivity 15-8
Spanning-Tree Address Management 15-8
Accelerated Aging to Retain Connectivity 15-8
Spanning-Tree Modes and Protocols 15-9
Supported Spanning-Tree Instances 15-9
Spanning-Tree Interoperability and Backward Compatibility 15-10
STP and IEEE 802.1Q Trunks 15-10

Configuring Spanning-Tree Features 15-10

Default Spanning-Tree Configuration 15-11
Spanning-Tree Configuration Guidelines 15-12
Changing the Spanning-Tree Mode. 15-13
Disabling Spanning Tree 15-14

Contents

xiv

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Configuring the Root Switch 15-14
Configuring a Secondary Root Switch 15-16
Configuring Port Priority 15-16
Configuring Path Cost 15-18
Configuring the Switch Priority of a VLAN 15-19
Configuring Spanning-Tree Timers 15-20

Configuring the Hello Time 15-20
Configuring the Forwarding-Delay Time for a VLAN 15-21
Configuring the Maximum-Aging Time for a VLAN 15-21
Configuring the Transmit Hold-Count 15-22

Displaying the Spanning-Tree Status 15-22

CHAPTER

16 Configuring MSTP 16-1

Understanding MSTP 16-2

Multiple Spanning-Tree Regions 16-2
IST, CIST, and CST 16-3

Operations Within an MST Region 16-3
Operations Between MST Regions 16-4

IEEE 802.1s Terminology 16-5
Hop Count 16-5
Boundary Ports 16-6
IEEE 802.1s Implementation 16-6

Port Role Naming Change 16-7

Interoperation Between Legacy and Standard Switches 16-7

Detecting Unidirectional Link Failure 16-8
Interoperability with IEEE 802.1D STP 16-8

Understanding RSTP 16-8

Port Roles and the Active Topology 16-9
Rapid Convergence 16-10
Synchronization of Port Roles 16-11
Bridge Protocol Data Unit Format and Processing 16-12

Processing Superior BPDU Information 16-13

Processing Inferior BPDU Information 16-13
Topology Changes 16-13

Configuring MSTP Features 16-14

Default MSTP Configuration 16-14
MSTP Configuration Guidelines 16-15
Specifying the MST Region Configuration and Enabling MSTP 16-16
Configuring the Root Switch 16-17

Contents

xv

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Configuring a Secondary Root Switch 16-18
Configuring Port Priority 16-19
Configuring Path Cost 16-20
Configuring the Switch Priority 16-21
Configuring the Hello Time 16-22
Configuring the Forwarding-Delay Time 16-23
Configuring the Maximum-Aging Time 16-23
Configuring the Maximum-Hop Count 16-24
Specifying the Link Type to Ensure Rapid Transitions 16-24
Designating the Neighbor Type 16-25
Restarting the Protocol Migration Process 16-25

Displaying the MST Configuration and Status 16-26

CHAPTER

17 Configuring Optional Spanning-Tree Features 17-1

Understanding Optional Spanning-Tree Features 17-1

Understanding Port Fast 17-2
Understanding BPDU Guard 17-2
Understanding BPDU Filtering 17-3
Understanding UplinkFast 17-3
Understanding BackboneFast 17-5
Understanding EtherChannel Guard 17-7
Understanding Root Guard 17-8
Understanding Loop Guard 17-9

Configuring Optional Spanning-Tree Features 17-9

Default Optional Spanning-Tree Configuration 17-9
Optional Spanning-Tree Configuration Guidelines 17-10
Enabling Port Fast 17-10
Enabling BPDU Guard 17-11
Enabling BPDU Filtering 17-12
Enabling UplinkFast for Use with Redundant Links 17-13
Enabling BackboneFast 17-13
Enabling EtherChannel Guard 17-14
Enabling Root Guard 17-15
Enabling Loop Guard 17-15

Displaying the Spanning-Tree Status 17-16

CHAPTER

18 Configuring IGMP Snooping and MVR 18-1

Understanding IGMP Snooping 18-1

IGMP Versions 18-2

Contents

xvi

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Joining a Multicast Group 18-3
Leaving a Multicast Group 18-5
Immediate Leave 18-5
IGMP Configurable-Leave Timer 18-5
IGMP Report Suppression 18-6

Configuring IGMP Snooping 18-6

Default IGMP Snooping Configuration 18-6
Enabling or Disabling IGMP Snooping 18-7
Setting the Snooping Method 18-8
Configuring a Multicast Router Port 18-9
Configuring a Host Statically to Join a Group 18-10
Enabling IGMP Immediate Leave 18-10
Configuring the IGMP Leave Timer 18-11
Configuring TCN-Related Commands 18-12

Controlling the Multicast Flooding Time After a TCN Event 18-12

Recovering from Flood Mode 18-12

Disabling Multicast Flooding During a TCN Event 18-13
Configuring the IGMP Snooping Querier 18-14
Disabling IGMP Report Suppression 18-15

Displaying IGMP Snooping Information 18-15

Understanding Multicast VLAN Registration 18-17

Using MVR in a Multicast Television Application 18-18

Configuring MVR 18-19

Default MVR Configuration 18-19
MVR Configuration Guidelines and Limitations 18-20
Configuring MVR Global Parameters 18-20
Configuring MVR Interfaces 18-21

Displaying MVR Information 18-23

Configuring IGMP Filtering and Throttling 18-23

Default IGMP Filtering and Throttling Configuration 18-24
Configuring IGMP Profiles 18-24
Applying IGMP Profiles 18-25
Setting the Maximum Number of IGMP Groups 18-26
Configuring the IGMP Throttling Action 18-27

Displaying IGMP Filtering and Throttling Configuration 18-28

CHAPTER

19 Configuring Port-Based Traffic Control 19-1

Configuring Storm Control 19-1

Understanding Storm Control 19-1

Contents

xvii

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Default Storm Control Configuration 19-3
Configuring Storm Control and Threshold Levels 19-3

Configuring Protected Ports 19-5

Default Protected Port Configuration 19-6
Protected Port Configuration Guidelines 19-6
Configuring a Protected Port 19-6

Configuring Port Blocking 19-7

Default Port Blocking Configuration 19-7
Blocking Flooded Traffic on an Interface 19-7

Configuring Port Security 19-8

Understanding Port Security 19-8

Secure MAC Addresses 19-8

Security Violations 19-9
Default Port Security Configuration 19-10
Port Security Configuration Guidelines 19-10
Enabling and Configuring Port Security 19-11
Enabling and Configuring Port Security Aging 19-16

Displaying Port-Based Traffic Control Settings 19-17

CHAPTER

20 Configuring CDP 20-1

Understanding CDP 20-1

Configuring CDP 20-2

Default CDP Configuration 20-2
Configuring the CDP Characteristics 20-2
Disabling and Enabling CDP 20-3
Disabling and Enabling CDP on an Interface 20-4

Monitoring and Maintaining CDP 20-4

CHAPTER

21 Configuring LLDP and LLDP-MED 21-1

Understanding LLDP and LLDP-MED 21-1

Understanding LLDP 21-1
Understanding LLDP-MED 21-2

Configuring LLDP and LLDP-MED 21-3

Default LLDP Configuration 21-3
Configuring LLDP Characteristics 21-4
Disabling and Enabling LLDP Globally 21-5
Disabling and Enabling LLDP on an Interface 21-5
Configuring LLDP-MED TLVs 21-6

Contents

xviii

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Monitoring and Maintaining LLDP and LLDP-MED 21-7

CHAPTER

22 Configuring UDLD 22-1

Understanding UDLD 22-1

Modes of Operation 22-1
Methods to Detect Unidirectional Links 22-2

Configuring UDLD 22-4

Default UDLD Configuration 22-4
Configuration Guidelines 22-4
Enabling UDLD Globally 22-5
Enabling UDLD on an Interface 22-5
Resetting an Interface Disabled by UDLD 22-6

Displaying UDLD Status 22-6

CHAPTER

23 Configuring SPAN and RSPAN 23-1

Understanding SPAN and RSPAN 23-1

Local SPAN 23-2
Remote SPAN 23-2
SPAN and RSPAN Concepts and Terminology 23-3

SPAN Sessions 23-3
Monitored Traffic 23-4
Source Ports 23-5
Source VLANs 23-6
VLAN Filtering 23-6
Destination Port 23-6
RSPAN VLAN 23-7

SPAN and RSPAN Interaction with Other Features 23-8

Configuring SPAN and RSPAN 23-9

Default SPAN and RSPAN Configuration 23-9
Configuring Local SPAN 23-9

SPAN Configuration Guidelines 23-10
Creating a Local SPAN Session 23-10
Creating a Local SPAN Session and Configuring Incoming Traffic 23-13
Specifying VLANs to Filter 23-14

Configuring RSPAN 23-15

RSPAN Configuration Guidelines 23-16
Configuring a VLAN as an RSPAN VLAN 23-16
Creating an RSPAN Source Session 23-17
Creating an RSPAN Destination Session 23-19

Contents

xix

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Creating an RSPAN Destination Session and Configuring Incoming Traffic 23-20

Specifying VLANs to Filter 23-21

Displaying SPAN and RSPAN Status 23-22

CHAPTER

24 Configuring RMON 24-1

Understanding RMON 24-1

Configuring RMON 24-2

Default RMON Configuration 24-3
Configuring RMON Alarms and Events 24-3
Collecting Group History Statistics on an Interface 24-5
Collecting Group Ethernet Statistics on an Interface 24-5

Displaying RMON Status 24-6

CHAPTER

25 Configuring System Message Logging 25-1

Understanding System Message Logging 25-1

Configuring System Message Logging 25-2

System Log Message Format 25-2
Default System Message Logging Configuration 25-3
Disabling Message Logging 25-4
Setting the Message Display Destination Device 25-5
Synchronizing Log Messages 25-6
Enabling and Disabling Time Stamps on Log Messages 25-7
Enabling and Disabling Sequence Numbers in Log Messages 25-8
Defining the Message Severity Level 25-8
Limiting Syslog Messages Sent to the History Table and to SNMP 25-10
Enabling the Configuration-Change Logger 25-10
Configuring UNIX Syslog Servers 25-12

Logging Messages to a UNIX Syslog Daemon 25-12

Configuring the UNIX System Logging Facility 25-12

Displaying the Logging Configuration 25-13

CHAPTER

26 Configuring SNMP 26-1

Understanding SNMP 26-1

SNMP Versions 26-2
SNMP Manager Functions 26-3
SNMP Agent Functions 26-4
SNMP Community Strings 26-4
Using SNMP to Access MIB Variables 26-4

Contents

xx

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

SNMP Notifications 26-5
SNMP ifIndex MIB Object Values 26-6

Configuring SNMP 26-6

Default SNMP Configuration 26-7
SNMP Configuration Guidelines 26-7
Disabling the SNMP Agent 26-8
Configuring Community Strings 26-8
Configuring SNMP Groups and Users 26-10
Configuring SNMP Notifications 26-12
Setting the Agent Contact and Location Information 26-15
Limiting TFTP Servers Used Through SNMP 26-16
SNMP Examples 26-17

Displaying SNMP Status 26-18

CHAPTER

27 Configuring Cisco IOS IP SLAs Operations 27-1

Understanding Cisco IOS IP SLAs 27-1

Using Cisco IOS IP SLAs to Measure Network Performance 27-2
IP SLAs Responder and IP SLAs Control Protocol 27-3
Response Time Computation for IP SLAs 27-4

Configuring IP SLAs Operations 27-5

Default Configuration 27-5
Configuration Guidelines 27-5
Configuring the IP SLAs Responder 27-6

Monitoring IP SLAs Operations 27-7

CHAPTER

28 Configuring QoS 28-1

Understanding QoS 28-1

Basic QoS Model 28-3
Classification 28-5

Classification Based on QoS ACLs 28-7
Classification Based on Class Maps and Policy Maps 28-7

Policing and Marking 28-8

Policing on Physical Ports 28-9
Mapping Tables 28-11
Queueing and Scheduling Overview 28-12

Weighted Tail Drop 28-12

SRR Shaping and Sharing 28-13

Queueing and Scheduling on Ingress Queues 28-14

Queueing and Scheduling on Egress Queues 28-16

Contents

xxi

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Packet Modification 28-18

Configuring Auto-QoS 28-19

Generated Auto-QoS Configuration 28-20
Effects of Auto-QoS on the Configuration 28-24
Auto-QoS Configuration Guidelines 28-25
Enabling Auto-QoS for VoIP 28-25
Auto-QoS Configuration Example 28-27

Displaying Auto-QoS Information 28-29

Configuring Standard QoS 28-29

Default Standard QoS Configuration 28-30

Default Ingress Queue Configuration 28-30
Default Egress Queue Configuration 28-31
Default Mapping Table Configuration 28-32

Standard QoS Configuration Guidelines 28-32

QoS ACL Guidelines 28-32
Policing Guidelines 28-32

General QoS Guidelines 28-33
Enabling QoS Globally 28-33
Configuring Classification Using Port Trust States 28-34

Configuring the Trust State on Ports within the QoS Domain 28-34

Configuring the CoS Value for an Interface 28-36

Configuring a Trusted Boundary to Ensure Port Security 28-36

Enabling DSCP Transparency Mode 28-38

Configuring the DSCP Trust State on a Port Bordering Another QoS Domain 28-38
Configuring a QoS Policy 28-40

Classifying Traffic by Using ACLs 28-41

Classifying Traffic by Using Class Maps 28-44

Classifying, Policing, and Marking Traffic on Physical Ports by Using Policy Maps 28-46

Classifying, Policing, and Marking Traffic by Using Aggregate Policers 28-49
Configuring DSCP Maps 28-51

Configuring the CoS-to-DSCP Map 28-52

Configuring the IP-Precedence-to-DSCP Map 28-53

Configuring the Policed-DSCP Map 28-54

Configuring the DSCP-to-CoS Map 28-55

Configuring the DSCP-to-DSCP-Mutation Map 28-56
Configuring Ingress Queue Characteristics 28-57

Mapping DSCP or CoS Values to an Ingress Queue and Setting WTD Thresholds 28-58

Allocating Buffer Space Between the Ingress Queues 28-59

Allocating Bandwidth Between the Ingress Queues 28-60

Contents

xxii

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Configuring the Ingress Priority Queue 28-61

Configuring Egress Queue Characteristics 28-62

Configuration Guidelines 28-62
Allocating Buffer Space to and Setting WTD Thresholds for an Egress Queue-Set 28-62
Mapping DSCP or CoS Values to an Egress Queue and to a Threshold ID 28-65
Configuring SRR Shaped Weights on Egress Queues 28-66
Configuring SRR Shared Weights on Egress Queues 28-67
Configuring the Egress Expedite Queue 28-68
Limiting the Bandwidth on an Egress Interface 28-68

Displaying Standard QoS Information 28-69

CHAPTER

29 Configuring IPv6 Host Functions 29-1

Understanding IPv6 29-1

IPv6 Addresses 29-2
Supported IPv6 Unicast Routing Features 29-3

128-Bit Wide Unicast Addresses 29-3
DNS for IPv6 29-4
ICMPv6 29-4
Neighbor Discovery 29-4
IPv6 Stateless Autoconfiguration and Duplicate Address Detection 29-4
IPv6 Applications 29-5
Dual IPv4 and IPv6 Protocol Stacks 29-5

SDM Templates 29-6

Dual IPv4-and-IPv6 SDM Templates 29-7

Configuring IPv6 29-7

Default IPv6 Configuration 29-8
Configuring IPv6 ICMP Rate Limiting 29-8
Configuring Static Routes for IPv6 29-9

Displaying IPv6 29-11

CHAPTER

30 Configuring IPv6 MLD Snooping 30-1

Understanding MLD Snooping 30-1

MLD Messages 30-2
MLD Queries 30-3
Multicast Client Aging Robustness 30-3
Multicast Router Discovery 30-3
MLD Reports 30-4
MLD Done Messages and Immediate-Leave 30-4
Topology Change Notification Processing 30-5

Contents

xxiii

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Configuring IPv6 MLD Snooping 30-5

Default MLD Snooping Configuration 30-5
MLD Snooping Configuration Guidelines 30-6
Enabling or Disabling MLD Snooping 30-6
Configuring a Static Multicast Group 30-8
Configuring a Multicast Router Port 30-8
Enabling MLD Immediate Leave 30-9
Configuring MLD Snooping Queries 30-10
Disabling MLD Listener Message Suppression 30-11

Displaying MLD Snooping Information 30-11

CHAPTER

31 Configuring EtherChannels and Link-State Tracking 31-1

Understanding EtherChannels 31-1

EtherChannel Overview 31-2
Port-Channel Interfaces 31-3
Port Aggregation Protocol 31-4

PAgP Modes 31-4

PAgP Interaction with Other Features 31-5
Link Aggregation Control Protocol 31-5

LACP Modes 31-5

LACP Interaction with Other Features 31-6
EtherChannel On Mode 31-6
Load Balancing and Forwarding Methods 31-6

Configuring EtherChannels 31-8

Default EtherChannel Configuration 31-9
EtherChannel Configuration Guidelines 31-9
Configuring Layer 2 EtherChannels 31-10
Configuring EtherChannel Load Balancing 31-12
Configuring the PAgP Learn Method and Priority 31-13
Configuring LACP Hot-Standby Ports 31-14

Configuring the LACP System Priority 31-15

Configuring the LACP Port Priority 31-15

Displaying EtherChannel, PAgP, and LACP Status 31-16

Understanding Link-State Tracking 31-17

Configuring Link-State Tracking 31-19

Default Link-State Tracking Configuration 31-20
Link-State Tracking Configuration Guidelines 31-20
Configuring Link-State Tracking 31-20
Displaying Link-State Tracking Status 31-21

Contents

xxiv

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

CHAPTER

32 Troubleshooting 32-1

Recovering from a Software Failure 32-2

Recovering from a Lost or Forgotten Password 32-3

Procedure with Password Recovery Enabled 32-4
Procedure with Password Recovery Disabled 32-6

Recovering from a Command Switch Failure 32-7

Replacing a Failed Command Switch with a Cluster Member 32-8
Replacing a Failed Command Switch with Another Switch 32-10

Recovering from Lost Cluster Member Connectivity 32-11

Preventing Autonegotiation Mismatches 32-11

SFP Module Security and Identification 32-12

Monitoring SFP Module Status 32-12

Using Ping 32-12

Understanding Ping 32-13
Executing Ping 32-13

Using Layer 2 Traceroute 32-14

Understanding Layer 2 Traceroute 32-14
Usage Guidelines 32-14
Displaying the Physical Path 32-15

Using IP Traceroute 32-15

Understanding IP Traceroute 32-15
Executing IP Traceroute 32-16

Using TDR 32-17

Understanding TDR 32-17
Running TDR and Displaying the Results 32-18

Using Debug Commands 32-18

Enabling Debugging on a Specific Feature 32-18
Enabling All-System Diagnostics 32-19
Redirecting Debug and Error Message Output 32-19

Using the show platform forward Command 32-20

Using the crashinfo Files 32-21

Basic crashinfo Files 32-21
Extended crashinfo Files 32-22

APPENDIX

A Supported MIBs A-1

MIB List A-1

Using FTP to Access the MIB Files A-3

Contents

xxv

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

APPENDIX

B Working with the Cisco IOS File System, Configuration Files, and Software Images B-1

Working with the Flash File System B-1

Displaying Available File Systems B-2
Setting the Default File System B-3
Displaying Information about Files on a File System B-3
Changing Directories and Displaying the Working Directory B-4
Creating and Removing Directories B-4
Copying Files B-5
Deleting Files B-5
Creating, Displaying, and Extracting tar Files B-6

Creating a tar File B-6

Displaying the Contents of a tar File B-7

Extracting a tar File B-7
Displaying the Contents of a File B-8

Working with Configuration Files B-8

Guidelines for Creating and Using Configuration Files B-9
Configuration File Types and Location B-10
Creating a Configuration File By Using a Text Editor B-10
Copying Configuration Files By Using TFTP B-10

Preparing to Download or Upload a Configuration File B y Using TFTP B-10

Downloading the Configuration File By Using TFTP B-11

Uploading the Configuration File By Using TFTP B-12
Copying Configuration Files By Using FTP B-12

Preparing to Download or Upload a Configuration File By Using FTP B-13

Downloading a Configuration File By Using FTP B-13

Uploading a Configuration File By Using FTP B-14
Copying Configuration Files By Using RCP B-15

Preparing to Download or Upload a Configuration File By Using RCP B-16

Downloading a Configuration File By Using RCP B-17

Uploading a Configuration File By Using RCP B-18
Clearing Configuration Information B-19

Clearing the Startup Configuration File B-19

Deleting a Stored Configuration File B-19
Replacing and Rolling Back Configurations B-19

Understanding Configuration Replacement and Rollback B-19

Configuration Guidelines B-21

Configuring the Configuration Archive B-21

Performing a Configuration Replacement or Rollback Operation B-22

Contents

xxvi

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Working with Software Images B-23

Image Location on the Switch B-24
tar File Format of Images on a Server or Cisco.com B-24
Copying Image Files By Using TFTP B-25

Preparing to Download or Upload an Image File By Using TFTP B-26
Downloading an Image File By Using TFTP B-27
Uploading an Image File By Using TFTP B-28

Copying Image Files By Using FTP B-29

Preparing to Download or Upload an Image File By Using FTP B-29
Downloading an Image File By Using FTP B-30
Uploading an Image File By Using FTP B-32

Copying Image Files By Using RCP B-33

Preparing to Download or Upload an Image File By Using RCP B-33
Downloading an Image File By Using RCP B-35
Uploading an Image File By Using RCP B-37

B-38

APPENDIX

C Recommendations for Upgrading a Catalyst 2950 Switch to a Catalyst 2960 Switch C-1

Configuration Compatibility Issues C-1

Feature Behavior Incompatibilities C-5

APPENDIX

D Unsupported Commands in Cisco IOS Release 12.2(40)SE D-1

Access Control Lists D-1

Unsupported Privileged EXEC Commands D-1
Unsupported Global Configuration Commands D-1
Unsupported Route-Map Configuration Commands D-1

Boot Loader Commands D-2

Unsupported User EXEC Commands D-2
Unsupported Global Configuration Commands D-2

Embedded Event Manager D-2

Unsupported Privileged EXEC Commands D-2
Unsupported Global Configuration Commands D-2
Unsupported Commands in Applet Configuration Mode D-2

Debug Commands D-2

Unsupported Privileged EXEC Commands D-2

|IGMP Snooping Commands D-3

Unsupported Global Configuration Commands D-3

Contents

xxvii

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Interface Commands D-3

Unsupported Privileged EXEC Commands D-3
Unsupported Global Configuration Commands D-3
Unsupported Interface Configuration Commands D-3

MAC Address Commands D-3

Unsupported Privileged EXEC Commands D-3
Unsupported Global Configuration Commands D-4

Miscellaneous D-4

Unsupported Privileged EXEC Commands D-4
Unsupported Global Configuration Commands D-4

Network Address Translation (NAT) Commands D-4

Unsupported Privileged EXEC Commands D-4

QoS D-5

Unsupported Global Configuration Command D-5
Unsupported Interface Configuration Commands D-5
Unsupported Policy-Map Configuration Command D-5

RADIUS D-5

Unsupported Global Configuration Commands D-5

SNMP D-5

Unsupported Global Configuration Commands D-5

Spanning Tree D-6

Unsupported Global Configuration Command D-6
Unsupported Interface Configuration Command D-6

VLAN D-6

Unsupported Global Configuration Command D-6
Unsupported vlan-config Command D-6
Unsupported User EXEC Commands D-6

VTP D-6

Unsupported Privileged EXEC Commands D-6

I

NDEX

Contents

xxviii

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

xxix

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Preface

Audience

This guide is for the networking professional managing the Catalyst 2960 switch, hereafter referred to
as the switch module. Before using this guide, you should have experience working with the Cisco IOS
software and be familiar with the concepts and terminology of Ethernet and local area networking.

Purpose

This guide provides the information that you need to configure Cisco IOS software features on your
switch. The Catalyst 2960 software provides enterprise-class intelligent services such as access control
lists (ACLs) and quality of service (QoS) features.

This guide provides procedures for using the commands that have been created or changed for use with
the Catalyst 2960 switch. It does not provide detailed information about these commands. For detailed
information about these commands, see the Catalyst 2960 Switch Command Reference for this release.
For information about the standard Cisco IOS Release 12.2 commands, see the Cisco IOS documentation
set available from the Cisco.com home page at Documentation > Cisco IOS Software.

This guide does not provide detailed information on the graphical user interfaces (GUIs) for the
embedded device manager or for Cisco Network Assistant (hereafter referred to as Network Assistant)
that you can use to manage the switch. However, the concepts in this guide are applicable to the GUI
user. For information about the device manager, see the switch online help. For information about
Network Assistant, see Getting Started with Cisco Network Assistant, available on Cisco.com.

This guide does not describe system messages you might encounter or how to install your switch. For
more information, see the Catalyst 2960 Switch System Message Guide for this release and the Catalyst
2960 Switch Hardware Installation Guide.

For documentation updates, see the release notes for this release.

xxx

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Preface

Conventions

Conventions

This publication uses these conventions to convey instructions and information:

Command descriptions use these conventions:

• Commands and keywords are in boldface text.

• Arguments for which you supply values are in italic.

• Square brackets ([ ]) mean optional elements.

• Braces ({ }) group required choices, and vertical bars ( | ) separate the alternative elements.

• Braces and vertical bars within square brackets ([{ | }]) mean a required choice within an optional

element.

Interactive examples use these conventions:

• Terminal sessions and system displays are in screen font.

• Information you enter is in boldface screen font.

• Nonprinting characters, such as passwords or tabs, are in angle brackets (< >).

Notes, cautions, and timesavers use these conventions and symbols:

Note Means reader take note. Notes contain helpful suggestions or references to materials not contained in

this manual.

Caution Means reader be careful. In this situation, you might do something that could result in equipment

damage or loss of data.

Related Publications

These documents provide complete information about the switch and are available from this Cisco.com
site:

http://www.cisco.com/en/US/products/ps6406/tsd_products_support_series_home.html

Note Before installing, configuring, or upgrading the switch, see these documents:

• For initial configuration information, see the “Using Express Setup” section in the getting started

guide or the “Configuring the Switch with the CLI-Based Setup Program” appendix in the hardware
installation guide.

• For device manager requirements, see the “System Requirements” section in the release notes (not

orderable but available on Cisco.com).

• For Network Assistant requirements, see the Getting Started with Cisco Network Assistant (not

orderable but available on Cisco.com).

xxxi

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Preface

Related Publications

• For cluster requirements, see the Release Notes for Cisco Network Assistant (not orderable but

available on Cisco.com).

• For upgrading information, see the “Downloading Software” section in the release notes.

You can order printed copies of documents with a DOC-xxxxxx= number from the Cisco.com sites and
from the telephone numbers listed in the URL referenced in the “Obtaining Documentation, Obtaining

Support, and Security Guidelines” section on page xxxii.

• Release Notes for the Catalyst 3750, 3560, 2970, and 2960 Switches (not orderable but available on

Cisco.com)

• Catalyst 3750, 3560, 3550, 2970, and 2960 Switch System Message Guide (not orderable but

available on Cisco.com)

• Catalyst 2960 Switch Software Configuration Guide (not orderable but available on Cisco.com)

• Catalyst 2960 Switch Command Reference (not orderable but available on Cisco.com)

• Device manager online help (available on the switch)

• Catalyst 2960 Switch Hardware Installation Guide (not orderable but available on Cisco.com)

• Catalyst 2960 Switch Getting Started Guide (order number DOC-7816879=)

• Regulatory Compliance and Safety Information for the Catalyst 2960 Switch (order number

DOC-7816880=)

• Getting Started with Cisco Network Assistant (not orderable but available on Cisco.com)

• Release Notes for Cisco Network Assistant (not orderable but available on Cisco.com)

• Cisco Small Form-Factor Pluggable Modules Installation Notes (order number DOC-7815160=)

• Cisco RPS 300 Redundant Power System Hardware Installation Guide (order number

DOC-7810372=)

• Cisco RPS 675 Redundant Power System Hardware Installation Guide (order number

DOC-7815201=)

• Cisco Redundant Power System 2300 Hardware Installation Guide (order number DOC-7817647=)

• For more information about the Network Admission Control (NAC) features, see the Network

Admission Control Software Configuration Guide (not orderable but available on Cisco.com)

• These compatibility matrix documents are available from this Cisco.com site:

http://www.cisco.com/en/US/products/hw/modules/ps5455/products_device_support_tables_list.html

–

Cisco Gigabit Ethernet Transceiver Modules Compatibility Matrix (not orderable but available
on Cisco.com)

–

Cisco 100-Megabit Ethernet SFP Modules Compatibility Matrix (not orderable but available on
Cisco.com)

–

Cisco Small Form-Factor Pluggable Modules Compatibility Matrix (not orderable but available
on Cisco.com)

–

Compatibility Matrix for 1000BASE-T Small Form-Factor Pluggable Modules (not orderable
but available on Cisco.com)

xxxii

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Preface

Obtaining Documentation, Obtaining Support, and Security Guidelines

Obtaining Documentation, Obtaining Support, and Security
Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback,
security guidelines, and also recommended aliases and general Cisco documents, see the monthly
What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical
documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

CHA PTER

1-1

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

1

Overview

This chapter provides these topics about the Catalyst 2960 switch software:

• Features, page 1-1

• Default Settings After Initial Switch Configuration, page 1-10

• Network Configuration Examples, page 1-12

• Where to Go Next, page 1-18

In this document, IP refers to IP Version 4 (IPv4).

Features

Some features described in this chapter are available only on the cryptographic (supports encryption)
version of the software. You must obtain authorization to use this feature and to download the
cryptographic version of the software from Cisco.com. For more information, see the release notes for
this release.

The switch has these features:

• Ease-of-Deployment and Ease-of-Use Features, page 1-1

• Performance Features, page 1-2

• Management Options, page 1-3

• Manageability Features, page 1-4 (includes a feature requiring the cryptographic version of the

software)

• Availability and Redundancy Features, page 1-6

• VLAN Features, page 1-7

• Security Features, page 1-7 (includes a feature requiring the cryptographic version of the software)

• QoS and CoS Features, page 1-9

• Monitoring Features, page 1-10

Ease-of-Deployment and Ease-of-Use Features

The switch ships with these features to make the deployment and the use easier:

1-2

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 1 Overview

Features

• Express Setup for quickly configuring a switch for the first time with basic IP information, contact

information, switch and Telnet passwords, and Simple Network Management Protocol (SNMP)
information through a browser-based program. For more information about Express Setup, see the
getting started guide.

• User-defined and Cisco-default Smartports macros for creating custom switch configurations for

simplified deployment across the network.

• An embedded device manager GUI for configuring and monitoring a single switch through a web

browser. For information about launching the device manager, see the getting started guide. For more
information about the device manager, see the switch online help.

• Cisco Network Assistant (hereafter referred to as Network Assistant) for

–

Managing communities, which are device groups like clusters, except that they can contain
routers and access points and can be made more secure.

–

Simplifying and minimizing switch and switch cluster management from anywhere in your
intranet.

–

Accomplishing multiple configuration tasks from a single graphical interface without needing
to remember command-line interface (CLI) commands to accomplish specific tasks.

–

Interactive guide mode that guides you in configuring complex features such as VLANs, ACLs,
and quality of service (QoS).

–

Configuration wizards that prompt you to provide only the minimum required information to
configure complex features such as QoS priorities for traffic, priority levels for data
applications, and security.

–

Downloading an image to a switch.

–

Applying actions to multiple ports and multiple switches at the same time, such as VLAN and
QoS settings, inventory and statistic reports, link- and switch-level monitoring and
troubleshooting, and multiple switch software upgrades.

–

Viewing a topology of interconnected devices to identify existing switch clusters and eligible
switches that can join a cluster and to identify link information between switches.

–

Monitoring real-time status of a switch or multiple switches from the LEDs on the front-panel
images. The system, redundant power system (RPS), and port LED colors on the images are
similar to those used on the physical LEDs.

• Switch clustering technology for

–

Unified configuration, monitoring, authentication, and software upgrade of multiple,
cluster-capable switches, regardless of their geographic proximity and interconnection media,
including Ethernet, Fast Ethernet, Fast EtherChannel, small form-factor pluggable (SFP)
modules, Gigabit Ethernet, and Gigabit EtherChannel connections. For a list of cluster-capable
switches, see the release notes.

–

Automatic discovery of candidate switches and creation of clusters of up to 16 switches that can
be managed through a single IP address.

–

Extended discovery of cluster candidates that are not directly connected to the command switch.

Performance Features

The switch ships with these performance features:

• Autosensing of port speed and autonegotiation of duplex mode on all switch ports for optimizing

bandwidth

1-3

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 1 Overview

Features

• Automatic-medium-dependent interface crossover (auto-MDIX) capability on 10/100 and

10/100/1000 Mb/s interfaces and on 10/100/1000 BASE-TX SFP module interfaces that enables the
interface to automatically detect the required cable connection type (straight-through or crossover)
and to configure the connection appropriately

• Support for up to 9000 bytes for frames that are bridged in hardware, and up to 2000 bytes for frames

that are bridged by software

• IEEE 802.3x flow control on all ports (the switch does not send pause frames)

• EtherChannel for enhanced fault tolerance and for providing up to 8 Gb/s (Gigabit EtherChannel)

or 800 Mb/s (Fast EtherChannel) full-duplex bandwidth among switches, routers, and servers

• Port Aggregation Protocol (PAgP) and Link Aggregation Control Protocol (LACP) for automatic

creation of EtherChannel links

• Forwarding of Layer 2 packets at Gigabit line rate

• Per-port storm control for preventing broadcast, multicast, and unicast storms

• Port blocking on forwarding unknown Layer 2 unknown unicast, multicast, and bridged broadcast

traffic

• Internet Group Management Protocol (IGMP) snooping for IGMP Versions 1, 2, and 3 for

efficiently forwarding multimedia and multicast traffic

• IGMP report suppression for sending only one IGMP report per multicast router query to the

multicast devices (supported only for IGMPv1 or IGMPv2 queries)

• IGMP snooping querier support to configure switch to generate periodic IGMP general query

messages

• IPv6 host support for basic IPv6 management

• Multicast Listener Discovery (MLD) snooping to enable efficient distribution of IP version 6 (IPv6)

multicast data to clients and routers in a switched network

• Multicast VLAN registration (MVR) to continuously send multicast streams in a multicast VLAN

while isolating the streams from subscriber VLANs for bandwidth and security reasons

• IGMP filtering for controlling the set of multicast groups to which hosts on a switch port can belong

• IGMP throttling for configuring the action when the maximum number of entries is in the IGMP

forwarding table

• IGMP leave timer for configuring the leave latency for the network

• Switch Database Management (SDM) templates for allocating system resources to maximize

support for user-selected features

• Cisco IOS IP Service Level Agreements (SLAs), a part of Cisco IOS software that uses active traffic

monitoring for measuring network performance Support for Cisco IOS IP Service Level Agreements
(SLAs) responder that allows the system to anticipate and respond to Cisco IOS IP SLAs request
packets for monitoring network performance. See the release notes for responder configuration.

Management Options

These are the options for configuring and managing the switch:

• An embedded device manager—The device manager is a GUI that is integrated in the software

image. You use it to configure and to monitor a single switch. For information about launching the
device manager, see the getting started guide. For more information about the device manager, see the
switch online help.

1-4

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 1 Overview

Features

• Network Assistant—Network Assistant is a network management application that can be

downloaded from Cisco.com. You use it to manage a single switch, a cluster of switches, or a
community of devices. For more information about Network Assistant, see Getting Started with
Cisco Network Assistant, available on Cisco.com.

• CLI—The Cisco IOS software supports desktop- and multilayer-switching features. You can access

the CLI either by connecting your management station directly to the switch console port or by using
Telnet from a remote management station. For more information about the CLI, see Chapter 2,

“Using the Command-Line Interface.”

• SNMP—SNMP management applications such as CiscoWorks2000 LAN Management Suite (LMS)

and HP OpenView. You can manage from an SNMP-compatible management station that is running
platforms such as HP OpenView or SunNet Manager. The switch supports a comprehensive set of
MIB extensions and four remote monitoring (RMON) groups. For more information about using
SNMP, see Chapter 26, “Configuring SNMP.”

• CNS—Cisco Networking Services is network management software that acts as a configuration

service for automating the deployment and management of network devices and services. You can
automate initial configurations and configuration updates by generating switch-specific
configuration changes, sending them to the switch, executing the configuration change, and logging
the results.

For more information about CNS, see Chapter 4, “Configuring Cisco IOS CNS Agents.”

Manageability Features

These are the manageability features:

• CNS embedded agents for automating switch management, configuration storage, and delivery

• DHCP for automating configuration of switch information (such as IP address, default gateway,

hostname, and Domain Name System [DNS] and TFTP server names)

• DHCP relay for forwarding User Datagram Protocol (UDP) broadcasts, including IP address

requests, from DHCP clients

• DHCP server for automatic assignment of IP addresses and other DHCP options to IP hosts

• Directed unicast requests to a DNS server for identifying a switch through its IP address and its

corresponding hostname and to a TFTP server for administering software upgrades from a TFTP
server

• Address Resolution Protocol (ARP) for identifying a switch through its IP address and its

corresponding MAC address

• Unicast MAC address filtering to drop packets with specific source or destination MAC addresses

• Cisco Discovery Protocol (CDP) Versions 1 and 2 for network topology discovery and mapping

between the switch and other Cisco devices on the network

• Link Layer Discovery Protocol (LLDP) and LLDP Media Endpoint Discovery (LLDP-MED) for

interoperability with third-party IP phones

• LLDP media extensions (LLDP-MED) location TLV that provides location information from the

switch to the endpoint device

• Network Time Protocol (NTP) for providing a consistent time stamp to all switches from an external

source

• Cisco IOS File System (IFS) for providing a single interface to all file systems that the switch uses

1-5

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 1 Overview

Features

• Support for Enhanced Interior Gateway Routing Protocol (EIGRP) IPv6 to utilize IPv6 transport,

communicate with IPv6 peers, and advertise IPv6 routes

• Support for these IP services, making them VRF aware so that they can operate on multiple routing

instances: HSRP, GLBP, uRPF, ARP, SNMP, IP SLA, TFTP, FTP, syslog, traceroute, and ping

• Configuration logging to log and to view changes to the switch configuration

• Unique device identifier to provide product identification information through a show inventory

user EXEC command display

• In-band management access through the device manager over a Netscape Navigator or Microsoft

Internet Explorer browser session

• In-band management access for up to 16 simultaneous Telnet connections for multiple CLI-based

sessions over the network

• In-band management access for up to five simultaneous, encrypted Secure Shell (SSH) connections

for multiple CLI-based sessions over the network (requires the cryptographic version of the
software)

• In-band management access through SNMP Versions 1, 2c, and 3 get and set requests

• Out-of-band management access through the switch console port to a directly attached terminal or

to a remote terminal through a serial connection or a modem

• Secure Copy Protocol (SCP) feature to provide a secure and authenticated method for copying

switch configuration or switch image files (requires the cryptographic version of the software)

• Configuration replacement and rollback to replace the running configuration on a switch with any

saved Cisco IOS configuration file

1-6

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 1 Overview

Features

Availability and Redundancy Features

These are the availability and redundancy features:

• Enhanced object tracking, which separates the tracking mechanism from HSRP and creates a

separate, standalone tracking process that can be used by processes other than HSRP

• UniDirectional Link Detection (UDLD) and aggressive UDLD for detecting and disabling

unidirectional links on fiber-optic interfaces caused by incorrect fiber-optic wiring or port faults

• IEEE 802.1D Spanning Tree Protocol (STP) for redundant backbone connections and loop-free

networks. STP has these features:

–

Up to 128 spanning-tree instances supported

–

Per-VLAN spanning-tree plus (PVST+) for load balancing across VLANs

–

Rapid PVST+ for load balancing across VLANs and providing rapid convergence of
spanning-tree instances

–

UplinkFast and BackboneFast for fast convergence after a spanning-tree topology change and
for achieving load balancing between redundant uplinks, including Gigabit uplinks

• IEEE 802.1s Multiple Spanning Tree Protocol (MSTP) for grouping VLANs into a spanning-tree

instance and for providing multiple forwarding paths for data traffic and load balancing and rapid
per-VLAN Spanning-Tree plus (rapid-PVST+) based on the IEEE 802.1w Rapid Spanning Tree
Protocol (RSTP) for rapid convergence of the spanning tree by immediately changing root and
designated ports to the forwarding state

• Optional spanning-tree features available in PVST+, rapid-PVST+, and MSTP mode:

–

Port Fast for eliminating the forwarding delay by enabling a port to immediately change from
the blocking state to the forwarding state

–

BPDU guard for shutting down Port Fast-enabled ports that receive bridge protocol data units
(BPDUs)

–

BPDU filtering for preventing a Port Fast-enabled port from sending or receiving BPDUs

–

Root guard for preventing switches outside the network core from becoming the spanning-tree
root

–

Loop guard for preventing alternate or root ports from becoming designated ports because of a
failure that leads to a unidirectional link

• Flex Link Layer 2 interfaces to back up one another as an alternative to STP for basic link

redundancy

1-7

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 1 Overview

Features

• Link-state tracking to mirror the state of the ports that carry upstream traffic from connected hosts

and servers, and to allow the failover of the server traffic to an operational link on another Cisco
Ethernet switch.

• RPS support through the Cisco RPS 300 and Cisco RPS 675 for enhancing power reliability

VLAN Features

These are the VLAN features:

• Support for up to 255 VLANs for assigning users to VLANs associated with appropriate network

resources, traffic patterns, and bandwidth

• Support for VLAN IDs in the 1 to 4094 range as allowed by the IEEE 802.1Q standard

• VLAN Query Protocol (VQP) for dynamic VLAN membership

• IEEE 802.1Q trunking encapsulation on all ports for network moves, adds, and changes;

management and control of broadcast and multicast traffic; and network security by establishing
VLAN groups for high-security users and network resources

• Dynamic Trunking Protocol (DTP) for negotiating trunking on a link between two devices and for

negotiating the type of trunking encapsulation (IEEE 802.1Q) to be used

• VLAN Trunking Protocol (VTP) and VTP pruning for reducing network traffic by restricting

flooded traffic to links destined for stations receiving the traffic

• Voice VLAN for creating subnets for voice traffic from Cisco IP Phones

• VLAN 1 minimization for reducing the risk of spanning-tree loops or storms by allowing VLAN 1

to be disabled on any individual VLAN trunk link. With this feature enabled, no user traffic is sent
or received on the trunk. The switch CPU continues to send and receive control protocol frames.

• VLAN Flex Link Load Balancing to provide Layer 2 redundancy without requiring Spanning Tree

Protocol (STP). A pair of interfaces configured as primary and backup links can load balance traffic
based on VLAN.

Security Features

The switch ships with these security features:

• IP Service Level Agreements (IP SLAs) responder support that allows the switch to be a target

device for IP SLAs active traffic monitoring

• Web authentication to allow a supplicant (client) that does not support IEEE 802.1x functionality to

be authenticated using a web browser

• Password-protected access (read-only and read-write access) to management interfaces (device

manager, Network Assistant, and the CLI) for protection against unauthorized configuration
changes

• Multilevel security for a choice of security level, notification, and resulting actions

• Static MAC addressing for ensuring security

• Protected port option for restricting the forwarding of traffic to designated ports on the same switch

• Port security option for limiting and identifying MAC addresses of the stations allowed to access

the port

1-8

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 1 Overview

Features

• VLAN aware port security option to shut down the VLAN on the port when a violation occurs,

instead of shutting down the entire port.

• Port security aging to set the aging time for secure addresses on a port

• BPDU guard for shutting down a Port Fast-configured port when an invalid configuration occurs

• Standard and extended IP access control lists (ACLs) for defining inbound security policies on Layer

2 interfaces (port ACLs)

• Extended MAC access control lists for defining security policies in the inbound direction on Layer 2

interfaces

• Source and destination MAC-based ACLs for filtering non-IP traffic

• DHCP snooping to filter untrusted DHCP messages between untrusted hosts and DHCP servers

• IEEE 802.1x port-based authentication to prevent unauthorized devices (clients) from gaining

access to the network. These features are supported:

–

Dynamic voice virtual LAN (VLAN) for MDA to allow a dynamic voice VLAN on an
MDA-enabled port

–

VLAN assignment for restricting IEEE 802.1x-authenticated users to a specified VLAN

–

Port security for controlling access to IEEE 802.1x ports

–

Voice VLAN to permit a Cisco IP Phone to access the voice VLAN regardless of the authorized
or unauthorized state of the port

–

IP phone detection enhancement to detect and recognize a Cisco IP phone.

–

Guest VLAN to provide limited services to non-IEEE 802.1x-compliant users

–

Restricted VLAN to provide limited services to users who are IEEE 802.1x compliant, but do
not have the credentials to authenticate via the standard IEEE 802.1x processes

–

IEEE 802.1x accounting to track network usage

–

IEEE 802.1x with wake-on-LAN to allow dormant PCs to be powered on based on the receipt
of a specific Ethernet frame

• MAC authentication bypass to authorize clients based on the client MAC address.

• Network Admission Control (NAC) Layer 2 IEEE 802.1x validation of the antivirus condition or

posture of endpoint systems or clients before granting the devices network access.

For information about configuring NAC Layer 2 IEEE 802.1x validation, see the “Configuring NAC

Layer 2 IEEE 802.1x Validation” section on page 9-37.

• TACACS+, a proprietary feature for managing network security through a TACACS server

• RADIUS for verifying the identity of, granting access to, and tracking the actions of remote users

through authentication, authorization, and accounting (AAA) services

• Secure Socket Layer (SSL) Version 3.0 support for the HTTP 1.1 server authentication, encryption,

and message integrity and HTTP client authentication to allow secure HTTP communications
(requires the cryptographic version of the software)

1-9

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 1 Overview

Features

QoS and CoS Features

These are the QoS and CoS features:

• Automatic QoS (auto-QoS) to simplify the deployment of existing QoS features by classifying

traffic and configuring egress queues

• Classification

–

IP type-of-service/Differentiated Services Code Point (IP ToS/DSCP) and IEEE 802.1p CoS
marking priorities on a per-port basis for protecting the performance of mission-critical
applications

–

IP ToS/DSCP and IEEE 802.1p CoS marking based on flow-based packet classification
(classification based on information in the MAC, IP, and TCP/UDP headers) for
high-performance quality of service at the network edge, allowing for differentiated service
levels for different types of network traffic and for prioritizing mission-critical traffic in the
network

–

Trusted port states (CoS, DSCP, and IP precedence) within a QoS domain and with a port
bordering another QoS domain

–

Trusted boundary for detecting the presence of a Cisco IP Phone, trusting the CoS value
received, and ensuring port security

• Policing

–

Traffic-policing policies on the switch port for managing how much of the port bandwidth
should be allocated to a specific traffic flow

–

In Cisco IOS Release 12.2(25)SED and later, if you configure multiple class maps for a
hierarchical policy map, each class map can be associated with its own port-level (second-level)
policy map. Each second-level policy map can have a different policer.

–

Aggregate policing for policing traffic flows in aggregate to restrict specific applications or
traffic flows to metered, predefined rates

• Out-of-Profile

–

Out-of-profile markdown for packets that exceed bandwidth utilization limits

• Ingress queueing and scheduling

–

Two configurable ingress queues for user traffic (one queue can be the priority queue)

–

Weighted tail drop (WTD) as the congestion-avoidance mechanism for managing the queue
lengths and providing drop precedences for different traffic classifications

–

Shaped round robin (SRR) as the scheduling service for specifying the rate at which packets are
sent to the internal ring (sharing is the only supported mode on ingress queues)

• Egress queues and scheduling

–

Four egress queues per port

–

WTD as the congestion-avoidance mechanism for managing the queue lengths and providing
drop precedences for different traffic classifications

–

SRR as the scheduling service for specifying the rate at which packets are dequeued to the
egress interface (shaping or sharing is supported on egress queues). Shaped egress queues are
guaranteed but limited to using a share of port bandwidth. Shared egress queues are also
guaranteed a configured share of bandwidth, but can use more than the guarantee if other queues
become empty and do not use their share of the bandwidth.

1-10

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 1 Overview

Default Settings After Initial Switch Configuration

Monitoring Features

These are the monitoring features:

• Switch LEDs that provide port- and switch-level status

• MAC address notification traps and RADIUS accounting for tracking users on a network by storing

the MAC addresses that the switch has learned or removed

• Switched Port Analyzer (SPAN) and Remote SPAN (RSPAN) for traffic monitoring on any port or

VLAN

• SPAN and RSPAN support of Intrusion Detection Systems (IDS) to monitor, repel, and report

network security violations

• Four groups (history, statistics, alarms, and events) of embedded RMON agents for network

monitoring and traffic analysis

• Syslog facility for logging system messages about authentication or authorization errors, resource

issues, and time-out events

• Layer 2 traceroute to identify the physical path that a packet takes from a source device to a

destination device

• Time Domain Reflector (TDR) to diagnose and resolve cabling problems on 10/100 and

10/100/1000 copper Ethernet ports

• SFP module diagnostic management interface to monitor physical or operational status of an SFP

module

Default Settings After Initial Switch Configuration

The switch is designed for plug-and-play operation, requiring only that you assign basic IP information
to the switch and connect it to the other devices in your network. If you have specific network needs,
you can change the interface-specific and system-wide settings.

Note For information about assigning an IP address by using the browser-based Express Setup program, see

the getting started guide. For information about assigning an IP address by using the CLI-based setup
program, see the hardware installation guide.

If you do not configure the switch at all, the switch operates with these default settings:

• Default switch IP address, subnet mask, and default gateway is 0.0.0.0. For more information, see

Chapter 3, “Assigning the Switch IP Address and Default Gateway,” and Chapter 22, “Configuring
DHCP Features and IP Source Guard.”

• Default domain name is not configured. For more information, see Chapter 3, “Assigning the Switch

IP Address and Default Gateway.”

• DHCP client is enabled, the DHCP server is enabled (only if the device acting as a DHCP server is

configured and is enabled), and the DHCP relay agent is enabled (only if the device is acting as a
DHCP relay agent is configured and is enabled). For more information, see Chapter 3, “Assigning

the Switch IP Address and Default Gateway,” and Chapter 22, “Configuring DHCP Features and IP
Source Guard.”

• Switch cluster is disabled. For more information about switch clusters, see Chapter 5, “Clustering

Switches,” and the Getting Started with Cisco Network Assistant, available on Cisco.com.

1-11

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 1 Overview

Default Settings After Initial Switch Configuration

• No passwords are defined. For more information, see Chapter 6, “Administering the Switch.”

• System name and prompt is Switch. For more information, see Chapter 6, “Administering the

Switch.”

• NTP is enabled. For more information, see Chapter 6, “Administering the Switch.”

• DNS is enabled. For more information, see Chapter 6, “Administering the Switch.”

• TACACS+ is disabled. For more information, see Chapter 8, “Configuring Switch-Based

Authentication.”

• RADIUS is disabled. For more information, see Chapter 8, “Configuring Switch-Based

Authentication.”

• The standard HTTP server and Secure Socket Layer (SSL) HTTPS server are both enabled. For more

information, see Chapter 8, “Configuring Switch-Based Authentication.”

• IEEE 802.1x is disabled. For more information, see Chapter 9, “Configuring IEEE 802.1x

Port-Based Authentication.”

• Port parameters

–

Interface speed and duplex mode is autonegotiate. For more information, see Chapter 10,

“Configuring Interface Characteristics.”

–

Auto-MDIX is enabled. For more information, see Chapter 10, “Configuring Interface

Characteristics.”

–

Flow control is off. For more information, see Chapter 10, “Configuring Interface

Characteristics.”

• No Smartports macros are defined. For more information, see Chapter 11, “Configuring Smartports

Macros.”

• VLANs

–

Default VLAN is VLAN 1. For more information, see Chapter 12, “Configuring VLANs.”

–

VLAN trunking setting is dynamic auto (DTP). For more information, see Chapter 12,

“Configuring VLANs.”

–

Trunk encapsulation is negotiate. For more information, see Chapter 12, “Configuring

VLANs.”

–

VTP mode is server. For more information, see Chapter 13, “Configuring VTP.”

–

VTP version is Version 1. For more information, see Chapter 13, “Configuring VTP.”

–

Voice VLAN is disabled. For more information, see Chapter 14, “Configuring Voice VLAN.”

• STP, PVST+ is enabled on VLAN 1. For more information, see Chapter 15, “Configuring STP.”

• MSTP is disabled. For more information, see Chapter 16, “Configuring MSTP.”

• Optional spanning-tree features are disabled. For more information, see Chapter 17, “Configuring

Optional Spanning-Tree Features.”

• Flex Links are not configured. For more information, see Chapter 21, “Configuring Flex Links and

the MAC Address-Table Move Update Feature.”

• DHCP snooping is disabled. The DHCP snooping information option is enabled. For more

information, see Chapter 22, “Configuring DHCP Features and IP Source Guard.”

• IGMP snooping is enabled. No IGMP filters are applied. For more information, see Chapter 18,

“Configuring IGMP Snooping and MVR.”

1-12

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 1 Overview

Network Configuration Examples

• IGMP throttling setting is deny. For more information, see Chapter 18, “Configuring IGMP

Snooping and MVR.”

• The IGMP snooping querier feature is disabled. For more information, see Chapter 18, “Configuring

IGMP Snooping and MVR.”

• MVR is disabled. For more information, see Chapter 18, “Configuring IGMP Snooping and MVR.”

• Port-based traffic

–

Broadcast, multicast, and unicast storm control is disabled. For more information, see

Chapter 19, “Configuring Port-Based Traffic Control.”

–

No protected ports are defined. For more information, see Chapter 19, “Configuring Port-Based

Traffic Control.”

–

Unicast and multicast traffic flooding is not blocked. For more information, see Chapter 19,

“Configuring Port-Based Traffic Control.”

–

No secure ports are configured. For more information, see Chapter 19, “Configuring Port-Based

Traffic Control.”

• CDP is enabled. For more information, see Chapter 20, “Configuring CDP.”

• UDLD is disabled. For more information, see Chapter 22, “Configuring UDLD.”

• SPAN and RSPAN are disabled. For more information, see Chapter 23, “Configuring SPAN and

RSPAN.”

• RMON is disabled. For more information, see Chapter 24, “Configuring RMON.”

• Syslog messages are enabled and appear on the console. For more information, see Chapter 25,

“Configuring System Message Logging.”

• SNMP is enabled (Version 1). For more information, see Chapter 26, “Configuring SNMP.”

• No ACLs are configured. For more information, see Chapter 34, “Configuring Network Security

with ACLs.”

• QoS is disabled. For more information, see Chapter 28, “Configuring QoS.”

• No EtherChannels are configured. For more information, see Chapter 31, “Configuring

EtherChannels and Link-State Tracking.”

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.

• “Design Concepts for Using the Switch” section on page 1-12

• “Small to Medium-Sized Network Using Catalyst 2960 Switches” section on page 1-16

• “Long-Distance, High-Bandwidth Transport Configuration” section on page 1-17

Design Concepts for Using the Switch

As your network users compete for network bandwidth, it takes longer to send and receive data. When
you configure your network, consider the bandwidth required by your network users and the relative
priority of the network applications that they use.

1-13

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 1 Overview

Network Configuration Examples

Table 1-1 describes what can cause network performance to degrade and how you can configure your

network to increase the bandwidth available to your network users.

Bandwidth alone is not the only consideration when designing your network. As your network traffic
profiles evolve, consider providing network services that can support applications for voice and data
integration, multimedia integration, application prioritization, and security. Table 1-2 describes some
network demands and how you can meet them.

Table 1-1 Increasing Network Performance

Network Demands Suggested Design Methods

Too many users on a single network
segment and a growing number of
users accessing the Internet

• Create smaller network segments so that fewer users share the bandwidth, and use

VLANs and IP subnets to place the network resources in the same logical network
as the users who access those resources most.

• Use full-duplex operation between the switch and its connected workstations.

• Increased power of new PCs,

workstations, and servers

• High bandwidth demand from

networked applications (such as
e-mail with large attached files)
and from bandwidth-intensive
applications (such as
multimedia)

• Connect global resources—such as servers and routers to which the network users

require equal access—directly to the high-speed switch ports so that they have
their own high-speed segment.

• Use the EtherChannel feature between the switch and its connected servers and

routers.

Table 1-2 Providing Network Services

Network Demands Suggested Design Methods

Efficient bandwidth usage for
multimedia applications and
guaranteed bandwidth for critical
applications

• Use IGMP snooping to efficiently forward multimedia and multicast traffic.

• Use other QoS mechanisms such as packet classification, marking, scheduling,

and congestion avoidance to classify traffic with the appropriate priority level,
thereby providing maximum flexibility and support for mission-critical, unicast,
and multicast and multimedia applications.

• Use MVR to continuously send multicast streams in a multicast VLAN but to

isolate the streams from subscriber VLANs for bandwidth and security reasons.

High demand on network redundancy
and availability to provide always on
mission-critical applications

• Use VLAN trunks and BackboneFast for traffic-load balancing on the uplink ports

so that the uplink port with a lower relative port cost is selected to carry the VLAN
traffic.

1-14

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 1 Overview

Network Configuration Examples

You can use the switches to create the following:

• Cost-effective Gigabit-to-the-desktop for high-performance workgroups (Figure 1-1)—For

high-speed access to network resources, you can use the Cisco Catalyst 2960 switches in the access
layer to provide Gigabit Ethernet to the desktop. To prevent congestion, use QoS DSCP marking
priorities on these switches. For high-speed IP forwarding at the distribution layer, connect the
switches in the access layer to a Gigabit multilayer switch with routing capability, such as a
Catalyst 3750 switch, or to a router.

The first illustration is of an isolated high-performance workgroup, where the Catalyst 2960
switches are connected to Catalyst 3750 switches in the distribution layer. The second illustration is
of a high-performance workgroup in a branch office, where the Catalyst 2960 switches are
connected to a router in the distribution layer.

Each switch in this configuration provides users with a dedicated 1-Gb/s connection to network
resources. Using SFP modules also provides flexibility in media and distance options through
fiber-optic connections.

Figure 1-1 High-Performance Workgroup (Gigabit-to-the-Desktop)

An evolving demand for IP telephony • Use QoS to prioritize applications such as IP telephony during congestion and to

help control both delay and jitter within the network.

• Use switches that support at least two queues per port to prioritize voice and data

traffic as either high- or low-priority, based on IEEE 802.1p/Q. The switch
supports at least four queues per port.

• Use voice VLAN IDs (VVIDs) to provide separate VLANs for voice traffic.

A growing demand for using existing
infrastructure to transport data and
voice from a home or office to the
Internet or an intranet at higher
speeds

Use the Catalyst Long-Reach Ethernet (LRE) switches to provide up to 15 Mb of IP
connectivity over existing infrastructure, such as existing telephone lines.

Note LRE is the technology used in the Catalyst 2900 LRE XL and Catalyst 2950

LRE switches. See the documentation sets specific to these switches for LRE
information.

Table 1-2 Providing Network Services (continued)

Network Demands Suggested Design Methods

89373

Access-layer
Catalyst
switches

Catalyst 3750
switches

1-15

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 1 Overview

Network Configuration Examples

• Server aggregation (Figure 1-2)—You can use the switches to interconnect groups of servers,

centralizing physical security and administration of your network. For high-speed IP forwarding at
the distribution layer, connect the switches in the access layer to multilayer switches with routing
capability. The Gigabit interconnections minimize latency in the data flow.

QoS and policing on the switches provide preferential treatment for certain data streams. They
segment traffic streams into different paths for processing. Security features on the switch ensure
rapid handling of packets.

Fault tolerance from the server racks to the core is achieved through dual homing of servers
connected to switches, which have redundant Gigabit EtherChannels.

Using dual SFP module uplinks from the switches provides redundant uplinks to the network core.
Using SFP modules provides flexibility in media and distance options through fiber-optic
connections.

89374

Cisco 2600
router

Access-layer
Catalyst
switches

WAN

1-16

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 1 Overview

Network Configuration Examples

Figure 1-2 Server Aggregation

Small to Medium-Sized Network Using Catalyst 2960 Switches

Figure 1-3 shows a configuration for a network of up to 500 employees. This network uses Catalyst 2960

switches with high-speed connections to two routers. This ensures connectivity to the Internet, WAN,
and mission-critical network resources in case one of the routers fails. The switches are using
EtherChannel for load sharing.

The switches are connected to workstations and local servers. The server farm includes a call-processing
server running Cisco CallManager software. Cisco CallManager controls call processing, routing, and
Cisco IP Phone features and configuration. The switches are interconnected through Gigabit interfaces.

This network uses VLANs to logically segment the network into well-defined broadcast groups and for
security management. Data and multimedia traffic are configured on the same VLAN. Voice traffic from
the Cisco IP Phones are configured on separate VVIDs. If data, multimedia, and voice traffic are
assigned to the same VLAN, only one VLAN can be configured per wiring closet.

When an end station in one VLAN needs to communicate with an end station in another VLAN, a router
routes the traffic to the destination VLAN. In this network, the routers are providing inter-VLAN
routing. VLAN access control lists (VLAN maps) on the switch provide intra-VLAN security and
prevent unauthorized users from accessing critical areas of the network.

In addition to inter-VLAN routing, the routers provide QoS mechanisms such as DSCP priorities to
prioritize the different types of network traffic and to deliver high-priority traffic. If congestion occurs,
QoS drops low-priority traffic to allow delivery of high-priority traffic.

Cisco CallManager controls call processing, routing, and Cisco IP Phone features and configuration.
Users with workstations running Cisco SoftPhone software can place, receive, and control calls from
their PCs. Using Cisco IP Phones, Cisco CallManager software, and Cisco SoftPhone software integrates
telephony and IP networks, and the IP network supports both voice and data.

The routers also provide firewall services, Network Address Translation (NAT) services, voice-over-IP
(VoIP) gateway services, and WAN and Internet access.

89376

Campus

core

Catalyst
6500 switches

Catalyst 3750
StackWise
switch stacks

Access-layer
Catalyst
switches

Server racks

1-17

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 1 Overview

Network Configuration Examples

Figure 1-3 Catalyst 2960 Switches in a Collapsed Backbone Configuration

Long-Distance, High-Bandwidth Transport Configuration

Figure 1-4 shows a configuration for sending 8 Gigabits of data over a single fiber-optic cable. The

Catalyst 2960 switches have coarse wavelength-division multiplexing (CWDM) fiber-optic SFP
modules installed. Depending on the CWDM SFP module, data is sent at wavelengths from 1470 to
1610 nm. The higher the wavelength, the farther the transmission can travel. A common wavelength used
for long-distance transmissions is 1550 nm.

The CWDM SFP modules connect to CWDM optical add/drop multiplexer (OADM) modules over
distances of up to 393,701 feet (74.5 miles or 120 km). The CWDM OADM modules combine (or
multiplex) the different CWDM wavelengths, allowing them to travel simultaneously on the same
fiber-optic cable. The CWDM OADM modules on the receiving end separate (or demultiplex) the
different wavelengths.

For more information about the CWDM SFP modules and CWDM OADM modules, see the Cisco
CWDM GBIC and CWDM SFP Installation Note.

Gigabit
servers

101388

Cisco 2600 or

3700 routers

Internet

Cisco IP

phones

Workstations

running

Cisco SoftPhone

software

Aironet wireless

access points

IP IP

1-18

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 1 Overview

Where to Go Next

Figure 1-4 Long-Distance, High-Bandwidth Transport Configuration

Where to Go Next

Before configuring the switch, review these sections for startup information:

• Chapter 2, “Using the Command-Line Interface”

• Chapter 3, “Assigning the Switch IP Address and Default Gateway”

95750

Access layer

Catalyst 4500

multilayer

switches

Eight

1-Gbps

connections

8 Gbps

Catalyst switches

CWDM

OADM

modules

CWDM

OADM

modules

Aggregation layer

CHA PTER

2-1

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

2

Using the Command-Line Interface

This chapter describes the Cisco IOS command-line interface (CLI) and how to use it to configure your
Catalyst 2960 switch. It contains these sections:

• Understanding Command Modes, page 2-1

• Understanding the Help System, page 2-3

• Understanding Abbreviated Commands, page 2-4

• Understanding no and default Forms of Commands, page 2-4

• Understanding CLI Error Messages, page 2-5

• Using Configuration Logging, page 2-5

• Using Command History, page 2-6

• Using Editing Features, page 2-7

• Searching and Filtering Output of show and more Commands, page 2-10

• Accessing the CLI, page 2-10

Understanding Command Modes

The Cisco IOS user interface is divided into many different modes. The commands available to you
depend on which mode you are currently in. Enter a question mark (?) at the system prompt to obtain a
list of commands available for each command mode.

When you start a session on the switch, you begin in user mode, often called user EXEC mode. Only a
limited subset of the commands are available in user EXEC mode. For example, most of the user EXEC
commands are one-time commands, such as show commands, which show the current configuration
status, and clear commands, which clear counters or interfaces. The user EXEC commands are not saved
when the switch reboots.

To have access to all commands, you must enter privileged EXEC mode. Normally, you must enter a
password to enter privileged EXEC mode. From this mode, you can enter any privileged EXEC
command or enter global configuration mode.

Using the configuration modes (global, interface, and line), you can make changes to the running
configuration. If you save the configuration, these commands are stored and used when the switch
reboots. To access the various configuration modes, you must start at global configuration mode. From
global configuration mode, you can enter interface configuration mode and line configuration mode.

2-2

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 2 Using the Command-Line Interface

Understanding Command Modes

Table 2-1 describes the main command modes, how to access each one, the prompt you see in that mode,

and how to exit the mode. The examples in the table use the hostname Switch.

Table 2-1 Command Mode Summary

Mode Access Method Prompt Exit Method About This Mode

User EXEC Begin a session with

your switch.

Switch>

Enter logout or
quit.

Use this mode to

• Change terminal settings.

• Perform basic tests.

• Display system

information.

Privileged EXEC While in user EXEC

mode, enter the
enable command.

Switch#

Enter disable to
exit.

Use this mode to verify
commands that you have
entered. Use a password to
protect access to this mode.

Global configuration While in privileged

EXEC mode, enter
the configure
command.

Switch(config)#

To exit to privileged
EXEC mode, enter

exit or end, or press
Ctrl-Z.

Use this mode to configure
parameters that apply to the
entire switch.

Config-vlan While in global

configuration mode,
enter the
vlan vlan-id
command.

Switch(config-vlan)#

To exit to global
configuration mode,
enter the exit
command.

To return to
privileged EXEC
mode, press Ctrl-Z
or enter end.

Use this mode to configure
VLAN parameters. When VTP
mode is transparent, you can
create extended-range VLANs
(VLAN IDs greater than 1005)
and save configurations in the
switch startup configuration
file.

VLAN configuration While in privileged

EXEC mode, enter
the vlan database
command.

Switch(vlan)#

To exit to privileged
EXEC mode, enter
exit.

Use this mode to configure
VLAN parameters for VLANs
1 to 1005 in the VLAN
database.

2-3

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 2 Using the Command-Line Interface

Understanding the Help System

For more detailed information on the command modes, see the command reference guide for this release.

Understanding the Help System

You can enter a question mark (?) at the system prompt to display a list of commands available for each
command mode. You can also obtain a list of associated keywords and arguments for any command, as
shown in Table 2 -2.

Interface
configuration

While in global
configuration mode,
enter the interface
command (with a
specific interface).

Switch(config-if)#

To exit to global
configuration mode,
enter exit.

To return to
privileged EXEC
mode, press Ctrl-Z
or enter end.

Use this mode to configure
parameters for the Ethernet
ports.

For information about defining
interfaces, see the “Using

Interface Configuration Mode”
section on page 10-4.

To configure multiple
interfaces with the same
parameters, see the

“Configuring a Range of
Interfaces” section on
page 10-6.

Line configuration While in global

configuration mode,
specify a line with
the line vty or line
console command.

Switch(config-line)#

To exit to global
configuration mode,
enter exit.

To return to
privileged EXEC
mode, press Ctrl-Z
or enter end.

Use this mode to configure
parameters for the terminal
line.

Table 2-1 Command Mode Summary (continued)

Mode Access Method Prompt Exit Method About This Mode

Ta b l e 2 -2 H e l p S u m m ar y

Command Purpose

help Obtain a brief description of the help system in any command mode.

abbreviated-command-entry? Obtain a list of commands that begin with a particular character string.

For example:

Switch# di?
dir disable disconnect

abbreviated-command-entry<Ta b> Complete a partial command name.

For example:

Switch# sh conf<tab>
Switch# show configuration

2-4

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 2 Using the Command-Line Interface

Understanding Abbreviated Commands

Understanding Abbreviated Commands

You need to enter only enough characters for the switch to recognize the command as unique.

This example shows how to enter the show configuration privileged EXEC command in an abbreviated
form:

Switch# show conf

Understanding no and default Forms of Commands

Almost every configuration command also has a no form. In general, use the no form to disable a feature
or function or reverse the action of a command. For example, the no shutdown interface configuration
command reverses the shutdown of an interface. Use the command without the keyword no to re-enable
a disabled feature or to enable a feature that is disabled by default.

Configuration commands can also have a default form. The default form of a command returns the
command setting to its default. Most commands are disabled by default, so the default form is the same
as the no form. However, some commands are enabled by default and have variables set to certain default
values. In these cases, the default command enables the command and sets variables to their default
values.

? List all commands available for a particular command mode.

For example:

Switch> ?

command ? List the associated keywords for a command.

For example:

Switch> show ?

command keyword ? List the associated arguments for a keyword.

For example:

Switch(config)# cdp holdtime ?
<10-255> Length of time (in sec) that receiver must keep this packet

Table 2-2 Help Summary (continued)

Command Purpose

2-5

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 2 Using the Command-Line Interface

Understanding CLI Error Messages

Understanding CLI Error Messages

Table 2-3 lists some error messages that you might encounter while using the CLI to configure your

switch.

Using Configuration Logging

Beginning with Cisco IOS Release 12.2(25)SED, you can log and view changes to the switch
configuration. You can use the Configuration Change Logging and Notification feature to track changes
on a per-session and per-user basis. The logger tracks each configuration command that is applied, the
user who entered the command, the time that the command was entered, and the parser return code for
the command. This feature includes a mechanism for asynchronous notification to registered
applications whenever the configuration changes. You can choose to have the notifications sent to the
syslog.

For more information, see the Configuration Change Notification and Logging feature module at this
URL:

http://www.cisco.com/en/US/products/sw/iosswrel/ps5207/products_feature_guide09186a00801d1e81.
html

Note Only CLI or HTTP changes are logged.

Table 2-3 Common CLI Error Messages

Error Message Meaning How to Get Help

% Ambiguous command:
"show con"

You did not enter enough characters
for your switch to recognize the
command.

Re-enter the command followed by a question mark (?)
with a space between the command and the question
mark.

The possible keywords that you can enter with the
command appear.

% Incomplete command.

You did not enter all the keywords or
values required by this command.

Re-enter the command followed by a question mark (?)
with a space between the command and the question
mark.

The possible keywords that you can enter with the
command appear.

% Invalid input detected
at ‘^’ marker.

You entered the command
incorrectly. The caret (^) marks the
point of the error.

Enter a question mark (?) to display all the commands
that are available in this command mode.

The possible keywords that you can enter with the
command appear.

2-6

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 2 Using the Command-Line Interface

Using Command History

Using Command History

The software provides a history or record of commands that you have entered. The command history
feature is particularly useful for recalling long or complex commands or entries, including access lists.
You can customize this feature to suit your needs as described in these sections:

• Changing the Command History Buffer Size, page 2-6 (optional)

• Recalling Commands, page 2-6 (optional)

• Disabling the Command History Feature, page 2-7 (optional)

Changing the Command History Buffer Size

By default, the switch records ten command lines in its history buffer. You can alter this number for a
current terminal session or for all sessions on a particular line. These procedures are optional.

Beginning in privileged EXEC mode, enter this command to change the number of command lines that
the switch records during the current terminal session:

Switch# terminal history [size

number-of-lines

]

The range is from 0 to 256.

Beginning in line configuration mode, enter this command to configure the number of command lines
the switch records for all sessions on a particular line:

Switch(config-line)# history [size

number-of-lines

]

The range is from 0 to 256.

Recalling Commands

To recall commands from the history buffer, perform one of the actions listed in Table 2-4. These actions
are optional.

Table 2-4 Recalling Commands

Action

1

1. The arrow keys function only on ANSI-compatible terminals such as VT100s.

Result

Press Ctrl-P or the up arrow key. Recall commands in the history buffer, beginning with the most recent command.

Repeat the key sequence to recall successively older commands.

Press Ctrl-N or the down arrow key. Return to more recent commands in the history buffer after recalling commands

with Ctrl-P or the up arrow key. Repeat the key sequence to recall successively
more recent commands.

show history While in privileged EXEC mode, list the last several commands that you just

entered. The number of commands that appear is controlled by the setting of the
terminal history global configuration command and the history line configuration
command.

2-7

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 2 Using the Command-Line Interface

Using Editing Features

Disabling the Command History Feature

The command history feature is automatically enabled. You can disable it for the current terminal
session or for the command line. These procedures are optional.

To disable the feature during the current terminal session, enter the terminal no history privileged
EXEC command.

To disable command history for the line, enter the no history line configuration command.

Using Editing Features

This section describes the editing features that can help you manipulate the command line. It contains
these sections:

• Enabling and Disabling Editing Features, page 2-7 (optional)

• Editing Commands through Keystrokes, page 2-7 (optional)

• Editing Command Lines that Wrap, page 2-9 (optional)

Enabling and Disabling Editing Features

Although enhanced editing mode is automatically enabled, you can disable it, re-enable it, or configure
a specific line to have enhanced editing. These procedures are optional.

To globally disable enhanced editing mode, enter this command in line configuration mode:

Switch (config-line)# no editing

To re-enable the enhanced editing mode for the current terminal session, enter this command in
privileged EXEC mode:

Switch# terminal editing

To reconfigure a specific line to have enhanced editing mode, enter this command in line configuration
mode:

Switch(config-line)# editing

Editing Commands through Keystrokes

Table 2-5 shows the keystrokes that you need to edit command lines. These keystrokes are optional.

Table 2-5 Editing Commands through Keystrokes

Capability Keystroke

1

Purpose

Move around the command line to
make changes or corrections.

Press Ctrl-B, or press the
left arrow key.

Move the cursor back one character.

2-8

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 2 Using the Command-Line Interface

Using Editing Features

Press Ctrl-F, or press the
right arrow key.

Move the cursor forward one character.

Press Ctrl-A. Move the cursor to the beginning of the command line.

Press Ctrl-E. Move the cursor to the end of the command line.

Press Esc B. Move the cursor back one word.

Press Esc F. Move the cursor forward one word.

Press Ctrl-T. Transpose the character to the left of the cursor with the

character located at the cursor.

Recall commands from the buffer and
paste them in the command line. The
switch provides a buffer with the last
ten items that you deleted.

Press Ctrl-Y. Recall the most recent entry in the buffer.

Press Esc Y. Recall the next buffer entry.

The buffer contains only the last 10 items that you have
deleted or cut. If you press Esc Y more than ten times, you
cycle to the first buffer entry.

Delete entries if you make a mistake
or change your mind.

Press the Delete or
Backspace key.

Erase the character to the left of the cursor.

Press Ctrl-D. Delete the character at the cursor.

Press Ctrl-K. Delete all characters from the cursor to the end of the

command line.

Press Ctrl-U or Ctrl-X. Delete all characters from the cursor to the beginning of

the command line.

Press Ctrl-W. Delete the word to the left of the cursor.

Press Esc D. Delete from the cursor to the end of the word.

Capitalize or lowercase words or
capitalize a set of letters.

Press Esc C. Capitalize at the cursor.

Press Esc L. Change the word at the cursor to lowercase.

Press Esc U. Capitalize letters from the cursor to the end of the word.

Designate a particular keystroke as
an executable command, perhaps as a
shortcut.

Press Ctrl-V or Esc Q.

Table 2-5 Editing Commands through Keystrokes (continued)

Capability Keystroke

1

Purpose

2-9

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 2 Using the Command-Line Interface

Using Editing Features

Editing Command Lines that Wrap

You can use a wraparound feature for commands that extend beyond a single line on the screen. When
the cursor reaches the right margin, the command line shifts ten spaces to the left. You cannot see the
first ten characters of the line, but you can scroll back and check the syntax at the beginning of the
command. The keystroke actions are optional.

To scroll back to the beginning of the command entry, press Ctrl-B or the left arrow key repeatedly. You
can also press Ctrl-A to immediately move to the beginning of the line.

The arrow keys function only on ANSI-compatible terminals such as VT100s.

In this example, the access-list global configuration command entry extends beyond one line. When the
cursor first reaches the end of the line, the line is shifted ten spaces to the left and redisplayed. The dollar
sign ($) shows that the line has been scrolled to the left. Each time the cursor reaches the end of the line,
the line is again shifted ten spaces to the left.

Switch(config)# access-list 101 permit tcp 131.108.2.5 255.255.255.0 131.108.1
Switch(config)# $ 101 permit tcp 131.108.2.5 255.255.255.0 131.108.1.20 255.25
Switch(config)# $t tcp 131.108.2.5 255.255.255.0 131.108.1.20 255.255.255.0 eq
Switch(config)# $108.2.5 255.255.255.0 131.108.1.20 255.255.255.0 eq 45

After you complete the entry, press Ctrl-A to check the complete syntax before pressing the Return key
to execute the command. The dollar sign ($) appears at the end of the line to show that the line has been
scrolled to the right:

Switch(config)# access-list 101 permit tcp 131.108.2.5 255.255.255.0 131.108.1$

The software assumes you have a terminal screen that is 80 columns wide. If you have a width other than
that, use the terminal width privileged EXEC command to set the width of your terminal.

Use line wrapping with the command history feature to recall and modify previous complex command
entries. For information about recalling previous command entries, see the “Editing Commands through

Keystrokes” section on page 2-7.

Scroll down a line or screen on
displays that are longer than the
terminal screen can display.

Note The More prompt is used for

any output that has more
lines than can be displayed
on the terminal screen,
including show command
output. You can use the
Return and Space bar
keystrokes whenever you see
the More prompt.

Press the Return key. Scroll down one line.

Press the Space bar. Scroll down one screen.

Redisplay the current command line
if the switch suddenly sends a
message to your screen.

Press Ctrl-L or Ctrl-R. Redisplay the current command line.

1. The arrow keys function only on ANSI-compatible terminals such as VT100s.

Table 2-5 Editing Commands through Keystrokes (continued)

Capability Keystroke

1

Purpose

2-10

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 2 Using the Command-Line Interface

Searching and Filtering Output of show and more Commands

Searching and Filtering Output of show and more Commands

You can search and filter the output for show and more commands. This is useful when you need to sort
through large amounts of output or if you want to exclude output that you do not need to see. Using these
commands is optional.

To use this functionality, enter a show or more command followed by the pipe character (|), one of the
keywords begin, include, or exclude, and an expression that you want to search for or filter out:

command | {begin | include | exclude} regular-expression

Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output appear.

This example shows how to include in the output display only lines where the expression protocol
appears:

Switch# show interfaces | include protocol
Vlan1 is up, line protocol is up
Vlan10 is up, line protocol is down
GigabitEthernet0/1 is up, line protocol is down
GigabitEthernet0/2 is up, line protocol is up

Accessing the CLI

You can access the CLI through a console connection, through Telnet, or by using the browser.

Accessing the CLI through a Console Connection or through Telnet

Before you can access the CLI, you must connect a terminal or PC to the switch console port and power
on the switch, as described in the getting started guide that shipped with your switch. Then, to understand
the boot process and the options available for assigning IP information, see Chapter 3, “Assigning the

Switch IP Address and Default Gateway.”

If your switch is already configured, you can access the CLI through a local console connection or
through a remote Telnet session, but your switch must first be configured for this type of access. For
more information, see the “Setting a Telnet Password for a Terminal Line” section on page 8-6.

You can use one of these methods to establish a connection with the switch:

• Connect the switch console port to a management station or dial-up modem. For information about

connecting to the console port, see the switch getting started guide or hardware installation guide.

• Use any Telnet TCP/IP or encrypted Secure Shell (SSH) package from a remote management

station. The switch must have network connectivity with the Telnet or SSH client, and the switch
must have an enable secret password configured.

For information about configuring the switch for Telnet access, see the “Setting a Telnet Password

for a Terminal Line” section on page 8-6. The switch supports up to 16 simultaneous Telnet

sessions. Changes made by one Telnet user are reflected in all other Telnet sessions.

For information about configuring the switch for SSH, see the “Configuring the Switch for Secure

Shell” section on page 8-33. The switch supports up to five simultaneous secure SSH sessions.

After you connect through the console port, through a Telnet session or through an SSH session, the
user EXEC prompt appears on the management station.

CHA PTER

3-1

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

3

Assigning the Switch IP Address and Default
Gateway

This chapter describes how to create the initial switch configuration (for example, assigning the IP
address and default gateway information) for the Catalyst 2960 switch by using a variety of automatic
and manual methods. It also describes how to modify the switch startup configuration.

Note For complete syntax and usage information for the commands used in this chapter, see the command

reference for this release and the Cisco IOS IP Command Reference, Volume 1 of 3: Addressing and
Services from the Cisco.com page under Documentation > Cisco IOS Software > 12.2 Mainline >

Command References.

This chapter consists of these sections:

• Understanding the Boot Process, page 3-1

• Assigning Switch Information, page 3-2

• Checking and Saving the Running Configuration, page 3-10

• Modifying the Startup Configuration, page 3-11

• Scheduling a Reload of the Software Image, page 3-16

Understanding the Boot Process

To start your switch, you need to follow the procedures in the Getting Started Guide or the hardware
installation guide for installing and powering on the switch and setting up the initial switch configuration
(IP address, subnet mask, default gateway, secret and Telnet passwords, and so forth).

The normal boot process involves the operation of the boot loader software, which performs these
activities:

• Performs low-level CPU initialization. It initializes the CPU registers, which control where physical

memory is mapped, its quantity, its speed, and so forth.

• Performs power-on self-test (POST) for the CPU subsystem. It tests the CPU DRAM and the portion

of the flash device that makes up the flash file system.

• Initializes the flash file system on the system board.

• Loads a default operating system software image into memory and boots up the switch.

3-2

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 3 Assigning the Switch IP Address and Default Gateway

Assigning Switch Information

The boot loader provides access to the flash file system before the operating system is loaded. Normally,
the boot loader is used only to load, uncompress, and launch the operating system. After the boot loader
gives the operating system control of the CPU, the boot loader is not active until the next system reset
or power-on.

The boot loader also provides trap-door access into the system if the operating system has problems
serious enough that it cannot be used. The trap-door mechanism provides enough access to the system
so that if it is necessary, you can format the flash file system, reinstall the operating system software
image by using the Xmodem Protocol, recover from a lost or forgotten password, and finally restart the
operating system. For more information, see the “Recovering from a Software Failure” section on

page 32-2 and the “Recovering from a Lost or Forgotten Password” section on page 32-3.

Note You can disable password recovery. For more information, see the “Disabling Password Recovery”

section on page 8-5.

Before you can assign switch information, make sure you have connected a PC or terminal to the console
port, and configured the PC or terminal-emulation software baud rate and character format to match
these of the switch console port:

• Baud rate default is 9600.

• Data bits default is 8.

Note If the data bits option is set to 8, set the parity option to none.

• Stop bits default is 1.

• Parity settings default is none.

Assigning Switch Information

You can assign IP information through the switch setup program, through a DHCP server, or manually.

Use the switch setup program if you want to be prompted for specific IP information. With this program,
you can also configure a hostname and an enable secret password. It gives you the option of assigning a
Telnet password (to provide security during remote management) and configuring your switch as a
command or member switch of a cluster or as a standalone switch. For more information about the setup
program, see the hardware installation guide.

Use a DHCP server for centralized control and automatic assignment of IP information after the server
is configured.

Note If you are using DHCP, do not respond to any of the questions in the setup program until the switch

receives the dynamically assigned IP address and reads the configuration file.

If you are an experienced user familiar with the switch configuration steps, manually configure the
switch. Otherwise, use the setup program described previously.

3-3

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 3 Assigning the Switch IP Address and Default Gateway

Assigning Switch Information

These sections contain this configuration information:

• Default Switch Information, page 3-3

• Understanding DHCP-Based Autoconfiguration, page 3-3

• Manually Assigning IP Information, page 3-10

Default Switch Information

Table 3-1 shows the default switch information.

Understanding DHCP-Based Autoconfiguration

DHCP provides configuration information to Internet hosts and internetworking devices. This protocol
consists of two components: one for delivering configuration parameters from a DHCP server to a device
and a mechanism for allocating network addresses to devices. DHCP is built on a client-server model,
in which designated DHCP servers allocate network addresses and deliver configuration parameters to
dynamically configured devices. The switch can act as both a DHCP client and a DHCP server.

During DHCP-based autoconfiguration, your switch (DHCP client) is automatically configured at
startup with IP address information and a configuration file.

With DHCP-based autoconfiguration, no DHCP client-side configuration is needed on your switch.
However, you need to configure the DHCP server for various lease options associated with IP addresses.
If you are using DHCP to relay the configuration file location on the network, you might also need to
configure a Trivial File Transfer Protocol (TFTP) server and a Domain Name System (DNS) server.

The DHCP server for your switch can be on the same LAN or on a different LAN than the switch. If the
DHCP server is running on a different LAN, you should configure a DHCP relay device between your
switch and the DHCP server. A relay device forwards broadcast traffic between two directly connected
LANs. A router does not forward broadcast packets, but it forwards packets based on the destination IP
address in the received packet.

DHCP-based autoconfiguration replaces the BOOTP client functionality on your switch.

Table 3-1 Default Switch Information

Feature Default Setting

IP address and subnet mask No IP address or subnet mask are defined.

Default gateway No default gateway is defined.

Enable secret password No password is defined.

Hostname The factory-assigned default hostname is Switch.

Telnet password No password is defined.

Cluster command switch functionality Disabled.

Cluster name No cluster name is defined.

3-4

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 3 Assigning the Switch IP Address and Default Gateway

Assigning Switch Information

DHCP Client Request Process

When you boot up your switch, the DHCP client is invoked and requests configuration information from
a DHCP server when the configuration file is not present on the switch. If the configuration file is present
and the configuration includes the ip address dhcp interface configuration command on specific routed
interfaces, the DHCP client is invoked and requests the IP address information for those interfaces.

Figure 3-1 shows the sequence of messages that are exchanged between the DHCP client and the DHCP

server.

Figure 3-1 DHCP Client and Server Message Exchange

The client, Switch A, broadcasts a DHCPDISCOVER message to locate a DHCP server. The DHCP
server offers configuration parameters (such as an IP address, subnet mask, gateway IP address, DNS IP
address, a lease for the IP address, and so forth) to the client in a DHCPOFFER unicast message.

In a DHCPREQUEST broadcast message, the client returns a formal request for the offered
configuration information to the DHCP server. The formal request is broadcast so that all other DHCP
servers that received the DHCPDISCOVER broadcast message from the client can reclaim the IP
addresses that they offered to the client.

The DHCP server confirms that the IP address has been allocated to the client by returning a DHCPACK
unicast message to the client. With this message, the client and server are bound, and the client uses
configuration information received from the server. The amount of information the switch receives
depends on how you configure the DHCP server. For more information, see the “Configuring the TFTP

Server” section on page 3-6.

If the configuration parameters sent to the client in the DHCPOFFER unicast message are invalid (a
configuration error exists), the client returns a DHCPDECLINE broadcast message to the DHCP server.

The DHCP server sends the client a DHCPNAK denial broadcast message, which means that the offered
configuration parameters have not been assigned, that an error has occurred during the negotiation of the
parameters, or that the client has been slow in responding to the DHCPOFFER message (the DHCP
server assigned the parameters to another client).

A DHCP client might receive offers from multiple DHCP or BOOTP servers and can accept any of the
offers; however, the client usually accepts the first offer it receives. The offer from the DHCP server is
not a guarantee that the IP address is allocated to the client; however, the server usually reserves the
address until the client has had a chance to formally request the address. If the switch accepts replies
from a BOOTP server and configures itself, the switch broadcasts, instead of unicasts, TFTP requests to
obtain the switch configuration file.

Switch A

DHCPACK (unicast)

DHCPREQUEST (broadcast)

DHCPOFFER (unicast)

DHCPDISCOVER (broadcast)

DHCP server

51807

3-5

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 3 Assigning the Switch IP Address and Default Gateway

Assigning Switch Information

Configuring DHCP-Based Autoconfiguration

These sections contain this configuration information:

• DHCP Server Configuration Guidelines, page 3-5

• Configuring the TFTP Server, page 3-6

• Configuring the DNS, page 3-6

• Configuring the Relay Device, page 3-6

• Obtaining Configuration Files, page 3-7

• Example Configuration, page 3-8

If your DHCP server is a Cisco device, for additional information about configuring DHCP, see the
“Configuring DHCP” section of the “IP Addressing and Services” section of the Cisco IOS IP

Configuration Guide from the Cisco.com page under Documentation > Cisco IOS Software > 12.2
Mainline > Configuration Guides.

DHCP Server Configuration Guidelines

Follow these guidelines if you are configuring a device as a DHCP server:

You should configure the DHCP server with reserved leases that are bound to each switch by the switch
hardware address.

If you want the switch to receive IP address information, you must configure the DHCP server with these
lease options:

• IP address of the client (required)

• Subnet mask of the client (required)

• DNS server IP address (optional)

• Router IP address (default gateway address to be used by the switch) (required)

If you want the switch to receive the configuration file from a TFTP server, you must configure the
DHCP server with these lease options:

• TFTP server name (required)

• Boot filename (the name of the configuration file that the client needs) (recommended)

• Hostname (optional)

Depending on the settings of the DHCP server, the switch can receive IP address information, the
configuration file, or both.

If you do not configure the DHCP server with the lease options described previously, it replies to client
requests with only those parameters that are configured. If the IP address and the subnet mask are not in
the reply, the switch is not configured. If the router IP address or the TFTP server name are not found,
the switch might send broadcast, instead of unicast, TFTP requests. Unavailability of other lease options
does not affect autoconfiguration.

3-6

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 3 Assigning the Switch IP Address and Default Gateway

Assigning Switch Information

Configuring the TFTP Server

Based on the DHCP server configuration, the switch attempts to download one or more configuration
files from the TFTP server. If you configured the DHCP server to respond to the switch with all the
options required for IP connectivity to the TFTP server, and if you configured the DHCP server with a
TFTP server name, address, and configuration filename, the switch attempts to download the specified
configuration file from the specified TFTP server.

If you did not specify the configuration filename, the TFTP server, or if the configuration file could not
be downloaded, the switch attempts to download a configuration file by using various combinations of
filenames and TFTP server addresses. The files include the specified configuration filename (if any) and
these files: network-config, cisconet.cfg, hostname.config, or hostname.cfg, where hostname is the
switch’s current hostname. The TFTP server addresses used include the specified TFTP server address
(if any) and the broadcast address (255.255.255.255).

For the switch to successfully download a configuration file, the TFTP server must contain one or more
configuration files in its base directory. The files can include these files:

• The configuration file named in the DHCP reply (the actual switch configuration file).

• The network-confg or the cisconet.cfg file (known as the default configuration files).

• The router-confg or the ciscortr.cfg file (These files contain commands common to all switches.

Normally, if the DHCP and TFTP servers are properly configured, these files are not accessed.)

If you specify the TFTP server name in the DHCP server-lease database, you must also configure the
TFTP server name-to-IP-address mapping in the DNS-server database.

If the TFTP server to be used is on a different LAN from the switch, or if it is to be accessed by the
switch through the broadcast address (which occurs if the DHCP server response does not contain all the
required information described previously), a relay must be configured to forward the TFTP packets to
the TFTP server. For more information, see the “Configuring the Relay Device” section on page 3-6.
The preferred solution is to configure the DHCP server with all the required information.

Configuring the DNS

The DHCP server uses the DNS server to resolve the TFTP server name to an IP address. You must
configure the TFTP server name-to-IP address map on the DNS server. The TFTP server contains the
configuration files for the switch.

You can configure the IP addresses of the DNS servers in the lease database of the DHCP server from
where the DHCP replies will retrieve them. You can enter up to two DNS server IP addresses in the lease
database.

The DNS server can be on the same or on a different LAN as the switch. If it is on a different LAN, the
switch must be able to access it through a router.

Configuring the Relay Device

You must configure a relay device, also referred to as a relay agent, when a switch sends broadcast
packets that require a response from a host on a different LAN. Examples of broadcast packets that the
switch might send are DHCP, DNS, and in some cases, TFTP packets. You must configure this relay
device to forward received broadcast packets on an interface to the destination host.

If the relay device is a Cisco router, enable IP routing (ip routing global configuration command), and
configure helper addresses by using the ip helper-address interface configuration command.

3-7

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 3 Assigning the Switch IP Address and Default Gateway

Assigning Switch Information

For example, in Figure 3-2, configure the router interfaces as follows:

On interface 10.0.0.2:

router(config-if)# ip helper-address 20.0.0.2
router(config-if)# ip helper-address 20.0.0.3
router(config-if)# ip helper-address 20.0.0.4

On interface 20.0.0.1

router(config-if)# ip helper-address 10.0.0.1

Figure 3-2 Relay Device Used in Autoconfiguration

Obtaining Configuration Files

Depending on the availability of the IP address and the configuration filename in the DHCP reserved
lease, the switch obtains its configuration information in these ways:

• The IP address and the configuration filename is reserved for the switch and provided in the DHCP

reply (one-file read method).

The switch receives its IP address, subnet mask, TFTP server address, and the configuration
filename from the DHCP server. The switch sends a unicast message to the TFTP server to retrieve
the named configuration file from the base directory of the server and upon receipt, it completes its
boot-up process.

• The IP address and the configuration filename is reserved for the switch, but the TFTP server

address is not provided in the DHCP reply (one-file read method).

The switch receives its IP address, subnet mask, and the configuration filename from the DHCP
server. The switch sends a broadcast message to a TFTP server to retrieve the named configuration
file from the base directory of the server, and upon receipt, it completes its boot-up process.

• Only the IP address is reserved for the switch and provided in the DHCP reply. The configuration

filename is not provided (two-file read method).

The switch receives its IP address, subnet mask, and the TFTP server address from the DHCP server.
The switch sends a unicast message to the TFTP server to retrieve the network-confg or cisconet.cfg
default configuration file. (If the network-confg file cannot be read, the switch reads the cisconet.cfg
file.)

Switch

(DHCP client)

Cisco router

(Relay)

49068

DHCP server TFTP server DNS server

20.0.0.2 20.0.0.3

20.0.0.1

10.0.0.2

10.0.0.1

20.0.0.4

3-8

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 3 Assigning the Switch IP Address and Default Gateway

Assigning Switch Information

The default configuration file contains the hostnames-to-IP-address mapping for the switch. The
switch fills its host table with the information in the file and obtains its hostname. If the hostname
is not found in the file, the switch uses the hostname in the DHCP reply. If the hostname is not
specified in the DHCP reply, the switch uses the default Switch as its hostname.

After obtaining its hostname from the default configuration file or the DHCP reply, the switch reads
the configuration file that has the same name as its hostname (hostname-confg or hostname.cfg,
depending on whether network-confg or cisconet.cfg was read earlier) from the TFTP server. If the
cisconet.cfg file is read, the filename of the host is truncated to eight characters.

If the switch cannot read the network-confg, cisconet.cfg, or the hostname file, it reads the
router-confg file. If the switch cannot read the router-confg file, it reads the ciscortr.cfg file.

Note The switch broadcasts TFTP server requests if the TFTP server is not obtained from the DHCP replies,

if all attempts to read the configuration file through unicast transmissions fail, or if the TFTP server
name cannot be resolved to an IP address.

Example Configuration

Figure 3-3 shows a sample network for retrieving IP information by using DHCP-based autoconfiguration.

Figure 3-3 DHCP-Based Autoconfiguration Network Example

Table 3-2 shows the configuration of the reserved leases on the DHCP server.

Switch 1

00e0.9f1e.2001

Cisco router

111394

Switch 2

00e0.9f1e.2002

Switch 3

00e0.9f1e.2003

DHCP server DNS server TFTP server

(tftpserver)

10.0.0.1

10.0.0.10

10.0.0.2 10.0.0.3

Switch 4

00e0.9f1e.2004

Table 3-2 DHCP Server Configuration

Switch A Switch B Switch C Switch D

Binding key (hardware address) 00e0.9f1e.2001 00e0.9f1e.2002 00e0.9f1e.2003 00e0.9f1e.2004

IP address 10.0.0.21 10.0.0.22 10.0.0.23 10.0.0.24

Subnet mask 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0

Router address 10.0.0.10 10.0.0.10 10.0.0.10 10.0.0.10

DNS server address 10.0.0.2 10.0.0.2 10.0.0.2 10.0.0.2

TFTP server name tftpserver or

10.0.0.3

tftpserver or

10.0.0.3

tftpserver or

10.0.0.3

tftpserver or

10.0.0.3

3-9

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 3 Assigning the Switch IP Address and Default Gateway

Assigning Switch Information

DNS Server Configuration

The DNS server maps the TFTP server name tftpserver to IP address 10.0.0.3.

TFTP Server Configuration (on UNIX)

The TFTP server base directory is set to /tftpserver/work/. This directory contains the network-confg file
used in the two-file read method. This file contains the hostname to be assigned to the switch based on
its IP address. The base directory also contains a configuration file for each switch (switcha-confg,
switchb-confg, and so forth) as shown in this display:

prompt> cd /tftpserver/work/
prompt> ls
network-confg
switcha-confg
switchb-confg
switchc-confg
switchd-confg
prompt> cat network-confg
ip host switcha 10.0.0.21
ip host switchb 10.0.0.22
ip host switchc 10.0.0.23
ip host switchd 10.0.0.24

DHCP Client Configuration

No configuration file is present on Switch A through Switch D.

Configuration Explanation

In Figure 3-3, Switch A reads its configuration file as follows:

• It obtains its IP address 10.0.0.21 from the DHCP server.

• If no configuration filename is given in the DHCP server reply, Switch A reads the network-confg

file from the base directory of the TFTP server.

• It adds the contents of the network-confg file to its host table.

• It reads its host table by indexing its IP address 10.0.0.21 to its hostname (switcha).

• It reads the configuration file that corresponds to its hostname; for example, it reads switch1-confg

from the TFTP server.

Switches B through D retrieve their configuration files and IP addresses in the same way.

Boot filename (configuration file)
(optional)

switcha-confg switchb-confg switchc-confg switchd-confg

Hostname (optional) switcha switchb switchc switchd

Table 3-2 DHCP Server Configuration (continued)

Switch A Switch B Switch C Switch D

3-10

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 3 Assigning the Switch IP Address and Default Gateway

Checking and Saving the Running Configuration

Manually Assigning IP Information

Beginning in privileged EXEC mode, follow these steps to manually assign IP information to multiple
switched virtual interfaces (SVIs):

To remove the switch IP address, use the no ip address interface configuration command. If you are
removing the address through a Telnet session, your connection to the switch will be lost. To remove the
default gateway address, use the no ip default-gateway global configuration command.

For information on setting the switch system name, protecting access to privileged EXEC commands,
and setting time and calendar services, see Chapter 6, “Administering the Switch.”

Checking and Saving the Running Configuration

You can check the configuration settings that you entered or changes that you made by entering this
privileged EXEC command:

Switch# show running-config
Building configuration...

Current configuration: 1363 bytes
!
version 12.1
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname Switch A
!

Command Purpose

Step 1

configure terminal Enter global configuration mode.

Step 2

interface vlan vlan-id Enter interface configuration mode, and enter the VLAN to which the IP

information is assigned. The VLAN range is 1 to 4094.

Step 3

ip address ip-address subnet-mask Enter the IP address and subnet mask.

Step 4

exit Return to global configuration mode.

Step 5

ip default-gateway ip-address Enter the IP address of the next-hop router interface that is directly

connected to the switch where a default gateway is being configured. The
default gateway receives IP packets with unresolved destination IP
addresses from the switch.

Once the default gateway is configured, the switch has connectivity to the
remote networks with which a host needs to communicate.

Note When your switch is configured to route with IP, it does not need

to have a default gateway set.

Step 6

end Return to privileged EXEC mode.

Step 7

show interfaces vlan vlan-id Verify the configured IP address.

Step 8

show ip redirects Verify the configured default gateway.

Step 9

copy running-config startup-config (Optional) Save your entries in the configuration file.

3-11

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 3 Assigning the Switch IP Address and Default Gateway

Modifying the Startup Configuration

enable secret 5 $1$ej9.$DMUvAUnZOAmvmgqBEzIxE0
!
.
<output truncated>
.
interface gigabitethernet0/1
ip address 172.20.137.50 255.255.255.0
!
interface gigabitethernet0/2
mvr type source

<output truncated>

...!
interface VLAN1
ip address 172.20.137.50 255.255.255.0
no ip directed-broadcast
!
ip default-gateway 172.20.137.1 !
!
snmp-server community private RW
snmp-server community public RO
snmp-server community private@es0 RW
snmp-server community public@es0 RO
snmp-server chassis-id 0x12
!
end

To store the configuration or changes you have made to your startup configuration in flash memory, enter
this privileged EXEC command:

Switch# copy running-config startup-config
Destination filename [startup-config]?
Building configuration...

This command saves the configuration settings that you made. If you fail to do this, your configuration
will be lost the next time you reload the system. To display information stored in the NVRAM section
of flash memory, use the show startup-config or more startup-config privileged EXEC command.

For more information about alternative locations from which to copy the configuration file, see

Appendix B, “Working with the Cisco IOS File System, Configuration Files, and Software Images.”

Modifying the Startup Configuration

These sections describe how to modify the switch startup configuration:

• Default Boot Configuration, page 3-12

• Automatically Downloading a Configuration File, page 3-12

• Booting Manually, page 3-13

• Booting a Specific Software Image, page 3-14

• Controlling Environment Variables, page 3-14

See also Appendix B, “Working with the Cisco IOS File System, Configuration Files, and Software

Images,” for information about switch configuration files.

3-12

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 3 Assigning the Switch IP Address and Default Gateway

Modifying the Startup Configuration

Default Boot Configuration

Table 3-3 shows the default boot-up configuration.

Automatically Downloading a Configuration File

You can automatically download a configuration file to your switch by using the DHCP-based
autoconfiguration feature. For more information, see the “Understanding DHCP-Based

Autoconfiguration” section on page 3-3.

Specifying the Filename to Read and Write the System Configuration

By default, the Cisco IOS software uses the file config.text to read and write a nonvolatile copy of the
system configuration. However, you can specify a different filename, which will be loaded during the
next boot-up cycle.

Beginning in privileged EXEC mode, follow these steps to specify a different configuration filename:

Table 3-3 Default Boot Configuration

Feature Default Setting

Operating system software image The switch attempts to automatically boot up the system using information in the

BOOT environment variable. If the variable is not set, the switch attempts to load and
execute the first executable image it can by performing a recursive, depth-first search
throughout the flash file system.

The Cisco IOS image is stored in a directory that has the same name as the image file
(excluding the .bin extension).

In a depth-first search of a directory, each encountered subdirectory is completely
searched before continuing the search in the original directory.

Configuration file Configured switches use the config.text file stored on the system board in flash

memory.

A new switch has no configuration file.

Command Purpose

Step 1

configure terminal Enter global configuration mode.

Step 2

boot config-file flash:/file-url Specify the configuration file to load during the next boot-up

cycle.

For file-url, specify the path (directory) and the configuration
filename.

Filenames and directory names are case sensitive.

Step 3

end Return to privileged EXEC mode.

Step 4

show boot Verify your entries.

The boot config-file global configuration command changes the
setting of the CONFIG_FILE environment variable.

Step 5

copy running-config startup-config (Optional) Save your entries in the configuration file.

3-13

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 3 Assigning the Switch IP Address and Default Gateway

Modifying the Startup Configuration

To return to the default setting, use the no boot config-file global configuration command.

Booting Manually

By default, the switch automatically boots up; however, you can configure it to manually boot up.

Beginning in privileged EXEC mode, follow these steps to configure the switch to manually boot up
during the next boot cycle:

To disable manual booting, use the no boot manual global configuration command.

Command Purpose

Step 1

configure terminal Enter global configuration mode.

Step 2

boot manual Enable the switch to manually boot up during the next boot cycle.

Step 3

end Return to privileged EXEC mode.

Step 4

show boot Verify your entries.

The boot manual global command changes the setting of the
MANUAL_BOOT environment variable.

The next time you reboot the system, the switch is in boot loader
mode, shown by the switch: prompt. To boot up the system, use the
boot filesystem:/file-url boot loader command.

• For filesystem:, use flash: for the system board flash device.

• For file-url, specify the path (directory) and the name of the

bootable image.

Filenames and directory names are case sensitive.

Step 5

copy running-config startup-config (Optional) Save your entries in the configuration file.

3-14

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 3 Assigning the Switch IP Address and Default Gateway

Modifying the Startup Configuration

Booting a Specific Software Image

By default, the switch attempts to automatically boot up the system using information in the BOOT
environment variable. If this variable is not set, the switch attempts to load and execute the first
executable image it can by performing a recursive, depth-first search throughout the flash file system.
In a depth-first search of a directory, each encountered subdirectory is completely searched before
continuing the search in the original directory. However, you can specify a specific image to boot up.

Beginning in privileged EXEC mode, follow these steps to configure the switch to boot a specific image
during the next boot cycle:

To return to the default setting, use the no boot system global configuration command.

Controlling Environment Variables

With a normally operating switch, you enter the boot loader mode only through a switch console
connection configured for 9600 b/s. Unplug the switch power cord, and press the switch Mode button
while reconnecting the power cord. You can release the Mode button a second or two after the LED
above port 1 turns off. Then the boot loader switch: prompt appears.

The switch boot loader software provides support for nonvolatile environment variables, which can be
used to control how the boot loader, or any other software running on the system, behaves. Boot loader
environment variables are similar to environment variables that can be set on UNIX or DOS systems.

Environment variables that have values are stored in flash memory outside of the flash file system.

Each line in these files contains an environment variable name and an equal sign followed by the value
of the variable. A variable has no value if it is not listed in this file; it has a value if it is listed in the file
even if the value is a null string. A variable that is set to a null string (for example, “ ”) is a variable with
a value. Many environment variables are predefined and have default values.

Command Purpose

Step 1

configure terminal Enter global configuration mode.

Step 2

boot system filesystem:/file-url Configure the switch to boot a specific image in flash memory during the

next boot cycle.

• For filesystem:, use flash: for the system board flash device.

• For file-url, specify the path (directory) and the name of the bootable

image.

Filenames and directory names are case sensitive.

Step 3

end Return to privileged EXEC mode.

Step 4

show boot Verify your entries.

The boot system global command changes the setting of the BOOT
environment variable.

During the next boot cycle, the switch attempts to automatically boot up the
system using information in the BOOT environment variable.

Step 5

copy running-config startup-config (Optional) Save your entries in the configuration file.

3-15

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 3 Assigning the Switch IP Address and Default Gateway

Modifying the Startup Configuration

Environment variables store two kinds of data:

• Data that controls code, which does not read the Cisco IOS configuration file. For example, the name

of a boot loader helper file, which extends or patches the functionality of the boot loader can be
stored as an environment variable.

• Data that controls code, which is responsible for reading the Cisco IOS configuration file. For

example, the name of the Cisco IOS configuration file can be stored as an environment variable.

You can change the settings of the environment variables by accessing the boot loader or by using Cisco
IOS commands. Under normal circumstances, it is not necessary to alter the setting of the environment
variables.

Note For complete syntax and usage information for the boot loader commands and environment variables,

see the command reference for this release.

Table 3-4 describes the function of the most common environment variables.

Table 3-4 Environment Variables

Variable Boot Loader Command Cisco IOS Global Configuration Command

BOOT set BOOT filesystem:/file-url ...

A semicolon-separated list of executable files to
try to load and execute when automatically
booting. If the BOOT environment variable is not
set, the system attempts to load and execute the
first executable image it can find by using a
recursive, depth-first search through the flash file
system. If the BOOT variable is set but the
specified images cannot be loaded, the system
attempts to boot the first bootable file that it can
find in the flash file system.

boot system filesystem:/file-url ...

Specifies the Cisco IOS image to load during the
next boot cycle. This command changes the
setting of the BOOT environment variable.

MANUAL_BOOT set MANUAL_BOOT yes

Decides whether the switch automatically or
manually boots up.

Valid values are 1, yes, 0, and no. If it is set to no
or 0, the boot loader attempts to automatically
boot up the system. If it is set to anything else,
you must manually boot up the switch from the
boot loader mode.

boot manual

Enables manually booting up the switch during
the next boot cycle and changes the setting of the
MANUAL_BOOT environment variable.

The next time you reboot the system, the switch is
in boot loader mode. To boot up the system, use
the boot flash:filesystem:/file-url boot loader
command, and specify the name of the bootable
image.

CONFIG_FILE set CONFIG_FILE flash:/file-url

Changes the filename that Cisco IOS uses to read
and write a nonvolatile copy of the system
configuration.

boot config-file flash:/file-url

Specifies the filename that Cisco IOS uses to read
and write a nonvolatile copy of the system
configuration. This command changes the
CONFIG_FILE environment variable.

3-16

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 3 Assigning the Switch IP Address and Default Gateway

Scheduling a Reload of the Software Image

Scheduling a Reload of the Software Image

You can schedule a reload of the software image to occur on the switch at a later time (for example, late
at night or during the weekend when the switch is used less), or you can synchronize a reload
network-wide (for example, to perform a software upgrade on all switches in the network).

Note A scheduled reload must take place within approximately 24 days.

Configuring a Scheduled Reload

To configure your switch to reload the software image at a later time, use one of these commands in
privileged EXEC mode:

• reload in [hh:]mm [text]

This command schedules a reload of the software to take affect in the specified minutes or hours and
minutes. The reload must take place within approximately 24 days. You can specify the reason for
the reload in a string up to 255 characters in length.

• reload at hh:mm [month day | day month] [text]

This command schedules a reload of the software to take place at the specified time (using a 24-hour
clock). If you specify the month and day, the reload is scheduled to take place at the specified time
and date. If you do not specify the month and day, the reload takes place at the specified time on the
current day (if the specified time is later than the current time) or on the next day (if the specified
time is earlier than the current time). Specifying 00:00 schedules the reload for midnight.

Note Use the at keyword only if the switch system clock has been set (through Network Time

Protocol (NTP), the hardware calendar, or manually). The time is relative to the configured
time zone on the switch. To schedule reloads across several switches to occur
simultaneously, the time on each switch must be synchronized with NTP.

The reload command halts the system. If the system is not set to manually boot up, it reboots itself. Use
the reload command after you save the switch configuration information to the startup configuration
(copy running-config startup-config).

If your switch is configured for manual booting, do not reload it from a virtual terminal. This restriction
prevents the switch from entering the boot loader mode and thereby taking it from the remote user’s
control.

If you modify your configuration file, the switch prompts you to save the configuration before reloading.
During the save operation, the system requests whether you want to proceed with the save if the
CONFIG_FILE environment variable points to a startup configuration file that no longer exists. If you
proceed in this situation, the system enters setup mode upon reload.

This example shows how to reload the software on the switch on the current day at 7:30 p.m:

Switch# reload at 19:30
Reload scheduled for 19:30:00 UTC Wed Jun 5 1996 (in 2 hours and 25 minutes)
Proceed with reload? [confirm]

3-17

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 3 Assigning the Switch IP Address and Default Gateway

Scheduling a Reload of the Software Image

This example shows how to reload the software on the switch at a future time:

Switch# reload at 02:00 jun 20
Reload scheduled for 02:00:00 UTC Thu Jun 20 1996 (in 344 hours and 53 minutes)
Proceed with reload? [confirm]

To cancel a previously scheduled reload, use the reload cancel privileged EXEC command.

Displaying Scheduled Reload Information

To display information about a previously scheduled reload or to find out if a reload has been scheduled
on the switch, use the show reload privileged EXEC command.

It displays reload information including the time the reload is scheduled to occur and the reason for the
reload (if it was specified when the reload was scheduled).

3-18

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 3 Assigning the Switch IP Address and Default Gateway

Scheduling a Reload of the Software Image

CHA PTER

4-1

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

4

Configuring Cisco IOS CNS Agents

This chapter describes how to configure the Cisco IOS CNS agents on the Catalyst 2960 switch.

Note For complete configuration information for the Cisco Configuration Engine, see this URL on Cisco.com

http://www.cisco.com/en/US/products/sw/netmgtsw/ps4617/tsd_products_support_series_home.html

This chapter consists of these sections:

• Understanding Cisco Configuration Engine Software, page 4-1

• Understanding Cisco IOS Agents, page 4-5

• Configuring Cisco IOS Agents, page 4-6

• Displaying CNS Configuration, page 4-12

Understanding Cisco Configuration Engine Software

The Cisco Configuration Engine is network management software that acts as a configuration service
for automating the deployment and management of network devices and services (see Figure 4-1). Each
Configuration Engine manages a group of Cisco devices (switches and routers) and the services that they
deliver, storing their configurations and delivering them as needed. The Configuration Engine automates
initial configurations and configuration updates by generating device-specific configuration changes,
sending them to the device, executing the configuration change, and logging the results.

The Configuration Engine supports standalone and server modes and has these CNS components:

• Configuration service (web server, file manager, and namespace mapping server)

• Event service (event gateway)

• Data service directory (data models and schema)

In standalone mode, the Configuration Engine supports an embedded Directory Service. In this mode,
no external directory or other data store is required. In server mode, the Configuration Engine supports
the use of a user-defined external directory.

4-2

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 4 Configuring Cisco IOS CNS Agents

Understanding Cisco Configuration Engine Software

Figure 4-1 Configuration Engine Architectural Overview

These sections contain this conceptual information:

• Configuration Service, page 4-2

• Event Service, page 4-3

• What You Should Know About the CNS IDs and Device Hostnames, page 4-3

Configuration Service

The Configuration Service is the core component of the Cisco Configuration Engine. It consists of a
configuration server that works with Cisco IOS CNS agents on the switch. The Configuration Service
delivers device and service configurations to the switch for initial configuration and mass
reconfiguration by logical groups. Switches receive their initial configuration from the Configuration
Service when they start up on the network for the first time.

The Configuration Service uses the CNS Event Service to send and receive configuration change events
and to send success and failure notifications.

The configuration server is a web server that uses configuration templates and the device-specific
configuration information stored in the embedded (standalone mode) or remote (server mode) directory.

Configuration templates are text files containing static configuration information in the form of CLI
commands. In the templates, variables are specified using lightweight directory access protocol (LDAP)
URLs that reference the device-specific configuration information stored in a directory.

The Cisco IOS agent can perform a syntax check on received configuration files and publish events to
show the success or failure of the syntax check. The configuration agent can either apply configurations
immediately or delay the application until receipt of a synchronization event from the configuration
server.

Configuration

engine

Service provider network

Order entry

configuration management

Data service
directory

Configuration server

Event service

Web-based
user interface

141327

4-3

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 4 Configuring Cisco IOS CNS Agents

Understanding Cisco Configuration Engine Software

Event Service

The Cisco Configuration Engine uses the Event Service for receipt and generation of configuration
events. The event agent is on the switch and facilitates the communication between the switch and the
event gateway on the Configuration Engine.

The Event Service is a highly capable publish-and-subscribe communication method. The Event Service
uses subject-based addressing to send messages to their destinations. Subject-based addressing
conventions define a simple, uniform namespace for messages and their destinations.

NameSpace Mapper

The Configuration Engine includes the NameSpace Mapper (NSM) that provides a lookup service for
managing logical groups of devices based on application, device or group ID, and event.

Cisco IOS devices recognize only event subject-names that match those configured in Cisco IOS
software; for example, cisco.cns.config.load. You can use the namespace mapping service to designate
events by using any desired naming convention. When you have populated your data store with your
subject names, NSM changes your event subject-name strings to those known by Cisco IOS.

For a subscriber, when given a unique device ID and event, the namespace mapping service returns a set
of events to which to subscribe. Similarly, for a publisher, when given a unique group ID, device ID, and
event, the mapping service returns a set of events on which to publish.

What You Should Know About the CNS IDs and Device Hostnames

The Cisco Configuration Engine assumes that a unique identifier is associated with each configured
switch. This unique identifier can take on multiple synonyms, where each synonym is unique within a
particular namespace. The event service uses namespace content for subject-based addressing of
messages.

The Configuration Engine intersects two namespaces, one for the event bus and the other for the
configuration server. Within the scope of the configuration server namespace, the term ConfigID is the
unique identifier for a device. Within the scope of the event bus namespace, the term DeviceID is the
CNS unique identifier for a device.

Because the Configuration Engine uses both the event bus and the configuration server to provide
configurations to devices, you must define both ConfigID and Device ID for each configured switch.

Within the scope of a single instance of the configuration server, no two configured switches can share
the same value for ConfigID. Within the scope of a single instance of the event bus, no two configured
switches can share the same value for DeviceID.

ConfigID

Each configured switch has a unique ConfigID, which serves as the key into the Configuration Engine
directory for the corresponding set of switch CLI attributes. The ConfigID defined on the switch must
match the ConfigID for the corresponding switch definition on the Configuration Engine.

The ConfigID is fixed at startup time and cannot be changed until the device restarts, even if the switch
hostname is reconfigured.

4-4

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 4 Configuring Cisco IOS CNS Agents

Understanding Cisco Configuration Engine Software

DeviceID

Each configured switch participating on the event bus has a unique DeviceID, which is analogous to the
switch source address so that the switch can be targeted as a specific destination on the bus. All switches
configured with the cns config partial global configuration command must access the event bus.
Therefore, the DeviceID, as originated on the switch, must match the DeviceID of the corresponding
switch definition in the Configuration Engine.

The origin of the DeviceID is defined by the Cisco IOS hostname of the switch. However, the DeviceID
variable and its usage reside within the event gateway adjacent to the switch.

The logical Cisco IOS termination point on the event bus is embedded in the event gateway, which in
turn functions as a proxy on behalf of the switch. The event gateway represents the switch and its
corresponding DeviceID to the event bus.

The switch declares its hostname to the event gateway immediately after the successful connection to
the event gateway. The event gateway couples the DeviceID value to the Cisco IOS hostname each time
this connection is established. The event gateway caches this DeviceID value for the duration of its
connection to the switch.

Hostname and DeviceID

The DeviceID is fixed at the time of the connection to the event gateway and does not change even when
the switch hostname is reconfigured.

When changing the switch hostname on the switch, the only way to refresh the DeviceID is to break the
connection between the switch and the event gateway. Enter the no cns event global configuration
command followed by the cns event global configuration command.

When the connection is re-established, the switch sends its modified hostname to the event gateway. The
event gateway redefines the DeviceID to the new value.

Caution When using the Configuration Engine user interface, you must first set the DeviceID field to the

hostname value that the switch acquires after–not before–you use the cns config initial global
configuration command at the switch. Otherwise, subsequent cns config partial global configuration
command operations malfunction.

Using Hostname, DeviceID, and ConfigID

In standalone mode, when a hostname value is set for a switch, the configuration server uses the
hostname as the DeviceID when an event is sent on hostname. If the hostname has not been set, the event
is sent on the cn=<value> of the device.

In server mode, the hostname is not used. In this mode, the unique DeviceID attribute is always used for
sending an event on the bus. If this attribute is not set, you cannot update the switch.

These and other associated attributes (tag value pairs) are set when you run Setup on the Configuration
Engine.

Note For more information about running the setup program on the Configuration Engine, see the

Configuration Engine setup and configuration guide at this URL on cisco.com:

http://www.cisco.com/en/US/products/sw/netmgtsw/ps4617/products_installation_and_configuration_
guide_book09186a00803b59db.html

4-5

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 4 Configuring Cisco IOS CNS Agents

Understanding Cisco IOS Agents

Understanding Cisco IOS Agents

The CNS event agent feature allows the switch to publish and subscribe to events on the event bus and
works with the Cisco IOS agent. The Cisco IOS agent feature supports the switch by providing these
features:

• Initial Configuration, page 4-5

• Incremental (Partial) Configuration, page 4-6

• Synchronized Configuration, page 4-6

Initial Configuration

When the switch first comes up, it attempts to get an IP address by broadcasting a DHCP request on the
network. Assuming there is no DHCP server on the subnet, the distribution switch acts as a DHCP relay
agent and forwards the request to the DHCP server. Upon receiving the request, the DHCP server assigns
an IP address to the new switch and includes the TFTP server IP address, the path to the bootstrap
configuration file, and the default gateway IP address in a unicast reply to the DHCP relay agent. The
DHCP relay agent forwards the reply to the switch.

The switch automatically configures the assigned IP address on interface VLAN 1 (the default) and
downloads the bootstrap configuration file from the TFTP server. Upon successful download of the
bootstrap configuration file, the switch loads the file in its running configuration.

The Cisco IOS agents initiate communication with the Configuration Engine by using the appropriate
ConfigID and EventID. The Configuration Engine maps the Config ID to a template and downloads the
full configuration file to the switch.

Figure 4-2 shows a sample network configuration for retrieving the initial bootstrap configuration file

by using DHCP-based autoconfiguration.

Figure 4-2 Initial Configuration Overview

TFTP
server

DHCP relay agent
default gatewayDistribution layer

Configuration

Engine

Access layer

switches

141328

DHCP
server

V

WAN

4-6

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 4 Configuring Cisco IOS CNS Agents

Configuring Cisco IOS Agents

Incremental (Partial) Configuration

After the network is running, new services can be added by using the Cisco IOS agent. Incremental
(partial) configurations can be sent to the switch. The actual configuration can be sent as an event
payload by way of the event gateway (push operation) or as a signal event that triggers the switch to
initiate a pull operation.

The switch can check the syntax of the configuration before applying it. If the syntax is correct, the
switch applies the incremental configuration and publishes an event that signals success to the
configuration server. If the switch does not apply the incremental configuration, it publishes an event
showing an error status. When the switch has applied the incremental configuration, it can write it to
NVRAM or wait until signaled to do so.

Synchronized Configuration

When the switch receives a configuration, it can defer application of the configuration upon receipt of a
write-signal event. The write-signal event tells the switch not to save the updated configuration into its
NVRAM. The switch uses the updated configuration as its running configuration. This ensures that the
switch configuration is synchronized with other network activities before saving the configuration in
NVRAM for use at the next reboot.

Configuring Cisco IOS Agents

The Cisco IOS agents embedded in the switch Cisco IOS software allow the switch to be connected and
automatically configured as described in the “Enabling Automated CNS Configuration” section on

page 4-6. If you want to change the configuration or install a custom configuration, see these sections

for instructions:

• Enabling the CNS Event Agent, page 4-8

• Enabling the Cisco IOS CNS Agent, page 4-9

Enabling Automated CNS Configuration

To enable automated CNS configuration of the switch, you must first complete the prerequisites in

Table 4-1. When you complete them, power on the switch. At the setup prompt, do nothing: The switch

begins the initial configuration as described in the “Initial Configuration” section on page 4-5. When the
full configuration file is loaded on your switch, you need to do nothing else.

4-7

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 4 Configuring Cisco IOS CNS Agents

Configuring Cisco IOS Agents

Note For more information about running the setup program and creating templates on the Configuration

Engine, see the Cisco Configuration Engine Installation and Setup Guide, 1.5 for Linux at this URL:

http://www.cisco.com/en/US/products/sw/netmgtsw/ps4617/products_installation_and_configuration_
guide_book09186a00803b59db.html

Table 4-1 Prerequisites for Enabling Automatic Configuration

Device Required Configuration

Access switch Factory default (no configuration file)

Distribution switch

• IP helper address

• Enable DHCP relay agent

• IP routing (if used as default gateway)

DHCP server • IP address assignment

• TFTP server IP address

• Path to bootstrap configuration file on the TFTP server

• Default gateway IP address

TFTP server

• A bootstrap configuration file that includes the CNS

configuration commands that enable the switch to
communicate with the Configuration Engine

• The switch configured to use either the switch MAC address

or the serial number (instead of the default hostname) to
generate the ConfigID and EventID

• The CNS event agent configured to push the configuration file

to the switch

CNS Configuration Engine One or more templates for each type of device, with the ConfigID

of the device mapped to the template.

4-8

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 4 Configuring Cisco IOS CNS Agents

Configuring Cisco IOS Agents

Enabling the CNS Event Agent

Note You must enable the CNS event agent on the switch before you enable the CNS configuration agent.

Beginning in privileged EXEC mode, follow these steps to enable the CNS event agent on the switch:

To disable the CNS event agent, use the no cns event {ip-address | hostname} global configuration
command.

This example shows how to enable the CNS event agent, set the IP address gateway to 10.180.1.27, set
120 seconds as the keepalive interval, and set 10 as the retry count.

Switch(config)# cns event 10.180.1.27 keepalive 120 10

Command Purpose

Step 1

configure terminal Enter global configuration mode.

Step 2

cns event {ip-address | hostname} [port-number]
[backup] [init-retry retry-count] [keepalive seconds
retry-count] [source ip-address]

Enable the event agent, and enter the gateway parameters.

• For {ip-address | hostname}, enter either the

IP address or the hostname of the event gateway.

• (Optional) For port number, enter the port number for

the event gateway. The default port number is 11011.

• (Optional) Enter backup to show that this is the

backup gateway. (If omitted, this is the primary
gateway.)

• (Optional) For init-retry retry-count, enter the

number of initial retries before switching to backup.
The default is 3.

• (Optional) For keepalive seconds, enter how often the

switch sends keepalive messages. For retry-count,
enter the number of unanswered keepalive messages
that the switch sends before the connection is
terminated. The default for each is 0.

• (Optional) For source ip-address, enter the source IP

address of this device.

Note Though visible in the command-line help string,

the encrypt and force-fmt1 keywords are not
supported.

Step 3

end Return to privileged EXEC mode.

Step 4

show cns event connections Verify information about the event agent.

Step 5

show running-config Verify your entries.

Step 6

copy running-config startup-config (Optional) Save your entries in the configuration file.

4-9

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 4 Configuring Cisco IOS CNS Agents

Configuring Cisco IOS Agents

Enabling the Cisco IOS CNS Agent

After enabling the CNS event agent, start the Cisco IOS CNS agent on the switch. You can enable the
Cisco IOS agent with these commands:

• The cns config initial global configuration command enables the Cisco IOS agent and initiates an

initial configuration on the switch.

• The cns config partial global configuration command enables the Cisco IOS agent and initiates a

partial configuration on the switch. You can then use the Configuration Engine to remotely send
incremental configurations to the switch.

Enabling an Initial Configuration

Beginning in privileged EXEC mode, follow these steps to enable the CNS configuration agent and
initiate an initial configuration on the switch:

Command Purpose

Step 1

configure terminal Enter global configuration mode.

Step 2

cns config connect-intf interface-prefix
[ping-interval seconds] [retries num]

Enter the connect-interface-config submode, and specify
the interface for connecting to the Configuration Engine.

• Enter the interface-prefix for the connecting interface.

You must specify the interface type but need not
specify the interface number.

• (Optional) For ping-interval seconds, enter the

interval between successive ping attempts. The range
is 1 to 30 seconds. The default is 10 seconds.

• (Optional) For retries num, enter the number of ping

retries. The range is 1 to 30. The default is 5.

Step 3

config-cli

or

line-cli

Enter config-cli to connect to the Configuration Engine
through the interface defined in cns config connect-intf.
Enter line-cli to connect to the Configuration Engine
through modem dialup lines.

Note The config-cli interface configuration command

accepts the special character & that acts as a
placeholder for the interface name. When the
configuration is applied, the & is replaced with the
interface name. For example, to connect through
FastEthernet0/1, the command

config-cli ip

route 0.0.0.0 0.0.0.0 &

generates the command

ip route 0.0.0.0 0.0.0.0 FastEthernet0/1.

Step 4

exit Return to global configuration mode.

Step 5

hostname name Enter the hostname for the switch.

Step 6

ip route network-number Establish a static route to the Configuration Engine whose

IP address is network-number.

4-10

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 4 Configuring Cisco IOS CNS Agents

Configuring Cisco IOS Agents

Step 7

cns id interface num {dns-reverse | ipaddress |
mac-address} [event]

or
cns id {hardware-serial | hostname | string string}
[event]

Set the unique EventID or ConfigID used by the
Configuration Engine.

• For interface num, enter the type of interface–for

example, Ethernet, Group-Async, Loopback, or
Virtual-Template. This setting specifies from which
interface the IP or MAC address should be retrieved to
define the unique ID.

• For {dns-reverse | ipaddress | mac-address} enter

dns-reverse to retrieve the hostname and assign it as

the unique ID, enter ipaddress to use the IP address, or
enter mac-address to use the MAC address as the
unique ID.

• (Optional) Enter event to set the ID to be the event-id

value used to identify the switch.

• For {hardware-serial | hostname| string string},

enter hardware-serial to set the switch serial number
as the unique ID, enter hostname (the default) to select
the switch hostname as the unique ID, or enter an
arbitrary text string for string string as the unique ID.

Step 8

cns config initial {ip-address | hostname}
[port-number] [event] [no-persist] [page page]
[source ip-address] [syntax-check]

Enable the Cisco IOS agent, and initiate an initial
configuration.

• For {ip-address | hostname}, enter the IP address or

the hostname of the configuration server.

• (Optional) For port-number, enter the port number of

the configuration server. The default port number is 80.

• (Optional) Enable event for configuration success,

failure, or warning messages when the configuration is
finished.

• (Optional) Enable no-persist to suppress the

automatic writing to NVRAM of the configuration
pulled as a result of entering the cns config initial
global configuration command. If the no-persist
keyword is not entered, using the cns config initial
command causes the resultant configuration to be
automatically written to NVRAM.

• (Optional) For page page, enter the web page of the

initial configuration. The default is /Config/config/asp.

• (Optional) Enter source ip-address to use for source IP

address.

• (Optional) Enable syntax-check to check the syntax

when this parameter is entered.

Note Though visible in the command-line help string,

the encrypt keyword is not supported.

Step 9

end Return to privileged EXEC mode.

Command Purpose

4-11

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 4 Configuring Cisco IOS CNS Agents

Configuring Cisco IOS Agents

To disable the CNS Cisco IOS agent, use the no cns config initial {ip-address | hostname} global
configuration command.

This example shows how to configure an initial configuration on a remote switch. The switch hostname
is the unique ID. The Cisco Configuration Engine IP address is 172.28.129.22.

Switch(config)# cns config connect-intf serial ping-interval 1 retries 1
Switch(config-cns-conn-if)# config-cli ip address negotiated
Switch(config-cns-conn-if)# config-cli encapsulation ppp
Switch(config-cns-conn-if)# config-cli ip directed-broadcast
Switch(config-cns-conn-if)# config-cli no keepalive
Switch(config-cns-conn-if)# config-cli no shutdown
Switch(config-cns-conn-if)# exit
Switch(config)# hostname RemoteSwitch
RemoteSwitch(config)# ip route 10.1.1.1 255.255.255.255 11.11.11.1
RemoteSwitch(config)# cns id Ethernet 0 ipaddress
RemoteSwitch(config)# cns config initial 10.1.1.1 no-persist

Enabling a Partial Configuration

Beginning in privileged EXEC mode, follow these steps to enable the Cisco IOS agent and to initiate a
partial configuration on the switch:

To disable the Cisco IOS agent, use the no cns config partial {ip-address | hostname} global
configuration command. To cancel a partial configuration, use the cns config cancel privileged EXEC
command.

Step 10

show cns config connections Verify information about the configuration agent.

Step 11

show running-config Verify your entries.

Command Purpose

Command Purpose

Step 1

configure terminal Enter global configuration mode.

Step 2

cns config partial {ip-address | hostname}
[port-number] [source ip-address]

Enable the configuration agent, and initiate a partial
configuration.

• For {ip-address | hostname}, enter the IP address or

the hostname of the configuration server.

• (Optional) For port-number, enter the port number of

the configuration server. The default port number is 80.

• (Optional) Enter source ip-address to use for the

source IP address.

Note Though visible in the command-line help string,

the encrypt keyword is not supported.

Step 3

end Return to privileged EXEC mode.

Step 4

show cns config stats

or

show cns config outstanding

Verify information about the configuration agent.

Step 5

show running-config Verify your entries.

Step 6

copy running-config startup-config (Optional) Save your entries in the configuration file.

4-12

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 4 Configuring Cisco IOS CNS Agents

Displaying CNS Configuration

Displaying CNS Configuration

You can use the privileged EXEC commands in Ta b le 4 -2 to display CNS configuration information.

Table 4-2 Displaying CNS Configuration

Command Purpose

show cns config connections Displays the status of the CNS Cisco IOS agent connections.

show cns config outstanding Displays information about incremental (partial) CNS

configurations that have started but are not yet completed.

show cns config stats Displays statistics about the Cisco IOS agent.

show cns event connections Displays the status of the CNS event agent connections.

show cns event stats Displays statistics about the CNS event agent.

show cns event subject Displays a list of event agent subjects that are subscribed to by

applications.

CHA PTER

5-1

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

5

Clustering Switches

This chapter provides the concepts and procedures to create and manage Catalyst 2960 switch clusters.
You can create and manage switch clusters by using Cisco Network Assistant (hereafter known as
Network Assistant), the command-line interface (CLI), or SNMP. For complete procedures, see the
online help. For the CLI cluster commands, see the switch command reference.

Note Network Assistant supports switch clusters, but we recommend that you instead group switches into

communities. Network Assistant has a Cluster Conversion Wizard to help you convert a cluster to a
community. For more information about Network Assistant, including introductory information on
managing switch clusters and converting a switch cluster to a community, see Getting Started with Cisco
Network Assistant, available on Cisco.com.

This chapter focuses on Catalyst 2960 switch clusters. It also includes guidelines and limitations for
clusters mixed with other cluster-capable Catalyst switches, but it does not provide complete
descriptions of the cluster features for these other switches. For complete cluster information for a
specific Catalyst platform, refer to the software configuration guide for that switch.

This chapter consists of these sections:

• Understanding Switch Clusters, page 5-1

• Planning a Switch Cluster, page 5-4

• Using the CLI to Manage Switch Clusters, page 5-14

• Using SNMP to Manage Switch Clusters, page 5-15

Note We do not recommend using the ip http access-class global configuration command to limit access to

specific hosts or networks. Access should be controlled through the cluster command switch or by
applying access control lists (ACLs) on interfaces that are configured with IP address. For more
information on ACLs, see Chapter 34, “Configuring Network Security with ACLs.”.

Understanding Switch Clusters

A switch cluster is a set of up to 16 connected, cluster-capable Catalyst switches that are managed as a
single entity. The switches in the cluster use the switch clustering technology so that you can configure
and troubleshoot a group of different Catalyst desktop switch platforms through a single IP address.

5-2

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 5 Clustering Switches

Understanding Switch Clusters

In a switch cluster, 1 switch must be the cluster command switch and up to 15 other switches can be
cluster member switches. The total number of switches in a cluster cannot exceed 16 switches. The

cluster command switch is the single point of access used to configure, manage, and monitor the cluster
member switches. Cluster members can belong to only one cluster at a time.

The benefits of clustering switches include:

• Management of Catalyst switches regardless of their interconnection media and their physical

locations. The switches can be in the same location, or they can be distributed across a Layer 2 or
Layer 3 (if your cluster is using a Catalyst 3550, Catalyst 3560, or Catalyst 3750 switch as a Layer 3
router between the Layer 2 switches in the cluster) network.

Cluster members are connected to the cluster command switch according to the connectivity
guidelines described in the “Automatic Discovery of Cluster Candidates and Members” section on

page 5-4. This section includes management VLAN considerations for the Catalyst 1900,

Catalyst 2820, Catalyst 2900 XL, Catalyst 2950, and Catalyst 3500 XL switches. For complete
information about these switches in a switch-cluster environment, refer to the software
configuration guide for that specific switch.

• Command-switch redundancy if a cluster command switch fails. One or more switches can be

designated as standby cluster command switches to avoid loss of contact with cluster members. A
cluster standby group is a group of standby cluster command switches.

• Management of a variety of Catalyst switches through a single IP address. This conserves on IP

addresses, especially if you have a limited number of them. All communication with the switch
cluster is through the cluster command switch IP address.

Table 5-1 lists the Catalyst switches eligible for switch clustering, including which ones can be cluster

command switches and which ones can only be cluster member switches, and the required software
versions.

Table 5-1 Switch Software and Cluster Capability

Switch Cisco IOS Release Cluster Capability

Catalyst 3750 12.1(11)AX or later Member or command switch

Catalyst 3560 12.1(19)EA1b or later Member or command switch

Catalyst 3550 12.1(4)EA1 or later Member or command switch

Catalyst 2970 12.1(11)AX or later Member or command switch

Catalyst 2960 12.2(25)FX or later Member or command switch

Catalyst 2955 12.1(12c)EA1 or later Member or command switch

Catalyst 2950 12.0(5.2)WC(1) or later Member or command switch

Catalyst 2950 LRE 12.1(11)JY or later Member or command switch

Catalyst 2940 12.1(13)AY or later Member or command switch

Catalyst 3500 XL 12.0(5.1)XU or later Member or command switch

Catalyst 2900 XL (8-MB switches) 12.0(5.1)XU or later Member or command switch

Catalyst 2900 XL (4-MB switches) 11.2(8.5)SA6 (recommended) Member switch only

Catalyst 1900 and 2820 9.00(-A or -EN) or later Member switch only

5-3

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 5 Clustering Switches

Understanding Switch Clusters

Cluster Command Switch Characteristics

A cluster command switch must meet these requirements:

• It is running Cisco IOS Release 12.2(25)FX or later.

• It has an IP address.

• It has Cisco Discovery Protocol (CDP) version 2 enabled (the default).

• It is not a command or cluster member switch of another cluster.

• It is connected to the standby cluster command switches through the management VLAN and to the

cluster member switches through a common VLAN.

Standby Cluster Command Switch Characteristics

A standby cluster command switch must meet these requirements:

• It is running Cisco IOS 12.2(25)FX or later.

• It has an IP address.

• It has CDP version 2 enabled.

• It is connected to the command switch and to other standby command switches through its

management VLAN.

• It is connected to all other cluster member switches (except the cluster command and standby

command switches) through a common VLAN.

• It is redundantly connected to the cluster so that connectivity to cluster member switches is

maintained.

• It is not a command or member switch of another cluster.

Note Standby cluster command switches must be the same type of switches as the cluster command

switch. For example, if the cluster command switch is a Catalyst switch, the standby cluster
command switches must also be Catalyst switches. Refer to the switch configuration guide of
other cluster-capable switches for their requirements on standby cluster command switches.

Candidate Switch and Cluster Member Switch Characteristics

Candidate switches are cluster-capable switches that have not yet been added to a cluster. Cluster
member switches are switches that have actually been added to a switch cluster. Although not required,
a candidate or cluster member switch can have its own IP address and password (for related
considerations, see the “IP Addresses” section on page 5-12 and “Passwords” section on page 5-13).

To join a cluster, a candidate switch must meet these requirements:

• It is running cluster-capable software.

• It has CDP version 2 enabled.

• It is not a command or cluster member switch of another cluster.

5-4

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 5 Clustering Switches

Planning a Switch Cluster

• If a cluster standby group exists, it is connected to every standby cluster command switch through

at least one common VLAN. The VLAN to each standby cluster command switch can be different.

• It is connected to the cluster command switch through at least one common VLAN.

Note Catalyst 1900, Catalyst 2820, Catalyst 2900 XL, Catalyst 2950, and Catalyst 3500 XL

candidate and cluster member switches must be connected through their management VLAN
to the cluster command switch and standby cluster command switches. For complete
information about these switches in a switch-cluster environment, refer to the software
configuration guide for that specific switch.

This requirement does not apply if you have a Catalyst 2970, Catalyst 3550, Catalyst 3560,
or Catalyst 3750 cluster command switch. Candidate and cluster member switches can
connect through any VLAN in common with the cluster command switch.

Planning a Switch Cluster

Anticipating conflicts and compatibility issues is a high priority when you manage several switches
through a cluster. This section describes these guidelines, requirements, and caveats that you should
understand before you create the cluster:

• Automatic Discovery of Cluster Candidates and Members, page 5-4

• HSRP and Standby Cluster Command Switches, page 5-9

• IP Addresses, page 5-12

• Hostnames, page 5-12

• Passwords, page 5-13

• SNMP Community Strings, page 5-13

• TACACS+ and RADIUS, page 5-14

• LRE Profiles, page 5-14

Refer to the release notes for the list of Catalyst switches eligible for switch clustering, including which
ones can be cluster command switches and which ones can only be cluster member switches, and for the
required software versions and browser and Java plug-in configurations.

Automatic Discovery of Cluster Candidates and Members

The cluster command switch uses Cisco Discovery Protocol (CDP) to discover cluster member switches,
candidate switches, neighboring switch clusters, and edge devices across multiple VLANs and in star or
cascaded topologies.

Note Do not disable CDP on the cluster command switch, on cluster members, or on any cluster-capable

switches that you might want a cluster command switch to discover. For more information about CDP,
see Chapter 20, “Configuring CDP.”

5-5

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 5 Clustering Switches

Planning a Switch Cluster

Following these connectivity guidelines ensures automatic discovery of the switch cluster, cluster
candidates, connected switch clusters, and neighboring edge devices:

• Discovery Through CDP Hops, page 5-5

• Discovery Through Non-CDP-Capable and Noncluster-Capable Devices, page 5-6

• Discovery Through Different VLANs, page 5-6

• Discovery Through Different Management VLANs, page 5-7

• Discovery of Newly Installed Switches, page 5-8

Discovery Through CDP Hops

By using CDP, a cluster command switch can discover switches up to seven CDP hops away (the default
is three hops) from the edge of the cluster. The edge of the cluster is where the last cluster member
switches are connected to the cluster and to candidate switches. For example, cluster member switches 9
and 10 in Figure 5-1 are at the edge of the cluster.

In Figure 5-1, the cluster command switch has ports assigned to VLANs 16 and 62. The CDP hop count
is three. The cluster command switch discovers switches 11, 12, 13, and 14 because they are within three
hops from the edge of the cluster. It does not discover switch 15 because it is four hops from the edge of
the cluster.

Figure 5-1 Discovery Through CDP Hops

Command device

Member
device 10

Member
device 8

Member
device 9

VLAN 62

Edge of
cluster

VLAN 16

101321

Device 11

candidate

device

Candidate
devices

Device 12

Device 13

Device 14

Device 15

5-6

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 5 Clustering Switches

Planning a Switch Cluster

Discovery Through Non-CDP-Capable and Noncluster-Capable Devices

If a cluster command switch is connected to a non-CDP-capable third-party hub (such as a non-Cisco
hub), it can discover cluster-enabled devices connected to that third-party hub. However, if the cluster
command switch is connected to a noncluster-capable Cisco device, it cannot discover a cluster-enabled
device connected beyond the noncluster-capable Cisco device.

Figure 5-2 shows that the cluster command switch discovers the switch that is connected to a third-party

hub. However, the cluster command switch does not discover the switch that is connected to a
Catalyst 5000 switch.

Figure 5-2 Discovery Through Non-CDP-Capable and Noncluster-Capable Devices

Discovery Through Different VLANs

If the cluster command switch is a Catalyst 2970, Catalyst 3550, Catalyst 3560, or Catalyst 3750 switch,
the cluster can have cluster member switches in different VLANs. As cluster member switches, they
must be connected through at least one VLAN in common with the cluster command switch. The cluster
command switch in Figure 5-3 has ports assigned to VLANs 9, 16, and 62 and therefore discovers the
switches in those VLANs. It does not discover the switch in VLAN 50. It also does not discover the
switch in VLAN 16 in the first column because the cluster command switch has no VLAN connectivity
to it.

Catalyst 2900 XL, Catalyst 2950, and Catalyst 3500 XL cluster member switches must be connected to
the cluster command switch through their management VLAN. For information about discovery through
management VLANs, see the “Discovery Through Different Management VLANs” section on page 5-7.
For more information about VLANs, see Chapter 12, “Configuring VLANs.”

Command device

Catalyst 5000 switch
(noncluster-capable)

Third-party hub

(non-CDP-capable)

Candidate device Candidate device

89377

5-7

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 5 Clustering Switches

Planning a Switch Cluster

Figure 5-3 Discovery Through Different VLANs

Discovery Through Different Management VLANs

Catalyst 2970, Catalyst 3550, Catalyst 3560, or Catalyst 3750 cluster command switches can discover
and manage cluster member switches in different VLANs and different management VLANs. As cluster
member switches, they must be connected through at least one VLAN in common with the cluster
command switch. They do not need to be connected to the cluster command switch through their
management VLAN. The default management VLAN is VLAN 1.

Note If the switch cluster has a Catalyst 3750 switch or switch stack, that switch or switch stack must be the

cluster command switch.

The cluster command switch and standby command switch in Figure 5-4 (assuming they are
Catalyst 2960 Catalyst 2970, Catalyst 3550, Catalyst 3560, or Catalyst 3750 cluster command switches)
have ports assigned to VLANs 9, 16, and 62. The management VLAN on the cluster command switch is
VLAN 9. Each cluster command switch discovers the switches in the different management VLANs
except these:

• Switches 7 and 10 (switches in management VLAN 4) because they are not connected through a

common VLAN (meaning VLANs 62 and 9) with the cluster command switch

• Switch 9 because automatic discovery does not extend beyond a noncandidate device, which is

switch 7

VLAN 62

VLAN 62

VLAN 16

VLAN trunk 9,16

Command device

VLAN 50

VLAN trunk 9,16

VLAN trunk 4,16

101322

5-8

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 5 Clustering Switches

Planning a Switch Cluster

Figure 5-4 Discovery Through Different Management VLANs with a Layer 3 Cluster Command

Switch

Discovery of Newly Installed Switches

To join a cluster, the new, out-of-the-box switch must be connected to the cluster through one of its
access ports. An access port (AP) carries the traffic of and belongs to only one VLAN. By default, the
new switch and its access ports are assigned to VLAN 1.

When the new switch joins a cluster, its default VLAN changes to the VLAN of the immediately
upstream neighbor. The new switch also configures its access port to belong to the VLAN of the
immediately upstream neighbor.

The cluster command switch in Figure 5-5 belongs to VLANs 9 and 16. When new cluster-capable
switches join the cluster:

• One cluster-capable switch and its access port are assigned to VLAN 9.

• The other cluster-capable switch and its access port are assigned to management VLAN 16.

101323

VLAN 62

VLAN trunk 4, 62

VLAN 62

VLAN 16

VLAN 9

VLAN 16

VLAN 9

Standby command

device

Command

device

VLAN 9

Device 7
(management
VLAN 4)

Device 9
(management
VLAN 62)

VLAN 4

Device 3

(management

VLAN 16)

Device 4

(management

VLAN 16)

Device 10
(management
VLAN 4)

Device 8
(management
VLAN 9)

Device 6
(management
VLAN 9)

Device 5
(management
VLAN 62)

5-9

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 5 Clustering Switches

Planning a Switch Cluster

Figure 5-5 Discovery of Newly Installed Switches

HSRP and Standby Cluster Command Switches

The switch uses Hot Standby Router Protocol (HSRP) so that you can configure a group of standby
cluster command switches. Because a cluster command switch manages the forwarding of all
communication and configuration information to all the cluster member switches, we strongly
recommend the following:

• For a cluster command switch stack, a standby cluster command switch is necessary if the entire

switch stack fails. However, if only the stack master in the command switch stack fails, the switch
stack elects a new stack master and resumes its role as the cluster command switch stack.

• For a cluster command switch that is a standalone switch, configure a standby cluster command

switch to take over if the primary cluster command switch fails.

A cluster standby group is a group of command-capable switches that meet the requirements described
in the “Standby Cluster Command Switch Characteristics” section on page 5-3. Only one cluster standby
group can be assigned per cluster.

The switches in the cluster standby group are ranked according to HSRP priorities. The switch with the
highest priority in the group is the active cluster command switch (AC). The switch with the next highest
priority is the standby cluster command switch (SC). The other switches in the cluster standby group are
the passive cluster command switches (PC). If the active cluster command switch and the standby cluster
command switch become disabled at the same time, the passive cluster command switch with the highest
priority becomes the active cluster command switch. For the limitations to automatic discovery, see the

“Automatic Recovery of Cluster Configuration” section on page 5-11.

Note The HSRP standby hold time interval should be greater than or equal to three times the hello time

interval. The default HSRP standby hold time interval is 10 seconds. The default HSRP standby hello
time interval is 3 seconds.

Command device

New (out-of-box)
candidate device

AP

Device A Device B

VLAN 9

VLAN 9

VLAN 16

VLAN 16

New (out-of-box)
candidate device

AP

101325

5-10

Catalyst 2960 Switch Software Configuration Guide

OL-8603-04

Chapter 5 Clustering Switches

Planning a Switch Cluster

These connectivity guidelines ensure automatic discovery of the switch cluster, cluster candidates,
connected switch clusters, and neighboring edge devices. These topics also provide more detail about
standby cluster command switches:

• Virtual IP Addresses, page 5-10

• Other Considerations for Cluster Standby Groups, page 5-10

• Automatic Recovery of Cluster Configuration, page 5-11

Virtual IP Addresses

You need to assign a unique virtual IP address and group number and name to the cluster standby group.
This information must be configured on a specific VLAN or routed port on the active cluster command
switch. The active cluster command switch receives traffic destined for the virtual IP address. To manage
the cluster, you must access the active cluster command switch through the virtual IP address, not
through the command-switch IP address. This is in case the IP address of the active cluster command
switch is different from the virtual IP address of the cluster standby group.

If the active cluster command switch fails, the standby cluster command switch assumes ownership of
the virtual IP address and becomes the active cluster command switch. The passive switches in the
cluster standby group compare their assigned priorities to decide the new standby cluster command
switch. The passive standby switch with the highest priority then becomes the standby cluster command
switch. When the previously active cluster command switch becomes active again, it resumes its role as
the active cluster command switch, and the current active cluster command switch becomes the standby
cluster command switch again. For more information about IP address in switch clusters, see the “IP

Addresses” section on page 5-12.

Other Considerations for Cluster Standby Groups

These requirements also apply:

• Standby cluster command switches must be the same type of switches as the cluster command

switch. For example, if the cluster command switch is a Catalyst 2960 switch, the standby cluster
command switches must also be Catalyst 2960 switches. Refer to the switch configuration guide of
other cluster-capable switches for their requirements on standby cluster command switches.

If your switch cluster has a Catalyst 2960 switch, it should be the cluster command switch.

• Only one cluster standby group can be assigned to a cluster. You can have more than one

router-redundancy standby group.