Weird new ap problem

Unanswered Question
Mar 25th, 2010

This is from an out of the box access point. To me it appears to have been used previously!!

Code version is 6.0.196 on a 5508. Plenty of ap capacity. Its an 1142 and we have been having some fun and games with this particular setup already.

I am going to make the ap autonomous then upgrade to LWAPP so it is fresh again but if anyone can explain why this is happening I would be grateful.

022.bd1a.98c9#

., 1)25 15:36:50.299: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(UNKNOWN_MESSAGE_TYPE (5)

*Mar 25 15:36:50.299: %CAPWAP-3-ERRORLOG: GOING BACK TO DISCOVER MODE

*Mar 25 15:36:50.299: %DTLS-5-SEND_ALERT: Send WARNING : Close notify Alert to 10.64.99.5:5246

*Mar 25 15:36:50.334: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Mar 25 15:36:50.334: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Mar 25 15:36:50.345: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down

*Mar 25 15:36:50.345: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down

*Mar 25 15:36:50.360: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Mar 25 15:36:50.361: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up

*Mar 25 15:36:50.376: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Mar 25 15:36:50.376: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset

*Mar 25 15:36:50.393: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up

*Mar 25 15:36:50.393: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Mar 25 15:36:50.399: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Mar 25 15:37:00.370: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Mar 25 15:37:00.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.64.99.5 peer_port: 5246

*Mar 25 15:37:00.000: %CAPWAP-5-CHANGED: CAPWAP changed state to

*Mar 25 15:37:01.120: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.64.99.5 peer_port: 5246

*Mar 25 15:37:01.121: %CAPWAP-5-SENDJOIN: sending Join Request to 10.64.99.5

*Mar 25 15:37:01.121: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN

*Mar 25 15:37:01.301: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG

*Mar 25 15:37:01.301: %CAPWAP-3-ERRORLOG: Starting config timer

*Mar 25 15:37:01.406: %DTLS-3-BAD_RECORD: Erroneous record received from 10.64.99.5: Duplicate (replayed) recordlwapp ap controller ip address 10.65.99.5

ERROR!!! Command is disabled.

AP0022.bd1a.98c9#

AP0022.bd1a.98c9#lwapp ap controller ip address 10.65.99.5

ERROR!!! Command is disabled.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Scott Fella Thu, 03/25/2010 - 20:28

The issue is that the ap initially joined:

*Mar 25 15:37:01.121: %CAPWAP-5-SENDJOIN: sending Join Request to 10.64.99.5

*Mar 25 15:37:01.121: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN

*Mar 25 15:37:01.301: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG

*Mar 25 15:37:01.301: %CAPWAP-3-ERRORLOG: Starting config timer

That is why you are getting this:

ERROR!!! Command is disabled.

Here is what you can try.... this was for an 1131 so just adjust for your 1142:

First, check the flash:
lap_1131#dir
Directory of flash:/

2 -rwx 279 May 09 2008 11:52:20 +00:00 env_vars
4 -rwx 6168 May 09 2008 11:52:20 +00:00 private-multiple-fs
6 drwx 256 May 09 2008 11:49:05 +00:00 c1130-k9w8-mx.124-3g.JA2
5 drwx 128 Mar 01 2002 00:03:43 +00:00 c1130-rcvk9w8-mx

15998976 bytes total (10716672 bytes free)


Then delete the LWAPP image:
lap_1131#delete /r /f flash:/c11310-k9w8-mx.124-3g.JA2

Not the one the has rcv in it!!!!!!


Thirdly reload the AP:
lap_1131#reload

Then issue a clear lwapp private-config

You'll end up with a clear AP.

*****************************************************************

Option 2 - If there in no rcv image

delete /r /f flash:private-multiple-fs

Then reload the LAP.

Here is a link to another thread:

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

Peter Nugent Sat, 03/27/2010 - 10:37

Discovered where the issue lies. The US WLC has master mode enabled, disabled that

everything started working, the ap had homed to the US but then stranded itself. Recommended that the client actually gets the whole thing archetected properly

rob.huffman Sun, 03/28/2010 - 07:54

Hi Pete,

Thanks for following up with your resolution here! +5 points

this good gesture.

Cheers!

Rob

Peter Nugent Sun, 03/28/2010 - 08:07

Many thanks Rob, love the forums and its a great place to bounce ideas around, not here for the points, Im never going tto catch guys like you but feel that I can contribute a little and when you get weird stuff it may help someone in the future

rob.huffman Mon, 03/29/2010 - 06:45

Hey Pete,

You are right on the money my friend it's about

helping each other out while working through this

crazy stuff! That's why the kind follow-up like yours here

is most appreciated.

Cheers!

Rob

Actions

This Discussion