NNNMi 2023.05:

Hi,  Experts

customer came across strange issue - some ospfNbrStateChange traps from some nodes are not displayed in NNMi Incident''s browser.
After some investigations we narrowed down problem to the following:

 sending (simulating from NNMi) ospfNbrStateChange  traps from the same node with different router IP and Ndr IP addresses in the vabinds.

trap1:
/opt/OV/bin/nnmsnmpnotify.ovpl -v 1 localhost -a zl-rc0001-dr105.metro.mgt.local .1.3.6.1.2.1.14.16.2.2  \
.1.3.6.1.2.1.14.1.1 ipaddress 213.51.159.138 \
.1.3.6.1.2.1.14.10.1.1 ipaddress 213.51.160.143 \
.1.3.6.1.2.1.14.10.1.2 integer 0 \
.1.3.6.1.2.1.14.10.1.3 ipaddress 213.51.159.13 \
.1.3.6.1.2.1.14.10.1.6 integer 1

trap2:
/opt/OV/bin/nnmsnmpnotify.ovpl -v 2c localhost -a zl-rc0001-dr105.metro.mgt.local .1.3.6.1.2.1.14.16.2.2 \
.1.3.6.1.2.1.14.1.1 ipaddress 10.110.2.51 \
.1.3.6.1.2.1.14.10.1.1 ipaddress 172.19.22.102 \
.1.3.6.1.2.1.14.10.1.2 integer 0 \
.1.3.6.1.2.1.14.10.1.3 ipaddress 10.110.2.60 \
.1.3.6.1.2.1.14.10.1.6 integer 1

trap3 (no varbinds):
/opt/OV/bin/nnmsnmpnotify.ovpl -v 2c localhost -a _zl-rc0001-dr105.metro.mgt.local  .1.3.6.1.2.1.14.16.2.2

Trap2 and trap3 are received and displayed, trap1 is not  - even not seen in "nnmtrapdump.ovpl -t " output.
Incident's ospfNbrStateChange configuration is plain -  no enrichments, no suppressions. No filters in trapFilter.conf/nnmtrapd.conf.

How it could be? Why trap1 is dropped?  Can you reproduce it on your NNMI?
Seems it's related to IPs in the varbind. Could it be that some filter is hardcoded NNMi ovjboss? 

thank you in advance
Gedas

Tags: