Tuesday - last edited Tuesday
I have AP650 and AP460C's and it was hell doing the 10.7.2.0 up to 10.7.3.0, where you would update the AP, it went through the long process, and then it would go offline with the error message "Device Update Failed". You can Ping it, you can SSH into it, but it stays offline in the Interface. I dont recall how I fixed the issue, but things got better with 10.8.3.0.
I just went and updated three AP650's with the 10.8.4 and have the SAME EXACT issue I had with the 10.7.2.x updates, as explained above.
Extreme WHAT THE HECK IS GOING ON. Your Customers ARE NOT your Beta testers.
I SSH'd into each of them (because I can ping and SSH, even those they show offline in XIQ) and ran a reboot command, as well as reboot current and reboot backup and that did not fix the issue.
I might have got lucky using a paper clip pressing in the reset button for 30 seconds, letting it boot up - still showing as offline - then unplugging it from the network counting to 30 and plugging it back in... and in one case repeating the steps, and got ONE AP to now show in XIQ, but still have the "device update failed" message, a reboot from the XIQ interface clears that though.....
What is the OFFICIAL fix to this complete **** of a firmware update? Remember that version is for more than just the AP650, its also for a lot more including the AP460C's...
I await your - or anyone else's - feedback -. Regards, Jason,
PS: And DO NOT mark this as SPAM....Again....
Wednesday
First, I can understand how frustrating this can be. Now, I haven't encountered this issue, but I can suggest some things. Since you can SSH into the APs, what troubleshooting did you do? Did you run a show capwap client? Did you do a capwap ping to the Extreme servers? Did you check your firewalls to make sure all of the Extreme URLs are whitelisted? Did you check the status of AWS (XIQ is hosted in AWS)?
Wednesday
I upgrade 7 units. 2 of them gave me the same message Device Update Failed. I rebooted them. I applied the update. All was good.
Wednesday - last edited Wednesday
Thats almost 27% failure rate, thats unacceptable... if you had 700 AP's.... you would be in serious trouble, but were your AP's AP650(AH)'s? I SSH'd into them and issues the "reboot" command, they rebooted but would never come back online (only SSH'able).... even pulled the network cable and plugged back in, pulled network cable and different port, nothing.....
Thursday
Yes, mine at AP650 units.