Controllerless Networks

Reply
New Contributor
Posts: 3
Registered: ‎02-07-2014

AP135 in reboot loop with any IAP images

[ Edited ]

Hello

 

I'm fiddling with an AP135 that I'm trying to get to work.

 

Unfortunately, I *think* it might be a case of Flash being corrupted/Defect, and I'd like to have a second opinion before chucking it.

 

 

 

After trying 5-6 various IAP images from the download site, I always get the same state/result

 

Ex:

 

Upgrade with latest IAP image:

 

apboot> upgrade os 192.168.0.10:ArubaInstant_Cassiopeia_6.3.1.2-4.0.0.3_41784
eth1: up, 100 Mb/s, full duplex
Using eth1 device
TFTP from server 192.168.0.10; our IP address is 192.168.0.111
Filename 'ArubaInstant_Cassiopeia_6.3.1.2-4.0.0.3_41784'.
Load address: 0x2000000
Loading: #################################################################
################################
done
Bytes transferred = 6308284 (6041bc hex)

Image is signed; verifying checksum... passed
Signer Cert OK
Policy Cert OK
RSA signature verified.
Erasing flash sector @ 0xf8100000....................................................................................................done
Erased 97 sectors
Copying to flash...
Writing ..................................................................................

 

 

No error pertaining to device type/model, so right image.

Image transfer is successful, Certs are OK, Checksum OK, Sig OK... no problems on the TFTP transfer.

 

 

AP then reboots after writing:

 

APBoot 1.2.5.0 (build 27650)
Built: 2011-03-30 at 13:34:38

Model: AP-13x
CPU: 88F6560 A0 (DDR3)
Clock: CPU 1600MHz, L2 533MHz, SysClock 533MHz, TClock 200MHz
DRAM: 256MB
POST1: passed
Flash: 16 MB
Power: 802.3af POE
LAN: done
PHY: done
PEX 0: RC, link up, x1
bus.dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
00.00 00 11ab 6560 00005 02 f1000000 00000000 00000000 00000000
00.01 00 168c 0030 00002 01 90000000 00000000 00000000 00000000
PEX 1: RC, link up, x1
bus.dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
01.00 00 11ab 6500 00005 02 f1000000 00000000 00000000 00000000
01.01 00 168c 0030 00002 01 94000000 00000000 00000000 00000000
Net: eth0, eth1
Radio: ar9390#0, ar9390#1

Hit <Enter> to stop autoboot: 0
Checking image @ 0xf8100000
Copying image from 0xf8100000

Image is signed; verifying checksum... failed! 0xfa3b7d00
Checking image @ 0xf8800000
Invalid image format version: 0xc
eth0: down
eth1: up, 100 Mb/s, full duplex
DHCP broadcast 1
DHCP IP address: 192.168.0.111
DHCP subnet mask: 255.255.255.0
DHCP def gateway: 192.168.0.1
DHCP DNS server: 8.8.8.8
DHCP DNS domain: jumpspace.ca
ADP multicast 1

Abort
apboot>

 

 

Image checksum failure and reboot loop starting.

 

 

Anything more to do before declaring it Dead as a Doorstop?

 

 

 

Moderator
Posts: 681
Registered: ‎04-16-2009

Re: AP135 in reboot loop with any IAP images

Is this an IAP-135 or is it an AP-135 you are trying to load IAP code onto?    The only visual indication is a white sticker on the back of the AP that would say "IAP-135-US".

New Contributor
Posts: 3
Registered: ‎02-07-2014

Re: AP135 in reboot loop with any IAP images

Ha, there's the reason then...  I thought I did my homework, seems like I missed something

 

the sticket says "AP-135"... 

 

Any ways to make it into an Instant AP, or are they hard-locked?

Moderator
Posts: 681
Registered: ‎04-16-2009

Re: AP135 in reboot loop with any IAP images

A controller-based AP, like the AP-135,  cannot be converted to an IAP.

 

An IAP, however, can run as either an IAP or managed by a controller.

New Contributor
Posts: 3
Registered: ‎02-07-2014

Re: AP135 in reboot loop with any IAP images

Oh well, I guess I'll swap it for another one in our lab

 

Thanks for the info!

Search Airheads
Showing results for 
Search instead for 
Did you mean: