Configuring Internal NTP Servers

Updated

On this page

HyperScale X leverages the public RHEL Network Time Protocol (NTP) servers to maintain time synchronization. Configure the nodes if your environment requires the use of internal NTP servers to enforce synchronization.

Procedure

  1. Login to the first node in the storage pool using an SSH or KVM Console connection.

  2. Edit the following file, using a text editor such as nano, vi or vim:

    /etc/chrony.conf

  3. Edit the following section of the configuration file, replacing the rhel.pool.ntp.org addresses with the desired NTP server's IP address.

    # Use public servers from the pool.ntp.org project.

    # Please consider joining the pool (http://www.pool.ntp.org/join.html).

    server 0.rhel.pool.ntp.org iburst maxpoll 10

    server 1.rhel.pool.ntp.org iburst maxpoll 10

    server 2.rhel.pool.ntp.org iburst maxpoll 10

    server 3.rhel.pool.ntp.org iburst maxpoll 10
  4. Save the file and exit.

  5. Restart the chronyd service as follows:

    # systemctl restart chronyd.service
  6. Verify the NTP configuration, using the following command:

    # chronyc sources

    Output similar to the following will be displayed:

    Each server should be listed with details of the connection.

    Note: Depending on how far off the existing time on the node was, the NTP client will slowly bring the time in sync. Large time jumps can result in erratic application behavior, so it is recommended to allow the system to sync slowly.

    If the time is off by a significant factor and is preventing the node from operating properly (such as failing certificate verification), you can force an immediate synchronization using the following steps:

    1. Force an immediate synchronization, using the following command:

      #chronyc -a makestep
    2. It is recommended that you restart the Commvault services using the following command:

      # commvault restart
  7. Repeat all of these steps for all of the nodes in the cluster.