-
Catalyst 6500 Series Cisco IOS Command Reference, 12.1 E
-
Quick Links to Catalyst 6500 Series Switch Cisco IOS Commands
-
Index
-
Preface
-
Command-Line Interface
-
action to cd
-
channel-group to clear catalyst6000
-
clear counters to debug callback
-
debug cca to duplex
-
erase to mls aging
-
mls exclude to pagp port-priority
-
policy-map to protocol filtering
-
rcv-queue to show bootflash:
-
shutdown vlan to time-range
-
show bootvar to show ip cache
-
T1
-
show ip cef to show mls asic
-
show mls cef to show qm-sp
-
show queueing to show vtp
-
udld to username
-
verify to wrr-queue bandwidth
-
wrr-queue cos-map to wrr-queue threshold
-
Acronyms
-
Acknowledgments for Open-Source Software
-
Table Of Contents
spanning-tree etherchannel guard misconfig
spanning-tree extend system-id
spanning-tree loopguard default
spanning-tree mst configuration
spanning-tree mst forward-time
spanning-tree portfast (interface configuration mode)
spanning-tree portfast bpdufilter default
spanning-tree portfast bpduguard default
spanning-tree portfast default
switchport capture allowed vlan
switchport port-security aging time
switchport port-security mac-address
switchport port-security maximum
switchport port-security violation
switchport private-vlan host-association
switchport private-vlan mapping
22shutdown vlan
To shut down local traffic on a specified VLAN, use the shutdown vlan command. Use the no form of this command to restart local traffic on the VLAN.
shutdown vlan vlan-id
no shutdown vlan vlan-id
Syntax Description
Defaults
This command has no default settings.
Command Modes
Global configuration
Command History
12.0(7)XE
Support for this command was introduced on the Catalyst 6500 series switches.
Usage Guidelines
This command does not support extended-range VLANs.
Examples
This example shows how to cause traffic to be shut down on VLAN 2:
Router(config)# shutdown vlan 2Router(config)#snmp ifindex clear
To clear any previously configured snmp ifindex commands issued for a specific interface, use the snmp ifindex clear command.
snmp ifindex clear
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Interface configuration
Command History
12.1(13)E
Support for this command was introduced on the Catalyst 6500 series switches.
Usage Guidelines
Interface index persistence occurs when ifIndex values in the IF-MIB persist across reboots and allow for consistent identification of specific interfaces using SNMP.
Use the snmp ifindex clear command on a specific interface when you want that interface to use the global configuration setting for ifIndex persistence. This command clears any ifIndex configuration commands previously entered for that specific interface.
Examples
This example shows how to enable ifIndex persistence for all interfaces:
Router(config)# snmp-server ifindex persistThis example shows how to disable IfIndex persistence for Ethernet 0/1 only:
Router(config)# interface ethernet 0/1Router(config-if)# no snmp ifindex persistRouter(config-if)# exitThis example shows how to clear the ifIndex configuration from the Ethernet 0/1 configuration:
Router(config)# interface ethernet 0/1Router(config-if)# snmp ifindex clearRouter(config-if)# exitThis leaves ifIndex persistence enabled for all interfaces as specified by the snmp-server ifindex persist global configuration command.
Related Commands
snmp ifindex persist
snmp-server ifindex persistsnmp ifindex persist
To enable ifIndex values in the Interfaces MIB (IF-MIB) that persist across reboots (ifIndex persistence) only on a specific interface, use the snmp ifindex persist command. Use the no form of this command to disable ifIndex persistence only on a specific interface.
snmp ifindex persist
no snmp ifindex persist
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
12.1(13)E
Support for this command was introduced on the Catalyst 6500 series switches.
Usage Guidelines
Interface index persistence occurs when ifIndex values in the IF-MIB persist across reboots and allow for consistent identification of specific interfaces using SNMP.
The snmp ifindex persist interface configuration command enables and disables ifIndex persistence for individual entries (that correspond to individual interfaces) in the ifIndex table of the IF-MIB.
The snmp-server ifindex persist global configuration command enables and disables ifIndex persistence for all interfaces on the routing device. This action applies only to interfaces that have ifDescr and ifIndex entries in the ifIndex table of the IF-MIB.
IfIndex commands that you configure for an interface apply to all subinterfaces on that interface.
Examples
This example shows how to enable ifIndex persistence for interface Ethernet 0/1 only:
Router(config)# interface ethernet 0/1Router(config-if)# snmp ifindex persistRouter(config-if)# exitThis example shows how to enable ifIndex persistence for all interfaces and then disable ifIndex persistence for interface Ethernet 0/1 only:
Router(config)# snmp-server ifindex persistRouter(config)# interface ethernet 0/1Router(config-if)# no snmp ifindex persistRouter(config-if)# exitRelated Commands
snmp-server enable traps
To enable SNMP notifications (traps or informs) that are available on your system, use the snmp-server enable traps command. To disable all available SNMP notifications, use the no form of this command.
snmp-server enable traps [notification-type]
no snmp-server enable traps [notification-type]
Syntax Description
notification-type
(Optional) Type of notification (trap or inform) to enable or disable. See the "Usage Guidelines" section for additional information.
Defaults
This command is disabled by default. Most notification types are disabled. However, some notification types cannot be controlled with this command.
Command Modes
Global configuration
Command History
Usage Guidelines
If you do not specify a notification-type, all notifications that are available on your device are enabled or disabled. The notification type can be one of the following keywords:
•
chassis—Controls the SNMP chassis trap notifications
•
–
–
•
•
•
•
•
•
•
•
For additional notification types, refer to the Cisco IOS Release 12.1 Command Reference.
SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests for the specified notification types. To specify whether the notifications should be sent as traps or informs, use the snmp-server host [traps | informs] command.
If you do not enter an snmp-server enable traps command, no notifications that are controlled by this command are sent. To configure the router to send these SNMP notifications, you must enter at least one snmp-server enable traps command. If you enter the command with no keywords, all notification types are enabled. If you enter the command with a keyword, only the notification type that is related to that keyword is enabled. To enable multiple types of notifications, you must issue a separate snmp-server enable traps command for each notification type and notification option.
The snmp-server enable traps command is used with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP notifications. To send notifications, you must configure at least one snmp-server host command.
The following is a list of the MIBs that are used for the traps:
•
•
–
–
•
•
•
•
•
•
Examples
This example shows how to send all traps to the host that are specified by the name myhost.cisco.com, using the community string that is defined as public:
Router(config)# snmp-server enable trapsRouter(config)# snmp-server host myhost.cisco.com publicRelated Commands
Refer to the Cisco IOS Release 12.1 Command Reference for additional snmp-server enable traps commands.
snmp-server ifindex persist
To globally enable ifIndex values that will remain constant across reboots for use by SNMP, use the snmp-server ifindex persist command. Use the no form of this command to globally disable ifIndex persistence.
snmp-server ifindex persist
no snmp-server ifindex persist
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
12.1(13)E
Support for this command was introduced on the Catalyst 6500 series switches.
Usage Guidelines
Interface index persistence occurs when ifIndex values in the IF-MIB persist across reboots and allow for consistent identification of specific interfaces using SNMP.
The snmp-server ifindex persist global configuration command does not override interface-specific configuration. To override the interface-specific configuration of ifIndex persistence, enter the [no] snmp ifindex persist and snmp ifindex clear interface configuration commands.
Entering the [no] snmp-server ifindex persist global configuration command enables and disables ifIndex persistence for all interfaces on the routing device using ifDescr and ifIndex entries in the ifIndex table of the IF-MIB.
Examples
This example shows how to enable ifIndex persistence for all interfaces:
Router(config)# snmp-server ifindex persist
Note
Related Commands
spanning-tree backbonefast
To enable the BackboneFast feature on all Ethernet VLANs, use the spanning-tree backbonefast command. Use the no form of this command to disable BackboneFast.
spanning-tree backbonefast
no spanning-tree backbonefast
Syntax Description
This command has no arguments or keywords.
Defaults
BackboneFast is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
Enable BackboneFast on all Catalyst 6500 series switches to allow the detection of indirect link failures in order to start spanning tree reconfiguration sooner.
Examples
This example shows how to enable BackboneFast on all Ethernet VLANs:
Router(config)# spanning-tree backbonefast vlan all ethernetRouter(config)#Related Commands
spanning-tree bpdufilter
To enable BPDU filtering on the interface, use the spanning-tree bpdufilter command. Use the no form of this command to return to the default settings.
spanning-tree bpdufilter {enable | disable}
no spanning-tree bpdufilter
Syntax Description
Defaults
The setting that is already configured when you enter the spanning-tree portfast bpdufilter default command.
Command Modes
Interface configuration
Command History
12.1(11b)EX
Support for this command was introduced on the Catalyst 6500 series switches.
12.1(13)E
Support for this command was introduced on the Catalyst 6500 series switches.
Usage Guidelines
Caution
When configuring Layer 2 protocol tunneling on all the service provider edge switches, you must enable spanning tree BPDU filtering on the 802.1Q tunnel ports by entering the spanning-tree bpdufilter enable command.
BPDU filtering allows you to prevent a port from sending and receiving BPDUs. The configuration is applicable to the whole interface, whether it is trunking or not. This command has three states:
•
•
•
Examples
This example shows how to enable the BPDU filter feature on this interface:
Router(config-if)# spanning-tree bpdufilter enableRouter(config-if)#Related Commands
show spanning-tree
spanning-tree portfast bpdufilter defaultspanning-tree bpduguard
To enable BPDU guard on the interface, use the spanning-tree bpduguard command. Use the no form of this command to return to the default settings.
spanning-tree bpduguard {enable | disable}
no spanning-tree bpduguard
Syntax Description
Defaults
The setting that is already configured when you enter the spanning-tree portfast bpduguard default command.
Command Modes
Interface configuration
Command History
12.1(11b)EX
Support for this command was introduced on the Catalyst 6500 series switches.
12.1(13)E
Support for this command was introduced on the Catalyst 6500 series switches.
Usage Guidelines
BPDU guard prevents a port from receiving BPDUs. Typically, this feature is used in a service provider environment where the administrator wants to prevent an access port from participating in the spanning tree. If the port still receives a BPDU, it is put in the ErrDisable state as a protective measure. This command has three states:
•
•
•
Examples
This example shows how to enable BPDU guard on this interface:
Router(config-if)# spanning-tree bpduguard enableRouter(config-if)#Related Commands
show spanning-tree
spanning-tree portfast bpduguard defaultspanning-tree cost
To set the path cost of the interface for STP calculations, use the spanning-tree cost command. Use the no form of this command to revert to the default settings.
spanning-tree cost cost
no spanning-tree cost
Syntax Description
Defaults
The default path cost is computed from the interface's bandwidth setting; default path costs are as follows:
•
•
•
•
•
•
•
•
Command Modes
Interface configuration
Command History
Usage Guidelines
Valid path cost values are from 1 to 200000000 for Releases 12.1(3a)E and later and from 1 to 65535 for releases prior to Release 12.1(3a)E.
Spanning-tree protocol uses the port cost value when the LAN interface is configured as an access port and uses the VLAN port cost values when the LAN interface is configured as a trunk port.
If a loop occurs, STP considers the port cost when selecting a LAN interface to put into the forwarding state. You can assign lower cost values to the LAN interfaces that you want STP to select first and higher cost values to the LAN interfaces that you want STP to select last. If all LAN interfaces have the same cost value, STP puts the LAN interface with the lowest LAN interface number in the forwarding state and blocks other LAN interfaces.
The possible cost range is 0 through 200000000 (the default is media specific).
When you configure the cost, note that higher values indicate higher costs. This range applies regardless of the protocol type that is specified.
Examples
This example shows how to access an interface and set a path cost value of 250 for the spanning tree VLAN that is associated with that interface:
Router(config)# interface ethernet 2/0Router(config-if)# spanning-tree cost 250Router(config-if)#Related Commands
spanning-tree etherchannel guard misconfig
To display an error message when a loop due to a channel misconfiguration is detected, use the spanning-tree etherchannel guard misconfig command. Use the no form of this command to disable the feature.
spanning-tree etherchannel guard misconfig
no spanning-tree etherchannel guard misconfig
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Global configuration
Command History
12.1(8a)E
Support for this command was introduced on the Catalyst 6500 series switches.
Usage Guidelines
When an EtherChannel guard misconfiguration is detected, this error message displays:
msgdef(CHNL_MISCFG, SPANTREE, LOG_CRIT, 0, "Detected loop due to etherchannel misconfiguration of %s %s")To determine which local ports are involved in the misconfiguration, enter the show interfaces status err-disabled command. To check the EtherChannel configuration on the remote device, enter the show etherchannel summary command on the remote device.
After you correct the configuration, enter the shutdown and the no shutdown commands on the associated port-channel interface.
Examples
This example shows how to enable the EtherChannel guard misconfiguration feature:
Router(config)# spanning-tree etherchannel guard misconfigRouter(config)#Related Commands
show interfaces status err-disabled
show etherchannel summary
shutdown (refer to the Cisco IOS Release 12.1 Command Reference)spanning-tree extend system-id
To enable the extended system ID feature on chassis that support 1024 MAC addresses, use the spanning-tree extend system-id command. Use the no form of this command to disable the feature.
spanning-tree extend system-id
no spanning-tree extend system-id
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled on systems that do not provide 1024 MAC addresses.
Command Modes
Global configuration
Command History
12.1(8a)E
Support for this command was introduced on the Catalyst 6500 series switches.
Usage Guidelines
Releases 12.1(8a)E and later support chassis with 64 or 1024 MAC addresses. For chassis with 64 MAC addresses, STP uses the extended system ID plus a MAC address to make the bridge ID unique for each VLAN.
You cannot disable the extended system ID on chassis that support 64 MAC addresses.
Enabling or disabling the extended system ID updates the bridge IDs of all active STP instances, which might change the spanning tree topology.
Examples
This example shows how to enable the extended system ID:
Router(config)# spanning-tree extend system-idRouter(config)#Related Commands
spanning-tree guard
To enable or disable the guard mode, use the spanning-tree guard command. Use the no form of this command to revert to the default settings.
spanning-tree guard {loop | root | none}
no spanning-tree guard
Syntax Description
loop
Enables the loop-guard mode on the interface.
root
Enables root-guard mode on the interface.
none
Sets the guard mode to none.
Defaults
Guard mode is disabled.
Command Modes
Interface configuration
Command History
Examples
This example shows how to enable root guard:
Router(config-if)# spanning-tree guard rootRouter(config-if)#Related Commands
show spanning-tree
spanning-tree loopguard defaultspanning-tree link-type
To configure a link type for a port, use the spanning-tree link-type command. Use the no form of this command to return to the default settings.
spanning-tree link-type {point-to-point | shared}
no spanning-tree link-type
Syntax Description
point-to-point
Specifies that the interface is a point-to-point link.
shared
Specifies that the interface is a shared medium.
Defaults
Link type is automatically derived from the duplex operational setting unless you explicitly configure the link type.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is not supported on systems configured with a Supervisor Engine 1.
RSTP+ fast transition only works on point-to-point links between two bridges.
By default, the switch derives the link type of a port from the duplex mode. A full-duplex port is considered as a point-to-point link while a half-duplex configuration is assumed to be on a shared link.
If you designate a port as a shared link, RSTP+ fast transition is forbidden, regardless of the duplex setting.
Examples
This example shows how to configure the port as a shared link:
Router(config-if)# spanning-tree link-type sharedRouter(config-if)#Related Commands
show spanning-tree interface
spanning-tree loopguard default
To enable loop guard as a default on all ports of a given bridge, use the spanning-tree loopguard default command. Use the no form of this command to disable loop guard.
spanning-tree loopguard default
no spanning-tree loopguard default
Syntax Description
This command has no keywords or arguments.
Defaults
Loop guard is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
Loop guard provides an additional security in the bridge network. Loop guard prevents alternate or root ports from becoming the designated port due to a failure that could lead to a unidirectional link.
Loop guard only operates on ports that are considered point to point by the spanning tree.
The individual loop-guard port configuration overrides this command.
Examples
This example shows how to enable loop guard:
Router(config)# spanning-tree loopguard defaultRouter(config)#Related Commands
show spanning-tree
spanning-tree guardspanning-tree mode
To switch between PVST+, Rapid PVST, and MST modes, use the spanning-tree mode command. Use the no form of this command to return to the default settings.
spanning-tree mode [pvst | mst | rapid-pvst]
no spanning-tree mode
Syntax Description
Defaults
pvst
Command Modes
Global configuration
Command History
Usage Guidelines
Caution
This command is not supported on systems configured with a Supervisor Engine 1.
Examples
This example shows how to switch to MST mode:
Router(config)# spanning-tree mode mstRouter(config)#This example shows how to return to the default mode (PVST):
Router(config)# no spanning-tree modeRouter(config)#Related Commands
spanning-tree mst
To set the path cost and port-priority parameters for any MST instance (including the CIST with instance ID 0), use the spanning-tree mst command. Use the no form of this command to return to the default settings.
spanning-tree mst instance-id {cost cost} | {port-priority prio}
Syntax Description
Defaults
The defaults are as follows:
•
•
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is not supported on systems configured with a Supervisor Engine 1.
Higher cost cost values indicate higher costs. When entering the cost, do not include a comma in the entry; for example, enter 1000, not 1,000.
Higher port-priority prio values indicate smaller priorities.
Examples
This example shows how to set the interface path cost:
Router(config-if)# spanning-tree mst 0 cost 17031970Router(config-if)#This example shows how to set the interface priority:
Router(config-if)# spanning-tree mst 0 port-priority 64Router(config-if)#Related Commands
show spanning-tree mst
spanning-tree port-priorityspanning-tree mst configuration
To enter MST configuration submode, use the spanning-tree mst configuration command. Use the no form of this command to return to the default MST configuration.
spanning-tree mst configuration
no spanning-tree mst configuration
Syntax Description
This command has no keywords or arguments.
Defaults
The default value for the MST configuration is the default value for all its parameters:
•
•
•
Command Modes
Global configuration
Command History
Usage Guidelines
This command is not supported on systems configured with a Supervisor Engine 1.
The MST configuration consists of three main parameters:
•
•
•
The abort and exit commands allow you to exit MST configuration submode. The difference between the two commands depends on whether you want to save your changes or not.
The exit command commits all the changes before leaving MST configuration submode. If you do not map secondary VLANs to the same instance as the associated primary VLAN, when you exit MST configuration submode, a warning message displays and lists the secondary VLANs that are not mapped to the same instance as the associated primary VLAN. The warning message is as follows:
These secondary vlans are not mapped to the same instance as their primary:-> 3The abort command leaves MST configuration submode without committing any changes.
Whenever you change an MST configuration submode parameter, it can cause a loss of connectivity. To reduce the number of service disruptions, when you enter MST configuration submode, you are changing a copy of the current MST configuration. When you are done editing the configuration, you can apply all the changes at once by using the exit keyword, or you can exit the submode without committing any change to the configuration by using the abort keyword.
In the unlikely event that two users commit a new configuration at exactly at the same time, this warning message displays:
Router(config-mst)# exit% MST CFG:Configuration change lost because of concurrent accessRouter(config-mst)#Examples
This example shows how to enter MST configuration submode:
Router(config)# spanning-tree mst configurationRouter(config-mst)#This example shows how to reset the MST configuration to the default settings:
Router(config)# no spanning-tree mst configurationRouter(config)#Related Commands
spanning-tree mst forward-time
To set the forward delay timer for all the instances on the Catalyst 6500 series switch, use the spanning-tree mst forward-time command. Use the no form of this command to return to the default settings.
spanning-tree mst forward-time seconds
no spanning-tree mst forward-time
Syntax Description
seconds
Number of seconds to set the forward delay timer for all the instances on the Catalyst 6500 series switch; valid values are from 4 to 30 seconds.
Defaults
seconds is 15.
Command Modes
Global configuration
Command History
Usage Guidelines
This command is not supported on systems configured with a Supervisor Engine 1.
Examples
This example shows how to set the forward-delay timer:
Router(config)# spanning-tree mst forward-time 20Router(config)#
Related Commands
spanning-tree mst hello-time
To set the hello-time delay timer for all the instances on the Catalyst 6500 series switch, use the spanning-tree mst hello-time command. Use the no form of this command to return to the default settings.
spanning-tree mst hello-time seconds
no spanning-tree ms hello-time
Syntax Description
seconds
Number of seconds to set the hello-time delay timer for all the instances on the Catalyst 6500 series switch; valid values are from 1 to 10 seconds.
Defaults
2 seconds
Command Modes
Global configuration
Command History
Usage Guidelines
This command is not supported on systems configured with a Supervisor Engine 1.
If you do not specify the hello-time value, the value is calculated from the network diameter.
Examples
This example shows how to set the hello-time delay timer:
Router(config)# spanning-tree mst hello-time 3Router(config)#
Related Commands
spanning-tree mst max-age
To set the max-age timer for all the instances on the Catalyst 6500 series switch, use the spanning-tree mst max-age command. Use the no form of this command to return to the default settings.
spanning-tree mst max-age seconds
no spanning-tree mst max-age
Syntax Description
seconds
Number of seconds to set the max-age timer for all the instances on the Catalyst 6500 series switch; valid values are from 6 to 40 seconds.
Defaults
20 seconds
Command Modes
Global configuration
Command History
Usage Guidelines
This command is not supported on systems configured with a Supervisor Engine 1.
Examples
This example shows how to set the max-age:
Router(config)# spanning-tree mst max-age 40Router(config)#
Related Commands
spanning-tree mst max-hops
To specify the number of possible hops in the region before a BPDU is discarded, use the spanning-tree mst max-hops command. Use the no form of this command to return to the default settings.
spanning-tree mst max-hops hopnumber
no spanning-tree mst max-hops
Syntax Description
hopnumber
Number of possible hops in the region before a BPDU is discarded; valid values are from 1 to 40 hops.
Defaults
20 hops
Command Modes
Global configuration
Command History
Usage Guidelines
This command is not supported on systems configured with a Supervisor Engine 1.
Examples
This example shows how to set the max-hops:
Router(config)# spanning-tree mst max-hops 25Router(config)#
Related Commands
spanning-tree mst root
To designate the primary and secondary root, set the bridge priority, and set the timer value for an instance, use the spanning-tree mst root command. Use the no form of this command to return to the default settings.
spanning-tree mst instance-id {root {primary | secondary} | {priority prio}} [diameter dia] [hello-time hello-time]
no spanning-tree mst root
Syntax Description
Defaults
The defaults are as follows:
•
•
Command Modes
Global configuration
Command History
Usage Guidelines
This command is not supported on systems configured with a Supervisor Engine 1.
The bridge priority can
