Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

CAPWAP SM handler: Failed to process message type 2 state 2

i have a 5508 controller  with software version 7.0.116.0,  we just got in some new  AIR-CAP2602I-A-K9 waps,  we already have some 1142 LAP on our sytem that work great, the proble is with the new waps, they are not connecting to our controller,  i dont know why, we are not blocking any ports internal with in our firewall, here is the logs from the controller  and logs from the ap log , please help...

*dot1xMsgTask: Jul 29 10:38:32.417: %DOT1X-3-MAX_EAPOL_KEY_RETRANS: 1x_ptsm.c:444 Max EAPOL-key M3 retransmissions exceeded for client 00:26:5e:42:59:03

*Dot1x_NW_MsgTask_3: Jul 29 10:38:29.218: %DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:843 Received EAPOL-key M2 msg has invalid information when mobile is in START  state - invalid secure bit; KeyLen 22, Key type 1, client 00:26:5e:42:59:03

*Dot1x_NW_MsgTask_3: Jul 29 10:38:28.050: %DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:843 Received EAPOL-key M2 msg has invalid information when mobile is in START  state - invalid secure bit; KeyLen 22, Key type 1, client 00:26:5e:42:59:03

*spamApTask0: Jul 29 10:38:23.331: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP b8:62:1f:41:d9:b0

*spamApTask4: Jul 29 10:38:12.536: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP e8:04:62:60:c3:e0

*dot1xMsgTask: Jul 29 10:38:02.617: %DOT1X-3-MAX_EAPOL_KEY_RETRANS: 1x_ptsm.c:444 Max EAPOL-key M3 retransmissions exceeded for client 00:22:5f:68:70:b6

*spamApTask0: Jul 29 10:37:53.992: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (181) on interface (13) from AP b8:62:1f:45:ba:c0

*spamApTask4: Jul 29 10:37:21.224: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP b8:62:1f:41:cb:d0

*spamApTask1: Jul 29 10:37:06.317: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (181) on interface (13) from AP b8:62:1f:41:dc:b0

*spamApTask5: Jul 29 10:36:48.424: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP b8:62:1f:41:d0:a0

*spamApTask0: Jul 29 10:36:23.325: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP b8:62:1f:41:d9:b0

*DHCP Client Task: Jul 29 10:36:19.881: %DHCP-3-BIND_SRPORT_ERR: dhcp_support.c:373 Binding service port failed.

*spamApTask4: Jul 29 10:36:12.531: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP e8:04:62:60:c3:e0

*spamApTask0: Jul 29 10:35:53.985: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (181) on interface (13) from AP b8:62:1f:45:ba:c0

*spamApTask4: Jul 29 10:35:21.217: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP b8:62:1f:41:cb:d0

*spamApTask1: Jul 29 10:35:06.309: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (181) on interface (13) from AP b8:62:1f:41:dc:b0

*Dot1x_NW_MsgTask_7: Jul 29 10:34:53.414: %DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:843 Received EAPOL-key M2 msg has invalid information when mobile is in START  state - invalid secure bit; KeyLen 40, Key type 1, client 88:53:2e:cf:41:8f

*Dot1x_NW_MsgTask_7: Jul 29 10:34:52.278: %DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:843 Received EAPOL-key M2 msg has invalid information when mobile is in START  state - invalid secure bit; KeyLen 40, Key type 1, client 88:53:2e:cf:41:8f

*spamApTask5: Jul 29 10:34:48.415: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP b8:62:1f:41:d0:a0

*spamApTask0: Jul 29 10:34:23.319: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP b8:62:1f:41:d9:b0

*spamApTask4: Jul 29 10:34:12.526: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP e8:04:62:60:c3:e0

*spamApTask0: Jul 29 10:33:53.978: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (181) on interface (13) from AP b8:62:1f:45:ba:c0

*spamApTask4: Jul 29 10:33:21.211: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP b8:62:1f:41:cb:d0

*spamApTask1: Jul 29 10:33:06.300: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (181) on interface (13) from AP b8:62:1f:41:dc:b0

*spamApTask5: Jul 29 10:32:48.407: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP b8:62:1f:41:d0:a0

*dot1xMsgTask: Jul 29 10:32:39.013: %DOT1X-3-MAX_EAPOL_KEY_RETRANS: 1x_ptsm.c:444 Max EAPOL-key M3 retransmissions exceeded for client c0:cb:38:06:61:61

*Dot1x_NW_MsgTask_1: Jul 29 10:32:35.814: %DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:843 Received EAPOL-key M2 msg has invalid information when mobile is in START  state - invalid secure bit; KeyLen 22, Key type 1, client c0:cb:38:06:61:61

*Dot1x_NW_MsgTask_1: Jul 29 10:32:34.638: %DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:843 Received EAPOL-key M2 msg has invalid information when mobile is in START  state - invalid secure bit; KeyLen 22, Key type 1, client c0:cb:38:06:61:61

*spamApTask0: Jul 29 10:32:23.313: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP b8:62:1f:41:d9:b0

*spamApTask4: Jul 29 10:32:12.521: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP e8:04:62:60:c3:e0

*dot1xMsgTask: Jul 29 10:32:10.213: %DOT1X-3-MAX_EAP_RETRIES: 1x_auth_pae.c:2992 Max EAP identity request retries (3) exceeded for client 00:26:c6:7c:6c:0a

*spamApTask0: Jul 29 10:31:53.971: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (181) on interface (13) from AP b8:62:1f:45:ba:c0

*spamApTask4: Jul 29 10:31:21.205: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP b8:62:1f:41:cb:d0

*spamApTask1: Jul 29 10:31:06.292: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (181) on interface (13) from AP b8:62:1f:41:dc:b0

*spamApTask5: Jul 29 10:30:48.398: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP b8:62:1f:41:d0:a0

*spamApTask0: Jul 29 10:30:23.307: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP b8:62:1f:41:d9:b0

*spamApTask4: Jul 29 10:30:12.516: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP e8:04:62:60:c3:e0

*dot1xMsgTask: Jul 29 10:30:07.813: %DOT1X-3-MAX_EAPOL_KEY_RETRANS: 1x_ptsm.c:444 Max EAPOL-key M3 retransmissions exceeded for client 9c:b7:0d:f9:12:23

*spamApTask0: Jul 29 10:29:53.965: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (181) on interface (13) from AP b8:62:1f:45:ba:c0

*spamApTask4: Jul 29 10:29:21.199: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP b8:62:1f:41:cb:d0

*spamApTask1: Jul 29 10:29:06.284: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (181) on interface (13) from AP b8:62:1f:41:dc:b0

*spamApTask5: Jul 29 10:28:48.389: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP b8:62:1f:41:d0:a0

*spamApTask0: Jul 29 10:28:23.288: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP b8:62:1f:41:d9:b0

*spamApTask4: Jul 29 10:28:12.511: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP e8:04:62:60:c3:e0

*DHCP Client Task: Jul 29 10:27:58.837: %DHCP-3-BIND_SRPORT_ERR: dhcp_support.c:373 Binding service port failed.

*dot1xMsgTask: Jul 29 10:27:58.213: %DOT1X-3-MAX_EAPOL_KEY_RETRANS: 1x_ptsm.c:444 Max EAPOL-key M3 retransmissions exceeded for client 00:1e:65:a3:22:b0

*dot1xMsgTask: Jul 29 10:27:54.413: %DOT1X-3-MAX_EAPOL_KEY_RETRANS: 1x_ptsm.c:444 Max EAPOL-key M3 retransmissions exceeded for client 00:1e:65:a3:22:b0

*spamApTask0: Jul 29 10:27:53.958: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (181) on interface (13) from AP b8:62:1f:45:ba:c0

*dot1xMsgTask: Jul 29 10:27:50.813: %DOT1X-3-MAX_EAPOL_KEY_RETRANS: 1x_ptsm.c:444 Max EAPOL-key M3 retransmissions exceeded for client 00:1e:65:a3:22:b0

*dot1xMsgTask: Jul 29 10:27:47.013: %DOT1X-3-MAX_EAPOL_KEY_RETRANS: 1x_ptsm.c:444 Max EAPOL-key M3 retransmissions exceeded for client 00:1e:65:a3:22:b0

*dot1xMsgTask: Jul 29 10:27:43.413: %DOT1X-3-MAX_EAPOL_KEY_RETRANS: 1x_ptsm.c:444 Max EAPOL-key M3 retransmissions exceeded for client 00:1e:65:a3:22:b0

*dot1xMsgTask: Jul 29 10:27:39.613: %DOT1X-3-MAX_EAPOL_KEY_RETRANS: 1x_ptsm.c:444 Max EAPOL-key M3 retransmissions exceeded for client 00:1e:65:a3:22:b0

*spamApTask4: Jul 29 10:27:21.193: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP b8:62:1f:41:cb:d0

*spamApTask1: Jul 29 10:27:06.276: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (181) on interface (13) from AP b8:62:1f:41:dc:b0

*spamApTask5: Jul 29 10:26:48.381: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP b8:62:1f:41:d0:a0

*dot1xMsgTask: Jul 29 10:26:40.413: %DOT1X-3-MAX_EAPOL_KEY_RETRANS: 1x_ptsm.c:444 Max EAPOL-key M5 retransmissions exceeded for client 00:1e:65:a5:54:ae

*spamApTask0: Jul 29 10:26:23.282: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP b8:62:1f:41:d9:b0

*spamApTask4: Jul 29 10:26:12.507: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP e8:04:62:60:c3:e0

*spamApTask0: Jul 29 10:25:53.951: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (181) on interface (13) from AP b8:62:1f:45:ba:c0

*spamApTask4: Jul 29 10:25:21.187: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP b8:62:1f:41:cb:d0

*spamApTask1: Jul 29 10:25:06.260: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (181) on interface (13) from AP b8:62:1f:41:dc:b0

*spamApTask5: Jul 29 10:24:48.372: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP b8:62:1f:41:d0:a0

*spamApTask0: Jul 29 10:24:23.276: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP b8:62:1f:41:d9:b0

*spamApTask4: Jul 29 10:24:12.502: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP e8:04:62:60:c3:e0

*spamApTask0: Jul 29 10:23:53.944: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (181) on interface (13) from AP b8:62:1f:45:ba:c0

*dot1xMsgTask: Jul 29 10:23:47.813: %DOT1X-3-MAX_EAPOL_KEY_RETRANS: 1x_ptsm.c:444 Max EAPOL-key M3 retransmissions exceeded for client 78:e4:00:c4:13:0a

*Dot1x_NW_MsgTask_2: Jul 29 10:23:44.614: %DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:843 Received EAPOL-key M2 msg has invalid information when mobile is in START  state - invalid secure bit; KeyLen 22, Key type 1, client 78:e4:00:c4:13:0a

*Dot1x_NW_MsgTask_2: Jul 29 10:23:43.499: %DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:843 Received EAPOL-key M2 msg has invalid information when mobile is in START  state - invalid secure bit; KeyLen 22, Key type 1, client 78:e4:00:c4:13:0a

*spamApTask4: Jul 29 10:23:21.180: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP b8:62:1f:41:cb:d0

*spamApTask1: Jul 29 10:23:06.252: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (181) on interface (13) from AP b8:62:1f:41:dc:b0

*spamApTask5: Jul 29 10:22:48.364: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP b8:62:1f:41:d0:a0

*spamApTask0: Jul 29 10:22:23.269: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP b8:62:1f:41:d9:b0

*spamApTask4: Jul 29 10:22:12.497: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP e8:04:62:60:c3:e0

*spamApTask0: Jul 29 10:21:53.937: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (181) on interface (13) from AP b8:62:1f:45:ba:c0

*spamApTask4: Jul 29 10:21:21.174: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP b8:62:1f:41:cb:d0

*spamApTask1: Jul 29 10:21:06.244: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (181) on interface (13) from AP b8:62:1f:41:dc:b0

*spamApTask5: Jul 29 10:20:48.355: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP b8:62:1f:41:d0:a0

*spamApTask0: Jul 29 10:20:23.263: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP b8:62:1f:41:d9:b0

*spamApTask4: Jul 29 10:20:12.492: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (182) on interface (13) from AP e8:04:62:60:c3:e0

*spamApTask0: Jul 29 10:19:53.930: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1468 Ignoring Primary discovery request received on a wrong VLAN (181) on interface (13) from AP b8:62:1f:45:ba:c0

logs form the ap

*Mar  1 00:35:41.575: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'CH550801'running version 7.0.116.0 is rejected.

*Mar  1 00:35:41.575: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar  1 00:35:41.575: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 00:35:41.575: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar  1 00:35:41.575: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 192.168.4.6

*Mar  1 00:35:41.575: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'CH550801'running version 7.0.116.0 is rejected.

*Mar  1 00:35:41.575: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar  1 00:35:41.575: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 00:35:41.575: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar  1 00:35:41.575: %CAPWAP-3-ERRORLOG: Failed to

process unencrypted capwap packet from 192.168.4.6

*Mar  1 00:35:41.575: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'CH550801'running version 7.0.116.0 is rejected.

--More--

*Mar  1 00:58:20.115: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER.cityama.com

*Mar  1 00:58:20.115: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'CH550801'running version 7.0.116.0 is rejected.

*Mar  1 00:58:20.115: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar  1 00:58:20.115: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 00:58:20.115: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar  1 00:35:41.575: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar  1 00:35:41.575: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 00:35:41.575: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar  1 00:35:41.575: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 192.168.4.6

*Mar  1 00:35:41.575: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'CH550801'running version 7.0.116.0 is rejected.

*Mar  1 00:35:41.575: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar  1 00:35:41.575: %00:58:20.115: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 192.168.4.6

*Mar  1 00:58:20.119: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'CH550801'running version 7.0.116.0 is rejected.

*Mar  1 00:58:20.119CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 00:35:41.575: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar  1 00:35:41.575: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 192.168.4.6

*Mar  1 00:35:51.575: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'CH550801'running version 7.0.116.0 is rejected.

*Mar  1 00:35:51.575: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar  1 00:35:51.575: %CAP: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar  1 00:58:20.119: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.WAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 00:35:51.575: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar  1 00:35:51.575: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 192.168.4.6

*Mar  1 00:35:51.575: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'CH550801'running version 7.0.116.0 is rejected.

*Mar  1 00:35:51.575: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar  1 00:35:51.575: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 00:35:51.575: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar  1 00:35:51.575: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 192.168.4.6

*Mar  1 00:36:01.575: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'CH550801'running version 7.0.116.0 is rejected.

*Mar  1 00:36:01.575: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar  1 00:36:01.575: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 00:36:01.575: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar  1 00:36:01.575: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 192.168.4.6

*Mar  1 00:36:01.575: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'CH550801'running version 7.0.116.0 is rejected.

*Mar  1 00:36:01.575: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar  1 00:36:01.575: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 00:36:01.575: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar  1 00:36:01.575: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 192.168.4.6

*Mar  1 00:36:01.575: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'CH550801'running version 7.0.116.0 is rejected.

*Mar  1 00:36:01.575: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar  1 00:36:01.575: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 00:36:01.575: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar  1 00:36:01.575: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 192.168.4.6

*Mar  1 00:36:01.575: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'CH550801'running version 7.0.116.0 is rejected.

*Mar  1 00:36:01.575: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar  1 00:36:01.575: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 00:36:01.575: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar  1 00:36:01.575: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 192.168.4.6

*Mar  1 00:36:17.075: %CAPWAP-3-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.

*Mar  1 00:36:21.691: %CAPWAP-3-ERRORLOG: Invalid event 38 & state 2 combination.

*Mar  1 00:36:21.811: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 192.168.4.241, mask 255.255.255.0, hostname AP6c41.6aa3.3c6a

*Mar  1 00:36:28.075: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.

*Mar  1 00:36:31.075: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER.cityama.com

*Mar  1 00:36:31.075: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'CH550801'running version 7.0.116.0 is rejected.

*Mar  1 00:36:31.075: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar  1 00:36:31.075: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 00:36:31.075: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar  1 00:36:31.075: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 192.168.4.6

*Mar  1 00:36:31.075: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'CH550801'running version 7.0.116.0 is rejected.

*Mar  1 00:36:31.075: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar  1 00:36:31.075: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 00:36:31.075: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar  1 00:36:31.075: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 192.168.4.6

*Mar  1 00:36:31.075: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'CH550801'running version 7.0.116.0 is rejected.

*Mar  1 00:36:31.079: %CAPWAP-3-ERRORLOG: Failed to decod

*Mar  1 00:58:30.115: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'CH550801'running version 7.0.116.0 is rejected.

*Mar  1 00:58:30.115: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar  1 00:58:30.115: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 00:58:30.115: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar  1 00:58:30.115: %CAPWAP-3-ERRORLOG: Failed to process unencryptede discovery response.

*Mar  1 00:36:31.079: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 00:36:31.079: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar  1 00:36:31.079: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 192.168.4.6

*Mar  1 00:36:31.079: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'CH550801'running version 7.0.116.0 is rejected.

*Mar  1 00:36:31.079: %CAPWAP-3-ERRORLOG: Failed to decode d capwap packet from 192.168.4.6

*Mar  1 00:58:30.115: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'CH550801'running version 7.0.116.0 is rejected.

*Mar  1 00:58:30.115: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar  1 00:58:30.115: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 00:58:30.115: %Ciscovery response.

*Mar  1 00:36:31.079: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 00:36:31.079: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar  1 00:36:31.079: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 192.168.4.6

*Mar  1 00:36:41.075: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'CH550801'running version 7.0.116.0 is rejected.

*Mar  1 00:36:41.075: %CAPWAPWAP-3-ERRORLOG: Failed to handle capwap control message from controllerAP-3-ERRORLOG: Failed to decode discovery response.

*Mar  1 00:36:41.075: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 00:36:41.075: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar  1 00:36:41.075: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 192.168.4.6

*Mar  1 00:36:41.075: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'CH550801'running version 7.0.116.0 is rejected.

*Mar  1 00:36:41.075: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar  1 00:36:41.075: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 00:36:41.075: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar  1 00:36:41.075: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 192.168.4.6

*Mar  1 00:36:51.075: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'CH550801'running version 7.0.116.0 is rejected.

*Mar  1 00:36:51.075: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar  1 00:36:51.075: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 00:36:51.075: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar  1 00:36:51.075: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 192.168.4.6

*Mar  1 00:36:51.075: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'CH550801'running version 7.0.116.0 is rejected.

*Mar  1 00:36:51.075: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar  1 00:36:51.075: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 00:36:51.075: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar  1 00:36:51.075: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 192.168.4.6

*Mar  1 00:36:51.075: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'CH550801'running version 7.0.116.0 is rejected.

*Mar  1 00:36:51.075: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar  1 00:36:51.075: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 00:36:51.075: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar  1 00:36:51.075: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 192.168.4.6

*Mar  1 00:36:51.075: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'CH550801'running version 7.0.116.0 is rejected.

*Mar  1 00:36:51.075: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar  1 00:36:51.075: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 00:36:51.075: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar  1 00:36:51.075: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 192.168.4.6

*Mar  1 00:37:01.075: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'CH550801'running version 7.0.116.0 is rejected.

*Mar  1 00:37:01.075: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar  1 00:37:01.075: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 00:37:01.075: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar  1 00:37:01.075: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 192.168.4.6

*Mar  1 00:37:01.075: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'CH550801'running version 7.0.116.0 is rejected.

*Mar  1 00:37:01.075: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar  1 00:37:01.075: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 00:37:01.075: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar  1 00:37:01.075: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 192.168.4.6

*Mar  1 00:37:16.575: %CAPWAP-3-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.

*Mar  1 00:37:21.179: %CAPWAP-3-ERRORLOG: Invalid event 38 & state 2 combination.

*Mar  1 00:37:21.183: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 192.168.4.241, mask 255.255.255.0, hostname AP6c41.6aa3.3c6a



1 REPLY
Hall of Fame Super Gold

Re: CAPWAP SM handler: Failed to process message type 2 state 2

i have a 5508 controller  with software version 7.0.116.0,  we just got in some new  AIR-CAP2602I-A-K9 waps

For AP2600, you need a minimum of 7.2.110.0.   Read this.

4535
Views
0
Helpful
1
Replies
CreatePlease to create content