SNMP Inform Request
The Simple Network Management Protocol (SNMP) Inform Requests feature allows devices to send inform requests to SNMP managers.
- Finding Feature Information
- Information About SNMP Inform Requests
- How to Configure SNMP Inform Requests
- Configuration Examples for SNMP Inform Request
- Additional References
- Feature Information for SNMP Inform Request
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Information About SNMP Inform Requests
SNMP Inform Request
The SNMP Inform Request feature supports sending inform requests. SNMP asynchronous notifications are usually sent as SNMP traps.
Traps are less reliable than informs because an acknowledgment is not sent from the receiving end when a trap is received; however, an SNMP manager that receives an inform acknowledges the message with an SNMP response PDU. If the sender does not receive a response for an inform, the inform can be sent again.
How to Configure SNMP Inform Requests
Configuring Devices to Send Traps
Perform the following task to configure the device to send traps to a host in global configuration mode:
1. enable
2.
configure
terminal
3.
snmp-server
host
host[version {1|2c}]community-string[udp-port
port][notification-type]
4.
snmp-server
enable
traps[
notification-type] [notification-option]
5.
end
DETAILED STEPS
Changing Inform Operation Values
Perform the following optional task in global configuration mode to change inform operation values:
1.
enable
2.
configure
terminal
3.
snmp-server
informs
[retries
retries] [timeout
seconds] [pending
pending]
4.
snmp-server
trap-source
interface
5.
end
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
Step 1 |
enable
Example: Device> enable |
Enables privileged EXEC mode. |
Step 2 |
configure
terminal
Example: Device# configure terminal |
Enters global configuration mode. |
Step 3 |
snmp-server
informs
[retries
retries] [timeout
seconds] [pending
pending]
Example: Device(config)# snmp-server informs retries 10 timeout 30 pending 100 |
Configures inform-specific operation values. |
Step 4 |
snmp-server
trap-source
interface
Example: Device(config)# snmp-server trap-source Gigabitethernet 1/2/1 |
This example sets the IP address for the Fast Ethernet interface in slot2, port 1 as the source for all SNMP notifications. |
Step 5 | end
Example: Device(config)# end |
Exits global configuration mode. |
Configuration Examples for SNMP Inform Request
Example: Configuring SNMP Inform Request
The following configuration example shows how to configure the SNMP Inform Request feature for SNMPv1 or SNMPv2:
The following example sends the SNMP and Cisco environmental monitor enterprise-specific traps to address 172.30.2.160:
Device(config)# snmp-server enable traps Device(config)# snmp-server host 172.30.2.160 public snmp envmon
The following example enables the device to send all traps to the host myhost.example.com using the community string public:
Device(config)# snmp-server enable traps Device(config)# snmp-server host myhost.example.com public
The following example will not send traps to any host. The BGP traps are enabled for all hosts, but only the ISDN traps are enabled to be sent to a host.
Device(config)# snmp-server enable traps bgp Device(config)# snmp-server host bob public isdn
The following example enables the device to send all inform requests to the host myhost.example.com using the community string public:
Device(config)# snmp-server enable traps Device(config)# snmp-server host myhost.example.com informs version 2c public
Additional References
Related Documents
Related Topic |
Document Title |
---|---|
Cisco IOS commands |
|
SNMP commands: complete command syntax, command mode, command history, defaults, usage guidelines, and examples |
|
Cisco implementation of RFC 1724, RIP Version 2 MIB Extensions |
RIPv2 Monitoring with SNMP Using the RFC 1724 MIB Extensions feature module |
DSP Operational State Notifications for notifications to be generated when a digital signaling processor (DSP) is used |
DSP Operational State Notifications feature module |
Standards and RFCs
Standard/RFC |
Title |
---|---|
CBC-DES (DES-56) standard |
Symmetric Encryption Protocol |
STD: 58 |
Structure of Management Information Version 2 (SMIv2) |
RFC 1067 |
A Simple Network Management Protocol |
RFC 1091 |
Telnet terminal-type option |
RFC 1098 |
Simple Network Management Protocol (SNMP) |
RFC 1157 |
Simple Network Management Protocol (SNMP) |
RFC 1213 |
Management Information Base for Network Management of TCP/IP-based internets:MIB-II |
RFC 1215 |
Convention for defining traps for use with the SNMP |
RFC 1901 |
Introduction to Community-based SNMPv2 |
RFC 1905 |
Common Management Information Services and Protocol over TCP/IP (CMOT) |
RFC 1906 |
Telnet X Display Location Option |
RFC 1908 |
Simple Network Management Protocol (SNMP) |
RFC 2104 |
HMAC: Keyed-Hashing for Message Authentication |
RFC 2206 |
RSVP Management Information Base using SMIv2 |
RFC 2213 |
Integrated Services Management Information Base using SMIv2 |
RFC 2214 |
Integrated Services Management Information Base Guaranteed Service Extensions using SMIv2 |
RFC 2271 |
An Architecture for Describing SNMP Management Frameworks |
RFC 2570 |
Introduction to Version 3 of the Internet-standard Network Management Framework |
RFC 2578 |
Structure of Management Information Version 2 (SMIv2) |
RFC 2579 |
Textual Conventions for SMIv2 |
RFC 2580 |
Conformance Statements for SMIv2 |
RFC 2981 |
Event MIB |
RFC 2982 |
Distributed Management Expression MIB |
RFC 3413 |
SNMPv3 Applications |
RFC 3415 |
View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP) |
RFC 3418 |
Management Information Base (MIB) for the Simple Network Management Protocol (SNMP) |
MIBs
MIB |
MIBs Link |
---|---|
|
To locate and download MIBs for selected platforms, releases, and feature sets, use Cisco MIB Locator found at the following URL: |
Technical Assistance
Description |
Link |
---|---|
The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password. |
Feature Information for SNMP Inform Request
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to . An account on Cisco.com is not required.
Feature Name |
Releases |
Feature Information |
---|---|---|
SNMP Inform Request |
Cisco IOS XE Release 3.3SE |
The SNMP Inform Request feature supports sending inform requests. SNMP asynchronous notifications are usually sent as SNMP traps. Traps are less reliable than informs because an acknowledgment is not sent from the receiving end when a trap is received; however, an SNMP manager that receives an inform acknowledges the message with an SNMP response PDU. If the sender does not receive a response for an inform, the inform can be sent again. In Cisco IOS XE Release 3.3SE, support was added for the Cisco Catalyst 3650 Series Switches and Cisco Catalyst 3850 Series Switches. |