root@xx-xx-xx-xx:/var/lib/avi/backups# ls -l
total 18816
-rw-r--r-- 1 root root 4865034 Month DD 15:52 backup_Default-Scheduler_YYYYMMDD_HHMMSS.json
-rw-r--r-- 1 root root 4852392 Month DD 15:52 backup_Default-Scheduler_YYYYMMDD_HHMMSS.json
-rw-r--r-- 1 root root 4776040 Month DD 15:52 backup_Default-Scheduler_YYYYMMDD_HHMMSS.json
-rw-r--r-- 1 root root 4763800 Month DD 15:52 backup_Default-Scheduler_YYYYMMDD_HHMMSS.json
How to identify the NTP Issue
To identify the NTP out of sync, when you login to the controller from the browser and just after you authenticate, you will see a pop-up box on the top which will tell you if the NTP time sync is not correct.
# timedatectl
# systemctl status ntp.service
root@:/home/admin# ntpq -pn
remote refid st t when poll reach delay offset jitter
==============================================================================
xx.xx.xx.xx .INIT. 16 u - 1024 0 0.000 0.000 0.000
yy.yy.yy.yy .INIT. 16 u - 1024 0 0.000 0.000 0.000
>> Ping Test from Controller to NTP Server IP
root@:/home/admin# ping ntp.ubuntu.com
>> Check UDP Port 123 allow from Controller to NTP Server
echo "Test message" | nc -u ntp.ubuntu.com 123
If the UDP port is reachable and open, the message sent from the client will appear on the server's terminal.
If there’s no response, it might indicate that the port is blocked by a firewall, or the service isn't reachable. Note that UDP is connectionless, so you won't receive an acknowledgment like with TCP.