Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
25.1.2
-
Security Level: Default (Default Security Scheme)
-
Horizon 2020 - April 15th, Horizon 2020 - April 29th, Horizon 2020 - May 13
Description
Provisiond accepts node definitions with two primary tagged snmp interfaces.
<node node-label="test" foreign-id="test"> <interface ip-addr="192.168.0.10" snmp-primary="P"> <monitored-service service-name="ICMP"/> </interface> <interface ip-addr="62.209.55.22" snmp-primary="P"> <monitored-service service-name="ICMP"/> <monitored-service service-name="SNMP"/> </interface> </node>
The result is, that OpenNMS does not collect any interface table metrics from this device without any hint why (or maybe I didn't find one).
We really have too many places why a collection can fail. See here: https://opennms.discourse.group/t/troubleshoot-performance-data-collection-from-snmp-agents/
It was not obvious to search in provisiond for a collection issue.
I think provisiond should complain about not valid node definitions and raise an alarm, so a administrator is able to notice it somehow.
But it should import all other nodes with correct definitions in that case.