2802i is enable to join Controller

[Hamza DEHAL]

Hello,

I have a 2802i as a Mobility Express Controller with 5 APs (2800 and 1830 Capwap and ME), I am trying to add another 2802i but it can't joun the controller.

I tried to upgrade the AP to the same version as the controller (8.10.130.0) when I use the command: ap-type mobility-express tftp://IP@/image_name.tar it says : image upgrade not needed (same thing with .zip file)

I used: archive download-sw /reload tftp://IP@/image_name

This time it starts uploading the image and when it reaches 100% it replies with an ERROR!

Any help would be much appreciated.

[Leo Laohoo]

The error message means the AP is already on ME image.

[Hamza DEHAL]

@Leo Laohoo 

Even if it is already in ME image it still can't join the Controller 

[Leo Laohoo]

---

@Hamza DEHAL wrote:

Even if it is already in ME image it still can't join the Controller 

---

Mobility Express means the AP is already operating as a mini-WLC. 

IF you want an AP to join a WLC or a ME, the AP needs to operate as local mode.

[Hamza DEHAL]

@Leo Laohoo 

I changed the ap-type to Capwap and here is a screenshot of the logs when trying to join the Controller: 

would it be better to have the same software version?

[Leo Laohoo]

No need.  

If the WLC is configured properly the AP should join.

[Hamza DEHAL]

@Leo Laohoo 

Any suggestions to resolve this issue ?

[Leo Laohoo]

Post the complete output to the following commands: 

• WLC:  sh sysinfo
• WLC:  sh time
• AP:  sh version
• AP:  sh ip int brief

[Hamza DEHAL]

@Leo Laohoo 

Here is the outputs:

[Leo Laohoo]

Uhhhh ... The AP is still running Mobility Express image. 

[Hamza DEHAL]

@Leo Laohoo 

I tried to convert it via cli to capwap via : ap-type capwap after rebooting here is the output:

I can see it is in ME mode, here is the output of the log while booting :

[*09/01/2021 12:52:54.8730] CAPWAP State: Discovery

[*09/01/2021 12:52:54.8737] IP DNS query for CISCO-CAPWAP-CONTROLLER.airalgerie.dz

[*09/01/2021 12:52:54.8803] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)

[*09/01/2021 12:52:54.8811] Discovery Response from 192.168.252.10

[*09/01/2021 12:52:54.8886] Unsupported vendor spec payload TLV_VENDOR_SPECIFIC_PAYLOAD(215) for msgtype 2

[*09/01/2021 12:53:04.0000]  can't find the Ip from discoveryRequest array

[*09/01/2021 12:53:04.0000]

[*09/01/2021 12:53:04.0001]

[*09/01/2021 12:53:04.0001] CAPWAP State: DTLS Setup

[*09/01/2021 12:53:04.6844]

[*09/01/2021 12:53:04.6844] CAPWAP State: Join

[*09/01/2021 12:53:04.6861] Sending Join request to 192.168.252.10 through port 5248

[*09/01/2021 12:53:12.7331] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Join(5).

[*09/01/2021 12:53:12.7331] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Join(5).

[*09/01/2021 12:53:17.1294] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Join(5).

[*09/01/2021 12:53:17.7250] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Join(5).

APDC8C.37BF.B8C6#

APDC8C.37BF.B8C6#[*09/01/2021 12:54:01.0171]

[*09/01/2021 12:54:01.0171] CAPWAP State: DTLS Teardown

[*09/01/2021 12:54:05.8729]

[*09/01/2021 12:54:05.8729] CAPWAP State: Discovery

[*09/01/2021 12:54:05.8736] IP DNS query for CISCO-CAPWAP-CONTROLLER.airalgerie.dz

[*09/01/2021 12:54:05.8824] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)

[*09/01/2021 12:54:05.8832] Discovery Response from 192.168.252.10

[*09/01/2021 12:54:05.8908] Unsupported vendor spec payload TLV_VENDOR_SPECIFIC_PAYLOAD(215) for msgtype 2

[*09/01/2021 12:54:15.0000]  can't find the Ip from discoveryRequest array

[*09/01/2021 12:54:15.0000]

[*09/01/2021 12:54:15.0001]

[*09/01/2021 12:54:15.0001] CAPWAP State: DTLS Setup

[*09/01/2021 12:54:15.7008]

[*09/01/2021 12:54:15.7008] CAPWAP State: Join

[*09/01/2021 12:54:15.7021] Sending Join request to 192.168.252.10 through port 5248

[*09/01/2021 12:54:15.7057] Join Response from 192.168.252.10

[*09/01/2021 12:54:15.7915] HW CAPWAP tunnel is ADDED

[*09/01/2021 12:54:15.8069]

[*09/01/2021 12:54:15.8069] CAPWAP State: Image Data

[*09/01/2021 12:54:15.8456] do PRECHECK, part2 is active part

[*09/01/2021 12:54:15.9797] Image Data Request sent to 192.168.252.10

[*09/01/2021 12:54:54.4812] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).

[Arshad Safrulla]

[*09/01/2021 12:54:15.9797] Image Data Request sent to 192.168.252.10

[*09/01/2021 12:54:54.4812] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).

Your AP is running 8.5.151 and it will not join the ME controller running 8.10.130 without a software upgrade. So as I mentioned below you have 2 options. One upgrade the AP manually using the below command, download the lightweight ap image from cisco

archive download-sw /reload <source iamge>

Or connect a TFTP server to the ME controller and host the AP images in the TFTP root. This AP image bundle also can be downloaded from the Cisco site. It's zip file u need to unzip it in the tftp root directory. TFTP server configuration is under management==>software upgrade, trasnfer mode tftp or whatever you prefer, set the tftp ip, file path /, ) Configure the tftp parameters and save. Remember each time when an ap joins this tftp server has to be available

[Leo Laohoo]

Console into the AP and enter the following command:  ap-type capwap

[Scott Fella · Accepted solution]

@Leo Laohoo I think he did try that command but it failed.

@Hamza DEHAL I think you need to push a new image to the ap using the mode button or via ssh if the ap is up and you can connect to it without it rebooting.  There are many guides and videos on this, just search for "cisco ap tftp using the mode button".  Even guides for converting autonomous to lightweight or vice versa will have the instructions.

[Arshad Safrulla]

AP registration is failing due to image download issues and mismatch, solution is to either upgrade all the capwap AP's to match the ME controller image or spin up a TFTP server to assist ME to send the images to capwap AP's. First download and store the AP images in the TFTP root. Then configure the ME to access the TFTP server (Its under management==>software upgrade, trasnfer mode tftp or whatever you prefer, set the tftp ip, file path /, ) Configure the tftp parameters and save. Remember each time when an ap joins this tftp server has to be available

https://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/8-2/b_Mobility_Express_Deployment_guide/b_Mobility_Express_Deployment_guide_chapter_01000.html

This is becaise unlike a physical WLC ME doesnt have storage and other resources to hold the AP images for different AP's.