Vyatta NOS documentation

Learn how to install, configure, and operate Vyatta Network Operating System (Vyatta NOS), which helps to drive our virtual networking and physical platforms portfolio.

GNSS events

The GNSS (Global Navigation Satellite System) can be in an unexpected state, or be in a temporary state for too long. Therefore, when such issues are detected, an SNMP GNSS failure trap is sent, with a reason for the failure. When the failure event ends, an SNMP GNSS recovery trap is sent. They are also resent periodically when in a failure condition.

The GnssFailure trap is sent for any of the GNSS failure conditions. The failure reason message indicates the cause for the failure. While in a failure condition the trap is sent every 60 minutes. When leaving the failure condition, the GnssRecovery trap is sent.

Note:

Timings for the traps sent are approximate, as polling for GNSS status is done about every 10 to 15 seconds.

The following table describes the possible reasons for GNSS failures. These are in the order that is reported if more than one issue occurs.

Failure reason

Text of reason sent in trap

The GNSS module has not been detected.

Module not detected

The GNSS module has been disabled by the administrator.

Module disabled by admin

The GNSS module has reported a failure.

Hardware failure

The antenna of the GNSS module has failed.

Antenna failure

The GNSS module has not been able to enter the tracking state for at least the time specified by the Holdover time limit configuration value.

Holdover exceeded configured duration

The GNSS module has taken longer than the time specified by the Tracking time limit configuration value to enter the tracking state for the satellites.

Too long in entering tracking state

This patch adds the following configuration commands:

set service gnss instance [number] tracking-time-limit [seconds]

number is the instance number of the GNSS receiver in the system. Most systems have at most one GNSS receiver with an instance number of 0.

seconds is how long to wait, in seconds, until a GNSS failure trap indicates that it has taken too long to enter the tracking state. This value must be as follows:

  • Has a minimum value of 10
  • Is a multiple of 10
  • Less than the holdover-time-limit configuration variable
  • Defaults to a value of 900 (15 minutes)

If the tracking state has not transitioned to tracking by the time specified in this configuration value, then a trap is sent with the reason Too long in entering tracking state.

set service gnss instance [number] holdover-time-limit [seconds]

number is the instance number of the GNSS receiver in the system. Most systems have at most one GNSS receiver with an instance number of 0.

seconds is how long to wait, in seconds, until a GNSS failure trap indicates that the holdover time has been exceeded. This value must be as follows:

  • Has a minimum value of 20
  • Is a multiple of 10
  • More than the tracking-time-limit configuration variable
  • Defaults to a value of 7200 (2 hours)

If the tracking state has not transitioned to tracking by the time given in this configuration value, then a trap is sent with the reason Holdover exceeded configured duration.