- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: NTP Stratum 11
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-10-2011 06:45 AM
08-10-2011 06:45 AM
Hi All,
can someone explain why NTP is reporting @ stratum 11 - I am guessing that there is some configuration at the NTP server that isnt quite correct ....
remote refid st t when poll reach delay offset disp
==============================================================================
*coredns LOCAL(0) 11 u 81 128 377 13.93 -0.427 0.49
Thakns
Chris
Solved! Go to Solution.
- Tags:
- NTP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-10-2011 07:40 AM - edited 08-10-2011 07:44 AM
08-10-2011 07:40 AM - edited 08-10-2011 07:44 AM
Re: NTP Stratum 11
Hi:
Either you haven't configured viable time sources or they aren't reachable. As a fall-back, NTP is using your server's local clock. You can use 'ntpq -pn' to troubleshoot.
Too, make sure that your server's time is close to the correct time. NTP will abandon synchronization if the difference of the true time and the server's time is too large. Verify your server time with 'date -u' and compare that value to an external clock. If this is the problem, adjust your server time to match an external source and stop/start the NTPD daemon again.
Remember stepping a server's time forward is rarely a problem. Stepping it backwards can play havoc with source control systems, logs and databases. If you need to roll the time backwards, I suggest shutting down the databases; changing the time; and simply rebooting.
Regards!
...JRF...
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2011 03:46 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2011 12:07 AM
08-25-2011 12:07 AM
Re: NTP Stratum 11
Just a little clarification: to me, this looks like the local xntpd can connect to the remote NTP server on host "coredns" just fine, but the "coredns" system is using its internal clock instead of any better time sources.
(coredns is listed as a remote timesource, and it has a non-zero delay value. The refid field is reported by coredns. Its timesource has stratum 10, which would be typical for a local clock with some default NTP configurations. "Real" timesources like GPS time receivers are defined as stratum 0, and NTP daemons directly connected to them are stratum 1.)