AP1562i-T cannot join 5508(8.5.110)! AP LOG:MWAR ''running version 0.0.0.0

[linfeng]

Hello,

My 5508 run 8.5.110 firmware, and the ap1562i-T cannot join it.....

I found one bug id: CSCvf71074 (AP 1562 Failed to decode discovery response)

Have the same log....

But I already upgrade to 8.5.110 (fix firmware), no fix the issue...

Have any idea about it ?

AP console log:

[*12/12/2017 01:37:53.7569] CAPWAP State: Discovery
[*12/12/2017 01:37:53.7581] Discovery Response from 10.40.50.245
[*12/12/2017 01:37:53.7583] Discovery response from MWAR ''running version 0.0.0.0 is rejected.
[*12/12/2017 01:37:53.7584] Failed to decode discovery response.
[*12/12/2017 01:37:53.7584] CAPWAP SM handler: Failed to process message type 2 state 2.
[*12/12/2017 01:37:53.7584] Failed to handle capwap control message from controller - status 4
[*12/12/2017 01:37:53.7584] Failed to process unencrypted capwap packet 0x1eb2000 from 10.40.50.245
[*12/12/2017 01:37:53.7584] Failed to send capwap message 0 to the state machine. Packet already freed.
[*12/12/2017 01:37:53.7584] IPv4 wtpProcessPacketFromSocket returned 4
[*12/12/2017 01:37:53.7587] Discovery Response from 10.40.50.245
[*12/12/2017 01:37:53.7588] Discovery response from MWAR ''running version 0.0.0.0 is rejected.
[*12/12/2017 01:37:53.7588] Failed to decode discovery response.

=====

WLC Debug log:

*spamApTask1: Jan 05 17:31:27.300: 4c:77:6d:d9:b2:80 Discovery Response sent to 10.40.50.101:5264

*capwapSocketTask: Jan 05 17:31:36.800: acParsePacket: LRAD IP: 10.40.50.101, MWAR IP: 10.40.50.245

*spamApTask1: Jan 05 17:31:36.800: 4c:77:6d:d9:b2:80 length = 4, packet received from 4c:77:6d:d9:b2:80

*spamApTask1: Jan 05 17:31:36.800: 4c:77:6d:d9:b2:80 Discovery request: Total msgEleLen = 0

*spamApTask1: Jan 05 17:31:36.800: 4c:77:6d:d9:b2:80 Join Priority Processing status = 0, Incoming Ap's Priority 0, MaxLrads = 150, MaxLicense=50 joined Aps =0
*spamApTask1: Jan 05 17:31:36.800: 4c:77:6d:d9:b2:80 Send Discovery response to 10.40.50.101:5264

*spamApTask1: Jan 05 17:31:36.800: 4c:77:6d:d9:b2:80 apType = 71 apModel:

*spamApTask1: Jan 05 17:31:36.800: 4c:77:6d:d9:b2:80 Unknown AP type. Using Controller Version!!!

*spamApTask1: Jan 05 17:31:36.800: 4c:77:6d:d9:b2:80 msgLength = 36

*capwapSocketTask: Jan 05 17:31:36.801: acParsePacket: LRAD IP: 10.40.50.101, MWAR IP: 255.255.255.255

*spamApTask1: Jan 05 17:31:36.801: 4c:77:6d:d9:b2:80 Discovery resp:IPv4WtpManager[0]: a2832f5

*spamApTask1: Jan 05 17:31:36.801: 4c:77:6d:d9:b2:80 No AP manager found !! (rc=0)

*spamApTask1: Jan 05 17:31:36.801: 4c:77:6d:d9:b2:80 encodeLen = 116 len = 16 msgEleLen = 119

*spamApTask1: Jan 05 17:31:36.801: acSendDiscoveryResponsePacket: ipv4 lrad 10.40.50.101, mwar 10.40.50.245

*spamApTask1: Jan 05 17:31:36.801: acSendDiscoveryResponsePacket.2151: ipv4 lrad 10.40.50.101, mwar 10.40.50.245 Len 178

[Abdessattar_Belt]

Hi Saravanan,
Thank you for the answer.
I tried these 2 alternatives but there is no change.

[linfeng]

I try to upload new firmware to APs.

The issue is fix!

So, maybe the default firmware in AP1562 have some trouble.

===

archive download-sw /reload tftp://x.x.x.x/ap3g3-k9w8-tar.153-3.JF4.tar (upload firmware)

WLC version: 8.5.110

[Abdessattar_Belt]

Hi linfeng,

Thank you for the answer.

Actually, I downloaded that same image "ap3g3-k9w8-tar.153-3.JF4.tar " and it was successfully uploaded to the AP (it has become the running image) but I still have the same issue with the same error messages. I mention that I was using virtual WLC with software version 8.2.141.0 and now I am using 8.5.110.0

[linfeng]

Maybe try 8.5.110.

One bug id like the attached file.

[Abdessattar_Belt]

Update:

Now I am using version 153-3.JD11 on the AP and 8.5.100.0 on the virtual WLC.

I received a new type of error message that says: "This AP model is supported by controller version newer than 8.3.15.0".

Any suggestions ?

[Leo Laohoo]

---

@Abdessattar_Belt wrote:

Update:

Now I am using version 153-3.JD11 on the AP and 8.5.100.0 on the virtual WLC.

I received a new type of error message that says: "This AP model is supported by controller version newer than 8.3.15.0".

Any suggestions ?

---

If the vWLC is running 8.5, post the entire boot-up process of the AP.  I want to see what the AP is actually doing.

[Abdessattar_Belt1]

We are now using version 8.5.110 with 2504 WLC.

I attached the entire log of the AP.

[Leo Laohoo]

[*12/12/2017 04:52:23.5027] Discovery response from MWAR ''running version 0.0.0.0 is rejected.
[*12/12/2017 04:52:23.5028] Failed to decode discovery response.
[*12/12/2017 04:52:23.5028] CAPWAP SM handler: Failed to process message type 2 state 2.
[*12/12/2017 04:52:23.5028] Failed to handle capwap control message from controller - status 4

CSCvf71074

Can you post the complete output to the WLC command "sh sysinfo".

[Abdessattar_Belt1]

Here is the result of sysinfo command.

[Scott Fella]

If your 1562 is in bridge mode, it will not join since you have multiple country codes defined. Only a single country code is supported for bridge/mesh. If that AP is in bridge mode, you need to convert it to local. From the console, try this command:
capwap ap mode local

[Abdessattar_Belt1]

The AP is already running on local mode.

[Scott Fella]

As long as you are 100% sure it’s in local mode then make sure you have the correct power injector for that AP and connect it to the same vlan as the WLC management. If it doesn’t join, then there is a bug. If you’re not 100% sure it’s in local mode then you need to add the Ethernet MAC address that’s on the label on the AP or box and only have one country code defined on the controller.  There is nothing else you can really do here if it’s not a bug or is still acting in bridge mode. 

[Leo Laohoo]

The AP has a Regulatory Domain for RoC (Taiwan) but the controller is configured for France, UK and Taiwan.
Try to enable only Taiwan and see what happens.

[Abdessattar_Belt1]

We changed the Regulatory Domain of the WLC for Taiwan then for Tunisia (TN) but we are getting the same output.
How did you know that the RoC of the AP is configured for Taiwan ?

[Leo Laohoo]

Regulatory Domain of the AP, "-T", is for the RoC (aka Taiwan).