Individual SNMP Trap Support

Feature Overview

Benefits

Individual SNMP Trap Support

July 24, 2000

This feature module describes the Individual SNMP Trap Support feature introduce in Cisco IOS Release 12.1(3)T. It includes information on the benefits of the new feature, supported platforms, related documents, and the expanded command used to enable individual SNMP traps.

This document includes the following sections:

Feature Overview

The Individual SNMP Trap Support Feature adds the ability to enable or disable SNMP system management notifications (traps) individually. SNMP traps that can be specified are authentication-failure, linkup, linkdown, and coldstart. This feature expands the functionality of the snmp-server enable traps snmp command. Prior to the introduction of this feature, all four trap types were enabled or disabled simultaneously by the snmp-server enable traps snmp command.

Individual SNMP Trap Support is supported for all versions of SNMP supported by Cisco IOS software (SNMPv1, SNMPv2c, and SNMPv3).

Note As both SNMP traps and informs are enabled or disabled thorough the use of the snmp-server enable traps command, all references to traps in this document also apply to informs. The term "notifications" is used to refer to both traps and informs.

Benefits

Increased Control

The ability to enable or disable SNMP trap types individually increases your control over SNMP behaviors, allowing you to tailor characteristics to the specific needs of your network.

More Efficient Use of Resources

By disabling SNMP traps notifications which are not needed, you can increase the amount of free bandwidth and eliminate unnecessary SNMP processing tasks.

Supported Platforms

Cisco 1600 Series (Cisco 1601-1605, Cisco 1601R-1605R)
Cisco 2500 Series (Cisco 2501-2525)
Cisco 2600 Series
Cisco 4500/4700 Series (Cisco 4500-m, 4700, 4700-m)
Cisco AS5200 Series
Cisco AS5300 Series
Cisco AS5400 Series
Cisco AS5800 Series
Cisco 6400 NRP/NSP Series
Cisco 7200 Series (Cisco 7202, 7204, 7206)
Cisco UBR7200 Platforms

Supported Standards, MIBs, and RFCs

The authentication, linkup, linkdown and coldstart traps were originally defined in RFC 1157, "A Simple Network Management Protocol (SNMP)", which is a full Internet Standard (STD 15).

Configuration Tasks

See the following sections for configuration tasks for the Individual SNMP Trap Support feature. Each task is optional.

Enabling Individual SNMP Trap Types

You can enable SNMP trap types individually by using the authentication, linkup, linkdown or coldstart keywords with the snmp-server enable traps snmp command. For example, to enable only linkdown notifications, use the following command in global configuration mode:

Command Purpose

Router#snmp-server enable traps snmp linkdown
Enables only the linkdown SNMP trap type.

Command	Purpose
Router#snmp-server enable traps snmp linkdown	Enables only the linkdown SNMP trap type.

Configuring All SNMP Trap Types Simultaneously

To enable all the SNMP trap types at once, use the command snmp-server enable traps snmp command without any of the optional trap type keywords:

Command Purpose

Router#snmp-server enable traps snmp
Enables all SNMP trap types on the router.

Command	Purpose
Router#snmp-server enable traps snmp	Enables all SNMP trap types on the router.

This command will then appear in the configuration file (viewed using the show running-config command or more system:running-config command) as:

snmp-server enable traps snmp authentication linkup linkdown coldstart

Note that all traps types are listed as enabled.

To disable all SNMP trap types, use the no form of the command:

Command Purpose

Router#no snmp-server enable traps snmp
Disables all SNMP trap types on the router.

Command	Purpose
Router#no snmp-server enable traps snmp	Disables all SNMP trap types on the router.

Disabling Individual SNMP Trap Types

You can also enable all trap types, then disable the ones you don't need. To disable individual trap types, specify the specific trap type by using the authentication, linkup, linkdown or coldstart keywords. For example, to disable only the authentication-failure trap notification, use the following command:

Command Purpose

Router#no snmp-server enable traps snmp authentication
Disables authentication SNMP traps on the router.

Command	Purpose
Router#no snmp-server enable traps snmp authentication	Disables authentication SNMP traps on the router.

Assuming you had previously enabled all trap types, the configuration file will then list only:

snmp-server enable traps snmp linkup linkdown coldstart

Note that when specific SNMP trap types are disabled, they do not appear in the configuration file.

Configuration Examples

This section gives an example of enabling all SNMP trap types then disabling the linkup and linkdown traps.

Router> enable
Password:
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# snmp-server enable traps snmp
Router(config)#^Z
Router# more system:running-config
...
snmp-server enable traps snmp authentication linkup linkdown coldstart
...
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# no snmp-server enable traps snmp linkup
Router(config)# no snmp-server enable traps snmp linkdown
Router(config)#^Z
Router# more system:running-config
...
snmp-server enable traps snmp authentication coldstart
...

Command Reference

This section documents modified commands. All other commands used with this feature are documented in the Release 12.1 Cisco IOS Configuration Fundamentals Command Reference.

snmp-server enable traps

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

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

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

Syntax Description

notification-type

(Optional) Type of notification to enable. If no type is specified, all available notifications are enabled. Note that the notification types available on your system will vary depending on platform support. The notification type can be one of the following keywords:

bgp—Controls Border Gateway Protocol (BGP) state change notifications.

config—Controls SNMP configuration notifications.

dial—Controls SNMP dial control notifications.

entity—Controls Entity MIB modification notifications.

envmon—Controls Cisco enterprise-specific environmental monitor notifications when an environmental threshold is exceeded. When the envmon keyword is used, you can specify a notification-option value.

frame-relay—Controls Frame Relay notifications.

hsrp—Controls Hot Standby Routing Protocol (HSRP) notifications based on the HSRP MIB.

isdn—Controls Integrated Services Digital Network (ISDN) notifications. When the isdn keyword is used, you can specify a notification-option value.

repeater—Controls Ethernet hub repeater notifications. When the repeater keyword is selected, you can specify a notification-option value.

rsvp—Controls Resource Reservation Protocol (RSVP) notifications based on the RSVP MIB.

rtr—Controls Cisco Service Assurance Agent Response Time Reporter (SAA-RTR) notifications.

snmp—Controls Simple Network Management Protocol (SNMP) notifications. When the snmp keyword is used, you can optionally specify a notification-option value.

syslog—Controls error message notifications (Cisco Syslog MIB). Specify the level of messages to be sent with the logging history level command.

notification-option

(Optional)

envmon [voltage | shutdown | supply | fan | temperature]
—When the envmon keyword is used, you can enable a specific environmental notification type, or accept all notification types from the environmental monitor system. If no option is specified, all environmental notifications are enabled. The option can be one or more of the following keywords: voltage, shutdown, supply, fan, and temperature.

isdn [call-information | isdn u-interface]
—When the isdn keyword is used, you can specify the call-information keyword to enable an SNMP ISDN call information notification for the ISDN MIB subsystem, or you can specify the isdnu-interface keyword to enable an SNMP ISDN U interface notification for the ISDN U interface MIB subsystem.

repeater [health | reset]
—When the repeater keyword is used, you can specify the repeater option. If no option is specified, all repeater notifications are enabled. The option can be one or more of the following keywords:

health—Enables Repeater Hub MIB health notification.

reset—Enables Repeater Hub MIB reset notification.

snmp [authentication | linkup | linkdown | coldstart]
—(Optional) When the snmp keyword is used, you can specify the specific notification type you wish to enable or disable. If no keyword is used, all SNMP notification types are enabled (or disabled, if the no form is used). The notification types available are:

authentication—Controls the sending of SNMP authentication failure notifications. An authenticationFailure(4) trap signifies that the sending protocol entity is the addressee of a protocol message that is not properly authenticated.

linkup—Controls the sending of SNMP linkup notifications. A linkUp(3) trap signifies that the sending protocol entity recognizes that one of the communication links represented in the agent's configuration has come up.

linkdown—Controls the sending of SNMP linkdown notifications. A linkDown(2) trap signifies that the sending protocol entity recognizes a failure in one of the communication links represented in the agent's configuration.

coldstart—Controls the sending of SNMP coldstart notifications. A coldStart(0) trap signifies that the sending protocol entity is reinitializing itself such that the agent's configuration or the protocol entity implementation may be altered.

notification-type	(Optional) Type of notification to enable. If no type is specified, all available notifications are enabled. Note that the notification types available on your system will vary depending on platform support. The notification type can be one of the following keywords: bgp—Controls Border Gateway Protocol (BGP) state change notifications. config—Controls SNMP configuration notifications. dial—Controls SNMP dial control notifications. entity—Controls Entity MIB modification notifications. envmon—Controls Cisco enterprise-specific environmental monitor notifications when an environmental threshold is exceeded. When the envmon keyword is used, you can specify a notification-option value. frame-relay—Controls Frame Relay notifications. hsrp—Controls Hot Standby Routing Protocol (HSRP) notifications based on the HSRP MIB. isdn—Controls Integrated Services Digital Network (ISDN) notifications. When the isdn keyword is used, you can specify a notification-option value. repeater—Controls Ethernet hub repeater notifications. When the repeater keyword is selected, you can specify a notification-option value. rsvp—Controls Resource Reservation Protocol (RSVP) notifications based on the RSVP MIB. rtr—Controls Cisco Service Assurance Agent Response Time Reporter (SAA-RTR) notifications. snmp—Controls Simple Network Management Protocol (SNMP) notifications. When the snmp keyword is used, you can optionally specify a notification-option value. syslog—Controls error message notifications (Cisco Syslog MIB). Specify the level of messages to be sent with the logging history level command.
notification-option	(Optional) envmon [voltage \| shutdown \| supply \| fan \| temperature] —When the envmon keyword is used, you can enable a specific environmental notification type, or accept all notification types from the environmental monitor system. If no option is specified, all environmental notifications are enabled. The option can be one or more of the following keywords: voltage, shutdown, supply, fan, and temperature. isdn [call-information \| isdn u-interface] —When the isdn keyword is used, you can specify the call-information keyword to enable an SNMP ISDN call information notification for the ISDN MIB subsystem, or you can specify the isdnu-interface keyword to enable an SNMP ISDN U interface notification for the ISDN U interface MIB subsystem. repeater [health \| reset] —When the repeater keyword is used, you can specify the repeater option. If no option is specified, all repeater notifications are enabled. The option can be one or more of the following keywords: health—Enables Repeater Hub MIB health notification. reset—Enables Repeater Hub MIB reset notification. snmp [authentication \| linkup \| linkdown \| coldstart] —(Optional) When the snmp keyword is used, you can specify the specific notification type you wish to enable or disable. If no keyword is used, all SNMP notification types are enabled (or disabled, if the no form is used). The notification types available are: authentication—Controls the sending of SNMP authentication failure notifications. An authenticationFailure(4) trap signifies that the sending protocol entity is the addressee of a protocol message that is not properly authenticated. linkup—Controls the sending of SNMP linkup notifications. A linkUp(3) trap signifies that the sending protocol entity recognizes that one of the communication links represented in the agent's configuration has come up. linkdown—Controls the sending of SNMP linkdown notifications. A linkDown(2) trap signifies that the sending protocol entity recognizes a failure in one of the communication links represented in the agent's configuration. coldstart—Controls the sending of SNMP coldstart notifications. A coldStart(0) trap signifies that the sending protocol entity is reinitializing itself such that the agent's configuration or the protocol entity implementation may be altered.

Defaults

SNMP notifications are disabled.

If you enter this command with no notification-type keywords, the default is to enable all notification types controlled by this command.

Command Modes

Global configuration

Command History

Release Modification

11.1

This command was introduced.

12.0(2)T

The rsvp keyword was added.

12.0(3)T

The hsrp keyword was added.

12.1(3)T

The following keywords were added to the snmp-server enable traps snmp form of this command:

linkup

linkdown

coldstart

The following notification type keywords were added for the Cisco AS5300 platform only:

ds0-busyout

isdn chan-not-avail

modem-health

ds1-loopback

The following notification type keyword was added for the Cisco AS5300 and AS5800 platforms only:

aaa-server

Release	Modification
11.1	This command was introduced.
12.0(2)T	The rsvp keyword was added.
12.0(3)T	The hsrp keyword was added.
12.1(3)T	The following keywords were added to the snmp-server enable traps snmp form of this command: linkup linkdown coldstart The following notification type keywords were added for the Cisco AS5300 platform only: ds0-busyout isdn chan-not-avail modem-health ds1-loopback The following notification type keyword was added for the Cisco AS5300 and AS5800 platforms only: aaa-server

Usage Guidelines

The snmp-server enable traps snmp [ linkup] [linkdown] form of this command replaces the snmp trap link-status interface configuration mode command.

The no form of the snmp-server enable traps command is useful for disabling notifications that are generating a large amount of unneeded noise on your network.

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

If you do not enter an snmp-server enable traps 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 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. In order to enable multiple types of notifications, you must issue a separate snmp-server enable traps command for each notification type and notification option.

The snmp-server enable traps command is used 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.

For a host to receive a notification controlled by this command, both the snmp-server enable traps command and the snmp-server host command for that host must be enabled. If the notification type is not controlled by this command, just the appropriate snmp-server host command must be enabled.

The notification types used in this command all have an associated MIB object that allows them to be enabled or disabled (for example, HSRP traps are defined using the HSRP MIB, repeater traps are defined using the Repeater Hub MIB, and so on). Not all of the notification types available in the snmp-server host command have notificationEnable MIB objects, so some of these cannot be controlled using the snmp-server enable command.

Examples

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

snmp-server enable traps
snmp-server host myhost.cisco.com public

The following example enables the router to send Frame Relay and environmental monitor traps to the host myhost.cisco.com using the community string public:

snmp-server enable traps frame-relay
snmp-server enable traps envmon temperature
snmp-server host myhost.cisco.com public

The following example will not send traps to any host. The 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).

snmp-server enable traps bgp
snmp-server host bob public isdn

The following example enables the router to send all inform requests to the host labeled myhost.cisco.com using the community string defined as public:

snmp-server enable traps
snmp-server host myhost.cisco.com informs version 2c public

The following example sends HSRP MIB traps to the host myhost.cisco.com using the community string public.

snmp-server enable hsrp
snmp-server host myhost.cisco.com traps version 2c public hsrp

Related Commands

Command Description

snmp-server host

Specifies the recipient of an SNMP notification operation.

snmp-server informs

Specifies inform request options.

snmp-server trap-source

Specifies the interface that an SNMP trap should originate from.

Table of Contents