I submit you the following problem. I installed NMMi 9.20 on Redhat 5.6 ( Tikanga ) Installation is OK.
I loaded 3 MIBs provided by vendors.( Tools > Load/Unload MIBS ) Traps have been loaded. Message of System The following traps were already configured and have been updated: alarmListReBuild - .126.96.36.199.188.8.131.52.2.0.4 alarmCleared - .184.108.40.206.220.127.116.11.2.0.3 alarmChanged - .18.104.22.168.22.214.171.124.2.0.2 alarmNew - .126.96.36.199.188.8.131.52.2.0.1 Traps have been enabled ( Configuration > Incidents >SNMP Trap Configurations )
I performed successfully a test with nnmsnmpnotify.ovpl to issue a "basic" Trap.
Node have been configured. "Configuration Poll" is OK. "Communication settings" shows that everythink is OK ( Active SNMP Agent, SNMPv1 used, ports 161,162 etc ... )
Thanks to tcpdump on its interface, I can see that my Server receive several traps from the managed node. Example of received trap : User Datagram Protocol, Src Port: snmp (161), Dst Port: snmptrap (162) Simple Network Management Protocol version: version-1 (0) community: public data: trap (4) trap enterprise: 184.108.40.206.220.127.116.11.2 (iso.18.104.22.168.22.214.171.124) agent-addr: 172.25.52.40 (172.25.52.40) generic-trap: enterpriseSpecific (6) specific-trap: 3 time-stamp: 2079863314 variable-bindings: 8 items => that indicate an "alarmCleared" trap. ( alarmCleared : .126.96.36.199.188.8.131.52.2.0.3 )
Problem : ---------- Without interruption, Server receive flood of alarms from the Node. Unfortunately, no trap appareared on the node. ( Network Overview > the Node > Incidents window ) It looks like that traps are not distributed on node.
Questions : -------------- Have you an idea please ? How NNMi deal with received traps ? ( have we got any logs ??? )
Two things you could look at: * Incident Browsing -> SNMP Traps - do you see your traps received here? * Check out the nnmtrapdump.ovpl utility, to see more about received traps, and how they were handled.