H3C 交换机NTP时间同步配置

本案例以H3C S6900交换机为案例

要求：

H3C 核心交换机同步阿里云时间，然后该核心交换机座位内网设备的ntp服务器，内网其他的设备从该核心交换机同步时间，以保内网设备时间统一性。

H3C 核心交换机配置

如果企业有自己的时钟源可以以此为时钟源，没有的就需要核心交换机能上互联网，同步阿里或者清华等等的时钟源

[CS01]clock protocol ntp     \\设置时间协议为ntp
[CS01]clock timezone BeiJing add 08:00:00       \\采用北京时间  
[CS01]ntp-service enable     \\开启NTP服务
[CS01]ntp-service unicast-server 182.92.12.11     \\配置ntp时间服务器
[CS01]dis ntp-service status        \\查看ntp状态  
[CS01]dis ntp-service sessions       \\查看ntp会话信息 

内网其他交换机配置

该交换机同步核心交换机的ntp地址一定是要网络可达才行，且同步的ntp服务器的地址不是业务地址，防止在核心交换机上删掉误删该ip导致内网的设备同步不了时间

测试网络连通性

[F5L-HJ01]ping 16.16.17.254
Ping 16.16.17.254 (16.16.17.254): 56 data bytes, press CTRL+C to break
56 bytes from 16.16.17.254: icmp_seq=0 ttl=64 time=2.795 ms
56 bytes from 16.16.17.254: icmp_seq=1 ttl=64 time=2.150 ms
56 bytes from 16.16.17.254: icmp_seq=2 ttl=64 time=1.871 ms
56 bytes from 16.16.17.254: icmp_seq=3 ttl=64 time=2.098 ms
56 bytes from 16.16.17.254: icmp_seq=4 ttl=64 time=1.876 ms

--- Ping statistics for 16.16.17.254 ---
5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss
round-trip min/avg/max/std-dev = 1.871/2.158/2.795/0.338 ms

配置NTP时间同步

[F5L-HJ01]clock protocol ntp 
[F5L-HJ01]ntp-service enable 
[F5L-HJ01]ntp-service unicast-server 16.16.17.254 vpn-instance LAB 

[F5L-HJ01]DIS ntp-service status      \\查看ntp同步状态，可以看到clock status是synchronized 
 Clock status: synchronized
 Clock stratum: 3 
 System peer: 16.16.17.254 
 Local mode: client
 Reference clock ID: 16.16.17.254
 Leap indicator: 00
 Clock jitter: 0.000168 s
 Stability: 0.000 pps 
 Clock precision: 2^-17
 Root delay: 2.36511 ms 
 Root dispersion: 3.52478 ms 
 Reference time: eaf0f6dc.976553d7  Wed, Nov 27 2024  9:39:40.591
 System poll interval: 64 s

[F5L-HJ01]dis ntp-service sessions 
       source          reference       stra reach poll  now offset  delay disper
********************************************************************************
[12345]16.16.17.254    182.92.12.11       2   255   64   50 -0.105 2.3651 3.0975
Notes: 1 source(master), 2 source(peer), 3 selected, 4 candidate, 5 configured.
 Total sessions: 1