- Preface
- Using the Command Line Interface
- Catalyst 3750 Switch Cisco IOS Commands - aaa accounting through reserved-only
- Catalyst 3750 Switch Cisco IOS Commands - rmon collection through show vtp
- Catalyst 3750 Switch Cisco IOS Commands - shutdown through vtp
- Catalyst 3750 Switch Bootloader Commands
- Catalyst 3750 Switch Debug Commands
- Catalyst 3750 Switch Show Platform Commands
- Acknowledgments for Open-Source Software
Catalyst 3750 Command Reference, Release 12.2(55)SE
- Updated:
- August 8, 2016
Chapter: Catalyst 3750 Switch Cisco IOS Commands - aaa accounting through reserved-only
- aaa accounting dot1x
- aaa authentication dot1x
- aaa authorization network
- action
- archive copy-sw
- archive download-sw
- archive tar
- archive upload-sw
- arp access-list
- authentication command bounce-port ignore
- authentication command disable-port ignore
- authentication control-direction
- authentication event
- authentication fallback
- authentication host-mode
- authentication mac-move permit
- authentication open
- authentication order
- authentication periodic
- authentication port-control
- authentication priority
- authentication timer
- authentication violation
- auto qos cla ssify
- auto qo s trust
- auto qos voip
- boot auto-copy-sw
- boot auto-download-sw
- boot buffersize
- boot config-file
- boot enable-break
- boot helper
- boot helper-config-file
- boot manual
- boot private-config-file
- boot system
- cdp forward
- channel-group
- channel-protocol
- cisp enable
- class
- class-map
- clear dot1x
- clear eap sessions
- clear errdisable interface
- clear arp inspection log
- clear ip arp inspection statistics
- clear ip dhcp snooping
- clear ipc
- clear ipv6 dhcp conflict
- clear l2protocol-tunnel counters
- clear lacp
- clear mac address-table
- clear mac address-table move update
- clear nmsp statistics
- clear pagp
- clear port-security
- clear spanning-tree counters
- clear spanning-tree detected-protocols
- clear vmps statistics
- clear vtp counters
- cluster commander-address
- cluster discovery hop-count
- cluster enable
- cluster holdtime
- cluster member
- cluster outside-interface
- cluster run
- cluster standby-group
- cluster timer
- define interface-range
- delete
- deny (ARP access-list configuration)
- deny (IPv6 access-list configuration)
- deny (MAC access-list configuration)
- diagnostic monitor
- diagnostic schedule
- diagnostic start
- dot1x
- dot1x auth-fail max-attempts
- dot1x auth-fail vlan
- dot1x control-direction
- dot1x credentials (global configuration)
- dot1x critical (global configuration)
- dot1x critical (interface configuration)
- dot1x default
- dot1x fallback
- dot1x guest-vlan
- dot1x host-mode
- dot1x initialize
- dot1x mac-auth-bypass
- dot1x max-reauth-req
- dot1x max-req
- dot1x multiple-hosts
- dot1x pae
- dot1x port-control
- dot1x re-authenticate
- dot1x re-authentication
- dot1x reauthentication
- dot1x supplicant force-multicast
- dot1x test eapol-capable
- dot1x test timeout
- dot1x timeout
- dot1x violation-mode
- duplex
- epm access-control open
- errdisable detect cause
- errdisable detect cause small-frame
- errdisable recovery cause small-frame
- errdisable recovery
- exception crashinfo
- fallback profile
- flowcontrol
- interface port-channel
- interface range
- interface vlan
- ip access-group
- ip address
- ip admission
- ip admission name proxy http
- ip arp inspection filter vlan
- ip arp inspection limit
- ip arp inspection log-buffer
- ip arp inspection trust
- ip arp inspection validate
- ip arp inspection vlan
- ip arp inspection vlan logging
- ip device tracking probe
- ip dev ice tracking
- ip dhcp snooping
- ip dhcp snooping binding
- ip dhcp snooping database
- ip dhcp snooping information option
- ip dhcp snooping information option allow-untrusted
- ip dhcp snooping information option format remote-id
- ip dhcp snooping limit rate
- ip dhcp snooping trust
- ip dhcp snooping verify
- ip dhcp snooping vlan
- ip dhcp snooping vlan information option format-type circuit-id string
- ip igmp filter
- ip igmp max-groups
- ip igmp profile
- ip igmp snooping
- ip igmp snooping last-member-query-interval
- ip igmp snooping querier
- ip igmp snooping report-suppression
- ip igmp snooping tcn
- ip igmp snooping tcn flood
- ip igmp snooping vlan immediate-leave
- ip igmp snooping vlan mrouter
- ip igmp snooping vlan static
- ip snap forwarding
- ip source binding
- ip ssh
- ip sticky-arp (global configuration)
- ip sticky-arp (interface configuration)
- ip verify source
- ipv6 access-list
- ipv6 address dhcp
- ip v6 dhcp client request vendor
- ipv6 dhcp ping packets
- ipv6 dhcp pool
- ipv6 dhcp server
- ipv6 mld snooping
- ipv6 mld snooping last-listener-query-count
- ipv6 mld snooping last-listener-query-interval
- ipv6 mld snooping listener-message-suppression
- ipv6 mld snooping robustness-variable
- ipv6 mld snooping tcn
- ipv6 mld snooping vlan
- ipv6 traffic-filter
- l2protocol-tunnel
- l2protocol-tunnel cos
- lacp port-priority
- lacp system-priority
- link state group
- link state track
- location (global configuration)
- location (interface configuration)
- logging event
- logging event power-inline-status
- logging file
- mab request format attribute 32
- mac access-group
- mac access-list extended
- mac address-table aging-time
- mac address-table learning vlan
- mac address-table move update
- mac address-table notification
- mac address-table static
- mac address-table static drop
- match (access-map configuration)
- match (class-map configuration)
- mdix auto
- mls qos
- mls qos aggregate-policer
- mls qos cos
- mls qos dscp-mutation
- mls qos map
- mls qos queue-set output buffers
- mls qos queue-set output threshold
- mls qos rewrite ip dscp
- mls qos srr-queue input bandwidth
- mls qos srr-queue input buffers
- mls qos srr-queue input cos-map
- mls qos srr-queue input dscp-map
- mls qos srr-queue input priority-queue
- mls qos srr-queue input threshold
- mls qos srr-queue output cos-map
- mls qos srr-queue output dscp-map
- mls qos trust
- mls qos vlan-based
- monitor session
- mvr (global configuration)
- mvr (interface configuration)
- network-policy
- network-policy profile (global configuration)
- network-policy profile (network-policy configuration)
- nmsp
- nmsp attachment suppress
- no authentication logging verbose
- no dot1x logging verbose
- no mab logging verbose
- nsf
- pagp learn-method
- pagp port-priority
- permit (ARP access-list configuration)
- permit (IPv6 access-list configuration)
- permit (MAC access-list configuration)
- police
- police aggregate
- policy-map
- port-channel load-balance
- power inline
- power inline consumption
- power rps
- priority-queue
- private-vlan
- private-vlan mapping
- queue-set
- radius-server dead-criteria
- radius-server host
- rcommand
- reload
- remote command
- remote-span
- renew ip dhcp snooping database
- reserved-only
Catalyst 3750 Switch Cisco IOS Commands
aaa accounting dot1x
Use the aaa accounting dot1x global configuration command to enable authentication, authorization, and accounting (AAA) accounting and to create method lists defining specific accounting methods on a per-line or per-interface basis for IEEE 802.1x sessions. Use the no form of this command to disable IEEE 802.1x accounting.
aaa accounting dot1x { name | default } start-stop { broadcast group { name | radius | tacacs+ } [ group { name | radius | tacacs+ }... ] | group { name | radius | tacacs+ } [ group { name | radius | tacacs+ }...]}
no aaa accounting dot1x { name | default }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
This command requires access to a RADIUS server.
We recommend that you enter the dot1x reauthentication interface configuration command before configuring IEEE 802.1x RADIUS accounting on an interface.
Examples
This example shows how to configure IEEE 802.1x accounting:
Note
The RADIUS authentication server must be properly configured to accept and log update or watchdog packets from the AAA client.
Related Commands
|
|
|
Specifies one or more AAA methods for use on interfaces running IEEE 802.1x. |
|
dot1x timeout reauth-period |
Sets the number of seconds between re-authentication attempts. |
aaa authentication dot1x
Use the aaa authentication dot1x global configuration command to specify the authentication, authorization, and accounting (AAA) method to use on ports complying with the IEEE 802.1x authentication. Use the no form of this command to disable authentication.
aaa authentication dot1x { default } method1
no aaa authentication dot1x { default }
Syntax Description
Use the listed authentication method that follows this argument as the default method when a user logs in. |
|
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 strings, only the default and group radius keywords are supported.
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The method argument identifies the method that the authentication algorithm tries in the given sequence to validate the password provided by the client. The only method that is truly IEEE 802.1x-compliant is the group radius method, in which the client data is validated against a RADIUS authentication server.
If you specify group radius, you must configure the RADIUS server by entering the radius-server host global configuration command.
Use the show running-config privileged EXEC command to display the configured lists of authentication methods.
Examples
This example shows how to enable AAA and how to create an IEEE 802.1x-compliant authentication list. This authentication first tries to contact a RADIUS server. If this action returns an error, the user is not allowed access to the network.
You can verify your settings by entering the show running-config privileged EXEC command.
Related Commands
|
|
|
|---|---|
aaa authorization network
Use the aaa authorization network global configuration command to the configure the switch to use user-RADIUS authorization for all network-related service requests, such as IEEE 802.1x aaa-user access control lists (ACLs) or VLAN assignment. Use the no form of this command to disable RADIUS user authorization.
aaa authorization network default group radius
no aaa authorization network default
Syntax Description
Use the list of all RADIUS hosts in the server group as the default authorization list. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the aaa authorization network default group radius global configuration command to allow the switch to download IEEE 802.1x authorization parameters from the RADIUS servers in the default authorization list. The authorization parameters are used by features such as per-user ACLs or VLAN assignment to get parameters from the RADIUS servers.
Use the show running-config privileged EXEC command to display the configured lists of authorization methods.
Examples
This example shows how to configure the switch for user RADIUS authorization for all network-related service requests:
You can verify your settings by entering the show running-config privileged EXEC command.
Related Commands
|
|
|
|---|---|
action
Use the action access-map configuration command to set the action for the VLAN access map entry. Use the no form of this command to return to the default setting.
Syntax Description
Forward the packet when the specified conditions are matched. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You enter access-map configuration mode by using the vlan access-map global configuration command.
If the action is drop, you should define the access map, including configuring any access control list (ACL) names in match clauses, before applying the map to a VLAN, or all packets could be dropped.
In access-map configuration mode, use the match access-map configuration command to define the match conditions for a VLAN map. Use the action command to set the action that occurs when a packet matches the conditions.
The drop and forward parameters are not used in the no form of the command.
Examples
This example shows how to identify and apply a VLAN access map vmap4 to VLANs 5 and 6 that causes the VLAN to forward an IP packet if the packet matches the conditions defined in access list al2 :
You can verify your settings by entering the show vlan access-map privileged EXEC command.
Related Commands
|
|
|
|---|---|
archive copy-sw
Use the archive copy-sw privileged EXEC command on the stack master to copy the running image from the flash memory on one stack member to the flash memory on one or more other members.
archive copy-sw [ /destination-system destination-stack-member-number ] [ /force-reload ] [ leave-old-sw ] [ /no-set-boot ] [ /overwrite ] [ /reload ] [ /safe ] source-stack-member-number
Syntax Description
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The current software image is not overwritten with the copied image.
Both the software image and HTML files are copied.
The new image is copied to the flash: file system.
The BOOT environment variable is changed to point to the new software image on the flash: file system.
Image names are case sensitive; the image file is provided in tar format.
Note To successfully use the archive copy-sw privileged EXEC command, you must have downloaded from a TFTP server the images for both the member switch being added and the master. You use the archive download-sw privileged EXEC command to perform the download.
At least one member must be running the image that is to be copied to the switch that has incompatible software.
You can copy the image to more than one specific member by repeating the /destination -system destination-stack-member-number option in the command for each member to be upgraded. If you do not specify the destination-stack-member-number, the default is to copy the running image file to all members.
Using the /safe or /leave-old-sw option can cause the new copied image to fail if there is insufficient flash memory. If leaving the software in place would prevent the new image from fitting in flash memory due to space constraints, an error results.
If you used the /leave-old-sw option and did not overwrite the old image when you copied the new one, you can remove the old image by using the delete privileged EXEC command. For more information, see the “delete” section.
Use the /overwrite option to overwrite the image on the flash device with the copied one.
If you specify the command without the /overwrite option, the algorithm verifies that the new image is not the same as the one on the switch flash device or is not running on any members. If the images are the same, the copy does not occur. If the images are different, the old image is deleted, and the new one is copied.
After copying a new image, enter the reload privileged EXEC command to begin using the new image, or specify the /reload or /force-reload option in the archive copy-sw command.
You can enter one or more of these options with the s ource-stack-member-number option:
- /destination-system destination-stack-member-number
- / force-reload
- / leave-old-sw
- / no-set-boot
- / overwrite
- / reload
- /safe
If you enter the s ource-stack-member-number option before one of the previous options, you can enter only the archive copy-sw s ource-stack-member-number command.
These are examples of how you can enter the archive copy-sw command:
- To copy the running image from a member to another member and to overwrite the software image in the second member’s flash memory (if it already exists) with the copied one, enter the archive copy-sw /destination destination-stack-member-number /overwrite s ource-stack-member-number command.
- To copy the running image from a member to another member, keep the current software image, and reload the system after the image copies, enter the archive copy-sw /destination destination-stack-member-number /safe /reload s ource-stack-member-number command.
Examples
This example shows how to copy the running image from member 6 to member 8:
This example shows how to copy the running image from member 6 to all the other members:
This example shows how to copy the running image from member 5 to member 7. If the image being copied already exists on the second member’s flash memory, it can be overwritten with the copied one. The system reloads after the image is copied:
Related Commands
|
|
|
|---|---|
Creates a tar file, lists the files in a tar file, or extracts the files from a tar file. |
|
archive download-sw
Use the archive download-sw privileged EXEC command to download a new image from a TFTP server to the switch or switch stack and to overwrite or keep the existing image.
archive download-sw {/ allow-feature-upgrade | /directory | /force-reload | /imageonly | /leave-old-sw | /no-set-boot | /no-version-check | /destination-system stack-member-number | /only-system-type system-type | /overwrite | /reload | /safe } source-url
Syntax Description
Defaults
The current software image is not overwritten with the downloaded image.
Both the software image and HTML files are downloaded.
The new image is downloaded to the flash: file system.
The BOOT environment variable is changed to point to the new software image on the flash: file system.
Image names are case sensitive; the image file is provided in tar format.
Compatibility of the stack protocol version on the image to be downloaded is checked with the version on the stack.
Command Modes
Command History
|
|
|
|---|---|
The allow-feature-upgrade and directory keywords were added. |
Usage Guidelines
Use the /allow-feature-upgrade option to allow installation of an image with a different feature set, for example, upgrading from the IP base image to the IP services image.
Use the archive download-sw /directory command to specify a directory one time followed by a tar file or list of tar files to be downloaded instead of specifying complete paths with each tar file. For example, enter archive download-sw /directory tftp://10.1.1.10/ c3750-ipservices-tar.122-35.SE.tar c3750-ipbase-tar.122-35.SE.tar.
The /imageonly option removes the HTML files for the existing image if the existing image is being removed or replaced. Only the Cisco IOS image (without the HTML files) is downloaded.
Using the /safe or /leave-old-sw option can cause the new image download to fail if there is insufficient flash memory. If leaving the software in place prevents the new image from fitting in flash memory due to space constraints, an error results.
If you used the /leave-old-sw option and did not overwrite the old image when you downloaded the new one, you can remove the old image by using the delete privileged EXEC command. For more information, see the “delete” section.
Use the /no-version-check option if you want to download an image that has a different stack protocol version than the one existing on the stack. You must use this option with the /destination-system option to specify the specific member to be upgraded with the image.
Note Use the /no-version-check option with care. All members, including the master, must have the same stack protocol version to be in the same stack. This option allows an image to be downloaded without first confirming the compatibility of its stack protocol version with the version of the stack.
You can upgrade more than one specific stack member by repeating the /destination-system option in the command for each stack member to be upgraded.
Use the /overwrite option to overwrite the image on the flash device with the downloaded one.
If you specify the command without the /overwrite option, the download algorithm verifies that the new image is not the same as the one on the switch flash device or is not running on any stack members. If the images are the same, the download does not occur. If the images are different, the old image is deleted, and the new one is downloaded.
After downloading a new image, enter the reload privileged EXEC command to begin using the new image, or specify the /reload or /force-reload option in the archive download-sw command.
Use the /directory option to specify a directory for images.
Examples
This example shows how to download a new image from a TFTP server at 172.20.129.10 and to overwrite the image on the switch:
This example shows how to download only the software image from a TFTP server at 172.20.129.10 to the switch:
This example shows how to keep the old software version after a successful download:
This example specifies the location of two tar images without having to specify the path each time:
This example shows how to upgrade stack members 6 and 8:
Related Commands
archive tar
Use the archive tar privileged EXEC command to create a tar file, list files in a tar file, or extract the files from a tar file.
archive tar { /create destination-url flash:/ file-url } | { /table source-url } | { /xtract source-url flash:/ file-ur l [ dir/file ...]}
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
This example shows how to create a tar file. The command writes the contents of the new-configs directory on the local flash device to a file named saved.tar on the TFTP server at 172.20.10.30:
This example shows how to display the contents of the file that is in flash memory. The contents of the tar file appear on the screen:
This example shows how to display only the /html directory and its contents:
This example shows how to extract the contents of a tar file on the TFTP server at 172.20.10.30. This command extracts just the new-configs directory into the root directory on the local flash file system. The remaining files in the saved.tar file are ignored.
Related Commands
|
|
|
|---|---|
| Copies the running image from the flash memory on one stack member to the flash memory on one or more other stack members. |
|
archive upload-sw
Use the archive upload-sw privileged EXEC command to upload an existing switch image to a server.
archive upload-sw [ /source-system-num stack member number | /version version_string ] destination-url
Syntax Description
Defaults
Uploads the currently running image from the flash file system.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You must specify the /source-system-num option to use the /version option. Using these options together uploads the specified image, not the running image, of a specific stack member.
Use the upload feature only if the HTML files associated with the embedded device manager have been installed with the existing image.
The files are uploaded in this sequence: the Cisco IOS image, the HTML files, and info. After these files are uploaded, the software creates the tar file.
Examples
This example shows how to upload the currently running image on stack member 6 to a TFTP server at 172.20.140.2:
Related Commands
arp access-list
Use the arp access-list global configuration command to define an Address Resolution Protocol (ARP) access control list (ACL) or to add clauses to the end of a previously defined list. Use the no form of this command to delete the specified ARP access list.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
After entering the arp access-list command, you enter ARP access-list configuration mode, and these configuration commands are available:
- default : returns a command to its default setting.
- deny : specifies packets to reject. For more information, see the “deny (ARP access-list configuration)” section.
- exit : exits ARP access-list configuration mode.
- no : negates a command or returns to default settings.
- permit : specifies packets to forward. For more information, see the “permit (ARP access-list configuration)” section.
Use the permit and deny access-list configuration commands to forward and to drop ARP packets based on the specified matching criteria.
When the ARP ACL is defined, you can apply it to a VLAN by using the ip arp inspection filter vlan global configuration command. ARP packets containing only IP-to-MAC address bindings are compared to the ACL. All other types of packets are bridged in the ingress VLAN without validation. If the ACL permits a packet, the switch forwards it. If the ACL denies a packet because of an explicit deny statement, the switch drops the packet. If the ACL denies a packet because of an implicit deny statement, the switch compares the packet to the list of DHCP bindings (unless the ACL is static, which means that packets are not compared to the bindings).
Examples
This example shows how to define an ARP access list and to permit both ARP requests and ARP responses from a host with an IP address of 1.1.1.1 and a MAC address of 0000.0000.abcd:
You can verify your settings by entering the show arp access-list privileged EXEC command.
Related Commands
authentication command bounce-port ignore
Use the authentication command bounce-port ignore global configuration command on the switch stack or on a standalone switch to allow the switch to ignore a command to temporarily disable a port. Use the no form of this command to return to the default status.
authentication command bounce-port ignore
no authentication command bounce-port ignore
Syntax Description
Defaults
The switch accepts a RADIUS Change of Authorization (CoA) bounce port command.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The CoA bounce port command causes a link flap, which triggers a DHCP renegotiation from the host. This is useful when a VLAN change occurs and the endpoint is a device such as a printer, that has no supplicant to detect the change. Use this command to configure the switch to ignore the bounce port command.
Examples
This example shows how to instruct the switch to ignore a CoA bounce port command:
Related Commands
|
|
|
authentication command disable-port ignore
Use the authentication command disable-port ignore global configuration command on the switch stack or on a standalone switch to allow the switch to ignore a command to disable a port. Use the no form of this command to return to the default status.
authentication command disable-port ignore
no authentication command disable-port ignore
Syntax Description
Defaults
The switch accepts a RADIUS Change of Authorization (CoA) disable port command.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The CoA disable port command administratively shuts down a port hosting a session, resulting in session termination. Use this command to configure the switch to ignore this command.
Examples
This example shows how to instruct the switch to ignore a CoA disable port command:
Related Commands
|
|
|
authentication control-direction
Use the authentication control-direction interface configuration command to configure the port mode as unidirectional or bidirectional. Use the no form of this command to return to the default setting.
authentication control-direction {both | in}
no authentication control-direction
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the both keyword or the no form of this command to return to the default setting (bidirectional mode).
Examples
This example shows how to enable bidirectional mode:
This example shows how to enable unidirectional mode:
You can verify your settings by entering the show authentication privileged EXEC command.
Related Commands
authentication event
Use the authentication event interface configuration command to set the actions for specific authentication events on the port.
authentication event {fail [action [authorize vlan vlan-id | next-method] {| retry {retry count}]} { no-response action authorize vlan vlan-id} {server {alive action reinitialize} | {dead action [authorize | reinitialize vlan vlan-id]}}
no authentication event {fail [action [authorize vlan vlan-id | next-method] {| retry {retry count}]} {no-response action authorize vlan vlan-id} {server {alive action reinitialize} | {dead action [authorize | reinitialize vlan vlan-id]}}
Syntax Description
Configure the authentication, authorization, and accounting (AAA) server alive actions. |
|
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use this command with the fail, no-response, or event keywords to configure the switch response for a specific action.
- When the switch moves to the critical-authentication state, new hosts trying to authenticate are moved to the critical-authentication VLAN (or critical VLAN). This applies whether the port is in single-host, multiple-host, multiauth, or MDA mode. Authenticated hosts remain in the authenticated VLAN, and the reauthentication timers are disabled.
- If a client is running Windows XP and the critical 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 and a critical port receives an EAP-Success message, the DHCP configuration process might not re-initiate.
- If you enable a guest VLAN on an IEEE 802.1x port, the switch assigns clients to a guest VLAN when it does not receive a response to its Extensible Authentication Protocol over LAN (EAPOL) request/identity frame or when EAPOL packets are not sent by the client.
- The switch maintains the EAPOL packet history. If another EAPOL packet is detected on the port during the lifetime of the link, the guest VLAN feature is disabled. If the port is already in the guest VLAN state, the port returns to the unauthorized state, and authentication restarts. The EAPOL history is cleared.
- If the switch port is moved to the guest VLAN (multi-host mode), multiple non-IEEE 802.1x-capable clients are allowed access. If an IEEE 802.1x-capable client joins the same port on which the guest VLAN is configured, the port is put in the unauthorized state in the RADIUS-configured or user-configured access VLAN, and authentication restarts.
You can configure any active VLAN except a Remote Switched Port Analyzer (RSPAN) VLAN, a primary private VLAN, or a voice VLAN as an IEEE 802.1x guest VLAN. The guest VLAN feature is supported only on access ports. It is not supported on internal VLANs (routed ports) or trunk ports.
- When MAC authentication bypass is enabled on an IEEE 802.1x port, the switch can authorize clients based on the client MAC address if IEEE 802.1x authentication times out while waiting for an EAPOL message exchange. After detecting a client on an IEEE 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 “Using IEEE 802.1x Authentication with MAC Authentication Bypass” section in the “Configuring IEEE 802.1x Port-Based Authentication” chapter of the software configuration guide.
For authentication-fail events:
- If the supplicant fails authentication, the port is moved to a restricted VLAN, and an EAP success message is sent to the supplicant because it i s not notified of the actual authentication failure.
– If the EAP success message is not sent, the supplicant tries to authenticate every 60 seconds (the default) by sending an EAP-start message.
– Some hosts (for example, devices running Windows XP) cannot implement DHCP until they receive an EAP success message.
The restricted VLAN is supported only in single host mode (the default port mode). When a port is placed in a restricted VLAN, the supplicant's MAC address is added to the MAC address table. Any other MAC address on the port is treated as a security violation.
- You cannot configure an internal VLANs for Layer 3 ports as a restricted VLAN. You cannot specify the same VLAN as a restricted VLAN and as a voice VLAN.
Enable re-authentication with restricted VLANs. If re-authentication is disabled, the ports in the restricted VLANs do not receive re-authentication requests if it is disabled.
To start the re-authentication process, the restricted VLAN must receive a link-down event or an Extensible Authentication Protocol (EAP) logoff event from the port. If a host is connected through a hub:
– The port might not receive a link-down event when the host is disconnected.
– The port might not detect new hosts until the next re-authentication attempt occurs.
When you reconfigure a restricted VLAN as a different type of VLAN, ports in the restricted VLAN are also moved and stay in their currently authorized state.
Examples
This example shows how to configure the authentication event fail command:
This example shows how to configure a no-response action:
This example shows how to configure a server-response action:
This example shows how to configure a port to send both new and existing hosts to the critical VLAN when the RADIUS server is unavailable. Use this command for ports in multiple authentication (multiauth) mode or if the voice domain of the port is in MDA mode:
You can verify your settings by entering the show authentication privileged EXEC command.
Related Commands
authentication fallback
Use the authentication fallback interface configuration command to configure a port to use web authentication as a fallback method for clients that do not support IEEE 802.1x authentication. To return to the default setting, use the no form of this command.
no authentication fallback name
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You must enter the authentication port-control auto interface configuration command before configuring a fallback method.
You can only configure web authentication as a fallback method to 802.1x or MAB, so one or both of these authentication methods should be configured for the fallback to enable.
Examples
This example shows how to specify a fallback profile on a port:
You can verify your settings by entering the show authentication privileged EXEC command.
Related Commands
authentication host-mode
Use the authentication host-mode interface configuration command to set the authorization manager mode on a port.
authentication host-mode [multi-auth | multi-domain | multi-host | single-host]
no authentication host-mode [multi-auth | multi-domain | multi-host | single-host]
Syntax Description
Enable multiple-authorization mode (multiauth mode) on the port. |
|
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Single-host mode should be configured if only one data host is connected. Do not connect a voice device to authenticate on a single-host port. Voice device authorization fails if no voice VLAN is configured on the port.
Multi-domain mode should be configured if data host is connected through an IP Phone to the port. Multi-domain mode should be configured if the voice device needs to be authenticated.
Multi-auth mode should be configured to allow up to eight devices behind a hub to obtain secured port access through individual authentication. Only one voice device can be authenticated in this mode if a voice VLAN is configured.
Multi-host mode also offers port access for multiple hosts behind a hub, but multi-host mode gives unrestricted port access to the devices after the first user gets authenticated.
Examples
This example shows how to enable multiauth mode on a port:
This example shows how to enable multi-domain mode on a port:
Switch(config-if)# authentication host-mode multi-domain
This example shows how to enable multi-host mode on a port:
Switch(config)# authentication host-mode multi-host
This example shows how to enable single-host mode on a port:
Switch(config-if)# authentication host-mode single-host
You can verify your settings by entering the show authentication privileged EXEC command.
Related Commands
authentication mac-move permit
Use the authentication mac-move permit global configuration command to enable MAC move on a switch. Use the no form of this command to return to the default setting.
authentication mac-move permit
no authentication mac-move permit
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The command enables authenticated hosts to move between 802.1x-enabled ports on a switch. For example, if there is a device between an authenticated host and port, and that host moves to another port, the authentication session is deleted from the first port, and the host is reauthenticated on the new port.
If MAC move is disabled, and an authenticated host moves to another port, it is not reauthenticated, and a violation error occurs.
MAC move is not supported on port-security enabled 802.1x ports. If MAC move is globally configured on the switch and a port security-enabled host moves to an 802.1x-enabled port, a violation error occurs.
Examples
This example shows how to enable MAC move on a switch:
Related Commands
authentication open
Use the authentication open interface configuration command to enable or disable open access on a port. Use the no form of this command to disable open access.
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Open authentication must be enabled if a device requires network access before it is authenticated.
A port ACL should be used to restrict host access when open authentication is enabled.
Examples
This example shows how to enable open access on a port:
This example shows how to set the port to disable open access on a port:
Related Commands
authentication order
Use the authentication order interface configuration command to set the order of authentication methods used on a port.
authentication order [dot1x | mab] {webauth}
Syntax Description
Add MAC authentication bypass (MAB) to the order of authentication methods. |
|
Add web authentication to the order of authentication methods. |
Command Default
The default authentication order is dot1x followed by mab and webauth.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Ordering sets the order of methods that the switch attempts when trying to authenticate a new device connected to a port. If one method in the list is unsuccessful, the next method is attempted.
Each method can only be entered once. Flexible ordering is only possible between 802.1x and MAB.
Web authentication can be configured as either a standalone method or as the last method in the order after either 802.1x or MAB. Web authentication should be configured only as fallback to dot1x or mab.
Examples
This example shows how to add 802.1x as the first authentication method, MAB as the second method, and web authentication as the third method:
This example shows how to add MAC authentication Bypass (MAB) as the first authentication method and web authentication as the second authentication method:
You can verify your settings by entering the show authentication privileged EXEC command.
Related Commands
authentication periodic
Use the authentication periodic interface configuration command to enable or disable reauthentication on a port. Enter the no form of this command to disable reauthentication.
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You configure the amount of time between periodic re-authentication attempts by using the authentication timer reauthentication interface configuration command.
Examples
This example shows how to enable periodic reauthentication on a port:
This example shows how to disable periodic reauthentication on a port:
You can verify your settings by entering the show authentication privileged EXEC command.
Related Commands
authentication port-control
Use the authentication port-control interface configuration command to enable manual control of the port authorization state. Use the no form of this command to return to the default setting.
authentication port-control {auto | force-authorized | force-un authorized}
no authentication port-control {auto | force-authorized | force-un authorized}
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the auto keyword only on one of these port types:
- Trunk port—If you try to enable IEEE 802.1x authentication 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, an error message appears, and the port mode is not changed.
- Dynamic ports—A dynamic port can negotiate with its neighbor to become a trunk port. If you try to enable IEEE 802.1x authentication on a dynamic port, an error message appears, and IEEE 802.1x authentication is not enabled. If you try to change the mode of an IEEE 802.1x-enabled port to dynamic, an error message appears, and the port mode does not change.
- Dynamic-access ports—If you try to enable IEEE 802.1x authentication on a dynamic-access (VLAN Query Protocol [VQP]) port, an error message appears, and IEEE 802.1x authentication is not enabled. If you try to change an IEEE 802.1x-enabled port to dynamic VLAN, an error message appears, and the VLAN configuration does not change.
- EtherChannel port—Do not configure a port that is an active or a not-yet-active member of an EtherChannel as an IEEE 802.1x port. If you try to enable IEEE 802.1x authentication on an EtherChannel port, an error message appears, and IEEE 802.1x authentication is not enabled.
- Switched Port Analyzer (SPAN) and Remote SPAN (RSPAN) destination ports—You can enable IEEE 802.1x authentication on a port that is a SPAN or RSPAN destination port. However, IEEE 802.1x authentication is disabled until the port is removed as a SPAN or RSPAN destination. You can enable IEEE 802.1x authentication on a SPAN or RSPAN source port.
To globally disable IEEE 802.1x authentication on the switch, use the no dot1x system-auth-control global configuration command. To disable IEEE 802.1x authentication on a specific port or to return to the default setting, use the no authentication port-control interface configuration command.
Examples
This example shows how to set the port state to automatic:
This example shows how to set the port state to the force- authorized state:
This example shows how to set the port state to the force-unauthorized state:
You can verify your settings by entering the show authentication privileged EXEC command.
Related Commands
authentication priority
Use the authentication priority interface configuration command to add an authentication method to the port-priority list.
auth priority [dot1x | mab] {webauth}
no auth priority [dot1x | mab] {webauth}
Syntax Description
Add MAC authentication bypass (MAB) to the order of authentication methods. |
|
Add web authentication to the order of authentication methods. |
Command Default
The default priority is 802.1x authentication, followed by MAC authentication bypass and web authentication.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Ordering sets the order of methods that the switch attempts when trying to authenticate a new device is connected to a port.
When configuring multiple fallback methods on a port, set web authentication (webauth) last.
Assigning priorities to different authentication methods allows a higher-priority method to interrupt an in-progress authentication method with a lower priority.
Note If a client is already authenticated, it might be reauthenticated if an interruption from a higher-priority method occurs.
The default priority of an authentication method is equivalent to its position in execution-list order: 802.1x authentication, MAC authentication bypass, and web authentication. Use the dot1x, mab, and webauth keywords to change this default order.
Examples
This example shows how to set 802.1x as the first authentication method and web authentication as the second authentication method:
This example shows how to set MAC authentication Bypass (MAB) as the first authentication method and web authentication as the second authentication method:
You can verify your settings by entering the show authentication privileged EXEC command.
Related Commands
authentication timer
Use the authentication timer interface configuration command to configure the timeout and reauthentication parameters for an 802.1x-enabled port.
authentication timer {{[inactivity | reauthenticate] [server | am]} {restart value}}
no authentication timer {{[inactivity | reauthenticate] [server | am]} {restart value}}
Syntax Description
Defaults
The inactivity, server, and restart keywords are set to 60 seconds. The reauthenticate keyword is set to one hour.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
If a timeout value is not configured, an 802.1x session stays authorized indefinitely. No other host can use the port, and the connected host cannot move to another port on the same switch.
Examples
This example shows how to set the authentication inactivity timer to 60 seconds:
This example shows how to set the reauthentication timer to 120 seconds:
You can verify your settings by entering the show authentication privileged EXEC command.
Related Commands
authentication violation
Use the authentication violation interface configuration command to 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.
authentication violation {protect | replace | restrict | shutdown}
no authentication violation {protect | replace | restrict | shutdown}
Syntax Description
Defaults
By default authentication violation shutdown mode is enabled.
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to configure an IEEE 802.1x-enabled port as error disabled and to shut down when a new device connects it:
This example shows how to configure an 802.1x-enabled port to generate a system error message and to change the port to restricted mode when a new device connects to it:
This example shows how to configure an 802.1x-enabled port to ignore a new device when it connects to the port:
This example shows how to configure an 802.1x-enabled port to remove the current session and initiate authentication with a new device when it connects to the port:
You can verify your settings by entering the show authentication privileged EXEC command.
Related Commands
auto qos classify
Use the auto qos classify interface configuration command to automatically configure quality of service (QoS) classification for untrusted devices within a QoS domain. Use the no form of this command to return to the default setting.
no auto qos classify [ police ]
Syntax Description
Defaults
Auto-QoS classify is disabled on the port.
|
|
|
|
|
|
|---|---|---|---|---|
SRR1 shared |
||||
|
1.SRR = shaped round robin. Ingress queues support shared mode only. |
Table 1-2 shows the generated auto-QoS configuration for the egress queues.
|
|
|
|
|
|
|
|---|---|---|---|---|---|
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use this command to configure the QoS for trusted interfaces within the QoS domain. The QoS domain includes the switch, the network interior, and edge devices that can classify incoming traffic for QoS.
Auto-QoS configures the switch for connectivity with a trusted interface. The QoS labels of incoming packets are trusted. For nonrouted ports, the CoS value of the incoming packets is trusted. For routed ports, the DSCP value of the incoming packet is trusted.
To take advantage of the auto-QoS defaults, you should enable auto-QoS before you configure other QoS commands. You can fine-tune the auto-QoS configuration after you enable auto-QoS.
This is the policy map when the auto qos classify command is configured:
This is the policy map when the auto qos classify police command is configured:
Note The switch applies the auto-QoS-generated commands as if the commands were entered from the command-line interface (CLI). An existing user configuration can cause the application of the generated commands to fail or to be overridden by the generated commands. These actions occur without warning. If all the generated commands are successfully applied, any user-entered configuration that was not overridden remains in the running configuration. Any user-entered configuration that was overridden can be retrieved by reloading the switch without saving the current configuration to memory. If the generated commands fail to be applied, the previous running configuration is restored.
After auto-QoS is enabled, do not modify a policy map or aggregate policer that includes AutoQoS in its name. If you need to modify the policy map or aggregate policer, make a copy of it, and change the copied policy map or policer. To use the new policy map instead of the generated one, remove the generated policy map from the interface, and apply the new policy map.
To display the QoS configuration that is automatically generated when auto-QoS is enabled, enable debugging before you enable auto-QoS. Use the debug auto qos privileged EXEC command to enable auto-QoS debugging. For more information, see the debug auto qos command.
To disable auto-QoS on a port, use the no auto qos trust interface configuration command. Only the auto-QoS-generated interface configuration commands for this port are removed. If this is the last port on which auto-QoS is enabled and you enter the no auto qos trust command, auto-QoS is considered disabled even though the auto-QoS-generated global configuration commands remain (to avoid disrupting traffic on other ports affected by the global configuration). You can use the no mls qos global configuration command to disable the auto-QoS-generated global configuration commands. With QoS disabled, there is no concept of trusted or untrusted ports because the packets are not modified. The CoS, DSCP, and IP precedence values in the packet are not changed. Traffic is switched in pass-through mode. Packets are switched without any rewrites and classified as best effort without any policing.
Examples
This example shows how to enable auto-QoS classification of an untrusted device and police traffic:
You can verify your settings by entering the show auto qos interface interface-id privileged EXEC command.
Related Commands
|
|
|
|---|---|
Assigns the shared weights and enables bandwidth sharing on the four egress queues mapped to a port. |
|
auto qos trust
Use the auto qos trust interface configuration command on the switch stack or on a standalone switch to automatically configure quality of service (QoS) for trusted interfaces within a QoS domain. Use the no form of this command to return to the default setting.
no auto qos trust { cos | dscp }
Syntax Description
Defaults
Auto-QoS trust is disabled on the port.
When auto-QoS is enabled, it uses the ingress packet label to categorize traffic, to assign packet labels, and to configure the ingress and egress queues.
|
|
Traffic |
|
|
|
|
||
|---|---|---|---|---|---|---|---|
DSCP4 |
|||||||
CoS5 |
|||||||
|
|
|
|
|
|
|
|
|---|---|---|---|---|
SRR6 shared |
||||
|
6.SRR = shaped round robin. Ingress queues support shared mode only. |
|
|
|
|
|
|
|
|---|---|---|---|---|---|
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use this command to configure the QoS for trusted interfaces within the QoS domain. The QoS domain includes the switch, the network interior, and edge devices that can classify incoming traffic for QoS.
Auto-QoS configures the switch for connectivity with a trusted interface. The QoS labels of incoming packets are trusted. For nonrouted ports, the CoS value of the incoming packets is trusted. For routed ports, the DSCP value of the incoming packet is trusted.
To take advantage of the auto-QoS defaults, you should enable auto-QoS before you configure other QoS commands. You can fine-tune the auto-QoS configuration after you enable auto-QoS.
If the port is configured with auto-QoS trust, it trusts all the packets on the port. If the packets are not marked with a DSCP or CoS value, default marking takes affect.
Note The switch applies the auto-QoS-generated commands as if the commands were entered from the command-line interface (CLI). An existing user configuration can cause the application of the generated commands to fail or to be overridden by the generated commands. These actions occur without warning. If all the generated commands are successfully applied, any user-entered configuration that was not overridden remains in the running configuration. Any user-entered configuration that was overridden can be retrieved by reloading the switch without saving the current configuration to memory. If the generated commands fail to be applied, the previous running configuration is restored.
After auto-QoS is enabled, do not modify a policy map or aggregate policer that includes AutoQoS in its name. If you need to modify the policy map or aggregate policer, make a copy of it, and change the copied policy map or policer. To use the new policy map instead of the generated one, remove the generated policy map from the interface, and apply the new policy map.
To display the QoS configuration that is automatically generated when auto-QoS is enabled, enable debugging before you enable auto-QoS. Use the debug auto qos privileged EXEC command to enable auto-QoS debugging. For more information, see the debug auto qos command.
To disable auto-QoS on a port, use the no auto qos trust interface configuration command. Only the auto-QoS-generated interface configuration commands for this port are removed. If this is the last port on which auto-QoS is enabled and you enter the no auto qos trust command, auto-QoS is considered disabled even though the auto-QoS-generated global configuration commands remain (to avoid disrupting traffic on other ports affected by the global configuration). You can use the no mls qos global configuration command to disable the auto-QoS-generated global configuration commands. With QoS disabled, there is no concept of trusted or untrusted ports because the packets are not modified (the CoS, DSCP, and IP precedence values in the packet are not changed). Traffic is switched in pass-through mode (packets are switched without any rewrites and classified as best effort without any policing).
Examples
This example shows how to enable auto-QoS for a trusted interface with specific cos classification.
You can verify your settings by entering the show auto qos interface interface-id privileged EXEC command.
Related Commands
|
|
|
|---|---|
Assigns the shared weights and enables bandwidth sharing on the four egress queues mapped to a port. |
|
auto qos voip
Use the auto qos voip interface configuration command to automatically configure quality of service (QoS) for voice over IP (VoIP) within a QoS domain. Use the no form of this command to return to the default setting.
auto qos voip { cisco-phone | cisco-softphone | trust }
no auto qos voip [ cisco-phone | cisco-softphone | trust ]
Syntax Description
Defaults
When auto-QoS is enabled, it uses the ingress packet label to categorize traffic, to assign packet labels, and to configure the ingress and egress queues.
|
|
Traffic |
|
|
|
|
||
|---|---|---|---|---|---|---|---|
DSCP9 |
|||||||
CoS10 |
|||||||
|
|
|
|
|
|
|
|
|---|---|---|---|---|
SRR11 shared |
||||
|
11.SRR = shaped round robin. Ingress queues support shared mode only. |
|
|
|
|
|
|
|
|---|---|---|---|---|---|
Command Modes
Command History
|
|
|
|---|---|
The cisco-softphone keyword was added, and the generated auto-QoS configuration changed. |
|
Usage Guidelines
Use this command to configure the QoS appropriate for VoIP traffic within the QoS domain. The QoS domain includes the switch, the interior of the network, and edge devices that can classify incoming traffic for QoS.
Auto-QoS configures the switch for VoIP with Cisco IP Phones on switch and routed ports and for VoIP with devices running the Cisco SoftPhone application. These releases support only Cisco IP SoftPhone Version 1.3(3) or later. Connected devices must use Cisco Call Manager Version 4 or later.
The show auto qos command output shows the service policy information for the Cisco IP phone.
To take advantage of the auto-QoS defaults, you should enable auto-QoS before you configure other QoS commands. You can fine-tune the auto-QoS configuration after you enable auto-QoS.
Note The switch applies the auto-QoS-generated commands as if the commands were entered from the command-line interface (CLI). An existing user configuration can cause the application of the generated commands to fail or to be overridden by the generated commands. These actions occur without warning. If all the generated commands are successfully applied, any user-entered configuration that was not overridden remains in the running configuration. Any user-entered configuration that was overridden can be retrieved by reloading the switch without saving the current configuration to memory. If the generated commands fail to be applied, the previous running configuration is restored.
If this is the first port on which you have enabled auto-QoS, the auto-QoS-generated global configuration commands are executed followed by the interface configuration commands. If you enable auto-QoS on another port, only the auto-QoS-generated interface configuration commands for that port are executed.
When you enable the auto-QoS feature on the first port, these automatic actions occur:
- QoS is globally enabled (mls qos global configuration command), and other global configuration commands are added.
- When you enter the auto qos voip cisco-phone interface configuration command on a port at the edge of the network that is connected to a Cisco IP Phone, the switch enables the trusted boundary feature. The switch uses the Cisco Discovery Protocol (CDP) to detect the presence or absence of a Cisco IP Phone. When a Cisco IP Phone is detected, the ingress classification on the port is set to trust the QoS label received in the packet. The switch also uses policing to determine whether a packet is in or out of profile and to specify the action on the packet. If the packet does not have a DSCP value of 24, 26, or 46 or is out of profile, the switch changes the DSCP value to 0. When a Cisco IP Phone is absent, the ingress classification is set to not trust the QoS label in the packet. The switch configures ingress and egress queues on the port according to the settings in Table 1-7 and Table 1-8 . The policing is applied to traffic matching the policy-map classification before the switch enables the trust boundary feature.
If the switch port was configured by using the auto qos voip cisco-phone interface configuration command in Cisco IOS Release 12.2(37)SE or earlier, the auto-QoS generated commands new to Cisco IOS Release 12.2(40)SE are not applied to the port. To have these commands automatically applied, you must remove and then reapply the configuration to the port.
- When you enter the auto qos voip cisco-softphone interface configuration command on a port at the edge of the network that is connected to a device running the Cisco SoftPhone, the switch uses policing to decide whether a packet is in or out of profile and to specify the action on the packet. If the packet does not have a DSCP value of 24, 26, or 46 or is out of profile, the switch changes the DSCP value to 0. The switch configures ingress and egress queues on the port according to the settings in Table 1-7 and Table 1-8 .
- When you enter the auto qos voip trust interface configuration command on a port connected to the interior of the network, the switch trusts the CoS value for nonrouted ports or the DSCP value for routed ports in ingress packets (the assumption is that traffic has already been classified by other edge devices). The switch configures the ingress and egress queues on the port according to the settings in Table 1-7 and Table 1-8 .
You can enable auto-QoS on static, dynamic-access, and voice VLAN access, and trunk ports. When enabling auto-QoS with a Cisco IP Phone on a routed port, you must assign a static IP address to the IP phone.
Note When a device running Cisco SoftPhone is connected to a switch or routed port, the switch supports only one Cisco SoftPhone application per port.
After auto-QoS is enabled, do not modify a policy map or aggregate policer that includes AutoQoS in its name. If you need to modify the policy map or aggregate policer, make a copy of it, and change the copied policy map or policer. To use the new policy map instead of the generated one, remove the generated policy map from the interface, and apply the new policy map.
To display the QoS configuration that is automatically generated when auto-QoS is enabled, enable debugging before you enable auto-QoS. Use the debug auto qos privileged EXEC command to enable auto-QoS debugging.
To disable auto-QoS on a port, use the no auto qos voip interface configuration command. Only the auto-QoS-generated interface configuration commands for this port are removed. If this is the last port on which auto-QoS is enabled and you enter the no auto qos voip command, auto-QoS is considered disabled even though the auto-QoS-generated global configuration commands remain (to avoid disrupting traffic on other ports affected by the global configuration). You can use the no mls qos global configuration command to disable the auto-QoS-generated global configuration commands. With QoS disabled, there is no concept of trusted or untrusted ports because the packets are not modified (the CoS, DSCP, and IP precedence values in the packet are not changed). Traffic is switched in pass-through mode (packets are switched without any rewrites and classified as best effort without any policing).
On a port on which the auto qos voip command is enabled, the queue-set ID that is generated depends on the interface:
- For a Fast Ethernet interface, auto-QoS generates queue-set 1 (which is the default).
- For a Gigabit Ethernet interface, auto-QoS generates queue-set 2.
This is the enhanced configuration for the auto qos voip cisco-phone command:
This is the enhanced configuration for the auto qos voip cisco-softphone command:
Examples
This example shows how to enable auto-QoS and to trust the QoS labels received in incoming packets when the switch or router connected to the port is a trusted device:
You can verify your settings by entering the show auto qos interface interface-id privileged EXEC command.
Related Commands
boot auto-copy-sw
Use the boot auto-copy-sw global configuration command from the stack master to enable the automatic upgrade (auto-upgrade) process. It automatically upgrades a switch in version-mismatch mode by copying the running software image on any stack member or by copying a tar file image in switch stack flash memory. Use the no form of this command to disable the auto-upgrade process.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
A switch in version-mismatch mode is a switch that has a different minor version number than the version on the stack. A switch in version-mismatch mode cannot join the stack as a fully functioning member. If the stack has an image that can be copied to a switch in version-mismatch mode, the auto-upgrade process automatically copies the image from a stack member to the switch in version-mismatch mode. The switch then exits version-mismatch mode, reboots, and joins the stack as a fully functioning member.
The auto-upgrade process affects only switches in version-mismatch mode. It does not affect existing stack members.
Related Commands
|
|
|
|---|---|
boot auto-download-sw
Use the boot auto-download-sw global configuration command to specify a URL pathname to use for automatic software upgrades. Use the no form of this command to return to the default setting.
boot auto-download-sw source-url
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
This command specifies a path URL to use for automatic software upgrades.
You can use this command to configure the URL for the master switch to access in case of a version-mismatch.
Related Commands
|
|
|
|---|---|
boot buffersize
Use the boot buffersize global configuration command on the switch stack or on a standalone switch to configure the NVRAM size. Use the no form of this command to return to the default.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
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.
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.
Examples
This example shows how to configure the NVRAM buffer size:
Switch(config)# boot buffersize 524288
Switch(config)# end
Related Commands
|
|
|
|---|---|
boot config-file
Use the boot config-file global configuration command on a standalone switch to specify the filename that Cisco IOS uses to read and write a nonvolatile copy of the system configuration. Use the no form of this command to return to the default setting.
boot config-file flash: / file-url
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
This command works properly only from a standalone switch.
Filenames and directory names are case sensitive.
This command changes the setting of the CONFIG_FILE environment variable. For more information, see Appendix 1, “Catalyst 3750 Switch Bootloader Commands.”
Related Commands
|
|
|
|---|---|
boot enable-break
Use the boot enable-break global configuration command on a standalone switch to enable interrupting the automatic boot process. Use the no form of this command to return to the default setting.
Syntax Description
Defaults
Disabled. The automatic boot process cannot be interrupted by pressing the Break key on the console.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
This command works properly only from a standalone switch.
When you enter this command, you can interrupt the automatic boot process by pressing the Break key on the console after the flash file system is initialized.
Note Despite the setting of this command, you can interrupt the automatic boot process at any time by pressing the MODE button on the switch front panel.
This command changes the setting of the ENABLE_BREAK environment variable. For more information, see Appendix 1, “Catalyst 3750 Switch Bootloader Commands.”
Related Commands
|
|
|
|---|---|
boot helper
Use the boot helper global configuration command to dynamically load files during boot loader initialization to extend or patch the functionality of the boot loader. Use the no form of this command to return to the default.
boot helper filesystem :/ file-url...
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
This variable is used only for internal development and testing.
Filenames and directory names are case sensitive.
This command changes the setting of the HELPER environment variable. For more information, see Appendix 1, “Catalyst 3750 Switch Bootloader Commands.”
Related Commands
|
|
|
|---|---|
boot helper-config-file
Use the boot helper-config-file global configuration command to specify the name of the configuration file to be used by the Cisco IOS helper image. If this is not set, the file specified by the CONFIG_FILE environment variable is used by all versions of Cisco IOS that are loaded. Use the no form of this command to return to the default setting.
boot helper-config-file filesystem :/ file-url
Syntax Description
Alias for a flash file system. Use flash: for the system board flash device. |
|
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
This variable is used only for internal development and testing.
Filenames and directory names are case sensitive.
This command changes the setting of the HELPER_CONFIG_FILE environment variable. For more information, see Appendix 1, “Catalyst 3750 Switch Bootloader Commands.”
Related Commands
|
|
|
|---|---|
boot manual
Use the boot manual global configuration command on a standalone switch to enable manually booting the switch during the next boot cycle. Use the no form of this command to return to the default setting.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
This command works properly only from a standalone switch.
The next time you reboot the system, the switch is in boot loader mode, which is shown by the switch: prompt. To boot up the system, use the boot boot loader command, and specify the name of the bootable image.
This command changes the setting of the MANUAL_BOOT environment variable. For more information, see Appendix 1, “Catalyst 3750 Switch Bootloader Commands.”
Related Commands
|
|
|
|---|---|
boot private-config-file
Use the boot private-config-file global configuration command on a standalone switch to specify the filename that Cisco IOS uses to read and write a nonvolatile copy of the private configuration. Use the no form of this command to return to the default setting.
boot private-config-file filename
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
This example shows how to specify the name of the private configuration file to be pconfig :
Related Commands
|
|
|
|---|---|
boot system
Use the boot system global configuration command to specify the Cisco IOS image to load during the next boot cycle. Use the no form of this command to return to the default setting.
boot system { filesystem :/ file-url ... | switch { number | all }}
no boot system switch { number | all }
Syntax Description
Defaults
The switch attempts to automatically boot up the system by 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.
Command Modes
Command History
|
|
|
|---|---|
The switch { number | all } keywords were added. The boot system command now works properly on switch stacks and standalone switches. |
Usage Guidelines
Filenames and directory names are case sensitive.
If you enter the boot system f ilesystem:/file-url command on the stack master, the specified software image is loaded only on the stack master during the next boot cycle.
On the stack master, use the boot system switch number command to specify that the software image is loaded on the specified stack member during the next boot cycle. Use the boot system switch all command to specify that the software image is loaded on all the stack members during the next boot cycle.
When you enter the boot system switch number or the boot system switch all command on the stack master, the stack master checks if a software image is already on the stack member (except on the stack master). If the software image does not exist on the stack member (for example, stack member 1), an error message like this appears:
When you enter the boot system switch number command on the stack master, you can specify only one stack member for the number variable. Entering more than one stack member for the number variable is not supported.
If you are using the archive download-sw privileged EXEC command to maintain system images, you never need to use the boot system command. The boot system command is automatically manipulated to load the downloaded image.
This command changes the setting of the BOOT environment variable. For more information, see Appendix 1, “Catalyst 3750 Switch Bootloader Commands.”
Related Commands
|
|
|
|---|---|
cdp forward
To specify the ingress and egress switch ports for CDP traffic, use the cdp forward global configuration command. To return to the default setting, use the no form of this command.
cdp forward ingress port-id egress port-id
no cdp forward ingress port-id
Syntax Description
Specifies the switch port that receives the CDP packet from an IP phone. |
|
Specifies the switch port that forwards the CDP packet to the Cisco TelePresence System. |
Defaults
The default path for CDP packets through the switch is from any ingress port to the egress port connected to the Cisco TelePresence System.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You must use only CDP-enabled phones with TelePresence E911 IP phone support.
You can connect the IP phone and codec in the Cisco TelePresence System through any two ports in a switch stack.
Examples
Related Commands
|
|
|
|---|---|
channel-group
Use the channel-group interface configuration command to assign an Ethernet port to an EtherChannel group, to enable an EtherChannel mode, or both. Use the no form of this command to remove an Ethernet port from an EtherChannel group.
channel-group channel -group-number mode { active | { auto [ non-silent ]} | { desirable [ non-silent ]} | on | passive }
PAgP modes:
channel-group channel -group-number mode { { auto [ non-silent ]} | { desirable [ non-silent}}
LACP modes:
channel-group channel -group-number mode {active | passive}
On mode:
channel-group channel -group-number mode on
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
The channel -group-number range was changed from 1 to 12 to 1 to 48. |
|
Usage Guidelines
For Layer 2 EtherChannels, you do not have to create a port-channel interface first by using the interface port-channel global configuration command before assigning a physical port to a channel group. Instead, you can use the channel-group interface configuration command. It automatically creates the port-channel interface when the channel group gets its first physical port if the logical interface is not already created. If you create the port-channel interface first, the channel-group-number can be the same as the port - channel-number, or you can use a new number. If you use a new number, the channel-group command dynamically creates a new port channel.
You do not have to disable the IP address that is assigned to a physical port that is part of a channel group, but we strongly recommend that you do so.
You create Layer 3 port channels by using the interface port-channel command followed by the no switchport interface configuration command. You should manually configure the port-channel logical interface before putting the interface into the channel group.
After you configure an EtherChannel, configuration changes that you make on the port-channel interface apply to all the physical ports assigned to the port-channel interface. Configuration changes applied to the physical port affect only the port where you apply the configuration. To change the parameters of all ports in an EtherChannel, apply configuration commands to the port-channel interface, for example, spanning-tree commands or commands to configure a Layer 2 EtherChannel as a trunk.
If you do not specify non-silent with the auto or desirable mode, silent is assumed. The silent mode is used when the switch is connected to a device that is not PAgP-capable and seldom, if ever, sends packets. A example of a silent partner is a file server or a packet analyzer that is not generating traffic. In this case, running PAgP on a physical port prevents that port from ever becoming operational. However, it allows PAgP to operate, to attach the port to a channel group, and to use the port for transmission. Both ends of the link cannot be set to silent.
In the on mode, an EtherChannel exists only when a port group in the on mode is connected to another port group in the on mode.
You should use care when using the on mode. This is a manual configuration, and ports on both ends of the EtherChannel must have the same configuration. If the group is misconfigured, packet loss or spanning-tree loops can occur.
A cross-stack EtherChannel supports up to two 10-Gigabit Ethernet interfaces.
Do not configure an EtherChannel in both the PAgP and LACP modes. EtherChannel groups running PAgP and LACP can coexist on the same switch or on different switches in the stack (but not in a cross-stack configuration). Individual EtherChannel groups can run either PAgP or LACP, but they cannot interoperate.
If you set the protocol by using the channel-protocol interface configuration command, the setting is not overridden by the channel-group interface configuration command.
Do not configure a port that is an active or a not-yet-active member of an EtherChannel as an IEEE 802.1x port. If you try to enable IEEE 802.1x authentication on an EtherChannel port, an error message appears, and IEEE 802.1x authentication is not enabled.
Do not configure a secure port as part of an EtherChannel or an EtherChannel port as a secure port.
For a complete list of configuration guidelines, see the “Configuring EtherChannels” chapter in the software configuration guide for this release.
Do not enable Layer 3 addresses on the physical EtherChannel ports. Do not assign bridge groups on the physical EtherChannel ports because it creates loops.
Examples
This example shows how to configure an EtherChannel on a single switch. It assigns two static-access ports in VLAN 10 to channel 5 with the PAgP mode desirable :
This example shows how to configure an EtherChannel on a single switch. It assigns two static-access ports in VLAN 10 to channel 5 with the LACP mode active :
This example shows how to configure a cross-stack EtherChannel. It uses LACP passive mode and assigns two ports on stack member 2 and one port on stack member 3 as static-access ports in VLAN 10 to channel 5:
You can verify your settings by entering the show running-config privileged EXEC command.
Related Commands
|
|
|
|---|---|
channel-protocol
Use the channel-protocol interface configuration command to restrict the protocol used on a port to manage channeling. Use the no form of this command to return to the default setting.
channel-protocol { lacp | pagp }
Syntax Description
Configure an EtherChannel with the Link Aggregation Control Protocol (LACP). |
|
Configure an EtherChannel with the Port Aggregation Protocol (PAgP). |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the channel-protocol command only to restrict a channel to LACP or PAgP. If you set the protocol by using the channel-protocol command, the setting is not overridden by the channel-group interface configuration command.
You must use the channel-group interface configuration command to configure the EtherChannel parameters. The channel-group command also can set the mode for the EtherChannel.
You cannot enable both the PAgP and LACP modes on an EtherChannel group.
PAgP and LACP are not compatible; both ends of a channel must use the same protocol.
Examples
This example shows how to specify LACP as the protocol that manages the EtherChannel:
You can verify your settings by entering the show etherchannel [ channel-group-number ] protocol privileged EXEC command.
Related Commands
|
|
|
|---|---|
show etherchannel protocol |
cisp enable
Use the cisp enable global configuration command to enable Client Information Signalling Protocol (CISP) on a switch so that it acts as an authenticator to a supplicant switch.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The link between the authenticator and supplicant switch is a trunk. When you enable VTP on both switches, the VTP domain name must be the same, and the VTP mode must be server.
When you configure VTP mode, to avoid the MD5 checksum mismatch error, verify that:
Examples
This example shows how to enable CISP:
Related Commands
|
|
|
|---|---|
class
Use the class policy-map configuration command to define a traffic classification match criteria (through the police, set, and trust policy-map class configuration commands) for the specified class-map name. Use the no form of this command to delete an existing class map.
class { class-map-name | class-default }
no class { class-map-name | class-default }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Before using the class command, you must use the policy-map global configuration command to identify the policy map and to enter policy-map configuration mode. After specifying a policy map, you can configure a policy for new classes or modify a policy for any existing classes in that policy map. You attach the policy map to a port by using the service-policy interface configuration command.
After entering the class command, you enter policy-map class configuration mode, and these configuration commands are available:
- exit : exits policy-map class configuration mode and returns to policy-map configuration mode.
- no : returns a command to its default setting.
- police : defines a policer or aggregate policer for the classified traffic. The policer specifies the bandwidth limitations and the action to take when the limits are exceeded. For more information, see the police and police aggregate policy-map class commands.
- set : specifies a value to be assigned to the classified traffic. For more information, see the set command.
- trust : defines a trust state for traffic classified with the class or the class-map command. For more information, see the trust command.
To return to policy-map configuration mode, use the exit command. To return to privileged EXEC mode, use the end command.
The class command performs the same function as the class-map global configuration command. Use the class command when a new classification, which is not shared with any other ports, is needed. Use the class-map command when the map is shared among many ports.
You can configure a default class by using the class class-default policy-map configuration command. Unclassified traffic (traffic that does not meet the match criteria specified in the traffic classes) is treated as default traffic.
Examples
This example shows how to create a policy map called policy1. When attached to the ingress direction, it matches all the incoming traffic defined in class1, sets the IP Differentiated Services Code Point (DSCP) to 10, and polices the traffic at an average rate of 1 Mb/s and bursts at 20 KB. Traffic exceeding the profile is marked down to a DSCP value gotten from the policed-DSCP map and then sent.
This example shows how to configure a default traffic class to a policy map:
This example shows how the default traffic class is automatically placed at the end of policy-map pm3 even though class-default was configured first:
Related Commands
class-map
Use the class-map global configuration command to create a class map to be used for matching packets to the class name you specify and to enter class-map configuration mode. Use the no form of this command to delete an existing class map and to return to global configuration mode.
class-map [ match-all | match-any ] class-map-name
no class-map [ match-all | match-any ] class-map-name
Syntax Description
Defaults
If neither the match-all or match-any keyword is specified, the default is match-all.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use this command to specify the name of the class for which you want to create or modify class-map match criteria and to enter class-map configuration mode.
The class-map command and its subcommands are used to define packet classification, marking, and aggregate policing as part of a globally named service policy applied on a per-port basis.
After you are in quality of service (QoS) class-map configuration mode, these configuration commands are available:
- description : describes the class map (up to 200 characters). The show class-map privileged EXEC command displays the description and the name of the class-map.
- exit : exits from QoS class-map configuration mode.
- match : configures classification criteria. For more information, see the match (class-map configuration) command.
- no : removes a match statement from a class map.
- rename : renames the current class map. If you rename a class map with a name that is already used, the message
A class-map with this name already existsappears.
To define packet classification on a physical-port basis, only one match command per class map is supported. In this situation, the match-all and match-any keywords are equivalent.
Only one access control list (ACL) can be configured in a class map. The ACL can have multiple access control entries (ACEs).
Examples
This example shows how to configure the class map called class1 with one match criterion, which is an access list called 103 :
This example shows how to delete the class map class1 :
You can verify your settings by entering the show class-map privileged EXEC command.
Related Commands
clear dot1x
Use the clear dot1x privileged EXEC command to clear IEEE 802.1x information for the switch or for the specified port.
clear dot1x { all | interface interface-id }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You can clear all the information by using the clear dot1x all command, or you can clear only the information for the specified interface by using the clear dot1x interface interface-id command.
Examples
This example shows how to clear all IEEE 8021.x information:
Switch# clear dot1x all
This example shows how to clear IEEE 8021.x information for the specified interface:
Switch# clear dot1x interface gigabithethernet1/0/1
Switch# clear dot1x interface gigabithethernet1/1
You can verify that the information was deleted by entering the show dot1x privileged EXEC command.
Related Commands
|
|
|
|---|---|
Displays IEEE 802.1x statistics, administrative status, and operational status for the switch or for the specified port. |
clear eap sessions
Use the clear eap sessions privileged EXEC command to clear Extensible Authentication Protocol (EAP) session information for the switch or for the specified port.
clear eap sessions [ credentials name [ interface interface-id ] | interface interface-id | method name | transport name ] [ credentials name | interface interface-id | transport name ]...
Syntax Description
Clear EAP transport information for the specified lower level. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You can clear all counters by using the clear eap sessions command, or you can clear only the specific information by using the keywords.
Examples
This example shows how to clear all EAP information:
Switch# clear eap
This example shows how to clear EAP-session credential information for the specified profile:
Switch# clear eap sessions credential type1
You can verify that the information was deleted by entering the show dot1x privileged EXEC command.
Related Commands
|
|
|
|---|---|
Displays EAP registration and session information for the switch or for the specified port |
clear errdisable interface
Use the clear errdisable interface privileged EXEC command to re-enable a VLAN that was error disabled.
clear errdisable interface interface-id vlan [vlan-list]
Syntax Description
(Optional) Specify a list of VLANs to be re-enabled. If a vlan-list is not specified, then all VLANs are re-enabled. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You can re-enable a port by using the shutdown and no shutdown interface configuration commands, or you can clear error disable for VLANs by using the clear errdisable interface command.
Examples
This example shows how to re-enable all VLANs that were error-disabled on port 2.
Switch# clear errdisable interface GigabitEthernet4/0/2 vlan
Related Commands
|
|
|
|---|---|
Enables error-disabled detection for a specific cause or all causes. |
|
show interfaces status err-disabled |
Displays interface status of a list of interfaces in error-disabled state. |
clear arp inspection log
Use the clear ip arp inspection log privileged EXEC command to clear the dynamic Address Resolution Protocol (ARP) inspection log buffer.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to clear the contents of the log buffer:
Switch# clear ip arp inspection log
You can verify that the log was cleared by entering the show ip arp inspection log privileged command.
Related Commands
|
|
|
|---|---|
show inventory log |
Displays the configuration and contents of the dynamic ARP inspection log buffer. |
clear ip arp inspection statistics
Use the clear ip arp inspection statistics privileged EXEC command to clear the dynamic Address Resolution Protocol (ARP) inspection statistics.
clear ip arp inspection statistics [ vlan vlan-range ]
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to clear the statistics for VLAN 1:
You can verify that the statistics were deleted by entering the show ip arp inspection statistics vlan 1 privileged EXEC command.
Related Commands
|
|
|
|---|---|
show inventory statistics |
Displays statistics for forwarded, dropped, MAC validation failure, and IP validation failure packets for all VLANs or the specified VLAN. |
clear ip dhcp snooping
Use the clear ip dhcp snooping privileged EXEC command to clear the DHCP snooping binding database, the DHCP snooping binding database agent statistics, or the DHCP snooping statistics counters.
clear ip dhcp snooping { binding {* | ip-address | interface interface-id | vlan vlan-id } | database statistics | statistics }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
The *, ip-address, interface interface-id, and vlan vlan-id keywords were introduced. |
Usage Guidelines
When you enter the clear ip dhcp snooping database statistics command, the switch does not update the entries in the binding database and in the binding file before clearing the statistics.
Examples
This example shows how to clear the DHCP snooping binding database agent statistics:
You can verify that the statistics were cleared by entering the show ip dhcp snooping database privileged EXEC command.
This example shows how to clear the DHCP snooping statistics counters:
Switch# clear ip dhcp snooping statistics
You can verify that the statistics were cleared by entering the show ip dhcp snooping statistics user EXEC command.
Related Commands
|
|
|
|---|---|
Configures the DHCP snooping binding database agent or the binding file. |
|
Displays the DHCP snooping binding database agent statistics. |
|
show ip dhcp snooping statistics |
clear ipc
Use the clear ipc privileged EXEC command to clear Interprocess Communications Protocol (IPC) statistics.
clear ipc { queue-statistics | statistics }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You can clear all statistics by using the clear ipc statistics command, or you can clear only the queue statistics by using the clear ipc queue-statistics command.
Examples
This example shows how to clear all statistics:
Switch# clear ipc statistics
This example shows how to clear only the queue statistics:
Switch# clear ipc queue-statistics
You can verify that the statistics were deleted by entering the show ipc rpc or the show ipc session privileged EXEC command.
Related Commands
|
|
|
|---|---|
show ipc { rpc | session } |
clear ipv6 dhcp conflict
Use the clear ipv6 dhcp conflict privileged EXEC command to clear an address conflict from the Dynamic Host Configuration Protocol for IPv6 (DHCPv6) server database.
clear ipv6 dhcp conflict {* | IPv6-address}
Note This command is available only if you have configured a dual IPv4 and IPv6 Switch Database Management (SDM) template on the switch.
Syntax Description
Clear the host IPv6 address that contains the conflicting address. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
To configure the dual IPv4 and IPv6 template, enter the sdm prefer dual-ipv4-and-ipv6 { default | vlan } global configuration command, and reload the switch.
When you configure the DHCPv6 server to detect conflicts, it uses ping. The client uses neighbor discovery to detect clients and reports to the server through a DECLINE message. If an address conflict is detected, the address is removed from the pool, and the address is not assigned until the administrator removes the address from the conflict list.
If you use the asterisk (*) character as the address parameter, DHCP clears all conflicts.
Examples
This example shows how to clear all address conflicts from the DHCPv6 server database:
Related Commands
|
|
|
|---|---|
Displays address conflicts found by a DHCPv6 server, or reported through a DECLINE message from a client. |
clear l2protocol-tunnel counters
Use the clear l2protocol-tunnel counters privileged EXEC command to clear the protocol counters in protocol tunnel ports.
clear l2protocol-tunnel counters [ interface-id ]
Syntax Description
(Optional) Specify interface (physical interface or port channel) for which protocol counters are to be cleared. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use this command to clear protocol tunnel counters on the switch or on the specified interface.
Examples
This example shows how to clear Layer 2 protocol tunnel counters on an interface:
Switch# clear l2protocol-tunnel counters gigabitethernet1/0/3
Related Commands
|
|
|
|---|---|
Displays information about ports configured for Layer 2 protocol tunneling. |
clear lacp
Use the clear lacp privileged EXEC command to clear Link Aggregation Control Protocol (LACP) channel-group counters.
clear lacp { channel-group-number counters | counters }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
The channel -group-number range was changed from 1 to 12 to 1 to 48. |
Usage Guidelines
You can clear all counters by using the clear lacp counters command, or you can clear only the counters for the specified channel group by using the clear lacp channel-group-number counters command.
Examples
This example shows how to clear all channel-group information:
Switch# clear lacp counters
This example shows how to clear LACP traffic counters for group 4:
Switch# clear lacp 4 counters
You can verify that the information was deleted by entering the show lacp counters or the show lacp 4 counters privileged EXEC command.
Related Commands
|
|
|
|---|---|
clear mac address-table
Use the clear mac address-table privileged EXEC command to delete from the MAC address table a specific dynamic address, all dynamic addresses on a particular interface, all dynamic addresses on stack members, or all dynamic addresses on a particular VLAN. This command also clears the MAC address notification global counters.
clear mac address-table { dynamic [ address mac-addr | interface interface-id | vlan vlan-id ] | notification }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
The clear mac-address-table command (with the hyphen) was replaced by the clear mac address-table command (without the hyphen). |
Examples
This example shows how to remove a specific MAC address from the dynamic address table:
You can verify that the information was deleted by entering the show mac address-table privileged EXEC command.
Related Commands
clear mac address-table move update
Use the clear mac address-table move update privileged EXEC command to clear the mac address-table-move update-related counters.
clear mac address-table move update
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to clear the mac address-table move update related counters.
You can verify that the information was cleared by entering the show mac address-table move update privileged EXEC command.
Related Commands
|
|
|
|---|---|
Displays the MAC address-table move update information on the switch. |
clear nmsp statistics
Use the clear nmsp statistics privileged EXEC command to clear the Network Mobility Services Protocol (NMSP) statistics. This command is available only when your switch is running the cryptographic (encrypted) software image.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to clear NMSP statistics:
You can verify that information was deleted by entering the show nmsp statistics privileged EXEC command.
Related Commands
|
|
|
|---|---|
clear pagp
Use the clear pagp privileged EXEC command to clear Port Aggregation Protocol (PAgP) channel-group information.
clear pagp { channel-group-number counters | counters }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
The channel -group-number range was changed from 1 to 12 to 1 to 48. |
Usage Guidelines
You can clear all counters by using the clear pagp counters command, or you can clear only the counters for the specified channel group by using the clear pagp channel-group-number counters command.
Examples
This example shows how to clear all channel-group information:
Switch# clear pagp counters
This example shows how to clear PAgP traffic counters for group 10:
Switch# clear pagp 10 counters
You can verify that information was deleted by entering the show pagp privileged EXEC command.
Related Commands
|
|
|
|---|---|
clear port-security
Use the clear port-security privileged EXEC command to delete from the MAC address table all secure addresses or all secure addresses of a specific type (configured, dynamic, or sticky) on the switch or on an interface.
clear port-security { all | configured | dynamic | sticky } [[ address mac-addr | interface interface-id ] [ vlan { vlan-id | { access | voice}}]]
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to clear all secure addresses from the MAC address table:
This example shows how to remove a specific configured secure address from the MAC address table:
This example shows how to remove all the dynamic secure addresses learned on a specific interface:
This example shows how to remove all the dynamic secure addresses from the address table:
You can verify that the information was deleted by entering the show port-security privileged EXEC command.
Related Commands
|
|
|
|---|---|
switchport port-security mac-address mac-address |
|
switchport port-security maximum value |
Configures a maximum number of secure MAC addresses on a secure interface. |
Displays the port security settings defined for an interface or for the switch. |
clear spanning-tree counters
Use the clear spanning-tree counters privileged EXEC command to clear the spanning-tree counters.
clear spanning-tree counters [ interface interface-id ]
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
If the interface-id is not specified, spanning-tree counters are cleared for all interfaces.
Examples
This example shows how to clear spanning-tree counters for all interfaces:
Related Commands
|
|
|
|---|---|
clear spanning-tree detected-protocols
Use the clear spanning-tree detected-protocols privileged EXEC command to restart the protocol migration process (force the renegotiation with neighboring switches) on all interfaces or on the specified interface.
clear spanning-tree detected-protocols [ interface interface-id ]
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
A switch running the rapid per-VLAN spanning-tree plus (rapid-PVST+) protocol or the Multiple Spanning Tree Protocol (MSTP) supports a built-in protocol migration mechanism that enables it to interoperate with legacy IEEE 802.1D switches. If a rapid-PVST+ switch or an MSTP switch receives a legacy IEEE 802.1D configuration bridge protocol data unit (BPDU) with the protocol version set to 0, it sends only IEEE 802.1D BPDUs on that port. A multiple spanning-tree (MST) switch can also detect that a port is at the boundary of a region when it receives a legacy BPDU, an MST BPDU (Version 3) associated with a different region, or a rapid spanning-tree (RST) BPDU (Version 2).
However, the switch does not automatically revert to the rapid-PVST+ or the MSTP mode if it no longer receives IEEE 802.1D BPDUs because it cannot learn whether the legacy switch has been removed from the link unless the legacy switch is the designated switch. Use the clear spanning-tree detected-protocols command in this situation.
Examples
This example shows how to restart the protocol migration process on a port:
Related Commands
|
|
|
|---|---|
Overrides the default link-type setting and enables rapid spanning-tree changes to the forwarding state. |
clear vmps statistics
Use the clear vmps statistics privileged EXEC command to clear the statistics maintained by the VLAN Query Protocol (VQP) client.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to clear VLAN Membership Policy Server (VMPS) statistics:
You can verify that information was deleted by entering the show vmps statistics privileged EXEC command.
Related Commands
|
|
|
|---|---|
Displays the VQP version, reconfirmation interval, retry count, VMPS IP addresses, and the current and primary servers. |
clear vtp counters
Use the clear vtp counters privileged EXEC command to clear the VLAN Trunking Protocol (VTP) and pruning counters.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to clear the VTP counters:
You can verify that information was deleted by entering the show vtp counters privileged EXEC command.
Related Commands
|
|
|
|---|---|
Displays general information about the VTP management domain, status, and counters. |
cluster commander-address
You do not need to enter this command from a standalone cluster member switch. The cluster command switch automatically provides its MAC address to cluster member switches when these switches join the cluster. The cluster member switch adds this information and other cluster information to its running configuration file. Use the no form of this global configuration command from the cluster member switch console port to remove the switch from a cluster only during debugging or recovery procedures.
cluster commander-address mac-address [ member number name name ]
Syntax Description
(Optional) Number of a configured cluster member switch. The range is 0 to 15. |
|
(Optional) Name of the configured cluster up to 31 characters. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
This command is available only on the cluster command switch.
A cluster member can have only one cluster command switch.
The cluster member switch retains the identity of the cluster command switch during a system reload by using the mac-address parameter.
You can enter the no form on a cluster member switch to remove it from the cluster during debugging or recovery procedures. You would normally use this command from the cluster member switch console port only when the member has lost communication with the cluster command switch. With normal switch configuration, we recommend that you remove cluster member switches only by entering the no cluster member n global configuration command on the cluster command switch.
When a standby cluster command switch becomes active (becomes the cluster command switch), it removes the cluster commander address line from its configuration.
Examples
This is partial sample output from the running configuration of a cluster member.
This example shows how to remove a member from the cluster by using the cluster member console.
You can verify your settings by entering the show cluster privileged EXEC command.
Related Commands
|
|
|
|---|---|
Displays the cluster status and a summary of the cluster to which the switch belongs. |
cluster discovery hop-count
Use the cluster discovery hop-count global configuration command on the cluster command switch to set the hop-count limit for extended discovery of candidate switches. Use the no form of this command to return to the default setting.
cluster discovery hop-count number
no cluster discovery hop-count
Syntax Description
Number of hops from the cluster edge that the cluster command switch limits the discovery of candidates. The range is 1 to 7. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
This command is available only on the cluster command switch. This command does not operate on cluster member switches.
If the hop count is set to 1, it disables extended discovery. The cluster command switch discovers only candidates that are one hop from the edge of the cluster. The edge of the cluster is the point between the last discovered cluster member switch and the first discovered candidate switch.
Examples
This example shows how to set hop count limit to 4. This command is executed on the cluster command switch.
You can verify your setting by entering the show cluster privileged EXEC command.
Related Commands
|
|
|
|---|---|
Displays the cluster status and a summary of the cluster to which the switch belongs. |
|
cluster enable
Use the cluster enable global configuration command on a command-capable switch to enable it as the cluster command switch, assign a cluster name, and to optionally assign a member number to it. Use the no form of the command to remove all members and to make the cluster command switch a candidate switch.
cluster enable name [ command-switch-member-number ]
Syntax Description
Defaults
The switch is not a cluster command switch.
The member number is 0 when the switch is the cluster command switch.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Enter this command on any command-capable switch that is not part of any cluster. This command fails if a device is already configured as a member of the cluster.
You must name the cluster when you enable the cluster command switch. If the switch is already configured as the cluster command switch, this command changes the cluster name if it is different from the previous cluster name.
Examples
This example shows how to enable the cluster command switch, name the cluster, and set the cluster command switch member number to 4.
You can verify your setting by entering the show cluster privileged EXEC command on the cluster command switch.
Related Commands
|
|
|
|---|---|
Displays the cluster status and a summary of the cluster to which the switch belongs. |
cluster holdtime
Use the cluster holdtime global configuration command on the cluster command switch to set the duration in seconds before a switch (either the command or cluster member switch) declares the other switch down after not receiving heartbeat messages. Use the no form of this command to set the duration to the default value.
cluster holdtime holdtime-in-secs
Syntax Description
Duration in seconds before a switch (either a command or cluster member switch) declares the other switch down. The range is 1 to 300 seconds. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Enter this command with the cluster timer global configuration command only on the cluster command switch. The cluster command switch propagates the values to all its cluster members so that the setting is consistent among all switches in the cluster.
The holdtime is typically set as a multiple of the interval timer (cluster timer). For example, it takes (holdtime-in-secs divided by the interval-in-secs) number of heartbeat messages to be missed in a row to declare a switch down.
Examples
This example shows how to change the interval timer and the duration on the cluster command switch.
You can verify your settings by entering the show cluster privileged EXEC command.
Related Commands
|
|
|
|---|---|
Displays the cluster status and a summary of the cluster to which the switch belongs. |
cluster member
Use the cluster member global configuration command on the cluster command switch to add candidates to a cluster. Use the no form of the command to remove members from the cluster.
cluster member [ n ] mac-address H.H.H [ password enable-password ] [ vlan vlan-id ]
Syntax Description
Defaults
A newly enabled cluster command switch has no associated cluster members.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Enter this command only on the cluster command switch to add a candidate to or remove a member from the cluster. If you enter this command on a switch other than the cluster command switch, the switch rejects the command and displays an error message.
You must enter a member number to remove a switch from the cluster. However, you do not need to enter a member number to add a switch to the cluster. The cluster command switch selects the next available member number and assigns it to the switch that is joining the cluster.
You must enter the enable password of the candidate switch for authentication when it joins the cluster. The password is not saved in the running or startup configuration. After a candidate switch becomes a member of the cluster, its password becomes the same as the cluster command-switch password.
If a switch does not have a configured hostname, the cluster command switch appends a member number to the cluster command-switch hostname and assigns it to the cluster member switch.
If you do not specify a VLAN ID, the cluster command switch automatically chooses a VLAN and adds the candidate to the cluster.
Examples
This example shows how to add a switch as member 2 with MAC address 00E0.1E00.2222 and the password key to a cluster. The cluster command switch adds the candidate to the cluster through VLAN 3.
This example shows how to add a switch with MAC address 00E0.1E00.3333 to the cluster. This switch does not have a password. The cluster command switch selects the next available member number and assigns it to the switch that is joining the cluster.
You can verify your settings by entering the show cluster members privileged EXEC command on the cluster command switch.
Related Commands
|
|
|
|---|---|
Displays the cluster status and a summary of the cluster to which the switch belongs. |
|
cluster outside-interface
Use the cluster outside-interface global configuration command on the cluster command switch to configure the outside interface for cluster Network Address Translation (NAT) so that a member without an IP address can communicate with devices outside the cluster. Use the no form of this command to return to the default setting.
cluster outside-interface interface-id
Syntax Description
Interface to serve as the outside interface. Valid interfaces include physical interfaces, port-channels, or VLANs. The port-channel range is 1 to 48. The VLAN range is 1 to 4094. |
Defaults
The default outside interface is automatically selected by the cluster command switch.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Enter this command only on the cluster command switch. If you enter this command on a cluster member switch, an error message appears.
Examples
This example shows how to set the outside interface to VLAN 1:
You can verify your setting by entering the show running-config privileged EXEC command.
Related Commands
|
|
|
|---|---|
cluster run
Use the cluster run global configuration command to enable clustering on a switch. Use the no form of this command to disable clustering on a switch.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
When you enter the no cluster run command on a cluster command switch, the cluster command switch is disabled. Clustering is disabled, and the switch cannot become a candidate switch.
When you enter the no cluster run command on a cluster member switch, it is removed from the cluster. Clustering is disabled, and the switch cannot become a candidate switch.
When you enter the no cluster run command on a switch that is not part of a cluster, clustering is disabled on this switch. This switch cannot then become a candidate switch.
Examples
This example shows how to disable clustering on the cluster command switch:
You can verify your setting by entering the show cluster privileged EXEC command.
Related Commands
|
|
|
|---|---|
Displays the cluster status and a summary of the cluster to which the switch belongs. |
cluster standby-group
Use the cluster standby-group global configuration command to enable cluster command-switch redundancy by binding the cluster to an existing Hot Standby Router Protocol (HSRP). Entering the routing-redundancy keyword enables the same HSRP group to be used for cluster command-switch redundancy and routing redundancy. Use the no form of this command to return to the default setting.
cluster standby-grou p HSRP-group-name [ routing-redundancy ]
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Enter this command only on the cluster command switch. If you enter it on a cluster member switch, an error message appears.
The cluster command switch propagates the cluster-HSRP binding information to all cluster-HSRP capable members. Each cluster member switch stores the binding information in its NVRAM. The HSRP group name must be a valid standby group; otherwise, the command exits with an error.
The same group name should be used on all members of the HSRP standby group that is to be bound to the cluster. The same HSRP group name should also be used on all cluster-HSRP capable members for the HSRP group that is to be bound. (When not binding a cluster to an HSRP group, you can use different names on the cluster commander and the members.)
Examples
This example shows how to bind the HSRP group named my_hsrp to the cluster. This command is executed on the cluster command switch.
This example shows how to use the same HSRP group named my_hsrp for routing redundancy and cluster redundancy.
This example shows the error message when this command is executed on a cluster command switch and the specified HSRP standby group does not exist:
This example shows the error message when this command is executed on a cluster member switch:
You can verify your settings by entering the show cluster privileged EXEC command. The output shows whether redundancy is enabled in the cluster.
Related Commands
|
|
|
|---|---|
Displays the cluster status and a summary of the cluster to which the switch belongs. |
|
cluster timer
Use the cluster timer global configuration command on the cluster command switch to set the interval in seconds between heartbeat messages. Use the no form of this command to set the interval to the default value.
cluster timer interval-in-secs
Syntax Description
Interval in seconds between heartbeat messages. The range is 1 to 300 seconds. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Enter this command with the cluster holdtime global configuration command only on the cluster command switch. The cluster command switch propagates the values to all its cluster members so that the setting is consistent among all switches in the cluster.
The holdtime is typically set as a multiple of the heartbeat interval timer (cluster timer). For example, it takes (holdtime-in-secs divided by the interval-in-secs) number of heartbeat messages to be missed in a row to declare a switch down.
Examples
This example shows how to change the heartbeat interval timer and the duration on the cluster command switch:
You can verify your settings by entering the show cluster privileged EXEC command.
Related Commands
|
|
|
|---|---|
Displays the cluster status and a summary of the cluster to which the switch belongs. |
define interface-range
Use the define interface-range global configuration command to create an interface-range macro. Use the no form of this command to delete the defined macro.
define interface-range macro-name interface-range
no define interface-range macro-name interface-range
Syntax Description
Interface range; for valid values for interface ranges, see “Usage Guidelines.” |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The macro name is a 32-character maximum character string.
A macro can contain up to five ranges.
All interfaces in a range must be the same type; that is, all Fast Ethernet ports, all Gigabit Ethernet ports, all EtherChannel ports, or all VLANs, but you can combine multiple interface types in a macro.
When entering the interface-range, use this format:
- type { first-interface } - { last-interface }
- You must add a space between the first interface number and the hyphen when entering an interface-range. For example, gigabitethernet 1/0/1 - 2 is a valid range; gigabit ethernet 1/0/1 -2 is not a valid range.
Valid values for type and interface :
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 in interface-ranges.
- port-channel port-channel-number, where port-channel-number is from 1 to 48
- fastethernet stack member/module/{ first port } - { last port }
- gigabitethernet stack member/module/{ first port } - { last port }
- stack member is the number used to identify the switch within the stack. The number ranges from 1 to 9 and is assigned to the switch the first time the stack member initializes.
- module is always 0.
- the range is type stack member /0/number - number (for example, gigabitethernet 1/0/1/1 - 2).
When you define a range, you must enter a space before the hyphen (-), for example:
You can also enter multiple ranges. When you define multiple ranges, you must enter a space after the first entry before the comma (,). The space after the comma is optional, for example:
Examples
This example shows how to create a multiple-interface macro:
Related Commands
delete
Use the delete privileged EXEC command to delete a file or directory on the flash memory device.
delete [ /force ] [/ recursive ] filesystem :/ file-url
Syntax Description
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
If you use the /force keyword, you are prompted once at the beginning of the deletion process to confirm the deletion.
If you use the /recursive keyword without the /force keyword, you are prompted to confirm the deletion of every file.
The prompting behavior depends on the setting of the file prompt global configuration command. By default, the switch prompts for confirmation on destructive file operations. For more information about this command, see the Cisco IOS Command Reference for Release 12.1.
Examples
This example shows how to remove the directory that contains the old software image after a successful download of a new image:
You can verify that the directory was removed by entering the dir filesystem : privileged EXEC command.
Related Commands
|
|
|
|---|---|
Downloads a new image to the switch and overwrites or keeps the existing image. |
deny (ARP access-list configuration)
Use the deny Address Resolution Protocol (ARP) access-list configuration command to deny an ARP packet based on matches against the DHCP bindings. Use the no form of this command to remove the specified access control entry (ACE) from the access list.
deny {[ request ] ip { any | host sender-ip | sender-ip sender-ip-mask } mac { any | host sender-mac | sender-mac sender-mac-mask } | response ip { any | host sender-ip | sender-ip sender-ip-mask } [{ any | host target-ip | target-ip target-ip-mask }] mac { any | host sender-mac | sender-mac sender-mac-mask } [{ any | host target-mac | target-mac target-mac-mask }]} [ log ]
no deny {[ request ] ip { any | host sender-ip | sender-ip sender-ip-mask } mac { any | host sender-mac | sender-mac sender-mac-mask } | response ip { any | host sender-ip | sender-ip sender-ip-mask } [{ any | host target-ip | target-ip target-ip-mask }] mac { any | host sender-mac | sender-mac sender-mac-mask } [{ any | host target-mac | target-mac target-mac-mask }]} [ log ]
Syntax Description
(Optional) Define a match for the ARP request. When request is not specified, matching is performed against all ARP packets. |
|
Defaults
There are no default settings. However, at the end of the ARP access list, there is an implicit deny ip any mac any command.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You can add deny clauses to drop ARP packets based on matching criteria.
Examples
This example shows how to define an ARP access list and to deny both ARP requests and ARP responses from a host with an IP address of 1.1.1.1 and a MAC address of 0000.0000.abcd:
You can verify your settings by entering the show arp access-list privileged EXEC command.
Related Commands
|
|
|
|---|---|
Permits ARP requests and responses from a host configured with a static IP address. |
|
Permits an ARP packet based on matches against the DHCP bindings. |
|
deny (IPv6 access-list configuration)
Use the deny command in IPv6 access list configuration mode to set deny conditions for an IPv6 access list. Use the no form of this command to remove the deny conditions.
deny { protocol } { source-ipv6-prefix / prefix-length | any | host source-ipv6-address } [ operator [ port-number ]] { destination-ipv6-prefix/prefix-length | any | host destination-ipv6-address } [ operator [ port-number ]] [ dscp value ] [ fragments ] [ log ] [ log-input ] [ sequence value ] [ time-range name ]
no deny { protocol } { source-ipv6-prefix / prefix-length | any | host source-ipv6-address } [ operator [ port-number ]] { destination-ipv6-prefix/prefix-length | any | host destination-ipv6-address } [ operator [ port-number ]] [ dscp value ] [ fragments ] [ log ] [ log-input ] [ sequence value ] [ time-range name ]
Internet Control Message Protocol
deny icmp { source-ipv6-prefix / prefix-length | any | host source-ipv6-address } [ operator [ port-number ]] { destination-ipv6-prefix/prefix-length | any | host destination-ipv6-address } [ operator [ port-number ]] [ icmp-type [ icmp-code ] | icmp-message ] [ dscp value ] [ log ] [ log-input ] [ sequence value ] [ time-range name ]
deny tcp { source-ipv6-prefix / prefix-length | any | host source-ipv6-address } [ operator [ port-number ]] { destination-ipv6-prefix/prefix-length | any | host destination-ipv6-address } [ operator [ port-number ]] [ ack ] [ dscp value ] [ established ] [ fin ] [ log ] [ log-input ] [ neq { port | protocol }] [ psh ] [ range { port | protocol }] [ rst ] [ sequence value ] [ syn ] [ time-range name ] [ urg ]
deny udp { source-ipv6-prefix / prefix-length | any | host source-ipv6-address } [ operator [ port-number ]] { destination-ipv6-prefix/prefix-length | any | host destination-ipv6-address } [ operator [ port-number ]] [ dscp value ] [ log ] [ log-input ] [ neq { port | protocol }] [ range { port | protocol }] [ sequence value ] [ time-range name ]
Note This command is available only if you have configured a dual IPv4 and IPv6 Switch Database Management (SDM) template on the switch stack.
Syntax Description
Note Although visible in the command-line help strings, the flow-label, routing, and undetermined-transport keywords are not supported.
Defaults
Command Modes
IPv6 access list configuration
Command History
|
|
|
|---|---|
Usage Guidelines
The deny (IPv6 access-list configuration mode) command is similar to the deny (IPv4 access-list configuration mode) command, except that it is IPv6-specific.
Use the deny (IPv6) command after the ipv6 access-list command to enter IPv6 access list configuration mode and to define the conditions under which a packet passes the access list.
Specifying IPv6 for the protocol argument matches against the IPv6 header of the packet.
By default, the first statement in an access list is number 10, and the subsequent statements are numbered in increments of 10.
You can add permit, deny, or remark statements to an existing access list without re-entering the entire list. To add a new statement anywhere other than at the end of the list, create a new statement with an appropriate entry number that falls between two existing entry numbers to show where it belongs.
Note Every IPv6 ACL has implicit permit icmp any any nd-na, permit icmp any any nd-ns, and deny ipv6 any any statements as its last match conditions. The two permit conditions allow ICMPv6 neighbor discovery. To disallow ICMPv6 neighbor discovery and to deny icmp any any nd-na or icmp any any nd-ns, there must be an explicit deny entry in the ACL. For the implicit deny ipv6 any any statement to take effect, an IPv6 ACL must contain at least one entry.
The IPv6 neighbor discovery process uses the IPv6 network layer service. Therefore, by default, IPv6 ACLs implicitly allow IPv6 neighbor discovery packets to be sent and received on an interface. In IPv4, the Address Resolution Protocol (ARP), which is equivalent to the IPv6 neighbor discovery process, uses a separate data-link layer protocol. Therefore, by default, IPv4 ACLs implicitly allow ARP packets to be sent and received on an interface.
Both the source-ipv6-prefix / prefix-length and destination-ipv6-prefix / prefix-length arguments are used for traffic filtering. (The source prefix filters traffic based upon the traffic source; the destination prefix filters traffic based upon the traffic destination.)
The switch supports only prefixes from /0 to /64 and EUI-based /128 prefixes for aggregatable global unicast and link-local host addresses.
The fragments keyword is an option only if the protocol is ipv6 and the operator [ port-number ] arguments are not specified.
This is a list of ICMP message names:
Examples
This example configures the IPv6 access list named CISCO and applies the access list to outbound traffic on a Layer 3 interface. The first deny entry in the list prevents all packets that have a destination TCP port number greater than 5000 from leaving the interface. The second deny entry in the list prevents all packets that have a source UDP port number less than 5000 from leaving the interface. The second deny also logs all matches to the console. The first permit entry in the list permits all ICMP packets to leave the interface. The second permit entry in the list permits all other traffic to leave the interface. The second permit entry is necessary because an implicit deny-all condition is at the end of each IPv6 access list.
Related Commands
|
|
|
|---|---|
Defines an IPv6 access list and enters IPv6 access list configuration mode. |
|
deny (MAC access-list configuration)
Use the deny MAC access-list configuration command to prevent non-IP traffic from being forwarded if the conditions are matched. Use the no form of this command to remove a deny condition from the named MAC access list.
{ deny | permit } { any | host src-MAC-addr | src-MAC-addr mask } { any | host dst-MAC-addr | dst-MAC-addr mask } [ type mask | aarp | amber | cos cos | dec-spanning | decnet-iv | diagnostic | dsm | etype-6000 | etype-8042 | lat | lavc-sca | lsap lsap mask |mop-console | mop-dump | msdos | mumps | netbios | vines-echo | vines-ip | xns-idp ]
no { deny | permit } { any | host src-MAC-addr | src-MAC-addr mask } { any | host dst-MAC-addr | dst-MAC-addr mask } [ type mask | aarp | amber | cos cos | dec-spanning | decnet-iv | diagnostic | dsm | etype-6000 | etype-8042 | lat | lavc-sca | lsap lsap mask | mop-console | mop-dump | msdos | mumps | netbios | vines-echo | vines-ip | xns-idp ]
Syntax Description
Note Though visible in the command-line help strings, appletalk is not supported as a matching condition.
To filter IPX traffic, you use the type mask or lsap lsap mask keywords, depending on the type of IPX encapsulation being used. Filter criteria for IPX encapsulation types as specified in Novell terminology and Cisco IOS terminology are listed in Table 1-9 .
|
|
|
|
|---|---|---|
|
|
|
|
Defaults
This command has no defaults. However; the default action for a MAC-named ACL is to deny.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You enter MAC-access list configuration mode by using the mac access-list extended global configuration command.
If you use the host keyword, you cannot enter an address mask; if you do not use the host keyword, you must enter an address mask.
When an access control entry (ACE) is added to an access control list, an implied deny - any - any condition exists at the end of the list. That is, if there are no matches, the packets are denied. However, before the first ACE is added, the list permits all packets.
For more information about named MAC extended access lists, see the software configuration guide for this release.
Examples
This example shows how to define the named MAC extended access list to deny NETBIOS traffic from any source to MAC address 00c0.00a0.03fa. Traffic matching this list is denied.
This example shows how to remove the deny condition from the named MAC extended access list:
This example denies all packets with Ethertype 0x4321:
You can verify your settings by entering the show access-lists privileged EXEC command.
Related Commands
|
|
|
|---|---|
Creates an access list based on MAC addresses for non-IP traffic. |
|
Permits non-IP traffic to be forwarded if conditions are matched. |
|
diagnostic monitor
Use the diagnostic monitor global configuration command to configure the health-monitoring diagnostic testing. Use the no form of this command to disable testing and return to the default settings.
diagnostic monitor switch { num } test { test-id | test-id-range | all }
diagnostic monitor interval switch { num } test { test-id | test-id-range | all } hh:mm:ss milliseconds day
diagnostic monitor threshold switch { num } test { test-id | test-id-range | all } count failure count
no diagnostic monitor switch { num } test { test-id | test-id-range | all }
no diagnostic monitor interval switch { num } test { test-id | test-id-range | all }
no diagnostic monitor threshold switch { num } test { test-id | test-id-range | all } failure coun t
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use these guidelines when scheduling testing:
- test-id — Enter the show diagnostic content privileged EXEC command to display the test ID list.
- test-id-range — Enter the show diagnostic content command to display the test ID list. Enter the range as integers separated by a comma and a hyphen (for example, 1,3-6 specifies test IDs 1, 3, 4, 5, and 6).
- hh— Enter the hours from 0 to 23.
- mm— Enter the minutes from 0 to 60.
- ss— Enter the seconds from 0 to 60.
- milliseconds— Enter the milliseconds from 0 to 999.
- day— Enter the day as a number from 0 to 20.
When entering the diagnostic monitor switch { num } test { test-id | test-id-range | all } command, follow these required guidelines
- Isolate network traffic by disabling all connected ports, and do not pump test packets during the test.
- Reset the system or the test module before putting the system back into the normal operating mode.
Note If you are running a diagnostic test that has the reload attribute on a switch in a stack, you could potentially partition the stack depending on your cabling configuration. To avoid partitioning your stack, you should enter the show switch detail privileged EXEC command to verify the stack configuration.
Examples
This example shows how to configure the specified test to run every 2 minutes:
Switch(config)# diagnostic monitor interval switch 1 test 1 00:02:00 0 1
This example shows how to run the test on the specified switch if health monitoring has not previously been enabled:
Switch(config)# diagnostic monitor switch 1 test 1
This example shows how to set the failure threshold for test monitoring on a switch:
Switch(config)# diagnostic monitor threshold switch 1 test 1 failure count 50
This example shows how to enable generating a syslog message when any health monitoring test fails:
Switch(config)# diagnostic monitor syslog
Related Commands
|
|
|
|---|---|
diagnostic schedule
Use the diagnostic schedule privileged EXEC command to configure the scheduling of diagnostic testing. Use the no form of this command to remove the scheduling and return to the default setting.
diagnostic schedule switch num test { test-id | test-id-range | all | basic | non-disruptive } { daily hh : mm | on mm dd yyyy hh : mm | weekly day-of-week hh : mm }
no diagnostic schedule switch num test { test-id | test-id-range | all | basic | non-disruptive } { daily hh : mm | on mm dd yyyy hh : mm | weekly day-of-week hh : mm }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use these guidelines when scheduling testing:
- test-id — Enter the show diagnostic content command to display the test ID list.
- test-id-range — Enter the show diagnostic content command to display the test ID list. Enter the range as integers separated by a comma and a hyphen (for example, 1,3-6 specifies test IDs 1, 3, 4, 5, and 6).
- hh : mm— Enter the time as a 2-digit number (for a 24-hour clock) for hours:minutes; the colon ( : ) is required.
- mm— Spell out the month, such as January, February... December (either upper case or lower case characters).
- dd— Enter the day as a 2-digit number.
- yyyy— Enter the year as a 4-digit number.
- day-of-week— Spell out the day of the week, such as Monday, Tuesday... Sunday (either upper case or lower case characters).
Examples
This example shows how to schedule diagnostic testing on a specific date and time for a specific switch:
This example shows how to schedule diagnostic testing to occur weekly at a certain time for a specific switch:
Related Commands
|
|
|
|---|---|
diagnostic start
Use the diagnostic start user command to run the specified diagnostic test.
diagnostic start switch num test { test-id | test-id-range | all | basic | non-disruptive }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Enter the show diagnostic content command to display the test ID list.
Enter the test-id-range as integers separated by a comma and a hyphen (for example, 1,3-6 specifies test IDs 1, 3, 4, 5, and 6).
Examples
This example shows how to start a diagnostic test on a specific switch:
This example shows how to start diagnostics test 2 on a switch that will disrupt normal system operation:
This message appears if the test can cause the switch to lose stack connectivity:
This message appears if the test will cause a stack partition:
Related Commands
|
|
|
|---|---|
dot1x
Use the dot1x global configuration command to globally enable IEEE 802.1x authentication. Use the no form of this command to return to the default setting.
dot1x { critical { eapol | recovery delay milliseconds } | { guest-vlan supplicant } | system-auth-control }
no dot1x { critical { eapol | recovery delay } | { guest-vlan supplicant } | system-auth-control }
Note Though visible in the command-line help strings, the credentials name keywords are not supported.
Syntax Description
Configure the inaccessible authentication bypass parameters. For more information, see the dot1x critical (global configuration) command. |
|
Defaults
IEEE 802.1x authentication is disabled, and the optional guest VLAN behavior is disabled.
Command Modes
Command History
|
|
|
|---|---|
The critical { eapol | recovery delay milliseconds } keywords were added. |
Usage Guidelines
You must enable authentication, authorization, and accounting (AAA) and specify the authentication method list before globally enabling IEEE 802.1x authentication. A method list describes the sequence and authentication methods to be used to authenticate a user.
Before globally enabling IEEE 802.1x authentication on a switch, remove the EtherChannel configuration from the interfaces on which IEEE 802.1x authentication and EtherChannel are configured.
If you are using a device running the Cisco Access Control Server (ACS) application for IEEE 802.1x authentication with EAP-Transparent LAN Services (TLS) and with EAP-MD5 and your switch is running Cisco IOS Release 12.1(14)EA1, make sure that the device is running ACS Version 3.2.1 or later.
You can use the guest-vlan supplicant keywords to enable the optional IEEE 802.1x guest VLAN behavior globally on the switch. For more information, see the dot1x guest-vlan command.
Examples
This example shows how to globally enable IEEE 802.1x authentication on a switch:
This example shows how to globally enable the optional guest VLAN behavior on a switch:
You can verify your settings by entering the show dot1x [ interface interface-id ] privileged EXEC command.
Related Commands
|
|
|
|---|---|
Configures the parameters for the inaccessible authentication bypass feature on the switch. |
|
Enables and specifies an active VLAN as an IEEE 802.1x guest VLAN. |
|
Enables manual control of the authorization state of the port. |
|
show dot1x [ interface interface-id ] |
dot1x auth-fail max-attempts
Use the dot1x auth-fail max-attempts interface configuration command to configure the maximum allowable authentication attempts before a port is moved to the restricted VLAN. To return to the default setting, use the no form of this command.
dot1x auth-fail max-attempts max-attempts
no dot1x auth-fail max-attempts
Syntax Description
Specify a maximum number of authentication attempts allowed before a port is moved to the restricted VLAN. The range is 1 to 3, the default value is 3. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
If you reconfigure the maximum number of authentication attempts allowed by the VLAN, the change takes effect after the re-authentication timer expires.
Examples
This example shows how to set 2 as the maximum number of authentication attempts allowed before the port is moved to the restricted VLAN on port 3:
You can verify your settings by entering the show dot1x [ interface interface-id ] privileged EXEC command.
Related Commands
|
|
|
|---|---|
dot1x auth-fail vlan [ vlan id] |
|
dot1x max-reauth-req [ count] |
Sets the maximum number of times that the switch restarts the authentication process before a port changes to the unauthorized state. |
show dot1x [ interface interface-id ] |
dot1x auth-fail vlan
Use the dot1x auth-fail vlan interface configuration command to enable the restricted VLAN on a port. To return to the default setting, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You can configure a restricted VLAN on ports configured as follows:
You should enable re-authentication. The ports in restricted VLANs do not receive re-authentication requests if it is disabled. To start the re-authentication process, the restricted VLAN must receive a link-down event or an Extensible Authentication Protocol (EAP) logoff event from the port. If a host is connected through a hub, the port might never receive a link-down event when that host is disconnected, and, as a result, might not detect any new hosts until the next re-authentication attempt occurs.
If the supplicant fails authentication, the port is moved to a restricted VLAN, and an EAP success message is sent to the supplicant. Because the supplicant is not notified of the actual authentication failure, there might be confusion about this restricted network access. An EAP success message is sent for these reasons:
- If the EAP success message is not sent, the supplicant tries to authenticate every 60 seconds (the default) by sending an EAP-start message.
- Some hosts (for example, devices running Windows XP) cannot implement DHCP until they receive an EAP success message.
A supplicant might cache an incorrect username and password combination after receiving an EAP success message from the authenticator and re-use that information in every re-authentication. Until the supplicant sends the correct username and password combination, the port remains in the restricted VLAN.
Internal VLANs used for Layer 3 ports cannot be configured as restricted VLANs.
You cannot configure a VLAN to be both a restricted VLAN and a voice VLAN. If you do this, a syslog message is generated.
When a restricted VLAN port is moved to an unauthorized state, the authentication process restarts. If the supplicant fails the authentication process again, the authenticator waits in the held state. After the supplicant has correctly re-authenticated, all IEEE 802.1x ports are reinitialized and treated as normal IEEE 802.1x ports.
When you reconfigure a restricted VLAN as a different VLAN, any ports in the restricted VLAN are also moved, and the ports stay in their currently authorized state.
When you shut down or remove a restricted VLAN from the VLAN database, any ports in the restricted VLAN are immediately moved to an unauthorized state, and the authentication process restarts. The authenticator does not wait in a held state because the restricted VLAN configuration still exists. While the restricted VLAN is inactive, all authentication attempts are counted so that when the restricted VLAN becomes active, the port is immediately placed in the restricted VLAN.
The restricted VLAN is supported only in single host mode (the default port mode). For this reason, when a port is placed in a restricted VLAN, the supplicant’s MAC address is added to the MAC address table, and any other MAC address that appears on the port is treated as a security violation.
Examples
This example shows how to configure a restricted VLAN on port 1:
You can verify your configuration by entering the show dot1x [ interface interface-id ] privileged EXEC command.
Related Commands
|
|
|
|---|---|
dot1x auth-fail max-attempts [ max-attempts] |
Configures the number of authentication attempts allowed before assigning a supplicant to the restricted VLAN. |
show dot1x [ interface interface-id ] |
dot1x control-direction
Use the dot1x control-direction interface configuration command to enable the IEEE 802.1x authentication with the wake-on-LAN (WoL) feature and to configure the port control as unidirectional or bidirectional. Use the no form of this command to return to the default setting.
dot1x control-direction { both | in }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the both keyword or the no form of this command to return to the default setting, bidirectional mode.
For more information about WoL, see the “Using IEEE 802.1x Authentication with Wake-on-LAN” section in the “Configuring IEEE 802.1x Port-Based Authentication” chapter in the software configuration guide.
Examples
This example shows how to enable unidirectional control:
This example shows how to enable bidirectional control:
You can verify your settings by entering the show dot1x all privileged EXEC command.
The show dot1x all privileged EXEC command output is the same for all switches except for the port names and the state of the port. If a host is attached to the port but is not yet authenticated, a display similar to this appears:
If you enter the dot1x control-direction in interface configuration command to enable unidirectional control, this appears in the show dot1x all command output:
If you enter the dot1x control-direction in interface configuration command and the port cannot support this mode due to a configuration conflict, this appears in the show dot1x all command output:
Related Commands
|
|
|
|---|---|
show dot1x [ all | interface interface-id ] |
Displays control-direction port setting status for the specified interface. |
dot1x credentials (global configuration)
Use the dot1x credentials global configuration command to configure a profile on a supplicant switch.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You must have another switch set up as the authenticator for this switch to be the supplicant.
Examples
This example shows how to configure a switch as a supplicant:
You can verify your settings by entering the show running-config privileged EXEC command.
Related Commands
|
|
|
|---|---|
dot1x critical (global configuration)
Use the dot1x critical global configuration command to configure the parameters for the inaccessible authentication bypass feature, also referred to as critical authentication or the authentication, authorization, and accounting (AAA) fail policy. To return to default settings, use the no form of this command.
dot1x critical { eapol | recovery delay milliseconds }
no dot1x critical { eapol | recovery delay }
Syntax Description
Defaults
The switch does not send an EAPOL-Success message to the host when the switch successfully authenticates the critical port by putting the critical port in the critical-authentication state.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the eapol keyword to specify that the switch sends an EAPOL-Success message when the switch puts the critical port in the critical-authentication state.
Use the recovery delay milliseconds keyword to 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 default recovery delay period is 1000 milliseconds. A port can be re-initialized every second.
To enable inaccessible authentication bypass on a port, use the dot1x critical interface configuration command. To configure the access VLAN to which the switch assigns a critical port, use the dot1x critical vlan vlan-id interface configuration command.
Examples
This example shows how to set 200 as the recovery delay period on the switch:
You can verify your configuration by entering the show dot1x privileged EXEC command.
Related Commands
|
|
|
|---|---|
Enables the inaccessible authentication bypass feature, and configures the access VLAN for the feature. |
|
dot1x critical (interface configuration)
Use the dot1x critical interface configuration command to enable the inaccessible-authentication-bypass feature, also referred to as critical authentication or the authentication, authorization, and accounting (AAA) fail policy. You can also configure the access VLAN to which the switch assigns the critical port when the port is in the critical-authentication state. To disable the feature or return to default, use the no form of this command.
dot1x critical [ recovery action reinitialize | vlan vlan-id ]
no dot1x critical [ recovery | vlan ]
Syntax Description
Defaults
The inaccessible-authentication-bypass feature is disabled.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
To specify the access VLAN to which the switch assigns a critical port when the port is in the critical-authentication state, use the vlan vlan-id keywords. The specified type of VLAN must match the type of port, as follows:
- If the critical port is an access port, the VLAN must be an access VLAN.
- If the critical port is a private VLAN host port, the VLAN must be a secondary private VLAN.
- If the critical port is a routed port, you can specify a VLAN, but this is optional.
If the client is running Windows XP and the critical 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 IEEE 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 it remains in the restricted VLAN.
You can configure the inaccessible bypass feature and port security on the same switch port.
Examples
This example shows how to enable the inaccessible authentication bypass feature on a port:
You can verify your configuration by entering the show dot1x [ interface interface-id ] privileged EXEC command.
Related Commands
|
|
|
|---|---|
Configures the parameters for the inaccessible authentication bypass feature on the switch. |
|
show dot1x [ interface interface-id ] |
dot1x default
Use the dot1x default interface configuration command to reset the IEEE 802.1x parameters to their default values.
Syntax Description
Defaults
- The per-port IEEE 802.1x protocol enable state is disabled (force-authorized).
- The number of seconds between re-authentication attempts is 3600 seconds.
- The periodic re-authentication is disabled.
- The quiet period is 60 seconds.
- The retransmission time is 30 seconds.
- The maximum retransmission number is 2 times.
- The host mode is single host.
- The client timeout period is 30 seconds.
- The authentication server timeout period is 30 seconds.
Command Modes
Command History
|
|
|
|---|---|
This command was changed to the interface configuration mode. |
Examples
This example shows how to reset the IEEE 802.1x parameters on a port:
You can verify your settings by entering the show dot1x [ interface interface-id ] privileged EXEC command.
Related Commands
|
|
|
|---|---|
show dot1x [ interface interface-id ] |
dot1x fallback
Use the dot1xfallback interface configuration command to configure a port to use web authentication as a fallback method for clients that do not support IEEE 802.1x authentication. To return to the default setting, use the no form of this command.
Syntax Description
Specify a fallback profile for clients that do not support IEEE 802.1x authentication. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You must enter the dot1x port-control auto interface configuration command on a switch port before entering this command.
Examples
This example shows how to specify a fallback profile to a switch port that has been configured for IEEE 802.1x authentication:
You can verify your settings by entering the show dot1x [ interface interface-id ] privileged EXEC command.
Related Commands
|
|
|
|---|---|
show dot1x [ interface interface-id ] |
|
dot1x guest-vlan
Use the dot1x guest-vlan interface configuration command to specify an active VLAN as an IEEE 802.1x guest VLAN. Use the no form of this command to return to the default setting.
Syntax Description
Specify an active VLAN as an IEEE 802.1x guest VLAN. The range is 1 to 4094. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command was modified to change the default guest VLAN behavior. |
Usage Guidelines
You can configure a guest VLAN on one of these switch ports:
- A static-access port that belongs to a nonprivate VLAN.
- A private-VLAN port that belongs to a secondary private VLAN. All the hosts connected to the switch port are assigned to private VLANs, whether or not the posture validation was successful. The switch determines the primary private VLAN by using the primary- and secondary-private-VLAN associations on the switch.
For each IEEE 802.1x port on the switch, you can configure a guest VLAN to provide limited services to clients (a device or workstation connected to the switch) not running IEEE 802.1x authentication. These users might be upgrading their systems for IEEE 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 IEEE 802.1x port, the switch assigns clients to a guest VLAN when it does not receive a response to its Extensible Authentication Protocol over LAN (EAPOL) request/identity frame or when EAPOL packets are not sent by the client.
The switch maintains the EAPOL packet history. If another EAPOL packet is detected on the interface during the lifetime of the link, the guest VLAN feature is disabled. If the port is already in the guest VLAN state, the port returns to the unauthorized state, and authentication restarts. The EAPOL history is reset upon loss of link.
Before Cisco IOS Release 12.2(25)SE, the switch did not maintain the EAPOL packet history and allowed clients that failed authentication access to the guest VLAN, regardless of whether EAPOL packets had been detected on the interface. In Cisco IOS Release 12.2(25)SE, you can use the dot1x guest-vlan supplicant global configuration command to enable this behavior.
However, in Cisco IOS Release 12.2(25)SEE, the dot1x guest-vlan supplicant global configuration command is no longer supported. You can use a restricted VLAN to allow clients that failed authentication access to the network by entering the dot1x auth-fail vlan vlan-id interface configuration command.
Any number of non-IEEE 802.1x-capable clients are allowed access when the switch port is moved to the guest VLAN. If an IEEE 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 RADIUS-configured or user-configured access VLAN, and authentication is restarted.
Guest VLANs are supported on IEEE 802.1x ports in single-host or multiple-hosts mode.
You can configure any active VLAN except an Remote Switched Port Analyzer (RSPAN) VLAN, a primary private VLAN, or a voice VLAN as an IEEE 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 IEEE 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 IEEE 802.1x authentication process (dot1x timeout quiet-period and dot1x timeout tx-period interface configuration commands). The amount to decrease the settings depends on the connected IEEE 802.1x client type.
The switch supports MAC authentication bypass. When it is enabled on an IEEE 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 IEEE 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 “Using IEEE 802.1x Authentication with MAC Authentication Bypass” section in the “Configuring IEEE 802.1x Port-Based Authentication” chapter of the software configuration guide.
Examples
This example shows how to specify VLAN 5 as an IEEE 802.1x guest VLAN:
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 resending the request, and to enable VLAN 2 as an IEEE 802.1x guest VLAN when an IEEE 802.1x port is connected to a DHCP client:
This example shows how to enable the optional guest VLAN behavior and to specify VLAN 5 as an IEEE 802.1x guest VLAN:
You can verify your settings by entering the show dot1x [ interface interface-id ] privileged EXEC command.
Related Commands
|
|
|
|---|---|
show dot1x [ interface interface-id ] |
dot1x host-mode
Use the dot1x host-mode interface configuration command to allow a single host (client) or multiple hosts on an IEEE 802.1x-authorized port. Use the multi-domain keyword to enable multidomain authentication (MDA) on an IEEE 802.1x-authorized port. Use the no form of this command to return to the default setting.
dot1x host-mode { multi-host | single-host | multi-domain }
no dot1x host-mode [ multi-host | single-host | multi-domain }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command was introduced. It replaces the dot1x multiple-hosts interface configuration command. |
|
Usage Guidelines
Use this command to limit an IEEE 802.1x-enabled port to a single client or to attach multiple clients to an IEEE 802.1x-enabled port. In multiple-hosts mode, only one of the attached hosts needs to be successfully authorized for all hosts to be granted network access. If the port becomes unauthorized (re-authentication fails or an Extensible Authentication Protocol over LAN [EAPOL]-logoff message is received), all attached clients are denied access to the network.
Use the multi-domain keyword to enable MDA on a port. MDA divides the port into both a data domain and a voice domain. MDA allows both a data device and a voice device, such as an IP phone (Cisco or non-Cisco), on the same IEEE 802.1x-enabled port.
Before entering this command, make sure that the dot1x port-control interface configuration command is set to auto for the specified port.
Examples
This example shows how to enable IEEE 802.1x authentication globally, to enable IEEE 802.1x authentication on a port, and to enable multiple-hosts mode:
This example shows how to globally enable IEEE 802.1x authentication, to enable IEEE 802.1x authentication, and to enable MDA on the specified port:
You can verify your settings by entering the show dot1x [ interface interface-id ] privileged EXEC command.
Related Commands
|
|
|
|---|---|
show dot1x [ interface interface-id ] |
dot1x initialize
Use the dot1x initialize privileged EXEC command to manually return the specified IEEE 802.1x-enabled port to an unauthorized state before initiating a new authentication session on the port.
dot1x initialize [ interface interface-id ]
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use this command to initialize the IEEE 802.1x state machines and to set up a fresh environment for authentication. After you enter this command, the port status becomes unauthorized.
Examples
This example shows how to manually initialize a port:
You can verify the unauthorized port status by entering the show dot1x [ interface interface-id ] privileged EXEC command.
Related Commands
|
|
|
|---|---|
show dot1x [ interface interface-id ] |
dot1x mac-auth-bypass
Use the dot1x mac-auth-bypass interface configuration command to enable the MAC authentication bypass feature. Use the no form of this command to disable MAC authentication bypass feature.
dot1x mac-auth-bypass [ eap | timeout inactivity value ]
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Unless otherwise stated, the MAC authentication bypass usage guidelines are the same as the IEEE 802.1x authentication guidelines.
If you disable MAC authentication bypass from a port after the port has been authenticated 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.
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 uses IEEE 802.1x authentication (not MAC authentication bypass) to authorize the interface.
Clients that were authorized with MAC authentication bypass can be re-authenticated.
For more information about how MAC authentication bypass and IEEE 802.lx authentication interact, see the “Understanding IEEE 802.1x Authentication with MAC Authentication Bypass” section and the “IEEE 802.1x Authentication Configuration Guidelines” section in the “Configuring IEEE 802.1x Port-Based Authentication” chapter of the software configuration guide.
Examples
This example shows how to enable MAC authentication bypass and to configure the switch to use EAP for authentication:
This example shows how to enable MAC authentication bypass and to configure the timeout if the connected host is inactive for 30 seconds:
You can verify your settings by entering the show dot1x [ interface interface-id ] privileged EXEC command.
Related Commands
|
|
|
|---|---|
show dot1x [ interface interface-id ] |
dot1x max-reauth-req
Use the dot1x max-reauth-req interface configuration command to set the maximum number of times that the switch restarts the authentication process before a port changes to the unauthorized state. Use the no form of this command to return to the default setting.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
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.
Examples
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:
You can verify your settings by entering the show dot1x [ interface interface-id ] privileged EXEC command.
Related Commands
|
|
|
|---|---|
Sets the maximum number of times that the switch forwards an EAP frame (assuming that no response is received) to the authentication server before restarting the authentication process. |
|
dot1x timeout tx-period |
Sets the number of seconds that the switch waits for a response to an EAP-request/identity frame from the client before resending the request. |
show dot1x [ interface interface-id ] |
dot1x max-req
Use the dot1x max-req interface configuration command to set the maximum number of times that the switch sends an Extensible Authentication Protocol (EAP) frame from the authentication server (assuming that no response is received) to the client before restarting the authentication process. Use the no form of this command to return to the default setting.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command was changed to the interface configuration mode. |
Usage Guidelines
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.
Examples
This example shows how to set 5 as the number of times that the switch sends an EAP frame from the authentication server to the client before restarting the authentication process:
You can verify your settings by entering the show dot1x [ interface interface-id ] privileged EXEC command.
Related Commands
|
|
|
|---|---|
dot1x timeout tx-period |
Sets the number of seconds that the switch waits for a response to an EAP-request/identity frame from the client before resending the request. |
show dot1x [ interface interface-id ] |
dot1x multiple-hosts
In past releases, the dot1x multiple-hosts interface configuration command was used to allow multiple hosts (clients) on an IEEE 802.1x-authorized port.
Command History
|
|
|
|---|---|
The dot1x multiple-hosts interface configuration command was replaced by the dot1x host-mode interface configuration command. |
Related Commands
|
|
|
|---|---|
Displays IEEE 802.1x statistics, administrative status, and operational status for the switch or for the specified port. |
dot1x pae
Use the dot1x pae interface configuration command to configure the port as an IEEE 802.1x port access entity (PAE) authenticator. Use the no form of this command to disable IEEE 802.1x authentication on the port.
Syntax Description
Defaults
The port is not an IEEE 802.1x PAE authenticator, and IEEE 802.1x authentication is disabled on the port.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the no dot1x pae interface configuration command to disable IEEE 802.1x authentication on the port.
When you configure IEEE 802.1x authentication on a port, such as by entering the dot1x port-control interface configuration command, the switch automatically configures the port as an EEE 802.1x authenticator. After the no dot1x pae interface configuration command is entered, the Authenticator PAE operation is disabled.
Examples
This example shows how to disable IEEE 802.1x authentication on the port:
You can verify your settings by entering the show dot1x or show eap privileged EXEC command.
Related Commands
dot1x port-control
Use the dot1x port-control interface configuration command to enable manual control of the authorization state of the port. Use the no form of this command to return to the default setting.
dot1x port-control { auto | force-authorized | force-unauthorized }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You must globally enable IEEE 802.1x authentication on the switch by using the dot1x system-auth-control global configuration command before enabling IEEE 802.1x authentication on a specific port.
The IEEE 802.1x standard is supported on Layer 2 static-access ports, voice VLAN ports, and Layer 3 routed ports.
You can use the auto keyword only if the port is not configured as one of these:
- Trunk port—If you try to enable IEEE 802.1x authentication 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, 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 IEEE 802.1x authentication on a dynamic port, an error message appears, and IEEE 802.1x authentication is not enabled. If you try to change the mode of an IEEE 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 IEEE 802.1x authentication on a dynamic-access (VLAN Query Protocol [VQP]) port, an error message appears, and IEEE 802.1x authentication 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.
- EtherChannel port—Do not configure a port that is an active or a not-yet-active member of an EtherChannel as an IEEE 802.1x port. If you try to enable IEEE 802.1x authentication on an EtherChannel port, an error message appears, and IEEE 802.1x authentication is not enabled.
- Switched Port Analyzer (SPAN) and Remote SPAN (RSPAN) destination ports—You can enable IEEE 802.1x authentication on a port that is a SPAN or RSPAN destination port. However, IEEE 802.1x authentication is disabled until the port is removed as a SPAN or RSPAN destination. You can enable IEEE 802.1x authentication on a SPAN or RSPAN source port.
To globally disable IEEE 802.1x authentication on the switch, use the no dot1x system-auth-control global configuration command. To disable IEEE 802.1x authentication on a specific port or to return to the default setting, use the no dot1x port-control interface configuration command.
Examples
This example shows how to enable IEEE 802.1x authentication on a port:
You can verify your settings by entering the show dot1x [ interface interface-id ] privileged EXEC command.
Related Commands
|
|
|
|---|---|
show dot1x [ interface interface-id ] |
dot1x re-authenticate
Use the dot1x re-authenticate privileged EXEC command to manually initiate a re-authentication of the specified IEEE 802.1x-enabled port.
dot1x re-authenticate [ interface interface-id ]
Syntax Description
(Optional) Stack switch number, module, and port number of the interface to re-authenticate |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You can use this command to re-authenticate a client without waiting for the configured number of seconds between re-authentication attempts (re-authperiod) and automatic re-authentication.
Examples
This example shows how to manually re-authenticate the device connected to a port:
Related Commands
|
|
|
|---|---|
dot1x timeout reauth-period |
Sets the number of seconds between re-authentication attempts. |
dot1x re-authentication
In past releases, the dot1x re-authentication global configuration command was used to set the amount of time between periodic re-authentication attempts.
Command History
|
|
|
|---|---|
The dot1x reauthentication interface configuration command replaced the dot1x re-authentication global configuration command. |
Related Commands
dot1x reauthentication
Use the dot1x reauthentication interface configuration command to enable periodic re-authentication of the client. Use the no form of this command to return to the default setting.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command was introduced. It replaces the dot1x re-authentication global configuration command (with the hyphen). |
Usage Guidelines
You configure the amount of time between periodic re-authentication attempts by using the dot1x timeout reauth-period interface configuration command.
Examples
This example shows how to disable periodic re-authentication of the client:
This example shows how to enable periodic re-authentication and to set the number of seconds between re-authentication attempts to 4000 seconds:
You can verify your settings by entering the show dot1x [ interface interface-id ] privileged EXEC command.
Related Commands
|
|
|
|---|---|
Manually initiates a re-authentication of all IEEE 802.1x-enabled ports. |
|
dot1x timeout reauth-period |
Sets the number of seconds between re-authentication attempts. |
show dot1x [ interface interface-id ] |
dot1x supplicant force-multicast
Use the dot1x supplicant force-multicast global configuration command to force a supplicant switch to send only multicast Extensible Authentication Protocol over LAN (EAPOL) packets whenever it receives multicast or unicast EAPOL packets. Use the no form of this command to return to the default setting.
dot1x supplicant force-multicast
no dot1x supplicant force-multicast
Syntax Description
Defaults
The supplicant switch sends unicast EAPoL packets when it receives unicast EAPOL packets. Similarly, it sends multicast EAPOL packets when it receives multicast EAPOL packets.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Enable this command on the supplicant switch for Network Edge Access Topology (NEAT) to work in all host modes.
Examples
This example shows how force a supplicant switch to send multicast EAPOL packets to authenticator switch:
Related Commands
|
|
|
|---|---|
Enable Client Information Signalling Protocol (CISP) on a switch so that it acts as an authenticator to a supplicant switch. |
|
dot1x test eapol-capable
Use the dot1x test eapol-capable privileged EXEC command to monitor IEEE 802.1x activity on all the switch ports and to display information about the devices that are connected to the ports that support IEEE 802.1x.
dot1x test eapol-capable [ interface interface-id ]
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use this command to test the IEEE 802.1x capability of the devices connected to all ports or to specific ports on a switch.
Examples
This example shows how to enable the IEEE 802.1x 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 IEEE 802.1x-capable:
Related Commands
|
|
|
|---|---|
dot1x test timeout timeout |
Configures the timeout used to wait for EAPOL response to an IEEE 802.1x readiness query. |
dot1x test timeout
Use the dot1x test timeout global configuration command to configure the timeout used to wait for EAPOL response from a port being queried for IEEE 802.1x readiness.
Syntax Description
Time in seconds to wait for an EAPOL response. The range is from 1 to 65535 seconds. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use this command to configure the timeout used to wait for EAPOL response.
Examples
This example shows how to configure the switch to wait 27 seconds for an EAPOL response:
You can verify the timeout configuration status by entering the show run privileged EXEC command.
Related Commands
|
|
|
|---|---|
dot1x test eapol-capable [ interface interface-id ] |
Checks for IEEE 802.1x readiness on devices connected to all or to specified IEEE 802.1x-capable ports. |
dot1x timeout
Use the dot1x timeout interface configuration command to set IEEE 802.1x timers. Use the no form of this command to return to the default setting.
dot1x timeout { quiet-period seconds | ratelimit-period seconds | reauth-period { seconds | server } | server-timeout seconds | supp-timeout seconds | tx-period seconds }
no dot1x timeout { quiet-period | reauth-period | server-timeout | supp-timeout | tx-period }
Syntax Description
Defaults
These are the default settings:
Command Modes
Command History
Usage Guidelines
You should change the default value of this command only to adjust for unusual circumstances such as unreliable links or specific behavioral problems with certain clients and authentication servers.
The dot1x timeout reauth-period interface configuration command affects the behavior of the switch only if you have enabled periodic re-authentication by using the dot1x reauthentication interface configuration command.
During the quiet period, the switch does not accept or initiate any authentication requests. If you want to provide a faster response time to the user, enter a number smaller than the default.
When the ratelimit-period is set to 0 (the default), the switch does not ignore EAPOL packets from clients that have been successfully authenticated and forwards them to the RADIUS server.
Examples
This example shows how to enable periodic re-authentication and to set 4000 as the number of seconds between re-authentication attempts:
This example shows how to enable periodic re-authentication and to specify the value of the Session-Timeout RADIUS attribute as the number of seconds between re-authentication attempts:
This example shows how to set 30 seconds as the quiet time on the switch:
This example shows how to set 45 seconds as the switch-to-authentication server retransmission time:
This example shows how to set 45 seconds as the switch-to-client retransmission time for the EAP request frame:
This example shows how to set 60 as the number of seconds to wait for a response to an EAP-request/identity frame from the client before re-transmitting the request:
This example shows how to set 30 as the number of seconds that the switch ignores EAPOL packets from successfully authenticated clients:
You can verify your settings by entering the show dot1x privileged EXEC command.
Related Commands
|
|
|
|---|---|
Sets the maximum number of times that the switch sends an EAP-request/identity frame before restarting the authentication process. |
|
dot1x violation-mode
Use the dot1x violation-mode interface configuration command to 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.
dot1x violation-mode {shutdown | restrict | protect}
Syntax Description
Error disables the port or the virtual port on which a new unexpected MAC address occurs. |
|
Silently discards packets from any new MAC addresses. This is the default setting. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Examples
This example shows how to configure an IEEE 802.1x-enabled port as error disabled and to shut down when a new device connects to the port:
This example shows how to configure an IEEE 802.1x-enabled port to generate a system error message and change the port to restricted mode when a new device connects to the port:
This example shows how to configure an IEEE 802.1x-enabled port to ignore a new connected device when it is connected to the port:
You can verify your settings by entering the show dot1x [ interface interface-id ] privileged EXEC command.
Related Commands
|
|
|
|---|---|
show dot1x [ interface interface-id ] |
duplex
Use the duplex interface configuration command to specify the duplex mode of operation for a port. Use the no form of this command to return the port to its default value.
Syntax Description
Defaults
The default is auto for Fast Ethernet and Gigabit Ethernet ports.
The default is half for 100BASE-x (where -x is -BX, -FX, -FX-FE, or - LX) small form-factor pluggable (SFP) modules.
Duplex options are not supported on the 1000BASE- x (where - x is -BX, -CWDM, -LX, -SX, or -ZX) SFP modules.
For information about which SFP modules are supported on your switch, see the product release notes.
Command Modes
Command History
|
|
|
|---|---|
Support for the half keyword was added for the 100BASE-FX SFP module. |
Usage Guidelines
This command is not available on a 10-Gigabit Ethernet interface.
For Fast Ethernet ports, setting the port to auto has the same effect as specifying half if the attached device does not autonegotiate the duplex parameter.
For Gigabit Ethernet ports, setting the port to auto has the same effect as specifying full if the attached device does not autonegotiate the duplex parameter.
Note Half-duplex mode is supported on Gigabit Ethernet interfaces if the duplex mode is auto and the connected device is operating at half duplex. However, you cannot configure these interfaces to operate in half-duplex mode.
Certain ports can be configured to be either full duplex or half duplex. Applicability of this command depends on the device to which the switch is attached.
If both ends of the line support autonegotiation, we highly recommend using the default autonegotiation settings. If one interface supports autonegotiation and the other end does not, configure duplex and speed on both interfaces; do use the auto setting on the supported side.
If the speed is set to auto, the switch negotiates with the device at the other end of the link for the speed setting and then forces the speed setting to the negotiated value. The duplex setting remains as configured on each end of the link, which could result in a duplex setting mismatch.
You can configure the duplex setting when the speed is set to auto.
Changing the interface speed and duplex mode configuration might shut down and re-enable the interface during the reconfiguration.
For guidelines on setting the switch speed and duplex parameters, see the “Configuring Interface Characteristics” chapter in the software configuration guide for this release.
Examples
This example shows how to configure an interface for full-duplex operation:
You can verify your setting by entering the show interfaces privileged EXEC command.
Related Commands
|
|
|
|---|---|
epm access-control open
Use the epm access-control open global configuration command on the switch stack or on a standalone switch to configure an open directive for ports that do not have an access control list (ACL) configured. Use the no form of this command to disable the open directive.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
Usage Guidelines
Use this command to configure an open directive that allows hosts without an authorization policy to access ports configured with a static ACL. If you do not configure this command, the port applies the policies of the configured ACL to the traffic. If no static ACL is configured on a port, both the default and open directives allow access to the port.
Examples
This example shows how to configure an open directive.
You can verify your settings by entering the show running-config privileged EXEC command.
Related Commands
|
|
|
|---|---|
Displays the operating configuration. For syntax information, use this link to the Cisco IOS Release 12.2 Command Reference listing page: http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/prod_command_reference_list.html |
errdisable detect cause
Use the errdisable detect cause global configuration command to enable error-disable detection for a specific cause or all causes. Use the no form of this command to disable the error-disable detection feature.
errdisable detect cause { all | arp-inspection | bpduguard | dhcp-rate-limit | dtp-flap | gbic-invalid | inline-power | l2ptguard | link-flap | loopback | pagp-flap | security-violation shutdown vlan | sfp-config-mismatch }
no errdisable detect cause { all | arp-inspection | bpduguard | dhcp-rate-limit | dtp-flap | gbic-invalid | inline-power | l2ptguard | link-flap | loopback | pagp-flap | security-violation shutdown vlan | sfp-config-mismatch }
For the BPDU guard and port-security features, you can use this command to globally configure the switch to shut down just the offending VLAN on the port when a violation occurs, instead of shutting down the entire port.
When the per-VLAN error-disable feature is turned off and a BPDU guard violation occurs, the entire port is disabled. Use the no form of this command to disable the per-VLAN error-disable feature.
errdisable detect cause bpduguard shutdown vlan
no errdisable detect cause bpduguard shutdown vlan
Syntax Description
Command Default
Detection is enabled for all causes. All causes, except for per-VLAN error disabling, are configured to shut down the entire port.
Command Modes
Command History
|
|
|
|---|---|
The Per-VLAN error-detection feature was added. The inline-power and sfp-config-mismatch keywords were added. |
|
Usage Guidelines
A cause (link-flap, dhcp-rate-limit, and so forth) is the reason why the error-disabled state occurred. When a cause is detected on a port, the port is placed in an error-disabled state, an operational state that is similar to a link-down state.
When a port is error-disabled, it is effectively shut down, and no traffic is sent or received on the port. For the BPDU, voice aware 802.1x security, guard and port-security features, you can configure the switch to shut down just the offending VLAN on the port when a violation occurs, instead of shutting down the entire port.
If you set a recovery mechanism for the cause by entering the errdisable recovery global configuration command for the cause, the port is brought out of the error-disabled state and allowed to retry the operation when all causes have timed out. If you do not set a recovery mechanism, you must enter the shutdown and then the no shutdown commands to manually change the port from the error-disabled state.
Examples
This example shows how to enable error-disable detection for the link-flap error-disabled cause:
Switch(config)# errdisable detect cause link-flap
This command shows how to globally configure BPDU guard for per-VLAN error disable:
Switch(config)# errdisable detect cause bpduguard shutdown vlan
This command shows how to globally configure voice aware 802.1x security for per-VLAN error disable:
Switch(config)# errdisable detect cause security-violation shutdown vlan
You can verify your settings by entering the show errdisable detect privileged EXEC command.
Related Commands
|
|
|
|---|---|
show interfaces status err-disabled |
Displays interface status or a list of interfaces in the error-disabled state. |
Clears the error-disabled state from a port or VLAN that was error disabled by the per-VLAN error disable feature. |