el 09-24-2013 03:27 PM
I've recently obtained several of the 2602i APs and a Cisco 5500 Controller. I'm having issues with the two talking to each other. Below are the error messages I'm receiving. I've seen other posts that suggests that the software on the controller may need to be upgraded.
I've run the commands lwapp ap ip address x.x.x.x x.x.x.x, and lwapp ap ip default-gatway x.x.x.x, and lwapp ap controller ip address x.x.x.x but am having no luck. The controller shows it attempting to connect but shows as Not Joined. I've also changed the IOS on the AP to the lightweight IOS and am still having the same issues.
Thanks
49:28.071: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 10.1.201.50
*Jun 18 19:49:28.071: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'Andy_Cisco-5500'running version 6.0.199.4 is rejected.
*Jun 18 19:49:28.071: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.
*Jun 18 19:49:28.071: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Jun 18 19:49:47.071: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Jun 18 19:49:47.071: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'Andy_Cisco-5500'running version 6.0.199.4 is rejected.
*Jun 18 19:49:47.071: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.
*Jun 18 19:49:47.071: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.
*Jun 18 19:49:47.071: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
*Jun 18 19:49:47.071: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 10.1.201.50
*Jun 18 19:49:47.071: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'Andy_Cisco-5500'running version 6.0.199.4 is rejected.
*Jun 18 19:49:47.071: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.
*Jun 18 19:49:47.071: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Jun 18 19:50:06.071: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Jun 18 19:50:06.071: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'Andy_Cisco-5500'running version 6.0.199.4 is rejected.
*Jun 18 19:50:06.071: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.
*Jun 18 19:50:06.071: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.
*Jun 18 19:50:06.071: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
*Jun 18 19:50:06.071: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 10.1.201.50
*Jun 18 19:50:06.071: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'Andy_Cisco-5500'running version 6.0.199.4 is rejected.
*Jun 18 19:50:06.071: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.
*Jun 18 19:50:06.071: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.
¡Resuelto! Ir a solución.
el 09-24-2013 04:18 PM
*Jun 18 19:50:06.071: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'Andy_Cisco-5500'running version 6.0.199.4 is rejected.
Read this: Software Release Support for Access Points
Your WLC is running an old firmware that won't support the 2600. You need a minimum of 7.2.110.0.
el 09-24-2013 04:18 PM
*Jun 18 19:50:06.071: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'Andy_Cisco-5500'running version 6.0.199.4 is rejected.
Read this: Software Release Support for Access Points
Your WLC is running an old firmware that won't support the 2600. You need a minimum of 7.2.110.0.
el 10-31-2013 08:28 AM
Sorry for the delayed response. Yes upgraded the firmware and it is now working.
Thanks for your help with this.
Descubra y salve sus notas favoritas. Vuelva a encontrar las respuestas de los expertos, guías paso a paso, temas recientes y mucho más.
¿Es nuevo por aquí? Empiece con estos tips. Cómo usar la comunidad Guía para nuevos miembros
Navegue y encuentre contenido personalizado de la comunidad