Shulou(Shulou.com)06/02 Report--

1. AIX server-side? Edit the / etc/ntp.conf file as follows:

-

# broadcastclient

Server 210.72.145.44 prefer

Server 218.21.130.42

Server 127.127.1.0

Driftfile / etc/ntp.drift

Tracefile / etc/ntp.trace

-

Notice the line server 127.127.1.0 in the file, where 127.127.1.0 is a special address indicating that the NTP master server is synchronized with its own system clock.

? Then start the xntpd service

# startsrc-s xntpd

0513-059 The xntpd Subsystem has been started. Subsystem PID is 7274732.

? View xntpd status:

# lager thanks to c-ls xntpd

Program name: / usr/sbin/xntpd

Version: 3

Leap indicator: 11 (Leap indicator is insane.) / / initialization is not completed

Sys peer: no peer, system is insane / / initialization is not completed

Sys stratum: 16 / / initialization is not completed

Sys precision:-17

Debug/Tracing: DISABLED

Root distance: 0.000000

Root dispersion: 0.000000

Reference ID: no refid, system is insane / / initialization is not completed

Reference time: no reftime, system is insane / / initialization is not completed

Broadcast delay: 0.003906 (sec)

Auth delay: 0.000122 (sec)

System flags: bclient pll monitor filegen

System uptime: 40 (sec)

Clock stability: 0.000000 (sec)

Clock frequency: 0.000000 (sec)

Peer: 127.127.1.0

Flags: (configured) (refclock)

Stratum: 3, version: 3

Our mode: client, his mode: server

Peer: 218.21.130.42

Flags: (configured)

Stratum: 16, version: 3

Our mode: client, his mode: unspecified

Peer: 210.72.145.44

Flags: (configured) (preferred)

Stratum: 16, version: 3

Our mode: client, his mode: unspecified

Subsystem Group PID Status

Xntpd tcpip 7274732 active

After waiting for 6-10 minutes, sys peer is no longer an insane'.

Second, AIX client? Add in / etc/ntp.conf

Server 192.168.15.92

Driftfile / etc/ntp.drift

Tracefile / etc/ntp.trace

? After editing the / etc/ntp.conf, start the xntpd daemon

# startsrc-s xntpd

? Xntpd status query, using # lumped status query c-ls xntpd

When xntpd is first started, a sys peer of 'insane', indicates that xntpd has not completed synchronization.

# lager thanks to c-ls xntpd

Peer: 192.168.1.1

? NTP client query NTP server / / optional

The ntp client uses the ntpdate command to confirm that time synchronization is available with the specified ntp server.

The result of the command shows the time offset between the client and the server.

# ntpdate-d 192.168.15.92

? By calling smitty, xntpd can start automatically when the server is restarted later.

# smit xntpd

Select Start Using the xntpd Subsyste

Select BOTH mode to start immediately and the system will start automatically the next time it starts

As you can see from the following command, xntpd is actually a sub-service of the tcpip service group.

# lager tcpip c-g

Subsystem Group PID Status

Inetd tcpip 303118 active

Snmpd tcpip 651356 active

Xntpd tcpip 589898 active

……

Similarly, / etc/rc.tcpip can see the following, indicating that the service is started with the TCPIP service group

# Start up Network Time Protocol (NTP) daemon

Start / usr/sbin/xntpd "$src_running"

The time offset between the client and the server is too large, so even if the client xntpd daemon is started, the client cannot synchronize with the server, and the ntp process shuts down automatically. You need to manually modify the time before doing ntp synchronization.

The following normal output:

Synchronize with the ip server with a * sign

3. Linux configure ntp client? Configure ntp.conf

# vi / etc/ntp.conf

Restrict default kod nomodify notrap nopeer noquery

Restrict-6 default kod nomodify notrap nopeer noquery

Restrict 127.0.0.1

Restrict-6:: 1

Server 127.127.1.0 # local clock

Fudge 127.127.1.0 stratum 10

Driftfile / var/lib/ntp/drift

Keys / etc/ntp/keys

Server 192.168.15.92 prefer

? Restart the ntp service

# service ntpd restart

? View ntp

# ntpq-p

Remote refid st t when poll reach delay offset jitter

=

LOCAL (0) .LOCL. 10 l 17 64 17 0.000 0.000 0.001

* 192.168.15.92 LOCAL (0) 4 u 29 64 17 0.397-2.224 0.786

With a * sign, it indicates that the IP is the NTP time synchronization.

4. Windows client configures NTP

Note: windows in domain mode cannot use NTP

? FAQ

A1: if the ntpq-p report is executed

Temporary failure in name resolution

Q1: the hosts file does not have 127.0.0.1 record

Add 127.0.0.1 to the hosts file

127.0.0.1 localhost.localdomain localhost

Restart the ntp service

# Service ntpd restart

A2: if you execute ntpq-p report

Read: A remote host refused an attempted connect operation

Q2: the difference between system time and ntp time is too big, which needs to be adjusted manually.

Manually adjust the time and restart the ntp service

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.