settings ntp

The settings ntp command manages the clock of the device: it determines which time servers the clock will be taken from, how many sources have to agree for a correction to be accepted, how large a correction will be allowed at most and the time zone of the device.

Why the clock is important

The certificate validity check, the ordering of the log records, the session durations and the scheduled jobs depend on the device clock. The clock having drifted affects all of these.

Command Summary

TR7 WEB-CLI · settings ntp

# Tab after the command

admin@TR7LBWAF01> settings ntp

show update

 

admin@TR7LBWAF01> settings ntp show # show the settings

admin@TR7LBWAF01> settings ntp update … # change

admin@TR7LBWAF01>  

Fields

This resource is a single setting: no identifier is written, update is run directly and only the fields to be changed are given.

Field	What it does	What is written after it
--ntpServer	Determines the time servers the clock will be taken from	The server name or address. More than one server is written inside a single value separated by spaces; when more than one server is given, the value is put inside double quotation marks
--minSources	Determines how many sources have to agree for the clock to be corrected	An integer between 1 and 8 (the default is 1)
--maxClockChange.val	Limits the largest clock correction that a single measurement can request	A number. When it is left empty, the size of the correction is not limited
--maxClockChange.unit	Selects the unit of that limit	s (the default) · m · h; the total duration cannot be smaller than 30 seconds or larger than 24 hours
--timezone	Determines the time zone of the device	A time zone value, for example Europe/Istanbul. Tab opens the list; there are 476 values in the set

Examples

TR7 WEB-CLI · the clock setting

# a single server and the time zone

admin@TR7LBWAF01> settings ntp update --ntpServer ntp.kurum.com.tr --timezone Europe/Istanbul

 

# three independent sources, the clock should not change unless two of them agree

admin@TR7LBWAF01> settings ntp update --ntpServer "ntp1.kurum.com.tr ntp2.kurum.com.tr ntp3.kurum.com.tr" \

--minSources 2

 

# allow a correction of at most 10 minutes at one time

admin@TR7LBWAF01> settings ntp update --maxClockChange.val 10 --maxClockChange.unit m

admin@TR7LBWAF01> settings ntp show

admin@TR7LBWAF01>  

Things to Know

• The agreement count is not raised with a single server. The default of --minSources is 1; raising the value is meaningful only while more than one source independent of each other is defined. If the value is raised in a setup with a single server, the clock is never synchronized.
• The correction limit protects against a broken source. When --maxClockChange is given, a source that reports the wrong time cannot shift the clock more than the limit. When the field is left empty, there is no such limit.
• More than one server is written in a single field. The servers are separated by spaces and the value is put inside quotation marks as a whole; each of them opens into its own line in the configuration produced.
• The time zone set is wide. The value is a standard time zone name in the Region/City format; the Tab completion narrows the list down by filtering it.
• The clock affects the certificate and log jobs. A time zone change is reflected in the stamps of the log records and in the running times of the scheduled jobs.