To enable debugging of spanning-tree activities, use the debug spanning-tree command in EXEC mode. To disable debugging, use the no form of this command.
Displays the spanning-tree synchronization event debug messages.
switch
Displays switch shim command debug messages. This shim is the software module that is the interface between the generic Spanning Tree Protocol (STP) code and the platform-specific code of various switch platforms.
uplinkfast
Displays UplinkFast-event debug messages.
Command Default
Debugging is disabled.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
Modification
15.0
This command was introduced.
Usage Guidelines
The undebug spanning-tree command is the same as the no debug spanning-tree 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. You also can use the remote commandstack-member-number LINE EXEC command on the active switch to enable debugging on a member switch without first starting a session.
Related Commands
Command
Description
show debugging
Displays information about the types of debugging that are enabled.
show spanning-tree
Displays spanning-tree state information.
ip wccp
To enable the web cache service, and specify the service number that corresponds to a dynamic service that is defined by the application engine, use the ip wccp global configuration command on the switch. Use the no form of this command to disable the service.
Specifies the web-cache service (WCCP Version 1 and Version 2).
service-number
Dynamic service identifier, which means the service definition is dictated by the cache. The dynamic service number can be from 0 to 254. The maximum number of services is 256, which includes the web-cache service specified with the web-cache keyword.
group-addressgroupaddress
(Optional) Specifies the multicast group address used by the switches and the application engines to participate in the service group.
group-listaccess-list
(Optional) If a multicast group address is not used, specifies a list of valid IP addresses that correspond to the application engines that are participating in the service group.
redirect-listaccess-list
(Optional) Specifies the redirect service for specific hosts or specific packets from hosts.
password encryption-numberpassword
(Optional) Specifies an encryption number. The range is 0 to 7. Use 0 for not encrypted, and use 7 for proprietary. Also, specifies a password name up to seven characters in length. The switch combines the password with the MD5 authentication value to create security for the connection between the switch and the application engine. By default, no password is configured, and no authentication is performed.
Command Default
WCCP services are not enabled on the device.
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
WCCP transparent caching bypasses Network Address Translation (NAT) when Cisco Express Forwarding switching is enabled. To work around this situation, configure WCCP transparent caching in the outgoing direction, enable Cisco Express Forwarding switching on the content engine interface, and specify the ip wccp web-cache redirect out command. Configure WCCP in the incoming direction on the inside interface by specifying the ip wccp redirect exclude in command on the router interface facing the cache. This configuration prevents the redirection of any packets arriving on that interface.
You can also include a redirect list when configuring a service group. The specified redirect list will deny packets with a NAT (source) IP address and prevent redirection.
This command instructs a switch to enable or disable support for the specified service number or the web-cache service name. A service number can be from 0 to 254. Once the service number or name is enabled, the router can participate in the establishment of a service group.
When the no ip wccp command is entered, the switch terminates participation in the service group, deallocates space if none of the interfaces still has the service configured, and terminates the WCCP task if no other services are configured.
The keywords following the web-cache keyword and the service-number argument are optional and may be specified in any order, but only may be specified once.
Examples
Example
The following example configures a web cache, the interface connected to the application engine or the server, and the interface connected to the client:
Switch(config)# ip wccp web-cacheSwitch(config)# interface gigabitethernet1/0/1Switch(config-if)# no switchportSwitch(config-if)# ip address 172.20.10.30 255.255.255.0Switch(config-if)# no shutdownSwitch(config-if)# exitSwitch(config)# interface gigabitethernet1/0/2Switch(config-if)# no switchportSwitch(config-if)#
*Dec 6 13:11:29.507: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/3, changed state to down
Switch(config-if)# ip address 175.20.20.10 255.255.255.0Switch(config-if)# no shutdownSwitch(config-if)# ip wccp web-cache redirect inSwitch(config-if)# ip wccp web-cache group-listenSwitch(config-if)# exit
show ip sla statistics
To display current or aggregated operational status and statistics of all Cisco IOS IP Service Level Agreement (SLA) operations or a
specified operation, use the
showipslastatistics command in user EXEC or
privileged EXEC mode.
(Optional) Number of the operation for which operational status and
statistics are displayed. Accepted values are from 1 to
2147483647.
details
Specifies
detailed output.
aggregated
Specifies the
IP SLA aggregated statistics.
Command Default
Displays output for all running IP SLA operations.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
Use the showipslastatistics to display the current state of IP SLA operations, including how much life the operation has left, whether the operation is active, and the completion time. The output also includes the monitoring data returned for the last (most recently completed) operation. This generated operation ID is displayed when you use the show ip sla configuration command for the base multicast operation, and as part of the summary statistics for the entire operation.
Enter the show command for a specific operation ID to display details for that one responder.
Examples
Examples
The following is sample output from the showipslastatistics command:
Switch# show ip sla statistics
Current Operational State
Entry Number: 3
Modification Time: *22:15:43.000 UTC Sun Feb 11 2001
Diagnostics Text:
Last Time this Entry was Reset: Never
Number of Octets in use by this Entry: 1332
Number of Operations Attempted: 2
Current Seconds Left in Life: 3511
Operational State of Entry: active
Latest Completion Time (milliseconds): 544
Latest Operation Start Time: *22:16:43.000 UTC Sun Feb 11 2001
Latest Oper Sense: ok
Latest Sense Description: 200 OK
Total RTT: 544
DNS RTT: 12
TCP Connection RTT: 28
HTTP Transaction RTT: 504
HTTP Message Size: 9707
show monitor
To display information about all Switched Port Analyzer (SPAN) and Remote SPAN (RSPAN) sessions, use the show monitor command in EXEC mode.
show monitor [
session {
session_number |
all |
local |
rangelist |
remote} [
detail]]
Syntax Description
session
(Optional) Displays information about specified SPAN sessions.
session_number
The number of the SPAN or RSPAN session. The range is 1 to 66.
all
Displays all SPAN sessions.
local
Displays only local SPAN sessions.
rangelist
Displays a range of SPAN sessions, where list is the range of valid sessions. The range is either a single session or a range of sessions described by two numbers, the lower one first, separated by a hyphen. Do not enter any spaces between comma-separated parameters or in hyphen-specified ranges.
Note
This keyword is available only in privileged EXEC mode.
remote
Displays only remote SPAN sessions.
detail
(Optional) Displays detailed information about the specified sessions.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
The output is the same for the show monitor command and the show monitor session all command.
Examples
Examples
This is an example of output for the show monitor user EXEC command:
Switch# show monitor
Session 1
---------
Type : Local Session
Source Ports :
RX Only : Gi4/0/1
Both : Gi4/0/2-3,Gi4/0/5-6
Destination Ports : Gi4/0/20
Encapsulation : Replicate
Ingress : Disabled
Session 2
---------
Type : Remote Source Session
Source VLANs :
TX Only : 10
Both : 1-9
Dest RSPAN VLAN : 105
This is an example of output for the show monitor user EXEC command for local SPAN source session 1:
Switch# show monitor session 1
Session 1
---------
Type : Local Session
Source Ports :
RX Only : Gi4/0/1
Both : Gi4/0/2-3,Gi4/0/5-6
Destination Ports : Gi4/0/20
Encapsulation : Replicate
Ingress : Disabled
This is an example of output for the show monitor session all user EXEC command when ingress traffic forwarding is enabled:
Switch# show monitor session all
Session 1
---------
Type : Local Session
Source Ports :
Both : Gi4/0/2
Destination Ports : Gi4/0/3
Encapsulation : Native
Ingress : Enabled, default VLAN = 5
Ingress encap : DOT1Q
Session 2
---------
Type : Local Session
Source Ports :
Both : Gi4/0/8
Destination Ports : Gi4/012
Encapsulation : Replicate
Ingress : Enabled, default VLAN = 4
Ingress encap : Untagged
show platform ip wccp
To display platform-dependent Web Cache Communication Protocol (WCCP) information, use
the show platform ip wccp privileged EXEC command.
show platform ip wccp
{ cache-engines | interfaces | service-groups } [
switchswitch-number]
Syntax Description
cache-engines
Displays WCCP cache engines.
interfaces
Displays WCCP interfaces.
service-groups
Displays WCCP service groups.
switchswitch-number
(Optional) Displays WCCP information only for specified switch-number.
Command Modes
Privileged EXEC
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
Use this command only when you are working directly with a technical support
representative while troubleshooting a problem. Do not use this command unless a
technical support representative asks you to do so.
This command is available only if your switch is running the IP services feature
set.
Examples
The following example displays WCCP interfaces:
Switch# show platform ip wccp interfaces
WCCP Interfaces
**** WCCP Interface Gi1/0/3 iif_id:0x104a60000000087 (#SG:1), vrf:0 Ingress
le_handle:0x565dd208 IPv4 Sw-Label:3, Asic-Label:3
* Service group id:0 type: Well-known token:126 vrf:0 (ref count:1)
Open service prot: PROT_TCP l4_type: Dest ports priority: 240
port[0]: 80
snmp-server enable traps
To enable the switch to send Simple Network Management Protocol (SNMP) notifications for
various traps or inform requests to the network management system (NMS), use the
snmp-server enable traps command in global configuration
mode. Use the no form of this command to return to the default
setting.
(Optional) Generates entity field-replaceable unit (FRU) control traps. In a
switch stack, this trap refers to the insertion or removal of a switch in
the stack.
*The command options marked with an asterisk in the table above have sub-commands. For more information on these sub-commands, see the Related Topics section below.
Specify the host (NMS) that receives the traps by using the snmp-server
host global configuration command. If no trap types are specified,
all trap types are sent.
When supported, use the snmp-server enable traps command to
enable sending of traps or informs.
Note
Though visible in the command-line help strings, the fru-ctrl,
insertion, and removal keywords are not
supported on the switch. The snmp-server enable informs
global configuration command is not supported. To enable the sending of SNMP inform
notifications, use the snmp-server enable traps global
configuration command combined with the snmp-server hosthost-addrinforms global configuration command.
Note
Informs are not supported in SNMPv1.
To enable more than one type of trap, you must enter a separate snmp-server
enable traps command for each trap type.
Examples
This example shows how to enable more than one type of SNMP trap:
To enable the switch to send Simple Network Management Protocol (SNMP) notifications for
Border Gateway Protocol (BGP) state-change traps to the network management system (NMS),
use the snmp-server enable traps bgp command in global
configuration mode. Use the no form of this command to return to the default
setting.
(Optional) Enable finite state machine (FSM) state-change traps.
all
(Optional) Enable a CISCO specific trap for all FSM state changes.
backward-trans
(Optional) Enable traps for FSM state changes.
limited
(Optional) Enable a trap for standard backward transition and established.
threshold
(Optional) Enable traps for threshold events.
prefix
(Optional) Enable a CISCO specific trap for prefix threshold events.
Command Default
The sending of SNMP BGP traps is disabled.
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
This command is available only when the IP services feature set is enabled on the switch.
Specify the host (NMS) that receives the traps by using the snmp-server
host global configuration command. If no trap types are specified,
all trap types are sent.
When supported, use the snmp-server enable traps command to
enable sending of traps or informs.
Note
Informs are not supported in SNMPv1.
To enable more than one type of trap, you must enter a separate snmp-server
enable traps command for each trap type.
Examples
This example shows how to send BGP state change traps to the NMS:
To generate STP bridge MIB traps, use the snmp-server enable traps
bridge command in global configuration mode. Use the
no form of this command to return to the default
setting.
Specify the host (NMS) that receives the traps by using the snmp-server
host global configuration command. If no trap types are specified,
all trap types are sent.
Note
Informs are not supported in SNMPv1.
To enable more than one type of trap, you must enter a separate snmp-server
enable traps command for each trap type.
Examples
This example shows how to send bridge new root traps to the NMS:
To enable data-collection-MIB traps, use the snmp-server enable traps
bulkstat command in global configuration mode. Use the
no form of this command to return to the default
setting.
(Optional) Enables data-collection-MIB transfer traps.
Command Default
The sending of data-collection-MIB traps is disabled.
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
Specify the host (NMS) that receives the traps by using the snmp-server
host global configuration command. If no trap types are specified,
all trap types are sent.
Note
Informs are not supported in SNMPv1.
To enable more than one type of trap, you must enter a separate snmp-server
enable traps command for each trap type.
Examples
This example shows how to generate data-collection-MIB collection traps:
To enable SNMP CISCO-CALLHOME-MIB traps, use the snmp-server enable traps
call-home command in global configuration mode. Use the
no form of this command to return to the default
setting.
The sending of SNMP CISCO-CALLHOME-MIB traps is disabled.
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
Specify the host (NMS) that receives the traps by using the snmp-server
host global configuration command. If no trap types are specified,
all trap types are sent.
Note
Informs are not supported in SNMPv1.
To enable more than one type of trap, you must enter a separate snmp-server
enable traps command for each trap type.
Examples
This example shows how to generate SNMP message-send-fail traps:
To enable SNMP Cisco Express Forwarding (CEF) traps, use the snmp-server enable traps
cef command in global configuration mode. Use the
no form of this command to return to the default
setting.
Specify the host (NMS) that receives the traps by using the snmp-server
host global configuration command. If no trap types are specified,
all trap types are sent.
Note
Informs are not supported in SNMPv1.
To enable more than one type of trap, you must enter a separate snmp-server
enable traps command for each trap type.
Examples
This example shows how to generate SNMP CEF inconsistency traps:
To enable CPU notifications, use the snmp-server enable traps
cpu command in global configuration mode. Use the
no form of this command to return to the default
setting.
snmp-serverenabletrapscpu [
threshold]
nosnmp-serverenabletrapscpu [
threshold]
Syntax Description
threshold
(Optional) Enables CPU threshold notification.
Command Default
The sending of CPU notifications is disabled.
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
Specify the host (NMS) that receives the traps by using the snmp-server
host global configuration command. If no trap types are specified,
all trap types are sent.
Note
Informs are not supported in SNMPv1.
To enable more than one type of trap, you must enter a separate snmp-server
enable traps command for each trap type.
Examples
This example shows how to generate CPU threshold notifications:
Switch(config)# snmp-server enable traps cpu threshold
snmp-server enable traps envmon
To enable SNMP environmental traps, use the snmp-server enable traps
envmon command in global configuration mode. Use the
no form of this command to return to the default
setting.
snmp-serverenabletrapsenvmon [
fan |
shutdown |
status |
supply |
temperature]
nosnmp-serverenabletrapsenvmon [
fan |
shutdown |
status |
supply |
temperature]
(Optional) Enables environmental monitor temperature traps.
Command Default
The sending of environmental SNMP traps is disabled.
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
Specify the host (NMS) that receives the traps by using the snmp-server
host global configuration command. If no trap types are specified,
all trap types are sent.
Note
Informs are not supported in SNMPv1.
To enable more than one type of trap, you must enter a separate snmp-server
enable traps command for each trap type.
Examples
This example shows how to generate fan traps:
Switch(config)# snmp-server enable traps envmon fan
snmp-server enable traps errdisable
To enable SNMP notifications of error disabling, use the snmp-server enable traps
errdisable command in global configuration mode. Use the
no form of this command to return to the default
setting.
(Optional) Specifies number of notifications per minute as the notification rate. Accepted values are from 0-4294967295.
Command Default
The sending of SNMP notifications of error disabling is disabled.
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
Specify the host (NMS) that receives the traps by using the snmp-server
host global configuration command. If no trap types are specified,
all trap types are sent.
Note
Informs are not supported in SNMPv1.
To enable more than one type of trap, you must enter a separate snmp-server
enable traps command for each trap type.
Examples
This example shows how to set the number SNMP notifications of error disabling to 2:
To enable SNMP flash notifications, use the snmp-server enable traps
flash command in global configuration mode. Use the
no form of this command to return to the default
setting.
The sending of SNMP flash notifications is disabled.
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
Specify the host (NMS) that receives the traps by using the snmp-server
host global configuration command. If no trap types are specified,
all trap types are sent.
Note
Informs are not supported in SNMPv1.
To enable more than one type of trap, you must enter a separate snmp-server
enable traps command for each trap type.
Examples
This example shows how to generate SNMP flash insertion notifications:
To enable intermediate system-to-intermediate system (IS-IS) link-state routing protocol traps, use the snmp-server enable traps
isis command in global configuration mode. Use the
no form of this command to return to the default
setting.
Specify the host (NMS) that receives the traps by using the snmp-server
host global configuration command. If no trap types are specified,
all trap types are sent.
Note
Informs are not supported in SNMPv1.
To enable more than one type of trap, you must enter a separate snmp-server
enable traps command for each trap type.
Examples
This example shows how to generate IS-IS error traps:
To enable license traps, use the snmp-server enable traps
license command in global configuration mode. Use the
no form of this command to return to the default
setting.
Specify the host (NMS) that receives the traps by using the snmp-server
host global configuration command. If no trap types are specified,
all trap types are sent.
Note
Informs are not supported in SNMPv1.
To enable more than one type of trap, you must enter a separate snmp-server
enable traps command for each trap type.
Examples
This example shows how to generate license deployment traps:
To enable SNMP MAC notification traps, use the snmp-server enable traps
mac-notification command in global configuration mode. Use the
no form of this command to return to the default
setting.
The sending of SNMP MAC notification traps is disabled.
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
Specify the host (NMS) that receives the traps by using the snmp-server
host global configuration command. If no trap types are specified,
all trap types are sent.
Note
Informs are not supported in SNMPv1.
To enable more than one type of trap, you must enter a separate snmp-server
enable traps command for each trap type.
Examples
This example shows how to generate SNMP MAC notification change traps:
To enable SNMP Open Shortest Path First (OSPF) traps, use the snmp-server
enable traps ospf command in global configuration mode. Use the
no form of this command to return to the default
setting.
(Optional) Specifies window of time in seconds for rate-limit traps. Accepted values are 2 - 60.
max-number-of-traps
(Optional) Specifies maximum number of rate-limit traps to be sent in window time.
retransmit
(Optional) Enable packet-retransmit traps.
state-change
(Optional) Enable state-change traps.
Command Default
The sending of OSPF SNMP traps is disabled.
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
Specify the host (NMS) that receives the traps by using the snmp-server
host global configuration command. If no trap types are specified,
all trap types are sent.
Note
Informs are not supported in SNMPv1.
To enable more than one type of trap, you must enter a separate snmp-server
enable traps command for each trap type.
Examples
This example shows how to enable LSA traps:
Switch(config)# snmp-server enable traps ospf lsa
snmp-server enable traps pim
To enable SNMP Protocol-Independent Multicast (PIM) traps, use the
snmp-server enable traps pim command in global
configuration mode. Use the no form of this command to return
to the default setting.
(Optional) Enable rendezvous point (RP)-mapping change traps.
Command Default
The sending of PIM SNMP traps is disabled.
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
Specify the host (NMS) that receives the traps by using the snmp-server
host global configuration command. If no trap types are specified,
all trap types are sent.
Note
Informs are not supported in SNMPv1.
To enable more than one type of trap, you must enter a separate snmp-server
enable traps command for each trap type.
Examples
This example shows how to enable invalid PIM message traps:
To enable SNMP port security traps, use the snmp-server enable traps
port-security command in global configuration mode. Use the
no form of this command to return to the default
setting.
(Optional) Set the maximum number of port-security traps sent per second. The range is from 0 to 1000; the default is 0 (no limit imposed; a trap is sent at every occurrence).
Command Default
The sending of port security SNMP traps is disabled.
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
Specify the host (NMS) that receives the traps by using the snmp-server
host global configuration command. If no trap types are specified,
all trap types are sent.
Note
Informs are not supported in SNMPv1.
To enable more than one type of trap, you must enter a separate snmp-server
enable traps command for each trap type.
Examples
This example shows how to enable port-security traps at a rate of 200 per second:
To enable SNMP power-over-Ethernet (PoE) traps, use the snmp-server enable traps
power-ethernet command in global configuration mode. Use the
no form of this command to return to the default
setting.
Enable inline power group-based traps for the specified group number or list.
police
Enable inline power policing traps.
Command Default
The sending of power-over-Ethernet SNMP traps is disabled.
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
Specify the host (NMS) that receives the traps by using the snmp-server
host global configuration command. If no trap types are specified,
all trap types are sent.
Note
Informs are not supported in SNMPv1.
To enable more than one type of trap, you must enter a separate snmp-server
enable traps command for each trap type.
Examples
This example shows how to enable power-over-Ethernet traps for group
poe1:
Switch(config)# snmp-server enable traps poower-over-ethernet group poe1
snmp-server enable traps snmp
To enable SNMP traps, use the snmp-server enable traps snmp
command in global configuration mode. Use the no form of this
command to return to the default setting.
Specify the host (NMS) that receives the traps by using the snmp-server
host global configuration command. If no trap types are specified,
all trap types are sent.
Note
Informs are not supported in SNMPv1.
To enable more than one type of trap, you must enter a separate snmp-server
enable traps command for each trap type.
Examples
This example shows how to enable a warmstart SNMP trap:
To enable SNMP stackwise traps, use the snmp-server enable traps
stackwise command in global configuration mode. Use the
no form of this command to return to the default
setting.
(Optional) Enables stackwise stack power GLS trap.
ILS
(Optional) Enables stackwise stack power ILS trap.
SRLS
(Optional) Enables stackwise stack power SRLS trap.
insufficient-power
(Optional) Enables stackwise stack power unbalanced power supplies trap.
invalid-input-current
(Optional) Enables stackwise stack power invalid input current trap.
invalid-output-current
(Optional) Enables stackwise stack power invalid output current trap.
member-removed
(Optional) Enables stackwise stack member removed trap.
member-upgrade-notification
(Optional) Enables stackwise member to be reloaded for upgrade trap.
new-master
(Optional) Enables stackwise new master trap.
Syntax Description
new-member
(Optional) Enables stackwise stack new member trap.
port-change
(Optional) Enables stackwise port change trap.
power-budget-warning
(Optional) Enables stackwise stack power budget warning trap.
power-invalid-topology
(Optional) Enables stackwise stack power invalid topology trap.
power-link-status-changed
(Optional) Enables stackwise stack power link status changed trap.
power-oper-status-changed
(Optional) Enables stackwise stack power port oper status changed trap.
power-priority-conflict
(Optional) Enables stackwise stack power priority conflict trap.
power-version-mismatch
(Optional) Enables stackwise stack power version mismatch discovered trap.
ring-redundant
(Optional) Enables stackwise stack ring redundant trap.
stack-mismatch
(Optional) Enables stackwise stack mismatch trap.
unbalanced-power-supplies
(Optional) Enables stackwise stack power unbalanced power supplies trap.
under-budget
(Optional) Enables stackwise stack power under budget trap.
under-voltage
(Optional) Enables stackwise stack power under voltage trap.
Command Default
The sending of SNMP stackwise traps is disabled.
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
Specify the host (NMS) that receives the traps by using the snmp-server
host global configuration command. If no trap types are specified,
all trap types are sent.
Note
Informs are not supported in SNMPv1.
To enable more than one type of trap, you must enter a separate snmp-server
enable traps command for each trap type.
Examples
This example shows how to generate stackwise stack power GLS traps:
To enable SNMP storm-control trap parameters, use the snmp-server enable traps
storm-control command in global configuration mode. Use the
no form of this command to return to the default
setting.
(Optional) Specifies the SNMP storm-control trap rate in minutes. Accepted values are from 0-1000.
Command Default
The sending of SNMP storm-control trap parameters is disabled.
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
Specify the host (NMS) that receives the traps by using the snmp-server
host global configuration command. If no trap types are specified,
all trap types are sent.
Note
Informs are not supported in SNMPv1.
To enable more than one type of trap, you must enter a separate snmp-server
enable traps command for each trap type.
Examples
This example shows how to set the SNMP storm-control trap rate to 10 traps per minute:
To enable SNMP STPX MIB traps, use the snmp-server enable traps
stpx command in global configuration mode. Use the
no form of this command to return to the default
setting.
Specify the host (NMS) that receives the traps by using the snmp-server
host global configuration command. If no trap types are specified,
all trap types are sent.
Note
Informs are not supported in SNMPv1.
To enable more than one type of trap, you must enter a separate snmp-server
enable traps command for each trap type.
Examples
This example shows how to generate SNMP STPX MIB inconsistency update traps:
To enable SNMP transceiver traps, use the snmp-server enable traps
transceiver command in global configuration mode. Use the
no form of this command to return to the default
setting.
snmp-serverenabletrapstransceiver [
all]
nosnmp-serverenabletrapstransceiver [
all]
Syntax Description
all
(Optional) Enables all SNMP transceiver traps.
Command Default
The sending of SNMP transceiver traps is disabled.
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
Specify the host (NMS) that receives the traps by using the snmp-server
host global configuration command. If no trap types are specified,
all trap types are sent.
Note
Informs are not supported in SNMPv1.
To enable more than one type of trap, you must enter a separate snmp-server
enable traps command for each trap type.
Examples
This example shows how to set all SNMP transceiver traps:
Switch(config)# snmp-server enable traps transceiver all
snmp-server enable traps vrfmib
To allow SNMP vrfmib traps, use the snmp-server enable traps
vrfmib command in global configuration mode. Use the
no form of this command to return to the default
setting.
Specify the host (NMS) that receives the traps by using the snmp-server
host global configuration command. If no trap types are specified,
all trap types are sent.
Note
Informs are not supported in SNMPv1.
To enable more than one type of trap, you must enter a separate snmp-server
enable traps command for each trap type.
Examples
This example shows how to generate vrfmib trunk down traps:
To enable SNMP smart install traps, use the snmp-server enable traps
vstack command in global configuration mode. Use the
no form of this command to return to the default
setting.
snmp-serverenabletrapsvstack [
addition |
failure |
lost |
operation]
nosnmp-serverenabletrapsvstack [
addition |
failure |
lost |
operation]
The sending of SNMP smart install traps is disabled.
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
Specify the host (NMS) that receives the traps by using the snmp-server
host global configuration command. If no trap types are specified,
all trap types are sent.
Note
Informs are not supported in SNMPv1.
To enable more than one type of trap, you must enter a separate snmp-server
enable traps command for each trap type.
Examples
This example shows how to generate SNMP smart install client added traps:
To enable sending Simple Network Management Protocol (SNMP) notifications for various wireless traps or inform requests to the network management system (NMS), use the snmp-server enable traps wireless command in global configuration mode. Use the no form of this command to return to the default setting.
Enables sending traps for AP parameters that get updated.
bsnAPProfile
Enables bsn AP profile traps.
bsnAccessPoint
Enables access point traps.
bsnMobileStation
Controls wireless client traps.
bsnRogue
Enables rogue related traps.
client
Enables client traps.
mfp
Enables MFP traps.
rogue
Enables rogue traps.
Command Default
Disabled
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
Specify the host (NMS) that receives the traps by using the snmp-server
host global configuration command. If no trap types are specified,
all trap types are sent.
Note
Informs are not supported in SNMPv1.
To enable more than one type of trap, you must enter a separate snmp-server
enable traps command for each trap type.
Examples
Examples
This example shows how to generate sending AP related wireless traps:
Switch(config)# snmp-server enable traps wireless ap
snmp-server engineID
To configure a name for either the local or remote copy of SNMP, use the
snmp-serverengineID command in global configuration mode.
The engineid-string is a 24-character ID string with the name of the copy of SNMP. You need not specify the entire 24-character engine ID if it has trailing zeros. Specify only the portion of the engine ID up to the point where only zeros remain in the value. The example below configures an engine ID of 123400000000000000000000.
remoteip-address
Specifies the remote SNMP copy.
If you select remote, specify the ip-address of the device that contains the remote copy of SNMP.
udp-portport-number
(Optional) Specifies the User Datagram Protocol (UDP) port on the remote device. The default is 162.
Command Default
None
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
None
Examples
Examples
The following example configures a local engineID of 123400000000000000000000:
Switch(config)# snmp-server engineID local 1234
snmp-server host
To specify the recipient (host) of a Simple Network Management Protocol (SNMP)
notification operation, use the snmp-server host global configuration command on the
switch. Use the no form of this command to
remove the specified host.
noauth (Default)—The noAuthNoPriv security
level. This is the default if the auth |
noauth | priv keyword choice is not
specified.
priv (Optional)—Enables Data Encryption
Standard (DES) packet encryption (also called privacy).
community-string
Password-like community string sent with the notification operation. Though
you can set this string by using the snmp-server
host command, we recommend that you define this string by
using the snmp-server community global
configuration command before using the snmp-server
host command.
Note
The @ symbol is used for delimiting the context information. Avoid using the @ symbol as part of the SNMP community string when configuring this command.
notification-type
(Optional) Type of notification to be sent to the host. If no type is specified, all notifications are sent. The notification type can be one or more of the these keywords:
bgp—Send Border Gateway Protocol (BGP) state
change traps. This keyword is available only when the IP services feature
set is enabled on the switch or the active switch.
bridge—Sends SNMP Spanning Tree Protocol (STP)
bridge MIB traps.
This command is disabled by default. No notifications are sent.
If you enter this command with no keywords, the default is to send all trap types to the host. No informs are sent to this host.
If no version keyword is present, the default is Version
1.
If Version 3 is selected and no authentication keyword is entered, the default is the
noauth (noAuthNoPriv) security level.
Note
Though visible in the command-line help strings, the
fru-ctrl keyword is not supported.
Command Modes
Global configuration
Command History
Release
Modification
Cisco IOS XE 3.2SE
This command was introduced.
Usage Guidelines
SNMP notifications can be sent as traps or inform requests. Traps are unreliable because the receiver does not send acknowledgments when it receives traps. The sender cannot determine if the traps were received. However, an SNMP entity that receives an inform request acknowledges the message with an SNMP response PDU. If the sender never receives the response, the inform request can be sent again. Thus, informs are more likely to reach their intended destinations.
However, informs consume more resources in the agent and in the network. Unlike a trap, which is discarded as soon as it is sent, an inform request must be held in memory until a response is received or the request times out. Traps are also sent only once, but an inform might be retried several times. The retries increase traffic and contribute to a higher overhead on the network.
If you do not enter an snmp-server host command, no
notifications are sent. To configure the switch to send SNMP notifications, you must
enter at least one snmp-server host command. If you enter the
command with no keywords, all trap types are enabled for the host. To enable multiple
hosts, you must enter a separate snmp-server host command for
each host. You can specify multiple notification types in the command for each host.
If a local user is not associated with a remote host, the switch does not send informs
for the auth (authNoPriv) and the
priv (authPriv) authentication levels.
When multiple snmp-server host commands are given for the same
host and kind of notification (trap or inform), each succeeding command overwrites the
previous command. Only the last snmp-server host command is in
effect. For example, if you enter an snmp-server host inform
command for a host and then enter another snmp-server host
inform command for the same host, the second command replaces the
first.
The snmp-server host command is used with the
snmp-server enable traps global configuration command.
Use the snmp-server enable traps command to specify which SNMP
notifications are sent globally. For a host to receive most notifications, at least one
snmp-server enable traps command and the
snmp-server host command for that host must be enabled.
Some notification types cannot be controlled with the snmp-server enable
traps command. For example, some notification types are always
enabled. Other notification types are enabled by a different command.
The no snmp-server host command with no keywords disables
traps, but not informs, to the host. To disable informs, use the no
snmp-server host informs command.
Examples
This example shows how to configure a unique SNMP community string named comaccess for traps and prevent SNMP polling access with this string through access-list 10:
Switch(config)# snmp-server community comaccess ro 10Switch(config)# snmp-server host 172.20.2.160 comaccessSwitch(config)# access-list 10 deny any
This example shows how to send the SNMP traps to the host specified by the name myhost.cisco.com. The community string is defined as comaccess: