The whole idea behind the status of "unplugged" is to not alert against them. This is a status used so that the interface doesnt get marked down when folks go home after work. I wouldnt create an alert based on unplugged. Also, this is best used only for ports with user devices on them that go home at night.
The thought behind keeping unplugged interfaces in SolarWinds is to keep an inventory of open ports vs used ports. Also, it is an easy way for our helpdesk to quickly identify when a user has accidentally unplugged their device from the network. I would just like to be able to acknowledge these alerts and not have them re-trigger.
1 of 1 people found this helpful
The alert re-trigger is something that is an underlying "feature" in the product. It can be changed with some modifications in the config files, however the maximum is 90 days.
A couple of observations:
1) I wouldn't be alerting on an unplugged interface, as it will likely stay in alert state for an extended time. When you acknowledge the alert, it will re-trigger after 10 days, so you'll be caught in a cycle.
2) Set your alert for "down" with a reset on "up". To protect against ports coming up without approval, once an interface alerts on down, and is expected, set this interface to admin down on the device itself. If you also set "status = shutdown" to your reset trigger, this will also clear the alert. you will need to set the port to "admin up" for anyone to use the port.
3) Unpluggable interfaces are generally set on interfaces that will go up and down and you do not wish to be alerted.