topic Re: AP 9115 unable to join VWLC controller in Wireless

AP 9115 unable to join VWLC controller

Calin Cristea — Wed, 11 Jan 2023 07:32:20 GMT

Hello,

I have a VWLC controller with image version 8.10.181.0 with several access points already associate to it (model 1542 and 2700).

I want to add a 9115 Access point. This AP is unable to join, i have enough licenses.

AP ip: 10.1.1.2/16

Controller ip 10.1.1.3/16

If i try associating the AP into the same network, i keep getting this message:

[*01/10/2023 15:54:01.7820] No more AP manager addresses remain..
[*01/10/2023 15:54:01.7820] No valid AP manager found for controller 'Controller_' (ip: 10.1.1.3)
[*01/10/2023 15:54:01.7820] Failed to join controller Controller
[*01/10/2023 15:54:01.7820] Failed to join controller.

The same AP if i move it to a different location on a different subnet with VPN L3, the AP joins instantly on Layer 3.

Problem is that AP is not joining the Controller on the same network, on different networks it joins .

I need to mention,that there are 2 other controllers in the same network (subnet), but with old OS versions, so AP 9115 could not be able to join to them.

LOGS:

[*01/10/2023 15:52:50.7840] CAPWAP State: Discovery
[*01/10/2023 15:52:50.7860] Discovery Request sent to 10.1.1.3, discovery type STATIC_CONFIG(1)
[*01/10/2023 15:52:50.7920] Discovery Request sent to 10.1.1.3, discovery type STATIC_CONFIG(1)
[*01/10/2023 15:52:50.7940] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*01/10/2023 15:52:50.7950] Discovery Response from 10.1.1.5
[*01/10/2023 15:52:50.7950] Discovery response from MWAR 'Controller_1' running version 8.0.150.0 is rejected.
[*01/10/2023 15:52:50.7950] Failed to decode discovery response(status = 4).
[*01/10/2023 15:52:50.7950] CAPWAP SM handler: Failed to process message type 2 state 2.
[*01/10/2023 15:52:50.7950] Failed to handle capwap control message from controller - status 4
[*01/10/2023 15:52:50.7950] Failed to process unencrypted capwap packet 0x55a0c7b000 from 10.1.1.5
[*01/10/2023 15:52:50.7950] Failed to send capwap message 0 to the state machine. Packet already freed.
[*01/10/2023 15:52:50.7950] Discovery Response from 10.1.1.6
[*01/10/2023 15:52:50.7950] Discovery response from MWAR 'Controller_2' running version 8.5.171.0 is rejected.
[*01/10/2023 15:52:50.7950] Failed to decode discovery response(status = 4).
[*01/10/2023 15:52:50.7950] CAPWAP SM handler: Failed to process message type 2 state 2.
[*01/10/2023 15:52:50.7950] Failed to handle capwap control message from controller - status 4
[*01/10/2023 15:52:50.7950] Failed to process unencrypted capwap packet 0x55a0c0a000 from 10.1.1.6
[*01/10/2023 15:52:50.7950] Failed to send capwap message 0 to the state machine. Packet already freed.
[*01/10/2023 15:52:50.7950] Discovery Response from 10.1.1.5
[*01/10/2023 15:52:50.7960] Discovery Response from 10.1.1.6
[*01/10/2023 15:52:50.7960] Discovery response from MWAR 'XXXX' running version 8.8.125.0 is rejected.
[*01/10/2023 15:52:50.7960] Failed to decode discovery response(status = 4).
[*01/10/2023 15:52:50.7960] CAPWAP SM handler: Failed to process message type 2 state 2.
[*01/10/2023 15:52:50.7960] Failed to handle capwap control message from controller - status 4
[*01/10/2023 15:52:50.7960] Failed to process unencrypted capwap packet 0x55a0c0a000 from 10.1.1.5
[*01/10/2023 15:52:50.7960] Failed to send capwap message 0 to the state machine. Packet already freed.
[*01/10/2023 15:53:00.0000]
[*01/10/2023 15:53:00.0000] CAPWAP State: DTLS Setup
[*01/10/2023 15:53:57.0300]
[*01/10/2023 15:53:57.0300] CAPWAP State: DTLS Teardown
[*01/10/2023 15:53:57.1060] upgrade.sh: Script called with args:[ABORT]
[*01/10/2023 15:53:57.1450] do ABORT, part1 is active part
[*01/10/2023 15:53:57.1610] upgrade.sh: Cleanup tmp files ...
[*01/10/2023 15:53:57.1790] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Teardown(4).
[*01/10/2023 15:53:57.1790] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Teardown(4).
[*01/10/2023 15:54:01.7820] No more AP manager addresses remain..
[*01/10/2023 15:54:01.7820] No valid AP manager found for controller 'Controller_1' (ip: 10.1.1.3)
[*01/10/2023 15:54:01.7820] Failed to join controller Controller_1.
[*01/10/2023 15:54:01.7820] Failed to join controller.

Re: AP 9115 unable to join 2504 controller

Leo Laohoo — Tue, 10 Jan 2023 22:57:36 GMT

@Calin Cristea wrote:
I have a 2504 controller with image version 8.10 with several access points already associate to it (model 1700 and 1600).

Not correct. 2504 would not be able to support 8.10.X.X firmware. And if the controller is a 3504 and is running 8.10.X.X, then the controller will not support 1600.

Re: AP 9115 unable to join 2504 controller

Calin Cristea — Wed, 11 Jan 2023 07:35:19 GMT

Hello Leo, thank you for you`re response, i have edited the question. My bad, the controller is a wireless lan controller, and AP`s are 1542 and 2700

Re: AP 9115 unable to join 2504 controller

Leo Laohoo — Wed, 11 Jan 2023 08:35:15 GMT

@Calin Cristea wrote:
[*01/10/2023 15:52:50.7950] Discovery response from MWAR 'Controller_1' running version 8.0.150.0 is rejected.
[*01/10/2023 15:52:50.7950] Discovery response from MWAR 'Controller_2' running version 8.5.171.0 is rejected.
[*01/10/2023 15:52:50.7960] Discovery response from MWAR 'XXXX' running version 8.8.125.0 is rejected.

AP is being pointed to controllers that are not 8.10.18X.X.

Console into the AP and enter the command "capwap ap primary-base <WLC NAME> <WLC IP ADDRESS>".

Re: AP 9115 unable to join 2504 controller

Calin Cristea — Wed, 11 Jan 2023 08:40:06 GMT

Hello Leo, i already entered that command. But , the access point is keep bouncing through Controllers.

I have 2 old controllers and a Mobility express AP. But on the 9115 i did type to join the VWLC controller by name and ip address.

When AP is not able to join, it seems that he is trying to find other WLC`s. I cannot shutdown other WLCs or try to isolate, because they are in the same network.

Re: AP 9115 unable to join 2504 controller

Leo Laohoo — Wed, 11 Jan 2023 09:02:28 GMT

Can the AP ping the controller with 8.10.18X.X firmware?

Re: AP 9115 unable to join 2504 controller

Calin Cristea — Wed, 11 Jan 2023 09:07:07 GMT

Yes, the AP is able to ping the WLC. The AP and the ESX that contains the VWLC are connected on the same switch.

Re: AP 9115 unable to join VWLC controller

JPavonM — Wed, 11 Jan 2023 09:42:15 GMT

Try factory resetting the AP with "capwap ap erase" or if that doesn't work enter U-BOOT mode from AP console and remove previous config files "flash:config.*"

Re: AP 9115 unable to join 2504 controller

Leo Laohoo — Wed, 11 Jan 2023 09:46:30 GMT

Post the complete output to the command "sh capwap client rcb".

Re: AP 9115 unable to join 2504 controller

Calin Cristea — Wed, 11 Jan 2023 10:01:43 GMT

AP1006.EDD9.7A94#sh capwap client rcb
AdminState : ADMIN_ENABLED
OperationState : DTLS SETUP
Name : AP1006.EDD9.7A94
SwVer : 8.10.181.0
HwVer : 1.0.0.0
MwarApMgrIp : 10.1.1.3
MwarName : Controller_1
MwarHwVer : 0.0.0.0
Location : default location
ApMode : Local
ApSubMode : Not Configured
CAPWAP Path MTU : 576
Software Initiated Reload Reason : Unknown
CAPWAP Sliding Window
Active Window Size : 0
CAPWAP UDP-Lite : Enabled
IP Prefer-mode : IPv4
AP Link DTLS Encryption : OFF
AP TCP MSS Adjust : Disabled
LinkAuditing : disabled
AP Group Name : default-group
Cisco Trustsec Config
AP Inline Tagging Mode : Disabled
--More-- [*01/11/2023 12:02:23.0280]
[*01/11/2023 12:02:23.0280] CAPWAP State: DTLS Teardown
[*01/11/2023 12:02:23.0840] upgrade.sh: Script called with args:[ABORT]
[*01/11/2023 12:02:23.1230] do ABORT, part2 is active part
[*01/11/2023 12:02:23.1380] upgrade.sh: Cleanup tmp files ...

Re: AP 9115 unable to join VWLC controller

Calin Cristea — Wed, 11 Jan 2023 10:02:07 GMT

I did reset the AP.

Re: AP 9115 unable to join VWLC controller

Leo Laohoo — Wed, 11 Jan 2023 10:34:36 GMT

@Calin Cristea wrote:
MwarApMgrIp : 10.1.1.3
MwarName : Controller_1

The AP is configured to go to Controller_1. This controller is loaded with 8.0.150.0.

If the command "capwap ap primary-base <WLC NAME> <WLC IP ADDRESS>" was entered correctly, the details would have reflected here.

Re: AP 9115 unable to join VWLC controller

Calin Cristea — Wed, 11 Jan 2023 10:39:51 GMT

Controller 1 has the correct Name and IP address.
I have just modify the real name for security reasons, maybe i misspelled
it.

Re: AP 9115 unable to join VWLC controller

Calin Cristea — Thu, 19 Jan 2023 06:18:13 GMT

I have solved the problem. Added AP and Controller into the same mobility Group.

https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-4/config-guide/b_cg84/high_availability.html#vwlc-and-nplus1-ha