H3C Technologies H3C MSR 50 - Manual (Page 67)

Configuration procedure
Before you perform the following configuration, be sure you have completed MPLS VPN-related
configurations and make sure of the reachability between CE 1 and PE 1, between PE 1 and PE 2, and
between PE 2 and CE 3. For information about configuring MPLS VPN, see MPLS Configuration Guide.
Figure 23 . (Details not shown.) 1. Set the IP address for each interface as shown in
2. Configure CE 1:
# Specify the local clock as the reference source, with the stratum level 1.
system-view
[CE1] ntp-service refclock-master 1
3. Configure PE 2:
# Specify CE 1 as the NTP server for VPN 1.
system-view
[PE2] ntp-service unicast-server 10.1.1.1
# Display the NTP session information and status information on PE 2 a certain period of time later.
The information should show that PE 2 has been synchronized to CE 1, with the stratum level 2.
[PE2] display ntp-service status
Clock status: synchronized
Clock stratum: 2
Reference clock ID: 10.1.1.1
Nominal frequency: 63.9100 Hz
Actual frequency: 63.9100 Hz
Clock precision: 2^7
Clock offset: 0.0000 ms
Root delay: 47.00 ms
Root dispersion: 0.18 ms
Peer dispersion: 34.29 ms
Reference time: 02:36:23.119 UTC Jan 1 2001(BDFA6BA7.1E76C8B4)
[PE2] display ntp-service sessions
source reference stra reach poll now offset delay disper
**************************************************************************
[12345]10.1.1.1 LOCL 1 7 64 15 0.0 47.0 7.8
note: 1 source(master),2 source(peer),3 selected,4 candidate,5 configured
Total associations : 1
[PE2] display ntp-service trace
server 127.0.0.1,stratum 2, offset -0.013500, synch distance 0.03154
server 10.1.1.1,stratum 1, offset -0.506500, synch distance 0.03429
refid 127.127.1.0
Configuration example for MPLS VPN time synchronization in
symmetric peers mode
Network requirements
As shown in Figure 23 , 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
54