F3726, F3211, F3174, R5135, R3816-HP Firewalls and UTM Devices System Management and Maintenance Configuration Guide-6PW100

126
<FirewallB> system-view
[FirewallB] interface gigabitethernet 0/1
[FirewallB-GigabitEthernet0/1] ntp-service broadcast-client
Firewall A and Firewall B get synchronized upon receiving a broadcast message from Firewall C.
# Take Firewall A as an example. Display the NTP status of Firewall A after clock synchronization.
[FirewallA-GigabitEthernet0/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: 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)
The output shows that Firewall A has synchronized to Firewall C. The stratum level of Firewall A is
3, and that of Firewall C is 2.
# Display NTP session information for Firewall A, which shows that an association has been set up
between Firewall A and Firewall C.
[FirewallA-GigabitEthernet0/1] display ntp-service sessions
source reference stra reach poll now offset delay disper
**************************************************************************
[1234] 3.0.1.31 127.127.1.0 2 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
252BConfiguring NTP multicast mode
430BNetwork requirements
As shown in 845HFigure 55, Firewall B functions as the NTP server for multiple devices on different network
segments and synchronizes the time among multiple devices.
• Firewall B's local clock is to be used as a reference source, with the stratum level 2.
• Firewall B operates in multicast server mode and sends multicast messages from GigabitEthernet
0/1.
• Firewall A and Firewall C operate in multicast client mode and receive multicast messages through
their respective GigabitEthernet 0/1.