NTP sync failure(s) for Cisco Nexus




Indeni will alert if one or more of the configured NTP servers is not syncing correctly.

Remediation Steps

Review the cause for the NTP sync not working.
Examples of common NTP issues are the next:
• NTP packets are not received.
• NTP packets are received, but are not processed by the NTP process on the NX-OS.
• NTP packets are processed, but erroneous factors or packet data causes the loss of synchronization.
• NTP clock-period is manually set.

1. Check the current ntp status by running the NX-OS command "show ntp peer-status".
2. If the "show ntp peer-status" command does not provide any output then try to ping the NTP servers. The ntp source and vrf may need to be provided as command options.
3. Check the routing table with the "show ip route vrf all" NX-OS command to verify that there is routing to the NTP servers.
4. Check that the UDP 123 port used by NTP service is permitted to the network.
5. Execute the "show run ntp" NX-OS command to review the NTP current configuration.
6. For more information review the next Nexus NTP troubleshooting guide: https://www.cisco.com/c/en/us/support/docs/ip/network-time-protocol-ntp/116161-trouble-ntp-00.html

How does this work?

This script logs into the Cisco Nexus switch using SSH and retrieves the output of the "show ntp peer-status" command. The output includes the state information for all configured NTP servers.

Why is this important?

Monitor NTP server state. NTP servers are used to sync the time across all hosts and network devices. This is critical for things such as event correlation and logging.

Without Indeni how would you find this?

It is not possible to poll this data through SNMP or Syslog.

View Source Code