×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

AIR-WLC2112-K9 and CAPWAP access point

Unanswered Question
Nov 26th, 2013
User Badges:

Hi everybody!!

I have a AIR-WLC2112-K9 (Software Version 6.0.199.4). Also, I have five AIR-LAP1242G-A-K9 controlled with WLC.

I want to add to these deployment AIR-LAP1261N-E-K9. My WLC works only with LWAPP-enabled access points. But this 1260 series AP start guide describe:

http://www.cisco.com/en/US/docs/wireless/access_point/1260/quick/guide/ap1260getstart.html  (The Controller discovery process, 1st paragraph)

"The 1260 series access point uses the IETF standard Control and Provisioning of Wireless Access Points Protocol (CAPWAP) to communicate between the controller and other wireless access points on the network. CAPWAP is a standard, interoperable protocol which enables an access controller to manage a collection of wireless termination points. The discovery process using CAPWAP is identical to the Lightweight Access Point Protocol (LWAPP) used with previous Cisco Aironet access points. LWAPP-enabled access points are compatible with CAPWAP and conversion to a CAPWAP controller is seamless. Deployments can combine CAPWAP and LWAPP software on the controllers."


Here is logs from AIR-LAP1261N-E-K9 CLI:

*Mar  1 01:33:00.169: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER.internal.shate-m.com

*Mar  1 01:33:00.172: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'Cisco_62:e0:60'running version 6.0.199.4 is rejected.

*Mar  1 01:33:00.172: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar  1 01:33:00.172: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 01:33:00.172: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar  1 01:33:00.172: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 10.8.0.2

*Mar  1 01:33:00.172: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'Cisco_62:e0:60'running version 6.0.199.4 is rejected.

*Mar  1 01:33:00.172: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar  1 01:33:00.172: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 01:33:10.173: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'Cisco_62:e0:60'running version 6.0.199.4 is rejected.

*Mar  1 01:33:10.173: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar  1 01:33:10.173: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 01:33:10.173: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar  1 01:33:10.173: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 10.8.0.2

*Mar  1 01:33:10.173: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'Cisco_62:e0:60'running version 6.0.199.4 is rejected.

*Mar  1 01:33:10.173: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar  1 01:33:10.173: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 01:33:10.173: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar  1 01:33:20.173: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'Cisco_62:e0:60'running version 6.0.199.4 is rejected.

*Mar  1 01:33:20.173: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar  1 01:33:20.173: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 01:33:20.173: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar  1 01:33:20.173: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 10.8.0.2

*Mar  1 01:33:20.173: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'Cisco_62:e0:60'running version 6.0.199.4 is rejected.

*Mar  1 01:33:20.173: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar  1 01:33:20.173: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 01:33:20.173: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar  1 01:33:30.173: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'Cisco_62:e0:60'running version 6.0.199.4 is rejected.

*Mar  1 01:33:30.173: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar  1 01:33:30.173: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 01:33:30.173: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar  1 01:33:30.173: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 10.8.0.2

*Mar  1 01:33:30.173: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'Cisco_62:e0:60'running version 6.0.199.4 is rejected.

*Mar  1 01:33:30.173: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar  1 01:33:30.173: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar  1 01:33:30.173: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller


Is it possible to join new AIR-LAP1261N-E-K9 to my LWAPP-enabled WLC?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Pablo Montiel Bernal Fri, 12/13/2013 - 14:57
User Badges:

AIR-LAP1261N-E-K9 not support Software Version 6.0.199.4


CAPWAP support is provided in controller software release 5.2 or later. However, your controller must be running release 7.0 or later to support 1260 series access points.


http://www.cisco.com/en/US/docs/wireless/access_point/1260/quick/guide/ap1260getstart.html


You can upgrade AIR-WLC2112-K9 to Release 7.0.240.0


Don´t worry with AIR-LAP1242G-A-K9 are still supported.

Leo Laohoo Fri, 12/13/2013 - 15:51
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 LAN, Wireless

Minimum WLC firmware to support 1260 is 7.0.116.0.


If you can upgrade your WLC to 7.0.240.X then I'd recommend you go to this version.

Actions

This Discussion

Related Content

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode