Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Set node to "Warning" when alerting on Interface

I have an alert (alerting on interface) that detects when a router fails over to the 4G backup by detecting if traffic is over a certain BPS on the 4G interface. This is usually caused by a primary WAN issue.

When this alert triggers, the primary WAN can still show as "Up" as the problem is usually downstream in the providers network. The 4G interface is obviously "Up" but in use. Overall the node is "Up" so the node itself doesn't go into warning state.

I have a dashboard that shows the status of all our routers but because the node that has failed over to 4G backup still shows as "Up" it never appears on the dashboard.

I've tried adding a "Set Custom Status" action in the trigger action to put the node into "Warning" state but this doesn't seem to work, possibly because I'm alerting on an interface and not a node.

Any thoughts how I can set the node to "Warning" even though it's polling as "Up"?

Find more posts tagged with

Accepted answers

All comments

mesverrum

I think you may be right about the custom status issue, you could rebuild your alert so it is targeting the node instead of the interface, i cant recall off hand if the condition builder GUI would let you do that or if you would have to do a custom alert with swql/sql.

leo18106

I just came across your post. I made a post yesterday with the same issue you are having. We are moving our edge locations from MPLS T1 circuits to SDWAN with the vast majority of them connected with broadband connections with a modem, so the actual interface doesn't go down when we lose Internet. I think I may have figured out a solution. I wont know until we have a location lose their Internet connection. But here is a link to my post below. I went with the opposite thought process as you. Instead of thinking about a "greater than" data threshold on the wireless backup, I thought about a "less than" data threshold on the main Internet connection. Maybe my post can help you out.

https://thwack.solarwinds.com/product-forums/network-performance-monitor-npm/f/forum/100732/edit-an-alert-for-unmanaged-interfaces

infspt

Awesome! Thanks for taking the time to reply.

JiriPsota

Since version 2022.4 you can use Enhanced interface status calculation. It means status is affected by critical and warning thresholds.

- set the thresholds on Interface edit page (Receive Interface Utilization)
- on Polling Settings page enable Enhanced for INTERFACE STATUS
- make sure Enhanced is also enabled for NODE STATUS
- make sure Interface is enabled on Node child status participation page

Now, when the utilization will be over limit, interface status will change to warning/critical and it will affect also Node status

infspt

Thanks for the suggestion. I'm aware of the feature and have all those options active.

The main problem is that a 4G interface doesn't have a fixed bandwidth as it's dependant on signal strength and other factors. Setting a percentage trigger for over 170 sites where the bandwidth can vary greatly isn't going to be workable I believe.

I'll have a further think about it and maybe something based on your suggestion might work.