Cisco AVS 3120 Software 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 3120 for HP Software Configuration Guide Cisco IOS Release 12.2(40)EX November 2007 Text Part Number: OL-12247-01

STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. CCVP, the Cisco logo, and Welcome to the Human Network are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networkers, Networking Academy, Network Registrar, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries. All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0711R) 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 3120 for HP Software Configuration Guide © 2007 Cisco Systems, Inc. All rights reserved.

OL-12247-01 C O N T E N T S Preface xliii Audience xliii Purpose xliii Conventions xliii Related Publications xliv C H A P T E R 1 Overview 1-1 Features 1-1 Deployment Features 1-2 Performance Features 1-3 Management Options 1-5 Manageability Features 1-5 Availability and Redundancy Features 1-6 VLAN Features 1-7 Security Features 1-8 QoS and CoS Features 1-10 Layer 3 Features 1-11 Monitoring Features 1-12 Default Settings After Initial Switch Configuration 1-13 Network Configuration Examples 1-16 Design Concepts for Using the Switch 1-16 Small to Medium-Sized Network 1-19 Where to Go Next 1-20 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-4 Understanding no and default Forms of Commands 2-4 Understanding CLI Error Messages 2-5 Using Configuration Logging 2-5 Using Command History 2-6

OL-12247-01 Changing the Command History Buffer Size 2-6 Recalling Commands 2-6 Disabling the Command History Feature 2-7 Using Editing Features 2-7 Enabling and Disabling Editing Features 2-7 Editing Commands through Keystrokes 2-8 Editing Command Lines that Wrap 2-9 Searching and Filtering Output of show and more Commands 2-10 Accessing the CLI 2-10 Accessing the CLI through a Console Connection or through Telnet 2-11 C H A P T E R 3 Assigning the Switch IP Address and Default Gateway 3-1 Understanding the Boot Process 3-1 Assigning Switch Information 3-2 Default Switch Information 3-3 Understanding DHCP-Based Autoconfiguration 3-3 DHCP Client Request Process 3-4 Configuring DHCP-Based Autoconfiguration 3-5 DHCP Server Configuration Guidelines 3-5 Configuring the TFTP Server 3-6 Configuring the DNS 3-6 Configuring the Relay Device 3-7 Obtaining Configuration Files 3-7 Example Configuration 3-8 Manually Assigning IP Information 3-10 Checking and Saving the Running Configuration 3-11 Modifying the Startup Configuration 3-12 Default Boot Configuration 3-12 Automatically Downloading a Configuration File 3-12 Specifying the Filename to Read and Write the System Configuration 3-13 Booting Manually 3-13 Booting a Specific Software Image 3-14 Controlling Environment Variables 3-15 Scheduling a Reload of the Software Image 3-17 Configuring a Scheduled Reload 3-17 Displaying Scheduled Reload Information 3-18

OL-12247-01 C H A P T E R 4 Configuring Cisco IOS CNS Agents 4-1 Understanding Cisco Configuration Engine Software 4-1 Configuration Service 4-2 Event Service 4-3 NameSpace Mapper 4-3 What You Should Know About the CNS IDs and Device Hostnames 4-3 ConfigID 4-3 DeviceID 4-4 Hostname and DeviceID 4-4 Using Hostname, DeviceID, and ConfigID 4-4 Understanding Cisco IOS Agents 4-5 Initial Configuration 4-5 Incremental (Partial) Configuration 4-6 Synchronized Configuration 4-6 Configuring Cisco IOS Agents 4-6 Enabling Automated CNS Configuration 4-6 Enabling the CNS Event Agent 4-8 Enabling the Cisco IOS CNS Agent 4-9 Enabling an Initial Configuration 4-9 Enabling a Partial Configuration 4-13 Displaying CNS Configuration 4-14 C H A P T E R 5 Managing Switch Stacks 5-1 Understanding Switch Stacks 5-1 Switch Stack Membership 5-3 Stack Master Election and Re-Election 5-6 Switch Stack Bridge ID and Router MAC Address 5-8 Stack Member Numbers 5-8 Stack Member Priority Values 5-9 Switch Stack Offline Configuration 5-9 Effects of Adding a Provisioned Switch to a Switch Stack 5-9 Effects of Replacing a Provisioned Switch in a Switch Stack 5-11 Effects of Removing a Provisioned Switch from a Switch Stack 5-11 Hardware Compatibility and SDM Mismatch Mode in Switch Stacks 5-11 Switch Stack Software Compatibility Recommendations 5-11 Stack Protocol Version Compatibility 5-12 Major Version Number Incompatibility Among Switches 5-12

OL-12247-01 Minor Version Number Incompatibility Among Switches 5-12 Understanding Auto-Upgrade and Auto-Advise 5-13 Auto-Upgrade and Auto-Advise Example Messages 5-14 Incompatible Software and Stack Member Image Upgrades 5-16 Switch Stack Configuration Files 5-16 Additional Considerations for System-Wide Configuration on Switch Stacks 5-17 Switch Stack Management Connectivity 5-17 Connectivity to the Switch Stack Through an IP Address 5-18 Connectivity to the Switch Stack Through an SSH Session 5-18 Connectivity to the Switch Stack Through Console Ports or Ethernet Management Ports 5-18 Connectivity to Specific Stack Members 5-18 Switch Stack Configuration Scenarios 5-19 Configuring the Switch Stack 5-21 Default Switch Stack Configuration 5-21 Enabling Persistent MAC Address 5-21 Assigning Stack Member Information 5-23 Assigning a Stack Member Number 5-23 Setting the Stack Member Priority Value 5-23 Provisioning a New Member for a Switch Stack 5-24 Accessing the CLI of a Specific Stack Member 5-25 Displaying Switch Stack Information 5-25 C H A P T E R 6 Administering the Switch 6-1 Managing the System Time and Date 6-1 Understanding the System Clock 6-1 Understanding Network Time Protocol 6-2 Configuring NTP 6-3 Default NTP Configuration 6-4 Configuring NTP Authentication 6-4 Configuring NTP Associations 6-5 Configuring NTP Broadcast Service 6-6 Configuring NTP Access Restrictions 6-8 Configuring the Source IP Address for NTP Packets 6-10 Displaying the NTP Configuration 6-11 Configuring Time and Date Manually 6-11 Setting the System Clock 6-11 Displaying the Time and Date Configuration 6-12 Configuring the Time Zone 6-12 Configuring Summer Time (Daylight Saving Time) 6-13

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

OL-12247-01 Controlling Switch Access with TACACS+ 7-10 Understanding TACACS+ 7-10 TACACS+ Operation 7-12 Configuring TACACS+ 7-12 Default TACACS+ Configuration 7-13 Identifying the TACACS+ Server Host and Setting the Authentication Key 7-13 Configuring TACACS+ Login Authentication 7-14 Configuring TACACS+ Authorization for Privileged EXEC Access and Network Services 7-16 Starting TACACS+ Accounting 7-17 Displaying the TACACS+ Configuration 7-17 Controlling Switch Access with RADIUS 7-17 Understanding RADIUS 7-18 RADIUS Operation 7-19 Configuring RADIUS 7-20 Default RADIUS Configuration 7-20 Identifying the RADIUS Server Host 7-20 Configuring RADIUS Login Authentication 7-23 Defining AAA Server Groups 7-25 Configuring RADIUS Authorization for User Privileged Access and Network Services 7-27 Starting RADIUS Accounting 7-28 Configuring Settings for All RADIUS Servers 7-29 Configuring the Switch to Use Vendor-Specific RADIUS Attributes 7-29 Configuring the Switch for Vendor-Proprietary RADIUS Server Communication 7-30 Displaying the RADIUS Configuration 7-31 Controlling Switch Access with Kerberos 7-31 Understanding Kerberos 7-32 Kerberos Operation 7-34 Authenticating to a Boundary Switch 7-34 Obtaining a TGT from a KDC 7-35 Authenticating to Network Services 7-35 Configuring Kerberos 7-35 Configuring the Switch for Local Authentication and Authorization 7-36 Configuring the Switch for Secure Shell 7-37 Understanding SSH 7-38 SSH Servers, Integrated Clients, and Supported Versions 7-38 Limitations 7-39

OL-12247-01 Configuring SSH 7-39 Configuration Guidelines 7-39 Setting Up the Switch to Run SSH 7-40 Configuring the SSH Server 7-41 Displaying the SSH Configuration and Status 7-42 Configuring the Switch for Secure Socket Layer HTTP 7-42 Understanding Secure HTTP Servers and Clients 7-42 Certificate Authority Trustpoints 7-43 CipherSuites 7-44 Configuring Secure HTTP Servers and Clients 7-45 Default SSL Configuration 7-45 SSL Configuration Guidelines 7-45 Configuring a CA Trustpoint 7-45 Configuring the Secure HTTP Server 7-46 Configuring the Secure HTTP Client 7-48 Displaying Secure HTTP Server and Client Status 7-49 Configuring the Switch for Secure Copy Protocol 7-49 Information About Secure Copy 7-49 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-1 Device Roles 9-2 Authentication Process 9-3 Authentication Initiation and Message Exchange 9-5 Ports in Authorized and Unauthorized States 9-7 IEEE 802.1x Authentication and Switch Stacks 9-7 IEEE 802.1x Host Mode 9-8 IEEE 802.1x Accounting 9-9 IEEE 802.1x Accounting Attribute-Value Pairs 9-9

OL-12247-01 Using IEEE 802.1x Authentication with VLAN Assignment 9-10 Using IEEE 802.1x Authentication with Per-User ACLs 9-12 Using IEEE 802.1x Authentication with Guest VLAN 9-13 Using IEEE 802.1x Authentication with Restricted VLAN 9-14 Using IEEE 802.1x Authentication with Inaccessible Authentication Bypass 9-15 Using IEEE 802.1x Authentication with Voice VLAN Ports 9-16 Using IEEE 802.1x Authentication with Port Security 9-17 Using IEEE 802.1x Authentication with Wake-on-LAN 9-18 Using IEEE 802.1x Authentication with MAC Authentication Bypass 9-18 Network Admission Control Layer 2 IEEE 802.1x Validation 9-20 Using Multidomain Authentication 9-20 Using Web Authentication 9-21 Web Authentication with Automatic MAC Check 9-22 Configuring IEEE 802.1x Authentication 9-22 Default IEEE 802.1x Authentication Configuration 9-23 IEEE 802.1x Authentication Configuration Guidelines 9-24 IEEE 802.1x Authentication 9-24 VLAN Assignment, Guest VLAN, Restricted VLAN, and Inaccessible Authentication Bypass 9-25 MAC Authentication Bypass 9-26 Configuring IEEE 802.1x Authentication 9-26 Configuring the Switch-to-RADIUS-Server Communication 9-28 Configuring the Host Mode 9-29 Configuring Periodic Re-Authentication 9-30 Manually Re-Authenticating a Client Connected to a Port 9-30 Changing the Quiet Period 9-31 Changing the Switch-to-Client Retransmission Time 9-31 Setting the Switch-to-Client Frame-Retransmission Number 9-32 Setting the Re-Authentication Number 9-33 Configuring IEEE 802.1x Accounting 9-33 Configuring a Guest VLAN 9-34 Configuring a Restricted VLAN 9-35 Configuring the Inaccessible Authentication Bypass Feature 9-37 Configuring IEEE 802.1x Authentication with WoL 9-39 Configuring MAC Authentication Bypass 9-40 Configuring NAC Layer 2 IEEE 802.1x Validation 9-41 Configuring Web Authentication 9-42 Disabling IEEE 802.1x Authentication on the Port 9-44 Resetting the IEEE 802.1x Authentication Configuration to the Default Values 9-45 Displaying IEEE 802.1x Statistics and Status 9-45

OL-12247-01 C H A P T E R 10 Configuring Interface Characteristics 10-1 Understanding Interface Types 10-1 Port-Based VLANs 10-2 Switch Ports 10-2 Access Ports 10-3 Trunk Ports 10-3 Tunnel Ports 10-4 Routed Ports 10-4 Switch Virtual Interfaces 10-5 EtherChannel Port Groups 10-5 10-Gigabit Ethernet Interfaces 10-6 Connecting Interfaces 10-6 Using Interface Configuration Mode 10-7 Procedures for Configuring Interfaces 10-8 Configuring a Range of Interfaces 10-9 Configuring and Using Interface Range Macros 10-10 Using the Internal Ethernet Management Port 10-12 Understanding the Internal Ethernet Management Port 10-12 Supported Features on the Ethernet Management Port 10-14 Layer 3 Routing Configuration Guidelines 10-14 Monitoring the Ethernet Management Port 10-15 TFTP and the Ethernet Management Port 10-15 Configuring Ethernet Interfaces 10-15 Default Ethernet Interface Configuration 10-16 Configuring Interface Speed and Duplex Mode 10-17 Speed and Duplex Configuration Guidelines 10-17 Setting the Interface Speed and Duplex Parameters 10-18 Configuring IEEE 802.3x Flow Control 10-19 Configuring Auto-MDIX on an Interface 10-20 Adding a Description for an Interface 10-21 Configuring Layer 3 Interfaces 10-21 Configuring the System MTU 10-23 Monitoring and Maintaining the Interfaces 10-25 Monitoring Interface Status 10-25 Clearing and Resetting Interfaces and Counters 10-26 Shutting Down and Restarting the Interface 10-26

OL-12247-01 C H A P T E R 11 Configuring Smartports Macros 11-1 Understanding Smartports Macros 11-1 Configuring Smartports Macros 11-2 Default Smartports Macro Configuration 11-2 Smartports Macro Configuration Guidelines 11-3 Creating Smartports Macros 11-4 Applying Smartports Macros 11-5 Applying Cisco-Default Smartports Macros 11-6 Displaying Smartports Macros 11-8 C H A P T E R 12 Configuring VLANs 12-1 Understanding VLANs 12-1 Supported VLANs 12-2 VLAN Port Membership Modes 12-3 Configuring Normal-Range VLANs 12-4 Token Ring VLANs 12-6 Normal-Range VLAN Configuration Guidelines 12-6 VLAN Configuration Mode Options 12-7 VLAN Configuration in config-vlan Mode 12-7 VLAN Configuration in VLAN Database Configuration Mode 12-7 Saving VLAN Configuration 12-7 Default Ethernet VLAN Configuration 12-8 Creating or Modifying an Ethernet VLAN 12-9 Deleting a VLAN 12-10 Assigning Static-Access Ports to a VLAN 12-11 Configuring Extended-Range VLANs 12-12 Default VLAN Configuration 12-12 Extended-Range VLAN Configuration Guidelines 12-13 Creating an Extended-Range VLAN 12-14 Creating an Extended-Range VLAN with an Internal VLAN ID 12-15 Displaying VLANs 12-16 Configuring VLAN Trunks 12-16 Trunking Overview 12-16 Encapsulation Types 12-19 IEEE 802.1Q Configuration Considerations 12-19 Default Layer 2 Ethernet Interface VLAN Configuration 12-20

OL-12247-01 Configuring an Ethernet Interface as a Trunk Port 12-20 Interaction with Other Features 12-20 Configuring a Trunk Port 12-21 Defining the Allowed VLANs on a Trunk 12-22 Changing the Pruning-Eligible List 12-23 Configuring the Native VLAN for Untagged Traffic 12-24 Configuring Trunk Ports for Load Sharing 12-24 Load Sharing Using STP Port Priorities 12-25 Load Sharing Using STP Path Cost 12-27 Configuring VMPS 12-28 Understanding VMPS 12-28 Dynamic-Access Port VLAN Membership 12-29 Default VMPS Client Configuration 12-30 VMPS Configuration Guidelines 12-30 Configuring the VMPS Client 12-30 Entering the IP Address of the VMPS 12-31 Configuring Dynamic-Access Ports on VMPS Clients 12-31 Reconfirming VLAN Memberships 12-32 Changing the Reconfirmation Interval 12-32 Changing the Retry Count 12-33 Monitoring the VMPS 12-33 Troubleshooting Dynamic-Access Port VLAN Membership 12-34 VMPS Configuration Example 12-34 C H A P T E R 13 Configuring VTP 13-1 Understanding VTP 13-1 The VTP Domain 13-2 VTP Modes 13-3 VTP Advertisements 13-3 VTP Version 2 13-4 VTP Pruning 13-4 VTP and Switch Stacks 13-6 Configuring VTP 13-6 Default VTP Configuration 13-7 VTP Configuration Options 13-7 VTP Configuration in Global Configuration Mode 13-7 VTP Configuration in VLAN Database Configuration Mode 13-8

OL-12247-01 VTP Configuration Guidelines 13-8 Domain Names 13-8 Passwords 13-8 VTP Version 13-9 Configuration Requirements 13-9 Configuring a VTP Server 13-9 Configuring a VTP Client 13-11 Disabling VTP (VTP Transparent Mode) 13-12 Enabling VTP Version 2 13-13 Enabling VTP Pruning 13-14 Adding a VTP Client Switch to a VTP Domain 13-14 Monitoring VTP 13-16 C H A P T E R 14 Configuring Voice VLAN 14-1 Understanding Voice VLAN 14-1 Cisco IP Phone Voice Traffic 14-2 Cisco IP Phone Data Traffic 14-2 Configuring Voice VLAN 14-3 Default Voice VLAN Configuration 14-3 Voice VLAN Configuration Guidelines 14-3 Configuring a Port Connected to a Cisco 7960 IP Phone 14-4 Configuring Cisco IP Phone Voice Traffic 14-5 Configuring the Priority of Incoming Data Frames 14-6 Displaying Voice VLAN 14-7 C H A P T E R 15 Configuring Private VLANs 15-1 Understanding Private VLANs 15-1 IP Addressing Scheme with Private VLANs 15-3 Private VLANs across Multiple Switches 15-4 Private-VLAN Interaction with Other Features 15-4 Private VLANs and Unicast, Broadcast, and Multicast Traffic 15-5 Private VLANs and SVIs 15-5 Private VLANs and Switch Stacks 15-5 Configuring Private VLANs 15-6 Tasks for Configuring Private VLANs 15-6 Default Private-VLAN Configuration 15-6

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

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

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

OL-12247-01 How CSUF Works 19-6 Events that Cause Fast Convergence 19-7 Understanding BackboneFast 19-7 Understanding EtherChannel Guard 19-10 Understanding Root Guard 19-10 Understanding Loop Guard 19-11 Configuring Optional Spanning-Tree Features 19-11 Default Optional Spanning-Tree Configuration 19-12 Optional Spanning-Tree Configuration Guidelines 19-12 Enabling Port Fast 19-12 Enabling BPDU Guard 19-13 Enabling BPDU Filtering 19-14 Enabling UplinkFast for Use with Redundant Links 19-15 Enabling Cross-Stack UplinkFast 19-16 Enabling BackboneFast 19-16 Enabling EtherChannel Guard 19-17 Enabling Root Guard 19-18 Enabling Loop Guard 19-18 Displaying the Spanning-Tree Status 19-19 C H A P T E R 20 Configuring Flex Links and the MAC Address-Table Move Update Feature 20-1 Understanding Flex Links and the MAC Address-Table Move Update 20-1 Flex Links 20-1 VLAN Flex Link Load Balancing and Support 20-2 MAC Address-Table Move Update 20-3 Configuring Flex Links and MAC Address-Table Move Update 20-5 Configuration Guidelines 20-5 Default Configuration 20-5 Configuring Flex Links and MAC Address-Table Move Update 20-6 Configuring Flex Links 20-6 Configuring VLAN Load Balancing on Flex Links 20-8 Configuring the MAC Address-Table Move Update Feature 20-9 Monitoring Flex Links and the MAC Address-Table Move Update 20-11 C H A P T E R 21 Configuring DHCP Features and IP Source Guard 21-1 Understanding DHCP Features 21-1 DHCP Server 21-2 DHCP Relay Agent 21-2 DHCP Snooping 21-2

OL-12247-01 Option-82 Data Insertion 21-3 Cisco IOS DHCP Server Database 21-6 DHCP Snooping Binding Database 21-6 DHCP Snooping and Switch Stacks 21-8 Configuring DHCP Features 21-8 Default DHCP Configuration 21-8 DHCP Snooping Configuration Guidelines 21-9 Configuring the DHCP Server 21-10 DHCP Server and Switch Stacks 21-10 Configuring the DHCP Relay Agent 21-11 Specifying the Packet Forwarding Address 21-11 Enabling DHCP Snooping and Option 82 21-12 Enabling DHCP Snooping on Private VLANs 21-14 Enabling the Cisco IOS DHCP Server Database 21-14 Enabling the DHCP Snooping Binding Database Agent 21-14 Displaying DHCP Snooping Information 21-15 Understanding IP Source Guard 21-16 Source IP Address Filtering 21-16 Source IP and MAC Address Filtering 21-17 Configuring IP Source Guard 21-17 Default IP Source Guard Configuration 21-17 IP Source Guard Configuration Guidelines 21-17 Enabling IP Source Guard 21-18 Displaying IP Source Guard Information 21-19 C H A P T E R 22 Configuring Dynamic ARP Inspection 22-1 Understanding Dynamic ARP Inspection 22-1 Interface Trust States and Network Security 22-3 Rate Limiting of ARP Packets 22-4 Relative Priority of ARP ACLs and DHCP Snooping Entries 22-4 Logging of Dropped Packets 22-5 Configuring Dynamic ARP Inspection 22-5 Default Dynamic ARP Inspection Configuration 22-5 Dynamic ARP Inspection Configuration Guidelines 22-6 Configuring Dynamic ARP Inspection in DHCP Environments 22-7 Configuring ARP ACLs for Non-DHCP Environments 22-8 Limiting the Rate of Incoming ARP Packets 22-11 Performing Validation Checks 22-12 Configuring the Log Buffer 22-13

OL-12247-01 Displaying Dynamic ARP Inspection Information 22-15 C H A P T E R 23 Configuring IGMP Snooping and MVR 23-1 Understanding IGMP Snooping 23-2 IGMP Versions 23-3 Joining a Multicast Group 23-3 Leaving a Multicast Group 23-5 Immediate Leave 23-6 IGMP Configurable-Leave Timer 23-6 IGMP Report Suppression 23-6 IGMP Snooping and Switch Stacks 23-7 Configuring IGMP Snooping 23-7 Default IGMP Snooping Configuration 23-7 Enabling or Disabling IGMP Snooping 23-8 Setting the Snooping Method 23-9 Configuring a Multicast Router Port 23-10 Configuring a Blade Server Statically to Join a Group 23-10 Enabling IGMP Immediate Leave 23-11 Configuring the IGMP Leave Timer 23-12 Configuring TCN-Related Commands 23-12 Controlling the Multicast Flooding Time After a TCN Event 23-13 Recovering from Flood Mode 23-13 Disabling Multicast Flooding During a TCN Event 23-14 Configuring the IGMP Snooping Querier 23-14 Disabling IGMP Report Suppression 23-16 Displaying IGMP Snooping Information 23-16 Understanding Multicast VLAN Registration 23-18 Using MVR in a Multicast Television Application 23-19 Configuring MVR 23-20 Default MVR Configuration 23-20 MVR Configuration Guidelines and Limitations 23-20 Configuring MVR Global Parameters 23-21 Configuring MVR Interfaces 23-22 Displaying MVR Information 23-23 Configuring IGMP Filtering and Throttling 23-24 Default IGMP Filtering and Throttling Configuration 23-25 Configuring IGMP Profiles 23-25 Applying IGMP Profiles 23-26

OL-12247-01 Setting the Maximum Number of IGMP Groups 23-27 Configuring the IGMP Throttling Action 23-27 Displaying IGMP Filtering and Throttling Configuration 23-29 C H A P T E R 24 Configuring IPv6 MLD Snooping 24-1 Understanding MLD Snooping 24-1 MLD Messages 24-3 MLD Queries 24-3 Multicast Client Aging Robustness 24-3 Multicast Router Discovery 24-4 MLD Reports 24-4 MLD Done Messages and Immediate-Leave 24-4 Topology Change Notification Processing 24-5 MLD Snooping in Switch Stacks 24-5 Configuring IPv6 MLD Snooping 24-5 Default MLD Snooping Configuration 24-6 MLD Snooping Configuration Guidelines 24-6 Enabling or Disabling MLD Snooping 24-7 Configuring a Static Multicast Group 24-8 Configuring a Multicast Router Port 24-8 Enabling MLD Immediate Leave 24-9 Configuring MLD Snooping Queries 24-10 Disabling MLD Listener Message Suppression 24-11 Displaying MLD Snooping Information 24-11 C H A P T E R 25 Configuring Port-Based Traffic Control 25-1 Configuring Storm Control 25-1 Understanding Storm Control 25-1 Default Storm Control Configuration 25-3 Configuring Storm Control and Threshold Levels 25-3 Configuring Protected Ports 25-5 Default Protected Port Configuration 25-5 Protected Port Configuration Guidelines 25-6 Configuring a Protected Port 25-6 Configuring Port Blocking 25-6 Default Port Blocking Configuration 25-7 Blocking Flooded Traffic on an Interface 25-7

OL-12247-01 Configuring Port Security 25-7 Understanding Port Security 25-8 Secure MAC Addresses 25-8 Security Violations 25-9 Default Port Security Configuration 25-10 Port Security Configuration Guidelines 25-10 Enabling and Configuring Port Security 25-12 Enabling and Configuring Port Security Aging 25-16 Port Security and Switch Stacks 25-17 Port Security and Private VLANs 25-17 Displaying Port-Based Traffic Control Settings 25-18 C H A P T E R 26 Configuring CDP 26-1 Understanding CDP 26-1 CDP and Switch Stacks 26-2 Configuring CDP 26-2 Default CDP Configuration 26-2 Configuring the CDP Characteristics 26-2 Disabling and Enabling CDP 26-3 Disabling and Enabling CDP on an Interface 26-4 Monitoring and Maintaining CDP 26-5 C H A P T E R 27 Configuring LLDP and LLDP-MED 27-1 Understanding LLDP and LLDP-MED 27-1 Understanding LLDP 27-1 Understanding LLDP-MED 27-2 Configuring LLDP and LLDP-MED 27-3 Default LLDP Configuration 27-3 Configuring LLDP Characteristics 27-4 Disabling and Enabling LLDP Globally 27-5 Disabling and Enabling LLDP on an Interface 27-5 Configuring LLDP-MED TLVs 27-6 Monitoring and Maintaining LLDP and LLDP-MED 27-7 C H A P T E R 28 Configuring UDLD 28-1 Understanding UDLD 28-1 Modes of Operation 28-1 Methods to Detect Unidirectional Links 28-2

OL-12247-01 Configuring UDLD 28-3 Default UDLD Configuration 28-4 Configuration Guidelines 28-4 Enabling UDLD Globally 28-5 Enabling UDLD on an Interface 28-6 Resetting an Interface Disabled by UDLD 28-6 Displaying UDLD Status 28-7 C H A P T E R 29 Configuring SPAN and RSPAN 29-1 Understanding SPAN and RSPAN 29-1 Local SPAN 29-2 Remote SPAN 29-3 SPAN and RSPAN Concepts and Terminology 29-4 SPAN Sessions 29-4 Monitored Traffic 29-6 Source Ports 29-7 Source VLANs 29-7 VLAN Filtering 29-8 Destination Port 29-8 RSPAN VLAN 29-9 SPAN and RSPAN Interaction with Other Features 29-9 SPAN and RSPAN and Switch Stacks 29-11 Configuring SPAN and RSPAN 29-11 Default SPAN and RSPAN Configuration 29-11 Configuring Local SPAN 29-11 SPAN Configuration Guidelines 29-12 Creating a Local SPAN Session 29-13 Creating a Local SPAN Session and Configuring Incoming Traffic 29-15 Specifying VLANs to Filter 29-16 Configuring RSPAN 29-17 RSPAN Configuration Guidelines 29-17 Configuring a VLAN as an RSPAN VLAN 29-18 Creating an RSPAN Source Session 29-19 Specifying VLANs to Filter 29-20 Creating an RSPAN Destination Session 29-21 Creating an RSPAN Destination Session and Configuring Incoming Traffic 29-22 Displaying SPAN and RSPAN Status 29-24

OL-12247-01 C H A P T E R 30 Configuring RMON 30-1 Understanding RMON 30-1 Configuring RMON 30-2 Default RMON Configuration 30-3 Configuring RMON Alarms and Events 30-3 Collecting Group History Statistics on an Interface 30-5 Collecting Group Ethernet Statistics on an Interface 30-5 Displaying RMON Status 30-6 C H A P T E R 31 Configuring System Message Logging 31-1 Understanding System Message Logging 31-1 Configuring System Message Logging 31-2 System Log Message Format 31-2 Default System Message Logging Configuration 31-4 Disabling Message Logging 31-4 Setting the Message Display Destination Device 31-5 Synchronizing Log Messages 31-6 Enabling and Disabling Time Stamps on Log Messages 31-8 Enabling and Disabling Sequence Numbers in Log Messages 31-8 Defining the Message Severity Level 31-9 Limiting Syslog Messages Sent to the History Table and to SNMP 31-10 Enabling the Configuration-Change Logger 31-11 Configuring UNIX Syslog Servers 31-12 Logging Messages to a UNIX Syslog Daemon 31-12 Configuring the UNIX System Logging Facility 31-13 Displaying the Logging Configuration 31-14 C H A P T E R 32 Configuring SNMP 32-1 Understanding SNMP 32-1 SNMP Versions 32-2 SNMP Manager Functions 32-3 SNMP Agent Functions 32-4 SNMP Community Strings 32-4 Using SNMP to Access MIB Variables 32-4 SNMP Notifications 32-5 SNMP ifIndex MIB Object Values 32-5

OL-12247-01 Configuring SNMP 32-6 Default SNMP Configuration 32-6 SNMP Configuration Guidelines 32-6 Disabling the SNMP Agent 32-7 Configuring Community Strings 32-8 Configuring SNMP Groups and Users 32-9 Configuring SNMP Notifications 32-11 Setting the Agent Contact and Location Information 32-15 Limiting TFTP Servers Used Through SNMP 32-15 SNMP Examples 32-16 Displaying SNMP Status 32-17 C H A P T E R 33 Configuring Embedded Event Manager 33-1 Understanding Embedded Event Manager 33-1 Event Detectors 33-2 Embedded Event Manager Actions 33-4 Embedded Event Manager Policies 33-4 Embedded Event Manager Environment Variables 33-4 Configuring Embedded Event Manager 33-5 Registering and Defining an Embedded Event Manager Applet 33-5 Registering and Defining an Embedded Event Manager TCL Script 33-6 Displaying Embedded Event Manager Information 33-7 C H A P T E R 34 Configuring Network Security with ACLs 34-1 Understanding ACLs 34-1 Supported ACLs 34-2 Port ACLs 34-3 Router ACLs 34-4 VLAN Maps 34-5 Handling Fragmented and Unfragmented Traffic 34-5 ACLs and Switch Stacks 34-6 Configuring IPv4 ACLs 34-7 Creating Standard and Extended IPv4 ACLs 34-8 Access List Numbers 34-8 ACL Logging 34-9 Creating a Numbered Standard ACL 34-10 Creating a Numbered Extended ACL 34-11 Resequencing ACEs in an ACL 34-15 Creating Named Standard and Extended ACLs 34-15

OL-12247-01 Using Time Ranges with ACLs 34-17 Including Comments in ACLs 34-19 Applying an IPv4 ACL to a Terminal Line 34-19 Applying an IPv4 ACL to an Interface 34-20 Hardware and Software Treatment of IP ACLs 34-22 IPv4 ACL Configuration Examples 34-22 Numbered ACLs 34-24 Extended ACLs 34-24 Named ACLs 34-25 Time Range Applied to an IP ACL 34-25 Commented IP ACL Entries 34-25 ACL Logging 34-26 Creating Named MAC Extended ACLs 34-27 Applying a MAC ACL to a Layer 2 Interface 34-28 Configuring VLAN Maps 34-29 VLAN Map Configuration Guidelines 34-30 Creating a VLAN Map 34-31 Examples of ACLs and VLAN Maps 34-32 Applying a VLAN Map to a VLAN 34-34 Using VLAN Maps in Your Network 34-34 Denying Access to a Server on Anothera VLAN 34-34 Using VLAN Maps with Router ACLs 34-35 VLAN Maps and Router ACL Configuration Guidelines 34-36 Examples of Router ACLs and VLAN Maps Applied to VLANs 34-37 ACLs and Switched Packets 34-37 ACLs and Bridged Packets 34-37 ACLs and Routed Packets 34-38 ACLs and Multicast Packets 34-39 Displaying IPv4 ACL Configuration 34-39 C H A P T E R 35 Configuring IPv6 ACLs 35-1 Understanding IPv6 ACLs 35-2 Supported ACL Features 35-3 IPv6 ACL Limitations 35-3 IPv6 ACLs and Switch Stacks 35-3 Configuring IPv6 ACLs 35-4 Default IPv6 ACL Configuration 35-4 Interaction with Other Features and Switches 35-4

OL-12247-01 Creating IPv6 ACLs 35-5 Applying an IPv6 ACL to an Interface 35-8 Displaying IPv6 ACLs 35-9 C H A P T E R 36 Configuring QoS 36-1 Understanding QoS 36-2 Basic QoS Model 36-3 Classification 36-5 Classification Based on QoS ACLs 36-7 Classification Based on Class Maps and Policy Maps 36-7 Policing and Marking 36-8 Policing on Physical Ports 36-9 Policing on SVIs 36-10 Mapping Tables 36-12 Queueing and Scheduling Overview 36-13 Weighted Tail Drop 36-13 SRR Shaping and Sharing 36-14 Queueing and Scheduling on Ingress Queues 36-15 Queueing and Scheduling on Egress Queues 36-17 Packet Modification 36-19 Configuring Auto-QoS 36-20 Generated Auto-QoS Configuration 36-21 Effects of Auto-QoS on the Configuration 36-25 Auto-QoS Configuration Guidelines 36-25 Enabling Auto-QoS for VoIP 36-26 Auto-QoS Configuration Example 36-27 Displaying Auto-QoS Information 36-29 Configuring Standard QoS 36-29 Default Standard QoS Configuration 36-30 Default Ingress Queue Configuration 36-30 Default Egress Queue Configuration 36-31 Default Mapping Table Configuration 36-32 Standard QoS Configuration Guidelines 36-32 QoS ACL Guidelines 36-32 Applying QoS on Interfaces 36-32 Policing Guidelines 36-33 General QoS Guidelines 36-33 Enabling QoS Globally 36-34 Enabling VLAN-Based QoS on Physical Ports 36-34

OL-12247-01 Configuring Classification Using Port Trust States 36-35 Configuring the Trust State on Ports within the QoS Domain 36-35 Configuring the CoS Value for an Interface 36-37 Configuring a Trusted Boundary to Ensure Port Security 36-38 Enabling DSCP Transparency Mode 36-39 Configuring the DSCP Trust State on a Port Bordering Another QoS Domain 36-40 Configuring a QoS Policy 36-42 Classifying Traffic by Using ACLs 36-43 Classifying Traffic by Using Class Maps 36-46 Classifying, Policing, and Marking Traffic on Physical Ports by Using Policy Maps 36-48 Classifying, Policing, and Marking Traffic on SVIs by Using Hierarchical Policy Maps 36-52 Classifying, Policing, and Marking Traffic by Using Aggregate Policers 36-58 Configuring DSCP Maps 36-60 Configuring the CoS-to-DSCP Map 36-60 Configuring the IP-Precedence-to-DSCP Map 36-61 Configuring the Policed-DSCP Map 36-62 Configuring the DSCP-to-CoS Map 36-63 Configuring the DSCP-to-DSCP-Mutation Map 36-64 Configuring Ingress Queue Characteristics 36-66 Mapping DSCP or CoS Values to an Ingress Queue and Setting WTD Thresholds 36-67 Allocating Buffer Space Between the Ingress Queues 36-68 Allocating Bandwidth Between the Ingress Queues 36-68 Configuring the Ingress Priority Queue 36-69 Configuring Egress Queue Characteristics 36-70 Configuration Guidelines 36-71 Allocating Buffer Space to and Setting WTD Thresholds for an Egress Queue-Set 36-71 Mapping DSCP or CoS Values to an Egress Queue and to a Threshold ID 36-73 Configuring SRR Shaped Weights on Egress Queues 36-75 Configuring SRR Shared Weights on Egress Queues 36-76 Configuring the Egress Expedite Queue 36-76 Limiting the Bandwidth on an Egress Interface 36-77 Displaying Standard QoS Information 36-78 C H A P T E R 37 Configuring EtherChannels and Link-State Tracking 37-1 Understanding EtherChannels 37-1 EtherChannel Overview 37-2 Port-Channel Interfaces 37-4

OL-12247-01 Port Aggregation Protocol 37-5 PAgP Modes 37-5 PAgP Interaction with Other Features 37-6 Link Aggregation Control Protocol 37-6 LACP Modes 37-6 LACP Interaction with Other Features 37-7 EtherChannel On Mode 37-7 Load-Balancing and Forwarding Methods 37-7 EtherChannel and Switch Stacks 37-9 Configuring EtherChannels 37-10 Default EtherChannel Configuration 37-10 EtherChannel Configuration Guidelines 37-11 Configuring Layer 2 EtherChannels 37-12 Configuring Layer 3 EtherChannels 37-14 Creating Port-Channel Logical Interfaces 37-14 Configuring the Physical Interfaces 37-15 Configuring EtherChannel Load-Balancing 37-17 Configuring the PAgP Learn Method and Priority 37-18 Configuring LACP Hot-Standby Ports 37-19 Configuring the LACP System Priority 37-20 Configuring the LACP Port Priority 37-21 Displaying EtherChannel, PAgP, and LACP Status 37-22 Understanding Link-State Tracking 37-22 Configuring Link-State Tracking 37-24 Default Link-State Tracking Configuration 37-24 Link-State Tracking Configuration Guidelines 37-24 Configuring Link-State Tracking 37-25 Displaying Link-State Tracking Status 37-26 C H A P T E R 38 Configuring IP Unicast Routing 38-1 Understanding IP Routing 38-2 Types of Routing 38-2 IP Routing and Switch Stacks 38-3 Steps for Configuring Routing 38-5 Configuring IP Addressing 38-5 Default Addressing Configuration 38-6 Assigning IP Addresses to Network Interfaces 38-7 Use of Subnet Zero 38-7 Classless Routing 38-8

OL-12247-01 Configuring Address Resolution Methods 38-9 Define a Static ARP Cache 38-10 Set ARP Encapsulation 38-11 Enable Proxy ARP 38-12 Routing Assistance When IP Routing is Disabled 38-12 Proxy ARP 38-12 Default Gateway 38-12 ICMP Router Discovery Protocol (IRDP) 38-13 Configuring Broadcast Packet Handling 38-14 Enabling Directed Broadcast-to-Physical Broadcast Translation 38-15 Forwarding UDP Broadcast Packets and Protocols 38-16 Establishing an IP Broadcast Address 38-17 Flooding IP Broadcasts 38-17 Monitoring and Maintaining IP Addressing 38-18 Enabling IP Unicast Routing 38-19 Configuring RIP 38-20 Default RIP Configuration 38-21 Configuring Basic RIP Parameters 38-21 Configuring RIP Authentication 38-23 Configuring Summary Addresses and Split Horizon 38-23 Configuring Split Horizon 38-25 Configuring OSPF 38-25 Default OSPF Configuration 38-26 OSPF Nonstop Forwarding 38-28 Configuring Basic OSPF Parameters 38-29 Configuring OSPF Interfaces 38-30 Configuring OSPF Area Parameters 38-31 Configuring Other OSPF Parameters 38-32 Changing LSA Group Pacing 38-35 Configuring a Loopback Interface 38-35 Monitoring OSPF 38-36 Configuring EIGRP 38-36 Default EIGRP Configuration 38-38 EIGRP Nonstop Forwarding 38-39 Configuring Basic EIGRP Parameters 38-40 Configuring EIGRP Interfaces 38-41 Configuring EIGRP Route Authentication 38-42 EIGRP Stub Routing 38-43 Monitoring and Maintaining EIGRP 38-44

OL-12247-01 Configuring BGP 38-44 Default BGP Configuration 38-46 Nonstop Forwarding Awareness 38-48 Enabling BGP Routing 38-49 Managing Routing Policy Changes 38-51 Configuring BGP Decision Attributes 38-53 Configuring BGP Filtering with Route Maps 38-55 Configuring BGP Filtering by Neighbor 38-55 Configuring Prefix Lists for BGP Filtering 38-57 Configuring BGP Community Filtering 38-58 Configuring BGP Neighbors and Peer Groups 38-59 Configuring Aggregate Addresses 38-61 Configuring Routing Domain Confederations 38-62 Configuring BGP Route Reflectors 38-62 Configuring Route Dampening 38-63 Monitoring and Maintaining BGP 38-64 Configuring Multi-VRF CE 38-65 Understanding Multi-VRF CE 38-66 Default Multi-VRF CE Configuration 38-68 Multi-VRF CE Configuration Guidelines 38-68 Configuring VRFs 38-69 Configuring VRF-Aware Services 38-70 User Interface for ARP 38-70 User Interface for PING 38-71 User Interface for SNMP 38-71 User Interface for HSRP 38-71 User Interface for uRPF 38-72 User Interface for Syslog 38-72 User Interface for Traceroute 38-73 User Interface for FTP and TFTP 38-73 Configuring Multicast VRFs 38-74 Configuring a VPN Routing Session 38-74 Configuring BGP PE to CE Routing Sessions 38-75 Multi-VRF CE Configuration Example 38-76 Displaying Multi-VRF CE Status 38-80 Configuring Unicast Reverse Path Forwarding 38-80 Configuring Protocol-Independent Features 38-81 Configuring Distributed Cisco Express Forwarding 38-81 Configuring the Number of Equal-Cost Routing Paths 38-82

OL-12247-01 Configuring Static Unicast Routes 38-83 Specifying Default Routes and Networks 38-84 Using Route Maps to Redistribute Routing Information 38-85 Configuring Policy-Based Routing 38-88 PBR Configuration Guidelines 38-89 Enabling PBR 38-90 Filtering Routing Information 38-92 Setting Passive Interfaces 38-92 Controlling Advertising and Processing in Routing Updates 38-93 Filtering Sources of Routing Information 38-93 Managing Authentication Keys 38-94 Monitoring and Maintaining the IP Network 38-95 C H A P T E R 39 Configuring IPv6 Unicast Routing 39-1 Understanding IPv6 39-1 IPv6 Addresses 39-2 Supported IPv6 Unicast Routing Features 39-3 128-Bit Wide Unicast Addresses 39-3 DNS for IPv6 39-4 Path MTU Discovery for IPv6 Unicast 39-4 ICMPv6 39-4 Neighbor Discovery 39-4 IPv6 Applications 39-5 Dual IPv4 and IPv6 Protocol Stacks 39-5 EIGRP IPv6 39-6 Unsupported IPv6 Unicast Routing Features 39-9 Limitations 39-9 IPv6 and Switch Stacks 39-10 SDM Templates 39-11 Dual IPv4-and IPv6 SDM Templates 39-11 Configuring IPv6 39-12 Default IPv6 Configuration 39-13 Configuring IPv6 Addressing and Enabling IPv6 Routing 39-13 Configuring IPv4 and IPv6 Protocol Stacks 39-15 Configuring IPv6 ICMP Rate Limiting 39-17 Configuring CEF and dCEF for IPv6 39-17 Configuring Static Routing for IPv6 39-18 Configuring RIP for IPv6 39-20 Configuring OSPF for IPv6 39-22

OL-12247-01 Displaying IPv6 39-24 C H A P T E R 40 Configuring HSRP 40-1 Understanding HSRP 40-1 Multiple HSRP 40-3 HSRP and Switch Stacks 40-4 Configuring HSRP 40-4 Default HSRP Configuration 40-5 HSRP Configuration Guidelines 40-5 Enabling HSRP 40-5 Configuring HSRP Priority 40-7 Configuring MHSRP 40-9 Configuring HSRP Authentication and Timers 40-9 Enabling HSRP Support for ICMP Redirect Messages 40-11 Configuring HSRP Groups and Clustering 40-11 Displaying HSRP Configurations 40-11 C H A P T E R 41 Configuring Cisco IOS IP SLAs Operations 41-1 Understanding Cisco IOS IP SLAs 41-1 Using Cisco IOS IP SLAs to Measure Network Performance 41-3 IP SLAs Responder and IP SLAs Control Protocol 41-4 Response Time Computation for IP SLAs 41-4 IP SLAs Operation Scheduling 41-5 IP SLAs Operation Threshold Monitoring 41-5 Configuring IP SLAs Operations 41-6 Default Configuration 41-6 Configuration Guidelines 41-6 Configuring the IP SLAs Responder 41-8 Analyzing IP Service Levels by Using the UDP Jitter Operation 41-8 Analyzing IP Service Levels by Using the ICMP Echo Operation 41-11 Monitoring IP SLAs Operations 41-14 C H A P T E R 42 Configuring Enhanced Object Tracking 42-1 Understanding Enhanced Object Tracking 42-1 Configuring Enhanced Object Tracking Features 42-2 Default Configuration 42-2 Tracking Interface Line-Protocol or IP Routing State 42-2 Configuring a Tracked List 42-3

OL-12247-01 Configuring a Tracked List with a Boolean Expression 42-3 Configuring a Tracked List with a Weight Threshold 42-4 Configuring a Tracked List with a Percentage Threshold 42-5 Configuring HSRP Object Tracking 42-7 Configuring Other Tracking Characteristics 42-8 Configuring IP SLAs Object Tracking 42-9 Monitoring Enhanced Object Tracking 42-10 C H A P T E R 43 Configuring Web Cache Services By Using WCCP 43-1 Understanding WCCP 43-1 WCCP Message Exchange 43-2 WCCP Negotiation 43-3 MD5 Security 43-3 Packet Redirection and Service Groups 43-3 WCCP and Switch Stacks 43-4 Unsupported WCCP Features 43-5 Configuring WCCP 43-5 Default WCCP Configuration 43-5 WCCP Configuration Guidelines 43-5 Enabling the Web Cache Service 43-6 Monitoring and Maintaining WCCP 43-10 C H A P T E R 44 Configuring IP Multicast Routing 44-1 Understanding Cisco’s Implementation of IP Multicast Routing 44-2 Understanding IGMP 44-3 IGMP Version 1 44-3 IGMP Version 2 44-3 Understanding PIM 44-4 PIM Versions 44-4 PIM Modes 44-4 PIM Stub Routing 44-5 IGMP Helper 44-6 Auto-RP 44-6 Bootstrap Router 44-7 Multicast Forwarding and Reverse Path Check 44-7 Understanding DVMRP 44-9 Understanding CGMP 44-9 Multicast Routing and Switch Stacks 44-9

OL-12247-01 Configuring IP Multicast Routing 44-10 Default Multicast Routing Configuration 44-10 Multicast Routing Configuration Guidelines 44-11 PIMv1 and PIMv2 Interoperability 44-11 Auto-RP and BSR Configuration Guidelines 44-12 Configuring Basic Multicast Routing 44-12 Configuring PIM Stub Routing 44-14 PIM Stub Routing Configuration Guidelines 44-14 Enabling PIM Stub Routing 44-15 Configuring a Rendezvous Point 44-16 Manually Assigning an RP to Multicast Groups 44-16 Configuring Auto-RP 44-18 Configuring PIMv2 BSR 44-22 Using Auto-RP and a BSR 44-26 Monitoring the RP Mapping Information 44-27 Troubleshooting PIMv1 and PIMv2 Interoperability Problems 44-27 Configuring Advanced PIM Features 44-27 Understanding PIM Shared Tree and Source Tree 44-27 Delaying the Use of PIM Shortest-Path Tree 44-29 Modifying the PIM Router-Query Message Interval 44-30 Configuring Optional IGMP Features 44-30 Default IGMP Configuration 44-31 Configuring the Switch as a Member of a Group 44-31 Controlling Access to IP Multicast Groups 44-32 Changing the IGMP Version 44-33 Modifying the IGMP Host-Query Message Interval 44-33 Changing the IGMP Query Timeout for IGMPv2 44-34 Changing the Maximum Query Response Time for IGMPv2 44-35 Configuring the Switch as a Statically Connected Member 44-35 Configuring Optional Multicast Routing Features 44-36 Enabling CGMP Server Support 44-36 Configuring sdr Listener Support 44-37 Enabling sdr Listener Support 44-38 Limiting How Long an sdr Cache Entry Exists 44-38 Configuring an IP Multicast Boundary 44-39 Configuring Basic DVMRP Interoperability Features 44-40 Configuring DVMRP Interoperability 44-41 Configuring a DVMRP Tunnel 44-43

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

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

OL-12247-01 Using TDR 47-15 Understanding TDR 47-15 Running TDR and Displaying the Results 47-16 Using Debug Commands 47-16 Enabling Debugging on a Specific Feature 47-17 Enabling All-System Diagnostics 47-17 Redirecting Debug and Error Message Output 47-18 Using the show platform forward Command 47-18 Using the crashinfo Files 47-21 Basic crashinfo Files 47-21 Extended crashinfo Files 47-21 Using On-Board Failure Logging 47-22 Understanding OBFL 47-22 Configuring OBFL 47-22 Displaying OBFL Information 47-23 C H A P T E R 48 Configuring Online Diagnostics 48-1 Understanding Online Diagnostics 48-1 Configuring Online Diagnostics 48-2 Scheduling Online Diagnostics 48-2 Configuring Health-Monitoring Diagnostics 48-3 Running Online Diagnostic Tests 48-5 Starting Online Diagnostic Tests 48-5 Displaying Online Diagnostic Tests and Test Results 48-6 A P P E N D I X A Supported MIBs A-1 MIB List A-1 Using FTP to Access the MIB Files A-4 A P P E N D I X B Working with the Cisco IOS File System, Configuration Files, and Software Images B-1 Working with the Flash File System B-1 Displaying Available File Systems B-2 Setting the Default File System B-3 Displaying Information about Files on a File System B-3 Changing Directories and Displaying the Working Directory B-4 Creating and Removing Directories B-4 Copying Files B-5

OL-12247-01 Deleting Files B-5 Creating, Displaying, and Extracting Files B-6 Working with Configuration Files B-9 Guidelines for Creating and Using Configuration Files B-10 Configuration File Types and Location B-10 Creating a Configuration File By Using a Text Editor B-11 Copying Configuration Files By Using TFTP B-11 Preparing to Download or Upload a Configuration File By Using TFTP B-11 Downloading the Configuration File By Using TFTP B-12 Uploading the Configuration File By Using TFTP B-12 Copying Configuration Files By Using FTP B-13 Preparing to Download or Upload a Configuration File By Using FTP B-14 Downloading a Configuration File By Using FTP B-14 Uploading a Configuration File By Using FTP B-15 Copying Configuration Files By Using RCP B-16 Preparing to Download or Upload a Configuration File By Using RCP B-17 Downloading a Configuration File By Using RCP B-18 Uploading a Configuration File By Using RCP B-19 Clearing Configuration Information B-19 Clearing the Startup Configuration File B-20 Deleting a Stored Configuration File B-20 Replacing and Rolling Back Configurations B-20 Understanding Configuration Replacement and Rollback B-20 Configuration Guidelines B-21 Configuring the Configuration Archive B-22 Performing a Configuration Replacement or Rollback Operation B-23 Working with Software Images B-23 Image Location on the Switch B-25 File Format of Images on a Server or Cisco.com B-25 Copying Image Files By Using TFTP B-26 Preparing to Download or Upload an Image File By Using TFTP B-26 Downloading an Image File By Using TFTP B-27 Uploading an Image File By Using TFTP B-29 Copying Image Files By Using FTP B-29 Preparing to Download or Upload an Image File By Using FTP B-30 Downloading an Image File By Using FTP B-31 Uploading an Image File By Using FTP B-33

OL-12247-01 Copying Image Files By Using RCP B-34 Preparing to Download or Upload an Image File By Using RCP B-35 Downloading an Image File By Using RCP B-36 Uploading an Image File By Using RCP B-38 Copying an Image File from One Stack Member to Another B-39 A P P E N D I X C Unsupported Commands in Cisco IOS Release 12.2(40)EX C-1 Access Control Lists C-1 Unsupported Privileged EXEC Commands C-1 Unsupported Global Configuration Commands C-1 Unsupported Route-Map Configuration Commands C-1 Archive Commands C-2 Unsupported Privileged EXEC Commands C-2 ARP Commands C-2 Unsupported Global Configuration Commands C-2 Unsupported Interface Configuration Commands C-2 Boot Loader Commands C-2 Unsupported User EXEC Commands C-2 Unsupported Global Configuration Commands C-2 Debug Commands C-3 Unsupported Privileged EXEC Commands C-3 Embedded Event Manager C-3 Unsupported Privileged EXEC Commands C-3 Unsupported Global Configuration Commands C-3 Unsupported Commands in Applet Configuration Mode C-3 Fallback Bridging C-3 Unsupported Privileged EXEC Commands C-3 Unsupported Global Configuration Commands C-4 Unsupported Interface Configuration Commands C-4 HSRP C-5 Unsupported Global Configuration Commands C-5 Unsupported Interface Configuration Commands C-5 IGMP Snooping Commands C-5 Unsupported Global Configuration Commands C-5 Interface Commands C-6 Unsupported Privileged EXEC Commands C-6 Unsupported Global Configuration Commands C-6 Unsupported Interface Configuration Commands C-6

OL-12247-01 IP Multicast Routing C-6 Unsupported Privileged EXEC Commands C-6 Unsupported Global Configuration Commands C-7 Unsupported Interface Configuration Commands C-7 IP Unicast Routing C-7 Unsupported Privileged EXEC or User EXEC Commands C-7 Unsupported Global Configuration Commands C-8 Unsupported Interface Configuration Commands C-8 Unsupported BGP Router Configuration Commands C-8 Unsupported VPN Configuration Commands C-9 Unsupported Route Map Commands C-9 MAC Address Commands C-9 Unsupported Privileged EXEC Commands C-9 Unsupported Global Configuration Commands C-10 Miscellaneous C-10 Unsupported Privileged EXEC Commands C-10 Unsupported Global Configuration Commands C-10 MSDP C-11 Unsupported Privileged EXEC Commands C-11 Unsupported Global Configuration Commands C-11 NetFlow Commands C-11 Unsupported Global Configuration Commands C-11 Network Address Translation (NAT) Commands C-11 Unsupported Privileged EXEC Commands C-11 QoS C-12 Unsupported Global Configuration Command C-12 Unsupported Interface Configuration Commands C-12 Unsupported Policy-Map Configuration Command C-12 RADIUS C-12 Unsupported Global Configuration Commands C-12 SNMP C-12 Unsupported Global Configuration Commands C-12 Spanning Tree C-13 Unsupported Global Configuration Command C-13 Unsupported Interface Configuration Command C-13 VLAN C-13 Unsupported Global Configuration Command C-13 Unsupported User EXEC Commands C-13

OL-12247-01 VTP C-13 Unsupported Privileged EXEC Command C-13 I N D E X

OL-12247-01 Preface Audience This guide is for the networking professional managing the standalone Cisco Catalyst Blade Switch 3120 for HP or blade switch stack, referred to as the switch. Before using this guide, you should have experience working with the Cisco IOS software and be familiar with the concepts and terminology of Ethernet and local area networking. You install the switch in the HP BladeSystem 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. • Square brackets ([ ]) mean optional elements.

OL-12247-01 Preface Related Publications • 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/ps6748/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. You can order printed copies of documents with a DOC-xxxxxx= number from the Cisco.com sites and from the telephone numbers listed in the URL referenced in the Obtaining Documentation and Submitting a Service Request section. • Release Notes for the Cisco Catalyst Blade Switch 3120 for HP (not orderable but available on Cisco.com) • Cisco Catalyst Blade Switch 3120 for HP Software Configuration Guide (not orderable but available on Cisco.com) • Cisco Catalyst Blade Switch 3120 for HP Command Reference (not orderable but available on Cisco.com)

OL-12247-01 Preface Related Publications • Cisco Catalyst Blade Switch 3120 for HP System Message Guide (not orderable but available on Cisco.com) • Cisco Software Activation Document for HP • Device manager online help (available on the switch) • Cisco Catalyst Blade Switch 3120 for HP Hardware Installation Guide (not orderable but available on Cisco.com) • Cisco Catalyst Blade Switch 3000 Series for HP Getting Started Guide (not orderable but available on Cisco.com) • Regulatory Compliance and Safety Information for the Cisco Catalyst Blade Switch 3000 Series for HP (not orderable but available on Cisco.com) • Installation Note for the Cisco TwinGig Converter Module (order number DOC-7817572=) • Cisco Small Form-Factor Pluggable Modules Installation Notes (order number DOC-7815160=) • Cisco CWDM GBIC and CWDM SFP Installation Note (not orderable but available on Cisco.com) • These compatibility matrix documents are available from this Cisco.com site: http://www.cisco.com/en/US/products/hw/modules/ps5455/products_device_support_tables_list. html – Cisco Gigabit Ethernet Transceiver Modules Compatibility Matrix (not orderable but available on Cisco.com) – Cisco 100-Megabit Ethernet SFP Modules Compatibility Matrix (not orderable but available on Cisco.com) – Cisco Small Form-Factor Pluggable Modules Compatibility Matrix (not orderable but available on Cisco.com) – Compatibility Matrix for 1000BASE-T Small Form-Factor Pluggable Modules (not orderable but available on Cisco.com) • For information about the Network Admission Control (NAC) features, see the Network Admission Control Software Configuration Guide (Not orderable but available on Cisco.com) 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-12247-01 Preface Related Publications

1-1 Cisco Catalyst Blade Switch 3120 for HP Software Configuration Guide OL-12247-01 1 Overview This chapter provides these topics about the switch software: • Features, page 1-1 • Default Settings After Initial Switch Configuration, page 1-13 • Network Configuration Examples, page 1-16 • Where to Go Next, page 1-20 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). Features The switch supports either the cryptographic (supports encryption) or the noncryptographic universal software image. The cryptographic universal software image supports the IP base, IP services, and advanced IP services feature sets. The noncryptographic universal software image supports only the IP base and IP services feature sets. You must have a Cisco IOS software license for a specific feature set to enable it. For more information about the software license, see the Cisco Software Activation for HP 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. • IP services feature set, which provides a richer set of enterprise-class intelligent services. 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 IPv6 access control lists (ACLs) and Multicast Listener Discovery (MLD) snooping. Switches with the IP services feature set can be upgraded to the advanced IP services feature set. IP services-only Layer 3 features are described in the “Layer 3 Features” section on page 1-11.

OL-12247-01 Chapter 1 Overview Features For more information, see Chapter 24, “Configuring IPv6 MLD Snooping,” and Chapter 35, “Configuring IPv6 ACLs.” • Advanced IP services feature set, which provides full IPv6 support. It includes all IP service features with IPv6 routing and IPv6 ACLs. For more information on IPv6 routing, see Chapter 39, “Configuring IPv6 Unicast Routing.” For more information about IPv6 ACLs, see Chapter 35, “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-2 • Performance Features, page 1-3 • Management Options, page 1-5 • Manageability Features, page 1-5 (includes a feature requiring the cryptographic universal software image) • Availability and Redundancy Features, page 1-6 • VLAN Features, page 1-7 • Security Features, page 1-8 (includes a feature requiring the cryptographic universal software image) • QoS and CoS Features, page 1-10 • Layer 3 Features, page 1-11 (includes features requiring the IP services feature set) • Monitoring Features, page 1-12 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. • 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.

OL-12247-01 Chapter 1 Overview Features – 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 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. – 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). 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

OL-12247-01 Chapter 1 Overview Features • 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 • 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 • Cisco Group Management Protocol (CGMP) server support and Internet Group Management Protocol (IGMP) snooping for IGMP Versions 1, 2, and 3: – (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 • IIGMP 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 • 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 image)

OL-12247-01 Chapter 1 Overview Features 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. • 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 32, “Configuring SNMP.” • CNS—Cisco Networking Services is network management software that acts as a configuration service for automating the deployment and management of network devices and services. You can automate initial configurations and configuration updates by generating switch-specific configuration changes, sending them to the switch, executing the configuration change, and logging the results. For more information about CNS, see Chapter 4, “Configuring Cisco IOS CNS Agents.” • Onboard Administrator 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 Onboard Administrator. The port is connected to the Onboard Administrator 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 • 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

OL-12247-01 Chapter 1 Overview Features • Address Resolution Protocol (ARP) for identifying a switch through its IP address and its corresponding MAC address • Unicast MAC address filtering to drop packets with specific source or destination MAC addresses • Cisco Discovery Protocol (CDP) Versions 1 and 2 for network topology discovery and mapping between the switch and other Cisco devices on the network • Link Layer Discovery Protocol (LLDP) and LLDP Media Endpoint Discovery (LLDP-MED) for interoperability with third-party IP phones • Support for the LLDP-MED location TLV that provides location information from the switch to the endpoint device • Network Time Protocol (NTP) for providing a consistent time stamp to all switches from an external source • Cisco IOS File System (IFS) for providing a single interface to all file systems that the switch uses • 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 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) Note For additional descriptions of the management interfaces, see the “Network Configuration Examples” section on page 1-16. 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 The newly elected stack master begins accepting Layer 2 traffic in less than 1 second and Layer 3 traffic between 3 to 5 seconds.

OL-12247-01 Chapter 1 Overview Features • Cross-stack EtherChannel for providing redundant links across the switch stack • UniDirectional Link Detection (UDLD) and aggressive UDLD for detecting and disabling unidirectional links on fiber-optic interfaces caused by incorrect fiber-optic wiring or port faults • IEEE 802.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, 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 • 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 • 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 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

OL-12247-01 Chapter 1 Overview Features • Inter-Switch Link (ISL) and IEEE 802.1Q trunking encapsulation on all ports for network moves, adds, and changes; management and control of broadcast and multicast traffic; and network security by establishing VLAN groups for high-security users and network resources • Dynamic Trunking Protocol (DTP) for negotiating trunking on a link between two devices and for negotiating the type of trunking encapsulation (IEEE 802.1Q or ISL) to be used • VLAN Trunking Protocol (VTP) and VTP pruning for reducing network traffic by restricting flooded traffic to links destined for stations receiving the traffic • Voice VLAN for creating subnets for voice traffic from Cisco IP Phones • 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. 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

OL-12247-01 Chapter 1 Overview Features • 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 • 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 • 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 – Port security for controlling access to IEEE 802.1x ports – Voice VLAN to permit a Cisco IP Phone to access the voice VLAN regardless of the authorized or unauthorized state of the port – IP phone detection enhancement to detect and recognize a Cisco IP phone – Guest VLAN to provide limited services to non-IEEE 802.1x-compliant users – Restricted VLAN to provide limited services to users who are IEEE 802.1x compliant, but do not have the credentials to authenticate via the standard IEEE 802.1x processes – IEEE 802.1x accounting to track network usage – IEEE 802.1x with wake-on-LAN to allow dormant PCs to be powered on based on the receipt of a specific Ethernet frame • MAC authentication bypass to authorize clients based on the client MAC address. • Network Admission Control (NAC) 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 IEEE 802.1x Validation” section on page 9-41. – 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-12247-01 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-37. – 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 • 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) 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 • 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

OL-12247-01 Chapter 1 Overview Features • 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 – 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 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 for Layer 3 router redundancy • IP routing protocols for load balancing and for constructing scalable, routed backbones: – RIP Versions 1 and 2 – OSPF (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

OL-12247-01 Chapter 1 Overview Features • 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 • 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 • IPv6 unicast routing capability for forwarding IPv6 traffic through configured interfaces (requires the advanced 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 Monitoring Features These are the monitoring features: • Switch LEDs that provide port-, switch-, and stack-level status on 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

OL-12247-01 Chapter 1 Overview Default Settings After Initial Switch Configuration • 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 • 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 • Embedded event manager (EEM) for device and system management to monitor key system events and then act on them though a policy 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. Note For information about assigning an IP address by using the browser-based Express Setup program, see the getting started guide. For information about assigning an IP address by using the CLI-based setup program, see the hardware installation guide. If you do not configure the switch at all, the switch operates with these default settings: • Default switch IP address, subnet mask, and default gateway is 0.0.0.0. For more information, see Chapter 3, “Assigning the Switch IP Address and Default Gateway,” and Chapter 21, “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 21, “Configuring DHCP Features and IP Source Guard.” • Switch stack is enabled (not configurable). For more information, see Chapter 5, “Managing Switch Stacks.” • No passwords are defined. For more information, see Chapter 6, “Administering the Switch.” • System name and prompt is Switch. For more information, see Chapter 6, “Administering the Switch.” • NTP is enabled. For more information, see Chapter 6, “Administering the Switch.”

OL-12247-01 Chapter 1 Overview Default Settings After Initial Switch Configuration • DNS is enabled. For more information, see Chapter 6, “Administering the Switch.” • TACACS+ is disabled. For more information, see Chapter 7, “Configuring Switch-Based Authentication.” • RADIUS is disabled. For more information, see Chapter 7, “Configuring Switch-Based Authentication.” • The standard HTTP server and Secure Socket Layer (SSL) HTTPS server are both enabled. For more information, see Chapter 7, “Configuring Switch-Based Authentication.” • IEEE 802.1x is disabled. For more information, see Chapter 9, “Configuring IEEE 802.1x Port-Based Authentication.” • Port parameters – Operating mode is Layer 2 (switchport). For more information, see Chapter 10, “Configuring Interface Characteristics.” – Interface speed and duplex mode is autonegotiate. For more information, see Chapter 10, “Configuring Interface Characteristics.” – Auto-MDIX is enabled. For more information, see Chapter 10, “Configuring Interface Characteristics.” – Flow control is off. For more information, see Chapter 10, “Configuring Interface Characteristics.” • No Smartports macros are defined. For more information, see Chapter 11, “Configuring Smartports Macros.” • VLANs – Default VLAN is VLAN 1. For more information, see Chapter 12, “Configuring VLANs.” – VLAN trunking setting is dynamic auto (DTP). For more information, see Chapter 12, “Configuring VLANs.” – Trunk encapsulation is negotiate. For more information, see Chapter 12, “Configuring VLANs.” – VTP mode is server. For more information, see Chapter 13, “Configuring VTP.” – VTP version is Version 1. For more information, see Chapter 13, “Configuring VTP.” – No private VLANs are configured. For more information, see Chapter 15, “Configuring Private VLANs.” – Voice VLAN is disabled. For more information, see Chapter 14, “Configuring Voice VLAN.” • IEEE 802.1Q tunneling and Layer 2 protocol tunneling are disabled. For more information, see Chapter 16, “Configuring IEEE 802.1Q and Layer 2 Protocol Tunneling.” • STP, PVST+ is enabled on VLAN 1. For more information, see Chapter 17, “Configuring STP.” • MSTP is disabled. For more information, see Chapter 18, “Configuring MSTP.” • Optional spanning-tree features are disabled. For more information, see Chapter 19, “Configuring Optional Spanning-Tree Features.” • Flex Links are not configured. For more information, see Chapter 20, “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 21, “Configuring DHCP Features and IP Source Guard.” • IP source guard is disabled. For more information, see Chapter 21, “Configuring DHCP Features and IP Source Guard.”

OL-12247-01 Chapter 1 Overview Default Settings After Initial Switch Configuration • Dynamic ARP inspection is disabled on all VLANs. For more information, see Chapter 22, “Configuring Dynamic ARP Inspection.” • IGMP snooping is enabled. No IGMP filters are applied. For more information, see Chapter 23, “Configuring IGMP Snooping and MVR.” • IGMP throttling setting is deny. For more information, see Chapter 23, “Configuring IGMP Snooping and MVR.” • The IGMP snooping querier feature is disabled. For more information, see Chapter 23, “Configuring IGMP Snooping and MVR.” • MVR is disabled. For more information, see Chapter 23, “Configuring IGMP Snooping and MVR.” • Port-based traffic – Broadcast, multicast, and unicast storm control is disabled. For more information, see Chapter 25, “Configuring Port-Based Traffic Control.” – No protected ports are defined. For more information, see Chapter 25, “Configuring Port-Based Traffic Control.” – Unicast and multicast traffic flooding is not blocked. For more information, see Chapter 25, “Configuring Port-Based Traffic Control.” – No secure ports are configured. For more information, see Chapter 25, “Configuring Port-Based Traffic Control.” • CDP is enabled. For more information, see Chapter 26, “Configuring CDP.” • UDLD is disabled. For more information, see Chapter 28, “Configuring UDLD.” • SPAN and RSPAN are disabled. For more information, see Chapter 29, “Configuring SPAN and RSPAN.” • RMON is disabled. For more information, see Chapter 30, “Configuring RMON.” • Syslog messages are enabled and appear on the console. For more information, see Chapter 31, “Configuring System Message Logging.” • SNMP is enabled (Version 1). For more information, see Chapter 32, “Configuring SNMP.” • No ACLs are configured. For more information, see Chapter 34, “Configuring Network Security with ACLs.” • QoS is disabled. For more information, see Chapter 36, “Configuring QoS.” • No EtherChannels are configured. For more information, see Chapter 37, “Configuring EtherChannels and Link-State Tracking.” • IP unicast routing is disabled. For more information, see Chapter 38, “Configuring IP Unicast Routing.” • No HSRP groups are configured. For more information, see Chapter 40, “Configuring HSRP.” • IP multicast routing is disabled on all interfaces. For more information, see Chapter 44, “Configuring IP Multicast Routing.” • MSDP is disabled. For more information, see Chapter 45, “Configuring MSDP.” • Fallback bridging is not configured. For more information, see Chapter 46, “Configuring Fallback Bridging.”

OL-12247-01 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-16 • “Small to Medium-Sized Network” section on page 1-19 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-12247-01 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. 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. 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-12247-01 Chapter 1 Overview Network Configuration Examples 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-12247-01 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-12247-01 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” 201914 Campus core Catalyst 6500 switches Blade switch StackWise switch stacks Blade server enclosures

2-1 Cisco Catalyst Blade Switch 3120 for HP Software Configuration Guide OL-12247-01 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-4 • Understanding no and default Forms of Commands, page 2-4 • Understanding CLI Error Messages, page 2-5 • Using Configuration Logging, page 2-5 • Using Command History, page 2-6 • Using Editing Features, page 2-7 • Searching and Filtering Output of show and more Commands, page 2-10 • Accessing the CLI, page 2-10 Understanding Command Modes The Cisco IOS user interface is divided into many different modes. The commands available to you depend on which mode you are currently in. Enter a question mark (?) at the system prompt to obtain a list of commands available for each command mode. When you start a session on the switch, you begin in user mode, often called user EXEC mode. Only a limited subset of the commands are available in user EXEC mode. For example, most of the user EXEC commands are one-time commands, such as show commands, which show the current configuration status, and clear commands, which clear counters or interfaces. The user EXEC commands are not saved when the switch reboots. To have access to all commands, you must enter privileged EXEC mode. Normally, you must enter a password to enter privileged EXEC mode. From this mode, you can enter any privileged EXEC command or enter global configuration mode. Using the configuration modes (global, interface, and line), you can make changes to the running configuration. If you save the configuration, these commands are stored and used when the switch reboots. To access the various configuration modes, you must start at global configuration mode. From global configuration mode, you can enter interface configuration mode and line configuration mode.

OL-12247-01 Chapter 2 Using the Command-Line Interface Understanding Command Modes Table 2-1 describes the main command modes, how to access each one, the prompt you see in that mode, and how to exit the mode. The examples in the table use the hostname Switch. Table 2-1 Command Mode Summary Mode Access Method Prompt Exit Method About This Mode User EXEC Begin a session with your switch. Switch> Enter logout or quit. Use this mode to • Change terminal settings. • Perform basic tests. • Display system information. Privileged EXEC While in user EXEC mode, enter the enable command. Switch# Enter disable to exit. Use this mode to verify commands that you have entered. Use a password to protect access to this mode. Global configuration While in privileged EXEC mode, enter the configure command. Switch(config)# To exit to privileged EXEC mode, enter exit or end, or press Ctrl-Z. Use this mode to configure parameters that apply to the entire switch. Config-vlan While in global configuration mode, enter the vlan vlan-id command. Switch(config-vlan)# To exit to global configuration mode, enter the exit command. To return to privileged EXEC mode, press Ctrl-Z or enter end. Use this mode to configure VLAN parameters. When VTP mode is transparent, you can create extended-range VLANs (VLAN IDs greater than 1005) and save configurations in the switch startup configuration file. VLAN configuration While in privileged EXEC mode, enter the vlan database command. Switch(vlan)# To exit to privileged EXEC mode, enter exit. Use this mode to configure VLAN parameters for VLANs 1 to 1005 in the VLAN database.

OL-12247-01 Chapter 2 Using the Command-Line Interface Understanding the Help System For more detailed information on the command modes, see the command reference guide for this release. Understanding the Help System You can enter a question mark (?) at the system prompt to display a list of commands available for each command mode. You can also obtain a list of associated keywords and arguments for any command, as shown in Table 2-2. Interface configuration While in global configuration mode, enter the interface command (with a specific interface). Switch(config-if)# To exit to global configuration mode, enter exit. To return to privileged EXEC mode, press Ctrl-Z or enter end. Use this mode to configure parameters for the Ethernet ports. For information about defining interfaces, see the “Using Interface Configuration Mode” section on page 10-7. To configure multiple interfaces with the same parameters, see the “Configuring a Range of Interfaces” section on page 10-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. Table 2-1 Command Mode Summary (continued) Mode Access Method Prompt Exit Method About This Mode 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

OL-12247-01 Chapter 2 Using the Command-Line Interface Understanding Abbreviated Commands Understanding Abbreviated Commands You need to enter only enough characters for the switch to recognize the command as unique. This example shows how to enter the show configuration privileged EXEC command in an abbreviated form: Switch# show conf Understanding no and default Forms of Commands Almost every configuration command also has a no form. In general, use the no form to disable a feature or function or reverse the action of a command. For example, the no shutdown interface configuration command reverses the shutdown of an interface. Use the command without the keyword no to re-enable a disabled feature or to enable a feature that is disabled by default. Configuration commands can also have a default form. The default form of a command returns the command setting to its default. Most commands are disabled by default, so the default form is the same as the no form. However, some commands are enabled by default and have variables set to certain default values. In these cases, the default command enables the command and sets variables to their default values. ? List all commands available for a particular command mode. For example: Switch> ? command ? List the associated keywords for a command. For example: Switch> show ? command keyword ? List the associated arguments for a keyword. For example: Switch(config)# cdp holdtime ? <10-255> Length of time (in sec) that receiver must keep this packet Table 2-2 Help Summary (continued) Command Purpose

OL-12247-01 Chapter 2 Using the Command-Line Interface Understanding CLI Error Messages Understanding CLI Error Messages Table 2-3 lists some error messages that you might encounter while using the CLI to configure your switch. Using Configuration Logging 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 at this URL: http://www.cisco.com/en/US/products/ps6350/products_configuration_guide_chapter09186a0080454f 73.html Note Only CLI or HTTP changes are logged. Table 2-3 Common CLI Error Messages Error Message Meaning How to Get Help % Ambiguous command: "show con" You did not enter enough characters for your switch to recognize the command. Re-enter the command followed by a question mark (?) with a space between the command and the question mark. The possible keywords that you can enter with the command appear. % Incomplete command. You did not enter all the keywords or values required by this command. Re-enter the command followed by a question mark (?) with a space between the command and the question mark. The possible keywords that you can enter with the command appear. % Invalid input detected at ‘^’ marker. You entered the command incorrectly. The caret (^) marks the point of the error. Enter a question mark (?) to display all the commands that are available in this command mode. The possible keywords that you can enter with the command appear.

OL-12247-01 Chapter 2 Using the Command-Line Interface Using Command History Using Command History The software provides a history or record of commands that you have entered. The command history feature is particularly useful for recalling long or complex commands or entries, including access lists. You can customize this feature to suit your needs as described in these sections: • Changing the Command History Buffer Size, page 2-6 (optional) • Recalling Commands, page 2-6 (optional) • Disabling the Command History Feature, page 2-7 (optional) Changing the Command History Buffer Size By default, the switch records ten command lines in its history buffer. You can alter this number for a current terminal session or for all sessions on a particular line. These procedures are optional. Beginning in privileged EXEC mode, enter this command to change the number of command lines that the switch records during the current terminal session: Switch# terminal history [size number-of-lines] The range is from 0 to 256. Beginning in line configuration mode, enter this command to configure the number of command lines the switch records for all sessions on a particular line: Switch(config-line)# history [size number-of-lines] The range is from 0 to 256. Recalling Commands To recall commands from the history buffer, perform one of the actions listed in Table 2-4. These actions are optional. Table 2-4 Recalling Commands 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-12247-01 Chapter 2 Using the Command-Line Interface Using Editing Features Disabling the Command History Feature The command history feature is automatically enabled. You can disable it for the current terminal session or for the command line. These procedures are optional. To disable the feature during the current terminal session, enter the terminal no history privileged EXEC command. To disable command history for the line, enter the no history line configuration command. Using Editing Features This section describes the editing features that can help you manipulate the command line. It contains these sections: • Enabling and Disabling Editing Features, page 2-7 (optional) • Editing Commands through Keystrokes, page 2-8 (optional) • Editing Command Lines that Wrap, page 2-9 (optional) Enabling and Disabling Editing Features Although enhanced editing mode is automatically enabled, you can disable it, re-enable it, or configure a specific line to have enhanced editing. These procedures are optional. To globally disable enhanced editing mode, enter this command in line configuration mode: Switch (config-line)# no editing To re-enable the enhanced editing mode for the current terminal session, enter this command in privileged EXEC mode: Switch# terminal editing To reconfigure a specific line to have enhanced editing mode, enter this command in line configuration mode: Switch(config-line)# editing

OL-12247-01 Chapter 2 Using the Command-Line Interface Using Editing Features 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. 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.

OL-12247-01 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 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. 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-12247-01 Chapter 2 Using the Command-Line Interface Searching and Filtering Output of show and more Commands 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-8. 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 10-7. 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.

OL-12247-01 Chapter 2 Using the Command-Line Interface Accessing the CLI 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 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 7-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 7-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 7-37. 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.

OL-12247-01 Chapter 2 Using the Command-Line Interface Accessing the CLI

3-1 Cisco Catalyst Blade Switch 3120 for HP Software Configuration Guide OL-12247-01 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 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-1 • Assigning Switch Information, page 3-2 • Checking and Saving the Running Configuration, page 3-11 • Modifying the Startup Configuration, page 3-12 • Scheduling a Reload of the Software Image, page 3-17 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 39, “Configuring IPv6 Unicast Routing” for information specific to IPv6 address format and configuration. To enable IPv6, the stack or switch must be running the advanced IP services feature set. 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).

OL-12247-01 Chapter 3 Assigning the Switch IP Address and Default Gateway Assigning Switch Information 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 47-2 and the “Recovering from a Lost or Forgotten Password” section on page 47-3. Note You can disable password recovery. For more information, see the “Disabling Password Recovery” section on page 7-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. Assigning Switch Information You can assign IP information through the Onboard Administrator 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.

OL-12247-01 Chapter 3 Assigning the Switch IP Address and Default Gateway Assigning Switch Information 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-3 • Manually Assigning IP Information, page 3-10 Default Switch Information Table 3-1 shows the default switch information. Understanding DHCP-Based Autoconfiguration DHCP provides configuration information to Internet hosts and internetworking devices. This protocol consists of two components: one for delivering configuration parameters from a DHCP server to a device and a mechanism for allocating network addresses to devices. DHCP is built on a client-server model, in which designated DHCP servers allocate network addresses and deliver configuration parameters to dynamically configured devices. The switch can act as both a DHCP client and a DHCP server. During DHCP-based autoconfiguration, your switch (DHCP client) is automatically configured at startup with IP address information and a configuration file. 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-12247-01 Chapter 3 Assigning the Switch IP Address and Default Gateway Assigning Switch Information 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. In a DHCPREQUEST broadcast message, the client returns a formal request for the offered configuration information to the DHCP server. The formal request is broadcast so that all other DHCP servers that received the DHCPDISCOVER broadcast message from the client can reclaim the IP addresses that they offered to the client. The DHCP server confirms that the IP address has been allocated to the client by returning a DHCPACK unicast message to the client. With this message, the client and server are bound, and the client uses configuration information received from the server. The amount of information the switch receives depends on how you configure the DHCP server. For more information, see the “Configuring the TFTP Server” section on page 3-6. If the configuration parameters sent to the client in the DHCPOFFER unicast message are invalid (a configuration error exists), the client returns a DHCPDECLINE broadcast message to the DHCP server. Switch A DHCPACK (unicast) DHCPREQUEST (broadcast) DHCPOFFER (unicast) DHCPDISCOVER (broadcast) DHCP server 51807

OL-12247-01 Chapter 3 Assigning the Switch IP Address and Default Gateway Assigning Switch Information 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. Configuring DHCP-Based Autoconfiguration These sections contain this configuration information: • DHCP Server Configuration Guidelines, page 3-5 • Configuring the TFTP Server, page 3-6 • Configuring the DNS, page 3-6 • Configuring the Relay Device, page 3-7 • Obtaining Configuration Files, page 3-7 • Example Configuration, page 3-8 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.

OL-12247-01 Chapter 3 Assigning the Switch IP Address and Default Gateway Assigning Switch Information 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. 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-7. 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.

OL-12247-01 Chapter 3 Assigning the Switch IP Address and Default Gateway Assigning Switch Information 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. 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 10-4 and the “Configuring Layer 3 Interfaces” section on page 10-21. 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. 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-12247-01 Chapter 3 Assigning the Switch IP Address and Default Gateway Assigning Switch Information • The IP address and the configuration filename is reserved for the switch, but the TFTP server address is not provided in the DHCP reply (one-file read method). The switch receives its IP address, subnet mask, and the configuration filename from the DHCP server. The switch sends a broadcast message to a TFTP server to retrieve the named configuration file from the base directory of the server, and upon receipt, it completes its boot up process. • Only the IP address is reserved for the switch and provided in the DHCP reply. The configuration filename is not provided (two-file read method). The switch receives its IP address, subnet mask, and the TFTP server address from the DHCP server. The switch sends a unicast message to the TFTP server to retrieve the network-confg or cisconet.cfg default configuration file. (If the network-confg file cannot be read, the switch reads the cisconet.cfg file.) 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 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

OL-12247-01 Chapter 3 Assigning the Switch IP Address and Default Gateway Assigning Switch Information Table 3-2 shows the configuration of the reserved leases on the DHCP server. 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. Table 3-2 DHCP Server Configuration Switch A Switch B Switch C Switch D Binding key (hardware address) 00e0.9f1e.2001 00e0.9f1e.2002 00e0.9f1e.2003 00e0.9f1e.2004 IP address 10.0.0.21 10.0.0.22 10.0.0.23 10.0.0.24 Subnet mask 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 Router address 10.0.0.10 10.0.0.10 10.0.0.10 10.0.0.10 DNS server address 10.0.0.2 10.0.0.2 10.0.0.2 10.0.0.2 TFTP server name tftpserver or 10.0.0.3 tftpserver or 10.0.0.3 tftpserver or 10.0.0.3 tftpserver or 10.0.0.3 Boot filename (configuration file) (optional) switcha-confg switchb-confg switchc-confg switchd-confg Hostname (optional) switcha switchb switchc switchd

OL-12247-01 Chapter 3 Assigning the Switch IP Address and Default Gateway Assigning Switch Information Switches B through D retrieve their configuration files and IP addresses in the same way. 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. 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). 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. 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.

OL-12247-01 Chapter 3 Assigning the Switch IP Address and Default Gateway Checking and Saving the Running Configuration 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 6, “Administering the Switch.” Checking and Saving the Running Configuration You can check the configuration settings you entered or changes you made by entering this privileged EXEC command: Switch# show running-config Building configuration... Current configuration: 1363 bytes ! version 12.2 no service pad service timestamps debug uptime service timestamps log uptime no service password-encryption ! hostname Stack1 ! enable secret 5 $1$ej9.$DMUvAUnZOAmvmgqBEzIxE0 ! .

. interface gigabitethernet6/0/20 no switchport ip address 172.20.137.50 255.255.255.0 ! interface gigabitethernet6/0/21 mvr type source

...! interface VLAN1 ip address 172.20.137.50 255.255.255.0 no ip directed-broadcast ! ip default-gateway 172.20.137.1 ! ! snmp-server community private RW snmp-server community public RO snmp-server community private@es0 RW snmp-server community public@es0 RO snmp-server chassis-id 0x12 ! end To store the configuration or changes you have made to your startup configuration in flash memory, enter this privileged EXEC command: Switch# copy running-config startup-config Destination filename [startup-config]? Building configuration...

OL-12247-01 Chapter 3 Assigning the Switch IP Address and Default Gateway Modifying the Startup Configuration This command saves the configuration settings that you made. If you fail to do this, your configuration will be lost the next time you reload the system. To display information stored in the NVRAM section of flash memory, use the show startup-config or more startup-config privileged EXEC command. For more information about alternative locations from which to copy the configuration file, see Appendix B, “Working with the Cisco IOS File System, Configuration Files, and Software Images.” Modifying the Startup Configuration These sections describe how to modify the switch startup configuration: • Default Boot Configuration, page 3-12 • Automatically Downloading a Configuration File, page 3-12 • Booting Manually, page 3-13 • Booting a Specific Software Image, page 3-14 • Controlling Environment Variables, page 3-15 See also Appendix B, “Working with the Cisco IOS File System, Configuration Files, and Software Images,” for information about switch configuration files. See the “Switch Stack Configuration Files” section on page 5-16 for information about switch stack configuration files. Default Boot Configuration Table 3-3 shows the default boot configuration. Automatically Downloading a Configuration File You can automatically download a configuration file to your switch by using the DHCP-based autoconfiguration feature. For more information, see the “Understanding DHCP-Based Autoconfiguration” section on page 3-3. Table 3-3 Default Boot Configuration Feature Default Setting Operating system software image The switch attempts to automatically boot up the system using information in the BOOT environment variable. If the variable is not set, the switch attempts to load and execute the first executable image it can by performing a recursive, depth-first search throughout the flash file system. The Cisco IOS image is stored in a directory that has the same name as the image file (excluding the .bin extension). In a depth-first search of a directory, each encountered subdirectory is completely searched before continuing the search in the original directory. Configuration file Configured switches use the config.text file stored on the system board in flash memory. A new switch has no configuration file.

OL-12247-01 Chapter 3 Assigning the Switch IP Address and Default Gateway Modifying the Startup Configuration Specifying the Filename to Read and Write the System Configuration By default, the Cisco IOS software uses the file config.text to read and write a nonvolatile copy of the system configuration. However, you can specify a different filename, which will be loaded during the next boot cycle. Note This command only works properly from a standalone switch. Beginning in privileged EXEC mode, follow these steps to specify a different configuration filename: To return to the default setting, use the no boot config-file global configuration command. Booting Manually By default, the switch automatically boots up; however, you can configure it to manually boot up. Note This command only works properly from a standalone switch. Beginning in privileged EXEC mode, follow these steps to configure the switch to manually boot up during the next boot cycle: Command Purpose Step 1 configure terminal Enter global configuration mode. Step 2 boot config-file flash:/file-url Specify the configuration file to load during the next boot cycle. For file-url, specify the path (directory) and the configuration filename. Filenames and directory names are case sensitive. Step 3 end Return to privileged EXEC mode. Step 4 show boot Verify your entries. The boot config-file global configuration command changes the setting of the CONFIG_FILE environment variable. Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file. Command Purpose Step 1 configure terminal Enter global configuration mode. Step 2 boot manual Enable the switch to manually boot up during the next boot cycle. Step 3 end Return to privileged EXEC mode.

OL-12247-01 Chapter 3 Assigning the Switch IP Address and Default Gateway Modifying the Startup Configuration To disable manual booting, use the no boot manual global configuration command. Booting a Specific Software Image By default, the switch attempts to automatically boot up the system using information in the BOOT environment variable. If this variable is not set, the switch attempts to load and execute the first executable image it can by performing a recursive, depth-first search throughout the flash file system. In a depth-first search of a directory, each encountered subdirectory is completely searched before continuing the search in the original directory. However, you can specify a specific image to boot up. Beginning in privileged EXEC mode, follow these steps to configure the switch to boot up a specific image during the next boot cycle: Step 4 show boot Verify your entries. The boot manual global command changes the setting of the MANUAL_BOOT environment variable. The next time you reboot the system, the switch is in boot loader mode, shown by the switch: prompt. To boot up the system, use the boot filesystem:/file-url boot loader command. • For filesystem:, use flash: for the system board flash device. • For file-url, specify the path (directory) and the name of the bootable image. Filenames and directory names are case sensitive. Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file. Command Purpose Command Purpose Step 1 configure terminal Enter global configuration mode. Step 2 boot system filesystem:/file-url Configure the switch to boot up a specific image in flash memory during the next boot cycle. • For filesystem:, use flash: for the system board flash device. • For file-url, specify the path (directory) and the name of the bootable image. If you enter this command on a stack master, the specified software image is loaded only on the stack master during the next boot cycle. Filenames and directory names are case sensitive. Step 3 boot system switch {number | all} (Optional) Specify the switch members on which the system image is loaded during the next boot cycle: • Use number to specify a stack member. • Use all to specify all stack members. Step 4 end Return to privileged EXEC mode.

OL-12247-01 Chapter 3 Assigning the Switch IP Address and Default Gateway Modifying the Startup Configuration To return to the default setting, use the no boot system global configuration command. Controlling Environment Variables With a normally operating switch, you enter the boot loader mode only through a switch console connection configured for 9600 b/s by performing these tasks: 1. Power off the switch by using the Onboard Administrator GUI or by removing the switch from the enclosure. 2. Power on the switch by using the GUI or re-inserting the switch in the enclosure. 3. Press the switch Mode button while powering on the switch. You can release the Mode button after the system LED stops blinking and is solid green. Then the boot loader switch: prompt appears. The switch boot loader software provides support for nonvolatile environment variables, which can be used to control how the boot loader, or any other software running on the system, behaves. Boot loader environment variables are similar to environment variables that can be set on UNIX or DOS systems. Environment variables that have values are stored in flash memory outside of the flash file system. Each line in these files contains an environment variable name and an equal sign followed by the value of the variable. A variable has no value if it is not listed in this file; it has a value if it is listed in the file even if the value is a null string. A variable that is set to a null string (for example, “ ”) is a variable with a value. Many environment variables are predefined and have default values. Environment variables store two kinds of data: • Data that controls code, which does not read the Cisco IOS configuration file. For example, the name of a boot loader helper file, which extends or patches the functionality of the boot loader can be stored as an environment variable. • Data that controls code, which is responsible for reading the Cisco IOS configuration file. For example, the name of the Cisco IOS configuration file can be stored as an environment variable. You can change the settings of the environment variables by accessing the boot loader or by using Cisco IOS commands. Under normal circumstances, it is not necessary to alter the setting of the environment variables. Note For complete syntax and usage information for the boot loader commands and environment variables, see the command reference for this release. Step 5 show boot Verify your entries. The boot system global command changes the setting of the BOOT environment variable. During the next boot cycle, the switch attempts to automatically boot up the system using information in the BOOT environment variable. Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file. Command Purpose

OL-12247-01 Chapter 3 Assigning the Switch IP Address and Default Gateway Modifying the Startup Configuration Table 3-4 describes the function of the most common environment variables. Table 3-4 Environment Variables Variable Boot Loader Command Cisco IOS Global Configuration Command BOOT set BOOT filesystem:/file-url ... A semicolon-separated list of executable files to try to load and execute when automatically booting. If the BOOT environment variable is not set, the system attempts to load and execute the first executable image it can find by using a recursive, depth-first search through the flash file system. If the BOOT variable is set but the specified images cannot be loaded, the system attempts to boot up the first bootable file that it can find in the flash file system. boot system {filesystem:/file-url ...| switch {number | all}} Specifies the Cisco IOS image to load during the next boot cycle and the stack members on which the image is loaded. This command changes the setting of the BOOT environment variable. MANUAL_BOOT set MANUAL_BOOT yes Decides whether the switch automatically or manually boots. Valid values are 1, yes, 0, and no. If it is set to no or 0, the boot loader attempts to automatically boot up the system. If it is set to anything else, you must manually boot up the switch from the boot loader mode. boot manual Enables manually booting the switch during the next boot cycle and changes the setting of the MANUAL_BOOT environment variable. The next time you reboot the system, the switch is in boot loader mode. To boot up the system, use the boot flash:filesystem:/file-url boot loader command, and specify the name of the bootable image. CONFIG_FILE set CONFIG_FILE flash:/file-url Changes the filename that Cisco IOS uses to read and write a nonvolatile copy of the system configuration. boot config-file flash:/file-url Specifies the filename that Cisco IOS uses to read and write a nonvolatile copy of the system configuration. This command changes the CONFIG_FILE environment variable. SWITCH_NUMBER set SWITCH_NUMBER stack-member-number Changes the member number of a stack member. switch current-stack-member-number renumber new-stack-member-number Note Changes the member number of a stack member. SWITCH_PRIORITY set SWITCH_PRIORITY stack-member-number Changes the priority value of a stack member. switch stack-member-number priority priority-number Note Changes the priority value of a stack member.

OL-12247-01 Chapter 3 Assigning the Switch IP Address and Default Gateway Scheduling a Reload of the Software Image When the switch is connected to a PC through the internal Ethernet management port, you can download or upload a configuration file to the boot loader by using TFTP. Make sure the environment variables in Table 3-5 are configured. Scheduling a Reload of the Software Image You can schedule a reload of the software image to occur on the switch at a later time (for example, late at night or during the weekend when the switch is used less), or you can synchronize a reload network-wide (for example, to perform a software upgrade on all switches in the network). Note A scheduled reload must take place within approximately 24 days. Configuring a Scheduled Reload To configure your switch to reload the software image at a later time, use one of these commands in privileged EXEC mode: • reload in [hh:]mm [text] This command schedules a reload of the software to take affect in the specified minutes or hours and minutes. The reload must take place within approximately 24 days. You can specify the reason for the reload in a string up to 255 characters in length. To reload a specific switch in a switch stack, use the reload slot stack-member-number privileged EXEC command. • reload at hh:mm [month day | day month] [text] This command schedules a reload of the software to take place at the specified time (using a 24-hour clock). If you specify the month and day, the reload is scheduled to take place at the specified time and date. If you do not specify the month and day, the reload takes place at the specified time on the current day (if the specified time is later than the current time) or on the next day (if the specified time is earlier than the current time). Specifying 00:00 schedules the reload for midnight. Table 3-5 Environment Variables for TFTP Variable Description MAC_ADDR Specifies the MAC address of the switch. Note We recommend that you do not modify this variable. However, if you modify this variable after the boot loader is up or the value is different than the saved value, enter this command before using TFTP. IP_ADDR Specifies the IP address and the subnet mask for the associated IP subnet of the switch. DEFAULT_ROUTER Specifies the IP address and subnet mask of the default gateway.

OL-12247-01 Chapter 3 Assigning the Switch IP Address and Default Gateway Scheduling a Reload of the Software Image Note Use the at keyword only if the switch system clock has been set (through Network Time Protocol (NTP), the hardware calendar, or manually). The time is relative to the configured time zone on the switch. To schedule reloads across several switches to occur simultaneously, the time on each switch must be synchronized with NTP. The reload command halts the system. If the system is not set to manually bootup, it reboots itself. Use the reload command after you save the switch configuration information to the startup configuration (copy running-config startup-config). If your switch is configured for manual booting, do not reload it from a virtual terminal. This restriction prevents the switch from entering the boot loader mode and thereby taking it from the remote user’s control. If you modify your configuration file, the switch prompts you to save the configuration before reloading. During the save operation, the system requests whether you want to proceed with the save if the CONFIG_FILE environment variable points to a startup configuration file that no longer exists. If you proceed in this situation, the system enters setup mode upon reload. This example shows how to reload the software on the switch on the current day at 7:30 p.m: Switch# reload at 19:30 Reload scheduled for 19:30:00 UTC Wed Jun 5 1996 (in 2 hours and 25 minutes) Proceed with reload? [confirm] This example shows how to reload the software on the switch at a future time: Switch# reload at 02:00 jun 20 Reload scheduled for 02:00:00 UTC Thu Jun 20 1996 (in 344 hours and 53 minutes) Proceed with reload? [confirm] To cancel a previously scheduled reload, use the reload cancel privileged EXEC command. Displaying Scheduled Reload Information To display information about a previously scheduled reload or to find out if a reload has been scheduled on the switch, use the show reload privileged EXEC command. It displays reload information including the time the reload is scheduled to occur and the reason for the reload (if it was specified when the reload was scheduled).

4-1 Cisco Catalyst Blade Switch 3120 for HP Software Configuration Guide OL-12247-01 4 Configuring Cisco IOS CNS Agents This chapter describes how to configure the Cisco IOS Cisco Network Services (CNS) agents on the switch. Unless otherwise noted, the term switch refers to a standalone switch and to a switch stack. Note For complete configuration information for the Cisco Configuration Engine, see this URL on Cisco.com http://www.cisco.com/en/US/products/sw/netmgtsw/ps4617/tsd_products_support_series_home.html For complete syntax and usage information for the commands used in this chapter, see the Cisco IOS Network Management Command Reference, Release 12.4 at this URL on Cisco.com: http://www.cisco.com/en/US/products/ps6350/products_command_reference_book09186a008042df72. html This chapter consists of these sections: • Understanding Cisco Configuration Engine Software, page 4-1 • Understanding Cisco IOS Agents, page 4-5 • Configuring Cisco IOS Agents, page 4-6 • Displaying CNS Configuration, page 4-14 Understanding Cisco Configuration Engine Software The Cisco Configuration Engine is network management software that acts as a configuration service for automating the deployment and management of network devices and services (see Figure 4-1). Each Configuration Engine manages a group of Cisco devices (switches and routers) and the services that they deliver, storing their configurations and delivering them as needed. The Configuration Engine automates initial configurations and configuration updates by generating device-specific configuration changes, sending them to the device, executing the configuration change, and logging the results. The Configuration Engine supports standalone and server modes and has these CNS components: • Configuration service (web server, file manager, and namespace mapping server) • Event service (event gateway) • Data service directory (data models and schema) In standalone mode, the Configuration Engine supports an embedded Directory Service. In this mode, no external directory or other data store is required. In server mode, the Configuration Engine supports the use of a user-defined external directory.

OL-12247-01 Chapter 4 Configuring Cisco IOS CNS Agents Understanding Cisco Configuration Engine Software Figure 4-1 Configuration Engine Architectural Overview These sections contain this conceptual information: • Configuration Service, page 4-2 • Event Service, page 4-3 • What You Should Know About the CNS IDs and Device Hostnames, page 4-3 Configuration Service The Configuration Service is the core component of the Cisco Configuration Engine. It consists of a configuration server that works with Cisco IOS CNS agents on the switch. The Configuration Service delivers device and service configurations to the switch for initial configuration and mass reconfiguration by logical groups. Switches receive their initial configuration from the Configuration Service when they start up on the network for the first time. The Configuration Service uses the CNS Event Service to send and receive configuration change events and to send success and failure notifications. The configuration server is a web server that uses configuration templates and the device-specific configuration information stored in the embedded (standalone mode) or remote (server mode) directory. Configuration templates are text files containing static configuration information in the form of CLI commands. In the templates, variables are specified by using Lightweight Directory Access Protocol (LDAP) URLs that reference the device-specific configuration information stored in a directory. The Cisco IOS agent can perform a syntax check on received configuration files and publish events to show the success or failure of the syntax check. The configuration agent can either apply configurations immediately or delay the application until receipt of a synchronization event from the configuration server. Configuration engine Service provider network Order entry configuration management Data service directory Configuration server Event service Web-based user interface 141327

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

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