Solaris Cluster Node/System/Server Do Not Sync Time with Newly Added NTP Server
Last updated on JUNE 08, 2017
Applies to:Solaris Cluster - Version 3.3 U2 to 4.3 [Release 3.3 to 4.3]
Solaris Cluster Geographic Edition - Version 3.3 U2 to 4.3 [Release 3.3 to 4.3]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
Solaris Cluster does support usage of NTP server (running outside of the cluster) as time sources. In order to have a minimally working config even in cases where ntp server are not configured, the Solaris Cluster software does provide some default configuration files in order to configure ntp on the nodes. If the cluster software get installed without any prior NTP configuration in place, the provided NTP config files are meant to setup the nodes as NTP peers of one another and without any external NTP server.
A NTP server directive was added to /etc/inet/ntp.conf using the pre-existing /etc/inet/ntp.conf supplied by cluster.
Therefore the "ntpq -p" command shall report an * sign near the name of the NTP server when the node have selected and used as time source.
However, the date/time on the cluster nodes do not converge to the time supplied by the NTP servers and the "ntpq -p" command do not report the NTP server as selected.
This resulting ntpq output will show both nodes (since they are peers) as well as the external server, but this is not going to be selected as time source (not flagged with *) even if you wait for long time for the synchronization to happen.
In order to synchronize cluster nodes with an external NTP server, the /etc/inet/ntp.conf file was edited adding lines with the "server" directive and the cluster nodes were shutdown and rebooted.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms