JUNIPER-IPv6-MIB :: jnxIpv6StatsFragOverFlows

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › JUNIPER-IPv6-MIB › jnxIpv6StatsFragOverFlows

jnxIpv6StatsFragOverFlows

Module: JUNIPER-IPv6-MIB

OID (symbolic): JUNIPER-IPv6-MIB::jnxIpv6StatsFragOverFlows

OID (numeric): 1.3.6.1.4.1.2636.3.11.1.1.9

Node type: OBJECT-TYPE

Type: Counter64

Access: read-only

Description: The total number of fragments that exceeded limit.

What is jnxIpv6StatsFragOverFlows?

This Counter64 tracks IPv6 fragments dropped because they exceeded an internal reassembly limit. It is a resource-exhaustion indicator distinct from a simple timeout, useful when diagnosing why large fragmented flows are being discarded.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2636.3.11.1.1.9
snmpwalk -v2c -c public <target> JUNIPER-IPv6-MIB::jnxIpv6StatsFragOverFlows

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2636.3.11.1.1.9.1
snmpget -v2c -c public <target> JUNIPER-IPv6-MIB::jnxIpv6StatsFragOverFlows.1

Start monitoring Juniper Networks router/switch running IPv6 (JUNOS-based platform) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the JUNIPER-IPv6-MIB::jnxIpv6StatsFragOverFlows OID value, configure state conditions and alerts, and monitor any Juniper Networks router/switch running IPv6 (JUNOS-based platform) from a single console.

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.11jnxIpv6JUNIPER-IPv6-MIB
1.3.6.1.4.1.2636.3.11.1jnxIpv6StatsJUNIPER-IPv6-MIB
1.3.6.1.4.1.2636.3.11.1.1jnxIpv6GlobalStatsJUNIPER-IPv6-MIB
1.3.6.1.4.1.2636.3.11.1.1.9jnxIpv6StatsFragOverFlowsJUNIPER-IPv6-MIB