[c-nsp] Issue with WLC 2504 and 1242 APs

[Mike Hale]

Did you try a factory reset of the AP yet?

On Wed, Mar 12, 2014 at 1:43 PM, Christopher Werny <cwerny at ernw.de> wrote:
> Hi everyone,
>
> I have a small WLC deployment (1 2504 WLC running 7.6.110.0) and 12 APs (8 x 1242 and 4 x 1602). All APs are joining the WLC correctly.
> The issue that I have is that configuration changes (e.g. activating SSH access on the APs) do not get applied to the 1242 APs. This only affects the 1242 APs, the 1602 are working as intended.
>
> When I apply the changes, the following errors messages appear on the 1242 APs (I am connected over the console port).
>
> *Mar 12 15:15:27.519: %CAPWAP-3-ERRORLOG: Validate Msg: msg type 12 does not supported
> payload 215
>
> *Mar 12 15:15:27.519: %CAPWAP-3-ERRORLOG: Validate Msg: error in Unknown Payload(215)
> payload (received length = 9, payload type = 215)
>
> *Mar 12 15:15:27.519: %CAPWAP-3-ERRORLOG: Failed to validate vendor specific message
> element type 215 len 9.
>
> *Mar 12 15:15:27.519: %CAPWAP-3-ERRORLOG: Failed to decode Configuration update request.
>
> *Mar 12 15:15:27.520: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message
> type 7 state 11.
>
> *Mar 12 15:15:27.520: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from
> controller
>
> *Mar 12 15:15:27.520: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from
> 172.20.40.10
>
> Googling around a little bit, I found the following thread in the support forums:
>
> https://supportforums.cisco.com/discussion/12115351/wlc-5508-lap1242-failed-handle-capwap-control-message-controller
>
> This thread mentioned that it could be that there is not enough space on the AP to hold the configuration.
> I verified the free space on the APs and it is around 10 Megabyte on every AP. So this *should* be enough.
>
> TAC Case is open, but didn't resolve the issue yet, as the engineer redirected me to the thread above.
>
> So I thought I give it a shot and query the wisdom of this list.
>
> Did anyone run into this issue, or have some tips/hints on how to resolve it?
>
> Appreciate your input.
>
> Best,
> Chris
>
>
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/



-- 
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0