AP´s not Join

[athan1234]

Hello everyone.

This is the case I have. A few APs were configured to connect to the controller. I notice that the APs are not joining.

I am tryng to troubleshoot, but I am unable to find any solutions to identify the problem.

My coworker configured the capwap  tunnel i requested to him the set up . I dont have access to AP they are on the customer on the ceeliing , tomorrow maybe  i am going to the customer  if i dont get to join before

/////

The ip are fixed 

The model are air-ap1852

I dont know the firmware

////////////////////////
24:36:da:2e:96:40 N A APZALF5_39 10.54.10.239 Not Joined
252 10.54.10.252 Not Joined
F5_13 10.54.10.213 Not Joined
32 10.54.10.232 Not Joined

///////

>show ap join stats detailed 24:36:da:2e:96:40

Sync phase statistics
- Time at sync request received............................ Not applicable
- Time at sync completed................................... Not applicable

Discovery phase statistics
- Discovery requests received.............................. 211
- Successful discovery responses sent...................... 211
- Unsuccessful discovery request processing................ 0
- Reason for last unsuccessful discovery attempt........... Not applicable
- Time at last successful discovery attempt................ Aug 22 17:16:17.466
- Time at last unsuccessful discovery attempt.............. Not applicable

Join phase statistics
- Join requests received................................... 0
- Successful join responses sent........................... 0
- Unsuccessful join request processing..................... 0
- Reason for last unsuccessful join attempt................ Not applicable
- Time at last successful join attempt..................... Not applicable
- Time at last unsuccessful join attempt................... Not applicable

Configuration phase statistics

--More-- or (q)uit
- Configuration requests received.......................... 0
- Successful configuration responses sent.................. 0
- Unsuccessful configuration request processing............ 0
- Reason for last unsuccessful configuration attempt....... Not applicable
- Time at last successful configuration attempt............ Not applicable
- Time at last unsuccessful configuration attempt.......... Not applicable

Last AP message decryption failure details
- Reason for last message decryption failure............... Not applicable

Last AP disconnect details
- Reason for last AP connection failure.................... Not applicable
- Last AP disconnect reason................................ Not applicable

Last join error summary
- Type of error that occurred last......................... None
- Reason for error that occurred last...................... Not applicable
- Time at which the last join error occurred............... Not applicable

AP disconnect details
- Reason for last AP connection failure.................... Not applicable
Ethernet Mac : 00:00:00:00:00:00 Ip Address : 10.54.10.239

///////////////////////

The stup the cawap tunnel was this

capwap ap primary-base WLC1 10.50.4.101

capwap ap ip 10.54.10.239 255.255.255.0 10.54.10.1

capwap ap hostname   name AP 

///////////////////////

I'm using SSH to connect to an APit is work , and while I can see the configuration, I'm not sure whether it's enabled correctly or if the tunnel capwap mask needs to be changed. Does it not? Maybe that was the mistake, right?

>show capwap ip
config CAPWAP IP static configuration
APZALF5_210>show capwap ip config
IP Address : 10.54.10.210
IP netmask : 255.255.0.0
Default Gateway : 10.54.4.1
/////

CONTROLER VERSION

System Information
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 8.5.161.0
RTOS Version..................................... 8.5.161.0
Bootloader Version............................... 8.5.103.0
Emergency Image Version.......................... 8.5.103.0

OUI File Last Update Time........................ N/A
Build Type....................................... DATA + WPS

System Name...................................... WLC_ZAL_F5
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.2427
Redundancy Mode.................................. SSO
IP Address....................................... 10.54.4.101
IPv6 Address..................................... ::

[marce1000]

  - What controller model is this ?
     + Normally I would ask the full console boot (output) from an AP ; but since they are remote on the ceiling I would ask to reboot one of them and just after available in the network again issue the command show logging , post the output here.

 M.

[Flavio Miranda]

@athan1234 

 Based on the information you shared above:

- Discovery requests received.............................. 211
- Successful discovery responses sent...................... 211

The AP is reaching the WLC and the WLC is replying back to the AP. Meaning, the communication seems to be fine, unless of course, the AP is not receiving the reply from the WLC.

 To figure that out, you need to have console cable to at least on AP presenting the problem to check either the AP is receiving the discovery response or it is not receiving.

CAPWAP access point will not allow you to SSH when it is not joined on the WLC, you need to have console access on it either locally or someone providing you access via console.

My suspicious is related to firm version on the Access Point, but need to check.

[athan1234]

Regards, @Flavio Miranda 

so , Is it right that the capwap tunnel was configured in this app but was not joined?

capwap ap primary-base WLC1 10.50.4.101

capwap ap ip 10.54.10.239 255.255.255.0 10.54.10.1

capwap ap hostname   name AP 

//////////////////////////////

On the other hand, the APs are currently in the celling; I plan to check them tomorrow.

Which command I have to check it on the AP.

//////

One more thing: what will the user and password be when i try to conncet  via to  those  AP's console?

[marce1000]

       >...One more thing: what will the user and password be when i try to conncect  via to  those  AP's console?
  - It's only set or can be set when the AP is managed by the controller , for the time being getting the boot
    process (output) from one of them is the most important task.

                                   + Also specify the controller model

 M.

[Flavio Miranda · Accepted solution]

"so , Is it right that the capwap tunnel was configured in this app but was not joined?"

capwap ap primary-base WLC1 10.50.4.101

capwap ap ip 10.54.10.239 255.255.255.0 10.54.10.1

capwap ap hostname name AP"

If the log you share above is from the Access Point, yes, the tunnel is right as the AP is hitting the WLC and asking to join.

//////////////////////////////

"On the other hand, the APs are currently in the celling; I plan to check them tomorrow.

Which command I have to check it on the AP."

You dont need to check with commnads. Only connect to the AP in console mode, restart the AP and try to catch the logs. There will be some message on why the AP is not joining. Share the logs here please.

//////

"One more thing: what will the user and password be when i try to conncet via to those AP's console?"

Cisco/Cisco

This is the standard username and password.  You can also reset it in case it does not work. Just press the button on the back with a something, then connect the AP to the network or power supply, if that is the case, and hold for 20 seconds.

This should be enough to reset the AP.

Go prepared to maybe replace the AP firmware because this could be easly the problem.

[athan1234]

Hi @Flavio Miranda Thank you for all and your help.

[Rob Getrost]

From your output above, the  WLC you are trying to join is

WLC_ZAL_F5  10.54.4.101

So your join statement on the AP should match:

capwap ap primary-base WLC_ZAL_F5  10.54.4.101   NOT   capwap ap primary-base WLC1 10.50.4.101

A remote workaround you could consider only if this is your only WLC is to create the dns name CISCO-CAPWAP-CONTROLLER  to the IP of your WLC. This is the default catchall that an AP will use when it can't find a WLC. If its not your only WLC, doing this could cause other AP's to move if they are already relying on that DNS, so be careful with this. 

[athan1234]

Hi @Rob Getrost Sorry for the delayed response; I was out. 

You are right so thanks 

[Rob Getrost]

Please check your addressing

The instruction you have given to the AP is to reach the WLC @ capwap ap primary-base WLC1 10.50.4.101
But the IP specified in the Controller Version Details specifies IP Address....................................... 10.54.4.101 Look at the second octet

[Leo Laohoo]

Post the complete output to the following WLC commands: 

sh sysinfo
sh time

From the AP, post the complete output to the following commands: 

sh ip interface brief
sh capwap client rcb

[Rich R]

@athan1234 
What model(s) are the APs? (show ver)
What model is the WLC? Marce has already asked you this twice - but you need to answer because it is important. (show inventory)

The software version (8.5.161.0) is old but the recommended version to upgrade to will depend on the WLC and AP models.  If you want to work it out for yourself refer to the Compatibility Matrix and TAC Recommended links below.  In general it should be on 8.5.182.12 (for older WLCs and APs which ended on 8.5) or 8.10.196.0 for newer WLC and AP models.

[athan1234]

I appreciate all of your responses.