Wireless Access

Hi all,

We recently received 13 new AP105's, but they all keep rebooting and don't show up in our W-3400 controller.

We already have 39 other AP105's that work without any problems, but when i connect any "new" AP105 to an existing PoE connection, it keeps rebooting.

I've attached the logfiles of the new rebooting AP and an existing working AP.

Can somebody please help me out with this problem?

Thanks in advance, kind regards.

Jeroen

Attachment(s)

130815 AP BOOT - A117 - WORKING.docx   15 KB 1 version

130815 AP BOOT - D108 - FAILING.docx   14 KB 1 version

You need to paste in the output of "show log system 50" on the controller while that is happening to get a better picture.

Can you please explain to me how to do that? I'm sorry i'm new to troubleshooting the controller.

You have to SSH into the controller and get into enable mode before executing "show log system 50"

I've included the logfile in the attachment, hope it helps...

Thanks, Jeroen

Attachment(s)

130815 W3400 Controller - show log system 50.docx   13 KB 1 version

• Did u check your AP-license? PEFNG-license?
• Are u working with control-plance security?
• You sure that no one use the address that been alocated to those ap's from the DHCP?

• I have 15 free AP and PEF licenses, these are newly activated in our W3400.
• I'm not working with control-plance security
• The IP adresses are unique in our network, no other appliances are using these IP's.

OK.

Take a look on this:

http://community.arubanetworks.com/t5/802-11n-and-802-11ac-Basics-RF/AP-105-sendbytes-error-bailout/td-p/65798

but before u doing it - just try to take one unit that is failing - connect console - stop in the begning (with enter key) and write

purge

clear os

saveenv
boot

and then let it boot and get the AOS - and check if it's up with no problems..i

OK, i did what u asked, but i still have the same problem...

In the attachment is the log.

Thanks for the reply btw.

Attachment(s)

130815 AP BOOT - D108 - Cleared OS.docx   13 KB 1 version

OK.it's was worth a shoot :) as written in the previous post

http://community.arubanetworks.com/t5/802-11n-and-802-11ac-Basics-RF/AP-105-sendbytes-error-bailout/td-p/65798

Output from the AP: error -bailout indicate a hardware failure moreover the AP  is not completing the boot process. We have process RMA for the APs.

With the same ap output,I recommend you to open a TAC.

Regards.

Me

Please read the attached field bulletin. Even if your SN is not in the list, it may have the problem; I've seen it at multiple customers this past month.

The following commands in order should reset the AP to bootable, however you will likely run into the same thing until you upgrade your code per the bulletin.     It may just help you from having to RMA them.

purgeenv

saveenv

factory_reset

saveenv

Attachment(s)

Field Bulletin AP1306-2 (AP-100 TPM).pdf   217 KB 1 version

My new APs are indeed from the SN mentioned in the bulletin.

I will try to upgrade the firmware of our controller and factory reset the AP afterwards.

I will post my results later, thanks for the help!

The new Access Points are working!

• I've updated the W3400 controller to ArubaOS: 6.2.0.2.
• Then I disconnected all the AP's from the PoE switch, causing them to restart.
• Then the new mac adresses were showing in the controller, provisioned the AP's, everything is working!

Thanks to all of you that contributed to this problem!