AP1141 rebooting constantly

Unanswered Question
Oct 12th, 2010
User Badges:

Hi


I have a set up with an 5508 controller and some AP1141.

i get this in the log


LogSystem TimeTrap
0Tue Oct 12 14:50:23 2010AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:e8:04:62:60:76:50 Cause=Radio reset due to Init. Status:NA
1Tue Oct 12 14:50:23 2010AP 'APf866.f292.b28e', MAC: e8:04:62:60:76:50 disassociated previously due to AP Reset. Uptime: 0 days, 00 h 26 m 38 s . Last reset reason: power loss.
2Tue Oct 12 14:50:23 2010AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:e8:04:62:0b:41:20 Cause=Radio interface reset. Status:NA
3Tue Oct 12 14:50:23 2010AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:e8:04:62:0b:41:20 Cause=Radio interface reset. Status:NA
4Tue Oct 12 14:50:20 2010AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:e8:04:62:0b:41:20 Cause=Radio reset due to Init. Status:NA
5Tue Oct 12 14:50:20 2010AP 'APf866.f292.b2f2', MAC: e8:04:62:0b:41:20 disassociated previously due to AP Reset. Uptime: 0 days, 00 h 26 m 44 s . Last reset reason: power loss.
6Tue Oct 12 14:49:52 2010AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:e8:04:62:60:84:10 Cause=Radio interface reset. Status:NA
7Tue Oct 12 14:49:52 2010AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:e8:04:62:60:84:10 Cause=Radio interface reset. Status:NA
8Tue Oct 12 14:49:49 2010AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:e8:04:62:60:84:10 Cause=Radio reset due to Init. Status:NA
9Tue Oct 12 14:49:48 2010AP 'APf866.f2d7.8a61', MAC: e8:04:62:60:84:10 disassociated previously due to AP Reset. Uptime: 0 days, 00 h 26 m 37 s . Last reset reason: power loss.
10Tue Oct 12 14:49:48 2010AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:e8:04:62:60:7e:70 Cause=Radio interface reset. Status:NA
11Tue Oct 12 14:49:48 2010AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:e8:04:62:60:7e:70 Cause=Radio interface reset. Status:NA
12Tue Oct 12 14:49:45 2010AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:e8:04:62:60:7e:70 Cause=Radio reset due to Init. Status:NA
13Tue Oct 12 14:49:45 2010AP 'APf866.f2ab.2fc5', MAC: e8:04:62:60:7e:70 disassociated previously due to AP Reset. Uptime: 0 days, 00 h 26 m 38 s . Last reset reason: power loss.
14Tue Oct 12 14:49:30 2010AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:a8:b1:d4:9d:1a:b0 Cause=Radio interface reset. Status:NA
15Tue Oct 12 14:49:30 2010AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:a8:b1:d4:9d:1a:b0 Cause=Radio interface reset. Status:NA
16Tue Oct 12 14:49:30 2010AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:58:bc:27:be:14:40 Cause=Radio interface reset. Status:NA
17Tue Oct 12 14:49:30 2010AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:58:bc:27:be:14:40 Cause=Radio interface reset. Status:NA
18Tue Oct 12 14:49:27 2010AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:a8:b1:d4:9d:1a:b0 Cause=Radio reset due to Init. Status:NA
19Tue Oct 12 14:49:27 2010AP 'APc84c.75ed.fad0', MAC: a8:b1:d4:9d:1a:b0 disassociated previously due to AP Reset. Uptime: 0 days, 00 h 26 m 43 s . Last reset reason: power loss.


The ap's are powered from a 3560 poe switch, have movet the ap's to another switch, same problem

Controller is running 7.0.98.0


Any ideas hwat could be causing this ?


Per Buch

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (5 ratings)
Loading.
Tiago Antunes Tue, 10/12/2010 - 06:52
User Badges:
  • Cisco Employee,

Hi,


This would mean the switch is shutting down the port so I would look into the switch logs why is that happening.


HTH,

Tiago

pbuch Tue, 10/12/2010 - 06:54
User Badges:

There is nothing in the switch log

Leo Laohoo Tue, 10/12/2010 - 17:49
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

The information is not enough.  When the AP joins to the WLC, what is it doing?  Is it (continuous) downloading an image?

pbuch Tue, 10/12/2010 - 19:22
User Badges:

The image is downloaded, AP's are associated and should just be in a normal running state.

George Stefanick Tue, 10/12/2010 - 19:45
User Badges:
  • Purple, 4500 points or more
  • Community Spotlight Award,

    Best Publication, October 2015

Did you get this log by console or logging? Plug into the AP with the console and reboot the ap and collect that information,

pbuch Tue, 10/12/2010 - 22:42
User Badges:

The log is from the controller.

I will try to get a consolelog, but i am not onsite right now.

Tiago Antunes Wed, 10/13/2010 - 00:11
User Badges:
  • Cisco Employee,

I agree, plugging a conolse cable into the AP and getting the logs would give us more info.

However, the switch should also have logs, at least interface down-up...


As this is over PoE, i would advise toconnet to the switch (console or telnet), make sure logging is on and the switch i sending the logs on the screen (term mon) and run the following debugs on the PoE switch:


debug ilpower event

debug ilpower cdp


If we have the AP console debugs and the switch PoE debugs maybe we can find something...

pbuch Fri, 10/15/2010 - 01:05
User Badges:

This is from the AP Console


*Oct 15 07:41:44.073: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.
1.2.100:5246
*Oct 15 07:41:44.110: %WIDS-6-DISABLED: IDS Signature is removed and disabled.
*Oct 15 07:41:44.112: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Oct 15 07:41:44.112: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Oct 15 07:41:44.158: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to a
dministratively down
*Oct 15 07:41:44.168:  status of voice_diag_test from WLC is false
*Oct 15 07:41:44.168: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Oct 15 07:41:44.176: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to r
eset
*Oct 15 07:41:44.190: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Oct 15 07:41:54.168: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Oct 15 07:41:44.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_i
p: 10.1.2.100 peer_port: 5246
*Oct 15 07:41:44.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Oct 15 07:41:44.833: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully
peer_ip: 10.1.2.100 peer_port: 5246
*Oct 15 07:41:44.834: %CAPWAP-5-SENDJOIN: sending Join Request to 10.1.2.100
*Oct 15 07:41:44.834: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Oct 15 07:41:44.953: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
*Oct 15 07:41:45.067: %CAPWAP-5-CHANGED: CAPWAP changed state to UP
*Oct 15 07:41:45.106: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller WLC55
08-1
*Oct 15 07:41:45.152: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to r
eset
*Oct 15 07:41:45.154: %LWAPP-3-CLIENTEVENTLOG: SSID JellingBib added to the slot
[0]
*Oct 15 07:41:45.169: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Oct 15 07:43:54.702: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.1.2.100:5246
*Oct 15 07:43:54.741: %WIDS-6-DISABLED: IDS Signature is removed and disabled.
*Oct 15 07:43:54.742: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Oct 15 07:43:54.743: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Oct 15 07:43:54.790: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively
down
*Oct 15 07:43:54.800:  status of voice_diag_test from WLC is false
*Oct 15 07:43:54.800: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Oct 15 07:43:54.808: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Oct 15 07:43:54.822: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Oct 15 07:44:04.799: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Oct 15 07:43:55.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.1.2.100 pe
er_port: 5246
*Oct 15 07:43:55.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Oct 15 07:43:55.835: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.1.2
.100 peer_port: 5246
*Oct 15 07:43:55.836: %CAPWAP-5-SENDJOIN: sending Join Request to 10.1.2.100
*Oct 15 07:43:55.836: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Oct 15 07:43:55.954: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
*Oct 15 07:43:56.064: %CAPWAP-5-CHANGED: CAPWAP changed state to UP
*Oct 15 07:43:56.103: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller WLC5508-1
*Oct 15 07:43:56.148: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Oct 15 07:43:56.149: %LWAPP-3-CLIENTEVENTLOG: SSID JellingBib added to the slot[0]
*Oct 15 07:43:56.164: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

Tiago Antunes Fri, 10/15/2010 - 01:32
User Badges:
  • Cisco Employee,

Ok, so we have interesting logs:


*Oct 15 07:41:45.169: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Oct 15 07:43:54.702: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.1.2.100:5246


This shows the Ap joined to the WLC, then after 2 mins it gets a DTLS error and the connection is closed...

Is this AP located in a remote site and the connection is done via WAN?


I have seen this when the AP manager interface is not reachable, when the connection is slow and the dtls keepalives are lost, when the country code is incorrect, etc...but here it stays connected for 2 mins...so we need to check on the WLC debugs why the connection breaks...

Now it is time to check if we have similar messages on the debugs of the WLC.


Can you please enable the following debugs on the WLC:


debug mac address

debug capwap events enable

debug capwap errors enable
debug capwap dtls-keepalive enable


then let's see what the WLC says...


Thanks,

Tiago


--

If this answers your question please mark the question as "answered" and rate it, so other users can easily find it.

pbuch Fri, 10/15/2010 - 02:08
User Badges:

Its on a remote location with a 100Mbit fiber connection.

I have enablet the debugs on the controller via telnet, but nothing shows.

Is there a "ter mon" command ?

Tiago Antunes Fri, 10/15/2010 - 02:18
User Badges:
  • Cisco Employee,

Nope, you should be able to get everything even on telnet...

Are you sure you typed the correct mac address?

if you remove the mac address filter command, do you see anything?

pbuch Fri, 10/15/2010 - 02:44
User Badges:

It should be the mac of the radio interface



(Cisco Controller) >*spamApTask5: Oct 15 11:40:52.245: a8:b1:d4:9d:2f:d0 Primary
Discovery Request from 10.73.1.156:57297

*spamApTask0: Oct 15 11:40:52.245: a8:b1:d4:9d:2f:d0 Received LWAPP PRIMARY_DISC
OVERY_REQ from AP
*spamApTask5: Oct 15 11:40:52.246: a8:b1:d4:9d:2f:d0 Primary Discovery Response
sent to  10.73.1.156:57297

*spamApTask5: Oct 15 11:40:52.285: a8:b1:d4:9d:2f:d0 DTLS keys for Control Plane
deleted successfully for AP 10.73.1.156

*spamApTask5: Oct 15 11:40:52.286: a8:b1:d4:9d:2f:d0 DTLS connection was closed
*spamApTask5: Oct 15 11:40:52.286: a8:b1:d4:9d:2f:d0 DTLS connection closed even
t receivedserver (10:1:2:100/5246) client (10:73:1:156/57297)
*spamApTask5: Oct 15 11:40:52.286: a8:b1:d4:9d:2f:d0 Entry exists for AP (10:73:
1:156/57297)
*spamApTask5: Oct 15 11:40:52.286: a8:b1:d4:9d:2f:d0 apfSpamProcessStateChangeIn
SpamContext: Deregister LWAPP event for AP a8:b1:d4:9d:2f:d0 slot 0
*apfReceiveTask: Oct 15 11:40:52.286: a8:b1:d4:9d:2f:d0 Deregister LWAPP event f
or AP a8:b1:d4:9d:2f:d0 slot 0
*spamApTask6: Oct 15 11:40:52.383: a8:b1:d4:9d:2f:d0 Discovery Request from 10.7
3.1.156:57298

*spamApTask6: Oct 15 11:40:52.383: a8:b1:d4:9d:2f:d0 Join Priority Processing st
atus = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =3
*spamApTask6: Oct 15 11:40:52.383: a8:b1:d4:9d:2f:d0 Discovery Response sent to
10.73.1.156:57298

*spamReceiveTask: Oct 15 11:40:59.785: spamProcessGlobalPathMtuUpdate: Changing
Global LRAD MTU to 576

*spamApTask6: Oct 15 11:41:02.384: a8:b1:d4:9d:2f:d0 DTLS connection not found,
creating new connection for 10:73:1:156 (57298) 10:1:2:100 (5246)

*spamApTask6: Oct 15 11:41:03.217: a8:b1:d4:9d:2f:d0 Allocated index from main l
ist, Index: 18

*spamApTask6: Oct 15 11:41:03.217: a8:b1:d4:9d:2f:d0 DTLS keys for Control Plane
are plumbed successfully for AP 10.73.1.156. Index 19

*spamApTask6: Oct 15 11:41:03.218: a8:b1:d4:9d:2f:d0 DTLS Session established se
rver (10.1.2.100:5246), client (10.73.1.156:57298)
*spamApTask6: Oct 15 11:41:03.218: a8:b1:d4:9d:2f:d0 Starting wait join timer fo
r AP: 10.73.1.156:57298

*spamApTask6: Oct 15 11:41:03.221: a8:b1:d4:9d:2f:d0 Join Request from 10.73.1.1
56:57298

*spamApTask6: Oct 15 11:41:03.221: a8:b1:d4:9d:2f:d0 Join Version: = 117465600

*spamApTask6: Oct 15 11:41:03.221: a8:b1:d4:9d:2f:d0 Join resp: CAPWAP Maximum M
sg element len = 86

*spamApTask6: Oct 15 11:41:03.222: a8:b1:d4:9d:2f:d0 Join Response sent to 10.73
.1.156:57298

*spamApTask6: Oct 15 11:41:03.222: a8:b1:d4:9d:2f:d0 CAPWAP State: Join

*spamApTask6: Oct 15 11:41:03.222: a8:b1:d4:9d:2f:d0 capwap_ac_platform.c:1216 -
Operation State 0 ===> 4
*apfReceiveTask: Oct 15 11:41:03.222: a8:b1:d4:9d:2f:d0 Register LWAPP event for
AP a8:b1:d4:9d:2f:d0 slot 0
*apfReceiveTask: Oct 15 11:41:03.223: WARP IEs: (12)

*apfReceiveTask: Oct 15 11:41:03.223:      [0000] dd 0a 00 c0 b9 01 00 00 00 08
01 01

*spamApTask6: Oct 15 11:41:03.338: a8:b1:d4:9d:2f:d0 Configuration Status from 1
0.73.1.156:57298

*spamApTask6: Oct 15 11:41:03.338: a8:b1:d4:9d:2f:d0 CAPWAP State: Configure

*spamApTask6: Oct 15 11:41:03.338: a8:b1:d4:9d:2f:d0 Updating IP info for AP a8:
b1:d4:9d:2f:d0 -- static 0, 10.73.1.156/255.255.255.0, gtw 10.73.1.1
*spamApTask6: Oct 15 11:41:03.338: a8:b1:d4:9d:2f:d0 Updating IP 10.73.1.156 ===
> 10.73.1.156 for AP a8:b1:d4:9d:2f:d0
*spamApTask6: Oct 15 11:41:03.338: a8:b1:d4:9d:2f:d0 Setting MTU to 1485
*spamApTask6: Oct 15 11:41:03.394: a8:b1:d4:9d:2f:d0 Configuration Status Respon
se sent to 10:73:1:156

*spamApTask6: Oct 15 11:41:03.485: a8:b1:d4:9d:2f:d0 Change State Event Request
from 10.73.1.156:57298

*apfReceiveTask: Oct 15 11:41:03.485: a8:b1:d4:9d:2f:d0 Received LWAPP Up event
for AP a8:b1:d4:9d:2f:d0 slot 0!
*spamApTask6: Oct 15 11:41:03.485: a8:b1:d4:9d:2f:d0 Radio state change for slot
: 0 state: 2 cause: 0 detail cause: 72
*spamApTask6: Oct 15 11:41:03.486: a8:b1:d4:9d:2f:d0 Change State Event Response
sent to 10.73.1.156:57298

*spamApTask6: Oct 15 11:41:03.486: a8:b1:d4:9d:2f:d0 CAPWAP State: Run

*spamApTask6: Oct 15 11:41:03.486: a8:b1:d4:9d:2f:d0 Sending the remaining confi
g to AP 10.73.1.156:57298

*spamApTask6: Oct 15 11:41:03.486: a8:b1:d4:9d:2f:d0 Configuration update reques
t for Init VAP-DATA for slot 0 sent to 10.73.1.156:57298

*spamApTask6: Oct 15 11:41:03.486: a8:b1:d4:9d:2f:d0 Configuration update reques
t for configuring association limit params sent to 10.73.1.156:57298

*spamApTask6: Oct 15 11:41:03.487: a8:b1:d4:9d:2f:d0 Configuration update reques
t for Band Select Cfg sent to 10.73.1.156:57298

*spamApTask6: Oct 15 11:41:03.487: a8:b1:d4:9d:2f:d0 Configuration update reques
t for HaConfig message sent to 10.73.1.156:57298

*spamReceiveTask: Oct 15 11:41:03.487: a8:b1:d4:9d:2f:d0 Configuration update re
quest for PHY payload sent to 10:73:1:156

*spamReceiveTask: Oct 15 11:41:03.487: a8:b1:d4:9d:2f:d0 Configuration update re
quest for RrmInterferenceCtrl payload sent to 10:73:1:156

*spamReceiveTask: Oct 15 11:41:03.487: a8:b1:d4:9d:2f:d0 Configuration update re
quest for RrmNeighbourCtrl payload sent to 10.73.1.156

*spamReceiveTask: Oct 15 11:41:03.487: a8:b1:d4:9d:2f:d0 Configuration update re
quest for RrmReceiveCtrl payload sent to 10:73:1:156

*spamReceiveTask: Oct 15 11:41:03.487: a8:b1:d4:9d:2f:d0 Configuration update re
quest for CcxRmMeas payload sent to 10.73.1.156

*spamApTask6: Oct 15 11:41:03.531: a8:b1:d4:9d:2f:d0 WTP Event Request from 10.7
3.1.156:57298

*spamApTask6: Oct 15 11:41:03.531: a8:b1:d4:9d:2f:d0 WTP Event Response sent to
10.73.1.156:57298

*spamApTask6: Oct 15 11:41:03.532: a8:b1:d4:9d:2f:d0 Configuration Update Respon
se from 10.73.1.156:57298

*spamApTask6: Oct 15 11:41:03.536: a8:b1:d4:9d:2f:d0 WTP Event Request from 10.7
3.1.156:57298

*spamApTask6: Oct 15 11:41:03.536: a8:b1:d4:9d:2f:d0 WTP Event Response sent to
10.73.1.156:57298

*spamApTask6: Oct 15 11:41:03.537: a8:b1:d4:9d:2f:d0 Configuration Update Respon
se from 10.73.1.156:57298

*spamApTask6: Oct 15 11:41:03.539: a8:b1:d4:9d:2f:d0 WTP Event Request from 10.7
3.1.156:57298

*spamApTask6: Oct 15 11:41:03.539: a8:b1:d4:9d:2f:d0 Updated Link Latency contro
l for AP a8:b1:d4:9d:2f:d0
*spamApTask6: Oct 15 11:41:03.539: a8:b1:d4:9d:2f:d0 WTP Event Response sent to
10.73.1.156:57298

*spamApTask6: Oct 15 11:41:03.539: a8:b1:d4:9d:2f:d0 Configuration Update Respon
se from 10.73.1.156:57298

*spamApTask6: Oct 15 11:41:03.540: a8:b1:d4:9d:2f:d0 WTP Event Request from 10.7
3.1.156:57298

*spamApTask6: Oct 15 11:41:03.541: a8:b1:d4:9d:2f:d0 Configuration Update Respon
se from 10.73.1.156:57298

*spamApTask6: Oct 15 11:41:03.543: a8:b1:d4:9d:2f:d0 Configuration Update Respon
se from 10.73.1.156:57298

*spamApTask6: Oct 15 11:41:03.547: a8:b1:d4:9d:2f:d0 Configuration Update Respon
se from 10.73.1.156:57298

*spamApTask6: Oct 15 11:41:03.549: a8:b1:d4:9d:2f:d0 Configuration Update Respon
se from 10.73.1.156:57298

*spamApTask6: Oct 15 11:41:03.551: a8:b1:d4:9d:2f:d0 Configuration Update Respon
se from 10.73.1.156:57298

*spamApTask6: Oct 15 11:41:03.553: a8:b1:d4:9d:2f:d0 Configuration Update Respon
se from 10.73.1.156:57298

*spamApTask6: Oct 15 11:41:03.555: a8:b1:d4:9d:2f:d0 Configuration Update Respon
se from 10.73.1.156:57298

*spamApTask6: Oct 15 11:41:04.700: a8:b1:d4:9d:2f:d0 Configuration Update Respon
se from 10.73.1.156:57298

pbuch Fri, 10/15/2010 - 03:04
User Badges:

Changed "AP Primary Discovery Timeout" from 120 to 1200

Looks like it makes a difference.

Tiago Antunes Fri, 10/15/2010 - 03:30
User Badges:
  • Cisco Employee,

Hi,


IOn the debugs we don't any disconnect event...maybe you debugged it not long enough...

Can you run the debugs from ~5 mins making sure the AP disconnects during that time so we have the logs regarding a disconnection?

Athonia Cappelli Thu, 06/21/2012 - 07:52
User Badges:

I'm seeing the same error message in the WLC and the symptom users are seeing is that the SSID advertisement goes away causing their connection to flap.  We have a new 2504 with four 1142n lightweight AP.


I'm running a very recent version:   AIR-CT2500-K9-7-2-110-0.aes


The APs are not actually rebooting and there are no log entires on the 3750g PoE switch. WE do have the CISCO-CAPWAP-CONTROLLER DNS entry setup properly.


This wlc has been working perfectly for two months since I first installed it. It's just recently started acting up. Any ideas?


Here are the logs from the last few minutes:


1Thu Jun 21 14:42:52 2012AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:27:0d:48:e5:00 Cause=Radio interface reset. Status:NA
2Thu Jun 21 14:42:52 2012AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:27:0d:48:e5:00 Cause=Radio interface reset. Status:NA
3Thu Jun 21 14:42:49 2012AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:27:0d:48:e5:00 Cause=Unknown Reset Status:NA
4Thu Jun 21 14:42:48 2012AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:27:0d:48:e5:00 Cause=Unknown Reset Status:NA
5Thu Jun 21 14:42:47 2012AP '1014ConferenceRoom', MAC: 00:27:0d:48:e5:00 disassociated previously due to AP Reset. Uptime: 0 days, 12 h 18 m 39 s . Last reset reason: operator changed 11g mode.
6Thu Jun 21 14:42:36 2012AP Disassociated. Base Radio MAC:00:27:0d:48:e5:00
7Thu Jun 21 14:42:36 2012AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:27:0d:48:e5:00 Cause=New Discovery Status:NA
Leo Laohoo Sat, 12/01/2012 - 00:38
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

Try upgrading to 7.3.101.0.

Alessandro Bertacco Fri, 11/26/2010 - 06:55
User Badges:

Hi all, same problem Here, with WLC4402 25 AP Firmware version



7.0.98.0. There is 14 AP


1242AG connected in LAN and power used Cisco poe switch 3560 and 296

0. Today Customer want to add another Ap1242AG power with PoE, The AP downloaded correctly the fir

mware from controller register and constantly reset with these log


Fri Nov 26 15:56:06 2010AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:3a:99:13:1a:30 Cause=Radio interface reset. Status:NA 1Fri Nov 26 15:56:06 2010AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:3a:99:13:1a:30 Cause=Radio interface reset. Status:NA 2Fri Nov 26 15:56:06 2010AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:00:3a:99:13:1a:30 Cause=Radio interface reset. Status:NA 3Fri Nov 26 15:56:06 2010AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:3a:99:13:1a:30 Cause=Radio interface reset. Status:NA 4Fri Nov 26 15:56:03 2010AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:00:3a:99:13:1a:30 Cause=Radio reset due to Init. Status:NA 5Fri Nov 26 15:56:03 2010AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:3a:99:13:1a:30 Cause=Radio reset due to Init. Status:NA 6Fri Nov 26 15:56:03 2010AP 'AP07', MAC: 00:3a:99:13:1a:30 disassociated previously due to AP Reset. Uptime: 0 days, 00 h 37 m 35 s . Last reset reason: power loss.



I've change port, switch and AP with new one. Same Problem. Only with the new AP Added. I'm desperate, and I'don't have Smartnet.


Please Help!!


Thank you


Alessandro

bashir.rabbani Wed, 12/01/2010 - 06:19
User Badges:

Hi


Any solution on this problem?


/* Style Definitions */ table.MsoNormalTable {mso-style-name:"Normal tabell"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} One customer running 7.0.98.0  have the same problem.  The controllers are upgraded from 5.2.178 and after the upgrade all new AP reboots constantly. Haven't debugged it yet, just searching around for this error. Controllers used are 5508, 4404 and 4402...


Best regards

pbuch Wed, 12/01/2010 - 06:22
User Badges:

Solved mine by doing af reset to factory default, and reconfigure

bashir.rabbani Fri, 12/03/2010 - 00:42
User Badges:
/* Style Definitions */ table.MsoNormalTable {mso-style-name:"Normal tabell"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin-top:0cm; mso-para-margin-right:0cm; mso-para-margin-bottom:10.0pt; mso-para-margin-left:0cm; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;}

Solved mine as well. Just debugged the AP and got this message:

%CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER.xxxxx.xx

Added the cisco-capwap-controller in the DNS..

florinanor Thu, 11/08/2012 - 07:52
User Badges:

I had the same problem, but with an 1242 AP, 2106 wlc and 7.0.235 code. The log was the same


AP 'yyyyyy, MAC: 00:1c:0f:xxxxx disassociated previously due to AP Reset. Uptime: 0 days, 00 h 11 m 58 s . Last reset reason: power loss.


, but the AP did not restart at all, only disconected from the controller. I soved my problem by putting the name and the IP of the controller in AP->hight availability tab.

Maybe it will help.

Sebastian Helmer Sat, 12/01/2012 - 00:13
User Badges:
  • Silver, 250 points or more

Did you check the "Power Over Ethernet Settings" on the AP settings gui? Inthe past that was one of my problem..

Actions

This Discussion