Network requirements – H3C Technologies H3C MSR 5600 User Manual
Page 113
100
Clock status: synchronized
Clock stratum: 3
System peer: 10.1.1.1
Local mode: client
Reference clock ID: 10.1.1.1
Leap indicator: 00
Clock jitter: 0.005096 s
Stability: 0.000 pps
Clock precision: 2^-10
Root delay: 0.00655 ms
Root dispersion: 1.15869 ms
Reference time: d0c62687.ab1bba7d Wed, Dec 29 2010 21:28:39.668
[PE2] display ntp-service sessions
source reference stra reach poll now offset delay disper
********************************************************************************
[1245]10.1.1.1 127.127.1.0 2 1 64 519 -0.0 0.0065 0.0
Notes: 1 source(master),2 source(peer),3 selected,4 candidate,5 configured.
Total sessions : 1
[PE2] display ntp-service trace
Server 127.0.0.1
Stratum 3 , jitter 0.000, synch distance 796.50.
Server 10.1.1.1
Stratum 2 , jitter 939.00, synch distance 0.0000.
RefID 127.127.1.0
Configuration example for MPLS VPN time
synchronization in symmetric active/passive mode
Network requirements
As shown in
, two VPNs are present on PE 1 and PE 2: VPN 1 and VPN 2. CE 1 and CE 3
belong to VPN 1. To synchronize the time between PE 1 and CE 1 in VPN 1, configure CE 1's local clock
as a reference source, with the stratum level 2, configure CE 1 to operate in symmetric active mode, and
specify VPN 1 as the target VPN.