SONOMA-MIB: View SNMP OID List / Download MIB

EndRun Technologies Enterprise MIB

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

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 2 is the synchronized, actively locked to a network stratum 1 server stratum 16 is the unsynchronized stratum level

Time since NTP daemon restart.

Total number of Interrupts handled by the NTP daemon.

Total number of NTP request packets received by the NTP daemon.

Total number of NTP request packets received via IRQ by the NTP daemon.

Total number of NTP reply packets transmitted by the NTP daemon.

NTP reply packets sent per second by the NTP daemon.

Total number of NTP reply packets unsent by the NTP daemon.

Total number of NTP request packets ignored by the NTP daemon.

Total number of NTP request packets dropped by the NTP daemon.

Total number of authentication failures detected by the NTP daemon.

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 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 TFOM Fault Level, the NTP server will cease to send stratum 1 reply packets and an Alarm LED will be energized. Enumeration: 'lessthan1ms': 7, 'lessthan10ms': 8, 'lessthan100us': 6, 'greaterthan10ms': 9.

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. Enumeration: 'leapDelWarning': 2, 'noFaultorLeap': 0, 'leapInsWarning': 1, 'unSynchronized': 3.

This is an ASCII string identifying the synchronization source for this NTP server. It is one of CDMA, an IP address of a stratum 1 server, 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 an IP address, then the server is operating as a stratum 2 server synchronized to the network connected stratum 1 server whose IP address is shown. 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 an IP address or 0.0.0.0 (NONE).

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.

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 greater than 1 and less than 16, it is synchronized to a network connected NTP server operating at one stratum lower. If it is 16, then the server is unambiguously unsynchronized. NTP clients on the network should be configured to not use the time from this server if the stratum is 16. Enumeration: 'cntpStratumUnsync': 16, 'cntpStratumOne': 1, 'cntpStratumTwo': 2.

This is an ASCII string showing the system root file system firmware version.

This is an ASCII string showing the system Linux kernel firmware version.

This is an ASCII string showing the installed oscillator type. It is one of TCXO, OCXO, or Rubidium.

This is an ASCII string showing the time mode of operation for any optional IRIG timecode outputs or the optional front panel vacuum fluorescent display. It DOES NOT indicate the time mode of the Linux OS clock or the NTP sub-system. Both of these are ALWAYS UTC. It can be LOCAL_AUTO, LOCAL_MANUAL, GPS or UTC. In LOCAL_AUTO mode, the local offset to UTC is automatically determined from the CDMA transmissions received from the base station. In LOCAL_MANUAL mode, the local offset to UTC is user programmed and overrides the CDMA system data.

This value is the local time offset configured for any optional IRIG timecode outputs or the optional front panel vacuum fluorescent display. It is only pertinent when cntpTimeMode is set to LOCAL_MANUAL or LOCAL_AUTO. It DOES NOT indicate the local time offset of the Linux OS clock or the NTP sub-system. Both of these are ALWAYS UTC. When cntpTimeMode is set to LOCAL_AUTO, cntpLocalOffset is determined from the CDMA base station. When cntpTimeMode is set to LOCAL_MANUAL, cntpLocalOffset is the user configured value. Its units are half-hours, ranging from -25 to 25, where negative values imply that the local time is behind UTC.

This value is the month that Daylight Savings Time begins. It affects the local time operation of any optional IRIG timecode outputs or the optional front panel vacuum fluorescent display. It is only pertinent when cntpTimeMode is set to LOCAL_MANUAL. It DOES NOT affect the Linux OS clock or the NTP sub-system. Both of these are ALWAYS UTC. Enumeration: 'jan': 1, 'mar': 3, 'feb': 2, 'aug': 8, 'sep': 9, 'apr': 4, 'jun': 6, 'jul': 7, 'disabled': 0, 'may': 5, 'nov': 11, 'dec': 12, 'oct': 10.

This value is the Sunday of the month that Daylight Savings Time begins. It affects the local time operation of any optional IRIG timecode outputs or the optional front panel vacuum fluorescent display. It is only pertinent when cntpTimeMode is set to LOCAL_MANUAL. It DOES NOT affect the Linux OS clock or the NTP sub-system. Both of these are ALWAYS UTC. Enumeration: 'fourthSunday': 4, 'thirdSunday': 3, 'firstSunday': 1, 'disabled': 0, 'secondSunday': 2, 'lastSunday': 5.

This value is the hour that Daylight Savings Time begins. It affects the local time operation of any optional IRIG timecode outputs or the optional front panel vacuum fluorescent display. It is only pertinent when cntpTimeMode is set to LOCAL_MANUAL. It DOES NOT affect the Linux OS clock or the NTP sub-system. Both of these are ALWAYS UTC. It ranges from 0 to 23, where 0 is midnight.

This value is the month that Daylight Savings Time ends. It affects the local time operation of any optional IRIG timecode outputs or the optional front panel vacuum fluorescent display. It is only pertinent when cntpTimeMode is set to LOCAL_MANUAL. It DOES NOT affect the Linux OS clock or the NTP sub-system. Both of these are ALWAYS UTC. Enumeration: 'jan': 1, 'mar': 3, 'feb': 2, 'aug': 8, 'sep': 9, 'apr': 4, 'jun': 6, 'jul': 7, 'disabled': 0, 'may': 5, 'nov': 11, 'dec': 12, 'oct': 10.

This value is the Sunday of the month that Daylight Savings Time ends. It affects the local time operation of any optional IRIG timecode outputs or the optional front panel vacuum fluorescent display. It is only pertinent when cntpTimeMode is set to LOCAL_MANUAL. It DOES NOT affect the Linux OS clock or the NTP sub-system. Both of these are ALWAYS UTC. Enumeration: 'fourthSunday': 4, 'thirdSunday': 3, 'firstSunday': 1, 'disabled': 0, 'secondSunday': 2, 'lastSunday': 5.

This value is the hour that Daylight Savings Time ends. It affects the local time operation of any optional IRIG timecode outputs or the optional front panel vacuum fluorescent display. It is only pertinent when cntpTimeMode is set to LOCAL_MANUAL. It DOES NOT affect the Linux OS clock or the NTP sub-system. Both of these are ALWAYS UTC. It ranges from 0 to 23, where 0 is midnight.

ASCII string representing the current CPU internal die temperature, in units of Celsius degrees in floating point notation.

This value is the CPU Free Memory in kiloBytes.

This value is the CPU Load Average as percent of total load.

A cdmaTrapFaultStatusChange trap signifies that the value of the least significant two nibbles of the fault status word reported by the CDMA sub-system has changed. The current value is contained in the included cdmaFaultStatus.

A cdmaTrapFault2StatusChange trap signifies that the value of the most significant two nibbles of the fault status word reported by the CDMA sub-system has changed. The current value is contained in the included cdmaFault2Status.

A cdmaTrapTimeFigureOfMeritChange trap signifies that the value of the TFOM reported by the CDMA sub-system has changed. The current value is contained in the included cdmaTimeFigureOfMerit.

This is a bit string contained in one character representing the least significant two nibbles of the CDMA subsystem 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 system Oscillator is near the high or low limit. Bit 6: Time Figure of Merit has been >= TFOM Fault Level for 1 hour. Bit 5: Field Programmable Gate Array (FPGA) did not configure properly. Bit 4: FLASH memory had a write fault. Bit 3: CDMA Receiver Communication fault. Bit 2: CDMA reference time fault (fails sanity checks). Bit 1: NTP daemon is not polling the CDMA reference clock. Bit 0: CDMA Receiver Fault, see cdmaReceiverFaultStatus for details. ATTENTION: This object is deprecated for use in snmpget queries due to a defect in reporting for one specific combination of bits. It remains in this MIB for use with the cdmaTrapFaultStatusChange object, where it reports accurately. Use the new cdmaFaultNibble0Status and cdmaFaultNibble1Status objects for querying via snmpget. Bits: 'cdmaReceiverCommFlt': 3, 'cdmaFLASHWriteFlt': 4, 'cdmaDACNearLimit': 7, 'cdmaRefTimeFlt': 2, 'cdmaNoSignalTimeout': 6, 'cdmaNTPNotPolling': 1, 'cdmaReceiverFlt': 0, 'cdmaFPGACfgFlt': 5.

This is a bit string contained in one character representing the most 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: Primary Redundant Power Supply is Faulting. Bit 6: Secondary Redundant Power Supply is Faulting. Bit 5: Oscillator PLL Faulting. Bit 4: Not Used. Bit 3: Not Used. Bit 2: Not Used. Bit 1: Not Used. Bit 0: Installed System Power exceeds maximum. ATTENTION: This object is deprecated for use in snmpget queries due to a defect in reporting for one specific combination of bits. It remains in this MIB for use with the cdmaTrapFault2StatusChange object, where it reports accurately. Use the new cdmaFaultNibble2Status and cdmaFaultNibble3Status objects for querying via snmpget. Bits: 'cdmaSysPwrOvld': 0, 'cdmaPriPwrSplyFlt': 7, 'cdmaNotUsed4': 4, 'cdmaNotUsed3': 3, 'cdmaNotUsed2': 2, 'cdmaNotUsed1': 1, 'cdmaSecPwrSplyFlt': 6, 'cdmaOscPLLFlt': 5.

This is a bit string contained in one character representing the least significant nibble of the CDMA receiver fault status byte. 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 3: CDMA Receiver Main Oscillator Frequency Control DAC near high or low limit. Bit 2: Time Figure of Merit has been >= TFOM Fault Level for 1 hour. Bit 1: Field Programmable Gate Array (FPGA) Configuration Fault. Bit 0: FLASH Memory Write Fault. Bits: 'cdmaDACNearLimit': 3, 'cdmaFPGACfgFlt': 1, 'cdmaNoSignalTimeout': 2, 'cdmaFLASHWriteFlt': 0.

This is a bit string contained in one character representing the most significant nibble of the CDMA receiver fault status byte. 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 3: CDMA Receiver Local Oscillator Synthesizer Fault. Bit 2: CDMA Receiver Local Oscillator Synthesizer Near Tuning Limit. Bit 1: CDMA Decoded Time Jump. Bit 0: CDMA Receiver Main Oscillator Fault. Bits: 'cdmaSynthNearLimit': 3, 'cdmaRefTimeFlt': 1, 'cdmaMainOscFlt': 0, 'cdmaSynthFlt': 2.

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 TFOM Fault Level, the NTP server will cease to send stratum 1 reply packets and an Alarm LED will be energized. Enumeration: 'lessthan1ms': 7, 'lessthan10ms': 8, 'lessthan100us': 6, 'greaterthan10ms': 9.

Current CDMA receiver subsytem state. One of WRM, ACQ, LKG or LKD with WRM indicating either an OCXO or Rubidium is warming up, ACQ indicating the acquisition state and LKD the fully locked on state. This is the status of the lock of the main system timing signals to the CDMA Receiver.

Current CDMA Receiver signal processor state. One of ACQ, DET, LKG, TKG or LKD with ACQ indicating the acquisition state and LKD the fully locked on state.

Current CDMA channelset, or frequency band, and specific channel being used. The first field indicates the channelset or band: NAC (North American Cellular), NAP (North American PCS), SKC (South Korean Cellular), IND (Indian Cellular) or JC (Japanese Cellular). The specific channel within the channelset is indicated in the next field, and the last field indicates the service provider. This field is not always meaningful. An example channel might be NAP_01_A which indicates channel 1 in service provider A's group of channels in the North American PCS channelset.

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.

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.

Current CDMA Receiver 16 bit, Voltage Controlled TCXO DAC value. Typical range is 20000 to 40000, where more positive numbers have the effect of raising the oscillator frequency. This is not the DAC controlling the main system oscillator.

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.

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.

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.

This value is the user-entered current difference in seconds between GPS time and UTC time. GPS time is ahead of UTC time by this amount.

This value is the user-entered 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 cdmaUserCurrentLeapSeconds, 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. On the day of a scheduled leap insertion or deletion event, the value in cdmaUserFutureLeapSeconds will be transferred to cdmaFutureLeapSeconds, which will set in motion the leap second insert/delete process. that will advance or retard the system clock so that GPS time will be ahead of UTC time by this amount.

This value is the active current difference in seconds between GPS time and UTC time. GPS time is ahead of UTC time by this amount.

This value is the active 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 on Dec 31 or June 30, then no leap second insertion or deletion will occur. If it is different, then the change will take affect at UTC midnight. GPS time will then be ahead of UTC time by this amount.

ASCII string showing the CDMA sub-system firmware and FPGA versions.

ASCII string showing the CDMA receiver firmware and FPGA versions.

Signed integer representing the current calibration delay being applied to the timing outputs, in units of nanoseconds. Positive values indicate that the timing outputs are advanced.

Unsigned integer representing the current elapsed time since the unit lost CDMA reception in units of seconds.

ASCII string representing the magnitude of the estimated time error since the unit lost CDMA reception, in units of seconds in scientific floating point notation. While locked, the value is the magnitude of the measured time error relative to CDMA.

ASCII string representing the measured time error of the timing outputs relative to CDMA, in units of seconds in scientific floating point notation. While coasting, the value is the last measured value prior to losing CDMA reception.

ASCII string representing the time deviation (TDEV) of the CDMA measurement data, in units of seconds in scientific floating point notation. While coasting, the value is the last computed value prior to losing CDMA reception.

Current system 20 bit, Voltage Controlled TCXO DAC value. Typical range is 320000 to 640000, where more positive numbers have the effect of raising the oscillator frequency. This is the DAC controlling the main system oscillator.

ASCII string representing the ageing rate per day of the installed osc- illator, in scientific floating point notation. It is computed via linear regression and requires several hours following initial lock to CDMA to see the first update. While coasting, the value is the last computed value prior to losing CDMA reception.

ASCII string representing the current equivalent averaging time of the oscillator control loop, in units of seconds in floating point notation. The value is dynamically updated based on the stability of the oscillator.

ASCII string representing the current internal chassis temperature, in units of Celsius degrees in floating point notation. A value is only available when the installed oscillator is an OCXO or Rubidium.

The CDMA signal loss fault mask is either on or off. When it is off, the server will set the Signal Loss Fault Bit in the Fault Status Byte one hour after TFOM reaches the TFOM Fault Level. When the setting is on, the server will not set the Signal Loss Fault Bit in the Fault Status Byte one hour or more after TFOM reaches TFOM Fault level.

The Primary Power input fault alarm mask is either on or off. When it is on, the server will not assert an Alarm condition on a fault in the Primary Power supply. Unlike other fault masks, the fault condition will continue to be visible in the Fault Status Byte. This mask capability is useful when performing system tests when only a single power input is available and an alarm would be undesirable. When the setting is off, the server will assert an Alarm condition in addition to setting the appropriate bit in the Fault Status Byte.

The Secondary Power input fault alarm mask is either on or off. When it is on, the server will not assert an Alarm condition on a fault in the Secondary Power supply. Unlike other fault masks, the fault condition will continue to be visible in the Fault Status Byte. This mask capability is useful when performing system tests when only a single power input is available and an alarm would be undesirable. When the setting is off, the server will assert an Alarm condition in addition to setting the appropriate bit in the Fault Status Byte.

This is a bit string contained in one character representing the least significant nibble of the CDMA subsystem 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 3: DAC controlling the system Oscillator is near the high or low limit. Bit 2: Time Figure of Merit has been >= TFOM Fault Level for 1 hour. Bit 1: Field Programmable Gate Array (FPGA) did not configure properly. Bit 0: FLASH memory had a write fault. Bits: 'cdmaDACNearLimit': 3, 'cdmaFPGACfgFlt': 1, 'cdmaNoSignalTimeout': 2, 'cdmaFLASHWriteFlt': 0.

This is a bit string contained in one character representing the second nibble of the CDMA subsystem 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 3: CDMA Receiver Communication fault. Bit 2: CDMA reference time fault (fails sanity checks). Bit 1: NTP daemon is not polling the CDMA reference clock. Bit 0: CDMA Receiver Fault, see cdmaReceiverFaultStatus for details. Bits: 'cdmaReceiverFlt': 0, 'cdmaRefTimeFlt': 2, 'cdmaReceiverCommFlt': 3, 'cdmaNTPNotPolling': 1.

This is a bit string contained in one character representing the third nibble 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 3: Primary Redundant Power Supply is Faulting. Bit 2: Secondary Redundant Power Supply is Faulting. Bit 1: Oscillator PLL Faulting. Bit 0: Not Used. Bits: 'cdmaSecPwrSplyFlt': 2, 'cdmaPriPwrSplyFlt': 3, 'cdmaNotUsed4': 0, 'cdmaOscPLLFlt': 1.

This is a bit string contained in one character representing the most significant nibble 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 3: Not Used. Bit 2: Not Used. Bit 1: Not Used. Bit 0: Installed System Power exceeds maximum. Bits: 'cdmaSysPwrOvld': 0, 'cdmaNotUsed3': 3, 'cdmaNotUsed2': 2, 'cdmaNotUsed1': 1.

ASCII string showing the status of the Settable PulseWidth, 1PPS Output, system-wide I/O signal. It may be NOT INSTALLED, or a string showing the current pulsewidth setting.

ASCII string showing the status of the Selectable Format, Time Code Output, system-wide I/O signal. It may be NOT INSTALLED, or a string showing the current time code output format setting.

Integer showing the current frequency setting of the 1 Hz resolution, Direct Digital Synthesizer (DDS) Output, system-wide I/O signal. If this option is not installed the value is -1, otherwise the value ranges from 0 to 10000000 Hz.

ASCII string showing the Baudrate of the Serial Time Output, system-wide I/O signal. It may be NOT INSTALLED, or a string showing one of 4800, 9600, 19200 or 57600.

ASCII string showing the Format of the Serial Time Output, system-wide I/O signal. It may be NOT INSTALLED, or a string showing one of SYSPLEX, TRUETIME, NENA0, NENA1, NENA8, ENDRUN, ENDRUNX or NMEA.

ASCII string showing the Parity of the Serial Time Output, system-wide I/O signal. It may be NOT INSTALLED, or a string showing one of ODD, EVEN or NONE.

ASCII string showing the first NMEA sentence selected for output from the Serial Time Output, system-wide I/O signal. This sentence is only output from the Meridian2 when the Serial Time Output Format is set to NMEA. It may be NOT INSTALLED, or a string showing one of GGA, GLL, GSA, GSV1, GSV2, RMC, VTG, ZDA or NONE. At this time, only the ZDA sentence is active from the CDMA products.

ASCII string showing the second NMEA sentence selected for output from the Serial Time Output, system-wide I/O signal. This sentence is only output from the Meridian2 when the Serial Time Output Format is set to NMEA. It may be NOT INSTALLED, or a string showing one of GGA, GLL, GSA, GSV1, GSV2, RMC, VTG, ZDA or NONE. At this time, only the ZDA sentence is active from the CDMA products.

ASCII string showing the third NMEA sentence selected for output from the Serial Time Output, system-wide I/O signal. This sentence is only output from the Meridian2 when the Serial Time Output Format is set to NMEA. It may be NOT INSTALLED, or a string showing one of GGA, GLL, GSA, GSV1, GSV2, RMC, VTG, ZDA or NONE. At this time, only the ZDA sentence is active from the CDMA products.

ASCII string showing the status of the CPU I/O Connector A. It may be NOT INSTALLED, or a string showing the current I/O selection.

ASCII string showing the status of the CPU I/O Connector B. It may be NOT INSTALLED, or a string showing the current I/O selection.

ASCII string showing the status of the CPU I/O Connector C. It may be NOT INSTALLED, or a string showing the current I/O selection.

This value is the Version of the Precise Time Protocol, which is 2.

This value is the log base 2 of the PTP Sync Interval in seconds. Values range from -7 to 0, which covers the range from 1/128 to 1 second. Enumeration: 'msec8': -7, 'msec125': -3, 'msec16': -6, 'sec1': 0, 'msec31': -5, 'msec500': -1, 'msec250': -2, 'msec63': -4.

This value is the log base 2 of the PTP Announce Interval in seconds. Values range from 0 to 4, which covers the range from 1 to 16 seconds. Enumeration: 'sec1': 0, 'sec8': 3, 'sec2': 1, 'sec4': 2, 'sec16': 4.

This value is the PTP Priority1 parameter. It ranges from 0 to 255.

This value is the PTP Priority2 parameter. It ranges from 0 to 255.

This value maps to the PTP Delay Mechanism, one of E2E, P2P or disabled. Enumeration: 'disabled': 254, 'e2e': 0, 'p2p': 1.

This value is the PTP Domain parameter. It ranges from 0 to 255.

This value maps to the PTP Time Mode, one of UTC or PTP. Enumeration: 'utc': 0, 'ptp': 1.

This value is the PTP multicast Time-To-Live parameter. It ranges from 1 to 255.

This value maps to the PTP Clock Class, one of Locked, Holdover or Unlocked on either the PTP or arbitrary, i.e. UTC time scale. Enumeration: 'unlockedARB': 58, 'unlockedPTP': 52, 'holdoverPTP': 7, 'holdoverARB': 14, 'lockedPTP': 6, 'lockedARB': 13.

This value maps to the PTP Time Scale, one of ARB or PTP. When operating in other than PTP Time Mode, this value is always ARB, arbitrary. Enumeration: 'arb': 0, 'ptp': 1.

This value maps to the PTP Port State, one of Initializing, Faulty, Disabled, Listening, PreMaster, Master, Passive, Uncalibrated or Slave. Enumeration: 'unCalibrated': 8, 'passive': 7, 'slave': 9, 'preMaster': 5, 'disabled': 3, 'init': 1, 'master': 6, 'listening': 4, 'faulty': 2.

This value maps to the PTP Time Source, one of Atom, GPS, Radio, PTP, NTP, Hand, Other or Oscillator. Enumeration: 'ntp': 80, 'oscillator': 160, 'hand': 96, 'other': 144, 'radio': 48, 'atom': 16, 'gps': 32, 'ptp': 64.

This value is the UTC offset from Atomic Time in seconds. It is currently 35 seconds.

This value maps to the validity of the UTC offset from Atomic Time in seconds. It is either False or True. Enumeration: 'true': 1, 'false': 0.

This value maps to the PTP Clock Accuracy, with values ranging from 25 nanoseconds to Unknown. Enumeration: 'usec2500': 42, 'usec10': 37, 'nsec1000': 35, 'nsec25': 32, 'unknown': 254, 'msec10': 43, 'nsec250': 34, 'usec1000': 41, 'usec250': 40, 'nsec2500': 36, 'nsec100': 33, 'usec100': 39, 'usec25': 38.

This value maps to the state of the Leap 59 second indicator, which when True, indicates that a UTC leap second deletion event is imminent. It is either False or True. Enumeration: 'true': 1, 'false': 0.

This value maps to the state of the Leap 61 second indicator, which when True, indicates that a UTC leap second insertion event is imminent. It is either False or True. Enumeration: 'true': 1, 'false': 0.

This value maps to the state of the PTP Time Traceable indicator, which when True, indicates that the time of the PTP synchronization messages is traceable to the designated time scale. It is either False or True. Enumeration: 'true': 1, 'false': 0.

This value maps to the state of the PTP Frequency Traceable indicator, which when True, indicates that the frequency of the PTP synchronization messages is traceable to the designated time scale. It is either False or True. Enumeration: 'true': 1, 'false': 0.

This value is the Version of the Precise Time Protocol, which is 2.

This value is the log base 2 of the PTP Sync Interval in seconds. Values range from -7 to 0, which covers the range from 1/128 to 1 second. Enumeration: 'msec8': -7, 'msec125': -3, 'msec16': -6, 'sec1': 0, 'msec31': -5, 'msec500': -1, 'msec250': -2, 'msec63': -4.

This value is the log base 2 of the PTP Announce Interval in seconds. Values range from 0 to 4, which covers the range from 1 to 16 seconds. Enumeration: 'sec1': 0, 'sec8': 3, 'sec2': 1, 'sec4': 2, 'sec16': 4.

This value is the PTP Priority1 parameter. It ranges from 0 to 255.

This value is the PTP Priority2 parameter. It ranges from 0 to 255.

This value maps to the PTP Delay Mechanism, one of E2E, P2P or disabled. Enumeration: 'disabled': 254, 'e2e': 0, 'p2p': 1.

This value is the PTP Domain parameter. It ranges from 0 to 255.

This value maps to the PTP Time Mode, one of UTC or PTP. Enumeration: 'utc': 0, 'ptp': 1.

This value is the PTP multicast Time-To-Live parameter. It ranges from 1 to 255.

This value maps to the PTP Clock Class, one of Locked, Holdover or Unlocked on either the PTP or arbitrary, i.e. UTC time scale. Enumeration: 'unlockedARB': 58, 'unlockedPTP': 52, 'holdoverPTP': 7, 'holdoverARB': 14, 'lockedPTP': 6, 'lockedARB': 13.

This value maps to the PTP Time Scale, one of ARB or PTP. When operating in other than PTP Time Mode, this value is always ARB, arbitrary. Enumeration: 'arb': 0, 'ptp': 1.

This value maps to the PTP Port State, one of Initializing, Faulty, Disabled, Listening, PreMaster, Master, Passive, Uncalibrated or Slave. Enumeration: 'unCalibrated': 8, 'passive': 7, 'slave': 9, 'preMaster': 5, 'disabled': 3, 'init': 1, 'master': 6, 'listening': 4, 'faulty': 2.

This value maps to the PTP Time Source, one of Atom, GPS, Radio, PTP, NTP, Hand, Other or Oscillator. Enumeration: 'ntp': 80, 'oscillator': 160, 'hand': 96, 'other': 144, 'radio': 48, 'atom': 16, 'gps': 32, 'ptp': 64.

This value is the UTC offset from Atomic Time in seconds. It is currently 35 seconds.

This value maps to the validity of the UTC offset from Atomic Time in seconds. It is either False or True. Enumeration: 'true': 1, 'false': 0.

This value maps to the PTP Clock Accuracy, with values ranging from 25 nanoseconds to Unknown. Enumeration: 'usec2500': 42, 'usec10': 37, 'nsec1000': 35, 'nsec25': 32, 'unknown': 254, 'msec10': 43, 'nsec250': 34, 'usec1000': 41, 'usec250': 40, 'nsec2500': 36, 'nsec100': 33, 'usec100': 39, 'usec25': 38.

This value maps to the state of the Leap 59 second indicator, which when True, indicates that a UTC leap second deletion event is imminent. It is either False or True. Enumeration: 'true': 1, 'false': 0.

This value maps to the state of the Leap 61 second indicator, which when True, indicates that a UTC leap second insertion event is imminent. It is either False or True. Enumeration: 'true': 1, 'false': 0.

This value maps to the state of the PTP Time Traceable indicator, which when True, indicates that the time of the PTP synchronization messages is traceable to the designated time scale. It is either False or True. Enumeration: 'true': 1, 'false': 0.

This value maps to the state of the PTP Frequency Traceable indicator, which when True, indicates that the frequency of the PTP synchronization messages is traceable to the designated time scale. It is either False or True. Enumeration: 'true': 1, 'false': 0.

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

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 2 is the synchronized, actively locked to a network stratum 1 server stratum 16 is the unsynchronized stratum level

Time since NTP daemon restart.

Total number of Interrupts handled by the NTP daemon.

Total number of NTP request packets received by the NTP daemon.

Total number of NTP request packets received via IRQ by the NTP daemon.

Total number of NTP reply packets transmitted by the NTP daemon.

NTP reply packets sent per second by the NTP daemon.

Total number of NTP reply packets unsent by the NTP daemon.

Total number of NTP request packets ignored by the NTP daemon.

Total number of NTP request packets dropped by the NTP daemon.

Total number of authentication failures detected by the NTP daemon.

The Time Figure of Merit (TFOM) value ranges from 3 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 3 and implies a worst case time error of 100 nanoseconds. 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 TFOM Fault Level, the NTP server will cease to send stratum 1 reply packets and an Alarm LED will be energized. Enumeration: 'lessthan1us': 4, 'lessthan10ms': 8, 'lessthan1ms': 7, 'lessthan10us': 5, 'lessthan100us': 6, 'greaterthan10ms': 9, 'lessthan100ns': 3.

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. Enumeration: 'leapDelWarning': 2, 'noFaultorLeap': 0, 'leapInsWarning': 1, 'unSynchronized': 3.

This is an ASCII string identifying the synchronization source for this NTP server. It is one of GPS, an IP address of a stratum 1 server, 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 an IP address, then the server is operating as a stratum 2 server synchronized to the network connected stratum 1 server whose IP address is shown. 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 an IP address or 0.0.0.0 (NONE).

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.

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 greater than 1 and less than 16, it is synchronized to a network connected NTP server operating at one stratum lower. If it is 16, then the server is unambiguously unsynchronized. NTP clients on the network should be configured to not use the time from this server if the stratum is 16. Enumeration: 'gntpStratumUnsync': 16, 'gntpStratumOne': 1, 'gntpStratumTwo': 2.

This is an ASCII string showing the system root file system firmware version.

This is an ASCII string showing the system Linux kernel firmware version.

This is an ASCII string showing the installed oscillator type. It is one of TCXO, OCXO, or Rubidium.

This is an ASCII string showing the time mode of operation for any optional IRIG timecode outputs or the optional front panel vacuum fluorescent display. It DOES NOT indicate the time mode of the Linux OS clock or the NTP sub-system. Both of these are ALWAYS UTC. It can be LOCAL, GPS or UTC.

This value is the local time offset configured for any optional IRIG timecode outputs or the optional front panel vacuum fluorescent display. It is only pertinent when gntpTimeMode is set to LOCAL. It DOES NOT indicate the local time offset of the Linux OS clock or the NTP sub-system. Both of these are ALWAYS UTC. Its units are half-hours, ranging from -25 to 25, where negative values imply that the local time is behind UTC.

This value is the month that Daylight Savings Time begins. It affects the local time operation of any optional IRIG timecode outputs or the optional front panel vacuum fluorescent display. It is only pertinent when gntpTimeMode is set to LOCAL. It DOES NOT affect the Linux OS clock or the NTP sub-system. Both of these are ALWAYS UTC. Enumeration: 'jan': 1, 'mar': 3, 'feb': 2, 'aug': 8, 'sep': 9, 'apr': 4, 'jun': 6, 'jul': 7, 'disabled': 0, 'may': 5, 'nov': 11, 'dec': 12, 'oct': 10.

This value is the Sunday of the month that Daylight Savings Time begins. It affects the local time operation of any optional IRIG timecode outputs or the optional front panel vacuum fluorescent display. It is only pertinent when gntpTimeMode is set to LOCAL. It DOES NOT affect the Linux OS clock or the NTP sub-system. Both of these are ALWAYS UTC. Enumeration: 'fourthSunday': 4, 'thirdSunday': 3, 'firstSunday': 1, 'disabled': 0, 'secondSunday': 2, 'lastSunday': 5.

This value is the hour that Daylight Savings Time begins. It affects the local time operation of any optional IRIG timecode outputs or the optional front panel vacuum fluorescent display. It is only pertinent when gntpTimeMode is set to LOCAL. It DOES NOT affect the Linux OS clock or the NTP sub-system. Both of these are ALWAYS UTC. It ranges from 0 to 23, where 0 is midnight.

This value is the month that Daylight Savings Time ends. It affects the local time operation of any optional IRIG timecode outputs or the optional front panel vacuum fluorescent display. It is only pertinent when gntpTimeMode is set to LOCAL. It DOES NOT affect the Linux OS clock or the NTP sub-system. Both of these are ALWAYS UTC. Enumeration: 'jan': 1, 'mar': 3, 'feb': 2, 'aug': 8, 'sep': 9, 'apr': 4, 'jun': 6, 'jul': 7, 'disabled': 0, 'may': 5, 'nov': 11, 'dec': 12, 'oct': 10.

This value is the Sunday of the month that Daylight Savings Time ends. It affects the local time operation of any optional IRIG timecode outputs or the optional front panel vacuum fluorescent display. It is only pertinent when gntpTimeMode is set to LOCAL. It DOES NOT affect the Linux OS clock or the NTP sub-system. Both of these are ALWAYS UTC. Enumeration: 'fourthSunday': 4, 'thirdSunday': 3, 'firstSunday': 1, 'disabled': 0, 'secondSunday': 2, 'lastSunday': 5.

This value is the hour that Daylight Savings Time ends. It affects the local time operation of any optional IRIG timecode outputs or the optional front panel vacuum fluorescent display. It is only pertinent when gntpTimeMode is set to LOCAL. It DOES NOT affect the Linux OS clock or the NTP sub-system. Both of these are ALWAYS UTC. It ranges from 0 to 23, where 0 is midnight.

ASCII string representing the current CPU internal die temperature, in units of Celsius degrees in floating point notation.

This value is the CPU Free Memory in kiloBytes.

This value is the CPU Load Average as percent of total load.

A gpsTrapFaultStatusChange trap signifies that the value of the least significant two nibbles of the fault status word reported by the GPS sub-system has changed. The current value is contained in the included gpsFaultStatus.

A gpsTrapFault2StatusChange trap signifies that the value of the most significant two nibbles of the fault status word reported by the GPS sub-system has changed. The current value is contained in the included gpsFault2Status.

A gpsTrapTimeFigureOfMeritChange trap signifies that the value of the TFOM reported by the GPS sub-system has changed. The current value is contained in the included gpsTimeFigureOfMerit.

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 >= TFOM Fault Level for 1 hour. Bit 5: Field Programmable Gate Array (FPGA) did not configure properly. Bit 4: FLASH memory had a write fault. Bit 3: GPS receiver communication fault. Bit 2: GPS reference time fault (fails sanity checks). Bit 1: NTP daemon is not polling the GPS reference clock. Bit 0: GPS antenna or feedline is shorted or open. ATTENTION: This object is deprecated for use in snmpget queries due to a defect in reporting for one specific combination of bits. It remains in this MIB for use with the gpsTrapFaultStatusChange object, where it reports accurately. Use the new gpsFaultNibble0Status and gpsFaultNibble1Status objects for polling via snmpget. Bits: 'gpsReceiverCommFlt': 3, 'gpsRefTimeFlt': 2, 'gpsAntennaFlt': 0, 'gpsNTPNotPolling': 1, 'gpsNoSignalTimeout': 6, 'gpsFLASHWriteFlt': 4, 'gpsFPGACfgFlt': 5, 'gpsDACNearLimit': 7.

This is a bit string contained in one character representing the most 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: Primary Redundant Power Supply is Faulting. Bit 6: Secondary Redundant Power Supply is Faulting. Bit 5: Oscillator PLL Faulting. Bit 4: Not Used. Bit 3: Not Used. Bit 2: Not Used. Bit 1: Not Used. Bit 0: Installed System Power exceeds maximum. ATTENTION: This object is deprecated for use in snmpget queries due to a defect in reporting for one specific combination of bits. It remains in this MIB for use with the gpsTrapFault2StatusChange object, where it reports accurately. Use the new gpsFaultNibble2Status and gpsFaultNibble3Status objects for polling via snmpget. Bits: 'gpsSysPwrOvld': 0, 'gpsSecPwrSplyFlt': 6, 'gpsPriPwrSplyFlt': 7, 'gpsOscPLLFlt': 5, 'gpsNotUsed3': 3, 'gpsNotUsed2': 2, 'gpsNotUsed1': 1, 'gpsNotUsed4': 4.

The Time Figure of Merit (TFOM) value ranges from 3 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 3 and implies a worst case time error of 100 nanoseconds. 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 TFOM Fault Level, the NTP server will cease to send stratum 1 reply packets and an Alarm LED will be energized. Enumeration: 'lessthan1us': 4, 'lessthan10ms': 8, 'lessthan1ms': 7, 'lessthan10us': 5, 'lessthan100us': 6, 'greaterthan10ms': 9, 'lessthan100ns': 3.

Current GPS signal processor state. One of WRM, ACQ, LKG or LKD with WRM indicating either an OCXO or Rubidium is warming up, ACQ indicating the acquisition state and LKD the fully locked on state. This is the status of the lock of the main system timing signals to the GPS Receiver.

Current number of GPS satellites being tracked.

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.

Channel 1 tracking status of the GPS receiver. Information includes the Satellite ID #, the Azimuth angle in degrees, the Elevation angle in degrees and the Carrier to Noise ratio, C/No in dB. If the Satellite ID # is 0, then no satellite is being tracked in this channel.

Channel 2 tracking status of the GPS receiver. Information includes the Satellite ID #, the Azimuth angle in degrees, the Elevation angle in degrees and the Carrier to Noise ratio, C/No in dB. If the Satellite ID # is 0, then no satellite is being tracked in this channel.

Channel 3 tracking status of the GPS receiver. Information includes the Satellite ID #, the Azimuth angle in degrees, the Elevation angle in degrees and the Carrier to Noise ratio, C/No in dB. If the Satellite ID # is 0, then no satellite is being tracked in this channel.

Channel 4 tracking status of the GPS receiver. Information includes the Satellite ID #, the Azimuth angle in degrees, the Elevation angle in degrees and the Carrier to Noise ratio, C/No in dB. If the Satellite ID # is 0, then no satellite is being tracked in this channel.

Channel 5 tracking status of the GPS receiver. Information includes the Satellite ID #, the Azimuth angle in degrees, the Elevation angle in degrees and the Carrier to Noise ratio, C/No in dB. If the Satellite ID # is 0, then no satellite is being tracked in this channel.

Channel 6 tracking status of the GPS receiver. Information includes the Satellite ID #, the Azimuth angle in degrees, the Elevation angle in degrees and the Carrier to Noise ratio, C/No in dB. If the Satellite ID # is 0, then no satellite is being tracked in this channel.

Channel 7 tracking status of the GPS receiver. Information includes the Satellite ID #, the Azimuth angle in degrees, the Elevation angle in degrees and the Carrier to Noise ratio, C/No in dB. If the Satellite ID # is 0, then no satellite is being tracked in this channel.

Channel 8 tracking status of the GPS receiver. Information includes the Satellite ID #, the Azimuth angle in degrees, the Elevation angle in degrees and the Carrier to Noise ratio, C/No in dB. If the Satellite ID # is 0, then no satellite is being tracked in this channel.

Channel 9 tracking status of the GPS receiver. Information includes the Satellite ID #, the Azimuth angle in degrees, the Elevation angle in degrees and the Carrier to Noise ratio, C/No in dB. If the Satellite ID # is 0, then no satellite is being tracked in this channel.

Channel 10 tracking status of the GPS receiver. Information includes the Satellite ID #, the Azimuth angle in degrees, the Elevation angle in degrees and the Carrier to Noise ratio, C/No in dB. If the Satellite ID # is 0, then no satellite is being tracked in this channel.

Channel 11 tracking status of the GPS receiver. Information includes the Satellite ID #, the Azimuth angle in degrees, the Elevation angle in degrees and the Carrier to Noise ratio, C/No in dB. If the Satellite ID # is 0, then no satellite is being tracked in this channel.

Channel 12 tracking status of the GPS receiver. Information includes the Satellite ID #, the Azimuth angle in degrees, the Elevation angle in degrees and the Carrier to Noise ratio, C/No in dB. If the Satellite ID # is 0, then no satellite is being tracked in this channel.

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. This value is the last instantaneous position fix as reported by the GPS receiver. It is not averaged.

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. When the GPS Dynamic Mode is OFF or Static, this value is the result of a 24 hour average of fixes that is used to establish the precise timing reference position.

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), DYN (current un-averaged 3-D position fix, operation is in dynamic mode), UNK (unknown).

This value is the current difference in seconds between GPS time and UTC time. GPS time is ahead of UTC time by this amount.

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 gpsCurrentLeapSeconds, 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.

This value, LS is the current difference in seconds between GPS time and UTC time as contained in the GPS Almanac UTC data. GPS time is ahead of UTC time by this amount. For more detailed information, consult the GPS-ICD-200.

This value, LSF is the future difference in seconds between GPS time and UTC time as contained in the GPS Almanac UTC data. 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 gpsAlmLS, 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 time defined by the GPS Almanac parameters, WN_lsf and DN. GPS time will be ahead of UTC time by this amount. For more detailed information, consult the GPS-ICD-200.

This value, WN_lsf is the GPS Week Number during which the UTC leap second offset to GPS time will transition to the Leap Second Future value. The GPS week numbers began on January 6, 1980 with week number 0. If a leap second has recently been inserted, this week number could be in the past, in which case the current and future leap seconds values will be equal. For more detailed information, consult the GPS-ICD-200.

This value, DN is the Day Number of the week in which the UTC leap second offset to GPS time will transition to the Leap Second Future value. The GPS day numbers begin on Sunday with day number 1. The leap second insertion occurs at the end of the given day. For more detailed information, consult the GPS-ICD-200.

ASCII string representing the value of the a0 coefficient of the linear fit of the UTC offset to GPS time. a0 is the constant term in the equation, in units of seconds, in scientific floating point notation. The GPS and UTC timescales are separated by leap seconds and another small error, typically less than 10 nanoseconds, which is estimated using this linear fit. For more detailed information, consult the GPS-ICD-200.

ASCII string representing the value of the a1 coefficient of the linear fit of the UTC offset to GPS time. a1 is the slope term in the equation, in units of seconds per second, in scientific floating point notation. The GPS and UTC timescales are separated by leap seconds and another small error, typically less than 10 nanoseconds, which is estimated using this linear fit. For more detailed information, consult the GPS-ICD-200.

This value, WN_t is the GPS Week Number during which the reference time for the linear fit equation defined by a0 and a1 occurs. It is used along with t_ot to calculate a value of GPS seconds to offset the linear fit in the time domain. For more detailed information, consult the GPS-ICD-200.

This value, t_ot is the second of the GPS week WN_t at which time the linear fit equation defined by a0 and a1 will evaluate to a0. The seconds range from 0 at the beginning of day number 1 to 604799 at the end of day number 7. For more detailed information, consult the GPS-ICD-200.

This value, (GPS - UTC) is the current sub-seconds offset of the GPS timescale to the UTC timescale, computed using the received GPS almanac parameters (WN_t, t_ot, a0 and a1) and the current GPS week number and time-of-week. The units are in picoseconds. This value must be added to the current leap seconds offset to fully quantify the amount that the GPS timescale is ahead of the UTC timescale. For more detailed information, consult the GPS-ICD-200.

ASCII string showing the GPS sub-system firmware and FPGA versions.

The GPS dynamic mode is either on or off. When it is off, the server is assumed to be in a static installation. In this case, single satellite mode of operation is supported and Timing Receiver Autonomous Integrity Monitoring (TRAIM) is supported. When the setting is on, the server is assumed to be on a moving platform. In this case, minimum four satellite, 3-D operation is required and the TRAIM functionality is minimal. Enumeration: 'gpsDynModeOFF': 0, 'gpsDynModeON': 1.

Signed integer representing the current calibration delay being applied to the timing outputs, in units of nanoseconds. Positive values indicate that the timing outputs are advanced.

Unsigned integer representing the current elapsed time since the unit lost GPS reception in units of seconds.

ASCII string representing the magnitude of the estimated time error since the unit lost GPS reception, in units of seconds in scientific floating point notation. While locked, the value is the magnitude of the measured time error relative to GPS.

ASCII string representing the measured time error of the timing outputs relative to GPS, in units of seconds in scientific floating point notation. While coasting, the value is the last measured value prior to losing GPS reception.

ASCII string representing the time deviation (TDEV) of the GPS measurement data, in units of seconds in scientific floating point notation. While coasting, the value is the last computed value prior to losing GPS reception.

Current 20 bit, System Voltage Controlled Oscillator DAC value. Typical range is 320000 to 640000, where more positive numbers have the effect of raising the oscillator frequency.

ASCII string representing the ageing rate per day of the installed osc- illator, in scientific floating point notation. It is computed via linear regression and requires several hours following initial lock to GPS to see the first update. While coasting, the value is the last computed value prior to losing GPS reception.

ASCII string representing the current equivalent averaging time of the oscillator control loop, in units of seconds in floating point notation. The value is dynamically updated based on the stability of the oscillator.

ASCII string representing the current internal chassis temperature, in units of Celsius degrees in floating point notation. A value is only available when the installed oscillator is an OCXO or Rubidium.

The GPS antenna fault mask is either on or off. When it is off, the server will set the Antenna Fault Bit in the Fault Status Byte if an improper antenna impedance is detected. When the setting is on, the server will not set the Antenna Fault Bit in the Fault Status Byte if an improper antenna impedance is detected.

The GPS signal loss fault mask is either on or off. When it is off, the server will set the Signal Loss Fault Bit in the Fault Status Byte one hour after TFOM reaches the TFOM Fault Level. When the setting is on, the server will not set the Signal Loss Fault Bit in the Fault Status Byte one hour or more after TFOM reaches TFOM Fault level.

The Primary Power input fault alarm mask is either on or off. When it is on, the server will not assert an Alarm condition on a fault in the Primary Power supply. Unlike other fault masks, the fault condition will continue to be visible in the Fault Status Byte. This mask capability is useful when performing system tests when only a single power input is available and an alarm would be undesirable. When the setting is off, the server will assert an Alarm condition in addition to setting the appropriate bit in the Fault Status Byte.

The Secondary Power input fault alarm mask is either on or off. When it is on, the server will not assert an Alarm condition on a fault in the Secondary Power supply. Unlike other fault masks, the fault condition will continue to be visible in the Fault Status Byte. This mask capability is useful when performing system tests when only a single power input is available and an alarm would be undesirable. When the setting is off, the server will assert an Alarm condition in addition to setting the appropriate bit in the Fault Status Byte.

This is a bit string contained in one character representing the least significant nibble 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 3: DAC controlling the TCXO is near the high or low limit. Bit 2: Time Figure of Merit has been >= TFOM Fault Level for 1 hour. Bit 1: Field Programmable Gate Array (FPGA) did not configure properly. Bit 0: FLASH memory had a write fault. Bits: 'gpsNoSignalTimeout': 2, 'gpsFPGACfgFlt': 1, 'gpsDACNearLimit': 3, 'gpsFLASHWriteFlt': 0.

This is a bit string contained in one character representing the second nibble 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 3: GPS receiver communication fault. Bit 2: GPS reference time fault (fails sanity checks). Bit 1: NTP daemon is not polling the GPS reference clock. Bit 0: GPS antenna or feedline is shorted or open. Bits: 'gpsReceiverCommFlt': 3, 'gpsRefTimeFlt': 2, 'gpsAntennaFlt': 0, 'gpsNTPNotPolling': 1.

This is a bit string contained in one character representing the third nibble 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 3: Primary Redundant Power Supply is Faulting. Bit 2: Secondary Redundant Power Supply is Faulting. Bit 1: Oscillator PLL Faulting. Bit 0: Not Used. Bits: 'gpsPriPwrSplyFlt': 3, 'gpsOscPLLFlt': 1, 'gpsSecPwrSplyFlt': 2, 'gpsNotUsed4': 0.

This is a bit string contained in one character representing the most significant nibble 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 3: Not Used. Bit 2: Not Used. Bit 1: Not Used. Bit 0: Installed System Power exceeds maximum. Bits: 'gpsSysPwrOvld': 0, 'gpsNotUsed2': 2, 'gpsNotUsed1': 1, 'gpsNotUsed3': 3.

ASCII string showing the status of the Settable PulseWidth, 1PPS Output, system-wide I/O signal. It may be NOT INSTALLED, or a string showing the current pulsewidth setting.

ASCII string showing the status of the Selectable Format, Time Code Output, system-wide I/O signal. It may be NOT INSTALLED, or a string showing the current time code output format setting.

Integer showing the current frequency setting of the 1 Hz resolution, Direct Digital Synthesizer (DDS) Output, system-wide I/O signal. If this option is not installed the value is -1, otherwise the value ranges from 0 to 10000000 Hz.

ASCII string showing the Baudrate of the Serial Time Output, system-wide I/O signal. It may be NOT INSTALLED, or a string showing one of 4800, 9600, 19200 or 57600.

ASCII string showing the Format of the Serial Time Output, system-wide I/O signal. It may be NOT INSTALLED, or a string showing one of SYSPLEX, TRUETIME, NENA0, NENA1, NENA8, ENDRUN, ENDRUNX or NMEA.

ASCII string showing the Parity of the Serial Time Output, system-wide I/O signal. It may be NOT INSTALLED, or a string showing one of ODD, EVEN or NONE.

ASCII string showing the first NMEA sentence selected for output from the Serial Time Output, system-wide I/O signal. This sentence is only output from the Meridian2 when the Serial Time Output Format is set to NMEA. It may be NOT INSTALLED, or a string showing one of GGA, GLL, GSA, GSV1, GSV2, RMC, VTG, ZDA or NONE.

ASCII string showing the second NMEA sentence selected for output from the Serial Time Output, system-wide I/O signal. This sentence is only output from the Meridian2 when the Serial Time Output Format is set to NMEA. It may be NOT INSTALLED, or a string showing one of GGA, GLL, GSA, GSV1, GSV2, RMC, VTG, ZDA or NONE.

ASCII string showing the third NMEA sentence selected for output from the Serial Time Output, system-wide I/O signal. This sentence is only output from the Meridian2 when the Serial Time Output Format is set to NMEA. It may be NOT INSTALLED, or a string showing one of GGA, GLL, GSA, GSV1, GSV2, RMC, VTG, ZDA or NONE.

ASCII string showing the status of the CPU I/O Connector A. It may be NOT INSTALLED, or a string showing the current I/O selection.

ASCII string showing the status of the CPU I/O Connector B. It may be NOT INSTALLED, or a string showing the current I/O selection.

ASCII string showing the status of the CPU I/O Connector C. It may be NOT INSTALLED, or a string showing the current I/O selection.

This value is the Version of the Precise Time Protocol, which is 2.

This value is the log base 2 of the PTP Sync Interval in seconds. Values range from -7 to 0, which covers the range from 1/128 to 1 second. Enumeration: 'msec8': -7, 'msec125': -3, 'msec16': -6, 'sec1': 0, 'msec31': -5, 'msec500': -1, 'msec250': -2, 'msec63': -4.

This value is the log base 2 of the PTP Announce Interval in seconds. Values range from 0 to 4, which covers the range from 1 to 16 seconds. Enumeration: 'sec1': 0, 'sec8': 3, 'sec2': 1, 'sec4': 2, 'sec16': 4.

This value is the PTP Priority1 parameter. It ranges from 0 to 255.

This value is the PTP Priority2 parameter. It ranges from 0 to 255.

This value maps to the PTP Delay Mechanism, one of E2E, P2P or disabled. Enumeration: 'disabled': 254, 'e2e': 0, 'p2p': 1.

This value is the PTP Domain parameter. It ranges from 0 to 255.

This value maps to the PTP Time Mode, one of UTC or PTP. Enumeration: 'utc': 0, 'ptp': 1.

This value is the PTP multicast Time-To-Live parameter. It ranges from 1 to 255.

This value maps to the PTP Clock Class, one of Locked, Holdover or Unlocked on either the PTP or arbitrary, i.e. UTC time scale. Enumeration: 'unlockedARB': 58, 'unlockedPTP': 52, 'holdoverPTP': 7, 'holdoverARB': 14, 'lockedPTP': 6, 'lockedARB': 13.

This value maps to the PTP Time Scale, one of ARB or PTP. When operating in other than PTP Time Mode, this value is always ARB, arbitrary. Enumeration: 'arb': 0, 'ptp': 1.

This value maps to the PTP Port State, one of Initializing, Faulty, Disabled, Listening, PreMaster, Master, Passive, Uncalibrated or Slave. Enumeration: 'unCalibrated': 8, 'passive': 7, 'slave': 9, 'preMaster': 5, 'disabled': 3, 'init': 1, 'master': 6, 'listening': 4, 'faulty': 2.

This value maps to the PTP Time Source, one of Atom, GPS, Radio, PTP, NTP, Hand, Other or Oscillator. Enumeration: 'ntp': 80, 'oscillator': 160, 'hand': 96, 'other': 144, 'radio': 48, 'atom': 16, 'gps': 32, 'ptp': 64.

This value is the UTC offset from Atomic Time in seconds. It is currently 35 seconds.

This value maps to the validity of the UTC offset from Atomic Time in seconds. It is either False or True. Enumeration: 'true': 1, 'false': 0.

This value maps to the PTP Clock Accuracy, with values ranging from 25 nanoseconds to Unknown. Enumeration: 'usec2500': 42, 'usec10': 37, 'nsec1000': 35, 'nsec25': 32, 'unknown': 254, 'msec10': 43, 'nsec250': 34, 'usec1000': 41, 'usec250': 40, 'nsec2500': 36, 'nsec100': 33, 'usec100': 39, 'usec25': 38.

This value maps to the state of the Leap 59 second indicator, which when True, indicates that a UTC leap second deletion event is imminent. It is either False or True. Enumeration: 'true': 1, 'false': 0.

This value maps to the state of the Leap 61 second indicator, which when True, indicates that a UTC leap second insertion event is imminent. It is either False or True. Enumeration: 'true': 1, 'false': 0.

This value maps to the state of the PTP Time Traceable indicator, which when True, indicates that the time of the PTP synchronization messages is traceable to the designated time scale. It is either False or True. Enumeration: 'true': 1, 'false': 0.

This value maps to the state of the PTP Frequency Traceable indicator, which when True, indicates that the frequency of the PTP synchronization messages is traceable to the designated time scale. It is either False or True. Enumeration: 'true': 1, 'false': 0.

This value is the Version of the Precise Time Protocol, which is 2.

This value is the log base 2 of the PTP Sync Interval in seconds. Values range from -7 to 0, which covers the range from 1/128 to 1 second. Enumeration: 'msec8': -7, 'msec125': -3, 'msec16': -6, 'sec1': 0, 'msec31': -5, 'msec500': -1, 'msec250': -2, 'msec63': -4.

This value is the log base 2 of the PTP Announce Interval in seconds. Values range from 0 to 4, which covers the range from 1 to 16 seconds. Enumeration: 'sec1': 0, 'sec8': 3, 'sec2': 1, 'sec4': 2, 'sec16': 4.

This value is the PTP Priority1 parameter. It ranges from 0 to 255.

This value is the PTP Priority2 parameter. It ranges from 0 to 255.

This value maps to the PTP Delay Mechanism, one of E2E, P2P or disabled. Enumeration: 'disabled': 254, 'e2e': 0, 'p2p': 1.

This value is the PTP Domain parameter. It ranges from 0 to 255.

This value maps to the PTP Time Mode, one of UTC or PTP. Enumeration: 'utc': 0, 'ptp': 1.

This value is the PTP multicast Time-To-Live parameter. It ranges from 1 to 255.

This value maps to the PTP Clock Class, one of Locked, Holdover or Unlocked on either the PTP or arbitrary, i.e. UTC time scale. Enumeration: 'unlockedARB': 58, 'unlockedPTP': 52, 'holdoverPTP': 7, 'holdoverARB': 14, 'lockedPTP': 6, 'lockedARB': 13.

This value maps to the PTP Time Scale, one of ARB or PTP. When operating in other than PTP Time Mode, this value is always ARB, arbitrary. Enumeration: 'arb': 0, 'ptp': 1.

This value maps to the PTP Port State, one of Initializing, Faulty, Disabled, Listening, PreMaster, Master, Passive, Uncalibrated or Slave. Enumeration: 'unCalibrated': 8, 'passive': 7, 'slave': 9, 'preMaster': 5, 'disabled': 3, 'init': 1, 'master': 6, 'listening': 4, 'faulty': 2.

This value maps to the PTP Time Source, one of Atom, GPS, Radio, PTP, NTP, Hand, Other or Oscillator. Enumeration: 'ntp': 80, 'oscillator': 160, 'hand': 96, 'other': 144, 'radio': 48, 'atom': 16, 'gps': 32, 'ptp': 64.

This value is the UTC offset from Atomic Time in seconds. It is currently 35 seconds.

This value maps to the validity of the UTC offset from Atomic Time in seconds. It is either False or True. Enumeration: 'true': 1, 'false': 0.

This value maps to the PTP Clock Accuracy, with values ranging from 25 nanoseconds to Unknown. Enumeration: 'usec2500': 42, 'usec10': 37, 'nsec1000': 35, 'nsec25': 32, 'unknown': 254, 'msec10': 43, 'nsec250': 34, 'usec1000': 41, 'usec250': 40, 'nsec2500': 36, 'nsec100': 33, 'usec100': 39, 'usec25': 38.

This value maps to the state of the Leap 59 second indicator, which when True, indicates that a UTC leap second deletion event is imminent. It is either False or True. Enumeration: 'true': 1, 'false': 0.

This value maps to the state of the Leap 61 second indicator, which when True, indicates that a UTC leap second insertion event is imminent. It is either False or True. Enumeration: 'true': 1, 'false': 0.

This value maps to the state of the PTP Time Traceable indicator, which when True, indicates that the time of the PTP synchronization messages is traceable to the designated time scale. It is either False or True. Enumeration: 'true': 1, 'false': 0.

This value maps to the state of the PTP Frequency Traceable indicator, which when True, indicates that the frequency of the PTP synchronization messages is traceable to the designated time scale. It is either False or True. Enumeration: 'true': 1, 'false': 0.