Symptom
Time on the logical device is not in sync with the NTP server configured on the platform settings at the chassis.
This may manifest out of sync alerts on the FMC and lack of connection events on the FMC due to the time mismatch between the FTD instance and the FMC.
Conditions
To have a non-native instance on your security module, 1 instance is enough as long as it is not using all the cores available to the security module.
No impact on FTD running in native mode.
Workaround
If a time change is required (i.e., switching between two different NTP servers, toggling between manual and NTP server as the clock source on MIO/Supervisor), the best-effort attempt is to try to reload/reboot the container instance to see if the updated time can be picked up after the instance reload.
Further Problem Description
NTP synchronization works correctly on the chassis, it only fails on the instances.
