Network requirements – H3C Technologies H3C SR8800 User Manual

Page 91

Advertising
background image

79

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, Router D has been synchronized to Router C and the clock stratum level of Router

D is 4, while that of Router C is 3.
# View the NTP session information of Router D, which shows that an association has been set up
between Router D and Router C.

[RouterD-GigabitEthernet3/1/10] display ntp-service sessions

source reference

stra reach poll now offset delay disper

**************************************************************************

[1234] 3.0.1.31 127.127.1.0 3 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 MPLS VPN time synchronization in client/server

mode

Network requirements

As shown in

Figure 31

, two VPNs are present on PE 1 and PE 2: VPN 1 and VPN 2. CE 1 and CE 3 are

routers in VPN 1. To synchronize the time between CE 1 and CE 3 in VPN 1, perform the following
configurations:

CE 1’s local clock is to be used as a reference source, with the stratum level of 1.

CE 3 is synchronized to CE 1 in the client/server mode.

NOTE:

At present, MPLS L3VPN time synchronization can be implemented only in the unicast mode (client/server
mode or symmetric peers mode), but not in the multicast or broadcast mode.

Advertising