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

Attention: The Cisco Support Community site will be in read only mode on Dec14, 2017 from 12:01am PST to 11:30am for standard maintenance. Sorry for the inconvenience.

New Member

Reason for association 'Dot11g Mode Change '.

Hi

I got a few messages during a day that APs have been gone down:

2. Message: 802.11b/g interface of AP MYAP is down: Controller 10.15.15.15

A few minutes later the AP came back to the controller with the message:

4. Message: Access Point 'MYAP' associated to controller '10.15.15.15' on port number '0'. Reason for association 'Dot11g Mode Change '.

WISM and WCS are 7.0.220.

APs are type 3502i and 1141.

need some help on why this happened....anyone?

13 REPLIES
New Member

Reason for association 'Dot11g Mode Change '.

I'm also having the same issue, I have 75 APs in all, the only APs being affected though are my Local APs. None of them reset, they just disassociate and then associate again. Same log entry Message: Access Point associated to controller 'X.X.X.X' on port number '0'. Reason for association 'Dot11g Mode Change '.

What's strange is it's not just one, it's all my local APs, except for 2.

The difference is that the 2 are on Gigabit uplink ports the rest are on 100Mb, we dont have Gig switches in other closets yet. Related?

HREAP APs dont flip to standalone they continue to see controller fine, those are also on 100Mb switches.

WLC 5508

Ver 7.0.116

3/8 ports are connected to our backbone.

WCS 7.0.172.0

All APs are C3502E

I also noticed that 11n is enabled and 40MHz channel width with extended channels, this would turn on 300Mbps throughput but if the APs are connected to 100Mb switches, it doesn't make sense to turn on 11n. Could this be related.

Hall of Fame Super Silver

Re: Reason for association 'Dot11g Mode Change '.

Seems like you sort isolated the problem. I would try the set the speed and duplex on the switchport and AP to 100 full and see if that fixes the issue. Only test with one or a few at first. I was doing some testing a couple days ago with an 1131 and that ap was disassociating from the wlc because it was connected to a 10/100 unmanaged switch. But since we were testing, we didn't care to much. In h-reap, the ap had no problems.

Thanks,

Scott Fella

Sent from my iPhone

-Scott
*** Please rate helpful posts ***
New Member

Reason for association 'Dot11g Mode Change '.

Thanks Scott, well we haven't had the issue again but have now turned on debugs on our controller and 1 of the 35 Local APs are being monitored.

I've also changed the switchport that one of the APs is connected to, I added the switch port allowed vlan and only allowing the vlans that correspond with our WLANs.

Now just waiting for the problem to re-occur.

New Member

Re: Reason for association 'Dot11g Mode Change '.

what kind of debugging do you have configured? the problem occours hourly on my APs perhaps we can get results earlyer..

New Member

Reason for association 'Dot11g Mode Change '.

Turn on these debugs on your controller:

config session timout 0

debug mac addr xx:xx:xx:xx:xx:xx (MAC of AP)

debug capwap events enable

debug capwap errors enable

Turn on these debugs on the AP, connect to it via console:

No exec-timeout

Debug capwap client events

Debug capwap client errors

Once you collect the debugs not sure what more help I can provide but maybe there will be a clue there? :-)

Post when you can.

New Member

Re: Reason for association 'Dot11g Mode Change '.

lthere was nothing special on the controller debug...

attached the log sniped from the ap. 

there are a few wired things like:

*Feb  7 13:44:50.077: %CAPWAP-3-EVENTLOG: Max retransmission count exceeded going back to DISCOVER mode.

*Feb  7 13:44:50.077: %CAPWAP-3-EVENTLOG: The function which Posted the message to send out of the box is capwap_hreap_fault_client_inf and of Type=64

or:

*Feb  7 13:44:47.076: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message.

*Feb  7 13:44:47.076: %CAPWAP-3-ERRORLOG: Failed to handle timer message.

*Feb  7 13:44:47.076: %CAPWAP-3-ERRORLOG: Failed to process Message timer message.

*Feb  7 13:44:47.076: %CAPWAP-3-ERRORLOG: Message timeout timer expiry handler failed.

*Feb  7 13:44:50.077: %CAPWAP-3-EVENTLOG: Retransmission Count= 5 Max Re-Transmission Value=5

*Feb  7 13:44:50.077: %CAPWAP-3-EVENTLOG: Max retransmission count exceeded going back to DISCOVER mode.

*Feb  7 13:44:50.077: %CAPWAP-3-EVENTLOG: The function which Posted the message to send out of the box is capwap_hreap_fault_client_inf and of Type=64

*Feb  7 13:44:50.077: %CAPWAP-3-EVENTLOG: Retransmission count for packet exceeded max(CAPWAP_WTP_EVENT_REQUEST

., 6)

*Feb  7 13:44:50.077: %LWAPP-3-CLIENTEVENTLOG: Switching to Standalone mode

*Feb  7 13:44:50.080: %CAPWAP-3-EVENTLOG: GOING BACK TO DISCOVER MODE

*Feb  7 13:44:50.149: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.31.127.61:5246

*Feb  7 13:44:50.152: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.

At the end my ssh session gets closed but the uptime is still around 19 hours...

OM: Bootstrap program is C3500 boot loader

BOOTLDR: C3500 Boot Loader (AP3G1-BOOT-M) Version 12.4(23c)JA, RELEASE SOFTWARE (fc3)

zug-meta-f1 uptime is 19 hours, 38 minutes

System returned to ROM by reload

System image file is "flash:/ap3g1-k9w8-mx.124-23c.JA2/ap3g1-k9w8-mx.124-23c.JA2"

Last reload reason:

Full log:

*Feb  7 13:44:29.630: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:44:29.803: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:44:29.803: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:44:29.815: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:44:29.815: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:44:29.828: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:44:29.831: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:44:29.844: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:44:29.847: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:44:32.033: %CAPWAP-3-EVENTLOG: Retransmission Count= 0 Max Re-Transmission Value=5

*Feb  7 13:44:32.033: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:44:32.046: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:44:32.046: %CAPWAP-3-EVENTLOG: Wtp Event Response from 10.31.127.61

*Feb  7 13:44:32.058: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:44:32.058: %CAPWAP-3-EVENTLOG: Wtp Event Response from 10.31.127.61

*Feb  7 13:44:32.071: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:44:32.071: %CAPWAP-3-ERRORLOG: Failed to send packet from queue

*Feb  7 13:44:32.071: %CAPWAP-3-ERRORLOG: Failed to send message from queue.

*Feb  7 13:44:32.071: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Feb  7 13:44:32.071: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 10.31.127.61

*Feb  7 13:44:35.072: %CAPWAP-3-EVENTLOG: Retransmission Count= 0 Max Re-Transmission Value=5

*Feb  7 13:44:35.072: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:44:35.072: %CAPWAP-3-ERRORLOG: Failed to send packet from queue

*Feb  7 13:44:35.072: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message.

*Feb  7 13:44:35.072: %CAPWAP-3-ERRORLOG: Failed to handle timer message.

*Feb  7 13:44:35.072: %CAPWAP-3-ERRORLOG: Failed to process Message timer message.

*Feb  7 13:44:35.072: %CAPWAP-3-ERRORLOG: Message timeout timer expiry handler failed.

*Feb  7 13:44:37.717: %CLEANAIR-5-STATE: Slot 0 disabled

*Feb  7 13:44:37.717: %CLEANAIR-5-STATE: Slot 1 disabled

*Feb  7 13:44:38.073: %CAPWAP-3-EVENTLOG: Retransmission Count= 1 Max Re-Transmission Value=5

*Feb  7 13:44:38.073: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:44:38.073: %CAPWAP-3-ERRORLOG: Failed to send packet from queue

*Feb  7 13:44:38.073: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message.

*Feb  7 13:44:38.073: %CAPWAP-3-ERRORLOG: Failed to handle timer message.

*Feb  7 13:44:38.073: %CAPWAP-3-ERRORLOG: Failed to process Message timer message.

*Feb  7 13:44:38.073: %CAPWAP-3-ERRORLOG: Message timeout timer expiry handler failed.

*Feb  7 13:44:39.948: %CAPWAP-3-EVENTLOG: Config update:Ap CDP cache payload sent to 10:31:127:61

*Feb  7 13:44:41.074: %CAPWAP-3-EVENTLOG: Retransmission Count= 2 Max Re-Transmission Value=5

*Feb  7 13:44:41.074: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:44:41.074: %CAPWAP-3-ERRORLOG: Failed to send packet from queue

*Feb  7 13:44:41.074: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message.

*Feb  7 13:44:41.074: %CAPWAP-3-ERRORLOG: Failed to handle timer message.

*Feb  7 13:44:41.074: %CAPWAP-3-ERRORLOG: Failed to process Message timer message.

*Feb  7 13:44:41.074: %CAPWAP-3-ERRORLOG: Message timeout timer expiry handler failed.

*Feb  7 13:44:44.075: %CAPWAP-3-EVENTLOG: Retransmission Count= 3 Max Re-Transmission Value=5

*Feb  7 13:44:44.075: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:44:44.075: %CAPWAP-3-ERRORLOG: Failed to send packet from queue

*Feb  7 13:44:44.075: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message.

*Feb  7 13:44:44.075: %CAPWAP-3-ERRORLOG: Failed to handle timer message.

*Feb  7 13:44:44.075: %CAPWAP-3-ERRORLOG: Failed to process Message timer message.

*Feb  7 13:44:44.075: %CAPWAP-3-ERRORLOG: Message timeout timer expiry handler failed.

*Feb  7 13:44:47.076: %CAPWAP-3-EVENTLOG: Retransmission Count= 4 Max Re-Transmission Value=5

*Feb  7 13:44:47.076: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:44:47.076: %CAPWAP-3-ERRORLOG: Failed to send packet from queue

*Feb  7 13:44:47.076: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message.

*Feb  7 13:44:47.076: %CAPWAP-3-ERRORLOG: Failed to handle timer message.

*Feb  7 13:44:47.076: %CAPWAP-3-ERRORLOG: Failed to process Message timer message.

*Feb  7 13:44:47.076: %CAPWAP-3-ERRORLOG: Message timeout timer expiry handler failed.

*Feb  7 13:44:50.077: %CAPWAP-3-EVENTLOG: Retransmission Count= 5 Max Re-Transmission Value=5

*Feb  7 13:44:50.077: %CAPWAP-3-EVENTLOG: Max retransmission count exceeded going back to DISCOVER mode.

*Feb  7 13:44:50.077: %CAPWAP-3-EVENTLOG: The function which Posted the message to send out of the box is capwap_hreap_fault_client_inf and of Type=64

*Feb  7 13:44:50.077: %CAPWAP-3-EVENTLOG: Retransmission count for packet exceeded max(CAPWAP_WTP_EVENT_REQUEST

., 6)

*Feb  7 13:44:50.077: %LWAPP-3-CLIENTEVENTLOG: Switching to Standalone mode

*Feb  7 13:44:50.080: %CAPWAP-3-EVENTLOG: GOING BACK TO DISCOVER MODE

*Feb  7 13:44:50.149: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.31.127.61:5246

*Feb  7 13:44:50.152: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.

*Feb  7 13:44:50.156: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. Restarting capwap state machine.

*Feb  7 13:44:50.225: %WIDS-5-DISABLED: IDS Signature is removed and disabled.

*Feb  7 13:44:50.225: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Feb  7 13:44:50.225: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Feb  7 13:44:50.225: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Feb  7 13:44:50.225: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117470208

*Feb  7 13:44:50.225: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.31.127.41 with discovery type set to 1

*Feb  7 13:44:50.225: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117470208

*Feb  7 13:44:50.225: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.31.127.45 with discovery type set to 1

*Feb  7 13:44:50.225: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117470208

*Feb  7 13:44:50.225: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.31.127.61 with discovery type set to 1

*Feb  7 13:44:50.225: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117470208

*Feb  7 13:44:50.225: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.8.127.61 with discovery type set to 1

*Feb  7 13:44:50.225: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117470208

*Feb  7 13:44:50.225: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.31.127.31 with discovery type set to 1

*Feb  7 13:44:50.228: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117470208

*Feb  7 13:44:50.228: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.31.127.35 with discovery type set to 1

*Feb  7 13:44:50.228: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117470208

*Feb  7 13:44:50.228: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.31.127.21 with discovery type set to 1

*Feb  7 13:44:50.228: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117470208

*Feb  7 13:44:50.228: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.31.127.25 with discovery type set to 1

*Feb  7 13:44:50.228: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117470208

*Feb  7 13:44:50.228: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.255 with discovery type set to 0

*Feb  7 13:44:50.237: %CAPWAP-3-EVENTLOG: Discovery Response from 10.31.127.41

*Feb  7 13:44:50.237: %CAPWAP-3-EVENTLOG: Discovery Response from 10.31.127.45

*Feb  7 13:44:50.240: %CAPWAP-3-EVENTLOG: Discovery Response from 10.31.127.35

*Feb  7 13:44:50.240: %CAPWAP-3-EVENTLOG: Discovery Response from 10.31.127.21

*Feb  7 13:44:50.240: %CAPWAP-3-EVENTLOG: Discovery Response from 10.31.127.31

*Feb  7 13:44:50.240: %CAPWAP-3-EVENTLOG: Discovery Response from 10.31.127.25

*Feb  7 13:44:50.240: %CAPWAP-3-EVENTLOG: Discovery Response from 10.8.127.61

*Feb  7 13:44:50.240: %CAPWAP-3-EVENTLOG: Discovery Response from 10.31.127.61

*Feb  7 13:45:00.228: %CAPWAP-3-EVENTLOG: Selected MWAR 'scho-wism-s4'(index 0).

*Feb  7 13:45:00.228: %CAPWAP-3-EVENTLOG: Selected MWAR 'scho-wism-s4' (index 7).

*Feb  7 13:45:00.228: %CAPWAP-3-EVENTLOG: Ap mgr count=1

*Feb  7 13:45:00.228: %CAPWAP-3-EVENTLOG: Go join a capwap controller

*Feb  7 13:45:00.228: %CAPWAP-3-EVENTLOG: Choosing AP Mgr with index 0, IP = 0xA1F7F3D , load = 57..

*Feb  7 13:45:00.228: %CAPWAP-3-EVENTLOG: Synchronizing time with AC time.

*Feb  7 13:45:00.000: %CAPWAP-3-EVENTLOG: Setting time to 13:45:00 UTC Feb 7 2012

*Feb  7 13:45:00.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.31.127.61 peer_port: 5246

*Feb  7 13:45:00.000: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Setup.

*Feb  7 13:45:00.000: %CAPWAP-5-CHANGED: CAPWAP changed state to 

*Feb  7 13:45:00.556: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.31.127.61 peer_port: 5246

*Feb  7 13:45:00.556: %CAPWAP-3-EVENTLOG: Dtls Session Established with the AC 10.31.127.61,port= 5246

*Feb  7 13:45:00.556: %CAPWAP-3-EVENTLOG: CAPWAP State: Join.

*Feb  7 13:45:00.556: %CAPWAP-3-EVENTLOG: Join request: version=117470208

*Feb  7 13:45:00.556: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117470208

*Feb  7 13:45:00.556: %CAPWAP-3-EVENTLOG: Join request: hasMaximum Message Payload

*Feb  7 13:45:00.556: %CAPWAP-3-EVENTLOG: Sending Join Request Path MTU payload, Length 1376

*Feb  7 13:45:00.556: %CAPWAP-5-SENDJOIN: sending Join Request to 10.31.127.61

*Feb  7 13:45:00.556: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN

*Feb  7 13:45:00.575: %CAPWAP-3-EVENTLOG: Join Response from 10.31.127.61

*Feb  7 13:45:00.575: %CAPWAP-3-EVENTLOG: PTMU : Setting MTU to : 1485

*Feb  7 13:45:00.578: %CAPWAP-3-EVENTLOG: Starting Post Join timer

*Feb  7 13:45:00.578: %CAPWAP-3-EVENTLOG: CAPWAP State: Configure.

*Feb  7 13:45:00.641: %CAPWAP-3-EVENTLOG: reboot reason flag 21

*Feb  7 13:45:02.091: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:02.091: %CAPWAP-3-EVENTLOG: Configuration Status sent to 10.31.127.61

*Feb  7 13:45:02.091: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG

*Feb  7 13:45:02.091: %CAPWAP-3-EVENTLOG: Current image is good. Connecting to the controller.

*Feb  7 13:45:02.154: %CAPWAP-3-EVENTLOG: Queue Empty.

*Feb  7 13:45:02.154: %CAPWAP-3-EVENTLOG: Configuration Status Response from 10.31.127.61

*Feb  7 13:45:02.227: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:31:127:61

*Feb  7 13:45:02.233: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:31:127:61

*Feb  7 13:45:02.233: %CAPWAP-5-CHANGED: CAPWAP changed state to UP

*Feb  7 13:45:02.242: %LWAPP-3-CLIENTEVENTLOG: OfficeExtend Localssid saved in AP flash

*Feb  7 13:45:02.312: %CAPWAP-3-EVENTLOG: testWmmAC configuration is 0

*Feb  7 13:45:02.488: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:02.488: %CAPWAP-3-EVENTLOG: CAPWAP State: Run.

*Feb  7 13:45:02.488: %CAPWAP-3-EVENTLOG: CAPWAP State: Run.

*Feb  7 13:45:02.488: %CAPWAP-3-EVENTLOG: CAPWAP moved to RUN state stopping post join timer

*Feb  7 13:45:02.488: %CAPWAP-3-EVENTLOG: Send Interface Info Update message sent to10:31:127:61

*Feb  7 13:45:02.488: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller scho-wism-s4

*Feb  7 13:45:02.488: %CAPWAP-3-EVENTLOG: Configuration update for  LinkAuditPayload  sent to10:31:127:61

*Feb  7 13:45:02.560: %LWAPP-3-CLIENTEVENTLOG: Switching to Connected mode

*Feb  7 13:45:02.560: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:02.560: %CAPWAP-3-EVENTLOG: Change State Event Response from 10.31.127.61

*Feb  7 13:45:02.560: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:02.560: %LWAPP-3-CLIENTEVENTLOG: SSID MSS added to the slot[1]

*Feb  7 13:45:02.560: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:02.736: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:02.736: %CAPWAP-3-EVENTLOG: Change State Event Response from 10.31.127.61

*Feb  7 13:45:02.736: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:02.736: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:02.912: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:02.912: %CAPWAP-3-EVENTLOG: Wtp Event Response from 10.31.127.61

*Feb  7 13:45:02.912: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:02.912: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:02.919: %CAPWAP-3-EVENTLOG: WTP Event Request:Ap Hreap Fault Client sent

*Feb  7 13:45:02.919: %CAPWAP-3-EVENTLOG: WTP Event Request:Ap Hreap Fault Client sent

*Feb  7 13:45:02.919: %CAPWAP-3-EVENTLOG: WTP Event Request:Ap Hreap Fault Client sent

*Feb  7 13:45:02.928: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:02.928: %CAPWAP-3-EVENTLOG: Wtp Event Response from 10.31.127.61

*Feb  7 13:45:02.928: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:05.722: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:05.725: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:05.725: %CAPWAP-3-EVENTLOG: Wtp Event Response from 10.31.127.61

*Feb  7 13:45:05.734: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:05.734: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:05.737: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:05.737: %CAPWAP-3-EVENTLOG: Wtp Event Response from 10.31.127.61

*Feb  7 13:45:05.750: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:05.750: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:05.753: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:05.753: %CAPWAP-3-EVENTLOG: Wtp Event Response from 10.31.127.61

*Feb  7 13:45:05.766: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:05.766: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:05.778: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:05.778: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:05.791: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:05.791: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:05.803: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:05.803: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:05.816: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:05.816: %WIDS-5-ENABLED: IDS Signature is loaded and enabled

*Feb  7 13:45:05.816: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:05.829: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:05.829: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:06.008: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:06.008: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:06.020: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:06.086: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:06.099: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:06.099: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:06.112: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:06.115: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:06.124: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:06.127: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:06.300: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:06.300: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:06.313: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:06.313: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:06.326: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:06.329: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:06.341: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:06.341: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:06.354: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:06.354: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:06.530: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:06.530: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:06.543: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:06.543: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:06.555: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:06.555: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:06.568: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:06.568: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:06.584: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:06.584: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:06.596: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:06.599: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:06.612: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:06.612: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:06.659: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:06.659: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:06.678: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:06.681: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:08.754: %CAPWAP-3-EVENTLOG: Retransmission Count= 0 Max Re-Transmission Value=5

*Feb  7 13:45:08.754: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:08.767: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:08.767: %CAPWAP-3-EVENTLOG: Wtp Event Response from 10.31.127.61

*Feb  7 13:45:08.779: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:08.779: %CAPWAP-3-EVENTLOG: Wtp Event Response from 10.31.127.61

*Feb  7 13:45:08.792: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:08.792: %CAPWAP-3-ERRORLOG: Failed to send packet from queue

*Feb  7 13:45:08.792: %CAPWAP-3-ERRORLOG: Failed to send message from queue.

*Feb  7 13:45:08.792: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Feb  7 13:45:08.792: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 10.31.127.61

*Feb  7 13:45:11.793: %CAPWAP-3-EVENTLOG: Retransmission Count= 0 Max Re-Transmission Value=5

*Feb  7 13:45:11.793: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:11.793: %CAPWAP-3-ERRORLOG: Failed to send packet from queue

*Feb  7 13:45:11.793: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message.

*Feb  7 13:45:11.793: %CAPWAP-3-ERRORLOG: Failed to handle timer message.

*Feb  7 13:45:11.793: %CAPWAP-3-ERRORLOG: Failed to process Message timer message.

*Feb  7 13:45:11.793: %CAPWAP-3-ERRORLOG: Message timeout timer expiry handler failed.

*Feb  7 13:45:12.557: %CLEANAIR-5-STATE: Slot 0 disabled

*Feb  7 13:45:12.557: %CLEANAIR-5-STATE: Slot 1 disabled

*Feb  7 13:45:14.794: %CAPWAP-3-EVENTLOG: Retransmission Count= 1 Max Re-Transmission Value=5

*Feb  7 13:45:14.794: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:14.794: %CAPWAP-3-ERRORLOG: Failed to send packet from queue

*Feb  7 13:45:14.794: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message.

*Feb  7 13:45:14.794: %CAPWAP-3-ERRORLOG: Failed to handle timer message.

*Feb  7 13:45:14.794: %CAPWAP-3-ERRORLOG: Failed to process Message timer message.

*Feb  7 13:45:14.794: %CAPWAP-3-ERRORLOG: Message timeout timer expiry handler failed.

*Feb  7 13:45:17.795: %CAPWAP-3-EVENTLOG: Retransmission Count= 2 Max Re-Transmission Value=5

*Feb  7 13:45:17.795: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:17.795: %CAPWAP-3-ERRORLOG: Failed to send packet from queue

*Feb  7 13:45:17.795: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message.

*Feb  7 13:45:17.795: %CAPWAP-3-ERRORLOG: Failed to handle timer message.

*Feb  7 13:45:17.795: %CAPWAP-3-ERRORLOG: Failed to process Message timer message.

*Feb  7 13:45:17.795: %CAPWAP-3-ERRORLOG: Message timeout timer expiry handler failed.

*Feb  7 13:45:20.796: %CAPWAP-3-EVENTLOG: Retransmission Count= 3 Max Re-Transmission Value=5

*Feb  7 13:45:20.796: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:20.796: %CAPWAP-3-ERRORLOG: Failed to send packet from queue

*Feb  7 13:45:20.796: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message.

*Feb  7 13:45:20.796: %CAPWAP-3-ERRORLOG: Failed to handle timer message.

*Feb  7 13:45:20.796: %CAPWAP-3-ERRORLOG: Failed to process Message timer message.

*Feb  7 13:45:20.796: %CAPWAP-3-ERRORLOG: Message timeout timer expiry handler failed.

*Feb  7 13:45:23.797: %CAPWAP-3-EVENTLOG: Retransmission Count= 4 Max Re-Transmission Value=5

*Feb  7 13:45:23.797: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:23.797: %CAPWAP-3-ERRORLOG: Failed to send packet from queue

*Feb  7 13:45:23.797: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message.

*Feb  7 13:45:23.797: %CAPWAP-3-ERRORLOG: Failed to handle timer message.

*Feb  7 13:45:23.797: %CAPWAP-3-ERRORLOG: Failed to process Message timer message.

*Feb  7 13:45:23.797: %CAPWAP-3-ERRORLOG: Message timeout timer expiry handler failed.

*Feb  7 13:45:26.798: %CAPWAP-3-EVENTLOG: Retransmission Count= 5 Max Re-Transmission Value=5

*Feb  7 13:45:26.798: %CAPWAP-3-EVENTLOG: Max retransmission count exceeded going back to DISCOVER mode.

*Feb  7 13:45:26.798: %CAPWAP-3-EVENTLOG: The function which Posted the message to send out of the box is capwap_hreap_fault_client_inf and of Type=64

*Feb  7 13:45:26.798: %CAPWAP-3-EVENTLOG: Retransmission count for packet exceeded max(CAPWAP_WTP_EVENT_REQUEST

., 5)

*Feb  7 13:45:26.798: %LWAPP-3-CLIENTEVENTLOG: Switching to Standalone mode

*Feb  7 13:45:26.801: %CAPWAP-3-EVENTLOG: GOING BACK TO DISCOVER MODE

*Feb  7 13:45:26.870: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.31.127.61:5246

*Feb  7 13:45:26.870: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.

*Feb  7 13:45:26.873: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. Restarting capwap state machine.

*Feb  7 13:45:26.943: %WIDS-5-DISABLED: IDS Signature is removed and disabled.

*Feb  7 13:45:26.943: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Feb  7 13:45:26.943: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Feb  7 13:45:26.943: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Feb  7 13:45:26.943: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117470208

*Feb  7 13:45:26.943: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.31.127.41 with discovery type set to 1

*Feb  7 13:45:26.943: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117470208

*Feb  7 13:45:26.943: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.31.127.45 with discovery type set to 1

*Feb  7 13:45:26.943: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117470208

*Feb  7 13:45:26.943: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.31.127.61 with discovery type set to 1

*Feb  7 13:45:26.943: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117470208

*Feb  7 13:45:26.943: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.8.127.61 with discovery type set to 1

*Feb  7 13:45:26.943: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117470208

*Feb  7 13:45:26.943: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.31.127.31 with discovery type set to 1

*Feb  7 13:45:26.946: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117470208

*Feb  7 13:45:26.946: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.31.127.35 with discovery type set to 1

*Feb  7 13:45:26.946: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117470208

*Feb  7 13:45:26.946: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.31.127.21 with discovery type set to 1

*Feb  7 13:45:26.946: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117470208

*Feb  7 13:45:26.946: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.31.127.25 with discovery type set to 1

*Feb  7 13:45:26.946: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117470208

*Feb  7 13:45:26.946: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.255 with discovery type set to 0

*Feb  7 13:45:26.955: %CAPWAP-3-EVENTLOG: Discovery Response from 10.31.127.41

*Feb  7 13:45:26.955: %CAPWAP-3-EVENTLOG: Discovery Response from 10.31.127.45

*Feb  7 13:45:26.955: %CAPWAP-3-EVENTLOG: Discovery Response from 10.31.127.31

*Feb  7 13:45:26.955: %CAPWAP-3-EVENTLOG: Discovery Response from 10.31.127.35

*Feb  7 13:45:26.955: %CAPWAP-3-EVENTLOG: Discovery Response from 10.31.127.21

*Feb  7 13:45:26.955: %CAPWAP-3-EVENTLOG: Discovery Response from 10.31.127.25

*Feb  7 13:45:26.958: %CAPWAP-3-EVENTLOG: Discovery Response from 10.8.127.61

*Feb  7 13:45:26.958: %CAPWAP-3-EVENTLOG: Discovery Response from 10.31.127.61

*Feb  7 13:45:36.946: %CAPWAP-3-EVENTLOG: Selected MWAR 'scho-wism-s4'(index 0).

*Feb  7 13:45:36.946: %CAPWAP-3-EVENTLOG: Selected MWAR 'scho-wism-s4' (index 7).

*Feb  7 13:45:36.946: %CAPWAP-3-EVENTLOG: Ap mgr count=1

*Feb  7 13:45:36.946: %CAPWAP-3-EVENTLOG: Go join a capwap controller

*Feb  7 13:45:36.946: %CAPWAP-3-EVENTLOG: Choosing AP Mgr with index 0, IP = 0xA1F7F3D , load = 57..

*Feb  7 13:45:36.946: %CAPWAP-3-EVENTLOG: Synchronizing time with AC time.

*Feb  7 13:45:37.000: %CAPWAP-3-EVENTLOG: Setting time to 13:45:37 UTC Feb 7 2012

*Feb  7 13:45:37.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.31.127.61 peer_port: 5246

*Feb  7 13:45:37.000: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Setup.

*Feb  7 13:45:37.000: %CAPWAP-5-CHANGED: CAPWAP changed state to 

*Feb  7 13:45:37.556: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.31.127.61 peer_port: 5246

*Feb  7 13:45:37.556: %CAPWAP-3-EVENTLOG: Dtls Session Established with the AC 10.31.127.61,port= 5246

*Feb  7 13:45:37.556: %CAPWAP-3-EVENTLOG: CAPWAP State: Join.

*Feb  7 13:45:37.556: %CAPWAP-3-EVENTLOG: Join request: version=117470208

*Feb  7 13:45:37.556: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117470208

*Feb  7 13:45:37.556: %CAPWAP-3-EVENTLOG: Join request: hasMaximum Message Payload

*Feb  7 13:45:37.556: %CAPWAP-3-EVENTLOG: Sending Join Request Path MTU payload, Length 1376

*Feb  7 13:45:37.556: %CAPWAP-5-SENDJOIN: sending Join Request to 10.31.127.61

*Feb  7 13:45:37.556: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN

*Feb  7 13:45:37.572: %CAPWAP-3-EVENTLOG: Join Response from 10.31.127.61

*Feb  7 13:45:37.572: %CAPWAP-3-EVENTLOG: PTMU : Setting MTU to : 1485

*Feb  7 13:45:37.578: %CAPWAP-3-EVENTLOG: Starting Post Join timer

*Feb  7 13:45:37.578: %CAPWAP-3-EVENTLOG: CAPWAP State: Configure.

*Feb  7 13:45:37.641: %CAPWAP-3-EVENTLOG: reboot reason flag 21

*Feb  7 13:45:39.192: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:39.192: %CAPWAP-3-EVENTLOG: Configuration Status sent to 10.31.127.61

*Feb  7 13:45:39.192: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG

*Feb  7 13:45:39.195: %CAPWAP-3-EVENTLOG: Current image is good. Connecting to the controller.

*Feb  7 13:45:39.258: %CAPWAP-3-EVENTLOG: Queue Empty.

*Feb  7 13:45:39.258: %CAPWAP-3-EVENTLOG: Configuration Status Response from 10.31.127.61

*Feb  7 13:45:39.330: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:31:127:61

*Feb  7 13:45:39.340: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:31:127:61

*Feb  7 13:45:39.340: %CAPWAP-5-CHANGED: CAPWAP changed state to UP

*Feb  7 13:45:39.349: %LWAPP-3-CLIENTEVENTLOG: OfficeExtend Localssid saved in AP flash

*Feb  7 13:45:39.419: %CAPWAP-3-EVENTLOG: testWmmAC configuration is 0

*Feb  7 13:45:39.588: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:39.592: %CAPWAP-3-EVENTLOG: CAPWAP State: Run.

*Feb  7 13:45:39.592: %CAPWAP-3-EVENTLOG: CAPWAP State: Run.

*Feb  7 13:45:39.592: %CAPWAP-3-EVENTLOG: CAPWAP moved to RUN state stopping post join timer

*Feb  7 13:45:39.592: %CAPWAP-3-EVENTLOG: Send Interface Info Update message sent to10:31:127:61

*Feb  7 13:45:39.592: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller scho-wism-s4

*Feb  7 13:45:39.592: %CAPWAP-3-EVENTLOG: Configuration update for  LinkAuditPayload  sent to10:31:127:61

*Feb  7 13:45:39.658: %LWAPP-3-CLIENTEVENTLOG: Switching to Connected mode

*Feb  7 13:45:39.658: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:39.661: %CAPWAP-3-EVENTLOG: Change State Event Response from 10.31.127.61

*Feb  7 13:45:39.661: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:39.661: %LWAPP-3-CLIENTEVENTLOG: SSID MSS added to the slot[1]

*Feb  7 13:45:39.661: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:39.834: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:39.834: %CAPWAP-3-EVENTLOG: Change State Event Response from 10.31.127.61

*Feb  7 13:45:39.834: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:39.834: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:40.004: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:40.004: %CAPWAP-3-EVENTLOG: Wtp Event Response from 10.31.127.61

*Feb  7 13:45:40.004: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:40.004: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:40.010: %CAPWAP-3-EVENTLOG: WTP Event Request:Ap Hreap Fault Client sent

*Feb  7 13:45:40.010: %CAPWAP-3-EVENTLOG: WTP Event Request:Ap Hreap Fault Client sent

*Feb  7 13:45:40.010: %CAPWAP-3-EVENTLOG: WTP Event Request:Ap Hreap Fault Client sent

*Feb  7 13:45:40.019: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:40.019: %CAPWAP-3-EVENTLOG: Wtp Event Response from 10.31.127.61

*Feb  7 13:45:40.023: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:40.092: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:40.092: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:40.092: %CAPWAP-3-EVENTLOG: Wtp Event Response from 10.31.127.61

*Feb  7 13:45:40.104: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:40.104: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:40.117: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:40.117: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:40.129: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:40.129: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:40.155: %CAPWAP-3-EVENTLOG: Config update:Ap CDP cache payload sent to 10:31:127:61

*Feb  7 13:45:40.155: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:40.155: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:40.170: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:40.170: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:40.183: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:40.183: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:40.196: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:40.196: %WIDS-5-ENABLED: IDS Signature is loaded and enabled

*Feb  7 13:45:40.196: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:40.208: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:40.208: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:41.797: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:41.797: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:41.809: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:41.879: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:41.897: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:41.897: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:41.910: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:41.910: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:41.923: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:41.923: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:42.102: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:42.102: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:42.114: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:42.114: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:42.127: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:42.130: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:42.143: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:42.143: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:42.155: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:42.155: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:42.332: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:42.332: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:42.344: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:45:42.344: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:45:43.093: %CAPWAP-3-EVENTLOG: Retransmission Count= 0 Max Re-Transmission Value=5

*Feb  7 13:45:43.093: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:43.105: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:43.105: %CAPWAP-3-EVENTLOG: Wtp Event Response from 10.31.127.61

*Feb  7 13:45:43.118: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:43.118: %CAPWAP-3-EVENTLOG: Wtp Event Response from 10.31.127.61

*Feb  7 13:45:43.131: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:43.131: %CAPWAP-3-ERRORLOG: Failed to send packet from queue

*Feb  7 13:45:43.131: %CAPWAP-3-ERRORLOG: Failed to send message from queue.

*Feb  7 13:45:43.131: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Feb  7 13:45:43.131: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 10.31.127.61

*Feb  7 13:45:46.132: %CAPWAP-3-EVENTLOG: Retransmission Count= 0 Max Re-Transmission Value=5

*Feb  7 13:45:46.132: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:46.132: %CAPWAP-3-ERRORLOG: Failed to send packet from queue

*Feb  7 13:45:46.132: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message.

*Feb  7 13:45:46.132: %CAPWAP-3-ERRORLOG: Failed to handle timer message.

*Feb  7 13:45:46.132: %CAPWAP-3-ERRORLOG: Failed to process Message timer message.

*Feb  7 13:45:46.132: %CAPWAP-3-ERRORLOG: Message timeout timer expiry handler failed.

*Feb  7 13:45:49.133: %CAPWAP-3-EVENTLOG: Retransmission Count= 1 Max Re-Transmission Value=5

*Feb  7 13:45:49.133: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:49.133: %CAPWAP-3-ERRORLOG: Failed to send packet from queue

*Feb  7 13:45:49.133: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message.

*Feb  7 13:45:49.133: %CAPWAP-3-ERRORLOG: Failed to handle timer message.

*Feb  7 13:45:49.133: %CAPWAP-3-ERRORLOG: Failed to process Message timer message.

*Feb  7 13:45:49.133: %CAPWAP-3-ERRORLOG: Message timeout timer expiry handler failed.

*Feb  7 13:45:52.134: %CAPWAP-3-EVENTLOG: Retransmission Count= 2 Max Re-Transmission Value=5

*Feb  7 13:45:52.134: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:52.134: %CAPWAP-3-ERRORLOG: Failed to send packet from queue

*Feb  7 13:45:52.134: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message.

*Feb  7 13:45:52.134: %CAPWAP-3-ERRORLOG: Failed to handle timer message.

*Feb  7 13:45:52.134: %CAPWAP-3-ERRORLOG: Failed to process Message timer message.

*Feb  7 13:45:52.134: %CAPWAP-3-ERRORLOG: Message timeout timer expiry handler failed.

*Feb  7 13:45:55.135: %CAPWAP-3-EVENTLOG: Retransmission Count= 3 Max Re-Transmission Value=5

*Feb  7 13:45:55.135: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:55.135: %CAPWAP-3-ERRORLOG: Failed to send packet from queue

*Feb  7 13:45:55.135: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message.

*Feb  7 13:45:55.135: %CAPWAP-3-ERRORLOG: Failed to handle timer message.

*Feb  7 13:45:55.135: %CAPWAP-3-ERRORLOG: Failed to process Message timer message.

*Feb  7 13:45:55.135: %CAPWAP-3-ERRORLOG: Message timeout timer expiry handler failed.

*Feb  7 13:45:58.136: %CAPWAP-3-EVENTLOG: Retransmission Count= 4 Max Re-Transmission Value=5

*Feb  7 13:45:58.136: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:45:58.136: %CAPWAP-3-ERRORLOG: Failed to send packet from queue

*Feb  7 13:45:58.136: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message.

*Feb  7 13:45:58.136: %CAPWAP-3-ERRORLOG: Failed to handle timer message.

*Feb  7 13:45:58.136: %CAPWAP-3-ERRORLOG: Failed to process Message timer message.

*Feb  7 13:45:58.136: %CAPWAP-3-ERRORLOG: Message timeout timer expiry handler failed.

*Feb  7 13:46:01.137: %CAPWAP-3-EVENTLOG: Retransmission Count= 5 Max Re-Transmission Value=5

*Feb  7 13:46:01.137: %CAPWAP-3-EVENTLOG: Max retransmission count exceeded going back to DISCOVER mode.

*Feb  7 13:46:01.137: %CAPWAP-3-EVENTLOG: The function which Posted the message to send out of the box is capwap_hreap_fault_client_inf and of Type=64

*Feb  7 13:46:01.137: %CAPWAP-3-EVENTLOG: Retransmission count for packet exceeded max(CAPWAP_WTP_EVENT_REQUEST

., 6)

*Feb  7 13:46:01.137: %LWAPP-3-CLIENTEVENTLOG: Switching to Standalone mode

*Feb  7 13:46:01.140: %CAPWAP-3-EVENTLOG: GOING BACK TO DISCOVER MODE

*Feb  7 13:46:01.209: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.31.127.61:5246

*Feb  7 13:46:01.209: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.

*Feb  7 13:46:01.212: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. Restarting capwap state machine.

*Feb  7 13:46:01.278: %WIDS-5-DISABLED: IDS Signature is removed and disabled.

*Feb  7 13:46:01.281: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Feb  7 13:46:01.281: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Feb  7 13:46:01.281: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Feb  7 13:46:01.281: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117470208

*Feb  7 13:46:01.281: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.31.127.41 with discovery type set to 1

*Feb  7 13:46:01.281: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117470208

*Feb  7 13:46:01.281: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.31.127.45 with discovery type set to 1

*Feb  7 13:46:01.281: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117470208

*Feb  7 13:46:01.281: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.31.127.61 with discovery type set to 1

*Feb  7 13:46:01.281: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117470208

*Feb  7 13:46:01.281: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.8.127.61 with discovery type set to 1

*Feb  7 13:46:01.281: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117470208

*Feb  7 13:46:01.281: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.31.127.31 with discovery type set to 1

*Feb  7 13:46:01.281: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117470208

*Feb  7 13:46:01.281: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.31.127.35 with discovery type set to 1

*Feb  7 13:46:01.281: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117470208

*Feb  7 13:46:01.281: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.31.127.21 with discovery type set to 1

*Feb  7 13:46:01.281: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117470208

*Feb  7 13:46:01.281: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.31.127.25 with discovery type set to 1

*Feb  7 13:46:01.281: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117470208

*Feb  7 13:46:01.285: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.255 with discovery type set to 0

*Feb  7 13:46:01.294: %CAPWAP-3-EVENTLOG: Discovery Response from 10.31.127.41

*Feb  7 13:46:01.294: %CAPWAP-3-EVENTLOG: Discovery Response from 10.31.127.45

*Feb  7 13:46:01.294: %CAPWAP-3-EVENTLOG: Discovery Response from 10.31.127.31

*Feb  7 13:46:01.294: %CAPWAP-3-EVENTLOG: Discovery Response from 10.31.127.35

*Feb  7 13:46:01.294: %CAPWAP-3-EVENTLOG: Discovery Response from 10.31.127.21

*Feb  7 13:46:01.294: %CAPWAP-3-EVENTLOG: Discovery Response from 10.31.127.25

*Feb  7 13:46:01.294: %CAPWAP-3-EVENTLOG: Discovery Response from 10.8.127.61

*Feb  7 13:46:01.294: %CAPWAP-3-EVENTLOG: Discovery Response from 10.31.127.61

*Feb  7 13:46:11.285: %CAPWAP-3-EVENTLOG: Selected MWAR 'scho-wism-s4'(index 0).

*Feb  7 13:46:11.285: %CAPWAP-3-EVENTLOG: Selected MWAR 'scho-wism-s4' (index 7).

*Feb  7 13:46:11.285: %CAPWAP-3-EVENTLOG: Ap mgr count=1

*Feb  7 13:46:11.285: %CAPWAP-3-EVENTLOG: Go join a capwap controller

*Feb  7 13:46:11.285: %CAPWAP-3-EVENTLOG: Choosing AP Mgr with index 0, IP = 0xA1F7F3D , load = 57..

*Feb  7 13:46:11.285: %CAPWAP-3-EVENTLOG: Synchronizing time with AC time.

*Feb  7 13:46:11.000: %CAPWAP-3-EVENTLOG: Setting time to 13:46:11 UTC Feb 7 2012

*Feb  7 13:46:11.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.31.127.61 peer_port: 5246

*Feb  7 13:46:11.000: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Setup.

*Feb  7 13:46:11.000: %CAPWAP-5-CHANGED: CAPWAP changed state to 

*Feb  7 13:46:11.556: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.31.127.61 peer_port: 5246

*Feb  7 13:46:11.556: %CAPWAP-3-EVENTLOG: Dtls Session Established with the AC 10.31.127.61,port= 5246

*Feb  7 13:46:11.556: %CAPWAP-3-EVENTLOG: CAPWAP State: Join.

*Feb  7 13:46:11.556: %CAPWAP-3-EVENTLOG: Join request: version=117470208

*Feb  7 13:46:11.556: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117470208

*Feb  7 13:46:11.556: %CAPWAP-3-EVENTLOG: Join request: hasMaximum Message Payload

*Feb  7 13:46:11.556: %CAPWAP-3-EVENTLOG: Sending Join Request Path MTU payload, Length 1376

*Feb  7 13:46:11.556: %CAPWAP-5-SENDJOIN: sending Join Request to 10.31.127.61

*Feb  7 13:46:11.556: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN

*Feb  7 13:46:11.575: %CAPWAP-3-EVENTLOG: Join Response from 10.31.127.61

*Feb  7 13:46:11.575: %CAPWAP-3-EVENTLOG: PTMU : Setting MTU to : 1485

*Feb  7 13:46:11.578: %CAPWAP-3-EVENTLOG: Starting Post Join timer

*Feb  7 13:46:11.578: %CAPWAP-3-EVENTLOG: CAPWAP State: Configure.

*Feb  7 13:46:11.635: %CAPWAP-3-EVENTLOG: reboot reason flag 21

*Feb  7 13:46:11.780: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:46:11.780: %CAPWAP-3-EVENTLOG: Configuration Status sent to 10.31.127.61

*Feb  7 13:46:11.780: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG

*Feb  7 13:46:11.780: %CAPWAP-3-EVENTLOG: Current image is good. Connecting to the controller.

*Feb  7 13:46:11.843: %CAPWAP-3-EVENTLOG: Queue Empty.

*Feb  7 13:46:11.843: %CAPWAP-3-EVENTLOG: Configuration Status Response from 10.31.127.61

*Feb  7 13:46:11.918: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:31:127:61

*Feb  7 13:46:11.924: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending channel and power levels info.10:31:127:61

*Feb  7 13:46:11.924: %CAPWAP-5-CHANGED: CAPWAP changed state to UP

*Feb  7 13:46:11.934: %LWAPP-3-CLIENTEVENTLOG: OfficeExtend Localssid saved in AP flash

*Feb  7 13:46:13.321: %CAPWAP-3-EVENTLOG: testWmmAC configuration is 0

*Feb  7 13:46:13.491: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:46:13.494: %CAPWAP-3-EVENTLOG: CAPWAP State: Run.

*Feb  7 13:46:13.494: %CAPWAP-3-EVENTLOG: CAPWAP State: Run.

*Feb  7 13:46:13.494: %CAPWAP-3-EVENTLOG: CAPWAP moved to RUN state stopping post join timer

*Feb  7 13:46:13.494: %CAPWAP-3-EVENTLOG: Send Interface Info Update message sent to10:31:127:61

*Feb  7 13:46:13.494: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller scho-wism-s4

*Feb  7 13:46:13.494: %CAPWAP-3-EVENTLOG: Configuration update for  LinkAuditPayload  sent to10:31:127:61

*Feb  7 13:46:13.563: %LWAPP-3-CLIENTEVENTLOG: Switching to Connected mode

*Feb  7 13:46:13.570: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:46:13.570: %CAPWAP-3-EVENTLOG: Change State Event Response from 10.31.127.61

*Feb  7 13:46:13.570: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:46:13.570: %LWAPP-3-CLIENTEVENTLOG: SSID MSS added to the slot[1]

*Feb  7 13:46:13.570: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:46:13.743: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:46:13.743: %CAPWAP-3-EVENTLOG: Change State Event Response from 10.31.127.61

*Feb  7 13:46:13.743: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:46:13.746: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:46:13.919: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:46:13.919: %CAPWAP-3-EVENTLOG: Wtp Event Response from 10.31.127.61

*Feb  7 13:46:13.919: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:46:13.919: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:46:13.919: %CAPWAP-3-EVENTLOG: WTP Event Request:Ap Hreap Fault Client sent

*Feb  7 13:46:13.919: %CAPWAP-3-EVENTLOG: WTP Event Request:Ap Hreap Fault Client sent

*Feb  7 13:46:13.919: %CAPWAP-3-EVENTLOG: WTP Event Request:Ap Hreap Fault Client sent

*Feb  7 13:46:13.931: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:46:13.931: %CAPWAP-3-EVENTLOG: Wtp Event Response from 10.31.127.61

*Feb  7 13:46:13.934: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:46:14.004: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:46:14.004: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:46:14.007: %CAPWAP-3-EVENTLOG: Wtp Event Response from 10.31.127.61

*Feb  7 13:46:14.016: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:46:14.016: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:46:14.029: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:46:14.032: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:46:14.045: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:46:14.045: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:46:14.057: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:46:14.057: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:46:14.070: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:46:14.070: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:46:14.082: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:46:14.085: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:46:14.098: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:46:14.098: %WIDS-5-ENABLED: IDS Signature is loaded and enabled

*Feb  7 13:46:14.098: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:46:14.111: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:46:14.111: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:46:15.599: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:46:15.599: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:46:15.611: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:46:15.683: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:46:15.696: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:46:15.696: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:46:15.709: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:46:15.709: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:46:15.721: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:46:15.721: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:46:15.897: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:46:15.897: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:46:15.910: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:46:15.910: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:46:15.923: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:46:15.923: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:46:15.938: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:46:15.938: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:46:15.951: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:46:15.951: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:46:16.130: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:46:16.130: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:46:16.143: %CAPWAP-3-EVENTLOG: Configuration update request from 10.31.127.61

*Feb  7 13:46:16.143: %CAPWAP-3-EVENTLOG: Configuration update response sent to 10.31.127.61

*Feb  7 13:46:17.005: %CAPWAP-3-EVENTLOG: Retransmission Count= 0 Max Re-Transmission Value=5

*Feb  7 13:46:17.005: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:46:17.017: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:46:17.017: %CAPWAP-3-EVENTLOG: Wtp Event Response from 10.31.127.61

*Feb  7 13:46:17.030: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:46:17.030: %CAPWAP-3-EVENTLOG: Wtp Event Response from 10.31.127.61

*Feb  7 13:46:17.042: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:46:17.042: %CAPWAP-3-ERRORLOG: Failed to send packet from queue

*Feb  7 13:46:17.042: %CAPWAP-3-ERRORLOG: Failed to send message from queue.

*Feb  7 13:46:17.042: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Feb  7 13:46:17.042: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 10.31.127.61

*Feb  7 13:46:20.043: %CAPWAP-3-EVENTLOG: Retransmission Count= 0 Max Re-Transmission Value=5

*Feb  7 13:46:20.043: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:46:20.043: %CAPWAP-3-ERRORLOG: Failed to send packet from queue

*Feb  7 13:46:20.043: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message.

*Feb  7 13:46:20.043: %CAPWAP-3-ERRORLOG: Failed to handle timer message.

*Feb  7 13:46:20.043: %CAPWAP-3-ERRORLOG: Failed to process Message timer message.

*Feb  7 13:46:20.043: %CAPWAP-3-ERRORLOG: Message timeout timer expiry handler failed.

*Feb  7 13:46:23.044: %CAPWAP-3-EVENTLOG: Retransmission Count= 1 Max Re-Transmission Value=5

*Feb  7 13:46:23.044: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb  7 13:46:23.044: %CAPWAP-3-ERRORLOG: Failed to send packet from queue

*Feb  7 13:46:23.044: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message.

*Feb  7 13:46:23.044: %CAPWAP-3-ERRORLOG: Failed to handle timer message.

*Feb  7 13:46:23.044: %CAPWAP-3-ERRORLOG: Failed to process Message timer message.

New Member

Re: Reason for association 'Dot11g Mode Change '.

TR,

These APs are in Local or HREAP mode?

From the first entry and now the logs, i'm confused on the setup:

Controller - 10.15.15.15

or

Controller - 10.31.127.61?

Also, from the debugs, looks like your connection to the controller times out and retries a max of 5 times. which triggers a standalone mode. That would tell me that your AP is in HREAP mode, if this is across a WAN have you configured QoS? is your WAN MPLS or VPN?

i think your issue is different than mine, as my APs dont switch to standalone mode, since mine are in Local.

New Member

Re: Reason for association 'Dot11g Mode Change '.

sorry the aps ar in HREAP mode.

the controller ip is 10.31.127.61. i modified it on my first post. WAN is MPLS.

would be interesting how your debugg looks like.

at the moment there is no reason why the ap times out. so i will setup a monitor trace, perhaps i can archive more information why the ap times out......

New Member

Re: Reason for association 'Dot11g Mode Change '.

How long do the APs stay connetcted for before they drop from the controller. Have you run a ping test from the remote location back to the controller?

If you have the APs in HREAP and there is no QoS in place on the WAN, the your CAPWAP traffic is subject to drops and the APs will keep on dissasociating from controller.

Your WAN routers at each end need to have QoS in place. you also need to verify that your WAN provider offers QoS queues so that your QoS markings making it accross the WAN.

New Member

Re: Reason for association 'Dot11g Mode Change '.

ihernandez81 schrieb:

How long do the APs stay connetcted for before they drop from the controller. Have you run a ping test from the remote location back to the controller?

after rebooting the WISMs and APs i cant see the problem anymore.. however i will update the case when the problems reoccur...

ihernandez81 schrieb:

If you have the APs in HREAP and there is no QoS in place on the WAN, the your CAPWAP traffic is subject to drops and the APs will keep on dissasociating from controller.

Your WAN routers at each end need to have QoS in place. you also need to verify that your WAN provider offers QoS queues so that your QoS markings making it accross the WAN.

QoS is/was actually well implementet.

New Member

Reason for association 'Dot11g Mode Change '.

I fixed the speed and duplex on a few APs. But this didnt fix the problem.

My switches are series: 3750 and 2960

The 3502 APs has HREAP configured. The 1141 or 1131 does not.

New Member

Re: Reason for association 'Dot11g Mode Change '.

I had this happen on 2 of my 270 or so AP's after upgrading to 7.2.103.0.  I went into the individual AP's settings under "Wireless" and did a "Clear All Config".  That seemed to fix the issue for now.

New Member

Reason for association 'Dot11g Mode Change '.

I had this issue for a while but only just decided to look into it. 

Setting the ports to Auto Duplex/Speed on the switches solved the issue.

Apparently LAPs do not like hard-coded duplex settings on network ports.

8844
Views
0
Helpful
13
Replies
CreatePlease to create content