Hey everyone,
Even though Critical Path configuration Iāve setup seems to show correctly (info > path outages), Iām not getting the āpathOutageā event only the individual nodeDown events.
Iāve setup the Foreign Parent ID on each node in order for to be shown on the path outages screen. The Parent ID is in a separate provisioning request so I provided the name to that as well.
Also, Iāve set pathOutageEnabled=ātrueā in poller-configuration.xml and issued a pollerd restart request then restarted openNMS completely when it didnāt seem to do anything.
From what Iāve read in the docs, the nodeDown events should still be generated but they should have additional āeventReasonā parameters along with the seperate āpathOutageā event.
Update: nodeDown event description does state āAll interfaces on node x.x.x.x are down because of the following condition: pathOutageā but still donāt see the pathOutage event.
Prior to use the provisioning method, Iād also setup the Critical Paths manually through Notifications > Configure Path Outages and the Primary Interface IP but this didnāt seem to work either.
Currently running Horizon 24.1.3.
In case it matters, Iāve been testing the outage by blackholing the routes on the openNMS server itself rather than ākillingā my real network, for example:
ip route add blackhole x.x.x.x
Would anyone be able fill me in on any other configuration I may have missed?
Thanks
Derek