You are on page 1of 1026

Catalyst 2960 and 2960-S Switches Software Configuration Guide

Cisco IOS Release 15.0(2)SE August 2012

Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883

Text Part Number: OL-26520-02

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. Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental. Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE Copyright © 2004–2012 Cisco Systems, Inc. All rights reserved.

CONTENTS
Preface
xxxvii xxxvii xxxvii xxxviii xxxix xl

Audience Purpose Conventions

Related Publications

Obtaining Documentation, Obtaining Support, and Security Guidelines
1

CHAPTER

Overview

1-1

Features 1-1 Ease-of-Deployment and Ease-of-Use Features Performance Features 1-4 Management Options 1-5 Manageability Features 1-6 Availability and Redundancy Features 1-8 VLAN Features 1-9 Security Features 1-10 QoS and CoS Features 1-13 Layer 3 Features 1-15 Power over Ethernet Features 1-15 Monitoring Features 1-15 Default Settings After Initial Switch Configuration

1-2

1-16

Network Configuration Examples 1-19 Design Concepts for Using the Switch 1-19 Small to Medium-Sized Network Using Catalyst 2960, 2960-S and 2960-C Switches Long-Distance, High-Bandwidth Transport Configuration 1-24 Where to Go Next
2
1-25

1-23

CHAPTER

Using the Command-Line Interface Understanding Command Modes Understanding the Help System

2-1 2-1 2-3 2-3 2-4

Understanding Abbreviated Commands Understanding CLI Error Messages
2-4

Understanding no and default Forms of Commands

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE OL-26520-02

iii

Contents

Using Configuration Logging

2-4

Using Command History 2-5 Changing the Command History Buffer Size 2-5 Recalling Commands 2-6 Disabling the Command History Feature 2-6 Using Editing Features 2-6 Enabling and Disabling Editing Features 2-6 Editing Commands through Keystrokes 2-7 Editing Command Lines that Wrap 2-8 Searching and Filtering Output of show and more Commands
2-9

Accessing the CLI 2-9 Accessing the CLI through a Console Connection or through Telnet
3

2-10

CHAPTER

Assigning the Switch IP Address and Default Gateway Understanding the Boot Process
3-1

3-1

Assigning Switch Information 3-2 Default Switch Information 3-3 Understanding DHCP-Based Autoconfiguration 3-3 DHCP Client Request Process 3-3 Understanding DHCP-based Autoconfiguration and Image Update 3-5 DHCP Autoconfiguration 3-5 DHCP Auto-Image Update 3-5 Limitations and Restrictions 3-5 Configuring DHCP-Based Autoconfiguration 3-6 DHCP Server Configuration Guidelines 3-6 Configuring the TFTP Server 3-7 Configuring the DNS 3-7 Configuring the Relay Device 3-7 Obtaining Configuration Files 3-8 Example Configuration 3-9 Configuring the DHCP Auto Configuration and Image Update Features 3-11 Configuring DHCP Autoconfiguration (Only Configuration File) 3-11 Configuring DHCP Auto-Image Update (Configuration File and Image) 3-12 Configuring the Client 3-13 Manually Assigning IP Information 3-14 Checking and Saving the Running Configuration Configuring the NVRAM Buffer Size 3-16 Modifying the Startup Configuration 3-17 Default Boot Configuration 3-18
Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE

3-15

iv

OL-26520-02

Contents

Automatically Downloading a Configuration File 3-18 Specifying the Filename to Read and Write the System Configuration Booting Manually 3-19 Booting a Specific Software Image 3-19 Controlling Environment Variables 3-20 Scheduling a Reload of the Software Image 3-21 Configuring a Scheduled Reload 3-22 Displaying Scheduled Reload Information 3-23
4

3-18

CHAPTER

Configuring Cisco IOS Configuration Engine

4-1

Understanding Cisco Configuration Engine Software 4-1 Configuration Service 4-2 Event Service 4-3 NameSpace Mapper 4-3 What You Should Know About the CNS IDs and Device Hostnames ConfigID 4-3 DeviceID 4-4 Hostname and DeviceID 4-4 Using Hostname, DeviceID, and ConfigID 4-4 Understanding Cisco IOS Agents 4-5 Initial Configuration 4-5 Incremental (Partial) Configuration Synchronized Configuration 4-6

4-3

4-6

Configuring Cisco IOS Agents 4-6 Enabling Automated CNS Configuration 4-6 Enabling the CNS Event Agent 4-8 Enabling the Cisco IOS CNS Agent 4-9 Enabling an Initial Configuration 4-9 Enabling a Partial Configuration 4-12 Displaying CNS Configuration
5
4-13

CHAPTER

Administering the Switch

5-1 5-1

Identifying the Switch Image

Managing the System Time and Date 5-2 Understanding the System Clock 5-2 Understanding Network Time Protocol 5-3 NTP Version 4 5-5 Configuring Time and Date Manually 5-5 Setting the System Clock 5-6
Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE OL-26520-02

v

Contents

Displaying the Time and Date Configuration 5-6 Configuring the Time Zone 5-7 Configuring Summer Time (Daylight Saving Time) 5-8 Configuring a System Name and Prompt 5-9 Default System Name and Prompt Configuration Configuring a System Name 5-10 Understanding DNS 5-10 Default DNS Configuration 5-11 Setting Up DNS 5-11 Displaying the DNS Configuration 5-12 Creating a Banner 5-12 Default Banner Configuration 5-12 Configuring a Message-of-the-Day Login Banner Configuring a Login Banner 5-14
5-10

5-13

Managing the MAC Address Table 5-14 Building the Address Table 5-15 MAC Addresses and VLANs 5-15 MAC Addresses and Switch Stacks 5-16 Default MAC Address Table Configuration 5-16 Changing the Address Aging Time 5-16 Removing Dynamic Address Entries 5-17 Configuring MAC Address Change Notification Traps 5-17 Configuring MAC Address Move Notification Traps 5-19 Configuring MAC Threshold Notification Traps 5-20 Adding and Removing Static Address Entries 5-21 Configuring Unicast MAC Address Filtering 5-22 Disabling MAC Address Learning on a VLAN 5-23 Displaying Address Table Entries 5-24 Managing the ARP Table
6
5-25

CHAPTER

Clustering Switches

6-1

Understanding Switch Clusters 6-2 Cluster Command Switch Characteristics 6-3 Standby Cluster Command Switch Characteristics 6-3 Candidate Switch and Cluster Member Switch Characteristics

6-4

Planning a Switch Cluster 6-4 Automatic Discovery of Cluster Candidates and Members 6-5 Discovery Through CDP Hops 6-5 Discovery Through Non-CDP-Capable and Noncluster-Capable Devices
Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE

6-6

vi

OL-26520-02

Contents

Discovery Through Different VLANs 6-7 Discovery Through Different Management VLANs 6-7 Discovery of Newly Installed Switches 6-8 HSRP and Standby Cluster Command Switches 6-9 Virtual IP Addresses 6-11 Other Considerations for Cluster Standby Groups 6-11 Automatic Recovery of Cluster Configuration 6-12 IP Addresses 6-13 Hostnames 6-13 Passwords 6-13 SNMP Community Strings 6-14 Switch Clusters and Switch Stacks 6-14 TACACS+ and RADIUS 6-16 LRE Profiles 6-16 Using the CLI to Manage Switch Clusters Using SNMP to Manage Switch Clusters
7
6-16 6-17

CHAPTER

Managing Switch Stacks

7-1

Understanding Stacks 7-1 Stack Membership 7-3 Master Election 7-5 Stack MAC Address 7-6 Member Numbers 7-6 Member Priority Values 7-7 Stack Offline Configuration 7-7 Effects of Adding a Provisioned Switch to a Stack 7-8 Effects of Replacing a Provisioned Switch in a Stack 7-9 Effects of Removing a Provisioned Switch from a Stack 7-9 Stack Software Compatibility Recommendations 7-9 Stack Protocol Version Compatibility 7-10 Major Version Number Incompatibility Among Switches 7-10 Minor Version Number Incompatibility Among Switches 7-10 Understanding Auto-Upgrade and Auto-Advise 7-11 Auto-Upgrade and Auto-Advise Example Messages 7-12 Incompatible Software and Member Image Upgrades 7-13 Stack Configuration Files 7-14 Additional Considerations for System-Wide Configuration on Switch Stacks Stack Management Connectivity 7-15 Stack Through an IP Address 7-15

7-14

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE OL-26520-02

vii

Contents

Stack Through an SSH Session 7-15 Stack Through Console Ports 7-15 Specific Members 7-16 Stack Configuration Scenarios 7-16 Configuring the Switch Stack 7-17 Default Switch Stack Configuration 7-17 Enabling Persistent MAC Address 7-18 Assigning Stack Member Information 7-20 Assigning a Member Number 7-20 Setting the Member Priority Value 7-20 Provisioning a New Member for a Stack 7-21 Changing the Stack Membership 7-22 Accessing the CLI of a Specific Member Displaying Stack Information
7-22 7-22

Troubleshooting Stacks 7-23 Manually Disabling a Stack Port 7-23 Re-Enabling a Stack Port While Another Member Starts 7-23 Understanding the show switch stack-ports summary Output 7-24
8

CHAPTER

Configuring SDM Templates

8-1

Understanding the SDM Templates 8-1 SDM Templates and Switch Stacks 8-3 Configuring the Switch SDM Template 8-4 Default SDM Template 8-4 SDM Template Configuration Guidelines Setting the SDM Template 8-5 .Displaying the SDM Templates
9
8-5

8-4

CHAPTER

Configuring Switch-Based Authentication

9-1 9-1

Preventing Unauthorized Access to Your Switch

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

9-3

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE

viii

OL-26520-02

Contents

Setting the Privilege Level for a Command 9-8 Changing the Default Privilege Level for Lines 9-9 Logging into and Exiting a Privilege Level 9-10 Controlling Switch Access with TACACS+ 9-10 Understanding TACACS+ 9-10 TACACS+ Operation 9-12 Configuring TACACS+ 9-13 Default TACACS+ Configuration 9-13 Identifying the TACACS+ Server Host and Setting the Authentication Key 9-13 Configuring TACACS+ Login Authentication 9-14 Configuring TACACS+ Authorization for Privileged EXEC Access and Network Services Starting TACACS+ Accounting 9-17 Establishing a Session with a Router if the AAA Server is Unreachable 9-17 Displaying the TACACS+ Configuration 9-18

9-16

Controlling Switch Access with RADIUS 9-18 Understanding RADIUS 9-18 RADIUS Operation 9-20 RADIUS Change of Authorization 9-20 Overview 9-20 Change-of-Authorization Requests 9-21 CoA Request Response Code 9-22 CoA Request Commands 9-23 Stacking Guidelines for Session Termination 9-26 Configuring RADIUS 9-27 Default RADIUS Configuration 9-27 Identifying the RADIUS Server Host 9-28 Configuring RADIUS Login Authentication 9-30 Defining AAA Server Groups 9-32 Configuring RADIUS Authorization for User Privileged Access and Network Services 9-34 Starting RADIUS Accounting 9-35 Establishing a Session with a Router if the AAA Server is Unreachable 9-36 Configuring Settings for All RADIUS Servers 9-36 Configuring the Switch to Use Vendor-Specific RADIUS Attributes 9-36 Configuring the Switch for Vendor-Proprietary RADIUS Server Communication 9-38 Configuring CoA on the Switch 9-39 Monitoring and Troubleshooting CoA Functionality 9-40 Configuring RADIUS Server Load Balancing 9-40 Displaying the RADIUS Configuration 9-40 Configuring the Switch for Local Authentication and Authorization
9-40

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE OL-26520-02

ix

Contents

Configuring the Switch for Secure Shell 9-41 Understanding SSH 9-42 SSH Servers, Integrated Clients, and Supported Versions Limitations 9-42 Configuring SSH 9-43 Configuration Guidelines 9-43 Setting Up the Switch to Run SSH 9-43 Configuring the SSH Server 9-44 Displaying the SSH Configuration and Status 9-45 Configuring the Switch for Secure Socket Layer HTTP 9-46 Understanding Secure HTTP Servers and Clients 9-46 Certificate Authority Trustpoints 9-46 CipherSuites 9-48 Configuring Secure HTTP Servers and Clients 9-48 Default SSL Configuration 9-48 SSL Configuration Guidelines 9-49 Configuring a CA Trustpoint 9-49 Configuring the Secure HTTP Server 9-50 Configuring the Secure HTTP Client 9-51 Displaying Secure HTTP Server and Client Status 9-52 Configuring the Switch for Secure Copy Protocol Information About Secure Copy 9-53
10
9-52

9-42

CHAPTER

Configuring IEEE 802.1x Port-Based Authentication

10-1

Understanding IEEE 802.1x Port-Based Authentication 10-1 Device Roles 10-3 Authentication Process 10-4 Authentication Initiation and Message Exchange 10-5 Authentication Manager 10-7 Port-Based Authentication Methods 10-7 Per-User ACLs and Filter-Ids 10-8 Authentication Manager CLI Commands 10-9 Ports in Authorized and Unauthorized States 10-10 802.1x Authentication and Switch Stacks 10-11 802.1x Host Mode 10-12 Multidomain Authentication 10-13 802.1x Multiple Authentication Mode 10-14 MAC Move 10-15 MAC Replace 10-15

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE

x

OL-26520-02

Contents

802.1x Accounting 10-16 802.1x Accounting Attribute-Value Pairs 10-16 802.1x Readiness Check 10-17 802.1x Authentication with VLAN Assignment 10-18 Using 802.1x Authentication with Per-User ACLs 10-19 802.1x Authentication with Downloadable ACLs and Redirect URLs 10-20 Cisco Secure ACS and Attribute-Value Pairs for the Redirect URL 10-22 Cisco Secure ACS and Attribute-Value Pairs for Downloadable ACLs 10-22 VLAN ID-based MAC Authentication 10-22 802.1x Authentication with Guest VLAN 10-23 802.1x Authentication with Restricted VLAN 10-24 802.1x Authentication with Inaccessible Authentication Bypass 10-25 Support on Multiple-Authentication Ports 10-25 Authentication Results 10-25 Feature Interactions 10-26 802.1x Critical Voice VLAN 10-27 802.1x Authentication with Voice VLAN Ports 10-27 802.1x Authentication with Port Security 10-28 802.1x Authentication with Wake-on-LAN 10-28 802.1x Authentication with MAC Authentication Bypass 10-28 802.1x User Distribution 10-30 802.1x User Distribution Configuration Guidelines 10-30 Network Admission Control Layer 2 802.1x Validation 10-31 Flexible Authentication Ordering 10-31 Open1x Authentication 10-31 Using Voice Aware 802.1x Security 10-32 802.1x Supplicant and Authenticator Switches with Network Edge Access Topology (NEAT) Guidelines 10-34 Using IEEE 802.1x Authentication with ACLs and the RADIUS Filter-Id Attribute 10-34 Common Session ID 10-34 Configuring 802.1x Authentication 10-35 Default 802.1x Authentication Configuration 10-36 802.1x Authentication Configuration Guidelines 10-37 802.1x Authentication 10-37 VLAN Assignment, Guest VLAN, Restricted VLAN, and Inaccessible Authentication Bypass 10-38 MAC Authentication Bypass 10-39 Maximum Number of Allowed Devices Per Port 10-39 Configuring 802.1x Readiness Check 10-39 Configuring Voice Aware 802.1x Security 10-40
Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE OL-26520-02

10-32

xi

Contents

Configuring 802.1x Violation Modes 10-42 Configuring 802.1x Authentication 10-43 Configuring the Switch-to-RADIUS-Server Communication 10-44 Configuring the Host Mode 10-45 Configuring Periodic Re-Authentication 10-47 Manually Re-Authenticating a Client Connected to a Port 10-48 Changing the Quiet Period 10-48 Changing the Switch-to-Client Retransmission Time 10-48 Setting the Switch-to-Client Frame-Retransmission Number 10-49 Setting the Re-Authentication Number 10-50 Enabling MAC Move 10-50 Enabling MAC Replace 10-51 Configuring 802.1x Accounting 10-52 Configuring a Guest VLAN 10-53 Configuring a Restricted VLAN 10-53 Configuring Inaccessible Authentication Bypass and Critical Voice VLAN 10-55 Configuring 802.1x Authentication with Wake-on-LAN 10-57 Configuring MAC Authentication Bypass 10-58 Configuring a MAC Authentication Bypass (MAB) Username and Password 10-58 Configuring 802.1x User Distribution 10-59 Configuring NAC Layer 2 802.1x Validation 10-60 Configuring an Authenticator and a Supplicant Switch with NEAT 10-61 Configuring NEAT with Auto Smartports Macros 10-62 Configuring 802.1x Authentication with Downloadable ACLs and Redirect URLs 10-63 Configuring Downloadable ACLs 10-63 Configuring a Downloadable Policy 10-63 Configuring VLAN ID-based MAC Authentication 10-65 Configuring Flexible Authentication Ordering 10-65 Configuring Open1x 10-66 Disabling 802.1x Authentication on the Port 10-67 Resetting the 802.1x Authentication Configuration to the Default Values 10-67 Displaying 802.1x Statistics and Status
11
10-68

CHAPTER

Configuring Web-Based Authentication Understanding Web-Based Authentication Device Roles 11-2 Host Detection 11-2 Session Creation 11-3 Authentication Process 11-3

11-1 11-1

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE

xii

OL-26520-02

Contents

Local Web Authentication Banner 11-4 Web Authentication Customizable Web Pages 11-6 Guidelines 11-6 Web-based Authentication Interactions with Other Features Port Security 11-7 LAN Port IP 11-8 Gateway IP 11-8 ACLs 11-8 Context-Based Access Control 11-8 802.1x Authentication 11-8 EtherChannel 11-8

11-7

Configuring Web-Based Authentication 11-9 Default Web-Based Authentication Configuration 11-9 Web-Based Authentication Configuration Guidelines and Restrictions Web-Based Authentication Configuration Task List 11-10 Configuring the Authentication Rule and Interfaces 11-10 Configuring AAA Authentication 11-11 Configuring Switch-to-RADIUS-Server Communication 11-11 Configuring the HTTP Server 11-13 Customizing the Authentication Proxy Web Pages 11-13 Specifying a Redirection URL for Successful Login 11-15 Configuring the Web-Based Authentication Parameters 11-15 Configuring a Web Authentication Local Banner 11-16 Removing Web-Based Authentication Cache Entries 11-16 Displaying Web-Based Authentication Status
12
11-17

11-9

CHAPTER

Configuring Interface Characteristics

12-1

Understanding Interface Types 12-1 Connecting Interfaces, page 12-11Port-Based VLANs 12-2 Switch Ports 12-2 Access Ports 12-3 Trunk Ports 12-3 Switch Virtual Interfaces 12-3 EtherChannel Port Groups 12-4 Dual-Purpose Uplink Ports 12-4 Power over Ethernet Ports 12-5 Supported Protocols and Standards 12-5 Powered-Device Detection and Initial Power Allocation Power Management Modes 12-7

12-6

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE OL-26520-02

xiii

Contents

Power Monitoring and Power Policing 12-8 PoE Uplinks and PoE Pass-Through Capability Connecting Interfaces 12-11 Using the Switch USB Ports 12-11 USB Mini-Type B Console Port 12-12 Console Port Change Logs 12-12 Configuring the Console Media Type 12-13 Configuring the USB Inactivity Timeout 12-13 USB Type A Port 12-14 Using Interface Configuration Mode 12-17 Procedures for Configuring Interfaces 12-18 Configuring a Range of Interfaces 12-19 Configuring and Using Interface Range Macros

12-10

12-20

Using the Ethernet Management Port (Catalyst 2960-S Only) 12-22 Understanding the Ethernet Management Port 12-22 Supported Features on the Ethernet Management Port 12-23 Configuring the Ethernet Management Port 12-24 TFTP and the Ethernet Management Port 12-24 Configuring Ethernet Interfaces 12-25 Default Ethernet Interface Configuration 12-25 Setting the Type of a Dual-Purpose Uplink Port 12-26 Configuring Interface Speed and Duplex Mode 12-28 Speed and Duplex Configuration Guidelines 12-28 Setting the Interface Speed and Duplex Parameters 12-29 Configuring IEEE 802.3x Flow Control 12-30 Configuring Auto-MDIX on an Interface 12-31 Configuring a Power Management Mode on a PoE Port 12-32 Budgeting Power for Devices Connected to a PoE Port 12-33 Configuring Power Policing 12-35 Configuring Catalyst PoE and PoE Pass-Through Ports on Compact Switches Adding a Description for an Interface 12-39 Configuring Layer 3 SVIs
12-39 12-40

12-37

Configuring the System MTU

Monitoring and Maintaining the Interfaces 12-42 Monitoring Interface Status 12-42 Clearing and Resetting Interfaces and Counters 12-43 Shutting Down and Restarting the Interface 12-43

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE

xiv

OL-26520-02

Contents

CHAPTER

13

Configuring VLANs

13-1

Understanding VLANs 13-1 Supported VLANs 13-3 VLAN Port Membership Modes

13-4

Configuring Normal-Range VLANs 13-5 Token Ring VLANs 13-6 Normal-Range VLAN Configuration Guidelines 13-6 Configuring Normal-Range VLANs 13-7 Default Ethernet VLAN Configuration 13-8 Creating or Modifying an Ethernet VLAN 13-8 Deleting a VLAN 13-9 Assigning Static-Access Ports to a VLAN 13-10 Configuring Extended-Range VLANs 13-11 Default VLAN Configuration 13-11 Extended-Range VLAN Configuration Guidelines Creating an Extended-Range VLAN 13-12 Displaying VLANs
13-13

13-11

Configuring VLAN Trunks 13-14 Trunking Overview 13-14 IEEE 802.1Q Configuration Considerations 13-15 Default Layer 2 Ethernet Interface VLAN Configuration 13-15 Configuring an Ethernet Interface as a Trunk Port 13-16 Interaction with Other Features 13-16 Configuring a Trunk Port 13-17 Defining the Allowed VLANs on a Trunk 13-18 Changing the Pruning-Eligible List 13-19 Configuring the Native VLAN for Untagged Traffic 13-20 Configuring Trunk Ports for Load Sharing 13-20 Load Sharing Using STP Port Priorities 13-21 Load Sharing Using STP Path Cost 13-23 Configuring VMPS 13-24 Understanding VMPS 13-24 Dynamic-Access Port VLAN Membership 13-25 Default VMPS Client Configuration 13-25 VMPS Configuration Guidelines 13-26 Configuring the VMPS Client 13-26 Entering the IP Address of the VMPS 13-26 Configuring Dynamic-Access Ports on VMPS Clients Reconfirming VLAN Memberships 13-28

13-27

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE OL-26520-02

xv

Contents

Changing the Reconfirmation Interval 13-28 Changing the Retry Count 13-28 Monitoring the VMPS 13-29 Troubleshooting Dynamic-Access Port VLAN Membership VMPS Configuration Example 13-29
14

13-29

CHAPTER

Configuring VTP

14-1

Understanding VTP 14-1 The VTP Domain 14-2 VTP Modes 14-3 VTP Advertisements 14-4 VTP Version 2 14-5 VTP Version 3 14-5 VTP Pruning 14-6 VTP and Switch Stacks 14-8 Configuring VTP 14-8 Default VTP Configuration 14-9 VTP Configuration Guidelines 14-9 Domain Names 14-10 Passwords 14-10 VTP Version 14-10 Configuration Requirements 14-11 Configuring VTP Mode 14-11 Configuring a VTP Version 3 Password 14-14 Configuring a VTP Version 3 Primary Server 14-14 Enabling the VTP Version 14-15 Enabling VTP Pruning 14-16 Configuring VTP on a Per-Port Basis 14-16 Adding a VTP Client Switch to a VTP Domain 14-17 Monitoring VTP
15
14-18

CHAPTER

Configuring Voice VLAN

15-1

Understanding Voice VLAN 15-1 Cisco IP Phone Voice Traffic 15-2 Cisco IP Phone Data Traffic 15-2 Configuring Voice VLAN 15-3 Default Voice VLAN Configuration 15-3 Voice VLAN Configuration Guidelines 15-3 Configuring a Port Connected to a Cisco 7960 IP Phone
Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE

15-4

xvi

OL-26520-02

Contents

Configuring Cisco IP Phone Voice Traffic 15-5 Configuring the Priority of Incoming Data Frames Displaying Voice VLAN
16
15-7

15-6

CHAPTER

Configuring STP

16-1

Understanding Spanning-Tree Features 16-1 STP Overview 16-2 Spanning-Tree Topology and BPDUs 16-3 Bridge ID, Switch Priority, and Extended System ID 16-4 Spanning-Tree Interface States 16-5 Blocking State 16-6 Listening State 16-7 Learning State 16-7 Forwarding State 16-7 Disabled State 16-8 How a Switch or Port Becomes the Root Switch or Root Port 16-8 Spanning Tree and Redundant Connectivity 16-9 Spanning-Tree Address Management 16-9 Accelerated Aging to Retain Connectivity 16-9 Spanning-Tree Modes and Protocols 16-10 Supported Spanning-Tree Instances 16-10 Spanning-Tree Interoperability and Backward Compatibility 16-11 STP and IEEE 802.1Q Trunks 16-11 Spanning Tree and Switch Stacks 16-12 Configuring Spanning-Tree Features 16-12 Default Spanning-Tree Configuration 16-13 Spanning-Tree Configuration Guidelines 16-14 Changing the Spanning-Tree Mode. 16-15 Disabling Spanning Tree 16-16 Configuring the Root Switch 16-16 Configuring a Secondary Root Switch 16-18 Configuring Port Priority 16-18 Configuring Path Cost 16-20 Configuring the Switch Priority of a VLAN 16-21 Configuring Spanning-Tree Timers 16-22 Configuring the Hello Time 16-22 Configuring the Forwarding-Delay Time for a VLAN 16-23 Configuring the Maximum-Aging Time for a VLAN 16-23 Configuring the Transmit Hold-Count 16-24

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE OL-26520-02

xvii

Contents

Displaying the Spanning-Tree Status
17

16-24

CHAPTER

Configuring MSTP

17-1

Understanding MSTP 17-2 Multiple Spanning-Tree Regions 17-2 IST, CIST, and CST 17-3 Operations Within an MST Region 17-3 Operations Between MST Regions 17-4 IEEE 802.1s Terminology 17-5 Hop Count 17-5 Boundary Ports 17-6 IEEE 802.1s Implementation 17-6 Port Role Naming Change 17-7 Interoperation Between Legacy and Standard Switches Detecting Unidirectional Link Failure 17-8 MSTP and Switch Stacks 17-8 Interoperability with IEEE 802.1D STP 17-9 Understanding RSTP 17-9 Port Roles and the Active Topology 17-9 Rapid Convergence 17-10 Synchronization of Port Roles 17-11 Bridge Protocol Data Unit Format and Processing 17-12 Processing Superior BPDU Information 17-13 Processing Inferior BPDU Information 17-13 Topology Changes 17-13 Configuring MSTP Features 17-14 Default MSTP Configuration 17-14 MSTP Configuration Guidelines 17-15 Specifying the MST Region Configuration and Enabling MSTP Configuring the Root Switch 17-18 Configuring a Secondary Root Switch 17-19 Configuring Port Priority 17-20 Configuring Path Cost 17-22 Configuring the Switch Priority 17-23 Configuring the Hello Time 17-24 Configuring the Forwarding-Delay Time 17-24 Configuring the Maximum-Aging Time 17-25 Configuring the Maximum-Hop Count 17-25 Specifying the Link Type to Ensure Rapid Transitions 17-26

17-7

17-16

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE

xviii

OL-26520-02

Contents

Designating the Neighbor Type 17-26 Restarting the Protocol Migration Process Displaying the MST Configuration and Status
18

17-27 17-27

CHAPTER

Configuring Optional Spanning-Tree Features

18-1

Understanding Optional Spanning-Tree Features 18-1 Understanding Port Fast 18-2 Understanding BPDU Guard 18-2 Understanding BPDU Filtering 18-3 Understanding UplinkFast 18-4 Understanding Cross-Stack UplinkFast 18-5 How CSUF Works 18-6 Events that Cause Fast Convergence 18-7 Understanding BackboneFast 18-7 Understanding EtherChannel Guard 18-10 Understanding Root Guard 18-10 Understanding Loop Guard 18-11 Configuring Optional Spanning-Tree Features 18-12 Default Optional Spanning-Tree Configuration 18-12 Optional Spanning-Tree Configuration Guidelines 18-12 Enabling Port Fast 18-13 Enabling BPDU Guard 18-14 Enabling BPDU Filtering 18-15 Enabling UplinkFast for Use with Redundant Links 18-16 Enabling Cross-Stack UplinkFast 18-17 Enabling BackboneFast 18-17 Enabling EtherChannel Guard 18-17 Enabling Root Guard 18-18 Enabling Loop Guard 18-19 Displaying the Spanning-Tree Status
19
18-19

CHAPTER

Configuring Flex Links and the MAC Address-Table Move Update Feature Understanding Flex Links and the MAC Address-Table Move Update Flex Links 19-2 VLAN Flex Link Load Balancing and Support 19-2 Flex Link Multicast Fast Convergence 19-3 Learning the Other Flex Link Port as the mrouter Port 19-3 Generating IGMP Reports 19-4 Leaking IGMP Reports 19-4
19-1

19-1

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE OL-26520-02

xix

Contents

Configuration Examples 19-4 MAC Address-Table Move Update 19-6 Configuring Flex Links and the MAC Address-Table Move Update 19-7 Default Configuration 19-8 Configuration Guidelines 19-8 Configuring Flex Links 19-9 Configuring VLAN Load Balancing on Flex Links 19-11 Configuring the MAC Address-Table Move Update Feature 19-13 Monitoring Flex Links and the MAC Address-Table Move Update
20
19-15

CHAPTER

Configuring DHCP and IP Source Guard Features Understanding DHCP Snooping 20-1 DHCP Server 20-2 DHCP Relay Agent 20-2 DHCP Snooping 20-2 Option-82 Data Insertion 20-3 DHCP Snooping Binding Database 20-6 DHCP Snooping and Switch Stacks 20-7

20-1

Configuring DHCP Snooping 20-7 Default DHCP Snooping Configuration 20-8 DHCP Snooping Configuration Guidelines 20-8 Configuring the DHCP Relay Agent 20-9 Enabling DHCP Snooping and Option 82 20-10 Enabling the DHCP Snooping Binding Database Agent Displaying DHCP Snooping Information
20-12

20-11

Understanding IP Source Guard 20-13 Source IP Address Filtering 20-13 Source IP and MAC Address Filtering 20-14 IP Source Guard for Static Hosts 20-14 Configuring IP Source Guard 20-15 Default IP Source Guard Configuration 20-15 IP Source Guard Configuration Guidelines 20-16 Enabling IP Source Guard 20-16 Configuring IP Source Guard for Static Hosts 20-17 Configuring IP Source Guard for Static Hosts on a Layer 2 Access Port Displaying IP Source Guard Information
20-21 20-21

20-18

Understanding DHCP Server Port-Based Address Allocation Configuring DHCP Server Port-Based Address Allocation

20-22

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE

xx

OL-26520-02

0(1)SE OL-26520-02 xxi .Contents Default Port-Based Address Allocation Configuration 20-22 Port-Based Address Allocation Configuration Guidelines 20-22 Enabling DHCP Server Port-Based Address Allocation 20-23 Displaying DHCP Server Port-Based Address Allocation 21 20-25 CHAPTER Configuring IGMP Snooping and MVR 21-1 Understanding IGMP Snooping 21-2 IGMP Versions 21-3 Joining a Multicast Group 21-3 Leaving a Multicast Group 21-5 Immediate Leave 21-5 IGMP Configurable-Leave Timer 21-6 IGMP Report Suppression 21-6 IGMP Snooping and Switch Stacks 21-6 Configuring IGMP Snooping 21-7 Default IGMP Snooping Configuration 21-7 Enabling or Disabling IGMP Snooping 21-7 Setting the Snooping Method 21-8 Configuring a Multicast Router Port 21-9 Configuring a Host Statically to Join a Group 21-10 Enabling IGMP Immediate Leave 21-10 Configuring the IGMP Leave Timer 21-11 Configuring TCN-Related Commands 21-12 Controlling the Multicast Flooding Time After a TCN Event Recovering from Flood Mode 21-13 Disabling Multicast Flooding During a TCN Event 21-13 Configuring the IGMP Snooping Querier 21-14 Disabling IGMP Report Suppression 21-15 Displaying IGMP Snooping Information 21-16 21-12 Understanding Multicast VLAN Registration 21-17 Using MVR in a Multicast Television Application Configuring MVR 21-19 Default MVR Configuration 21-19 MVR Configuration Guidelines and Limitations Configuring MVR Global Parameters 21-20 Configuring MVR Interfaces 21-21 Displaying MVR Information 21-23 21-18 21-20 Configuring IGMP Filtering and Throttling 21-23 Default IGMP Filtering and Throttling Configuration 21-24 Catalyst 2960 and 2960-S Switches Software Configuration Guide. Release 15.

0(1)SE 23-3 xxii OL-26520-02 . Release 15.Contents Configuring IGMP Profiles 21-24 Applying IGMP Profiles 21-26 Setting the Maximum Number of IGMP Groups Configuring the IGMP Throttling Action 21-27 Displaying IGMP Filtering and Throttling Configuration 22 21-26 21-28 CHAPTER Configuring Dynamic ARP Inspection 22-1 Understanding Dynamic ARP Inspection 22-1 Interface Trust States and Network Security 22-3 Rate Limiting of ARP Packets 22-4 Relative Priority of ARP ACLs and DHCP Snooping Entries Logging of Dropped Packets 22-5 Configuring Dynamic ARP Inspection 22-5 Default Dynamic ARP Inspection Configuration 22-5 Dynamic ARP Inspection Configuration Guidelines 22-6 Configuring Dynamic ARP Inspection in DHCP Environments Configuring ARP ACLs for Non-DHCP Environments 22-9 Limiting the Rate of Incoming ARP Packets 22-11 Performing Validation Checks 22-13 Configuring the Log Buffer 22-14 Displaying Dynamic ARP Inspection Information 23 22-15 22-4 22-7 CHAPTER Configuring Port-Based Traffic Control 23-1 Configuring Storm Control 23-1 Understanding Storm Control 23-1 Default Storm Control Configuration 23-3 Configuring Storm Control and Threshold Levels Configuring Small-Frame Arrival Rate 23-5 Configuring Protected Ports 23-6 Default Protected Port Configuration 23-6 Protected Port Configuration Guidelines 23-7 Configuring a Protected Port 23-7 Configuring Port Blocking 23-7 Default Port Blocking Configuration 23-8 Blocking Flooded Traffic on an Interface 23-8 Configuring Port Security 23-8 Understanding Port Security 23-9 Secure MAC Addresses 23-9 Security Violations 23-10 Catalyst 2960 and 2960-S Switches Software Configuration Guide.

Release 15.Contents Default Port Security Configuration 23-11 Port Security Configuration Guidelines 23-11 Enabling and Configuring Port Security 23-12 Enabling and Configuring Port Security Aging 23-17 Port Security and Switch Stacks 23-19 Configuring Protocol Storm Protection 23-19 Understanding Protocol Storm Protection 23-19 Default Protocol Storm Protection Configuration 23-20 Enabling Protocol Storm Protection 23-20 Displaying Port-Based Traffic Control Settings 24 23-21 CHAPTER Configuring UDLD 24-1 Understanding UDLD 24-1 Modes of Operation 24-1 Methods to Detect Unidirectional Links Configuring UDLD 24-3 Default UDLD Configuration 24-4 Configuration Guidelines 24-4 Enabling UDLD Globally 24-5 Enabling UDLD on an Interface 24-6 Resetting an Interface Disabled by UDLD Displaying UDLD Status 25 24-7 24-2 24-6 CHAPTER Configuring CDP 25-1 Understanding CDP 25-1 CDP and Switch Stacks 25-2 Configuring CDP 25-2 Default CDP Configuration 25-2 Configuring the CDP Characteristics 25-3 Disabling and Enabling CDP 25-3 Disabling and Enabling CDP on an Interface Monitoring and Maintaining CDP 26 25-5 25-4 CHAPTER Configuring LLDP. and Wired Location Service LLDP 26-1 LLDP-MED 26-2 Wired Location Service 26-4 26-1 26-1 Catalyst 2960 and 2960-S Switches Software Configuration Guide. and Wired Location Service Understanding LLDP. LLDP-MED.0(1)SE OL-26520-02 xxiii . LLDP-MED.

LLDP-MED. and Wired Location Service 27 CHAPTER Configuring SPAN and RSPAN 27-1 Understanding SPAN and RSPAN 27-1 Local SPAN 27-2 Remote SPAN 27-3 SPAN and RSPAN Concepts and Terminology 27-4 SPAN Sessions 27-4 Monitored Traffic 27-5 Source Ports 27-6 Source VLANs 27-7 VLAN Filtering 27-7 Destination Port 27-7 RSPAN VLAN 27-8 SPAN and RSPAN Interaction with Other Features 27-9 SPAN and RSPAN and Switch Stacks 27-10 Configuring SPAN and RSPAN 27-10 Default SPAN and RSPAN Configuration 27-10 Configuring Local SPAN 27-11 SPAN Configuration Guidelines 27-11 Creating a Local SPAN Session 27-11 Creating a Local SPAN Session and Configuring Incoming Traffic 27-14 Specifying VLANs to Filter 27-16 Configuring RSPAN 27-17 RSPAN Configuration Guidelines 27-17 Configuring a VLAN as an RSPAN VLAN 27-18 Creating an RSPAN Source Session 27-18 Creating an RSPAN Destination Session 27-20 Creating an RSPAN Destination Session and Configuring Incoming Traffic Specifying VLANs to Filter 27-22 Displaying SPAN and RSPAN Status 27-23 27-21 Catalyst 2960 and 2960-S Switches Software Configuration Guide.0(1)SE xxiv OL-26520-02 . Release 15. LLDP-MED.Contents Configuring LLDP. and Wired Location Service Default LLDP Configuration 26-5 Configuration Guidelines 26-5 Enabling LLDP 26-6 Configuring LLDP Characteristics 26-6 Configuring LLDP-MED TLVs 26-7 Configuring Network-Policy TLV 26-8 Configuring Location TLV and Wired Location Service 26-5 26-9 26-11 Monitoring and Maintaining LLDP.

Contents CHAPTER 28 Configuring RMON 28-1 28-2 Understanding RMON Configuring RMON 28-3 Default RMON Configuration 28-3 Configuring RMON Alarms and Events 28-3 Collecting Group History Statistics on an Interface 28-5 Collecting Group Ethernet Statistics on an Interface 28-6 Displaying RMON Status 29 28-6 CHAPTER Configuring System Message Logging 29-1 29-1 Understanding System Message Logging Configuring System Message Logging 29-2 System Log Message Format 29-2 Default System Message Logging Configuration 29-4 Disabling Message Logging 29-4 Setting the Message Display Destination Device 29-5 Synchronizing Log Messages 29-6 Enabling and Disabling Time Stamps on Log Messages 29-8 Enabling and Disabling Sequence Numbers in Log Messages 29-8 Defining the Message Severity Level 29-9 Limiting Syslog Messages Sent to the History Table and to SNMP 29-10 Enabling the Configuration-Change Logger 29-11 Configuring UNIX Syslog Servers 29-13 Logging Messages to a UNIX Syslog Daemon 29-13 Configuring the UNIX System Logging Facility 29-13 Displaying the Logging Configuration 30 29-14 CHAPTER Configuring SNMP 30-1 Understanding SNMP 30-1 SNMP Versions 30-2 SNMP Manager Functions 30-3 SNMP Agent Functions 30-4 SNMP Community Strings 30-4 Using SNMP to Access MIB Variables 30-5 SNMP Notifications 30-5 SNMP ifIndex MIB Object Values 30-6 Configuring SNMP 30-6 Default SNMP Configuration 30-7 Catalyst 2960 and 2960-S Switches Software Configuration Guide.0(1)SE OL-26520-02 xxv . Release 15.

Release 15.0(1)SE xxvi OL-26520-02 .Contents SNMP Configuration Guidelines 30-7 Disabling the SNMP Agent 30-8 Configuring Community Strings 30-8 Configuring SNMP Groups and Users 30-10 Configuring SNMP Notifications 30-13 Setting the CPU Threshold Notification Types and Values 30-16 Setting the Agent Contact and Location Information 30-17 Limiting TFTP Servers Used Through SNMP 30-17 SNMP Examples 30-18 Displaying SNMP Status 31 30-19 CHAPTER Configuring Network Security with ACLs 31-1 Understanding ACLs 31-2 Supported ACLs 31-2 Port ACLs 31-3 Router ACLs 31-4 Handling Fragmented and Unfragmented Traffic ACLs and Switch Stacks 31-6 31-5 Configuring IPv4 ACLs 31-6 Creating Standard and Extended IPv4 ACLs 31-7 Access List Numbers 31-8 Creating a Numbered Standard ACL 31-9 Creating a Numbered Extended ACL 31-10 Resequencing ACEs in an ACL 31-14 Creating Named Standard and Extended ACLs 31-14 Using Time Ranges with ACLs 31-16 Including Comments in ACLs 31-18 Applying an IPv4 ACL to a Terminal Line 31-19 Applying an IPv4 ACL to an Interface 31-19 Hardware and Software Treatment of IP ACLs 31-21 Troubleshooting ACLs 31-21 IPv4 ACL Configuration Examples 31-22 Numbered ACLs 31-22 Extended ACLs 31-23 Named ACLs 31-23 Time Range Applied to an IP ACL 31-23 Commented IP ACL Entries 31-24 Creating Named MAC Extended ACLs 31-24 Applying a MAC ACL to a Layer 2 Interface 31-25 Catalyst 2960 and 2960-S Switches Software Configuration Guide.

Trust. Release 15. and Classification 33-22 Auto-QoS Configuration Migration 33-22 Global Auto-QoS Configuration 33-23 Auto-QoS Generated Configuration For VoIP Devices 33-27 Auto-QoS Generated Configuration For Enhanced Video.0(1)SE OL-26520-02 33-30 xxvii . and Classify Devices Effects of Auto-QoS on the Configuration 33-32 Auto-QoS Configuration Guidelines 33-33 Auto-QoS Enhanced Considerations 33-33 Catalyst 2960 and 2960-S Switches Software Configuration Guide.Contents Displaying IPv4 ACL Configuration 32 31-27 CHAPTER Configuring Cisco IOS IP SLAs Operations 32-1 Understanding Cisco IOS IP SLAs 32-1 Using Cisco IOS IP SLAs to Measure Network Performance IP SLAs Responder and IP SLAs Control Protocol 32-4 Response Time Computation for IP SLAs 32-4 Configuring IP SLAs Operations 32-5 Default Configuration 32-5 Configuration Guidelines 32-5 Configuring the IP SLAs Responder Monitoring IP SLAs Operations 33 32-6 32-3 32-6 CHAPTER Configuring QoS 33-1 Understanding QoS 33-2 Basic QoS Model 33-3 Classification 33-5 Classification Based on QoS ACLs 33-8 Classification Based on Class Maps and Policy Maps Policing and Marking 33-9 Policing on Physical Ports 33-10 Mapping Tables 33-11 Queueing and Scheduling Overview 33-12 Weighted Tail Drop 33-13 SRR Shaping and Sharing 33-13 Queueing and Scheduling on Ingress Queues 33-14 Queueing and Scheduling on Egress Queues 33-16 Packet Modification 33-19 33-8 Configuring Auto-QoS 33-20 Generated Auto-QoS Configuration 33-20 VOIP Device Specifics 33-21 Enhanced Auto-QoS for Video. Trust.

and Marking Traffic on Physical Ports by Using Policy Maps 33-53 Classifying. Release 15. Policing. Policing. and Marking Traffic by Using Aggregate Policers 33-58 Configuring DSCP Maps 33-61 Configuring the CoS-to-DSCP Map 33-61 Configuring the IP-Precedence-to-DSCP Map 33-62 Configuring the Policed-DSCP Map 33-63 Configuring the DSCP-to-CoS Map 33-64 Configuring the DSCP-to-DSCP-Mutation Map 33-65 Configuring Ingress Queue Characteristics 33-67 Mapping DSCP or CoS Values to an Ingress Queue and Setting WTD Thresholds 33-67 Allocating Buffer Space Between the Ingress Queues 33-69 Allocating Bandwidth Between the Ingress Queues 33-69 Configuring the Ingress Priority Queue 33-70 Configuring Egress Queue Characteristics 33-71 Configuration Guidelines 33-72 Allocating Buffer Space to and Setting WTD Thresholds for an Egress Queue-Set 33-72 Mapping DSCP or CoS Values to an Egress Queue and to a Threshold ID 33-74 Configuring SRR Shaped Weights on Egress Queues 33-76 Catalyst 2960 and 2960-S Switches Software Configuration Guide.0(1)SE xxviii OL-26520-02 .Contents Enabling Auto-QoS 33-34 Troubleshooting Auto QoS Commands Displaying Auto-QoS Information 33-35 33-35 Configuring Standard QoS 33-35 Default Standard QoS Configuration 33-36 Default Ingress Queue Configuration 33-36 Default Egress Queue Configuration 33-37 Default Mapping Table Configuration 33-38 Standard QoS Configuration Guidelines 33-38 QoS ACL Guidelines 33-38 Policing Guidelines 33-39 General QoS Guidelines 33-39 Enabling QoS Globally 33-40 Configuring Classification Using Port Trust States 33-40 Configuring the Trust State on Ports Within the QoS Domain 33-40 Configuring the CoS Value for an Interface 33-42 Configuring a Trusted Boundary to Ensure Port Security 33-43 Enabling DSCP Transparency Mode 33-44 Configuring the DSCP Trust State on a Port Bordering Another QoS Domain 33-45 Configuring a QoS Policy 33-47 Classifying Traffic by Using ACLs 33-47 Classifying Traffic by Using Class Maps 33-51 Classifying.

Contents Configuring SRR Shared Weights on Egress Queues 33-77 Configuring the Egress Expedite Queue 33-78 Limiting the Bandwidth on an Egress Interface 33-78 Displaying Standard QoS Information 34 33-79 CHAPTER Configuring Static IP Unicast Routing Understanding IP Routing 34-1 Types of Routing 34-2 IP Routing and Switch Stacks Steps for Configuring Routing Enabling IP Unicast Routing Assigning IP Addresses to SVIs Configuring Static Unicast Routes 34-3 34-3 34-4 34-1 34-2 34-5 34-5 Monitoring and Maintaining the IP Network 35 CHAPTER Configuring IPv6 Host Functions 35-1 Understanding IPv6 35-1 IPv6 Addresses 35-2 Supported IPv6 Host Features 35-2 128-Bit Wide Unicast Addresses 35-3 DNS for IPv6 35-3 ICMPv6 35-3 Neighbor Discovery 35-4 First Hop Security in IPv6 35-4 IPv6 Stateless Autoconfiguration and Duplicate Address Detection IPv6 Applications 35-9 Dual IPv4 and IPv6 Protocol Stacks 35-9 onfiguring IPSec on OSPFv3SNMP and Syslog Over IPv6 35-10 HTTP(S) Over IPv6 35-11 IPv6 and Switch Stacks 35-11 Configuring IPv6 35-11 Default IPv6 Configuration 35-12 Configuring IPv6 Addressing and Enabling IPv6 Host 35-12 Configuring First Hop Security in IPv6 35-14 Configuring an IPv6 Snooping Policy 35-14 Configuring IPv6 DHCP Guard 35-16 Configuring IPv6 Source Guard 35-17 Configuration Examples for Implementing First Hop Security in IPv6 35-9 35-17 Catalyst 2960 and 2960-S Switches Software Configuration Guide. Release 15.0(1)SE OL-26520-02 xxix .

0(1)SE xxx OL-26520-02 .Contents Configuring IPv6 ICMP Rate Limiting 35-20 Configuring Static Routes for IPv6 35-21 Displaying IPv6 36 35-22 CHAPTER Configuring IPv6 MLD Snooping 36-1 Understanding MLD Snooping 36-2 MLD Messages 36-3 MLD Queries 36-3 Multicast Client Aging Robustness 36-3 Multicast Router Discovery 36-4 MLD Reports 36-4 MLD Done Messages and Immediate-Leave 36-4 Topology Change Notification Processing 36-5 MLD Snooping in Switch Stacks 36-5 Configuring IPv6 MLD Snooping 36-5 Default MLD Snooping Configuration 36-6 MLD Snooping Configuration Guidelines 36-6 Enabling or Disabling MLD Snooping 36-7 Configuring a Static Multicast Group 36-8 Configuring a Multicast Router Port 36-8 Enabling MLD Immediate Leave 36-9 Configuring MLD Snooping Queries 36-10 Disabling MLD Listener Message Suppression 36-11 Displaying MLD Snooping Information 37 36-12 CHAPTER Configuring IPv6 ACLs 37-1 Understanding IPv6 ACLs 37-1 Supported ACL Features 37-2 IPv6 ACL Limitations 37-2 Configuring IPv6 ACLs 37-3 Default IPv6 ACL Configuration 37-4 Interaction with Other Features 37-4 Creating IPv6 ACLs 37-4 Applying an IPv6 ACL to an Interface 37-7 Displaying IPv6 ACLs 38 37-8 CHAPTER Configuring EtherChannels and Link-State Tracking Understanding EtherChannels 38-1 38-1 Catalyst 2960 and 2960-S Switches Software Configuration Guide. Release 15.

and LACP Status Understanding Link-State Tracking 38-21 38-21 38-6 Configuring Link-State Tracking 38-23 Default Link-State Tracking Configuration 38-23 Link-State Tracking Configuration Guidelines 38-24 Configuring Link-State Tracking 38-24 Displaying Link-State Tracking Status 38-25 39 CHAPTER Troubleshooting 39-1 39-2 Recovering from a Software Failure Recovering from a Lost or Forgotten Password 39-3 Procedure with Password Recovery Enabled 39-4 Procedure with Password Recovery Disabled 39-6 Preventing Switch Stack Problems 39-8 Recovering from a Command Switch Failure 39-8 Replacing a Failed Command Switch with a Cluster Member 39-9 Replacing a Failed Command Switch with Another Switch 39-11 Recovering from Lost Cluster Member Connectivity 39-12 Catalyst 2960 and 2960-S Switches Software Configuration Guide. PAgP.Contents EtherChannel Overview 38-2 Port-Channel Interfaces 38-4 Port Aggregation Protocol 38-5 PAgP Modes 38-6 PAgP Interaction with Virtual Switches and Dual-Active Detection PAgP Interaction with Other Features 38-7 Link Aggregation Control Protocol 38-7 LACP Modes 38-7 LACP Interaction with Other Features 38-8 EtherChannel On Mode 38-8 Load Balancing and Forwarding Methods 38-8 EtherChannel and Switch Stacks 38-10 Configuring EtherChannels 38-11 Default EtherChannel Configuration 38-11 EtherChannel Configuration Guidelines 38-11 Configuring Layer 2 EtherChannels 38-13 Configuring EtherChannel Load Balancing 38-15 Configuring the PAgP Learn Method and Priority 38-16 Configuring LACP Hot-Standby Ports 38-18 Configuring the LACP System Priority 38-18 Configuring the LACP Port Priority 38-19 Displaying EtherChannel. Release 15.0(1)SE OL-26520-02 xxxi .

Contents Preventing Autonegotiation Mismatches 39-12 39-13 Troubleshooting Power over Ethernet Switch Ports Disabled Port Caused by Power Loss 39-13 Disabled Port Caused by False Link Up 39-13 SFP Module Security and Identification Monitoring SFP Module Status Using Ping 39-14 Understanding Ping 39-14 Executing Ping 39-15 Using Layer 2 Traceroute 39-15 Understanding Layer 2 Traceroute 39-16 Usage Guidelines 39-16 Displaying the Physical Path 39-17 Using IP Traceroute 39-17 Understanding IP Traceroute 39-17 Executing IP Traceroute 39-18 Using TDR 39-19 Understanding TDR 39-19 Running TDR and Displaying the Results 39-14 39-13 39-19 Using Debug Commands 39-20 Enabling Debugging on a Specific Feature 39-20 Enabling All-System Diagnostics 39-21 Redirecting Debug and Error Message Output 39-21 Using the show platform forward Command Using the crashinfo Files 39-23 Basic crashinfo Files 39-23 Extended crashinfo Files 39-25 Using On-Board Failure Logging 39-25 Understanding OBFL 39-25 Configuring OBFL 39-26 Displaying OBFL Information 39-26 Memory Consistency Check Routines 39-27 39-22 Troubleshooting Tables 39-28 Troubleshooting CPU Utilization 39-28 Possible Symptoms of High CPU Utilization 39-28 Verifying the Problem and Cause 39-29 Troubleshooting Power over Ethernet (PoE) 39-30 Troubleshooting Switch Stacks 39-33 Catalyst 2960 and 2960-S Switches Software Configuration Guide.0(1)SE xxxii OL-26520-02 . Release 15.

Configuration Files. Release 15.0(1)SE OL-26520-02 xxxiii .Contents CHAPTER 40 Configuring Online Diagnostics Scheduling Online Diagnostics 40-1 40-1 Understanding How Online Diagnostics Work 40-2 Configuring Health-Monitoring Diagnostics Running Online Diagnostic Tests 40-3 Starting Online Diagnostic Tests 40-3 40-2 Displaying Online Diagnostic Tests and Test Results A 40-4 APPENDIX Working with the Cisco IOS File System. and Extracting tar Files A-6 Creating a tar File A-6 Displaying the Contents of a tar File A-7 Extracting a tar File A-7 Displaying the Contents of a File A-8 A-1 A-4 Working with Configuration Files A-8 Guidelines for Creating and Using Configuration Files A-9 Configuration File Types and Location n A-10 Creating a Configuration File By Using a Text Editor A-10 Copying Configuration Files By Using TFTP A-10 Preparing to Download or Upload a Configuration File B y Using TFTP A-10 Downloading the Configuration File By Using TFTP A-11 Uploading the Configuration File By Using TFTP A-12 Copying Configuration Files By Using FTP A-12 Preparing to Download or Upload a Configuration File By Using FTP A-13 Downloading a Configuration File By Using FTP A-13 Uploading a Configuration File By Using FTP A-15 Copying Configuration Files By Using RCP A-16 Preparing to Download or Upload a Configuration File By Using RCP A-16 Downloading a Configuration File By Using RCP A-17 Uploading a Configuration File By Using RCP A-18 Clearing Configuration Information A-19 Catalyst 2960 and 2960-S Switches Software Configuration Guide. and Software Images Working with the Flash File System A-1 Displaying Available File Systems A-2 Setting the Default File System A-3 Displaying Information about Files on a File System A-3 Changing Directories and Displaying the Working Directory Creating and Removing Directories A-4 Copying Files A-5 Deleting Files A-5 Creating. Displaying.

0(1)SE xxxiv OL-26520-02 .com A-25 Copying Image Files By Using TFTP A-26 Preparing to Download or Upload an Image File By Using TFTP A-26 Downloading an Image File By Using TFTP A-27 Uploading an Image File By Using TFTP A-29 Copying Image Files By Using FTP A-29 Preparing to Download or Upload an Image File By Using FTP A-30 Downloading an Image File By Using FTP A-31 Uploading an Image File By Using FTP A-32 Copying Image Files By Using RCP A-33 Preparing to Download or Upload an Image File By Using RCP A-34 Downloading an Image File By Using RCP A-35 Uploading an Image File By Using RCP A-37 Copying an Image File from One Stack Member to Another A-38 B APPENDIX Unsupported Commands in Cisco IOS Release 15.0(2)SE B-1 Access Control Lists B-1 Unsupported Privileged EXEC Commands B-1 Unsupported Global Configuration Commands B-2 Unsupported Route-Map Configuration Commands B-2 Boot Loader Commands B-2 Unsupported Global Configuration Commands B-2 Embedded Syslog Manager B-2 Unsupported Global Configuration Commands B-2 Unsupported Privileged EXEC Commands B-2 IGMP Snooping Commands B-2 Unsupported Global Configuration Commands B-2 Interface Commands B-3 Unsupported Privileged EXEC Commands B-3 Unsupported Global Configuration Commands B-3 Catalyst 2960 and 2960-S Switches Software Configuration Guide. Release 15.Contents Clearing the Startup Configuration File A-19 Deleting a Stored Configuration File A-19 Replacing and Rolling Back Configurations A-19 Understanding Configuration Replacement and Rollback A-20 Configuration Guidelines A-21 Configuring the Configuration Archive A-22 Performing a Configuration Replacement or Rollback Operation A-23 Working with Software Images A-24 Image Location on the Switch A-25 tar File Format of Images on a Server or Cisco.

Release 15.0(1)SE OL-26520-02 xxxv .Contents Unsupported Interface Configuration Commands B-3 MAC Address Commands B-3 Unsupported Privileged EXEC Commands B-3 Unsupported Global Configuration Commands B-4 Miscellaneous B-4 Unsupported User EXEC Commands B-4 Unsupported Privileged EXEC Commands B-4 Unsupported Global Configuration Commands B-4 Network Address Translation (NAT) Commands B-4 Unsupported Privileged EXEC Commands B-4 QoS B-5 Unsupported Global Configuration Command B-5 Unsupported Interface Configuration Commands B-5 Unsupported Policy-Map Configuration Command B-5 RADIUS B-5 Unsupported Global Configuration Commands SNMP B-5 Unsupported Global Configuration Commands SNMPv3 B-6 Unsupported 3DES Encryption Commands B-6 B-5 B-5 Spanning Tree B-6 Unsupported Global Configuration Command B-6 Unsupported Interface Configuration Command B-6 VLAN B-6 Unsupported Global Configuration Command B-6 Unsupported vlan-config Command B-6 Unsupported User EXEC Commands B-6 Unsupported vlan-config Command B-7 Unsupported VLAN Database Commands B-7 VTP B-7 Unsupported Privileged EXEC Commands C B-7 APPENDIX Recommendations for Upgrading a Catalyst 2950 Switch to a Catalyst 2960 Switch Configuration Compatibility Issues Feature Behavior Incompatibilities C-1 C-5 C-1 INDEX Catalyst 2960 and 2960-S Switches Software Configuration Guide.

0(1)SE xxxvi OL-26520-02 . Release 15.Contents Catalyst 2960 and 2960-S Switches Software Configuration Guide.

depending on the switch model. and 2960-C switches run one of these images: • The LAN base software image provides enterprise-class intelligent services such as access control lists (ACLs) and quality of service (QoS) features. For example. Enter the show license privileged EXEC command. 2960-S. hereafter referred to as the switch. The line that shows the product ID also ends in either -L (if running the LAN base image) or -S (if running the LAN Lite image). Catalyst 2960. stacking is also supported. WS-C2960S-24TS-S is running LAN Lite image. Release 15. 2960-S. On the front of the switch. They do not have a FlexStack module slot on the rear of the switch. Before using this guide. The LAN Lite image provides reduced functionality. and 2960-C switch.0(1)SE OL-26520-02 xxxvii . the label in the top right corner ends in -S if the switch model runs the LAN Lite image. On a Catalyst 2960-S switch. Enter the show version privileged EXEC command. WS-C2960S-48PD-L is running LAN base. Purpose This guide provides the information that you need to configure Cisco IOS software features on your switch. • The Catalyst 2960-S ships with a universal image that includes cryptographic functionality. you should have experience working with the Cisco IOS software and be familiar with the concepts and terminology of Ethernet and local area networking. and see which is the active image: Switch# show license Index 1 Feature: lanlite Period left: 0 minute • 0 second Catalyst 2960 and 2960-S Switches Software Configuration Guide. The software image on the switch is either the LAN base or LAN Lite image. To determine which image your switch is running: • • • Switches running the LAN Lite image do not support the FlexStack module.Preface Audience This guide is for the networking professional managing the Catalyst 2960.

such as passwords or tabs. Arguments for which you supply values are in italic.Preface Index 2 Feature: lanbase Period left: Life time License Type: Permanent License State: Active.0 commands. Terminal sessions and system displays are in screen font. you might do something that could result in equipment damage or loss of data. Conventions This publication uses these conventions to convey instructions and information: Command descriptions use these conventions: • • • • • Commands and keywords are in boldface text. see the Catalyst 2960. This guide does not describe system messages you might encounter or how to install your switch. Release 15.com. Caution Means reader be careful. and 2960-C Switch Command Reference for this release. cautions. It does not provide detailed information about these commands. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Nonprinting characters. For detailed information about these commands. Interactive examples use these conventions: • • • Notes. see Getting Started with Cisco Network Assistant. see the Cisco IOS documentation set available on Cisco. Information you enter is in boldface screen font. For more information. 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. In Use License Priority: Medium License Count: Non-Counted This guide provides procedures for using the commands that have been created or changed for use with the switch. and vertical bars ( | ) separate the alternative elements. For information about the standard Cisco IOS Release 15. Braces and vertical bars within square brackets ([{ | }]) mean a required choice within an optional element. For documentation updates. the concepts in this guide are applicable to the GUI user. see the switch online help. For information about Network Assistant. Square brackets ([ ]) mean optional elements.com.0(1)SE xxxviii OL-26520-02 . see the release notes for this release. are in angle brackets (< >). Notes contain helpful suggestions or references to materials not contained in this manual. 2960-S. However. Braces ({ }) group required choices. available on Cisco. In this situation. For information about the device manager. see the appropriate system message guide and hardware installation guide. and timesavers use these conventions and symbols: Note Means reader take note.

or upgrading the switch. and 2960-C Switch Software Configuration Guide Catalyst 2960. 2960-S. see the “Downloading Software” section in the release notes. For device manager requirements. For Network Assistant requirements. 3560. see these documents: • For initial configuration information. and 2960 and 2960-S Switch System Message Guide Catalyst 3560-C and 2960-C Switch Hardware Installation Guide Catalyst 3560-C and 2960-C Switch Getting Started Guide Release Notes for the Catalyst 2960-S switches Catalyst 2960 Switch Getting Started Guide Catalyst 2960-S Switch Getting Started Guide Catalyst 3560-C and 2960-C Switch Hardware Installation Guide Catalyst 2960. 2970. 3560-C. see the “System Requirements” section in the release notes (not orderable but available on Cisco.com).com site: http://www.cisco. 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. Release 15. For cluster requirements. and 2960. 2960-S. 3560.C Switches Catalyst 3750.com). 2960. 2960.Preface Related Publications These documents provide complete information about the switch and are available from this Cisco. 3550. see the Release Notes for Cisco Network Assistant (not orderable but available on Cisco. configuring.com/en/US/products/ps6406/tsd_products_support_series_home. 2975.0(1)SE OL-26520-02 xxxix . 2960-S. and 2960-C Switch Command Reference Catalyst 2960 Switch Hardware Installation Guide Catalyst 2960-S Switch Hardware Installation Guide Catalyst 3560-C and 2960-C Switch Hardware Installation Guide Regulatory Compliance and Safety Information for the Catalyst 2960 and 2960-S Switch Regulatory Compliance and Safety Information for the Catalyst 3560-C and 2960-C Switch Catalyst 3750. • • • • See these documents for other information about the switch: • • • • • • • • • • • • • • • • • • • • • Release Notes for the Catalyst 3750. and 2960-S Switch System Message Guide Auto Smartports Configuration Guide Call Home Configuration Guide Cisco EnergyWise Configuration Guide Smart Install Configuration Guide Release Notes for Cisco Network Assistant Catalyst 2960 and 2960-S Switches Software Configuration Guide. 2975. see the Getting Started with Cisco Network Assistant (not orderable but available on Cisco. For upgrading information.com).html Note Before installing. 3560.

ht ml Obtaining Documentation. which also lists all new and revised Cisco technical documentation: http://www. see the monthly What’s New in Cisco Product Documentation. and Security Guidelines For information on obtaining documentation. Release 15.com site: http://www.html Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. Obtaining Support. Catalyst 2960 and 2960-S Switches Software Configuration Guide.cisco. see the Network Admission Control Software Configuration Guide Information about Cisco SFP. SFP+.com/en/US/products/hw/modules/ps5455/products_device_support_tables_list.com/en/US/docs/general/whatsnew/whatsnew.cisco. and GBIC modules is available from this Cisco. submitting a service request.html SFP compatibility matrix documents are available from this Cisco.0(1)SE xl OL-26520-02 .0.cisco.Preface • • • • • • • Getting Started with Cisco Network Assistant Cisco CWDM GBIC and CWDM SFP Installation Note Cisco RPS 300 Redundant Power System Hardware Installation Guide Cisco RPS 675 Redundant Power System Hardware Installation Guide Cisco Redundant Power System 2300 Hardware Installation Guide For information about the Network Admission Control (NAC) features.com/en/US/products/hw/modules/ps5455/prod_installation_guides_list. and gathering additional information. The RSS feeds are a free service and Cisco currently supports RSS version 2.com site: http://www.

page 1-25 Unless otherwise noted. page 1-13 Power over Ethernet Features. page 1-8 VLAN Features. page 1-19 Where to Go Next. • • • • • • • • • • Ease-of-Deployment and Ease-of-Use Features. page 1-5 Manageability Features. 2960-S and 2960-C switch software: • • • • Features. page 1-2 Performance Features. Features The switch supports a LAN base image or a LAN lite image with a reduced feature set. page 1-6 Availability and Redundancy Features. In this document. page 1-15 Monitoring Features. Release 15. page 1-1 Default Settings After Initial Switch Configuration. page 1-10 QoS and CoS Features.CH A P T E R 1 Overview This chapter provides these topics about the Catalyst 2960.0(1)SE OL-26520-02 1-1 . IP refers to IP Version 4 (IPv4) unless there is a specific reference to IP Version 6 (IPv6). page 1-4 Management Options. the term switch refers to a standalone switch and to a switch stack. page 1-16 Network Configuration Examples. page 1-15 Catalyst 2960 and 2960-S Switches Software Configuration Guide. page 1-9 Security Features. depending on switch hardware.

you can configure ACLs. – Simplifying and minimizing switch. Cisco Network Assistant (hereafter referred to as Network Assistant) for – Managing communities. see the getting started guide. and Simple Network Management Protocol (SNMP) information through a browser-based program. and security. – Configuration wizards that prompt you to provide only the minimum required information to configure complex features such as QoS priorities for traffic. except that they can contain • • • routers and access points and can be made more secure. • Cisco FlexStack technology on Catalyst 2960-S switches running the LAN base image for – Connecting up to four switches through their FlexStack ports to operate as a single switch in the network. – Creating a bidirectional 32-Gb/s switching fabric across the switch stack. For more information about the device manager. Catalyst 2960 and 2960-S Switches Software Configuration Guide. switch stack. – Monitoring real-time status of a switch or multiple switches from the LEDs on the front-panel images. and port LED colors on the images are similar to those used on the physical LEDs. see the getting started guide. Note If the switch is running the LAN Lite image. redundant power system (RPS). and switch cluster management from anywhere in your intranet. such as VLAN and QoS settings. which are device groups like clusters. – Accomplishing multiple configuration tasks from a single graphical interface without needing to remember command-line interface (CLI) commands to accomplish specific tasks. but you cannot attach them to interfaces or VLANs. For more information about Express Setup. For information about launching the device manager.0(1)SE 1-2 OL-26520-02 . An embedded device manager GUI for configuring and monitoring a single switch through a web browser. switch and Telnet passwords. priority levels for data applications. inventory and statistic reports. – Applying actions to multiple ports and multiple switches at the same time.Chapter 1 Features Overview Ease-of-Deployment and Ease-of-Use Features • Express Setup for quickly configuring a switch for the first time with basic IP information. the switch must be running the LAN Base image. Release 15.com/go/cna. User-defined and Cisco-default Smartports macros for creating custom switch configurations for simplified deployment across the network. – Downloading an image to a switch. and quality of service (QoS). – Interactive guide mode that guides you in configuring complex features such as VLANs. ACLs.and switch-level monitoring and troubleshooting. The system. The Network Assistant must be downloaded from cisco. see the switch online help. contact information. Note To use the RPS. – 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. link. where all stack members have full access to the system bandwidth. and multiple switch software upgrades.

– Automatic Cisco IOS version-check of new stack members with the option to automatically load images from the stack master or from a TFTP server. cluster-capable switches. and software upgrade of multiple. increased device visibility. Gigabit Ethernet. and IP phones. Catalyst 2960 and 2960-S Switches Software Configuration Guide. small form-factor pluggable (SFP) modules. with all stack members having full access to the system bandwidth. The switch stack retains this information across stack reloads whether or not the provisioned switch is part of the stack. – Automatic discovery of candidate switches and creation of clusters of up to 16 switches that can be managed through a single IP address. EtherChannels. Fast EtherChannel. For more information. authentication. Release 15. – Using a single IP address and configuration file to manage the entire switch stack.0(1)SE OL-26520-02 1-3 . The device classifier is enabled by default. – Extended discovery of cluster candidates that are not directly connected to the command switch. MAC address and OUI-based triggers. including Ethernet. You can configure in advance the interface configuration for a specific stack member number and for a specific switch type of a new switch that is not part of the stack. see the Cisco Smart Install Configuration Guide. LLDP-based triggers. • Smart Install to allow a single point of management (director) in a network. remote macros as well as for automatic configuration based on these two new device types: Cisco Digital Media Player (Cisco DMP) and Cisco IP Video Surveillance Camera (Cisco IPVSC). • Switch clustering technology for – Unified configuration. – Displaying stack-ring activity statistics (the number of frames sent by each stack member to the ring). You can use Smart Install to provide zero touch image and configuration upgrade of newly deployed switches and image and configuration downloads for any client switches. access points. and enhanced macro management. – Enhancements to add support for global macros. and can classify devices based on DHCP options. and replacing switches in the stack without disrupting the operation of the stack.Chapter 1 Overview Features – Creating a bidirectional 20-Gb/s switching fabric across the switch stack. – Adding. removing. For a list of cluster-capable switches. regardless of their geographic proximity and interconnection media. – Improved device classification capabilities and accuracy. Fast Ethernet. – Auto Smartports enhancement to enable auto-QoS on a CDP-capable Cisco digital media player. last-resort macros. see the Auto Smartports Configuration Guide. monitoring. • • Stack troubleshooting enhancements Auto Smartports – Cisco-default and user-defined macros for dynamic port configuration based on the device type detected on the port. event trigger control. see the release notes. and Gigabit EtherChannel connections. – Provisioning a new member for a switch stack with the offline configuration feature. auto-QoS with Cisco Medianet. – Enhancements to add support for macro persistency. For information.

SFP+ support for 10Gigabit speeds (Catalyst 2960-S only) 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. Users with a service contract directly with Cisco Systems can register Call Home devices for the Cisco Smart Call Home service that generates automatic service requests with the Cisco TAC. Port Aggregation Protocol (PAgP) and Link Aggregation Control Protocol (LACP) for automatic creation of EtherChannel links. automatic generation of the image list file. see the Cisco EnergyWise documentation on Cisco. and unicast storms. and upgrade status. Per-port storm control for preventing broadcast. hostname changes. 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. to remove selected clients from the director database. multicast.0(1)SE 1-4 OL-26520-02 . and to provide more information about client devices. 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).com.5 enhancements that add support for a query to analyze and display domain information and for Wake on LAN (WoL) to remotely power on a WoL-capable PC. – Smart Install enhancements in Cisco IOS Release 12.2(58)SE including the ability to manually change a client switch health state from denied to allowed or hold for on-demand upgrades. including device status.3x flow control on all ports (the switch does not send pause frames). multicast. For more information. health status. Release 15. 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. Internet Group Management Protocol (IGMP) snooping for IGMP Versions 1. IGMP snooping querier support to configure switch to generate periodic IGMP general query messages. transparent connection of the director to client. zero-touch replacement for clients with the same product-ID. and bridged broadcast traffic. Up to 20 Gb/s of forwarding rates in a Catalyst 2960-S switch stack. EnergyWise Phase 2. and servers. • • • • • • • • • • • • Catalyst 2960 and 2960-S Switches Software Configuration Guide. • Call Home to provide e-mail-based and web-based notification of critical system events. 2. and USB storage for image and seed configuration. Performance Features • • • • Cisco EnergyWise manages the energy usage of endpoints connected to domain members. Port blocking on forwarding unknown Layer 2 unknown unicast. Forwarding of Layer 2 packets at Gigabit line rate across the switches in the stack. routers. configurable file repository. Autosensing of port speed and autonegotiation of duplex mode on all switch ports for optimizing bandwidth. to allow simultaneous on-demand upgrade of multiple clients.Chapter 1 Features Overview – Smart Install enhancements supporting client backup files.

the switch must be running the LAN Base image. For information about launching the device manager. Note • • • • • • To use MVR. RADIUS server load balancing to allow access and authentication requests to be distributed evenly across a server group. 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. Network Assistant—Network Assistant is a network management application that can be downloaded from Cisco. Configurable small-frame arrival threshold to prevent storm control when small frames (64 bytes or less) arrive on an interface at a specified rate (the threshold). Flex Link Multicast Fast Convergence to reduce the multicast traffic convergence time after a Flex Link failure. Release 15. available on Cisco.com. IGMP throttling for configuring the action when the maximum number of entries is in the IGMP forwarding table.Chapter 1 Overview Features • • 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 Note • To use IPv6 features. by connecting your PC directly to the Ethernet management port.and multilayer-switching features. Support for QoS marking of CPU-generated traffic and queue CPU-generated traffic on the egress network ports. see the switch online help. You use it to manage a single switch.com. or a community of devices. You can access the CLI by connecting your management station directly to the switch console port. You use it to configure and to monitor a single switch. IGMP filtering for controlling the set of multicast groups to which hosts on a switch port can belong. Management Options • An embedded device manager—The device manager is a GUI that is integrated in the software image.0(1)SE OL-26520-02 1-5 . see Getting Started with Cisco Network Assistant. 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. Memory consistency check routines to detect and correct invalid ternary content addressable memory (TCAM) table entries. For more information about the device manager. Note • • • To use Flex Link Multicast Fast Convergence. see the getting started guide. the switch must be running the LAN Base image. or by using Telnet from a remote management • • Catalyst 2960 and 2960-S Switches Software Configuration Guide. a cluster of switches. For more information about Network Assistant. CLI—The Cisco IOS software supports desktop. the switch must be running the LAN Base image.

0(1)SE 1-6 OL-26520-02 . The switch supports a comprehensive set of MIB extensions and four remote monitoring (RMON) groups. Catalyst 2960 and 2960-S Switches Software Configuration Guide. including IP address requests. from DHCP clients DHCP server for automatic assignment of IP addresses and other DHCP options to IP hosts DHCP-based autoconfiguration and image update to download a specified configuration a new image to a large number of switches DHCP server port-based address allocation for the preassignment of an IP address to a switch port 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 Configurable MAC address scaling that allows disabling MAC address learning on a VLAN to limit the size of the MAC address table Cisco Discovery Protocol (CDP) Versions 1 and 2 for network topology discovery and mapping between the switch and other Cisco devices on the network Link Layer Discovery Protocol (LLDP) and LLDP Media Endpoint Discovery (LLDP-MED) for interoperability with third-party IP phones LLDP media extensions (LLDP-MED) location TLV that provides location information from the switch to the endpoint device • • • • • • Note To use LLDP-MED. You can automate initial configurations and configuration updates by generating switch-specific configuration changes.” • SNMP—SNMP management applications such as CiscoWorks2000 LAN Management Suite (LMS) and HP OpenView. see Chapter 4. For more information about CNS. “Configuring SNMP. default gateway. hostname. sending them to the switch. Release 15. executing the configuration change. You can manage the switch stack by connecting to the console port or Ethernet management port of any stack member. “Using the Command-Line Interface. configuration storage. see Chapter 30. You can manage from an SNMP-compatible management station that is running platforms such as HP OpenView or SunNet Manager. For more information about using SNMP. “Configuring Cisco IOS Configuration Engine.Chapter 1 Features Overview station or PC. the switch must be running the LAN Base image. see Chapter 2.” • Manageability Features • • • • • • • CNS embedded agents for automating switch management.” Cisco IOS Configuration Engine (previously known to as the Cisco IOS CNS agent)-—Configuration service automates the deployment and management of network devices and services. and Domain Name System [DNS] and TFTP server names) DHCP relay for forwarding User Datagram Protocol (UDP) broadcasts. and logging the results. For more information about the CLI. and delivery DHCP for automating configuration of switch information (such as IP address.

Catalyst 2960 and 2960-S Switches Software Configuration Guide. CPU utilization threshold trap monitors CPU utilization Note To use CPU utilization. In-band management access through SNMP Versions 1. Wired location service sends location and attachment tracking information for connected devices to a Cisco Mobility Services Engine (MSE) • • • • • • • Note • To use wired location. 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 Out-of-band management access through the Ethernet management port to a PC (Catalyst 2960-only) 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) for both IPv4 and IPv6 Configuration replacement and rollback to replace the running configuration on a switch with any saved Cisco IOS configuration file The HTTP client in Cisco IOS supports can send requests to both IPv4 and IPv6 HTTP server. 2c. subnet.0(1)SE OL-26520-02 1-7 . and site addressing changes.Chapter 1 Overview Features • • • • • • • • • • • • • • Support for CDP and LLDP enhancements for exchanging location information with video end points for dynamic location-based content distribution from servers Network Time Protocol (NTP) version 4 for NTP time synchronization for both IPv4 and IPv6 Cisco IOS File System (IFS) for providing a single interface to all file systems that the switch uses 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. the switch must be running the LAN Base image. and the HTTP server in Cisco IOS can service HTTP requests from both IPv4 and IPv6 HTTP clients Simple Network and Management Protocol (SNMP) can be configured over IPv6 transport so that an IPv6 host can send SNMP queries and receive SNMP notifications from a device running IPv6 IPv6 stateless autoconfiguration to manage link. the switch must be running the LAN Base image. Support for IPv6 Host on the LAN Base and LAN Lite image (Catalyst 2960 and 2960-S). such as management of host and mobile IP addresses Disabling MAC address learning on a VLAN DHCP server port-based address allocation for the preassignment of an IP address to a switch port. encrypted Secure Shell (SSH) connections for multiple CLI-based sessions over the network Support for SSH for IPv6. Release 15.

1w Rapid Spanning Tree Protocol (RSTP) for rapid convergence of the spanning tree by immediately changing root and designated ports to the forwarding state Catalyst 2960 and 2960-S Switches Software Configuration Guide. Console input is active on only one port at a time.0(1)SE 1-8 OL-26520-02 . (Catalyst 2960-S only) USB Type A port for external Cisco USB flash memory devices (thumb drives or USB keys). Support for including a hostname in the option 12 field of DHCPDISCOVER packets. based on the power policy TLV request USB mini-Type B console port in addition to the standard RJ-45 console port. cross-stack UplinkFast. (Catalyst 2960-S only) Availability and Redundancy Features • Automatic stack master re-election for replacing stack masters that become unavailable (failover support) The newly elected stack master begins accepting Layer 2 traffic in less than 1 second and Layer 3 traffic between 3 to 5 seconds. erase. and BackboneFast for fast convergence after a spanning-tree topology change and for achieving load balancing between redundant uplinks. length. You can use standard Cisco CLI commands to read. including Gigabit uplinks and cross-stack Gigabit uplinks • IEEE 802.2(55)SE and later. or boot from the flash memory. class of service (CoS).1D Spanning Tree Protocol (STP) for redundant backbone connections and loop-free networks. Release 15. • • • Cross-stack EtherChannel for providing redundant links across the switch stack 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. value (TLV) for creating a profile for voice and voice-signalling by specifying the values for VLAN. This provides identical configuration files to be sent by using the DHCP protocol DHCP Snooping enhancement to support the selection of a fixed string-based format for the circuit-id sub-option of the Option 82 DHCP field Increased support for LLPD-MED by allowing the switch to grant power to the power device (PD). STP has these features: – Up to 128 spanning-tree instances supported Note Up to 64 spanning-tree instances are supported when the switch is running the LAN Lite image. copy. differentiated services code point (DSCP). and tagging mode Note • • • • • Supported on all images in Cisco IOS Release 12. – 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.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. write.Chapter 1 Features Overview • LLDP-MED network-policy profile time.

0(1)SE OL-26520-02 1-9 . Support for VLAN IDs in the 1 to 4094 range as allowed by the IEEE 802. rapid-PVST+. adds.1Q trunking encapsulation on all ports for network moves. and bandwidth Note • • • Up to 64 VLANs are supported when the switch is running the LAN Lite image. VLAN Features • Support for up to 255 VLANs for assigning users to VLANs associated with appropriate network resources. Release 15.1Q standard VLAN Query Protocol (VQP) for dynamic VLAN membership IEEE 802. the switch must be running the LAN Base image.Chapter 1 Overview Features • Optional spanning-tree features available in 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 Note • To use Flex Links.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 • • • Catalyst 2960 and 2960-S Switches Software Configuration Guide. Note To use Link-state Tracking. and changes. the switch must be running the LAN Base image. 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. Link-state tracking to mirror the state of the ports that carry upstream traffic from connected hosts and servers. traffic patterns. and to allow the failover of the server traffic to an operational link on another Cisco Ethernet switch. management and control of broadcast and multicast traffic.

The switch CPU continues to send and receive control protocol frames. no user traffic is sent or received on the trunk. VTP primary and secondary servers.Chapter 1 Features Overview • 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. the switch must be running the LAN Base image. enhanced authentication (hidden or secret passwords).1x functionality to be authenticated using a web browser Note • • To use Web Authentication. and resulting actions Static MAC addressing for ensuring security Protected port option for restricting the forwarding of traffic to designated ports on the same switch Port security option for limiting and identifying MAC addresses of the stations allowed to access the port VLAN aware port security option to shut down the VLAN on the port when a violation occurs. Password-protected access (read-only and read-write access) to management interfaces (device manager. Network Assistant. Local web authentication banner so that a custom banner or an image file can be displayed at a web authentication login screen IEEE 802. the switch must be running the LAN Base image.1x authentication with restricted VLANs (also known as authentication failed VLANs) Support for VTP version 3 that includes support for configuring extended range VLANs (VLANs 1006 to 4094) in any VTP mode. notification. With this feature enabled. Release 15. • Note • • To use VLAN Flex Link Load Balancing. VLAN Flex Link Load Balancing to provide Layer 2 redundancy without requiring Spanning Tree Protocol (STP). Port security aging to set the aging time for secure addresses on a port Protocol storm protection to control the rate of incoming protocol traffic to a switch by dropping packets that exceed a specified ingress rate.1x Authentication with ACLs and the RADIUS Filter-Id Attribute Note • To use this feature. the switch must be running the LAN Base image. A pair of interfaces configured as primary and backup links can load balance traffic based on VLAN. Support for 802. and the CLI) for protection against unauthorized configuration changes Multilevel security for a choice of security level.0(1)SE 1-10 OL-26520-02 . and the option to turn VTP on or off by port Security Features • Web authentication to allow a supplicant (client) that does not support IEEE 802. BPDU guard for shutting down a Port Fast-configured port when an invalid configuration occurs • • • • • • • • Catalyst 2960 and 2960-S Switches Software Configuration Guide. propagation of other databases in addition to VTP. instead of shutting down the entire port.

such as an IP phone (Cisco or non-Cisco).1x port-based authentication to prevent unauthorized devices (clients) from gaining access to the network. the switch must be running the LAN Base image.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.1x-authenticated users to a specified VLAN – Support for VLAN assignment on a port configured for multi-auth mode.1x compliant.1x accounting to track network usage – 802.1x on the switch Catalyst 2960 and 2960-S Switches Software Configuration Guide. Note To use this feature.1x-compliant users – Restricted VLAN to provide limited services to users who are 802. – Dynamic voice virtual LAN (VLAN) for MDA to allow a dynamic voice VLAN on an MDA-enabled port – VLAN assignment for restricting 802.0(1)SE OL-26520-02 1-11 .1x with wake-on-LAN to allow dormant PCs to be powered on based on the receipt of a specific Ethernet frame – 802. and subsequent hosts use the same VLAN. – 802.1x readiness check to determine the readiness of connected end hosts before configuring IEEE 802. – Port security for controlling access to 802.1x-enabled switch port Note To use MDA. These features are supported: – Multidomain authentication (MDA) to allow both a data device and a voice device. but do not have the credentials to authenticate via the standard 802.Chapter 1 Overview Features • • • • • • • 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 IP source guard to restrict traffic on nonrouted interfaces by filtering traffic based on the DHCP snooping database and IP source bindings Dynamic ARP inspection to prevent malicious attacks on the switch by not relaying invalid ARP requests and responses to other ports in the same VLAN IEEE 802. Voice VLAN assignment is supported for one IP phone. the switch must be running the LAN Base image. The RADIUS server assigns a VLAN to the first host to authenticate on the port. the switch must be running the LAN Base image. to independently authenticate on the same IEEE 802. – Guest VLAN to provide limited services to non-802.1x processes Note To use authentication with restricted VLANs. Release 15.

– Flexible-authentication sequencing to configure the order of the authentication methods that a port tries when authenticating a new host. Note To use this feature. host authorization with CISP. Note To use NAC. Note To use MAC authentication bypass.1x validation. • • • • TACACS+. the switch must be running the LAN Base image. encryption. TACACS+. • • Catalyst 2960 and 2960-S Switches Software Configuration Guide.1x validation of the antivirus condition or posture of endpoint systems or clients before granting the devices network access. the switch must be running the LAN Base image. the switch must be running the LAN Base image. – Network Edge Access Topology (NEAT) with 802. the switch must be running the LAN Base image.1x authentication. – IEEE 802. Note To use voice aware 802.0 support for the HTTP 1.1x readiness check. – MAC authentication bypass to authorize clients based on the client MAC address.0(1)SE 1-12 OL-26520-02 .1x Authentication with ACLs and the RADIUS Filter-Id Attribute Support for IP source guard on static hosts. and tracking the actions of remote users through authentication. – IEEE 802. Secure Socket Layer (SSL) Version 3.1x authentication with downloadable ACLs and redirect URLs to allow per-user ACL downloads from a Cisco Secure ACS server to an authenticated switch.Chapter 1 Features Overview Note To use 802. a proprietary feature for managing network security through a TACACS server for both IPv4 and IPv6 RADIUS for verifying the identity of. see the “Network Admission Control Layer 2 802. and auto enablement to authenticate a switch outside a wiring closet as a supplicant to another switch.1x with open access to allow a host to access the network before being authenticated. For information about configuring NAC Layer 2 802.1X switch supplicant. and message integrity and HTTP client authentication to allow secure HTTP communications (requires the cryptographic version of the software) IEEE 802. – Multiple-user authentication to allow more than one host to authenticate on an 802. and SSH to function over IPv6.1x-enabled port. – Voice aware 802. Release 15. – Network Admission Control (NAC) Layer 2 802. – Support for dynamic creation or attachment of an auth-default ACL on a port that has no configured static ACLs. the switch must be running the LAN Base image. and accounting (AAA) services for both IPv4 and IPv6 Enhancements to RADIUS.1x security to apply traffic violation actions only on the VLAN on which a security violation occurs.1 server authentication. granting access to.1x Validation” section on page 10-31. authorization.

and TCP/UDP headers) for high-performance quality of service at the network edge. MAC move to allow hosts (including the hosts connected behind an IP phone) to move across ports within the same switch without any restrictions to enable mobility. – IP ToS/DSCP and IEEE 802. With MAC move. such as Cisco Secure ACS to reinitialize authentication. the switch must be running the LAN Base image. failure and expire web pages for local web authentication. assigned by RADIUS server. allowing for differentiated service levels for different types of network traffic and for prioritizing mission-critical traffic in the network Catalyst 2960 and 2960-S Switches Software Configuration Guide. and 256-bit Advanced Encryption Standard (AES) encryption algorithms to SNMPv3. Support for 3DES and AES with version 3 of the Simple Network Management Protocol (SNMPv3). • • • • • • • QoS and CoS Features • Automatic QoS (auto-QoS) to simplify the deployment of existing QoS features by classifying traffic and configuring egress queues Note • • To use auto-QoS. Release 15. the port is placed in a critical VLAN in order to still permit access to critical resources.1p CoS marking priorities on a per-port basis for protecting the performance of mission-critical applications Note To use DSCP. Authorized users are assigned to the least populated VLAN in the group. This release adds support for the 168-bit Triple Data Encryption Standard (3DES) and the 128-bit. When there is a change in policy for a user or user group in AAA. 192-bit. VLAN-ID based MAC authentication to use the combined VLAN and MAC address information for user authentication to prevent network access from unauthorized VLANs. and an AAA server becomes unreachable.1x User Distribution to allow deployments with multiple VLANs (for a group of users) to improve scalability of the network by load balancing users across different VLANs.1p CoS marking based on flow-based packet classification (classification based on information in the MAC. IEEE 802. the switch must be running the LAN Base image.Chapter 1 Overview Features • RADIUS Change of Authorization (CoA) to change the attributes of a certain session after it is authenticated. success. Customizable web authentication enhancement to allow the creation of user-defined login. Support for critical VLAN with multiple-host authentication so that when a port is configured for multi-auth. Support for Network Edge Access Topology (NEAT) to change the port host mode and to apply a standard port configuration on the authenticator switch port. and apply to the new policies. administrators can send the RADIUS CoA packets from the AAA server. Cross-stack QoS for configuring QoS features to all switches in a switch stack rather than on an individual-switch basis Classification – IP type-of-service/Differentiated Services Code Point (IP ToS/DSCP) and IEEE 802. the switch treats the reappearance of the same MAC address on another port in the same way as a completely new MAC address. IP.0(1)SE OL-26520-02 1-13 .

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 Catalyst 2960 and 2960-S Switches Software Configuration Guide. Note • Ingress queueing is not supported on Catalyst 2960-S switches.0(1)SE 1-14 OL-26520-02 . trusting the CoS value received. the Catalyst 2960 switch must be running the LAN Base image. the switch must be running the LAN Base image. Policing Note To use policy maps. 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 Note To use WTD. Release 15.Chapter 1 Features Overview Note To use flow-based packet classification. – Trusted port states (CoS. Each second-level policy map can have a different policer. the switch must be running the LAN Base image. each class map can be associated with its own port-level (second-level) policy map. – Aggregate policing for policing traffic flows in aggregate to restrict specific applications or traffic flows to metered. – Shaped round robin (SRR) as the scheduling service for specifying the rate at which packets are sent to the stack ring (sharing is the only supported mode on ingress queues) Note To use ingress queueing. DSCP. and ensuring port security Note • To use trusted boundary. the switch must be running the LAN Base image – Traffic-policing policies on the switch port for managing how much of the port bandwidth should be allocated to a specific traffic flow – If you configure multiple class maps for a hierarchical policy map. 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. the switch must be running the LAN Base image.

IPv6 default router preference (DRP) for improving the ability of a host to select an appropriate router (requires the LAN Base image) Power over Ethernet Features • Ability to provide power to connected Cisco pre-standard and IEEE 802. but can use more than the guarantee if other queues become empty and do not use their share of the bandwidth.and switch-level status Switch LEDs that provide port-.3at.4 W per port to 30 W per port (Catalyst 2960-S only) Support for CDP with power consumption. (PoE+) that increases the available power that can be drawn by powered devices from 15. the switch supports static routing and router ACLs on SVIs (supported only on switches running the LAN base image). the switch senses the total power consumption. Shaped egress queues are guaranteed but limited to using a share of port bandwidth. the switch maintains a power budget. Shared egress queues are also guaranteed a configured share of bandwidth. Note • To use egress queueing. such as the Cisco Telepresence System and Cisco Surveillance Camera. and grants power only when it is available. • • • • • Monitoring Features • • • Switch LEDs that provide port. and stack-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 Catalyst 2960 and 2960-S Switches Software Configuration Guide. Support for IEEE 802. Release 15. Note To use Auto-QoS enhancements. switch-. The powered device notifies the switch of the amount of power it is consuming. Auto-QoS enhancements that add automatic configuration classification of traffic flow from video devices.0(1)SE OL-26520-02 1-15 . the switch must be running the LAN Base image. Support for Cisco intelligent power management. and reports the power usage. Automatic detection and power budgeting.3af-compliant powered devices from Power over Ethernet (PoE)-capable ports if the switch detects that there is no power on the circuit. The powered device and the switch negotiate through power-negotiation CDP messages for an agreed power-consumption level. On a per-PoE port basis. the switch must be running the LAN Base image. Ability to monitor the real-time power consumption. monitors and tracks requests for power. Layer 3 Features • • When you configure the lanbase-routing SDM template. polices the power usage. The negotiation allows a high-power Cisco powered device to operate at its highest power mode.Chapter 1 Overview Features – 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).

Chapter 1 Default Settings After Initial Switch Configuration Overview • • • • • • • • • • 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.” Default domain name is not configured. If you do not configure the switch at all. repel. statistics. the switch must be running the LAN Base image.” and Chapter 20. alarms. For more information. modules. Release 15. “Assigning the Switch IP Address and Default Gateway. and default gateway is 0. see the hardware installation guide. subnet mask.0. the switch operates with these default settings: • Default switch IP address. On-board failure logging (OBFL) to collect information about the switch and the power supplies connected to it (Catalyst 2960-S only) IP Service Level Agreements (IP SLAs) responder support that allows the switch to be a target device for IP SLAs active traffic monitoring Note To use IP SLAs. resource issues. “Assigning the Switch IP Address and Default Gateway. 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. and report network security violations Four groups (history.” • Catalyst 2960 and 2960-S Switches Software Configuration Guide.0.0(1)SE 1-16 OL-26520-02 . see the getting started guide. and switch while the switch is connected to a live network(Catalyst 2960-S only). “Configuring DHCP and IP Source Guard Features. see Chapter 3. 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 Generic online diagnostics to test hardware functionality of the supervisor engine. For more information. For information about assigning an IP address by using the CLI-based setup program. Note For information about assigning an IP address by using the browser-based Express Setup program. see Chapter 3. Default Settings After Initial Switch Configuration The switch is designed for plug-and-play operation. you can change the interface-specific and system. and events) of embedded RMON agents for network monitoring and traffic analysis Syslog facility for logging system messages about authentication or authorization errors.and stack-wide settings.0.

Chapter 1 Overview Default Settings After Initial Switch Configuration • DHCP client is enabled. For more information. “Configuring Switch-Based Authentication.” • • • • STP. For more information. For more information. “Configuring STP.” DNS is enabled. “Clustering Switches. For more information. For more information. For more information.” – Voice VLAN is disabled. “Configuring DHCP and IP Source Guard Features.” IEEE 802. For more information. see • • • • • • • • • • • • VLANs – Default VLAN is VLAN 1. “Configuring Switch-Based Authentication.” Switch stack is enabled (not configurable). see – PoE is autonegotiate. see Chapter 5.” Switch cluster is disabled. For more information.” – VLAN trunking setting is dynamic auto (DTP).” RADIUS is disabled. see Chapter 10. “Configuring IEEE 802. the DHCP server is enabled (only if the device acting as a DHCP server is configured and is enabled). see Chapter 18. see Chapter 13. For more information.” Catalyst 2960 and 2960-S Switches Software Configuration Guide. For more information. “Configuring MSTP. see Chapter 14. For more information.com. “Configuring VTP. see Chapter 6. see – Flow control is off.0(1)SE OL-26520-02 1-17 . “Administering the Switch. Release 15.” and Chapter 20. see Chapter 5. see Chapter 9.” – Trunk encapsulation is negotiate. For more information.” – VTP mode is server.” NTP is enabled. For more information.1x Port-Based Authentication. see Chapter 3. see Chapter 14. For more information. see Chapter 9. and the DHCP relay agent is enabled (only if the device is acting as a DHCP relay agent is configured and is enabled). “Assigning the Switch IP Address and Default Gateway. see Chapter 13. “Configuring VLANs. For more information. For more information. “Configuring Switch-Based Authentication. see Chapter 9. “Configuring Voice VLAN. see Chapter 7. see Chapter 5. “Configuring VLANs. see Chapter 17. see – Auto-MDIX is enabled.” Optional spanning-tree features are disabled. available on Cisco. “Administering the Switch. For more information. see Chapter 19.” The standard HTTP server and Secure Socket Layer (SSL) HTTPS server are both enabled. see Chapter 16.1x is disabled.” and the Getting Started with Cisco Network Assistant. For more information. see Chapter 13. “Configuring Optional Spanning-Tree Features. see Chapter 15. For more information about switch clusters. “Configuring VTP.” MSTP is disabled. “Configuring VLANs.” System name and prompt is Switch. “Managing Switch Stacks. “Administering the Switch. For more information. PVST+ is enabled on VLAN 1. For more information. For more information. For more information. “Administering the Switch. For more information. No passwords are defined.” Flex Links are not configured. “Configuring Flex Links and the MAC Address-Table Move Update Feature. see Chapter 5. For more information.” – VTP version is Version 1.” Port parameters – Interface speed and duplex mode is autonegotiate.” TACACS+ is disabled.

“Configuring SPAN and RSPAN. see Chapter 27. see Chapter 23. “Configuring UDLD.” • • • CDP is enabled.” IGMP snooping is enabled. No IGMP filters are applied.” Dynamic ARP inspection is disabled on all VLANs. For more information. For more information. see Chapter 23. and unicast storm control is disabled. see Chapter 20. “Configuring Port-Based Traffic Control. “Configuring IGMP Snooping and MVR.” – No protected ports are defined. see Chapter 20.” No ACLs are configured.” IP source guard is disabled. Release 15. For more information. For more information.” SNMP is enabled (Version 1). “Configuring DHCP and IP Source Guard Features. “Configuring Port-Based Traffic Control. For more information. For more information.” Note • • • • To use RSPAN. For more information. “Configuring Network Security with ACLs.” MVR is disabled.” Syslog messages are enabled and appear on the console. see Chapter 24.” Note • To use MVR.” – No secure ports are configured.” SPAN and RSPAN are disabled. “Configuring Port-Based Traffic Control.” IGMP throttling setting is deny. For more information. For more information. the switch must be running the LAN Base image. Port-based traffic – Broadcast. “Configuring Port-Based Traffic Control. For more information. For more information. see Chapter 21. DHCP snooping is disabled. “Configuring System Message Logging. see Chapter 23. multicast. “Configuring IGMP Snooping and MVR. “Configuring IGMP Snooping and MVR.” – Unicast and multicast traffic flooding is not blocked.” DHCP server port-based address allocation is disabled. For more information. see Chapter 20. For more information. see Chapter 30.” Catalyst 2960 and 2960-S Switches Software Configuration Guide. see Chapter 28. For more information.0(1)SE 1-18 OL-26520-02 . see Chapter 29. “Configuring IGMP Snooping and MVR. see Chapter 21. the switch must be running the LAN Base image. see Chapter 21.Chapter 1 Default Settings After Initial Switch Configuration Overview Note • • • • • • • • To use Flex Links. “Configuring DHCP and IP Source Guard Features. For more information. the switch must be running the LAN Base image. For more information. “Configuring Dynamic ARP Inspection. see Chapter 23. “Configuring CDP. see Chapter 31. The DHCP snooping information option is enabled. “Configuring DHCP and IP Source Guard Features.” The IGMP snooping querier feature is disabled. For more information. For more information. For more information. see Chapter 22. RMON is disabled. “Configuring RMON. “Configuring SNMP.” UDLD is disabled. see Chapter 25. see Chapter 21.

High-Bandwidth Transport Configuration” section on page 1-24 Design Concepts for Using the Switch As your network users compete for network bandwidth. application prioritization. For more information.0(1)SE OL-26520-02 1-19 . multimedia integration.Chapter 1 Overview Network Configuration Examples • • QoS is disabled. Table 1-1 Increasing Network Performance Network Demands Too many users on a single network segment and a growing number of users accessing the Internet • • Suggested Design Methods • Create smaller network segments so that fewer users share the bandwidth. 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. 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. it takes longer to send and receive data. Table 1-2 describes some network demands and how you can meet them.” No EtherChannels are configured. As your network traffic profiles evolve.” 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. see Chapter 38. • • • “Design Concepts for Using the Switch” section on page 1-19 “Small to Medium-Sized Network Using Catalyst 2960. Use full-duplex operation between the switch and its connected workstations. “Configuring EtherChannels and Link-State Tracking. 2960-S and 2960-C Switches” section on page 1-23 “Long-Distance. consider providing network services that can support applications for voice and data integration. Use the EtherChannel feature between the switch and its connected servers and routers. workstations. • Increased power of new PCs. “Configuring QoS. consider the bandwidth required by your network users and the relative priority of the network applications that they use. For more information. see Chapter 33. and use VLANs and IP subnets to place the network resources in the same logical network as the users who access those resources most. When you configure your network. and security. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Release 15. and servers High bandwidth demand from networked applications (such as e-mail with large attached files) and from bandwidth-intensive applications (such as multimedia) • • Bandwidth alone is not the only consideration when designing your network.

Stacking is supported only on Catalyst 2960-S switches running the LAN base image. If one of the redundant Catalyst 2960 and 2960-S Switches Software Configuration Guide.1p/Q. You can have redundant uplink connections. See the documentation sets specific to these switches for LRE information. using SFP modules in the switch stack to a Gigabit backbone switch. marking.Chapter 1 Network Configuration Examples Overview Table 1-2 Providing Network Services Network Demands Efficient bandwidth usage for multimedia applications and guaranteed bandwidth for critical applications Suggested Design Methods • • Use IGMP snooping to efficiently forward multimedia and multicast traffic. and enable either cross-stack Etherchannel or cross-stack UplinkFast. • High demand on network redundancy and availability to provide always on mission-critical applications • Note • • High demand on network redundancy and availability to provide always on mission-critical applications An evolving demand for IP telephony • • • • A growing demand for using existing infrastructure to transport data and voice from a home or office to the Internet or an intranet at higher speeds Use the Catalyst Long-Reach Ethernet (LRE) switches to provide up to 15 Mb of IP connectivity over existing infrastructure. To preserve switch connectivity if one switch in the stack fails. You can use the switches and switch stacks to create the following: • Cost-effective wiring closet (Figure 1-1)—A cost-effective way to connect many users to the wiring closet is to have a switch stack of up to four Catalyst 2960-S switches. and multicast and multimedia applications. All stack members have synchronized copies of the saved and running configuration files of the switch stack. thereby providing maximum flexibility and support for mission-critical. You can also create backup paths by using Fast Ethernet. Use switch stacks. LRE is the technology used in the Catalyst 2900 LRE XL and Catalyst 2950 LRE switches. Use cross-stack EtherChannels for providing redundant links across the switch stack.0(1)SE 1-20 OL-26520-02 . where all stack members are eligible stack masters in case of stack-master failure. Note Note To use LRE. Use VLAN trunks. scheduling. Use other QoS mechanisms such as packet classification. the switch must be running the LAN Base image. connect the switches as recommended in the hardware installation guide. Use QoS to prioritize applications such as IP telephony during congestion and to help control both delay and jitter within the network. such as a Catalyst 4500 or Catalyst 3750-12S Gigabit switch. cross-stack UplinkFast. Use voice VLAN IDs (VVIDs) to provide separate VLANs for voice traffic. and congestion avoidance to classify traffic with the appropriate priority level. Gigabit. such as existing telephone lines. unicast. 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. Use MVR to continuously send multicast streams in a multicast VLAN but to isolate the streams from subscriber VLANs for bandwidth and security reasons. based on IEEE 802. Use switches that support at least two queues per port to prioritize voice and data traffic as either high. The switch supports at least four queues per port. or EtherChannel links. 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.or low-priority. Release 15.

where the switch is connected to Catalyst 3750 switches in the distribution layer. use QoS DSCP marking priorities on these switches. Using SFP modules also provides flexibility in media and distance options through fiber-optic connections.0(1)SE OL-26520-02 250870 1-21 . the other can serve as a backup path. Release 15. The first illustration is of an isolated high-performance workgroup. The second illustration is of a high-performance workgroup in a branch office. Each switch in this configuration provides users with a dedicated 1-Gb/s connection to network resources. Figure 1-1 Cost-Effective Wiring Closet Gigabit server Catalyst Gigabit Ethernet multilayer switch Si Catalyst 2975 switch stack • Cost-effective Gigabit-to-the-desktop for high-performance workgroups (Figure 1-2)—For high-speed access to network resources. you can use the Catalyst 2960 switch in the access layer to provide Gigabit Ethernet to the desktop. If the Gigabit switch is cluster-capable. Catalyst 2960 and 2960-S Switches Software Configuration Guide. you can configure it and the switch stack as a switch cluster to manage them through a single IP address. To prevent congestion. The Gigabit switch can be connected to a Gigabit server through a 1000BASE-T connection. Note Stacking is supported only on Catalyst 2960-S switches running the LAN base image.Chapter 1 Overview Network Configuration Examples connections fails. connect the switches in the access layer to a Gigabit multilayer switch with routing capability. For high-speed IP forwarding at the distribution layer. such as a Catalyst 3750 switch. or to a router. where the stack is connected to a router in the distribution layer.

which have redundant Gigabit EtherChannels and cross-stack EtherChannels. Catalyst 2960 and 2960-S Switches Software Configuration Guide. The Gigabit interconnections minimize latency in the data flow.0(1)SE 1-22 89374 89373 OL-26520-02 . connect the switches in the access layer to multilayer switches with routing capability. For high-speed IP forwarding at the distribution layer. QoS and policing on the switches provide preferential treatment for certain data streams.Chapter 1 Network Configuration Examples Overview Figure 1-2 High-Performance Workgroup (Gigabit-to-the-Desktop) Catalyst 3750 switches Access-layer Catalyst switches WAN Cisco 2600 router Access-layer Catalyst switches • Server aggregation (Figure 1-3)—You can use the switches and switch stacks to interconnect groups of servers. Fault tolerance from the server racks to the core is achieved through dual homing of servers connected to dual switch stacks. Using SFP modules provides flexibility in media and distance options through fiber-optic connections. centralizing physical security and administration of your network. Release 15. Using dual SFP module uplinks from the switches provides redundant uplinks to the network core. They segment traffic streams into different paths for processing. Security features on the switch ensure rapid handling of packets.

and Cisco SoftPhone software integrates telephony and IP networks. ranging from 0. and Cisco IP Phone features and configuration. The server farm includes a call-processing server running Cisco CallManager software. VLAN access control lists (VLAN maps) on the stack provide intra-VLAN security and prevent unauthorized users from accessing critical areas of the network. This ensures connectivity to the Internet. Users with workstations running Cisco SoftPhone software can place. a router or Layer 3 switch routes the traffic to the destination VLAN. Data and multimedia traffic are configured on the same VLAN. only one VLAN can be configured per wiring closet. the routers are providing inter-VLAN routing. This network uses a switch stack with high-speed connections to two routers. Voice traffic from the Cisco IP Phones are configured on separate VVIDs. Cisco CallManager controls call processing. and control calls from their PCs. The switches are interconnected through Gigabit interfaces. Cisco CallManager controls call processing. If congestion occurs. Catalyst 2960 and 2960-S Switches Software Configuration Guide.Chapter 1 Overview Network Configuration Examples The various lengths of stack cable available. WAN. routing. and mission-critical network resources if one of the routers fails. Figure 1-3 Server Aggregation Campus core Catalyst 6500 switches Catalyst 3750 StackWise switch stacks Access-layer Catalyst switches 89376 Server racks Small to Medium-Sized Network Using Catalyst 2960. In addition to inter-VLAN routing. routing. the multilayer switches or routers provide QoS mechanisms such as DSCP priorities to prioritize the different types of network traffic and to deliver high-priority traffic. and voice traffic are assigned to the same VLAN. QoS drops low-priority traffic to allow delivery of high-priority traffic. The switch stack uses cross-stack EtherChannel for loading sharing.0(1)SE OL-26520-02 1-23 . When an end station in one VLAN needs to communicate with an end station in another VLAN. and Cisco IP Phone features and configuration. Cisco CallManager software.5 meter to 3 meters provide extended connections to the switch stacks across multiple server racks. for multiple stack aggregation. The switches are connected to workstations and local servers. If data. Release 15. and the IP network supports both voice and data. Using Cisco IP Phones. multimedia. 2960-S and 2960-C Switches Figure 1-4 shows a configuration for a network of up to 500 employees. This network uses VLANs to logically segment the network into well-defined broadcast groups and for security management. receive. In this network.

The CWDM OADM modules combine (or multiplex) the different CWDM wavelengths. High-Bandwidth Transport Configuration Note To use CWDM SFPs. The CWDM SFP modules connect to CWDM optical add/drop multiplexer (OADM) modules over distances of up to 393. Figure 1-4 Collapsed Backbone Configuration Internet Cisco 2600 or 3700 routers Gigabit servers Cisco IP phones Workstations running Cisco SoftPhone software Aironet wireless access points Long-Distance. the farther the transmission can travel.Chapter 1 Network Configuration Examples Overview The routers also provide firewall services. data is sent at wavelengths from 1470 to 1610 nm.5 miles or 120 km). Release 15. and WAN and Internet access. A common wavelength used for long-distance transmissions is 1550 nm. Depending on the CWDM SFP module.0(1)SE 1-24 101388 IP IP OL-26520-02 . voice-over-IP (VoIP) gateway services. Network Address Translation (NAT) services. 2960-S or 2960-C switches have coarse wavelength-division multiplexing (CWDM) fiber-optic SFP modules installed. Figure 1-5 shows a configuration for sending 8 Gigabits of data over a single fiber-optic cable. allowing them to travel simultaneously on the same fiber-optic cable. Catalyst 2960 and 2960-S Switches Software Configuration Guide. The Catalyst 2960. For more information about the CWDM SFP modules and CWDM OADM modules. The CWDM OADM modules on the receiving end separate (or demultiplex) the different wavelengths. see the Cisco CWDM GBIC and CWDM SFP Installation Note.701 feet (74. The higher the wavelength. the switch must be running the LAN Base image.

Release 15.shtml. review these sections for startup information: • • Chapter 2.com/public/sw-center/netmgmt/cmtk/mibs. use the Cisco MIB Locator: http://cisco. “Using the Command-Line Interface” Chapter 3. Catalyst 2960 and 2960-S Switches Software Configuration Guide.0(1)SE OL-26520-02 1-25 . “Assigning the Switch IP Address and Default Gateway” To locate and download MIBs for a specific Cisco product and release.Chapter 1 Overview Where to Go Next Figure 1-5 Long-Distance. High-Bandwidth Transport Configuration Where to Go Next Before configuring the switch.

Release 15.Chapter 1 Where to Go Next Overview Catalyst 2960 and 2960-S Switches Software Configuration Guide.0(1)SE 1-26 OL-26520-02 .

Unless otherwise noted. which show the current configuration status. page 2-9 Accessing the CLI. the term switch refers to a standalone switch and to a switch stack. page 2-4 Using Command History. you must enter privileged EXEC mode. Normally. Enter a question mark (?) at the system prompt to obtain a list of commands available for each command mode. 2960-SC or 2960-S switch. you can enter any privileged EXEC command or enter global configuration mode. To access the various configuration modes. page 2-5 Using Editing Features. If you save the configuration. you begin in user mode. For example. most of the user EXEC commands are one-time commands. The commands available to you depend on which mode you are currently in. page 2-4 Using Configuration Logging. Catalyst 2960 and 2960-S Switches Software Configuration Guide. and clear commands. From this mode.CH A P T E R 2 Using the Command-Line Interface This chapter describes the Cisco IOS command-line interface (CLI) and how to use it to configure your 2960. page 2-4 Understanding CLI Error Messages. often called user EXEC mode. which clear counters or interfaces. such as show commands. these commands are stored and used when the switch reboots. To have access to all commands. Only a limited subset of the commands are available in user EXEC mode. and line). When you start a session on the switch. Release 15. • • • • • • • • • • Understanding Command Modes. From global configuration mode. interface. you must enter a password to enter privileged EXEC mode. The user EXEC commands are not saved when the switch reboots. page 2-1 Understanding the Help System. you can make changes to the running configuration. you can enter interface configuration mode and line configuration mode. page 2-9 Understanding Command Modes The Cisco IOS user interface is divided into many different modes. page 2-6 Searching and Filtering Output of show and more Commands.0(1)SE OL-26520-02 2-1 . Using the configuration modes (global. page 2-3 Understanding no and default Forms of Commands. page 2-3 Understanding Abbreviated Commands. you must start at global configuration mode.

the prompt you see in that mode. Catalyst 2960 and 2960-S Switches Software Configuration Guide. see the “Configuring a Range of Interfaces” section on page 12-19. Display system information. Prompt Switch> Exit Method Enter logout or quit. Ctrl-Z. enter parameters that apply to the exit or end. Switch(config-if)# Use this mode to configure To exit to global configuration mode. To return to privileged EXEC mode. enter the exit command. or press entire switch. The examples in the table use the hostname Switch. Perform basic tests. and how to exit the mode. Use this mode to configure VLAN parameters. Release 15.0(1)SE 2-2 OL-26520-02 . you can create extended-range VLANs (VLAN IDs greater than 1005) and save configurations in the switch startup configuration file. To configure multiple interfaces with the same parameters. VLAN configuration Interface configuration While in global configuration mode. Use this mode to verify commands that you have entered. mode. Privileged EXEC Switch# While in user EXEC mode. About This Mode Use this mode to • • • Change terminal settings. press Ctrl-Z or enter end. Global configuration While in privileged Switch(config)# EXEC mode. see the “Using Interface Configuration Mode” section on page 12-17. enter the configure command. press Ctrl-Z or enter end. Enter disable to exit. For information about defining interfaces. line with the To return to line vty or line privileged EXEC console command. parameters for the Ethernet ports. enter exit. press Ctrl-Z or enter end. Use a password to protect access to this mode. Switch(config-vlan)# To exit to privileged Use this mode to configure EXEC mode. To return to privileged EXEC mode. how to access each one. To exit to global configuration mode. Line configuration Switch(config-line)# To exit to global While in global Use this mode to configure configuration configuration mode. enter the interface command (with a specific interface). mode. specify a enter exit. enter the vlan vlan-id command. Table 2-1 Command Mode Summary Mode User EXEC Access Method Begin a session with your switch. enter the enable command. When VTP mode is transparent.Chapter 2 Understanding Command Modes Using the Command-Line Interface Table 2-1 describes the main command modes. parameters for the terminal line. While in global configuration mode.

Release 15. 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. Obtain a list of commands that begin with a particular character string. For example: Switch# di? dir disable disconnect abbreviated-command-entry<Tab> Complete a partial command name. For example: Switch> show ? command keyword ? List the associated arguments for a keyword. This example shows how to enter the show configuration privileged EXEC command in an abbreviated form: Switch# show conf Catalyst 2960 and 2960-S Switches Software Configuration Guide.Chapter 2 Using the Command-Line Interface Understanding the Help System For more detailed information on the command modes. as shown in Table 2-2. For example: Switch# sh conf<tab> Switch# show configuration ? List all commands available for a particular command mode. For example: Switch> ? command ? List the associated keywords for a command.0(1)SE OL-26520-02 2-3 . see the command reference guide for this release. For example: Switch(config)# cdp holdtime ? <10-255> Length of time (in sec) that receiver must keep this packet Understanding Abbreviated Commands You need to enter only enough characters for the switch to recognize the command as unique. Table 2-2 Help Summary Command help abbreviated-command-entry? Purpose Obtain a brief description of the help system in any command mode.

The default form of a command returns the command setting to its default. Using Configuration Logging You can log and view changes to the switch configuration. Use the command without the keyword no to re-enable a disabled feature or to enable a feature that is disabled by default. You did not enter all the keywords or Re-enter the command followed by a question mark (?) values required by this command. so the default form is the same as the no form. Release 15. with a space between the command and the question mark. the user who entered the command. the time that the Catalyst 2960 and 2960-S Switches Software Configuration Guide. The possible keywords that you can enter with the command appear.0(1)SE 2-4 OL-26520-02 . the no shutdown interface configuration command reverses the shutdown of an interface. The logger tracks each configuration command that is applied. In these cases. You entered the command incorrectly. the default command enables the command and sets variables to their default values. The caret (^) marks the point of the error. some commands are enabled by default and have variables set to certain default values. Enter a question mark (?) to display all the commands that are available in this command mode. Most commands are disabled by default. % Incomplete command. However. For example. You can use the Configuration Change Logging and Notification feature to track changes on a per-session and per-user basis. In general. The possible keywords that you can enter with the command appear. Configuration commands can also have a default form.Chapter 2 Understanding no and default Forms of Commands Using the Command-Line Interface Understanding no and default Forms of Commands Almost every configuration command also has a no form. use the no form to disable a feature or function or reverse the action of a command. Table 2-3 Common CLI Error Messages Error Message % Ambiguous command: "show con" Meaning You did not enter enough characters for your switch to recognize the command. Understanding CLI Error Messages Table 2-3 lists some error messages that you might encounter while using the CLI to configure your switch. % Invalid input detected at ‘^’ marker. How to Get Help 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.

Release 15. You can choose to have the notifications sent to the syslog. 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. 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. The command history feature is particularly useful for recalling long or complex commands or entries. Using Command History The software provides a history or record of commands that you have entered.com/en/US/docs/ios/fundamentals/configuration/guide/cf_config-logger_ps6350_TS D_Products_Configuration_Guide_Chapter.0(1)SE OL-26520-02 2-5 . including access lists. see the Configuration Change Notification and Logging feature module: http://www.html Note Only CLI or HTTP changes are logged.cisco. 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. Catalyst 2960 and 2960-S Switches Software Configuration Guide. This feature includes a mechanism for asynchronous notification to registered applications whenever the configuration changes. Beginning in privileged EXEC mode. These procedures are optional. page 2-6 (optional) Changing the Command History Buffer Size By default. and the parser return code for the command.Chapter 2 Using the Command-Line Interface Using Command History command was entered. page 2-5 (optional) Recalling Commands. page 2-6 (optional) Disabling the Command History Feature. Beginning in line configuration mode. For more information. You can customize this feature to suit your needs as described in these sections: • • • Changing the Command History Buffer Size.

Return to more recent commands in the history buffer after recalling commands with Ctrl-P or the up arrow key. The number of commands that appear is controlled by the setting of the terminal history global configuration command and the history line configuration command. These procedures are optional. Release 15. beginning with the most recent command. page 2-8 (optional) Enabling and Disabling Editing Features Although enhanced editing mode is automatically enabled. Result Recall commands in the history buffer. You can disable it for the current terminal session or for the command line. These procedures are optional. Table 2-4 Recalling Commands Action1 Press Ctrl-P or the up arrow key. The arrow keys function only on ANSI-compatible terminals such as VT100s. Press Ctrl-N or the down arrow key. Using Editing Features This section describes the editing features that can help you manipulate the command line. show history 1. enter the no history line configuration command. Repeat the key sequence to recall successively older commands. While in privileged EXEC mode. enter the terminal no history privileged EXEC command. enter this command in line configuration mode: Switch (config-line)# no editing Catalyst 2960 and 2960-S Switches Software Configuration Guide.0(1)SE 2-6 OL-26520-02 . To globally disable enhanced editing mode. perform one of the actions listed in Table 2-4. Repeat the key sequence to recall successively more recent commands.Chapter 2 Using Editing Features Using the Command-Line Interface Recalling Commands To recall commands from the history buffer. To disable the feature during the current terminal session. It contains these sections: • • • Enabling and Disabling Editing Features. you can disable it. To disable command history for the line. re-enable it. These actions are optional. page 2-7 (optional) Editing Command Lines that Wrap. list the last several commands that you just entered. Disabling the Command History Feature The command history feature is automatically enabled. page 2-6 (optional) Editing Commands through Keystrokes. or configure a specific line to have enhanced editing.

Press Esc Y. Delete from the cursor to the end of the word. Table 2-5 Editing Commands through Keystrokes Capability Move around the command line to make changes or corrections. Press Ctrl-F. Backspace key. paste them in the command line. Press Esc B. Recall commands from the buffer and Press Ctrl-Y. Press Ctrl-A. Press Esc F.Chapter 2 Using the Command-Line Interface Using Editing Features To re-enable the enhanced editing mode for the current terminal session. Recall the next buffer entry.0(1)SE OL-26520-02 2-7 . left arrow key. you cycle to the first buffer entry. These keystrokes are optional. Erase the character to the left of the cursor. Move the cursor back one word. or press the right arrow key. Press Esc C. or press the Move the cursor back one character. Press Ctrl-W. Press Ctrl-K. Move the cursor to the end of the command line. Move the cursor forward one character. Move the cursor forward one word. If you press Esc Y more than ten times. Keystroke1 Purpose Press Ctrl-B. enter this command in privileged EXEC mode: Switch# terminal editing To reconfigure a specific line to have enhanced editing mode. Press Ctrl-E. Recall the most recent entry in the buffer. Release 15. Delete the word to the left of the cursor. 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. Delete the character at the cursor. The switch provides a buffer with the last ten items that you deleted. Capitalize or lowercase words or capitalize a set of letters. Delete all characters from the cursor to the end of the command line. Press Esc D. Press Ctrl-D. Delete all characters from the cursor to the beginning of the command line. Capitalize at the cursor. Move the cursor to the beginning of the command line. Press Ctrl-T. Transpose the character to the left of the cursor with the character located at the cursor. Press Ctrl-U or Ctrl-X. Delete entries if you make a mistake Press the Delete or or change your mind. The buffer contains only the last 10 items that you have deleted or cut. Catalyst 2960 and 2960-S Switches Software Configuration Guide.

2.5 255.1. Note Press the Return key. You can also press Ctrl-A to immediately move to the beginning of the line.Chapter 2 Using Editing Features Using the Command-Line Interface Table 2-5 Editing Commands through Keystrokes (continued) Capability Keystroke1 Press Esc L.255.0(1)SE 2-8 OL-26520-02 . Press Ctrl-L or Ctrl-R.0 131.5 255.255. To scroll back to the beginning of the command entry. Each time the cursor reaches the end of the line.1$ Catalyst 2960 and 2960-S Switches Software Configuration Guide. but you can scroll back and check the syntax at the beginning of the command. an executable command.255.0 131. Scroll down one screen.2.0 131. 1. In this example.108.255.255.25 $t tcp 131.5 255.108.255. 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. Release 15. Redisplay the current command line if the switch suddenly sends a message to your screen. Purpose Change the word at the cursor to lowercase.0 eq 45 After you complete the entry. The keystroke actions are optional. Press the Space bar.20 255.255. When the cursor first reaches the end of the line.108.108. Switch(config)# Switch(config)# Switch(config)# Switch(config)# access-list 101 permit tcp 131.255. The arrow keys function only on ANSI-compatible terminals such as VT100s. the line is shifted ten spaces to the left and redisplayed. perhaps as a shortcut. You can use the Return and Space bar keystrokes whenever you see the More prompt.255.108.5 255.1 $ 101 permit tcp 131.5 255. You cannot see the first ten characters of the line.108.2.2. Editing Command Lines that Wrap You can use a wraparound feature for commands that extend beyond a single line on the screen. including show command output. The dollar sign ($) shows that the line has been scrolled to the left. The More prompt is used for any output that has more lines than can be displayed on the terminal screen.0 131. The arrow keys function only on ANSI-compatible terminals such as VT100s.255.255. Scroll down a line or screen on displays that are longer than the terminal screen can display.108.2.255. Press Esc U. press Ctrl-B or the left arrow key repeatedly. Capitalize letters from the cursor to the end of the word.0 131.20 255.1. Scroll down one line.255.255. the command line shifts ten spaces to the left.20 255.0 eq $108. Redisplay the current command line.108.108. Designate a particular keystroke as Press Ctrl-V or Esc Q.1. the line is again shifted ten spaces to the left. When the cursor reaches the right margin. the access-list global configuration command entry extends beyond one line. press Ctrl-A to check the complete syntax before pressing the Return key to execute the command.

Be careful with using multiple CLI sessions to the stack master. 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. If you want to configure a specific stack member port. and where the system prompt for the stack master is Switch. To use this functionality. you can access it from the stack master by using the session stack-member-number privileged EXEC command. For example. For more information about interface notations. Commands you enter in one session are not displayed in the other sessions. 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. You cannot manage stack members on an individual switch basis. and an expression that you want to search for or filter out: command | {begin | include | exclude} regular-expression Expressions are case sensitive. You manage the switch stack and the stack member interfaces through the stack master. For example. Using these commands is optional. Note Stacking is supported only on Catalyst 2960-S switches running the LAN base image. You can connect to the stack master through the console port of one or more stack members. through Telnet.Chapter 2 Using the Command-Line Interface Searching and Filtering Output of show and more Commands The software assumes you have a terminal screen that is 80 columns wide. Release 15. one of the keywords begin. use the terminal width privileged EXEC command to set the width of your terminal. the lines that contain output are not displayed. enter a show or more command followed by the pipe character (|). Note We recommend using one CLI session when managing the switch stack. or exclude. Catalyst 2960 and 2960-S Switches Software Configuration Guide. For information about recalling previous command entries. include. line protocol is up Vlan10 is up. it is possible to lose track of the session from which you entered commands. If you have a width other than that. The stack member number is appended to the system prompt. Switch-2# is the prompt in privileged EXEC mode for stack member 2. Therefore.0(1)SE OL-26520-02 2-9 . but the lines that contain Output appear. Use line wrapping with the command history feature to recall and modify previous complex command entries. see the “Editing Commands through Keystrokes” section on page 2-7. Only the show and debug commands are available in a CLI session to a specific stack member. you must include the stack member number in the CLI command interface notation. see the “Using Interface Configuration Mode” section on page 12-17. To debug a specific stack member. or by using the browser. if you enter | exclude output. Searching and Filtering Output of show and more Commands You can search and filter the output for show and more commands. line protocol is down Accessing the CLI You can access the CLI through a console connection.

you can access the CLI through a local console connection or through a remote Telnet session. Then. you must connect a terminal or PC to the switch console port and power on the switch. The switch supports up to five simultaneous secure SSH sessions. to understand the boot process and the options available for assigning IP information. For information about configuring the switch for SSH. The switch must have network connectivity with the Telnet or SSH client.” If your switch is already configured. and the switch must have an enable secret password configured. 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. see the “Setting a Telnet Password for a Terminal Line” section on page 9-6. the user EXEC prompt appears on the management station. “Assigning the Switch IP Address and Default Gateway. For information about connecting to the console port. For information about configuring the switch for Telnet access. The switch supports up to 16 simultaneous Telnet sessions. see the “Configuring the Switch for Secure Shell” section on page 9-41. see Chapter 3.0(1)SE 2-10 OL-26520-02 . For more information. see the “Setting a Telnet Password for a Terminal Line” section on page 9-6. but your switch must first be configured for this type of access. as described in the getting started guide that shipped with your switch. Use any Telnet TCP/IP or encrypted Secure Shell (SSH) package from a remote management station. Catalyst 2960 and 2960-S Switches Software Configuration Guide. After you connect through the console port. Changes made by one Telnet user are reflected in all other Telnet sessions. through a Telnet session or through an SSH session.Chapter 2 Accessing the CLI Using the Command-Line Interface Accessing the CLI through a Console Connection or through Telnet Before you can access the CLI. Release 15. see the switch getting started guide or hardware installation guide.

default gateway. Loads a default operating system software image into memory and boots up the switch. and launch the operating system. which control where physical memory is mapped. page 3-15 Modifying the Startup Configuration. • • • • • Understanding the Boot Process. It initializes the CPU registers. Performs power-on self-test (POST) for the CPU subsystem. and so forth.com page. its speed.CH A P T E R 3 Assigning the Switch IP Address and Default Gateway Note This chapter describes how to create the initial switch configuration (for example. page 3-17 Scheduling a Reload of the Software Image. see the command reference for this release and the Cisco IOS IP Command Reference. page 3-1 Assigning Switch Information. The boot loader provides access to the flash file system before the operating system is loaded. page 3-2 Checking and Saving the Running Configuration. assigning the IP address and default gateway information) for the Catalyst switch by using a variety of automatic and manual methods.0(1)SE OL-26520-02 3-1 . subnet mask. which performs these activities: • • • Performs low-level CPU initialization. The normal boot process involves the operation of the boot loader software. It also describes how to modify the switch startup configuration. For complete syntax and usage information for the commands used in this chapter. secret and Telnet passwords. the boot loader is used only to load. It tests the CPU DRAM and the portion of the flash device that makes up the flash file system. Catalyst 2960 and 2960-S Switches Software Configuration Guide. After the boot loader gives the operating system control of the CPU. its quantity. page 3-21 Understanding the Boot Process To start your switch. Release 15. Normally. the boot loader is not active until the next system reset or power-on. and so forth). Volume 1 of 3: Addressing and Services from Cisco. you need to follow the procedures in the Getting Started Guide or the hardware installation guide for installing and powering on the switch and for setting up the initial switch configuration (IP address. uncompress.

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. For more information. you can format the flash file system. recover from a lost or forgotten password. Use a DHCP server for centralized control and automatic assignment of IP information after the server is configured. set the parity option to none. Assigning Switch Information You can assign IP information through the switch setup program. see the hardware installation guide. 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. reinstall the operating system software image by using the Xmodem Protocol. you can also configure a hostname and an enable secret password. Note • • If the data bits option is set to 8. see the “Disabling Password Recovery” section on page 9-5.0(1)SE 3-2 OL-26520-02 . see the “Recovering from a Software Failure” section on page 39-2 and the “Recovering from a Lost or Forgotten Password” section on page 39-3. Note If you are using DHCP. For more information. make sure you have connected a PC or terminal to the console port. Note You can disable password recovery. Parity settings default is none. Release 15. Use the switch setup program if you want to be prompted for specific IP information. use the setup program described previously. manually configure the switch. Data bits default is 8. page 3-3 Understanding DHCP-Based Autoconfiguration. through a DHCP server. Stop bits default is 1. The trap-door mechanism provides enough access to the system so that if it is necessary. Otherwise. page 3-3 Manually Assigning IP Information. For more information about the setup program. With this program. Before you can assign switch information. or manually. page 3-14 Catalyst 2960 and 2960-S Switches Software Configuration Guide. If you are an experienced user familiar with the switch configuration steps. 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.Chapter 3 Assigning Switch Information Assigning the Switch IP Address and Default Gateway The boot loader also provides trap-door access into the system if the operating system has problems serious enough that it cannot be used. • • • Default Switch Information. and finally restart the operating system.

The DHCP server for your switch can be on the same LAN or on a different LAN than the switch. A router does not forward broadcast packets. Catalyst 2960 and 2960-S Switches Software Configuration Guide. A relay device forwards broadcast traffic between two directly connected LANs. your switch (DHCP client) is automatically configured at startup with IP address information and a configuration file.Chapter 3 Assigning the Switch IP Address and Default Gateway Assigning Switch Information Default Switch Information Table 3-1 shows the default switch information. but it forwards packets based on the destination IP address in the received packet. With DHCP-based autoconfiguration. No default gateway is defined. Table 3-1 Default Switch Information Feature IP address and subnet mask Default gateway Enable secret password Hostname Telnet password Cluster command switch functionality Cluster name Default Setting No IP address or subnet mask are defined. The factory-assigned default hostname is Switch. 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. Disabled. During DHCP-based autoconfiguration. If the DHCP server is running on a different LAN. No password is defined. Understanding DHCP-Based Autoconfiguration DHCP provides configuration information to Internet hosts and internetworking devices. The switch can act as both a DHCP client and a DHCP server. DHCP is built on a client-server model.0(1)SE OL-26520-02 3-3 . No password is defined. DHCP Client Request Process When you boot up your switch. you should configure a DHCP relay device between your switch and the DHCP server. the DHCP client is invoked and requests the IP address information for those interfaces. However. no DHCP client-side configuration is needed on your switch. Release 15. you might also need to configure a Trivial File Transfer Protocol (TFTP) server and a Domain Name System (DNS) server. in which designated DHCP servers allocate network addresses and deliver configuration parameters to dynamically configured devices. you need to configure the DHCP server for various lease options associated with IP addresses. the DHCP client is invoked and requests configuration information from a DHCP server when the configuration file is not present on the switch. DHCP-based autoconfiguration replaces the BOOTP client functionality on your switch. If you are using DHCP to relay the configuration file location on the network. If the configuration file is present and the configuration includes the ip address dhcp interface configuration command on specific routed interfaces. No cluster name is defined.

a lease for the IP address. the client returns a formal request for the offered configuration information to the DHCP server. the client accepts the DHCP hostname option and sets the flag to show that the system now has a hostname configured. However. broadcasts a DHCPDISCOVER message to locate a DHCP server. if the client receives the DCHP hostname option from the DHCP interaction while acquiring an IP address for an interface.0(1)SE 3-4 OL-26520-02 . Switch A. the DHCP hostname option is not included in the packet when you enter the ip address dhcp interface configuration command. Release 15. the client and server are bound. If a client has a default hostname (the hostname name global configuration command is not configured or the no hostname global configuration command is entered to remove the hostname). The DHCP server offers configuration parameters (such as an IP address. The DHCP server sends the client a DHCPNAK denial broadcast message. subnet mask. The DHCP hostname option allows a group of switches to obtain hostnames and a standard configuration from the central management DHCP server. In this case. the switch broadcasts. The amount of information the switch receives depends on how you configure the DHCP server. that an error has occurred during the negotiation of the parameters. gateway IP address. see the “Configuring the TFTP Server” section on page 3-7. If the switch accepts replies from a BOOTP server and configures itself. (The DHCP server assigned the parameters to another client. The offer from the DHCP server is not a guarantee that the IP address is allocated to the switch. DNS IP address. or that the client has been slow in responding to the DHCPOFFER message. The DHCP server confirms that the IP address has been allocated to the client by returning a DHCPACK unicast message to the client. instead of unicasts.) A DHCP client might receive offers from multiple DHCP or BOOTP servers and can accept any of the offers. For more information. the client returns a DHCPDECLINE broadcast message to the DHCP server. If the configuration parameters sent to the client in the DHCPOFFER unicast message are invalid (a configuration error exists). Catalyst 2960 and 2960-S Switches Software Configuration Guide. the client usually accepts the first offer it receives. A client (switch) includes in its DCHPDISCOVER message an option 12 field used to request a hostname and other configuration parameters from the DHCP server. Figure 3-1 DHCP Client and Server Message Exchange DHCPDISCOVER (broadcast) Switch A DHCPOFFER (unicast) DHCPREQUEST (broadcast) 51807 DHCP server DHCPACK (unicast) The client. however. 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.Chapter 3 Assigning Switch Information Assigning the Switch IP Address and Default Gateway Figure 3-1 shows the sequence of messages that are exchanged between the DHCP client and the DHCP server. and so forth) to the client in a DHCPOFFER unicast message. and the client uses configuration information received from the server. which means that the offered configuration parameters have not been assigned. TFTP requests to obtain the switch configuration file. the server usually reserves the address until the client has had a chance to formally request the address. In a DHCPREQUEST broadcast message. With this message. The configuration files on all clients are identical except for their DHCP-obtained hostnames.

It does not over write the bootup configuration saved in the flash. DHCP Autoconfiguration DHCP autoconfiguration downloads a configuration file to one or more switches in your network from a DHCP server. the TFTP server where the image and configuration files are located must be configured with the correct option 67 (the configuration filename). The downloaded configuration file is saved in the running configuration of the switch. DHCP Auto-Image Update You can use DHCP auto-image upgrade with DHCP autoconfiguration to download both a configuration and a new image to one or more switches in your network. This helps ensure that each new switch added to a network receives the same image and configuration. the configuration is stored in the saved configuration on the switch. After you install the switch in your network. the auto-image update feature starts. Release 15. The switch (or switches) downloading the new configuration and the new image can be blank (or only have a default factory configuration loaded). the DHCP-based autoconfiguration with a saved configuration feature tries indefinitely to download an IP address. see the “Configuring DHCP-Based Autoconfiguration” section on page 3-6 and the “Configuring DHCP” section of the “IP addressing and Services” section of the Cisco IOS IP Configuration Guide. Limitations and Restrictions • • • The DHCP-based autoconfiguration with a saved configuration process stops if there is not at least one Layer 3 interface in an up state without an assigned IP address in the network. option 66 (the DHCP server hostname) option 150 (the TFTP server address). Release 12. until you reload the switch. and the new image is downloaded and installed on the switch. For procedures to configure the switch as a DHCP server. Catalyst 2960 and 2960-S Switches Software Configuration Guide. The auto-install process stops if a configuration file cannot be downloaded or it the configuration file is corrupted. When you reboot the switch. and option 125 (description of the file) settings. If the new configuration is downloaded to a switch that already has a configuration. the downloaded configuration is appended to the configuration file stored on the switch.0(1)SE OL-26520-02 3-5 .) Note To enable a DHCP auto-image update on the switch. Unless you configure a timeout.Chapter 3 Assigning the Switch IP Address and Default Gateway Assigning Switch Information Understanding DHCP-based Autoconfiguration and Image Update You can use the DHCP image upgrade features to configure a DHCP server to download both a new image and a new configuration file to one or more switches in a network. There are two types of DHCP image upgrades: DHCP autoconfiguration and DHCP auto-image update. (Any existing configuration is not overwritten by the downloaded one. The downloaded configuration file becomes the running configuration of the switch.2.

the feature is not triggered during subsequent system restarts. page 3-7 Configuring the Relay Device. or both. the Cisco IOS DHCP server and relay agent features are enabled on your switch but are not configured. If you want the switch to receive IP address information. If the router IP address or the TFTP server name are not found. page 3-7 Obtaining Configuration Files.0(1)SE 3-6 OL-26520-02 . see the “Configuring DHCP” section of the “IP Addressing and Services” section of the Cisco IOS IP Configuration Guide on Cisco. the configuration file. page 3-7 Configuring the DNS. If the IP address and the subnet mask are not in the reply. Note that if the downloaded configuration is saved to the startup configuration. the switch is not configured. you must configure the DHCP server with these lease options: • • • • IP address of the client (required) Subnet mask of the client (required) Router IP address (default gateway address to be used by the switch) (required) DNS server IP address (optional) If you want the switch to receive the configuration file from a TFTP server. Catalyst 2960 and 2960-S Switches Software Configuration Guide. instead of unicast. By default. If your DHCP server is a Cisco device. If you do not configure the DHCP server with the lease options described previously. 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. Release 15. page 3-9 DHCP Server Configuration Guidelines You should configure the DHCP server with reserved leases that are bound to each switch by the switch hardware address.com page. TFTP requests. Configuring DHCP-Based Autoconfiguration • • • • • • DHCP Server Configuration Guidelines. page 3-6 Configuring the TFTP Server. it replies to client requests with only those parameters that are configured.Chapter 3 Assigning Switch Information Assigning the Switch IP Address and Default Gateway Note The configuration file that is downloaded from TFTP is merged with the existing configuration in the running configuration but is not saved in the NVRAM unless you enter the write memory or copy running-configuration startup-configuration privileged EXEC command. The switch can act as a DHCP server. page 3-8 Example Configuration. for additional information about configuring DHCP. the switch can receive IP address information. Unavailability of other lease options does not affect autoconfiguration. the switch might send broadcast. These features are not operational.

If it is on a different LAN. 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). when a switch sends broadcast packets that require a response from a host on a different LAN. Normally. You must configure this relay device to forward received broadcast packets on an interface to the destination host. The router-confg or the ciscortr. and configuration filename. If the relay device is a Cisco router.config.255. 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. if the DHCP and TFTP servers are properly configured. or hostname. The TFTP server addresses used include the specified TFTP server address (if any) and the broadcast address (255. If you did not specify the configuration filename. see the “Configuring the Relay Device” section on page 3-7.Chapter 3 Assigning the Switch IP Address and Default Gateway Assigning Switch Information Configuring the TFTP Server Based on the DHCP server configuration. You must configure the TFTP server name-to-IP address map on the DNS server. the switch attempts to download the specified configuration file from the specified TFTP server. TFTP packets.255).cfg.255. the TFTP server must contain one or more configuration files in its base directory. enable IP routing (ip routing global configuration command). If you configured the DHCP server to respond to the switch with all the options required for IP connectivity to the TFTP server. address. the TFTP server. the switch attempts to download one or more configuration files from the TFTP server. and if you configured the DHCP server with a TFTP server name. The files include the specified configuration filename (if any) and these files: network-config. a relay must be configured to forward the TFTP packets to the TFTP server. Configuring the Relay Device You must configure a relay device. The DNS server can be on the same or on a different LAN as the switch. or if the configuration file could not be downloaded. For the switch to successfully download a configuration file. hostname. you must also configure the TFTP server name-to-IP-address mapping in the DNS-server database. 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. the switch attempts to download a configuration file by using various combinations of filenames and TFTP server addresses. If the TFTP server to be used is on a different LAN from the switch. also referred to as a relay agent. The TFTP server contains the configuration files for the switch. The preferred solution is to configure the DHCP server with all the required information. and configure helper addresses by using the ip helper-address interface configuration command. For more information.cfg file (These files contain commands common to all switches.0(1)SE OL-26520-02 3-7 .cfg.) If you specify the TFTP server name in the DHCP server-lease database. these files are not accessed. Configuring the DNS The DHCP server uses the DNS server to resolve the TFTP server name to an IP address. and in some cases.cfg file (known as the default configuration files). cisconet. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Examples of broadcast packets that the switch might send are DHCP. the switch must be able to access it through a router. DNS. You can enter up to two DNS server IP addresses in the lease database. where hostname is the switch’s current hostname. Release 15.

subnet mask. it completes its boot-up process.cfg default configuration file. • Only the IP address is reserved for the switch and provided in the DHCP reply.0. but the TFTP server address is not provided in the DHCP reply (one-file read method). 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. and the configuration filename from the DHCP server.4 49068 DHCP server TFTP server DNS server Obtaining Configuration Files Depending on the availability of the IP address and the configuration filename in the DHCP reserved lease.0. 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).0.0. The switch receives its IP address. The configuration filename is not provided (two-file read method).0.0. the switch reads the cisconet.2 20. and the configuration filename from the DHCP server.0.0.0.) Catalyst 2960 and 2960-S Switches Software Configuration Guide.1 Figure 3-2 Relay Device Used in Autoconfiguration Switch (DHCP client) Cisco router (Relay) 10.0. in Figure 3-2.0.cfg file.0. TFTP server address.Chapter 3 Assigning Switch Information Assigning the Switch IP Address and Default Gateway For example.0(1)SE 3-8 OL-26520-02 . and the TFTP server address from the DHCP server.0.4 On interface 20.0. configure the router interfaces as follows: On interface 10. subnet mask. and upon receipt.0. subnet mask. • The IP address and the configuration filename is reserved for the switch. Release 15. The switch sends a unicast message to the TFTP server to retrieve the network-confg or cisconet.2: router(config-if)# ip helper-address 20. The switch receives its IP address.0.0.0.3 router(config-if)# ip helper-address 20.1 router(config-if)# ip helper-address 10. it completes its boot-up process.1 20.0.2 10.2 router(config-if)# ip helper-address 20.0. The switch receives its IP address.0.0.1 20. (If the network-confg file cannot be read.0.3 20.0. The switch sends a broadcast message to a TFTP server to retrieve the named configuration file from the base directory of the server.

cfg was read earlier) from the TFTP server.9f1e.0 10. If the cisconet.255.2003 00e0.255.0.0.9f1e.0. it reads the router-confg file.0 10. the switch uses the default Switch as its hostname.2001 10.9f1e.0.2002 00e0.10 10.2 Catalyst 2960 and 2960-S Switches Software Configuration Guide.0. or if the TFTP server name cannot be resolved to an IP address.10 10.0.255.0.2004 10.21 255.0.0.10 10.255.0.0.0.2 10.0.255.2 111394 Switch D 00e0.2004 Cisco router 10.2003 10.255.0.0.10 10. it reads the ciscortr. The switch fills its host table with the information in the file and obtains its hostname.0. the filename of the host is truncated to eight characters.0.0.0. or the hostname file.22 255.0.0 10. Figure 3-3 DHCP-Based Autoconfiguration Network Example Switch 1 Switch 2 Switch 3 Switch 4 00e0.0.2 Switch B 00e0.0.24 255.0.1 10.9f1e.0 10.cfg file is read. if all attempts to read the configuration file through unicast transmissions fail.0.0. If the hostname is not found in the file.2002 10.2 Switch C 00e0.0.255.0.9f1e.0.3 DHCP server DNS server TFTP server (tftpserver) Table 3-2 shows the configuration of the reserved leases on the DHCP server. Note The switch broadcasts TFTP server requests if the TFTP server is not obtained from the DHCP replies.23 255.9f1e.0. Table 3-2 DHCP Server Configuration Switch A Binding key (hardware address) IP address Subnet mask Router address DNS server address 00e0.cfg file. If the switch cannot read the router-confg file.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.0(1)SE OL-26520-02 3-9 . cisconet.255.cfg.9f1e.cfg. If the switch cannot read the network-confg. After obtaining its hostname from the default configuration file or the DHCP reply. If the hostname is not specified in the DHCP reply. Release 15.0.10 10.0. Example Configuration Figure 3-3 shows a sample network for retrieving IP information by using DHCP-based autoconfiguration. the switch uses the hostname in the DHCP reply. depending on whether network-confg or cisconet.2001 00e0.9f1e.0. the switch reads the configuration file that has the same name as its hostname (hostname-confg or hostname.

0.3 switcha-confg switcha Switch B tftpserver or 10. It reads the configuration file that corresponds to its hostname.0.22 ip host switchc 10.3 switchd-confg switchd DNS Server Configuration The DNS server maps the TFTP server name tftpserver to IP address 10.24 DHCP Client Configuration No configuration file is present on Switch A through Switch D.0. switchb-confg. Switch A reads its configuration file as follows: • • • • • It obtains its IP address 10. This directory contains the network-confg file used in the two-file read method.0.0. It reads its host table by indexing its IP address 10. It adds the contents of the network-confg file to its host table.0. for example. Switches B through D retrieve their configuration files and IP addresses in the same way.21 from the DHCP server.0.21 ip host switchb 10.0. TFTP Server Configuration (on UNIX) The TFTP server base directory is set to /tftpserver/work/. it reads switch1-confg from the TFTP server. The base directory also contains a configuration file for each switch (switcha-confg. Switch A reads the network-confg file from the base directory of the TFTP server.0.0.0. Configuration Explanation In Figure 3-3.0.0.Chapter 3 Assigning Switch Information Assigning the Switch IP Address and Default Gateway Table 3-2 DHCP Server Configuration (continued) Switch A TFTP server name Boot filename (configuration file) (optional) Hostname (optional) tftpserver or 10.0.0(1)SE 3-10 OL-26520-02 .21 to its hostname (switcha).0.0. This file contains the hostname to be assigned to the switch based on its IP address. Catalyst 2960 and 2960-S Switches Software Configuration Guide.0. 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.23 ip host switchd 10.0. Release 15.3 switchc-confg switchc Switch D tftpserver or 10.3 switchb-confg switchb Switch C tftpserver or 10.0.3. If no configuration filename is given in the DHCP server reply.0.

This example shows how to configure a switch as a DHCP server so that it will download a configuration file: Switch# configure terminal Switch(config)# ip dhcp pool pool1 Switch(dhcp-config)# network 10.10. (Optional) Save your entries in the configuration file. The client switch is configured to download either a new configuration file or a new configuration file and a new image file. Command Step 1 Step 2 Step 3 Step 4 Purpose Enter global configuration mode.0 255. Specify the subnet network number and mask of the DHCP address pool.255. Return to privileged EXEC mode.255. Release 15. Return to global configuration mode.1 Switch(dhcp-config)# option 150 10.10. Put the interface into Layer 3 mode. Specify the name of the configuration file that is used as a boot image. Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Step 11 Step 12 Step 13 default-router address option 150 address exit tftp-server flash:filename. Configuring DHCP Autoconfiguration (Only Configuration File) Beginning in privileged EXEC mode.Chapter 3 Assigning the Switch IP Address and Default Gateway Assigning Switch Information Configuring the DHCP Auto Configuration and Image Update Features Using DHCP to download a new image and a new configuration to a switch requires that you configure at least two switches: One switch acts as a DHCP and TFTP server.0(1)SE OL-26520-02 3-11 .text Switch(config-if)# no switchport Switch(config-if)# ip address 10.10.1 Switch(dhcp-config)# exit Switch(config)# tftp-server flash:config-boot. and enter DHCP pool configuration mode.255. Specify the IP address and mask for the interface.10.1 255.10.text interface interface-id no switchport ip address address mask end copy running-config startup-config Specify the IP address of the default router for a DHCP client. The prefix length must be preceded by a forward slash (/).0 Switch(config-if)# end Catalyst 2960 and 2960-S Switches Software Configuration Guide. Specify the IP address of the TFTP server.0 Switch(dhcp-config)# bootfile config-boot.10. The prefix is an alternative way of specifying the network mask of the client.text Switch(dhcp-config)# default-router 10.10. Specify the address of the client that will receive the configuration file.255. Note configure terminal ip dhcp poolname bootfile filename network network-number mask prefix-length The prefix length specifies the number of bits that comprise the address prefix. Create a name for the DHCP Server address pool. follow these steps to configure DHCP autoconfiguration of the TFTP and DHCP settings on a new switch to download a new configuration file. Specify the configuration file on the TFTP server.10.

Specify the image name on the TFTP server.tar exit tftp-server flash:config. Specify the path to the text file that describes the path to the image file. Create a name for the DHCP server address pool and enter DHCP pool configuration mode. follow these steps to configure DHCP autoconfiguration to configure TFTP and DHCP settings on a new switch to download a new image and a new configuration file. Note Before following the steps in this table. Specify the subnet network number and mask of the DHCP address pool. Upload the text file to the switch. Specify the IP address of the TFTP server. The prefix is an alternative way of specifying the network mask of the client. Specify the text file that contains the name of the image file to download Specify the address of the client that will receive the configuration file. The prefix length must be preceded by a forward slash (/). Catalyst 2960 and 2960-S Switches Software Configuration Guide. Return to privileged EXEC mode.text tftp-server flash:imagename.0(1)SE 3-12 OL-26520-02 . This image must be a tar and not a bin file. Release 15. In the text file. Specify the name of the file that is used as a boot image. Specify the Cisco IOS configuration file on the TFTP server.txt interface interface-id no switchport ip address address mask end copy running-config startup-config Specify the IP address of the default router for a DHCP client. Command Step 1 Step 2 Step 3 Step 4 Purpose Enter global configuration mode. you must create a text file (for example. Upload the tar file for the new image to the switch. put the name of the image that you want to download. autoinstall_dhcp) that will be uploaded to the switch. Specify the IP address and mask for the interface.tar tftp-server flash:filename.txt copy tftp flash imagename. (Optional) Save your entries in the configuration file. Note configure terminal ip dhcp pool name bootfile filename network network-number mask prefix-length The prefix length specifies the number of bits that comprise the address prefix. Return to global configuration mode.Chapter 3 Assigning Switch Information Assigning the Switch IP Address and Default Gateway Configuring DHCP Auto-Image Update (Configuration File and Image) Beginning in privileged EXEC mode. Put the interface into Layer 3 mode. Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Step 11 Step 12 Step 13 Step 14 Step 15 Step 16 Step 17 Step 18 default-router address option 150 address option 125 hex copy tftp flash filename.

10.1 255. Release 15.0(1)SE OL-26520-02 3-13 .255.text Switch(config)# tftp-server flash:boot-config.6f69.255.1 Switch(dhcp-config)# option 150 10.0a05.7461. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Enable autoconfiguration with a saved configuration. Step 4 Step 5 Step 6 banner config-save ^C warning-message ^C end show boot (Optional) Create warning messages to be displayed when you try to save the configuration file to NVRAM.686370 Switch(dhcp-config)# exit Switch(config)# tftp-server flash:config-boot.7574.1 Switch(dhcp-config)# option 125 hex 0000.10.10.08661. follow these steps to configure a switch to download a configuration file and new image from a DHCP server: Command Step 1 Step 2 Step 3 Purpose Enter global configuration mode.6c6c. Note configure terminal boot host dhcp boot host retry timeout timeout-value If you do not set a timeout the system will indefinitely try to obtain an IP address from the DHCP server.10.0 255.5f64.6e73.10.text Switch(dhcp-config)# default-router 10. Return to privileged EXEC mode.0 Switch(dhcp-config)# bootfile config-boot.0 Switch(config-if)# end Configuring the Client Beginning in privileged EXEC mode.255.text Switch(config)# tftp-server flash: autoinstall_dhcp Switch(config-if)# no switchport Switch(config-if)# ip address 10.Chapter 3 Assigning the Switch IP Address and Default Gateway Assigning Switch Information This example shows how to configure a switch as a DHCP server so it downloads a configuration file: Switch# config terminal Switch(config)# ip dhcp pool pool1 Switch(dhcp-config)# network 10.10.10.0009. Verify the configuration.255. (Optional) Set the amount of time the system tries to download a configuration file.10.

Saving Configuration File to NVRAM May Cause You to No longer Automatically Download Configuration Files at Reboot^C Switch(config)# vlan 99 Switch(config-vlan)# interface vlan 99 Switch(config-if)# no shutdown Switch(config-if)# end Switch# show boot BOOT path-list: Config file: flash:/config. Manually Assigning IP Information Beginning in privileged EXEC mode.0(1)SE 3-14 OL-26520-02 . the switch has connectivity to the remote networks with which a host needs to communicate. Once the default gateway is configured. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Return to global configuration mode. Enter interface configuration mode. Release 15. 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 VLAN range is 1 to 4094. Step 6 end Return to privileged EXEC mode.text Enable Break: no Manual Boot: no HELPER path-list: NVRAM/Config file buffer size: 32768 Timeout for Config Download: 300 seconds Config Download via DHCP: enabled (next boot: enabled) Switch# Note You should only configure and enable the Layer 3 interface. Enter the IP address and subnet mask. follow these steps to manually assign IP information to multiple switched virtual interfaces (SVIs): Command Step 1 Step 2 Step 3 Step 4 Step 5 Purpose Enter global configuration mode. Do not assign an IP address or DHCP-based autoconfiguration with a saved configuration. The default gateway receives IP packets with unresolved destination IP addresses from the switch.text Private Config file: flash:/private-config. and enter the VLAN to which the IP information is assigned.Chapter 3 Assigning Switch Information Assigning the Switch IP Address and Default Gateway This example uses a Layer 3 SVI interface on VLAN 99 to enable DHCP-based autoconfiguration with a saved configuration: Switch# configure terminal Switch(conf)# boot host dhcp Switch(conf)# boot host retry timeout 300 Switch(conf)# banner config-save ^C Caution . it does not need to have a default gateway set. Note configure terminal interface vlan vlan-id ip address ip-address subnet-mask exit ip default-gateway ip-address When your switch is configured to route with IP.

137.0(1)SE OL-26520-02 3-15 . To remove the default gateway address.255. Current configuration: 1363 bytes ! version 12. For information on setting the switch system name. If you are removing the address through a Telnet session.20.0 ! mvr type source <output truncated> . (Optional) Save your entries in the configuration file.” 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.255.255.255.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 Catalyst 2960 and 2960-S Switches Software Configuration Guide. <output truncated> . show interfaces vlan vlan-id show ip redirects copy running-config startup-config To remove the switch IP address. protecting access to privileged EXEC commands.137.0 no ip directed-broadcast ! ip default-gateway 172..2 no service pad service timestamps debug uptime service timestamps log uptime no service password-encryption ! hostname ! enable secret 5 $1$ej9.Chapter 3 Assigning the Switch IP Address and Default Gateway Checking and Saving the Running Configuration Command Step 7 Step 8 Step 9 Purpose Verify the configured IP address.20..137.. see Chapter 5. ip address 172. “Administering the Switch. Verify the configured default gateway. Release 15.20.$DMUvAUnZOAmvmgqBEzIxE0 ! . use the no ip address interface configuration command. use the no ip default-gateway global configuration command..50 255.50 255.! interface VLAN1 ip address 172. your connection to the switch will be lost. and setting time and calendar services.

reload the switch or switch stack. For more information about alternative locations from which to copy the configuration file.” Configuring the NVRAM Buffer Size The default NVRAM buffer size is 512 KB. You can configure the size of the NVRAM buffer to support larger configuration files. the configuration file might be too large to save to NVRAM. enter this privileged EXEC command: Switch# copy running-config startup-config Destination filename [startup-config]? Building configuration. use the show startup-config or more startup-config privileged EXEC command.Chapter 3 Checking and Saving the Running Configuration Assigning the Switch IP Address and Default Gateway To store the configuration or changes you have made to your startup configuration in flash memory. and Software Images.. To display information stored in the NVRAM section of flash memory. When you add a switch to a stack and the NVRAM size differs. follow these steps to configure the NVRAM buffer size: Command Step 1 Step 2 Step 3 Step 4 Purpose Enter global configuration mode. your configuration will be lost the next time you reload the system. this occurs when you have many switches in a switch stack. see Appendix A. The valid range for size is from 4096 to 1048576. Configure the NVRAM buffersize in KB..0(1)SE 3-16 OL-26520-02 . Verify the configuration. configure terminal boot buffersize size end show boot Catalyst 2960 and 2960-S Switches Software Configuration Guide. The new NVRAM buffer size is synced to all current and new member switches. This command saves the configuration settings that you made. In some cases. Beginning in privileged EXEC mode. “Working with the Cisco IOS File System. Configuration Files. If you fail to do this. the new switch syncs with the stack and reloads automatically. Note After you configure the NVRAM buffer size. Release 15. Return to privileged EXEC mode. Typically.

page 3-20 See also Appendix A. Configuration Files. End with CNTL/Z.” for information about switch configuration files.text Enable Break : no Manual Boot : no HELPER path-list : Auto upgrade : yes Auto upgrade path : NVRAM/Config file buffer size: 524288 Timeout for Config Download: 300 seconds Config Download via DHCP: enabled (next boot: enabled) Switch# Modifying the Startup Configuration These sections describe how to modify the switch startup configuration: • • • • • Default Boot Configuration. one per line. Catalyst 2960 and 2960-S Switches Software Configuration Guide.Chapter 3 Assigning the Switch IP Address and Default Gateway Modifying the Startup Configuration This example shows how to configure the NVRAM buffer size: Switch# configure terminal Enter configuration commands. page 3-19 Controlling Environment Variables. page 3-19 Booting a Specific Software Image. “Working with the Cisco IOS File System.text Private Config file : flash:/private-config. Release 15. page 3-18 Automatically Downloading a Configuration File.0(1)SE OL-26520-02 3-17 . and Software Images. Switch(config)# boot buffersize 524288 Switch(config)# end Switch# show boot BOOT path-list : Config file : flash:/config. page 3-18 Booting Manually.

which will be loaded during the next boot-up cycle. Filenames and directory names are case sensitive. A new switch has no configuration file. For more information. depth-first search throughout the flash file system.Chapter 3 Modifying the Startup Configuration Assigning the Switch IP Address and Default Gateway Default Boot Configuration Table 3-3 Default Boot Configuration Feature Operating system software image Default Setting The switch attempts to automatically boot up the system using information in the BOOT environment variable. Specify the configuration file to load during the next boot-up cycle. If the variable is not set. specify the path (directory) and the configuration filename. Specifying the Filename to Read and Write the System Configuration By default.text to read and write a nonvolatile copy of the system configuration. Configuration file Configured switches use the config.bin extension).text file stored on the system board in flash memory.0(1)SE 3-18 OL-26520-02 . Release 15. The Cisco IOS image is stored in a directory that has the same name as the image file (excluding the . you can specify a different filename. Automatically Downloading a Configuration File You can automatically download a configuration file to your switch by using the DHCP-based autoconfiguration feature. the switch attempts to load and execute the first executable image it can by performing a recursive. For file-url. the Cisco IOS software uses the file config. In a depth-first search of a directory. each encountered subdirectory is completely searched before continuing the search in the original directory. Catalyst 2960 and 2960-S Switches Software Configuration Guide. use the no boot config-file global configuration command. The boot config-file global configuration command changes the setting of the CONFIG_FILE environment variable. Verify your entries. configure terminal boot config-file flash:/file-url Step 3 Step 4 end show boot Return to privileged EXEC mode. Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file. see the “Understanding DHCP-Based Autoconfiguration” section on page 3-3. Beginning in privileged EXEC mode. To return to the default setting. However. follow these steps to specify a different configuration filename: Command Step 1 Step 2 Purpose Enter global configuration mode.

However. use the no boot manual global configuration command. If this variable is not set. Beginning in privileged EXEC mode. the switch attempts to load and execute the first executable image it can by performing a recursive. The boot manual global command changes the setting of the MANUAL_BOOT environment variable. To disable manual booting. Beginning in privileged EXEC mode. follow these steps to configure the switch to boot a specific image during the next boot cycle: Command Step 1 Step 2 Purpose Enter global configuration mode. use the boot filesystem:/file-url boot loader command. follow these steps to configure the switch to manually boot up during the next boot cycle: Command Step 1 Step 2 Step 3 Step 4 Purpose Enter global configuration mode. In a depth-first search of a directory. Release 15. Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file. Verify your entries. each encountered subdirectory is completely searched before continuing the search in the original directory. depth-first search throughout the flash file system. the switch automatically boots up. shown by the switch: prompt.0(1)SE OL-26520-02 3-19 . For file-url. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Filenames and directory names are case sensitive. • • configure terminal boot manual end show boot For filesystem:. specify the path (directory) and the name of the bootable image. Booting a Specific Software Image By default. • • configure terminal boot system filesystem:/file-url For filesystem:. Enable the switch to manually boot up during the next boot cycle. the switch attempts to automatically boot up the system using information in the BOOT environment variable. the switch is in boot loader mode. however. you can specify a specific image to boot up. use flash: for the system board flash device. To boot up the system. Return to privileged EXEC mode. you can configure it to manually boot up. For file-url. Configure the switch to boot a specific image in flash memory during the next boot cycle. use flash: for the system board flash device. specify the path (directory) and the name of the bootable image. Filenames and directory names are case sensitive.Chapter 3 Assigning the Switch IP Address and Default Gateway Modifying the Startup Configuration Booting Manually By default. The next time you reboot the system.

which can be used to control how the boot loader. behaves. Boot loader environment variables are similar to environment variables that can be set on UNIX or DOS systems. The switch boot loader software provides support for nonvolatile environment variables. “ ”) is a variable with a value. To return to the default setting. For example. which does not read the Cisco IOS configuration file. the switch attempts to automatically boot up the system using information in the BOOT environment variable. see the command reference for this release. it has a value if it is listed in the file even if the value is a null string. which extends or patches the functionality of the boot loader can be stored as an environment variable. Release 15. During the next boot cycle. Controlling Environment Variables With a normally operating switch. A variable has no value if it is not listed in this file. and press the switch Mode button while reconnecting the power cord. it is not necessary to alter the setting of the environment variables. Then the boot loader switch: prompt appears.0(1)SE 3-20 OL-26520-02 . the name of a boot loader helper file. For example. The boot system global command changes the setting of the BOOT environment variable. Note For complete syntax and usage information for the boot loader commands and environment variables. which is responsible for reading the Cisco IOS configuration file. the name of the Cisco IOS configuration file can be stored as an environment variable. Data that controls code. Many environment variables are predefined and have default values. Under normal circumstances. • You can change the settings of the environment variables by accessing the boot loader or by using Cisco IOS commands. you enter the boot loader mode only through a switch console connection configured for 9600 b/s. Environment variables that have values are stored in flash memory outside of the flash file system.Chapter 3 Modifying the Startup Configuration Assigning the Switch IP Address and Default Gateway Command Step 3 Step 4 Purpose Return to privileged EXEC mode. use the no boot system global configuration command. end show boot Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file. or any other software running on the system. A variable that is set to a null string (for example. Environment variables store two kinds of data: • Data that controls code. Verify your entries. You can release the Mode button a second or two after the LED above port 1 turns off. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Each line in these files contains an environment variable name and an equal sign followed by the value of the variable. Unplug the switch power cord.

the system attempts to load and execute the first executable image it can find by using a recursive. the system attempts to boot the first bootable file that it can find in the flash file system. 0. late at night or during the weekend when the switch is used less). and specify the name of the bootable image.Chapter 3 Assigning the Switch IP Address and Default Gateway Scheduling a Reload of the Software Image Table 3-4 describes the function of the most common environment variables. The next time you reboot the system. If the BOOT variable is set but the specified images cannot be loaded. you must manually boot up the switch from the boot loader mode. Table 3-4 Environment Variables Variable BOOT Boot Loader Command set BOOT filesystem:/file-url .. yes.. boot config-file flash:/file-url Changes the filename that Cisco IOS uses to read Specifies the filename that Cisco IOS uses to read and write a nonvolatile copy of the system and write a nonvolatile copy of the system configuration. A semicolon-separated list of executable files to Specifies the Cisco IOS image to load during the next boot cycle. If it is set to no or 0. CONFIG_FILE set CONFIG_FILE flash:/file-url boot manual Enables manually booting up the switch during the next boot cycle and changes the setting of the MANUAL_BOOT environment variable. Cisco IOS Global Configuration Command boot system filesystem:/file-url . Catalyst 2960 and 2960-S Switches Software Configuration Guide. To boot up the system.. Valid values are 1.0(1)SE OL-26520-02 3-21 . set. This command changes the configuration. MANUAL_BOOT set MANUAL_BOOT yes Decides whether the switch automatically or manually boots up. to perform a software upgrade on all switches in the network). use the boot flash:filesystem:/file-url boot loader command. the switch is in boot loader mode. If it is set to anything else. depth-first search through the flash file system. or you can synchronize a reload network-wide (for example. Note A scheduled reload must take place within approximately 24 days. 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.. If the BOOT environment variable is not setting of the BOOT environment variable. Release 15. and no. the boot loader attempts to automatically boot up the system. This command changes the try to load and execute when automatically booting. CONFIG_FILE environment variable.

Release 15. During the save operation. the hardware calendar. To schedule reloads across several switches to occur simultaneously. 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 reload is scheduled to take place at the specified time and date. 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. 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. it reboots itself. You can specify the reason for the reload in a string up to 255 characters in length. Specifying 00:00 schedules the reload for midnight. do not reload it from a virtual terminal. 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). or manually).Chapter 3 Scheduling a Reload of the Software Image Assigning the Switch IP Address and Default Gateway Configuring a Scheduled Reload To configure your switch to reload the software image at a later time. If your switch is configured for manual booting. If you proceed in this situation. If the system is not set to manually boot up. the switch prompts you to save the configuration before reloading. Note Use the at keyword only if the switch system clock has been set (through Network Time Protocol (NTP). The reload must take place within approximately 24 days. The time is relative to the configured time zone on the switch. Note • 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). Use the reload command after you save the switch configuration information to the startup configuration (copy running-config startup-config). If you specify the month and day. The reload command halts the system. If you do not specify the month and day. Catalyst 2960 and 2960-S Switches Software Configuration Guide.0(1)SE 3-22 OL-26520-02 . the time on each switch must be synchronized with NTP. the system enters setup mode upon reload.

Catalyst 2960 and 2960-S Switches Software Configuration Guide.m: Switch# reload at 19:30 Reload scheduled for 19:30:00 UTC Wed Jun 5 1996 (in 2 hours and 25 minutes) Proceed with reload? [confirm] This example shows how to reload the software on the switch at a future time: Switch# reload at 02:00 jun 20 Reload scheduled for 02:00:00 UTC Thu Jun 20 1996 (in 344 hours and 53 minutes) Proceed with reload? [confirm] To cancel a previously scheduled reload.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 on the current day at 7:30 p. Release 15. use the show reload 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.0(1)SE OL-26520-02 3-23 . use the reload cancel 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).

and logging the results. executing the configuration change. page 4-5 Configuring Cisco IOS Agents.cisco. 2960-S. page 4-1 Understanding Cisco IOS Agents.cisco. sending them to the device. file manager. In this mode. page 4-13 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).html For complete syntax and usage information for the commands used in this chapter. The Configuration Engine supports standalone and server modes and has these CNS components: • • • Configuration service (web server. The Configuration Engine automates initial configurations and configuration updates by generating device-specific configuration changes. storing their configurations and delivering them as needed. go to the Cisco IOS Network Management Command Reference. Note For complete configuration information for the Cisco Configuration Engine.CH A P T E R 4 Configuring Cisco IOS Configuration Engine This chapter describes how to configure the feature on the Catalyst 2960. and namespace mapping server) Event service (event gateway) Data service directory (data models and schema) In standalone mode. In server mode.0(1)SE OL-26520-02 4-1 . no external directory or other data store is required.4: http://www. page 4-6 Displaying CNS Configuration. go to http://www. Each Configuration Engine manages a group of Cisco devices (switches and routers) and the services that they deliver.com/en/US/docs/ios/netmgmt/command/reference/nm_book. and 2960-C switch. the Configuration Engine supports an embedded Directory Service.com/en/US/products/sw/netmgtsw/ps4617/tsd_products_support_series_home. Catalyst 2960 and 2960-S Switches Software Configuration Guide.html • • • • Understanding Cisco Configuration Engine Software. Release 12. Release 15. the Configuration Engine supports the use of a user-defined external directory.

The Configuration Service delivers device and service configurations to the switch for initial configuration and mass reconfiguration by logical groups. Configuration templates are text files containing static configuration information in the form of CLI commands. page 4-2 Event Service. Catalyst 2960 and 2960-S Switches Software Configuration Guide. page 4-3 Configuration Service The Configuration Service is the core component of the Cisco Configuration Engine. 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. The configuration agent can either apply configurations immediately or delay the application until receipt of a synchronization event from the configuration server.0(1)SE OL-26520-02 141327 4-2 .Chapter 4 Configuring Cisco IOS Configuration Engine Understanding Cisco Configuration Engine Software Figure 4-1 Configuration Engine Architectural Overview Service provider network Configuration engine Data service directory Configuration server Event service Web-based user interface Order entry configuration management • • • Configuration Service. The Configuration Service uses the CNS Event Service to send and receive configuration change events and to send success and failure notifications. Switches receive their initial configuration from the Configuration Service when they start up on the network for the first time. variables are specified using Lightweight Directory Access Protocol (LDAP) URLs that reference the device-specific configuration information stored in a directory. Release 15. page 4-3 What You Should Know About the CNS IDs and Device Hostnames. 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. In the templates. It consists of a configuration server that works with Cisco IOS CNS agents on the switch.

When you have populated your data store with your subject names. The Configuration Engine intersects two namespaces. Because the Configuration Engine uses both the event bus and the configuration server to provide configurations to devices. device or group ID. Similarly. the term ConfigID is the unique identifier for a device. Within the scope of a single instance of the configuration server. when given a unique device ID and event. Subject-based addressing conventions define a simple. cisco. which serves as the key into the Configuration Engine directory for the corresponding set of switch CLI attributes. The Event Service is a highly capable publish-and-subscribe communication method.config. The Event Service uses subject-based addressing to send messages to their destinations. the namespace mapping service returns a set of events to which to subscribe. no two configured switches can share the same value for DeviceID. The event agent is on the switch and facilitates the communication between the switch and the event gateway on the Configuration Engine. ConfigID Each configured switch has a unique ConfigID. Within the scope of a single instance of the event bus. For a subscriber. when given a unique group ID. and event. NSM changes your event subject-name strings to those known by Cisco IOS. no two configured switches can share the same value for ConfigID. the term DeviceID is the CNS unique identifier for a device. the mapping service returns a set of events on which to publish. This unique identifier can take on multiple synonyms. The ConfigID is fixed at startup time and cannot be changed until the device restarts.load.cns.0(1)SE 4-3 OL-26520-02 . Release 15. NameSpace Mapper The Configuration Engine includes the NameSpace Mapper (NSM) that provides a lookup service for managing logical groups of devices based on application. Cisco IOS devices recognize only event subject-names that match those configured in Cisco IOS software. The ConfigID defined on the switch must match the ConfigID for the corresponding switch definition on the Configuration Engine. even if the switch hostname is reconfigured. one for the event bus and the other for the configuration server. you must define both ConfigID and Device ID for each configured switch. Within the scope of the event bus namespace. for a publisher. Within the scope of the configuration server namespace. device ID. Catalyst 2960 and 2960-S Switches Software Configuration Guide. where each synonym is unique within a particular namespace. for example. and event. The event service uses namespace content for subject-based addressing of messages. uniform namespace for messages and their destinations. You can use the namespace mapping service to designate events by using any desired naming convention. What You Should Know About the CNS IDs and Device Hostnames The Configuration Engine assumes that a unique identifier is associated with each configured switch.Chapter 4 Understanding Cisco Configuration Engine Software Configuring Cisco IOS Configuration Engine Event Service The Cisco Configuration Engine uses the Event Service for receipt and generation of configuration events.

In server mode. and ConfigID In standalone mode. the configuration server uses the hostname as the DeviceID when an event is sent on hostname.com/en/US/products/sw/netmgtsw/ps4617/prod_installation_guides_list. However. All switches configured with the cns config partial global configuration command must access the event bus. the unique DeviceID attribute is always used for sending an event on the bus. If this attribute is not set. when a hostname value is set for a switch. the only way to refresh the DeviceID is to break the connection between the switch and the event gateway. When changing the switch hostname on the switch.cisco. When the connection is re-established. subsequent cns config partial global configuration command operations malfunction. Enter the no cns event global configuration command followed by the cns event global configuration command. Caution When using the Configuration Engine user interface. Release 15. as originated on the switch. which is analogous to the switch source address so that the switch can be targeted as a specific destination on the bus. see the Configuration Engine setup and configuration guide: http://www. The event gateway caches this DeviceID value for the duration of its connection to the switch.html Catalyst 2960 and 2960-S Switches Software Configuration Guide. The event gateway couples the DeviceID value to the Cisco IOS hostname each time this connection is established. Otherwise. The origin of the DeviceID is defined by the Cisco IOS hostname of the switch. These and other associated attributes (tag value pairs) are set when you run Setup on the Configuration Engine. Using Hostname. the DeviceID. the hostname is not used.0(1)SE OL-26520-02 4-4 . The logical Cisco IOS termination point on the event bus is embedded in the event gateway. must match the DeviceID of the corresponding switch definition in the Configuration Engine. the event is sent on the cn=<value> of the device. you cannot update the switch. The event gateway represents the switch and its corresponding DeviceID to the event bus. In this mode. which in turn functions as a proxy on behalf of the switch. 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. If the hostname has not been set. Therefore. The switch declares its hostname to the event gateway immediately after the successful connection to the event gateway. 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. the switch sends its modified hostname to the event gateway. the DeviceID variable and its usage reside within the event gateway adjacent to the switch. The event gateway redefines the DeviceID to the new value.Chapter 4 Configuring Cisco IOS Configuration Engine Understanding Cisco Configuration Engine Software DeviceID Each configured switch participating on the event bus has a unique DeviceID. Note For more information about running the setup program on the Configuration Engine. DeviceID.

0(1)SE 4-5 141328 Access layer switches OL-26520-02 . The switch automatically configures the assigned IP address on interface VLAN 1 (the default) and downloads the bootstrap configuration file from the TFTP server.Chapter 4 Understanding Cisco IOS Agents Configuring Cisco IOS Configuration Engine 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 distribution switch acts as a DHCP relay agent and forwards the request to the DHCP server. Upon receiving the request. page 4-6 Synchronized Configuration. it attempts to get an IP address by broadcasting a DHCP request on the network. The DHCP relay agent forwards the reply to the switch. Upon successful download of the bootstrap configuration file. The Configuration Engine maps the Config ID to a template and downloads the full configuration file to the switch. page 4-6 Initial Configuration When the switch first comes up. Assuming there is no DHCP server on the subnet. The Cisco IOS agents initiate communication with the Configuration Engine by using the appropriate ConfigID and EventID. Figure 4-2 shows a sample network configuration for retrieving the initial bootstrap configuration file by using DHCP-based autoconfiguration. page 4-5 Incremental (Partial) Configuration. the switch loads the file in its running configuration. Figure 4-2 Initial Configuration Overview TFTP server Configuration Engine V WAN DHCP server DHCP relay agent default gateway Distribution layer Catalyst 2960 and 2960-S Switches Software Configuration Guide. 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. The Cisco IOS agent feature supports the switch by providing these features: • • • Initial Configuration. and the default gateway IP address in a unicast reply to the DHCP relay agent. Release 15.

Chapter 4 Configuring Cisco IOS Configuration Engine Configuring Cisco IOS Agents Incremental (Partial) Configuration After the network is running. When you complete them. 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. it can defer application of the configuration upon receipt of a write-signal event. If the switch does not apply the incremental 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. it can write it to NVRAM or wait until signaled to do so. The write-signal event tells the switch not to save the updated configuration into its NVRAM. power on the switch. Synchronized Configuration When the switch receives a configuration. Release 15. The switch uses the updated configuration as its running configuration. Table 4-1 Prerequisites for Enabling Automatic Configuration Device Access switch Distribution switch Required Configuration Factory default (no configuration file) • • • IP helper address Enable DHCP relay agent IP routing (if used as default gateway) Catalyst 2960 and 2960-S Switches Software Configuration Guide. If the syntax is correct. If you want to change the configuration or install a custom configuration. At the setup prompt. 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. it publishes an event showing an error status. page 4-9 Enabling Automated CNS Configuration To enable automated CNS configuration of the switch. When the switch has applied the incremental configuration.0(1)SE OL-26520-02 4-6 . you must first complete the prerequisites in Table 4-1. The switch can check the syntax of the configuration before applying it. page 4-8 Enabling the Cisco IOS CNS Agent. see these sections for instructions: • • Enabling the CNS Event Agent. 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 applies the incremental configuration and publishes an event that signals success to the configuration server. Incremental (partial) configurations can be sent to the switch. new services can be added by using the Cisco IOS agent. you need to do nothing else.

see the Cisco Configuration Engine Installation and Setup Guide. with the ConfigID of the device mapped to the template. Note For more information about running the setup program and creating templates on the Configuration Engine.0(1)SE 4-7 OL-26520-02 .5/installation_linux/guide/ setup_1.html Catalyst 2960 and 2960-S Switches Software Configuration Guide. Release 15.5 for Linux: http://www. 1.cisco.Chapter 4 Configuring Cisco IOS Agents Configuring Cisco IOS Configuration Engine Table 4-1 Prerequisites for Enabling Automatic Configuration (continued) Device DHCP server Required Configuration • • • • IP address assignment TFTP server IP address Path to bootstrap configuration file on the TFTP server Default gateway IP address A bootstrap configuration file that includes the CNS configuration commands that enable the switch to communicate with the Configuration Engine The switch configured to use either the switch MAC address or the serial number (instead of the default hostname) to generate the ConfigID and EventID The CNS event agent configured to push the configuration file to the switch TFTP server • • • CNS Configuration Engine One or more templates for each type of device.com/en/US/docs/net_mgmt/configuration_engine/1.

this is the primary gateway.27. Though visible in the command-line help string. enter either the hostname or the IP address of the event gateway. and enter the gateway parameters. (Optional) For port number. (Optional) For source ip-address. set 120 seconds as the keepalive interval. Beginning in privileged EXEC mode.180. (If omitted. follow these steps to enable the CNS event agent on the switch: Command Step 1 Step 2 Purpose Enter global configuration mode. (Optional) Enter backup to show that this is the backup gateway. (Optional) Save your entries in the configuration file. (Optional) For keepalive seconds. Release 15. enter how long the switch waits for the primary gateway route after the route to the backup gateway is established. • • • • Note Step 3 Step 4 Step 5 Step 6 end show cns event connections show running-config copy running-config startup-config Return to privileged EXEC mode. This example shows how to enable the CNS event agent.1. enter the number of unanswered keepalive messages that the switch sends before the connection is terminated. To disable the CNS event agent. The default for each is 0.0(1)SE OL-26520-02 4-8 . set the IP address gateway to 10. enter the maximum time interval that the switch waits before trying to reconnect to the event gateway.Chapter 4 Configuring Cisco IOS Configuration Engine 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. Switch(config)# cns event 10. the encrypt and the clock-timeout time keywords are not supported. enter the port number for the event gateway. The default port number is 11011.) (Optional) For failover-time seconds.27 keepalive 120 10 Catalyst 2960 and 2960-S Switches Software Configuration Guide. enter the source IP address of this device. (Optional) For reconnect time. For retry-count. use the no cns event {ip-address | hostname} global configuration command. Verify your entries. Enable the event agent.180. and set 10 as the retry count. • • • configure terminal cns event {hostname | ip-address} [port-number] [backup] [failover-time seconds] [keepalive seconds retry-count] [reconnect time] [source ip-address] For {hostname | ip-address}. enter how often the switch sends keepalive messages.1. Verify information about the event agent.

The default is 3. • • Catalyst 2960 and 2960-S Switches Software Configuration Guide. The range is 0 to 250 seconds. The range is 1 to 30. Release 15. start the Cisco IOS CNS agent on the switch.Chapter 4 Configuring Cisco IOS Agents Configuring Cisco IOS Configuration Engine Enabling the Cisco IOS CNS Agent After enabling the CNS event agent. enter the amount of time before which the first connection attempt occurs. The default is 0. (Optional) For sleep seconds. The switch uses the CNS connect profile to connect to the Configuration Engine. enter the interval between successive connection attempts to the Configuration Engine. Enter CNS template connect configuration mode. (Optional) For retry-interval seconds. Repeat Steps 2 to 3 to configure another CNS connect template. Enabling an Initial Configuration Beginning in privileged EXEC mode. The default is 120. You can then use the Configuration Engine to remotely send incremental configurations to the switch. Repeat this step for each command line in the template. follow these steps to enable the CNS configuration agent and initiate an initial configuration on the switch: Command Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Purpose Enter global configuration mode. Enter CNS connect configuration mode. Enter a command line for the CNS connect template. The cns config partial global configuration command enables the Cisco IOS agent and initiates a partial configuration on the switch. enter the amount of time after which the connection attempts end. and specify the name of the CNS connect template. specify the name of the CNS connect profile. enter the number of connection retries. (Optional) For timeout seconds.0(1)SE 4-9 OL-26520-02 . and define the profile parameters. (Optional) For retries number. The range is 1 to 40 seconds. Return to global configuration mode. The default is 10 seconds. 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. • • • configure terminal cns template connect name cli config-text exit cns connect name [retries number] [retry-interval seconds] [sleep seconds] [timeout seconds] Enter the name of the CNS connect profile. The range is 10 to 2000 seconds.

Step 9 Step 10 Step 11 Step 12 Step 13 exit hostname name ip route network-number Return to global configuration mode.0(1)SE OL-26520-02 4-10 . enter hardware-serial to set the switch serial number as the unique ID. Enter the hostname for the switch. For {dns-reverse | ipaddress | mac-address}. (Optional) Enter event to set the ID to be the event-id value used to identify the switch. (Optional) Establish a static route to the Configuration Engine whose IP address is network-number. This setting specifies from which interface the IP or MAC address should be retrieved to define the unique ID. [interface-type] | line line-type} • For dlci.. enter the type of interface. For {hardware-serial | hostname| string string | udi}. • • Note • Catalyst 2960 and 2960-S Switches Software Configuration Guide. (Optional) For subinterface subinterface-number. loopback. the image-id value is used to identify the switch. or enter mac-address to use the MAC address as the unique ID. | mac-address} [event] [image] or cns id {hardware-serial | hostname | string string | udi} [event] [image] • • For interface num. For line line-type. specify the point-to-point subinterface number that is used to search for active DLCIs. You can specify more than one template. or virtual-template. cns id interface num {dns-reverse | ipaddress (Optional) Set the unique EventID or ConfigID used by the Configuration Engine. enter the type of interface–for example. or enter udi to set the unique device identifier (UDI) as the unique ID. • • For interface [interface-type]. Release 15. enter hostname (the default) to select the switch hostname as the unique ID. Step 8 template name [ . name] Specify the list of CNS connect templates in the CNS connect profile to be applied to the switch configuration. enter the line type.Chapter 4 Configuring Cisco IOS Configuration Engine Configuring Cisco IOS Agents Command Step 7 Purpose discover {controller controller-type | dlci Specify the interface parameters in the CNS connect profile. enter ipaddress to use the IP address. enter the controller type. group-async. enter the active data-link connection identifiers (DLCIs). ethernet. enter an arbitrary text string for string string as the unique ID. [subinterface subinterface-number] | interface • For controller controller-type. (Optional) Enter image to set the ID to be the image-id value used to identify the switch. Repeat Steps 7 to 8 to specify more interface parameters and CNS connect templates in the CNS connect profile. enter dns-reverse to retrieve the hostname and assign it as the unique ID. If both the event and image keywords are omitted..

(Optional) Enable event for configuration success.0. the encrypt. To disable the CNS Cisco IOS agent. Though visible in the command-line help string. (Optional) Enable syntax-check to check the syntax when this parameter is entered. Switch(config)# cns template connect template-dhcp Switch(config-tmpl-conn)# cli ip address dhcp Switch(config-tmpl-conn)# exit Switch(config)# cns template connect ip-route Switch(config-tmpl-conn)# cli ip route 0.0 ${next-hop} Switch(config-tmpl-conn)# exit Switch(config)# cns connect dhcp Switch(config-cns-conn)# discover interface gigabitethernet Switch(config-cns-conn)# template template-dhcp Switch(config-cns-conn)# template ip-route Switch(config-cns-conn)# exit Switch(config)# hostname RemoteSwitch RemoteSwitch(config)# cns config initial 10. • • • Note Step 15 Step 16 Step 17 end show cns config connections show running-config Return to privileged EXEC mode. Verify information about the configuration agent.0.1 no-persist Catalyst 2960 and 2960-S Switches Software Configuration Guide.0 0. If the no-persist keyword is not entered. using the cns config initial command causes the resultant configuration to be automatically written to NVRAM.0. enter the port number of the configuration server.0(1)SE 4-11 OL-26520-02 . status url. and inventory keywords are not supported. [port-number] [event] [no-persist] [page page] • For {hostname | ip-address}. The default port number is 80. and initiate an initial configuration. or warning messages when the configuration is finished.0. enter the web page of the initial configuration. enter the hostname or the [source ip-address] [syntax-check] IP address of the configuration server. This example shows how to configure an initial configuration on a remote switch when the switch configuration is unknown (the CNS Zero Touch feature). Release 15. (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.1. The default is /Config/config/asp. • • • (Optional) For port-number. failure. (Optional) Enter source ip-address to use for source IP address. use the no cns config initial {ip-address | hostname} global configuration command. Verify your entries. (Optional) For page page.1.Chapter 4 Configuring Cisco IOS Agents Configuring Cisco IOS Configuration Engine Command Step 14 Purpose cns config initial {hostname | ip-address} Enable the Cisco IOS agent.

Chapter 4 Configuring Cisco IOS Configuration Engine Configuring Cisco IOS Agents This example shows how to configure an initial configuration on a remote switch when the switch IP address is known.22 no-persist Enabling a Partial Configuration Beginning in privileged EXEC mode. (Optional) Enter source ip-address to use for the source IP address. use the cns config cancel privileged EXEC command.1 RemoteSwitch(config)# cns id ethernet 0 ipaddress RemoteSwitch(config)# cns config initial 172. enter the IP address or the hostname of the configuration server. To cancel a partial configuration.11. Though visible in the command-line help string. use the no cns config partial {ip-address | hostname} global configuration command.0.28.0(1)SE OL-26520-02 4-12 . To disable the Cisco IOS agent. Switch(config)# cns template connect template-dhcp Switch(config-tmpl-conn)# cli ip address dhcp Switch(config-tmpl-conn)# exit Switch(config)# cns template connect ip-route Switch(config-tmpl-conn)# cli ip route 0. and initiate a partial configuration.255 11.22 255.11. enter the port number of the configuration server.255.0.0. The default port number is 80.28.129. the encrypt keyword is not supported.0 ${next-hop} Switch(config-tmpl-conn)# exit Switch(config)# cns connect dhcp Switch(config-cns-conn)# discover interface gigabitethernet Switch(config-cns-conn)# template template-dhcp Switch(config-cns-conn)# template ip-route Switch(config-cns-conn)# exit Switch(config)# hostname RemoteSwitch RemoteSwitch(config)# ip route 172. follow these steps to enable the Cisco IOS agent and to initiate a partial configuration on the switch: Command Step 1 Step 2 Purpose Enter global configuration mode. • • • Note configure terminal cns config partial {ip-address | hostname} [port-number] [source ip-address] For {ip-address | hostname}.0.28. Release 15.255.22. Verify information about the configuration agent.0 0. (Optional) Save your entries in the configuration file. (Optional) For port-number.129. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Step 3 Step 4 end show cns config stats or show cns config outstanding show running-config copy running-config startup-config Return to privileged EXEC mode. Enable the configuration agent.129. The Configuration Engine IP address is 172. Step 5 Step 6 Verify your entries.

Chapter 4 Displaying CNS Configuration Configuring Cisco IOS Configuration Engine Displaying CNS Configuration Table 4-2 Privileged EXEC show Commands Command show cns config connections show cns config outstanding show cns config stats show cns event connections show cns event stats show cns event subject Purpose Displays the status of the CNS Cisco IOS agent connections. Displays the status of the CNS event agent connections. Displays information about incremental (partial) CNS configurations that have started but are not yet completed.0(1)SE 4-13 OL-26520-02 . Displays statistics about the Cisco IOS agent. Release 15. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Displays a list of event agent subjects that are subscribed to by applications. Displays statistics about the CNS event agent.

They do not have a FlexStack module slot on the rear of the switch. On a Catalyst 2960-S switch. page 5-14 Managing the ARP Table. depending on the switch model. Catalyst 2960 and 2960-S Switches Software Configuration Guide. or 2960-C switch. 2960-S. page 5-25 Identifying the Switch Image The Catalyst 2960 and 2960-S switches run one of these images: • The LAN base software image provides enterprise-class intelligent services such as access control lists (ACLs) and quality of service (QoS) features. stacking is also supported.0(1)SE OL-26520-02 5-1 . To determine which image your switch is running: • • Switches running the LAN Lite image do not support the FlexStack module. Note Stacking is supported only on Catalyst 2960-S switches running the LAN base image.CH A P T E R 5 Administering the Switch This chapter describes how to perform one-time operations to administer the Catalyst 2960. page 5-9 Creating a Banner. The software image on the switch is either the LAN base or LAN Lite image. This chapter consists of these sections: • • • • • • Identifying the Switch Image. page 5-2 Configuring a System Name and Prompt. The LAN Lite image provides reduced functionality. On the front of the switch. Release 15. Unless otherwise noted. page 5-1 Managing the System Time and Date. • The Catalyst 2960-S ships with a universal image that includes cryptographic functionality. the label in the top right corner ends in -L if the switch model runs the LAN base image and -S if the switch model runs the LAN Lite image. page 5-12 Managing the MAC Address Table. the term switch refers to a standalone switch and to a switch stack.

also known as Greenwich Mean Time (GMT). WS-C2960S-24TS-S is running LAN Lite image. the time is available only for display purposes and is not redistributed. Note For complete syntax and usage information for the commands used in this section.Chapter 5 Managing the System Time and Date Administering the Switch • Enter the show version privileged EXEC command. and see which is the active image: Switch# show license Index 1 Feature: lanlite Period left: 0 minute 0 second Index 2 Feature: lanbase Period left: Life time License Type: Permanent License State: Active. or manual configuration methods. The line that shows the product ID also ends in either -L (if running the LAN base image) or -S (if running the LAN Lite image). For configuration information. WS-C2960S-48PD-L is running LAN base. The system clock keeps track of whether the time is authoritative or not (that is. You can configure information about the local time zone and summer time (daylight saving time) so that the time appears correctly for the local time zone. page 5-5 Configuring Time and Date Manually. For example. Release 15.0(1)SE 5-2 OL-26520-02 . These sections contain this configuration information: • • • • Understanding the System Clock. page 5-5 Understanding the System Clock The heart of the time service is the system clock. whether it has been set by a time source considered to be authoritative). In Use License Priority: Medium License Count: Non-Counted • Managing the System Time and Date You can manage the system time and date on your switch using automatic configuration. see the “Configuring Time and Date Manually” section on page 5-5. Catalyst 2960 and 2960-S Switches Software Configuration Guide. This clock runs from the moment the system starts up and keeps track of the date and time. page 5-2 Understanding Network Time Protocol. If it is not authoritative. The system clock can then be set from these sources: • • NTP Manual configuration User show commands Logging and debugging messages The system clock can provide time to these services: • • The system clock keeps track of time internally based on Universal Time Coordinated (UTC).com. page 5-3 NTP Version 4. see the Cisco IOS Configuration Fundamentals Command Reference on Cisco. Enter the show license privileged EXEC command. such as the Network Time Protocol (NTP).

NTP can be configured to use IP broadcast messages instead. However. An NTP network usually gets its time from an authoritative time source. NTP also compares the time reported by several devices and does not synchronize to a device whose time is significantly different than the others. you should use the security features of NTP to avoid the accidental or malicious setting of an incorrect time. This alternative reduces configuration complexity because each device can simply be configured to send or receive broadcast messages. Accurate timekeeping is possible by exchanging NTP messages between each pair of devices with an association. information flow is one-way only. Release 15. The time kept on a device is a critical resource. We recommend that the time service for your network be derived from the public NTP servers available on the IP Internet.0(1)SE OL-26520-02 5-3 . even if its stratum is lower. Cisco’s implementation of NTP does not support stratum 1 service. NTP then distributes this time across the network. A device running NTP automatically chooses as its time source the device with the lowest stratum number with which it communicates through NTP. NTP is documented in RFC 1305. Two mechanisms are available: an access list-based restriction scheme and an encrypted authentication mechanism. However. This strategy effectively builds a self-organizing tree of NTP speakers. each device is given the IP address of all devices with which it should form associations. NTP is extremely efficient. NTP avoids synchronizing to a device whose time might not be accurate by never synchronizing to a device that is not synchronized. no more than one packet per minute is necessary to synchronize two devices to within a millisecond of one another. which runs over IP. and so on. The communications between devices running NTP (known as associations) are usually statically configured. NTP uses the concept of a stratum to describe how many NTP hops away a device is from an authoritative time source. such as a radio clock or an atomic clock attached to a time server. in a LAN environment. a stratum 2 time server receives its time through NTP from a stratum 1 time server. in that case. it is not possible to connect to a radio or atomic clock. NTP runs over User Datagram Protocol (UDP). Catalyst 2960 and 2960-S Switches Software Configuration Guide.Chapter 5 Administering the Switch Managing the System Time and Date Understanding Network Time Protocol The NTP is designed to time-synchronize a network of devices. A stratum 1 time server has a radio or atomic clock directly attached.

Figure 5-1 Typical NTP Network Configuration Switch A Local workgroup servers Switch B Switch C Switch D Switch E Workstations Switch F Workstations If the network is isolated from the Internet. with Switches B. When multiple sources of time are available. Switch E is configured as an NTP peer to the upstream and downstream switches. C. Switch A is the NTP master. when in fact it has learned the time by using other means. Cisco’s implementation of NTP allows a device to act as if it is synchronized through NTP.0(1)SE 5-4 101349 OL-26520-02 . This software allows host systems to be time-synchronized as well. NTP is always considered to be more authoritative. NTP time overrides the time set by any other method. and a publicly available version for systems running UNIX and its various derivatives is also available. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Release 15. Several manufacturers include NTP software for their host systems. in server association with Switch A. and D configured in NTP server mode. Switch B and Switch F. Other devices then synchronize to that device through NTP.Chapter 5 Managing the System Time and Date Administering the Switch Figure 5-1 shows a typical network example using NTP.

NTPv4 is an extension of NTP version 3.0(1)SE OL-26520-02 5-5 . see the “Disabling NTPv4 Services on a Specific Interface” section of the “Implementing NTPv4 in IPv6” chapter of the Cisco IOS IPv6 Configuration Guide. Release 12. The NTPv4 protocol provides a security framework based on public key cryptography and standard X509 certificates. NTPv4 automatically configures the hierarchy of the servers to achieve the best time accuracy for the lowest bandwidth cost. You cannot disable NTP packets from being received on access ports. The time remains accurate until the next system restart. Configuring Time and Date Manually If no other source of time is available. page 5-7 Configuring Summer Time (Daylight Saving Time). Note You must reset this setting if you have manually set the system clock and the stack master fails and different stack member resumes the role of stack master. page 5-8 Catalyst 2960 and 2960-S Switches Software Configuration Guide. Note You can disable NTP packets from being received on routed ports and VLAN interfaces.4T. Release 15. If you have an outside source to which the switch can synchronize. Improved security compared to NTPv3. page 5-6 Displaying the Time and Date Configuration. you do not need to manually set the system clock. Using specific multicast groups. For details.Chapter 5 Administering the Switch Managing the System Time and Date NTP Version 4 NTP version 4 is implemented on the switch. see the “Implementing NTPv4 in IPv6” chapter of the Cisco IOS IPv6 Configuration Guide. Automatic calculation of the time-distribution hierarchy for a network. page 5-6 Configuring the Time Zone. NTPv4 supports both IPv4 and IPv6 and is backward-compatible with NTPv3. you can manually configure the time and date after the system is restarted. Release 12. We recommend that you use manual configuration only as a last resort. This feature leverages site-local IPv6 multicast addresses.4T. For details about configuring NTPv4. These sections contain this configuration information: • • • • Setting the System Clock. NTPv4 provides these capabilities: • • • Support for IPv6.

on July 23. Until the clock is authoritative and the authoritative flag is set. . Beginning in privileged EXEC mode. use the show clock [detail] privileged EXEC command. you do not need to manually set the system clock. If the time is not authoritative. The system clock keeps an authoritative flag that shows whether the time is authoritative (believed to be accurate). • • • This example shows how to manually set the system clock to 1:32 p. For month. specify the time in hours (24-hour format). the flag is set. (blank)—Time is authoritative. If the system clock has been set by a timing source such as NTP. The time specified is relative to the configured time zone.m. and seconds. For year. minutes. but NTP is not synchronized.0(1)SE 5-6 OL-26520-02 .Chapter 5 Managing the System Time and Date Administering the Switch Setting the System Clock If you have an outside source on the network that provides time services. The symbol that precedes the show clock display has this meaning: • • • *—Time is not authoritative. it is used only for display purposes. such as an NTP server.—Time is authoritative. 2001: Switch# clock set 13:32:00 23 July 2001 Displaying the Time and Date Configuration To display the time and date configuration. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Release 15. follow these steps to set the system clock: Command Step 1 Purpose Manually set the system clock using one of these formats. specify the month by name. specify the day by date in the month. For day. • clock set hh:mm:ss day month year or clock set hh:mm:ss month day year For hh:mm:ss. the flag prevents peers from synchronizing to the clock when the peers’ time is invalid. specify the year (no abbreviation).

Set the time zone. Catalyst 2960 and 2960-S Switches Software Configuration Guide. In this case. • • • configure terminal clock timezone zone hours-offset [minutes-offset] For zone. enter the hours offset from UTC. (Optional) Save your entries in the configuration file. For example. Verify your entries. To set the time to UTC.0(1)SE OL-26520-02 5-7 . Step 3 Step 4 Step 5 end show running-config copy running-config startup-config Return to privileged EXEC mode. use the no clock timezone global configuration command. (Optional) For minutes-offset. so this command is used only for display purposes and when the time is manually set. For hours-offset. where the 3 means 3 hours and . follow these steps to manually configure the time zone: Command Step 1 Step 2 Purpose Enter global configuration mode.5 means 50 percent.Chapter 5 Administering the Switch Managing the System Time and Date Configuring the Time Zone Beginning in privileged EXEC mode. enter the name of the time zone to be displayed when standard time is in effect. the time zone for some sections of Atlantic Canada (AST) is UTC-3. The default is UTC.5. The switch keeps internal time in universal time coordinated (UTC). the necessary command is clock timezone AST -3 30. enter the minutes offset from UTC. Release 15. The minutes-offset variable in the clock timezone global configuration command is available for those cases where a local time zone is a percentage of an hour different from UTC.

0(1)SE 5-8 OL-26520-02 . Monday. the system assumes that you are in the southern hemisphere. specify the day of the week (Sunday. If the starting month is after the ending month. (Optional) For day.). (Optional) For month. and the second part specifies when it ends. configure terminal clock summer-time zone recurring Configure summer time to start and end on the specified days every year. All times are relative to the local time zone. (Optional) For week. specify the time (24-hour format) in hours and minutes. follow these steps to configure summer time (daylight saving time) in areas where it starts and ends on a particular day of the week each year: Command Step 1 Step 2 Purpose Enter global configuration mode. Verify your entries. The default is 60. • • • • • • For zone. If you specify clock summer-time hh:mm [offset]] zone recurring without parameters. The start time is relative to standard time. specify the name of the time zone (for example. PDT) to be displayed when summer time is in effect. specify the number of minutes to add during summer time.Chapter 5 Managing the System Time and Date Administering the Switch Configuring Summer Time (Daylight Saving Time) Beginning in privileged EXEC mode. The end time is relative to summer time. specify the month (January. (Optional) Save your entries in the configuration file.. specify the week of the month (1 to 5 or last). the summer time rules default to the United States rules. Step 3 Step 4 Step 5 end show running-config copy running-config startup-config Return to privileged EXEC mode. This example shows how to specify that summer time starts on the first Sunday in April at 02:00 and ends on the last Sunday in October at 02:00: Switch(config)# clock summer-time PDT recurring 1 Sunday April 2:00 last Sunday October 2:00 Catalyst 2960 and 2960-S Switches Software Configuration Guide. [week day month hh:mm week day month Summer time is disabled by default.. February..). The first part of the clock summer-time global configuration command specifies when summer time begins.. (Optional) For hh:mm. (Optional) For offset. Release 15.

2000. (Optional) For hh:mm. specify the number of minutes to add during summer time. and end on April 26. specify the month (January.). If you are accessing a stack member through the stack master.0(1)SE OL-26520-02 5-9 . The default is 60. at 02:00: Switch(config)# clock summer-time pdt date 12 October 2000 2:00 26 April 2001 2:00 Configuring a System Name and Prompt You configure the system name on the switch to identify it. month year hh:mm date month year • (Optional) For week. configure terminal Configure summer time to start on the first date and end on the second clock summer-time zone date [month date year hh:mm month date year hh:mm date. specify the day of the week (Sunday. By default. Switch-2# is the prompt in privileged EXEC mode for stack member 2. Catalyst 2960 and 2960-S Switches Software Configuration Guide. The start time is relative to standard time. For example. the system name and prompt are Switch. February. Monday. and the second part specifies when it ends. [offset]] Summer time is disabled by default. The prompt is updated whenever the system name changes. at 02:00. the system assumes that you are in the southern hemisphere.. If you have not configured a system prompt. the stack member number is appended to the system prompt. use the no clock summer-time global configuration command. PDT) to be clock summer-time zone date [date displayed when summer time is in effect. specify the week of the month (1 to 5 or last). follow these steps if summer time in your area does not follow a recurring pattern (configure the exact date and time of the next summer time events): Command Step 1 Step 2 Purpose Enter global configuration mode. A greater-than symbol [>] is appended. hh:mm [offset]] • (Optional) For day.Chapter 5 Administering the Switch Configuring a System Name and Prompt Beginning in privileged EXEC mode... you must use the session stack-member-number privileged EXEC command. (Optional) For offset. To disable summer time. specify the name of the time zone (for example. If the starting month is after the ending month. 2001. The end time is relative to summer time. This example shows how to set summer time to start on October 12. Release 15.. Step 3 Step 4 Step 5 end show running-config copy running-config startup-config Return to privileged EXEC mode. • • • (Optional) For month. The first part of the clock summer-time global configuration command specifies when summer time begins. the first 20 characters of the system name are used as the system prompt. (Optional) Save your entries in the configuration file.). specify the time (24-hour format) in hours and minutes. or • For zone. and the system prompt for the switch stack is Switch. All times are relative to the local time zone. When you use this command. The stack member number range is from 1 through 4. Verify your entries.

When you configure DNS on your switch. (Optional) Save your entries in the configuration file. Cisco Systems is a commercial organization that IP identifies by a com domain name. A specific device in this domain. so its domain name is cisco. Domain names are pieced together with periods (.) as the delimiting characters. configure terminal hostname name Step 3 Step 4 Step 5 end show running-config copy running-config startup-config Return to privileged EXEC mode. you can substitute the hostname for the IP address with all IP commands. IP defines a hierarchical naming scheme that allows a device to be identified by its location or domain. follow these steps to manually configure a system name: Command Step 1 Step 2 Purpose Enter global configuration mode. telnet. and related Telnet support operations. Release 15. page 5-10 Default System Name and Prompt Configuration The default switch system name and prompt is Switch. see the Cisco IOS Configuration Fundamentals Command Reference and the Cisco IOS IP Command Reference. end with a letter or digit. such as ping. When you set the system name. They must start with a letter. a distributed database with which you can map hostnames to IP addresses. for example. page 5-10 Configuring a System Name. The name must follow the rules for ARPANET hostnames. page 5-10 Understanding DNS. To return to the default hostname.0(1)SE 5-10 OL-26520-02 . Names can be up to 63 characters. Volume 2 of 3: Routing Protocols. use the no hostname global configuration command. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Verify your entries.com.Chapter 5 Configuring a System Name and Prompt Administering the Switch For complete syntax and usage information for the commands used in this section. it is also used as the system prompt. For example. and have as interior characters only letters. Understanding DNS The DNS protocol controls the Domain Name System (DNS).cisco. Configuring a System Name Beginning in privileged EXEC mode. Manually configure a system name. digits. connect. The default setting is switch. These sections contain this configuration information: • • • Default System Name and Prompt Configuration. and hyphens.com. the File Transfer Protocol (FTP) system is identified as ftp.

You can specify up to six name servers. page 5-12 Default DNS Configuration Table 5-1 shows the default DNS configuration. Release 15. page 5-11 Setting Up DNS. Table 5-1 Default DNS Configuration Feature DNS enable state DNS default domain name DNS servers Default Setting Enabled.0(1)SE OL-26520-02 5-11 . Separate each server address with a space. the backup servers are queried. Setting Up DNS Beginning in privileged EXEC mode. None configured. No name server addresses are configured. To map domain names to IP addresses. If that query fails. follow these steps to set up your switch to use the DNS: Command Step 1 Step 2 Purpose Enter global configuration mode.Chapter 5 Administering the Switch Configuring a System Name and Prompt To keep track of domain names. This feature is enabled by default. if the switch configuration comes from a BOOTP or Dynamic Host Configuration Protocol (DHCP) server. configure terminal ip domain-name name Step 3 ip name-server server-address1 [server-address2 . you can dynamically assign device names that uniquely identify your devices by using the global Internet naming scheme (DNS). specify the name server that is present on your network. Define a default domain name that the software uses to complete unqualified hostnames (names without a dotted-decimal domain name). page 5-11 Displaying the DNS Configuration.. Step 4 ip domain-lookup Catalyst 2960 and 2960-S Switches Software Configuration Guide. IP has defined the concept of a domain name server. Do not include the initial period that separates an unqualified name from the domain name. If your network devices require connectivity with devices in networks for which you do not control name assignment. At boot-up time. no domain name is configured. then the default domain name might be set by the BOOTP or DHCP server (if the servers were configured with this information). which holds a cache (or database) of names mapped to IP addresses. (Optional) Enable DNS-based hostname-to-address translation on your switch.. however. you must first identify the hostnames. The first server specified is the primary server. These sections contain this configuration information: • • • Default DNS Configuration. server-address6] Specify the address of one or more name servers to use for name and address resolution. and enable the DNS. The switch sends DNS queries to the primary server first.

Chapter 5 Creating a Banner Administering the Switch Command Step 5 Step 6 Step 7 Purpose Return to privileged EXEC mode. use the show running-config privileged EXEC command. end show running-config copy running-config startup-config If you use the switch IP address as its hostname. page 5-14 Default Banner Configuration The MOTD and login banners are not configured. If there is a period (. The default domain name is the value set by the ip domain-name global configuration command. use the no ip domain-lookup global configuration command. If you configure a hostname that contains no periods (.) in the hostname. To remove a domain name.).0(1)SE 5-12 OL-26520-02 . The login banner also displays on all connected terminals. Release 12. (Optional) Save your entries in the configuration file. the IP address is used and no DNS query occurs. use the no ip name-server server-address global configuration command. The MOTD banner displays on all connected terminals at login and is useful for sending messages that affect all network users (such as impending system shutdowns).4 on Cisco. Displaying the DNS Configuration To display the DNS configuration information. To disable DNS on the switch. Verify your entries. see the Cisco IOS Configuration Fundamentals Command Reference. Release 15. It appears after the MOTD banner and before the login prompts. a period followed by the default domain name is appended to the hostname before the DNS query is made to map the name to an IP address. use the no ip domain-name name global configuration command.com. Note For complete syntax and usage information for the commands used in this section. Creating a Banner You can configure a message-of-the-day (MOTD) and a login banner. page 5-12 Configuring a Message-of-the-Day Login Banner. To remove a name server address. These sections contain this configuration information: • • • Default Banner Configuration. page 5-13 Configuring a Login Banner. the Cisco IOS software looks up the IP address without appending any default domain name to the hostname. Catalyst 2960 and 2960-S Switches Software Configuration Guide.

follow these steps to configure a MOTD login banner: Command Step 1 Step 2 Purpose Enter global configuration mode. a pound sign (#). for example. For c. Connected to 172.Chapter 5 Administering the Switch Creating a Banner Configuring a Message-of-the-Day Login Banner You can create a single or multiline message banner that appears on the screen when someone logs in to the switch. # Switch(config)# This example shows the banner that appears from the previous configuration: Unix> telnet 172.2. Characters after the ending delimiter are discarded. contact technical support. (Optional) Save your entries in the configuration file. For access. Only authorized users are allowed. enter the delimiting character of your choice.0(1)SE OL-26520-02 5-13 . This example shows how to configure a MOTD banner for the switch by using the pound sign (#) symbol as the beginning and ending delimiter: Switch(config)# banner motd # This is a secure site.. contact technical support. Escape character is '^]'. For message..4.2. The delimiting character signifies the beginning and end of the banner text.5. use the no banner motd global configuration command. Only authorized users are allowed.2. enter a banner message up to 255 characters. Verify your entries. You cannot use the delimiting character in the message.4.5. User Access Verification Password: Catalyst 2960 and 2960-S Switches Software Configuration Guide. To delete the MOTD banner.5. Release 15. configure terminal banner motd c message c Step 3 Step 4 Step 5 end show running-config copy running-config startup-config Return to privileged EXEC mode. This is a secure site. For access.4 Trying 172. Specify the message of the day. and press the Return key. Beginning in privileged EXEC mode.

and port number associated with the address and the type (static or dynamic). The delimiting character signifies the beginning and end of the banner text. To delete the login banner. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Beginning in privileged EXEC mode. For c. This banner appears after the MOTD banner and before the login prompt. Verify your entries. The address table lists the destination MAC address. $ Switch(config)# Managing the MAC Address Table The MAC address table contains address information that the switch uses to forward traffic between ports. use the no banner login global configuration command. All MAC addresses in the address table are associated with one or more ports.Chapter 5 Managing the MAC Address Table Administering the Switch Configuring a Login Banner You can configure a login banner to be displayed on all connected terminals. For message. enter a login message up to 255 characters. (Optional) Save your entries in the configuration file.0(1)SE 5-14 OL-26520-02 . The address table includes these types of addresses: • • Dynamic address: a source MAC address that the switch learns and then ages when it is not in use. You cannot use the delimiting character in the message. follow these steps to configure a login banner: Command Step 1 Step 2 Purpose Enter global configuration mode. Release 15. for example. Please enter your username and password. Static address: a manually entered unicast address that does not age and that is not lost when the switch resets. Specify the login message. configure terminal banner login c message c Step 3 Step 4 Step 5 end show running-config copy running-config startup-config Return to privileged EXEC mode. enter the delimiting character of your choice. and press the Return key. see the command reference for this release. Note For complete syntax and usage information for the commands used in this section. a pound sign (#). the associated VLAN ID. Characters after the ending delimiter are discarded. This example shows how to configure a login banner for the switch by using the dollar sign ($) symbol as the beginning and ending delimiter: Switch(config)# banner login $ Access for authorized users only.

or other network devices. Unicast addresses. Catalyst 2960 and 2960-S Switches Software Configuration Guide. page 5-24 Building the Address Table With multiple MAC addresses supported on all ports. page 5-19 Configuring MAC Threshold Notification Traps. As stations are added or removed from the network.Chapter 5 Administering the Switch Managing the MAC Address Table These sections contain this configuration information: • • • • • • • • • • • • • Building the Address Table. based on the destination address of the received packet. switches. An address can exist in more than one VLAN and have different destinations in each. page 5-15 MAC Addresses and Switch Stacks. and STP can accelerate the aging interval on a per-VLAN basis. Using the MAC address table. for example. page 5-16 Removing Dynamic Address Entries. page 5-16 Default MAC Address Table Configuration. The switch always uses the store-and-forward method: complete packets are stored and checked for errors before transmission. page 5-21 Configuring Unicast MAC Address Filtering. The switch provides dynamic addressing by learning the source address of packets it receives on each port and adding the address and its associated port number to the address table. The aging interval is globally configured on a standalone switch or on the switch stack. page 5-23 Displaying Address Table Entries. the switch updates the address table. The switch sends packets between any combination of ports. However. A known address in one VLAN is unknown in another until it is learned or statically associated with a port in the other VLAN. repeaters. page 5-20 Adding and Removing Static Address Entries. page 5-17 Configuring MAC Address Move Notification Traps. If the destination address is on the port that sent the packet. page 5-22 Disabling MAC Address Learning on a VLAN. page 5-15 MAC Addresses and VLANs. 10. the switch forwards the packet only to the port associated with the destination address. you can connect any port on the switch to individual workstations. the switch maintains an address table for each VLAN. MAC Addresses and VLANs All addresses are associated with a VLAN. Each VLAN maintains its own logical address table. page 5-17 Configuring MAC Address Change Notification Traps. adding new dynamic addresses and aging out those that are not in use.0(1)SE OL-26520-02 5-15 . Release 15. and 1 in VLAN 5. could be forwarded to port 1 in VLAN 1 and ports 9. page 5-16 Changing the Address Aging Time. the packet is filtered and not forwarded. routers.

which can impact switch performance. the address is removed from the address tables on all stack members. each stack member has the same copy of the address tables for each VLAN. follow these steps to configure the dynamic address table aging time: Command Step 1 Step 2 Purpose Enter global configuration mode.Chapter 5 Managing the MAC Address Table Administering the Switch MAC Addresses and Switch Stacks The MAC address tables on all stack members are synchronized. You can also enter 0. The default is 300. the remaining stack members age out or remove all addresses learned by the former stack member. that switch receives the addresses for each VLAN learned on the other stack members. which disables aging. At any given time. To return to the default value. Setting too short an aging time can cause addresses to be prematurely removed from the table.0(1)SE 5-16 OL-26520-02 . Beginning in privileged EXEC mode. Release 15. Flooding results. configure terminal mac address-table aging-time [0 | 10-1000000] [vlan vlan-id] Step 3 Step 4 Step 5 end show mac address-table aging-time copy running-config startup-config Return to privileged EXEC mode. When a stack member leaves the switch stack. valid IDs are 1 to 4094. which prevents new addresses from being learned. it floods the packet to all ports in the same VLAN as the receiving port. Catalyst 2960 and 2960-S Switches Software Configuration Guide. (Optional) Save your entries in the configuration file. use the no mac address-table aging-time global configuration command. Verify your entries. Static address entries are never aged or removed from the table. For vlan-id. The range is 10 to 1000000 seconds. Then when the switch receives a packet for an unknown destination. When an address ages out. You can change the aging time setting for all VLANs or for a specified VLAN. Default MAC Address Table Configuration Table 5-2 shows the default MAC address table configuration. Setting too long an aging time can cause the address table to be filled with unused addresses. Set the length of time that a dynamic entry remains in the MAC address table after the entry is used or updated. When a switch joins a switch stack. This unnecessary flooding can impact performance. Table 5-2 Default MAC Address Table Configuration Feature Aging time Dynamic addresses Static addresses Default Setting 300 seconds Automatically learned None configured Changing the Address Aging Time Dynamic addresses are source MAC addresses that the switch learns and then ages when they are not in use.

is not available with informs. MAC address change notifications are generated for dynamic and secure MAC addresses. For notification-type. You can also remove a specific MAC address (clear mac address-table dynamic address mac-address). remove all addresses on the specified physical port or port channel (clear mac address-table dynamic interface interface-id). Notifications are not generated for self addresses. Catalyst 2960 and 2960-S Switches Software Configuration Guide. use the show mac address-table dynamic privileged EXEC command. • Specify traps (the default) to send SNMP traps to the host. Version 1. To verify that dynamic entries have been removed. configure terminal snmp-server host host-addr {traps | informs} {version {1 Specify the recipient of the trap message. Specify the SNMP version to support. Release 15. an SNMP notification trap can be sent to the NMS. or remove all addresses on a specified VLAN (clear mac address-table dynamic vlan vlan-id). specify the name or address of the NMS. Configuring MAC Address Change Notification Traps MAC address change notification tracks users on a network by storing the MAC address change activity. the default. you can set a trap-interval time to bundle the notification traps to reduce network traffic.Chapter 5 Administering the Switch Managing the MAC Address Table Removing Dynamic Address Entries To remove all dynamic entries. The MAC notification history table stores MAC address activity for each port for which the trap is set. Though you can set this string by using the snmp-server host command. If you have many users coming and going from the network. use the mac-notification keyword. When the switch learns or removes a MAC address. specify the string to send with the notification operation. Beginning in privileged EXEC mode. | 2c | 3}} community-string notification-type • For host-addr. use the clear mac address-table dynamic command in privileged EXEC mode. Enable the MAC address change notification feature. multicast addresses. • • • Step 3 Step 4 snmp-server enable traps mac-notification change mac address-table notification change Enable the switch to send MAC address change notification traps to the NMS.0(1)SE OL-26520-02 5-17 . Specify informs to send SNMP informs to the host. or other static addresses. For community-string. we recommend that you define this string by using the snmp-server community command before using the snmp-server host command. follow these steps to configure the switch to send MAC address change notification traps to an NMS host: Command Step 1 Step 2 Purpose Enter global configuration mode.

(Optional) Save your entries in the configuration file. • Step 6 interface interface-id Enter interface configuration mode. Enable the MAC address change notification trap on the interface.10. • • Step 7 snmp trap mac-notification change {added | removed} Enable the trap when a MAC address is added on this interface. Catalyst 2960 and 2960-S Switches Software Configuration Guide. use the no snmp-server enable traps mac-notification change global configuration command. specify the notification trap interval in seconds between each set of traps that are generated to the NMS. Step 8 Step 9 end show mac address-table notification change interface show running-config copy running-config startup-config Return to privileged EXEC mode. Verify your entries. use the no mac address-table notification change global configuration command. The range is 0 to 2147483647 seconds.10. Step 10 To disable MAC address-change notification traps. the default is 1. To disable the MAC address-change notification traps on a specific interface. Enable the trap when a MAC address is removed from this interface. use the no snmp trap mac-notification change {added | removed} interface configuration command.10 as the NMS. set the interval time to 123 seconds. • mac address-table notification change [interval value] [history-size value] (Optional) For interval value. Release 15. To disable the MAC address-change notification feature. and specify the interface on which to enable the SNMP MAC address notification trap. The range is 0 to 500. (Optional) For history-size value. the default is 1 second. enable the MAC address-change notification feature.Chapter 5 Managing the MAC Address Table Administering the Switch Command Step 5 Purpose Enter the trap interval time and the history table size. Switch(config)# snmp-server host 172. set the history-size to 100 entries. and enable traps whenever a MAC address is added on the specified port.20.10 traps private mac-notification Switch(config)# snmp-server enable traps mac-notification change Switch(config)# mac address-table notification change Switch(config)# mac address-table notification change interval 123 Switch(config)# mac address-table notification change history-size 100 Switch(config)# interface gigabitethernet1/0/2 Switch(config-if)# snmp trap mac-notification change added You can verify your settings by entering the show mac address-table notification change interface and the show mac address-table notification change privileged EXEC commands.20. specify the maximum number of entries in the MAC notification history table. enable the switch to send MAC address notification traps to the NMS. This example shows how to specify 172.0(1)SE 5-18 OL-26520-02 .

use the mac-notification keyword.10. Verify your entries. Enable the MAC address move notification feature. | 2c | 3}} community-string notification-type • For host-addr. Switch(config)# snmp-server host 172. enable the switch to send MAC address move notification traps to the NMS. Catalyst 2960 and 2960-S Switches Software Configuration Guide.20. and enable traps when a MAC address moves from one port to another. • Specify traps (the default) to send SNMP traps to the host.20. Specify informs to send SNMP informs to the host. is not available with informs. we recommend that you define this string by using the snmp-server community command before using the snmp-server host command. Beginning in privileged EXEC mode. • • • Step 3 Step 4 Step 5 Step 6 snmp-server enable traps mac-notification move mac address-table notification mac-move end show mac address-table notification mac-move show running-config copy running-config startup-config Enable the switch to send MAC address move notification traps to the NMS. Release 15.10 as the NMS. follow these steps to configure the switch to send MAC address-move notification traps to an NMS host: Command Step 1 Step 2 Purpose Enter global configuration mode. For notification-type. configure terminal snmp-server host host-addr {traps | informs} {version {1 Specify the recipient of the trap message. enable the MAC address move notification feature. To disable the MAC address-move notification feature. specify the name or address of the NMS. This example shows how to specify 172. Version 1. use the no snmp-server enable traps mac-notification move global configuration command. Return to privileged EXEC mode. use the no mac address-table notification mac-move global configuration command. an SNMP notification is generated and sent to the network management system whenever a MAC address moves from one port to another within the same VLAN.10. Step 7 To disable MAC address-move notification traps. the default.Chapter 5 Administering the Switch Managing the MAC Address Table Configuring MAC Address Move Notification Traps When you configure MAC-move notification.10 traps private mac-notification Switch(config)# snmp-server enable traps mac-notification move Switch(config)# mac address-table notification mac-move You can verify your settings by entering the show mac address-table notification mac-move privileged EXEC commands. specify the string to send with the notification operation. (Optional) Save your entries in the configuration file. Specify the SNMP version to support. For community-string.0(1)SE OL-26520-02 5-19 . Though you can set this string by using the snmp-server host command.

an SNMP notification is generated and sent to the network management system when a MAC address table threshold limit is reached or exceeded. specify the name or address of the NMS. specify the string to send with the notification operation. Enable the MAC address threshold notification feature. Enter the threshold value for the MAC address threshold usage monitoring. the default. Verify your entries. (Optional) For interval time. For notification-type. Release 15. follow these steps to configure the switch to send MAC address table threshold notification traps to an NMS host: Command Step 1 Step 2 Purpose Enter global configuration mode. | 2c | 3}} community-string notification-type • For host-addr. • Specify traps (the default) to send SNMP traps to the host. (Optional) Save your entries in the configuration file. specify the percentage of the MAC address table use. • (Optional) For limit percentage. use the mac-notification keyword.0(1)SE 5-20 OL-26520-02 . is not available with informs. Specify the SNMP version to support. Catalyst 2960 and 2960-S Switches Software Configuration Guide. • • • Step 3 Step 4 Step 5 snmp-server enable traps mac-notification threshold mac address-table notification threshold mac address-table notification threshold [limit percentage] | [interval time] Enable the switch to send MAC threshold notification traps to the NMS. configure terminal snmp-server host host-addr {traps | informs} {version {1 Specify the recipient of the trap message. valid values are greater than or equal to 120 seconds. Though you can set this string by using the snmp-server host command.Chapter 5 Managing the MAC Address Table Administering the Switch Configuring MAC Threshold Notification Traps When you configure MAC threshold notification. valid values are from 1 to 100 percent. • Step 6 Step 7 Step 8 end show mac address-table notification threshold show running-config copy running-config startup-config Return to privileged EXEC mode. For community-string. Beginning in privileged EXEC mode. Specify informs to send SNMP informs to the host. The default is 50 percent. specify the time between notifications. The default is 120 seconds. Version 1. we recommend that you define this string by using the snmp-server community command before using the snmp-server host command.

you can enter only one interface at a time.10 as the NMS. and set the limit to 78 per cent.10. Packets with this destination address received in the specified VLAN are forwarded to the specified interface. Adding and Removing Static Address Entries A static address has these characteristics: • • • It is manually entered in the address table and must be manually removed.10 traps private mac-notification snmp-server enable traps mac-notification threshold mac address-table notification threshold mac address-table notification threshold interval 123 mac address-table notification threshold limit 78 You can verify your settings by entering the show mac address-table notification threshold privileged EXEC commands. use the no snmp-server enable traps mac-notification threshold global configuration command. Add a static address to the MAC address table. but you can enter the command multiple times with the same MAC address and VLAN ID. Beginning in privileged EXEC mode. A packet with a static address that arrives on a VLAN where it has not been statically entered is flooded to all ports and not learned. You can specify a different list of destination ports for each source port. you can enter multiple interface IDs. This example shows how to specify 172. You can add and remove static addresses and define the forwarding behavior for them. Release 15. specify the VLAN for which the packet with the specified MAC address is received. For static multicast addresses.0(1)SE OL-26520-02 5-21 .20. You add a static address to the address table by specifying the destination MAC unicast address and the VLAN from which it is received. It can be a unicast or multicast address. Packets received with this destination address are forwarded to the interface specified with the interface-id option. To disable the MAC address-threshold notification feature. For interface-id. • configure terminal mac address-table static mac-addr vlan vlan-id interface interface-id For mac-addr. Valid interfaces include physical ports or port channels. enable the MAC address threshold notification feature. • • Catalyst 2960 and 2960-S Switches Software Configuration Guide. the switch acquires the VLAN ID for the address from the ports that you specify. Switch(config)# Switch(config)# Switch(config)# Switch(config)# Switch(config)# snmp-server host 172. use the no mac address-table notification threshold global configuration command.10. specify the interface to which the received packet is forwarded.Chapter 5 Administering the Switch Managing the MAC Address Table To disable MAC address-threshold notification traps. For static unicast addresses. Valid VLAN IDs are 1 to 4094. specify the destination MAC unicast address to add to the address table. set the interval time to 123 seconds. It does not age and is retained when the switch restarts.20. For vlan-id. Because all ports are associated with at least one VLAN. The forwarding behavior defines how a port that receives a packet forwards it to another port for transmission. follow these steps to add a static address: Command Step 1 Step 2 Purpose Enter global configuration mode.

0(1)SE 5-22 OL-26520-02 . (Optional) Save your entries in the configuration file. Follow these guidelines when using this feature: • Multicast MAC addresses. use the no mac address-table static mac-addr vlan vlan-id [interface interface-id] global configuration command. If you enter the mac address-table static mac-addr vlan vlan-id drop global configuration command followed by the mac address-table static mac-addr vlan vlan-id interface interface-id command.220a. For example. You enable unicast MAC address filtering and configure the switch to drop packets with a specific address by specifying the source or destination unicast MAC address and the VLAN from which it is received. If you specify one of these addresses when entering the mac address-table static mac-addr vlan vlan-id drop global configuration command.Chapter 5 Managing the MAC Address Table Administering the Switch Command Step 3 Step 4 Step 5 Purpose Return to privileged EXEC mode. The second command that you entered overrides the first command. if you enter the mac address-table static mac-addr vlan vlan-id interface interface-id global configuration command followed by the mac address-table static mac-addr vlan vlan-id drop command. When a packet is received in VLAN 4 with this MAC address as its destination address. the switch either adds the MAC address as a static address or drops packets with that MAC address. the packet is forwarded to the specified port: Switch(config)# mac address-table static c2f3. This feature is disabled by default and only supports unicast static addresses.220a. the switch drops packets with specific source or destination MAC addresses. one of these messages appears: % Only unicast addresses can be configured to be dropped % CPU destined address cannot be configured as drop address • • Packets that are forwarded to the CPU are also not supported.12f4 to the MAC address table. the switch drops packets with the specified MAC address as a source or destination. Catalyst 2960 and 2960-S Switches Software Configuration Guide. broadcast MAC addresses. depending on which command was entered last. This example shows how to add the static address c2f3. If you add a unicast MAC address as a static address and configure unicast MAC address filtering. and router MAC addresses are not supported. Release 15. Verify your entries. the switch adds the MAC address as a static address. end show mac address-table static copy running-config startup-config To remove static entries from the address table.12f4 vlan 4 interface gigabitethernet1/0/1 Configuring Unicast MAC Address Filtering When unicast MAC address filtering is enabled.

You cannot disable MAC address learning on a VLAN that is used internally by the switch. specify the VLAN for which the packet with the specified MAC address is received. no mac address-table learning vlan 1-20. This example shows how to enable unicast MAC address filtering and to configure the switch to drop packets that have a source or destination address of c2f3. • • Catalyst 2960 and 2960-S Switches Software Configuration Guide.Chapter 5 Administering the Switch Managing the MAC Address Table Beginning in privileged EXEC mode. You can control MAC address learning on a VLAN to manage the available MAC address table space by controlling which VLANs.220a. and therefore which ports. We recommend that you disable MAC address learning only in VLANs with two ports. specify a source or destination unicast MAC address. Packets with this MAC address are dropped. every packet entering the switch is flooded in that VLAN domain. be sure that you are familiar with the network topology and the switch system configuration. 15). Step 3 Step 4 Step 5 end show mac address-table static copy running-config startup-config Return to privileged EXEC mode. Disabling MAC address learning on a VLAN could cause flooding in the network. • • configure terminal mac address-table static mac-addr vlan vlan-id drop For mac-addr. Enable unicast MAC address filtering and configure the switch to drop a packet with the specified source or destination unicast static address. If the VLAN ID that you enter is an internal VLAN.12f4 vlan 4 drop Disabling MAC Address Learning on a VLAN By default. the switch generates an error message and rejects the command.220a. If you disable MAC address learning on a VLAN with more than two ports. Use caution before disabling MAC address learning on a VLAN with a configured switch virtual interface (SVI). Valid VLAN IDs are 1 to 4094. You can disable MAC address learning on a single VLAN ID (for example. Verify your entries. For vlan-id. When a packet is received in VLAN 4 with this MAC address as its source or destination. no mac address-table learning vlan 223) or on a range of VLAN IDs (for example. The switch then floods all IP packets in the Layer 2 domain. (Optional) Save your entries in the configuration file. Release 15. Follow these guidelines when disabling MAC address learning on a VLAN: • • • Disabling MAC address learning on a VLAN is supported only if the switch is running the IP Services or LAN base image. Before you disable MAC address learning.12f4. follow these steps to configure the switch to drop a source or destination unicast static address: Command Step 1 Step 2 Purpose Enter global configuration mode. enter the show vlan internal usage privileged EXEC command.0(1)SE OL-26520-02 5-23 . use the no mac address-table static mac-addr vlan vlan-id global configuration command. the packet is dropped: Switch(config)# mac a ddress-table static c2f3. can learn MAC addresses. To disable unicast MAC address filtering. MAC address learning is enabled on all VLANs on the switch. To view internal VLANs in use.

Displaying Address Table Entries You can display the MAC address table by using one or more of the privileged EXEC commands described in Table 5-3: Table 5-3 Commands for Displaying the MAC Address Table Command show ip igmp snooping groups show mac address-table address show mac address-table aging-time show mac address-table count Description Displays the Layer 2 multicast entries for all VLANs or the specified VLAN. MAC address learning occurs on the primary VLAN and is replicated on the secondary VLAN. configure terminal no mac address-table learning vlan vlan-id end Step 3 Step 4 Step 5 show mac address-table learning [vlan Verify the configuration. • • Beginning in privileged EXEC mode. Release 15. the configured MAC address learning state is enabled.0(1)SE 5-24 OL-26520-02 . vlan-id] copy running-config startup-config (Optional) Save your entries in the configuration file. Displays the number of addresses present in all VLANs or the specified VLAN. follow these steps to disable MAC address learning on a VLAN: Command Step 1 Step 2 Purpose Enter global configuration mode. MAC addresses are still learned on the secondary VLAN that belongs to the private VLAN and are then replicated on the primary VLAN. The configuration is not allowed. If you disable port security. You can also reenable MAC address learning on a VLAN by entering the mac address-table learning vlan vlan-id global configuration command. The second command causes the configuration to appear in the show running-config privileged EXEC command display. You cannot disable MAC address learning on an RSPAN VLAN. You can specify a single VLAN ID or a range of VLAN IDs separated by a hyphen or comma. Catalyst 2960 and 2960-S Switches Software Configuration Guide. If you disable MAC address learning on the secondary VLAN. Valid VLAN IDs are 1 to 4094. This example shows how to disable MAC address learning on VLAN 200: Switch(config)# no mac a ddress-table learning vlan 200 You can display the MAC address learning status of all VLANs or a specified VLAN by entering the show mac-address-table learning [vlan vlan-id] privileged EXEC command. MAC address learning is not disabled on that port. use the default mac address-table learning vlan vlan-id global configuration command. If you disable MAC address learning on a VLAN that includes a secure port. Displays the aging time in all VLANs or the specified VLAN. Disable MAC address learning on the specified VLAN or VLANs. The first (default) command returns to a default condition and therefore does not appear in the output from the show running-config command. To reenable MAC address learning on a VLAN. Displays MAC address table information for the specified MAC address. Return to privileged EXEC mode.Chapter 5 Managing the MAC Address Table Administering the Switch • If you disable MAC address learning on a VLAN configured as a private-VLAN primary VLAN. but not the primary VLAN of a private VLAN.

Chapter 5 Administering the Switch Managing the ARP Table Table 5-3 Commands for Displaying the MAC Address Table (continued) Command show mac address-table dynamic show mac address-table interface show mac address-table learning show mac address-table notification show mac address-table static show mac address-table vlan Description Displays only dynamic MAC address table entries. Encapsulation of IP datagrams and ARP requests and replies on IEEE 802 networks other than Ethernet is specified by the Subnetwork Access Protocol (SNAP). Catalyst 2960 and 2960-S Switches Software Configuration Guide. the software first must learn the 48-bit MAC address or the local data link address of that device. see the Cisco IOS Release 12. By default. Displays the MAC address table information for the specified VLAN. Note For CLI procedures.4 documentation on Cisco. Then the IP datagram is encapsulated in a link-layer frame and sent over the network. Release 15. Displays the MAC address table information for the specified interface. Displays MAC address learning status of all VLANs or the specified VLAN. ARP entries added manually to the table do not age and must be manually removed. Managing the ARP Table To communicate with a device (over Ethernet. ARP finds the associated MAC address. Using an IP address.0(1)SE OL-26520-02 5-25 .com. the IP-MAC address association is stored in an ARP cache for rapid retrieval. standard Ethernet-style ARP encapsulation (represented by the arpa keyword) is enabled on the IP interface. When a MAC address is found. for example). The process of learning the local data link address from an IP address is called address resolution. Displays the MAC notification parameters and history table. Displays only static MAC address table entries. The Address Resolution Protocol (ARP) associates a host IP address with the corresponding media or MAC addresses and the VLAN ID.

0(1)SE 5-26 OL-26520-02 . Release 15.Chapter 5 Managing the ARP Table Administering the Switch Catalyst 2960 and 2960-S Switches Software Configuration Guide.

Note Network Assistant supports switch clusters. available on Cisco. including introductory information on managing switch clusters and converting a switch cluster to a community. Access should be controlled through the cluster command switch or by applying access control lists (ACLs) on interfaces that are configured with IP address. Unless otherwise noted. “Configuring Network Security with ACLs. page 6-4 Using the CLI to Manage Switch Clusters. For complete procedures. Network Assistant has a Cluster Conversion Wizard to help you convert a cluster to a community.CH A P T E R 6 Clustering Switches This chapter provides the concepts and procedures to create and manage Catalyst 2960. For more information on ACLs. but we recommend that you instead group switches into communities. but it does not provide complete descriptions of the cluster features for these other switches. see the online help. page 6-16 Using SNMP to Manage Switch Clusters. You can create and manage switch clusters by using Cisco Network Assistant (hereafter known as Network Assistant). the command-line interface (CLI). It also includes guidelines and limitations for clusters mixed with other cluster-capable Catalyst switches. Release 15. This chapter focuses on Catalyst 2960. 2960-S or and 2960-C switch clusters.com. Note Stacking is supported only on Catalyst 2960-S switches running the LAN base image. refer to the software configuration guide for that switch. For the CLI cluster commands. or SNMP. This chapter consists of these sections: • • • • Understanding Switch Clusters. see Getting Started with Cisco Network Assistant. 2960-S or and 2960-C switch clusters. For more information about Network Assistant. page 6-17 Note We do not recommend using the ip http access-class global configuration command to limit access to specific hosts or networks.0(1)SE OL-26520-02 6-1 . Catalyst 2960 and 2960-S Switches Software Configuration Guide. page 6-2 Planning a Switch Cluster.”. For complete cluster information for a specific Catalyst platform. see Chapter 31. the term switch refers to a standalone switch and to a switch stack. see the switch command reference.

see the “Switch Clusters and Switch Stacks” section on page 6-14.1(19)EA1b or later 12. The switches can be in the same location. and Catalyst 3500 XL switches.1(11)AX or later 12. and monitor the cluster member switches. A cluster standby group is a group of standby cluster command switches. Catalyst 2950. For more information about how switch stacks differ from switch clusters. and the required software versions. Catalyst 3560. Stacking is supported only on Catalyst 2960-S switches running the LAN base image. For complete information about these switches in a switch-cluster environment. Catalyst 2820. The benefits of clustering switches include: • Management of Catalyst switches regardless of their interconnection media and their physical locations.1(4)EA1 or later 12.0(1)SE 6-2 OL-26520-02 . This conserves on IP addresses. refer to the software configuration guide for that specific switch.2(46)EX or later 12. All communication with the switch cluster is through the cluster command switch IP address. Table 6-1 Switch Software and Cluster Capability Switch Catalyst 3750-E or Catalyst 3560-E Catalyst 3750 Catalyst 3560 Catalyst 3550 Catalyst 2975 Catalyst 2970 Cisco IOS Release 12. including which ones can be cluster command switches and which ones can only be cluster member switches. or they can be distributed across a Layer 2 or Layer 3 (if your cluster is using a Catalyst 3550. In a switch cluster. especially if you have a limited number of them. Release 15. The cluster command switch is the single point of access used to configure. One or more switches can be designated as standby cluster command switches to avoid loss of contact with cluster members.1(11)AX or later Cluster Capability Member or command switch Member or command switch Member or command switch Member or command switch Member or command switch Member or command switch Member or command switch Catalyst 3750-X or Catalyst 3560-X 12.2(53)SE2 or later Catalyst 2960 and 2960-S Switches Software Configuration Guide. The total number of switches in a cluster cannot exceed 16 switches. cluster-capable Catalyst switches that are managed as a single entity. or Catalyst 3750 switch as a Layer 3 router between the Layer 2 switches in the cluster) network. • Table 6-1 lists the Catalyst switches eligible for switch clustering. 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 6-5. • Command-switch redundancy if a cluster command switch fails. Management of a variety of Catalyst switches through a single IP address. This section includes management VLAN considerations for the Catalyst 1900.2(35)SE2 or later 12. Note A switch cluster is different from a switch stack. 1 switch must be the cluster command switch and up to 15 other switches can be cluster member switches.Chapter 6 Understanding Switch Clusters Clustering Switches Understanding Switch Clusters A switch cluster is a set of up to 16 connected. A switch stack is a set of Catalyst 2960-S switches connected through their stack ports. Catalyst 2900 XL. Cluster members can belong to only one cluster at a time. 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. manage.

1(13)AY or later 12.2)WC(1) or later 12. Standby Cluster Command Switch Characteristics A standby cluster command switch must meet these requirements: • • • • • • • It is running Cisco IOS 12.1)XU or later 11.0(5.2(8. It has Cisco Discovery Protocol (CDP) version 2 enabled (the default). It has an IP address.1)XU or later 12.2(53)SE or later 12.0(5. 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. or Cisco IOS Release 12. It has CDP version 2 enabled.5)SA6 (recommended) 9.0(5. Catalyst 2960 and 2960-S Switches Software Configuration Guide. It has an IP address.2(53)SE or later for a Catalyst 2960-S switch.0(1)SE OL-26520-02 6-3 .2(53)SE or later for a Catalyst 2960-S switch. It is connected to all other cluster member switches (except the cluster command and standby command switches) through a common VLAN. It is connected to the standby cluster command switches through the management VLAN and to the cluster member switches through a common VLAN.2(25)FX or later for a Catalyst 2960 switch.00(-A or -EN) or later Cluster Capability Member or command switch Member or command switch Member or command switch Member or command switch Member or command switch Member or command switch Member or command switch Member or command switch Member switch only Member switch only Cluster Command Switch Characteristics A cluster command switch must meet these requirements: • • • • • It is running Cisco IOS Release 12.Chapter 6 Clustering Switches Understanding Switch Clusters Table 6-1 Switch Software and Cluster Capability (continued) Switch Catalyst 2960-S Catalyst 2960 Catalyst 2955 Catalyst 2950 Catalyst 2950 LRE Catalyst 2940 Catalyst 3500 XL Catalyst 2900 XL (8-MB switches) Catalyst 2900 XL (4-MB switches) Catalyst 1900 and 2820 Cisco IOS Release 12.2(25)FX or later 12. It is connected to the command switch and to other standby command switches through its management VLAN.2(25)FX or later for a Catalyst 2960 switch.1(11)JY or later 12.1(12c)EA1 or later 12. Release 15. It is not a command or cluster member switch of another cluster. or Cisco IOS Release 12.

Catalyst 3550. page 6-9 Catalyst 2960 and 2960-S Switches Software Configuration Guide. the standby cluster command switches must also be Catalyst 2960-S switches. or Catalyst 3750 cluster command switch. Release 15. It is connected to the cluster command switch through at least one common VLAN.0(1)SE 6-4 OL-26520-02 . refer to the software configuration guide for that specific switch. It has CDP version 2 enabled. Refer to the switch configuration guide of other cluster-capable switches for their requirements on standby cluster command switches. Although not required. Cluster member switches are switches and switch stacks that have actually been added to a switch cluster. the standby cluster command switches must also be Catalyst 2960 switches. The VLAN to each standby cluster command switch can be different. Catalyst 2900 XL. For example. 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. Catalyst 3560. Catalyst 2820. it is connected to every standby cluster command switch through at least one common VLAN. It is not a command or cluster member switch of another cluster.Chapter 6 Planning a Switch Cluster Clustering Switches Note Standby cluster command switches must be the same type of switches as the cluster command switch. Catalyst 2950. This section describes these guidelines. If the cluster command switch is a Catalyst 2960-S switch. requirements. The ip http server global configuration command must be configured on the switch. 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. Note Stacking is supported only on Catalyst 2960-S switches running the LAN base image. and caveats that you should understand before you create the cluster: • • Automatic Discovery of Cluster Candidates and Members. a candidate switch must meet these requirements: • • • • • • It is running cluster-capable software. For complete information about these switches in a switch-cluster environment. page 6-5 HSRP and Standby Cluster Command Switches. If a cluster standby group exists. To join a cluster. a candidate or cluster member switch can have its own IP address and password (for related considerations. Candidate Switch and Cluster Member Switch Characteristics Candidate switches are cluster-capable switches and switch stacks that have not yet been added to a cluster. if the cluster command switch is a Catalyst 2960 switch. Note Catalyst 1900. see the “IP Addresses” section on page 6-13 and “Passwords” section on page 6-13). This requirement does not apply if you have a Catalyst 2970.

and for the required software versions and browser and Java plug-in configurations. neighboring switch clusters. page 6-13 Hostnames. page 6-14 TACACS+ and RADIUS. page 6-7 Discovery of Newly Installed Switches. page 6-16 LRE Profiles. the cluster command switch has ports assigned to VLANs 16 and 62. The CDP hop count is three. or on any cluster-capable switches that you might want a cluster command switch to discover. page 6-13 SNMP Community Strings. The edge of the cluster is where the last cluster member switches are connected to the cluster and to candidate switches. cluster candidates. and neighboring edge devices: • • • • • Discovery Through CDP Hops. see Chapter 25. page 6-16 Refer to the release notes for the list of Catalyst switches eligible for switch clustering. For more information about CDP. connected switch clusters. page 6-13 Passwords. page 6-7 Discovery Through Different Management VLANs. page 6-6 Discovery Through Different VLANs. page 6-14 Switch Clusters and Switch Stacks. candidate switches. and edge devices across multiple VLANs and in star or cascaded topologies. Automatic Discovery of Cluster Candidates and Members The cluster command switch uses Cisco Discovery Protocol (CDP) to discover cluster member switches. page 6-5 Discovery Through Non-CDP-Capable and Noncluster-Capable Devices. 13. page 6-8 Discovery Through CDP Hops By using CDP. including which ones can be cluster command switches and which ones can only be cluster member switches. Release 15. Note Do not disable CDP on the cluster command switch. 12. a cluster command switch can discover switches up to seven CDP hops away (the default is three hops) from the edge of the cluster.0(1)SE OL-26520-02 6-5 . In Figure 6-1. “Configuring CDP.Chapter 6 Clustering Switches Planning a Switch Cluster • • • • • • • IP Addresses. Catalyst 2960 and 2960-S Switches Software Configuration Guide. For example. The cluster command switch discovers switches 11. 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. on cluster members.” Following these connectivity guidelines ensures automatic discovery of the switch cluster. cluster member switches 9 and 10 in Figure 6-1 are at the edge of the cluster.

0(1)SE 6-6 OL-26520-02 .Chapter 6 Planning a Switch Cluster Clustering Switches Figure 6-1 Discovery Through CDP Hops Command device VLAN 16 Member device 8 Member device 9 Device 11 candidate device Edge of cluster VLAN 62 Member device 10 Device 12 Device 13 Candidate devices Device 14 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 cannot discover a cluster-enabled device connected beyond the noncluster-capable Cisco device. However. the cluster command switch does not discover the switch that is connected to a Catalyst 5000 switch. Release 15. if the cluster command switch is connected to a noncluster-capable Cisco device. However. Figure 6-2 shows that the cluster command switch discovers the switch that is connected to a third-party hub. Figure 6-2 Discovery Through Non-CDP-Capable and Noncluster-Capable Devices Command device Third-party hub (non-CDP-capable) Catalyst 5000 switch (noncluster-capable) 101321 89377 Device 15 Candidate device Candidate device Catalyst 2960 and 2960-S Switches Software Configuration Guide. it can discover cluster-enabled devices connected to that third-party hub.

Catalyst 2950. Catalyst 3550.16 VLAN 50 VLAN 62 VLAN trunk 9. Catalyst 3560.” Note For additional considerations about VLANs in switch stacks. Figure 6-3 Discovery Through Different VLANs Command device VLAN 62 VLAN trunk 9. see the “Discovery Through Different Management VLANs” section on page 6-7. Release 15. As cluster member switches. Catalyst 3560. 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. “Configuring VLANs. Catalyst 2900 XL. and 62 and therefore discovers the switches in those VLANs. or Catalyst 3750 switch.16 VLAN 16 VLAN trunk 4. They do not need to be connected to the cluster command switch through their management VLAN.0(1)SE OL-26520-02 6-7 . As cluster member switches. It does not discover the switch in VLAN 50.Chapter 6 Clustering Switches Planning a Switch Cluster Discovery Through Different VLANs If the cluster command switch is a Catalyst 2970. they must be connected through at least one VLAN in common with the cluster command switch. The default management VLAN is VLAN 1. see Chapter 13. 16. Catalyst 3550. the cluster can have cluster member switches in different VLANs.16 101322 Discovery Through Different Management VLANs Catalyst 2970. see the “Switch Clusters and Switch Stacks” section on page 6-14. The cluster command switch in Figure 6-3 has ports assigned to VLANs 9. they must be connected through at least one VLAN in common with the cluster command switch. For more information about VLANs. or Catalyst 3750 cluster command switches can discover and manage cluster member switches in different VLANs and different management VLANs. 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 2960 and 2960-S Switches Software Configuration Guide.

An access port carries the traffic of and belongs to only one VLAN. which is switch 7 Discovery Through Different Management VLANs with a Layer 3 Cluster Command Switch Figure 6-4 Command device VLAN 9 VLAN 16 VLAN 62 Device 5 (management VLAN 62) VLAN trunk 4. The cluster command switch and standby command switch in Figure 6-4 (assuming they are Catalyst 2960. out-of-the-box switch must be connected to the cluster through one of its access ports. The management VLAN on the cluster command switch is VLAN 9. that switch or switch stack must be the cluster command switch. 16.Chapter 6 Planning a Switch Cluster Clustering Switches Note If the switch cluster has a Catalyst 3750 or 2960-S switch or has a switch stack. Catalyst 2960 and 2960-S Switches Software Configuration Guide. the new switch and its access ports are assigned to VLAN 1. When the new switch joins a cluster. Catalyst 2975. The new switch also configures its access port to belong to the VLAN of the immediately upstream neighbor. Catalyst 3550. or Catalyst 3750 cluster command switches) have ports assigned to VLANs 9. 62 Standby command device Device 3 (management VLAN 16) VLAN 9 Device 6 (management VLAN 9) VLAN 9 VLAN 16 Device 7 (management VLAN 4) Device 4 (management VLAN 16) VLAN 62 Device 9 (management VLAN 62) Device 8 (management VLAN 9) VLAN 4 Device 10 (management VLAN 4) Discovery of Newly Installed Switches To join a cluster. 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. and 62. Catalyst 2970. By default. Catalyst 3560. Release 15.0(1)SE 6-8 101323 OL-26520-02 . its default VLAN changes to the VLAN of the immediately upstream neighbor. the new.

Note The HSRP standby hold time interval should be greater than or equal to three times the hello time interval. The other switches in the cluster standby group are the passive cluster command switches (PC). The other cluster-capable switch and its access port are assigned to management VLAN 16. • 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 6-3. the switch stack elects a new stack master and resumes its role as the cluster command switch stack. the passive cluster command switch with the highest priority becomes the active cluster command switch. If the active cluster command switch and the standby cluster command switch become disabled at the same time. Discovery of Newly Installed Switches Figure 6-5 Command device VLAN 9 Device A AP VLAN 9 New (out-of-box) candidate device VLAN 16 Device B AP VLAN 16 101325 New (out-of-box) candidate device 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. The default HSRP standby hold time interval is 10 seconds. see the “Automatic Recovery of Cluster Configuration” section on page 6-12. When new cluster-capable switches join the cluster: • • One cluster-capable switch and its access port are assigned to VLAN 9. Release 15. The switches in the cluster standby group are ranked according to HSRP priorities. For a cluster command switch that is a standalone switch. Only one cluster standby group can be assigned per cluster.0(1)SE OL-26520-02 6-9 . if only the stack master in the command switch stack fails.Chapter 6 Clustering Switches Planning a Switch Cluster The cluster command switch in Figure 6-5 belongs to VLANs 9 and 16. we strongly recommend the following: • For a cluster command switch stack. The switch with the highest priority in the group is the active cluster command switch (AC). a standby cluster command switch is necessary if the entire switch stack fails. The switch with the next highest priority is the standby cluster command switch (SC). Catalyst 2960 and 2960-S Switches Software Configuration Guide. The default HSRP standby hello time interval is 3 seconds. configure a standby cluster command switch to take over if the primary cluster command switch fails. Because a cluster command switch manages the forwarding of all communication and configuration information to all the cluster member switches. For the limitations to automatic discovery. However.

These topics also provide more detail about standby cluster command switches: • • • Virtual IP Addresses. connected switch clusters.0(1)SE 6-10 OL-26520-02 .Chapter 6 Planning a Switch Cluster Clustering Switches These connectivity guidelines ensure automatic discovery of the switch cluster. Release 15. page 6-12 Catalyst 2960 and 2960-S Switches Software Configuration Guide. page 6-11 Other Considerations for Cluster Standby Groups. cluster candidates. page 6-11 Automatic Recovery of Cluster Configuration. and neighboring edge devices.

Refer to the switch configuration guide of other cluster-capable switches for their requirements on standby cluster command switches. You can have more than one router-redundancy standby group. If your switch cluster has a Catalyst 2960 switchor a Cisco FlexStack (a stack that contains only 2960-S switches). This information must be configured on a specific VLAN or routed port on the active cluster command switch. Catalyst 2960 and 2960-S Switches Software Configuration Guide. When the previously active cluster command switch becomes active again. These requirements also apply: • Standby cluster command switches must be the same type of switches as the cluster command switch. If the cluster command switch is a Catalyst 2960-S switch.0(1)SE OL-26520-02 6-11 . the cluster command switch and standby cluster command switches are Catalyst 2970. Catalyst 3550.Chapter 6 Clustering Switches Planning a Switch Cluster Virtual IP Addresses You need to assign a unique virtual IP address and group number and name to the cluster standby group. All standby-group members must be members of the cluster. it resumes its role as the active cluster command switch. the standby cluster command switch assumes ownership of the virtual IP address and becomes the active cluster command switch. However. not through the command-switch IP address. If the active cluster command switch fails. Release 15. or Catalyst 3750 cluster command switches. In this example. Catalyst 3560. The active cluster command switch receives traffic destined for the virtual IP address. if the cluster command switch is a Catalyst 2960 switch. To manage the cluster. and cluster member switches—cannot be more than 16. standby-group members. you must access the active cluster command switch through the virtual IP address. The passive standby switch with the highest priority then becomes the standby cluster command switch. 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. The passive switches in the cluster standby group compare their assigned priorities to decide the new standby cluster command switch. For more information about IP address in switch clusters. and the current active cluster command switch becomes the standby cluster command switch again. • Each standby-group member (Figure 6-6) must be connected to the cluster command switch through the same VLAN. see the “IP Addresses” section on page 6-13. the standby cluster command switches must also be Catalyst 2960-S switches. Note There is no limit to the number of switches that you can assign as standby cluster command switches. the standby cluster command switches must also be Catalyst 2960 switches. Stacking is supported only on Catalyst 2960-S switches running the LAN base image. it should be the cluster command switch. • • Only one cluster standby group can be assigned to a cluster. see the “Switch Clusters and Switch Stacks” section on page 6-14. the total number of switches in the cluster—which would include the active cluster command switch. Other Considerations for Cluster Standby Groups Note For additional considerations about cluster standby groups in switch stacks. Each standby-group member must also be redundantly connected to each other through at least one VLAN in common with the switch cluster. For example.

Catalyst 2900 XL.0(1)SE 6-12 101326 OL-26520-02 . because it was a passive standby cluster command switch. Catalyst 2820. You must re-add these cluster member switches to the cluster. and Catalyst 3750 command and standby cluster command switches: If the active cluster command switch and standby cluster command switch become disabled at the same time. Automatic discovery has these limitations: • This limitation applies only to clusters that have Catalyst 2950. You must therefore rebuild the cluster. The active cluster command switch only forwards cluster-configuration information to the standby cluster command switch. Catalyst 2820. Catalyst 3560. This ensures that the standby cluster command switch can take over the cluster immediately after the active cluster command switch fails. and Catalyst 3500 XL cluster member switches must be connected to the cluster standby group through their management VLANs. Catalyst 2950. the passive cluster command switch with the highest priority becomes the active cluster command switch. and Catalyst 2916M XL cluster member switches.16 VLANs 9. it does not discover any Catalyst 1900. see these sections: – “Discovery Through Different VLANs” section on page 6-7 – “Discovery Through Different Management VLANs” section on page 6-7 Figure 6-6 VLAN Connectivity between Standby-Group Members and Cluster Members Standby Command Passive command device device command device VLANs 9. This limitation applies to all clusters: If the active cluster command switch fails and becomes active again. the new cluster command switch does not discover any Catalyst 1900. You must again add these cluster member switches to the cluster. Catalyst 2820.16 Management VLAN 16 VLAN 9 Management VLAN 9 VLAN 9 Management VLAN 16 VLAN 16 Member devices Automatic Recovery of Cluster Configuration The active cluster command switch continually forwards cluster-configuration information (but not device-configuration information) to the standby cluster command switch. Release 15. This limitation applies to all clusters: If the active cluster command switch fails and there are more than two switches in the cluster standby group. and Catalyst 2916M XL cluster member switches. For more information about VLANs in switch clusters. the previous cluster command switch did not forward cluster-configuration information to it.Chapter 6 Planning a Switch Cluster Clustering Switches Catalyst 1900. However. • • Catalyst 2960 and 2960-S Switches Software Configuration Guide. Catalyst 3550.

If the cluster member switch leaves the cluster and it does not have its own IP address. was then added to a new cluster. was removed from a cluster. If no command-switch password is configured. However. When a switch joins a cluster. For example. see Chapter 3. Catalyst 2960 and 2960-S Switches Software Configuration Guide.Chapter 6 Clustering Switches Planning a Switch Cluster When the previously active cluster command switch resumes its active role. it receives a copy of the latest cluster configuration from the active cluster command switch. A cluster member switch is managed and communicates with other cluster member switches through the command-switch IP address. You can assign an IP address to a cluster-capable switch. You can assign more than one IP address to the cluster command switch. you must use the standby-group virtual IP address to manage the cluster from the active cluster command switch. If a switch received its hostname from the cluster command switch. Release 15. it retains that name when it joins a cluster and when it leaves the cluster. the cluster member switch inherits a null password. a hostname assigned to the cluster command switch can help to identify the switch cluster. but it is not necessary. “Assigning the Switch IP Address and Default Gateway. If a switch joins a cluster and it does not have a hostname. If the switch member number changes in the new cluster (such as 3). and kept the same member number (such as 5). you must either use the standby-group virtual IP address or any of the IP addresses available on the new active cluster command switch to access the cluster. Cluster member switches only inherit the command-switch password. the switch overwrites the old hostname (such as eng-cluster-5) with the hostname of the cluster command switch in the new cluster (such as mkg-cluster-5). the cluster command switch appends a unique member number to its own hostname and assigns it sequentially as each switch joins the cluster. For more information about IP addresses. The number means the order in which the switch was added to the cluster. a cluster command switch named eng-cluster could name the fifth cluster member eng-cluster-5. The active cluster command switch sends a copy of the cluster configuration to the cluster standby group. it inherits the command-switch password and retains it when it leaves the cluster. including members that were added while it was down. the switch retains the previous name (eng-cluster-5). you must assign an IP address to manage it as a standalone switch.” Hostnames You do not need to assign a host name to either a cluster command switch or an eligible cluster member. The default hostname for the switch is Switch. Using the virtual IP address ensures that you retain connectivity to the cluster if the active cluster command switch fails and that a standby cluster command switch becomes the active cluster command switch. Passwords You do not need to assign passwords to an individual switch if it will be a cluster member. If you configure a cluster standby group.0(1)SE OL-26520-02 6-13 . If the active cluster command switch fails and the standby cluster command switch takes over. and you can access the cluster through any of the command-switch IP addresses. IP Addresses You must assign IP information to a cluster command switch. If a switch has a hostname.

Release 15. “Managing Switch Stacks. SNMP Community Strings A cluster member switch inherits the command-switch first read-only (RO) and read-write (RW) community strings with @esN appended to the community strings: • • command-switch-readonly-community-string@esN. Each switch stack can act as the cluster command switch or as a single cluster member. see the “Preventing Unauthorized Access to Your Switch” section on page 9-1.Chapter 6 Planning a Switch Cluster Clustering Switches If you change the member-switch password to be different from the command-switch password and save the change. “Configuring SNMP. where N is the member-switch number. where N is the member-switch number. see Chapter 7.” Note Stacking is supported only on Catalyst 2960-S switches running the LAN base image. and Catalyst 2960-S switches Cluster members are connected through LAN ports Requires one stack master and supports up to four other stack Requires 1 cluster command switch and supports up to members 15 other cluster member switches Can be a cluster command switch or a cluster member switch Cannot be a stack master or stack member Stack master is the single point of complete management for all stack members in a particular switch stack Cluster command switch is the single point of some management for all cluster members in a particular switch cluster Catalyst 2960 and 2960-S Switches Software Configuration Guide. command-switch-readwrite-community-string@esN. Rebooting the member switch does not revert the password back to the command-switch password. The switches support an unlimited number of community strings and string lengths. For more information about switch stacks. Switch Clusters and Switch Stacks A switch cluster can have one or more Catalyst 2960-S switch stacks. If the cluster command switch has multiple read-only or read-write community strings. Table 6-2 describes the basic differences between switch stacks and switch clusters.” For SNMP considerations specific to the Catalyst 1900 and Catalyst 2820 switches. Table 6-2 Basic Comparison of Switch Stacks and Switch Clusters Switch Stack Made up of Catalyst 2960-S switches only Stack members are connected through StackWise ports Switch Cluster Made up of cluster-capable switches. the switch is not manageable by the cluster command switch until you change the member-switch password to match the command-switch password. refer to the installation and configuration guides for those switches. see Chapter 30. Catalyst 3550. such as Catalyst 3750. refer to the installation and configuration guides specific to those switches. We recommend that you do not change the member-switch password after it joins a cluster.0(1)SE 6-14 OL-26520-02 . For more information about passwords. For more information about SNMP and community strings. For password considerations specific to the Catalyst 1900 and Catalyst 2820 switches. only the first read-only and read-write strings are propagated to the cluster member switch.

and the original stack master is not re-elected. connectivity between the switch stacks is lost if there are no redundant connections between the switch stack and the cluster command switch. All stack members should have redundant connectivity to all VLANs in the switch cluster. a cluster can potentially have up to 16 switch stacks. stack members connected to any VLANs not configured on the new stack master lose their connectivity to the switch cluster. the switch cluster recognizes switch stacks. Because a switch cluster must have 1 cluster command switch and can have up to 15 cluster members. independent switches that are a single. You must add the switch stacks to the cluster. if a new stack master is elected. Release 15. unified system in the network not managed as and do not behave as a unified system Integrated management of stack members through a single configuration file Stack. including the cluster command switch stack. If a cluster command switch stack reloads. as eligible cluster members. You must add the switch stack to the switch cluster. individual configuration files Cluster configuration are stored on the cluster command switch and the standby cluster command switch New cluster members must be manually added to the switch cluster Recall that stack members work together to behave as a unified system (as a single switch stack) in the network and are presented to the network as such by Layer 2 and Layer 3 protocols. Otherwise. you must rebuild the entire switch cluster. totalling 144 devices.0(1)SE OL-26520-02 6-15 . These are considerations to keep in mind when you have switch stacks in switch clusters: • If the cluster command switch is not a Catalyst 2960-S switch or switch stack and a new stack master is elected in a cluster member switch stack.Chapter 6 Clustering Switches Planning a Switch Cluster Table 6-2 Basic Comparison of Switch Stacks and Switch Clusters (continued) Switch Stack Switch Cluster Back-up stack master is automatically determined in case the Standby cluster command switch must be pre-assigned in case stack master fails the cluster command switch fails Switch stack supports up to four simultaneous stack master failures Switch cluster supports only one cluster command switch failure at a time Stack members (as a switch stack) behave and is presented as Cluster members are various. You must add the switch stack back to the switch cluster. If the cluster command switch is a switch stack and new stack masters are simultaneously elected in the cluster command switch stack and in cluster member switch stacks. You must change the VLAN configuration of the stack master or the stack members and add the stack members back to the switch cluster. • • • • For more information about switch stacks. see Chapter 7. Individual stack members cannot join a switch cluster or participate as separate cluster members. not individual stack members. the switch stack loses its connectivity to the switch cluster if there are no redundant connections between the switch stack and the cluster command switch. If a cluster member switch stack reloads and a new stack master is elected.” Catalyst 2960 and 2960-S Switches Software Configuration Guide. the switch stack loses connectivity with the cluster command switch. Therefore.and interface-level configurations are stored on each stack member New stack members are automatically added to the switch stack Cluster members have separate. “Managing Switch Stacks. Cluster configuration of switch stacks is through the stack master.

Enter the exit privileged EXEC command on the cluster member switch to return to the command-switch CLI. For more information about RADIUS. For instructions on configuring the switch for a Telnet session. If one LRE switch in a cluster is assigned a public profile. see the “Switch Clusters and Switch Stacks” section on page 6-14. Note The CLI supports creating and maintaining switch clusters with up to 16 switch stacks. For more information about TACACS+. the Telnet session accesses the management console (a menu-driven interface) if the cluster command switch is at privilege level 15. The Telnet session accesses the member-switch CLI at the same privilege level as on the cluster command switch. Using the CLI to Manage Switch Clusters You can configure cluster member switches from the CLI by first logging into the cluster command switch.0(1)SE 6-16 OL-26520-02 . Release 15. The command mode changes. see the “Controlling Switch Access with RADIUS” section on page 9-18. For more information about switch stack and switch cluster. if RADIUS is configured on a cluster member. it must be configured on all cluster members. it must be configured on all cluster members. make sure that you assign it the same public profile used by other LRE switches in the cluster. For more information about the rcommand command and all other cluster commands. Stacking is supported only on Catalyst 2960-S switches running the LAN base image. all LRE switches in that cluster must have that same public profile. If the cluster command switch is at privilege level 1 to 14. you are prompted for the password to access the menu console. the same switch cluster cannot have some members configured with TACACS+ and other members configured with RADIUS. see the “Disabling Password Recovery” section on page 9-5. Enter the rcommand user EXEC command and the cluster member switch number to start a Telnet session (through a console or Telnet connection) and to access the cluster member switch CLI. enter the show cluster members privileged EXEC command on the cluster command switch. The Cisco IOS commands then operate as usual. Further. LRE Profiles A configuration conflict occurs if a switch cluster has Long-Reach Ethernet (LRE) switches that use both private and public profiles.Chapter 6 Using the CLI to Manage Switch Clusters Clustering Switches TACACS+ and RADIUS If Terminal Access Controller Access Control System Plus (TACACS+) is configured on a cluster member. Similarly. see the “Controlling Switch Access with TACACS+” section on page 9-10. refer to the switch command reference. Catalyst 1900 and Catalyst 2820 CLI Considerations If your switch cluster has Catalyst 1900 and Catalyst 2820 switches running standard edition software. Before you add an LRE switch to a cluster. and the Cisco IOS commands operate as usual. Catalyst 2960 and 2960-S Switches Software Configuration Guide. This example shows how to log into member-switch 3 from the command-switch CLI: switch# rcommand 3 If you do not know the member-switch number. A cluster can have a mix of LRE switches that use different private profiles.

For more information about SNMP and community strings. SNMP is enabled by default. Use the first read-write and read-only community strings to communicate with the cluster command switch if there is a cluster standby group configured for the cluster. the cluster member switch is accessed at privilege level 1. refer to the installation and configuration guides for those switches.” Catalyst 2960 and 2960-S Switches Software Configuration Guide. Release 15. If you did not use the setup program to enter the IP information and SNMP was not enabled. where N is the switch number) to the first configured read-write and read-only community strings on the cluster command switch and propagates them to the cluster member switch. see Chapter 30. The cluster command switch uses this community string to control the forwarding of gets. you can enable it as described in the “Configuring SNMP” section on page 30-6. as shown in Figure 6-7. For more information about the Catalyst 1900 and Catalyst 2820 switches. If the command-switch privilege level is 15. Note The Catalyst 1900 and Catalyst 2820 CLI is available only on switches running Enterprise Edition Software. Note When a cluster standby group is configured. SNMP is enabled if you enter the IP information by using the setup program and accept its proposed configuration. If a cluster member switch has its own IP address and community strings. the cluster command switch redirects traps from the cluster member switch to the management station. Using SNMP to Manage Switch Clusters When you first power on the switch. If the cluster member switch does not have an IP address. On Catalyst 1900 and Catalyst 2820 switches. they can be used in addition to the access provided by the cluster command switch.Chapter 6 Clustering Switches Using SNMP to Manage Switch Clusters Command-switch privilege levels map to the Catalyst 1900 and Catalyst 2820 cluster member switches running standard and Enterprise Edition Software as follows: • • If the command-switch privilege level is 1 to 14. If a cluster member switch has its own IP address and community strings. the cluster member switch can send traps directly to the management station. the cluster command switch manages the exchange of messages between cluster member switches and an SNMP application. sets. the cluster command switch can change without your knowledge. When you create a cluster. without going through the cluster command switch.0(1)SE OL-26520-02 6-17 . and get-next messages between the SNMP management station and the cluster member switches. the cluster member switch is accessed at privilege level 15. The cluster software on the cluster command switch appends the cluster member switch number (@esN. “Configuring SNMP.

Trap 3 ap Tr Tr ap Trap Member 1 Member 2 Member 3 Catalyst 2960 and 2960-S Switches Software Configuration Guide.0(1)SE 6-18 33020 OL-26520-02 .Chapter 6 Using SNMP to Manage Switch Clusters Clustering Switches Figure 6-7 SNMP Management for a Cluster SNMP Manager Command switch Trap 1. Trap 2. Release 15.

com. From the master. such as cabling the switches through their stack ports and using the LEDs for switch stack status. See the command reference for command syntax and usage information. Understanding Stacks A switch stack is a set of up to four Catalyst 2960-S switches connected through their stack ports. page 7-22 Displaying Stack Information. For more information about how switch stacks differ from switch clusters. page 7-23 Note A stack can have only Catalyst 2960-S member switches. Note A switch stack is different from a switch cluster. A switch cluster is a set of switches connected through their LAN ports. such as the 10/100/1000 ports. The stack master and the other switches in the stack are stack members. you configure: • • System-level (global) features that apply to all members Interface-level features for each member Catalyst 2960 and 2960-S Switches Software Configuration Guide. Layer 2 protocol presents the entire switch stack as a single entity to the network.CH A P T E R 7 Managing Switch Stacks This chapter provides the concepts and procedures to manage Catalyst 2960-S stacks. Note Stacking is supported only on Catalyst 2960-S switches running the LAN base image. page 7-1 Configuring the Switch Stack. Release 15. For other switch stack-related information. page 7-17 Accessing the CLI of a Specific Member. also referred to as Cisco FlexStacks. One of the switches controls the operation of the stack and is called the stack master. see the hardware installation guide. • • • • • Understanding Stacks.0(1)SE OL-26520-02 7-1 . page 7-22 Troubleshooting Stacks. see the “Planning and Creating Clusters” chapter in the Getting Started with Cisco Network Assistant on Cisco. The master is the single point of stack-wide management.

One of the factors is the stack member priority value. CiscoWorks network management software These concepts on stack formations: – Stack Membership. The configuration files include the system-level settings for the stack and the interface-level settings for each member. page 7-3 – Master Election. You can use these methods to manage stacks: • • • Network Assistant (available on Cisco. The switch with the highest stack-member priority-value becomes the master. page 7-6 – Member Priority Values. page 7-7 – Stack Software Compatibility Recommendations. the encryption features are available. page 7-7 – Stack Offline Configuration. The switch does not support MIBs to manage stacking-specific features such as stack membership and election. Every member is uniquely identified by its own stack member number. the remaining members elect a new master from among themselves. page 7-9 – Stack Protocol Version Compatibility. you should understand: • • These concepts on stack and member configurations: – Stack MAC Address. The master contains the saved and running configuration files for the stack. page 7-10 – Incompatible Software and Member Image Upgrades. page 7-14 – Additional Considerations for System-Wide Configuration on Switch Stacks. supports encryption) of the software. page 7-10 – Minor Version Number Incompatibility Among Switches.0(1)SE 7-2 OL-26520-02 . page 7-13 – Stack Configuration Files.com) Command-line interface (CLI) over a serial connection to the console port of any member A network management application through the Simple Network Management Protocol (SNMP) Note Use SNMP to manage network features across the stack that are defined by supported MIBs. You can manage the stack through the same IP address even if you remove the master or any other member from the stack. page 7-5 • To manage stacks. page 7-14 Catalyst 2960 and 2960-S Switches Software Configuration Guide. page 7-6 – Member Numbers. Each member has a current copy of these files for back-up purposes.Chapter 7 Understanding Stacks Managing Switch Stacks If the stack master is running the cryptographic version (that is. You manage the stack through a single IP address. All members are eligible masters. The system-level features supported on the master are supported on the entire stack. page 7-10 – Major Version Number Incompatibility Among Switches. Release 15. If the master becomes unavailable. The IP address is a system-level setting and is not specific to the master or to any other member.

make sure the switches that you add to or remove from the stack are powered off. reload and join the stack as members. If you want the stacks to remain separate. A standalone switch is a stack with one member that is also the master. Press the Mode button on a member until the Stack mode LED is on. The last two port LEDs on all switches in the stack should be green. each with the same configuration. the new switch functions with the same configuration as the replaced switch (assuming that the new switch is using the same member number as the replaced switch). see the “Stack Offline Configuration” section on page 7-7. After adding or removing members. For information about replacing a failed switch. Note To prevent interrupted stack operations.0(1)SE OL-26520-02 7-3 . Release 15. change the IP address or addresses of the newly created stacks. the stack is not operating at full bandwidth. • Catalyst 2960 and 2960-S Switches Software Configuration Guide. All remaining switches.Chapter 7 Managing Switch Stacks Understanding Stacks – Stack Management Connectivity. make sure that the stack ring is operating at full bandwidth (20 Gb/s). If you replace a stack member with an identical model. page 7-15 – Stack Configuration Scenarios. If any one or both of any the last two port LEDs are not green. • Adding powered-on switches (merging) causes the masters of the merging stacks to elect a master from among themselves. Removing powered-on members divides (partitions) the stack into two or more switch stacks. including the former masters. see the “Troubleshooting” chapter in the hardware installation guide. with one of them as the master. You can connect one standalone switch to another (Figure 7-1 on page 7-4) to create a stack containing two stack members. For information about the benefits of provisioning a switch stack. The new master keeps its role and configuration and so do its members. This can create an IP address configuration conflict in your network. The operation of the stack continues uninterrupted during membership changes unless you remove the master or you add powered-on standalone switches or stacks. page 7-16 Stack Membership Note A switch stack can have only Catalyst 2960-S stack members. They change their member numbers to the lowest available numbers and use the configuration of the new master. You can connect standalone switches to an existing stack (Figure 7-2 on page 7-4) to increase the stack membership.

Release 15.Chapter 7 Understanding Stacks Managing Switch Stacks Figure 7-1 Creating a Switch Stack from Two Standalone Switches 1 1 2 3 207006 1 1 2 3 207006 1 2 Figure 7-2 Standalone switch Stack member 1 3 Stack member 2 and stack master Adding a Standalone Switch to a Switch Stack 1 2 3 5 1 2 3 4 207007 Catalyst 2960 and 2960-S Switches Software Configuration Guide.0(1)SE 7-4 OL-26520-02 .

When a new master is elected and the previous stack master becomes available. The switch is then re-elected as master if a re-election occurs. The switch that has the configuration file. Release 15. the current stack master might be re-elected based on the listed factors. When you power on or reset an entire stack. Members that are powered on within the same 20-second time frame participate in the master election and have a chance to become the master.0(1)SE OL-26520-02 7-5 . see the “Switch Installation” chapter in the hardware installation guide. For all powering considerations that affect stack-master elections. Members that are powered on after the 20-second time frame do not participate in this initial election and only become members. The stack membership is increased by adding powered-on standalone switches or switch stacks. The master fails.Chapter 7 Managing Switch Stacks Understanding Stacks 1 2 3 Stack member 1 Stack member 2 and stack master Stack member 3 4 5 Stack member 4 Standalone switch For information about cabling and powering switch stacks. The switch with the lowest MAC address. The stack is reset. The switch that is currently the stack master. the switch stack uses the forwarding tables in memory to minimize network disruption. see the “Switch Installation” chapter in the hardware installation guide. In the meantime. The new master is available after a few seconds. 2. The master is reset or powered off. some stack members might not participate in the master election. Catalyst 2960 and 2960-S Switches Software Configuration Guide. 3. • • • All members participate in re-elections. 4.* A stack master keeps its role unless one of these events occurs: • • • • • In the events marked by an asterisk (*). Note We recommend you assign the highest priority value to the switch that you want to be the master.* The master is removed from the stack. Master Election The stack master is elected based on one of these factors in the order listed: 1. the previous master does not resume its role as stack master. The physical interfaces on the other available stack members are not affected while a new stack master is elected and is resetting. The switch with the highest stack member priority value.

If it is being used by another member in the stack. A new. see the “Stack Configuration Files” section on page 7-14. If the previous master does not rejoin the stack during this period. the stack takes the MAC address of the new stack master as the stack MAC address. Members in the same stack cannot have the same member number. If the master changes. The procedure to change a member number. See the “Enabling Persistent MAC Address” section on page 7-18 for more information. • If you manually change the member number by using the switch current-stack-member-number renumber new-stack-member-number global configuration command. Merging stacks. When it joins a stack. out-of-the-box switch (one that has not joined a stack or has not been manually assigned a member number) ships with a default member number of 1. the MAC address of the master determines the bridge ID that identifies the stack in the network. See the following sections for information about stack member configuration: • • • • Catalyst 2960 and 2960-S Switches Software Configuration Guide. the command is rejected.0(1)SE 7-6 OL-26520-02 . the switch selects the lowest available number in the stack. see the “Assigning a Member Number” section on page 7-20. When the stack initializes. the stack member keeps its number only if the number is not being used by another member in the stack. • If you move a stack member to a different switch stack. However. Release 15. The SWITCH_NUMBER environment variable. that member resets to its default configuration.Chapter 7 Understanding Stacks Managing Switch Stacks Stack MAC Address The MAC address of the master determines the stack MAC address. the MAC address of the new master determines the new bridge ID. even if the switch is now a member and not a master. if the previous master rejoins the stack. there is an approximate 4-minute delay before the stack MAC address changes. If you do. You can also change the stack member number is by using the SWITCH_NUMBER environment variable. see the “Stack Membership” section on page 7-3. the new number goes into effect after that member resets (or after you use the reload slot stack-member-number privileged EXEC command) and only if that number is not already changed. see the “Controlling Environment Variables” section on page 3-20. If you manually change the member number and no interface-level configuration is associated with that number. Member Numbers The member number (1 to 4) identifies each member in the stack. The member number also determines the interface-level configuration that a member uses. the switch selects the lowest available number in the stack. Member numbers and configurations. During this time period. its default stack member number changes to the lowest available member number in the stack. the stack continues to use its MAC address as the stack MAC address. when the persistent MAC address feature is enabled. You cannot use the switch current-stack-member-number renumber new-stack-member-number global configuration command on a provisioned switch. If the number is being used by another member in the stack.

You can manually create the provisioned configuration by using the switch stack-member-number provision type global configuration command. The priority value can be 1 to 15. The switch to be added to the stack and to get this configuration is the provisioned switch. as part of a VLAN). Release 15. That configuration is the provisioned configuration.0(1)SE OL-26520-02 7-7 . The switch is then re-elected as master if a re-election occurs. The startup configuration file ensures that the stack can reload and can use the saved information whether or not the provisioned switch is part of the stack. Catalyst 2960 and 2960-S Switches Software Configuration Guide. the information appears in the stack running configuration whether or not the provisioned switch is part of the stack. When you configure the interfaces for a provisioned switch (for example. The provisioned configuration is automatically created when a switch is added to a stack and when no provisioned configuration exists. the switch type. Stack Offline Configuration You can use the offline configuration feature to provision (to configure) a new switch before it joins the stack. Note We recommend that you assign the highest priority value to the switch that you want to be the stack master. The new priority value takes effect immediately but does not affect the current master until the current master or the stack resets. The interface for the provisioned switch is not active and does not appear in the display of a specific feature (for example. The default priority value is 1. You can configure the member number. Entering the no shutdown interface configuration command has no effect. and the interfaces associated with a switch that is not yet part of the stack.Chapter 7 Managing Switch Stacks Understanding Stacks Member Priority Values A high priority value for a member increases the chance that it will be elected master and keep its member number. in the show vlan user EXEC command output).

The switch stack applies the provisioned configuration to the provisioned switch and adds it to the stack. Table 7-1 Results of Comparing the Provisioned Configuration with the Provisioned Switch Scenario The stack member numbers and the switch types match. 2. If the switch type of the provisioned switch matches the switch type in the provisioned configuration on the stack. The stack member numbers match. The switch stack applies the default configuration to the provisioned switch and adds it to the stack. The stack member numbers match but the switch types do not match. the stack applies either the provisioned configuration or the default configuration to it. The switch stack applies the default configuration to the provisioned switch and adds it to the stack. match: The provisioned configuration is changed to reflect the new information. If the stack member number of the provisioned switch matches the stack member number in the provisioned configuration on the stack. 1. Release 15. and 2. but The switch type of the provisioned switch does not match the switch type in the provisioned configuration on the stack. 2. If the stack member number of the provisioned switch matches the stack member number in the provisioned configuration on the stack. Catalyst 2960 and 2960-S Switches Software Configuration Guide. The provisioned configuration is changed to reflect the new information. If the new stack member number of the provisioned switch matches the stack member number in the provisioned configuration on the stack. The stack member number of the provisioned switch is in conflict with an existing stack member. The switch stack applies the default configuration to the provisioned switch and adds it to the stack. but the switch types do not match: 1. The provisioned configuration is changed to reflect the new information. 1. Result If the stack member number of the provisioned switch matches the stack member number in the provisioned configuration on the stack. 1. but The switch type of the provisioned switch does not match the switch type in the provisioned configuration on the stack.Chapter 7 Understanding Stacks Managing Switch Stacks Effects of Adding a Provisioned Switch to a Stack When you add a provisioned switch to the switch stack.0(1)SE 7-8 OL-26520-02 . The switch stack applies the provisioned configuration to the provisioned switch The stack member numbers and the switch types and adds it to the stack. and If the switch type of the provisioned switch matches the switch type in the provisioned configuration on the stack. The stack master assigns a new stack member number to the provisioned switch. The provisioned configuration is changed to reflect the new information. The stack member number is not found in the provisioned configuration. Table 7-1 lists the events that occur when the switch stack compares the provisioned configuration with the provisioned switch. 2.

To completely remove the configuration. Catalyst 2960 and 2960-S Switches Software Configuration Guide. The switch stack then adds to its running configuration a switch stack-member-number provision type global configuration command that matches the new switch. If you add a provisioned switch that is a different type than specified in the provisioned configuration to a powered-down switch stack and then apply power. Release 15. the switch joins the stack with the default interface configuration. and is replaced with another switch. Result The switch stack applies the default configuration to the provisioned switch and adds it to the stack. the switch stack rejects the (now incorrect) switch stack-member-number provision type global configuration command in the startup configuration file. However. Depending on how different the actual switch type is from the previously provisioned switch type. the configuration associated with the removed stack member remains in the running configuration as provisioned information. Note If the switch stack does not contain a provisioned configuration for a new switch. during stack initialization. some commands are rejected.Chapter 7 Managing Switch Stacks Understanding Stacks Table 7-1 Results of Comparing the Provisioned Configuration with the Provisioned Switch (continued) Scenario The stack member number of the provisioned switch is not found in the provisioned configuration. the stack applies either the provisioned configuration or the default configuration to it. see the “Provisioning a New Member for a Stack” section on page 7-21. Effects of Replacing a Provisioned Switch in a Stack When a provisioned switch in a switch stack fails. is removed from the stack.0(1)SE OL-26520-02 7-9 . Effects of Removing a Provisioned Switch from a Stack If you remove a provisioned switch from the switch stack. and some commands are accepted. The events that occur when the switch stack compares the provisioned configuration with the provisioned switch are the same as those described in the “Effects of Adding a Provisioned Switch to a Stack” section on page 7-8. use the no switch stack-member-number provision global configuration command. Stack Software Compatibility Recommendations All stack members must run the same Cisco IOS software version to ensure compatibility in the stack protocol version among the members. For configuration information. the nondefault interface configuration information in the startup configuration file for the provisioned interfaces (potentially of the wrong type) are executed.

a partially compatible switch enters version-mismatch mode and cannot join the stack as a fully functioning member. the correct directory structure is not properly created. Minor Version Number Incompatibility Among Switches Switches with the same major version number but with a different minor version number as the master are considered partially compatible. When connected to a stack. Pressing the Mode button does not change the LED mode. a system message describes the cause of the incompatibility on the specific stack members.com” section on page A-25. For more information about the info file. Release 15. Major Version Number Incompatibility Among Switches Switches with different Cisco IOS software versions likely have different stack protocol versions. If an incompatibility exists.0(1)SE 7-10 OL-26520-02 . Note Auto-advise and auto-copy identify which images are running by examining the info file and by searching the directory structure on the switch stack. Catalyst 2960 and 2960-S Switches Software Configuration Guide. The master sends the message to all members. The port LEDs on switches in version-mismatch mode will also stay off. The software uses the automatic upgrade (auto-upgrade) and the automatic advise (auto-advise) features. see the “tar File Format of Images on a Server or Cisco. see the “Major Version Number Incompatibility Among Switches” procedure on page 7-10 and the “Minor Version Number Incompatibility Among Switches” procedure on page 7-10. If you download your image by using the copy tftp: command instead of by using the archive download-sw privileged EXEC command. All features function properly across the stack.Chapter 7 Understanding Stacks Managing Switch Stacks Stack Protocol Version Compatibility The stack protocol version has a major version number and a minor version number (for example 1. For more information. The software detects the mismatched software and tries to upgrade (or downgrade) the switch in version-mismatch mode with the stack image or with a tar file image from the stack flash memory. Switches with different major version numbers are incompatible and cannot exist in the same stack. Switches with the same Cisco IOS software version have the same stack protocol version.4. These switches with the same software version as the master immediately join the stack. where 1 is the major version number and 4 is the minor version number).

the auto-advise process tells you to install new software on the stack. By default. If you have both stack cables connected during the reload. If a tar file suitable for the switch in version-mismatch mode is found. You can disable auto-upgrade by using the no boot auto-copy-sw global configuration command on the master.0(1)SE OL-26520-02 7-11 . – Automatic extraction (auto-extract) occurs when the auto-upgrade process cannot find the appropriate software in the stack to copy to the switch in version-mismatch mode. The tar file can be in any flash file system in the stack (including the switch in version-mismatch mode). the switch that was in version-mismatch mode reloads and joins the stack as a fully functioning member. You can use the archive-download-sw /allow-feature-upgrade privileged EXEC command to allow installing an image with a different feature set.The same events occur when cryptographic and noncryptographic images are running. the auto-advise process tells you the command (archive copy-sw or archive download-sw privileged EXEC command) and the image name (tar filename) needed to manually upgrade the switch stack or the switch in version-mismatch mode. the process extracts the file and automatically upgrades that switch. You can check the status of auto-upgrade by using the show boot privileged EXEC command and by checking the Auto upgrade line in the display. and there is no command to check its status. In that case. Catalyst 2960 and 2960-S Switches Software Configuration Guide. – Auto-copy automatically copies the software image running on any member to the switch in version-mismatch mode to upgrade (auto-upgrade) it. Auto-advise cannot be disabled. • Automatic advise (auto-advise)—when the auto-upgrade process cannot find appropriate version-mismatch member software to copy to the switch in version-mismatch mode. If an appropriate image is not found in the stack flash file systems. When the auto-upgrade process is complete. Auto-copy occurs if auto-upgrade is enabled. the auto-extract process searches all switches in the stack. The recommended image can be the running stack image or a tar file in any flash file system in the stack (including the switch in version-mismatch mode). Release 15. new switch hardware is not recognized in earlier versions of software. and if the software image running on the stack is suitable for the switch in version-mismatch mode. if there is enough flash memory in the switch in version-mismatch mode. for the tar file needed to upgrade the switch stack or the switch in version-mismatch mode. network downtime does not occur because the stack operates on two rings. • The automatic upgrade (auto-upgrade) process includes an auto-copy process and an auto-extract process. two software processes are involved: automatic upgrade and automatic advise.Chapter 7 Managing Switch Stacks Understanding Stacks Understanding Auto-Upgrade and Auto-Advise When the software detects mismatched software and tries to upgrade the switch in version-mismatch mode. auto-upgrade is enabled (the boot auto-copy-sw global configuration command is enabled). Note A switch in version-mismatch mode might not run all released software. whether they are in version-mismatch mode or not. For example. The auto-advise software does not give suggestions when the stack software and the software of the switch in version-mismatch mode do not contain the same feature sets. The auto-upgrade (auto-copy and auto-extract) processes start a few minutes after the mismatched software is detected.

Chapter 7 Understanding Stacks

Managing Switch Stacks

Auto-Upgrade and Auto-Advise Example Messages
When you add a switch that has a different minor version number to the stack, the software displays messages in sequence (assuming that there are no other system messages generated by the switch). This example shows that the stack detected a new switch that is running a different minor version number than the stack. Auto-copy launches, finds suitable software to copy from a member to the switch in version-mismatch mode, upgrades the switch in version-mismatch mode, and then reloads it:
*Mar 11 20:31:19.247:%STACKMGR-6-STACK_LINK_CHANGE:Stack Port 2 Switch 2 has changed to state UP *Mar 11 20:31:23.232:%STACKMGR-6-SWITCH_ADDED_VM:Switch 1 has been ADDED to the stack (VERSION_MISMATCH) *Mar 11 20:31:23.291:%STACKMGR-6-SWITCH_ADDED_VM:Switch 1 has been ADDED to the stack (VERSION_MISMATCH) (Stack_1-3) *Mar 11 20:33:23.248:%IMAGEMGR-6-AUTO_COPY_SW_INITIATED:Auto-copy-software process initiated for switch number(s) 1 *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW: *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:Searching for stack member to act *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:as software donor... *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:Found donor (system #2) for *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:member(s) 1 *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:System software to be uploaded: *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:System Type: 0x00000000 *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:archiving c260c-lanbase-mz.122-50.SE (directory) *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:archiving c260c-lanbase-mz.122-50.SE/c260c-lanbase-mz.122-50.SE.bin (4945851 bytes) *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:archiving c260c-lanbase-mz.122-50.SE/info (450 bytes) *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:archiving info (104 bytes) *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:examining image... *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:extracting info (104 bytes) *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:extracting c260c-lanbase-mz.122-50.SE/info (450 bytes) *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:extracting info (104 bytes) *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW: *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:Stacking Version Number:1.4 *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW: *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:System Type: 0x00000000 *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW: Ios Image File Size: 0x004BA200 *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW: Total Image File Size:0x00818A00 *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW: Minimum Dram required:0x08000000 *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW: Image Suffix:universalk9-122-53.SE *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW: Image Directory:c260c-lanbase-mz.122-50.SE *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW: Image Name:c260c-lanbase-mz.122-50.SE *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW: Image Feature:IP|LAYER_3|PLUS|MIN_DRAM_MEG=128 *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW: *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:Old image for switch 1:flash1:c260c-lanbase-mz.122-50.SE *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW: Old image will be deleted after download. *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW: *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:Extracting images from archive into flash on switch 1... *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:c260c-lanbase-mz.122-50.SE (directory) *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:extracting c260c-lanbase-mz.122-50.SE/c260c-lanbase-mz.122-50.SE (4945851 bytes) *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:extracting c260c-lanbase-mz.122-50.SE/info (450 bytes) *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:extracting info (104 bytes) *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE

7-12

OL-26520-02

Chapter 7

Managing Switch Stacks Understanding Stacks

*Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:Installing (renaming):`flash1:update/c260c-lanbase-mz.122-50.SE' -> *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW: `flash1:c260c-lanbase-mz.122-50.SE' *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:New software image installed in flash1:c260c-lanbase-mz.122-50.SE *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW: *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW: *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:Removing old image:flash1:c260c-lanbase-mz.122-50.SE *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW: *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:All software images installed. *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:Requested system reload in progress... *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:Software successfully copied to *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:system(s) 1 *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:Done copying software *Mar 11 20:36:15.038:%IMAGEMGR-6-AUTO_COPY_SW:Reloading system(s) 1

This example shows that the stack detected a new switch that is running a different minor version number than the stack. Auto-copy launches but cannot find software in the stack to copy to the switch in version-mismatch mode to make it compatible with the stack. The auto-advise process launches and recommends that you download a tar file from the network to the switch in version-mismatch mode:
*Mar 1 00:01:11.319:%STACKMGR-6-STACK_LINK_CHANGE:Stack Port 2 Switch 2 has changed to state UP *Mar 1 00:01:15.547:%STACKMGR-6-SWITCH_ADDED_VM:Switch 1 has been ADDED to the stack (VERSION_MISMATCH) stack_2# *Mar 1 00:03:15.554:%IMAGEMGR-6-AUTO_COPY_SW_INITIATED:Auto-copy-software process initiated for switch number(s) 1 *Mar 1 00:03:15.554:%IMAGEMGR-6-AUTO_COPY_SW: *Mar 1 00:03:15.554:%IMAGEMGR-6-AUTO_COPY_SW:Searching for stack member to act *Mar 1 00:03:15.554:%IMAGEMGR-6-AUTO_COPY_SW:as software donor... *Mar 1 00:03:15.554:%IMAGEMGR-6-AUTO_COPY_SW:Software was not copied *Mar 1 00:03:15.562:%IMAGEMGR-6-AUTO_ADVISE_SW_INITIATED:Auto-advise-software process initiated for switch number(s) 1 *Mar 1 00:04:22.537:%IMAGEMGR-6-AUTO_ADVISE_SW: *Mar 1 00:04:22.537:%IMAGEMGR-6-AUTO_ADVISE_SW: *Mar 1 00:04:22.537:%IMAGEMGR-6-AUTO_ADVISE_SW:Systems with incompatible software *Mar 1 00:04:22.537:%IMAGEMGR-6-AUTO_ADVISE_SW:have been added to the stack. The *Mar 1 00:04:22.537:%IMAGEMGR-6-AUTO_ADVISE_SW:storage devices on all of the stack *Mar 1 00:04:22.537:%IMAGEMGR-6-AUTO_ADVISE_SW:members have been scanned, and it has *Mar 1 00:04:22.537:%IMAGEMGR-6-AUTO_ADVISE_SW:been determined that the stack can be *Mar 1 00:04:22.537:%IMAGEMGR-6-AUTO_ADVISE_SW:repaired by issuing the following *Mar 1 00:04:22.537:%IMAGEMGR-6-AUTO_ADVISE_SW:command(s): *Mar 1 00:04:22.537:%IMAGEMGR-6-AUTO_ADVISE_SW: *Mar 1 00:04:22.537:%IMAGEMGR-6-AUTO_ADVISE_SW: archive download-sw /force-reload /overwrite /dest 1 flash1:c260c-lanbase-mz.122-50.SE.tar *Mar 1 00:04:22.537:%IMAGEMGR-6-AUTO_ADVISE_SW:

For information about using the archive download-sw privileged EXEC command, see the “Working with Software Images” section on page A-24.

Incompatible Software and Member Image Upgrades
You can upgrade a switch that has an incompatible software image by using the archive copy-sw privileged EXEC command to copy the software image from an existing member. That switch automatically reloads with the new image and joins the stack as a fully functioning member. For more information, see the “Copying an Image File from One Stack Member to Another” section on page A-38.

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE OL-26520-02

7-13

Chapter 7 Understanding Stacks

Managing Switch Stacks

Stack Configuration Files
The master has the saved and running configuration files for the stack. All members periodically receive synchronized copies of the configuration files from the master. If the master becomes unavailable, any member assuming the role of master has the latest configuration files.
• •

System-level (global) configuration settings—such as IP, STP, VLAN, and SNMP settings—that apply to all members Member interface-specific configuration settings, which are specific for each member

A new, out-of-box switch joining a stack uses the system-level settings of that stack. If a switch is moved to a different stack, it loses its saved configuration file and uses the system-level configuration of the new stack. The interface-specific configuration of each member is associated with its member number. A stack member keeps its number unless it is manually changed or it is already used by another member in the same stack.
• •

If an interface-specific configuration does not exist for that member number, the member uses its default interface-specific configuration. If an interface-specific configuration exists for that member number, the member uses the interface-specific configuration associated with that member number.

If you replace a failed member with an identical model, the replacement member automatically uses the same interface-specific configuration. You do not need to reconfigure the interface settings. The replacement switch must have the same member number as the failed switch. You back up and restore the stack configuration in the same way as you do for a standalone switch configuration. For information about
• •

The benefits of provisioning a switch stack, see the “Stack Offline Configuration” section on page 7-7. File systems and configuration files, see Appendix A, “Working with the Cisco IOS File System, Configuration Files, and Software Images.”

Additional Considerations for System-Wide Configuration on Switch Stacks
• • • • • • • • • • •

“Planning and Creating Clusters” chapter in the Getting Started with Cisco Network Assistant, available on Cisco.com “MAC Addresses and Switch Stacks” section on page 5-16 “802.1x Authentication and Switch Stacks” section on page 10-11 “VTP and Switch Stacks” section on page 14-8 “Spanning Tree and Switch Stacks” section on page 16-12 “MSTP and Switch Stacks” section on page 17-8 “DHCP Snooping and Switch Stacks” section on page 20-7 “IGMP Snooping and Switch Stacks” section on page 21-6 “Port Security and Switch Stacks” section on page 23-19 “CDP and Switch Stacks” section on page 25-2 “SPAN and RSPAN and Switch Stacks” section on page 27-10

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE

7-14

OL-26520-02

Chapter 7

Managing Switch Stacks Understanding Stacks

• • • •

“Configuring QoS” section on page 33-1 “ACLs and Switch Stacks” section on page 31-6 “EtherChannel and Switch Stacks” section on page 38-10 “IPv6 and Switch Stacks” section on page 35-11

Stack Management Connectivity
You manage the stack and the member interfaces through the master. You can use the CLI, SNMP, Network Assistant, and CiscoWorks network management applications. You cannot manage members as individual switches.
• • • •

Stack Through an IP Address, page 7-15 Stack Through an SSH Session, page 7-15 Stack Through Console Ports, page 7-15 Specific Members, page 7-16

Stack Through an IP Address
The stack is managed through a system-level IP address. You can still manage the stack through the same IP address even if you remove the master or any other stack member from the stack, provided there is IP connectivity.

Note

Members keep their IP addresses when you remove them from a stack. To avoid having two devices with the same IP address in your network, change the IP address of the switch that you removed from the stack. For related information about switch stack configurations, see the “Stack Configuration Files” section on page 7-14.

Stack Through an SSH Session
The Secure Shell (SSH) connectivity to the stack can be lost if a master running the cryptographic version fails and is replaced by a switch that is running a noncryptographic version. We recommend that a switch running the cryptographic version of the software be the master.

Stack Through Console Ports
You can connect to the master through the console port of one or more members. Be careful when using multiple CLI sessions to the master. Commands that you enter in one session are not displayed in the other sessions. Therefore, it is possible that you might not be able to identify the session from which you entered a command. We recommend that you use only one CLI session when managing the stack.

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE OL-26520-02

7-15

Chapter 7 Understanding Stacks

Managing Switch Stacks

Specific Members
If you want to configure a specific member port, you must include the stack member number in the CLI notation. To access a specific member, see the “Accessing the CLI of a Specific Member” section on page 7-22.

Stack Configuration Scenarios
Most of the scenarios in Table 7-2 assume at least two switches are connected through their stack ports.
Table 7-2 Switch Stack Configuration Scenarios

Scenario Master election specifically determined by existing masters Master election specifically determined by the member priority value Connect two powered-on stacks through the stack ports.
1. 2.

Result Only one of the two masters becomes the new stack master. The member with the higher priority value is elected master.

Connect two switches through their stack ports. Use the switch stack-member-number priority new-priority-number global configuration command to set one member with a higher member priority value. Restart both members at the same time.

3.

Master election specifically determined by the configuration file

Assuming that both members have the same priority value:
1.

The member with the saved configuration file is elected master.

Make sure that one member has a default configuration and that the other member has a saved (nondefault) configuration file. Restart both members at the same time.

2.

Master election specifically determined by the MAC address

Assuming that both members have the same priority The member with the lower MAC address value, configuration file, and software image, restart is elected master. both stack members at the same time. The member with the higher priority value keeps its member number. The other member has a new stack member number.

Member number conflict Assuming that one member has a higher priority value than the other member:
1.

Ensure that both members have the same member number. If necessary, use the switch current-stack-member-number renumber new-stack-member-number global configuration command. Restart both members at the same time. Power off the new switch. Through their stack ports, connect the new switch to a powered-on stack. Power on the new switch.

2.

Add a member

1. 2. 3.

The master is kept. The new switch is added to the stack.

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE

7-16

OL-26520-02

Chapter 7

Managing Switch Stacks Configuring the Switch Stack

Table 7-2

Switch Stack Configuration Scenarios (continued)

Scenario Master failure Remove (or power off) the master.

Result One of the remaining stack members becomes the new master. All other members in the stack remain members and do not restart.

Add more than four members

Through their stack ports, connect ten switches. Two switches become masters. One master has four stack members. The other 2. Power on all switches. master remains a standalone switch.
1.

Use the Mode button and port LEDs on the switches to identify which switches are masters and which switches belong to each master. For information about the Mode button and the LEDs, see the hardware installation guide.

Configuring the Switch Stack
• • • •

Default Switch Stack Configuration, page 7-17 Enabling Persistent MAC Address, page 7-18 Assigning Stack Member Information, page 7-20 Changing the Stack Membership, page 7-22

Default Switch Stack Configuration
Table 7-3 shows the default switch stack configuration.
Table 7-3 Default Switch Stack Configuration

Feature Stack MAC address timer Member number Member priority value Offline configuration Persistent MAC address

Default Setting Disabled. 1 1 The switch stack is not provisioned. Disabled.

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE OL-26520-02

7-17

Chapter 7 Configuring the Switch Stack

Managing Switch Stacks

Enabling Persistent MAC Address
The MAC address of the master determines the stack MAC address. When a master is removed from the stack and a new master takes over, the MAC address of the new master to become the new stack MAC address. However, you can set the persistent MAC address feature with a time delay before the stack MAC address changes. During this time period, if the previous master rejoins the stack, the stack continues to use that MAC address as the stack MAC address, even if the switch is now a member and not a master. You can also configure stack MAC persistency so that the stack MAC address never changes to the new master MAC address.

Caution

When you configure this feature, a warning message displays the consequences of your configuration. You should use this feature cautiously. Using the old master MAC address elsewhere in the domain could result in lost traffic. You can set the time period from 0 to 60 minutes.

If you enter the command with no value, the default delay is 4 minutes. We recommend that you always enter a value. The time delay appears in the configuration file with an explicit timer value of 4 minutes. If you enter 0, the stack MAC address of the previous master is used until you enter the no stack-mac persistent timer global configuration command, which changes the stack MAC address to that of the current master. If you do not enter this command, the stack MAC address does not change. If you enter a time delay of 1 to 60 minutes, the stack MAC address of the previous master is used until the configured time period expires or until you enter the no stack-mac persistent timer command.

If the previous master does not rejoin the stack during this period, the stack uses the MAC address of the new master as the stack MAC address.

Note

If the entire switch stack reloads, it acquires the MAC address of the master as the stack MAC address.

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE

7-18

OL-26520-02

Chapter 7

Managing Switch Stacks Configuring the Switch Stack

Beginning in privileged EXEC mode, follow these steps to enable persistent MAC address. This procedure is optional. Command
Step 1 Step 2

Purpose Enter global configuration mode. Enable a time delay after a stack-master change before the stack MAC address changes to that of the new stack master. If the previous stack master rejoins the stack during this period, the stack uses that MAC address as the stack MAC address.
• • •

configure terminal stack-mac persistent timer [0 | time-value]

Enter the command with no value to set the default delay of 4 minutes. We recommend that you always configure a value. Enter 0 to use the MAC address of the current master indefinitely. Enter a time-value from 1 to 60 to configure the time period (in minutes) before the stack MAC address changes to the new master.

Caution

When you enter this command, a warning states that traffic might be lost if the old master MAC address appears elsewhere in the network domain.

If you enter the no stack-mac persistent timer command after a new stack master takes over, before the time expires, the stack uses the current master MAC address.
Step 3 Step 4

end show running-config or show switch

Return to privileged EXEC mode. Verify that the stack MAC address timer is enabled. The output shows stack-mac persistent timer and the time in minutes. The output shows Mac persistency wait time with the number of minutes configured and the stack MAC address. (Optional) Save your entries in the configuration file.

Step 5

copy running-config startup-config

Use the no stack-mac persistent timer global configuration command to disable the persistent MAC address feature. This example shows how to configure the persistent MAC address feature for a 7-minute time delay and to verify the configuration:
Switch(config)# stack-mac persistent timer 7 WARNING: The stack continues to use the base MAC of the old Master WARNING: as the stack MAC after a master switchover until the MAC WARNING: persistency timer expires. During this time the Network WARNING: Administrators must make sure that the old stack-mac does WARNING: not appear elsewhere in this network domain. If it does, WARNING: user traffic may be blackholed. Switch(config)# end Switch# show switch Switch/Stack Mac Address : 0016.4727.a900 Mac persistency wait time: 7 mins H/W Current Switch# Role Mac Address Priority Version State ---------------------------------------------------------*1 Master 0016.4727.a900 1 0 Ready

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE OL-26520-02

7-19

Chapter 7 Configuring the Switch Stack

Managing Switch Stacks

Assigning Stack Member Information
• • •

Assigning a Member Number, page 7-20 (optional) Setting the Member Priority Value, page 7-20 (optional) Provisioning a New Member for a Stack, page 7-21 (optional)

Assigning a Member Number
Note

This task is available only from the master. Beginning in privileged EXEC mode, follow these steps to assign a member number to a member. This procedure is optional.

Command
Step 1 Step 2

Purpose Enter global configuration mode. Specify the current member number and the new member number for the member. The range is 1 to 4. You can display the current member number by using the show switch user EXEC command.

configure terminal switch current-stack-member-number renumber new-stack-member-number

Step 3 Step 4 Step 5 Step 6

end reload slot stack-member-number show switch copy running-config startup-config

Return to privileged EXEC mode. Reset the stack member. Verify the stack member number. Save your entries in the configuration file.

Setting the Member Priority Value
Note

This task is available only from the master. Beginning in privileged EXEC mode, follow these steps to assign a priority value to a member: This procedure is optional.

Command
Step 1 Step 2

Purpose Enter global configuration mode. Specify the member number and the new priority for the member. The member number range is 1 to 4. The priority value range is 1 to 15. You can display the current priority value by using the show switch user EXEC command. The new priority value takes effect immediately but does not affect the current master until the current master or the stack resets.

configure terminal switch stack-member-number priority new-priority-number

Step 3 Step 4

end reload slot stack-member-number

Return to privileged EXEC mode. Reset the member, and apply this configuration.

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE

7-20

OL-26520-02

Chapter 7

Managing Switch Stacks Configuring the Switch Stack

Command
Step 5 Step 6

Purpose Verify the member priority value. (Optional) Save your entries in the configuration file.

show switch stack-member-number copy running-config startup-config

You can also set the SWITCH_PRIORITY environment variable. For more information, see the “Controlling Environment Variables” section on page 3-20.

Provisioning a New Member for a Stack
Note

This task is available only from the master. Beginning in privileged EXEC mode, follow these steps to provision a new member for a stack. This procedure is optional.

Command
Step 1 Step 2 Step 3

Purpose Display summary information about the stack. Enter global configuration mode. Specify the member number for the provisioned switch. By default, no switches are provisioned. For stack-member-number, the range is 1 to 4. Enter a member number that is not already used in the stack. See Step 1. For type, enter the model number of the member.

show switch configure terminal switch stack-member-number provision type

Step 4 Step 5 Step 6 Step 7

end show running-config show switch stack-member-number copy running-config startup-config

Return to privileged EXEC mode. Verify the correct numbering of interfaces in the configuration. Verify the status of the provisioned switch. For stack-member-number, enter the same number as in Step 2. (Optional) Save your entries in the configuration file.

To remove provisioned information and to avoid receiving an error message, remove the specified switch from the stack before you use the no form of this command. This example shows how to provision a switch with a stack member number of 2 for the stack. The show running-config command output shows the interfaces associated with the provisioned switch:
Switch(config)# switch 2 provision switch PID Switch(config)# end Switch# show running-config | include switch 2 ! interface GigabitEthernet2/0/1 ! interface GigabitEthernet2/0/2 ! interface GigabitEthernet2/0/3 <output truncated>

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE OL-26520-02

7-21

Chapter 7 Accessing the CLI of a Specific Member

Managing Switch Stacks

Changing the Stack Membership
If you remove powered-on members but do not want to partition the stack:
Step 1 Step 2 Step 3

Power off the newly created stacks. Reconnect them to the original stack through their stack ports. Power on the switches.

Accessing the CLI of a Specific Member
Note

This task is only for debugging purposes, and is only available from the master. You can access all or specific members by using the remote command {all | stack-member-number} privileged EXEC command. The stack member number range is 1 to 4. You can access specific members by using the session stack-member-number privileged EXEC command. The member number is appended to the system prompt. For example, the prompt for member 2 is Switch-2#, and system prompt for the master is Switch#. Enter exit to return to the CLI session on the master. Only the show and debug commands are available on a specific member. For more information, see the “Using Interface Configuration Mode” section on page 12-17.

Displaying Stack Information
To display saved configuration changes after resetting a specific member or the stack, use these privileged EXEC commands:
Table 7-4 Commands for Displaying Stack Information

Command show controller ethernet-controller stack port [1 | 2] show platform stack passive-links all show switch show switch stack-member-number show switch detail show switch neighbors show switch stack-ports

Description Display stack port counters (or per-interface and per-stack port send and receive statistics read from the hardware). Display all stack information, such as the stack protocol version. Display summary information about the stack, including the status of provisioned switches and switches in version-mismatch mode. Display information about a specific member. Display detailed information about the stack ring. Display the stack neighbors. Display port information for the stack.

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE

7-22

OL-26520-02

Chapter 7

Managing Switch Stacks Troubleshooting Stacks

Troubleshooting Stacks
• • •

Manually Disabling a Stack Port, page 7-23 Re-Enabling a Stack Port While Another Member Starts, page 7-23 Understanding the show switch stack-ports summary Output, page 7-24

Manually Disabling a Stack Port
If a stack port is flapping and causing instability in the stack ring, to disable the port, enter the switch stack-member-number stack port port-number disable privileged EXEC command. To re-enable the port, enter the switch stack-member-number stack port port-number enable command.

Note

Be careful when using the switch stack-member-number stack port port-number disable command. When you disable the stack port, the stack operates at half bandwidth.
• •

A stack is in the full-ring state when all members are connected through the stack ports and are in the ready state. The stack is in the partial-ring state when
– All members are connected through the stack ports, but some all are not in the ready state. – Some members are not connected through the stack ports.

When you enter the switch stack-member-number stack port port-number disable privileged EXEC command and

The stack is in the full-ring state, you can disable only one stack port. This message appears:
Enabling/disabling a stack port may cause undesired stack changes. Continue?[confirm]

The stack is in the partial-ring state, you cannot disable the port. This message appears:
Disabling stack port not allowed with current stack configuration.

Re-Enabling a Stack Port While Another Member Starts
Stack Port 1 on Switch 1 is connected to Port 2 on Switch 4. If Port 1 is flapping, disable Port 1 with the switch 1 stack port 1 disable privileged EXEC command. While Port 1 on Switch 1 is disabled and Switch 1 is still powered on:
1. 2. 3. 4. 5. 6.

Disconnect the stack cable between Port 1 on Switch 1 and Port 2 on Switch 4. Remove Switch 4 from the stack. Add a switch to replace Switch 4 and assign it switch-number 4. Reconnect the cable between Port 1 on Switch 1 and Port 2 on Switch 4 (the replacement switch). Re-enable the link between the switches. Enter the switch 1 stack port 1 enable privileged EXEC command to enable Port 1 on Switch 1. Power on Switch 4.

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE OL-26520-02

7-23

Chapter 7 Troubleshooting Stacks

Managing Switch Stacks

Caution

Powering on Switch 4 before enabling the Port 1 on Switch 1 might cause one of the switches to reload. If Switch 4 is powered on first, you might need to enter the switch 1 stack port 1 enable and the switch 4 stack port 2 enable privileged EXEC commands to bring up the link.

Understanding the show switch stack-ports summary Output
Only Port 1 on stack member 2 is disabled.
Switch# show switch stack-ports summary Switch#/ Stack Neighbor Cable Link Port# Port Length OK Status -------- ------ -------- -------- ---1/1 OK 3 50 cm Yes 1/2 Down None 3 m Yes 2/1 Down None 3 m Yes 2/2 OK 3 50 cm Yes 3/1 OK 2 50 cm Yes 3/2 OK 1 50 cm Yes Link Active -----Yes No No Yes Yes Yes Sync OK ---Yes Yes Yes Yes Yes Yes # Changes To LinkOK --------1 1 1 1 1 1 In Loopback -------No No No No No No

Table 7-5

show switch stack-ports summary Command Output

Field Switch#/Port# Stack Port Status

Description Member number and its stack port number.
• • •

Absent—No cable is detected on the stack port. Down—A cable is detected, but either no connected neighbor is up, or the stack port is disabled. OK—A cable is detected, and the connected neighbor is up.

Neighbor Cable Length

Switch number of the active member at the other end of the stack cable. Valid lengths are 50 cm, 1 m, or 3 m. If the switch cannot detect the cable length, the value is no cable. The cable might not be connected, or the link might be unreliable.

Link OK

This shows if the link is stable. The link partner is a stack port on a neighbor switch.
• •

No—The link partner receives invalid protocol messages from the port. Yes—The link partner receives valid protocol messages from the port. No—The port cannot send traffic to the link partner. Yes—The port can send traffic to the link partner. No—The link partner does not send valid protocol messages to the stack port. Yes—The link partner sends valid protocol messages to the port.

Link Active

This shows if the stack port is in the same state as its link partner.
• •

Sync OK

• •

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE

7-24

OL-26520-02

Chapter 7

Managing Switch Stacks Troubleshooting Stacks

Table 7-5

show switch stack-ports summary Command Output (continued)

Field # Changes to LinkOK

Description This shows the relative stability of the link. If a large number of changes occur in a short period of time, link flapping can occur.

In Loopback

• •

No—At least one stack port on the member has an attached stack cable. Yes—None of the stack ports on the member has an attached stack cable.

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE OL-26520-02

7-25

Chapter 7 Troubleshooting Stacks

Managing Switch Stacks

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE

7-26

OL-26520-02

CH A P T E R

8

Configuring SDM Templates
The Catalyst 2960, 2960-S, and 2960-C switch command reference has command syntax and usage information about the Switch Database Management (SDM) templates. Different platform support different SDM templates.
• • •

Understanding the SDM Templates, page 8-1 Configuring the Switch SDM Template, page 8-4 .Displaying the SDM Templates, page 8-5

Understanding the SDM Templates
Note

The SDM template used by Catalyst 2960-C Gigabit Ethernet switch and by the Catalyst 2960-S running LAN Lite image is a default templates and is not configurable. Catalyst 2960-S switches running the LAN base image support a default template and the lanbase-routing template. You can use SDM templates to configure system resources in the switch to optimize support for specific features, depending on how the switch is used in the network. You can select a template to provide maximum system usage for some functions or use the default template to balance resources. To allocate ternary content addressable memory (TCAM) resources for different usages, the switch SDM templates prioritize system resources to optimize support for certain features. You can select ond of these SDM templates to optimize features on the Catalyst 2960 switch and on the Catalyst 2960-C Fast Ethernet switch: :
• •

Default—The default template gives balance to all functions. Dual—The dual IPv4 and IPv6 template allows the switch to be used in dual stack environments (supporting both IPv4 and IPv6). Using the dual stack templates results in less TCAM capacity allowed for each resource. Do not use them if you plan to forward only IPv4 traffic.

Note

The dual IPv4 and IPv6 template is not supported on Catalyst 2960 switches running the LAN Lite image and is not required on Catalyst 2960-S switches. LAN base routing—The lanbase-routing template supports IPv4 unicast routes for configuring static routing SVIs

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE OL-26520-02

8-1

Chapter 8 Understanding the SDM Templates

Configuring SDM Templates

Note

The lanbase-routing template is supported only on Catalyst 2960 and 2960-S switches running Cisco IOS Release 12.2(55)SE or later andonly with the LAN base image. QoS—The QoS template maximizes system resources for quality of service (QoS) access control entries (ACEs).
Approximate Feature Resources Allowed on 2960-S Switch Templates

Table 8-1

Resource Unicast MAC addresses IPv4 IGMP groups IPv4 unicast routes
• •

Default 8K 256 256

LAN base routing 4K 256 .75 K .75 K 16 0 0 0 0

Directly connected hosts Indirect routes

IPv6 multicast groups Directly connected IPv6 addresses Indirect IPv6 unicast routes IPv4 policy-based routing aces IPv4 MAC QoS ACEs IPv4 MAC security ACEs IPv6 policy-based routing aces IPv6 QoS ACEs IPv6 security ACEs 128 384 384

128 384 0 0 0

Table 8-2

Approximate Feature Resources Allowed on Catalyst 2960-C Fast Ethernet Switch Templates

Resource Unicast MAC addresses IPv4 IGMP groups and multicast routes IPv4 unicast routes
• •

Default 8K .25 K 0 0 0 0 0 0 0 .125 K

QoS 8K .25 K 0 0 0 0 0 0 0 .375 K

Dual 8K .25 K 0 0 0 .375 K 0 0 0 .125 K

LAN base routing 4K .25 K .75 K .75 K 16 K .25 K .25 K 0 0 .125 K

Directly connected hosts Indirect routes

IPv6 multicast groups Directly connected IPv6 addresses Indirect IPv6 unicast routes IPv4 policy-based routing aces IPv4 MAC QoS ACEs

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE

8-2

OL-26520-02

Chapter 8

Configuring SDM Templates Understanding the SDM Templates

Table 8-2

Approximate Feature Resources Allowed on Catalyst 2960-C Fast Ethernet Switch Templates

Resource IPv4 MAC security ACEs IPv6 policy-based routing aces IPv6 QoS ACEs IPv6 security ACEs

Default .375 K 0 0 0

QoS .125 K 0 0 0

Dual .375 K 0 20 77

LAN base routing .375 K 0 0 .125 K

Table 8-3

Approximate Feature Resources Allowed on 2960-C Gigabit Ethernet Switch Templates

Resource Unicast MAC addresses IPv4 IGMP groups IPv6 multicast groups Directly connected IPv6 addresses Indirect IPv6 unicast routes IPv4 policy-based routing aces IPv4 MAC QoS ACEs IPv4 MAC security ACEs IPv6 policy-based routing aces IPv6 QoS ACEs IPv6 security ACEs

Default 4K 256 0 0 0 0 128 384 0 0 0

The rows in the tables represent approximate hardware boundaries set when a template is selected. If a section of a hardware resource is full, all processing overflow is sent to the CPU, seriously impacting switch performance.

SDM Templates and Switch Stacks
Note

Stacking is supported only on Catalyst 2960-S switches running the LAN base image. All stack members use the same SDM template that is stored on the stack master. When a new switch is added to a stack, as with the switch configuration and VLAN database files, the SDM configuration that is stored on the stack master overrides the template configured on an individual switch. For more information about stacking, see Chapter 7, “Managing Switch Stacks.” You can use the show switch privileged EXEC command to see if any stack members are in SDM mismatch mode. This example shows the output from the show switch privileged EXEC command when an SDM mismatch exists:
Switch# Role Mac Address Priority Current State

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE OL-26520-02

8-3

Chapter 8 Configuring the Switch SDM Template

Configuring SDM Templates

-----------------------------------------------------------*2 Master 000a.fdfd.0100 5 Ready 4 Member 0003.fd63.9c00 5 SDM Mismatch

This is an example of a syslog message notifying the stack master that a stack member is in SDM mismatch mode:
2d23h:%STACKMGR-6-SWITCH_ADDED_SDM:Switch 2 has been ADDED to the stack (SDM_MISMATCH) 2d23h:%SDM-6-MISMATCH_ADVISE: 2d23h:%SDM-6-MISMATCH_ADVISE: 2d23h:%SDM-6-MISMATCH_ADVISE:System (#2) is incompatible with the SDM 2d23h:%SDM-6-MISMATCH_ADVISE:template currently running on the stack and 2d23h:%SDM-6-MISMATCH_ADVISE:will not function unless the stack is 2d23h:%SDM-6-MISMATCH_ADVISE:downgraded. Issuing the following commands 2d23h:%SDM-6-MISMATCH_ADVISE:will downgrade the stack to use a smaller 2d23h:%SDM-6-MISMATCH_ADVISE:compatible desktop SDM template: 2d23h:%SDM-6-MISMATCH_ADVISE: !!!!!!! SDM MISMATCH !!!!!!! Master Template is lanbase-routing & Local Template is default Reloading because of sdm template mismatch Please reboot the switch

Configuring the Switch SDM Template
• • •

Default SDM Template, page 8-4 SDM Template Configuration Guidelines, page 8-4 Setting the SDM Template, page 8-5

Default SDM Template
The default template for the Catalyst 2960 and 2960-S switches is the default desktop template.

SDM Template Configuration Guidelines

You configure multiple SDM templates on Catalyst 2960 switches and on Catalyst 2960-C Fast Ethernet switches. A Catalyst 2960-S switch running the LAN base image supports the desktop default template that includes maximum resources for all supported features and the lanbase-routing template for static routing. The Catalyst 2960-C Gigabit Ethernet switch supports only a default template. When you select and configure SDM templates, you must reload the switch for the configuration to take effect. Do not use the routing template if you do not have routing enabled on your switch. The sdm prefer lanbase routing global configuration command prevents other features from using the memory allocated to unicast routing in the routing template. If you try to configure IPv6 features without first selecting a dual IPv4 and IPv6 template, a warning message appears.

• •

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE

8-4

OL-26520-02

Chapter 8

Configuring SDM Templates .Displaying the SDM Templates

Note

The dual template is not supported on switches running the LAN lite image and is not required on Catalyst 2960-S switches.

Using the dual stack templates results in less TCAM capacity allowed for each resource, so do not use it if you plan to forward only IPv4 traffic.

Setting the SDM Template
Beginning in privileged EXEC mode, follow these steps to use the SDM template to maximize feature usage: Command
Step 1 Step 2

Purpose Enter global configuration mode. Specify the SDM template to be used on the switch: The keywords have these meanings:
• • • •

configure terminal sdm prefer {default | dual-ipv4-and-ipv6 default | lanbase-routing | qos}

default—Gives balance to all functions. dual-ipv4-and-ipv6 default—Allows the switch to be used in dual stack environments (supporting both IPv4 and IPv6). lanbase-routing—Supports configuring unicast routes for static routing on SVIs. qos—Maximizes system resources for QoS ACEs.

Use the no sdm prefer command to set the switch to the default template. The default template balances the use of system resources.
Note

The Catalyst 2960-S switch supports only the default and lanbase-routing templates. Catalyst 2960-C Gigabit Ethernet switches support only a default template.

Step 3 Step 4

end reload

Return to privileged EXEC mode. Reload the operating system. After the system reboots, you can use the show sdm prefer privileged EXEC command to verify the new template configuration. If you enter the show sdm prefer command before you enter the reload privileged EXEC command, the show sdm prefer command shows the template in use and the template that becomes active after a reload.

.

Displaying the SDM Templates
Use the show sdm prefer privileged EXEC command with no parameters to display the active template. Use the show sdm prefer [default | dual-ipv4-and-ipv6 default | lanbase-routing | qos] privileged EXEC command to display the resource numbers supported by the specified template.

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE OL-26520-02

8-5

Switch# show sdm prefer The current template is "lanbase-routing" template.Displaying the SDM Templates Configuring SDM Templates Note The Catalyst 2960-S switch supports only the default and lanbase-routing templates.0(1)SE 8-6 OL-26520-02 . displaying the template in use.75K 16 0 0.75K 0.125k 0. This is an example of output from the show sdm prefer command. The Catalyst 2960-C Gigabit Ethernet switch supports only a default template. number of unicast mac addresses: number of IPv4 IGMP groups + multicast routes: number of IPv4 unicast routes: number of directly-connected IPv4 hosts: number of indirect IPv4 routes: number of IPv4 policy based routing aces: number of IPv4/MAC qos aces: number of IPv4/MAC security aces: 4K 0.Chapter 8 . Release 15.25K 0.375k Catalyst 2960 and 2960-S Switches Software Configuration Guide. The selected template optimizes the resources in the switch to support this level of features for 8 routed interfaces and 255 VLANs.

Release 15.0(1)SE OL-26520-02 9-1 . page 9-2 Controlling Switch Access with TACACS+. page 9-41 Configuring the Switch for Secure Socket Layer HTTP. 2960-S. see the “Protecting Access to Privileged EXEC Commands” section on page 9-2. connect from outside the network through a serial port. page 9-18 Configuring the Switch for Local Authentication and Authorization. page 9-46 Configuring the Switch for Secure Copy Protocol. or 2960-C switch. you want network administrators to have access to your switch while you restrict access to users who dial from outside the network through an asynchronous port. page 9-10 Controlling Switch Access with RADIUS. or connect through a terminal or workstation from within the local network. page 9-1 Protecting Access to Privileged EXEC Commands. This chapter consists of these sections: • • • • • • • • Preventing Unauthorized Access to Your Switch. the term switch refers to a standalone switch and to a switch stack. These passwords are locally stored on the switch. you should configure one or more of these security features: • At a minimum. Unless otherwise noted. page 9-52 Preventing Unauthorized Access to Your Switch You can prevent unauthorized users from reconfiguring your switch and viewing configuration information.CH A P T E R 9 Configuring Switch-Based Authentication This chapter describes how to configure switch-based authentication on the Catalyst 2960. they must enter the password specified for the port or line before they can access the switch. Typically. Catalyst 2960 and 2960-S Switches Software Configuration Guide. For more information. you should configure passwords and privileges at each switch port. page 9-40 Configuring the Switch for Secure Shell. Note Stacking is supported only on Catalyst 2960-S switches running the LAN base image. To prevent unauthorized access into your switch. When users attempt to access the switch through a port or line.

Release 12. Note For complete syntax and usage information for the commands used in this section. see the Cisco IOS Security Command Reference. The default is level 15 (privileged EXEC level). page 9-5 Setting a Telnet Password for a Terminal Line. see the “Controlling Switch Access with TACACS+” section on page 9-10. If you want to use username and password pairs. page 9-8 Default Password and Privilege Level Configuration Table 9-1 shows the default password and privilege level configuration. but you want to store them centrally on a server instead of locally.Chapter 9 Protecting Access to Privileged EXEC Commands Configuring Switch-Based Authentication • For an additional layer of security. No password is defined. page 9-3 Disabling Password Recovery. Privilege levels define what commands users can enter after they have logged into a network device.4 on Cisco. Multiple networking devices can then use the same database to obtain user authentication (and. if necessary. page 9-7 Configuring Multiple Privilege Levels. you can store them in a database on a security server. The password is not encrypted in the configuration file. If you have defined privilege levels. Password protection restricts access to a network or network device. Table 9-1 Default Password and Privilege Levels Feature Enable password and privilege level Enable secret password and privilege level Line password Default Setting No password is defined. page 9-2 Setting or Changing a Static Enable Password. For more information. These pairs are assigned to lines or ports and authenticate each user before that user can access the switch. authorization) information. Release 15.0(1)SE 9-2 OL-26520-02 . you can also assign a specific privilege level (with associated rights and privileges) to each username and password pair. These sections contain this configuration information: • • • • • • • Default Password and Privilege Level Configuration. The default is level 15 (privileged EXEC level). page 9-6 Configuring Username and Password Pairs. For more information. Catalyst 2960 and 2960-S Switches Software Configuration Guide. No password is defined. which are locally stored on the switch. The password is encrypted before it is written to the configuration file. see the “Configuring Username and Password Pairs” section on page 9-7. page 9-3 Protecting Enable and Enable Secret Passwords with Encryption. • Protecting Access to Privileged EXEC Commands A simple way of providing terminal access control in your network is to use passwords and assign privilege levels. you can also configure username and password pairs.com.

The string cannot start with a number. The enable password is not encrypted and can be read in the switch configuration file. For password. configure terminal enable password password Step 3 Step 4 Step 5 end show running-config copy running-config startup-config Return to privileged EXEC mode. it takes precedence over the enable password command. no password is defined. Define a new password or change an existing password for access to privileged EXEC mode. do this: Enter abc. you can simply enter abc?123 at the password prompt. The password is not encrypted and provides access to level 15 (traditional privileged EXEC mode access): Switch(config)# enable password l1u2c3k4y5 Protecting Enable and Enable Secret Passwords with Encryption To provide an additional layer of security.0(1)SE OL-26520-02 9-3 . Both commands accomplish the same thing. follow these steps to set or change a static enable password: Command Step 1 Step 2 Purpose Enter global configuration mode. Catalyst 2960 and 2960-S Switches Software Configuration Guide. to create the password abc?123. (Optional) Save your entries in the configuration file. and allows spaces but ignores leading spaces. you can establish an encrypted password that users must enter to access privileged EXEC mode (the default) or any privilege level you specify. Enter Crtl-v. If you configure the enable secret command. particularly for passwords that cross the network or that are stored on a Trivial File Transfer Protocol (TFTP) server. Release 15. use the no enable password global configuration command. To remove the password. is case sensitive. This example shows how to change the enable password to l1u2c3k4y5. Beginning in privileged EXEC mode. that is. It can contain the question mark (?) character if you precede the question mark with the key combination Crtl-v when you create the password. Verify your entries. We recommend that you use the enable secret command because it uses an improved encryption algorithm. specify a string from 1 to 25 alphanumeric characters. for example. Enter ?123. the two commands cannot be in effect simultaneously. By default. When the system prompts you to enter the enable password. you can use either the enable password or enable secret global configuration commands. you need not precede the question mark with the Ctrl-v.Chapter 9 Configuring Switch-Based Authentication Protecting Access to Privileged EXEC Commands Setting or Changing a Static Enable Password The enable password controls access to the privileged EXEC mode.

and console and virtual terminal line passwords. Step 4 Step 5 end copy running-config startup-config Return to privileged EXEC mode. users must enter the enable secret password.Chapter 9 Protecting Access to Privileged EXEC Commands Configuring Switch-Based Authentication Beginning in privileged EXEC mode. the range is from 0 to 15. see the “Configuring Multiple Privilege Levels” section on page 9-8. By default. For more information. You cannot recover a lost encrypted password by any method. If you specify an encryption type and then enter a clear text password. you must provide an encrypted password—an encrypted password that you copy from another switch configuration. Use the level keyword to define a password for a specific privilege level. Level 1 is normal user EXEC mode privileges. (Optional) For encryption-type. The default level is 15 (privileged EXEC mode privileges). To disable password encryption. use the no service password-encryption global configuration command. only type 5. and allows spaces but ignores leading spaces.0(1)SE 9-4 OL-26520-02 . Use the privilege level global configuration command to specify commands accessible at various levels. Encryption prevents the password from being readable in the configuration file. If both the enable and enable secret passwords are defined. you can not re-enter privileged EXEC mode. give the password only to users who need to have access at this level. The string cannot start with a number. • configure terminal enable password [level level] {password | encryption-type encrypted-password} or enable secret [level level] {password | encryption-type encrypted-password} (Optional) For level. no password is defined. To remove a password and level. authentication key passwords. it applies to all passwords including username passwords. follow these steps to configure encryption for enable and enable secret passwords: Command Step 1 Step 2 Purpose Enter global configuration mode. (Optional) Save your entries in the configuration file. is available. After you specify the level and set a password. use the no enable password [level level] or no enable secret [level level] global configuration command. the privileged command password. If you enable password encryption. Define a new password or change an existing password for access to privileged EXEC mode. For password. or Define a secret password. If you specify an encryption type. specify a string from 1 to 25 alphanumeric characters. a Cisco proprietary encryption algorithm. is case sensitive. Release 15. • • Note Step 3 service password-encryption (Optional) Encrypt the password when the password is defined or when the configuration is written. Catalyst 2960 and 2960-S Switches Software Configuration Guide. which is saved using a nonreversible encryption method.

Verify the configuration by checking the last few lines of the command output. we recommend that you also keep a backup copy of the VLAN database file on a secure server. you can still interrupt the boot process and change the password.dat) are deleted. Beginning in privileged EXEC mode. Note Disabling password recovery will not work if you have set the switch to boot up manually by using the boot manual global configuration command. use the service password-recovery global configuration command. To re-enable password recovery. When the switch is returned to the default system configuration. The password-recovery disable feature protects access to the switch password by disabling part of this functionality.text) and the VLAN database file (vlan. see the “Recovering from a Lost or Forgotten Password” section on page 39-3. For more information. Do not keep a backup copy of the configuration file on the switch. any end user with physical access to the switch can recover from a lost password by interrupting the boot process while the switch is powering on and then by entering a new password.0(1)SE OL-26520-02 9-5 . Disable password recovery. Catalyst 2960 and 2960-S Switches Software Configuration Guide. but the configuration file (config. but it is not part of the file system and is not accessible by any user. configure terminal no service password-recovery Step 3 Step 4 end show version Return to privileged EXEC mode. This setting is saved in an area of the flash memory that is accessible by the boot loader and the Cisco IOS image. With password recovery disabled.Chapter 9 Configuring Switch-Based Authentication Protecting Access to Privileged EXEC Commands This example shows how to configure the encrypted password $1$FaD0$Xyti5Rkls3LoyxzS8 for privilege level 2: Switch(config)# enable secret level 2 5 $1$FaD0$Xyti5Rkls3LoyxzS8 Disabling Password Recovery By default. we recommend that you keep a backup copy of the configuration file on a secure server in case the end user interrupts the boot process and sets the system back to default values. Release 15. the end user can interrupt the boot process only by agreeing to set the system back to the default configuration. follow these steps to disable password recovery: Command Step 1 Step 2 Purpose Enter global configuration mode. you can download the saved files to the switch by using the Xmodem protocol. When this feature is enabled. Note If you disable password recovery. If the switch is operating in VTP transparent mode. This command produces the boot loader prompt (switch:) after the switch is power cycled.

Configure the number of Telnet sessions (lines). is case sensitive. The default data characteristics of the console port are 9600. There are 16 possible sessions on a command-capable switch. The setup program also prompts you to configure your switch for Telnet access through a password. you can configure it now through the command-line interface (CLI). 1. specify a string from 1 to 25 alphanumeric characters. Step 5 password password Enter a Telnet password for the line or lines. Step 2 Step 3 Step 4 enable password password configure terminal line vty 0 15 Enter privileged EXEC mode. If you did not configure this password during the setup program. and allows spaces but ignores leading spaces. follow these steps to configure your switch for Telnet access: Command Step 1 Purpose Attach a PC or workstation with emulation software to the switch console port. By default. The string cannot start with a number. Step 8 To remove the password.Chapter 9 Protecting Access to Privileged EXEC Commands Configuring Switch-Based Authentication Setting a Telnet Password for a Terminal Line When you power-up your switch for the first time. (Optional) Save your entries in the configuration file. Beginning in privileged EXEC mode. The 0 and 15 mean that you are configuring all 16 possible Telnet sessions. use the no password global configuration command. 8. For password. Release 15. The password is listed under the command line vty 0 15. no password is defined. an automatic setup program runs to assign IP information and to create a default configuration for continued use. Verify your entries. and enter line configuration mode. This example shows how to set the Telnet password to let45me67in89: Switch(config)# line vty 10 Switch(config-line)# password let45me67in89 Catalyst 2960 and 2960-S Switches Software Configuration Guide.0(1)SE 9-6 OL-26520-02 . You might need to press the Return key several times to see the command-line prompt. Enter global configuration mode. Step 6 Step 7 end show running-config copy running-config startup-config Return to privileged EXEC mode. no parity.

If you have defined privilege levels. Step 4 Step 5 Step 6 Step 7 login local end show running-config copy running-config startup-config Enable local password checking at login time. privilege level. • • Step 3 line console 0 or line vty 0 15 Enter line configuration mode. use the no login line configuration command. Level 15 gives privileged EXEC mode access. you can also assign a specific privilege level (with associated rights and privileges) to each username and password pair. specify the privilege level the user has after gaining access. Enter the username. Return to privileged EXEC mode. (Optional) For level.Chapter 9 Configuring Switch-Based Authentication Protecting Access to Privileged EXEC Commands Configuring Username and Password Pairs You can configure username and password pairs. Enter 7 to specify that a hidden password will follow. which are locally stored on the switch. (Optional) Save your entries in the configuration file. Verify your entries. Level 1 gives user EXEC mode access. use the no username name global configuration command. can contain embedded spaces. follow these steps to establish a username-based authentication system that requests a login username and a password: Command Step 1 Step 2 Purpose Enter global configuration mode. • • configure terminal username name [privilege level] {password encryption-type password} For name. specify the password the user must enter to gain access to the switch. The password must be from 1 to 25 characters. For password. The range is 0 to 15.0(1)SE OL-26520-02 9-7 . and must be the last option specified in the username command. To disable username authentication for a specific user. specify the user ID as one word. Release 15. Spaces and quotation marks are not allowed. Catalyst 2960 and 2960-S Switches Software Configuration Guide. For encryption-type. and configure the console port (line 0) or the VTY lines (line 0 to 15). enter 0 to specify that an unencrypted password will follow. These pairs are assigned to lines or ports and authenticate each user before that user can access the switch. and password for each user. To disable password checking and allow connections without a password. Authentication is based on the username specified in Step 2. Beginning in privileged EXEC mode.

Level 1 is for normal user EXEC mode privileges. and allows spaces but ignores leading spaces. specify the command to which you want to restrict access. no password is defined. (Optional) Save your entries in the configuration file. By configuring multiple passwords. But if you want more restricted access to the configure command. The string cannot start with a number. page 9-10 Setting the Privilege Level for a Command Beginning in privileged EXEC mode. For password.0(1)SE 9-8 OL-26520-02 . For level. specify a string from 1 to 25 alphanumeric characters. You can configure up to 16 hierarchical levels of commands for each mode. These sections contain this configuration information: • • • Setting the Privilege Level for a Command. or line for line configuration mode. Verify your entries. the Cisco IOS software has two modes of password security: user EXEC and privileged EXEC. Level 15 is the level of access permitted by the enable password. follow these steps to set the privilege level for a command mode: Command Step 1 Step 2 Purpose Enter global configuration mode. Step 6 copy running-config startup-config Catalyst 2960 and 2960-S Switches Software Configuration Guide. you can assign it level 2 security and distribute the level 2 password fairly widely. interface for interface configuration mode. For command. is case sensitive. • • Step 4 Step 5 end show running-config or show privilege Return to privileged EXEC mode. you can allow different sets of users to have access to specified commands. Release 15. • configure terminal privilege mode level level command For mode. By default. page 9-9 Logging into and Exiting a Privilege Level. Level 1 is for normal user EXEC mode privileges. the range is from 0 to 15. exec for EXEC mode. The second command shows the privilege level configuration. Set the privilege level for a command.Chapter 9 Protecting Access to Privileged EXEC Commands Configuring Switch-Based Authentication Configuring Multiple Privilege Levels By default. For level. the range is from 0 to 15. The first command shows the password and access level configuration. you can assign it level 3 security and distribute that password to a more restricted group of users. enter configure for global configuration mode. • • Step 3 enable password level level password Specify the enable password for the privilege level. For example. if you want many users to have access to the clear line command. page 9-8 Changing the Default Privilege Level for Lines.

Verify your entries. Release 15. To return to the default line privilege level. use the no privilege level line configuration command. You might specify a high level or privilege level for your console line to restrict line usage. (Optional) Save your entries in the configuration file. This example shows how to set the configure command to privilege level 14 and define SecretPswd14 as the password users must enter to use level 14 commands: Switch(config)# privilege exec level 14 configure Switch(config)# enable password level 14 SecretPswd14 Changing the Default Privilege Level for Lines Beginning in privileged EXEC mode. Step 6 copy running-config startup-config Users can override the privilege level you set using the privilege level line configuration command by logging in to the line and enabling a different privilege level. To return to the default privilege for a given command. Level 1 is for normal user EXEC mode privileges. the range is from 0 to 15. For example. Level 15 is the level of access permitted by the enable password. Change the default privilege level for the line. all commands whose syntax is a subset of that command are also set to that level. Catalyst 2960 and 2960-S Switches Software Configuration Guide. follow these steps to change the default privilege level for a line: Command Step 1 Step 2 Step 3 Purpose Enter global configuration mode. use the no privilege mode level level command global configuration command. For level. configure terminal line vty line privilege level level Step 4 Step 5 end show running-config or show privilege Return to privileged EXEC mode. Select the virtual terminal line on which to restrict access. The first command shows the password and access level configuration. They can lower the privilege level by using the disable command.0(1)SE OL-26520-02 9-9 . If users know the password to a higher privilege level. The second command shows the privilege level configuration.Chapter 9 Configuring Switch-Based Authentication Protecting Access to Privileged EXEC Commands When you set a command to a privilege level. the show commands and show ip commands are automatically set to privilege level 15 unless you set them individually to different levels. if you set the show ip traffic command to level 15. they can use that password to enable the higher privilege level.

Release 2. page 9-13 Displaying the TACACS+ Configuration.4. TACACS+ is facilitated through authentication.Chapter 9 Controlling Switch Access with TACACS+ Configuring Switch-Based Authentication Logging into and Exiting a Privilege Level Beginning in privileged EXEC mode. page 9-10 TACACS+ Operation. authorization. These sections contain this configuration information: • • • • Understanding TACACS+. the range is 0 to 15. For level. page 9-12 Configuring TACACS+. which provides detailed accounting information and flexible administrative control over authentication and authorization processes. follow these steps to log in to a specified privilege level and to exit to a specified privilege level: Command Step 1 Purpose Log in to a specified privilege level. page 9-18 Understanding TACACS+ TACACS+ is a security application that provides centralized validation of users attempting to gain access to your switch. Catalyst 2960 and 2960-S Switches Software Configuration Guide. see the Cisco IOS Security Command Reference.2(58)SE. accounting (AAA) and can be enabled only through AAA commands.0(1)SE 9-10 OL-26520-02 . For information about configuring this feature. Release 15. TACACS+ services are maintained in a database on a TACACS+ daemon typically running on a UNIX or Windows NT workstation. You should have access to and should configure a TACACS+ server before the configuring TACACS+ features on your switch. Release 2. Note For complete syntax and usage information for the commands used in this section. enable level disable level Step 2 Controlling Switch Access with TACACS+ This section describes how to enable and configure Terminal Access Controller Access Control System Plus (TACACS+). For level. Release 12. Release 12. the switch supports TACACS+ for IPv6. the range is 0 to 15.4 and the Cisco IOS IPv6 Command Reference. Exit to a specified privilege level. Information is in the “TACACS+ Over an IPv6 Transport” section of the “Implementing ADSL for IPv6” chapter in the Cisco IOS XE IPv6 Configuration Guide. Beginning with Cisco IOS Release 12. see the Cisco IOS Security Command Reference. Note For complete syntax and usage information for the commands used in this section. see the “Configuring TACACS+ over IPv6” section of the “Implementing ADSL for IPv6” chapter in the Cisco IOS XE IPv6 Configuration Guide.

Create a login authentication method list.10. after a username and password are provided. TACACS+ allows for a single access control server (the TACACS+ daemon) to provide each service—authentication. Catalyst 2960 and 2960-S Switches Software Configuration Guide. and accounting—independently.20. and accounting facilities. and messaging support. mother’s maiden name.20. and to interconnected networks as shown in Figure 9-1. can provide these services: • Authentication—Provides complete control of authentication through login and password dialog. The goal of TACACS+ is to provide a method for managing multiple network access points from a single management service. service type. authorization. The TACACS+ authentication service can also send messages to user screens. a message could notify users that their passwords must be changed because of the company’s password aging policy. Each service can be tied into its own database to take advantage of other services available on that server or on the network. and social security number). Your switch can be a network access server along with other Cisco routers and access servers. TACACS+.8 Workstations Configure the switches with the TACACS+ server addresses.0(1)SE OL-26520-02 101230 9-11 . Apply the list to the terminal lines. For example.10. such as home address. Release 15. to challenge a user with several questions. A network access server provides connections to a single user. Figure 9-1 Typical TACACS+ Network Configuration UNIX workstation (TACACS+ server 1) Catalyst 6500 series switch 171. Create an authorization and accounting Workstations method list as required. This is to help ensure that the TACACS+ server remains accessible in case one of the connected stack members is removed from the switch stack. challenge and response.Chapter 9 Configuring Switch-Based Authentication Controlling Switch Access with TACACS+ Note We recommend a redundant connection between a switch stack and the TACACS+ server. authorization. administered through the AAA security services. Set an authentication key (also configure the same key on the TACACS+ servers). Enable AAA.7 UNIX workstation (TACACS+ server 2) 171. The authentication facility can conduct a dialog with the user (for example. TACACS+ provides for separate and modular authentication. to a network or subnetwork. depending on the capabilities of the daemon.

Secure Shell (SSH). Users must first successfully complete TACACS+ authentication before proceeding to TACACS+ authorization. Release 15. and it returns an ACCEPT or REJECT authorization response. the TACACS+ daemon is again contacted. and number of bytes. rlogin. the user enters a password. Network managers can use the accounting facility to track user activity for a security audit or to provide information for user billing.0(1)SE 9-12 OL-26520-02 . and the switch then contacts the TACACS+ daemon to obtain a password prompt. such as the user’s mother’s maiden name. The switch displays the password prompt to the user.Chapter 9 Controlling Switch Access with TACACS+ Configuring Switch-Based Authentication • Authorization—Provides fine-grained control over user capabilities for the duration of the user’s session. Accounting—Collects and sends information used for billing. • The TACACS+ protocol provides authentication between the switch and the TACACS+ daemon. If an ERROR response is received. If TACACS+ authorization is required. You can also enforce restrictions on what commands a user can execute with the TACACS+ authorization feature. or privileged EXEC services Connection parameters. and it ensures confidentiality because all protocol exchanges between the switch and the TACACS+ daemon are encrypted. session duration. CONTINUE—The user is prompted for additional authentication information. and reporting to the TACACS+ daemon. access control. executed commands (such as PPP). 2. including but not limited to setting autocommands. The user enters a username. but can include other items. REJECT—The user is not authenticated. the user undergoes an additional authorization phase if authorization has been enabled on the switch. 3. the response contains data in the form of attributes that direct the EXEC or NETWORK session for that user and the services that the user can access: • • Telnet. TACACS+ Operation When a user attempts a simple ASCII login by authenticating to a switch using TACACS+. including the host or client IP address. When the connection is established. auditing. access list. The daemon prompts for a username and password combination. and user timeouts Catalyst 2960 and 2960-S Switches Software Configuration Guide. start and stop times. If the switch is configured to require authorization. authorization begins at this time. number of packets. depending on the TACACS+ daemon. ERROR—An error occurred at some time during authentication with the daemon or in the network connection between the daemon and the switch. the switch contacts the TACACS+ daemon to obtain a username prompt to show to the user. • After authentication. The user can be denied access or is prompted to retry the login sequence. this process occurs: 1. Accounting records include user identities. and the password is then sent to the TACACS+ daemon. You need a system running the TACACS+ daemon software to use TACACS+ on your switch. or protocol support. TACACS+ allows a dialog between the daemon and the user until the daemon receives enough information to authenticate the user. the switch typically tries to use an alternative method for authenticating the user. The switch eventually receives one of these responses from the TACACS+ daemon: • • • ACCEPT—The user is authenticated and service can begin. If an ACCEPT response is returned.

Note Although TACACS+ configuration is performed through the CLI. you must identify the host or hosts maintaining the TACACS+ daemon and define the method lists for TACACS+ authentication. or to keep accounts on a user. page 9-13 Configuring TACACS+ Login Authentication. thus ensuring a backup system if the initial method fails. Catalyst 2960 and 2960-S Switches Software Configuration Guide. You can optionally define method lists for TACACS+ authorization and accounting. To prevent a lapse in security. When enabled. The software uses the first method listed to authenticate. or to keep accounts on users. page 9-16 Starting TACACS+ Accounting. You can group servers to select a subset of the configured server hosts and use them for a particular service. Release 15. TACACS+ can authenticate users accessing the switch through the CLI. if that method does not respond.Chapter 9 Configuring Switch-Based Authentication Controlling Switch Access with TACACS+ Configuring TACACS+ This section describes how to configure your switch to support TACACS+. page 9-14 Configuring TACACS+ Authorization for Privileged EXEC Access and Network Services. At a minimum. You can use method lists to designate one or more security protocols to be used. page 9-13 Identifying the TACACS+ Server Host and Setting the Authentication Key. A method list defines the sequence and methods to be used to authenticate. to authorize. These sections contain this configuration information: • • • • • Default TACACS+ Configuration. The server group is used with a global server-host list and contains the list of IP addresses of the selected server hosts. page 9-17 Default TACACS+ Configuration TACACS+ and AAA are disabled by default. This process continues until there is successful communication with a listed method or the method list is exhausted. to authorize. you cannot configure TACACS+ through a network management application.0(1)SE OL-26520-02 9-13 . the software selects the next method in the list. Identifying the TACACS+ Server Host and Setting the Authentication Key You can configure the switch to use a single server or AAA server groups to group existing server hosts for authentication. the TACACS+ server authenticates HTTP connections that have been configured with a privilege level of 15.

The default is 5 seconds. (Optional) For port integer. The range is 1 to 1000 seconds. • Step 3 Step 4 aaa new-model aaa group server tacacs+ group-name server ip-address Enable AAA. use the no tacacs-server host hostname global configuration command. The range is 1 to 65535. Identify the IP host or hosts maintaining a TACACS+ server. The method list defines the types of authentication to be performed and the sequence in which they are performed. The software searches for hosts in the order in which you specify them. The default is port 49.0(1)SE 9-14 OL-26520-02 . Release 15. by coincidence. specify a server port number.Chapter 9 Controlling Switch Access with TACACS+ Configuring Switch-Based Authentication Beginning in privileged EXEC mode. (Optional) For timeout integer. • • • configure terminal tacacs-server host hostname [port integer] [timeout integer] [key string] For hostname. Enter this command multiple times to create a list of preferred hosts. Step 5 Step 6 Step 7 Step 8 end show tacacs copy running-config startup-config To remove the specified TACACS+ server name or address. To remove the IP address of a TACACS+ server. Verify your entries. Each server in the group must be previously defined in Step 2. specify the name or IP address of the host. thus ensuring a backup system for authentication in case the initial method fails. use the no aaa group server tacacs+ group-name global configuration command. To remove a server group from the configuration list. The default method list is automatically applied to all ports except those that have a named method list explicitly defined. you define a named list of authentication methods and then apply that list to various ports. use the no server ip-address server group subconfiguration command. The software uses the first method listed to Catalyst 2960 and 2960-S Switches Software Configuration Guide. The only exception is the default method list (which. (Optional) Save your entries in the configuration file. specify the encryption key for encrypting and decrypting all traffic between the switch and the TACACS+ daemon. (Optional) For key string. A method list describes the sequence and authentication methods to be queried to authenticate a user. it must be applied to a specific port before any of the defined authentication methods are performed. A defined method list overrides the default method list. Repeat this step for each TACACS+ server in the AAA server group. is named default). specify a time in seconds the switch waits for a response from the daemon before it times out and declares an error. Return to privileged EXEC mode. (Optional) Define the AAA server-group with a group name. follow these steps to identify the IP host or host maintaining TACACS+ server and optionally set the encryption key: Command Step 1 Step 2 Purpose Enter global configuration mode. Configuring TACACS+ Login Authentication To configure AAA authentication. You must configure the same key on the TACACS+ daemon for encryption to be successful. You can designate one or more security protocols to be used for authentication. This command puts the switch in a server group subconfiguration mode. (Optional) Associate a particular TACACS+ server with the defined server group.

if that method fails to respond. you must define a line password. Beginning in privileged EXEC mode. For more information. The additional methods of authentication are used only if the previous method returns an error. not if it fails. specify a character string to name the list you are creating. Enable AAA. and no other authentication methods are attempted. Create a login authentication method list. • • Select one of these methods: • • • • • • Step 4 line [console | tty | vty] line-number [ending-line-number] Enter line configuration mode. You must enter username information in the database. Use the password password line configuration command. local—Use the local username database for authentication. If authentication fails at any point in this cycle—meaning that the security server or local username database responds by denying the user access—the authentication process stops. Before you can use this authentication method. line—Use the line password for authentication. This process continues until there is successful communication with a listed authentication method or until all defined methods are exhausted.] To create a default list that is used when a named list is not specified in the login authentication command. Release 15. For list-name. • configure terminal aaa new-model aaa authentication login {default | list-name} method1 [method2. and configure the lines to which you want to apply the authentication list. enable—Use the enable password for authentication.Chapter 9 Configuring Switch-Based Authentication Controlling Switch Access with TACACS+ authenticate users.. the software selects the next authentication method in the method list. use the default keyword followed by the methods that are to be used in default situations. local-case—Use a case-sensitive local username database for authentication.. Catalyst 2960 and 2960-S Switches Software Configuration Guide. you must configure the TACACS+ server. The default method list is automatically applied to all ports.. you must define an enable password by using the enable password global configuration command. You must enter username information in the database by using the username name password global configuration command. specify the actual method the authentication algorithm tries. see the “Identifying the TACACS+ Server Host and Setting the Authentication Key” section on page 9-13.. group tacacs+—Uses TACACS+ authentication. Use the username password global configuration command. Before you can use this authentication method.. none—Do not use any authentication for login. Before you can use this authentication method. follow these steps to configure login authentication: Command Step 1 Step 2 Step 3 Purpose Enter global configuration mode.0(1)SE OL-26520-02 9-15 . For method1.

To either disable TACACS+ authentication for logins or to return to the default value. (Optional) Save your entries in the configuration file. Configure the switch for user TACACS+ authorization for all network-related service requests. use the no aaa new-model global configuration command. Verify your entries. • • login authentication {default | list-name} If you specify default. The aaa authorization exec tacacs+ local command sets these authorization parameters: • • Use TACACS+ for privileged EXEC access authorization if authentication was performed by using TACACS+. For list-name. Note To secure the switch for HTTP access by using AAA methods. Step 6 Step 7 Step 8 end show running-config copy running-config startup-config Return to privileged EXEC mode. The user is granted access to a requested service only if the information in the user profile allows it. to configure the user’s session. Note Authorization is bypassed for authenticated users who log in through the CLI even if authorization has been configured. specify the list created with the aaa authentication login command. Release 15. see the Cisco IOS Security Command Reference. follow these steps to specify TACACS+ authorization for privileged EXEC access and network services: Command Step 1 Step 2 Purpose Enter global configuration mode. Configuring AAA authentication does not secure the switch for HTTP access by using AAA methods. To disable AAA. Release 12. When AAA authorization is enabled. Use the local database if authentication was not performed by using TACACS+.0(1)SE 9-16 OL-26520-02 . which is located either in the local user database or on the security server. configure terminal aaa authorization network tacacs+ Catalyst 2960 and 2960-S Switches Software Configuration Guide.com. Configuring TACACS+ Authorization for Privileged EXEC Access and Network Services AAA authorization limits the services available to a user.] global configuration command.. you must configure the switch with the ip http authentication aaa global configuration command. use the no login authentication {default | list-name} line configuration command.4 on Cisco. use the default list created with the aaa authentication login command. Beginning in privileged EXEC mode. the switch uses information retrieved from the user’s profile. For more information about the ip http authentication command. To disable AAA authentication. You can use the aaa authorization global configuration command with the tacacs+ keyword to set parameters that restrict a user’s network access to privileged EXEC mode. use the no aaa authentication login {default | list-name} method1 [method2..Chapter 9 Controlling Switch Access with TACACS+ Configuring Switch-Based Authentication Command Step 5 Purpose Apply the authentication list to a line or set of lines.

In some situations. (Optional) Save your entries in the configuration file. use the no aaa accounting {network | exec} {start-stop} method1. Each accounting record contains accounting attribute-value (AV) pairs and is stored on the security server. Enable TACACS+ accounting to send a start-record accounting notice at the beginning of a privileged EXEC process and a stop-record at the end. Return to privileged EXEC mode. follow these steps to enable TACACS+ accounting for each Cisco IOS privilege level and for network services: Command Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Purpose Enter global configuration mode. configure terminal aaa accounting network start-stop tacacs+ aaa accounting exec start-stop tacacs+ end show running-config copy running-config startup-config To disable accounting.0(1)SE OL-26520-02 9-17 . Catalyst 2960 and 2960-S Switches Software Configuration Guide. (Optional) Save your entries in the configuration file. Verify your entries.. or auditing. This data can then be analyzed for network management. global configuration command. Release 15. the switch reports user activity to the TACACS+ security server in the form of accounting records. users might be prevented from starting a session on the console or terminal connection until after the system reloads. aaa authorization exec tacacs+ Step 4 Step 5 Step 6 end show running-config copy running-config startup-config Return to privileged EXEC mode. use the no aaa authorization {network | exec} method1 global configuration command. Verify your entries. which is the default condition. To disable authorization.Chapter 9 Configuring Switch-Based Authentication Controlling Switch Access with TACACS+ Command Step 3 Purpose Configure the switch for user TACACS+ authorization if the user has privileged EXEC access. Enable TACACS+ accounting for all network-related service requests. client billing. Beginning in privileged EXEC mode. Establishing a Session with a Router if the AAA Server is Unreachable Note To configure this command. When AAA accounting is enabled.. The aaa accounting system guarantee-first command guarantees system accounting as the first record. The exec keyword might return user profile information (such as autocommand information). which can take more than 3 minutes. Starting TACACS+ Accounting The AAA accounting feature tracks the services that users are accessing and the amount of network resources that they are consuming. the switch must be running the LAN Base image.

Clients send authentication requests to a central RADIUS server. This is to help ensure that the RADIUS server remains accessible in case one of the connected stack members is removed from the switch stack. Note We recommend a redundant connection between a switch stack and the RADIUS server. Beginning with Cisco IOS Release 12. Microsoft.0(1)SE 9-18 OL-26520-02 . RADIUS is facilitated through AAA and can be enabled only through AAA commands. Release 15. or another software provider. For information about configuring this feature.0). use the no aaa accounting system guarantee-first command. Catalyst 2960 and 2960-S Switches Software Configuration Guide.2(58)SE. RADIUS clients run on supported Cisco routers and switches. Release 2. the switch supports RADIUS for IPv6. Merit. which provides detailed accounting information and flexible administrative control over authentication and authorization processes. Information is in the “RADIUS Over IPv6” section of the “Implementing ADSL for IPv6” chapter in the Cisco IOS XE IPv6 Configuration Guide. page 9-18 RADIUS Operation. Note For complete syntax and usage information for the commands used in this section. see the RADIUS server documentation. page 9-27 Displaying the RADIUS Configuration. Release 2. see the Cisco IOS Security Command Reference and the Cisco IOS IPv6 Command Reference.Chapter 9 Controlling Switch Access with RADIUS Configuring Switch-Based Authentication To establish a console or Telnet session with the router if the AAA server is unreachable when the router reloads. The RADIUS host is normally a multiuser system running RADIUS server software from Cisco (Cisco Secure Access Control Server Version 3. see the “Configuring the NAS” section in the “Implementing ADSL for IPv6” chapter in the Cisco IOS XE IPv6 Configuration Guide. Displaying the TACACS+ Configuration To display TACACS+ server statistics. use the show tacacs privileged EXEC command. page 9-20 Configuring RADIUS. Livingston. For more information. Controlling Switch Access with RADIUS This section describes how to enable and configure the RADIUS. page 9-40 Understanding RADIUS RADIUS is a distributed client/server system that secures networks against unauthorized access. These sections contain this configuration information: • • • • • Understanding RADIUS. which contains all user authentication and network service access information. page 9-20 RADIUS Change of Authorization.

RADIUS generally binds a user to one service model. Turnkey network security environments in which applications support the RADIUS protocol. NetBIOS Frame Control Protocol (NBFCP).25 PAD connections. RADIUS does not support AppleTalk Remote Access (ARA). RADIUS can be used to authenticate from one device to a non-Cisco device if the non-Cisco device requires authentication. and so forth) used during the session. see Chapter 10. showing the amount of resources (such as time. Using RADIUS. dial-in users are authenticated through a RADIUS server that has been customized to work with the Kerberos security system. or X.1x. to a single utility such as Telnet. “Configuring IEEE 802. This might be the first step when you make a transition to a TACACS+ server. Release 15. bytes. For more information about this protocol. In one case. such as in an access environment that uses a smart card access control system.” Networks that require resource accounting. Network in which the user must only access a single service.Chapter 9 Configuring Switch-Based Authentication Controlling Switch Access with RADIUS Use RADIUS in these network environments that require access security: • Networks with multiple-vendor access servers. You can use RADIUS accounting independently of RADIUS authentication or authorization.0(1)SE OL-26520-02 86891 9-19 . or to the network through a protocol such as IEEE 802. RADIUS does not provide two-way authentication. Multiprotocol access environments. you can control user access to a single host. Networks already using RADIUS. In an IP-based network with multiple vendors’ access servers. See Figure 9-2 on page 9-19. packets. Switch-to-switch or router-to-router situations. each supporting RADIUS. access servers from several vendors use a single RADIUS server-based security database. RADIUS has been used with Enigma’s security cards to validates users and to grant access to network resources. Networks using a variety of services.1x Port-Based Authentication. The RADIUS accounting functions allow data to be sent at the start and end of services. You can add a Cisco switch containing a RADIUS client to the network. Transitioning from RADIUS to TACACS+ Services • • • • RADIUS is not suitable in these network security situations: • • • Figure 9-2 R1 RADIUS server RADIUS server TACACS+ server TACACS+ server R2 T1 Remote PC T2 Workstation Catalyst 2960 and 2960-S Switches Software Configuration Guide. For example. An Internet service provider might use a freeware-based version of RADIUS access control and accounting software to meet special security and billing needs. NetWare Asynchronous Services Interface (NASI).

CHALLENGE—A challenge requires additional data from the user. Beginning with Cisco IOS Release 12. including the host or client IP address. REJECT—The user is either not authenticated and is prompted to re-enter the username and password. or privileged EXEC services Connection parameters. page 9-21 CoA Request Response Code. The username and encrypted password are sent over the network to the RADIUS server. the switch must be running the LAN Base image. Catalyst switches support the RADIUS Change of Authorization (CoA) extensions defined in RFC 5176 that are typically used in a pushed model and allow for the dynamic reconfiguring of sessions from external authentication.Chapter 9 Controlling Switch Access with RADIUS Configuring Switch-Based Authentication RADIUS Operation When a user attempts to log in and authenticate to a switch that is access controlled by a RADIUS server. ACCEPT—The user is authenticated. authorization. • • • • • • Overview. b. Release 15. the switch supports these per-session CoA requests: • • • Session reauthentication Session termination Session termination with port shutdown Catalyst 2960 and 2960-S Switches Software Configuration Guide. The user is prompted to enter a username and password. Users must first successfully complete RADIUS authentication before proceeding to RADIUS authorization. or access is denied. if it is enabled. This section provides an overview of the RADIUS interface including available primitives and how they are used during a Change of Authorization (CoA). and user timeouts RADIUS Change of Authorization To use this feature. these events occur: 1. The user receives one of these responses from the RADIUS server: a. SSH. CHALLENGE PASSWORD—A response requests the user to select a new password. page 9-22 CoA Request Commands. The ACCEPT or REJECT response is bundled with additional data that is used for privileged EXEC or network authorization. access list.0(1)SE 9-20 OL-26520-02 . page 9-26 Overview A standard RADIUS interface is typically used in a pulled model where the request originates from a network attached device and the response come from the queried servers. d. 2. 3. page 9-24 Stacking Guidelines for Session Termination. and accounting (AAA) or policy servers. page 9-23 Session Reauthentication. rlogin. The additional data included with the ACCEPT or REJECT packets includes these items: • • Telnet. c.2(52)SE. page 9-20 Change-of-Authorization Requests.

Table 9-2 Supported IETF Attributes Attribute Number 24 31 44 80 101 Attribute Name State Calling-Station-ID Acct-Session-ID Message-Authenticator Error-Cause Table 9-3 shows the possible values for the Error-Cause attribute. Table 9-2 shows the IETF attributes are supported for this feature.0(1)SE OL-26520-02 9-21 . is supported by the switch for session termination.2(50)SE.html The RADIUS interface is enabled by default on Catalyst switches.Chapter 9 Configuring Switch-Based Authentication Controlling Switch Access with RADIUS • Session termination with port bounce This feature is integrated with the Cisco Secure Access Control Server (ACS) 5. some basic configuration is required for these attributes: • Security and Password—See the “Preventing Unauthorized Access to Your Switch” section in the “Configuring Switch-Based Authentication” chapter in the Catalyst 3750 Switch Software Configuration Guide. as described in RFC 5176. This section includes these topics: • • • CoA Request Response Code CoA Request Commands Session Reauthentication RFC 5176 Compliance The Disconnect Request message. The model is comprised of one request (CoA-Request) and two possible response codes: • • CoA acknowledgement (ACK) [CoA-ACK] CoA non-acknowledgement (NAK) [CoA-NAK] The request is initiated from a CoA client (typically a RADIUS or policy server) and directed to the switch that acts as a listener.cisco.2(50)SE. Cisco Release 12. Accounting—See the “Starting RADIUS Accounting” section in the “Configuring Switch-Based Authentication” chapter in the Catalyst 3750 Switch Software Configuration Guide. Catalyst 2960 and 2960-S Switches Software Configuration Guide. However. are used in a push model to allow for session identification. and session termination. For information about ACS: http://www. Release 15. which is also referred to as Packet of Disconnect (POD). • Change-of-Authorization Requests Change of Authorization (CoA) requests.1. host reauthentication. 12.com/en/US/products/ps9911/tsd_products_support_series_home.

The supported commands are listed in Table 9-4 on page 9-24.0(1)SE 9-22 OL-26520-02 . the switch returns a Disconnect-NAK or CoA-NAK with the Invalid Attribute Value error-code attribute. Session Identification For disconnect and CoA requests targeted at a particular session. Catalyst 2960 and 2960-S Switches Software Configuration Guide. CoA can be used to identify a session and enforce a disconnect request. the switch locates the session based on one or more of the following attributes: • • • Calling-Station-Id (IETF attribute 31 which contains the host MAC address) Audit-Session-Id (Cisco VSA) Acct-Session-Id (IETF attribute 44) Unless all session identification attributes included in the CoA message match the session. CoA Request Response Code The CoA Request response code can be used to convey a command to the switch. The update affects only the specified session.Chapter 9 Controlling Switch Access with RADIUS Configuring Switch-Based Authentication Table 9-3 Error-Cause Values Value 201 202 401 402 403 404 405 406 407 501 502 503 504 505 506 507 508 Explanation Residual Session Context Removed Invalid EAP Packet (Ignored) Unsupported Attribute Missing Attribute NAS Identification Mismatch Invalid Request Unsupported Service Unsupported Extension Invalid Attribute Value Administratively Prohibited Request Not Routable (Proxy) Session Context Not Found Session Context Not Removable Other Proxy Processing Error Resources Unavailable Request Initiated Multiple Session Selection Unsupported Preconditions To use the CoA interface. a session must already exist on the switch. Release 15.

0(1)SE OL-26520-02 9-23 . CoA NAK Response Code A negative acknowledgement (NAK) indicates a failure to change the authorization state and can include attributes that indicate the reason for the failure. CoA Request Commands This section includes: • • • • • • Session Reauthentication Session Reauthentication in a Switch Stack Session Termination CoA Disconnect-Request CoA Request: Disable Host Port CoA Request: Bounce-Port Beginning with Cisco IOS Release 12. If more than one session identification attribute is included in the message. Identifier.Chapter 9 Configuring Switch-Based Authentication Controlling Switch Access with RADIUS For disconnect and CoA requests targeted to a particular session.. a positive acknowledgement (ACK) is sent. 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Code | Identifier | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | | Authenticator | | | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Attributes . Release 15.negative acknowledgement (NAK) or CoA-NAK with the error code Invalid Attribute Value. The attributes returned within CoA ACK will vary based on the CoA Request and are discussed in individual CoA Commands. Length. which should contain the MAC address) Audit-Session-ID (Cisco vendor-specific attribute) Accounting-Session-ID (IETF attribute 44). +-+-+-+-+-+-+-+-+-+-+-+-+- The attributes field is used to carry Cisco VSAs. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Authenticator. CoA ACK Response Code If the authorization state is changed successfully. all the attributes must match the session or the switch returns a Disconnect.. The packet format for a CoA Request code as defined in RFC 5176 consists of the fields: Code.2(52)SE. and Attributes in Type:Length:Value (TLV) format. any one of these session identifiers can be used: • • • Calling-Station-ID (IETF attribute 31. Use show commands to verify a successful CoA. the switch supports the commands shown in Table 9-4.

the switch sends an access-request to the server. the reauthentication message restarts the access control methods. the signal that triggered the reauthentication is removed from the stack member. the switch responds by sending an Extensible Authentication Protocol over LAN (EAPoL) RequestId message to the server. Catalyst 2960 and 2960-S Switches Software Configuration Guide. and restarts the authentication sequence. The current authorization of the session is maintained until the reauthentication leads to a different authorization result. If the session is currently authenticated by IEEE 802. Session Reauthentication in a Switch Stack When a switch stack receives a session reauthentication message: • • • • • It checkpoints the need for a re-authentication before returning an acknowledgement (ACK). beginning with the method configured to be attempted first. the new stack master treats the re-transmitted command as a new command. passing the same identity attributes used for the initial successful authentication. or similar policies. or is authorized via guest VLAN. If authentication completes with either success or failure. starting with the method configured to be attempted first. reauthentication is initiated after stack master switch-over based on the original command (which is subsequently removed). If the stack master fails before authentication completes. It initiates reauthentication for the appropriate session.1x. Session Reauthentication The AAA server typically generates a session reauthentication request when a host with an unknown identity or posture joins the network and is associated with a restricted access authorization profile (such as a guest VLAN). Release 15.Chapter 9 Controlling Switch Access with RADIUS Configuring Switch-Based Authentication Table 9-4 CoA Commands Supported on the Switch Command1 Reauthenticate host Terminate session Bounce host port Disable host port Cisco VSA Cisco:Avpair=“subscriber:command=reauthenticate” This is a standard disconnect request that does not require a VSA. A reauthentication request allows the host to be placed in the appropriate authorization group when its credentials are known. All CoA commands must include the session identifier between the switch and the CoA client. Cisco:Avpair=“subscriber:command=bounce-host-port” Cisco:Avpair=“subscriber:command=disable-host-port” 1. The current session state determines the switch response to the message. the switch terminates the process. To initiate session authentication.0(1)SE 9-24 OL-26520-02 . If the session is currently authenticated by MAC authentication bypass (MAB). If the session is not yet authorized. the AAA server sends a standard CoA-Request message which contains a Cisco vendor-specific attribute (VSA) in this form: Cisco:Avpair=“subscriber:command=reauthenticate” and one or more session identification attributes. or critical VLAN. If the stack master fails before sending an ACK. If session authentication is in progress when the switch receives the command.

This command causes re-initialization of the authenticator state machine for the specified host.Chapter 9 Configuring Switch-Based Authentication Controlling Switch Access with RADIUS Session Termination There are three types of CoA requests that can trigger session termination. the switch returns a Disconnect-ACK. re-enable it using a non-RADIUS mechanism. Note A Disconnect-Request failure following command re-sending could be the result of either a successful session termination before change-over (if the Disconnect-ACK was not sent) or a session termination by other means (for example. If the session is located. If the switch fails-over to a standby switch before returning a Disconnect-ACK to the client. Release 15. Because this command is session-oriented. and you need to immediately block network access for the host. If the switch fails before returning a CoA-ACK to the client. use a CoA Request with the Cisco:Avpair="subscriber:command=disable-host-port" VSA. needs to acquire a new IP address (for example. CoA Disconnect-Request This command is a standard Disconnect-Request. When you want to restore network access on the port. it must be accompanied by one or more of the session identification attributes described in the “Session Identification” section on page 9-22. a Disconnect-ACK is sent with the “Session Context Not Found” error-code attribute.0(1)SE OL-26520-02 9-25 . If the session is located. the operation is restarted on the new active switch. a link failure) that occurred after the original command was issued and before the standby switch became active. the switch disables the hosting port and returns a CoA-ACK message. Catalyst 2960 and 2960-S Switches Software Configuration Guide. the switch returns a CoA-NAK message with the “Session Context Not Found” error-code attribute. the process is repeated on the new active switch when the request is re-sent from the client. After the session has been completely removed. after a VLAN change). without disabling the host port. the switch returns a Disconnect-NAK message with the “Session Context Not Found” error-code attribute. When a device with no supplicant. CoA Request: Disable Host Port This command is carried in a standard CoA-Request message that has this new VSA: Cisco:Avpair="subscriber:command=disable-host-port" Because this command is session-oriented. terminate the session on the host port with port-bounce (temporarily disable and then re-enable the port). the process is repeated on the new active switch when the request is re-sent from the client. it must be accompanied by one or more of the session identification attributes described in the “Session Identification” section on page 9-22. To restrict a host’s access to the network. A CoA Disconnect-Request terminates the session. the switch terminates the session. If the session is not found following re-sending. such as a printer. If the session cannot be located. If the session cannot be located. If the switch fails after returning a CoA-ACK message to the client but before the operation has completed. This command is useful when a host is known to be causing problems on the network. but does not restrict that host’s access to the network.

If the session is located. Catalyst 2960 and 2960-S Switches Software Configuration Guide.0(1)SE 9-26 OL-26520-02 . the new stack master treats the re-sent command as a new command. it verifies this information before returning a CoA-ACK message: • • Need for a port-disable Port-ID (in the local session context) The switch attempts to disable the port. then re-enables it). the port is disabled after stack master change-over based on the original command (which is subsequently removed). a port-bounce is initiated after stack master change-over based on the original command (which is subsequently removed). the command cannot be executed. and returns a CoA-ACK. Stacking Guidelines for CoA-Request Disable-Port Because the disable-port command is targeted at a session. the signal that triggered the port-disable is removed from the standby stack master. If the stack master fails before the port-bounce completes. not a port. If the stack master fails before sending a CoA-ACK message. If the session cannot be located. When the Auth Manager command handler on the stack master receives a valid disable-port command. If the switch fails before returning a CoA-ACK to the client. the process is repeated on the new active switch when the request is re-sent from the client. the switch disables the hosting port for a period of 10 seconds. it must be accompanied by one or more of the session identification attributes described in the “Session Identification” section on page 9-22. not a port. Stacking Guidelines for CoA-Request Bounce-Port Because the bounce-port command is targeted at a session. it checkpoints this information before returning a CoA-ACK message: • • Need for a port-bounce Port-ID (found in the local session context) The switch initiates a port-bounce (disables the port for 10 seconds. Release 15. If the port-disable operation is successful. When the Auth Manager command handler on the stack master receives a valid bounce-port command. If the port-bounce is successful. Stacking Guidelines for Session Termination No special handling is required for CoA Disconnect-Request messages in a switch stack. If the stack master fails before the port-disable operation completes. the signal that triggered the port-bounce is removed from the standby stack master. the switch returns a CoA-NAK message with the “Session Context Not Found” error-code attribute.Chapter 9 Controlling Switch Access with RADIUS Configuring Switch-Based Authentication CoA Request: Bounce-Port This command is carried in a standard CoA-Request message that contains this VSA: Cisco:Avpair="subscriber:command=bounce-host-port" Because this command is session-oriented. re-enables it (port-bounce). If the switch fails after returning a CoA-ACK message to the client but before the operation has completed. if the session is not found. the operation is re-started on the new active switch. the command cannot be executed. if the session is not found.

To prevent a lapse in security. page 9-32 (optional) Configuring RADIUS Authorization for User Privileged Access and Network Services. If that method does not respond. page 9-27 Identifying the RADIUS Server Host. page 9-28 (required) Configuring RADIUS Login Authentication. to authorize. page 9-39 Monitoring and Troubleshooting CoA Functionality. you must identify the host or hosts that run the RADIUS server software and define the method lists for RADIUS authentication. thus ensuring a backup system if the initial method fails. A method list defines the sequence and methods to be used to authenticate. You should have access to and should configure a RADIUS server before configuring RADIUS features on your switch. page 9-40 Configuring RADIUS Server Load Balancing. At a minimum.0(1)SE OL-26520-02 9-27 . Configuring RADIUS This section describes how to configure your switch to support RADIUS. or to keep accounts on a user. page 9-38 (optional) Configuring CoA on the Switch. page 9-36 (optional) Configuring the Switch for Vendor-Proprietary RADIUS Server Communication. or to keep accounts on users.Chapter 9 Configuring Switch-Based Authentication Controlling Switch Access with RADIUS If the stack master fails before sending a CoA-ACK message. You can use method lists to designate one or more security protocols to be used (such as TACACS+ or local username lookup). Release 15. the software selects the next method in the list. page 9-35 (optional) Configuring Settings for All RADIUS Servers. When enabled. Catalyst 2960 and 2960-S Switches Software Configuration Guide. RADIUS can authenticate users accessing the switch through the CLI. The software uses the first method listed to authenticate. page 9-36 (optional) Configuring the Switch to Use Vendor-Specific RADIUS Attributes. You can optionally define method lists for RADIUS authorization and accounting. the new stack master treats the re-sent command as a new command. page 9-40 (optional) Default RADIUS Configuration RADIUS and AAA are disabled by default. page 9-30 (required) Defining AAA Server Groups. • • • • • • • • • • • • Default RADIUS Configuration. you cannot configure RADIUS through a network management application. page 9-34 (optional) Starting RADIUS Accounting. This process continues until there is successful communication with a listed method or the method list is exhausted. to authorize.

radius-server retransmit. and encryption key values can be configured globally for all RADIUS servers. and then the switch tries the second host entry configured on the same device for accounting services. For more information. (The RADIUS host entries are tried in the order that they are configured. retransmission. Release 15. To apply these values on a specific RADIUS server. retransmission. the per-server timer. and radius-server key. use the radius-server host global configuration command. and key value commands. If two different host entries on the same RADIUS server are configured for the same service—for example. or in some combination of global and per-server settings. hostname and specific UDP port numbers. see the “Defining AAA Server Groups” section on page 9-32. retransmission. The timeout. To configure RADIUS to use the AAA security commands. or their IP address and specific UDP port numbers. Catalyst 2960 and 2960-S Switches Software Configuration Guide. allowing different ports to be individually defined as RADIUS hosts providing a specific AAA service. The combination of the IP address and the UDP port number creates a unique identifier. you must specify the host running the RADIUS server daemon and a secret text (key) string that it shares with the switch. Using this example. This unique identifier enables RADIUS requests to be sent to multiple UDP ports on a server at the same IP address.Chapter 9 Controlling Switch Access with RADIUS Configuring Switch-Based Authentication Identifying the RADIUS Server Host Switch-to-RADIUS-server communication involves several components: • • • • • • Hostname or IP address Authentication destination port Accounting destination port Key string Timeout period Retransmission value You identify RADIUS security servers by their hostname or IP address. the %RADIUS-4-RADIUS_DEAD message appears. and key commands) on the switch. if the first host entry fails to provide accounting services. For information on configuring these settings on all RADIUS servers. see the “Configuring Settings for All RADIUS Servers” section on page 9-36. use the three unique global configuration commands: radius-server timeout. To apply these settings globally to all RADIUS servers communicating with the switch. Note If you configure both global and per-server functions (timeout. accounting—the second host entry configured acts as a fail-over backup to the first one. on a per-server basis.) A RADIUS server and the switch use a shared secret text string to encrypt passwords and exchange responses. retransmission. You can configure the switch to use AAA server groups to group existing server hosts for authentication. and key value commands override global timer.0(1)SE 9-28 OL-26520-02 .

the setting of the radius-server timeout command is used. The range is 1 to 1000. The key is a text string that must match the encryption key used on the RADIUS server.49 auth-port 1612 key rad1 Switch(config)# radius-server host 172. retransmit. (Optional) Save your entries in the configuration file.50 acct-port 1618 key rad2 Catalyst 2960 and 2960-S Switches Software Configuration Guide. enter this command as many times as necessary. Set the timeout. specify the UDP destination port for authentication requests. • • Note To configure the switch to recognize more than one host entry associated with a single IP address. but spaces within and at the end of the key are used. Leading spaces are ignored. Release 15. do not enclose the key in quotation marks unless the quotation marks are part of the key.0(1)SE OL-26520-02 9-29 . Always configure the key as the last item in the radius-server host command.29. Verify your entries. (Optional) For key string. This procedure is required. specify the number of times a RADIUS request is resent to a server if that server is not responding or responding slowly. To remove the specified RADIUS server. Step 3 Step 4 Step 5 end show running-config copy running-config startup-config Return to privileged EXEC mode. making sure that each UDP port number is different. The switch software searches for hosts in the order in which you specify them.36. The range is 1 to 1000. specify the UDP destination port for accounting requests. If you use spaces in your key. This example shows how to configure one RADIUS server to be used for authentication and another to be used for accounting: Switch(config)# radius-server host 172.20. and encryption key values to use with the specific RADIUS host. Specify the IP address or hostname of the remote RADIUS server host. (Optional) For retransmit retries. (Optional) For acct-port port-number.Chapter 9 Configuring Switch-Based Authentication Controlling Switch Access with RADIUS Beginning in privileged EXEC mode. Command Step 1 Step 2 Purpose Enter global configuration mode. use the no radius-server host hostname | ip-address global configuration command. If no retransmit value is set with the radius-server host command. (Optional) For timeout seconds. follow these steps to configure per-server RADIUS server communication. This setting overrides the radius-server timeout global configuration command setting.36. If no timeout is set with the radius-server host command. specify the authentication and encryption key used between the switch and the RADIUS daemon running on the RADIUS server. • • • configure terminal radius-server host {hostname | ip-address} [auth-port port-number] [acct-port port-number] [timeout seconds] [retransmit retries] [key string] (Optional) For auth-port port-number. specify the time interval that the switch waits for the RADIUS server to reply before resending. the setting of the radius-server retransmit global configuration command is used.

it must be applied to a specific port before any of the defined authentication methods are performed. Command Step 1 Step 2 Purpose Enter global configuration mode. and no other authentication methods are attempted. Beginning in privileged EXEC mode. by coincidence. For more information. These settings include the IP address of the switch and the key string to be shared by both the server and the switch. thus ensuring a backup system for authentication in case the initial method fails. the software selects the next authentication method in the method list. is named default). Configuring RADIUS Login Authentication To configure AAA authentication. The software uses the first method listed to authenticate users. you define a named list of authentication methods and then apply that list to various ports. follow these steps to configure login authentication.0(1)SE 9-30 OL-26520-02 . If authentication fails at any point in this cycle—meaning that the security server or local username database responds by denying the user access—the authentication process stops. if that method fails to respond. This process continues until there is successful communication with a listed authentication method or until all defined methods are exhausted. The default method list is automatically applied to all ports except those that have a named method list explicitly defined. see the RADIUS server documentation. configure terminal aaa new-model Catalyst 2960 and 2960-S Switches Software Configuration Guide. The only exception is the default method list (which. Release 15. This procedure is required. The method list defines the types of authentication to be performed and the sequence in which they are performed. A method list describes the sequence and authentication methods to be queried to authenticate a user.Chapter 9 Controlling Switch Access with RADIUS Configuring Switch-Based Authentication This example shows how to configure host1 as the RADIUS server and to use the default ports for both authentication and accounting: Switch(config)# radius-server host host1 Note You also need to configure some settings on the RADIUS server. You can designate one or more security protocols to be used for authentication. Enable AAA.

. Step 4 Step 5 line [console | tty | vty] line-number [ending-line-number] login authentication {default | list-name} Enter line configuration mode. specify the actual method the authentication algorithm tries. Catalyst 2960 and 2960-S Switches Software Configuration Guide. You must enter username information in the database by using the username password global configuration command.Chapter 9 Configuring Switch-Based Authentication Controlling Switch Access with RADIUS Command Step 3 Purpose aaa authentication login {default Create a login authentication method list. • • For list-name. you must define a line password. For method1.0(1)SE OL-26520-02 9-31 . For more information. and configure the lines to which you want to apply the authentication list.. – local—Use the local username database for authentication. – group radius—Use RADIUS authentication... You must enter username information in the database. • • If you specify default. specify a character string to name the list you are creating. Before you can use this authentication method. see the “Identifying the RADIUS Server Host” section on page 9-28. Verify your entries.. you must define an enable password by using the enable password global configuration command. Use the username name password global configuration command. Release 15. use the default list created with the aaa authentication login command. The default method list is automatically applied to all ports. you must configure the RADIUS server. For list-name. use the default keyword followed by the methods that are to be used in default situations. | list-name} method1 [method2. specify the list created with the aaa authentication login command. (Optional) Save your entries in the configuration file. Select one of these methods: – enable—Use the enable password for authentication. Before you can use this authentication method. – line—Use the line password for authentication. Use the password password line configuration command. Before you can use this authentication method.] • To create a default list that is used when a named list is not specified in the login authentication command. – none—Do not use any authentication for login. – local-case—Use a case-sensitive local username database for authentication. The additional methods of authentication are used only if the previous method returns an error. Apply the authentication list to a line or set of lines. not if it fails. Step 6 Step 7 Step 8 end show running-config copy running-config startup-config Return to privileged EXEC mode.

(for example. You can either identify the server by its IP address or identify multiple host instances or entries by using the optional auth-port and acct-port keywords. Release 15. To disable AAA authentication.4 on Cisco. see the Cisco IOS Security Command Reference. For more information about the ip http authentication command. Note To secure the switch for HTTP access by using AAA methods. use the no login authentication {default | list-name} line configuration command.Chapter 9 Controlling Switch Access with RADIUS Configuring Switch-Based Authentication To disable AAA. You select a subset of the configured server hosts and use them for a particular service. accounting). If you configure two different host entries on the same RADIUS server for the same service. Catalyst 2960 and 2960-S Switches Software Configuration Guide. allowing different ports to be individually defined as RADIUS hosts providing a specific AAA service. To either disable RADIUS authentication for logins or to return to the default value.. Server groups also can include multiple host entries for the same server if each entry has a unique identifier (the combination of the IP address and UDP port number).0(1)SE 9-32 OL-26520-02 . use the no aaa new-model global configuration command.. Configuring AAA authentication does not secure the switch for HTTP access by using AAA methods. Release 12. Defining AAA Server Groups You can configure the switch to use AAA server groups to group existing server hosts for authentication. you must configure the switch with the ip http authentication aaa global configuration command. which lists the IP addresses of the selected server hosts. You use the server group server configuration command to associate a particular server with a defined group server. use the no aaa authentication login {default | list-name} method1 [method2.] global configuration command. the second configured host entry acts as a fail-over backup to the first one.com. The server group is used with a global server-host list.

The range is 1 to 1000. • • Note To configure the switch to recognize more than one host entry associated with a single IP address. If no retransmit value is set with the radius-server host command.0(1)SE OL-26520-02 9-33 . making sure that each UDP port number is different. and encryption key values to use with the specific RADIUS host.Chapter 9 Configuring Switch-Based Authentication Controlling Switch Access with RADIUS Beginning in privileged EXEC mode. specify the number of times a RADIUS request is resent to a server if that server is not responding or responding slowly. (Optional) For retransmit retries. Each server in the group must be previously defined in Step 2. • • • configure terminal radius-server host {hostname | ip-address} [auth-port port-number] [acct-port port-number] [timeout seconds] [retransmit retries] [key string] (Optional) For auth-port port-number. Define the AAA server-group with a group name. Associate a particular RADIUS server with the defined server group. Leading spaces are ignored. If no timeout is set with the radius-server host command. The switch software searches for hosts in the order in which you specify them. Repeat this step for each RADIUS server in the AAA server group. enter this command as many times as necessary. (Optional) For timeout seconds. Step 5 Step 6 Step 7 end show running-config Catalyst 2960 and 2960-S Switches Software Configuration Guide. specify the UDP destination port for accounting requests. This command puts the switch in a server group configuration mode. do not enclose the key in quotation marks unless the quotation marks are part of the key. If you use spaces in your key. Step 3 Step 4 aaa new-model aaa group server radius group-name server ip-address Enable AAA. The range is 1 to 1000. but spaces within and at the end of the key are used. (Optional) For acct-port port-number. specify the authentication and encryption key used between the switch and the RADIUS daemon running on the RADIUS server. The key is a text string that must match the encryption key used on the RADIUS server. (Optional) For key string. Always configure the key as the last item in the radius-server host command. Verify your entries. This setting overrides the radius-server timeout global configuration command setting. specify the time interval that the switch waits for the RADIUS server to reply before resending. Release 15. follow these steps to define the AAA server group and associate a particular RADIUS server with it: Command Step 1 Step 2 Purpose Enter global configuration mode. retransmit. Return to privileged EXEC mode. Set the timeout. the setting of the radius-server retransmit global configuration command is used. Specify the IP address or hostname of the remote RADIUS server host. specify the UDP destination port for authentication requests. the setting of the radius-server timeout command is used.

20. To remove a server group from the configuration list.0. The user is granted access to a requested service only if the information in the user profile allows it. to configure the user’s session.20.10. which is in the local user database or on the security server. use the no aaa group server radius group-name global configuration command. The aaa authorization exec radius local command sets these authorization parameters: • • Use RADIUS for privileged EXEC access authorization if authentication was performed by using RADIUS. Enable RADIUS login authentication.0. use the no radius-server host hostname | ip-address global configuration command. In this example. Switch(config)# radius-server host 172. To remove the specified RADIUS server. the switch is configured to recognize two different RADIUS group servers (group1 and group2).0.1 auth-port 2000 acct-port 2001 Switch(config-sg-radius)# exit copy running-config startup-config Configuring RADIUS Authorization for User Privileged Access and Network Services AAA authorization limits the services available to a user. See the “Configuring RADIUS Login Authentication” section on page 9-30. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Group1 has two different host entries on the same RADIUS server configured for the same services.0. To remove the IP address of a RADIUS server.0(1)SE 9-34 OL-26520-02 .1 auth-port 1645 acct-port 1646 Switch(config)# aaa new-model Switch(config)# aaa group server radius group1 Switch(config-sg-radius)# server 172. use the no server ip-address server group configuration command. You can use the aaa authorization global configuration command with the radius keyword to set parameters that restrict a user’s network access to privileged EXEC mode. the switch uses information retrieved from the user’s profile. Use the local database if authentication was not performed by using RADIUS.1 auth-port 1000 acct-port 1001 Switch(config)# radius-server host 172. Note Authorization is bypassed for authenticated users who log in through the CLI even if authorization has been configured.1 auth-port 1000 acct-port 1001 Switch(config-sg-radius)# exit Switch(config)# aaa group server radius group2 Switch(config-sg-radius)# server 172. Release 15.20. The second host entry acts as a fail-over backup to the first entry. When AAA authorization is enabled.Chapter 9 Controlling Switch Access with RADIUS Configuring Switch-Based Authentication Command Step 8 Step 9 Purpose (Optional) Save your entries in the configuration file.

Beginning in privileged EXEC mode. or auditing. To disable authorization. configure terminal aaa accounting network start-stop radius aaa accounting exec start-stop radius end show running-config copy running-config startup-config To disable accounting. follow these steps to enable RADIUS accounting for each Cisco IOS privilege level and for network services: Command Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Purpose Enter global configuration mode.. use the no aaa authorization {network | exec} method1 global configuration command. the switch reports user activity to the RADIUS security server in the form of accounting records. Configure the switch for user RADIUS authorization for all network-related service requests. follow these steps to specify RADIUS authorization for privileged EXEC access and network services: Command Step 1 Step 2 Step 3 Purpose Enter global configuration mode.0(1)SE OL-26520-02 9-35 . Catalyst 2960 and 2960-S Switches Software Configuration Guide. client billing.. Return to privileged EXEC mode. configure terminal aaa authorization network radius aaa authorization exec radius Step 4 Step 5 Step 6 end show running-config copy running-config startup-config Return to privileged EXEC mode. Each accounting record contains accounting attribute-value (AV) pairs and is stored on the security server. Configure the switch for user RADIUS authorization if the user has privileged EXEC access. Enable RADIUS accounting for all network-related service requests. The exec keyword might return user profile information (such as autocommand information). Enable RADIUS accounting to send a start-record accounting notice at the beginning of a privileged EXEC process and a stop-record at the end. global configuration command. (Optional) Save your entries in the configuration file. When AAA accounting is enabled.Chapter 9 Configuring Switch-Based Authentication Controlling Switch Access with RADIUS Beginning in privileged EXEC mode. Release 15. use the no aaa accounting {network | exec} {start-stop} method1. Verify your entries. Verify your entries. (Optional) Save your entries in the configuration file. This data can then be analyzed for network management. Starting RADIUS Accounting The AAA accounting feature tracks the services that users are accessing and the amount of network resources that they are consuming.

If you use spaces in your key. which is not responding to authentication requests. which is the default condition. but spaces within and at the end of the key are used. The default is 0. follow these steps to configure global communication settings between the switch and all RADIUS servers: Command Step 1 Step 2 Purpose Enter global configuration mode. the range is 1 to 1440 minutes. In some situations. use the no forms of these commands. use the no aaa accounting system guarantee-first command. to be skipped. Verify your settings. Specify the number of seconds a switch waits for a reply to a RADIUS request before resending the request. Note configure terminal radius-server key string The key is a text string that must match the encryption key used on the RADIUS server. Return to privileged EXEC mode. Specify the shared secret text string used between the switch and all RADIUS servers. the range is 1 to 1000. The default is 5 seconds. To establish a console or Telnet session with the router if the AAA server is unreachable when the router reloads. Configuring Settings for All RADIUS Servers Beginning in privileged EXEC mode.Chapter 9 Controlling Switch Access with RADIUS Configuring Switch-Based Authentication Establishing a Session with a Router if the AAA Server is Unreachable Note To configure this command. Specify the number of minutes a RADIUS server. which can take more than 3 minutes. The aaa accounting system guarantee-first command guarantees system accounting as the first record. users might be prevented from starting a session on the console or terminal connection until after the system reloads. Vendor-specific attributes (VSAs) allow vendors to support their own extended Catalyst 2960 and 2960-S Switches Software Configuration Guide. the range 1 to 1000. Configuring the Switch to Use Vendor-Specific RADIUS Attributes The Internet Engineering Task Force (IETF) draft standard specifies a method for communicating vendor-specific information between the switch and the RADIUS server by using the vendor-specific attribute (attribute 26). Release 15. Leading spaces are ignored. do not enclose the key in quotation marks unless the quotation marks are part of the key. and deadtime.0(1)SE 9-36 OL-26520-02 . Step 5 radius-server deadtime minutes Step 6 Step 7 Step 8 end show running-config copy running-config startup-config To return to the default setting for the retransmit. timeout. The default is 3. thus avoiding the wait for the request to timeout before trying the next configured server. Step 3 Step 4 radius-server retransmit retries radius-server timeout seconds Specify the number of times the switch sends each RADIUS request to the server before giving up. (Optional) Save your entries in the configuration file. the switch must be running the LAN Base image.

Cisco’s vendor-ID is 9. Catalyst 2960 and 2960-S Switches Software Configuration Guide. The full set of features available for TACACS+ authorization can then be used for RADIUS. The Cisco RADIUS implementation supports one vendor-specific option by using the format recommended in the specification.10. and sep is = for mandatory attributes and is * for optional attributes. Enable the switch to recognize and use VSAs as defined by RADIUS IETF attribute 26. options.255 20.255 any” Other vendors have their own unique vendor-IDs.255. see RFC 2138.10. Release 15. and associated VSAs.0. “Remote Authentication Dial-In User Service (RADIUS).0.10.10.10. this AV pair activates Cisco’s multiple named ip address pools feature during IP authorization (during PPP IPCP address assignment): cisco-avpair= ”ip:addr-pool=first“ This example shows how to provide a user logging in from a switch with immediate access to privileged EXEC commands: cisco-avpair= ”shell:priv-lvl=15“ This example shows how to specify an authorized VLAN in the RADIUS server database: cisco-avpair= ”tunnel-type(#64)=VLAN(13)” cisco-avpair= ”tunnel-medium-type(#65)=802 media(6)” cisco-avpair= ”tunnel-private-group-id(#81)=vlanid” This example shows how to apply an input ACL in ASCII format to an interface for the duration of this connection: cisco-avpair= “ip:inacl#1=deny ip 10.255 any” cisco-avpair= “mac:inacl#3=deny any any decnet-iv” This example shows how to apply an output ACL in ASCII format to an interface for the duration of this connection: cisco-avpair= “ip:outacl#2=deny ip 10. which is named cisco-avpair. For example.0.20. (Optional) Use the authentication keyword to limit the set of recognized vendor-specific attributes to only authentication attributes.10 0. • • configure terminal radius-server vsa send [accounting | authentication] (Optional) Use the accounting keyword to limit the set of recognized vendor-specific attributes to only accounting attributes.255.10. follow these steps to configure the switch to recognize and use VSAs: Command Step 1 Step 2 Purpose Enter global configuration mode.255.10 0. Attribute and value are an appropriate attribute-value (AV) pair defined in the Cisco TACACS+ specification. If you enter this command without keywords. The value is a string with this format: protocol : attribute sep value * Protocol is a value of the Cisco protocol attribute for a particular type of authorization.0(1)SE OL-26520-02 9-37 . and the supported option has vendor-type 1.20.0.0” cisco-avpair= “ip:inacl#2=deny ip 10. Step 3 end Return to privileged EXEC mode.255.10 0. For more information about vendor-IDs and VSAs.” Beginning in privileged EXEC mode.Chapter 9 Configuring Switch-Based Authentication Controlling Switch Access with RADIUS attributes not suitable for general use.20 255. both accounting and authentication vendor-specific attributes are used.

follow these steps to specify a vendor-proprietary RADIUS server host and a shared secret text string: Command Step 1 Step 2 Purpose Enter global configuration mode.0(1)SE 9-38 OL-26520-02 . You specify the RADIUS host and secret text string by using the radius-server global configuration commands. To disable the key. to configure RADIUS (whether vendor-proprietary or IETF draft-compliant). you must specify the host running the RADIUS server daemon and the secret text string it shares with the switch.com. Verify your settings. Specify the shared secret text string used between the switch and the vendor-proprietary RADIUS server. show running-config copy running-config startup-config Note For a complete list of RADIUS attributes or more information about vendor-specific attribute 26. Step 4 Step 5 Step 6 end show running-config copy running-config startup-config Return to privileged EXEC mode. but spaces within and at the end of the key are used. Beginning in privileged EXEC mode. If you use spaces in your key. do not enclose the key in quotation marks unless the quotation marks are part of the key. As mentioned earlier. Cisco IOS software supports a subset of vendor-proprietary RADIUS attributes. Release 15. (Optional) Save your entries in the configuration file. Leading spaces are ignored. (Optional) Save your entries in the configuration file. Configuring the Switch for Vendor-Proprietary RADIUS Server Communication Although an IETF draft standard for RADIUS specifies a method for communicating vendor-proprietary information between the switch and the RADIUS server. Catalyst 2960 and 2960-S Switches Software Configuration Guide. see the “RADIUS Attributes” appendix in the Cisco IOS Security Configuration Guide. Note configure terminal radius-server host {hostname | ip-address} non-standard Step 3 radius-server key string The key is a text string that must match the encryption key used on the RADIUS server.Chapter 9 Controlling Switch Access with RADIUS Configuring Switch-Based Authentication Command Step 4 Step 5 Purpose Verify your settings. Specify the IP address or hostname of the remote RADIUS server host and identify that it is using a vendor-proprietary implementation of RADIUS.4. use the no radius-server host {hostname | ip-address} non-standard global configuration command. use the no radius-server key global configuration command. Release 12. The switch and the RADIUS server use this text string to encrypt passwords and exchange responses. To delete the vendor-proprietary RADIUS host. on Cisco. some vendors have extended the RADIUS attribute set in a unique way.

Verify your entries. see the Cisco IOS Intelligent Services Gateway Command Reference on Cisco.Chapter 9 Configuring Switch-Based Authentication Controlling Switch Access with RADIUS This example shows how to specify a vendor-proprietary RADIUS host and to use a secret key of rad124 between the switch and the server: Switch(config)# radius-server host 172.15 nonstandard Switch(config)# radius-server key rad124 Configuring CoA on the Switch Beginning in privileged EXEC mode. For more information about the ignore command. end show running-config copy running-config startup-config Return to privileged EXEC mode. server-key [0 | 7] string port port-number auth-type {any | all | session-key} ignore session-key Configure the RADIUS key to be shared between a device and RADIUS clients. The client must match all the configured attributes for authorization. Step 10 authentication command bounce-port (Optional) Configure the switch to ignore a CoA request to temporarily ignore disable the port hosting a session. (Optional) Configure the switch to ignore the session-key. For more information about the ignore command.20. The purpose of temporarily disabling the port is to trigger a DHCP renegotiation from the host when a VLAN change occurs and there is no supplicant on the endpoint to detect the change. (Optional) Save your entries in the configuration file. Use standard CLI or SNMP commands to re-enable the port. Release 15. Step 5 Step 6 Step 7 Step 8 Step 9 ignore server-key (Optional) Configure the switch to ignore the server-key. Enable AAA. Shutting down the port results in termination of the session.30.0(1)SE OL-26520-02 9-39 . Configure the switch as an authentication. Specify the port on which a device listens for RADIUS requests from configured RADIUS clients.com. authorization. Command Step 1 Step 2 Step 3 Step 4 Purpose Enter global configuration mode. Step 11 Step 12 Step 13 Step 14 Catalyst 2960 and 2960-S Switches Software Configuration Guide. Specify the type of authorization the switch uses for RADIUS clients. follow these steps to configure CoA on a switch. and accounting (AAA) server to facilitate interaction with an external policy server. This procedure is required. see the Cisco IOS Intelligent Services Gateway Command Reference on Cisco. configure terminal aaa new-model aaa server radius dynamic-author client {ip-address | name} [vrf vrfname] Enter dynamic authorization local server configuration mode and specify [server-key string] a RADIUS client from which a device will accept CoA and disconnect requests. authentication command disable-port (Optional) Configure the switch to ignore a nonstandard command ignore requesting that the port hosting a session be administratively shut down.com.

For more information. No accounting is available in this configuration. use the no aaa new-model global configuration command. The default keyword applies the local user database authentication to all ports. check the local database. use the no aaa server radius dynamic authorization global configuration command. To disable the AAA server functionality on the switch. Release 15. Configure user AAA authorization. Monitoring and Troubleshooting CoA Functionality Use these Cisco IOS commands to monitor and troubleshoot CoA functionality on the switch: • • • • • • debug radius debug aaa coa debug aaa pod debug aaa subsys debug cmdhd [detail | error | events] show aaa attributes protocol radius Configuring RADIUS Server Load Balancing This feature allows access and authentication requests to be evenly across all RADIUS servers in a server group. Configuring the Switch for Local Authentication and Authorization You can configure AAA to operate without a server by setting the switch to implement AAA in local mode.Chapter 9 Configuring the Switch for Local Authentication and Authorization Configuring Switch-Based Authentication To disable AAA. The switch then handles authentication and authorization. follow these steps to configure the switch for local AAA: Command Step 1 Step 2 Step 3 Step 4 Step 5 Purpose Enter global configuration mode. Configure user AAA authorization for all network-related service requests.html Displaying the RADIUS Configuration To display the RADIUS configuration. Enable AAA.com/en/US/docs/ios/12_2sb/feature/guide/sbrdldbl.0(1)SE 9-40 OL-26520-02 . configure terminal aaa new-model aaa authentication login default local aaa authorization exec local aaa authorization network local Catalyst 2960 and 2960-S Switches Software Configuration Guide. and allow the user to run an EXEC shell. see the “RADIUS Server Load Balancing” chapter of the Cisco IOS Security Configuration Guide: http://www. Beginning in privileged EXEC mode. Set the login authentication to use the local username database. use the show running-config privileged EXEC command.ciscosystems.

Chapter 9 Configuring Switch-Based Authentication Configuring the Switch for Secure Shell Command Step 6 Purpose Enter the local database. For more information. see the “SSH Configuration Examples” section in the “Configuring Secure Shell” chapter of the Cisco IOS Security Configuration Guide: http://www. Enter 7 to specify that a hidden password follows. (Optional) For level. Configuring AAA authentication does not secure the switch for HTTP access by using AAA methods. copy running-config startup-config (Optional) Save your entries in the configuration file. specify the privilege level the user has after gaining access. For more information about the ip http authentication command. SSH supports IPv6 addresses and enables secure. page 9-43 Displaying the SSH Configuration and Status. you must configure the switch with the ip http authentication aaa global configuration command.0(1)SE OL-26520-02 9-41 . specify the password the user must enter to gain access to the switch. Configuring the Switch for Secure Shell This section describes how to configure the Secure Shell (SSH) feature.com. • • Step 7 Step 8 Step 9 end show running-config Return to privileged EXEC mode. Release 15. Note To secure the switch for HTTP access by using AAA methods. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Release 12. use the no aaa authorization {network | exec} method1 global configuration command. Level 0 gives user EXEC mode access. Spaces and quotation marks are not allowed.html SSH functions the same in IPv6 as in IPv4.com/en/US/docs/ios/12_2/security/configuration/guide/scfssh. can contain embedded spaces. For IPv6. • • • Understanding SSH. The password must be from 1 to 25 characters. For password. you must install the cryptographic (encrypted) software image on your switch. page 9-42 Configuring SSH. To use this feature. see the release notes for this release. see the Cisco IOS Security Command Reference. and must be the last option specified in the username command. enter 0 to specify that an unencrypted password follows.cisco. For encryption-type. Level 15 gives privileged EXEC mode access. encrypted connections with remote IPv6 nodes over an IPv6 transport. To disable AAA. Repeat this command for each user. specify the user ID as one word.4. page 9-45 For SSH configuration examples. use the no aaa new-model global configuration command. To disable authorization. Verify your entries. • • username name [privilege level] {password encryption-type password} For name. You must obtain authorization to use this feature and to download the cryptographic software files from Cisco. and establish a username-based authentication system. The range is 0 to 15.

cisco. The SSH server and the SSH client are supported only on DES (56-bit) and 3DES (168-bit) data encryption software. The SSH client also works with the SSH server supported in this release and with non-Cisco SSH servers.2: http://www. The SSH server works with the SSH client supported in this release and with non-Cisco SSH clients. Integrated Clients. see the “Configuring the Switch for Local Authentication and Authorization” section on page 9-40) Note The switch does not support IP Security (IPSec). and Supported Versions The SSH feature has an SSH server and an SSH integrated client.html and the Cisco IOS IPv6 Command Reference. SSH supports only the execution-shell application. and Adelman (RSA) authentication. This software release supports SSH Version 1 (SSHv1) and SSH Version 2 (SSHv2). Shamir. SSH supports the Data Encryption Standard (DES) encryption algorithm. The switch supports an SSHv1 client. Understanding SSH SSH is a protocol that provides a secure.Chapter 9 Configuring the Switch for Secure Shell Configuring Switch-Based Authentication Note For complete syntax and usage information for the commands used in this section. You can use an SSH client to connect to a switch running the SSH server. SSH also supports these user authentication methods: • • • TACACS+ (for more information. see the “Controlling Switch Access with RADIUS” section on page 9-18) Local authentication and authorization (for more information. SSH provides more security for remote connections than Telnet does by providing strong encryption when a device is authenticated.0(1)SE 9-42 OL-26520-02 . • • SSH Servers. see the command reference for this release and the command reference for Cisco IOS Release 12. page 9-42 Limitations. The switch supports an SSHv1 or an SSHv2 server. and password-based user authentication. see the “Controlling Switch Access with TACACS+” section on page 9-10) RADIUS (for more information. page 9-42 SSH Servers. which are applications that run on the switch. Integrated Clients. Release 15. and Supported Versions. Catalyst 2960 and 2960-S Switches Software Configuration Guide. the Triple DES (3DES) encryption algorithm. Limitations These limitations apply to SSH: • • • The switch supports Rivest.com/en/US/docs/ios/12_2/security/command/reference/fsecur_r. remote connection to a device.

symmetric cipher AES to encrypt the keys is not supported. If it does. For more information. the message No domain specified might appear. If the SSH server is running on a stack master and the stack master fails. When generating the RSA key pair. page 9-43 (required) Configuring the SSH Server. 2. Follow this procedure only if you are configuring the switch as an SSH server. an RSA key pair has not been generated. the new stack master uses the RSA key pair generated by the previous stack master. If it does. you must configure an IP domain name by using the ip domain-name global configuration command. or 256-bit key. Download the cryptographic software image from Cisco. For more information. Release 15. and the reverse. the message No host name specified might appear. If you get CLI error messages after entering the crypto key generate rsa global configuration command. page 9-44 (required only if you are configuring the switch as an SSH server) Configuration Guidelines Follow these guidelines when configuring the switch as an SSH server or SSH client: • • • An RSA key pair generated by a SSHv1 server can be used by an SSHv2 server. When generating the RSA key pair. When configuring the local authentication and authorization authentication method. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Configure a hostname and IP domain name for the switch. see the release notes for this release. you must configure a hostname by using the hostname global configuration command.Chapter 9 Configuring Switch-Based Authentication Configuring the Switch for Secure Shell • The switch supports the Advanced Encryption Standard (AES) encryption algorithm with a 128-bit key. and then enter the crypto key generate rsa command. see the “Setting Up the Switch to Run SSH” section on page 9-43. However. Reconfigure the hostname and domain. page 9-43 Setting Up the Switch to Run SSH. This step is required.0(1)SE OL-26520-02 9-43 . Configuring SSH This section has this configuration information: • • • Configuration Guidelines. 192-bit key. make sure that AAA is disabled on the console. • • • Setting Up the Switch to Run SSH Follow these steps to set up your switch to run SSH: 1.com.

Release 15. (Optional) Save your entries in the configuration file. if the SSH client supports SSHv1 and SSHv2. After the RSA key pair is deleted. 2—Configure the switch to run SSH Version 2. • • configure terminal ip ssh version [1 | 2] 1—Configure the switch to run SSH Version 1. Configure user authentication for local or remote access. Configure a host domain for your switch. 4. A longer modulus length might be more secure. the SSH server selects the latest SSH version supported by the SSH client. configure terminal hostname hostname ip domain-name domain_name crypto key generate rsa Step 5 Step 6 end show ip ssh or show ssh Return to privileged EXEC mode. We recommend that a minimum modulus size of 1024 bits. the SSH server selects SSHv2. Follow this procedure only if you are configuring the switch as an SSH server. Beginning in privileged EXEC mode. Enable the SSH server for local and remote authentication on the switch and generate an RSA key pair. follow these steps to configure a hostname and an IP domain name and to generate an RSA key pair. For more information. which automatically enables SSH. see the “Configuring the Switch for Local Authentication and Authorization” section on page 9-40. This step is required. This procedure is required if you are configuring the switch as an SSH server.Chapter 9 Configuring the Switch for Secure Shell Configuring Switch-Based Authentication 3. Show the status of the SSH server on the switch. Configure a hostname for your switch. Catalyst 2960 and 2960-S Switches Software Configuration Guide. you are prompted to enter a modulus length.0(1)SE 9-44 OL-26520-02 . Command Step 1 Step 2 Step 3 Step 4 Purpose Enter global configuration mode. the SSH server is automatically disabled. follow these steps to configure the SSH server: Command Step 1 Step 2 Purpose Enter global configuration mode. use the crypto key zeroize rsa global configuration command. Configuring the SSH Server Beginning in privileged EXEC mode. Show the version and configuration information for your SSH server. but it takes longer to generate and to use. If you do not enter this command or do not specify a keyword. When you generate RSA keys. For example. Step 7 copy running-config startup-config To delete the RSA key pair. Generate an RSA key pair for the switch. (Optional) Configure the switch to run SSH Version 1 or SSH Version 2.

Chapter 9

Configuring Switch-Based Authentication Configuring the Switch for Secure Shell

Command
Step 3

Purpose Configure the SSH control parameters:

ip ssh {timeout seconds | authentication-retries number}

Specify the time-out value in seconds; the default is 120 seconds. The range is 0 to 120 seconds. This parameter applies to the SSH negotiation phase. After the connection is established, the switch uses the default time-out values of the CLI-based sessions. By default, up to five simultaneous, encrypted SSH connections for multiple CLI-based sessions over the network are available (session 0 to session 4). After the execution shell starts, the CLI-based session time-out value returns to the default of 10 minutes.

Specify the number of times that a client can re-authenticate to the server. The default is 3; the range is 0 to 5.

Repeat this step when configuring both parameters.
Step 4

line vty line_number [ending_line_number] transport input ssh

(Optional) Configure the virtual terminal line settings.

Enter line configuration mode to configure the virtual terminal line settings. For line_number and ending_line_number, specify a pair of lines. The range is 0 to 15. Specify that the switch prevent non-SSH Telnet connections. This limits the router to only SSH connections.

• Step 5 Step 6

end show ip ssh or show ssh

Return to privileged EXEC mode. Show the version and configuration information for your SSH server. Show the status of the SSH server connections on the switch. (Optional) Save your entries in the configuration file.

Step 7

copy running-config startup-config

To return to the default SSH control parameters, use the no ip ssh {timeout | authentication-retries} global configuration command.

Displaying the SSH Configuration and Status
To display the SSH server configuration and status, use one or more of the privileged EXEC commands in Table 9-5:
Table 9-5 Commands for Displaying the SSH Server Configuration and Status

Command show ip ssh show ssh

Purpose Shows the version and configuration information for the SSH server. Shows the status of the SSH server.

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE OL-26520-02

9-45

Chapter 9 Configuring the Switch for Secure Socket Layer HTTP

Configuring Switch-Based Authentication

For more information about these commands, see the “Secure Shell Commands” section in the “Other Security Features” chapter of the Cisco IOS Security Command Reference: http://www.cisco.com/en/US/docs/ios/12_2/security/configuration/guide/scfpass.html

Configuring the Switch for Secure Socket Layer HTTP
This section describes how to configure Secure Socket Layer (SSL) version 3.0 support for the HTTP 1.1 server and client. SSL provides server authentication, encryption, and message integrity, as well as HTTP client authentication, to allow secure HTTP communications.To use this feature, the cryptographic (encrypted) software image must be installed on your switch. You must obtain authorization to use this feature and to download the cryptographic software files from Cisco.com. For more information about the crypto image, see the release notes for this release. These sections contain this information:
• • •

Understanding Secure HTTP Servers and Clients, page 9-46 Configuring Secure HTTP Servers and Clients, page 9-48 Displaying Secure HTTP Server and Client Status, page 9-52

For configuration examples and complete syntax and usage information for the commands used in this section, see the “HTTPS - HTTP Server and Client with SSL 3.0” feature description for Cisco IOS Release 12.2(15)T: http://www.cisco.com/en/US/docs/ios/netmgmt/configuration/guide/nm_https_sc_ssl3.html

Understanding Secure HTTP Servers and Clients
On a secure HTTP connection, data to and from an HTTP server is encrypted before being sent over the Internet. HTTP with SSL encryption provides a secure connection to allow such functions as configuring a switch from a Web browser. Cisco's implementation of the secure HTTP server and secure HTTP client uses an implementation of SSL Version 3.0 with application-layer encryption. HTTP over SSL is abbreviated as HTTPS; the URL of a secure connection begins with https:// instead of http://. The primary role of the HTTP secure server (the switch) is to listen for HTTPS requests on a designated port (the default HTTPS port is 443) and pass the request to the HTTP 1.1 Web server. The HTTP 1.1 server processes requests and passes responses (pages) back to the HTTP secure server, which, in turn, responds to the original request. The primary role of the HTTP secure client (the web browser) is to respond to Cisco IOS application requests for HTTPS User Agent services, perform HTTPS User Agent services for the application, and pass the response back to the application.

Certificate Authority Trustpoints
Certificate authorities (CAs) manage certificate requests and issue certificates to participating network devices. These services provide centralized security key and certificate management for the participating devices. Specific CA servers are referred to as trustpoints. When a connection attempt is made, the HTTPS server provides a secure connection by issuing a certified X.509v3 certificate, obtained from a specified CA trustpoint, to the client. The client (usually a Web browser), in turn, has a public key that allows it to authenticate the certificate.

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE

9-46

OL-26520-02

Chapter 9

Configuring Switch-Based Authentication Configuring the Switch for Secure Socket Layer HTTP

For secure HTTP connections, we highly recommend that you configure a CA trustpoint. If a CA trustpoint is not configured for the device running the HTTPS server, the server certifies itself and generates the needed RSA key pair. Because a self-certified (self-signed) certificate does not provide adequate security, the connecting client generates a notification that the certificate is self-certified, and the user has the opportunity to accept or reject the connection. This option is useful for internal network topologies (such as testing). If you do not configure a CA trustpoint, when you enable a secure HTTP connection, either a temporary or a persistent self-signed certificate for the secure HTTP server (or client) is automatically generated.

If the switch is not configured with a hostname and a domain name, a temporary self-signed certificate is generated. If the switch reboots, any temporary self-signed certificate is lost, and a new temporary new self-signed certificate is assigned. If the switch has been configured with a host and domain name, a persistent self-signed certificate is generated. This certificate remains active if you reboot the switch or if you disable the secure HTTP server so that it will be there the next time you re-enable a secure HTTP connection.

Note

The certificate authorities and trustpoints must be configured on each device individually. Copying them from other devices makes them invalid on the switch. If a self-signed certificate has been generated, this information is included in the output of the show running-config privileged EXEC command. This is a partial sample output from that command displaying a self-signed certificate.
Switch# show running-config Building configuration... <output truncated> crypto pki trustpoint TP-self-signed-3080755072 enrollment selfsigned subject-name cn=IOS-Self-Signed-Certificate-3080755072 revocation-check none rsakeypair TP-self-signed-3080755072 ! ! crypto ca certificate chain TP-self-signed-3080755072 certificate self-signed 01 3082029F 30820208 A0030201 02020101 300D0609 2A864886 F70D0101 04050030 59312F30 2D060355 04031326 494F532D 53656C66 2D536967 6E65642D 43657274 69666963 6174652D 33303830 37353530 37323126 30240609 2A864886 F70D0109 <output truncated>

You can remove this self-signed certificate by disabling the secure HTTP server and entering the no crypto pki trustpoint TP-self-signed-30890755072 global configuration command. If you later re-enable a secure HTTP server, a new self-signed certificate is generated.

Note

The values that follow TP self-signed depend on the serial number of the device. You can use an optional command (ip http secure-client-auth) to allow the HTTPS server to request an X.509v3 certificate from the client. Authenticating the client provides more security than server authentication by itself. For additional information on Certificate Authorities, see the “Configuring Certification Authority Interoperability” chapter in the Cisco IOS Security Configuration Guide, Release 124 on Cisco.com.

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE OL-26520-02

9-47

Chapter 9 Configuring the Switch for Secure Socket Layer HTTP

Configuring Switch-Based Authentication

CipherSuites
A CipherSuite specifies the encryption algorithm and the digest algorithm to use on a SSL connection. When connecting to the HTTPS server, the client Web browser offers a list of supported CipherSuites, and the client and server negotiate the best encryption algorithm to use from those on the list that are supported by both. For example, Netscape Communicator 4.76 supports U.S. security with RSA Public Key Cryptography, MD2, MD5, RC2-CBC, RC4, DES-CBC, and DES-EDE3-CBC. For the best possible encryption, you should use a client browser that supports 128-bit encryption, such as Microsoft Internet Explorer Version 5.5 (or later) or Netscape Communicator Version 4.76 (or later). The SSL_RSA_WITH_DES_CBC_SHA CipherSuite provides less security than the other CipherSuites, as it does not offer 128-bit encryption. The more secure and more complex CipherSuites require slightly more processing time. This list defines the CipherSuites supported by the switch and ranks them from fastest to slowest in terms of router processing load (speed):
1. 2. 3. 4.

SSL_RSA_WITH_DES_CBC_SHA—RSA key exchange (RSA Public Key Cryptography) with DES-CBC for message encryption and SHA for message digest SSL_RSA_WITH_RC4_128_MD5—RSA key exchange with RC4 128-bit encryption and MD5 for message digest SSL_RSA_WITH_RC4_128_SHA—RSA key exchange with RC4 128-bit encryption and SHA for message digest SSL_RSA_WITH_3DES_EDE_CBC_SHA—RSA key exchange with 3DES and DES-EDE3-CBC for message encryption and SHA for message digest

RSA (in conjunction with the specified encryption and digest algorithm combinations) is used for both key generation and authentication on SSL connections. This usage is independent of whether or not a CA trustpoint is configured.

Configuring Secure HTTP Servers and Clients
• • • • •

Default SSL Configuration, page 9-48 SSL Configuration Guidelines, page 9-49 Configuring a CA Trustpoint, page 9-49 Configuring the Secure HTTP Server, page 9-50 Configuring the Secure HTTP Client, page 9-51

Default SSL Configuration
The standard HTTP server is enabled. SSL is enabled. No CA trustpoints are configured. No self-signed certificates are generated.

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE

9-48

OL-26520-02

Chapter 9

Configuring Switch-Based Authentication Configuring the Switch for Secure Socket Layer HTTP

SSL Configuration Guidelines
When SSL is used in a switch cluster, the SSL session terminates at the cluster commander. Cluster member switches must run standard HTTP. Before you configure a CA trustpoint, you should ensure that the system clock is set. If the clock is not set, the certificate is rejected due to an incorrect date. In a switch stack, the SSL session terminates at the stack master.

Configuring a CA Trustpoint
For secure HTTP connections, we recommend that you configure an official CA trustpoint. A CA trustpoint is more secure than a self-signed certificate. Beginning in privileged EXEC mode, follow these steps to configure a CA trustpoint: Command
Step 1 Step 2

Purpose Enter global configuration mode. Specify the hostname of the switch (required only if you have not previously configured a hostname). The hostname is required for security keys and certificates. Specify the IP domain name of the switch (required only if you have not previously configured an IP domain name). The domain name is required for security keys and certificates. (Optional) Generate an RSA key pair. RSA key pairs are required before you can obtain a certificate for the switch. RSA key pairs are generated automatically. You can use this command to regenerate the keys, if needed. Specify a local configuration name for the CA trustpoint and enter CA trustpoint configuration mode. Specify the URL to which the switch should send certificate requests. (Optional) Configure the switch to obtain certificates from the CA through an HTTP proxy server. Configure the switch to request a certificate revocation list (CRL) to ensure that the certificate of the peer has not been revoked. (Optional) Specify that the trustpoint should be used as the primary (default) trustpoint for CA requests. Exit CA trustpoint configuration mode and return to global configuration mode. Authenticate the CA by getting the public key of the CA. Use the same name used in Step 5. Obtain the certificate from the specified CA trustpoint. This command requests a signed certificate for each RSA key pair. Return to privileged EXEC mode. Verify the configuration. (Optional) Save your entries in the configuration file.

configure terminal hostname hostname

Step 3

ip domain-name domain-name

Step 4

crypto key generate rsa

Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Step 11 Step 12 Step 13 Step 14 Step 15

crypto ca trustpoint name enrollment url url enrollment http-proxy host-name port-number crl query url primary exit crypto ca authentication name crypto ca enroll name end show crypto ca trustpoints copy running-config startup-config

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE OL-26520-02

9-49

Chapter 9 Configuring the Switch for Secure Socket Layer HTTP

Configuring Switch-Based Authentication

Use the no crypto ca trustpoint name global configuration command to delete all identity information and certificates associated with the CA.

Configuring the Secure HTTP Server
If you are using a certificate authority for certification, you should use the previous procedure to configure the CA trustpoint on the switch before enabling the HTTP server. If you have not configured a CA trustpoint, a self-signed certificate is generated the first time that you enable the secure HTTP server. After you have configured the server, you can configure options (path, access list to apply, maximum number of connections, or timeout policy) that apply to both standard and secure HTTP servers. Beginning in privileged EXEC mode, follow these steps to configure a secure HTTP server: Command
Step 1

Purpose (Optional) Display the status of the HTTP server to determine if the secure HTTP server feature is supported in the software. You should see one of these lines in the output:
HTTP secure server capability: Present or HTTP secure server capability: Not present

show ip http server status

Step 2 Step 3 Step 4

configure terminal ip http secure-server ip http secure-port port-number

Enter global configuration mode. Enable the HTTPS server if it has been disabled. The HTTPS server is enabled by default. (Optional) Specify the port number to be used for the HTTPS server. The default port number is 443. Valid options are 443 or any number in the range 1025 to 65535. (Optional) Specify the CipherSuites (encryption algorithms) to be used for encryption over the HTTPS connection. If you do not have a reason to specify a particularly CipherSuite, you should allow the server and client to negotiate a CipherSuite that they both support. This is the default. (Optional) Configure the HTTP server to request an X.509v3 certificate from the client for authentication during the connection process. The default is for the client to request a certificate from the server, but the server does not attempt to authenticate the client. Specify the CA trustpoint to use to get an X.509v3 security certificate and to authenticate the client certificate connection.
Note

Step 5

ip http secure-ciphersuite {[3des-ede-cbc-sha] [rc4-128-md5] [rc4-128-sha] [des-cbc-sha]} ip http secure-client-auth

Step 6

Step 7

ip http secure-trustpoint name

Use of this command assumes you have already configured a CA trustpoint according to the previous procedure.

Step 8

ip http path path-name

(Optional) Set a base HTTP path for HTML files. The path specifies the location of the HTTP server files on the local system (usually located in system flash memory). (Optional) Specify an access list to use to allow access to the HTTP server. (Optional) Set the maximum number of concurrent connections that are allowed to the HTTP server. The range is 1 to 16; the default value is 5.

Step 9 Step 10

ip http access-class access-list-number ip http max-connections value

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE

9-50

OL-26520-02

Chapter 9

Configuring Switch-Based Authentication Configuring the Switch for Secure Socket Layer HTTP

Command
Step 11

Purpose

ip http timeout-policy idle seconds life (Optional) Specify how long a connection to the HTTP server can remain seconds requests value open under the defined circumstances:

idle—the maximum time period when no data is received or response data cannot be sent. The range is 1 to 600 seconds. The default is 180 seconds (3 minutes). life—the maximum time period from the time that the connection is established. The range is 1 to 86400 seconds (24 hours). The default is 180 seconds. requests—the maximum number of requests processed on a persistent connection. The maximum value is 86400. The default is 1.

• Step 12 Step 13 Step 14

end show ip http server secure status copy running-config startup-config

Return to privileged EXEC mode. Display the status of the HTTP secure server to verify the configuration. (Optional) Save your entries in the configuration file.

Use the no ip http server global configuration command to disable the standard HTTP server. Use the no ip http secure-server global configuration command to disable the secure HTTP server. Use the no ip http secure-port and the no ip http secure-ciphersuite global configuration commands to return to the default settings. Use the no ip http secure-client-auth global configuration command to remove the requirement for client authentication. To verify the secure HTTP connection by using a Web browser, enter https://URL, where the URL is the IP address or hostname of the server switch. If you configure a port other than the default port, you must also specify the port number after the URL. For example:
https://209.165.129:1026

or
https://host.domain.com:1026

Configuring the Secure HTTP Client
The standard HTTP client and secure HTTP client are always enabled. A certificate authority is required for secure HTTP client certification. This procedure assumes that you have previously configured a CA trustpoint on the switch. If a CA trustpoint is not configured and the remote HTTPS server requires client authentication, connections to the secure HTTP client fail. Beginning in privileged EXEC mode, follow these steps to configure a secure HTTP client: Command
Step 1 Step 2

Purpose Enter global configuration mode. (Optional) Specify the CA trustpoint to be used if the remote HTTP server requests client authentication. Using this command assumes that you have already configured a CA trustpoint by using the previous procedure. The command is optional if client authentication is not needed or if a primary trustpoint has been configured. (Optional) Specify the CipherSuites (encryption algorithms) to be used for encryption over the HTTPS connection. If you do not have a reason to specify a particular CipherSuite, you should allow the server and client to negotiate a CipherSuite that they both support. This is the default.

configure terminal ip http client secure-trustpoint name

Step 3

ip http client secure-ciphersuite {[3des-ede-cbc-sha] [rc4-128-md5] [rc4-128-sha] [des-cbc-sha]}

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE OL-26520-02

9-51

Chapter 9 Configuring the Switch for Secure Copy Protocol

Configuring Switch-Based Authentication

Command
Step 4 Step 5 Step 6

Purpose Return to privileged EXEC mode. Display the status of the HTTP secure server to verify the configuration. (Optional) Save your entries in the configuration file.

end show ip http client secure status copy running-config startup-config

Use the no ip http client secure-trustpoint name to remove a client trustpoint configuration. Use the no ip http client secure-ciphersuite to remove a previously configured CipherSuite specification for the client.

Displaying Secure HTTP Server and Client Status
To display the SSL secure server and client status, use the privileged EXEC commands in Table 9-6:
Table 9-6 Commands for Displaying the SSL Secure Server and Client Status

Command show ip http client secure status show ip http server secure status show running-config

Purpose Shows the HTTP secure client configuration. Shows the HTTP secure server configuration. Shows the generated self-signed certificate for secure HTTP connections.

Configuring the Switch for Secure Copy Protocol
The Secure Copy Protocol (SCP) feature provides a secure and authenticated method for copying switch configurations or switch image files. SCP relies on Secure Shell (SSH), an application and a protocol that provides a secure replacement for the Berkeley r-tools. For SSH to work, the switch needs an RSA public/private key pair. This is the same with SCP, which relies on SSH for its secure transport. Because SSH also relies on AAA authentication, and SCP relies further on AAA authorization, correct configuration is necessary.
• •

Before enabling SCP, you must correctly configure SSH, authentication, and authorization on the switch. Because SCP relies on SSH for its secure transport, the router must have an Rivest, Shamir, and Adelman (RSA) key pair.

Note

When using SCP, you cannot enter the password into the copy command. You must enter the password when prompted.

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE

9-52

OL-26520-02

Chapter 9

Configuring Switch-Based Authentication Configuring the Switch for Secure Copy Protocol

Information About Secure Copy
To configure the Secure Copy feature, you should understand these concepts. The behavior of SCP is similar to that of remote copy (rcp), which comes from the Berkeley r-tools suite, except that SCP relies on SSH for security. SCP also requires that authentication, authorization, and accounting (AAA) authorization be configured so the router can determine whether the user has the correct privilege level. A user who has appropriate authorization can use SCP to copy any file in the Cisco IOS File System (IFS) to and from a switch by using the copy command. An authorized administrator can also do this from a workstation. For information about how to configure and verify SCP, see the “Secure Copy Protocol” section in the Cisco IOS Security Configuration Guide: Securing User Services, Release 12.4: http://www.cisco.com/en/US/docs/ios/sec_user_services/configuration/guide/sec_secure_copy_ps6350 _TSD_Products_Configuration_Guide_Chapter.html

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE OL-26520-02

9-53

Chapter 9 Configuring the Switch for Secure Copy Protocol

Configuring Switch-Based Authentication

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE

9-54

OL-26520-02

CH A P T E R

10

Configuring IEEE 802.1x Port-Based Authentication
IEEE 802.1x port-based authentication prevents unauthorized devices (clients) from gaining access to the network. Unless otherwise noted, the term switch refers to a standalone switch and to a switch stack.

Note

Stacking is supported only on Catalyst 2960-S switches running the LAN base image. The Catalyst 2960, 2960-S, and 2960-C switch command reference and the “RADIUS Commands” section in the Cisco IOS Security Command Reference, Release 12.4, have command syntax and usage information. This chapter includes these sections:
• • •

Understanding IEEE 802.1x Port-Based Authentication, page 10-1 Configuring 802.1x Authentication, page 10-35 Displaying 802.1x Statistics and Status, page 10-68

Understanding IEEE 802.1x Port-Based Authentication
The standard defines a client-server-based access control and authentication protocol to prevent unauthorized clients from connecting to a LAN through publicly accessible ports.The authentication server authenticates each client connected to a switch port before making available any switch or LAN services. Until the client is authenticated, IEEE 802.1x access control allows only Extensible Authentication Protocol over LAN (EAPOL), Cisco Discovery Protocol (CDP), and Spanning Tree Protocol (STP) traffic through the port to which the client is connected. After authentication, normal traffic passes through the port.
• • • • • •

Device Roles, page 10-3 Authentication Process, page 10-4 Authentication Initiation and Message Exchange, page 10-5 Authentication Manager, page 10-7 Ports in Authorized and Unauthorized States, page 10-10 802.1x Authentication and Switch Stacks, page 10-11

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE OL-26520-02

10-1

Chapter 10 Understanding IEEE 802.1x Port-Based Authentication

Configuring IEEE 802.1x Port-Based Authentication

• • • • • • • • • • • • •

802.1x Host Mode, page 10-12 Multidomain Authentication, page 10-13 802.1x Multiple Authentication Mode, page 10-14 MAC Move, page 10-15 MAC Replace, page 10-15 802.1x Accounting, page 10-16 802.1x Accounting Attribute-Value Pairs, page 10-16 802.1x Readiness Check, page 10-17 802.1x Authentication with VLAN Assignment, page 10-18 Using 802.1x Authentication with Per-User ACLs, page 10-19 802.1x Authentication with Guest VLAN, page 10-23 802.1x Authentication with Restricted VLAN, page 10-24 802.1x Authentication with Inaccessible Authentication Bypass, page 10-25

Note

To use 802.1x authentication with inaccessible authentication bypass, the switch must be running the LAN base image. 802.1x Authentication with Voice VLAN Ports, page 10-27 802.1x Authentication with Port Security, page 10-28 802.1x Authentication with Wake-on-LAN, page 10-28 802.1x Authentication with MAC Authentication Bypass, page 10-28 802.1x User Distribution, page 10-30 Network Admission Control Layer 2 802.1x Validation, page 10-31

• • • • • •

Note • • • • • •

To use Network Admission Control, the switch must be running the LAN base image. Flexible Authentication Ordering, page 10-31 Open1x Authentication, page 10-31 Using Voice Aware 802.1x Security, page 10-32 802.1x Supplicant and Authenticator Switches with Network Edge Access Topology (NEAT), page 10-32 802.1x Authentication with Downloadable ACLs and Redirect URLs, page 10-20 Using IEEE 802.1x Authentication with ACLs and the RADIUS Filter-Id Attribute, page 10-34

Note

To use IEEE 802.1x authentication with ACLs and the Filter-Id attribute, the switch must be running the LAN base image. Common Session ID, page 10-34

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE

10-2

OL-26520-02

Chapter 10

Configuring IEEE 802.1x Port-Based Authentication Understanding IEEE 802.1x Port-Based Authentication

Device Roles
Figure 10-1 802.1x Device Roles

Authentication server (RADIUS) Workstations (clients)

Client—the device (workstation) that requests access to the LAN and switch services and responds to requests from the switch. The workstation must be running 802.1x-compliant client software such as that offered in the Microsoft Windows XP operating system. (The client is the supplicant in the 802.1x standard.)

Note

To resolve Windows XP network connectivity and 802.1x authentication issues, read the Microsoft Knowledge Base article: http://support.microsoft.com/support/kb/articles/Q303/5/97.ASP

Authentication server—performs the actual authentication of the client. The authentication server validates the identity of the client and notifies the switch whether or not the client is authorized to access the LAN and switch services. Because the switch acts as the proxy, the authentication service is transparent to the client. In this release, the RADIUS security system with Extensible Authentication Protocol (EAP) extensions is the only supported authentication server. It is available in Cisco Secure Access Control Server Version 3.0 or later. RADIUS operates in a client/server model in which secure authentication information is exchanged between the RADIUS server and one or more RADIUS clients. Switch (edge switch or wireless access point)—controls the physical access to the network based on the authentication status of the client. The switch acts as an intermediary (proxy) between the client and the authentication server, requesting identity information from the client, verifying that information with the authentication server, and relaying a response to the client. The switch includes the RADIUS client, which is responsible for encapsulating and decapsulating the EAP frames and interacting with the authentication server. (The switch is the authenticator in the 802.1x standard.) When the switch receives EAPOL frames and relays them to the authentication server, the Ethernet header is stripped, and the remaining EAP frame is re-encapsulated in the RADIUS format. The EAP frames are not modified during encapsulation, and the authentication server must support EAP within the native frame format. When the switch receives frames from the authentication server, the server’s frame header is removed, leaving the EAP frame, which is then encapsulated for Ethernet and sent to the client. The devices that can act as intermediaries include the Catalyst 3750-E, Catalyst 3560-E, Catalyst 3750, Catalyst 3560, Catalyst 3550, Catalyst 2975, Catalyst 2970, Catalyst 2960, Catalyst 2955, Catalyst 2950, Catalyst 2940 switches, or a wireless access point. These devices must be running software that supports the RADIUS client and 802.1x authentication.

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE OL-26520-02

101229

10-3

Chapter 10 Understanding IEEE 802.1x Port-Based Authentication

Configuring IEEE 802.1x Port-Based Authentication

Authentication Process
When 802.1x port-based authentication is enabled and the client supports 802.1x-compliant client software, these events occur:
• •

If the client identity is valid and the 802.1x authentication succeeds, the switch grants the client access to the network. If 802.1x authentication times out while waiting for an EAPOL message exchange and MAC authentication bypass is enabled, the switch can use the client MAC address for authorization. If the client MAC address is valid and the authorization succeeds, the switch grants the client access to the network. If the client MAC address is invalid and the authorization fails, the switch assigns the client to a guest VLAN that provides limited services if a guest VLAN is configured. If the switch gets an invalid identity from an 802.1x-capable client and a restricted VLAN is specified, the switch can assign the client to a restricted VLAN that provides limited services. If the RADIUS authentication server is unavailable (down) and inaccessible authentication bypass is enabled, the switch grants the client access to the network by putting the port in the critical-authentication state in the RADIUS-configured or the user-specified access VLAN.

• •

Note

Inaccessible authentication bypass is also referred to as critical authentication or the AAA fail policy.
Authentication Flowchart
Start

Figure 10-2

Is the client IEEE 802.1x capable? Yes

No

IEEE 802.1x authentication process times out. The switch gets an EAPOL message, and the EAPOL message exchange begins.

Is MAC authentication bypass enabled? 1 Yes No

User does not have a certificate but the system previously logged on to the network using a computer certificate.

Start IEEE 802.1x port-based authentication. Client Client identity is identity is invalid valid Assign the port to a restricted VLAN. Done Assign the port to a VLAN. Done

Use MAC authentication bypass.1 Client MAC address identity is valid. Assign the port to a VLAN. Done All authentication servers are down. Client MAC address identity is invalid. Assign the port to a guest VLAN. 1 Done

Assign the port to a guest VLAN. Done

All authentication servers are down. Use inaccessible authentication bypass (critical authentication) to assign the critical port to a VLAN. Done

1 = This occurs if the switch does not detect EAPOL packets from the client.
281594

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE

10-4

OL-26520-02

Chapter 10

Configuring IEEE 802.1x Port-Based Authentication Understanding IEEE 802.1x Port-Based Authentication

The switch reauthenticates a client when one of these situations occurs:

Periodic reauthentication is enabled, and the reauthentication timer expires. You can configure the reauthentication timer to use a switch-specific value or to be based on values from the RADIUS server. After 802.1x authentication using a RADIUS server is configured, the switch uses timers based on the Session-Timeout RADIUS attribute (Attribute[27]) and the Termination-Action RADIUS attribute (Attribute [29]). The Session-Timeout RADIUS attribute (Attribute[27]) specifies the time after which reauthentication occurs. The Termination-Action RADIUS attribute (Attribute [29]) specifies the action to take during reauthentication. The actions are Initialize and ReAuthenticate. When the Initialize action is set (the attribute value is DEFAULT), the 802.1x session ends, and connectivity is lost during reauthentication. When the ReAuthenticate action is set (the attribute value is RADIUS-Request), the session is not affected during reauthentication. We recommend that you specify the attribute value as RADIUS-Request. You manually reauthenticate the client by entering the dot1x reauthenticate interface interface-id privileged EXEC command.

If Multidomain authentication (MDA) is enabled on a port, this flow can be used with some exceptions that are applicable to voice authorization. For more information on MDA, see the “Multidomain Authentication” section on page 10-13.

Authentication Initiation and Message Exchange
During 802.1x authentication, the switch or the client can initiate authentication. If you enable authentication on a port by using the authentication port-control auto interface configuration command, the switch initiates authentication when the link state changes from down to up or periodically as long as the port remains up and unauthenticated. The switch sends an EAP-request/identity frame to the client to request its identity. Upon receipt of the frame, the client responds with an EAP-response/identity frame. However, if during boot up, the client does not receive an EAP-request/identity frame from the switch, the client can initiate authentication by sending an EAPOL-start frame, which prompts the switch to request the client’s identity.

Note

If 802.1x authentication is not enabled or supported on the network access device, any EAPOL frames from the client are dropped. If the client does not receive an EAP-request/identity frame after three attempts to start authentication, the client sends frames as if the port is in the authorized state. A port in the authorized state effectively means that the client has been successfully authenticated. For more information, see the “Ports in Authorized and Unauthorized States” section on page 10-10. When the client supplies its identity, the switch begins its role as the intermediary, passing EAP frames between the client and the authentication server until authentication succeeds or fails. If the authentication succeeds, the switch port becomes authorized. If the authentication fails, authentication can be retried, the port might be assigned to a VLAN that provides limited services, or network access is not granted. For more information, see the “Ports in Authorized and Unauthorized States” section on page 10-10.

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE OL-26520-02

10-5

Chapter 10 Understanding IEEE 802.1x Port-Based Authentication

Configuring IEEE 802.1x Port-Based Authentication

The specific exchange of EAP frames depends on the authentication method being used. Figure 10-3 shows a message exchange initiated by the client when the client uses the One-Time-Password (OTP) authentication method with a RADIUS server.
Figure 10-3 Message Exchange

Client

Authentication server (RADIUS)

EAPOL-Start EAP-Request/Identity EAP-Response/Identity EAP-Request/OTP EAP-Response/OTP EAP-Success RADIUS Access-Request RADIUS Access-Challenge RADIUS Access-Request RADIUS Access-Accept Port Authorized EAPOL-Logoff
101228

Port Unauthorized

If 802.1x authentication times out while waiting for an EAPOL message exchange and MAC authentication bypass is enabled, the switch can authorize the client when the switch detects an Ethernet packet from the client. The switch uses the MAC address of the client as its identity and includes this information in the RADIUS-access/request frame that is sent to the RADIUS server. After the server sends the switch the RADIUS-access/accept frame (authorization is successful), the port becomes authorized. If authorization fails and a guest VLAN is specified, the switch assigns the port to the guest VLAN. If the switch detects an EAPOL packet while waiting for an Ethernet packet, the switch stops the MAC authentication bypass process and stops 802.1x authentication. Figure 10-4 shows the message exchange during MAC authentication bypass.

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE

10-6

OL-26520-02

Chapter 10

Configuring IEEE 802.1x Port-Based Authentication Understanding IEEE 802.1x Port-Based Authentication

Figure 10-4

Message Exchange During MAC Authentication Bypass

Client

Switch

Authentication server (RADIUS)

EAPOL Request/Identity EAPOL Request/Identity EAPOL Request/Identity Ethernet packet RADIUS Access/Request
141681

RADIUS Access/Accept

Authentication Manager
In Cisco IOS Release 12.2(46)SE and earlier, you could not use the same authorization methods, including CLI commands and messages, on this switch and also on other network devices, such as a Catalyst 6000. You had to use separate authentication configurations. Cisco IOS Release 12.2(50)SE and later supports the same authorization methods on all Catalyst switches in a network. Cisco IOS Release 12.2(55)SE supports filtering verbose system messages from the authentication manager. For details, see the “Authentication Manager CLI Commands” section on page 10-9.
• • •

Port-Based Authentication Methods, page 10-7 Per-User ACLs and Filter-Ids, page 10-8 Authentication Manager CLI Commands, page 10-9

Port-Based Authentication Methods
Table 10-1 lists the authentication methods supported in these host modes:
• • • •

Single host–Only one data or voice host (client) can be authenticated on a port. Multiple host–Multiple data hosts can be authenticated on the same port. (If a port becomes unauthorized in multiple-host mode, the switch denies network access to all of the attached clients.) Multidomain authentication (MDA) –Both a data device and voice device can be authenticated on the same switch port. The port is divided into a data domain and a voice domain. Multiple authentication–Multiple hosts can authenticate on the data VLAN. This mode also allows one client on the VLAN if a voice VLAN is configured.

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE OL-26520-02

10-7

Chapter 10 Understanding IEEE 802.1x Port-Based Authentication

Configuring IEEE 802.1x Port-Based Authentication

Table 10-1

802.1x Features

Mode Authentication method 802.1x Single Host VLAN assignment Per-user ACL Filter-ID attribute Downloadable ACL3 Redirect URL 3 MAC authentication bypass VLAN assignment Per-user ACL Filter-ID attribute Downloadable ACL3 Redirect URL3 Standalone web authentication4 NAC Layer 2 IP validation Multiple Host VLAN assignment Per-user ACL Filter-ID attribute Downloadable ACL4 Redirect URL 3 VLAN assignment Per-user ACL Filter-ID attribute Downloadable ACL3 Redirect URL3 MDA1 VLAN assignment Per-user ACL3 Filter-Id attribute3 Downloadable ACL3 Redirect URL3 VLAN assignment Per-user ACL3 Filter-Id attribute3 Downloadable ACL3 Redirect URL3 Per-user ACL3 Filter-Id attribute3 Downloadable ACL3 Redirect URL3 Multiple Authentication2 Per-user ACL3 Filter-Id attribute3 Downloadable ACL3 Redirect URL3

Proxy ACL, Filter-Id attribute, downloadable ACL2 Filter-Id attribute3 Filter-Id attribute3 Filter-Id attribute3 Filter-Id attribute3 Downloadable ACL Downloadable ACL Downloadable ACL Downloadable ACL3 Redirect URL Redirect URL Redirect URL Redirect URL3

Web authentication as fallback method5

Proxy ACL Filter-Id attribute3 Downloadable ACL3

Proxy ACL Filter-Id attribute3 Downloadable ACL3

Proxy ACL Filter-Id attribute3 Downloadable ACL3

Proxy ACL3 Filter-Id attribute3 Downloadable ACL3

1. MDA = Multidomain authentication. 2. Also referred to as multiauth. 3. Supported in Cisco IOS Release 12.2(50)SE and later. 4. Supported in Cisco IOS Release 12.2(50)SE and later. 5. For clients that do not support 802.1x authentication.

Per-User ACLs and Filter-Ids
In releases earlier than Cisco IOS Release 12.2(50)SE, per-user ACLs and filter Ids were only supported in single-host mode. In Cisco IOS Release 12.2(50), support was added for MDA- and multiauth-enabled ports. In 12.2(52)SE and later, support was added for ports in multihost mode. In releases earlier than Cisco IOS Release 12.2(50)SE, an ACL configured on the switch is not compatible with an ACL configured on another device running Cisco IOS software, such as a Catalyst 6000 switch. In Cisco IOS Release 12.2(50)SE or later, the ACLs configured on the switch are compatible with other devices running the Cisco IOS release.

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE

10-8

OL-26520-02

Chapter 10

Configuring IEEE 802.1x Port-Based Authentication Understanding IEEE 802.1x Port-Based Authentication

Note

You can only set any as the source in the ACL.

Note

For any ACL configured for multiple-host mode, the source portion of statement must be any. (For example, permit icmp any host 10.10.1.1.) You must specify any in the source ports of any defined ACL. Otherwise, the ACL cannot be applied and authorization fails. Single host is the only exception to support backward compatibility. More than one host can be authenticated on MDA-enabled and multiauth ports. The ACL policy applied for one host does not effect the traffic of another host. If only one host is authenticated on a multi-host port, and the other hosts gain network access without authentication, the ACL policy for the first host can be applied to the other connected hosts by specifying any in the source address.

Authentication Manager CLI Commands
The authentication-manager interface-configuration commands control all the authentication methods, such as 802.1x, MAC authentication bypass, and web authentication. The authentication manager commands determine the priority and order of authentication methods applied to a connected host. The authentication manager commands control generic authentication features, such as host-mode, violation mode, and the authentication timer. Generic authentication commands include the authentication host-mode, authentication violation, and authentication timer interface configuration commands. 802.1x-specific commands begin with the dot1x or authentication keyword. For example, the authentication port-control auto interface configuration command enables authentication on an interface. However, the dot1x system-authentication control global configuration command only globally enables or disables 802.1x authentication.

Note

If 802.1x authentication is globally disabled, other authentication methods are still enabled on that port, such as web authentication. The authentication manager commands provide the same functionality as earlier 802.1x commands.

Table 10-2

Authentication Manager Commands and Earlier 802.1x Commands

The authentication manager commands in Cisco IOS Release 12.2(50)SE or later authentication control-direction {both | in} authentication event

The equivalent 802.1x commands in Cisco IOS Release 12.2(46)SE and earlier Description dot1x control-direction {both | in} dot1x auth-fail vlan dot1x critical (interface configuration) dot1x guest-vlan6 Enable authentication with the wake-on-LAN (WoL) feature, and configure the port control as unidirectional or bidirectional. Enable the restricted VLAN on a port. Enable the inaccessible-authentication-bypass feature. Specify an active VLAN as an guest VLAN.

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE OL-26520-02

10-9

Chapter 10 Understanding IEEE 802.1x Port-Based Authentication

Configuring IEEE 802.1x Port-Based Authentication

Table 10-2

Authentication Manager Commands and Earlier 802.1x Commands (continued)

The authentication manager commands in Cisco IOS Release 12.2(50)SE or later authentication fallback fallback-profile authentication host-mode [multi-auth | multi-domain | multi-host | single-host] authentication order authentication periodic

The equivalent 802.1x commands in Cisco IOS Release 12.2(46)SE and earlier Description dot1x fallback fallback-profile Configure a port to use web authentication as a fallback method for clients that do not support authentication. Allow a single host (client) or multiple hosts on an authorized port. Provides the flexibility to define the order of authentication methods to be used. Enable periodic reauthentication of the client. Enable manual control of the authorization state of the port. Set the timers.

dot1x host-mode {single-host | multi-host | multi-domain} dot1x mac-auth-bypass dot1x reauthentication

authentication port-control {auto dot1x port-control {auto | | force-authorized | force-un force-authorized | authorized} force-unauthorized} authentication timer dot1x timeout

authentication violation {protect | dot1x violation-mode {shutdown Configure the violation modes that occur when a restrict | shutdown} | restrict | protect} new device connects to a port or when a new device connects to a port after the maximum number of devices are connected to that port. Beginning with Cisco IOS Release 12.2(55)SE, you can filter out verbose system messages generated by the authentication manager. The filtered content typically relates to authentication success. You can also filter verbose messages for 802.1x authentication and MAB authentication. There is a separate command for each authentication method:
• • •

The no authentication logging verbose global configuration command filters verbose messages from the authentication manager. The no dot1x logging verbose global configuration command filters 802.1x authentication verbose messages. The no mab logging verbose global configuration command filters MAC authentication bypass (MAB) verbose messages

For more information, see the command reference for this release.

Ports in Authorized and Unauthorized States
During 802.1x authentication, depending on the switch port state, the switch can grant a client access to the network. The port starts in the unauthorized state. While in this state, the port that is not configured as a voice VLAN port disallows all ingress and egress traffic except for 802.1x authentication, CDP, and STP packets. When a client is successfully authenticated, the port changes to the authorized state, allowing all traffic for the client to flow normally. If the port is configured as a voice VLAN port, the port allows VoIP traffic and 802.1x protocol packets before the client is successfully authenticated. If a client that does not support 802.1x authentication connects to an unauthorized 802.1x port, the switch requests the client’s identity. In this situation, the client does not respond to the request, the port remains in the unauthorized state, and the client is not granted access to the network.

Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE

10-10

OL-26520-02

” and the 802. If the authentication fails. causing the switch port to change to the unauthorized state. and network access is not granted. and all frames from the authenticated client are allowed through the port. “Managing Switch Stacks. Release 15. The switch requests the identity of the client and begins relaying authentication messages between the client and the authentication server. force-unauthorized—causes the port to remain in the unauthorized state.1x authentication and causes the port to begin in the unauthorized state. authentication fails. 802. or if an EAPOL-logoff frame is received. When no response is received. This is the default setting. If a switch is added to or removed from a switch stack.1x Port-Based Authentication In contrast.1x standard. ignoring all attempts by the client to authenticate.1x-enabled client connects to a port that is not running the 802. Communication with the RADIUS server is required. but authentication can be retried. Because no response is received. The port sends and receives normal traffic without 802. Communication with the RADIUS server is not required. When a client logs off. If the link state of a port changes from up to down.1x authentication is not affected as long as the IP connectivity between the RADIUS server and the stack remains intact. • • If the client is successfully authenticated (receives an Accept frame from the authentication server). 802.Chapter 10 Configuring IEEE 802. Ports return to the unauthenticated state during the reauthentication process.1x authentication process continues as usual. when an 802. the client begins sending frames as if the port is in the authorized state.1x Authentication and Switch Stacks Note Switch stacks are supported only on Catalyst 2960-S switches running the LAN base image. these events occur: • • Ports that are already authenticated and that do not have periodic reauthentication enabled remain in the authenticated state. the port remains in the unauthorized state. If no response is received from the server after the specified number of attempts. Ports that are already authenticated and that have periodic reauthentication enabled (with the dot1x reauthentication global configuration command) fail the authentication process when the reauthentication occurs. The switch cannot provide authentication services to the client through the port.1x authentication and causes the port to change to the authorized state without any authentication exchange required. Catalyst 2960 and 2960-S Switches Software Configuration Guide. a stack member becomes the new stack master by using the election process described in Chapter 7. it sends an EAPOL-logoff message. The authentication process begins when the link state of the port changes from down to up or when an EAPOL-start frame is received. allowing only EAPOL frames to be sent and received through the port. the switch can resend the request. the port returns to the unauthorized state. This statement also applies if the stack master is removed from the switch stack. Each client attempting to access the network is uniquely identified by the switch by using the client MAC address. Note that if the stack master fails. If IP connectivity to the RADIUS server is interrupted because the switch that was connected to the server is removed or fails. If the authentication server cannot be reached. the port state changes to authorized.0(1)SE OL-26520-02 10-11 .1x Port-Based Authentication Understanding IEEE 802.1x-based authentication of the client. auto—enables 802. the client sends the request for a fixed number of times. the client initiates the authentication process by sending the EAPOL-start frame. You control the port authorization state by using the authentication port-control interface configuration command and these keywords: • force-authorized—disables 802.

1x port-based authentication in a wireless LAN. such as an IP Phone (Cisco or non-Cisco). you can attach multiple hosts to a single 802. For example. and if the stack master fails. Figure 10-5 Multiple Host Mode Example Authentication server (RADIUS) Workstations (clients) Note For all host modes. In multiple-hosts mode.1x-enabled switch port. In this topology. the switch denies network access to all of the attached clients. which allows both a data device and a voice device. the switch changes the port link state to down. Figure 10-5 on page 10-12 shows 802. To avoid loss of connectivity to the RADIUS server. only one of the attached clients must be authorized for all clients to be granted network access.0(1)SE 10-12 101229 OL-26520-02 .1x port for single-host or for multiple-hosts mode. see the “Multidomain Authentication” section on page 10-13. the authentication fails immediately because there is no server connectivity. Catalyst 2960 and 2960-S Switches Software Configuration Guide. The switch detects the client by sending an EAPOL frame when the port link state changes to the up state.1x-enabled port. and it also acts as a client to the switch.Chapter 10 Understanding IEEE 802. In single-host mode (see Figure 10-1 on page 10-3). only one client can be connected to the 802. If the port becomes unauthorized (reauthentication fails or an EAPOL-logoff message is received). the authentications might or might not fail depending on the boot-up time and whether the connectivity to the RADIUS server is re-established by the time the authentication is attempted. For more information.1x Port-Based Authentication • For an ongoing authentication. the wireless access point is responsible for authenticating the clients attached to it. to connect to the same switch port. the switch stack still has connectivity to the RADIUS server. the line protocol stays up before authorization when port-based authentication is configured. you can have a redundant connection to the stack master and another to a stack member. The switch supports multidomain authentication (MDA). In this mode. If the switch that failed comes up and rejoins the switch stack. Release 15.1x Port-Based Authentication Configuring IEEE 802. If a client leaves or is replaced with another client.1x Host Mode You can configure an 802. and the port returns to the unauthorized state. you should ensure that there is a redundant connection to it. 802.

or multihost to multidomain mode. Note To use MDA. which allows both a data device and voice device. Release 15. The port is divided into a data domain and a voice domain. However.2(40)SE and later. MDA can use MAC authentication bypass as a fallback mechanism to allow the switch port to connect to devices that do not support 802. Active fallback mechanisms such as guest VLAN and restricted VLAN remain configured after a port changes from single-host or multiple-host mode to multidomain mode. The data VLAN allows the voice device to contact a DHCP server to obtain an IP address and acquire the voice VLAN information.2(37)SE. the port drops its traffic. the AAA server must be configured to send a Cisco Attribute-Value (AV) pair attribute with a value of device-traffic-class=voice. such as an IP phone (Cisco or non-Cisco). the MAC address remains blocked for 5 minutes.1x Port-Based Authentication Multidomain Authentication The switch supports multidomain authentication (MDA). its access to the data VLAN is blocked. an authorized data device remains authorized on the port. Follow these guidelines for configuring MDA: • • • To configure a switch port for MDA. A voice device MAC address that is binding on the data VLAN is not counted towards the port security MAC address limit.0(1)SE OL-26520-02 10-13 . to authenticate on the same switch port. it is error disabled. If more than five devices are detected on the data VLAN or more than one voice device is detected on the voice VLAN while a port is unauthorized. Without this value. When a data or a voice device is detected on a port.1x Port-Based Authentication Understanding IEEE 802. the switch treats the voice device as a data device.” Voice VLAN assignment on an MDA-enabled port is supported in Cisco IOS Release 12. However. The guest VLAN and restricted VLAN features only apply to the data devices on an MDA-enabled port. Note If you use a dynamic VLAN to assign a voice VLAN on an MDA-enabled switch port on a switch running Cisco IOS Release 12. the voice device fails authorization. To authorize a voice device. The switch treats a voice device that fails authorization as a data device. a Cisco IP phone on the port voice VLAN is automatically removed and must be reauthenticated on that port. If more than one device attempts authorization on either the voice or the data domain of a port. see Chapter 13. we recommend that a voice device is authenticated before a data device on an MDA-enabled port. the port is error disabled. see the “Configuring the Host Mode” section on page 10-45. For more information. MDA does not enforce the order of device authentication. When a port host mode changes from single. After the voice device starts sending on the voice VLAN. the switch must be running the LAN base image. If the authorization fails. • • • • • • • • • • Catalyst 2960 and 2960-S Switches Software Configuration Guide. Until a device is authorized. its MAC address is blocked until authorization succeeds. For more information. “Configuring VLANs.Chapter 10 Configuring IEEE 802. Non-Cisco IP phones or voice devices are allowed into both the data and voice VLANs.1x authentication. for best results. You must configure the voice VLAN for the IP phone when the host mode is set to multidomain. see the “MAC Authentication Bypass” section on page 10-39.

Beginning with Cisco IOS Release 12. Catalyst 2960 and 2960-S Switches Software Configuration Guide. they are discarded from the port. For MDA functionality on the voice VLAN. Each host is individually authenticated. An authorized device with a per-user ACL policy might impact traffic on both the port voice and data VLANs. (The same is true for an 802.1x-capable voice devices need their packets tagged on the voice VLAN to trigger authentication. Release 15.1x-enabled port. you can assign a RADIUS-server-supplied VLAN in multi-auth mode. Since there is no host limit defined violation will not be trigger. if a second voice is seen we silently discard it but do not trigger violation. If a voice VLAN is configured. There is no limit to the number of data hosts can authenticate on a multiauthport. If a VLAN list is used. and subsequent hosts either have no VLAN assignment. depending on the VSAs received from the authentication server. under these conditions: • • • • • The switch is running the LAN base image. For non-802. The host is the first host authorized on the port.2(55)SE. multiple-authentication mode assigns authenticated devices to either a data or a voice VLAN. see the “802.1x devices. each connected client must be authenticated. but no violation errors occur. see the “Configuring the Host Mode” section on page 10-45. For more information about configuring multiauth mode on a port. the guest VLAN and the authentication-failed VLAN features do not activate. non-802.) If a hub or access point is connected to an 802. see the “Configuring the Host Mode” section on page 10-45.) We do not recommend per-user ACLs with an MDA-enabled port. Note When a port is in multiple-authentication mode. or their VLAN information matches the operational VLAN. If a data domain is authorized first and placed in the guest VLAN. all hosts are subject to the conditions specified in the VLAN list. or their group VLAN matches the group VLAN on the port. However. 802. (If the port detects any additional voice clients. A host is authorized on the port with no VLAN assignment. • For more information. you can use MAC authentication bypass or web authentication as the per-host authentication fallback method to authenticate different hosts with different methods on a single port. For more information about critical authentication mode and the critical VLAN. and the RADIUS server supplies VLAN information. Subsequent hosts are authorized with a VLAN that matches the operational VLAN. You can use only one device on the port to enforce per-user ACLs. only one voice device is allowed if the voice VLAN is configured.1x Authentication with Inaccessible Authentication Bypass” section on page 10-25. The first host authorized on the port has a group VLAN assignment. and subsequent hosts either have no VLAN assignment.1x Port-Based Authentication Configuring IEEE 802.1x Multiple Authentication Mode Multiple-authentication (multiauth) mode allows multiple authenticated clients on the data VLAN. The phone need not need to send tagged traffic. Subsequent hosts must use the same VLAN from the VLAN group as the first host.0(1)SE 10-14 OL-26520-02 .1x Port-Based Authentication • • Switching a port host mode from multidomain to single-host or multiple-hosts mode removes all authorized devices from the port. this mode also allows one client on the VLAN.Chapter 10 Understanding IEEE 802.1x-capable phone.

For example. You cannot configure a guest VLAN or an auth-fail VLAN in multi-auth mode. that address is not allowed on another authentication manager-enabled port of the switch.0(1)SE OL-26520-02 10-15 . all authorized hosts are reinitialized in the configured VLAN. After a VLAN is assigned to a host on the port. Catalyst 2960 and 2960-S Switches Software Configuration Guide. the session on the first port is deleted.1x Port-Based Authentication • • • • Only one voice VLAN assignment is supported on a multi-auth port. only the first host requires authentication. no matter which host mode is enabled on the that port. There are situations where a MAC address might need to move from one port to another on the same switch. with no requirement for authorization on the new port.Chapter 10 Configuring IEEE 802. MAC Move When a MAC address is authenticated on one switch port. When a host tries to authenticate and the server is not reachable. You can globally enable MAC move so the device is reauthenticated on the new port. When a host moves to a second port. It does not apply to ports in multiple host mode. Beginning with Cisco IOS Release 12. Note In open authentication mode. the MAC replace feature can be configured to address the violation that occurs when a host attempts to connect to a port where another host was previously authenticated. the address is not allowed. Release 15. and the host is reauthenticated on the new port. The MAC move feature applies to both voice and data hosts.) When a MAC address moves from one port to another. If the switch detects that same MAC address on another authentication manager-enabled port. because violations are not triggered in that mode. the switch terminates the authenticated session on the original port and initiates a new authentication sequence on the new port. the switch must be running the LAN base image.1x Port-Based Authentication Understanding IEEE 802. Note This feature does not apply to ports in multi-auth mode. For more information see the “Enabling MAC Move” section on page 10-50. because in that mode. you might want to disconnect the host from the device and connect it directly to another port on the same switch. The behavior of the critical-auth VLAN is not changed for multi-auth mode. (The authenticated host can move to any port on the switch.2(55)SE. when there is another device (for example a hub or an IP phone) between an authenticated host and a switch port. MAC Replace Note To configure the MAC replace feature. MAC move is supported on all host modes. a MAC address is immediately moved from the original port to the new port. subsequent hosts must have matching VLAN information or be denied access to the port.

0(1)SE 10-16 OL-26520-02 . The authentication manager initiates the authentication process for the new MAC address. 802.1x Port-Based Authentication Configuring IEEE 802. (For example. The switch does not log 802. 802.) AV pairs are automatically sent by a switch that is configured for 802.1x Port-Based Authentication If you configure the authentication violation interface configuration command with the replace keyword.1x standard defines how users are authorized and authenticated for network access but does not keep track of network usage. 802. For more information see the “Enabling MAC Replace” section on page 10-51. Link-down occurs. If a port is in open authentication mode. Reauthentication successfully occurs. User logs off. the original voice host is removed. it sends this information to the RADIUS server. Instead. Three types of RADIUS accounting packets are sent by a switch: • • • START–sent when a new user session starts INTERIM–sent during an existing session for updates STOP–sent when a session terminates Table 10-3 lists the AV pairs and when they are sent are sent by the switch: Table 10-3 Accounting AV Pairs Attribute Number Attribute[1] Attribute[4] AV Pair Name User-Name NAS-IP-Address START Always Always INTERIM Always Always STOP Always Always Catalyst 2960 and 2960-S Switches Software Configuration Guide.Chapter 10 Understanding IEEE 802. Release 15. If the authentication manager determines that the new host is a voice host.1x Accounting The 802. You can enable 802. which must be configured to log accounting messages. Reauthentication fails.1x accounting. the authentication process on a port in multi-domain mode is: • • • • A new MAC address is received on a port with an existing authenticated MAC address. The authentication manager replaces the MAC address of the current data host on the port with the new MAC address. a billing application might require information that is in the Acct-Input-Octets or the Acct-Output-Octets attributes of a RADIUS packet.1x-enabled ports: • • • • • User successfully authenticates.1x accounting information. These AV pairs provide data for different applications.1x accounting to monitor this activity on 802.1x Accounting Attribute-Value Pairs The information sent to the RADIUS server is represented in the form of Attribute-Value (AV) pairs. any new MAC address is immediately added to the MAC address table.1x accounting is disabled by default.

cisco. For more information about this command. This feature only works if the supplicant on the client supports a query with the NOTIFY EAP notification packet. You can view the AV pairs that are being sent by the switch by entering the debug radius accounting privileged EXEC command.1x functionality. The client must respond within the 802. You use an alternate authentication such as MAC authentication bypass or web authentication for the devices that do not support 802.” 802.1x Readiness Check Note To use 802.com/en/US/docs/ios/12_2/debug/command/reference/122debug.1x Remote Authentication Dial In User Service (RADIUS) Usage Guidelines.1x readiness check.Chapter 10 Configuring IEEE 802. For information on configuring the switch for the 802. the switch must be running the LAN base image.1x Readiness Check” section on page 10-39. “802. see the “Configuring 802. see the Cisco IOS Debug Command Reference: http://www. Catalyst 2960 and 2960-S Switches Software Configuration Guide.html For more information about AV pairs.1x readiness check. The 802.1x activity on all the switch ports and displays information about the devices connected to the ports that support 802. Release 15.0(1)SE OL-26520-02 10-17 .1x Port-Based Authentication Table 10-3 Accounting AV Pairs (continued) Attribute Number Attribute[5] Attribute[8] Attribute[25] Attribute[30] Attribute[31] Attribute[40] Attribute[41] Attribute[42] Attribute[43] Attribute[44] Attribute[45] Attribute[46] Attribute[49] Attribute[61] AV Pair Name NAS-Port Framed-IP-Address Class Called-Station-ID Calling-Station-ID Acct-Status-Type Acct-Delay-Time Acct-Input-Octets Acct-Output-Octets Acct-Session-ID Acct-Authentic Acct-Session-Time Acct-Terminate-Cause NAS-Port-Type START Always Never Always Always Always Always Always Never Never Always Always Never Never Always INTERIM Always Sometimes Always Always Always Always Always Always Always Always Always Always Never Always 1 STOP Always Sometimes1 Always Always Always Always Always Always Always Always Always Always Always Always 1.1x Port-Based Authentication Understanding IEEE 802. You can use this feature to determine if the devices connected to the switch ports are 802.1x timeout value.1x.1x-capable. The Framed-IP-Address AV pair is sent only if a valid Dynamic Host Control Protocol (DHCP) binding exists for the host in the DHCP snooping bindings table.1x readiness check monitors 802. see RFC 3580.

2(40)SE and later. the voice VLAN on the port is configured to send and receive packets on the assigned voice VLAN. Configuration errors could include specifying a malformed VLAN ID. The RADIUS server database maintains the username-to-VLAN mappings.1x Authentication with VLAN Assignment The RADIUS server sends the VLAN assignment to configure the switch port. see the “Multidomain Authentication” section on page 10-13.1x authentication is disabled. For more information. the authorized device is placed in the specified VLAN after authentication. In the case of a mutlidomain host port. In the case of a multidomain host. it is returned to the configured access VLAN and configured voice VLAN. the port is configured in its access VLAN after successful authentication.1x authentication with VLAN assignment has these characteristics: • If no VLAN is supplied by the RADIUS server or if 802. – If a voice device is authorized and is using a downloaded voice VLAN. 802. unauthorized. all hosts are placed in the same VLAN (specified by the RADIUS server) as the first authenticated host. Recall that an access VLAN is a VLAN assigned to an access port. In Cisco IOS Release 12. When the port is in the force authorized.1x authentication is enabled and all information from the RADIUS server is valid. any change to the port access VLAN configuration does not take effect. or with dynamic-access port assignment through a VLAN Membership Policy Server (VMPS).1x authentication is enabled but the VLAN information from the RADIUS server is not valid.1x Port-Based Authentication Configuring IEEE 802. Release 15. Enabling port security does not impact the RADIUS server-assigned VLAN behavior. then authorization of all devices on the port is terminated and multidomain host mode is disabled until a valid configuration is restored where data and voice device configured VLANs no longer match. a shut down or suspended VLAN. If 802.1x port. Catalyst 2960 and 2960-S Switches Software Configuration Guide. If 802.1x authentication with VLAN assignment feature is not supported on trunk ports. Voice VLAN assignment behaves the same as data VLAN assignment on multidomain authentication (MDA)-enabled ports.Chapter 10 Understanding IEEE 802. authorization fails and configured VLAN remains in use. force unauthorized. the removal of the voice VLAN configuration. an RSPAN VLAN. If the multiple-hosts mode is enabled on an 802. Voice device authentication is supported with multidomain host mode in Cisco IOS Release 12. it is put into the configured access VLAN. dynamic ports. When configured on the switch and the RADIUS server.2(37)SE. or modifying the configuration value to dot1p or untagged results in voice device un-authorization and the disablement of multi-domain host mode. assigning the VLAN based on the username of the client connected to the switch port. If an 802. when a voice device is authorized and the RADIUS server returned an authorized VLAN. All packets sent from or received on this port belong to this VLAN. • • • • • • If 802. a nonexistent VLAN ID.0(1)SE 10-18 OL-26520-02 .1x port is authenticated and put in the RADIUS server-assigned VLAN. or shutdown state.1x authentication is disabled on the port. This prevents ports from appearing unexpectedly in an inappropriate VLAN because of a configuration error. You can use this feature to limit network access for certain users. the same applies to voice devices when the port is fully authorized with these exceptions: – If the VLAN configuration change of one device results in matching the other device configured or assigned VLAN. configuration errors can also be due to an attempted assignment of a data VLAN that matches the configured or assigned voice VLAN ID (or the reverse). The 802.1x Port-Based Authentication 802.

Outgoing routed packets are filtered by the router ACL. For more information.1x port for the duration of the user session.1x-authenticated user.1x Authentication with Per-User ACLs You can enable per-user access control lists (ACLs) to provide different levels of network access and service to an 802. Enable 802. For examples of tunnel attributes. You can configure router ACLs and input port ACLs on the same switch. “Configuring Network Security with ACLs. It does not support port ACLs in the egress direction on Layer 2 ports. However. a port ACL takes precedence over a router ACL. Attribute [81] specifies the VLAN name or VLAN ID assigned to the 802. To avoid configuration conflicts.1x Port-Based Authentication To configure VLAN assignment you need to perform these tasks: • • • Enable AAA authorization by using the network keyword to allow interface configuration from the RADIUS server. the port ACL takes precedence over an input router ACL applied to the VLAN interface. The switch applies the attributes to the 802.1x authentication.1x port. The RADIUS server must return these attributes to the switch: – [64] Tunnel-Type = VLAN – [65] Tunnel-Medium-Type = 802 – [81] Tunnel-Private-Group-ID = VLAN name. These vendor-specific attributes (VSAs) are in octet-string format and are passed to the switch during the authentication process. including vendor-specific attributes. Incoming packets received on the port to which a port ACL is applied are filtered by the port ACL. When the RADIUS server authenticates a user connected to an 802. or VLAN-Group – [83] Tunnel-Preference Attribute [64] must contain the value VLAN (type 13). you should carefully plan the user profiles stored on the RADIUS server. The switch supports VSAs only in the ingress direction. Incoming routed packets received on other ports are filtered by the router ACL.1x-authenticated user. see the “Configuring the Switch to Use Vendor-Specific RADIUS Attributes” section on page 9-36. it retrieves the ACL attributes based on the user identity and sends them to the switch.1x Port-Based Authentication Understanding IEEE 802.0(1)SE OL-26520-02 10-19 . Assign vendor-specific tunnel attributes in the RADIUS server. if you use the Filter-Id attribute. they are created by using the extended naming convention.Chapter 10 Configuring IEEE 802. (The VLAN assignment feature is automatically enabled when you configure 802. if authentication fails. the switch removes the ACL from the port. When the definitions are passed from the RADIUS server. The switch does not save RADIUS-specified ACLs in the running configuration. see Chapter 31. Using 802.” Use only the extended ACL syntax style to define the per-user configuration stored on the RADIUS server. RADIUS supports per-user attributes. it can point to a standard ACL. When the port is unauthorized. If you apply input port ACL to an interface that belongs to a VLAN. The switch removes the per-user ACL configuration when the session is over. Release 15. Attribute [65] must contain the value 802 (type 6). MAC ACLs are supported only in the ingress direction. However.1x authentication on an access port). Catalyst 2960 and 2960-S Switches Software Configuration Guide. VLAN ID. or if a link-down condition occurs. The VSAs used for per-user ACLs are inacl#<n> for the ingress direction and outacl#<n> for the egress direction.

Beginning with Cisco IOS Release 12.1x-enabled port.out syntax.2(55)SE. see the “Authentication Manager” section on page 10-7. the access list is applied to the outbound ACL by default. see Chapter 31. The attribute contains the ACL number followed by . the Filter-Id attribute is supported only for IP ACLs numbered 1 to 199 and 1300 to 2699 (IP standard and IP extended ACLs).1x authentication or MAC authentication bypass of the host. or multiple-authentication mode. If the RADIUS server does not allow the . Note A downloadable ACL is also referred to as a dACL. Enable AAA authorization by using the network keyword to allow interface configuration from the RADIUS server.1x port for single-host mode. Configure the user profile and VSAs on the RADIUS server. a dynamic auth-default ACL is created. For examples of vendor-specific attributes. Because of limited support of Cisco IOS access lists on the switch. the switch applies the static default ACL on the port to the host. MDA.out for egress filtering. 802.in or . you need to perform these tasks: • • • • • Enable AAA authentication.0(1)SE 10-20 OL-26520-02 . the switch changes the source address of the ACL to the host IP address.Chapter 10 Understanding IEEE 802. If no ACLs are downloaded during 802.1x Port-Based Authentication You can use the Filter-Id attribute to specify an inbound or outbound ACL that is already configured on the switch.in for ingress filtering or . see the “Configuring the Switch to Use Vendor-Specific RADIUS Attributes” section on page 9-36. For more configuration information. the switch applies the ACL only to the phone as part of the authorization policies. You can apply the ACLs and redirect URLs to all the devices connected to the 802. To configure per-user ACLs. On a voice VLAN port configured in multi-auth or MDA mode. The maximum size of the per-user ACL is 4000 ASCII characters but is limited by the maximum size of RADIUS-server per-user ACLs. “Configuring Network Security with ACLs. Configure the 802.1x Authentication with Downloadable ACLs and Redirect URLs You can download ACLs and redirect URLs from a RADIUS server to the switch during 802.1x authentication. and policies are enforced before dACLs are downloaded and applied. You can also download ACLs during web authentication. For more information about configuring ACLs. Enable 802. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Note The auth-default-ACL is created only when the switch is running the LAN base image. if there is no static ACL on a port.1x Port-Based Authentication Configuring IEEE 802. If more than one host is authenticated and the host is in single-host. Release 15.1x authentication.” Note Per-user ACLs are supported only in single-host mode.

the authorization policy is applied without IP address insertion. If the configured fallback profile does not include a fallback ACL. You can configure the directive either in the user profile on the AAA server or on the switch. When the first host authenticates.1x and MAB authentication methods support two authentication modes. An auth-default-ACL-OPEN is created and allows all traffic. Policies are enforced with IP address insertion to prevent security breaches.Chapter 10 Configuring IEEE 802. If there is no static ACL on a port in open authentication mode: • • • To control access for hosts with no authorization policy.1x Port-Based Authentication Note The auth-default-ACL does not appear in the running configuration. The 802. all traffic is allowed. The auth-default ACL is created when at least one host with an authorization policy is detected on the port. the auth-default-ACL-OPEN is created. the auth-default-ACL is created. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Note If you use a custom logo with web authentication and it is stored on an external server. To configure the directive on the switch. To configure the directive on the AAA server. the host is subject to the auth-default-ACL associated with the port. You can configure the auth-default ACL by using the ip access-list extended auth-default-acl global configuration command. The supported values for the directive are open and default. You must configure a static ACL on the interface to support CDP bypass.1x Port-Based Authentication Understanding IEEE 802. When you configure the open directive. Web authentication is subject to the auth-default-ACL-OPEN. open and closed. Note The auth-default-ACL does not support Cisco Discovery Protocol (CDP) bypass in the single host mode. The default directive subjects traffic to the access provided by the port. You must either configure a static port ACL or change the auth-default-ACL to provide appropriate access to the external server. The auth-default-ACL allows only DHCP traffic until policies are enforced. Note The default value of the directive is default. The auth-default ACL is removed from the port when the last authenticated session ends. Release 15. use the epm access-control open global configuration command. use the authz-directive =<open/default> global command.0(1)SE OL-26520-02 10-21 . the port ACL must allow access to the external server before authentication. If the port is in closed authentication mode. The access control entries (ACEs) in the fallback ACL are converted to per-user entries. When a second host is detected. and policies for the first and subsequent sessions are enforced with IP address insertion. the policies for the first host are refreshed. you can configure a directive. If a host falls back to web authentication on a port without a configured ACL: • • If the port is in open authentication mode. If there is no static ACL on a port in closed authentication mode: • • • • An auth-default-ACL is created.

The feature also limits the number of VLANs monitored and handled by STP. The url-redirect-acl attribute value pair contains the name or number of an ACL that specifies the HTTP or HTTPS traffic to redirect. VLAN information is sent to an IAS (Microsoft) RADIUS server along with the MAC address of each host for authentication. The url-redirect attribute value pair on the Cisco Secure ACS contains the URL to which the web browser is redirected. If a downloadable ACL is configured for a client on the authentication server. if the switch receives an host access policy from the Cisco Secure ACS but the default ACL is not configured. The switch then forwards the client web browser to the specified redirect address. 3f783768). When you have a static VLAN policy configured on your switch.0(1)SE 10-22 OL-26520-02 . VLAN ID-based MAC Authentication You can use VLAN ID-based MAC authentication if you wish to authenticate hosts based on a static VLAN ID instead of a downloadable VLAN. By using VLAN ID-based MAC authentication with an IAS server.1x Port-Based Authentication Configuring IEEE 802. The VLAN ID configured on the connected port is used for MAC authentication. The number is the version number (for example. Release 15. For configuration details. If the Cisco Secure ACS sends the switch a downloadable ACL. the authorization failure is declared. the switch applies the default ACL. If a redirect URL is configured for a client on the authentication server.Chapter 10 Understanding IEEE 802. Note Define the URL redirect ACL and the default port ACL on the switch. a default port ACL on the connected client switch port must also be configured. This pair specifies the names of the downloadable ACLs on the Cisco Secure ACS with the #ACL#-IP-name-number attribute. Cisco Secure ACS and Attribute-Value Pairs for Downloadable ACLs You can set the CiscoSecure-Defined-ACL Attribute-Value pair on the Cisco Secure ACS with the RADIUS cisco-av-pair vendor-specific attributes (VSAs). However. see the “Authentication Manager” section on page 10-7 and the “Configuring 802. Catalyst 2960 and 2960-S Switches Software Configuration Guide. • • The name is the ACL name. The switch uses the CiscoSecure-Defined-ACL attribute value pair to intercept an HTTP or HTTPS request from the end point device. a default port ACL on the connected client switch port must also be configured. this ACL takes precedence over the default ACL that is configured on the switch port. Traffic that matches a permit ACE in the ACL is redirected. it applies the policy to traffic from the host connected to a switch port. If the default ACL is configured on the switch and the Cisco Secure ACS sends a host-access-policy to the switch.1x Port-Based Authentication Cisco Secure ACS and Attribute-Value Pairs for the Redirect URL The switch uses these cisco-av-pair VSAs: • • url-redirect is the HTTP to HTTPS URL. you can have a fixed number of VLANs in the network.1x Authentication with Downloadable ACLs and Redirect URLs” section on page 10-63. url-redirect-acl is the switch ACL name or number.The network can be managed as a fixed VLAN. If the policy does not apply.

If no EAPOL packet is detected on the interface. When the AAA server becomes available.1x ports in single host.1x-capable. Guest VLANs are supported on 802.1x Port-Based Authentication Understanding IEEE 802. the switch assigns clients to a guest VLAN when the switch does not receive a response to its EAP request/identity frame or when EAPOL packets are not sent by the client. If an EAPOL packet is detected on the interface during the lifetime of the link.1x Authentication with Guest VLAN You can configure a guest VLAN for each 802. To prevent this situation. see the “Configuring VLAN ID-based MAC Authentication” section on page 10-65. multiple host. the authorization attempt fails.1x-capable client joins the same port on which the guest VLAN is configured. Note If an EAPOL packet is detected after the interface has changed to the guest VLAN. and some hosts. and the interface does not change to the guest VLAN state. Additional configuration is similar MAC authentication bypass. If devices send EAPOL packets to the switch during the lifetime of the link. (The ACS server ignores the sent VLAN-IDs for new hosts and only authenticates based on the MAC address.) For configuration information.1x-capable voice device and the AAA server is unavailable. it is supported only on access ports.1x-capable supplicant.1x Port-Based Authentication Note This feature is not supported on Cisco ACS Server. Release 15.1x port.1x client. or multi-domain modes. the interface changes to the guest VLAN state. The guest VLAN feature is not supported on trunk ports. EAPOL history is cleared if the interface link status goes down. and 802. the switch no longer allows other devices access to the guest VLAN. such as downloading the 802. but the detection of the EAPOL packet is saved in the EAPOL history. If the switch is trying to authorize an 802.1x authentication restarts. When you enable a guest VLAN on an 802. Catalyst 2960 and 2960-S Switches Software Configuration Guide. the switch authorizes the voice device.1x authentication. These clients might be upgrading their system for 802. such as Windows 98 systems. the switch determines that the device connected to that interface is an 802.1x port on the switch to provide limited services to clients. You can configure any active VLAN except an RSPAN VLAN or a voice VLAN as an 802. Any number of 802. and authentication is restarted. might not be 802.Chapter 10 Configuring IEEE 802. use one of these command sequences: • • Enter the authentication event no-response action authorize vlan vlan-id interface configuration command to allow access to the guest VLAN. If an 802. Enter the shutdown interface configuration command followed by the no shutdown interface configuration command to restart the port. 802. the switch no longer allows clients that fail authentication access to the guest VLAN. the interface reverts to an unauthorized state.1x-incapable clients are allowed access when the switch port is moved to the guest VLAN. the port is put into the unauthorized state in the user-configured access VLAN. as described in the “Configuring MAC Authentication Bypass” section on page 10-58.1x guest VLAN. The switch maintains the EAPOL packet history. However.0(1)SE OL-26520-02 10-23 .

1x port. When MAC authentication bypass is enabled on an 802. the port might not receive the link down or EAP logoff event. When this count exceeds the configured maximum number of authentication attempts. Without this feature.1x Authentication with Restricted VLAN You can configure a restricted VLAN (also referred to as an authentication failed VLAN) for each 802. When the port moves into the restricted VLAN.1x Authentication with MAC Authentication Bypass” section on page 10-28. visitors to an enterprise) to access a limited set of services. If you do this. A port in the restricted VLAN tries to reauthenticate at configured intervals (the default is 60 seconds).1x Port-Based Authentication The switch supports MAC authentication bypass. the client attempts and fails authentication indefinitely. Some clients (for example. it is supported only on access ports. These clients are 802. If authorization fails. The failed attempt count increments when the RADIUS server replies with either an EAP failure or an empty response without an EAP packet. the port remains in the restricted VLAN. A restricted VLAN allows users without valid credentials in an authentication server (typically. We recommend that you keep reauthentication enabled if a client might connect through a hub.Chapter 10 Understanding IEEE 802.1x Port-Based Authentication Configuring IEEE 802. devices running Windows XP) cannot implement DHCP without EAP success. you can configure the switch port to be in the restricted VLAN after a specified number of authentication attempts (the default value is 3 attempts).0(1)SE 10-24 OL-26520-02 . If authorization succeeds. With this feature. Users who fail authentication remain in the restricted VLAN until the next reauthentication attempt. see the “Configuring a Restricted VLAN” section on page 10-53. For more information. the port moves either to the configured VLAN or to a VLAN sent by the RADIUS server. and the switch port remains in the spanning-tree blocking state. You can disable reauthentication. The switch sends the authentication server a RADIUS-access/request frame with a username and password based on the MAC address. The administrator can control the services available to the restricted VLAN. the switch can authorize clients based on the client MAC address when 802. The authenticator counts the failed authentication attempts for the client. and IP source guard can be configured independently on a restricted VLAN. the switch grants the client access to the network. the switch assigns the port to the guest VLAN if one is specified. a simulated EAP success message is sent to the client. DHCP snooping. For more information.1x port on a switch to provide limited services to clients that cannot access the guest VLAN. Other security features such as dynamic ARP Inspection.1x port. the port moves to the restricted VLAN. You can configure any active VLAN except an RSPAN VLAN or a voice VLAN as an 802. This prevents clients from indefinitely attempting authentication. the failed attempt counter resets.1x restricted VLAN. After detecting a client on an 802.1x authentication times out while waiting for an EAPOL message exchange. When a client disconnects from the hub. see the “Configuring a Guest VLAN” section on page 10-53.1x ports in single-host mode and on Layer 2 ports. The restricted VLAN feature is not supported on trunk ports. Release 15. the only way to restart the authentication process is for the port to receive a link down or EAP logoff event. the switch waits for an Ethernet packet from the client. Note You can configure a VLAN to be both the guest VLAN and the restricted VLAN if you want to provide the same services to both types of users. see the “802. For more information. Catalyst 2960 and 2960-S Switches Software Configuration Guide.1x-compliant and cannot access another VLAN because they fail the authentication process. After a port moves to the restricted VLAN. 802. If reauthentication fails. Restricted VLANs are supported only on 802. If reauthentication is successful.

For more information. If a server is available. the switch puts the critical port in the critical-authentication state in the current VLAN. Release 15. when the switch cannot reach the configured RADIUS servers and new hosts cannot be authenticated. and the switch puts the critical port in the critical-authentication state during the next authentication attempt. Support on Multiple-Authentication Ports When a port is configured on any host mode and the AAA server is unavailable. The administrator gives limited authentication to the hosts. When a new host tries to connect to the critical port. the switch puts the port in the critical-authentication state in the RADIUS-configured or user-specified access VLAN. the port is then configured to multi-host mode and moved to the critical VLAN. see the command reference for this release and the “Configuring Inaccessible Authentication Bypass and Critical Voice VLAN” section on page 10-55. This command is supported on all host modes. use the authentication event server dead action reinitialize vlan vlan-id command. • • You can configure the critical port to reinitialize hosts and move them out of the critical VLAN when the RADIUS server is again available. When a new host tries to connect to the critical port.1x Authentication with Inaccessible Authentication Bypass Use the inaccessible authentication bypass feature. that port is reinitialized and all the connected hosts are moved to the user-specified access VLAN. if all the RADIUS servers are unavailable. the switch checks the status of the configured RADIUS server. the switch can authenticate the host. When the switch tries to authenticate a host connected to a critical port.Chapter 10 Configuring IEEE 802. the switch grants network access to the host and puts the port in the critical-authentication state. To support this inaccessible bypass on multiple-authentication (multiauth) ports. also referred to as critical authentication or the AAA fail policy. which might be the one previously assigned by the RADIUS server. Authentication Results The behavior of the inaccessible authentication bypass feature depends on the authorization state of the port: • If the port is unauthorized when a host connected to a critical port tries to authenticate and all servers are unavailable. If the port is already authorized and reauthentication occurs.1x Port-Based Authentication 802. Catalyst 2960 and 2960-S Switches Software Configuration Guide. all critical ports in the critical-authentication state are automatically reauthenticated. the current exchange times out. When this is configured. which is a special case of the authentication state.1x Port-Based Authentication Understanding IEEE 802. the critical VLAN.0(1)SE OL-26520-02 10-25 . However. You can configure the switch to connect those hosts to critical ports. If the RADIUS server becomes unavailable during an authentication exchange. that host is moved to a user-specified access VLAN.

the switch assigns a client to a guest VLAN when the switch does not receive a response to its EAP request/identity frame or when EAPOL packets are not sent by the client.Chapter 10 Understanding IEEE 802. the link between the switch stack and RADIUS server might change. When a guest VLAN is enabled on 8021. the stack master sends the member the server status. If the server status changes from dead to alive. Private VLAN—You can configure inaccessible authentication bypass on a private VLAN host port. The stack master checks the status of the RADIUS servers by sending keepalive packets. the features interact as follows: – If at least one RADIUS server is available. 802. the stack master sends the information to the stack members. Remote Switched Port Analyzer (RSPAN)—Do not configure an RSPAN VLAN as the RADIUS-configured or user-specified access VLAN for inaccessible authentication bypass. but the RADIUS-configured or user-specified access VLAN and the voice VLAN must be different. the switch keeps the port in the guest VLAN. Release 15. • Restricted VLAN—If the port is already authorized in a restricted VLAN and the RADIUS servers are unavailable. The access VLAN must be a secondary private VLAN.1x Port-Based Authentication Configuring IEEE 802. the switch might not assign clients to the guest VLAN if one is configured. The stack members can then check the status of RADIUS servers when reauthenticating critical ports. the switch reauthenticates all switch ports in the critical-authentication state. the switch authenticates the client and puts the critical port in the critical-authentication state in the RADIUS-configured or user-specified access VLAN. – If all the RADIUS servers are not available and the client is connected to a critical port. – If all the RADIUS servers are not available and if a client is connected to a critical port and was previously assigned to a guest VLAN. the switch puts the critical port in the critical-authentication state in the restricted VLAN. Voice VLAN—Inaccessible authentication bypass is compatible with voice VLAN.x port. Catalyst 2960 and 2960-S Switches Software Configuration Guide.0(1)SE 10-26 OL-26520-02 . and the new stack immediately sends keepalive packets to update the status of the RADIUS servers. • When a member is added to the stack. When the status of a RADIUS server changes. – If all the RADIUS servers are not available and the client is not connected to a critical port. Note Switch stacks are supported only on Catalyst 2960-S switches running the LAN base image.1x accounting—Accounting is not affected if the RADIUS servers are unavailable.1x Port-Based Authentication Feature Interactions Inaccessible authentication bypass interacts with these features: • Guest VLAN—Inaccessible authentication bypass is compatible with guest VLAN. • • • • In a switch stack: • • If the new stack master is elected.

1x authentication is enabled on a voice VLAN port. As a result. if several IP phones are connected in series. and the device MAC address appears after the first CDP message from the IP phone. you can enter the authentication event server dead action authorize voice interface configuration command to configure the critical voice VLAN feature. In multiple-hosts mode. When the ACS does not respond. This allows the phone to work independently of 802. the switch drops packets from unrecognized IP phones more than one hop away. the switch cannot determine if the device is a voice device. When multiple-hosts mode is enabled. When the switch cannot reach the configured RADIUS servers and new hosts cannot be authenticated. This feature is supported in multidomain and multi-auth host modes. the switch connects those hosts to critical ports. the critical VLAN. you can configure inaccessible authentication bypass. Catalyst 2960 and 2960-S Switches Software Configuration Guide. The IP phones learn the voice VLAN identification through CDP (Cisco devices) or through LLDP or DHCP. and granted limited authentication. If the server is unavailable. you cannot configure a port VLAN that is equal to a voice VLAN.Chapter 10 Configuring IEEE 802. the switch recognizes only the one directly connected to it.1x Critical Voice VLAN When an IP phone connected to a port is authenticated by the access control server (ACS). or critical authentication. If the RADIUS authentication server is unavailable (down) and inaccessible authentication bypass is enabled.1x Authentication with Voice VLAN Ports A voice VLAN port is a special access port associated with two VLAN identifiers: • • VVID to carry voice traffic to and from the IP phone. the connected device (the phone) is put in the configured voice VLAN for the port.0(1)SE OL-26520-02 10-27 . The IP phone uses the VVID for its voice traffic. regardless of the authorization state of the port. A new host trying to connect to the critical port is moved to a user-specified access VLAN. For data traffic. You can configure the voice VLAN for a port by entering the switchport voice vlan vlan-id interface configuration command. the command has no effect unless the device changes to multidomain or multi-auth host mode.1x authentication is enabled on a port. A voice VLAN port becomes active when there is a link. the port goes into critical authentication mode. When 802. Although you can enter the command when the switch in single-host or multi-host mode. The VVID is used to configure the IP phone connected to the port.1x Port-Based Authentication 802.1x Port-Based Authentication Understanding IEEE 802. to allow traffic to pass through on the native VLAN when the server is not available. When traffic coming from the host is tagged with the voice VLAN. PVID to carry the data traffic to and from the workstation connected to the switch through the IP phone. the switch grants the client access to the network and puts the port in the critical-authentication state in the RADIUS-configured or the user-specified access VLAN. With this release. Release 15. In single-host mode. The PVID is the native VLAN of the port. the supplicant authentication affects both the PVID and the VVID.1x authentication. When 802. additional clients can send traffic on the voice VLAN after a supplicant is authenticated on the PVID. the phone is put into the voice domain. 802. Cisco IP phones do not relay CDP messages from other devices. If the ACS is not reachable. only the IP phone is allowed on the voice VLAN. the phone cannot access the voice network and therefore cannot operate.

1x enforces a single MAC address per port (or per VLAN when MDA is configured for IP telephony).1x port becomes unauthorized. “Configuring Voice VLAN. Cisco does not recommend enabling port security when IEEE 802. While the port is unauthorized. We recommend that you use multidomain authentication (MDA) on the port to authenticate both a data device and a voice device.1x Authentication with Port Security In general.1x Authentication with MAC Authentication Bypass You can configure the switch to authorize clients based on the client MAC address (see Figure 10-2 on page 10-4) by using the MAC authentication bypass feature. the Cisco IP phone loses connectivity to the switch for up to 30 seconds. For more information about voice VLANs.1x Port-Based Authentication Configuring IEEE 802. The port can send packets to the host but cannot receive packets from the host. When the switch uses 802. it is not authorized. When you configure a port as unidirectional by using the authentication control-direction in interface configuration command.1x Port-Based Authentication When IP phones are connected to an 802.1x port and the host powers off. The port does not receive packets from or send packets to the host. For example.1x authentication on an access port on which a voice VLAN is configured and to which a Cisco IP Phone is connected. When a host that uses WoL is attached through an 802. the switch forwards traffic to unauthorized 802.1x authentication with the wake-on-LAN (WoL) feature allows dormant PCs to be powered when the switch receives a specific Ethernet frame. Note If PortFast is not enabled on the port. see Chapter 15. The port can only receive and send EAPOL packets.1x authentication with WoL.1x operations. 802. such as an IP phone. When you configure a port as bidirectional by using the authentication control-direction both interface configuration command. 802. and WoL magic packets cannot reach the host.1x is enabled. You can use this feature in environments where administrators need to connect to systems that have been powered down.Chapter 10 Understanding IEEE 802. including magic packets.1x ports.1x ports connected to devices such as printers. The host can receive packets but cannot send packets to other devices in the network.1x-enabled switch port that is in single host mode. the port changes to the spanning-tree forwarding state. you can enable this feature on 802. known as the magic packet.” 802.1x Authentication with Wake-on-LAN The 802.0(1)SE 10-28 OL-26520-02 . When the PC is powered off. the port is access-controlled in both directions. Since IEEE 802. the switch continues to block ingress traffic other than EAPOL packets. the 802. Catalyst 2960 and 2960-S Switches Software Configuration Guide. the port is forced to the bidirectional state. and the switch port is not opened. Release 15. Note If you enable 802. the switch grants the phones network access without authenticating them. port security is redundant and in some cases may interfere with expected IEEE 802.

lx port is authenticated with MAC authentication bypass. the switch assigns the port to the guest VLAN. see RFC 3580. the switch grants the client access to the network.1x supplicant. During reauthentication.1x authentication—You can enable MAC authentication bypass only if 802. Network Edge Access Topology (NEAT)MAB and NEAT are mutually exclusive. If authorization fails.1X Remote Authentication Dial In User Service (RADIUS) Usage Guidelines.1x port.1x authentication times out while waiting for an EAPOL response from the client. If reauthentication is based on the Session-Timeout RADIUS attribute (Attribute[27]) and the Termination-Action RADIUS attribute (Attribute [29]) and if the Termination-Action RADIUS attribute (Attribute [29]) action is Initialize. Voice VLAN—See the “802. the switch assigns the client to a guest VLAN if one is configured. the switch uses the MAC address as the client identity. and you cannot enable NEAT when MAB is enabled on an interface. When reauthentication occurs. After detecting a client on an 802. If the switch already authorized a port by using MAC authentication bypass and detects an 802. EAPOL history is cleared if the interface link status goes down. “802.1x Authentication with Voice VLAN Ports” section on page 10-27.” MAC authentication bypass interacts with the features: • • • • • • • • 802. and connectivity is lost during reauthentication. the switch uses the MAC authentication bypass feature to initiate reauthorization. the switch tries to authorize the client by using MAC authentication bypass. You can configure how MAB authentication is performed for clients with MAC addresses that deviate from the standard format or where the RADIUS configuration requires the user name and password to differ. See the “Configuring a MAC Authentication Bypass (MAB) Username and Password” section on page 10-58. the switch assigns the port to the guest VLAN if one is configured. If reauthentication fails.1x Port-Based Authentication If 802. the switch uses 802. Catalyst 2960 and 2960-S Switches Software Configuration Guide. The switch sends the authentication server a RADIUS-access/request frame with a username and password based on the MAC address.1x authentication is enabled on the port.1x Port-Based Authentication Understanding IEEE 802. You cannot enable MAB when NEAT is enabled on an interface.Chapter 10 Configuring IEEE 802.1x and VMPS are mutually exclusive.1x. The authentication server has a database of client MAC addresses that are allowed network access.1x authentication as the preferred reauthentication process if the previous session ended because the Termination-Action RADIUS attribute value is DEFAULT. VLAN Membership Policy Server (VMPS)—802. Guest VLAN—If a client has an invalid MAC address identity. the switch determines that the device connected to that interface is an 802. Clients that were authorized with MAC authentication bypass can be reauthenticated. The reauthentication process is the same as that for clients that were authenticated with 802.1x port. If an EAPOL packet is detected on the interface during the lifetime of the link. if one is configured. If reauthentication is successful. the switch keeps the port in the same VLAN. however. it does not work for clients that use an alternate MAC address format. If MAC authentication bypass is enabled and the 802.1x-capable supplicant and uses 802.0(1)SE OL-26520-02 10-29 . the switch waits for an Ethernet packet from the client. If authorization succeeds. Private VLAN—You can assign a client to a private VLAN. Port security—See the “802.1x Authentication with Port Security” section on page 10-28. This process works for most client devices.1x authentication times out. (the attribute value is DEFAULT). Release 15.1x authentication (not MAC authentication bypass) to authorize the interface. When the MAC authentication bypass feature is enabled on an 802. For more information about these AV pairs. the MAC authentication bypass session ends. the switch does not unauthorize the client connected to the port. Restricted VLAN—This feature is not supported when the client connected to an 802. the port remains in the previously assigned VLAN.

1x user distribution to load-balance users with the same group name across multiple different VLANs. but the VLAN mappings to the VLAN group are cleared.1x User Distribution Configuration Guidelines • • • • • • Confirm that at least one VLAN is mapped to the VLAN group. The VLANs are either supplied by the RADIUS server or configured through the switch CLI under a VLAN group name. When you clear an existing VLAN from the VLAN group name.2(55)SE and later supports filtering of verbose MAB system messages. • Note The RADIUS server can send the VLAN information in any combination of VLAN-IDs.1x user distribution tracks all the users in a particular VLAN and achieves load balancing by moving the authorized user to the least populated VLAN. Release 15. 802. Catalyst 2960 and 2960-S Switches Software Configuration Guide. If you clear the last VLAN from the VLAN group name. The 802. For more information.1x Port-Based Authentication Configuring IEEE 802. see the “Configuring 802. See the “Authentication Manager CLI Commands” section on page 10-9. the VLAN group is cleared.Chapter 10 Understanding IEEE 802. or VLAN groups.1x Port-Based Authentication For more configuration information.1x User Distribution” section on page 10-59. 802. If the VLAN group name is found. the corresponding VLANs under this VLAN group name are searched to find the least populated VLAN. see the “Authentication Manager” section on page 10-7. Configure the RADIUS server to send a VLAN group name for a user.1x User Distribution You can configure 802. You can map more than one VLAN to a VLAN group. VLAN names.0(1)SE 10-30 OL-26520-02 . You can modify the VLAN group by adding or deleting a VLAN. You can search for the selected VLAN group name among the VLAN group names that you configured by using the switch CLI. none of the authenticated ports in the VLAN are cleared. The VLAN group name can be sent as part of the response to the user. but the mappings are removed from the existing VLAN group. The multiple VLAN names can be sent as part of the response to the user. Cisco IOS Release 12. You can clear a VLAN group even when the active VLANs are mapped to the group. none of the ports or users that are in the authenticated state in any VLAN within the group are cleared. • Configure the RADIUS server to send more than one VLAN name for a user. Load balancing is achieved by moving the corresponding authorized user to that VLAN. When you clear a VLAN group.

see the “Configuring NAC Layer 2 802. After the host is authenticated. and web authentication can be the fallback method if either or both of those authentication attempts fail. which checks the antivirus condition or posture of endpoint systems or clients before granting the devices network access. see the “Authentication Manager” section on page 10-7. • • • • Configuring NAC Layer 2 802. For more information about NAC. the session ends. For more information see the “Configuring Flexible Authentication Ordering” section on page 10-65.0(1)SE OL-26520-02 10-31 . Flexible Authentication Ordering You can use flexible authentication ordering to configure the order of methods that a port uses to authenticate a new host. see the Network Admission Control Software Configuration Guide. Set the number of seconds between reauthentication attempts as the value of the Session-Timeout RADIUS attribute (Attribute[27]) and get an access policy against the client from the RADIUS server. by using the show authentication or show dot1x privileged EXEC command.1x Validation Note To use Network Admission Control. View the NAC posture token.1x Port-Based Authentication Understanding IEEE 802. Release 15. The switch supports the Network Admission Control (NAC) Layer 2 802. When open authentication is configured.1x validation. the first Tunnel Group Private ID (Attribute[81]) attribute is picked up from the list. Open1x Authentication Open1x authentication allows a device to access a port before that device is authenticated. which shows the posture of the client.1x can be the primary or secondary authentication methods. MAC authentication bypass and 802.1x Validation” section on page 10-60 and the “Configuring Periodic Re-Authentication” section on page 10-47. Configure secondary private VLANs as guest VLANs. For more configuration information. For information about configuring NAC Layer 2 802.1x validation is similar to configuring 802.1x validation.1x Port-Based Authentication Network Admission Control Layer 2 802. you can do these tasks: • • Download the Session-Timeout RADIUS attribute (Attribute[27]) and the Termination-Action RADIUS attribute (Attribute[29]) from the authentication server.1x validation. a new host can pass traffic according to the access control list (ACL) defined on the port. If the value is the DEFAULT or is not set. Catalyst 2960 and 2960-S Switches Software Configuration Guide. If the value is RADIUS-Request.1x port-based authentication except that you must configure a posture token on the RADIUS server. the reauthentication process starts.Chapter 10 Configuring IEEE 802. Set the list of VLAN number or name or VLAN group name as the value of the Tunnel Group Private ID (Attribute[81]) and the preference for the VLAN number or name or VLAN group name as the value of the Tunnel Preference (Attribute[83]). Set the action to be taken when the switch tries to reauthenticate the client by using the Termination-Action RADIUS attribute (Attribute[29]). the switch must be running the LAN base image. With NAC Layer 2 802. If you do not configure the Tunnel Preference. the policies configured on the RADIUS server are applied to that host.

A switch configured with the 802. This configuration is helpful in a scenario. the port will grant access to the host irrespective of the authentication port-control interface configuration command.1x switch supplicant: You can configure a switch to act as a supplicant to another switch by using the 802. Once the supplicant switch authenticates successfully the port mode changes from access to trunk.1x switch supplicant feature authenticates with the upstream switch for secure connectivity. whether it is a data or voice VLAN. Using Voice Aware 802.Chapter 10 Understanding IEEE 802. the switch must be running the LAN base image.1x Security” section on page 10-40.0(1)SE 10-32 OL-26520-02 . When an attempt to authenticate the data client caused a security violation in previous releases. except multiple hosts can be authenticated. Multiple-hosts mode with open authentication–Any host can access the network. MDA mode with open authentication–Only one user in the voice domain and one user in the data domain are allowed.1x Supplicant and Authenticator Switches with Network Edge Access Topology (NEAT) The Network Edge Access Topology (NEAT) feature extends identity to areas outside the wiring closet (such as conference rooms).1x Port-Based Authentication You can configure open authentication with these scenarios: • • • • Single-host mode with open authentication–Only one user is allowed network access before and after authentication. 802.1x Security Note To use voice aware IEEE 802.1x Port-Based Authentication Configuring IEEE 802. where. You can use this feature where a PC is connected to the IP phone. it becomes the native VLAN for the trunk port after successful authentication. see the “Configuring Voice Aware 802. the entire port shut down. This allows any type of device to authenticate on the port.1x authentication. Note If open authentication is configured. • 802. This means that if you use the authentication open interface configuration command. a switch is outside a wiring closet and is connected to an upstream switch through a trunk port. A security violation found on the data VLAN shuts down only the data VLAN. You use the voice aware 802. for example. Release 15. • Catalyst 2960 and 2960-S Switches Software Configuration Guide. Multiple-authentication mode with open authentication–Similar to MDA. The traffic on the voice VLAN continues without interruption. For more information see the “Configuring the Host Mode” section on page 10-45. it takes precedence over other authentication controls.1x security. If the access VLAN is configured on the authenticator switch.1x supplicant feature. For information on configuring voice aware 802.1x security feature to configure the switch to disable only the VLAN on which a security violation occurs. resulting in a complete loss of connectivity.

as shown in Figure 10-6. This is the default behavior. • Host Authorization: Ensures that only traffic from authorized hosts (connecting to the switch with supplicant) is allowed on the network. allowing user traffic from multiple VLANs coming from supplicant switches.0(1)SE OL-26520-02 10-33 . You can enable MDA or multiauth mode on the authenticator switch interface that connects to one more supplicant switches.) Authenticator and Supplicant Switch using CISP • Figure 10-6 2 3 4 1 5 205718 1 3 5 Workstations (clients) Authenticator switch Trunk port 2 4 Supplicant switch (outside wiring closet) Access control server (ACS) Catalyst 2960 and 2960-S Switches Software Configuration Guide. Multihost mode is not supported on the authenticator switch interface. Configure the cisco-av-pair as device-traffic-class=switch at the ACS. the supplicant port opens. Release 15.1x Port-Based Authentication In the default state. If authentication fails.1x Port-Based Authentication Understanding IEEE 802. Entering the no dot1x supplicant controlled transient global configuration command opens the supplicant port during the authentication period.Chapter 10 Configuring IEEE 802. Auto enablement: Automatically enables trunk configuration on the authenticator switch. you can control traffic exiting the supplicant port during the authentication period.0(1)SE. We strongly recommend using the dot1x supplicant controlled transient command on a supplicant switch when BPDU guard is enabled on the authenticator switch port with the spanning-tree bpduguard enable interface onfiguration command. the authenticator port could be error-disabled if it receives a Spanning Tree Protocol (STP) bridge protocol data unit (BPDU) packets before the supplicant switch has authenticated. entering the dot1x supplicant controlled transient command does not prevent the BPDU violation. Use the dot1x supplicant force-multicast global configuration command on the supplicant switch for Network Edge Access Topology (NEAT) to work in all host modes. Entering the dot1x supplicant controlled transient global configuration command temporarily blocks the supplicant port during authentication to ensure that the authenticator port does not shut down before authentication completes. Beginning with Cisco IOS Release 15. Note If you globally enable BPDU guard on the authenticator switch by using the spanning-tree portfast bpduguard default global configuration command. when you connect a supplicant switch to an authenticator switch that has BPDU guard enabled. The switches use Client Information Signalling Protocol (CISP) to send the MAC addresses connecting to the supplicant switch to the authenticator switch. (You can configure this under the group or the user settings.

0(1)SE 10-34 OL-26520-02 . the port becomes unauthorized. This ID is used for all reporting purposes. Only IP standard and IP extended port ACLs from the ACS support the Filter-Id attribute. This allows you to remove unsupported configurations on the authenticator switch port and to change the port mode from access to trunk.1x authentication with ACLs and the Filter-Id attribute. • • For more information. it sends ACL attributes based on the user identity to the switch.1x-authenticated user. The session ID appears with all per-session syslog messages. The switch applies the attributes to the port for the duration of the user session. see the “Configuring an Authenticator and a Supplicant Switch with NEAT” section on page 10-61. • • ACLs that you configure ACLs from the Access Control Server (ACS) An IEEE 802. and the switch removes the ACL from the port.1x trunk encapsulation and the access VLAN if any would be converted to a native trunk VLAN. and the port returns to the unauthorized state. it takes precedence over a user-configured ACL.1x Port-Based Authentication Configuring IEEE 802. Common Session ID Authentication manager uses a single session ID (referred to as a common session ID) for a client no matter which authentication method is used.1x Port-Based Authentication Guidelines • You can configure NEAT ports with the same configurations as the other authentication ports. The Filter-id attribute can also specify the direction (inbound or outbound) and a user or a group to which the user belongs. The switch supports both IP standard and IP extended port access control lists (ACLs) applied to ingress ports. If the Filter-Id attribute is not defined on the switch. For information. Using IEEE 802. • • • The Filter-Id attribute for the user takes precedence over that for the group.1x port in single-host mode uses ACLs from the ACS to provide different levels of service to an IEEE 802. VSA does not change any of the port configurations on the supplicant To change the host mode and the apply a standard port configuration on the authenticator switch port. the switch must be running the LAN base image. authentication fails. only the last attribute is applied. you can also use Auto Smartports user-defined macros. authentication fails. When the RADIUS server authenticates this type of user and port.Chapter 10 Understanding IEEE 802. Catalyst 2960 and 2960-S Switches Software Configuration Guide. If a Filter-Id attribute from the ACS specifies an ACL that is already configure. or a link fails. (device-traffic-class=switch). If the RADIUS server sends more than one Filter-Id attribute.1x Authentication with ACLs and the RADIUS Filter-Id Attribute Note To use IEEE 802. such as the show commands and MIBs. instead of the switch VSA. The VSA changes the authenticator switch port mode from access to trunk and enables 802. the port mode is changed from access to trunk based on the switch vendor-specific attributes (VSAs). It specifies the name or number of an ACL. If the session is over. Release 15. When the supplicant switch authenticates. see the AutoSmartports Configuration Guide.

page 10-36 802.1x Authentication Configuration. page 10-42 (optional) Configuring 802.1x Port-Based Authentication Configuring 802. page 10-44 (required) Configuring the Host Mode.0(1)SE OL-26520-02 10-35 . page 10-52 (optional) Enabling MAC Move. page 10-50 (optional) Enabling MAC Replace. and other report-analyzing applications to identify the client.1x Accounting. page 10-53 (optional) Catalyst 2960 and 2960-S Switches Software Configuration Guide.1x Authentication Configuration Guidelines.0000. page 10-45 (optional) Configuring Periodic Re-Authentication. page 10-37 Configuring 802.0203) on Interface Fa4/0/4 AuditSessionID 160000050000000B288508E5 The session ID is used by the NAD.0203) on Interface Fa4/0/4 AuditSessionID 160000050000000B288508E5 1w0d: %MAB-5-SUCCESS: Authentication successful for client (0000.1x Authentication The session ID includes: • • • The IP address of the Network Access Device (NAD) A monotonically increasing unique 32 bit integer The session start time stamp (a 32 bit integer) This example shows how the session ID appears in the output of the show authentication command.1x Readiness Check. The session ID in this example is 160000050000000B288508E5: Switch# show authentication sessions Interface Fa4/0/4 MAC Address 0000.1x Violation Modes. The ID appears automatically. Configuring 802. the AAA server. page 10-48 (optional) Setting the Switch-to-Client Frame-Retransmission Number.1x Authentication. page 10-39 (optional) Configuring Voice Aware 802. page 10-50 (optional) Configuring 802.0000.1x Security. The session ID in this example is also160000050000000B288508E5: 1w0d: %AUTHMGR-5-START: Starting 'mab' for client (0000.0000. Release 15. page 10-48 (optional) Changing the Switch-to-Client Retransmission Time. page 10-51 (optional) Configuring a Guest VLAN. page 10-49 (optional) Setting the Re-Authentication Number.0203) on Interface Fa4/0/4 AuditSessionID 160000050000000B288508E5 1w0d: %AUTHMGR-7-RESULT: Authentication result 'success' from 'mab' for client (0000. page 10-43 (optional) Configuring the Switch-to-RADIUS-Server Communication.1x Authentication • • • • • • • • • • • • • • • • • • Default 802.Chapter 10 Configuring IEEE 802. page 10-47 (optional) Manually Re-Authenticating a Client Connected to a Port. page 10-48 (optional) Changing the Quiet Period.0000.0203 Method mab Domain DATA Status Authz Success Session ID 160000050000000B288508E5 This is an example of how the session ID appears in the syslog output. page 10-40 (optional) Configuring 802. No configuration is required.

page 10-61 (optional) Configuring 802. • • • IP address UDP authentication port Key None specified.1x enable state Per-port 802. 3600 seconds. Disabled.1x Authentication Configuration to the Default Values. 30 seconds (number of seconds that the switch should wait for a response to an EAP request/identity frame from the client before resending the request). page 10-55 (optional) Configuring 802.1x-based authentication of the client. page 10-67 (optional) Default 802.1x enable state Default Setting Disabled.1x Authentication Configuration Table 10-4 Default 802. None specified. page 10-65 (optional) Disabling 802.Chapter 10 Configuring 802. page 10-57 (optional) Configuring MAC Authentication Bypass. 1812. Release 15.1x Port-Based Authentication • • • • • • • • • • Configuring a Restricted VLAN. page 10-53 (optional) Configuring Inaccessible Authentication Bypass and Critical Voice VLAN. page 10-58 (optional) Configuring NAC Layer 2 802. Bidirectional control.1x Authentication Configuration Feature Switch 802. AAA RADIUS server • • • Disabled.1x Validation.1x Authentication with Wake-on-LAN.1x Authentication Configuring IEEE 802. Host mode Control direction Periodic reauthentication Number of seconds between reauthentication attempts Reauthentication number Quiet period Retransmission time Maximum retransmission number Single-host mode.1x Authentication on the Port. 60 seconds (number of seconds that the switch remains in the quiet state following a failed authentication exchange with the client).1x Authentication with Downloadable ACLs and Redirect URLs. 2 times (number of times that the switch restarts the authentication process before the port changes to the unauthorized state). 2 times (number of times that the switch will send an EAP-request/identity frame before restarting the authentication process). The port sends and receives normal traffic without 802. page 10-63 (optional) Configuring Flexible Authentication Ordering. Disabled (force-authorized). page 10-67 (optional) Resetting the 802. Catalyst 2960 and 2960-S Switches Software Configuration Guide.0(1)SE 10-36 OL-26520-02 . page 10-60 (optional) Configuring an Authenticator and a Supplicant Switch with NEAT.

) You can change this timeout period by using the authentication timer server interface configuration command.1x-enabled port is assigned changes. an error message appears. Release 15.1x Authentication Table 10-4 Default 802.1x protocol is supported on Layer 2 static-access ports and voice VLAN ports. the port becomes unauthorized. None specified. this change occurs if a port is assigned to a RADIUS server-assigned VLAN and is then assigned to a different VLAN after reauthentication. the amount of time the switch waits for a response before resending the request to the client. None specified.1x Authentication. Disabled. page 10-39 Maximum Number of Allowed Devices Per Port. For example. page 10-39 802.1x Authentication Configuration Guidelines • • • • 802.1x Port-Based Authentication Configuring 802. or removed.1x-enabled port to trunk.1x Authentication Configuration (continued) Feature Client timeout period Default Setting 30 seconds (when relaying a request from the authentication server to the client. the amount of time the switch waits for a reply before resending the response to the server.1x authentication is enabled.1x authentication is not enabled. an error message appears. Guest VLAN. Disabled. If the VLAN to which an 802. Authentication server timeout period Inactivity timeout Guest VLAN Inaccessible authentication bypass Restricted VLAN Authenticator (switch) mode MAC authentication bypass Voice-aware security Disabled. page 10-37 VLAN Assignment. • The IEEE 802. If the VLAN to which an 802. For example. and the port mode is not changed. and 802.0(1)SE OL-26520-02 10-37 .Chapter 10 Configuring IEEE 802. Catalyst 2960 and 2960-S Switches Software Configuration Guide. None specified.1x port is assigned to shut down. Disabled 802. and Inaccessible Authentication Bypass. but it is not supported on these port types: – Trunk port—If you try to enable 802. disabled.1x Authentication • • When IEEE 802. ports are authenticated before any other Layer 2 feature is enabled. If you try to change the mode of an 802.1x authentication on a trunk port. Restricted VLAN. this change is transparent and does not affect the switch. the port is unauthorized after the access VLAN to which a port is assigned shuts down or is removed.) 30 seconds (when relaying a response from the client to the authentication server. page 10-38 MAC Authentication Bypass.

The amount to decrease the settings depends on the connected 802. remove the EtherChannel configuration from the interfaces on which 802.1x authentication on a port that is a SPAN or RSPAN destination port. • Before globally enabling 802.1x client type. – If the Windows XP client is configured for DHCP and has an IP address from the DHCP server. and the port mode is not changed. switch changes the port state to the critical authentication state and remains in the restricted VLAN.1x authentication is not enabled. and 802.1x port in single-host mode and multihosts mode. – EtherChannel port—Do not configure a port that is an active or a not-yet-active member of an EtherChannel as an 802.1x authentication on a SPAN or RSPAN source port. Release 15. dynamic ports. and 802. However. – If the client is running Windows XP and the port to which the client is connected is in the • critical-authentication state. You can enable 802.1x authentication on a dynamic port. The guest VLAN feature is not supported on trunk ports.1x-enabled port to dynamic VLAN assignment.1x-enabled port to dynamic. and 802. When configuring the inaccessible authentication bypass feature.1x authentication is enabled on a port. – You can configure the inaccessible authentication bypass feature and the restricted VLAN on an 802. After you configure a guest VLAN for an 802.1x authentication on a switch by entering the dot1x system-auth-control global configuration command.1x authentication process (authentication timer inactivity and authentication timer reauthentication interface configuration commands).1x authentication is disabled until the port is removed as a SPAN or RSPAN destination port.0(1)SE 10-38 OL-26520-02 .1x authentication with VLAN assignment feature is not supported on trunk ports. If you try to change an 802.1x Authentication Configuring IEEE 802. an error message appears.2(55)SE and later supports filtering of system messages related to 802. You can change the settings for restarting the 802.1x port. or with dynamic-access port assignment through a VMPS. Cisco IOS Release 12. an error message appears. receiving an EAP-Success message on a critical port might not re-initiate the DHCP configuration process. Restricted VLAN. Catalyst 2960 and 2960-S Switches Software Configuration Guide. – Switched Port Analyzer (SPAN) and Remote SPAN (RSPAN) destination ports—You can enable 802.1x Port-Based Authentication – Dynamic ports—A port in dynamic mode can negotiate with its neighbor to become a trunk port.1x authentication on an EtherChannel port. 802.1x guest VLAN. an error message appears. follow these guidelines: – The feature is supported on 802. If the switch tries to reauthenticate a critical port in a restricted VLAN and all the RADIUS servers are unavailable. If you try to enable 802. • VLAN Assignment. and the VLAN configuration is not changed. If you try to change the mode of an 802. See the “Authentication Manager CLI Commands” section on page 10-9. an error message appears. Decrease the settings for the 802. and Inaccessible Authentication Bypass • • • • When 802.1x authentication is not enabled.1x authentication on a dynamic-access (VLAN Query Protocol [VQP]) port. Guest VLAN.1x authentication is not enabled.1x port to which a DHCP client is connected.1x authentication and EtherChannel are configured.1x authentication. The 802. If you try to enable 802. an error message appears. – Dynamic-access ports—If you try to enable 802. you might need to get a host IP address from a DHCP server.Chapter 10 Configuring 802. it is supported only on access ports.1x port. you cannot configure a port VLAN that is equal to a voice VLAN.1x authentication process on the switch before the DHCP process on the client times out and tries to get a host IP address from the DHCP server. You can configure any VLAN except an RSPAN VLAN or a voice VLAN as an 802. Windows XP might report that the interface is not authenticated.

1x Authentication • You can configure any VLAN except an RSPAN VLAN or a voice VLAN as an 802.1x capability.1x-capable. the client is not 802. If you disable MAC authentication bypass from a port after the port has been authorized with its MAC address. When you configure the dot1x test eapol-capable command on an 802.1x readiness check monitors 802. If you use the dot1x test eapol-capable privileged EXEC command without specifying an interface.Chapter 10 Configuring IEEE 802. No syslog message is generated.1x Authentication” section on page 10-37.1x readiness check is allowed on all ports that can be configured for 802. In multidomain authentication (MDA) mode. If the port is in the unauthorized state and the client MAC address is not the authentication-server database. see the “802. A syslog message is generated if the client responds within the timeout period. only one device is allowed on the access VLAN. one device is allowed for the access VLAN.1x Port-Based Authentication Configuring 802.1x. The readiness check is not available on a port that is configured as dot1x force-unauthorized. The 802. However. but an unlimited number of non-802. • • Configuring 802.1x authentication guidelines. The restricted VLAN feature is not supported on trunk ports. and the link comes up. Catalyst 2960 and 2960-S Switches Software Configuration Guide. The range is 1to 65535 seconds. An unlimited number of devices are allowed on the voice VLAN. the port state is not affected. You can configure a timeout period for hosts that are connected by MAC authentication bypass but are inactive.1x supplicant is allowed on the port. In multiple-host mode. the port queries the connected client about its 802. it is supported only on access ports. the switch can use MAC authentication bypass to reauthorize the port. the MAC authentication bypass guidelines are the same as the 802. all the ports on the switch stack are tested. When the client responds with a notification packet. it is 802. an unlimited number of Cisco IP phones can send and receive traffic through the voice VLAN.1x-capable.1x is enabled on the switch. the port remains in the unauthorized state.1x-enabled port. • • • • Maximum Number of Allowed Devices Per Port This is the maximum number of devices allowed on an 802. If the client does not respond to the query. If the port is also configured with a voice VLAN.1x-capable.0(1)SE OL-26520-02 10-39 . only one 802. Follow these guidelines to enable the readiness check on the switch: • • • The readiness check is typically used before 802. For more information.1x restricted VLAN. if the client MAC address is added to the database.1x hosts are allowed on the access VLAN.1x Readiness Check The 802. Release 15. and one IP phone is allowed for the voice VLAN. the port remains in this state until reauthorization occurs.1x-enabled port: • In single-host mode.1x. MAC Authentication Bypass • Unless otherwise stated. You can use this feature to determine if the devices connected to the switch ports are 802.1x activity on all the switch ports and displays information about the devices connected to the ports that support 802. If the port is in the authorized state.

The range is from 1 to 65535 seconds. all interfaces on the switch are tested.1x-configured ports in the switch. whether it is a data or voice VLAN. (Optional) Configure the timeout used to wait for EAPOL response.1x readiness check on the switch: Command Step 1 Purpose Enable the 802.1x readiness.1x-capable: Switch# dot1x test eapol-capable interface gigabitethernet1/0/13 DOT1X_PORT_EAPOL_CAPABLE:DOT1X: MAC 00-01-02-4b-f1-a3 on gigabitethernet1/0/13 is EAPOL capable Configuring Voice Aware 802. Step 1 Step 2 Step 3 Step 4 configure terminal dot1x test timeout timeout end show running-config (Optional) Enter global configuration mode. a PC that is connected to an IP phone). The traffic on the voice VLAN flows through the switch without interruption.1x Port-Based Authentication • The readiness check can be sent on a port that handles multiple hosts (for example.1x voice security on the switch: • You enable voice aware 802. You can use this feature in IP phone deployments where a PC is connected to the IP phone.1x Authentication Configuring IEEE 802. A syslog message is generated for each of the clients that respond to the readiness check within the timer period.1x security by entering the errdisable detect cause security-violation shutdown vlan global configuration command. You disable voice aware 802. (Optional) Return to privileged EXEC mode.1x security feature on the switch to disable only the VLAN on which a security violation occurs. Note dot1x test eapol-capable [interface interface-id] If you omit the optional interface keyword. Note If you do not include the shutdown vlan keywords. You use the voice aware 802. Beginning in privileged EXEC mode. This example shows how to enable a readiness check on a switch to query a port. the switch must be running the LAN base image.1x authentication. This command applies to all 802. It also shows the response received from the queried port verifying that the device connected to it is 802. The default is 10 seconds.1x Security Note To use voice aware IEEE 802. follow these steps to enable the 802.1x security by entering the no version of this command.1x readiness check on the switch. the entire port is shut down when it enters the error-disabled state.Chapter 10 Configuring 802. (Optional) Verify your modified timeout values.0(1)SE 10-40 OL-26520-02 . Release 15. Follow these guidelines to configure voice aware 802. A security violation found on the data VLAN results in the shutdown of only the data VLAN. Catalyst 2960 and 2960-S Switches Software Configuration Guide. (Optional) For interface-id specify the port on which to check for 802.

If you do not specify a range. the port is automatically re-enabled. If error-disabled recovery is not configured for the port. • Beginning in privileged EXEC mode. Step 5 shutdown no-shutdown end show errdisable detect copy running-config startup-config (Optional) Re-enable an error-disabled VLAN. Release 15. Verify your entries. Catalyst 2960 and 2960-S Switches Software Configuration Guide. the entire port enters the error-disabled state and shuts down. all VLANs are re-enabled. Return to privileged EXEC mode. If vlan-list is not specified. follow these steps to enable voice aware 802. Step 3 Step 4 (Optional) Enable automatic per-VLAN error recovery. Switch# clear errdisable interface gigabitethernet4/0/2 vlan You can verify your settings by entering the show errdisable detect privileged EXEC command.1x Authentication • If you use the errdisable recovery cause security-violation global configuration command to configure error-disabled recovery.0(1)SE OL-26520-02 10-41 . and clear all error-disable indications. Note configure terminal errdisable detect cause security-violation shutdown vlan errdisable recovery cause security-violation clear errdisable interface interface-id vlan [vlan-list] If the shutdown vlan keywords are not included. all VLANs on the port are enabled.Chapter 10 Configuring IEEE 802. You can re-enable individual VLANs by using the clear errdisable interface interface-id vlan [vlan-list] privileged EXEC command.1x security: Command Step 1 Step 2 Purpose Enter global configuration mode. you re-enable it by using the shutdown and no-shutdown interface configuration commands. (Optional) Reenable individual VLANs that have been error disabled. • • For interface-id specify the port on which to reenable individual VLANs.1x Port-Based Authentication Configuring 802. Step 6 Step 7 Step 8 This example shows how to configure the switch to shut down any VLAN on which a security violation error occurs: Switch(config)# errdisable detect cause security-violation shutdown vlan This example shows how to re-enable all VLANs that were error disabled on port Gigabit Ethernet 40/2. (Optional) For vlan-list specify a list of VLANs to be re-enabled. (Optional) Save your entries in the configuration file. Shut down any VLAN on which a security violation error occurs.

0(1)SE 10-42 OL-26520-02 . Configure the violation mode. Verify your entries. use the default keyword followed by the method that is to be used in default situations.1x Port-Based Authentication Configuring 802. or discards packets from a new device when: • • a device connects to an 802.1x authentication method list. follow these steps to configure the security violation actions on the switch: Command Step 1 Step 2 Step 3 Purpose Enter global configuration mode. Enable AAA. Step 4 Step 5 Step 6 interface interface-id switchport mode access authentication violation {shutdown | restrict | protect | replace} Specify the port connected to the client that is to be enabled for 802. the switch must be running the LAN base image. For method1.1x Violation Modes Note To configure violation modes. replace–Removes the current session and authenticates with the new host. (Optional) Save your entries in the configuration file. generates a syslog error.Chapter 10 Configuring 802. restrict–Generate a syslog error. You can configure an 802. Set the port to access mode. protect–Drop packets from any new device that sends traffic to the port. The default method list is automatically applied to all ports. and enter interface configuration mode. Create an 802. To create a default list to use when a named list is not specified in the authentication command.1x port so that it shuts down. The keywords have these meanings: • • • • shutdown–Error disable the port. enter the group radius keywords to use the list of all RADIUS servers for authentication.1x-enabled port the maximum number of allowed about devices have been authenticated on the port Beginning in privileged EXEC mode. only the group radius keywords are supported.1x authentication. Step 7 Step 8 Step 9 end show authentication copy running-config startup-config Return to privileged EXEC mode. Release 15. Note configure terminal aaa new-model aaa authentication dot1x {default} method1 Though other keywords are visible in the command-line help string.1x Authentication Configuring IEEE 802. Catalyst 2960 and 2960-S Switches Software Configuration Guide.

The switch sends a start message to an accounting server. The default method list is automatically applied to all ports.1x Port-Based Authentication Configuring 802. follow these steps to configure 802. Beginning in privileged EXEC mode. as necessary. Specify the port connected to the client to enable for 802.1x AAA process: Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 A user connects to a port on the switch. Catalyst 2960 and 2960-S Switches Software Configuration Guide. This is the 802. such as VLAN assignment. (Optional) Specify the authentication and encryption key used between the switch and the RADIUS daemon running on the RADIUS server. (Optional) Specify the IP address of the RADIUS server. To create a default list to use when a named list is not specified in the authentication command.1x port-based authentication. Release 15. Enable AAA. only the group radius keywords are supported. For method1. VLAN assignment is enabled.1x authentication globally on the switch. you must enable authentication. To allow VLAN assignment.1x authentication method list.1x port-based authentication: Command Step 1 Step 2 Step 3 Purpose Enter global configuration mode.1x Authentication To configure 802. The user disconnects from the port. The switch sends a stop message to the accounting server. (Optional) Configure the switch to use user-RADIUS authorization for all network-related service requests. as appropriate. and enter interface configuration mode. authorization.0(1)SE OL-26520-02 10-43 . Note configure terminal aaa new-model aaa authentication dot1x {default} method1 Though other keywords are visible in the command-line help string. and accounting (AAA) and specify the authentication method list. enter the group radius keywords to use the list of all RADIUS servers for authentication. The switch sends an interim accounting update to the accounting server. Step 4 Step 5 Step 6 Step 7 Step 8 dot1x system-auth-control aaa authorization network {default} group radius radius-server host ip-address radius-server key string interface interface-id Enable 802. that is based on the result of reauthentication. use the default keyword followed by the method to use in default situations.1x authentication. based on the RADIUS server configuration. you must enable AAA authorization to configure the switch for all network-related service requests. A method list describes the sequence and authentication method to be queried to authenticate a user. Create an 802. Reauthentication is performed.Chapter 10 Configuring IEEE 802. Authentication is performed.1x Authentication Configuring 802.

Beginning in privileged EXEC mode.1x authentication on the port.0(1)SE 10-44 OL-26520-02 . ip-address} auth-port port-number key For hostname | ip-address. configure terminal radius-server host {hostname | Configure the RADIUS server parameters. Enable 802. Command Step 1 Step 2 Purpose Enter global configuration mode. which enables RADIUS requests to be sent to multiple UDP ports on a server at the same IP address. do not enclose the key in quotation marks unless the quotation marks are part of the key. The key is a text string that must match the encryption key used on the RADIUS server. re-enter this command. but spaces within and at the end of the key are used. Verify your entries. specify the hostname or IP address of the string remote RADIUS server. hostname and specific UDP port numbers.1x Authentication Configuration Guidelines” section on page 10-37. The combination of the IP address and the UDP port number creates a unique identifier.1x Authentication Configuring IEEE 802. Configuring the Switch-to-RADIUS-Server Communication RADIUS security servers are identified by their hostname or IP address. For auth-port port-number. The range is 0 to 65536. follow these steps to configure the RADIUS server parameters on the switch. see the “802. This procedure is required. or IP address and specific UDP port numbers. The RADIUS host entries are tried in the order in which they were configured. If you use spaces in the key. authentication—the second host entry configured acts as the fail-over backup to the first one. Release 15. Note Always configure the key as the last item in the radius-server host command syntax because leading spaces are ignored. switchport mode access authentication port-control auto Step 11 Step 12 Step 13 Step 14 dot1x pae authenticator end show authentication copy running-config startup-config Set the interface Port Access Entity to act only as an authenticator and ignore messages meant for a supplicant. specify the authentication and encryption key used between the switch and the RADIUS daemon running on the RADIUS server. Step 3 end Return to privileged EXEC mode. For key string. This key must match the encryption used on the RADIUS daemon.1x Port-Based Authentication Command Step 9 Step 10 Purpose (Optional) Set the port to access mode only if you configured the RADIUS server in Step 6 and Step 7. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Return to privileged EXEC mode.Chapter 10 Configuring 802. If two different host entries on the same RADIUS server are configured for the same service—for example. specify the UDP destination port for authentication requests. For feature interaction information. If you want to use multiple RADIUS servers. (Optional) Save your entries in the configuration file. The default is 1812.

This procedure is optional. and encryption key values for all RADIUS servers by using the radius-server host global configuration command.46 as the RADIUS server. show running-config copy running-config startup-config To clear the specified RADIUS server.1x-authorized port that has the authentication port-control interface configuration command set to auto.1x Authentication Command Step 4 Step 5 Purpose Verify your entries.39. retransmission.46 auth-port 1612 key rad123 You can globally configure the timeout. see the RADIUS server documentation. see the “Configuring Settings for All RADIUS Servers” section on page 9-36. You also need to configure some settings on the RADIUS server. (Optional) Save your entries in the configuration file. and enter interface configuration mode. Use the multi-domain keyword to configure multidomain authentication (MDA) to enable authentication of both a host and a voice device. These settings include the IP address of the switch and the key string to be shared by both the server and the switch. Configure the network access server to recognize and use vendor-specific attributes (VSAs). Specify the port to which multiple hosts are indirectly attached. Configuring the Host Mode Beginning in privileged EXEC mode. to use port 1612 as the authorization port.l20. and to set the encryption key to rad123. use the no radius-server host {hostname | ip-address} global configuration command. Release 15. such as an IP phone (Cisco or non-Cisco) on the same switch port. follow these steps to allow a single host (client) or multiple hosts on an 802.39. This example shows how to specify the server with IP address 172. matching the key on the RADIUS server: Switch(config)# radius-server host 172. For more information.20.Chapter 10 Configuring IEEE 802. Command Step 1 Step 2 Step 3 Purpose Enter global configuration mode. configure terminal radius-server vsa send authentication interface interface-id Catalyst 2960 and 2960-S Switches Software Configuration Guide. use the radius-server timeout. radius-server retransmit and the radius-server key global configuration commands. For more information.0(1)SE OL-26520-02 10-45 . If you want to configure these options on a per-server basis.1x Port-Based Authentication Configuring 802.

Each host is individually authenticated. multi-host–Allow multiple hosts on an 802. Return to privileged EXEC mode.Chapter 10 Configuring 802. see Chapter 15. • • Note • Make sure that the authentication port-control interface configuration command set is set to auto for the specified interface.1x-authorized port after a single host has been authenticated. Note The multi-auth keyword is only available with the authentication host-mode command. Release 15. Step 5 Step 6 Step 7 Step 8 switchport voice vlan vlan-id end show authentication interface interface-id copy running-config startup-config (Optional) Configure the voice VLAN. (Optional) Save your entries in the configuration file. use the no authentication host-mode interface configuration command. “Configuring Voice VLAN.0(1)SE 10-46 OL-26520-02 .1x-authorized port. multi-domain–Allow both a host and a voice device. You must configure the voice VLAN for the IP phone when the host mode is set to multi-domain. Verify your entries.1x-authorized port. such as an IP phone (Cisco or non-Cisco).” single-host–Allow a single host (client) on an 802. This example shows how to enable 802.1x Authentication Configuring IEEE 802. To disable multiple hosts on the port. For more information. to be authenticated on an 802.1x authentication and to allow multiple hosts: Switch(config)# interface gigabitethernet2/0/1 Switch(config-if)# authentication port-control auto Switch(config-if)# authentication host-mode multi-host Switch(config-if)# end This example shows how to enable MDA and to allow both a host and a voice device on the port: Switch(config)# interface gigabitethernet2/0/1 Switch(config-if)# authentication port-control auto Switch(config-if)# authentication host-mode multi-domain Switch(config-if)# switchport voice vlan 101 Switch(config-if)# end Catalyst 2960 and 2960-S Switches Software Configuration Guide.1x Port-Based Authentication Command Step 4 Purpose authentication host-mode [multi-auth | The keywords have these meanings: multi-domain | multi-host | • multi-auth–Allow one client on the voice VLAN and multiple single-host] authenticated clients on the data VLAN.

1x client reauthentication and specify how often it occurs. Beginning in privileged EXEC mode. use the no authentication periodic interface configuration command. follow these steps to enable periodic reauthentication of the client and to configure the number of seconds between reauthentication attempts. If you do not specify a time period before enabling reauthentication. (Optional) Save your entries in the configuration file. Step 4 authentication timer {{[inactivity | reauthenticate]} {restart value}} Set the number of seconds between reauthentication attempts. Enable periodic reauthentication of the client. Release 15. This procedure is optional. the number of seconds between attempts is 3600. Verify your entries.Chapter 10 Configuring IEEE 802. which is disabled by default.1x Authentication Configuring Periodic Re-Authentication You can enable periodic 802. enter the authentication timer reauthenticate command.0(1)SE OL-26520-02 10-47 . use the no authentication timer interface configuration command. The authentication timer keywords have these meanings: • • • inactivity—Interval in seconds after which if there is no activity from the client then it is unauthorized reauthenticate—Time in seconds after which an automatic reauthentication attempt is be initiated restart value—Interval in seconds after which an attempt is made to authenticate an unauthorized port This command affects the behavior of the switch only if periodic reauthentication is enabled. and enter interface configuration mode. To change the value of the reauthentication timer or to have the switch use a RADIUS-provided session timeout. Note configure terminal interface interface-id authentication periodic The default value is 3600 seconds.1x Port-Based Authentication Configuring 802. This example shows how to enable periodic reauthentication and set the number of seconds between reauthentication attempts to 4000: Switch(config-if)# authentication periodic Switch(config-if)# authentication timer reauthenticate 4000 Catalyst 2960 and 2960-S Switches Software Configuration Guide. Step 5 Step 6 Step 7 end show authentication interface interface-id copy running-config startup-config Return to privileged EXEC mode. To disable periodic reauthentication. To return to the default number of seconds between reauthentication attempts. Command Step 1 Step 2 Step 3 Purpose Enter global configuration mode. Specify the port to be configured.

the switch remains idle for a set period of time and then tries again.Chapter 10 Configuring 802. You can provide a faster response time to the user by entering a number smaller than the default. If the switch does not receive this response. Catalyst 2960 and 2960-S Switches Software Configuration Guide. use the no authentication timer inactivity interface configuration command. This example shows how to set the quiet time on the switch to 30 seconds: Switch(config-if)# authentication timer inactivity 30 Changing the Switch-to-Client Retransmission Time The client responds to the EAP-request/identity frame from the switch with an EAP-response/identity frame. The range is 1 to 65535 seconds. it waits a set period of time (known as the retransmission time) and then resends the frame.1x Port-Based Authentication Manually Re-Authenticating a Client Connected to a Port You can manually reauthenticate the client connected to a specific port at any time by entering the dot1x reauthenticate interface interface-id privileged EXEC command. Specify the port to be configured. This step is optional. configure terminal interface interface-id authentication timer inactivity seconds Set the number of seconds that the switch remains in the quiet state after a failed authentication exchange with the client. Beginning in privileged EXEC mode. Verify your entries. see the “Configuring Periodic Re-Authentication” section on page 10-47. This example shows how to manually reauthenticate the client connected to a port: Switch# dot1x reauthenticate interface gigabitethernet2/0/1 Changing the Quiet Period When the switch cannot authenticate the client. The authentication timer inactivity interface configuration command controls the idle period. the default is 60. end show authentication interface interface-id copy running-config startup-config Return to privileged EXEC mode. Release 15. If you want to enable or disable periodic reauthentication. Step 4 Step 5 Step 6 To return to the default quiet time. Note You should change the default value of this command only to adjust for unusual circumstances such as unreliable links or specific behavioral problems with certain clients and authentication servers. follow these steps to change the quiet period. This procedure is optional. Command Step 1 Step 2 Step 3 Purpose Enter global configuration mode.1x Authentication Configuring IEEE 802.0(1)SE 10-48 OL-26520-02 . (Optional) Save your entries in the configuration file. A failed client authentication might occur because the client provided an invalid password. and enter interface configuration mode.

and enter interface configuration mode. This procedure is optional. Command Step 1 Step 2 Step 3 Purpose Enter global configuration mode. Beginning in privileged EXEC mode. This example shows how to set 60 as the number of seconds that the switch waits for a response to an EAP-request/identity frame from the client before resending the request: Switch(config-if)# authentication timer reauthenticate 60 Setting the Switch-to-Client Frame-Retransmission Number You can change the number of times that the switch sends an EAP-request/identity frame (assuming no response is received) to the client before restarting the authentication process. Set the number of seconds that the switch waits for a response to an EAP-request/identity frame from the client before resending the request. configure terminal interface interface-id dot1x max-req count Step 4 Step 5 Step 6 end show authentication interface interface-id copy running-config startup-config Catalyst 2960 and 2960-S Switches Software Configuration Guide. The range is 1 to 65535 seconds.1x Port-Based Authentication Configuring 802. Verify your entries. use the no authentication timer reauthenticate interface configuration command.1x Authentication Beginning in privileged EXEC mode. Specify the port to configure. The range is 1 to 10.0(1)SE OL-26520-02 10-49 . Return to privileged EXEC mode. follow these steps to change the amount of time that the switch waits for client notification. Command Step 1 Step 2 Step 3 Purpose Enter global configuration mode. and enter interface configuration mode. (Optional) Save your entries in the configuration file. Set the number of times that the switch sends an EAP-request/identity frame to the client before restarting the authentication process. configure terminal interface interface-id authentication timer reauthenticate seconds end show authentication interface interface-id copy running-config startup-config Step 4 Step 5 Step 6 To return to the default retransmission time. follow these steps to set the switch-to-client frame-retransmission number. This procedure is optional. Return to privileged EXEC mode. Release 15. (Optional) Save your entries in the configuration file. Note You should change the default value of this command only to adjust for unusual circumstances such as unreliable links or specific behavioral problems with certain clients and authentication servers. the default is 5. the default is 2.Chapter 10 Configuring IEEE 802. Verify your entries. Specify the port to be configured.

Set the number of times that the switch restarts the authentication process before the port changes to the unauthorized state. configure terminal interface interface-id dot1x max-req count Step 4 Step 5 Step 6 end show authentication interface interface-id copy running-config startup-config To return to the default reauthentication number. Beginning in privileged EXEC mode. Note You should change the default value of this command only to adjust for unusual circumstances such as unreliable links or specific behavioral problems with certain clients and authentication servers. the default is 2. follow these steps to set the reauthentication number. Beginning in privileged EXEC mode. configure terminal authentication mac-move permit Catalyst 2960 and 2960-S Switches Software Configuration Guide. Command Step 1 Step 2 Purpose Enter global configuration mode. use the no dot1x max-req interface configuration command. Command Step 1 Step 2 Step 3 Purpose Enter global configuration mode. This procedure is optional. Enable MAC move on the switch.1x Port-Based Authentication To return to the default retransmission number. The range is 0 to 10. follow these steps to globally enable MAC move on the switch. Verify your entries. use the no dot1x max-reauth-req interface configuration command. Release 15.0(1)SE 10-50 OL-26520-02 . This procedure is optional. Specify the port to be configured. This example shows how to set 4 as the number of times that the switch restarts the authentication process before the port changes to the unauthorized state: Switch(config-if)# dot1x max-reauth-req 4 Enabling MAC Move MAC move allows an authenticated host to move from one port on the switch to another. This example shows how to set 5 as the number of times that the switch sends an EAP-request/identity request before restarting the authentication process: Switch(config-if)# dot1x max-reauth-req 5 Setting the Re-Authentication Number You can also change the number of times that the switch restarts the authentication process before the port changes to the unauthorized state.1x Authentication Configuring IEEE 802. Return to privileged EXEC mode.Chapter 10 Configuring 802. (Optional) Save your entries in the configuration file. and enter interface configuration mode.

Chapter 10 Configuring IEEE 802. Beginning in privileged EXEC mode. Command Step 1 Step 2 Step 3 Purpose Enter global configuration mode. shutdown: the port is error disabled when it receives an unexpected MAC address. Release 15. (Optional) Verify your entries. follow these steps to enable MAC replace on an interface. MAC replace allows a host to replace an authenticated host on a port. This example shows how to enable MAC replace on an interface: Switch(config)# interface gigabitethernet2/0/2 Switch(config-if)# authentication violation replace Catalyst 2960 and 2960-S Switches Software Configuration Guide.1x Port-Based Authentication Configuring 802. (Optional) Saves your entries in the configuration file. (Optional) Save your entries in the configuration file. The port removes the current session and initiates authentication with the new host.0(1)SE OL-26520-02 10-51 . Use the replace keyword to enable MAC replace on the interface.1x Authentication Command Step 3 Step 4 Step 5 Purpose Return to privileged EXEC mode. restrict: violating packets are dropped by the CPU and a system message is generated. This procedure is optional. Step 4 Step 5 Step 6 end show running-config copy running-config startup-config Return to privileged EXEc mode. the switch must be running the LAN base image. Verify your entries. and enter interface configuration mode. The other keywords have these effects: • • • configure terminal interface interface-id authentication violation {protect | replace | restrict | shutdown} protect: the port drops packets with unexpected MAC addresses without generating a system message. Specify the port to be configured. end show running-config copy running-config startup-config This example shows how to globally enable MAC move on a switch: Switch(config)# authentication mac-move permit Enabling MAC Replace Note To enable MAC replace.

39. Enable 802.1x sessions are closed.1x Port-Based Authentication Configuring 802. enable logging of “Update/Watchdog packets from this AAA client” in your RADIUS server Network Configuration tab.246. stop. accounting messages might be lost due to poor network conditions. To turn on these functions. configure terminal interface interface-id aaa accounting dot1x default start-stop group radius aaa accounting system default start-stop group radius end show running-config copy running-config startup-config Step 5 Step 6 Step 7 Use the show radius statistics privileged EXEC command to display the number of RADIUS messages that do not receive the accounting response message. Release 15. The first command configures the RADIUS server. This example shows how to configure 802.0(1)SE 10-52 OL-26520-02 .20.Chapter 10 Configuring 802. and enter interface configuration mode. Beginning in privileged EXEC mode. specifying 1813 as the UDP port for accounting: Switch(config)# radius-server host 172. such as logging start.201:1645. follow these steps to configure 802. Command Step 1 Step 2 Step 3 Step 4 Purpose Enter global configuration mode. Specify the port to be configured.46 auth-port 1812 acct-port 1813 key rad123 Switch(config)# aaa accounting dot1x default start-stop group radius Switch(config)# aaa accounting system default start-stop group radius Catalyst 2960 and 2960-S Switches Software Configuration Guide. Verify your entries.1x Authentication Configuring IEEE 802. The server can then infer that all active 802.1x accounting after AAA is enabled on your switch. This procedure is optional.1646 is not responding. When the stop message is not sent successfully. this system message appears: Accounting message %s for session %s failed to receive Accounting Response. Next. and interim-update messages and time stamps.1x accounting using the list of all RADIUS servers. Because RADIUS uses the unreliable UDP transport protocol. (Optional) Saves your entries in the configuration file. enable “CVS RADIUS Accounting” in your RADIUS server System Configuration tab.1x accounting allows system reload events to be sent to the accounting RADIUS server for logging.1x Accounting Enabling AAA system accounting with 802.120. (Optional) Enables system accounting (using the list of all RADIUS servers) and generates system accounting reload event messages when the switch reloads. Note You must configure the RADIUS server to perform accounting tasks. If the switch does not receive the accounting response message from the RADIUS server after a configurable number of retransmissions of an accounting request. Return to privileged EXEc mode.1x accounting. this message appears: 00:09:55: %RADIUS-4-RADIUS_DEAD: RADIUS server 172.

Release 15.1x Port-Based Authentication Configuring 802.1x guest VLAN.0(1)SE OL-26520-02 10-53 . The port returns to the unauthorized state. You can configure any active VLAN except an RSPAN VLAN or a voice VLAN as an 802. (Optional) Save your entries in the configuration file. to set 15 as the number of seconds that the switch waits for a response to an EAP-request/identity frame from the client before re-sending the request. Specify the port to be configured.1x Authentication Configuration Guidelines” section on page 10-37.1x-compliant are moved into the restricted VLAN when the authentication server does not receive a valid username and password. This example shows how to enable VLAN 2 as an 802. clients that are 802. Beginning in privileged EXEC mode. follow these steps to configure a guest VLAN. use the no authentication event no-response action authorize vlan vlan-id interface configuration command.1x guest VLAN: Switch(config)# interface gigabitethernet2/0/2 Switch(config-if)# authentication event no-response action authorize vlan 2 This example shows how to set 3 as the quiet time on the switch. The switch supports restricted VLANs only in single-host mode. see the “802.Chapter 10 Configuring IEEE 802. Set the port to access mode. Catalyst 2960 and 2960-S Switches Software Configuration Guide. clients that are not 802. Command Step 1 Step 2 Purpose Enter global configuration mode.1x guest VLAN when an 802.1x-capable are put into the guest VLAN when the server does not receive a response to its EAP request/identity frame.1x Authentication Configuring a Guest VLAN When you configure a guest VLAN. and to enable VLAN 2 as an 802.1x guest VLAN. To disable and remove the guest VLAN. The range is 1 to 4094. The switch supports guest VLANs in single-host or multiple-hosts mode.1x port is connected to a DHCP client: Switch(config-if)# authentication timer inactivity 3 Switch(config-if)# authentication timer reauthenticate 15 Switch(config-if)# authentication event no-response action authorize vlan 2 Configuring a Restricted VLAN When you configure a restricted VLAN on a switch stack or a switch. This procedure is optional. For the supported port types.1x-capable but that fail authentication are not granted network access. Enable 802. configure terminal interface interface-id Step 3 Step 4 Step 5 switchport mode access authentication port-control auto authentication event no-response action authorize vlan vlan-id Step 6 Step 7 Step 8 end show authentication interface interface-id copy running-config startup-config Return to privileged EXEC mode. Specify an active VLAN as an 802. Clients that are 802.1x authentication on the port. Verify your entries. and enter interface configuration mode.

see the “802.1x Authentication Configuration Guidelines” section on page 10-37. Enable 802. This procedure is optional.1x Authentication Configuring IEEE 802. (Optional) Save your entries in the configuration file. This example shows how to enable VLAN 2 as an 802.1x restricted VLAN. follow these steps to configure a restricted VLAN. You can configure any active VLAN except an RSPAN VLAN or a voice VLAN as an 802. configure terminal interface interface-id Step 3 Step 4 Step 5 switchport mode access authentication port-control auto authentication event fail action authorize vlan-id Step 6 Step 7 Step 8 end show authentication interface interface-id copy running-config startup-config Return to privileged EXEC mode. and enter interface configuration mode. You can configure any active VLAN except an RSPAN VLAN or a voice VLAN as an 802. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Command Step 1 Step 2 Purpose Enter global configuration mode. Beginning in privileged EXEC mode.0(1)SE 10-54 OL-26520-02 . This procedure is optional.1x restricted VLAN. Specify the port to be configured.1x authentication on the port.1x Port-Based Authentication Beginning in privileged EXEC mode.1x restricted VLAN: Switch(config-if)# authentication event fail action authorize 2 You can configure the maximum number of authentication attempts allowed before a user is assigned to the restricted VLAN by using the authentication event retry retry count interface configuration command. Specify an active VLAN as an 802.1x authentication on the port. The range of allowable authentication attempts is 1 to 3. The port returns to the unauthorized state. The default is 3 attempts. Set the port to access mode. For the supported port types. (Optional) Verify your entries. For the supported port types.1x restricted VLAN. configure terminal interface interface-id Step 3 Step 4 Step 5 switchport mode access authentication port-control auto authentication event fail action authorize vlan-id Step 6 authentication event retry retry count Specify a number of authentication attempts to allow before a port moves to the restricted VLAN. Set the port to access mode. The range is 1 to 3. The range is 1 to 4094. Specify the port to be configured.Chapter 10 Configuring 802. Release 15.1x restricted VLAN.1x Authentication Configuration Guidelines” section on page 10-37. and the default is 3. The range is 1 to 4094. see the “802. use the no authentication event fail action authorize vlan-id interface configuration command. Specify an active VLAN as an 802. follow these steps to configure the maximum number of allowed authentication attempts. and enter interface configuration mode. Enable 802. To disable and remove the restricted VLAN. Command Step 1 Step 2 Purpose Enter global configuration mode.

also referred to as critical authentication or the AAA fail policy to allow data traffic to pass through on the native VLAN when the server is not available. • • configure terminal radius-server dead-criteria time time tries tries The range for time is from 1 to 120 seconds. Step 3 radius-server deadtime minutes (Optional) Sets the number of minutes during which a RADIUS server is not sent requests. Beginning in privileged EXEC mode. This example shows how to set 2 as the number of authentication attempts allowed before the port moves to the restricted VLAN: Switch(config-if)# authentication event retry 2 Configuring Inaccessible Authentication Bypass and Critical Voice VLAN You can configure the inaccessible bypass feature. Sets the conditions that are used to decide when a RADIUS server is considered unavailable or down (dead).0(1)SE OL-26520-02 10-55 . follow these steps to configure critical voice VLAN on a port and enable the inaccessible authentication bypass feature. The switch dynamically determines a default tries parameter between 10 and 100. You can also configure the critical voice VLAN feature so that if the server is not available and traffic from the host is tagged with the voice VLAN. The switch dynamically determines a default seconds value between 10 and 60 seconds. Command Step 1 Step 2 Purpose Enters global configuration mode. (Optional) Save your entries in the configuration file.Chapter 10 Configuring IEEE 802. The range is from 0 to 1440 minutes (24 hours).1x Port-Based Authentication Configuring 802. The default is 0 minutes. use the no authentication event retry interface configuration command. (Optional) Verify your entries.1x Authentication Command Step 7 Step 8 Step 9 Purpose Return to privileged EXEC mode. end show authentication interface interface-id copy running-config startup-config To return to the default value. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Release 15. the connected device (the phone) is put in the configured voice VLAN for the port. The range for tries is from 1 to 100.

You should configure the UDP port for the RADIUS accounting server and the UDP port for the RADIUS authentication server to nondefault values. (Optional) Verifies your entries.Chapter 10 Configuring 802. Catalyst 2960 and 2960-S Switches Software Configuration Guide. idle-time time—Sets the interval of time in minutes after which the switch sends test packets to the server. The range is from 1 to 35791 minutes. You can also configure the authentication and encryption key by using the radius-server key {0 string | 7 string | string} global configuration command. If you use spaces in the key. The default is 1646. Note • • • • • Note Step 5 Step 6 interface interface-id authentication event server dead action {authorize | reinitialize} vlan vlan-id Specifies the port to be configured and enters interface configuration mode. auth-port udp-port—Specifies the UDP port for the RADIUS authentication server. The default is 60 minutes (1 hour). but spaces within and at the end of the key are used. Step 7 Step 8 Step 9 Step 10 switchport voice vlan vlan-id authentication event server dead action authorize voice end show authentication interface interface-id Specifies the voice VLAN for the port. Returns to privileged EXEC mode. Release 15.1x Authentication Configuring IEEE 802. ignore-acct-port—Disables testing on the RADIUS-server accounting port. Always configure the key as the last item in the radius-server host command syntax because leading spaces are ignored. The range for the UDP port number is from 0 to 65536. specify the authentication and encryption key used between the switch and the RADIUS daemon running on the RADIUS server. For key string. This key must match the encryption used on the RADIUS daemon.0(1)SE 10-56 OL-26520-02 .1x Port-Based Authentication Command Step 4 Purpose Configures the RADIUS server parameters: • • radius-server host ip-address [acct-port udp-port] [auth-port udp-port] [test username name [idle-time time] [ignore-acct-port] [ignoreauth-port]] [key string] acct-port udp-port—Specifies the UDP port for the RADIUS accounting server. and specifies the username to be used. test username name—Enables automatic testing of the RADIUS server status. reinitialize—Moves all authorized hosts on the port to the user-specified critical VLAN. Configures a critical VLAN to move hosts on the port if the RADIUS server is unreachable: • • authorize—Moves any new hosts trying to authenticate to the user-specified critical VLAN. ignoreauth-port—Disables testing on the RADIUS-server authentication port. Configures critical voice VLAN to move data traffic on the port to the voice VLAN if the RADIUS server is unreachable. The default is 1645. The voice VLAN cannot be the same as the critical data VLAN configured in Step 6. The range for the UDP port number is from 0 to 65536. do not enclose the key in quotation marks unless the quotation marks are part of the key.

use the no authentication control-direction interface configuration command.0(1)SE OL-26520-02 10-57 .1x Authentication with Wake-on-LAN Beginning in privileged EXEC mode. The port cannot receive packets from or send packets to the host.2 acct-port 1550 auth-port 1560 test username user1 idle-time 30 key abc1234 Switch(config)# interface gigabitethernet 1/0/1 Switch(config)# radius-server deadtime 60 Switch(config-if)# authentication event server dead action reinitialicze vlan 20 Switch(config-if)# switchport voice vlan Switch(config-if)# authentication event server dead action authorize voice Switch(config-if)# end Configuring 802. (Optional) Save your entries in the configuration file. This procedure is optional.1x authentication with WoL.Chapter 10 Configuring IEEE 802. and use these | in} keywords to configure the port as bidirectional or unidirectional. configure terminal interface interface-id Step 3 authentication control-direction {both Enable 802. For the supported port types.1x authentication with WoL and set the port as bidirectional: Switch(config-if)# authentication control-direction both Catalyst 2960 and 2960-S Switches Software Configuration Guide.1x Authentication This example shows how to configure the inaccessible authentication bypass feature and configure the critical voice VLAN: Switch(config)# radius-server dead-criteria time 30 tries 20 Switch(config)# radius-server deadtime 60 Switch(config)# radius-server host 1.1x Authentication Configuration Guidelines” section on page 10-37. Verify your entries. These examples show how to enable 802.1. Command Step 1 Step 2 Purpose Enter global configuration mode.1x Port-Based Authentication Configuring 802. The port can send packets to the host but cannot receive packets from the host. Release 15.1x authentication with WoL. the port is bidirectional. and enter interface configuration mode. see the “802. Specify the port to be configured. • • both—Sets the port as bidirectional. By default. in—Sets the port as unidirectional. Step 4 Step 5 Step 6 end show authentication interface interface-id copy running-config startup-config Return to privileged EXEC mode. To disable 802. follow these steps to enable 802.1x authentication with WoL on the port.1.

0(1)SE 10-58 OL-26520-02 . see the “802. Specify the port to be configured. use the no authentication order interface configuration command. separator—The character that separates the hex nibbles according to group size. configure terminal mab request format attribute 1 Specifies the format of the MAC address in the User-Name attribute of groupsize {1 | 2 | 4 | 12} separator{. This procedure is optional.1x Authentication Configuration Guidelines” section on page 10-37. 2. This procedure is optional. {lowercase | uppercase}—Specifies if nonnumeric hex nibbles should be in lowercase or uppercase. mab—Add MAC authentication bypass (MAB) to the order of authentication methods.1x Port-Based Authentication Configuring MAC Authentication Bypass Beginning in privileged EXEC mode. and enter interface configuration mode. | . A valid groupsize must be either 1.| : MAB-generated Access-Request packets. To disable MAC authentication bypass. follow these steps to enable MAC authentication bypass. Enable 802.1x Authentication Configuring IEEE 802. Catalyst 2960 and 2960-S Switches Software Configuration Guide. or period.Chapter 10 Configuring 802. (Optional) Save your entries in the configuration file. or 12. For the supported port types. webauth—Add web authentication to the order of authentication methods.} {lowercase | uppercase} group size—The number of hex nibbles to concatenate before insertion of a separator. This example shows how to enable MAC authentication bypass: Switch(config-if)# authentication order Configuring a MAC Authentication Bypass (MAB) Username and Password Beginning in privileged EXEC mode. No separator is used for a group size of 12.1x authentication on the port. • • configure terminal interface interface-id Step 3 Step 4 authentication port-control auto authentication order [mab] {webauth} Set the order of authentication methods. colon. Command Step 1 Step 2 Purpose Enters global configuration mode. 4. Release 15. Command Step 1 Step 2 Purpose Enter global configuration mode. Verify your entries. A valid separator must be either a hyphen. Step 5 Step 6 Step 7 end show authentication interface interface-id copy running-config startup-config Return to privileged EXEC mode. follow these steps to configure a MAB username and password.

to and verify the VLAN group configurations and mapping to the specified VLANs: Switch(config)# vlan group eng-dept vlan-list 10 switch(config)# show vlan group group-name eng-dept Group Name Vlans Mapped -------------------------eng-dept 10 switch# show dot1x vlan-group all Group Name Vlans Mapped -------------------------eng-dept 10 hr-dept 20 This example shows how to add a VLAN to an existing VLAN group and to verify that the VLAN was added: switch(config)# vlan group eng-dept vlan-list 30 switch(config)# show vlan group eng-dept Group Name Vlans Mapped -------------------------eng-dept 10. <LINE>—Specifies the password to be used in the User-Password attribute.1x User Distribution Beginning in global configuration. follow these steps to configure a VLAN group and to map a VLAN to it: Command Step 1 Step 2 Step 3 Purpose Configure a VLAN group. Verify the configuration. to map the VLANs to the groups. and map a single VLAN or a range of VLANs to it. vlan group vlan-group-name vlan-list vlan-list show vlan group all vlan-group-name no vlan group vlan-group-name vlan-list vlan-list This example shows how to configure the VLAN groups. Release 15. Clear the VLAN group configuration or elements of the VLAN group configuration. Step 4 end Returns to privileged EXEC mode. use the no mab request format interface configuration command.0(1)SE OL-26520-02 10-59 . 7—Specifies an encrypted password. 0—Specifies a cleartext password. To disable configurable MAC authentication bypass.1x Port-Based Authentication Configuring 802.30 Catalyst 2960 and 2960-S Switches Software Configuration Guide.Chapter 10 Configuring IEEE 802.1x Authentication Command Step 3 Purpose mab request format attribute 2 {0 | 7} Specifies a custom (nondefault) value for the User-Password attribute in <LINE> MAB-generated Access-Request packets. This example shows how to enable configurable MAC authentication bypass: Switch(config-if)# mab request format Configuring 802.

You can configure any active VLAN except an RSPAN VLAN. Verify your 802. Specify an active VLAN as an 802. (Optional) Save your entries in the configuration file. Specify the port to be configured. the VLAN group is cleared: switch(config)# no vlan group eng-dept vlan-list 30 Vlan 30 is successfully cleared from vlan group eng-dept.1x Authentication Configuring IEEE 802. Command Step 1 Step 2 Step 3 Purpose Enter global configuration mode.Chapter 10 Configuring 802. This example shows how to configure NAC Layer 2 802. and enter interface configuration mode.1x validation. configure terminal interface interface-id authentication event no-response action authorize vlan vlan-id Step 4 Step 5 authentication periodic authentication timer reauthenticate Enable periodic reauthentication of the client. Beginning in privileged EXEC mode. which is disabled by default.1x guest VLAN.1x validation. which is also referred to as 802. switch(config)# show vlan group group-name eng-dept This example shows how to clear all the VLAN groups: switch(config)# no vlan group end-dept vlan-list all switch(config)# show vlan-group all For more information about these commands.1x authentication configuration. Set reauthentication attempt for the client (set to one hour). see the Cisco IOS Security Command Reference. or a voice VLAN as an 802.1x Port-Based Authentication This example shows how to remove a VLAN from a VLAN group: switch# no vlan group eng-dept vlan-list 10 This example shows that when all the VLANs are cleared from a VLAN group. This command affects the behavior of the switch only if periodic reauthentication is enabled. Step 6 Step 7 Step 8 end show authentication interface interface-id copy running-config startup-config Return to privileged EXEC mode.1x guest VLAN.1x authentication with a RADIUS server. follow these steps to configure NAC Layer 2 802. The procedure is optional. Release 15. Configuring NAC Layer 2 802.0(1)SE 10-60 OL-26520-02 . The range is 1 to 4094.1x validation: Switch# configure terminal Switch(config)# interface gigabitethernet1/0/2 Switch(config-if)# authentication periodic Switch(config-if)# authentication timer reauthenticate Catalyst 2960 and 2960-S Switches Software Configuration Guide.1x Validation You can configure NAC Layer 2 802.

Enable Port Fast on an access port connected to a single workstation or server.1x credentials profile. follow these steps to configure a switch as an authenticator: Command Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Purpose Enter global configuration mode. Release 15. For overview information. Return to privileged EXEC mode. This must be attached to the port that is configured as supplicant. configure terminal cisp enable dot1x credentials profile username suppswitch Catalyst 2960 and 2960-S Switches Software Configuration Guide.0(1)SE OL-26520-02 10-61 . see the “802. Configure the interface as a port access entity (PAE) authenticator.1x Authentication Configuring an Authenticator and a Supplicant Switch with NEAT Configuring this feature requires that one switch outside a wiring closet is configured as a supplicant and is connected to an authenticator switch. which sets the interface as a trunk after the supplicant is successfully authenticated.Chapter 10 Configuring IEEE 802. and enter interface configuration mode. Specify the port to be configured. Set the port mode to access.1x Port-Based Authentication Configuring 802. Enable CISP. configure terminal cisp enable interface interface-id switchport mode access authentication port-control auto dot1x pae authenticator spanning-tree portfast end show running-config interface interface-id copy running-config startup-config This example shows how to configure a switch as an 802. Create a username. Note The cisco-av-pairs must be configured as device-traffic-class=switch on the ACS. (Optional) Save your entries in the configuration file.1x Supplicant and Authenticator Switches with Network Edge Access Topology (NEAT)” section on page 10-32. Set the port-authentication mode to auto. Beginning in privileged EXEC mode. Enable CISP. Verify your configuration. Create 802. follow these steps to configure a switch as a supplicant: Command Step 1 Step 2 Step 3 Step 4 Purpose Enter global configuration mode.1x authenticator: Switch# configure terminal Switch(config)# cisp enable Switch(config)# interface gigabitethernet2/0/1 Switch(config-if)# switchport mode access Switch(config-if)# authentication port-control auto Switch(config-if)# dot1x pae authenticator Switch(config-if)# spanning-tree portfast trunk Beginning in privileged EXEC mode.

Return to privileged EXEC mode. Configure the interface as a port access entity (PAE) supplicant. For information. Configure the interface as a VLAN trunk port. This also allows NEAT to work on the supplicant switch in all host modes. Attach the 802.0(1)SE 10-62 OL-26520-02 . This example shows how to configure a switch as a supplicant: Switch# configure terminal Switch(config)# cisp enable Switch(config)# dot1x credentials test Switch(config)# username suppswitch Switch(config)# password myswitch Switch(config)# dot1x supplicant force-multicast Switch(config)# interface gigabitethernet2/0/1 Switch(config-if)# switchport trunk encapsulation dot1q Switch(config-if)# switchport mode trunk Switch(config-if)# dot1x pae supplicant Switch(config-if)# dot1x credentials test Switch(config-if)# end Configuring NEAT with Auto Smartports Macros You can also use an Auto Smartports user-defined macro instead of the switch VSA to configure the authenticator switch.1x Port-Based Authentication Command Step 5 Step 6 Purpose Create a password for the new username. Force the switch to send only multicast EAPOL packets when it receives either unicast or multicast packets. Release 15. see the Auto Smartports Configuration Guide. and enter interface configuration mode. Set the port to trunk mode. Verify your configuration.1x Authentication Configuring IEEE 802. Catalyst 2960 and 2960-S Switches Software Configuration Guide.Chapter 10 Configuring 802. (Optional) Save your entries in the configuration file. password password dot1x supplicant force-multicast Step 7 Step 8 Step 9 Step 10 Step 11 Step 12 Step 13 Step 14 interface interface-id switchport trunk encapsulation dot1q switchport mode trunk dot1x pae supplicant dot1x credentials profile-name end show running-config interface interface-id copy running-config startup-config Specify the port to be configured.1x credentials profile to the interface.

and enter interface configuration mode. (Optional) Save your entries in the configuration file. Configure the ip device tracking table. Configure the radius vsa send authentication.0(1)SE OL-26520-02 10-63 .1x Port-Based Authentication Configuring 802. Configure the default ACL on the port in the input direction. To remove the authorization method. you need to configure the ACS. Enables AAA. Beginning in privileged EXEC mode: Command Step 1 Step 2 Step 3 Step 4 Purpose Enter global configuration mode. Note configure terminal ip device tracking aaa new-model aaa authorization network default group radius radius-server vsa send authentication interface interface-id ip access-group acl-id in show running-config interface interface-id copy running-config startup-config Step 5 Step 6 Step 7 The acl-id is an access list name or number. you can use the show ip access-list privileged EXEC command to display the downloaded ACLs on the port. Release 15. Step 8 Step 9 Verify your configuration. see the Cisco Secure ACS configuration guides.1x Authentication with Downloadable ACLs and Redirect URLs In addition to configuring 802. Sets the authorization method to local. For more information.1x Authentication Configuring 802. After authentication on the port. use the no aaa authorization network default group radius command.Chapter 10 Configuring IEEE 802. Configuring Downloadable ACLs The policies take effect after client authentication and the client IP address addition to the IP device tracking table. The switch then applies the downloadable ACL to the port. Configuring a Downloadable Policy Beginning in privileged EXEC mode: Catalyst 2960 and 2960-S Switches Software Configuration Guide.1x authentication on the switch. Specify the port to be configured. Note You must configure a downloadable ACL on the ACS before downloading it to the switch.

0. Note The acl-id is an access list name or number. Defines the default port ACL by using a source address and wildcard.0. The default is 30 seconds. The range is from 1 to 5. use-svi—Uses the switch virtual interface (SVI) IP address as source of ARP probes.0. Enter deny or permit to specify whether to deny or permit access if conditions are matched. The keyword any as an abbreviation for source and source-wildcard value of 0. interval interval—Sets the number of seconds that the switch waits for a response before resending the ARP probe. Note The downloadable ACL must be operational.1x Port-Based Authentication Command Step 1 Step 2 Purpose Enter global configuration mode.255. The default is 3. Configure the default ACL on the port in the input direction. Step 3 Step 4 interface interface-id ip access-group acl-id in exit aaa new-model aaa authorization network default group radius ip device tracking Enter interface configuration mode. (Optional) Enters log to cause an informational logging message about the packet that matches the entry to be sent to the console.0 255. Step 11 end Returns to privileged EXEC mode. such as this: • • configure terminal access-list access-list-number deny source source-wildcard log The 32-bit quantity in dotted-decimal format. • Step 10 radius-server vsa send authentication Configures the network access server to recognize and use vendor-specific attributes. Step 8 Step 9 ip device tracking probe [count | interval | use-svi] (Optional) Configures the IP device tracking table: • • count count—Sets the number of times that the switch sends the ARP probe.1x Authentication Configuring IEEE 802. The keyword host as an abbreviation for source and source-wildcard of source 0. use the no ip device tracking global configuration commands. The access-list-number is a decimal number from 1 to 99 or 1300 to 1999.0(1)SE 10-64 OL-26520-02 . Step 5 Step 6 Step 7 Returns to global configuration mode. The source is the source address of the network or host that sends a packet. Enables AAA. The range is from 30 to 300 seconds. Sets the authorization method to local. To disable the IP device tracking table. To remove the authorization method. Release 15.255. Catalyst 2960 and 2960-S Switches Software Configuration Guide.Chapter 10 Configuring 802. use the no aaa authorization network default group radius command.0. You do not need to enter a source-wildcard value.0.255. • (Optional) Applies the source-wildcard wildcard bits to the source. Enables the IP device tracking table.

Release 15. (Optional) Save your entries in the configuration file. and enter interface configuration mode. Switch(config)# aaa new-model Switch(config)# aaa authorization network default group radius Switch(config)# ip device tracking Switch(config)# ip access-list extended default_acl Switch(config-ext-nacl)# permit ip any any Switch(config-ext-nacl)# exit Switch(config)# radius-server vsa send authentication Switch(config)# interface gigabitethernet1/0/2 Switch(config-if)# ip access-group default_acl in Switch(config-if)# exit Configuring VLAN ID-based MAC Authentication Beginning in privileged EXEC mode. one per line. follow these steps: Command Step 1 Step 2 Step 3 Purpose Enter global configuration mode. You can use the debug radius accounting privileged EXEC command to confirm the RADIUS attribute 32. (Optional) Saves your entries in the configuration file.html#wp1123741 This example shows how to globally enable VLAN ID-based MAC authentication on a switch: Switch# configure terminal Enter configuration commands.cisco.Chapter 10 Configuring IEEE 802. show ip device tracking all copy running-config startup-config This example shows how to configure a switch for a downloadable policy: Switch# config terminal Enter configuration commands. configure terminal mab request format attribute 32 vlan access-vlan copy running-config startup-config There is no show command to confirm the status of VLAN ID-based MAC authentication. one per line. follow these steps: Command Step 1 Step 2 Purpose Enter global configuration mode.1x Authentication Command Step 12 Step 13 Purpose Displays information about the entries in the IP device tracking table. For more information about this command. End with CNTL/Z.0(1)SE OL-26520-02 10-65 . End with CNTL/Z.1x Port-Based Authentication Configuring 802. Specify the port to be configured. Switch(config)# mab request format attribute 32 vlan access-vlan Switch(config-if)# exit Configuring Flexible Authentication Ordering Beginning in privileged EXEC mode.com/en/US/docs/ios/debug/command/reference/db_q1. see the Cisco IOS Debug Command Reference: http://www. Enable VLAN ID-based MAC authentication. configure terminal interface interface-id Catalyst 2960 and 2960-S Switches Software Configuration Guide.

(Optional) Verify your entries.1x authentication first. (Optional) Verify your entries. configure terminal interface interface-id authentication control-direction {both | in} authentication fallback name Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Step 11 authentication host-mode [multi-auth | multi-domain | multi-host | single-host] authentication open authentication order [dot1x | mab] | {webauth} authentication periodic authentication port-control {auto | force-authorized | force-un authorized} show authentication copy running-config startup-config This example shows how to configure open 1x on a port: Switch# configure terminal Switch(config)# interface gigabitethernet1/0/2 Switch(config)# authentication control-direction both Switch(config)# au ten tic at ion fallback profile1 Switch(config)# authentication host-mode multi-auth Switch(config)# authentication open Catalyst 2960 and 2960-S Switches Software Configuration Guide.1x Port-Based Authentication Command Step 3 Step 4 Step 5 Step 6 Purpose (Optional) Set the order of authentication methods used on a port.1x authentication. (Optional) Save your entries in the configuration file. and enter interface configuration mode. (Optional) Enable or disable reauthentication on a port. (Optional) Save your entries in the configuration file. (Optional) Configure the port control as unidirectional or bidirectional. followed by web authentication as fallback method: Switch# configure terminal Switch(config)# interface gigabitethernet1/0/2 Switch(config)# authentication order dot1x webauth Configuring Open1x Beginning in privileged EXEC mode: Command Step 1 Step 2 Step 3 Step 4 Purpose Enter global configuration mode. authentication order [dot1x | mab] | {webauth} authentication priority [dot1x | mab] | {webauth} show authentication copy running-config startup-config This example shows how to configure a port attempt 802. (Optional) Set the order of authentication methods used on a port. (Optional) Enable or disable open access on a port.0(1)SE 10-66 OL-26520-02 .1x Authentication Configuring IEEE 802. (Optional) Enable manual control of the port authorization state. (Optional) Set the authorization manager mode on a port.Chapter 10 Configuring 802. Release 15. (Optional) Configure a port to use web authentication as a fallback method for clients that do not support 802. Specify the port to be configured. (Optional) Add an authentication method to the port-priority list.

1x parameters to the default values.1x authentication on the port: Switch(config)# interface gigabitethernet1/0/2 Switch(config-if)# no dot1x pae authenticator Resetting the 802.1x Authentication Switch(config)# authentication order dot1x webauth Switch(config)# authentication periodic Switch(config)# authentication port-control auto Disabling 802. This procedure is optional. configure terminal interface interface-id dot1x default end show authentication interface interface-id copy running-config startup-config Catalyst 2960 and 2960-S Switches Software Configuration Guide. configure terminal interface interface-id no dot1x pae end show authentication interface interface-id copy running-config startup-config To configure the port as an 802.1x authentication configuration to the default values. Command Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Purpose Enter global configuration mode.1x Authentication on the Port You can disable 802. (Optional) Save your entries in the configuration file. Return to privileged EXEC mode.0(1)SE OL-26520-02 10-67 . Enter interface configuration mode. Return to privileged EXEC mode.1x authentication on the port. and enter interface configuration mode.1x Authentication Configuration to the Default Values Beginning in privileged EXEC mode. Verify your entries. Specify the port to be configured.1x authentication on the port.Chapter 10 Configuring IEEE 802. which enables 802. Command Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Purpose Enter global configuration mode. This example shows how to disable 802. Reset the 802. Disable 802. use the dot1x pae authenticator interface configuration command. follow these steps to disable 802. (Optional) Save your entries in the configuration file. Release 15. and specify the port to be configured.1x Port-Based Authentication Configuring 802. Beginning in privileged EXEC mode. This procedure is optional.1x on the port but does not allow clients connected to the port to be authorized.1x port access entity (PAE) authenticator. follow these steps to reset the 802.1x authentication on the port by using the no dot1x pae interface configuration command. Verify your entries.

1x administrative and operational status for the switch.Chapter 10 Displaying 802.1x authentication messages.1x Port-Based Authentication Displaying 802.1x Statistics and Status To display 802. Beginning with Cisco IOS Release 12. use the show dot1x interface interface-id privileged EXEC command. To display 802. use the show dot1x statistics interface interface-id privileged EXEC command.1x administrative and operational status for a specific port. see the command reference for this release. To display the 802. use the show dot1x all statistics privileged EXEC command.1x statistics for all ports. Release 15. use the show dot1x all [details | statistics | summary] privileged EXEC command. See the “Authentication Manager CLI Commands” section on page 10-9. Catalyst 2960 and 2960-S Switches Software Configuration Guide.1x Statistics and Status Configuring IEEE 802. To display the 802.1x statistics for a specific port. you can use the no dot1x logging verbose global configuration command to filter verbose 802.0(1)SE 10-68 OL-26520-02 .2(55)SE. For detailed information about the fields in these displays.

1x Port-Based Authentication Displaying 802.Chapter 10 Configuring IEEE 802.0(1)SE OL-26520-02 10-69 .1x Statistics and Status Catalyst 2960 and 2960-S Switches Software Configuration Guide. Release 15.

known as web authentication proxy. Note You can configure web-based authentication on Layer 2 and Layer 3 interfaces. page 11-2 Host Detection. page 11-3 Authentication Process. If the user exceeds the maximum number of attempts. prompting the user to retry the login. Understanding Web-Based Authentication Use the web-based authentication feature. web-based authentication forwards a Login-Expired HTML page to the host. authorization. and the user is placed on a watch list for a waiting period. to authenticate end users on host systems that do not run the IEEE 802. web-based authentication forwards a Login-Fail HTML page to the user. When you initiate an HTTP session. web-based authentication intercepts ingress HTTP packets from the host and sends an HTML login page to the users. page 11-3 Catalyst 2960 and 2960-S Switches Software Configuration Guide. page 11-17 Note For complete syntax and usage information for the switch commands used in this chapter. The users enter their credentials. Release 15. page 11-9 Displaying Web-Based Authentication Status. If authentication succeeds. If authentication fails. which the web-based authentication feature sends to the authentication. It contains these sections: • • • Understanding Web-Based Authentication.CH A P T E R 11 Configuring Web-Based Authentication This chapter describes how to configure web-based authentication. page 11-1 Configuring Web-Based Authentication. and accounting (AAA) server for authentication. web-based authentication sends a Login-Successful HTML page to the host and applies the access policies returned by the AAA server. These sections describe the role of web-based authentication as part of AAA: • • • • Device Roles. page 11-2 Session Creation.0(1)SE OL-26520-02 11-1 . refer to the command reference for this release.1x supplicant.

Dynamic ARP inspection DHCP snooping—Web-based authentication is notified when the switch creates a DHCP-binding entry for the host. Note By default.Chapter 11 Configuring Web-Based Authentication Understanding Web-Based Authentication • • Web Authentication Customizable Web Pages. verifying that information with the authentication server. the devices in the network have these specific roles: • Client—The device (workstation) that requests access to the LAN and the services and responds to requests from the switch. The switch acts as an intermediary (proxy) between the client and the authentication server. and relaying a response to the client. page 11-6 Web-based Authentication Interactions with Other Features. Catalyst 2960 and 2960-S Switches Software Configuration Guide.0(1)SE OL-26520-02 79549 11-2 . The authentication server validates the identity of the client and notifies the switch that the client is authorized to access the LAN and the switch services or that the client is denied. page 11-7 Device Roles With web-based authentication. requesting identity information from the client. the IP device tracking feature is disabled on a switch. Switch—Controls the physical access to the network based on the authentication status of the client. You must enable the IP device tracking feature to use web-based authentication. For Layer 2 interfaces. • • Figure 11-1 shows the roles of these devices in a network: Figure 11-1 Web-Based Authentication Device Roles Catalyst switch or Cisco Router Workstations (clients) Authentication server (RADIUS) Host Detection The switch maintains an IP device tracking table to store information about detected hosts. Release 15. web-based authentication detects IP hosts by using these mechanisms: • • • ARP based trigger—ARP redirect ACL allows web-based authentication to detect hosts with a static IP address or a dynamic IP address. Authentication server—Authenticates the client. The workstation must be running an HTML browser with Java Script enabled.

The user enters a username and password.) The switch reauthenticates a client when the host does not respond to an ARP probe on a Layer 2 interface. The login success page is sent to the user. If the authentication succeeds. If the maximum number of attempts fails. • Reviews for authorization bypass If the host IP is not on the exception list. • Sets up the HTTP intercept ACL If the server response to the NRH request is access rejected. The feature applies the downloaded timeout or the locally configured session timeout. or when the host does not send any traffic within the idle timeout on a Layer 3 interface. The user retries the login. Release 15.0(1)SE 11-3 OL-26520-02 . these events occur: • • The user initiates an HTTP session. The login success page is sent to the user. and the session is established. authorization is bypassed for this host. the policy from the exception list entry is applied. If the host IP is included in the exception list. If the terminate action is default. the session is dismantled. (See the “Local Web Authentication Banner” section on page 11-4. The session is established. and if an AAA fail policy is configured. the feature sends a nonresponsive host (NRH) request to the server. If the server response is access accepted.Chapter 11 Understanding Web-Based Authentication Configuring Web-Based Authentication Session Creation When web-based authentication detects a new host. Authentication Process When you enable web-based authentication. • • • • • • • Catalyst 2960 and 2960-S Switches Software Configuration Guide. and the session waits for HTTP traffic from the host. and the host is placed in a watch list. it creates a session as follows: • Reviews the exception list. the switch downloads and activates the user’s access policy from the authentication server. and the switch sends the entries to the authentication server. the user can retry the authentication process. If the terminate action is RADIUS. the switch sends the login expired page. After the watch list times out. and authorization is initiated. If the authentication fails. web-based authentication sends a nonresponsive-host (NRH) request to the server. The terminate action is included in the response from the server. The switch sends the login page to the user. The HTTP traffic is intercepted. the switch applies the failure access policy to the host. the HTTP intercept ACL is activated. If the authentication server does not respond to the switch. and the applied policy is removed. the switch sends the login fail page.

Figure 11-2 Authentication Successful Banner You can also customize the banner.0(1)SE OL-26520-02 11-4 . Add a logo or text file to the banner by using the ip admission auth-proxy-banner http file-path global configuration command. The banner appears on both the login page and the authentication-result pop-up pages. Cisco Systems appears on the authentication result pop-up page. • • Add a switch. The default banner Cisco Systems and Switch host-name Authentication appear on the Login Page. router. as shown in Figure 11-2. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Release 15. as shown in Figure 11-3.Chapter 11 Configuring Web-Based Authentication Understanding Web-Based Authentication Local Web Authentication Banner You can create a banner that will appear when you log in to a switch by using web authentication. • • • Authentication Successful Authentication Failed Authentication Expired You create a banner by using the ip admission auth-proxy-banner http global configuration command. or company name to the banner by using the ip admission auth-proxy-banner http banner-text global configuration command.

see the Cisco IOS Security Command Reference and the “Configuring a Web Authentication Local Banner” section on page 11-16. as shown in Figure 11-4.Chapter 11 Understanding Web-Based Authentication Configuring Web-Based Authentication Figure 11-3 Customized Web Banner If you do not enable a banner. Catalyst 2960 and 2960-S Switches Software Configuration Guide. only the username and password dialog boxes appear in the web authentication login screen. Figure 11-4 Login Screen With No Banner For more information. and no banner appears when you log into the switch.0(1)SE 11-5 OL-26520-02 . Release 15.

to set a hidden password. An incomplete URL might cause page not found or similar errors on a web browser. and so on) that are stored in the system directory (for example. On the banner page. If you configure web pages for HTTP authentication. You must configure all four pages. The server uses these pages to notify you of these four-authentication process states: • • • • Login—Your credentials are requested. The configured authentication proxy feature supports both HTTP and SSL. disk0. they must include the appropriate HTML commands (for example. Catalyst 2960 and 2960-S Switches Software Configuration Guide.Chapter 11 Configuring Web-Based Authentication Understanding Web-Based Authentication Web Authentication Customizable Web Pages During the web-based authentication process. for the default internal HTML pages. or disk) and that must be displayed on the login page must use web_auth_<filename> as the file name. Fail—The login failed. audio. http://www. the CLI command redirecting users to a specific URL does not take effect. Configured web pages can be copied to the switch boot flash or flash. flash. which replaces the internal Success page. You must include an HTML redirect command in the success page to access a specific URL. Guidelines • • • • • • • You can substitute your own HTML pages for the default internal HTML pages. video. the switch internal HTTP server hosts four HTML pages to deliver to an authenticating client.cisco. The login page can be on one flash. • • • • • • • • • You can substitute your HTML pages. Release 15. You can also specify a URL to which users are redirected after authentication occurs. the flash on the stack master or a member). The CLI command to redirect users to a specific URL is not available when the configured login form is enabled. Success—The login was successful. you can specify text in the login page. The administrator should ensure that the redirection is configured in the web page. You can use a logo or specify text in the login. flash. If the CLI command redirecting users to specific URL after authentication occurs is entered and then the command configuring web pages is entered. All of the logo files (image. or to confirm that the same page is not submitted twice). and the success and failure pages can be another flash (for example. failure. The banner page has no effect if it is configured with the web page. Expire—The login session has expired because of excessive login failures. as shown in Figure 11-5 on page 11-7. The pages are in HTML. Configured pages can be accessed from the flash on the stack master or members. and expire web pages. to set the page time out.0(1)SE OL-26520-02 11-6 .com). The URL string must be a valid URL (for example. success.

1x Authentication. For more information about enabling port security.0(1)SE 11-7 OL-26520-02 . page 11-8 ACLs. Release 15. including that of the client. and port security manages network access for all MAC addresses. Catalyst 2960 and 2960-S Switches Software Configuration Guide. see the “Configuring Port Security” section on page 23-8. You can then limit the number or group of clients that can access the network through the port. page 11-8 802. page 11-8 Context-Based Access Control. page 11-8 EtherChannel. page 11-8 Port Security You can configure web-based authentication and port security on the same port. page 11-8 Gateway IP. page 11-7 LAN Port IP.Chapter 11 Understanding Web-Based Authentication Configuring Web-Based Authentication Figure 11-5 Customizeable Authentication Page For more information. Web-based Authentication Interactions with Other Features • • • • • • • Port Security. Web-based authentication authenticates the port. see the “Customizing the Authentication Proxy Web Pages” section on page 11-13.

and posture is validated again. You cannot configure a MAC ACL and web-based authentication on the same interface. The web-based authentication configuration applies to all member channels. After authentication. 802. The host is authenticated by using web-based authentication first. The GWIP policy overrides the web-based authentication host policy. You cannot configure web-based authentication on a port whose access VLAN is configured for VACL capture. EtherChannel You can configure web-based authentication on a Layer 2 EtherChannel interface. followed by LPIP posture validation. the ACL is applied to the host traffic only after the web-based authentication host policy is applied. ACLs If you configure a VLAN ACL or a Cisco IOS ACL on an interface. Release 15.0(1)SE OL-26520-02 11-8 . Context-Based Access Control Web-based authentication cannot be configured on a Layer 2 port if context-based access control (CBAC) is configured on the Layer 3 VLAN interface of the port VLAN. If the web-based authentication idle timer expires.1x Authentication We recommend that you not configure web-based authentication on the same port as 802. The host is authenticated.Chapter 11 Configuring Web-Based Authentication Understanding Web-Based Authentication LAN Port IP You can configure LAN port IP (LPIP) and Layer 2 web-based authentication on the same port. the web-based authentication host policy overrides the PACL.1x authentication except as a fallback authentication method. you must configure a port ACL (PACL) as the default access policy for ingress traffic from hosts connected to the port. You can configure web-based authentication on the same Layer 3 interface as Gateway IP. the NAC policy is removed. Gateway IP You cannot configure Gateway IP (GWIP) on a Layer 3 VLAN interface if web-based authentication is configured on any of the switch ports in the VLAN. Catalyst 2960 and 2960-S Switches Software Configuration Guide. For Layer 2 web-based authentication. The host policies for both features are applied in software. The LPIP host policy overrides the web-based authentication host policy.

or dynamic trunk ports. page 11-11 Configuring Switch-to-RADIUS-Server Communication. Catalyst 2960 and 2960-S Switches Software Configuration Guide. EtherChannel member ports. You must configure the default ACL on the interface before configuring web-based authentication. Configure a port ACL for a Layer 2 interface or a Cisco IOS ACL for a Layer 3 interface. page 11-10 Configuring the Authentication Rule and Interfaces. These hosts are not detected by the web-based authentication feature because they do not send ARP messages. page 11-15 Removing Web-Based Authentication Cache Entries. page 11-9 Web-Based Authentication Configuration Task List. page 11-16 Default Web-Based Authentication Configuration Table 11-1 shows the default web-based authentication configuration. page 11-11 Configuring the HTTP Server. You can configure web-based authentication only on access ports. By default. Release 15.0(1)SE 11-9 OL-26520-02 . Table 11-1 Default Web-based Authentication Configuration Feature AAA RADIUS server • • • Default Setting Disabled • • • IP address UDP authentication port Key None specified 1812 None specified Default value of inactivity timeout Inactivity timeout 3600 seconds Enabled Web-Based Authentication Configuration Guidelines and Restrictions • • • • • • Web-based authentication is an ingress-only feature. page 11-9 Web-Based Authentication Configuration Guidelines and Restrictions. You must enable the IP device tracking feature to use web-based authentication. The HTTP server sends the HTTP login page to the host. page 11-13 Configuring the Web-Based Authentication Parameters. You must also configure routes to reach each host IP address. You cannot authenticate hosts on Layer 2 interfaces with static ARP cache assignment. page 11-10 Configuring AAA Authentication. Web-based authentication is not supported on trunk ports. the IP device tracking feature is disabled on a switch.Chapter 11 Configuring Web-Based Authentication Configuring Web-Based Authentication Configuring Web-Based Authentication • • • • • • • • • Default Web-Based Authentication Configuration. You must configure at least one IP address to run the switch HTTP server.

(Optional) Save your entries in the configuration file. You cannot use web-based authentication when NEAT is enabled on an interface.Chapter 11 Configuring Web-Based Authentication Configuring Web-Based Authentication • Hosts that are more than one hop away might experience traffic disruption if an STP topology change results in the host traffic arriving on a different port. Return to configuration mode.0(1)SE OL-26520-02 11-10 . gigabit ethernet. page 11-15 Removing Web-Based Authentication Cache Entries. This occurs because the ARP and DHCP updates might not be sent after a Layer 2 (STP) topology change. Configures web-based authentication on the specified interface. page 11-10 Configuring AAA Authentication. and you cannot use NEAT when web-based authentication is running on an interface. Enables the IP device tracking table. page 11-16 Configuring the Authentication Rule and Interfaces Command Step 1 Step 2 Purpose Configure an authentication rule for web-based authorization. page 11-15 Configuring the Web-Based Authentication Parameters. Enter interface configuration mode and specifies the ingress Layer 2 or Layer 3 interface to be enabled for web-based authentication. Web-based authentication does not support VLAN assignment as a downloadable-host policy. ip admission name name proxy http interface type slot/port Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 ip access-group name ip admission name exit ip device tracking end show ip admission configuration copy running-config startup-config This example shows how to enable web-based authentication on Fast Ethernet port 5/1: Switch(config)# ip admission name webauth1 proxy http Switch(config)# interface fastethernet 5/1 Switch(config-if)# ip admission webauth1 Switch(config-if)# exit Switch(config)# ip device tracking Catalyst 2960 and 2960-S Switches Software Configuration Guide. or tengigabitethernet. page 11-11 Configuring the HTTP Server. Apply the default ACL. Web-based authentication is not supported for IPv6 traffic. type can be fastethernet. Display the configuration. Release 15. Web-based authentication and Network Edge Access Topology (NEAT) are mutually exclusive. page 11-13 Configuring the Web-Based Authentication Parameters. Return to privileged EXEC mode. • • • Web-Based Authentication Configuration Task List • • • • • • • Configuring the Authentication Rule and Interfaces. page 11-11 Configuring Switch-to-RADIUS-Server Communication.

Chapter 11 Configuring Web-Based Authentication Configuring Web-Based Authentication This example shows how to verify the configuration: Switch# show ip admission configuration Authentication Proxy Banner not configured Authentication global cache time is 60 minutes Authentication global absolute time is 0 minutes Authentication global init state time is 2 minutes Authentication Proxy Watch-list is disabled Authentication Proxy Rule Configuration Auth-proxy name webauth1 http list not specified inactivity-time 60 minutes Authentication Proxy Auditing is disabled Max Login attempts per user is 5 Configuring AAA Authentication Command Step 1 Step 2 Step 3 Step 4 Purpose Enables AAA functionality. Step 5 Step 6 tacacs-server key {key-data} copy running-config startup-config This example shows how to enable AAA: Switch(config)# aaa new-model Switch(config)# aaa authentication login default group tacacs+ Switch(config)# aaa authorization auth-proxy default group tacacs+ Configuring Switch-to-RADIUS-Server Communication RADIUS security servers identification: • • • • Host name Host IP address Host name and specific UDP port numbers IP address and specific UDP port numbers Catalyst 2960 and 2960-S Switches Software Configuration Guide. (Optional) Save your entries in the configuration file.0(1)SE 11-11 OL-26520-02 . aaa new-model aaa authentication login default group {tacacs+ | radius} aaa authorization auth-proxy default group {tacacs+ Create an authorization method list for web-based | radius} authorization. see the “Configuring Switch-to-RADIUS-Server Communication” section on page 11-11. Defines the list of authentication methods at login. Release 15. Configure the authorization and encryption key used between the switch and the TACACS server. tacacs-server host {hostname | ip_address} Specify an AAA server. For RADIUS servers.

Step 4 radius-server vsa send authentication Step 5 radius-server dead-criteria tries num-tries When you configure the RADIUS server parameters: • • Specify the key string on a separate command line. specify the authentication and encryption key used between the switch and the RADIUS daemon running on the RADIUS server. When you specify the key string. ip radius source-interface interface_name radius-server host {hostname | ip-address} test username username Step 3 radius-server key string Configure the authorization and encryption key used between the switch and the RADIUS daemon running on the RADIUS server.cisco. Specify the number of unanswered sent messages to a RADIUS server before considering the server to be inactive. To use multiple RADIUS servers. The test username username option enables automated testing of the RADIUS server connection. If two different host entries on the same RADIUS server are configured for the same service (for example. and the radius-server key global configuration commands.2(50)SG. use the radius-server timeout. do not enclose the key in quotation marks unless the quotation marks are part of the key. The range of num-tries is 1 to 100.com/en/US/docs/ios/12_2/security/command/reference/fsecur_r. Specify the host name or IP address of the remote RADIUS server. If you want to configure these options on a per-server basis. reenter this command for each server. For more information. use spaces within and at the end of the key. Release 15. To configure the RADIUS server parameters. This feature is supported in Cisco IOS Release 12. that enables RADIUS requests to be sent to multiple UDP ports on a server at the same IP address. The key is a text string that must match the encryption key used on the RADIUS server. For key string. This key must match the encryption used on the RADIUS daemon. see the Cisco IOS Security Configuration Guide and the Cisco IOS Security Command Reference: http://www.html • • Catalyst 2960 and 2960-S Switches Software Configuration Guide. The key option specifies an authentication and encryption key to use between the switch and the RADIUS server. The RADIUS host entries are chosen in the order that they were configured. Enable downloading of an ACL from the RADIUS server. authentication) the second host entry that is configured functions as the failover backup to the first one. If you use spaces in the key. and encryption key values for all RADIUS servers by using with the radius-server host global configuration command. The specified username does not need to be a valid user name. radius-server retransmit.Chapter 11 Configuring Web-Based Authentication Configuring Web-Based Authentication The combination of the IP address and UDP port number creates a unique identifier.0(1)SE OL-26520-02 11-12 . retransmission. You can globally configure the timeout. perform this task: Command Step 1 Step 2 Purpose Specify that the RADIUS packets have the IP address of the indicated interface.

then perform this task in global configuration mode: Command Step 1 Purpose Specify the location in the switch memory file system of the custom HTML file to use in place of the default login page. The device: is flash memory. Enable HTTPS. the login page is always in HTTPS (secure HTTP) even if the user sends an HTTP request. The web-based authentication feature uses the HTTP server to communicate with the hosts for user authentication.l20. the key string to be shared by both the server and the switch. To specify the use of your custom authentication proxy web pages. and the downloadable ACL (DACL). You can enable the server for either HTTP or HTTPS. ip http server ip http secure-server Step 2 You can configure custom authentication proxy web pages or specify a redirection URL for successful login. Command Step 1 Purpose Enable the HTTP server. This example shows how to configure the RADIUS server parameters on a switch: Switch(config)# Switch(config)# Switch(config)# Switch(config)# ip radius source-interface Vlan80 radius-server host 172. see the RADIUS server documentation.Chapter 11 Configuring Web-Based Authentication Configuring Web-Based Authentication Note You need to configure some settings on the RADIUS server. ip admission proxy http login page file device:login-filename ip admission proxy http success page file device:success-filename Step 2 Catalyst 2960 and 2960-S Switches Software Configuration Guide. Release 15. you must enable the HTTP server within the switch. first store your custom HTML files on the switch flash memory.46 test username user1 radius-server key rad123 radius-server dead-criteria tries 2 Configuring the HTTP Server To use web-based authentication.39.0(1)SE 11-13 OL-26520-02 . including: the switch IP address. Specify the location of the custom HTML file to use in place of the default login success page. • • Customizing the Authentication Proxy Web Pages Specifying a Redirection URL for Successful Login Customizing the Authentication Proxy Web Pages You can configure web authentication to display four substitute HTML pages to the user in place of the switch default HTML pages during web-based authentication. Note To ensure secure authentication when you enter the ip http secure-secure command. For more information.

htm Success page : flash:success.htm Authentication global cache time is 60 minutes Authentication global absolute time is 0 minutes Authentication global init state time is 2 minutes Authentication Proxy Session ratelimit is 100 Authentication Proxy Watch-list is disabled Authentication Proxy Auditing is disabled Max Login attempts per user is 5 Catalyst 2960 and 2960-S Switches Software Configuration Guide.htm fail page file flash:fail. The login form must accept user entries for the username and password and must show them as uname and pwd. Because the custom login page is a public web form. a configured auth-proxy-banner is not used.htm login expired page flash flash:expired. Release 15. specify all four custom HTML files.0(1)SE OL-26520-02 11-14 . the redirection URL for successful login feature is not available. consider these guidelines for the page: • • This example shows how to configure custom authentication proxy web pages: Switch(config)# Switch(config)# Switch(config)# Switch(config)# ip ip ip ip admission admission admission admission proxy proxy proxy proxy http http http http login page file flash:login. any name resolution required for external links or images requires configuration of an intercept ACL within the admission rule. T o access a valid DNS server. If you specify fewer than four files. Any images on the custom pages must be on an accessible HTTP server. The maximum size of each HTML file is 8 KB.htm This example shows how to verify the configuration of a custom authentication proxy web pages: Switch# show ip admission configuration Authentication proxy webpage Login page : flash:login. The custom login page should follow best practices for a web form.Chapter 11 Configuring Web-Based Authentication Configuring Web-Based Authentication Command Step 3 Step 4 Purpose Specify the location of the custom HTML file to use in place of the default login failure page. If the custom web pages feature is enabled.htm Login expired Page : flash:expired. ip admission proxy http failure page file device:fail-filename ip admission proxy http login expired page file device:expired-filename When configuring customized authentication proxy web pages. The four custom HTML files must be present on the flash memory of the switch. Specify the location of the custom HTML file to use in place of the default login expired page. use the no form of the command. If the custom web pages feature is enabled.htm Fail Page : flash:fail.htm success page file flash:success. the internal default HTML pages are used. To remove the specification of a custom file. Configure an intercept ACL within the admission rule. such as page timeout. Any external link from a custom page requires configuration of an intercept ACL within the admission rule. follow these guidelines: • • • • • • • • To enable the custom web pages feature. hidden password. and prevention of redundant submissions.

Display the authentication proxy configuration.com Authentication global cache time is 60 minutes Authentication global absolute time is 0 minutes Authentication global init state time is 2 minutes Authentication Proxy Watch-list is disabled Authentication Proxy Max HTTP process is 7 Authentication Proxy Auditing is disabled Max Login attempts per user is 5 Configuring the Web-Based Authentication Parameters You can configure the maximum number of failed login attempts before the client is placed in a watch list for a waiting period.Chapter 11 Configuring Web-Based Authentication Configuring Web-Based Authentication Specifying a Redirection URL for Successful Login You can specify a URL to which the user is redirected after authentication. When configuring a redirection URL for successful login. Returns to privileged EXEC mode. use the no form of the command. Command Step 1 Step 2 Step 3 Step 4 Step 5 Purpose Set the maximum number of failed login attempts. • • This example shows how to configure a redirection URL for successful login: Switch(config)# ip admission proxy http success redirect www.0(1)SE 11-15 OL-26520-02 .cisco. Release 15. the redirection URL feature is disabled and is not available in the CLI.com This example shows how to verify the redirection URL for successful login: Switch# show ip admission configuration Authentication Proxy Banner not configured Customizable Authentication Proxy webpage not configured HTTP Authentication success redirect to URL: http://www. You can perform redirection in the custom-login success page. To remove the specification of a redirection URL. Command ip admission proxy http success redirect url-string Purpose Specify a URL for redirection of the user in place of the default login success page. The default is 5. If the redirection URL feature is enabled. The range is 1 to 2147483647 attempts. (Optional) Save your entries in the configuration file. effectively replacing the internal Success HTML page. consider these guidelines: • If the custom authentication proxy web pages feature is enabled.cisco. ip admission max-login-attempts number end show ip admission configuration show ip admission cache copy running-config startup-config This example shows how to set the maximum number of failed login attempts to 10: Switch(config)# ip admission max-login-attempts 10 Catalyst 2960 and 2960-S Switches Software Configuration Guide. Display the list of authentication entries. a configured auth-proxy-banner is not used.

see the “Authentication Proxy Commands” section of the Cisco IOS Security Command Reference on Cisco.165. Use an asterisk to delete all cache entries.201.1 Catalyst 2960 and 2960-S Switches Software Configuration Guide. Enable the local banner.1: Switch# clear ip auth-proxy cache 209. (Optional) Create a custom banner by entering C banner-text C. Command Step 1 Step 2 Purpose Enter global configuration mode. Use an asterisk to delete all cache entries. Delete authentication proxy entries. a logo or text file) that appears in the banner.0(1)SE OL-26520-02 11-16 . follow these steps to configure a local banner on a switch that has web authentication configured. (Optional) Save your entries in the configuration file.165. Removing Web-Based Authentication Cache Entries Command clear ip auth-proxy cache {* | host ip address} Purpose Delete authentication proxy entries. where C is a delimiting character or a file-path indicates a file (for example. Enter a specific IP address to delete the entry for a single host. Enter a specific IP address to delete the entry for a single host. configure terminal ip admission auth-proxy-banner http [banner-text | file-path] Step 3 Step 4 end copy running-config startup-config This example shows how to configure a local banner with the custom message My Switch: Switch(config) configure terminal Switch(config)# aaa new-model Switch(config)# aaa ip auth-proxy auth-proxy-banner C My Switch C Switch(config) end For more information about the ip auth-proxy auth-proxy-banner command.201.com. clear ip admission cache {* | host ip address} This example shows how to remove the web-based authentication session for the client at the IP address 209. Return to privileged EXEC mode. Release 15.Chapter 11 Configuring Web-Based Authentication Configuring Web-Based Authentication Configuring a Web Authentication Local Banner Beginning in privileged EXEC mode.

Release 15. or tengigabitethernet (Optional) Use the interface keyword to display the web-based authentication settings for a specific interface.Chapter 11 Displaying Web-Based Authentication Status Configuring Web-Based Authentication Displaying Web-Based Authentication Status Perform this task to display the web-based authentication settings for all interfaces or for specific ports: Command Step 1 Purpose Displays the web-based authentication settings. This example shows how to view only the global web-based authentication status: Switch# show authentication sessions show authentication sessions [interface type slot/port] This example shows how to view the web-based authentication settings for gigabit interface 3/27: Switch# show authentication sessions interface gigabitethernet 3/27 Catalyst 2960 and 2960-S Switches Software Configuration Guide. gigabitethernet.0(1)SE 11-17 OL-26520-02 . type = fastethernet.

CH A P T E R 12 Configuring Interface Characteristics This chapter defines the types of Catalyst 2960. and 2960-C interfaces and describes how to configure them. Understanding Interface Types This section describes the different types of supported interfaces with references to chapters that contain more detailed information about configuring these interfaces.4 on Cisco. page 12-17 Using the Ethernet Management Port (Catalyst 2960-S Only). 2960-S.0(1)SE OL-26520-02 12-1 . page 12-1 Using the Switch USB Ports. page 12-4 Power over Ethernet Ports. the term switch refers to a standalone switch and a switch stack. page 12-40 Monitoring and Maintaining the Interfaces. Release 15. see the switch command reference for this release and the Cisco IOS Interface Command Reference. page 12-4 Dual-Purpose Uplink Ports. • • • • • • • • Understanding Interface Types. page 12-42 Note For complete syntax and usage information for the commands used in this chapter. page 12-5 Catalyst 2960 and 2960-S Switches Software Configuration Guide.com. page 12-3 EtherChannel Port Groups. page 12-39 Configuring the System MTU. page 12-22 Configuring Ethernet Interfaces. page 12-11Port-Based VLANs. Release 12. page 12-25 Configuring Layer 3 SVIs. Note The stack ports on the rear of the switch are not Ethernet ports and cannot be configured. page 12-11 Using Interface Configuration Mode. Unless otherwise noted. page 12-2 Switch Virtual Interfaces. • • • • • • Connecting Interfaces. page 12-2 Switch Ports.

A VLAN is a switched network that is logically segmented by function. For detailed information about configuring access port and trunk port characteristics.” Packets received on a port are forwarded only to ports that belong to the same VLAN as the receiving port. You can configure a port as an access port or trunk port or let the Dynamic Trunking Protocol (DTP) operate on a per-port basis to set the switchport mode by negotiating with the port on the other end of the link. The running configuration and the saved configuration are the same for all switches in a stack. and each VLAN has its own MAC address table. VLAN partitions provide hard firewalls for traffic in the VLAN.” Catalyst 2960 and 2960-S Switches Software Configuration Guide. Note Stacking is supported only on Catalyst 2960-S switches running the LAN base image. For more information about VLANs. The VLAN database is downloaded to all switches in a stack. set trunk characteristics. set and define the VLAN to which it belongs. A VLAN comes into existence when you configure a local port to be associated with the VLAN. Switch ports belong to one or more VLANs. With VTP version 3. see the Chapter 13. or when a user creates a VLAN. Add ports to a VLAN by using the switchport interface configuration commands: • • • Identify the interface. you can create extended-range VLANs in client or server mode. you must first set VTP mode to transparent to configure extended-range VLANs (VLAN IDs 1006 to 4094). and. see Chapter 13. These VLANs are saved in the VLAN database. page 12-11 Port-Based VLANs Note Stacking is supported only on Catalyst 2960-S switches running the LAN base image. For an access port. when the VLAN Trunking Protocol (VTP) learns of its existence from a neighbor on a trunk. if desired. without regard to the physical location of the users. A switch port can be an access port or a trunk port.Chapter 12 Understanding Interface Types Configuring Interface Characteristics Connecting Interfaces. “Configuring VLANs. If VTP is version 1 or 2. and all switches in the stack build the same VLAN database. You use switch ports for managing the physical interface and associated Layer 2 protocols. The VLAN configurations for normal-range VLANs (VLAN IDs 1 to 1005) are saved in the VLAN database. Configure switch ports by using the switchport interface configuration commands. use the vlan vlan-id global configuration command to enter VLAN configuration mode. For a trunk port. or application. team.0(1)SE 12-2 OL-26520-02 . “Configuring VLANs. Switch Ports Switch ports are Layer 2-only interfaces associated with a physical port. Network devices in different VLANs cannot communicate with one another without a Layer 3 device to route traffic between the VLANs. To configure VLANs. Extended-range VLANs created in transparent mode are not added to the VLAN database but are saved in the switch running configuration. Release 15. VLANs can be formed with ports across the stack. define the VLANs to which it can belong.

the trunk port automatically becomes a member of that VLAN. the port does not become a member of the VLAN. the packet is dropped. For more information.0(1)SE OL-26520-02 12-3 . You can associate only one SVI with a VLAN. and the source address is not learned. You configure an SVI for a VLAN only to route between VLANs or to provide IP host connectivity to the switch. VLAN membership of dynamic access ports is learned through incoming packets. “Configuring VLANs. a trunk port is a member of every VLAN known to the VTP. For more information about voice VLAN ports. Catalyst 2960 and 2960-S Switches Software Configuration Guide. A packet with a VLAN ID equal to the outgoing port default PVID is sent untagged.1Q trunk ports. All other traffic is sent with a VLAN tag. All untagged traffic and tagged traffic with a NULL VLAN ID belong to the port default PVID. An 802. For more information about trunk ports. If VTP learns of an enabled VLAN that is not in the allowed list for a trunk port. A trunk port can become a member of a VLAN only if VTP knows of the VLAN and if the VLAN is enabled. “Configuring Voice VLAN. Traffic arriving on an access port is assumed to belong to the VLAN assigned to the port. If VTP learns of a new. all possible VLANs (VLAN ID 1 to 4094) are in the allowed list. Although by default.1x). Supported access ports: • Static access ports are manually assigned to a VLAN (or through a RADIUS server for use with IEEE 802. see Chapter 13. The list of allowed VLANs affects only the associated trunk port. enabled VLAN and the VLAN is in the allowed list.1x Authentication with VLAN Assignment” section on page 10-18. By default. By default. see Chapter 15. Traffic is received and sent in native formats with no VLAN tagging. Traffic forwarding to and from the port is enabled only when the port VLAN membership is discovered.1Q tagged packet. Release 15. you can limit VLAN membership by configuring an allowed list of VLANs for each trunk port. Traffic is forwarded to and from the trunk port for that VLAN.1Q trunk port supports simultaneous tagged and untagged traffic. an SVI is created for the default VLAN (VLAN 1) to permit remote switch administration. see the “802. The trunk port is assigned a default port VLAN ID (PVID). By default. • You can also configure an access port with an attached Cisco IP Phone to use one VLAN for voice traffic and another VLAN for data traffic from a device attached to the phone.” Switch Virtual Interfaces A switch virtual interface (SVI) represents a VLAN of switch ports as one interface to the routing or bridging function in the system. The VMPS can be a Catalyst 6500 series switch. The switch supports only 802.Chapter 12 Configuring Interface Characteristics Understanding Interface Types Access Ports An access port belongs to and carries the traffic of only one VLAN (unless it is configured as a voice VLAN port). and traffic for the VLAN is not forwarded to or from the port. 2960-S or 2960-C switch cannot be a VMPS server. and all untagged traffic travels on the port default PVID. The Catalyst 2960. Additional SVIs must be explicitly configured. Dynamic access ports on the switch are assigned to a VLAN by a VLAN Membership Policy Server (VMPS). a dynamic access port is not a member of any VLAN. If an access port receives an 802.” Trunk Ports A trunk port carries the traffic of multiple VLANs and by default is a member of all VLANs in the VLAN database.

you create a port-channel logical interface and assign an interface to the EtherChannel. Use the channel-group interface configuration command to dynamically create the port-channel logical interface. The dual front ends are not redundant interfaces. This command binds the physical and logical ports together. see Chapter 38. Most protocols operate over either single ports or aggregated switch ports and do not recognize the physical ports within the port group. SVIs provide IP host connectivity only to the system. the switch dynamically selects the interface type that first links up. see the “Setting the Interface Speed and Duplex Parameters” section on page 12-29. Each uplink port is considered as a single interface with dual front ends—an RJ-45 connector and a small form-factor pluggable (SFP) module connector.Beginning with Cisco IOS release 12. An EtherChannel port group acts as a single logical port for high-bandwidth connections between switches or between switches and servers. see the “Manually Assigning IP Information” section on page 3-14. An EtherChannel balances the traffic load across the links in the channel. it does not become active until it you associate it with a physical port. For more information. For information about configuring speed and duplex settings for a dual-purpose uplink. the Cisco Discovery Protocol (CDP). you can enable routing and configure static routes on SVIs. The DTP. Note When you create an SVI. and the Port Aggregation Protocol (PAgP) operate only on physical ports. and the switch activates only one connector of the pair.You can group multiple trunk ports into one logical trunk port or multiple access ports into one logical access port. The VLAN corresponds to the VLAN tag associated with data frames on an encapsulated trunk port or the VLAN ID configured for an access port. EtherChannel Port Groups EtherChannel port groups treat multiple switch ports as one switch port.0(1)SE 12-4 OL-26520-02 . “Configuring EtherChannels and Link-State Tracking. For more information. By default. and assign it an IP address.” Dual-Purpose Uplink Ports Note Catalyst 2960-S switches do not have dual-purpose uplink ports. Catalyst 2960 and 2960-S Switches Software Configuration Guide. you can use the media-type interface configuration command to manually select the RJ-45 connector or the SFP module connector. When you configure an EtherChannel. Note Static routing is supported on SVIs only when the switch is running the LAN base image. Some switches support dual-purpose uplink ports. SVIs are created the first time that you enter the vlan interface configuration command for a VLAN interface. However. Release 15.Chapter 12 Understanding Interface Types Configuring Interface Characteristics Note You cannot delete interface VLAN 1. If a link within the EtherChannel fails. Configure a VLAN interface for each VLAN for which you want to route traffic.2(55)SE. traffic previously carried over the failed link changes to the remaining links.

which consumes more than 7 W. For more information about the LEDs.3 at-compliant powered devices (PoE+ on Catalyst 2960-S switches only) A powered device can receive redundant power when it is connected only to a PoE switch port and to an AC power source. The port LED is on for whichever connector is active. and negotiates to obtain enough power to operate in high-power mode. page 12-7 Power Monitoring and Power Policing. The powered device first boots up in low-power mode. see the hardware installation guide. CDP is not supported on third-party powered devices. Release 15. page 12-5 Powered-Device Detection and Initial Power Allocation. The switch does not reply to the power-consumption messages. and one shows the status of the SFP module port. the switch uses the IEEE classification to determine the power usage of the device. Power over Ethernet Ports Note PoE is supported only when the switch is running the LAN base image. Power over Ethernet Plus (PoE+) is supported only on Catalyst 2960-S switches. to operate at its highest power mode. PoE switch ports automatically supply power to these connected devices (if the switch senses that there is no power on the circuit): • • • Cisco pre-standard powered devices (such as Cisco IP Phones and Cisco Aironet access points) IEEE 802. consumes less than 7 W.0(1)SE OL-26520-02 12-5 . Cisco intelligent power management—The powered device and the switch negotiate through power-negotiation CDP messages for an agreed power-consumption level. page 12-6 Power Management Modes. The device changes to high-power mode only when it receives confirmation from the switch. Cisco intelligent power management is backward-compatible with CDP with power consumption. High-power devices can operate in low-power mode on switches that do not support power-negotiation CDP. • Catalyst 2960 and 2960-S Switches Software Configuration Guide. After the switch detects a powered device. The negotiation allows a high-power Cisco powered device. the switch responds according to the CDP message that it receives. The switch can only supply power to or remove power from the PoE port. This section has this PoE information: • • • • Supported Protocols and Standards.Chapter 12 Configuring Interface Characteristics Understanding Interface Types Each uplink port has two LEDs: one shows the status of the RJ-45 port.3 af-compliant powered devices IEEE 802. page 12-8 Supported Protocols and Standards The switch uses these protocols and standards to support PoE: • CDP with power consumption—The powered device notifies the switch of the amount of power it is consuming. it determines the device power requirements and then grants or denies power to the device. therefore. The switch can also sense the real-time power consumption of the device by monitoring and policing the power usage.

For more information. disconnect detection.4 W 30 W PoE+ devices only The switch monitors and tracks requests for power and grants power only when it is available. IEEE Power Classifications Table 12-1 Class 0 (class status unknown) 1 2 3 4 Maximum Power Level Required from the Switch 15.1af and increases the maximum power available on each PoE port from 15. the initial power allocation might be adjusted. After power is applied to the port. The initial power allocation is the maximum amount of power that a powered device requires. Based on the available power in the power budget. Catalyst 2960 and 2960-S Switches Software Configuration Guide. generates a syslog message. As the switch receives CDP messages from the powered device and as the powered device negotiates power levels with the switch through CDP power-negotiation messages. and optional powered-device power classification.3at —This PoE+ standard supports all the features of 802.4 W as the initial allocation for power budgeting. If the request is granted. and updates the LEDs. and the switch adjusts the power budget accordingly. IEEE 802. and the connected device is not being powered by an AC adaptor.4 W 4W 7W 15. If the request is denied. This does not apply to third-party PoE devices. the switch updates the power budget. a PoE+ switch allocates 30 W (PoE+). power administration.0(1)SE 12-6 OL-26520-02 . the switch ensures that power to the port is turned off. PoE is enabled (the default). the switch determines if a port can be powered. The switch initially allocates this amount of power when it detects and powers the powered device. Powered-Device Detection and Initial Power Allocation The switch detects a Cisco pre-standard or an IEEE-compliant powered device when the PoE-capable port is in the no-shutdown state. the switch uses CDP to determine the actual power consumption requirement of the connected Cisco powered devices. The switch tracks its power budget (the amount of power available on the switch for PoE). • The switch classifies the detected IEEE device within a power consumption class. The switch processes a request and either grants or denies power. Powered devices can also negotiate with the switch for more power.Chapter 12 Understanding Interface Types Configuring Interface Characteristics • IEEE 802. Table 12-1 lists these levels.3af—The major features of this standard are powered-device discovery. The switch performs power-accounting calculations when a port is granted or denied power to keep the power budget up to date. see the standard. After device detection. • Note Only Catalyst 2960-S or 2960-C switches support IEEE 802.3at. Release 15.4 W to 30 W. the switch determines the device power requirements based on its type: • A Cisco prestandard powered device does not provide its power requirement when the switch detects it. so a switch that does not support PoE+ allocates 15.

overtemperature. If there is not enough available PoE. and the amount is never adjusted through the IEEE class or by CDP messages from the powered device. updates the power budget. If the IEEE class maximum wattage of the powered device is greater than the configured maximum value. If the switch discovers a powered device connected to the port and if the switch has enough power. the switch denies power. Catalyst 2960 and 2960-S Switches Software Configuration Guide. the switch automatically detects the disconnect and removes power from the port. If enough power is available for all powered devices connected to the switch. the switch pre-allocates the maximum value. If granting power would exceed the system power budget. oscillator-fault. and updates the power budget and LEDs. or short-circuit condition. You can specify the maximum wattage that is allowed on the port. the switch periodically rechecks the power budget and continues to attempt to grant the request for power. the switch does not provide power to the port. If the switch powers a powered device. Election of a new stack master does not affect PoE operation. overvoltage. power is turned on to all devices. If a device being powered by the switch is then connected to wall power. If the switch has enough power for all the powered devices. the PoE feature operates the same whether or not the switch is a stack member. and updates the LEDs. The stack master keeps track of PoE status for all switches and ports in the stack and includes the status in output displays. generates a syslog message. they all come up. see the hardware installation guide. The auto mode is the default setting. it turns off power to the port. turns on power to the port on a first-come. Use the auto setting on any PoE port. Release 15. If you do not specify a wattage. first-served basis. The switch might continue to report that it is still powering the device whether the device is being powered by the switch or receiving power from an AC power source. and updates the LEDs. • static—The switch pre-allocates power to the port (even when no powered device is connected) and guarantees that power will be available for the port.Chapter 12 Configuring Interface Characteristics Understanding Interface Types If the switch detects a fault caused by an undervoltage. if the powered-device IEEE class is greater than the maximum wattage. the switch might continue to power the device. In a Catalyst 2960-S switch stack. The switch powers the port only if it discovers a powered device. the switch does not supply power to it. If a powered device is removed. generates a syslog message. but the powered device later requests through CDP messages more than the configured maximum value. Use the static setting on a high-priority interface. Because power is pre-allocated. any powered device that uses less than or equal to the maximum wattage is guaranteed to be powered when it is connected to the static port. ensures that power to the port is turned off. it cannot be determined which devices are granted or are denied power. The switch allocates the port configured maximum wattage. it grants power. the switch delivers the maximum value. Power Management Modes Supported PoE modes: • auto—The switch automatically detects if the connected device requires power. the switch removes power to the port. If you do not specify a wattage. For LED information. first-served model. or if a device is disconnected and reconnected while other devices are waiting for power. After power has been denied. If the switch learns through CDP messages that the powered device needs more than the maximum wattage. The power that was allocated to the powered device is reclaimed into the global power budget. However. You can connect a nonpowered device without damaging it.0(1)SE OL-26520-02 12-7 . The power budget is per-switch and independent of any other switch in the stack. the powered device is shutdown. The port no longer participates in the first-come.

It works with these features to ensure that the PoE port can supply power to the powered device. also referred to as the cutoff power. this is called power monitoring or power sensing. making the port a data-only port. If the device uses more than the maximum power allocation on the port. you can manually re-enable the PoE port by using the shutdown and no shutdown interface configuration commands. 2. Maximum Power Allocation (Cutoff Power) on a PoE Port When power policing is enabled.Chapter 12 Understanding Interface Types Configuring Interface Characteristics • never—The switch disables powered-device detection and never powers the PoE port even if an unpowered device is connected. Release 15. no action occurs when the powered device consumes more than the maximum power allocation on the PoE port. the switch senses the real-time power consumption of the powered device and monitors the power consumption of the connected powered device. the switch automatically takes the PoE port out of the error-disabled state after the specified amount of time. For information on configuring a PoE port. The switch records the power consumption. the switch polices power usage by comparing the real-time power consumption to the maximum power allocated to the device. also referred to as the cutoff-power value. the switch can either turn off power to the port. If error recovery is disabled. see the “Powered-Device Detection and Initial Power Allocation” section on page 12-6. If policing is disabled.0(1)SE 12-8 OL-26520-02 . CISCO-POWER-ETHERNET-EXT-MIB. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Manually when you set the user-defined power level that the switch budgets for the port by using the power inline consumption default wattage global or interface configuration command Manually when you set the user-defined power level that limits the power allowed on the port by using the power inline auto max max-wattage or the power inline static max max-wattage interface configuration command Automatically when the switch sets the power usage of the device by using CDP power negotiationor by the IEEE classification and LLDP power negotiation. Power Monitoring and Power Policing When policing of the real-time power consumption is enabled. the switch takes action when a powered device consumes more power than the maximum amount allocated. including peak power usage. 3. The switch monitors the real-time power consumption on individual ports. and reports the information through an SNMP MIB. power-usage policing is disabled on all PoE ports. When PoE is enabled. The switch senses the power consumption of the connected device as follows: 1. Use this mode only when you want to make sure power is never applied to a PoE-capable port. 2. which could adversely affect the switch. By default. If power policing is enabled. The switch also uses the power policing feature to police the power usage. Power monitoring is backward-compatible with Cisco intelligent power management and CDP-based power consumption. the switch determines the cutoff power on the PoE port in this order: 1. on a PoE port. If error recovery from the PoE error-disabled state is enabled. see the “Configuring a Power Management Mode on a PoE Port” section on page 12-32. 3. For more information about the maximum power consumption. For more information about these PoE features. or the switch can generate a syslog message and update the LEDs (the port LED is now blinking amber) while still providing power to the device based on the switch configuration. see the “Maximum Power Allocation (Cutoff Power) on a PoE Port” section on page 12-8. 4.

For example. which is 0. If CDP is disabled after the switch has locked on it. If you do not manually configure the cutoff-power value.5 W).4 W without CDP or LLDP negotiation. the device might be in violation of the maximum current (Imax) limitation and might experience an Icut fault for drawing more current than the maximum.3 W (6300 mW). the configured maximum power allocation on the PoE port is 6. it uses the default value of 15. Release 15. When you manually set the maximum power allocation. it does not provide power to devices that send LLDP requests. Catalyst 2960 and 2960-S Switches Software Configuration Guide. When power policing is enabled. the switch polices the power usage at the switch port. and the device can consume more power than the maximum allocated amount. the cycle repeats. The switch provides power to the connected devices on the port if the device needs up to 6. The actual amount of power consumed by a powered device on a PoE port is the cutoff-power value plus a calibration factor of 500 mW (0. However. For example.4 W. The cutoff power is the sum of the rated power consumption of the powered device and the worst-case power loss over the cable. the switch automatically determines it by using CDP power negotiation or the device IEEE classification and LLDP power negotiation. the switch does not allow devices to consume more than 15. if you do not manually configure the cutoff-power value. the switch does not police the real-time power consumption of the device.4 W of power because values from 15400 to 30000 mW are only allocated based on CDP or LLDP requests. However without CDP or LLDP. you should restart the powered device. which is greater than the power consumption of the device. if the configured cutoff power is 12 W. In this case. you must consider the power loss over the cable from the switch port to the powered device. If a powered device consumes more than 15. The actual cutoff power value that the switch uses for power policing is not equal to the configured power value. Power Consumption Values You can configure the initial power allocation and the maximum power allocation on a port.05% less than the configured value. On a switch with PoE+. The port remains in the fault state for a time before attempting to power on again. After the switch turns on power to the PoE port. If the CDP-power negotiated value or the IEEE classification value exceeds the configured cutoff value. the switch locks to the power-negotiation protocol of that first packet and does not respond to power requests from the other protocol. the actual cutoff-value is 11. Note When a powered device connected to a PoE+ port restarts and sends a CDP or LLDP packet with a power TLV.4 W. if policing is disabled and you set the cutoff-power value by using the power inline auto max 6300 interface configuration command.0(1)SE OL-26520-02 12-9 . the default value of 30 W is applied.3 W. We recommend that you enable power policing when PoE is enabled on your switch. The actual cutoff value is approximate and varies from the configured value by a percentage of the configured value. the switch does not respond to LLDP power requests and can no longer power on any accessories.4 W. The maximum power allocation is not the same as the actual power consumption of the powered device. the switch does not provide power to the connected device. these values are only the configured values that determine when the switch should turn on or turn off power on the PoE port.Chapter 12 Configuring Interface Characteristics Understanding Interface Types Use the first or second method in the previous list to manually configure the cutoff-power value by entering the power inline consumption default wattage or the power inline [auto | static max] max-wattage command. If the port continuously draws more than 15. If the switch cannot determine the value by using one of these methods. For example. if the switch is locked to CDP. the switch automatically determines the value by using CDP power negotiation. If CDP or LLDP are not enabled. which could adversely affect the switch and the devices connected to the other PoE ports.

If the new power supply supports more power than the previous one and the switch now has more power available. PoE Uplinks and PoE Pass-Through Capability The Catalyst 2960-C compact switch can receive power on the two uplink Gigabit Ethernet ports from a PoE or PoE+ capable-switch (for example a Catalyst 3750-X or 3560-X switch). video cameras.0(1)SE 12-10 OL-26520-02 .8 W 30 W 45. it denies power to the PoE ports in static mode in descending order of the port numbers. • If a power supply is removed and replaced by a new power supply with less power and the switch does not have enough power for the powered devices.4 W 22. If the switch still does not have enough power. the power budget is similar to that of any other PoE switch. see the “Configuring Power Policing” section on page 12-35. If it still has power available.4 W For information about configuring these ports. Release 15. the switch then grants power to the PoE ports in auto mode in ascending order of the port numbers. The Catalyst 2960CPD-8PT switch can provide power to end devices through the eight downlink ports in one of two ways: • When the switch receives power from the auxiliary power input. it acts like any other PoE switch and can supply power to end devices connected to the eight downlink ports according to the total power budget. the power budget (the available power on downlink ports) depends on the power source options shown in the table. the total amount of power available for the powered devices varies depending on the power supply configuration. the auxiliary power input takes precedence. and access points. When the switch draws power from the uplink ports.Chapter 12 Understanding Interface Types Configuring Interface Characteristics Because the switch supports internal power supplies and the Cisco Redundant Power System 2300 (also referred to as the RPS 2300). The available power depends on the power drawn from the uplink ports and varies. When the switch receives power through the auxiliary connector.4 W per port to a connected powered device. depending if one or both uplink ports are connected and if the source is PoE or PoE+.4 W 22. it can provide PoE pass-through. • The downlink ports are PoE-capable. Possible end devices are IP phones. The switch can also receive power from an AC power source when you use the auxiliary power input. • For configuration information. When both uplink ports and auxiliary power are connected. see the “Configuring Catalyst PoE and PoE Pass-Through Ports on Compact Switches” section on page 12-37. taking the surplus power from the PoE or PoE+ uplinks and passing it through the downlink ports to end devices.4 W 30. the switch grants power to the PoE ports in static mode in ascending order of the port numbers. and each port can supply up to 15.4 W 60 W — 0 7W 7W 15. When the switch receives power through one or both uplink ports. Table 12-2 Catalyst 2960CPD-8PT Power Budget Power Source Options 1 PoE uplink port 2 PoE uplink ports 1 PoE+ uplink port 1 PoE and 1 PoE+ uplink 2 PoE+ uplink ports Auxiliary power input Power Sent from Uplink Switches Available PoE Budget 15. the switch denies power to the PoE ports that are in auto mode in descending order of the port numbers. Catalyst 2960 and 2960-S Switches Software Configuration Guide.

Release 15. when you configure both VLAN 20 and VLAN 30 with an SVI to which an IP address is assigned. back to the switch. the data must go from Host A to the switch. By using the switch with routing enabled. ports in different VLANs have to exchange information through a router. Catalyst 2960 and 2960-S Switches Software Configuration Guide. page 12-14 The Catalyst Fast Ethernet switches (Catalyst 2960CPD-8PT-L and the 2960CPD-8TT-L switches) have only the USB mini-Type B console port. page 12-12 USB Type A Port. packets can be sent from Host A to Host B directly through the switch with no need for an external router (Figure 12-1). Figure 12-1 Connecting VLANs with Layer 2 Switches Cisco router Switch Host A Host B VLAN 20 VLAN 30 With a standard Layer 2 switch.Chapter 12 Configuring Interface Characteristics Using the Switch USB Ports Connecting Interfaces Devices within a single VLAN can communicate directly through any switch. to the router. The Catalyst 2960-S and Catalyst 2960-C Gigabit Ethernet switches have two USB ports on the front panel: • • USB Mini-Type B Console Port. when Host A in VLAN 20 sends data to Host B in VLAN 30. and then to Host B. Using the Switch USB Ports Note USB ports are supported only on Catalyst 2960-S and 2960-C switches.0(1)SE OL-26520-02 46647 12-11 . Ports in different VLANs cannot exchange data without going through a routing device. In the configuration shown in Figure 12-1.

and you can configure an inactivity timeout for the USB connector. switch-stack-3) *Mar 1 00:01:10.523: %USB_CONSOLE-6-MEDIA_RJ45: Console media-type is RJ45.835: %USB_CONSOLE-6-MEDIA_RJ45: Console media-type is RJ45. switch 1 has a connected USB console cable. Switch 2 and switch 3 have connected RJ-45 console cables. the console changes and the USB console log appears. You can configure the console type to always be RJ-45. Use the supplied USB Type A-to-USB mini-Type B cable to connect a PC or other device to the switch. *Mar 1 00:01:00. When the USB cable is removed or the PC de-activates the USB connection. switch-stack-2 *Mar 1 00:01:09. Because the bootloader did not change to the USB console. An LED on the switch shows which console connection is in use. The connected device must include a terminal emulation application. switch-stack-1 *Mar 1 00:01:00. Every switch always first displays the RJ-45 media type. Console Port Change Logs At software startup. input from the RJ-45 console is immediately disabled. Removing the USB connection immediately reenables input from the RJ-45 console connection. When the switch detects a valid USB connection to a powered-on device that supports host functionality (such as a PC). Each switch in a 2960-S stack issues this log. a log shows whether the USB or the RJ-45 console is active. but console input is active on only one port at a time.0(1)SE 12-12 OL-26520-02 . Note Windows PCs require a driver for the USB port. and input from the USB console is enabled. the first log from switch 1 shows the RJ-45 console.171: %USB_CONSOLE-6-MEDIA_RJ45: Console media-type is RJ45.635: %USB_CONSOLE-6-MEDIA_RJ45: Console media-type is RJ45. Console output appears on devices connected to both ports. In the sample output. Catalyst 2960 and 2960-S Switches Software Configuration Guide. See the hardware installation guide for driver installation instructions.Chapter 12 Using the Switch USB Ports Configuring Interface Characteristics USB Mini-Type B Console Port The switch has two console ports available—a USB mini-Type B console connection and an RJ-45 console port. A short time later. Release 15.431: %USB_CONSOLE-6-MEDIA_USB: Console media-type is USB. The USB connector takes precedence over the RJ-45 connector. the hardware automatically changes to the RJ-45 console interface: switch-stack-1 Mar 1 00:20:48.

This configuration applies to all switches in a stack. Switch# configure terminal Switch(config)# line console 0 Switch(config-line)# no media-type rj45 Configuring the USB Inactivity Timeout The configurable inactivity timeout reactivates the RJ-45 console port if the USB console port is activated but no input activity occurs on it for a specified time period. If you configure the RJ-45 console. Switch# configure terminal Switch(config)# line console 0 Switch(config-line)# media-type rj45 This configuration terminates any active USB console media type in the stack. (switch-stk-2) This example reverses the previous configuration and immediately activates any USB console that is connected. Configure the console.498: %USB_CONSOLE-6-CONFIG_DISALLOW: Console media-type USB is disallowed by system configuration.860: %USB_CONSOLE-6-CONFIG_DISABLE: Console media-type USB disabled by system configuration. Note The configured inactivity timeout applies to all switches in a stack.Chapter 12 Configuring Interface Characteristics Using the Switch USB Ports Configuring the Console Media Type Beginning in privileged EXEC mode. A log entry shows when a console cable is attached. Catalyst 2960 and 2960-S Switches Software Configuration Guide. *Mar 1 00:34:27. Return to privileged EXEC mode. This example shows that the console on switch 1 reverted to RJ-45. If you do not enter this command and both types are connected. At this point no switches in the stack allow a USB console to have input. configure terminal line console 0 media-type rj45 end show running-configuration copy running-config startup-config This example disables the USB console media type and enables the RJ-45 console media type. media-type reverted to RJ45. If a USB console cable is connected to switch 2. *Mar 1 00:25:36. A log shows that this termination has occurred. media-type remains RJ45. When the USB console port is deactivated due to a timeout. Verify your settings. you can restore its operation by disconnecting and reconnecting the USB cable.0(1)SE OL-26520-02 12-13 . However. Configure the console media type to always be RJ-45. USB console operation is disabled. follow these steps to select the RJ-45 console media type. a timeout on one switch does not cause a timeout on other switches in the stack. and input always remains with the RJ-45 console. (Optional) Save your entries in the configuration file. Enter line configuration mode. Release 15. Command Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Purpose Enter global configuration mode. the default is USB. it is prevented from providing input.

640: %USB_CONSOLE-6-MEDIA_USB: Console media-type is USB. 256 MB. Beginning in privileged EXEC mode.0(1)SE 12-14 OL-26520-02 . (Optional) Save your entries in the configuration file. the only way to reactivate the USB console port is to disconnect and reconnect the cable. and a log shows this occurrence: *Mar 1 00:47:25. Verify your setting. Release 15. write. The switch supports Cisco 64 MB.line interface (CLI) commands to read. follow these steps to allow booting from the USB flash device. At this point. Catalyst 2960 and 2960-S Switches Software Configuration Guide. a log similar to this appears: *Mar 1 00:48:28. follow these steps to configure an inactivity timeout. use these commands: Switch#(config)# line console 0 Switch#(config-line)# no usb-inactivity-timeout If there is no (input) activity on a USB console port for the configured number of minutes. Specify an inactivity timeout for the console port. When the USB cable on the switch has been disconnected and reconnected. also known as thumb drives or USB keys. Configure the switch to boot from the USB flash device. Command Step 1 Step 2 Step 3 Step 4 Step 5 Purpose Enter global configuration mode. configure terminal line console 0 usb-inactivity-timeout timeout-minutes show running-configuration copy running-config startup-config This example configures the inactivity timeout to 30 minutes: Switch# configure terminal Switch#(config)# line console 0 Switch#(config-line)# usb-inactivity-timeout 30 To disable the configuration. configure terminal boot system flash usbflash0: image show running-configuration copy running-config startup-config To get information about the USB device. 512 MB and 1 GB flash drives. Enter console line configuration mode.Chapter 12 Using the Switch USB Ports Configuring Interface Characteristics Beginning in privileged EXEC mode. and copy to or from the flash device. You can also configure the switch to boot from the USB flash drive. The range is 1 to 240 minutes. media-type reverted to RJ45. (Optional) Save your entries in the configuration file. Verify your setting. USB Type A Port The USB Type A port provides access to external USB flash devices. The image is the name of the bootable image. the inactivity timeout setting applies to the RJ-45 port. Configure the console port. use the show usb {controllers | device | driver | port | tree} privileged EXEC command. erase. Command Step 1 Step 2 Step 3 Step 4 Purpose Enter global configuration mode. The default is to have no timeout configured.625: %USB_CONSOLE-6-INACTIVITY_DISABLE: Console media-type USB disabled due to inactivity. You can use standard Cisco IOS command.

Chapter 12 Configuring Interface Characteristics Using the Switch USB Ports This example configures the switch to boot from the Catalyst 2960-S flash device.0 Serial Number: STI 3D508232204731 Device Handle: 0x1010000 USB Version Compliance: 2. enter the no form of the command. This is sample output from the show usb device command: Switch# show usb device Host Controller: 1 Address: 0x1 Device Configured: YES Device Supported: YES Description: STEC USB 1GB Manufacturer: STEC Version: 1. Release 15.0(1)SE OL-26520-02 12-15 . Packet Size of Endpoint Zero: 64 Number of Configurations: 1 Speed: High Selected Configuration: 1 Selected Interface: 0 Configuration: Number: 1 Number of Interfaces: 1 Description: Storage Attributes: None Max Power: 200 mA Interface: Number: 0 Description: Bulk Class Code: 8 Subclass: 6 Protocol: 80 Number of Endpoints: 2 Endpoint: Number: 1 Transfer Type: BULK Transfer Direction: Device to Host Max Packet: 512 Interval: 0 Endpoint: Number: 2 Transfer Type: BULK Transfer Direction: Host to Device Max Packet: 512 Interval: 0 Catalyst 2960 and 2960-S Switches Software Configuration Guide. The image is the Catalyst 2960-S LAN base image.0 Class Code: 0x0 Subclass Code: 0x0 Protocol: 0x0 Vendor ID: 0x136b Product ID: 0x918 Max. Switch# configure terminal Switch#(config)# boot system flash usbflash0: c2960s-lanbase-mz To disable booting from flash.

0(1)SE 12-16 OL-26520-02 . Release 15.Chapter 12 Using the Switch USB Ports Configuring Interface Characteristics This is sample output from the show usb port command: Switch# show usb port Port Number: 0 Status: Enabled Connection State: Connected Speed: High Power State: ON Catalyst 2960 and 2960-S Switches Software Configuration Guide.

particularly regarding the presence of a stack member number. The default switch number. Module number—The module or slot number on the switch (always 0). Catalyst 2960 and 2960-S Switches Software Configuration Guide. before it is integrated into a switch stack. 10-Gigabit Ethernet (tengigabitethernet or te) for 10. for example. SFP module ports are numbered consecutively following the 10/100/1000 ports. specify the interface type. it keeps that number until another is assigned to it. Stack member number—The number that identifies the switch within the stack. and enter interface configuration mode. module number. For a switch with 10/100/1000 ports and SFP module ports. To configure a physical interface (port) on a Catalyst 2960 or 2960-C switch or a Catalyst 2960-S switch running the LAN Lite image. When a switch has been assigned a stack member number. You can use the switch port LEDs in Stack mode to identify the stack member number of a switch. enter this command: Switch(config)# interface gigabitethernet3/0/4 This example identifies an interface on a Catalyst 2960 or 2960-C switch or a Catalyst 2960-S switch running the LAN Lite image: • To configure 10/100/1000 port 4. You can also use the show privileged EXEC commands to display information about a specific interface or all the interfaces. gigabitethernet1/0/1. Release 15. enter this command: Switch(config)# interface gigabit tethernet1/0/4 • To configure 10/100 port 4 on stack member 3. is 1. module number. enter this command: Switch(config)# interface gigabitethernet0/4 Note Configuration examples and outputs in this book might not be specific to your switch. The switch number range is 1 to 4 and is assigned the first time the switch initializes. specify the interface type.0(1)SE OL-26520-02 12-17 . and enter interface configuration mode. • • • You can identify physical interfaces by looking at the switch. Gigabit Ethernet (gigabitethernet or gi) for 10/100/1000 Mb/s Ethernet ports. The port numbers always begin at 1. These examples identify interfaces on a Catalyst 2960-S switch running the LAN base image: • To configure 10/100/1000 port 4 on a standalone switch. and switch port number. stack member number. The remainder of this chapter primarily provides physical interface configuration procedures. and switch port number. or small form-factor pluggable (SFP) module Gigabit Ethernet interfaces. Port number—The interface number on the switch. To configure a port on a Catalyst 2960-S switch running the LAN base image (supporting stacking). Possible types are: Fast Ethernet (fastethernet or fa) for 10/100 Mb/s Ethernet. • Type—Port types depend on those supported on the switch.Chapter 12 Configuring Interface Characteristics Using Interface Configuration Mode Using Interface Configuration Mode The switch supports these interface types: • • • Physical ports—switch ports VLANs—switch virtual interfaces Port channels—EtherChannel interfaces You can also configure a range of interfaces (see the “Configuring a Range of Interfaces” section on page 12-19). starting with the far left port when facing the front of the switch.000 Mb/s.

A report is provided for each interface that the device supports or for the specified interface. and the interface number. Switch(config)# Step 2 Enter the interface global configuration command. Gigabit Ethernet port 1 in this example: Switch(config)# interface gigabitethernet1/0/1 Switch(config-if)# Note Step 3 Entering a space between the interface type and interface number is optional Follow each interface command with the configuration commands that the interface requires. verify its status by using the show privileged EXEC commands listed in the “Monitoring and Maintaining the Interfaces” section on page 12-42.Chapter 12 Using Interface Configuration Mode Configuring Interface Characteristics Procedures for Configuring Interfaces These general instructions apply to all interface configuration processes. The commands that you enter define the protocols and applications that will run on the interface. the switch number. Identify the interface type. End with CNTL/Z. The commands are collected and applied to the interface when you enter another interface command or enter end to return to privileged EXEC mode. Step 1 Enter the configure terminal command at the privileged EXEC prompt: Switch# configure terminal Enter configuration commands. Step 4 After you configure an interface. In this example. Release 15.0(1)SE 12-18 OL-26520-02 . Enter the show interfaces privileged EXEC command to see a list of all interfaces on or configured for the switch. Catalyst 2960 and 2960-S Switches Software Configuration Guide. You can also configure a range of interfaces by using the interface range or interface range macro global configuration commands. one per line. Interfaces configured in a range must be the same type and must be configured with the same feature options. Gigabit Ethernet port 1 on switch 1 is selected: Identify the interface type and the interface number.

{last port}. and enter interface-range configuration mode. Catalyst 2960 and 2960-S Switches Software Configuration Guide. In a hyphen-separated port-range. – gigabitethernet stack member/module/{first port} . these options are not supported on Catalyst 2960 and 2960-S switches. Step 3 Use the normal configuration commands to apply the configuration parameters to all interfaces in the range. depending on port types on the switch: – vlan vlan-ID. Each command is executed as it is entered. Specify the range of interfaces (VLANs or physical ports) to be configured. but you must enter a space before the hyphen.{last port}. where the module is always 0 – port-channel port-channel-number . you must enter the interface type for each entry and enter spaces before and after the comma. Verify the configuration of the interfaces in the range.port-channel-number. Release 15. Step 4 Step 5 Step 6 When using the interface range global configuration command. all command parameters that you enter are attributed to all interfaces within that range until you exit this mode. In a comma-separated port-range. The macro variable is explained in the “Configuring and Using Interface Range Macros” section on page 12-20. (Optional) Save your entries in the configuration file. the first and last port-channel number must be active port channels. • • • • configure terminal interface range {port-range | macro macro_name} You can use the interface range command to configure up to five port ranges or a previously defined macro.Chapter 12 Configuring Interface Characteristics Using Interface Configuration Mode Configuring a Range of Interfaces You can use the interface range global configuration command to configure multiple interfaces with the same configuration parameters. where the VLAN ID is 1 to 4094 Note Although the command-line interface shows options to set multiple VLANs. where the module is always 0 – fastethernet module/{first port} .0(1)SE OL-26520-02 12-19 . end show interfaces [interface-id] copy running-config startup-config Return to privileged EXEC mode. you do not need to re-enter the interface type. note these guidelines: • Valid entries for port-range. where the module is always 0 – gigabitethernet module/{first port} . follow these steps to configure a range of interfaces with the same parameters: Command Step 1 Step 2 Purpose Enter global configuration mode. When you enter the interface-range configuration mode. where the port-channel-number is 1 to 6 Note When you use the interface range command with port channels. Beginning in privileged EXEC mode.{last port}.

but you can enter multiple ranges in a command.3. Release 15. follow these steps to define an interface range macro: Command Step 1 Step 2 Purpose Enter global configuration mode. and save it in NVRAM. all EtherChannel ports. each command is executed as it is entered. interface range gigabitethernet0/1-4 is not. gigabitethernet1/0/1 . Catalyst 2960 and 2960-S Switches Software Configuration Guide.Chapter 12 Using Interface Configuration Mode Configuring Interface Characteristics • You must add a space between the first interface number and the hyphen when using the interface range command.2 Switch(config-if-range)# flowcontrol receive on If you enter multiple configuration commands while you are in interface-range mode. VLAN interfaces not displayed by the show running-config command cannot be used with the interface range command. For example. Before you can use the macro keyword in the interface range macro global configuration command string. interface range gigabitethernet 0/1 .4 is a valid range. or all VLANs). interface range gigabitethernet1/0/1 . • • • configure terminal define interface-range macro_name interface-range The macro_name is a 32-character maximum character string. some commands might not be executed on all interfaces in the range. Configuring and Using Interface Range Macros You can create an interface range macro to automatically select a range of interfaces for configuration. The show running-config privileged EXEC command displays the configured VLAN interfaces. Wait until the command prompt reappears before exiting interface-range configuration mode. • This example shows how to use the interface range global configuration command to set the speed on ports 1 to 2 to 100 Mb/s: Switch# configure terminal Switch(config)# interface range gigabitethernet1/0/1 . All interfaces defined in a range must be the same type (all Fast Ethernet ports. all Gigabit Ethernet ports. Beginning in privileged EXEC mode. A macro can contain up to five comma-separated interface ranges. The commands are not batched and executed after you exit interface-range mode. you must use the define interface-range global configuration command to define the macro. For example. If you exit interface-range configuration mode while the commands are being executed. Each interface-range must consist of the same port type. • The interface range command only works with VLAN interfaces that have been configured with the interface vlan command.2 Switch(config-if-range)# speed 100 This example shows how to use a comma to add different interface type strings to the range to enable Fast Ethernet ports 1 to 3 on switch 1 and Gigabit Ethernet ports 1 and 2 on switch 2 to receive flow-control pause frames: Switch# configure terminal Switch(config)# interface range gigabitethernet1/0/1 . Define the interface-range macro.0(1)SE 12-20 OL-26520-02 . interface range gigabitethernet1/0/1-4 is not.4 is a valid range.

{last port}.Chapter 12 Configuring Interface Characteristics Using Interface Configuration Mode Command Step 3 Purpose Select the interface range to be configured using the values saved in the interface-range macro called macro_name.{last port}. – fastethernet stack member/module/{first port} . but you can combine multiple interface types in a macro. Release 15. note these guidelines: • Valid entries for interface-range.port-channel-number. the first and last port-channel number must be active port channels. these options are not supported on Catalyst 2960 switches. depending on port types on the switch: – vlan vlan-ID. all EtherChannel ports. interface range macro macro_name Step 4 Step 5 Step 6 end show running-config | include define copy running-config startup-config Return to privileged EXEC mode.2 Catalyst 2960 and 2960-S Switches Software Configuration Guide. All interfaces defined as in a range must be the same type (all Fast Ethernet ports. where the module is always 0 – gigabitethernet stack member/module/{first port} .{last port}. • You must add a space between the first interface number and the hyphen when entering an interface-rang.2 Switch(config)# end Switch# show running-config | include define Switch# define interface-range enet_list gigabitethernet1/0/1 . gigabitethernet1/0/1-4 is not. gigabitethernet1/0/1 . For example. The show running-config privileged EXEC command displays the configured VLAN interfaces. • This example shows how to define an interface-range named enet_list to include ports 1 and 2 and to verify the macro configuration: Switch# configure terminal Switch(config)# define interface-range enet_list gigabitethernet1/0/1 . Use the no define interface-range macro_name global configuration command to delete a macro. VLAN interfaces not displayed by the show running-config command cannot be used as interface-ranges.0(1)SE OL-26520-02 12-21 . where the module is always 0 – port-channel port-channel-number .4 is a valid range. or all VLANs). (Optional) Save your entries in the configuration file. where the module is always 0 – gigabitethernet module/{first port} . • The VLAN interfaces must have been configured with the interface vlan command. all Gigabit Ethernet ports. You can now use the normal configuration commands to apply the configuration to all interfaces in the defined macro. where the port-channel-number is 1 to 6 Note When you use the interface range command with port channels. Show the defined interface range macro configuration. When using the define interface-range global configuration command. where the VLAN ID is 1 to 4094 Note Although the command-line interface shows options to set multiple VLANs. where the module is always 0 – fastethernet module/{first port} .{last port}.

Chapter 12 Using the Ethernet Management Port (Catalyst 2960-S Only) Configuring Interface Characteristics This example shows how to create a multiple-interface macro named macro1: Switch# configure terminal Switch(config)# define interface-range macro1 gigabitethernet1/0/1 .2. page 12-24 Understanding the Ethernet Management Port The Ethernet management port. gigabitethernet1/0/1 . Switch# configure terminal Switch(config)# no define interface-range enet_list Switch(config)# end Switch# show run | include define Switch# Using the Ethernet Management Port (Catalyst 2960-S Only) Note The Ethernet management port is not supported on Catalyst 2960 switches. • • • • Understanding the Ethernet Management Port. When managing a switch stack. Catalyst 2960 and 2960-S Switches Software Configuration Guide. You can use the Ethernet management port instead of the switch console port for network management. you must assign an IP address.2 Switch(config)# end This example shows how to enter interface-range configuration mode for the interface-range macro enet_list: Switch# configure terminal Switch(config)# interface range macro enet_list Switch(config-if-range)# This example shows how to delete the interface-range macro enet_list and to verify that it was deleted. page 12-24 TFTP and the Ethernet Management Port. page 12-22 Supported Features on the Ethernet Management Port. connect the PC to the Ethernet management port on a Catalyst 2960-S stack member. is a Layer 3 host port to which you can connect a PC. also referred to as the Fa0 or fastethernet0 port. When connecting a PC to the Ethernet management port.0(1)SE 12-22 OL-26520-02 . Release 15. page 12-23 Configuring the Ethernet Management Port.

the Ethernet management port is enabled. connect the Ethernet management port to the PC as shown in Figure 12-2. the active link is now from the Ethernet management port on the new stack master to the PC.0(1)SE OL-26520-02 12-23 . Figure 12-3 Connecting a Switch Stack to a PC Switch stack Stack member 1 Stack member 2 Stack member 3 Stack member 4 Ethernet management ports 253665 157549 Network ports Hub PC By default. As shown in Figure 12-3. Release 15. Supported Features on the Ethernet Management Port The Ethernet management port supports these features: • • • • • • • • Express Setup (only in switch stacks) Network Assistant Telnet with passwords TFTP Secure Shell (SSH) DHCP-based autoconfiguration SMNP (only the ENTITY-MIB and the IF-MIB) IP ping Catalyst 2960 and 2960-S Switches Software Configuration Guide.Chapter 12 Configuring Interface Characteristics Using the Ethernet Management Port (Catalyst 2960-S Only) For a Catalyst 2960-S standalone switch. Figure 12-2 Connecting a Switch to a PC Switch Ethernet management port PC Network cloud In a Catalyst 2960-S stack. If the stack master fails and a new stack master is elected. the active link is from the Ethernet management port on the stack master (switch 2) through the hub. all the Ethernet management ports on the stack members are connected to a hub to which the PC is connected. to the PC.

To display the link status. use the no shutdown interface configuration command. and the switch might fail. To disable the port. Release 15. If you try to configure an unsupported feature on the Ethernet Management port. Starts the Ethernet management port. mgmt_clr mgmt_init mgmt_show ping host_ip_address Clears the statistics for the Ethernet management port. Sends ICMP ECHO_REQUEST packets to the specified network host. make sure that the feature is supported. Catalyst 2960 and 2960-S Switches Software Configuration Guide. use the shutdown interface configuration command. the feature might not work properly. you can monitor the LED for the Ethernet management port. TFTP and the Ethernet Management Port Use the commands in Table 12-3 when using TFTP to download or upload a configuration file to the boot loader. 100 Mb/s. The LED is amber when there is a POST failure. To find out the link status to the PC.0(1)SE 12-24 OL-26520-02 . enter fastethernet0. and the LED is off when the link is down. Displays the statistics for the Ethernet management port. The LED is green (on) when the link is active. and autonegotiation – Duplex mode—Full. Enables ARP to associate a MAC address with the specified IP address when this command is entered with the ip_address parameter. To enable the port. Table 12-3 Boot Loader Commands Command arp [ip_address] Description Displays the currently cached ARP1 table when this command is entered without the ip_address parameter.Chapter 12 Using the Ethernet Management Port (Catalyst 2960-S Only) Configuring Interface Characteristics • Interface features – Speed—10 Mb/s. and autonegotiation – Loopback detection • • • Cisco Discovery Protocol (CDP) DHCP relay agent IPv4 and IPv6 access control lists (ACLs) Caution Before enabling a feature on the Ethernet management port. Configuring the Ethernet Management Port To specify the Ethernet management port in the CLI. half. use the show interfaces fastethernet 0 privileged EXEC command.

All ports are enabled. ARP = Address Resolution Protocol. Description Loads and boots an executable image from the TFTP server and enters the command-line interface.0(1)SE OL-26520-02 12-25 . page 12-35 Configuring Catalyst PoE and PoE Pass-Through Ports on Compact Switches. page 12-28 Configuring IEEE 802. see the command reference for this release. page 12-26 Configuring Interface Speed and Duplex Mode. Drop all packets tagged with VLAN 0.. copy tftp:/source-file-url filesystem:/destination-fileurl 1. page 12-39 Default Ethernet Interface Configuration Table 12-4 shows the Ethernet interface default configuration. For more details on the VLAN parameters listed in the table. see Chapter 13.” Table 12-4 Default Layer 2 Ethernet Interface Configuration Feature Allowed VLAN range Default VLAN (for access ports) Native VLAN (for IEEE 802.” For details on controlling traffic to the port.. see Chapter 23.3x Flow Control.Chapter 12 Configuring Interface Characteristics Configuring Ethernet Interfaces Table 12-3 Boot Loader Commands (continued) Command boot tftp:/file-url . page 12-31 Configuring a Power Management Mode on a PoE Port. VLAN 1. page 12-37 Adding a Description for an Interface. None defined. Switchport mode dynamic auto (supports DTP). Release 15. VLAN 1. For more details. page 12-32 Budgeting Power for Devices Connected to a PoE Port. “Configuring VLANs. “Configuring Port-Based Traffic Control. Catalyst 2960 and 2960-S Switches Software Configuration Guide. page 12-25 Setting the Type of a Dual-Purpose Uplink Port.1p priority-tagged traffic VLAN trunking Port enable state Port description Default Setting VLANs 1 to 4094. page 12-33 Configuring Power Policing. Copies a Cisco IOS image from the TFTP server to the specified location. page 12-30 Configuring Auto-MDIX on an Interface.1Q trunks) 802. For more details. Configuring Ethernet Interfaces • • • • • • • • • • Default Ethernet Interface Configuration. see the command reference for this release.

By default.3af—if that powered device is connected to the switch through a crossover cable. multicast. This is regardless of whether auto-MIDX is enabled on the switch port. See the “Configuring Port Blocking” and unknown unicast traffic) section on page 23-7. Disabled on all Ethernet ports. See the “Default Port Security Configuration” section on page 23-11. Setting the Type of a Dual-Purpose Uplink Port Note Only Catalyst 2960 switches have dual-purpose uplinks ports. Disabled. It is always off for sent packets. Flow control is set to receive: off. Disabled. you can use the media-type interface configuration command to manually select the RJ-45 connector or the SFP module connector. Chapter 38. See the “Configuring Protected Ports” section on page 23-6. Enabled. Release 15. the switch dynamically selects the interface type that first links up.Chapter 12 Configuring Ethernet Interfaces Configuring Interface Characteristics Table 12-4 Default Layer 2 Ethernet Interface Configuration (continued) Feature Speed Duplex mode Flow control EtherChannel (PAgP) Default Setting Autonegotiate. Broadcast. enabled on all other ports. For more information. Some switches support dual-purpose uplink ports. see the “Dual-Purpose Uplink Ports” section on page 12-4. However. “Configuring EtherChannels and Link-State Tracking. and unicast storm control Protected port Port security Port Fast Auto-MDIX Disabled. Autonegotiate. See the “Default Storm Control Configuration” section on page 23-3. Disabled.” Port blocking (unknown multicast Disabled (not blocked). Power over Ethernet (PoE) Keepalive messages Enabled (auto). Note The switch might not support a pre-standard powered device—such as Cisco IP phones and access points that do not fully support IEEE 802. See the “Default Optional Spanning-Tree Configuration” section on page 18-12. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Disabled on SFP module ports.0(1)SE 12-26 OL-26520-02 .

use the media-type auto interface or the no media-type interface configuration commands. If you configure auto-select. and enter interface configuration mode. When the active link goes down. The keywords have these meanings: • configure terminal interface interface-id media-type {auto-select | rj45 | sfp} auto-select—The switch dynamically selects the type. you cannot configure the speed and duplex interface configuration commands. the switch configures both types with autonegotiation of speed and duplex (the default). • • For information about setting the speed and duplex. Command Step 1 Step 2 Step 3 Purpose Enter global configuration mode. the switch gives preference to the SFP module interface. sfp—The switch disables the RJ-45 interface. If you connect a cable to the RJ-45 port. Select the interface and type of a dual-purpose uplink port. Depending on the type of installed SFP module. If you connect an SFP module to this port. In this mode. the switch selects the active link based on which type first links up. see the information that follows this procedure. it cannot attain a link even if the SFP module side is down or if the SFP module is not present. see the “Speed and Duplex Configuration Guidelines” section on page 12-28. rj45—The switch disables the SFP module interface. To return to the default setting. it cannot attain a link even if the RJ-45 side is down or is not connected. the switch might not be able to dynamically select it. The switch operates with 100BASE-x (where -x is -BX. Based on the type of installed SFP module. In all other situations. -FX-FE. -LX) SFP modules as follows: Catalyst 2960 and 2960-S Switches Software Configuration Guide. Release 15. You can configure the speed and duplex settings consistent with this interface type. Specify the dual-purpose uplink port to be configured. In auto-select mode.0(1)SE OL-26520-02 12-27 .Chapter 12 Configuring Interface Characteristics Configuring Ethernet Interfaces Beginning in privileged EXEC mode. the dual-purpose port behaves like a 10/100/1000BASE-TX interface. When the switch powers on or when you enable a dual-purpose uplink port through the shutdown and the no shutdown interface configuration commands. (Optional) Save your entries in the configuration file. you can configure the speed and duplex settings consistent with this interface type. This procedure is optional. e switch configures both types to autonegotiate speed and duplex (the default). the switch disables the other type until the active link goes down. the switch enables both types until one of them links up. follow these steps to select which dual-purpose uplink to activate so that you can set the speed and duplex. For more information. Step 4 Step 5 Step 6 end show interfaces interface-id transceiver properties copy running-config startup-config Return to privileged EXEC mode. Verify your setting. When link up is achieved.

we highly recommend the default setting of auto negotiation. 100.duplex options but do not support autonegotiation. For information about which SFP modules are supported on your switch.and half. When the 100BASE-x SFP module is inserted and there is a link on the RJ-45 side. Ethernet interfaces on the switch operate at 10. see the product release notes.0(1)SE 12-28 OL-26520-02 . -SX. • • The switch does not have this behavior with 100BASE-FX-GE SFP modules. Gigabit Ethernet ports operating at 1000 Mb/s do not support half-duplex mode. When the 100BASE-x SFP module is removed. note these guidelines: • • Fast Ethernet (10/100-Mb/s) ports support all speed and duplex options. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Configuring Interface Speed and Duplex Mode Depending on the supported port types. – The 100BASE-x (where -x is -BX. two stations can send and receive traffic at the same time. If the link goes down. These sections describe how to configure the interface speed and duplex mode: • • Speed and Duplex Configuration Guidelines. half. page 12-29 Speed and Duplex Configuration Guidelines When configuring an interface speed and duplex mode. 10-Mb/s ports operate in half-duplex mode. and small form-factor pluggable (SFP) module slots supporting SFP modules. -CWDM. and -ZX) SFP module ports support • the nonegotiate keyword in the speed interface configuration command. or 1000 Mb/s. the switch disables the RJ-45 side and selects the SFP module interface. the switch disables the RJ-45 interface and selects the SFP module interface.000 Mb/s and in either full. 10-Gigabit module ports. – The 1000BASE-T SFP module ports support the same speed and duplex options as the 10/100/1000-Mb/s ports. Gigabit Ethernet (10/100/1000-Mb/s) ports support all speed options and all duplex options (auto. the speed and duplex CLI options change depending on the SFP module type: – The 1000BASE-x (where -x is -BX. and -ZX) SFP module ports support only 100 Mb/s. In full-duplex mode. However. For SFP module ports. the switch continues with that link. Duplex options are not supported. -SX. Gigabit Ethernet (10/100/1000-Mb/s) ports.Chapter 12 Configuring Ethernet Interfaces Configuring Interface Characteristics • When the 100BASE -x SFP module is inserted into the module slot and there is no link on the RJ-45 side. and full). This is the behavior even if there is no cable connected and if there is no link on the SFP module side. -LX. -LX. the switch again dynamically selects the type (auto-select) and re-enables the RJ-45 side. • If both ends of the line support autonegotiation. or 10. Release 15. Switch models can include combinations of Fast Ethernet (10/100-Mb/s) ports. page 12-28 Setting the Interface Speed and Duplex Parameters. These modules support full. which means that stations can either receive or send traffic. Normally.or half-duplex mode. -CWDM.

100. do not use the auto setting on the supported side. Use the no speed and no duplex interface configuration commands to return the interface to the default speed and duplex settings (autonegotiate). The port LED is amber while STP reconfigures. • For more information about speed settings. Step 4 duplex {auto | full | half} Enter the duplex parameter for the interface. configure duplex and speed on both interfaces. Caution Changing the interface speed and duplex mode configuration might shut down and re-enable the interface during the reconfiguration. the switch can take up to 30 seconds to check for loops. If you use the 10. or 1000 to set a specific speed for the interface. and enter interface configuration mode. Specify the physical interface to be configured. Release 15. For more information about duplex settings. see the “Speed and Duplex Configuration Guidelines” section on page 12-28. Catalyst 2960 and 2960-S Switches Software Configuration Guide. or the 1000 keywords with the auto keyword.0(1)SE OL-26520-02 12-29 . the port autonegotiates only at the specified speeds. Step 5 Step 6 Step 7 end show interfaces interface-id copy running-config startup-config Return to privileged EXEC mode. Setting the Interface Speed and Duplex Parameters Beginning in privileged EXEC mode.Chapter 12 Configuring Interface Characteristics Configuring Ethernet Interfaces • • If one interface supports autonegotiation and the other end does not. The 1000 keyword is available only for 10/100/1000 Mb/s ports. Enter the appropriate speed parameter for the interface: • • configure terminal interface interface-id speed {10 | 100 | 1000 | auto [10 | 100 | 1000] | nonegotiate} Enter 10. You cannot configure half-duplex mode for interfaces operating at 1000 Mb/s. use the default interface interface-id interface configuration command. Enter auto to enable the interface to autonegotiate speed with the connected device. follow these steps to set the speed and duplex mode for a physical interface: Command Step 1 Step 2 Step 3 Purpose Enter global configuration mode. Enable half-duplex mode (for interfaces operating only at 10 or 100 Mb/s). The nonegotiate keyword is available only for SFP module ports. When STP is enabled and a port is reconfigured. 100. SFP module ports operate only at 1000 Mb/s but can be configured to not negotiate if connected to a device that does not support autonegotiation. see the “Speed and Duplex Configuration Guidelines” section on page 12-28. (Optional) Save your entries in the configuration file. To return all interface settings to the defaults. Display the interface speed and duplex mode configuration.

3x Flow Control Flow control enables connected Ethernet ports to control traffic rates during congestion by allowing congested nodes to pause link operation at the other end. the port can receive pause frames. The default state is off. no indication is given to the link partner. Beginning in privileged EXEC mode. If one port experiences congestion and cannot receive any more traffic. These rules apply to flow control settings on the device: • • receive on (or desired): The port cannot send pause frames but can operate with an attached device that is required to or can send pause frames. Configure the flow control mode for the port. Release 15. or desired. (Optional) Save your entries in the configuration file. You use the flowcontrol interface configuration command to set the interface’s ability to receive pause frames to on. follow these steps to configure flow control on an interface: Command Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Purpose Enter global configuration mode. which prevents any loss of data packets during the congestion period. Verify the interface flow control settings. configure terminal interface interface-id flowcontrol {receive} {on | off | desired} end show interfaces interface-id copy running-config startup-config Catalyst 2960 and 2960-S Switches Software Configuration Guide.0(1)SE 12-30 OL-26520-02 . pause frames. off. an interface can operate with an attached device that is required to send flow-control packets or with an attached device that is not required to but can send flow-control packets. and enter interface configuration mode. When set to desired. the sending device stops sending any data packets. Upon receipt of a pause frame. see the flowcontrol interface configuration command in the command reference for this release. Note For details on the command settings and the resulting flow control resolution on local and remote ports. but not send. receive off: Flow control does not operate in either direction. and no pause frames are sent or received by either device.Chapter 12 Configuring Ethernet Interfaces Configuring Interface Characteristics This example shows how to set the interface speed to 10 Mb/s and the duplex mode to half on a 10/100 Mb/s port: Switch# configure terminal Switch(config)# interface fasttethernet1/0/3 Switch(config-if)# speed 10 Switch(config-if)# duplex half This example shows how to set the interface speed to 100 Mb/s on a 10/100/1000 Mb/s port: Switch# configure terminal Switch(config)# interface gigabitethernet1/0/2 Switch(config-if)# speed 100 Configuring IEEE 802. it notifies the other port by sending a pause frame to stop sending until the condition clears. In case of congestion. Note Ports on the switch can receive. Specify the physical interface to be configured. Return to privileged EXEC mode.

Chapter 12 Configuring Interface Characteristics Configuring Ethernet Interfaces To disable flow control. This example shows how to turn on flow control on a port: Switch# configure terminal Switch(config)# interface gigabitethernet1/0/1 Switch(config-if)# flowcontrol receive on Switch(config-if)# end Configuring Auto-MDIX on an Interface When automatic medium-dependent interface crossover (auto-MDIX) is enabled on an interface. Release 15. the interface automatically detects the required cable connection type (straight through or crossover) and configures the connection appropriately. For more information about cabling requirements. Configure the interface to autonegotiate duplex mode with the connected device. you must use straight-through cables to connect to devices such as servers. configure terminal interface interface-id speed auto duplex auto mdix auto end show controllers ethernet-controller Verify the operational state of the auto-MDIX feature on the interface. Configure the interface to autonegotiate speed with the connected device.0(1)SE OL-26520-02 12-31 . you can use either type of cable to connect to other devices. and enter interface configuration mode. Auto-MDIX is enabled by default. Auto-MDIX is supported on all 10/100 and 10/100/1000-Mb/s interfaces. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Table 12-5 shows the link states that result from auto-MDIX settings and correct and incorrect cabling. you must also set the interface speed and duplex to auto so that the feature operates correctly. Enable auto-MDIX on the interface. or routers and crossover cables to connect to other switches or repeaters. follow these steps to configure auto-MDIX on an interface: Command Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Purpose Enter global configuration mode. workstations. With auto-MDIX enabled. interface-id phy copy running-config startup-config (Optional) Save your entries in the configuration file. Specify the physical interface to be configured. use the flowcontrol receive off interface configuration command. see the hardware installation guide. When connecting switches without the auto-MDIX feature. Table 12-5 Link Conditions and Auto-MDIX Settings Local Side Auto-MDIX On On Off Off Remote Side Auto-MDIX With Correct Cabling On Off On Off Link up Link up Link up Link up With Incorrect Cabling Link up Link up Link up Link down Beginning in privileged EXEC mode. It is not supported on 1000BASE-SX or -LX SFP module interfaces. Return to privileged EXEC mode. When you enable auto-MDIX. and the interface automatically corrects for any incorrect cabling.

the state of the other PoE ports. The switch repowers the port only if the powered device is a Class 1. For most situations. For example. or to specify a maximum wattage to disallow high-power powered devices on a port. the port might not be powered up again. This example shows how to enable auto-MDIX on a port: Switch# configure terminal Switch(config)# interface gigabitethernet1/0/1 Switch(config-if)# speed auto Switch(config-if)# duplex auto Switch(config-if)# mdix auto Switch(config-if)# end Configuring a Power Management Mode on a PoE Port Note PoE commands are supported only when the switch is running the LAN base image. and you configure it for static mode. detects the powered device. Release 15. Class 2. Depending on the new configuration. If port 1 is in the auto and on state and you configure it with a maximum wattage of 10 W. or a Cisco-only powered device. configure terminal interface interface-id Catalyst 2960 and 2960-S Switches Software Configuration Guide. Power over Ethernet Plus (PoE+) is supported only on Catalyst 2960-S switches. use the no mdix auto interface configuration command.Chapter 12 Configuring Ethernet Interfaces Configuring Interface Characteristics To disable auto-MDIX. port 1 is in the auto and on state.0(1)SE 12-32 OL-26520-02 . No further configuration is required. Note When you make PoE configuration changes. and the state of the power budget. The switch removes power from port 1. providing plug-and-play operation. follow these steps to configure a power management mode on a PoE-capable port: Command Step 1 Step 2 Purpose Enter global configuration mode. the default configuration (auto mode) works well. Beginning in privileged EXEC mode. the port being configured drops power. the switch removes power from the port and then redetects the powered device. and repowers the port. and enter interface configuration mode. to make it data only. use the following procedure to give a PoE port higher priority. However. Specify the physical port to be configured.

(Optional) Save your entries in the configuration file.” Budgeting Power for Devices Connected to a PoE Port When Cisco powered devices are connected to PoE ports.400 milliwatts for the device. If enough power is available. By using the power inline consumption wattage configuration command. A false link-up can occur. you can override the default power requirement specified by the IEEE classification. For more information about PoE-related commands. The range is 4000 to 15400 milliwatts on a PoE port and 4000 to 30000 milliwatts on a PoE+ port. placing the port into an error-disabled state. Step 4 Step 5 end show power inline [interface-id | module switch-number] Return to privileged EXEC mode. • • Note • The switch allocates power to a port configured in static mode before it allocates power to a port configured in auto mode. Step 6 copy running-config startup-config For information about the output of the show power inline user EXEC command. do not use the power inline never command to configure the port. and disable power to the port. the switch uses Cisco Discovery Protocol (CDP) to determine the actual power consumption of the devices. The module keyword is applicable only on Catalyst 2960-S switches running the LAN base image. and the switch adjusts the power budget accordingly. never—Disable device detection. for the specified interface.0(1)SE OL-26520-02 12-33 . For information about configuring voice VLAN. see the command reference for this release. “Configuring Voice VLAN. Release 15. static—Enable powered-device detection.Chapter 12 Configuring Interface Characteristics Configuring Ethernet Interfaces Command Step 3 Purpose Configure the PoE mode on the port. the switch adjusts the power budget according to the powered-device IEEE classification. Catalyst 2960 and 2960-S Switches Software Configuration Guide. regardless of the actual amount of power needed. The CDP protocol works with Cisco powered devices and does not apply to IEEE third-party powered devices. the switch can power fewer devices because it uses the IEEE class information to track the global power budget. This is the default setting. the maximum is allowed. The difference between what is mandated by the IEEE classification and what is actually needed by the device is reclaimed into the global power budget for use by additional devices. automatically allocate power to the PoE port after device detection. or for a specified stack member. The switch reserves power for this port even when no device is connected and guarantees that power will be provided upon device detection. the switch budgets 15. If the powered device is a Class 0 (class status unknown) or a Class 3. You can then extend the switch power budget and use it more effectively. when the switch grants a power request. The keywords have these meanings: • power inline {auto [max max-wattage] | never | static [max max-wattage]} auto—Enable powered-device detection. Display PoE status for a switch or switch stack. Pre-allocate (reserve) power for a port before the switch discovers the powered device. If the powered device reports a higher class than its actual consumption or does not support power classification (defaults to Class 0). For these devices. If no value is specified. (Optional) max max-wattage—Limit the power allowed on the port. see Chapter 15. see the “Troubleshooting Power over Ethernet Switch Ports” section on page 39-13. If a port has a Cisco powered device connected to it.

Catalyst 2960 and 2960-S Switches Software Configuration Guide. Note When you manually configure the power budget.0(1)SE 12-34 OL-26520-02 .Chapter 12 Configuring Ethernet Interfaces Configuring Interface Characteristics For example. Step 4 Step 5 Step 6 end show power inline consumption copy running-config startup-config Return to privileged EXEC mode.000 milliwatts. The total PoE output power available on a 24-port or 48-port switch is 370. the switch continues to operate but its reliability is reduced. Release 15. use the no power inline consumption default global configuration command. follow these steps to configure the amount of power budgeted to a powered device connected to each PoE port on a switch: Command Step 1 Step 2 Step 3 Purpose Enter global configuration mode. Display the power consumption status. Note configure terminal no cdp run power inline consumption default wattage When you use this command. or the power inline consumption wattage or the no power inline consumption interface configuration command this caution message appears: %CAUTION: Interface interface-id: Misconfiguring the 'power inline consumption/allocation' command may cause damage to the switch and void your warranty. we recommend you also enable power policing. If your Class 0 device power requirement is actually 5000 milliwatts. The range for each de vice is 4000 to 15400 milliwatts on a PoE switch and 4000 to 30000 milliwatts on a PoE+ switch. Refer to documentation.400 milliwatts on each PoE port. If the power supply is over-subscribed to by up to 20 percent. Caution You should carefully plan your switch power budget and make certain not to oversubscribe the power supply. If the power supply is subscribed to by more than 20 percent. the short-circuit protection circuitry triggers and shuts the switch down. For more information about the IEEE power classifications. Take precaution not to oversubscribe the power supply. (Optional) Save your entries in the configuration file. you can set the consumption wattage to 5000 milliwatts and connect up to 48 devices. The default is 15400 milliwatts on a PoE switch and 30000 milliwatts on a PoE+ switch. (Optional) Disable CDP. Configure the power consumption of powered devices connected to each the PoE port on the switch. To return to the default setting. Beginning in privileged EXEC mode. if the switch budgets 15. It is recommended to enable power policing if the switch supports it. see the “Power over Ethernet Ports” section on page 12-5. you must also consider the power loss over the cable between the switch and the powered device. you can connect only 24 Class 0 powered devices. When you enter the power inline consumption default wattage or the no power inline consumption default global configuration command.

Specify the physical port to be configured. For more information about the cutoff power value. Configuring Power Policing By default.Chapter 12 Configuring Interface Characteristics Configuring Ethernet Interfaces Beginning in privileged EXEC mode. The range for each de vice is 4000 to 15400 milliwatts on a PoE port and 4000 to 30000 milliwatts on a PoE+ port. see the “Power Monitoring and Power Policing” section. Display the power consumption status. Beginning in privileged EXEC mode. Release 15.0(1)SE OL-26520-02 12-35 . Note configure terminal no cdp run interface interface-id power inline consumption wattage When you use this command. and enter interface configuration mode. use the no power inline consumption interface configuration command. and the actual power consumption value of the connected device. For information about the output of the show power inline consumption privileged EXEC command. You can configure the switch to police the power usage. see the command reference for this release. configure terminal interface interface-id Catalyst 2960 and 2960-S Switches Software Configuration Guide. Step 5 Step 6 Step 7 end show power inline consumption copy running-config startup-config Return to privileged EXEC mode. we recommend you also enable power policing. the power consumption values that the switch uses. Specify the physical port to be configured. policing is disabled. follow these steps to configure amount of power budgeted to a powered device connected to a specific PoE port: Command Step 1 Step 2 Step 3 Step 4 Purpose Enter global configuration mode. The default is 15400 milliwatts on a PoE port and 30000 milliwatts on a PoE+ port. and enter interface configuration mode. (Optional) Disable CDP. To return to the default setting. the switch monitors the real-time power consumption of connected powered devices. (Optional) Save your entries in the configuration file. By default. Configure the power consumption of a powered device connected to a PoE port on the switch. follow these steps to enable policing of the real-time power consumption of a powered device connected to a PoE port: Command Step 1 Step 2 Purpose Enter global configuration mode.

Step 6 Step 7 exit show power inline police show errdisable recovery copy running-config startup-config Step 8 To disable policing of the real-time power consumption. To disable error recovery for PoE error-disabled cause. For interval interval. and configure the PoE recover mechanism variables. use the no power inline police interface configuration command. and verify the error recovery settings. (Optional) Enable error recovery from the PoE error-disabled state. Display the power monitoring status. see the command reference for this release.Chapter 12 Configuring Ethernet Interfaces Configuring Interface Characteristics Command Step 3 Purpose power inline police [action {errdisable If the real-time power consumption exceeds the maximum power | log}] allocation on the port. For information about the output from the show power inline police privileged EXEC command. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Generate a syslog message while still providing power to the port—Enter the power inline police action log command. • If you do not enter the action keywords. and put it in the error-dsabled state—Enter the power inline police command. Release 15. use the no errdisable recovery cause inline-power global configuration command. turn off power to it. (Optional) Save your entries in the configuration file. You can also enable the timer to recover from the PoE error-disabled state by using the errdisable recovery cause inline-power interval interval global configuration command. the default action shuts down the port and puts the port in the error-disabled state. specify the time in seconds to recover from the error-disabled state. the recovery interval is 300 seconds. You can enable error detection for the PoE error-disabled cause by using the errdisable detect cause inline-power global configuration command. Return to privileged EXEC mode. configure the switch to take one of these actions: • Note Shut down the PoE port. The range is 30 to 86400. By default. Step 4 Step 5 exit errdisable detect cause inline-power and errdisable recovery cause inline-power and errdisable recovery interval interval Return to global configuration mode.0(1)SE 12-36 OL-26520-02 .

Back-up* : In the absence of 'Available' power mode.4(w) Interface Admin Oper Remaining:7. The show env power inline privileged EXEC command provides information about powering options and power backup on your switch: Switch# show env power PoE Power . the PoE received on this link is used for powering this switch and providing PoE pass-through if applicable. Input Gi0/2 Type -------------Auxilliary Type1 Backup:0.4 15. capable of providing pass-through power: Switch# show power inline Available:22. budgeting. the PoE received on this link is used for powering this switch but does not contribute to the PoE pass-through.0 Fa0/8 auto off 0.4 15.4 15. You can see the available power and the power required by each connected device by entering the show power inline privileged EXEC command.0(w) Power(w) --------51(w) 15.0 Fa0/3 auto off 0.0 Fa0/2 auto off 0. This is an example of output from a Catalyst 2960CPD-8PT.4(w) Power Source -------------A.0(w) Device ------------------n/a n/a n/a n/a IP Phone 8961 n/a n/a n/a Class Max ----n/a n/a n/a n/a 4 n/a n/a n/a ---15.C. Available*: The PoE received on this link is used for powering this switch but does not contribute to the PoE pass-through.------Fa0/1 auto off 0.0(1)SE OL-26520-02 12-37 .0 Fa0/5 auto on 15.4 15.4 Fa0/6 auto off 0.0 Fa0/4 auto off 0.---------. Release 15. and policing on the Catalyst 2960-C compact switch PoE ports the same as with any other PoE switch.4 15.Chapter 12 Configuring Interface Characteristics Configuring Ethernet Interfaces Configuring Catalyst PoE and PoE Pass-Through Ports on Compact Switches You can configure the power management.4 Power (Watts) --------.4 15.Available:22.0 Fa0/7 auto off 0.4 15.4(w) Mode --------Available Back-up Available : The PoE received on this link is used for powering this switch and providing PoE pass-through if applicable.4(w) Used:15. Back-up : In the absence of 'Available' power mode.-----.0 Catalyst 2960 and 2960-S Switches Software Configuration Guide.

0(1)SE 12-38 OL-26520-02 .----.4(w) Used:15.-------Fa0/1 off High Fa0/2 off High Fa0/3 off High Fa0/4 off High Fa0/5 off High Fa0/6 off High Fa0/7 off High Fa0/8 off High Catalyst 2960 and 2960-S Switches Software Configuration Guide.-----Totals: Oper State ---------off off off off on off off off ---------Admin Police ---------none none none none none none none none ---------Oper Police ---------n/a n/a n/a n/a n/a n/a n/a n/a ---------Cutoff Power -----n/a n/a n/a n/a n/a n/a n/a n/a -----Oper Power ----0. This is an example of output from the show power inline command on a C2960CPD-8TT switch: Switch# show power inline Available:0.4(w) Remaining:7.-----.0 0.5 0.0 0.0(w) Power Device Class Max (Watts) --------.0 0.0(w) Interface Admin Oper Remaining:0. This is an example of output from a Catalyst 2960CPD-8PT: Switch# show power inline police Available:22.-----Fa0/1 auto Fa0/2 auto Fa0/3 auto Fa0/4 auto Fa0/5 auto Fa0/6 auto Fa0/7 auto Fa0/8 auto --------.0 9.---- The show power inline dynamic-priority command shows the power priority of each port: Switch# show power inline dynamic-priority Dynamic Port Priority ----------------------Port OperState Priority --------.5 The Catalyst 2960CPD-8TT and Catalyst 2960CG-8TC downlink ports cannot provide power to end devices.Chapter 12 Configuring Ethernet Interfaces Configuring Interface Characteristics Enter the show power inline police privileged EXEC command to see power monitoring status.0 0.0 ----9.--------.0(w) Used:0. Release 15.0(w) Interface Admin State --------.------------------.---------.------.0 0.

This example shows how to add a description on a port and how to verify the description: Switch# config terminal Enter configuration commands. Release 15.Chapter 12 Configuring Interface Characteristics Configuring Layer 3 SVIs Adding a Description for an Interface You can add a description about an interface to help you remember its function. Beginning in privileged EXEC mode. SVIs are created when you enter a VLAN ID following the interface vlan global configuration command. and enter interface configuration mode. “Configuring VLANs. show running-config. Add a description (up to 240 characters) for an interface. For information about assigning Layer 2 ports to VLANs. To delete an SVI. All Layer 3 interfaces require an IP address to route traffic. see Chapter 13. it does not become active until you associate it with a physical port. follow these steps to add a description for an interface: Command Step 1 Step 2 Step 3 Step 4 Step 5 Purpose Enter global configuration mode. Return to privileged EXEC mode. Note When you create an SVI. This procedure shows how to configure an interface as a Layer 3 interface and how to assign an IP address to an interface. You should configure SVIs for any VLANs for which you want to route traffic.Protocol Description Gi1/0/2 admin down down Connects to Marketing Configuring Layer 3 SVIs Note Only switches running the LAN base image support Layer 3 SVIs for static routing. Use the no description interface configuration command to delete the description. one per line. Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file. Catalyst 2960 and 2960-S Switches Software Configuration Guide. and show interfaces. You cannot delete VLAN 1.0(1)SE OL-26520-02 12-39 . but the switch supports static routing on 16 SVIs.” A Layer 3 switch can have an IP address assigned to each SVI. configure terminal interface interface-id description string end or show running-config show interfaces interface-id description Verify your entry. Specify the interface for which you are adding a description. The description appears in the output of these privileged EXEC commands: show configuration. Switch(config)# interface gigabitethernet1/0/2 Switch(config-if)# description Connects to Marketing Switch(config-if)# end Switch# show interfaces gigabitethernet1/0/2 description Interface Status . use the no interface vlan global configuration command. End with CNTL/Z.

255. Release 15. This example shows how to configure a Layer 3 SVI and to assign it an IP address: Switch# configure terminal Enter configuration commands. one per line. SNMP. or Telnet. Specify the VLAN to be configured as a Layer 3 SVI. 10/100 ports are not affected by the system mtu jumbo command. Verify the configuration. you must reset the switch before the new configuration takes effect. To remove an IP address from an SVI. Switch(config)# interface vlan 33 Switch(config-if)# ip address 192. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Frames sizes that can be received by the switch CPU are limited to 1998 bytes. Configure the IP address and IP subnet. no matter what value was entered with the system mtu or system mtu jumbo commands.0 Configuring the System MTU The default maximum transmission unit (MTU) size for frames received and transmitted on all interfaces is 1500 bytes. the setting of the system mtu command applies to all Gigabit Ethernet interfaces. When you change the system or jumbo MTU size. You can increase the MTU size for all interfaces operating at 10 or 100 Mb/s by using the system mtu global configuration command. and enter interface configuration mode. You cannot set the MTU size for an individual interface. Gigabit Ethernet ports are not affected by the system mtu command.255.20.Chapter 12 Configuring the System MTU Configuring Interface Characteristics Beginning in privileged EXEC mode. If you do not configure the system mtu jumbo command.0(1)SE 12-40 OL-26520-02 . such as traffic sent to control traffic. use the no ip address interface configuration command. Return to privileged EXEC mode. follow these steps to configure a Layer 3 SVI: Command Step 1 Step 2 Step 3 Step 4 Step 5 Purpose Enter global configuration mode. configure terminal interface vlan vlan-id ip address ip_address subnet_mask end show interfaces [interface-id] show ip interface [interface-id] show running-config interface [interface-id] Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.135. packets are sent to the CPU. you set it for all 10/100 or all Gigabit Ethernet interfaces. Although frames that are forwarded are typically not received by the CPU. You can increase the MTU size to support jumbo frames on all Gigabit Ethernet interfaces by using the system mtu jumbo global configuration command. in some cases. End with CNTL/Z.21 255.

you can verify your settings by entering the show system mtu privileged EXEC command. follow these steps to change MTU size for all 10/100 or Gigabit Ethernet interfaces: Command Step 1 Step 2 Purpose Enter global configuration mode. the default is 1500 bytes. If you enter a value that is outside the allowed range for the specific type of interface. Beginning in privileged EXEC mode.Chapter 12 Configuring Interface Characteristics Configuring the System MTU Note If Layer 2 Gigabit Ethernet interfaces are configured to accept frames greater than the 10/100 interfaces. Reload the operating system. This example shows how to set the maximum packet size for a Gigabit Ethernet port to 1800 bytes: Switch(config)# system mtu jumbo 1800 Switch(config)# exit Switch# reload This example shows the response when you try to set Gigabit Ethernet interfaces to an out-of-range number: Switch(config)# system mtu jumbo 25000 ^ % Invalid input detected at '^' marker. The range is 1500 to 1998 bytes. the value is not accepted. (Optional) Change the MTU size for all Gigabit Ethernet interfaces on the switch stack. configure terminal system mtu bytes Step 3 system mtu jumbo bytes (Optional) Change the MTU size for all Gigabit Ethernet interfaces on the switch. Once the switch reloads. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Step 4 Step 5 Step 6 end copy running-config startup-config reload Return to privileged EXEC mode. jumbo frames received on a Layer 2 Gigabit Ethernet interface and sent on a Layer 2 10/100 interface are dropped. The range is 1500 to 9000 bytes. Release 15. Save your entries in the configuration file. the default is 1500 bytes. (Optional) Change the MTU size for all interfaces on the switch stack that are operating at 10 or 100 Mb/s.0(1)SE OL-26520-02 12-41 .

the names and sources of configuration files. (You can display the full list of show commands by using the show ? command at the privileged EXEC prompt. Release 15. page 12-43 Shutting Down and Restarting the Interface. Display PoE status for a switch or for an interface. and the boot images.Chapter 12 Monitoring and Maintaining the Interfaces Configuring Interface Characteristics Monitoring and Maintaining the Interfaces These sections contain interface monitoring and maintenance information: • • • Monitoring Interface Status. software version. Display the running configuration in RAM for the interface. Catalyst 2960 and 2960-S Switches Software Configuration Guide.com. including the versions of the software and the hardware. Table 12-6 lists some of these interface monitoring commands. page 12-42 Clearing and Resetting Interfaces and Counters. (Optional) Display speed and duplex settings on the interface. Release 12. Display the power policing data.0(1)SE 12-42 OL-26520-02 .4 from Cisco. (Optional) Display the input and output packets by the switching path for the interface. (Optional) Display the usability status of all interfaces configured for IP routing or the specified interface.) These commands are fully described in the Cisco IOS Interface Command Reference. (Optional) Display interface status or a list of interfaces in an error-disabled state. Display the hardware configuration. page 12-43 Monitoring Interface Status Commands entered at the privileged EXEC prompt display information about the interface. Display the operational state of the auto-MDIX feature on the interface. (Optional) Display administrative and operational status of switching ports. Table 12-6 Show Commands for Interfaces Command show interfaces [interface-id] show interfaces interface-id status [err-disabled] show interfaces [interface-id] switchport show interfaces [interface-id] description show ip interface [interface-id] show interface [interface-id] stats show interfaces transceiver properties show interfaces [interface-id] [{transceiver properties | detail}] module number] show running-config interface [interface-id] show version show controllers ethernet-controller interface-id phy show power inline [interface-id] show power inline police Purpose (Optional) Display the status and configuration of all interfaces or a specific interface. the configuration. (Optional) Display the description configured on an interface or all interfaces and the interface status. and statistics about the interfaces. Display physical and operational status about an SFP module.

Table 12-7 Clear Commands for Interfaces Command clear counters [interface-id] clear interface interface-id clear line [number | console 0 | vty number] Purpose Clear interface counters. Beginning in privileged EXEC mode. follow these steps to shut down an interface: Command Step 1 Step 2 Step 3 Step 4 Step 5 Purpose Enter global configuration mode.0(1)SE OL-26520-02 12-43 . Shutting Down and Restarting the Interface Shutting down an interface disables all functions on the specified interface and marks the interface as unavailable on all monitoring command displays. Catalyst 2960 and 2960-S Switches Software Configuration Guide. configure terminal interface {vlan vlan-id} | {{fastethernet | gigabitethernet} Select the interface to be configured. but only those seen with the show interface privileged EXEC command. Return to privileged EXEC mode. Reset the hardware logic on an asynchronous serial line. This information is communicated to other network servers through all dynamic routing protocols. Verify your entry. use the clear counters privileged EXEC command. interface-id} | {port-channel port-channel-number} shutdown end show running-config Shut down an interface. The interface is not mentioned in any routing updates. To clear the interface counters shown by the show interfaces privileged EXEC command.Chapter 12 Configuring Interface Characteristics Monitoring and Maintaining the Interfaces Clearing and Resetting Interfaces and Counters Table 12-7 lists the privileged EXEC mode clear commands that you can use to clear counters and reset interfaces. Reset the hardware logic on an interface. The clear counters command clears all current interface counters from the interface unless you specify optional arguments that clear only a specific interface type from a specific interface number. Note The clear counters privileged EXEC command does not clear counters retrieved by using Simple Network Management Protocol (SNMP). Release 15.

Release 15.0(1)SE 12-44 OL-26520-02 .Chapter 12 Monitoring and Maintaining the Interfaces Configuring Interface Characteristics Catalyst 2960 and 2960-S Switches Software Configuration Guide.

The chapter consists of these sections: • • • • • • Understanding VLANs.0(1)SE OL-26520-02 13-1 . VLAN configuration modes. It includes information about VLAN membership modes. broadcast. Note For complete syntax and usage information for the commands used in this chapter. page 13-5 Configuring Extended-Range VLANs. or 2960-C switch. and dynamic VLAN assignment from a VLAN Membership Policy Server (VMPS). VLANs can be formed with ports across the stack.CH A P T E R 13 Configuring VLANs This chapter describes how to configure normal-range VLANs (VLAN IDs 1 to 1005) and extended-range VLANs (VLAN IDs 1006 to 4094) on the Catalyst C2960. See Chapter 16. as shown in Figure 13-1. page 13-13 Configuring VLAN Trunks. Because a VLAN is considered a separate logical network. but you can group end stations even if they are not physically located on the same LAN segment. see the command reference for this release. without regard to the physical locations of the users. VLAN trunks. 2960-S. Any switch port can belong to a VLAN. project team. “Configuring STP. and unicast. it contains its own bridge Management Information Base (MIB) information and can support its own implementation of spanning tree. page 13-24 Understanding VLANs A VLAN is a switched network that is logically segmented by function. page 13-11 Displaying VLANs. and packets destined for stations that do not belong to the VLAN must be forwarded through a router or a switch supporting fallback bridging. VLANs have the same attributes as physical LANs. Note Stacking is supported only on Catalyst 2960-S switches running the LAN base image.” Catalyst 2960 and 2960-S Switches Software Configuration Guide. Each VLAN is considered a logical network. Unless otherwise noted. the term switch refers to a standalone switch and a switch stack. and multicast packets are forwarded and flooded only to end stations in the VLAN. page 13-1 Configuring Normal-Range VLANs. Release 15. page 13-14 Configuring VMPS. or application.

“Configuring VTP. When you assign switch interfaces to VLANs by using this method. it is known as interface-based. Release 15. you must decide whether to use VLAN Trunking Protocol (VTP) to maintain global VLAN configuration for your network. Catalyst 2960 and 2960-S Switches Software Configuration Guide. For example. all the end stations in a particular IP subnet belong to the same VLAN. Figure 13-1 VLANs as Logically Defined Networks Engineering VLAN Cisco router Marketing VLAN Accounting VLAN Floor 3 Gigabit Ethernet Floor 2 Floor 1 90571 VLANs are often associated with IP subnetworks.0(1)SE 13-2 OL-26520-02 . VLAN membership. or static.Chapter 13 Understanding VLANs Configuring VLANs Note Before you create VLANs. For more information on VTP. Interface VLAN membership on the switch is assigned manually on an interface-by-interface basis. Traffic between VLANs must be routed or fallback bridged. see Chapter 14.” Figure 13-1 shows an example of VLANs segmented into logically defined networks.

VLANs are identified by a number from 1 to 4094. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Note Up to 64 VLANs are supported when the switch is running the LAN Lite image. The switch supports only IEEE 802. See the “Normal-Range VLAN Configuration Guidelines” section on page 13-6 for more information about the number of spanning-tree instances and the number of VLANs. server. VLAN IDs 1002 through 1005 are reserved for Token Ring and FDDI VLANs.1Q trunking methods for sending VLAN traffic over Ethernet ports. and transparent modes. the switch must be in VTP transparent mode when you create VLAN IDs from 1006 to 4094. You cannot convert from VTP version 3 to VTP version 2 if extended VLANs are configured in the domain.Chapter 13 Configuring VLANs Understanding VLANs Supported VLANs The switch supports VLANs in VTP client. In these versions.2(52)SE and later support VTP version 3. VTP version 3 supports the entire VLAN range (VLANs 1 to 4094). Extended range VLANs (VLANs 1006 to 4094) are supported only in VTP version 3. Note Up to 64 spanning-tree instances are supported when the switch is running the LAN Lite image. The switch supports per-VLAN spanning-tree plus (PVST+) or rapid PVST+ with a maximum of 128 spanning-tree instances. Cisco IOS Release 12.0(1)SE OL-26520-02 13-3 . the number of configured features affects the use of the switch hardware. One spanning-tree instance is allowed per VLAN. Release 15. VTP version 1 and version 2 support only normal-range VLANs (VLAN IDs 1 to 1005). Although the switch stack supports a total of 255 (normal range and extended range) VLANs.

0(1)SE 13-4 OL-26520-02 . 2960-S. and renaming of VLANs on a network-wide basis. configured to use one VLAN for voice traffic and another VLAN for data traffic from a device attached to the phone. VTP is recommended but not required. but never a Catalyst 2960. see the “Configuring Dynamic-Access Ports on VMPS Clients” section on page 13-27. Table 13-1 lists the membership modes and membership and VTP characteristics. VTP exchanges VLAN configuration messages with other switches over trunk links. Table 13-1 Port Membership Modes and Characteristics Membership Mode Static-access VLAN Membership Characteristics A static-access port can belong to one VLAN and is manually assigned to that VLAN. it has no effect on a A voice VLAN port is an access port attached to a voice VLAN. 2960-S. at least one trunk port on the switch stack must be connected to a trunk port of a second switch or switch stack. You can have dynamic-access ports and trunk ports on the same switch. but membership can be limited by configuring the allowed-VLAN list. or 2960-C switch is a VMPS client. To participate in VTP. Release 15. Stacking is supported only on Catalyst 2960-S switches running the LAN base image. but you must connect the dynamic-access port to an end station or hub and not to another switch. You can also modify the pruning-eligible list to block flooded traffic to VLANs on trunk ports that are included in the list. deletion.” Catalyst 2960 and 2960-S Switches Software Configuration Guide. VTP Characteristics VTP is not required. see the “Assigning Static-Access Ports to a VLAN” section on page 13-10. For configuration information. “Configuring Voice VLAN. Configure the VMPS and the client with the same VTP domain name. see Chapter 15. To participate in VTP. Voice VLAN VTP is not required. see the “Configuring an Ethernet Interface as a Trunk Port” section on page 13-16. The Catalyst 2960. VTP is required. Cisco IP Phone. For information about configuring trunk ports. or 2960-C switch. For more information. including extended-range VLANs. For more information about voice VLAN ports. If you do not want VTP to globally propagate information. for example.Chapter 13 Understanding VLANs Configuring VLANs VLAN Port Membership Modes You configure a port to belong to a VLAN by assigning a membership mode that specifies the kind of traffic the port carries and the number of VLANs to which it can belong. Trunk (IEEE 802. The VMPS can be a Catalyst 5000 or Catalyst 6500 series switch. Dynamic access A dynamic-access port can belong to one VLAN (VLAN ID 1 to 4094) and is dynamically assigned by a VMPS. there must be at least one trunk port on the switch stack connected to a trunk port of a second switch or switch stack. VTP maintains VLAN configuration consistency by managing the addition.1Q) A trunk port is a member of all VLANs by default. set the VTP mode to transparent.

Token Ring. “Configuring VTP.dat file. If the switch is in VTP server or VTP transparent mode. See the “Configuring Extended-Range VLANs” section on page 13-11. Stack members have a vlan. and you can display the file by entering the show running-config privileged EXEC command. For more information. or TrCRF. you can add. To change the VTP configuration.” You use the interface configuration mode to define the port membership mode and to add and remove ports from VLANs. Caution You can cause inconsistency in the VLAN database if you attempt to manually delete the vlan.) In VTP versions 1 and 2. modify or remove configurations for VLANs 2 to 1001 in the VLAN database. see the “Managing the MAC Address Table” section on page 5-14. TrBRF.dat file that is consistent with the stack master.0(1)SE OL-26520-02 13-5 .dat file is stored in flash memory on the stack master. Configurations for VLAN IDs 1 to 1005 are written to the file vlan. the switch must be in VTP transparent mode when you create extended-range VLANs (VLANs with IDs from 1006 to 4094). Release 15. The results of these commands are written to the running-configuration file. VTP version 3 supports extended-range VLANs in VTP server and transparent mode. (VLAN IDs 1 and 1002 to 1005 are automatically created and cannot be removed. Configuring Normal-Range VLANs Normal-range VLANs are VLANs with VLAN IDs 1 to 1005. Token Ring-Net) VLAN state (active or suspended) Maximum transmission unit (MTU) for the VLAN Security Association Identifier (SAID) Bridge identification number for TrBRF VLANs Ring number for FDDI and TrCRF VLANs Parent VLAN number for TrCRF VLANs Spanning Tree Protocol (STP) type for TrCRF VLANs VLAN number to use when translating from one VLAN type to another Catalyst 2960 and 2960-S Switches Software Configuration Guide. If you want to modify the VLAN configuration. When a port belongs to a VLAN. and you can display them by entering the show vlan privileged EXEC command. the switch learns and manages the addresses associated with the port on a per-VLAN basis.Chapter 13 Configuring VLANs Configuring Normal-Range VLANs For more detailed definitions of access and trunk modes and their functions. The vlan. but these VLANs are not saved in the VLAN database. use the commands described in these sections and in the command reference for this release. see Table 13-4 on page 13-14.dat (VLAN database). FDDI network entity title [NET]. see Chapter 14. Fiber Distributed Data Interface [FDDI]. You can set these parameters when you create a new normal-range VLAN or modify an existing VLAN in the VLAN database: • • • • • • • • • • • VLAN ID VLAN name VLAN type (Ethernet.

the switch supports VLAN IDs 1006 through 4094 only in VTP transparent mode (VTP disabled). you must define a VTP domain or VTP will not function. FDDI-Net. server. you cannot convert from VTP version 3 to version 1 or 2. VLAN numbers 1002 through 1005 are reserved for Token Ring and FDDI VLANs. page 13-8 Deleting a VLAN. see the Catalyst 5000 Series Software Configuration Guide. but it does propagate the VLAN configuration through VTP. Normal-Range VLAN Configuration Guidelines Follow these guidelines when creating and modifying normal-range VLANs in your network: • • • • The switch supports 255 VLANs in VTP client. The switch does not forward FDDI. • • Catalyst 2960 and 2960-S Switches Software Configuration Guide. With VTP versions 1 and 2. TrCRF. Switches running VTP Version 2 advertise information about these Token Ring VLANs: • • Token Ring TrBRF VLANs Token Ring TrCRF VLANs For more information on configuring Token Ring VLANs. page 13-7 Default Ethernet VLAN Configuration.Chapter 13 Configuring Normal-Range VLANs Configuring VLANs Note This section does not provide configuration details for most of these parameters. and transparent modes. page 13-10 Token Ring VLANs Although the switch does not support Token Ring connections. VTP version 3 supports extended range VLAN (VLANs 1006 to 4094) database propagation. or TrBRF traffic. VTP and VLAN configuration are also saved in the switch running configuration file. If extended VLANs are configured. the switch must be in VTP server mode or VTP transparent mode. page 13-6 Normal-Range VLAN Configuration Guidelines. page 13-6 Configuring Normal-Range VLANs. Before you can create a VLAN. page 13-8 Creating or Modifying an Ethernet VLAN. If the switch is a VTP server. a remote device such as a Catalyst 5000 series switch with Token Ring connections could be managed from one of the supported switches. Extended-range VLANs created in VTP transparent mode are not saved in the VLAN database and are not propagated. Normal-range VLANs are identified with a number between 1 and 1001. VLAN configuration for VLANs 1 to 1005 are always saved in the VLAN database. For complete information on the commands and parameters that control VLAN configuration. Release 15. If the VTP mode is transparent. page 13-9 Assigning Static-Access Ports to a VLAN. These sections contain normal-range VLAN configuration information: • • • • • • • Token Ring VLANs. See the “Configuring Extended-Range VLANs” section on page 13-11. see the command reference for this release.0(1)SE 13-6 OL-26520-02 . These are extended-range VLANs and configuration options are limited. The switch does not support Token Ring or FDDI media.

enter the show vlan privileged EXEC command. particularly if there are several adjacent switches that all have run out of spanning-tree instances. For more information about commands available in this mode. this could create a loop in the new VLAN that would not be broken. see the vlan global configuration command description in the command reference for this release. you must exit VLAN configuration mode for the configuration to take effect. they are also saved in the switch running configuration file. the switch configuration is selected as follows: • If the VTP mode is transparent in the startup configuration. the domain name and VTP mode and configuration for the first 1005 VLANs use the VLAN database information.Chapter 13 Configuring VLANs Configuring Normal-Range VLANs • The switch supports 128 spanning-tree instances. If the number of VLANs on the switch exceeds the number of supported spanning-tree instances. If the VTP mode or domain name in the startup configuration does not match the VLAN database. In a switch stack. If you have already used all available spanning-tree instances on a switch. VTP information (the vlan. Release 15. You can prevent this possibility by setting allowed lists on the trunk ports of switches that have used up their allocation of spanning-tree instances. the whole stack uses the same vlan. You can enter the copy running-config startup-config privileged EXEC command to save the configuration in the startup configuration file. When a switch joins a stack or when stacks merge. and the VTP and VLAN configurations in the startup configuration file are used. The VLAN database revision number remains unchanged in the VLAN database. Configuring Normal-Range VLANs You configure VLANs in vlan global configuration command by entering a VLAN ID. the new VLAN is carried on all trunk ports. Enter a new VLAN ID to create a VLAN. Depending on the topology of the network.dat file and running configuration. and the VLAN database and the VTP domain name from the VLAN database matches that in the startup configuration file. the VLAN information is communicated to all stack members. To display the VLAN configuration. If a switch has more active VLANs than supported spanning-tree instances. we recommend that you configure the IEEE 802. spanning tree can be enabled on 128 VLANs and is disabled on the remaining VLANs. If the VTP mode is transparent. You can use the default VLAN configuration (Table 13-2) or enter multiple commands to configure the VLAN. the VLAN database is ignored (cleared). The configurations of VLAN IDs 1 to 1005 are always saved in the VLAN database (vlan.dat file). • Note Stacking is supported only on Catalyst 2960-S switches running the LAN base image. see Chapter 17. enter the show vlan privileged EXEC command.1s Multiple STP (MSTP) on your switch to map multiple VLANs to a single spanning-tree instance. To display the VLAN configuration. For more information about MSTP. When you save VLAN and VTP information (including extended-range VLAN configuration information) in the startup configuration file and reboot the switch.0(1)SE OL-26520-02 13-7 . or enter an existing VLAN ID to modify that VLAN. adding another VLAN anywhere in the VTP domain creates a VLAN on that switch that is not running spanning-tree.” • When a switch in a stack learns a new VLAN or deletes or modifies an existing VLAN (either through VTP over network ports or through the CLI). When you have finished the configuration. • Catalyst 2960 and 2960-S Switches Software Configuration Guide. “Configuring MSTP.dat file) on the new switches will be consistent with the stack master. If you have the default allowed list on the trunk ports of that switch (which is to allow all VLANs).

For the list of default parameters that are assigned when you add a VLAN. the domain name and VLAN configuration for only the first 1005 VLANs use the VLAN database information. you only configure FDDI and Token Ring media-specific characteristics for VTP global advertisements to other switches. VLAN IDs 1002 to 1005 are reserved for Token Ring and FDDI VLANs. Note With VTP version 1 and 2. Because FDDI and Token Ring VLANs are not locally supported. disabled IEEE 802. Catalyst 2960 and 2960-S Switches Software Configuration Guide. if VTP mode is server. but they are not added to the VLAN database. VLAN name VLANxxxx. see the “Configuring Normal-Range VLANs” section on page 13-5.Chapter 13 Configuring Normal-Range VLANs Configuring VLANs • In VTP versions 1 and 2. Note The switch supports Ethernet interfaces exclusively.0(1)SE 13-8 OL-26520-02 .10 SAID MTU size Translational bridge 1 Translational bridge 2 VLAN state Remote SPAN Creating or Modifying an Ethernet VLAN Each Ethernet VLAN in the VLAN database has a unique. Release 15. you can assign VLAN IDs greater than 1006. where xxxx represents four numeric No range digits (including leading zeros) equal to the VLAN ID number 100001 (100000 plus the VLAN ID) 1500 0 0 active disabled 1 to 4294967294 1500 to 18190 0 to 1005 0 to 1005 active. Note Extended-range VLANs (VLAN IDs 1006 to 4094) are only saved in the VLAN database in VTP version 3. VTP version 3 also supports VLANs 1006 to 4094. suspend enabled. 4-digit ID that can be a number from 1 to 1001. Default Ethernet VLAN Configuration Table 13-2 shows the default configuration for Ethernet VLANs. Table 13-2 Ethernet VLAN Defaults and Ranges Parameter VLAN ID Default 1 Range 1 to 4094. See the “Configuring Extended-Range VLANs” section on page 13-11. if the switch is in VTP transparent mode. assign a number and name to the VLAN. To create a normal-range VLAN to be added to the VLAN database.

and add it to the VLAN database: Switch# configure terminal Switch(config)# vlan 20 Switch(config-vlan)# name test20 Switch(config-vlan)# end Deleting a VLAN When you delete a VLAN from a switch that is in VTP server mode. To return the VLAN name to the default settings. For example. see Chapter 27. name it test20. follow these steps to create or modify an Ethernet VLAN: Command Step 1 Step 2 Purpose Enter global configuration mode. Note configure terminal vlan vlan-id The available VLAN ID range for this command is 1 to 4094. Step 6 Step 7 Step 8 end copy running-config startup config Return to privileged EXEC mode.” Note Step 4 Step 5 mtu mtu-size remote-span The switch must be running the LAN Base image to use RSPAN. and enter VLAN configuration mode. the VLAN configuration is saved in the running configuration file as well as in the VLAN database. When you delete a VLAN from a switch that is in VTP transparent mode. They remain associated with the VLAN (and thus inactive) until you assign them to a new VLAN. Enter a new VLAN ID to create a VLAN. Caution When you delete a VLAN. (Optional) Change the MTU size (or other VLAN characteristic). If no name is entered for the VLAN. This example shows how to create Ethernet VLAN 20. For more information on remote SPAN. For information about adding VLAN IDs greater than 1005 (extended-range VLANs). Enter a VLAN ID. This saves the configuration in the switch startup configuration file. VLAN0004 is a default VLAN name for VLAN 4. see the “Configuring Extended-Range VLANs” section on page 13-11.0(1)SE OL-26520-02 13-9 . no mtu. You cannot delete the default VLANs for the different media types: Ethernet VLAN 1 and FDDI or Token Ring VLANs 1002 to 1005. any ports assigned to that VLAN become inactive. or enter an existing VLAN ID to modify that VLAN. the VLAN is deleted only on that specific switch stack. use the no name. Step 3 name vlan-name (Optional) Enter a name for the VLAN. (Optional) If the switch is in VTP transparent mode. “Configuring SPAN and RSPAN. Release 15. show vlan {name vlan-name | id vlan-id} Verify your entries. Catalyst 2960 and 2960-S Switches Software Configuration Guide.Chapter 13 Configuring VLANs Configuring Normal-Range VLANs Beginning in privileged EXEC mode. (Optional) Configure the VLAN as the RSPAN VLAN for a remote SPAN session. or no remote-span commands. the VLAN is removed from the VLAN database for all switches in the VTP domain. the default is to append the vlan-id with leading zeros to the word VLAN.

Catalyst 2960 and 2960-S Switches Software Configuration Guide. Valid VLAN IDs are 1 to 4094.0(1)SE 13-10 OL-26520-02 . follow these steps to assign a port to a VLAN in the VLAN database: Command Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Purpose Enter global configuration mode Enter the interface to be added to the VLAN. (See the “Creating or Modifying an Ethernet VLAN” section on page 13-8. Verify the VLAN membership mode of the interface. Release 15. Verify your entries in the Administrative Mode and the Access Mode VLAN fields of the display. Note If you assign an interface to a VLAN that does not exist. first use the rcommand privileged EXEC command to log in to the cluster member switch. Assign the port to a VLAN.Chapter 13 Configuring Normal-Range VLANs Configuring VLANs Beginning in privileged EXEC mode.) Beginning in privileged EXEC mode. use the default interface interface-id interface configuration command. Return to privileged EXEC mode. This saves the configuration in the switch startup configuration file. configure terminal no vlan vlan-id end show vlan brief copy running-config startup config Assigning Static-Access Ports to a VLAN You can assign a static-access port to a VLAN without having VTP globally propagate VLAN configuration information by disabling VTP (VTP transparent mode). (Optional) If the switch is in VTP transparent mode. the new VLAN is created. Define the VLAN membership mode for the port (Layer 2 access port). Return to privileged EXEC mode. follow these steps to delete a VLAN on the switch: Command Step 1 Step 2 Step 3 Step 4 Step 5 Purpose Enter global configuration mode. the VLAN configuration is saved in the running configuration file as well as in the VLAN database. If you are assigning a port on a cluster member switch to a VLAN. Verify the VLAN removal. (Optional) Save your entries in the configuration file. configure terminal interface interface-id switchport mode access switchport access vlan vlan-id end show running-config interface interface-id show interfaces interface-id switchport copy running-config startup-config To return an interface to its default configuration. Remove the VLAN by entering the VLAN ID.

but because VTP mode is transparent. page 13-11 Creating an Extended-Range VLAN. These sections contain extended-range VLAN configuration information: • • • Default VLAN Configuration. You cannot include extended-range VLANs in the pruning eligible range. extended-range VLAN configurations are not stored in the VLAN database. you can create extended-range VLANs (in the range 1006 to 4094). they are stored in the switch running configuration file. Extended-Range VLAN Configuration Guidelines Follow these guidelines when creating extended-range VLANs: • • VLAN IDs in the extended range are not saved in the VLAN database and are not recognized by VTP unless the switch is running VTP version 3.0(1)SE OL-26520-02 13-11 . Switch(config)# interface gigabitethernet2/0/1 Switch(config-if)# switchport mode access Switch(config-if)# switchport access vlan 2 Switch(config-if)# end Configuring Extended-Range VLANs With VTP version 1 and version 2. Catalyst 2960 and 2960-S Switches Software Configuration Guide. when the switch is in VTP transparent mode (VTP disabled). Note Although the switch supports 4094 VLAN IDs. End with CNTL/Z. VTP version supports extended-range VLANs in server or transparent move. page 13-11 Extended-Range VLAN Configuration Guidelines. Note The switch must be running the LAN Base image to support remote SPAN. The extended-range VLAN IDs are allowed for any switchport commands that allow VLAN IDs. Extended-range VLANs enable service providers to extend their infrastructure to a greater number of customers. one per line. Release 15. page 13-12 Default VLAN Configuration See Table 13-2 on page 13-8 for the default configuration for Ethernet VLANs.Chapter 13 Configuring VLANs Configuring Extended-Range VLANs This example shows how to configure a port as an access port in VLAN 2: Switch# configure terminal Enter configuration commands. all other characteristics must remain at the default state. You can change only the MTU size and the remote SPAN configuration state on extended-range VLANs. With VTP version 1 or 2. Extended-range VLANs created in VTP version 3 are stored in the VLAN database. see the “Supported VLANs” section on page 13-3 for the actual number of VLANs supported. and you can save the configuration in the startup configuration file by using the copy running-config startup-config privileged EXEC command.

0(1)SE 13-12 OL-26520-02 . Note configure terminal vtp mode transparent vlan vlan-id This step is not required for VTP version 3. you cannot convert to VTP version 1 or 2.1s Multiple STP (MSTP) on your switch to map multiple VLANs to a single spanning-tree instance. and RSPAN configuration are the only parameters you can change. If the number of VLANs on the switch exceeds the maximum number of spanning-tree instances. you can set the VTP mode to transparent in global configuration mode. you lose the extended-range VLAN configuration if the switch resets. and extended-range VLAN information is shared across the stack. For VTP version 1 or 2. and the extended-range VLAN is rejected. If you try to create an extended-range VLAN and there are not enough hardware resources available. but you can disable it by using the no spanning-tree vlan vlan-id global configuration command. spanning tree is disabled on any newly created VLANs. an error message is generated when you exit VLAN configuration mode. VTP version 3 saves extended-range VLANs in the VLAN database. disabling VTP. Catalyst 2960 and 2960-S Switches Software Configuration Guide. For more information about MSTP.” Although the switch stack supports a total of 255 (normal-range and extended-range) VLANs.Chapter 13 Configuring Extended-Range VLANs Configuring VLANs • In VTP version 1 and 2. Beginning in privileged EXEC mode. an error message is generated. When the maximum number of spanning-tree instances are on the switch. See the “Configuring VTP Mode” section on page 14-11. a switch must be in VTP transparent mode when you create extended-range VLANs. an error message is generated. If you create extended-range VLANs in VTP version 3. see Chapter 17. VTP version 3 supports extended VLANs in server and transparent modes. Release 15. In VTP version 1 and 2. The range is 1006 to 4094. See the description of the vlan global configuration command in the command reference for the default settings of all parameters. the whole stack uses the same running configuration and saved configuration. STP is enabled by default on extended-range VLANs. extended-range VLANs are not saved in the VLAN database. Otherwise. In a switch stack. If VTP mode is server or client. “Configuring MSTP. Step 3 Enter an extended-range VLAN ID and enter VLAN configuration mode. The extended-range VLAN has the default Ethernet VLAN characteristics (see Table 13-2) and the MTU size. and the extended-range VLAN is rejected. the number of configured features affects the use of the switch hardware. You can save the extended-range VLAN configuration in the switch startup configuration file by using the copy running-config startup-config privileged EXEC command. if you enter an extended-range VLAN ID when the switch is not in VTP transparent mode. • • • • Creating an Extended-Range VLAN You create an extended-range VLAN in global configuration mode by entering the vlan global configuration command with a VLAN ID from 1006 to 4094. In VTP version 1 or 2. Configure the switch for VTP transparent mode. we recommend that you configure the IEEE 802. follow these steps to create an extended-range VLAN: Command Step 1 Step 2 Purpose Enter global configuration mode. and the extended-range VLAN is not created. You should save this configuration to the startup configuration so that the switch boots up in VTP transparent mode. they are saved in the switch running configuration file.

if the switch resets. Table 13-3 lists the privileged EXEC commands for monitoring VLANs. The display includes VLAN status. enter VLAN configuration mode. This example shows how to create a new extended-range VLAN with all default characteristics. the VLAN configuration is also saved in the VLAN database. and the extended-range VLAN IDs will not be saved. see the command reference for this release. use the no vlan vlan-id global configuration command. RSPAN is supported only if the switch is running the LAN Base image. Note mtu mtu-size Although all VLAN commands appear in the CLI help. and remote-span commands are supported for extended-range VLANs. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Step 5 remote-span (Optional) Configure the VLAN as the RSPAN VLAN. See the “Configuring a VLAN as an RSPAN VLAN” section on page 27-18. it will default to VTP server mode. For more details about the show command options and explanations of output fields. ports. Return to privileged EXEC mode. Save your entries in the switch startup configuration file. and save the new VLAN in the switch startup configuration file: Switch(config)# vtp mode transparent Switch(config)# vlan 2000 Switch(config-vlan)# end Switch# copy running-config startup config Displaying VLANs Use the show vlan privileged EXEC command to display a list of all VLANs on the switch. Display parameters for all VLANs or the specified VLAN on the switch. including extended-range VLANs. To delete an extended-range VLAN. To save extended-range VLAN configurations. Note Step 6 Step 7 Step 8 end show vlan id vlan-id copy running-config startup config With VTP version 3. The procedure for assigning static-access ports to an extended-range VLAN is the same as for normal-range VLANs. and configuration information. Verify that the VLAN has been created. See the “Assigning Static-Access Ports to a VLAN” section on page 13-10. only the mtu mtu-size.Chapter 13 Configuring VLANs Displaying VLANs Command Step 4 Purpose (Optional) Modify the VLAN by changing the MTU size. Table 13-3 VLAN Monitoring Commands Command show interfaces [vlan vlan-id] show vlan [id vlan-id] Purpose Display characteristics for all interfaces or for the specified VLAN configured on the switch.0(1)SE OL-26520-02 13-13 . you need to save the VTP transparent mode configuration and the extended-range VLAN configuration in the switch startup configuration file. Otherwise. Release 15.

Chapter 13 Configuring VLAN Trunks Configuring VLANs Configuring VLAN Trunks These sections contain this conceptual information: • • • • Trunking Overview. you should configure interfaces connected to devices that do not support DTP to not forward DTP frames. use the switchport mode access interface configuration command to disable trunking. However. some internetworking devices might forward DTP frames improperly. For more information about EtherChannel. The interface becomes a trunk interface if the neighboring interface is set to trunk or desirable mode. use the switchport mode trunk and switchport nonegotiate interface configuration commands to cause the interface to become a trunk but to not generate DTP frames. Makes the interface actively attempt to convert the link to a trunk link. Makes the interface able to convert the link to a trunk link. Trunk negotiation is managed by the Dynamic Trunking Protocol (DTP). switchport mode dynamic auto switchport mode dynamic desirable Catalyst 2960 and 2960-S Switches Software Configuration Guide. and you can extend the VLANs across an entire network. The interface becomes a trunk interface if the neighboring interface is set to trunk. which could cause misconfigurations.” Ethernet trunk interfaces support different trunking modes (see Table 13-4). that is. page 13-14 Default Layer 2 Ethernet Interface VLAN Configuration. The default switchport mode for all Ethernet interfaces is dynamic auto.1Q encapsulation. or auto mode. page 13-20 Trunking Overview A trunk is a point-to-point link between one or more Ethernet switch interfaces and another networking device such as a router or a switch. desirable. Table 13-4 Layer 2 Interface Modes Mode switchport mode access Function Puts the interface (access port) into permanent nontrunking mode and negotiates to convert the link into a nontrunk link. You can set an interface as trunking or nontrunking or to negotiate trunking with the neighboring interface. page 13-16 Configuring Trunk Ports for Load Sharing. To enable trunking to a device that does not support DTP. To avoid this. see Chapter 38. Ethernet trunks carry the traffic of multiple VLANs over a single link. You can configure a trunk on a single Ethernet interface or on an EtherChannel bundle. To autonegotiate trunking. to turn off DTP. The switch supports IEEE 802. • • If you do not intend to trunk across those links.0(1)SE 13-14 OL-26520-02 . “Configuring EtherChannels and Link-State Tracking. The interface becomes a nontrunk interface regardless of whether or not the neighboring interface is a trunk interface. the interfaces must be in the same VTP domain. Release 15. page 13-15 Configuring an Ethernet Interface as a Trunk Port. which is a Point-to-Point Protocol.

1Q trunk or disable spanning tree on every VLAN in the network. the switches maintain one spanning-tree instance for each VLAN allowed on the trunks. spanning-tree information for each VLAN is maintained by Cisco switches separated by a cloud of non-Cisco IEEE 802.0(1)SE OL-26520-02 13-15 . • Default Layer 2 Ethernet Interface VLAN Configuration Table 13-5 shows the default Layer 2 Ethernet interface VLAN configuration. Release 15.1Q cloud separating the Cisco switches is treated as a single trunk link between the switches. Table 13-5 Default Layer 2 Ethernet Interface VLAN Configuration Feature Interface mode Allowed VLAN range VLAN range eligible for pruning Default VLAN (for access ports) Default Setting switchport mode dynamic auto VLANs 1 to 4094 VLANs 2 to 1001 VLAN 1 Native VLAN (for IEEE 802.1Q trunks. Disabling spanning tree on the native VLAN of an IEEE 802. spanning-tree loops might result.1Q trunks) VLAN 1 Catalyst 2960 and 2960-S Switches Software Configuration Guide. You must manually configure the neighboring interface as a trunk interface to establish a trunk link. You can use this command only when the interface switchport mode is access or trunk. Make sure your network is loop-free before you disable spanning tree.1Q switch. the Cisco switch combines the spanning-tree instance of the VLAN of the trunk with the spanning-tree instance of the non-Cisco IEEE 802. However. Non-Cisco devices might support one spanning-tree instance for all VLANs.Chapter 13 Configuring VLANs Configuring VLAN Trunks Table 13-4 Layer 2 Interface Modes (continued) Mode switchport mode trunk Function Puts the interface into permanent trunking mode and negotiates to convert the neighboring link into a trunk link.1Q trunks impose these limitations on the trunking strategy for a network: • In a network of Cisco switches connected through IEEE 802.1Q trunk is the same on both ends of the trunk link. The interface becomes a trunk interface even if the neighboring interface is not a trunk interface. The non-Cisco IEEE 802. When you connect a Cisco switch to a non-Cisco device through an IEEE 802. Prevents the interface from generating DTP frames.1Q switches.1Q trunk.1Q Configuration Considerations The IEEE 802. If the native VLAN on one end of the trunk is different from the native VLAN on the other end. • Make sure the native VLAN for an IEEE 802. switchport nonegotiate IEEE 802.1Q trunk without disabling spanning tree on every VLAN in the network can potentially cause spanning-tree loops. We recommend that you leave spanning tree enabled on the native VLAN of an IEEE 802.

• • We recommend that you configure no more than 24 trunk ports in PVST mode and no more than 40 trunk ports in MST mode. Trunk ports can be grouped into EtherChannel port groups. the switch propagates the setting you entered to all ports in the group: – allowed-VLAN list. If you change the configuration of one of these parameters. page 13-18 Changing the Pruning-Eligible List. but all trunks in the group must have the same configuration. an error message appears. A port in dynamic mode can negotiate with its neighbor to become a trunk port.1x is not enabled. the port mode is not changed.1x on a trunk port. Release 15. If you try to change the mode of an IEEE 802. page 13-16 Defining the Allowed VLANs on a Trunk. the port mode is not changed. all ports cease to be trunks.1x-enabled port to trunk.Chapter 13 Configuring VLAN Trunks Configuring VLANs Configuring an Ethernet Interface as a Trunk Port Because trunk ports send and receive VTP advertisements. page 13-19 Configuring the Native VLAN for Untagged Traffic. If you try to enable IEEE 802. – STP Port Fast setting.1x on a dynamic port. If you try to enable IEEE 802. When a group is first created. These sections contain this configuration information: • • • • Interaction with Other Features. an error message appears. – trunk status: if one port in a port group ceases to be a trunk. the switch cannot receive any VTP advertisements.1x is not enabled. • Catalyst 2960 and 2960-S Switches Software Configuration Guide. Otherwise. If you try to change the mode of an IEEE 802. and IEEE 802. and IEEE 802. all ports follow the parameters set for the first port to be added to the group.0(1)SE 13-16 OL-26520-02 . to use VTP you must ensure that at least one trunk port is configured on the switch and that this trunk port is connected to the trunk port of a second switch. page 13-20 Interaction with Other Features Trunking interacts with other features in these ways: • • A trunk port cannot be a secure port.1x-enabled port to dynamic. – STP port priority for each VLAN.

show interfaces interface-id switchport Display the switchport configuration of the interface in the Administrative Mode and the Administrative Trunking Encapsulation fields of the display. • • • configure terminal interface interface-id switchport mode {dynamic {auto | desirable} | trunk} dynamic auto—Set the interface to a trunk link if the neighboring interface is set to trunk or desirable mode.Chapter 13 Configuring VLANs Configuring VLAN Trunks Configuring a Trunk Port Beginning in privileged EXEC mode. use the default interface interface-id interface configuration command. This example shows how to configure a port as an IEEE 802. desirable. Switch(config)# interface gigabitethernet1/0/2 Switch(config-if)# switchport mode dynamic desirable Switch(config-if)# end Catalyst 2960 and 2960-S Switches Software Configuration Guide. End with CNTL/Z. Step 8 Step 9 To return an interface to its default configuration. or auto mode. use the no switchport trunk interface configuration command.0(1)SE OL-26520-02 13-17 . This is the default. dynamic desirable—Set the interface to a trunk link if the neighboring interface is set to trunk. To disable trunking. Step 4 Step 5 Step 6 Step 7 switchport access vlan vlan-id switchport trunk native vlan vlan-id end (Optional) Specify the default VLAN. To reset all trunking characteristics of a trunking interface to the defaults. Configure the interface as a Layer 2 trunk (required only if the interface is a Layer 2 access port or to specify the trunking mode).1Q trunking. The example assumes that the neighbor interface is configured to support IEEE 802. which is used if the interface stops trunking. trunk—Set the interface in permanent trunking mode and negotiate to convert the link to a trunk link even if the neighboring interface is not a trunk interface. Switch# configure terminal Enter configuration commands. Specify the port to be configured for trunking.1Q trunks. Return to privileged EXEC mode. show interfaces interface-id trunk copy running-config startup-config Display the trunk configuration of the interface. follow these steps to configure a port as a trunk port: Command Step 1 Step 2 Step 3 Purpose Enter global configuration mode. (Optional) Save your entries in the configuration file. use the switchport mode access interface configuration command to configure the port as a static-access port. Release 15. Specify the native VLAN for IEEE 802. one per line.1Q trunk. and enter interface configuration mode.

it is added to the access VLAN. use the switchport trunk allowed vlan remove vlan-list interface configuration command to remove specific VLANs from the allowed list. Note VLAN 1 is the default VLAN on all trunk ports in all Cisco switches. However. Link Aggregation Control Protocol (LACP). follow these steps to modify the allowed list of a trunk: Command Step 1 Step 2 Step 3 Step 4 Purpose Enter global configuration mode. show interfaces interface-id switchport Verify your entries in the Trunking VLANs Enabled field of the display. (Optional) Configure the list of VLANs allowed on the trunk. the trunk port automatically becomes a member of the enabled VLAN. separated by a hyphen. except. To reduce the risk of spanning-tree loops or storms. All VLAN IDs. the lower one first. the trunk port does not become a member of the new VLAN. and if the VLAN is in the allowed list for the port.Chapter 13 Configuring VLAN Trunks Configuring VLANs Defining the Allowed VLANs on a Trunk By default. regardless of the switchport trunk allowed setting. Configure the interface as a VLAN trunk port. When VTP detects a newly enabled VLAN and the VLAN is in the allowed list for a trunk port. you can disable VLAN 1 on any individual VLAN trunk port by removing VLAN 1 from the allowed list. a trunk port sends traffic to and receives traffic from all VLANs. A trunk port can become a member of a VLAN if the VLAN is enabled. configure terminal interface interface-id switchport mode trunk switchport trunk allowed vlan {add | all | except | remove} vlan-list Step 5 Step 6 Step 7 end copy running-config startup-config Return to privileged EXEC mode. Specify the port to be configured. If the access VLAN is set to 1. When VTP detects a new VLAN and the VLAN is not in the allowed list for a trunk port. Port Aggregation Protocol (PAgP). Do not enter any spaces between comma-separated VLAN parameters or in hyphen-specified ranges. and VTP in VLAN 1. The same is true for any VLAN that has been disabled on the port. If a trunk port with VLAN 1 disabled is converted to a nontrunk port. the interface continues to sent and receive management traffic. All VLANs are allowed by default. Cisco Discovery Protocol (CDP). For explanations about using the add. The vlan-list parameter is either a single VLAN number from 1 to 4094 or a range of VLANs described by two VLAN numbers. (Optional) Save your entries in the configuration file. Beginning in privileged EXEC mode. 1 to 4094. DTP.0(1)SE 13-18 OL-26520-02 . and enter interface configuration mode. see the command reference for this release. all. Release 15. You can use the VLAN 1 minimization feature to disable VLAN 1 on any individual VLAN trunk link so that no user traffic (including spanning-tree advertisements) is sent or received on VLAN 1. and it has previously been a requirement that VLAN 1 always be enabled on every trunk link. preventing traffic from those VLANs from passing over the trunk. and remove keywords. if VTP knows of the VLAN. the port will be added to VLAN 1. Catalyst 2960 and 2960-S Switches Software Configuration Guide. To restrict the traffic a trunk carries. When you remove VLAN 1 from a trunk port. for example. are allowed on each trunk. you can remove VLANs from the allowed list.

configure terminal interface interface-id switchport trunk pruning vlan {add | except | none | remove} vlan-list [. The “Enabling VTP Pruning” section on page 14-16 describes how to enable VTP pruning. Select the trunk port for which VLANs should be pruned.vlan[. (Optional) Save your entries in the configuration file.0(1)SE OL-26520-02 13-19 . Extended-range VLANs (VLAN IDs 1006 to 4094) cannot be pruned. use a hyphen to designate a range of IDs. Valid IDs are 2 to 1001. VLANs that are pruning-ineligible receive flooded traffic.]] Step 4 Step 5 Step 6 end copy running-config startup-config Return to privileged EXEC mode. use the no switchport trunk pruning vlan interface configuration command. This example shows how to remove VLAN 2 from the allowed VLAN list on a port: Switch(config)# interface gigabitethernet1/0/1 Switch(config-if)# switchport trunk allowed vlan remove 2 Switch(config-if)# end Changing the Pruning-Eligible List The pruning-eligible list applies only to trunk ports. and enter interface configuration mode. The default list of VLANs allowed to be pruned contains VLANs 2 to 1001. Beginning in privileged EXEC mode.. Catalyst 2960 and 2960-S Switches Software Configuration Guide. Each trunk port has its own eligibility list. (See the “VTP Pruning” section on page 14-6). none. For explanations about using the add.Chapter 13 Configuring VLANs Configuring VLAN Trunks To return to the default allowed VLAN list of all VLANs. Separate nonconsecutive V