Refer to the exhibit. A collaboration engineer is troubleshooting an issue with database replication on a Cisco UCM subscriber node. The engineer runs the utils NTP status command to check the NTP…

Question

Exhibit

Options

• AThe Cisco UCM subscriber node is synced at stratum 4, which can cause temporary issues.
• BThe Cisco UCM subscriber node polling interval is too high and must be reduced to avoid issues.
• CThe Cisco UCM subscriber node is synced correctly with NTP on the Cisco UCM publisher node.
• DThe reachability value of the Cisco UCM subscriber node indicates intermittent connectivity

• A
  4% (1)
• B
  4% (1)
• C
  93% (26)

Explanation

The utils ntp status command output shows the NTP synchronization status for the Cisco UCM subscriber node. Let's break down the key indicators: "synchronised to NTP server (80.81.128.1) at stratum 4" - This means the node is successfully synchronized with an NTP server that is at stratum 4, which is a valid sync level. Reachability value: 377 - This is an octal representation of successful reachability over the last 8 polling intervals (fully reachable). Delay, Offset, and Jitter values - The delay (0.865 ms), offset (0.607 ms), and jitter (0.666 ms) are all within an acceptable range, meaning time synchronization is stable. Since the node is correctly synchronized, we can conclude that NTP is not the cause of the database replication issue and is functioning properly.

No community discussion yet for this question.