07-17-2019 11:27 AM - edited 07-05-2021 10:43 AM
Was wondering if anybody can help me out. Having issues with 2 1562i APs.
The 1562i CAPWAP AP running 8.3.150.0 has the bug "Discovery response from MWAR ''running version 0.0.0.0 is rejected." so it won't join the other 1562i Mobility Express AP. Interestingly the Mobility Express AP doesn't have a backup image so it does report that missing backup image as version 0.0.0.0, so maybe that's the issue?
So to fix this I thought I would just update the software on the Mobility Express AP but it fails to upgrade it's software because it a single AP and doesn't have any subordinate AP to upgrade.
Any advise on how to get these APs fixed without climbing a pole to retrieve the master AP?
Thanks
07-17-2019 03:12 PM
Any way to force a software update on a 1562i Mobility Express AP when changing ap-type from capwap to ME? This AP is mobility express capable so it says update not needed changing type to ME when the command is issued "ap-type mobility-express tftp://TFTP Server/ap3g3". Any help would be appreciated.
Thanks
07-17-2019 03:52 PM
So lets convert one of the APs to ME and shut the current controller down... so I can upgrade off 8.3.150.0 to 8.8.125.0 which shouldn't have the "Discovery response from MWAR ''running version 0.0.0.0 is rejected." Bug
##archive download-sw /reload tftp://0.0.0.0/AIR-AP1560-K9-ME-8-8-125-0.tar
######################################################################## 100.0%
Image downloaded, writing to flash...
do PREDOWNLOAD, part2 is active part
Image signing verify success.
upgrade.sh: part to upgrade is part1
tar: write error: No space left on device
upgrade.sh: Command "tar -xf /tmp/part.tar -C /bootpart/part1" failed.
upgrade.sh: df /bootpart/part1
upgrade.sh: du -h /bootpart/part1
upgrade.sh: Writing image to disk...
sh: 1K-blocks: unknown operand
upgrade.sh: AP backup version: 8.8.125.0
do ACTIVATE, part2 is active part
upgrade.sh: activate part1, set BOOT to part1
upgrade.sh: AP primary version: 8.8.125.0
upgrade.sh: AP backup version: 8.3.150.0
Archive done.
upgrade: AP Rebooting: CLI triggered reboot(archive command)
oh my ... so flash is to small? Anybody have any suggestions, any would be appreciated, especially recommendations for AP vendors who put enough flash in their devices ....
07-18-2019 05:56 AM
07-18-2019 12:54 PM
Thanks rrudling,
I was able to find an image that fit and get the other APs up and running and then was able upgrade everything to 8.5.151.0 which at the moment has no problems. The original AP I believe has a hardware issue as it's now in a boot loop vomiting status messages for every single electron that passes through it in typical unix fashion, I have tried breaking in and stop the logging but i never get there before it reboots. I can stop at Uboot, so if you have any ideas on how to get a good image on this I would appreciate it
Thanks
07-18-2019 02:14 PM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide