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
тАО07-01-2009 02:55 AM
тАО07-01-2009 02:55 AM
Hi admins,
I have 2 ntp servers .primary and secondary.
i have configured both in /etc/ntp.conf and /etc/rc.config.d/netdaemons
its working fine primary as master and secondery as optional(+)
but i commented(#) primary in ntp.conf so secondary should act as master with next time sync. But it shows previous output only.when i
restarted xntpd it shows sec ans master.
without restring xntpd i want secondery acts as master
help me on this
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-01-2009 03:13 AM
тАО07-01-2009 03:13 AM
Re: ntp
The ntp client only reads the config file at startup. You can use the xntpdc command to add and remove services if you set up the ntp security keys. Restarting ntp on a sychronised system usualy has little effect.
Check the offsets with ntpdate first though.
However there is no real concept of secondary and primary time servers. ntp works out which is the most reliable time server and chooses that as the server to synchronise the clock with. If you only use two time sources it will flip flop between them, because it never quite knows which is correct. You should use a third one to give you a casting vote. So if two agree and one has gone wrong you still have a reliable time setting .
I hope this helps
Mike
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-01-2009 03:24 AM
тАО07-01-2009 03:24 AM
Re: ntp
my concern is if first server crashed,the second one should take care of time syncing.
in ntp.conf and netdaemons i have mentione dboth servers
ntp.conf
------
10.10.15.10
10.10.18.23
NETDAEMONS
-------
export NTPDATE_SERVER='10.10.15.10 10.10.18.23'
export XNTPD=1
export XNTPD_ARGS=
regards
himacs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-01-2009 03:33 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-01-2009 03:35 AM
тАО07-01-2009 03:35 AM
Re: ntp
Your ntp setup should work as a sort of cluster.
If both servers have access to external time sources, then if primary is gone for a while nothing bad will happen.
The key is to configure the internal systems connecting to use both servers, then you will be fine.
ntp was designed as an active active highly available mode of operation.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-01-2009 04:02 AM
тАО07-01-2009 04:02 AM
Re: ntp
BUPA is correct. A good setup uses at least three time sources to avoid synchronization with an "insane" timekeeper. As NTP works you may see a different time source "promoted". This is normal and occurs if/when NTP decides that a better source exists.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-01-2009 09:12 PM
тАО07-01-2009 09:12 PM
Re: ntp
/sbin/init.d/xntpd start
2 Jul 09:08:58 ntpdate[23513]: step time server 10.10.45.21 offset -288.642757 sec
here whats step time server...whether it means secondery one..
regards
himacs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-02-2009 04:53 AM
тАО07-02-2009 04:53 AM
Re: ntp
> 2 Jul 09:08:58 ntpdate[23513]: step time server 10.10.45.21 offset -288.642757 sec
The step time message comes from ntpdate and it shows you the result of the ntpdate call (using the list in /etc/rc.config.d/netdaemons ). the message shows you that it had to adjust the time by 288 seconds to line it up with the ntp server at address 10.10.45.21. Which by the way was not one of the addresses you mentioned earlier. The start script then moves on and starts ntpd using the ntp.conf settings .
Regards
Mike