Create the file /etc/inet/ntp.conf with the following entries:
server <0.0.0.0 > (Some document says it can be hostname as well. Please use IP
for safer option)
driftfile /var/ntp/ntp.drift
• Create the file /var/ntp/ntp.drift with the following entry
0.0 → It inform to NTP daemon rate of drift of client clock.
• Restart NTP services
• Solaris 8/9 – Use /etc/rc2.d/S74xntd stop/start
• Solaris 10 – Use svcadm restart ntp
• Check Status
• #ntpq
• ntpq> peers
remote refid st t when poll reach delay offset disp
=====================================================
*NTP Server IP some_ip 2 u 29 64 377 0.52 -13.796 0.93
• According to Sun, NTP can only sync time if it is off by no more than 17 minutes.
Furthermore, adjusting time being off by seconds will take several minutes because NTP is
architected to slowly adjust to the NTP master's time. It may also be adviseable to to use rdate
daily\weekly to account for systems that, for whatever reason, have their clocks off by more
than 17 minutes.
• Do not try this on a cluster. You need to shutdown the cluster when changing the cluster nodes
time
• Solaris Zones sync their time with Global Zones. So NTP Client configuration will not work for
Zones.
• Refer following links for detailed design, architecture, administration of NTP functioning.
• http://www.sun.com/blueprints/0701/NTP.pdf
• http://www.sun.com/blueprints/0801/NTPpt2.pdf
• http://www.sun.com/blueprints/0901/NTPpt3.pdf
• use ntpdate or rdate to sync time instantaneously
• NTP uses UDP Port – 123 for all communications.
• In case of using Multiple NTP Server, add flag “prefer” in front of your preferred server. Else,
NTP protocol will identify accuracy based on its algorithm and sync accordingly.
• Use multicasr or broadcast in case client need to use any broadcasted/multicasted packets on
network from any NTP server
• multicastclient 224.0.1.1 → Default address is used if not specified. You can specify any other
multicast address as well.
• Broadcastclient word do not require any address in front of it as it listens all brodcasted packets
server <0.0.0.0 > (Some document says it can be hostname as well. Please use IP
for safer option)
driftfile /var/ntp/ntp.drift
• Create the file /var/ntp/ntp.drift with the following entry
0.0 → It inform to NTP daemon rate of drift of client clock.
• Restart NTP services
• Solaris 8/9 – Use /etc/rc2.d/S74xntd stop/start
• Solaris 10 – Use svcadm restart ntp
• Check Status
• #ntpq
• ntpq> peers
remote refid st t when poll reach delay offset disp
=====================================================
*NTP Server IP some_ip 2 u 29 64 377 0.52 -13.796 0.93
• According to Sun, NTP can only sync time if it is off by no more than 17 minutes.
Furthermore, adjusting time being off by seconds will take several minutes because NTP is
architected to slowly adjust to the NTP master's time. It may also be adviseable to to use rdate
daily\weekly to account for systems that, for whatever reason, have their clocks off by more
than 17 minutes.
• Do not try this on a cluster. You need to shutdown the cluster when changing the cluster nodes
time
• Solaris Zones sync their time with Global Zones. So NTP Client configuration will not work for
Zones.
• Refer following links for detailed design, architecture, administration of NTP functioning.
• http://www.sun.com/blueprints/0701/NTP.pdf
• http://www.sun.com/blueprints/0801/NTPpt2.pdf
• http://www.sun.com/blueprints/0901/NTPpt3.pdf
• use ntpdate or rdate to sync time instantaneously
• NTP uses UDP Port – 123 for all communications.
• In case of using Multiple NTP Server, add flag “prefer” in front of your preferred server. Else,
NTP protocol will identify accuracy based on its algorithm and sync accordingly.
• Use multicasr or broadcast in case client need to use any broadcasted/multicasted packets on
network from any NTP server
• multicastclient 224.0.1.1 → Default address is used if not specified. You can specify any other
multicast address as well.
• Broadcastclient word do not require any address in front of it as it listens all brodcasted packets
No comments:
Post a Comment