Cisco WS-CBS3032-DEL Software Configuration Manual

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 Cisco Catalyst Blade Switch 3130 and 3032 for Dell Software Configuration Guide Cisco IOS Release 12.2(58)SE April 2011 Text Part Number: OL-13270-06

STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at 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. (1005R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental. Cisco Catalyst Blade Switch 3130 and 3032 for Dell Software Configuration Guide © 2008–20010 Cisco Systems, Inc. All rights reserved.

OL-13270-06 C O N T E N T S Preface xlix Audience xlix Purpose xlix Conventions xlix Related Publications l Obtaining Documentation and Submitting a Service Request li C H A P T E R 1 Overview 1-1 Features 1-1 Deployment Features 1-3 Performance Features 1-4 Management Options 1-5 Manageability Features 1-6 Availability and Redundancy Features 1-8 VLAN Features 1-9 Security Features 1-10 QoS and CoS Features 1-13 Layer 3 Features 1-14 Monitoring Features 1-15 Default Settings After Initial Switch Configuration 1-16 Network Configuration Examples 1-20 Design Concepts for Using the Switch 1-20 Small to Medium-Sized Network 1-23 Where to Go Next 1-24 C H A P T E R 2 Using the Command-Line Interface 2-1 Understanding Command Modes 2-1 Understanding the Help System 2-3 Understanding Abbreviated Commands 2-3 Understanding no and default Forms of Commands 2-4 Understanding CLI Error Messages 2-4 Using Configuration Logging 2-5 Using Command History 2-5

OL-13270-06 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 2-10 C H A P T E R 3 Assigning the Switch IP Address and Default Gateway 3-1 Understanding the Boot Process 3-2 Assigning Switch Information 3-3 Default Switch Information 3-3 Understanding DHCP-Based Autoconfiguration 3-4 DHCP Client Request Process 3-4 Understanding DHCP-based Autoconfiguration and Image Update 3-5 DHCP Autoconfiguration 3-5 DHCP Auto-Image Update 3-6 Limitations and Restrictions 3-6 Configuring DHCP-Based Autoconfiguration 3-7 DHCP Server Configuration Guidelines 3-7 Configuring the TFTP Server 3-8 Configuring the DNS 3-8 Configuring the Relay Device 3-8 Obtaining Configuration Files 3-9 Example Configuration 3-10 Configuring the DHCP Auto Configuration and Image Update Features 3-12 Configuring DHCP Autoconfiguration (Only Configuration File) 3-12 Configuring DHCP Auto-Image Update (Configuration File and Image) 3-13 Configuring the Client 3-14 Manually Assigning IP Information 3-15 Checking and Saving the Running Configuration 3-17 Configuring the NVRAM Buffer Size 3-18 Modifying the Startup Configuration 3-19 Default Boot Configuration 3-19 Automatically Downloading a Configuration File 3-19 Specifying the Filename to Read and Write the System Configuration 3-20

OL-13270-06 Booting Manually 3-20 Booting a Specific Software Image 3-21 Controlling Environment Variables 3-22 Scheduling a Reload of the Software Image 3-24 Configuring a Scheduled Reload 3-24 Displaying Scheduled Reload Information 3-25 C H A P T E R 4 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 4-3 ConfigID 4-3 DeviceID 4-4 Hostname and DeviceID 4-4 Using Hostname, DeviceID, and ConfigID 4-4 Understanding Cisco IOS Agents 4-5 Initial Configuration 4-5 Incremental (Partial) Configuration 4-6 Synchronized Configuration 4-6 Configuring Cisco IOS Agents 4-6 Enabling Automated CNS Configuration 4-7 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-13 Displaying CNS Configuration 4-14 C H A P T E R 5 Administering the Switch 5-1 Managing the System Time and Date 5-1 Understanding the System Clock 5-2 Understanding Network Time Protocol 5-2 NTP Version 4 5-4 Configuring Time and Date Manually 5-4 Setting the System Clock 5-5 Displaying the Time and Date Configuration 5-5 Configuring the Time Zone 5-6 Configuring Summer Time (Daylight Saving Time) 5-7

OL-13270-06 Configuring a System Name and Prompt 5-8 Default System Name and Prompt Configuration 5-9 Configuring a System Name 5-9 Understanding DNS 5-9 Default DNS Configuration 5-10 Setting Up DNS 5-10 Displaying the DNS Configuration 5-11 Creating a Banner 5-11 Default Banner Configuration 5-11 Configuring a Message-of-the-Day Login Banner 5-12 Configuring a Login Banner 5-13 Managing the MAC Address Table 5-13 Building the Address Table 5-14 MAC Addresses and VLANs 5-14 MAC Addresses and Switch Stacks 5-15 Default MAC Address Table Configuration 5-15 Changing the Address Aging Time 5-16 Removing Dynamic Address Entries 5-16 Configuring MAC Address Change Notification Traps 5-16 Configuring MAC Address Move Notification Traps 5-18 Configuring MAC Threshold Notification Traps 5-19 Adding and Removing Static Address Entries 5-20 Configuring Unicast MAC Address Filtering 5-21 Disabling MAC Address Learning on a VLAN 5-23 Displaying Address Table Entries 5-24 Managing the ARP Table 5-24 C H A P T E R 6 Configuring Switch-Based Authentication 6-1 Preventing Unauthorized Access to Your Switch 6-1 Protecting Access to Privileged EXEC Commands 6-2 Default Password and Privilege Level Configuration 6-2 Setting or Changing a Static Enable Password 6-3 Protecting Enable and Enable Secret Passwords with Encryption 6-3 Disabling Password Recovery 6-5 Setting a Telnet Password for a Terminal Line 6-6 Configuring Username and Password Pairs 6-6 Configuring Multiple Privilege Levels 6-7 Setting the Privilege Level for a Command 6-8 Changing the Default Privilege Level for Lines 6-9

OL-13270-06 Logging into and Exiting a Privilege Level 6-9 Controlling Switch Access with TACACS+ 6-10 Understanding TACACS+ 6-10 TACACS+ Operation 6-12 Configuring TACACS+ 6-12 Default TACACS+ Configuration 6-13 Identifying the TACACS+ Server Host and Setting the Authentication Key 6-13 Configuring TACACS+ Login Authentication 6-14 Configuring TACACS+ Authorization for Privileged EXEC Access and Network Services 6-16 Starting TACACS+ Accounting 6-17 Establishing a Session with a Router if the AAA Server is Unreachable 6-17 Displaying the TACACS+ Configuration 6-17 Controlling Switch Access with RADIUS 6-18 Understanding RADIUS 6-18 RADIUS Operation 6-19 RADIUS Change of Authorization 6-20 Overview 6-20 Change-of-Authorization Requests 6-21 CoA Request Response Code 6-22 CoA Request Commands 6-23 Stacking Guidelines for Session Termination 6-26 Configuring RADIUS 6-27 Default RADIUS Configuration 6-27 Identifying the RADIUS Server Host 6-27 Configuring RADIUS Login Authentication 6-30 Defining AAA Server Groups 6-32 Configuring RADIUS Authorization for User Privileged Access and Network Services 6-34 Starting RADIUS Accounting 6-35 Establishing a Session with a Router if the AAA Server is Unreachable 6-35 Configuring Settings for All RADIUS Servers 6-36 Configuring the Switch to Use Vendor-Specific RADIUS Attributes 6-36 Configuring the Switch for Vendor-Proprietary RADIUS Server Communication 6-38 Configuring CoA on the Switch 6-39 Monitoring and Troubleshooting CoA Functionality 6-40 Configuring RADIUS Server Load Balancing 6-40 Displaying the RADIUS Configuration 6-40 Controlling Switch Access with Kerberos 6-40 Understanding Kerberos 6-41 Kerberos Operation 6-43

OL-13270-06 Authenticating to a Boundary Switch 6-43 Obtaining a TGT from a KDC 6-43 Authenticating to Network Services 6-44 Configuring Kerberos 6-44 Configuring the Switch for Local Authentication and Authorization 6-44 Configuring the Switch for Secure Shell 6-45 Understanding SSH 6-46 SSH Servers, Integrated Clients, and Supported Versions 6-46 Limitations 6-47 Configuring SSH 6-47 Configuration Guidelines 6-47 Setting Up the Switch to Run SSH 6-47 Configuring the SSH Server 6-48 Displaying the SSH Configuration and Status 6-49 Configuring the Switch for Secure Socket Layer HTTP 6-50 Understanding Secure HTTP Servers and Clients 6-50 Certificate Authority Trustpoints 6-50 CipherSuites 6-51 Configuring Secure HTTP Servers and Clients 6-52 Default SSL Configuration 6-52 SSL Configuration Guidelines 6-52 Configuring a CA Trustpoint 6-53 Configuring the Secure HTTP Server 6-54 Configuring the Secure HTTP Client 6-55 Displaying Secure HTTP Server and Client Status 6-56 Configuring the Switch for Secure Copy Protocol 6-57 Information About Secure Copy 6-57 C H A P T E R 7 Managing Switch Stacks 7-1 Understanding Switch Stacks 7-1 Switch Stack Membership 7-3 Stack Master Election and Re-Election 7-6 Switch Stack Bridge ID and Router MAC Address 7-8 Stack Member Numbers 7-8 Stack Member Priority Values 7-9 Switch Stack Offline Configuration 7-9 Effects of Adding a Provisioned Switch to a Switch Stack 7-10 Effects of Replacing a Provisioned Switch in a Switch Stack 7-11 Effects of Removing a Provisioned Switch from a Switch Stack 7-11

OL-13270-06 Hardware Compatibility and SDM Mismatch Mode in Switch Stacks 7-12 Switch Stack Software Compatibility Recommendations 7-12 Stack Protocol Version Compatibility 7-12 Major Version Number Incompatibility Among Switches 7-12 Minor Version Number Incompatibility Among Switches 7-13 Understanding Auto-Upgrade and Auto-Advise 7-13 Auto-Upgrade and Auto-Advise Example Messages 7-14 Incompatible Software and Stack Member Image Upgrades 7-16 Switch Stack Configuration Files 7-16 Additional Considerations for System-Wide Configuration on Switch Stacks 7-17 Switch Stack Management Connectivity 7-18 Connectivity to the Switch Stack Through an IP Address 7-18 Connectivity to the Switch Stack Through an SSH Session 7-18 Connectivity to the Switch Stack Through Console Ports or Ethernet Management Ports 7-18 Connectivity to Specific Stack Members 7-19 Switch Stack Configuration Scenarios 7-19 Configuring the Switch Stack 7-21 Default Switch Stack Configuration 7-21 Enabling Persistent MAC Address 7-21 Assigning Stack Member Information 7-24 Assigning a Stack Member Number 7-24 Setting the Stack Member Priority Value 7-25 Provisioning a New Member for a Switch Stack 7-25 Accessing the CLI of a Specific Stack Member 7-26 Displaying Switch Stack Information 7-27 Troubleshooting Stacks 7-27 Manually Disabling a Stack Port 7-28 Re-Enabling a Stack Port While Another Member Starts 7-28 Understanding the show switch stack-ports summary Output 7-29 Identifying Loopback Problems 7-30 Software Loopback 7-30 Software Loopback Example: No Connected Stack Cable 7-31 Software Loopback Examples: Connected Stack Cables 7-31 Hardware Loopback 7-32 Hardware Loopback Example: LINK OK event 7-32 Hardware Loop Example: LINK NOT OK Event 7-33 Finding a Disconnected Stack Cable 7-33 Fixing a Bad Connection Between Stack Ports 7-34

OL-13270-06 C H A P T E R 8 Configuring SDM Templates 8-1 Understanding the SDM Templates 8-1 Dual IPv4 and IPv6 SDM Templates 8-2 SDM Templates and Switch Stacks 8-3 Configuring the Switch SDM Template 8-4 Default SDM Template 8-4 SDM Template Configuration Guidelines 8-4 Setting the SDM Template 8-5 Displaying the SDM Templates 8-6 C H A P T E R 9 Configuring IEEE 802.1x Port-Based Authentication 9-1 Understanding IEEE 802.1x Port-Based Authentication 9-2 Device Roles 9-3 Authentication Process 9-4 Authentication Initiation and Message Exchange 9-6 Authentication Manager 9-8 Port-Based Authentication Methods 9-8 Per-User ACLs and Filter-Ids 9-9 Authentication Manager CLI Commands 9-9 Ports in Authorized and Unauthorized States 9-11 802.1x Authentication and Switch Stacks 9-12 802.1x Host Mode 9-12 802.1x Multiple Authentication Mode 9-13 MAC Move 9-14 MAC Replace 9-14 802.1x Accounting 9-15 802.1x Accounting Attribute-Value Pairs 9-15 802.1x Readiness Check 9-16 802.1x Authentication with VLAN Assignment 9-16 802.1x Authentication with Per-User ACLs 9-18 802.1x Authentication with Downloadable ACLs and Redirect URLs 9-19 Cisco Secure ACS and Attribute-Value Pairs for the Redirect URL 9-20 Cisco Secure ACS and Attribute-Value Pairs for Downloadable ACLs 9-21 VLAN ID-based MAC Authentication 9-21 802.1x Authentication with Guest VLAN 9-21 802.1x Authentication with Restricted VLAN 9-22 802.1x Authentication with Inaccessible Authentication Bypass 9-23 Overview 9-23 Support on Multiple-Authentication Ports 9-24

OL-13270-06 Authentication Results 9-24 Feature Interactions 9-24 802.1x Authentication with Voice VLAN Ports 9-25 802.1x Authentication with Port Security 9-26 802.1x Authentication with Wake-on-LAN 9-26 802.1x User Distribution 9-26 802.1x User Distribution Configuration Guidelines 9-27 802.1x Authentication with MAC Authentication Bypass 9-27 Network Admission Control Layer 2 802.1x Validation 9-28 Flexible Authentication Ordering 9-29 Open1x Authentication 9-29 Multidomain Authentication 9-30 Voice Aware 802.1x Security 9-31 802.1x Supplicant and Authenticator Switches with Network Edge Access Topology (NEAT) 9-31 Guidelines 9-32 Common Session ID 9-32 Configuring 802.1x Authentication 9-33 Default 802.1x Authentication Configuration 9-34 802.1x Authentication Configuration Guidelines 9-35 802.1x Authentication 9-35 VLAN Assignment, Guest VLAN, Restricted VLAN, and Inaccessible Authentication Bypass 9-36 MAC Authentication Bypass 9-37 Maximum Number of Allowed Devices Per Port 9-37 Configuring 802.1x Violation Modes 9-38 Configuring 802.1x Authentication 9-38 Configuring 802.1x Readiness Check 9-40 Configuring Voice Aware 802.1x Security 9-41 Configuring the Switch-to-RADIUS-Server Communication 9-42 Configuring the Host Mode 9-44 Configuring Periodic Re-Authentication 9-45 Manually Re-Authenticating a Client Connected to a Port 9-46 Changing the Quiet Period 9-46 Changing the Switch-to-Client Retransmission Time 9-46 Setting the Switch-to-Client Frame-Retransmission Number 9-47 Setting the Re-Authentication Number 9-48 Enabling MAC Move 9-48 Enabling MAC Replace 9-49 Configuring 802.1x Accounting 9-50 Configuring a Guest VLAN 9-51

OL-13270-06 Configuring a Restricted VLAN 9-52 Configuring the Inaccessible Authentication Bypass Feature 9-53 Configuring 802.1x User Distribution 9-56 Configuring 802.1x Authentication with WoL 9-57 Configuring MAC Authentication Bypass 9-57 Configuring NAC Layer 2 802.1x Validation 9-58 Configuring an Authenticator and a Supplicant Switch with NEAT 9-59 Configuring NEAT with ASP 9-60 Configuring 802.1x Authentication with Downloadable ACLs and Redirect URLs 9-60 Configuring Downloadable ACLs 9-61 Configuring a Downloadable Policy 9-62 Configuring VLAN ID-based MAC Authentication 9-63 Configuring Flexible Authentication Ordering 9-64 Configuring Open1x 9-64 Disabling 802.1x Authentication on the Port 9-65 Resetting the 802.1x Authentication Configuration to the Default Values 9-66 Displaying 802.1x Statistics and Status 9-66 C H A P T E R 10 Configuring Web-Based Authentication 10-1 Understanding Web-Based Authentication 10-1 Device Roles 10-2 Host Detection 10-2 Session Creation 10-3 Authentication Process 10-3 Local Web Authentication Banner 10-4 Web Authentication Customizable Web Pages 10-6 Guidelines 10-6 Web-based Authentication Interactions with Other Features 10-7 Port Security 10-7 LAN Port IP 10-8 Gateway IP 10-8 ACLs 10-8 Context-Based Access Control 10-8 802.1x Authentication 10-8 EtherChannel 10-8 Configuring Web-Based Authentication 10-9 Default Web-Based Authentication Configuration 10-9 Web-Based Authentication Configuration Guidelines and Restrictions 10-9 Web-Based Authentication Configuration Task List 10-10

OL-13270-06 Configuring the Authentication Rule and Interfaces 10-10 Configuring AAA Authentication 10-11 Configuring Switch-to-RADIUS-Server Communication 10-11 Configuring the HTTP Server 10-13 Customizing the Authentication Proxy Web Pages 10-13 Specifying a Redirection URL for Successful Login 10-15 Configuring the Web-Based Authentication Parameters 10-15 Configuring a Web Authentication Local Banner 10-16 Removing Web-Based Authentication Cache Entries 10-16 Displaying Web-Based Authentication Status 10-17 C H A P T E R 11 Configuring Interface Characteristics 11-1 Understanding Interface Types 11-1 Port-Based VLANs 11-2 Switch Ports 11-2 Access Ports 11-3 Trunk Ports 11-3 Tunnel Ports 11-3 Routed Ports 11-4 Switch Virtual Interfaces 11-4 SVI Autostate Exclude 11-5 EtherChannel Port Groups 11-6 10-Gigabit Ethernet Interfaces 11-6 Connecting Interfaces 11-6 Using Interface Configuration Mode 11-8 Procedures for Configuring Interfaces 11-9 Configuring a Range of Interfaces 11-9 Configuring and Using Interface Range Macros 11-12 Using the Internal Ethernet Management Port 11-13 Understanding the Internal Ethernet Management Port 11-13 Supported Features on the Ethernet Management Port 11-17 Layer 3 Routing Configuration Guidelines 11-17 Monitoring the Ethernet Management Port 11-18 TFTP and the Ethernet Management Port 11-18 Configuring Ethernet Interfaces 11-18 Default Ethernet Interface Configuration 11-19 Configuring Interface Speed and Duplex Mode 11-20 Speed and Duplex Configuration Guidelines 11-20 Setting the Interface Speed and Duplex Parameters 11-21

OL-13270-06 Configuring IEEE 802.3x Flow Control 11-22 Configuring Auto-MDIX on an Interface 11-23 Adding a Description for an Interface 11-24 Configuring Layer 3 Interfaces 11-25 Configuring SVI Autostate Exclude 11-26 Configuring the System MTU 11-27 Monitoring and Maintaining the Interfaces 11-29 Monitoring Interface Status 11-29 Clearing and Resetting Interfaces and Counters 11-30 Shutting Down and Restarting the Interface 11-30 C H A P T E R 12 Configuring Smartports Macros 12-1 Understanding Smartports Macros 12-1 Configuring Smartports Macros 12-2 Default Smartports Macro Configuration 12-2 Smartports Macro Configuration Guidelines 12-2 Creating Smartports Macros 12-4 Applying Smartports Macros 12-5 Applying Cisco-Default Smartports Macros 12-6 Displaying Smartports Macros 12-8 C H A P T E R 13 Configuring VLANs 13-1 Understanding VLANs 13-1 Supported VLANs 13-2 VLAN Port Membership Modes 13-3 Configuring Normal-Range VLANs 13-4 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 13-11 Creating an Extended-Range VLAN 13-12 Creating an Extended-Range VLAN with an Internal VLAN ID 13-13

OL-13270-06 Displaying VLANs 13-14 Configuring VLAN Trunks 13-15 Trunking Overview 13-15 IEEE 802.1Q Configuration Considerations 13-17 Default Layer 2 Ethernet Interface VLAN Configuration 13-17 Configuring an Ethernet Interface as a Trunk Port 13-18 Interaction with Other Features 13-18 Configuring a Trunk Port 13-19 Defining the Allowed VLANs on a Trunk 13-20 Changing the Pruning-Eligible List 13-21 Configuring the Native VLAN for Untagged Traffic 13-22 Configuring Trunk Ports for Load Sharing 13-22 Load Sharing Using STP Port Priorities 13-23 Load Sharing Using STP Path Cost 13-24 Configuring VMPS 13-26 Understanding VMPS 13-26 Dynamic-Access Port VLAN Membership 13-27 Default VMPS Client Configuration 13-27 VMPS Configuration Guidelines 13-28 Configuring the VMPS Client 13-28 Entering the IP Address of the VMPS 13-28 Configuring Dynamic-Access Ports on VMPS Clients 13-29 Reconfirming VLAN Memberships 13-29 Changing the Reconfirmation Interval 13-30 Changing the Retry Count 13-30 Monitoring the VMPS 13-30 Troubleshooting Dynamic-Access Port VLAN Membership 13-31 VMPS Configuration Example 13-31 C H A P T E R 14 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-4 VTP Version 3 14-5 VTP Pruning 14-6 VTP and Switch Stacks 14-8 Configuring VTP 14-8

OL-13270-06 Default VTP Configuration 14-8 VTP Configuration Guidelines 14-9 Domain Names 14-9 Passwords 14-10 VTP Version 14-10 Configuration Requirements 14-11 Configuring VTP Mode 14-11 Configuring a VTP Version 3 Password 14-13 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 14-18 C H A P T E R 15 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 15-4 Configuring Cisco IP Phone Voice Traffic 15-5 Configuring the Priority of Incoming Data Frames 15-6 Displaying Voice VLAN 15-7 C H A P T E R 16 Configuring Private VLANs 16-1 Understanding Private VLANs 16-1 IP Addressing Scheme with Private VLANs 16-3 Private VLANs across Multiple Switches 16-4 Private-VLAN Interaction with Other Features 16-5 Private VLANs and Unicast, Broadcast, and Multicast Traffic 16-5 Private VLANs and SVIs 16-5 Private VLANs and Switch Stacks 16-6 Configuring Private VLANs 16-6 Tasks for Configuring Private VLANs 16-6 Default Private-VLAN Configuration 16-7 Private-VLAN Configuration Guidelines 16-7

OL-13270-06 Secondary and Primary VLAN Configuration 16-7 Private-VLAN Port Configuration 16-9 Limitations with Other Features 16-9 Configuring and Associating VLANs in a Private VLAN 16-10 Configuring a Layer 2 Interface as a Private-VLAN Host Port 16-12 Configuring a Layer 2 Interface as a Private-VLAN Promiscuous Port 16-13 Mapping Secondary VLANs to a Primary VLAN Layer 3 VLAN Interface 16-14 Monitoring Private VLANs 16-15 C H A P T E R 17 Configuring IEEE 802.1Q and Layer 2 Protocol Tunneling 17-1 Understanding IEEE 802.1Q Tunneling 17-1 Configuring IEEE 802.1Q Tunneling 17-4 Default IEEE 802.1Q Tunneling Configuration 17-4 IEEE 802.1Q Tunneling Configuration Guidelines 17-4 Native VLANs 17-4 System MTU 17-5 IEEE 802.1Q Tunneling and Other Features 17-6 Configuring an IEEE 802.1Q Tunneling Port 17-6 Understanding Layer 2 Protocol Tunneling 17-7 Configuring Layer 2 Protocol Tunneling 17-10 Default Layer 2 Protocol Tunneling Configuration 17-11 Layer 2 Protocol Tunneling Configuration Guidelines 17-12 Configuring Layer 2 Protocol Tunneling 17-13 Configuring Layer 2 Tunneling for EtherChannels 17-14 Configuring the SP Edge Switch 17-14 Configuring the Customer Switch 17-16 Monitoring and Maintaining Tunneling Status 17-18 C H A P T E R 18 Configuring STP 18-1 Understanding Spanning-Tree Features 18-1 STP Overview 18-2 Spanning-Tree Topology and BPDUs 18-3 Bridge ID, Switch Priority, and Extended System ID 18-4 Spanning-Tree Interface States 18-5 Blocking State 18-6 Listening State 18-7 Learning State 18-7 Forwarding State 18-7 Disabled State 18-7

OL-13270-06 How a Switch or Port Becomes the Root Switch or Root Port 18-8 Spanning Tree and Redundant Connectivity 18-8 Spanning-Tree Address Management 18-9 Accelerated Aging to Retain Connectivity 18-9 Spanning-Tree Modes and Protocols 18-10 Supported Spanning-Tree Instances 18-10 Spanning-Tree Interoperability and Backward Compatibility 18-11 STP and IEEE 802.1Q Trunks 18-11 VLAN-Bridge Spanning Tree 18-12 Spanning Tree and Switch Stacks 18-12 Configuring Spanning-Tree Features 18-13 Default Spanning-Tree Configuration 18-13 Spanning-Tree Configuration Guidelines 18-14 Changing the Spanning-Tree Mode. 18-15 Disabling Spanning Tree 18-16 Configuring the Root Switch 18-16 Configuring a Secondary Root Switch 18-18 Configuring Port Priority 18-18 Configuring Path Cost 18-20 Configuring the Switch Priority of a VLAN 18-21 Configuring Spanning-Tree Timers 18-22 Configuring the Hello Time 18-22 Configuring the Forwarding-Delay Time for a VLAN 18-23 Configuring the Maximum-Aging Time for a VLAN 18-23 Configuring the Transmit Hold-Count 18-24 Displaying the Spanning-Tree Status 18-24 C H A P T E R 19 Configuring MSTP 19-1 Understanding MSTP 19-2 Multiple Spanning-Tree Regions 19-2 IST, CIST, and CST 19-3 Operations Within an MST Region 19-3 Operations Between MST Regions 19-4 IEEE 802.1s Terminology 19-5 Hop Count 19-5 Boundary Ports 19-6 IEEE 802.1s Implementation 19-6 Port Role Naming Change 19-7 Interoperation Between Legacy and Standard Switches 19-7

OL-13270-06 Detecting Unidirectional Link Failure 19-8 MSTP and Switch Stacks 19-8 Interoperability with IEEE 802.1D STP 19-9 Understanding RSTP 19-9 Port Roles and the Active Topology 19-9 Rapid Convergence 19-10 Synchronization of Port Roles 19-12 Bridge Protocol Data Unit Format and Processing 19-13 Processing Superior BPDU Information 19-13 Processing Inferior BPDU Information 19-14 Topology Changes 19-14 Configuring MSTP Features 19-15 Default MSTP Configuration 19-15 MSTP Configuration Guidelines 19-16 Specifying the MST Region Configuration and Enabling MSTP 19-17 Configuring the Root Switch 19-18 Configuring a Secondary Root Switch 19-19 Configuring Port Priority 19-20 Configuring Path Cost 19-22 Configuring the Switch Priority 19-23 Configuring the Hello Time 19-23 Configuring the Forwarding-Delay Time 19-24 Configuring the Maximum-Aging Time 19-25 Configuring the Maximum-Hop Count 19-25 Specifying the Link Type to Ensure Rapid Transitions 19-26 Designating the Neighbor Type 19-26 Restarting the Protocol Migration Process 19-27 Displaying the MST Configuration and Status 19-27 C H A P T E R 20 Configuring Optional Spanning-Tree Features 20-1 Understanding Optional Spanning-Tree Features 20-1 Understanding Port Fast 20-2 Understanding BPDU Guard 20-3 Understanding BPDU Filtering 20-3 Understanding UplinkFast 20-4 Understanding Cross-Stack UplinkFast 20-5 How CSUF Works 20-6 Events that Cause Fast Convergence 20-7 Understanding BackboneFast 20-7

OL-13270-06 Understanding EtherChannel Guard 20-10 Understanding Root Guard 20-10 Understanding Loop Guard 20-11 Configuring Optional Spanning-Tree Features 20-11 Default Optional Spanning-Tree Configuration 20-12 Optional Spanning-Tree Configuration Guidelines 20-12 Enabling Port Fast 20-12 Enabling BPDU Guard 20-13 Enabling BPDU Filtering 20-14 Enabling UplinkFast for Use with Redundant Links 20-15 Enabling Cross-Stack UplinkFast 20-16 Enabling BackboneFast 20-16 Enabling EtherChannel Guard 20-17 Enabling Root Guard 20-18 Enabling Loop Guard 20-18 Displaying the Spanning-Tree Status 20-19 C H A P T E R 21 Configuring Flex Links and the MAC Address-Table Move Update Feature 21-1 Understanding Flex Links and the MAC Address-Table Move Update 21-1 Flex Links 21-2 VLAN Flex Link Load Balancing and Support 21-3 Flex Link Multicast Fast Convergence 21-3 Learning the Other Flex Link Port as the mrouter Port 21-3 Generating IGMP Reports 21-4 Leaking IGMP Reports 21-4 Configuration Examples 21-4 MAC Address-Table Move Update 21-6 Configuring Flex Links and MAC Address-Table Move Update 21-7 Configuration Guidelines 21-8 Default Configuration 21-8 Configuring Flex Links 21-9 Configuring VLAN Load Balancing on Flex Links 21-11 Configuring the MAC Address-Table Move Update Feature 21-12 Monitoring Flex Links and the MAC Address-Table Move Update Information 21-14 C H A P T E R 22 Configuring DHCP Features and IP Source Guard 22-1 Understanding DHCP Features 22-1 DHCP Server 22-2 DHCP Relay Agent 22-2

OL-13270-06 DHCP Snooping 22-2 Option-82 Data Insertion 22-3 Cisco IOS DHCP Server Database 22-6 DHCP Snooping Binding Database 22-6 DHCP Snooping and Switch Stacks 22-8 Configuring DHCP Features 22-8 Default DHCP Configuration 22-8 DHCP Snooping Configuration Guidelines 22-9 Configuring the DHCP Server 22-10 DHCP Server and Switch Stacks 22-10 Configuring the DHCP Relay Agent 22-11 Specifying the Packet Forwarding Address 22-11 Enabling DHCP Snooping and Option 82 22-12 Enabling DHCP Snooping on Private VLANs 22-14 Enabling the Cisco IOS DHCP Server Database 22-14 Enabling the DHCP Snooping Binding Database Agent 22-15 Displaying DHCP Snooping Information 22-16 Understanding IP Source Guard 22-16 Source IP Address Filtering 22-17 Source IP and MAC Address Filtering 22-17 IP Source Guard for Static Hosts 22-17 Configuring IP Source Guard 22-18 Default IP Source Guard Configuration 22-18 IP Source Guard Configuration Guidelines 22-18 Enabling IP Source Guard 22-19 Configuring IP Source Guard for Static Hosts 22-21 Configuring IP Source Guard for Static Hosts on a Layer 2 Access Port 22-21 Configuring IP Source Guard for Static Hosts on a Private VLAN Host Port 22-24 Displaying IP Source Guard Information 22-26 Understanding DHCP Server Port-Based Address Allocation 22-26 Configuring DHCP Server Port-Based Address Allocation 22-27 Default Port-Based Address Allocation Configuration 22-27 Port-Based Address Allocation Configuration Guidelines 22-27 Enabling DHCP Server Port-Based Address Allocation 22-27 Displaying DHCP Server Port-Based Address Allocation 22-30 C H A P T E R 23 Configuring Dynamic ARP Inspection 23-1 Understanding Dynamic ARP Inspection 23-1 Interface Trust States and Network Security 23-3

OL-13270-06 Rate Limiting of ARP Packets 23-4 Relative Priority of ARP ACLs and DHCP Snooping Entries 23-4 Logging of Dropped Packets 23-5 Configuring Dynamic ARP Inspection 23-5 Default Dynamic ARP Inspection Configuration 23-5 Dynamic ARP Inspection Configuration Guidelines 23-6 Configuring Dynamic ARP Inspection in DHCP Environments 23-7 Configuring ARP ACLs for Non-DHCP Environments 23-8 Limiting the Rate of Incoming ARP Packets 23-10 Performing Validation Checks 23-12 Configuring the Log Buffer 23-13 Displaying Dynamic ARP Inspection Information 23-14 C H A P T E R 24 Configuring IGMP Snooping and MVR 24-1 Understanding IGMP Snooping 24-2 IGMP Versions 24-3 Joining a Multicast Group 24-3 Leaving a Multicast Group 24-5 Immediate Leave 24-6 IGMP Configurable-Leave Timer 24-6 IGMP Report Suppression 24-6 IGMP Snooping and Switch Stacks 24-7 Configuring IGMP Snooping 24-7 Default IGMP Snooping Configuration 24-7 Enabling or Disabling IGMP Snooping 24-8 Setting the Snooping Method 24-9 Configuring a Multicast Router Port 24-10 Configuring a Blade Server Statically to Join a Group 24-11 Enabling IGMP Immediate Leave 24-11 Configuring the IGMP Leave Timer 24-12 Configuring TCN-Related Commands 24-13 Controlling the Multicast Flooding Time After a TCN Event 24-13 Recovering from Flood Mode 24-13 Disabling Multicast Flooding During a TCN Event 24-14 Configuring the IGMP Snooping Querier 24-15 Disabling IGMP Report Suppression 24-16 Displaying IGMP Snooping Information 24-17 Understanding Multicast VLAN Registration 24-18 Using MVR in a Multicast Television Application 24-19

OL-13270-06 Configuring MVR 24-20 Default MVR Configuration 24-20 MVR Configuration Guidelines and Limitations 24-21 Configuring MVR Global Parameters 24-21 Configuring MVR Interfaces 24-22 Displaying MVR Information 24-24 Configuring IGMP Filtering and Throttling 24-24 Default IGMP Filtering and Throttling Configuration 24-25 Configuring IGMP Profiles 24-25 Applying IGMP Profiles 24-27 Setting the Maximum Number of IGMP Groups 24-27 Configuring the IGMP Throttling Action 24-28 Displaying IGMP Filtering and Throttling Configuration 24-29 C H A P T E R 25 Configuring IPv6 MLD Snooping 25-1 Understanding MLD Snooping 25-1 MLD Messages 25-2 MLD Queries 25-3 Multicast Client Aging Robustness 25-3 Multicast Router Discovery 25-3 MLD Reports 25-4 MLD Done Messages and Immediate-Leave 25-4 Topology Change Notification Processing 25-5 MLD Snooping in Switch Stacks 25-5 Configuring IPv6 MLD Snooping 25-5 Default MLD Snooping Configuration 25-5 MLD Snooping Configuration Guidelines 25-6 Enabling or Disabling MLD Snooping 25-7 Configuring a Static Multicast Group 25-8 Configuring a Multicast Router Port 25-9 Enabling MLD Immediate Leave 25-9 Configuring MLD Snooping Queries 25-10 Disabling MLD Listener Message Suppression 25-11 Displaying MLD Snooping Information 25-12 C H A P T E R 26 Configuring Port-Based Traffic Control 26-1 Configuring Storm Control 26-1 Understanding Storm Control 26-2 Default Storm Control Configuration 26-3

OL-13270-06 Configuring Storm Control and Threshold Levels 26-3 Configuring Small-Frame Arrival Rate 26-5 Configuring Protected Ports 26-6 Default Protected Port Configuration 26-7 Protected Port Configuration Guidelines 26-7 Configuring a Protected Port 26-7 Configuring Port Blocking 26-8 Default Port Blocking Configuration 26-8 Blocking Flooded Traffic on an Interface 26-8 Configuring Port Security 26-9 Understanding Port Security 26-9 Secure MAC Addresses 26-9 Security Violations 26-10 Default Port Security Configuration 26-11 Port Security Configuration Guidelines 26-12 Enabling and Configuring Port Security 26-13 Enabling and Configuring Port Security Aging 26-18 Port Security and Switch Stacks 26-19 Port Security and Private VLANs 26-20 Configuring Protocol Storm Protection 26-21 Understanding Protocol Storm Protection 26-21 Default Protocol Storm Protection Configuration 26-21 Enabling Protocol Storm Protection 26-22 Displaying Port-Based Traffic Control Settings 26-23 C H A P T E R 27 Configuring CDP 27-1 Understanding CDP 27-1 CDP and Switch Stacks 27-2 Configuring CDP 27-2 Default CDP Configuration 27-2 Configuring the CDP Characteristics 27-3 Disabling and Enabling CDP 27-3 Disabling and Enabling CDP on an Interface 27-4 Monitoring and Maintaining CDP 27-5 C H A P T E R 28 Configuring LLDP, LLDP-MED, and Wired Location Service 28-1 Understanding LLDP, LLDP-MED, and Wired Location Service 28-1 LLDP 28-1

OL-13270-06 LLDP-MED 28-2 Wired Location Service 28-3 Configuring LLDP, LLDP-MED, and Wired Location Service 28-4 Default LLDP Configuration 28-4 Configuration Guidelines 28-5 Enabling LLDP 28-5 Configuring LLDP Characteristics 28-6 Configuring LLDP-MED TLVs 28-7 Configuring Network-Policy TLV 28-7 Configuring Location TLV and Wired Location Service 28-9 Monitoring and Maintaining LLDP, LLDP-MED, and Wired Location Service 28-11 C H A P T E R 29 Configuring UDLD 29-1 Understanding UDLD 29-1 Modes of Operation 29-1 Methods to Detect Unidirectional Links 29-2 Configuring UDLD 29-4 Default UDLD Configuration 29-4 Configuration Guidelines 29-4 Enabling UDLD Globally 29-5 Enabling UDLD on an Interface 29-6 Resetting an Interface Disabled by UDLD 29-6 Displaying UDLD Status 29-7 C H A P T E R 30 Configuring SPAN and RSPAN 30-1 Understanding SPAN and RSPAN 30-1 Local SPAN 30-2 Remote SPAN 30-3 SPAN and RSPAN Concepts and Terminology 30-4 SPAN Sessions 30-4 Monitored Traffic 30-5 Source Ports 30-6 Source VLANs 30-7 VLAN Filtering 30-7 Destination Port 30-8 RSPAN VLAN 30-9 SPAN and RSPAN Interaction with Other Features 30-9 SPAN and RSPAN and Switch Stacks 30-10 Understanding Flow-Based SPAN 30-10

OL-13270-06 Configuring SPAN and RSPAN 30-11 Default SPAN and RSPAN Configuration 30-12 Configuring Local SPAN 30-12 SPAN Configuration Guidelines 30-12 Creating a Local SPAN Session 30-13 Creating a Local SPAN Session and Configuring Incoming Traffic 30-15 Specifying VLANs to Filter 30-16 Configuring RSPAN 30-17 RSPAN Configuration Guidelines 30-18 Configuring a VLAN as an RSPAN VLAN 30-18 Creating an RSPAN Source Session 30-19 Specifying VLANs to Filter 30-21 Creating an RSPAN Destination Session 30-22 Creating an RSPAN Destination Session and Configuring Incoming Traffic 30-23 Configuring FSPAN and FRSPAN 30-24 Configuration Guidelines 30-24 Configuring an FSPAN Session 30-25 Configuring an FRSPAN Session 30-27 Displaying SPAN and RSPAN Status 30-29 C H A P T E R 31 Configuring RMON 31-1 Understanding RMON 31-2 Configuring RMON 31-3 Default RMON Configuration 31-3 Configuring RMON Alarms and Events 31-3 Collecting Group History Statistics on an Interface 31-5 Collecting Group Ethernet Statistics on an Interface 31-6 Displaying RMON Status 31-6 C H A P T E R 32 Configuring System Message Logging 32-1 Understanding System Message Logging 32-1 Configuring System Message Logging 32-2 System Log Message Format 32-2 Default System Message Logging Configuration 32-4 Disabling Message Logging 32-4 Setting the Message Display Destination Device 32-5 Synchronizing Log Messages 32-6 Enabling and Disabling Time Stamps on Log Messages 32-8 Enabling and Disabling Sequence Numbers in Log Messages 32-8

OL-13270-06 Defining the Message Severity Level 32-9 Limiting Syslog Messages Sent to the History Table and to SNMP 32-10 Enabling the Configuration-Change Logger 32-11 Configuring UNIX Syslog Servers 32-12 Logging Messages to a UNIX Syslog Daemon 32-13 Configuring the UNIX System Logging Facility 32-13 Displaying the Logging Configuration 32-14 C H A P T E R 33 Configuring SNMP 33-1 Understanding SNMP 33-1 SNMP Versions 33-2 SNMP Manager Functions 33-3 SNMP Agent Functions 33-4 SNMP Community Strings 33-4 Using SNMP to Access MIB Variables 33-4 SNMP Notifications 33-5 SNMP ifIndex MIB Object Values 33-5 Configuring SNMP 33-6 Default SNMP Configuration 33-6 SNMP Configuration Guidelines 33-6 Disabling the SNMP Agent 33-7 Configuring Community Strings 33-8 Configuring SNMP Groups and Users 33-9 Configuring SNMP Notifications 33-12 Setting the CPU Threshold Notification Types and Values 33-16 Setting the Agent Contact and Location Information 33-16 Limiting TFTP Servers Used Through SNMP 33-17 SNMP Examples 33-18 Displaying SNMP Status 33-19 C H A P T E R 34 Configuring Embedded Event Manager 34-1 Understanding Embedded Event Manager 34-1 Event Detectors 34-3 Embedded Event Manager Actions 34-4 Embedded Event Manager Policies 34-4 Embedded Event Manager Environment Variables 34-5 EEM 3.2 34-5 Configuring Embedded Event Manager 34-6 Registering and Defining an Embedded Event Manager Applet 34-6

OL-13270-06 Registering and Defining an Embedded Event Manager TCL Script 34-7 Displaying Embedded Event Manager Information 34-8 C H A P T E R 35 Configuring Network Security with ACLs 35-1 Understanding ACLs 35-2 Supported ACLs 35-2 Port ACLs 35-3 Router ACLs 35-4 VLAN Maps 35-5 Handling Fragmented and Unfragmented Traffic 35-6 ACLs and Switch Stacks 35-7 Configuring IPv4 ACLs 35-7 Creating Standard and Extended IPv4 ACLs 35-8 Access List Numbers 35-8 ACL Logging 35-9 Creating a Numbered Standard ACL 35-10 Creating a Numbered Extended ACL 35-11 Resequencing ACEs in an ACL 35-15 Creating Named Standard and Extended ACLs 35-15 Using Time Ranges with ACLs 35-17 Including Comments in ACLs 35-19 Applying an IPv4 ACL to a Terminal Line 35-19 Applying an IPv4 ACL to an Interface 35-20 Hardware and Software Treatment of IP ACLs 35-22 Troubleshooting ACLs 35-22 IPv4 ACL Configuration Examples 35-23 Numbered ACLs 35-25 Extended ACLs 35-25 Named ACLs 35-26 Time Range Applied to an IP ACL 35-26 Commented IP ACL Entries 35-27 ACL Logging 35-27 Creating Named MAC Extended ACLs 35-28 Applying a MAC ACL to a Layer 2 Interface 35-29 Configuring VLAN Maps 35-30 VLAN Map Configuration Guidelines 35-31 Creating a VLAN Map 35-32 Examples of ACLs and VLAN Maps 35-33 Applying a VLAN Map to a VLAN 35-35

OL-13270-06 Using VLAN Maps in Your Network 35-35 Denying Access to a Server on Another VLAN 35-35 Configuring VACL Logging 35-36 Using VLAN Maps with Router ACLs 35-38 VLAN Maps and Router ACL Configuration Guidelines 35-39 Examples of Router ACLs and VLAN Maps Applied to VLANs 35-39 ACLs and Switched Packets 35-39 ACLs and Bridged Packets 35-40 ACLs and Routed Packets 35-41 ACLs and Multicast Packets 35-41 Displaying IPv4 ACL Configuration 35-42 C H A P T E R 36 Configuring IPv6 ACLs 36-1 Understanding IPv6 ACLs 36-1 Supported ACL Features 36-2 IPv6 ACL Limitations 36-2 IPv6 ACLs and Switch Stacks 36-3 Configuring IPv6 ACLs 36-3 Default IPv6 ACL Configuration 36-4 Interaction with Other Features and Switches 36-4 Creating IPv6 ACLs 36-4 Applying an IPv6 ACL to an Interface 36-8 Displaying IPv6 ACLs 36-9 C H A P T E R 37 Configuring QoS 37-1 Understanding QoS 37-2 Basic QoS Model 37-4 Classification 37-5 Classification Based on QoS ACLs 37-8 Classification Based on Class Maps and Policy Maps 37-8 Policing and Marking 37-9 Policing on Physical Ports 37-10 Policing on SVIs 37-11 Mapping Tables 37-13 Queueing and Scheduling Overview 37-14 Weighted Tail Drop 37-14 SRR Shaping and Sharing 37-15 Queueing and Scheduling on Ingress Queues 37-16 Queueing and Scheduling on Egress Queues 37-18

OL-13270-06 Packet Modification 37-20 Configuring Auto-QoS 37-21 Generated Auto-QoS Configuration 37-22 VOIP Device Specifics 37-22 Enhanced Auto-QoS for Video, Trust, and Classification 37-24 Auto-QoS Configuration Migration 37-24 Global Auto-QoS Configuration 37-25 Auto-QoS Generated Configuration For VoIP Devices 37-28 Auto-QoS Generated Configuration For Enhanced Video, Trust, and Classify Devices 37-29 Effects of Auto-QoS on the Configuration 37-32 Auto-QoS Configuration Guidelines 37-32 Auto-QoS VoIP Considerations 37-33 Auto-QoS Enhanced Considerations 37-33 Enabling Auto-QoS 37-33 Troubleshooting Auto QoS Commands 37-34 Displaying Auto-QoS Information 37-35 Configuring Standard QoS 37-35 Default Standard QoS Configuration 37-36 Default Ingress Queue Configuration 37-36 Default Egress Queue Configuration 37-37 Default Mapping Table Configuration 37-38 Standard QoS Configuration Guidelines 37-38 QoS ACL Guidelines 37-38 IPv6 QoS ACL Guidelines 37-38 Applying QoS on Interfaces 37-39 Configuring IPv6 QoS on Switch Stacks 37-39 Policing Guidelines 37-40 General QoS Guidelines 37-40 Enabling QoS Globally 37-41 Enabling VLAN-Based QoS on Physical Ports 37-41 Configuring Classification Using Port Trust States 37-42 Configuring the Trust State on Ports within the QoS Domain 37-42 Configuring the CoS Value for an Interface 37-43 Configuring a Trusted Boundary to Ensure Port Security 37-44 Enabling DSCP Transparency Mode 37-46 Configuring the DSCP Trust State on a Port Bordering Another QoS Domain 37-46 Configuring a QoS Policy 37-48 Classifying Traffic by Using ACLs 37-49 Classifying Traffic by Using Class Maps 37-54

OL-13270-06 Classifying Traffic by Using Class Maps and Filtering IPv6 Traffic 37-57 Classifying, Policing, and Marking Traffic on Physical Ports by Using Policy Maps 37-59 Classifying, Policing, and Marking Traffic on SVIs by Using Hierarchical Policy Maps 37-64 Classifying, Policing, and Marking Traffic by Using Aggregate Policers 37-72 Configuring DSCP Maps 37-75 Configuring the CoS-to-DSCP Map 37-75 Configuring the IP-Precedence-to-DSCP Map 37-76 Configuring the Policed-DSCP Map 37-77 Configuring the DSCP-to-CoS Map 37-78 Configuring the DSCP-to-DSCP-Mutation Map 37-79 Configuring Ingress Queue Characteristics 37-81 Mapping DSCP or CoS Values to an Ingress Queue and Setting WTD Thresholds 37-82 Allocating Buffer Space Between the Ingress Queues 37-83 Allocating Bandwidth Between the Ingress Queues 37-83 Configuring the Ingress Priority Queue 37-84 Configuring Egress Queue Characteristics 37-85 Configuration Guidelines 37-86 Allocating Buffer Space to and Setting WTD Thresholds for an Egress Queue-Set 37-86 Mapping DSCP or CoS Values to an Egress Queue and to a Threshold ID 37-88 Configuring SRR Shaped Weights on Egress Queues 37-90 Configuring SRR Shared Weights on Egress Queues 37-91 Configuring the Egress Expedite Queue 37-92 Limiting the Bandwidth on an Egress Interface 37-92 Displaying Standard QoS Information 37-93 C H A P T E R 38 Configuring EtherChannels and Link-State Tracking 38-1 Understanding EtherChannels 38-1 EtherChannel Overview 38-2 Port-Channel Interfaces 38-4 Port Aggregation Protocol 38-5 PAgP Modes 38-5 PAgP Interaction with Virtual Switches and Dual-Active Detection 38-6 PAgP Interaction with Other Features 38-6 Link Aggregation Control Protocol 38-6 LACP Modes 38-7 LACP Interaction with Other Features 38-7 EtherChannel On Mode 38-7 Load-Balancing and Forwarding Methods 38-8 EtherChannel and Switch Stacks 38-9

OL-13270-06 Configuring EtherChannels 38-10 Default EtherChannel Configuration 38-10 EtherChannel Configuration Guidelines 38-11 Configuring Layer 2 EtherChannels 38-12 Configuring Layer 3 EtherChannels 38-15 Creating Port-Channel Logical Interfaces 38-15 Configuring the Physical Interfaces 38-16 Configuring EtherChannel Load-Balancing 38-18 Configuring the PAgP Learn Method and Priority 38-19 Configuring LACP Hot-Standby Ports 38-20 Configuring the LACP System Priority 38-21 Configuring the LACP Port Priority 38-22 Displaying EtherChannel, PAgP, and LACP Status 38-23 Understanding Link-State Tracking 38-23 Configuring Link-State Tracking 38-25 Default Link-State Tracking Configuration 38-25 Link-State Tracking Configuration Guidelines 38-25 Configuring Link-State Tracking 38-26 Displaying Link-State Tracking Status 38-27 C H A P T E R 39 Configuring IP Unicast Routing 39-1 Understanding IP Routing 39-2 Types of Routing 39-2 IP Routing and Switch Stacks 39-3 Steps for Configuring Routing 39-5 Configuring IP Addressing 39-5 Default Addressing Configuration 39-6 Assigning IP Addresses to Network Interfaces 39-7 Use of Subnet Zero 39-7 Classless Routing 39-8 Configuring Address Resolution Methods 39-9 Define a Static ARP Cache 39-10 Set ARP Encapsulation 39-11 Enable Proxy ARP 39-12 Routing Assistance When IP Routing is Disabled 39-12 Proxy ARP 39-12 Default Gateway 39-12 ICMP Router Discovery Protocol (IRDP) 39-13 Configuring Broadcast Packet Handling 39-14

OL-13270-06 Enabling Directed Broadcast-to-Physical Broadcast Translation 39-15 Forwarding UDP Broadcast Packets and Protocols 39-16 Establishing an IP Broadcast Address 39-16 Flooding IP Broadcasts 39-17 Monitoring and Maintaining IP Addressing 39-18 Enabling IP Unicast Routing 39-19 Configuring RIP 39-20 Default RIP Configuration 39-21 Configuring Basic RIP Parameters 39-22 Configuring RIP Authentication 39-23 Configuring Summary Addresses and Split Horizon 39-24 Configuring Split Horizon 39-25 Configuring OSPF 39-25 Default OSPF Configuration 39-28 OSPF for Routed Access 39-30 OSPF Nonstop Forwarding 39-30 Configuring Basic OSPF Parameters 39-31 Configuring OSPF Interfaces 39-32 Configuring OSPF Area Parameters 39-33 Configuring Other OSPF Parameters 39-35 Changing LSA Group Pacing 39-36 Configuring a Loopback Interface 39-37 Monitoring OSPF 39-38 Configuring EIGRP 39-38 Default EIGRP Configuration 39-40 EIGRP Nonstop Forwarding 39-42 Configuring Basic EIGRP Parameters 39-43 Configuring EIGRP Interfaces 39-44 Configuring EIGRP Route Authentication 39-45 EIGRP Stub Routing 39-46 Monitoring and Maintaining EIGRP 39-46 Configuring BGP 39-47 Default BGP Configuration 39-49 Nonstop Forwarding Awareness 39-52 Enabling BGP Routing 39-52 Managing Routing Policy Changes 39-55 Configuring BGP Decision Attributes 39-56 Configuring BGP Filtering with Route Maps 39-58 Configuring BGP Filtering by Neighbor 39-59

OL-13270-06 Configuring Prefix Lists for BGP Filtering 39-60 Configuring BGP Community Filtering 39-61 Configuring BGP Neighbors and Peer Groups 39-63 Configuring Aggregate Addresses 39-65 Configuring Routing Domain Confederations 39-65 Configuring BGP Route Reflectors 39-66 Configuring Route Dampening 39-67 Monitoring and Maintaining BGP 39-68 Configuring ISO CLNS Routing 39-69 Configuring IS-IS Dynamic Routing 39-70 Default IS-IS Configuration 39-71 Nonstop Forwarding Awareness 39-72 Enabling IS-IS Routing 39-72 Configuring IS-IS Global Parameters 39-74 Configuring IS-IS Interface Parameters 39-76 Monitoring and Maintaining ISO IGRP and IS-IS 39-79 Configuring Multi-VRF CE 39-80 Understanding Multi-VRF CE 39-80 Default Multi-VRF CE Configuration 39-82 Multi-VRF CE Configuration Guidelines 39-82 Configuring VRFs 39-83 Configuring VRF-Aware Services 39-84 User Interface for ARP 39-85 User Interface for PING 39-85 User Interface for SNMP 39-85 User Interface for HSRP 39-86 User Interface for Unicast RPF 39-86 User Interface for Syslog 39-87 User Interface for Traceroute 39-87 User Interface for FTP and TFTP 39-87 User Interface for VRF-Aware RADIUS 39-88 Configuring Multicast VRFs 39-88 Configuring a VPN Routing Session 39-89 Configuring BGP PE to CE Routing Sessions 39-90 Multi-VRF CE Configuration Example 39-90 Displaying Multi-VRF CE Status 39-94 Configuring Unicast Reverse Path Forwarding 39-95 Configuring Protocol-Independent Features 39-95 Configuring Cisco Express Forwarding and Distributed Cisco Express Forwarding 39-95

OL-13270-06 Configuring the Number of Equal-Cost Routing Paths 39-97 Configuring Static Unicast Routes 39-97 Specifying Default Routes and Networks 39-98 Using Route Maps to Redistribute Routing Information 39-99 Configuring Policy-Based Routing 39-103 PBR Configuration Guidelines 39-103 Enabling PBR 39-105 Filtering Routing Information 39-106 Setting Passive Interfaces 39-106 Controlling Advertising and Processing in Routing Updates 39-107 Filtering Sources of Routing Information 39-108 Managing Authentication Keys 39-109 Monitoring and Maintaining the IP Network 39-111 C H A P T E R 40 Configuring IPv6 Unicast Routing 40-1 Understanding IPv6 40-1 IPv6 Addresses 40-2 Supported IPv6 Unicast Routing Features 40-3 128-Bit Wide Unicast Addresses 40-4 DNS for IPv6 40-4 Path MTU Discovery for IPv6 Unicast 40-4 ICMPv6 40-4 Neighbor Discovery 40-4 Default Router Preference 40-5 IPv6 Stateless Autoconfiguration and Duplicate Address Detection 40-5 IPv6 Applications 40-5 Dual IPv4 and IPv6 Protocol Stacks 40-6 DHCP for IPv6 Address Assignment 40-6 Static Routes for IPv6 40-7 RIP for IPv6 40-7 OSPF for IPv6 40-7 EIGRP for IPv6 40-7 HSRP for IPv6 40-8 SNMP and Syslog Over IPv6 40-8 HTTP(S) Over IPv6 40-8 Unsupported IPv6 and Unicast Routing Features 40-9 Limitations 40-9 IPv6 and Switch Stacks 40-10 Configuring IPv6 40-11

OL-13270-06 Default IPv6 Configuration 40-11 Configuring IPv6 Addressing and Enabling IPv6 Host Functions or Routing 40-12 Configuring Default Router Preference 40-14 Configuring IPv4 and IPv6 Protocol Stacks 40-15 Configuring DHCP for IPv6 Address Assignment 40-16 Default DHCPv6 Address Assignment Configuration 40-16 DHCPv6 Address Assignment Configuration Guidelines 40-16 Enabling DHCPv6 Server Function 40-17 Enabling DHCPv6 Client Function 40-19 Configuring IPv6 ICMP Rate Limiting 40-20 Configuring CEF and dCEF for IPv6 40-20 Configuring Static Routes for IPv6 40-21 Configuring RIP for IPv6 40-22 Configuring OSPF for IPv6 40-23 Configuring EIGRP for IPv6 40-25 Configuring HSRP for IPv6 40-25 Enabling HSRP Version 2 40-26 Enabling an HSRP Group for IPv6 40-26 Displaying IPv6 40-28 C H A P T E R 41 Configuring HSRP and VRRP 41-1 Understanding HSRP 41-1 HSRP Versions 41-3 Multiple HSRP 41-4 HSRP and Switch Stacks 41-5 Configuring HSRP 41-5 Default HSRP Configuration 41-6 HSRP Configuration Guidelines 41-6 Enabling HSRP 41-7 Configuring HSRP Priority 41-8 Configuring MHSRP 41-10 Configuring HSRP Authentication and Timers 41-11 Enabling HSRP Support for ICMP Redirect Messages 41-12 Displaying HSRP Configurations 41-12 Configuring VRRP 41-13 VRRP Limitations 41-13 C H A P T E R 42 Configuring Cisco IOS IP SLAs Operations 42-1 Understanding Cisco IOS IP SLAs 42-1

OL-13270-06 Using Cisco IOS IP SLAs to Measure Network Performance 42-3 IP SLAs Responder and IP SLAs Control Protocol 42-4 Response Time Computation for IP SLAs 42-4 IP SLAs Operation Scheduling 42-5 IP SLAs Operation Threshold Monitoring 42-5 Configuring IP SLAs Operations 42-6 Default Configuration 42-6 Configuration Guidelines 42-6 Configuring the IP SLAs Responder 42-7 Analyzing IP Service Levels by Using the UDP Jitter Operation 42-8 Analyzing IP Service Levels by Using the ICMP Echo Operation 42-11 Monitoring IP SLAs Operations 42-13 C H A P T E R 43 Configuring Enhanced Object Tracking 43-1 Understanding Enhanced Object Tracking 43-1 Configuring Enhanced Object Tracking Features 43-2 Default Configuration 43-2 Tracking Interface Line-Protocol or IP Routing State 43-2 Configuring a Tracked List 43-3 Configuring a Tracked List with a Boolean Expression 43-3 Configuring a Tracked List with a Weight Threshold 43-4 Configuring a Tracked List with a Percentage Threshold 43-5 Configuring HSRP Object Tracking 43-7 Configuring Other Tracking Characteristics 43-8 Configuring IP SLAs Object Tracking 43-8 Monitoring Enhanced Object Tracking 43-10 C H A P T E R 44 Configuring Cache Services By Using WCCP 44-1 Understanding WCCP 44-2 WCCP Message Exchange 44-3 WCCP Negotiation 44-3 MD5 Security 44-4 Packet Redirection and Service Groups 44-4 WCCP and Switch Stacks 44-5 Unsupported WCCP Features 44-5 Configuring WCCP 44-5 Default WCCP Configuration 44-6 WCCP Configuration Guidelines 44-6 Enabling the Cache Service 44-7

OL-13270-06 Monitoring and Maintaining WCCP 44-11 C H A P T E R 45 Configuring IP Multicast Routing 45-1 Understanding Cisco’s Implementation of IP Multicast Routing 45-2 Understanding IGMP 45-3 IGMP Version 1 45-3 IGMP Version 2 45-3 Understanding PIM 45-4 PIM Versions 45-4 PIM Modes 45-4 PIM Stub Routing 45-5 IGMP Helper 45-6 Auto-RP 45-7 Bootstrap Router 45-7 Multicast Forwarding and Reverse Path Check 45-8 Understanding DVMRP 45-9 Understanding CGMP 45-9 Multicast Routing and Switch Stacks 45-10 Configuring IP Multicast Routing 45-11 Default Multicast Routing Configuration 45-11 Multicast Routing Configuration Guidelines 45-11 PIMv1 and PIMv2 Interoperability 45-12 Auto-RP and BSR Configuration Guidelines 45-12 Configuring Basic Multicast Routing 45-13 Configuring Source-Specific Multicast 45-15 SSM Components Overview 45-15 How SSM Differs from Internet Standard Multicast 45-15 SSM IP Address Range 45-16 SSM Operations 45-16 IGMPv3 Host Signalling 45-16 Configuration Guidelines 45-17 Configuring SSM 45-18 Monitoring SSM 45-18 Configuring Source Specific Multicast Mapping 45-18 Configuration Guidelines 45-19 SSM Mapping Overview 45-19 Configuring SSM Mapping 45-21 Monitoring SSM Mapping 45-23 Configuring Source-Specific Multicast 45-23

OL-13270-06 SSM Components Overview 45-23 How SSM Differs from Internet Standard Multicast 45-24 SSM IP Address Range 45-24 SSM Operations 45-24 IGMPv3 Host Signalling 45-25 Configuration Guidelines 45-25 Configuring SSM 45-26 Monitoring SSM 45-26 Enabling PIM Stub Routing 45-27 Configuring a Rendezvous Point 45-28 Manually Assigning an RP to Multicast Groups 45-28 Configuring Auto-RP 45-30 Configuring PIMv2 BSR 45-34 Using Auto-RP and a BSR 45-38 Monitoring the RP Mapping Information 45-39 Troubleshooting PIMv1 and PIMv2 Interoperability Problems 45-39 Configuring Advanced PIM Features 45-39 Understanding PIM Shared Tree and Source Tree 45-39 Delaying the Use of PIM Shortest-Path Tree 45-41 Modifying the PIM Router-Query Message Interval 45-42 Configuring Optional IGMP Features 45-43 Default IGMP Configuration 45-43 Configuring the Switch as a Member of a Group 45-43 Controlling Access to IP Multicast Groups 45-44 Changing the IGMP Version 45-45 Modifying the IGMP Host-Query Message Interval 45-46 Changing the IGMP Query Timeout for IGMPv2 45-47 Changing the Maximum Query Response Time for IGMPv2 45-47 Configuring the Switch as a Statically Connected Member 45-48 Configuring Optional Multicast Routing Features 45-48 Enabling CGMP Server Support 45-49 Configuring sdr Listener Support 45-50 Enabling sdr Listener Support 45-50 Limiting How Long an sdr Cache Entry Exists 45-50 Configuring an IP Multicast Boundary 45-51 Configuring Basic DVMRP Interoperability Features 45-53 Configuring DVMRP Interoperability 45-53 Configuring a DVMRP Tunnel 45-55 Advertising Network 0.0.0.0 to DVMRP Neighbors 45-57

OL-13270-06 Responding to mrinfo Requests 45-58 Configuring Advanced DVMRP Interoperability Features 45-58 Enabling DVMRP Unicast Routing 45-59 Rejecting a DVMRP Nonpruning Neighbor 45-60 Controlling Route Exchanges 45-62 Limiting the Number of DVMRP Routes Advertised 45-62 Changing the DVMRP Route Threshold 45-62 Configuring a DVMRP Summary Address 45-63 Disabling DVMRP Autosummarization 45-65 Adding a Metric Offset to the DVMRP Route 45-65 Monitoring and Maintaining IP Multicast Routing 45-66 Clearing Caches, Tables, and Databases 45-66 Displaying System and Network Statistics 45-67 Monitoring IP Multicast Routing 45-68 C H A P T E R 46 Configuring MSDP 46-1 Understanding MSDP 46-1 MSDP Operation 46-2 MSDP Benefits 46-3 Configuring MSDP 46-4 Default MSDP Configuration 46-4 Configuring a Default MSDP Peer 46-4 Caching Source-Active State 46-6 Requesting Source Information from an MSDP Peer 46-8 Controlling Source Information that Your Switch Originates 46-8 Redistributing Sources 46-9 Filtering Source-Active Request Messages 46-10 Controlling Source Information that Your Switch Forwards 46-12 Using a Filter 46-12 Using TTL to Limit the Multicast Data Sent in SA Messages 46-13 Controlling Source Information that Your Switch Receives 46-15 Configuring an MSDP Mesh Group 46-16 Shutting Down an MSDP Peer 46-17 Including a Bordering PIM Dense-Mode Region in MSDP 46-17 Configuring an Originating Address other than the RP Address 46-18 Monitoring and Maintaining MSDP 46-19 C H A P T E R 47 Configuring Fallback Bridging 47-1 Understanding Fallback Bridging 47-1

OL-13270-06 Fallback Bridging Overview 47-1 Fallback Bridging and Switch Stacks 47-3 Configuring Fallback Bridging 47-3 Default Fallback Bridging Configuration 47-4 Fallback Bridging Configuration Guidelines 47-4 Creating a Bridge Group 47-4 Adjusting Spanning-Tree Parameters 47-6 Changing the VLAN-Bridge Spanning-Tree Priority 47-6 Changing the Interface Priority 47-7 Assigning a Path Cost 47-8 Adjusting BPDU Intervals 47-8 Disabling the Spanning Tree on an Interface 47-10 Monitoring and Maintaining Fallback Bridging 47-11 C H A P T E R 48 Troubleshooting 48-1 Recovering from a Software Failure 48-2 Recovering from a Lost or Forgotten Password 48-3 Procedure with Password Recovery Enabled 48-5 Procedure with Password Recovery Disabled 48-7 Preventing Switch Stack Problems 48-8 Preventing Autonegotiation Mismatches 48-9 SFP Module Security and Identification 48-9 Monitoring SFP Module Status 48-10 Monitoring Temperature 48-10 Using Ping 48-10 Understanding Ping 48-11 Executing Ping 48-11 Using Layer 2 Traceroute 48-12 Understanding Layer 2 Traceroute 48-12 Usage Guidelines 48-12 Displaying the Physical Path 48-13 Using IP Traceroute 48-13 Understanding IP Traceroute 48-14 Executing IP Traceroute 48-14 Using TDR 48-15 Understanding TDR 48-15 Running TDR and Displaying the Results 48-16 Using Debug Commands 48-16

OL-13270-06 Enabling Debugging on a Specific Feature 48-17 Enabling All-System Diagnostics 48-17 Redirecting Debug and Error Message Output 48-17 Using the show platform forward Command 48-19 Using the crashinfo Files 48-21 Basic crashinfo Files 48-21 Extended crashinfo Files 48-21 Using Memory Consistency Check Routines 48-22 Using On-Board Failure Logging 48-23 Understanding OBFL 48-23 Configuring OBFL 48-23 Displaying OBFL Information 48-24 Troubleshooting CPU Utilization 48-25 Possible Symptoms of High CPU Utilization 48-25 Verifying the Problem and Cause 48-25 C H A P T E R 49 Configuring Online Diagnostics 49-1 Understanding Online Diagnostics 49-1 Configuring Online Diagnostics 49-2 Scheduling Online Diagnostics 49-2 Configuring Health-Monitoring Diagnostics 49-3 Running Online Diagnostic Tests 49-5 Starting Online Diagnostic Tests 49-5 Displaying Online Diagnostic Tests and Test Results 49-6 A P P E N D I X A Working with the Cisco IOS File System, Configuration Files, and Software Images A-1 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 A-4 Creating and Removing Directories A-5 Copying Files A-5 Deleting Files A-6 Creating, Displaying, and Extracting Files A-6 Working with Configuration Files A-9 Guidelines for Creating and Using Configuration Files A-10 Configuration File Types and Location A-11

OL-13270-06 Creating a Configuration File By Using a Text Editor A-11 Copying Configuration Files By Using TFTP A-11 Preparing to Download or Upload a Configuration File By Using TFTP A-12 Downloading the Configuration File By Using TFTP A-12 Uploading the Configuration File By Using TFTP A-13 Copying Configuration Files By Using FTP A-14 Preparing to Download or Upload a Configuration File By Using FTP A-14 Downloading a Configuration File By Using FTP A-15 Uploading a Configuration File By Using FTP A-16 Copying Configuration Files By Using RCP A-17 Preparing to Download or Upload a Configuration File By Using RCP A-18 Downloading a Configuration File By Using RCP A-18 Uploading a Configuration File By Using RCP A-19 Clearing Configuration Information A-20 Clearing the Startup Configuration File A-20 Deleting a Stored Configuration File A-21 Replacing and Rolling Back Configurations A-21 Understanding Configuration Replacement and Rollback A-21 Configuration Guidelines A-22 Configuring the Configuration Archive A-23 Performing a Configuration Replacement or Rollback Operation A-24 Working with Software Images A-25 Image Location on the Switch A-26 File Format of Images on a Server or Cisco.com A-26 Copying Image Files By Using TFTP A-27 Preparing to Download or Upload an Image File By Using TFTP A-28 Downloading an Image File By Using TFTP A-28 Uploading an Image File By Using TFTP A-30 Copying Image Files By Using FTP A-31 Preparing to Download or Upload an Image File By Using FTP A-31 Downloading an Image File By Using FTP A-32 Uploading an Image File By Using FTP A-34 Copying Image Files By Using RCP A-35 Preparing to Download or Upload an Image File By Using RCP A-36 Downloading an Image File By Using RCP A-37 Uploading an Image File By Using RCP A-39 Copying an Image File from One Stack Member to Another A-40

OL-13270-06 A P P E N D I X B Unsupported Commands in Cisco IOS Release 12.2(58)SE B-1 Access Control Lists B-1 Unsupported Privileged EXEC Commands B-1 Unsupported Global Configuration Commands B-1 Unsupported Route-Map Configuration Commands B-1 Archive Commands B-2 Unsupported Privileged EXEC Commands B-2 ARP Commands B-2 Unsupported Global Configuration Commands B-2 Unsupported Interface Configuration Commands B-2 Boot Loader Commands B-2 Unsupported User EXEC Commands B-2 Unsupported Global Configuration Commands B-2 Debug Commands B-3 Unsupported Privileged EXEC Commands B-3 Embedded Event Manager B-3 Unsupported Privileged EXEC Commands B-3 Unsupported Global Configuration Commands B-3 Unsupported Commands in Applet Configuration Mode B-3 Fallback Bridging B-4 Unsupported Privileged EXEC Commands B-4 Unsupported Global Configuration Commands B-4 Unsupported Interface Configuration Commands B-4 HSRP B-5 Unsupported Global Configuration Commands B-5 Unsupported Interface Configuration Commands B-6 IGMP Snooping Commands B-6 Unsupported Global Configuration Commands B-6 Interface Commands B-6 Unsupported Privileged EXEC Commands B-6 Unsupported Global Configuration Commands B-6 Unsupported Interface Configuration Commands B-6 IP Multicast Routing B-7 Unsupported Privileged EXEC Commands B-7 Unsupported Global Configuration Commands B-7 Unsupported Interface Configuration Commands B-8 IP Unicast Routing B-9 Unsupported Privileged EXEC or User EXEC Commands B-9

OL-13270-06 Unsupported Global Configuration Commands B-9 Unsupported Interface Configuration Commands B-10 Unsupported BGP Router Configuration Commands B-10 Unsupported VPN Configuration Commands B-10 Unsupported Route Map Commands B-10 MAC Address Commands B-11 Unsupported Privileged EXEC Commands B-11 Unsupported Global Configuration Commands B-11 Miscellaneous B-11 Unsupported User EXEC Commands B-11 Unsupported Privileged EXEC Commands B-12 Unsupported Global Configuration Commands B-12 MSDP B-12 Unsupported Privileged EXEC Commands B-12 Unsupported Global Configuration Commands B-12 NetFlow Commands B-12 Unsupported Global Configuration Commands B-12 Network Address Translation (NAT) Commands B-13 Unsupported Privileged EXEC Commands B-13 QoS B-13 Unsupported Global Configuration Command B-13 Unsupported Interface Configuration Commands B-13 Unsupported Policy-Map Configuration Command B-13 RADIUS B-13 Unsupported Global Configuration Commands B-13 SNMP B-14 Unsupported Global Configuration Commands B-14 Spanning Tree B-14 Unsupported Global Configuration Command B-14 Unsupported Interface Configuration Command B-14 VLAN B-14 Unsupported Global Configuration Command B-14 Unsupported User EXEC Commands B-14 Unsupported VLAN Database commands B-14 VTP B-15 Unsupported Privileged EXEC Command B-15 I N D E X

OL-13270-06

OL-13270-06 Preface Audience This guide is for the networking professional using the Cisco IOS command-line interface (CLI) to manage the standalone Cisco Catalyst Blade Switch 3130 for Dell or blade switch stack, referred to as the switch. Before using this guide, you should have experience working with the Cisco IOS commands and the switch software features. Before using this guide, you should have experience working with the concepts and terminology of Ethernet and local area networking. You install the switch in the Dell M1000e blade server chassis, referred to as the enclosure. Purpose This guide provides procedures for using the commands that have been created or changed for use with the switches. It does not provide detailed information about these commands. For detailed information about these commands, see the command reference for this release. For information about the standard Cisco IOS Release 12.2 commands, see the Cisco IOS documentation set available from the Cisco.com home page at Products & Services > Technical Support & Documentation > See Documentation > Cisco IOS Software. This guide does not provide detailed information on the GUIs for the embedded device manager or for Cisco Network Assistant (hereafter referred to as Network Assistant) that you can use to manage the switch. However, the concepts in this guide are applicable to the GUI user. For information about the device manager, see the switch online help. For information about Network Assistant, see Getting Started with Cisco Network Assistant, available on Cisco.com. This guide does not describe system messages you might encounter or how to install your switch. For more information, see the system message guide for this release and the hardware installation guide. For documentation updates, see the release notes for this release. Conventions This publication uses these conventions to convey instructions and information: Command descriptions use these conventions: • Commands and keywords are in boldface text. • Arguments for which you supply values are in italic.

OL-13270-06 Preface • Square brackets ([ ]) mean optional elements. • Braces ({ }) group required choices, and vertical bars ( | ) separate the alternative elements. • Braces and vertical bars within square brackets ([{ | }]) mean a required choice within an optional element. Interactive examples use these conventions: • Terminal sessions and system displays are in screen font. • Information you enter is in boldface screen font. • Nonprinting characters, such as passwords or tabs, are in angle brackets (< >). Notes, cautions, and timesavers use these conventions and symbols: Note Means reader take note. Notes contain helpful suggestions or references to materials not contained in this manual. Caution Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data. Related Publications These documents provide complete information about the switch and are available from this Cisco.com site: http://www.cisco.com/en/US/products/ps8742/tsd_products_support_series_home.html Note Before installing, configuring, or upgrading the switch, see these documents: • For initial configuration information, see the “Using Express Setup” section in the getting started guide or the “Configuring the Switch with the CLI-Based Setup Program” appendix in the hardware installation guide. • For device manager requirements, see the “System Requirements” section in the release notes (not orderable but available on Cisco.com). • For Network Assistant requirements, see the Getting Started with Cisco Network Assistant (not orderable but available on Cisco.com). • For upgrading information, see the “Downloading Software” section in the release notes. • Release Notes for the Cisco Catalyst Blade Switch 3130 for Dell • Cisco Catalyst Blade Switch 3130 for Dell Software Configuration Guide • Cisco Catalyst Blade Switch 3130 for Dell Command Reference • Cisco Catalyst Blade Switch3130 for Dell System Message Guide • Cisco Software Activation Document for Dell • Device manager online help (available on the switch)

OL-13270-06 Preface • Cisco Catalyst Blade Switch 3130 for Dell and Cisco Catalyst Blade Switch 3032 for Dell Hardware Installation Guide • Cisco Catalyst Blade Switch 3130 for Dell and Cisco Catalyst Blade Switch 3032 for Dell Getting Started Guide • Regulatory Compliance and Safety Information for the Cisco Catalyst Blade Switch 3000 Series for Dell • Device manager online help (available on the switch) • Getting Started with Cisco Network Assistant • Release Notes for Cisco Network Assistant • Installation Note for the Cisco TwinGig Converter Module • Cisco Small Form-Factor Pluggable Modules Installation Notes • Cisco CWDM GBIC and CWDM SFP Installation Note • These compatibility matrix documents are available from this Cisco.com site: http://www.cisco.com/en/US/products/hw/modules/ps5455/products_device_support_tables_list. html – Cisco Gigabit Ethernet Transceiver Modules Compatibility Matrix – Cisco 100-Megabit Ethernet SFP Modules Compatibility Matrix – Cisco Small Form-Factor Pluggable Modules Compatibility Matrix – Compatibility Matrix for 1000BASE-T Small Form-Factor Pluggable Modules • For information about the Network Admission Control (NAC) features, see the Network Admission Control Software Configuration Guide Obtaining Documentation and Submitting a Service Request For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html 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. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.

OL-13270-06 Preface

1-1 Cisco Catalyst Blade Switch 3130 and 3032 for Dell Software Configuration Guide OL-13270-06 1 Overview This chapter provides these topics about the switch software: • Features, page 1-1 • Default Settings After Initial Switch Configuration, page 1-16 • Network Configuration Examples, page 1-20 • Where to Go Next, page 1-24 The term switch refers to a standalone switch and to a switch stack. In this document, IP refers to IP Version 4 (IPv4) unless there is a specific reference to IP Version 6 (IPv6). Note The examples in this document are for a stacking-capable switch. When you specify an interface in a command-line interface (CLI) command, the interface is on the stacking-capable switch, for example, gigabitethernet 1/0/5. The examples also apply to the nonstacking-capable switch. In the previous example, the specified interface on a nonstacking-capable switch is gigabitethernet0/5 (without the stack member number of 1/). Features The switch supports either the cryptographic (supports encryption) or the noncryptographic universal software image. The cryptographic and noncryptographic universal software images support the IP base and IP services feature sets. To enable a specific feature set, you must have a Cisco IOS software license for that feature set. For more information about the software license, see the Cisco Software Activation for Dell document on Cisco.com. Some features described in this chapter are only available on the cryptographic software image. You must obtain authorization to use these features and to download the cryptographic software from Cisco.com. For more information, see the release notes for this release. The switch supports one of these feature sets: • IP base feature set, which provides Layer 2+ features (enterprise-class intelligent services). These features include access control lists (ACLs), quality of service (QoS), static routing, EIGRP stub routing, PIM stub routing, the Hot Standby Router Protocol (HSRP), Routing Information Protocol (RIP), and basic IPv6 management. Switches with the IP base feature set can be upgraded to the IP services feature set.

OL-13270-06 Chapter 1 Overview Features • IP services feature set, which provides a richer set of enterprise-class intelligent services and full IPv6 support. It includes all IP base features plus full Layer 3 routing (IP unicast routing, IP multicast routing, and fallback bridging). The IP services feature set includes protocols such as the Enhanced Interior Gateway Routing Protocol (EIGRP) and the Open Shortest Path First (OSPF) Protocol. This feature set also supports all IP service features with IPv6 routing and IPv6 ACLs and Multicast Listener Discovery (MLD) snooping. IP services-only Layer 3 features are described in the “Layer 3 Features” section on page 1-14. For more information, see Chapter 25, “Configuring IPv6 MLD Snooping,” and Chapter 36, “Configuring IPv6 ACLs.” For more information on IPv6 routing, see Chapter 40, “Configuring IPv6 Unicast Routing.” For more information about IPv6 ACLs, see Chapter 36, “Configuring IPv6 ACLs.” Note Unless otherwise noted, all features described in this chapter and in this guide are supported on both the IP base and IP services feature sets. The switch has these features: • Deployment Features, page 1-3 • Performance Features, page 1-4 • Management Options, page 1-5 • Manageability Features, page 1-6 (includes a feature requiring the cryptographic universal software image) • Availability and Redundancy Features, page 1-8 • VLAN Features, page 1-9 • Security Features, page 1-10 (includes a feature requiring the cryptographic universal software image) • QoS and CoS Features, page 1-13 • Layer 3 Features, page 1-14 (includes features requiring the IP services feature set) • Monitoring Features, page 1-15

OL-13270-06 Chapter 1 Overview Features Deployment Features The switch ships with these features: • Express Setup for quickly configuring a switch for the first time with basic IP information, contact information, switch and Telnet passwords, and Simple Network Management Protocol (SNMP) information through a browser-based program. For more information about Express Setup, see the getting started guide. • User-defined and Cisco-default Smartports macros for creating custom switch configurations for simplified deployment across the network. • Local web authentication banner so that custom banner or image file can be displayed at a web authentication login screen. • An embedded device manager GUI for configuring and monitoring a single switch through a web browser. For information about starting the device manager, see the getting started guide. For more information about the device manager, see the switch online help. • Cisco Network Assistant (referred to as Network Assistant) for – Managing communities, which are device groups like clusters, except that they can contain routers and access points and can be made more secure. – Simplifying and minimizing switch and switch stack management from anywhere in your intranet. – Accomplishing multiple configuration tasks from a single graphical interface without needing to remember command-line interface (CLI) commands to accomplish specific tasks. – Interactive guide mode that guides you in configuring complex features such as VLANs, ACLs, and quality of service (QoS). – Configuration wizards that prompt you to provide only the minimum required information to configure complex features such as QoS priorities for video traffic, priority levels for data applications, and security. – Downloading an image to a switch. – Applying actions to multiple ports and multiple switches at the same time, such as VLAN and QoS settings, inventory and statistic reports, link- and switch-level monitoring and troubleshooting, and multiple switch software upgrades. – Viewing a topology of interconnected devices to identify existing switch clusters and eligible switches that can join a cluster and to identify link information between switches. – Monitoring real-time status of a switch or multiple switches from the LEDs on the front-panel images. The system and port LED colors on the images are similar to those used on the physical LEDs. • Cisco StackWise Plus technology on stacking-capable switches for – Connecting up to nine switches through their StackWise Plus ports that operate as a single switch or switch-router in the network. – Creating a bidirectional 32-Gb/s switching fabric across the switch stack, with all stack members having full access to the system bandwidth. – Using a single IP address and configuration file to manage the entire switch stack. – Automatic Cisco IOS version-check of new stack members with the option to automatically load images from the stack master or from a TFTP server.

OL-13270-06 Chapter 1 Overview Features – Adding, removing, and replacing switches in the stack without disrupting the operation of the stack. – Provisioning a new member for a switch stack with the offline configuration feature. You can configure in advance the interface configuration for a specific stack member number and for a specific switch type of a new switch that is not part of the stack. The switch stack retains this information across stack reloads whether or not the provisioned switch is part of the stack. – Displaying stack-ring activity statistics (the number of frames sent by each stack member to the ring). • Stack troubleshooting enhancements • Call Home to provide e-mail-based and web-based notification of critical system events. 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. Performance Features The switch ships with these performance features: • Autosensing of port speed and autonegotiation of duplex mode on all switch ports for optimizing bandwidth • Automatic-medium-dependent interface crossover (auto-MDIX) capability on 10/100- and 10/100/1000-Mb/s interfaces and on 10/100/1000 BASE-TX SFP module interfaces that enables the interface to automatically detect the required cable connection type (straight-through or crossover) and to configure the connection appropriately • Support for the maximum packet size or maximum transmission unit (MTU) size for these types of frames: – Up to 9216 bytes for routed frames – Up to 9216 bytes for frames that are bridged in hardware and software through Gigabit Ethernet ports and 10-Gigabit Ethernet ports • IEEE 802.3x flow control on all ports (the switch does not send pause frames) • Up to 64 Gb/s of throughput in a switch stack • EtherChannel for enhanced fault tolerance and for providing up to 8 Gb/s (Gigabit EtherChannel) or 80 Gb/s (10-Gigabit EtherChannel) full-duplex bandwidth among switches, routers, and servers • Port Aggregation Protocol (PAgP) and Link Aggregation Control Protocol (LACP) for automatic creation of EtherChannel links • Support for up to 64 EtherChannels • Forwarding of Layer 2 and Layer 3 packets at Gigabit line rate • Forwarding of Layer 2 and Layer 3 packets at Gigabit line rate across the switches in the stack • Per-port storm control for preventing broadcast, multicast, and unicast storms • Port blocking on forwarding unknown Layer 2 unknown unicast, multicast, and bridged broadcast traffic • Protocol storm protection to control the rate of incoming protocol traffic to a switch by dropping packets that exceed a specified ingress rate • Cisco Group Management Protocol (CGMP) server support and Internet Group Management Protocol (IGMP) snooping for IGMP Versions 1, 2, and 3:

OL-13270-06 Chapter 1 Overview Features – (For CGMP devices) CGMP for limiting multicast traffic to specified end stations and reducing overall network traffic – (For IGMP devices) IGMP snooping for efficiently forwarding multimedia and multicast traffic • IGMP report suppression for sending only one IGMP report per multicast router query to the multicast devices (supported only for IGMPv1 or IGMPv2 queries) • IGMP snooping querier support to configure switch to generate periodic IGMP General Query messages • IGMP Helper to allow the switch to forward a host request to join a multicast stream to a specific IP destination address • Multicast Listener Discovery (MLD) snooping to enable efficient distribution of IP Version 6 (IPv6) multicast data to clients and routers in a switched network. • Multicast VLAN registration (MVR) to continuously send multicast streams in a multicast VLAN while isolating the streams from subscriber VLANs for bandwidth and security reasons • IGMP filtering for controlling the set of multicast groups to which hosts on a switch port can belong • IGMP throttling for configuring the action when the maximum number of entries is in the IGMP forwarding table • IGMP leave timer for configuring the leave latency for the network • Switch Database Management (SDM) templates for allocating system resources to maximize support for user-selected features • Introduction of a new switch database management (SDM) dual IPv4 and IPv6 template that supports more indirect routes • Web Cache Communication Protocol (WCCP) for redirecting traffic to wide-area application engines, for enabling content requests to be fulfilled locally, and for localizing web-traffic patterns in the network (requires the IP services feature set )Support for deny ACL entries in Web Cache Communication Protocol (WCCP) redirect lists. Previously only permit entries were supported. • 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) • RADIUS server load balancing to allow access and authentication requests to be distributed evenly across a server group • CDP and LLDP enhancements for exchanging location information with video end points for dynamic location-based content distribution from servers. Management Options These are the options for configuring and managing the switch: • An embedded device manager—The device manager is a GUI that is integrated in the universal software image. You use it to configure and to monitor a single switch. For information about starting the device manager, see the getting started guide. For more information about the device manager, see the switch online help. • Network Assistant—Network Assistant is a network management application that can be downloaded from Cisco.com. You use it to manage a single switch, a cluster of switches, or a community of devices. For more information about Network Assistant, see Getting Started with Cisco Network Assistant, available on Cisco.com.

OL-13270-06 Chapter 1 Overview Features • CLI—The Cisco IOS software supports desktop- and multilayer-switching features. You can access the CLI by connecting your management station directly to the switch console port, by connecting your PC directly to the Ethernet management port, or by using Telnet from a remote management station or PC. You can manage the switch stack by connecting to the console port or Ethernet management port of any stack member. For more information about the CLI, see Chapter 2, “Using the Command-Line Interface.” • SNMP—SNMP management applications such as CiscoWorks2000 LAN Management Suite (LMS) and HP OpenView. You can manage from an SNMP-compatible management station or a PC that is running platforms such as HP OpenView or SunNet Manager. The switch supports a comprehensive set of MIB extensions and four remote monitoring (RMON) groups. For more information about using SNMP, see Chapter 33, “Configuring SNMP.” • 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. You can automate initial configurations and configuration updates by generating switch-specific configuration changes, sending them to the switch, executing the configuration change, and logging the results. For more information about CNS, see Chapter 4, “Configuring Cisco IOS Configuration Engine.” • Chassis management controller (CMC) GUI—The internal Ethernet management port (also referred to as the Fa0 or fastethernet0 port) on the switch sends and receives only management traffic between the switch and the CMC. The port is connected to the CMC through the backplane connector. Manageability Features These are the manageability features: • CNS embedded agents for automating switch management, configuration storage, and delivery • DHCP for automating configuration of switch information (such as IP address, default gateway, hostname, and Domain Name System [DNS] and TFTP server names) • DHCP relay for forwarding User Datagram Protocol (UDP) broadcasts, including IP address requests, from DHCP clients • DHCP server for automatic assignment of IP addresses and other DHCP options to IP hosts • 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

OL-13270-06 Chapter 1 Overview Features • Support for the LLDP-MED location TLV that provides location information from the switch to the endpoint device • CDP and LLDP enhancements for exchanging location information with video end points for dynamic location-based content distribution from servers • Network Time Protocol (NTP) for providing a consistent time stamp to all switches from an external source • Network Time Protocol version 4 (NTPv4) to support both IPv4 and IPv6 and compatibility with NTPv3 • Cisco IOS File System (IFS) for providing a single interface to all file systems that the switch uses • Configuration logging to log and to view changes to the switch configuration • Configuration replacement and rollback to replace the running configuration on a switch with any saved Cisco IOS configuration file • Unique device identifier to provide product identification information through a show inventory user EXEC command display • In-band management access through the device manager over a Netscape Navigator or Microsoft Internet Explorer browser session • In-band management access for up to 16 simultaneous Telnet connections for multiple CLI-based sessions over the network • In-band management access for up to five simultaneous, encrypted Secure Shell (SSH) connections for multiple CLI-based sessions over the network (requires the cryptographic universal software image) • In-band management access through SNMP Versions 1, 2c, and 3 get and set requests • Out-of-band management access through the switch console port to a directly attached terminal or to a remote terminal through a serial connection or a modem • Out-of-band management access through the internal Ethernet management port to a PC • Secure Copy Protocol (SCP) feature to provide a secure and authenticated method for copying switch configuration or switch image files (requires the cryptographic universal software image) • Wired location service that sends location and attachment tracking information for connected devices to a Cisco Mobility Services Engine (MSE) • LLDP-MED network-policy profile time, length, value (TLV) for creating a profile for voice and voice-signalling by specifying the values for VLAN, class of service (CoS), differentiated services code point (DSCP), and tagging mode CPU utilization threshold trap to monitor CPU utilization • The HTTP client in Cisco IOS supports can send requests to both IPv4 and IPv6 HTTP servers, and the HTTP server in Cisco IOS can service HTTP requests from both IPv4 and IPv6 HTTP clients. • SNMP can be configured over IPv6 transport so that an IPv6 host can send SNMP queries and receive SNMP notifications from a device running IPv6. • IPv6 supports stateless autoconfiguration to manage link, subnet, and site addressing changes, such as management of host and mobile IP addresses. • Support for including a hostname in the option 12 field of DHCPDISCOVER packets. 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. • Cisco EnergyWise to manage the power usage of EnergyWise entities, such as power over Ethernet (PoE) devices and end points running daemons.

OL-13270-06 Chapter 1 Overview Features Note For additional descriptions of the management interfaces, see the “Network Configuration Examples” section on page 1-20. Availability and Redundancy Features These are the availability and redundancy features: • HSRP for command switch and Layer 3 router redundancy • Automatic stack master re-election (failover support) for replacing stack masters that become unavailable (only stacking-capable switches) The newly elected stack master begins accepting Layer 2 traffic in less than 1 second and Layer 3 traffic between 3 to 5 seconds. • Cross-stack EtherChannel for providing redundant links across the switch stack (only stacking-capable switches) • UniDirectional Link Detection (UDLD) and aggressive UDLD for detecting and disabling unidirectional links on fiber-optic interfaces caused by incorrect fiber-optic wiring or port faults • IEEE 802.1D Spanning Tree Protocol (STP) for redundant backbone connections and loop-free networks. STP has these features: – Up to 128 spanning-tree instances supported – Per-VLAN spanning-tree plus (PVST+) for load-balancing across VLANs – Rapid PVST+ for load-balancing across VLANs and providing rapid convergence of spanning-tree instances – UplinkFast, cross-stack UplinkFast (only stacking-capable switches), and BackboneFast for fast convergence after a spanning-tree topology change and for achieving load-balancing between redundant uplinks, including Gigabit uplinks and cross-stack Gigabit uplinks (only stacking-capable switches) • IEEE 802.1s Multiple Spanning Tree Protocol (MSTP) for grouping VLANs into a spanning-tree instance and for providing multiple forwarding paths for data traffic and load-balancing and rapid per-VLAN Spanning-Tree plus (rapid-PVST+) based on the IEEE 802.1w Rapid Spanning Tree Protocol (RSTP) for rapid convergence of the spanning tree by immediately changing root and designated ports to the forwarding state • Optional spanning-tree features available in PVST+, rapid-PVST+, and MSTP mode: – Port Fast for eliminating the forwarding delay by enabling a port to immediately change from the blocking state to the forwarding state – BPDU guard for shutting down Port Fast-enabled ports that receive bridge protocol data units (BPDUs) – BPDU filtering for preventing a Port Fast-enabled port from sending or receiving BPDUs – Root guard for preventing switches outside the network core from becoming the spanning-tree root – Loop guard for preventing alternate or root ports from becoming designated ports because of a failure that leads to a unidirectional link • Equal-cost routing for link-level and switch-level redundancy

OL-13270-06 Chapter 1 Overview Features • Flex Link Layer 2 interfaces to back up one another as an alternative to STP for basic link redundancy • Link-state tracking to mirror the state of the ports that carry upstream traffic from connected hosts and servers and to allow the failover of the server traffic to an operational link on another Cisco Ethernet switch • Support for VTP version 3 that includes support for configuring extended range VLANs (VLANs 1006 to 4094) in any VTP mode, enhanced authentication (hidden or secret passwords), propagation of other databases in addition to VTP, VTP primary and secondary servers, and the option to turn VTP on or off by port. VLAN Features These are the VLAN features: • Support for up to 1005 VLANs for assigning users to VLANs associated with appropriate network resources, traffic patterns, and bandwidth • Support for VLAN IDs in the 1 to 4094 range as allowed by the IEEE 802.1Q standard • VLAN Query Protocol (VQP) for dynamic VLAN membership • IEEE 802.1Q trunking encapsulation on all ports for network moves, adds, and changes; management and control of broadcast and multicast traffic; and network security by establishing VLAN groups for high-security users and network resources • Dynamic Trunking Protocol (DTP) for negotiating trunking and encapsulation on a link between two devices • VLAN Trunking Protocol (VTP) and VTP pruning for reducing network traffic by restricting flooded traffic to links destined for stations receiving the traffic • Voice VLAN for creating subnets for voice traffic from Cisco IP Phones • Dynamic voice virtual LAN (VLAN) for multidomain authentication (MDA) to allow a dynamic voice VLAN on an MDA-enabled port • VLAN 1 minimization for reducing the risk of spanning-tree loops or storms by allowing VLAN 1 to be disabled on any individual VLAN trunk link. With this feature enabled, no user traffic is sent or received on the trunk. The switch CPU continues to send and receive control protocol frames. • Private VLANs to address VLAN scalability problems, to provide a more controlled IP address allocation, and to allow Layer 2 ports to be isolated from other ports on the switch • Port security on a PVLAN host to limit the number of MAC addresses learned on a port, or define which MAC addresses may be learned on a port • VLAN Flex Link Load Balancing to provide Layer 2 redundancy without requiring Spanning Tree Protocol (STP). A pair of interfaces configured as primary and backup links can load balance traffic based on VLAN.

OL-13270-06 Chapter 1 Overview Features Security Features The switch ships with these security features: • Web authentication to allow a supplicant (client) that does not support IEEE 802.1x functionality to be authenticated using a web browser. • Password-protected access (read-only and read-write access) to management interfaces (device manager, Network Assistant, and the CLI) for protection against unauthorized configuration changes • Multilevel security for a choice of security level, notification, and resulting actions • Static MAC addressing for ensuring security • Protected port option for restricting the forwarding of traffic to designated ports on the same switch • Port security option for limiting and identifying MAC addresses of the stations allowed to access the port • VLAN aware port security option to shut down the VLAN on the port when a violation occurs, instead of shutting down the entire port • Port security aging to set the aging time for secure addresses on a port • BPDU guard for shutting down a Port Fast-configured port when an invalid configuration occurs • Standard and extended IP access control lists (ACLs) for defining security policies in both directions on routed interfaces (router ACLs) and VLANs and inbound on Layer 2 interfaces (port ACLs) • Extended MAC access control lists for defining security policies in the inbound direction on Layer 2 interfaces • VLAN ACLs (VLAN maps) for providing intra-VLAN security by filtering traffic based on information in the MAC, IP, and TCP/UDP headers • Source and destination MAC-based ACLs for filtering non-IP traffic • IPv6 ACLs to be applied to interfaces to filter IPv6 traffic • Support for dynamic creation or attachment of an auth-default ACL on a port that has no configured static ACLs • VACL Logging to generate syslog messages for ACL denied IP packets • DHCP snooping to filter untrusted DHCP messages between untrusted hosts and DHCP servers • IP source guard to restrict traffic on nonrouted interfaces by filtering traffic based on the DHCP snooping database and IP source bindings • Dynamic ARP inspection to prevent malicious attacks on the switch by not relaying invalid ARP requests and responses to other ports in the same VLAN • IEEE 802.1Q tunneling so that customers with users at remote sites across a service-provider network can keep VLANs segregated from other customers and Layer 2 protocol tunneling to ensure that the customer’s network has complete STP, CDP, and VTP information about all users • Layer 2 point-to-point tunneling to facilitate the automatic creation of EtherChannels • Layer 2 protocol tunneling bypass feature to provide interoperability with third-party vendors • Flexible-authentication sequencing to configure the order of the authentication methods that a port tries when authenticating a new host • IEEE 802.1x with open access to allow a host to access the network before being authenticated

OL-13270-06 Chapter 1 Overview Features • IEEE 802.1x port-based authentication to prevent unauthorized devices (clients) from gaining access to the network. These features are supported: – Multidomain authentication (MDA) to allow both a data device and a voice device, such as an IP phone (Cisco or non-Cisco), to independently authenticate on the same IEEE 802.1x-enabled switch port – VLAN assignment for restricting IEEE 802.1x-authenticated users to a specified VLAN – Support for VLAN assignment on a port configured for multi-auth mode. The RADIUS server assigns a VLAN to the first host to authenticate on the port, and subsequent hosts use the same VLAN. Voice VLAN assignment is supported for one IP phone – Port security for controlling access to IEEE 802.1x ports – Voice VLAN to permit a Cisco IP Phone to access the voice VLAN regardless of the authorized or unauthorized state of the port – IP phone detection enhancement to detect and recognize a Cisco IP phone – Guest VLAN to provide limited services to non-IEEE 802.1x-compliant users – Restricted VLAN to provide limited services to users who are IEEE 802.1x compliant, but do not have the credentials to authenticate via the standard IEEE 802.1x processes – IEEE 802.1x accounting to track network usage – IEEE 802.1x with wake-on-LAN to allow dormant PCs to be powered on based on the receipt of a specific Ethernet frame – Voice aware IEEE 802.1x and MAC authentication bypass (MAB) security violation to shut down only the data VLAN on a port when a security violation occurs – IEEE 802.1x readiness check to determine the readiness of connected end hosts before configuring IEEE 802.1x on the switch – Network Edge Access Topology (NEAT) with 802.1x switch supplicant, host authorization with Client Information Signalling Protocol (CISP), and auto enablement to authenticate a switch outside a wiring closet as a supplicant to another switch – IEEE 802.1x authentication with downloadable ACLs and redirect URLs to allow per-user ACL downloads from a Cisco Secure ACS server to an authenticated switch – Multiple-user authentication to allow more than one host to authenticate on an 802.1x-enabled port. • MAC authentication bypass to authorize clients based on the client MAC address. • “Configuring NAC Layer 2 802.1x Validation” section on page 9-58Network Admission Control (NAC) features: – NAC Layer 2 IEEE 802.1x validation of the antivirus condition or posture of endpoint systems or clients before granting the devices network access. For information about configuring NAC Layer 2 IEEE 802.1x validation, see the “Configuring NAC Layer 2 802.1x Validation” section on page 9-58. – NAC Layer 2 IP validation of the posture of endpoint systems or clients before granting the devices network access. For information about configuring NAC Layer 2 IP validation, see the Network Admission Control Software Configuration Guide.

OL-13270-06 Chapter 1 Overview Features – IEEE 802.1x inaccessible authentication bypass. For information about configuring this feature, see the “Configuring the Inaccessible Authentication Bypass Feature” section on page 9-53. – Authentication, authorization, and accounting (AAA) down policy for a NAC Layer 2 IP validation of a host if the AAA server is not available when the posture validation occurs. For information about this feature, see the Network Admission Control Software Configuration Guide. • TACACS+, a proprietary feature for managing network security through a TACACS server • RADIUS for verifying the identity of, granting access to, and tracking the actions of remote users through AAA services • Enhancements to RADIUS, TACACS+, and SSH to function over IPv6. • Kerberos security system to authenticate requests for network resources by using a trusted third party (requires the cryptographic universal software image) • Secure Socket Layer (SSL) Version 3.0 support for the HTTP 1.1 server authentication, encryption, and message integrity and HTTP client authentication to allow secure HTTP communications (requires the cryptographic universal software image) • Support for IP source guard on static hosts. • RADIUS Change of Authorization (CoA) to change the attributes of a certain session after it is authenticated. When there is a change in policy for a user or user group in AAA, administrators can send the RADIUS CoA packets from the AAA server, such as Cisco Secure ACS to reinitialize authentication, and apply to the new policies. • IEEE 802.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. Authorized users are assigned to the least populated VLAN in the group, assigned by RADIUS server. • Support for critical VLAN with multiple-host authentication so that when a port is configured for multi-auth, and an AAA server becomes unreachable, the port is placed in a critical VLAN in order to still permit access to critical resources. • Customizable web authentication enhancement to allow the creation of user-defined login, success, failure and expire web pages for local web authentication. • 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. • VLAN-ID based MAC authentication to use the combined VLAN and MAC address information for user authentication to prevent network access from unauthorized VLANs. • 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. With MAC move, the switch treats the reappearance of the same MAC address on another port in the same way as a completely new MAC address. • Support for 3DES and AES with version 3 of the Simple Network Management Protocol (SNMPv3). This release adds support for the 168-bit Triple Data Encryption Standard (3DES) and the 128-bit, 192-bit, and 256-bit Advanced Encryption Standard (AES) encryption algorithms to SNMPv3. • Support for the Security Group Tag (SCT) Exchange Protocol (SXP) component of Cisco TrustSec, a security architecture using authentication, encryption, and access control.

OL-13270-06 Chapter 1 Overview Features QoS and CoS Features These are the QoS and CoS features: • Automatic QoS (auto-QoS) to simplify the deployment of existing QoS features by classifying traffic and configuring egress queues • Cross-stack QoS for configuring QoS features to all switches in a switch stack rather than on an individual-switch basis (only stacking-capable switches) • Classification – IP type-of-service/Differentiated Services Code Point (IP ToS/DSCP) and IEEE 802.1p CoS marking priorities on a per-port basis for protecting the performance of mission-critical applications – IP ToS/DSCP and IEEE 802.1p CoS marking based on flow-based packet classification (classification based on information in the MAC, IP, and TCP/UDP headers) for high-performance quality of service at the network edge, allowing for differentiated service levels for different types of network traffic and for prioritizing mission-critical traffic in the network – Trusted port states (CoS, DSCP, and IP precedence) within a QoS domain and with a port bordering another QoS domain – Trusted boundary for detecting the presence of a Cisco IP Phone, trusting the CoS value received, and ensuring port security • Policing – Traffic-policing policies on the switch port for managing how much of the port bandwidth should be allocated to a specific traffic flow – If you configure multiple class maps for a hierarchical policy map, each class map can be associated with its own port-level (second-level) policy map. Each second-level policy map can have a different policer. – Aggregate policing for policing traffic flows in aggregate to restrict specific applications or traffic flows to metered, predefined rates • Out-of-Profile – Out-of-profile markdown for packets that exceed bandwidth utilization limits • Ingress queueing and scheduling – Two configurable ingress queues for user traffic (one queue can be the priority queue) – Weighted tail drop (WTD) as the congestion-avoidance mechanism for managing the queue lengths and providing drop precedences for different traffic classifications – Shaped round robin (SRR) as the scheduling service for specifying the rate at which packets are sent to the stack or internal ring (sharing is the only supported mode on ingress queues) • Egress queues and scheduling – Four egress queues per port – WTD as the congestion-avoidance mechanism for managing the queue lengths and providing drop precedences for different traffic classifications

OL-13270-06 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). Shaped egress queues are guaranteed but limited to using a share of port bandwidth. Shared egress queues are also guaranteed a configured share of bandwidth, but can use more than the guarantee if other queues become empty and do not use their share of the bandwidth. • Automatic quality of service (QoS) voice over IP (VoIP) enhancement for port -based trust of DSCP and priority queuing for egress traffic • Full QoS support for IPv6 traffic • Auto-QoS enhancements that add automatic configuration classification of traffic flow from video devices, such as the Cisco TelePresence System and Cisco Surveillance Camera. Layer 3 Features These are the Layer 3 features: Note Some features noted in this section are available only in the IP services feature set. • HSRP Version 1 (HSRPv1) and HSRP Version 2 (HSRPv2) for Layer 3 router redundancy • HSRP for IPv6 (requires the IP services feature set) • IPv6 default router preference (DRP) for improving the ability of a host to select an appropriate router. • IP routing protocols for load balancing and for constructing scalable, routed backbones: – RIP Versions 1 and 2 Full OSPF support (requires the IP services feature set)The IP Base image supports OSPF for routed access to enable customers to extend Layer 3 routing capabilities to the access or wiring closet. – HSRP for IPv6 (requires the IP services feature set) – Enhanced IGRP (EIGRP) (requires the IP services feature set) – Border Gateway Protocol (BGP) Version 4 (requires the IP services feature set) • IP routing between VLANs (inter-VLAN routing) for full Layer 3 routing between two or more VLANs, allowing each VLAN to maintain its own autonomous data-link domain • Policy-based routing (PBR) for configuring defined policies for traffic flows • Multiple VPN routing/forwarding (multi-VRF) instances in customer edge devices to allow service providers to support multiple virtual private networks (VPNs) and overlap IP addresses between VPNs (requires the IP services feature set) • VRF Lite for configuring multiple private routing domains for network virtualization and virtual private multicast networks • Support for these IP services, making them VRF aware so that they can operate on multiple routing instances: HSRP, uRPF, ARP, SNMP, IP SLA, TFTP, FTP, syslog, traceroute, and ping • Fallback bridging for forwarding non-IP traffic between two or more VLANs (requires the IP services feature set) • Static IP routing for manually building a routing table of network path information • Equal-cost routing for load-balancing and redundancy

OL-13270-06 Chapter 1 Overview Features • Internet Control Message Protocol (ICMP) and ICMP Router Discovery Protocol (IRDP) for using router advertisement and router solicitation messages to discover the addresses of routers on directly attached subnets • Protocol-Independent Multicast (PIM) for multicast routing within the network, allowing for devices in the network to receive the multicast feed requested and for switches not participating in the multicast to be pruned. Includes support for PIM sparse mode (PIM-SM), PIM dense mode (PIM-DM), and PIM sparse-dense mode (requires the IP services feature set) • Multicast Source Discovery Protocol (MSDP) for connecting multiple PIM-SM domains (requires the IP services feature set) • Distance Vector Multicast Routing Protocol (DVMRP) tunneling for interconnecting two multicast-enabled networks across nonmulticast networks (requires the IP services feature set) • DHCP relay for forwarding UDP broadcasts, including IP address requests, from DHCP clients • DHCP for IPv6 relay, client, server address assignment and prefix delegation • DHCPv6 bulk-lease query to support new bulk lease query type (as defined in RFC5460) • The DHCPv6 relay source configuration feature to configure a source address for DHCPv6 relay agent • IPv6 unicast routing capability for forwarding IPv6 traffic through configured interfaces (requires the IP services feature set) • IPv6 default router preference (DRP) for improving the ability of a host to select an appropriate router • IPv6 unicast routing capability for forwarding IPv6 traffic through configured interfaces (requires the IP services feature set) • Support for EIGRP IPv6, which utilizes IPv6 transport, communicates with IPv6 peers, and advertises IPv6 routes • IP unicast reverse path forwarding (unicast RPF) for confirming source packet IP addresses • Nonstop forwarding (NSF) awareness to enable the Layer 3 switch to continue forwarding packets from an NSF-capable neighboring router when the primary route processor (RP) is failing and the backup RP is taking over, or when the primary RP is manually reloaded for a nondisruptive software upgrade (requires the IP services feature set) • NSF-capable routing for OSPF and EIGRP that allows the switch to rebuild routing tables based on information from NSF-aware and NSF-capable neighbors (only stacking-capable switches)NSF IETF mode for OSPFv2—OSPFv2 graceful restart support for IPv4 (IP services feature set only) • NSF IETF mode for OSPFv3—OSPFv3 graceful restart support for IPv6 (IP services feature set only) • The ability to exclude a port in a VLAN from the SVI line-state up or down calculation • Intermediate System-to-Intermediate System (IS-IS) routing supports dynamic routing protocols for Connectionless Network Service (CLNS) networks (requires the IP services feature set)Support for the Virtual Router Redundancy Protocol (VRRPv4), which dynamically assigns responsibility for one or more virtual routers to the VRRP routers on a LAN, allowing multiple routers on a multiaccess link to utilize the same virtual IP address. Monitoring Features These are the monitoring features:

OL-13270-06 Chapter 1 Overview Default Settings After Initial Switch Configuration • Switch LEDs that provide port- and switch-level status on nonstacking-capable switches • Switch LEDs that provide port-, switch-, and stack-level status on stacking-capable switches • MAC address notification traps and RADIUS accounting for tracking users on a network by storing the MAC addresses that the switch has learned or removed • Switched Port Analyzer (SPAN) and Remote SPAN (RSPAN) for traffic monitoring on any port or VLAN • SPAN and RSPAN support of Intrusion Detection Systems (IDS) to monitor, repel, and report network security violations • Four groups (history, statistics, alarms, and events) of embedded RMON agents for network monitoring and traffic analysis • Syslog facility for logging system messages about authentication or authorization errors, resource issues, and time-out events • Layer 2 traceroute to identify the physical path that a packet takes from a source device to a destination device • Time Domain Reflector (TDR) to diagnose and resolve cabling problems on 10/100 and 10/100/1000 copper Ethernet ports • SFP module diagnostic management interface to monitor physical or operational status of an SFP module • Online diagnostics to test the hardware functionality of the supervisor engine, modules, and switch while the switch is connected to a live network • On-board failure logging (OBFL) to collect information about the switch and the power supplies connected to it • Digital optical monitoring (DOM) to check status of X2 small form-factor pluggable (SFP) modules • Enhanced object tracking (EOT) for HSRP to determine the proportion of hosts in a LAN by tracking the routing table state or to trigger the standby router failover • IP Service Level Agreements (IP SLAs) support to measure network performance by using active traffic monitoring • IP SLAs EOT to use the output from IP SLAs tracking operations triggered by an action such as latency, jitter, or packet loss for a standby router failover takeover • Support for Embedded Event Manager (EEM) for event detection and recovery within a Cisco IOS device, and EEM 3.2, which introduces event detectors for Neighbor Discovery, Identity, and MAC-Address-Table • Memory consistency check routine enhancements to detect and correct invalid ternary content addressable memory (TCAM) table entries that can affect switch performance • IETF IP-MIB and IP-FORWARD-MIB(RFC4292 and RFC4293) updates to support the IP version 6 (IPv6)-only and the IPv6 part of the protocol-version independent (PVI) objects and tables Default Settings After Initial Switch Configuration The switch is designed for plug-and-play operation, requiring only that you assign basic IP information to the switch and connect it to the other devices in your network. If you have specific network needs, you can change the interface-specific and system- and stack-wide settings.

OL-13270-06 Chapter 1 Overview Default Settings After Initial Switch Configuration Note For information about assigning an IP address by using the browser-based Express Setup program, see the getting started guide. For information about assigning an IP address by using the CLI-based setup program, see the hardware installation guide. If you do not configure the switch at all, the switch operates with these default settings: • Default switch IP address, subnet mask, and default gateway is 0.0.0.0. For more information, see Chapter 3, “Assigning the Switch IP Address and Default Gateway,” andChapter 22, “Configuring DHCP Features and IP Source Guard.” • Default domain name is not configured. For more information, see Chapter 3, “Assigning the Switch IP Address and Default Gateway.” • DHCP client is enabled, the DHCP server is enabled (only if the device acting as a DHCP server is configured and is enabled), and the DHCP relay agent is enabled (only if the device is acting as a DHCP relay agent is configured and is enabled). For more information, see Chapter 3, “Assigning the Switch IP Address and Default Gateway,” and Chapter 22, “Configuring DHCP Features and IP Source Guard.” • Switch stack is enabled (not configurable). For more information, see Chapter 7, “Managing Switch Stacks.” • No passwords are defined. For more information, see Chapter 5, “Administering the Switch.” • System name and prompt is Switch. For more information, see Chapter 5, “Administering the Switch.” • NTP is enabled. For more information, see Chapter 5, “Administering the Switch.” • DNS is enabled. For more information, see Chapter 5, “Administering the Switch.” • TACACS+ is disabled. For more information, see Chapter 6, “Configuring Switch-Based Authentication.” • RADIUS is disabled. For more information, see Chapter 6, “Configuring Switch-Based Authentication.” • The standard HTTP server and Secure Socket Layer (SSL) HTTPS server are both enabled. For more information, see Chapter 6, “Configuring Switch-Based Authentication.” • IEEE 802.1x is disabled. For more information, see Chapter 9, “Configuring IEEE 802.1x Port-Based Authentication.”

OL-13270-06 Chapter 1 Overview Default Settings After Initial Switch Configuration • Port parameters – Operating mode is Layer 2 (switchport). For more information, see Chapter 11, “Configuring Interface Characteristics.” – Interface speed and duplex mode is autonegotiate. For more information, see Chapter 11, “Configuring Interface Characteristics.” – Auto-MDIX is enabled. For more information, see Chapter 11, “Configuring Interface Characteristics.” – Flow control is off. For more information, see Chapter 11, “Configuring Interface Characteristics.” • No Smartports macros are defined. For more information, see Chapter 12, “Configuring Smartports Macros.” • VLANs – Default VLAN is VLAN 1. For more information, see Chapter 13, “Configuring VLANs.” – VLAN trunking setting is dynamic auto (DTP). For more information, see Chapter 13, “Configuring VLANs.” – Trunk encapsulation is negotiate. For more information, see Chapter 13, “Configuring VLANs.” – VTP mode is server. For more information, see Chapter 14, “Configuring VTP.” – VTP version is Version 1. For more information, see Chapter 14, “Configuring VTP.” – No private VLANs are configured. For more information, see Chapter 16, “Configuring Private VLANs.” – Voice VLAN is disabled. For more information, see Chapter 15, “Configuring Voice VLAN.” • IEEE 802.1Q tunneling and Layer 2 protocol tunneling are disabled. For more information, see Chapter 17, “Configuring IEEE 802.1Q and Layer 2 Protocol Tunneling.” • STP, PVST+ is enabled on VLAN 1. For more information, see Chapter 18, “Configuring STP.” • MSTP is disabled. For more information, see Chapter 19, “Configuring MSTP.” • Optional spanning-tree features are disabled. For more information, see Chapter 20, “Configuring Optional Spanning-Tree Features.” • Flex Links are not configured. For more information, see Chapter 21, “Configuring Flex Links and the MAC Address-Table Move Update Feature.” • DHCP snooping is disabled. The DHCP snooping information option is enabled. For more information, see Chapter 22, “Configuring DHCP Features and IP Source Guard.” • IP source guard is disabled. For more information, see Chapter 22, “Configuring DHCP Features and IP Source Guard.” • Dynamic ARP inspection is disabled on all VLANs. For more information, see Chapter 23, “Configuring Dynamic ARP Inspection.” • IGMP snooping is enabled. No IGMP filters are applied. For more information, see Chapter 24, “Configuring IGMP Snooping and MVR.” • IGMP throttling setting is deny. For more information, see Chapter 24, “Configuring IGMP Snooping and MVR.” • The IGMP snooping querier feature is disabled. For more information, see Chapter 24, “Configuring IGMP Snooping and MVR.” • MVR is disabled. For more information, see Chapter 24, “Configuring IGMP Snooping and MVR.”

OL-13270-06 Chapter 1 Overview Default Settings After Initial Switch Configuration • Port-based traffic – Broadcast, multicast, and unicast storm control is disabled. For more information, see Chapter 26, “Configuring Port-Based Traffic Control.” – No protected ports are defined. For more information, see Chapter 26, “Configuring Port-Based Traffic Control.” – Unicast and multicast traffic flooding is not blocked. For more information, see Chapter 26, “Configuring Port-Based Traffic Control.” – No secure ports are configured. For more information, see Chapter 26, “Configuring Port-Based Traffic Control.” • CDP is enabled. For more information, see Chapter 27, “Configuring CDP.” • UDLD is disabled. For more information, see Chapter 29, “Configuring UDLD.” • SPAN and RSPAN are disabled. For more information, see Chapter 30, “Configuring SPAN and RSPAN.” • RMON is disabled. For more information, see Chapter 31, “Configuring RMON.” • Syslog messages are enabled and appear on the console. For more information, see Chapter 32, “Configuring System Message Logging.” • SNMP is enabled (Version 1). For more information, see Chapter 33, “Configuring SNMP.” • No ACLs are configured. For more information, see Chapter 35, “Configuring Network Security with ACLs.” • QoS is disabled. For more information, see Chapter 37, “Configuring QoS.” • No EtherChannels are configured. For more information, see Chapter 38, “Configuring EtherChannels and Link-State Tracking.” • IP unicast routing is disabled. For more information, see Chapter 39, “Configuring IP Unicast Routing.” • No HSRP groups are configured. For more information, see Chapter 41, “Configuring HSRP and VRRP.” • IP multicast routing is disabled on all interfaces. For more information, see Chapter 45, “Configuring IP Multicast Routing.” • MSDP is disabled. For more information, see Chapter 46, “Configuring MSDP.” • Fallback bridging is not configured. For more information, see Chapter 47, “Configuring Fallback Bridging.”

OL-13270-06 Chapter 1 Overview Network Configuration Examples Network Configuration Examples This section provides network configuration concepts and includes examples of using the switch to create dedicated network segments and interconnecting the segments through Gigabit Ethernet and 10-Gigabit Ethernet connections. • “Design Concepts for Using the Switch” section on page 1-20 • “Small to Medium-Sized Network” section on page 1-23 Design Concepts for Using the Switch As your network users compete for network bandwidth, it takes longer to send and receive data. When you configure your network, consider the bandwidth required by your network users and the relative priority of the network applications that they use. Table 1-1 describes what can cause network performance to degrade and how you can configure your network to increase the bandwidth available to your network users. Table 1-1 Increasing Network Performance Network Demands Suggested Design Methods Too many users on a single network segment and a growing number of users accessing the Internet • Create smaller network segments so that fewer users share the bandwidth, and use VLANs and IP subnets to place the network resources in the same logical network as the users who access those resources most. • Use full-duplex operation between the switch and its connected workstations. • Increased power of new PCs, workstations, and servers • High bandwidth demand from networked applications (such as e-mail with large attached files) and from bandwidth-intensive applications (such as multimedia) • Connect global resources—such as servers and routers to which the network users require equal access—directly to the high-speed switch ports so that they have their own high-speed segment. • Use the EtherChannel feature between the switch and its connected servers and routers.

OL-13270-06 Chapter 1 Overview Network Configuration Examples Bandwidth alone is not the only consideration when designing your network. As your network traffic profiles evolve, consider providing network services that can support applications for voice and data integration, multimedia integration, application prioritization, and security. Table 1-2 describes some network demands and how you can meet them. Table 1-2 Providing Network Services Network Demands Suggested Design Methods Efficient bandwidth usage for multimedia applications and guaranteed bandwidth for critical applications • Use IGMP snooping to efficiently forward multimedia and multicast traffic. • Use other QoS mechanisms such as packet classification, marking, scheduling, and congestion avoidance to classify traffic with the appropriate priority level, thereby providing maximum flexibility and support for mission-critical, unicast, and multicast, and multimedia applications. • Use optional IP multicast routing to design networks better suited for multicast traffic. • Use MVR to continuously send multicast streams in a multicast VLAN but to isolate the streams from subscriber VLANs for bandwidth and security reasons. High demand on network redundancy and availability to provide always on mission-critical applications • Use switch stacks, where all stack members are eligible stack masters in case of stack-master failure. All stack members have synchronized copies of the saved and running configuration files of the switch stack. • Use cross-stack EtherChannels for providing redundant links across the switch stack. • Use Hot Standby Router Protocol (HSRP) for cluster command switch and router redundancy. • Use VLAN trunks, cross-stack UplinkFast, and BackboneFast for traffic-load balancing on the uplink ports so that the uplink port with a lower relative port cost is selected to carry the VLAN traffic. An evolving demand for IP telephony • Use QoS to prioritize applications such as IP telephony during congestion and to help control both delay and jitter within the network. • Use switches that support at least two queues per port to prioritize voice and data traffic as either high- or low-priority, based on IEEE 802.1p/Q. The switch supports at least four queues per port. • Use voice VLAN IDs (VVIDs) to provide separate VLANs for voice traffic. A growing demand for using existing infrastructure to transport data and voice from a home or office to the Internet or an intranet at higher speeds Use the Catalyst Long-Reach Ethernet (LRE) switches to provide up to 15 Mb of IP connectivity over existing infrastructure, such as existing telephone lines. Note LRE is the technology used in the Catalyst 2950 LRE switch. See the documentation sets specific to this switch for LRE information.

OL-13270-06 Chapter 1 Overview Network Configuration Examples You can use the switches and switch stacks to create the following: • Data center (Figure 1-1)—For high-speed access to network resources, you can use switches and switch stacks in the access layer to provide Gigabit Ethernet access to the blade servers. To prevent congestion, use QoS DSCP marking priorities on these switches. For high-speed IP forwarding at the distribution layer, connect the switches in the access layer to a Gigabit multilayer switch in the backbone, such as a Catalyst 4500 Gigabit switch or Catalyst 6500 Gigabit switch. Figure 1-1 Data Center • Expanded data center (Figure 1-2)—You can use standalone switches and switch stacks to interconnect groups of servers, centralizing physical security and administration of your network. For high-speed IP forwarding at the distribution layer, connect the switches in the access layer to multilayer switches with routing capability. The Gigabit interconnections minimize latency in the data flow. QoS and policing on the switches provide preferential treatment for certain data streams. They segment traffic streams into different paths for processing. Security features on the switch ensure rapid handling of packets. Fault tolerance from the server racks to the core is achieved through dual homing of servers connected to dual switch stacks or the switches, which have redundant Gigabit EtherChannels and cross-stack EtherChannels. Using dual SFP module uplinks from the switches provides redundant uplinks to the network core. Using SFP modules provides flexibility in media and distance options through fiber-optic connections. The various lengths of stack cable available, ranging from 0.5 meter to 3 meters, provide extended connections to the switch stacks across multiple server racks, for multiple stack aggregation. Si 201756 Catalyst 4500 or 6500 multilayer switch Distribution layer Access layer Blade servers Blade switch Layer 3 StackWise Plus switch stack Core

OL-13270-06 Chapter 1 Overview Network Configuration Examples Figure 1-2 Expanded Data Center Small to Medium-Sized Network Figure 1-3 shows a configuration for a network of up to 500 employees. This network uses a Layer 3 switch stack with high-speed connections to two routers. For network reliability and load-balancing, this network has HSRP enabled on the routers and on the switches. This ensures connectivity to the Internet, WAN, and mission-critical network resources in case one of the routers or switches fails. The switches are using routed uplinks for faster failover. They are also configured with equal-cost routing for load sharing and redundancy. A Layer 2 switch stack can use cross-stack EtherChannel for load sharing. The switches are connected to local servers. The server farm includes a call-processing server running Cisco CallManager software. Cisco CallManager controls call processing and routing. The switches are interconnected through Gigabit interfaces. This network uses VLANs to logically segment the network into well-defined broadcast groups and for security management. Data and multimedia traffic are configured on the same VLAN. Voice traffic is configured on separate VVIDs. If data, multimedia, and voice traffic are assigned to the same VLAN, only one VLAN can be configured per wiring closet. When an end station in one VLAN needs to communicate with an end station in another VLAN, a router or Layer 3 switch routes the traffic to the destination VLAN. In this network, the switch stack is providing inter-VLAN routing. VLAN access control lists (VLAN maps) on the switch stack or switch provide intra-VLAN security and prevent unauthorized users from accessing critical areas of the network. In addition to inter-VLAN routing, the multilayer switches provide QoS mechanisms such as DSCP priorities to prioritize the different types of network traffic and to deliver high-priority traffic. If congestion occurs, QoS drops low-priority traffic to allow delivery of high-priority traffic. Cisco CallManager controls call processing and routing. Users with workstations running Cisco SoftPhone software can place, receive, and control calls from their PCs. Using Cisco CallManager software and Cisco SoftPhone software integrates telephony and IP networks, and the IP network supports both voice and data. 201757 Si Si Si Si Si Si Campus core Catalyst 6500 switches Catalyst 6500 multilayer switches Blade switch StackWise switch stacks Blade server enclosures

OL-13270-06 Chapter 1 Overview Where to Go Next With the multilayer switches providing inter-VLAN routing and other network services, the routers focus on firewall services, Network Address Translation (NAT) services, voice-over-IP (VoIP) gateway services, and WAN and Internet access. Figure 1-3 Switch Stack in a Collapsed Backbone Where to Go Next Before configuring the switch, review these sections for startup information: • Chapter 2, “Using the Command-Line Interface” • Chapter 3, “Assigning the Switch IP Address and Default Gateway” To locate and download MIBs for a specific Cisco product and release, use the Cisco MIB Locator: http://cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml. 201914 Campus core Catalyst 6500 switches Blade switch StackWise switch stacks Blade server enclosures

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

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

OL-13270-06 Chapter 2 Using the Command-Line Interface Understanding the Help System For more detailed information on the command modes, see the command reference guide for this release. Understanding the Help System You can enter a question mark (?) at the system prompt to display a list of commands available for each command mode. You can also obtain a list of associated keywords and arguments for any command, as shown in Table 2-2. Understanding Abbreviated Commands You need to enter only enough characters for the switch to recognize the command as unique. This example shows how to enter the show configuration privileged EXEC command in an abbreviated form: Switch# show conf Table 2-2 Help Summary Command Purpose help Obtain a brief description of the help system in any command mode. abbreviated-command-entry? Obtain a list of commands that begin with a particular character string. For example: Switch# di? dir disable disconnect abbreviated-command-entry Complete a partial command name. For example: Switch# sh conf Switch# show configuration ? List all commands available for a particular command mode. For example: Switch> ? command ? List the associated keywords for a command. For example: Switch> show ? command keyword ? List the associated arguments for a keyword. For example: Switch(config)# cdp holdtime ? <10-255> Length of time (in sec) that receiver must keep this packet

OL-13270-06 Chapter 2 Using the Command-Line Interface Understanding no and default Forms of Commands Understanding no and default Forms of Commands Almost every configuration command also has a no form. In general, use the no form to disable a feature or function or reverse the action of a command. For example, the no shutdown interface configuration command reverses the shutdown of an interface. Use the command without the keyword no to re-enable a disabled feature or to enable a feature that is disabled by default. Configuration commands can also have a default form. The default form of a command returns the command setting to its default. Most commands are disabled by default, so the default form is the same as the no form. However, some commands are enabled by default and have variables set to certain default values. In these cases, the default command enables the command and sets variables to their default values. Understanding CLI Error Messages Table 2-3 lists some error messages that you might encounter while using the CLI to configure your switch. Table 2-3 Common CLI Error Messages Error Message Meaning How to Get Help % Ambiguous command: "show con" You did not enter enough characters for your switch to recognize the command. Re-enter the command followed by a question mark (?) with a space between the command and the question mark. The possible keywords that you can enter with the command appear. % Incomplete command. You did not enter all the keywords or values required by this command. Re-enter the command followed by a question mark (?) with a space between the command and the question mark. The possible keywords that you can enter with the command appear. % Invalid input detected at ‘^’ marker. You entered the command incorrectly. The caret (^) marks the point of the error. Enter a question mark (?) to display all the commands that are available in this command mode. The possible keywords that you can enter with the command appear.

OL-13270-06 Chapter 2 Using the Command-Line Interface Using Configuration Logging Using Configuration Logging You can log and view changes to the switch configuration. You can use the Configuration Change Logging and Notification feature to track changes on a per-session and per-user basis. The logger tracks each configuration command that is applied, the user who entered the command, the time that the command was entered, and the parser return code for the command. This feature includes a mechanism for asynchronous notification to registered applications whenever the configuration changes. You can choose to have the notifications sent to the syslog. For more information, see the “Configuration Change Notification and Logging” section of the Cisco IOS Configuration Fundamentals Configuration Guide, Release 12.4. Note Only CLI or HTTP changes are logged. Using Command History The software provides a history or record of commands that you have entered. The command history feature is particularly useful for recalling long or complex commands or entries, including access lists. You can customize this feature to suit your needs as described in these sections: • Changing the Command History Buffer Size, page 2-5 (optional) • Recalling Commands, page 2-6 (optional) • Disabling the Command History Feature, page 2-6 (optional) Changing the Command History Buffer Size By default, the switch records ten command lines in its history buffer. You can alter this number for a current terminal session or for all sessions on a particular line. These procedures are optional. Beginning in privileged EXEC mode, enter this command to change the number of command lines that the switch records during the current terminal session: Switch# terminal history [size number-of-lines] The range is from 0 to 256. Beginning in line configuration mode, enter this command to configure the number of command lines the switch records for all sessions on a particular line: Switch(config-line)# history [size number-of-lines] The range is from 0 to 256.

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

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

OL-13270-06 Chapter 2 Using the Command-Line Interface Using Editing Features Editing Command Lines that Wrap You can use a wraparound feature for commands that extend beyond a single line on the screen. When the cursor reaches the right margin, the command line shifts ten spaces to the left. You cannot see the first ten characters of the line, but you can scroll back and check the syntax at the beginning of the command. The keystroke actions are optional. To scroll back to the beginning of the command entry, press Ctrl-B or the left arrow key repeatedly. You can also press Ctrl-A to immediately move to the beginning of the line. Note The arrow keys function only on ANSI-compatible terminals such as VT100s. In this example, the access-list global configuration command entry extends beyond one line. When the cursor first reaches the end of the line, the line is shifted ten spaces to the left and redisplayed. The dollar sign ($) shows that the line has been scrolled to the left. Each time the cursor reaches the end of the line, the line is again shifted ten spaces to the left. Switch(config)# access-list 101 permit tcp 131.108.2.5 255.255.255.0 131.108.1 Switch(config)# $ 101 permit tcp 131.108.2.5 255.255.255.0 131.108.1.20 255.25 Switch(config)# $t tcp 131.108.2.5 255.255.255.0 131.108.1.20 255.255.255.0 eq Switch(config)# $108.2.5 255.255.255.0 131.108.1.20 255.255.255.0 eq 45 Press Esc L. Change the word at the cursor to lowercase. Press Esc U. Capitalize letters from the cursor to the end of the word. Designate a particular keystroke as an executable command, perhaps as a shortcut. Press Ctrl-V or Esc Q. Scroll down a line or screen on displays that are longer than the terminal screen can display. Note The More prompt is used for any output that has more lines than can be displayed on the terminal screen, including show command output. You can use the Return and Space bar keystrokes whenever you see the More prompt. Press the Return key. Scroll down one line. Press the Space bar. Scroll down one screen. Redisplay the current command line if the switch suddenly sends a message to your screen. Press Ctrl-L or Ctrl-R. Redisplay the current command line. 1. The arrow keys function only on ANSI-compatible terminals such as VT100s. Table 2-5 Editing Commands through Keystrokes (continued) Capability Keystroke1 Purpose

OL-13270-06 Chapter 2 Using the Command-Line Interface Searching and Filtering Output of show and more Commands After you complete the entry, press Ctrl-A to check the complete syntax before pressing the Return key to execute the command. The dollar sign ($) appears at the end of the line to show that the line has been scrolled to the right: Switch(config)# access-list 101 permit tcp 131.108.2.5 255.255.255.0 131.108.1$ The software assumes you have a terminal screen that is 80 columns wide. If you have a width other than that, use the terminal width privileged EXEC command to set the width of your terminal. Use line wrapping with the command history feature to recall and modify previous complex command entries. For information about recalling previous command entries, see the “Editing Commands through Keystrokes” section on page 2-7. Searching and Filtering Output of show and more Commands You can search and filter the output for show and more commands. This is useful when you need to sort through large amounts of output or if you want to exclude output that you do not need to see. Using these commands is optional. To use this functionality, enter a show or more command followed by the pipe character (|), one of the keywords begin, include, or exclude, and an expression that you want to search for or filter out: command | {begin | include | exclude} regular-expression Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output are not displayed, but the lines that contain Output appear. This example shows how to include in the output display only lines where the expression protocol appears: Switch# show interfaces | include protocol Vlan1 is up, line protocol is up Vlan10 is up, line protocol is down GigabitEthernet1/0/1 is up, line protocol is down GigabitEthernet1/0/2 is up, line protocol is up Accessing the CLI You can access the CLI through a console connection, through Telnet, or by using the browser. You manage the switch stack and the stack member interfaces through the stack master. You cannot manage stack members on an individual switch basis. You can connect to the stack master through the console port or the Ethernet management port of one or more stack members. Be careful with using multiple CLI sessions to the stack master. Commands you enter in one session are not displayed in the other sessions. Therefore, it is possible to lose track of the session from which you entered commands. Note We recommend using one CLI session when managing the switch stack. If you want to configure a specific stack member port, you must include the stack member number in the CLI command interface notation. For more information about interface notations, see the “Using Interface Configuration Mode” section on page 11-8.

OL-13270-06 Chapter 2 Using the Command-Line Interface Accessing the CLI To debug a specific stack member, you can access it from the stack master by using the session stack-member-number privileged EXEC command. The stack member number is appended to the system prompt. For example, Switch-2# is the prompt in privileged EXEC mode for stack member 2, and where the system prompt for the stack master is Switch. Only the show and debug commands are available in a CLI session to a specific stack member. Accessing the CLI through a Console Connection or through Telnet Before you can access the CLI, you must connect a terminal or a PC to the switch console or connect a PC to the Ethernet management port and then power on the switch, as described in the hardware installation guide that shipped with your switch. Then, to understand the boot up process and the options available for assigning IP information, see Chapter 3, “Assigning the Switch IP Address and Default Gateway.” If your switch is already configured, you can access the CLI through a local console connection or through a remote Telnet session, but your switch must first be configured for this type of access. For more information, see the “Setting a Telnet Password for a Terminal Line” section on page 6-6. You can use one of these methods to establish a connection with the switch: • Connect the switch console port to a management station or dial-up modem, or connect the Ethernet management port to a PC. For information about connecting to the console or Ethernet management port, see the switch hardware installation guide. • Use any Telnet TCP/IP or encrypted Secure Shell (SSH) package from a remote management station. The switch must have network connectivity with the Telnet or SSH client, and the switch must have an enable secret password configured. For information about configuring the switch for Telnet access, see the “Setting a Telnet Password for a Terminal Line” section on page 6-6. The switch supports up to 16 simultaneous Telnet sessions. Changes made by one Telnet user are reflected in all other Telnet sessions. For information about configuring the switch for SSH, see the “Configuring the Switch for Secure Shell” section on page 6-45. The switch supports up to five simultaneous secure SSH sessions. After you connect through the console port, through the Ethernet management port, through a Telnet session or through an SSH session, the user EXEC prompt appears on the management station.

3-1 Cisco Catalyst Blade Switch 3130 and 3032 for Dell Software Configuration Guide OL-13270-06 3 Assigning the Switch IP Address and Default Gateway This chapter describes how to create the initial switch configuration (for example, assigning the IP address and default gateway information) by using a variety of automatic and manual methods. It also describes how to modify the switch startup configuration. Unless otherwise noted, the term switch refers to a standalone switch and to a switch stack. Note For complete syntax and usage information for the commands used in this chapter, see the command reference for this release and the Cisco IOS IP Command Reference, Volume 1 of 3: Addressing and Services, Release 12.2. This chapter consists of these sections: • Understanding the Boot Process, page 3-2 • Assigning Switch Information, page 3-3 • Checking and Saving the Running Configuration, page 3-17 • Modifying the Startup Configuration, page 3-19 • Scheduling a Reload of the Software Image, page 3-24 Note Information in this chapter about configuring IP addresses and DHCP is specific to IP Version 4 (IPv4). If you plan to enable IP Version 6 (IPv6) forwarding on your switch, see Chapter 40, “Configuring IPv6 Unicast Routing” for information specific to IPv6 address format and configuration. To enable IPv6, the stack or switch must be running the IP services feature set.

OL-13270-06 Chapter 3 Assigning the Switch IP Address and Default Gateway Understanding the Boot Process Understanding the Boot Process To start your switch, you need to follow the procedures in the hardware installation guide for installing and powering on the switch and setting up the initial switch configuration (IP address, subnet mask, default gateway, secret and Telnet passwords, and so forth). The normal boot process involves the operation of the boot loader software, which performs these activities: • Performs low-level CPU initialization. It initializes the CPU registers, which control where physical memory is mapped, its quantity, its speed, and so forth. • Performs power-on self-test (POST) for the CPU subsystem. It tests the CPU DRAM and the portion of the flash device that makes up the flash file system. • Initializes the flash file system on the system board. • Loads a default operating system software image into memory and boots up the switch. The boot loader provides access to the flash file system before the operating system is loaded. Normally, the boot loader is used only to load, uncompress, and start the operating system. After the boot loader gives the operating system control of the CPU, the boot loader is not active until the next system reset or power-on. The boot loader also provides trap-door access into the system if the operating system has problems serious enough that it cannot be used. The trap-door mechanism provides enough access to the system so that if it is necessary, you can format the flash file system, reinstall the operating system software image by using the Xmodem Protocol, recover from a lost or forgotten password, and finally restart the operating system. For more information, see the “Recovering from a Software Failure” section on page 48-2 and the “Recovering from a Lost or Forgotten Password” section on page 48-3. Note You can disable password recovery. For more information, see the “Disabling Password Recovery” section on page 6-5. Before you can assign switch information, make sure you have connected a PC or terminal to the console port or a PC to the Ethernet management port, and make sure you have configured the PC or terminal-emulation software baud rate and character format to match these of the switch console port: • Baud rate default is 9600. • Data bits default is 8. Note If the data bits option is set to 8, set the parity option to none. • Stop bits default is 1. • Parity settings default is none.

OL-13270-06 Chapter 3 Assigning the Switch IP Address and Default Gateway Assigning Switch Information Assigning Switch Information You can assign IP information through the chassis management module GUI or manually. If the switch reboots, it uses the IP address, subnet mask, and gateway in the saved configuration file. The switch stack is managed through a single IP address. The IP address is a system-level setting and is not specific to the stack master or to any other stack member. You can still manage the stack through the same IP address even if you remove the stack master or any other stack member from the stack, provided there is IP connectivity. Note Stack members retain their IP address when you remove them from a switch stack. To avoid a conflict by having two devices with the same IP address in your network, change the IP address of the switch that you removed from the switch stack. Use a DHCP server for centralized control and automatic assignment of IP information after the server is configured. Note If you are using DHCP, do not respond to any of the questions in the setup program until the switch receives the dynamically assigned IP address and reads the configuration file. If you are an experienced user familiar with the switch configuration steps, manually configure the switch. Otherwise, use the setup program described previously. These sections contain this configuration information: • Default Switch Information, page 3-3 • Understanding DHCP-Based Autoconfiguration, page 3-4 • Configuring DHCP-Based Autoconfiguration, page 3-7 • Manually Assigning IP Information, page 3-15 Default Switch Information Table 3-1 shows the default switch information. Table 3-1 Default Switch Information Feature Default Setting DCHP client Disabled. IP address and subnet mask No IP address or subnet mask are defined. Default gateway No default gateway is defined. Enable secret password No password is defined. Hostname The factory-assigned default hostname is Switch. Telnet password No password is defined.

OL-13270-06 Chapter 3 Assigning the Switch IP Address and Default Gateway Assigning Switch Information Understanding DHCP-Based Autoconfiguration DHCP provides configuration information to Internet hosts and internetworking devices. This protocol consists of two components: one for delivering configuration parameters from a DHCP server to a device and a mechanism for allocating network addresses to devices. DHCP is built on a client-server model, in which designated DHCP servers allocate network addresses and deliver configuration parameters to dynamically configured devices. The switch can act as both a DHCP client and a DHCP server. During DHCP-based autoconfiguration, your switch (DHCP client) is automatically configured at startup with IP address information and a configuration file. With DHCP-based autoconfiguration, no DHCP client-side configuration is needed on your switch. However, you need to configure the DHCP server for various lease options associated with IP addresses. If you are using DHCP to relay the configuration file location on the network, you might also need to configure a Trivial File Transfer Protocol (TFTP) server and a Domain Name System (DNS) server. Note We recommend a redundant connection between a switch stack and the DHCP, DNS, and TFTP servers. This is to help ensure that these servers remain accessible in case one of the connected stack members is removed from the switch stack. The DHCP server for your switch can be on the same LAN or on a different LAN than the switch. If the DHCP server is running on a different LAN, you should configure a DHCP relay device between your switch and the DHCP server. A relay device forwards broadcast traffic between two directly connected LANs. A router does not forward broadcast packets, but it forwards packets based on the destination IP address in the received packet. DHCP-based autoconfiguration replaces the BOOTP client functionality on your switch. DHCP Client Request Process When you boot up your switch, the DHCP client is invoked and requests configuration information from a DHCP server when the configuration file is not present on the switch. If the configuration file is present and the configuration includes the ip address dhcp interface configuration command on specific routed interfaces, the DHCP client is invoked and requests the IP address information for those interfaces. Figure 3-1 shows the sequence of messages that are exchanged between the DHCP client and the DHCP server. Figure 3-1 DHCP Client and Server Message Exchange The client, Switch A, broadcasts a DHCPDISCOVER message to locate a DHCP server. The DHCP server offers configuration parameters (such as an IP address, subnet mask, gateway IP address, DNS IP address, a lease for the IP address, and so forth) to the client in a DHCPOFFER unicast message. Switch A DHCPACK (unicast) DHCPREQUEST (broadcast) DHCPOFFER (unicast) DHCPDISCOVER (broadcast) DHCP server 51807

OL-13270-06 Chapter 3 Assigning the Switch IP Address and Default Gateway Assigning Switch Information In a DHCPREQUEST broadcast message, the client returns a formal request for the offered configuration information to the DHCP server. The formal request is broadcast so that all other DHCP servers that received the DHCPDISCOVER broadcast message from the client can reclaim the IP addresses that they offered to the client. The DHCP server confirms that the IP address has been allocated to the client by returning a DHCPACK unicast message to the client. With this message, the client and server are bound, and the client uses configuration information received from the server. The amount of information the switch receives depends on how you configure the DHCP server. For more information, see the “Configuring the TFTP Server” section on page 3-8. If the configuration parameters sent to the client in the DHCPOFFER unicast message are invalid (a configuration error exists), the client returns a DHCPDECLINE broadcast message to the DHCP server. The DHCP server sends the client a DHCPNAK denial broadcast message, which means that the offered configuration parameters have not been assigned, that an error has occurred during the negotiation of the parameters, or that the client has been slow in responding to the DHCPOFFER message (the DHCP server assigned the parameters to another client). A DHCP client might receive offers from multiple DHCP or BOOTP servers and can accept any of the offers; however, the client usually accepts the first offer it receives. The offer from the DHCP server is not a guarantee that the IP address is allocated to the client; however, the server usually reserves the address until the client has had a chance to formally request the address. If the switch accepts replies from a BOOTP server and configures itself, the switch broadcasts, instead of unicasts, TFTP requests to obtain the switch configuration file. The DHCP hostname option allows a group of switches to obtain hostnames and a standard configuration from the central management DHCP server. 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. The configuration files on all clients are identical except for their DHCP-obtained hostnames. 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 hostname option is not included in the packet when you enter the ip address dhcp interface configuration command. In this case, if the client receives the DCHP hostname option from the DHCP interaction while acquiring an IP address for an interface, the client accepts the DHCP hostname option and sets the flag to show that the system now has a hostname configured. Understanding DHCP-based Autoconfiguration and Image Update You can use the DHCP image upgrade features to configure a DHCP server to download both a new image and a new configuration file to one or more switches in a network. This helps ensure that each new switch added to a network receives the same image and configuration. There are two types of DHCP image upgrades: DHCP autoconfiguration and DHCP auto-image update. DHCP Autoconfiguration DHCP autoconfiguration downloads a configuration file to one or more switches in your network from a DHCP server. The downloaded configuration file becomes the running configuration of the switch. It does not over write the bootup configuration saved in the flash, until you reload the switch.

OL-13270-06 Chapter 3 Assigning the Switch IP Address and Default Gateway Assigning Switch Information DHCP Auto-Image Update You can use DHCP auto-image upgrade with DHCP autoconfiguration to download both a configuration and a new image to one or more switches in your network. The switch (or switches) downloading the new configuration and the new image can be blank (or only have a default factory configuration loaded). If the new configuration is downloaded to a switch that already has a configuration, the downloaded configuration is appended to the configuration file stored on the switch. (Any existing configuration is not overwritten by the downloaded one.) Note To enable a DHCP auto-image update on the switch, the TFTP server where the image and configuration files are located must be configured with the correct option 67 (the configuration filename), option 66 (the DHCP server hostname) option 150 (the TFTP server address), and option 125 (description of the file) settings. For procedures to configure the switch as a DHCP server, see the “Configuring DHCP-Based Autoconfiguration” section on page 3-7 and the “Configuring DHCP” section of the “IP addressing and Services” section of the Cisco IOS IP Configuration Guide, Release 12.2. After you install the switch in your network, the auto-image update feature starts. The downloaded configuration file is saved in the running configuration of the switch, and the new image is downloaded and installed on the switch. When you reboot the switch, the configuration is stored in the saved configuration on the switch. Limitations and Restrictions These are the limitations: • The DHCP-based autoconfiguration with a saved configuration process stops if there is not at least one Layer 3 interface in an up state without an assigned IP address in the network. • Unless you configure a timeout, the DHCP-based autoconfiguration with a saved configuration feature tries indefinitely to download an IP address. • The auto-install process stops if a configuration file cannot be downloaded or it the configuration file is corrupted. The configuration file that is downloaded from TFTP is merged with the existing configuration in the running configuration but is not saved in the NVRAM unless you enter the write memory or copy running-configuration startup-configuration privileged EXEC command. Note that if the downloaded configuration is saved to the startup configuration, the feature is not triggered during sub- sequent system restarts.

OL-13270-06 Chapter 3 Assigning the Switch IP Address and Default Gateway Assigning Switch Information Configuring DHCP-Based Autoconfiguration These sections contain this configuration information: • DHCP Server Configuration Guidelines, page 3-7 • Configuring the TFTP Server, page 3-8 • Configuring the DNS, page 3-8 • Configuring the Relay Device, page 3-8 • Obtaining Configuration Files, page 3-9 • Example Configuration, page 3-10 If your DHCP server is a Cisco device, see the “Configuring DHCP” section of the “IP Addressing and Services” section of the Cisco IOS IP Configuration Guide, Release 12.2 for additional information about configuring DHCP. DHCP Server Configuration Guidelines Follow these guidelines if you are configuring a device as a DHCP server: You should configure the DHCP server with reserved leases that are bound to each switch by the switch hardware address. If you want the switch to receive IP address information, you must configure the DHCP server with these lease options: • IP address of the client (required) • Subnet mask of the client (required) • DNS server IP address (optional) • Router IP address (default gateway address to be used by the switch) (required) If you want the switch to receive the configuration file from a TFTP server, you must configure the DHCP server with these lease options: • TFTP server name (required) • Boot filename (the name of the configuration file that the client needs) (recommended) • Hostname (optional) Depending on the settings of the DHCP server, the switch can receive IP address information, the configuration file, or both. If you do not configure the DHCP server with the lease options described previously, it replies to client requests with only those parameters that are configured. If the IP address and the subnet mask are not in the reply, the switch is not configured. If the router IP address or the TFTP server name are not found, the switch might send broadcast, instead of unicast, TFTP requests. Unavailability of other lease options does not affect autoconfiguration. The switch can act as a DHCP server. By default, the Cisco IOS DHCP server and relay agent features are enabled on your switch but are not configured. These features are not operational. If your DHCP server is a Cisco device, for additional information about configuring DHCP, see the “Configuring DHCP” section of the “IP Addressing and Services” section of the Cisco IOS IP Configuration Guide from the Cisco.com page under Documentation > Cisco IOS Software > 12.2 Mainline > Configuration Guides.

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

OL-13270-06 Chapter 3 Assigning the Switch IP Address and Default Gateway Assigning Switch Information For example, in Figure 3-2, configure the router interfaces as follows: On interface 10.0.0.2: router(config-if)# ip helper-address 20.0.0.2 router(config-if)# ip helper-address 20.0.0.3 router(config-if)# ip helper-address 20.0.0.4 On interface 20.0.0.1 router(config-if)# ip helper-address 10.0.0.1 Note If the switch is acting as the relay device, configure the interface as a routed port. For more information, see the “Routed Ports” section on page 11-4 and the “Configuring Layer 3 Interfaces” section on page 11-25. Figure 3-2 Relay Device Used in Autoconfiguration Obtaining Configuration Files Depending on the availability of the IP address and the configuration filename in the DHCP reserved lease, the switch obtains its configuration information in these ways: • The IP address and the configuration filename is reserved for the switch and provided in the DHCP reply (one-file read method). The switch receives its IP address, subnet mask, TFTP server address, and the configuration filename from the DHCP server. The switch sends a unicast message to the TFTP server to retrieve the named configuration file from the base directory of the server and upon receipt, it completes its boot up process. • The IP address and the configuration filename is reserved for the switch, but the TFTP server address is not provided in the DHCP reply (one-file read method). The switch receives its IP address, subnet mask, and the configuration filename from the DHCP server. The switch sends a broadcast message to a TFTP server to retrieve the named configuration file from the base directory of the server, and upon receipt, it completes its boot up process. Switch (DHCP client) Cisco router (Relay) 49068 DHCP server TFTP server DNS server 20.0.0.2 20.0.0.3 20.0.0.1 10.0.0.2 10.0.0.1 20.0.0.4

OL-13270-06 Chapter 3 Assigning the Switch IP Address and Default Gateway Assigning Switch Information • Only the IP address is reserved for the switch and provided in the DHCP reply. The configuration filename is not provided (two-file read method). The switch receives its IP address, subnet mask, and the TFTP server address from the DHCP server. The switch sends a unicast message to the TFTP server to retrieve the network-confg or cisconet.cfg default configuration file. (If the network-confg file cannot be read, the switch reads the cisconet.cfg file.) The default configuration file contains the hostnames-to-IP-address mapping for the switch. The switch fills its host table with the information in the file and obtains its hostname. If the hostname is not found in the file, the switch uses the hostname in the DHCP reply. If the hostname is not specified in the DHCP reply, the switch uses the default Switch as its hostname. After obtaining its hostname from the default configuration file or the DHCP reply, the switch reads the configuration file that has the same name as its hostname (hostname-confg or hostname.cfg, depending on whether network-confg or cisconet.cfg was read earlier) from the TFTP server. If the cisconet.cfg file is read, the filename of the host is truncated to eight characters. If the switch cannot read the network-confg, cisconet.cfg, or the hostname file, it reads the router-confg file. If the switch cannot read the router-confg file, it reads the ciscortr.cfg file. Note The switch broadcasts TFTP server requests if the TFTP server is not obtained from the DHCP replies, if all attempts to read the configuration file through unicast transmissions fail, or if the TFTP server name cannot be resolved to an IP address. Example Configuration Figure 3-3 shows a sample network for retrieving IP information by using DHCP-based autoconfiguration. Figure 3-3 DHCP-Based Autoconfiguration Network Example Table 3-2 shows the configuration of the reserved leases on the DHCP server. Switch 1 00e0.9f1e.2001 Cisco router 111394 Switch 2 00e0.9f1e.2002 Switch 3 00e0.9f1e.2003 DHCP server DNS server TFTP server (tftpserver) 10.0.0.1 10.0.0.10 10.0.0.2 10.0.0.3 Switch 4 00e0.9f1e.2004 Table 3-2 DHCP Server Configuration Switch A Switch B Switch C Switch D Binding key (hardware address) 00e0.9f1e.2001 00e0.9f1e.2002 00e0.9f1e.2003 00e0.9f1e.2004 IP address 10.0.0.21 10.0.0.22 10.0.0.23 10.0.0.24

OL-13270-06 Chapter 3 Assigning the Switch IP Address and Default Gateway Assigning Switch Information DNS Server Configuration The DNS server maps the TFTP server name tftpserver to IP address 10.0.0.3. TFTP Server Configuration (on UNIX) The TFTP server base directory is set to /tftpserver/work/. This directory contains the network-confg file used in the two-file read method. This file contains the hostname to be assigned to the switch based on its IP address. The base directory also contains a configuration file for each switch (switcha-confg, switchb-confg, and so forth) as shown in this display: prompt> cd /tftpserver/work/ prompt> ls network-confg switcha-confg switchb-confg switchc-confg switchd-confg prompt> cat network-confg ip host switcha 10.0.0.21 ip host switchb 10.0.0.22 ip host switchc 10.0.0.23 ip host switchd 10.0.0.24 DHCP Client Configuration No configuration file is present on Switch A through Switch D. Configuration Explanation In Figure 3-3, Switch A reads its configuration file as follows: • It obtains its IP address 10.0.0.21 from the DHCP server. • If no configuration filename is given in the DHCP server reply, Switch A reads the network-confg file from the base directory of the TFTP server. • It adds the contents of the network-confg file to its host table. • It reads its host table by indexing its IP address 10.0.0.21 to its hostname (switcha). • It reads the configuration file that corresponds to its hostname; for example, it reads switch1-confg from the TFTP server. Switches B through D retrieve their configuration files and IP addresses in the same way. Subnet mask 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 Router address 10.0.0.10 10.0.0.10 10.0.0.10 10.0.0.10 DNS server address 10.0.0.2 10.0.0.2 10.0.0.2 10.0.0.2 TFTP server name tftpserver or 10.0.0.3 tftpserver or 10.0.0.3 tftpserver or 10.0.0.3 tftpserver or 10.0.0.3 Boot filename (configuration file) (optional) switcha-confg switchb-confg switchc-confg switchd-confg Hostname (optional) switcha switchb switchc switchd Table 3-2 DHCP Server Configuration (continued) Switch A Switch B Switch C Switch D

OL-13270-06 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. The client switch is configured to download either a new configuration file or a new configuration file and a new image file. Configuring DHCP Autoconfiguration (Only Configuration File) Beginning in privileged EXEC mode, follow these steps to configure DHCP autoconfiguration of the TFTP and DHCP settings on a new switch to download a new configuration file. Command Purpose Step 1 configure terminal Enter global configuration mode. Step 2 ip dhcp poolname Create a name for the DHCP Server address pool, and enter DHCP pool configuration mode. Step 3 bootfile filename Specify the name of the configuration file that is used as a boot image. Step 4 network network-number mask prefix-length Specify the subnet network number and mask of the DHCP address pool. Note The prefix length specifies the number of bits that comprise the address prefix. The prefix is an alternative way of specifying the network mask of the client. The prefix length must be preceded by a forward slash (/). Step 5 default-router address Specify the IP address of the default router for a DHCP client. Step 6 option 150 address Specify the IP address of the TFTP server. Step 7 exit Return to global configuration mode. Step 8 tftp-server flash:filename.text Specify the configuration file on the TFTP server. Step 9 interface interface-id Specify the address of the client that will receive the configuration file. Step 10 no switchport Put the interface into Layer 3 mode. Step 11 ip address address mask Specify the IP address and mask for the interface. Step 12 end Return to privileged EXEC mode. Step 13 copy running-config startup-config (Optional) Save your entries in the configuration file.

OL-13270-06 Chapter 3 Assigning the Switch IP Address and Default Gateway Assigning Switch Information This example shows how to configure a switch as a DHCP server so that it downloads a configuration file: Switch# configure terminal Switch(config)# ip dhcp pool pool1 Switch(dhcp-config)# network 10.10.10.0 255.255.255.0 Switch(dhcp-config)# bootfile config-boot.text Switch(dhcp-config)# default-router 10.10.10.1 Switch(dhcp-config)# option 150 10.10.10.1 Switch(dhcp-config)# exit Switch(config)# tftp-server flash:config-boot.text Switch(config)# interface gigabitethernet1/0/4 Switch(config-if)# no switchport Switch(config-if)# ip address 10.10.10.1 255.255.255.0 Switch(config-if)# end Configuring DHCP Auto-Image Update (Configuration File and Image) Beginning in privileged EXEC mode, follow these steps to configure DHCP autoconfiguration to configure TFTP and DHCP settings on a new switch to download a new image and a new configuration file. Note Before following the steps in this table, you must create a text file (for example, autoinstall_dhcp) that will be uploaded to the switch. In the text file, put the name of the image that you want to download. This image must be a tar and not a bin file. Command Purpose Step 1 configure terminal Enter global configuration mode. Step 2 ip dhcp pool name Create a name for the DHCP server address pool and enter DHCP pool configuration mode. Step 3 bootfile filename Specify the name of the file that is used as a boot image. Step 4 network network-number mask prefix-length Specify the subnet network number and mask of the DHCP address pool. Note The prefix length specifies the number of bits that comprise the address prefix. The prefix is an alternative way of specifying the network mask of the client. The prefix length must be preceded by a forward slash (/). Step 5 default-router address Specify the IP address of the default router for a DHCP client. Step 6 option 150 address Specify the IP address of the TFTP server. Step 7 option 125 hex Specify the path to the text file that describes the path to the image file. Step 8 copy tftp flash filename.txt Upload the text file to the switch. Step 9 copy tftp flash imagename.tar Upload the tarfile for the new image to the switch. Step 10 exit Return to global configuration mode. Step 11 tftp-server flash:config.text Specify the Cisco IOS configuration file on the TFTP server. Step 12 tftp-server flash:imagename.tar Specify the image name on the TFTP server. Step 13 tftp-server flash:filename.txt Specify the text file that contains the name of the image file to download Step 14 interface interface-id Specify the address of the client that will receive the configuration file.

OL-13270-06 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# configure terminal Switch(config)# ip dhcp pool pool1 Switch(dhcp-config)# network 10.10.10.0 255.255.255.0 Switch(dhcp-config)# bootfile config-boot.text Switch(dhcp-config)# default-router 10.10.10.1 Switch(dhcp-config)# option 150 10.10.10.1 Switch(dhcp-config)# option 125 hex 0000.0009.0a05.08661.7574.6f69.6e73.7461.6c6c.5f64.686370 Switch(dhcp-config)# exit Switch(config)# tftp-server flash:config-boot.text Switch(config)# tftp-server flash:cbs31x0-ipservices-mz.122-44.3.SE.tar Switch(config)# tftp-server flash:boot-config.text Switch(config)# tftp-server flash: autoinstall_dhcp Switch(config)# interface gigabitethernet1/0/4 Switch(config-if)# no switchport Switch(config-if)# ip address 10.10.10.1 255.255.255.0 Switch(config-if)# end Configuring the Client Beginning in privileged EXEC mode, follow these steps to configure a switch to download a configuration file and new image from a DHCP server: Step 15 no switchport Put the interface into Layer 3 mode. Step 16 ip address address mask Specify the IP address and mask for the interface. Step 17 end Return to privileged EXEC mode. Step 18 copy running-config startup-config (Optional) Save your entries in the configuration file. Command Purpose Command Purpose Step 1 configure terminal Enter global configuration mode. Step 2 boot host dhcp Enable autoconfiguration with a saved configuration. Step 3 boot host retry timeout timeout-value (Optional) Set the amount of time the system tries to download a configuration file. Note If you do not set a timeout the system will indefinitely try to obtain an IP address from the DHCP server. Step 4 banner config-save ^C warning-message ^C (Optional) Create warning messages to be displayed when you try to save the configuration file to NVRAM. Step 5 end Return to privileged EXEC mode. Step 6 show boot Verify the configuration.

OL-13270-06 Chapter 3 Assigning the Switch IP Address and Default Gateway Assigning Switch Information This example uses a Layer 3 SVI interface on VLAN 99 to enable DHCP-based autoconfiguration with a saved configuration: Switch# configure terminal Switch(conf)# boot host dhcp Switch(conf)# boot host retry timeout 300 Switch(conf)# banner config-save ^C Caution - Saving Configuration File to NVRAM May Cause You to Nolonger Automatically Download Configuration Files at Reboot^C Switch(config)# vlan 99 Switch(config-vlan)# interface vlan 99 Switch(config-if)# no shutdown Switch(config-if)# end Switch# show boot BOOT path-list: Config file: flash:/config.text Private Config file: flash:/private-config.text Enable Break: no Manual Boot: no HELPER path-list: NVRAM/Config file buffer size: 32768 Timeout for Config Download: 300 seconds Config Download via DHCP: enabled (next boot: enabled) Switch# Note You should only configure and enable the Layer 3 interface. Do not assign an IP address or DHCP-based autoconfiguration with a saved configuration. Manually Assigning IP Information Beginning in privileged EXEC mode, follow these steps to manually assign IP information to multiple switched virtual interfaces (SVIs): Note If the switch is running the IP services feature set, you can also manually assign IP information to a port if you first put the port into Layer 3 mode by using the no switchport interface configuration command. Command Purpose Step 1 configure terminal Enter global configuration mode. Step 2 interface vlan vlan-id Enter interface configuration mode, and enter the VLAN to which the IP information is assigned. The range is 1 to 4094. Step 3 ip address dhcp [client-id interface-name] [hostname host-name] Get an IP address for the VLAN interface from the DHCP server. Step 4 ip address ip-address subnet-mask Enter the IP address and subnet mask. Step 5 exit Return to global configuration mode.

OL-13270-06 Chapter 3 Assigning the Switch IP Address and Default Gateway Assigning Switch Information To remove the switch IP address, use the no ip address interface configuration command. If you are removing the address through a Telnet session, your connection to the switch will be lost. To remove the default gateway address, use the no ip default-gateway global configuration command. All VLAN interfaces have assigned MAC addresses that are derived from the base MAC address. The base MAC address is the hardware address that is on the switch label. It also appears when you enter the show version privileged EXEC command. On the first VLAN interface (VLAN 1), the MAC address is the base MAC address + 0 x 40. On the next VLAN interface that you configure, the MAC address is the base MAC address + 0 x 40 +1, and so on for other VLAN interfaces. You can enter the show interfaces vlan vlan-id privileged EXEC command to show the MAC and IP addresses. The MAC addresses that appear in the show interfaces vlan vlan-id command output are not the same as the MAC address that is printed on the switch label (the base MAC address). By default, VLAN 1 is the interface that connects to the management network. When the switch boots up, the DHCP client (switch) requests an IP address from a DHCP server by using the MAC address of VLAN 1. For information on setting the switch system name, protecting access to privileged EXEC commands, and setting time and calendar services, see Chapter 5, “Administering the Switch.” Step 6 ip default-gateway ip-address Enter the IP address of the next-hop router interface that is directly connected to the switch where a default gateway is being configured. The default gateway receives IP packets with unresolved destination IP addresses from the switch. Once the default gateway is configured, the switch has connectivity to the remote networks with which a host needs to communicate. Note When your switch is configured to route with IP, it does not need to have a default gateway set. Step 7 end Return to privileged EXEC mode. Step 8 show interfaces vlan vlan-id Verify the configured IP address. Step 9 show ip redirects Verify the configured default gateway. Step 10 copy running-config startup-config (Optional) Save your entries in the configuration file. Command Purpose