Aruba Wireless: Difference between revisions
(Created page with "Source: https://blog.theitrebel.com/2020/04/28/two-simple-words/ # Campus AP Keeps Rebooting / Upgrade Failed If a Campus AP keeps rebooting, and its serial console output shows: `SAPD: Reboot after image upgrade failed: 65280` Interrupt the AP boot and execute: <code> apboot> osinfo Partition 0 does not contain a valid OS image Partition 1: image type: 0 machine type: 40 size: 7211308 version: 6.4.4.0-wave2 build string: ArubaOS version 6....") |
No edit summary |
||
Line 5: | Line 5: | ||
If a Campus AP keeps rebooting, and its serial console output shows: | If a Campus AP keeps rebooting, and its serial console output shows: | ||
<code>SAPD: Reboot after image upgrade failed: 65280</code> | |||
Interrupt the AP boot and execute: | Interrupt the AP boot and execute: |
Revision as of 01:02, 11 November 2023
Source: https://blog.theitrebel.com/2020/04/28/two-simple-words/
- Campus AP Keeps Rebooting / Upgrade Failed
If a Campus AP keeps rebooting, and its serial console output shows:
SAPD: Reboot after image upgrade failed: 65280
Interrupt the AP boot and execute:
apboot> osinfo
Partition 0 does not contain a valid OS image
Partition 1:
image type: 0
machine type: 40
size: 7211308
version: 6.4.4.0-wave2
build string: ArubaOS version 6.4.4.0-wave2 for 32x (p4build@cyprus) (gcc version 4.6.3 20120201 (prerelease) (Linaro GCC 4.6-2012.02) ) #49847 SMP Thu Apr 30 14:49:32 PDT 2015
flags: preserve factory
oem: aruba
Image is signed; verifying checksum... passed
Signer Cert OK
Policy Cert OK
RSA signature verified.
This means the problem is the old 6.4.4.0 firmware. You need to clear it:
apboot> clear all
Checking OS image and flags
Invalid image format version: 0x0
Continuing with OS clear
512 bytes written to volume aos0
Erasing flash sector @ 0x3a0000...OK
Device 0: nand0... is now current device
Erasing UBIFS ...OK
Remove UBI volume ubifs (id 0)
Creating dynamic volume ubifs of size 63361024
Device 1: nand1... is now current device
Now tell the AP to boot and it should find mama (the Master):
apboot> boot