MERIDIAN2-MIB :: gpsCurrentLeapSeconds

MIB Reference — IPNetwork Monitor · Updated October 02, 2026

All MIBs › MERIDIAN2-MIB › gpsCurrentLeapSeconds

gpsCurrentLeapSeconds

Module: MERIDIAN2-MIB

OID (symbolic): MERIDIAN2-MIB::gpsCurrentLeapSeconds

OID (numeric): 1.3.6.1.4.1.13827.14.2.28

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

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

What is gpsCurrentLeapSeconds?

The current whole-second offset between GPS time and UTC time, with GPS time running ahead by this many seconds. This is the live, currently-in-effect value, distinct from gpsFutureLeapSeconds which shows what it's about to become if a leap second is pending.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.13827.14.2.28
snmpwalk -v2c -c public <target> MERIDIAN2-MIB::gpsCurrentLeapSeconds

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.13827.14.2.28.1
snmpget -v2c -c public <target> MERIDIAN2-MIB::gpsCurrentLeapSeconds.1

Start monitoring EndRun Technologies Meridian II GPS-disciplined time/frequency reference with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the MERIDIAN2-MIB::gpsCurrentLeapSeconds OID value, configure state conditions and alerts, and monitor any EndRun Technologies Meridian II GPS-disciplined time/frequency reference from a single console.

OID Breakdown

Upper-level ancestors (7 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.13827endRunTechnologiesMIBENDRUNTECHNOLOGIES-MIB
Numeric OIDNameModule
1.3.6.1.4.1.13827.14meridian2GPSMERIDIAN2-MIB
1.3.6.1.4.1.13827.14.2gpsMERIDIAN2-MIB
1.3.6.1.4.1.13827.14.2.28gpsCurrentLeapSecondsMERIDIAN2-MIB