I did a software update from Airwave 7.6.2 to 7.7.14 and we use IAP135 with software 184.108.40.206.
In the past we had the bug that it was not possible to reboot one single IAP in a cluster via Airwave.
When we tested new software I think it was possible to do this.
But now with the versions above it is again not working.
Is there any trick or is it again a bug?
Thank you very much!
It should work,
I tested with 8.0.5 and worked :)
thank you for the response.
But no, it is not working :-)
My IAPs are in managed mode, but to be sure I also set this option in the AMP setup.
It is also not working.
The funny fact is:
I click the "reboot" button.
The IAP is shown in the list on Airwave as "Down" and "Rebooting"
It comes back online with the same uptime as before (3 days)
My icmp is running completely well the whole time.
Anything else I can check here?
The reboot is not working due to an issue in the 220.127.116.11 firmware. Please contact support so see about getting an image to upgrade to a 18.104.22.168 build to get the single IAP reboot feature to work.
A quick test by the QA team has confirmed that it works on firmware image: 22.214.171.124-126.96.36.199 (available under the early availability folder: http://support.arubanetworks.com/DownloadSoftware/tabid/75/DMXModule/510/Default.aspx?EntryId=15809)
You are right, with 188.8.131.52 it is working again.
I am still seeing this with Airwave 8.0.5 and IAP 184.108.40.206
A few things to check:
1) AMP Setup -> Allow reboot when AP in monitor only mode
2) Are you using IGC?
2b) If using IGC, then reboot option needs to be performed from device list -> modify devices drop down -> reboot option
3) Do the device logs show the reboot attempt? Any failure message output? (/var/log/ap/<ap_id>)
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2020 Hewlett Packard Enterprise Development LPAll Rights Reserved.