H3C SecPath F1800-A Operation Manual page 144

Operation Manual - System Management
H3C SecPath F1800-A Firewall
# Configure SecPath 4 as a multicast client.
<SecPath4> system-view
[SecPath4] interface Ethernet 1/0/0
[SecPath4-Ethernet1/0/0] ntp-service multicast-client
3) Configuring SecPath 1
# Configure SecPath 1 as a multicast client.
<SecPath1> system-view
[SecPath1] interface ethernet 1/0/0
[SecPath1-Ethernet1/0/0] ntp-service multicast-client
After the above configuration, SecPath 3 sends multicast messages through the
interface Ethernet 1/0/0, and SecPath 4 and SecPath 1 monitor multicast messages
from respective interface Ethernet 1/0/0. Since SecPath 1 and SecPath 3 are not on
the same network segment, SecPath 1 does not receive the multicast messages from
SecPath 3. SecPath 4 can receive the multicast messages from SecPath 3, and then
it is synchronized to SecPath 3.
After the synchronization, the status of SecPath 4 is shown below.
[SecPath4] display ntp-service status
clock status: synchronized
clock stratum: 3
reference clock ID: 3.0.1.31
nominal frequency: 250.0000 Hz
actual frequency: 249.9992 Hz
clock precision: 2^19
clock offset: 198.7425 ms
root delay: 27.47 ms
root dispersion: 208.39 ms
peer dispersion: 9.63 ms
reference time: 17:03:32.022 UTC Thu Sep 6 2001 (BF422AE4.05AEA86C)
In this way, SecPath 4 has been synchronized to SecPath 3, and its stratum is 3.
You can see SecPath 4 has been connected with SecPath 3 after viewing the session
status of SecPath 4.
[SecPath4] display ntp-service sessions
source
********************************************************************
[12345]127.127.7.1
note: 1 source(master),2 source(peer),3 selected,4 candidate,5 configured
refid st now
LOCAL(0) 3 1
2-51
Chapter 3 NTP Configuration
poll reach delay offset
64 377 26.1
dis
199.53 9.7