Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
Text Part Number: OL-23145-01
Page 2
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL
STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
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
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at
www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership
relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the
document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
Understanding DHCP-based Autoconfiguration and Image Update3-5
DHCP Autoconfiguration3-5
DHCP Auto-Image Update3-5
Limitations and Restrictions3-6
Configuring DHCP-Based Autoconfiguration3-6
DHCP Server Configuration Guidelines3-6
Configuring the TFTP Server3-7
Configuring the DNS3-8
Configuring the Relay Device3-8
Obtaining Configuration Files3-9
Example Configuration3-9
Configuring the DHCP Auto Configuration and Image Update Features3-11
Configuring DHCP Autoconfiguration (Only Configuration File)3-11
Configuring DHCP Auto-Image Update (Configuration File and Image)3-12
Configuring the Client3-13
Manually Assigning IP Information3-14
iv
Checking and Saving the Running Configuration3-15
Modifying the Startup Configuration3-16
Default Boot Configuration3-17
Automatically Downloading a Configuration File3-17
Specifying the Filename to Read and Write the System Configuration3-17
Booting Manually3-18
Booting a Specific Software Image3-19
Controlling Environment Variables3-19
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 5
Scheduling a Reload of the Software Image3-21
Configuring a Scheduled Reload3-21
Displaying Scheduled Reload Information3-22
Enabling Automated CNS Configuration4-6
Enabling the CNS Event Agent4-7
Enabling the Cisco IOS CNS Agent4-9
Enabling an Initial Configuration4-9
Enabling a Partial Configuration4-12
CHAPTER
OL-23145-01
Displaying CNS Configuration4-13
5Clustering Switches5-1
Understanding Switch Clusters5-1
Cluster Command Switch Characteristics5-3
Standby Cluster Command Switch Characteristics5-3
Candidate Switch and Cluster Member Switch Characteristics5-3
Planning a Switch Cluster5-4
Automatic Discovery of Cluster Candidates and Members5-4
Discovery Through CDP Hops5-5
Discovery Through Non-CDP-Capable and Noncluster-Capable Devices5-6
Discovery Through Different VLANs5-6
Discovery Through Different Management VLANs5-7
Discovery of Newly Installed Switches5-8
Virtual IP Addresses5-9
Cisco IE 3010 Switch Software Configuration Guide
v
Page 6
Contents
Other Considerations for Cluster Standby Groups5-9
Automatic Recovery of Cluster Configuration5-10
IP Addresses5-11
Hostnames5-11
Passwords5-12
SNMP Community Strings5-12
TACACS+ and RADIUS5-12
LRE Profiles5-13
Using the CLI to Manage Switch Clusters5-13
Using SNMP to Manage Switch Clusters5-14
CHAPTER
6Administering the Switch6-1
Managing the System Time and Date6-1
Understanding the System Clock 6-1
Understanding Network Time Protocol6-2
Configuring NTP6-4
Default NTP Configuration6-4
Configuring NTP Authentication6-5
Configuring NTP Associations6-6
Configuring NTP Broadcast Service6-7
Configuring NTP Access Restrictions6-8
Configuring the Source IP Address for NTP Packets6-10
Displaying the NTP Configuration6-11
Configuring Time and Date Manually6-11
Setting the System Clock6-11
Displaying the Time and Date Configuration6-12
Configuring the Time Zone 6-12
Configuring Summer Time (Daylight Saving Time)6-13
Configuring a System Name and Prompt6-14
Default System Name and Prompt Configuration6-15
Configuring a System Name6-15
Understanding DNS6-15
Default DNS Configuration6-16
Setting Up DNS6-16
Displaying the DNS Configuration6-17
vi
Creating a Banner6-17
Default Banner Configuration6-17
Configuring a Message-of-the-Day Login Banner6-18
Configuring a Login Banner6-19
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 7
Managing the MAC Address Table6-19
Building the Address Table6-20
MAC Addresses and VLANs6-20
Default MAC Address Table Configuration6-21
Changing the Address Aging Time6-21
Removing Dynamic Address Entries6-22
Configuring MAC Address Change Notification Traps6-22
Configuring MAC Address Move Notification Traps6-24
Configuring MAC Threshold Notification Traps6-25
Adding and Removing Static Address Entries6-26
Configuring Unicast MAC Address Filtering6-27
Disabling MAC Address Learning on a VLAN6-28
Displaying Address Table Entries6-30
Managing the ARP Table6-30
Contents
CHAPTER
7Configuring the Switch Alarms7-1
Understanding IE 3010 Switch Alarms7-1
Global Status Monitoring Alarms7-2
FCS Error Hysteresis Threshold7-2
Port Status Monitoring Alarms7-2
Triggering Alarm Options7-3
Configuring IE 3010 External Alarms7-4
Configuring IE 3010 Switch Alarms7-6
Default Switch Alarm Configuration7-6
Configuring the Power Supply Alarms7-6
Configuring the Switch Temperature Alarms7-7
Setting the Primary Temperature Threshold for the Switch7-7
Setting a Secondary Temperature Threshold for the Switch7-8
Associating the Temperature Alarms to a Relay7-9
Configuring the FCS Bit Error Rate Alarm7-10
Setting the FCS Error Threshold7-10
Setting the FCS Error Hysteresis Threshold7-10
Configuring Alarm Profiles7-11
Creating or Modifying an Alarm Profile7-11
Attaching an Alarm Profile to a Specific Port7-12
Enabling SNMP Traps7-13
OL-23145-01
Displaying IE 3010 Switch Alarms Status7-13
Cisco IE 3010 Switch Software Configuration Guide
vii
Page 8
Contents
CHAPTER
CHAPTER
8Configuring SDM Templates8-1
Understanding the SDM Templates8-1
Configuring the Switch SDM Template8-2
SDM Template Configuration Guidelines8-2
Setting the SDM Template8-3
Displaying the SDM Templates8-4
9Configuring Switch-Based Authentication9-1
Preventing Unauthorized Access to Your Switch9-1
Protecting Access to Privileged EXEC Commands9-2
Default Password and Privilege Level Configuration9-3
Setting or Changing a Static Enable Password9-3
Protecting Enable and Enable Secret Passwords with Encryption9-4
Disabling Password Recovery9-5
Setting a Telnet Password for a Terminal Line9-6
Configuring Username and Password Pairs9-7
Configuring Multiple Privilege Levels9-8
Identifying the TACACS+ Server Host and Setting the Authentication Key9-13
Configuring TACACS+ Login Authentication9-14
Configuring TACACS+ Authorization for Privileged EXEC Access and Network Services9-16
Starting TACACS+ Accounting9-17
Establishing a Session with a Router if the AAA Server is Unreachable9-18
Displaying the TACACS+ Configuration9-18
Controlling Switch Access with RADIUS9-18
Understanding RADIUS9-18
RADIUS Operation9-20
RADIUS Change of Authorization9-20
Overview9-21
Change-of-Authorization Requests9-21
CoA Request Response Code9-22
CoA Request Commands9-24
viii
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 9
Configuring RADIUS9-27
Default RADIUS Configuration9-27
Identifying the RADIUS Server Host 9-28
Configuring RADIUS Login Authentication9-30
Defining AAA Server Groups9-32
Configuring RADIUS Authorization for User Privileged Access and Network Services9-34
Starting RADIUS Accounting9-35
Establishing a Session with a Router if the AAA Server is Unreachable9-36
Configuring Settings for All RADIUS Servers9-36
Configuring the Switch to Use Vendor-Specific RADIUS Attributes9-36
Configuring the Switch for Vendor-Proprietary RADIUS Server Communication9-38
Configuring CoA on the Switch9-39
Monitoring and Troubleshooting CoA Functionality9-40
Configuring RADIUS Server Load Balancing9-40
Displaying the RADIUS Configuration9-40
Contents
Controlling Switch Access with Kerberos9-40
Understanding Kerberos9-41
Kerberos Operation9-43
Authenticating to a Boundary Switch9-43
Obtaining a TGT from a KDC9-43
Authenticating to Network Services9-44
Configuring Kerberos9-44
Configuring the Switch for Local Authentication and Authorization9-44
Configuring the Switch for Secure Shell9-45
Understanding SSH9-46
SSH Servers, Integrated Clients, and Supported Versions9-46
Limitations9-46
Configuring SSH9-47
Configuration Guidelines9-47
Setting Up the Switch to Run SSH9-47
Configuring the SSH Server9-48
Displaying the SSH Configuration and Status9-49
Configuring the Switch for Secure Socket Layer HTTP9-50
VLAN Assignment, Guest VLAN, Restricted VLAN, and Inaccessible Authentication
Bypass10-36
MAC Authentication Bypass10-37
Maximum Number of Allowed Devices Per Port10-37
Configuring 802.1x Readiness Check10-37
Configuring Voice Aware 802.1x Security10-38
Configuring 802.1x Violation Modes10-39
Configuring 802.1x Authentication10-40
Configuring the Switch-to-RADIUS-Server Communication10-42
Configuring the Host Mode10-43
Configuring Periodic Re-Authentication10-44
Manually Re-Authenticating a Client Connected to a Port10-45
Changing the Quiet Period10-46
Changing the Switch-to-Client Retransmission Time10-46
Setting the Switch-to-Client Frame-Retransmission Number10-47
Setting the Re-Authentication Number10-48
Enabling MAC Move10-48
Enabling MAC Replace10-49
Configuring 802.1x Accounting10-50
Configuring a Guest VLAN10-51
Configuring a Restricted VLAN10-52
Configuring the Inaccessible Authentication Bypass Feature10-54
Configuring 802.1x Authentication with WoL10-56
Configuring MAC Authentication Bypass10-57
Contents
OL-23145-01
Cisco IE 3010 Switch Software Configuration Guide
xi
Page 12
Contents
Configuring 802.1x User Distribution10-58
Configuring NAC Layer 2 802.1x Validation10-59
Configuring an Authenticator and a Supplicant Switch with NEAT10-60
Configuring NEAT with Auto Smartports Macros10-61
Configuring 802.1x Authentication with Downloadable ACLs and Redirect URLs10-61
Configuring Downloadable ACLs10-62
Configuring a Downloadable Policy10-62
Configuring VLAN ID-based MAC Authentication10-64
Configuring Flexible Authentication Ordering10-64
Configuring Open1x10-65
Disabling 802.1x Authentication on the Port10-65
Resetting the 802.1x Authentication Configuration to the Default Values10-66
Displaying 802.1x Statistics and Status10-67
CHAPTER
11Configuring Web-Based Authentication11-1
Understanding Web-Based Authentication11-1
Device Roles11-2
Host Detection11-2
Session Creation11-2
Authentication Process11-3
Local Web Authentication Banner11-3
Web Authentication Customizable Web Pages11-5
Guidelines11-5
Web-based Authentication Interactions with Other Features11-7
Port Security11-7
LAN Port IP11-7
Gateway IP11-7
ACLs11-7
Context-Based Access Control11-8
802.1x Authentication11-8
EtherChannel11-8
Configuring Web-Based Authentication11-9
Default Web-Based Authentication Configuration11-9
Web-Based Authentication Configuration Guidelines and Restrictions11-9
Web-Based Authentication Configuration Task List11-10
Configuring the Authentication Rule and Interfaces11-10
Configuring AAA Authentication11-11
Configuring Switch-to-RADIUS-Server Communication 11-11
Configuring the HTTP Server11-13
xii
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 13
Customizing the Authentication Proxy Web Pages11-13
Specifying a Redirection URL for Successful Login11-15
Configuring an AAA Fail Policy11-15
Configuring the Web-Based Authentication Parameters11-16
Configuring a Web Authentication Local Banner11-16
Removing Web-Based Authentication Cache Entries11-17
Displaying Web-Based Authentication Status11-17
Contents
CHAPTER
12Configuring Interface Characteristics12-1
Understanding Interface Types12-1
Port-Based VLANs12-2
Switch Ports12-2
Access Ports12-2
Trunk Ports12-3
EtherChannel Port Groups12-3
Dual-Purpose Uplink Ports12-4
Power over Ethernet Ports12-4
Supported Protocols and Standards12-4
Powered-Device Detection and Initial Power Allocation12-5
Power Management Modes12-6
Power Monitoring and Power Policing12-7
Connecting Interfaces12-9
Using Interface Configuration Mode12-9
Procedures for Configuring Interfaces12-10
Configuring a Range of Interfaces12-10
Configuring and Using Interface Range Macros12-12
OL-23145-01
Configuring Ethernet Interfaces12-14
Default Ethernet Interface Configuration12-14
Setting the Type of a Dual-Purpose Uplink Port12-15
Configuring Interface Speed and Duplex Mode12-16
Speed and Duplex Configuration Guidelines12-17
Setting the Interface Speed and Duplex Parameters12-17
Configuring IEEE 802.3x Flow Control12-18
Configuring Auto-MDIX on an Interface12-19
Configuring a Power Management Mode on a PoE Port12-20
Budgeting Power for Devices Connected to a PoE Port12-22
Adding a Description for an Interface12-23
Configuring Layer 3 Interfaces12-24
Configuring the System MTU12-24
Cisco IE 3010 Switch Software Configuration Guide
xiii
Page 14
Contents
Monitoring and Maintaining the Interfaces12-26
Monitoring Interface Status12-26
Clearing and Resetting Interfaces and Counters12-27
Shutting Down and Restarting the Interface12-27
Supported VLANs14-2
VLAN Port Membership Modes14-3
Configuring Normal-Range VLANs14-4
Token Ring VLANs14-5
Normal-Range VLAN Configuration Guidelines14-5
Configuring Normal-Range VLANs14-6
Default Ethernet VLAN Configuration14-6
Creating or Modifying an Ethernet VLAN14-7
Deleting a VLAN14-8
Assigning Static-Access Ports to a VLAN14-9
xiv
Configuring Extended-Range VLANs14-10
Default VLAN Configuration14-10
Extended-Range VLAN Configuration Guidelines14-10
Creating an Extended-Range VLAN14-11
Creating an Extended-Range VLAN with an Internal VLAN ID14-12
Displaying VLANs14-13
Configuring VLAN Trunks14-14
Trunking Overview14-14
IEEE 802.1Q Configuration Considerations14-15
Default Layer 2 Ethernet Interface VLAN Configuration14-16
Configuring an Ethernet Interface as a Trunk Port14-16
Interaction with Other Features14-16
Configuring a Trunk Port14-17
Defining the Allowed VLANs on a Trunk14-18
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 15
Changing the Pruning-Eligible List14-19
Configuring the Native VLAN for Untagged Traffic14-19
Configuring Trunk Ports for Load Sharing14-20
Load Sharing Using STP Port Priorities14-20
Load Sharing Using STP Path Cost14-22
Configuring VMPS14-23
Understanding VMPS14-24
Dynamic-Access Port VLAN Membership14-24
Default VMPS Client Configuration14-25
VMPS Configuration Guidelines14-25
Configuring the VMPS Client14-26
Entering the IP Address of the VMPS14-26
Configuring Dynamic-Access Ports on VMPS Clients14-26
Reconfirming VLAN Memberships14-27
Changing the Reconfirmation Interval14-27
Changing the Retry Count14-28
Monitoring the VMPS14-28
Troubleshooting Dynamic-Access Port VLAN Membership14-29
VMPS Configuration Example14-29
Contents
CHAPTER
15Configuring VTP15-1
Understanding VTP15-1
The VTP Domain15-2
VTP Modes15-3
VTP Advertisements15-3
VTP Version 215-4
VTP Version 315-4
VTP Pruning15-5
Disabled State17-7
How a Switch or Port Becomes the Root Switch or Root Port17-7
Spanning Tree and Redundant Connectivity17-8
Spanning-Tree Address Management17-8
Accelerated Aging to Retain Connectivity17-8
Spanning-Tree Modes and Protocols17-9
Supported Spanning-Tree Instances17-9
Spanning-Tree Interoperability and Backward Compatibility17-10
STP and IEEE 802.1Q Trunks17-10
VLAN-Bridge Spanning Tree17-10
xvi
Configuring Spanning-Tree Features17-11
Default Spanning-Tree Configuration17-11
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 17
Spanning-Tree Configuration Guidelines17-12
Changing the Spanning-Tree Mode.17-13
Disabling Spanning Tree17-14
Configuring the Root Switch17-14
Configuring a Secondary Root Switch17-16
Configuring Port Priority17-16
Configuring Path Cost17-18
Configuring the Switch Priority of a VLAN17-19
Configuring Spanning-Tree Timers17-20
Configuring the Hello Time17-20
Configuring the Forwarding-Delay Time for a VLAN17-21
Configuring the Maximum-Aging Time for a VLAN17-21
Configuring the Transmit Hold-Count 17-22
Displaying the Spanning-Tree Status17-22
Contents
CHAPTER
18Configuring MSTP18-1
Understanding MSTP18-2
Multiple Spanning-Tree Regions18-2
IST, CIST, and CST18-2
Operations Within an MST Region18-3
Operations Between MST Regions18-3
IEEE 802.1s Terminology18-5
Hop Count18-5
Boundary Ports18-6
IEEE 802.1s Implementation18-6
Port Role Naming Change18-6
Interoperation Between Legacy and Standard Switches18-7
Detecting Unidirectional Link Failure18-7
Interoperability with IEEE 802.1D STP18-8
Understanding RSTP18-8
Port Roles and the Active Topology18-9
Rapid Convergence18-9
Synchronization of Port Roles18-11
Bridge Protocol Data Unit Format and Processing18-12
MSTP Configuration Guidelines18-14
Specifying the MST Region Configuration and Enabling MSTP18-15
Configuring the Root Switch18-17
Configuring a Secondary Root Switch18-18
Configuring Port Priority 18-19
Configuring Path Cost18-20
Configuring the Switch Priority18-21
Configuring the Hello Time18-22
Configuring the Forwarding-Delay Time18-23
Configuring the Maximum-Aging Time18-23
Configuring the Maximum-Hop Count18-24
Specifying the Link Type to Ensure Rapid Transitions18-24
Designating the Neighbor Type18-25
Restarting the Protocol Migration Process18-25
Default Optional Spanning-Tree Configuration19-9
Optional Spanning-Tree Configuration Guidelines19-10
Enabling Port Fast19-10
Enabling BPDU Guard19-11
Enabling BPDU Filtering19-12
Enabling UplinkFast for Use with Redundant Links19-13
Enabling BackboneFast19-13
Enabling EtherChannel Guard19-14
Enabling Root Guard19-15
Enabling Loop Guard19-15
xviii
Displaying the Spanning-Tree Status19-16
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 19
Contents
CHAPTER
20Configuring Flex Links and the MAC Address-Table Move Update Feature20-1
Understanding Flex Links and the MAC Address-Table Move Update20-1
Flex Links20-1
VLAN Flex Link Load Balancing and Support20-2
Flex Link Multicast Fast Convergence20-3
Learning the Other Flex Link Port as the mrouter Port20-3
Generating IGMP Reports20-3
Leaking IGMP Reports20-4
Configuration Examples20-4
MAC Address-Table Move Update20-6
Configuring Flex Links and the MAC Address-Table Move Update20-7
Default Configuration20-7
Configuration Guidelines20-8
Configuring Flex Links20-8
Configuring VLAN Load Balancing on Flex Links20-10
Configuring the MAC Address-Table Move Update Feature20-12
Monitoring Flex Links and the MAC Address-Table Move Update20-14
CHAPTER
21Configuring DHCP Features and IP Source Guard Features21-1
Understanding DHCP Snooping21-1
DHCP Server21-2
DHCP Relay Agent21-2
DHCP Snooping21-2
Option-82 Data Insertion21-4
Cisco IOS DHCP Server Database21-7
DHCP Snooping Binding Database21-7
Configuring DHCP Snooping21-8
Default DHCP Snooping Configuration21-9
DHCP Snooping Configuration Guidelines21-9
Configuring the DHCP Relay Agent 21-11
Specifying the Packet Forwarding Address21-11
Enabling DHCP Snooping and Option 8221-12
Enabling the Cisco IOS DHCP Server Database21-14
Enabling the DHCP Snooping Binding Database Agent21-14
Displaying DHCP Snooping Information21-15
Understanding IP Source Guard21-15
Source IP Address Filtering21-16
Source IP and MAC Address Filtering21-16
IP Source Guard for Static Hosts21-16
OL-23145-01
Cisco IE 3010 Switch Software Configuration Guide
xix
Page 20
Contents
Configuring IP Source Guard21-17
Default IP Source Guard Configuration21-17
IP Source Guard Configuration Guidelines21-17
Enabling IP Source Guard21-18
Configuring IP Source Guard for Static Hosts21-19
Configuring IP Source Guard for Static Hosts on a Layer 2 Access Port21-19
Configuring IP Source Guard for Static Hosts on a Private VLAN Host Port21-24
Displaying IP Source Guard Information21-26
Understanding DHCP Server Port-Based Address Allocation21-26
Configuring DHCP Server Port-Based Address Allocation21-26
Displaying DHCP Server Port-Based Address Allocation21-29
CHAPTER
CHAPTER
22Configuring Dynamic ARP Inspection22-1
Understanding Dynamic ARP Inspection22-1
Interface Trust States and Network Security22-3
Rate Limiting of ARP Packets22-4
Relative Priority of ARP ACLs and DHCP Snooping Entries22-4
Logging of Dropped Packets22-4
Configuring Dynamic ARP Inspection22-5
Default Dynamic ARP Inspection Configuration22-5
Dynamic ARP Inspection Configuration Guidelines22-5
Configuring Dynamic ARP Inspection in DHCP Environments22-7
Configuring ARP ACLs for Non-DHCP Environments22-8
Limiting the Rate of Incoming ARP Packets22-10
Performing Validation Checks22-11
Configuring the Log Buffer22-12
IGMP Versions23-2
Joining a Multicast Group23-3
Leaving a Multicast Group23-5
Immediate Leave 23-5
IGMP Configurable-Leave Timer23-5
IGMP Report Suppression23-5
xx
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 21
Configuring IGMP Snooping23-6
Default IGMP Snooping Configuration23-6
Enabling or Disabling IGMP Snooping23-7
Setting the Snooping Method23-8
Configuring a Multicast Router Port23-9
Configuring a Host Statically to Join a Group23-10
Enabling IGMP Immediate Leave23-10
Configuring the IGMP Leave Timer23-11
Configuring TCN-Related Commands23-12
Controlling the Multicast Flooding Time After a TCN Event23-12
Recovering from Flood Mode23-12
Disabling Multicast Flooding During a TCN Event23-13
Configuring the IGMP Snooping Querier23-14
Disabling IGMP Report Suppression23-15
Displaying IGMP Snooping Information23-15
Contents
CHAPTER
Understanding Multicast VLAN Registration23-17
Using MVR in a Multicast Television Application23-17
Configuring MVR23-19
Default MVR Configuration23-19
MVR Configuration Guidelines and Limitations23-19
Configuring MVR Global Parameters23-20
Configuring MVR Interfaces23-21
Displaying MVR Information23-23
Configuring IGMP Filtering and Throttling23-23
Default IGMP Filtering and Throttling Configuration23-24
Configuring IGMP Profiles23-24
Applying IGMP Profiles23-26
Setting the Maximum Number of IGMP Groups23-26
Configuring the IGMP Throttling Action23-27
Displaying IGMP Filtering and Throttling Configuration23-28
24Configuring Port-Based Traffic Control24-1
Configuring Storm Control24-1
Understanding Storm Control24-1
Default Storm Control Configuration24-3
Configuring Storm Control and Threshold Levels24-3
OL-23145-01
Configuring Protected Ports24-5
Default Protected Port Configuration24-5
Protected Port Configuration Guidelines24-5
Cisco IE 3010 Switch Software Configuration Guide
xxi
Page 22
Contents
Configuring a Protected Port24-6
Configuring Port Blocking24-6
Default Port Blocking Configuration24-7
Blocking Flooded Traffic on an Interface24-7
Configuring Port Security24-7
Understanding Port Security24-8
Secure MAC Addresses24-8
Security Violations24-9
Default Port Security Configuration24-10
Port Security Configuration Guidelines24-10
Enabling and Configuring Port Security24-12
Enabling and Configuring Port Security Aging24-16
Port Security and Private VLANs24-17
Displaying Port-Based Traffic Control Settings24-18
CHAPTER
CHAPTER
25Configuring CDP25-1
Understanding CDP25-1
Configuring CDP25-2
Default CDP Configuration25-2
Configuring the CDP Characteristics25-3
Disabling and Enabling CDP25-3
Disabling and Enabling CDP on an Interface25-4
Monitoring and Maintaining CDP25-5
26Configuring LLDP, LLDP-MED, and Wired Location Service26-1
Understanding LLDP, LLDP-MED, and Wired Location Service26-1
LLDP-MED26-2
Wired Location Service26-3
Configuring LLDP, LLDP-MED, and Wired Location Service26-4
Monitoring and Maintaining LLDP, LLDP-MED, and Wired Location Service26-10
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 23
Contents
CHAPTER
CHAPTER
27Configuring UDLD27-1
Understanding UDLD27-1
Modes of Operation27-1
Methods to Detect Unidirectional Links27-2
Configuring UDLD27-3
Default UDLD Configuration27-4
Configuration Guidelines27-4
Enabling UDLD Globally27-5
Enabling UDLD on an Interface27-5
Resetting an Interface Disabled by UDLD27-6
Displaying UDLD Status27-6
28Configuring SPAN and RSPAN28-1
Understanding SPAN and RSPAN28-1
Local SPAN28-2
Remote SPAN28-2
SPAN and RSPAN Concepts and Terminology28-3
SPAN and RSPAN Interaction with Other Features28-8
OL-23145-01
Configuring SPAN and RSPAN28-9
Default SPAN and RSPAN Configuration28-9
Configuring Local SPAN28-10
SPAN Configuration Guidelines28-10
Creating a Local SPAN Session28-11
Creating a Local SPAN Session and Configuring Incoming Traffic28-13
Specifying VLANs to Filter28-14
Configuring RSPAN28-15
RSPAN Configuration Guidelines28-15
Configuring a VLAN as an RSPAN VLAN28-16
Creating an RSPAN Source Session28-17
Creating an RSPAN Destination Session28-18
Creating an RSPAN Destination Session and Configuring Incoming Traffic28-19
Specifying VLANs to Filter28-21
Cisco IE 3010 Switch Software Configuration Guide
xxiii
Page 24
Contents
Displaying SPAN and RSPAN Status28-22
CHAPTER
CHAPTER
29Configuring RMON29-1
Understanding RMON29-1
Configuring RMON29-2
Default RMON Configuration29-3
Configuring RMON Alarms and Events29-3
Collecting Group History Statistics on an Interface29-5
Collecting Group Ethernet Statistics on an Interface29-5
Displaying RMON Status29-6
30Configuring System Message Logging30-1
Understanding System Message Logging30-1
Configuring System Message Logging30-2
System Log Message Format30-2
Default System Message Logging Configuration30-3
Disabling Message Logging30-4
Setting the Message Display Destination Device30-5
Synchronizing Log Messages30-6
Enabling and Disabling Time Stamps on Log Messages30-7
Enabling and Disabling Sequence Numbers in Log Messages30-8
Defining the Message Severity Level30-8
Limiting Syslog Messages Sent to the History Table and to SNMP30-10
Enabling the Configuration-Change Logger30-10
Configuring UNIX Syslog Servers30-11
Logging Messages to a UNIX Syslog Daemon30-12
Configuring the UNIX System Logging Facility30-12
CHAPTER
xxiv
Displaying the Logging Configuration30-13
31Configuring SNMP31-1
Understanding SNMP31-1
SNMP Versions31-2
SNMP Manager Functions31-3
SNMP Agent Functions31-4
SNMP Community Strings31-4
Using SNMP to Access MIB Variables 31-4
SNMP Notifications31-5
SNMP ifIndex MIB Object Values31-5
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 25
Configuring SNMP31-6
Default SNMP Configuration31-6
SNMP Configuration Guidelines31-6
Disabling the SNMP Agent31-7
Configuring Community Strings31-8
Configuring SNMP Groups and Users31-9
Configuring SNMP Notifications31-11
Setting the CPU Threshold Notification Types and Values31-15
Setting the Agent Contact and Location Information31-16
Limiting TFTP Servers Used Through SNMP31-16
SNMP Examples31-17
Displaying SNMP Status31-18
Contents
CHAPTER
32Configuring Network Security with ACLs32-1
Understanding ACLs32-1
Supported ACLs32-2
Handling Fragmented and Unfragmented Traffic32-3
Configuring IPv4 ACLs32-4
Creating Standard and Extended IPv4 ACLs32-5
Access List Numbers32-6
ACL Logging32-6
Creating a Numbered Standard ACL32-7
Creating a Numbered Extended ACL32-8
Resequencing ACEs in an ACL32-12
Creating Named Standard and Extended ACLs32-12
Using Time Ranges with ACLs32-14
Including Comments in ACLs32-16
Applying an IPv4 ACL to a Terminal Line32-17
Applying an IPv4 ACL to an Interface32-17
Hardware and Software Treatment of IP ACLs32-19
Troubleshooting ACLs32-19
IPv4 ACL Configuration Examples32-20
Numbered ACLs32-22
Extended ACLs32-22
Named ACLs32-22
Time Range Applied to an IP ACL32-23
Commented IP ACL Entries32-23
ACL Logging32-24
OL-23145-01
Creating Named MAC Extended ACLs32-25
Cisco IE 3010 Switch Software Configuration Guide
xxv
Page 26
Contents
Applying a MAC ACL to a Layer 2 Interface32-26
Displaying IPv4 ACL Configuration32-28
CHAPTER
33Configuring QoS33-1
Understanding QoS33-1
Basic QoS Model33-3
Classification33-4
Classification Based on QoS ACLs33-7
Classification Based on Class Maps and Policy Maps33-7
Policing and Marking33-8
Policing on Physical Ports33-9
Policing on SVIs33-10
Mapping Tables33-12
Queueing and Scheduling Overview33-13
Weighted Tail Drop33-13
SRR Shaping and Sharing33-14
Queueing and Scheduling on Ingress Queues33-14
Queueing and Scheduling on Egress Queues33-16
Packet Modification33-18
Configuring Auto-QoS33-18
Generated Auto-QoS Configuration33-19
Effects of Auto-QoS on the Configuration33-24
Auto-QoS Configuration Guidelines33-24
Enabling Auto-QoS for VoIP33-25
Auto-QoS Configuration Example33-27
xxvi
Displaying Auto-QoS Information33-28
Configuring Standard QoS33-29
Default Standard QoS Configuration33-29
Default Ingress Queue Configuration33-30
Default Egress Queue Configuration33-30
Default Mapping Table Configuration33-31
Standard QoS Configuration Guidelines33-32
QoS ACL Guidelines33-32
Applying QoS on Interfaces33-32
Policing Guidelines33-33
General QoS Guidelines33-33
Enabling QoS Globally33-34
Enabling VLAN-Based QoS on Physical Ports33-34
Configuring Classification Using Port Trust States33-35
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 27
Configuring the Trust State on Ports within the QoS Domain33-35
Configuring the CoS Value for an Interface33-37
Configuring a Trusted Boundary to Ensure Port Security33-37
Enabling DSCP Transparency Mode33-39
Configuring the DSCP Trust State on a Port Bordering Another QoS Domain33-39
Configuring a QoS Policy33-41
Classifying Traffic by Using ACLs33-42
Classifying Traffic by Using Class Maps33-45
Classifying, Policing, and Marking Traffic on Physical Ports by Using Policy Maps33-47
Classifying, Policing, and Marking Traffic on SVIs by Using Hierarchical Policy Maps 33-51
Classifying, Policing, and Marking Traffic by Using Aggregate Policers33-57
Configuring DSCP Maps33-59
Configuring the CoS-to-DSCP Map33-59
Configuring the IP-Precedence-to-DSCP Map33-60
Configuring the Policed-DSCP Map33-61
Configuring the DSCP-to-CoS Map33-62
Configuring the DSCP-to-DSCP-Mutation Map33-63
Configuring Ingress Queue Characteristics33-65
Mapping DSCP or CoS Values to an Ingress Queue and Setting WTD Thresholds33-65
Allocating Buffer Space Between the Ingress Queues33-67
Allocating Bandwidth Between the Ingress Queues33-67
Configuring the Ingress Priority Queue33-68
Configuring Egress Queue Characteristics33-69
Configuration Guidelines33-70
Allocating Buffer Space to and Setting WTD Thresholds for an Egress Queue-Set33-70
Mapping DSCP or CoS Values to an Egress Queue and to a Threshold ID33-72
Configuring SRR Shaped Weights on Egress Queues33-73
Configuring SRR Shared Weights on Egress Queues33-74
Configuring the Egress Expedite Queue33-75
Limiting the Bandwidth on an Egress Interface33-76
Contents
CHAPTER
OL-23145-01
Displaying Standard QoS Information33-77
34Configuring EtherChannels and Link-State Tracking34-1
Understanding EtherChannels34-1
EtherChannel Overview34-2
Port-Channel Interfaces34-3
Port Aggregation Protocol34-4
PAgP Modes34-4
PAgP Interaction with Virtual Switches and Dual-Active Detection34-5
Cisco IE 3010 Switch Software Configuration Guide
xxvii
Page 28
Contents
PAgP Interaction with Other Features34-5
Link Aggregation Control Protocol34-5
LACP Modes34-6
LACP Interaction with Other Features34-6
EtherChannel On Mode34-6
Load Balancing and Forwarding Methods34-7
Using Cisco IOS IP SLAs to Measure Network Performance35-3
IP SLAs Responder and IP SLAs Control Protocol35-4
Response Time Computation for IP SLAs35-4
IP SLAs Operation Scheduling35-5
IP SLAs Operation Threshold Monitoring35-5
Configuring IP SLAs Operations35-6
Default Configuration35-6
Configuration Guidelines35-6
Configuring the IP SLAs Responder35-7
Analyzing IP Service Levels by Using the UDP Jitter Operation35-8
Analyzing IP Service Levels by Using the ICMP Echo Operation35-11
xxviii
Monitoring IP SLAs Operations35-13
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 29
Contents
CHAPTER
36Troubleshooting36-1
Recovering from a Software Failure36-2
Recovering from a Lost or Forgotten Password36-3
Recovering from Lost Cluster Member Connectivity36-4
Preventing Autonegotiation Mismatches36-4
Troubleshooting Power over Ethernet Switch Ports36-5
Disabled Port Caused by Power Loss36-5
Disabled Port Caused by False Link Up36-5
SFP Module Security and Identification36-5
Monitoring SFP Module Status36-6
Using Ping36-6
Understanding Ping 36-6
Using Layer 2 Traceroute36-6
Understanding Layer 2 Traceroute36-7
Usage Guidelines36-7
Displaying the Physical Path36-8
Using IP Traceroute36-8
Understanding IP Traceroute 36-8
Executing IP Traceroute36-9
Using TDR36-10
Understanding TDR36-10
Running TDR and Displaying the Results36-10
Using Debug Commands36-11
Enabling Debugging on a Specific Feature36-11
Enabling All-System Diagnostics36-12
Redirecting Debug and Error Message Output36-12
Possible Symptoms of High CPU Utilization36-15
Verifying the Problem and Cause36-15
Troubleshooting Power over Ethernet (PoE)36-17
OL-23145-01
Cisco IE 3010 Switch Software Configuration Guide
xxix
Page 30
Contents
APPENDIX
APPENDIX
ASupported MIBsA-1
MIB ListA-1
Using FTP to Access the MIB FilesA-3
BWorking with the Cisco IOS File System, Configuration Files, and Software ImagesB-1
Working with the Flash File SystemB-1
Displaying Available File SystemsB-1
Detecting an Unsupported SD Flash Memory CardB-2
SD Flash Memory Card LEDB-3
Setting the Default File SystemB-3
Displaying Information about Files on a File SystemB-4
Changing Directories and Displaying the Working DirectoryB-4
Creating and Removing DirectoriesB-5
Copying FilesB-5
Deleting FilesB-6
Creating, Displaying, and Extracting tar FilesB-6
Creating a tar FileB-7
Displaying the Contents of a tar FileB-7
Extracting a tar FileB-8
Displaying the Contents of a FileB-8
Working with Configuration FilesB-9
Guidelines for Creating and Using Configuration FilesB-9
Configuration File Types and Location nB-10
Creating a Configuration File By Using a Text EditorB-10
Copying Configuration Files By Using TFTPB-10
Preparing to Download or Upload a Configuration File B y Using TFTPB-10
Downloading the Configuration File By Using TFTPB-11
Uploading the Configuration File By Using TFTPB-12
Copying Configuration Files By Using FTPB-12
Preparing to Download or Upload a Configuration File By Using FTPB-13
Downloading a Configuration File By Using FTPB-13
Uploading a Configuration File By Using FTPB-14
Copying Configuration Files By Using RCPB-15
Preparing to Download or Upload a Configuration File By Using RCPB-16
Downloading a Configuration File By Using RCPB-17
Uploading a Configuration File By Using RCPB-18
Clearing Configuration InformationB-18
Clearing the Startup Configuration FileB-19
Deleting a Stored Configuration FileB-19
xxx
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 31
Replacing and Rolling Back ConfigurationsB-19
Understanding Configuration Replacement and RollbackB-19
Configuration GuidelinesB-20
Configuring the Configuration ArchiveB-21
Performing a Configuration Replacement or Rollback OperationB-21
Working with Software ImagesB-22
Image Location on the SwitchB-23
tar File Format of Images on a Server or Cisco.comB-23
Copying Image Files By Using TFTPB-24
Preparing to Download or Upload an Image File By Using TFTPB-24
Downloading an Image File By Using TFTPB-25
Uploading an Image File By Using TFTPB-27
Copying Image Files By Using FTPB-27
Preparing to Download or Upload an Image File By Using FTPB-28
Downloading an Image File By Using FTPB-29
Uploading an Image File By Using FTPB-30
Copying Image Files By Using RCPB-31
Preparing to Download or Upload an Image File By Using RCPB-32
Downloading an Image File By Using RCPB-33
Uploading an Image File By Using RCPB-34
Contents
APPENDIX
CUnsupported Commands in Cisco IOS Release 12.2(53)EZC-1
Unsupported Global Configuration CommandC-7
Unsupported Interface Configuration CommandC-7
VLANC-7
Unsupported Global Configuration CommandC-7
Unsupported User EXEC CommandsC-8
Unsupported VLAN Database CommandsC-8
I
NDEX
xxxii
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 33
Audience
Purpose
Preface
This guide is for the networking professional managing the IE 3010 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.
The switch is supported by the Layer 2 LAN base image. Layer 3 routing functionality is not supported.
This guide provides the information that you need to configure Cisco IOS software features on your
switch. This guide provides procedures for using the commands that have been created or changed for
use with the switch. It does not provide detailed information about these commands. For detailed
information about these commands, see the IE 3010 Switch Command Reference for this release. For
information about the standard Cisco IOS Release 12.2 commands, see the Cisco IOS documentation set
available from the Cisco.com home page at Documentation > Cisco IOS Software.
This guide does not provide detailed information on the graphical user interfaces (GUIs) for the
embedded device manager. However, the concepts in this guide are applicable to the GUI user. For
information about the device manager, see the switch online help.
This guide does not describe system messages you might encounter or how to install your switch. For
more information, see the IE 3010 Switch System Message Guide for this release and the IE 3010 Switch Hardware Installation Guide.
For documentation updates, see the release notes for this release.
Conventions
This publication uses these conventions to convey instructions and information:
Command descriptions use these conventions:
•Commands and keywords are in boldface text.
•Arguments for which you supply values are in italic.
OL-23145-01
•Square brackets ([ ]) mean optional elements.
•Braces ({ }) group required choices, and vertical bars ( | ) separate the alternative elements.
Cisco IE 3010 Switch Software Configuration Guide
xxxiii
Page 34
Preface
•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:
NoteMeans reader take note. Notes contain helpful suggestions or references to materials not contained in
this manual.
CautionMeans 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:
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.
technical documentation, at:
New in Cisco Product Documentation, which also lists all new and
OL-23145-01
Cisco IE 3010 Switch Software Configuration Guide
xxxv
Page 36
Preface
xxxvi
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 37
Features
CHA PTER
1
Overview
This chapter provides these topics about the IE 3010 switch software:
•Features, page 1-1
•Default Settings After Initial Switch Configuration, page 1-11
•Network Configuration Examples, page 1-13
•Where to Go Next, page 1-14
In this document, IP refers to IP Version 4 (IPv4).
The switch ships with the LAN base image that supports basic Layer 2 intelligent features, such as access
control lists (ACLs) and quality of service (QoS).
Some features described in this chapter are available only on the cryptographic (supports encryption)
version of the software. You must obtain authorization to use this feature and to download the
cryptographic version of the software from Cisco.com. For more information, see the release notes for
this release.
•Ease-of-Deployment and Ease-of-Use Features, page 1-2
•Performance Features, page 1-2
•Management Options, page 1-3
•Manageability Features, page 1-4
•Availability and Redundancy Features, page 1-5
•VLAN Features, page 1-6
•Security Features, page 1-6
•QoS and CoS Features, page 1-9
•Monitoring Features, page 1-10
OL-23145-01
Cisco IE 3010 Switch Software Configuration Guide
1-1
Page 38
Features
Ease-of-Deployment and Ease-of-Use Features
•Express Setup for quickly configuring a switch for the first time with basic IP information, contact
information, switch and Telnet passwords, and Simple Network Management Protocol (SNMP)
information through a browser-based program. For more information about Express Setup, see the
getting started guide.
•User-defined and Cisco-default Smartports macros for creating custom switch configurations for
simplified deployment across the network.
•An embedded device manager GUI for configuring and monitoring a single switch through a web
browser. For information about launching the device manager, see the getting started guide. For more
information about the device manager, see the switch online help.
•Switch clustering technology for
–
Unified configuration, monitoring, authentication, and software upgrade of multiple,
cluster-capable switches, regardless of their geographic proximity and interconnection media,
including Ethernet, Fast Ethernet, Fast EtherChannel, small form-factor pluggable (SFP)
modules, Gigabit Ethernet, and Gigabit EtherChannel connections. For a list of cluster-capable
switches, see the release notes.
Chapter 1 Overview
–
Automatic discovery of candidate switches and creation of clusters of up to 16 switches that can
be managed through a single IP address.
–
Extended discovery of cluster candidates that are not directly connected to the command switch.
Performance Features
•Cisco EnergyWise manages the energy usage of power over Ethernet (PoE) entities.
For more information, see the Cisco EnergyWise Version 2 Configuration Guide on Cisco.com.
•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/1000 Mb/s
interfaces and on 10/100/1000 BASE-TX SFP module interfaces that enables the interface to
automatically detect the required cable connection type (straight-through or crossover) and to
configure the connection appropriately
•Support for up to 1546 bytes routed frames, up to 9000 bytes for frames that are bridged in hardware,
and up to 2000 bytes for frames that are bridged by software
•IEEE 802.3x flow control on all ports (the switch does not send pause frames)
•EtherChannel for enhanced fault tolerance and for providing up to 8 Gb/s (Gigabit EtherChannel)
or 800 Mb/s (Fast EtherChannel) full-duplex bandwidth among switches, routers, and servers
•Port Aggregation Protocol (PAgP) and Link Aggregation Control Protocol (LACP) for automatic
creation of EtherChannel links
1-2
•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
Cisco IE 3010 Switch Software Configuration Guide
1, 2, and 3:
OL-23145-01
Page 39
Chapter 1 Overview
Features
–
(For CGMP devices) CGMP for limiting multicast traffic to specified end stations and reducing
overall network traffic
–
(For IGMP devices) IGMP snooping for forwarding multimedia and multicast traffic
•IGMP report suppression for sending only one IGMP report per multicast router query to the
multicast devices (supported only for IGMPv1 or IGMPv2 queries)
•IGMP snooping querier support to configure switch to generate periodic IGMP general query
messages
•IGMP helper to allow the switch to forward a host request to join a multicast stream to a specific IP
destination address
•IGMP filtering for controlling the set of multicast groups to which hosts on a switch port can belong
•IGMP throttling for configuring the action when the maximum number of entries is in the IGMP
forwarding table
•IGMP leave timer for configuring the leave latency for the network
•Switch Database Management (SDM) templates for allocating system resources to maximize
support for user-selected features
•Cisco IOS IP Service Level Agreements (SLAs), a part of Cisco IOS software that uses active traffic
monitoring for measuring network performance.
•Configurable small-frame arrival threshold to prevent storm control when small frames (64 bytes or
less) arrive on an interface at a specified rate (the threshold)
•Flex Link Multicast Fast Convergence to reduce the multicast traffic convergence time after a Flex
Link failure
•RADIUS server load balancing to allow access and authentication requests to be distributed evenly
across a server group.
•Support for QoS marking of CPU-generated traffic and queue CPU-generated traffic on the egress
network ports.
Management Options
•An embedded device manager—The device manager is a GUI that is integrated in the software
image. You use it to configure and to monitor a single switch. For information about launching the
device manager, see the getting started guide. For more information about the device manager, see the
switch online help.
•CLI—The Cisco IOS software supports desktop- and multilayer-switching features. You can access
the CLI either by connecting your management station directly to the switch console port or by using
Telnet from a remote management station. For more information about the CLI, see
“Using the Command-Line Interface.”
•SNMP—SNMP management applications such as CiscoWorks2000 LAN Management Suite (LMS)
and HP OpenView. You can manage from an SNMP-compatible management station that is running
platforms such as HP OpenView or SunNet Manager. The switch supports a comprehensive set of
MIB extensions and four remote monitoring (RMON) groups. For more information about using
SNMP, see
Chapter 2,
Chapter 31, “Configuring SNMP.”
OL-23145-01
Cisco IE 3010 Switch Software Configuration Guide
1-3
Page 40
Features
•Cisco IOS Configuration Engine (previously known to as the Cisco IOS CNS
agent)-—Configuration service automates the deployment and management of network devices and
services. You can automate initial configurations and configuration updates by generating
switch-specific configuration changes, sending them to the switch, executing the configuration
change, and logging the results.
For more information about CNS, see Chapter 4, “Configuring Cisco IOS Configuration Engine.”
Manageability Features
•CNS embedded agents for automating switch management, configuration storage, and delivery
•DHCP for automating configuration of switch information (such as IP address, default gateway,
hostname, and Domain Name System [DNS] and TFTP server names)
•DHCP relay for forwarding User Datagram Protocol (UDP) broadcasts, including IP address
requests, from DHCP clients
•DHCP server for automatic assignment of IP addresses and other DHCP options to IP hosts
•DHCP-based autoconfiguration and image update to download a specified configuration a new
image to a large number of switches
Chapter 1 Overview
•DHCP server port-based address allocation for the preassignment of an IP address to a switch port
•Directed unicast requests to a DNS server for identifying a switch through its IP address and its
corresponding hostname and to a TFTP server for administering software upgrades from a TFTP
server
•Address Resolution Protocol (ARP) for identifying a switch through its IP address and its
corresponding MAC address
•Unicast MAC address filtering to drop packets with specific source or destination MAC addresses
•Configurable MAC address scaling that allows disabling MAC address learning on a VLAN to limit
the size of the MAC address table
•Cisco Discovery Protocol (CDP) Versions 1 and 2 for network topology discovery and mapping
between the switch and other Cisco devices on the network
•Link Layer Discovery Protocol (LLDP) and LLDP Media Endpoint Discovery (LLDP-MED) for
interoperability with third-party IP phones
•LLDP media extensions (LLDP-MED) location TLV that provides location information from the
switch to the endpoint device
•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
•Support for the SSM PIM protocol to optimize multicast applications, such as video
•Configuration logging to log and to view changes to the switch configuration
1-4
•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
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 41
Chapter 1 Overview
Features
•In-band management access for up to five simultaneous, encrypted Secure Shell (SSH) connections
for multiple CLI-based sessions over the network
•In-band management access through SNMP Versions 1, 2c, and 3 get and set requests
•Out-of-band management access through the switch console port to a directly attached terminal or
to a remote terminal through a serial connection or a modem
•Secure Copy Protocol (SCP) feature to provide a secure and authenticated method for copying
switch configuration or switch image files (requires the cryptographic version of the software)
•Configuration replacement and rollback to replace the running configuration on a switch with any
saved Cisco IOS configuration file
•Disabling MAC address learning on a VLAN
•DHCP server port-based address allocation for the preassignment of an IP address to a switch port.
•Wired location service sends location and attachment tracking information for connected devices to
a Cisco Mobility Services Engine (MSE).
•CPU utilization threshold trap monitors CPU utilization.
•LLDP-MED network-policy profile time, length, value (TLV) for creating a profile for voice and
voice-signalling by specifying the values for VLAN, class of service (CoS), differentiated services
code point (DSCP), and tagging mode.
•Support for including a hostname in the option 12 field of DHCPDISCOVER packets. This provides
identical configuration files to be sent by using the DHCP protocol.
•DHCP Snooping enhancement to support the selection of a fixed string-based format for the
circuit-id sub-option of the Option 82 DHCP field.
Availability and Redundancy Features
•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
•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
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)
802.1w Rapid Spanning Tree
OL-23145-01
–
BPDU filtering for preventing a Port Fast-enabled port from sending or receiving BPDUs
Cisco IE 3010 Switch Software Configuration Guide
1-5
Page 42
Features
VLAN Features
Chapter 1 Overview
–
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.
•Support for up to 1005 VLANs for assigning users to VLANs associated with appropriate network
resources, traffic patterns, and bandwidth
•Support for VLAN IDs in the 1 to 4094 range as allowed by the IEEE 802.1Q standard
•VLAN Query Protocol (VQP) for dynamic VLAN membership
•IEEE 802.1Q trunking encapsulation on all ports for network moves, adds, and changes;
management and control of broadcast and multicast traffic; and network security by establishing
VLAN groups for high-security users and network resources
•Dynamic Trunking Protocol (DTP) for negotiating trunking on a link between two devices and for
negotiating the type of trunking encapsulation (IEEE 802.1Q) to be used
•VLAN Trunking Protocol (VTP) and VTP pruning for reducing network traffic by restricting
flooded traffic to links destined for stations receiving the traffic
•Voice VLAN for creating subnets for voice traffic from Cisco IP Phones
•VLAN 1 minimization for reducing the risk of spanning-tree loops or storms by allowing VLAN 1
to be disabled on any individual VLAN trunk link. With this feature enabled, no user traffic is sent
or received on the trunk. The switch CPU continues to send and receive control protocol frames.
•VLAN Flex Link Load Balancing to provide Layer 2 redundancy without requiring Spanning Tree
Protocol (STP). A pair of interfaces configured as primary and backup links can load balance traffic
based on VLAN.
•Support for 802.1x authentication with restricted VLANs (also known as authentication failed
VLANs).
•Support for VTP version 3 that includes support for configuring extended range VLANs (VLANs
1006 to 4094) in any VTP mode, enhanced authentication (hidden or secret passwords), propagation
of other databases in addition to VTP, VTP primary and secondary servers, and the option to turn
VTP on or off by port.
Security Features
•IP Service Level Agreements (IP SLAs) support to measure network performance by using active
•Web authentication to allow a supplicant (client) that does not support IEEE 802.1x functionality to
Cisco IE 3010 Switch Software Configuration Guide
1-6
traffic monitoring
be authenticated using a web browser
OL-23145-01
Page 43
Chapter 1 Overview
Features
•Local web authentication banner so that a custom banner or an image file can be displayed at a web
authentication login screen
•MAC authentication bypass (MAB) aging timer to detect inactive hosts that have authenticated after
they have authenticated by using MAB
•Password-protected access (read-only and read-write access) to management interfaces (device
manager, 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
•Source and destination MAC-based ACLs for filtering non-IP traffic
•DHCP snooping to filter untrusted DHCP messages between untrusted hosts and DHCP servers
•IP source guard to restrict traffic on nonrouted interfaces by filtering traffic based on the DHCP
snooping database and IP source bindings
•Dynamic ARP inspection to prevent malicious attacks on the switch by not relaying invalid ARP
requests and responses to other ports in the same VLAN
•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
–
Dynamic voice virtual LAN (VLAN) for MDA to allow a dynamic voice VLAN on an
MDA-enabled port
–
VLAN assignment for restricting 802.1x-authenticated users to a specified VLAN
–
Port security for controlling access to 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
OL-23145-01
–
IP phone detection enhancement to detect and recognize a Cisco IP phone.
–
Guest VLAN to provide limited services to non-802.1x-compliant users
–
Restricted VLAN to provide limited services to users who are 802.1x compliant, but do not have
the credentials to authenticate via the standard 802.1x processes
–
802.1x accounting to track network usage
Cisco IE 3010 Switch Software Configuration Guide
1-7
Page 44
Features
Chapter 1 Overview
–
802.1x with wake-on-LAN to allow dormant PCs to be powered on based on the receipt of a
specific Ethernet frame
–
802.1x readiness check to determine the readiness of connected end hosts before configuring
IEEE 802.1x on the switch
–
Voice aware 802.1x security to apply traffic violation actions only on the VLAN on which a
security violation occurs.
–
MAC authentication bypass to authorize clients based on the client MAC address.
–
Network Edge Access Topology (NEAT) with 802.1X switch supplicant, host authorization
with CISP, and auto enablement to authenticate a switch outside a wiring closet as a supplicant
to another switch.
–
IEEE 802.1x with open access to allow a host to access the network before being authenticated.
–
IEEE 802.1x authentication with downloadable ACLs and redirect URLs to allow per-user ACL
downloads from a Cisco Secure ACS server to an authenticated switch.
–
Flexible-authentication sequencing to configure the order of the authentication methods that a
port tries when authenticating a new host.
–
Multiple-user authentication to allow more than one host to authenticate on an 802.1x-enabled
port.
•Network Admission Control (NAC) features:
–
NAC Layer 2 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 802.1x validation, see the “Configuring NAC
Layer 2 802.1x Validation” section on page 10-59.
–
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.
–
IEEE 802.1x inaccessible authentication bypass.
For information about configuring this feature, see the “Configuring the Inaccessible
Authentication Bypass Feature” section on page 10-54.
–
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 versions of the software)
1-8
•Secure Socket Layer (SSL) Version 3.0 support for the HTTP 1.1 server authentication, encryption,
and message integrity and HTTP client authentication to allow secure HTTP communications
(requires the cryptographic version of the software)
•Voice aware IEEE 802.1x and MAC authentication bypass (MAB) security violation to shut down
only the data VLAN on a port when a security violation occurs
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 45
Chapter 1 Overview
Features
•Support for IP source guard on static hosts.
•RADIUS Change of Authorization (CoA) to change the attributes of a certain session after it is
authenticated. When there is a change in policy for a user or user group in AAA, administrators can
send the RADIUS CoA packets from the AAA server, such as Cisco Secure ACS to reinitialize
authentication, and apply to the new policies.
•IEEE 802.1x User Distribution to allow deployments with multiple VLANs (for a group of users) to
improve scalability of the network by load balancing users across different VLANs. Authorized
users are assigned to the least populated VLAN in the group, assigned by RADIUS server.
•Support for critical VLAN with multiple-host authentication so that when a port is configured for
multi-auth, and an AAA server becomes unreachable, the port is placed in a critical VLAN in order
to still permit access to critical resources.
•Customizable web authentication enhancement to allow the creation of user-defined login, success,
failure and expire web pages for local web authentication.
•Support for Network Edge Access Topology (NEAT) to change the port host mode and to apply a
standard port configuration on the authenticator switch port.
•VLAN-ID based MAC authentication to use the combined VLAN and MAC address information for
user authentication to prevent network access from unauthorized VLANs.
•MAC move to allow hosts (including the hosts connected behind an IP phone) to move across ports
within the same switch without any restrictions to enable mobility. With MAC move, the switch
treats the reappearance of the same MAC address on another port in the same way as a completely
new MAC address.
•Support for 3DES and AES with version 3 of the Simple Network Management Protocol (SNMPv3).
This release adds support for the 168-bit Triple Data Encryption Standard (3DES) and the 128-bit,
192-bit, and 256-bit Advanced Encryption Standard (AES) encryption algorithms to SNMPv3.
QoS and CoS Features
•Automatic QoS (auto-QoS) to simplify the deployment of existing QoS features by classifying
traffic and configuring egress queues
•Automatic quality of service (QoS) Voice over IP (VoIP) enhancement for port -based trust of DSCP
and priority queuing for egress traffic
•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
OL-23145-01
–
Trusted boundary for detecting the presence of a Cisco IP Phone, trusting the CoS value
received, and ensuring port security
•Policing
Cisco IE 3010 Switch Software Configuration Guide
1-9
Page 46
Features
–
Traffic-policing policies on the switch port for managing how much of the port bandwidth
should be allocated to a specific traffic flow
–
If you configure multiple class maps for a hierarchical policy map, each class map can be
associated with its own port-level (second-level) policy map. Each second-level policy map can
have a different policer.
–
Aggregate policing for policing traffic flows in aggregate to restrict specific applications or
traffic flows to metered, predefined rates
•Out-of-Profile
–
Out-of-profile markdown for packets that exceed bandwidth utilization limits
•Ingress queueing and scheduling
–
Two configurable ingress queues for user traffic (one queue can be the priority queue)
–
Weighted tail drop (WTD) as the congestion-avoidance mechanism for managing the queue
lengths and providing drop precedences for different traffic classifications
–
Shaped round robin (SRR) as the scheduling service for specifying the rate at which packets are
sent to the ring (sharing is the only supported mode on ingress queues)
•Egress queues and scheduling
–
Four egress queues per port
Chapter 1 Overview
–
–
Monitoring Features
•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
WTD as the congestion-avoidance mechanism for managing the queue lengths and providing
drop precedences for different traffic classifications
SRR as the scheduling service for specifying the rate at which packets are dequeued to the
egress interface (shaping or sharing is supported on egress queues). Shaped egress queues are
guaranteed but limited to using a share of port bandwidth. Shared egress queues are also
guaranteed a configured share of bandwidth, but can use more than the guarantee if other queues
become empty and do not use their share of the bandwidth.
1-10
•Time Domain Reflector (TDR) to diagnose and resolve cabling problems on 10/100/1000 copper
Ethernet ports
•SFP module diagnostic management interface to monitor physical or operational status of an SFP
module
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 47
Chapter 1 Overview
Default Settings After Initial Switch Configuration
•Digital optical monitoring (DOM) to check status of X2 small form-factor pluggable (SFP) modules
Default Settings After Initial Switch Configuration
The switch is designed for plug-and-play operation, requiring only that you assign basic IP information
to the switch and connect it to the other devices in your network. If you have specific network needs,
you can change the interface-specific and system-wide settings.
NoteFor 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 Features.”
•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 Features.”
•Switch cluster is disabled. For more information about switch clusters, see Chapter 5, “Clustering
Switches,” available on Cisco.com.
•No passwords are defined. For more information, see Chapter 6, “Administering the Switch.”
•System name and prompt is Switch. For more information, see Chapter 6, “Administering the
Switch.”
•NTP is enabled. For more information, see Chapter 6, “Administering the Switch.”
•DNS is enabled. For more information, see Chapter 6, “Administering the Switch.”
•TACACS+ is disabled. For more information, see Chapter 9, “Configuring Switch-Based
Authentication.”
•RADIUS is disabled. For more information, see Chapter 9, “Configuring Switch-Based
Authentication.”
•The standard HTTP server and Secure Socket Layer (SSL) HTTPS server are both enabled. For more
No protected ports are defined. For more information, see Chapter 24, “Configuring Port-Based
Traffic Control.”
–
Unicast and multicast traffic flooding is not blocked. For more information, see Chapter 24,
“Configuring Port-Based Traffic Control.”
–
No secure ports are configured. For more information, see Chapter 24, “Configuring Port-Based
Traffic Control.”
1-12
•CDP is enabled. For more information, see Chapter 25, “Configuring CDP.”
•UDLD is disabled. For more information, see Chapter 27, “Configuring UDLD.”
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 49
Chapter 1 Overview
•SPAN and RSPAN are disabled. For more information, see Chapter 28, “Configuring SPAN and
RSPAN.”
•RMON is disabled. For more information, see Chapter 29, “Configuring RMON.”
•Syslog messages are enabled and appear on the console. For more information, see Chapter 30,
“Configuring System Message Logging.”
•SNMP is enabled (Version 1). For more information, see Chapter 31, “Configuring SNMP.”
•No ACLs are configured. For more information, see Chapter 32, “Configuring Network Security
with ACLs.”
•QoS is disabled. For more information, see Chapter 33, “Configuring QoS.”
•No EtherChannels are configured. For more information, see Chapter 34, “Configuring
EtherChannels and Link-State Tracking.”
Network Configuration Examples
Network Configuration Examples
This section provides network configuration concepts and includes examples of using the switch to
create dedicated network segments and interconnecting the segments through Fast Ethernet and Gigabit
Ethernet connections.
•“Design Concepts for Using the Switch” section on page 1-13
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.
Ta b l e 1-1Increasing Network Performance
Network DemandsSuggested Design Methods
Too many users on a single network
segment and a growing number of
users accessing the Internet
•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)
•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.
•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-23145-01
Cisco IE 3010 Switch Software Configuration Guide
1-13
Page 50
Chapter 1 Overview
Where to Go Next
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.
network demands and how you can meet them.
Ta b l e 1-2Providing Network Services
Network DemandsSuggested 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.
High demand on network redundancy
and availability to provide always on
mission-critical applications
•Use VLAN trunks and BackboneFast for traffic-load balancing on the uplink ports
so that the uplink port with a lower relative port cost is selected to carry the VLAN
traffic.
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.
Table 1-2 describes some
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”
•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.
1-14
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 51
CHA PTER
2
Using the Command-Line Interface
This chapter describes the Cisco IOS command-line interface (CLI) and how to use it to configure your
IE3010 switch.Unless otherwise noted, the term switch refers to a standalone switch and to a switch
stack.
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-23145-01
Cisco IE 3010 Switch Software Configuration Guide
2-1
Page 52
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.
Ta b l e 2-1Command Mode Summary
ModeAccess MethodPromptExit MethodAbout This Mode
User EXECBegin a session with
your switch.
Privileged EXECWhile in user EXEC
mode, enter the
enable command.
Global configurationWhile in privileged
EXEC mode, enter
the configure
command.
Config-vlanWhile in global
configuration mode,
enter the
vlan
vlan-id
command.
VLAN configurationWhile in privileged
EXEC mode, enter
the vlan database
command.
Switch>
Switch#
Switch(config)#
Switch(config-vlan)#
Switch(vlan)#
Enter logout or
quit.
Enter disable to
exit.
To exit to privileged
EXEC mode, enter
exit or end, or press
Ctrl-Z.
To exit to global
configuration mode,
enter the exit
command.
To return to
privileged EXEC
mode, press Ctrl-Z
or enter end.
To exit to privileged
EXEC mode, enter
exit.
Use this mode to
•Change terminal settings.
•Perform basic tests.
•Display system
information.
Use this mode to verify
commands that you have
entered. Use a password to
protect access to this mode.
Use this mode to configure
parameters that apply to the
entire switch.
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.
Use this mode to configure
VLAN parameters for VLANs
1 to 1005 in the VLAN
database.
2-2
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 53
Chapter 2 Using the Command-Line Interface
Understanding the Help System
Table 2-1Command Mode Summary (continued)
ModeAccess MethodPromptExit MethodAbout This Mode
Interface
configuration
While in global
configuration mode,
enter the interface
command (with a
specific interface).
Line configurationWhile in global
configuration mode,
specify a line with
the line
vty or line
console command.
Switch(config-if)#
Switch(config-line)#
To exit to global
configuration mode,
enter exit.
To return to
privileged EXEC
mode, press Ctrl-Z
or enter end.
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
Interface Configuration Mode”
section on page 12-9.
To configure multiple
interfaces with the same
parameters, see the
“Configuring a Range of
Interfaces” section on
page 12-10.
Use this mode to configure
parameters for the terminal
line.
“Using
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
Ta b l e 2-2Help Summary
CommandPurpose
helpObtain 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.
abbreviated-command-entry<Ta b>Complete a partial command name.
Table 2-2.
For example:
Switch# di?
dir disable disconnect
For example:
Switch# sh conf<tab>
Switch# show configuration
OL-23145-01
Cisco IE 3010 Switch Software Configuration Guide
2-3
Page 54
Chapter 2 Using the Command-Line Interface
Understanding Abbreviated Commands
Table 2-2Help Summary (continued)
CommandPurpose
?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
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.
2-4
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 55
Chapter 2 Using the Command-Line Interface
Understanding CLI Error Messages
Table 2-3 lists some error messages that you might encounter while using the CLI to configure your
switch.
Ta b l e 2-3Common CLI Error Messages
Error MessageMeaningHow to Get Help
% Ambiguous command:
"show con"
% Incomplete command.
% Invalid input detected
at ‘^’ marker.
You did not enter enough characters
for your switch to recognize the
command.
You did not enter all the keywords or
values required by this command.
You entered the command
incorrectly. The caret (^) marks the
point of the error.
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.
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.
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.
Understanding CLI Error Messages
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.
NoteOnly CLI or HTTP changes are logged.
OL-23145-01
Cisco IE 3010 Switch Software Configuration Guide
2-5
Page 56
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
Chapter 2 Using the Command-Line Interface
]
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
The range is from 0 to 256.
number-of-lines
]
Recalling Commands
To recall commands from the history buffer, perform one of the actions listed in Ta ble 2-4. These actions
are optional.
Ta b l e 2-4Recalling Commands
1
Action
Press Ctrl-P or the up arrow key.Recall commands in the history buffer, beginning with the most recent command.
Press Ctrl-N or the down arrow key.Return to more recent commands in the history buffer after recalling commands
show historyWhile in privileged EXEC mode, list the last several commands that you just
1. The arrow keys function only on ANSI-compatible terminals such as VT100s.
Result
Repeat the key sequence to recall successively older commands.
with Ctrl-P or the up arrow key. Repeat the key sequence to recall successively
more recent commands.
entered. The number of commands that appear is controlled by the setting of the
terminal history global configuration command and the history line configuration
command.
2-6
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 57
Chapter 2 Using the Command-Line Interface
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)
Using Editing Features
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-23145-01
Cisco IE 3010 Switch Software Configuration Guide
2-7
Page 58
Using Editing Features
Editing Commands through Keystrokes
Table 2-5 shows the keystrokes that you need to edit command lines. These keystrokes are optional.
Ta b l e 2-5Editing Commands through Keystrokes
Chapter 2 Using the Command-Line Interface
CapabilityKeystroke
Move around the command line to
make changes or corrections.
Press Ctrl-B, or press the
left arrow key.
Press Ctrl-F, or press the
right arrow key.
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
Recall commands from the buffer
Press Ctrl-Y.Recall the most recent entry in the buffer.
and paste them in the command line.
The switch provides a buffer with the
last ten items that you deleted.
Press Esc Y.Recall the next buffer entry.
Delete entries if you make a mistake
or change your mind.
Press the Delete or
Backspace key.
Press Ctrl-D.Delete the character at the cursor.
Press Ctrl-K.Delete all characters from the cursor to the end of the
Press Ctrl-U or Ctrl-X.Delete all characters from the cursor to the beginning of
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
Press Esc C.Capitalize at the cursor.
capitalize a set of letters.
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
Press Ctrl-V or Esc Q.
an executable command, perhaps as a
shortcut.
1
Purpose
Move the cursor back one character.
Move the cursor forward one character.
character located at the cursor.
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.
Erase the character to the left of the cursor.
command line.
the command line.
2-8
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 59
Chapter 2 Using the Command-Line Interface
Table 2-5Editing Commands through Keystrokes (continued)
Using Editing Features
CapabilityKeystroke
Scroll down a line or screen on
Press the Return key.Scroll down one line.
1
displays that are longer than the
terminal screen can display.
NoteThe 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 Space bar.Scroll down one screen.
Redisplay the current command line
Press Ctrl-L or Ctrl-R.Redisplay the current command line.
if the switch suddenly sends a
message to your screen.
1. The arrow keys function only on ANSI-compatible terminals such as VT100s.
Editing Command Lines that Wrap
Purpose
You can use a wraparound feature for commands that extend beyond a single line on the screen. When
the cursor reaches the right margin, the command line shifts ten spaces to the left. You cannot see the
first ten characters of the line, but you can scroll back and check the syntax at the beginning of the
command. The keystroke actions are optional.
To scroll back to the beginning of the command entry, press Ctrl-B or the left arrow key repeatedly. You
can also press Ctrl-A to immediately move to the beginning of the line.
The arrow keys function only on ANSI-compatible terminals such as VT100s.
In this example, the access-list global configuration command entry extends beyond one line. When the
cursor first reaches the end of the line, the line is shifted ten spaces to the left and redisplayed. The dollar
sign ($) shows that the line has been scrolled to the left. Each time the cursor reaches the end of the line,
the line is again shifted ten spaces to the left.
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:
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.
OL-23145-01
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.
Cisco IE 3010 Switch Software Configuration Guide
2-9
Page 60
Chapter 2 Using the Command-Line Interface
Searching and Filtering Output of show and more Commands
Searching and Filtering Output of show and more Commands
You can search and filter the output for show and more commands. This is useful when you need to sort
through large amounts of output or if you want to exclude output that you do not need to see. Using these
commands is optional.
To use this functionality, enter a show or more command followed by the pipe character (|), one of the
keywords begin, include, or exclude, and an expression that you want to search for or filter out:
command| {begin | include | exclude} regular-expression
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output appear.
This example shows how to include in the output display only lines where the expression protocol
appears:
Switch# show interfaces | include protocol
Vlan1 is up, line protocol is up
Vlan10 is up, line protocol is down
Accessing the CLI
You can access the CLI through a console connection, through Telnet, or by using the browser.
Accessing the CLI through a Console Connection or through Telnet
Before you can access the CLI, you must connect a terminal or PC to the switch console port and power
on the switch, as described in the getting started guide that shipped with your switch. Then, to understand
the boot process and the options available for assigning IP information, see
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
You can use one of these methods to establish a connection with the switch:
•Connect the switch console port to a management station or dial-up modem. For information about
connecting to the console port, see the switch getting started guide or hardware installation guide.
•Use any Telnet TCP/IP or encrypted Secure Shell (SSH) package from a remote management
station. The switch must have network connectivity with the Telnet or SSH client, and the switch
must have an enable secret password configured.
For information about configuring the switch for Telnet access, see the “Setting a Telnet Password
for a Terminal Line” section on page 9-6. The switch supports up to 16 simultaneous Telnet sessions.
Changes made by one Telnet user are reflected in all other Telnet sessions.
“Setting a Telnet Password for a Terminal Line” section on page 9-6.
Chapter 3, “Assigning the
2-10
For information about configuring the switch for SSH, see the “Configuring the Switch for Secure
Shell” section on page 9-45. The switch supports up to five simultaneous secure SSH sessions.
After you connect through the console port, through a Telnet session or through an SSH session, the
user
EXEC prompt appears on the management station.
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 61
CHA PTER
3
Assigning the Switch IP Address and Default
Gateway
This chapter describes how to create the initial switch configuration (for example, assigning the IP
address and default gateway information) for the IE 3010 switch by using a variety of automatic and
manual methods. It also describes how to modify the switch startup configuration.
NoteFor complete syntax and usage information for the commands used in this chapter, see the command
reference for this release and the Cisco IOS IP Command Reference, Volume 1 of 3: Addressing and
Services from the Cisco.com page under Documentation > Cisco IOS Software > 12.2 Mainline >
Command References.
This chapter consists of these sections:
•Understanding the Boot Process, page 3-1
•Assigning Switch Information, page 3-3
•Checking and Saving the Running Configuration, page 3-15
•Modifying the Startup Configuration, page 3-16
•Scheduling a Reload of the Software Image, page 3-21
NoteInformation in this chapter about configuring IP addresses and DHCP is specific to IP Version 4 (IPv4).
Understanding the Boot Process
To start your switch, you need to follow the procedures in the Getting Started Guide or the hardware
installation guide for installing and powering on the switch and for setting up the initial switch
configuration (IP address, subnet mask, default gateway, secret and Telnet passwords, and so forth).
The normal boot process involves the operation of the boot loader software, which performs these
activities:
•Performs low-level CPU initialization. It initializes the CPU registers, which control where physical
memory is mapped, its quantity, its speed, and so forth.
•Performs power-on self-test (POST) for the CPU subsystem. It tests the CPU DRAM and the portion
of the flash device that makes up the flash file system.
OL-23145-01
Cisco IE 3010 Switch Software Configuration Guide
3-1
Page 62
Understanding the Boot Process
•Initializes the compact 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 launch the operating system. After the boot loader
gives the operating system control of the CPU, the boot loader is not active until the next system reset
or power-on.
The switch has a removable compact flash card that stores the Cisco IOS software image and
configuration files. You can replace and upgrade the switch without reconfiguring the switch. Removing
the compact flash card does not interrupt switch operation, unless you need to reload the Cisco IOS software
due to a power cycle or user action. However, when the compact flash card is removed, you do not have access
to the flash file system, and any attempt to access it generates an error message. The switch ships with the
compact flash memory card installed and supports any size compact flash card.
Use the show flash: privileged EXEC command to display the compact flash file settings. For more
information about the command, go to this URL:
For information about how to remove or replace the compact flash memory card on the switch, see the
Cisco IE 3010 Hardware Installation Guide.
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
page 36-2 and the “Recovering from a Lost or Forgotten Password” section on page 36-3.
Chapter 3 Assigning the Switch IP Address and Default Gateway
“Recovering from a Software Failure” section on
NoteYou can disable password recovery. For more information, see the “Disabling Password Recovery”
section on page 9-5.
Before you can assign switch information, make sure you have connected a PC or terminal to the console
port, and configured the PC or terminal-emulation software baud rate and character format to match
these of the switch console port:
•Baud rate default is 9600.
•Data bits default is 8.
NoteIf the data bits option is set to 8, set the parity option to none.
•Stop bits default is 1.
•Parity settings default is none.
3-2
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 63
Chapter 3 Assigning the Switch IP Address and Default Gateway
Assigning Switch Information
You can assign IP information through the switch setup program, through a DHCP server, or manually.
Use the switch setup program if you want to be prompted for specific IP information. With this program,
you can also configure a hostname and an enable secret password. It gives you the option of assigning a
Telnet password (to provide security during remote management) and configuring your switch as a
command or member switch of a cluster or as a standalone switch. For more information about the setup
program, see the hardware installation guide.
Use a DHCP server for centralized control and automatic assignment of IP information after the server
is configured.
NoteIf 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:
IP address and subnet maskNo IP address or subnet mask are defined.
Default gatewayNo default gateway is defined.
Enable secret passwordNo password is defined.
HostnameThe factory-assigned default hostname is Switch.
Telnet passwordNo password is defined.
Cluster command switch functionalityDisabled.
Cluster nameNo cluster name is defined.
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.
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
3-3
Page 64
Assigning Switch Information
Switch A
DHCPACK (unicast)
DHCPREQUEST (broadcast)
DHCPOFFER (unicast)
DHCPDISCOVER (broadcast)
DHCP server
51807
During DHCP-based autoconfiguration, your switch (DHCP client) is automatically configured at
startup with IP address information and a configuration file.
With DHCP-based autoconfiguration, no DHCP client-side configuration is needed on your switch.
However, you need to configure the DHCP server for various lease options associated with IP addresses.
If you are using DHCP to relay the configuration file location on the network, you might also need to
configure a Trivial File Transfer Protocol (TFTP) server and a Domain Name System (DNS) server.
The DHCP server for your switch can be on the same LAN or on a different LAN than the switch. If the
DHCP server is running on a different LAN, you should configure a DHCP relay device between your
switch and the DHCP server. A relay device forwards broadcast traffic between two directly connected
LANs. A router does not forward broadcast packets, but it forwards packets based on the destination IP
address in the received packet.
DHCP-based autoconfiguration replaces the BOOTP client functionality on your switch.
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.
Chapter 3 Assigning the Switch IP Address and Default Gateway
Figure 3-1DHCP 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-7.
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.
3-4
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.)
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 65
Chapter 3 Assigning the Switch IP Address and Default Gateway
Assigning Switch Information
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 switch. However, the server usually reserves the
address until the client has had a chance to formally request the address. If the switch accepts replies
from a BOOTP server and configures itself, the switch broadcasts, instead of unicasts, TFTP requests to
obtain the switch configuration file.
The DHCP hostname option allows a group of switches to obtain hostnames and a standard configuration
from the central management DHCP server. A client (switch) includes in its DCHPDISCOVER message
an option 12 field used to request a hostname and other configuration parameters from the DHCP server.
The configuration files on all clients are identical except for their DHCP-obtained hostnames.
If a client has a default hostname (the hostname name global configuration command is not configured
or the no hostname global configuration command is entered to remove the hostname), the DHCP
hostname option is not included in the packet when you enter the ip address dhcp interface
configuration command. In this case, if the client receives the DCHP hostname option from the DHCP
interaction while acquiring an IP address for an interface, the client accepts the DHCP hostname option
and sets the flag to show that the system now has a hostname configured.
Understanding DHCP-based Autoconfiguration and Image Update
You can use the DHCP image upgrade features to configure a DHCP server to download both a new
image and a new configuration file to one or more switches in a network. This helps ensure that each
new switch added to a network receives the same image and configuration.
There are two types of DHCP image upgrades: DHCP autoconfiguration and DHCP auto-image update.
DHCP Autoconfiguration
DHCP autoconfiguration downloads a configuration file to one or more switches in your network from
a DHCP server. The downloaded configuration file becomes the running configuration of the switch. It
does not over write the bootup configuration saved in the flash, until you reload the switch.
DHCP Auto-Image Update
You can use DHCP auto-image upgrade with DHCP autoconfiguration to download both a configuration
and a new image to one or more switches in your network. The switch (or switches) downloading the
new configuration and the new image can be blank (or only have a default factory configuration loaded).
If the new configuration is downloaded to a switch that already has a configuration, the downloaded
configuration is appended to the configuration file stored on the switch. (Any existing configuration is
not overwritten by the downloaded one.)
NoteTo enable a DHCP auto-image update on the switch, the TFTP server where the image and configuration
files are located must be configured with the correct option 67 (the configuration filename), option 66
(the DHCP server hostname) option 150 (the TFTP server address), and option 125 (description of the
file) settings.
For procedures to configure the switch as a DHCP server, see the “Configuring DHCP-Based
Autoconfiguration” section on page 3-6 and the “Configuring DHCP” section of the “IP addressing and
Services” section of the Cisco IOS IP Configuration Guide, Release 12.2.
OL-23145-01
Cisco IE 3010 Switch Software Configuration Guide
3-5
Page 66
Assigning Switch Information
After you install the switch in your network, the auto-image update feature starts. The downloaded
configuration file is saved in the running configuration of the switch, and the new image is downloaded
and installed on the switch. When you reboot the switch, the configuration is stored in the saved
configuration on the switch.
Limitations and Restrictions
These are the limitations:
•The DHCP-based autoconfiguration with a saved configuration process stops if there is not at least
one Layer 3 interface in an up state without an assigned IP address in the network.
•Unless you configure a timeout, the DHCP-based autoconfiguration with a saved configuration
feature tries indefinitely to download an IP address.
•The auto-install process stops if a configuration file cannot be downloaded or it the configuration
file is corrupted.
NoteThe configuration file that is downloaded from TFTP is merged with the existing configuration in the
running configuration but is not saved in the NVRAM unless you enter the write memory or
copy
running-configuration startup-configuration privileged EXEC command. Note that if the
downloaded configuration is saved to the startup configuration, the feature is not triggered during
subsequent system restarts.
Chapter 3 Assigning the Switch IP Address and Default Gateway
Configuring DHCP-Based Autoconfiguration
These sections contain this configuration information:
•DHCP Server Configuration Guidelines, page 3-6
•Configuring the TFTP Server, page 3-7
•Configuring the DNS, page 3-8
•Configuring the Relay Device, page 3-8
•Obtaining Configuration Files, page 3-9
•Example Configuration, page 3-9
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)
•Router IP address (default gateway address to be used by the switch) (required)
3-6
•DNS server IP address (optional)
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 67
Chapter 3 Assigning the Switch IP Address and Default Gateway
If you want the switch to receive the configuration file from a TFTP server, you must configure the
DHCP server with these lease options:
•TFTP server name (required)
•Boot filename (the name of the configuration file that the client needs) (recommended)
•Hostname (optional)
Depending on the settings of the DHCP server, the switch can receive IP address information, the
configuration file, or both.
If you do not configure the DHCP server with the lease options described previously, it replies to client
requests with only those parameters that are configured. If the IP address and the subnet mask are not in
the reply, the switch is not configured. If the router IP address or the TFTP server name are not found,
the switch might send broadcast, instead of unicast, TFTP requests. Unavailability of other lease options
does not affect autoconfiguration.
The switch can act as a DHCP server. By default, the Cisco IOS DHCP server and relay agent features
are enabled on your switch but are not configured. These features are not operational. If your DHCP
server is a Cisco device, for additional information about configuring DHCP, see the “Configuring
DHCP” section of the “IP Addressing and Services” section of the Cisco IOS IP Configuration Guide
from the Cisco.com page under Documentation > Cisco IOS Software > 12.2 Mainline > Configuration Guides.
Assigning Switch Information
Configuring the TFTP Server
Based on the DHCP server configuration, the switch attempts to download one or more configuration
files from the TFTP server. If you configured the DHCP server to respond to the switch with all the
options required for IP connectivity to the TFTP server, and if you configured the DHCP server with a
TFTP server name, address, and configuration filename, the switch attempts to download the specified
configuration file from the specified TFTP server.
If you did not specify the configuration filename, the TFTP server, or if the configuration file could not
be downloaded, the switch attempts to download a configuration file by using various combinations of
filenames and TFTP server addresses. The files include the specified configuration filename (if any) and
these files: network-config, cisconet.cfg, hostname.config, or hostname.cfg, where hostname is the
switch’s current hostname. The TFTP server addresses used include the specified TFTP server address
(if any) and the broadcast address (255.255.255.255).
For the switch to successfully download a configuration file, the TFTP server must contain one or more
configuration files in its base directory. The files can include these files:
•The configuration file named in the DHCP reply (the actual switch configuration file).
•The network-confg or the cisconet.cfg file (known as the default configuration files).
•The router-confg or the ciscortr.cfg file (These files contain commands common to all switches.
Normally, if the DHCP and TFTP servers are properly configured, these files are not accessed.)
If you specify the TFTP server name in the DHCP server-lease database, you must also configure the
TFTP server name-to-IP-address mapping in the DNS-server database.
If the TFTP server to be used is on a different LAN from the switch, or if it is to be accessed by the switch
through the broadcast address (which occurs if the DHCP server response does not contain all the
required information described previously), a relay must be configured to forward the TFTP packets to
the TFTP server. For more information, see the
preferred solution is to configure the DHCP server with all the required information.
“Configuring the Relay Device” section on page 3-8. The
OL-23145-01
Cisco IE 3010 Switch Software Configuration Guide
3-7
Page 68
Assigning Switch Information
Switch
(DHCP client)
Cisco router
(Relay)
49068
DHCP serverTFTP serverDNS server
20.0.0.220.0.0.3
20.0.0.1
10.0.0.2
10.0.0.1
20.0.0.4
Configuring the DNS
The DHCP server uses the DNS server to resolve the TFTP server name to an IP address. You must
configure the TFTP server name-to-IP address map on the DNS server. The TFTP server contains the
configuration files for the switch.
You can configure the IP addresses of the DNS servers in the lease database of the DHCP server from
where the DHCP replies will retrieve them. You can enter up to two DNS server IP addresses in the lease
database.
The DNS server can be on the same or on a different LAN as the switch. If it is on a different LAN, the
switch must be able to access it through a router.
Configuring the Relay Device
You must configure a relay device, also referred to as a relay agent, when a switch sends broadcast
packets that require a response from a host on a different LAN. Examples of broadcast packets that the
switch might send are DHCP, DNS, and in some cases, TFTP packets. You must configure this relay
device to forward received broadcast packets on an interface to the destination host.
If the relay device is a Cisco router, enable IP routing (ip routing global configuration command), and
configure helper addresses by using the ip helper-address interface configuration command.
Chapter 3 Assigning the Switch IP Address and Default Gateway
For example, in Figure 3-2, configure the router interfaces as follows:
On interface 10.0.0.2:
router(config-if)# ip helper-address 20.0.0.2
router(config-if)# ip helper-address 20.0.0.3
router(config-if)# ip helper-address 20.0.0.4
On interface 20.0.0.1
router(config-if)# ip helper-address 10.0.0.1
Figure 3-2Relay Device Used in Autoconfiguration
Cisco IE 3010 Switch Software Configuration Guide
3-8
OL-23145-01
Page 69
Chapter 3 Assigning the Switch IP Address and Default Gateway
Obtaining Configuration Files
Depending on the availability of the IP address and the configuration filename in the DHCP reserved
lease, the switch obtains its configuration information in these ways:
•The IP address and the configuration filename is reserved for the switch and provided in the DHCP
reply (one-file read method).
The switch receives its IP address, subnet mask, TFTP server address, and the configuration
filename from the DHCP server. The switch sends a unicast message to the TFTP server to retrieve
the named configuration file from the base directory of the server and upon receipt, it completes its
boot-up process.
•The IP address and the configuration filename is reserved for the switch, but the TFTP server
address is not provided in the DHCP reply (one-file read method).
The switch receives its IP address, subnet mask, and the configuration filename from the DHCP
server. The switch sends a broadcast message to a TFTP server to retrieve the named configuration
file from the base directory of the server, and upon receipt, it completes its boot-up process.
•Only the IP address is reserved for the switch and provided in the DHCP reply. The configuration
filename is not provided (two-file read method).
Assigning Switch Information
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.
NoteThe 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-3shows a sample network for retrieving IP information by using DHCP-based autoconfiguration.
OL-23145-01
Cisco IE 3010 Switch Software Configuration Guide
3-9
Page 70
Assigning Switch Information
Switch 1
00e0.9f1e.2001
Cisco router
111394
Switch 2
00e0.9f1e.2002
Switch 3
00e0.9f1e.2003
DHCP serverDNS serverTFTP server
(tftpserver)
10.0.0.1
10.0.0.10
10.0.0.210.0.0.3
Switch 4
00e0.9f1e.2004
Figure 3-3DHCP-Based Autoconfiguration Network Example
Table 3-2 shows the configuration of the reserved leases on the DHCP server.
Ta b l e 3-2DHCP Server Configuration
Chapter 3 Assigning the Switch IP Address and Default Gateway
The DNS server maps the TFTP server nametftpserver 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
3-10
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 71
Chapter 3 Assigning the Switch IP Address and Default Gateway
ip host switchc 10.0.0.23
ip host switchd 10.0.0.24
DHCP Client Configuration
No configuration file is present on Switch A through Switch D.
Configuration Explanation
In Figure 3-3, Switch A reads its configuration file as follows:
•It obtains its IP address 10.0.0.21 from the DHCP server.
•If no configuration filename is given in the DHCP server reply, Switch A reads the network-confg
file from the base directory of the TFTP server.
•It adds the contents of the network-confg file to its host table.
•It reads its host table by indexing its IP address 10.0.0.21 to its hostname (switcha).
•It reads the configuration file that corresponds to its hostname; for example, it reads switch1-confg
from the TFTP server.
Switches B through D retrieve their configuration files and IP addresses in the same way.
Assigning Switch Information
Configuring the DHCP Auto Configuration and Image Update Features
Using DHCP to download a new image and a new configuration to a switch requires that you configure
at least two switches: One switch acts as a DHCP and TFTP server. The client switch is configured to
download either a new configuration file or a new configuration file and a new image file.
Beginning in privileged EXEC mode, follow these steps to configure DHCP autoconfiguration of the
TFTP and DHCP settings on a new switch to download a new configuration file.
CommandPurpose
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
configure terminalEnter global configuration mode.
ip dhcp poolnameCreate a name for the DHCP Server address pool, and enter DHCP
pool configuration mode.
bootfile filenameSpecify the name of the configuration file that is used as a boot image.
network network-number mask
prefix-length
Specify the subnet network number and mask of the DHCP address
pool.
NoteThe prefix length specifies the number of bits that comprise
the address prefix. The prefix is an alternative way of
specifying the network mask of the client. The prefix length
must be preceded by a forward slash (/).
default-router addressSpecify the IP address of the default router for a DHCP client.
option 150 addressSpecify the IP address of the TFTP server.
exitReturn to global configuration mode.
tftp-server flash:filename.textSpecify the configuration file on the TFTP server.
OL-23145-01
Cisco IE 3010 Switch Software Configuration Guide
3-11
Page 72
Assigning Switch Information
CommandPurpose
Step 9
Step 10
Step 11
Step 12
Step 13
interface interface-idSpecify the address of the client that will receive the configuration
no switchportPut the interface into Layer 3 mode.
ip address address maskSpecify the IP address and mask for the interface.
end Return to privileged EXEC mode.
copy running-config startup-config(Optional) Save your entries in the configuration file.
Chapter 3 Assigning the Switch IP Address and Default Gateway
file.
This example shows how to configure a switch as a DHCP server so that it will download a configuration file:
Switch# configure terminal
Switch(config)# ip dhcp poolpool1
Switch(dhcp-config)# network10.10.10.0 255.255.255.0
Switch(dhcp-config)# bootfileconfig-boot.text
Switch(dhcp-config)# default-router 10.10.10.1
Switch(dhcp-config)# option 150 10.10.10.1
Switch(dhcp-config)# exit
Switch(config)# tftp-server flash:config-boot.text
Switch(config)# interface gigabitethernet0/1
Switch(config-if)# no switchport
Switch(config-if)# ip address 10.10.10.1 255.255.255.0
Switch(config-if)# end
Configuring DHCP Auto-Image Update (Configuration File and Image)
Beginning in privileged EXEC mode, follow these steps to configure DHCP autoconfiguration to
configure TFTP and DHCP settings on a new switch to download a new image and a new configuration
file.
NoteBefore following the steps in this table, you must create a text file (for example, autoinstall_dhcp) that
will be uploaded to the switch. In the text file, put the name of the image that you want to download.
This image must be a tar and not a bin file.
CommandPurpose
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
configure terminalEnter global configuration mode.
ip dhcp pool nameCreate a name for the DHCP server address pool and enter DHCP pool
configuration mode.
bootfile filenameSpecify the name of the file that is used as a boot image.
network network-number mask
prefix-length
Specify the subnet network number and mask of the DHCP address pool.
NoteThe prefix length specifies the number of bits that comprise the
address prefix. The prefix is an alternative way of specifying the
network mask of the client. The prefix length must be preceded
by a forward slash (/).
default-router addressSpecify the IP address of the default router for a DHCP client.
option 150 addressSpecify the IP address of the TFTP server.
option 125 hexSpecify the path to the text file that describes the path to the image file.
3-12
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 73
Chapter 3 Assigning the Switch IP Address and Default Gateway
CommandPurpose
Step 8
Step 9
Step 10
Step 11
Step 12
Step 13
Step 14
Step 15
Step 16
Step 17
Step 18
copy tftp flash filename.txtUpload the text file to the switch.
copy tftp flash imagename.tarUpload the tar file for the new image to the switch.
exitReturn to global configuration mode.
tftp-server flash:config.textSpecify the Cisco IOS configuration file on the TFTP server.
tftp-server flash:imagename.tarSpecify the image name on the TFTP server.
tftp-server flash:filename.txtSpecify the text file that contains the name of the image file to download
interface interface-idSpecify the address of the client that will receive the configuration file.
no switchportPut the interface into Layer 3 mode.
ip address address maskSpecify the IP address and mask for the interface.
end Return to privileged EXEC mode.
copy running-config startup-config(Optional) Save your entries in the configuration file.
This example shows how to configure a switch as a DHCP server so it downloads a configuration file:
Beginning in privileged EXEC mode, follow these steps to configure a switch to download a
configuration file and new image from a DHCP server:
CommandPurpose
Step 1
Step 2
Step 3
configure terminalEnter global configuration mode.
boot host dhcpEnable autoconfiguration with a saved configuration.
boot host retry timeout timeout-value(Optional) Set the amount of time the system tries to
OL-23145-01
download a configuration file.
NoteIf you do not set a timeout the system will
indefinitely try to obtain an IP address from the
DHCP server.
Cisco IE 3010 Switch Software Configuration Guide
3-13
Page 74
Assigning Switch Information
CommandPurpose
Step 4
Step 5
Step 6
banner config-save ^C warning-message ^C(Optional) Create warning messages to be displayed
end Return to privileged EXEC mode.
show boot Verify the configuration.
Chapter 3 Assigning the Switch IP Address and Default Gateway
when you try to save the configuration file to NVRAM.
This example uses a Layer 3 SVI interface on VLAN 99 to enable DHCP-based autoconfiguration with
a saved configuration:
Switch# configure terminal
Switch(conf)# boot host dhcp
Switch(conf)# boot host retry timeout 300
Switch(conf)# banner config-save ^C Caution - Saving Configuration File to NVRAM May Cause
You to Nolonger Automatically Download Configuration Files at Reboot^C
Switch(config)# vlan 99
Switch(config-vlan)# interface vlan 99
Switch(config-if)# no shutdown
Switch(config-if)# end
Switch# show boot
BOOT path-list:
Config file: flash:/config.text
Private Config file: flash:/private-config.text
Enable Break: no
Manual Boot: no
HELPER path-list:
NVRAM/Config file
buffer size: 32768
Timeout for Config
Download: 300 seconds
Config Download
via DHCP: enabled (next boot: enabled)
Switch#
NoteYou should only configure and enable the Layer 3 interface. Do not assign an IP address or DHCP-based
autoconfiguration with a saved configuration.
Manually Assigning IP Information
Beginning in privileged EXEC mode, follow these steps to manually assign IP information to multiple
switched virtual interfaces (SVIs):
CommandPurpose
Step 1
Step 2
Step 3
Step 4
configure terminalEnter global configuration mode.
interface vlan vlan-idEnter interface configuration mode, and enter the VLAN to which the IP
information is assigned. The VLAN range is 1 to 4094.
ip address ip-address subnet-maskEnter the IP address and subnet mask.
exitReturn to global configuration mode.
Cisco IE 3010 Switch Software Configuration Guide
3-14
OL-23145-01
Page 75
Chapter 3 Assigning the Switch IP Address and Default Gateway
CommandPurpose
Step 5
Step 6
Step 7
Step 8
Step 9
ip default-gateway ip-addressEnter the IP address of the next-hop router interface that is directly
endReturn to privileged EXEC mode.
show interfaces vlan vlan-idVerify the configured IP address.
show ip redirectsVerify the configured default gateway.
copy running-config startup-config(Optional) Save your entries in the configuration file.
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.
Checking and Saving the Running Configuration
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.
NoteWhen your switch is configured to route with IP, it does not need
to have a default gateway set.
For information on setting the switch system name, protecting access to privileged EXEC commands,
and setting time and calendar services, see
Chapter 6, “Administering the Switch.”
Checking and Saving the Running Configuration
You can check the configuration settings that you entered or changes that you made by entering this
privileged EXEC command:
Switch# show running-config
Building configuration...
Current configuration: 1363 bytes
!
version 12.2
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname Switch A
!
enable secret 5 $1$ej9.$DMUvAUnZOAmvmgqBEzIxE0
!
.
<output truncated>
.
interface gigabitethernet0/1
no switchport
ip address 172.20.137.50 255.255.255.0
!
interface gigabitethernet0/2
mvr type source
OL-23145-01
<output truncated>
...!
Cisco IE 3010 Switch Software Configuration Guide
3-15
Page 76
Modifying the Startup Configuration
interface VLAN1
ip address 172.20.137.50 255.255.255.0
no ip directed-broadcast
!
ip default-gateway 172.20.137.1 !
!
snmp-server community private RW
snmp-server community public RO
snmp-server community private@es0 RW
snmp-server community public@es0 RO
snmp-server chassis-id 0x12
!
end
To store the configuration or changes you have made to your startup configuration in flash memory, enter
this privileged EXEC command:
Switch# copy running-config startup-config
Destination filename [startup-config]?
Building configuration...
This command saves the configuration settings that you made. If you fail to do this, your configuration
will be lost the next time you reload the system. To display information stored in the NVRAM section
of flash memory, use the show startup-config or more startup-config privileged EXEC command.
Chapter 3 Assigning the Switch IP Address and Default Gateway
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-17
•Automatically Downloading a Configuration File, page 3-17
•Booting Manually, page 3-18
•Booting a Specific Software Image, page 3-19
•Controlling Environment Variables, page 3-19
See also Appendix B, “Working with the Cisco IOS File System, Configuration Files, and Software
Images,” for information about switch configuration files.
3-16
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 77
Chapter 3 Assigning the Switch IP Address and Default Gateway
Modifying the Startup Configuration
Default Boot Configuration
Table 3-3 shows the default boot-up configuration.
Ta b l e 3-3Default Boot Configuration
FeatureDefault Setting
Operating system software imageThe 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 fileConfigured switches use the config.text file stored on the system board in flash
memory.
A new switch has no configuration file.
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
Autoconfiguration” section on page 3-3.
“Understanding DHCP-Based
Specifying the Filename to Read and Write the System Configuration
By default, the Cisco IOS software uses the file config.text to read and write a nonvolatile copy of the
system configuration. However, you can specify a different filename, which will be loaded during the
next boot-up cycle.
Beginning in privileged EXEC mode, follow these steps to specify a different configuration filename:
CommandPurpose
Step 1
Step 2
configure terminalEnter global configuration mode.
boot config-file flash:/file-urlSpecify the configuration file to load during the next boot-up
cycle.
For file-url, specify the path (directory) and the configuration
filename.
Step 3
Step 4
Step 5
OL-23145-01
Filenames and directory names are case sensitive.
endReturn to privileged EXEC mode.
show bootVerify your entries.
The boot config-file global configuration command changes the
setting of the CONFIG_FILE environment variable.
copy running-config startup-config(Optional) Save your entries in the configuration file.
Cisco IE 3010 Switch Software Configuration Guide
3-17
Page 78
Modifying the Startup Configuration
To return to the default setting, use the no boot config-file global configuration command.
Booting Manually
By default, the switch automatically boots up; however, you can configure it to manually boot up.
Beginning in privileged EXEC mode, follow these steps to configure the switch to manually boot up
during the next boot cycle:
CommandPurpose
Step 1
Step 2
Step 3
Step 4
configure terminalEnter global configuration mode.
boot manualEnable the switch to manually boot up during the next boot cycle.
endReturn to privileged EXEC mode.
show bootVerify your entries.
Chapter 3 Assigning the Switch IP Address and Default Gateway
The boot manual global command changes the setting of the
MANUAL_BOOT environment variable.
Step 5
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
bootfilesystem:/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.
copy running-config startup-config(Optional) Save your entries in the configuration file.
To disable manual booting, use the no boot manual global configuration command.
3-18
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 79
Chapter 3 Assigning the Switch IP Address and Default Gateway
Booting a Specific Software Image
By default, the switch attempts to automatically boot up the system using information in the BOOT
environment variable. If this variable is not set, the switch attempts to load and execute the first
executable image it can by performing a recursive, depth-first search throughout the flash file system. In
a depth-first search of a directory, each encountered subdirectory is completely searched before
continuing the search in the original directory. However, you can specify a specific image to boot up.
Beginning in privileged EXEC mode, follow these steps to configure the switch to boot a specific image
during the next boot cycle:
CommandPurpose
Step 1
Step 2
configure terminalEnter global configuration mode.
boot system filesystem:/file-urlConfigure the switch to boot a specific image in flash memory during the
next boot cycle.
•For filesystem:, use flash: for the system board flash device.
•For file-url, specify the path (directory) and the name of the bootable
Modifying the Startup Configuration
image.
Filenames and directory names are case sensitive.
Step 3
Step 4
Step 5
endReturn to privileged EXEC mode.
show bootVerify 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.
copy running-config startup-config(Optional) Save your entries in the configuration file.
To return to the default setting, use the no boot system global configuration command.
Controlling Environment Variables
With a normally operating switch, you enter the boot loader mode only through a switch console
connection configured for 9600 b/s. Unplug the switch power cord, and press the switch Mode button
while reconnecting the power cord. You can release the Mode button a second or two after the LED
above port 1 turns off. Then the boot loader switch: prompt appears.
The switch boot loader software provides support for nonvolatile environment variables, which can be
used to control how the boot loader, or any other software running on the system, behaves. Boot loader
environment variables are similar to environment variables that can be set on UNIX or DOS systems.
OL-23145-01
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.
Cisco IE 3010 Switch Software Configuration Guide
3-19
Page 80
Chapter 3 Assigning the Switch IP Address and Default Gateway
Modifying the Startup Configuration
Environment variables store two kinds of data:
•Data that controls code, which does not read the Cisco IOS configuration file. For example, the name
of a boot loader helper file, which extends or patches the functionality of the boot loader can be
stored as an environment variable.
•Data that controls code, which is responsible for reading the Cisco IOS configuration file. For
example, the name of the Cisco IOS configuration file can be stored as an environment variable.
You can change the settings of the environment variables by accessing the boot loader or by using Cisco
IOS commands. Under normal circumstances, it is not necessary to alter the setting of the environment
variables.
NoteFor complete syntax and usage information for the boot loader commands and environment variables,
see the command reference for this release.
Table 3-4 describes the function of the most common environment variables.
Ta b l e 3-4Environment Variables
VariableBoot Loader CommandCisco IOS Global Configuration Command
BOOTset BOOT filesystem:/file-url ...
boot system filesystem:/file-url ...
A semicolon-separated list of executable files to
try to load and execute when automatically
booting. If the BOOT environment variable is not
set, the system attempts to load and execute the
first executable image it can find by using a
recursive, depth-first search through the flash file
system. If the BOOT variable is set but the
specified images cannot be loaded, the system
attempts to boot the first bootable file that it can
find in the flash file system.
MANUAL_BOOTset MANUAL_BOOT yes
Decides whether the switch automatically or
manually boots up.
Valid values are 1, yes, 0, and no. If it is set to no
or 0, the boot loader attempts to automatically
boot up the system. If it is set to anything else,
you must manually boot up the switch from the
boot loader mode.
CONFIG_FILEset CONFIG_FILEflash:/file-url
Changes the filename that Cisco IOS uses to read
and write a nonvolatile copy of the system
configuration.
Specifies the Cisco IOS image to load during the
next boot cycle. This command changes the
setting of the BOOT environment variable.
boot manual
Enables manually booting up the switch during
the next boot cycle and changes the setting of the
MANUAL_BOOT environment variable.
The next time you reboot the system, the switch is
in boot loader mode. To boot up the system, use
the bootflash:filesystem:/file-url boot loader
command, and specify the name of the bootable
image.
boot config-file flash:/file-url
Specifies the filename that Cisco IOS uses to read
and write a nonvolatile copy of the system
configuration. This command changes the
CONFIG_FILE environment variable.
3-20
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 81
Chapter 3 Assigning the Switch IP Address and Default Gateway
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).
NoteA 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.
Scheduling a Reload of the Software Image
•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.
NoteUse the at keyword only if the switch system clock has been set (through Network Time
Protocol (NTP), the hardware calendar, or manually). The time is relative to the configured
time zone on the switch. To schedule reloads across several switches to occur
simultaneously, the time on each switch must be synchronized with NTP.
The reload command halts the system. If the system is not set to manually boot up, it reboots itself. Use
the reload command after you save the switch configuration information to the startup configuration
(copy running-config startup-config).
If your switch is configured for manual booting, do not reload it from a virtual terminal. This restriction
prevents the switch from entering the boot loader mode and thereby taking it from the remote user’s
control.
If you modify your configuration file, the switch prompts you to save the configuration before reloading.
During the save operation, the system requests whether you want to proceed with the save if the
CONFIG_FILE environment variable points to a startup configuration file that no longer exists. If you
proceed in this situation, the system enters setup mode upon reload.
OL-23145-01
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)
Cisco IE 3010 Switch Software Configuration Guide
3-21
Page 82
Scheduling a Reload of the Software Image
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).
Chapter 3 Assigning the Switch IP Address and Default Gateway
3-22
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 83
CHA PTER
4
Configuring Cisco IOS Configuration Engine
This chapter describes how to configure the feature on the IE 3010 switch.
NoteFor complete configuration information for the Cisco Configuration Engine, go to
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
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.
•What You Should Know About the CNS IDs and Device Hostnames, page 4-3
Configuration Service
The Configuration Service is the core component of the Cisco Configuration Engine. It consists of a
configuration server that works with Cisco IOS CNS agents on the switch. The Configuration Service
delivers device and service configurations to the switch for initial configuration and mass
reconfiguration by logical groups. Switches receive their initial configuration from the Configuration
Service when they start up on the network for the first time.
The Configuration Service uses the CNS Event Service to send and receive configuration change events
and to send success and failure notifications.
The configuration server is a web server that uses configuration templates and the device-specific
configuration information stored in the embedded (standalone mode) or remote (server mode) directory.
Configuration templates are text files containing static configuration information in the form of CLI
commands. In the templates, variables are specified using Lightweight Directory Access Protocol
(LDAP) URLs that reference the device-specific configuration information stored in a directory.
The Cisco IOS agent can perform a syntax check on received configuration files and publish events to
show the success or failure of the syntax check. The configuration agent can either apply configurations
immediately or delay the application until receipt of a synchronization event from the configuration
server.
The Cisco Configuration Engine uses the Event Service for receipt and generation of configuration
events. The event agent is on the switch and facilitates the communication between the switch and the
event gateway on the Configuration Engine.
The Event Service is a highly capable publish-and-subscribe communication method. The Event Service
uses subject-based addressing to send messages to their destinations. Subject-based addressing
conventions define a simple, uniform namespace for messages and their destinations.
NameSpace Mapper
The Configuration Engine includes the NameSpace Mapper (NSM) that provides a lookup service for
managing logical groups of devices based on application, device or group ID, and event.
Cisco IOS devices recognize only event subject-names that match those configured in Cisco IOS
software; for example, cisco.cns.config.load. You can use the namespace mapping service to designate
events by using any desired naming convention. When you have populated your data store with your
subject names, NSM changes your event subject-name strings to those known by Cisco IOS.
For a subscriber, when given a unique device ID and event, the namespace mapping service returns a set
of events to which to subscribe. Similarly, for a publisher, when given a unique group ID, device ID, and
event, the mapping service returns a set of events on which to publish.
Understanding Cisco Configuration Engine Software
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-23145-01
Cisco IE 3010 Switch Software Configuration Guide
4-3
Page 86
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.
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.
CautionWhen using the Configuration Engine user interface, you must first set the DeviceID field to the
hostname value that the switch acquires after–not before–you use the cns config initial global
configuration command at the switch. Otherwise, subsequent cns config partial global configuration
command operations malfunction.
Using Hostname, DeviceID, and ConfigID
In standalone mode, when a hostname value is set for a switch, the configuration server uses the
hostname as the DeviceID when an event is sent on hostname. If the hostname has not been set, the event
is sent on the cn=<value> of the device.
In server mode, the hostname is not used. In this mode, the unique DeviceID attribute is always used for
sending an event on the bus. If this attribute is not set, you cannot update the switch.
These and other associated attributes (tag value pairs) are set when you run Setup on the Configuration
Engine.
4-4
NoteFor more information about running the setup program on the Configuration Engine, see the
Configuration Engine setup and configuration guide:
The CNS event agent feature allows the switch to publish and subscribe to events on the event bus and
works with the Cisco IOS agent. The Cisco IOS agent feature supports the switch by providing these
features:
•Initial Configuration, page 4-5
•Incremental (Partial) Configuration, page 4-6
•Synchronized Configuration, page 4-6
Initial Configuration
When the switch first comes up, it attempts to get an IP address by broadcasting a DHCP request on the
network. Assuming there is no DHCP server on the subnet, the distribution switch acts as a DHCP relay
agent and forwards the request to the DHCP server. Upon receiving the request, the DHCP server assigns
an IP address to the new switch and includes the TFTP server IP address, the path to the bootstrap
configuration file, and the default gateway IP address in a unicast reply to the DHCP relay agent. The
DHCP relay agent forwards the reply to the switch.
Understanding Cisco IOS Agents
The switch automatically configures the assigned IP address on interface VLAN 1 (the default) and
downloads the bootstrap configuration file from the TFTP server. Upon successful download of the
bootstrap configuration file, the switch loads the file in its running configuration.
The Cisco IOS agents initiate communication with the Configuration Engine by using the appropriate
ConfigID and EventID. The Configuration Engine maps the Config ID to a template and downloads the
full configuration file to the switch.
Figure 4-2 shows a sample network configuration for retrieving the initial bootstrap configuration file
by using DHCP-based autoconfiguration.
Figure 4-2Initial Configuration Overview
OL-23145-01
Cisco IE 3010 Switch Software Configuration Guide
4-5
Page 88
Configuring Cisco IOS Agents
Incremental (Partial) Configuration
After the network is running, new services can be added by using the Cisco IOS agent. Incremental
(partial) configurations can be sent to the switch. The actual configuration can be sent as an event
payload by way of the event gateway (push operation) or as a signal event that triggers the switch to
initiate a pull operation.
The switch can check the syntax of the configuration before applying it. If the syntax is correct, the
switch applies the incremental configuration and publishes an event that signals success to the
configuration server. If the switch does not apply the incremental configuration, it publishes an event
showing an error status. When the switch has applied the incremental configuration, it can write it to
NVRAM or wait until signaled to do so.
Synchronized Configuration
When the switch receives a configuration, it can defer application of the configuration upon receipt of a
write-signal event. The write-signal event tells the switch not to save the updated configuration into its
NVRAM. The switch uses the updated configuration as its running configuration. This ensures that the
switch configuration is synchronized with other network activities before saving the configuration in
NVRAM for use at the next reboot.
The Cisco IOS agents embedded in the switch Cisco IOS software allow the switch to be connected and
automatically configured as described in the
page 4-6. If you want to change the configuration or install a custom configuration, see these sections
for instructions:
•Enabling the CNS Event Agent, page 4-7
•Enabling the Cisco IOS CNS Agent, page 4-9
Enabling Automated CNS Configuration
To enable automated CNS configuration of the switch, you must first complete the prerequisites in
Table 4-1. When you complete them, power on the switch. At the setup prompt, do nothing: The switch
begins the initial configuration as described in the “Initial Configuration” section on page 4-5. When the
full configuration file is loaded on your switch, you need to do nothing else.
Ta b l e 4-1Prerequisites for Enabling Automatic Configuration
DeviceRequired Configuration
Access switchFactory default (no configuration file)
Beginning in privileged EXEC mode, follow these steps to enable the CNS event agent on the switch:
Enable the event agent, and enter the gateway parameters.
•For {hostname | ip-address}, enter either the
hostname or the IP
•(Optional) For port number, enter the port number for
the event gateway. The default port number is 11011.
•(Optional) Enter backup to show that this is the
backup gateway. (If omitted, this is the primary
gateway.)
•(Optional) For failover-time seconds, enter how long
the switch waits for the primary gateway route after
the route to the backup gateway is established.
•(Optional) For keepalive seconds, enter how often
the switch sends keepalive messages. For retry-count,
enter the number of unanswered keepalive messages
that the switch sends before the connection is
terminated. The default for each is
address of the event gateway.
0.
Step 3
Step 4
Step 5
Step 6
•(Optional) For reconnect time, enter the maximum
time interval that the switch waits before trying to
reconnect to the event gateway.
•(Optional) For source ip-address, enter the source IP
address of this device.
NoteThough visible in the command-line help string,
the encrypt and the clock-timeout time keywords
are not supported.
endReturn to privileged EXEC mode.
show cns event connectionsVerify information about the event agent.
show running-configVerify your entries.
copy running-config startup-config(Optional) Save your entries in the configuration file.
To disable the CNS event agent, use the no cns event {ip-address | hostname} global configuration
command.
This example shows how to enable the CNS event agent, set the IP address gateway to 10.180.1.27, set
120 seconds as the keepalive interval, and set 10 as the retry count.
Repeat Steps 2 to 3 to configure another CNS connect template.
Enter CNS connect configuration mode, specify the name of the
CNS connect profile, and define the profile parameters. The
switch uses the CNS connect profile to connect to the
Configuration Engine.
•Enter the name of the CNS connect profile.
OL-23145-01
•(Optional) For retries number, enter the number of
connection retries. The range is 1 to 30. The default is
•(Optional) For retry-interval seconds, enter the interval
3.
between successive connection attempts to the Configuration
Engine. The range is 1 to 40 seconds. The default is
10
seconds.
•(Optional) For sleep seconds, enter the amount of time
before which the first connection attempt occurs. The range
is 0 to 250 seconds. The default is
•(Optional) For timeout seconds, enter the amount of time
0.
after which the connection attempts end. The range is 10 to
2000 seconds. The default is
Specify the interface parameters in the CNS connect profile.
•For controllercontroller-type, enter the controller type.
•For dlci, enter the active data-link connection identifiers
(DLCIs).
(Optional) For subinterface subinterface-number, specify
the point-to-point subinterface number that is used to search
for active DLCIs.
•For interface [interface-type], enter the type of interface.
•For lineline-type, enter the line type.
profile to be applied to the switch configuration. You can specify
more than one template.
Repeat Steps 7 to 8 to specify more interface parameters and CNS
connect templates in the CNS connect profile.
whose IP address is network-number.
(Optional) Set the unique EventID or ConfigID used by the
Configuration Engine.
•For interface num, enter the type of interface–for example,
ethernet, group-async, loopback, or virtual-template. This
setting specifies from which interface the IP or MAC address
should be retrieved to define the unique
ID.
•For {dns-reverse | ipaddress | mac-address}, enter
dns-reverse to retrieve the hostname and assign it as the unique ID, enter ipaddress to use the IP address, or enter
mac-address to use the MAC address as the unique ID.
•(Optional) Enter event to set the ID to be the event-id value
used to identify the switch.
•(Optional) Enter image to set the ID to be the image-id value
used to identify the switch.
NoteIf both the event and image keywords are omitted, the
image-id value is used to identify the switch.
•For {hardware-serial | hostname| stringstring | udi}, enter
hardware-serial to set the switch serial number as the
unique ID, enter hostname (the default) to select the switch
hostname as the unique ID, enter an arbitrary text string for
stringstring as the unique ID, or enter udi to set the unique
device identifier (UDI) as the unique ID.
Enable the Cisco IOS agent, and initiate an initial configuration.
•For {hostname | ip-address}, enter the hostname or the
IP
address of the configuration server.
•(Optional) For port-number, enter the port number of the
configuration server. The default port number is 80.
•(Optional) Enable event for configuration success, failure, or
warning messages when the configuration is finished.
•(Optional) Enable no-persist to suppress the automatic
writing to NVRAM of the configuration pulled as a result of
entering the cns config initial global configuration
command. If the no-persist keyword is not entered, using the
cns config initial command causes the resultant
configuration to be automatically written to NVRAM.
•(Optional) For page page, enter the web page of the initial
configuration. The default is /Config/config/asp.
•(Optional) Enter source ip-address to use for source IP
address.
Step 15
Step 16
Step 17
•(Optional) Enable syntax-check to check the syntax when
this parameter is entered.
NoteThough visible in the command-line help string, the
encrypt, statusurl, and inventory keywords are not
supported.
endReturn to privileged EXEC mode.
show cns config connectionsVerify information about the configuration agent.
show running-configVerify your entries.
To disable the CNS Cisco IOS agent, use the no cns config initial {ip-address | hostname} global
configuration command.
This example shows how to configure an initial configuration on a remote switch when the switch
configuration is unknown (the CNS Zero Touch feature).
This example shows how to configure an initial configuration on a remote switch when the switch IP
address is known. The Configuration Engine IP address is 172.28.129.22.
configure terminalEnter global configuration mode.
cns config partial {ip-address | hostname}
[port-number] [source ip-address]
Enable the configuration agent, and initiate a partial
configuration.
•For {ip-address | hostname}, enter the IP address or
the hostname of the configuration server.
•(Optional) For port-number, enter the port number of
the configuration server. The default port number is
80.
•(Optional) Enter source ip-address to use for the
source IP address.
NoteThough visible in the command-line help string,
the encrypt keyword is not supported.
endReturn to privileged EXEC mode.
show cns config stats
Verify information about the configuration agent.
or
show cns config outstanding
show running-configVerify your entries.
copy running-config startup-config(Optional) Save your entries in the configuration file.
4-12
To disable the Cisco IOS agent, use the no cns config partial {ip-address | hostname} global
configuration command. To cancel a partial configuration, use the cns config cancel privileged
command.
This chapter provides the concepts and procedures to create and manage IE 3010 switch clusters. You
can create and manage switch clusters by using the command-line interface (CLI), or SNMP. For
complete procedures, see the online help. For the CLI cluster commands, see the switch command
reference.
This chapter focuses on IE 3010 switch clusters. It also includes guidelines and limitations for clusters
mixed with other cluster-capable Catalyst switches, but it does not provide complete descriptions of the
cluster features for these other switches. For complete cluster information for a specific Catalyst
platform, refer to the software configuration guide for that switch.
This chapter consists of these sections:
•Understanding Switch Clusters, page 5-1
•Planning a Switch Cluster, page 5-4
•Using the CLI to Manage Switch Clusters, page 5-13
•Using SNMP to Manage Switch Clusters, page 5-14
NoteWe do not recommend using the ip http access-class global configuration command to limit access to
specific hosts or networks. Access should be controlled through the cluster command switch or by
applying access control lists (ACLs) on interfaces that are configured with IP address. For more
information on ACLs, see Chapter 32, “Configuring Network Security with ACLs.”.
Understanding Switch Clusters
A switch cluster is a set of up to 16 connected, cluster-capable Catalyst switches that are managed as a
single entity. The switches in the cluster use the switch clustering technology so that you can configure
and troubleshoot a group of different Catalyst desktop switch platforms through a single IP address.
In a switch cluster, 1 switch must be the cluster command switch and up to 15 other switches can be
cluster member switches. The total number of switches in a cluster cannot exceed 16
cluster command switch is the single point of access used to configure, manage, and monitor the cluster
member switches. Cluster members can belong to only one cluster at a time.
The benefits of clustering switches include:
OL-23145-01
switches. The
Cisco IE 3010 Switch Software Configuration Guide
5-1
Page 98
Understanding Switch Clusters
•Management of switches regardless of their interconnection media and their physical locations. The
•Command-switch redundancy if a cluster command switch fails. One or more switches can be
•Management of a variety of switches through a single IP address. This conserves on IP addresses,
Table 5-1 lists the switches eligible for switch clustering, including which ones can be cluster command
switches and which ones can only be cluster member switches, and the required software versions.
Chapter 5 Clustering Switches
switches can be in the same location, or they can be distributed across a Layer
cluster is using a Catalyst
the Layer
2 switches in the cluster) network.
3550, Catalyst 3560, or Catalyst 3750 switch as a Layer 3 router between
Cluster members are connected to the cluster command switch according to the connectivity
guidelines described in the
“Automatic Discovery of Cluster Candidates and Members” section on
page 5-4. This section includes management VLAN considerations for the Catalyst 1900,
Catalyst 2820, Catalyst 2900 XL, Catalyst 2950, and Catalyst 3500 XL switches. For complete
information about these switches in a switch-cluster environment, refer to the software
configuration guide for that specific switch.
designated as standby cluster command switches to avoid loss of contact with cluster members. A
cluster standby group is a group of standby cluster command switches.
especially if you have a limited number of them. All communication with the switch cluster is
through the cluster command switch IP address.
2 or Layer 3 (if your
Ta b l e 5-1Switch Software and Cluster Capability
SwitchCisco IOS ReleaseCluster Capability
IE 3010 switch12.2(53)EZ or laterMember or command switch
Catalyst 3750-X or Catalyst 3560-X 12.2(53)SE2 or laterMember or command switch
Catalyst 3750-E or Catalyst 3560-E12.2(35)SE2 or laterMember or command switch
Catalyst 375012.1(11)AX or laterMember or command switch
Catalyst 356012.1(19)EA1b or laterMember or command switch
Catalyst 355012.1(4)EA1 or laterMember or command switch
Catalyst 297512.2(46)EX or laterMember or command switch
Catalyst 297012.1(11)AX or laterMember or command switch
Catalyst 2960-S12.2(53)SE or laterMember or command switch
Catalyst 296012.2(25)FX or laterMember or command switch
Catalyst 295512.1(12c)EA1 or laterMember or command switch
Catalyst 295012.0(5.2)WC(1) or laterMember or command switch
Catalyst 2950 LRE12.1(11)JY or laterMember or command switch
Catalyst 294012.1(13)AY or laterMember or command switch
Catalyst 3500 XL12.0(5.1)XU or laterMember or command switch
Catalyst 2900 XL (8-MB switches)12.0(5.1)XU or laterMember or command switch
Catalyst 2900 XL (4-MB switches)11.2(8.5)SA6 (recommended)Member switch only
Catalyst 1900 and 28209.00(-A or -EN) or laterMember switch only
5-2
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Page 99
Chapter 5 Clustering Switches
Cluster Command Switch Characteristics
A cluster command switch must meet these requirements:
•It is running Cisco IOS Release 12.2(53)EZ or later.
•It has an IP address.
•It has Cisco Discovery Protocol (CDP) version 2 enabled (the default).
•It is not a command or cluster member switch of another cluster.
•It is connected to the standby cluster command switches through the management VLAN and to the
cluster member switches through a common VLAN.
Standby Cluster Command Switch Characteristics
A standby cluster command switch must meet these requirements:
•It is running Cisco IOS 12.2(53)EZ or later.
•It has an IP address.
Understanding Switch Clusters
•It has CDP version 2 enabled.
•It is connected to the command switch and to other standby command switches through its
management VLAN.
•It is connected to all other cluster member switches (except the cluster command and standby
command switches) through a common VLAN.
•It is redundantly connected to the cluster so that connectivity to cluster member switches is
maintained.
•It is not a command or member switch of another cluster.
Candidate Switch and Cluster Member Switch Characteristics
Candidate switches are cluster-capable switches that have not yet been added to a cluster. Cluster
member switches are switches that have actually been added to a switch cluster. Although not required,
a candidate or cluster member switch can have its own IP address and password (for related
considerations, see the
To join a cluster, a candidate switch must meet these requirements:
•It is running cluster-capable software.
•It has CDP version 2 enabled.
•It is not a command or cluster member switch of another cluster.
•If a cluster standby group exists, it is connected to every standby cluster command switch through
at least one common VLAN. The VLAN to each standby cluster command switch can be different.
•It is connected to the cluster command switch through at least one common VLAN.
“IP Addresses” section on page 5-11 and “Passwords” section on page 5-12).
candidate and cluster member switches must be connected through their management VLAN
to the cluster command switch and standby cluster command switches. For complete
information about these switches in a switch-cluster environment, refer to the software
configuration guide for that specific switch.
This requirement does not apply if you have a Catalyst 2970, Catalyst 3550, Catalyst 3560,
or Catalyst
3750 cluster command switch. Candidate and cluster member switches can
connect through any VLAN in common with the cluster command switch.
Planning a Switch Cluster
Anticipating conflicts and compatibility issues is a high priority when you manage several switches
through a cluster. This section describes these guidelines, requirements, and caveats that you should
understand before you create the cluster:
•Automatic Discovery of Cluster Candidates and Members, page 5-4
Chapter 5 Clustering Switches
•Virtual IP Addresses, page 5-9
•IP Addresses, page 5-11
•Hostnames, page 5-11
•Passwords, page 5-12
•SNMP Community Strings, page 5-12
•TACACS+ and RADIUS, page 5-12
•LRE Profiles, page 5-13
Refer to the release notes for the list of Catalyst switches eligible for switch clustering, including which
ones can be cluster command switches and which ones can only be cluster member switches, and for the
required software versions and browser and Java plug-in configurations.
Automatic Discovery of Cluster Candidates and Members
The cluster command switch uses Cisco Discovery Protocol (CDP) to discover cluster member switches,
candidate switches, neighboring switch clusters, and edge devices across multiple VLANs and in star or
cascaded topologies.
NoteDo not disable CDP on the cluster command switch, on cluster members, or on any cluster-capable
switches that you might want a cluster command switch to discover. For more information about CDP,
see Chapter 25, “Configuring CDP.”
5-4
Following these connectivity guidelines ensures automatic discovery of the switch cluster, cluster
candidates, connected switch clusters, and neighboring edge devices:
•Discovery Through CDP Hops, page 5-5
•Discovery Through Non-CDP-Capable and Noncluster-Capable Devices, page 5-6
•Discovery Through Different VLANs, page 5-6
Cisco IE 3010 Switch Software Configuration Guide
OL-23145-01
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.