Analysis

Use the following checklist to check for traps not forwarded by trap forwarder daemon:
  1. Is the target address correctly configured in the TRAPFWD.CONF file?

    If the target is designated by a host name, check the trapfwd trace to determine whether the hostname was correctly resolved to an IP address. If the target is designated by an IPv6 colon-hexadecimal address, then your TCP/IP stack must be running with IPv6 support. If the stack is not running with IPv6 support, then the trap forwarder daemon cannot forward traps to IPv6 listener addresses.

  2. Is the trap being received at the trap forwarder daemon?

    If trapfwd traces indicate the trap is not being received at the trapfwd daemon, examine traces from the SNMP agent sending the trap. Determine whether the SNMP agent did send the trap.

  3. Are there network problems between the trap forward daemon and the target client?

    By issuing an SNMP GET request at the target client to the SNMP agent on the same host as the trap forward daemon, you can determine whether UDP packets are correctly reaching the client.

  4. Are the UDP packets being discarded due to congestion at the TCP/IP stack?

    If the trapfwd trace indicates that the trap is correctly being sent from the trap forwarder daemon to the target client, but the trap is not being received, consider setting NOUDPQueuelimit on the UDPCONFIG statement. This is used to specify that UDP should not have a queue limit and would prevent traps from being lost due to congestion.

If the above analysis does not correct the problem, the following documentation should be gathered and the IBM® Software Support Center should be contacted:
  • UDP packet trace on the TCP/IP stacks where the originating SNMP agent, the trap forwarder daemon, and the target client are running.
Parent topic: Traps not forwarded by trap forwarder daemon