09-17-2018 06:33 AM - edited 03-08-2019 04:11 PM
Hi Experts,
We have a WLC 2106. Everytime this WLC reloads due to whatever reason then the time of this is always ressting it to about it to something else than the current time. We nothing in NTP settings before that we used to have NTP server configured in this WLC but status was same.
Not sure why this is happening and how to correct it permanently? Any suggestion? I am happy to provide more information on this.
09-17-2018 02:01 PM
what is the version running.
show time post output.
09-17-2018 03:56 PM - edited 09-17-2018 03:57 PM
Hi Balaji - Thanks for your response. Please find below:-
1. Version = 4.2.130.0
2. Show time output:-
(Cisco Controller) >show time
Time............................................. Mon Sep 17 18:51:42 2018
Timezone delta................................... -5:0
NTP Servers
NTP Polling Interval......................... 86400
Index NTP Server
------- --------------------------------
(Cisco Controller) >
09-18-2018 12:13 AM
you need to configured NTP configuration and save configuration. make sure it sync the time across network is same.
once the configuration saved, you can reload and power off and test is the config retain same, as you see config loosing all the time power loss.
09-18-2018 06:15 AM
09-17-2018 02:53 PM
09-17-2018 03:58 PM
09-17-2018 05:23 PM - edited 09-17-2018 05:24 PM
If NTP is configured, then how come the output to the command "sh time" shows no NTP synchronized?
Another thing, what is the NTP server? Is it a MS Windows based system?
09-18-2018 06:10 AM
Hi Leo - As I mentioned in my question that we have that configured before and we removed few weeks ago. We have the same problem even when NTP was configured. No, NTP was not windows based system - it was our core switch on different location. Any issues with that configuration?
09-18-2018 12:14 PM
When you mention different location, Do you have reachability for that NTP all the time, Why not setup one for Local site - do you have any limitation. so that you can monitor the NTP debug enable, why you loosing the NTP sync.
This is suggestion to test.
09-18-2018 02:14 PM
@Hwarraich wrote:
No, NTP was not windows based system - it was our core switch on different location. Any issues with that configuration?
Is your core switch synchroized, in some way, to a trusted NTP server?
09-19-2018 11:26 AM
Hi Leo - I am not sure. But need your help to verify this. below is the output from my core switch:-
sh ntp status
Clock is unsynchronized, stratum 16, no reference clock
nominal freq is 250.0000 Hz, actual freq is 250.0000 Hz, precision is 2**10
ntp uptime is 3091553700 (1/100 of seconds), resolution is 4000
reference time is 00000000.00000000 (19:00:00.000 EST Thu Dec 31 1899)
clock offset is 0.0000 msec, root delay is 0.00 msec
root dispersion is 463732.88 msec, peer dispersion is 0.00 msec
loopfilter state is 'NSET' (Never set), drift is 0.000000000 s/s
system poll interval is 8, never updated.
sh ntp config
ntp server x.x.x.x
sh ntp information
Ntp Software Name : Cisco-ntpv4
Ntp Software Version : Cisco-ntpv4-1.0
Ntp Software Vendor : CISCO
Ntp System Type : Cisco IOS / P5040
09-19-2018 11:34 AM
Clock is unsynchronized, stratum 16, no reference clock
is this your core switch, what is X.X.X.X ?
here is my NTP reference :
ntp server 0.uk.pool.ntp.org
my NTP output for your reference.
DHCP-CA-DNS#show ntp status
Clock is synchronized, stratum 3, reference is 145.239.118.233
nominal freq is 250.0000 Hz, actual freq is 249.9132 Hz, precision is 2**10
ntp uptime is 267587800 (1/100 of seconds), resolution is 4016
reference time is DF4D14A3.AE978F30 (19:32:03.682 GMT Wed Sep 19 2018)
clock offset is 52.5760 msec, root delay is 32.75 msec
root dispersion is 139.06 msec, peer dispersion is 69.68 msec
loopfilter state is 'CTRL' (Normal Controlled Loop), drift is 0.000347060 s/s
system poll interval is 64, last update was 34 sec ago.
09-20-2018 07:08 AM
09-19-2018 04:32 PM
@Hwarraich wrote:
Clock is unsynchronized, stratum 16
1. Stratum number = the high the the number, the "less trustworthy" the source is. Stratum 16 is the highest and this equates to "not trusted".
2. The output you've posted means the core switch is not even synchronized to anything.
If you look at the output to the command "sh clock", you'll see the time starts with a "." and this means that the time and date is not to be trusted.
SO going back to the WLC2100, this means that any APs won't join the controller because the time and date of the controller isn't accurate.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide