After the NTP server is configured on the eBackup portal, the NTP of the active eBackup node points to the configured NTP server. Other nodes point to the master node.
Possible causes:
1. The network between the eBackup node and the NTP server is abnormal.
Troubleshooting Procedure:
Log in to the active eBackup node and run the ping command to check the network connectivity between the eBackup node and the NTP server. If the NTP server can be pinged, run the ntpq -p command to check the configured NTP server. If there is no asterisk (*) or plus sign (+) before the NTP server in the command output, the NTP server is faulty. Check the NTP server or the operating system.
2. The NTP level configured on eBackup exceeds 15.
IP address of the node for which the alarm is generated. Run the ntpq -p command to check whether the value of the st column exceeds 15. The value of the st column cannot exceed 15. If the value of the st column exceeds 15, the time cannot be synchronized. The upper-layer NTP server must be configured as the NTP server.
The NTP uses the hierarchical synchronization mode. Generally, the clock source at the n+1 level is synchronized with the clock source at the nth level. NTP supports a maximum of 16 layers of synchronization, that is, layers 0 to 15. More than 16 layers will not be synchronized. Note that the value of st indicates the level of the remote host. If the remote host is the NTP server of the current host, the level of the current host is st+1.
