-
Catalyst 4500 Series Switch Cisco IOS Command Reference, 12.2(54)SG
-
Quick Links to Catalyst 4500 Series Switch Cisco IOS Commands
-
Index
-
Preface
-
Command-Line Interface
-
aaa accounting dot1x default start-stop group radius through instance
-
interface port-channel through shape
-
show access-group mode interface through show vtp
-
snmp ifindex clear through vtp v2-mode
-
Acronyms and Abbreviations
-
Feedback
Table Of Contents
ip arp inspection limit (interface)
ip arp inspection vlan logging
ip dhcp snooping information option
ip dhcp snooping information option allow-untrusted
ip dhcp snooping vlan information option format-type circuit-id string
ip igmp snooping report-suppression
ip igmp snooping vlan explicit-tracking
ip igmp snooping vlan immediate-leave
ip verify unicast source reachable-via
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
l2protocol-tunnel drop-threshold
l2protocol-tunnel shutdown-threshold
lldp tlv-select power-management
logging event link-status global (global configuration)
logging event link-status (interface configuration)
logging event trunk-status global (global configuration)
logging event trunk-status (interface configuration)
mac-address-table dynamic group protocols
mac address-table learning vlan
mac-address-table notification
macro auto execute (built-in function)
macro auto execute (remotely-defined trigger)
macro auto execute (user-defined function)
macro global apply cisco-global
match (class-map configuration)
port-security mac-address sticky
pppoe intermediate-agent (global)
pppoe intermediate-agent (interface)
pppoe intermediate-agent (interface vlan-range)
pppoe intermediate-agent format-type (global)
pppoe intermediate-agent format-type (interface)
pppoe intermediate-agent format-type (interface vlan-range)
pppoe intermediate-agent limit rate
pppoe intermediate-agent trust
pppoe intermediate-agent vendor-tag strip
qos (global configuration mode)
qos (interface configuration mode)
qos account layer2 encapsulation
redundancy config-sync mismatched-commands
renew ip dhcp snooping database
service-policy (interface configuration)
service-policy (policy-map class)
service-policy input (control-plane)
shape (interface configuration)
interface
To select an interface to configure and to enter interface configuration mode, use the interface command.
interface type number
Syntax Description
type
Type of interface to be configured; see Table 2-6 for valid values.
number
Module and port number.
Defaults
No interface types are configured.
Command Modes
Global configuration mode
Command History
Usage Guidelines
Table 2-6 lists the valid values for type.
Table 2-6 Valid type Values
ethernet
Ethernet IEEE 802.3 interface.
fastethernet
100-Mbps Ethernet interface.
gigabitethernet
Gigabit Ethernet IEEE 802.3z interface.
tengigabitethernet
10-Gigabit Ethernet IEEE 802.3ae interface.
ge-wan
Gigabit Ethernet WAN IEEE 802.3z interface; supported on Catalyst 4500 series switches that are configured with a Supervisor Engine 2 only.
pos
Packet OC-3 interface on the Packet over SONET Interface Processor; supported on Catalyst 4500 series switches that are configured with a Supervisor Engine 2 only.
atm
ATM interface; supported on Catalyst 4500 series switches that are configured with a Supervisor Engine 2 only.
vlan
VLAN interface; see the interface vlan command.
port-channel
Port channel interface; see the interface port-channel command.
null
Null interface; the valid value is 0.
Examples
This example shows how to enter the interface configuration mode on the Fast Ethernet interface 2/4:
Switch(config)# interface fastethernet2/4Switch(config-if)#Related Commands
interface port-channel
To access or create a port-channel interface, use the interface port-channel command.
interface port-channel channel-group
Syntax Description
Defaults
This command has no default settings.
Command Modes
Global configuration mode
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
You do not have to create a port-channel interface before assigning a physical interface to a channel group. A port-channel interface is created automatically when the channel group gets its first physical interface, if it is not already created.
You can also create the port channels by entering the interface port-channel command. This will create a Layer 3 port channel. To change the Layer 3 port channel into a Layer 2 port channel, use the switchport command before you assign the physical interfaces to the channel group. A port channel cannot be changed from Layer 3 to Layer 2 or vice versa when it contains member ports.
Only one port channel in a channel group is allowed.
CautionThe Layer 3 port-channel interface is the routed interface. Do not enable Layer 3 addresses on the physical Fast Ethernet interfaces.
If you want to use CDP, you must configure it only on the physical Fast Ethernet interface and not on the port-channel interface.
Examples
This example creates a port-channel interface with a channel-group number of 64:
Switch(config)# interface port-channel 64Switch(config)#Related Commands
Assigns and configures an EtherChannel interface to an EtherChannel group.
Displays EtherChannel information for a channel.
interface range
To run a command on multiple ports at the same time, use the interface range command.
interface range {vlan vlan_id - vlan_id} {port-range | macro name}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Global configuration mode
Interface configuration mode
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4500 series switch.
12.1(12c)EW
Support for extended VLAN addresses added.
Usage Guidelines
You can use the interface range command on the existing VLAN SVIs only. To display the VLAN SVIs, enter the show running config command. The VLANs that are not displayed cannot be used in the interface range command.
The values that are entered with the interface range command are applied to all the existing VLAN SVIs.
Before you can use a macro, you must define a range using the define interface-range command.
All configuration changes that are made to a port range are saved to NVRAM, but the port ranges that are created with the interface range command do not get saved to NVRAM.
You can enter the port range in two ways:
•
•
You can either specify the ports or the name of a port-range macro. A port range must consist of the same port type, and the ports within a range cannot span the modules.
You can define up to five port ranges on a single command; separate each range with a comma.
When you define a range, you must enter a space between the first port and the hyphen (-):
interface range gigabitethernet 5/1 -20, gigabitethernet4/5 -20.Use these formats when entering the port-range:
•
•
Valid values for interface-type are as follows:
•
•
•
You cannot specify both a macro and an interface range in the same command. After creating a macro, you can enter additional ranges. If you have already entered an interface range, the CLI does not allow you to enter a macro.
You can specify a single interface in the port-range value. This makes the command similar to the interface interface-number command.
Examples
This example shows how to use the interface range command to interface to FE 5/18 - 20:
Switch(config)# interface range fastethernet 5/18 - 20Switch(config-if)#This command shows how to run a port-range macro:
Switch(config)# interface range macro macro1Switch(config-if)#Related Commands
Creates a macro of interfaces.
show running config (refer to Cisco IOS documentation)
Displays the running configuration for a switch.
interface vlan
To create or access a Layer 3 switch virtual interface (SVI), use the interface vlan command. To delete an SVI, use the no form of this command.
interface vlan vlan_id
no interface vlan vlan_id
Syntax Description
Defaults
Fast EtherChannel is not specified.
Command Modes
Global configuration mode
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4500 series switch.
12.1(12c)EW
Support for extended addressing was added.
Usage Guidelines
The SVIs are created the first time that you enter the interface vlan vlan_id command for a particular VLAN. The vlan_id value corresponds to the VLAN tag that is associated with the data frames on an ISL or 802.1Q-encapsulated trunk or the VLAN ID that is configured for an access port. A message is displayed whenever a VLAN interface is newly created, so you can check that you entered the correct VLAN number.
If you delete an SVI by entering the no interface vlan vlan_id command, the associated interface is forced into an administrative down state and marked as deleted. The deleted interface will no longer be visible in a show interface command.
You can reinstate a deleted SVI by entering the interface vlan vlan_id command for the deleted interface. The interface comes back up, but much of the previous configuration will be gone.
Examples
This example shows the output when you enter the interface vlan vlan_id command for a new VLAN number:
Switch(config)# interface vlan 23% Creating new VLAN interface.Switch(config)#ip arp inspection filter vlan
To permit ARPs from hosts that are configured for static IP when DAI is enabled and to define an ARP access list and apply it to a VLAN, use the ip arp inspection filter vlan command. To disable this application, use the no form of this command.
ip arp inspection filter arp-acl-name vlan vlan-range [static]
no ip arp inspection filter arp-acl-name vlan vlan-range [static]
Syntax Description
arp-acl-name
Access control list name.
vlan-range
VLAN number or range; valid values are from 1 to 4094.
static
(Optional) Specifies that the access control list should be applied statically.
Defaults
No defined ARP ACLs are applied to any VLAN.
Command Modes
Global configuration mode
Command History
12.1(19)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
When an ARP access control list is applied to a VLAN for dynamic ARP inspection, the ARP packets containing only the IP-to-Ethernet MAC bindings are compared against the ACLs. All other packet types are bridged in the incoming VLAN without validation.
This command specifies that the incoming ARP packets are compared against the ARP access control list, and the packets are permitted only if the access control list permits them.
If the access control lists deny the packets because of explicit denies, the packets are dropped. If the packets are denied because of an implicit deny, they are then matched against the list of DHCP bindings if the ACL is not applied statically.
Examples
This example shows how to apply the ARP ACL static hosts to VLAN 1 for DAI:
Switch# config terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# ip arp inspection filter static-hosts vlan 1Switch(config)# endSwitch#Switch# show ip arp inspection vlan 1Source Mac Validation : EnabledDestination Mac Validation : DisabledIP Address Validation : DisabledVlan Configuration Operation ACL Match Static ACL---- ------------- --------- --------- ----------1 Enabled Active static-hosts NoVlan ACL Logging DHCP Logging---- ----------- ------------1 Acl-Match DenySwitch#Related Commands
Defines an ARP access list or adds clauses at the end of a predefined list.
Displays the status of dynamic ARP inspection for a specific range of VLANs.
ip arp inspection limit (interface)
To limit the rate of incoming ARP requests and responses on an interface and prevent DAI from consuming all of the system's resources in the event of a DoS attack, use the ip arp inspection limit command. To release the limit, use the no form of this command.
ip arp inspection limit {rate pps | none} [burst interval seconds]
no ip arp inspection limit
Syntax Description
Defaults
The rate is set to 15 packets per second on the untrusted interfaces, assuming that the network is a switched network with a host connecting to as many as 15 new hosts per second.
The rate is unlimited on all the trusted interfaces.
The burst interval is set to 1 second by default.
Command Modes
Interface configuration mode
Command History
12.1(19)EW
Support for this command was introduced on the Catalyst 4500 series switch.
12.1(20)EW
Added support for interface monitoring.
Usage Guidelines
The trunk ports should be configured with higher rates to reflect their aggregation. When the rate of the incoming packets exceeds the user-configured rate, the interface is placed into an error-disabled state. The error-disable timeout feature can be used to remove the port from the error-disabled state. The rate applies to both the trusted and nontrusted interfaces. Configure appropriate rates on trunks to handle the packets across multiple DAI-enabled VLANs or use the none keyword to make the rate unlimited.
The rate of the incoming ARP packets onthe channel ports is equal to the sum of the incoming rate of packets from all the channel members. Configure the rate limit for the channel ports only after examining the rate of the incoming ARP packets on the channel members.
After a switch receives more than the configured rate of packets every second consecutively over a period of burst seconds, the interface is placed into an error-disabled state.
Examples
This example shows how to limit the rate of the incoming ARP requests to 25 packets per second:
Switch# config terminalSwitch(config)# interface fa6/3Switch(config-if)# ip arp inspection limit rate 25Switch(config-if)# endSwitch# show ip arp inspection interfaces fastEthernet 6/3Interface Trust State Rate (pps)--------------- ----------- ----------Fa6/3 Trusted 25Switch#This example shows how to limit the rate of the incoming ARP requests to 20 packets per second and to set the interface monitoring interval to 5 consecutive seconds:
Switch# config terminalSwitch(config)# interface fa6/1Switch(config-if)# ip arp inspection limit rate 20 burst interval 5Switch(config-if)# endRelated Commands
ip arp inspection log-buffer
To configure the parameters that are associated with the logging buffer, use the ip arp inspection log-buffer command. To disable the parameters, use the no form of this command.
ip arp inspection log-buffer {entries number | logs number interval seconds}
no ip arp inspection log-buffer {entries | logs}
Syntax Description
Defaults
When dynamic ARP inspection is enabled, denied, or dropped, the ARP packets are logged.
The number of entries is set to 32.
The number of logging entries is limited to 5 per second.
The interval is set to 1.
Command Modes
Global configuration mode
Command History
12.1(19)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
The first dropped packet of a given flow is logged immediately. The subsequent packets for the same flow are registered but are not logged immediately. Registering these packets is done in a log buffer that is shared by all the VLANs. Entries from this buffer are logged on a rate-controlled basis.
Examples
This example shows how to configure the logging buffer to hold up to 45 entries:
Switch# config terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# ip arp inspection log-buffer entries 45Switch(config)# endSwitch# show ip arp inspection logTotal Log Buffer Size : 45Syslog rate : 5 entries per 1 seconds.No entries in log buffer.Switch#This example shows how to configure the logging rate to 10 logs per 3 seconds:
Switch(config)# ip arp inspection log-buffer logs 10 interval 3Switch(config)# endSwitch# show ip arp inspection logTotal Log Buffer Size : 45Syslog rate : 10 entries per 3 seconds.No entries in log buffer.Switch#Related Commands
Defines an ARP access list or adds clauses at the end of a predefined list.
Displays the status of dynamic ARP inspection for a specific range of VLANs.
ip arp inspection trust
To set a per-port configurable trust state that determines the set of interfaces where incoming ARP packets are inspected, use the ip arp inspection trust command. To make the interfaces untrusted, use the no form of this command.
ip arp inspection trust
no ip arp inspection trust
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Interface configuration mode
Command History
12.1(19)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Examples
This example shows how to configure an interface to be trusted:
Switch# config terminalSwitch(config)# interface fastEthernet 6/3Switch(config-if)# ip arp inspection trustSwitch(config-if)# endTo verify the configuration, use the show form of this command:
Switch# show ip arp inspection interfaces fastEthernet 6/3Interface Trust State Rate (pps) Burst Interval--------------- ----------- ---------- --------------Fa6/3 Trusted None 1Switch#Related Commands
ip arp inspection validate
To perform specific checks for ARP inspection, use the ip arp inspection validate command. To disable checks, use the no form of this command.
ip arp inspection validate [src-mac] [dst-mac] [ip]
no ip arp inspection validate [src-mac] [dst-mac] [ip]
Syntax Description
Defaults
Checks are disabled.
Command Modes
Global configuration mode
Command History
12.1(19)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
When enabling the checks, specify at least one of the keywords (src-mac, dst-mac, and ip) on the command line. Each command overrides the configuration of the previous command. If a command enables src and dst mac validations, and a second command enables IP validation only, the src and dst mac validations are disabled as a result of the second command.
The no form of this command disables only the specified checks. If none of the check options are enabled, all the checks are disabled.
Examples
This example show how to enable the source MAC validation:
Switch(config)# ip arp inspection validate src-macSwitch(config)# endSwitch# show ip arp inspection vlan 1Source Mac Validation : EnabledDestination Mac Validation : DisabledIP Address Validation : DisabledVlan Configuration Operation ACL Match Static ACL---- ------------- --------- --------- ----------1 Enabled ActiveVlan ACL Logging DHCP Logging---- ----------- ------------1 Deny DenySwitch#Related Commands
Defines an ARP access list or adds clauses at the end of a predefined list.
Displays the status of dynamic ARP inspection for a specific range of VLANs.
ip arp inspection vlan
To enable dynamic ARP inspection (DAI) on a per-VLAN basis, use the ip arp inspection vlan command. To disable DAI, use the no form of this command.
ip arp inspection vlan vlan-range
no ip arp inspection vlan vlan-range
Syntax Description
Defaults
ARP inspection is disabled on all VLANs.
Command Modes
Global configuration mode
Command History
12.1(19)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
You must specify on which VLANs to enable DAI. DAI may not function on the configured VLANs if they have not been created or if they are private.
Examples
This example shows how to enable DAI on VLAN 1:
Switch# configure terminalSwitch(config)# ip arp inspection vlan 1Switch(config)# endSwitch# show ip arp inspection vlan 1Source Mac Validation : DisabledDestination Mac Validation : DisabledIP Address Validation : DisabledVlan Configuration Operation ACL Match Static ACL---- ------------- --------- --------- ----------1 Enabled ActiveVlan ACL Logging DHCP Logging---- ----------- ------------1 Deny DenySwitch#This example shows how to disable DAI on VLAN 1:
Switch# configure terminalSwitch(config)# no ip arp inspection vlan 1Switch(config)#Related Commands
Defines an ARP access list or adds clauses at the end of a predefined list.
Displays the status of dynamic ARP inspection for a specific range of VLANs.
ip arp inspection vlan logging
To control the type of packets that are logged, use the ip arp inspection vlan logging command. To disable this logging control, use the no form of this command.
ip arp inspection vlan vlan-range logging {acl-match {matchlog | none} | dhcp-bindings {permit | all | none}}
no ip arp inspection vlan vlan-range logging {acl-match | dhcp-bindings}
Syntax Description
Defaults
All denied or dropped packets are logged.
Command Modes
Global configuration mode
Command History
12.1(19)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
The acl-match and dhcp-bindings keywords merge with each other. When you set an ACL match configuration, the DHCP bindings configuration is not disabled. You can use the no form of this command to reset some of the logging criteria to their defaults. If you do not specify either option, all the logging types are reset to log on when the ARP packets are denied. The two options that are available to you are as follows:
•
•
Examples
This example shows how to configure an ARP inspection on VLAN 1 to add packets to a log on matching against the ACLs with the logging keyword:
Switch# config terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# ip arp inspection vlan 1 logging acl-match matchlogSwitch(config)# endSwitch# show ip arp inspection vlan 1Source Mac Validation : EnabledDestination Mac Validation : DisabledIP Address Validation : DisabledVlan Configuration Operation ACL Match Static ACL---- ------------- --------- --------- ----------1 Enabled ActiveVlan ACL Logging DHCP Logging---- ----------- ------------1 Acl-Match DenySwitch#Related Commands
Defines an ARP access list or adds clauses at the end of a predefined list.
Displays the status of dynamic ARP inspection for a specific range of VLANs.
ip cef load-sharing algorithm
To configure the load-sharing hash function so that the source TCP/UDP port, the destination TCP/UDP port, or both ports can be included in the hash in addition to the source and destination IP addresses, use the ip cef load-sharing algorithm command. To revert back to the default, which does not include the ports, use the no form of this command.
ip cef load-sharing algorithm {include-ports {source source | destination dest} | original | tunnel | universal}
no ip cef load-sharing algorithm {include-ports {source source | destination dest} | original | tunnel | universal}
Syntax Description
Defaults
Default load-sharing algorithm is disabled.
Note
Command Modes
Global configuration mode
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
The original algorithm, tunnel algorithm, and universal algorithm are routed through the hardware. For software-routed packets, the algorithms are handled by the software. The include-ports option does not apply to the software-switched traffic.
Examples
This example shows how to configure the IP CEF load-sharing algorithm that includes Layer 4 ports:
Switch(config)# ip cef load-sharing algorithm include-portsSwitch(config)#This example shows how to configure the IP CEF load-sharing algorithm that includes Layer 4 tunneling ports:
Switch(config)# ip cef load-sharing algorithm include-ports tunnelSwitch(config)#Related Commands
ip device tracking maximum
To enable IP port security binding tracking on a Layer 2 port, use the ip device tracking maximum command. To disable IP port security on untrusted Layer 2 interfaces, use the no form of this command.
ip device tracking maximum {number}
no ip device tracking maximum {number}
Syntax Description
number
Specifies the number of bindings created in the IP device tracking table for a port, valid values are from 0 to 2048.
Defaults
This command has no default settings.
Command Modes
Interface configuration mode
Command History
12.2(37)SG
Support for this command was introduced on the Catalyst 4500 series switch.
Examples
This example shows how to enable IP port security with IP-MAC filters on a Layer 2 access port:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# ip device trackingSwitch(config)# interface fastethernet 4/3Switch(config-if)# switchport mode accessSwitch(config-if)# switchport access vlan 1Switch(config-if)# ip device tracking maximum 5Switch(config-if)# switchport port-securitySwitch(config-if)# switchport port-security maximum 5Switch(config-if)# ip verify source tracking port-securitySwitch(config-if)# endYou can verify your settings by entering the show ip verify source privileged EXEC command.
Related Commands
Enables IP source guard on untrusted Layer 2 interfaces.
Displays the IP source guard configuration and filters on a particular interface.
ip dhcp snooping
To enable DHCP snooping globally, use the ip dhcp snooping command. To disable DHCP snooping, use the no form of this command.
ip dhcp snooping
no ip dhcp snooping
Syntax Description
This command has no arguments or keywords.
Defaults
DHCP snooping is disabled.
Command Modes
Global configuration mode
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
You must enable DHCP snooping globally before you can use DHCP snooping on a VLAN.
Examples
This example shows how to enable DHCP snooping:
Switch(config)# ip dhcp snoopingSwitch(config)#This example shows how to disable DHCP snooping:
Switch(config)# no ip dhcp snoopingSwitch(config)#Related Commands
ip dhcp snooping binding
To set up and generate a DHCP binding configuration to restore bindings across reboots, use the ip dhcp snooping binding command. To disable the binding configuration, use the no form of this command.
ip dhcp snooping binding mac-address vlan vlan-# ip-address interface interface expiry seconds
no ip dhcp snooping binding mac-address vlan vlan-# ip-address interface interface
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC mode
Command History
Usage Guidelines
Whenever a binding is added or removed using this command, the binding database is marked as changed and a write is initiated.
Examples
This example shows how to generate a DHCP binding configuration on interface gigabitethernet1/1 in VLAN 1 with an expiration time of 1000 seconds:
Switch# ip dhcp snooping binding 0001.1234.1234 vlan 1 172.20.50.5 interface gi1/1 expiry 1000Switch#Related Commands
ip dhcp snooping database
To store the bindings that are generated by DHCP snooping, use the ip dhcp snooping database command. To either reset the timeout, reset the write-delay, or delete the agent specified by the URL, use the no form of this command.
ip dhcp snooping database {url | timeout seconds | write-delay seconds}
no ip dhcp snooping database {timeout | write-delay}
Syntax Description
Defaults
The timeout value is set to 300 seconds (5 minutes).
The write-delay value is set to 300 seconds.
Command Modes
Interface configuration mode
Command History
12.1(19)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
You need to create an empty file at the configured URL on network-based URLs (such as TFTP and FTP) before the switch can write the set of bindings for the first time at the URL.
Note
Examples
This example shows how to store a database file with the IP address 10.1.1.1 within a directory called directory. A file named file must be present on the TFTP server.
Switch# config terminalSwitch(config)# ip dhcp snooping database tftp://10.1.1.1/directory/fileSwitch(config)# endSwitch# show ip dhcp snooping databaseAgent URL : tftp://10.1.1.1/directory/fileWrite delay Timer : 300 secondsAbort Timer : 300 secondsAgent Running : YesDelay Timer Expiry : Not RunningAbort Timer Expiry : Not RunningLast Succeded Time : NoneLast Failed Time : NoneLast Failed Reason : No failure recorded.Total Attempts : 1 Startup Failures : 0Successful Transfers : 0 Failed Transfers : 0Successful Reads : 0 Failed Reads : 0Successful Writes : 0 Failed Writes : 0Media Failures : 0Switch#Related Commands
ip dhcp snooping information option
To enable DHCP option 82 data insertion, use the ip dhcp snooping information option command. To disable DHCP option 82 data insertion, use the no form of this command.
ip dhcp snooping information option format remote-id {hostname | string {word}}
no ip dhcp snooping information option format remote-id {hostname | string {word}}
Syntax Description
Defaults
DHCP option 82 data insertion is enabled.
Command Modes
Global configuration mode
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4500 series switch.
12.2(40)SG
Added remote-id keyword to support option 82 enhancement.
Usage Guidelines
If the hostname is longer than 63 characters it is truncated to 63 characters in the remote ID.
Examples
This example shows how to enable DHCP option 82 data insertion:
Switch(config)# ip dhcp snooping information optionSwitch(config)#This example shows how to disable DHCP option 82 data insertion:
Switch(config)# no ip dhcp snooping information optionSwitch(config)#This example shows how to configure the hostname as the remote ID:
Switch(config)# ip dhcp snooping information option format remote-id hostnameSwitch(config)#The following example shows how to enable DHCP Snooping on VLAN 500 through 555 and option 82 remote ID:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# ip dhcp snoopingSwitch(config)# ip dhcp snooping vlan 500 555Switch(config)# ip dhcp snooping information option format remote-id string switch123Switch(config)# interface GigabitEthernet 5/1Switch(config-if)# ip dhcp snooping trustSwitch(config-if)# ip dhcp snooping limit rate 100Switch(config-if)# ip dhcp snooping vlan 555 information option format-type circuit-id string customer-555Switch(config-if)# interface FastEthernet 2/1Switch(config-if)# ip dhcp snooping vlan 555 information option format-type circuit-id string customer-500Switch(config)# endRelated Commands
Globally enables DHCP snooping.
Sets up and generates a DHCP binding configuration to restore bindings across reboots.
Enables DHCP option 82 data insertion.
Configures the number of the DHCP messages that an interface can receive per second.
Enables DHCP snooping on a trusted VLAN.
Enables DHCP snooping on a VLAN or a group of VLANs.
ip dhcp snooping vlan information option format-type circuit-id string
Enables circuit-id (a sub-option of DHCP snooping option-82) on a VLAN.
Displays the DHCP snooping configuration.
Displays the DHCP snooping binding entries.
ip dhcp snooping information option allow-untrusted
To allow DHCP packets with option 82 data inserted to be received from a snooping untrusted port, use the ip dhcp snooping information option allow-untrusted command. To disallow receipt of these DHCP packets, use the no form of this command.
ip dhcp snooping information option allow-untrusted
no ip dhcp snooping information option allow-untrusted
Syntax Description
This command has no arguments or keywords.
Defaults
DHCP packets with option 82 are not allowed on snooping untrusted ports.
Command Modes
Global configuration mode
Command History
12.2(25)EWA
Support for this command was introduced on the Catalyst 4500 series switch.
Examples
This example shows how to allow DHCP packets with option 82 data inserted to be received from a snooping untrusted port:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# ip dhcp snooping information option allow-untrustedSwitch(config)#endSwitch#Related Commands
ip dhcp snooping limit rate
To configure the number of the DHCP messages that an interface can receive per second, use the ip dhcp snooping limit rate command. To disable the DHCP snooping rate limiting, use the no form of this command.
ip dhcp snooping limit rate rate
no ip dhcp snooping limit rate
Syntax Description
Defaults
DHCP snooping rate limiting is disabled.
Command Modes
Interface configuration mode
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
Typically, the rate limit applies to the untrusted interfaces. If you want to set up rate limiting for the trusted interfaces, note that the trusted interfaces aggregate all DHCP traffic in the switch, and you will need to adjust the rate limit of the interfaces to a higher value.
Examples
This example shows how to enable the DHCP message rate limiting:
Switch(config-if)# ip dhcp snooping limit rate 150Switch(config)#This example shows how to disable the DHCP message rate limiting:
Switch(config-if)# no ip dhcp snooping limit rateSwitch(config)#Related Commands
ip dhcp snooping trust
To configure an interface as trusted for DHCP snooping purposes, use the ip dhcp snooping trust command. To configure an interface as untrusted, use the no form of this command.
ip dhcp snooping trust
no ip dhcp snooping trust
Syntax Description
This command has no arguments or keywords.
Defaults
DHCP snooping trust is disabled.
Command Modes
Interface configuration mode
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Examples
This example shows how to enable DHCP snooping trust on an interface:
Switch(config-if)# ip dhcp snooping trustSwitch(config)#This example shows how to disable DHCP snooping trust on an interface:
Switch(config-if)# no ip dhcp snooping trustSwitch(config)#Related Commands
ip dhcp snooping vlan
Use the ip dhcp snooping vlan command to enable DHCP snooping on a VLAN. To disable DHCP snooping on a VLAN, use the no form of this command.
ip dhcp snooping [vlan number]
no ip dhcp snooping [vlan number]
Syntax Description
Defaults
DHCP snooping is disabled.
Command Modes
Global configuration mode
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
DHCP snooping is enabled on a VLAN only if both global snooping and the VLAN snooping are enabled.
Examples
This example shows how to enable DHCP snooping on a VLAN:
Switch(config)# ip dhcp snooping vlan 10Switch(config)#This example shows how to disable DHCP snooping on a VLAN:
Switch(config)# no ip dhcp snooping vlan 10Switch(config)#This example shows how to enable DHCP snooping on a group of VLANs:
Switch(config)# ip dhcp snooping vlan 10 55Switch(config)#This example shows how to disable DHCP snooping on a group of VLANs:
Switch(config)# no ip dhcp snooping vlan 10 55Switch(config)#Related Commands
Globally enables DHCP snooping.
Enables DHCP option 82 data insertion.
Configures the number of the DHCP messages that an interface can receive per second.
Enables DHCP snooping on a trusted VLAN.
ip dhcp snooping vlan information option format-type circuit-id string
Enables circuit-id (a suboption of DHCP snooping option-82) on a VLAN.
Displays the DHCP snooping configuration.
Displays the DHCP snooping binding entries.
ip dhcp snooping vlan information option format-type circuit-id string
To enable circuit-id (a suboption of DHCP snooping option 82) on a VLAN, use the ip dhcp snooping vlan information option format-type circuit-id string command. To disable circuit-id on a VLAN, use the no form of this command.
ip dhcp snooping vlan number information option format-type circuit-id [override] string string
no ip dhcp snooping vlan number information option format-type circuit-id [override] string
Syntax Description
Defaults
VLAN-mod-port, if DHCP snooping option-82 is disabled.
Command Modes
Interface configuration
Command History
12.2(40)SG
Support for this command was introduced on the Catalyst 4500 series switch.
12.2(54)SG
Added the override option
Usage Guidelines
The circuit-id suboption of DHCP option 82 is supported only when DHCP snooping is globally enabled and on VLANs using DHCP option 82.
This command allows you to configure a string of ASCII characters to be the circuit ID. When you want to override the vlan-mod-port format type and instead use the circuit-ID to define subscriber information, use the override keyword.
Examples
The following example shows how to enable DHCP snooping on VLAN 500 through 555 and option 82 circuit-id:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# ip dhcp snoopingSwitch(config)# ip dhcp snooping vlan 500 555Switch(config)# ip dhcp snooping information option format remote-id string switch123Switch(config)# interface GigabitEthernet 5/1Switch(config-if)# ip dhcp snooping trustSwitch(config-if)# ip dhcp snooping limit rate 100Switch(config-if)# ip dhcp snooping vlan 555 information option format-type circuit-id string customer-555Switch(config-if)# interface FastEthernet 2/1Switch(config-if)# ip dhcp snooping vlan 555 information option format-type circuit-id string customer-500Switch(config)# endThis example shows how to configure the option-82 circuit-ID override suboption:
Switch(config-if)# ip dhcp snooping vlan 250 information option format-type circuit-idoverride string testcustomerYou can verify your settings by entering the show ip dhcp snooping user EXEC command.
Note
Related Commands
ip igmp filter
To control whether all hosts on a Layer 2 interface can join one or more IP multicast groups by applying an IGMP profile to the interface, use the ip igmp filter command. To remove a profile from the interface, use the no form of this command.
ip igmp filter profile number
no ip igmp filter
Syntax Description
Defaults
Profiles are not applied.
Command Modes
Interface configuration mode
Command History
12.1(11b)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
You can apply IGMP filters only to Layer 2 physical interfaces; you cannot apply IGMP filters to routed ports, switch virtual interfaces (SVIs), or ports that belong to an EtherChannel group.
An IGMP profile can be applied to one or more switch port interfaces, but one port can have only one profile applied to it.
Examples
This example shows how to apply IGMP profile 22 to an interface:
Switch(config)# interface gigabitethernet1/1Switch(config-if)# ip igmp filter 22Switch(config-if)#Related Commands
Creates an IGMP profile.
Displays all configured IGMP profiles or a specified IGMP profile.
ip igmp max-groups
To set the maximum number of IGMP groups that a Layer 2 interface can join, use the ip igmp max-groups command. To set the maximum back to the default, use the no form of this command.
ip igmp max-groups number
no ip igmp max-groups
Syntax Description
number
Maximum number of IGMP groups that an interface can join; valid values are from 0 to 4294967294.
Defaults
No maximum limit.
Command Modes
Interface configuration mode
Command History
12.1(11b)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
You can use the ip igmp max-groups command only on Layer 2 physical interfaces; you cannot set the IGMP maximum groups for the routed ports, the switch virtual interfaces (SVIs), or the ports that belong to an EtherChannel group.
Examples
This example shows how to limit the number of IGMP groups that an interface can join to 25:
Switch(config)# interface gigabitethernet1/1Switch(config-if)# ip igmp max-groups 25Switch(config-if)ip igmp profile
To create an IGMP profile, use the ip igmp profile command. To delete the IGMP profile, use the no form of this command.
ip igmp profile profile number
no ip igmp profile profile number
Syntax Description
Defaults
No profile created.
Command Modes
Global configuration mode
IGMP profile configuration
Command History
12.1(11b)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
When entering a range, enter the low IP multicast address, a space, and the high IP multicast address.
You can apply an IGMP profile to one or more Layer 2 interfaces, but each interface can have only one profile applied to it.
Examples
This example shows how to configure IGMP profile 40 that permits the specified range of IP multicast addresses:
Switch # config terminalSwitch(config)# ip igmp profile 40Switch(config-igmp-profile)# permitSwitch(config-igmp-profile)# range 233.1.1.1 233.255.255.255Switch(config-igmp-profile)#Related Commands
ip igmp query-interval
To configure the frequency that the switch sends the IGMP host-query messages, use the ip igmp query-interval command. To return to the default frequency, use the no form of this command.
ip igmp query-interval seconds
no ip igmp query-interval
Syntax Description
seconds
Frequency, in seconds, at which the IGMP host-query messages are transmitted; valid values depend on the IGMP snooping mode. See the "Usage Guidelines" section for more information.
Defaults
The query interval is set to 60 seconds.
Command Modes
Interface configuration mode
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
If you use the default IGMP snooping configuration, the valid query interval values are from 1 to 65535 seconds. If you have changed the default configuration to support CGMP as the IGMP snooping learning method, the valid query interval values are from 1 to 300 seconds.
The designated switch for a LAN is the only switch that sends the IGMP host-query messages. For IGMP version 1, the designated switch is elected according to the multicast routing protocol that runs on the LAN. For IGMP version 2, the designated querier is the lowest IP-addressed multicast switch on the subnet.
If no queries are heard for the timeout period (controlled by the ip igmp query-timeout command), the switch becomes the querier.
Note
Examples
This example shows how to change the frequency at which the designated switch sends the IGMP host-query messages:
Switch(config-if)#ip igmp query-interval 120Switch(config-if)#Related Commands
ip igmp snooping
To enable IGMP snooping, use the ip igmp snooping command. To disable IGMP snooping, use the no form of this command.
ip igmp snooping [tcn {flood query count count | query solicit}]
no ip igmp snooping [tcn {flood query count count | query solicit}]
Syntax Description
Defaults
IGMP snooping is enabled.
Command Modes
Global configuration mode
Interface configuration mode
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4500 series switch.
12.1(11)EW
Support for flooding the spanning tree table was added.
Usage Guidelines
The tcn flood option applies only to Layer 2 switch ports and EtherChannels; it does not apply to routed ports, VLAN interfaces, or Layer 3 channels.
The ip igmp snooping command is disabled by default on multicast routers.
Note
Examples
This example shows how to enable IGMP snooping:
Switch(config)#ip igmp snoopingSwitch(config)#This example shows how to disable IGMP snooping:
Switch(config)#no ip igmp snoopingSwitch(config)#This example shows how to enable the flooding of the spanning tree table to the network after nine topology changes have occurred:
Switch(config)#ip igmp snooping tcn flood query count 9Switch(config)#This example shows how to disable the flooding of the spanning tree table to the network:
Switch(config)#no ip igmp snooping tcn floodSwitch(config)#This example shows how to enable an IGMP general query:
Switch(config)#ip igmp snooping tcn query solicitSwitch(config)#This example shows how to disable an IGMP general query:
Switch(config)#no ip igmp snooping tcn query solicitSwitch(config)#Related Commands
Enable IGMP immediate-leave processing.
Configures a Layer 2 interface as a multicast router interface for a VLAN.
Configures a Layer 2 interface as a member of a group.
ip igmp snooping report-suppression
To enable report suppression, use the ip igmp snooping report-suppression command. To disable report suppression and forward the reports to the multicast devices, use the no form of this command.
ip igmp snooping report-suppression
no igmp snooping report-suppression
Syntax Description
This command has no arguments or keywords.
Defaults
IGMP snooping report-suppression is enabled.
Command Modes
Global configuration mode
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
If the ip igmp snooping report-suppression command is disabled, all the IGMP reports are forwarded to the multicast devices.
If the command is enabled, report suppression is done by IGMP snooping.
Examples
This example shows how to enable report suppression:
Switch(config)#ip igmp snooping report-suppressionSwitch(config)#This example shows how to disable report suppression:
Switch(config)#no ip igmp snooping report-suppressionSwitch(config)#This example shows how to display the system status for report suppression:
Switch#show ip igmp snoopvlan 1----------IGMP snooping is globally enabledIGMP snooping TCN solicit query is globally disabledIGMP snooping global TCN flood query count is 2IGMP snooping is enabled on this VlanIGMP snooping immediate-leave is disabled on this VlanIGMP snooping mrouter learn mode is pim-dvmrp on this VlanIGMP snooping is running in IGMP_ONLY mode on this VlanIGMP snooping report suppression is enabled on this VlanSwitch#Related Commands
Enable IGMP immediate-leave processing.
Configures a Layer 2 interface as a multicast router interface for a VLAN.
Configures a Layer 2 interface as a member of a group.
ip igmp snooping vlan
To enable IGMP snooping for a VLAN, use the ip igmp snooping vlan command. To disable IGMP snooping, use the no form of this command.
ip igmp snooping vlan vlan-id
no ip igmp snooping vlan vlan-id
Syntax Description
Defaults
IGMP snooping is disabled.
Command Modes
Global configuration mode
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4500 series switch.
12.1(12c)EW
Support for extended addressing was added.
Usage Guidelines
This command is entered in VLAN interface configuration mode only.
The ip igmp snooping vlan command is disabled by default on multicast routers.
Examples
This example shows how to enable IGMP snooping on a VLAN:
Switch(config)#ip igmp snooping vlan 200Switch(config)#This example shows how to disable IGMP snooping on a VLAN:
Switch(config)#no ip igmp snooping vlan 200Switch(config)#Related Commands
Enable IGMP immediate-leave processing.
Configures a Layer 2 interface as a multicast router interface for a VLAN.
Configures a Layer 2 interface as a member of a group.
ip igmp snooping vlan explicit-tracking
To enable per-VLAN explicit host tracking, use the ip igmp snooping vlan explicit-tracking command. To disable explicit host tracking, use the no form of this command.
ip igmp snooping vlan vlan-id explicit-tracking
no ip igmp snooping vlan vlan-id explicit-tracking
Syntax Description
Defaults
Explicit host tracking is enabled.
Command Modes
Global configuration mode
Command History
12.1(20)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Examples
This example shows how to disable IGMP explicit host tracking on interface VLAN 200 and how to verify the configuration:
Switch(config)# no ip igmp snooping vlan 200 explicit-trackingSwitch(config)# endSwitch# show ip igmp snooping vlan 200 | include explicit trackingGlobal IGMP Snooping configuration:-----------------------------------IGMP snooping : EnabledIGMPv3 snooping : EnabledReport suppression : EnabledTCN solicit query : DisabledTCN flood query count : 2Vlan 2:--------IGMP snooping : EnabledIGMPv2 immediate leave : DisabledExplicit host tracking : DisabledMulticast router learning mode : pim-dvmrpCGMP interoperability mode : IGMP_ONLYExplicit host tracking : DisabledSwitch#Related Commands
ip igmp snooping vlan immediate-leave
To enable IGMP immediate-leave processing, use the ip igmp snooping vlan immediate-leave command. To disable immediate-leave processing, use the no form of this command.
ip igmp snooping vlan vlan_num immediate-leave
no ip igmp snooping vlan vlan_num immediate-leave
Syntax Description
vlan_num
Number of the VLAN; valid values are from 1 to 4094.
immediate-leave
Enables immediate leave processing.
Defaults
Immediate leave processing is disabled.
Command Modes
Global configuration mode
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4500 series switch.
12.1(12c)EW
Support for extended addressing was added.
Usage Guidelines
You enter this command in global configuration mode only.
Use the immediate-leave feature only when there is a single receiver for the MAC group for a specific VLAN.
The immediate-leave feature is supported only with IGMP version 2 hosts.
Examples
This example shows how to enable IGMP immediate-leave processing on VLAN 4:
Switch(config)#ip igmp snooping vlan 4 immediate-leaveSwitch(config)#This example shows how to disable IGMP immediate-leave processing on VLAN 4:
Switch(config)#no ip igmp snooping vlan 4 immediate-leaveSwitch(config)#Related Commands
ip igmp snooping vlan mrouter
To statically configure an Layer 2 interface as a multicast router interface for a VLAN, use the
ip igmp snooping vlan mrouter command. To remove the configuration, use the no form of this command.ip igmp snooping vlan vlan-id mrouter {interface {{fastethernet slot/port} | {gigabitethernet slot/port} | {tengigabitethernet slot/port} | {port-channel number}} |
{learn {cgmp | pim-dvmrp}}no ip igmp snooping vlan vlan-id mrouter {interface {{fastethernet slot/port} | {gigabitethernet slot/port} | {tengigabitethernet slot/port} | {port-channel number}} |
{learn {cgmp | pim-dvmrp}}Syntax Description
Defaults
Multicast switch snooping PIM-DVMRP packets are specified.
Command Modes
Interface configuration mode
Command History
Usage Guidelines
You enter this command in VLAN interface configuration mode only.
The interface to the switch must be in the VLAN where you are entering the command. It must be both administratively up and line protocol up.
The CGMP learning method can decrease control traffic.
The learning method that you configure is saved in NVRAM.
The static connections to multicast interfaces are supported only on switch interfaces.
Examples
This example shows how to specify the next-hop interface to a multicast switch:
Switch(config-if)#ip igmp snooping 400 mrouter interface fastethernet 5/6Switch(config-if)#This example shows how to specify the multicast switch learning method:
Switch(config-if)#ip igmp snooping 400 mrouter learn cgmpSwitch(config-if)#Related Commands
ip igmp snooping vlan static
To configure a Layer 2 interface as a member of a group, use the ip igmp snooping vlan static command. To remove the configuration, use the no form of this command.
ip igmp snooping vlan vlan_num static mac-address {interface {fastethernet slot/port} | {gigabitethernet slot/port} | {tengigabitethernet slot/port} | {port-channel number}}
no ip igmp snooping vlan vlan_num static mac-address {interface {fastethernet slot/port} | {gigabitethernet slot/port} | {tengigabitethernet mod/interface-number} | {port-channel number}}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Global configuration mode
Command History
Examples
This example shows how to configure a host statically on an interface:
Switch(config)#ip igmp snooping vlan 4 static 0100.5e02.0203 interface fastethernet 5/11Configuring port FastEthernet5/11 on group 0100.5e02.0203 vlan 4Switch(config)#Related Commands
ip local-proxy-arp
To enable the local proxy ARP feature, use the ip local-proxy-arp command. To disable the local proxy ARP feature, use the no form of this command.
ip local-proxy-arp
no ip local-proxy-arp
Syntax Description
This command has no arguments or keywords.
Defaults
Local proxy ARP is disabled.
Command Modes
Interface configuration mode
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
Use this feature only on subnets where hosts are intentionally prevented from communicating directly to the switch on which they are connected.
ICMP redirect is disabled on interfaces where the local proxy ARP feature is enabled.
Examples
This example shows how to enable the local proxy ARP feature:
Switch(config-if)#ip local-proxy-arpSwitch(config-if)#ip mfib fastdrop
To enable MFIB fast drop, use the ip mfib fastdrop command. To disable MFIB fast drop, use the no form of this command.
ip mfib fastdrop
no ip mfib fastdrop
Syntax Description
This command has no arguments or keywords.
Defaults
MFIB fast drop is enabled.
Command Modes
Privileged EXEC mode
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Examples
This example shows how to enable MFIB fast drops:
Switch# ip mfib fastdropSwitch#Related Commands
Clears all the MFIB fast-drop entries.
Displays all currently active fast-drop entries and shows whether fast drop is enabled.
ip multicast multipath
To enable load splitting of IP multicast traffic over Equal Cost Multipath (ECMP), use the
ip multicast multipath command in global configuration mode. To disable this functionality, use the no form of this command.ip multicast [vrf vrf-name] multipath [s-g-hash {basic | next-hop-based}]
no ip multicast [vrf vrf-name] multipath [s-g-hash {basic | next-hop-based}]
Syntax Description
Command Default
If multiple equal-cost paths exist, multicast traffic will not be load-split across those paths.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
The ip multicast multipath command does not work with bidirectional Protocol Independent Multicast (PIM).
Use the ip multicast multipath command to enable load splitting of IP multicast traffic across multiple equal-cost paths.
If two or more equal-cost paths from a source are available, unicast traffic will be load-split across those paths. However, by default, multicast traffic is not load-split across multiple equal-cost paths. In general, multicast traffic flows down from the reverse path forwarding (RPF) neighbor. According to the PIM specifications, this neighbor must have the highest IP address if more than one neighbor has the same metric.
When you configue load splitting with the ip multicast multipath command, the system splits multicast traffic across multiple equal-cost paths based on source address using the S-hash algorithm. When the ip multicast multipath command is configured and multiple equal-cost paths exist, the path in which multicast traffic will travel is selected based on the source IP address. Multicast traffic from different sources will be load-split across the different equal-cost paths. Load splitting will not occur across equal-cost paths for multicast traffic from the same source sent to different multicast groups.
Note
If the ip multicast multipath command is configured with the s-g-hash keyword and multiple equal-cost paths exist, load splitting will occur across equal-cost paths based on source and group address or on source, group, and next-hop address. If you specify the optional s-g-hash keyword for load splitting IP multicast traffic, you must select the algorithm used to calculate the equal-cost paths by specifying one of the following keywords:
•
•
Examples
The following example shows how to enable ECMP multicast load splitting on a router based on source address using the S-hash algorithm:
Switch(config)# ip multicast multipathThe following example shows how to enable ECMP multicast load splitting on a router based on source and group address using the basic S-G-hash algorithm:
Switch(config)# ip multicast multipath s-g-hash basicThe following example shows how to enable ECMP multicast load splitting on a router based on source, group, and next-hop address using the next-hop-based S-G-hash algorithm:
Switch(config)# ip multicast multipath s-g-hash next-hop-basedip route-cache flow
To enable NetFlow statistics for IP routing, use the ip route-cache flow command. To disable NetFlow statistics, use the no form of this command.
ip route-cache flow [infer-fields]
no ip route-cache flow [infer-fields]
Syntax Description
infer-fields
(Optional) Includes the NetFlow fields as inferred by the software: Input identifier, Output identifier, and Routing information.
Defaults
NetFlow statistics is disabled.
Inferred information is excluded.
Command Modes
Global configuration mode
Command History
12.1(13)EW
Support for this command was introduced on the Catalyst 4500 series switches.
12.1(19)EW
Command enhanced to support infer fields.
Usage Guidelines
To use these commands, you need to install the Supervisor Engine IV and the NetFlow Service Card.
The NetFlow statistics feature captures a set of traffic statistics. These traffic statistics include the source IP address, destination IP address, Layer 4 port information, protocol, input and output identifiers, and other routing information that can be used for network analysis, planning, accounting, billing and identifying DoS attacks.
NetFlow switching is supported on IP and IP-encapsulated traffic over all interface types.
If you enter the ip route-cache flow infer-fields command after the ip route-cache flow command, you will purge the existing cache, and vice versa. This action is done to avoid having flows with and without inferred fields in the cache simultaneously.
For additional information on NetFlow switching, refer to the Catalyst 4500 Series Switch Cisco IOS Software Configuration Guide.
Note
Examples
This example shows how to enable NetFlow switching on the switch:
Switch# config terminalSwitch(config)# ip route-cache flowSwitch(config)# exitSwitch#
Note
ip source binding
To add or delete a static IP source binding entry, use the ip source binding command. To delete the corresponding IP source binding entry, use the no form of this command.
ip source binding ip-address mac-address vlan vlan-id interface interface-name
no ip source binding ip-address mac-address vlan vlan-id interface interface-name
Syntax Description
ip-address
Binding IP address.
mac-address
Binding MAC address.
vlan vlan-id
VLAN number.
interface interface-name
Binding interface.
Defaults
This command has no default settings.
Command Modes
Global configuration mode
Command History
12.1(19)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
The ip source binding command is used to add a static IP source binding entry only.
The no form of this command deletes the corresponding IP source binding entry. For the deletion to succeed, all required parameters must match.
Each static IP binding entry is keyed by a MAC address and VLAN number. If the CLI contains an existing MAC and VLAN, the existing binding entry will be updated with the new parameters; a separate binding entry will not be created.
Examples
This example shows how to configure the static IP source binding:
Switch# config terminalSwitch(config)# ip source binding 11.0.0.1 0000.000A.000B vlan 10 interface fastethernet6/10Switch(config)#Related Commands
ip sticky-arp
To enable sticky ARP, use the ip sticky-arp command. Use the no form of this command to disable sticky ARP.
ip sticky-arp
no ip sticky-arp
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Global configuration mode
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
This command is supported on PVLANs only.
ARP entries that are learned on Layer 3 PVLAN interfaces are sticky ARP entries. (You should display and verify ARP entries on the PVLAN interface using the show arp command).
For security reasons, sticky ARP entries on the PVLAN interface do not age out. Connecting new equipment with the same IP address generates a message and the ARP entry is not created.
Because the ARP entries on the PVLAN interface do not age out, you must manually remove ARP entries on the PVLAN interface if a MAC address changes.
Unlike static entries, sticky-ARP entries are not stored and restored when you enter the reboot and restart commands.
Examples
This example shows how to enable sticky ARP:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config) ip sticky-arpSwitch(config)#endSwitch#This example shows how to disable sticky ARP:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config) no ip sticky-arpSwitch(config)#endSwitch#Related Commands
ip verify header vlan all
To enable IP header validation for Layer 2-switched IPv4 packets, use the ip verify header vlan all command. To disable the IP header validation, use the no form of this command.
ip verify header vlan all
no ip verify header vlan all
Syntax Description
This command has no default settings.
Defaults
The IP header is validated for bridged and routed IPv4 packets.
Command Modes
Global configuration mode
Command History
12.1(20)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
This command does not apply to Layer 3-switched (routed) packets.
The Catalyst 4500 series switch checks the validity of the following fields in the IPv4 header for all switched IPv4 packets:
•
•
•
If an IPv4 packet fails the IP header validation, the packet is dropped. If you disable the header validation, the packets with the invalid IP headers are bridged but are not routed even if routing was intended. The IPv4 access lists also are not applied to the IP headers.
Examples
This example shows how to disable the IP header validation for the Layer 2-switched IPv4 packets:
Switch# config terminalSwitch(config)# no ip verify header vlan allSwitch(config)# endSwitch#ip verify source
To enable IP source guard on untrusted Layer 2 interfaces, use the ip verify source command. To disable IP source guard on untrusted Layer 2 interfaces, use the no form of this command.
ip verify source {vlan dhcp-snooping | tracking} [port-security]
no ip verify source {vlan dhcp-snooping | tracking} [port-security]
Syntax Description
Defaults
IP source guard is disabled.
Command Modes
Global configuration mode
Command History
12.1(19)EW
Support for this command was introduced on the Catalyst 4500 series switch.
12.2(37)SG
Added support for IP port security and tracking.
Examples
This example shows how to enable IP source guard on VLANs 10 through 20 on a per-port basis:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# ip dhcp snoopingSwitch(config)# ip dhcp snooping vlan 10 20Switch(config)# interface fastethernet6/1Switch(config-if)# switchport trunk encapsulation dot1qSwitch(config-if)# switchport mode trunkSwitch(config-if)# switchport trunk native vlan 10Switch(config-if)# switchport trunk allowed vlan 11-20Switch(config-if)# no ip dhcp snooping trustSwitch(config-if)# ip verify source vlan dhcp-snoopingSwitch(config)# endSwitch# show ip verify source interface f6/1Interface Filter-type Filter-mode IP-address Mac-address Vlan--------- ----------- ----------- --------------- ----------------- ----------Fa6/1 ip-mac active 10.0.0.1 10Fa6/1 ip-mac active deny-all 11-20Switch#This example shows how to enable IP port security with IP-MAC filters on a Layer 2 access port:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# ip device trackingSwitch(config)# interface fastEthernet 4/3Switch(config-if)# switchport mode accessSwitch(config-if)# switchport access vlan 1Switch(config-if)# ip device tracking maximum 5Switch(config-if)# switchport port-securitySwitch(config-if)# switchport port-security maximum 5Switch(config-if)# ip verify source tracking port-securitySwitch(config-if)# endYou can verify your settings by entering the show ip verify source privileged EXEC command.
Related Commands
ip verify unicast source reachable-via
To enable and configure unicast RPF checks on a Supervisor Engine 6-E and Catalyst 4900M chassis IPv4 interface, use the ip verify unicast source reachable-via command. To disable unicast RPF, use the no form of this command.
ip verify unicast source reachable-via rx allow-default
no ip verify unicast source reachable-via
Syntax Description
rx
Verifies that the source address is reachable on the interface where the packet was received.
allow-default
Verifies that the default route matches the source address.
Defaults
Disabled
Command Modes
Interface configuration mode
Command History
12.2(40)SG
Support for this command was introduced on the Catalyst 4500 with a Supervisor Engine 6-E and the Catalyst 4900M chassis.
Usage Guidelines
Note
Do not use unicast RPF on internal network interfaces. Internal interfaces might have routing asymmetry, which means that there are multiple routes to the source of a packet. Apply unicast RPF only where there is natural or configured symmetry.
Examples
This example shows how to enable unicast RPF exist-only checking mode:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# interface gigabitethernet1/1Switch(config-if)# ip verify unicast source reachable-via rx allow-defaultSwitch(config-if)# endSwitch#Related Commands
ip cef (refer to Cisco IOS documentation)
Enables Cisco Express Forwarding (CEF) on the switch.
Displays the current running configuration for a switch.
ipv6 mld snooping
To enable IP version 6 (IPv6) Multicast Listener Discovery (MLD) snooping globally or on the specified VLAN, use the ipv6 mld snooping command without keywords. To disable MLD snooping on a switch or the VLAN, use the no form of this command.
ipv6 mld snooping [vlan vlan-id]
no ipv6 mld snooping [vlan vlan-id]
Syntax Description
vlan vlan-id
(Optional) Enables or disables IPv6 MLD snooping on the specified VLAN. The VLAN ID range is 1 to 1001 and 1006 to 4094.
Defaults
MLD snooping is globally disabled on the switch.
MLD snooping is enabled on all VLANs. However, MLD snooping must be globally enabled before VLAN snooping can take place.
Command Modes
Global configuration mode
Command History
Usage Guidelines
When MLD snooping is globally disabled, it is disabled on all the existing VLAN interfaces. When you globally enable MLD snooping, it is enabled on all VLAN interfaces that are in the default state (enabled). VLAN configuration overrides global configuration on interfaces on which MLD snooping has been disabled.
If MLD snooping is globally disabled, you cannot enable it on a VLAN. If MLD snooping is globally enabled, you can disable it on individual VLANs.
VLAN numbers 1002 through 1005 are reserved for Token Ring and FDDI VLANs and cannot be used in MLD snooping.
Examples
This example shows how to globally enable MLD snooping:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# ipv6 mld snoopingSwitch(config)# endSwitch#This example shows how to disable MLD snooping on a VLAN:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# no ipv6 mld snooping vlan 11Switch(config)# endSwitch#You can verify your settings by entering the show ipv6 mld snooping user EXEC command.
Related Commands
Displays IP version 6 (IPv6) Multicast Listener Discovery (MLD) snooping configuration of the switch or the VLAN.
ipv6 mld snooping last-listener-query-count
To configure IP version 6 (IPv6) Multicast Listener Discovery Mulitcast Address Specific Queries (MASQs) that will be sent before aging out a client, use the ipv6 mld snooping last-listener-query-count command. To reset the query count to the default settings, use the no form of this command.
ipv6 mld snooping [vlan vlan-id] last-listener-query-count integer_value
no ipv6 mld snooping [vlan vlan-id] last-listener-query-count
Syntax Description
vlan vlan-id
(Optional) Configures last-listener query count on the specified VLAN. The VLAN ID range is 1 to 1001 and 1006 to 4094.
integer_value
The integer range is 1 to 7.
Command Default
The default global count is 2.
The default VLAN count is 0 (the global count is used).
Command Modes
Global configuration mode
Command History
Usage Guidelines
In MLD snooping, the IPv6 multicast switch periodically sends out queries to hosts belonging to the multicast group. If a host wants to leave a multicast group, it can silently leave or it can respond to the query with a Multicast Listener Done message (equivalent to an IGMP Leave message). When Immediate Leave is not configured (it should not be configured if multiple clients for a group exist on the same port), the configured last-listener query count determines the number of MASQs that are sent before an MLD client is aged out.
When the last-listener query count is set for a VLAN, this count overrides the value configured globally. When the VLAN count is not configured (set to the default of 0), the global count is used.
VLAN numbers 1002 through 1005 are reserved for Token Ring and FDDI VLANs and cannot be used in MLD snooping.
Examples
This example shows how to globally set the last-listener query count:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# ipv6 mld snooping last-listener-query-count 1Switch(config)# endSwitch#This example shows how to set the last-listener query count for VLAN 10:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# ipv6 mld snooping vlan 10 last-listener-query-count 3Switch(config)# endSwitch#You can verify your settings by entering the show ipv6 mld snooping [vlan vlan-id] user EXEC command.
Related Commands
ipv6 mld snooping last-listener-query-interval
To configure IP version 6 (IPv6) Multicast Listener Discovery (MLD) snooping last-listener query interval on the switch or on a VLAN, use the ipv6 mld snooping last-listener-query-interval command. To reset the query time to the default settings, use the no form of this command.
ipv6 mld snooping [vlan vlan-id] last-listener-query-interval integer_value
no ipv6 mld snooping [vlan vlan-id] last-listener-query-interval
Syntax Description
Command Default
The default global query interval (maximum response time) is 1000 (1 second).
The default VLAN query interval (maximum response time) is 0 (the global count is used).
Command Modes
Global configuration mode
Command History
Usage Guidelines
The last-listener-query-interval time is the maximum time that a multicast switch waits after issuing a Mulitcast Address Specific Query (MASQ) before deleting a port from the multicast group.
In MLD snooping, when the IPv6 multicast switch receives an MLD leave message, it sends out queries to hosts belonging to the multicast group. If there are no responses from a port to a MASQ for a length of time, the switch deletes the port from the membership database of the multicast address. The last listener query interval is the maximum time that the switch waits before deleting a nonresponsive port from the multicast group.
When a VLAN query interval is set, the global query interval is overridden. When the VLAN interval is set at 0, the global value is used.
VLAN numbers 1002 through 1005 are reserved for Token Ring and FDDI VLANs and cannot be used in MLD snooping.
Examples
This example shows how to globally set the last-listener query interval to 2 seconds:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# ipv6 mld snooping last-listener-query-interval 2000Switch(config)# endSwitch#This example shows how to set the last-listener query interval for VLAN 1 to 5.5 seconds:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# ipv6 mld snooping vlan 1 last-listener-query-interval 5500Switch(config)# endSwitch#You can verify your settings by entering the show ipv6 MLD snooping [vlan vlan-id] user EXEC command.
Related Commands
ipv6 mld snooping listener-message-suppression
To enable IP version 6 (IPv6) Multicast Listener Discovery (MLD) snooping listener message suppression, use the ipv6 mld snooping listener-message-suppression command. To disable MLD snooping listener message suppression, use the no form of this command.
ipv6 mld snooping listener-message-suppression
no ipv6 mld snooping listener-message-suppression
Command Default
The default is for MLD snooping listener message suppression to be disabled.
Command Modes
Global configuration mode
Command History
Usage Guidelines
MLD snooping listener message suppression is equivalent to IGMP snooping report suppression. When it is enabled, received MLDv1 reports to a group are forwarded to IPv6 multicast switchs only once in every report-forward time. This prevents the forwarding of duplicate reports.
Examples
This example shows how to enable MLD snooping listener message suppression:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# ipv6 mld snooping listener-message-suppressionSwitch(config)# endSwitch#This example shows how to disable MLD snooping listener message suppression:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# no ipv6 mld snooping listener-message-suppressionSwitch(config)# endSwitch#You can verify your settings by entering the show ipv6 mld snooping [vlan vlan-id] user EXEC command.
Related Commands
ipv6 mld snooping robustness-variable
To configure the number of IP version 6 (IPv6) Multicast Listener Discovery (MLD) queries that the switch sends before deleting a listener that does not respond, or to enter a VLAN ID to configure the number of queries per VLAN, use the ipv6 mld snooping robustness-variable command. To reset the variable to the default settings, use the no form of this command.
ipv6 mld snooping [vlan vlan-id] robustness-variable integer_value
no ipv6 mld snooping [vlan vlan-id] robustness-variable
Syntax Description
vlan vlan-id
(Optional) Configures the robustness variable on the specified VLAN. The VLAN ID range is 1 to 1001 and 1006 to 4094.
integer_value
The robustness value ranges from 1 to 3.
Command Default
The default global robustness variable (number of queries before deleting a listener) is 2.
The default VLAN robustness variable (number of queries before aging out a multicast address) is 0, which means that the system uses the global robustness variable for aging out the listener.
Command Modes
Global configuration mode
Command History
Usage Guidelines
Robustness is measured by the number of MLDv1 queries sent with no response before a port is removed from a multicast group. A port is deleted when there are no MLDv1 reports received for the configured number of MLDv1 queries. The global value determines the number of queries that the switch waits before deleting a listener that does not respond, and it applies to all VLANs that do not have a VLAN value set.
The robustness value configured for a VLAN overrides the global value. If the VLAN robustness value is 0 (the default), the global value is used.
VLAN numbers 1002 through 1005 are reserved for Token Ring and FDDI VLANs and cannot be used in MLD snooping.
Examples
This example shows how to configure the global robustness variable so that the switch sends out three queries before it deletes a listener port that does not respond:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# ipv6 mld snooping robustness-variable 3Switch(config)# endSwitch#This example shows how to configure the robustness variable for VLAN 1. This value overrides the global configuration for the VLAN:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# ipv6 mld snooping vlan 1 robustness-variable 1Switch(config)# endSwitch#You can verify your settings by entering the show ipv6 MLD snooping [vlan vlan-id] user EXEC command.
Related Commands
ipv6 mld snooping tcn
To configure IP version 6 (IPv6) Multicast Listener Discovery (MLD) Topology Change Notifications (TCNs), use the ipv6 mld snooping tcn commands. To reset the default settings, use the no form of the commands.
ipv6 mld snooping tcn {flood query count integer_value | query solicit}
no ipv6 mld snooping tcn {flood query count integer_value | query solicit}
Syntax Description
Command Default
TCN query soliciting is disabled.
When enabled, the default flood query count is 2.
Command Modes
Global configuration mode
Command History
Examples
This example shows how to enable TCN query soliciting:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# ipv6 mld snooping tcn query solicit.Switch(config)# endSwitch#This example shows how to set the flood query count to 5:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# ipv6 mld snooping tcn flood query count 5.Switch(config)# endSwitch#You can verify your settings by entering the show ipv6 MLD snooping [vlan vlan-id] user EXEC command.
Related Commands
Displays IP version 6 (IPv6) MLD snooping configuration of the switch or the VLAN.
ipv6 mld snooping vlan
To configure IP version 6 (IPv6) Multicast Listener Discovery (MLD) snooping parameters on the VLAN interface, use the ipv6 mld snooping vlan command. To reset the parameters to the default settings, use the no form of this command.
ipv6 mld snooping vlan vlan-id [immediate-leave | mrouter interface interface-id | static ipv6-multicast-address interface interface-id]
no ipv6 mld snooping vlan vlan-id [immediate-leave | mrouter interface interface-id | static ip-address interface interface-id]
Syntax Description
Command Default
MLD snooping Immediate-Leave processing is disabled.
By default, there are no static IPv6 multicast groups.
By default, there are no multicast switch ports.
Command Modes
Global configuration mode
Command History
Usage Guidelines
You should only configure the Immediate-Leave feature when there is only one receiver on every port in the VLAN. The configuration is saved in NVRAM.
The static keyword is used for configuring the MLD member ports statically.
The configuration and the static ports and groups are saved in NVRAM.
VLAN numbers 1002 through 1005 are reserved for Token Ring and FDDI VLANs and cannot be used in MLD snooping.
Examples
This example shows how to enable MLD Immediate-Leave processing on VLAN 1:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# ipv6 mld snooping vlan 1 immediate-leaveSwitch(config)# endSwitch#This example shows how to disable MLD Immediate-Leave processing on VLAN 1:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# no ipv6 mld snooping vlan 1 immediate-leaveSwitch(config)# endSwitch#This example shows how to configure a port as a multicast switch port:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# ipv6 mld snooping vlan 1 mrouter interface gigabitethernet1/0/2Switch(config)# endSwitch#This example shows how to configure a static multicast group:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# ipv6 mld snooping vlan 2 static FF12::34 interface gigabitethernet1/0/2Switch(config)# endSwitch#You can verify your settings by entering the show ipv6 mld snooping vlan vlan-id user EXEC command.
Related Commands
issu abortversion
To cancel the ISSU upgrade or the downgrade process in progress and to restore the Catalyst 4500 series switch to its state before the start of the process, use the issue abortversion command.
issu abortversion active-slot [active-image-new]
Syntax Description
active-slot
Specifies the slot number for the current standby supervisor engine.
active-image-new
(Optional) Name of the new image present in the current standby supervisor engine.
Defaults
There are no default settings.
Command Modes
Privileged EXEC mode
Command History
Usage Guidelines
You can use the issu abortversion command at any time to stop the ISSU process. To complete the process enter the issu commitversion command. Before any action is taken, a check ensures that both supervisor engines are either in the run version (RV) or load version (LV) state.
When the issu abortversion command is entered before the issu runversion command, the standby supervisor engine is reset and reloaded with the old image. When the issu abortversion command is entered after the issu runversion command, a change takes place and the new standby supervisor engine is reset and reloaded with the old image.
Examples
This example shows how you can reset and reload the standby supervisor engine:
Switch# issu abortversion 2Switch#Related Commands
issu acceptversion
To halt the rollback timer and to ensure that the new Cisco IOS software image is not automatically stopped during the ISSU process, use the issu acceptversion command.
issu acceptversion active-slot [active-image-new]
Syntax Description
active-slot
Specifies the slot number for the currently active supervisor engine.
active-image-new
(Optional) Name of the new image on the currently active supervisor engine.
Defaults
Rollback timer resets automatically 45 minutes after you enter the issu runversion command.
Command Modes
Privileged EXEC mode
Command History
Usage Guidelines
After you are satisfied with the new image and have confirmed the new supervisor engine is reachable by both the console and the network, enter the issu acceptversion command to halt the rollback timer. If the issu acceptversion command is not entered within 45 minutes from the time the issu runversion command is entered, the entire ISSU process is automatically rolled back to the previous version of the software. The rollback timer starts immediately after you enter the issu runversion command.
If the rollback timer expires before the standby supervisor engine goes to a hot standby state, the timer is automatically extended by up to 15 minutes. If the standby state goes to a hot-standby state within this extension time or the 15 minute extension expires, the switch aborts the ISSU process. A warning message that requires your intervention is displayed every 1 minute of the timer extension.
If the rollback timer is set to a long period of time, such as the default of 45 minutes, and the standby supervisor engine goes into the hot standby state in 7 minutes, you have 38 minutes (45 minus 7) to roll back if necessary.
Use the issu set rollback-timer to configure the rollback timer.
Examples
This example shows how to halt the rollback timer and allow the ISSU process to continue:
Switch# issu acceptversion 2Switch#Related Commands
issu commitversion
To load the new Cisco IOS software image into the new standby supervisor engine, use the
issu commitversion command.issu commitversion standby-slot [standby-image-new]
Syntax Description
standby-slot
Specifies the slot number for the currently active supervisor engine.
standby-image-new
(Optional) Name of the new image on the currently active supervisor engine.
Defaults
Enabled by default.
Command Modes
Privileged EXEC mode
Command History
Usage Guidelines
The issu commitversion command verifies that the standby supervisor engine has the new Cisco IOS software image in its file system and that both supervisor engines are in the run version (RV) state. If these conditions are met, the following actions take place:
•
•
•
Entering the issu commitversion command completes the In Service Software Upgrade (ISSU) process. This process cannot be stopped or reverted to its original state without starting a new ISSU process.
Entering the issu commitversion command without entering the issu acceptversion command is equivalent to entering both the issu acceptversion and the issu commitversion commands. Use the
issu commitversion command if you do not intend to run in the current state for an extended period of time and are satisfied with the new software version.Examples
This example shows how you can configure the standby supervisor engine to be reset and reloaded with the new Cisco IOS software version:
Switch# issu commitversion 1Switch#Related Commands
issu loadversion
To start the ISSU process, use the issu loadversion command.
issu loadversion active-slot active-image-new standby-slot standby-image-new [force]
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC mode
Command History
Usage Guidelines
The issu loadversion command causes the standby supervisor engine to be reset and booted with the new Cisco IOS software image specified by the command. If both the old image and the new image are ISSU capable, ISSU compatible, and have no configuration mismatches, the standby supervisor engine moves into Stateful Switchover (SSO) mode, and both supervisor engines move into the load version (LV) state.
It will take several seconds after the issu loadversion command is entered for Cisco IOS software to load onto the standby supervisor engine and the standby supervisor engine to transition to SSO mode.
Examples
This example shows how to initiate the ISSU process:
Switch# issu loadversion 1 bootflash:new-image 2 slavebootflash:new-imageSwitch#Related Commands
issu runversion
To force a change from the active supervisor engine to the standby supervisor engine and to cause the newly active supervisor engine to run the new image specified in the issu loadversion command, use the issu runversion command.
issu runversion standby-slot [standby-image-new]
Syntax Description
standby-slot
Specifies the standby slot on the networking device.
standby-image-new
(Optional) Specifies the name of the new image on the standby supervisor engine.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC mode
Command History
Usage Guidelines
The issu runversion command changes the currently active-supervisor engine to standby-supervisor engine and the real standby-supervisor engine is booted with the old image version following and resets the switch. As soon as the standby-supervisor engine moves into the standby state, the rollback timer is started.
Examples
This example shows how to force a change of the active-supervisor engine to standby-supervisor engine:
Switch# issu runversion 2Switch#Related Commands
issu set rollback-timer
To configure the In Service Software Upgrade (ISSU) rollback timer value, use the
issu set rollback-timer command.issu set rollback-timer seconds
Syntax Description
seconds
Specfies the rollback timer value, in seconds. The valid timer value range is from 0 to 7200 seconds (2 hours). A value of 0 seconds disables the rollback timer.
Defaults
Rollback timer value is 2700 seconds.
Command Modes
Global configuration mode
Command History
Usage Guidelines
Use the issue set rollback-timer command to configure the rollback timer value. You can only enable this command when the supervisor engines are in the init state.
Examples
This example shows how you can set the rollback timer value to 3600 seconds, or 1 hour:
Switch# configure terminalSwitch(config)# issu set rollback-timer 3600Switch(config)# endSwitch#Related Commands
l2protocol-tunnel
To enable protocol tunneling on an interface, use the l2protocol-tunnel command. You can enable tunneling for the Cisco Discovery Protocol (CDP), Spanning Tree Protocol (STP), or VLAN Trunking Protocol (VTP) packets. To disable tunneling on the interface, use the no form of this command.
l2protocol-tunnel [cdp | stp | vtp]
no l2protocol-tunnel [cdp | stp | vtp]
Syntax Description
cdp
(Optional) Enables tunneling of CDP.
stp
(Optional) Enables tunneling of STP.
vtp
(Optional) Enables tunneling of VTP.
Defaults
The default is that no Layer 2 protocol packets are tunneled.
Command Modes
Interface configuration mode
Command History
12.2(18)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
You must enter this command, with or without protocol types, to tunnel Layer 2 packets.
Layer 2 protocol tunneling across a service-provider network ensures that Layer 2 information is propagated across the network to all customer locations. When protocol tunneling is enabled, protocol packets are encapsulated with a well-known Cisco multicast address for transmission across the network. When the packets reach their destination, the well-known MAC address is replaced by the Layer 2 protocol MAC address.
You can enable Layer 2 protocol tunneling for CDP, STP, and VTP individually or for all three protocols.
Examples
This example shows how to enable protocol tunneling for the CDP packets:
Switch(config-if)# l2protocol-tunnel cdpSwitch(config-if)#Related Commands
l2protocol-tunnel cos
To configure the class of service (CoS) value for all tunneled Layer 2 protocol packets, use the l2protocol-tunnel cos command. To return to the default value of zero, use the no form of this command.
l2protocol-tunnel cos value
no l2protocol-tunnel cos
Syntax Description
value
Specifies the CoS priority value for tunneled Layer 2 protocol packets. The range is 0 to 7, with 7 being the highest priority.
Defaults
The default is to use the CoS value that is configured for data on the interface. If no CoS value is configured, the default is 5 for all tunneled Layer 2 protocol packets.
Command Modes
Global configuration mode
Command History
12.2(18)EW
This command was first introduced on the Catalyst 4500 series switch.
Usage Guidelines
When enabled, the tunneled Layer 2 protocol packets use this CoS value.
The value is saved in NVRAM.
Examples
This example shows how to configure a Layer 2 protocol tunnel CoS value of 7:
Switch(config)# l2protocol-tunnel cos 7Switch(config)#Related Commands
l2protocol-tunnel drop-threshold
To set a drop threshold for the maximum rate of Layer 2 protocol packets per second to be received before an interface drops packets, use the I2protocol-tunnel drop-threshold command. You can set the drop threshold for the Cisco Discovery Protocol (CDP), Spanning Tree Protocol (STP), or VLAN Trunking Protocol (VTP) packets. To disable the drop threshold on the interface, use the no form of this command.
l2protocol-tunnel drop-threshold [cdp | stp | vtp] value
no l2protocol-tunnel drop-threshold [cdp | stp | vtp] value
Syntax Description
Defaults
The default is no drop threshold for the number of the Layer 2 protocol packets.
Command Modes
Interface configuration mode
Command History
12.2(18)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
The l2protocol-tunnel drop-threshold command controls the number of protocol packets per second that are received on an interface before it drops packets. When no protocol option is specified with a keyword, the threshold is applied to each of the tunneled Layer 2 protocol types. If you also set a shutdown threshold on the interface, the drop-threshold value must be less than or equal to the shutdown-threshold value.
When the drop threshold is reached, the interface drops the Layer 2 protocol packets until the rate at which they are received is below the drop threshold.
Examples
This example shows how to configure the drop threshold rate:
Switch(config-if)# l2protocol-tunnel drop-threshold cdp 50Switch(config-if)#Related Commands
l2protocol-tunnel shutdown-threshold
To configure the protocol tunneling encapsulation rate, use the I2protocol-tunnel shutdown-threshold command. You can set the encapsulation rate for the Cisco Discovery Protocol (CDP), Spanning Tree Protocol (STP), or VLAN Trunking Protocol (VTP) packets. To disable the encapsulation rate on the interface, use the no form of this command.
l2protocol-tunnel shutdown-threshold [cdp | stp | vtp] value
no l2protocol-tunnel shutdown-threshold [cdp | stp | vtp] value
Syntax Description
Defaults
The default is no shutdown threshold for the number of Layer 2 protocol packets.
Command Modes
Interface configuration mode
Command History
12.2(18)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
The l2-protocol-tunnel shutdown-threshold command controls the number of protocol packets per second that are received on an interface before it shuts down. When no protocol option is specified with the keyword, the threshold is applied to each of the tunneled Layer 2 protocol types. If you also set a drop threshold on the interface, the shutdown-threshold value must be greater than or equal to the drop-threshold value.
When the shutdown threshold is reached, the interface is error disabled. If you enable error recovery by entering the errdisable recovery cause l2ptguard command, the interface is brought out of the error-disabled state and allowed to retry the operation again when all the causes have timed out. If the error recovery feature generation is not enabled for l2ptguard, the interface stays in the error-disabled state until you enter the shutdown and no shutdown commands.
Examples
This example shows how to configure the maximum rate:
Switch(config-if)# l2protocol-tunnel shutdown-threshold cdp 50Switch(config-if)#Related Commands
lacp port-priority
To set the LACP priority for the physical interfaces, use the lacp port-priority command.
lacp port-priority priority
Syntax Description
Defaults
Priority is set to 32768.
Command Modes
Interface configuration mode
Command History
Usage Guidelines
This command is not supported on the systems that are configured with a Supervisor Engine I.
You must assign each port in the switch a port priority that can be specified automatically or by entering the lacp port-priority command. The port priority is used with the port number to form the port identifier. The port priority is used to decide which ports should be put in standby mode when there is a hardware limitation that prevents all compatible ports from aggregating.
Although this command is a global configuration command, the priority value is supported only on port channels with LACP-enabled physical interfaces.This command is supported on LACP-enabled interfaces.
When setting the priority, the higher numbers indicate lower priorities.
Examples
This example shows how to set the priority for the interface:
Switch(config-if)# lacp port-priority 23748Switch(config-if)#Related Commands
lacp system-priority
To set the priority of the system for LACP, use the lacp system-priority command.
lacp system-priority priority
Syntax Description
Defaults
Priority is set to 32768.
Command Modes
Global configuration mode
Command History
Usage Guidelines
This command is not supported on systems that are configured with a Supervisor Engine I.
You must assign each switch that is running LACP a system priority that can be specified automatically or by entering the lacp system-priority command. The system priority is used with the switch MAC address to form the system ID and is also used during negotiation with other systems.
Although this command is a global configuration command, the priority value is supported on port channels with LACP-enabled physical interfaces.
When setting the priority, tthe higher numbers indicate lower priorities.
You can also enter the lacp system-priority command in interface configuration mode. After you enter the command, the system defaults to global configuration mode.
Examples
This example shows how to set the system priority:
Switch(config)# lacp system-priority 23748Switch(config)#Related Commands
>
lldp run
To enable processing of received LLDP control packets and enable transmission of LLDP packets with default or configured TLVs..
lldp run
Syntax Description
Defaults
LLDP is disabled.
Command Modes
global interface level
Command History
Usage Guidelines
Configuring this command enables LLDP protocol on the switch. Unconfiguring it disables processing or transmit of LLDP protocol packets from the switch.
Examples
This example shows how to enable LLDP on the switch:Switch(config)# lldp runlldp tlv-select power-management
To to enable power negotiation through LLDP, use the lldp tlv-select power-management interface command.
lldp tlv-select power-management
Syntax Description
Defaults
Enabled on POEP ports
Command Modes
Interface level
Command History
Usage Guidelines
You need to disable this feature if you do not want to perform power negotiation through LLDP.
This feature is not supported on non-POEP ports; the CLI is suppressed on such ports and TLV is not exchanged.
Examples
This example shows how to enable LLDP power negotiation on interface Gigabit Ethernet 3/1:
Switch# config tEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# int gi 3/1Switch(config-if)# lldp tlv-select power-managementRelated Commands
logging event link-status global (global configuration)
To change the default switch-wide global link-status event messaging settings, use the
logging event link-status global command. Use the no form of this command to disable the link-status event messaging.logging event link-status global
no logging event link-status global
Syntax Description
This command has no arguments or keywords.
Defaults
The global link-status messaging is disabled.
Command Modes
Global configuration mode
Command History
12.2(25)SG
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
If link-status logging event is not configured at the interface level, this global link-status setting takes effect for each interface.
Examples
This example shows how to globally enable link status message on each interface:
Switch# config terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# logging event link-status globalSwitch(config)# endSwitch#Related Commands
logging event link-status (interface configuration)
To enable the link-status event messaging on an interface, use the logging event link-status command. Use the no form of this command to disable link-status event messaging. Use the
logging event link-status use-global command to apply the global link-status setting.logging event link-status
no logging event link-status
logging event link-status use-global
Defaults
Global link-status messaging is enabled.
Command Modes
Interface configuration mode
Command History
12.2(25)SG
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
To enable system logging of interface state-change events on a specific interface, enter the
logging event link-status command in interface configuration mode.To enable system logging of interface state-change events on all interfaces in the system, enter the logging event link-status global command in global configuration mode. All interfaces without the state change event configuration use the global setting.
Examples
This example shows how to enable logging event state-change events on interface gi11/1:
Switch# config terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# interface gi11/1Switch(config-if)# logging event link-statusSwitch(config-if)# endSwitch#This example shows how to turn off logging event link status regardless of the global setting:
Switch# config terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# interface gi11/1Switch(config-if)# no logging event link-statusSwitch(config-if)# endSwitch#This example shows how to enable the global event link-status setting on interface gi11/1:
Switch# config terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# interface gi11/1Switch(config-if)# logging event link-status use-globalSwitch(config-if)# endSwitch#Related Commands
logging event trunk-status global (global configuration)
To enable the trunk-status event messaging globally, use the logging event trunk-status global command. Use the no form of this command to disable trunk-status event messaging.
logging event trunk-status global
no logging event trunk-status global
Syntax Description
This command has no arguments or keywords.
Defaults
Global trunk-status messaging is disabled.
Command Modes
Global configuration mode
Command History
12.2(25)SG
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
If trunk-status logging event is not configured at the interface level, the global trunk-status setting takes effect for each interface.
Examples
This example shows how to globally enable link status messaging on each interface:
Switch# config terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# logging event trunk-status globalSwitch(config)# endSwitch#Related Commands
logging event trunk-status (interface configuration)
To enable the trunk-status event messaging on an interface, use the logging event trunk-status command. Use the no form of this command to disable the trunk-status event messaging. Use the
logging event trunk-status use-global command to apply the global trunk-status setting.logging event trunk-status
no logging event trunk-status
logging event trunk-status use-global
Defaults
Global trunk-status messaging is enabled.
Command Modes
Interface configuration mode
Command History
12.2(25)SG
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
To enable system logging of interface state-change events on a specific interface, enter the
logging event trunk-status command in interface configuration mode.To enable system logging of interface state-change events on all interfaces in the system, enter the logging event trunk-status use-global command in global configuration mode. All interfaces without the state change event configuration use the global setting.
Examples
This example shows how to enable logging event state-change events on interface gi11/1:
Switch# config terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# interface gi11/1Switch(config-if)# logging event trunk-statusSwitch(config-if)# endSwitch#This example shows how to turn off logging event trunk status regardless of the global setting:
Switch# config terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# interface gi11/1Switch(config-if)# no logging event trunk-statusSwitch(config-if)# endSwitch#This example shows how to enable the global event trunk-status setting on interface gi11/1:
Switch# config terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# interface gi11/1Switch(config-if)# logging event trunk-status use-globalSwitch(config-if)# endSwitch#Related Commands
mab
To enable and configure MAC authorization bypass (MAB) on a port, use the mab command in interface configuration mode. To disable MAB, use the no form of this command.
mab [eap]
no mab [eap]
Note
Syntax Description
eap
(Optional) Specifies that a full EAP conversation should be used, as opposed to standard RADIUS Access-Request, Access-Accept conversation.
Command Default
Disabled
Command Modes
Interface configuration mode
Command History
Usage Guidelines
When a port is configured for MAB as a fallback method, it operates in a typical dot1X method until a configurable number of failed attempts to request the identity of the host. The authenticator learns the MAC address of the host and uses that information to query an authentication server to see whether this MAC address will be granted access.
Examples
The following example shows how to enable MAB on a port:
Switch(config-if)# mabSwitch(config-if)#The following example shows how to enable and configure MAB on a port:
Switch(config-if)# mab eapSwitch(config-if)#The following example shows how to disable MAB on a port:
Switch(config-if)# no mabSwitch(config-if)#Related Commands
Displays Authentication Manager information.
Displays MAB information.
Displays the running configuration information.
mac access-list extended
To define the extended MAC access lists, use the mac access-list extended command. To remove the MAC access lists, use the no form of this command.
mac access-list extended name
no mac access-list extended name
Syntax Description
Defaults
MAC access lists are not defined.
Command Modes
Global configuration mode
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
When you enter the ACL name, follow these naming conventions:
•
•
•
•
•
When you enter the mac access-list extended name command, you use the following subset to create or delete entries in a MAC layer access list:
[no] {permit | deny} {{src-mac mask | any} [dest-mac mask]} [protocol-family {appletalk | arp-non-ipv4 | decnet | ipx | ipv6 | rarp-ipv4 | rarp-non-ipv4 | vines | xns} | <arbitrary ethertype> | name-coded ethertype].Table 2-7 describes the syntax of the mac access-list extended subcommands.
Table 2-7 mac access-list extended Subcommands
any
Specifies any source-host or destination-host.
arbitrary ethertype
(Optional) Specifies an arbitrary ethertype in the range 1536 to 65535 (Decimal or Hexadecimal)
deny
Prevents access if the conditions are matched.
dest-mac mask
(Optional) Specifies a destination MAC address of the form: dest-mac-address dest-mac-address-mask.
name-coded ethertype
(Optional) Denotes a predefined name-coded ethertype for common protocols:
aarp—AppleTalk ARP
amber—DEC-Amber
appletalk—AppleTalk/EtherTalk
dec-spanning—DEC-Spanning-Tree
decnet-iv—DECnet Phase IV
diagnostic—DEC-Diagnostic
dsm—DEC-DSM
etype-6000—0x6000
etype-8042—0x8042
lat—DEC-LAT
lavc-sca—DEC-LAVC-SCA
mop-console—DEC-MOP Remote Console
mop-dump—DEC-MOP Dump
msdos—DEC-MSDOS
mumps—DEC-MUMPS
netbios—DEC-NETBIOS
protocol-family An Ethernet protocol family
vines-echo—VINES Echo
vines-ip—VINES IP
xns-idp—XNS IDP
no
(Optional) Deletes a statement from an access list.
permit
Allows access if the conditions are matched.
protocol-family
(Optional) Name of the protocol family. Table 2-8 lists which packets are mapped to a particular protocol family.
src-mac mask
Source MAC address in the form: source-mac-address source-mac-address-mask.
Table 2-8 describes mapping an Ethernet packet to a protocol family.
When you enter the src-mac mask or dest-mac mask value, follow these guidelines:
•
•
•
•
•
•
•
Examples
This example shows how to create a MAC layer access list named mac_layer that denies traffic from 0000.4700.0001, which is going to 0000.4700.0009, and permits all other traffic:
Switch(config)# mac access-list extended mac_layerSwitch(config-ext-macl)# deny 0000.4700.0001 0.0.0 0000.4700.0009 0.0.0 protocol-family appletalkSwitch(config-ext-macl)# permit any anySwitch(config-ext-macl)# endSwitch#Related Commands
mac-address-table aging-time
To configure the aging time for the entries in the Layer 2 table, use the mac-address-table aging-time command. To reset the seconds value to the default setting, use the no form of this command.
mac-address-table aging-time seconds [vlan vlan_id]
no mac-address-table aging-time seconds [vlan vlan_id]
Syntax Description
seconds
Aging time in seconds; valid values are 0 and from 10 to 1000000 seconds.
vlan vlan_id
(Optional) Single VLAN number or a range of VLANs; valid values are from 1 to 4094.
Defaults
Aging time is set to 300 seconds.
Command Modes
Global configuration mode
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4500 series switch.
12.1(12c)EW
Support for extended addressing was added.
Usage Guidelines
If you do not enter a VLAN, the change is applied to all routed-port VLANs.
Enter 0 seconds to disable aging.
Examples
This example shows how to configure the aging time to 400 seconds:
Switch(config)#mac-address-table aging-time 400Switch(config)#This example shows how to disable aging:
Switch(config)#mac-address-table aging-time 0Switch(config)Related Commands
mac-address-table dynamic group protocols
To enable the learning of MAC addresses in both the "ip" and "other" protocol buckets, even though the incoming packet may belong to only one of the protocol buckets, use the
mac-address-table dynamic group protocols command. To disable grouped learning, use the no form of this command.mac-address-table dynamic group protocols {ip | other} {ip | other}
no mac-address-table dynamic group protocols {ip | other} {ip | other}
Syntax Description
Defaults
The group learning feature is disabled.
Command Modes
Global configuration mode
Command History
12.2(18)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
The entries within the "ip" and "other" protocol buckets are created according to the protocol of the incoming traffic.
When you use the mac-address-table dynamic group protocols command, an incoming MAC address that might belong to either the "ip" or the "other" protocol bucket, is learned on both protocol buckets. Therefore, any traffic destined to this MAC address and belonging to any of the protocol buckets is unicasted to that MAC address, rather than flooded. This reduces the unicast Layer 2 flooding that might be caused if the incoming traffic from a host belongs to a different protocol bucket than the traffic that is destined to the sending host.
Examples
This example shows that the MAC addresses are initially assigned to either the "ip" or the "other" protocol bucket:
Switch# show mac-address-table dynamicUnicast Entriesvlan mac address type protocols port-------+---------------+--------+---------------------+--------------------1 0000.0000.5000 dynamic other GigabitEthernet1/11 0001.0234.6616 dynamic ip GigabitEthernet3/11 0003.3178.ec0a dynamic assigned GigabitEthernet3/11 0003.4700.24c3 dynamic ip GigabitEthernet3/11 0003.4716.f475 dynamic ip GigabitEthernet3/11 0003.4748.75c5 dynamic ip GigabitEthernet3/11 0003.47f0.d6a3 dynamic ip GigabitEthernet3/11 0003.47f6.a91a dynamic ip GigabitEthernet3/11 0003.ba06.4538 dynamic ip GigabitEthernet3/11 0003.fd63.3eb4 dynamic ip GigabitEthernet3/11 0004.2326.18a1 dynamic ip GigabitEthernet3/11 0004.5a5d.de53 dynamic ip GigabitEthernet3/11 0004.5a5e.6ecc dynamic ip GigabitEthernet3/11 0004.5a5e.f60e dynamic ip GigabitEthernet3/11 0004.5a5f.06f7 dynamic ip GigabitEthernet3/11 0004.5a5f.072f dynamic ip GigabitEthernet3/11 0004.5a5f.08f6 dynamic ip GigabitEthernet3/11 0004.5a5f.090b dynamic ip GigabitEthernet3/11 0004.5a88.b075 dynamic ip GigabitEthernet3/11 0004.c1bd.1b40 dynamic ip GigabitEthernet3/11 0004.c1d8.b3c0 dynamic ip GigabitEthernet3/11 0004.c1d8.bd00 dynamic ip GigabitEthernet3/11 0007.e997.74dd dynamic ip GigabitEthernet3/11 0007.e997.7e8f dynamic ip GigabitEthernet3/11 0007.e9ad.5e24 dynamic ip GigabitEthernet3/11 000b.5f0a.f1d8 dynamic ip GigabitEthernet3/11 000b.fdf3.c498 dynamic ip GigabitEthernet3/11 0010.7be8.3794 dynamic assigned GigabitEthernet3/11 0012.436f.c07f dynamic ip GigabitEthernet3/11 0050.0407.5fe1 dynamic ip GigabitEthernet3/11 0050.6901.65af dynamic ip GigabitEthernet3/11 0050.da6c.81cb dynamic ip GigabitEthernet3/11 0050.dad0.af07 dynamic ip GigabitEthernet3/11 00a0.ccd7.20ac dynamic ip GigabitEthernet3/11 00b0.64fd.1c23 dynamic ip GigabitEthernet3/11 00b0.64fd.2d8f dynamic assigned GigabitEthernet3/11 00d0.b775.c8bc dynamic ip GigabitEthernet3/11 00d0.b79e.de1d dynamic ip GigabitEthernet3/11 00e0.4c79.1939 dynamic ip GigabitEthernet3/11 00e0.4c7b.d765 dynamic ip GigabitEthernet3/11 00e0.4c82.66b7 dynamic ip GigabitEthernet3/11 00e0.4c8b.f83e dynamic ip GigabitEthernet3/11 00e0.4cbc.a04f dynamic ip GigabitEthernet3/11 0800.20cf.8977 dynamic ip GigabitEthernet3/11 0800.20f2.82e5 dynamic ip GigabitEthernet3/1Switch#This example shows how to assign MAC addresses that belong to either the "ip" or the "other" bucket to both buckets:
Switch(config)# mac-address-table dynamic group protocols ip otherSwitch(config)# exitSwitch# show mac address-table dynamicUnicast Entriesvlan mac address type protocols port-------+---------------+--------+---------------------+--------------------1 0000.0000.5000 dynamic ip,other GigabitEthernet1/11 0001.0234.6616 dynamic ip,other GigabitEthernet3/11 0003.4700.24c3 dynamic ip,other GigabitEthernet3/11 0003.4716.f475 dynamic ip,other GigabitEthernet3/11 0003.4748.75c5 dynamic ip,other GigabitEthernet3/11 0003.47c4.06c1 dynamic ip,other GigabitEthernet3/11 0003.47f0.d6a3 dynamic ip,other GigabitEthernet3/11 0003.47f6.a91a dynamic ip,other GigabitEthernet3/11 0003.ba0e.24a1 dynamic ip,other GigabitEthernet3/11 0003.fd63.3eb4 dynamic ip,other GigabitEthernet3/11 0004.2326.18a1 dynamic ip,other GigabitEthernet3/11 0004.5a5d.de53 dynamic ip,other GigabitEthernet3/11 0004.5a5d.de55 dynamic ip,other GigabitEthernet3/11 0004.5a5e.6ecc dynamic ip,other GigabitEthernet3/11 0004.5a5e.f60e dynamic ip,other GigabitEthernet3/11 0004.5a5f.08f6 dynamic ip,other GigabitEthernet3/11 0004.5a5f.090b dynamic ip,other GigabitEthernet3/11 0004.5a64.f813 dynamic ip,other GigabitEthernet3/11 0004.5a66.1a77 dynamic ip,other GigabitEthernet3/11 0004.5a6b.56b2 dynamic ip,other GigabitEthernet3/11 0004.5a6c.6a07 dynamic ip,other GigabitEthernet3/11 0004.5a88.b075 dynamic ip,other GigabitEthernet3/11 0004.c1bd.1b40 dynamic ip,other GigabitEthernet3/11 0004.c1d8.b3c0 dynamic ip,other GigabitEthernet3/11 0004.c1d8.bd00 dynamic ip,other GigabitEthernet3/11 0005.dce0.7c0a dynamic assigned GigabitEthernet3/11 0007.e997.74dd dynamic ip,other GigabitEthernet3/11 0007.e997.7e8f dynamic ip,other GigabitEthernet3/11 0007.e9ad.5e24 dynamic ip,other GigabitEthernet3/11 0007.e9c9.0bc9 dynamic ip,other GigabitEthernet3/11 000b.5f0a.f1d8 dynamic ip,other GigabitEthernet3/11 000b.fdf3.c498 dynamic ip,other GigabitEthernet3/11 0012.436f.c07f dynamic ip,other GigabitEthernet3/11 0050.0407.5fe1 dynamic ip,other GigabitEthernet3/11 0050.6901.65af dynamic ip,other GigabitEthernet3/11 0050.da6c.81cb dynamic ip,other GigabitEthernet3/11 0050.dad0.af07 dynamic ip,other GigabitEthernet3/11 00a0.ccd7.20ac dynamic ip,other GigabitEthernet3/11 00b0.64fd.1b84 dynamic assigned GigabitEthernet3/11 00d0.b775.c8bc dynamic ip,other GigabitEthernet3/11 00d0.b775.c8ee dynamic ip,other GigabitEthernet3/11 00d0.b79e.de1d dynamic ip,other GigabitEthernet3/11 00e0.4c79.1939 dynamic ip,other GigabitEthernet3/11 00e0.4c7b.d765 dynamic ip,other GigabitEthernet3/11 00e0.4c82.66b7 dynamic ip,other GigabitEthernet3/11 00e0.4c8b.f83e dynamic ip,other GigabitEthernet3/11 00e0.4c8c.0861 dynamic ip,other GigabitEthernet3/11 0800.20d1.bf09 dynamic ip,other GigabitEthernet3/1Switch#mac address-table learning vlan
To enable MAC address learning on a VLAN, use the mac address-table learning global configuration command. Use the no form of this command to disable MAC address learning on a VLAN to control which VLANs can learn MAC addresses.
mac address-table learning vlan vlan-id
no mac address-table learning vlan vlan-id
Syntax Description
vlan-id
Specifies a single VLAN ID or a range of VLAN IDs separated by a hyphen or comma. Valid VLAN IDs are 1 to 4094.
Defaults
Enabled on all VLANs
Command Modes
Global configuration
Command History
12.2(54)SG
This command was modified to support the disable learning feature on the Catalyst 4500 series switch.
Usage Guidelines
When you control MAC address learning on a VLAN, you can manage the available table space by controlling which VLANs, and which ports can learn MAC addresses.
You can disable MAC address learning on a single VLAN ID (for example, by entering
no mac address-table learning vlan 223) or on a range of VLAN IDs (for example, by entering
no mac address-table learning vlan 1-20, 15.)Before you disable MAC address learning, familiarize yourself with the network topology and the switch system configuration. If you disable MAC address learning on a VLAN, flooding may occur in the network. For example, if you disable MAC address learning on a VLAN with a configured switch virtual interface (SVI), the switch floods all IP packets in the Layer 2 domain. If you disable MAC address learning on a VLAN that includes more than two ports, every packet entering the switch is flooded in that VLAN domain. Disable MAC address learning only in VLANs that contain two ports. Use caution before disabling MAC address learning on a VLAN with an SVI.
You cannot disable MAC address learning on a VLAN that the switch uses internally. This action causes the switch to generate an error message and rejects the no mac address-table learning vlan command. To view used internal VLANs, enter the show vlan internal usage privileged EXEC command.
If you disable MAC address learning on a VLAN configured as a PVLAN primary or a secondary VLAN, the MAC addresses are still learned on the VLAN (primary or secondary) associated with the PVLAN.
You cannot disable MAC address learning on an RSPAN VLAN. The configuration is not allowed.
If you disable MAC address learning on a VLAN that includes a secure port, MAC address learning is not disabled on the secure port. If you later disable port security on the interface, the disabled MAC address learning state is enabled.
To display the MAC address learning status of a specific VLAN or for all VLANs, enter the
show mac-address-table learning vlan command.Examples
This example shows how to disable MAC address learning on VLAN 2003:
Switch(config)# no mac address-table learning vlan 2003Related Commands
mac-address-table notification
To enable MAC address notification on a switch, use the mac-address-table notification command. To return to the default setting, use the no form of this command
mac-address-table notification [[change [history-size hs_value | interval intv_value]] | [mac-move] | [threshold [limit percentage | interval time]] | [learn-fail [interval time | limit num_fail]]
no mac-address-table notification [[change [history-size hs_value | interval intv_value]] | [mac-move] | [threshold [limit percentage | interval time]] | [learn-fail [interval time | limit num_fail]]
Syntax Description
Defaults
MAC address notification feature is disabled.
The default MAC change trap interval value is 1 second.
The default number of entries in the history table is 1.
MAC move notification is disabled.
MAC threshold monitoring feature is disabled.
The default limit is 50 percent.
The default time is 120 seconds.
Hardware MAC learning failure syslog notification is disabled.
The default limit is 1000.
The default interval is 150 seconds.
Command Modes
Global configuration mode
Command History
Usage Guidelines
You can enable the MAC change notification feature using the mac-address-table notification change command. If you do this, you must also enable MAC notification traps on an interface using the
snmp trap mac-notification change interface configuration command and configure the switch to send MAC change traps to the NMS using the snmp-server enable traps mac-notification global configuration command.When the history-size option is configured, the existing MAC change history table is deleted, and a new table is created.
Examples
This example shows how to set the MAC address notification history table size to 300 entries:
Switch(config)#mac-address-table notification change history-size 300Switch(config)#This example shows how to set the MAC address notification interval time to 1250 seconds:
Switch(config)#mac-address-table notification change interval 1250Switch(config)#This example shows how to enable hardware MAC address learning failure syslog notification:
Switch(config)# mac address-table notification learn-failThis example shows how to set the interval of hardware MAC address learning failure syslog notification to 30 seconds:
Switch(config)# mac address-table notification learn-fail interval 30Related Commands
mac-address-table static
To configure the static MAC addresses for a VLAN interface or drop unicast traffic for a MAC address for a VLAN interface, use the mac-address-table static command. To remove the static MAC address configurations, use the no form of this command.
mac-address-table static mac-addr {vlan vlan-id} {interface type | drop}
no mac-address-table static mac-addr {vlan vlan-id} {interface type} {drop}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Global configuration mode
Command History
12.1(13)EW
Support for this command was introduced on the Catalyst 4500 series switches.
Usage Guidelines
When a static MAC address is installed, it is associated with a port.
The output interface specified must be a Layer 2 interface and not an SVI.
If you do not enter a protocol type, an entry is automatically created for each of the four protocol types.
Entering the no form of this command does not remove the system MAC addresses.
When removing a MAC address, entering interface int is optional. For unicast entries, the entry is removed automatically. For multicast entries, if you do not specify an interface, the entire entry is removed. You can specify the selected ports to be removed by specifying the interface.
Examples
This example shows how to add the static entries to the MAC address table:
Switch(config)#mac-address-table static 0050.3e8d.6400 vlan 100 interface fastethernet5/7Switch(config)#Related Commands
macro apply cisco-desktop
To enable the Cisco-recommended features and settings that are suitable for connecting a switch port to a standard desktop, use the macro apply cisco-desktop command.
macro apply cisco-desktop $AVID access_vlanid
Syntax Description
Defaults
This command has no default settings.
Command Modes
Interface configuration mode
Command History
12.2(18)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
This command can only be viewed and applied; it cannot be modified.
Ensure that the existing configuration on the interface does not conflict with the intended macro configuration. Before you apply the macro, clear the configuration on the interface with the default interface command.
Examples
This example shows how to enable the Cisco-recommended features and settings on port fa2/1:
Switch(config)# interface FastEthernet2/1Switch(config-if)# macro apply cisco-desktop $AVID 50Switch(config-if)#The contents of this macro are as follows:
# Basic interface - Enable data VLAN only# Recommended value for access vlan (AVID) should not be 1switchport access vlan $AVID [access_vlanid]switchport mode access# Enable port security limiting port to a single# MAC address -- that of desktopswitchport port-security# Ensure port-security age is greater than one minute# and use inactivity timer# "Port-security maximum 1" is the default and will not# Show up in the configswitchport port-security violation restrictswitchport port-security aging time 2switchport port-security aging type inactivity# Configure port as an edge network portspanning-tree portfastspanning-tree bpduguard enableRelated Commands
macro apply cisco-phone
To enable the Cisco-recommended features and settings that are suitable for connecting a switch port to a standard desktop and a Cisco IP phone, use the macro apply cisco-phone command.
macro apply cisco-phone $AVID access_vlanid $VVID voice_vlanid
Syntax Description
Defaults
This command has no default settings.
Command Modes
Interface configuration mode
Command History
12.2(18)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
This command can only be viewed and applied; it cannot be modified.
Ensure that the existing configuration on the interface does not conflict with the intended macro configuration. Before you apply the macro, clear the configuration on the interface with the default interface command.
Examples
This example shows how to enable the Cisco-recommended features and settings on port fa2/1:
Switch(config)# interface FastEthernet2/1Switch(config-if)# macro apply cisco-phone $AVID 10 $VVID 50Switch(config-if)#The contents of this macro are as follows:
# VoIP enabled interface - Enable data VLAN# and voice VLAN (VVID)# Recommended value for access vlan (AVID) should not be 1\switchport access vlan $AVID [access_vlan_id]switchport mode access# Update the Voice VLAN (VVID) value which should be# different from data VLAN# Recommended value for voice vlan (VVID) should not be 1switchport voice vlan $VVID [voice_vlan_id]# Enable port security limiting port to a 3 MAC# addressees -- One for desktop and two for phoneswitchport port-securityswitchport port-security maximum 3# Ensure port-security age is greater than one minute# and use inactivity timerswitchport port-security violation restrictswitchport port-security aging time 2switchport port-security aging type inactivity# Enable auto-qos to extend trust to attached Cisco phoneauto qos voip cisco-phone# Configure port as an edge network portspanning-tree portfastspanning-tree bpduguard enable@Related Commands
macro apply cisco-router
To enable the Cisco-recommended features and settings that are suitable for connecting a switch port to a router, use the macro apply cisco-router command.
macro apply cisco-router $NVID native_vlanid
Syntax Description
Defaults
This command has no default settings.
Command Modes
Interface configuration mode
Command History
12.2(18)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
This command can only be viewed and applied; it cannot be modified.
Ensure that the existing configuration on the interface does not conflict with the intended macro configuration. Before you apply the macro apply cisco-router command, clear the configuration on the interface with the default interface command.
Examples
This example shows how to enable the Cisco-recommended features and settings on port fa2/1:
Switch(config)# interface FastEthernet2/1Switch(config-if)# macro apply cisco-router $NVID 80Switch(config-if)#The contents of this macro are as follows:
# Access Uplink to Distributionswitchport trunk encapsulation dot1q# Define unique Native VLAN on trunk ports# Recommended value for native vlan (NVID) should not be 1switchport trunk native vlan $NVID [native_vlan_id]# Update the allowed VLAN range (VRANGE) such that it# includes data, voice and native VLANs# switchport trunk allowed vlan $VRANGE [vlan_range]# Hardcode trunk and disable negotiation to# speed up convergence# Hardcode speed and duplex to routerswitchport mode trunkswitchport nonegotiatespeed 100duplex full# Configure qos to trust this interfaceauto qos voip trustqos trust dscp# Ensure fast access to the network when enabling the interface.# Ensure that switch devices cannot become active on the interface.spanning-tree portfastspanning-tree bpduguard enableRelated Commands
macro apply cisco-switch
To enable the Cisco-recommended features and settings that are suitable for connecting a switch port to another switch, use the macro apply cisco-switch command.
macro apply cisco-switch $NVID native_vlanid
Syntax Description
Defaults
This command has no default settings.
Command Modes
Interface configuration mode
Command History
12.2(18)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
This command can only be viewed and applied; it cannot be modified.
Ensure that the existing configuration on the interface does not conflict with the intended macro configuration. Before you apply this macro, clear the configuration on the interface with the default interface command.
Examples
This example shows how to enable the Cisco-recommended features and settings on port fa2/1:
Switch(config)# interface FastEthernet2/1Switch(config-if)# macro apply cisco-switch $NVID 45Switch(config-if)#The contents of this macro are as follows:
# Access Uplink to Distributionswitchport trunk encapsulation dot1q# Define unique Native VLAN on trunk ports# Recommended value for native vlan (NVID) should not be 1switchport trunk native vlan $NVID [native_vlan_id]# Update the allowed VLAN range (VRANGE) such that it# includes data, voice and native VLANs# switchport trunk allowed vlan $VRANGE# Hardcode trunk and disable negotiation to# speed up convergenceswitchport mode trunkswitchport nonegotiate# Configure qos to trust this interfaceauto qos voip trust# 802.1w defines the link as pt-pt for rapid convergencespanning-tree link-type point-to-pointRelated Commands
macro auto device
Use the macro auto device command to simplify changing the parameters for a built-in functions for a device type. Use the no form of this command to revert to the intial parameter values.
macro auto device device_type [params values]
no macro auto device device_type [params values]
Syntax Description
Command Modes
Global configuration
Command History
Usage Guidelines
Although you can use the macro auto execute command to produce the same effect as the macro auto device command, the later is simpler.
Examples
This example shows how to change the access VLAN and voice VLAN from their default value to user defined values for phone devices.
(config)# macro auto device phone ACCESS_VLAN=10 VOICE_VLAN=20Related Commands
macro auto execute (built-in function)
Use the macro auto execute configuration command to change built-in function default values or to map user-defined triggers to built-in functions and to pass the parameter values. Use the no form of this command to unmap the trigger.
macro auto execute event_trigger builtin shell_function [param name=values]
no macro auto execute event_trigger builtin shell_function [param name=values]
Syntax Description
Defaults
Auto Smartports is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
The switch automatically maps from builtin event triggers to builtin functions. The builtin functions are system-defined functions in the software image.
Use the macro auto execute global configuration command to replace the builtin function default values with values specific to your switch.
You can also create user-defined triggers and use this command to map the triggers to builtin functions.
You can create user-defined event triggers by entering the shell trigger global configuration command. Use the show shell privileged EXEC command to display the contents of the builtin and user-defined triggers and functions.
Examples
This example shows how to use two built-in Auto Smartports macros for connecting Cisco switches and Cisco IP phones to the switch. It modifies the default voice VLAN, access VLAN, and native VLAN for the trunk interface:
Switch# configure terminalSwitch(config)#!!! the next command modifies the access and voice vlansSwitch(config)#!!! for the built in Cisco IP phone auto smartport macroSwitch(config)# macro auto execute CISCO_PHONE_EVENT builtin CISCO_PHONE_AUTO_SMARTPORT ACCESS_VLAN=10 VOICE_VLAN=20Switch(config)#Switch(config)#!!! the next command modifies the native vlanSwitch(config)#!!! for the built in switch auto smartport macroSwitch(config)# macro auto execute CISCO_SWITCH_EVENT builtin CISCO_SWITCH_AUTO_SMARTPORT NATIVE_VLAN=10Switch(config)#!!! the next example creates a user-defined trigger and maps it to a builtin functionsSwitch(config)# shell trigger myTrigger "user-defined trigger"Switch(config)# macro auto execute myTrigger builtin CISCO_PHONE_AUTO_SMARTPORT_ACCESSVLAN voice_vlanSwitch(config)#!!! the next command enables auto smart ports globallySwitch(config)# macro auto global processing fallback CDPSwitch# !!! here's the running configuration of the interface connectedSwitch# !!! to another Cisco Switch after the Macro is appliedSwitch#Switch# show running-config interface Gi1/0/1Building configuration...Current configuration : 284 bytes!interface GigabitEthernet1/0/1switchport trunk encapsulation dot1qswitchport trunk native vlan 10switchport mode trunksrr-queue bandwidth share 10 10 60 20queue-set 2priority-queue outmls qos trust cosauto qos voip trustmacro description CISCO_SWITCH_EVENTendRelated Commands
macro auto execute (remotely-defined trigger)
Use the macro auto execute configuration command to map a trigger to a remotely defined function. Use the no form of this command to unmap the trigger.
macro auto execute trigger_name remote url
no macro auto execute trigger_name remote url
Syntax Description
Defaults
None
Command Modes
Global configuration
Command History
Usage Guidelines
This command enables you to store shell functions in a central location and utilized by ASP on many switches. This alleviates the problem of updating functions on every switch for each modification.Triggering of the remotely defined function requires network connectivity to the URL, which is accessed for each execution of the function.Examples
This example shows how to map a trigger to the remotely defined function myfunction - the filename that contains the function body:
Switch(config)# macro auto execute mytrigger remote tftp://dirt/tftpboot/myfunctionRelated Commands
macro auto execute (user-defined function)
Use the macro auto execute configuration command to map a trigger to a user-defined function. Use the no form of this command to unmap the trigger.
macro auto execute trigger_name [param_name=value] {function body}
no macro auto execute trigger_name [param_name=value]
Syntax Description
trigger_name
Specifies the trigger name.
param name=value
(Optional) Specifies values for the parameters that are to be used in the function body.
function_body
Shell functions with CLIs.
Defaults
None.
Command Modes
Global configuration
Command History
Usage Guidelines
Because the function defined in this command does not have a name, you cannot use it to map to another trigger. This is the only way that you can map a trigger to a user defined function. Shell functions defined in the non-configure mode can not be used to map triggers.Examples
This example shows how to map the user-defined event trigger Cisco Digital Media Player (DMP) to a user-defined macro.
a.
b.
c.
d.
Switch(config)# shell trigger CISCO_DMP_EVENT Cisco DMP playerSwitch(config)# macro auto execute CISCO_DMP_EVENT {if [[ $LINKUP -eq YES ]]; thenconf tinterface $INTERFACEmacro description $TRIGGERswitchport access vlan 1switchport mode accessswitchport port-securityswitchport port-security maximum 1switchport port-security violation restrictswitchport port-security aging time 2switchport port-security aging type inactivityspanning-tree portfastspanning-tree bpduguard enableexitfiif [[ $LINKUP -eq NO ]]; thenconf tinterface $INTERFACEno macro description $TRIGGERno switchport access vlan 1if [[ $AUTH_ENABLED -eq NO ]]; thenno switchport mode accessfino switchport port-securityno switchport port-security maximum 1no switchport port-security violation restrictno switchport port-security aging time 2no switchport port-security aging type inactivityno spanning-tree portfastno spanning-tree bpduguard enableexitfi}Switch(config)# endRelated Commands
macro auto global processing
Use the macro auto global processing global configuration command to enable Auto SmartPorts macros on the switch. Use the no form of this command to disable Auto SmartPorts (ASP) macros globally.
macro auto global processing [fallback cdp] [fallback lldp]
no macro auto global processing [fallback cdp] [fallback lldp]
Syntax Description
Defaults
Auto Smartports is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the macro auto global processing global configuration command to globally enable Auto Smartports macros on the switch. To disable ASP macros on a specific port, use the no macro auto processing command in the interface mode before ASP is enabled globally.
Auto Smartports macros dynamically configure ports based on the device type detected on the port. When the switch detects a new device on a port it applies the appropriate ASP macro. When a link-down event occurs on a port, the switch removes the macro. For example, when you connect a Cisco IP phone to a port, ASP automatically applies the IP phone macro. The IP phone macro enables quality of service (QoS), security features, and a dedicated voice VLAN to ensure proper treatment of delay-sensitive voice traffic.
ASP uses event triggers to map devices to macros. The most common event triggers are based on Cisco Discovery Protocol (CDP) messages received from connected devices. The detection of a device invokes a CDP event trigger: Cisco IP phone, Cisco wireless access point, Cisco switch, or Cisco router. Other event triggers use MAC authentication bypass (MAB) and 802.1X authentication messages.
Use CDP if port authentication is enabled and the RADIUS server does not send an event trigger.
Select LLDP to apply auto configuration if authentication fails.
If authentication is enabled on a port, a switch ignores CDP and LLDP messages unless the fallback cdp keyword is enabled.
When using 802.1X or MAB authentication, configure the RADIUS server to support the Cisco attribute-value (AV) pair auto-smart-port=event trigger.
When CDP-identified devices advertise multiple capabilities, a switch chooses a capability in this priority order: switch, router, access point, lightweight access point, phone, host.
To verify that an ASP macro is applied to an interface, use the show running config command.
The macro auto global processing fallback cdp and macro auto global processing fallback lldp commands enables ASP globally if it is not already enabled, and set the fallback to CDP or LLDP, respectively. However, the no macro auto global processing fallback [cdp | lldp] command only removes the fallback mechanism. It does not disable ASP globally; only the no macro auto global processing command disables ASP globally.
The keywords fallback cdp and fallback lldp are also controlled at the interface level; by default, CDP is the fallback mechanism on an interface. If you prefer LLDP, first enter the no macro auto processing fallback cdp command, then enter the macro auto processing fallback lldp command.
If you want to activate both CDP and LLDP, you must enable them in sequence. For example, you would first enter the macro auto processing fallback cdp command, then the macro auto processing fallback lldp command.
Examples
This example shows how enable ASP on a switch and to disable the feature on Gi1/0/1:
Switch(config)# interface interface Gi1/0/1Switch(config-if)# no macro auto processingSwitch(config)# macro auto global processingRelated Commands
macro auto mac-address-group
Use the macro auto mac-address-group command to configure a group of MAC-address or OUIs as a trigger. Use the no form of this command to unconfigure the group.
macro auto mac-address-group grp_name
no macro auto mac-address-group grp_namel
Syntax Description
Command Modes
Global configuration
Command History
Usage Guidelines
This command changes the mode to config-mac-addr-grp, in which you can add or remove a MAC address or OUI from the group.
You can specify a list of MACs or OUIs, or a range of OUIs (maximum of 5 in the range).
Examples
This example shows how to configure testGroup as a trigger:
Switch(config)# macro auto mac-address-group testGroupSwitch(config-addr-grp-mac)# mac-address list 1111.1111.1111 2222.2222.2222Switch(config-addr-grp-mac)# exitSwitch(config)# exitRelated Commands
macro auto processing
Note
Use the macro auto processing interface configuration command to enable ASP macros on a specific interface. Use the no form of this command to disable ASP on a specific interface before ASP is enabled globally.
macro auto processing [fallback cdp] [fallback lldp]
no macro auto processing [fallback cdp] [fallback lldp]
Syntax Description
fallback cdp
Specifies as CDP as the fallback mechanism.
fallback lldp
Specifies as LLDP as the fallback mechanism.
Defaults
Fallback mechanism is CDP.
Command Modes
Interface level configuration
Command History
Usage Guidelines
The no macro auto processing command should be configured on all interfaces where ASP is not desirable (such as Layer 3 and EtherChannel interfaces) before ASP is enabled globally.
At the interface level, the default fallback mechanism is CDP. To change the mechanism to LLDP, enter the no macro auto processing fallback cdp command, followed by the macro auto processing fallback lldp command.
Examples
This example shows how to enable the feature on an interface:
Switch(config)# interface Gi3/1Switch(config-if)# macro auto processingRelated Commands
macro auto sticky
Use the macro auto sticky configuration to specify not to remove configurations applied by ASP across link flaps and device removal.
macro auto sticky
Syntax Description
Defaults
Not sticky (macros are removed
Command Modes
Global configuration
Command History
Usage Guidelines
This command enables you to avoid unnecessary removal of ASP configurations when a feature intentionally shuts down a link (like EnergyWise, which shuts down inactive links to save energy). When such a feature is enabled, you don't want ASP macros to be applied and removed unnecessarily. So you configure the sticky feature.
Examples
This example shows how to specify not to remove configurations:
Switch(config)# macro auto sticky
Related Commands
macro global apply cisco-global
To apply the system-defined default template to the switch, use the macro global apply cisco-global global configuration command on the switch stack or on a standalone switch.
macro global apply cisco-global
Syntax Description
This command has no keywords or variables.
Defaults
This command has no default setting.
Command Modes
Global configuration mode
Command History
12.2(31)SG
Support for this command was introduced on the Catalyst 4500 series switch.
Examples
These examples show how to apply the system-defined default to the switch:
Switch(config)# macro global apply cisco-globalChanging VTP domain name from gsg-vtp to [smartports] Device mode already VTP TRANSPARENT.Switch(config)#macro global apply system-cpp
To apply the control plane policing default template to the switch, use the macro global apply system-cpp global configuration command on the switch stack or on a standalone switch.
macro global apply system-cpp
Syntax Description
This command has no keywords or variables.
Defaults
This command has no default setting.
Command Modes
Global configuration mode
Command History
12.2(31)SG
Support for this command was introduced on the Catalyst 4500 series switch.
Examples
This example shows how to apply the system-defined default to the switch:
Switch (config)# macro global apply system-cppSwitch (config)#Related Commands
Applies the system-defined default template to the switch.
Enters a description about the macros that are applied to the switch.
macro global description
To enter a description about the macros that are applied to the switch, use the macro global description global configuration command on the switch stack or on a standalone switch. Use the no form of this command to remove the description.
macro global description text
no macro global description text
Syntax Description
Defaults
This command has no default setting.
Command Modes
Global configuration mode
Command History
12.2(31)SG
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
This command associates comment text, or the macro name, with a switch. When multiple macros are applied on a switch, the description text will be from the last applied macro.
Examples
This example shows how to add a description to a switch:
Switch(config)# macro global description udld aggressive mode enabledYou can verify your settings by entering the show parser macro description privileged EXEC command.
Related Commands
main-cpu
To enter the main CPU submode and manually synchronize the configurations on the two supervisor engines, use the main-cpu command.
main-cpu
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Redundancy mode
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4500 series switch. (Catalyst 4507R only).
Usage Guidelines
The main CPU submode is used to manually synchronize the configurations on the two supervisor engines. From the main CPU submode, use the auto-sync command to enable automatic synchronization of the configuration files in NVRAM.
Note
Examples
This example shows how to reenable the default automatic synchronization feature using the auto-sync standard command to synchronize the startup-config and config-register configuration of the active supervisor engine with the standby supervisor engine. The updates for the boot variables are automatic and cannot be disabled.
Switch(config)# redundancySwitch(config-red)# main-cpuSwitch(config-r-mc)# auto-sync standardSwitch(config-r-mc)# endSwitch# copy running-config startup-configSwitch#Related Commands
match
To specify a match clause by selecting one or more ACLs for a VLAN access-map sequence, use the match subcommand. To remove the match clause, use the no form of this command.
match {ip address {acl-number | acl-name}} | {mac address acl-name}
no match {ip address {acl-number | acl-name}} | {mac address acl-name}
Note
Syntax Description
Defaults
This command has no default settings.
Command Modes
VLAN access-map mode
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
The match clause specifies the IP or MAC ACL for traffic filtering.
The MAC sequence is not effective for IP packets. IP packets should be access controlled by IP match clauses.
Refer to the Catalyst 4500 Series Switch Cisco IOS Software Configuration Guide for additional configuration guidelines and restrictions.
Refer to the Cisco IOS Command Reference publication for additional match command information.
Examples
This example shows how to define a match clause for a VLAN access map:
Switch(config)# vlan access-map ganymede 10Switch(config-access-map)# match ip address 13Switch(config-access-map)#Related Commands
Displays the contents of a VLAN access map.
Enters VLAN access-map command mode to create a VLAN access map.
match (class-map configuration)
To define the match criteria for a class map, use the match class-map configuration command. To remove the match criteria, use the no form of this command.
Non-Supervisor Engine 6-E
match {access-group acl-index-or-name | cos cos-list | [lp] dscp dscp-list | [lp] precedence ip-precedence-list
no match {access-group acl-index-or-name | cos cos-list | [lp] dscp dscp-list | [lp] precedence ip-precedence-list
Supervisor Engine 6-E and Catalyst 4900M chassis
match {access-group acl-index-or-name | cos cos-list | [lp] dscp dscp-list | [lp] precedence ip-precedence-list | qos-group value | protocol [ip | ipv6 | arp]
no match {access-group acl-index-or-name | cos cos-list | [lp] dscp dscp-list | [lp] precedence ip-precedence-list | qos-group value | protocol [ip | ipv6 | arp]
Syntax Description
Defaults
No match criteria are defined.
Command Modes
Class-map configuration mode
Command History
Usage Guidelines
Before entering the match command, you must first enter the class-map global configuration command to specify the name of the class whose match criteria you want to establish. The match command is used to specify which fields in the packets are examined to classify the packets. If a packet matches the specified criteria, the packet is considered a member of the class and is forwarded according to the quality of service (QoS) specifications set in the traffic policy.
For the match ip dscp dscp-list or the match ip precedence ip-precedence-list command, you can enter a mnemonic name for a commonly used value. For example, you can enter the match ip dscp af11 command, which is the same as entering the match ip dscp 10 command. You can enter the match ip precedence critical command, which is the same as entering the match ip precedence 5 command. For a list of supported mnemonics, enter the match ip dscp ? or the match ip precedence ? command to see the command-line help strings.
To match only IPv6 packets, you must use the match protocol ipv6 command. To match only IPv4 packets you can use either the ip prefix or the protocol ip keyword.
To match only ARP packets, you must use the match protocol arp command.
You can configure the match cos cos-list, match ip dscp dscp-list, match ip precedence ip-precedence-list command in a class map within a policy map.
The match cos cos-list command applies only to Ethernet frames that carry a VLAN tag.
The match qos-group command is used by the class-map to identify a specific QoS group value assigned to a packet. The QoS group value is local to the switch and is associated with a packet on the input Qos classification.
Packets that do not meet any of the matching criteria are classified as members of the default traffic class. You configure it by specifying class-default as the class name in the class policy-map configuration command. For more information, see the "class" section.
Examples
This example shows how to create a class map called class2, which matches all the inbound traffic with DSCP values of 10, 11, and 12:
Switch# configure terminalSwitch(config)# class-map class2Switch(config-cmap)# match ip dscp 10 11 12Switch(config-cmap)# exitSwitch#This example shows how to create a class map called class3, which matches all the inbound traffic with IP-precedence values of 5, 6, and 7 for both IPv4 and IPv6 traffic:
Switch# configure terminalSwitch(config)# class-map class3Switch(config-cmap)# match ip precedence 5 6 7Switch(config-cmap)# exitSwitch#This example shows how to delete the IP-precedence match criteria and to classify traffic using acl1:
Switch# configure terminalSwitch(config)# class-map class2Switch(config-cmap)# match ip precedence 5 6 7Switch(config-cmap)# no match ip precedenceSwitch(config-cmap)# match access-group acl1Switch(config-cmap)# exitSwitch#This example shows how to specify a class-map that applies only to IPv6 traffic on a Supervisor Engine 6-E:
Switch# configure terminalSwitch(config)# class-map match all ipv6 onlySwitch(config-cmap)# match dscp af21Switch(config-cmap)# match protocol ipv6Switch(config-cmap)# exitSwitch#You can verify your settings by entering the show class-map privileged EXEC command.
Related Commands
Creates a class map to be used for matching packets to the class whose name you specify and to enter class-map configuration mode.
Displays class map information.
match flow ip
To specify match criteria to treat flows with a unique source or destination address as new flows, use the match flow ip command. To disable this function, use the no form of this command.
match flow ip {source-address [ip destination-address ip protocol L4 source-address L4 destination-address] | destination-address}
no match flow ip {source-address [ip destination-address ip protocol L4 source-address L4 destination-address] | destination-address}
Syntax Description
Defaults
This command has no default settings..
Command Modes
class-map configuration submode
Command History
12.2(25)EW
Support for this command was introduced on the Catalyst 4500 series switch.
12.2(25)SG
Support for the full flow option was added.
Usage Guidelines
When you specify the source-address keyword, each flow with a unique source address is treated as a new flow.
When you specify the destination-address keyword, each flow with a unique destination address is treated as a new flow.
A policy map is called a flow-based policy map when you configure the flow keywords on the class map that it uses. To attach a flow-based policy map as a child to an aggregate policy map, use the service-policy command.
Note
Supervisor Engine VI (WS-X4516-10GE) is present.
Examples
This example shows how to create a flow-based class map associated with a source address:
Switch(config)# class-map match-all c1Switch(config-cmap)# match flow ip source-addressSwitch(config-cmap)# endSwitch#Switch# show class-map c1Class Map match-all c1 (id 2)Match flow ip source-addressSwitch#This example shows how to create a flow-based class map associated with a destination address:
Switch(config)# class-map match-all c1Switch(config-cmap)# match flow ip destination-addressSwitch(config-cmap)# endSwitch#Switch# show class-map c1Class Map match-all c1 (id 2)Match flow ip destination-addressSwitch#Assume there are two active flows on the Fast Ethernet interface 6/1 with source addresses 192.168.10.20 and 192.168.10.21. The following example shows how to maintain each flow to 1 Mbps with an allowed burst value of 9000 bytes:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# class-map c1Switch(config-cmap)# match flow ip source-addressSwitch(config-cmap)# exitSwitch(config)# policy-map p1Switch(config-pmap)# class c1Switch(config-pmap-c)# police 1000000 9000Switch(config-pmap-c)# exitSwitch(config-pmap)# exitSwitch(config)# interface fastethernet6/1Switch(config-if)# service-policy input p1Switch(config-if)# endSwitch# write memorySwitch# show policy-map interfaceFastEthernet6/1Service-policy input: p1Class-map: c1 (match-all)15432182 packetsMatch: flow ip source-addresspolice: Per-interfaceConform: 64995654 bytes Exceed: 2376965424 bytesClass-map: class-default (match-any)0 packetsMatch: any0 packetsSwitch#This example shows two active flows on the Fast Ethernet interface 6/1 with destination addresses of 192.168.20.20 and 192.168.20.21. The following example shows how to maintain each flow to 1 Mbps with an allowed burst value of 9000 bytes:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# class-map c1Switch(config-cmap)# match flow ip destination-addressSwitch(config-cmap)# exitSwitch(config)# policy-map p1Switch(config-pmap)# class c1Switch(config-pmap-c)# police 1000000 9000Switch(config-pmap-c)# exitSwitch(config-pmap)# exitSwitch(config)# interface fastethernet6/1Switch(config-if)# service-policy input p1Switch(config-if)# endSwitch# write memorySwitch# show policy-map interfaceFastEthernet6/1Service-policy input: p1Class-map: c1 (match-all)2965072 packetsMatch: flow ip destination-addresspolice: Per-interfaceConform: 6105636 bytes Exceed: 476652528 bytesClass-map: class-default (match-any)0 packetsMatch: any0 packetsSwitch#Assume there are two active flows as shown below on the Fast Ethernet interface 6/1:
SrcIp DstIp IpProt SrcL4Port DstL4Port--------------------------------------------------------192.168.10.10 192.168.20.20 20 6789 81192.168.10.10 192.168.20.20 20 6789 21With the following configuration, each flow is policed to a 1000000 bps with an allowed 9000-byte burst value.
Note
Switch# conf terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# class-map c1Switch(config-cmap)# match flow ip source-address ip destination-address ip protocol l4 source-port l4 destination-portSwitch(config-cmap)# exitSwitch(config)# policy-map p1Switch(config-pmap)# class c1Switch(config-pmap-c)# police 1000000 9000Switch(config-pmap-c)# exitSwitch(config-pmap)# exitSwitch(config)# interface fastEthernet 6/1Switch(config-if)# service-policy input p1Switch(config-if)# endSwitch# write memorySwitch# show policy-map interfaceFastEthernet6/1class-map c1match flow ip source-address ip destination-address ip protocol l4 source-port l4 destination-port!policy-map p1class c1police 1000000 bps 9000 byte conform-action transmit exceed-action drop!interface FastEthernet 6/1service-policy input p1Switch# show class-map c1Class Map match-all c1 (id 2)Match flow ip source-address ip destination-address ip protocol l4 source-port l4 destination-portSwitch# show policy-map p1Policy Map p1Class c1police 1000000 bps 9000 byte conform-action transmit exceed-action dropSwitch# show policy-map interfaceFastEthernet6/1Service-policy input: p1Class-map: c1 (match-all)15432182 packetsMatch: flow ip source-address ip destination-address ip protocol l4 source-port l4 destination-portpolice: Per-interfaceConform: 64995654 bytes Exceed: 2376965424 bytesClass-map: class-default (match-any)0 packetsMatch: any0 packetsSwitch#Related Commands
mdix auto
To enable the automatic medium-dependent interface crossover (auto-MDIX) feature on the interface, use the mdix auto command. When auto-MDIX is enabled, the interface automatically detects the required cable connection type (straight-through or crossover) and configures the connection appropriately. Use the no form of this command to disable auto-MDIX.
mdix auto
no mdix auto
Syntax Description
This command has no arguments or keywords.
Defaults
Auto-MDIX is enabled.
Command Modes
Interface configuration mode
Command History
12.2(31)SGA
Support for this command was introduced on the Catalyst 4500 series switch.
12.2(46)SG
Added supported and unsupported linecard information to the usage guidelines.
Usage Guidelines
The following linecards support Auto-MDIX through the CLI on their copper media ports: WS-X4124-RJ45, WS-X4148-RJ45 (hardware revision 3.0 or higher), and WS-X4232-GB-RJ45 (hardware revision 3.0, or higher), WS-X4920-GE-RJ45, and WS-4648-RJ45V+E (Auto-MDIX support when inline power is disabled on the port).
Linecards that support auto-MDIX by default when port auto-negotiation enabled and cannot be turned off using an mdix CLI command include: WS-X4448-GB-RJ45, WS-X4548-GB-RJ45, WS-X4424-GB-RJ45, and WS-X4412-2GB-T.
Linecards that cannot support auto-MDIX functionality, either by default or CLI commands, include: WS-X4548-GB-RJ45V, WS-X4524-GB-RJ45V, WS-X4506-GB-T, WS-X4148-RJ, WS-X4248-RJ21V, WS-X4248-RJ45V, WS-X4224-RJ45V, and WS-X4232-GB-RJ.
When you enable auto-MDIX on an interface, you must also set the interface speed to be autoneogiated so that the feature operates correctly.
When auto-MDIX (and autonegotiation of speed) is enabled on one or both of connected interfaces, link up occurs even if the cable type (straight-through or crossover) is incorrect.
Examples
This example shows how to enable auto MDIX on a port:
Switch# configure terminalSwitch(config)# interface FastEthernet6/3Switch(config-if)# speed autoSwitch(config-if)# mdix autoSwitch(config-if)# endRelated Commands
media-type
To select the connector for a dual-mode capable port, use the media-type command.
media-type {rj45 | sfp}
Syntax Description
Defaults
sfp
Command Modes
Interface configuration mode
Command History
12.2(20)EWA
Support for this command was introduced for the WS-X4306-GB-T module and the WS-X4948 chassis.
Usage Guidelines
This command is supported on all ports on the WS-X4306-GB-T module and ports 1/45-48 on the WS-X4948 chassis.
Entering the show interface capabilities command provides the Multiple Media Types field, which displays the value no if a port is not dual-mode capable and lists the media types (sfp and rj45) for dual-mode capable ports.
Examples
This example shows how to configure port 5/45 on a WS-X4948 chassis to use the RJ-45 connector:
Switch(config)# interface gigabitethernet 5/45Switch(config-if)# media-type rj45mode
To set the redundancy mode, use the mode command.
mode {rpr | sso}
Syntax Description
Defaults
For Catalyst 4500 series switches that are configured with Supervisor Engine II+, Supervisor Engine IV, and Supervisor Engine V, the defaults are as follows:
•
•
Note
Command Modes
Redundancy configuration mode
Command History
12.2(20)EWA
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
RPR and SSO mode are not supported on Catalyst 4500 series switches that are configured with Supervisor Engine 2.
The mode command can be entered only from within redundancy configuration mode.
Follow these guidelines when configuring your system to RPR or SSO mode:
•
•
•
•
The redundant supervisor engine reloads on any mode change and begins to work in the current mode.
Examples
This example shows how to set the redundancy mode to SSO:
Switch(config)# redundancySwitch(config-red)# mode ssoSwitch(config-red)#Related Commands
monitor session
To enable the SPAN sessions on interfaces or VLANs, use the monitor session command. To remove one or more source or destination interfaces from a SPAN session, or a source VLAN from a SPAN session, use the no form of this command.
monitor session session {destination interface {FastEthernet interface-number | GigabitEthernet interface-number} [encapsulation {isl | dot1q}] [ingress [vlan vlan_id] [learning]]} | {remote vlan vlan_id} | {source {interface {FastEthernet interface-number | GigabitEthernet interface-number | Port-channel interface-number}} | [vlan vlan_id] |{remote vlan vlan_id} | {cpu [queue queue_id | acl {input {error {rx} | log {rx} | punt {rx} | rx}} | output {error {rx} | forward {rx} | log {rx} | punt {rx} | rx} | adj-same-if {rx} | all {rx} | bridged {1 {rx} | 2 {rx} | 3 {rx} | 4 {rx} | rx} | control-packet {rx} | mtu-exceeded {rx} | routed {forward {1 {rx} | 2 {rx} | 3 {rx} | 4 {rx} | rx} | received {1 {rx} | 2 {rx} | 3 {rx} | 4{rx} | rx} | rx] | rpf-failure {rx} | unknown-sa {rx}]}]} [ , | - | rx | tx | both]} | {filter {ip access-group [name | id]}{vlan vlan_id [ , | - ]} | {packet-type {good | bad}} | {address-type {unicast | multicast | broadcast} [rx | tx | both]}
no monitor session session {destination interface {FastEthernet interface-number | GigabitEthernet interface-number} [encapsulation {isl | dot1q}] [ingress [vlan vlan_id] [learning]]} | {remote vlan vlan_id} | {source {interface {FastEthernet interface-number | GigabitEthernet interface-number | Port-channel interface-number}} | [vlan vlan_id] |{remote vlan vlan_id} | {cpu [queue queue_id | acl {input {error {rx} | log {rx} | punt {rx} | rx}} | output {error {rx} | forward {rx} | log {rx} | punt {rx} | rx} | adj-same-if {rx} | all {rx} | bridged {1 {rx} | 2 {rx} | 3 {rx} | 4 {rx} | rx} | control-packet {rx} | mtu-exceeded {rx} | routed {forward {1 {rx} | 2 {rx} | 3 {rx} | 4 {rx} | rx} | received {1 {rx} | 2 {rx} | 3 {rx} | 4{rx} | rx} | rx] | rpf-failure {rx} | unknown-sa {rx}]}]} [ , | - | rx | tx | both]} | {filter {ip access-group [name | id]}{vlan vlan_id [ , | - ]} | {packet-type {good | bad}} | {address-type {unicast | multicast | broadcast} [rx | tx | both]}
Supervisor Engine 6-E and Catalyst 4900M chassis
monitor session session {destination interface {FastEthernet interface-number | GigabitEthernet interface-number} [encapsulation {isl | dot1q}] [ingress [vlan vlan_id] [learning]]} | {remote vlan vlan_id} | {source { interface {FastEthernet interface-number | GigabitEthernet interface-number | Port-channel interface-number}} | [vlan vlan_id] |{remote vlan vlan_id} | {cpu [queue queue_id | acl { input {copy {rx} | error {rx} | forward {rx} | punt {rx} | rx} } | output {copy {rx} | error {rx} | forward {rx} | punt {rx} | rx} | all {rx} | control-packet {rx} | esmp {rx} | l2-forward { adj-same-if {rx} | bridge-cpu {rx} | ip-option {rx} | ipv6-scope-check-fail {rx} | l2-src-index-check-fail {rx} | mcast-rpf-fail {rx} | non-arpa {rx} | router-cpu {rx} | ttl-expired {rx} | ucast-rpf-fail {rx} | rx} | l3-forward { forward {rx} | glean {rx} | receive {rx} | rx} mtu-exceeded {rx} | unknown-port-vlan-mapping {rx} | unknown-sa {rx}]} [ , | - | rx | tx | both]} | {filter {ip access-group [name | id]}{vlan vlan_id [ , | - ]} | {packet-type {good | bad}} | {address-type {unicast | multicast | broadcast} [rx | tx | both]}
no monitor session session {destination interface {FastEthernet interface-number | GigabitEthernet interface-number} [encapsulation {isl | dot1q}] [ingress [vlan vlan_id] [learning]]} | {remote vlan vlan_id} | {source {cpu{both | queue | rx | tx} | interface {FastEthernet interface-number | GigabitEthernet interface-number | Port-channel interface-number}} | [vlan vlan_id] |{remote vlan vlan_id} | {cpu [queue queue_id | acl {input {copy {rx} | error {rx} | forward {rx} | punt {rx} | rx} } | output {copy {rx} | error {rx} | forward {rx} | punt {rx} | rx} | all {rx} | control-packet {rx} | esmp {rx} | l2-forward { adj-same-if {rx} | bridge-cpu {rx} | ip-option {rx} | ipv6-scope-check-fail {rx} | l2-src-index-check-fail {rx} | mcast-rpf-fail {rx} | non-arpa {rx} | router-cpu {rx} | ttl-expired {rx} | ucast-rpf-fail {rx} | rx} | l3-forward {forward {rx} | glean {rx} | receive {rx} | rx} mtu-exceeded {rx} | unknown-port-vlan-mapping {rx} | unknown-sa {rx}]} [ , | - | rx | tx | both]} | {filter {ip access-group [name | id]}{vlan vlan_id [ , | - ]} | {packet-type {good | bad}} | {address-type {unicast | multicast | broadcast} [rx | tx | both]}
Syntax Description
Defaults
Received and transmitted traffic, as well as all VLANs, packet types, and address types are monitored on a trunking interface.
Packets are transmitted untagged out the destination port; ingress and learning are disabled.
All packets are permitted and forwarded "as is" on the destination port.
Command Modes
Global configuration mode
Command History
Usage Guidelines
Only one SPAN destination for a SPAN session is supported. If you attempt to add another destination interface to a session that already has a destination interface that is configured, you will get an error. You must first remove a SPAN destination interface before changing the SPAN destination to a different interface.
Beginning in Cisco IOS Release 12.1(12c)EW, you can configure sources from different directions within a single user session.
Note
A particular SPAN session can either monitor VLANs or monitor individual interfaces: you cannot have a SPAN session that monitors both specific interfaces and specific VLANs. If you first configure a SPAN session with a source interface, and then try to add a source VLAN to the same SPAN session, you will receive an error. You will also receive an error message if you configure a SPAN session with a source VLAN, and then try to add a source interface to that session. You must first clear any sources for a SPAN session before switching to another type of source. CPU sources may be combined with source interfaces and source VLANs.
When configuring the ingress option on a destination port, you must specify an ingress VLAN if the configured encapsulation type is untagged (the default) or is 802.1Q. If the encapsulation type is ISL, then no ingress VLAN specification is necessary.
By default, when you enable ingress, no host learning is performed on destination ports. When you enter the learning keyword, host learning is performed on the destination port, and traffic to learned hosts is forwarded out the destination port.
If you enter the filter keyword on a monitored trunking interface, only traffic on the set of specified VLANs is monitored. Port-channel interfaces are displayed in the list of interface options if you have them configured. VLAN interfaces are not supported. However, you can span a particular VLAN by entering the monitor session session source vlan vlan-id command.
The packet-type filters are supported only in the Rx direction. You can specify both Rx- and Tx-type filters and multiple-type filters at the same time (for example, you can use good and unicast to only sniff nonerror unicast frames). As with VLAN filters, if you do not specify the type, the session will sniff all packet types.
The queue identifier allows sniffing for only traffic that is sent or received on the specified CPU queues. The queues may be identified either by number or by name. The queue names may contain multiple numbered queues for convenience.
Examples
This example shows how to configure IP access group 100 on a SPAN session:
Switch# configure terminalSwitch(config)# monitor session 1 filter ip access-group 100Switch(config)# endSwitch(config)#This example shows how to add a source interface to a SPAN session:
Switch# configure terminalSwitch(config)# monitor session 1 source interface fa2/3Switch(config)# endSwitch(config)#Switch(config)#Switch(config)#This example shows how to configure the sources with different directions within a SPAN session:
Switch# configure terminalSwitch(config)# monitor session 1 source interface fa2/3 rxSwitch(config)# monitor session 1 source interface fa2/2 txSwitch(config)# endThis example shows how to remove a source interface from a SPAN session:
Switch# configure terminalSwitch(config)# no monitor session 1 source interface fa2/3Switch(config)# endThis example shows how to limit SPAN traffic to VLANs 100 through 304:
Switch# configure terminalSwitch(config)# monitor session 1 filter vlan 100 - 304Switch(config)# endThis example shows how to configure RSPAN VLAN 20 as the destination:
Switch# configure terminalSwitch(config)# monitor session 2 destination remote vlan 20Switch(config)# endThis example shows how to use queue names and queue number ranges for the CPU as a SPAN source on Supervisor Engine 6-E:
Switch# configure terminalSwitch(config)# monitor session 2 source cpu queue control-packet rxSwitch(config)# monitor session 3 source cpu queue 10 rxSwitch(config)# end
Note
Related Commands
mtu
To enable jumbo frames on an interface by adjusting the maximum size of a packet or maximum transmission unit (MTU), use the mtu command. To return to the default setting, use the no form of this command.
mtu bytes
no mtu
Syntax Description
Defaults
The default settings are as follows:
•
•
Command Modes
Interface configuration mode
Command History
12.1(13)EW
Support for this command was introduced on the Catalyst 4500 series switches.
Usage Guidelines
Jumbo frames are supported on nonblocking Gigabit Ethernet ports, switch virtual interfaces (SVI), and EtherChannels. Jumbo frames are not available for stub-based ports.
The baby giants feature uses the global system mtu size command to set the global baby giant MTU. It allows all stub-based port interfaces to support an Ethernet payload size of up to 1552 bytes.
Both the system mtu command and the per-interface mtu command work on interfaces that can support jumbo frames, but the per-interface mtu command takes precedence.
Examples
This example shows how to specify an MTU of 1800 bytes:
Switch(config)# interface GigabitEthernet 1/1Switch(config-if)# mtu 1800Related Commands
name
To set the MST region name, use the name command. To return to the default name, use the no form of this command.
name name
no name name
Syntax Description
name
Specifies the name of the MST region. The name can be any string with a maximum length of 32 characters.
Defaults
The MST region name is not set.
Command Modes
MST configuration mode
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
Two or more Catalyst 4500 series switches with the same VLAN mapping and configuration version number are considered to be in different MST regions if the region names are different.
Examples
This example shows how to name a region:
Switch(config-mst)# name CiscoSwitch(config-mst)#Related Commands
Maps a VLAN or a set of VLANs to an MST instance.
Sets the MST configuration revision number.
Displays MST protocol information.
Enters the MST configuration submode.
nmsp
To configure Network Mobility Services Protocol (NMSP) on the switch, use the nmsp command. This command is available only when your switch is running the cryptographic (encrypted) software image. Use the no form of this command to return to the default setting.
nmsp {enable | {notification interval {attachment | location} interval-seconds}}
no nmsp {enable | {notification interval {attachment | location} interval-seconds}}
Syntax Description
Defaults
NMSP is disabled, NMSP notification interval attachment and NMSP notification interval location defaults are 30 seconds.
Command Modes
Global configuration mode
Command History
12.2(52)SG
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
Use the nmsp global configuration command to enable the switch to send encrypted NMSP location and attachment notifications to a Cisco Mobility Services Engine (MSE).
Examples
This example shows how to enable NMSP on a switch and set the location notification time to 10 seconds:
Switch(config)# nmsp enableSwitch(config)# nmsp notification interval location 10Switch(config)#Related Commands
Clears the NMSP statistic counters.
Suppress reporting attachment information from a specified interface.
Displays the NMSP information.
nmsp attachment suppress
To suppress reporting attachment information from a specified interface, use the nmsp attachment suppress interface command. This command is available only when your switch is running the cryptographic (encrypted) software image. Use the no form of this command to report attachment information.
nmsp attachment suppress
no nmsp attachment suppress
Syntax Description
This command has no arguments or keywords.
Defaults
Attachment information is reported.
Command Modes
Interface configuration mode
Command History
12.2(52)SG
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
Use the nmsp attachment suppress interface configuration command to configure an interface to not send attachment notifications to a Cisco Mobility Services Engine (MSE).
Examples
This example shows how to configure an interface to not send attachment information to the MSE:
Switch(config)# switch interface gigabitethernet1/2Switch(config-if)# nmsp attachment suppressSwitch(config-if)#Related Commands
Configures Network Mobility Services Protocol (NMSP) on the switch.
Displays the NMSP information.
pagp learn-method
To learn the input interface of the incoming packets, use the pagp learn-method command. To return to the default value, use the no form of this command.
pagp learn-method {aggregation-port | physical-port}
no pagp learn-method
Syntax Description
aggregation-port
Specifies learning the address on the port channel.
physical-port
Specifies learning the address on the physical port within the bundle.
Defaults
Aggregation port is enabled.
Command Modes
Interface configuration mode
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Examples
This example shows how to enable physical port address learning within the bundle:
Switch(config-if)#pagp learn-method physical-portSwitch(config-if)#This example shows how to enable aggregation port address learning within the bundle:
Switch(config-if)#pagp learn-method aggregation-portSwitch(config-if)#Related Commands
pagp port-priority
To select a port in hot standby mode, use the pagp port-priority command. To return to the default value, use the no form of this command.
pagp port-priority priority
no pagp port-priority
Syntax Description
Defaults
Port priority is set to 128.
Command Modes
Interface configuration mode
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
The higher the priority, the better the chances are that the port will be selected in the hot standby mode.
Examples
This example shows how to set the port priority:
Switch(config-if)#pagp port-priority 45Switch(config-if)#Related Commands
Learns the input interface of the incoming packets.
Displays information about the port channel.
passive-interface
To disable sending routing updates on an interface, use the passive-interface command. To reenable the sending of routing updates, use the no form of this command.
passive-interface [[default] {interface-type interface-number}] | {range interface-type interface-number-interface-type interface-number}
no passive-interface [[default] {interface-type interface-number}] | {range interface-type interface-number-interface-type interface-number}
Syntax Description
Defaults
Routing updates are sent on the interface.
Command Modes
Router configuration mode
Command History
12.2(31)SG
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
You can use the passive-interface range command on the following interfaces: FastEthernet, GigabitEthernet, VLAN, Loopback, Port-channel, 10-GigabitEthernet, and Tunnel. When you use the passive-interface range command on a VLAN interface, the interface should be the existing VLAN SVIs. To display the VLAN SVIs, enter the show running config command. The VLANs that are not displayed cannot be used in the passive-interface range command.
The values that are entered with the passive-interface range command are applied to all the existing VLAN SVIs.
Before you can use a macro, you must define a range using the define interface-range command.
All configuration changes that are made to a port range through the passive-interface range command are retained in the running-configuration as individual passive-interface commands.
You can enter the range in two ways:
•
•
You can either specify the interfaces or the name of an interface-range macro. An interface range must consist of the same interface type, and the interfaces within a range cannot span across the modules.
You can define up to five interface ranges on a single command; separate each range with a comma:
interface range gigabitethernet 5/1-20, gigabitethernet4/5-20.Use this format when entering the port-range:
•
You cannot specify both a macro and an interface range in the same command. After creating a macro, you can enter additional ranges. If you have already entered an interface range, the CLI does not allow you to enter a macro.
You can specify a single interface in the range range value. This makes the command similar to the passive-interface interface-number command.
Note
If you disable the sending of routing updates on an interface, the particular subnet will continue to be advertised to other interfaces, and updates from other routers on that interface continue to be received and processed.
The default keyword sets all interfaces as passive by default. You can then configure individual interfaces where adjacencies are desired using the no passive-interface command. The default keyword is useful in Internet service provider (ISP) and large enterprise networks where many of the distribution routers have more than 200 interfaces.
For the Open Shortest Path First (OSPF) protocol, OSPF routing information is neither sent nor received through the specified router interface. The specified interface address appears as a stub network in the OSPF domain.
For the Intermediate System-to-Intermediate System (IS-IS) protocol, this command instructs IS-IS to advertise the IP addresses for the specified interface without actually running IS-IS on that interface. The no form of this command for IS-IS disables advertising IP addresses for the specified address.
Note
Enhanced Interior Gateway Routing Protocol (EIGRP) is disabled on an interface that is configured as passive although it advertises the route.
Examples
The following example sends EIGRP updates to all interfaces on network 10.108.0.0 except GigabitEthernet interface 1/1:
Switch(config)#interface gigabitethernet 1/1Switch(config-if)#router eigrp 109Switch(config-router)#network 10.108.0.0Switch(config-router)#passive-interface gigabitethernet 1/1Switch(config-router)#The following configuration enables IS-IS on Ethernet interface 1 and serial interface 0 and advertises the IP addresses of Ethernet interface 0 in its link-state protocol data units (PDUs):
Switch(config-if)#router isis FinanceSwitch(config-router)#passive-interface Ethernet 0Switch(config-router)#interface Ethernet 1Switch(config-router)#ip router isis FinanceSwitch(config-router)#interface serial 0Switch(config-router)#ip router isis FinanceSwitch(config-router)#The following example sets all interfaces as passive, then activates Ethernet interface 0:
Switch(config-if)#router ospf 100Switch(config-router)#passive-interface defaultSwitch(config-router)#no passive-interface ethernet0Switch(config-router)#network 10.108.0.1 0.0.0.255 area 0Switch(config-router)#The following configuration sets the Ethernet ports 3 through 4 on module 0 and GigabitEthernet ports 4 through 7 on module 1 as passive:
Switch(config-if)#router ospf 100Switch(config-router)#passive-interface range ethernet0/3-4,gigabitethernet1/4-7Switch(config-router)#permit
To permit an ARP packet based on matches against the DHCP bindings, use the permit command. To remove a specified ACE from an access list, use the no form of this command.
permit {[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 permit {[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
Defaults
This command has no default settings.
Command Modes
arp-nacl configuration mode
Command History
12.1(19)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
Permit clauses can be added to forward or drop ARP packets based on some matching criteria.
Examples
This example shows a host with a MAC address of 0000.0000.abcd and an IP address of 1.1.1.1. This example shows how to permit both requests and responses from this host:
Switch(config)# arp access-list static-hostsSwitch(config-arp-nacl)# permit ip host 1.1.1.1 mac host 0000.0000.abcdSwitch(config-arp-nacl)# endSwitch# show arp access-listARP access list static-hostspermit ip host 1.1.1.1 mac host 0000.0000.abcdSwitch#Related Commands
police
To configure the Traffic Policing feature, use the police QoS policy-map class configuration command. To remove the Traffic Policing feature from the configuration, use the no form of this command.
police {bps | kbps | mbps |gbps} [burst-normal] [burst-max] conform-action action exceed-action action [violate-action action]
no police {bps | kbps | mbps |gbps} [burst-normal] [burst-max] conform-action action exceed-action action [violate-action action]
Syntax Description
Defaults
This command is disabled by default.
Command Modes
Policy-map class configuration mode (when specifying a single action to be applied to a market packet)
Policy-map class police configuration mode (when specifying multiple actions to be applied to a marked packet)
Command History
12.2(40)SG
This command was introduced on the Catalyst 4500 series switch using a Supervisor Engine 6E.
Usage Guidelines
Use the police command to mark a packet with different quality of service (QoS) values based on conformance to the service-level agreement.
Traffic policing will not be executed for traffic that passes through an interface.
Specifying Multiple Actions
The police command allows you to specify multiple policing actions. When specifying multiple policing actions when configuring the police command, note the following points:
•
•
Using the Police Command with the Traffic Policing Feature
The police command can be used with Traffic Policing feature. The Traffic Policing feature works with a token bucket algorithm. Two types of token bucket algorithms are a single-token bucket algorithm and a two-token bucket algorithm. A single-token bucket system is used when the violate-action option is not specified, and a two-token bucket system is used when the violate-action option is specified.
Token Bucket Algorithm with One Token Bucket
The one token bucket algorithm is used when the violate-action option is not specified in the police command of the command-line interface (CLI).
The conform bucket is initially set to the full size (the full size is the number of bytes specified as the normal burst size).
When a packet of a given size (for example, "B" bytes) arrives at specific time (time "T") the following actions occur:
•
(time between packets <which is equal to T - T1> * policer rate)/8 bytes
•
•
Token Bucket Algorithm with Two Token Buckets (Refer to RFC 2697)
The two-token bucket algorithm is used when the violate-action is specified in the police command CLI.
The conform bucket is initially full (the full size is the number of bytes specified as the normal burst size).
The exceed bucket is initially full (the full exceed bucket size is the number of bytes specified in the maximum burst size).
The tokens for both the conform and exceed token buckets are updated based on the token arrival rate, or committed information rate (CIR).
When a packet of given size (for example, "B" bytes) arrives at specific time (time "T") the following actions occur:
•
The token arrival rate is calculated as follows:
(time between packets <which is equal to T-T1> * policer rate)/8 bytes
•
•
•
Examples
Token Bucket Algorithm with One Token Bucket
This example shows how to define a traffic class (using the class-map command) and associate the match criteria from the traffic class with the Traffic Policing configuration, which is configured in the service policy (using the policy-map command). The service-policy command is then used to attach this service policy to the interface.
In this particular example, Traffic Policing is configured with the average rate at 8000 bits per second and the normal burst size at 1000 bytes for all packets leaving Gigabit Ethernet interface 6/1:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# class-map access-matchSwitch(config-cmap)# match access-group 1Switch(config-cmap)# exitSwitch(config)# policy-map police-settingSwitch(config-pmap)# class access-matchSwitch(config-pmap-c)# police 8000 1000 conform-action transmit exceed-action dropSwitch(config-pmap-c)# exitSwitch(config-pmap)# exitSwitch(config)# interface gigabitethernet 6/1Switch(config-if)# service-policy output police-settingSwitch(config-if)# endIn this example, the initial token buckets starts full at 1000 bytes. If a 450-byte packet arrives, the packet conforms because enough bytes are available in the conform token bucket. The conform action (send) is taken by the packet and 450 bytes are removed from the conform token bucket (leaving 550 bytes).
If the next packet arrives 0.25 seconds later, 250 bytes are added to the token bucket ((0.25 * 8000)/8), leaving 800 bytes in the token bucket. If the next packet is 900 bytes, the packet exceeds and the exceed action (drop) is taken. No bytes are taken from the token bucket.
Token Bucket Algorithm with Two Token Buckets Example (Refer to RFC 2697)
In this particular example, Traffic Policing is configured with the average rate at 8000 bits per second, the normal burst size at 1000 bytes, and the excess burst size at 1000 bytes for all packets leaving Gigabit Ethernet interface 6/1.
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# class-map access-matchSwitch(config-cmap)# match access-group 1Switch(config-cmap)# exitSwitch(config)# policy-map police-settingSwitch(config-pmap)# class access-matchSwitch(config-pmap-c)# police 8000 1000 1000 conform-action transmit exceed-action set-qos-transmit 1 violate-action dropSwitch(config-pmap-c)# exitSwitch(config-pmap)# exitSwitch(config)# interface gigabitethernet 6/1Switch(config-if)# service-policy output police-settingSwitch(config-if)# endIn this example, the initial token buckets starts full at 1000 bytes. If a 450-byte packet arrives, the packet conforms because enough bytes are available in the conform token bucket. The conform action (send) is taken by the packet and 450 bytes are removed from the conform token bucket (leaving 550 bytes).
If the next packet arrives 0.25 seconds later, 250 bytes are added to the conform token bucket ((0.25 * 8000)/8), leaving 800 bytes in the conform token bucket. If the next packet is 900 bytes, the packet does not conform because only 800 bytes are available in the conform token bucket.
The exceed token bucket, which starts full at 1000 bytes (as specified by the excess burst size) is then checked for available bytes. Because enough bytes are available in the exceed token bucket, the exceed action (set the QoS transmit value of 1) is taken and 900 bytes are taken from the exceed bucket (leaving 100 bytes in the exceed token bucket.
If the next packet arrives 0.40 seconds later, 400 bytes are added to the token buckets ((.40 * 8000)/8). Therefore, the conform token bucket now has 1000 bytes (the maximum number of tokens available in the conform bucket) and 200 bytes overflow the conform token bucket (because it only 200 bytes were needed to fill the conform token bucket to capacity). These overflow bytes are placed in the exceed token bucket, giving the exceed token bucket 300 bytes.
If the arriving packet is 1000 bytes, the packet conforms because enough bytes are available in the conform token bucket. The conform action (transmit) is taken by the packet and 1000 bytes are removed from the conform token bucket (leaving 0 bytes).
If the next packet arrives 0.20 seconds later, 200 bytes are added to the token bucket ((.20 * 8000)/8). Therefore, the conform bucket now has 200 bytes. If the arriving packet is 400 bytes, the packet does not conform because only 200 bytes are available in the conform bucket. Similarly, the packet does not exceed because only 300 bytes are available in the exceed bucket. Therefore, the packet violates and the violate action (drop) is taken.
Related Commands
police (percent)
To configure traffic policing on the basis of a percentage of bandwidth available on an interface, use the police command in QoS policy-map class configuration mode. To remove traffic policing from the configuration, use the no form of this command.
police cir percent percent [bc conform-burst-in-msec] [pir percent percentage] [be peak-burst-inmsec]
no police cir percent percent [bc conform-burst-in-msec] [pir percent percentage] [be peak-burst-inmsec]
Syntax Description
Command Default
This command is disabled by default.
Command Modes
Policy-map class configuration mode
Command History
12.2(40)SG
This command was introduced on the Catalyst 4500 series switch using a Supervisor Engine 6E.
Usage Guidelines
This command calculates the CIR and PIR on the basis of a percentage of the maximum amount of bandwidth available on the interface. When a policy map is attached to the interface, the equivalent CIR and PIR values in bits per second (bps) are calculated on the basis of the interface bandwidth and the percent value entered with this command. The show policy-map interface command can then be used to verify the bps rate calculated.
The calculated CIR and PIR bps rates must be in the range of 32,000 and 32,000,000,000 bps. If the rates are outside this range, the associated policy map cannot be attached to the interface. If the interface bandwidth changes (for example, more is added), the bps values of the CIR and the PIR are recalculated on the basis of the revised amount of bandwidth. If the CIR and PIR percentages are changed after the policy map is attached to the interface, the bps values of the CIR and PIR are recalculated.
This command also allows you to specify the values for the conform burst size and the peak burst size in milliseconds. If you want bandwidth to be calculated as a percentage, the conform burst size and the peak burst size must be specified in milliseconds (ms).
Examples
This example shows how to configure traffic policing using a CIR and a PIR based on a percentage of bandwidth on Gigabit interface 6/2. In this example, a CIR of 20 percent and a PIR of 40 percent have been specified. Additionally, an optional bc value and be value (300 ms and 400 ms, respectively) have been specified.
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# policy-map policy1Switch(config-pmap)# class-map class1Switch(config-pmap-c)# police cir percent 20 bc 3 ms pir percent 40 be 4 msSwitch(config-pmap-c)# exitSwitch(config-pmap-c)# interface gigabitethernet 6/2Switch(config-if)# service-policy output policySwitch(config-if)# endpolice rate
To configure single or dual rate policer, use the police rate command in policy-map configuration mode. To remove traffic policing from the configuration, use the no form of this command.
Syntax for Bytes Per Second
police rate units bps [burst burst-in-bytes bytes] [peak-rate peak-rate-in-bps bps] [pack-burst peak-burst-in-bytes bytes]
no police rate units bps [burst burst-in-bytes bytes] [peak-rate peak-rate-in-bps bps] [pack-burst peak-burst-in-bytes bytes]
Syntax for Percent
police rate percent percentage [burst ms ms] [peak-rate percent percentage] [pack-burst ms ms]
no police rate percent percentage [burst ms ms] [peak-rate percent percentage] [pack-burst ms ms]
Syntax Description
Command Default
This command is disabled by default.
Command Modes
Policy-map configuration mode
Command History
12.2(40)SG
This command was introduced on the Catalyst 4500 series switch using a Supervisor Engine 6E.
Usage Guidelines
Use the police rate command to limit traffic on the basis of pps, bps, or a percentage of interface bandwidth.
If the police rate command is issued, but the a rate is not specified, traffic that is destined will be policed on the basis of bps.
Examples
This example shows how to configure policing on a class to limit traffic to an average rate of 1,500,000 bps:
Switch(config)# class-map c1Switch(config-cmap)# match access-group 140Switch(config-cmap)# exitSwitch(config)# policy-map p1Switch(config-pmap)# class c1Switch(config-pmap-c)# police rate 1500000 burst 500000Switch(config-pmap-c)# exitRelated Commands
police (two rates)
To configure traffic policing using two rates, the committed information rate (CIR) and the peak information rate (PIR), use the police command in policy-map configuration mode. To remove two-rate traffic policing from the configuration, use the no form of this command.
police cir cir [bc conform-burst] pir pir [be peak-burst] [conform-action action [exceed-action action [violate-action action]]]
no police cir cir [bc conform-burst] pir pir [be peak-burst] [conform-action action [exceed-action action [violate-action action]]]
Syntax Description
Command Default
This command is disabled by default.
Command Modes
Policy-map configuration mode
Command History
12.2(40)SG
This command was introduced on the Catalyst 4500 series switch using a Supervisor Engine 6E.
Usage Guidelines
Refer to RFC 2698-Two Rate Three Color Marker.
Two-rate traffic policing uses two token buckets—Tc and Tp—for policing traffic at two independent rates. Note the following points about the two token buckets:
•
•
Updating Token Buckets
The following scenario illustrates how the token buckets are updated:
A packet of B bytes arrives at time t. The last packet arrived at time t1. The CIR and the PIR token buckets at time t are represented by Tc(t) and Tp(t), respectively. Using these values and in this scenario, the token buckets are updated as follows:
Tc(t) = min(CIR * (t-t1) + Tc(t1), Bc)
Tp(t) = min(PIR * (t-t1) + Tp(t1), Be)
Marking Traffic
The two-rate policer marks packets as either conforming, exceeding, or violating a specified rate. The following points (using a packet of B bytes) illustrate how a packet is marked:
•
•
Otherwise, the packet is marked as conforming to the specified rate, and both token buckets—Tc(t) and Tp(t)—are updated as follows:
Tp(t) = Tp(t) - B
Tc(t) = Tc(t) - B
For example, if the CIR is 100 kbps, the PIR is 200 kbps, and a data stream with a rate of 250 kbps arrives at the two-rate policer, the packet would be marked as follows:
•
•
•
Marking Packets and Assigning Actions Flowchart
The flowchart in Figure 2-1 illustrates how the two-rate policer marks packets and assigns a corresponding action (that is, violate, exceed, or conform) to the packet.
Figure 2-1 Marking Packets and Assigning Actions with the Two-Rate Policer
Examples
This example shows how to configure two-rate traffic policing on a class to limit traffic to an average committed rate of 500 kbps and a peak rate of 1 Mbps:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# class-map policeSwitch(config-cmap)# match access-group 101Switch(config-cmap)# policy-map policy1Switch(config-pmap)# class policeSwitch(config-pmap-c)# police cir 500000 bc 10000 pir 1000000 be 10000 conform-action transmit exceed-action set-prec-transmit 2 violate-action dropSwitch(config-pmap-c)# interface gigabitethernet 6/1Switch(config-if)# service-policy output policy1Switch(config-if)# endSwitch# show policy-map policy1Policy Map policy1Class policepolice cir 500000 conform-burst 10000 pir 1000000 peak-burst 10000 conform-action transmit exceed-action set-prec-transmit 2 violate-action dropSwitch#Traffic marked as conforming to the average committed rate (500 kbps) will be sent as is. Traffic marked as exceeding 500 kbps, but not exceeding 1 Mbps, will be marked with IP Precedence 2 and then sent. All traffic marked as exceeding 1 Mbps will be dropped. The burst parameters are set to 10000 bytes.
In the following example, 1.25 Mbps of traffic is sent ("offered") to a policer class:
Switch# show policy-map interface gigabitethernet 6/1GigabitEthernet6/1Service-policy output: policy1Class-map: police (match all)148803 packets, 36605538 bytes30 second offered rate 1249000 bps, drop rate 249000 bpsMatch: access-group 101police:cir 500000 bps, conform-burst 10000, pir 1000000, peak-burst 100000conformed 59538 packets, 14646348 bytes; action: transmitexceeded 59538 packets, 14646348 bytes; action: set-prec-transmit 2violated 29731 packets, 7313826 bytes; action: dropconformed 499000 bps, exceed 500000 bps violate 249000 bpsClass-map: class-default (match-any)19 packets, 1990 bytes30 seconds offered rate 0 bps, drop rate 0 bpsMatch: anySwitch#The two-rate policer marks 500 kbps of traffic as conforming, 500 kbps of traffic as exceeding, and 250 kbps of traffic as violating the specified rate. Packets marked as conforming to the rate will be sent as is, and packets marked as exceeding the rate will be marked with IP Precedence 2 and then sent. Packets marked as violating the rate are dropped.
policy-map
To create or modify a policy map that can be attached to multiple ports to specify a service policy and to enter policy-map configuration mode, use the policy-map global configuration command. To delete an existing policy map and to return to global configuration mode, use the no form of this command.
policy-map policy-map-name
no policy-map policy-map-name
Syntax Description
Defaults
No policy maps are defined.
Command Modes
Global configuration mode
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4500 series switch.
12.2(40)SG
Added support for the Supervisor Engine 6-E and Catalyst 4900M chassis.
Usage Guidelines
Before configuring policies for classes whose match criteria are defined in a class map, use the policy-map command to specify the name of the policy map to be created or modified. After you enter the policy-map command, the switch enters policy-map configuration mode. You can configure or modify the class policies for that policy map and decide how to treat the classified traffic.
These configuration commands are available in policy-map configuration mode:
•
•
•
•
To return to global configuration mode, use the exit command. To return to privileged EXEC mode, use the end command.
You can configure class policies in a policy map only if the classes have match criteria defined for them. To configure the match criteria for a class, use the class-map global configuration and match class-map configuration commands.
Examples
This example shows how to create a policy map called policy1. When attached to the ingress direction, it matches all the inbound traffic defined in class1, sets the IP DSCP to 10, and polices the traffic at an average rate of 1 Mbps and bursts at 20 KB. Traffic exceeding the profile is marked down to a DSCP value obtained from the policed-DSCP map and then sent. This policer action is applicable on all Catalyst 4500 supervisor engines except the Supervisor Engine 6-E and Catalyst 4900M chassis.
Switch# configure terminalSwitch(config)# policy-map policy1Switch(config-pmap)# class class1Switch(config-pmap-c)# set ip dscp 10Switch(config-pmap-c)# police 1000000 20000 exceed-action policed-dscp-transmitSwitch(config-pmap-c)# exitSwitch#This example shows how to configure multiple classes in a policy map called policymap2 on a Supervisor Engine 6-E:
Switch# configure terminalSwitch(config)# policy-map policymap2Switch(config-pmap)# class class1Switch(config-pmap-c)# police 100000 20000 exceed-actionSwitch(config-pmap-c)# set-dscp-transmit cs3Switch(config-pmap-c)# set-cos-transmit 3Switch(config-pmap-c)# exitSwitch(config-pmap)# class class2Switch(config-pmap-c)# police cir 32000 pir 64000 conform-action transmit exceed-actionSwitch(config-pmap-c)# set-dscp-transmit cs3 violate-action dropSwitch(config-pmap-c)# exitSwitch(config-pmap)# class class3Switch(config-pmap-c)# set dscp cs3Switch(config-pmap-c)# exitSwitch#This example shows how to delete the policy map called policymap2:
Switch# configure terminalSwitch(config)# no policy-map policymap2Switch#You can verify your settings by entering the show policy-map privileged EXEC command.
Related Commands
port-channel load-balance
To set the load-distribution method among the ports in the bundle, use the port-channel load-balance command. To reset the load distribution to the default, use the no form of this command.
port-channel load-balance method
no port-channel load-balance
Syntax Description
method
Specifies the load distribution method. See the "Usage Guidelines" section for more information.
Defaults
Load distribution on the source XOR destination IP address is enabled.
Command Modes
Global configuration mode
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
The following values are valid for the load-distribution method:
•
•
•
•
•
•
•
•
•
Examples
This example shows how to set the load-distribution method to the destination IP address:
Switch(config)#port-channel load-balance dst-ipSwitch(config)#This example shows how to set the load-distribution method to the source XOR destination IP address:
Switch(config)#port-channel load-balance src-dst-portSwitch(config)#Related Commands
Accesses or creates a port-channel interface.
Displays EtherChannel information for a channel.
port-security mac-address
To configure a secure address on an interface for a specific VLAN or VLAN range, use the
port-security mac-address command.port-security mac-address mac_address
Syntax Description
Command Modes
VLAN-range interface submode
Command History
12.2(25)EWA
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
Layer 2 interfaces can be part of multiple VLANs (for example, a typical trunk port). In conjunction with the vlan command, you can use the port-security mac-address command to specify different addresses on different VLANs.
Examples
This example shows how to configure the secure address 1.1.1 on interface Gigabit Ethernet 1/1 for VLANs 2-3:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# interface gigabitethernet1/1Switch(config-if)# switchport trunk encapsulation dot1qSwitch(config-if)# switchport mode trunkSwitch(config-if)# vlan 2-3Switch(config-if-vlan-range)# port-security mac-address 1.1.1Switch(config-if-vlan-range)# endSwitch#Related Commands
Configures a sticky address on an interface for a specific VLAN or VLAN range.
Configures the maximum number of addresses on an interface for a specific VLAN or VLAN range.
port-security mac-address sticky
To configure a sticky address on an interface for a specific VLAN or VLAN range, use the
port-security mac-address sticky command.port-security mac-address sticky mac_address
Syntax Description
Command Modes
VLAN-range interface submode
Command History
12.2(25)EWA
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
The Sticky feature must be enabled on an interface before you can configure the
port-security mac-address sticky command.Usage Guidelines
Layer 2 interfaces can be part of multiple VLANs (for example, a typical trunk port). In conjunction with the vlan command, you can use the port-security mac-address sticky command to specify different sticky addresses on different VLANs.
The Sticky feature must be enabled on an interface before you can configure the
port-security mac-address sticky command.Sticky MAC addresses are addresses that persist across switch reboots and link flaps.
Examples
This example shows how to configure the sticky address 1.1.1 on interface Gigabit Ethernet 1/1 for VLANs 2-3:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# interface gigabitethernet1/1Switch(config-if)# switchport trunk encapsulation dot1qSwitch(config-if)# switchport mode trunkSwitch(config-if)# vlan 2-3Switch(config-if-vlan-range)# port-security mac-address sticky 1.1.1Switch(config-if-vlan-range)# endSwitch#Related Commands
Configures a secure address on an interface for a specific VLAN or VLAN range.
Configures the maximum number of addresses on an interface for a specific VLAN or VLAN range.
port-security maximum
To configure the maximum number of addresses on an interface for a specific VLAN or VLAN range, use the port-security maximum command.
port-security maximum max_value
Syntax Description
Command Modes
VLAN-range interface submode
Command History
12.2(25)EWA
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
Layer 2 interfaces can be part of multiple VLANs (for example, a typical trunk port). In conjunction with the vlan command, you can use the port-security maximum command to specify the maximum number of secure addresses on different VLANs.
If a specific VLAN on a port is not configured with a maximum value, the maximum configured for the port is used for that VLAN. In this situation, the maximum number of addresses that can be secured on this VLAN is limited to the maximum value configured on the port.
Each VLAN can be configured with a maximum count that is greater than the value configured on the port. Also, the sum total of the maximum configured values for all the VLANs can exceed the maximum configured for the port. In either of these situations, the number of MAC addresses secured on each VLAN is limited to the lesser of the VLAN configuration maximum and the port configuration maximum.
Examples
This example shows how to configure a maximum number of addresses (5) on interface
Gigabit Ethernet 1/1 for VLANs 2-3:Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# interface g1/1Switch(config-if)# switchport trunk encapsulation dot1qSwitch(config-if)# switchport mode trunkSwitch(config-if)# vlan 2-3Switch(config-if-vlan-range)# port-security maximum 5Switch(config-if-vlan-range)# exitSwitch#Related Commands
Configures a secure address on an interface for a specific VLAN or VLAN range.
Configures a sticky address on an interface for a specific VLAN or VLAN range.
power dc input
To configure the power DC input parameters on the switch, use the power dc input command. To return to the default power settings, use the no form of this command.
power dc input watts
no power dc input
Syntax Description
watts
Sets the total capacity of the external DC source in watts; valid values are from 300 to 8500.
Defaults
DC power input is 2500 W.
Command Modes
Global configuration mode
Command History
12.1(11)EW
Support for this command was introduced on the Catalyst 4500 series switch.
12.1(13)EW
Support for dc input was added.
Usage Guidelines
If your interface is not capable of supporting Power over Ethernet, you will receive this message:
Power over Ethernet not supported on interface AdminExamples
This example shows how to set the total capacity of the external DC power source to 5000 W:
Switch(config)# power dc input 5000Switch(config)#Related Commands
power inline
To set the inline-power state for the inline-power-capable interfaces, use the power inline command. To return to the default values, use the no form of this command.
power inline {auto [max milliwatt] | never | static [max milliwatt] | consumption milliwatt}
no power inline
Syntax Description
Defaults
The default settings are as follows:
•
•
•
Command Modes
Interface configuration mode
Command History
Usage Guidelines
If your interface is not capable of supporting Power over Ethernet, you will receive this message:
Power over Ethernet not supported on interface AdminExamples
This example shows how to set the inline-power detection and power for the inline-power-capable interfaces:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# interface fastethernet 4/1Switch(config-if)# power inline autoSwitch(config-if)#endSwitch#This example shows how to disable the inline-power detection and power for the inline-power-capable interfaces:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# interface fastethernet 4/1Switch(config-if)# power inline neverSwitch(config-if)#endSwitch#This example shows how to set the permanent Power over Ethernet allocation to 8000 mW for Fast Ethernet interface 4/1 regardless what is mandated either by the 802.3af class of the discovered device or by any CDP packet that is received from the powered device:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# interface fastethernet 4/1Switch(config-if)#power inline consumption 8000Switch(config-if)#endSwitch#This example shows how to pre-allocate Power over Ethernet to 16500 mW for Gigabit Ethernet interface 2/1 regardless of what is mandated either by the 802.3af class of the discovered device or by any CDP packet that is received from the powered device:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# interface gigabitethernet 2/1Switch(config-if)# power inline static max 16500Switch(config-if)# endSwitch#Related Commands
power inline consumption
To set the default power that is allocated to an interface for all the inline-power-capable interfaces on the switch, use the power inline consumption command. To return to the default values, use the no form of this command.
power inline consumption default milliwatts
no power inline consumption default
Syntax Description
Defaults
Milliwatt mode is set to 15400.
Command Modes
Global configuration mode
Command History
12.1(11)EW
Support for this command was introduced on the Catalyst 4500 series switch.
12.1(20)EW
Support added for Power over Ethernet.
Usage Guidelines
The inline power consumption command overrides the power allocated to the port through IEEE/Cisco phone discovery and CDP/LLDP power negotiation. To guarantee safe operation of the system, ensure that the value configured here is no less than the actual power requirement of the attached device. If the power drawn by the inline powered devices exceeds the capability of the power supply, it could trip the power supply.
If your interface is not capable of supporting Power over Ethernet, you will receive this message:
Power over Ethernet not supported on interface AdminExamples
This example shows how to set the Power over Ethernet allocation to use 8000 mW, regardless of any CDP packet that is received from the powered device:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# power inline consumption default 8000Switch(config)#endSwitch#Related Commands
Sets the inline-power state for the inline-power-capable interfaces.
Displays information about the power status.
power inline police
To configure Power over Ethernet policing on a particular interface, use the power inline police command. The no form of the command disables PoE policing on an interface.
power inline police [action] [errdisable | log]
no power inline police [action] [errdisable | log]
Syntax Description
Defaults
PoE policing is disabled.
Command Modes
Interface configuration mode
Command History
12.2(50)SG
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
If a port is in the errdisable state because of a PoE policing fault, enter the shut command followed by a no shut on the interface to make the port operational again.
You can also configure inline-power errdisable autorecovery so that an errdisabled interface is automatically revived when the errdisable autorecovery timer expires.
Examples
This example shows how to enable PoE policing and configure a policing action:
Switch(config)# int gigabitEthernet 2/1Switch(config-if)# power inline policeSwitch(config-if)# do show power inline police gigabitEthernet 2/1Available:421(w) Used:39(w) Remaining:382(w)Interface Admin Oper Admin Oper Cutoff OperState State Police Police Power Power--------- ------ ---------- ---------- ---------- ------ -----Gi2/1 auto on errdisable ok 17.4 7.6Switch(config-if)# power inline police action logAvailable:421(w) Used:39(w) Remaining:382(w)Interface Admin Oper Admin Oper Cutoff OperState State Police Police Power Power--------- ------ ---------- ---------- ---------- ------ -----Gi2/1 auto on log ok 17.4 9.6Related Commands
power redundancy-mode
To configure the power settings for the chassis, use the power redundancy-mode command. To return to the default setting, use the default form of this command.
power redundancy-mode {redundant | combined}
default power redundancy-mode
Syntax Description
redundant
Configures the switch to redundant power management mode.
combined
Configures the switch to combined power management mode.
Defaults
Redundant power management mode
Command Modes
Global configuration mode
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4500 series switch. (Catalyst 4500 series switches only: 4503, 4506, and 4507).
Usage Guidelines
The two power supplies must be the same type and wattage.
Caution
In redundant mode, the power from a single power supply must provide enough power to support the switch configuration.
Table 2-9 lists the maximum available power for chassis and Power over Ethernet for each power supply.
Table 2-9 Available Power
1000 W AC
System1 = 1000
Inline = 0
System = 1667
Inline = 0
2800 W AC
System = 1360
Inline = 1400
System = 2473
Inline = 2333
1 The system power includes power for the supervisor engines, all modules, and the fan tray.
Examples
This example shows how to set the power management mode to combined:
Switch(config)#power redundancy-mode combinedSwitch(config)#Related Commands
pppoe intermediate-agent (global)
To enable the PPPoE Intermediate Agent feature on a switch, use the pppoe intermediate-agent global configuration command. To disable the feature, use the no form of this command.
pppoe intermediate-agent
no pppoe intermediate-agent
Syntax Description
This command has no arguments or keywords.
Defaults
disabled
Command Modes
Global configuration mode
Command History
