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

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

CAPWAP error on WLC

Yesterday I had an AP that disassociated from the controller and now it won't join.  I'm getting the following errors.  Cisco's documentation is not really pointing out the issue.  Any one encountered these before?

Software Version: 7.4.100.0

FRI: 1.0.0

*spamApTask0: Dec 16 19:24:13.613: fc:99:47:d9:8a:4b Failed to parse CAPWAP packet from 10.141.16.44:39077

*spamApTask0: Dec 16 19:25:08.194: 00:00:00:00:00:00 DTLS connection was closed

*spamApTask1: Dec 16 19:25:18.699: 00:00:00:00:00:00 Not allocating an entry for the AP, received an AP with zero mac 00:00:00:00:00:00

*spamApTask1: Dec 16 19:25:18.699: 00:00:00:00:00:00 Failed to allocate database entry for AP 10.141.16.44:39078

*spamApTask1: Dec 16 19:25:18.700: 00:00:00:00:00:00 Failed to add database entry for 10.141.16.44:39078

*spamApTask1: Dec 16 19:25:18.700: 00:00:00:00:00:00 State machine handler: Failed to process  msg type = 3 state = 0 from 10.141.16.44:39078

*spamApTask1: Dec 16 19:25:18.700: fc:99:47:d9:8a:4b Failed to parse CAPWAP packet from 10.141.16.44:39078

*spamApTask1: Dec 16 19:25:23.697: 00:00:00:00:00:00 Not allocating an entry for the AP, received an AP with zero mac 00:00:00:00:00:00

*spamApTask1: Dec 16 19:25:23.697: 00:00:00:00:00:00 Failed to allocate database entry for AP 10.141.16.44:39078

*spamApTask1: Dec 16 19:25:23.697: 00:00:00:00:00:00 Failed to add database entry for 10.141.16.44:39078

*spamApTask1: Dec 16 19:25:23.697: 00:00:00:00:00:00 State machine handler: Failed to process  msg type = 3 state = 0 from 10.141.16.44:39078

  • Getting Started with Wireless
21 REPLIES
VIP Purple

Re: CAPWAP error on WLC

If you are running Software Version: 7.4.100.0, then you should upgrade it to at least 7.4.110.0 (7.4MR1)  as the code you are running is very first release of 7.4 ( released on 2012 Dec) which consists of many bugs.

If you are interested latest bug fixed version of 7.4 (which is 7.4.111.x or 7.4MR2) you can get a pre-release code from here

https://supportforums.cisco.com/docs/DOC-37334

Here is a summary of bugs we encounter in this 7.4.x journey sofar.

http://mrncciew.com/2013/02/10/day-0-with-wlc-7-4-code/

Then see if this issue still there. Also make sure you upgraded your WLC FUS to 1.7.0.0 as well (this could lead upto 30-40 min of downtime to your wireless)

http://www.cisco.com/en/US/docs/wireless/controller/release/notes/fus_rn_1_7_0_0.html

HTH

Rasika

**** Pls rate all useful responses *****

CAPWAP error on WLC

Thank you for the awesome reply and cool links.  I'm going to look into that but I just found out another issue.  On the switch where this AP is connected when I do "show power inline"  I get this:

Fa0/2     auto   on         15.0    Ieee PD             3     15.4

So the port recognizes the AP for a min or two and then it goes into this state.  I will post back the results.

VIP Purple

Re: CAPWAP error on WLC

If it is 1042/1142 AP then this definetely a bug of that software code. WLC software Upgrade including FUS would be the fix

HTH

Rasika

CAPWAP error on WLC

Its is actually AIR-CAP2602E-A-K9.  I believe it might be related to the physical connectivity as well since it is not showing up properly on the switch.

VIP Purple

Re: CAPWAP error on WLC

If your WLC FUS has not upgraded to 1.7.0.0, this could be a potential reason 2600 series AP get stranded.

Check that & see.

Here is a similar issue get fixed by FUS upgrade.

https://supportforums.cisco.com/message/4087264#4087264

HTH

Rasika

Hall of Fame Super Gold

CAPWAP error on WLC

Fa0/2     auto   on         15.0    Ieee PD             3     15.4

You've got a cable issue.  Do the following commands:

1.  Command:  test cable tdr interface f0/2;

2.  Wait for 5 to 7 seconds;

3.  Command:  sh cable tdr interface f0/2; and

4.  Post the output to #3. 

Hall of Fame Super Silver

Re: CAPWAP error on WLC

Like Leo mentioned, when you see IEEE when looking at the power, it's almost 99% a layer 1 (cable issue) or 1% is a bad port which I just ran into.

Sent from Cisco Technical Support iPhone App

Thanks, Scott *****Help out other by using the rating system and marking answered questions as "Answered"*****
Hall of Fame Super Gold

CAPWAP error on WLC

1% is a bad port which I just ran into.

Scott,

Bad port of the switch?

Hall of Fame Super Silver

Re: CAPWAP error on WLC

Yup... Actually ran into that issue twice. One was a ASIC went bad and just last week it was a bad port. Moved the AP to another port and it came up fine. I took a good ap and connected it directly to the port and I got the IEEE. Took another AP and plugged it in and got the same error. We RMA'd the switch

Sent from Cisco Technical Support iPhone App

Thanks, Scott *****Help out other by using the rating system and marking answered questions as "Answered"*****
1842
Views
5
Helpful
21
Replies
This widget could not be displayed.