JUNIPER-IFOPTICS-MIB :: jnxPMCurSuspectReason

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › JUNIPER-IFOPTICS-MIB › jnxPMCurSuspectReason

jnxPMCurSuspectReason

Module: JUNIPER-IFOPTICS-MIB

OID (symbolic): JUNIPER-IFOPTICS-MIB::jnxPMCurSuspectReason

OID (numeric): 1.3.6.1.4.1.2636.3.71.1.2.1.1.34

Node type: OBJECT-TYPE

Type: Integer32

Access: read-only

Description: If SuspectedFlag is true, the reson for the PM data being suspect. 0 - not applicable 1 - unknown 2 - new object 3 - interface disabled 4 - clock shift detected 5 - cleared by user 6 - interval too short secs < 890 7 - interval too long secs > 910 8 - near end unavailable 9 - far end unavailable 10 - partial data 11 - missing intervals due to restarts

What is jnxPMCurSuspectReason?

When jnxPMCurSuspectedFlag is true, this code explains why the current interval's PM data is considered unreliable: reasons include the object being newly created, the interface being disabled, a clock shift being detected, the data being manually cleared, the interval being too short or too long, either end of the link being unavailable, partial data, or missing intervals due to a restart. Admins use this to decide whether a suspicious PM reading reflects a real optical problem or just a data-collection artifact they can safely ignore.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2636.3.71.1.2.1.1.34
snmpwalk -v2c -c public <target> JUNIPER-IFOPTICS-MIB::jnxPMCurSuspectReason

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2636.3.71.1.2.1.1.34.1
snmpget -v2c -c public <target> JUNIPER-IFOPTICS-MIB::jnxPMCurSuspectReason.1

Start monitoring Juniper router or switch with pluggable optical/DWDM transceivers with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the JUNIPER-IFOPTICS-MIB::jnxPMCurSuspectReason OID value, configure state conditions and alerts, and monitor any Juniper router or switch with pluggable optical/DWDM transceivers from a single console.

OID Breakdown

Upper-level ancestors (9 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.2636juniperMIBJUNIPER-SMI
1.3.6.1.4.1.2636.3jnxMibsJUNIPER-SMI
1.3.6.1.4.1.2636.3.71jnxOpticsMibRootJUNIPER-SMI
Numeric OIDNameModule
1.3.6.1.4.1.2636.3.71.1jnxIfOpticsMibJUNIPER-IFOPTICS-MIB
1.3.6.1.4.1.2636.3.71.1.2jnxOpticsPerformanceMonitoringJUNIPER-IFOPTICS-MIB
1.3.6.1.4.1.2636.3.71.1.2.1jnxOpticsPMCurrentTableJUNIPER-IFOPTICS-MIB
1.3.6.1.4.1.2636.3.71.1.2.1.1jnxOpticsPMCurrentEntryJUNIPER-IFOPTICS-MIB
1.3.6.1.4.1.2636.3.71.1.2.1.1.34jnxPMCurSuspectReasonJUNIPER-IFOPTICS-MIB