I just lost one AP from vWLC and found this trap:
Time sync between AP and Controller failed
What that is means?
I check time on remaining AP's and found out that time on AP's is different form wlc (time on AP's is 2 hours less than time configured on vWLC).
On vWLC I have configured NTP and timezone.
Kindly provide the complete logs and version of the WLC. As I see that there is a known issue with the 8.0.x release for OEAP AP.
What is the model of your AP?
Provide me the console logs of the AP and make sure the country code is set on the WLC correctly.
I have Virtual WLC running 7.6.130 software, AP is 1602E-E-K9.
Unfortunately wlc and ap are 300 km away from me so I don't have console loggs from AP. I asked costumer to reload ap and now is on.
In attach I send sh logg from ap after reboot. On wlc I don't have loggs from yesterday.
In logg you will see many tracebacks like:
%SYS-3-TIMERNEG: Cannot start timer (0x6A47EF8) with negative offset (-1576609296). -Process= "CAPWAP CLIENT", ipl= 0, pid= 125
-Traceback= 298098z 3A5660z 3A3A44z AB2DC4z 99F8D0z A1B630z 9BB734z 9B3FBCz 958EA0z 96ED68z 97E1F4z 97A6A4z 9804F4z 9807D4z 969C48z 96A114z
I have that logg on many ap's.
Country code is correct on wlc.
Thanks for your quick and promot response. It seems like the APs has crashed.
Please do provide me the "show version" output from one of the AP I will decode the traceback and update you if there is any known Bug.
I have decoded the Traceback and found that you are hitting an internal bug CSCud87439.
This seems to be fixed in integrated releases.
It will be good if you open a TAC case to get an escalation image for the Bug fix.
I agree... I don't think there is an escalation image for v220.127.116.11 as it just came out a couple weeks ago.
Your best bet is to go onsite and take a look at the AP from the console. The upgrade could of had a corrupt image for the 1600's. The only thing you can try to do is upload the image again and check the MD5 hash prior to uploading. If that doesn't work. Factory reset of the AP would be what I would do next. This requires access to the AP however. Is the time on the WLC correct and the timezone?
That is correct.... I beta test a lot and images get corrupt, so what I do is erase the nvram, delete all the images in flash and upload the rcv directly to the AP and let it join.
Yes, I understand that the release is just out and there is no escalation image for now. However, once filed a Bug they should be able to get you one escalation image.
But, if you would like to fix this without an escalation image as Scott mentioned you can download the recovery image on the APs or download 18.104.22.168 version once again.
In the software version of WLC, there will be images for all the models of APs supported in that version.
I'll try to download rckw image on one ap next Monday and see what will happen.
I'm curious about log:
Dtx dump: 4AE4F00 2197 0 flags 23 101000 blkedmsk:FE01 blkedidx:0 aid:25 cpq 7C31D58
What that's mean?
Thanks for your quick response, this logs means that the registry was dumped or overload while performing a task and caused the APs to crashed. Let us know once after your test.