This article describes how to mitigate the need of NTP server on VOS.
Following are different solutions:
Solution-1:
If user devices are connected to internet via VOS, configure reliable NTP servers such as time.google.com, time.apple.com, time.facebook.com, time.windows.com, time.aws.com, pool.ntp.org etc. Do not worry about these public NTP server scalability, they scale massively. Refer to the below link for documentation on the configuration
Solution-2:
If VOS has connectivity to NTP server either in public or private network and devices connected via VOS does not have access to NTP server, configure DNAT on VOS to forward NTP packets to NTP server. Devices connected VOS can point to DNAT address configured on VOS and VOS will forward the packets to NTP server.
Solution-3:
If user devices are not connected to internet but want to to use central NTP server in private network and provide internet access only to Central NTP server without using NAT on VOS, spin up Linux or your favorite OS supporting NTP server and configure NTP server on Linux and point all user devices to internal NTP server.
Solution-4:
If bringing up Linux or third party NTP server is not possible, make use of Versa uCPE solution to spin up linux VM within Versa platform, configure NTP in Linux VM and point user devices to this NTP server.
Please refer our documentation for uCPE at - https://docs.versa-networks.com/Secure_SD-WAN/01_Configuration_from_Director/Common_Configuration/Configure_uCPE_on_a_VOS_Device