snmp-server enable traps

To enable all Simple Network Management Protocol (SNMP) notification types that are available on your system, use the snmp-server enable traps command in global configuration mode. To disable all available SNMP notifications, use the no form of this command.

snmp-server enable traps [notification-type] [vrrp]

nosnmp-server enable traps [notification-type] [vrrp]

Syntax Description

notification-type

(Optional) Type of notification (trap or inform) to enable or disable. If no type is specified, all notifications available on your device are enabled or disabled (if the no form is used). The notification type can be one of the following keywords:

alarms—Enables alarm filtering to limit the number of syslog messages generated. Alarms are generated for the severity configured as well as for the higher severity values.

•The severity argument is an integer or string value that identifies the severity of an alarm. Integer values are from 1 to 4. String values are critical, major, minor, and informational. The default is 4 (informational). Severity levels are defined as follows:

•ds0-busyout—Sends notification when the busyout of a DS0 interface changes state (Cisco AS5300 platform only). This notification is defined in the CISCO-POP-MGMT-MIB (enterprise 1.3.6.1.4.1.9.10.19.2), and the notification type is (1) cpmDS0BusyoutNotification.

•license—Enables licensing notifications as traps or informs. The notifications are grouped into categories that can be individually controlled by combining the keywords with the license keyword, or as a group by using the license keyword by itself.

–deploy—Controls notifications generated as a result of install, clear, or revoke license events.

–error—Controls notifications generated as a result of a problem with the license or with the usage of the license.

–imagelevel—Controls notifications related to the image level of the license.

Support for this command was implemented on the Supervisor Engine 720.

12.2(18)S

This command was integrated into Cisco IOS Release 12.2(18)S.

12.2(17d)SXB

Support for this command on the Supervisor Engine 2 was integrated into Cisco IOS Release 12.2(17d)SXB.

12.3(11)T

The vrrp notification type was added in Cisco IOS Release 12.3(11)T.

12.4(4)T

Support for the alarms notification type and severity argument was added in Cisco IOS Release 12.4(4)T.

Support for the dsp and dsp oper-state notification types was added in Cisco IOS Release 12.4(4)T.

12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.4(11)T

The dot1x notification type was added in Cisco IOS Release 12.4(11)T.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

12.2SX

This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

12.4(20)T

The license notification type keyword was added.

12.2(33)SXH

The l2tc keyword was added and supported on the Catalyst 6500 series switch.

12.2(33)SXI

The following keywords were added and supported on the Catalyst 6500 series switch:

•auth-fail-vlan

•entity-diag

•guest-vlan

•module-auto-shutdown

•no-auth-fail-vlan

•no-guest-vlan

•sys-threshold

Cisco IOS XE Release 2.6

This command was integrated into Cisco IOS XE Release 2.6.

15.0(1)S

The flowmon notification ype was added in Cisco IOS Release 15.0(1)S.

Usage Guidelines

For additional notification types, see the Related Commands table for this command.

SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests for the specified notification types. To specify whether the notifications should be sent as traps or informs, use the snmp-server host [traps |informs] command.

To configure the router to send these SNMP notifications, you must enter at least one snmp-server enable traps command. If you enter the command with no keywords, all notification types are enabled. If you enter the command with a keyword, only the notification type related to that keyword is enabled. To enable multiple types of notifications, you must issue a separate snmp-server enable trapscommand for each notification type and notification option.

Most notification types are disabled by default but some cannot be controlled with the snmp-server enable trapscommand.

The snmp-server enable traps command is used in conjunction with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP notifications. To send notifications, you must configure at least one snmp-server host command.

Catalyst 6500 Series Switches

The following MIBs were enhanced or supported in Cisco IOS Release 12.2(33)SXI and later releases on the Catalyst 6500 series switch:

Examples

The following example shows how to enable the router to send all traps to the host specified by the name myhost.cisco.com, using the community string defined as public:

Router(config)# snmp-server enable traps

Router(config)# snmp-server host myhost.cisco.com public

The following example shows how to configure an alarm severity threshold of 3:

Router# snmp-server enable traps alarms 3

The following example shows how to enable the generation of a DSP operational state notification from from the command-line interface (CLI):

Router(config)# snmp-server enable traps dsp oper-state

The following example shows how to enable the generation of a DSP operational state notification from a network management device:

setany -v2c 1.4.198.75 test cdspEnableOperStateNotification.0 -i 1

cdspEnableOperStateNotification.0=true(1)

The following example shows how to send no traps to any host. The Border Gateway Protocol (BGP) traps are enabled for all hosts, but the only traps enabled to be sent to a host are ISDN traps (which are not enabled in this example).

Router(config)# snmp-server enable traps bgp

Router(config)# snmp-server host user1 public isdn

The following example shows how to enable the router to send all inform requests to the host at the address myhost.cisco.com, using the community string defined as public:

The following example shows how to send IEEE 802.1X MIB traps to the host "myhost.example.com" using the community string defined as public:

Router(config)# snmp-server enable traps dot1x

Router(config)# snmp-server host myhost.example.com traps public

Related Commands

Command

Description

snmp-server enable traps atm pvc

Enables ATM PVC SNMP notifications.

snmp-server enable traps atm pvc extension

Enables extended ATM PVC SNMP notifications.

snmp-server enable traps bgp

Enables BGP server state change SNMP notifications.

snmp-server enable traps calltracker

Enables Call Tracker callSetup and callTerminate SNMP notifications.

snmp-server enable traps envmon

Enables environmental monitor SNMP notifications.

snmp-server enable traps frame-relay

Enables Frame Relay DLCI link status change SNMP notifications.

snmp-server enable traps ipsec

Enables IPsec SNMP notifications.

snmp-server enable traps isakmp

Enables IPsec ISAKMP SNMP notifications.

snmp-server enable traps isdn

Enables ISDN SNMP notifications.

snmp-server enable traps memory

Enables memory pool and buffer pool SNMP notifications.

snmp-server enable traps mpls ldp

Enables MPLS LDP SNMP notifications.

snmp-server enable traps mpls traffic-eng

Enables MPLS TE tunnel state-change SNMP notifications.

snmp-server enable traps mpls vpn

Enables MPLS VPN specific SNMP notifications.

snmp-server enable traps repeater

Enables RFC 1516 hub notifications.

snmp-server enable traps snmp

Enables RFC 1157 SNMP notifications.

snmp-server enable traps syslog

Enables the sending of system logging messages via SNMP.

snmp-server host

Specifies whether you want the SNMP notifications sent as traps or informs, the version of SNMP to use, the security level of the notifications (for SNMPv3), and the destination host (recipient) for the notifications.

snmp-server informs

Specifies inform request options.

snmp-server trap-source

Specifies the interface (and the corresponding IP address) from which an SNMP trap should originate.

snmp trap illegal-address

Issues an SNMP trap when a MAC address violation is detected on an Ethernet hub port of a Cisco 2505, Cisco 2507, or Cisco 2516 router.

vrrp shutdown

Disables a VRRP group.

snmp-server enable traps (MPLS)

To enable a label switch router (LSR) to send Simple Network Management Protocol (SNMP) notifications or informs to an SNMP host, use the snmp-server enable traps command in global configuration mode. To disable notifications or informs, use the no form of this command.

snmp-server enable traps [notification-type] [notification-option]

nosnmp-server enable traps [notification-type] [notification-option]

Syntax Description

notification-type

(Optional) Specifies the particular type of SNMP notification(s) to be enabled on the LSR. If a notification type is not specified, all SNMP notifications applicable to the LSR are enabled and sent to the SNMP host. Any one or all of the following keywords can be specified in any combination as the notification-type (family name) in the snmp-server enable traps command:

•snmp [authentication]—Sends RFC 1157 SNMP notifications. Using the authentication keyword produces the same effect as not using it. Both the snmp-server enable traps snmp and the snmp-server enable traps snmp authentication forms of this command globally enable the following SNMP notifications (or, if you are using the no form of the command, disables such notifications): authenticationFailure, linkUp, linkDown, and warmstart.

•syslog—Sends system error message (syslog) notifications. You can specify the level of messages to be sent using the logging history level command.

notification-type (continued)

•mpls ldp—Sends notifications about status changes in LDP sessions. Note that this keyword is specified as mpls ldp. This syntax, which the CLI interprets as a two-word construct, has been implemented in this manner to maintain consistency with other MPLS commands. Notification-option arguments (below) can be specified in combination with thiskeyword.

•mpls traffic-eng—Sends notifications about status changes in MPLS label distribution tunnels. This keyword is specified as mpls traffic-eng. This syntax, which the CLI interprets as a two-word construct, has been implemented in this manner to maintain consistency with other MPLS commands. Notification-option arguments (below) can be specified in combination with thiskeyword.

notification-option

(Optional) Defines the particular options associated with the specified notification-type that are to be enabled on the LSR.

•envmon [voltage | shutdown | supply | fan | temperature]

When you specify the envmon keyword, you can enable any one or all of the following environmental notifications in any combination: voltage, shutdown, supply, fan, or temperature. If you do not specify an argument with the envmon keyword, all types of system environmental notifications are enabled on the LSR.

•isdn [call-information | isdn u-interface]

When you specify the isdnkeyword, you can use either the call-information argument (to enable an SNMP ISDN call information option for the ISDN MIB subsystem) or the isdn u-interface argument (to enable an SNMP ISDN U interface option for the ISDN U Interfaces MIB subsystem), or both. If you do not specify an argument with the isdn keyword, both types of isdn notifications are enabled on the LSR.

•repeater [health | reset]

When you specify the repeater keyword, you can use either the health argument or the reset argument, or both (to enable the IETF Repeater Hub MIB [RFC 1516] notification). If you do not specify an argument with the repeater keyword, both types of notifications are enabled on the LSR.

•mpls ldp [session-up | session-down | pv-limit | threshold]

When you specify the mpls ldp keyword, you can use any one or all of the following arguments in any combination to indicate status changes in LDP sessions: session-up, session-down, pv-limit,or threshold.If you do not specify an argument with the mpls ldp keyword, all four types of LDP session notifications are enabled on the LSR.

•mpls traffic-eng [up | down | reroute]

When you specify the mpls traffic-eng keyword, you can use any one or all of the following arguments in any combination to enable the sending of notifications regarding status changes in MPLS label distribution tunnels: up, down, or reroute. If you do not specify an argument with the mpls traffic-eng keyword, all three types of tunnel notifications are enabled on the LSR.

Defaults

If you issue this command on an LSR without specifying any notification-type keywords, the default behavior of the LSR is to enable all notification types controlled by the command (some notification types cannot be controlled by means of this command).

Command Modes

Global configuration

Command History

Release

Modification

11.1

This command was introduced.

11.3

The snmp-server enable traps snmp authentication form of this command was introduced to replace the snmp-server trap-authentication command.

12.0(17)ST

The mpls traffic-eng keyword was added to define a class or family of specific SNMP notifications for use with the notification-type and notification-option parameters of the snmp-server enable traps command.

12.0(21)ST

The mpls ldp keyword was added to define a class or family of specific SNMP notifications for use with the notification-type and notification-option parameters of the snmp-server enable traps command.

12.0(22)S

This command was integrated into Cisco IOS Release 12.0(22)S.

12.2(18)S

This command was integrated into Cisco IOS Release 12.2(18)S.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.4(11)T

This command was integrated into Cisco IOS Release 12.4(11)T.

12.2(31)SB2

This command was integrated into Cisco IOS Release 12.2(31)SB2.

12.2(33)SXH

This command was integrated into Cisco IOS Release 12.2(33)SXH.

Usage Guidelines

To configure an LSR to send SNMP LDP notifications, you must issue at least one snmp-server enable traps command on the router.

To configure an LSR to send either notifications (traps) or informs to a designated network management station (NMS), you must issue the snmp-server host command on that device, usingthe keyword (traps or informs) that suits your purposes.

If you issue the snmp-server enable traps command without keywords, all SNMP notification types are enabled on the LSR. If you issue this command with specific keywords, only the notification types associated with those particular keywords are enabled on the LSR.

The snmp-server enable traps command is used in conjunction with the snmp-server host command. You use the latter command to specify the NMS host (or hosts) targeted as the recipient(s) of the SNMP notifications generated by SNMP-enabled LSRs in the network. To enable an LSR to send such notifications, you must issue at least one snmp-server host command on the LSR.

Examples

In the following example, the router is enabled to send all notifications to the host specified as myhost.cisco.com. The community string is defined as public.

Router(config)# snmp-server enable traps

Router(config)# snmp-server host myhost.cisco.com public

In the following example, the router is enabled to send Frame Relay and environmental monitor notifications to the host specified as myhost.cisco.com. Thecommunity string is defined as public:

Router(config)# snmp-server enable traps frame-relay

Router(config)# snmp-server enable traps envmon temperature

Router(config)# snmp-server host myhost.cisco.com public

In the following example, notifications are not sent to any host. BGP notifications are enabled for all hosts, but the only notifications enabled to be sent to a host are ISDN notifications (which are not enabled in this example).

Router(config)# snmp-server enable traps bgp

Router(config)# snmp-server host host1 public isdn

In the following example, the router is enabled to send all inform requests to the host specified as myhost.cisco.com. The community string is defined as public.

Related Commands

Specifies the intended recipient of an SNMP notification (that is, the designated NMS workstation in the network).

snmp-server enable traps aaa_server

To enable authentication, authorization, and accounting (AAA) server state-change Simple Network Management Protocol (SNMP) notifications, use the snmp-server enable traps aaa_server command in global configuration mode. To disable AAA server state-change SNMP notifications, use the no form of this command.

snmp-server enable traps aaa_server

no snmp-server enable traps aaa_server

Syntax Description

This command has no arguments or keywords.

Command Default

SNMP notifications are disabled by default.

Command Modes

Global configuration

Command History

Release

Modification

12.1(3)T

This command was introduced for the Cisco AS5300 and Cisco AS5800.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2SX

This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Usage Guidelines

SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests.

This command controls (enables or disables) AAA Server state change (casServerStateChange) notifications. ServerStateChange notifications, when enabled, will be sent when the server moves from an "up" to "dead" state or when a server moves from a "dead" to "up" state.

The Cisco AAA Server State is defined by the casState object in the Cisco AAA Server MIB. The possible values are as follows:

•up(1)—Server is responding to requests.

• dead(2)—Server failed to respond to requests.

A server is marked "dead" if it does not respond after maximum retransmissions. A server is marked "up" again either after a waiting period or if some response is received from it. The initial value of casState is "up(1)" at system startup. This will only transition to "dead(2)" if an attempt to communicate fails.

For a complete description of this notification and additional MIB functions, see the CISCO-AAA-SERVER-MIB.my file, available on Cisco.com at http://www.cisco.com/public/mibs/v2/.

The snmp-server enable traps aaa_sever command is used in conjunction with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP notifications. To send SNMP notifications, you must configure at least one snmp-server host command.

Examples

The following example enables the router to send AAA server up/down informs to the host at the address myhost.cisco.com using the community string defined as public:

Syntax Description

(Optional) Specifies a minimum period between successive traps. Generation of PVC traps is dampened by the notification interval to prevent trap storms. No traps are sent until the interval lapses.

The seconds argument is an integer in the range from 1 to 3600. The default is 30.

fail-intervalseconds

(Optional) Specifies a minimum period for storing the failed time stamp.

The seconds argument is an integer in the range from 0 to 3600. The default is 0.

Command Default

SNMP notifications are disabled.

Command Modes

Global configuration

Command History

Release

Modification

12.0(1)T

This command was introduced for the platforms that support ATM PVC Management.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2SX

This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Cisco IOS XE Release 2.3

This command was integrated into Cisco IOS XE Software Release 2.3 and implemented on the Cisco ASR 1000 series routers.

Usage Guidelines

SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests for the specified notification types. ATM notifications are defined in the CISCO-IETF-ATM2-PVCTRAP-MIB.my file, available from the Cisco FTP site at ftp://ftp.cisco.com/pub/mibs/v2/.

ATM PVC failure notifications are sent when a PVC on an ATM interface fails or leaves the UP operational state. Only one trap is generated per hardware interface, within the specified interval defined by the interval keyword (stored as the atmIntfPvcNotificationInterval in the MIB). If other PVCs on the same interface go DOWN during this interval, traps are generated and held until the fail interval has elapsed. When the interval has elapsed, the traps are sent if the PVCs are still DOWN.

No notifications are generated when a PVC returns to the UP state after having been in the DOWN state. If you need to detect the recovery of PVCs, you must use the SNMP management application to regularly poll your router.

The snmp-server enable traps atm pvc command is used in conjunction with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP notifications. To send notifications, you must configure at least one snmp-server host command.

Examples

The following example shows the enabling of ATM PVC traps on a router, so that if PVC 0/1 goes down, host 172.16.61.90 will receive the notifications:

!For ATM PVC Trap Support to work on your router, you must first have SNMP support and

Command Default

SNMP notifications are disabled. The interval between successive traps is 30 seconds.

Command Modes

Global configuration

Command History

Release

Modification

12.2(4)T

This command was introduced for those platforms that support ATM PVC management.

12.2(13)T

This command was modified to configure SNMP notification support for ATM OAM F5 CC and ATM OAM F5 AIS/RDI failures.

12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB.

Cisco IOS XE Release 2.3

This command was integrated into Cisco IOS XE Software Release 2.3 and implemented on the Cisco ASR 1000 series routers.

Usage Guidelines

For PVCs that are not part of a range, extended ATM PVC traps include virtual path identifier/virtual channel identifier (VPI/ VCI) information, the number of state transitions a PVC goes through in an interval, and the timestamp for the start and end of the transitions. For PVCs that are part of a range, extended ATM PVC traps include the first and last VPI/VCI of the range and the timestamp for the first failure and the last failure within the same range.

Extended ATM PVC and ATM OAM F5 CC traps cannot be used at the same time as the legacy ATM PVC trap. The legacy ATM PVC trap must be disabled by using the no snmp-server enable traps atm pvc command before extended ATM PVC traps can be configured.

The extended ATM PVC failure trap (which is enabled by the snmp-server enable traps atm pvc extension down command) is the same trap as the legacy ATM PVC failure trap (which is enabled by the snmp-server enable traps atm pvc command), but with the following differences:

SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests for the specified notification types.

The extended ATM PVC notifications for MIB version 1 are defined in the CISCO-IETF-ATM2-PVCTRAP-MIB.my file.The extended ATM PVC notifications for MIB version 2 are defined in the CISCO-ATM-PVCTRAP-EXTN-MIB.my file. Both of these MIB files are available from the Cisco FTP site at ftp://ftp.cisco.com/pub/mibs/v2/.

ATM PVC traps are generated at the end of the notification interval. It is possible to generate all three types of ATM PVC traps (the ATM PVC failure trap, ATM PVC up trap, and ATM PVC OAM failure trap) at the end of the same notification interval; however, only one type of trap will be generated for each PVC.

The snmp-server enable traps atm pvc extension command is used in conjunction with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP notifications. In order to send notifications, you must configure at least one snmp-server host command.

When the ATM OAM F5 loopback, AIS/RDI, or CC failure trap is enabled, the PVC remains in the UP state when an OAM loopback, AIS/RDI, or CC failure is detected, so that the flow of data will still be possible. If one of these traps is not enabled, the PVC will be placed in the DOWN state when an OAM loopback, AIS/RDI, or CC failure is detected.

Examples

Extended ATM PVC Notifications Example

The following example shows all three of the extended ATM PVC traps enabled on a router. If PVC 0/1 leaves the UP state, leaves the DOWN state, or has an OAM loopback failure, host 172.16.61.90 will receive the SNMP notifications:

The following example shows output for extended ATM PVC failure trap for PVCs 1/100, 1/102, and 1/103. Note that only one trap is generated for all the PVCs associated with the same interface or subinterface (in contrast to the legacy ATM PVC failure trap, which generates a separate trap for each PVC). The VPI/VCI information and timing information are located in the objects associated with the trap.

00:23:56:SNMP:Queuing packet to 1.1.1.1

00:23:56:SNMP:V2 Trap, reqid 2, errstat 0, erridx 0

sysUpTime.0 = 143636

snmpTrapOID.0 = atmIntfPvcFailuresTrap

ifEntry.1.19 = 19

atmIntfPvcFailures.2 = 7

atmIntfCurrentlyFailingPVcls.2 = 3

atmPVclLowerRangeValue.19.1.2 = 102

atmPVclHigherRangeValue.19.1.2 = 103

atmPVclRangeStatusChangeStart.19.1.2 = 140643

atmPVclRangeStatusChangeEnd.19.1.2 = 140698

atmPVclStatusTransition.19.1.100 = 1

atmPVclStatusChangeStart.19.1.100 = 140636

atmPVclStatusChangeEnd.19.1.100 = 140636

00:23:56:SNMP:Packet sent via UDP to 1.1.1.1

Extended ATM PVC Up Trap Output: Example

The following example shows output for the extended ATM PVC up trap for PVCs 1/100, 1/102, and 1/103:

00:31:29:SNMP:Queuing packet to 1.1.1.1

00:31:29:SNMP:V2 Trap, reqid 2, errstat 0, erridx 0

sysUpTime.0 = 188990

snmpTrapOID.0 = atmIntfPvcUpTrap

ifEntry.1.19 = 19

atmIntfCurrentlyDownToUpPVcls.2 = 3

atmPVclLowerRangeValue.19.1.2 = 102

atmPVclHigherRangeValue.19.1.2 = 103

atmPVclRangeStatusChangeStart.19.1.2 = 186005

atmPVclRangeStatusChangeEnd.19.1.2 = 186053

atmPVclStatusTransition.19.1.100 = 1

atmPVclStatusChangeStart.19.1.100 = 185990

atmPVclStatusChangeEnd.19.1.100 = 185990

00:31:30:SNMP:Packet sent via UDP to 1.1.1.1

ATM OAM F5 CC Notifications Example

In the following example, the ATM OAM CC notifications and an extended ATM PVC notification are enabled. If connectivity failures are detected on PVC 0/1, host 172.16.61.90 will receive the SNMP notifications:

Syntax Description

Specifies the MIB that supports the extended ATM permanent virtual circuit (PVC) SNMP notifications. This is the default.

2

Specifies the MIB that supports ATM OAM F5 CC and ATM OAM F5 AIS/RDI SNMP notifications, in addition to the notifications supported by MIB version 1.

Command Default

SNMP notifications are disabled.

Command Modes

Global configuration

Command History

Release

Modification

12.2(15)T

This command was introduced.

12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB.

Usage Guidelines

MIB version 1 specifies the MIB that supports legacy extended ATM PVC traps and is defined in the file CISCO-IETF-ATM2-PVCTRAP-MIB-EXTN.my. MIB version 1 is implemented by default. Use the snmp-server enable traps atm pvc extension mibversion 1 command or the nosnmp-server enable traps atmpvcextension mibversion 2 command to reenable this MIB if it was previously disabled with the snmp-server enable traps atm pvc extension mibversion 2 command.

Use the snmp-server enable traps atmpvcextension mibversion 2 command to specify the MIB that supports ATM OAM F5 CC and ATM OAM AID/RDI failure notifications. This MIB is defined in the file CISCO-ATM-PVCTRAP-EXTN-MIB.my.

To enable the SNMP notifications that support ATM OAM F5 continuity checking, use the snmp-server enable traps atmpvcextension command in global configuration mode. These SNMP notifications are defined in the file CISCO-ATM-PVCTRAP-EXTN-MIB.my, available from the Cisco FTP site at ftp://ftp.cisco.com/pub/mibs/v2/.

OAM management and support for OAM F5 continuity checking must be enabled on the PVC by using the oam-pvc manage cc command before you can use the ATM OAM continuity check SNMP notifications.

Examples

In the following example, the MIB that supports the SNMP notifications for ATM OAM continuity checking is implemented, and the ATM OAM continuity checking notifications are enabled. Support for end-to-end OAM F5 continuity checking is enabled on PVC 0/1:

snmp-server enable traps atm subif

To enable the sending of ATM subinterface Simple Network Management Protocol (SNMP) notifications, use the snmp-server enable traps atm subif command in global configuration mode. To disable ATM subinterface-specific SNMP notifications, use the no form of this command.

Syntax Description

(Optional) Specifies the maximum number of traps that will be sent in the specified interval.

number-of-traps

(Optional) Integer in the range from 1 to 1000. The default is 10.

Command Default

ATM subinterface SNMP notifications are disabled.

Command Modes

Global configuration

Command History

Release

Modification

12.2(13)T

This command was introduced.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2(33)SXH

This command was integrated into Cisco IOS Release 12.2(33)SXH.

Usage Guidelines

The snmp-server trap link ietf command must be configured in order to use the snmp-server enable traps atm subif command. The snmp-server trap link ietf command is used to configure a router to use the RFC 2233 IETF standards-based implementation of linkUp/linkDown traps. The default Cisco object definitions do not generate linkUp/linkDown traps correctly for subinterfaces.

SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests for the specified notification types.

ATM subinterface traps are sent to the network management system (NMS) when a subinterface enters or leaves the down state.

To prevent trap storms, the countand interval keywords can be configured to limit the number of traps and the frequency at which they are sent. Configuring an interval of 0 seconds causes all ATM subinterface traps to be sent.

You can disable ATM subinterface traps by using the nosnmp-server enable traps atm subif command. When traps are disabled, you can use the SNMP management application to poll your router for subinterface status information.

The snmp-server enable traps atm subif command is used in conjunction with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP notifications. To send notifications, you must configure at least one snmp-server host command.

By default (when the snmp-server enable traps atm subif command is not configured), the ifLinkUpDownTrapEnable object returns disabled(2), and no traps are generated for the subinterfaces.

When the snmp-server enable traps atm subif command is configured, the ifLinkUpDownTrapEnable object is set to enabled(1) for all the ATM aal5 layers of the subinterfaces. To verify that the traps are generated (with the debug snmp packets command enabled), enter the shutdown or no shutdown commands to display the traps.

Configuring the snmp trap link-status command on a subinterface generates the traps and sets the ifLinkUpDownTrapEnable object to enabled(1). If the snmp trap link-status command is not configured on the subinterface, then the ifLinkUpDownTrapEnable object is set to disabled(2) for that subinterface, and the shutdown or no shutdown commands no longer generate traps for that subinterface.

Examples

The following example shows how to enable ATM subinterface traps on a router. If an ATM subinterface on this router changes state, host 172.16.61.90 will receive the notifications:

!For ATM subinterface trap to work on your router, you must first have SNMP support and

snmp-server enable traps bfd

To enable the sending of Bidirectional Forwarding Detection (BFD) Simple Network Management Protocol (SNMP) notifications, use the snmp-server enable traps bfd command in global configuration mode. To disable the sending of BFD notifications, use the no form of this command.

Syntax Description

Command Default

The sending of SNMP notifications is disabled. If you do not specify an optional keyword, all types of BFD notifications are enabled.

Command Modes

Global configuration (config)

Command History

Release

Modification

12.2(33)SRE

This command was introduced.

Usage Guidelines

Thesnmp-server enable traps bfd command is used with the snmp-server host command. Use thesnmp-server host command to specify which host or hosts receive SNMP notifications. To send SNMP notifications, you must configure at least one snmp-server host command.

If the session-down keyword is used with the snmp-server enable traps bfd command, a session-down message is generated when a BFD session between the router and its adjacent peer is terminated.

If the session-up keyword is used with the snmp-server enable traps bfd command, a message is generated when the router establishes a BFD session.

Examples

In the following example, BFD-specific informs are enabled and will be sent to the host myhost.cisco.com through use of community string defined as public:

Related Commands

Command

Description

snmp-server host

Specifies whether you want the SNMP notifications sent as traps or informs, the version of SNMP to use, the security level of the notifications (for SNMPv3), and the recipient (host) of the notifications.

snmp-server enable traps bgp

To enable Border Gateway Protocol (BGP) support for Simple Network Management Protocol (SNMP) operations on a router, use the snmp-server enable traps bgp command in global configuration mode. To disable BGP support for SNMP operations, use the no form of this command.

This command was implemented on the following platforms: Cisco 7301, Cisco 7200 series, and Cisco 10000 series.

Usage Guidelines

SNMP notifications can be sent as traps or inform requests and this command enables both notification types. If this command is entered with no keywords specified, support for all configurable options is enabled.

Using this command you can enable or disable BGP server state change notifications for the BGP4-MIB (enterprise 1.3.6.1.2.1.15.7). The notifications types are:

•bgpEstablished

•bgpBackwardsTransition

For a complete description of BGP notifications and additional MIB functions, see the BGP4-MIB.my file, available through the Cisco FTP site at ftp://ftp.cisco.com/pub/mibs/v2/.

Note You may notice incorrect BGP trap object ID (OID) output when using the SNMP version 1 BGP4-MIB that is available for download at ftp://ftp.cisco.com/pub/mibs/v1/BGP4-MIB-V1SMI.my. When a router sends out BGP traps (notifications) about state changes on an SNMP version 1 monitored BGP peer, the enterprise OID is incorrectly displayed as .1.3.6.1.2.1.15 (bgp) instead of .1.3.6.1.2.1.15.7 (bgpTraps). This problem occurs because the BGP4-MIB does not follow RFC 1908 rules for version 1 and version 2 trap compliance. The problem is not due to an error in Cisco IOS software.This MIB is controlled by IANA under the guidance of the IETF, and work is currently in progress by the IETF to replace this MIB with a new version that represents the current state of the BGP protocol. In the meantime, we recommend that you use the SNMP version 2 BGP4-MIB or the CISCO-BGP4-MIB to avoid an incorrect trap OID.

The snmp-server enable traps bgp command also can be enabled to control BGP server state change notifications for the CISCO-BGP4-MIB. This MIB contains support the following SNMP operations:

•Notification for all BGP FSM transition changes.

•Notifications to query for total number of routes received by a BGP peer.

•Notifications for the maximum prefix-limit threshold on a BGP peer.

•GET operations for VPNv4 unicast routes.

For a complete description of BGP notifications and additional MIB functions, see the CISCO-BGP4-MIB.my file, available through the Cisco FTP site at ftp://ftp.cisco.com/pub/mibs/v2/.

The snmp-server enable traps bgp command is used in conjunction with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP notifications. To send SNMP notifications, you must configure at least one snmp-server host command.

Examples

The following example shows how to enable the router to send BGP state change informs to the host at the address myhost.cisco.com using the community string defined as public:

Related Commands

snmp-server enable traps bulkstat

To enable the sending of Simple Network Management Protocol (SNMP) bulk statistics collection and transfer SNMP notifications, use the snmp-server enable traps bulkstat command in global configuration mode. To disable bulk statistics SNMP notifications, use the no form of this command.

snmp-server enable traps bulkstat [collection] [transfer]

no snmp-server enable traps bulkstat [collection] [transfer]

Syntax Description

collection

(Optional) Controls bulk statistics collection notifications, which are sent when data collection cannot be carried out successfully. (Defined as cdcVFileCollectionError in the CISCO-DATA-COLLECTION-MIB.)

transfer

(Optional) Controls bulk statistics transfer notifications, which are sent when a transfer attempt is successful or when a transfer attempt fails. (Defined as cdcFileXferComplete in the CISCO-DATA-COLLECTION-MIB. The varbind cdcFilXferStatus object in the trap indicates if the transfer is successful or not.)

Command Default

SNMP notifications are disabled.

Command Modes

Global configuration (config)

Command History

Release

Modification

12.0(24)S

This command was introduced.

12.3(2)T

This command was integrated into Cisco IOS Release 12.3(2)T.

12.2(25)S

This command was integrated into Cisco IOS Release 12.2(25)S.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2(33)SXH

This command was integrated into Cisco IOS Release 12.2(33)SXH.

12.2(33)SB

This command was integrated into Cisco IOS Release 12.2(33)SB.

Cisco IOS XE Release 2.1

This command was integrated into Cisco IOS Release XE 2.1.

Usage Guidelines

SNMP notifications can be sent as traps or inform requests. The snmp-server enable traps bulkstat command enables both traps and inform requests for the specified notification types. Use this command with the snmp-server host[bulkstat] command.

The optional collection keyword controls bulk statistics collection notifications that are sent when data collection cannot be carried out successfully. One possible reason for this condition is insufficient memory on the device.

If the optional keywords are not used, all bulk statistics notification types are enabled (or disabled, if the no form of the command is used).

Examples

In the following example, bulk statistics collection and transfer notifications are configured to be sent to the host myhost.cisco.com using the community string public:

snmp-server enable traps c6kxbar

To enable CISCO-CAT6K-CROSSBAR-MIB Simple Network Management Protocol (SNMP) notifications (traps and informs), use the snmp-server enable traps c6kxbar command in global configuration mode. To disable cc6kxbar notifications, use the no form of this command.

Added tm-channel for Supervisor Engine 720 only and tm-swbus keywords.

Usage Guidelines

The flowctrl-bus keyword is supported on the Supervisor Engine 32 only.

The tm-channel keyword is not supported on the Supervisor Engine 32.

Examples

This example shows how to enable SNMP cc6kxbarFlowCtrlBusThrExcdNotif notifications:

Router(config)# snmp-server enable traps c6kxbar flowctrl-bus

Router(config)#

This example shows how to enable SNMP cc6kxbarIntBusCRCErrExcdNotif notifications:

Router(config)# snmp-server enable traps c6kxbar intbus-crcexcd

Router(config)#

This example shows how to enable SNMP cc6kxbarIntBusCRCErrRcvrdNotif notifications:

Router(config)# snmp-server enable traps c6kxbar intbus-crcvrd

Router(config)#

This example shows how to enable SNMP cc6kxbarSwBusStatusChangeNotif notifications:

Router(config)# snmp-server enable traps c6kxbar swbus

Router(config)#

This example shows how to enable SNMP cc6kxbarTMChUtilAboveNotif and cc6kxbarTMChUtilBelowNotif notifications:

Router(config)# snmp-server enable traps c6kxbar tm-channel

Router(config)#

This example shows how to enable SNMP cc6kxbarTMSwBusUtilAboveNotif and cc6kxbarTMSwBusUtilBelowNotif notifications:

Router(config)# snmp-server enable traps c6kxbar tm-swbus

Router(config)#

Related Commands

Command

Description

test snmp trap c6kxbar

Tests the SNMP c6kxbar notification traps.

snmp-server enable traps calltracker

To enable Call Tracker CallSetup and Call Terminate Simple Network Management Protocol (SNMP) notifications, use the snmp-server enable traps calltracker command in global configuration mode. To disable Call Tracker SNMP notifications, use the no form of this command.

snmp-server enable traps calltracker

no snmp-server enable traps calltracker

Syntax Description

This command has no arguments or keywords.

Command Default

SNMP notifications are disabled.

Command Modes

Global configuration

Command History

Release

Modification

12.1(3)T

This command was introduced for the Cisco AS5300 and Cisco AS580 access servers.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2SX

This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Usage Guidelines

SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests.

This command controls (enables or disables) Call Tracker CallSetup and CallTerminate notifications. CallSetup notifications are generated at the start of each call, when an entry is created in the active table (cctActiveTable), and CallTerminate notifications are generated at the end of each call, when an entry is created in the history table (cctHistoryTable).

For a complete description of these notifications and additional MIB functions, refer to the CISCO-CALL-TRACKER-MIB.my file, available on Cisco.com at http://www.cisco.com/public/mibs/v2/.

The snmp-server enable traps calltracker command is used in conjunction with the snmp-server host global configurationcommand. Use the snmp-server host command to specify which host or hosts receive SNMP notifications. To send SNMP notifications, you must configure at least one snmp-server host command.

Examples

The following example enables the router to send call-start and call-stop informs to the host at the address myhost.cisco.com using the community string defined as public:

Related Commands

Enables call record SYSLOG generation for the purpose of debugging, monitoring, or externally saving detailed call record information.

calltracker enable

Enables the Call Tracker feature on an access server.

isdn snmp busyout b-channel

Enables PRI B channels to be busied out via SNMP.

show call calltracker

Displays Call Tracker activity and configuration information such as the number of active calls and the history table attributes.

show modem calltracker

Displays all of the information stored within the Call Tracker Active or History Database for the latest call assigned to specified modem.

snmp-server host

Specifies the recipient of an SNMP notification operation.

snmp-server trap-source

Specifies the interface that an SNMP trap should originate from.

snmp-server enable traps cnpd

To enable Cisco Network-Based Application Recognition (NBAR) Protocol Discovery (CNPD) MIB notifications, use the snmp-server enable traps cnpd command in global configuration mode. To disable CNPD MIB notifications, use the no form of this command.

snmp-server enable traps cnpd

no snmp-server enable traps cnpd

Syntax Description

This command has no arguments or keywords.

Command Default

CNPD MIB notifications are disabled.

Command Modes

Global configuration (config)

Command History

Release

Modification

12.2(15)T

This command was introduced.

Usage Guidelines

CNPD notifications are used with the CNPD MIB to provide information related to protocol discovery. The snmp-server enable traps cnpd command enables these notifications. It also enables SNMP notifications as either traps or inform requests.

The snmp-server enable traps cnpd command is used in conjunction with the snmp-server host command, which specifies the host or hosts that will receive SNMP notifications. To send SNMP notifications, you must configure at least one snmp-server host command. The default action is to send notifications to the default port, but you can specify a port by configuring the udp-port option of the snmp-server host command.

Examples

The following example shows how to enable CNPD notifications:

Router(config)# snmp-server enable traps cnpd

Related Commands

Command

Description

snmp-server host

Specifies the recipient of SNMP notifications.

snmp-server enable traps cpu

To enable a device to send CPU thresholding violation notifications, use the snmp-server enable traps cpu command in global configuration mode. To stop a device from sending CPU thresholding notifications, use the no form of this command.

snmp-server enable traps cputhreshold

no snmp-server enable traps cpu

Syntax Description

threshold

Enables notifications of CPU threshold violations.

Command Default

SNMP notifications are disabled.

Command Modes

Global configuration

Command History

Release

Modification

12.0(26)S

This command was introduced.

12.3(4)T

This command was integrated into Cisco IOS Release 12.3(4)T.

12.2(25)S

This command was integrated into Cisco IOS Release 12.2(25)S.

Usage Guidelines

SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests and controls CPU thresholding notifications, as defined in the Process MIB (CISCO-PROCESS-MIB).

For a complete description of these notification types, and for information about the other MIB functions, see the CISCO-PROCESS-MIB.my file available from Cisco.com at http://www.cisco.com/go/mibs.

The snmp-server enable traps cpu command is used in conjunction with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP notifications. To send SNMP notifications, you must configure at least one snmp-server host command.

Examples

The following example shows how to enable the router to send CPU threshold related informs to the host at the address myhost.cisco.com using the community string defined as public:

Related Commands

Specifies the destination NMS and transfer parameters for SNMP notifications.

snmp-server trap-source

Specifies the interface from which an SNMP trap should originate.

snmp-server enable traps dhcp

To enable DHCP Simple Network Management Protocol (SNMP) trap notifications, use the snmp-server enable traps dhcp command in global configuration mode. To disable DHCP trap notifications, use the no form of this command.

Syntax Description

(Optional) Sends notification that a per interface lease limit is exceeded.

pool

(Optional) Sends notification when address utilization for an address pool has risen above or fallen below a configurable threshold.

subnet

(Optional) Sends notification when address utilization for a subnet has risen above or fallen below a configurable threshold.

time

(Optional) Sends notification that the DHCP server has started or stopped.

Command Default

DHCP trap notifications are not sent.

Command Modes

Global configuration (config)

Command History

Release

Modification

12.2(33)SRC

This command was introduced.

Usage Guidelines

If you do not specify any of the optional keywords, all DHCP trap notifications are enabled.

Examples

The following example shows how to send SNMP trap notifications to the SNMP manager when the secondary subnet utilization falls below or exceeds the configured threshold:

Router(config)# ip dhcp pool pool2

Router(dhcp-config)# utilization mark high 80 log

Router(dhcp-config)# utilization mark low 70 log

Router(dhcp-config)# network 192.0.2.0 255.255.255.0

Router(dhcp-config)# network 192.0.4.0 255.255.255.252 secondary

Router(config-dhcp-subnet-secondary)# override utilization high 40

Router(config-dhcp-subnet-secondary)# override utilization low 30

!

Router(config)# snmp-server enable traps dhcp subnet

In the following example, all DHCP trap notifications will be sent to the SNMP manager in response to DHCP server events:

Router(config)# snmp-server enable traps dhcp

snmp-server enable traps dhcp-snooping bindings

To enable DHCP-snooping bindings Simple Network Management Protocol (SNMP) notifications (traps and informs), use the snmp-server enable traps dhcp-snooping bindings command in global configuration mode. To disable DHCP-snooping bindings notifications, use the no form of this command.

Usage Guidelines

Examples

This example shows how to enable DHCP-snooping bindings SNMP notifications:

Router(config)# snmp-server enable traps dhcp-snooping bindings

Router(config)#

snmp-server enable traps director

Note Effective with Cisco IOS Release 12.4(24)T, the snmp-server enable traps director command is not available in Cisco IOS software.

To enable DistributedDirector Simple Network Management Protocol (SNMP) notifications, use the snmp-server enable traps director command in global configuration mode. To disable DistributedDirector SNMP notifications, use the no form of this command.

snmp-server enable traps director [server-up | server-down]

no snmp-server enable traps director [server-up | server-down]

Syntax Description

server-up

(Optional) Enables the DistributedDirector notification that the server has changed to the "up" state.

server-down

(Optional) Enables the DistributedDirector notification that the server has changed to the "down" state.

Command Default

SNMP notifications are disabled.

Command Modes

Global configuration

Command History

Release

Modification

12.2(8)T

This command was introduced.

12.4(24)T

This command was removed.

Usage Guidelines

SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests.

This command controls (enables or disables) DistributedDirector status notifications for systems. If none of the optional keywords is specified, all available environmental notifications are enabled.

Examples

In the following example, both ciscoDistDirEventServerUp and ciscoDistDirEventServerDown notifications are enabled:

Router(config)#snmp-server enable traps director

Router# show running-config

ip host myhost 172.20.2.10 172.20.2.20 172.20.2.30

.

.

.

ip director host myhost

ip dns primary myhost soa myhost myhost@com

ip director host myhost priority boomerang 1

no ip director drp synchronized

snmp-server enable traps director server-up server-down

Related Commands

Command

Description

snmp-server enable traps

Enables the router to send SNMP traps.

snmp-server host

Specifies the recipient of an SNMP notification.

snmp-server informs

Specifies inform request options.

snmp-server trap-source

Specifies the interface (and hence the corresponding IP address) from which an SNMP trap should originate.

snmp-server trap-timeout

Defines how often to try resending trap messages on the retransmission queue.

snmp trap link-status

Enables SNMP trap notifications to be generated when a specific port is brought up or down.

snmp-server enable traps dlsw

To enable the sending of Data Link Switch (DLSw) circuit and peer connection Simple Network Management Protocol (SNMP) notifications (traps and informs), use the snmp-server enable traps dlsw command in global configuration mode. To disable DLSw notifications, use the no form of this command.

snmp-server enable traps dlsw [circuit | tconn]

no snmp-server enable traps dlsw [circuit | tconn]

Syntax Description

circuit

(Optional) Enables DLSw circuit traps:

•(5) ciscoDlswTrapCircuitUp

•(6) ciscoDlswTrapCircuitDown

tconn

(Optional) Enables DLSw peer transport connection traps:

•(1) ciscoDlswTrapTConnPartnerReject

•(2) ciscoDlswTrapTConnProtViolation

•(3) ciscoDlswTrapTConnUp

•(4) ciscoDlswTrapTConnDown

Command Default

SNMP notifications are disabled.

If the optional keywords are not used, all DLSw notification types are enabled (or disabled, if the no form of the command is used).

Command Modes

Global configuration

Command History

Release

Modification

12.1

This command was introduced.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2SX

This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Usage Guidelines

SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests. Use this command in conjunction with the snmp-server host command.

Related Commands

snmp-server enable traps eigrp

To enable support for Enhanced Interior Gateway Routing Protocol (EIGRP) notifications on a Cisco router, use the snmp-server enable traps eigrp command in global configuration mode. To disable EIGRP notification support, use the no form of this command.

snmp-server enable traps eigrp

no snmp-server enable traps eigrp

Syntax Description

This command has no keywords or arguments.

Command Default

EIGRP notification support is not enabled.

Command Modes

Global configuration (config)

Command History

Release

Modification

12.3(14)T

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

15.0(1)M

This command was integrated into Cisco IOS Release 15.0(1)M.

12.2(33)XNE

This command was integrated into Cisco IOS Release 12.2(33)XNE.

IOS XE Release 2.6

This command was integrated into Cisco IOS XE Release 2.6.

12.2(33)SXI4

This command was integrated into Cisco IOS Release 12.2(33)SXI4.

Usage Guidelines

The snmp-server enable traps eigrp command is used to enable notifications (traps) for stuck-in-active (SIA) and neighbor authentication failure events. Support for trap events is not activated until a trap destination is configured with the snmp-server hostcommand and until a community string is defined with the snmp-server community command.

Examples

In the following example, an SNMP server host is specified, a community string is configured, and support for EIGRP notifications is enabled:

Related Commands

Configures a community access string to permit SNMP access to the local router by the remote SNMP software client.

snmp-server host

Specifies the destination host or address for SNMP notifications.

snmp-server enable traps envmon

To enable environmental monitor Simple Network Management Protocol (SNMP) notifications, use the snmp-server enable traps envmon command in global configuration mode. To disable environmental monitor SNMP notifications, use the no form of this command.

Command Default

Command Modes

Command History

Support for this command was introduced for the Cisco AS5300 access server.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2SX

This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Usage Guidelines

SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests.

This command enables or disables Environmental Monitor (EnvMon) status notifications for supported systems. Cisco enterprise EnvMon notifications are triggered when an environmental threshold is exceeded. If none of the optional keywords are specified, all available environmental notifications are enabled.

When the shutdown keyword is used, a ciscoEnvMonShutdownNotification (enterprise MIB OID 1.3.6.1.4.1.9.9.13.3.1) is sent if the environmental monitor detects a testpoint reaching a critical state and is about to initiate a shutdown.

When the voltage keyword is used, a ciscoEnvMonVoltageNotification (enterprise MIB OID 1.3.6.1.4.1.9.9.13.3.2) is sent if the voltage measured at a given testpoint is outside the normal range for the testpoint (that is, at the warning, critical, or shutdown stage). For access servers, this notification is defined as the caemVoltageNotification (enterprise MIB OID 1.3.6.1.4.1.9.9.61.2.2).

When the temperature keyword is used, a ciscoEnvMonTemperatureNotification (enterprise MIB OID 1.3.6.1.4.1.9.9.13.3.3) is sent if the temperature measured at a given testpoint is outside the normal range for the testpoint (i.e. is at the warning, critical, or shutdown stage). For access servers, this notification is defined as the caemTemperatureNotification (enterprise MIB OID 1.3.6.1.4.1.9.9.61.2.1).

When the fan keyword is used, a ciscoEnvMonFanNotification (enterprise MIB OID 1.3.6.1.4.1.9.9.13.3.4) is sent if any one of the fans in a fan array fails.

When the supply keyword is used, a ciscoEnvMonRedundantSupplyNotification (enterprise MIB OID 1.3.6.1.4.1.9.9.13.2.5) is sent if a redundant power supply fails.

For a complete description of these notifications and additional MIB functions, see the CISCO-ENVMON-MIB.my and CISCO-ACCESS-ENVMON-MIB.my files, available on Cisco.com at http://www.cisco.com/public/mibs/v2/.

Status of the Environmental Monitor can be viewed using theshow environment command.

The snmp-server enable traps envmon command is used in conjunction with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP notifications. To send SNMP notifications, you must configure at least one snmp-server host command.

Examples

The following example shows how to enable a Cisco 12000 GSR to send environmental failure informs to the host at the address myhost.cisco.com using the community string defined as public:

snmp-server enable traps errdisable

To enable the CISCO-ERR-DISABLE-MIBSimple Network Management Protocol (SNMP) notification for traps and informs, use the snmp-server enable traps errdisable command in global configuration mode. To disable errdisable notifications, use the no form of this command.

snmp-server enable traps errdisable [notification-raterate]

no snmp-server enable traps [notification-raterate]

Syntax Description

notification-raterate

(Optional) Sets the number of notifications per minute.

Command Default

SNMP notifications are disabled.

Command Modes

Global configuration (config)

Command History

Release

Modification

12.2(33)SXI4

This command was introduced on the Supervisor Engine 720 and Supervisor Engine 32.

Examples

This example shows how to enable the SNMP errdisable notifications:

Router(config)# snmp-server enable traps errdisable

Router(config)#

This example shows how to set the SNMP errdisable notification rate to 500 per minute:

Related Commands

Command

Description

test snmp trap errdisable ifevent

Tests the cErrDisableInterfaceEventRev1 trap.

snmp-server enable traps firewall

To enable the router to send firewall Simple Network Management Protocol (SNMP) notifications, use the snmp-server enable traps firewall command in global configuration mode. To disable firewall SNMP notifications, use the no form of this command.

snmp-server enable traps firewallserverstatus

no snmp-server enable traps firewall serverstatus

Syntax Description

serverstatus

Displays the status of configured servers.

Command Default

SNMP notifications are disabled by default.

Command Modes

Global configuration

Command History

Release

Modification

12.4(6)T

This command was introduced.

Usage Guidelines

SNMP notifications are sent as traps by the agent. Currently, only one URL filtering trap is generated.

For a complete description of the notification types and additional MIB functions, refer to the CISCO-UNIFIED-FIREWALL-MIB.my and CISCO-FIREWALL-TC.my files, available on Cisco.com through:

http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml

The snmp-server enable traps firewall command is used in conjunction with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP notifications. To send SNMP notifications, you must configure at least one snmp-server host command.

Examples

In the following example, the router is configured to send firewall MIB inform notifications to the host nms.cisco.com using the community string named "public":

snmp-server enable traps firewall serverstatus

snmp-server host nms.cisco.com informs public firewall

Related Commands

Command

Description

snmp-server host

Specifies the recipient of an SNMP notification operation.

snmp-server enable traps flash

To enable Flash device insertion and removal Simple Network Management Protocol (SNMP) notifications, use the snmp-server enable traps flash command in global configuration mode. To disable Flash device SNMP notifications, use the no form of this command.

snmp-server enable traps flash [insertion] [removal]

no snmp-server enable traps flash [insertion] [removal]

Syntax Description

insertion

(Optional) Controls Flash card insertion notifications.

removal

(Optional) Controls Flash card removal notifications.

Command Default

SNMP notifications are disabled by default.

Command Modes

Global configuration

Command History

Release

Modification

12.3(2)T

This command was introduced.

12.0(23)S

This command was integrated in Cisco IOS Release 12.0 S.

12.1(13)E4

This command was implemented on the Cisco Catalyst 6000 Series.

Usage Guidelines

SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests.

This command enables or disables Flash card insertion and removal notifications, as defined by the ciscoFlashDeviceInsertedNotif and ciscoFlashDeviceRemovedNotif objects in the Cisco Flash MIB.

When the insertion keyword is used, a ciscoFlashDeviceInsertedNotif (OID 1.3.6.1.4.1.9.9.10.1.3.0.5) is sent whenever a removable Flash device is inserted.

When the removal keyword is used, a ciscoFlashDeviceRemovedNotif (OID 1.3.6.1.4.1.9.9.10.1.3.0.6) notification is sent whenever a removable Flash device is removed.

For a complete description of these notifications and additional MIB functions, see the CISCO-FLASH-MIB.my file, available on Cisco.com at http://www.cisco.com/go/mibs.

The snmp-server enable traps flash command is used in conjunction with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP notifications. To send SNMP notifications, you must configure at least one snmp-server host command.

Examples

The following example shows how to enable the router to send Flash card insertion and removal informs to the host at the address myhost.cisco.com using the community string defined as public:

Related Commands

snmp-server enable traps flowmon

To enable flow monitoring SNMP trap notifications, use the snmp-server enable traps flowmon command in global configuration mode. To disable flow monitoring trap notifications, use the no form of this command.

snmp-server enable traps flowmon

no snmp-server enable traps flowmon

Syntax Description

This command has no arguments or keywords.

Command Default

Flow monitoring trap notifications are disabled.

Command Modes

Global configuration (config)

Command History

Release

Modification

15.0(1)S

This command was introduced.

Usage Guidelines

SNMP notifications can be sent as traps or informs. This command enables trap notification requests only.

By default all notifications (traps) are disabled. You must explicitly enable any notifications that you need in your system. The snmp-server enable traps flowmon command is used in conjunction with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP notifications. To send SNMP notifications, you must configure at least one snmp-server host command.

Note For a complete description of the MIB tables for flow monitoring, see the appropriate CISCO_MIB.my file, available on Cisco.com at http://www.cisco.com/go/mibs.

This trap indicates that the indicated virtual circuit (VC) or subinterface has changed state, meaning that the VC or subinterface has either been created or invalidated, or has toggled between the active and inactive states.

Note For large scale configurations (systems containing hundreds of Frame Relay point-to-point subinterfaces), note that having Frame Relay notifications enabled could potentially have a negative impact on network performance when there are line status changes.

For a complete description of this notification and additional MIB functions, see the RFC1315-MIB.my file and the CISCO-FRAME-RELAY-MIB.my file, available in the "v1" and "v2" directories, respectively, at the Cisco.com MIB web site at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.

The snmp-server enable traps frame-relay command is used in conjunction with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP notifications. To send SNMP notifications, you must configure at least one snmp-server host command.

Examples

In the following example, the router is configured to send Frame Relay DLCI and subinterface state change informs to the host at the address myhost.cisco.com using the community string defined as public:

Related Commands

snmp-server enable traps frame-relay multilink bundle-mismatch

To enable multilink Frame Relay Simple Network Management Protocol (SNMP) notifications, use the snmp-server enable traps frame-relay multilink bundle-mismatch command in global configuration mode. To disable these notifications, use the no form of this command.

snmp-server enable traps frame-relay multilink bundle-mismatch

no snmp-server enable traps frame-relay multilink bundle-mismatch

Syntax Description

This command has no arguments or keywords.

Command Default

SNMP notifications are disabled.

Command Modes

Global configuration (config)

Command History

Release

Modification

12.4(9)T

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

12.2(33)SB

This command was integrated into Cisco IOS Release 12.2(33)SB.

Usage Guidelines

Use the multilink Frame Relay MIB to manage devices that are configured with multilink Frame Relay.

SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests.

Although the bundle-mismatch trap is one of five traps defined in RFC 3020, Cisco IOS supports only the bundle-mismatch trap.

For a complete description of MIB functions, see the CISCO-FRAME-RELAY-MIB.my file, which is available in the "SNMP v2 MIBs" directory found at the following URL:

Syntax Description

(Optional) Specifies a maximum number of traps that will be sent in the specified interval.

number-of-traps

(Optional) Integer in the range from 1 to 1000. The default is 10.

Command Default

Frame Relay subinterface SNMP notifications are disabled.

Command Modes

Global configuration

Command History

Release

Modification

12.2(13)T

This command was introduced.

Usage Guidelines

SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests.

Frame Relay subinterface traps are sent to the network management system (NMS) when a subinterface enters or leaves the down state.

To prevent trap storms, the countand interval keywords can be configured to limit the number of traps and the frequency at which they are sent. Configuring an interval of 0 seconds causes all Frame Relay subinterface traps to be sent.

You can disable Frame Relay subinterface traps by using the nosnmp-server enable traps frame-relay subif command. When traps are disabled, you can use the SNMP management application to poll your router for subinterface status information.

The snmp-server enable traps frame-relay subif command is used in conjunction with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP notifications. In order to send notifications, you must configure at least one snmp-server host command.

The snmp-server trap link ietf command must be configured in order to use the snmp-server enable traps frame-relay subif command. The snmp-server trap link ietf command is used to configure your router to use the RFC 2233 IETF standards-based implementation of linkUp/linkDown traps. The default Cisco object definitions do not generate linkUp/linkDown traps correctly for subinterfaces.

Examples

The following example shows how to enable Frame Relay subinterface traps on a router. If a Frame Relay subinterface on this router changes state, host 172.16.61.90 will receive the notifications:

! For Frame Relay subinterface traps to work on your router, you must first have SNMP
! support and an IP routing protocol configured on your router:

snmp-server enable traps if-monitor

To globally enable if-monitor traps, use the snmp-server enable traps if-monitor command in global configuration mode. To disable if-monitor traps, use the no form of this command.

snmp-server enable traps if-monitor

no snmp-server enable traps if-monitor

Syntax Description

This command has no arguments or keywords.

Command Default

Traps are not generated.

Command Modes

Global configuration (config)

Command History

Release

Modification

12.3(1)

This command was introduced.

Usage Guidelines

The snmp-server enable traps if-monitor command enables the if-monitor threshold traps for link monitoring. To enable traps for a particular interface, you must enable them globally using the snmp-server enable traps if-monitor command and then explicitly on that interface using the snmp trap if-monitor command.

A high threshold limit is the highest value for a parameter on a specific link. If that value is reached or exceeded in the configured major monitoring interval, a trap is sent and a message is logged. The link is brought down if the restart mechanism is enabled.

A low threshold limit is the lowest value for a parameter on a specified link. If that value is reached or exceeded in the major monitoring interval, a trap is sent and a message is logged.

Examples

The following example shows how to enable if-monitor traps on all interfaces:

Router(config)# snmp-server enable traps if-monitor

Related Commands

Command

Description

snmp trap if-monitor

Enables if-monitor traps for a particular interface.

snmp-server enable traps ip local pool

To enable the sending of local IP pool Simple Network Management Protocol (SNMP) notifications, use the snmp-server enable traps ip local pool command in global configuration mode. To disable local IP pool notifications, use the no form of this command.

snmp-server enable traps ip local pool

no snmp-server enable traps ip local pool

Syntax Description

This command has no arguments or keywords.

Command Default

This command is disabled; no notifications are sent.

Command Modes

Global configuration

Command History

Release

Modification

12.3(8)T

This command was introduced.

Examples

The following example shows how to enable the sending of local IP SNMP notifications:

Router(config)# snmp-server enable traps ip local pool

Related Commands

Command

Description

snmp-server host

Specifies the recipient of an SNMP notification operation.

snmp-server enable traps isdn

To enable the sending of Integrated Services Digital Network (ISDN)-specific Simple Network Management Protocol (SNMP) notifications, use the snmp-server enable traps isdn command in global configuration mode. To disable ISDN-specific SNMP notifications, use the no form of this command.

Syntax Description

•demandNbrCallInformation (1) This notification is sent to the manager whenever a successful call clears, or a failed call attempt is determined to have ultimately failed. In the event that call retry is active, then this is after all retry attempts have failed. However, only one such notification is sent in between successful call attempts; subsequent call attempts do not generate notifications of this type.

•demandNbrCallDetails (2) This notification is sent to the manager whenever a call connects, or clears, or a failed call attempt is determined to have ultimately failed. In the event that call retry is active, then this is after all retry attempts have failed. However, only one such notification is sent in between successful call attempts; subsequent call attempts do not generate notifications of this type.

chan-not-avail

(Optional) Controls SNMP ISDN channel-not-available notifications. ISDN PRI channel-not-available traps are generated when a requested DS-0 channel is not available, or when there is no modem available to take the incoming call. These notifications are available only for ISDN PRI interfaces.

ietf

(Optional) Controls the SNMP ISDN IETF traps.

isdnu-interface

(Optional) Controls SNMP ISDN U interface notifications.

layer2

(Optional) Controls SNMP ISDN Layer 2 transition notifications.

Defaults

SNMP notifications are disabled by default.

If you enter this command with none of the optional keywords, all available notifications are enabled.

Command Modes

Global configuration (config)

Command History

Release

Modification

10.3

This command was introduced.

11.3

This command was modified. The call-information and isdnu-interface keywords were added for the Cisco 1600 series router.

12.0

This command was modified. Support for the call-information and isdnu-interface keywords was introduced for most voice platforms.

12.1(5)T

This command was modified. Support for the chan-not-available keyword was added for the Cisco AS5300, Cisco AS5400, and Cisco AS5800 access servers only.

Usage Guidelines

SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests for the specified notification types. ISDN notifications are defined in the CISCO-ISDN-MIB.my and CISCO-ISDNU-IF-MIB.my files, available on Cisco.com at http://www.cisco.com/public/mibs/v2/.

Availability of notifications will depend on your platform. To see what notifications are available, use the snmp-server enable traps isdn ? command.

If you do not enter an snmp-server enable traps isdn command, no notifications controlled by this command are sent. In order to configure the router to send these SNMP notifications, you must enter at least one snmp-server enable traps isdn command. If you enter the command with no keywords, all notification types are enabled. If you enter the command with a keyword, only the notification type related to that keyword is enabled.

The snmp-server enable traps snmp command is used in conjunction with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP notifications. To send SNMP notifications, you must configure at least one snmp-server host command.

Examples

The following example shows how to determine what notification types are available on a Cisco AS5300 and then shows how to enable channel-not-available and Layer 2 informs:

snmp-server enable traps l2tun pseudowire status

To enable the sending of Simple Network Management Protocol (SNMP) notifications when a pseudowire changes state, use the snmp-server enable traps l2tun pseudowire status command in global configuration mode. To disable SNMP notifications of pseudowire state changes, use the no form of this command.

snmp-server enable traps l2tun pseudowire status

no snmp-server enable traps l2tun pseudowire status

Syntax Description

This command has no arguments or keywords.

Defaults

SNMP notifications are disabled by default.

Command Modes

Global configuration

Command History

Release

Modification

12.0(31)S

This command was introduced.

12.2(27)SBC

This command was integrated into Cisco IOS Release 12.2(27)SBC.

Cisco IOS XE Release 2.4

This command was integrated into Cisco IOS XE Release 2.4.

Usage Guidelines

SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests.

This command controls (enables or disables) notification of pseudowire state changes. For a complete description of these notification types, and for information about the other MIB functions, see the VPDN MIB, available through the Cisco Technical Assistance Center (TAC) SNMP Object Navigator tool at http://www.cisco.com/go/mibs.

The snmp-server enable traps l2tun pseudowire status command is used in conjunction with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP notifications. To send SNMP notifications, you must configure at least one snmp-server host command.

Use the snmp-server enable traps command without any additional syntax to disable all SNMP notification types supported on your system.

Examples

The following example enables the router to send pseudowire state change informs to the host at the address myhost.cisco.com using the community string defined as public:

SNMP notifications can be sent as traps or inform requests and this command enables both types of notifications for L2TP sessions. To specify whether the notifications should be sent as traps or informs, and to specify which host or hosts receive SNMP notifications, use the snmp-server host [traps | informs] command.

Use the snmp-server enable traps command without any additional syntax to disable all SNMP notification types supported on your system.

Examples

The following example shows how to enable a router to send L2TP session traps to the host specified by the name myhost.example.com, using the community string defined as public:

Related Commands

Command

Description

snmp-server enable traps

Enables all SNMP notifications available on your system.

snmp-server host

Specifies whether you want the SNMP notifications sent as traps or informs, the version of SNMP to use, the security level of the notifications (for SNMPv3), and the recipient (host) of the notifications.

snmp-server enable traps memory

To enable a device to send Simple Network Management Protocol (SNMP) notifications when memory pool buffer usage reaches a new peak, use the snmp-server enable traps memory command in global configuration mode. To stop notifications from being generated, use the no form of this command.

snmp-server enable traps memory [bufferpeak]

no snmp-server enable traps memory [bufferpeak]

Syntax Description

bufferpeak

(Optional) Specifies memory buffer peak notifications.

Command Default

SNMP notifications in the MEMPOOL-MIB are not enabled.

Command Modes

Global configuration

Command History

Release

Modification

12.3(4)T

This command was introduced.

12.2(25)S

This command was integrated into Cisco IOS Release 12.2(25)S.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2(33)SXH

This command was integrated into Cisco IOS Release 12.2(33)SXH.

Usage Guidelines

SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests.

This command enables or disables memory buffer peak (cempMemBufferNotify) notifications.When they are enabled, these notifications are sent when the value of the maximum number of buffer objects changes.

In current releases of Cisco IOS software, this command has the same behavior whether you use or omit the bufferpeak keyword.

The cempMemBufferNotify notification type is defined as {cempMIBNotifications 1} in the CISCO-ENHANCED-MEMPOOL-MIB. For a complete description of this notification and additional MIB functions, see the CISCO-ENHANCED-MEMPOOL-MIB.my file, available on Cisco.com at http://www.cisco.com/go/mibs/.

Examples

In the following example all available memory related SNMP notifications are enabled and configured to be sent as informs to the host myhost.cisco.com using the community string public:

Related Commands

Command

Description

show buffers

Displays memory buffer pool related information.

show memory

Displays memory pool related information.

snmp-server host

Specifies whether you want the SNMP notifications sent as traps or informs, the version of SNMP to use, the security level of the notifications (for SNMPv3), and the recipient (host) of the notifications.

Syntax Description

Command Default

This command is disabled by default; therefore, SNMP notifications for OSPF nonvirtual interface mismatch errors are not created.

Command Modes

Global configuration

Command History

Release

Modification

12.3(5)

This command was introduced.

12.3(4)T

This command was integrated into Cisco IOS Release 12.3(4)T.

12.0(26)S

This command was integrated into Cisco IOS Release 12.0(26)S.

12.2(25)S

This command was integrated into Cisco IOS Release 12.2(25)S.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2(31)SB2

This command was integrated into Cisco IOS Release 12.2(31)SB2.

12.2(33)SXH

This command was integrated into Cisco IOS Release 12.2(33)SXH.

Usage Guidelines

To enable the cospfShamLinkConfigError trap, you must first enter the snmp-server enable traps ospf cisco-specific errors config-error command in global configuration mode. The snmp-server enable traps ospf cisco-specific errors config-error command enables the cospfConfigError trap, so that both traps can be generated at the same place and maintain consistency with a similar case for configuration errors across virtual links.

If you try to enable the cospfShamLinkConfigError trap before configuring the cospfospfConfigError trap you will receive an error message stating you must first configure the cospfConfigError trap.

Examples

The following example enables the router to send nonvirtual interface mismatch error notifications to the host at the address myhost.cisco.com using the community string defined as public:

Command Default

This command is disabled by default; therefore, SNMP notifications for OSPF sham-link errors are not created.

Command Modes

Global configuration

Command History

Release

Modification

12.0(30)S

This command was introduced.

12.3(14)T

This command was integrated into Cisco IOS Release 12.3(14)T.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2(31)SB2

This command was integrated into Cisco IOS Release 12.2(31)SB2.

12.2(33)SXH

This command was integrated into Cisco IOS Release 12.2(33)SXH.

Usage Guidelines

To enable the cospfShamLinkConfigError trap, you must first enter the snmp-server enable traps ospf cisco-specific errors config-error command in global configuration mode. The snmp-server enable traps ospf cisco-specific errors config-error command enables the cospfConfigError trap, so that both traps can be generated at the same place and maintain consistency with a similar case for configuration errors across virtual links.

If you try to enable the cospfShamLinkConfigError trap before configuring the cospfospfConfigError trap you will receive an error message stating you must first configure the cospfConfigError trap.

Examples

The following example enables the router to send OSPF sham-link error notifications to the host at the address myhost.cisco.com using the community string defined as public:

snmp-server enable traps ospf cisco-specific retransmit

To enable Simple Network Management Protocol (SNMP) notifications for Open Shortest Path First (OSPF) retransmission errors, use the snmp-server enable traps ospf cisco-specific retransmit command in global configuration mode. To disable OSPF sham-link error SNMP notifications, use the no form of this command.