ENDRUNTECHNOLOGIES-MIB

All MIBs › ENDRUNTECHNOLOGIES-MIB

Organization: EndRun Technologies LLC

Last Updated: 2002-08-19

Category: Protocol: SNTP/NTP, Technology: Time Synchronization, Vendor: EndRun Technologies

Description: EndRun Technologies MIB for managing EndRun GPS/timing appliances including time synchronization status and reference source quality.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is ENDRUNTECHNOLOGIES-MIB?

ENDRUNTECHNOLOGIES-MIB is the enterprise MIB for EndRun Technologies' GPS and CDMA-based network time server appliances, covering NTP service statistics and time-reference quality. It exposes NTP traffic counters (received, transmitted, ignored, dropped packets, authentication failures), synchronization quality metrics (time figure of merit, leap indicator bits, stratum, sync source), and reference-source health such as CDMA fault status. This is squarely a software/hardware status monitoring MIB: administrators use it to verify the appliance's NTP service is healthy via the packet and auth-failure counters, confirm the time reference is trustworthy via stratum and sync source, and detect reference hardware faults via cdmaFaultStatus. It builds on standard NTP concepts such as stratum and leap indicator but is a self-contained enterprise MIB not formally dependent on another SNMP MIB. It is typically deployed on EndRun GPS/CDMA network time servers providing authoritative NTP time to enterprise or carrier networks. Engineers can download the ENDRUNTECHNOLOGIES-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in ENDRUNTECHNOLOGIES-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

EndRun Technologies GPS/CDMA network time server
NTP appliance

Monitoring Examples

An admin could poll cntpStratum and cntpSyncSource together with cntpTimeFigureOfMerit to confirm the appliance is locked to a high-quality time reference, and watch cntpOffsetToCDMAReference for drift. Rising cntpDroppedPkts, cntpIgnoredPkts, or cntpAuthFail counts would indicate misbehaving NTP clients or peers degrading service. cdmaFaultStatus would flag a hardware fault in the CDMA reference receiver, prompting a check of antenna or signal issues.

What Can Be Monitored

NTP packet counters (rx/tx/dropped/ignored)
authentication failures
time figure of merit
sync source
stratum
offset to CDMA reference
CDMA fault status

Imported Objects

From SNMPv2-SMI

Counter32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
enterprises

From SNMPv2-TC

DisplayString

How to Use in IPNetwork Monitor

Example using cntpRxPkts OID:

Select an EndRun Technologies GPS/CDMA network time server as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type cntpRxPkts into the Find box to locate it in the OID tree, then select it and click OK. It reports the total number of NTP request packets received by the NTP daemon. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
endRunTechnologiesMIB	1.3.6.1.4.1.13827
endRunTechnologies	1.3.6.1.4.1.13827.0			EndRun Technologies Enterprise MIB
praecisCntp	1.3.6.1.4.1.13827.1
cntp	1.3.6.1.4.1.13827.1.0
cntptrap	1.3.6.1.4.1.13827.1.0.0
NTF cntpTrapLeapIndBitsChange	1.3.6.1.4.1.13827.1.0.0.1			A cntpTrapNTPLeapIndBitsChange trap signifies that the value of the leap indicator bits contained in the NTP reply packets sent by the time server has changed. The current value of these bits is contained in the included cntpLeapIndBits. The decimal value of these bits ranges from 0 to 3: 0 is the no fault, no leap warning condition 1 is the no fault, leap second insertion warning condition 2 is the no fault, leap second deletion warning condition 3 is the unsynchronized, alarm condition
NTF cntpTrapStratumChange	1.3.6.1.4.1.13827.1.0.0.2			A cntpTrapStratumChange trap signifies that the value of the stratum field contained in the NTP reply packets sent by the time server has changed. The current value is contained in the included variable, cntpStratum. The decimal value of this field ranges from 1 to 16: 1 is the synchronized, actively locked to the reference UTC source stratum 11 is the synchronized, but flywheeling on the local real time clock stratum 16 is the unsynchronized stratum level
C32 cntpRxPktsEx	1.3.6.1.4.1.13827.1.0.1	Counter32	read-only	Total number of NTP request packets received by the NTP daemon.
C32 cntpTxPkts	1.3.6.1.4.1.13827.1.0.2	Counter32	read-only	Total number of NTP reply packets transmitted by the NTP daemon.
C32 cntpIgnoredPkts	1.3.6.1.4.1.13827.1.0.3	Counter32	read-only	Total number of NTP request packets ignored by the NTP daemon.
C32 cntpDroppedPkts	1.3.6.1.4.1.13827.1.0.4	Counter32	read-only	Total number of NTP request packets dropped by the NTP daemon.
C32 cntpAuthFail	1.3.6.1.4.1.13827.1.0.5	Counter32	read-only	Total number of authentication failures detected by the NTP daemon.
INT cntpTimeFigureOfMerit	1.3.6.1.4.1.13827.1.0.6	INTEGER	read-only	The Time Figure of Merit (TFOM) value ranges from 4 to 9 and indicates the current estimate of the worst case time error. It is a logarithmic scale, with each increment indicating a tenfold increase in the worst case time error boundaries. The scale is referenced to a worst case time error of 100 picoseconds, equivalent to a TFOM of zero. During normal locked operation with CDMA the TFOM is 6 and implies a worst case time error of 100 microseconds. During periods of signal loss, the CDMA sub-system will compute an extrapolated worst case time error. One hour after the worst case time error has reached the value equivalent to a TFOM of 9, the NTP server will cease to send stratum 1 reply packets and an Alarm LED will be energized.
INT cntpLeapIndBits	1.3.6.1.4.1.13827.1.0.7	INTEGER	read-only	This is a status code indicating: normal operation, a leap second to be inserted in the last minute of the current day, a leap second to be deleted in the last second of the day or an alarm condition indicating loss of timing synchronization. The leap indicator field of NTP reply packets sent from this server is set to cntpLeapIndBits.
STR cntpSyncSource	1.3.6.1.4.1.13827.1.0.8	DisplayString	read-only	This is an ASCII string identifying the synchronization source for this NTP server. It is one of CDMA, CPU or NONE. If it is NONE, then the server is not synchronized, has its Leap Indicator Bits in the Alarm state and is running at Stratum 16. If it is CPU, then the server is free running on its NTP disciplined CPU clock at Stratum 11. Check the Stratum, Leap Indicator Bits and Time Figure of Merit for further information. NTP reply packets from this server will have the reference identifier field set to cntpSyncSource if it is CDMA. Otherwise it will be set to either 127.127.1.0 (CPU) or 0.0.0.0 (NONE).
STR cntpOffsetToCDMAReference	1.3.6.1.4.1.13827.1.0.9	DisplayString	read-only	This is an ASCII string containing the floating value of the current offset in units of seconds of the NTP server CPU clock to the CDMA reference time. Positive values imply that the NTP server clock is ahead of the CDMA reference time.
INT cntpStratum	1.3.6.1.4.1.13827.1.0.10	INTEGER	read-only	This is an integer showing the current stratum level being reported by the NTP daemon in its reply packets to clients. If it is 1, then the server is fully synchronized and delivering Stratum 1 accuracy. If it is 16, then the server is unambiguously unsynchronized. If it is 11, and the previous stratum value was 1, then the server is flywheeling on the local CPU clock. However, if the previous stratum value was 16, then the server has synchronized to its CPU Real Time Clock. NTP clients on the network should be configured to not use the time from this server if the stratum is not 1.
STR cntpVersion	1.3.6.1.4.1.13827.1.0.11	DisplayString	read-only	This is an ASCII string showing the NTP server firmware version.
cdma	1.3.6.1.4.1.13827.1.1
cdmatrap	1.3.6.1.4.1.13827.1.1.0
NTF cdmaTrapFaultStatusChange	1.3.6.1.4.1.13827.1.1.0.1			A cdmaTrapFaultStatusChange trap signifies that the value of the fault status word reported by the CDMA sub-system has changed. The current value is contained in the included cdmaFaultStatus.
BIT cdmaFaultStatus	1.3.6.1.4.1.13827.1.1.1	Bits	read-only	This is a bit string contained in one character representing the least significant two nibbles of the CDMA fault status word. Unfortunately, SNMP numbers the bits in the reverse order, so that the enumerated values are backwards from the description contained in the User's Manual for the fault status field returned by the cdmastat command. Each bit indicates a fault when set. Currently defined fault states encoded in this value: Bit 7: DAC controlling the TCXO is near the high or low limit. Bit 6: Time Figure of Merit has been 9 (unsynchronized) for 1 hour. Bit 5: Field Programmable Gate Array (FPGA) did not configure properly. Bit 4: FLASH memory had a write fault. Bit 3: Local Oscillator PLL fault. Bit 2: Local Oscillator PLL failed. Bit 1: NTP daemon is not polling the CDMA reference clock. Bit 0: Not Used.
INT cdmaTimeFigureOfMerit	1.3.6.1.4.1.13827.1.1.2	INTEGER	read-only	The Time Figure of Merit (TFOM) value ranges from 6 to 9 and indicates the current estimate of the worst case time error. It is a logarithmic scale, with each increment indicating a tenfold increase in the worst case time error boundaries. The scale is referenced to a worst case time error of 100 picoseconds, equivalent to a TFOM of zero. During normal locked operation the TFOM is 6 and implies a worst case time error of 100 microseconds. During periods of signal loss, the CDMA sub-system will compute an extrapolated worst case time error. One hour after the worst case time error has reached the value equivalent to a TFOM of 9, the NTP server will cease to send stratum 1 reply packets and an Alarm LED will be energized.
INT cdmaSigProcState	1.3.6.1.4.1.13827.1.1.3	INTEGER	read-only	Current CDMA signal processor state. One of 0, 1, 2, 4 or 8, with 0 indicating the acquisition state and 8 the fully locked on state.
INT cdmaChannel	1.3.6.1.4.1.13827.1.1.4	INTEGER	read-only	Current CDMA frequency band and channel being used. Channels 0-3 are the North American cellular channels. Channels 4-7 are the South Korean cellular channels.
INT cdmaPNO	1.3.6.1.4.1.13827.1.1.5	INTEGER	read-only	Current Pseudo Noise Offset of the base station being tracked. The value ranges from 0 to 511 and is in units of 64 Pseudo Noise Code chips. This offset serves as a base station identifier that is analogous to the Pseudo Random Noise (PRN) codes used by the individual satellites in the GPS system.
INT cdmaAGC	1.3.6.1.4.1.13827.1.1.6	INTEGER	read-only	Current 8 bit, Automatic Gain Control (AGC) DAC value. Typical values are around 200, but proximity to the base station, type of building construction and orientation within the building have a strong influence on this value. More positive values have the effect of increasing the RF gain.
INT cdmaVCDAC	1.3.6.1.4.1.13827.1.1.7	INTEGER	read-only	Current 16 bit, Voltage Controlled TCXO DAC value. Typical range is 20000 to 40000, where more positive numbers have the effect of raising the TCXO frequency.
STR cdmaCarrierToNoiseRatio	1.3.6.1.4.1.13827.1.1.8	DisplayString	read-only	ASCII string representing the current received CDMA signal carrier-to-noise ratio, a unitless quantity. Numbers less than 2.5 indicate a very weak signal condition.
STR cdmaFrameErrorRate	1.3.6.1.4.1.13827.1.1.9	DisplayString	read-only	ASCII string representing the current sync channel message error rate, a number ranging from 0.000 to 1.000. It indicates the proportion of messages received that fail the Cyclical Redundancy Check.
STR cdmaLeapMode	1.3.6.1.4.1.13827.1.1.10	DisplayString	read-only	ASCII string showing the current leap second mode of operation for the CDMA sub-system. It is either AUTO or USER. If the mode is USER, then the current and future values of the UTC to GPS leap second offset is also included.
INT cdmaCurrentLeapSeconds	1.3.6.1.4.1.13827.1.1.11	INTEGER	read-only	This value is the current difference in seconds between GPS time and UTC time. GPS time is ahead of UTC time by this amount.
INT cdmaFutureLeapSeconds	1.3.6.1.4.1.13827.1.1.12	INTEGER	read-only	This value is the future difference in seconds between GPS time and UTC time. Leap seconds may be inserted or deleted from the UTC timescale twice during the year: Dec 31 and June 30 at UTC midnight. If this value is the same as cdmaCurrentLeapSeconds, then no leap second insertion or deletion will occur at the next possible time. If it is different, then the change will take affect at the next possible time. GPS time will be ahead of UTC time by this amount.
STR cdmaVersion	1.3.6.1.4.1.13827.1.1.13	DisplayString	read-only	ASCII string showing the CDMA sub-system firmware and FPGA versions.
praecisGntp	1.3.6.1.4.1.13827.2
gntp	1.3.6.1.4.1.13827.2.0
gntptrap	1.3.6.1.4.1.13827.2.0.0
NTF gntpTrapLeapIndBitsChange	1.3.6.1.4.1.13827.2.0.0.1			A gntpTrapNTPLeapIndBitsChange trap signifies that the value of the leap indicator bits contained in the NTP reply packets sent by the time server has changed. The current value of these bits is contained in the included gntpLeapIndBits. The decimal value of these bits ranges from 0 to 3: 0 is the no fault, no leap warning condition 1 is the no fault, leap second insertion warning condition 2 is the no fault, leap second deletion warning condition 3 is the unsynchronized, alarm condition
NTF gntpTrapStratumChange	1.3.6.1.4.1.13827.2.0.0.2			A gntpTrapStratumChange trap signifies that the value of the stratum field contained in the NTP reply packets sent by the time server has changed. The current value is contained in the included variable, gntpStratum. The decimal value of this field ranges from 1 to 16: 1 is the synchronized, actively locked to the reference UTC source stratum 11 is the synchronized, but flywheeling on the local real time clock stratum 16 is the unsynchronized stratum level
C32 gntpRxPkts	1.3.6.1.4.1.13827.2.0.1	Counter32	read-only	Total number of NTP request packets received by the NTP daemon.
C32 gntpTxPkts	1.3.6.1.4.1.13827.2.0.2	Counter32	read-only	Total number of NTP reply packets transmitted by the NTP daemon.
C32 gntpIgnoredPkts	1.3.6.1.4.1.13827.2.0.3	Counter32	read-only	Total number of NTP request packets ignored by the NTP daemon.
C32 gntpDroppedPkts	1.3.6.1.4.1.13827.2.0.4	Counter32	read-only	Total number of NTP request packets dropped by the NTP daemon.
C32 gntpAuthFail	1.3.6.1.4.1.13827.2.0.5	Counter32	read-only	Total number of authentication failures detected by the NTP daemon.
INT gntpTimeFigureOfMerit	1.3.6.1.4.1.13827.2.0.6	INTEGER	read-only	The Time Figure of Merit (TFOM) value ranges from 4 to 9 and indicates the current estimate of the worst case time error. It is a logarithmic scale, with each increment indicating a tenfold increase in the worst case time error boundaries. The scale is referenced to a worst case time error of 100 picoseconds, equivalent to a TFOM of zero. During normal locked operation with GPS the TFOM is 4 and implies a worst case time error of 1 microsecond. During periods of signal loss, the GPS sub-system will compute an extrapolated worst case time error. One hour after the worst case time error has reached the value equivalent to a TFOM of 9, the NTP server will cease to send stratum 1 reply packets and an Alarm LED will be energized.
INT gntpLeapIndBits	1.3.6.1.4.1.13827.2.0.7	INTEGER	read-only	This is a status code indicating: normal operation, a leap second to be inserted in the last minute of the current day, a leap second to be deleted in the last second of the day or an alarm condition indicating loss of timing synchronization. The leap indicator field of NTP reply packets sent from this server is set to gntpLeapIndBits.
STR gntpSyncSource	1.3.6.1.4.1.13827.2.0.8	DisplayString	read-only	This is an ASCII string identifying the synchronization source for this NTP server. It is one of GPS, CPU or NONE. If it is NONE, then the server is not synchronized, has its Leap Indicator Bits in the Alarm state and is running at Stratum 16. If it is CPU, then the server is running on its NTP disciplined CPU clock at Stratum 11. Check the Stratum, Leap Indicator Bits and Time Figure of Merit for further information. NTP reply packets from this server will have the reference identifier field set to gntpSyncSource if it is GPS. Otherwise it will be set to either 127.127.1.0 (CPU) or 0.0.0.0 (NONE).
STR gntpOffsetToGPSReference	1.3.6.1.4.1.13827.2.0.9	DisplayString	read-only	This is an ASCII string containing the floating value of the current offset in units of seconds of the NTP server CPU clock to the GPS reference time. Positive values imply that the NTP server clock is ahead of the GPS reference time.
INT gntpStratum	1.3.6.1.4.1.13827.2.0.10	INTEGER	read-only	This is an integer showing the current stratum level being reported by the NTP daemon in its reply packets to clients. If it is 1, then the server is fully synchronized and delivering Stratum 1 accuracy. If it is 16, then the server is unambiguously unsynchronized. If it is 11, and the previous stratum value was 1, then the server is flywheeling on the local CPU clock. However, if the previous stratum value was 16, then the server has synchronized to its CPU Real Time Clock. NTP clients on the network should be configured to not use the time from this server if the stratum is not 1.
STR gntpVersion	1.3.6.1.4.1.13827.2.0.11	DisplayString	read-only	This is an ASCII string showing the NTP server firmware version.
gps	1.3.6.1.4.1.13827.2.1
gpstrap	1.3.6.1.4.1.13827.2.1.0
NTF gpsTrapFaultStatusChange	1.3.6.1.4.1.13827.2.1.0.1			A gpsTrapFaultStatusChange trap signifies that the value of the fault status word reported by the GPS sub-system has changed. The current value is contained in the included gpsFaultStatus.
BIT gpsFaultStatus	1.3.6.1.4.1.13827.2.1.1	Bits	read-only	This is a bit string contained in one character representing the least significant two nibbles of the GPS fault status word. Unfortunately, SNMP numbers the bits in the reverse order, so that the enumerated values are backwards from the description contained in the User's Manual for the fault status field returned by the gpsstat command. Each bit indicates a fault when set. Currently defined fault states encoded in this value: Bit 7: DAC controlling the TCXO is near the high or low limit. Bit 6: Time Figure of Merit has been 9 (unsynchronized) for 1 hour. Bit 5: Field Programmable Gate Array (FPGA) did not configure properly. Bit 4: FLASH memory had a write fault. Bit 3: Not Used. Bit 2: Not Used. Bit 1: NTP daemon is not polling the GPS reference clock. Bit 0: GPS antenna or feedline is shorted or open.
INT gpsTimeFigureOfMerit	1.3.6.1.4.1.13827.2.1.2	INTEGER	read-only	The Time Figure of Merit (TFOM) value ranges from 4 to 9 and indicates the current estimate of the worst case time error. It is a logarithmic scale, with each increment indicating a tenfold increase in the worst case time error boundaries. The scale is referenced to a worst case time error of 100 picoseconds, equivalent to a TFOM of zero. During normal locked operation the TFOM is 4 and implies a worst case time error of 1 microsecond. During periods of signal loss, the GPS sub-system will compute an extrapolated worst case time error. One hour after the worst case time error has reached the value equivalent to a TFOM of 9, the NTP server will cease to send stratum 1 reply packets and an Alarm LED will be energized.
INT gpsSigProcState	1.3.6.1.4.1.13827.2.1.3	INTEGER	read-only	Current GPS signal processor state. One of 0, 1 or 2, with 0 being the acquisition state and 2 the fully locked on state.
INT gpsNumTrackSats	1.3.6.1.4.1.13827.2.1.4	INTEGER	read-only	Current number of GPS satellites being tracked.
INT gpsVCDAC	1.3.6.1.4.1.13827.2.1.5	INTEGER	read-only	Current 16 bit, Voltage Controlled TCXO DAC value. Typical range is 20000 to 40000, where more positive numbers have the effect of raising the TCXO frequency.
STR gpsAvgCarrierToNoiseRatiodB	1.3.6.1.4.1.13827.2.1.6	DisplayString	read-only	ASCII string representing the current average carrier to noise ratio of all tracked satellites, in units of dB. Values less than 35 indicate weak signal conditions.
STR gpsReferencePosition	1.3.6.1.4.1.13827.2.1.7	DisplayString	read-only	WGS-84 latitude, longitude and height above the reference ellipsoid of the GPS antenna. Ellipsoid height may deviate from local Mean Sea Level by as much as 100 meters.
STR gpsRefPosSource	1.3.6.1.4.1.13827.2.1.8	DisplayString	read-only	ASCII string indicating the source of the GPS antenna reference position. It is one of: USR (user supplied), AVG (automatically determined by averaging thousands of 3-D position fixes, UNK (unknown).
INT gpsCurrentLeapSeconds	1.3.6.1.4.1.13827.2.1.9	INTEGER	read-only	This value is the current difference in seconds between GPS time and UTC time. GPS time is ahead of UTC time by this amount.
INT gpsFutureLeapSeconds	1.3.6.1.4.1.13827.2.1.10	INTEGER	read-only	This value is the future difference in seconds between GPS time and UTC time. Leap seconds may be inserted or deleted from the UTC timescale twice during the year: Dec 31 and June 30 at UTC midnight. If this value is the same as cdmaCurrentLeapSeconds, then no leap second insertion or deletion will occur at the next possible time. If it is different, then the change will take affect at the next possible time. GPS time will be ahead of UTC time by this amount.
STR gpsVersion	1.3.6.1.4.1.13827.2.1.11	DisplayString	read-only	ASCII string showing the GPS sub-system firmware and FPGA versions.

RFC description

EndRun Technologies enterprise MIB defining management objects for Praecis CNTP time servers and CDMA devices.

Start monitoring EndRun Technologies GPS/CDMA network time server with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download ENDRUNTECHNOLOGIES-MIB