A routing neighbor(a node) going down that is seen by different routers(also nodes) only to be shown as one alert

abdullah.khalid

The aim is to log a single ticket( in notes) against a WAN site being reported as down, in other simple rollup WAN site down as single alert.

Issue:

Currently a single routing neighbor going down shows as multiple alerts in the All Active Alerts resource

Current setup is alerting on routing neighbors in Orion Platform:

Possible solution:

I have a lead to setup and change the custom property of the node owning the IP address of the affected routing neighbor, this is to leverage to achieve the goal.

Implementation:

In trigger action section I am updating a custom property of the node owning the IP address of the affected routing neighbor

Stuck at:

Issue i am stuck here is the NeighborIP is not Node IP and i have to fetch this from NodeData table as interface addresses.

The limitation at play is the I am running an update SQL statement that further increases the challenge.

${SQL:SELECT 'Look the other way';

UPDATE  Nodes SET BGP_Peer_connect_issue_count = 1 where NodeID=${N=SwisEntity;M=NeighborIP}}

Possible statement could be like below but does not work.

${SQL:SELECT 'Look the other way';

UPDATE  Nodes SET BGP_Peer_connect_issue_count = 1 where NodeID=${ SQL:SELECT NodesData.NodeID FROM NodesData

left join NodeIPAddresses on NodesData.NodeID=NodeIPAddresses.NodeID

  where (NodeIPAddresses.IPAddress='${N=SwisEntity;M=NeighborIP}'}

abdullah.khalid

This is now solved !

Set trigger at advance SQL query, had to work from Nodes tables targeting the routing neighbor table in order to roll up alerts as sites.

SELECT Nodes.Caption, Nodes.NodeID FROM Nodes

join NodeIPAddresses ni on nodes.nodeid=ni.nodeid

join NPM_RoutingNeighbor_V RN on ni.IPAddress=RN.NeighborIP

WHERE (( (RN.OrionStatus = 2) OR (RN.IsDeleted = 1) )  and nodes.status <> 9 )

group by Nodes.Caption, Nodes.NodeID