MERIDIAN2-MIB :: gptp0DelayMechanism

MIB Reference — IPNetwork Monitor · Updated October 02, 2026

All MIBs › MERIDIAN2-MIB › gptp0DelayMechanism

gptp0DelayMechanism

Module: MERIDIAN2-MIB

OID (symbolic): MERIDIAN2-MIB::gptp0DelayMechanism

OID (numeric): 1.3.6.1.4.1.13827.14.5.6

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: This value maps to the PTP Delay Mechanism, one of E2E, P2P or disabled.

What is gptp0DelayMechanism?

The path-delay measurement mechanism PTP instance 0 uses: e2e (end-to-end, delay measured to the master), p2p (peer-to-peer, delay measured hop-by-hop), or disabled. This must match what the connected PTP network/switches are configured to expect, or delay compensation (and therefore sync accuracy) will be wrong.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.13827.14.5.6
snmpwalk -v2c -c public <target> MERIDIAN2-MIB::gptp0DelayMechanism

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.13827.14.5.6.1
snmpget -v2c -c public <target> MERIDIAN2-MIB::gptp0DelayMechanism.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::gptp0DelayMechanism 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.5gptp0MERIDIAN2-MIB
1.3.6.1.4.1.13827.14.5.6gptp0DelayMechanismMERIDIAN2-MIB