Top_XX_Routing_Flaps.OrionReport

Hi zackm

Thank you for sharing.

I have had a play with your SQL and have found that the result is not quite the same as in "Top 10 Flapping Routes" resource for the interface. I have then added CIDR grouping and the output result is now identical. I guess CIDR grouping is necessary here but I just wanted to hear your view if possible. Without this grouping SQL picks up much more...

SELECT

  Nodes.NodeID 

,Nodes.Caption AS 'NODE'

,rtf.RouteDestination AS 'DEST'

,rtf.CIDR AS 'CIDR'

,COUNT(*) AS 'FLAPS'

FROM Solarwinds.dbo.Nodes

INNER JOIN Solarwinds.dbo.NPM_RoutingTable_Flap rtf ON rtf.NodeId = Nodes.NodeID

WHERE

  rtf.DateTime > DATEADD(HOUR,-168,GETDATE()) --7 Days

GROUP BY Nodes.NodeID, Nodes.Caption, rtf.RouteDestination, rtf.CIDR

  HAVING

    COUNT(*) >= 1 --to adjust threshold

ORDER BY Nodes.NodeID, COUNT(*) DESC

Thank You,

Alex

I don't have a lab to look at this in at the moment, but I would trust your input here. If it requires CIDR, then I can definitely update the report.

Has this been confirmed in earnest at this point, or is it just a theory?

I am running this report as a resource in my test lab and it does flag everything across the board, same as would standard flapping interfaces resource would do per interface. The benefits of using the above script is that it is actually monitoring entire infrastructure. So, I think to answer your question - in my environment I would be happy to roll this live pretty soon