Anticipates: agent-addr xxLP
SNMPv1-Trap message formatEdit
The SNMPv1-Trap message, which is also called SNMPv1 Trap PDU format, consists of enterprise, agent-addr, generic-trap, specific-trap, time-stamp and variable-bindings. The whole SNMPv1-Trap message format is defined in RFC1157, and it is shown in figure 1.</p>
Figure 1: the SNMPv1-Trap message format.
Explanations are given as follows.
|enterprise||Sequence of Integer||Variable||This field is an object identifier for a group. It is used to indicate the type of object that generates the trap.|
|agent-addr||NetworkAddress||4||It provides the network address of the managed object that generates the trap. And it can be used to specify the preferred address in case of multihomed host.|
|generic-trap||Integer||4||The generic-trap is used to indicate one of predefined-generic trap types. Its value is a number of 4 bypes long.|
|specific-trap||Integer||4||The generic-trap is used to specify an implementation-specific trap types. Its value is a number of 4 bypes long.|
|time-stamp||TimeTicks||4||The value of time-stamp indicates the amount of time between the generation of the trap and the element which sends the Trap PDU message last rebooted.|
|variable-bindings||Variable||Variable||This field consists of a set of name-value pairs. Each pair binds associates a particular object instance with its current value.|
Links to other slides:
- The definition of SNMPv1 can be found in xxU8 Protocol: SNMP.
- If you want to know the difference between SNMPv1-trap and SNMPv2-trap, you can read following slide xxQK SNMPv2-Trap.
- The general SNMP message format can be found in xxZ6 SNMP message format.