NTP leap seconds file may expires on the Aria Operations for Networks appliances.

Products

• VCF Operations for Networks

Issue/Introduction

When the leap seconds file expires, you may observe the following symptoms:

• NTP sync failures, and the ntp show command displays "NOT-IN-SYNC."
• Running ntpq -cpe may show larger offset values or a leap indicator warning (where leap=11 signifies unsynchronized status).
• The syslog may contain entries such as: "leapsecond file expired" or "ntp server dropped leap not in sync."

Environment

VMware Aria Operations for Networks

VCF Operations for Networks

Resolution

To resolve this issue, follow the instructions below:

First, SSH into the affected platform or collector node using a support user account.

1. Download the ntp.leapseconds file attached to the Knowledge Base (KB) article.
2. Back up the current file: sudo cp /etc/ntp.leapseconds /etc/ntp.leapseconds.backup
3. Delete the existing file. Before deleting, you can check its current permissions: ls -lthr /etc/ntp.leapseconds
4. Then, delete the file: sudo rm -rf /etc/ntp.leapseconds
5. Upload the downloaded ntp.leapseconds file using WinSCP and copy it to /etc.
6. Set the correct permissions for the new file: sudo chmod 644 /etc/ntp.leapseconds
7. Restart the ntpsec service on the affected node: sudo systemctl restart ntpsec
8. Switch to consoleuser mode: sudo su consoleuser
9. Sync the Network Time Protocol (NTP) by running: ntp sync

Additional Information

Note: This is one potential reason why the NTP is not in sync; however, if the issue symptoms do not match, please review the following KB article for further troubleshooting on this NTP-related issue.

https://knowledge.broadcom.com/external/article?articleNumber=340847