I was hoping that the NTP001 would offer a way to monitor if it has lost GPS Fix, but there appears to be nothing in it’s MIB to allow the monitoring of any of these parameters:
At the moment, the NTP001 does not provide any GPS or GNSS-related parameters through SNMP. The current SNMP MIB includes only general device and I/O information, and it does not expose GPS fix status, satellite count, or any other positioning data. Because of this, GPS synchronization status cannot be monitored via SNMP on the NTP001.
For more information regarding available parameters, you can refer this wiki article:
I’d read the docs already which is what prompted my question here, so I suppose my specific question is now how do we go about monitoring this? It’s critical for us that we know if we lost fix for some reason.
And to ask again is there anything in the roadmap that might include this feature or a way for us to formally request a feature here to try and get this included in the future, I think it’s a reasonable request to be able to monitor these parameters on a device that is specifically for NTP services.
When GPS fix is present, the NTP001’s clock is continuously disciplined by GNSS and the time offset stays small and stable.
If GPS fix is lost, discipline stops and the device enters holdover, relying only on its internal oscillator. That oscillator will drift, so the offset begins to grow steadily over time.
You’re not detecting GPS loss directly; you’re detecting the loss of GPS clock discipline, which is the operationally relevant failure.
Additionally, I will pass on your request to our R&D team to consider.
NTP001 does not have proper GNSS/GPS functionality.
It only synchronizes time over GNSS, but the overall approach is drastically different from how our other routers function. Our R&D team informed that it is not available for NTP001 due to deeper functional aspects.