A customer added an NTP server to provide a clock source for the company's internal equipment, but when configuring, the customer found that the clocks of several Huasan switches could not be synchronized. As shown in the figure below:
Treatment process
The NTP configuration on the 1. device is as follows:
NTP- Service Access Server 200 1
Ntp service unicast server vpn instance management 10.xx.xx.30
#
Acl number 200 1
Rule 5 allows vpn instances to manage the source 10.xx.xx.30 0.
Rule 100 Rejected
Copy after login
There are some other operations before checking the device configuration. For this problem, because some devices can synchronize the clock normally, it is necessary to pay attention to the difference between devices that can synchronize the clock normally and devices that can't, including but not limited to version information, device model, command line, etc. By comparison, it is found that the devices that can synchronize clocks normally belong to the platform of H3C V7, and those that can't register normally belong to the platform of V5. There are still some differences between the command lines of V5 and V7 platforms, which need our attention. The above is the NTP configuration of V5 platform.
2. First check the connectivity between the switch and NTP server. Of course, only the connectivity between IPS is checked here, and the connectivity of UDP port 123 cannot be checked. But we can indirectly check whether there is a problem with connectivity through the interaction of debugging information and messages of the device.
3. You can turn on NTP debugging of the switch through the commands Terminal Monitor, Terminal Debugging, Debugging NTP- Service All in turn, and you can see the interaction of NTP messages, indicating that there is no problem with connectivity.
* February 6, 05: 33: 25: 789 20134 # kunanbglntp/7/packet _ send:
Package to 10.xx.xx.30, length: 48.
Leap: 3, version: 3, mode: 3, vrfindex: 1
Class: 16, voting: 6, accuracy: 2-19.
rdel: 0.000，rdsp: 46955.643，refid: INIT
Reftime: 00000000.00000000, February 7th, 2036, 6:28: 16.000.
Organization time: 00000000.0000000 Thursday, February 7, 2036, 6:28: 16.000.
Remittance time: 00000000.000000 Thursday, February 7, 2036 at 6:28: 16.000.
Xmttime: d4bc69a5.c9a0940b Wednesday, February 6th 20 13 5:33:25.787.
* March 20201316: 41:18: 78 zhl-9508-01NTP/7/debug _ NTP _ packet _ RCV;
Packets from 10.xx.xx.30 to 10.xx.xx.254 on LoopBack0.
Leap: 0, version: 4, mode: 4, vrfindex: 1
Class: 9, vote: 64, accuracy: 218.
rdel: 10.345，rdsp: 3 1.89 1，refid: 10.80 . 25 1.254
March 65438 UTC, 2020. C 10B73D 1)
org time: 16:40: 13.747 UTC Mar 13 2020(e 2 1635 ed。 BF4EB9A 1)
March 65438 UTC, 2020. C 10B73D 1)
March 2020 13 UTC (E216362e.102cb20f)
Time:16: 41:18.077 March 202013 (e 216362e.13b9bed3)
Copy after login
From the debugging log above, we can see that both received and sent messages can be captured, which indicates that there is no problem with the connection. However, when we look at the details of the message, we find that the version of the NTP message sent is 3, but the version information received from the NTP server is 4. Solid judgment is caused by inconsistent versions at both ends.
Summary:
When dealing with NTP, we should pay attention to the following points:
Is a function of 1 NTP on? ? There are some differences between different devices. For example, H3C V5 platform is turned on by default, but V7 platform needs to manually turn on "ntp-service enable".
2. Make sure that you have correctly pointed to the NTP server.
3. Ensure that NTP servers can be routed.
4. Ensure that the NTP service port of NTP server has not been modified.
5. Ensure that the parameters at both ends of NTP are consistent; For example, version information and mode information (3 for the client and 4 for the server)
network
network protocol
Glasses order business system, the boss said good before!
Unique domain
advertisement
H3C_NTP Clock Synchronization Basic Configuration Case
4 Download 0 comments
April 26(th), 2022
NTP Configuration of H3C Switch
Download 4 comments
20 1 1 1 1.8
H3C S3 100V3-SI switch sets NTP time.
Read 0 comments 3 like 8854.
20 19 February 12
Huawei NTP configuration command, comprehensive
1895 Read 0 comments 1 like it.
202 1 12 19
H3c NTP configuration of huasan
7982 Read 0 comments 2 like it.
65438+February 20, 2020
[H3C experimental environment] NTP internal and external networks cannot be synchronized.
1 145 Read 0 comments 1 like it.
September 25(th), 2020
Wd tv, a complete collection of pictures, click to view details!
Selected recommendation
advertisement
Huawei /H3C switch is configured with NTP clock synchronization.
Read 0 comments 0 likes 386
165438+2022 10/2
Huawei switch failed to configure ntp service time automatic synchronization, which was not synchronized.
Read 0 comments 0 likes 4228.
202 1 June 17
H3C switch configuration NTP
1377 Read 0 comments 0 likes it.
August 2022 10
Solution of Time Synchronization Caused by Inconsistent NTP Version between Huawei and H3C Switch
Read 0 comments 0 likes 4929.
2065438+July 27, 2008
NTP protocol
1.7W Read 0 comments 3 like it.
2065438+March 6, 2009
Huawei switch cannot handle synchronization failure with Windows NTP clock server.
Read 0 comments 0 likes 2395
20 1610 June16
H3C switch loop monitoring, NTP time synchronization.
Read 0 comments 0 likes 2953
202128 February
H3C NTP experiment
Read 1 comment 0 Like it.
June 23(rd), 2022
Time zone setting and time synchronization of H3C switch
6.0W Read 0 comments 1 like it.
April 5, 2065 438+07
How to set the time of Hua San switch
3. 1W Read 0 comments 4 like it.
2065438+May 27, 2009
H3C switch settings are synchronized with the wireless controller time.
1689 Read 0 comments 1 like it.
202065438+1October 24th.
Go to home page
See more popular content