F3726, F3211, F3174, R5135, R3816-HP Firewalls and UTM Devices System Management and Maintenance Configuration Guide-6PW100
124
2. Configure Firewall A:
# Specify the local clock as the reference source, with the stratum level 2.
<FirewallA> system-view
[FirewallA] ntp-service refclock-master 2
3. Configure Firewall B:
# Specify Firewall A as the NTP server of Firewall B.
<FirewallB> system-view
[FirewallB] ntp-service unicast-server 3.0.1.31
4. Configure Firewall C (after Firewall B is synchronized to Firewall A):
# Specify the local clock as the reference source, with the stratum level 1.
<FirewallC> system-view
[FirewallC] ntp-service refclock-master 1
# Configure Firewall B as a symmetric peer after local synchronization.
[FirewallC] ntp-service unicast-peer 3.0.1.32
In the step above, Firewall B and Firewall C are configured as symmetric peers, with Firewall C in
the symmetric-active mode and Firewall B in the symmetric-passive mode. Because the stratus level
of Firewall C is 1 while that of Firewall B is 3, Firewall B synchronizes to Firewall C.
# Display the NTP status of Firewall B after clock synchronization.
[FirewallB] display ntp-service status
Clock status: synchronized
Clock stratum: 2
Reference clock ID: 3.0.1.33
Nominal frequency: 64.0000 Hz
Actual frequency: 64.0000 Hz
Clock precision: 2^7
Clock offset: -21.1982 ms
Root delay: 15.00 ms
Root dispersion: 775.15 ms
Peer dispersion: 34.29 ms
Reference time: 15:22:47.083 UTC Sep 19 2005 (C6D95647.153F7CED)
The output shows that Firewall B has synchronized to Firewall C. The stratum level of Firewall B is
2, and that of Firewall C is 1.
# Display NTP session information for Firewall B, which shows that an association has been set up
between Firewall B and Firewall C.
[FirewallB] display ntp-service sessions
source reference stra reach poll now offset delay disper
**************************************************************************
[245] 3.0.1.31 127.127.1.0 2 15 64 24 10535.0 19.6 14.5
[1234] 3.0.1.33 LOCL 1 14 64 27 -77.0 16.0 14.8
note: 1 source(master),2 source(peer),3 selected,4 candidate,5 configured
Total associations : 2