Wireless Access

Hi all, got a 105 not attaching to a controller, its brand new. Just done 3 others and this one sits at "Running ADP..." and then after a few minutes reboots. Tried manually inputting our controller IP. Any ideas? Its picked up the correct firmware, just won't register.

Thanks.

You might want to publish the boot log for us to see.

Attached:smileyhappy:

Attachment(s)

putty.zip   2 KB 1 version

Are you using the same port as the other APs?  Are you sure it's getting an IP address? 

If you are sure it's getting an address and it's on the same VLAN as the other APs, purge it and see if it comes back up.  To do that, hit the Enter key when prompted during the boot, then type "purge".  After that finishes, type "save".  Now reboot the AP and see if it connects.

If it doesn't, like Colin said, post the boot log and let us see where it is breaking down.

Tried a purge, really odd, all the others worked fine, I've done hundreds of these!

What is the AP using to find the controller?

Like Olino says, stop it at apboot and type dhcp.  Send us that output.

It has the correct IP for our network and I can ping it from my workstation.

Yes, but what is that access point using to discover the controller?

Well it hangs on Running ADP so I assume its doing that. Is there a way I can hard code it, should'nt need to do this as I've just done a load of others. Thanks. 

At the apboot> prompt type "setenv master <ip address of controller>" and then type "save".

That will not deal with the underlying issue, however, which is that the AP cannot find the controller using a standard discovery method.  You might have to troubleshoot that, as well.

That sorted it, dunno why ADP did'nt work, all the other APs I just did were fine. Plugged it into my little A200 test system and that was ok (older firmware though). Its now all ready to provision so I might default it and try again. Ta for all help.

This is a great time to promote the video in the post here:  http://community.arubanetworks.com/t5/Community-Knowledge-Base/Aruba-Controller-and-AP-Troubleshooting-Part-1/ta-p/18988

Ok having it worked ok on our test A200, I then plugged it back into the original network in office. Did'nt work, hard coded the controller, fine. I then done a purgeenv, then save, the purgeenv and reset. Then factory_reset, save, then factory_reset then reset to be sure!!!! It has come up ok and attached ok, so not sure what happened but its fine now! The servername=aruba_master is back and still works.

Try this ,

Break the boot sequence on the AP-105 then set the IP address for that AP manually

ap> setenv ipaddr < IP Address for the AP>
ap> setenv subnetmask <subnetmask>
ap> setenv gatewayip <gateway ip>

ap> setenv serverip <Master Controller IP Address>
ap> setenv master <Master Controller IP Address>

ap>save

ap>reset

The command for the network mask

is netmask x.x.x.x

The

subnetmask x.x.x.x is incorrect... i just tried doing that and that didnt work... but netmask x.x.x.x does work thats the correct command.

Cheers