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

Yesterday, the customer's intranet network equipment was configured with NTP service, using Huawei 9303 as the NTP server, and the other devices were NTP clients. However, all Huawei devices were successfully synchronized to the NTP server, while H3C devices were unable to synchronize properly.

The Huawei switch is configured as a server as follows:

Ntp-service refclock-master 2

Ntp-service authentication enable

Ntp-service source-interface loopback0

Ntp-service authentication-keyid 1 authentication-mode md5 simple admin

Ntp-service reliable authentication-keyid 1

Undo ntp-service disable

The Huawei switch is configured as a client as follows:

Ntp-service authentication enable

Ntp-service authentication-keyid 1 authentication-mode md5 simple admin

Ntp-service reliable authentication-keyid 1

Ntp-service unicast-server 10.1.1.1

The H3C cannot synchronize the device configuration as follows:

Ntp-service enable

Ntp-service authentication enable

Ntp-service authentication-keyid 1 authentication-mode md5 simple admin

Ntp-service reliable authentication-keyid 1

Ntp-service unicast-server 10.1.1.1

Configuration is not asked.

View the details of the local device NTP session

Huawei server:

Display ntp-service sessions verbose

9303 > DIS NTP sessions verbose

Clock source: 127.127.1.0

Clock stratum: 1

Clock status: configured, master, sane, valid

Reference clock ID: LOCAL (0)

Local mode: client, local poll: 64, current poll: 64

Peer mode: server, peer poll: 64, now: 20

Offset: 0.0000 ms, delay: 0.00 ms, disper: 0.97 ms

Root delay: 0.00 ms, root disper: 10.00 ms

Reach: 377, sync dist: 0.011, sync state: 4

Precision: 2 ^ 17, version: 3, peer interface: InLoopBack0

Reftime: 17 DF0335A2.80851A86 45 reftime 06.502 UTC Jul 25 2018 (DF0335A2.80851A86)

Orgtime: 17 DF0335A2.80851A86 45 orgtime 06.502 UTC Jul 25 2018 (DF0335A2.80851A86)

Rcvtime: 17 DF0335A2.808626F6 45 rcvtime 06.502 UTC Jul 25 2018 (DF0335A2.808626F6)

Xmttime: 17 DF0335A2.80842FA5 45 xmttime 06.502 UTC Jul 25 2018 (DF0335A2.80842FA5)

Filter delay: 0.00 0.00 0.00

Filter offset: 0.00 0.00 0.00

Filter disper: 0.00 0.00 0.01 0.01 0.00 0.00 0.00

Reference clock status: normal

H4C client:

Display ntp-service sessions verbose

Clock source: 10.1.1.1

Session ID: 56760

Clock stratum: 16

Clock status: configured, insane, valid, unsynced

Reference clock ID: INIT

* × × instance: none

Local mode: client

Local poll interval: 6

Peer mode: unspec

Peer poll interval: 10

Offset: 0.0000ms

Roundtrip delay: 0.0000ms

Dispersion: 0.0000ms

Root roundtrip delay: 0.0000ms

Root dispersion: 0.0000ms

Reachabilities:0

Sync distance: 0.0010

Precision: 2 ^-20

Version: 4

Source interface: Not specified

Reftime: 00000000.00000000

Thu, Feb 7 2036 14:28:16.000

Orgtime: df021d74.804177f0 Wed, Jul 25 2018 5:49:40.500

Rcvtime: 00000000.00000000 Thu, Feb 7 2036 14:28:16.000

Xmttime: 00000000.00000000 Thu, Feb 7 2036 14:28:16.000

Roundtrip delay samples: 0.000 0.000 0.000

Offset samples: 0.00 0.00 0.00

Filter order: 0 1 2 3 4 5 6 7

Total sessions: 1

You can see Clock status: configured, insane, valid, unsynced

Check the official document: (status of the session. The value and meaning of this field are:

Configured: indicates that the session was established by the configuration command

Dynamic: indicates that the session is dynamically generated

Master: indicates that the time server corresponding to this session is the master time server of the current system.

Selected: indicates that the clock of the time server corresponding to this session has passed the clock selection algorithm.

Candidate: indicates that the clock of the time server corresponding to the session is the candidate clock

Sane: indicates that the time server corresponding to the session is authenticated, and the clock of the time server will be used as the reference clock

Insane: indicates that the time server corresponding to the session is not authenticated, or that the time server is authenticated but its clock is not used as a reference clock

Valid: indicates that the time server corresponding to the session is valid (verified, synchronized, valid number of layers, root delay / deviation not out of bounds, etc.)

Invalid: indicates that the corresponding time server for this session is invalid

Unsynced: indicates that the clock of the time server corresponding to the session is not synchronized or the number of layers is illegal)

It can be seen that the server is valid, it may be a verification failure or the clock is not used as a reference clock, verify that the configured password is the same, then look at the others and find that the version is inconsistent.

One is version: 4, the other is version: 3. The higher version is supposed to be compatible with the lower version, but there is no other reason why it cannot be synchronized.

Force a downgrade on H3C

Ntp-service unicast-server 10.1.1.1 version 3, about one minute, shows that the synchronization is successful. OK, it's done.

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.