Forum Discussion
Dazzla_20011
Nimbostratus
Jul 12, 2011The BIG-IP ntpd process is unable to communicate with the NTP server
Hi,
Following a power down our GTM is reporting the following errors.
Time difference between GTM and me is 66 seconds -- Make sure NTP is running and GTM times are in sync.
It seems the solution is to restart the ntpd process. Could restarting this process cause any problems or loss of service?
Thanks
Darren
4 Replies
- hoolio
Cirrostratus
I don't think restarting NTP should have any impact on GTM. You can check ntp using these links:
http://devcentral.f5.com/Forums/tabid/53/aft/59890/Default.aspx59899
SOL10240: Verifying Network Time Protocol peer server communications
https://support.f5.com/kb/en-us/solutions/public/10000/200/sol10240.html
Searching for ntpq also returns this related solution:
SOL7017: The BIG-IP ntpd daemon is unable to communicate with the NTP server
https://support.f5.com/kb/en-us/solutions/public/7000/000/sol7017.html
If you get stuck on this, you might try searching online for related docs or opening a case with F5 Support.
Aaron - Nathan_Houck_65
Nimbostratus
It could be this as well ....
sol9356: The eventlib timer causes time differences between BIG-IP GTM sync group members
https://support.f5.com/kb/en-us/solutions/public/9000/300/sol9356.html?sr=13763717 - Dazzla_20011
Nimbostratus
Thanks for the help. Restarting the ntpd process on both GTMs fixed the issue. - hoolio
Cirrostratus
Hi Darren,
Thanks for confirming.
Aaron
Recent Discussions
Related Content
DevCentral Quicklinks
* 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
Discover DevCentral Connects
