SNMPv1 Traps

SNMPv1 traps embed the Agent Address inside the SNMP trap PDU. The following table shows the format of an SNMPv1 trap, with the IP header forming the top section and the SNMP trap PDU forming the lower section.

SNMPv1 Trap Format

Version and other information

Source Address

Destination Address

PDU-Type: 4

Enterprise

Agent Address

Generic Trap Code

Specific Trap Code

Timestamp

PDU Variable Bindings

Because the Agent Address is embedded in the PDU rather than the header, usually the NAT router will not translate this value. You can enable NNMi to note the address in the header and ignore the Agent Address in the payload by doing the following:

  1. Edit the following file:

    • Windows: %NNM_PROPS%\nms-jboss.properties
    • UNIX: $NNM_PROPS/nms-jboss.properties
  2. Find the following line

    #!com.hp.nnm.trapd.useUdpHeaderIpAddress=false
  3. Change the value to true and remove the #! characters as shown below:

    com.hp.nnm.trapd.useUdpHeaderIpAddress=true
  4. Save the file; then restart NNMi.

The following diagram shows an example of an SNMPv1 trap where NNMi ignores the conflicting IP address fields.

SNMPv1 Example

Note NNMi provides the following related Custom Incident Attributes (CIAs):

  • cia.agentAddress—the IP address stored in the SNMPv1 trap data for the SNMP Agent that generated the trap.
  • cia.internalAddress—If static NAT is part of your network management domain, the NNMi administrator can configure this attribute to show the internal IP address that is mapped to the external management address of the selected incident's Source Node.

    The external management IP address (public address) must be mapped to this internal address (private address) using the Overlapping IP Address Mapping form. For more information, see the NNMi help.