Forum Discussion
Peer Timing out of sync
Hey Guys,
Wondering if I get some assistance to a small timing issue issues between devices.
I recently upgraded to 13.1.1 from 12.1.2, everything is in sync and look good except and when I got the following WARNING:
'System timing of device does not match one or more system times of the device trust and do not match the system time of the local device." Ran a show /sys service ntp to verify ntp was running as well as a ntpq -np to verify ntp peer server communications.
Did a show /cm and noticed the time delta on one device is 8 seconds different that the other device.
Tried to modify /sys db configsync.timesyncthreshold value to 8, BUT still no joy.
Restarted ntpd and the devices itself. Still showing the 8 second peer time out of sync.
Is there a way to get the timing back within standards? Maybe removing the device trust/groups and re-establishing (just a guess) so please, any ideas would be appreciated.
- socar65
Nimbostratus
I also read some Linux verbage that would require me to expand the ntp.conf mix/max iburt for the NTP SERVERS. Has anyone else had to do this as well to restore the "Peer Timing out of sync?"
- FrancisOlivier
Nimbostratus
Hello
I had exactly the same issue. my problem was located in 2 points
1 - F5 side: Vlan issue ( Selected Vlan to NTP was different from Cluster Members)
2 - Private NTP Server: NTP public servers were suddently unreachable from my server; after modifying the list of public ntp servers, Issue is resolve.
Regards.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com