2802i APs not associating to Mobility Express controller

[jonathanking09]

I have some new 2802i APs I am trying to associate to a 2802 Mobility Express controller. ME controller is running 8.10.151.0. New APs have been converted to ME, now running 8.10.196.0.

AP is trying to associate with controller, but continually looping:

[*08/06/2024 15:40:40.0003] CAPWAP State: DTLS Setup
[*08/06/2024 15:40:40.7376]
[*08/06/2024 15:40:40.7376] CAPWAP State: Join
[*08/06/2024 15:40:40.8381] Sending Join request to 192.168.1.3 through port 5264
[*08/06/2024 15:41:37.0305]
[*08/06/2024 15:41:37.0305] CAPWAP State: DTLS Teardown
[*08/06/2024 15:41:37.1052] upgrade.sh: Script called with args:[ABORT]
[*08/06/2024 15:41:37.1641] do ABORT, part2 is active part
[*08/06/2024 15:41:37.1857] upgrade.sh: Cleanup tmp files ...
[*08/06/2024 15:41:37.2208] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Teardown(4).
[*08/06/2024 15:41:37.2209] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Teardown(4).
[*08/06/2024 15:41:51.7835]
[*08/06/2024 15:41:51.7835] CAPWAP State: Discovery
[*08/06/2024 15:41:51.7869] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*08/06/2024 15:41:51.7885] Discovery Response from 192.168.1.3
[*08/06/2024 15:42:01.0003]
[*08/06/2024 15:42:01.0003] CAPWAP State: DTLS Setup
[*08/06/2024 15:42:01.7306]
[*08/06/2024 15:42:01.7306] CAPWAP State: Join
[*08/06/2024 15:42:01.8310] Sending Join request to 192.168.1.3 through port 5264

The clock on both the controller and the AP are correct.

I appreciate any suggestions!

[marce1000]

              >...New APs have been converted to ME, now running 8.10.196.0.
  For the APs to be able to join a controller they must be in client CAPWAP mode , 

 M.
   

[jonathanking09]

Hi Marce,

The behavior is the same on these 2802s whether they are in CAPWAP or Mobility Express mode. I have verified this using command "ap-type capwap" and "ap-type mobility-express tftp://<server_IP/AIR-AP2800-K9-ME-8-10-196-0.tar".

[marce1000 · Accepted solution]

   - Ok, but that is a bit confusing the idea is to 'not have' 
     "ap-type mobility-express tftp://<server_IP/AIR-AP2800-K9-ME-8-10-196-0.tar".
     You can resolve this issue with the command show version

     + The ME controller should be  running 8.10.196.0 and not the reverse , if the AP's have a higher CAPWAP image version
        then the controller then that could lead to problems

    + Also have a checkup of the mobility express controller's configuration using : WirelessAnalyzer input (procedure) for AireOs controllers  and feed the output from that into Wireless Config Analyzer

   M.
       

[jonathanking09]

Thank you, Marce. I downgraded the firmware on the new APs to match that of the controller, and we're back in business now. I greatly appreciate your help!

[Rich R]

Glad to hear you got it working but really what you should have been doing is upgrading the ME to the current release, not downgrading the new APs to the old version!  Remember ME needs a TFTP server for the APs to download the images from and the TFTP server details need to be configured on the ME WLC so that ME can tell the APs where to fetch the image from.  The ME zip file should be unzipped on the TFTP server so that the images are there ready for download.