Configuring ntp multicast mode, Network requirements – H3C Technologies H3C SecPath F1000-E User Manual
Page 132
20
Clock status: synchronized
Clock stratum: 3
Reference clock ID: 3.0.1.31
Nominal frequency: 64.0000 Hz
Actual frequency: 64.0000 Hz
Clock precision: 2^7
Clock offset: 0.0000 ms
Root delay: 31.00 ms
Root dispersion: 8.31 ms
Peer dispersion: 34.30 ms
Reference time: 16:01:51.713 UTC Sep 19 2005 (C6D95F6F.B6872B02)
As shown above, Device A has been synchronized to Device C and the clock stratum level of Device A
is 3, while that of Device C is 2.
# View the NTP session information of Device A, which shows that an association has been set up
between Device A and Device C.
[DeviceA-GigabitEthernet0/1] display ntp-service sessions
source reference stra reach poll now offset delay disper
**************************************************************************
[1234] 3.0.1.31 127.127.1.0 2 254 64 62 -16.0 32.0 16.6
note: 1 source(master),2 source(peer),3 selected,4 candidate,5 configured
Total associations : 1
Configuring NTP Multicast Mode
Network requirements
As shown in
, Device C functions as the NTP server for multiple devices on different network
segments and synchronizes the time among multiple devices. More specifically:
•
Device C’s local clock is to be used as a reference source, with the stratum level of 2.
•
Device C works in multicast server mode and sends out multicast messages from GigabitEthernet
0/1.
•
Device D and Device A work in multicast client mode and receive multicast messages through their
respective GigabitEthernet 0/1.