Not join AP controller

[athan1234]

Hi

I attempt to do join with the controller i get thois error

[Flavio Miranda]

Hi

 There is not enough information to tell you what might be wrong. Do you see any log on the WLC for this AP?

Which WLC do you have and which version is this WLC?

[athan1234]

I belive it is for the licenses . Licenses are now the focus. Is there a cli command that will delete the existing AP and release the licenses necessary to join the new AP?

[Flavio Miranda]

Licensing on WLC does not work like that. If you have license for 100 AP, you can get to 100 AP. If you disconnect 1 AP, then you have 100 license and you are using 99.

 So, either you have licensing for this AP or not. You dont need to remove anything.

 the logs on the WLC can help you. Go to Monitor page, Statiistics and AP join.

[Julio E. Moisa · Accepted solution]

Hi

If the primary controller is already configured into the access point, try configuring the next line

capwap ap mode local

Please remember the AP must obtain an IP address (static or via DHCP)

capwap ap ip xxxx
capwap ap controller o primary-base

https://www.cisco.com/c/en/us/td/docs/wireless/access_point/wave2-ap/command-reference/8-7/b-cisco-wave2-ap-cr/capwap_commands.pdf

This process could take long because the AP will be rebooting.

@Flavio Miranda mentioned you could also check the license availability into the WLC.

Regards.

[athan1234]

Dear Julio I configured a capwap tunnel, and from AP to I can ping the controller. The issue is that I am the only one with cli control.

I am unable to see the AP join. Any thoughts? any troubleshooting from the controller or AP to address the issue

[Daniel Ordóñez Flores]

Hi @athan1234 

Please share the complete output of your AP and fromt WLC side turn on "debug capawap errors" comands and share with us too

[athan1234]

The ap is join  @Julio E. Moisa  for your steps

[Daniel Ordóñez Flores]

Ok, it a local deployment or the AP is in other location thant you WLC?

[athan1234]

AP was in local mode while the rest of the network was using flex connect; I switched to flex connect, and everything is working now.

[Julio E. Moisa]

Great! flexconnect is used when the APs are located remotely. Good to know it is working now, have a good day!. 

[athan1234]

Thanks @Flavio Miranda  and @Daniel Ordóñez Flores  and @Julio E. Moisa  for your support

[athan1234]

Hello, I have a question about this customer's use of Flex Connect.
When the customer lost connectivity, I could not see his SSID all of them AP are configuring with Flex Connect configured without a VLAN local.
I apologize for my flex connect theory.
I want to configure a local vlan for my client ;I guess is the best way to leverage the flex connect potencial , he will be able to connect locally to those SSIDs. isent´ìt ?

I have some doubt to set up  i would like to start oonly in one AP

The first step will be to configure VLAN 110. My customer has vlan management 110.Right?

The next step SSID with ID 2 is enabled the FlexConnect Local Switching option on the following screen. And because the other SSID does not have this local flexconnect enabled, what would happen if the other SSID's enable option was selected? Would the rest of the APs or clients experience a cut, or something else? I want to include the SSID as well as the local flex connection.

The second query is whether I can enter a vlan ID, for example 15, in the vlan ID field.

[Daniel Ordóñez Flores]

Hi @athan1234 

Sorry I wanna try to get this right. Let me ask you something

1. What do you mean when you say "When the client lost connectivity? The APs lost connectivity with the WLC?

2. Where do you stop to see the SSIDs?

If you can switch to spanish, is possible to get a better understanding