NTP client/server mode configuration example
Network requirements
As shown in Figure 35, perform the following tasks:
Configure the local clock of Device A as a reference source, with stratum level 2.
Configure Device B to operate in client mode and Device A to be used as the NTP server for Device B.
Figure 35: Network diagram
Configuration procedure
Assign an IP address to each interface, and make sure Device A and Device B can reach each other, as shown in Figure 35. (Details not shown.)
Configure Device A:
# Enable the NTP service.
<DeviceA> system-view [DeviceA] ntp-service enable
# Specify the local clock as the reference source, with stratum level 2.
[DeviceA] ntp-service refclock-master 2
Configure Device B:
# Enable the NTP service.
<DeviceB> system-view [DeviceB] ntp-service enable
# Specify Device A as the NTP server of Device B so that Device B is synchronized to Device A.
[DeviceB] ntp-service unicast-server 1.0.1.11
Verify the configuration:
# Verify that Device B has synchronized to Device A, and the clock stratum level is 3 on Device B and 2 on Device A.
[DeviceB] display ntp-service status Clock status: synchronized Clock stratum: 3 System peer: 1.0.1.11 Local mode: client Reference clock ID: 1.0.1.11 Leap indicator: 00 Clock jitter: 0.000977 s Stability: 0.000 pps Clock precision: 2^-18 Root delay: 0.00383 ms Root dispersion: 16.26572 ms Reference time: d0c6033f.b9923965 Wed, Dec 29 2010 18:58:07.724
# Verify that an IPv4 NTP association has been established between Device B and Device A.
[DeviceB] display ntp-service sessions source reference stra reach poll now offset delay disper ******************************************************************************** [12345]1.0.1.11 127.127.1.0 2 1 64 15 -4.0 0.0038 16.262 Notes: 1 source(master), 2 source(peer), 3 selected, 4 candidate, 5 configured. Total sessions: 1