You might try changing the no longer true reset condition to be explicitly a "WAP status is equal to UP"
I find that sometimes the automatic resets get a little iffy. I've never really poked inside the system to see if the WAP's are persistent objects, and dont have a wlc to check against, but another idea might be that when the LAP joins the controller solarwinds doesn't correlate the new "instance" of it to the old one, instead it might be adding it as if it were a completely new AP. If that were the case things would get tricky. I guess the easiest way to verify that is look at the end of the url on the AP page when it is up, should be like WLTAP:xxxx and then disconnect it, give some time to let solarwinds notice that it is gone, after your alert triggers reconnect it and see if that wltap number is the same as it was before. If the number hasn't changed then things shouldn't be too hard to sort out.
Loop1 Systems: SolarWinds Training and Professional Services
First, thanks for your help .
I’ve then tried multiple things:
The ID is changing only when the AP is moving from a WLC to another e.g.
On WLC#1 the ID is 111
When the same AP is on WLC#2 the ID is 222
This sounds quite normal as SolarWinds is gathering data from the WLC. So if the WLC differ the ID won’t be the same...
When the same AP will come back to the WLC #1 the ID remain the same original ID (111)
Strange things even if the APs don’t move from a WLC to another the reset condition isn’t working.
So the ID is probably not the root cause of my issue.
(to execute this test I’ve removed failover configuration on the test AP)
I’ve changed the reset condition to "WAP status is equal to UP"
It’s also not working.
I’ve also tried to change the trigger condition to
if WAP ID = 111
if WAP status is not equal to UP
and do the same reset condition “reversed”:
if WAP ID = 111
if WAP status is equal to UP
Again the reset condition failed during the multiple tests executed.
Strange things I’ve clicked on the message (generated from the alert) in the event log and an error popped:
Unexpected Website Error
Object WLAP:111 was not found in the database.
(The alert NPM message is a link to the object web-page)
When the AP is not associated to the WLC the object is removed from the database.
When the AP comebacks, as said it comes with the same ID and the URL is reachable without any error (by clicking on the same alert message) as the ID remain the same...
So it look like Solar Winds is removing the object from its database when the AP is no longer on the WLC and at this time the reset condition is not checked anymore (as the server can’t find the object on its database and then an error may occur) … ?
Did you get this working? I have a similar experience where the Alert triggers when I unplug the test AP it changes to Unknown state, but it doesn't change to anything else. However it does clear the alert when I plug it back in so I guess I am making some progress.
I did remove the RemoveDissappeared check from Advanced Configuration to see if that would make a difference, and it does keep the alert now, but just as Unknown state.