Amer Networks E5Web GUI - Manual (Page 233)

Example 3.38. Manually Triggering a Time Synchronization
Time synchronization can be triggered from the CLI. The output below shows a typical response.
Command-Line Interface
Device:/> time -sync
Attempting to synchronize system time...
Server time: 2008-02-27 12:21:52 (UTC+00:00)
Local time:
2008-02-27 12:24:30 (UTC+00:00) (diff: 158)
Local time successfully changed to server time.
Maximum Time Adjustment
To avoid situations where a faulty time server causes the clock to be updated with an extremely
inaccurate time, a Maximum Adjustment value (in seconds) can be set. If the difference between
the current cOS Core time and the time received from a time server is greater than this maximum
adjustment value, then the time server response will be discarded.
For example, assume that the maximum adjustment value is set to 60 seconds and the current
cOS Core time is 16:42:35. If a time server responds with a time of 16:43:38 then the difference is
63 seconds. This is greater than the maximum adjustment value so no update occurs for this
response.
Example 3.39. Modifying the Maximum Adjustment Value
Command-Line Interface
Device:/> set DateTime TimeSyncMaxAdjust=40000
InControl
Follow the same steps used for the Web Interface below.
Web Interface
1. Go to: System > Device > Date and Time
2. For the setting Maximum time drift that a server is allowed to adjust, enter the
maximum time difference in seconds that an external server is allowed to adjust for. There
may be a valid reason why there is a significant difference such as an incorrect cOS Core
configuration.
3. Click OK
Sometimes it might be necessary to override the maximum adjustment. For example, if time
synchronization has just been enabled and the initial time difference is greater than the
maximum adjust value. It is then possible to manually force a synchronization and disregard the
maximum adjustment parameter.
Chapter 3: Fundamentals
233