Use On-Premise NTP Source
By default, the gateway Virtual Appliance synchronizes its local time with the hypervisor host. For performance-related testing and production environments, using NTP with an on-premise time server is preferable.
gateway83
By default, the
CA API Gateway
Virtual Appliance synchronizes its local time with the hypervisor host. For performance-related testing and production environments, using NTP with an on-premise time server is preferable.To change the NTP source in the Virtual Appliance:
- Log in to the image as the root user.
- Run the following command to disable the sync to host functionality in the image:# vmware-toolbox-cmd timesync disable
- Configure your NTP time server on theCA API Gateway. For more information, see Option 1 - Configure Networking and System Time Settings.
- Restart the Virtual Appliance. The Gateway synchronizes with the NTP time servers after rebooting.
For any NTP configuration, CA Technologies strongly recommends synchronizing the Virtual Appliance with an on-premise time source, and not a pooled net source. The Gateway time should align closely to other internal resources and should be the same as other servers that send/receive from it. Ideally, you have a single internal server acting as a time source, with all other resources (including the Virtual Appliance) synchronizing with it.
For more information, see this KB article from VMware: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1006427
This KB article suggests using the kernel parameter “divider=10”. This is intended to help to reduce the timekeeping interrupts by 10X and thus minimize the CPU resources that are dedicated to timekeeping. However, this setting is
not
recommended for the Virtual Appliance, due to the time sensitivity of many of the operations supported by the CA API Gateway
.