AP WAS NOT JOINING TO WLC

[raghu0001]

1832i-D-K9 AP not joining to WLC 2504

Getting AP CLI errors as below

 [*02/03/2021 15:13:25.6645] CAPWAP State: Discovery
[*02/03/2021 15:13:25.6645] Discovery Request sent to 192.168.0.73, discovery type STATIC_CONFIG(1)
[*02/03/2021 15:13:25.6645] Discovery Request sent to 192.168.0.73, discovery type STATIC_CONFIG(1)
[*02/03/2021 15:13:25.6645] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*02/03/2021 15:13:25.6645] Discovery Response from 192.168.0.73
[*02/03/2021 15:13:25.6645] Discovery response from MWAR ''running version 0.0.0.0 is rejected.
[*02/03/2021 15:13:25.6645] Failed to decode discovery response(status = 4).
[*02/03/2021 15:13:25.6645] CAPWAP SM handler: Failed to process message type 2 state 2.
[*02/03/2021 15:13:25.6645] Failed to handle capwap control message from controller - status 4
[*02/03/2021 15:13:25.6645] Failed to process unencrypted capwap packet 0x25be000 from 192.168.0.73
[*02/03/2021 15:13:25.6645] Failed to send message to CAPWAP state machine, msgId 0
[*02/03/2021 15:13:25.6645] Failed to send capwap message 0 to the state machine. Packet already freed.
[*02/03/2021 15:13:25.6645] IPv4 wtpProcessPacketFromSocket returned 4
[*02/03/2021 15:13:25.6645] Discovery Response from 192.168.0.73

AP Running Image version  8.5.140.0

WLC  version 8.5.140.0

[balaji.bandi]

is this only AP not joining others working as expected? is this any upgrade or changes?

there is some bug around not sure if this effecting you (worth checking)

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvu20765

[raghu0001]

Only one AP has not joining to WLC rest of all joined and working fine.

For reference i have attached AP CLI OUTPUT and WLC shw sysinfo and Shw time outputs

Regards

[Sandeep Choudhary]

paste the output of these commands from WLC:

show sysinfo

show time

Regards

Dont forget to rate helpful posts

[raghu0001]

Only one AP has not joining to WLC rest of all joined and working fine.

For reference i have attached AP CLI OUTPUT and WLC commands outputs

Regards

[joyaljp]

Did you check this AP model supported by the software which is running on your controller? 

Could you share show sysinfo output from controller CLI

[raghu0001]

Yes, the model AIR-AP-1832i was supported to WLC software 8.5.140.0

This one AP was not joining rest of all joined and working fine

WLC and AP outputs as attached below

[joyaljp]

Can you check the reason for the join failure in the WLC. Monitor>Ap statistics> AP join. You will see the reason for the AP join rejection.

[raghu0001]

WLC.>Monitor>Ap statistics> AP join output images are attached 

[joyaljp]

Are all your other AP's also configured on the same 192.168.12.0/24 subnet? The error says this subnet is not known by the WLC. If your using some other subnets to manage your AP's then try configuring the AP switch port with the correct VLAN.

[raghu0001]

it's not /24

it is /20 subnet

and the switch port is in same subnet

all other ap's are in same subnet and same VLAN and connected to wlc and working fine

[Leo Laohoo]

---

@raghu0001 wrote:

it's not /24

it is /20 subnet

and the switch port is in same subnet

all other ap's are in same subnet and same VLAN and connected to wlc and working fine

---

Erase the config of the AP and see if makes any difference. 

capwap ap erase all

[joyaljp]

Try the following.

1. @Leo Laohoo  Rest the ap via cli.

2.Hard reset the AP.

3. Try loading another firmware into the AP and then repet the join process.

[Leo Laohoo]

ip 192.168.12.119, netmask 255.255.240.0, gw 192.168.0.1, bcast 192.168.15.255

Wow!  For 75 APs, that is one HUGE subnet!