Forum Discussion

Seth's avatar
3 years ago

Internet link down monitoring

Hi Team,

We have three different internet connections and need to setup alerting of any Primary or secondary internet connection link goes down. we're using Netgear Router, could someone check and advise on this

Thanks in Advance !

 

 

5 Replies

  • Anonymous's avatar
    Anonymous

    I may be missing the picture here, but if SNMP is enabled on the router and you're monitoring it, you'll get interface down alerts. 

  • As per what Stuart said. It depends on how your router is set up. I wouldn't think all your internet connections are on the same router though? If you don't have access to all the devices/interfaces your internet connections are set up on, you would probably need some way to monitor the IP addresses of each of the interfaces that those connections are on. It would be great if you could let us know how your 3 internet connections are set up. Ideally you would have all routers that have those 3 interfaces that connect to the internet reachable and set up in LM.

  • Anonymous's avatar
    Anonymous

    Right. If your interfaces are on separate devices or act as a single logical unit, you would use Service Insight to setup the service.

  • Here is an example of what we've done comparable to this for each of our datacenters in Service Insights (this one shows link health for ALL, but we also have them broken out by DC):

    It's primarily captured by naming conventions on the 'ifAlias/ifDescr' of the interfaces (which we needed to add to the _wildalias_ of the interfaces -- It's frustrating that we can't filter by _instance_ properties in this case, which necessitates us making kinda ridiculously long wildaliases, just so we can dynamically keep these services up to date).

    In summary, if we have 6 links out of a given datacenter (2 to each of the other datacenters), then not only can we have severity-based alerting on % of links available, but we can also calculate interface utilization as a function of the _newly reduced_ capacity, and alert on that seperately.

    One could _theoretically_ reproduce this in a datasource itself using batchscript data collection -- it was just more convenient for us to do it using Service Insights (which can certainly be a little pricey - I've found a way to only create a 'service' for each datacenter though, and have multiple service datasources aligned with each service).

  • Anonymous's avatar
    Anonymous
    20 hours ago, Austin Culbertson said:

    It's frustrating that we can't filter by _instance_ properties in this case, which necessitates us making kinda ridiculously long wildaliases, just so we can dynamically keep these services up to date).

    Preach.