Advertisement
Advertisement
Cisco Catalyst Blade Switch 3030 for Dell
Software Configuration Guide
Cisco IOS Release 15.0(2)SE
August 2012
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA http://www.cisco.com
800 553-NETS (6387)
Text Part Number: OL-27326-01
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL
STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this
URL: www.cisco.com/go/trademarks . Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
© 2006-2012 Cisco Systems, Inc. All rights reserved.
OL-27326-01
C O N T E N T S
xxxvii
xxxvii
xxxvii
xxxvii
xxxviii
Obtaining Documentation and Submitting a Service Request
xxxix
1-1
1-1
Ease-of-Deployment and Ease-of-Use Features
1-2
1-2
1-3
1-4
Availability and Redundancy Features
1-5
1-6
1-7
1-10
1-11
1-12
Default Settings After Initial Switch Configuration
1-12
Design Concepts for Using the Switch
1-15
1-17
Using the Command-Line Interface
2-1
2-1
2-3
Understanding Abbreviated Commands
2-3
Understanding no and default Forms of Commands
2-4
Understanding CLI Error Messages
2-4
2-4
2-5
Changing the Command History Buffer Size
2-5
2-5
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide iii
Contents
Disabling the Command History Feature
2-6
2-6
Enabling and Disabling Editing Features
2-6
Editing Commands through Keystrokes
2-7
Editing Command Lines that Wrap
2-8
Searching and Filtering Output of show and more Commands
2-9
2-9
3 Assigning the Switch IP Address and Default Gateway
3-1
Understanding the Bootup Process
3-1
3-2
3-3
Understanding DHCP-Based Autoconfiguration
3-3
3-4
Understanding DHCP-based Autoconfiguration and Image Update
3-5
3-5
3-5
3-5
Configuring DHCP-Based Autoconfiguration
3-6
DHCP Server Configuration Guidelines
3-6
3-7
3-7
3-8
3-9
3-10
Configuring the DHCP Auto Configuration and Image Update Features
3-11
Configuring DHCP Autoconfiguration (Only Configuration File)
3-11
Configuring DHCP Auto-Image Update (Configuration File and Image)
3-12
3-13
Manually Assigning IP Information
3-14
Checking and Saving the Running Configuration
3-15
Configuring the NVRAM Buffer Size
3-16
Modifying the Startup Configuration
3-17
3-18
Automatically Downloading a Configuration File
3-18
Specifying the Filename to Read and Write the System Configuration
3-18
3-19
Booting Up a Specific Software Image
3-19
Controlling Environment Variables
3-20
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide iv OL-27326-01
OL-27326-01
Scheduling a Reload of the Software Image
3-22
Configuring a Scheduled Reload
3-23
Displaying Scheduled Reload Information
3-24
Configuring Cisco IOS Configuration Engine
4-1
Understanding Cisco Configuration Engine Software
4-1
4-2
4-3
4-3
What You Should Know About the CNS IDs and Device Hostnames
4-3
4-3
4-4
4-4
Using Hostname, DeviceID, and ConfigID
4-4
Understanding Cisco IOS Agents
4-5
4-5
Incremental (Partial) Configuration
4-6
4-6
4-6
Enabling Automated CNS Configuration
4-6
4-8
Enabling the Cisco IOS CNS Agent
4-9
Enabling an Initial Configuration
4-9
Enabling a Partial Configuration
4-13
4-14
5-1
Managing the System Time and Date
5-1
Understanding the System Clock
5-1
Understanding Network Time Protocol
5-2
5-3
Configuring Time and Date Manually
5-4
5-4
Displaying the Time and Date Configuration
5-5
5-5
Configuring Summer Time (Daylight Saving Time)
5-6
Configuring a System Name and Prompt
5-7
Default System Name and Prompt Configuration
5-8
5-8
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
Contents v
Contents
5-8
5-9
5-9
Displaying the DNS Configuration
5-10
5-10
5-10
Configuring a Message-of-the-Day Login Banner
5-11
5-12
Managing the MAC Address Table
5-12
5-13
5-13
Default MAC Address Table Configuration
5-14
Changing the Address Aging Time
5-14
Removing Dynamic Address Entries
5-15
Configuring MAC Address Change Notification Traps
5-15
Configuring MAC Address Move Notification Traps
5-17
Configuring MAC Threshold Notification Traps
5-18
Adding and Removing Static Address Entries
5-19
Configuring Unicast MAC Address Filtering
5-20
Disabling MAC Address Learning on a VLAN
5-21
Displaying Address Table Entries
5-23
5-23
6-1
Understanding the SDM Templates
6-1
Dual IPv4 and IPv6 SDM Templates
6-2
Configuring the Switch SDM Template
6-3
6-3
SDM Template Configuration Guidelines
6-4
6-4
6-5
7 Configuring Switch-Based Authentication
7-1
Preventing Unauthorized Access to Your Switch
7-1
Protecting Access to Privileged EXEC Commands
7-2
Default Password and Privilege Level Configuration
7-2
Setting or Changing a Static Enable Password
7-3
Protecting Enable and Enable Secret Passwords with Encryption
7-3
7-5
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide vi OL-27326-01
OL-27326-01
Contents
Setting a Telnet Password for a Terminal Line
7-6
Configuring Username and Password Pairs
7-6
Configuring Multiple Privilege Levels
7-7
Setting the Privilege Level for a Command
7-8
Changing the Default Privilege Level for Lines
7-9
Logging into and Exiting a Privilege Level
7-9
Controlling Switch Access with TACACS+
7-10
7-10
7-12
7-12
7-13
Identifying the TACACS+ Server Host and Setting the Authentication Key
7-13
Configuring TACACS+ Login Authentication
7-14
Configuring TACACS+ Authorization for Privileged EXEC Access and Network Services
7-16
7-17
Establishing a Session with a Router if the AAA Server is Unreachable
7-17
Displaying the TACACS+ Configuration
7-17
Controlling Switch Access with RADIUS
7-17
7-18
7-19
RADIUS Change of Authorization
7-20
7-20
Change-of-Authorization Requests
7-20
7-22
7-23
7-25
7-26
Identifying the RADIUS Server Host
7-26
Configuring RADIUS Login Authentication
7-28
7-30
Configuring RADIUS Authorization for User Privileged Access and Network Services
7-32
7-33
Establishing a Session with a Router if the AAA Server is Unreachable
7-33
Configuring Settings for All RADIUS Servers
7-34
Configuring the Switch to Use Vendor-Specific RADIUS Attributes
7-34
Configuring the Switch for Vendor-Proprietary RADIUS Server Communication
7-36
7-37
Monitoring and Troubleshooting CoA Functionality
7-38
Configuring RADIUS Server Load Balancing
7-38
Displaying the RADIUS Configuration
7-38
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide vii
Contents
Controlling Switch Access with Kerberos
7-38
7-39
7-41
Authenticating to a Boundary Switch
7-41
7-41
Authenticating to Network Services
7-42
7-42
Configuring the Switch for Local Authentication and Authorization
7-42
Configuring the Switch for Secure Shell
7-43
7-44
SSH Servers, Integrated Clients, and Supported Versions
7-44
7-45
7-45
7-45
Setting Up the Switch to Run SSH
7-46
7-47
Displaying the SSH Configuration and Status
7-48
Configuring the Switch for Secure Socket Layer HTTP
7-48
Understanding Secure HTTP Servers and Clients
7-48
Certificate Authority Trustpoints
7-49
7-50
Configuring Secure HTTP Servers and Clients
7-51
7-51
7-51
7-51
Configuring the Secure HTTP Server
7-52
Configuring the Secure HTTP Client
7-54
Displaying Secure HTTP Server and Client Status
7-54
Configuring the Switch for Secure Copy Protocol
7-55
7-55
Configuring IEEE 802.1x Port-Based Authentication
8-1
Understanding IEEE 802.1x Port-Based Authentication
8-1
8-3
8-4
Authentication Initiation and Message Exchange
8-6
8-8
Port-Based Authentication Methods
8-9
8-9
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide viii OL-27326-01
OL-27326-01
Contents
Authentication Manager CLI Commands
8-10
Ports in Authorized and Unauthorized States
8-11
8-12
802.1x Multiple Authentication Mode
8-13
8-14
8-14
8-15
802.1x Accounting Attribute-Value Pairs
8-15
8-16
802.1x Authentication with VLAN Assignment
8-16
802.1x Authentication with Per-User ACLs
8-18
802.1x Authentication with Downloadable ACLs and Redirect URLs
8-19
Cisco Secure ACS and Attribute-Value Pairs for the Redirect URL
8-20
Cisco Secure ACS and Attribute-Value Pairs for Downloadable ACLs
8-21
VLAN ID-based MAC Authentication
8-21
802.1x Authentication with Guest VLAN
8-21
802.1x Authentication with Restricted VLAN
8-23
802.1x Authentication with Inaccessible Authentication Bypass
8-24
Support on Multiple-Authentication Ports
8-24
8-24
8-24
8-25
802.1x User Distribution Configuration Guidelines
8-26
802.1x Authentication with Voice VLAN Ports
8-26
802.1x Authentication with Port Security
8-26
802.1x Authentication with Wake-on-LAN
8-27
802.1x Authentication with MAC Authentication Bypass
8-27
Network Admission Control Layer 2 802.1x Validation
8-28
Flexible Authentication Ordering
8-29
8-29
Using Multidomain Authentication
8-30
8-31
802.1x Supplicant and Authenticator Switches with Network Edge Access Topology (NEAT)
8-31
8-32
8-32
Configuring 802.1x Authentication
8-33
Default 802.1x Authentication Configuration
8-34
802.1x Authentication Configuration Guidelines
8-35
8-35
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide ix
Contents
VLAN Assignment, Guest VLAN, Restricted VLAN, and Inaccessible Authentication
8-36
8-37
Maximum Number of Allowed Devices Per Port
8-37
Configuring 802.1x Readiness Check
8-38
Configuring Voice Aware 802.1x Security
8-39
Configuring 802.1x Violation Modes
8-40
Configuring 802.1x Authentication
8-41
Configuring the Switch-to-RADIUS-Server Communication
8-42
8-43
8-44
8-45
Configuring Periodic Re-Authentication
8-45
Manually Re-Authenticating a Client Connected to a Port
8-46
8-47
Changing the Switch-to-Client Retransmission Time
8-47
Setting the Switch-to-Client Frame-Retransmission Number
8-48
Setting the Re-Authentication Number
8-49
8-49
8-50
8-51
Configuring the Inaccessible Authentication Bypass Feature
8-53
Configuring 802.1x User Distribution
8-56
Configuring 802.1x Authentication with WoL
8-57
Configuring MAC Authentication Bypass
8-57
Configuring NAC Layer 2 802.1x Validation
8-58
Configuring IEEE 802.1x Authentication Using a RADIUS Server
8-59
Configuring an Authenticator and a Supplicant Switch with NEAT
8-60
8-61
Configuring 802.1x Authentication with Downloadable ACLs and Redirect URLs
8-61
8-62
Configuring a Downloadable Policy
8-62
Configuring VLAN ID-based MAC Authentication
8-64
Configuring Flexible Authentication Ordering
8-64
8-65
Disabling 802.1x Authentication on the Port
8-65
Resetting the 802.1x Authentication Configuration to the Default Values
8-66
Displaying 802.1x Statistics and Status
8-66 x
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
OL-27326-01
Configuring Web-Based Authentication
9-1
Understanding Web-Based Authentication
9-1
9-2
9-2
9-3
9-3
Local Web Authentication Banner
9-4
Web Authentication Customizable Web Pages
9-6
9-6
Web-based Authentication Interactions with Other Features
9-7
9-7
9-8
9-8
9-8
9-8
9-8
9-8
Configuring Web-Based Authentication
9-9
Default Web-Based Authentication Configuration
9-9
Web-Based Authentication Configuration Guidelines and Restrictions
9-9
Web-Based Authentication Configuration Task List
9-10
Configuring the Authentication Rule and Interfaces
9-10
Configuring AAA Authentication
9-11
Configuring Switch-to-RADIUS-Server Communication
9-12
9-13
Customizing the Authentication Proxy Web Pages
9-14
Specifying a Redirection URL for Successful Login
9-15
Configuring the Web-Based Authentication Parameters
9-16
Configuring a Web Authentication Local Banner
9-16
Removing Web-Based Authentication Cache Entries
9-17
Displaying Web-Based Authentication Status
9-17
Configuring Interface Characteristics
10-1
10-1
10-2
10-2
10-3
10-3
10-4
10-4
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
Contents xi
Contents
10-4
10-5
10-6
10-6
Using Interface Configuration Mode
10-7
Procedures for Configuring Interfaces
10-8
Configuring a Range of Interfaces
10-8
Configuring and Using Interface Range Macros
10-10
Configuring Ethernet Interfaces
10-11
Default Ethernet Interface Configuration
10-12
Configuring Interface Speed and Duplex Mode
10-13
Speed and Duplex Configuration Guidelines
10-13
Setting the Interface Speed and Duplex Parameters
10-14
Configuring IEEE 802.3x Flow Control
10-15
Configuring Auto-MDIX on an Interface
10-16
Adding a Description for an Interface
10-17
Configuring Layer 3 Interfaces
10-17
Configuring SVI Autostate Exclude
10-19
10-20
Monitoring and Maintaining the Interfaces
10-21
10-22
Clearing and Resetting Interfaces and Counters
10-22
Shutting Down and Restarting the Interface
10-23
11-1
Understanding Smartports Macros
11-1
11-2
Default Smartports Macro Configuration
11-2
Smartports Macro Configuration Guidelines
11-2
11-4
11-5
Applying Cisco-Default Smartports Macros
11-6
11-8
12-1
12-1
12-2
12-3
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide xii OL-27326-01
OL-27326-01
Configuring Normal-Range VLANs
12-4
12-6
Normal-Range VLAN Configuration Guidelines
12-6
12-7
Default Ethernet VLAN Configuration
12-7
Creating or Modifying an Ethernet VLAN
12-8
12-9
Assigning Static-Access Ports to a VLAN
12-10
Configuring Extended-Range VLANs
12-11
12-11
Extended-Range VLAN Configuration Guidelines
12-11
Creating an Extended-Range VLAN
12-12
Creating an Extended-Range VLAN with an Internal VLAN ID
12-13
12-14
12-15
12-15
12-17
IEEE 802.1Q Configuration Considerations
12-17
Default Layer 2 Ethernet Interface VLAN Configuration
12-18
Configuring an Ethernet Interface as a Trunk Port
12-18
Interaction with Other Features
12-18
12-19
Defining the Allowed VLANs on a Trunk
12-20
Changing the Pruning-Eligible List
12-21
Configuring the Native VLAN for Untagged Traffic
12-22
Configuring Trunk Ports for Load Sharing
12-22
Load Sharing Using STP Port Priorities
12-23
Load Sharing Using STP Path Cost
12-24
12-26
12-26
Dynamic-Access Port VLAN Membership
12-27
Default VMPS Client Configuration
12-27
12-27
12-28
Entering the IP Address of the VMPS
12-28
Configuring Dynamic-Access Ports on VMPS Clients
12-29
12-29
Changing the Reconfirmation Interval
12-30
12-30
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
Contents xiii
Contents
12-30
Troubleshooting Dynamic-Access Port VLAN Membership
12-31
12-31
13-1
13-1
13-2
13-3
13-3
13-4
13-5
13-5
13-7
13-7
13-8
13-8
13-8
13-9
13-10
13-10
Configuring a VTP Version 3 Password
13-12
Configuring a VTP Version 3 Primary Server
13-13
13-13
13-14
Configuring VTP on a Per-Port Basis
13-15
Adding a VTP Client Switch to a VTP Domain
13-15
13-16
14-1
14-1
14-2
14-2
14-3
Default Voice VLAN Configuration
14-3
Voice VLAN Configuration Guidelines
14-3
Configuring a Port Connected to a Cisco 7960 IP Phone
14-4
Configuring Cisco IP Phone Voice Traffic
14-5
Configuring the Priority of Incoming Data Frames
14-6
14-7
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide xiv OL-27326-01
OL-27326-01
15-1
15-1
IP Addressing Scheme with Private VLANs
15-3
Private VLANs across Multiple Switches
15-4
Private-VLAN Interaction with Other Features
15-4
Private VLANs and Unicast, Broadcast, and Multicast Traffic
15-5
15-5
15-5
Tasks for Configuring Private VLANs
15-6
Default Private-VLAN Configuration
15-6
Private-VLAN Configuration Guidelines
15-6
Secondary and Primary VLAN Configuration
15-7
Private-VLAN Port Configuration
15-8
Limitations with Other Features
15-8
Configuring and Associating VLANs in a Private VLAN
15-9
Configuring a Layer 2 Interface as a Private-VLAN Host Port
15-11
Configuring a Layer 2 Interface as a Private-VLAN Promiscuous Port
15-12
Mapping Secondary VLANs to a Primary VLAN Layer 3 VLAN Interface
15-13
15-14
Configuring IEEE 802.1Q and Layer 2 Protocol Tunneling
16-1
Understanding IEEE 802.1Q Tunneling
16-1
Configuring IEEE 802.1Q Tunneling
16-4
Default IEEE 802.1Q Tunneling Configuration
16-4
IEEE 802.1Q Tunneling Configuration Guidelines
16-4
16-4
16-5
IEEE 802.1Q Tunneling and Other Features
16-6
Configuring an IEEE 802.1Q Tunneling Port
16-6
Understanding Layer 2 Protocol Tunneling
16-7
Configuring Layer 2 Protocol Tunneling
16-10
Default Layer 2 Protocol Tunneling Configuration
16-11
Layer 2 Protocol Tunneling Configuration Guidelines
16-11
Configuring Layer 2 Protocol Tunneling
16-13
Configuring Layer 2 Tunneling for EtherChannels
16-14
Configuring the SP Edge Switch
16-14
Configuring the Customer Switch
16-16
Monitoring and Maintaining Tunneling Status
16-18
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
Contents xv
Contents
17-1
Understanding Spanning-Tree Features
17-1
17-2
Spanning-Tree Topology and BPDUs
17-3
Bridge ID, Switch Priority, and Extended System ID
17-4
Spanning-Tree Interface States
17-4
17-5
17-6
17-6
17-6
17-7
How a Switch or Port Becomes the Root Switch or Root Port
17-7
Spanning Tree and Redundant Connectivity
17-8
Spanning-Tree Address Management
17-8
Accelerated Aging to Retain Connectivity
17-8
Spanning-Tree Modes and Protocols
17-9
Supported Spanning-Tree Instances
17-9
Spanning-Tree Interoperability and Backward Compatibility
17-10
17-10
Configuring Spanning-Tree Features
17-10
Default Spanning-Tree Configuration
17-11
Spanning-Tree Configuration Guidelines
17-12
Changing the Spanning-Tree Mode.
17-13
17-14
17-14
Configuring a Secondary Root Switch
17-16
17-16
17-18
Configuring the Switch Priority of a VLAN
17-19
Configuring Spanning-Tree Timers
17-20
17-20
Configuring the Forwarding-Delay Time for a VLAN
17-21
Configuring the Maximum-Aging Time for a VLAN
17-21
Configuring the Transmit Hold-Count
17-22
Displaying the Spanning-Tree Status
17-22
18-1
18-2
Multiple Spanning-Tree Regions
18-2
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide xvi OL-27326-01
OL-27326-01
18-3
Operations Within an MST Region
18-3
Operations Between MST Regions
18-4
18-5
18-5
18-6
18-6
18-7
Interoperation Between Legacy and Standard Switches
18-7
Detecting Unidirectional Link Failure
18-8
Interoperability with IEEE 802.1D STP
18-8
18-8
Port Roles and the Active Topology
18-9
18-10
18-11
Bridge Protocol Data Unit Format and Processing
18-12
Processing Superior BPDU Information
18-13
Processing Inferior BPDU Information
18-13
18-13
18-14
18-14
18-15
Specifying the MST Region Configuration and Enabling MSTP
18-16
18-17
Configuring a Secondary Root Switch
18-19
18-19
18-20
Configuring the Switch Priority
18-21
18-22
Configuring the Forwarding-Delay Time
18-23
Configuring the Maximum-Aging Time
18-23
Configuring the Maximum-Hop Count
18-24
Specifying the Link Type to Ensure Rapid Transitions
18-24
18-25
Restarting the Protocol Migration Process
18-25
Displaying the MST Configuration and Status
18-26
Configuring Optional Spanning-Tree Features
19-1
Understanding Optional Spanning-Tree Features
19-1
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
Contents xvii
Contents
19-2
19-2
19-3
19-3
19-5
Understanding EtherChannel Guard
19-7
19-8
19-9
Configuring Optional Spanning-Tree Features
19-9
Default Optional Spanning-Tree Configuration
19-9
Optional Spanning-Tree Configuration Guidelines
19-10
19-10
19-11
19-12
Enabling UplinkFast for Use with Redundant Links
19-13
19-13
19-14
19-15
19-15
Displaying the Spanning-Tree Status
19-16
Configuring Flex Links and the MAC Address-Table Move Update Feature
20-1
Understanding Flex Links and the MAC Address-Table Move Update
20-1
20-1
VLAN Flex Link Load Balancing and Support
20-2
Flex Link Multicast Fast Convergence
20-3
Learning the Other Flex Link Port as the mrouter Port
20-3
20-3
20-4
20-6
Configuring Flex Links and MAC Address-Table Move Update
20-7
20-8
20-8
20-9
Configuring VLAN Load Balancing on Flex Links
20-10
Configuring the MAC Address-Table Move Update Feature
20-12
Monitoring Flex Links and the MAC Address-Table Move Update Information
20-14 xviii
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
21 Configuring DHCP Features and IP Source Guard
21-1
21-1
21-2
21-2
21-2
21-3
Cisco IOS DHCP Server Database
21-6
DHCP Snooping Binding Database
21-6
21-7
21-8
DHCP Snooping Configuration Guidelines
21-8
21-9
Configuring the DHCP Relay Agent
21-10
Specifying the Packet Forwarding Address
21-10
Enabling DHCP Snooping and Option 82
21-11
Enabling DHCP Snooping on Private VLANs
21-13
Enabling the Cisco IOS DHCP Server Database
21-13
Enabling the DHCP Snooping Binding Database Agent
21-14
Displaying DHCP Snooping Information
21-15
21-15
21-16
Source IP and MAC Address Filtering
21-16
IP Source Guard for Static Hosts
21-16
21-17
Default IP Source Guard Configuration
21-17
IP Source Guard Configuration Guidelines
21-17
21-18
Configuring IP Source Guard for Static Hosts
21-19
Configuring IP Source Guard for Static Hosts on a Layer 2 Access Port
21-19
Configuring IP Source Guard for Static Hosts on a Private VLAN Host Port
21-23
Displaying IP Source Guard Information
21-25
Understanding DHCP Server Port-Based Address Allocation
21-25
Configuring DHCP Server Port-Based Address Allocation
21-25
Default Port-Based Address Allocation Configuration
21-25
Port-Based Address Allocation Configuration Guidelines
21-26
Enabling DHCP Server Port-Based Address Allocation
21-26
Displaying DHCP Server Port-Based Address Allocation
21-28
Contents
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide xix
Contents
22 Configuring Dynamic ARP Inspection
22-1
Understanding Dynamic ARP Inspection
22-1
Interface Trust States and Network Security
22-3
22-4
Relative Priority of ARP ACLs and DHCP Snooping Entries
22-4
22-4
Configuring Dynamic ARP Inspection
22-5
Default Dynamic ARP Inspection Configuration
22-5
Dynamic ARP Inspection Configuration Guidelines
22-6
Configuring Dynamic ARP Inspection in DHCP Environments
22-7
Configuring ARP ACLs for Non-DHCP Environments
22-8
Limiting the Rate of Incoming ARP Packets
22-10
22-12
22-13
Displaying Dynamic ARP Inspection Information
22-14
23 Configuring IGMP Snooping and MVR
23-1
23-1
23-2
23-3
23-5
23-5
23-5
23-6
23-6
Default IGMP Snooping Configuration
23-6
Enabling or Disabling IGMP Snooping
23-7
23-8
Configuring a Multicast Router Port
23-9
Configuring a Blade Server Statically to Join a Group
23-9
23-10
Configuring the IGMP Leave Timer
23-11
Configuring TCN-Related Commands
23-11
Controlling the Multicast Flooding Time After a TCN Event
23-12
23-12
Disabling Multicast Flooding During a TCN Event
23-13
Configuring the IGMP Snooping Querier
23-13
Disabling IGMP Report Suppression
23-15
Displaying IGMP Snooping Information
23-16
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide xx OL-27326-01
OL-27326-01
Understanding Multicast VLAN Registration
23-17
Using MVR in a Multicast Television Application
23-17
23-19
23-19
MVR Configuration Guidelines and Limitations
23-20
Configuring MVR Global Parameters
23-20
23-21
23-23
Configuring IGMP Filtering and Throttling
23-23
Default IGMP Filtering and Throttling Configuration
23-24
23-24
23-26
Setting the Maximum Number of IGMP Groups
23-26
Configuring the IGMP Throttling Action
23-27
Displaying IGMP Filtering and Throttling Configuration
23-28
Configuring Port-Based Traffic Control
24-1
24-1
24-1
Default Storm Control Configuration
24-3
Configuring Storm Control and Threshold Levels
24-3
Configuring Small-Frame Arrival Rate
24-5
24-6
Default Protected Port Configuration
24-6
Protected Port Configuration Guidelines
24-7
24-7
24-7
Default Port Blocking Configuration
24-8
Blocking Flooded Traffic on an Interface
24-8
24-8
24-9
24-9
24-10
Default Port Security Configuration
24-11
Port Security Configuration Guidelines
24-11
Enabling and Configuring Port Security
24-13
Enabling and Configuring Port Security Aging
24-17
Port Security and Private VLANs
24-18
Configuring Protocol Storm Protection
24-19
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
Contents xxi
Contents
Understanding Protocol Storm Protection
24-19
Default Protocol Storm Protection Configuration
24-20
Enabling Protocol Storm Protection
24-20
Displaying Port-Based Traffic Control Settings
24-21
25-1
25-1
25-2
25-2
Configuring the CDP Characteristics
25-2
25-3
Disabling and Enabling CDP on an Interface
25-4
Monitoring and Maintaining CDP
25-5
Configuring LLDP, LLDP-MED, and Wired Location Service
26-1
Understanding LLDP, LLDP-MED, and Wired Location Service
26-1
26-1
26-2
26-3
Configuring LLDP, LLDP-MED, and Wired Location Service
26-4
26-4
26-5
26-5
Configuring LLDP Characteristics
26-6
26-6
Configuring Network-Policy TLV
26-7
Configuring Location TLV and Wired Location Service
26-9
Monitoring and Maintaining LLDP, LLDP-MED, and Wired Location Service
26-10
27-1
27-1
27-1
Methods to Detect Unidirectional Links
27-2
27-4
27-4
27-4
27-5
27-5
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide xxii OL-27326-01
OL-27326-01
Resetting an Interface Disabled by UDLD
27-6
27-6
28-1
28-1
28-2
28-2
SPAN and RSPAN Concepts and Terminology
28-3
28-3
28-4
28-5
28-6
28-6
28-7
28-8
SPAN and RSPAN Interaction with Other Features
28-8
28-9
Default SPAN and RSPAN Configuration
28-9
28-10
28-10
28-11
Creating a Local SPAN Session and Configuring Incoming Traffic
28-13
28-14
28-15
RSPAN Configuration Guidelines
28-15
Configuring a VLAN as an RSPAN VLAN
28-16
Creating an RSPAN Source Session
28-17
Creating an RSPAN Destination Session
28-19
Creating an RSPAN Destination Session and Configuring Incoming Traffic
28-20
28-22
Displaying SPAN and RSPAN Status
28-23
29-1
29-1
29-3
29-3
Configuring RMON Alarms and Events
29-3
Collecting Group History Statistics on an Interface
29-5
Collecting Group Ethernet Statistics on an Interface
29-6
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
Contents xxiii
Contents
29-6
Configuring System Message Logging
30-1
Understanding System Message Logging
30-1
Configuring System Message Logging
30-2
30-2
Default System Message Logging Configuration
30-3
30-4
Setting the Message Display Destination Device
30-4
30-5
Enabling and Disabling Time Stamps on Log Messages
30-7
Enabling and Disabling Sequence Numbers in Log Messages
30-7
Defining the Message Severity Level
30-8
Limiting Syslog Messages Sent to the History Table and to SNMP
30-9
Enabling the Configuration-Change Logger
30-10
Configuring UNIX Syslog Servers
30-11
Logging Messages to a UNIX Syslog Daemon
30-11
Configuring the UNIX System Logging Facility
30-12
Displaying the Logging Configuration
30-13
31-1
31-1
31-2
31-3
31-4
31-4
Using SNMP to Access MIB Variables
31-4
31-5
SNMP ifIndex MIB Object Values
31-5
31-6
31-6
31-6
31-7
31-8
Configuring SNMP Groups and Users
31-9
Configuring SNMP Notifications
31-12
Setting the CPU Threshold Notification Types and Values
31-16
Setting the Agent Contact and Location Information
31-16
Limiting TFTP Servers Used Through SNMP
31-17
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide xxiv OL-27326-01
OL-27326-01
31-17
31-19
Configuring Embedded Event Manager
32-1
Understanding Embedded Event Manager
32-1
32-2
Embedded Event Manager Actions
32-4
Embedded Event Manager Policies
32-4
Embedded Event Manager Environment Variables
32-5
32-5
Configuring Embedded Event Manager
32-6
Registering and Defining an Embedded Event Manager Applet
32-6
Registering and Defining an Embedded Event Manager TCL Script
32-7
Displaying Embedded Event Manager Information
32-7
Configuring Network Security with ACLs
33-1
33-2
33-2
33-3
33-4
33-5
Handling Fragmented and Unfragmented Traffic
33-5
33-6
Creating Standard and Extended IPv4 ACLs
33-7
33-8
33-8
Creating a Numbered Standard ACL
33-9
Creating a Numbered Extended ACL
33-10
33-14
Creating Named Standard and Extended ACLs
33-14
33-16
33-18
Applying an IPv4 ACL to a Terminal Line
33-18
Applying an IPv4 ACL to an Interface
33-19
Hardware and Software Treatment of IP ACLs
33-21
33-21
IPv4 ACL Configuration Examples
33-22
33-24
33-24
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
Contents xxv
Contents
33-24
Time Range Applied to an IP ACL
33-25
33-25
33-26
Creating Named MAC Extended ACLs
33-27
Applying a MAC ACL to a Layer 2 Interface
33-28
33-29
VLAN Map Configuration Guidelines
33-30
33-31
Examples of ACLs and VLAN Maps
33-32
33-34
Using VLAN Maps in Your Network
33-34
33-34
Denying Access to a Server on Another VLAN
33-36
33-37
Using VLAN Maps with Router ACLs
33-38
VLAN Maps and Router ACL Configuration Guidelines
33-38
Examples of Router ACLs and VLAN Maps Applied to VLANs
33-39
33-39
33-40
Displaying IPv4 ACL Configuration
33-41
34-1
34-1
34-3
34-5
Classification Based on QoS ACLs
34-7
Classification Based on Class Maps and Policy Maps
34-7
34-8
34-9
34-10
34-12
Queueing and Scheduling Overview
34-13
34-13
34-14
Queueing and Scheduling on Ingress Queues
34-15
Queueing and Scheduling on Egress Queues
34-17
34-19
34-20
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide xxvi OL-27326-01
OL-27326-01
Contents
Generated Auto-QoS Configuration
34-21
34-21
Enhanced Auto-QoS for Video, Trust, and Classification
34-22
Auto-QoS Configuration Migration
34-22
Auto-QoS Generated Configuration For VoIP Devices
34-26
Auto-QoS Generated Configuration For Enhanced Video, Trust, and Classify Devices
34-27
Effects of Auto-QoS on the Configuration
34-30
Auto-QoS Configuration Guidelines
34-30
34-31
Auto-QoS Enhanced Considerations
34-31
34-31
Troubleshooting Auto QoS Commands
34-32
Displaying Auto-QoS Information
34-33
34-33
Default Standard QoS Configuration
34-34
Default Ingress Queue Configuration
34-34
Default Egress Queue Configuration
34-35
Default Mapping Table Configuration
34-36
Standard QoS Configuration Guidelines
34-36
34-36
34-37
34-37
34-38
34-38
Enabling VLAN-Based QoS on Physical Ports
34-39
Configuring Classification Using Port Trust States
34-39
Configuring the Trust State on Ports within the QoS Domain
34-39
Configuring the CoS Value for an Interface
34-41
Configuring a Trusted Boundary to Ensure Port Security
34-42
Enabling DSCP Transparency Mode
34-43
Configuring the DSCP Trust State on a Port Bordering Another QoS Domain
34-44
34-46
Classifying Traffic by Using ACLs
34-47
Classifying Traffic by Using Class Maps
34-50
Classifying, Policing, and Marking Traffic on Physical Ports by Using Policy Maps
34-52
Classifying, Policing, and Marking Traffic on SVIs by Using Hierarchical Policy Maps
34-56
Classifying, Policing, and Marking Traffic by Using Aggregate Policers
34-63
34-65
Configuring the CoS-to-DSCP Map
34-66
Configuring the IP-Precedence-to-DSCP Map
34-67
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide xxvii
Contents
Configuring the Policed-DSCP Map
34-68
Configuring the DSCP-to-CoS Map
34-69
Configuring the DSCP-to-DSCP-Mutation Map
34-70
Configuring Ingress Queue Characteristics
34-71
Mapping DSCP or CoS Values to an Ingress Queue and Setting WTD Thresholds
34-72
Allocating Buffer Space Between the Ingress Queues
34-73
Allocating Bandwidth Between the Ingress Queues
34-74
Configuring the Ingress Priority Queue
34-75
Configuring Egress Queue Characteristics
34-76
34-76
Allocating Buffer Space to and Setting WTD Thresholds for an Egress Queue-Set
34-77
Mapping DSCP or CoS Values to an Egress Queue and to a Threshold ID
34-79
Configuring SRR Shaped Weights on Egress Queues
34-80
Configuring SRR Shared Weights on Egress Queues
34-81
Configuring the Egress Expedite Queue
34-82
Limiting the Bandwidth on an Egress Interface
34-82
Displaying Standard QoS Information
34-83
35 Configuring EtherChannels and Layer 2 Trunk Failover
35-1
35-1
35-2
35-3
35-4
35-4
PAgP Interaction with Virtual Switches and Dual-Active Detection
35-5
PAgP Interaction with Other Features
35-5
Link Aggregation Control Protocol
35-5
35-6
LACP Interaction with Other Features
35-6
35-6
Load Balancing and Forwarding Methods
35-7
35-8
Default EtherChannel Configuration
35-9
EtherChannel Configuration Guidelines
35-9
Configuring Layer 2 EtherChannels
35-11
Configuring Layer 3 EtherChannels
35-13
Creating Port-Channel Logical Interfaces
35-13
Configuring the Physical Interfaces
35-14
Configuring EtherChannel Load Balancing
35-16
Configuring the PAgP Learn Method and Priority
35-17
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide xxviii OL-27326-01
OL-27326-01
Configuring LACP Hot-Standby Ports
35-18
Configuring the LACP System Priority
35-19
Configuring the LACP Port Priority
35-20
Displaying EtherChannel, PAgP, and LACP Status
35-21
Understanding Layer 2 Trunk Failover
35-21
Configuring Layer 2 Trunk Failover
35-22
Default Layer 2 Trunk Failover Configuration
35-22
Layer 2 Trunk Failover Configuration Guidelines
35-23
Configuring Layer 2 Trunk Failover
35-23
Displaying Layer 2 Trunk Failover Status
35-24
Configuring IP Unicast Routing
36-1
36-1
36-2
36-3
36-3
Default Addressing Configuration
36-4
Assigning IP Addresses to Network Interfaces
36-5
36-5
36-6
Configuring Address Resolution Methods
36-7
36-8
36-9
36-9
Routing Assistance When IP Routing is Disabled
36-10
36-10
36-10
ICMP Router Discovery Protocol (IRDP)
36-11
Configuring Broadcast Packet Handling
36-12
Enabling Directed Broadcast-to-Physical Broadcast Translation
36-12
Forwarding UDP Broadcast Packets and Protocols
36-13
Establishing an IP Broadcast Address
36-14
36-15
Monitoring and Maintaining IP Addressing
36-16
36-17
36-17
36-18
Configuring Basic RIP Parameters
36-19
Configuring RIP Authentication
36-20
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
Contents xxix
Contents
Configuring Summary Addresses and Split Horizon
36-21
36-22
Configuring OSPF for Routed Access
36-23
36-24
Configuring Basic OSPF Parameters
36-25
36-26
Configuring OSPF Area Parameters
36-27
Configuring Other OSPF Parameters
36-28
36-30
Configuring a Loopback Interface
36-30
36-31
36-32
Understanding PIM Stub Routing
36-32
36-33
PIM Stub Routing Configuration Guidelines
36-33
36-33
Understanding EIGRP Stub Routing
36-35
Configuring EIGRP Stub Routing
36-36
Configuring Protocol-Independent Features
36-37
Configuring Cisco Express Forwarding
36-37
Configuring the Number of Equal-Cost Routing Paths
36-38
Configuring Static Unicast Routes
36-39
Specifying Default Routes and Networks
36-40
Using Route Maps to Redistribute Routing Information
36-41
36-43
36-43
Controlling Advertising and Processing in Routing Updates
36-44
Filtering Sources of Routing Information
36-44
36-45
To remove the key chain, use the no key chain
name-of-chain global configuration command.
36-46
User Interface for VRF-Aware RADIUS
36-46
Monitoring and Maintaining the IP Network
36-46
Configuring IPv6 Unicast Routing
37-1
37-1
37-2
Supported IPv6 Unicast Host Features
37-2
128-Bit Wide Unicast Addresses
37-3
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide xxx OL-27326-01
OL-27326-01
37-3
Path MTU Discovery for IPv6 Unicast
37-3
37-4
37-4
37-4
IPv6 Stateless Autoconfiguration and Duplicate Address Detection
37-4
37-5
Dual IPv4 and IPv6 Protocol Stacks
37-5
DHCP for IPv6 Address Assignment
37-6
37-6
37-6
37-7
37-7
Unsupported IPv6 Unicast Routing Features
37-7
37-8
37-9
37-9
Configuring IPv6 Addressing and Enabling IPv6 Routing
37-9
Configuring Default Router Preference
37-12
Configuring IPv4 and IPv6 Protocol Stacks
37-12
Configuring IPv6 ICMP Rate Limiting
37-14
37-14
Configuring Static Routes for IPv6
37-15
37-16
37-17
38-1
38-1
38-2
38-3
Multicast Client Aging Robustness
38-3
38-3
38-4
MLD Done Messages and Immediate-Leave
38-4
Topology Change Notification Processing
38-5
38-5
Default MLD Snooping Configuration
38-5
MLD Snooping Configuration Guidelines
38-6
Enabling or Disabling MLD Snooping
38-6
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
Contents xxxi
Contents
Configuring a Static Multicast Group
38-8
Configuring a Multicast Router Port
38-8
38-9
Configuring MLD Snooping Queries
38-10
Disabling MLD Listener Message Suppression
38-11
Displaying MLD Snooping Information
38-11
39-1
39-1
39-2
39-2
39-3
Default IPv6 ACL Configuration
39-3
Interaction with Other Features
39-3
39-4
Applying an IPv6 ACL to an Interface
39-6
39-7
Configuring HSRP, VRRP, and Enhanced Object Tracking
40-1
40-1
40-3
40-4
40-5
40-5
40-5
40-6
40-7
40-9
Configuring HSRP Authentication and Timers
40-10
Enabling HSRP Support for ICMP Redirect Messages
40-11
Displaying HSRP Configurations
40-11
40-12
40-12
Configuring Enhanced Object Tracking
40-12
Understanding Enhanced Object Tracking
40-13
Configuring Enhanced Object Tracking Features
40-13
Tracking Interface Line-Protocol or IP Routing State
40-13
40-14 xxxii
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
OL-27326-01
Configuring HSRP Object Tracking
40-18
Configuring Other Tracking Characteristics
40-19
Monitoring Enhanced Object Tracking
40-19
Configuring Cisco IOS IP SLAs Operations
41-1
Understanding Cisco IOS IP SLAs
41-1
Using Cisco IOS IP SLAs to Measure Network Performance
41-3
IP SLAs Responder and IP SLAs Control Protocol
41-4
Response Time Computation for IP SLAs
41-4
Configuring IP SLAs Operations
41-5
41-5
41-5
Configuring the IP SLAs Responder
41-6
41-6
42-1
Recovering from a Software Failure
42-2
Recovering from a Lost or Forgotten Password
42-4
Procedure with Password Recovery Enabled
42-5
Procedure with Password Recovery Disabled
42-7
Preventing Autonegotiation Mismatches
42-8
SFP Module Security and Identification
42-9
42-9
42-9
42-10
42-10
42-11
Understanding Layer 2 Traceroute
42-11
42-11
42-13
42-13
42-13
42-14
42-15
Enabling Debugging on a Specific Feature
42-15
Enabling All-System Diagnostics
42-16
Redirecting Debug and Error Message Output
42-16
Using the show platform forward Command
42-16
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
Contents xxxiii
Contents
42-18
42-19
42-19
Memory Consistency Check Routines
42-19
Displaying TCAM Memory Consistency Check Errors
42-20
Troubleshooting CPU Utilization
42-21
Possible Symptoms of High CPU Utilization
42-21
Verifying the Problem and Cause
42-21
Configuring Online Diagnostics
43-1
Understanding How Online Diagnostics Work
43-1
43-1
Configuring Health-Monitoring Diagnostics
43-2
Running Online Diagnostic Tests
43-3
Starting Online Diagnostic Tests
43-3
Displaying Online Diagnostic Tests and Test Results
43-3
Working with the Cisco IOS File System, Configuration Files, and Software Images
44-1
Working with the Flash File System
44-1
Displaying Available File Systems
44-2
Setting the Default File System
44-3
Displaying Information about Files on a File System
44-3
Changing Directories and Displaying the Working Directory
44-3
Creating and Removing Directories
44-4
44-4
44-5
Creating, Displaying, and Extracting tar Files
44-5
44-6
Displaying the Contents of a tar File
44-6
44-8
Displaying the Contents of a File
44-8
Working with Configuration Files
44-8
Guidelines for Creating and Using Configuration Files
44-9
Configuration File Types and Location
44-10
Creating a Configuration File By Using a Text Editor
44-10
Copying Configuration Files By Using TFTP
44-10
Preparing to Download or Upload a Configuration File By Using TFTP
44-11
Downloading the Configuration File By Using TFTP
44-11 xxxiv
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
OL-27326-01
Uploading the Configuration File By Using TFTP
44-12
Copying Configuration Files By Using FTP
44-12
Preparing to Download or Upload a Configuration File By Using FTP
44-13
Downloading a Configuration File By Using FTP
44-13
Uploading a Configuration File By Using FTP
44-14
Copying Configuration Files By Using RCP
44-15
Preparing to Download or Upload a Configuration File By Using RCP
44-16
Downloading a Configuration File By Using RCP
44-17
Uploading a Configuration File By Using RCP
44-18
Clearing Configuration Information
44-18
Clearing the Startup Configuration File
44-19
Deleting a Stored Configuration File
44-19
Replacing and Rolling Back Configurations
44-19
Understanding Configuration Replacement and Rollback
44-19
44-20
Configuring the Configuration Archive
44-21
Performing a Configuration Replacement or Rollback Operation
44-22
44-23
44-23
tar File Format of Images on a Server or Cisco.com
44-24
Copying Image Files By Using TFTP
44-25
Preparing to Download or Upload an Image File By Using TFTP
44-25
Downloading an Image File By Using TFTP
44-26
Uploading an Image File By Using TFTP
44-27
Copying Image Files By Using FTP
44-28
Preparing to Download or Upload an Image File By Using FTP
44-28
Downloading an Image File By Using FTP
44-29
Uploading an Image File By Using FTP
44-31
Copying Image Files By Using RCP
44-32
Preparing to Download or Upload an Image File By Using RCP
44-32
Downloading an Image File By Using RCP
44-34
Uploading an Image File By Using RCP
44-35
Unsupported Commands in Cisco IOS Release 15.0(2)SE
45-1
45-1
Unsupported Privileged EXEC Commands
45-1
Unsupported Global Configuration Commands
45-1
Unsupported Route-Map Configuration Command
45-1
45-2
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
Contents xxxv
Contents
Unsupported Privileged EXEC Commands
45-2
45-2
Unsupported Global Configuration Commands
45-2
Unsupported Interface Configuration Commands
45-2
45-2
45-2
Unsupported Global Configuration Command
45-2
45-3
Unsupported Privileged EXEC Commands
45-3
45-3
Unsupported Global Configuration Commands
45-3
Unsupported Privileged EXEC Commands
45-3
45-3
Unsupported Global Configuration Commands
45-3
Unsupported Interface Configuration Commands
45-3
45-4
Unsupported Global Configuration Command
45-4
45-4
Unsupported Privileged EXEC Command
45-4
Unsupported Global Configuration Command
45-4
Unsupported Interface Configuration Command
45-4
45-4
Unsupported Privileged EXEC or User EXEC Commands
45-4
Unsupported Global Configuration Commands
45-4
Unsupported Interface Configuration Commands
45-5
Unsupported Route Map Commands
45-5
45-7
Unsupported Privileged EXEC Commands
45-7
Unsupported Global Configuration Commands
45-7
45-7
Unsupported User EXEC Commands
45-7
Unsupported Privileged EXEC Commands
45-7
Unsupported Global Configuration Commands
45-8
45-8
Unsupported Global Configuration Commands
45-8
Network Address Translation (NAT) Commands
45-8
Unsupported Privileged EXEC Commands
45-8
45-8
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide xxxvi OL-27326-01
Unsupported Global Configuration Command
45-8
Unsupported Interface Configuration Commands
45-8
Unsupported Policy-Map Configuration Command
45-9
45-9
Unsupported Global Configuration Commands
45-9
45-9
Unsupported Global Configuration Commands
45-9
45-9
Unsupported Global Configuration Command
45-9
Unsupported Interface Configuration Command
45-9
45-10
Unsupported Global Configuration Command
45-10
Unsupported User EXEC Commands
45-10
45-10
Unsupported Privileged EXEC Command
45-10
Contents
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide xxxvii
Contents xxxviii
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Preface
Audience
This guide is for the networking professional managing the Cisco Catalyst Blade Switch 3030 for Dell, referred to as the switch . Before using this guide, you should have experience working with the Cisco
IOS software and be familiar with the concepts and terminology of Ethernet and local area networking.
Purpose
The Layer 3 switch IP base image provides Layer 2+ features including access control lists (ACLs), quality of service (QoS), static routing, EIGRP and PIM stub routing, and the Routing Information
Protocol (RIP).
This guide provides the information that you need to configure Cisco IOS software features on your switch. The Cisco Catalyst Blade Switch 3030 for Dell software provides enterprise-class intelligent services such as access control lists (ACLs) and quality of service (QoS) features.
This guide provides procedures for using the commands that have been created or changed for use with the Cisco Catalyst Blade Switch 3030 for Dell switch. It does not provide detailed information about these commands. For detailed information about these commands, see the Cisco Catalyst Blade
Switch 3030 for Dell Command Reference for this release. For information about the standard Cisco IOS
Release 15.0 commands, see the Cisco IOS documentation set available from the Cisco.com.
This guide does not provide detailed information on the graphical user interface (GUIs) for the embedded device manager that you can use to manage the switch. However, the concepts in this guide are applicable to the GUI user. For information about the device manager, see the switch online help.
This guide does not describe system messages you might encounter or how to install your switch. For more information, see the Cisco Catalyst Blade Switch 3030 for Dell System Message Guide for this release and the Cisco Catalyst Blade Switch 3030 for Dell 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.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide xxxix
Preface
•
•
Arguments for which you supply values are in italic .
Square brackets ([ ]) mean optional elements.
Braces ({ }) group required choices, and vertical bars ( | ) separate the alternative elements.
•
• Braces and vertical bars within square brackets ([{ | }]) mean a required choice within an optional element.
Interactive examples use these conventions:
•
•
Terminal sessions and system displays are in screen font.
Information you enter is in boldface screen
font.
• Nonprinting characters, such as passwords or tabs, are in angle brackets (< >).
Notes, cautions, and timesavers use these conventions and symbols:
Note Means reader take note . Notes contain helpful suggestions or references to materials not contained in this manual.
Caution Means reader be careful . In this situation, you might do something that could result in equipment damage or loss of data.
Related Publications
For more information about the switch, see the Cisco Catalyst Blade Switch 3030 for Dell documentation on Cisco.com: http://www.cisco.com/en/US/products/ps8742/tsd_products_support_series_home.html
Note Before installing, configuring, or upgrading the switch, see these documents:
•
•
•
For initial configuration information, see the blade switch configuration and installation instructions in the getting started guide or the “Configuring the Switch with the CLI-Based Setup Program” appendix in the hardware installation guide.
For device manager requirements, see the “System Requirements” section in the release notes (not orderable but available on Cisco.com).
For upgrading information, see the “Downloading Software” section in the release notes.
•
•
•
•
•
•
•
Release Notes for the Cisco Catalyst Blade Switch 3030 for Dell, Cisco IOS Release 12.2(50)SE
Cisco Catalyst Blade Switch 3030 for Dell System Message Guide
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
Cisco Catalyst Blade Switch 3030 for Dell Command Reference
Device manager online help (available on the switch)
Cisco Catalyst Blade Switch 3030 for Dell Hardware Installation Guide
Cisco Catalyst Blade Switch 3030 for Dell Getting Started Guide xl
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Preface
•
•
•
Regulatory Compliance and Safety Information for the Cisco Catalyst Blade Switch 3030 for Dell
Cisco Small Form-Factor Pluggable Modules Installation Notes
These compatibility matrix documents are available from this Cisco.com site: http://www.cisco.com/en/US/products/hw/modules/ps5455/products_device_support_tables_list.ht
ml
– Cisco Gigabit Ethernet Transceiver Modules Compatibility Matrix
–
–
Cisco Small Form-Factor Pluggable Modules Compatibility Matrix
Compatibility Matrix for 1000BASE-T Small Form-Factor Pluggable Modules
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation , which also lists all new and revised Cisco technical documentation, at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide xli
Preface xlii
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
C H A P T E R
1
Overview
This chapter provides these topics about the switch software:
•
•
•
Default Settings After Initial Switch Configuration, page 1-12
Design Concepts for Using the Switch, page 1-15
•
In this document, IP refers to IP Version 4 (IPv4) unless there is a specific reference to IP Version 6
(IPv6).
Features
The switch ships with the IP base image installed, which provides Layer 2+ features (enterprise-class intelligent services). These features include access control lists (ACLs), quality of service (QoS), static routing, EIGRP and PIM stub routing, the Hot Standby Router Protocol (HSRP), the Routing
Information Protocol (RIP), IPv6 host management, and IPv6 MLD snooping.
Some features described in this chapter are available only on the cryptographic (supports encryption) version of the software. You must obtain authorization to use this feature and to download the cryptographic version of the software from Cisco.com. For more information, see the release notes for this release.
The switch has these features:
•
•
•
•
Ease-of-Deployment and Ease-of-Use Features, page 1-2
Performance Features, page 1-2
Manageability Features, page 1-4
(includes a feature requiring the cryptographic version of the software)
•
•
•
•
•
•
Availability and Redundancy Features, page 1-5
Security Features, page 1-7 (includes a feature requiring the cryptographic version of the software)
QoS and CoS Features, page 1-10
Monitoring Features, page 1-12
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
1-1
Chapter 1 Overview
Features
Ease-of-Deployment and Ease-of-Use Features
The switch ships with an embedded device manager GUI for configuring and monitoring a single switch through a web browser. For more information about launching the device manager, see the getting started guide. For more information about the device manager, see the switch online help.
• User-defined and Cisco-default Smartports macros for creating custom switch configurations for simplified deployment across the network.
•
•
AutoSmartport enhancements, which add support for global macros, last-resort macros, event trigger control, access points, EtherChannels, auto-QoS with Cisco Medianet, and IP phones.
Call Home to provide e-mail-based and web-based notification of critical system events. Users with a service contract directly with Cisco Systems can register Call Home devices for the Cisco Smart
Call Home service that generates automatic service requests with the Cisco TAC.
Performance Features
The switch ships with these performance features:
• Autosensing of port speed and autonegotiation of duplex mode on all switch ports for optimizing bandwidth
•
•
•
Automatic-medium-dependent interface crossover (auto-MDIX) capability on 10/100/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
•
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) full-duplex bandwidth among switches, routers, and servers
•
•
•
•
Port Aggregation Protocol (PAgP) and Link Aggregation Control Protocol (LACP) for automatic creation of EtherChannel links
Forwarding of Layer 2 and Layer 3 packets at Gigabit line rate
Per-port storm control for preventing broadcast, multicast, and unicast storms
Port blocking on forwarding unknown Layer 2 unknown unicast, multicast, and bridged broadcast traffic
•
•
•
•
Protocol storm protection to control the rate of incoming protocol traffic to a switch by dropping packets that exceed a specified ingress rate
Cisco Group Management Protocol (CGMP) server support and Internet Group Management
Protocol (IGMP) snooping for IGMP Versions 1, 2, and 3:
–
–
(For CGMP devices) CGMP for limiting multicast traffic to specified end stations and reducing overall network traffic
(For IGMP devices) IGMP snooping for efficiently forwarding multimedia and multicast traffic
Internet Group Management Protocol (IGMP) snooping for IGMP Versions 1, 2, and 3 for efficiently forwarding multimedia and multicast traffic
IGMP report suppression for sending only one IGMP report per multicast router query to the multicast devices (supported only for IGMPv1 or IGMPv2 queries)
1-2
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 1 Overview
Features
•
•
•
•
•
•
•
•
•
•
•
•
•
•
IGMP snooping querier support to configure switch to generate periodic IGMP General Query messages
IGMP helper to allow the switch to forward a host request to join a multicast stream to a specific IP destination address
Multicast Listener Discovery (MLD) snooping to enable efficient distribution of IP Version 6 (IPv6) multicast data to clients and routers in a switched network.
Multicast VLAN registration (MVR) to continuously send multicast streams in a multicast VLAN while isolating the streams from subscriber VLANs for bandwidth and security reasons
IGMP filtering for controlling the set of multicast groups to which hosts on a switch port can belong
IGMP throttling for configuring the action when the maximum number of entries is in the IGMP forwarding table
IGMP leave timer for configuring the leave latency for the network
Switch Database Management (SDM) templates for allocating system resources to maximize support for user-selected features
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)
RADIUS server load balancing to allow access and authentication requests to be distributed evenly across a server group
Cisco Medianet to enable intelligent services in the network infrastructure for a wide variety of video applications. One of the services of Medianet is auto provisioning for Cisco Digital Media
Players and Cisco IP Video Surveillance cameras through Auto Smartports.
Multicast VLAN registration (MVR) enhancements include the ability to configure 2000 MVR groups when the switch is in dynamic MVR mode and a new command ( mvr ringmode flood ) to ensure that forwarding in a ring topology is limited to member ports.
Memory consistency check routines to detect and correct invalid ternary content addressable memory (TCAM) table entries.
Management Options
These are the options for configuring and managing the switch:
•
•
An embedded device manager—The device manager is a GUI that is integrated in the software image. You use it to configure and to monitor a single switch. For information about launching the device manager, see the getting started guide. For more information about the device manager, see the switch online help.
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 asHP 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 31, “Configuring SNMP.”
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
1-3
Features
Chapter 1 Overview
• 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, see
Chapter 4, “Configuring Cisco IOS
Note For additional descriptions of the management interfaces, see the
“Design Concepts for Using the
.
Manageability Features
These are the manageability features:
• CNS embedded agents for automating switch management, configuration storage, and delivery
•
•
•
DHCP for automating configuration of switch information (such as IP address, default gateway, hostname, and Domain Name System [DNS] and TFTP server names)
DHCP relay for forwarding User Datagram Protocol (UDP) broadcasts, including IP address requests, from DHCP clients
DHCP server for automatic assignment of IP addresses and other DHCP options to IP hosts
•
•
•
•
•
•
DHCP-based autoconfiguration and image update to download a specified configuration a new image to a large number of switches
DHCP server port-based address allocation for the preassignment of an IP address to a switch port
Directed unicast requests to a DNS server for identifying a switch through its IP address and its corresponding hostname and to a TFTP server for administering software upgrades from a TFTP server
Address Resolution Protocol (ARP) for identifying a switch through its IP address and its corresponding MAC address
Unicast MAC address filtering to drop packets with specific source or destination MAC addresses
Disabling MAC address learning on a VLAN
•
•
•
•
•
•
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
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
CDP and LLDP enhancements for exchanging location information with video end points for dynamic location-based content distribution from servers
1-4
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 1 Overview
Features
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Wired location service sends location and attachment tracking information for connected devices to a Cisco Mobility Services Engine (MSE)
Network Time Protocol (NTP) for providing a consistent time stamp to all switches from an external source
Network Time Protocol version 4 (NTPv4) to support both IPv4 and IPv6 and compatibility with
NTPv3
Cisco IOS File System (IFS) for providing a single interface to all file systems that the switch uses
Configuration logging to log and to view changes to the switch configuration
Unique device identifier to provide product identification information through a show inventory user EXEC command display
In-band management access through the device manager over a Netscape Navigator or Microsoft
Internet Explorer browser session
In-band management access for up to 16 simultaneous Telnet connections for multiple CLI-based sessions over the network
In-band management access for up to five simultaneous, encrypted Secure Shell (SSH) connections for multiple CLI-based sessions over the network (requires the cryptographic version of the software)
In-band management access through SNMP Versions 1, 2c, and 3 get and set requests
Out-of-band management access through the switch console port to a directly attached terminal or to a remote terminal through a serial connection or a modem
CPU utilization threshold trap monitors CPU utilization
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)
The HTTP client in Cisco IOS supports can send requests to both IPv4 and IPv6 HTTP servers, and the HTTP server in Cisco IOS can service HTTP requests from both IPv4 and IPv6 HTTP clients.
Simple Network and Management Protocol (SNMP) can be configured over IPv6 transport so that an IPv6 host can send SNMP queries and receive SNMP notifications from a device running IPv6.
IPv6 supports stateless autoconfiguration to manage link, subnet, and site addressing changes, such as management of host and mobile IP addresses.
Support for including a hostname in the option 12 field of DHCPDISCOVER packets. This provides identical configuration files to be sent by using the DHCP protocol.DHCP Snooping enhancement to support the selection of a fixed string-based format for the circuit-id sub-option of the Option 82
DHCP field.
Availability and Redundancy Features
These are the availability and redundancy features:
• HSRP for command switch and Layer 3 router redundancy
•
•
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
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
1-5
Features
Chapter 1 Overview
•
•
•
•
•
– Per-VLAN spanning-tree plus (PVST+) for load balancing across VLANs
–
–
Rapid PVST+ for load balancing across VLANs and providing rapid convergence of spanning-tree instances
UplinkFast and BackboneFast for fast convergence after a spanning-tree topology change and for achieving load balancing between redundant uplinks, including Gigabit uplinks
IEEE 802.1s Multiple Spanning Tree Protocol (MSTP) for grouping VLANs into a spanning-tree instance and for providing multiple forwarding paths for data traffic and load balancing and rapid per-VLAN Spanning-Tree plus (rapid-PVST+) based on the IEEE 802.1w Rapid Spanning Tree
Protocol (RSTP) for rapid convergence of the spanning tree by immediately changing root and designated ports to the forwarding state
Optional spanning-tree features available in PVST+, rapid-PVST+, and MSTP mode:
–
–
Port Fast for eliminating the forwarding delay by enabling a port to immediately change from the blocking state to the forwarding state
BPDU guard for shutting down Port Fast-enabled ports that receive bridge protocol data units
(BPDUs)
–
–
BPDU filtering for preventing a Port Fast-enabled port from sending or receiving BPDUs
Root guard for preventing switches outside the network core from becoming the spanning-tree root
– Loop guard for preventing alternate or root ports from becoming designated ports because of a failure that leads to a unidirectional link
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 (Layer 2 trunk failover) to mirror the state of the external Ethernet links and to allow the failover of the processor blade traffic to an operational external link on a separate Cisco
Ethernet switch
VLAN Features
These are the VLAN features:
• Support for up to 1005 VLANs for assigning users to VLANs associated with appropriate network resources, traffic patterns, and bandwidth
•
•
•
Support for VLAN IDs in the 1 to 4094 range as allowed by the IEEE 802.1Q standard
VLAN Query Protocol (VQP) for dynamic VLAN membership
•
Inter-Switch Link (ISL) and IEEE 802.1Q trunking encapsulation on all ports for network moves, adds, and changes; management and control of broadcast and multicast traffic; and network security by establishing VLAN groups for high-security users and network resources
Dynamic Trunking Protocol (DTP) for negotiating trunking on a link between two devices and for negotiating the type of trunking encapsulation (IEEE 802.1Q or ISL) to be used
•
•
VLAN Trunking Protocol (VTP) and VTP pruning for reducing network traffic by restricting flooded traffic to links destined for stations receiving the traffic
Voice VLAN for creating subnets for voice traffic from Cisco IP Phones
1-6
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 1 Overview
Features
•
•
•
•
•
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.
Private VLANs to address VLAN scalability problems, to provide a more controlled IP address allocation, and to allow Layer 2 ports to be isolated from other ports on the switch
Port security on a PVLAN host to limit the number of MAC addresses learned on a port, or define which MAC addresses may be learned on a port
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
The switch ships with these security features:
• IP Service Level Agreements (IP SLAs) support to measure network performance by using active traffic monitoring
•
•
Web authentication to allow a supplicant (client) that does not support IEEE 802.1x functionality to be authenticated using a web browser
MAC authentication bypass (MAB) aging timer to detect inactive hosts that have authenticated after they have authenticated by using MAB
•
•
•
•
•
Local web authentication banner so that custom banner or image file can be displayed at a web authentication login screen
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 shut down the VLAN on the port when a violation occurs, instead of shutting down the entire port.
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
Port security aging to set the aging time for secure addresses on a port
BPDU guard for shutting down a Port Fast-configured port when an invalid configuration occurs
•
Standard and extended IP access control lists (ACLs) for defining security policies in both directions on routed interfaces (router ACLs) and VLANs and inbound on Layer 2 interfaces (port ACLs)
Extended MAC access control lists for defining security policies in the inbound direction on Layer 2 interfaces
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
1-7
Features
Chapter 1 Overview
•
•
•
•
•
•
•
•
•
•
•
•
VLAN ACLs (VLAN maps) for providing intra-VLAN security by filtering traffic based on information in the MAC, IP, and TCP/UDP headers
Source and destination MAC-based ACLs for filtering non-IP traffic
Support for dynamic creation or attachment of an auth-default ACL on a port that has no configured static ACLs
DHCP snooping to filter untrusted DHCP messages between untrusted hosts and DHCP servers
IP source guard to restrict traffic on nonrouted interfaces by filtering traffic based on the DHCP snooping database and IP source bindings
Dynamic ARP inspection to prevent malicious attacks on the switch by not relaying invalid ARP requests and responses to other ports in the same VLAN
IEEE 802.1Q tunneling so that customers with users at remote sites across a service-provider network can keep VLANs segregated from other customers and Layer 2 protocol tunneling to ensure that the customer’s network has complete STP, CDP, and VTP information about all users
Layer 2 point-to-point tunneling to facilitate the automatic creation of EtherChannels
Layer 2 protocol tunneling bypass feature to provide interoperability with third-party vendors
IEEE 802.1x with open access to allow a host to access the network before being authenticated
Flexible-authentication sequencing to configure the order of the authentication methods that a port tries when authenticating a new host
IEEE 802.1x port-based authentication to prevent unauthorized devices (clients) from gaining access to the network. These features are supported:
– VLAN assignment for restricting IEEE 802.1x-authenticated users to a specified VLAN
–
–
Port security for controlling access to IEEE 802.1x ports
Voice VLAN to permit a Cisco IP Phone to access the voice VLAN regardless of the authorized or unauthorized state of the port
–
–
Guest VLAN to provide limited services to non-IEEE 802.1x-compliant users
Restricted VLAN to provide limited services to users who are IEEE 802.1x compliant, but do not have the credentials to authenticate via the standard IEEE 802.1x processes
–
–
Support for VLAN assignment on a port configured for multi-auth mode. The RADIUS server assigns a VLAN to the first host to authenticate on the port, and subsequent hosts use the same
VLAN. Voice VLAN assignment is supported for one IP phone.
IEEE 802.1x accounting to track network usage
–
–
IEEE 802.1x with wake-on-LAN to allow dormant PCs to be powered on based on the receipt of a specific Ethernet frame
IEEE 802.1x readiness check to determine the readiness of connected end hosts before configuring IEEE 802.1x on the switch
–
–
Voice aware IEEE 802.1x security to apply traffic violation actions only on the VLAN on which a security violation occurs
Voice aware IEEE 802.1x security to apply traffic violation actions only on the VLAN on which a security violation occurs
– 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
1-8
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 1 Overview
Features
•
•
•
•
•
•
•
•
•
•
•
•
– IEEE 802.1x authentication with downloadable ACLs and redirect URLs to allow per-user ACL downloads from a Cisco Secure ACS server to an authenticated switch
– Multiple-user authentication to allow more than one host to authenticate on an 802.1x-enabled port
MAC authentication bypass to authorize clients based on the client MAC address
Network Admission Control (NAC) features:
– NAC Layer 2 IEEE 802.1x validation of the antivirus condition or posture of endpoint systems or clients before granting the devices network access.
–
For information about configuring NAC Layer 2 IEEE 802.1x validation, see the
NAC Layer 2 802.1x Validation” section on page 8-58
.
NAC Layer 2 IP validation of the posture of endpoint systems or clients before granting the devices network access.
–
–
For information about configuring NAC Layer 2 IP validation, see the Network Admission
Control Software Configuration Guide .
IEEE 802.1x inaccessible authentication bypass.
For information about configuring this feature, see the
Authentication Bypass Feature” section on page 8-53
.
Authentication, authorization, and accounting (AAA) down policy for a NAC Layer 2 IP validation of a host if the AAA server is not available when the posture validation occurs.
For information about this feature, see the Network Admission Control Software Configuration
Guide .
TACACS+, a proprietary feature for managing network security through a TACACS server
RADIUS for verifying the identity of, granting access to, and tracking the actions of remote users through authentication, authorization, and accounting (AAA) services
Enhancements to RADIUS, TACACS+, and SSH to function over IPv6.
Kerberos security system to authenticate requests for network resources by using a trusted third party (requires the cryptographic version of the software)
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)
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.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
1-9
Features
Chapter 1 Overview
•
•
•
•
•
Support for Network Edge Access Topology (NEAT) to change the port host mode and to apply a standard port configuration on the authenticator switch port.
VLAN-ID based MAC authentication to use the combined VLAN and MAC address information for user authentication to prevent network access from unauthorized VLANs.
MAC move to allow hosts (including the hosts connected behind an IP phone) to move across ports within the same switch without any restrictions to enable mobility. With MAC move, the switch treats the reappearance of the same MAC address on another port in the same way as a completely new MAC address.
Support for 3DES and AES with version 3 of the Simple Network Management Protocol (SNMPv3).
This release adds support for the 168-bit Triple Data Encryption Standard (3DES) and the 128-bit,
192-bit, and 256-bit Advanced Encryption Standard (AES) encryption algorithms to SNMPv3.
Support for the Security Group Tag (SCT) Exchange Protocol (SXP) component of Cisco TrustSec, a security architecture using authentication, encryption, and access control.
QoS and CoS Features
These are the QoS and CoS features:
• Automatic QoS (auto-QoS) to simplify the deployment of existing QoS features by classifying traffic and configuring egress queues
• Classification
– IP type-of-service/Differentiated Services Code Point (IP ToS/DSCP) and IEEE 802.1p CoS marking priorities on a per-port basis for protecting the performance of mission-critical applications
–
–
IP ToS/DSCP and IEEE 802.1p CoS marking based on flow-based packet classification
(classification based on information in the MAC, IP, and TCP/UDP headers) for high-performance quality of service at the network edge, allowing for differentiated service levels for different types of network traffic and for prioritizing mission-critical traffic in the network
Trusted port states (CoS, DSCP, and IP precedence) within a QoS domain and with a port bordering another QoS domain
•
•
•
– Trusted boundary for detecting the presence of a Cisco IP Phone, trusting the CoS value received, and ensuring port security
Policing
–
–
Traffic-policing policies on the switch port for managing how much of the port bandwidth should be allocated to a specific traffic flow
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)
1-10
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 1 Overview
Features
•
•
•
–
– Shaped round robin (SRR) as the scheduling service for specifying the rate at which packets are sent to the internal ring (sharing is the only supported mode on ingress queues)
Egress queues and scheduling
–
Weighted tail drop (WTD) as the congestion-avoidance mechanism for managing the queue lengths and providing drop precedences for different traffic classifications
–
Four egress queues per port
WTD as the congestion-avoidance mechanism for managing the queue lengths and providing drop precedences for different traffic classifications
– SRR as the scheduling service for specifying the rate at which packets are dequeued to the egress interface (shaping or sharing is supported on egress queues). Shaped egress queues are guaranteed but limited to using a share of port bandwidth. Shared egress queues are also guaranteed a configured share of bandwidth, but can use more than the guarantee if other queues become empty and do not use their share of the bandwidth.
Support for IPv6 QoS trust capability.
Auto-QoS enhancements that add automatic configuration classification of traffic flow from video devices, such as the Cisco Telepresence System and Cisco Surveillance Camera.
Layer 3 Features
•
•
•
•
•
•
•
•
•
•
•
•
•
•
HSRP Version 1 (HSRPv1) and HSRP Version 2 (HSRPv2) for Layer 3 router redundancy
IP routing protocols for load balancing and for constructing scalable, routed backbones, including
RIP Versions 1 and 2
OSPF for routed access to enable customers to extend Layer 3 routing capabilities to the access or wiring closet.
IP routing between VLANs (inter-VLAN routing) for full Layer 3 routing between two or more
VLANs, allowing each VLAN to maintain its own autonomous data-link domain
Static IP routing for manually building a routing table of network path information
Equal-cost routing for load balancing and redundancy
Internet Control Message Protocol (ICMP) and ICMP Router Discovery Protocol (IRDP) for using router advertisement and router solicitation messages to discover the addresses of routers on directly attached subnets
DHCP relay for forwarding UDP broadcasts, including IP address requests, from DHCP clients
DHCPv6 bulk-lease query to support new bulk lease query type (as defined in RFC5460).
The DHCPv6 relay source configuration feature to configure a source address for DHCPv6 relay agent.
IPv6 default router preference (DRP) for improving the ability of a host to select an appropriate router
IPv6 unicast host management
The ability to exclude a port in a VLAN from the SVI line-state up or down calculation
Support for the Virtual Router Redundancy Protocol (VRRP for IPv4), which dynamically assigns responsibility for one or more virtual routers to the VRRP routers on a LAN, allowing multiple routers on a multiaccess link to utilize the same virtual IP address.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
1-11
Chapter 1 Overview
Default Settings After Initial Switch Configuration
Monitoring Features
These are the monitoring features:
• Switch LEDs that provide port- and switch-level status
•
•
MAC address notification traps and RADIUS accounting for tracking users on a network by storing the MAC addresses that the switch has learned or removed
Switched Port Analyzer (SPAN) and Remote SPAN (RSPAN) for traffic monitoring on any port or
VLAN
•
•
•
•
SPAN and RSPAN support of Intrusion Detection Systems (IDS) to monitor, repel, and report network security violations
Four groups (history, statistics, alarms, and events) of embedded RMON agents for network monitoring and traffic analysis
Syslog facility for logging system messages about authentication or authorization errors, resource issues, and time-out events
Layer 2 traceroute to identify the physical path that a packet takes from a source device to a destination device
•
•
•
•
•
SFP module diagnostic management interface to monitor physical or operational status of an SFP module
Generic online diagnostics to test hardware functionality of the supervisor engine, modules, and switch while the switch is connected to a live network.
Enhanced object tracking for HSRP.
Support for Embedded Event Manager (EEM) for event detection and recovery within a Cisco IOS device, and EEM 3.2, which introduces event detectors for Neighbor Discovery, Identity, and
MAC-Address-Table.
IETF IP-MIB and IP-FORWARD-MIB(RFC4292 and RFC4293) updates to support the IP version 6
(IPv6)-only and the IPv6 part of the protocol-version independent (PVI) objects and tables.
Default Settings After Initial Switch Configuration
The switch is designed for plug-and-play operation, requiring only that you assign basic IP information to the switch and connect it to the other devices in your network. If you have specific network needs, you can change the interface-specific and system-wide settings.
Note 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
DHCP Features and IP Source Guard.”
• Default domain name is not configured. For more information, see
Chapter 3, “Assigning the Switch
IP Address and Default Gateway.”
1-12
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 1 Overview
Default Settings After Initial Switch Configuration
•
•
•
•
•
•
•
•
•
•
•
•
•
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
Chapter 21, “Configuring DHCP Features and IP
No passwords are defined. For more information, see
Chapter 5, “Administering the Switch.”
System name and prompt is Switch. For more information, see
NTP is enabled. For more information, see
Chapter 5, “Administering the Switch.”
DNS is enabled. For more information, see
Chapter 5, “Administering the Switch.”
TACACS+ is disabled. For more information, see
Chapter 7, “Configuring Switch-Based
RADIUS is disabled. For more information, see
Chapter 7, “Configuring Switch-Based
The standard HTTP server and Secure Socket Layer (SSL) HTTPS server are both enabled. For more information, see
Chapter 7, “Configuring Switch-Based Authentication.”
IEEE 802.1x is disabled. For more information, see
Chapter 8, “Configuring IEEE 802.1x
Port parameters
– Operating mode is Layer 2 (switchport). For more information, see
–
–
Interface speed and duplex mode is autonegotiate. For more information, see
“Configuring Interface Characteristics.”
Auto-MDIX is enabled. For more information, see
Chapter 10, “Configuring Interface
–
–
No Smartports macros are defined. For more information, see Chapter 11, “Configuring Smartports
VLANs
–
Flow control is off. For more information, see
Chapter 10, “Configuring Interface
PortFast is enabled on the ten internal Gigabit Ethernet ports. For more information, see
Chapter 19, “Configuring Optional Spanning-Tree Features.”
–
Default VLAN is VLAN 1. For more information, see
Chapter 12, “Configuring VLANs.”
VLAN trunking setting is dynamic auto (DTP). For more information, see
–
–
–
–
Trunk encapsulation is negotiate. For more information, see
Chapter 12, “Configuring VLANs.”
VTP mode is server. For more information, see
Chapter 13, “Configuring VTP.”
VTP version is Version 1. For more information, see
Chapter 13, “Configuring VTP.”
No private VLANs are configured. For more information, see
Chapter 15, “Configuring Private
– Voice VLAN is disabled. For more information, see
Chapter 14, “Configuring Voice VLAN.”
IEEE 802.1Q tunneling and Layer 2 protocol tunneling are disabled. For more information, see
Chapter 16, “Configuring IEEE 802.1Q and Layer 2 Protocol Tunneling.”
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
1-13
Chapter 1 Overview
Default Settings After Initial Switch Configuration
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
STP, PVST+ is enabled on VLAN 1. For more information, see
Chapter 17, “Configuring STP.”
MSTP is disabled. For more information, see
Chapter 18, “Configuring MSTP.”
Optional spanning-tree features are disabled. For more information, see Chapter 19, “Configuring
Optional Spanning-Tree Features.”
Flex Links are not configured. For more information, see
Chapter 20, “Configuring Flex Links and the MAC Address-Table Move Update Feature.”
DHCP snooping is disabled. The DHCP snooping information option is enabled. For more information, see
Chapter 21, “Configuring DHCP Features and IP Source Guard.”
IP source guard is disabled. For more information, see
Chapter 21, “Configuring DHCP Features and IP Source Guard.”
Dynamic ARP inspection is disabled on all VLANs. For more information, see
“Configuring Dynamic ARP Inspection.”
IGMP snooping is enabled. No IGMP filters are applied. For more information, see
“Configuring IGMP Snooping and MVR.”
IGMP throttling setting is deny. For more information, see
The IGMP snooping querier feature is disabled. For more information, see
MVR is disabled. For more information, see
Chapter 23, “Configuring IGMP Snooping and MVR.”
Port-based traffic
– Broadcast, multicast, and unicast storm control is disabled. For more information, see
Chapter 24, “Configuring Port-Based Traffic Control.”
–
–
No protected ports are defined. For more information, see
Chapter 24, “Configuring Port-Based
Unicast and multicast traffic flooding is not blocked. For more information, see
“Configuring Port-Based Traffic Control.”
– No secure ports are configured. For more information, see
Chapter 24, “Configuring Port-Based
CDP is enabled. For more information, see
Chapter 25, “Configuring CDP.”
UDLD is disabled. For more information, see Chapter 27, “Configuring UDLD.”
SPAN and RSPAN are disabled. For more information, see
Chapter 28, “Configuring SPAN and
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 33, “Configuring Network Security with ACLs.”
QoS is disabled. For more information, see
Chapter 34, “Configuring QoS.”
No EtherChannels are configured. For more information, see
EtherChannels and Layer 2 Trunk Failover.”
IP unicast routing is disabled. For more information, see Chapter 36, “Configuring IP Unicast
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
1-14 OL-27326-01
Chapter 1 Overview
Design Concepts for Using the Switch
• No HSRP groups are configured. For more information, see
Chapter 40, “Configuring HSRP, VRRP, and Enhanced Object Tracking.”
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.
describes what can cause network performance to degrade and how you can configure your network to increase the bandwidth available to your network users.
Table 1-1 Increasing Network Performance
Network Demands
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)
Suggested Design Methods
• 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.
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.
describes some network demands and how you can meet them.
Providing Network Services Table 1-2
Network Demands
Efficient bandwidth usage for multimedia applications and guaranteed bandwidth for critical applications
Suggested Design Methods
•
•
•
Use IGMP snooping to efficiently forward multimedia and multicast traffic.
Use other QoS mechanisms such as packet classification, marking, scheduling, and congestion avoidance to classify traffic with the appropriate priority level, thereby providing maximum flexibility and support for mission-critical, unicast, and multicast and multimedia applications.
Use MVR to continuously send multicast streams in a multicast VLAN but to isolate the streams from subscriber VLANs for bandwidth and security reasons.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
1-15
Chapter 1 Overview
Design Concepts for Using the Switch
Table 1-2 Providing Network Services (continued)
Network Demands
High demand on network redundancy and availability to provide always on mission-critical applications
Suggested Design Methods
• Use Hot Standby Router Protocol (HSRP) for cluster command switch and router redundancy.
• 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.
• 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.
You can use the switches to create the following:
• Cost-effective Gigabit-to-the-blade server for high-performance workgroups (
high-speed access to network resources, you can use the Cisco Catalyst Blade Switch 3030 for Dell in the access layer to provide Gigabit Ethernet to the blade servers. To prevent congestion, use QoS
DSCP marking priorities on these switches. For high-speed IP forwarding at the distribution layer, connect the switches in the access layer to a Gigabit multilayer switch with routing capability, such as a Catalyst 3750 switch, or to a router.
The first illustration is of an isolated high-performance workgroup, where the blade switches are connected to Catalyst 3750 switches in the distribution layer.
Each blade switch in this configuration provides users with a dedicated 1-Gb/s connection to network resources. Using SFP modules also provides flexibility in media and distance options through fiber-optic connections.
Figure 1-1 High-Performance Workgroup (Gigabit-to-the-Blade Server)
Catalyst 3750 switches
Blade Switches
Blade Server Blade Server
1-16
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 1 Overview
Figure 1-2
Where to Go Next
• Server aggregation (
Figure 1-2 )—You can use the switches to interconnect groups of servers,
centralizing physical security and administration of your network. For high-speed IP forwarding at the distribution layer, connect the switches in the access layer to multilayer switches with routing capability. The Gigabit interconnections minimize latency in the data flow.
QoS and policing on the blade switches provide preferential treatment for certain data streams. They segment traffic streams into different paths for processing. Security features on the blade switch ensure rapid handling of packets.
Fault tolerance from the server racks to the core is achieved through dual homing of servers connected to the blade switches, which have redundant Gigabit EtherChannels.
Using dual SFP module uplinks from the blade switches provides redundant uplinks to the network core. Using SFP modules provides flexibility in media and distance options through fiber-optic connections.
Server Aggregation
Campus core
Catalyst 6500 switches
Catalyst 3750
StackWise switch stacks
Blade
Switches
Blade
Servers
Where to Go Next
Before configuring the switch, review these sections for startup information:
•
Chapter 2, “Using the Command-Line Interface”
•
Chapter 3, “Assigning the Switch IP Address and Default Gateway”
To locate and download MIBs for a specific Cisco product and release, use the Cisco MIB Locator: http://cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
1-17
Where to Go Next
Chapter 1 Overview
1-18
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
C H A P T E R
2
Using the Command-Line Interface
This chapter describes the Cisco IOS command-line interface (CLI) and how to use it to configure your switch. It contains these sections:
•
Understanding Command Modes, page 2-1
•
•
•
•
•
Understanding the Help System, page 2-3
Understanding Abbreviated Commands, page 2-3
Understanding no and default Forms of Commands, page 2-4
Understanding CLI Error Messages, page 2-4
•
•
•
•
Using Configuration Logging, page 2-4
Using Command History, page 2-5
Using Editing Features, page 2-6
Searching and Filtering Output of show and more Commands, page 2-9
Understanding Command Modes
The Cisco IOS user interface is divided into many different modes. The commands available to you depend on which mode you are currently in. Enter a question mark (?) at the system prompt to obtain a list of commands available for each command mode.
When you start a session on the switch, you begin in user mode, often called user EXEC mode. Only a limited subset of the commands are available in user EXEC mode. For example, most of the user EXEC commands are one-time commands, such as show commands, which show the current configuration status, and clear commands, which clear counters or interfaces. The user EXEC commands are not saved when the switch reboots.
To have access to all commands, you must enter privileged EXEC mode. Normally, you must enter a password to enter privileged EXEC mode. From this mode, you can enter any privileged EXEC command or enter global configuration mode.
Using the configuration modes (global, interface, and line), you can make changes to the running configuration. If you save the configuration, these commands are stored and used when the switch reboots. To access the various configuration modes, you must start at global configuration mode. From global configuration mode, you can enter interface configuration mode and line configuration mode.
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
2-1 OL-27326-01
Chapter 2 Using the Command-Line Interface
Understanding Command Modes
Table 2-1 describes the main command modes, how to access each one, the prompt you see in that mode,
and how to exit the mode. The examples in the table use the hostname Switch .
Command Mode Summary Table 2-1
Mode
User EXEC
Privileged EXEC
Interface configuration
Line configuration
Access Method
Begin a session with your switch.
While in user EXEC mode, enter the enable command.
Prompt
Switch>
Global configuration While in privileged
EXEC mode, enter the configure command.
VLAN configuration While in global configuration mode, enter the vlan vlan-id command.
Switch(config)#
Switch(config-vlan)#
While in global configuration mode, enter the interface command (with a specific interface).
Switch#
Switch(config-if)#
While in global configuration mode, specify a line with the line vty or line console command.
Switch(config-line)#
Exit Method
Enter logout or quit .
About This Mode
Use this mode to
•
•
Change terminal settings.
Perform basic tests.
• Display system information.
Enter exit.
disable to
To exit to privileged
EXEC mode, enter exit or end , or press
Ctrl-Z .
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.
To exit to global configuration mode, enter the exit command.
To return to privileged EXEC mode, press or enter end .
Ctrl-Z
To exit to global configuration mode, enter exit .
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 parameters for the Ethernet ports.
To return to privileged EXEC mode, press or enter end .
Ctrl-Z
For information about defining interfaces, see the
Interface Configuration Mode” section on page 10-7 .
To configure multiple interfaces with the same parameters, see the
Interfaces” section on page 10-8 .
To exit to global configuration mode, enter exit .
Use this mode to configure parameters for the terminal line.
To return to privileged EXEC mode, press Ctrl-Z or enter end .
2-2
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 2 Using the Command-Line Interface
Understanding the Help System
For more detailed information on the command modes, see the command reference guide for this release.
Understanding the Help System
You can enter a question mark (?) at the system prompt to display a list of commands available for each command mode. You can also obtain a list of associated keywords and arguments for any command, as shown in
Table 2-2 Help Summary
Command help abbreviated-command-entry ?
abbreviated-command-entry < Tab >
?
command ?
command keyword ?
Purpose
Obtain a brief description of the help system in any command mode.
Obtain a list of commands that begin with a particular character string.
For example:
Switch# di?
dir disable disconnect
Complete a partial command name.
For example:
Switch# sh conf <tab>
Switch# show configuration
List all commands available for a particular command mode.
For example:
Switch> ?
List the associated keywords for a command.
For example:
Switch> show ?
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
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
2-3
Chapter 2 Using the Command-Line Interface
Understanding no and default Forms of Commands
Understanding no and default Forms of Commands
Almost every configuration command also has a no form. In general, use the no form to disable a feature or function or reverse the action of a command. For example, the no shutdown interface configuration command reverses the shutdown of an interface. Use the command without the keyword no to re-enable a disabled feature or to enable a feature that is disabled by default.
Configuration commands can also have a default form. The default form of a command returns the command setting to its default. Most commands are disabled by default, so the default form is the same as the no form. However, some commands are enabled by default and have variables set to certain default values. In these cases, the default command enables the command and sets variables to their default values.
Understanding CLI Error Messages
Table 2-3 lists some error messages that you might encounter while using the CLI to configure your
switch.
Table 2-3 Common CLI Error Messages
Error Message
% Ambiguous command:
"show con"
Meaning
You did not enter enough characters for your switch to recognize the command.
How to Get Help
Re-enter the command followed by a question mark (?) with a space between the command and the question mark.
% Incomplete command.
% Invalid input detected at ‘^’ marker.
You did not enter all the keywords or values required by this command.
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.
You entered the command incorrectly. The caret (^) marks the point of the error.
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.
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.
2-4
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 2 Using the Command-Line Interface
Using Command History
For more information, see the Configuration Change Notification and Logging feature module at this
URL: http://www.cisco.com/en/US/products/sw/iosswrel/ps5207/products_feature_guide09186a00801d1e81.
html
Note Only CLI or HTTP changes are logged.
Using Command History
The software provides a history or record of commands that you have entered. The command history feature is particularly useful for recalling long or complex commands or entries, including access lists.
You can customize this feature to suit your needs as described in these sections:
•
•
Changing the Command History Buffer Size, page 2-5 (optional)
(optional)
•
Disabling the Command History Feature, page 2-6 (optional)
Changing the Command History Buffer Size
By default, the switch records ten command lines in its history buffer. You can alter this number for a current terminal session or for all sessions on a particular line. These procedures are optional.
Beginning in privileged EXEC mode, enter this command to change the number of command lines that the switch records during the current terminal session:
Switch# terminal history
[ size number-of-lines
]
The range is from 0 to 256.
Beginning in line configuration mode, enter this command to configure the number of command lines the switch records for all sessions on a particular line:
Switch(config-line)# history
[ size number-of-lines
]
The range is from 0 to 256.
Recalling Commands
To recall commands from the history buffer, perform one of the actions listed in
are optional.
Table 2-4 Recalling Commands
Action
1
Press Ctrl-P or the up arrow key.
Result
Recall commands in the history buffer, beginning with the most recent command.
Repeat the key sequence to recall successively older commands.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
2-5
Chapter 2 Using the Command-Line Interface
Using Editing Features
Table 2-4 Recalling Commands (continued)
Action
Press
1
Ctrl-N show history
or the down arrow key.
Result
Return to more recent commands in the history buffer after recalling commands with Ctrl-P or the up arrow key. Repeat the key sequence to recall successively more recent commands.
While in privileged EXEC mode, list the last several commands that you just entered. The number of commands that appear is controlled by the setting of the terminal history global configuration command and the history line configuration command.
1.
The arrow keys function only on ANSI-compatible terminals such as VT100s.
Disabling the Command History Feature
The command history feature is automatically enabled. You can disable it for the current terminal session or for the command line. These procedures are optional.
To disable the feature during the current terminal session, enter the terminal no history privileged
EXEC command.
To disable command history for the line, enter the no history line configuration command.
Using Editing Features
This section describes the editing features that can help you manipulate the command line. It contains these sections:
•
•
•
Enabling and Disabling Editing Features, page 2-6
Editing Commands through Keystrokes, page 2-7
(optional)
Editing Command Lines that Wrap, page 2-8
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
2-6
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 2 Using the Command-Line Interface
Using Editing Features
Editing Commands through Keystrokes
shows the keystrokes that you need to edit command lines. These keystrokes are optional.
Table 2-5 Editing Commands through Keystrokes
Capability
Move around the command line to make changes or corrections.
Keystroke
1
Press Ctrl-B , or press the left arrow key.
Purpose
Move the cursor back one character.
Press Ctrl-F , or press the right arrow key.
Press Ctrl-A .
Press
Press
Press
Press
Ctrl-E
Esc B
Esc F .
.
Ctrl-T .
.
Move the cursor forward one character.
Move the cursor to the beginning of the command line.
Move the cursor to the end of the command line.
Move the cursor back one word.
Move the cursor forward one word.
Transpose the character to the left of the cursor with the character located at the cursor.
Recall the most recent entry in the buffer.
Recall commands from the buffer and paste them in the command line. The switch provides a buffer with the last ten items that you deleted.
Press Ctrl-Y.
Press Esc Y .
Recall the next buffer entry.
The buffer contains only the last 10 items that you have deleted or cut. If you press Esc Y more than ten times, you cycle to the first buffer entry.
Erase the character to the left of the cursor.
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 command line.
Press Ctrl-U or Ctrl-X .
Delete all characters from the cursor to the beginning of the command line.
Press Ctrl-W .
Press Esc D .
Press Esc C .
Capitalize or lowercase words or capitalize a set of letters.
Press Esc L .
Press Esc U .
Designate a particular keystroke as an executable command, perhaps as a shortcut.
Press Ctrl-V or Esc Q .
Delete the word to the left of the cursor.
Delete from the cursor to the end of the word.
Capitalize at the cursor.
Change the word at the cursor to lowercase.
Capitalize letters from the cursor to the end of the word.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
2-7
Chapter 2 Using the Command-Line Interface
Using Editing Features
Table 2-5 Editing Commands through Keystrokes (continued)
Capability
Scroll down a line or screen on displays that are longer than the terminal screen can display.
Keystroke
Press the
1
Return key.
Purpose
Scroll down one line.
Note The More prompt is used for any output that has more lines than can be displayed on the terminal screen, including show command output. You can use the
Return and Space bar keystrokes whenever you see the More prompt.
Redisplay the current command line if the switch suddenly sends a message to your screen.
Press the Space bar.
Scroll down one screen.
Press Ctrl-L or Ctrl-R.
Redisplay the current command line.
1.
The arrow keys function only on ANSI-compatible terminals such as VT100s.
Editing Command Lines that Wrap
You can use a wraparound feature for commands that extend beyond a single line on the screen. When the cursor reaches the right margin, the command line shifts ten spaces to the left. You cannot see the first ten characters of the line, but you can scroll back and check the syntax at the beginning of the command. The keystroke actions are optional.
To scroll back to the beginning of the command entry, press Ctrl-B or the left arrow key repeatedly. You can also press Ctrl-A to immediately move to the beginning of the line.
The arrow keys function only on ANSI-compatible terminals such as VT100s.
In this example, the access-list global configuration command entry extends beyond one line. When the cursor first reaches the end of the line, the line is shifted ten spaces to the left and redisplayed. The dollar sign ($) shows that the line has been scrolled to the left. Each time the cursor reaches the end of the line, the line is again shifted ten spaces to the left.
Switch(config)# access-list 101 permit tcp 131.108.2.5 255.255.255.0 131.108.1
Switch(config)# $ 101 permit tcp 131.108.2.5 255.255.255.0 131.108.1.20 255.25
Switch(config)# $ t tcp 131.108.2.5 255.255.255.0 131.108.1.20 255.255.255.0 eq
Switch(config)# $ 108.2.5 255.255.255.0 131.108.1.20 255.255.255.0 eq 45
After you complete the entry, press Ctrl-A to check the complete syntax before pressing the Return key to execute the command. The dollar sign ($) appears at the end of the line to show that the line has been scrolled to the right:
Switch(config)# access-list 101 permit tcp 131.108.2.5 255.255.255.0 131.108.1$
The software assumes you have a terminal screen that is 80 columns wide. If you have a width other than that, use the terminal width privileged EXEC command to set the width of your terminal.
Use line wrapping with the command history feature to recall and modify previous complex command entries. For information about recalling previous command entries, see the
Keystrokes” section on page 2-7 .
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
2-8 OL-27326-01
Chapter 2 Using the Command-Line Interface
Searching and Filtering Output of show and more Commands
Searching and Filtering Output of show and more Commands
You can search and filter the output for show and more commands. This is useful when you need to sort through large amounts of output or if you want to exclude output that you do not need to see. Using these commands is optional.
To use this functionality, enter a show or more command followed by the pipe character (|), one of the keywords begin , include , or exclude , and an expression that you want to search for or filter out: command | { begin | include | exclude } regular-expression
Expressions are case sensitive. For example, if you enter | exclude output , the lines that contain output are not displayed, but the lines that contain Output appear.
This example shows how to include in the output display only lines where the expression protocol appears:
Switch# show interfaces | include protocol
Vlan1 is up, line protocol is up
Vlan10 is up, line protocol is down
GigabitEthernet0/1 is up, line protocol is down
GigabitEthernet0/2 is up, line protocol is up
Accessing the CLI
You can access the CLI through a console connection, through Telnet, or by using the browser.
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 hardware installation guide that shipped with your switch. Then, to understand the boot up process and the options available for assigning IP information, see
“Assigning the Switch IP Address and Default Gateway.”
If your switch is already configured, you can access the CLI through a local console connection or through a remote Telnet session, but your switch must first be configured for this type of access. For more information, see the
“Setting a Telnet Password for a Terminal Line” section on page 7-6 .
You can use one of these methods to establish a connection with the switch:
• Connect the switch console port to a management station or dial-up modem. For information about connecting to the console port, see the switch hardware installation guide.
• Use any Telnet TCP/IP or encrypted Secure Shell (SSH) package from a remote management station. The switch must have network connectivity with the Telnet or SSH client, and the switch must have an enable secret password configured.
For information about configuring the switch for Telnet access, see the
“Setting a Telnet Password for a Terminal Line” section on page 7-6
. The switch supports up to 16 simultaneous Telnet sessions.
Changes made by one Telnet user are reflected in all other Telnet sessions.
For information about configuring the switch for SSH, see the
“Configuring the Switch for Secure
Shell” section on page 7-43 . 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.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
2-9
Accessing the CLI
Chapter 2 Using the Command-Line Interface
2-10
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
C H A P T E R
3
Assigning the Switch IP Address and Default
Gateway
This chapter describes how to create the initial switch configuration (for example, assigning the IP address and default gateway information) by using a variety of automatic and manual methods. It also describes how to modify the switch startup configuration.
Note For complete syntax and usage information for the commands used in this chapter, see the command reference for this release and the Cisco IOS IP Command Reference, Volume 1 of 3: Addressing and
Services from Cisco.com.
This chapter consists of these sections:
•
•
Understanding the Bootup Process, page 3-1
Assigning Switch Information, page 3-2
•
•
•
Checking and Saving the Running Configuration, page 3-15
Modifying the Startup Configuration, page 3-17
Scheduling a Reload of the Software Image, page 3-22
Note Information in this chapter about configuring IP addresses and DHCP is specific to IP Version 4 (IPv4).
Understanding the Bootup Process
To start your switch, you need to follow the procedures in the getting started guide or the hardware installation guide for installing the switch and setting up the initial switch configuration (IP address, subnet mask, default gateway, secret and Telnet passwords, and so forth).
The normal bootup process involves the operation of the bootloader software, which performs these activities:
•
•
•
Performs low-level CPU initialization. It initializes the CPU registers, which control where physical memory is mapped, its quantity, its speed, and so forth.
Performs power-on self-test (POST) for the CPU subsystem. It tests the CPU DRAM and the portion of the flash device that makes up the flash file system.
Initializes the flash file system on the system board.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
3-1
Chapter 3 Assigning the Switch IP Address and Default Gateway
Assigning Switch Information
• Loads a default operating system software image into memory and boots the switch.
The bootloader provides access to the flash file system before the operating system is loaded. Normally, the bootloader is used only to load, uncompress, and launch the operating system. After the bootloader gives the operating system control of the CPU, the bootloader is not active until the next system reset or power-on.
The bootloader 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
“Recovering from a Lost or Forgotten Password” section on page 42-4
.
Note
.
Before you can assign switch information, make sure you have connected a PC or terminal to the console port, and configured the PC or terminal-emulation software baud rate and character format to match these of the switch console port:
•
•
Baud rate default is 9600.
Data bits default is 8.
Note If the data bits option is set to 8, set the parity option to none.
•
•
Stop bits default is 1.
Parity settings default is none.
Assigning Switch Information
You can assign IP information through the switch setup program, through a DHCP server, or manually.
Use the switch setup program if you want to be prompted for specific IP information. With this program, you can also configure a hostname and an enable secret password. It gives you the option of assigning a
Telnet password (to provide security during remote management) and configuring your switch as a standalone switch. For more information about the setup program, see the hardware installation guide.
Use a DHCP server for centralized control and automatic assignment of IP information after the server is configured.
Note If you are using DHCP, do not respond to any of the questions in the setup program until the switch receives the dynamically assigned IP address and reads the configuration file.
3-2
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 3 Assigning the Switch IP Address and Default Gateway
Assigning Switch Information
If you are an experienced user familiar with the switch configuration steps, manually configure the switch. Otherwise, use the setup program described previously.
These sections contain this configuration information:
•
Default Switch Information, page 3-3
•
•
Understanding DHCP-Based Autoconfiguration, page 3-3
Manually Assigning IP Information, page 3-14
Default Switch Information
shows the default switch information.
Table 3-1 Default Switch Information
Feature
IP address and subnet mask
Default gateway
Enable secret password
Hostname
Telnet password
Default Setting
No IP address or subnet mask are defined.
No default gateway is defined.
No password is defined.
The factory-assigned default hostname is Switch .
No password 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.
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.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
3-3
Chapter 3 Assigning the Switch IP Address and Default Gateway
Assigning Switch Information
DHCP Client Request Process
When you boot up your switch, the DHCP client is invoked and requests configuration information from a DHCP server when the configuration file is not present on the switch. If the configuration file is present and the configuration includes the ip address dhcp interface configuration command on specific routed interfaces, the DHCP client is invoked and requests the IP address information for those interfaces.
shows the sequence of messages that are exchanged between the DHCP client and the DHCP server.
Figure 3-1
Switch A
DHCP Client and Server Message Exchange
DHCPDISCOVER (broadcast)
DHCPOFFER (unicast)
DHCPREQUEST (broadcast)
DHCPACK (unicast)
DHCP server
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
If the configuration parameters sent to the client in the DHCPOFFER unicast message are invalid (a configuration error exists), the client returns a DHCPDECLINE broadcast message to the DHCP server.
The DHCP server sends the client a DHCPNAK denial broadcast message, which means that the offered configuration parameters have not been assigned, that an error has occurred during the negotiation of the parameters, or that the client has been slow in responding to the DHCPOFFER message (the DHCP server assigned the parameters to another client).
A DHCP client might receive offers from multiple DHCP or BOOTP servers and can accept any of the offers; however, the client usually accepts the first offer it receives. The offer from the DHCP server is not a guarantee that the IP address is allocated to the client; however, the server usually reserves the address until the client has had a chance to formally request the address. If the switch accepts replies from a BOOTP server and configures itself, the switch broadcasts, instead of unicasts, TFTP requests to obtain the switch configuration file.
The DHCP hostname option allows a group of switches to obtain hostnames and a standard configuration from the central management DHCP server. A client (switch) includes in its DCHPDISCOVER message an option 12 field used to request a hostname and other configuration parameters from the DHCP server.
The configuration files on all clients are identical except for their DHCP-obtained hostnames.
If a client has a default hostname (the hostname name global configuration command is not configured or the no hostname global configuration command is entered to remove the hostname), the DHCP hostname option is not included in the packet when you enter the ip address dhcp interface
3-4
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 3 Assigning the Switch IP Address and Default Gateway
Assigning Switch Information 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.)
Note To enable a DHCP auto-image update on the switch, the TFTP server where the image and configuration files are located must be configured with the correct option 67 (the configuration filename), option 66
(the DHCP server hostname) option 150 (the TFTP server address), and option 125 (description of the file) settings.
For procedures to configure the switch as a DHCP server, see the
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
.
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.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
3-5
Chapter 3 Assigning the Switch IP Address and Default Gateway
Assigning Switch Information
• The auto-install process stops if a configuration file cannot be downloaded or it the configuration file is corrupted.
Note The configuration file that is downloaded from TFTP is merged with the existing configuration in the running configuration but is not saved in the NVRAM unless you enter the write memory or copy running-configuration startup-configuration privileged EXEC command. Note that if the downloaded configuration is saved to the startup configuration, the feature is not triggered during subsequent system restarts.
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 Relay Device, page 3-8
•
Obtaining Configuration Files, page 3-9
•
Example Configuration, page 3-10
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 Cisco.com.
DHCP Server Configuration Guidelines
Follow these guidelines if you are configuring a device as a DHCP server:
You should configure the DHCP server with reserved leases that are bound to each switch by the switch hardware address.
If you want the switch to receive IP address information, you must configure the DHCP server with these lease options:
• IP address of the client (required)
•
•
Subnet mask of the client (required)
DNS server IP address (optional)
• Router IP address (default gateway address to be used by the switch) (required)
If you want the switch to receive the configuration file from a TFTP server, you must configure the
DHCP server with these lease options:
•
•
TFTP server name (required)
Boot filename (the name of the configuration file that the client needs) (recommended)
• Hostname (optional)
Depending on the settings of the DHCP server, the switch can receive IP address information, the configuration file, or both.
3-6
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 3 Assigning the Switch IP Address and Default Gateway
Assigning Switch Information
If you do not configure the DHCP server with the lease options described previously, it replies to client requests with only those parameters that are configured. If the IP address and the subnet mask are not in the reply, the switch is not configured. If the router IP address or the TFTP server name are not found, the switch might send broadcast, instead of unicast, TFTP requests. Unavailability of other lease options does not affect autoconfiguration.
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 .
Configuring the TFTP Server
Based on the DHCP server configuration, the switch attempts to download one or more configuration files from the TFTP server. If you configured the DHCP server to respond to the switch with all the options required for IP connectivity to the TFTP server, and if you configured the DHCP server with a
TFTP server name, address, and configuration filename, the switch attempts to download the specified configuration file from the specified TFTP server.
If you did not specify the configuration filename, the TFTP server, or if the configuration file could not be downloaded, the switch attempts to download a configuration file by using various combinations of filenames and TFTP server addresses. The files include the specified configuration filename (if any) and these files: network-config, cisconet.cfg, hostname .config, or hostname .cfg, where hostname is the switch’s current hostname. The TFTP server addresses used include the specified TFTP server address
(if any) and the broadcast address (255.255.255.255).
For the switch to successfully download a configuration file, the TFTP server must contain one or more configuration files in its base directory. The files can include these files:
•
•
The configuration file named in the DHCP reply (the actual switch configuration file).
The network-confg or the cisconet.cfg file (known as the default configuration files).
• The router-confg or the ciscortr.cfg file (These files contain commands common to all switches.
Normally, if the DHCP and TFTP servers are properly configured, these files are not accessed.)
If you specify the TFTP server name in the DHCP server-lease database, you must also configure the
TFTP server name-to-IP-address mapping in the DNS-server database.
If the TFTP server to be used is on a different LAN from the switch, or if it is to be accessed by the switch through the broadcast address (which occurs if the DHCP server response does not contain all the required information described previously), a relay must be configured to forward the TFTP packets to the TFTP server. For more information, see the
“Configuring the Relay Device” section on page 3-8 . The
preferred solution is to configure the DHCP server with all the required information.
Configuring the DNS
The DHCP server uses the DNS server to resolve the TFTP server name to an IP address. You must configure the TFTP server name-to-IP address map on the DNS server. The TFTP server contains the configuration files for the switch.
You can configure the IP addresses of the DNS servers in the lease database of the DHCP server from where the DHCP replies will retrieve them. You can enter up to two DNS server IP addresses in the lease database.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
3-7
Chapter 3 Assigning the Switch IP Address and Default Gateway
Assigning Switch Information
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.
For example, in
Figure 3-2 , configure the router interfaces as follows:
On interface 10.0.0.2: router(config-if)# ip helper-address 20.0.0.2
router(config-if)# ip helper-address 20.0.0.3
router(config-if)# ip helper-address 20.0.0.4
On interface 20.0.0.1
router(config-if)# ip helper-address 10.0.0.1
Note If the switch is acting as the relay device, configure the interface as a routed port. For more information, see the
“Routed Ports” section on page 10-4 and the
“Configuring Layer 3 Interfaces” section on page 10-17
.
Figure 3-2 Relay Device Used in Autoconfiguration
Switch
(DHCP client)
Cisco router
(Relay)
10.0.0.2
10.0.0.1
20.0.0.1
20.0.0.2
20.0.0.3
20.0.0.4
DHCP server TFTP server DNS server
3-8
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 3 Assigning the Switch IP Address and Default Gateway
Assigning Switch Information
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 bootup 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 bootup process.
Only the IP address is reserved for the switch and provided in the DHCP reply. The configuration filename is not provided (two-file read method).
The switch receives its IP address, subnet mask, and the TFTP server address from the DHCP server.
The switch sends a unicast message to the TFTP server to retrieve the network-confg or cisconet.cfg default configuration file. (If the network-confg file cannot be read, the switch reads the cisconet.cfg file.)
The default configuration file contains the hostnames-to-IP-address mapping for the switch. The switch fills its host table with the information in the file and obtains its hostname. If the hostname is not found in the file, the switch uses the hostname in the DHCP reply. If the hostname is not specified in the DHCP reply, the switch uses the default Switch as its hostname.
After obtaining its hostname from the default configuration file or the DHCP reply, the switch reads the configuration file that has the same name as its hostname ( hostname -confg or hostname .cfg, depending on whether network-confg or cisconet.cfg was read earlier) from the TFTP server. If the cisconet.cfg file is read, the filename of the host is truncated to eight characters.
If the switch cannot read the network-confg, cisconet.cfg, or the hostname file, it reads the router-confg file. If the switch cannot read the router-confg file, it reads the ciscortr.cfg file.
Note The switch broadcasts TFTP server requests if the TFTP server is not obtained from the DHCP replies, if all attempts to read the configuration file through unicast transmissions fail, or if the TFTP server name cannot be resolved to an IP address.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
3-9
Chapter 3 Assigning the Switch IP Address and Default Gateway
Assigning Switch Information
Example Configuration
shows a sample network for retrieving IP information by using DHCP-based autoconfiguration.
Figure 3-3 DHCP-Based Autoconfiguration Network Example
Switch 1
00e0.9f1e.2001
Switch 2
00e0.9f1e.2002
Switch 3
00e0.9f1e.2003
Switch 4
00e0.9f1e.2004
Cisco router
10.0.0.10
10.0.0.1
10.0.0.2
10.0.0.3
DHCP server DNS server TFTP server
(tftpserver)
Table 3-2 shows the configuration of the reserved leases on the DHCP server.
DHCP Server Configuration Table 3-2
Binding key (hardware address)
IP address
Subnet mask
Router address
DNS server address
TFTP server name
Switch A
00e0.9f1e.2001
10.0.0.21
255.255.255.0
10.0.0.10
10.0.0.2
tftpserver or
10.0.0.3
switcha-confg Boot filename (configuration file)
(optional)
Hostname (optional) switcha
Switch B
00e0.9f1e.2002
10.0.0.22
255.255.255.0
10.0.0.10
10.0.0.2
tftpserver or
10.0.0.3
switchb-confg switchb
Switch C
00e0.9f1e.2003
10.0.0.23
255.255.255.0
10.0.0.10
10.0.0.2
tftpserver or
10.0.0.3
switchc-confg switchc
Switch D
00e0.9f1e.2004
10.0.0.24
255.255.255.0
10.0.0.10
10.0.0.2
tftpserver or
10.0.0.3
switchd-confg switchd
DNS Server Configuration
The DNS server maps the TFTP server name tftpserver to IP address 10.0.0.3.
TFTP Server Configuration (on UNIX)
The TFTP server base directory is set to /tftpserver/work/. This directory contains the network-confg file used in the two-file read method. This file contains the hostname to be assigned to the switch based on its IP address. The base directory also contains a configuration file for each switch ( switcha-confg , switchb-confg , and so forth) as shown in this display: prompt> cd /tftpserver/work/ prompt> ls network-confg switcha-confg switchb-confg
3-10
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 3 Assigning the Switch IP Address and Default Gateway
Assigning Switch Information switchc-confg switchd-confg prompt> cat network-confg ip host switcha 10.0.0.21
ip host switchb 10.0.0.22
ip host switchc 10.0.0.23
ip host switchd 10.0.0.24
DHCP Client Configuration
No configuration file is present on Switch A through Switch D.
Configuration Explanation
In
Figure 3-3 , Switch A reads its configuration file as follows:
• It obtains its IP address 10.0.0.21 from the DHCP server.
•
•
•
If no configuration filename is given in the DHCP server reply, Switch A reads the network-confg file from the base directory of the TFTP server.
It adds the contents of the network-confg file to its host table.
•
It reads its host table by indexing its IP address 10.0.0.21 to its hostname (switcha).
It reads the configuration file that corresponds to its hostname; for example, it reads switch1-confg from the TFTP server.
Switches B through D retrieve their configuration files and IP addresses in the same way.
Configuring the DHCP Auto Configuration and Image Update Features
Using DHCP to download a new image and a new configuration to a switch requires that you configure at least two switches: One switch acts as a DHCP and TFTP server. The client switch is configured to download either a new configuration file or a new configuration file and a new image file.
Configuring DHCP Autoconfiguration (Only Configuration File)
Beginning in privileged EXEC mode, follow these steps to configure DHCP autoconfiguration of the
TFTP and DHCP settings on a new switch to download a new configuration file.
Step 1
Step 2
Command configure terminal ip dhcp poolname
Step 3
Step 4 bootfile filename network network-number mask prefix-length
Step 5
Step 6 default-router address option 150 address
Purpose
Enter global configuration mode.
Create a name for the DHCP Server address pool, and enter DHCP pool configuration mode.
Specify the name of the configuration file that is used as a boot image.
Specify the subnet network number and mask of the DHCP address pool.
Note The prefix length specifies the number of bits that comprise the address prefix. The prefix is an alternative way of specifying the network mask of the client. The prefix length must be preceded by a forward slash (/).
Specify the IP address of the default router for a DHCP client.
Specify the IP address of the TFTP server.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
3-11
Chapter 3 Assigning the Switch IP Address and Default Gateway
Assigning Switch Information
Step 7
Step 8
Step 9
Command exit tftp-server flash: filename.text
interface interface-id
Step 10
Step 11
Step 12
Step 13 no switchport ip address address mask end copy running-config startup-config
Purpose
Return to global configuration mode.
Specify the configuration file on the TFTP server.
Specify the address of the client that will receive the configuration file.
Put the interface into Layer 3 mode.
Specify the IP address and mask for the interface.
Return to privileged EXEC mode.
(Optional) Save your entries in the configuration 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 pool pool1
Switch(dhcp-config)# network 10.10.10.0 255.255.255.0
Switch(dhcp-config)# bootfile config-boot.text
Switch(dhcp-config)# default-router 10.10.10.1
Switch(dhcp-config)# option 150 10.10.10.1
Switch(dhcp-config)# exit
Switch(config)# tftp-server flash:config-boot.text
Switch(config)# interface gigabitethernet1/0/4
Switch(config-if)# no switchport
Switch(config-if)# ip address 10.10.10.1 255.255.255.0
Switch(config-if)# end
Configuring DHCP Auto-Image Update (Configuration File and Image)
Beginning in privileged EXEC mode, follow these steps to configure DHCP autoconfiguration to configure TFTP and DHCP settings on a new switch to download a new image and a new configuration file.
Note Before following the steps in this table, you must create a text file (for example, autoinstall_dhcp) that will be uploaded to the switch. In the text file, put the name of the image that you want to download (for example, c3030mipbase-mz.122-44.3.SE.tar). This image must be a tar and not a bin file.
Step 1
Step 2
Step 3
Step 4
Command configure terminal ip dhcp pool name bootfile filename network network-number mask prefix-length
Step 5 default-router address
Purpose
Enter global configuration mode.
Create a name for the DHCP server address pool and enter DHCP pool configuration mode.
Specify the name of the file that is used as a boot image.
Specify the subnet network number and mask of the DHCP address pool.
Note The prefix length specifies the number of bits that comprise the address prefix. The prefix is an alternative way of specifying the network mask of the client. The prefix length must be preceded by a forward slash (/).
Specify the IP address of the default router for a DHCP client.
3-12
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 3 Assigning the Switch IP Address and Default Gateway
Assigning Switch Information
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
Step 12
Step 13
Step 14
Step 15
Step 16
Step 17
Step 18
Command option 150 address option 125 hex copy tftp flash filename.txt
copy tftp flash imagename.tar
exit tftp-server flash: config.text
tftp-server flash: imagename.tar
Purpose
Specify the IP address of the TFTP server.
Specify the path to the text file that describes the path to the image file.
Upload the text file to the switch.
Upload the tarfile for the new image to the switch.
Return to global configuration mode.
Specify the Cisco IOS configuration file on the TFTP server.
Specify the image name on the TFTP server.
tftp-server flash: filename.txt
interface interface-id no switchport ip address address mask
Specify the text file that contains the name of the image file to download
Specify the address of the client that will receive the configuration file.
Put the interface into Layer 3 mode.
Specify 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:
Switch# config terminal
Switch(config)# ip dhcp pool pool1
Switch(dhcp-config)# network 10.10.10.0 255.255.255.0
Switch(dhcp-config)# bootfile config-boot.text
Switch(dhcp-config)# default-router 10.10.10.1
Switch(dhcp-config)# option 150 10.10.10.1
Switch(dhcp-config)# option 125 hex
0000.0009.0a05.08661.7574.6f69.6e73.7461.6c6c.5f64.686370
Switch(dhcp-config)# exit
Switch(config)# tftp-server flash:config-boot.text
Switch(config)# tftp-server flash:c3750m-ipservices-mz.122-44.3.SE.tar
Switch(config)# tftp-server flash:boot-config.text
Switch(config)# tftp-server flash: autoinstall_dhcp
Switch(config)# interface gigabitEthernet1/0/4
Switch(config-if)# no switchport
Switch(config-if)# ip address 10.10.10.1 255.255.255.0
Switch(config-if)# end
Configuring the Client
Beginning in privileged EXEC mode, follow these steps to configure a switch to download a configuration file and new image from a DHCP server:
Step 1
Step 2
Step 3
Command configure terminal boot host dhcp boot host retry timeout timeout-value
Purpose
Enter global configuration mode.
Enable autoconfiguration with a saved configuration.
(Optional) Set the amount of time the system tries to download a configuration file.
Note If you do not set a timeout the system will indefinitely try to obtain an IP address from the
DHCP server.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
3-13
Chapter 3 Assigning the Switch IP Address and Default Gateway
Assigning Switch Information
Step 4
Command banner config-save ^C warning-message ^C
Step 5
Step 6 end show boot
Purpose
(Optional) Create warning messages to be displayed when you try to save the configuration file to NVRAM.
Return to privileged EXEC mode.
Verify the configuration.
This example uses a Layer 3 SVI interface on VLAN 99 to enable DHCP-based autoconfiguration with a saved configuration:
Switch# configure terminal
Switch(conf)# boot host dhcp
Switch(conf)# boot host retry timeout 300
Switch(conf)# banner config-save ^C Caution - Saving Configuration File to NVRAM May Cause
You to Nolonger Automatically Download Configuration Files at Reboot^C
Switch(config)# vlan 99
Switch(config-vlan)# interface vlan 99
Switch(config-if)# no shutdown
Switch(config-if)# end
Switch# show boot
BOOT path-list:
Config file: flash:/config.text
Private Config file: flash:/private-config.text
Enable Break: no
Manual Boot: no
HELPER path-list:
NVRAM/Config file
buffer size: 32768
Timeout for Config
Download: 300 seconds
Config Download
via DHCP: enabled (next boot: enabled)
Switch#
Note You should only configure and enable the Layer 3 interface. Do not assign an IP address or DHCP-based autoconfiguration with a saved configuration.
Manually Assigning IP Information
Beginning in privileged EXEC mode, follow these steps to manually assign IP information to multiple switched virtual interfaces (SVIs):
Note You can also manually assign IP information to a port if you first put the port into Layer 3 mode by using the no switchport interface configuration command.
Step 1
Step 2
Command configure terminal interface vlan vlan-id
Step 3 ip address ip-address subnet-mask
Purpose
Enter global configuration mode.
Enter interface configuration mode, and enter the VLAN to which the IP information is assigned. The VLAN range is 1 to 4094.
Enter the IP address and subnet mask.
3-14
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 3 Assigning the Switch IP Address and Default Gateway
Checking and Saving the Running Configuration
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Command exit ip default-gateway ip-address end show interfaces vlan vlan-id show ip redirects copy running-config startup-config
Purpose
Return to global configuration mode.
Enter the IP address of the next-hop router interface that is directly connected to the switch where a default gateway is being configured. The default gateway receives IP packets with unresolved destination IP addresses from the switch.
Once the default gateway is configured, the switch has connectivity to the remote networks with which a host needs to communicate.
Note When your switch is configured to route with IP, it does not need to have a default gateway set.
Return to privileged EXEC mode.
Verify the configured IP address.
Verify the configured default gateway.
(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.
For information on setting the switch system name, protecting access to privileged EXEC commands,
and setting time and calendar services, see Chapter 5, “Administering the Switch” .
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 : 1833 bytes
!
version 12.2
no service pad service timestamps debug uptime service timestamps log uptime no service password-encryption
!
!
no aaa new-model ip subnet-zero
!
no file verify auto
!
spanning-tree mode pvst spanning-tree extend system-id
!
vlan internal allocation policy ascending
!
interface GigabitEthernet0/1
switchport trunk encapsulation dot1q
switchport mode trunk
speed 1000
spanning-tree portfast
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
3-15
Chapter 3 Assigning the Switch IP Address and Default Gateway
Checking and Saving the Running Configuration
!
interface GigabitEthernet0/2
switchport access vlan 2
speed 1000
storm-control unicast level 50.00
storm-control action shutdown
spanning-tree portfast
!
<output truncated>
! interface Vlan1
ip address 192.168.100.21 255.255.255.0
no ip route-cache
!
ip http server ip http secure-server
!
!
!
control-plane line con 0
exec-timeout 0 0 line vty 0 4
no login line vty 5 15
no login
!
end
To store the configuration or changes you have made to your startup configuration in flash memory, enter this privileged EXEC command:
Switch# copy running-config startup-config
Destination filename [startup-config]?
Building configuration...
This command saves the configuration settings that you made. If you fail to do this, your configuration will be lost the next time you reload the system. To display information stored in the NVRAM section of flash memory, use the show startup-config or more startup-config privileged EXEC command.
For more information about alternative locations from which to copy the configuration file, see
Appendix 44, “Working with the Cisco IOS File System, Configuration Files, and Software Images.”
Configuring the NVRAM Buffer Size
The default NVRAM buffer size is 512 KB. In some cases, the configuration file might be too large to save to NVRAM. Typically, this occurs when you have many switches in a switch stack. You can configure the size of the NVRAM buffer to support larger configuration files. The new NVRAM buffer size is synced to all current and new member switches.
Note After you configure the NVRAM buffer size, reload the switch or switch stack.
When you add a switch to a stack and the NVRAM size differs, the new switch syncs with the stack and reloads automatically.
Beginning in privileged EXEC mode, follow these steps to configure the NVRAM buffersize:
3-16
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 3 Assigning the Switch IP Address and Default Gateway
Modifying the Startup Configuration
Step 1
Step 2
Command configure terminal boot buffersize size
Step 3
Step 4 end show boot
Purpose
Enter global configuration mode.
Configure the NVRAM buffersize in KB. The valid range for size is from 4096 to 1048576.
Return to privileged EXEC mode.
Verify the configuration.
This example shows how to configure the NVRAM buffer size:
Switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# boot buffersize 524288
Switch(config)# 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 :
Auto upgrade : yes
Auto upgrade path :
NVRAM/Config file
buffer size: 524288
Timeout for Config
Download: 300 seconds
Config Download
via DHCP: enabled (next boot: enabled)
Switch#
Modifying the Startup Configuration
These sections describe how to modify the switch startup configuration:
•
•
Default Bootup Configuration, page 3-18
Automatically Downloading a Configuration File, page 3-18
•
•
Booting Up Manually, page 3-19
Booting Up a Specific Software Image, page 3-19
•
Controlling Environment Variables, page 3-20
See also
Appendix 44, “Working with the Cisco IOS File System, Configuration Files, and Software
for information about switch configuration files.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
3-17
Chapter 3 Assigning the Switch IP Address and Default Gateway
Modifying the Startup Configuration
Default Bootup Configuration
Table 3-3
Table 3-3 shows the default bootup configuration.
Default Bootup Configuration
Feature
Operating system software image
Configuration file
Default Setting
The switch attempts to automatically boot up the system using information in the
BOOT environment variable. If the variable is not set, the switch attempts to load and execute the first executable image it can by performing a recursive, depth-first search throughout the flash file system.
The Cisco IOS image is stored in a directory that has the same name as the image file
(excluding the .bin extension).
In a depth-first search of a directory, each encountered subdirectory is completely searched before continuing the search in the original directory.
Configured 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 .
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 bootup cycle.
Beginning in privileged EXEC mode, follow these steps to specify a different configuration filename:
Step 1
Step 2
Command configure terminal boot config-file flash:/ file-url
Step 3
Step 4 end show boot
Step 5 copy running-config startup-config
Purpose
Enter global configuration mode.
Specify the configuration file to load during the next bootup cycle.
For file-url , specify the path (directory) and the configuration filename.
Filenames and directory names are case sensitive.
Return to privileged EXEC mode.
Verify your entries.
The boot config-file global configuration command changes the setting of the CONFIG_FILE environment variable.
(Optional) Save your entries in the configuration file.
3-18
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 3 Assigning the Switch IP Address and Default Gateway
Modifying the Startup Configuration
To return to the default setting, use the no boot config-file global configuration command.
Booting Up 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 bootup cycle:
Step 1
Step 2
Step 3
Step 4
Command configure terminal boot manual end show boot
Purpose
Enter global configuration mode.
Enable the switch to manually boot up during the next bootup cycle.
Return to privileged EXEC mode.
Verify your entries.
The boot manual global command changes the setting of the
MANUAL_BOOT environment variable.
The next time you reboot the system, the switch is in bootloader mode, shown by the switch: prompt. To boot up the system, use the boot filesystem :/ file-url bootloader 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.
(Optional) Save your entries in the configuration file.
Step 5 copy running-config startup-config
To disable manual booting up, use the no boot manual global configuration command.
Booting Up 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 with which to boot up the switch.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
3-19
Chapter 3 Assigning the Switch IP Address and Default Gateway
Modifying the Startup Configuration
Beginning in privileged EXEC mode, follow these steps to configure the switch to boot up a specific image during the next bootup cycle:
Step 1
Step 2
Step 3
Step 4
Step 5
Command configure terminal boot system filesystem :/ file-url
Purpose
Enter global configuration mode.
Configure the switch to boot up a specific image in flash memory during the next bootup cycle.
•
•
For filesystem : , use flash: for the system board flash device.
For file-url , specify the path (directory) and the name of the bootable image.
end show boot
Filenames and directory names are case sensitive.
Return to privileged EXEC mode.
Verify your entries.
The boot system global command changes the setting of the BOOT environment variable.
During the next bootup 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 bootloader mode only through a switch console connection configured for 9600 b/s. The switch bootloader uses break-key detection to stop the automatic boot sequence and to enter bootloader mode.
Note The break-key character is different for each operating system.
On a SUN work station running UNIX, Ctrl-C is the break key.
On a PC running Hyperterminal on Windows XP or 2000, Ctrl-Break is the break key.
Cisco TAC has tabulated break keys for the most common operating systems and an alternative break key sequence for those terminal emulators that do not support the break keys. See http://www.cisco.com/warp/public/701/61.html#how-to for that list.
Follow these steps to enter bootloader mode:
Step 1
Step 2
Step 3
Connect a terminal or PC with terminal emulation software to the console port on the front of the switch.
For more information, see the switch hardware installation guide or the switch getting started guide.
Set the line speed on the emulation software to 9600 baud.
If the switch is already installed in a server chassis module bay, push the release latch on the front of the switch to the open position.
3-20
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 3 Assigning the Switch IP Address and Default Gateway
Modifying the Startup Configuration
Step 4
Step 5
Step 6
Pull the switch partially out of the module bay until the power disconnects, and then push it in again.
The switch restarts when it reseats in the server chassis. The switch performs POST after power is applied.
Push the release latch on the front of the switch to the closed position.
After the switch performs POST, the switch begins the autoboot process. Enter the break-key character during the bootup sequence, when this message appears:
Initializing Flash
This example shows the messages that appear on the console after you enter a break key:
The system has been interrupted prior to initializing the flash file system.
The following commands will initialize the flash file system, and finish loading the operating system software: flash_init load_helper boot
After the message appears, the bootloader prompt resumes.
OL-27326-01
Note You can also prompt the switch to reload the operating system by using the reload EXEC command or by using the interface provided by the Dell Remote Access Controller/Modular Chassis (DRAC/MC) management board.
See the “Connecting through the DRAC/MC” section of the Cisco Catalyst Blade Switch 3030 Getting
Started Guide for instructions on how to connect to the switch by using the DRAC/MC.
The switch bootloader software provides support for nonvolatile environment variables, which can be used to control how the bootloader, or any other software running on the system, behaves. bootloader environment variables are similar to environment variables that can be set on UNIX or DOS systems.
Environment variables that have values are stored in flash memory outside of the flash file system.
Each line in these files contains an environment variable name and an equal sign followed by the value of the variable. A variable has no value if it is not listed in this file; it has a value if it is listed in the file even if the value is a null string. A variable that is set to a null string (for example, “ ”) is a variable with a value. Many environment variables are predefined and have default values.
Environment variables store two kinds of data:
•
•
Data that controls code, which does not read the Cisco IOS configuration file. For example, the name of a bootloader helper file, which extends or patches the functionality of the bootloader 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 bootloader or by using Cisco
IOS commands. Under normal circumstances, it is not necessary to alter the setting of the environment variables.
Note For complete syntax and usage information for the bootloader commands and environment variables, see the command reference for this release.
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
3-21
Chapter 3 Assigning the Switch IP Address and Default Gateway
Scheduling a Reload of the Software Image
Table 3-4
Variable
BOOT
CONFIG_FILE
Table 3-4 describes the function of the most common environment variables.
Environment Variables
MANUAL_BOOT
Bootloader Command set BOOT filesystem :/ file-url ...
Cisco IOS Global Configuration Command boot system f ilesystem:/file-url ...
A semicolon-separated list of executable files to try to load and execute when automatically booting up the switch. If the BOOT environment variable is not set, the system attempts to load and execute the first executable image it can find by using a recursive, depth-first search through the flash file system. If the BOOT variable is set but the specified images cannot be loaded, the system attempts to boot up the first bootable file that it can find in the flash file system.
Specifies the Cisco IOS image to load during the next bootup cycle. This command changes the setting of the BOOT environment variable. set MANUAL_BOOT yes
Decides whether the switch automatically or manually boots up.
Valid values are 1, yes, 0, and no. If it is set to no or 0, the bootloader attempts to automatically boot up the system. If it is set to anything else, you must manually boot up the switch from the bootloader mode.
set CONFIG_FILE flash:/ file-url boot manual
Enables manually booting up the switch during the next bootup cycle and changes the setting of the MANUAL_BOOT environment variable.
The next time you reboot the system, the switch is in bootloader mode. To boot up the system, use the boot flash: image.
filesystem :/ file-url boot config-file flash:/ file-url bootloader command, and specify the name of the bootable
Changes the filename that Cisco IOS uses to read and write a nonvolatile copy of the system configuration.
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.
Scheduling a Reload of the Software Image
You can schedule a reload of the software image to occur on the switch at a later time (for example, late at night or during the weekend when the switch is used less), or you can synchronize a reload network-wide (for example, to perform a software upgrade on all switches in the network).
Note A scheduled reload must take place within approximately 24 days.
3-22
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 3 Assigning the Switch IP Address and Default Gateway
Scheduling a Reload of the Software Image
Configuring a Scheduled Reload
To configure your switch to reload the software image at a later time, use one of these commands in privileged EXEC mode:
• reload in [ hh : ] mm [ text ]
•
This command schedules a reload of the software to take affect in the specified minutes or hours and minutes. The reload must take place within approximately 24 days. You can specify the reason for the reload in a string up to 255 characters in length.
reload at hh : mm [ month day | day month ] [ text ]
This command schedules a reload of the software to take place at the specified time (using a 24-hour clock). If you specify the month and day, the reload is scheduled to take place at the specified time and date. If you do not specify the month and day, the reload takes place at the specified time on the current day (if the specified time is later than the current time) or on the next day (if the specified time is earlier than the current time). Specifying 00:00 schedules the reload for midnight.
Note Use the at keyword only if the switch system clock has been set (through Network Time
Protocol (NTP), the hardware calendar, or manually). The time is relative to the configured time zone on the switch. To schedule reloads across several switches to occur simultaneously, the time on each switch must be synchronized with NTP.
The reload command halts the system. If the system is not set to manually boot up, it reboots itself. Use the reload command after you save the switch configuration information to the startup configuration
( copy running-config startup-config ).
If your switch is configured for manual booting up, do not reload it from a virtual terminal. This restriction prevents the switch from entering the bootloader mode and thereby taking it from the remote user’s control.
If you modify your configuration file, the switch prompts you to save the configuration before reloading.
During the save operation, the system requests whether you want to proceed with the save if the
CONFIG_FILE environment variable points to a startup configuration file that no longer exists. If you proceed in this situation, the system enters setup mode upon reload.
This example shows how to reload the software on the switch on the current day at 7:30 p.m:
Switch# reload at 19:30
Reload scheduled for 19:30:00 UTC Wed Jun 5 1996 (in 2 hours and 25 minutes)
Proceed with reload? [confirm]
This example shows how to reload the software on the switch at a future time:
Switch# reload at 02:00 jun 20
Reload scheduled for 02:00:00 UTC Thu Jun 20 1996 (in 344 hours and 53 minutes)
Proceed with reload? [confirm]
To cancel a previously scheduled reload, use the reload cancel privileged EXEC command.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
3-23
Chapter 3 Assigning the Switch IP Address and Default Gateway
Scheduling a Reload of the Software Image
Displaying Scheduled Reload Information
To display information about a previously scheduled reload or to find out if a reload has been scheduled on the switch, use the show reload privileged EXEC command.
It displays reload information including the time the reload is scheduled to occur and the reason for the reload (if it was specified when the reload was scheduled).
3-24
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
C H A P T E R
4
Configuring Cisco IOS Configuration Engine
This chapter describes how to configure the feature on the switch.
Note For complete configuration information for the Cisco Configuration Engine, go to http://www.cisco.com/en/US/products/sw/netmgtsw/ps4617/tsd_products_support_series_home.html
For complete syntax and usage information for the commands used in this chapter, go to the Cisco IOS
Network Management Command Reference, Release 12.4
at http://www.cisco.com/en/US/docs/ios/netmgmt/command/reference/nm_book.html
This chapter consists of these sections:
•
Understanding Cisco Configuration Engine Software, page 4-1
•
•
•
Understanding Cisco IOS Agents, page 4-5
Configuring Cisco IOS Agents, page 4-6
Displaying CNS Configuration, page 4-14
Understanding Cisco Configuration Engine Software
The Cisco Configuration Engine is network management software that acts as a configuration service for automating the deployment and management of network devices and services (see
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.
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
4-1 OL-27326-01
Chapter 4 Configuring Cisco IOS Configuration Engine
Understanding Cisco Configuration Engine Software
Figure 4-1 Configuration Engine Architectural Overview
Service provider network
Configuration engine
Data service directory
Configuration server
Event service
Web-based user interface
Order entry configuration management
These sections contain this conceptual information:
•
•
•
Configuration Service, page 4-2
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.
4-2
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 4 Configuring Cisco IOS Configuration Engine
Understanding Cisco Configuration Engine Software
Event Service
The Cisco Configuration Engine uses the Event Service for receipt and generation of configuration events. The event agent is on the switch and facilitates the communication between the switch and the event gateway on the Configuration Engine.
The Event Service is a highly capable publish-and-subscribe communication method. The Event Service uses subject-based addressing to send messages to their destinations. Subject-based addressing conventions define a simple, uniform namespace for messages and their destinations.
NameSpace Mapper
The Configuration Engine includes the NameSpace Mapper (NSM) that provides a lookup service for managing logical groups of devices based on application, device or group ID, and event.
Cisco IOS devices recognize only event subject-names that match those configured in Cisco IOS software; for example, cisco.cns.config.load. You can use the namespace mapping service to designate events by using any desired naming convention. When you have populated your data store with your subject names, NSM changes your event subject-name strings to those known by Cisco IOS.
For a subscriber, when given a unique device ID and event, the namespace mapping service returns a set of events to which to subscribe. Similarly, for a publisher, when given a unique group ID, device ID, and event, the mapping service returns a set of events on which to publish.
What You Should Know About the CNS IDs and Device Hostnames
The 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-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
4-3
Chapter 4 Configuring Cisco IOS Configuration Engine
Understanding Cisco Configuration Engine Software
DeviceID
Each configured switch participating on the event bus has a unique DeviceID, which is analogous to the switch source address so that the switch can be targeted as a specific destination on the bus. All switches configured with the cns config partial global configuration command must access the event bus.
Therefore, the DeviceID, as originated on the switch, must match the DeviceID of the corresponding switch definition in the Configuration Engine.
The origin of the DeviceID is defined by the Cisco IOS hostname of the switch. However, the DeviceID variable and its usage reside within the event gateway adjacent to the switch.
The logical Cisco IOS termination point on the event bus is embedded in the event gateway, which in turn functions as a proxy on behalf of the switch. The event gateway represents the switch and its corresponding DeviceID to the event bus.
The switch declares its hostname to the event gateway immediately after the successful connection to the event gateway. The event gateway couples the DeviceID value to the Cisco IOS hostname each time this connection is established. The event gateway caches this DeviceID value for the duration of its connection to the switch.
Hostname and DeviceID
The DeviceID is fixed at the time of the connection to the event gateway and does not change even when the switch hostname is reconfigured.
When changing the switch hostname on the switch, the only way to refresh the DeviceID is to break the connection between the switch and the event gateway. Enter the no cns event global configuration command followed by the cns event global configuration command.
When the connection is re-established, the switch sends its modified hostname to the event gateway. The event gateway redefines the DeviceID to the new value.
Caution When using the Configuration Engine user interface, you must first set the DeviceID field to the hostname value that the switch acquires after –not before –you use the cns config initial global configuration command at the switch. Otherwise, subsequent cns config partial global configuration command operations malfunction.
Using Hostname, DeviceID, and ConfigID
In standalone mode, when a hostname value is set for a switch, the configuration server uses the hostname as the DeviceID when an event is sent on hostname. If the hostname has not been set, the event is sent on the cn=< value > of the device.
In server mode, the hostname is not used. In this mode, the unique DeviceID attribute is always used for sending an event on the bus. If this attribute is not set, you cannot update the switch.
These and other associated attributes (tag value pairs) are set when you run Setup on the Configuration
Engine.
Note For more information about running the setup program on the Configuration Engine, see the
Configuration Engine setup and configuration guide at http://www.cisco.com/en/US/products/sw/netmgtsw/ps4617/prod_installation_guides_list.html
4-4
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 4 Configuring Cisco IOS Configuration Engine
Understanding Cisco IOS Agents
Understanding Cisco IOS Agents
The CNS event agent feature allows the switch to publish and subscribe to events on the event bus and works with the Cisco IOS agent. The Cisco IOS agent feature supports the switch by providing these features:
•
Initial Configuration, page 4-5
•
•
Incremental (Partial) Configuration, page 4-6
Synchronized Configuration, page 4-6
Initial Configuration
When the switch first comes up, it attempts to get an IP address by broadcasting a DHCP request on the network. Assuming there is no DHCP server on the subnet, the distribution switch acts as a DHCP relay agent and forwards the request to the DHCP server. Upon receiving the request, the DHCP server assigns an IP address to the new switch and includes the TFTP server IP address, the path to the bootstrap configuration file, and the default gateway IP address in a unicast reply to the DHCP relay agent. The
DHCP relay agent forwards the reply to the switch.
The switch automatically configures the assigned IP address on interface VLAN 1 (the default) and downloads the bootstrap configuration file from the TFTP server. Upon successful download of the bootstrap configuration file, the switch loads the file in its running configuration.
The Cisco IOS agents initiate communication with the Configuration Engine by using the appropriate
ConfigID and EventID. The Configuration Engine maps the Config ID to a template and downloads the full configuration file to the switch.
by using DHCP-based autoconfiguration.
Figure 4-2
Configuration
Engine
Initial Configuration Overview
V
Distribution layer
TFTP server
WAN
DHCP server
DHCP relay agent default gateway
Access layer switches
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
4-5
Chapter 4 Configuring Cisco IOS Configuration Engine
Configuring Cisco IOS Agents
Incremental (Partial) Configuration
After the network is running, new services can be added by using the Cisco IOS agent. Incremental
(partial) configurations can be sent to the switch. The actual configuration can be sent as an event payload by way of the event gateway (push operation) or as a signal event that triggers the switch to initiate a pull operation.
The switch can check the syntax of the configuration before applying it. If the syntax is correct, the switch applies the incremental configuration and publishes an event that signals success to the configuration server. If the switch does not apply the incremental configuration, it publishes an event showing an error status. When the switch has applied the incremental configuration, it can write it to
NVRAM or wait until signaled to do so.
Synchronized Configuration
When the switch receives a configuration, it can defer application of the configuration upon receipt of a write-signal event. The write-signal event tells the switch not to save the updated configuration into its
NVRAM. The switch uses the updated configuration as its running configuration. This ensures that the switch configuration is synchronized with other network activities before saving the configuration in
NVRAM for use at the next reboot.
Configuring Cisco IOS Agents
The Cisco IOS agents embedded in the switch Cisco IOS software allow the switch to be connected and automatically configured as described in the
for instructions:
•
Enabling the CNS Event Agent, page 4-8
•
Enabling the Cisco IOS CNS Agent, page 4-9
Enabling Automated CNS Configuration
To enable automated CNS configuration of the switch, you must first complete the prerequisites in
Table 4-1 . When you complete them, power on the switch. At the
setup prompt, do nothing: The switch begins the initial configuration as described in the
“Initial Configuration” section on page 4-5 . When the
full configuration file is loaded on your switch, you need to do nothing else.
4-6
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 4 Configuring Cisco IOS Configuration Engine
Configuring Cisco IOS Agents
Table 4-1
Device
Access switch
Distribution switch
DHCP server
TFTP server
Prerequisites for Enabling Automatic Configuration
CNS Configuration Engine
Required Configuration
Factory default (no configuration file)
•
•
•
•
•
•
IP helper address
Enable DHCP relay agent
IP routing (if used as default gateway)
IP address assignment
TFTP server IP address
Path to bootstrap configuration file on the TFTP server
•
•
•
Default gateway IP address
A bootstrap configuration file that includes the CNS configuration commands that enable the switch to communicate with the Configuration Engine
The switch configured to use either the switch MAC address or the serial number (instead of the default hostname) to generate the ConfigID and EventID
• The CNS event agent configured to push the configuration file to the switch
One or more templates for each type of device, with the ConfigID of the device mapped to the template.
Note For more information about running the setup program and creating templates on the Configuration
Engine, see the Cisco Configuration Engine Installation and Setup Guide, 1.5 for Linux at http://www.cisco.com/en/US/docs/net_mgmt/configuration_engine/1.5/installation_linux/guide/setup_
1.html
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
4-7
Chapter 4 Configuring Cisco IOS Configuration Engine
Configuring Cisco IOS Agents
Enabling the CNS Event Agent
Note You must enable the CNS event agent on the switch before you enable the CNS configuration agent.
Beginning in privileged EXEC mode, follow these steps to enable the CNS event agent on the switch:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Command configure terminal cns event { hostname | ip-address } [ port-number ]
[ backup ] [ failover-time seconds ] [ keepalive seconds retry-count ] [ reconnect time ] [ source ip-address ]
Purpose
Enter global configuration mode.
Enable the event agent, and enter the gateway parameters.
•
•
For { hostname | ip-address }, enter either the hostname or the IP address of the event gateway.
(Optional) For port number , enter the port number for the event gateway. The default port number is 11011.
•
•
•
•
(Optional) Enter backup to show that this is the backup gateway. (If omitted, this is the primary gateway.)
(Optional) For 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 0.
(Optional) For reconnect time , enter the maximum time interval that the switch waits before trying to reconnect to the event gateway.
end show cns event connections show running-config copy running-config startup-config
•
Note
(Optional) For source ip-address , enter the source IP address of this device.
Though visible in the command-line help string, the encrypt and the clock-timeout time keywords are not supported.
Return to privileged EXEC mode.
Verify information about the event agent.
Verify your entries.
(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.
Switch(config)# cns event 10.180.1.27 keepalive 120 10
4-8
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 4 Configuring Cisco IOS Configuration Engine
Configuring Cisco IOS Agents
Enabling the Cisco IOS CNS Agent
After enabling the CNS event agent, start the Cisco IOS CNS agent on the switch. You can enable the
Cisco IOS agent with these commands:
• The cns config initial global configuration command enables the Cisco IOS agent and initiates an initial configuration on the switch.
• The cns config partial global configuration command enables the Cisco IOS agent and initiates a partial configuration on the switch. You can then use the Configuration Engine to remotely send incremental configurations to the switch.
Enabling an Initial Configuration
Beginning in privileged EXEC mode, follow these steps to enable the CNS configuration agent and initiate an initial configuration on the switch:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Command configure terminal cns template connect name cli config-text exit cns connect name [ retries number ] [ retry-interval seconds ] [ sleep seconds ] [ timeout seconds ]
Purpose
Enter global configuration mode.
Enter CNS template connect configuration mode, and specify the name of the CNS connect template.
Enter a command line for the CNS connect template.
Repeat this step for each command line in the template.
Repeat Steps 2 to 3 to configure another CNS connect template.
Return to global configuration mode.
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.
(Optional) For retries number , enter the number of connection retries. The range is 1 to 30. The default is 3.
(Optional) For retry-interva l seconds , enter the interval 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 0.
(Optional) For timeout seconds , enter the amount of time after which the connection attempts end. The range is 10 to 2000 seconds . The default is 120.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
4-9
Chapter 4 Configuring Cisco IOS Configuration Engine
Configuring Cisco IOS Agents
Step 7
Command discover { controller controller-type | dlci
[ subinterface subinterface-number ] | interface
[ interface-type ] | line line-type }
Step 8 template name [ ... name ]
Step 9
Step 10
Step 11
Step 12 exit hostname name ip route network-number
Purpose
Specify the interface parameters in the CNS connect profile.
• For controller controller-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 line line-type , enter the line type. •
Specify the list of CNS connect templates in the CNS connect 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.
Return to global configuration mode.
Enter the hostname for the switch.
(Optional) Establish a static route to the Configuration
Engine whose IP address is network-number .
4-10
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 4 Configuring Cisco IOS Configuration Engine
Configuring Cisco IOS Agents
Step 13
Command cns id interface num { dns-reverse | ipaddress | mac-address } [ event ] [ image ] or cns id { hardware-serial | hostname | string string | udi } [ event ] [ image ]
Purpose
(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.
•
Note
(Optional) Enter image to set the ID to be the image-id value used to identify the switch.
If both the event and image keywords are omitted, the image-id value is used to identify the switch.
• For { hardware-serial | hostname| string string | 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 string string as the unique
ID, or enter udi to set the unique device identifier
(UDI) as the unique ID.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
4-11
Chapter 4 Configuring Cisco IOS Configuration Engine
Configuring Cisco IOS Agents
Step 14
Step 15
Step 16
Step 17
Command cns config initial
[
[ port-number source
] [
{ event ip-address hostname
] [
] [ end show cns config connections show running-config
| ip-address no-persist syntax-check
] [
]
} page page ]
Purpose
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.
(Optional) Enable syntax-check to check the syntax when this parameter is entered.
Note Though visible in the command-line help string, the encrypt , status url , and inventory keywords are not supported.
Return to privileged EXEC mode.
Verify information about the configuration agent.
Verify 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).
Switch(config)# cns template connect template-dhcp
Switch(config-tmpl-conn)# cli ip address dhcp
Switch(config-tmpl-conn)# exit
Switch(config)# cns template connect ip-route
Switch(config-tmpl-conn)# cli ip route 0.0.0.0 0.0.0.0 ${next-hop}
Switch(config-tmpl-conn)# exit
Switch(config)# cns connect dhcp
Switch(config-cns-conn)# discover interface gigabitethernet
Switch(config-cns-conn)# template template-dhcp
Switch(config-cns-conn)# template ip-route
Switch(config-cns-conn)# exit
Switch(config)# hostname RemoteSwitch
RemoteSwitch(config)# cns config initial 10.1.1.1 no-persist
4-12
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 4 Configuring Cisco IOS Configuration Engine
Configuring Cisco IOS Agents
This example shows how to configure an initial configuration on a remote switch when the switch IP address is known. The Configuration Engine IP address is 172.28.129.22.
Switch(config)# cns template connect template-dhcp
Switch(config-tmpl-conn)# cli ip address dhcp
Switch(config-tmpl-conn)# exit
Switch(config)# cns template connect ip-route
Switch(config-tmpl-conn)# cli ip route 0.0.0.0 0.0.0.0 ${next-hop}
Switch(config-tmpl-conn)# exit
Switch(config)# cns connect dhcp
Switch(config-cns-conn)# discover interface gigabitethernet
Switch(config-cns-conn)# template template-dhcp
Switch(config-cns-conn)# template ip-route
Switch(config-cns-conn)# exit
Switch(config)# hostname RemoteSwitch
RemoteSwitch(config)# ip route 172.28.129.22 255.255.255.255 11.11.11.1
RemoteSwitch(config)# cns id ethernet 0 ipaddress
RemoteSwitch(config)# cns config initial 172.28.129.22 no-persist
Enabling a Partial Configuration
Beginning in privileged EXEC mode, follow these steps to enable the Cisco IOS agent and to initiate a partial configuration on the switch:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Command configure terminal cns config partial { ip-address | hostname }
[ port-number ] [ source ip-address ]
Purpose
Enter global configuration mode.
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.
•
Note
(Optional) Enter source ip-address to use for the source IP address.
Though visible in the command-line help string, the encrypt keyword is not supported.
Return to privileged EXEC mode.
Verify information about the configuration agent.
end show cns config stats or show cns config outstanding show running-config copy running-config startup-config
Verify your entries.
(Optional) Save your entries in the configuration file.
To disable the Cisco IOS agent, use the no cns config partial { ip-address | hostname } global configuration command. To cancel a partial configuration, use the cns config cancel privileged EXEC command.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
4-13
Chapter 4 Configuring Cisco IOS Configuration Engine
Displaying CNS Configuration
Displaying CNS Configuration
You can use the privileged EXEC commands in
to display CNS configuration information.
Table 4-2 Displaying CNS Configuration
Command Purpose show cns config connections Displays the status of the CNS Cisco IOS agent connections.
show cns config outstanding Displays information about incremental (partial) CNS configurations that have started but are not yet completed.
show cns config stats Displays statistics about the Cisco IOS agent.
show cns event connections show cns event stats show cns event subject
Displays the status of the CNS event agent connections.
Displays statistics about the CNS event agent.
Displays a list of event agent subjects that are subscribed to by applications.
4-14
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Administering the Switch
C H A P T E R
5
This chapter describes how to perform one-time operations to administer the switch.
This chapter consists of these sections:
•
•
•
•
•
Managing the System Time and Date, page 5-1
Configuring a System Name and Prompt, page 5-7
Managing the MAC Address Table, page 5-12
Managing the ARP Table, page 5-23
Managing the System Time and Date
You can manage the system time and date on your switch using automatic configuration, such as the
Network Time Protocol (NTP), or manual configuration methods.
Note For complete syntax and usage information for the commands used in this section, see the Cisco IOS
Configuration Fundamentals Command Reference from the Cisco.com page under Documentation >
Cisco IOS Software > 12.2 Mainline > Command References .
These sections contain this configuration information:
•
Understanding the System Clock, page 5-1
•
•
•
Understanding Network Time Protocol, page 5-2
Configuring Time and Date Manually, page 5-4
Understanding the System Clock
The heart of the time service is the system clock. This clock runs from the moment the system starts up and keeps track of the date and time.
The system clock can then be set from these sources:
• NTP
• Manual configuration
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01 5-1
Chapter 5 Administering the Switch
Managing the System Time and Date
The system clock can provide time to these services:
•
•
User show commands
Logging and debugging messages
The system clock keeps track of time internally based on Universal Time Coordinated (UTC), also known as Greenwich Mean Time (GMT). You can configure information about the local time zone and summer time (daylight saving time) so that the time appears correctly for the local time zone.
The system clock keeps track of whether the time is authoritative or not (that is, whether it has been set by a time source considered to be authoritative). If it is not authoritative, the time is available only for display purposes and is not redistributed. For configuration information, see the
Date Manually” section on page 5-4
.
Understanding Network Time Protocol
The NTP is designed to time-synchronize a network of devices. NTP runs over User Datagram Protocol
(UDP), which runs over IP. NTP is documented in RFC 1305.
An NTP network usually gets its time from an authoritative time source, such as a radio clock or an atomic clock attached to a time server. NTP then distributes this time across the network. NTP is extremely efficient; no more than one packet per minute is necessary to synchronize two devices to within a millisecond of one another.
NTP uses the concept of a stratum to describe how many NTP hops away a device is from an authoritative time source. A stratum 1 time server has a radio or atomic clock directly attached, a stratum 2 time server receives its time through NTP from a stratum 1 time server, and so on. A device running NTP automatically chooses as its time source the device with the lowest stratum number with which it communicates through NTP. This strategy effectively builds a self-organizing tree of NTP speakers.
NTP avoids synchronizing to a device whose time might not be accurate by never synchronizing to a device that is not synchronized. NTP also compares the time reported by several devices and does not synchronize to a device whose time is significantly different than the others, even if its stratum is lower.
The communications between devices running NTP (known as associations ) are usually statically configured; each device is given the IP address of all devices with which it should form associations.
Accurate timekeeping is possible by exchanging NTP messages between each pair of devices with an association. However, in a LAN environment, NTP can be configured to use IP broadcast messages instead. This alternative reduces configuration complexity because each device can simply be configured to send or receive broadcast messages. However, in that case, information flow is one-way only.
The time kept on a device is a critical resource; you should use the security features of NTP to avoid the accidental or malicious setting of an incorrect time. Two mechanisms are available: an access list-based restriction scheme and an encrypted authentication mechanism.
Cisco’s implementation of NTP does not support stratum 1 service; it is not possible to connect to a radio or atomic clock. We recommend that the time service for your network be derived from the public NTP servers available on the IP Internet.
5-2
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 5 Administering the Switch
Managing the System Time and Date
Figure 5-1 shows a typical network example using NTP. Switch A is the NTP master, with Switches B,
C, and D configured in NTP server mode, in server association with Switch A. Switch E is configured as an NTP peer to the upstream and downstream switches, Switch B and Switch F.
Figure 5-1 Typical NTP Network Configuration
Switch A
Local workgroup servers
Switch B Switch C Switch D
Switch E
Workstations
Switch F
Workstations
If the network is isolated from the Internet, Cisco’s implementation of NTP allows a device to act as if it is synchronized through NTP, when in fact it has learned the time by using other means. Other devices then synchronize to that device through NTP.
When multiple sources of time are available, NTP is always considered to be more authoritative. NTP time overrides the time set by any other method.
Several manufacturers include NTP software for their host systems, and a publicly available version for systems running UNIX and its various derivatives is also available. This software allows host systems to be time-synchronized as well.
NTP Version 4
NTP version 4 is implemented on the switch. NTPv4 is an extension of NTP version 3. NTPv4 supports both IPv4 and IPv6 and is backward-compatible with NTPv3.
NTPv4 provides these capabilities:
• Support for IPv6.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
5-3
Chapter 5 Administering the Switch
Managing the System Time and Date
• Improved security compared to NTPv3. The NTPv4 protocol provides a security framework based on public key cryptography and standard X509 certificates.
• Automatic calculation of the time-distribution hierarchy for a network. Using specific multicast groups, NTPv4 automatically configures the hierarchy of the servers to achieve the best time accuracy for the lowest bandwidth cost. This feature leverages site-local IPv6 multicast addresses.
For details about configuring NTPv4, see the Cisco IOS IPv6 Configuration Guide, Release 12.4T
.
Configuring Time and Date Manually
If no other source of time is available, you can manually configure the time and date after the system is restarted. The time remains accurate until the next system restart. We recommend that you use manual configuration only as a last resort. If you have an outside source to which the switch can synchronize, you do not need to manually set the system clock.
These sections contain this configuration information:
•
•
•
•
Setting the System Clock, page 5-4
Displaying the Time and Date Configuration, page 5-5
Configuring the Time Zone, page 5-5
Configuring Summer Time (Daylight Saving Time), page 5-6
Setting the System Clock
If you have an outside source on the network that provides time services, such as an NTP server, you do not need to manually set the system clock.
Beginning in privileged EXEC mode, follow these steps to set the system clock:
Step 1
Command clock set or clock set hh hh
:
: mm mm
:
: ss ss day month year month day year
Purpose
Manually set the system clock using one of these formats.
• For hh : mm : ss , specify the time in hours (24-hour format), minutes, and seconds. The time specified is relative to the configured time zone.
•
•
•
For day , specify the day by date in the month.
For month , specify the month by name.
For year , specify the year (no abbreviation).
This example shows how to manually set the system clock to 1:32 p.m. on July 23, 2001:
Switch# clock set 13:32:00 23 July 2001
5-4
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 5 Administering the Switch
Managing the System Time and Date
Displaying the Time and Date Configuration
To display the time and date configuration, use the show clock [ detail ] privileged EXEC command.
The system clock keeps an authoritative flag that shows whether the time is authoritative (believed to be accurate). If the system clock has been set by a timing source such as NTP, the flag is set. If the time is not authoritative, it is used only for display purposes. Until the clock is authoritative and the authoritative flag is set, the flag prevents peers from synchronizing to the clock when the peers’ time is invalid.
The symbol that precedes the show clock display has this meaning:
• *—Time is not authoritative.
•
•
(blank)—Time is authoritative.
.—Time is authoritative, but NTP is not synchronized.
Configuring the Time Zone
Beginning in privileged EXEC mode, follow these steps to manually configure the time zone:
Step 1
Step 2
Step 3
Step 4
Step 5
Command configure terminal clock timezone
[ minutes-offset ] zone hours-offset end show running-config copy running-config startup-config
Purpose
Enter global configuration mode.
Set the time zone.
The switch keeps internal time in universal time coordinated (UTC), so this command is used only for display purposes and when the time is manually set.
• For zone , enter the name of the time zone to be displayed when standard time is in effect. The default is UTC.
•
•
For hours-offset , enter the hours offset from UTC.
(Optional) For minutes-offset
Return to privileged EXEC mode.
, enter the minutes offset from UTC.
Verify your entries.
(Optional) Save your entries in the configuration file.
The minutes-offset variable in the clock timezone global configuration command is available for those cases where a local time zone is a percentage of an hour different from UTC. For example, the time zone for some sections of Atlantic Canada (AST) is UTC-3.5, where the 3 means 3 hours and .5 means 50 percent. In this case, the necessary command is clock timezone AST -3 30 .
To set the time to UTC, use the no clock timezone global configuration command.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
5-5
Chapter 5 Administering the Switch
Managing the System Time and Date
Configuring Summer Time (Daylight Saving Time)
Beginning in privileged EXEC mode, follow these steps to configure summer time (daylight saving time) in areas where it starts and ends on a particular day of the week each year:
Step 1
Step 2
Step 3
Step 4
Step 5
Command configure terminal
Purpose
Enter global configuration mode.
clock summer-time zone recurring
[ week day month hh : mm week day month hh : mm [ offset ]]
Configure summer time to start and end on the specified days every year.
Summer time is disabled by default. If you specify zone recurring
United States rules.
clock summer-time
without parameters, the summer time rules default to the
•
•
•
•
For zone , specify the name of the time zone (for example, PDT) to be displayed when summer time is in effect.
(Optional) For week , specify the week of the month (1 to 5 or last ).
(Optional) For day , specify the day of the week (Sunday, Monday...).
(Optional) For month , specify the month (January, February...).
end show running-config copy running-config startup-config
•
•
(Optional) For hh : mm , specify the time (24-hour format) in hours and minutes.
(Optional) For offset , specify the number of minutes to add during summer time. The default is 60.
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
The first part of the clock summer-time global configuration command specifies when summer time begins, and the second part specifies when it ends. All times are relative to the local time zone. The start time is relative to standard time. The end time is relative to summer time. If the starting month is after the ending month, the system assumes that you are in the southern hemisphere.
This example shows how to specify that summer time starts on the first Sunday in April at 02:00 and ends on the last Sunday in October at 02:00:
Switch(config)# clock summer-time PDT recurring 1 Sunday April 2:00 last Sunday October
2:00
5-6
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 5 Administering the Switch
Configuring a System Name and Prompt
Beginning in privileged EXEC mode, follow these steps if summer time in your area does not follow a recurring pattern (configure the exact date and time of the next summer time events):
Step 1
Step 2
Step 3
Step 4
Step 5
Command configure terminal
Purpose
Enter global configuration mode.
clock summer-time zone date [ month date year hh : mm month date year hh : mm
[ offset ]]
Configure summer time to start on the first date and end on the second date.
Summer time is disabled by default.
or
• For zone , specify the name of the time zone (for example, PDT) to be displayed when summer time is in effect.
clock summer-time zone date [ date month year hh : mm date month year hh : mm [ offset ]]
• (Optional) For week , specify the week of the month (1 to 5 or last ).
• (Optional) For day , specify the day of the week (Sunday, Monday...).
•
•
(Optional) For month , specify the month (January, February...).
(Optional) For hh : mm , specify the time (24-hour format) in hours and minutes.
end show running-config copy running-config startup-config
• (Optional) For offset , specify the number of minutes to add during summer time. The default is 60.
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
The first part of the clock summer-time global configuration command specifies when summer time begins, and the second part specifies when it ends. All times are relative to the local time zone. The start time is relative to standard time. The end time is relative to summer time. If the starting month is after the ending month, the system assumes that you are in the southern hemisphere.
To disable summer time, use the no clock summer-time global configuration command.
This example shows how to set summer time to start on October 12, 2000, at 02:00, and end on April 26,
2001, at 02:00:
Switch(config)# clock summer-time pdt date 12 October 2000 2:00 26 April 2001 2:00
Configuring a System Name and Prompt
You configure the system name on the switch to identify it. By default, the system name and prompt are
Switch .
If you have not configured a system prompt, the first 20 characters of the system name are used as the system prompt. A greater-than symbol [>] is appended. The prompt is updated whenever the system name changes.
For complete syntax and usage information for the commands used in this section, from the Cisco.com page, select Documentation > Cisco IOS Software > 12.2 Mainline > Command References and see the Cisco IOS Configuration Fundamentals Command Reference and the Cisco IOS IP Command
Reference, Volume 2 of 3: Routing Protocols.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
5-7
Chapter 5 Administering the Switch
Configuring a System Name and Prompt
These sections contain this configuration information:
•
•
•
Default System Name and Prompt Configuration, page 5-8
Configuring a System Name, page 5-8
Default System Name and Prompt Configuration
The default switch system name and prompt is Switch .
Configuring a System Name
Beginning in privileged EXEC mode, follow these steps to manually configure a system name:
Step 1
Step 2
Step 3
Step 4
Step 5
Command configure terminal hostname name
Purpose
Enter global configuration mode.
Manually configure a system name.
The default setting is switch .
The name must follow the rules for ARPANET hostnames. They must start with a letter, end with a letter or digit, and have as interior characters only letters, digits, and hyphens. Names can be up to 63 characters.
Return to privileged EXEC mode.
end show running-config Verify your entries.
copy running-config startup-confi g (Optional) Save your entries in the configuration file.
When you set the system name, it is also used as the system prompt.
To return to the default hostname, use the no hostname global configuration command.
Understanding DNS
The DNS protocol controls the Domain Name System (DNS), a distributed database with which you can map hostnames to IP addresses. When you configure DNS on your switch, you can substitute the hostname for the IP address with all IP commands, such as ping , telnet , connect , and related Telnet support operations.
IP defines a hierarchical naming scheme that allows a device to be identified by its location or domain.
Domain names are pieced together with periods (.) as the delimiting characters. For example, Cisco
Systems is a commercial organization that IP identifies by a com domain name, so its domain name is cisco.com
. A specific device in this domain, for example, the File Transfer Protocol (FTP) system is identified as ftp.cisco.com
.
To keep track of domain names, IP has defined the concept of a domain name server, which holds a cache
(or database) of names mapped to IP addresses. To map domain names to IP addresses, you must first identify the hostnames, specify the name server that is present on your network, and enable the DNS.
5-8
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 5 Administering the Switch
Configuring a System Name and Prompt
These sections contain this configuration information:
•
•
•
Default DNS Configuration, page 5-9
Displaying the DNS Configuration, page 5-10
Default DNS Configuration
shows the default DNS configuration.
Table 5-1 Default DNS Configuration
Feature
DNS enable state
DNS default domain name
DNS servers
Default Setting
Enabled.
None configured.
No name server addresses are configured.
Setting Up DNS
Beginning in privileged EXEC mode, follow these steps to set up your switch to use the DNS:
Step 1
Step 2
Step 3
Step 4
Step 5
Command configure terminal ip domain-name name ip name-server server-address1
[ server-address2 ... server-address6 ] ip domain-lookup end
Purpose
Enter global configuration mode.
Define a default domain name that the software uses to complete unqualified hostnames (names without a dotted-decimal domain name).
Do not include the initial period that separates an unqualified name from the domain name.
At bootup time, no domain name is configured; however, if the switch configuration comes from a BOOTP or Dynamic Host Configuration Protocol
(DHCP) server, then the default domain name might be set by the BOOTP or
DHCP server (if the servers were configured with this information).
Specify the address of one or more name servers to use for name and address resolution.
You can specify up to six name servers. Separate each server address with a space. The first server specified is the primary server. The switch sends DNS queries to the primary server first. If that query fails, the backup servers are queried.
(Optional) Enable DNS-based hostname-to-address translation on your switch.
This feature is enabled by default.
If your network devices require connectivity with devices in networks for which you do not control name assignment, you can dynamically assign device names that uniquely identify your devices by using the global Internet naming scheme
(DNS).
Return to privileged EXEC mode.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
5-9
Chapter 5 Administering the Switch
Creating a Banner
Step 6
Step 7
Command show running-config copy running-config startup-config
Purpose
Verify your entries.
(Optional) Save your entries in the configuration file.
If you use the switch IP address as its hostname, the IP address is used and no DNS query occurs. If you configure a hostname that contains no periods (.), a period followed by the default domain name is appended to the hostname before the DNS query is made to map the name to an IP address. The default domain name is the value set by the ip domain-name global configuration command. If there is a period (.) in the hostname, the Cisco IOS software looks up the IP address without appending any default domain name to the hostname.
To remove a domain name, use the no ip domain-name name global configuration command. To remove a name server address, use the no ip name-server server-address global configuration command. To disable DNS on the switch, use the no ip domain-lookup global configuration command.
Displaying the DNS Configuration
To display the DNS configuration information, use the show running-config privileged EXEC command.
Creating a Banner
You can configure a message-of-the-day (MOTD) and a login banner. The MOTD banner displays on all connected terminals at login and is useful for sending messages that affect all network users (such as impending system shutdowns).
The login banner also displays on all connected terminals. It appears after the MOTD banner and before the login prompts.
Note For complete syntax and usage information for the commands used in this section, see the Cisco IOS
Configuration Fundamentals Command Reference, Release 12.2
from the Cisco.com page under
Documentation > Cisco IOS Software > 12.2 Mainline > Command References .
These sections contain this configuration information:
•
•
•
Default Banner Configuration, page 5-10
Configuring a Message-of-the-Day Login Banner, page 5-11
Configuring a Login Banner, page 5-12
Default Banner Configuration
The MOTD and login banners are not configured.
5-10
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 5 Administering the Switch
Creating a Banner
Configuring a Message-of-the-Day Login Banner
You can create a single or multiline message banner that appears on the screen when someone logs in to the switch.
Beginning in privileged EXEC mode, follow these steps to configure a MOTD login banner:
Step 1
Step 2
Command configure terminal banner motd c message c
Step 3
Step 4
Step 5 end show running-config copy running-config startup-config
Purpose
Enter global configuration mode.
Specify the message of the day.
For c , enter the delimiting character of your choice, for example, a pound sign (#), and press the Return key. The delimiting character signifies the beginning and end of the banner text. Characters after the ending delimiter are discarded.
For message , enter a banner message up to 255 characters. You cannot use the delimiting character in the message.
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
To delete the MOTD banner, use the no banner motd global configuration command.
This example shows how to configure a MOTD banner for the switch by using the pound sign (#) symbol as the beginning and ending delimiter:
Switch(config)# banner motd #
This is a secure site. Only authorized users are allowed.
For access, contact technical support.
#
Switch(config)#
This example shows the banner that appears from the previous configuration:
Unix> telnet 172.2.5.4
Trying 172.2.5.4...
Connected to 172.2.5.4.
Escape character is '^]'.
This is a secure site. Only authorized users are allowed.
For access, contact technical support.
User Access Verification
Password:
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
5-11
Chapter 5 Administering the Switch
Managing the MAC Address Table
Configuring a Login Banner
You can configure a login banner to be displayed on all connected terminals. This banner appears after the MOTD banner and before the login prompt.
Beginning in privileged EXEC mode, follow these steps to configure a login banner:
Step 1
Step 2
Step 3
Step 4
Step 5
Command configure terminal banner login c message c
Purpose
Enter global configuration mode.
Specify the login message.
For c , enter the delimiting character of your choice, for example, a pound sign (#), and press the Return key. The delimiting character signifies the beginning and end of the banner text. Characters after the ending delimiter are discarded.
For message , enter a login message up to 255 characters. You cannot use the delimiting character in the message.
Return to privileged EXEC mode.
end show running-config Verify your entries.
copy running-config startup-config (Optional) Save your entries in the configuration file.
To delete the login banner, use the no banner login global configuration command.
This example shows how to configure a login banner for the switch by using the dollar sign ($) symbol as the beginning and ending delimiter:
Switch(config)# banner login $
Access for authorized users only. Please enter your username and password.
$
Switch(config)#
Managing the MAC Address Table
The MAC address table contains address information that the switch uses to forward traffic between ports. All MAC addresses in the address table are associated with one or more ports. The address table includes these types of addresses:
•
•
Dynamic address: a source MAC address that the switch learns and then ages when it is not in use.
Static address: a manually entered unicast address that does not age and that is not lost when the switch resets.
The address table lists the destination MAC address, the associated VLAN ID, and port number associated with the address and the type (static or dynamic).
Note For complete syntax and usage information for the commands used in this section, see the command reference for this release.
5-12
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 5 Administering the Switch
These sections contain this configuration information:
•
•
•
•
•
•
•
•
•
•
•
•
Building the Address Table, page 5-13
MAC Addresses and VLANs, page 5-13
Default MAC Address Table Configuration, page 5-14
Changing the Address Aging Time, page 5-14
Removing Dynamic Address Entries, page 5-15
Configuring MAC Address Change Notification Traps, page 5-15
Configuring MAC Address Move Notification Traps, page 5-17
Configuring MAC Threshold Notification Traps, page 5-18
Adding and Removing Static Address Entries, page 5-19
Configuring Unicast MAC Address Filtering, page 5-20
Disabling MAC Address Learning on a VLAN, page 5-21
Displaying Address Table Entries, page 5-23
Managing the MAC Address Table
Building the Address Table
With multiple MAC addresses supported on all ports, you can connect any port on the switch to individual workstations, repeaters, switches, routers, or other network devices. The switch provides dynamic addressing by learning the source address of packets it receives on each port and adding the address and its associated port number to the address table. As stations are added or removed from the network, the switch updates the address table, adding new dynamic addresses and aging out those that are not in use.
The aging interval is globally configured. However, the switch maintains an address table for each
VLAN, and STP can accelerate the aging interval on a per-VLAN basis.
The switch sends packets between any combination of ports, based on the destination address of the received packet. Using the MAC address table, the switch forwards the packet only to the port associated with the destination address. If the destination address is on the port that sent the packet, the packet is filtered and not forwarded. The switch always uses the store-and-forward method: complete packets are stored and checked for errors before transmission.
MAC Addresses and VLANs
All addresses are associated with a VLAN. An address can exist in more than one VLAN and have different destinations in each. Unicast addresses, for example, could be forwarded to port 1 in VLAN 1 and ports 9, 10, and 1 in VLAN 5.
Each VLAN maintains its own logical address table. A known address in one VLAN is unknown in another until it is learned or statically associated with a port in the other VLAN.
When private VLANs are configured, address learning depends on the type of MAC address:
• Dynamic MAC addresses learned in one VLAN of a private VLAN are replicated in the associated
VLANs. For example, a MAC address learned in a private-VLAN secondary VLAN is replicated in the primary VLAN.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
5-13
Chapter 5 Administering the Switch
Managing the MAC Address Table
• Static MAC addresses configured in a primary or secondary VLAN are not replicated in the associated VLANs. When you configure a static MAC address in a private VLAN primary or secondary VLAN, you should also configure the same static MAC address in all associated VLANs.
For more information about private VLANs, see
Chapter 15, “Configuring Private VLANs.”
Default MAC Address Table Configuration
Table 5-2 shows the default MAC address table configuration.
Table 5-2 Default MAC Address Table Configuration
Feature
Aging time
Dynamic addresses
Static addresses
Default Setting
300 seconds
Automatically learned
None configured
Changing the Address Aging Time
Dynamic addresses are source MAC addresses that the switch learns and then ages when they are not in use. You can change the aging time setting for all VLANs or for a specified VLAN.
Setting too short an aging time can cause addresses to be prematurely removed from the table. Then when the switch receives a packet for an unknown destination, it floods the packet to all ports in the same
VLAN as the receiving port. This unnecessary flooding can impact performance. Setting too long an aging time can cause the address table to be filled with unused addresses, which prevents new addresses from being learned. Flooding results, which can impact switch performance.
Beginning in privileged EXEC mode, follow these steps to configure the dynamic address table aging time:
Step 1
Step 2
Step 3
Step 4
Step 5
Command configure terminal mac address-table aging-time
10-1000000 ] [ vlan vlan-id ]
[ 0 | end show mac address-table aging-time copy running-config startup-config
Purpose
Enter global configuration mode.
Set the length of time that a dynamic entry remains in the MAC address table after the entry is used or updated.
The range is 10 to 1000000 seconds. The default is 300. You can also enter 0, which disables aging. Static address entries are never aged or removed from the table.
For vlan-id , valid IDs are 1 to 4094.
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
To return to the default value, use the no mac address-table aging-time global configuration command.
5-14
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 5 Administering the Switch
Managing the MAC Address Table
Removing Dynamic Address Entries
To remove all dynamic entries, use the clear mac address-table dynamic command in privileged EXEC mode. You can also remove a specific MAC address ( clear mac address-table dynamic address mac-address ), remove all addresses on the specified physical port or port channel ( clear mac address-table dynamic interface interface-id ), or remove all addresses on a specified VLAN ( clear mac address-table dynamic vlan vlan-id ).
To verify that dynamic entries have been removed, use the show mac address-table dynamic privileged
EXEC command.
Configuring MAC Address Change Notification Traps
MAC address change notification tracks users on a network by storing the MAC address change activity.
When the switch learns or removes a MAC address, an SNMP notification trap can be sent to the NMS.
If you have many users coming and going from the network, you can set a trap-interval time to bundle the notification traps to reduce network traffic. The MAC notification history table stores MAC address activity for each port for which the trap is set. MAC address change notifications are generated for dynamic and secure MAC addresses. Notifications are not generated for self addresses, multicast addresses, or other static addresses.
Beginning in privileged EXEC mode, follow these steps to configure the switch to send MAC address change notification traps to an NMS host:
Step 1
Step 2
Step 3
Step 4
Command configure terminal
Purpose
Enter global configuration mode.
snmp-server host host-addr { traps | informs } { version { 1
| 2c | 3 }} community-string notification-type
Specify the recipient of the trap message.
• For host-addr
NMS.
, specify the name or address of the
• Specify traps (the default) to send SNMP traps to the host. Specify informs to send SNMP informs to the host.
snmp-server enable traps mac-notification change mac address-table notification change
•
•
Specify the SNMP version to support. Version 1, the default, is not available with informs.
For community-string, specify the string to send with the notification operation. Though you can set this string by using the snmp-server host command, we recommend that you define this string by using the snmp-server community command before using the snmp-server host command.
• For notification-type , use the mac-notification keyword.
Enable the switch to send MAC address change notification traps to the NMS.
Enable the MAC address change notification feature.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
5-15
Chapter 5 Administering the Switch
Managing the MAC Address Table
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Command mac address-table notification change [ interval value ]
[ history-size value ]
Purpose
Enter the trap interval time and the history table size.
• (Optional) For interval value, specify the notification trap interval in seconds between each set of traps that are generated to the NMS.
The range is 0 to 2147483647 seconds; the default is 1 second.
• (Optional) For history-size value , specify the maximum number of entries in the MAC notification history table. The range is 0 to 500; the default is 1.
interface interface-id Enter interface configuration mode, and specify the
Layer 2 interface on which to enable the SNMP
MAC address notification trap.
snmp trap mac-notification change { added | removed } Enable the MAC address change notification trap on the interface.
end show mac address-table notification change interface show running-config copy running-config startup-config
•
•
Enable the trap when a MAC address is added on this interface.
Enable the trap when a MAC address is removed from this interface.
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
To disable MAC address-change notification traps, use the no snmp-server enable traps mac-notification change global configuration command. To disable the MAC address-change notification traps on a specific interface, use the no snmp trap mac-notification change { added | removed } interface configuration command. To disable the MAC address-change notification feature, use the no mac address-table notification change global configuration command.
This example shows how to specify 172.20.10.10 as the NMS, enable the switch to send MAC address notification traps to the NMS, enable the MAC address-change notification feature, set the interval time to 123 seconds, set the history-size to 100 entries, and enable traps whenever a MAC address is added on the specified port.
Switch(config)# snmp-server host 172.20.10.10 traps private mac-notification
Switch(config)# snmp-server enable traps mac-notification change
Switch(config)# mac address-table notification change
Switch(config)# mac address-table notification change interval 123
Switch(config)# mac address-table notification change history-size 100
Switch(config)# interface gigabitethernet0/2
Switch(config-if)# snmp trap mac-notification change added
You can verify your settings by entering the show mac address-table notification change interface and the show mac address-table notification change privileged EXEC commands.
5-16
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 5 Administering the Switch
Managing the MAC Address Table
Configuring MAC Address Move Notification Traps
When you configure MAC-move notification, an SNMP notification is generated and sent to the network management system whenever a MAC address moves from one port to another within the same VLAN.
Beginning in privileged EXEC mode, follow these steps to configure the switch to send MAC address-move notification traps to an NMS host:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Command configure terminal
Purpose
Enter global configuration mode.
snmp-server host host-addr { traps | informs } { version { 1
| 2c | 3 }} community-string notification-type
Specify the recipient of the trap message.
• For host-addr
NMS.
, specify the name or address of the
• Specify traps (the default) to send SNMP traps to the host. Specify informs to send SNMP informs to the host.
snmp-server enable traps mac-notification move mac address-table notification mac-move end show mac address-table notification mac-move show running-config copy running-config startup-config
•
•
Specify the SNMP version to support. Version 1, the default, is not available with informs.
For community-string, specify the string to send with the notification operation. Though you can set this string by using the snmp-server host command, we recommend that you define this string by using the snmp-server community command before using the snmp-server host command.
• For notification-type , use the mac-notification keyword.
Enable the switch to send MAC address move notification traps to the NMS.
Enable the MAC address move notification feature.
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
To disable MAC address-move notification traps, use the no snmp-server enable traps mac-notification move global configuration command. To disable the MAC address-move notification feature, use the no mac address-table notification mac-move global configuration command.
This example shows how to specify 172.20.10.10 as the NMS, enable the switch to send MAC address move notification traps to the NMS, enable the MAC address move notification feature, and enable traps when a MAC address moves from one port to another.
Switch(config)# snmp-server host 172.20.10.10 traps private mac-notification
Switch(config)# snmp-server enable traps mac-notification move
Switch(config)# mac address-table notification mac-move
You can verify your settings by entering the show mac address-table notification mac-move privileged
EXEC commands.
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01 5-17
Chapter 5 Administering the Switch
Managing the MAC Address Table
Configuring MAC Threshold Notification Traps
When you configure MAC threshold notification, an SNMP notification is generated and sent to the network management system when a MAC address table threshold limit is reached or exceeded.
Beginning in privileged EXEC mode, follow these steps to configure the switch to send MAC address table threshold notification traps to an NMS host:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Command configure terminal
Purpose
Enter global configuration mode.
snmp-server host host-addr { traps | informs } { version { 1
| 2c | 3 }} community-string notification-type
Specify the recipient of the trap message.
• For host-addr
NMS.
, specify the name or address of the
• Specify traps (the default) to send SNMP traps to the host. Specify informs to send SNMP informs to the host.
snmp-server enable traps mac-notification threshold mac address-table notification threshold mac address-table notification threshold percentage end
] | [ interval show running-config time ]
[ limit show mac address-table notification threshold copy running-config startup-config
•
•
Specify the SNMP version to support. Version 1, the default, is not available with informs.
For community-string, specify the string to send with the notification operation. Though you can set this string by using the snmp-server host command, we recommend that you define this string by using the snmp-server community command before using the snmp-server host command.
• For notification-type , use the mac-notification keyword.
Enable the switch to send MAC threshold notification traps to the NMS.
Enable the MAC address threshold notification feature.
Enter the threshold value for the MAC address threshold usage monitoring.
• (Optional) For limit percentage, specify the percentage of the MAC address table use; valid values are from 1 to 100 percent. The default is
50 percent.
• (Optional) For interval time, specify the time between notifications; valid values are greater than or equal to 120 seconds. The default is 120 seconds.
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
5-18
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 5 Administering the Switch
Managing the MAC Address Table
To disable MAC address-threshold notification traps, use the no snmp-server enable traps mac-notification threshold global configuration command. To disable the MAC address-threshold notification feature, use the no mac address-table notification threshold global configuration command.
This example shows how to specify 172.20.10.10 as the NMS, enable the MAC address threshold notification feature, set the interval time to 123 seconds, and set the limit to 78 per cent.
Switch(config)# snmp-server host 172.20.10.10 traps private mac-notification
Switch(config)# snmp-server enable traps mac-notification threshold
Switch(config)# mac address-table notification threshold
Switch(config)# mac address-table notification threshold interval 123
Switch(config)# mac address-table notification threshold limit 78
You can verify your settings by entering the show mac address-table notification threshold privileged
EXEC commands.
Adding and Removing Static Address Entries
A static address has these characteristics:
• It is manually entered in the address table and must be manually removed.
•
•
It can be a unicast or multicast address.
It does not age and is retained when the switch restarts.
You can add and remove static addresses and define the forwarding behavior for them. The forwarding behavior defines how a port that receives a packet forwards it to another port for transmission. Because all ports are associated with at least one VLAN, the switch acquires the VLAN ID for the address from the ports that you specify. You can specify a different list of destination ports for each source port.
A packet with a static address that arrives on a VLAN where it has not been statically entered is flooded to all ports and not learned.
You add a static address to the address table by specifying the destination MAC unicast address and the
VLAN from which it is received. Packets received with this destination address are forwarded to the interface specified with the interface-id option.
When you configure a static MAC address in a private-VLAN primary or secondary VLAN, you should also configure the same static MAC address in all associated VLANs. Static MAC addresses configured in a private-VLAN primary or secondary VLAN are not replicated in the associated VLAN. For more information about private VLANs, see
Chapter 15, “Configuring Private VLANs.”
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
5-19
Chapter 5 Administering the Switch
Managing the MAC Address Table
Beginning in privileged EXEC mode, follow these steps to add a static address:
Step 1
Step 2
Step 3
Step 4
Step 5
Command configure terminal mac address-table static vlan vlan-id interface mac-addr
interface-id end show mac address-table static copy running-config startup-config
Purpose
Enter global configuration mode.
Add a static address to the MAC address table.
•
•
For mac-addr , specify the destination MAC unicast address to add to the address table. Packets with this destination address received in the specified VLAN are forwarded to the specified interface.
For vlan-id , specify the VLAN for which the packet with the specified MAC address is received. Valid VLAN IDs are 1 to 4094.
• For interface-id , specify the interface to which the received packet is forwarded. Valid interfaces include physical ports or port channels.
For static multicast addresses, you can enter multiple interface IDs.
For static unicast addresses, you can enter only one interface at a time, but you can enter the command multiple times with the same
MAC address and VLAN ID.
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
To remove static entries from the address table, use the no mac address-table static mac-addr vlan vlan-id [ interface interface-id ] global configuration command.
This example shows how to add the static address c2f3.220a.12f4 to the MAC address table. When a packet is received in VLAN 4 with this MAC address as its destination address, the packet is forwarded to the specified port:
Switch(config)# mac address-table static c2f3.220a.12f4 vlan 4 interface gigabitethernet0/1
Configuring Unicast MAC Address Filtering
When unicast MAC address filtering is enabled, the switch drops packets with specific source or destination MAC addresses. This feature is disabled by default and only supports unicast static addresses.
Follow these guidelines when using this feature:
• Multicast MAC addresses, broadcast MAC addresses, and router MAC addresses are not supported.
If you specify one of these addresses when entering the mac address-table static mac-addr vlan vlan-id drop global configuration command, one of these messages appears:
% Only unicast addresses can be configured to be dropped
% CPU destined address cannot be configured as drop address
• Packets that are forwarded to the CPU are also not supported.
5-20
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 5 Administering the Switch
Managing the MAC Address Table
• If you add a unicast MAC address as a static address and configure unicast MAC address filtering, the switch either adds the MAC address as a static address or drops packets with that MAC address, depending on which command was entered last. The second command that you entered overrides the first command.
For example, if you enter the mac address-table static mac-addr vlan vlan-id interface interface-id global configuration command followed by the mac address-table static mac-addr vlan vlan-id drop command, the switch drops packets with the specified MAC address as a source or destination.
If you enter the mac address-table static mac-addr vlan vlan-id drop global configuration command followed by the mac address-table static mac-addr vlan vlan-id interface interface-id command, the switch adds the MAC address as a static address.
You enable unicast MAC address filtering and configure the switch to drop packets with a specific address by specifying the source or destination unicast MAC address and the VLAN from which it is received.
Beginning in privileged EXEC mode, follow these steps to configure the switch to drop a source or destination unicast static address:
Step 1
Step 2
Step 3
Step 4
Step 5
Command configure terminal mac address-table static vlan vlan-id drop mac-addr end show mac address-table static copy running-config startup-config
Purpose
Enter global configuration mode.
Enable unicast MAC address filtering and configure the switch to drop a packet with the specified source or destination unicast static address.
•
•
For mac-addr , specify a source or destination unicast MAC address.
Packets with this MAC address are dropped.
For vlan-id , specify the VLAN for which the packet with the specified MAC address is received. Valid VLAN IDs are 1 to 4094.
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
To disable unicast MAC address filtering, use the no mac address-table static mac-addr vlan vlan-id global configuration command.
This example shows how to enable unicast MAC address filtering and to configure the switch to drop packets that have a source or destination address of c2f3.220a.12f4. When a packet is received in
VLAN 4 with this MAC address as its source or destination, the packet is dropped:
Switch(config)# mac
a ddress-table static c2f3.220a.12f4 vlan 4 drop
Disabling MAC Address Learning on a VLAN
By default, MAC address learning is enabled on all VLANs on the switch. You can control MAC address learning on a VLAN to manage the available MAC address table space by controlling which VLANs, and therefore which ports, can learn MAC addresses. Before you disable MAC address learning, be sure that you are familiar with the network topology and the switch system configuration. Disabling MAC address learning on a VLAN could cause flooding in the network.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
5-21
Chapter 5 Administering the Switch
Managing the MAC Address Table
Follow these guidelines when disabling MAC address learning on a VLAN:
•
•
Use caution before disabling MAC address learning on a VLAN with a configured switch virtual interface (SVI). The switch then floods all IP packets in the Layer 2 domain.
You can disable MAC address learning on a single VLAN (for example, no mac address-table learning vlan 223 ) or on a range of VLANs (for example, no mac address-table learning vlan
1-10, 15 ).
•
•
•
We recommend that you disable MAC address learning only in VLANs with two ports. If you disable MAC address learning on a VLAN with more than two ports, every packet entering the switch is flooded in that VLAN domain.
You cannot disable MAC address learning on a VLAN that is used internally by the switch. If the
VLAN ID that you enter is an internal VLAN, the switch generates an error message and rejects the command. To view internal VLANs in use, enter the show vlan internal usage privileged EXEC command.
If you disable MAC address learning on a VLAN configured as a private-VLAN primary VLAN,
MAC addresses are still learned on the secondary VLAN that belongs to the private VLAN and are then replicated on the primary VLAN. If you disable MAC address learning on the secondary
VLAN, but not the primary VLAN of a private VLAN, MAC address learning occurs on the primary
VLAN and is replicated on the secondary VLAN.
You cannot disable MAC address learning on an RSPAN VLAN. The configuration is not allowed.
•
• If you disable MAC address learning on a VLAN that includes a secure port, MAC address learning is not disabled on that port. If you disable port security, the configured MAC address learning state is enabled.
Beginning in privileged EXEC mode, follow these steps to disable MAC address learning on a VLAN:
Step 1
Step 2
Step 3
Step 4
Step 5
Command configure terminal
Purpose
Enter global configuration mode.
no mac address-table learning vlan vlan-id
Disable MAC address learning on the specified VLAN or VLANs. You can specify a single VLAN, or a range of VLANs separated by a hyphen or comma.Valid VLAN IDs are 1 to 4094. It cannot be an internal VLAN.
Return to privileged EXEC mode.
end show mac address-table learning [ vlan vlan-id ]
Verify the configuration.
copy running-config startup-config (Optional) Save your entries in the configuration file.
To reenable MAC address learning on a VLAN, use the default mac address-table learning vlan vlan-id global configuration command. You can also reenable MAC address learning on a VLAN by entering the mac address-table learning vlan vlan-id global configuration command. The first
( default ) command returns to a default condition and therefore does not appear in the output from the show running-config command. The second command causes the configuration to appear in the show running-config privileged EXEC command display.
This example shows how to disable MAC address learning on VLAN 200:
Switch(config)# no mac
a ddress-table learning vlan 200
You can display the MAC address learning status of all VLANs or a specified VLAN by entering the show mac-address-table learning [ vlan vlan-id ] privileged EXEC command.
5-22
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 5 Administering the Switch
Managing the ARP Table
Displaying Address Table Entries
Table 5-3
You can display the MAC address table by using one or more of the privileged EXEC commands
Commands for Displaying the MAC Address Table
Command show ip igmp snooping groups show mac address-table address show mac address-table aging-time
Description
Displays the Layer 2 multicast entries for all VLANs or the specified VLAN.
Displays MAC address table information for the specified MAC address.
Displays the aging time in all VLANs or the specified VLAN.
show mac address-table count show mac address-table dynamic
Displays the number of addresses present in all VLANs or the specified VLAN.
Displays only dynamic MAC address table entries.
show mac address-table interface Displays the MAC address table information for the specified interface.
show mac address-table notification Displays the MAC notification parameters and history table.
show mac address-table static show mac address-table vlan
Displays only static MAC address table entries.
Displays the MAC address table information for the specified VLAN.
Managing the ARP Table
To communicate with a device (over Ethernet, for example), the software first must learn the 48-bit MAC address or the local data link address of that device. The process of learning the local data link address from an IP address is called address resolution .
The Address Resolution Protocol (ARP) associates a host IP address with the corresponding media or
MAC addresses and the VLAN ID. Using an IP address, ARP finds the associated MAC address. When a MAC address is found, the IP-MAC address association is stored in an ARP cache for rapid retrieval.
Then the IP datagram is encapsulated in a link-layer frame and sent over the network. Encapsulation of
IP datagrams and ARP requests and replies on IEEE 802 networks other than Ethernet is specified by the Subnetwork Access Protocol (SNAP). By default, standard Ethernet-style ARP encapsulation
(represented by the arpa keyword) is enabled on the IP interface.
ARP entries added manually to the table do not age and must be manually removed.
Note For CLI procedures, see the Cisco IOS Release 12.2 documentation from the Cisco.com page under
Documentation > Cisco IOS Software > 12.2 Mainline .
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
5-23
Managing the ARP Table
Chapter 5 Administering the Switch
5-24
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
C H A P T E R
6
Configuring SDM Templates
This chapter describes how to configure the Switch Database Management (SDM) templates on the switch.
Note For complete syntax and usage information for the commands used in this chapter, see the command reference for this release.
This chapter consists of these sections:
•
Understanding the SDM Templates, page 6-1
•
•
Configuring the Switch SDM Template, page 6-3
Displaying the SDM Templates, page 6-5
Understanding the SDM Templates
You can use SDM templates to configure system resources in the switch to optimize support for specific features, depending on how the switch is used in the network. You can select a template to provide maximum system usage for some functions or use the default template to balance resources. For example, you could use access template to obtain maximum ACL usage.
To allocate ternary content addressable memory (TCAM) resources for different usages, the switch SDM templates prioritize system resources to optimize support for certain features. You can select SDM templates for IP Version 4 (IPv4) to optimize these features:
• Access—The access template maximizes system resources for access control lists (ACLs) to accommodate a large number of ACLs.
•
•
Routing—The routing template maximizes system resources for unicast routing, typically required for a router or aggregator in the center of a network.
VLANs—The VLAN template disables routing and supports the maximum number of unicast MAC addresses. It would typically be selected for a Layer 2 switch.
• Default—The default template gives balance to all functions.
You can also select a dual IPv4 and IPv6 template to support a a dual-stack environment. See the
IPv4 and IPv6 SDM Templates” section on page 6-2
. You must enable a dual-stack template to configure
IPv6 host or IPv6 MLD snooping.
lists the approximate numbers of each resource supported in each IPv4 template.
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
6-1 OL-27326-01
Chapter 6 Configuring SDM Templates
Understanding the SDM Templates
Table 6-1 Approximate Number of IPv4 Features Allowed by Each Template
Resource
Unicast MAC addresses
IGMP groups and multicast routes
Unicast routes
Access
4 K
1 K
6 K
Default Routing VLAN
6 K
1 K
8 K
3 K
1 K
11 K
12 K
1 K
0
• Directly connected hosts
• Indirect routes
Policy-based routing ACEs
1
4 K
2 K
6 K
2 K
3 K
8 K
0
0
0.5 K 0 0.5 K 0
0.75K 0.75K 0.75K 0.75K
Security ACEs 2 K 1 K
1.Policy-based routing is not supported in the IP base image on the switch.
1 K 1 K
The rows in the table represent approximate hardware boundaries set when a template is selected. The template optimizes resources in the switch to support the indicated level of features for 8 routed interfaces and 1024 Layer 2 VLANs. If a section of a hardware resource is full, all processing overflow is sent to the CPU, seriously impacting switch performance.
Dual IPv4 and IPv6 SDM Templates
You can select SDM templates to support IP Version 6 (IPv6). For more information about IPv6, see
Chapter 37, “Configuring IPv6 Unicast Routing.” The switch does not support IPv6 multicast routing
and QoS. This release does support IPv6 host and IPv6 Multicast Listener Discovery (MLD) snooping.
The dual IPv4 and IPv6 template allows the switch to be used in dual stack environments (supporting both IPv4 and IPv6). Using the dual stack templates results in less TCAM capacity allowed for each resource. Do not use them if you plan to forward only IPv4 traffic.
The dual IPv4 and IPv6 default template supports Layer 2, multicast, routing, QoS, and ACLs for IPv4; and Layer 2, routing, and ACLs for IPv6 on the switch.
These SDM templates support IPv4 and IPv6 environments:
•
•
•
The dual IPv4 and IPv6 default template supports Layer 2, multicast, routing, QoS, and ACLs for
IPv4; and Layer 2, routing, and ACLs for IPv6 on the switch.
The dual IPv4 and IPv6 routing template supports Layer 2, multicast, routing (including policy-based routing), QoS, and ACLs for IPv4; and Layer 2, routing, and ACLs for IPv6 on the switch.
The dual IPv4 and IPv6 VLAN template supports basic Layer 2, multicast, QoS, and ACLs for IPv4, and basic Layer 2 and ACLs for IPv6 on the switch.
Note An IPv4 route requires only one TCAM entry. Because of the hardware compression scheme used for
IPv6, an IPv6 route can take more than one TCAM entry, reducing the number of entries forwarded in hardware. For example, for IPv6 directly connected IP addresses, the desktop template might allow less than two thousand entries.
Table 6-2 defines the approximate feature resources allocated by each new template. Template
estimations are based on a switch with 8 routed interfaces and approximately 1000 VLANs.
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
6-2 OL-27326-01
Chapter 6 Configuring SDM Templates
Configuring the Switch SDM Template
Table 6-2 Approximate Feature Resources Allowed by Dual IPv4-IPv6 Templates
Resource
Unicast MAC addresses
IPv4 IGMP groups and multicast routes
Total IPv4 unicast routes:
•
•
Directly connected IPv4 hosts
Indirect IPv4 routes
IPv6 multicast groups
Total IPv6 unicast routes:
• Directly connected IPv6 addresses
• Indirect IPv6 unicast routes
IPv4 policy-based routing ACEs
1
IPv4 or MAC QoS ACEs (total)
IPv4 or MAC security ACEs (total)
IPv6 policy-based routing ACEs
1
IPv6 QoS ACEs
1
IPv6 security ACEs
2
1.
Not supported in the IP base image that runs on the switch.
2.
The switch supports only input IPv6 router ACLs for management traffic.
2 K
1 K
0
0.75 K
1 K
0
0.5 K
0.5 K
IPv4-and-IPv6
Default
2 K
1 K
3 K
2 K
1 K
1.125 K
3 K
1.5 K
1.25 K
0.25 K
0.75 K
0.5 K
0.25 K
0.5 K
0.5 K
IPv4-and-IPv6
Routing
1.5 K
1K
2.75 K
1.5 K
1.25 K
1.125 K
2.75 K
0
0
0
0.75 K
1K
0
0.5 K
0.5 K
IPv4-and-IPv6
VLAN
8 K
0
0
1 K
0
1.125 K
0
Note Although these features are visible in the template in the CLI, the switch does not support IPv4 or IPv6 policy-based routing or IPv6 Qos ACLs.
Configuring the Switch SDM Template
These sections contain this configuration information:
•
•
•
Default SDM Template, page 6-3
SDM Template Configuration Guidelines, page 6-4
Setting the SDM Template, page 6-4
Default SDM Template
The default template is the default.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
6-3
Chapter 6 Configuring SDM Templates
Configuring the Switch SDM Template
SDM Template Configuration Guidelines
Follow these guidelines when selecting and configuring SDM templates:
• When you select and configure SDM templates, you must reload the switch for the configuration to take effect.
•
•
Use the sdm prefer vlan global configuration command only on switches intended for Layer 2 switching with no routing. When you use the VLAN template, no system resources are reserved for routing entries, and any routing is done through software. This overloads the CPU and severely degrades routing performance.
Do not use the routing template if you do not have routing enabled on your switch. The sdm prefer routing global configuration command prevents other features from using the memory allocated to unicast routing in the routing template.
•
•
•
If you try to configure IPv6 without first selecting a dual IPv4 and IPv6 template, a warning message is generated.
Using the dual stack templates results in less TCAM capacity allowed for each resource, so do not use if you plan to forward only IPv4 traffic.
Although these features are visible in the template in the CLI, the switch does not support IPv4 or
IPv6 policy-based routing or IPv6 Qos ACLs.
Setting the SDM Template
Beginning in privileged EXEC mode, follow these steps to use the SDM template to maximize feature usage:
Step 1
Step 2
Command configure terminal sdm prefer { access | default | dual-ipv4-and-ipv6 { default | routing | vlan } | routing | vlan }
Step 3 end
Purpose
Enter global configuration mode.
Specify the SDM template to be used on the switch:
The keywords have these meanings:
• access —Maximizes system resources for ACLs.
•
• default —Gives balance to all functions. dual-ipv4-and-ipv6 —Select a template that supports both IPv4 and IPv6 routing.
–
– default —Balance IPv4 and IPv6 Layer 2 and Layer 3 functionality.
routing —Provide maximum usage for IPv4 and IPv6 routing, including IPv4 policy-based routing.
– vlan —Provide maximum usage for IPv4 and IPv6 VLANs.
routing —Maximizes routing on the switch.
•
• vlan —Maximizes VLAN configuration on the switch with no routing supported in hardware.
The default template balances the use of system resources.
Return to privileged EXEC mode.
6-4
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 6 Configuring SDM Templates
Displaying the SDM Templates
Step 4
Command reload
Purpose
Reload the operating system.
After the system reboots, you can use the show sdm prefer privileged EXEC command to verify the new template configuration. If you enter the show sdm prefer command before you enter the reload privileged EXEC command, the show sdm prefer command shows the template currently in use and the template that will become active after a reload.
This is an example of an output display when you have changed the template and have not reloaded the switch:
Switch# show sdm prefer
The current template is "desktop default" template.
The selected template optimizes the resources in
the switch to support this level of features for
8 routed interfaces and 1024 VLANs.
number of unicast mac addresses: 6K
number of IPv4 IGMP groups + multicast routes: 1K
number of IPv4 unicast routes: 8K
number of directly-connected IPv4 hosts: 6K
number of indirect IPv4 routes: 2K
number of IPv4 policy based routing aces: 0
number of IPv4/MAC qos aces: 0.75K
number of IPv4/MAC security aces: 1K
On next reload, template will be “desktop vlan” template.
To return to the default template, use the no sdm prefer global configuration command.
This example shows how to configure a switch with the routing template.
Switch(config)# sdm prefer routing
Switch(config)# end
Switch# reload
Proceed with reload? [confirm]
This example shows how to configure the IPv4-and-IPv6 default template on a switch:
Switch(config)# sdm prefer dual-ipv4-and-ipv6 default
Switch(config)# exit
Switch# reload
Proceed with reload? [confirm]
Displaying the SDM Templates
Use the show sdm prefer privileged EXEC command with no parameters to display the active template.
Use the show sdm prefer [ access | default | dual-ipv4-and-ipv6 { default | vlan } | routing | vlan ] privileged EXEC command to display the resource numbers supported by the specified template.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
6-5
Chapter 6 Configuring SDM Templates
Displaying the SDM Templates
This is an example of output from the show sdm prefer command, displaying the template in use.
Switch# show sdm prefer
The current template is "desktop default" template.
The selected template optimizes the resources in
the switch to support this level of features for
8 routed interfaces and 1024 VLANs.
number of unicast mac addresses: 6K
number of IPv4 IGMP groups + multicast routes: 1K
number of IPv4 unicast routes: 8K
number of directly-connected IPv4 hosts: 6K
number of indirect IPv4 routes: 2K
number of IPv4 policy based routing aces: 0
number of IPv4/MAC qos aces: 0.75K
number of IPv4/MAC security aces: 1K
This is an example of output from the show sdm prefer routing command:
Switch# show sdm prefer routing
"desktop routing" template:
The selected template optimizes the resources in
the switch to support this level of features for
8 routed interfaces and 1024 VLANs.
number of unicast mac addresses: 3K
number of IPv4 IGMP groups + multicast routes: 1K
number of IPv4 unicast routes: 11K
number of directly-connected IPv4 hosts: 3K
number of indirect IPv4 routes: 8K
number of IPv4 policy based routing aces: 0.5K
number of IPv4/MAC qos aces: 0.75K
number of IPv4/MAC security aces: 1K
This is an example of output from the show sdm prefer dual-ipv4-and-ipv6 default command:
Switch# show sdm prefer dual-ipv4-and-ipv6 default
"desktop IPv4 and IPv6 default" template:
The selected template optimizes the resources in
the switch to support this level of features for
8 routed interfaces and 1024 VLANs.
number of unicast mac addresses: 2K
number of IPv4 IGMP groups + multicast routes: 1K
number of IPv4 unicast routes: 3K
number of directly-connected IPv4 hosts: 2K
number of indirect IPv4 routes: 1K
number of IPv6 multicast groups: 1.125k
number of directly-connected IPv6 addresses: 2K
number of indirect IPv6 unicast routes: 1K
number of IPv4 policy based routing aces: 0
number of IPv4/MAC qos aces: 0.75K
number of IPv4/MAC security aces: 1K
number of IPv6 policy based routing aces: 0
number of IPv6 qos aces: 0.5K
number of IPv6 security aces: 0.5K
6-6
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
C H A P T E R
7
Configuring Switch-Based Authentication
This chapter describes how to configure switch-based authentication on the switch. It consists of these sections:
•
Preventing Unauthorized Access to Your Switch, page 7-1
•
•
•
•
•
Protecting Access to Privileged EXEC Commands, page 7-2
Controlling Switch Access with TACACS+, page 7-10
Controlling Switch Access with RADIUS, page 7-17
Controlling Switch Access with Kerberos, page 7-38
•
•
•
Configuring the Switch for Local Authentication and Authorization, page 7-42
Configuring the Switch for Secure Shell, page 7-43
Configuring the Switch for Secure Socket Layer HTTP, page 7-48
Configuring the Switch for Secure Copy Protocol, page 7-55
Preventing Unauthorized Access to Your Switch
You can prevent unauthorized users from reconfiguring your switch and viewing configuration information. Typically, you want network administrators to have access to your switch while you restrict access to users who dial from outside the network through an asynchronous port, connect from outside the network through a serial port, or connect through a terminal or workstation from within the local network.
To prevent unauthorized access into your switch, you should configure one or more of these security features:
• At a minimum, you should configure passwords and privileges at each switch port. These passwords are locally stored on the switch. When users attempt to access the switch through a port or line, they must enter the password specified for the port or line before they can access the switch. For more information, see the
“Protecting Access to Privileged EXEC Commands” section on page 7-2 .
• For an additional layer of security, you can also configure username and password pairs, which are locally stored on the switch. These pairs are assigned to lines or ports and authenticate each user before that user can access the switch. If you have defined privilege levels, you can also assign a specific privilege level (with associated rights and privileges) to each username and password pair.
For more information, see the
“Configuring Username and Password Pairs” section on page 7-6 .
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
7-1 OL-27326-01
Chapter 7 Configuring Switch-Based Authentication
Protecting Access to Privileged EXEC Commands
• If you want to use username and password pairs, but you want to store them centrally on a server instead of locally, you can store them in a database on a security server. Multiple networking devices can then use the same database to obtain user authentication (and, if necessary, authorization) information. For more information, see the
“Controlling Switch Access with TACACS+” section on page 7-10 .
Protecting Access to Privileged EXEC Commands
A simple way of providing terminal access control in your network is to use passwords and assign privilege levels. Password protection restricts access to a network or network device. Privilege levels define what commands users can enter after they have logged into a network device.
Note For complete syntax and usage information for the commands used in this section, see the Cisco IOS
Security Command Reference, Release 12.2
from the Cisco.com page under Documentation > Cisco
IOS Software > 12.2 Mainline > Command References.
These sections contain this configuration information:
•
Default Password and Privilege Level Configuration, page 7-2
•
•
•
•
Setting or Changing a Static Enable Password, page 7-3
Protecting Enable and Enable Secret Passwords with Encryption, page 7-3
Disabling Password Recovery, page 7-5
•
•
Setting a Telnet Password for a Terminal Line, page 7-6
Configuring Username and Password Pairs, page 7-6
Configuring Multiple Privilege Levels, page 7-7
Default Password and Privilege Level Configuration
Table 7-1 shows the default password and privilege level configuration.
Table 7-1
Line password
Default Password and Privilege Levels
Feature
Enable password and privilege level
Enable secret password and privilege level
Default Setting
No password is defined. The default is level 15 (privileged EXEC level).
The password is not encrypted in the configuration file.
No password is defined. The default is level 15 (privileged EXEC level).
The password is encrypted before it is written to the configuration file.
No password is defined.
7-2
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 7 Configuring Switch-Based Authentication
Protecting Access to Privileged EXEC Commands
Setting or Changing a Static Enable Password
The enable password controls access to the privileged EXEC mode. Beginning in privileged EXEC mode, follow these steps to set or change a static enable password:
Step 1
Step 2
Step 3
Step 4
Step 5
Command configure terminal enable password password end show running-config copy running-config startup-config
Purpose
Enter global configuration mode.
Define a new password or change an existing password for access to privileged EXEC mode.
By default, no password is defined.
For password , specify a string from 1 to 25 alphanumeric characters. The string cannot start with a number, is case sensitive, and allows spaces but ignores leading spaces. It can contain the question mark (?) character if you precede the question mark with the key combination Crtl-v when you create the password; for example, to create the password abc?123, do this:
Enter abc .
Enter Crtl-v .
Enter ?123
.
When the system prompts you to enter the enable password, you need not precede the question mark with the Ctrl-v; you can simply enter abc?123 at the password prompt.
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
The enable password is not encrypted and can be read in the switch configuration file.
To remove the password, use the no enable password global configuration command.
This example shows how to change the enable password to l1u2c3k4y5 . The password is not encrypted and provides access to level 15 (traditional privileged EXEC mode access):
Switch(config)# enable password l1u2c3k4y5
Protecting Enable and Enable Secret Passwords with Encryption
To provide an additional layer of security, particularly for passwords that cross the network or that are stored on a Trivial File Transfer Protocol (TFTP) server, you can use either the enable password or enable secret global configuration commands. Both commands accomplish the same thing; that is, you can establish an encrypted password that users must enter to access privileged EXEC mode (the default) or any privilege level you specify.
We recommend that you use the enable secret command because it uses an improved encryption algorithm.
If you configure the enable secret command, it takes precedence over the enable password command; the two commands cannot be in effect simultaneously.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
7-3
Chapter 7 Configuring Switch-Based Authentication
Protecting Access to Privileged EXEC Commands
Beginning in privileged EXEC mode, follow these steps to configure encryption for enable and enable secret passwords:
Step 1
Step 2
Step 3
Step 4
Step 5
Command configure terminal enable password or
[ level level ] { service password-encryption password encryption-type encrypted-password } enable secret [ level level ] { password | encryption-type encrypted-password }
|
Purpose
Enter global configuration mode.
Define a new password or change an existing password for access to privileged EXEC mode.
or
Define a secret password, which is saved using a nonreversible encryption method.
•
•
(Optional) For level , the range is from 0 to 15. Level 1 is normal user EXEC mode privileges. The default level is
15 (privileged EXEC mode privileges).
For password , specify a string from 1 to 25 alphanumeric characters. The string cannot start with a number, is case sensitive, and allows spaces but ignores leading spaces. By default, no password is defined.
•
Note
(Optional) For encryption-type , only type 5, a Cisco proprietary encryption algorithm, is available. If you specify an encryption type, you must provide an encrypted password—an encrypted password that you copy from another switch configuration.
If you specify an encryption type and then enter a clear text password, you can not re-enter privileged
EXEC mode. You cannot recover a lost encrypted password by any method.
(Optional) Encrypt the password when the password is defined or when the configuration is written.
Encryption prevents the password from being readable in the configuration file.
Return to privileged EXEC mode.
(Optional) Save your entries in the configuration file.
end copy running-config startup-config
If both the enable and enable secret passwords are defined, users must enter the enable secret password.
Use the level keyword to define a password for a specific privilege level. After you specify the level and set a password, give the password only to users who need to have access at this level. Use the privilege level global configuration command to specify commands accessible at various levels. For more information, see the
“Configuring Multiple Privilege Levels” section on page 7-7 .
If you enable password encryption, it applies to all passwords including username passwords, authentication key passwords, the privileged command password, and console and virtual terminal line passwords.
To remove a password and level, use the no enable password [ level level ] or no enable secret [ level level ] global configuration command. To disable password encryption, use the no service password-encryption global configuration command.
7-4
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 7 Configuring Switch-Based Authentication
Protecting Access to Privileged EXEC Commands
This example shows how to configure the encrypted password $1$FaD0$Xyti5Rkls3LoyxzS8 for privilege level 2:
Switch(config)# enable secret level 2 5 $1$FaD0$Xyti5Rkls3LoyxzS8
Disabling Password Recovery
By default, any end user with physical access to the switch can recover from a lost password by interrupting the bootup process while the switch is powering on and then by entering a new password.
The password-recovery disable feature protects access to the switch password by disabling part of this functionality. When this feature is enabled, the end user can interrupt the bootup process only by agreeing to set the system back to the default configuration. With password recovery disabled, you can still interrupt the bootup process and change the password, but the configuration file (config.text) and the VLAN database file (vlan.dat) are deleted.
Note If you disable password recovery, we recommend that you keep a backup copy of the configuration file on a secure server in case the end user interrupts the bootup process and sets the system back to default values. Do not keep a backup copy of the configuration file on the switch. If the switch is operating in
VTP transparent mode, we recommend that you also keep a backup copy of the VLAN database file on a secure server. When the switch is returned to the default system configuration, you can download the saved files to the switch by using the Xmodem protocol. For more information, see the
“Recovering from a Lost or Forgotten Password” section on page 42-4 .
Beginning in privileged EXEC mode, follow these steps to disable password recovery:
Step 1
Step 2
Step 3
Step 4
Command configure terminal no service password-recovery end show version
Purpose
Enter global configuration mode.
Disable password recovery.
This setting is saved in an area of the flash memory that is accessible by the bootloader and the Cisco IOS image, but it is not part of the file system and is not accessible by any user.
Return to privileged EXEC mode.
Verify the configuration by checking the last few lines of the command output.
To re-enable password recovery, use the service password-recovery global configuration command.
Note Disabling password recovery will not work if you have set the switch to boot up manually by using the boot manual global configuration command. This command produces the bootloader prompt ( switch: ) after the switch is power cycled.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
7-5
Chapter 7 Configuring Switch-Based Authentication
Protecting Access to Privileged EXEC Commands
Setting a Telnet Password for a Terminal Line
When you power-up your switch for the first time, an automatic setup program runs to assign IP information and to create a default configuration for continued use. The setup program also prompts you to configure your switch for Telnet access through a password. If you did not configure this password during the setup program, you can configure it now through the command-line interface (CLI).
Beginning in privileged EXEC mode, follow these steps to configure your switch for Telnet access:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Command enable password password configure terminal line vty 0 15 password password end show running-config copy running-config startup-config
Purpose
Attach a PC or workstation with emulation software to the switch console port.
The default data characteristics of the console port are 9600, 8, 1, no parity. You might need to press the Return key several times to see the command-line prompt.
Enter privileged EXEC mode.
Enter global configuration mode.
Configure the number of Telnet sessions (lines), and enter line configuration mode.
There are 16 possible sessions on a command-capable switch. The 0 and 15 mean that you are configuring all 16 possible Telnet sessions.
Enter a Telnet password for the line or lines.
For password , specify a string from 1 to 25 alphanumeric characters. The string cannot start with a number, is case sensitive, and allows spaces but ignores leading spaces. By default, no password is defined.
Return to privileged EXEC mode.
Verify your entries.
The password is listed under the command line vty 0 15 .
(Optional) Save your entries in the configuration file.
To remove the password, use the no password global configuration command.
This example shows how to set the Telnet password to let45me67in89 :
Switch(config)# line vty 10
Switch(config-line)# password let45me67in89
Configuring Username and Password Pairs
You can configure username and password pairs, which are locally stored on the switch. These pairs are assigned to lines or ports and authenticate each user before that user can access the switch. If you have defined privilege levels, you can also assign a specific privilege level (with associated rights and privileges) to each username and password pair.
7-6
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 7 Configuring Switch-Based Authentication
Protecting Access to Privileged EXEC Commands
Beginning in privileged EXEC mode, follow these steps to establish a username-based authentication system that requests a login username and a password:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Command configure terminal username name [ privilege level ]
{ password encryption-type password } line console 0 or line vty 0 15 login local
Purpose
Enter global configuration mode.
Enter the username, privilege level, and password for each user.
•
•
For name , specify the user ID as one word. Spaces and quotation marks are not allowed.
(Optional) For level , specify the privilege level the user has after gaining access. The range is 0 to 15. Level 15 gives privileged EXEC mode access. Level 1 gives user EXEC mode access.
•
•
For encryption-type , enter 0 to specify that an unencrypted password will follow. Enter 7 to specify that a hidden password will follow.
For password , specify the password the user must enter to gain access to the switch. The password must be from 1 to 25 characters, can contain embedded spaces, and must be the last option specified in the username command.
Enter line configuration mode, and configure the console port (line 0) or the VTY lines (line 0 to 15).
end show running-config copy running-config startup-config
Enable local password checking at login time. Authentication is based on the username specified in Step 2.
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
To disable username authentication for a specific user, use the no username name global configuration command. To disable password checking and allow connections without a password, use the no login line configuration command.
Configuring Multiple Privilege Levels
By default, the Cisco IOS software has two modes of password security: user EXEC and privileged
EXEC. You can configure up to 16 hierarchical levels of commands for each mode. By configuring multiple passwords, you can allow different sets of users to have access to specified commands.
For example, if you want many users to have access to the clear line command, you can assign it level 2 security and distribute the level 2 password fairly widely. But if you want more restricted access to the configure command, you can assign it level 3 security and distribute that password to a more restricted group of users.
These sections contain this configuration information:
•
•
•
Setting the Privilege Level for a Command, page 7-8
Changing the Default Privilege Level for Lines, page 7-9
Logging into and Exiting a Privilege Level, page 7-9
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
7-7
Chapter 7 Configuring Switch-Based Authentication
Protecting Access to Privileged EXEC Commands
Setting the Privilege Level for a Command
Beginning in privileged EXEC mode, follow these steps to set the privilege level for a command mode:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Command configure terminal privilege mode level level command
Purpose
Enter global configuration mode.
Set the privilege level for a command.
• For mode , enter configure for global configuration mode, exec for
EXEC mode, interface for interface configuration mode, or line for line configuration mode.
• For level , the range is from 0 to 15. Level 1 is for normal user EXEC mode privileges. Level 15 is the level of access permitted by the enable password.
• For command , specify the command to which you want to restrict access.
enable password level level password Specify the enable password for the privilege level.
end show running-config or show privilege copy running-config startup-config
•
•
For level , the range is from 0 to 15. Level 1 is for normal user EXEC mode privileges.
For password , specify a string from 1 to 25 alphanumeric characters.
The string cannot start with a number, is case sensitive, and allows spaces but ignores leading spaces. By default, no password is defined.
Return to privileged EXEC mode.
Verify your entries.
The first command shows the password and access level configuration.
The second command shows the privilege level configuration.
(Optional) Save your entries in the configuration file.
When you set a command to a privilege level, all commands whose syntax is a subset of that command are also set to that level. For example, if you set the show ip traffic command to level 15, the show commands and show ip commands are automatically set to privilege level 15 unless you set them individually to different levels.
To return to the default privilege for a given command, use the no privilege mode level level command global configuration command.
This example shows how to set the configure command to privilege level 14 and define SecretPswd14 as the password users must enter to use level 14 commands:
Switch(config)# privilege exec level 14 configure
Switch(config)# enable password level 14 SecretPswd14
7-8
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 7 Configuring Switch-Based Authentication
Protecting Access to Privileged EXEC Commands
Changing the Default Privilege Level for Lines
Beginning in privileged EXEC mode, follow these steps to change the default privilege level for a line:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Command configure terminal line vty line privilege level level end show running-config or show privilege copy running-config startup-config
Purpose
Enter global configuration mode.
Select the virtual terminal line on which to restrict access.
Change the default privilege level for the line.
For level , the range is from 0 to 15. Level 1 is for normal user EXEC mode privileges. Level 15 is the level of access permitted by the enable password.
Return to privileged EXEC mode.
Verify your entries.
The first command shows the password and access level configuration.
The second command shows the privilege level configuration.
(Optional) Save your entries in the configuration file.
Users can override the privilege level you set using the privilege level line configuration command by logging in to the line and enabling a different privilege level. They can lower the privilege level by using the disable command. If users know the password to a higher privilege level, they can use that password to enable the higher privilege level. You might specify a high level or privilege level for your console line to restrict line usage.
To return to the default line privilege level, use the no privilege level line configuration command.
Logging into and Exiting a Privilege Level
Beginning in privileged EXEC mode, follow these steps to log in to a specified privilege level and to exit to a specified privilege level:
Step 1
Command enable level
Step 2 disable level
Purpose
Log in to a specified privilege level.
For level , the range is 0 to 15.
Exit to a specified privilege level.
For level , the range is 0 to 15.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
7-9
Chapter 7 Configuring Switch-Based Authentication
Controlling Switch Access with TACACS+
Controlling Switch Access with TACACS+
This section describes how to enable and configure Terminal Access Controller Access Control System
Plus (TACACS+), which provides detailed accounting information and flexible administrative control over authentication and authorization processes. TACACS+ is facilitated through authentication, authorization, accounting (AAA) and can be enabled only through AAA commands.
Beginning with Cisco IOS Release 12.2(58)SE, the switch supports TACACS+ for IPv6. For information about configuring this feature, see the “Implementing ADSL for IPv6” chapter in the Cisco IOS XE IPv6
Configuration Guide, Release 2 .
Note For complete syntax and usage information for the commands used in this section, see the Cisco IOS
Security Command Reference, Release 12.2
.
These sections contain this configuration information:
•
•
•
•
Understanding TACACS+, page 7-10
Configuring TACACS+, page 7-12
Displaying the TACACS+ Configuration, page 7-17
Understanding TACACS+
TACACS+ is a security application that provides centralized validation of users attempting to gain access to your switch. TACACS+ services are maintained in a database on a TACACS+ daemon typically running on a UNIX or Windows NT workstation. You should have access to and should configure a
TACACS+ server before the configuring TACACS+ features on your switch.
TACACS+ provides for separate and modular authentication, authorization, and accounting facilities.
TACACS+ allows for a single access control server (the TACACS+ daemon) to provide each service—authentication, authorization, and accounting—independently. Each service can be tied into its own database to take advantage of other services available on that server or on the network, depending on the capabilities of the daemon.
The goal of TACACS+ is to provide a method for managing multiple network access points from a single management service. Your switch can be a network access server along with other Cisco routers and access servers. A network access server provides connections to a single user, to a network or subnetwork, and to interconnected networks as shown in
7-10
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 7 Configuring Switch-Based Authentication
Figure 7-1
UNIX workstation
(TACACS+ server 1)
Typical TACACS+ Network Configuration
Catalyst 6500 series switch
Controlling Switch Access with TACACS+
171.20.10.7
UNIX workstation
(TACACS+ server 2)
171.20.10.8
Blade servers
Configure the Blade switches with the
TACACS+ server addresses.
Set an authentication key
(also configure the same key on the TACACS+ servers).
Enable AAA.
Create a login authentication method list.
Apply the list to the terminal lines.
Create an authorization and accounting method list as required.
Blade servers
TACACS+, administered through the AAA security services, can provide these services:
• Authentication—Provides complete control of authentication through login and password dialog, challenge and response, and messaging support.
The authentication facility can conduct a dialog with the user (for example, after a username and password are provided, to challenge a user with several questions, such as home address, mother’s maiden name, service type, and social security number). The TACACS+ authentication service can also send messages to user screens. For example, a message could notify users that their passwords must be changed because of the company’s password aging policy.
•
•
Authorization—Provides fine-grained control over user capabilities for the duration of the user’s session, including but not limited to setting autocommands, access control, session duration, or protocol support. You can also enforce restrictions on what commands a user can execute with the
TACACS+ authorization feature.
Accounting—Collects and sends information used for billing, auditing, and reporting to the
TACACS+ daemon. Network managers can use the accounting facility to track user activity for a security audit or to provide information for user billing. Accounting records include user identities, start and stop times, executed commands (such as PPP), number of packets, and number of bytes.
The TACACS+ protocol provides authentication between the switch and the TACACS+ daemon, and it ensures confidentiality because all protocol exchanges between the switch and the TACACS+ daemon are encrypted.
You need a system running the TACACS+ daemon software to use TACACS+ on your switch.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
7-11
Chapter 7 Configuring Switch-Based Authentication
Controlling Switch Access with TACACS+
TACACS+ Operation
When a user attempts a simple ASCII login by authenticating to a switch using TACACS+, this process occurs:
1.
When the connection is established, the switch contacts the TACACS+ daemon to obtain a username prompt to show to the user. The user enters a username, and the switch then contacts the TACACS+ daemon to obtain a password prompt. The switch displays the password prompt to the user, the user enters a password, and the password is then sent to the TACACS+ daemon.
2.
TACACS+ allows a dialog between the daemon and the user until the daemon receives enough information to authenticate the user. The daemon prompts for a username and password combination, but can include other items, such as the user’s mother’s maiden name.
The switch eventually receives one of these responses from the TACACS+ daemon:
•
•
ACCEPT—The user is authenticated and service can begin. If the switch is configured to require authorization, authorization begins at this time.
REJECT—The user is not authenticated. The user can be denied access or is prompted to retry the login sequence, depending on the TACACS+ daemon.
3.
•
•
•
ERROR—An error occurred at some time during authentication with the daemon or in the network connection between the daemon and the switch. If an ERROR response is received, the switch typically tries to use an alternative method for authenticating the user.
CONTINUE—The user is prompted for additional authentication information.
After authentication, the user undergoes an additional authorization phase if authorization has been enabled on the switch. Users must first successfully complete TACACS+ authentication before proceeding to TACACS+ authorization.
If TACACS+ authorization is required, the TACACS+ daemon is again contacted, and it returns an
ACCEPT or REJECT authorization response. If an ACCEPT response is returned, the response contains data in the form of attributes that direct the EXEC or NETWORK session for that user and the services that the user can access:
• Telnet, Secure Shell (SSH), rlogin, or privileged EXEC services
Connection parameters, including the host or client IP address, access list, and user timeouts
Configuring TACACS+
This section describes how to configure your switch to support TACACS+. At a minimum, you must identify the host or hosts maintaining the TACACS+ daemon and define the method lists for TACACS+ authentication. You can optionally define method lists for TACACS+ authorization and accounting. A method list defines the sequence and methods to be used to authenticate, to authorize, or to keep accounts on a user. You can use method lists to designate one or more security protocols to be used, thus ensuring a backup system if the initial method fails. The software uses the first method listed to authenticate, to authorize, or to keep accounts on users; if that method does not respond, the software selects the next method in the list. This process continues until there is successful communication with a listed method or the method list is exhausted.
7-12
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 7 Configuring Switch-Based Authentication
Controlling Switch Access with TACACS+
These sections contain this configuration information:
•
•
•
Default TACACS+ Configuration, page 7-13
Identifying the TACACS+ Server Host and Setting the Authentication Key, page 7-13
•
Configuring TACACS+ Login Authentication, page 7-14
Configuring TACACS+ Authorization for Privileged EXEC Access and Network Services, page 7-16
•
Starting TACACS+ Accounting, page 7-17
Default TACACS+ Configuration
TACACS+ and AAA are disabled by default.
To prevent a lapse in security, you cannot configure TACACS+ through a network management application. When enabled, TACACS+ can authenticate users accessing the switch through the CLI.
Note Although TACACS+ configuration is performed through the CLI, the TACACS+ server authenticates
HTTP connections that have been configured with a privilege level of 15.
Identifying the TACACS+ Server Host and Setting the Authentication Key
You can configure the switch to use a single server or AAA server groups to group existing server hosts for authentication. You can group servers to select a subset of the configured server hosts and use them for a particular service. The server group is used with a global server-host list and contains the list of IP addresses of the selected server hosts.
Beginning in privileged EXEC mode, follow these steps to identify the IP host or host maintaining
TACACS+ server and optionally set the encryption key:
Step 1
Step 2
Command configure terminal tacacs-server host hostname [ port integer ] [ timeout integer ] [ key string ]
Step 3 aaa new-model
Purpose
Enter global configuration mode.
Identify the IP host or hosts maintaining a TACACS+ server. Enter this command multiple times to create a list of preferred hosts. The software searches for hosts in the order in which you specify them.
• For hostname , specify the name or IP address of the host.
• (Optional) For port integer , specify a server port number. The default is port 49. The range is 1 to 65535.
•
•
(Optional) For timeout integer , specify a time in seconds the switch waits for a response from the daemon before it times out and declares an error. The default is 5 seconds. The range is 1 to 1000 seconds.
(Optional) For key string , specify the encryption key for encrypting and decrypting all traffic between the switch and the TACACS+ daemon. You must configure the same key on the TACACS+ daemon for encryption to be successful.
Enable AAA.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
7-13
Chapter 7 Configuring Switch-Based Authentication
Controlling Switch Access with TACACS+
Step 4
Step 5
Step 6
Step 7
Step 8
Command aaa group server tacacs+ group-name (Optional) Define the AAA server-group with a group name.
This command puts the switch in a server group subconfiguration mode.
server ip-address
Purpose
(Optional) Associate a particular TACACS+ server with the defined server group. Repeat this step for each TACACS+ server in the AAA server group.
end show tacacs copy running-config startup-config
Each server in the group must be previously defined in Step 2.
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
To remove the specified TACACS+ server name or address, use the no tacacs-server host hostname global configuration command. To remove a server group from the configuration list, use the no aaa group server tacacs+ group-name global configuration command. To remove the IP address of a
TACACS+ server, use the no server ip-address server group subconfiguration command.
Configuring TACACS+ Login Authentication
To configure AAA authentication, you define a named list of authentication methods and then apply that list to various ports. The method list defines the types of authentication to be performed and the sequence in which they are performed; it must be applied to a specific port before any of the defined authentication methods are performed. The only exception is the default method list (which, by coincidence, is named default ). The default method list is automatically applied to all ports except those that have a named method list explicitly defined. A defined method list overrides the default method list.
A method list describes the sequence and authentication methods to be queried to authenticate a user.
You can designate one or more security protocols to be used for authentication, thus ensuring a backup system for authentication in case the initial method fails. The software uses the first method listed to authenticate users; if that method fails to respond, the software selects the next authentication method in the method list. This process continues until there is successful communication with a listed authentication method or until all defined methods are exhausted. If authentication fails at any point in this cycle—meaning that the security server or local username database responds by denying the user access—the authentication process stops, and no other authentication methods are attempted.
Beginning in privileged EXEC mode, follow these steps to configure login authentication:
Step 1
Step 2
Command configure terminal aaa new-model
Purpose
Enter global configuration mode.
Enable AAA.
7-14
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 7 Configuring Switch-Based Authentication
Controlling Switch Access with TACACS+
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Command aaa authentication login { default | list-name } method1 [ method2...
] line
[
[ console list-name }
| tty | vty ending-line-number login authentication
]
{
] line-number default | end show running-config copy running-config startup-config
Purpose
Create a login authentication method list.
• To create a default list that is used when a named list is not specified in the login authentication command, use the default keyword followed by the methods that are to be used in default situations. The default method list is automatically applied to all ports.
•
•
For list-name , specify a character string to name the list you are creating.
For method1...
, specify the actual method the authentication algorithm tries. The additional methods of authentication are used only if the previous method returns an error, not if it fails.
Select one of these methods:
• enable —Use the enable password for authentication. Before you can use this authentication method, you must define an enable password by using the enable password global configuration command.
•
•
•
• group tacacs+ —Uses TACACS+ authentication. Before you can use this authentication method, you must configure the TACACS+ server.
For more information, see the
“Identifying the TACACS+ Server Host and Setting the Authentication Key” section on page 7-13 .
line —Use the line password for authentication. Before you can use this authentication method, you must define a line password. Use the password password line configuration command.
local —Use the local username database for authentication. You must enter username information in the database. Use the username password global configuration command.
local-case —Use a case-sensitive local username database for authentication. You must enter username information in the database by using the username name password global configuration command.
• none —Do not use any authentication for login.
Enter line configuration mode, and configure the lines to which you want to apply the authentication list.
Apply the authentication list to a line or set of lines.
•
•
If you specify default , use the default list created with the aaa authentication login command.
For list-name , specify the list created with the aaa authentication login command.
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
To disable AAA, use the no aaa new-model global configuration command. To disable AAA authentication, use the no aaa authentication login { default | list-name } method1 [ method2...
] global configuration command. To either disable TACACS+ authentication for logins or to return to the default value, use the no login authentication { default | list-name } line configuration command.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
7-15
Chapter 7 Configuring Switch-Based Authentication
Controlling Switch Access with TACACS+
Note To secure the switch for HTTP access by using AAA methods, you must configure the switch with the ip http authentication aaa global configuration command. Configuring AAA authentication does not secure the switch for HTTP access by using AAA methods.
For more information about the ip http authentication command, see the Cisco IOS Security Command
Reference, Release 12.2
from the Cisco.com page under Documentation > Cisco IOS Software > 12.2
Mainline > Command References .
Configuring TACACS+ Authorization for Privileged EXEC Access and Network Services
AAA authorization limits the services available to a user. When AAA authorization is enabled, the switch uses information retrieved from the user’s profile, which is located either in the local user database or on the security server, to configure the user’s session. The user is granted access to a requested service only if the information in the user profile allows it.
You can use the aaa authorization global configuration command with the tacacs+ keyword to set parameters that restrict a user’s network access to privileged EXEC mode.
The aaa authorization exec tacacs+ local command sets these authorization parameters:
•
•
Use TACACS+ for privileged EXEC access authorization if authentication was performed by using
TACACS+.
Use the local database if authentication was not performed by using TACACS+.
Note Authorization is bypassed for authenticated users who log in through the CLI even if authorization has been configured.
Beginning in privileged EXEC mode, follow these steps to specify TACACS+ authorization for privileged EXEC access and network services:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Command configure terminal aaa authorization network tacacs+ aaa authorization exec tacacs+ end show running-config copy running-config startup-config
Purpose
Enter global configuration mode.
Configure the switch for user TACACS+ authorization for all network-related service requests.
Configure the switch for user TACACS+ authorization if the user has privileged EXEC access.
The exec keyword might return user profile information (such as autocommand information).
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
To disable authorization, use the no aaa authorization { network | exec } method1 global configuration command.
7-16
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 7 Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
Starting TACACS+ Accounting
The AAA accounting feature tracks the services that users are accessing and the amount of network resources that they are consuming. When AAA accounting is enabled, the switch reports user activity to the TACACS+ security server in the form of accounting records. Each accounting record contains accounting attribute-value (AV) pairs and is stored on the security server. This data can then be analyzed for network management, client billing, or auditing.
Beginning in privileged EXEC mode, follow these steps to enable TACACS+ accounting for each Cisco
IOS privilege level and for network services:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Command Purpose configure terminal aaa accounting network start-stop tacacs+
Enter global configuration mode.
Enable TACACS+ accounting for all network-related service requests. aaa accounting exec start-stop tacacs+ Enable TACACS+ accounting to send a start-record accounting notice at the beginning of a privileged EXEC process and a stop-record at the end.
end Return to privileged EXEC mode.
show running-config copy running-config startup-config
Verify your entries.
(Optional) Save your entries in the configuration file.
To disable accounting, use the no aaa accounting { network | exec } { start-stop } method1...
global configuration command.
Establishing a Session with a Router if the AAA Server is Unreachable
The aaa accounting system guarantee-first command guarantees system accounting as the first record, which is the default condition. In some situations, users might be prevented from starting a session on the console or terminal connection until after the system reloads, which can take more than 3 minutes.
To establish a console or Telnet session with the router if the AAA server is unreachable when the router reloads, use the no aaa accounting system guarantee-first command.
Displaying the TACACS+ Configuration
To display TACACS+ server statistics, use the show tacacs privileged EXEC command.
Controlling Switch Access with RADIUS
This section describes how to enable and configure the RADIUS, which provides detailed accounting information and flexible administrative control over authentication and authorization processes.
RADIUS is facilitated through AAA and can be enabled only through AAA commands.
Beginning with Cisco IOS Release 12.2(58)SE, the switch supports RADIUS for IPv6. For information about configuring this feature, see the “Implementing ADSL for IPv6” chapter in the Cisco IOS XE IPv6
Configuration Guide, Release 2 .
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
7-17
Chapter 7 Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
Note For complete syntax and usage information for the commands used in this section, see the Cisco IOS
Security Command Reference, Release 12.2
.
These sections contain this configuration information:
•
•
•
•
•
Understanding RADIUS, page 7-18
RADIUS Change of Authorization, page 7-20
Displaying the RADIUS Configuration, page 7-38
Understanding RADIUS
RADIUS is a distributed client/server system that secures networks against unauthorized access.
RADIUS clients run on supported Cisco routers and switches. Clients send authentication requests to a central RADIUS server, which contains all user authentication and network service access information.
The RADIUS host is normally a multiuser system running RADIUS server software from Cisco (Cisco
Secure Access Control Server Version 3.0), Livingston, Merit, Microsoft, or another software provider.
For more information, see the RADIUS server documentation.
Use RADIUS in these network environments that require access security:
•
•
•
Networks with multiple-vendor access servers, each supporting RADIUS. For example, access servers from several vendors use a single RADIUS server-based security database. In an IP-based network with multiple vendors’ access servers, dial-in users are authenticated through a RADIUS server that has been customized to work with the Kerberos security system.
Turnkey network security environments in which applications support the RADIUS protocol, such as in an access environment that uses a smart card access control system. In one case, RADIUS has been used with Enigma’s security cards to validates users and to grant access to network resources.
Networks already using RADIUS. You can add a Cisco switch containing a RADIUS client to the network. This might be the first step when you make a transition to a TACACS+ server. See
.
•
•
Network in which the user must only access a single service. Using RADIUS, you can control user access to a single host, to a single utility such as Telnet, or to the network through a protocol such as IEEE 802.1x. For more information about this protocol, see
Chapter 8, “Configuring IEEE 802.1x
Networks that require resource accounting. You can use RADIUS accounting independently of
RADIUS authentication or authorization. The RADIUS accounting functions allow data to be sent at the start and end of services, showing the amount of resources (such as time, packets, bytes, and so forth) used during the session. An Internet service provider might use a freeware-based version of RADIUS access control and accounting software to meet special security and billing needs.
7-18
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 7 Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
RADIUS is not suitable in these network security situations:
•
•
Multiprotocol access environments. RADIUS does not support AppleTalk Remote Access (ARA),
NetBIOS Frame Control Protocol (NBFCP), NetWare Asynchronous Services Interface (NASI), or
X.25 PAD connections.
Switch-to-switch or router-to-router situations. RADIUS does not provide two-way authentication.
RADIUS can be used to authenticate from one device to a non-Cisco device if the non-Cisco device requires authentication.
• Networks using a variety of services. RADIUS generally binds a user to one service model.
Figure 7-2
Remote
PC
Transitioning from RADIUS to TACACS+ Services
R1 RADIUS server
R2
T1
RADIUS server
TACACS+ server
T2 TACACS+ server
Workstation
RADIUS Operation
When a user attempts to log in and authenticate to a switch that is access controlled by a RADIUS server, these events occur:
1.
2.
3.
The user is prompted to enter a username and password.
The username and encrypted password are sent over the network to the RADIUS server.
The user receives one of these responses from the RADIUS server: a.
ACCEPT—The user is authenticated.
b.
REJECT—The user is either not authenticated and is prompted to re-enter the username and password, or access is denied.
c.
CHALLENGE—A challenge requires additional data from the user.
d.
CHALLENGE PASSWORD—A response requests the user to select a new password.
The ACCEPT or REJECT response is bundled with additional data that is used for privileged EXEC or network authorization. Users must first successfully complete RADIUS authentication before proceeding to RADIUS authorization, if it is enabled. The additional data included with the ACCEPT or
REJECT packets includes these items:
•
•
Telnet, SSH, rlogin, or privileged EXEC services
Connection parameters, including the host or client IP address, access list, and user timeouts
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
7-19
Chapter 7 Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
RADIUS Change of Authorization
This section provides an overview of the RADIUS interface including available primitives and how they are used during a Change of Authorization (CoA).
•
•
•
•
•
Change-of-Authorization Requests, page 7-20
CoA Request Response Code, page 7-22
CoA Request Commands, page 7-23
Session Reauthentication, page 7-23
Overview
A standard RADIUS interface is typically used in a pulled model where the request originates from a network attached device and the response come from the queried servers. Catalyst switches support the
RADIUS Change of Authorization (CoA) extensions defined in RFC 5176 that are typically used in a pushed model and allow for the dynamic reconfiguring of sessions from external authentication, authorization, and accounting (AAA) or policy servers.
Beginning with Cisco IOS Release 12.2(52)SE, the switch supports these per-session CoA requests:
•
•
•
•
Session reauthentication
Session termination
Session termination with port shutdown
Session termination with port bounce
This feature is integrated with the Cisco Secure Access Control Server (ACS) 5.1. For information about
ACS, refer to: http://www.cisco.com/en/US/products/sw/secursw/ps2086/index.html
.
The RADIUS interface is enabled by default on Catalyst switches. However, some basic configuration is required for the following attributes:
•
•
Security and Password—refer to the “Preventing Unauthorized Access to Your Switch” section in the Configuring Switch-Based Authentication chapter in the Catalyst 3750 Switch Software
Configuration Guide, 12.2(50)SE .
Accounting—refer to the “Starting RADIUS Accounting” section in the Configuring Switch-Based
Authentication chapter in the Catalyst 3750 Switch Software Configuration Guide, 12.2(50)SE .
Change-of-Authorization Requests
Change of Authorization (CoA) requests, as described in RFC 5176, are used in a push model to allow for session identification, host reauthentication, and session termination. The model is comprised of one request (CoA-Request) and two possible response codes:
•
•
CoA acknowledgement (ACK) [CoA-ACK]
CoA non-acknowledgement (NAK) [CoA-NAK]
The request is initiated from a CoA client (typically a RADIUS or policy server) and directed to the switch that acts as a listener.
This section includes these topics:
•
7-20
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 7 Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
•
•
RFC 5176 Compliance
The Disconnect Request message, which is also referred to as Packet of Disconnect (POD), is supported by the switch for session termination.
shows the IETF attributes are supported for this feature.
Table 7-2 Supported IETF Attributes
Attribute Number
24
31
44
80
101
Attribute Name
State
Calling-Station-ID
Acct-Session-ID
Message-Authenticator
Error-Cause
shows the possible values for the Error-Cause attribute.
Table 7-3 Error-Cause Values
Value
502
503
504
505
506
507
508
405
406
407
501
201
202
401
402
403
404
Explanation
Residual Session Context Removed
Invalid EAP Packet (Ignored)
Unsupported Attribute
Missing Attribute
NAS Identification Mismatch
Invalid Request
Unsupported Service
Unsupported Extension
Invalid Attribute Value
Administratively Prohibited
Request Not Routable (Proxy)
Session Context Not Found
Session Context Not Removable
Other Proxy Processing Error
Resources Unavailable
Request Initiated
Multiple Session Selection Unsupported
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
7-21
Chapter 7 Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
Preconditions
To use the CoA interface, a session must already exist on the switch. CoA can be used to identify a session and enforce a disconnect request. The update affects only the specified session.
CoA Request Response Code
The CoA Request response code can be used to convey a command to the switch. The supported commands are listed in
Session Identification
For disconnect and CoA requests targeted at a particular session, the switch locates the session based on one or more of the following attributes:
•
•
Calling-Station-Id (IETF attribute #31 which contains the host MAC address)
Audit-Session-Id (Cisco VSA)
• Acct-Session-Id (IETF attribute #44)
Unless all session identification attributes included in the CoA message match the session, the switch returns a Disconnect-NAK or CoA-NAK with the “Invalid Attribute Value” error-code attribute.
For disconnect and CoA requests targeted to a particular session, any one of the following session identifiers can be used:
• Calling-Station-ID (IETF attribute #31, which should contain the MAC address)
•
•
Audit-Session-ID (Cisco vendor-specific attribute)
Accounting-Session-ID (IETF attribute #44).
If more than one session identification attribute is included in the message, all the attributes must match the session or the switch returns a Disconnect- negative acknowledgement (NAK) or CoA-NAK with the error code “Invalid Attribute Value.”
The packet format for a CoA Request code as defined in RFC 5176 consists of the fields: Code,
Identifier, Length, Authenticator, and Attributes in Type:Length:Value (TLV) format.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Code | Identifier | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| Authenticator |
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Attributes ...
+-+-+-+-+-+-+-+-+-+-+-+-+-
The attributes field is used to carry Cisco VSAs.
CoA ACK Response Code
If the authorization state is changed successfully, a positive acknowledgement (ACK) is sent. The attributes returned within CoA ACK will vary based on the CoA Request and are discussed in individual
CoA Commands.
7-22
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 7 Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
CoA NAK Response Code
A negative acknowledgement (NAK) indicates a failure to change the authorization state and can include attributes that indicate the reason for the failure. Use show commands to verify a successful CoA.
CoA Request Commands
This section includes:
•
•
•
•
CoA Request: Disable Host Port
•
Beginning with Cisco IOS Release 12.2(52)SE, the switch supports the commands shown in
.
Table 7-4 CoA Commands Supported on the Switch
Command
1
Cisco VSA
Reauthenticate host Cisco:Avpair=“subscriber:command=reauthenticate”
Terminate session
Bounce host port
Disable host port
This is a standard disconnect request that does not require a VSA.
Cisco:Avpair=“subscriber:command=bounce-host-port”
Cisco:Avpair=“subscriber:command=disable-host-port”
1.
All CoA commands must include the session identifier between the switch and the CoA client.
Session Reauthentication
The AAA server typically generates a session reauthentication request when a host with an unknown identity or posture joins the network and is associated with a restricted access authorization profile (such as a guest VLAN). A reauthentication request allows the host to be placed in the appropriate authorization group when its credentials are known.
To initiate session authentication, the AAA server sends a standard CoA-Request message which contains a Cisco vendor-specific attribute (VSA) in this form:
Cisco:Avpair=“subscriber:command=reauthenticate” and one or more session identification attributes.
The current session state determines the switch response to the message. If the session is currently authenticated by IEEE 802.1x, the switch responds by sending an Extensible Authentication Protocol over Lan (EAPoL)-RequestId message to the server.
If the session is currently authenticated by MAC authentication bypass (MAB), the switch sends an access-request to the server, passing the same identity attributes used for the initial successful authentication.
If session authentication is in progress when the switch receives the command, the switch terminates the process, and restarts the authentication sequence, starting with the method configured to be attempted first.
If the session is not yet authorized, or is authorized via guest VLAN, or critical VLAN, or similar policies, the reauthentication message restarts the access control methods, beginning with the method configured to be attempted first. The current authorization of the session is maintained until the reauthentication leads to a different authorization result.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
7-23
Chapter 7 Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
Session Termination
There are three types of CoA requests that can trigger session termination. A CoA Disconnect-Request terminates the session, without disabling the host port. This command causes re-initialization of the authenticator state machine for the specified host, but does not restrict that host’s access to the network.
To restrict a host’s access to the network, use a CoA Request with the
Cisco:Avpair="subscriber:command=disable-host-port" VSA. This command is useful when a host is known to be causing problems on the network, and you need to immediately block network access for the host. When you want to restore network access on the port, re-enable it using a non-RADIUS mechanism.
When a device with no supplicant, such as a printer, needs to acquire a new IP address (for example, after a VLAN change), terminate the session on the host port with port-bounce (temporarily disable and then re-enable the port).
CoA Disconnect-Request
This command is a standard Disconnect-Request. Because this command is session-oriented, it must be accompanied by one or more of the session identification attributes described in the
Identification” section on page 7-22 . If the session cannot be located, the switch returns a
Disconnect-NAK message with the “Session Context Not Found” error-code attribute. If the session is located, the switch terminates the session. After the session has been completely removed, the switch returns a Disconnect-ACK.
If the switch fails-over to a standby switch before returning a Disconnect-ACK to the client, the process is repeated on the new active switch when the request is re-sent from the client. If the session is not found following re-sending, a Disconnect-ACK is sent with the “Session Context Not Found” error-code attribute.
CoA Request: Disable Host Port
This command is carried in a standard CoA-Request message that has this new VSA:
Cisco:Avpair="subscriber:command=disable-host-port"
Because this command is session-oriented, it must be accompanied by one or more of the session identification attributes described in the
“Session Identification” section on page 7-22 . If the session
cannot be located, the switch returns a CoA-NAK message with the “Session Context Not Found” error-code attribute. If the session is located, the switch disables the hosting port and returns a CoA-ACK message.
If the switch fails before returning a CoA-ACK to the client, the process is repeated on the new active switch when the request is re-sent from the client. If the switch fails after returning a CoA-ACK message to the client but before the operation has completed, the operation is restarted on the new active switch.
Note A Disconnect-Request failure following command re-sending could be the result of either a successful session termination before change-over (if the Disconnect-ACK was not sent) or a session termination by other means (for example, a link failure) that occurred after the original command was issued and before the standby switch became active.
7-24
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 7 Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
CoA Request: Bounce-Port
This command is carried in a standard CoA-Request message that contains the following new VSA:
Cisco:Avpair="subscriber:command=bounce-host-port"
Because this command is session-oriented, it must be accompanied by one or more of the session identification attributes described in the
“Session Identification” section on page 7-22
. If the session cannot be located, the switch returns a CoA-NAK message with the “Session Context Not Found” error-code attribute. If the session is located, the switch disables the hosting port for a period of 10 seconds, re-enables it (port-bounce), and returns a CoA-ACK.
If the switch fails before returning a CoA-ACK to the client, the process is repeated on the new active switch when the request is re-sent from the client. If the switch fails after returning a CoA-ACK message to the client but before the operation has completed, the operation is re-started on the new active switch.
Configuring RADIUS
This section describes how to configure your switch to support RADIUS. At a minimum, you must identify the host or hosts that run the RADIUS server software and define the method lists for RADIUS authentication. You can optionally define method lists for RADIUS authorization and accounting.
A method list defines the sequence and methods to be used to authenticate, to authorize, or to keep accounts on a user. You can use method lists to designate one or more security protocols to be used (such as TACACS+ or local username lookup), thus ensuring a backup system if the initial method fails. The software uses the first method listed to authenticate, to authorize, or to keep accounts on users; if that method does not respond, the software selects the next method in the list. This process continues until there is successful communication with a listed method or the method list is exhausted.
You should have access to and should configure a RADIUS server before configuring RADIUS features on your switch.
•
•
•
These sections contain this configuration information:
•
Default RADIUS Configuration, page 7-26
•
•
Identifying the RADIUS Server Host, page 7-26
(required)
Configuring RADIUS Login Authentication, page 7-28 (required)
•
•
Defining AAA Server Groups, page 7-30 (optional)
Configuring RADIUS Authorization for User Privileged Access and Network Services, page 7-32
(optional)
Starting RADIUS Accounting, page 7-33 (optional)
Configuring Settings for All RADIUS Servers, page 7-34
(optional)
•
•
•
•
Configuring the Switch to Use Vendor-Specific RADIUS Attributes, page 7-34 (optional)
Configuring the Switch for Vendor-Proprietary RADIUS Server Communication, page 7-36
(optional)
Configuring CoA on the Switch, page 7-37
Monitoring and Troubleshooting CoA Functionality, page 7-38
Configuring RADIUS Server Load Balancing, page 7-38 (optional)
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
7-25
Chapter 7 Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
Default RADIUS Configuration
RADIUS and AAA are disabled by default.
To prevent a lapse in security, you cannot configure RADIUS through a network management application. When enabled, RADIUS can authenticate users accessing the switch through the CLI.
Identifying the RADIUS Server Host
Switch-to-RADIUS-server communication involves several components:
•
•
•
•
•
•
Hostname or IP address
Authentication destination port
Accounting destination port
Key string
Timeout period
Retransmission value
You identify RADIUS security servers by their hostname or IP address, hostname and specific UDP port numbers, or their IP address and specific UDP port numbers. The combination of the IP address and the
UDP port number creates a unique identifier, allowing different ports to be individually defined as
RADIUS hosts providing a specific AAA service. This unique identifier enables RADIUS requests to be sent to multiple UDP ports on a server at the same IP address.
If two different host entries on the same RADIUS server are configured for the same service—for example, accounting—the second host entry configured acts as a fail-over backup to the first one. Using this example, if the first host entry fails to provide accounting services, the
%RADIUS-4-RADIUS_DEAD message appears, and then the switch tries the second host entry configured on the same device for accounting services. (The RADIUS host entries are tried in the order that they are configured.)
A RADIUS server and the switch use a shared secret text string to encrypt passwords and exchange responses. To configure RADIUS to use the AAA security commands, you must specify the host running the RADIUS server daemon and a secret text (key) string that it shares with the switch.
The timeout, retransmission, and encryption key values can be configured globally for all RADIUS servers, on a per-server basis, or in some combination of global and per-server settings. To apply these settings globally to all RADIUS servers communicating with the switch, use the three unique global configuration commands: radius-server timeout , radius-server retransmit , and radius-server key . To apply these values on a specific RADIUS server, use the radius-server host global configuration command.
Note If you configure both global and per-server functions (timeout, retransmission, and key commands) on the switch, the per-server timer, retransmission, and key value commands override global timer, retransmission, and key value commands. For information on configuring these settings on all RADIUS servers, see the
“Configuring Settings for All RADIUS Servers” section on page 7-34 .
You can configure the switch to use AAA server groups to group existing server hosts for authentication.
For more information, see the
“Defining AAA Server Groups” section on page 7-30 .
7-26
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 7 Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
Beginning in privileged EXEC mode, follow these steps to configure per-server RADIUS server communication. This procedure is required.
Step 1
Step 2
Command configure terminal radius-server host { hostname | ip-address } [ auth-port port-number ]
[ acct-port port-number ] [ timeout seconds ] [ retransmit retries ] [ key string ]
Step 3
Step 4
Step 5 end show running-config copy running-config startup-config
Purpose
Enter global configuration mode.
Specify the IP address or hostname of the remote RADIUS server host.
•
•
•
•
(Optional) For auth-port port-number , specify the UDP destination port for authentication requests.
(Optional) For acct-port port-number , specify the UDP destination port for accounting requests.
(Optional) For timeout seconds , specify the time interval that the switch waits for the RADIUS server to reply before resending. The range is 1 to 1000. This setting overrides the radius-server timeout global configuration command setting. If no timeout is set with the radius-server host command, the setting of the radius-server timeout command is used.
(Optional) For retransmit retries , specify the number of times a
RADIUS request is resent to a server if that server is not responding or responding slowly. The range is 1 to 1000. If no retransmit value is set with the radius-server host command, the setting of the radius-server retransmit global configuration command is used.
•
Note
(Optional) For key string , specify the authentication and encryption key used between the switch and the RADIUS daemon running on the
RADIUS server.
The key is a text string that must match the encryption key used on the RADIUS server. Always configure the key as the last item in the radius-server host command. Leading spaces are ignored, but spaces within and at the end of the key are used. If you use spaces in your key, do not enclose the key in quotation marks unless the quotation marks are part of the key.
To configure the switch to recognize more than one host entry associated with a single IP address, enter this command as many times as necessary, making sure that each UDP port number is different. The switch software searches for hosts in the order in which you specify them. Set the timeout, retransmit, and encryption key values to use with the specific RADIUS host.
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
To remove the specified RADIUS server, use the no radius-server host hostname | ip-address global configuration command.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
7-27
Chapter 7 Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
This example shows how to configure one RADIUS server to be used for authentication and another to be used for accounting:
Switch(config)# radius-server host 172.29.36.49 auth-port 6403 key rad1
Switch(config)# radius-server host 172.20.36.50 acct-port 6403 key rad2
This example shows how to configure host1 as the RADIUS server and to use the default ports for both authentication and accounting:
Switch(config)# radius-server host host1
Note You also need to configure some settings on the RADIUS server. These settings include the IP address of the switch and the key string to be shared by both the server and the switch. For more information, see the RADIUS server documentation.
Configuring RADIUS Login Authentication
To configure AAA authentication, you define a named list of authentication methods and then apply that list to various ports. The method list defines the types of authentication to be performed and the sequence in which they are performed; it must be applied to a specific port before any of the defined authentication methods are performed. The only exception is the default method list (which, by coincidence, is named default ). The default method list is automatically applied to all ports except those that have a named method list explicitly defined.
A method list describes the sequence and authentication methods to be queried to authenticate a user.
You can designate one or more security protocols to be used for authentication, thus ensuring a backup system for authentication in case the initial method fails. The software uses the first method listed to authenticate users; if that method fails to respond, the software selects the next authentication method in the method list. This process continues until there is successful communication with a listed authentication method or until all defined methods are exhausted. If authentication fails at any point in this cycle—meaning that the security server or local username database responds by denying the user access—the authentication process stops, and no other authentication methods are attempted.
Beginning in privileged EXEC mode, follow these steps to configure login authentication. This procedure is required.
Step 1
Step 2
Command configure terminal aaa new-model
Purpose
Enter global configuration mode.
Enable AAA.
7-28
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 7 Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
Step 3
Step 4
Step 5 line [ console | tty | vty ] line-number
[ ending-line-number ] login authentication { default | list-name }
Step 6
Step 7
Step 8
Command aaa authentication login { default | list-name } method1 [ method2...
] end show running-config copy running-config startup-config
Purpose
Create a login authentication method list.
• To create a default list that is used when a named list is not specified in the login authentication command, use the default keyword followed by the methods that are to be used in default situations. The default method list is automatically applied to all ports.
•
•
For list-name , specify a character string to name the list you are creating.
For method1...
, specify the actual method the authentication algorithm tries. The additional methods of authentication are used only if the previous method returns an error, not if it fails.
Select one of these methods:
– enable —Use the enable password for authentication. Before you can use this authentication method, you must define an enable password by using the enable password global configuration command.
–
–
–
– group radius —Use RADIUS authentication. Before you can use this authentication method, you must configure the RADIUS
server. For more information, see the “Identifying the RADIUS
Server Host” section on page 7-26 .
line —Use the line password for authentication. Before you can use this authentication method, you must define a line password.
Use the password password line configuration command.
local —Use the local username database for authentication. You must enter username information in the database. Use the username name password global configuration command.
local-case —Use a case-sensitive local username database for authentication. You must enter username information in the database by using the username password global configuration command.
– none —Do not use any authentication for login.
Enter line configuration mode, and configure the lines to which you want to apply the authentication list.
Apply the authentication list to a line or set of lines.
•
•
If you specify default , use the default list created with the aaa authentication login command.
For list-name , specify the list created with the aaa authentication login command.
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
7-29
Chapter 7 Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
To disable AAA, use the no aaa new-model global configuration command. To disable AAA authentication, use the no aaa authentication login { default | list-name } method1 [ method2...
] global configuration command. To either disable RADIUS authentication for logins or to return to the default value, use the no login authentication { default | list-name } line configuration command.
Note To secure the switch for HTTP access by using AAA methods, you must configure the switch with the ip http authentication aaa global configuration command. Configuring AAA authentication does not secure the switch for HTTP access by using AAA methods.
For more information about the ip http authentication command, see the Cisco IOS Security Command
Reference, Release 12.2 from the Cisco.com page under Documentation > Cisco IOS Software > 12.2
Mainline > Command References .
Defining AAA Server Groups
You can configure the switch to use AAA server groups to group existing server hosts for authentication.
You select a subset of the configured server hosts and use them for a particular service. The server group is used with a global server-host list, which lists the IP addresses of the selected server hosts.
Server groups also can include multiple host entries for the same server if each entry has a unique identifier (the combination of the IP address and UDP port number), allowing different ports to be individually defined as RADIUS hosts providing a specific AAA service. If you configure two different host entries on the same RADIUS server for the same service, (for example, accounting), the second configured host entry acts as a fail-over backup to the first one.
You use the server group server configuration command to associate a particular server with a defined group server. You can either identify the server by its IP address or identify multiple host instances or entries by using the optional auth-port and acct-port keywords.
7-30
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 7 Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
Beginning in privileged EXEC mode, follow these steps to define the AAA server group and associate a particular RADIUS server with it:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Command configure terminal radius-server host { hostname | ip-address } [ auth-port port-number ]
[ acct-port port-number ] [ timeout seconds ] [ retransmit retries ] [ key string ]
Purpose
Enter global configuration mode.
Specify the IP address or hostname of the remote RADIUS server host.
•
•
•
•
(Optional) For auth-port port-number , specify the UDP destination port for authentication requests.
(Optional) For acct-port port-number , specify the UDP destination port for accounting requests.
(Optional) For timeout seconds , specify the time interval that the switch waits for the RADIUS server to reply before resending. The range is 1 to 1000. This setting overrides the radius-server timeout global configuration command setting. If no timeout is set with the radius-server host command, the setting of the radius-server timeout command is used.
(Optional) For retransmit retries , specify the number of times a
RADIUS request is resent to a server if that server is not responding or responding slowly. The range is 1 to 1000. If no retransmit value is set with the radius-server host command, the setting of the radius-server retransmit global configuration command is used.
•
Note
(Optional) For key string , specify the authentication and encryption key used between the switch and the RADIUS daemon running on the
RADIUS server.
The key is a text string that must match the encryption key used on the RADIUS server. Always configure the key as the last item in the radius-server host command. Leading spaces are ignored, but spaces within and at the end of the key are used. If you use spaces in your key, do not enclose the key in quotation marks unless the quotation marks are part of the key.
To configure the switch to recognize more than one host entry associated with a single IP address, enter this command as many times as necessary, making sure that each UDP port number is different. The switch software searches for hosts in the order in which you specify them. Set the timeout, retransmit, and encryption key values to use with the specific RADIUS host.
aaa new-model Enable AAA.
aaa group server radius group-name Define the AAA server-group with a group name.
server ip-address
This command puts the switch in a server group configuration mode.
Associate a particular RADIUS server with the defined server group.
Repeat this step for each RADIUS server in the AAA server group.
end show running-config
Each server in the group must be previously defined in Step 2.
Return to privileged EXEC mode.
Verify your entries.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
7-31
Chapter 7 Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
Step 8
Step 9
Command copy running-config startup-config
Purpose
(Optional) Save your entries in the configuration file.
Enable RADIUS login authentication. See the
Login Authentication” section on page 7-28
.
To remove the specified RADIUS server, use the no radius-server host hostname | ip-address global configuration command. To remove a server group from the configuration list, use the no aaa group server radius group-name global configuration command. To remove the IP address of a RADIUS server, use the no server ip-address server group configuration command.
In this example, the switch is configured to recognize two different RADIUS group servers ( group1 and group2 ). Group1 has two different host entries on the same RADIUS server configured for the same services. The second host entry acts as a fail-over backup to the first entry.
Switch(config)# radius-server host 172.20.0.1 auth-port 1000 acct-port 1001
Switch(config)# radius-server host 172.10.0.1 auth-port 1645 acct-port 1646
Switch(config)# aaa new-model
Switch(config)# aaa group server radius group1
Switch(config-sg-radius)# server 172.20.0.1 auth-port 1000 acct-port 1001
Switch(config-sg-radius)# exit
Switch(config)# aaa group server radius group2
Switch(config-sg-radius)# server 172.20.0.1 auth-port 2000 acct-port 2001
Switch(config-sg-radius)# exit
Configuring RADIUS Authorization for User Privileged Access and Network Services
AAA authorization limits the services available to a user. When AAA authorization is enabled, the switch uses information retrieved from the user’s profile, which is in the local user database or on the security server, to configure the user’s session. The user is granted access to a requested service only if the information in the user profile allows it.
You can use the aaa authorization global configuration command with the radius keyword to set parameters that restrict a user’s network access to privileged EXEC mode.
The aaa authorization exec radius local command sets these authorization parameters:
•
•
Use RADIUS for privileged EXEC access authorization if authentication was performed by using
RADIUS.
Use the local database if authentication was not performed by using RADIUS.
Note Authorization is bypassed for authenticated users who log in through the CLI even if authorization has been configured.
Beginning in privileged EXEC mode, follow these steps to specify RADIUS authorization for privileged
EXEC access and network services:
Step 1
Step 2
Command configure terminal aaa authorization network radius
Purpose
Enter global configuration mode.
Configure the switch for user RADIUS authorization for all network-related service requests.
7-32
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 7 Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
Step 3
Step 4
Step 5
Step 6
Command aaa authorization exec radius end show running-config copy running-config startup-config
Purpose
Configure the switch for user RADIUS authorization if the user has privileged EXEC access.
The exec keyword might return user profile information (such as autocommand information).
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
To disable authorization, use the no aaa authorization { network | exec } method1 global configuration command.
Starting RADIUS Accounting
The AAA accounting feature tracks the services that users are accessing and the amount of network resources that they are consuming. When AAA accounting is enabled, the switch reports user activity to the RADIUS security server in the form of accounting records. Each accounting record contains accounting attribute-value (AV) pairs and is stored on the security server. This data can then be analyzed for network management, client billing, or auditing.
Beginning in privileged EXEC mode, follow these steps to enable RADIUS accounting for each Cisco
IOS privilege level and for network services:
Step 1
Step 2
Step 3
Command configure terminal aaa accounting network start-stop radius aaa accounting exec start-stop radius
Step 4
Step 5
Step 6 end show running-config copy running-config startup-config
Purpose
Enter global configuration mode.
Enable RADIUS accounting for all network-related service requests.
Enable RADIUS accounting to send a start-record accounting notice at the beginning of a privileged EXEC process and a stop-record at the end.
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
To disable accounting, use the no aaa accounting { network | exec } { start-stop } method1...
global configuration command.
Establishing a Session with a Router if the AAA Server is Unreachable
The aaa accounting system guarantee-first command guarantees system accounting as the first record, which is the default condition. In some situations, users might be prevented from starting a session on the console or terminal connection until after the system reloads, which can take more than 3 minutes.
To establish a console or Telnet session with the router if the AAA server is unreachable when the router reloads, use the no aaa accounting system guarantee-first command.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
7-33
Chapter 7 Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
Configuring Settings for All RADIUS Servers
Beginning in privileged EXEC mode, follow these steps to configure global communication settings between the switch and all RADIUS servers:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Command configure terminal radius-server key string radius-server retransmit retries
Purpose
Enter global configuration mode.
Specify the shared secret text string used between the switch and all
RADIUS servers.
Note The key is a text string that must match the encryption key used on the RADIUS server. Leading spaces are ignored, but spaces within and at the end of the key are used. If you use spaces in your key, do not enclose the key in quotation marks unless the quotation marks are part of the key.
Specify the number of times the switch sends each RADIUS request to the server before giving up. The default is 3; the range 1 to 1000.
radius-server timeout seconds Specify the number of seconds a switch waits for a reply to a RADIUS request before resending the request. The default is 5 seconds; the range is
1 to 1000.
radius-server deadtime minutes Specify the number of minutes a RADIUS server, which is not responding to authentication requests, to be skipped, thus avoiding the wait for the request to timeout before trying the next configured server. The default is
0; the range is 1 to 1440 minutes.
Return to privileged EXEC mode.
end show running-config Verify your settings.
copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default setting for the retransmit, timeout, and deadtime, use the no forms of these commands.
Configuring the Switch to Use Vendor-Specific RADIUS Attributes
The Internet Engineering Task Force (IETF) draft standard specifies a method for communicating vendor-specific information between the switch and the RADIUS server by using the vendor-specific attribute (attribute 26). Vendor-specific attributes (VSAs) allow vendors to support their own extended attributes not suitable for general use. The Cisco RADIUS implementation supports one vendor-specific option by using the format recommended in the specification. Cisco’s vendor-ID is 9, and the supported option has vendor-type 1, which is named cisco-avpair . The value is a string with this format: protocol : attribute sep value *
Protocol is a value of the Cisco protocol attribute for a particular type of authorization. Attribute and value are an appropriate attribute-value (AV) pair defined in the Cisco TACACS+ specification, and sep is = for mandatory attributes and is * for optional attributes. The full set of features available for
TACACS+ authorization can then be used for RADIUS.
For example, this AV pair activates Cisco’s multiple named ip address pools feature during IP authorization (during PPP IPCP address assignment): cisco-avpair= ”ip:addr-pool=first“
7-34
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 7 Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
This example shows how to provide a user logging in from a switch with immediate access to privileged
EXEC commands: cisco-avpair= ”shell:priv-lvl=15“
This example shows how to specify an authorized VLAN in the RADIUS server database: cisco-avpair= ”tunnel-type(#64)=VLAN(13)” cisco-avpair= ”tunnel-medium-type(#65)=802 media(6)” cisco-avpair= ”tunnel-private-group-id(#81)=vlanid”
This example shows how to apply an input ACL in ASCII format to an interface for the duration of this connection: cisco-avpair= “ip:inacl#1=deny ip 10.10.10.10 0.0.255.255 20.20.20.20 255.255.0.0” cisco-avpair= “ip:inacl#2=deny ip 10.10.10.10 0.0.255.255 any” cisco-avpair= “mac:inacl#3=deny any any decnet-iv”
This example shows how to apply an output ACL in ASCII format to an interface for the duration of this connection: cisco-avpair= “ip:outacl#2=deny ip 10.10.10.10 0.0.255.255 any”
Other vendors have their own unique vendor-IDs, options, and associated VSAs. For more information about vendor-IDs and VSAs, see RFC 2138, “Remote Authentication Dial-In User Service (RADIUS).”
Beginning in privileged EXEC mode, follow these steps to configure the switch to recognize and use
VSAs:
Step 1
Step 2
Step 3
Step 4
Step 5
Command configure terminal
Purpose
Enter global configuration mode.
radius-server vsa send [ accounting | authentication ]
Enable the switch to recognize and use VSAs as defined by RADIUS IETF attribute 26.
• (Optional) Use the accounting keyword to limit the set of recognized vendor-specific attributes to only accounting attributes.
• (Optional) Use the authentication keyword to limit the set of recognized vendor-specific attributes to only authentication attributes.
If you enter this command without keywords, both accounting and authentication vendor-specific attributes are used.
Return to privileged EXEC mode.
end show running-config Verify your settings.
copy running-config startup-config (Optional) Save your entries in the configuration file.
For a complete list of RADIUS attributes or more information about vendor-specific attribute 26, see the
“RADIUS Attributes” appendix in the Cisco IOS Security Configuration Guide, Release 12.2 from the
Cisco.com page under Documentation > Cisco IOS Software > 12.2 Mainline > Command
References .
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
7-35
Chapter 7 Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
Configuring the Switch for Vendor-Proprietary RADIUS Server Communication
Although an IETF draft standard for RADIUS specifies a method for communicating vendor-proprietary information between the switch and the RADIUS server, some vendors have extended the RADIUS attribute set in a unique way. Cisco IOS software supports a subset of vendor-proprietary RADIUS attributes.
As mentioned earlier, to configure RADIUS (whether vendor-proprietary or IETF draft-compliant), you must specify the host running the RADIUS server daemon and the secret text string it shares with the switch. You specify the RADIUS host and secret text string by using the radius-server global configuration commands.
Beginning in privileged EXEC mode, follow these steps to specify a vendor-proprietary RADIUS server host and a shared secret text string:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Command configure terminal
Purpose
Enter global configuration mode.
radius-server host { hostname | ip-address } non-standard Specify the IP address or hostname of the remote
RADIUS server host and identify that it is using a vendor-proprietary implementation of RADIUS.
radius-server key string Specify the shared secret text string used between the switch and the vendor-proprietary RADIUS server.
The switch and the RADIUS server use this text string to encrypt passwords and exchange responses.
end show running-config copy running-config startup-config
Note The key is a text string that must match the encryption key used on the RADIUS server.
Leading spaces are ignored, but spaces within and at the end of the key are used. If you use spaces in your key, do not enclose the key in quotation marks unless the quotation marks are part of the key.
Return to privileged EXEC mode.
Verify your settings.
(Optional) Save your entries in the configuration file.
To delete the vendor-proprietary RADIUS host, use the no radius-server host { hostname | ip-address } non-standard global configuration command. To disable the key, use the no radius-server key global configuration command.
This example shows how to specify a vendor-proprietary RADIUS host and to use a secret key of rad124 between the switch and the server:
Switch(config)# radius-server host 172.20.30.15 nonstandard
Switch(config)# radius-server key rad124
7-36
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 7 Configuring Switch-Based Authentication
Controlling Switch Access with RADIUS
Configuring CoA on the Switch
Beginning in privileged EXEC mode, follow these steps to configure CoA on a switch. This procedure is required.
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
Step 12
Step 13
Step 14
Command configure terminal aaa new-model Enable AAA.
aaa server radius dynamic-author client { ip-address | name } [ vrf vrfname ]
[ server-key string ]
Configure the switch as an authentication, authorization, and accounting
(AAA) server to facilitate interaction with an external policy server.
Enter dynamic authorization local server configuration mode and specify a RADIUS client from which a device will accept CoA and disconnect requests.
server-ke y [ 0 | 7 ] string port port-number
Configure the RADIUS key to be shared between a device and RADIUS clients.
Specify the port on which a device listens for RADIUS requests from configured RADIUS clients.
auth-type { any | all | session-key }
Purpose
Enter global configuration mode.
ignore session-key ignore server-key
Specify the type of authorization the switch uses for RADIUS clients.
The client must match all the configured attributes for authorization.
(Optional) Configure the switch to ignore the session-key.
For more information about the ignore command, see the Cisco IOS
Intelligent Services Gateway Command Reference on Cisco.com.
(Optional) Configure the switch to ignore the server-key.
authentication command bounce-port ignore
For more information about the ignore command, see the Cisco IOS
Intelligent Services Gateway Command Reference on Cisco.com.
(Optional) Configure the switch to ignore a CoA request to temporarily disable the port hosting a session. The purpose of temporarily disabling the port is to trigger a DHCP renegotiation from the host when a VLAN change occurs and there is no supplicant on the endpoint to detect the change.
authentication command disable-port ignore
(Optional) Configure the switch to ignore a nonstandard command requesting that the port hosting a session be administratively shut down.
Shutting down the port results in termination of the session. end show running-config copy running-config startup-config
Use standard CLI or SNMP commands to re-enable the port.
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
To disable AAA, use the no aaa new-model global configuration command. To disable the AAA server functionality on the switch, use the no aaa server radius dynamic authorization global configuration command.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
7-37
Chapter 7 Configuring Switch-Based Authentication
Controlling Switch Access with Kerberos
Monitoring and Troubleshooting CoA Functionality
•
•
•
The following Cisco IOS commands can be used to monitor and troubleshoot CoA functionality on the switch:
• debug radius
•
• debug aaa coa debug aaa pod debug aaa subsys debug cmdhd [ detail | error | events ] show aaa attributes protocol radius
Configuring RADIUS Server Load Balancing
This feature allows access and authentication requests to be evenly across all RADIUS servers in a server group. For more information, see the “RADIUS Server Load Balancing” chapter of the “Cisco IOS
Security Configuration Guide”, Release 12.2: http://www.ciscosystems.com/en/US/docs/ios/12_2sb/feature/guide/sbrdldbl.html
Displaying the RADIUS Configuration
To display the RADIUS configuration, use the show running-config privileged EXEC command.
Controlling Switch Access with Kerberos
This section describes how to enable and configure the Kerberos security system, which authenticates requests for network resources by using a trusted third party. To use this feature, the cryptographic (that is, supports encryption) versions of the switch software must be installed on your switch.
You must obtain authorization to use this feature and to download the cryptographic software files from
Cisco.com. For more information, see the release notes for this release.
•
•
Understanding Kerberos, page 7-39
•
Configuring Kerberos, page 7-42
For Kerberos configuration examples, see the “Kerberos Configuration Examples” section in the
“Security Server Protocols” chapter of the Cisco IOS Security Configuration Guide, Release 12.2, at this
URL: http://www.cisco.com/en/US/docs/ios/12_2/security/configuration/guide/fsecur_c.html
For complete syntax and usage information for the commands used in this section, see the “Kerberos
Commands” section in the “Security Server Protocols” chapter of the Cisco IOS Security Command
Reference, Release 12.2, at this URL: http://www.cisco.com/en/US/docs/ios/12_2/security/command/reference/fsecur_r.html
7-38
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 7 Configuring Switch-Based Authentication
Controlling Switch Access with Kerberos
Note In the Kerberos configuration examples and in the Cisco IOS Security Command Reference,
Release 12.2, the trusted third party can be a switch that supports Kerberos, that is configured as a network security server, and that can authenticate users by using the Kerberos protocol.
Understanding Kerberos
Kerberos is a secret-key network authentication protocol, which was developed at the Massachusetts
Institute of Technology (MIT). It uses the Data Encryption Standard (DES) cryptographic algorithm for encryption and authentication and authenticates requests for network resources. Kerberos uses the concept of a trusted third party to perform secure verification of users and services. This trusted third party is called the key distribution center (KDC).
Kerberos verifies that users are who they claim to be and the network services that they use are what the services claim to be. To do this, a KDC or trusted Kerberos server issues tickets to users. These tickets, which have a limited lifespan, are stored in user credential caches. The Kerberos server uses the tickets instead of usernames and passwords to authenticate users and network services.
Note A Kerberos server can be a switch that is configured as a network security server and that can authenticate users by using the Kerberos protocol.
Table 7-5
Term
Authentication
The Kerberos credential scheme uses a process called single logon . This process authenticates a user once and then allows secure authentication (without encrypting another password) wherever that user credential is accepted.
This software release supports Kerberos 5, which allows organizations that are already using Kerberos 5 to use the same Kerberos authentication database on the KDC that they are already using on their other network hosts (such as UNIX servers and PCs).
In this software release, Kerberos supports these network services:
•
•
Telnet rlogin
• rsh (Remote Shell Protocol)
lists the common Kerberos-related terms and definitions:
Kerberos Terms
Authorization
Credential
Definition
A process by which a user or service identifies itself to another service. For example, a client can authenticate to a switch or a switch can authenticate to another switch.
A means by which the switch identifies what privileges the user has in a network or on the switch and what actions the user can perform.
A general term that refers to authentication tickets, such as TGTs
1
and service credentials.
Kerberos credentials verify the identity of a user or service. If a network service decides to trust the Kerberos server that issued a ticket, it can be used in place of re-entering a username and password. Credentials have a default lifespan of eight hours.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
7-39
Chapter 7 Configuring Switch-Based Authentication
Controlling Switch Access with Kerberos
Table 7-5 Kerberos Terms (continued)
Term
Instance
KDC
2
Kerberized
Kerberos realm
Kerberos server
KEYTAB
Principal
3
Service credential
SRVTAB
TGT
1.
TGT = ticket granting ticket
2.
KDC = key distribution center
3.
KEYTAB = key table
4.
SRVTAB = server table
Definition
An authorization level label for Kerberos principals. Most Kerberos principals are of the form user@REALM (for example, [email protected]). A Kerberos principal with a Kerberos instance has the form user/instance@REALM (for example, smith/[email protected]).
The Kerberos instance can be used to specify the authorization level for the user if authentication is successful. The server of each network service might implement and enforce the authorization mappings of Kerberos instances but is not required to do so.
Note The Kerberos principal and instance names must be in all lowercase characters.The
Kerberos realm name must be in all uppercase characters.
Key distribution center that consists of a Kerberos server and database program that is running on a network host.
A term that describes applications and services that have been modified to support the Kerberos credential infrastructure.
A domain consisting of users, hosts, and network services that are registered to a Kerberos server. The Kerberos server is trusted to verify the identity of a user or network service to another user or network service.
Note The Kerberos realm name must be in all uppercase characters.
A daemon that is running on a network host. Users and network services register their identity with the Kerberos server. Network services query the Kerberos server to authenticate to other network services.
A password that a network service shares with the KDC. In Kerberos 5 and later Kerberos versions, the network service authenticates an encrypted service credential by using the
KEYTAB to decrypt it. In Kerberos versions earlier than Kerberos 5, KEYTAB is referred to as
SRVTAB
4
.
Also known as a Kerberos identity, this is who you are or what a service is according to the
Kerberos server.
Note The Kerberos principal name must be in all lowercase characters.
A credential for a network service. When issued from the KDC, this credential is encrypted with the password shared by the network service and the KDC. The password is also shared with the user TGT.
A password that a network service shares with the KDC. In Kerberos 5 or later Kerberos versions, SRVTAB is referred to as KEYTAB.
Ticket granting ticket that is a credential that the KDC issues to authenticated users. When users receive a TGT, they can authenticate to network services within the Kerberos realm represented by the KDC.
7-40
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 7 Configuring Switch-Based Authentication
Controlling Switch Access with Kerberos
Kerberos Operation
A Kerberos server can be a switch that is configured as a network security server and that can authenticate remote users by using the Kerberos protocol. Although you can customize Kerberos in a number of ways, remote users attempting to access network services must pass through three layers of security before they can access network services.
To authenticate to network services by using a switch as a Kerberos server, remote users must follow these steps:
1.
2.
3.
Authenticating to a Boundary Switch, page 7-41
Obtaining a TGT from a KDC, page 7-41
Authenticating to Network Services, page 7-42
Authenticating to a Boundary Switch
This section describes the first layer of security through which a remote user must pass. The user must first authenticate to the boundary switch. This process then occurs:
1.
2.
3.
4.
The user opens an un-Kerberized Telnet connection to the boundary switch.
The switch prompts the user for a username and password.
The switch requests a TGT from the KDC for this user.
The KDC sends an encrypted TGT that includes the user identity to the switch.
5.
The switch attempts to decrypt the TGT by using the password that the user entered.
• If the decryption is successful, the user is authenticated to the switch.
• If the decryption is not successful, the user repeats Step 2 either by re-entering the username and password (noting if Caps Lock or Num Lock is on or off) or by entering a different username and password.
A remote user who initiates a un-Kerberized Telnet session and authenticates to a boundary switch is inside the firewall, but the user must still authenticate directly to the KDC before getting access to the network services. The user must authenticate to the KDC because the TGT that the KDC issues is stored on the switch and cannot be used for additional authentication until the user logs on to the switch.
Obtaining a TGT from a KDC
This section describes the second layer of security through which a remote user must pass. The user must now authenticate to a KDC and obtain a TGT from the KDC to access network services.
For instructions about how to authenticate to a KDC, see the “Obtaining a TGT from a KDC” section in the “Security Server Protocols” chapter of the Cisco IOS Security Configuration Guide, Release 12.2, at this URL: http://www.cisco.com/en/US/docs/ios/12_2/security/configuration/guide/scfkerb.html
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
7-41
Chapter 7 Configuring Switch-Based Authentication
Configuring the Switch for Local Authentication and Authorization
Authenticating to Network Services
This section describes the third layer of security through which a remote user must pass. The user with a TGT must now authenticate to the network services in a Kerberos realm.
For instructions about how to authenticate to a network service, see the “Authenticating to Network
Services” section in the “Security Server Protocols” chapter of the Cisco IOS Security Configuration
Guide, Release 12.2, at this URL: http://www.cisco.com/en/US/docs/ios/12_2/security/configuration/guide/scfkerb.html
Configuring Kerberos
So that remote users can authenticate to network services, you must configure the hosts and the KDC in the Kerberos realm to communicate and mutually authenticate users and network services. To do this, you must identify them to each other. You add entries for the hosts to the Kerberos database on the KDC and add KEYTAB files generated by the KDC to all hosts in the Kerberos realm. You also create entries for the users in the KDC database.
When you add or create entries for the hosts and users, follow these guidelines:
• The Kerberos principal name must be in all lowercase characters.
•
•
The Kerberos instance name must be in all lowercase characters.
The Kerberos realm name must be in all uppercase characters.
Note A Kerberos server can be a switch that is configured as a network security server and that can authenticate users by using the Kerberos protocol.
To set up a Kerberos-authenticated server-client system, follow these steps:
•
•
Configure the KDC by using Kerberos commands.
Configure the switch to use the Kerberos protocol.
For instructions, see the “Kerberos Configuration Task List” section in the “Security Server Protocols” chapter of the Cisco IOS Security Configuration Guide, Release 12.2, at this URL: http://www.cisco.com/en/US/docs/ios/12_2/security/configuration/guide/scfkerb.html
Configuring the Switch for Local Authentication and
Authorization
You can configure AAA to operate without a server by setting the switch to implement AAA in local mode. The switch then handles authentication and authorization. No accounting is available in this configuration.
Beginning in privileged EXEC mode, follow these steps to configure the switch for local AAA:
Step 1
Step 2
Command configure terminal aaa new-model
Purpose
Enter global configuration mode.
Enable AAA.
7-42
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 7 Configuring Switch-Based Authentication
Configuring the Switch for Secure Shell
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Command aaa authentication login default local Set the login authentication to use the local username database. The default keyword applies the local user database authentication to all ports.
aaa authorization exec local
Purpose aaa authorization network local
Configure user AAA authorization, check the local database, and allow the user to run an EXEC shell.
Configure user AAA authorization for all network-related service requests.
username name [ privilege level ]
{ password encryption-type password }
Enter the local database, and establish a username-based authentication system.
end show running-config copy running-config startup-config
Repeat this command for each user.
• For name , specify the user ID as one word. Spaces and quotation marks are not allowed.
•
•
(Optional) For level , specify the privilege level the user has after gaining access. The range is 0 to 15. Level 15 gives privileged EXEC mode access. Level 0 gives user EXEC mode access.
For encryption-type , enter 0 to specify that an unencrypted password follows. Enter 7 to specify that a hidden password follows.
• For password , specify the password the user must enter to gain access to the switch. The password must be from 1 to 25 characters, can contain embedded spaces, and must be the last option specified in the username command.
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
To disable AAA, use the no aaa new-model global configuration command. To disable authorization, use the no aaa authorization { network | exec } method1 global configuration command.
Note To secure the switch for HTTP access by using AAA methods, you must configure the switch with the ip http authentication aaa global configuration command. Configuring AAA authentication does not secure the switch for HTTP access by using AAA methods.
For more information about the ip http authentication command, see the Cisco IOS Security Command
Reference, Release 12.2
.
Configuring the Switch for Secure Shell
This section describes how to configure the Secure Shell (SSH) feature. To use this feature, the cryptographic (that is, supports encryption) versions of the switch software must be installed on your switch. You must obtain authorization to use this feature and to download the cryptographic software files from Cisco.com. For more information, see the release notes for this release.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
7-43
Chapter 7 Configuring Switch-Based Authentication
Configuring the Switch for Secure Shell
SSH in IPv6 functions the same and offers the same benefits as SSH in IPv4. IPv6 enhancements to SSH consist of support for IPv6 addresses that enable a Cisco router to accept and establish secure, encrypted connections with remote IPv6 nodes over an IPv6 transport.
These sections contain this information:
•
•
•
Displaying the SSH Configuration and Status, page 7-48
For SSH configuration examples, see the “SSH Configuration Examples” section in the “Configuring
Secure Shell” chapter of the Cisco IOS Security Configuration Guide, Cisco IOS Release 12.2
, at this URL: http://www.cisco.com/en/US/docs/ios/12_2/security/configuration/guide/scfssh.html
Note For complete syntax and usage information for the commands used in this section, see the command reference for this release and the command reference for Cisco IOS Release 12.2 at this URL: http://www.cisco.com/en/US/docs/ios/12_2/security/command/reference/fsecur_r.html
Understanding SSH
SSH is a protocol that provides a secure, remote connection to a device. SSH provides more security for remote connections than Telnet does by providing strong encryption when a device is authenticated. This software release supports SSH Version 1 (SSHv1) and SSH Version 2 (SSHv2).
This section consists of these topics:
•
•
SSH Servers, Integrated Clients, and Supported Versions, page 7-44
SSH Servers, Integrated Clients, and Supported Versions
The SSH feature has an SSH server and an SSH integrated client, which are applications that run on the switch. You can use an SSH client to connect to a switch running the SSH server. The SSH server works with the SSH client supported in this release and with non-Cisco SSH clients. The SSH client also works with the SSH server supported in this release and with non-Cisco SSH servers.
The switch supports an SSHv1 or an SSHv2 server.
The switch supports an SSHv1 client.
SSH supports the Data Encryption Standard (DES) encryption algorithm, the Triple DES (3DES) encryption algorithm, and password-based user authentication.
SSH also supports these user authentication methods:
•
•
•
RADIUS (for more information, see the
“Controlling Switch Access with RADIUS” section on page 7-17 )
Local authentication and authorization (for more information, see the
Local Authentication and Authorization” section on page 7-42 )
7-44
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 7 Configuring Switch-Based Authentication
Configuring the Switch for Secure Shell
Limitations
Note This software release does not support IP Security (IPSec).
These limitations apply to SSH:
•
•
•
The switch supports Rivest, Shamir, and Adelman (RSA) authentication.
SSH supports only the execution-shell application.
•
The SSH server and the SSH client are supported only on DES (56-bit) and 3DES (168-bit) data encryption software.
The switch supports the Advanced Encryption Standard (AES) encryption algorithm with a 128-bit key, 192-bit key, or 256-bit key. However, symmetric cipher AES to encrypt the keys is not supported.
Configuring SSH
This section has this configuration information:
•
Configuration Guidelines, page 7-45
•
•
Setting Up the Switch to Run SSH, page 7-46
(required)
Configuring the SSH Server, page 7-47
(required only if you are configuring the switch as an SSH server)
Configuration Guidelines
Follow these guidelines when configuring the switch as an SSH server or SSH client:
•
•
An RSA key pair generated by a SSHv1 server can be used by an SSHv2 server, and the reverse.
If you get CLI error messages after entering the crypto key generate rsa global configuration command, an RSA key pair has not been generated. Reconfigure the hostname and domain, and then enter the crypto key generate rsa command. For more information, see the
“Setting Up the Switch to Run SSH” section on page 7-46
.
•
•
•
When generating the RSA key pair, the message No host name specified might appear. If it does, you must configure a hostname by using the hostname global configuration command.
When generating the RSA key pair, the message
No domain specified
might appear. If it does, you must configure an IP domain name by using the ip domain-name global configuration command.
When configuring the local authentication and authorization authentication method, make sure that
AAA is disabled on the console.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
7-45
Chapter 7 Configuring Switch-Based Authentication
Configuring the Switch for Secure Shell
Setting Up the Switch to Run SSH
Follow these steps to set up your switch to run SSH:
1.
Download the cryptographic software image from Cisco.com. This step is required. For more information, see the release notes for this release.
2.
3.
Configure a hostname and IP domain name for the switch. Follow this procedure only if you are configuring the switch as an SSH server.
Generate an RSA key pair for the switch, which automatically enables SSH. Follow this procedure only if you are configuring the switch as an SSH server.
4.
Configure user authentication for local or remote access. This step is required. For more information, see the
“Configuring the Switch for Local Authentication and Authorization” section on page 7-42
.
Beginning in privileged EXEC mode, follow these steps to configure a hostname and an IP domain name and to generate an RSA key pair. This procedure is required if you are configuring the switch as an SSH server.
Step 1
Step 2
Step 3
Step 4
Command configure terminal hostname hostname ip domain-name domain_name crypto key generate rsa
Purpose
Enter global configuration mode.
Configure a hostname for your switch.
Configure a host domain for your switch.
Enable the SSH server for local and remote authentication on the switch and generate an RSA key pair.
We recommend that a minimum modulus size of 1024 bits.
When you generate RSA keys, you are prompted to enter a modulus length. A longer modulus length might be more secure, but it takes longer to generate and to use.
Return to privileged EXEC mode.
Show the version and configuration information for your SSH server.
Step 5
Step 6
Step 7 end show ip ssh or show ssh copy running-config startup-config
Show the status of the SSH server on the switch.
(Optional) Save your entries in the configuration file.
To delete the RSA key pair, use the crypto key zeroize rsa global configuration command. After the
RSA key pair is deleted, the SSH server is automatically disabled.
7-46
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 7 Configuring Switch-Based Authentication
Configuring the Switch for Secure Shell
Configuring the SSH Server
Beginning in privileged EXEC mode, follow these steps to configure the SSH server:
Step 1
Step 2
Step 3
Step 4
Command configure terminal ip ssh version [ 1 | 2 ] ip ssh { timeout seconds | authentication-retries number } line vty line_number
[ ending_line_number ] transport input ssh
Purpose
Enter global configuration mode.
(Optional) Configure the switch to run SSH Version 1 or SSH Version 2.
• 1 —Configure the switch to run SSH Version 1.
• 2 —Configure the switch to run SSH Version 2.
If you do not enter this command or do not specify a keyword, the SSH server selects the latest SSH version supported by the SSH client. For example, if the SSH client supports SSHv1 and SSHv2, the SSH server selects SSHv2.
Configure the SSH control parameters:
• Specify the time-out value in seconds; the default is 120 seconds. The range is 0 to 120 seconds. This parameter applies to the SSH negotiation phase. After the connection is established, the switch uses the default time-out values of the CLI-based sessions.
By default, up to five simultaneous, encrypted SSH connections for multiple CLI-based sessions over the network are available (session 0 to session 4). After the execution shell starts, the CLI-based session time-out value returns to the default of 10 minutes.
•
•
Specify the number of times that a client can re-authenticate to the server. The default is 3; the range is 0 to 5.
Repeat this step when configuring both parameters.
(Optional) Configure the virtual terminal line settings.
Enter line configuration mode to configure the virtual terminal line settings. For line_number and ending_line_number , specify a pair of lines. The range is 0 to 15.
• Specify that the switch prevent non-SSH Telnet connections. This limits the router to only SSH connections.
Return to privileged EXEC mode.
Show the version and configuration information for your SSH server.
Step 5
Step 6
Step 7 end show ip ssh or show ssh copy running-config startup-config
Show the status of the SSH server connections on the switch.
(Optional) Save your entries in the configuration file.
To return to the default SSH control parameters, use the no ip ssh { timeout | authentication-retries } global configuration command.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
7-47
Chapter 7 Configuring Switch-Based Authentication
Configuring the Switch for Secure Socket Layer HTTP
Displaying the SSH Configuration and Status
To display the SSH server configuration and status, use one or more of the privileged EXEC commands in
:
Table 7-6 Commands for Displaying the SSH Server Configuration and Status
Command show ip ssh show ssh
Purpose
Shows the version and configuration information for the SSH server.
Shows the status of the SSH server.
For more information about these commands, see the “ Secure Shell Commands ” section in the “Other
Security Features” chapter of the Cisco IOS Security Command Reference, Cisco IOS Release 12.2, at this URL: http://www.cisco.com/en/US/docs/ios/12_2/security/command/reference/fsecur_r.html
Configuring the Switch for Secure Socket Layer HTTP
This section describes how to configure Secure Socket Layer (SSL) version 3.0 support for the HTTP 1.1 server and client. SSL provides server authentication, encryption, and message integrity, as well as
HTTP client authentication, to allow secure HTTP communications. To use this feature, the cryptographic (encrypted) software image must be installed on your switch. You must obtain authorization to use this feature and to download the cryptographic software files from Cisco.com. For more information about the crypto image, see the release notes for this release.
These sections contain this information:
•
•
Understanding Secure HTTP Servers and Clients, page 7-48
Configuring Secure HTTP Servers and Clients, page 7-51
•
Displaying Secure HTTP Server and Client Status, page 7-54
For configuration examples and complete syntax and usage information for the commands used in this section, see the “HTTPS - HTTP Server and Client with SSL 3.0” feature description for Cisco IOS
Release 12.2T at this URL: http://www.cisco.com/en/US/docs/ios/12_2t/12_2t15/feature/guide/ftsslsht.html
Understanding Secure HTTP Servers and Clients
On a secure HTTP connection, data to and from an HTTP server is encrypted before being sent over the
Internet. HTTP with SSL encryption provides a secure connection to allow such functions as configuring a switch from a Web browser. Cisco's implementation of the secure HTTP server and secure HTTP client uses an implementation of SSL Version 3.0 with application-layer encryption. HTTP over SSL is abbreviated as HTTPS; the URL of a secure connection begins with https:// instead of http://.
The primary role of the HTTP secure server (the switch) is to listen for HTTPS requests on a designated port (the default HTTPS port is 443) and pass the request to the HTTP 1.1 Web server. The HTTP 1.1 server processes requests and passes responses (pages) back to the HTTP secure server, which, in turn, responds to the original request.
7-48
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 7 Configuring Switch-Based Authentication
Configuring the Switch for Secure Socket Layer HTTP
The primary role of the HTTP secure client (the web browser) is to respond to Cisco IOS application requests for HTTPS User Agent services, perform HTTPS User Agent services for the application, and pass the response back to the application.
Certificate Authority Trustpoints
Certificate authorities (CAs) manage certificate requests and issue certificates to participating network devices. These services provide centralized security key and certificate management for the participating devices. Specific CA servers are referred to as trustpoints .
When a connection attempt is made, the HTTPS server provides a secure connection by issuing a certified X.509v3 certificate, obtained from a specified CA trustpoint, to the client. The client (usually a Web browser), in turn, has a public key that allows it to authenticate the certificate.
For secure HTTP connections, we highly recommend that you configure a CA trustpoint. If a CA trustpoint is not configured for the device running the HTTPS server, the server certifies itself and generates the needed RSA key pair. Because a self-certified (self-signed) certificate does not provide adequate security, the connecting client generates a notification that the certificate is self-certified, and the user has the opportunity to accept or reject the connection. This option is useful for internal network topologies (such as testing).
If you do not configure a CA trustpoint, when you enable a secure HTTP connection, either a temporary or a persistent self-signed certificate for the secure HTTP server (or client) is automatically generated.
•
•
If the switch is not configured with a hostname and a domain name, a temporary self-signed certificate is generated. If the switch reboots, any temporary self-signed certificate is lost, and a new temporary new self-signed certificate is assigned.
If the switch has been configured with a host and domain name, a persistent self-signed certificate is generated. This certificate remains active if you reboot the switch or if you disable the secure
HTTP server so that it will be there the next time you re-enable a secure HTTP connection.
Note The certificate authorities and trustpoints must be configured on each device individually. Copying them from other devices makes them invalid on the switch.
If a self-signed certificate has been generated, this information is included in the output of the show running-config privileged EXEC command. This is a partial sample output from that command displaying a self-signed certificate.
Switch# show running-config
Building configuration...
<output truncated> crypto pki trustpoint TP-self-signed-3080755072
enrollment selfsigned
subject-name cn=IOS-Self-Signed-Certificate-3080755072
revocation-check none
rsakeypair TP-self-signed-3080755072
!
crypto ca certificate chain TP-self-signed-3080755072
certificate self-signed 01
3082029F 30820208 A0030201 02020101 300D0609 2A864886 F70D0101 04050030
59312F30 2D060355 04031326 494F532D 53656C66 2D536967 6E65642D 43657274
69666963 6174652D 33303830 37353530 37323126 30240609 2A864886 F70D0109
02161743 45322D33 3535302D 31332E73 756D6D30 342D3335 3530301E 170D3933
30333031 30303030 35395A17 0D323030 31303130 30303030 305A3059 312F302D
<output truncated>
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
7-49
Chapter 7 Configuring Switch-Based Authentication
Configuring the Switch for Secure Socket Layer HTTP
You can remove this self-signed certificate by disabling the secure HTTP server and entering the no crypto pki trustpoint TP-self-signed-30890755072 global configuration command. If you later re-enable a secure HTTP server, a new self-signed certificate is generated.
Note The values that follow TP self-signed depend on the serial number of the device.
You can use an optional command ( ip http secure-client-auth ) to allow the HTTPS server to request an
X.509v3 certificate from the client. Authenticating the client provides more security than server authentication by itself.
For additional information on Certificate Authorities, see the “Configuring Certification Authority
Interoperability” chapter in the Cisco IOS Security Configuration Guide, Release 12.2
from the
Cisco.com page under Documentation > Cisco IOS Software > 12.2 Mainline > Command
References .
CipherSuites
A CipherSuite specifies the encryption algorithm and the digest algorithm to use on a SSL connection.
When connecting to the HTTPS server, the client Web browser offers a list of supported CipherSuites, and the client and server negotiate the best encryption algorithm to use from those on the list that are supported by both. For example, Netscape Communicator 4.76 supports U.S. security with RSA Public
Key Cryptography, MD2, MD5, RC2-CBC, RC4, DES-CBC, and DES-EDE3-CBC.
For the best possible encryption, you should use a client browser that supports 128-bit encryption, such as Microsoft Internet Explorer Version 5.5 (or later) or Netscape Communicator Version 4.76 (or later).
The SSL_RSA_WITH_DES_CBC_SHA CipherSuite provides less security than the other CipherSuites, as it does not offer 128-bit encryption.
The more secure and more complex CipherSuites require slightly more processing time. This list defines the CipherSuites supported by the switch and ranks them from fastest to slowest in terms of router processing load (speed):
1.
2.
3.
4.
SSL_RSA_WITH_DES_CBC_SHA—RSA key exchange (RSA Public Key Cryptography) with
DES-CBC for message encryption and SHA for message digest
SSL_RSA_WITH_RC4_128_MD5—RSA key exchange with RC4 128-bit encryption and MD5 for message digest
SSL_RSA_WITH_RC4_128_SHA—RSA key exchange with RC4 128-bit encryption and SHA for message digest
SSL_RSA_WITH_3DES_EDE_CBC_SHA—RSA key exchange with 3DES and DES-EDE3-CBC for message encryption and SHA for message digest
RSA (in conjunction with the specified encryption and digest algorithm combinations) is used for both key generation and authentication on SSL connections. This usage is independent of whether or not a
CA trustpoint is configured.
7-50
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 7 Configuring Switch-Based Authentication
Configuring the Switch for Secure Socket Layer HTTP
Configuring Secure HTTP Servers and Clients
These sections contain this configuration information:
•
Default SSL Configuration, page 7-51
•
•
•
•
SSL Configuration Guidelines, page 7-51
Configuring a CA Trustpoint, page 7-51
Configuring the Secure HTTP Server, page 7-52
Configuring the Secure HTTP Client, page 7-54
Default SSL Configuration
The standard HTTP server is enabled.
SSL is enabled.
No CA trustpoints are configured.
No self-signed certificates are generated.
SSL Configuration Guidelines
Before you configure a CA trustpoint, you should ensure that the system clock is set. If the clock is not set, the certificate is rejected due to an incorrect date.
Configuring a CA Trustpoint
For secure HTTP connections, we recommend that you configure an official CA trustpoint.
A CA trustpoint is more secure than a self-signed certificate.
Beginning in privileged EXEC mode, follow these steps to configure a CA trustpoint:
Step 1
Step 2
Command configure terminal hostname hostname
Step 3 ip domain-name domain-name
Step 4 crypto key generate rsa
Step 5 crypto ca trustpoint name
Step 6
Step 7 enrollment url url enrollment http-proxy host-name port-number
Purpose
Enter global configuration mode.
Specify the hostname of the switch (required only if you have not previously configured a hostname). The hostname is required for security keys and certificates.
Specify the IP domain name of the switch (required only if you have not previously configured an IP domain name). The domain name is required for security keys and certificates.
(Optional) Generate an RSA key pair. RSA key pairs are required before you can obtain a certificate for the switch. RSA key pairs are generated automatically. You can use this command to regenerate the keys, if needed.
Specify a local configuration name for the CA trustpoint and enter CA trustpoint configuration mode.
Specify the URL to which the switch should send certificate requests.
(Optional) Configure the switch to obtain certificates from the CA through an HTTP proxy server.
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01 7-51
Chapter 7 Configuring Switch-Based Authentication
Configuring the Switch for Secure Socket Layer HTTP
Step 8
Command crl query url
Step 9 primary
Step 10 exit
Step 11
Step 12
Step 13
Step 14
Step 15 crypto ca authentication crypto ca enroll name name end show crypto ca trustpoints copy running-config startup-config
Purpose
Configure the switch to request a certificate revocation list (CRL) to ensure that the certificate of the peer has not been revoked.
(Optional) Specify that the trustpoint should be used as the primary
(default) trustpoint for CA requests.
Exit CA trustpoint configuration mode and return to global configuration mode.
Authenticate the CA by getting the public key of the CA. Use the same name used in Step 5.
Obtain the certificate from the specified CA trustpoint. This command requests a signed certificate for each RSA key pair.
Return to privileged EXEC mode.
Verify the configuration.
(Optional) Save your entries in the configuration file.
Use the no crypto ca trustpoint name global configuration command to delete all identity information and certificates associated with the CA.
Configuring the Secure HTTP Server
If you are using a certificate authority for certification, you should use the previous procedure to configure the CA trustpoint on the switch before enabling the HTTP server. If you have not configured a CA trustpoint, a self-signed certificate is generated the first time that you enable the secure HTTP server. After you have configured the server, you can configure options (path, access list to apply, maximum number of connections, or timeout policy) that apply to both standard and secure HTTP servers.
Beginning in privileged EXEC mode, follow these steps to configure a secure HTTP server:
Step 1
Step 2
Step 3
Step 4
Command show ip http server status configure terminal
ip http secure-server
ip http secure-port port-number
Step 5 ip http secure-ciphersuite
{[ 3des-ede-cbc-sha ] [ rc4-128-md5 ]
[ rc4-128-sha ] [ des-cbc-sha ]}
Purpose
(Optional) Display the status of the HTTP server to determine if the secure
HTTP server feature is supported in the software. You should see one of these lines in the output:
HTTP secure server capability: Present or
HTTP secure server capability: Not present
Enter global configuration mode.
Enable the HTTPS server if it has been disabled. The HTTPS server is enabled by default.
(Optional) Specify the port number to be used for the HTTPS server. The default port number is 443. Valid options are 443 or any number in the range 1025 to 65535.
(Optional) Specify the CipherSuites (encryption algorithms) to be used for encryption over the HTTPS connection. If you do not have a reason to specify a particularly CipherSuite, you should allow the server and client to negotiate a CipherSuite that they both support. This is the default.
7-52
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 7 Configuring Switch-Based Authentication
Configuring the Switch for Secure Socket Layer HTTP
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
Step 12
Step 13
Step 14
Command
ip http secure-client-auth ip http secure-trustpoint name
Purpose
(Optional) Configure the HTTP server to request an X.509v3 certificate from the client for authentication during the connection process. The default is for the client to request a certificate from the server, but the server does not attempt to authenticate the client.
Specify the CA trustpoint to use to get an X.509v3 security certificate and to authenticate the client certificate connection.
Note Use of this command assumes you have already configured a CA trustpoint according to the previous procedure.
ip http path path-name (Optional) Set a base HTTP path for HTML files. The path specifies the location of the HTTP server files on the local system (usually located in system flash memory).
ip http access-class access-list-number (Optional) Specify an access list to use to allow access to the HTTP server.
ip http max-connections value (Optional) Set the maximum number of concurrent connections that are allowed to the HTTP server. The range is 1 to 16; the default value is 5.
ip http timeout-policy idle seconds life seconds requests value
(Optional) Specify how long a connection to the HTTP server can remain open under the defined circumstances: end show ip http server secure status copy running-config startup-config
•
• idle —the maximum time period when no data is received or response data cannot be sent. The range is 1 to 600 seconds. The default is
180 seconds (3 minutes).
life —the maximum time period from the time that the connection is established. The range is 1 to 86400 seconds (24 hours). The default is 180 seconds.
• requests —the maximum number of requests processed on a persistent connection. The maximum value is 86400. The default is 1.
Return to privileged EXEC mode.
Display the status of the HTTP secure server to verify the configuration.
(Optional) Save your entries in the configuration file.
Use the no ip http server global configuration command to disable the standard HTTP server. Use the no ip http secure-server global configuration command to disable the secure HTTP server. Use the no ip http secure-port and the no ip http secure-ciphersuite global configuration commands to return to the default settings. Use the no ip http secure-client-auth global configuration command to remove the requirement for client authentication.
To verify the secure HTTP connection by using a Web browser, enter https:// URL , where the URL is the
IP address or hostname of the server switch. If you configure a port other than the default port, you must also specify the port number after the URL. For example: https://209.165.129:1026 or https://host.domain.com:1026
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
7-53
Chapter 7 Configuring Switch-Based Authentication
Configuring the Switch for Secure Socket Layer HTTP
Configuring the Secure HTTP Client
The standard HTTP client and secure HTTP client are always enabled. A certificate authority is required for secure HTTP client certification. This procedure assumes that you have previously configured a CA trustpoint on the switch. If a CA trustpoint is not configured and the remote HTTPS server requires client authentication, connections to the secure HTTP client fail.
Beginning in privileged EXEC mode, follow these steps to configure a secure HTTP client:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Command Purpose configure terminal Enter global configuration mode.
ip http client secure-trustpoint name (Optional) Specify the CA trustpoint to be used if the remote HTTP server requests client authentication. Using this command assumes that you have already configured a CA trustpoint by using the previous procedure. The command is optional if client authentication is not needed or if a primary trustpoint has been configured.
ip http client secure-ciphersuite
{[ 3des-ede-cbc-sha ] [ rc4-128-md5 ]
[ rc4-128-sha ] [ des-cbc-sha ]}
(Optional) Specify the CipherSuites (encryption algorithms) to be used for encryption over the HTTPS connection. If you do not have a reason to specify a particular CipherSuite, you should allow the server and client to negotiate a CipherSuite that they both support. This is the default.
Return to privileged EXEC mode.
end show ip http client secure status copy running-config startup-config
Display the status of the HTTP secure server to verify the configuration.
(Optional) Save your entries in the configuration file.
Use the no ip http client secure-trustpoint name to remove a client trustpoint configuration. Use the no ip http client secure-ciphersuite to remove a previously configured CipherSuite specification for the client.
Displaying Secure HTTP Server and Client Status
Table 7-7
To display the SSL secure server and client status, use the privileged EXEC commands in
:
Commands for Displaying the SSL Secure Server and Client Status
Command show ip http client secure status show ip http server secure status show running-config
Purpose
Shows the HTTP secure client configuration.
Shows the HTTP secure server configuration.
Shows the generated self-signed certificate for secure HTTP connections.
7-54
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 7 Configuring Switch-Based Authentication
Configuring the Switch for Secure Copy Protocol
Configuring the Switch for Secure Copy Protocol
The Secure Copy Protocol (SCP) feature provides a secure and authenticated method for copying switch configurations or switch image files. SCP relies on Secure Shell (SSH), an application and a protocol that provides a secure replacement for the Berkeley r-tools.
For SSH to work, the switch needs an RSA public/private key pair. This is the same with SCP, which relies on SSH for its secure transport.
Because SSH also relies on AAA authentication, and SCP relies further on AAA authorization, correct configuration is necessary.
• Before enabling SCP, you must correctly configure SSH, authentication, and authorization on the switch.
• Because SCP relies on SSH for its secure transport, the router must have an Rivest, Shamir, and
Adelman (RSA) key pair.
Note When using SCP, you cannot enter the password into the copy command. You must enter the password when prompted.
Information About Secure Copy
To configure the Secure Copy feature, you should understand these concepts.
The behavior of SCP is similar to that of remote copy (rcp), which comes from the Berkeley r-tools suite, except that SCP relies on SSH for security. SCP also requires that authentication, authorization, and accounting (AAA) authorization be configured so the router can determine whether the user has the correct privilege level.
A user who has appropriate authorization can use SCP to copy any file in the Cisco IOS File System
(IFS) to and from a switch by using the copy command. An authorized administrator can also do this from a workstation.
For information about how to configure and verify SCP, see the “Secure Copy Protocol” section in the
Cisco IOS Security Configuration Guide: Securing User Services, Release 12.4
: http://www.cisco.com/en/US/docs/ios/sec_user_services/configuration/guide/sec_secure_copy_ps6350
_TSD_Products_Configuration_Guide_Chapter.html
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
7-55
Configuring the Switch for Secure Copy Protocol
Chapter 7 Configuring Switch-Based Authentication
7-56
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
C H A P T E R
8
Configuring IEEE 802.1x Port-Based
Authentication
This chapter describes how to configure IEEE 802.1x port-based authentication on the switch.
IEEE 802.1x authentication prevents unauthorized devices (clients) from gaining access to the network.
Note For complete syntax and usage information for the commands used in this chapter, see the command reference for this release and the “RADIUS Commands” section in the Cisco IOS Security Command
Reference, Release 12.2
from the Cisco.com page under Documentation > Cisco IOS Software > 12.2
Mainline > Command References
The switch also supports Cisco TrustSec Security Group Tag (SCT) Exchange Protocol (SXP). This feature supports security group access control lists (SGACLs), which define ACL policies for a group of devices instead of an IP address. The SXP control protocol allows tagging packets with SCTs without a hardware upgrade, and runs between access layer devices at the Cisco TrustSec domain edge and distribution layer devices within the Cisco TrustSec domain. The blade switches operate as access layer switches in the Cisco TrustSec network.
For more information about Cisco TrustSec, see the “Cisco TrustSec Switch Configuration Guide” at this
URL: http://www.cisco.com/en/US/docs/switches/lan/trustsec/configuration/guide/trustsec.html
The sections on SXP define the capabilities supported on the blade switches.
This chapter consists of these sections:
•
•
•
Understanding IEEE 802.1x Port-Based Authentication, page 8-1
Configuring 802.1x Authentication, page 8-33
Displaying 802.1x Statistics and Status, page 8-66
Understanding IEEE 802.1x Port-Based Authentication
The IEEE 802.1x standard defines a client-server-based access control and authentication protocol that prevents unauthorized clients from connecting to a LAN through publicly accessible ports unless they are properly authenticated. The authentication server authenticates each client connected to a switch port before making available any services offered by the switch or the LAN.
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-1 OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
Until the client is authenticated, 802.1x access control allows only Extensible Authentication Protocol over LAN (EAPOL), Cisco Discovery Protocol (CDP), and Spanning Tree Protocol (STP) traffic through the port to which the client is connected. After authentication is successful, normal traffic can pass through the port.
These sections describe IEEE 802.1x port-based authentication:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Authentication Process, page 8-4
Authentication Initiation and Message Exchange, page 8-6
Ports in Authorized and Unauthorized States, page 8-11
Authentication Manager, page 8-8
802.1x Accounting Attribute-Value Pairs, page 8-15
802.1x Readiness Check, page 8-16
802.1x Authentication with VLAN Assignment, page 8-16
802.1x Authentication with Per-User ACLs, page 8-18
•
•
•
•
802.1x Authentication with Restricted VLAN, page 8-23
802.1x Authentication with Inaccessible Authentication Bypass, page 8-24
802.1x User Distribution, page 8-25
•
•
•
•
802.1x Authentication with Voice VLAN Ports, page 8-26
802.1x Authentication with Port Security, page 8-26
802.1x Authentication with Downloadable ACLs and Redirect URLs, page 8-19
VLAN ID-based MAC Authentication, page 8-21
•
•
•
•
802.1x Authentication with Wake-on-LAN, page 8-27
802.1x Authentication with MAC Authentication Bypass, page 8-27
Flexible Authentication Ordering, page 8-29
Open1x Authentication, page 8-29
•
802.1x Supplicant and Authenticator Switches with Network Edge Access Topology (NEAT), page 8-31
8-2
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
Device Roles
With IEEE 802.1x port-based authentication, the devices in the network have specific roles as shown in
Figure 8-1 IEEE 802.1x Device Roles
Authentication server
(RADIUS)
Workstations
(clients)
OL-27326-01
• Client —the device (workstation) that requests access to the LAN and switch services and responds to requests from the switch. The workstation must be running IEEE 802.1x-compliant client software such as that offered in the Microsoft Windows XP operating system. (The client is the supplicant in the IEEE 802.1x standard.)
Note To resolve Windows XP network connectivity and IEEE 802.1x authentication issues, read the Microsoft Knowledge Base article at this URL: http://support.microsoft.com/support/kb/articles/Q303/5/97.ASP
•
•
Authentication server —performs the actual authentication of the client. The authentication server validates the identity of the client and notifies the switch whether or not the client is authorized to access the LAN and switch services. Because the switch acts as the proxy, the authentication service is transparent to the client. In this release, the RADIUS security system with Extensible
Authentication Protocol (EAP) extensions is the only supported authentication server. It is available in Cisco Secure Access Control Server Version 3.0 or later. RADIUS operates in a client/server model in which secure authentication information is exchanged between the RADIUS server and one or more RADIUS clients.
Switch (edge switch or wireless access point)—controls the physical access to the network based on the authentication status of the client. The switch acts as an intermediary (proxy) between the client and the authentication server, requesting identity information from the client, verifying that information with the authentication server, and relaying a response to the client. The switch includes the RADIUS client, which is responsible for encapsulating and decapsulating the EAP frames and interacting with the authentication server. (The switch is the authenticator in the IEEE 802.1x standard.)
When the switch receives EAPOL frames and relays them to the authentication server, the Ethernet header is stripped, and the remaining EAP frame is re-encapsulated in the RADIUS format. The
EAP frames are not modified during encapsulation, and the authentication server must support EAP within the native frame format. When the switch receives frames from the authentication server, the server’s frame header is removed, leaving the EAP frame, which is then encapsulated for Ethernet and sent to the client.
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-3
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
The devices that can act as intermediaries include the Catalyst 3750-E, Catalyst 3560-E, Catalyst
3750, Catalyst 3560, Catalyst 3550, Catalyst 2970, Catalyst 2960, Cisco Catalyst Blade Switch 3030 for Dell, Catalyst 2955, Catalyst 2950, Catalyst 2940 switches, or a wireless access point. These devices must be running software that supports the RADIUS client and IEEE 802.1x authentication.
Authentication Process
When IEEE 802.1x port-based authentication is enabled and the client supports IEEE 802.1x-compliant client software, these events occur:
• If the client identity is valid and the IEEE 802.1x authentication succeeds, the switch grants the client access to the network.
•
•
If IEEE 802.1x authentication times out while waiting for an EAPOL message exchange and MAC authentication bypass is enabled, the switch can use the client MAC address for authorization. If the client MAC address is valid and the authorization succeeds, the switch grants the client access to the network. If the client MAC address is invalid and the authorization fails, the switch assigns the client to a guest VLAN that provides limited services if a guest VLAN is configured.
If the switch gets an invalid identity from an IEEE 802.1x-capable client and a restricted VLAN is specified, the switch can assign the client to a restricted VLAN that provides limited services.
• If the RADIUS authentication server is unavailable (down) and inaccessible authentication bypass is enabled, the switch grants the client access to the network by putting the port in the critical-authentication state in the RADIUS-configured or the user-specified access VLAN.
Note Inaccessible authentication bypass is also referred to as critical authentication or the AAA fail policy.
8-4
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
Figure 8-2 shows the authentication process.
If Multi Domain Authentication (MDA) is enabled on a port, this flow can be used with some exceptions that are applicable to voice authorization. For more information on MDA, see
Authentication” section on page 8-30 .
Figure 8-2 Authentication Flowchart
Start
User does not have a certificate but the system previously logged on to the network using a computer certificate.
Assign the port to a guest VLAN.
Is the client IEEE
802.1x capable?
Yes
No
IEEE 802.1x authentication process times out.
Start IEEE 802.1x port-based authentication.
Client identity is invalid
Client identity is valid
The switch gets an
EAPOL message, and the EAPOL message exchange begins.
Is MAC authentication bypass enabled? 1
Yes
Use MAC authentication bypass.
1
Client MAC address identity is valid.
Client MAC address identity is invalid.
No
Assign the port to a restricted VLAN.
Assign the port to a VLAN.
Assign the port to a VLAN.
Assign the port to a guest VLAN.
1
Done Done Done
Done Done
All authentication servers are down.
All authentication servers are down.
Use inaccessible authentication bypass
(critical authentication) to assign the critical port to a VLAN.
1 = This occurs if the switch does not detect EAPOL packets from the client.
Done
The switch re-authenticates a client when one of these situations occurs:
• Periodic re-authentication is enabled, and the re-authentication timer expires.
You can configure the re-authentication timer to use a switch-specific value or to be based on values from the RADIUS server.
After IEEE 802.1x authentication using a RADIUS server is configured, the switch uses timers based on the Session-Timeout RADIUS attribute (Attribute[27]) and the Termination-Action
RADIUS attribute (Attribute [29]).
The Session-Timeout RADIUS attribute (Attribute[27]) specifies the time after which re-authentication occurs.
The Termination-Action RADIUS attribute (Attribute [29]) specifies the action to take during re-authentication. The actions are Initialize and ReAuthenticate . When the Initialize action is set (the attribute value is DEFAULT ), the IEEE 802.1x session ends, and connectivity is lost during re-authentication. When the ReAuthenticate action is set (the attribute value is RADIUS-Request), the session is not affected during re-authentication.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-5
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
• You manually re-authenticate the client by entering the dot1x re-authenticate interface interface-id privileged EXEC command.
Authentication Initiation and Message Exchange
During IEEE 802.1x authentication, the switch or the client can initiate authentication. If you enable authentication on a port by using the authentication port-control auto or dot1x port-control auto interface configuration command, the switch initiates authentication when the link state changes from down to up or periodically as long as the port remains up and unauthenticated. The switch sends an
EAP-request/identity frame to the client to request its identity. Upon receipt of the frame, the client responds with an EAP-response/identity frame.
However, if during bootup, the client does not receive an EAP-request/identity frame from the switch, the client can initiate authentication by sending an EAPOL-start frame, which prompts the switch to request the client’s identity.
Note If IEEE 802.1x authentication is not enabled or supported on the network access device, any EAPOL frames from the client are dropped. If the client does not receive an EAP-request/identity frame after three attempts to start authentication, the client sends frames as if the port is in the authorized state. A port in the authorized state effectively means that the client has been successfully authenticated. For more information, see the
“Ports in Authorized and Unauthorized States” section on page 8-11
.
When the client supplies its identity, the switch begins its role as the intermediary, passing EAP frames between the client and the authentication server until authentication succeeds or fails. If the authentication succeeds, the switch port becomes authorized. If the authentication fails, authentication can be retried, the port might be assigned to a VLAN that provides limited services, or network access is not granted. For more information, see the
“Ports in Authorized and Unauthorized States” section on page 8-11 .
The specific exchange of EAP frames depends on the authentication method being used.
shows a message exchange initiated by the client when the client uses the One-Time-Password (OTP) authentication method with a RADIUS server.
8-6
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Figure 8-3
Client
Message Exchange
Blade Switch
Understanding IEEE 802.1x Port-Based Authentication
Authentication server
(RADIUS)
EAPOL-Start
EAP-Request/Identity
EAP-Response/Identity
EAP-Request/OTP
EAP-Response/OTP
EAP-Success
RADIUS Access-Request
RADIUS Access-Challenge
RADIUS Access-Request
RADIUS Access-Accept
Port Authorized
EAPOL-Logoff
Port Unauthorized
If IEEE 802.1x authentication times out while waiting for an EAPOL message exchange and MAC authentication bypass is enabled, the switch can authorize the client when the switch detects an Ethernet packet from the client. The switch uses the MAC address of the client as its identity and includes this information in the RADIUS-access/request frame that is sent to the RADIUS server. After the server sends the switch the RADIUS-access/accept frame (authorization is successful), the port becomes authorized. If authorization fails and a guest VLAN is specified, the switch assigns the port to the guest
VLAN. If the switch detects an EAPOL packet while waiting for an Ethernet packet, the switch stops the MAC authentication bypass process and stops IEEE 802.1x authentication.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-7
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
shows the message exchange during MAC authentication bypass.
Figure 8-4
Client
Message Exchange During MAC Authentication Bypass
Switch
Authentication server
(RADIUS)
EAPOL Request/Identity
EAPOL Request/Identity
EAPOL Request/Identity
Ethernet packet RADIUS Access/Request
RADIUS Access/Accept
Authentication Manager
In Cisco IOS Release 12.2(46)SE and earlier, you could not use the same authorization methods, including
CLI commands and messages, on this switch and also on other network devices, such as a Catalyst 6000.
You had to use separate authentication configurations. Cisco IOS Release 12.2(50)SE and later supports the same authorization methods on all Catalyst switches in a network.
Cisco IOS Release 12.2(55)SE supports filtering verbose system messages from the authentication manager. For details, see the
“Authentication Manager CLI Commands” section on page 8-10
.
•
Port-Based Authentication Methods, page 8-9
•
•
Per-User ACLs and Filter-Ids, page 8-9
Authentication Manager CLI Commands, page 8-10
8-8
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
Port-Based Authentication Methods
Table 8-1 802.1x Features
Authentication method
802.1x
MAC authentication bypass
Standalone web authentication
NAC Layer 2 IP validation
4
Web authentication as fallback method
4
Mode
Single host
VLAN assignment
Per-user ACL
Filter-ID attribute
Multiple host MDA
1
VLAN assignment VLAN assignment
Per-user ACL
2
Filter-Id attribute
2
Multiple
Authentication
2 2
Per-user ACL
2
Filter-Id attribute
2
Downloadable
ACL
2
Redirect URL
2
Downloadable
ACL
3
Redirect URL
2
VLAN assignment
Per-user ACL
Filter-ID attribute
Redirect URL
Proxy ACL
Filter-Id attribute
Downloadable
ACL
2
2
VLAN assignment
Downloadable
ACL
2
Redirect URL
2
VLAN assignment
Per-user ACL
2
Filter-Id attribute
2
Downloadable
ACL
2
Downloadable
ACL
2
Redirect URL
2
Redirect URL
2
Proxy ACL, Filter-Id attribute, downloadable ACL
2
Filter-Id attribute
2
Filter-Id attribute
2
Filter-Id attribute
2
Downloadable ACL Downloadable ACL Downloadable ACL
Redirect URL
Proxy ACL
Filter-Id attribute
Downloadable
ACL
2
2
Redirect URL
Proxy ACL
Filter-Id attribute
Downloadable
ACL
2
2
Per-user ACL
2
Filter-Id attribute
2
Downloadable
ACL
2
Redirect URL
2
Filter-Id attribute
2
Downloadable
ACL
2
Redirect URL
2
Proxy ACL
2
Filter-Id attribute
2
Downloadable
ACL
2
1.
MDA = Multidomain authentication.
2.
Also referred to as multiauth .
3.
Supported in Cisco IOS Release 12.2(50)SE and later.
4.
For clients that do not support 802.1x authentication.
Per-User ACLs and Filter-Ids
In releases earlier than Cisco IOS Release 12.2(50)SE, an ACL configured on the switch is not compatible with an ACL configured on another device running Cisco IOS software, such as a
Catalyst 6000 switch.
In Cisco IOS Release 12.2(50)SE or later, the ACLs configured on the switch are compatible with other devices running Cisco IOS release.
You can only set any as the source in the ACL.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-9
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
Note For any ACL configured for multiple-host mode, the source portion of statement must be any . (For example, permit icmp any host 10.10.1.1
.)
Authentication Manager CLI Commands
The authentication-manager interface-configuration commands control all the authentication methods, such as 802.1x, MAC authentication bypass, and web authentication. The authentication manager commands determine the priority and order of authentication methods applied to a connected host.
The authentication manager commands control generic authentication features, such as host-mode, violation mode, and the authentication timer. Generic authentication commands include the authentication host-mode , authentication violation , and authentication timer interface configuration commands.
802.1x-specific commands begin with the dot1x keyword.
For example, the authentication port-control auto interface configuration command enables authentication on an interface. However, the dot1x system-authentication control g lobal configuration command only globally enables or disables 802.1x authentication.
Note If 802.1x authentication is globally disabled, other authentication methods are still enabled on that port, such as web authentication.
The authentication manager commands provide the same functionality as earlier 802.1x commands.
Authentication Manager Commands and Earlier 802.1x Commands Table 8-2
The authentication manager commands in Cisco IOS
Release 12.2(50)SE or later authentication control-direction
{both | in } authentication event authentication fallback fallback-profile authentication host-mode
[ multi-auth | multi-domain multi-host | single-host ] authentication order authentication periodic
|
The equivalent 802.1x commands in
Cisco IOS Release 12.2(46)SE and earlier Description dot1x control-direction { both | in } dot1x auth-fail vlan
Enable 802.1x authentication with the wake-on-LAN (WoL) feature, and configure the port control as unidirectional or bidirectional.
Enable the restricted VLAN on a port.
dot1x critical (interface configuration) dot1x guest-vlan6 dot1x fallback fallback-profile dot1x host-mode { single-host | multi-host | multi-domain }
Enable the inaccessible-authentication-bypass feature.
Specify an active VLAN as an 802.1x guest
VLAN.
Configure a port to use web authentication as a fallback method for clients that do not support
802.1x authentication.
Allow a single host (client) or multiple hosts on an 802.1x-authorized port.
dot1x mac-auth-bypass dot1x reauthentication
Enable the MAC authentication bypass feature.
Enable periodic re-authentication of the client.
8-10
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
Table 8-2 Authentication Manager Commands and Earlier 802.1x Commands (continued)
The authentication manager commands in Cisco IOS
Release 12.2(50)SE or later
The equivalent 802.1x commands in
Cisco IOS Release 12.2(46)SE and earlier authentication port-control { auto
| force-authorized | f orce-un authorized } dot1x port-control {auto | force-authorized | force-unauthorized} dot1x timeout authentication timer authentication violation { protect | restrict | shutdown } dot1x violation-mode
| restrict | protect }
{ shutdown
Description
Enable manual control of the authorization state of the port.
Set the 802.1x timers.
Configure the violation modes that occur when a new device connects to a port or when a new device connects to a port after the maximum number of devices are connected to that port.
show authentication show dot1x Display 802.1x statistics, administrative status, and operational status for the switch or for the specified port.
Beginning with Cisco IOS Release 12.2(55)SE, you can filter out verbose system messages generated by the authentication manager. The filtered content typically relates to authentication success. You can also filter verbose messages for 802.1x authentication and MAB authentication. There is a separate command for each authentication method:
•
•
The no authentication logging verbose global configuration command filters verbose messages from the authentication manager.
The no dot1x logging verbose global configuration command filters 802.1x authentication verbose messages.
• The no mab logging verbose global configuration command filters MAC authentication bypass
(MAB) verbose messages
For more information, see the command reference for this release.
Ports in Authorized and Unauthorized States
During IEEE 802.1x authentication, depending on the switch port state, the switch can grant a client access to the network. The port starts in the unauthorized state. While in this state, the port that is not configured as a voice VLAN port disallows all ingress and egress traffic except for IEEE 802.1x authentication, CDP, and STP packets. When a client is successfully authenticated, the port changes to the authorized state, allowing all traffic for the client to flow normally. If the port is configured as a voice
VLAN port, the port allows VoIP traffic and IEEE 802.1x protocol packets before the client is successfully authenticated.
If a client that does not support IEEE 802.1x authentication connects to an unauthorized IEEE 802.1x port, the switch requests the client’s identity. In this situation, the client does not respond to the request, the port remains in the unauthorized state, and the client is not granted access to the network.
In contrast, when an IEEE 802.1x-enabled client connects to a port that is not running the IEEE 802.1x standard, the client initiates the authentication process by sending the EAPOL-start frame. When no response is received, the client sends the request for a fixed number of times. Because no response is received, the client begins sending frames as if the port is in the authorized state.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-11
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
You control the port authorization state by using the dot1x port-control interface configuration command and these keywords:
•
• force-authorized —disables IEEE 802.1x authentication and causes the port to change to the authorized state without any authentication exchange required. The port sends and receives normal traffic without IEEE 802.1x-based authentication of the client. This is the default setting.
force-unauthorized —causes the port to remain in the unauthorized state, ignoring all attempts by the client to authenticate. The switch cannot provide authentication services to the client through the port.
• auto —enables IEEE 802.1x authentication and causes the port to begin in the unauthorized state, allowing only EAPOL frames to be sent and received through the port. The authentication process begins when the link state of the port changes from down to up or when an EAPOL-start frame is received. The switch requests the identity of the client and begins relaying authentication messages between the client and the authentication server. Each client attempting to access the network is uniquely identified by the switch by using the client MAC address.
If the client is successfully authenticated (receives an Accept frame from the authentication server), the port state changes to authorized, and all frames from the authenticated client are allowed through the port. If the authentication fails, the port remains in the unauthorized state, but authentication can be retried. If the authentication server cannot be reached, the switch can resend the request. If no response is received from the server after the specified number of attempts, authentication fails, and network access is not granted.
When a client logs off, it sends an EAPOL-logoff message, causing the switch port to change to the unauthorized state.
If the link state of a port changes from up to down, or if an EAPOL-logoff frame is received, the port returns to the unauthorized state.
802.1x Host Mode
You can configure an IEEE 802.1x port for single-host or for multiple-hosts mode. In single-host mode
The switch detects the client by sending an EAPOL frame when the port link state changes to the up state. If a client leaves or is replaced with another client, the switch changes the port link state to down, and the port returns to the unauthorized state.
In multiple-hosts mode, you can attach multiple hosts to a single IEEE 802.1x-enabled port.
shows IEEE 802.1x port-based authentication in a wireless LAN. In this mode, only one of the attached clients must be authorized for all clients to be granted network access. If the port becomes unauthorized (re-authentication fails or an EAPOL-logoff message is received), the switch denies network access to all of the attached clients. In this topology, the wireless access point is responsible for authenticating the clients attached to it, and it also acts as a client to the switch.
8-12
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Figure 8-5 Multiple Host Mode Example
Access point
Wireless clients
Understanding IEEE 802.1x Port-Based Authentication
Authentication server
(RADIUS)
Note For all host modes, the line protocol stays up before authorization when port-based authentication is configured.
802.1x Multiple Authentication Mode
Multiple-authentication (multiauth) mode allows one client on the voice VLAN and multiple authenticated clients on the data VLAN. When a hub or access point is connected to an 802.1x-enabled port, multiple-authentication mode provides enhanced security over multiple-hosts mode by requiring authentication of each connected client. For non-802.1x devices, you can use MAC authentication bypass or web authentication as the fallback method for individual host authentications to authenticate different hosts through by different methods on a single port.
Multiple-authentication mode also supports MDA functionality on the voice VLAN by assigning authenticated devices to either a data or voice VLAN, depending on the VSAs received from the authentication server.
Note When a port is in multiple-authentication mode, the guest VLAN and authentication-failed VLAN features do not activate.
Beginning with Cisco IOS Release 12.2(55)SE, you can assign a RADIUS-server-supplied VLAN in multi-auth mode, under these conditions:
• The host is the first host authorized on the port, and the RADIUS server supplies VLAN information.
•
•
Subsequent hosts are authorized with a VLAN that matches the operational VLAN.
A host is authorized on the port with no VLAN assignment, and subsequent hosts either have no
VLAN assignment, or their VLAN information matches the operational VLAN.
•
•
•
•
The first host authorized on the port has a group VLAN assignment, and subsequent hosts either have no VLAN assignment, or their group VLAN matches the group VLAN on the port. Subsequent hosts must use the same VLAN from the VLAN group as the first host. If a VLAN list is used, all hosts are subject to the conditions specified in the VLAN list.
Only one voice VLAN assignment is supported on a multi-auth port.
After a VLAN is assigned to a host on the port, subsequent hosts must have matching VLAN information or be denied access to the port.
You cannot configure a guest VLAN or an auth-fail VLAN in multi-auth mode.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-13
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
• The behavior of the critical-auth VLAN is not changed for multi-auth mode. When a host tries to authenticate and the server is not reachable, all authorized hosts are reinitialized in the configured
VLAN.
For more information about critical authentication mode and the critical VLAN, see the
Authentication with Inaccessible Authentication Bypass” section on page 8-24 .
For more information see the
“Configuring the Host Mode” section on page 8-43.
MAC Move
When a MAC address is authenticated on one switch port, that address is not allowed on another authentication manager-enabled port of the switch. If the switch detects that same MAC address on another authentication manager-enabled port, the address is not allowed.
There are situations where a MAC address might need to move from one port to another on the same switch. For example, when there is another device (for example a hub or an IP phone) between an authenticated host and a switch port, you might want to disconnect the host from the device and connect it directly to another port on the same switch.
You can globally enable MAC move so the device is reauthenticated on the new port. When a host moves to a second port, the session on the first port is deleted, and the host is reauthenticated on the new port.
MAC move is supported on all host modes. (The authenticated host can move to any port on the switch, no matter which host mode is enabled on the that port.)
When a MAC address moves from one port to another, the switch terminates the authenticated session on the original port and initiates a new authentication sequence on the new port.
The MAC move feature applies to both voice and data hosts.
Note In open authentication mode, a MAC address is immediately moved from the original port to the new port, with no requirement for authorization on the new port.
For more information see the
“Enabling MAC Move” section on page 8-44.
Multi-Domain Authentication (MDA) which allows both a data device and a voice device, such as an IP
Phone (Cisco or non-Cisco), to connect to the same switch port. For more information, see the
Multidomain Authentication” section on page 8-30 .
MAC Replace
Beginning with Cisco IOS Release 12.2(55)SE, the MAC replace feature can be configured to address the violation that occurs when a host attempts to connect to a port where another host was previously authenticated.
Note This feature does not apply to ports in multi-auth mode, because violations are not triggered in that mode. It does not apply to ports in multiple host mode, because in that mode, only the first host requires authentication.
If you configure the authentication violation interface configuration command with the replace keyword, the authentication process on a port in multi-domain mode is:
• A new MAC address is received on a port with an existing authenticated MAC address.
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-14 OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
•
•
•
The authentication manager replaces the MAC address of the current data host on the port with the new MAC address.
The authentication manager initiates the authentication process for the new MAC address.
If the authentication manager determines that the new host is a voice host, the original voice host is removed.
If a port is in open authentication mode, any new MAC address is immediately added to the MAC address table.
For more information see the
“Enabling MAC Replace” section on page 8-45
.
802.1x Accounting
The 802.1x standard defines how users are authorized and authenticated for network access but does not keep track of network usage. 802.1x accounting is disabled by default. You can enable 802.1x accounting to monitor this activity on 802.1x-enabled ports:
• User successfully authenticates.
•
•
•
•
User logs off.
Link-down occurs.
Re-authentication successfully occurs.
Re-authentication fails.
The switch does not log 802.1x accounting information. Instead, it sends this information to the
RADIUS server, which must be configured to log accounting messages.
802.1x Accounting Attribute-Value Pairs
The information sent to the RADIUS server is represented in the form of Attribute-Value (AV) pairs.
These AV pairs provide data for different applications. (For example, a billing application might require information that is in the Acct-Input-Octets or the Acct-Output-Octets attributes of a RADIUS packet.)
AV pairs are automatically sent by a switch that is configured for 802.1x accounting. Three types of
RADIUS accounting packets are sent by a switch:
• START–sent when a new user session starts
•
•
INTERIM–sent during an existing session for updates
STOP–sent when a session terminates
lists the AV pairs and when they are sent by the switch:
Table 8-3 Accounting AV Pairs
Attribute Number AV Pair Name
Attribute[1] User-Name
Attribute[4]
Attribute[5]
NAS-IP-Address
NAS-Port
Attribute[8]
Attribute[25]
Framed-IP-Address
Class
START INTERIM
Always Always
Always Always
Always Always
Never Sometimes
1
Always Always
STOP
Always
Always
Always
Sometimes
1
Always
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-15
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
Table 8-3 Accounting AV Pairs (continued)
Attribute Number AV Pair Name
Attribute[30] Called-Station-ID
Attribute[31] Calling-Station-ID
Attribute[40]
Attribute[41]
Attribute[42]
Acct-Status-Type
Acct-Delay-Time
Acct-Input-Octets
Attribute[43] Acct-Output-Octets
Attribute[44] Acct-Session-ID
Attribute[45] Acct-Authentic
Attribute[46] Acct-Session-Time
Attribute[49] Acct-Terminate-Cause
Attribute[61] NAS-Port-Type
START
Always Always
Always Always
Always
Always Always
Never
Never
Always Always
Always Always
Never
Never
Always
INTERIM
Always
Always
Always
Always
Never
Always
STOP
Always
Always
Always
Always
Always
Always
Always
Always
Always
Always
Always
1.
The Framed-IP-Address AV pair is sent only if a valid Dynamic Host Control Protocol (DHCP) binding exists for the host in the DHCP snooping bindings table.
You can view the AV pairs that are being sent by the switch by entering the debug radius accounting privileged EXEC command. For more information about this command, see the Cisco IOS Debug
Command Reference, Release 12.2 at this URL: http://www.cisco.com/en/US/docs/ios/12_2/debug/command/reference/122debug.html
For more information about AV pairs, see RFC 3580, “IEEE 802.1X Remote Authentication Dial In User
Service (RADIUS) Usage Guidelines.”
802.1x Readiness Check
The 802.1x readiness check monitors 802.1x activity on all the switch ports and displays information about the devices connected to the ports that support 802.1x. You can use this feature to determine if the devices connected to the switch ports are 802.1x-capable. You use an alternate authentication such as
MAC authentication bypass or web authentication for the devices that do not support 802.1x functionality.
This feature only works if the supplicant on the client supports a query with the NOTIFY EAP notification packet. The client must respond within the 802.1x timeout value.
For information on configuring the switch for the 802.1x readiness check, see the .
802.1x Authentication with VLAN Assignment
The RADIUS server sends the VLAN assignment to configure the switch port. The RADIUS server database maintains the username-to-VLAN mappings, assigning the VLAN based on the username of the client connected to the switch port. You can use this feature to limit network access for certain users.
8-16
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
When a voice device is authorized and the RADIUS server returned an authorized VLAN, the voice
VLAN on the port is configured to send and receive packets on the assigned voice VLAN. Voice VLAN assignment behaves the same as data VLAN assignment on multidomain authentication (MDA)-enabled ports. For more information, see the
“Using Multidomain Authentication” section on page 8-30
.
When configured on the switch and the RADIUS server, 802.1x authentication with VLAN assignment has these characteristics:
• If no VLAN is supplied by the RADIUS server or if 802.1x authentication is disabled, the port is configured in its access VLAN after successful authentication. Recall that an access VLAN is a
VLAN assigned to an access port. All packets sent from or received on this port belong to this
VLAN.
• If 802.1x authentication is enabled but the VLAN information from the RADIUS server is not valid, the port returns to the unauthorized state and remains in the configured access VLAN. This prevents ports from appearing unexpectedly in an inappropriate VLAN because of a configuration error.
Configuration errors could include specifying a VLAN for a routed port, a malformed VLAN ID, a nonexistent or internal (routed port) VLAN ID, or an attempted assignment to a voice VLAN ID.
•
•
•
•
Configuration errors could include specifying a VLAN for a routed port, a malformed VLAN ID, a nonexistent or internal (routed port) VLAN ID, an RSPAN VLAN, a shut down or suspended VLAN. In the case of a mutlidomain host port, configuration errors can also be due to an attempted assignment of a data VLAN that matches the configured or assigned voice VLAN ID (or the reverse).
If 802.1x authentication is enabled and all information from the RADIUS server is valid, the port is placed in the specified VLAN after authentication.
If the multiple-hosts mode is enabled on an 802.1x port, all hosts are placed in the same VLAN
(specified by the RADIUS server) as the first authenticated host.
Enabling port security does not impact the RADIUS server-assigned VLAN behavior.
•
If 802.1x authentication is disabled on the port, it is returned to the configured access VLAN.
If an IEEE 802.1x port is authenticated and put in the RADIUS server-assigned VLAN, any change to the port access VLAN configuration does not take effect. In the case of a multidomain host, the same applies to voice devices when the port is fully authorized with these exceptions:
–
–
If the VLAN configuration change of one device results in matching the other device configured or assigned VLAN, then authorization of all devices on the port is terminated and multidomain host mode is disabled until a valid configuration is restored where data and voice device configured VLANs no longer match.
If a voice device is authorized and is using a downloaded voice VLAN, the removal of the voice
VLAN configuration, or modifying the configuration value to dot1p or untagged results in voice device un-authorization and the disablement of multi-domain host mode.
When the port is in the force authorized, force unauthorized, unauthorized, or shutdown state, it is put into the configured access VLAN.
The 802.1x authentication with VLAN assignment feature is not supported on trunk ports, dynamic ports, or with dynamic-access port assignment through a VLAN Membership Policy Server (VMPS).
To configure VLAN assignment you need to perform these tasks:
• Enable AAA authorization by using the network keyword to allow interface configuration from the
RADIUS server.
• Enable 802.1x authentication. (The VLAN assignment feature is automatically enabled when you configure 802.1x authentication on an access port).
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-17
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
• Assign vendor-specific tunnel attributes in the RADIUS server. The RADIUS server must return these attributes to the switch:
–
–
[64] Tunnel-Type = VLAN
[65] Tunnel-Medium-Type = 802
– [81] Tunnel-Private-Group-ID = VLAN name or VLAN ID
Attribute [64] must contain the value VLAN (type 13). Attribute [65] must contain the value 802
(type 6). Attribute [81] specifies the VLAN name or VLAN ID assigned to the
IEEE 802.1x-authenticated user.
For examples of tunnel attributes, see the
“Configuring the Switch to Use Vendor-Specific RADIUS
Attributes” section on page 7-34 .
802.1x Authentication with Per-User ACLs
You can enable per-user access control lists (ACLs) to provide different levels of network access and service to an 802.1x-authenticated user. When the RADIUS server authenticates a user connected to an 802.1x port, it retrieves the ACL attributes based on the user identity and sends them to the switch.
The switch applies the attributes to the 802.1x port for the duration of the user session. The switch removes the per-user ACL configuration when the session is over, if authentication fails, or if a link-down condition occurs. The switch does not save RADIUS-specified ACLs in the running configuration. When the port is unauthorized, the switch removes the ACL from the port.
You can configure router ACLs and input port ACLs on the same switch. However, a port ACL takes precedence over a router ACL. If you apply input port ACL to an interface that belongs to a VLAN, the port ACL takes precedence over an input router ACL applied to the VLAN interface. Incoming packets received on the port to which a port ACL is applied are filtered by the port ACL. Incoming routed packets received on other ports are filtered by the router ACL. Outgoing routed packets are filtered by the router
ACL. To avoid configuration conflicts, you should carefully plan the user profiles stored on the RADIUS server.
RADIUS supports per-user attributes, including vendor-specific attributes. These vendor-specific attributes (VSAs) are in octet-string format and are passed to the switch during the authentication process. The VSAs used for per-user ACLs are inacl#< n >
for the ingress direction and outacl#< n >
for the egress direction. MAC ACLs are supported only in the ingress direction. The switch supports VSAs only in the ingress direction. It does not support port ACLs in the egress direction on Layer 2 ports. For more information, see
Chapter 33, “Configuring Network Security with ACLs.”
Use only the extended ACL syntax style to define the per-user configuration stored on the RADIUS server. When the definitions are passed from the RADIUS server, they are created by using the extended naming convention. However, if you use the Filter-Id attribute, it can point to a standard ACL.
You can use the Filter-Id attribute to specify an inbound or outbound ACL that is already configured on the switch. The attribute contains the ACL number followed by .in
for ingress filtering or .out
for egress filtering. If the RADIUS server does not allow the .in
or .out
syntax, the access list is applied to the outbound ACL by default. Because of limited support of Cisco IOS access lists on the switch, the
Filter-Id attribute is supported only for IP ACLs numbered 1 to 199 and 1300 to 2699 (IP standard and
IP extended ACLs).
Only one 802.1x-authenticated user is supported on a port. If the multiple-hosts mode is enabled on the port, the per-user ACL attribute is disabled for the associated port.
The maximum size of the per-user ACL is 4000 ASCII characters but is limited by the maximum size of
RADIUS-server per-user ACLs.
8-18
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
For examples of vendor-specific attributes, see the “Configuring the Switch to Use Vendor-Specific
RADIUS Attributes” section on page 7-34 . For more information about configuring ACLs, see
Chapter 33, “Configuring Network Security with ACLs.”
To configure per-user ACLs:
• Enable AAA authentication.
•
•
•
•
Enable AAA authorization by using the network keyword to allow interface configuration from the
RADIUS server.
Enable 802.1x authentication.
Configure the user profile and VSAs on the RADIUS server.
Configure the 802.1x port for single-host mode.
Note Per-user ACLs are supported only in single-host mode.
802.1x Authentication with Downloadable ACLs and Redirect URLs
You can download ACLs and redirect URLs from a RADIUS server to the switch during 802.1x authentication or MAC authentication bypass of the host. You can also download ACLs during web authentication.
Note A downloadable ACL is also referred to as a dACL .
If more than one host is authenticated and the host is in single-host, MDA, or multiple-authentication mode, the switch changes the source address of the ACL to the host IP address.
You can apply the ACLs and redirect URLs to all the devices connected to the 802.1x-enabled port.
If no ACLs are downloaded during 802.1x authentication, the switch applies the static default ACL on the port to the host. On a voice VLAN port, the switch applies the ACL only to the phone.
Beginning with Cisco IOS Release 12.2(55)SE, if there is no static ACL on a port, a dynamic auth-default ACL is created, and policies are enforced before dACLs are downloaded and applied.
Note The auth-default-ACL does not appear in the running configuration.
The auth-default ACL is created when at least one host with an authorization policy is detected on the port. The auth-default ACL is removed from the port when the last authenticated session ends. You can configure the auth-default ACL by using the ip access-list extended auth-default-acl global configuration command.
Note The auth-default-ACL does not support Cisco Discovery Protocol (CDP) bypass in the single host mode.
You must configure a static ACL on the interface to support CDP bypass.
The 802.1x and MAB authentication methods support two authentication modes, open and closed . If there is no static ACL on a port in closed authentication mode:
• An auth-default-ACL is created.
• The auth-default-ACL allows only DHCP traffic until policies are enforced.
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01 8-19
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
•
•
When the first host authenticates, the authorization policy is applied without IP address insertion.
• When a second host is detected, the policies for the first host are refreshed, and policies for the first and subsequent sessions are enforced with IP address insertion.
If there is no static ACL on a port in open authentication mode:
• An auth-default-ACL-OPEN is created and allows all traffic.
Policies are enforced with IP address insertion to prevent security breaches.
• Web authentication is subject to the auth-default-ACL-OPEN.
To control access for hosts with no authorization policy, you can configure a directive. The supported values for the directive are open and default . When you configure the open directive, all traffic is allowed. The default directive subjects traffic to the access provided by the port. You can configure the directive either in the user profile on the AAA server or on the switch. To configure the directive on the
AAA server, use the authz-directive =<open/default> global command. To configure the directive on the switch, use the epm access-control open global configuration command.
Note The default value of the directive is default .
If a host falls back to web authentication on a port without a configured ACL:
•
•
If the port is in open authentication mode, the auth-default-ACL-OPEN is created.
If the port is in closed authentication mode, the auth-default-ACL is created.
The access control entries (ACEs) in the fallback ACL are converted to per-user entries. If the configured fallback profile does not include a fallback ACL, the host is subject to the auth-default-ACL associated with the port.
Note If you use a custom logo with web authentication and it is stored on an external server, the port ACL must allow access to the external server before authentication. You must either configure a static port
ACL or change the auth-default-ACL to provide appropriate access to the external server.
Cisco Secure ACS and Attribute-Value Pairs for the Redirect URL
The switch uses these cisco-av-pair VSAs:
•
• url-redirect is the HTTP to HTTPS URL.
url-redirect-acl is the switch ACL name or number.
The switch uses the CiscoSecure-Defined-ACL AV pair to intercept an HTTP or HTTPS request from the endpoint device. The switch then forwards the client web browser to the specified redirect address.
The url-redirect AV pair on the Cisco Secure ACS contains the URL to which the web browser is redirected. The url-redirect-acl AV pair contains the name or number of an ACL that specifies the HTTP or HTTPS traffic to redirect. Traffic that matches a permit ACE in the ACL is redirected.
Note Define the URL redirect ACL and the default port ACL on the switch.
If a redirect URL configured for a client on the authentication server, a default port ACL on the connected client switch port must also be configured
8-20
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
Cisco Secure ACS and Attribute-Value Pairs for Downloadable ACLs
You can set the CiscoSecure-Defined-ACL Attribute-Value (AV) pair on the Cisco Secure ACS with the
RADIUS cisco-av-pair vendor-specific attributes (VSAs). This pair specifies the names of the downloadable ACLs on the Cisco Secure ACS with the #ACL#-IP-name-number attribute.
• The name is the ACL name.
• The number is the version number (for example, 3f783768).
If a downloadable ACL is configured for a client on the authentication server, a default port ACL on the connected client switch port must also be configured.
If the default ACL is configured on the switch and the Cisco Secure ACS sends a host-access-policy to the switch, it applies the policy to traffic from the host connected to a switch port. If the policy does not apply, the switch applies the default ACL. If the Cisco Secure ACS sends the switch a downloadable
ACL, this ACL takes precedence over the default ACL that is configured on the switch port. However, if the switch receives an host access policy from the Cisco Secure ACS but the default ACL is not configured, the authorization failure is declared.
For configuration details, see the “ “Authentication Manager” section on page 8-8 and the
802.1x Authentication with Downloadable ACLs and Redirect URLs” section on page 8-61 .
VLAN ID-based MAC Authentication
You can use VLAN ID-based MAC authentication if you wish to authenticate hosts based on a static
VLAN ID instead of a downloadable VLAN. When you have a static VLAN policy configured on your switch, VLAN information is sent to an IAS (Microsoft) RADIUS server along with the MAC address of each host for authentication. The VLAN ID configured on the connected port is used for MAC authentication. By using VLAN ID-based MAC authentication with an IAS server, you can have a fixed number of VLANs in the network.
The feature also limits the number of VLANs monitored and handled by STP.The network can be managed as a fixed VLAN.
Note This feature is not supported on Cisco ACS Server. (The ACS server ignores the sent VLAN-IDs for new hosts and only authenticates based on the MAC address.)
For configuration information, see the
“Configuring VLAN ID-based MAC Authentication” section on page 8-64
. Additional configuration is similar MAC authentication bypass, as described in the
“Configuring MAC Authentication Bypass” section on page 8-57 .
802.1x Authentication with Guest VLAN
You can configure a guest VLAN for each 802.1x port on the switch to provide limited services to clients, such as downloading the 802.1x client. These clients might be upgrading their system for 802.1x authentication, and some hosts, such as Windows 98 systems, might not be IEEE 802.1x-capable.
When you enable a guest VLAN on an 802.1x port, the switch assigns clients to a guest VLAN when the switch does not receive a response to its EAP request/identity frame or when EAPOL packets are not sent by the client. The port is automatically set to multi-host mode.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-21
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
The switch maintains the EAPOL packet history. If an EAPOL packet is detected on the interface during the lifetime of the link, the switch determines that the device connected to that interface is an
IEEE 802.1x-capable supplicant, and the interface does not change to the guest VLAN state. EAPOL history is cleared if the interface link status goes down. If no EAPOL packet is detected on the interface, the interface changes to the guest VLAN state.
If the switch is trying to authorize an 802.1x-capable voice device and the AAA server is unavailable, the authorization attempt fails, but the detection of the EAPOL packet is saved in the EAPOL history.
When the AAA server becomes available, the switch authorizes the voice device. However, the switch no longer allows other devices access to the guest VLAN.
To prevent this situation, use one of these command sequences:
•
•
Enter the authentication event no-response action authorize vlan vlan-id interface configuration command to allow access to the guest VLAN.
Enter the shutdown interface configuration command followed by the no shutdown interface configuration command to restart the port.
If devices send EAPOL packets to the switch during the lifetime of the link, the switch does not allow clients that fail authentication access to the guest VLAN.
Note If an EAPOL packet is detected after the interface has changed to the guest VLAN, the interface reverts to an unauthorized state, and 802.1x authentication restarts.
Any number of 802.1x-incapable clients are allowed access when the switch port is moved to the guest
VLAN. If an 802.1x-capable client joins the same port on which the guest VLAN is configured, the port is put into the unauthorized state in the user-configured access VLAN, and authentication is restarted.
Guest VLANs are supported on 802.1x ports in single host, multiple host, or multi-domain modes.
You can configure any active VLAN except an RSPAN VLAN, a private VLAN, or a voice VLAN as an
802.1x guest VLAN. The guest VLAN feature is not supported on internal VLANs (routed ports) or trunk ports; it is supported only on access ports.
The switch supports MAC authentication bypass in Cisco IOS Release 12.2(25)SEE and later. When
MAC authentication bypass is enabled on an 802.1x port, the switch can authorize clients based on the client MAC address when IEEE 802.1x authentication times out while waiting for an EAPOL message exchange. After detecting a client on an 802.1x port, the switch waits for an Ethernet packet from the client. The switch sends the authentication server a RADIUS-access/request frame with a username and password based on the MAC address. If authorization succeeds, the switch grants the client access to the network. If authorization fails, the switch assigns the port to the guest VLAN if one is specified. For more information, see the
“802.1x Authentication with MAC Authentication Bypass” section on page 8-27 .
For more information, see the
“Configuring a Guest VLAN” section on page 8-50 .
8-22
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
802.1x Authentication with Restricted VLAN
You can configure a restricted VLAN (also referred to as an authentication failed VLAN ) for each
IEEE 802.1x port on a switch to provide limited services to clients that cannot access the guest VLAN.
These clients are 802.1x-compliant and cannot access another VLAN because they fail the authentication process. A restricted VLAN allows users without valid credentials in an authentication server (typically, visitors to an enterprise) to access a limited set of services. The administrator can control the services available to the restricted VLAN.
Note You can configure a VLAN to be both the guest VLAN and the restricted VLAN if you want to provide the same services to both types of users.
Without this feature, the client attempts and fails authentication indefinitely, and the switch port remains in the spanning-tree blocking state. With this feature, you can configure the switch port to be in the restricted VLAN after a specified number of authentication attempts (the default value is 3 attempts).
The authenticator counts the failed authentication attempts for the client. When this count exceeds the configured maximum number of authentication attempts, the port moves to the restricted VLAN. The failed attempt count increments when the RADIUS server replies with either an EAP failure or an empty response without an EAP packet. When the port moves into the restricted VLAN, the failed attempt counter resets.
Users who fail authentication remain in the restricted VLAN until the next re-authentication attempt. A port in the restricted VLAN tries to re-authenticate at configured intervals (the default is 60 seconds). If re-authentication fails, the port remains in the restricted VLAN. If re-authentication is successful, the port moves either to the configured VLAN or to a VLAN sent by the RADIUS server. You can disable re-authentication. If you do this, the only way to restart the authentication process is for the port to receive a link dow n or EAP logoff event. We recommend that you keep re-authentication enabled if a client might connect through a hub. When a client disconnects from the hub, the port might not receive the link down or EAP logoff event.
After a port moves to the restricted VLAN, a simulated EAP success message is sent to the client. This prevents clients from indefinitely attempting authentication. Some clients (for example, devices running
Windows XP) cannot implement DHCP without EAP success.
Restricted VLANs are supported only on 802.1x ports in single-host mode and on Layer 2 ports.
You can configure any active VLAN except an RSPAN VLAN, a primary private VLAN, or a voice
VLAN as an 802.1x restricted VLAN. The restricted VLAN feature is not supported on internal VLANs
(routed ports) or trunk ports; it is supported only on access ports.
Other security features such as dynamic ARP Inspection, DHCP snooping, and IP source guard can be configured independently on a restricted VLAN.
For more information, see the
“Configuring a Restricted VLAN” section on page 8-51 .
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-23
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
802.1x Authentication with Inaccessible Authentication Bypass
Use the inaccessible authentication bypass feature, also referred to as critical authentication or the AAA fail policy, when the switch cannot reach the configured RADIUS servers and new hosts cannot be authenticated. You can configure the switch to connect those hosts to critical ports .
When a new host tries to connect to the critical port, that host is moved to a user-specified access VLAN, the critical VLAN . The administrator gives limited authentication to the hosts.
When the switch tries to authenticate a host connected to a critical port, the switch checks the status of the configured RADIUS server. If a server is available, the switch can authenticate the host. However, if all the RADIUS servers are unavailable, the switch grants network access to the host and puts the port in the critical-authentication state, which is a special case of the authentication state.
Support on Multiple-Authentication Ports
When a port is configured on any host mode and the AAA server is unavailable, the port is then configured to multi-host mode and moved to the critical VLAN. To support this inaccessible bypass on multiple-authentication (multiauth) ports, use the authentication event server dead action reinitialize vlan vlan-id command. When a new host tries to connect to the critical port, that port is reinitialized and all the connected hosts are moved to the user-specified access VLAN.
This command is supported on all host modes.
Authentication Results
The behavior of the inaccessible authentication bypass feature depends on the authorization state of the port:
• If the port is unauthorized when a host connected to a critical port tries to authenticate and all servers are unavailable, the switch puts the port in the critical-authentication state in the
RADIUS-configured or user-specified access VLAN.
•
•
If the port is already authorized and reauthentication occurs, the switch puts the critical port in the critical-authentication state in the current VLAN, which might be the one previously assigned by the RADIUS server.
If the RADIUS server becomes unavailable during an authentication exchange, the current exchange times out, and the switch puts the critical port in the critical-authentication state during the next authentication attempt.
You can configure the critical port to reinitialize hosts and move them out of the critical VLAN when the RADIUS server is again available. When this is configured, all critical ports in the critical-authentication state are automatically re-authenticated. For more information, see the command reference for this release and the
“Configuring the Inaccessible Authentication Bypass Feature” section on page 8-53
.
Feature Interactions
Inaccessible authentication bypass interacts with these features:
• Guest VLAN—Inaccessible authentication bypass is compatible with guest VLAN. When a guest
VLAN is enabled on 8021.x port, the features interact as follows:
8-24
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
•
•
•
•
•
–
–
–
If at least one RADIUS server is available, the switch assigns a client to a guest VLAN when the switch does not receive a response to its EAP request/identity frame or when EAPOL packets are not sent by the client.
If all the RADIUS servers are not available and the client is connected to a critical port, the switch authenticates the client and puts the critical port in the critical-authentication state in the
RADIUS-configured or user-specified access VLAN.
If all the RADIUS servers are not available and the client is not connected to a critical port, the switch might not assign clients to the guest VLAN if one is configured.
– If all the RADIUS servers are not available and if a client is connected to a critical port and was previously assigned to a guest VLAN, the switch keeps the port in the guest VLAN.
Restricted VLAN—If the port is already authorized in a restricted VLAN and the RADIUS servers are unavailable, the switch puts the critical port in the critical-authentication state in the restricted
VLAN.
802.1x accounting—Accounting is not affected if the RADIUS servers are unavailable.
Private VLAN—You can configure inaccessible authentication bypass on a private VLAN host port.
The access VLAN must be a secondary private VLAN.
Voice VLAN—Inaccessible authentication bypass is compatible with voice VLAN, but the
RADIUS-configured or user-specified access VLAN and the voice VLAN must be different.
Remote Switched Port Analyzer (RSPAN)—Do not configure an RSPAN VLAN as the
RADIUS-configured or user-specified access VLAN for inaccessible authentication bypass.
802.1x User Distribution
You can configure 802.1x user distribution to load-balance users with the same group name across multiple different VLANs.
The VLANs are either supplied by the RADIUS server or configured through the switch CLI under a
VLAN group name.
•
•
Configure the RADIUS server to send more than one VLAN name for a user. The multiple VLAN names can be sent as part of the response to the user. The 802.1x user distribution tracks all the users in a particular VLAN and achieves load balancing by moving the authorized user to the least populated VLAN.
Configure the RADIUS server to send a VLAN group name for a user. The VLAN group name can be sent as part of the response to the user. You can search for the selected VLAN group name among the VLAN group names that you configured by using the switch CLI. If the VLAN group name is found, the corresponding VLANs under this VLAN group name are searched to find the least populated VLAN. Load balancing is achieved by moving the corresponding authorized user to that
VLAN.
Note The RADIUS server can send the VLAN information in any combination of VLAN-IDs, VLAN names, or VLAN groups.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-25
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
802.1x User Distribution Configuration Guidelines
•
•
•
•
Confirm that at least one VLAN is mapped to the VLAN group.
You can map more than one VLAN to a VLAN group.
You can modify the VLAN group by adding or deleting a VLAN.
When you clear an existing VLAN from the VLAN group name, none of the authenticated ports in the VLAN are cleared, but the mappings are removed from the existing VLAN group.
• If you clear the last VLAN from the VLAN group name, the VLAN group is cleared.
• You can clear a VLAN group even when the active VLANs are mapped to the group. When you clear a VLAN group, none of the ports or users that are in the authenticated state in any VLAN within the group are cleared, but the VLAN mappings to the VLAN group are cleared.
For more information, see the
“Configuring 802.1x User Distribution” section on page 8-56 .
802.1x Authentication with Voice VLAN Ports
A voice VLAN port is a special access port associated with two VLAN identifiers:
• VVID to carry voice traffic to and from the IP phone. The VVID is used to configure the IP phone connected to the port.
• PVID to carry the data traffic to and from the workstation connected to the switch through the IP phone. The PVID is the native VLAN of the port.
The IP phone uses the VVID for its voice traffic, regardless of the authorization state of the port. This allows the phone to work independently of IEEE 802.1x authentication.
In single-host mode, only the IP phone is allowed on the voice VLAN. In multiple-hosts mode, additional clients can send traffic on the voice VLAN after a supplicant is authenticated on the PVID.
When multiple-hosts mode is enabled, the supplicant authentication affects both the PVID and the
VVID.
A voice VLAN port becomes active when there is a link, and the device MAC address appears after the first CDP message from the IP phone. Cisco IP phones do not relay CDP messages from other devices.
As a result, if several IP phones are connected in series, the switch recognizes only the one directly connected to it. When 802.1x authentication is enabled on a voice VLAN port, the switch drops packets from unrecognized IP phones more than one hop away.
When 802.1x authentication is enabled on a port, you cannot configure a port VLAN that is equal to a voice VLAN.
Note If you enable 802.1x authentication on an access port on which a voice VLAN is configured and to which a Cisco IP Phone is connected, the Cisco IP phone loses connectivity to the switch for up to 30 seconds.
For more information about voice VLANs, see
Chapter 14, “Configuring Voice VLAN.”
802.1x Authentication with Port Security
In general, Cisco does not recommend enabling port security when IEEE 802.1x is enabled. Since IEEE
802.1x enforces a single MAC address per port (or per VLAN when MDA is configured for IP telephony), port security is redundant and in some cases may interfere with expected IEEE 802.1x operations.
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-26 OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
802.1x Authentication with Wake-on-LAN
The 802.1x authentication with wake-on-LAN (WoL) feature allows dormant PCs to be powered when the switch receives a specific Ethernet frame, known as the magic packet . You can use this feature in environments where administrators need to connect to systems that have been powered down.
When a host that uses WoL is attached through an 802.1x port and the host powers off, the IEEE 802.1x port becomes unauthorized. The port can only receive and send EAPOL packets, and WoL magic packets cannot reach the host. When the PC is powered off, it is not authorized, and the switch port is not opened.
When the switch uses 802.1x authentication with WoL, the switch forwards traffic to unauthorized
IEEE 802.1x ports, including magic packets. While the port is unauthorized, the switch continues to block ingress traffic other than EAPOL packets. The host can receive packets but cannot send packets to other devices in the network.
Note If PortFast is not enabled on the port, the port is forced to the bidirectional state.
When you configure a port as unidirectional by using the dot1x control-direction in interface configuration command, the port changes to the spanning-tree forwarding state. The port can send packets to the host but cannot receive packets from the host.
When you configure a port as bidirectional by using the dot1x control-direction both interface configuration command, the port is access-controlled in both directions. The port does not receive packets from or send packets to the host.
802.1x Authentication with MAC Authentication Bypass
You can configure the switch to authorize clients based on the client MAC address (see
) by using the MAC authentication bypass feature. For example, you can enable this feature on
IEEE 802.1x ports connected to devices such as printers.
If 802.1x authentication times out while waiting for an EAPOL response from the client, the switch tries to authorize the client by using MAC authentication bypass.
When the MAC authentication bypass feature is enabled on an 802.1x port, the switch uses the MAC address as the client identity. The authentication server has a database of client MAC addresses that are allowed network access. After detecting a client on an 802.1x port, the switch waits for an Ethernet packet from the client. The switch sends the authentication server a RADIUS-access/request frame with a username and password based on the MAC address. If authorization succeeds, the switch grants the client access to the network. If authorization fails, the switch assigns the port to the guest VLAN if one is configured.
If an EAPOL packet is detected on the interface during the lifetime of the link, the switch determines that the device connected to that interface is an 802.1x-capable supplicant and uses 802.1x authentication (not MAC authentication bypass) to authorize the interface. EAPOL history is cleared if the interface link status goes down.
If the switch already authorized a port by using MAC authentication bypass and detects an 802.1x supplicant, the switch does not unauthorize the client connected to the port. When re-authentication occurs, the switch uses 802.1x authentication as the preferred re-authentication process if the previous session ended because the Termination-Action RADIUS attribute value is DEFAULT.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-27
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
Clients that were authorized with MAC authentication bypass can be re-authenticated. The re-authentication process is the same as that for clients that were authenticated with 802.1x. During re-authentication, the port remains in the previously assigned VLAN. If re-authentication is successful, the switch keeps the port in the same VLAN. If re-authentication fails, the switch assigns the port to the guest VLAN, if one is configured.
If re-authentication is based on the Session-Timeout RADIUS attribute (Attribute[27]) and the
Termination-Action RADIUS attribute (Attribute [29]) and if the Termination-Action RADIUS attribute
(Attribute [29]) action is Initialize, (the attribute value is DEFAULT ), the MAC authentication bypass session ends, and connectivity is lost during re-authentication. If MAC authentication bypass is enabled and the 802.1x authentication times out, the switch uses the MAC authentication bypass feature to initiate re-authorization. For more information about these AV pairs, see RFC 3580, “802.1x Remote
Authentication Dial In User Service (RADIUS) Usage Guidelines.”
MAC authentication bypass interacts with the features:
•
•
•
•
•
802.1x authentication—You can enable MAC authentication bypass only if 802.1x authentication is enabled on the port.
Guest VLAN—If a client has an invalid MAC address identity, the switch assigns the client to a guest VLAN if one is configured.
Restricted VLAN—This feature is not supported when the client connected to an IEEE 802.lx port is authenticated with MAC authentication bypass.
Port security—See the
“802.1x Authentication with Port Security” section on page 8-26
.
Voice VLAN—See the
“802.1x Authentication with Voice VLAN Ports” section on page 8-26
.
VLAN Membership Policy Server (VMPS)—IEEE802.1x and VMPS are mutually exclusive.
•
•
•
Private VLAN—You can assign a client to a private VLAN.
Network admission control (NAC) Layer 2 IP validation—This feature takes effect after an
IEEE 802.1x port is authenticated with MAC authentication bypass, including hosts in the exception list.
• Network Edge Access Topology (NEAT)—MAB and NEAT are mutually exclusive. You cannot enable MAB when NEAT is enabled on an interface, and you cannot enable NEAT when MAB is enabled on an interface.
For more configuration information, see the
“Authentication Manager” section on page 8-8
.
Cisco IOS Release 12.2(55)SE and later supports filtering of verbose MAB system messages. See the
“Authentication Manager CLI Commands” section on page 8-10
.
Network Admission Control Layer 2 802.1x Validation
In Cisco IOS Release 12.2(44)SE and later, the switch supports the Network Admission Control (NAC)
Layer 2 802.1x validation, which checks the antivirus condition or posture of endpoint systems or clients before granting the devices network access. With NAC Layer 2 802.1x validation, you can do these tasks:
•
•
Download the Session-Timeout RADIUS attribute (Attribute[27]) and the Termination-Action
RADIUS attribute (Attribute[29]) from the authentication server.
Set the number of seconds between re-authentication attempts as the value of the Session-Timeout
RADIUS attribute (Attribute[27]) and get an access policy against the client from the RADIUS server.
8-28
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
•
•
Set the action to be taken when the switch tries to re-authenticate the client by using the
Termination-Action RADIUS attribute (Attribute[29]). If the value is the DEFAULT or is not set, the session ends. If the value is RADIUS-Request, the re-authentication process starts.
View the NAC posture token, which shows the posture of the client, by using the show dot1x privileged EXEC command.
Configure secondary private VLANs as guest VLANs.
•
Configuring NAC Layer 2 802.1x validation is similar to configuring 802.1x port-based authentication except that you must configure a posture token on the RADIUS server. For information about configuring NAC Layer 2 802.1x validation, see the
“Configuring NAC Layer 2 802.1x Validation” section on page 8-58 and the
“Configuring Periodic Re-Authentication” section on page 8-45
.
For more information about NAC, see the Network Admission Control Software Configuration Guide .
For more configuration information, see the
“Authentication Manager” section on page 8-8 .
Flexible Authentication Ordering
You can use flexible authentication ordering to configure the order of methods that a port uses to authenticate a new host. MAC authentication bypass and 802.1x can be the primary or secondary authentication methods, and web authentication can be the fallback method if either or both of those authentication attempts fail. For more information see the
“Configuring Flexible Authentication
Ordering” section on page 8-64 .
Open1x Authentication
Open1x authentication allows a device access to a port before that device is authenticated. When open authentication is configured, a new host can pass traffic according to the access control list (ACL) defined on the port. After the host is authenticated, the policies configured on the RADIUS server are applied to that host.
You can configure open authentication with these scenarios:
•
•
•
•
Single-host mode with open authentication–Only one user is allowed network access before and after authentication.
MDA mode with open authentication–Only one user in the voice domain and one user in the data domain are allowed.
Multiple-hosts mode with open authentication–Any host can access the network.
Multiple-authentication mode with open authentication–Similar to MDA, except multiple hosts can be authenticated.
For more information see the
“Configuring the Host Mode” section on page 8-43.
Note If open authentication is configured, it takes precedence over other authentication controls. This means that if you use the authentication open interface configuration command, the port will grant access to the host irrespective of the authentication port-control interface configuration command.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-29
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
Using Multidomain Authentication
The switch supports multidomain authentication (MDA), which allows both a data device and voice device, such as an IP phone (Cisco or non-Cisco), to authenticate on the same switch port. The port is divided into a data domain and a voice domain.
MDA does not enforce the order of device authentication. However, for best results, we recommend that a voice device is authenticated before a data device on an MDA-enabled port.
Follow these guidelines for configuring MDA:
• To configure a switch port for MDA, see the
“Configuring the Host Mode” section on page 8-43 .
•
•
You must configure the voice VLAN for the IP phone when the host mode is set to multidomain. For more information, see
Chapter 14, “Configuring Voice VLAN.”
Voice VLAN assignment on an MDA-enabled port is supported in Cisco IOS Release 12.2(40)SE and later.
•
•
•
•
•
•
•
To authorize a voice device, the AAA server must be configured to send a Cisco Attribute-Value
(AV) pair attribute with a value of device-traffic-class=voice . Without this value, the switch treats the voice device as a data device.
The guest VLAN and restricted VLAN features only apply to the data devices on an MDA-enabled port. The switch treats a voice device that fails authorization as a data device.
If more than one device attempts authorization on either the voice or the data domain of a port, it is error disabled.
Until a device is authorized, the port drops its traffic. Non-Cisco IP phones or voice devices are allowed into both the data and voice VLANs. The data VLAN allows the voice device to contact a
DHCP server to obtain an IP address and acquire the voice VLAN information. After the voice device starts sending on the voice VLAN, its access to the data VLAN is blocked.
A voice device MAC address that is binding on the data VLAN is not counted towards the port security MAC address limit.
You can use dynamic VLAN assignment from a RADIUS server only for data devices.
•
•
•
MDA can use MAC authentication bypass as a fallback mechanism to allow the switch port to connect to devices that do not support IEEE 802.1x authentication. For more information, see the
“MAC Authentication Bypass” section on page 8-37 .
When a data or a voice device is detected on a port, its MAC address is blocked until authorization succeeds. If the authorization fails, the MAC address remains blocked for 5 minutes.
If more than five devices are detected on the data VLAN or more than one voice device is detected on the voice VLAN while a port is unauthorized, the port is error disabled.
When a port host mode is changed from single- or multihost to multidomain mode, an authorized data device remains authorized on the port. However, a Cisco IP phone that has been allowed on the port voice VLAN is automatically removed and must be reauthenticated on that port.
•
•
•
Active fallback mechanisms such as guest VLAN and restricted VLAN remain configured after a port changes from single- or multihost mode to multidomain mode.
Switching a port host mode from multidomain to single- or multihost mode removes all authorized devices from the port.
If a data domain is authorized first and placed in the guest VLAN, non-IEEE 802.1x-capable voice devices need to tag their packets on the voice VLAN to trigger authentication.
8-30
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
• We do not recommend per-user ACLs with an MDA-enabled port. An authorized device with a per-user ACL policy might impact traffic on both the voice and data VLANs of the port. If used, only one device on the port should enforce per-user ACLs.
Voice Aware 802.1x Security
You use the voice aware 802.1x security feature to configure the switch to disable only the VLAN on which a security violation occurs, whether it is a data or voice VLAN. In previous releases, when an attempt to authenticate the data client caused a security violation, the entire port shut down, resulting in a complete loss of connectivity.
You can use this feature in IP phone deployments where a PC is connected to the IP phone. A security violation found on the data VLAN results in the shutdown of only the data VLAN. The traffic on the voice VLAN flows through the switch without interruption.
For information on configuring voice aware 802.1x security, see the .
802.1x Supplicant and Authenticator Switches with Network Edge Access
Topology (NEAT)
The Network Edge Access Topology (NEAT) feature extends identity to areas outside the wiring closet
(such as conference rooms). This allows any type of device to authenticate on the port.
• 802.1x switch supplicant: You can configure a switch to act as a supplicant to another switch by using the 802.1x supplicant feature. This configuration is helpful in a scenario, where, for example, a switch is outside a wiring closet and is connected to an upstream switch through a trunk port. A switch configured with the 802.1x switch supplicant feature authenticates with the upstream switch for secure connectivity.
•
You can enable MDA or multiauth mode on the authenticator switch interface that connects to one more supplicant switches. Multihost mode is not supported on the authenticator switch interface.
Use the dot1x supplicant force-multicast global configuration command on the supplicant switch for
Network Edge Access Topology (NEAT) to work in all host modes.
•
Once the supplicant switch authenticates successfully the port mode changes from access to trunk.
If the access VLAN is configured on the authenticator switch, it becomes the native VLAN for the trunk port after successful authentication.
•
Host Authorization: Ensures that only traffic from authorized hosts (connecting to the switch with supplicant) is allowed on the network. The switches use Client Information Signalling Protocol
(CISP) to send the MAC addresses connecting to the supplicant switch to the authenticator switch, as shown in
Auto Enablement: Automatically enables trunk configuration on the authenticator switch, allowing user traffic from multiple VLANs coming from supplicant switches. Configure the cisco-av-pair as device-traffic-class=switch at the ACS. (You can configure this under the group or the user settings.)
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-31
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Understanding IEEE 802.1x Port-Based Authentication
Figure 8-6 Authenticator and Supplicant Switch using CISP
4
2 3
1
5
1 Workstations (clients)
3 Authenticator switch
5 Trunk port
2 Supplicant switch (outside wiring closet)
4 Access control server (ACS)
Guidelines
• You can configure NEAT ports with the same configurations as the other authentication ports. When the supplicant switch authenticates, the port mode is changed from access to trunk based on the switch vendor-specific attributes (VSAs). ( device-traffic-class=switch).
•
•
The VSA changes the authenticator switch port mode from access to trunk and enables 802.1x trunk encapsulation and the access VLAN if any would be converted to a native trunk VLAN. VSA does not change any of the port configurations on the supplicant
To change the host mode and the apply a standard port configuration on the authenticator switch port, you can also use AutoSmart ports user-defined macros, instead of the switch VSA. This allows you to remove unsupported configurations on the authenticator switch port and to change the port mode from access to trunk . For more information, see
Chapter 11, “Configuring Smartports
.
For more information, see the
“Configuring an Authenticator and a Supplicant Switch with NEAT” section on page 8-60 .
Common Session ID
Authentication manager uses a single session ID (referred to as a common session ID) for a client no matter which authentication method is used. This ID is used for all reporting purposes, such as the show commands and MIBs. The session ID appears with all per-session syslog messages.
The session ID includes:
• The IP address of the Network Access Device (NAD)
•
•
A monotonically increasing unique 32 bit integer
The session start time stamp (a 32 bit integer)
This example shows how the session ID appears in the output of the show authentication command. The session ID in this example is 160000050000000B288508E5:
Switch# show authentication sessions
Interface MAC Address Method Domain Status Session ID
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-32 OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Configuring 802.1x Authentication
Fa4/0/4 0000.0000.0203 mab DATA Authz Success 160000050000000B288508E5
This is an example of how the session ID appears in the syslog output. The session ID in this example is also160000050000000B288508E5:
1w0d: %AUTHMGR-5-START: Starting 'mab' for client (0000.0000.0203) on Interface Fa4/0/4
AuditSessionID 160000050000000B288508E5
1w0d: %MAB-5-SUCCESS: Authentication successful for client (0000.0000.0203) on Interface
Fa4/0/4 AuditSessionID 160000050000000B288508E5
1w0d: %AUTHMGR-7-RESULT: Authentication result 'success' from 'mab' for client
(0000.0000.0203) on Interface Fa4/0/4 AuditSessionID 160000050000000B288508E5
The session ID is used by the NAD, the AAA server, and other report-analyzing applications to identify the client. The ID appears automatically. No configuration is required.
Configuring 802.1x Authentication
These sections contain this configuration information:
•
Default 802.1x Authentication Configuration, page 8-34
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
802.1x Authentication Configuration Guidelines, page 8-35
Configuring 802.1x Authentication, page 8-41
(required)
Configuring the Switch-to-RADIUS-Server Communication, page 8-42
Configuring Voice Aware 802.1x Security, page 8-39
Configuring 802.1x Violation Modes, page 8-40
Configuring the Host Mode, page 8-43 (optional)
(optional)
Enabling MAC Replace, page 8-45 (optional)
Configuring Periodic Re-Authentication, page 8-45
(required)
Manually Re-Authenticating a Client Connected to a Port, page 8-46
(optional)
Changing the Quiet Period, page 8-47
(optional)
Changing the Switch-to-Client Retransmission Time, page 8-47
(optional)
Setting the Switch-to-Client Frame-Retransmission Number, page 8-48
Setting the Re-Authentication Number, page 8-49
(optional)
Configuring 802.1x Accounting, page 8-49 (optional)
Configuring a Guest VLAN, page 8-50
(optional)
Configuring a Restricted VLAN, page 8-51
(optional)
Configuring the Inaccessible Authentication Bypass Feature, page 8-53
(optional)
Configuring 802.1x User Distribution, page 8-56
(optional)
Configuring 802.1x Authentication with WoL, page 8-57
(optional)
Configuring MAC Authentication Bypass, page 8-57 (optional)
Configuring NAC Layer 2 802.1x Validation, page 8-58
(optional)
(optional)
Configuring an Authenticator and a Supplicant Switch with NEAT, page 8-60
(optional)
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-33
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Configuring 802.1x Authentication
•
•
•
•
•
•
Configuring 802.1x Authentication with Downloadable ACLs and Redirect URLs, page 8-61
(optional)
Configuring VLAN ID-based MAC Authentication, page 8-64
(optional)
Configuring Flexible Authentication Ordering, page 8-64
(optional)
(optional)
Disabling 802.1x Authentication on the Port, page 8-65
(optional)
Resetting the 802.1x Authentication Configuration to the Default Values, page 8-66 (optional)
Default 802.1x Authentication Configuration
Table 8-4 shows the default 802.1x authentication configuration.
Table 8-4 Default 802.1x Authentication Configuration
Feature
Switch 802.1x enable state
Per-port 802.1x enable state
Default Setting
Disabled.
Disabled (force-authorized).
The port sends and receives normal traffic without
802.1x-based authentication of the client.
AAA Disabled.
RADIUS server
•
•
IP address
UDP authentication port
•
•
None specified.
1812.
• Key
Host mode
Control direction
Periodic re-authentication
Number of seconds between re-authentication attempts
Re-authentication number
• None specified.
Single-host mode.
Bidirectional control.
Disabled.
3600 seconds.
Quiet period
Retransmission time
Maximum retransmission number
2 times (number of times that the switch restarts the authentication process before the port changes to the unauthorized state).
60 seconds (number of seconds that the switch remains in the quiet state following a failed authentication exchange with the client).
30 seconds (number of seconds that the switch should wait for a response to an EAP request/identity frame from the client before resending the request).
2 times (number of times that the switch will send an
EAP-request/identity frame before restarting the authentication process).
8-34
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Configuring 802.1x Authentication
Table 8-4 Default 802.1x Authentication Configuration (continued)
Feature
Client timeout period
Authentication server timeout period
Inactivity timeout
Guest VLAN
Inaccessible authentication bypass
Restricted VLAN
Authenticator (switch) mode
MAC authentication bypass
Default Setting
30 seconds (when relaying a request from the authentication server to the client, the amount of time the switch waits for a response before resending the request to the client.)
30 seconds (when relaying a response from the client to the authentication server, the amount of time the switch waits for a reply before resending the response to the server.)
You can change this timeout period by using the dot1x timeout server-timeout interface configuration command.
Disabled.
None specified.
Disabled.
None specified.
None specified.
Disabled.
802.1x Authentication Configuration Guidelines
These section has configuration guidelines for these features:
•
•
802.1x Authentication, page 8-35
VLAN Assignment, Guest VLAN, Restricted VLAN, and Inaccessible Authentication Bypass, page 8-36
•
•
MAC Authentication Bypass, page 8-37
Maximum Number of Allowed Devices Per Port, page 8-37
802.1x Authentication
These are the 802.1x authentication configuration guidelines:
•
•
When IEEE 802.1x authentication is enabled, ports are authenticated before any other Layer 2 or
Layer 3 features are enabled.
If the VLAN to which an 802.1x-enabled port is assigned changes, this change is transparent and does not affect the switch. For example, this change occurs if a port is assigned to a RADIUS server-assigned VLAN and is then assigned to a different VLAN after re-authentication.
•
If the VLAN to which an 802.1x port is assigned to shut down, disabled, or removed, the port becomes unauthorized. For example, the port is unauthorized after the access VLAN to which a port is assigned shuts down or is removed.
The 802.1x protocol is supported on Layer 2 static-access ports, voice VLAN ports, and Layer 3 routed ports, but it is not supported on these port types:
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-35
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Configuring 802.1x Authentication
•
•
– Trunk port—If you try to enable 802.1x authentication on a trunk port, an error message appears, and 802.1x authentication is not enabled. If you try to change the mode of an
802.1x-enabled port to trunk, an error message appears, and the port mode is not changed.
–
–
Dynamic ports—A port in dynamic mode can negotiate with its neighbor to become a trunk port. If you try to enable 802.1x authentication on a dynamic port, an error message appears, and 802.1x authentication is not enabled. If you try to change the mode of an 802.1x-enabled port to dynamic, an error message appears, and the port mode is not changed.
Dynamic-access ports—If you try to enable 802.1x authentication on a dynamic-access (VLAN
Query Protocol [VQP]) port, an error message appears, and 802.1x authentication is not enabled. If you try to change an 802.1x-enabled port to dynamic VLAN assignment, an error message appears, and the VLAN configuration is not changed.
–
–
EtherChannel port—Do not configure a port that is an active or a not-yet-active member of an
EtherChannel as an 802.1x port. If you try to enable 802.1x authentication on an EtherChannel port, an error message appears, and 802.1x authentication is not enabled.
Switched Port Analyzer (SPAN) and Remote SPAN (RSPAN) destination ports—You can enable 802.1x authentication on a port that is a SPAN or RSPAN destination port. However,
802.1x authentication is disabled until the port is removed as a SPAN or RSPAN destination port. You can enable 802.1x authentication on a SPAN or RSPAN source port.
Before globally enabling 802.1x authentication on a switch by entering the dot1x system-auth-control global configuration command, remove the EtherChannel configuration from the interfaces on which 802.1x authentication and EtherChannel are configured.
Cisco IOS Release 12.2(55)SE and later supports filtering of system messages related to 802.1x
authentication. See the “Authentication Manager CLI Commands” section on page 8-10
.
VLAN Assignment, Guest VLAN, Restricted VLAN, and Inaccessible Authentication Bypass
These are the configuration guidelines for VLAN assignment, guest VLAN, restricted VLAN, and inaccessible authentication bypass:
• When 802.1x authentication is enabled on a port, you cannot configure a port VLAN that is equal to a voice VLAN.
•
•
The 802.1x authentication with VLAN assignment feature is not supported on trunk ports, dynamic ports, or with dynamic-access port assignment through a VMPS.
You can configure 802.1x authentication on a private-VLAN port, but do not configure IEEE 802.1x authentication with port security, a voice VLAN, a guest VLAN, a restricted VLAN, or a per-user
ACL on private-VLAN ports.
•
•
You can configure any VLAN except an RSPAN VLAN, private VLAN, or a voice VLAN as an
802.1x guest VLAN. The guest VLAN feature is not supported on internal VLANs (routed ports) or trunk ports; it is supported only on access ports.
After you configure a guest VLAN for an 802.1x port to which a DHCP client is connected, you might need to get a host IP address from a DHCP server. You can change the settings for restarting the IEEE 802.1x authentication process on the switch before the DHCP process on the client times out and tries to get a host IP address from the DHCP server. Decrease the settings for the 802.1x authentication process ( authentication timer inactivit y and authentication timer reauthentication interface configuration commands). The amount to decrease the settings depends on the connected 802.1x client type.
8-36
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Configuring 802.1x Authentication
•
•
When configuring the inaccessible authentication bypass feature, follow these guidelines:
–
–
The feature is supported on 802.1x port in single-host mode and multihosts mode.
If the client is running Windows XP and the port to which the client is connected is in the critical-authentication state, Windows XP might report that the interface is not authenticated.
–
–
If the Windows XP client is configured for DHCP and has an IP address from the DHCP server, receiving an EAP-Success message on a critical port might not re-initiate the DHCP configuration process.
You can configure the inaccessible authentication bypass feature and the restricted VLAN on an 802.1x port. If the switch tries to re-authenticate a critical port in a restricted VLAN and all the RADIUS servers are unavailable, the switch changes the port state to the critical authentication state and remains in the restricted VLAN.
You can configure any VLAN except an RSPAN VLAN or a voice VLAN as an 802.1x restricted
VLAN. The restricted VLAN feature is not supported on internal VLANs (routed ports) or trunk ports; it is supported only on access ports.
MAC Authentication Bypass
These are the MAC authentication bypass configuration guidelines:
•
•
Unless otherwise stated, the MAC authentication bypass guidelines are the same as the 802.1x authentication guidelines. For more information, see the
“802.1x Authentication” section on page 8-35
.
If you disable MAC authentication bypass from a port after the port has been authorized with its
MAC address, the port state is not affected.
•
•
•
If the port is in the unauthorized state and the client MAC address is not the authentication-server database, the port remains in the unauthorized state. However, if the client MAC address is added to the database, the switch can use MAC authentication bypass to re-authorize the port.
If the port is in the authorized state, the port remains in this state until re-authorization occurs.
You can configure a timeout period for hosts that are connected by MAC authentication bypass but are inactive. The range is 1-65535 seconds.
Maximum Number of Allowed Devices Per Port
This is the maximum number of devices allowed on an 802.1x-enabled port:
• In single-host mode, only one device is allowed on the access VLAN. If the port is also configured with a voice VLAN, an unlimited number of Cisco IP phones can send and receive traffic through the voice
VLAN.
•
•
In multidomain authentication (MDA) mode, one device is allowed for the access VLAN, and one
IP phone is allowed for the voice VLAN.
In multihost mode, only one 802.1x supplicant is allowed on the port, but an unlimited number of non-802.1x hosts are allowed on the access VLAN. An unlimited number of devices are allowed on the voice VLAN.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-37
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Configuring 802.1x Authentication
Configuring 802.1x Readiness Check
The 802.1x readiness check monitors 802.1x activity on all the switch ports and displays information about the devices connected to the ports that support 802.1x. You can use this feature to determine if the devices connected to the switch ports are 802.1x-capable.
The 802.1x readiness check is allowed on all ports that can be configured for 802.1x. The readiness check is not available on a port that is configured as dot1x force-unauthorized .
Follow these guidelines to enable the readiness check on the switch:
• The readiness check is typically used before 802.1x is enabled on the switch.
•
•
If you use the dot1x test eapol-capable privileged EXEC command without specifying an interface, all the ports on the switch are tested.
When you configure the dot1x test eapol-capable command on an 802.1x-enabled port, and the link comes up, the port queries the connected client about its 802.1x capability. When the client responds with a notification packet, it is 802.1x-capable. A syslog message is generated if the client responds within the timeout period. If the client does not respond to the query, the client is not
802.1x-capable. No syslog message is generated.
• The readiness check can be sent on a port that handles multiple hosts (for example, a PC that is connected to an IP phone). A syslog message is generated for each of the clients that respond to the readiness check within the timer period.
Beginning in privileged EXEC mode, follow these steps to enable the 802.1x readiness check on the switch:
Step 1
Step 1
Step 2
Step 3
Step 4
Command dot1x test eapol-capable interface-id ] configure terminal dot1x test timeout timeout end show running-config
[ interface
Purpose
Enable the 802.1x readiness check on the switch.
(Optional) For interface-id specify the port on which to check for
IEEE 802.1x readiness.
Note If you omit the optional interface keyword, all interfaces on the switch are tested.
(Optional) Enter global configuration mode.
(Optional) Configure the timeout used to wait for EAPOL response. The range is from 1 to 65535 seconds. The default is 10 seconds.
(Optional) Return to privileged EXEC mode.
(Optional) Verify your modified timeout values.
This example shows how to enable a readiness check on a switch to query a port. It also shows the response received from the queried port verifying that the device connected to it is 802.1x-capable: switch# dot1x test eapol-capable interface gigabitethernet1/0/13
DOT1X_PORT_EAPOL_CAPABLE:DOT1X: MAC 00-01-02-4b-f1-a3 on gigabitethernet1/0/13 is EAPOL capable
8-38
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Configuring 802.1x Authentication
Configuring Voice Aware 802.1x Security
You use the voice aware 802.1x security feature on the switch to disable only the VLAN on which a security violation occurs, whether it is a data or voice VLAN. You can use this feature in IP phone deployments where a PC is connected to the IP phone. A security violation found on the data VLAN results in the shutdown of only the data VLAN. The traffic on the voice VLAN flows through the switch without interruption.
Follow these guidelines to configure voice aware 802.1x voice security on the switch:
• You enable voice aware 802.1x security by entering the errdisable detect cause security-violation shutdown vlan global configuration command. You disable voice aware 802.1x security by entering the no version of this command. This command applies to all 802.1x-configured ports in the switch.
Note If you do not include the shutdown vlan keywords, the entire port is shut down when it enters the error-disabled state.
•
•
If you use the errdisable recovery cause security-violation global configuration command to configure error-disabled recovery, the port is automatically re-enabled. If error-disabled recovery is not configured for the port, you re-enable it by using the shutdown and no-shutdown interface configuration commands.
You can re-enable individual VLANs by using the clear errdisable interface interface-id vlan
[ vlan-list ] privileged EXEC command. If you do not specify a range, all VLANs on the port are enabled.
Beginning in privileged EXEC mode, follow these steps to enable voice aware 802.1x security:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Command configure terminal errdisable detect cause security-violation shutdown vlan shutdown no-shutdown end show errdisable detect copy running-config startup-config
Purpose
Enter global configuration mode.
Shut down any VLAN on which a security violation error occurs.
Note If the shutdown vlan keywords are not included, the entire port enters the error-disabled state and shuts down.
(Optional) Enable automatic per-VLAN error recovery.
errdisable recovery cause security-violation clear errdisable interface interface-id vlan [ vlan-list ]
(Optional) Reenable individual VLANs that have been error disabled.
• For interface-id specify the port on which to reenable individual
VLANs.
• (Optional) For vlan-list specify a list of VLANs to be re-enabled. If vlan-list is not specified, all VLANs are re-enabled.
(Optional) Re-enable an error-disabled VLAN, and clear all error-disable indications.
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-39
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Configuring 802.1x Authentication
This example shows how to configure the switch to shut down any VLAN on which a security violation error occurs:
Switch(config)# errdisable detect cause security-violation shutdown vlan
This example shows how to re-enable all VLANs that were error disabled on port Gi4/0/2.
Switch# clear errdisable interface GigabitEthernet4/0/2 vlan
You can verify your settings by entering the show errdisable detect privileged EXEC command.
Configuring 802.1x Violation Modes
You can configure an 802.1x port so that it shuts down, generates a syslog error, or discards packets from a new device when:
• a device connects to an 802.1x-enabled port
• the maximum number of allowed about devices have been authenticated on the port
Beginning in privileged EXEC mode, follow these steps to configure the security violation actions on the switch:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6 switchport mode access authentication violation shutdown | restrict | protect | replace }
Step 7
Step 8
Step 9
Command configure terminal aaa new-model aaa authentication dot1x { default } method1 interface interface-id end show authentication copy running-config startup-config
Purpose
Enter global configuration mode.
Enable AAA.
Create an 802.1x authentication method list.
To create a default list that is used when a named list is not specified in the authentication command, use the default keyword followed by the method that is to be used in default situations. The default method list is automatically applied to all ports.
For method1 , enter the group radius keywords to use the list of all
RADIUS servers for authentication.
Note Though other keywords are visible in the command-line help string, only the group radius keywords are supported.
Specify the port connected to the client that is to be enabled for
IEEE 802.1x authentication, and enter interface configuration mode.
Set the port to access mode.
Configure the violation mode. The keywords have these meanings:
• shutdown –Error disable the port.
•
• restrict –Generate a syslog error.
protect –Drop packets from any new device that sends traffic to the port.
• replace –Removes the current session and authenticates with the new host.
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
8-40
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Configuring 802.1x Authentication
Configuring 802.1x Authentication
To configure 802.1x port-based authentication, you must enable authentication, authorization, and accounting (AAA) and specify the authentication method list. A method list describes the sequence and authentication method to be queried to authenticate a user.
To allow per-user ACLs or VLAN assignment, you must enable AAA authorization to configure the switch for all network-related service requests.
This is the 802.1x AAA process:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
A user connects to a port on the switch.
Authentication is performed.
VLAN assignment is enabled, as appropriate, based on the RADIUS server configuration.
The switch sends a start message to an accounting server.
Re-authentication is performed, as necessary.
The switch sends an interim accounting update to the accounting server that is based on the result of re-authentication.
The user disconnects from the port.
The switch sends a stop message to the accounting server.
Beginning in privileged EXEC mode, follow these steps to configure 802.1x port-based authentication:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Command configure terminal aaa new-model aaa authentication dot1x { default } method1 dot1x system-auth-control aaa authorization network { default } group radius radius-server host radius-server key ip-address string
Purpose
Enter global configuration mode.
Enable AAA.
Create an 802.1x authentication method list.
To create a default list that is used when a named list is not specified in the authentication command, use the default keyword followed by the method that is to be used in default situations. The default method list is automatically applied to all ports.
For method1 , enter the group radius keywords to use the list of all
RADIUS servers for authentication.
Note Though other keywords are visible in the command-line help string, only the group radius keywords are supported.
Enable 802.1x authentication globally on the switch.
(Optional) Configure the switch to use user-RADIUS authorization for all network-related service requests, such as per-user ACLs or VLAN assignment.
Note For per-user ACLs, single-host mode must be configured. This setting is the default.
(Optional) Specify the IP address of the RADIUS server.
(Optional) Specify the authentication and encryption key used between the switch and the RADIUS daemon running on the RADIUS server.
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01 8-41
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Configuring 802.1x Authentication
Step 8
Command interface interface-id
Step 9 switchport mode access
Step 10 authentication port-control auto
Step 11 dot1x pae authenticator
Step 12
Step 13
Step 14 end show dot1x copy running-config startup-config
Purpose
Specify the port connected to the client that is to be enabled for
IEEE 802.1x authentication, and enter interface configuration mode.
(Optional) Set the port to access mode only if you configured the RADIUS server in Step 6 and Step 7.
Enable 802.1x authentication on the port.
For feature interaction information, see the
Configuration Guidelines” section on page 8-35 .
Set the interface Port Access Entity to act only as an authenticator and ignore messages meant for a supplicant.
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
Configuring the Switch-to-RADIUS-Server Communication
RADIUS security servers are identified by their hostname or IP address, hostname and specific UDP port numbers, or IP address and specific UDP port numbers. The combination of the IP address and UDP port number creates a unique identifier, which enables RADIUS requests to be sent to multiple UDP ports on a server at the same IP address. If two different host entries on the same RADIUS server are configured for the same service—for example, authentication—the second host entry configured acts as the fail-over backup to the first one. The RADIUS host entries are tried in the order that they were configured.
Beginning in privileged EXEC mode, follow these steps to configure the RADIUS server parameters on the switch. This procedure is required.
Step 1
Step 2
Command configure terminal
Purpose
Enter global configuration mode.
radius-server host { hostname | ip-address } auth-port port-number key string
Configure the RADIUS server parameters.
For hostname | ip-address, specify the hostname or IP address of the remote RADIUS server.
For auth-port port-number , specify the UDP destination port for authentication requests. The default is 1812. The range is 0 to 65536.
For key string , specify the authentication and encryption key used between the switch and the RADIUS daemon running on the RADIUS server. The key is a text string that must match the encryption key used on the RADIUS server.
Note Always configure the key as the last item in the radius-server host command syntax because leading spaces are ignored, but spaces within and at the end of the key are used. If you use spaces in the key, do not enclose the key in quotation marks unless the quotation marks are part of the key. This key must match the encryption used on the RADIUS daemon.
If you want to use multiple RADIUS servers, re-enter this command.
8-42
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Configuring 802.1x Authentication
Step 3
Step 4
Step 5
Command end show running-config copy running-config startup-config
Purpose
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
To delete the specified RADIUS server, use the no radius-server host { hostname | ip-address } global configuration command.
This example shows how to specify the server with IP address 172.20.39.46 as the RADIUS server, to use port 1612 as the authorization port, and to set the encryption key to rad123 , matching the key on the
RADIUS server:
Switch(config)# radius-server host 172.l20.39.46 auth-port 6403 key rad123
You can globally configure the timeout, retransmission, and encryption key values for all RADIUS servers by using the radius-server host global configuration command. If you want to configure these options on a per-server basis, use the radius-server timeout , radius-server retransmit , and the radius-server key global configuration commands. For more information, see the
“Configuring Settings for All RADIUS Servers” section on page 7-34 .
You also need to configure some settings on the RADIUS server. These settings include the IP address of the switch and the key string to be shared by both the server and the switch. For more information, see the RADIUS server documentation.
Configuring the Host Mode
Beginning in privileged EXEC mode, follow these steps to allow multiple hosts (clients) on an
IEEE 802.1x-authorized port that has the dot1x port-control interface configuration command set to auto . Use the multi-domain keyword to configure multidomain authentication (MDA) to enable authentication of both a host and a voice device, such as an IP phone (Cisco or non-Cisco) on the same switch port. This procedure is optional.
Step 1
Step 2
Command configure terminal interface interface-id
Purpose
Enter global configuration mode.
Specify the port to which multiple hosts are indirectly attached, and enter interface configuration mode.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-43
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Configuring 802.1x Authentication
Step 3
Step 4
Step 5
Step 6
Command Purpose authentication host-mode [ multi-auth | multi-domain | multi-host | single-host ]
The keywords have these meanings:
• multi-auth –Allow one client on the voice VLAN and multiple authenticated clients on the data VLAN.
Note The multi-auth keyword is only available with the authentication host-mode command.
end show authentication interface interface-id copy running-config startup-config
•
•
•
•
Note single-host –Allow a single host (client) on an
IEEE 802.1x-authorized port. multi-host –Allow multiple hosts on an 802.1x-authorized port after a single host has been authenticated.
single-host –Allow a single host (client) on an 802.1x-authorized port.
multi-domain –Allow both a host and a voice device, such as an IP phone (Cisco or non-Cisco), to be authenticated on an
IEEE 802.1x-authorized port.
You must configure the voice VLAN for the IP phone when the host mode is set to multi-domain . For more information, see
Chapter 14, “Configuring Voice VLAN.”
Make sure that the authentication port-control interface configuration command set is set to auto for the specified interface.
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
To disable multiple hosts on the port, use the no authentication host-mode interface configuration command.
This example shows how to enable 802.1x authentication and to allow multiple hosts:
Switch(config)# interface gigabitethernet0/1
Switch(config-if)# authentication port-control auto
Switch(config-if)# authentication host-mode multi-host
Enabling MAC Move
MAC move allows an authenticated host to move from one port on the switch to another.
Beginning in privileged EXEC mode, follow these steps to globally enable MAC move on the switch.
This procedure is optional.
Command configure terminal authentication mac-move permit end
Purpose
Enter global configuration mode.
Enable
Return to privileged EXEC mode.
8-44
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Configuring 802.1x Authentication
Command show run copy running-config startup-config
Purpose
Verify your entries.
(Optional) Save your entries in the configuration file.
This example shows how to globally enable MAC move on a switch:
Switch(config)# authentication mac-move permit
Enabling MAC Replace
MAC replace allows a host to replace an authenticated host on a port.
Beginning in privileged EXEC mode, follow these steps to enable MAC replace on an interface. This procedure is optional.
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Command configure terminal interface interface-id authentication violation { protect | replace | restrict | shutdown } end show running-config copy running-config startup-config
Purpose
Enter global configuration mode.
Specify the port to be configured, and enter interface configuration mode.
Use the replace keyword to enable MAC replace on the interface. The port removes the current session and initiates authentication with the new host.
The other keywords have these effects:
• protect : the port drops packets with unexpected MAC addresses without generating a system message.
•
• restrict : violating packets are dropped by the CPU and a system message is generated.
shutdown : the port is error disabled when it receives an unexpected
MAC address.
Return to privileged EXEc mode.
Verify your entries.
(Optional) Saves your entries in the configuration file.
This example shows how to enable MAC replace on an interface:
Switch(config)# interface gigabitethernet2/0/2
Switch(config-if)# authentication violation replace
Configuring Periodic Re-Authentication
You can enable periodic 802.1x client re-authentication and specify how often it occurs. If you do not specify a time period before enabling re-authentication, the number of seconds between attempts is 3600.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-45
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Configuring 802.1x Authentication
Beginning in privileged EXEC mode, follow these steps to enable periodic re-authentication of the client and to configure the number of seconds between re-authentication attempts. This procedure is optional.
Step 1
Step 2
Step 3
Step 4
Command configure terminal interface interface-id authentication periodic authentication timer {{[ inactivity | reauthenticate ]} { restart value }}
Step 5
Step 6
Step 7 end show authentication interface interface-id copy running-config startup-config
Purpose
Enter global configuration mode.
Specify the port to be configured, and enter interface configuration mode.
Enable periodic re-authentication of the client, which is disabled by default.
Note The default value is 3600 seconds. To change the value of the reauthentication timer or to have the switch use a
RADIUS-provided session timeout, enter the authentication timer reauthenticate command.
Set the number of seconds between re-authentication attempts.
The authentication timer keywords have these meanings:
• inactivity —Interval in seconds after which if there is no activity from the client then it is unauthorized
•
• reauthenticate —Time in seconds after which an automatic re-authentication attempt is be initiated restart value —Interval in seconds after which an attempt is made to authenticate an unauthorized port
This command affects the behavior of the switch only if periodic re-authentication is enabled.
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
To disable periodic re-authentication, use the no authentication periodic interface configuration command. To return to the default number of seconds between re-authentication attempts, use the no authentication timer interface configuration command.
This example shows how to enable periodic re-authentication and set the number of seconds between re-authentication attempts to 4000:
Switch(config-if)# authentication periodic
Switch(config-if)# authentication timer reauthenticate 4000
Manually Re-Authenticating a Client Connected to a Port
You can manually re-authenticate the client connected to a specific port at any time by entering the dot1x re-authenticate interface interface-id privileged EXEC command. This step is optional. If you want to enable or disable periodic re-authentication, see the
“Configuring Periodic Re-Authentication” section on page 8-45
.
This example shows how to manually re-authenticate the client connected to a port:
Switch# dot1x re-authenticate interface gigabitethernet0/1
8-46
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Configuring 802.1x Authentication
Changing the Quiet Period
When the switch cannot authenticate the client, the switch remains idle for a set period of time and then tries again. The dot1x timeout quiet-period interface configuration command controls the idle period.
A failed authentication of the client might occur because the client provided an invalid password. You can provide a faster response time to the user by entering a number smaller than the default.
Beginning in privileged EXEC mode, follow these steps to change the quiet period. This procedure is optional.
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Command configure terminal
Purpose
Enter global configuration mode.
interface interface-id Specify the port to be configured, and enter interface configuration mode.
authentication timer inactivity seconds Set the number of seconds that the switch remains in the quiet state following a failed authentication exchange with the client.
end show authentication interface interface-id copy running-config startup-config
The range is 1 to 65535 seconds; the default is 60.
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
To return to the default quiet time, use the no authentication timer inactivity interface configuration command.
This example shows how to set the quiet time on the switch to 30 seconds:
Switch(config-if)# authentication timer inactivity 30
Changing the Switch-to-Client Retransmission Time
The client responds to the EAP-request/identity frame from the switch with an EAP-response/identity frame. If the switch does not receive this response, it waits a set period of time (known as the retransmission time) and then resends the frame.
Note You should change the default value of this command only to adjust for unusual circumstances such as unreliable links or specific behavioral problems with certain clients and authentication servers.
Beginning in privileged EXEC mode, follow these steps to change the amount of time that the switch waits for client notification. This procedure is optional.
Step 1
Step 2
Step 3
Command configure terminal interface interface-id authentication timer reauthenticate seconds
Purpose
Enter global configuration mode.
Specify the port to be configured, and enter interface configuration mode.
Set the number of seconds that the switch waits for a response to an
EAP-request/identity frame from the client before resending the request.
The range is 1 to 65535 seconds; the default is 5.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-47
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Configuring 802.1x Authentication
Step 4
Step 5
Step 6
Command end show authentication interface interface-id copy running-config startup-config
Purpose
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
To return to the default retransmission time, use the no authentication timer reauthenticate interface configuration command.
This example shows how to set 60 as the number of seconds that the switch waits for a response to an
EAP-request/identity frame from the client before resending the request:
Switch(config-if)# authentication timer reauthenticate 60
Setting the Switch-to-Client Frame-Retransmission Number
In addition to changing the switch-to-client retransmission time, you can change the number of times that the switch sends an EAP-request/identity frame (assuming no response is received) to the client before restarting the authentication process.
Note You should change the default value of this command only to adjust for unusual circumstances such as unreliable links or specific behavioral problems with certain clients and authentication servers.
Beginning in privileged EXEC mode, follow these steps to set the switch-to-client frame-retransmission number. This procedure is optional.
Step 1
Step 2
Step 3
Command configure terminal interface interface-id dot1x max-reauth-req count
Purpose
Enter global configuration mode.
Specify the port to be configured, and enter interface configuration mode.
Set the number of times that the switch sends an EAP-request/identity frame to the client before restarting the authentication process. The range is 1 to 10; the default is 2.
Return to privileged EXEC mode.
Verify your entries.
Step 4
Step 5
Step 6 end show authentication interface interface-id copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default retransmission number, use the no dot1x max-req interface configuration command.
This example shows how to set 5 as the number of times that the switch sends an EAP-request/identity request before restarting the authentication process:
Switch(config-if)# dot1x max-reauth-req 5
8-48
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Configuring 802.1x Authentication
Setting the Re-Authentication Number
You can also change the number of times that the switch restarts the authentication process before the port changes to the unauthorized state.
Note You should change the default value of this command only to adjust for unusual circumstances such as unreliable links or specific behavioral problems with certain clients and authentication servers.
Beginning in privileged EXEC mode, follow these steps to set the re-authentication number. This procedure is optional.
Step 1
Step 2
Step 3
Command configure terminal interface interface-id dot1x max-req count
Purpose
Enter global configuration mode.
Specify the port to be configured, and enter interface configuration mode.
Set the number of times that the switch restarts the authentication process before the port changes to the unauthorized state. The range is 0 to 10; the default is 2.
Return to privileged EXEC mode.
Verify your entries.
Step 4
Step 5
Step 6 end show authentication interface interface-id copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default re-authentication number, use the no dot1x max-reauth-req interface configuration command.
This example shows how to set 4 as the number of times that the switch restarts the authentication process before the port changes to the unauthorized state:
Switch(config-if)# dot1x max-reauth-req 4
Configuring 802.1x Accounting
Enabling AAA system accounting with 802.1x accounting allows system reload events to be sent to the accounting RADIUS server for logging. The server can then infer that all active 802.1x sessions are closed.
Because RADIUS uses the unreliable UDP transport protocol, accounting messages might be lost due to poor network conditions. If the switch does not receive the accounting response message from the
RADIUS server after a configurable number of retransmissions of an accounting request, this system message appears:
Accounting message %s for session %s failed to receive Accounting Response.
When the stop message is not sent successfully, this message appears:
00:09:55: %RADIUS-4-RADIUS_DEAD: RADIUS server 172.20.246.201:1645,1646 is not responding.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-49
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Configuring 802.1x Authentication
Note You must configure the RADIUS server to perform accounting tasks, such as logging start, stop, and interim-update messages and time stamps. To turn on these functions, enable logging of
“Update/Watchdog packets from this AAA client” in your RADIUS server Network Configuration tab.
Next, enable “CVS RADIUS Accounting” in your RADIUS server System Configuration tab.
Beginning in privileged EXEC mode, follow these steps to configure 802.1x accounting after AAA is enabled on your switch. This procedure is optional.
Step 1
Step 2
Step 3
Step 4
Command configure terminal interface interface-id aaa accounting dot1x default start-stop group radius aaa accounting system default start-stop group radius
Step 5
Step 6
Step 7 end show running-config copy running-config startup-config
Purpose
Enter global configuration mode.
Specify the port to be configured, and enter interface configuration mode.
Enable 802.1x accounting using the list of all RADIUS servers.
(Optional) Enables system accounting (using the list of all RADIUS servers) and generates system accounting reload event messages when the switch reloads.
Return to privileged EXEc mode.
Verify your entries.
(Optional) Saves your entries in the configuration file.
Use the show radius statistics privileged EXEC command to display the number of RADIUS messages that do not receive the accounting response message.
This example shows how to configure 802.1x accounting. The first command configures the RADIUS server, specifying 1813 as the UDP port for accounting:
Switch(config)# radius-server host 172.120.39.46 auth-port 1812 acct-port 1813 key rad123
Switch(config)# aaa accounting dot1x default start-stop group radius
Switch(config)# aaa accounting system default start-stop group radius
Configuring a Guest VLAN
When you configure a guest VLAN, clients that are not 802.1x-capable are put into the guest VLAN when the server does not receive a response to its EAP request/identity frame. Clients that are
802.1x-capable but that fail authentication are not granted network access. The switch supports guest
VLANs in single-host or multiple-hosts mode.
Beginning in privileged EXEC mode, follow these steps to configure a guest VLAN. This procedure is optional.
Step 1
Step 2
Command configure terminal interface interface-id
Purpose
Enter global configuration mode.
Specify the port to be configured, and enter interface configuration mode.
For the supported port types, see the
Configuration Guidelines” section on page 8-35 .
8-50
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Configuring 802.1x Authentication
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Command switchport mode access or switchport mode private-vlan host dot1x port-control auto authentication event no-response action authorize vlan vlan-id end show authentication interface-id copy running-config startup-config
Purpose
Set the port to access mode, or
Configure the Layer 2 port as a private-VLAN host port.
Enable 802.1x authentication on the port.
Specify an active VLAN as an 802.1x guest VLAN. The range is 1 to
4094.
You can configure any active VLAN except an internal VLAN (routed port), an RSPAN VLAN, a primary private VLAN, or a voice VLAN as an 802.1x guest VLAN.
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
To disable and remove the guest VLAN, use the no authentication event no-response action authorize vlan vlan-id interface configuration command. The port returns to the unauthorized state.
This example shows how to enable VLAN 2 as an 802.1x guest VLAN:
Switch(config)# interface gigabitethernet0/2
Switch(config-if)# authentication event no-response action authorize vlan 2
This example shows how to set 3 as the quiet time on the switch, to set 15 as the number of seconds that the switch waits for a response to an EAP-request/identity frame from the client before re-sending the request, and to enable VLAN 2 as an 802.1x guest VLAN when an 802.1x port is connected to a DHCP client:
Switch(config-if)# authentication timer inactivity 3
Switch(config-if)# authentication timer reauthenticate 15
Switch(config-if)# authentication event no-response action authorize vlan 2
Configuring a Restricted VLAN
When you configure a restricted VLAN on a switch, clients that are IEEE 802.1x-compliant are moved into the restricted VLAN when the authentication server does not receive a valid username and password. The switch supports restricted VLANs only in single-host mode.
Beginning in privileged EXEC mode, follow these steps to configure a restricted VLAN. This procedure is optional.
Step 1
Step 2
Command configure terminal interface interface-id
Step 3 switchport mode access or switchport mode private-vlan host
Purpose
Enter global configuration mode.
Specify the port to be configured, and enter interface configuration mode.
For the supported port types, see the
Configuration Guidelines” section on page 8-35
.
Set the port to access mode, or
Configure the Layer 2 port as a private-VLAN host port.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-51
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Configuring 802.1x Authentication
Step 4
Step 5
Command authentication port-control auto dot1x auth-fail vlan vlan-id
Step 6
Step 7
Step 8 end show authentication interface interface-id copy running-config startup-config
Purpose
Enable 802.1x authentication on the port.
Specify an active VLAN as an 802.1x restricted VLAN. The range is 1 to
4094.
You can configure any active VLAN except an internal VLAN (routed port), an RSPAN VLAN, a primary private VLAN, or a voice VLAN as an 802.1x restricted VLAN.
Return to privileged EXEC mode.
(Optional) Verify your entries.
(Optional) Save your entries in the configuration file.
To disable and remove the restricted VLAN, use the no authentication event fail action authorize vlan-id interface configuration command. The port returns to the unauthorized state.
This example shows how to enable VLAN 2 as an 802.1x restricted VLAN:
Switch(config)# interface gigabitethernet0/2
Switch(config-if)# authentication event fail action authorize 2
You can configure the maximum number of authentication attempts allowed before a user is assigned to the restricted VLAN by using the authentication event retry retry count interface configuration command. The range of allowable authentication attempts is 1 to 3. The default is 3 attempts.
Beginning in privileged EXEC mode, follow these steps to configure the maximum number of allowed authentication attempts. This procedure is optional.
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Command configure terminal interface interface-id switchport mode access
Purpose
Enter global configuration mode.
Specify the port to be configured, and enter interface configuration mode.
For the supported port types, see the
Configuration Guidelines” section on page 8-35 .
Set the port to access mode, or switchport mode private-vlan host authentication port-control auto authentication event fail action authorize vlan-id or
Configure the Layer 2 port as a private-VLAN host port.
Enable 802.1x authentication on the port.
Specify an active VLAN as an 802.1x restricted VLAN. The range is 1 to
4094.
You can configure any active VLAN except an internal VLAN (routed port), an RSPAN VLAN, a primary private VLAN, or a voice VLAN as an 802.1x restricted VLAN.
authentication event retry retry count Specify a number of authentication attempts to allow before a port moves to the restricted VLAN. The range is 1 to 3, and the default is 3.
end Return to privileged EXEC mode.
(Optional) Verify your entries.
show authentication interface interface-id copy running-config startup-config (Optional) Save your entries in the configuration file.
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-52 OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Configuring 802.1x Authentication
To return to the default value, use the no authentication event retry interface configuration command.
This example shows how to set 2 as the number of authentication attempts allowed before the port moves to the restricted VLAN:
Switch(config-if)# authentication event retry 2
Configuring the Inaccessible Authentication Bypass Feature
You can configure the inaccessible bypass feature, also referred to as critical authentication or the AAA fail policy.
Beginning in privileged EXEC mode, follow these steps to configure the port as a critical port and enable the inaccessible authentication bypass feature. This procedure is optional.
Step 1
Step 2
Step 3
Command configure terminal radius-server dead-criteria time time tries tries radius-server deadtime minutes
Purpose
Enter global configuration mode.
(Optional) Set the conditions that are used to decide when a RADIUS server is considered unavailable or dead .
The range for time is from 1 to 120 seconds. The switch dynamically determines the default seconds value that is 10 to 60 seconds.
The range for tries is from 1 to 100. The switch dynamically determines the default tries parameter that is 10 to 100.
(Optional) Set the number of minutes that a RADIUS server is not sent requests. The range is from 0 to 1440 minutes (24 hours). The default is
0 minutes.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-53
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Configuring 802.1x Authentication
Step 4
Step 5
Command radius-server host ip-address
[acct-port udp-port ] [ auth-port udp-port ] [ test username name
[ idle-time time ] [ ignore-acct-port ]
[ ignore-auth-port ]] [ key string ]
Purpose
(Optional) Configure the RADIUS server parameters by using these keywords:
• acct-port udp-port— Specify the UDP port for the RADIUS accounting server. The range for the UDP port number is from 0 to
65536. The default is 1646.
•
Note auth-port udp-port— Specify the UDP port for the RADIUS authentication server. The range for the UDP port number is from 0 to 65536. The default is 1645.
You should configure the UDP port for the RADIUS accounting server and the UDP port for the RADIUS authentication server to nondefault values.
•
•
• test username name —Enable automated testing of the RADIUS server status, and specify the username to be used.
idle-time time— Set the interval of time in minutes after which the switch sends test packets to the server. The range is from 1 to
35791 minutes. The default is 60 minutes (1 hour).
ignore-acct-port — Disable testing on the RADIUS-server accounting port.
•
•
Note ignore-auth-port — Disable testing on the RADIUS-server authentication port.
For key string , specify the authentication and encryption key used between the switch and the RADIUS daemon running on the
RADIUS server. The key is a text string that must match the encryption key used on the RADIUS server.
Always configure the key as the last item in the radius-server host command syntax because leading spaces are ignored, but spaces within and at the end of the key are used. If you use spaces in the key, do not enclose the key in quotation marks unless the quotation marks are part of the key. This key must match the encryption used on the RADIUS daemon.You can also configure the authentication and encryption key by using the radius-server key { 0 string | 7 string | string } global configuration command.
dot1x critical { eapol | recovery delay milliseconds }
Note You can also configure the authentication and encryption key by using the radius-server key { 0 string | 7 string | string } global configuration command.
(Optional) Configure the parameters for inaccessible authentication bypass: eapol —Specify that the switch sends an EAPOL-Success message when the switch successfully authenticates the critical port.
recovery delay milliseconds —Set the recovery delay period during which the switch waits to re-initialize a critical port when a RADIUS server that was unavailable becomes available. The range is from 1 to
10000 milliseconds. The default is 1000 milliseconds (a port can be re-initialized every second).
8-54
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Configuring 802.1x Authentication
Step 6
Step 7
Command interface interface-id authentication event server dead action [authorize | reinitialize] vlan vlan-id
Step 8 authentication event server dead action { authorize | reinitialize } vlan vlan-id ]
Step 9
Step 10
Step 11
Step 12 authentication server dead action authorize [ vlan ] end show authentication interface interface-id copy running-config startup-config
Purpose
Specify the port to be configured, and enter interface configuration mode.
For the supported port types, see the
Configuration Guidelines” section on page 8-35 .
Use these keywords to move hosts on the port if the RADIUS server is unreachable:
• authorize –Move any new hosts trying to authenticate to the user-specified critical VLAN.
• reinitialize –Move all authorized hosts on the port to the user-specified critical VLAN.
Enable the inaccessible authentication bypass feature, and use these keywords to configure the feature:
•
• authorize —Authorize the port.
reinitialize —Reinitialize all authorized clients.
Authorize the switch in access VLAN or configured VLAN (if the VLAN is specified) when the ACS server is down.
Return to privileged EXEC mode.
(Optional) Verify your entries.
(Optional) Save your entries in the configuration file.
To return to the RADIUS server default settings, use the no radius-server dead-criteria , the no radius-server deadtime , and the no radius-server host global configuration commands. To return to the default settings of inaccessible authentication bypass, use the no authentication event server dead action {authorize | reinitialize } global configuration command. To disable inaccessible authentication bypass, use the n o authentication event server dead action interface configuration command.
This example shows how to configure the inaccessible authentication bypass feature:
Switch(config)# radius-server dead-criteria time 30 tries 20
Switch(config)# radius-server deadtime 60
Switch(config)# radius-server host 1.1.1.2 acct-port 1550 auth-port 1560 test username user1 idle-time 30 key abc1234
Switch(config)# dot1x critical eapol
Switch(config)# dot1x critical recovery delay 2000
Switch(config)# interface gigabitethernet0/1
Switch(config)# radius-server deadtime 60
Switch(config-if)# dot1x critical
Switch(config-if)# dot1x critical recovery action reinitialize
Switch(config-if)# dot1x critical vlan 20
Switch(config-if)# end
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-55
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Configuring 802.1x Authentication
Configuring 802.1x User Distribution
Beginning in global configuration, follow these steps to configure a VLAN group and to map a VLAN to it:
Step 1
Step 2
Step 3
Command vlan group vlan-group-name show vlan group no vlan group all vlan-list vlan-group-name
vlan-group-name vlan-list vlan-list vlan-list
Purpose
Configure a VLAN group, and map a single VLAN or a range of VLANs to it.
Verify the configuration.
Clear the VLAN group configuration or elements of the
VLAN group configuration.
This example shows how to configure the VLAN groups, to map the VLANs to the groups, to and verify the VLAN group configurations and mapping to the specified VLANs: switch(config)# vlan group eng-dept vlan-list 10 switch(config)# show vlan group group-name eng-dept
Group Name Vlans Mapped
------------- -------------eng-dept 10 switch# show dot1x vlan-group all
Group Name Vlans Mapped
------------- -------------eng-dept 10 hr-dept 20
This example shows how to add a VLAN to an existing VLAN group and to verify that the VLAN was added: switch(config)# vlan group eng-dept vlan-list 30 switch(config)# show vlan group eng-dept
Group Name Vlans Mapped
------------- -------------eng-dept 10,30
This example shows how to remove a VLAN from a VLAN group: switch# no vlan group eng-dept vlan-list 10
This example shows that when all the VLANs are cleared from a VLAN group, the VLAN group is cleared: switch(config)# no vlan group eng-dept vlan-list 30
Vlan 30 is successfully cleared from vlan group eng-dept.
switch(config)# show vlan group group-name eng-dept
This example shows how to clear all the VLAN groups: switch(config)# no vlan group end-dept vlan-list all switch(config)# show vlan-group all
For more information about these commands, see the Cisco IOS Security Command Reference.
8-56
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Configuring 802.1x Authentication
Configuring 802.1x Authentication with WoL
Beginning in privileged EXEC mode, follow these steps to enable 802.1x authentication with WoL. This procedure is optional.
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Command configure terminal
Purpose
Enter global configuration mode.
interface interface-id Specify the port to be configured, and enter interface configuration mode.
For the supported port types, see the
Configuration Guidelines” section on page 8-35
.
authentication control-direction { both
| in }
Enable 802.1x authentication with WoL on the port, and use these keywords to configure the port as bidirectional or unidirectional.
end show authentication or interface-id show dot1x interface interface-id copy running-config startup-config
•
• both —Sets the port as bidirectional. The port cannot receive packets from or send packets to the host. By default, the port is bidirectional.
in —Sets the port as unidirectional. The port can send packets to the host but cannot receive packets from the host.
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
To disable 802.1x authentication with WoL, use the no dot1x control-direction interface configuration command.
This example shows how to enable 802.1x authentication with WoL and set the port as bidirectional:
Switch(config-if)# authentication control-direction both
Configuring MAC Authentication Bypass
Beginning in privileged EXEC mode, follow these steps to enable MAC authentication bypass. This procedure is optional.
Step 1
Step 2
Command configure terminal interface interface-id
Step 3 authentication port-control auto
Purpose
Enter global configuration mode.
Specify the port to be configured, and enter interface configuration mode.
For the supported port types, see the
Configuration Guidelines” section on page 8-35
.
Enable 802.1x authentication on the port.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-57
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Configuring 802.1x Authentication
Step 4
Step 5
Step 6
Step 7
Command Purpose authentication order [ mab ] { webauth } Set the order of authentication methods.
• mab —Add MAC authentication bypass (MAB) to the order of authentication methods.
end show authentication interface interface-id copy running-config startup-config
• webauth —Add web authentication to the order of authentication methods.
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
To disable MAC authentication bypass, use the no authentication order interface configuration command.
This example shows how to enable MAC authentication bypass:
Switch(config-if)# authentication order
Configuring NAC Layer 2 802.1x Validation
You can configure NAC Layer 2 802.1x validation, which is also referred to as 802.1x authentication with a RADIUS server.
Beginning in privileged EXEC mode, follow these steps to configure NAC Layer 2 802.1x validation.
The procedure is optional.
Step 1
Step 2
Step 3
Command configure terminal interface interface-id authentication event no-response action authorize vlan vlan-id
Step 4 authentication periodic
Step 5 authentication timer reauthenticate
Step 6
Step 7
Step 8 end show authentication interface interface-id copy running-config startup-config
Purpose
Enter global configuration mode.
Specify the port to be configured, and enter interface configuration mode.
Specify an active VLAN as an 802.1x guest VLAN. The range is 1 to 4094.
You can configure any active VLAN except an internal VLAN (routed port), an RSPAN VLAN, or a voice VLAN as an 802.1x guest VLAN.
Enable periodic re-authentication of the client, which is disabled by default.
Set re-authentication attempt for the client (set to one hour).
This command affects the behavior of the switch only if periodic re-authentication is enabled.
Return to privileged EXEC mode.
Verify your 802.1x authentication configuration.
(Optional) Save your entries in the configuration file.
This example shows how to configure NAC Layer 2 802.1x validation:
Switch# configure terminal
Switch(config)# interface gigabitethernet0/1
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-58 OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Switch(config-if)# authentication periodic
Switch(config-if)# authentication timer reauthenticate
Configuring 802.1x Authentication
Configuring IEEE 802.1x Authentication Using a RADIUS Server
You can configure NAC Layer 2 802.1x validation, which is also referred to as 802.1x authentication with a RADIUS server.
Beginning in privileged EXEC mode, follow these steps to configure NAC Layer 2 802.1x validation.
The procedure is optional.
Step 1
Step 2
Step 3
Step 4
Step 5
Command configure terminal interface interface-id dot1x guest-vlan vlan-id authentication periodic authentication timer {{[ inactivity | reauthenticate ]} { restart value }}
Purpose
Enter global configuration mode.
Specify the port to be configured, and enter interface configuration mode.
Specify an active VLAN as an 802.1x guest VLAN. The range is 1 to
4094.
You can configure any active VLAN except an internal VLAN (routed port), an RSPAN VLAN, or a voice VLAN as an 802.1x guest VLAN.
Enable periodic re-authentication of the client, which is disabled by default.
Set the number of seconds between re-authentication attempts.
The authentication timer keywords have these meanings:
•
• inactivity —Interval in seconds after which if there is no activity from the client then it is unauthorized reauthenticate —Time in seconds after which an automatic re-authentication attempt is be initiated
• restart value —Interval in seconds after which an attempt is made to authenticate an unauthorized port
This command affects the behavior of the switch only if periodic re-authentication is enabled.
Return to privileged EXEC mode.
Verify your 802.1x authentication configuration.
Step 6
Step 7
Step 8 end show authentication interface interface-id copy running-config startup-config (Optional) Save your entries in the configuration file.
This example shows how to configure NAC Layer 2 802.1x validation:
Switch# configure terminal
Switch(config)# interface gigabitethernet0/1
Switch(config-if)# authentication periodic
Switch(config-if)# authentication timer reauthenticate 4000
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-59
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Configuring 802.1x Authentication
Configuring an Authenticator and a Supplicant Switch with NEAT
Configuring this feature requires that one switch outside a wiring closet is configured as a supplicant and is connected to an authenticator switch.
For overview information, see the
“802.1x Supplicant and Authenticator Switches with Network Edge
Access Topology (NEAT)” section on page 8-31 .
Note The cisco-av-pairs must be configured as device-traffic-class=switch on the ACS, which sets the interface as a trunk after the supplicant is successfully authenticated.
Beginning in privileged EXEC mode, follow these steps to configure a switch as an authenticator:
Step 1
Step 2
Step 3
Command configure terminal cisp enable interface interface-id
Step 4
Step 5
Step 6
Step 7 switchport mode access authentication port-control auto dot1x pae authenticator spanning-tree portfast
Step 8
Step 9
Step 10 end show running-config interface interface-id copy running-config startup-config
Purpose
Enter global configuration mode.
Enable CISP.
Specify the port to be configured, and enter interface configuration mode.
Set the port mode to access .
Set the port-authentication mode to auto.
Configure the interface as a port access entity (PAE) authenticator.
Enable Port Fast on an access port connected to a single workstation or server.
Return to privileged EXEC mode.
Verify your configuration.
(Optional) Save your entries in the configuration file.
This example shows how to configure a switch as an 802.1x authenticator:
Switch# configure terminal
Switch(config)# cisp enable
Switch(config)# interface gigabitethernet2/0/1
Switch(config-if)# switchport mode access
Switch(config-if)# authentication port-control auto
Switch(config-if)# dot1x pae authenticator
Switch(config-if)# spanning-tree portfast trunk
Beginning in privileged EXEC mode, follow these steps to configure a switch as a supplicant:
Step 1
Step 2
Step 3
Command configure terminal cisp enable dot1x credentials profile
Step 4 username suppswitch
Purpose
Enter global configuration mode.
Enable CISP.
Create 802.1x credentials profile. This must be attached to the port that is configured as supplicant.
Create a username.
8-60
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Configuring 802.1x Authentication
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
Step 12
Step 13
Step 14
Command password password dot1x supplicant force-multicast
Purpose
Create a password for the new username.
Force the switch to send only multicast EAPOL packets when it receives either unicast or multicast packets.
This also allows NEAT to work on the supplicant switch in all host modes.
interface interface-id Specify the port to be configured, and enter interface configuration mode.
Set the port to trunk mode.
switchport trunk encapsulation dot1q switchport mode trunk dot1x pae supplicant dot1x credentials profile-name end show running-config interface interface-id
Configure the interface as a VLAN trunk port.
Configure the interface as a port access entity (PAE) supplicant.
Attach the 802.1x credentials profile to the interface.
Return to privileged EXEC mode.
Verify your configuration.
copy running-config startup-config (Optional) Save your entries in the configuration file.
This example shows how to configure a switch as a supplicant:
Switch# configure terminal
Switch(config)# cisp enable
Switch(config)# dot1x credentials test
Switch(config)# username suppswitch
Switch(config)# password myswitch
Switch(config)# dot1x supplicant force-multicast
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# switchport trunk encapsulation dot1q
Switch(config-if)# switchport mode trunk
Switch(config-if)# dot1x pae supplicant
Switch(config-if)# dot1x credentials test
Switch(config-if)# end
Configuring NEAT with ASP
You can also use an AutoSmart Ports user-defined macro instead of the switch VSA to configure the
authenticator switch. For more information, see the Chapter 11, “Configuring Smartports Macros.”
Configuring 802.1x Authentication with Downloadable ACLs and Redirect URLs
In addition to configuring 802.1x authentication on the switch, you need to configure the ACS. For more information, see the Cisco Secure ACS configuration guides .
Note You must configure a downloadable ACL on the ACS before downloading it to the switch.
After authentication on the port, you can use the show ip access-list privileged EXEC command to display the downloaded ACLs on the port.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-61
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Configuring a Downloadable Policy
Configuring Downloadable ACLs
The policies take effect after client authentication and the client IP address addition to the IP device tracking table. The switch then applies the downloadable ACL to the port.
Beginning in privileged EXEC mode:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Command configure terminal ip device tracking aaa new-model aaa authorization network default group radius radius-server vsa send authentication interface interface-id ip access-group acl-id in
Step 8
Step 9 show running-config interface interface-id copy running-config startup-config
Purpose
Enter global configuration mode.
Configure the ip device tracking table.
Enables AAA.
Sets the authorization method to local. To remove the authorization method, use the no aaa authorization network default group radius command.
Configure the radius vsa send authentication.
Specify the port to be configured, and enter interface configuration mode.
Configure the default ACL on the port in the input direction.
Note The acl-id is an access list name or number.
Verify your configuration.
(Optional) Save your entries in the configuration file.
Configuring a Downloadable Policy
Beginning in privileged EXEC mode:
Step 1
Step 2
Command configure terminal access-list access-list-number deny source source-wildcard log
Purpose
Enter global configuration mode.
Defines the default port ACL by using a source address and wildcard.
The access-list-number is a decimal number from 1 to 99 or 1300 to 1999.
Enter deny or permit to specify whether to deny or permit access if conditions are matched.
The source is the source address of the network or host that sends a packet, such as this:
•
•
The 32-bit quantity in dotted-decimal format.
The keyword any as an abbreviation for source and source-wildcard value of
0.0.0.0 255.255.255.255. You do not need to enter a source-wildcard value.
• The keyword host as an abbreviation for source and source-wildcard of source 0.0.0.0.
(Optional) Applies the source-wildcard wildcard bits to the source.
(Optional) Enters log to cause an informational logging message about the packet that matches the entry to be sent to the console.
8-62
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Configuring a Downloadable Policy
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
Step 12
Step 13
Command interface interface-id ip access-group acl-id in exit aaa new-model aaa authorization network default group radius ip device tracking
Purpose
Enter interface configuration mode.
Configure the default ACL on the port in the input direction.
Note The acl-id is an access list name or number.
Returns to global configuration mode.
Enables AAA.
Sets the authorization method to local. To remove the authorization method, use the no aaa authorization network default group radius command.
Enables the IP device tracking table.
ip device tracking probe [ count | interval | use-svi ]
To disable the IP device tracking table, use the no ip device tracking global configuration commands.
(Optional) Configures the IP device tracking table:
•
• count count —Sets the number of times that the switch sends the ARP probe.
The range is from 1 to 5. The default is 3.
interval interval —Sets the number of seconds that the switch waits for a response before resending the ARP probe. The range is from 30 to 300 seconds. The default is 30 seconds.
radius-server vsa send authentication end show ip device tracking all copy running-config startup-config
• use-sv i—Uses the switch virtual interface (SVI) IP address as source of ARP probes.
Configures the network access server to recognize and use vendor-specific attributes.
Note The downloadable ACL must be operational.
Returns to privileged EXEC mode.
Displays information about the entries in the IP device tracking table.
(Optional) Saves your entries in the configuration file.
This example shows how to configure a switch for a downloadable policy:
Switch# config terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# aaa new-model
Switch(config)# aaa authorization network default group radius
Switch(config)# ip device tracking
Switch(config)# ip access-list extended default_acl
Switch(config-ext-nacl)# permit ip any any
Switch(config-ext-nacl)# exit
Switch(config)# radius-server vsa send authentication
Switch(config)# int fastEthernet 2/13
Switch(config-if)# ip access-group default_acl in
Switch(config-if)# exit
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-63
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Configuring a Downloadable Policy
Configuring VLAN ID-based MAC Authentication
Beginning in privileged EXEC mode, follow these steps:
Step 1
Step 2
Step 3
Command configure terminal mab request format attribute 32 vlan access-vlan copy running-config startup-config
Purpose
Enter global configuration mode.
Enable VLAN ID-based MAC authentication.
(Optional) Save your entries in the configuration file.
There is no show command to confirm the status of VLAN ID-based MAC authentication. You can use the debug radius accounting privileged EXEC command to confirm the RADIUS attribute 32. For more information about this command, see the Cisco IOS Debug Command Reference, Release 12.2 at this
URL: http://www.cisco.com/en/US/docs/ios/debug/command/reference/db_q1.html#wp1123741
This example shows how to globally enable VLAN ID-based MAC authentication on a switch:
Switch# config terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# mab request format attribute 32 vlan access-vlan
Switch(config-if)# exit
Configuring Flexible Authentication Ordering
Beginning in privileged EXEC mode, follow these steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Command configure terminal interface interface-id
Purpose
Enter global configuration mode.
Specify the port to be configured, and enter interface configuration mode.
authentication order dot1x | mab { webauth } (Optional) Set the order of authentication methods used on a port. authentication priority dot1x
{ webauth } show authentication
| mab (Optional) Add an authentication method to the port-priority list.
(Optional) Verify your entries.
copy running-config startup-config (Optional) Save your entries in the configuration file.
This example shows how to configure a port attempt 802.1x authentication first, followed by web authentication as fallback method:
Switch# configure terminal
Switch(config)# interface gigabitethernet 1/0/1
Switch(config)# authentication order dot1x webauth
8-64
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Configuring a Downloadable Policy
Configuring Open1x
Beginning in privileged EXEC mode:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
Command configure terminal
Purpose
Enter global configuration mode.
interface interface-id Specify the port to be configured, and enter interface configuration mode.
authentication control-direction {both | in } (Optional) Configure the port control as unidirectional or bidirectional.
authentication fallback name authentication host-mode [ multi-auth | multi-domain | multi-host | single-host ]
(Optional) Configure a port to use web authentication as a fallback method for clients that do not support 802.1x authentication.
(Optional) Set the authorization manager mode on a port.
(Optional) Enable or disable open access on a port.
(Optional) Set the order of authentication methods used on a port. authentication open authentication order [ dot1x | mab ] |
{ webauth } authentication periodic authentication port-control { auto | force-authorized | f orce-un authorized } show authentication copy running-config startup-config
(Optional) Enable or disable reauthentication on a port.
(Optional) Enable manual control of the port authorization state.
(Optional) Verify your entries.
(Optional) Save your entries in the configuration file.
This example shows how to configure open 1x on a port:
Switch# configure terminal
Switch(config)# interface gigabitethernet 1/0/1
Switch(config)# authentication control-direction both
Switch(config)# authentication fallback profile1
Switch(config)# authentication host-mode multi-auth
Switch(config)# authentication open
Switch(config)# authentication order dot1x webauth
Switch(config)# authentication periodic
Switch(config)# authentication port-control auto
Disabling 802.1x Authentication on the Port
You can disable 802.1x authentication on the port by using the no dot1x pae interface configuration command.
Beginning in privileged EXEC mode, follow these steps to disable 802.1x authentication on the port.
This procedure is optional.
Step 1
Step 2
Command configure terminal interface interface-id
Purpose
Enter global configuration mode.
Specify the port to be configured, and enter interface configuration mode.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
8-65
Chapter 8 Configuring IEEE 802.1x Port-Based Authentication
Displaying 802.1x Statistics and Status
Step 3
Step 4
Step 5
Step 6
Command no dot1x pae end show authentication interface interface-id copy running-config startup-config
Purpose
Disable 802.1x authentication on the port.
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
To configure the port as an 802.1x port access entity (PAE) authenticator, which enables IEEE 802.1x on the port but does not allow clients connected to the port to be authorized, use the dot1x pae authenticator interface configuration command.
This example shows how to disable 802.1x authentication on the port:
Switch(config)# interface gigabitethernet0/1
Switch(config-if)# no dot1x pae authenticator
Resetting the 802.1x Authentication Configuration to the Default Values
Beginning in privileged EXEC mode, follow these steps to reset the 802.1x authentication configuration to the default values. This procedure is optional.
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Command configure terminal interface interface-id dot1x default end show authentication interface interface-id copy running-config startup-config
Purpose
Enter global configuration mode.
Enter interface configuration mode, and specify the port to be configured.
Reset the 802.1x parameters to the default values.
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
Displaying 802.1x Statistics and Status
To display 802.1x statistics for all ports, use the show dot1x all statistics privileged EXEC command.
To display 802.1x statistics for a specific port, use the show dot1x statistics interface interface-id privileged EXEC command.
To display the 802.1x administrative and operational status for the switch, use the show dot1x all
[ details | statistics | summary ] privileged EXEC command. To display the 802.1x administrative and operational status for a specific port, use the show dot1x interface interface-id privileged EXEC command.
Beginning with Cisco IOS Release 12.2(55)SE, you can use the no dot1x logging verbose global configuration command to filter verbose 802.1x authentication messages. See the
Manager CLI Commands” section on page 8-10
.
For detailed information about the fields in these displays, see the command reference for this release.
8-66
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
C H A P T E R
9
Configuring Web-Based Authentication
This chapter describes how to configure web-based authentication. It contains these sections:
•
Understanding Web-Based Authentication, page 9-1
•
•
Configuring Web-Based Authentication, page 9-9
Displaying Web-Based Authentication Status, page 9-17
Note For complete syntax and usage information for the switch commands used in this chapter, refer to the command reference for this release.
Understanding Web-Based Authentication
Use the web-based authentication feature, known as web authentication proxy , to authenticate end users on host systems that do not run the IEEE 802.1x supplicant.
Note You can configure web-based authentication on Layer 2 and Layer 3 interfaces.
When you initiate an HTTP session, web-based authentication intercepts ingress HTTP packets from the host and sends an HTML login page to the users. The users enter their credentials, which the web-based authentication feature sends to the authentication, authorization, and accounting (AAA) server for authentication.
If authentication succeeds, web-based authentication sends a Login-Successful HTML pag e to the host and applies the access policies returned by the AAA server.
If authentication fails, web-based authentication forwards a Login-Fail HTML page to the user, prompting the user to retry the login. If the user exceeds the maximum number of attempts, web-based authentication forwards a Login-Expired HTML page to the host, and the user is placed on a watch list for a waiting period.
These sections describe the role of web-based authentication as part of AAA:
•
•
•
•
Authentication Process, page 9-3
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
9-1
Chapter 9 Configuring Web-Based Authentication
Understanding Web-Based Authentication
•
•
Web Authentication Customizable Web Pages, page 9-6
Web-based Authentication Interactions with Other Features, page 9-7
Device Roles
With web-based authentication, the devices in the network have these specific roles:
•
•
Client —The device (workstation) that requests access to the LAN and the services and responds to requests from the switch. The workstation must be running an HTML browser with Java Script enabled.
Authentication server —Authenticates the client. The authentication server validates the identity of the client and notifies the switch that the client is authorized to access the LAN and the switch services or that the client is denied.
• Switch —Controls the physical access to the network based on the authentication status of the client.
The switch acts as an intermediary (proxy) between the client and the authentication server, requesting identity information from the client, verifying that information with the authentication server, and relaying a response to the client.
shows the roles of these devices in a network:
Figure 9-1 Web-Based Authentication Device Roles
Catalyst switch or
Cisco Router
Authentication server
(RADIUS)
Workstations
(clients)
Host Detection
The switch maintains an IP device tracking table to store information about detected hosts.
Note By default, the IP device tracking feature is disabled on a switch. You must enable the IP device tracking feature to use web-based authentication.
For Layer 2 interfaces, web-based authentication detects IP hosts by using these mechanisms:
•
•
•
ARP based trigger—ARP redirect ACL allows web-based authentication to detect hosts with a static
IP address or a dynamic IP address.
Dynamic ARP inspection
DHCP snooping—Web-based authentication is notified when the switch creates a DHCP-binding entry for the host.
9-2
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 9 Configuring Web-Based Authentication
Understanding Web-Based Authentication
Session Creation
When web-based authentication detects a new host, it creates a session as follows:
• Reviews the exception list.
•
If the host IP is included in the exception list, the policy from the exception list entry is applied, and the session is established.
Reviews for authorization bypass
•
If the host IP is not on the exception list, web-based authentication sends a nonresponsive-host
(NRH) request to the server.
If the server response is access accepted , authorization is bypassed for this host. The session is established.
Sets up the HTTP intercept ACL
If the server response to the NRH request is access rejected , the HTTP intercept ACL is activated, and the session waits for HTTP traffic from the host.
Authentication Process
When you enable web-based authentication, these events occur:
• The user initiates an HTTP session.
•
•
The HTTP traffic is intercepted, and authorization is initiated. The switch sends the login page to the user. The user enters a username and password, and the switch sends the entries to the authentication server.
If the authentication succeeds, the switch downloads and activates the user’s access policy from the authentication server. The login success page is sent to the user.
•
•
If the authentication fails, the switch sends the login fail page. The user retries the login. If the maximum number of attempts fails, the switch sends the login expired page, and the host is placed in a watch list. After the watch list times out, the user can retry the authentication process.
If the authentication server does not respond to the switch, and if an AAA fail policy is configured, the switch applies the failure access policy to the host. The login success page is sent to the user.
(See the
“Local Web Authentication Banner” section on page 9-4
.)
•
•
•
•
The switch reauthenticates a client when the host does not respond to an ARP probe on a Layer 2 interface, or when the host does not send any traffic within the idle timeout on a Layer 3 interface.
The feature applies the downloaded timeout or the locally configured session timeout.
If the terminate action is RADIUS, the feature sends a nonresponsive host (NRH) request to the server. The terminate action is included in the response from the server.
If the terminate action is default, the session is dismantled, and the applied policy is removed.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
9-3
Chapter 9 Configuring Web-Based Authentication
Understanding Web-Based Authentication
Local Web Authentication Banner
You can create a banner that will appear when you log in to a switch by using web authentication.
The banner appears on both the login page and the authentication-result pop-up pages.
•
•
Authentication Successful
Authentication Failed
• Authentication Expired
You create a banner by using the ip admission auth-proxy-banner http global configuration command.
The default banner Cisco Systems and Switch host-name Authentication appear on the Login Page. Cisco
Systems appears on the authentication result pop-up page, as shown in
Figure 9-2 Authentication Successful Banner
You can also customize the banner, as shown in Figure 9-3
.
•
•
Add a switch, router, or company name to the banner by using the ip admission auth-proxy-banner http banner-text global configuration command.
Add a logo or text file to the banner by using the ip admission auth-proxy-banner http file-path global configuration command.
9-4
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 9 Configuring Web-Based Authentication
Figure 9-3 Customized Web Banner
Understanding Web-Based Authentication
If you do not enable a banner, only the username and password dialog boxes appear in the web authentication login screen, and no banner appears when you log into the switch, as shown in
Figure 9-4 Login Screen With No Banner
OL-27326-01
For more information, see the Cisco IOS Security Command Reference
Authentication Local Banner” section on page 9-16 .
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
9-5
Chapter 9 Configuring Web-Based Authentication
Understanding Web-Based Authentication
Web Authentication Customizable Web Pages
During the web-based authentication process, the switch internal HTTP server hosts four HTML pages to deliver to an authenticating client. The server uses these pages to notify you of these four-authentication process states:
• Login—Your credentials are requested.
•
•
•
Success—The login was successful.
Fail—The login failed.
Expire—The login session has expired because of excessive login failures.
Guidelines
•
•
•
•
•
•
•
•
•
You can substitute your own HTML pages for the default internal HTML pages.
You can use a logo or specify text in the login , success , failure , and expire web pages.
On the banner page, you can specify text in the login page.
The pages are in HTML.
You must include an HTML redirect command in the success page to access a specific URL.
The URL string must be a valid URL (for example, http://www.cisco.com). An incomplete URL might cause page not found or similar errors on a web browser.
If you configure web pages for HTTP authentication, they must include the appropriate HTML commands (for example, to set the page time out, to set a hidden password, or to confirm that the same page is not submitted twice).
The CLI command to redirect users to a specific URL is not available when the configured login form is enabled. The administrator should ensure that the redirection is configured in the web page.
If the CLI command redirecting users to specific URL after authentication occurs is entered and then the command configuring web pages is entered, the CLI command redirecting users to a specific
URL does not take effect.
•
•
•
•
Configured web pages can be copied to the switch boot flash or flash.
The login page can be on one flash, and the success and failure pages can be another flash (for example, the flash on the stack master or a member).
You must configure all four pages.
The banner page has no effect if it is configured with the web page.
• All of the logo files (image, flash, audio, video, and so on) that are stored in the system directory
(for example, flash, disk0, or disk) and that must be displayed on the login page must use web_auth_<filename> as the file name.
The configured authentication proxy feature supports both HTTP and SSL.
•
pages. You can also specify a URL to which users are redirected after authentication occurs, which replaces the internal Success page.
9-6
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 9 Configuring Web-Based Authentication
Figure 9-5 Customizeable Authentication Page
Understanding Web-Based Authentication
For more information, see the
“Customizing the Authentication Proxy Web Pages” section on page 9-14 .
Web-based Authentication Interactions with Other Features
•
•
•
•
•
•
•
Context-Based Access Control, page 9-8
802.1x Authentication, page 9-8
Port Security
You can configure web-based authentication and port security on the same port. Web-based authentication authenticates the port, and port security manages network access for all MAC addresses, including that of the client. You can then limit the number or group of clients that can access the network through the port.
For more information about enabling port security, see
“Configuring Port Security” section on page 24-8
.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
9-7
Chapter 9 Configuring Web-Based Authentication
Understanding Web-Based Authentication
LAN Port IP
You can configure LAN port IP (LPIP) and Layer 2 web-based authentication on the same port. The host is authenticated by using web-based authentication first, followed by LPIP posture validation. The LPIP host policy overrides the web-based authentication host policy.
If the web-based authentication idle timer expires, the NAC policy is removed. The host is authenticated, and posture is validated again.
Gateway IP
You cannot configure Gateway IP (GWIP) on a Layer 3 VLAN interface if web-based authentication is configured on any of the switch ports in the VLAN.
You can configure web-based authentication on the same Layer 3 interface as Gateway IP. The host policies for both features are applied in software. The GWIP policy overrides the web-based authentication host policy.
ACLs
If you configure a VLAN ACL or a Cisco IOS ACL on an interface, the ACL is applied to the host traffic only after the web-based authentication host policy is applied.
For Layer 2 web-based authentication, you must configure a port ACL (PACL) as the default access policy for ingress traffic from hosts connected to the port. After authentication, the web-based authentication host policy overrides the PACL.
Note When a proxy ACL is configured for a web-based authentication client, the proxy ACL is downloaded and applied as part of the authorization process. Hence, the PACL displays the proxy ACL access control entry (ACE).
You cannot configure a MAC ACL and web-based authentication on the same interface.
You cannot configure web-based authentication on a port whose access VLAN is configured for VACL capture.
Context-Based Access Control
Web-based authentication cannot be configured on a Layer 2 port if context-based access control
(CBAC) is configured on the Layer 3 VLAN interface of the port VLAN.
802.1x Authentication
We recommend that you not configure web-based authentication on the same port as 802.1x authentication except as a fallback authentication method.
EtherChannel
You can configure web-based authentication on a Layer 2 EtherChannel interface. The web-based authentication configuration applies to all member channels.
9-8
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 9 Configuring Web-Based Authentication
Configuring Web-Based Authentication
Configuring Web-Based Authentication
•
•
•
•
•
•
•
•
•
Default Web-Based Authentication Configuration, page 9-9
Web-Based Authentication Configuration Guidelines and Restrictions, page 9-9
Web-Based Authentication Configuration Task List, page 9-10
Configuring the Authentication Rule and Interfaces, page 9-10
Configuring AAA Authentication, page 9-11
Configuring Switch-to-RADIUS-Server Communication, page 9-12
Configuring the HTTP Server, page 9-13
Configuring the Web-Based Authentication Parameters, page 9-16
Removing Web-Based Authentication Cache Entries, page 9-17
Default Web-Based Authentication Configuration
shows the default web-based authentication configuration.
Table 9-1 Default Web-based Authentication Configuration
Feature Default Setting
AAA Disabled
RADIUS server
•
•
IP address
UDP authentication port
• Key
Default value of inactivity timeout
Inactivity timeout
•
•
None specified
1812
• None specified
3600 seconds
Enabled
Web-Based Authentication Configuration Guidelines and Restrictions
•
•
•
•
•
•
Web-based authentication is an ingress-only feature.
You can configure web-based authentication only on access ports. Web-based authentication is not supported on trunk ports, EtherChannel member ports, or dynamic trunk ports.
You must configure the default ACL on the interface before configuring web-based authentication.
Configure a port ACL for a Layer 2 interface or a Cisco IOS ACL for a Layer 3 interface.
You cannot authenticate hosts on Layer 2 interfaces with static ARP cache assignment. These hosts are not detected by the web-based authentication feature because they do not send ARP messages.
By default, the IP device tracking feature is disabled on a switch. You must enable the IP device tracking feature to use web-based authentication.
You must configure at least one IP address to run the switch HTTP server. You must also configure routes to reach each host IP address. The HTTP server sends the HTTP login page to the host.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
9-9
Chapter 9 Configuring Web-Based Authentication
Configuring Web-Based Authentication
•
•
•
•
•
Hosts that are more than one hop away might experience traffic disruption if an STP topology change results in the host traffic arriving on a different port. This occurs because the ARP and DHCP updates might not be sent after a Layer 2 (STP) topology change.
Web-based authentication does not support VLAN assignment as a downloadable-host policy.
Web-based authentication is not supported for IPv6 traffic.
Web-based authentication and Network Edge Access Topology (NEAT) are mutually exclusive. You cannot use web-based authentication when NEAT is enabled on an interface, and you cannot use
NEAT when web-based authentication is running on an interface.
Web-based authentication supports only RADIUS authorization servers. You cannot use TACACS+ servers or local authorization.
Web-Based Authentication Configuration Task List
•
•
•
•
•
•
•
Configuring the Authentication Rule and Interfaces, page 9-10
Configuring AAA Authentication, page 9-11
Configuring Switch-to-RADIUS-Server Communication, page 9-12
Configuring the HTTP Server, page 9-13
Configuring the Web-Based Authentication Parameters, page 9-16
Configuring a Web Authentication Local Banner, page 9-16
Removing Web-Based Authentication Cache Entries, page 9-17
Configuring the Authentication Rule and Interfaces
Step 1
Step 2
Command Purpose ip admission name name proxy http Configure an authentication rule for web-based authorization.
interface type slot/port Enter interface configuration mode and specifies the ingress Layer 2 or
Layer 3 interface to be enabled for web-based authentication.
Step 3 ip access-group name
Step 4 ip admission name
Step 5 exit type can be fastethernet, gigabit ethernet, or tengigabitethernet.
Apply the default ACL.
Configure web-based authentication on the specified interface.
Return to configuration mode.
Step 6 ip device tracking
Step 7 end
Step 8
Step 9 show ip admission configuration
Enable the IP device tracking table.
Return to privileged EXEC mode.
Display the configuration.
copy running-config startup-config (Optional) Save your entries in the configuration file.
This example shows how to enable web-based authentication on Fast Ethernet port 5/1:
Switch(config)# ip admission name webauth1 proxy http
Switch(config)# interface fastethernet 5/1
Switch(config-if)# ip admission webauth1
Switch(config-if)# exit
9-10
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 9 Configuring Web-Based Authentication
Switch(config)# ip device tracking
This example shows how to verify the configuration:
Switch# show ip admission configuration
Authentication Proxy Banner not configured
Authentication global cache time is 60 minutes
Authentication global absolute time is 0 minutes
Authentication global init state time is 2 minutes
Authentication Proxy Watch-list is disabled
Authentication Proxy Rule Configuration
Auth-proxy name webauth1
http list not specified inactivity-time 60 minutes
Authentication Proxy Auditing is disabled
Max Login attempts per user is 5
Configuring AAA Authentication
Configuring Web-Based Authentication
Command radius-server host { hostname | ip-address } test username username
Purpose
Step 1 aaa new-model Enables AAA functionality.
Step 2 aaa authentication login default group { tacacs+
| radius }
Defines the list of authentication methods at login.
Step 3 aaa authorization auth-proxy default group
{ tacacs+ | radius }
Create an authorization method list for web-based authorization.
Step 4 Specify an AAA server.
Specify the host name or IP address of the remote RADIUS server.
The test username username option enables automated testing of the RADIUS server connection. The specified username does not need to be a valid user name.
Step 5 radius-server key string
Step 6 copy running-config startup-config
Configure the authorization and encryption key used between the switch and the RADIUS daemon running on the RADIUS server. To use multiple RADIUS servers, reenter this command for each server.
(Optional) Save your entries in the configuration file.
This example shows how to enable AAA:
Switch(config)# aaa new-model
Switch(config)# aaa authentication login default group radius
Switch(config)# aaa authorization auth-proxy default group radius
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
9-11
Chapter 9 Configuring Web-Based Authentication
Configuring Web-Based Authentication
Configuring Switch-to-RADIUS-Server Communication
RADIUS security servers identification:
• Host name
•
•
Host IP address
Host name and specific UDP port numbers
• IP address and specific UDP port numbers
The combination of the IP address and UDP port number creates a unique identifier, that enables
RADIUS requests to be sent to multiple UDP ports on a server at the same IP address. If two different host entries on the same RADIUS server are configured for the same service (for example, authentication) the second host entry that is configured functions as the failover backup to the first one.
The RADIUS host entries are chosen in the order that they were configured.
To configure the RADIUS server parameters, perform this task:
Step 1
Step 2
Step 3
Step 4
Step 5
Command ip radius source-interface interface_name radius-server host { hostname | ip-address } test username username radius-server key string radius-server vsa send authentication radius-server dead-criteria tries num-tries
Purpose
Specify that the RADIUS packets have the IP address of the indicated interface.
Specify the host name or IP address of the remote
RADIUS server.
The test username username option enables automated testing of the RADIUS server connection. The specified username does not need to be a valid user name.
The key option specifies an authentication and encryption key to use between the switch and the RADIUS server.
To use multiple RADIUS servers, reenter this command for each server.
Configure the authorization and encryption key used between the switch and the RADIUS daemon running on the RADIUS server.
Enable downloading of an ACL from the RADIUS server.
This feature is supported in
Cisco IOS Release 12.2(50)SG.
Specify the number of unanswered sent messages to a
RADIUS server before considering the server to be inactive. The range of num-tries is 1 to 100.
When you configure the RADIUS server parameters:
•
•
Specify the key string on a separate command line.
For key string , specify the authentication and encryption key used between the switch and the
RADIUS daemon running on the RADIUS server. The key is a text string that must match the encryption key used on the RADIUS server.
• When you specify the key string , use spaces within and at the end of the key. If you use spaces in the key, do not enclose the key in quotation marks unless the quotation marks are part of the key.
This key must match the encryption used on the RADIUS daemon.
9-12
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 9 Configuring Web-Based Authentication
Configuring Web-Based Authentication
• You can globally configure the timeout, retransmission, and encryption key values for all RADIUS servers by using with the radius-server host global configuration command. If you want to configure these options on a per-server basis, use the radius-server timeout , radius-server retransmit , and the radius-server key global configuration commands. For more information, see the
Cisco IOS Security Configuration Guide, Release 12.2
and the
Cisco IOS Security Command Reference, Release 12.2
at this URL: http://www.cisco.com/en/US/docs/ios/12_2/security/command/reference/fsecur_r.html
Note You need to configure some settings on the RADIUS server, including: the switch IP address, the key string to be shared by both the server and the switch, and the downloadable ACL (DACL). For more information, see the RADIUS server documentation.
This example shows how to configure the RADIUS server parameters on a switch:
Switch(config)# ip radius source-interface Vlan80
Switch(config)# radius-server host 172.l20.39.46 test username user1
Switch(config)# radius-server key rad123
Switch(config)# radius-server dead-criteria tries 2
Configuring the HTTP Server
To use web-based authentication, you must enable the HTTP server within the switch. You can enable the server for either HTTP or HTTPS.
Step 1
Command ip http server
Step 2 ip http secure-server
Purpose
Enable the HTTP server. The web-based authentication feature uses the HTTP server to communicate with the hosts for user authentication.
Enable HTTPS.
You can configure custom authentication proxy web pages or specify a redirection URL for successful login.
Note To ensure secure authentication when you enter the ip http secure-secure command, the login page is always in HTTPS (secure HTTP) even if the user sends an HTTP request.
•
•
Customizing the Authentication Proxy Web Pages
Specifying a Redirection URL for Successful Login
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
9-13
Chapter 9 Configuring Web-Based Authentication
Configuring Web-Based Authentication
Customizing the Authentication Proxy Web Pages
You can configure web authentication to display four substitute HTML pages to the user in place of the switch default HTML pages during web-based authentication.
To specify the use of your custom authentication proxy web pages, first store your custom HTML files on the switch flash memory, then perform this task in global configuration mode:
Step 1
Step 2
Step 3
Step 4
Command ip admission proxy http login page file device:login-filename device:expired-filename ip admission proxy http success page file device:success-filename ip admission proxy http failure page file device:fail-filename ip admission proxy http login expired page file
Purpose
Specify the location in the switch memory file system of the custom HTML file to use in place of the default login page. The device: is flash memory.
Specify the location of the custom HTML file to use in place of the default login success page.
Specify the location of the custom HTML file to use in place of the default login failure page.
Specify the location of the custom HTML file to use in place of the default login expired page.
When configuring customized authentication proxy web pages, follow these guidelines:
• To enable the custom web pages feature, specify all four custom HTML files. If you specify fewer than four files, the internal default HTML pages are used.
•
•
The four custom HTML files must be present on the flash memory of the switch. The maximum size of each HTML file is 8 KB.
Any images on the custom pages must be on an accessible HTTP server. Configure an intercept ACL within the admission rule.
•
•
•
•
Any external link from a custom page requires configuration of an intercept ACL within the admission rule.
T o access a valid DNS server, any name resolution required for external links or images requires configuration of an intercept ACL within the admission rule.
If the custom web pages feature is enabled, a configured auth-proxy-banner is not used.
If the custom web pages feature is enabled, the redirection URL for successful login feature is not available.
• To remove the specification of a custom file, use the no form of the command.
Because the custom login page is a public web form, consider these guidelines for the page:
•
•
The login form must accept user entries for the username and password and must show them as uname and pwd .
The custom login page should follow best practices for a web form, such as page timeout, hidden password, and prevention of redundant submissions.
This example shows how to configure custom authentication proxy web pages:
Switch(config)# ip admission proxy http login page file flash:login.htm
Switch(config)# ip admission proxy http success page file flash:success.htm
Switch(config)# ip admission proxy http fail page file flash:fail.htm
Switch(config)# ip admission proxy http login expired page flash flash:expired.htm
9-14
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 9 Configuring Web-Based Authentication
Configuring Web-Based Authentication
This example shows how to verify the configuration of a custom authentication proxy web pages:
Switch# show ip admission configuration
Authentication proxy webpage
Login page : flash:login.htm
Success page : flash:success.htm
Fail Page : flash:fail.htm
Login expired Page : flash:expired.htm
Authentication global cache time is 60 minutes
Authentication global absolute time is 0 minutes
Authentication global init state time is 2 minutes
Authentication Proxy Session ratelimit is 100
Authentication Proxy Watch-list is disabled
Authentication Proxy Auditing is disabled
Max Login attempts per user is 5
Specifying a Redirection URL for Successful Login
You can specify a URL to which the user is redirected after authentication, effectively replacing the internal S uccess HTML page.
Command ip admission proxy http success redirect url-string
Purpose
Specify a URL for redirection of the user in place of the default login success page.
When configuring a redirection URL for successful login, consider these guidelines:
•
•
If the custom authentication proxy web pages feature is enabled, the redirection URL feature is disabled and is not available in the CLI. You can perform redirection in the custom-login success page.
If the redirection URL feature is enabled, a configured auth-proxy-banner is not used.
• To remove the specification of a redirection URL, use the no form of the command.
This example shows how to configure a redirection URL for successful login:
Switch(config)# ip admission proxy http success redirect www.cisco.com
This example shows how to verify the redirection URL for successful login:
Switch# show ip admission configuration
Authentication Proxy Banner not configured
Customizable Authentication Proxy webpage not configured
HTTP Authentication success redirect to URL: http://www.cisco.com
Authentication global cache time is 60 minutes
Authentication global absolute time is 0 minutes
Authentication global init state time is 2 minutes
Authentication Proxy Watch-list is disabled
Authentication Proxy Max HTTP process is 7
Authentication Proxy Auditing is disabled
Max Login attempts per user is 5
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
9-15
Chapter 9 Configuring Web-Based Authentication
Configuring Web-Based Authentication
Configuring the Web-Based Authentication Parameters
You can configure the maximum number of failed login attempts before the client is placed in a watch list for a waiting period.
Step 1
Step 2
Step 3
Step 4
Step 5
Command ip admission max-login-attempts end show ip admission configuration show ip admission cache number copy running-config startup-config
Purpose
Set the maximum number of failed login attempts. The range is 1 to 2147483647 attempts. The default is 5.
Returns to privileged EXEC mode.
Display the authentication proxy configuration.
Display the list of authentication entries.
(Optional) Save your entries in the configuration file.
This example shows how to set the maximum number of failed login attempts to 10:
Switch(config)# ip admission max-login-attempts 10
Configuring a Web Authentication Local Banner
Beginning in privileged EXEC mode, follow these steps to configure a local banner on a switch that has web authentication configured.
Step 1
Step 2
Step 3
Step 4
Command configure terminal ip admission auth-proxy-banner http
[ banner-text | file-path ] end copy running-config startup-config
Purpose
Enter global configuration mode.
Enable the local banner.
(Optional) Create a custom banner by entering C banner-text C, where
C is a delimiting character or a file-path indicates a file (for example, a logo or text file) that appears in the banner.
Return to privileged EXEC mode.
(Optional) Save your entries in the configuration file.
This example shows how to configure a local banner with the custom message My Switch :
Switch(config) configure terminal
Switch(config)# aaa new-model
Switch(config)# aaa ip auth-proxy auth-proxy-banner C My Switch C
Switch(config) end
For more information about the ip auth-proxy auth-proxy-banner command, see the “Authentication
Proxy Commands” section of the Cisco IOS Security Command Reference on Cisco.com.
9-16
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 9 Configuring Web-Based Authentication
Removing Web-Based Authentication Cache Entries
Displaying Web-Based Authentication Status
Command clear ip auth-proxy cache clear ip admission cache {
{
*
*
|
| host ip address host ip address }
}
Purpose
Delete authentication proxy entries. Use an asterisk to delete all cache entries. Enter a specific IP address to delete the entry for a single host.
Delete authentication proxy entries. Use an asterisk to delete all cache entries. Enter a specific IP address to delete the entry for a single host.
This example shows how to remove the web-based authentication session for the client at the IP address 209.165.201.1:
Switch# clear ip auth-proxy cache 209.165.201.1
Displaying Web-Based Authentication Status
Perform this task to display the web-based authentication settings for all interfaces or for specific ports:
Step 1
Command show authentication sessions
[ interface type slot/port ]
Purpose
Displays the web-based authentication settings.
type = fastethernet, gigabitethernet, or tengigabitethernet
(Optional) Use the interface keyword to display the web-based authentication settings for a specific interface.
This example shows how to view only the global web-based authentication status:
Switch# show authentication sessions
This example shows how to view the web-based authentication settings for gigabit interface 3/27:
Switch# show authentication sessions interface gigabitethernet 3/2
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
9-17
Displaying Web-Based Authentication Status
Chapter 9 Configuring Web-Based Authentication
9-18
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
C H A P T E R
10
Configuring Interface Characteristics
This chapter defines the types of interfaces on the switch and describes how to configure them. The chapter consists of these sections:
•
Understanding Interface Types, page 10-1
•
•
•
•
•
Using Interface Configuration Mode, page 10-7
Configuring Ethernet Interfaces, page 10-11
Configuring Layer 3 Interfaces, page 10-17
Configuring the System MTU, page 10-20
Monitoring and Maintaining the Interfaces, page 10-21
Note For complete syntax and usage information for the commands used in this chapter, see the switch command reference for this release and the online Cisco IOS Interface Command Reference,
Release 12.2.
Understanding Interface Types
This section describes the different types of interfaces supported by the switch with references to chapters that contain more detailed information about configuring these interface types. The rest of the chapter describes configuration procedures for physical interface characteristics.
These sections describe the interface types:
•
•
•
•
•
•
Switch Virtual Interfaces, page 10-4
EtherChannel Port Groups, page 10-6
Connecting Interfaces, page 10-6
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
10-1 OL-27326-01
Chapter 10 Configuring Interface Characteristics
Understanding Interface Types
Port-Based VLANs
A VLAN is a switched network that is logically segmented by function, team, or application, without regard to the physical location of the users.
For more information about VLANs, see Chapter 12,
“Configuring VLANs.” Packets received on a port are forwarded only to ports that belong to the same
VLAN as the receiving port. Network devices in different VLANs cannot communicate with one another without a Layer 3 device to route traffic between the VLANs.
VLAN partitions provide hard firewalls for traffic in the VLAN, and each VLAN has its own MAC address table. A VLAN comes into existence when a local port is configured to be associated with the
VLAN, when the VLAN Trunking Protocol (VTP) learns of its existence from a neighbor on a trunk, or when a user creates a VLAN.
To configure VLANs, use the vlan vlan-id global configuration command to enter VLAN configuration mode. The VLAN configurations for normal-range VLANs (VLAN IDs 1 to 1005) are saved in the
VLAN database. If VTP is version 1 or 2, to configure extended-range VLANs (VLAN IDs 1006 to
4094), you must first set VTP mode to transparent. Extended-range VLANs created in transparent mode are not added to the VLAN database but are saved in the switch running configuration. With VTP version 3, you can create extended-range VLANs in client or server mode. These VLANs are saved in the VLAN database.
Add ports to a VLAN by using the switchport interface configuration commands:
•
•
•
•
Identify the interface.
For a trunk port, set trunk characteristics, and if desired, define the VLANs to which it can belong.
For an access port, set and define the VLAN to which it belongs.
For a tunnel port, set and define the VLAN ID for the customer-specific VLAN tag. See
“Configuring IEEE 802.1Q and Layer 2 Protocol Tunneling.”
Switch Ports
Switch ports are Layer 2-only interfaces associated with a physical port. Switch ports belong to one or more VLANs. A switch port can be an access port, a trunk port, or a tunnel port. You can configure a port as an access port or trunk port or let the Dynamic Trunking Protocol (DTP) operate on a per-port basis to set the switchport mode by negotiating with the port on the other end of the link. You must manually configure tunnel ports as part of an asymmetric link connected to an IEEE 802.1Q trunk port. Switch ports are used for managing the physical interface and associated Layer 2 protocols and do not handle routing.
Configure switch ports by using the switchport interface configuration commands. Use the switchport command with no keywords to put an interface that is in Layer 3 mode into Layer 2 mode.
Note When you put an interface that is in Layer 3 mode into Layer 2 mode, the previous configuration information related to the affected interface might be lost, and the interface is returned to its default configuration.
For detailed information about configuring access port and trunk port characteristics, see
“Configuring VLANs.” For more information about tunnel ports, see
802.1Q and Layer 2 Protocol Tunneling.”
10-2
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 10 Configuring Interface Characteristics
Understanding Interface Types
Access Ports
An access port belongs to and carries the traffic of only one VLAN (unless it is configured as a voice
VLAN port). Traffic is received and sent in native formats with no VLAN tagging. Traffic arriving on an access port is assumed to belong to the VLAN assigned to the port. If an access port receives a tagged packet (Inter-Switch Link [ISL] or IEEE 802.1Q tagged), the packet is dropped, and the source address is not learned.
Two types of access ports are supported:
•
•
Static access ports are manually assigned to a VLAN (or through a RADIUS server for use with
IEEE 802.1x. For more information, see the
“802.1x Authentication with VLAN Assignment” section on page 8-16 .)
VLAN membership of dynamic access ports is learned through incoming packets. By default, a dynamic access port is not a member of any VLAN, and forwarding to and from the port is enabled only when the VLAN membership of the port is discovered. Dynamic access ports on the switch are assigned to a VLAN by a VLAN Membership Policy Server (VMPS). The VMPS can be a
Catalyst 6500 series switch; the Cisco Catalyst Blade Switch 3030 for Dell cannot be a VMPS server.
You can also configure an access port with an attached Cisco IP Phone to use one VLAN for voice traffic and another VLAN for data traffic from a device attached to the phone. For more information about voice
VLAN ports, see
Chapter 14, “Configuring Voice VLAN.”
Trunk Ports
A trunk port carries the traffic of multiple VLANs and by default is a member of all VLANs in the VLAN database. These trunk port types are supported:
• In an ISL trunk port, all received packets are expected to be encapsulated with an ISL header, and all transmitted packets are sent with an ISL header. Native (non-tagged) frames received from an
ISL trunk port are dropped.
• An IEEE 802.1Q trunk port supports simultaneous tagged and untagged traffic. An IEEE 802.1Q trunk port is assigned a default port VLAN ID (PVID), and all untagged traffic travels on the port default PVID. All untagged traffic and tagged traffic with a NULL VLAN ID are assumed to belong to the port default PVID. A packet with a VLAN ID equal to the outgoing port default PVID is sent untagged. All other traffic is sent with a VLAN tag.
Although by default, a trunk port is a member of every VLAN known to the VTP, you can limit VLAN membership by configuring an allowed list of VLANs for each trunk port. The list of allowed VLANs does not affect any other port but the associated trunk port. By default, all possible VLANs (VLAN ID 1 to 4094) are in the allowed list. A trunk port can become a member of a VLAN only if VTP knows of the VLAN and if the VLAN is in the enabled state. If VTP learns of a new, enabled VLAN and the VLAN is in the allowed list for a trunk port, the trunk port automatically becomes a member of that VLAN and traffic is forwarded to and from the trunk port for that VLAN. If VTP learns of a new, enabled VLAN that is not in the allowed list for a trunk port, the port does not become a member of the VLAN, and no traffic for the VLAN is forwarded to or from the port.
For more information about trunk ports, see Chapter 12, “Configuring VLANs.”
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
10-3
Chapter 10 Configuring Interface Characteristics
Understanding Interface Types
Tunnel Ports
Tunnel ports are used in IEEE 802.1Q tunneling to segregate the traffic of customers in a service-provider network from other customers who are using the same VLAN number. You configure an asymmetric link from a tunnel port on a service-provider edge switch to an IEEE 802.1Q trunk port on the customer switch. Packets entering the tunnel port on the edge switch, already
IEEE 802.1Q-tagged with the customer VLANs, are encapsulated with another layer of an IEEE 802.1Q tag (called the metro tag), containing a VLAN ID unique in the service-provider network, for each customer. The double-tagged packets go through the service-provider network keeping the original customer VLANs separate from those of other customers. At the outbound interface, also a tunnel port, the metro tag is removed, and the original VLAN numbers from the customer network are retrieved.
Tunnel ports cannot be trunk ports or access ports and must belong to a VLAN unique to each customer.
For more information about tunnel ports, see
Chapter 16, “Configuring IEEE 802.1Q and Layer 2
Routed Ports
A routed port is a physical port that acts like a port on a router; it does not have to be connected to a router. A routed port is not associated with a particular VLAN, as is an access port. A routed port behaves like a regular router interface, except that it does not support VLAN subinterfaces. Routed ports can be configured with a Layer 3 routing protocol. A routed port is a Layer 3 interface only and does not support
Layer 2 protocols, such as DTP and STP.
Configure routed ports by putting the interface into Layer 3 mode with the no switchport interface configuration command. Then assign an IP address to the port, enable routing, and assign routing protocol characteristics by using the ip routing and router protocol global configuration commands.
Note Entering a no switchport interface configuration command shuts down the interface and then re-enables it, which might generate messages on the device to which the interface is connected. When you put an interface that is in Layer 2 mode into Layer 3 mode, the previous configuration information related to the affected interface might be lost.
The number of routed ports that you can configure is not limited by software. However, the interrelationship between this number and the number of other features being configured might impact
CPU performance because of hardware limitations. See the
“Configuring Layer 3 Interfaces” section on page 10-17
for information about what happens when hardware resource limitations are reached.
For more information about IP unicast routing and routing protocols, see
Switch Virtual Interfaces
A switch virtual interface (SVI) represents a VLAN of switch ports as one interface to the routing or bridging function in the system. Only one SVI can be associated with a VLAN, but you need to configure an SVI for a VLAN only when you wish to route between VLANs, to fallback-bridge nonroutable protocols between VLANs, or to provide IP host connectivity to the switch. By default, an SVI is created for the default VLAN (VLAN 1) to permit remote switch administration. Additional SVIs must be explicitly configured.
10-4
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 10 Configuring Interface Characteristics
Understanding Interface Types
Note You cannot delete interface VLAN 1.
SVIs provide IP host connectivity only to the system; in Layer 3 mode, you can configure routing across
SVIs.
Although the switch supports a total or 1005 VLANs (and SVIs), the interrelationship between the number of SVIs and routed ports and the number of other features being configured might impact CPU performance because of hardware limitations. See the
“Configuring Layer 3 Interfaces” section on page 10-17
for information about what happens when hardware resource limitations are reached.
SVIs are created the first time that you enter the vlan interface configuration command for a VLAN interface. The VLAN corresponds to the VLAN tag associated with data frames on an ISL or
IEEE 802.1Q encapsulated trunk or the VLAN ID configured for an access port. Configure a VLAN interface for each VLAN for which you want to route traffic, and assign it an IP address. For more information, see the
“Manually Assigning IP Information” section on page 3-14
.
Note When you create an SVI, it does not become active until it is associated with a physical port.
SVIs support routing protocols and bridging configurations. For more information about configuring IP routing, see
Chapter 36, “Configuring IP Unicast Routing.”
SVI Autostate Exclude
The line state of an SVI with multiple ports on a VLAN is in the up state when it meets these conditions:
•
•
•
The VLAN exists and is active in the VLAN database on the switch.
The VLAN interface exists and is not administratively down.
At least one Layer 2 (access or trunk) port exists, has a link in the the spanning-tree forwarding state on the VLAN.
up state on this VLAN, and is in
Note The protocol link state for VLAN interfaces come up when the first switchport belonging to the corresponding VLAN link comes up and is in STP forwarding state.
The default action, when a VLAN has multiple ports, is that the SVI goes down when all ports in the
VLAN go down. You can use the SVI autostate exclude feature to configure a port so that it is not included in the SVI line-state up-an- down calculation. For example, if the only active port on the VLAN is a monitoring port, you might configure autostate exclude on that port so that the VLAN goes down when all other ports go down. When enabled on a port, autostate exclude applies to all VLANs that are enabled on that port.
The VLAN interface is brought up when one Layer 2 port in the VLAN has had time to converge
(transition from STP listening-learning state to forwarding state). This prevents features such as routing protocols from using the VLAN interface as if it were fully operational and minimizes other problems, such as routing black holes. For information about configuring autostate exclude, see the
SVI Autostate Exclude” section on page 10-19 .
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
10-5
Chapter 10 Configuring Interface Characteristics
Understanding Interface Types
EtherChannel Port Groups
EtherChannel port groups treat multiple switch ports as one switch port. These port groups act as a single logical port for high-bandwidth connections between switches or between switches and servers. An
EtherChannel balances the traffic load across the links in the channel. If a link within the EtherChannel fails, traffic previously carried over the failed link changes to the remaining links. You can group multiple trunk ports into one logical trunk port or multiple access ports into one logical access port.
Most protocols operate over either single ports or aggregated switch ports and do not recognize the physical ports within the port group. Exceptions are the DTP, the Cisco Discovery Protocol (CDP), and the Port Aggregation Protocol (PAgP), which operate only on physical ports.
When you configure an EtherChannel, you create a port-channel logical interface and assign an interface to the EtherChannel. For Layer 3 interfaces, you manually create the logical interface by using the interface port-channel global configuration command. Then you manually assign an interface to the
EtherChannel by using the channel-group interface configuration command. For Layer 2 interfaces, use the channel-group interface configuration command to dynamically create the port-channel logical interface. This command binds the physical and logical ports together. For more information, see
Chapter 35, “Configuring EtherChannels and Layer 2 Trunk Failover.”
Connecting Interfaces
Devices within a single VLAN can communicate directly through any switch. Ports in different VLANs cannot exchange data without going through a routing device. In the configuration shown in
, when Blade Server A in VLAN 20 sends data to Blade Server B in VLAN 30, the data must go from
Blade Server A to the switch, to the router, back to the switch, and then to Blade Server B.
Figure 10-1 Connecting VLANs with Layer 2 Switches
Cisco router
Blade Switch
Blade
Server A
Blade
Server B
VLAN 20 VLAN 30
By using the switch with routing enabled, when you configure both VLAN 20 and VLAN 30 with an
SVI to which an IP address is assigned, packets can be sent from Host A to Host B directly through the switch with no need for an external router.
10-6
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 10 Configuring Interface Characteristics
Using Interface Configuration Mode
The switch supports basic routing (static routing and RIP). Whenever possible, to maintain high performance, forwarding is done by the switch hardware. However, only IP Version 4 packets with
Ethernet II encapsulation can be routed in hardware. Non-IP traffic and traffic with other encapsulation methods can be fallback-bridged by hardware.
The routing function can be enabled on all SVIs and routed ports. The switch routes only IP traffic. When
IP routing protocol parameters and address configuration are added to an SVI or routed port, any IP traffic received from these ports is routed. For more information, see
Using Interface Configuration Mode
The switch supports these interface types:
• Physical ports—switch ports and routed ports
•
•
VLANs—switch virtual interfaces
Port channels—EtherChannel interfaces
You can also configure a range of interfaces (see the
“Configuring a Range of Interfaces” section on page 10-8
).
To configure a physical interface (port), specify the interface type, module number, and switch port number, and enter interface configuration mode.
•
•
Type—Gigabit Ethernet (gigabitethernet or gi) for 10/100/1000 Mb/s Ethernet port or small form-factor pluggable (SFP) module Gigabit Ethernet interfaces.
Module number—The module or slot number on the switch (always 0 on the Cisco Catalyst Blade
Switch 3030 for Dell).
• Port number—The interface number of the switch port. The port numbers of the internal Gigabit
Ethernet ports are from 1 to 10 (for example, gigabitethernet 0/6). The port numbers of the two
10/100/1000 ports on the front of the switch are 11 and 12 (for example, gigabitethernet 0/11). The port numbers of the SFP module ports are from 13 to16 (for example, gigabitethernet 0/14).
You can identify physical interfaces by physically checking the interface location on the switch. You can also use the show privileged EXEC commands to display information about a specific interface or all the interfaces on the switch. The remainder of this chapter primarily provides physical interface configuration procedures.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
10-7
Chapter 10 Configuring Interface Characteristics
Using Interface Configuration Mode
Procedures for Configuring Interfaces
These general instructions apply to all interface configuration processes.
Step 1
Step 2
Enter the configure terminal command at the privileged EXEC prompt:
Switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)#
Enter the interface global configuration command. Identify the interface type and the number of the connector. In this example, Gigabit Ethernet port 1 is selected:
Switch(config)# interface gigabitethernet0/1
Switch(config-if)#
Note You do not need to add a space between the interface type and interface number. For example, in the preceding line, you can specify either gigabitethernet 0/1 , gigabitethernet0/1 , gi 0/1 , or gi0/1 .
Step 3
Step 4
Follow each interface command with the interface configuration commands that the interface requires.
The commands that you enter define the protocols and applications that will run on the interface. The commands are collected and applied to the interface when you enter another interface command or enter end to return to privileged EXEC mode.
You can also configure a range of interfaces by using the interface range or interface range macro global configuration commands. Interfaces configured in a range must be the same type and must be configured with the same feature options.
After you configure an interface, verify its status by using the show privileged EXEC commands listed in the
“Monitoring and Maintaining the Interfaces” section on page 10-21 .
Enter the show interfaces privileged EXEC command to see a list of all interfaces on or configured for the switch. A report is provided for each interface that the device supports or for the specified interface.
Configuring a Range of Interfaces
You can use the interface range global configuration command to configure multiple interfaces with the same configuration parameters. When you enter the interface-range configuration mode, all command parameters that you enter are attributed to all interfaces within that range until you exit this mode.
10-8
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 10 Configuring Interface Characteristics
Using Interface Configuration Mode
Beginning in privileged EXEC mode, follow these steps to configure a range of interfaces with the same parameters:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Command configure terminal interface range macro_name }
{ port-range | macro end show interfaces [ interface-id ] copy running-config startup-config
Purpose
Enter global configuration mode.
Specify the range of interfaces (VLANs or physical ports) to be configured, and enter interface-range configuration mode.
•
•
You can use the interface range command to configure up to five port ranges or a previously defined macro.
The macro variable is explained in the
Interface Range Macros” section on page 10-10
.
•
•
In a comma-separated port-range , you must enter the interface type for each entry and enter spaces before and after the comma.
In a hyphen-separated port-range , you do not need to re-enter the interface type, but you must enter a space before the hyphen.
Use the normal configuration commands to apply the configuration parameters to all interfaces in the range. Each command is executed as it is entered.
Return to privileged EXEC mode.
Verify the configuration of the interfaces in the range.
(Optional) Save your entries in the configuration file.
When using the interface range global configuration command, note these guidelines:
• Valid entries for port-range :
–
– vlan vlan-ID - vlan-ID , where the VLAN ID is 1 to 4094 gigabitethernet module/{ first port } - { last port }, where the module is always 0
– port-channel port-channel-number - port-channel-number , where the port-channel-number is 1 to 48
Note When you use the interface range command with port channels, the first and last port-channel number must be active port channels.
•
•
You must add a space between the first interface number and the hyphen when using the interface range command. For example, the command interface range gigabitethernet0/1 - 4 is a valid range; the command interface range gigabitethernet0/1-4 is not a valid range.
The interface range command only works with VLAN interfaces that have been configured with the interface vlan command. The show running-config privileged EXEC command displays the configured VLAN interfaces. VLAN interfaces not displayed by the show running-config command cannot be used with the interface range command.
• All interfaces defined in a range must be the same type (all Gigabit Ethernet ports, all EtherChannel ports, or all VLANs), but you can enter multiple ranges in a command.
This example shows how to use the interface range global configuration command to set the speed on ports 1 to 4 to 100 Mb/s:
Switch# configure terminal
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01 10-9
Chapter 10 Configuring Interface Characteristics
Using Interface Configuration Mode
Switch(config)# interface range gigabitethernet0/1 - 4
Switch(config-if-range)# speed 100
If you enter multiple configuration commands while you are in interface-range mode, each command is executed as it is entered. The commands are not batched and executed after you exit interface-range mode. If you exit interface-range configuration mode while the commands are being executed, some commands might not be executed on all interfaces in the range. Wait until the command prompt reappears before exiting interface-range configuration mode.
Configuring and Using Interface Range Macros
You can create an interface range macro to automatically select a range of interfaces for configuration.
Before you can use the macro keyword in the interface range macro global configuration command string, you must use the define interface-range global configuration command to define the macro.
Beginning in privileged EXEC mode, follow these steps to define an interface range macro:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Command configure terminal define interface-range macro_name interface-range interface range macro macro_name end show running-config | include define copy running-config startup-config
Purpose
Enter global configuration mode.
Define the interface-range macro, and save it in NVRAM.
•
•
The macro_name is a 32-character maximum character string.
A macro can contain up to five comma-separated interface ranges.
• Each interface-range must consist of the same port type.
Select the interface range to be configured using the values saved in the interface-range macro called macro_name.
You can now use the normal configuration commands to apply the configuration to all interfaces in the defined macro.
Return to privileged EXEC mode.
Show the defined interface range macro configuration.
(Optional) Save your entries in the configuration file.
Use the no define interface-range macro_name global configuration command to delete a macro.
When using the define interface-range global configuration command, note these guidelines:
• Valid entries for interface-range :
– vlan vlan-ID - vlan-ID , where the VLAN ID is 1 to 4094
–
– gigabitethernet module/{ first port } - { last port }, where the module is always 0 port-channel port-channel-number - port-channel-number , where the port-channel-number is 1 to 48.
Note When you use the interface ranges with port channels, the first and last port-channel number must be active port channels.
• You must add a space between the first interface number and the hyphen when entering an interface-range . For example, gigabitethernet0/1 - 4 is a valid range; gigabitethernet0/1-4 is not a valid range.
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
10-10 OL-27326-01
Chapter 10 Configuring Interface Characteristics
Configuring Ethernet Interfaces
• The VLAN interfaces must have been configured with the interface vlan command. The show running-config privileged EXEC command displays the configured VLAN interfaces. VLAN interfaces not displayed by the show running-config command cannot be used as interface-ranges .
• All interfaces defined as in a range must be the same type (all Gigabit Ethernet ports, all
EtherChannel ports, or all VLANs), but you can combine multiple interface types in a macro.
This example shows how to define an interface-range named enet_list to include ports 1 and 2 and to verify the macro configuration:
Switch# configure terminal
Switch(config)# define interface-range enet_list gigabitethernet0/1 - 2
Switch(config)# end
Switch# show running-config | include define define interface-range enet_list GigabitEthernet0/1 - 2
This example shows how to create a multiple-interface macro named macro1 :
Switch# configure terminal
Switch(config)# define interface-range macro1 gigabitethernet0/1 - 2, gigabitethernet0/11
- 16
Switch(config)# end
This example shows how to enter interface-range configuration mode for the interface-range macro enet_list :
Switch# configure terminal
Switch(config)# interface range macro enet_list
Switch(config-if-range)#
This example shows how to delete the interface-range macro enet_list and to verify that it was deleted.
Switch# configure terminal
Switch(config)# no define interface-range enet_list
Switch(config)# end
Switch# show run | include define
Switch#
Configuring Ethernet Interfaces
These sections contain this configuration information:
•
•
•
•
•
Default Ethernet Interface Configuration, page 10-12
Configuring Interface Speed and Duplex Mode, page 10-13
Configuring IEEE 802.3x Flow Control, page 10-15
Configuring Auto-MDIX on an Interface, page 10-16
Adding a Description for an Interface, page 10-17
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
10-11
Chapter 10 Configuring Interface Characteristics
Configuring Ethernet Interfaces
Default Ethernet Interface Configuration
to Layer 2 interfaces. For more details on the VLAN parameters listed in the table, see
For details on controlling traffic to the port, see Chapter 24, “Configuring
Note To configure Layer 2 parameters, if the interface is in Layer 3 mode, you must enter the switchport interface configuration command without any parameters to put the interface into Layer 2 mode. This shuts down the interface and then re-enables it, which might generate messages on the device to which the interface is connected. When you put an interface that is in Layer 3 mode into Layer 2 mode, the previous configuration information related to the affected interface might be lost, and the interface is returned to its default configuration.
Table 10-1 Default Layer 2 Ethernet Interface Configuration
Feature
Operating mode
Native VLAN (for IEEE 802.1Q trunks)
VLAN trunking
Default Setting
Layer 2 or switching mode ( switchport command).
Allowed VLAN range VLANs 1 to 4094.
Default VLAN (for access ports) VLAN 1 (Layer 2 interfaces only).
VLAN 1 (Layer 2 interfaces only).
Switchport mode dynamic auto (supports DTP) (Layer 2 interfaces only).
Port enable state
Port description
Speed
Duplex mode
Flow control
EtherChannel (PAgP)
All ports are enabled.
None defined.
Autonegotiate.
Autonegotiate.
Port blocking (unknown multicast and unknown unicast traffic)
Broadcast, multicast, and unicast storm control
Protected port
Port security
Port Fast
Flow control is set to receive : off . It is always off for sent packets.
Disabled on all Ethernet ports. See Chapter 35, “Configuring
EtherChannels and Layer 2 Trunk Failover.”
Disabled (not blocked) (Layer 2 interfaces only). See the
“Configuring Port Blocking” section on page 24-7
.
Disabled. See the
“Default Storm Control Configuration” section on page 24-3 .
Disabled (Layer 2 interfaces only). See the
Disabled (Layer 2 interfaces only). See the
Configuration” section on page 24-11 .
Disabled. See the
“Default Optional Spanning-Tree
Configuration” section on page 19-9 .
10-12
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 10 Configuring Interface Characteristics
Configuring Ethernet Interfaces
Table 10-1
Feature
Auto-MDIX
Default Layer 2 Ethernet Interface Configuration (continued)
Keepalive messages
Default Setting
Enabled.
Note The switch might not support a pre-standard powered device—such as Cisco IP phones and access points that do not fully support IEEE 802.3af—if that powered device is connected to the switch through a crossover cable. This is regardless of whether auto-MIDX is enabled on the switch port.
Disabled on SFP module ports; enabled on all other ports.
Configuring Interface Speed and Duplex Mode
Ethernet interfaces on the switch operate at 10, 100, or 1000 Mb/s and in either full- or half-duplex mode.
In full-duplex mode, two stations can send and receive traffic at the same time. Normally, 10-Mb/s ports operate in half-duplex mode, which means that stations can either receive or send traffic.
Switch models include Gigabit Ethernet (10/100/1000-Mb/s) ports and small form-factor pluggable
(SFP) module slots supporting SFP modules.
These sections describe how to configure the interface speed and duplex mode:
•
Speed and Duplex Configuration Guidelines, page 10-13
•
Setting the Interface Speed and Duplex Parameters, page 10-14
Speed and Duplex Configuration Guidelines
When configuring an interface speed and duplex mode, note these guidelines:
• Gigabit Ethernet (10/100/1000-Mb/s) ports support all speed options and all duplex options (auto, half, and full). However, Gigabit Ethernet ports operating at 1000 Mb/s do not support half-duplex mode.
• For SFP module ports, the speed and duplex CLI options change depending on the SFP module type:
– The 1000BASEx (where x is -BX, -CWDM, -LX, -SX, and -ZX) SFP module ports support the nonegotiate keyword in the speed interface configuration command. Duplex options are not supported.
•
–
–
The 1000BASE-T SFP module ports support the same speed and duplex options as the
10/100/1000-Mbps ports.
The 100BASEx (where x is -BX, -CWDM, -LX, -SX, and -ZX) SFP module ports support only
100 Mbps. These modules support full- and half- duplex options but do not support autonegotiation.
For information about which SFP modules are supported on your switch, see the product release notes.
You cannot configure duplex mode on SFP module ports; they operate in full-duplex mode except in these situations:
–
–
You can configure Cisco 1000BASE-T SFP modules for auto, full, or half-duplex mode.
Cisco 1000BASE-SX SFP modules can operate only in full-duplex mode.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
10-13
Chapter 10 Configuring Interface Characteristics
Configuring Ethernet Interfaces
•
•
•
•
If you are connected to a device that does not support autonegotiation, you can configure speed on copper SFP module ports; however, you can only configure fiber SFP module ports to not negotiate
( nonegotiate ).
If both ends of the line support autonegotiation, we highly recommend the default setting of auto negotiation.
If one interface supports autonegotiation and the other end does not, configure duplex and speed on both interfaces; do not use the auto setting on the supported side.
When STP is enabled and a port is reconfigured, the switch can take up to 30 seconds to check for loops. The port LED is amber while STP reconfigures.
Caution Changing the interface speed and duplex mode configuration might shut down and re-enable the interface during the reconfiguration.
Setting the Interface Speed and Duplex Parameters
Beginning in privileged EXEC mode, follow these steps to set the speed and duplex mode for a physical interface:
Step 1
Step 2
Command configure terminal interface interface-id
Step 3 speed { 10 | 100 | 1000 | auto [ 10 | 100 |
1000 ] | nonegotiate }
Step 4
Step 5
Step 6
Step 7 duplex { auto | full | half } end
show interfaces interface-id copy running-config startup-config
Purpose
Enter global configuration mode.
Specify the physical interface to be configured, and enter interface configuration mode.
Enter the appropriate speed parameter for the interface:
• Enter 10 , 100 , or 1000 to set a specific speed for the interface.
The 1000 keyword is available only for 10/100/1000 Mb/s ports.
•
•
Enter auto to enable the interface to autonegotiate speed with the connected device. If you use the 10 , 100 , or the 1000 keywords with the auto keyword, the port autonegotiates only at the specified speeds.
The nonegotiate keyword is available only for SFP module ports.
SFP module ports operate only at 1000 Mb/s but can be configured to not negotiate if connected to a device that does not support autonegotiation.
For more information about speed settings, see the “Speed and Duplex
Configuration Guidelines” section on page 10-13 .
Enter the duplex parameter for the interface.
Enable half-duplex mode (for interfaces operating only at 10 or
100 Mb/s). You cannot configure half-duplex mode for interfaces operating at 1000 Mb/s.
For more information about duplex settings, see the
Duplex Configuration Guidelines” section on page 10-13
.
Return to privileged EXEC mode.
Display the interface speed and duplex mode configuration.
(Optional) Save your entries in the configuration file.
10-14
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 10 Configuring Interface Characteristics
Configuring Ethernet Interfaces
Use the no speed and no duplex interface configuration commands to return the interface to the default speed and duplex settings (autonegotiate). To return all interface settings to the defaults, use the default interface interface-id interface configuration command.
This example shows how to set the interface speed to 100 Mb/s on a 10/100/1000 Mb/s port:
Switch# configure terminal
Switch(config)# interface gigabitethernet0/2
Switch(config-if)# speed 100
Configuring IEEE 802.3x Flow Control
Flow control enables connected Ethernet ports to control traffic rates during congestion by allowing congested nodes to pause link operation at the other end. If one port experiences congestion and cannot receive any more traffic, it notifies the other port by sending a pause frame to stop sending until the condition clears. Upon receipt of a pause frame, the sending device stops sending any data packets, which prevents any loss of data packets during the congestion period.
Note Cisco Catalyst Blade Switch 3030 for Dellports can receive, but not send, pause frames.
You use the flowcontrol interface configuration command to set the interface’s ability to receive pause frames to on , off , or desired . The default state is off .
When set to desired , an interface can operate with an attached device that is required to send flow-control packets or with an attached device that is not required to but can send flow-control packets.
These rules apply to flow control settings on the device:
• receive on (or desired ): The port cannot send pause frames but can operate with an attached device that is required to or can send pause frames; the port can receive pause frames.
• receive off : Flow control does not operate in either direction. In case of congestion, no indication is given to the link partner, and no pause frames are sent or received by either device.
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Note For details on the command settings and the resulting flow control resolution on local and remote ports, see the flowcontrol interface configuration command in the command reference for this release.
Beginning in privileged EXEC mode, follow these steps to configure flow control on an interface:
Command configure terminal interface interface-id flowcontrol { receive } { on | off | desired } end show interfaces interface-id copy running-config startup-config
Purpose
Enter global configuration mode
Specify the physical interface to be configured, and enter interface configuration mode.
Configure the flow control mode for the port.
Return to privileged EXEC mode.
Verify the interface flow control settings.
(Optional) Save your entries in the configuration file.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
10-15
Chapter 10 Configuring Interface Characteristics
Configuring Ethernet Interfaces
To disable flow control, use the flowcontrol receive off interface configuration command.
This example shows how to turn on flow control on a port:
Switch# configure terminal
Switch(config)# interface gigabitethernet0/1
Switch(config-if)# flowcontrol receive on
Switch(config-if)# end
Configuring Auto-MDIX on an Interface
When automatic medium-dependent interface crossover (auto-MDIX) is enabled on an interface, the interface automatically detects the required cable connection type (straight through or crossover) and configures the connection appropriately. When connecting switches without the auto-MDIX feature, you must use straight-through cables to connect to devices such as servers, workstations, or routers and crossover cables to connect to other switches or repeaters. With auto-MDIX enabled, you can use either type of cable to connect to other devices, and the interface automatically corrects for any incorrect cabling. For more information about cabling requirements, see the hardware installation guide.
Auto-MDIX is enabled by default. When you enable auto-MDIX, you must also set the interface speed and duplex to auto so that the feature operates correctly. Auto-MDIX is supported on all
10/100/1000-Mb/s interfaces and on 10/100/1000BASE-T SFP-module interfaces. It is not supported on
1000BASE-SX or -LX SFP module interfaces.
Table 10-2 Link Conditions and Auto-MDIX Settings
Local Side Auto-MDIX Remote Side Auto-MDIX With Correct Cabling
On On Link up
On
Off
Off
Off
On
Off
Link up
Link up
Link up
With Incorrect Cabling
Link up
Link up
Link up
Link down
Beginning in privileged EXEC mode, follow these steps to configure auto-MDIX on an interface:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Command configure terminal interface interface-id speed auto duplex auto
Purpose
Enter global configuration mode
Specify the physical interface to be configured, and enter interface configuration mode.
Configure the interface to autonegotiate speed with the connected device.
Configure the interface to autonegotiate duplex mode with the connected device.
mdix auto end
Enable auto-MDIX on the interface.
Return to privileged EXEC mode.
show controllers ethernet-controller interface-id phy
Verify the operational state of the auto-MDIX feature on the interface.
copy running-config startup-config (Optional) Save your entries in the configuration file.
10-16
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 10 Configuring Interface Characteristics
Configuring Layer 3 Interfaces
To disable auto-MDIX, use the no mdix auto interface configuration command.
This example shows how to enable auto-MDIX on a port:
Switch# configure terminal
Switch(config)# interface gigabitethernet0/1
Switch(config-if)# speed auto
Switch(config-if)# duplex auto
Switch(config-if)# mdix auto
Switch(config-if)# end
Adding a Description for an Interface
You can add a description about an interface to help you remember its function. The description appears in the output of these privileged EXEC commands: show configuration , show running-config , and show interfaces .
Beginning in privileged EXEC mode, follow these steps to add a description for an interface:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Command configure terminal interface interface-id description string end show interfaces interface-id description or show running-config copy running-config startup-config
Purpose
Enter global configuration mode.
Specify the interface for which you are adding a description, and enter interface configuration mode.
Add a description (up to 240 characters) for an interface.
Return to privileged EXEC mode.
Verify your entry.
(Optional) Save your entries in the configuration file.
Use the no description interface configuration command to delete the description.
This example shows how to add a description on a port and how to verify the description:
Switch# config terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# interface gigabitethernet0/2
Switch(config-if)# description Connects to Marketing
Switch(config-if)# end
Switch# show interfaces gigabitethernet0/2 description
Interface Status Protocol Description
Gi0/2 admin down down Connects to Marketing
Configuring Layer 3 Interfaces
The switch supports these types of Layer 3 interfaces:
• SVIs: You should configure SVIs for any VLANs for which you want to route traffic. SVIs are created when you enter a VLAN ID following the interface vlan global configuration command. To delete an SVI, use the no interface vlan global configuration command. You cannot delete interface
VLAN 1.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
10-17
Chapter 10 Configuring Interface Characteristics
Configuring Layer 3 Interfaces
Note When you create an SVI, it does not become active until it is associated with a physical port.
For information about assigning Layer 2 ports to VLANs, see Chapter 12, “Configuring
•
When configuring SVIs, you can also configure SVI autostate exclude on a port in the SVI to
exclude that port from being included in determining SVI line-state status. See the “Configuring SVI
Autostate Exclude” section on page 10-19
.
Routed ports: Routed ports are physical ports configured to be in Layer 3 mode by using the no switchport interface configuration command.
•
•
Layer 3 EtherChannel ports: EtherChannel interfaces made up of routed ports.
EtherChannel port interfaces are described in
Chapter 35, “Configuring EtherChannels and Layer 2
A Layer 3 switch can have an IP address assigned to each routed port and SVI.
There is no defined limit to the number of SVIs and routed ports that can be configured in a switch stack.
However, the interrelationship between the number of SVIs and routed ports and the number of other features being configured might have an impact on CPU usage because of hardware limitations. If the switch is using maximum hardware resources, attempts to create a routed port or SVI have these results:
• If you try to create a new routed port, the switch generates a message that there are not enough resources to convert the interface to a routed port, and the interface remains as a switchport.
If you try to create an extended-range VLAN, an error message is generated, and the extended-range
VLAN is rejected.
•
•
If the switch is notified by VLAN Trunking Protocol (VTP) of a new VLAN, it sends a message that there are not enough hardware resources available and shuts down the VLAN. The output of the show vlan user EXEC command shows the VLAN in a suspended state.
If the switch attempts to boot up with a configuration that has more VLANs and routed ports than hardware can support, the VLANs are created, but the routed ports are shut down, and the switch sends a message that this was due to insufficient hardware resources.
All Layer 3 interfaces require an IP address to route traffic. This procedure shows how to configure an interface as a Layer 3 interface and how to assign an IP address to an interface.
Note If the physical port is in Layer 2 mode (the default), you must enter the no switchport interface configuration command to put the interface into Layer 3 mode. Entering a no switchport command disables and then re-enables the interface, which might generate messages on the device to which the interface is connected. Furthermore, when you put an interface that is in Layer 2 mode into Layer 3 mode, the previous configuration information related to the affected interface might be lost, and the interface is returned to its default configuration
Beginning in privileged EXEC mode, follow these steps to configure a Layer 3 interface:
Step 1
Step 2
Step 3
Command configure terminal
Purpose
Enter global configuration mode.
interface {{ fastethernet | gigabitethernet } interface-id }
| { vlan vlan-id } | { port-channel port-channel-number } no switchport
Specify the interface to be configured as a Layer 3 interface, and enter interface configuration mode.
For physical ports only, enter Layer 3 mode.
10-18
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 10 Configuring Interface Characteristics
Configuring Layer 3 Interfaces
Step 4
Step 5
Step 6
Step 7
Step 8
Command ip address ip_address subnet_mask no shutdown end show interfaces [ interface-id ] show ip interface [ interface-id ] show running-config interface [ interface-id ] copy running-config startup-config
Purpose
Configure the IP address and IP subnet.
Enable the interface.
Return to privileged EXEC mode.
Verify the configuration.
(Optional) Save your entries in the configuration file.
To remove an IP address from an interface, use the no ip address interface configuration command.
This example shows how to configure a port as a routed port and to assign it an IP address:
Switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# interface gigabitethernet0/2
Switch(config-if)# no switchport
Switch(config-if)# ip address 192.20.135.21 255.255.255.0
Switch(config-if)# no shutdown
Configuring SVI Autostate Exclude
Configuring SVI autostate exclude on an access or trunk port in an SVI excludes that port in the calculation of the status of the SVI line state (up or down) even if it belongs to the same VLAN. When the excluded port is in the up state, and all other ports in the VLAN are in the down state, the SVI state is changed to down.
At least one port in the VLAN should be up and not excluded to keep the SVI state up. You can use this command to exclude the monitoring port status when determining the status of the SVI.
Beginning in privileged EXEC mode, follow these steps to exclude a port from SVI state-change calculations:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Command configure terminal interface interface-id switchport autostate exclude end show running config interface interface-id show interface interface-id switchport copy running-config startup-config
Purpose
Enter global configuration mode.
Specify a Layer 2 interface (physical port or port channel), and enter interface configuration mode.
Exclude the access or trunk port when defining the status of an SVI line state (up or down)
Return to privileged EXEC mode.
(Optional) Show the running configuration.
Verify the configuration.
(Optional) Save your entries in the configuration file.
This example shows how to configure an access or trunk port in an SVI to be excluded from the status calculation:
Switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
10-19
Chapter 10 Configuring Interface Characteristics
Configuring the System MTU
Switch(config)# interface gigabitethernet0/2
Switch(config-if)# switchport autostate exclude
Switch(config-if)# exit
Configuring the System MTU
The default maximum transmission unit (MTU) size for frames received and transmitted on all interfaces on the switch is 1500 bytes. You can increase the MTU size for all interfaces operating at 10 or 100 Mb/s by using the system mtu global configuration command. You can increase the MTU size to support jumbo frames on all Gigabit Ethernet interfaces by using the system mtu jumbo global configuration command. You can change the MTU size for routed ports by using the system mtu routing global configuration command.
Note You cannot configure a routing MTU size that exceeds the system MTU size. If you change the system
MTU size to a value smaller than the currently configured routing MTU size, the configuration change is accepted, but not applied until the next switch reset. When the configuration change takes effect, the routing MTU size automatically defaults to the new system MTU size.
Gigabit Ethernet ports are not affected by the system mtu command; 10/100 ports are not affected by the system mtu jumbo command. If you do not configure the system mtu jumbo command, the setting of the system mtu command applies to all Gigabit Ethernet interfaces.
You cannot set the MTU size for an individual interface; you set it for all 10/100 or all Gigabit Ethernet interfaces on the switch. When you change the system or jumbo MTU size, you must reset the switch before the new configuration takes effect.The system mtu routing command does not require a switch reset to take effect.
Frames sizes that can be received by the switch CPU are limited to 1998 bytes, no matter what value was entered with the system mtu or system mtu jumbo commands. Although frames that are forwarded or routed are typically not received by the CPU, in some cases packets are sent to the CPU, such as traffic sent to control traffic, SNMP, or Telnet, or routing protocols.
Routed packets are subjected to MTU checks on the output ports. The MTU value used for routed ports is derived from the applied system mtu value (not the system mtu jumbo value). That is, the routed
MTU is never greater than the system MTU for any VLAN. The routing protocols use the system MTU value when negotiating adjacencies and the MTU of the link. To view the MTU value for routed packets for a specific VLAN, use the show platform port-asic mvid privileged EXEC command.
Note If Layer 2 Gigabit Ethernet interfaces are configured to accept frames greater than the 10/100 interfaces, jumbo frames received on a Layer 2 Gigabit Ethernet interface and sent on a Layer 2 10/100 interface are dropped.
Beginning in privileged EXEC mode, follow these steps to change MTU size for all 10/100 or Gigabit
Ethernet interfaces:
Step 1
Step 2
Command configure terminal system mtu bytes
Purpose
Enter global configuration mode.
(Optional) Change the MTU size for all interfaces on the switch that are operating at 10 or 100 Mb/s. The range is 1500 to 1998 bytes; the default is 1500 bytes.
10-20
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 10 Configuring Interface Characteristics
Monitoring and Maintaining the Interfaces
Step 3
Step 4
Step 5
Step 6
Step 7
Command system mtu jumbo bytes system mtu routing bytes end copy running-config startup-config reload
Purpose
(Optional) Change the MTU size for all Gigabit
Ethernet interfaces on the switch. The range is 1500 to
9000 bytes; the default is 1500 bytes.
(Optional) Change the system MTU for routed ports.
The range is 1500 to the system MTU value, the maximum MTU that can be routed for all ports.
Although larger packets can be accepted, they cannot be routed.
Return to privileged EXEC mode.
Save your entries in the configuration file.
Reload the operating system.
If you enter a value that is outside the allowed range for the specific type of interface, the value is not accepted.
Once the switch reloads, you can verify your settings by entering the show system mtu privileged EXEC command.
This example shows how to set the maximum packet size for a Gigabit Ethernet port to 1800 bytes:
Switch(config)# system mtu jumbo 1800
Switch(config)# exit
Switch# reload
This example shows the response when you try to set Gigabit Ethernet interfaces to an out-of-range number:
Switch(config)# system mtu jumbo 25000
^
% Invalid input detected at '^' marker.
Monitoring and Maintaining the Interfaces
These sections contain interface monitoring and maintenance information:
•
•
•
Monitoring Interface Status, page 10-22
Clearing and Resetting Interfaces and Counters, page 10-22
Shutting Down and Restarting the Interface, page 10-23
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
10-21
Chapter 10 Configuring Interface Characteristics
Monitoring and Maintaining the Interfaces
Monitoring Interface Status
Table 10-3
Commands entered at the privileged EXEC prompt display information about the interface, including the versions of the software and the hardware, the configuration, and statistics about the interfaces.
Table 10-3 lists some of these interface monitoring commands. (You can display the full list of
show commands by using the show ?
command at the privileged EXEC prompt.) These commands are fully described in the Cisco IOS Interface Command Reference, Release 12.2.
Show Commands for Interfaces
Command show interfaces [ interface-id ] show interfaces interface-id status [ err-disabled ] Display interface status or a list of interfaces in an error-disabled state.
show interfaces [ interface-id ] switchport Display administrative and operational status of switching
(nonrouting) ports. You can use this command to find out if a port is in routing or in switching mode.
show interfaces [ interface-id ] description show ip interface [ interface-id ]
Display the description configured on an interface or all interfaces and the interface status.
Display the usability status of all interfaces configured for IP routing or the specified interface.
show interface [ interface-id ] stats
Purpose
Display the status and configuration of all interfaces or a specific interface.
show interfaces transceiver properties show interfaces [ interface-id ] [{ transceiver properties | detail }] module number ] show running-config interface [ interface-id ] show version show controllers ethernet-controller phy interface-id
Display the input and output packets by the switching path for the interface.
(Optional) Display speed and duplex settings on the interface.
Display physical and operational status about an SFP module.
Display the running configuration in RAM for the interface.
Display the hardware configuration, software version, the names and sources of configuration files, and the bootup images.
Display the operational state of the auto-MDIX feature on the interface.
Clearing and Resetting Interfaces and Counters
Table 10-4
Table 10-4 lists the privileged EXEC mode
clear commands that you can use to clear counters and reset interfaces.
Clear Commands for Interfaces
Command clear counters [ interface-id ] clear interface interface-id clear line [ number | console 0 | vty number ]
Purpose
Clear interface counters.
Reset the hardware logic on an interface.
Reset the hardware logic on an asynchronous serial line.
10-22
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 10 Configuring Interface Characteristics
Monitoring and Maintaining the Interfaces
To clear the interface counters shown by the show interfaces privileged EXEC command, use the clear counters privileged EXEC command. The clear counters command clears all current interface counters from the interface unless you specify optional arguments that clear only a specific interface type from a specific interface number.
Note The clear counters privileged EXEC command does not clear counters retrieved by using Simple
Network Management Protocol (SNMP), but only those seen with the show interface privileged EXEC command.
Shutting Down and Restarting the Interface
Shutting down an interface disables all functions on the specified interface and marks the interface as unavailable on all monitoring command displays. This information is communicated to other network servers through all dynamic routing protocols. The interface is not mentioned in any routing updates.
Beginning in privileged EXEC mode, follow these steps to shut down an interface:
Step 1
Step 2
Step 3
Step 4
Step 5
Command configure terminal
Purpose
Enter global configuration mode.
interface { vlan vlan-id } | {{ gigabitethernet } interface-id } |
{ port-channel port-channel-number }
Select the interface to be configured.
shutdown end show running-config
Shut down an interface.
Return to privileged EXEC mode.
Verify your entry.
Use the no shutdown interface configuration command to restart the interface.
To verify that an interface is disabled, enter the show interfaces privileged EXEC command. A disabled interface is shown as administratively down in the display.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
10-23
Monitoring and Maintaining the Interfaces
Chapter 10 Configuring Interface Characteristics
10-24
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
C H A P T E R
11
Configuring Smartports Macros
This chapter describes how to configure and apply Smartports macros on the switch.
Note For complete syntax and usage information for the commands used in this chapter, see the command reference for this release.
This chapter consists of these sections:
•
Understanding Smartports Macros, page 11-1
•
•
Configuring Smartports Macros, page 11-2
Displaying Smartports Macros, page 11-8
Understanding Smartports Macros
Smartports macros provide a convenient way to save and share common configurations. You can use
Smartports macros to enable features and settings based on the location of a switch in the network and for mass configuration deployments across the network.
Each Smartports macro is a set of command-line interface (CLI) commands that you define. Smartports macros do not contain new CLI commands; they are simply a group of existing CLI commands.
When you apply a Smartports macro on an interface, the CLI commands within the macro are configured on the interface. When the macro is applied to an interface, the existing interface configurations are not lost. The new commands are added to the interface and are saved in the running configuration file.
There are Cisco-default Smartports macros embedded in the switch software (see
). You can display these macros and the commands they contain by using the show parser macro user EXEC command.
Table 11-1 Cisco-Default Smartports Macros
Macro Name cisco-global
1
Description
Use this global configuration macro to enable rapid PVST+, loop guard, and dynamic port error recovery for link state failures.
cisco-desktop Use this interface configuration macro for increased network security and reliability when connecting a desktop device, such as a PC, to a switch port.
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
11-1 OL-27326-01
Chapter 11 Configuring Smartports Macros
Configuring Smartports Macros
Table 11-1 Cisco-Default Smartports Macros (continued)
Macro Name cisco-phone
1
Description
Use this interface configuration macro when connecting a desktop device such as a
PC with a Cisco IP Phone to a switch port. This macro is an extension of the cisco-desktop macro and provides the same security and resiliency features, but with the addition of dedicated voice VLANs to ensure proper treatment of delay-sensitive voice traffic.
cisco-switch Use this interface configuration macro when connecting an access switch and a distribution switch or between access switches connected using small form-factor pluggable (SFP) modules.
cisco-router Use this interface configuration macro when connecting the switch and a WAN router.
cisco-wireless Use this interface configuration macro when connecting the switch and a wireless access point.
1.
Cisco-default Smartports macros vary depending on the software version running on your switch.
Configuring Smartports Macros
You can create a new Smartports macro or use an existing macro as a template to create a new macro that is specific to your application. After you create the macro, you can apply it globally to a switch or to a switch interface or range of interfaces.
These sections contain this configuration information:
•
Default Smartports Macro Configuration, page 11-2
•
•
•
•
Smartports Macro Configuration Guidelines, page 11-2
Creating Smartports Macros, page 11-4
Applying Smartports Macros, page 11-5
Applying Cisco-Default Smartports Macros, page 11-6
Default Smartports Macro Configuration
There are no Smartports macros enabled.
Smartports Macro Configuration Guidelines
Follow these guidelines when configuring macros on your switch:
•
•
When creating a macro, do not use the exit or end commands or change the command mode by using interface interface-id . This could cause commands that follow exit , end , or interface interface-id to execute in a different command mode.
When creating a macro, all CLI commands should be in the same configuration mode.
11-2
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 11 Configuring Smartports Macros
Configuring Smartports Macros
•
•
•
•
•
•
•
When creating a macro that requires the assignment of unique values, use the parameter value keywords to designate values specific to the interface. Keyword matching is case sensitive. All matching occurrences of the keyword are replaced with the corresponding value. Any full match of a keyword, even if it is part of a larger string, is considered a match and is replaced by the corresponding value.
Macro names are case sensitive. For example, the commands macro name Sample-Macro and macro name sample-macro will result in two separate macros.
Some macros might contain keywords that require a parameter value. You can use the macro global apply macro-name ?
global configuration command or the macro apply macro-name ?
interface configuration command to display a list of any required values in the macro. If you apply a macro without entering the keyword values, the commands are invalid and are not applied.
When a macro is applied globally to a switch or to a switch interface, all existing configuration on the interface is retained. This is helpful when applying an incremental configuration.
If you modify a macro definition by adding or deleting commands, the changes are not reflected on the interface where the original macro was applied. You need to reapply the updated macro on the interface to apply the new or changed commands.
You can use the macro global trace macro-name global configuration command or the macro trace macro-name interface configuration command to apply and debug a macro to find any syntax or configuration errors. If a command fails because of a syntax error or a configuration error, the macro continues to apply the remaining commands.
Some CLI commands are specific to certain interface types. If a macro is applied to an interface that does not accept the configuration, the macro will fail the syntax check or the configuration check, and the switch will return an error message.
•
•
There are Cisco-default Smartports macros embedded in the switch software (see
). You can display these macros and the commands they contain by using the show parser macro user EXEC command.
Follow these guidelines when you apply a Cisco-default Smartports macro on an interface:
•
Applying a macro to an interface range is the same as applying a macro to a single interface. When you use an interface range, the macro is applied sequentially to each interface within the range. If a macro command fails on one interface, it is still applied to the remaining interfaces.
When you apply a macro to a switch or a switch interface, the macro name is automatically added to the switch or interface. You can display the applied commands and macro names by using the show running-config user EXEC command.
•
Display all macros on the switch by using the show parser macro user EXEC command. Display the contents of a specific macro by using the show parser macro macro-name user EXEC command.
Keywords that begin with $ mean that a unique parameter value is required. Append the
Cisco-default macro with the required values by using the parameter value keywords.
The Cisco-default macros use the $ character to help identify required keywords. There is no restriction on using the $ character to define keywords when you create a macro.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
11-3
Chapter 11 Configuring Smartports Macros
Configuring Smartports Macros
Creating Smartports Macros
Beginning in privileged EXEC mode, follow these steps to create a Smartports macro:
Step 1
Step 2
Step 3
Step 4
Command configure terminal macro name macro-name
Purpose
Enter global configuration mode.
Create a macro definition, and enter a macro name. A macro definition can contain up to 3000 characters.
Enter the macro commands with one command per line. Use the @ character to end the macro. Use the # character at the beginning of a line to enter comment text within the macro.
(Optional) You can define keywords within a macro by using a help string to specify the keywords. Enter # macro keywords word to define the keywords that are available for use with the macro. Separated by a space, you can enter up to three help string keywords in a macro.
Macro names are case sensitive. For example, the commands macro name Sample-Macro and macro name sample-macro will result in two separate macros.
end
We recommend that you do not use the exit or end commands or change the command mode by using interface interface-id in a macro. This could cause any commands following exit , end , or interface interface-id to execute in a different command mode. For best results, all commands in a macro should be in the same configuration mode.
Return to privileged EXEC mode.
show parser macro name macro-name Verify that the macro was created.
The no form of the macro name global configuration command only deletes the macro definition. It does not affect the configuration of those interfaces on which the macro is already applied.
This example shows how to create a macro that defines the switchport access VLAN and the number of secure MAC addresses and also includes two help string keywords by using # macro keywords :
Switch(config)# macro name test switchport access vlan $VLANID switchport port-security maximum $MAX
#macro keywords $VLANID $MAX
@
11-4
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 11 Configuring Smartports Macros
Configuring Smartports Macros
Applying Smartports Macros
Beginning in privileged EXEC mode, follow these steps to apply a Smartports macro:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Command configure terminal macro global { apply | trace } macro-name [ parameter { value }]
[ parameter { value }] [ parameter
{ value }] macro global description text interface interface-id default interface interface-id macro { apply | trace } macro-name
[ parameter { value }] [ parameter
{ value }] [ parameter { value }] macro description text
Purpose
Enter global configuration mode.
Apply each individual command defined in the macro to the switch by entering macro global apply macro-name . Specify macro global trace macro-name to apply and debug a macro to find any syntax or configuration errors.
(Optional) Specify unique parameter values that are specific to the switch. You can enter up to three keyword-value pairs. Parameter keyword matching is case sensitive. All matching occurrences of the keyword are replaced with the corresponding value.
Some macros might contain keywords that require a parameter value.
You can use the macro global apply macro-name ?
command to display a list of any required values in the macro. If you apply a macro without entering the keyword values, the commands are invalid and are not applied.
(Optional) Enter a description about the macro that is applied to the switch.
(Optional) Enter interface configuration mode, and specify the interface on which to apply the macro.
(Optional) Clear all configuration from the specified interface.
Apply each individual command defined in the macro to the interface by entering macro apply macro-name . Specify macro trace macro-name to apply and debug a macro to find any syntax or configuration errors.
(Optional) Specify unique parameter values that are specific to the interface. You can enter up to three keyword-value pairs. Parameter keyword matching is case sensitive. All matching occurrences of the keyword are replaced with the corresponding value.
Some macros might contain keywords that require a parameter value.
You can use the macro apply macro-name ?
command to display a list of any required values in the macro. If you apply a macro without entering the keyword values, the commands are invalid and are not applied.
(Optional) Enter a description about the macro that is applied to the interface.
Return to privileged EXEC mode.
Verify that the macro is applied to the interface.
Step 8
Step 9
Step 10 end show parser macro description
[ interface interface-id ] copy running-config startup-config (Optional) Save your entries in the configuration file.
You can delete a global macro-applied configuration on a switch only by entering the no version of each command that is in the macro. You can delete a macro-applied configuration on an interface by entering the default interface interface-id interface configuration command.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
11-5
Chapter 11 Configuring Smartports Macros
Configuring Smartports Macros
This example shows how to apply the user-created macro called snmp , to set the hostname address to test-server , and to set the IP precedence value to 7 :
Switch(config)# macro global apply snmp ADDRESS test-server VALUE 7
This example shows how to debug the user-created macro called snmp by using the macro global trace global configuration command to find any syntax or configuration errors in the macro when it is applied to the switch.
Switch(config)# macro global trace snmp VALUE 7
Applying command...‘snmp-server enable traps port-security’
Applying command...‘snmp-server enable traps linkup’
Applying command...‘snmp-server enable traps linkdown’
Applying command...‘snmp-server host’
%Error Unknown error.
Applying command...‘snmp-server ip precedence 7’
This example shows how to apply the user-created macro called desktop-config and to verify the configuration.
Switch(config)# interface gigabitethernet0/2
Switch(config-if)# macro apply desktop-config
Switch(config-if)# end
Switch# show parser macro description
Interface Macro Description
--------------------------------------------------------------
Gi0/2 desktop-config
--------------------------------------------------------------
This example shows how to apply the user-created macro called desktop-config and to replace all occurrences of VLAN 1 with VLAN 25:
Switch(config-if)# macro apply desktop-config vlan 25
Applying Cisco-Default Smartports Macros
Beginning in privileged EXEC mode, follow these steps to apply a Smartports macro:
Step 1
Command show parser macro
Step 2
Step 3
Step 4 show parser macro macro-name configure terminal macro global { apply | trace } macro-name [ parameter { value }]
[ parameter { value }] [ parameter
{ value }]
Step 5 interface interface-id
Step 6 default interface interface-id
Purpose
Display the Cisco-default Smartports macros embedded in the switch software.
Display the specific macro that you want to apply.
Enter global configuration mode.
Append the Cisco-default macro with the required values by using the parameter value keywords and apply the macro to the switch.
Keywords that begin with $ mean that a unique parameter value is required.
You can use the macro global apply macro-name ?
command to display a list of any required values in the macro. If you apply a macro without entering the keyword values, the commands are invalid and are not applied.
(Optional) Enter interface configuration mode, and specify the interface on which to apply the macro.
(Optional) Clear all configuration from the specified interface.
11-6
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 11 Configuring Smartports Macros
Configuring Smartports Macros
Step 7
Command macro { apply | trace } macro-name
[ parameter { value }] [ parameter
{ value }] [ parameter { value }]
Purpose
Append the Cisco-default macro with the required values by using the parameter value keywords, and apply the macro to the interface.
Keywords that begin with $ mean that a unique parameter value is required.
You can use the macro apply macro-name ?
command to display a list of any required values in the macro. If you apply a macro without entering the keyword values, the commands are invalid and are not applied.
Return to privileged EXEC mode.
Verify that the macro is applied to an interface.
Step 8
Step 9
Step 10 end show running-config interface interface-id copy running-config startup-config (Optional) Save your entries in the configuration file.
You can delete a global macro-applied configuration on a switch only by entering the no version of each command that is in the macro. You can delete a macro-applied configuration on an interface by entering the default interface interface-id interface configuration command.
This example shows how to display the cisco-desktop macro, how to apply the macro, and to set the access VLAN ID to 25 on an interface:
Switch# show parser macro cisco-desktop
--------------------------------------------------------------
Macro name : cisco-desktop
Macro type : default
# Basic interface - Enable data VLAN only
# Recommended value for access vlan (AVID) should not be 1 switchport access vlan $AVID switchport mode access
# Enable port security limiting port to a single
# MAC address -- that of desktop switchport port-security switchport port-security maximum 1
# Ensure port-security age is greater than one minute
# and use inactivity timer switchport port-security violation restrict switchport port-security aging time 2 switchport port-security aging type inactivity
# Configure port as an edge network port spanning-tree portfast spanning-tree bpduguard enable
--------------------------------------------------------------
Switch#
Switch# configure terminal
Switch(config)# gigabitethernet0/4
Switch(config-if)# macro apply cisco-desktop $AVID 25
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
11-7
Chapter 11 Configuring Smartports Macros
Displaying Smartports Macros
Displaying Smartports Macros
To display the Smartports macros, use one or more of the privileged EXEC commands in
Table 11-2 Commands for Displaying Smartports Macros
Command show parser macro show parser macro name macro-name show parser macro brief show parser macro description [ interface interface-id ]
Purpose
Displays all configured macros.
Displays a specific macro.
Displays the configured macro names.
Displays the macro description for all interfaces or for a specified interface.
11-8
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
C H A P T E R
12
Configuring VLANs
This chapter describes how to configure normal-range VLANs (VLAN IDs 1 to 1005) and extended-range VLANs (VLAN IDs 1006 to 4094) on the switch. It includes information about VLAN membership modes, VLAN configuration modes, VLAN trunks, and dynamic VLAN assignment from a VLAN Membership Policy Server (VMPS).
Note For complete syntax and usage information for the commands used in this chapter, see the command reference for this release.
The chapter consists of these sections:
•
Understanding VLANs, page 12-1
•
•
•
•
•
Configuring Normal-Range VLANs, page 12-4
Configuring Extended-Range VLANs, page 12-11
Configuring VLAN Trunks, page 12-15
Understanding VLANs
A VLAN is a switched network that is logically segmented by function, project team, or application, without regard to the physical locations of the users. VLANs have the same attributes as physical LANs, but you can group end stations even if they are not physically located on the same LAN segment. Any switch port can belong to a VLAN, and unicast, broadcast, and multicast packets are forwarded and flooded only to end stations in the VLAN. Each VLAN is considered a logical network, and packets destined for stations that do not belong to the VLAN must be forwarded through a router or a switch supporting fallback bridging, as shown in
. Because a VLAN is considered a separate logical network, it contains its own bridge Management Information Base (MIB) information and can support its own implementation of spanning tree. See
Chapter 17, “Configuring STP.”
Note Before you create VLANs, you must decide whether to use VLAN Trunking Protocol (VTP) to maintain global VLAN configuration for your network. For more information on VTP, see
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
12-1 OL-27326-01
Chapter 12 Configuring VLANs
Understanding VLANs
shows an example of VLANs segmented into logically defined networks.
Figure 12-1 VLANs as Logically Defined Networks
Engineering
VLAN
Marketing
VLAN
Accounting
VLAN
Cisco router
Floor 3
Gigabit
Ethernet
Floor 2
Floor 1
VLANs are often associated with IP subnetworks. For example, all the end stations in a particular IP subnet belong to the same VLAN. Interface VLAN membership on the switch is assigned manually on an interface-by-interface basis. When you assign switch interfaces to VLANs by using this method, it is known as interface-based, or static, VLAN membership.
Traffic between VLANs must be routed or fallback bridged. The switch can route traffic between
VLANs by using switch virtual interfaces (SVIs). An SVI must be explicitly configured and assigned an
IP address to route traffic between VLANs. For more information, see the
“Switch Virtual Interfaces” section on page 10-4 and the
“Configuring Layer 3 Interfaces” section on page 10-17 .
Note If you plan to configure many VLANs on the switch and to not enable routing, you can use the sdm prefer vlan global configuration command to set the Switch Database Management (sdm) feature to the
VLAN template, which configures system resources to support the maximum number of unicast MAC addresses. For more information on the SDM templates, see
Chapter 6, “Configuring SDM Templates,”
or see the sdm prefer command in the command reference for this release.
Supported VLANs
The switch supports VLANs in VTP client, server, and transparent modes. VLANs are identified by a number from 1 to 4094. VLAN IDs 1002 through 1005 are reserved for Token Ring and FDDI VLANs.
VTP version 1 and version 2 support only normal-range VLANs (VLAN IDs 1 to 1005). In these versions, the switch must be in VTP transparent mode when you create VLAN IDs from 1006 to 4094.
Cisco IOS Release 12.2(52)SE and later support VTP version 3. VTP version 3 supports the entire
12-2
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 12 Configuring VLANs
Understanding VLANs
VLAN range (VLANs 1 to 4094). Extended range VLANs (VLANs 1006 to 4094) are supported only in
VTP version 3. You cannot convert from VTP version 3 to VTP version 2 if extended VLANs are configured in the domain.
Although the switch supports a total of 1005 (normal range and extended range) VLANs, the number of routed ports, SVIs, and other configured features affects the use of the switch hardware.
The switch supports per-VLAN spanning-tree plus (PVST+) or rapid PVST+ with a maximum of 128 spanning-tree instances. One spanning-tree instance is allowed per VLAN. See the
VLAN Configuration Guidelines” section on page 12-6
for more information about the number of spanning-tree instances and the number of VLANs. The switch supports both Inter-Switch Link (ISL) and IEEE 802.1Q trunking methods for sending VLAN traffic over Ethernet ports.
VLAN Port Membership Modes
You configure a port to belong to a VLAN by assigning a membership mode that specifies the kind of traffic the port carries and the number of VLANs to which it can belong.
Table 12-1 lists the membership
modes and membership and VTP characteristics.
Table 12-1 Port Membership Modes and Characteristics
Membership Mode
Static-access
Trunk (ISL or
IEEE 802.1Q)
Dynamic access
VLAN Membership Characteristics
A static-access port can belong to one VLAN and is manually assigned to that VLAN.
For more information, see the
Ports to a VLAN” section on page 12-10
.
VTP Characteristics
VTP is not required. If you do not want
VTP to globally propagate information, set the VTP mode to transparent. To participate in VTP, there must be at least one trunk port on the switch connected to a trunk port of a second switch.
A trunk port is a member of all VLANs by default, including extended-range VLANs, but membership can be limited by configuring the allowed-VLAN list. You can also modify the pruning-eligible list to block flooded traffic to VLANs on trunk ports that are included in the list.
VTP is recommended but not required.
VTP maintains VLAN configuration consistency by managing the addition, deletion, and renaming of VLANs on a network-wide basis. VTP exchanges
VLAN configuration messages with other switches over trunk links.
For information about configuring trunk ports, see the
“Configuring an Ethernet Interface as a Trunk Port” section on page 12-18 .
A dynamic-access port can belong to one VLAN (VLAN
ID 1 to 4094) and is dynamically assigned by a VMPS. The
VMPS can be a Catalyst 5000 or Catalyst 6500 series switch, for example, but never a Cisco Catalyst Blade
Switch 3030 for Dell, which is a VMPS client.
VTP is required.
Configure the VMPS and the client with the same VTP domain name.
To participate in VTP, at least one trunk port on the switch.
You can have dynamic-access ports and trunk ports on the same switch, but you must connect the dynamic-access port to an end station or hub and not to another switch.
must be connected to a trunk port of a second switch.
For configuration information, see the
Dynamic-Access Ports on VMPS Clients” section on page 12-29 .
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
12-3
Chapter 12 Configuring VLANs
Configuring Normal-Range VLANs
Membership Mode VLAN Membership Characteristics
Voice VLAN A voice VLAN port is an access port attached to a Cisco
IP Phone, configured to use one VLAN for voice traffic and another VLAN for data traffic from a device attached to the phone.
VTP Characteristics
VTP is not required; it has no effect on a voice VLAN.
Private VLAN
Tunnel
( dot1q-tunnel )
For more information about voice VLAN ports, see
Chapter 14, “Configuring Voice VLAN.”
A private VLAN port is a host or promiscuous port that belongs to a private VLAN primary or secondary VLAN.
For information about private VLANs, see
Tunnel ports are used for IEEE 802.1Q tunneling to maintain customer VLAN integrity across a service-provider network. You configure a tunnel port on an edge switch in the service-provider network and connect it to an IEEE 802.1Q trunk port on a customer interface, creating an asymetric link. A tunnel port belongs to a single VLAN that is dedicated to tunneling.
For more information about tunnel ports, see
“Configuring IEEE 802.1Q and Layer 2 Protocol
n VTP versions 1 and 2, the switch must be in VTP transparent mode when you configure private VLANs. When private
VLANs are configured on the switch, do not change VTP mode from transparent to client or server mode. VTP version 3 supports private VLANs in any mode.
VTP is not required. You manually assign the tunnel port to a VLAN by using the switchport access vlan interface configuration command.
For more detailed definitions of access and trunk modes and their functions, see
.
When a port belongs to a VLAN, the switch learns and manages the addresses associated with the port on a per-VLAN basis. For more information, see the
“Managing the MAC Address Table” section on page 5-12 .
Configuring Normal-Range VLANs
Normal-range VLANs are VLANs with VLAN IDs 1 to 1005. If the switch is in VTP server or
VTP transparent mode, you can add, modify or remove configurations for VLANs 2 to 1001 in the
VLAN database. (VLAN IDs 1 and 1002 to 1005 are automatically created and cannot be removed.)
In VTP versions 1 and 2, the switch must be in VTP transparent mode when you create extended-range
VLANs (VLANs with IDs from 1006 to 4094), but these VLANs are not saved in the VLAN database.
VTP version 3 supports extended-range VLANs in VTP server and transparent mode and saves them in the VLAN database. See the
“Configuring Extended-Range VLANs” section on page 12-11
.
Configurations for VLAN IDs 1 to 1005 are written to the file vlan.dat
(VLAN database), and you can display them by entering the show vlan privileged EXEC command. The vlan.dat
file is stored in flash memory.
12-4
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 12 Configuring VLANs
Configuring Normal-Range VLANs
Caution You can cause inconsistency in the VLAN database if you attempt to manually delete the vlan.dat
file.
If you want to modify the VLAN configuration, use the commands described in these sections and in the command reference
for this release. To change the VTP configuration, see Chapter 13, “Configuring
You use the interface configuration mode to define the port membership mode and to add and remove ports from VLANs. The results of these commands are written to the running-configuration file, and you can display the file by entering the show running-config privileged EXEC command.
You can set these parameters when you create a new normal-range VLAN or modify an existing VLAN in the VLAN database:
• VLAN ID
•
•
VLAN name
VLAN type (Ethernet, Fiber Distributed Data Interface [FDDI], FDDI network entity title [NET],
TrBRF, or TrCRF, Token Ring, Token Ring-Net)
•
•
•
•
•
•
•
•
VLAN state (active or suspended)
Maximum transmission unit (MTU) for the VLAN
Security Association Identifier (SAID)
Bridge identification number for TrBRF VLANs
Ring number for FDDI and TrCRF VLANs
Parent VLAN number for TrCRF VLANs
Spanning Tree Protocol (STP) type for TrCRF VLANs
VLAN number to use when translating from one VLAN type to another
Note This section does not provide configuration details for most of these parameters. For complete information on the commands and parameters that control VLAN configuration, see the command reference for this release.
These sections contain normal-range VLAN configuration information:
•
•
•
•
•
•
•
Normal-Range VLAN Configuration Guidelines, page 12-6
Creating Normal-Range VLANs, page 12-7
Default Ethernet VLAN Configuration, page 12-7
Creating or Modifying an Ethernet VLAN, page 12-8
Assigning Static-Access Ports to a VLAN, page 12-10
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
12-5
Chapter 12 Configuring VLANs
Configuring Normal-Range VLANs
Token Ring VLANs
Although the switch does not support Token Ring connections, a remote device such as a Catalyst 5000 series switch with Token Ring connections could be managed from one of the supported switches.
Switches running VTP version 2 advertise information about these Token Ring VLANs:
• Token Ring TrBRF VLANs
• Token Ring TrCRF VLANs
For more information on configuring Token Ring VLANs, see the Catalyst 5000 Series Software
Configuration Guide .
Normal-Range VLAN Configuration Guidelines
Follow these guidelines when creating and modifying normal-range VLANs in your network:
• The switch supports 1005 VLANs in VTP client, server, and transparent modes.
•
•
Normal-range VLANs are identified with a number between 1 and 1001. VLAN numbers 1002 through 1005 are reserved for Token Ring and FDDI VLANs.
VLAN configuration for VLANs 1 to 1005 are always saved in the VLAN database. If the VTP mode is transparent, VTP and VLAN configuration are also saved in the switch running configuration file.
•
•
•
•
With VTP versions 1 and 2, the switch supports extended-range VLANs (VLAN IDs 1006 through
4094) only in VTP transparent mode (VTP disabled). Extended-range VLANs created in VTP transparent mode are not saved in the VLAN database and are not propagated. VTP version 3 supports extended-range VLAN configuration and database propagation. If extended VLANs are
configured, you cannot convert from VTP version 3 to version 1 or 2. See the “Configuring
Extended-Range VLANs” section on page 12-11 .
Before you can create a VLAN, the switch must be in VTP server mode or VTP transparent mode.
If the switch is a VTP server, you must define a VTP domain or VTP will not function.
The switch does not support Token Ring or FDDI media. The switch does not forward FDDI,
FDDI-Net, TrCRF, or TrBRF traffic, but it does propagate the VLAN configuration through VTP.
The switch supports 128 spanning-tree instances. If a switch has more active VLANs than supported spanning-tree instances, spanning tree can be enabled on 128 VLANs and is disabled on the remaining VLANs. If you have already used all available spanning-tree instances on a switch, adding another VLAN anywhere in the VTP domain creates a VLAN on that switch that is not running spanning-tree. If you have the default allowed list on the trunk ports of that switch (which is to allow all VLANs), the new VLAN is carried on all trunk ports. Depending on the topology of the network, this could create a loop in the new VLAN that would not be broken, particularly if there are several adjacent switches that all have run out of spanning-tree instances. You can prevent this possibility by setting allowed lists on the trunk ports of switches that have used up their allocation of spanning-tree instances.
If the number of VLANs on the switch exceeds the number of supported spanning-tree instances, we recommend that you configure the IEEE 802.1s Multiple STP (MSTP) on your switch to map multiple VLANs to a single spanning-tree instance. For more information about MSTP, see
Chapter 18, “Configuring MSTP.”
12-6
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 12 Configuring VLANs
Configuring Normal-Range VLANs
Creating Normal-Range VLANs
You configure normal-range VLANs in VLAN configuration mode by entering the vlan global configuration command with a VLAN ID. Enter a new VLAN ID to create a VLAN, or enter an existing
VLAN ID to modify that VLAN. You can use the default VLAN configuration (
multiple commands to configure the VLAN. For more information about commands available in this mode, see the vlan global configuration command description in the command reference for this release.
When you have finished the configuration, you must exit VLAN configuration mode for the configuration to take effect. To display the VLAN configuration, enter the show vlan privileged EXEC command.
The configurations of VLAN IDs 1 to 1005 are always saved in the VLAN database (vlan.dat file). If the
VTP mode is transparent, they are also saved in the switch running configuration file. You can enter the copy running-config startup-config privileged EXEC command to save the configuration in the startup configuration file. To display the VLAN configuration, enter the show vlan privileged EXEC command.
When you save VLAN and VTP information (including extended-range VLAN configuration information) in the startup configuration file and reboot the switch, the switch configuration is selected as follows:
• If the VTP mode is transparent in the startup configuration, and the VLAN database and the VTP domain name from the VLAN database matches that in the startup configuration file, the VLAN database is ignored (cleared), and the VTP and VLAN configurations in the startup configuration file are used. The VLAN database revision number remains unchanged in the VLAN database.
•
•
If the VTP mode or domain name in the startup configuration does not match the VLAN database, the domain name and VTP mode and configuration for the first 1005 VLANs use the VLAN database information.
In VTP versions 1 and 2, if VTP mode is server, the domain name and VLAN configuration for only the first 1005 VLANs use the VLAN database information. VTP version 3 also supports VLANs
1006 to 4094.
Caution If the VLAN database configuration is used at startup and the startup configuration file contains extended-range VLAN configuration, this information is lost when the system boots up.
Default Ethernet VLAN Configuration
shows the default configuration for Ethernet VLANs.
Note The switch supports Ethernet interfaces exclusively. Because FDDI and Token Ring VLANs are not locally supported, you only configure FDDI and Token Ring media-specific characteristics for VTP global advertisements to other switches.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
12-7
Chapter 12 Configuring VLANs
Configuring Normal-Range VLANs
Table 12-2 Ethernet VLAN Defaults and Ranges
Parameter
VLAN ID
Default
1
Range
1 to 4094.
VLAN name
Note
VLANxxxx , where xxxx represents four numeric digits
(including leading zeros) equal to the VLAN ID number
No range
Extended-range VLANs (VLAN
IDs 1006 to 4094) are only saved in the VLAN database in VTP version 3.
1 to 4294967294 IEEE 802.10 SAID 100001 (100000 plus the
VLAN ID)
MTU size 1500
Translational bridge 1 0
1500 to 18190
0 to 1005
Translational bridge 2 0
VLAN state active
Remote SPAN
Private VLANs disabled none configured
0 to 1005 active, suspend enabled, disabled
2 to 1001, 1006 to 4094.
Creating or Modifying an Ethernet VLAN
Each Ethernet VLAN in the VLAN database has a unique, 4-digit ID that can be a number from 1 to
1001. VLAN IDs 1002 to 1005 are reserved for Token Ring and FDDI VLANs. To create a normal-range
VLAN to be added to the VLAN database, assign a number and name to the VLAN.
Note With VTP version 1 and 2, if the switch is in VTP transparent mode, you can assign VLAN IDs greater than 1006, but they are not added to the VLAN database. See the
VLANs” section on page 12-11 .
For the list of default parameters that are assigned when you add a VLAN, see the
Normal-Range VLANs” section on page 12-4 .
Beginning in privileged EXEC mode, follow these steps to create or modify an Ethernet VLAN:
Step 1
Step 2
Command configure terminal vlan vlan-id
Purpose
Enter global configuration mode.
Enter a VLAN ID, and enter VLAN configuration mode. Enter a new
VLAN ID to create a VLAN, or enter an existing VLAN ID to modify that VLAN.
Note The available VLAN ID range for this command is 1 to 4094.
For information about adding VLAN IDs greater than 1005
(extended-range VLANs), see the “Configuring
Extended-Range VLANs” section on page 12-11
.
12-8
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 12 Configuring VLANs
Configuring Normal-Range VLANs
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Command name vlan-name
Purpose
(Optional) Enter a name for the VLAN. If no name is entered for the
VLAN, the default is to append the vlan-id with leading zeros to the word VLAN. For example, VLAN0004 is a default VLAN name for
VLAN 4.
mtu mtu-size remote-span
(Optional) Change the MTU size (or other VLAN characteristic).
(Optional) Configure the VLAN as the RSPAN VLAN for a remote
SPAN session. For more information on remote SPAN, see Chapter 28,
end Return to privileged EXEC mode.
show vlan { name vlan-name | id vlan-id } Verify your entries.
copy running-config startup config (Optional) If the switch is in VTP transparent mode, the VLAN configuration is saved in the running configuration file as well as in the
VLAN database. This saves the configuration in the switch startup configuration file.
To return the VLAN name to the default settings, use the no name , no mtu , or no remote-span VLAN configuration commands.
This example shows how to use VLAN configuration mode to create Ethernet VLAN 20, name it test20, and add it to the VLAN database:
Switch# configure terminal
Switch(config)# vlan 20
Switch(config-vlan)# name test20
Switch(config-vlan)# end
Deleting a VLAN
When you delete a VLAN from a switch that is in VTP server mode, the VLAN is removed from the
VLAN database for all switches in the VTP domain. When you delete a VLAN from a switch that is in
VTP transparent mode, the VLAN is deleted only on that specific switch.
You cannot delete the default VLANs for the different media types: Ethernet VLAN 1 and FDDI or
Token Ring VLANs 1002 to 1005.
Caution When you delete a VLAN, any ports assigned to that VLAN become inactive. They remain associated with the VLAN (and thus inactive) until you assign them to a new VLAN.
Beginning in privileged EXEC mode, follow these steps to delete a VLAN on the switch:
Step 1
Step 2
Step 3
Command configure terminal no vlan vlan-id end
Purpose
Enter global configuration mode.
Remove the VLAN by entering the VLAN ID.
Return to privileged EXEC mode.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
12-9
Configuring Normal-Range VLANs
Step 4
Step 5
Command show vlan brief copy running-config startup config
Chapter 12 Configuring VLANs
Purpose
Verify the VLAN removal.
(Optional) If the switch is in VTP transparent mode, the VLAN configuration is saved in the running configuration file as well as in the VLAN database. This saves the configuration in the switch startup configuration file.
Assigning Static-Access Ports to a VLAN
You can assign a static-access port to a VLAN without having VTP globally propagate VLAN configuration information by disabling VTP (VTP transparent mode).
Note If you assign an interface to a VLAN that does not exist, the new VLAN is created. (See the
“Creating or Modifying an Ethernet VLAN” section on page 12-8 .)
Beginning in privileged EXEC mode, follow these steps to assign a port to a VLAN in the VLAN database:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Command configure terminal copy running-config startup-config
Purpose
Enter global configuration mode interface interface-id switchport mode access
Enter the interface to be added to the VLAN.
Define the VLAN membership mode for the port (Layer 2 access port).
Assign the port to a VLAN. Valid VLAN IDs are 1 to 4094.
switchport access vlan vlan-id end Return to privileged EXEC mode.
show running-config interface interface-id Verify the VLAN membership mode of the interface.
show interfaces interface-id switchport Verify your entries in the Administrative Mode and the Access Mode
VLAN fields of the display.
(Optional) Save your entries in the configuration file.
To return an interface to its default configuration, use the default interface interface-id interface configuration command.
This example shows how to configure a port as an access port in VLAN 2:
Switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# interface gigabitethernet0/1
Switch(config-if)# switchport mode access
Switch(config-if)# switchport access vlan 2
Switch(config-if)# end
12-10
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 12 Configuring VLANs
Configuring Extended-Range VLANs
Configuring Extended-Range VLANs
With VTP version 1 and version 2, when the switch is in VTP transparent mode (VTP disabled), you can create extended-range VLANs (in the range 1006 to 4094). VTP version supports extended-range
VLANs in server or transparent move. Extended-range VLANs enable service providers to extend their infrastructure to a greater number of customers. The extended-range VLAN IDs are allowed for any switchport commands that allow VLAN IDs.
With VTP version 1 or 2, extended-range VLAN configurations are not stored in the VLAN database, but because VTP mode is transparent, they are stored in the switch running configuration file, and you can save the configuration in the startup configuration file by using the copy running-config startup-config privileged EXEC command. Extended-range VLANs created in VTP version 3 are stored in the VLAN database.
Note Although the switch supports 4094 VLAN IDs, see the
“Supported VLANs” section on page 12-2 for
the actual number of VLANs supported.
These sections contain extended-range VLAN configuration information:
•
•
•
•
Default VLAN Configuration, page 12-11
Extended-Range VLAN Configuration Guidelines, page 12-11
Creating an Extended-Range VLAN, page 12-12
Creating an Extended-Range VLAN with an Internal VLAN ID, page 12-13
Default VLAN Configuration
for the default configuration for Ethernet VLANs. You can change only the
MTU size, private VLAN, and the remote SPAN configuration state on extended-range VLANs; all other characteristics must remain at the default state.
Extended-Range VLAN Configuration Guidelines
Follow these guidelines when creating extended-range VLANs:
• VLAN IDs in the extended range are not saved in the VLAN database and are not recognized by
VTP unless the switch is running VTP version 3.
•
•
You cannot include extended-range VLANs in the pruning eligible range.
•
In VTP version 1 and 2, a switch must be in VTP transparent mode when you create extended-range
VLANs. If VTP mode is server or client, an error message is generated, and the extended-range
VLAN is rejected. VTP version 3 supports extended VLANs in server and transparent modes.
For VTP version 1 or 2, you can set the VTP mode to transparent in global configuration mode. See the
“Configuring VTP Mode” section on page 13-10
. You should save this configuration to the startup configuration so that the switch boots up in VTP transparent mode. Otherwise, you lose the extended-range VLAN configuration if the switch resets. If you create extended-range VLANs in
VTP version 3, you cannot convert to VTP version 1 or 2.
• STP is enabled by default on extended-range VLANs, but you can disable it by using the no spanning-tree vlan vlan-id global configuration command. When the maximum number of spanning-tree instances are on the switch, spanning tree is disabled on any newly created VLANs.
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01 12-11
Chapter 12 Configuring VLANs
Configuring Extended-Range VLANs
•
•
If the number of VLANs on the switch exceeds the maximum number of spanning-tree instances, we recommend that you configure the IEEE 802.1s Multiple STP (MSTP) on your switch to map multiple VLANs to a single spanning-tree instance. For more information about MSTP, see
Chapter 18, “Configuring MSTP.”
Each routed port on the switch creates an internal VLAN for its use. These internal VLANs use extended-range VLAN numbers, and the internal VLAN ID cannot be used for an extended-range
VLAN. If you try to create an extended-range VLAN with a VLAN ID that is already allocated as an internal VLAN, an error message is generated, and the command is rejected.
– Because internal VLAN IDs are in the lower part of the extended range, we recommend that you create extended-range VLANs beginning from the highest number (4094) and moving to the lowest (1006) to reduce the possibility of using an internal VLAN ID.
–
–
Before configuring extended-range VLANs, enter the show vlan internal usage privileged
EXEC command to see which VLANs have been allocated as internal VLANs.
If necessary, you can shut down the routed port assigned to the internal VLAN, which frees up the internal VLAN, and then create the extended-range VLAN and re-enable the port, which then uses another VLAN as its internal VLAN. See the
“Creating an Extended-Range VLAN with an Internal VLAN ID” section on page 12-13 .
Although the switch supports a total of 1005 (normal-range and extended-range) VLANs, the number of routed ports, SVIs, and other configured features affects the use of the switch hardware.
If you try to create an extended-range VLAN and there are not enough hardware resources available, an error message is generated, and the extended-range VLAN is rejected.
Creating an Extended-Range VLAN
You create an extended-range VLAN in global configuration mode by entering the vlan global configuration command with a VLAN ID from 1006 to 4094. This command accesses VLAN configuration mode. The extended-range VLAN has the default Ethernet VLAN characteristics (see
Table 12-2 ) and the MTU size, private VLAN, and RSPAN configuration are the only parameters you
can change. See the description of the vlan global configuration command in the command reference for the default settings of all parameters. In VTP version 1 or 2, if you enter an extended-range VLAN ID when the switch is not in VTP transparent mode, an error message is generated when you exit VLAN configuration mode, and the extended-range VLAN is not created.
In VTP version 1 and 2, extended-range VLANs are not saved in the VLAN database; they are saved in the switch running configuration file. You can save the extended-range VLAN configuration in the switch startup configuration file by using the copy running-config startup-config privileged EXEC command. VTP version 3 saves extended-range VLANs in the VLAN database.
Note Before you create an extended-range VLAN, you can verify that the VLAN ID is not used internally by entering the show vlan internal usage privileged EXEC command. If the VLAN ID is used internally and you want to free it up, go to the
12-12
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 12 Configuring VLANs
Configuring Extended-Range VLANs
Beginning in privileged EXEC mode, follow these steps to create an extended-range VLAN:
Step 1
Step 2
Command configure terminal vtp mode transparent
Step 3 vlan vlan-id
Step 4 mtu mtu-size
Step 5 remote-span
Step 6
Step 7
Step 8 end show vlan id vlan-id copy running-config startup config
Purpose
Enter global configuration mode.
Configure the switch for VTP transparent mode, disabling VTP.
Note This step is not required for VTP version 3.
Enter an extended-range VLAN ID and enter VLAN configuration mode.
The range is 1006 to 4094.
(Optional) Modify the VLAN by changing the MTU size.
Note Although all VLAN commands appear in the CLI help in VLAN configuration mode, only the mtu mtu-size , private-vlan , and remote-span commands are supported for extended-range
VLANs.
(Optional) Configure the VLAN as the RSPAN VLAN. See the
“Configuring a VLAN as an RSPAN VLAN” section on page 28-16
.
Return to privileged EXEC mode.
Verify that the VLAN has been created.
Save your entries in the switch startup configuration file. To save extended-range VLAN configurations, you need to save the VTP transparent mode configuration and the extended-range VLAN configuration in the switch startup configuration file. Otherwise, if the switch resets, it will default to VTP server mode, and the extended-range
VLAN IDs will not be saved.
Note With VTP version 3, the VLAN configuration is also saved in the
VLAN database.
To delete an extended-range VLAN, use the no vlan vlan-id global configuration command.
The procedure for assigning static-access ports to an extended-range VLAN is the same as for normal-range VLANs. See the
“Assigning Static-Access Ports to a VLAN” section on page 12-10 .
This example shows how to create a new extended-range VLAN with all default characteristics, enter
VLAN configuration mode, and save the new VLAN in the switch startup configuration file:
Switch(config)# vtp mode transparent
Switch(config)# vlan 2000
Switch(config-vlan)# end
Switch# copy running-config startup config
Creating an Extended-Range VLAN with an Internal VLAN ID
If you enter an extended-range VLAN ID that is already assigned to an internal VLAN, an error message is generated, and the extended-range VLAN is rejected. To manually free an internal VLAN ID, you must temporarily shut down the routed port that is using the internal VLAN ID.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
12-13
Displaying VLANs
Chapter 12 Configuring VLANs
Beginning in privileged EXEC mode, follow these steps to release a VLAN ID that is assigned to an internal VLAN and to create an extended-range VLAN with that ID:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Command show vlan internal usage configure terminal interface interface-id shutdown exit vtp mode transparent
Step 7 vlan vlan-id
Step 8 exit
Step 9 interface interface-id
Step 10
Step 11
Step 12 no shutdown end copy running-config startup config
Purpose
Display the VLAN IDs being used internally by the switch. If the VLAN
ID that you want to use is an internal VLAN, the display shows the routed port that is using the VLAN ID. Enter that port number in Step 3.
Enter global configuration mode.
Specify the interface ID for the routed port that is using the VLAN ID, and enter interface configuration mode.
Shut down the port to free the internal VLAN ID.
Return to global configuration mode.
Set the VTP mode to transparent for creating extended-range VLANs.
Note This step is not required for VTP version 3.
Enter the new extended-range VLAN ID, and enter VLAN configuration mode.
Exit from VLAN configuration mode, and return to global configuration mode.
Specify the interface ID for the routed port that you shut down in Step 4, and enter interface configuration mode.
Re-enable the routed port. It will be assigned a new internal VLAN ID.
Return to privileged EXEC mode.
Save your entries in the switch startup configuration file. To save an extended-range VLAN configuration, you need to save the VTP transparent mode configuration and the extended-range VLAN configuration in the switch startup configuration file. Otherwise, if the switch resets, it will default to VTP server mode, and the extended-range
VLAN IDs will not be saved.
Note This step is not required for VTP version 3 because VLANs are saved in the VLAN database.
Displaying VLANs
Use the show vlan privileged EXEC command to display a list of all VLANs on the switch, including extended-range VLANs. The display includes VLAN status, ports, and configuration information.
Table 12-3 lists the commands for monitoring VLANs.
Table 12-3 VLAN Monitoring Commands
Command show interfaces [ vlan vlan-id ] show vlan [ id vlan-id ]
Purpose
Display characteristics for all interfaces or for the specified VLAN configured on the switch.
Display parameters for all VLANs or the specified VLAN on the switch.
12-14
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 12 Configuring VLANs
Configuring VLAN Trunks
For more details about the show command options and explanations of output fields, see the command reference for this release.
Configuring VLAN Trunks
These sections contain this conceptual information:
•
•
•
•
•
Encapsulation Types, page 12-17
Default Layer 2 Ethernet Interface VLAN Configuration, page 12-18
Configuring an Ethernet Interface as a Trunk Port, page 12-18
Configuring Trunk Ports for Load Sharing, page 12-22
Trunking Overview
A trunk is a point-to-point link between one or more Ethernet switch interfaces and another networking device such as a router or a switch. Ethernet trunks carry the traffic of multiple VLANs over a single link, and you can extend the VLANs across an entire network.
Two trunking encapsulations are available on all Ethernet interfaces:
• Inter-Switch Link (ISL)—Cisco-proprietary trunking encapsulation.
• IEEE 802.1Q— industry-standard trunking encapsulation.
Figure 12-2 shows a network of blade switches that are connected by ISL trunks.
Figure 12-2 Blade Switches in an ISL Trunking Environment
Catalyst 6500 series switch
Blade switch
ISL trunk
ISL trunk
Blade switch
VLAN1 VLAN3
VLAN2 VLAN1
ISL trunk
Blade switch
VLAN2
ISL trunk
Blade switch
VLAN3
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
12-15
Chapter 12 Configuring VLANs
Configuring VLAN Trunks
You can configure a trunk on a single Ethernet interface or on an EtherChannel bundle. For more information about EtherChannel, see
Chapter 35, “Configuring EtherChannels and Layer 2 Trunk
Ethernet trunk interfaces support different trunking modes (see Table 12-4
). You can set an interface as trunking or nontrunking or to negotiate trunking with the neighboring interface. To autonegotiate trunking, the interfaces must be in the same VTP domain.
Trunk negotiation is managed by the Dynamic Trunking Protocol (DTP), which is a Point-to-Point
Protocol. However, some internetworking devices might forward DTP frames improperly, which could cause misconfigurations.
To avoid this, you should configure interfaces connected to devices that do not support DTP to not forward DTP frames, that is, to turn off DTP.
• If you do not intend to trunk across those links, use the switchport mode access interface configuration command to disable trunking.
• To enable trunking to a device that does not support DTP, use the switchport mode trunk and switchport nonegotiate interface configuration commands to cause the interface to become a trunk but to not generate DTP frames. Use the switchport trunk encapsulation isl or switchport trunk encapsulation dot1q interface to select the encapsulation type on the trunk port.
You can also specify on DTP interfaces whether the trunk uses ISL or IEEE 802.1Q encapsulation or if the encapsulation type is autonegotiated. The DTP supports autonegotiation of both ISL and
IEEE 802.1Q trunks.
Note DTP is not supported on private-VLAN ports or tunnel ports.
Table 12-4 Layer 2 Interface Modes
Mode switchport mode access
Function
Puts the interface (access port) into permanent nontrunking mode and negotiates to convert the link into a nontrunk link. The interface becomes a nontrunk interface regardless of whether or not the neighboring interface is a trunk interface.
switchport mode dynamic auto Makes the interface able to convert the link to a trunk link. The interface becomes a trunk interface if the neighboring interface is set to trunk or desirable mode. The default switchport mode for all Ethernet interfaces is dynamic auto .
switchport mode dynamic desirable
Makes the interface actively attempt to convert the link to a trunk link. The interface becomes a trunk interface if the neighboring interface is set to mode. trunk , desirable , or auto switchport mode trunk switchport nonegotiate
Puts the interface into permanent trunking mode and negotiates to convert the neighboring link into a trunk link. The interface becomes a trunk interface even if the neighboring interface is not a trunk interface.
Prevents the interface from generating DTP frames. You can use this command only when the interface switchport mode is access or trunk . You must manually configure the neighboring interface as a trunk interface to establish a trunk link.
switchport mode dot1q-tunnel Configures the interface as a tunnel (nontrunking) port to be connected in an asymmetric link with an IEEE 802.1Q trunk port. The IEEE 802.1Q tunneling is used to maintain customer VLAN integrity across a service provider network. See
“Configuring IEEE 802.1Q and Layer 2 Protocol Tunneling,” for more information on
tunnel ports.
12-16
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 12 Configuring VLANs
Configuring VLAN Trunks
Encapsulation Types
lists the Ethernet trunk encapsulation types and keywords.
Table 12-5 Ethernet Trunk Encapsulation Types
Encapsulation switchport trunk encapsulation isl
Function
Specifies ISL encapsulation on the trunk link.
switchport trunk encapsulation dot1q Specifies IEEE 802.1Q encapsulation on the trunk link.
switchport trunk encapsulation negotiate Specifies that the interface negotiate with the neighboring interface to become an ISL (preferred) or IEEE 802.1Q trunk, depending on the configuration and capabilities of the neighboring interface. This is the default for the switch.
Note The switch does not support Layer 3 trunks; you cannot configure subinterfaces or use the encapsulation keyword on Layer 3 interfaces. The switch does support Layer 2 trunks and Layer 3 VLAN interfaces, which provide equivalent capabilities.
The trunking mode, the trunk encapsulation type, and the hardware capabilities of the two connected interfaces decide whether a link becomes an ISL or IEEE 802.1Q trunk.
IEEE 802.1Q Configuration Considerations
The IEEE 802.1Q trunks impose these limitations on the trunking strategy for a network:
• In a network of Cisco switches connected through IEEE 802.1Q trunks, the switches maintain one spanning-tree instance for each VLAN allowed on the trunks. Non-Cisco devices might support one spanning-tree instance for all VLANs.
When you connect a Cisco switch to a non-Cisco device through an IEEE 802.1Q trunk, the Cisco switch combines the spanning-tree instance of the VLAN of the trunk with the spanning-tree instance of the non-Cisco IEEE 802.1Q switch. However, spanning-tree information for each VLAN is maintained by Cisco switches separated by a cloud of non-Cisco IEEE 802.1Q switches. The non-Cisco IEEE 802.1Q cloud separating the Cisco switches is treated as a single trunk link between the switches.
•
•
Make sure the native VLAN for an IEEE 802.1Q trunk is the same on both ends of the trunk link. If the native VLAN on one end of the trunk is different from the native VLAN on the other end, spanning-tree loops might result.
Disabling spanning tree on the native VLAN of an IEEE 802.1Q trunk without disabling spanning tree on every VLAN in the network can potentially cause spanning-tree loops. We recommend that you leave spanning tree enabled on the native VLAN of an IEEE 802.1Q trunk or disable spanning tree on every VLAN in the network. Make sure your network is loop-free before disabling spanning tree.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
12-17
Chapter 12 Configuring VLANs
Configuring VLAN Trunks
Default Layer 2 Ethernet Interface VLAN Configuration
Table 12-6 shows the default Layer 2 Ethernet interface VLAN configuration.
Table 12-6 Default Layer 2 Ethernet Interface VLAN Configuration
Feature
Interface mode
Trunk encapsulation
Allowed VLAN range
Default Setting switchport mode dynamic auto switchport trunk encapsulation negotiate
VLANs 1 to 4094
VLAN range eligible for pruning
Default VLAN (for access ports)
VLANs 2 to 1001
VLAN 1
Native VLAN (for IEEE 802.1Q trunks) VLAN 1
Configuring an Ethernet Interface as a Trunk Port
•
•
•
Because trunk ports send and receive VTP advertisements, to use VTP you must ensure that at least one trunk port is configured on the switch and that this trunk port is connected to the trunk port of a second switch. Otherwise, the switch cannot receive any VTP advertisements.
These sections contain this configuration information:
•
Interaction with Other Features, page 12-18
Defining the Allowed VLANs on a Trunk, page 12-20
Changing the Pruning-Eligible List, page 12-21
Configuring the Native VLAN for Untagged Traffic, page 12-22
Note By default, an interface is in Layer 2 mode. The default mode for Layer 2 interfaces is switchport mode dynamic auto . If the neighboring interface supports trunking and is configured to allow trunking, the link is a Layer 2 trunk or, if the interface is in Layer 3 mode, it becomes a Layer 2 trunk when you enter the switchport interface configuration command. By default, trunks negotiate encapsulation. If the neighboring interface supports ISL and IEEE 802.1Q encapsulation and both interfaces are set to negotiate the encapsulation type, the trunk uses ISL encapsulation.
Interaction with Other Features
Trunking interacts with other features in these ways:
•
•
•
A trunk port cannot be a secure port.
A trunk port cannot be a tunnel port.
Trunk ports can be grouped into EtherChannel port groups, but all trunks in the group must have the same configuration. When a group is first created, all ports follow the parameters set for the first port to be added to the group. If you change the configuration of one of these parameters, the switch propagates the setting you entered to all ports in the group:
– allowed-VLAN list.
– STP port priority for each VLAN.
12-18
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 12 Configuring VLANs
Configuring VLAN Trunks
•
•
•
– STP Port Fast setting.
– trunk status: if one port in a port group ceases to be a trunk, all ports cease to be trunks.
We recommend that you configure no more than 24 trunk ports in PVST mode and no more than 40 trunk ports in MST mode.
If you try to enable IEEE 802.1x on a trunk port, an error message appears, and IEEE 802.1x is not enabled. If you try to change the mode of an IEEE 802.1x-enabled port to trunk, the port mode is not changed.
A port in dynamic mode can negotiate with its neighbor to become a trunk port. If you try to enable
IEEE 802.1x on a dynamic port, an error message appears, and IEEE 802.1x is not enabled. If you try to change the mode of an IEEE 802.1x-enabled port to dynamic, the port mode is not changed.
Configuring a Trunk Port
Beginning in privileged EXEC mode, follow these steps to configure a port as a trunk port:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Command configure terminal interface interface-id switchport trunk encapsulation dot1q | negotiate switchport mode desirable } |
} trunk
{
} dynamic {
{ auto isl
|
|
Purpose
Enter global configuration mode.
Specify the port to be configured for trunking, and enter interface configuration mode.
Configure the port to support ISL or IEEE 802.1Q encapsulation or to negotiate (the default) with the neighboring interface for encapsulation type.
You must configure each end of the link with the same encapsulation type.
Configure the interface as a Layer 2 trunk (required only if the interface is a Layer 2 access port or tunnel port or to specify the trunking mode).
• dynamic auto —Set the interface to a trunk link if the neighboring interface is set to trunk or desirable mode. This is the default.
•
• dynamic desirable —Set the interface to a trunk link if the neighboring interface is set to trunk, desirable, or auto mode.
trunk —Set the interface in permanent trunking mode and negotiate to convert the link to a trunk link even if the neighboring interface is not a trunk interface.
switchport access vlan vlan-id (Optional) Specify the default VLAN, which is used if the interface stops trunking.
Specify the native VLAN for IEEE 802.1Q trunks. switchport trunk native vlan vlan-id end Return to privileged EXEC mode.
show interfaces interface-id switchport Display the switchport configuration of the interface in the Administrative
Mode and the Administrative Trunking Encapsulation fields of the display.
show interfaces interface-id trunk copy running-config startup-config
Display the trunk configuration of the interface.
(Optional) Save your entries in the configuration file.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
12-19
Chapter 12 Configuring VLANs
Configuring VLAN Trunks
To return an interface to its default configuration, use the default interface interface-id interface configuration command. To reset all trunking characteristics of a trunking interface to the defaults, use the no switchport trunk interface configuration command. To disable trunking, use the switchport mode access interface configuration command to configure the port as a static-access port.
This example shows how to configure a port as an IEEE 802.1Q trunk. The example assumes that the neighbor interface is configured to support IEEE 802.1Q trunking.
Switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# interface gigabitethernet0/2
Switch(config-if)# switchport mode dynamic desirable
Switch(config-if)# switchport trunk encapsulation dot1q
Switch(config-if)# end
Defining the Allowed VLANs on a Trunk
By default, a trunk port sends traffic to and receives traffic from all VLANs. All VLAN IDs, 1 to 4094, are allowed on each trunk. However, you can remove VLANs from the allowed list, preventing traffic from those VLANs from passing over the trunk. To restrict the traffic a trunk carries, use the switchport trunk allowed vlan remove vlan-list interface configuration command to remove specific VLANs from the allowed list.
Step 1
Step 2
Step 3
Note VLAN 1 is the default VLAN on all trunk ports in all Cisco switches, and it has previously been a requirement that VLAN 1 always be enabled on every trunk link. You can use the VLAN 1 minimization feature to disable VLAN 1 on any individual VLAN trunk link so that no user traffic (including spanning-tree advertisements) is sent or received on VLAN 1.
To reduce the risk of spanning-tree loops or storms, you can disable VLAN 1 on any individual VLAN trunk port by removing VLAN 1 from the allowed list. When you remove VLAN 1 from a trunk port, the interface continues to sent and receive management traffic, for example, Cisco Discovery Protocol
(CDP), Port Aggregation Protocol (PAgP), Link Aggregation Control Protocol (LACP), DTP, and VTP in VLAN 1.
If a trunk port with VLAN 1 disabled is converted to a nontrunk port, it is added to the access VLAN. If the access VLAN is set to 1, the port will be added to VLAN 1, regardless of the switchport trunk allowed setting. The same is true for any VLAN that has been disabled on the port.
A trunk port can become a member of a VLAN if the VLAN is enabled, if VTP knows of the VLAN, and if the VLAN is in the allowed list for the port. When VTP detects a newly enabled VLAN and the
VLAN is in the allowed list for a trunk port, the trunk port automatically becomes a member of the enabled VLAN. When VTP detects a new VLAN and the VLAN is not in the allowed list for a trunk port, the trunk port does not become a member of the new VLAN.
Beginning in privileged EXEC mode, follow these steps to modify the allowed list of a trunk:
Command configure terminal interface interface-id switchport mode trunk
Purpose
Enter global configuration mode.
Specify the port to be configured, and enter interface configuration mode.
Configure the interface as a VLAN trunk port.
12-20
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 12 Configuring VLANs
Configuring VLAN Trunks
Step 4
Step 5
Step 6
Step 7
Command switchport trunk allowed vlan { add | all | except | remove } vlan-list
Purpose
(Optional) Configure the list of VLANs allowed on the trunk.
For explanations about using the add , all , except , and remove keywords, see the command reference for this release.
The vlan-list parameter is either a single VLAN number from 1 to 4094 or a range of VLANs described by two VLAN numbers, the lower one first, separated by a hyphen. Do not enter any spaces between comma-separated VLAN parameters or in hyphen-specified ranges.
end
All VLANs are allowed by default.
Return to privileged EXEC mode.
show interfaces interface-id switchport Verify your entries in the Trunking VLANs Enabled field of the display.
copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default allowed VLAN list of all VLANs, use the no switchport trunk allowed vlan interface configuration command.
This example shows how to remove VLAN 2 from the allowed VLAN list on a port:
Switch(config)# interface gigabitethernett0/1
Switch(config-if)# switchport trunk allowed vlan remove 2
Switch(config-if)# end
Changing the Pruning-Eligible List
The pruning-eligible list applies only to trunk ports. Each trunk port has its own eligibility list. VTP pruning must be enabled for this procedure to take effect. The
“Enabling VTP Pruning” section on page 13-14
describes how to enable VTP pruning.
Beginning in privileged EXEC mode, follow these steps to remove VLANs from the pruning-eligible list on a trunk port:
Step 1
Step 2
Step 3
Step 4
Command configure terminal interface interface-id switchport trunk pruning vlan { add | except | none | remove } vlan-list
[ ,vlan [ ,vlan [ ,,, ]]
Purpose
Enter global configuration mode.
Select the trunk port for which VLANs should be pruned, and enter interface configuration mode.
Configure the list of VLANs allowed to be pruned from the trunk.
(See the
“VTP Pruning” section on page 13-5
).
end
For explanations about using the add , except , none , and remove keywords, see the command reference for this release.
Separate nonconsecutive VLAN IDs with a comma and no spaces; use a hyphen to designate a range of IDs. Valid IDs are 2 to 1001.
Extended-range VLANs (VLAN IDs 1006 to 4094) cannot be pruned.
VLANs that are pruning-ineligible receive flooded traffic.
The default list of VLANs allowed to be pruned contains VLANs 2 to
1001.
Return to privileged EXEC mode.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
12-21
Chapter 12 Configuring VLANs
Configuring VLAN Trunks
Step 5
Step 6
Command Purpose show interfaces interface-id switchport Verify your entries in the Pruning VLANs Enabled field of the display.
copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default pruning-eligible list of all VLANs, use the no switchport trunk pruning vlan interface configuration command.
Configuring the Native VLAN for Untagged Traffic
A trunk port configured with IEEE 802.1Q tagging can receive both tagged and untagged traffic. By default, the switch forwards untagged traffic in the native VLAN configured for the port. The native
VLAN is VLAN 1 by default.
Note The native VLAN can be assigned any VLAN ID.
For information about IEEE 802.1Q configuration issues, see the
Considerations” section on page 12-17 .
Beginning in privileged EXEC mode, follow these steps to configure the native VLAN on an
IEEE 802.1Q trunk:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Command configure terminal interface interface-id switchport trunk native vlan vlan-id end show interfaces interface-id switchport copy running-config startup-config
Purpose
Enter global configuration mode.
Define the interface that is configured as the IEEE 802.1Q trunk, and enter interface configuration mode.
Configure the VLAN that is sending and receiving untagged traffic on the trunk port.
For vlan-id , the range is 1 to 4094.
Return to privileged EXEC mode.
Verify your entries in the Trunking Native Mode VLAN field.
(Optional) Save your entries in the configuration file.
To return to the default native VLAN, VLAN 1, use the no switchport trunk native vlan interface configuration command.
If a packet has a VLAN ID that is the same as the outgoing port native VLAN ID, the packet is sent untagged; otherwise, the switch sends the packet with a tag.
Configuring Trunk Ports for Load Sharing
Load sharing divides the bandwidth supplied by parallel trunks connecting switches. To avoid loops,
STP normally blocks all but one parallel link between switches. Using load sharing, you divide the traffic between the links according to which VLAN the traffic belongs.
12-22
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 12 Configuring VLANs
Configuring VLAN Trunks
You configure load sharing on trunk ports by using STP port priorities or STP path costs. For load sharing using STP port priorities, both load-sharing links must be connected to the same switch. For load sharing using STP path costs, each load-sharing link can be connected to the same switch or to two different switches. For more information about STP, see
Chapter 17, “Configuring STP.”
Load Sharing Using STP Port Priorities
When two ports on the same switch form a loop, the switch uses the STP port priority to decide which port is enabled and which port is in a blocking state. You can set the priorities on a parallel trunk port so that the port carries all the traffic for a given VLAN. The trunk port with the higher priority (lower values) for a VLAN is forwarding traffic for that VLAN. The trunk port with the lower priority (higher values) for the same VLAN remains in a blocking state for that VLAN. One trunk port sends or receives all traffic for the VLAN.
Figure 12-3 shows two trunks connecting supported switches. In this example, the switches are
configured as follows:
•
•
•
•
VLANs 8 through 10 are assigned a port priority of 16 on Trunk 1.
VLANs 3 through 6 retain the default port priority of 128 on Trunk 1.
VLANs 3 through 6 are assigned a port priority of 16 on Trunk 2.
VLANs 8 through 10 retain the default port priority of 128 on Trunk 2.
In this way, Trunk 1 carries traffic for VLANs 8 through 10, and Trunk 2 carries traffic for VLANs 3 through 6. If the active trunk fails, the trunk with the lower priority takes over and carries the traffic for all of the VLANs. No duplication of traffic occurs over any trunk port.
Figure 12-3 Load Sharing by Using STP Port Priorities
Switch A
Step 1
Step 2
Step 3
Step 4
Step 5
Command vtp domain
Trunk 1
VLANs 8 – 10 (priority 16)
VLANs 3 – 6 (priority 128) configure terminal domain-name vtp mode server end show vtp status
Trunk 2
VLANs 3 – 6 (priority 16)
VLANs 8 – 10 (priority 128)
Switch B
Beginning in privileged EXEC mode, follow these steps to configure the network shown in
.
Purpose
Enter global configuration mode on Switch A.
Configure a VTP administrative domain.
The domain name can be 1 to 32 characters.
Configure Switch A as the VTP server.
Return to privileged EXEC mode.
Verify the VTP configuration on both Switch A and Switch B.
In the display, check the VTP Operating Mode and the VTP Domain
Name fields.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
12-23
Chapter 12 Configuring VLANs
Configuring VLAN Trunks
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
Step 12
Step 13
Step 14
Step 15
Step 16
Step 17
Step 18
Step 19
Step 20
Step 21
Step 22
Step 23
Step 24
Command show vlan configure terminal interface gigabitethernet0/1
Purpose
Verify that the VLANs exist in the database on Switch A.
Enter global configuration mode.
Define the interface to be configured as a trunk, and enter interface configuration mode.
switchport trunk encapsulation dot1q | negotiate }
{ isl switchport mode trunk end show interfaces gigabitethernet0/1 switchport
| Configure the port to support ISL or IEEE 802.1Q encapsulation or to negotiate with the neighboring interface. You must configure each end of the link with the same encapsulation type.
Configure the port as a trunk port.
Return to privileged EXEC mode.
Verify the VLAN configuration.
show vlan When the trunk links come up, VTP passes the VTP and VLAN information to Switch B. Verify that Switch B has learned the VLAN configuration.
Enter global configuration mode on Switch A.
configure terminal interface gigabitethernet 0/1 Define the interface to set the STP port priority, and enter interface configuration mode.
spanning-tree vlan 8-10 port-priority 16 Assign the port priority of 16 for VLANs 8 through 10.
exit interface gigabitethernet0/2
Repeat Steps 7 through 11 on Switch A for a second port in the switch.
Repeat Steps 7 through 11 on Switch B to configure the trunk ports that connect to the trunk ports configured on Switch A.
spanning-tree vlan 3-6 port-priority 16 end show running-config copy running-config startup-config
Return to global configuration mode.
Define the interface to set the STP port priority, and enter interface configuration mode.
Assign the port priority of 16 for VLANs 3 through 6.
Return to privileged EXEC mode.
Verify your entries.
(Optional) Save your entries in the configuration file.
Load Sharing Using STP Path Cost
You can configure parallel trunks to share VLAN traffic by setting different path costs on a trunk and associating the path costs with different sets of VLANs, blocking different ports for different VLANs.
The VLANs keep the traffic separate and maintain redundancy in the event of a lost link.
In
, Trunk ports 1 and 2 are configured as 100BASE-T ports. These VLAN path costs are assigned:
•
•
•
•
VLANs 2 through 4 are assigned a path cost of 30 on Trunk port 1.
VLANs 8 through 10 retain the default 100BASE-T path cost on Trunk port 1 of 19.
VLANs 8 through 10 are assigned a path cost of 30 on Trunk port 2.
VLANs 2 through 4 retain the default 100BASE-T path cost on Trunk port 2 of 19.
12-24
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 12 Configuring VLANs
Figure 12-4 Load-Sharing Trunks with Traffic Distributed by Path Cost
Switch A
Configuring VLAN Trunks
Trunk port 1
VLANs 2 – 4 (path cost 30)
VLANs 8 – 10 (path cost 19)
Trunk port 2
VLANs 8 – 10 (path cost 30)
VLANs 2 – 4 (path cost 19)
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
Step 12
Step 13
Step 14
Step 15
Step 16
Step 17
Command configure terminal interface gigabitethernet0/1 switchport trunk encapsulation
{ isl | dot1q | negotiate } switchport mode trunk exit end show running-config show vlan configure terminal interface gigabitethernet0/1 spanning-tree vlan 2-4 cost 30 end exit
Switch B
Beginning in privileged EXEC mode, follow these steps to configure the network shown in
: show running-config copy running-config startup-config
Purpose
Enter global configuration mode on Switch A.
Define the interface to be configured as a trunk, and enter interface configuration mode.
Configure the port to support ISL or IEEE 802.1Q encapsulation. You must configure each end of the link with the same encapsulation type.
Configure the port as a trunk port. The trunk defaults to ISL trunking.
Return to global configuration mode.
Repeat Steps 2 through 5 on a second interface in Switch A.
Return to privileged EXEC mode.
Verify your entries. In the display, make sure that the interfaces are configured as trunk ports.
When the trunk links come up, Switch A receives the VTP information from the other switches. Verify that Switch A has learned the VLAN configuration.
Enter global configuration mode.
Define the interface on which to set the STP cost, and enter interface configuration mode.
Set the spanning-tree path cost to 30 for VLANs 2 through 4.
Return to global configuration mode.
Repeat Steps 9 through 13 on the other configured trunk interface on
Switch A, and set the spanning-tree path cost to 30 for VLANs 8, 9, and
10.
Return to privileged EXEC mode.
Verify your entries. In the display, verify that the path costs are set correctly for both trunk interfaces.
(Optional) Save your entries in the configuration file.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
12-25
Chapter 12 Configuring VLANs
Configuring VMPS
Configuring VMPS
The VLAN Query Protocol (VQP) is used to support dynamic-access ports, which are not permanently assigned to a VLAN, but give VLAN assignments based on the MAC source addresses seen on the port.
Each time an unknown MAC address is seen, the switch sends a VQP query to a remote VMPS; the query includes the newly seen MAC address and the port on which it was seen. The VMPS responds with a
VLAN assignment for the port. The switch cannot be a VMPS server but can act as a client to the VMPS and communicate with it through VQP.
These sections contain this information:
•
•
•
•
•
“Understanding VMPS” section on page 12-26
“Default VMPS Client Configuration” section on page 12-27
“VMPS Configuration Guidelines” section on page 12-27
“Configuring the VMPS Client” section on page 12-28
•
•
“Monitoring the VMPS” section on page 12-30
“Troubleshooting Dynamic-Access Port VLAN Membership” section on page 12-31
“VMPS Configuration Example” section on page 12-31
Understanding VMPS
Each time the client switch receives the MAC address of a new host, it sends a VQP query to the VMPS.
When the VMPS receives this query, it searches its database for a MAC-address-to-VLAN mapping. The server response is based on this mapping and whether or not the server is in open or secure mode. In secure mode, the server shuts down the port when an illegal host is detected. In open mode, the server simply denies the host access to the port.
If the port is currently unassigned (that is, it does not yet have a VLAN assignment), the VMPS provides one of these responses:
• If the host is allowed on the port, the VMPS sends the client a vlan-assignment response containing the assigned VLAN name and allowing access to the host.
•
•
If the host is not allowed on the port and the VMPS is in open mode, the VMPS sends an access-denied response.
If the VLAN is not allowed on the port and the VMPS is in secure mode, the VMPS sends a port-shutdown response.
If the port already has a VLAN assignment, the VMPS provides one of these responses:
• If the VLAN in the database matches the current VLAN on the port, the VMPS sends an success response, allowing access to the host.
• If the VLAN in the database does not match the current VLAN on the port and active hosts exist on the port, the VMPS sends an access-denied or a port-shutdown response, depending on the secure mode of the VMPS.
If the switch receives an access-denied response from the VMPS, it continues to block traffic to and from the host MAC address. The switch continues to monitor the packets directed to the port and sends a query to the VMPS when it identifies a new host address. If the switch receives a port-shutdown response from the VMPS, it disables the port. The port must be manually re-enabled by using the CLI or SNMP.
12-26
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 12 Configuring VLANs
Configuring VMPS
Dynamic-Access Port VLAN Membership
A dynamic-access port can belong to only one VLAN with an ID from 1 to 4094. When the link comes up, the switch does not forward traffic to or from this port until the VMPS provides the VLAN assignment. The VMPS receives the source MAC address from the first packet of a new host connected to the dynamic-access port and attempts to match the MAC address to a VLAN in the VMPS database.
If there is a match, the VMPS sends the VLAN number for that port. If the client switch was not previously configured, it uses the domain name from the first VTP packet it receives on its trunk port from the VMPS. If the client switch was previously configured, it includes its domain name in the query packet to the VMPS to obtain its VLAN number. The VMPS verifies that the domain name in the packet matches its own domain name before accepting the request and responds to the client with the assigned
VLAN number for the client. If there is no match, the VMPS either denies the request or shuts down the port (depending on the VMPS secure mode setting).
Multiple hosts (MAC addresses) can be active on a dynamic-access port if they are all in the same
VLAN; however, the VMPS shuts down a dynamic-access port if more than 20 hosts are active on the port.
If the link goes down on a dynamic-access port, the port returns to an isolated state and does not belong to a VLAN. Any hosts that come online through the port are checked again through the VQP with the
VMPS before the port is assigned to a VLAN.
Dynamic-access ports can be used for direct host connections, or they can connect to a network. A maximum of 20 MAC addresses are allowed per port on the switch. A dynamic-access port can belong to only one VLAN at a time, but the VLAN can change over time, depending on the MAC addresses seen.
Default VMPS Client Configuration
shows the default VMPS and dynamic-access port configuration on client switches.
Table 12-7 Default VMPS Client and Dynamic-Access Port Configuration
Feature
VMPS domain server
VMPS reconfirm interval
VMPS server retry count
Dynamic-access ports
Default Setting
None
60 minutes
3
None configured
VMPS Configuration Guidelines
These guidelines and restrictions apply to dynamic-access port VLAN membership:
•
•
You should configure the VMPS before you configure ports as dynamic-access ports.
When you configure a port as a dynamic-access port, the spanning-tree Port Fast feature is automatically enabled for that port. The Port Fast mode accelerates the process of bringing the port into the forwarding state.
• IEEE 802.1x ports cannot be configured as dynamic-access ports. If you try to enable IEEE 802.1x on a dynamic-access (VQP) port, an error message appears, and IEEE 802.1x is not enabled. If you try to change an IEEE 802.1x-enabled port to dynamic VLAN assignment, an error message appears, and the VLAN configuration is not changed.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
12-27
Configuring VMPS
Chapter 12 Configuring VLANs
•
•
•
•
•
•
•
•
Trunk ports cannot be dynamic-access ports, but you can enter the switchport access vlan dynamic interface configuration command for a trunk port. In this case, the switch retains the setting and applies it if the port is later configured as an access port.
You must turn off trunking on the port before the dynamic-access setting takes effect.
Dynamic-access ports cannot be monitor ports.
Secure ports cannot be dynamic-access ports. You must disable port security on a port before it becomes dynamic.
Private VLAN ports cannot be dynamic-access ports.
Dynamic-access ports cannot be members of an EtherChannel group.
Port channels cannot be configured as dynamic-access ports.
The VTP management domain of the VMPS client and the VMPS server must be the same.
The VLAN configured on the VMPS server should not be a voice VLAN.
Configuring the VMPS Client
You configure dynamic VLANs by using the VMPS (server). The switch can be a VMPS client; it cannot be a VMPS server.
Entering the IP Address of the VMPS
You must first enter the IP address of the server to configure the switch as a client.
Beginning in privileged EXEC mode, follow these steps to enter the IP address of the VMPS:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Command configure terminal vmps server vmps server ipaddress
ipaddress primary
Purpose
Enter global configuration mode.
Enter the IP address of the switch acting as the primary VMPS server.
(Optional) Enter the IP address of the switch acting as a secondary VMPS server.
end
You can enter up to three secondary server addresses.
Return to privileged EXEC mode.
show vmps Verify your entries in the VMPS Domain Server field of the display.
copy running-config startup-config (Optional) Save your entries in the configuration file.
Note You must have IP connectivity to the VMPS for dynamic-access ports to work. You can test for IP connectivity by pinging the IP address of the VMPS and verifying that you get a response.
12-28
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 12 Configuring VLANs
Configuring Dynamic-Access Ports on VMPS Clients
Configuring VMPS
Caution Dynamic-access port VLAN membership is for end stations or hubs connected to end stations.
Connecting dynamic-access ports to other switches can cause a loss of connectivity.
Beginning in privileged EXEC mode, follow these steps to configure a dynamic-access port on a VMPS client switch:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Command configure terminal interface interface-id switchport mode access switchport access vlan dynamic end show interfaces interface-id switchport copy running-config startup-config
Purpose
Enter global configuration mode.
Specify the switch port that is connected to the end station, and enter interface configuration mode.
Set the port to access mode.
Configure the port as eligible for dynamic VLAN membership.
The dynamic-access port must be connected to an end station.
Return to privileged EXEC mode.
Verify your entries in the Operational Mode field of the display.
(Optional) Save your entries in the configuration file.
To return an interface to its default configuration, use the default interface interface-id interface configuration command. To return an interface to its default switchport mode (dynamic auto), use the no switchport mode interface configuration command. To reset the access mode to the default VLAN for the switch, use the no switchport access vlan interface configuration command.
Reconfirming VLAN Memberships
Beginning in privileged EXEC mode, follow these steps to confirm the dynamic-access port VLAN membership assignments that the switch has received from the VMPS:
Step 1
Step 2
Command vmps reconfirm show vmps
Purpose
Reconfirm dynamic-access port VLAN membership.
Verify the dynamic VLAN reconfirmation status.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
12-29
Chapter 12 Configuring VLANs
Configuring VMPS
Changing the Reconfirmation Interval
VMPS clients periodically reconfirm the VLAN membership information received from the VMPS.You can set the number of minutes after which reconfirmation occurs.
Beginning in privileged EXEC mode, follow these steps to change the reconfirmation interval:
Step 1
Step 2
Step 3
Step 4
Step 5
Command Purpose configure terminal vmps reconfirm minutes
Enter global configuration mode.
Enter the number of minutes between reconfirmations of the dynamic
VLAN membership. The range is 1 to 120. The default is 60 minutes.
end show vmps
Return to privileged EXEC mode.
Verify the dynamic VLAN reconfirmation status in the Reconfirm Interval field of the display.
copy running-config startup-config (Optional) Save your entries in the configuration file.
To return the switch to its default setting, use the no vmps reconfirm global configuration command.
Changing the Retry Count
Beginning in privileged EXEC mode, follow these steps to change the number of times that the switch attempts to contact the VMPS before querying the next server:
Step 1
Step 2
Step 3
Step 4
Step 5
Command configure terminal vmps retry count end
Purpose
Enter global configuration mode.
Change the retry count. The retry range is 1 to 10; the default is 3.
Return to privileged EXEC mode.
show vmps Verify your entry in the Server Retry Count field of the display.
copy running-config startup-config (Optional) Save your entries in the configuration file.
To return the switch to its default setting, use the no vmps retry global configuration command.
Monitoring the VMPS
You can display information about the VMPS by using the show vmps privileged EXEC command. The switch displays this information about the VMPS:
• VMPS VQP Version—the version of VQP used to communicate with the VMPS. The switch queries the VMPS that is using VQP version 1.
•
•
Reconfirm Interval—the number of minutes the switch waits before reconfirming the
VLAN-to-MAC-address assignments.
Server Retry Count—the number of times VQP resends a query to the VMPS. If no response is received after this many tries, the switch starts to query the secondary VMPS.
12-30
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 12 Configuring VLANs
Configuring VMPS
•
•
VMPS domain server—the IP address of the configured VLAN membership policy servers. The switch sends queries to the one marked current . The one marked primary is the primary server.
VMPS Action—the result of the most recent reconfirmation attempt. A reconfirmation attempt can occur automatically when the reconfirmation interval expires, or you can force it by entering the vmps reconfirm privileged EXEC command or its SNMP equivalent.
This is an example of output for the show vmps privileged EXEC command:
Switch# show vmps
VQP Client Status:
--------------------
VMPS VQP Version: 1
Reconfirm Interval: 60 min
Server Retry Count: 3
VMPS domain server: 172.20.128.86 (primary, current)
172.20.128.87
Reconfirmation status
---------------------
VMPS Action: other
Troubleshooting Dynamic-Access Port VLAN Membership
The VMPS shuts down a dynamic-access port under these conditions:
• The VMPS is in secure mode, and it does not allow the host to connect to the port. The VMPS shuts down the port to prevent the host from connecting to the network.
• More than 20 active hosts reside on a dynamic-access port.
To re-enable a disabled dynamic-access port, enter the shutdown interface configuration command followed by the no shutdown interface configuration command.
VMPS Configuration Example
Figure 12-5 shows a network with a VMPS server switch and VMPS client switches with
dynamic-access ports. In this example, these assumptions apply:
• The VMPS server and the VMPS client are separate switches.
•
•
•
•
The Catalyst 6500 series Switch A is the primary VMPS server.
The Catalyst 6500 series Switch C and Switch J are secondary VMPS servers.
End stations are connected to the clients, Switch B and Switch I.
The database configuration file is stored on the TFTP server with the IP address 172.20.22.7.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
12-31
Configuring VMPS
Figure 12-5
End station 1
End station 2
Dynamic Port VLAN Membership Configuration
Catalyst 6500 series switch A
Primary VMPS
Server 1 172.20.26.150
Dynamic-access port
Catalyst 6500 series
Secondary VMPS
Server 2
Client switch B
172.20.26.151
Trunk port
Switch C
172.20.26.152
Switch D
172.20.26.153
172.20.26.154
Switch E
172.20.26.155
Switch F
172.20.26.156
Switch G
Switch H
Dynamic-access port
Catalyst 6500 series
Secondary VMPS
Server 3
172.20.26.157
Client switch I
172.20.26.158
Trunk port
172.20.26.159
Switch J
Chapter 12 Configuring VLANs
TFTP server
Router
172.20.22.7
12-32
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
C H A P T E R
13
Configuring VTP
This chapter describes how to use the VLAN Trunking Protocol (VTP) and the VLAN database for managing VLANs with the switch.
Note For complete syntax and usage information for the commands used in this chapter, see the command reference for this release.
The chapter consists of these sections:
•
•
•
Understanding VTP
VTP is a Layer 2 messaging protocol that maintains VLAN configuration consistency by managing the addition, deletion, and renaming of VLANs on a network-wide basis. VTP minimizes misconfigurations and configuration inconsistencies that can cause several problems, such as duplicate VLAN names, incorrect VLAN-type specifications, and security violations.
Before you create VLANs, you must decide whether to use VTP in your network. Using VTP, you can make configuration changes centrally on one or more switches and have those changes automatically communicated to all the other switches in the network. Without VTP, you cannot send information about
VLANs to other switches.
VTP is designed to work in an environment where updates are made on a single switch and are sent through VTP to other switches in the domain. It does not work well in a situation where multiple updates to the VLAN database occur simultaneously on switches in the same domain, which would result in an inconsistency in the VLAN database.
The switch supports 1005 VLANs, but the number of routed ports, SVIs, and other configured features affects the usage of the switch hardware. If the switch is notified by VTP of a new VLAN and the switch is already using the maximum available hardware resources, it sends a message that there are not enough hardware resources available and shuts down the VLAN. The output of the show vlan user EXEC command shows the VLAN in a suspended state.
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
13-1 OL-27326-01
Understanding VTP
Chapter 13 Configuring VTP
VTP version 1 and version 2 support only normal-range VLANs (VLAN IDs 1 to 1005). Cisco IOS
Release 12.2(52)SE and later support VTP version 3. VTP version 3 supports the entire VLAN range
(VLANs 1 to 4094). Extended range VLANs (VLANs 1006 to 4094) are supported only in VTP version 3. You cannot convert from VTP version 3 to VTP version 2 if extended VLANs are configured in the domain.
These sections contain this conceptual information:
•
•
•
•
•
•
The VTP Domain
A VTP domain (also called a VLAN management domain) consists of one switch or several interconnected switches under the same administrative responsibility sharing the same VTP domain name. A switch can be in only one VTP domain. You make global VLAN configuration changes for the domain.
By default, the switch is in the VTP no-management-domain state until it receives an advertisement for a domain over a trunk link (a link that carries the traffic of multiple VLANs) or until you configure a domain name. Until the management domain name is specified or learned, you cannot create or modify
VLANs on a VTP server, and VLAN information is not propagated over the network.
If the switch receives a VTP advertisement over a trunk link, it inherits the management domain name and the VTP configuration revision number. The switch then ignores advertisements with a different domain name or an earlier configuration revision number.
Caution Before adding a VTP client switch to a VTP domain, always verify that its VTP configuration revision number is lower than the configuration revision number of the other switches in the VTP domain.
Switches in a VTP domain always use the VLAN configuration of the switch with the highest VTP configuration revision number. If you add a switch that has a revision number higher than the revision number in the VTP domain, it can erase all VLAN information from the VTP server and VTP domain.
See the
“Adding a VTP Client Switch to a VTP Domain” section on page 13-15
for the procedure for verifying and resetting the VTP configuration revision number.
When you make a change to the VLAN configuration on a VTP server, the change is propagated to all switches in the VTP domain. VTP advertisements are sent over all IEEE trunk connections, including
Inter-Switch Link (ISL) and IEEE 802.1Q. VTP dynamically maps VLANs with unique names and internal index associates across multiple LAN types. Mapping eliminates excessive device administration required from network administrators.
If you configure a switch for VTP transparent mode, you can create and modify VLANs, but the changes are not sent to other switches in the domain, and they affect only the individual switch. However, configuration changes made when the switch is in this mode are saved in the switch running configuration and can be saved to the switch startup configuration file.
For domain name and password configuration guidelines, see the
“VTP Configuration Guidelines” section on page 13-8 .
13-2
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 13 Configuring VTP
Understanding VTP
VTP Modes
Table 13-1
You can configure a supported switch to be in one of the VTP modes listed in
VTP Modes
VTP Mode
VTP server
VTP off
Description
In VTP server mode, you can create, modify, and delete VLANs, and specify other configuration parameters (such as the VTP version) for the entire VTP domain. VTP servers advertise their VLAN configurations to other switches in the same VTP domain and synchronize their VLAN configurations with other switches based on advertisements received over trunk links.
VTP server is the default mode.
VTP client
Note In VTP server mode, VLAN configurations are saved in NVRAM. If the switch detects a failure while writing a configuration to NVRAM, VTP mode automatically changes from server mode to client mode. If this happens, the switch cannot be returned to VTP server mode until the NVRAM is functioning.
A VTP client behaves like a VTP server and transmits and receives VTP updates on its trunks, but you cannot create, change, or delete VLANs on a VTP client. VLANs are configured on another switch in the domain that is in server mode.
In VTP versions 1 and 2, in VTP client mode, VLAN configurations are not saved in NVRAM. In VTP version 3, VLAN configurations are saved in NVRAM in client mode.
VTP transparent VTP transparent switches do not participate in VTP. A VTP transparent switch does not advertise its VLAN configuration and does not synchronize its VLAN configuration based on received advertisements.
However, in VTP version 2 or version 3, transparent switches do forward VTP advertisements that they receive from other switches through their trunk interfaces. You can create, modify, and delete VLANs on a switch in VTP transparent mode.
In VTP versions 1 and 2, the switch must be in VTP transparent mode when you create extended-range
VLANs. VTP version 3 also supports creating extended-range VLANs in client or server mode. See the
“Configuring Extended-Range VLANs” section on page 12-11
.
In VTP versions 1 and 2, the switch must be in VTP transparent mode when you create private VLANs and when they are configured, you should not change the VTP mode from transparent to client or server mode.
VTP version 3 also supports private VLANs in client and server modes. See
When the switch is in VTP transparent mode, the VTP and VLAN configurations are saved in NVRAM, but they are not advertised to other switches. In this mode, VTP mode and domain name are saved in the switch running configuration, and you can save this information in the switch startup configuration file by using the copy running-config startup-config privileged EXEC command.
A switch in VTP off mode functions in the same manner as a VTP transparent switch, except that it does not forward VTP advertisements on trunks.
VTP Advertisements
Each switch in the VTP domain sends periodic global configuration advertisements from each trunk port to a reserved multicast address. Neighboring switches receive these advertisements and update their VTP and VLAN configurations as necessary.
OL-27326-01
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
13-3
Chapter 13 Configuring VTP
Understanding VTP
Note Because trunk ports send and receive VTP advertisements, you must ensure that at least one trunk port is configured on the switch and that this trunk port is connected to the trunk port of another switch.
Otherwise, the switch cannot receive any VTP advertisements. For more information on trunk ports, see the
“Configuring VLAN Trunks” section on page 12-15 .
VTP advertisements distribute this global domain information:
•
•
•
VTP domain name
VTP configuration revision number
Update identity and update timestamp
• MD5 digest VLAN configuration, including maximum transmission unit (MTU) size for each
VLAN.
• Frame format
VTP advertisements distribute this VLAN information for each configured VLAN:
•
•
VLAN IDs (ISL and IEEE 802.1Q)
VLAN name
VLAN type •
•
•
VLAN state
Additional VLAN configuration information specific to the VLAN type
In VTP version 3, VTP advertisements also include the primary server ID, an instance number, and a start index.
VTP Version 2
If you use VTP in your network, you must decide which version of VTP to use. By default, VTP operates in version 1.
VTP version 2 supports these features that are not supported in version 1:
• Token Ring support—VTP version 2 supports Token Ring Bridge Relay Function (TrBRF) and
Token Ring Concentrator Relay Function (TrCRF) VLANs. For more information about Token Ring
VLANs, see the
“Configuring Normal-Range VLANs” section on page 12-4
.
•
•
Unrecognized Type-Length-Value (TLV) support—A VTP server or client propagates configuration changes to its other trunks, even for TLVs it is not able to parse. The unrecognized TLV is saved in
NVRAM when the switch is operating in VTP server mode.
Version-Dependent Transparent Mode—In VTP version 1, a VTP transparent switch inspects VTP messages for the domain name and version and forwards a message only if the version and domain name match. Although VTP version 2 supports only one domain, a VTP version 2 transparent switch forwards a message only when the domain name matches.
• Consistency Checks—In VTP version 2, VLAN consistency checks (such as VLAN names and values) are performed only when you enter new information through the CLI or SNMP. Consistency checks are not performed when new information is obtained from a VTP message or when information is read from NVRAM. If the MD5 digest on a received VTP message is correct, its information is accepted.
13-4
Cisco Catalyst Blade Switch 3030 for Dell Software Configuration Guide
OL-27326-01
Chapter 13 Configuring VTP
Understanding VTP
VTP Version 3
VTP version 3 supports these features that are not supported in version 1 or version 2:
• Enhanced authentication—You can configure the authentication as hidden or secret . When hidden , the secret key from the password string is saved in the VLAN database file, but it does not appear in plain text in the configuration. Instead, the key associated with the password is saved in hexadecimal format in the running configuration. You must reenter the password if you enter a takeover command in the domain. When you enter the secret keyword, you can directly configure the password secret key.
• Support for extended range VLAN (VLANs 1006 to 4094) database propagation. VTP versions 1 and 2 propagate only VLANs 1 to 1005. If extended VLANs are configured, you cannot convert from VTP version 3 to version 1 or 2.
Note VTP pruning still applies only to VLANs 1 to 1005, and VLANs 1002 to 1005 are still reserved and cannot be modified.
•
•
•
•
Private VLAN support.
Support for any database in a domain. In addition to propagating VTP information, version 3 can propagate Multiple Spanning Tree (MST) protocol database information. A separate instance of the
VTP protocol runs for each application that uses VTP.
VTP primary server and VTP secondary servers. A VTP primary server updates the database information and sends updates that are honored by all devices in the system. A VTP secondary server can only back up the updated VTP configurations received from the primary server to its NVRAM.
By default, all devices come up as secondary servers. You can enter the vtp primary privileged
EXEC command to specify a primary server. Primary server status is only needed for database updates when the administrator issues a takeover message in the domain. You can have a working
VTP domain without any primary servers. Primary server status is lost if the device reloads or domain parameters change, even when a password is configured on the switch.
The option to turn VTP on or off on a per-trunk (per-por