Home > Articles > Operating Systems, Server > Solaris

Like this article? We recommend

Section 2.10: Configure ntp.conf on Each Cluster Node

On each node of the cluster, the /etc/inet/ntp.conf file must be updated to reflect the actual cluster configuration. This helps ensure cluster nodes recover (that is, reboot and reconfigure) more rapidly, and does not attempt to establish a running cluster using nodes that do not exist (because cluster nodes 3 through 8 are NOT configured).

  • Remove all entries for private host names that are not actively used in the cluster.

  • Private host names are normally modified and configured using scsetup.

  • An nsswitch.conf facility performs all lookups for private hostnames.


Cluster nodes are not to be configured as an NTP server. Enter the designated NTP server in the /etc/inet/ntp.conf file. Also, if you have changed the private host names of the cluster nodes, update this file accordingly to reflect the customer-specific private hostnames. For additional information, refer to the Network Time Protocol User's Guide, and the ntpdate(1M) man pages, for invoking the NTP from within cron scripts.

Step 2.10.1

On each cluster node, create and configure the /etc/inet/ntp.conf file. First, copy /etc/inet/ntp.conf.cluster to /etc/inet/ntp.conf.Next, edit /etc/inet/ntp.conf to comment out the host name entries for any cluster nodes that are not actually configured in the cluster. Verify the entries, as indicated:

# more /etc/inet/ntp.conf

...{{output omitted}}
peer clusternode1-priv prefer
peer clusternode2-priv
#peer clusternode3-priv
#peer clusternode4-priv
#peer clusternode5-priv
#peer clusternode6-priv
#peer clusternode7-priv
#peer clusternode8-priv

. . . {{output omitted}}


For this two-node configuration, only the first two cluster node entries are required.

  • + Share This
  • 🔖 Save To Your Account