- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: NTP .increase the 128ms treshold to avoid "syn...
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
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
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
тАО11-05-2008 01:35 AM
тАО11-05-2008 01:35 AM
Re: NTP .increase the 128ms treshold to avoid "synchronisation lost" alarm
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-05-2008 01:39 AM
тАО11-05-2008 01:39 AM
Re: NTP .increase the 128ms treshold to avoid "synchronisation lost" alarm
Sorry your second post crossed over while I was constructing my reply and I did not see it until it was finished ,
orphan mode should work on 4.1.2
the drift file value 132.005 is not too bad but I would be inclined to clear it anyway .
mike
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-05-2008 01:47 AM
тАО11-05-2008 01:47 AM
Re: NTP .increase the 128ms treshold to avoid "synchronisation lost" alarm
the ntpd should create the drift file again ?
thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-05-2008 03:47 AM
тАО11-05-2008 03:47 AM
Re: NTP .increase the 128ms treshold to avoid "synchronisation lost" alarm
It will not fix the problem on its own!
If you remove the drift file and NTP will recreate it for you with new values , but to fix the problem you need to do all the other things as well.
The problem, I think, is that your system is flip flopping between being in synch with itself and in synch with the NTP server.
You can see this by monitoring the ntpq -p output which will vary from being in synch with LOCAL to in synch with ntpd1. One of the side effects of this is an incorrect frequency drift value another is the messages you have seen.
The orphan mode in NTP V4 provides a cure for this but the lines
server 127.127.1.0 # local clock
fudge 127.127.1.0 stratum 10
have to come out of the ntp.conf file and be replaced with
tos orphan 7
(7 is two more than 5 from your rv output )
The setting of the system clock with ntpdate, followed by the setting of the hardware clock, and emptying the drift file give NTP a clean starting point to work from.
Mike
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-05-2008 04:59 AM
тАО11-05-2008 04:59 AM
Re: NTP .increase the 128ms treshold to avoid "synchronisation lost" alarm
fudge 127.127.1.0 stratum 10
tos orphan 7
please tell me if im correct:
the orphan designed to replace the local clock driver if the local clock failed.
the fudge is the priority of the redundancy
if so what is fudge 10 for local clock ?
thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-05-2008 05:08 AM
тАО11-05-2008 05:08 AM
Re: NTP .increase the 128ms treshold to avoid "synchronisation lost" alarm
is this the new configuration suppose to be like:
#server 127.127.1.0 # local clock
#fudge 127.127.1.0 stratum 10
tos orphan 7
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-05-2008 07:23 AM
тАО11-05-2008 07:23 AM
Re: NTP .increase the 128ms treshold to avoid "synchronisation lost" alarm
Your last post is correct but I would just delete the lines.
Please try all of the updates and suggetions in my 9.24 post and let me know how you get on .
to answer the other two questions.
orphan mode in fact replaces the need to use the local clock driver when you become disconnected from all other reliable time sources.
The fudge command sets the stratum layer for your local clock to 10. Briefly this means that your local time is now considered by NTP be less reliable than time from other sources.
- « Previous
-
- 1
- 2
- Next »