Controllerless Networks

last person joined: 11 hours ago 

Instant Mode - the controllerless Wi-Fi solution that's easy to set up, is loaded with security and smarts, and won't break your budget
Expand all | Collapse all

Ariwave trigger for Down iAP - not working.

This thread has been viewed 4 times
  • 1.  Ariwave trigger for Down iAP - not working.

    Posted Nov 14, 2014 12:18 PM

    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?"



  • 2.  RE: Ariwave trigger for Down iAP - not working.

    Posted Nov 14, 2014 12:45 PM

    The question is if your e-mail notification is actually working 

    You could run a test 

    Screen Shot 2014-05-22 at 9.45.48 AM.png

    And in the trigger do the following:

    2014-11-14 12_44_39-AMP-SERVER.png

     

     



  • 3.  RE: Ariwave trigger for Down iAP - not working.

    Posted Nov 14, 2014 01:53 PM

    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.



  • 4.  RE: Ariwave trigger for Down iAP - not working.

    EMPLOYEE
    Posted Nov 19, 2014 01:54 PM

    For Aruba Instant APs, the ability to mark the device as down depends on the group basic -> aruba instant box -> https timeout.

     

    2014_11_19-129.jpg

     

    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

     

    2014_11_19-131.jpg

    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.