You Are Here:
You are here: TIMEKEEPER > "Configuration" Tab > "TimeKeeper Configuration" Subtab

The "TimeKeeper Configuration" Subtab

This is the location where most of TimeKeeper's configuration settings are to be found.

The default TimeKeeper configuration will work well for many applications, i.e. the settings listed below need to be changed only if custom modifications have to be applied.

Application Settings

Serve NTP [checkbox; default = ON]

If ON, TimeKeeper will respond to NTP requests.

Send NTP followup packets [checkbox; default = OFF]

If enabled, TimeKeeper NTP server will also respond to NTP requests with a followup NTP packet. If VelaSync with TimeKeeper inside runs as a client, this allows processing of the followup to improve timing accuracy.

Serve NTP on interface [All, Eth0-4] (or, with option card: Eth0-6]

Determining the network interface that TimeKeeper should respond to NTP queries on. If TimeKeeper receives a request via that named interface, it will respond, but only on that interface. If set to "All", TimeKeeper listens and responds on all interfaces.

SNMP trap host [text field]

List of SNMP servers to send traps to.

In the field SNMP trap host, enter a host name or an IPv4 dotted notation address. TimeKeeper supports multiple SNMP trap destinations, to be entered in the following manner: host1, host2, host3.


An OID string to use for sending all SNMP trap messages. If left unspecified, TimeKeeper will deliver traps as specified in the TimeKeeper MIB.

In the field SNMP trap OID, enter the OID to which all traps will be emitted e.g., “”. Unless you need all traps sent to one OID, it is recommended you leave SNMPTRAPOID undefined in your configuration.

Avoid network interfaces

A comma separated list of network interface names. that TimeKeeper will not attempt to enable features on, e.g. timestamping capabilities.

Address for email notifications

List of email addresses (use comma to separate) to send alerts to [does currently not apply to TimeKeeper running on VelaSync].

Throttle to queue email

[Does currently not apply to TimeKeeper running on VelaSync]

A numeric value in seconds, to be used with email notification. If set, when an event occurs an initial email will be sent. Other emails that would be sent between then and the throttle timeout value will be queued.

Once the throttle timeout expires, any queued messages will be delivered as a single bundled email.

Set time on startup [checkbox]

If enabled, forcibly sets the time on startup regardless of offset, rather than trying to slew, for a faster sync on startup.

If disabled, TimeKeeper will slew in as long as the offset is less than ±5 seconds from the primary time source.

Correct a leap second with an immediate clock jump instead of slew [checkbox]

Per default, TimeKeeper introduces a leap second by "slewing". Alternatively, it is possible to introduce the leap second abruptly. For more information, see Leap Seconds.

Initial accuracy required before serving

Numeric value in seconds (i.e., 0.00001). If set, NTP/PTP/TIME protocols will not be served until the local clock accuracy meets this threshold.

Enable timing map [checkbox]

Enables the collection of information needed to build a map of the timing network.

Enable collecting detailed satellite signal strength information [checkbox]

Enables the collection of detailed GPS satellite angle/strength data.

Enable TK GPS device details [checkbox]

Enables the collection of detailed GPS states.

Enable sourcecheck [checkbox]

Will enable validity cross checks on timing sources. For more information, see Validating a Timing Source.

Bind TimeKeeper to CPU [Choose one, -1]

A numeric value indicating the CPU number that TimeKeeper should put all processes and threads on. A value of -1 will prevent TimeKeeper from applying affinities.

Enable management query [checkbox]

Enables the server to query PTP clients for their time sync quality data, which is stored on the server.

Enable management response [checkbox]

If enabled, allows the system to respond to incoming PTP management data requests.

Management query interval [15]

A numeric value in seconds that indicates how frequently to query PTP clients for their time sync quality data. Defaults to once every 15 seconds.

Sync error threshold throttle [5]

Numeric value in seconds that throttles the rate that TimeKeeper will send alerts about sync error threshold values being exceeded.

The default is 5, which will prevent TimeKeeper from sending alerts more often than every 5 seconds.

Enable web management [checkbox]

Enables the web management tools on the server.

Web management port [80]

A numeric value that indicates what port the web management should run on. If left unspecified, the web management tool will default to port 80.

Web management IP address [x.x.x.x]

By default, VelaSync will serve the Web UI (not the IPMI GUI) out any configured interface. You can restrict that if you want to by changing the Web management IP address option here: If you put an IP address in here, it will only serve the web out the interface with that IP address. If left blank VelaSync will serve the web out any configured interface.

Enable Solarflare UUID filtering [checkbox]

[Does not apply to VelaSync.]

Serve time (RFC 868) [checkbox]

If enabled, will cause TimeKeeper to respond to time requests (RFC 868) on all interfaces.

Days of TimeKeeper logs retained [7]

The default value is 7 days.

Verbose Settings

[All functions can be turned ON/OFF by means of a checkbox]

Enable verbose NMEA

Enables verbose logging of NMEA handling.

Enable verbose tcpdump

Enables tcpdump recording of PTP and NTP, kept alongside other TimeKeeper logs.

Enable verbose PPS

Enables verbose logging of PPS-based configurations.

Enable verbose server

Enables verbose logging of PTP behavior.

Enable verbose management

Enables verbose logging of management message behavior.

Enable verbose PTP

Enables verbose logging of PTP behavior.

Enable verbose NTP

Enables verbose logging of NTP behavior.

Enable verbose timestamps

Enables verbose logging of timestamping activity.

Enable verbose sourcecheck

Enables verbose logging of Sourcecheck-related activity.

Enable verbose BMC

Enables verbose logging of any BMC algorithm activity when handling PTP data.