Wireless Access

Reply
Occasional Contributor II

AP-135 not showing up as "un-provisioned"

This should be simple. I've got a 3600 and some AP135s new out of the box and trying to get things set up.

 

I have a DHCP pool enabled on the controller. I am consoling into the AP watching it boot up. It gets an IP address, ADP runs and gets the correct LMS IP. Everything from the standpoint of the AP looks good. However, it never shows up on the controller... not as up, not down, not in the list of unprovisioned. I can ping the AP from the controller and vice-versa. Both the controller and AP show 6.1.1.0 so it shouldn't be downloading an image.

 

Any ideas?

Guru Elite

Re: AP-135 not showing up as "un-provisioned"

Do you have licenses installed on that controller?  does the Unprovisioned AP have a Flag, saying why it is unprovisioned?



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Aruba Employee

Re: AP-135 not showing up as "un-provisioned"

Please run the following command from the CLI and post the output:

 

show ap database | include 135

Thanks,

Zach Jennings
Occasional Contributor II

Re: AP-135 not showing up as "un-provisioned"

Re: Licensing, yes - this is a 3600-64 actually.

 

show ap database | include 135 yields no results at all.... when I omit the pipe it just shows APs:0.

 

I have done nothing whatsoever to the original config other than adding the DHCP pool and a couple AP groups.

 

Thanks for the assistance, guys...

 

 

Occasional Contributor II

Re: AP-135 not showing up as "un-provisioned"

cjoseph: It's not showing up as unprovisioned... that's the problem. It's not showing up at all.

 

 

Aruba Employee

Re: AP-135 not showing up as "un-provisioned"

CPsec is enabled by default in ArubaOS 6.x . check whether the AP is the the campus whitelist. Did you add the ap to the campus whitelist?

 

In GUI

 

AP installation --->campus whitelist

 

Diasble CPSec and see whether the AP shows up.

Aruba Employee

Re: AP-135 not showing up as "un-provisioned"

What version of code is on your controller?  You will need a relatively new ArubaOS to support the AP-135.

 

Is there any messages in the system log (show log system all) about the AP not being recognized?

 

Is the AP continually rebooting?

Occasional Contributor II

Re: AP-135 not showing up as "un-provisioned"

Thanks for the continued help on this!

 

1) CPSec has been turned off but it did not help.

 

2) Code was 6.1.1.0 out of the  box. Should I upgrade? If so, to what?

 

3) As a matter of fact.... the AP IS rebooting. I hadn't noticed. It's doing it every 5 minutes or so. Here's what is reported in the log on the controller:

 

Nov 22 07:13:13  nanny[732]: <303022> <WARN> |AP d8:c7:c8:c0:c7:c8@10.201.255.25

4 nanny|  Reboot Reason: AP rebooted Fri Dec 31 16:04:19 PST 1999; SAPD: Unable

to contact switch. Called by sapd_hello_cb:4

Nov 22 07:17:58  nanny[732]: <303022> <WARN> |AP d8:c7:c8:c0:c7:c8@10.201.255.25

4 nanny|  Reboot Reason: AP rebooted Fri Dec 31 16:04:19 PST 1999; SAPD: Unable

to contact switch. Called by sapd_hello_cb:4

Nov 22 07:22:43  nanny[732]: <303022> <WARN> |AP d8:c7:c8:c0:c7:c8@10.201.255.25

4 nanny|  Reboot Reason: AP rebooted Fri Dec 31 16:04:19 PST 1999; SAPD: Unable

to contact switch. Called by sapd_hello_cb:4

Nov 22 07:27:28  nanny[732]: <303022> <WARN> |AP d8:c7:c8:c0:c7:c8@10.201.255.25

4 nanny|  Reboot Reason: AP rebooted Fri Dec 31 16:04:19 PST 1999; SAPD: Unable

to contact switch. Called by sapd_hello_cb:4

Nov 22 07:32:13  nanny[732]: <303022> <WARN> |AP d8:c7:c8:c0:c7:c8@10.201.255.25

4 nanny|  Reboot Reason: AP rebooted Fri Dec 31 16:04:19 PST 1999; SAPD: Unable

to contact switch. Called by sapd_hello_cb:4

 

Here's the reality check question - can APs terminate to a master, or do they have to terminate to a standalone or local? This is a master-local pair but before I got the local configured I just wanted to see if I could get an AP provisioned on the master. I am setting up the local now.

Aruba Employee

Re: AP-135 not showing up as "un-provisioned"

6.1 should be OK.

 

You can terminate APs on a master, as long as it is not a backup master in a redundant master design.

 

On the master, do a "show controller-ip".  On the AP, look at the master address.  Do they match?

Occasional Contributor II

Re: AP-135 not showing up as "un-provisioned"

I think I just answered my own question. Once I got the local online, the AP showed up right away and I was able to provision it. On to the next problem..... :)

 

Thanks again so much for the assistance on this!

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