98
[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
IPv6 NTP client/server mode configuration example
Network requirements
As shown in
, 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 IPv6 NTP server
for Device B.
Figure 37
Network diagram
Configuration procedure
1.
Assign an IP address to each interface, and make sure Device A and Device B can reach each
other, as shown in
. (Details not shown.)
2.
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
3.
Configure Device B:
# Enable the NTP service.
<DeviceB> system-view
3000::34/64
3000::39/64
Device A
Device B
NTP server
NTP client
Summary of Contents for FlexNetwork 10500 SERIES
Page 224: ...213 ...
Page 311: ...300 Now the system can record log information to the specified file ...