Network requirements – H3C Technologies H3C MSR 50 User Manual

Page 61

Advertising
background image

[RouterB-Ethernet1/1] igmp static-group 224.0.1.1

[RouterB-Ethernet1/1] quit

[RouterB] interface ethernet 1/2

[RouterB-Ethernet1/2] pim dm

5.

Configure Router A:

<RouterA> system-view

[RouterA] interface ethernet 1/1

# Configure Router A to operate in multicast client mode and receive multicast messages on
Ethernet 1/1.

[RouterA-Ethernet1/1] ntp-service multicast-client

# Display the NTP status of Router A after clock synchronization.

[RouterA-Ethernet1/1] display ntp-service status

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: 40.00 ms

Root dispersion: 10.83 ms

Peer dispersion: 34.30 ms

Reference time: 16:02:49.713 UTC Sep 19 2005 (C6D95F6F.B6872B02)

The output shows that Router A has synchronized to Router C. The stratum level of Router A is 3,
and that of Router C is 2.
# Display NTP session information for Router A, which shows that an association has been set up
between Router A and Router C.

[RouterA-Ethernet1/1] display ntp-service sessions

source reference

stra reach poll now offset delay disper

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

[1234] 3.0.1.31 127.127.1.0 2 255 64 26 -16.0 40.0 16.6

note: 1 source(master),2 source(peer),3 selected,4 candidate,5 configured

Total associations : 1

For more information about how to configuration IGMP and PIM, see IP Multicast Configuration Guide.

Configuration example for NTP client/server mode with

authentication

Network requirements

As shown in

Figure 21

, perform the following configurations to synchronize the time between Device B

and Device A and ensure network security.

The local clock of Device A is to be configured as a reference source, with the stratum level 2.

Device B operates in client mode and Device A is to be used as the NTP server of Device B, with
Device B as the client.

NTP authentication is to be enabled on both Device A and Device B.

48

Advertising