cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3428
Views
0
Helpful
7
Replies

8.3.112.0 Breaks 1142 APs, but not ones with HW revision 1

chris.brunt
Level 1
Level 1

I have discovered a serious problem with 1142 APs after moving them to a newer controller version. They were previously ether on WISM or 3750G controllers running 7.0.240.0 or similar. I have moved them to either 2504 or 5520 controller running 8.3.112.0.

Some 1142s ported over fine and are working normally but quite a few broke completely.

It seems any that are HW revision V01 printed on the back are working 100%

I am testing others i have some v02 and v06 i think....

I have a lot of V04 APs that are now broken. If I plug into the console and manage to erase the NVRAM so that I can get them to rejoin a controller on an older software version.

There is nothing in the release notes or bugs i can find to say these are not supported!

A console output from the AP I get the following in an infinite loop.

*Jul 27 12:49:56.458: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Jul 27 12:49:56.458: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Jul 27 12:49:56.515: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Jul 27 12:49:56.515: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
*Jul 27 12:49:56.525: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Jul 27 12:49:56.540: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Jul 27 12:49:57.152: status of voice_diag_test from WLC is false
*Jul 27 12:49:57.160: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Jul 27 12:49:57.176: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Jul 27 12:49:57.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.1.1.1 peer_port: 5246
*Jul 27 12:49:57.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Jul 27 12:49:57.611: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.1.1.1 peer_port: 5246
*Jul 27 12:49:57.612: %CAPWAP-5-SENDJOIN: sending Join Request to 10.1.1.1
*Jul 27 12:49:57.612: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Jul 27 12:50:02.611: %CAPWAP-5-SENDJOIN: sending Join Request to 10.1.1.1
*Jul 27 12:50:02.626: %CAPWAP-3-ERRORLOG: Validate Msg: msg type 4 does not supported payload 215
*Jul 27 12:50:02.626: %LWAPP-3-CLIENTERRORLOG: Validate Msg: msg type 4 does not supported payload 215
*Jul 27 12:50:02.626: %LWAPP-3-CLIENTERRORLOG: Validate Msg: error in unknown payload (received length = 9, payload type = 215)
*Jul 27 12:50:02.626: %CAPWAP-3-ERRORLOG: Failed to validate vendor specific message element type 215 len 9.
*Jul 27 12:50:02.627: %CAPWAP-3-ERRORLOG: Config status: Failed to validate vendor specific message element.
*Jul 27 12:50:02.627: %CAPWAP-3-ERRORLOG: Failed to decode join response.
*Jul 27 12:50:02.670: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.1.1.1:5246
*Jul 27 12:50:02.670: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 4 state 4.
7 Replies 7

chris.brunt
Level 1
Level 1