JUNIPER-PMON-MIB :: jnxPMonFlowAllocFailures

MIB Reference — IPNetwork Monitor · Updated October 02, 2026

All MIBs › JUNIPER-PMON-MIB › jnxPMonFlowAllocFailures

jnxPMonFlowAllocFailures

Module: JUNIPER-PMON-MIB

OID (symbolic): JUNIPER-PMON-MIB::jnxPMonFlowAllocFailures

OID (numeric): 1.3.6.1.4.1.2636.3.19.2.1.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The number of flow allocation failures.

What is jnxPMonFlowAllocFailures?

A cumulative count of failed attempts to allocate a new flow record on this monitoring interface. An admin watches for this counter increasing as a sign the flow table or memory pool is exhausted.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2636.3.19.2.1.1
snmpwalk -v2c -c public <target> JUNIPER-PMON-MIB::jnxPMonFlowAllocFailures

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2636.3.19.2.1.1.1
snmpget -v2c -c public <target> JUNIPER-PMON-MIB::jnxPMonFlowAllocFailures.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> jnxPMonFlowAllocFailures.1

Start monitoring Juniper Networks router with Passive Monitoring PIC with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the JUNIPER-PMON-MIB::jnxPMonFlowAllocFailures OID value, configure state conditions and alerts, and monitor any Juniper Networks router with Passive Monitoring PIC from a single console.

How to Use in IPNetwork Monitor

Select a Juniper Networks router with Passive Monitoring PIC 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 jnxPMonFlowAllocFailures into the Find box to locate it in the OID tree, then select it and click OK. The number of flow allocation failures. 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 between polls, since a rising count of errors, failures, or discards often points to a real underlying problem. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (8 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
Numeric OIDNameModule
1.3.6.1.4.1.2636.3.19jnxPMonJUNIPER-PMON-MIB
1.3.6.1.4.1.2636.3.19.2jnxPMonErrorTableJUNIPER-PMON-MIB
1.3.6.1.4.1.2636.3.19.2.1jnxPMonErrorEntryJUNIPER-PMON-MIB
1.3.6.1.4.1.2636.3.19.2.1.1jnxPMonFlowAllocFailuresJUNIPER-PMON-MIB