Difference between revisions of "TRAP"
From Net-SNMP Wiki
(Created page with "{{protocol|GET|utility=snmptrap|ref=3416|snmp=1-3}} A '''TRAP''' is a one-way communication, and is one of two types of notifications that can be delivered over SNMP. An en...") |
|||
| Line 1: | Line 1: | ||
{{protocol|GET|utility=snmptrap|ref=3416|snmp=1-3}} | {{protocol|GET|utility=snmptrap|ref=3416|snmp=1-3}} | ||
| − | A '''TRAP''' is a one-way communication, and is one of two types of [[notification]]s that can be delivered over SNMP. An entity that receives a '''TRAP''' does not acknowledge that it has received it, and thus it is not possible for the sender to be assured that the ''TRAP'' successfully made it to the destination. Because of this, the usage of [[INFORM]]s are recommended instead. | + | A '''TRAP''' is a one-way communication, and is one of two types of [[notification]]s that can be delivered over SNMP. An entity that receives a '''TRAP''' does not acknowledge that it has received it (like [[snmptrapd]], and thus it is not possible for the sender to be assured that the ''TRAP'' successfully made it to the destination. Because of this, the usage of [[INFORM]]s are recommended instead. |
== TRAP Versions == | == TRAP Versions == | ||
Latest revision as of 05:36, 19 July 2011
| SNMP Protocol Operation | |
| GET | |
| SNMP Versions: | SNMPv1-3 |
|---|---|
| CLI Utility: | snmptrap |
| Protocol List: | |
A TRAP is a one-way communication, and is one of two types of notifications that can be delivered over SNMP. An entity that receives a TRAP does not acknowledge that it has received it (like snmptrapd, and thus it is not possible for the sender to be assured that the TRAP successfully made it to the destination. Because of this, the usage of INFORMs are recommended instead.
TRAP Versions
SNMPv1 actually had a more complex TRAP definition that included a number of parameters.
In SNMPv2c, the TRAPv2 PDU was defined which is significantly simpler and matches the on-the-wire format of the other protocol operations.
