Wireless Access

Hi,

Just received a used AP125, used factory_reset to do its thing.

It's just sitting onthe bench, with Putty attached to the Console interface. It's just searching for a BOOTP device by the look of it, over and over again (see extract below).

But the question is: Every now and again it reboots the OS. Is this by design, as in a watchdog reset because it can't boot? Or does the AP have a fault?

Thanks

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2014.08.01 13:10:35 =~=~=~=~=~=~=~=~=~=~=~=


APBoot 1.0.8.3 (build 20343)
Built: 2008-12-27 at 17:03:46

Model: AP-12x
CPU:   OCTEON CN50XX-SCP revision: 1
Clock: 500 MHz, DDR clock: 333 MHz (666 Mhz data rate)
Power: DC
POST1: mem 0 mem 1 mem 2 mem 3 passed
POST2: mem 0 mem 1 mem 2 mem 3 passed
DRAM:  64 MB
Flash: 16 MB
Clear: done
BIST:  passed
PCI:   PCI 32-bit; scanning bus 0 ...
       dev fn venID devID class  rev    MBAR0    MBAR1    MBAR2    MBAR3
       03  00  168c  ff1d 00002   01 80000000 00000000 00000000 00000000
       04  00  168c  ff1d 00002   01 80010000 00000000 00000000 00000000
Net:   en0, en1
Radio: ar9160#0, ar9160#1

Hit <Enter> to stop autoboot:  2  1  0
Checking image @ 0xbed00000
Invalid image format version: 0xffffffff
Checking image @ 0xbf500000
Invalid image format version: 0xffffffff
en0:Down   1Gbs Half duplex, (port  1)
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5

Retry count exceeded; starting again
en1:Down   1Gbs Half duplex, (port  0)
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5

Retry count exceeded; starting again
en0: Down  10Mbs Half duplex, (port  1)
BOOTP broadcast 1
en0: Down   1Gbs Half duplex, (port  1)
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5

Retry count exceeded; starting again
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5

can you enter in the boot and run this

clear os

then  issue

reset

How does the AP finds the Controller? by DNS? static?

Cheers

Carlos

Hav

---

@NightShade1 wrote:

can you enter in the boot and run this

clear os

then  issue

reset

How does the AP finds the Controller? by DNS? static?

Cheers

Carlos

 

Thanks for the suggestions.

Have tried this.

 

Also tried method shown here:

 

http://geekbuddy.blogspot.com.au/2011/12/how-to-reset-aruba-networks-ap105-to.html

 

 Am still testing, but it looks like it's still rebooting. Will keep testing.

 

---

Hello

You need to investigate if you got a controller

You cannot use the AP 125 without a controller.

When you find out the controller and know the ip address of it and have access to it then we can continue to make this work

We need to know ifyou got licenses  and all that.

So the first step would be

1-Find the controller

2-Get access to it

Cheers

Carlos

sir, how to find the controller?

---

@chukang wrote:

sir, how to find the controller?

---

please start a new thread for a new question. i also see you started a thread about an instant AP, if that is related to this one, please stick to that thread and let this one rest.

---

@tsd25108 wrote:
First question, do you have a mobility controller?

---

Thanks for the reply.

This AP have just been factory reset, is sitting on bench not connected to anything but Console. Not sure if we have such a controller, and if we did I would not have access.

Cheers,

Hi,

the AP isn't booting, because there is valid OS image in both flash 1 and 2.

The AP checked that, you can see it in your console output.

Checking image @ 0xbed00000
Invalid image format version: 0xffffffff
Checking image @ 0xbf500000
Invalid image format version: 0xffffffff

Regards,

Thomas

That will help you:

1.) Download the APBoot-Image from Aruba Networks

Download Software -> AP Boot Image -> AP-12x

filename: ap12x-1.0.0.9-18209.ari

(If you are not able to download it, ask Aruba TAC if you can get it, I am not sure if I am allowed to give it to you.)

2.) Place the file into a TFTP-Server (root-level)

3.) Connect to the AP-12x and via console

Connect an Cable to ETH0

4.) Boot the AP and stop the autoboot hitting ENTER.

5.) Request a DHCP-Paket manually 

apboot> dhcp

OR

set the ip addess manually

setenv ipaddr <addr>

setenv netmask <mask>

setenv gatewayip <gateway>

save

(You can test the connectivity to the TFTP-Server via a ping command after that.)

6.) Upgrade the boot image

apboot> upgrade boot <ip_tftp_server>:<filename>

e.g. apboot> upgrade boot 192.168.10.10:ap12x-1.0.0.9-18209.ari

7.) boot the ap

apboot> boot

I attached  the technical bulletin.

Regards,

Thomas

Attachment(s)

TECH BULLETIN 20080501-ap12x-apboot-final.pdf   134 KB 1 version

Thanks all for responses.

I have had the AP on the bench for a couple of days now. The rebooting of the OS happens every 7 or so pages of Putty log, so I'm assuming it's a by-design watchdog occurring because it's finding no servers.

So next I will connect it in the real world (Aruba 6000 / RADIUS), get it configured currectly, and see if it still reboots.

Regards,

Just to confirm - the AP has been running configured on its Aruba 6000 for a week no with no reboots.

So it would seem that the repeating OS reboot is by design, or a bug that only appears when the AP is not configured and working as expected.

correct, that is by design.  If the AP cannot find a controller it will continually reboot and try again.  Similarly, it it does not get an ip address (necessary to find a controller), it will just reboot over and over.