Detailed description of NTP clock synchronization configuration on AIX 6.1

NTP synchronization server time
Currently, the NTP service is not widely used. Recently, a DB2 cluster has some requirements on time consistency, So I thought about NTP. Although timed can also be used, it is only valid for broadcast domains, NTP is more powerful.

Configuration:
First, select a server as the calibration server. Aix5l has a built-in NTP service named xntp. It can be seen from the lssrc-A. It is not started by default.

The xntp service uses/etc/NTP. the conf file is used as the startup configuration file. If the file does not exist in/etc, you can find the example under/usr/sample/xntp/. However, the example is very simple and useless.

Edit the/etc/NTP. conf file with the following content:
----------------------------
# Broadcastclient
Server 127.127.1.0
Tracefile/etc/NTP. Trace
----------------------------
Please note that the line "server XXXXX" in the file indicates the time source at the upper level of the server. It cannot work without xntp. If there is no time source at the upper level, such as on the Intranet, 127.127.1.0 is a special address, indicating that the NTP master server is synchronized with its own system clock.

Start:
After editing/etc/NTP. conf, start the xntpd daemon.
# Startsrc-s xntpd
I don't need to talk about the automatic start method.

Check:
The NTP service is not available immediately after it is started. It may take about 3-5 minutes. You can view the current NTP service status by using the lssrc command.
# Lssrc-ls xntpd

When xntpd is started, the Sys peer is 'insane ', indicating that xntpd has not completed synchronization.

# Lssrc-ls xntpd
Program name:/usr/sbin/xntpd
Version: 3
Leap indicator: 11 (LEAP indicator is insane .)
Sys peer: no peer, system is insane
...

Wait 3-5 minutes and the Sys peer will no longer be 'insane.

# Lssrc-ls xntpd
Program name:/usr/sbin/xntpd
Version: 3
Leap indicator: 00 (no leap second today .)
Sys peer: 127.127.1.0
...

Client synchronization:

Ntpdate (Server IP) enables the client to update to the server time. You can use cron To Set regular updates to maintain time consistency.

For reprint, please indicate the source and original article links:

Http://blog.csdn.net/xiangsir/article/details/8570441