DescriptionHow NTP Sync works in the Meru Controller
ScopeKB ARTICLE TYPE: Configuration
RELATED PRODUCTS: controller
RELATED SOFTWARE VERSIONS: N/A
KEYWORDS: NTP, Sync, Manually
SolutionTo configure NTP server in the controller, go through SETUP CLI or IOS CLI.
The
first time the NTP server is configured you will be required to reboot
the controller to update/sync the time with the NTP server. Further
updates/sync to the NTP server from the controller is either manual or
automatic.
- Manually - On issuing 'ntp sync' the controller updates/syncs the time with the NTP server time.
- Automatically - For every 1st minute of the hour the controller updates/syncs the time with the NTP server time.
If
the updated time is +/- 35 minutes from the present time of the
controller, the controller will not update and will disable NTP
sync-ing.
To re-enable the NTP sync-ing process, the controller has to be rebooted.
NOTE:
If the time skew is less than +/- 35 minutes the controller will take proportionate time to sync with the new time.
For
example, if the present time in controller is 10:00:01 and if the NTP
server at next sync if it is at 10:10:01, the controller will do
sync-ing (since the skew time is < +/-35 minutes) but it will take
several minutes to do sync-ing. If the present time in controller is
10:00:01 and if the NTP server at next sync if it is at 10:34:01, the
controller will do sync-ing (since the skew time is still < +/-35
minutes) but now it will take several hours to do sync-ing. But across
reboots the sync-ing will be immediate. The sync-ing time will be
proportionately more when the skewed time is more when the controller is
up and running. The sync-ing cannot happen immediate because there are
many functions/modules running in the controller which are time
dependent.
