You Are Here:
You are here: APPENDIX > TimeKeeper: Additional Information > TimeKeeper Event Notifications

TimeKeeper Event Notifications

SNMP, or Syslog Messages

Below are the specific messages that TimeKeeper will emit via SNMP, or syslog. Variable components of each message are replaced with the string VALUE below – depending on the specific value found, the message will vary here.

Each trap is followed by a brief explanation of the cause, and are grouped by function.

Client Sync Quality

  • Client sync quality error on PTP server VALUE, client VALUE, source VALUE: absolute value of offset VALUE > VALUE

VelaSync collects client sync accuracy information from clients - and will emit the above trap when one of the clients exceeds the server-specified accuracy threshold. (See the SYNCERRORTHRESHOLD configuration variable.)

These messages can be throttled by setting the “SYNC_ERROR_THRESHOLD_THROTTLE” variable.

When configured to send SNMP traps, this event will be delivered using the clientQualityTrap.

Invalid Sources

  1. Source VALUE: source appears to be valid again - re-enabling
  2. Source VALUE declared invalid/insecure
  3. Source VALUE declared invalid/insecure because of tickrate
  4. Source VALUE declared invalid/insecure because of offset
  5. Source VALUE declared invalid/insecure because of large time jump
  6. Source VALUE: TimeKeeper GPS/Oscillator detected moderate jamming
  7. Source VALUE: TimeKeeper GPS/Oscillator detected critical jamming level
  8. Source VALUE: TimeKeeper GPS device reports overheating, Temp: VALUEC/VALUEF
  9. Source VALUE: TimeKeeper GPS/Oscillator detected VALUE% jamming/noise

If TimeKeeper is crosschecking sources with the SOURCECHECK feature, some sources may be found to be invalid and rejected for a time. If a source has been rejected but is now found to be valid again, the first message will be sent. This is a clearing trap for the remainder of the list.

Similarly, TimeKeeper will send traps 2-5 above when a source is rejected. The second trap will be sent in every case, with one of the following traps 3-5 depending on the reason the source is being rejected.

The last four messages indicate there is an issue with the GPS device provided in TimeKeeper Grandmasters. These messages do not have clearing equivalents.

When configured to send SNMP traps, this event will be delivered using the sourceStateTrap.

Other Source-Related Messages

  1. Time source change VALUE -> VALUE
  2. Unable to find any valid time source.
  3. Previously unable to find any valid time source, now using source VALUE.

The first message above will be sent whenever TimeKeeper changes source for any reason - such as when one source stops providing timing data for more than 3 minutes. This will also occur in situations where the source TimeKeeper is tracking changes where it is getting time from, such as when an NTP server switches to another upstream source.

The second message will only be sent if TimeKeeper has failed over to the last configured source and even that has stopped responding. At this point, TimeKeeper is unable to track any sources and is driving the clock based on its best known clock rate.

The third message is a clearing trap for the second - if TimeKeeper previously lost all sources but one was found to be usable again, this message provides notification of the change.

When configured to send SNMP traps, this event will be delivered using the changedSourceTrap.

Sync Quality

  1. Sync quality error on source VALUE, absolute value of offset VALUE > VALUE
  2. Sync quality restored on source VALUE, absolute value of offset VALUE < VALUE

When a client has the SYNCERRORTHRESHOLD configuration option defined on a source, it will emit the first trap above whenever the sync offset exceeds that threshold.

When the sync comes back into the SYNCERRORTHRESHOLD range, the second trap above will be sent as a means of clearing state.

When configured to send SNMP traps, this event will be delivered using the sourceQualityTrap.

Grandmaster Issues

  1. Grandmaster unable to collect system chassis version information.*
  2. Grandmaster unable to collect system chassis information from pipe.*
  3. Grandmaster power supply 1 failure
  4. Grandmaster power supply 2 failure
  5. Inlet temperature failure

A “*” above indicates there may be further information provided in the data. These messages are specific to TimeKeeper Grandmasters, and indicate issues with the appliance.

Contact Spectracom Technical Support for assistance (see Technical Support). These messages do not have clearing equivalents.

When configured to send SNMP traps, this event will be delivered using the grandMasterFaultTrap.

Web Management IP Mismatch

  • Address VALUE specified for WEB_MANAGEMENT_IP but was not matched to a device. Ignoring parameter.

On startup, if the WEB_MANAGEMENT_IP parameter is used to limit access to the web tools, TimeKeeper makes sure that matches a configured interface. If it does not, this trap will be sent out and TimeKeeper will allow the web interface to be used on all interfaces so the issue can be resolved.

When configured to send SNMP traps, this event will be delivered using the startupFaultTrap.

Miscellaneous Issues at Startup

  1. Cannot open socket: VALUE
  2. Source VALUE: Cannot open socket: VALUE
  3. Source VALUE: Unable to prepare server socket descriptors for PTP
  4. Unable to prepare server socket descriptors for PTP
  5. Invalid MAJORTIME reference specified for source
  6. No time sources found. Make sure at least one time source is declared in /etc/timekeeper.conf
  7. Invalid CPU value specified: VALUE

This is a subset of the number of possible traps, sent on startup if TimeKeeper is unable to prepare internal resources as needed based on the current configuration, or if it is unable to start for other reasons, like an invalid configuration.

Regardless of the specific message, a startupFaultTrap indicates TimeKeeper is not operating normally and requires investigation — generally this is due to a misconfiguration. However, despite these messages thrown at startup, VelaSync will allow you to reconfigure TimeKeeper via the Web UI, in order to resolve the detected issue.

When configured to send SNMP traps, this event will be delivered using the startupFaultTrap.

Locating the MIB

For more details on the SNMP trap/Event types referenced below, refer to the MIB, which can be found in the Web UI under the Support tab.