Difference between revisions of "TUT:Configuring snmptrapd to receive SNMPv3 notifications"

From Net-SNMP Wiki
Jump to: navigation, search
(make definitions proper.)
Line 13: Line 13:
 
;TRAPs: Sent by an application or daemon but no response is sent or expected by the notification receiver.
 
;TRAPs: Sent by an application or daemon but no response is sent or expected by the notification receiver.
 
;INFORMs: INFORMs are nothing more than an acknowledged TRAP.  I.E., when the notification receiver receives an INFORM it sends a response back that indicates "I got it".  (An application may be configured to send more than one INFORM message if it failed to receive an acknowledgment)  
 
;INFORMs: INFORMs are nothing more than an acknowledged TRAP.  I.E., when the notification receiver receives an INFORM it sends a response back that indicates "I got it".  (An application may be configured to send more than one INFORM message if it failed to receive an acknowledgment)  
 +
 +
=== SNMPv3 INFORMs vs SNMP TRAPs ===
 +
 +
SNMPv3 with the [[User-Based Security Model]] (USM) makes use of an [[EngineID]] identifier for the SNMPv3 application that is ''authoratative'' (meaning the one who controls the flow of information).
 +
 +
With SNMPv3 TRAPs, the ''authoratative'' engine is the engine that sends the trap
 +
 +
With SNMPv3 INFORMs, the ''authoratative'' engine is the engine that receives the trap.
 +
 +
SNMPv3 USM users are uniquely defined by a combination of the authoratative EngineID and the user name.
  
 
{{TUT:LIST}}
 
{{TUT:LIST}}

Revision as of 16:54, 10 October 2007

SNMPv3 background

Before you can begin to understand how to use snmptrapd with SNMPv3 protected notifications you need to understand some basic concepts. Specifically, please read:

  • SNMPv3 Options -- Documents how to use Net-SNMP with SNMPv3 in general
  • TUT:snmptrap -- Discussing SNMP notifications and sending them using snmptrap
  • TUT:snmptrap SNMPv3 -- Discussing SNMPv3 notifications and sending them using snmptrap

SNMP INFORMs vs SNMP TRAPs Notifications

SNMP supports two types of notifications: TRAPs and INFORMs. (In SNMPv1, there was only TRAPs; SNMPv2c and SNMPv3 support INFORMs too). There is one fundamental difference between SNMP INFORMs and TRAPs:

TRAPs
Sent by an application or daemon but no response is sent or expected by the notification receiver.
INFORMs
INFORMs are nothing more than an acknowledged TRAP. I.E., when the notification receiver receives an INFORM it sends a response back that indicates "I got it". (An application may be configured to send more than one INFORM message if it failed to receive an acknowledgment)

SNMPv3 INFORMs vs SNMP TRAPs

SNMPv3 with the User-Based Security Model (USM) makes use of an EngineID identifier for the SNMPv3 application that is authoratative (meaning the one who controls the flow of information).

With SNMPv3 TRAPs, the authoratative engine is the engine that sends the trap

With SNMPv3 INFORMs, the authoratative engine is the engine that receives the trap.

SNMPv3 USM users are uniquely defined by a combination of the authoratative EngineID and the user name.

Tutorial Sections

About the SNMP Protocol

These tutorial links talk about SNMP generically and how the protocol itself works. They are good introductory reading material and the concepts are important to understand before diving into the later tutorials about Net-SNMP itself.

Net-SNMP Command Line Applications

These tutorial pages discuss the command line tools provided in the Net-SNMP suite of tools. Nearly all the example commands in these tutorials works if you try it yourself, as they're all examples that talk to our online Net-SNMP test agent. Given them a shot!

Application Configuration

All of our applications support configuration to allow you to customize how they behave.

Net-SNMP Daemons

Net-SNMP comes with two long-running daemons: a SNMP agent (snmpd) for responding to management requests and a notification receiver (snmptrapd) for receiving SNMP notifications.

Coding Tutorials

Net-SNMP comes with a highly flexible and extensible API. The API allows you to create your own commands, add extensions to the agent to support your own MIBs and perform specialized processing of notifications.

Debugging SNMP Applications and Agents

All our tools and applications have extensive debugging output. These tutorials talk about how the debugging system works and how you can add your own debugging statements to you code:

Operating System Specific Tutorials

Retrieved from "http://www.net-snmp.org/wiki/index.php?title=TUT:Configuring_snmptrapd_to_receive_SNMPv3_notifications&oldid=3082"