How do a monitor a node that has two routes?

We monitor a node that routed via a firewall using an internet link. If the link, or firewall, becomes unavailable the backup link takes over, and the traffic is routed through our backup firewall using another internet link.

When the primary link is active SolarWinds can monitor the link fine, however when the primary link is is not available and the traffic is routed over the secondary, backup link, SolarWinds fails to monitor the node i.e. fails to ping.

Is there a way to monitor the node (Windows server) with SolarWinds so that if the primary link is unavailable SolarWinds will use the backup route and continue to monitor it?

Find more posts tagged with

route

ncm

monitoring

Accepted answers

All comments

KMSigma.SWI

Depends on the IP you have used for said node.

If it's routable, then the platform will get to it in the way you'd expect. We've most often seen this when a specific node has multiple IPs (like a firewall or a router) and you are monitoring from the side where you don't have a good route from the SolarWinds server to that IP.

mesverrum

Right, there is nothing special about how Orion specifically does routing. It just lives in Windows on top of the native TCP IP stack the same as any other Windows server. If you can't route from Orion to a give destination then you just need to figure out why any generic server wouldn't route that path. If you are doing hostname based monitoring then one thing that could be jamming you up could be delays in DNS getting updated, but you'll find that the same problems likely happen for any server on your subnet trying to reach that same destination.

ascoyne

Thanks @KMSigma.SWI and @mesverrum I will do some more digging into our networking. I will feedback the outcome. I appreciate you taking the time to reply.

KMSigma.SWI

I got in the habit of setting up loopback interfaces on the "inside" for routers and using that IP for polling.