R3721-F3210-F3171-HP High-End Firewalls System Management and Maintenance Configuration Guide-6PW101
115
[FirewallB-GigabitEthernet0/2] pim dm
5. Configure Firewall A:
<FirewallA> system-view
[FirewallA] interface gigabitethernet 0/1
# Configure Firewall A to operate in multicast client mode and receive multicast messages on
GigabitEthernet 0/1.
[FirewallA-GigabitEthernet0/1] ntp-service multicast-client
# View 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: 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)
As shown above, Firewall A has been synchronized to Firewall C and the clock stratum level of
Firewall A is 3, while that of Firewall C is 2.
# View the NTP session information of 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 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 IGMP and PIM configuration, see Network Management
Configuration Guide.
Configuring the NTP client/server mode with authentication
In this configuration example, either Device A or Device B is the firewall.
Network requirements
As shown in Figure 54, 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 of 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.