Solved: Re: AP1815i can't join mobility express controller

Rafael Hengky · ‎12-05-2021

Hi,

Can anyone help my issue. APs can not join mobility express controller. Attached are the boot log, etc.

Sandeep Choudhary · ‎12-06-2021

can you convert AP member to capwap! by using the command:

AP#ap-type capwap

Regards

Dont forget to rate helpful posts

View solution in original post

Sandeep Choudhary · ‎12-05-2021

Is 1815 and master controlle rin same VLAN ?

If not then which method you configured on Switch/router side to discover the WLC?

Bets would be to put these two AP& WLC in same subnet and check again.

Regards

Dont forget to rate helpful posts

Rafael Hengky · ‎12-05-2021

Hi,

There is no VLAN, both AP (master & slave/member) are attached to unmanaged switch. Both are getting dhcp ip with 192.168.1.x/24 network. Strangely master can't ping slave and vice versa. Below are the logs from slave when trying to join master:

[*11/12/2021 00:12:48.0674] CAPWAP State: Discovery
[*11/12/2021 00:12:48.0730] IP DNS query for CISCO-CAPWAP-CONTROLLER.local
[*11/12/2021 00:12:48.0863] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*11/12/2021 00:13:17.5296]
[*11/12/2021 00:13:17.5296] CAPWAP State: Discovery
[*11/12/2021 00:13:17.5391] Discovery failed 5 times. Check Release/Renew DHCP AP CAPWAP MODE:[1] controller previously connected:[0]
[*11/12/2021 00:13:17.5399] IP DNS query for CISCO-CAPWAP-CONTROLLER.local
[*11/12/2021 00:13:17.5612] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*11/12/2021 00:13:36.9874] WTP IP address changed from 0.0.0.0 to 192.168.1.3, restart CAPWAP.
[*11/12/2021 00:13:36.9874]
[*11/12/2021 00:13:36.9875]
[*11/12/2021 00:13:36.9875] Going to restart CAPWAP (reason : WTP IP address changed)...
[*11/12/2021 00:13:36.9875]
[*11/12/2021 00:13:36.9880] Restarting CAPWAP State Machine.
[*11/12/2021 00:13:36.9883] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Discovery(2).
[*11/12/2021 00:13:37.0484]
[*11/12/2021 00:13:37.0484] CAPWAP State: DTLS Teardown
[*11/12/2021 00:13:37.3029] upgrade.sh: Script called with args:[ABORT]
[*11/12/2021 00:13:37.3989] do ABORT, part2 is active part
[*11/12/2021 00:13:37.4622] upgrade.sh: Cleanup tmp files ...
[*11/12/2021 00:13:37.5454] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Teardown(4).
[*11/12/2021 00:13:37.5456] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Teardown(4).

Rafael Hengky · ‎12-05-2021

Hi,

There are no VLANs. Both APs are attached to unmanaged switch. They got dhcp ip 192.168.1.x/24 network. Strangely master and slave can't ping each other. Below are logs from slave when trying to find controller:

[*11/12/2021 00:21:53.0291] CAPWAP State: Discovery
[*11/12/2021 00:21:53.0311] IP DNS query for CISCO-CAPWAP-CONTROLLER.local
[*11/12/2021 00:21:53.0408] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*11/12/2021 00:22:22.4931]
[*11/12/2021 00:22:22.4931] CAPWAP State: Discovery
[*11/12/2021 00:22:22.4947] Discovery failed 5 times. Check Release/Renew DHCP AP CAPWAP MODE:[1] controller previously connected:[0]
[*11/12/2021 00:22:22.4953] IP DNS query for CISCO-CAPWAP-CONTROLLER.local
[*11/12/2021 00:22:22.5056] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*11/12/2021 00:22:41.9514] WTP IP address changed from 0.0.0.0 to 192.168.1.3, restart CAPWAP.
[*11/12/2021 00:22:41.9514]
[*11/12/2021 00:22:41.9515]
[*11/12/2021 00:22:41.9515] Going to restart CAPWAP (reason : WTP IP address changed)...
[*11/12/2021 00:22:41.9515]
[*11/12/2021 00:22:41.9521] Restarting CAPWAP State Machine.
[*11/12/2021 00:22:41.9525] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Discovery(2).
[*11/12/2021 00:22:42.0125]
[*11/12/2021 00:22:42.0125] CAPWAP State: DTLS Teardown
[*11/12/2021 00:22:42.2764] upgrade.sh: Script called with args:[ABORT]
[*11/12/2021 00:22:42.3747] do ABORT, part2 is active part
[*11/12/2021 00:22:42.4397] upgrade.sh: Cleanup tmp files ...
[*11/12/2021 00:22:42.5214] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Teardown(4).
[*11/12/2021 00:22:42.5216] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Teardown(4).

Rafael Hengky · ‎12-06-2021

Hi,

There are no VLANs. Both APs are attached to unmanaged switch. They got dhcp ip 192.168.1.x/24 network. Strangely master and slave can't ping each other. Below are logs from slave when trying to find controller:

[*11/12/2021 00:21:53.0291] CAPWAP State: Discovery
[*11/12/2021 00:21:53.0311] IP DNS query for CISCO-CAPWAP-CONTROLLER.local
[*11/12/2021 00:21:53.0408] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*11/12/2021 00:22:22.4931]
[*11/12/2021 00:22:22.4931] CAPWAP State: Discovery
[*11/12/2021 00:22:22.4947] Discovery failed 5 times. Check Release/Renew DHCP AP CAPWAP MODE:[1] controller previously connected:[0]
[*11/12/2021 00:22:22.4953] IP DNS query for CISCO-CAPWAP-CONTROLLER.local
[*11/12/2021 00:22:22.5056] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*11/12/2021 00:22:41.9514] WTP IP address changed from 0.0.0.0 to 192.168.1.3, restart CAPWAP.
[*11/12/2021 00:22:41.9514]
[*11/12/2021 00:22:41.9515]
[*11/12/2021 00:22:41.9515] Going to restart CAPWAP (reason : WTP IP address changed)...
[*11/12/2021 00:22:41.9515]
[*11/12/2021 00:22:41.9521] Restarting CAPWAP State Machine.
[*11/12/2021 00:22:41.9525] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Discovery(2).
[*11/12/2021 00:22:42.0125]
[*11/12/2021 00:22:42.0125] CAPWAP State: DTLS Teardown
[*11/12/2021 00:22:42.2764] upgrade.sh: Script called with args:[ABORT]
[*11/12/2021 00:22:42.3747] do ABORT, part2 is active part
[*11/12/2021 00:22:42.4397] upgrade.sh: Cleanup tmp files ...
[*11/12/2021 00:22:42.5214] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Teardown(4).
[*11/12/2021 00:22:42.5216] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Teardown(4).

Rafael Hengky · ‎12-05-2021

Hi,

There are no VLANs. Both APs are attached to unmanaged switch. They got dhcp ip 192.168.1.x/24 network. Strangely master and slave can't ping each other. Below are logs from slave when trying to find controller:

[*11/12/2021 00:21:53.0291] CAPWAP State: Discovery
[*11/12/2021 00:21:53.0311] IP DNS query for CISCO-CAPWAP-CONTROLLER.local
[*11/12/2021 00:21:53.0408] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*11/12/2021 00:22:22.4931]
[*11/12/2021 00:22:22.4931] CAPWAP State: Discovery
[*11/12/2021 00:22:22.4947] Discovery failed 5 times. Check Release/Renew DHCP AP CAPWAP MODE:[1] controller previously connected:[0]
[*11/12/2021 00:22:22.4953] IP DNS query for CISCO-CAPWAP-CONTROLLER.local
[*11/12/2021 00:22:22.5056] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*11/12/2021 00:22:41.9514] WTP IP address changed from 0.0.0.0 to 192.168.1.3, restart CAPWAP.
[*11/12/2021 00:22:41.9514]
[*11/12/2021 00:22:41.9515]
[*11/12/2021 00:22:41.9515] Going to restart CAPWAP (reason : WTP IP address changed)...
[*11/12/2021 00:22:41.9515]
[*11/12/2021 00:22:41.9521] Restarting CAPWAP State Machine.
[*11/12/2021 00:22:41.9525] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Discovery(2).
[*11/12/2021 00:22:42.0125]
[*11/12/2021 00:22:42.0125] CAPWAP State: DTLS Teardown
[*11/12/2021 00:22:42.2764] upgrade.sh: Script called with args:[ABORT]
[*11/12/2021 00:22:42.3747] do ABORT, part2 is active part
[*11/12/2021 00:22:42.4397] upgrade.sh: Cleanup tmp files ...
[*11/12/2021 00:22:42.5214] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Teardown(4).
[*11/12/2021 00:22:42.5216] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Teardown(4).

Rafael Hengky · ‎12-05-2021

Why are my post replies didn't showing?

Sandeep Choudhary · ‎12-05-2021

Now its showing....

Rafael Hengky · ‎12-06-2021

Post this like 3-4 times and it's gone..

Sandeep Choudhary · ‎12-06-2021

can you convert AP member to capwap! by using the command:

AP#ap-type capwap

Regards

Dont forget to rate helpful posts

Rafael Hengky · ‎12-15-2021

Yes it turns out that AP members need to change to capwap with ap-type capwap command. So I read that AP members only need the same ME image but actually different firmware version can also join the controller as long it's in capwap mode (not ME). After issuing the command AP will restart and if the firmware is different from the controller it will try to upgrade. I got another issue with the upgrade process and solved it with turning the AP to ME mode and turn it back to capwap mode.

Rafael Hengky · ‎12-15-2021

Thank you Sandeep for the helpful post