Analysis

In the case of SNMPv1 traps, the address from which the trap originated is encoded within the trap packet. A manager that needs the originating address should look into the SNMP packet to get the address.

If the address is 0.0.0.0, the most likely cause is that the trap originated at an IPv6 address. If the trap originated at the z/OS® SNMP Agent, see 0.0.0.0 address in traps from the SNMP agent.

In the case of SNMPv2 traps, the originating address is not encoded within the trap PDU. If a manager uses the address from which the trap packet is received, it would not be the originating address but the address at which the trap forwarder daemon is running. If the manager needs the originating address if SNMPv2 traps, the trap forwarder should be configured to append the originating address to the trap and the manager should be capable of reading the address from the end of the received trap packet. For more information about the format in which the address is appended, see the z/OS Communications Server: IP User's Guide and Commands.

Check to see whether the ADD_RECVFROM_INFO is specified correctly in the TRAPFWD.CONF file. If it is not specified, then add the option to the configuration file. Note, the receiving manager must be capable of processing the RECVFROM information at the end of the trap packet.