11-14-2014 09:17 AM
We have an Airwave 8.0.0 that monitors iAP + VC and a trigger defined for AP down.
We had 3 AP's go down and Airwave did not create any Alarm thus did not trigger the email alert either.
We did a test from Airwave and we are able to receive emails from the email specified in the trigger thus this is not an issue.
One other question I had is :
"Given that the iAP doesn't have an Upstream Device - what is the behaviour when enabling - Send Alerts when Upstream Device is Down?"
11-14-2014 09:45 AM
The question is if your e-mail notification is actually working
You could run a test
And in the trigger do the following:
Lead Mobility Engineer @ Integration Partners
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
11-14-2014 10:53 AM
As mentioned in the firs post - We ran a test email from and to the same emails that are in the trigger and it worked.
11-19-2014 10:54 AM
For Aruba Instant APs, the ability to mark the device as down depends on the group basic -> aruba instant box -> https timeout.
By default, the HTTPS timeout is 5 minutes.
Then in the trigger definition (system -> triggers), you'll want to make sure you have 2 conditions in your down trigger event:
1) device type = AP
2) minutes down >= 5
This combination has worked for us in lab tests, and expect it to work for you as well. I do advise having the send alert for Thin APs when controller is down set to yes, as we have tested scenarios where only the VC AP goes down (at which point another AP should become the VC).
In regard to your question about upstream device down, this function only works if AirWave knows about the upstream devices. You should be getting the regular alerts regardless of the upstream device toggle when upstream device is unknown.
Senior QA Engineer - Network Services
Aruba Networks, a Hewlett Packard Enterprise Company