We are starting to deploy Starlink in our enterprise as an active and backup solution connected to our SDWAN. How can SolarWinds be used to monitor the Starlink connection and provide the most benefit?
IN the past, I used NPM and NCM to monitor the Firewall / SDWAN / Router / (edge device) ports where the multiple internet links were, so I knew I had connection etc. Our SDWAN device managed the inputs from the Internet, and we could route data depending on what it was with QoS or a priority to ensure we had the correct data and connectivity, we alerted when a connection was offline, so port monitoring. I would also recommend the NCM for configuration backs so in case someone makes a change, and you need to roll back you can. In the case of an active backup, you will need to make sure your DNS is in a place reachable by your device managing your connections. Also Netpath will be useful when you do switch to monitor issues with connectivity.
If you are already using SolarWinds/NPM to monitor other connections, Starlink shouldn't be any different. One of our customers has a couple of Starlink connections so I'll ask the question to see if they're doing anything differently.
The tricky part when monitoring a backup link is to know it's really working. The interface might be up but is it ok past the next routing hop? One thing to do can be to alert if you have zero traffic on a backup WAN interface. There should always be some background noise (routing protocol and so). If no traffic at all, there is probably something wrong further up the line.
Oh man I am so keen to give this a try
Generally solarwinds is unhappy with >200ms latency between servers, I believe that starlink specs should allow pretty global coverage for polling engines under those conditions without the need of super expensive lines. I think there are organizations in which this would solve a problem or a cost.
Please talk to me about your experience if you've got use of some kit!
In terms of monitoring the starlink itself, I've no idea what's available currently, but I'd love to poke at one if I had one
I have to agree with the comments here. Netpath is underused in this space. It does a great job of describing visually what is happening with a link. Netflow is also useful - confirms your data usage and where it is going. Also - Have to agree with monitoring traffic - should never be zero traffic. SAM has a variety of things - the https uplink check can poke a site, and the script monitors can do a wide variety of things - depending largely on your level of expertise and security config.
We use BGP to control that the path is working on both lines..
