To enable Cisco Discovery Protocol (CDP) on an interface and an access point, use the
apcdp command. To remove a CDP on an interface and access point, use the
no form of the command.
Specifies the Ethernet interface number. Values range from 0 to 3.
radioradio-id
Specifies the radio interface number. Values range from 0 to 3.
Command Default
None
Command Modes
Global Configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Examples
This example shows how to enable CDP on an interface:
Switch# ap cdp interface radio 3
client vlan
To configure a wireless LAN interface, use the
clientvlan command. To remove a wireless LAN interface, use the
no form of the command.
clientvlaninterface-name
noclientvlan
Syntax Description
vlan interface-name
Specifies the name of the interface.
Command Default
Disabled
Command Modes
Configuration mode
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Examples
This example shows how to configure vlan10 on an interface:
Switch# client vlan vlan10
debug ilpower
To enable debugging of the power controller and Power over Ethernet (PoE) system, use the debug ilpower command in privileged EXEC mode. To disable debugging, use the no form of this command.
debugilpower
{ cdp | controller | event | ha | ipc | police | port | powerman | registries | sense }
no debug ilpower
{ cdp | controller | event | ha | ipc | police | port | powerman | registries | sense }
Displays PoE Inter-Process Communication (IPC) debug messages.
police
Displays PoE high-availability messages.
port
Displays PoE port manager debug messages.
powerman
Displays PoE power management debug messages.
registries
Displays PoE registries debug messages.
sense
Displays PoE sense debug messages.
Command Default
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
This command is supported only on PoE-capable switches.
When you enable debugging on a switch stack, it is enabled only on the active switch. To enable debugging on a stack member, you can start a session from the active switch by using the sessionswitch-number EXEC command. Then enter the debug command at the command-line prompt of the stack member.
debug interface
To enable debugging of interface-related activities, use the debug interface command in privileged EXEC mode. To disable debugging, use the no form of this command.
no debug interface
{ interface-id | counters
{ exceptions | protocolmemory } | states }
Syntax Description
interface-id
ID of the physical interface. Displays debug messages for the specified physical port, identified by type switch number/module number/port, for example, gigabitethernet 1/0/2.
counters
Displays counters debugging information.
exceptions
Displays debug messages when a recoverable exceptional condition
occurs during the computation of the interface packet and data
rate statistics.
protocol memory
Displays debug messages for memory operations of protocol counters.
states
Displays intermediary debug messages when an interface's state transitions.
Command Default
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
If you do not specify a keyword, all debug messages appear.
The undebug interface command is the same as the no debug interface command.
When you enable debugging on a switch stack, it is enabled only on the active switch. To enable debugging on a stack member, you can start a session from the active switch by using the sessionswitch-number EXEC command. Then enter the debug command at the command-line prompt of the stack member.
debug lldp packets
To enable debugging of Link Layer Discovery Protocol (LLDP) packets, use the debug lldp packets command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug lldp packets
no debug lldp packets
Syntax Description
This command has no keywords or arguments.
Command Default
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
The undebug lldp packets command is the same as the no debug lldp packets command.
When you enable debugging on a switch stack, it is enabled only on the active switch. To enable debugging on a stack member, you can start a session from the active switch by using the sessionswitch-number EXEC command.
debug nmsp
To enable debugging of the Network Mobility Services Protocol (NMSP) on the switch, use the debug nmsp command in privileged EXEC mode. To disable debugging, use the no form of this command.
Displays debug messages for NMSP connection events.
detail
Displays detailed debug messages for NMSP.
error
Displays debugging information for NMSP error messages.
event
Displays debug messages for NMSP events.
message
Displays debugging information for NMSP messages.
rx
Displays debugging information for NMSP receive messages.
tx
Displays debugging information for NMSP transmit messages.
packet
Displays debug messages for NMSP packet events.
switchswitch-number
(Optional) Specifies the switch number for which to display NMSP debugging information.
Command Default
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
The undebug nmsp command is the same as the no debug nmsp command.
debug platform poe
To enable debugging of a Power over Ethernet (PoE) port, use the debug platform poe command in privileged EXEC mode. To disable debugging, use the no form of this command.
(Optional) Displays PoE-related information debug messages.
switchswitch-number
(Optional) Specifies the stack member. This keyword is supported only on stacking-capable switches.
Command Default
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
The undebug platform poe command is the same as the no debug platform poe command.
duplex
To specify the duplex mode of operation for a port, use the duplex command in interface configuration mode. To return to the default value, use the no form of this command.
duplex
{ auto | full | half }
no duplex
{ auto | full | half }
Syntax Description
auto
Enables automatic duplex configuration. The port automatically detects whether it should run in full- or half-duplex mode, depending on the attached device mode.
full
Enables full-duplex mode.
half
Enables half-duplex mode (only for interfaces operating at 10 or 100 Mb/s). You cannot configure half-duplex mode for interfaces operating at 1000 or 10,000 Mb/s.
Command Default
The default is auto for Gigabit Ethernet ports.
You cannot configure the duplex mode on 10-Gigabit Ethernet ports; it is always full.
Duplex options are not supported on the 1000BASE-x (where -x is -BX, -CWDM, -LX, -SX, or -ZX) small form-factor pluggable (SFP) modules.
Command Modes
Interface configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
For Gigabit Ethernet ports, setting the port to auto has the same effect as specifying full if the attached device does not autonegotiate the duplex parameter.
Note
Half-duplex mode is supported on Gigabit Ethernet interfaces if the duplex mode is auto and the connected device is operating at half duplex. However, you cannot configure these interfaces to operate in half-duplex mode.
Certain ports can be configured to be either full duplex or half duplex. How this command is applied depends on the device to which the switch is attached.
If both ends of the line support autonegotiation, we highly recommend using the default autonegotiation settings. If one interface supports autonegotiation and the other end does not, configure duplex and speed on both interfaces, and use the auto setting on the supported side.
If the speed is set to auto, the switch negotiates with the device at the other end of the link for the speed setting and then forces the speed setting to the negotiated value. The duplex setting remains as configured on each end of the link, which could result in a duplex setting mismatch.
You can configure the duplex setting when the speed is set to auto.
Caution
Changing the interface speed and duplex mode configuration might shut down and reenable the interface during the reconfiguration.
You can verify your setting by entering the show interfaces privileged EXEC command.
Examples
This example shows how to configure an interface for full-duplex operation:
Switch(config)# interface gigabitethernet1/0/1Switch(config-if)# duplex full
Displays the administrative and operational status of all interfaces or a specified interface.
errdisable detect cause
To enable error-disable detection for a specific cause or for all causes, use the errdisable detect cause command in global configuration mode. To disable the error-disable detection feature, use the no form of this command.
Enables error detection for all error-disabled causes.
arp-inspection
Enables error detection for dynamic Address Resolution Protocol (ARP) inspection.
bpduguardshutdownvlan
Enables per-VLAN error-disable for BPDU guard.
dhcp-rate-limit
Enables error detection for DHCP snooping.
dtp-flap
Enables error detection for the Dynamic Trunking Protocol (DTP) flapping.
gbic-invalid
Enables error detection for an invalid Gigabit Interface Converter (GBIC) module.
Note
This error refers to an invalid small form-factor pluggable (SFP) module.
inline-power
Enables error detection for the Power over Ethernet (PoE) error-disabled cause.
Note
This keyword is supported only on switches with PoE ports.
l2ptguard
Enables error detection for a Layer 2 protocol-tunnel error-disabled cause.
link-flap
Enables error detection for link-state flapping.
loopback
Enables error detection for detected loopbacks.
pagp-flap
Enables error detection for the Port Aggregation Protocol (PAgP) flap error-disabled cause.
pppoe-ia-rate-limit
Enables error detection for the PPPoE Intermediate Agent rate-limit error-disabled cause.
security-violationshutdownvlan
Enables voice aware 802.1x security.
sfp-config-mismatch
Enables error detection on an SFP configuration mismatch.
Command Default
Detection is enabled for all causes. All causes, except per-VLAN error disabling, are configured to shut down the entire port.
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
A cause (such as a link-flap or dhcp-rate-limit) is the reason for the error-disabled state. When a cause is detected on an interface, the interface is placed in an error-disabled state, an operational state that is similar to a link-down state.
When a port is error-disabled, it is effectively shut down, and no traffic is sent or received on the port. For the bridge protocol data unit (BPDU) guard, voice-aware 802.1x security, and port-security features, you can configure the switch to shut down only the offending VLAN on the port when a violation occurs, instead of shutting down the entire port.
If you set a recovery mechanism for the cause by entering the errdisable recovery global configuration command, the interface is brought out of the error-disabled state and allowed to retry the operation when all causes have timed out. If you do not set a recovery mechanism, you must enter the shutdown and then the no shutdown commands to manually recover an interface from the error-disabled state.
To verify your settings, enter the show errdisable detect privileged EXEC command.
Examples
This example shows how to enable error-disabled detection for the link-flap error-disabled cause:
Switch(config)# errdisable detect cause link-flap
This command shows how to globally configure BPDU guard for a per-VLAN error-disabled state:
Switch(config)# errdisable detect cause bpduguard shutdown vlan
This command shows how to globally configure voice-aware 802.1x security for a per-VLAN error-disabled state:
Switch(config)# errdisable detect cause security-violation shutdown vlan
You can verify your setting by entering the showerrdisabledetect privileged EXEC command.
To enable the error-disabled mechanism to recover from a specific cause, use the errdisable recovery cause command in global configuration mode. To return to the default setting, use the no form of this command.
Enables the timer to recover from all error-disabled causes.
arp-inspection
Enables the timer to recover from the Address Resolution Protocol (ARP) inspection error-disabled state.
bpduguard
Enables the timer to recover from the bridge protocol data unit (BPDU) guard error-disabled state.
channel-misconfig
Enables the timer to recover from the EtherChannel misconfiguration error-disabled state.
dhcp-rate-limit
Enables the timer to recover from the DHCP snooping error-disabled state.
dtp-flap
Enables the timer to recover from the Dynamic Trunking Protocol (DTP) flap error-disabled state.
gbic-invalid
Enables the timer to recover from an invalid Gigabit Interface Converter (GBIC) module error-disabled state.
Note
This error refers to an invalid small form-factor pluggable (SFP) error-disabled state.
inline-power
Enables the timer to recover from the Power over Ethernet (PoE) error-disabled state.
This keyword is supported only on switches with PoE ports.
l2ptguard
Enables the timer to recover from a Layer 2 protocol tunnel error-disabled state.
link-flap
Enables the timer to recover from the link-flap error-disabled state.
loopback
Enables the timer to recover from a loopback error-disabled state.
mac-limit
Enables the timer to recover from the mac limit error-disabled state.
pagp-flap
Enables the timer to recover from the Port Aggregation Protocol (PAgP)-flap error-disabled state.
port-mode-failure
Enables the timer to recover from the port mode change failure error-disabled state.
pppoe-ia-rate-limit
Enables the timer to recover from the PPPoE IA rate limit error-disabled state.
psecure-violation
Enables the timer to recover from a port security violation disable state.
security-violation
Enables the timer to recover from an IEEE 802.1x-violation disabled state.
sfp-config-mismatch
Enables error detection on an SFP configuration mismatch.
storm-control
Enables the timer to recover from a storm control error.
udld
Enables the timer to recover from the UniDirectional Link Detection (UDLD) error-disabled state.
vmps
Enables the timer to recover from the VLAN Membership Policy Server (VMPS) error-disabled state.
Command Default
Recovery is disabled for all causes.
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
A cause (such as all or BDPU guard) is defined as the reason that the error-disabled state occurred. When a cause is detected on an interface, the interface is placed in the error-disabled state, an operational state similar to link-down state.
When a port is error-disabled, it is effectively shut down, and no traffic is sent or received on the port. For the BPDU guard and port-security features, you can configure the switch to shut down only the offending VLAN on the port when a violation occurs, instead of shutting down the entire port.
If you do not enable the recovery for the cause, the interface stays in the error-disabled state until you enter the shutdown and the no shutdown interface configuration commands. If you enable the recovery for a cause, the interface is brought out of the error-disabled state and allowed to retry the operation again when all the causes have timed out.
Otherwise, you must enter the shutdown and then the no shutdown commands to manually recover an interface from the error-disabled state.
You can verify your settings by entering the show errdisable recovery privileged EXEC command.
Examples
This example shows how to enable the recovery timer for the BPDU guard error-disabled cause:
Switch(config)# errdisable recovery cause bpduguard
Displays the administrative and operational status of all interfaces or a specified interface.
errdisable recovery interval
To specify the time to recover from an error-disabled state, use the errdisable recovery interval command in global configuration mode. To return to the default setting, use the no form of this command.
errdisablerecoveryintervaltimer-interval
noerrdisablerecoveryintervaltimer-interval
Syntax Description
timer-interval
Time to recover from the error-disabled state. The range is 30 to 86400 seconds. The same interval is applied to all causes. The default interval is 300 seconds.
Command Default
The default recovery interval is 300 seconds.
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
The error-disabled recovery timer is initialized at a random differential from the configured interval value. The difference between the actual timeout value and the configured value can be up to 15 percent of the configured interval.
You can verify your settings by entering the show errdisable recovery privileged EXEC command.
Examples
This example shows how to set the timer to 500 seconds:
Displays the administrative and operational status of all interfaces or a specified interface.
interface
To configure an interface, use the
interface command.
interface
{ Auto-TemplateAuto-Template interface-number | CapwapCapwap interface-number | Gigabit Ethernet Gigabit Ethernet interface number | Group VI Group VI interface number Internal Interface Internal Interface number Loopback Loopback interface number Null Null interface Port-channel interface numberPort-channel interface number TenGigabit Ethernet interface number Tunnel interface number Vlan interface number }
Syntax Description
Auto-TemplateAuto-template interface-number
Enables you to configure auto-template interface. Values range from 1 to 999.
CapwapCapwap interface number
Enables you to configure CAPWAP tunnel interface. Values range from 0 to 2147483647.
GigabitEthernetGigabit Ethernet interface number
Enables you to configure Gigabit Ethernet IEEE 802.3z interface. Values range from 0 to 9.
Group VI Group VI interface number
Enables you to configure the internal interface. Values range from 0 to 9.
Internal Interface Internal Interface
Enables you to configure internal interface.
LoopbackLoopback Interface number
Enables you to configure loopback interface. Values range from 0 to 2147483647.
NullNull interface number
Enables you to configure null interface. Value is 0.
Port-channelinterface number
Enables you to configure Ethernet channel interfaces. Values range from 1 to 128.
TenGigabitEthernetinterface number
Enables you to configure a 10-Gigabit Ethernet interface. Values range from 0 to 9.
Tunnelinterface number
Enables you to configure the tunnel interface. Values range from 0 to 2147483647.
Vlaninterface number
Enables you to configure switch VLAN interfaces. Values range from 0 to 4098.
Command Default
None
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
You can not use the "no" form of this command.
Examples
This example shows how you can configure interface:
Switch# interface Tunnel 15
interface auto-template
To configure an auto-template interface, use the
interface auto-template command.
interface auto-template
interface-name
Syntax Description
interface-name
Specifies the interface number.
Command Default
Disabled
Command Modes
Global configuration mode
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Examples
Examples
This example shows how to configure interface auto-template:
# interface auto-template
interface range
To configure an interface range, use the
interfacerange command.
interface range
{ Gigabit Ethernet interface-number |
| Loopback interface-number | Port Channel interface-number | TenGigabit Ethernet interface-number Tunnel interface-number Vlan interface-number Macro WORD }
Syntax Description
GigabitEthernetinterface-number
Configures the Gigabit Ethernet IEEE 802.3z interface. Values range from 1 to 9.
Loopbackinterface-number
Configures the loopback interface. Values range from 0 to 2147483647.
Port-Channelinterface-number
Configures 10-Gigabit Ethernet channel of interfaces. Values range from 1 to 128.
TenGigabit Ethernetinterface-number
Configures 10-Gigabit Ethernet interfaces. Values range from 0 to 9.
Tunnel interface-number
Configures the tunnel interface. Values range from 0 to 2147483647.
VLANinterface-number
Configures the switch VLAN interfaces. Values range from 1 to 4095.
MacroWORD
Configures the keywords to interfaces. Support up to 32 characters.
Command Default
None
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Examples
This example shows how you can configure interface range:
Switch# interface range vlan
ip mtu
To set the IP maximum transmission unit (MTU) size of routed packets on all routed ports of the switch or switch stack, use the
ip mtu
command in interface configuration mode. To restore the default IP MTU
size, use the
no
form of this command.
ipmtubytes
noipmtubytes
Syntax Description
bytes
MTU size, in bytes. The range is from 68 up to the system MTU value (in bytes).
Command Default
The default IP MTU size for frames received and sent on all switch interfaces is 1500 bytes.
Command Modes
Interface configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
The upper limit of the IP value is based on the switch or switch stack configuration and refers to the currently applied system MTU value. For more information about setting the MTU sizes, see the system mtu global configuration command.
To return to the default IP MTU setting, you can apply the default ip mtu command or the no ip mtu command on the interface.
You can verify your setting by entering the show ip interfaceinterface-id or show interfacesinterface-id privileged EXEC command.
Examples
The following example sets the maximum IP packet size for VLAN 200 to 1000 bytes:
Switch(config)# interface vlan 200Switch(config-if)# ip mtu 1000
The following example sets the maximum IP packet size for VLAN 200 to the default setting of 1500 bytes:
Switch(config)# interface vlan 200Switch(config-if)# default ip mtu
This is an example of partial output from the show ip interfaceinterface-id command. It displays the current IP MTU setting for the interface.
Switch# show ip interface gigabitethernet4/0/1
GigabitEthernet4/0/1 is up, line protocol is up
Internet address is 18.0.0.1/24
Broadcast address is 255.255.255.255
Address determined by setup command
MTU is 1500 bytes
Helper address is not set
<output truncated>
Sets the global maximum packet size or MTU size for switched packets on Gigabit Ethernet and 10-Gigabit Ethernet ports.
ipv6 mtu
To set the IPv6 maximum transmission unit (MTU) size of routed packets on all routed ports of the switch or switch stack, use the
ipv6 mtu
command in interface configuration mode. To restore the default IPv6 MTU
size, use the
no
form of this command.
ipv6mtubytes
noipv6mtubytes
Syntax Description
bytes
MTU size, in bytes. The range is from 1280 up to the system MTU value (in bytes).
Command Default
The default IPv6 MTU size for frames received and sent on all switch interfaces is 1500 bytes.
Command Modes
Interface configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
The upper limit of the IPv6 MTU value is based on the switch or switch stack configuration and refers to the currently applied system MTU value. For more information about setting the MTU sizes, see the system mtu global configuration command.
To return to the default IPv6 MTU setting, you can apply the default ipv6 mtu command or the no ipv6 mtu command on the interface.
You can verify your setting by entering the show ipv6 interfaceinterface-id or show interfaceinterface-id privileged EXEC command.
Examples
The following example sets the maximum IPv6 packet size for an interface to 2000 bytes:
Switch(config)# interface gigabitethernet4/0/1Switch(config-if)# ipv6 mtu 2000
The following example sets the maximum IPv6 packet size for an interface to the default setting of 1500 bytes:
Switch(config)# interface gigabitethernet4/0/1Switch(config-if)# default ipv6 mtu
This is an example of partial output from the show ipv6 interfaceinterface-id command. It displays the current IPv6 MTU setting for the interface.
Switch# show ipv6 interface gigabitethernet4/0/1
GigabitEthernet4/0/1 is up, line protocol is up
Internet address is 18.0.0.1/24
Broadcast address is 255.255.255.255
Address determined by setup command
MTU is 1500 bytes
Helper address is not set
<output truncated>
Sets the global maximum packet size or MTU size for switched packets on Gigabit Ethernet and 10-Gigabit Ethernet ports.
lldp (interface configuration)
To enable Link Layer Discovery Protocol (LLDP) on an interface, use the lldp command in interface configuration mode. To disable LLDP on an interface, use the no form of this command.
To enable the
logging of Power over Ethernet (PoE) events, use the logging event
power-inline-status command in interface configuration mode. To
disable the logging of PoE status events, use the no form of
this command.
loggingeventpower-inline-status
nologgingeventpower-inline-status
Syntax Description
This command has no arguments or keywords.
Command Default
Logging of PoE events is enabled.
Command Modes
Interface configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
The no form of this command does not disable PoE error events.
Examples
This example shows how to enable logging of PoE events on a port:
Displays the PoE status for the specified PoE port, the specified stack member, or for all PoE ports in the switch stack.
mdix auto
To enable the automatic medium-dependent interface crossover (auto-MDIX) feature on the interface, use the mdix auto command in interface configuration mode. To disable auto-MDIX, use the no form of this command.
mdixauto
nomdixauto
Syntax Description
This command has no arguments or keywords.
Command Default
Auto-MDIX is enabled.
Command Modes
Interface configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
When auto-MDIX is enabled, the interface automatically detects the required cable connection type (straight-through or crossover) and configures the connection appropriately.
When you enable auto-MDIX on an interface, you must also set the interface speed and duplex to auto so that the feature operates correctly.
When auto-MDIX (and autonegotiation of speed and duplex) is enabled on one or both of the connected interfaces, link up occurs, even if the cable type (straight-through or crossover) is incorrect.
You can verify the operational state of auto-MDIX on the interface by entering the showcontrollersethernet-controllerinterface-idphy privileged EXEC command.
Examples
This example shows how to enable auto-MDIX on a port:
Displays per-interface send and receive statistics read from the hardware with keywords.
mode (power-stack configuration)
To configure power stack mode for the power stack, use the mode command in power-stack configuration mode. To return to the default settings, use the no form of the command.
mode
{ power-shared | redundant }
[strict]
no mode
Syntax Description
power-shared
Sets the power stack to operate in power-shared mode. This is the default.
redundant
Sets the power stack to operate in redundant mode. The largest power supply is removed from the power pool to be used as backup power in case one of the other power supplies fails.
strict
(Optional) Configures the power stack mode to run a strict power budget. The stack power needs cannot exceed the available power.
Command Default
The default modes are power-shared and nonstrict.
Command Modes
Power-stack configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
This command is available only on switch stacks running the IP Base or IP Services feature set.
To access power-stack configuration mode, enter the stack-power stackpower stack name global configuration command.
Entering the no mode command sets the switch to the defaults of power-shared and non-strict mode.
Note
For stack power, available power is the total power available for PoE from all power supplies in the power stack, available power is the power allocated to all powered devices connected to PoE ports in the stack, and consumed power is the actual power consumed by the powered devices.
In power-shared mode, all of the input power can be used for loads, and the total available power appears as one large power supply. The power budget includes all power from all supplies. No power is set aside for power supply failures. If a power supply fails, load shedding (shutting down of powered devices or switches) might occur.
In redundant mode, the largest power supply is removed from the power pool to use as backup power in case one of the other power supplies fails. The available power budget is the total power minus the largest power supply. This reduces the available power in the pool for switches and powered devices, but in case of a failure or an extreme power load, there is less chance of having to shut down switches or powered devices.
In strict mode, when a power supply fails and the available power drops below the budgeted power, the system balances the budget through load shedding of powered devices, even if the actual power is less than the available power. In nonstrict mode, the power stack can run in an over-allocated state and is stable as long as the actual power does not exceed the available power. In this mode, a powered device drawing more than normal power could cause the power stack to start shedding loads. This is normally not a problem because most devices do not run at full power. The chances of multiple powered devices in the stack requiring maximum power at the same time is small.
In both strict and nonstrict modes, power is denied when there is no power available in the power budget.
Examples
This is an example of setting the power stack mode for the stack named power1 to power-shared with strict power budgeting. All power in the stack is shared, but when the total available power is allotted, no more devices are allowed power.
This is an example of setting the power stack mode for the stack named power2 to redundant. The largest power supply in the stack is removed from the power pool to provide redundancy in case one of the other supplies fails.
Configures StackPower parameters for the power stack or for a switch in the power stack.
network-policy
To apply a network-policy profile to an interface, use the network-policy command in interface configuration mode. To remove the policy, use the no form of this command.
network-policyprofile-number
nonetwork-policy
Syntax Description
profile-number
The network-policy profile number to apply to the interface.
Command Default
No network-policy profiles are applied.
Command Modes
Interface configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
Use the network-policyprofile number interface configuration command to apply a profile to an interface.
You cannot apply the switchport voice vlan command on an interface if you first configure a network-policy profile on it. However, if switchport voice vlanvlan-id is already configured on the interface, you can apply a network-policy profile on the interface. The interface then has the voice or voice-signaling VLAN network-policy profile applied.
Examples
This example shows how to apply network-policy profile 60 to an interface:
Creates a network-policy profile for the voice application type.
network-policy profile (global configuration)
To create a network-policy profile and to enter network-policy configuration mode, use the network-policy profile command in global configuration mode. To delete the policy and to return to global configuration mode, use the no form of this command.
network-policy profileprofile-number
no network-policy profileprofile-number
Syntax Description
profile-number
Network-policy profile number. The range is 1 to 4294967295.
Command Default
No network-policy profiles are defined.
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
Use the network-policy profile global configuration command to create a profile and to enter network-policy profile configuration mode.
To return to privileged EXEC mode from the network-policy profile configuration mode, enter the exit command.
When you are in network-policy profile configuration mode, you can create the profile for voice and voice signaling by specifying the values for VLAN, class of service (CoS), differentiated services code point (DSCP), and tagging mode.
These profile attributes are contained in the Link Layer Discovery Protocol for Media Endpoint Devices (LLDP-MED) network-policy time-length-value (TLV).
Examples
This example shows how to create network-policy profile 60:
Creates a network-policy profile for the voice application type.
nmsp attachment suppress
To suppress the reporting of attachment information from a specified interface, use the nmsp attachment suppress command in interface configuration mode. To return to the default setting, use the no form of this command.
nmspattachmentsuppress
nonmspattachmentsuppress
Syntax Description
This command has no arguments or keywords.
Command Default
None
Command Modes
Interface configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
Use the nmspattachmentsuppress interface configuration command to configure an interface to not send location and 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:
To enable Energy Efficient Ethernet (EEE) for an interface, use the
power efficient-ethernet auto
command in interface configuration mode. To disable EEE on an interface, use the
no
form of this command.
powerefficient-ethernetauto
nopowerefficient-ethernetauto
Syntax Description
This command has no keywords or arguments.
Command Default
EEE is disabled.
Command Modes
Interface configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
You can enable EEE on devices that support low power idle (LPI) mode. Such devices can save power by entering LPI mode during periods of low utilization. In LPI mode, systems on both ends of the link can save power by shutting down certain services. EEE provides the protocol needed to transition into and out of LPI mode in a way that is transparent to upper layer protocols and applications.
The power efficient-ethernet auto command is available
only if the interface is EEE capable. To check if an interface is EEE capable, use the show eee capabilities EXEC command.
When EEE is enabled, the switch advertises and autonegotiates EEE to its link partner. To view the current EEE status for an interface, use the show eee status EXEC command.
This command does not require a license.
For more information about EEE, see the Interface and Hardware Component Configuration Guide (Catalyst 3850 Switches).
Examples
This example shows how to enable EEE for an interface:
Switch(config-if)# power efficient-ethernet autoSwitch(config-if)#
This example shows how to disable EEE for an interface:
Switch(config-if)# no power efficient-ethernet autoSwitch(config-if)#
power-priority
To configure Cisco StackPower power-priority values for a switch in a power stack and for its
high-priority and low-priority PoE ports, use the
power-priority command in switch stack-power configuration
mode. To return to the default setting, use the no form of the
command.
Sets the power priority for the ports configured as high-priority ports. The
range is 1 to 27, with 1 as the highest priority. The
high value must be lower than the value set
for the low-priority ports and higher than the value set for the switch.
lowvalue
Sets the power priority for the ports configured as low-priority ports. The
range is 1 to 27. The low value must be
higher than the value set for the high-priority ports and the value set for
the switch.
switchvalue
Sets the power priority for the switch. The range is 1 to 27. The
switch value must be lower than the values
set for the low and high-priority ports.
Command Default
If no values are configured, the power stack randomly determines a default priority.
The default ranges are 1 to 9 for switches, 10 to 18 for high-priority ports, 19 to 27
for low-priority ports.
On non-PoE switches, the high and low values (for port priority) have no effect.
Command Modes
Switch stack-power configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
To access switch stack-power configuration mode, enter the stack-power
switchswitch-number global configuration command.
Cisco StackPower power-priority values determine the order for shutting down switches and
ports when power is lost and load shedding must occur. Priority values are from 1 to 27;
the highest numbers are shut down first.
We recommend that you configure different priority values for each switch and for its
high priority ports and low priority ports to limit the number of devices shut down at
one time during a loss of power. If you try to configure the same priority value on
different switches in a power stack, the configuration is allowed, but you receive a
warning message.
Note
This command is available only on switch stacks running the IP Base or IP
Services feature set.
Examples
This is an example of setting the power priority for switch 1 in power stack a to 7, for
the high-priority ports to 11, and for the low-priority ports to 20.
Configures StackPower parameters for the power stack or for a switch in the power stack.
power inline
To configure the power management mode on Power over
Ethernet (PoE) ports, use the power
inline command in interface configuration mode. To return to the
default settings, use the no form of this command.
powerinline
{ auto
[ maxmax-wattage ] | never | port priority
{ high | low }
| static
[ maxmax-wattage ] }
powerinline
{ auto | never | port priority
{ high | low }
| static
[ maxmax-wattage ] }
Syntax Description
auto
Enables powered-device detection. If enough power is available,
automatically allocates power to the PoE port after device detection.
Allocation is first-come, first-serve.
maxmax-wattage
(Optional) Limits the power allowed on the port. The range is 4000 to 30000 mW. If no value is
specified, the maximum is allowed.
never
Disables device detection, and disables power to the port.
port priority
Configures the power priority of a Cisco StackPower port. The default priority is low.
high
Sets the power priority of a Cisco StackPower port to high. In case of a power supply failure, ports configured as high priority are turned off last.
low
Sets the power priority of a Cisco StackPower port to low. In case of a power supply failure, ports configured as low priority are turned off first.
static
Enables powered-device detection. Pre-allocates (reserves) power for a port
before the switch discovers the powered device. This action guarantees that the
device connected to the interface receives enough power.
Command Default
The default is auto (enabled).
The maximum wattage is 30,000 mW.
The default port priority is low.
Command Default
Interface configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
This command is supported only on PoE-capable ports. If you enter this command on a port
that does not support PoE, this error message appears:
Switch(config)# interface gigabitethernet1/0/1Switch(config-if)# power inline auto
^
% Invalid input detected at '^' marker.
In a switch stack, this command is supported on all ports in the stack that support
PoE.
Use the maxmax-wattage option to disallow higher-power powered devices. With
this configuration, when the powered device sends Cisco Discovery Protocol (CDP)
messages requesting more power than the maximum wattage, the switch removes power from
the port. If the powered-device IEEE class maximum is greater than the maximum wattage,
the switch does not power the device. The power is reclaimed into the global power
budget.
Note
The switch never powers any class 0 or class 3 device if the power inline max max-wattage command is configured for less than 30 W.
If the switch denies power to a powered device (the powered device requests more power
through CDP messages or if the IEEE class maximum is greater than the maximum wattage),
the PoE port is in a power-deny state. The switch generates a system message, and the
Oper column in the show power inline privileged EXEC command
output shows power-deny.
Use the power inline static maxmax-wattage command to give a port high priority. The switch
allocates PoE to a port configured in static mode before allocating power to a port
configured in auto mode. The switch reserves power for the static port when it is
configured rather than upon device discovery. The switch reserves the power on a static
port even when there is no connected device and whether or not the port is in a shutdown
or in a no shutdown state. The switch allocates the configured maximum wattage to the
port, and the amount is never adjusted through the IEEE class or by CDP messages from
the powered device. Because power is pre-allocated, any powered device that uses less
than or equal to the maximum wattage is guaranteed power when it is connected to a
static port. However, if the powered device IEEE class is greater than the maximum
wattage, the switch does not supply power to it. If the switch learns through CDP
messages that the powered device needs more than the maximum wattage, the powered device
is shut down.
If the switch cannot pre-allocate power when a port is in static mode (for example,
because the entire power budget is already allocated to other auto or static ports),
this message appears: Command rejected: power inline static: pwr not available. The port
configuration remains unchanged.
When you configure a port by using the power inline auto or
the power inline static interface configuration command, the
port autonegotiates by using the configured speed and duplex settings. This is necessary
to determine the power requirements of the connected device (whether or not it is a
powered device). After the power requirements have been determined, the switch hardcodes
the interface by using the configured speed and duplex settings without resetting the
interface.
When you configure a port by using the power inline never
command, the port reverts to the configured speed and duplex settings.
If a port has a Cisco powered device connected to it, you should not use the
power inline never command to configure the port. A
false link-up can occur, placing the port in an error-disabled state.
Use the power inline port priority {high | low} command to configure the power priority of a PoE port in a switch stack using StackPower. Powered devices connected to ports with low port priority are shut down first in case of a power shortage. Although this command is visible on switches that are not stacking-capable, it has no effect because StackPower is not supported.
You can verify your settings by entering the show power inline
EXEC command.
Examples
This example shows how to enable detection of a powered device and to automatically
power a PoE port on a switch:
Switch(config)# interface gigabitethernet1/0/2Switch(config-if)# power inline auto
This example shows how to configure a PoE port on a switch to allow a class 1 or a
class 2 powered device:
Switch(config)# interface gigabitethernet1/0/2Switch(config-if)# power inline auto max 7000
This example shows how to disable powered-device detection and to not power a PoE port
on a switch:
Switch(config)# interface gigabitethernet1/0/2Switch(config-if)# power inline never
This example shows how to set the priority of a port to high, so that it would be one of the last ports to be shut down in case of power supply failure:
Switch(config)# interface gigabitethernet1/0/2Switch(config-if)# power inline port priority high
Displays the PoE status for the specified PoE port, the specified stack member, or for all PoE ports in the switch stack.
power inline police
To enable policing of real-time power consumption on a powered device, use the
power
inline police command in interface configuration mode. To disable this
feature, use the no form of this command
powerinlinepolice
[ action
{ errdisable | log } ]
nopowerinlinepolice
Syntax Description
action errdisable
(Optional) Configures the switch to turn off power to the port if the
real-time power consumption exceeds the maximum power allocation on the
port. This is the default action.
action log
(Optional) Configures the switch to generate a syslog message while still
providing power to a connected device if the real-time power consumption
exceeds the maximum power allocation on the port.
Command Default
Policing of the real-time power consumption of the powered device is disabled.
Command Modes
Interface configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
This command is supported only on Power over Ethernet (PoE)-capable ports. If you enter
this command on a switch or port that does not support PoE, an error message
appears.
In a switch stack, this command is supported on all switches or ports in the stack that
support PoE and real-time power-consumption monitoring.
When policing of the real-time power consumption is enabled, the switch takes action
when a powered device consumes more power than the allocated maximum amount.
When PoE is enabled, the switch senses the real-time power consumption of the powered
device. This feature is called power monitoring or power sensing. The
switch also polices the power usage with the power policing feature.
When power policing is enabled, the switch uses one of the these values as the cutoff
power on the PoE port in this order:
The user-defined power level that limits the power allowed on the port when you
enter the power inline auto maxmax-wattage or the power inline static maxmax-wattage interface configuration command
The switch automatically sets the power usage of the device by using CDP power
negotiation or by the IEEE classification and LLPD power negotiation.
If you do not manually configure the cutoff-power value, the switch automatically determines it by using CDP power negotiation or the device IEEE classification and LLDP power negotiation. If CDP or LLDP are not enabled, the default value of 30 W is applied. However without CDP or LLDP, the switch does not allow devices to consume more than 15.4 W of power because values from 15400 to 30000 mW are only allocated based on CDP or LLDP requests. If a powered device consumes more than 15.4 W without CDP or LLDP negotiation, the device might be in violation of the maximum current Imax limitation and might experience an Icut fault for drawing more current than the maximum. The port remains in the fault state for a time before attempting to power on again. If the port continuously draws more than 15.4 W, the cycle repeats.
When a powered device connected to a PoE+ port restarts and sends a CDP or LLDP
packet with a power TLV, the switch locks to the power-negotiation protocol of that
first packet and does not respond to power requests from the other protocol. For
example, if the switch is locked to CDP, it does not provide power to devices that
send LLDP requests. If CDP is disabled after the switch has locked on it, the switch
does not respond to LLDP power requests and can no longer power on any accessories.
In this case, you should restart the powered device.
If power policing is enabled, the switch polices power usage by comparing the real-time
power consumption to the maximum power allocated on the PoE port. If the device uses
more than the maximum power allocation (or cutoff power) on the port, the switch
either turns power off to the port, or the switch generates a syslog message and updates
the LEDs (the port LEDs are blinking amber) while still providing power to the device.
To configure the switch to turn off power to the port and put the port in the
error-disabled state, use the power inline police interface
configuration command.
To configure the switch to generate a syslog message while still providing power to
the device, use the power inline police action log command.
If you do not enter
the action log keywords, the default action is to shut
down the port, turn off power to it, and put the port in the PoE error-disabled
state. To configure the PoE port to automatically recover from the error-disabled
state, use the errdisable detect cause inline-power
global configuration command to enable error-disabled detection for the PoE cause
and the errdisable recovery cause inline-power intervalinterval global configuration command to enable the recovery
timer for the PoE error-disabled cause.
Caution
If policing is disabled, no action occurs when the powered device consumes more than
the maximum power allocation on the port, which could adversely affect the
switch.
You can verify your settings by entering the show power inline
police privileged EXEC command.
Examples
This example shows how to enable policing of the power consumption and configuring the
switch to generate a syslog message on the PoE port on a switch:
Switch(config)# interface gigabitethernet1/0/2Switch(config-if)# power inline police action log
Displays fan, temperature, RPS availability, and power information.
show CAPWAP summary
To display all the CAPWAP tunnels established by the controller to access points and other mobility controllers use the
showCAPWAP summary command.
showCAPWAP summary
Syntax Description
This command has no keywords or arguments.
Command Default
None
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Examples
This example shows how to display CAPWAP tunnels established by the controllers to the access points and other controllers.
Switch# show capwap summary
CAPWAP Tunnels General Statistics:
Number of Capwap Data Tunnels = 8
Number of Capwap Mobility Tunnels = 0
Number of Capwap Multicast Tunnels = 0
Name APName Type PhyPortIf Mode McastIf
------ -------------------------------- ---- --------- ---------
-------
Ca4 AP-Behind-Router data - unicast -
Ca0 AP1142-kat data - unicast -
Ca5 APRFCHAMBER2-EDISON data - unicast -
Ca6 KATANA_2_RF data - unicast -
Ca1 AP-1040-RF data - unicast -
Ca7 KATANA_1_RF data - unicast -
Ca2 AP3500-2027 data - unicast -
Ca3 AP-1040-out data - unicast -
show controllers cpu-interface
To display the state of the CPU network interface ASIC and the send and receive statistics for packets reaching the CPU, use the showcontrollerscpu-interface command in privileged EXEC mode.
Displays the administrative and operational status of all interfaces or a specified interface.
show controllers ethernet-controller
To display per-interface send and receive statistics read from the hardware with keywords, use the showcontrollersethernet-controller command in EXEC mode.
(Optional) Displays states related to down-when-looped detection.
phy
(Optional) Displays the status of the internal registers on the switch physical layer device (PHY) for the device or the interface. This display includes the operational state of the automatic medium-dependent interface crossover (auto-MDIX) feature on an interface.
detail
(Optional) Displays details about the PHY internal registers.
port-asic
(Optional) Displays information about the port ASIC internal registers.
statistics
Displays port ASIC statistics, including the Rx/Sup Queue and miscellaneous statistics.
exceptions
Displays port ASIC exception statistics.
interfaceinterface-id
Specifies the interface for which to display port ASIC statistics.
l2
Displays statistics for the Layer 2 interface.
l3
Displays statistics for the Layer 3 interface.
l3-ifidif-id
Specifies the Layer 3 IF interface ID for which to display port ASIC statistics.
port-ifidif-id
Specifies the PortIF interface ID for which to display port ASIC statistics.
vlan-ifidif-id
Specifies the VLANIF interface ID for which to display port ASIC statistics.
switchstack-member-number
(Optional) Specifies the stack member number for which to display send and receive statistics.
asicasic-number
(Optional) Specifies the ASIC number.
Command Modes
User EXEC (only supported with the interface-id keywords in user EXEC mode)
Privileged EXEC
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
Without keywords, this command provides the RMON statistics for all interfaces or for the specified interface.
To display the interface internal registers, use the phy keyword. To display information about the port ASIC, use the port-asic keyword.
When you enter the phy or port-asic keywords, the displayed information is useful primarily for Cisco technical support representatives troubleshooting the switch.
Examples
This is an example of output from the showcontrollersethernet-controller command for an interface:
Switch# show controllers ethernet-controller gigabitethernet1/0/1
Transmit GigabitEthernet1/0/1 Receive
19216827 Total bytes 0 Total bytes
41935 Unicast frames 0 Unicast frames
2683840 Unicast bytes 0 Unicast bytes
216662 Multicast frames 0 Multicast frames
16532987 Multicast bytes 0 Multicast bytes
0 Broadcast frames 0 Broadcast frames
0 Broadcast bytes 0 Broadcast bytes
0 System FCS error frames 0 IpgViolation frames
0 MacUnderrun frames 0 MacOverrun frames
0 Pause frames 0 Pause frames
0 Cos 0 Pause frames 0 Cos 0 Pause frames
0 Cos 1 Pause frames 0 Cos 1 Pause frames
0 Cos 2 Pause frames 0 Cos 2 Pause frames
0 Cos 3 Pause frames 0 Cos 3 Pause frames
0 Cos 4 Pause frames 0 Cos 4 Pause frames
0 Cos 5 Pause frames 0 Cos 5 Pause frames
0 Cos 6 Pause frames 0 Cos 6 Pause frames
0 Cos 7 Pause frames 0 Cos 7 Pause frames
0 Oam frames 0 OamProcessed frames
0 Oam frames 0 OamDropped frames
251598 Minimum size frames 0 Minimum size frames
0 65 to 127 byte frames 0 65 to 127 byte frames
0 128 to 255 byte frames 0 128 to 255 byte frames
6999 256 to 511 byte frames 0 256 to 511 byte frames
0 512 to 1023 byte frames 0 512 to 1023 byte frames
0 1024 to 1518 byte frames 0 1024 to 1518 byte frames
0 1519 to 2047 byte frames 0 1519 to 2047 byte frames
0 2048 to 4095 byte frames 0 2048 to 4095 byte frames
0 4096 to 8191 byte frames 0 4096 to 8191 byte frames
0 8192 to 16383 byte frames 0 8192 to 16383 byte frames
0 16384 to 32767 byte frame 0 16384 to 32767 byte frame
0 > 32768 byte frames 0 > 32768 byte frames
0 Late collision frames 0 SymbolErr frames
0 Excess Defer frames 0 Collision fragments
0 Good (1 coll) frames 0 ValidUnderSize frames
0 Good (>1 coll) frames 0 InvalidOverSize frames
0 Deferred frames 0 ValidOverSize frames
0 Gold frames dropped 0 FcsErr frames
0 Gold frames truncated
0 Gold frames successful
0 1 collision frames
0 2 collision frames
0 3 collision frames
0 4 collision frames
0 5 collision frames
0 6 collision frames
0 7 collision frames
0 8 collision frames
0 9 collision frames
0 10 collision frames
0 11 collision frames
0 12 collision frames
0 13 collision frames
0 14 collision frames
0 15 collision frames
0 Excess collision frames
LAST UPDATE 850 msecs AGO
Table 1 Transmit Field Descriptions
Field
Description
Total bytes
The total number of bytes sent on an interface.
Unicast Frames
The total number of frames sent to unicast addresses.
Unicast bytes
The total number of bytes sent to unicast addresses.
Multicast frames
The total number of frames sent to multicast addresses.
Multicast bytes
The total number of bytes sent to multicast addresses.
Broadcast frames
The total number of frames sent to broadcast addresses.
Broadcast bytes
The total number of bytes sent to broadcast addresses.
System FCS error frames
The total number of frames that fail the Frame Check Sequence (FCS).
MacUnderrun frames
The total number of frames that have MAC Underrun errors.
Pause frames
The total number of pause frames sent on an interface.
Cos x Pause frames
The total number of class of service (CoS) x pause frames sent on an interface.
Oam frames
The total number of Ethernet Operations, Administration, and Maintenance (OAM) frames sent on an interface.
Minimum size frames
The number of frames that are the minimum allowed frame size.
65 to 127 byte frames
The total number of frames sent on an interface that are 65 to 127 bytes.
128 to 255 byte frames
The total number of frames sent on an interface that are 128 to 255 bytes.
256 to 511 byte frames
The total number of frames sent on an interface that are 256 to 511 bytes.
512 to 1023 byte frames
The total number of frames sent on an interface that are 512 to 1023 bytes.
1024 to 1518 byte frames
The total number of frames sent on an interface that are 1024 to 1518 bytes.
1519 to 2047 byte frames
The total number of frames sent on an interface that are 1519 to 2047 bytes.
2048 to 4095 byte frames
The total number of frames sent on an interface that are 2048 to 4095 bytes.
4096 to 8191 byte frames
The total number of frames sent on an interface that are 4096 to 8191 bytes.
8192 to 16383 byte frames
The total number of frames sent on an interface that are 8192 to 16383 bytes.
16384 to 32767 byte frames
The total number of frames sent on an interface that are 16384 to 32767 bytes.
> 32768 byte frames
The total number of frames sent on an interface that are greater than 32768 bytes.
Late collision frames
After a frame is sent, the number of frames dropped because late collisions were detected while the frame was sent.
Excess defer frames
The number of frames that are not sent after the time exceeds the maximum-packet time.
Good (1 coll) frames
The number of frames that are successfully sent on an interface after one collision occurs. This value does not include the number of frames that are not successfully sent after one collision occurs.
Good (>1 coll) frames
The number of frames that are successfully sent on an interface after more than one collision occurs. This value does not include the number of frames that are not successfully sent after more than one collision occurs.
Deferred frames
The number of frames that are not sent after the time exceeds 2*maximum-packet time.
Gold frames dropped
The number of gold frames that are dropped.
Gold frames truncated
The number of gold frames that are truncated.
Gold frames successful
The number of gold frames that are successful.
1 collision frames
The number of frames that are successfully sent on an interface after one collision occurs.
2 collision frames
The number of frames that are successfully sent on an interface after two collisions occur.
3 collision frames
The number of frames that are successfully sent on an interface after three collisions occur.
4 collision frames
The number of frames that are successfully sent on an interface after four collisions occur.
5 collision frames
The number of frames that are successfully sent on an interface after five collisions occur.
6 collision frames
The number of frames that are successfully sent on an interface after six collisions occur.
7 collision frames
The number of frames that are successfully sent on an interface after seven collisions occur.
8 collision frames
The number of frames that are successfully sent on an interface after eight collisions occur.
9 collision frames
The number of frames that are successfully sent on an interface after nine collisions occur.
10 collision frames
The number of frames that are successfully sent on an interface after ten collisions occur.
11 collision frames
The number of frames that are successfully sent on an interface after 11 collisions occur.
12 collision frames
The number of frames that are successfully sent on an interface after 12 collisions occur.
13 collision frames
The number of frames that are successfully sent on an interface after 13 collisions occur.
14 collision frames
The number of frames that are successfully sent on an interface after 14 collisions occur.
15 collision frames
The number of frames that are successfully sent on an interface after 15 collisions occur.
Excess collisions
The number of frames that could not be sent on an interface after 16 collisions occur.
Table 2 Receive Field Descriptions
Field
Description
Total Bytes
The total amount of memory (in bytes) used by frames received on an interface, including the FCS1 value and the incorrectly formed frames. This value excludes the frame header bits.
Unicast frames
The total number of frames successfully received on the interface that are directed to unicast addresses.
Unicast bytes
The total amount of memory (in bytes) used by unicast frames received on an interface, including the FCS value and the incorrectly formed frames. This value excludes the frame header bits.
Multicast frames
The total amount of memory (in bytes) used by multicast frames received on an interface, including the FCS value and the incorrectly formed frames. This value excludes the frame header bits.
Multicast bytes
The total number of bytes successfully received on the interface that are directed to multicast addresses.
Broadcast frames
The total number of frames successfully received on an interface that are directed to broadcast addresses.
Broadcast bytes
The total amount of memory (in bytes) used by broadcast frames received on an interface, including the FCS value and the incorrectly formed frames. This value excludes the frame header bits.
IpgViolation frames
The total number of frames with an interpacket gap (IPG) violation.
MacOverrun frames
The total number of frames with MacOverrun errors.
Pause frames
The total number of pause frames received on an interface.
Cos x Pause frames
The total number of class of service (CoS) x pause frames received on an interface.
OamProcessed
The total number of Ethernet Operations, Administration, and Maintenance (OAM) frames that are processed on an interface.
OamDropped
The total number of Ethernet Operations, Administration, and Maintenance (OAM) frames that are dropped on an interface.
Minimum size frames
The total number of frames that are the minimum frame size.
65 to 127 byte frames
The total number of frames that are from 65 to 127 bytes.
128 to 255 byte frames
The total number of frames that are from 128 to 255 bytes.
256 to 511 byte frames
The total number of frames that are from 256 to 511 bytes.
512 to 1023 byte frames
The total number of frames that are from 512 to 1023 bytes.
1024 to 1518 byte frames
The total number of frames that are from 1024 to 1518 bytes.
1519 to 2047 byte frames
The total number of frames that are from 1519 to 2047 bytes.
2048 to 4095 byte frames
The total number of frames that are from 2048 to 4095 bytes.
4096 to 8191 byte frames
The total number of frames that are from 4096 to 8191 bytes.
8192 to 16383 byte frames
The total number of frames that are from 8192 to 16383 bytes.
16384 to 32767 byte frames
The total number of frames that are from 16384 to 32767 bytes.
> 32768 byte frames
The total number of frames that are greater than 32768 bytes.
Symbol error frames
The number of frames received on an interface that have symbol errors.
Collision fragments
The number of collision fragments received on an interface.
Valid undersize frames
The number of frames received on an interface that are smaller than 64 bytes (or 68 bytes for VLAN-tagged frames) and that have valid FCS values. The frame size includes the FCS bits but excludes the frame header bits.
Invalid oversize frames
The number of frames received that were larger than maximum allowed maximum transmission unit (MTU) size (including the FCS bits and excluding the frame header) and that have either an FCS error or an alignment error.
Valid oversize frames
The number of frames received on an interface that are larger than the maximum allowed frame size and have valid FCS values. The frame size includes the FCS value but does not include the VLAN tag.
FcsErr frames
The total number of frames received on an interface that have a valid length (in bytes) but do not have the correct FCS values.
Table 3 Show controllers utilization Field Descriptions
Field
Description
Receive Bandwidth Percentage Utilization
Displays the received bandwidth usage of the switch, which is the sum of the received traffic on all the ports divided by the switch receive capacity.
Receive Bandwidth Percentage Utilization
Displays the received bandwidth usage of the switch, which is the sum of the received traffic on all the ports divided by the switch receive capacity.
Transmit Bandwidth Percentage Utilization
Displays the transmitted bandwidth usage of the switch, which is the sum of the transmitted traffic on all the ports divided it by the switch transmit capacity.
Average Switch Percentage Utilization
Displays the average of the transmitted and received bandwidth usage of the switch.
show eee
To display Energy Efficient Ethernet (EEE) information for an interface, use the
show eee
command in EXEC mode.
showeee
{ capabilities | status }
interfaceinterface-id
Syntax Description
capabilities
Displays EEE capabilities for the specified interface.
status
Displays EEE status information for the specified interface.
interfaceinterface-id
Specifies the interface for which to display EEE capabilities or status information.
Command Default
None
Command Modes
User EXEC
Privileged EXEC
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
You can enable EEE on devices that support low power idle (LPI) mode. Such devices can save power by entering LPI mode during periods of low power utilization. In LPI mode, systems on both ends of the link can save power by shutting down certain services. EEE provides the protocol needed to transition into and out of LPI mode in a way that is transparent to upper layer protocols and applications.
To check if an interface is EEE capable, use the show eee capabilities command. You can enable EEE on an interface that is EEE capable by using the power efficient-ethernet auto interface configuration command.
To view the EEE status, LPI status, and wake error count information for an interface, use the show eee status command.
For more information about EEE, see the Interface and Hardware Component Configuration Guide (Catalyst 3850 Switches).
Examples
This is an example of output from the show eee capabilities command on an interface where EEE is enabled:
Switch# show eee capabilities interface gigabitethernet1/0/1
Gi1/0/1
EEE(efficient-ethernet): yes (100-Tx and 1000T auto)
Link Partner : yes (100-Tx and 1000T auto)
This is an example of output from the show eee capabilities command on an interface where EEE is not enabled:
Switch# show eee capabilities interface gigabitethernet2/0/1
Gi2/0/1
EEE(efficient-ethernet): not enabled
Link Partner : not enabled
This is an example of output from the show eee status command on an interface where EEE is enabled and operational. The table that follows describes the fields in the display.
Switch# show eee status interface gigabitethernet1/0/4
Gi1/0/4 is up
EEE(efficient-ethernet): Operational
Rx LPI Status : Received
Tx LPI Status : Received
Wake Error Count : 0
This is an example of output from the show eee status command on an interface where EEE operational and the ports are in low power save mode:
Switch# show eee status interface gigabitethernet1/0/3
Gi1/0/3 is up
EEE(efficient-ethernet): Operational
Rx LPI Status : Low Power
Tx LPI Status : Low Power
Wake Error Count : 0
This is an example of output from the show eee status command on an interface where EEE is not enabled because a remote link partner is incompatible with EEE:
Switch# show eee status interface gigabitethernet1/0/3
Gi1/0/3 is up
EEE(efficient-ethernet): Disagreed
Rx LPI Status : None
Tx LPI Status : None
Wake Error Count : 0
Table 4 show eee status Field Descriptions
Field
Description
EEE (efficient-ethernet)
The EEE status for the interface. This field can have any of the following values:
N/A—The port is not capable of EEE.
Disabled—The port EEE is disabled.
Disagreed—The port EEE is not set because a remote link partner might be incompatible with EEE; either it is not EEE capable, or its EEE setting is incompatible.
Operational—The port EEE is enabled and operating.
If the interface speed is configured as 10 Mbps, EEE
is disabled internally. When the interface
speed moves back to auto, 100 Mbps or 1000 Mbps, EEE becomes active
again.
Rx/Tx LPI Status
The Low Power Idle (LPI) status for the link partner. These fields can have any of the following values:
N/A—The port is not capable of EEE.
Interrupted—The link partner is in the process of moving to low power mode.
Low Power—The link partner is in low power mode.
None— EEE is disabled or not capable at the link partner side.
Received—The link partner is in low power mode and there is traffic activity.
If an interface is configured as half-duplex, the LPI status is None, which means the interface cannot be in low power mode until it is configured as full-duplex.
Wake Error Count
The number of PHY wake-up faults that have occurred. A wake-up fault can occur when EEE is enabled and the connection to the link partner is broken.
This information is
useful for PHY debugging.
show env
To
display fan, temperature, redundant power system (RPS) availability, and power
information, use the show env command in EXEC mode.
showenv
{ all | fan | power
[ all | switch
[ stack-member-number ] ] | stack
[ stack-member-number ]
| temperature
[ status ] }
Syntax Description
all
Displays the fan and temperature environmental status and the status of the
internal power supplies and the RPS.
fan
Displays the switch fan status.
power
Displays the internal power status of the active switch.
all
(Optional) Displays the status of all the internal power supplies in a
standalone switch when the command is entered on the switch, or in all the
stack members when the command is entered on the active switch.
switch
(Optional) Displays the status of the internal power supplies for each
switch in the stack or for the specified switch.
This keyword is available only on stacking-capable switches.
stack-member-number
(Optional) Number of the stack member for which to display the status of the internal power supplies or the environmental status. The range is 1 to 9,
depending on the switch member numbers in the stack.
stack
Displays all environmental status for each switch in the stack or for the
specified switch.
This keyword is available only on stacking-capable switches.
temperature
Displays the switch temperature status.
status
(Optional) Displays the switch internal temperature (not the external
temperature) and the threshold values.
Command Default
None
Command Modes
User EXEC
Privileged EXEC
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
Use the showenv EXEC command to display the information for
the switch being accessed—a standalone switch or the active switch. Use this command with
the stack and switch keywords to
display all information for the stack or for the specified stack member.
If you enter the showenvtemperaturestatus command, the
command output shows the switch temperature state and the threshold level.
You can also use the showenvtemperature command to display
the switch temperature status. The command output shows the green and yellow states as
OK and the red state as FAULTY. If you enter the showenvall command, the command output is the same as the showenvtemperaturestatus command output.
Examples
This is an example of output from the showenvall command:
Switch>show env all
Switch 1 FAN 1 is OK
Switch 1 FAN 2 is OK
Switch 1 FAN 3 is OK
FAN PS-1 is NOT PRESENT
FAN PS-2 is OK
Switch 1: SYSTEM TEMPERATURE is OK
SW PID Serial# Status Sys Pwr PoE Pwr Watts
-- ------------------ ---------- --------------- ------- ------- -----
1A Not Present
1B C3KX-PWR-715WAC LIT150119Z1 OK Good Good 715
This is an example of output from the showenvfan
command:
Switch>show env fan
Switch 1 FAN 1 is OK
Switch 1 FAN 2 is OK
Switch 1 FAN 3 is OK
FAN PS-1 is NOT PRESENT
FAN PS-2 is OK
This is an example of output from the showenvpower
command:
Switch>show env power
SW PID Serial# Status Sys Pwr PoE Pwr Watts
-- ------------------ ---------- --------------- ------- ------- -----
1A Not Present
1B C3KX-PWR-715WAC LIT150119Z1 OK Good Good 715
This is an example of output from the showenvpowerall command
on the active switch:
Switch# show env power all
SW PID Serial# Status Sys Pwr PoE Pwr Watts
-- ------------------ ---------- --------------- ------- ------- -----
1A Not Present
1B C3KX-PWR-715WAC LIT150119Z1 OK Good Good 715
This is an example of output from the showenvstack command
on the active switch:
Switch> show env stack
SWITCH: 1
Switch 1 FAN 1 is OK
Switch 1 FAN 2 is OK
Switch 1 FAN 3 is OK
FAN PS-1 is NOT PRESENT
FAN PS-2 is OK
Switch 1: SYSTEM TEMPERATURE is OK
Temperature Value: 28 Degree Celsius
Temperature State: GREEN
Yellow Threshold : 41 Degree Celsius
Red Threshold : 56 Degree Celsius
This example shows how to display the temperature value, state, and the threshold values
on a standalone switch. The table describes the temperature states in the command
output.
Switch> show env temperature status
Temperature Value: 33 Degree Celsius
Temperature State: GREEN
Yellow Threshold : 65 Degree Celsius
Red Threshold : 75 Degree Celsius
Table 5 States in the show env temperature status Command Output
State
Description
Green
The switch temperature is in the normal operating range.
Yellow
The temperature is in the warning range. You should check the
external temperature around the switch.
Red
The temperature is in the critical range. The switch might not run
properly if the temperature is in this range.
show errdisable detect
To display error-disabled detection status, use the show errdisable detect command in EXEC mode.
show errdisable detect
Syntax Description
This command has no arguments or keywords.
Command Default
None
Command Modes
User EXEC
Privileged EXEC
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
A gbic-invalid error reason refers to an invalid small form-factor pluggable (SFP) module.
The error-disable reasons in the command output are listed in alphabetical order. The mode column shows how error-disable is configured for each feature.
You can configure error-disabled detection in these modes:
port mode—The entire physical port is error-disabled if a violation occurs.
vlan mode—The VLAN is error-disabled if a violation occurs.
port/vlan mode—The entire physical port is error-disabled on some ports and is per-VLAN error-disabled on other ports.
Examples
This is an example of output from the show errdisable detect command:
Switch> show errdisable detect
ErrDisable Reason Detection Mode
----------------- --------- ----
arp-inspection Enabled port
bpduguard Enabled vlan
channel-misconfig Enabled port
community-limit Enabled port
dhcp-rate-limit Enabled port
dtp-flap Enabled port
gbic-invalid Enabled port
inline-power Enabled port
invalid-policy Enabled port
l2ptguard Enabled port
link-flap Enabled port
loopback Enabled port
lsgroup Enabled port
pagp-flap Enabled port
psecure-violation Enabled port/vlan
security-violatio Enabled port
sfp-config-mismat Enabled port
storm-control Enabled port
udld Enabled port
vmps Enabled port
To display the administrative and operational status of all interfaces or for a specified interface, use the show interfaces command in privileged EXEC mode.
(Optional) ID of the interface. Valid interfaces include physical ports (including type, stack member for stacking-capable switches, module, and port number) and port channels. The port channel range is 1 to 128.
vlanvlan-id
(Optional) VLAN identification. The range is 1 to 4094.
accounting
(Optional) Displays accounting information on the interface, including active protocols and input and output packets and octets.
Note
The display shows only packets processed in software; hardware-switched packets do not appear.
capabilities
(Optional) Displays the capabilities of all interfaces or the specified interface, including the features and options that you can configure on the interface. Though visible in the command line help, this option is not available for VLAN IDs.
modulenumber
(Optional) Displays capabilities of all interfaces on the switch or specified stack member.
The range is 1 to 9.
This option is not available if you entered a specific interface ID.
debounce
(Optional) Displays port debounce timer information for an interface.
description
(Optional) Displays the administrative status and description set for an interface.
(Optional) Displays interface flow control information.
mtu
(Optional) Displays the MTU for each interface or for the specified interface.
pruning
(Optional) Displays trunk VTP pruning information for the interface.
stats
(Optional) Displays the input and output packets by switching the path for the interface.
status
(Optional) Displays the status of the interface. A status of unsupported in the Type field means that a non-Cisco small form-factor pluggable (SFP) module is inserted in the module slot.
err-disabled
(Optional) Displays interfaces in an error-disabled state.
inactive
(Optional) Displays interfaces in an inactive state.
trunk
(Optional) Displays interface trunk information. If you do not specify an interface, only information for active trunking ports appears.
Note
Though visible in the command-line help strings, the crb, fair-queue, irb, mac-accounting, precedence, random-detect, and rate-limit keywords are not supported.
Command Default
None
Command Modes
Privileged EXEC
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
The show interfaces capabilities command with different keywords has these results:
Use the show interface capabilities modulenumber command to display the capabilities of all interfaces on that switch in the stack. If there is no switch with that module number in the stack, there is no output.
Use the show interfacesinterface-idcapabilities to display the capabilities of the specified interface.
Use the show interfaces capabilities (with no module number or interface ID) to display the capabilities of all interfaces in the stack.
Examples
This is an example of output from the show interfaces command for an interface on stack member 3:
Switch# show interfaces gigabitethernet3/0/2
GigabitEthernet3/0/2 is down, line protocol is down (notconnect)
Hardware is Gigabit Ethernet, address is 2037.064d.4381 (bia 2037.064d.4381)
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Auto-duplex, Auto-speed, media type is 10/100/1000BaseTX
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out
This is an example of patrial output from the show interfaces accounting command:
Switch# show interfaces accounting
Vlan1
Protocol Pkts In Chars In Pkts Out Chars Out
IP 0 0 6 378
Vlan200
Protocol Pkts In Chars In Pkts Out Chars Out
No traffic sent or received on this interface.
GigabitEthernet0/0
Protocol Pkts In Chars In Pkts Out Chars Out
Other 165476 11417844 0 0
Spanning Tree 1240284 64494768 0 0
ARP 7096 425760 0 0
CDP 41368 18781072 82908 35318808
GigabitEthernet1/0/1
Protocol Pkts In Chars In Pkts Out Chars Out
No traffic sent or received on this interface.
GigabitEthernet1/0/2
Protocol Pkts In Chars In Pkts Out Chars Out
No traffic sent or received on this interface.
<output truncated>
This is an example of output from the show interfaces capabilities command for an interface:
Switch# show interfaces gigabitethernet1/0/2 capabilities
GigabitEthernet1/0/2
Model: UA-3850-24-CR
Type: 10/100/1000BaseTX
Speed: 10,100,1000,auto
Duplex: full,half,auto
Trunk encap. type: 802.1Q
Trunk mode: on,off,desirable,nonegotiate
Channel: yes
Fast Start: yes
QoS scheduling: rx-(not configurable on per port basis),
tx-(4q3t) (3t: Two configurable values and one fixed.)
CoS rewrite: yes
ToS rewrite: yes
UDLD: yes
Inline power: no
SPAN: source/destination
PortSecure: yes
Dot1x: yes
This is an example of output from the show interfacesinterfacedescription command when the interface has been described as Connects to Marketing by using the description interface configuration command:
Switch# show interfaces gigabitethernet1/0/2 description
Interface Status Protocol Description
Gi1/0/2 up down Connects to Marketing
This is an example of output from the show interfaces etherchannel command when port channels are configured on the switch:
Switch# show interfaces etherchannel
----
Port-channel34:
Age of the Port-channel = 28d:18h:51m:46s
Logical slot/port = 12/34 Number of ports = 0
GC = 0x00000000 HotStandBy port = null
Passive port list =
Port state = Port-channel L3-Ag Ag-Not-Inuse
Protocol = -
Port security = Disabled
This is an example of output from the show interfacesinterface-idpruning command when pruning is enabled in the VTP domain:
Switch# show interfaces gigabitethernet1/0/2 pruning
Port Vlans pruned for lack of request by neighbor
Gi1/0/2 3,4
Port Vlans traffic requested of neighbor
Gi1/0/2 1-3
This is an example of output from the show interfaces stats command for a specified VLAN interface:
Switch# show interfaces vlan 1 stats
Switching path Pkts In Chars In Pkts Out Chars Out
Processor 1165354 136205310 570800 91731594
Route cache 0 0 0 0
Total 1165354 136205310 570800 91731594
This is an example of partial output from the show interfaces status command. It displays the status of all interfaces:
Switch# show interfaces status
Port Name Status Vlan Duplex Speed Type
Gi1/0/1 notconnect 1 auto auto 10/100/1000Ba
seTX
Gi1/0/2 notconnect 1 auto 100 10/100/1000Ba
seTX
Gi1/0/3 notconnect 1 auto 1000 10/100/1000Ba
seTX
Gi1/0/4 notconnect 1 auto auto 10/100/1000Ba
seTX
Gi1/0/5 notconnect 1 auto auto 10/100/1000Ba
seTX
Gi1/0/6 notconnect 1 auto 10 10/100/1000Ba
seTX
Gi1/0/7 notconnect 1 auto auto 10/100/1000Ba
seTX
Gi1/0/8 notconnect 1 auto auto 10/100/1000Ba
seTX
Gi1/0/9 notconnect 1 auto auto 10/100/1000Ba
seTX
Gi1/0/10 notconnect 1 auto auto 10/100/1000Ba
seTX
This is an example of output from the show interfacesinterface-idstatus command:
Switch# show interfaces gigabitethernet1/0/20 status
Port Name Status Vlan Duplex Speed Type
Gi1/0/20 notconnect 1 auto auto 10/100/1000Ba
seTX
This is an example of output from the show interfaces status err-disabled command. It displays the status of interfaces in the error-disabled state:
Switch# show interfaces status err-disabled
Port Name Status Reason
Gi1/0/2 err-disabled gbic-invalid
Gi2/0/3 err-disabled dtp-flap
This is an example of output from the show interfacesinterface-idpruning command:
Switch# show interfaces gigabitethernet1/0/2 pruning
Port Vlans pruned for lack of request by neighbor
This is an example of output from the show interfacesinterface-idtrunk command. It displays trunking information for the port.
Switch# show interfaces gigabitethernet1/0/1 trunk
Port Mode Encapsulation Status Native vlan
Gi1/0/1 on 802.1q other 10
Port Vlans allowed on trunk
Gi1/0/1 none
Port Vlans allowed and active in management domain
Gi1/0/1 none
Port Vlans in spanning tree forwarding state and not pruned
Gi1/0/1 none
This is an example of partial output from the show interfaces counters module command for stack member 2. It displays all counters for the specified switch in the stack.
Displays the administrative and operational status of all interfaces or a specified interface.
show interfaces switchport
To display the administrative and operational status of a switching (nonrouting) port, including port blocking and port protection settings, use the show interfaces switchport backup command in privileged EXEC mode.
(Optional) ID of the interface. Valid interfaces include physical ports (including type, stack member for stacking-capable switches, module, and port number) and port channels. The port channel range is 1 to 128.
backup
(Optional) Displays Flex Link backup interface configuration for the specified interface or all interfaces.
detail
(Optional) Displays detailed backup information for the specified interface or all interfaces on the switch or the stack.
modulenumber
(Optional) Displays switchport configuration of all interfaces on the switch or specified stack member.
The range is 1 to 9.
This option is not available if you entered a specific interface ID.
Command Default
None
Command Modes
Privileged EXEC
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
Use the show interface switchport modulenumber command to display the switch port characteristics of all interfaces on that switch in the stack. If there is no switch with that module number in the stack, there is no output.
Examples
This is an example of output from the show interfaces switchport command for a port. The table that follows describes the fields in the display.
Note
Private VLANs are not supported in this release, so those fields are not applicable.
Displays the administrative and operational status of the port. In this display, the port is in switchport mode.
Administrative Mode
Operational Mode
Displays the administrative and operational modes.
Administrative Trunking Encapsulation
Operational Trunking Encapsulation
Negotiation of Trunking
Displays the administrative and operational encapsulation method and whether trunking negotiation is enabled.
Access Mode VLAN
Displays the VLAN ID to which the port is configured.
Trunking Native Mode VLAN
Trunking VLANs Enabled
Trunking VLANs Active
Lists the VLAN ID of the trunk that is in native mode. Lists the allowed VLANs on the trunk. Lists the active VLANs on the trunk.
Pruning VLANs Enabled
Lists the VLANs that are pruning-eligible.
Protected
Displays whether or not protected port is enabled (True) or disabled (False) on the interface.
Unknown unicast blocked
Unknown multicast blocked
Displays whether or not unknown multicast and unknown unicast traffic is blocked on the interface.
Voice VLAN
Displays the VLAN ID on which voice VLAN is enabled.
Appliance trust
Displays the class of service (CoS) setting of the data packets of the IP phone.
This is an example of output from the show interfaces switchport backup command:
Switch# show interfaces switchport backup
Switch Backup Interface Pairs:
Active Interface Backup Interface State
--------------------------------------------------------------
Gi1/0/1 Gi1/0/2 Active Up/Backup Standby
Gi3/0/3 Gi4/0/5 Active Down/Backup Up
Po1 Po2 Active Standby/Backup Up
In this example of output from the show interfaces switchport backup command, VLANs 1 to 50, 60, and 100 to 120 are configured on the switch:
When both interfaces are up, Gi2/0/8 forwards traffic for VLANs 60, 100 to 120, and Gi2/0/6 will forward traffic for VLANs 1 to 50.
Switch# show interfaces switchport backup
Switch Backup Interface Pairs:
Active Interface Backup Interface State
------------------------------------------------------------------------
GigabitEthernet2/0/6 GigabitEthernet2/0/8 Active Up/Backup Up
Vlans on Interface Gi 2/0/6: 1-50
Vlans on Interface Gi 2/0/8: 60, 100-120
When a Flex Link interface goes down (LINK_DOWN), VLANs preferred on this interface are moved to the peer interface of the Flex Link pair. In this example, if interface Gi2/0/6 goes down, Gi2/0/8 carries all VLANs of the Flex Link pair.
Switch# show interfaces switchport backup
Switch Backup Interface Pairs:
Active Interface Backup Interface State
------------------------------------------------------------------------
GigabitEthernet2/0/6 GigabitEthernet2/0/8 Active Down/Backup Up
Vlans on Interface Gi 2/0/6:
Vlans on Interface Gi 2/0/8: 1-50, 60, 100-120
When a Flex Link interface comes up, VLANs preferred on this interface are blocked on the peer interface and moved to the forwarding state on the interface that has just come up. In this example, if interface Gi2/0/6 comes up, then VLANs preferred on this interface are blocked on the peer interface Gi2/0/8 and forwarded on Gi2/0/6.
Switch# show interfaces switchport backup
Switch Backup Interface Pairs:
Active Interface Backup Interface State
------------------------------------------------------------------------
GigabitEthernet2/0/6 GigabitEthernet2/0/8 Active Up/Backup Up
Vlans on Interface Gi 2/0/6: 1-50
Vlans on Interface Gi 2/0/8: 60, 100-120
(Optional) ID of the physical interface, including type, stack member (stacking-capable switches only) module, and port number.
detail
(Optional) Displays calibration properties, including high and low numbers and any alarm information for any Digital Optical Monitoring (DoM)-capable transceiver if one is installed in the switch.
modulenumber
(Optional) Limits display to interfaces on module on the switch. The range is 1 to 9. This option is not available if you entered a specific interface ID.
properties
(Optional) Displays speed, duplex, and inline power settings on an interface.
supported-list
(Optional) Lists all supported transceivers.
threshold-table
(Optional) Displays alarm and warning threshold table.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Examples
This is an example of output from the show interfacesinterface-idtransceiver properties command:
Switch# show interfaces gigabitethernet1/0/1 transceiver properties
Name : Gi1/0/1
Administrative Speed: auto
Operational Speed: auto
Administrative Duplex: auto
Administrative Power Inline: enable
Operational Duplex: auto
Administrative Auto-MDIX: off
Operational Auto-MDIX: off
This is an example of output from the show interfacesinterface-idtransceiver detail command:
Switch# show interfaces gigabitethernet1/0/3 transceiver detail
ITU Channel not available (Wavelength not available),
Transceiver is externally calibrated.
mA:milliamperes, dBm:decibels (milliwatts), N/A:not applicable.
++:high alarm, +:high warning, -:low warning, -- :low alarm.
A2D readouts (if they differ), are reported in parentheses.
The threshold values are uncalibrated.
High Alarm High Warn Low Warn Low Alarm
Temperature Threshold Threshold Threshold Threshold
Port (Celsius) (Celsius) (Celsius) (Celsius) (Celsius)
------- ------------------ ---------- --------- --------- ---------
Gi1/0/3 41.5 110.0 103.0 -8.0 -12.0
High Alarm High Warn Low Warn Low Alarm
Voltage Threshold Threshold Threshold Threshold
Port (Volts) (Volts) (Volts) (Volts) (Volts)
------- --------------- ---------- --------- --------- ---------
Gi1/0/3 3.20 4.00 3.70 3.00 2.95
High Alarm High Warn Low Warn Low Alarm
Current Threshold Threshold Threshold Threshold
Port (milliamperes) (mA) (mA) (mA) (mA)
------- ----------------- ---------- --------- --------- ---------
Gi1/0/3 31.0 84.0 70.0 4.0 2.0
Optical High Alarm High Warn Low Warn Low Alarm
Transmit Power Threshold Threshold Threshold Threshold
Port (dBm) (dBm) (dBm) (dBm) (dBm)
------- ----------------- ---------- --------- --------- ---------
Gi1/0/3 -0.0 ( -0.0) -0.0 -0.0 -0.0 -0.0
Optical High Alarm High Warn Low Warn Low Alarm
Receive Power Threshold Threshold Threshold Threshold
Port (dBm) (dBm) (dBm) (dBm) (dBm)
------- ----------------- ---------- --------- --------- ---------
Gi1/0/3 N/A ( -0.0) -- -0.0 -0.0 -0.0 -0.0
This is an example of partial output from the show interfaces transceiver threshold-table command:
(Optional) Specifies the stack member number for which to display inline power messages within a trace buffer.
Command Default
None
Command Modes
Privileged EXEC
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Examples
This is an output example from the show mgmt-infra trace messages ilpower command:
Switch# show mgmt-infra trace messages ilpower
[10/23/12 14:05:10.984 UTC 1 3] Initialized inline power system configuration fo
r slot 1.
[10/23/12 14:05:10.984 UTC 2 3] Initialized inline power system configuration fo
r slot 2.
[10/23/12 14:05:10.984 UTC 3 3] Initialized inline power system configuration fo
r slot 3.
[10/23/12 14:05:10.984 UTC 4 3] Initialized inline power system configuration fo
r slot 4.
[10/23/12 14:05:10.984 UTC 5 3] Initialized inline power system configuration fo
r slot 5.
[10/23/12 14:05:10.984 UTC 6 3] Initialized inline power system configuration fo
r slot 6.
[10/23/12 14:05:10.984 UTC 7 3] Initialized inline power system configuration fo
r slot 7.
[10/23/12 14:05:10.984 UTC 8 3] Initialized inline power system configuration fo
r slot 8.
[10/23/12 14:05:10.984 UTC 9 3] Initialized inline power system configuration fo
r slot 9.
[10/23/12 14:05:10.984 UTC a 3] Inline power subsystem initialized.
[10/23/12 14:05:18.908 UTC b 264] Create new power pool for slot 1
[10/23/12 14:05:18.909 UTC c 264] Set total inline power to 450 for slot 1
[10/23/12 14:05:20.273 UTC d 3] PoE is not supported on .
[10/23/12 14:05:20.288 UTC e 3] PoE is not supported on .
[10/23/12 14:05:20.299 UTC f 3] PoE is not supported on .
[10/23/12 14:05:20.311 UTC 10 3] PoE is not supported on .
[10/23/12 14:05:20.373 UTC 11 98] Inline power process post for switch 1
[10/23/12 14:05:20.373 UTC 12 98] PoE post passed on switch 1
[10/23/12 14:05:20.379 UTC 13 3] Slot #1: PoE initialization for board id 16387
[10/23/12 14:05:20.379 UTC 14 3] Set total inline power to 450 for slot 1
[10/23/12 14:05:20.379 UTC 15 3] Gi1/0/1 port config Initialized
[10/23/12 14:05:20.379 UTC 16 3] Interface Gi1/0/1 initialization done.
[10/23/12 14:05:20.380 UTC 17 3] Gi1/0/24 port config Initialized
[10/23/12 14:05:20.380 UTC 18 3] Interface Gi1/0/24 initialization done.
[10/23/12 14:05:20.380 UTC 19 3] Slot #1: initialization done.
[10/23/12 14:05:50.440 UTC 1a 3] Slot #1: PoE initialization for board id 16387
[10/23/12 14:05:50.440 UTC 1b 3] Duplicate init event
Displays platform manager Power over Ethernet messages within a trace buffer.
show mgmt-infra trace messages ilpower-ha
To display inline power high availability messages within a trace buffer, use the show mgmt-infra trace messages ilpower-ha command in privileged EXEC mode.
Displays platform manager Power over Ethernet messages within a trace buffer.
show mgmt-infra trace messages platform-mgr-poe
To display platform manager Power over Ethernet (PoE) messages within a trace buffer, use the show mgmt-infra trace messages platform-mgr-poe privileged EXEC command.
(Optional) Specifies the stack member number for which to display messages within a trace buffer.
Command Default
None
Command Modes
Privileged EXEC
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Examples
This is an example of partial output from the show mgmt-infra trace messages platform-mgr-poe command:
Switch# show mgmt-infra trace messages platform-mgr-poe
[10/23/12 14:04:06.431 UTC 1 5495] PoE Info: get power controller param sent:
[10/23/12 14:04:06.431 UTC 2 5495] PoE Info: POE_SHUT sent for port 1 (0:0)
[10/23/12 14:04:06.431 UTC 3 5495] PoE Info: POE_SHUT sent for port 2 (0:1)
[10/23/12 14:04:06.431 UTC 4 5495] PoE Info: POE_SHUT sent for port 3 (0:2)
[10/23/12 14:04:06.431 UTC 5 5495] PoE Info: POE_SHUT sent for port 4 (0:3)
[10/23/12 14:04:06.431 UTC 6 5495] PoE Info: POE_SHUT sent for port 5 (0:4)
[10/23/12 14:04:06.431 UTC 7 5495] PoE Info: POE_SHUT sent for port 6 (0:5)
[10/23/12 14:04:06.431 UTC 8 5495] PoE Info: POE_SHUT sent for port 7 (0:6)
[10/23/12 14:04:06.431 UTC 9 5495] PoE Info: POE_SHUT sent for port 8 (0:7)
[10/23/12 14:04:06.431 UTC a 5495] PoE Info: POE_SHUT sent for port 9 (0:8)
[10/23/12 14:04:06.431 UTC b 5495] PoE Info: POE_SHUT sent for port 10 (0:9)
[10/23/12 14:04:06.431 UTC c 5495] PoE Info: POE_SHUT sent for port 11 (0:10)
[10/23/12 14:04:06.431 UTC d 5495] PoE Info: POE_SHUT sent for port 12 (0:11)
[10/23/12 14:04:06.431 UTC e 5495] PoE Info: POE_SHUT sent for port 13 (e:0)
[10/23/12 14:04:06.431 UTC f 5495] PoE Info: POE_SHUT sent for port 14 (e:1)
[10/23/12 14:04:06.431 UTC 10 5495] PoE Info: POE_SHUT sent for port 15 (e:2)
[10/23/12 14:04:06.431 UTC 11 5495] PoE Info: POE_SHUT sent for port 16 (e:3)
[10/23/12 14:04:06.431 UTC 12 5495] PoE Info: POE_SHUT sent for port 17 (e:4)
[10/23/12 14:04:06.431 UTC 13 5495] PoE Info: POE_SHUT sent for port 18 (e:5)
[10/23/12 14:04:06.431 UTC 14 5495] PoE Info: POE_SHUT sent for port 19 (e:6)
[10/23/12 14:04:06.431 UTC 15 5495] PoE Info: POE_SHUT sent for port 20 (e:7)
[10/23/12 14:04:06.431 UTC 16 5495] PoE Info: POE_SHUT sent for port 21 (e:8)
[10/23/12 14:04:06.431 UTC 17 5495] PoE Info: POE_SHUT sent for port 22 (e:9)
[10/23/12 14:04:06.431 UTC 18 5495] PoE Info: POE_SHUT sent for port 23 (e:10)
Creates a network-policy profile and enters network-policy configuration mode.
show platform CAPWAP summary
To display the tunnel identifier and the type all the CAPWAP tunnels established by the controller to the access points and other mobility controllers, use the
showplatformCAPWAPsummary command.
showplatformCAPWAPsummary
Syntax Description
This command has no keywords or arguments.
Command Default
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Examples
This example displays the tunnel identifier and details:
Switch# show platform capwap summary
Tunnel ID | Type | Src IP | Dst IP | SPrt | DPrt | S | A
-------------------------------------------------------------------------------
0x0088498000000983 data 9.6.44.61 9.12.138.101 5247 41894 1 1
0x00966dc000000010 data 9.6.44.61 9.6.47.101 5247 62526 1 2
0x00938e800000095b data 9.6.44.61 9.12.138.100 5247 45697 1 1
0x00ab1a8000000bd1 data 9.6.44.61 9.12.139.101 5247 38906 1 0
0x00896e40000000bd data 9.6.44.61 9.12.136.100 5247 1836 1 1
show power inline
To display the Power over Ethernet (PoE) status for the specified PoE port, the
specified stack member, or for all PoE ports in the
switch stack, use the show power inline command in EXEC mode.
show power inline
[ police | priority ]
[ interface-id | modulestack-member-number ]
[detail]
Syntax Description
police
(Optional) Displays the power policing information about real-time power
consumption.
priority
(Optional) Displays the power inline port priority for each port.
interface-id
(Optional) ID of the physical interface.
modulestack-member-number
(Optional) Limits the display to ports on the specified stack member. The
module number is 1 to 9.
This keyword is supported only on stacking-capable switches.
detail
(Optional) Displays detailed output of the interface or module.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Examples
This is an example of output from the show power inline
command. The table that follows describes the output
fields.
Switch> show power inline
Module Available Used Remaining
(Watts) (Watts) (Watts)
------ --------- -------- ---------
1 n/a n/a n/a
2 n/a n/a n/a
3 1440.0 15.4 1424.6
4 720.0 6.3 713.7
Interface Admin Oper Power Device Class Max
(Watts)
--------- ------ ---------- ------- ------------------- ----- ----
Gi3/0/1 auto off 0.0 n/a n/a 30.0
Gi3/0/2 auto off 0.0 n/a n/a 30.0
Gi3/0/3 auto off 0.0 n/a n/a 30.0
Gi3/0/4 auto off 0.0 n/a n/a 30.0
Gi3/0/5 auto off 0.0 n/a n/a 30.0
Gi3/0/6 auto off 0.0 n/a n/a 30.0
Gi3/0/7 auto off 0.0 n/a n/a 30.0
Gi3/0/8 auto off 0.0 n/a n/a 30.0
Gi3/0/9 auto off 0.0 n/a n/a 30.0
Gi3/0/10 auto off 0.0 n/a n/a 30.0
Gi3/0/11 auto off 0.0 n/a n/a 30.0
Gi3/0/12 auto off 0.0 n/a n/a 30.0
<output truncated>
This is an example of output from the show power inlineinterface-id command on a switch port:
Switch> show power inline gigabitethernet1/0/1
Interface Admin Oper Power Device Class Max
(Watts)
--------- ------ ---------- ------- ------------------- ----- ----
Gi1/0/1 auto off 0.0 n/a n/a 30.0
This is an example of output from the show power inline moduleswitch-number command on stack member 3. The table that follows describes the output fields.
Switch> show power inline module 3
Module Available Used Remaining
(Watts) (Watts) (Watts)
------ --------- -------- ---------
3 865.0 864.0 1.0
Interface Admin Oper Power Device Class Max
(Watts)
--------- ------ ---------- ------- ------------------- ----- ----
Gi3/0/1 auto power-deny 4.0 n/a n/a 15.4
Gi3/0/2 auto off 0.0 n/a n/a 15.4
Gi3/0/3 auto off 0.0 n/a n/a 15.4
Gi3/0/4 auto off 0.0 n/a n/a 15.4
Gi3/0/5 auto off 0.0 n/a n/a 15.4
Gi3/0/6 auto off 0.0 n/a n/a 15.4
Gi3/0/7 auto off 0.0 n/a n/a 15.4
Gi3/0/8 auto off 0.0 n/a n/a 15.4
Gi3/0/9 auto off 0.0 n/a n/a 15.4
Gi3/0/10 auto off 0.0 n/a n/a 15.4
<output truncated>
Table 6 show power inline Field Descriptions
Field
Description
Available
The total amount of configured power2 on the PoE switch in watts (W).
Used
The amount of configured power that is allocated to PoE ports in
watts.
Remaining
The amount of configured power in watts that is not allocated to ports in
the system. (Available – Used = Remaining)
Admin
Administration mode: auto, off, static.
Oper
Operating mode:
on—The powered device is detected, and power is applied.
off—No PoE is applied.
faulty—Device detection or a powered device is in a faulty state.
power-deny—A powered device is detected, but no PoE is available, or
the maximum wattage exceeds the detected powered-device maximum.
Power
The maximum amount of power that is allocated to the powered device in
watts. This value is the same as the value in the Cutoff Power
field in the show power inline police
command output.
Device
The device type detected: n/a, unknown, Cisco powered-device, IEEE
powered-device, or the name from CDP.
Class
The IEEE classification: n/a or a value from 0 to 4.
Max
The maximum amount of power allocated to the powered device in watts.
AdminPowerMax
The maximum amount power allocated to the powered device in watts when
the switch polices the real-time power consumption. This value is the
same as the Max field value.
AdminConsumption
The power consumption of the powered device in watts when the switch
polices the real-time power consumption. If policing is disabled, this
value is the same as the AdminPowerMax field value.
2 The configured power is the power
that you manually specify or that the switch specifies by using CDP
power negotiation or the IEEE classification, which is different than
the real-time power that is monitored with the power sensing feature.
This is an example of output from the show power inline police
command on a stacking-capable switch:
Switch> show power inline police
Module Available Used Remaining
(Watts) (Watts) (Watts)
------ --------- -------- ---------
1 370.0 0.0 370.0
3 865.0 864.0 1.0
Admin Oper Admin Oper Cutoff Oper
Interface State State Police Police Power Power
--------- ------ ----------- ---------- ---------- ------ ------
Gi1/0/1 auto off none n/a n/a 0.0
Gi1/0/2 auto off log n/a 5.4 0.0
Gi1/0/3 auto off errdisable n/a 5.4 0.0
Gi1/0/4 off off none n/a n/a 0.0
Gi1/0/5 off off log n/a 5.4 0.0
Gi1/0/6 off off errdisable n/a 5.4 0.0
Gi1/0/7 auto off none n/a n/a 0.0
Gi1/0/8 auto off log n/a 5.4 0.0
Gi1/0/9 auto on none n/a n/a 5.1
Gi1/0/10 auto on log ok 5.4 4.2
Gi1/0/11 auto on log log 5.4 5.9
Gi1/0/12 auto on errdisable ok 5.4 4.2
Gi1/0/13 auto errdisable errdisable n/a 5.4 0.0
<output truncated>
In the previous example:
The Gi1/0/1 port is shut down, and policing is not configured.
The Gi1/0/2 port is shut down, but policing is enabled with a policing action to
generate a syslog message.
The Gi1/0/3 port is shut down, but policing is enabled with a policing action is to
shut down the port.
Device detection is disabled on the Gi1/0/4 port, power is not applied to the port,
and policing is disabled.
Device detection is disabled on the Gi1/0/5 port, and power is not applied to the
port, but policing is enabled with a policing action to generate a syslog
message.
Device detection is disabled on the Gi1/0/6 port, and power is not applied to the
port, but policing is enabled with a policing action to shut down the port.
The Gi1/0/7 port is up, and policing is disabled, but the switch does not apply
power to the connected device.
The Gi1/0/8 port is up, and policing is enabled with a policing action to generate a
syslog message, but the switch does not apply power to the powered device.
The Gi1/0/9 port is up and connected to a powered device, and policing is
disabled.
The Gi1/0/10 port is up and connected to a powered device, and policing is enabled
with a policing action to generate a syslog message. The policing action does not
take effect because the real-time power consumption is less than the cutoff
value.
The Gi1/0/11 port is up and connected to a powered device, and policing is enabled
with a policing action to generate a syslog message.
The Gi1/0/12 port is up and connected to a powered device, and policing is enabled
with a policing action to shut down the port. The policing action does not take
effect because the real-time power consumption is less than the cutoff value.
The Gi1/0/13 port is up and connected to a powered device, and policing is enabled
with a policing action to shut down the port.
This is an example of output from the show power inline policeinterface-id command on a standalone switch. The table that follows describes the output fields.
Switch> show power inline police gigabitethernet1/0/1
Interface Admin Oper Admin Oper Cutoff Oper
State State Police Police Power Power
--------- ------ ---------- ---------- ---------- ------ -----
Gi1/0/1 auto off none n/a n/a 0.0
Table 7 show power inline police Field Descriptions
Field
Description
Available
The total amount of configured power3 on the switch in
watts (W).
Used
The amount of configured power allocated to PoE ports in watts.
Remaining
The amount of configured power in watts that is not allocated to ports in
the system. (Available – Used = Remaining)
Admin State
Administration mode: auto, off, static.
Oper State
Operating mode:
errdisable—Policing is enabled.
faulty—Device detection on a powered device is in a faulty state.
off—No PoE is applied.
on—The powered device is detected, and power is applied.
power-deny—A powered device is detected, but no PoE is available, or
the real-time power consumption exceeds the maximum power
allocation.
Note
The operating mode is the current PoE state for the specified PoE
port, the specified stack member, or for all PoE ports on the switch.
Admin Police
Status of the real-time power-consumption policing feature:
errdisable—Policing is enabled, and the switch shuts down the port
when the real-time power consumption exceeds the maximum power
allocation.
log—Policing is enabled, and the switch generates a syslog message
when the real-time power consumption exceeds the maximum power
allocation.
none—Policing is disabled.
Oper Police
Policing status:
errdisable—The real-time power consumption exceeds the maximum power
allocation, and the switch shuts down the PoE port.
log—The real-time power consumption exceeds the maximum power
allocation, and the switch generates a syslog message.
n/a—Device detection is disabled, power is not applied to the PoE
port, or no policing action is configured.
ok—Real-time power consumption is less than the maximum power
allocation.
Cutoff Power
The maximum power allocated on the port. When the real-time power
consumption is greater than this value, the switch takes the configured
policing action.
Oper Power
The real-time power consumption of the powered device.
3 The configured power is the power
that you manually specify or that the switch specifies by using CDP
power negotiation or the IEEE classification, which is different than
the real-time power that is monitored with the power sensing feature.
Configures the power management mode on PoE ports.
show stack-power
To display information about StackPower stacks or switches in a power stack, use the
show stack-power command in EXEC mode.
showstack-power
[ power-stack-name ]
Syntax Description
power-stack-name
(Optional) Name of the power stack for which to display power information. The name can be up to 31 characters.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
This command is available only on switch stacks running the
IP Base or IP Services image.
If a switch is shut down because of load shedding, the output of the
show stack-power command still includes the MAC address
of the shutdown neighbor switch. The command output shows the stack power topology even
if there is not enough power to power a switch.
Examples
This is an example of output from the show
stack-power command:
Switch# show stack-power
Power stack name: Powerstack-2
Stack mode: Redundant strict
Stack topology: Ring
Switch 2:
Power budget: 206
Low port priority value: 25
High port priority value: 13
Switch priority value: 4
Port 1 status: Connected
Port 2 status: Connected
Neighbor on port 1: 2037.06ce.1d00
Neighbor on port 2: 2037.06ce.5280
Switch 3:
Power budget: 596
Low port priority value: 23
High port priority value: 7
Switch priority value: 3
Port 1 status: Connected
Port 2 status: Connected
Neighbor on port 1: 2037.06ce.4000
Neighbor on port 2: 2037.06ce.1d00
Switch 1:
Power budget: 596
Low port priority value: 20
High port priority value: 12
Switch priority value: 2
Port 1 status: Connected
Port 2 status: Connected
Neighbor on port 1: 2037.06ce.5280
Neighbor on port 2: 2037.06ce.4000
Configures StackPower parameters for the power stack or for a switch in the power stack.
show storm-control
To display broadcast, multicast, or unicast storm control settings on the switch or on the specified interface or to display storm-control history, use the show storm-control command in user EXEC mode.
When you enter an interface ID, the storm control thresholds appear for the specified interface.
If you do not enter an interface ID, settings appear for one traffic type for all ports on the switch.
If you do not enter a traffic type, settings appear for broadcast storm control.
Examples
This is an example of a partial output from the show storm-control command when no keywords are entered. Because no traffic-type keyword was entered, the broadcast storm control settings appear.
Switch> show storm-control
Interface Filter State Upper Lower Current
--------- ------------- ---------- --------- ---------
Gi1/0/1 Forwarding 20 pps 10 pps 5 pps
Gi1/0/2 Forwarding 50.00% 40.00% 0.00%
<output truncated>
This is an example of output from the show storm-control command for a specified interface. Because no traffic-type keyword was entered, the broadcast storm control settings appear.
Switch> show storm-control gigabitethernet 1/0/1
Interface Filter State Upper Lower Current
--------- ------------- ---------- --------- ---------
Gi1/0/1 Forwarding 20 pps 10 pps 5 pps
The following table describes the fields in the show storm-control display:
Table 8 show storm-control Field Descriptions
Field
Description
Interface
Displays the ID of the interface.
Filter State
Displays the status of the filter:
Blocking—Storm control is enabled, and a storm has occurred.
Forwarding—Storm control is enabled, and no storms have occurred.
Inactive—Storm control is disabled.
Upper
Displays the rising suppression level as a percentage of total available bandwidth in packets per second or in bits per second.
Lower
Displays the falling suppression level as a percentage of total available bandwidth in packets per second or in bits per second.
Current
Displays the bandwidth usage of broadcast traffic or the specified traffic type (broadcast, multicast, or unicast) as a percentage of total available bandwidth. This field is only valid when storm control is enabled.
Enables broadcast, multicast, or unicast storm control and sets threshold levels on an interface.
show system mtu
To display the global maximum transmission unit (MTU) or maximum packet size set for the
switch, use the show system mtu command in privileged EXEC mode.
showsystemmtu
Syntax Description
This command has no arguments or keywords.
Command Default
None
Command Modes
Privileged EXEC
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
For information about the MTU values and the stack configurations that affect the MTU
values, see the system mtu command.
Examples
This is an example of output from the show system mtu
command:
Switch# show system mtu
Global Ethernet MTU is 1500 bytes.
Sets the global maximum packet size or MTU size for switched packets on Gigabit Ethernet and 10-Gigabit Ethernet ports.
speed
To specify the speed of a 10/100 Mb/s or 10/100/1000 Mb/s port, use the speed command in interface configuration mode. To return to the default value, use the no form of this command.
Specifies that the port runs at 1000 Mb/s. This option is valid and visible only on 10/100/1000 Mb/s ports.
auto
Automatically detects the speed the port should run at based on the port at the other end of the link. If you use the 10, 100, or 1000 keywords with the auto keyword, the port only autonegotiates at the specified speeds.
nonegotiate
Disables autonegotiation, and the port runs at 1000 Mb/s.
Command Default
The default is auto.
Command Modes
Interface configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
You cannot configure speed on the 10-Gigabit Ethernet ports.
Except for the 1000BASE-T small form-factor pluggable (SFP) modules, you can configure the speed to not negotiate (nonegotiate) when an SFP module port is connected to a device that does not support autonegotiation.
If the speed is set to auto, the switch negotiates with the device at the other end of the link for the speed setting and then forces the speed setting to the negotiated value. The duplex setting remains as configured on each end of the link, which could result in a duplex setting mismatch.
If both ends of the line support autonegotiation, we highly recommend the default autonegotiation settings. If one interface supports autonegotiation and the other end does not, do use the auto setting on the supported side, but set the duplex and speed on the other side.
Caution
Changing the interface speed and duplex mode configuration might shut down and reenable the interface during the reconfiguration.
For guidelines on setting the switch speed and duplex parameters, see the “Configuring Interface Characteristics” chapter in the software configuration guide for this release.
You can verify your settings by entering the showinterfaces privileged EXEC command.
Examples
This example shows how to set speed on a port to 100 Mb/s:
Displays the administrative and operational status of all interfaces or a specified interface.
stack-power
To configure StackPower parameters for the power stack or for a switch in the power
stack, use the stack power command in global configuration
mode. To return to the default setting, use the no form of the
command,
Specifies the name of the power stack. The name can be up to 31 characters. Entering
these keywords followed by a carriage return enters power stack
configuration mode.
switchstack-member-number
Specifies the switch number in the stack (1 to 4) to enter switch stack-power
configuration mode for the switch.
Command Default
There is no default.
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
When you enter the stack-power stackpower stack name command, you enter power stack configuration
mode, and these commands are available:
default—Returns a command to its default setting.
exit—Exits ARP access-list
configuration mode.
mode—Sets the power mode for the power stack. See the
mode command.
no—Negates a command or returns to default settings.
If you enter the stack-power switchswitch-number command with a switch number that is not
participating in StackPower, you receive an error message.
When you enter the stack-power switchswitch-number command with the number of a switch participating in
StackPower, you enter switch stack power configuration mode, and these commands are
available:
default—Returns a command to its default setting.
exit—Exits switch stack power configuration mode.
no—Negates a command or returns to default settings.
power-priority—Sets the power priority for the switch and
the switch ports. See the power-priority command.
stack-idname—Enters the name of the power stack to which the switch belongs. If you do
not enter the power stack-ID, the switch does not inherit the stack parameters. The
name can be up to 31 characters.
standalone—Forces the switch to operate in standalone
power mode. This mode shuts down both stack power ports.
Examples
This example removes switch 2, which is connected to the power stack,
from the power pool and shutting down both power ports:
Displays information about StackPower stacks or switches in a power stack.
storm-control
To enable broadcast, multicast, or unicast storm control and to set threshold levels on an interface, use the storm-control command in interface configuration mode. To return to the default setting, use the no form of this command.
Specifies the action taken when a storm occurs on a port. The default action is to filter traffic and to not send an Simple Network Management Protocol (SNMP) trap.
shutdown
Disables the port during a storm.
trap
Sends an SNMP trap when a storm occurs.
broadcast
Enables broadcast storm control on the interface.
multicast
Enables multicast storm control on the interface.
unicast
Enables unicast storm control on the interface.
level
Specifies the rising and falling suppression levels as a percentage of total bandwidth of the port.
level
Rising suppression level, up to two decimal places. The range is 0.00 to 100.00. Block the flooding of storm packets when the value specified for level is reached.
level-low
(Optional) Falling suppression level, up to two decimal places. The range is 0.00 to 100.00. This value must be less than or equal to the rising suppression value. If you do not configure a falling suppression level, it is set to the rising suppression level.
level bps
Specifies the rising and falling suppression levels as a rate in bits per second at which traffic is received on the port.
bps
Rising suppression level, up to 1 decimal place. The range is 0.0 to 10000000000.0. Block the flooding of storm packets when the value specified for bps is reached.
You can use metric suffixes such as k, m, and g for large number thresholds.
bps-low
(Optional) Falling suppression level, up to 1 decimal place. The range is 0.0 to 10000000000.0. This value must be equal to or less than the rising suppression value.
You can use metric suffixes such as k, m, and g for large number thresholds.
level pps
Specifies the rising and falling suppression levels as a rate in packets per second at which traffic is received on the port.
pps
Rising suppression level, up to 1 decimal place. The range is 0.0 to 10000000000.0. Block the flooding of storm packets when the value specified for pps is reached.
You can use metric suffixes such as k, m, and g for large number thresholds.
pps-low
(Optional) Falling suppression level, up to 1 decimal place. The range is 0.0 to 10000000000.0. This value must be equal to or less than the rising suppression value.
You can use metric suffixes such as k, m, and g for large number thresholds.
Command Default
Broadcast, multicast, and unicast storm control are disabled.
The default action is to filter traffic and to not send an SNMP trap.
Command Modes
Interface configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
The storm-control suppression level can be entered as a percentage of total bandwidth of the port, as a rate in packets per second at which traffic is received, or as a rate in bits per second at which traffic is received.
When specified as a percentage of total bandwidth, a suppression value of 100 percent means that no limit is placed on the specified traffic type. A value of level 0 0 means that all broadcast, multicast, or unicast traffic on that port is blocked. Storm control is enabled only when the rising suppression level is less than 100 percent. If no other storm-control configuration is specified, the default action is to filter the traffic causing the storm and to send no SNMP traps.
Note
When the storm control threshold for multicast traffic is reached, all multicast traffic except control traffic, such as bridge protocol data unit (BDPU) and Cisco Discovery Protocol (CDP) frames, are blocked. However, the switch does not differentiate between routing updates, such as Open Shortest Path First (OSPF) and regular multicast data traffic, so both types of traffic are blocked.
The trap and shutdown options are independent of each other.
If you configure the action to be taken as shutdown (the port is error-disabled during a storm) when a packet storm is detected, you must use the no shutdown interface configuration command to bring the interface out of this state. If you do not specify the shutdown action, specify the action as trap (the switch generates a trap when a storm is detected).
When a storm occurs and the action is to filter traffic, if the falling suppression level is not specified, the switch blocks all traffic until the traffic rate drops below the rising suppression level. If the falling suppression level is specified, the switch blocks traffic until the traffic rate drops below this level.
Note
Storm control is supported on physical interfaces. You can also configure storm control on an EtherChannel. When storm control is configured on an EtherChannel, the storm control settings propagate to the EtherChannel physical interfaces.
When a broadcast storm occurs and the action is to filter traffic, the switch blocks only broadcast traffic.
For more information, see the software configuration guide for this release.
Examples
This example shows how to enable broadcast storm control with a 75.5-percent rising suppression level:
This example shows how to enable unicast storm control on a port with a 87-percent rising suppression level and a 65-percent falling suppression level:
This example shows how to enable multicast storm control on a port with a 2000-packets-per-second rising suppression level and a 1000-packets-per-second falling suppression level:
Displays broadcast, multicast, or unicast storm control settings on all interfaces or on a specified interface.
switchport backup interface
To configure Flex Links, use the switchport backup interface command in interface configuration mode on a Layer 2 interface on the switch stack or on a standalone switch. To remove the Flex Links configuration, use the no form of this command.
(Optional) Configures the MAC move update (MMU) for a backup interface pair.
multicastfast-convergence
(Optional) Configures multicast fast convergence on the backup interface.
preemption
(Optional) Configures a preemption scheme for a backup interface pair.
delayseconds
Specifies a preemption delay. The range is 1 to 300 seconds.
The default is 35 seconds.
mode
Specifies the preemption mode.
bandwidth
Specifies that a higher bandwidth interface is preferred.
forced
Specifies that an active interface is preferred.
off
Specifies that no preemption occurs from backup to active.
prefervlanvlan-id
(Optional) Specifies that VLANs are carried on the backup interfaces of a Flex
Link pair. VLAN ID range is 1 to 4094.
Command Default
The default is to have no Flex Links defined. The preemption mode is off. No preemption occurs. Preemption delay is set to 35 seconds.
Command Modes
Interface configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
Flex Links are a pair of interfaces that provide backup to each other. With Flex Links configured, one link acts as the primary interface and forwards traffic, while the other interface is in standby mode, ready to begin forwarding traffic if the primary link shuts down. The interface being configured is referred to as the active link; the specified interface is identified as the backup link. The feature provides an alternative to the Spanning Tree Protocol (STP), allowing users to turn off STP and still retain basic link redundancy.
This command is available only for Layer 2 interfaces.
You can configure only one Flex Link backup link for any active link, and it must be a different interface from the active interface.
An interface can belong to only one Flex Link pair. An interface can be a backup link for only one active link. An active link cannot belong to another Flex Link pair.
A backup link does not have to be the same type (Fast Ethernet or Gigabit Ethernet, for instance) as the active link. However, you should configure both Flex Links with similar characteristics so that there are no loops or changes in behavior if the standby link begins to forward traffic.
Neither of the links can be a port that belongs to an EtherChannel. However, you can configure two port channels (EtherChannel logical interfaces) as Flex Links, and you can configure a port channel and a physical interface as Flex Links, with either the port channel or the physical interface as the active link.
If STP is configured on the switch, Flex Links do not participate in STP in all valid VLANs. If STP is not running, be sure that there are no loops in the configured topology.
Examples
This example shows how to configure two interfaces as Flex Links:
Switch# configure terminalSwitch(conf)# interface gigabitethernet1/0/1Switch(conf-if)# switchport backup interface gigabitethernet1/0/2Switch(conf-if)# end
This example shows how to configure the Gigabit Ethernet interface to always preempt the backup:
Displays the administrative and operational status of a switching (nonrouting) port.
switchport block
To prevent unknown multicast or unicast packets from being forwarded, use the switchport block command in interface configuration mode. To allow forwarding unknown multicast or unicast packets, use the no form of this command.
switchportblock
{ multicast | unicast }
noswitchportblock
{ multicast | unicast }
Syntax Description
multicast
Specifies that unknown multicast traffic should be blocked.
Note
Only pure Layer 2 multicast traffic is blocked. Multicast packets that contain IPv4 or IPv6 information in the header are not blocked.
unicast
Specifies that unknown unicast traffic should be blocked.
Command Default
Unknown multicast and unicast traffic is not blocked.
Command Modes
Interface configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
By default, all traffic with unknown MAC addresses is sent to all ports. You can block unknown multicast or unicast traffic on protected or nonprotected ports. If unknown multicast or unicast traffic is not blocked on a protected port, there could be security issues.
With multicast traffic, the port blocking feature blocks only pure Layer 2 packets. Multicast packets that contain IPv4 or IPv6 information in the header are not blocked.
Blocking unknown multicast or unicast traffic is not automatically enabled on protected ports; you must explicitly configure it.
For more information about blocking packets, see the software configuration guide for this release.
Examples
This example shows how to block unknown unicast traffic on an interface:
Switch(config-if)# switchport block unicast
You can verify your setting by entering the show interfacesinterface-idswitchport privileged EXEC command.
Displays the administrative and operational status of a switching (nonrouting) port.
switchport port-security aging
To set the aging time and type for secure address entries or to change the aging behavior for secure addresses on a particular port, use the switchport port-security aging command in interface configuration mode. Use the no form of this command to disable port security aging or to set the parameters to their default states.
noswitchportport-securityaging
{ static | time | type }
Syntax Description
static
Enables aging for statically configured secure addresses on this port.
timetime
Specifies the aging time for this port. The range is 0 to 1440 minutes. If the time is 0, aging is disabled for this port.
type
Sets the aging type.
absolute
Sets absolute aging type. All the secure addresses on this port age out exactly after the time (minutes) specified and are removed from the secure address list.
inactivity
Sets the inactivity aging type. The secure addresses on this port age out only if there is no data traffic from the secure source address for the specified time period.
Command Default
The port security aging feature is disabled. The default time is 0 minutes.
The default aging type is absolute.
The default static aging behavior is disabled.
Command Modes
Interface configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
To enable secure address aging for a particular port, set the aging time to a value other than 0 for that port.
To allow limited time access to particular secure addresses, set the aging type as absolute. When the aging time lapses, the secure addresses are deleted.
To allow continuous access to a limited number of secure addresses, set the aging type as inactivity. This removes the secure address when it become inactive, and other addresses can become secure.
To allow unlimited access to a secure address, configure it as a secure address, and disable aging for the statically configured secure address by using the no switchport port-security aging static interface configuration command.
Examples
This example sets the aging time as 2 hours for absolute aging for all the secure addresses on the port:
Switch(config)# interface gigabitethernet1/0/1Switch(config-if)# switchport port-security aging time 120
This example sets the aging time as 2 minutes for inactivity aging type with aging enabled for configured secure addresses on the port:
Switch(config)# interface gigabitethernet1/0/2Switch(config-if)# switchport port-security aging time 2Switch(config-if)# switchport port-security aging type inactivitySwitch(config-if)# switchport port-security aging static
This example shows how to disable aging for configured secure addresses:
Switch(config)# interface gigabitethernet1/0/2Switch(config-if)# no switchport port-security aging static
To configure secure MAC addresses or sticky MAC address learning, use the switchport port-security mac-address interface configuration command. To return to the default setting, use the no form of this command.
A secure MAC address for the interface by entering a 48-bit MAC address. You can add additional secure MAC addresses up to the maximum value configured.
vlanvlan-id
(Optional) On a trunk port only, specifies the VLAN ID and the MAC address. If no VLAN ID is specified, the native VLAN is used.
vlan access
(Optional) On an access port only, specifies the VLAN as an access VLAN.
vlan voice
(Optional) On an access port only, specifies the VLAN as a voice VLAN.
Note
The voice keyword is available only if voice VLAN is configured on a port and if that port is not the access VLAN.
sticky
Enables the interface for sticky learning. When sticky learning is enabled, the interface adds all secure MAC addresses that are dynamically learned to the running configuration and converts these addresses to sticky secure MAC addresses.
mac-address
(Optional) A MAC address to specify a sticky secure MAC address.
Command Default
No secure MAC addresses are configured.
Sticky learning is disabled.
Command Modes
Interface configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
A secure port has the following limitations:
A secure port can be an access port or a trunk port; it cannot be a dynamic access port.
A secure port cannot be a routed port.
A secure port cannot be a protected port.
A secure port cannot be a destination port for Switched Port Analyzer (SPAN).
A secure port cannot belong to a Gigabit or 10-Gigabit EtherChannel port group.
You cannot configure static secure or sticky secure MAC addresses in the voice VLAN.
When you enable port security on an interface that is also configured with a voice VLAN, set the maximum allowed secure addresses on the port to two. When the port is connected to a Cisco IP phone, the IP phone requires one MAC address. The Cisco IP phone address is learned on the voice VLAN, but is not learned on the access VLAN. If you connect a single PC to the Cisco IP phone, no additional MAC addresses are required. If you connect more than one PC to the Cisco IP phone, you must configure enough secure addresses to allow one for each PC and one for the Cisco IP phone.
Voice VLAN is supported only on access ports and not on trunk ports.
Sticky secure MAC addresses have these characteristics:
When you enable sticky learning on an interface by using the switchport port-security mac-address sticky interface configuration command, the interface converts all the dynamic secure MAC addresses, including those that were dynamically learned before sticky learning was enabled, to sticky secure MAC addresses and adds all sticky secure MAC addresses to the running configuration.
If you disable sticky learning by using the no switchport port-security mac-address sticky interface configuration command or the running configuration is removed, the sticky secure MAC addresses remain part of the running configuration but are removed from the address table. The addresses that were removed can be dynamically reconfigured and added to the address table as dynamic addresses.
When you configure sticky secure MAC addresses by using the switchport port-security mac-address stickymac-address interface configuration command, these addresses are added to the address table and the running configuration. If port security is disabled, the sticky secure MAC addresses remain in the running configuration.
If you save the sticky secure MAC addresses in the configuration file, when the switch restarts or the interface shuts down, the interface does not need to relearn these addresses. If you do not save the sticky secure addresses, they are lost. If sticky learning is disabled, the sticky secure MAC addresses are converted to dynamic secure addresses and are removed from the running configuration.
If you disable sticky learning and enter the switchport port-security mac-address stickymac-address interface configuration command, an error message appears, and the sticky secure MAC address is not added to the running configuration.
You can verify your settings by using the show port-security privileged EXEC command.
Examples
This example shows how to configure a secure MAC address and a VLAN ID on a port:
To configure the maximum number of secure MAC addresses, use the switchport port-security maximum command in interface configuration mode. To return to the default settings, use the no form of this command.
Sets the maximum number of secure MAC addresses for the interface.
The default setting is 1.
vlan
(Optional) For trunk ports, sets the maximum number of secure MAC addresses on a VLAN or range of VLANs. If the vlan keyword is not entered, the default value is used.
vlan-list
(Optional) Range of VLANs separated by a hyphen or a series of VLANs separated by commas. For nonspecified VLANs, the per-VLAN maximum value is used.
access
(Optional) On an access port only, specifies the VLAN as an access VLAN.
voice
(Optional) On an access port only, specifies the VLAN as a voice VLAN.
Note
The voice keyword is available only if voice VLAN is configured on a port and if that port is not the access VLAN.
Command Default
When port security is enabled and no keywords are entered, the default maximum number of secure MAC addresses is 1.
Command Modes
Interface configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
The maximum number of secure MAC addresses that you can configure on a switch or switch stack is set by the maximum number of available MAC addresses allowed in the system. This number is determined by the active Switch Database Management (SDM) template. See the sdm prefer command. This number represents the total of available MAC addresses, including those used for other Layer 2 functions and any other secure MAC addresses configured on interfaces.
A secure port has the following limitations:
A secure port can be an access port or a trunk port.
A secure port cannot be a routed port.
A secure port cannot be a protected port.
A secure port cannot be a destination port for Switched Port Analyzer (SPAN).
A secure port cannot belong to a Gigabit or 10-Gigabit EtherChannel port group.
When you enable port security on an interface that is also configured with a voice VLAN, set the maximum allowed secure addresses on the port to two. When the port is connected to a Cisco IP phone, the IP phone requires one MAC address. The Cisco IP phone address is learned on the voice VLAN, but is not learned on the access VLAN. If you connect a single PC to the Cisco IP phone, no additional MAC addresses are required. If you connect more than one PC to the Cisco IP phone, you must configure enough secure addresses to allow one for each PC and one for the Cisco IP phone.
Voice VLAN is supported only on access ports and not on trunk ports.
When you enter a maximum secure address value for an interface, if the new value is greater than the previous value, the new value overrides the previously configured value. If the new value is less than the previous value and the number of configured secure addresses on the interface exceeds the new value, the command is rejected.
Setting a maximum number of addresses to one and configuring the MAC address of an attached device ensures that the device has the full bandwidth of the port.
When you enter a maximum secure address value for an interface, this occurs:
If the new value is greater than the previous value, the new value overrides the previously configured value.
If the new value is less than the previous value and the number of configured secure addresses on the interface exceeds the new value, the command is rejected.
You can verify your settings by using the show port-security privileged EXEC command.
Examples
This example shows how to enable port security on a port and to set the maximum number of secure addresses to 5. The violation mode is the default, and no secure MAC addresses are configured.
To configure secure MAC address violation mode or the action to be taken if port security is violated, use the switchport port-security violation command in interface configuration mode. To return to the default settings, use the no form of this command.
Sets the security violation mode to per-VLAN shutdown.
Command Default
The default violation mode is shutdown.
Command Modes
Interface configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
In the security violation protect mode, when the number of port secure MAC addresses reaches the maximum limit allowed on the port, packets with unknown source addresses are dropped until you remove a sufficient number of secure MAC addresses to drop below the maximum value or increase the number of maximum allowable addresses. You are not notified that a security violation has occurred.
Note
We do not recommend configuring the protect mode on a trunk port. The protect mode disables learning when any VLAN reaches its maximum limit, even if the port has not reached its maximum limit.
In the security violation restrict mode, when the number of secure MAC addresses reaches the limit allowed on the port, packets with unknown source addresses are dropped until you remove a sufficient number of secure MAC addresses or increase the number of maximum allowable addresses. An SNMP trap is sent, a syslog message is logged, and the violation counter increments.
In the security violation shutdown mode, the interface is error-disabled when a violation occurs and the port LED turns off. An SNMP trap is sent, a syslog message is logged, and the violation counter increments. When a secure port is in the error-disabled state, you can bring it out of this state by entering the errdisable recovery cause psecure-violation global configuration command, or you can manually re-enable it by entering the shutdown and no shutdown interface configuration commands.
When the security violation mode is set to per-VLAN shutdown, only the VLAN on which the violation occurred is error-disabled.
A secure port has the following limitations:
A secure port can be an access port or a trunk port.
A secure port cannot be a routed port.
A secure port cannot be a protected port.
A secure port cannot be a destination port for Switched Port Analyzer (SPAN).
A secure port cannot belong to a Gigabit or 10-Gigabit EtherChannel port group.
A security violation occurs when the maximum number of secure MAC addresses are in the address table and a station whose MAC address is not in the address table attempts to access the interface or when a station whose MAC address is configured as a secure MAC address on another secure port attempts to access the interface.
When a secure port is in the error-disabled state, you can bring it out of this state by entering the errdisable recovery causepsecure-violation global configuration command. You can manually re-enable the port by entering the shutdown and no shutdown interface configuration commands or by using the clear errdisable interface privileged EXEC command.
You can verify your settings by using the show port-security privileged EXEC command.
Examples
This example show how to configure a port to shut down only the VLAN if a MAC security violation occurs:
Configures the maximum number of secure MAC addresses.
system mtu
To set the global maximum packet size or MTU size for switched packets on Gigabit Ethernet and 10-Gigabit Ethernet ports, use the
system mtu command in global configuration mode. To restore the global MTU value to its default value
use the no form of this command.
systemmtubytes
nosystemmtu
Syntax Description
bytes
The global MTU size in bytes. The range is 1500 to 9198 bytes; the default is 1500 bytes.
Command Default
The default MTU size for all ports is 1500 bytes.
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
You can verify your setting by entering the show system mtu
privileged EXEC command.
The switch does not support the MTU on a per-interface basis.
If you enter a value that is outside the allowed range for the specific type of interface, the value is not accepted.
Examples
This example shows how to set the global system MTU size to 6000 bytes:
Switch(config)# system mtu 6000
Global Ethernet MTU is set to 6000 bytes.
Note: this is the Ethernet payload size, not the total
Ethernet frame size, which includes the Ethernet
header/trailer and possibly other tags, such as ISL or
802.1q tags.
To create a network-policy profile for the voice-signaling application type, use the voice-signaling vlan command in network-policy configuration mode. To delete the policy, use the no form of this command.
(Optional) The VLAN for voice traffic. The range is 1 to 4094.
coscos-value
(Optional) Specifies the Layer 2 priority class of service (CoS) for the configured VLAN. The range is 0 to 7; the default is 5.
dscpdscp-value
(Optional) Specifies the differentiated services code point (DSCP) value for the configured VLAN. The range is 0 to 63; the default is 46.
dot1p
(Optional) Configures the phone to use IEEE 802.1p priority tagging and to use VLAN 0 (the native VLAN).
none
(Optional) Does not instruct the Cisco IP phone about the voice VLAN. The phone uses the configuration from the phone key pad.
untagged
(Optional) Configures the phone to send untagged voice traffic. This is the default for the phone.
Command Default
No network-policy profiles for the voice-signaling application type are defined.
The default CoS value is 5.
The default DSCP value is 46.
The default tagging mode is untagged.
Command Modes
Network-policy profile configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
Use the network-policy profile global configuration command to create a profile and to enter network-policy profile configuration mode.
The voice-signaling application type is for network topologies that require a different policy for voice signaling than for voice media. This application type should not be advertised if all of the same network policies apply as those advertised in the voice policy TLV.
When you are in network-policy profile configuration mode, you can create the profile for voice-signaling by specifying the values for VLAN, class of service (CoS), differentiated services code point (DSCP), and tagging mode.
These profile attributes are contained in the Link Layer Discovery Protocol for Media Endpoint Devices (LLDP-MED) network-policy time-length-value (TLV).
To return to privileged EXEC mode from the network-policy profile configuration mode, enter the exit command.
Examples
This example shows how to configure voice-signaling for VLAN 200 with a priority 2 CoS:
Switch(config)# network-policy profile 1Switch(config-network-policy)# voice-signaling vlan 200 cos 2
This example shows how to configure voice-signaling for VLAN 400 with a DSCP value of 45:
Creates a network-policy profile for the voice application type.
voice vlan (network-policy configuration)
To create a network-policy profile for the voice application type, use the voice vlan command in network-policy configuration mode. To delete the policy, use the no form of this command.
(Optional) The VLAN for voice traffic. The range is 1 to 4094.
coscos-value
(Optional) Specifies the Layer 2 priority class of service (CoS) for the configured VLAN. The range is 0 to 7; the default is 5.
dscpdscp-value
(Optional) Specifies the differentiated services code point (DSCP) value for the configured VLAN. The range is 0 to 63; the default is 46.
dot1p
(Optional) Configures the phone to use IEEE 802.1p priority tagging and to use VLAN 0 (the native VLAN).
none
(Optional) Does not instruct the Cisco IP phone about the voice VLAN. The phone uses the configuration from the phone key pad.
untagged
(Optional) Configures the phone to send untagged voice traffic. This is the default for the phone.
Command Default
No network-policy profiles for the voice application type are defined.
The default CoS value is 5.
The default DSCP value is 46.
The default tagging mode is untagged.
Command Modes
Network-policy profile configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
Use the network-policy profile global configuration command to create a profile and to enter network-policy profile configuration mode.
The voice application type is for dedicated IP telephones and similar devices that support interactive voice services. These devices are typically deployed on a separate VLAN for ease of deployment and enhanced security through isolation from data applications.
When you are in network-policy profile configuration mode, you can create the profile for voice by specifying the values for VLAN, class of service (CoS), differentiated services code point (DSCP), and tagging mode.
These profile attributes are contained in the Link Layer Discovery Protocol for Media Endpoint Devices (LLDP-MED) network-policy time-length-value (TLV).
To return to privileged EXEC mode from the network-policy profile configuration mode, enter the exit command.
Examples
This example shows how to configure the voice application type for VLAN 100 with a priority 4 CoS:
Switch(config)# network-policy profile 1Switch(config-network-policy)# voice vlan 100 cos 4
This example shows how to configure the voice application type for VLAN 100 with a DSCP value of 34:
Configures 10-Gigabit Ethernet interface. Values range from 0 to 9.
Vlaninterface-name
Configures VLANs. Values range from 1 to 4095.
Command Default
None
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Examples
This example shows how to configure the wireless AP-manager:
Switch# wireless ap-manager interface vlan
<1-4095> Vlan interface number
This example shows how to configure the wireless AP-manager:
Switch# #wireless ap-manager interface vlan 10
wireless exclusionlist
To manage exclusion list entries, use the
wirelessexclusionlist global configuration command. To remove the exclusion list entries, use the
no form of the command.
Specifies the link test frame size for each packet. The values range from 1 to 1400.
number-of-framesvalue
Specifies the number of frames to be sent for the link test. The values range from 1 to 100.
Command Default
None
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Examples
This example shows how to configure the link test frame size of each frame as 10:
Switch# wireless linktest frame-size 10
wireless management interface
To configure wireless management parameters on an interface, use the
wirelessmanagementinterface global configuration command. To remove a wireless management parameters on an interface, use the
no form of the command.
The 10-Gigabit Ethernet
interface number. The values range from 0 to 9.
Vlaninterface-name
The VLAN
interface number. The values range from 1 to 4095.
Command Default
None
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Examples
This example shows how to configure VLAN 10 on the wireless interface:
Switch# wireless management interface Vlan 10
wireless peer-blocking forward-upstream
To configure peer-to-peer blocking for forward upstream, use the
wirelesspeer-blockingforward-upstream command. To remove a peer-to-peer blocking, use the
no form of the command.