JUNIPER-IPv6-MIB :: jnxIcmpv6StatsBadNextHdrs

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › JUNIPER-IPv6-MIB › jnxIcmpv6StatsBadNextHdrs

jnxIcmpv6StatsBadNextHdrs

Module: JUNIPER-IPv6-MIB

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

OID (numeric): 1.3.6.1.4.1.2636.3.11.1.2.17

Node type: OBJECT-TYPE

Type: Counter64

Access: read-only

Description: The total number of 'unrecognized next header' messages generated.

What is jnxIcmpv6StatsBadNextHdrs?

This Counter64 tracks how many 'unrecognized next header type encountered' ICMPv6 Parameter Problem messages the router has generated, sent when a packet specifies a next-header value the router does not know how to parse.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2636.3.11.1.2.17
snmpwalk -v2c -c public <target> JUNIPER-IPv6-MIB::jnxIcmpv6StatsBadNextHdrs

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2636.3.11.1.2.17.1
snmpget -v2c -c public <target> JUNIPER-IPv6-MIB::jnxIcmpv6StatsBadNextHdrs.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::jnxIcmpv6StatsBadNextHdrs 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.2jnxIcmpv6GlobalStatsJUNIPER-IPv6-MIB
1.3.6.1.4.1.2636.3.11.1.2.17jnxIcmpv6StatsBadNextHdrsJUNIPER-IPv6-MIB