JUNIPER-PFE-MIB

All MIBs › JUNIPER-PFE-MIB

Organization: Juniper Networks, Inc.

Last Updated: 2014--1-1-

Category: Hardware and Environment, Vendor: Juniper

Description: Juniper Networks MIB for monitoring Packet Forwarding Engine (PFE) statistics, errors, and utilization on Juniper routing platforms.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is JUNIPER-PFE-MIB?

This Juniper enterprise MIB covers the Packet Forwarding Engine (PFE) on Juniper routing platforms, exposing internal PFE memory subsystem and forwarding-chip resource data. It includes micro-kernel (ukern) memory free-percentage, per-forwarding-chip-slot memory free-percentage, memory-type classification, and dedicated memory-error notification objects. Monitoring emphasis is squarely on hardware/software health of the forwarding plane — jnxPfeMemoryUkernFreePercent and jnxPfeMemoryForwardingPercentFree act as a memory-load gauge for the PFE, and jnxPfeMemoryNotifications alert on low-memory or memory-error conditions that can precede packet-forwarding failures. It complements Juniper's broader chassis/FPC MIB hierarchy for slot and line-card context. It is deployed on Juniper routers (e.g. MX/M/T series) to watch PFE memory health per line card/FPC as part of routine capacity and fault monitoring, and engineers can perform a JUNIPER-PFE-MIB download to load these objects into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in JUNIPER-PFE-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Juniper router (MX/M/T Series with Packet Forwarding Engine)

Monitoring Examples

Polling jnxPfeMemoryUkernTable/jnxPfeMemoryUkernEntry gives jnxPfeMemoryUkernFreePercent, revealing when microkernel memory on a PFE is running low, a precursor to forwarding instability. jnxPfeMemoryForwardingTable/jnxPfeMemoryForwardingEntry keyed by jnxPfeMemoryForwardingChipSlot lets an operator compare free memory across forwarding chips or slots to catch an unevenly loaded or leaking chip. A jnxPfeMemoryNotifications trap (under pfeMemoryErrorsNotificationPrefix) would fire when free memory crosses a critical threshold, prompting proactive intervention before packet loss occurs.

What Can Be Monitored

PFE microkernel memory free percentage
per-forwarding-chip memory free percentage
memory type breakdown
PFE memory error notifications/traps

Imported Objects

From JUNIPER-SMI

jnxPfeMibRoot

OBJECT-IDENTITY

From SNMPv2-SMI

Counter32
Counter64
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE

From SNMPv2-TC

DisplayString
TEXTUAL-CONVENTION

How to Use in IPNetwork Monitor

Example using jnxPfeNotifyGlParsed OID:

Select a Juniper router (MX/M/T Series, Packet Forwarding Engine memory health) 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 jnxPfeNotifyGlParsed into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. It reports the count of notifications reported by the routing chip. 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 sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
jnxPfeMib	1.3.6.1.4.1.2636.3.44.1			The MIB provides PFE specific data.
jnxPfeNotification	1.3.6.1.4.1.2636.3.44.1.1
pfeMemoryErrorsNotificationPrefix	1.3.6.1.4.1.2636.3.44.1.1.0
NTF pfeMemoryErrors	1.3.6.1.4.1.2636.3.44.1.1.0.1			A pfeMemoryErrors notification is sent when the value of jnxPfeParityErrors or jnxPfeEccErrors increases.
jnxPfeNotifyGlTable	1.3.6.1.4.1.2636.3.44.1.1.1		not-accessible	This table provides global PFE notification statistics.
jnxPfeNotifyGlEntry	1.3.6.1.4.1.2636.3.44.1.1.1.1		not-accessible
I32 jnxPfeNotifyGlSlot	1.3.6.1.4.1.2636.3.44.1.1.1.1.1	Integer32	not-accessible	The PFE slot number for this set of global PFE notification statistics.
C32 jnxPfeNotifyGlParsedEx	1.3.6.1.4.1.2636.3.44.1.1.1.1.2	Counter32	read-only	Count of notifications reported by the routing chip.
C32 jnxPfeNotifyGlAged	1.3.6.1.4.1.2636.3.44.1.1.1.1.3	Counter32	read-only	Count of notifications that are dropped due to the fact that the they have been in the system for too long and hence not valid anymore.
C32 jnxPfeNotifyGlCorrupt	1.3.6.1.4.1.2636.3.44.1.1.1.1.4	Counter32	read-only	Count of notifications dropped due to the fact that they have an invalid notification result format. This counter is valid for Internet Processor-I and Internet Processor-II only.
C32 jnxPfeNotifyGlIllegal	1.3.6.1.4.1.2636.3.44.1.1.1.1.5	Counter32	read-only	Count of notifications dropped due to the fact that they have an illegal notification type.
C32 jnxPfeNotifyGlSample	1.3.6.1.4.1.2636.3.44.1.1.1.1.6	Counter32	read-only	Count of sample notifications reported by the routing chip.
C32 jnxPfeNotifyGlGiants	1.3.6.1.4.1.2636.3.44.1.1.1.1.7	Counter32	read-only	Count of notifications dropped that are larger than the supported DMA size.
C32 jnxPfeNotifyGlTtlExceeded	1.3.6.1.4.1.2636.3.44.1.1.1.1.8	Counter32	read-only	Count of options/TTL-expired notifications that need to be sent to service interfaces as transit packets. This counter is valid for Internet Processor-I and Internet Processor-II only.
C32 jnxPfeNotifyGlTtlExcErrors	1.3.6.1.4.1.2636.3.44.1.1.1.1.9	Counter32	read-only	Count of options/TTL-expired packet notifications that could not be sent as transit packets because the output interface could not be determined. This counter is valid for Internet Processor-I and Internet Processor-II only.
C32 jnxPfeNotifyGlSvcOptAsp	1.3.6.1.4.1.2636.3.44.1.1.1.1.10	Counter32	read-only	Count of IP options packets that are sent out to a Services PIC.
C32 jnxPfeNotifyGlSvcOptRe	1.3.6.1.4.1.2636.3.44.1.1.1.1.11	Counter32	read-only	Count of IP options packets that are sent out to the Routing Engine.
C32 jnxPfeNotifyGlPostSvcOptOut	1.3.6.1.4.1.2636.3.44.1.1.1.1.12	Counter32	read-only	Count of notifications that were re-injected by the services PIC after it had processed the associated packets. These notifications now need to be forwarded out to their actual destination. This counter is valid for Internet Processor-I and Internet Processor-II only.
C32 jnxPfeNotifyGlOptTtlExp	1.3.6.1.4.1.2636.3.44.1.1.1.1.13	Counter32	read-only	Count of TTL-expired transit packets.
C32 jnxPfeNotifyGlDiscSample	1.3.6.1.4.1.2636.3.44.1.1.1.1.14	Counter32	read-only	Count of sample notifications that are dropped as they refer to discarded packets in PFE.
C32 jnxPfeNotifyGlRateLimited	1.3.6.1.4.1.2636.3.44.1.1.1.1.15	Counter32	read-only	Count of notifications ignored because of PFE software throttling.
C32 jnxPfeNotifyGlPktGetFails	1.3.6.1.4.1.2636.3.44.1.1.1.1.16	Counter32	read-only	Count of notifications where we could not allocate memory for DMA.
C32 jnxPfeNotifyGlDmaFails	1.3.6.1.4.1.2636.3.44.1.1.1.1.17	Counter32	read-only	Count of notifications where the DMA of associated packets failed for miscellaneous reasons. Valid for T-series Internet Processor only.
C32 jnxPfeNotifyGlDmaTotals	1.3.6.1.4.1.2636.3.44.1.1.1.1.18	Counter32	read-only	Count of notifications for which the packet DMA completed. Valid for T-series Internet Processor only.
C32 jnxPfeNotifyGlUnknowns	1.3.6.1.4.1.2636.3.44.1.1.1.1.19	Counter32	read-only	Count of notifications that could not be resolved to a known next hop destination. Valid for T-series Internet Processor only.
C32 jnxPfeNotifyGlParAccSec	1.3.6.1.4.1.2636.3.44.1.1.1.1.20	Counter32	read-only	Count of notifications for the packets parsed/processed by access-security.
jnxPfeNotifyTypeTable	1.3.6.1.4.1.2636.3.44.1.1.2		not-accessible	This provides type-specific PFE notification stats
jnxPfeNotifyTypeEntry	1.3.6.1.4.1.2636.3.44.1.1.2.1		not-accessible
INT jnxPfeNotifyTypeId	1.3.6.1.4.1.2636.3.44.1.1.2.1.1	INTEGER	not-accessible	This identifies the PFE notification type for this row's stats. Below is a description of each notification type: 1. illegal Packets with invalid notification type. 2. unclassified Packets that did not have a key lookup performed on them. 3. option Packets which have L3 options present. 4. nextHop Packets that are destined to the host. 5. discard Used when a discarded packet is sent to the route processor. 6. sample Unused. 7. redirect This is used when a packet is being sent out on the interface it came in on. 8. dontFragment This is used that a packet needs to be fragmented but the DF (don't fragment) bit is set. 9. cfdf When an MTU exceeded indication is triggered by the CF chip and the packet has DF (don't fragment) set. 10. poison Packets that resolved to a poisoned next hop index. 11. unknown Packets of unknown notification type. 12. specialMemPkt Packets with special memory pkt type notification used in diagnostics. 13. autoconfig Packets with autoconfig PFE notification type used for dynamic VLANs. 14. reject Packets of reject PFE notification type.
STR jnxPfeNotifyTypeDescr	1.3.6.1.4.1.2636.3.44.1.1.2.1.2	DisplayString	read-only	The description of the Pfe Notification type for this entry.
C32 jnxPfeNotifyTypeParsed	1.3.6.1.4.1.2636.3.44.1.1.2.1.3	Counter32	read-only	Count of successful parsing of notifications.
C32 jnxPfeNotifyTypeInput	1.3.6.1.4.1.2636.3.44.1.1.2.1.4	Counter32	read-only	Count of notifications whose associated packets were DMA'ed into route processor memory.
C32 jnxPfeNotifyTypeFailed	1.3.6.1.4.1.2636.3.44.1.1.2.1.5	Counter32	read-only	Count of failures in parsing the notifications.
C32 jnxPfeNotifyTypeIgnored	1.3.6.1.4.1.2636.3.44.1.1.2.1.6	Counter32	read-only	Count of notifications where the notification type in the message does not match any of the valid types.
jnxPfeMemoryErrorsTable	1.3.6.1.4.1.2636.3.44.1.1.3		not-accessible	This provides PFE memory errors
jnxPfeMemoryErrorsEntry	1.3.6.1.4.1.2636.3.44.1.1.3.1		not-accessible
I32 jnxPfeFpcSlot	1.3.6.1.4.1.2636.3.44.1.1.3.1.1	Integer32	not-accessible	The FPC slot number for this set of PFE notification
I32 jnxPfeSlot	1.3.6.1.4.1.2636.3.44.1.1.3.1.2	Integer32	not-accessible	The pfe slot number for this set of errors
C64 jnxPfeParityErrors	1.3.6.1.4.1.2636.3.44.1.1.3.1.3	Counter64	read-only	The parity error count
C64 jnxPfeEccErrors	1.3.6.1.4.1.2636.3.44.1.1.3.1.4	Counter64	read-only	The ECC error count
jnxPfeMemory	1.3.6.1.4.1.2636.3.44.1.2
jnxPfeMemoryUkernTable	1.3.6.1.4.1.2636.3.44.1.2.1		not-accessible	This table provides global PFE ukern memory statistics for specified slot.
jnxPfeMemoryUkernEntry	1.3.6.1.4.1.2636.3.44.1.2.1.1		not-accessible	Entry represent ukern memory percentage free.
U32 jnxPfeMemoryUkernFreePercent	1.3.6.1.4.1.2636.3.44.1.2.1.1.2	Unsigned32	read-only	The percent PFE ukern memory free within ukern heap.
jnxPfeMemoryForwardingTable	1.3.6.1.4.1.2636.3.44.1.2.2		not-accessible	This table provides PFE ASIC memory - NH/JTREE or FW/Filter or Encap memory utilization statistics.
jnxPfeMemoryForwardingEntry	1.3.6.1.4.1.2636.3.44.1.2.2.1		not-accessible	Entry represent ASIC memory free percent of a specific type in specified pfe instance
I32 jnxPfeMemoryForwardingChipSlot	1.3.6.1.4.1.2636.3.44.1.2.2.1.1	Integer32	not-accessible	ASIC instance number or pfe complex instance number.
JNX jnxPfeMemoryType	1.3.6.1.4.1.2636.3.44.1.2.2.1.2	JnxPfeMemoryTypeEnum	not-accessible	PFE ASIC memory type, nh = 1, fw = 2, encap = 3.
U32 jnxPfeMemoryForwardingPercentFree	1.3.6.1.4.1.2636.3.44.1.2.2.1.3	Unsigned32	read-only	Percentage ASIC memory free for a specific memory type. For Trio based linecards Encap memory is not available.Hence no value is returned
jnxPfeMemoryTrapVars	1.3.6.1.4.1.2636.3.44.1.2.3			PFE notification object definitions.
U32 jnxPfeGlSlot	1.3.6.1.4.1.2636.3.44.1.2.3.1	Unsigned32	accessible-for-notify	Global slot number for line card resource monitoring.
I32 jnxPfeInstanceNumber	1.3.6.1.4.1.2636.3.44.1.2.3.2	Integer32	accessible-for-notify	PFE instance number in pfe complex.
U32 jnxPfeMemoryThreshold	1.3.6.1.4.1.2636.3.44.1.2.3.3	Unsigned32	accessible-for-notify	Configured high memory utilization threshold.
jnxPfeMemoryNotificationsPrefix	1.3.6.1.4.1.2636.3.44.1.2.4
jnxPfeMemoryNotifications	1.3.6.1.4.1.2636.3.44.1.2.4.0
NTF jnxPfeHeapMemoryThresholdExceeded	1.3.6.1.4.1.2636.3.44.1.2.4.0.1			Indicates that the Heap Memory utilization has crossed the configured watermark.
NTF jnxPfeHeapMemoryThresholdAbated	1.3.6.1.4.1.2636.3.44.1.2.4.0.2			Indicates that the Heap Memory utilization has fallen below the configured watermark.
NTF jnxPfeNextHopMemoryThresholdExceeded	1.3.6.1.4.1.2636.3.44.1.2.4.0.3			Indicates that the Next Hop Memory utilization has crossed the configured watermark.
NTF jnxPfeNextHopMemoryThresholdAbated	1.3.6.1.4.1.2636.3.44.1.2.4.0.4			Indicates that the Next Hop Memory utilization has fallen below the configured watermark.
NTF jnxPfeFilterMemoryThresholdExceeded	1.3.6.1.4.1.2636.3.44.1.2.4.0.5			Indicates that the Filter Memory utilization has crossed the configured watermark.
NTF jnxPfeFilterMemoryThresholdAbated	1.3.6.1.4.1.2636.3.44.1.2.4.0.6			Indicates that the Filter Memory utilization has fallen below the configured watermark.
NTF jnxPfeEncapMemoryThresholdExceeded	1.3.6.1.4.1.2636.3.44.1.2.4.0.7			Indicates that the ENCAP Memory utilization has crossed the configured watermark.
NTF jnxPfeEncapMemoryThresholdAbated	1.3.6.1.4.1.2636.3.44.1.2.4.0.8			Indicates that the ENCAP Memory utilization has fallen below the configured watermark.

RFC description

Provides packet forwarding engine notification statistics, memory errors, and performance data for Juniper routers.

Start monitoring Juniper router (MX/M/T Series, Packet Forwarding Engine memory health) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download JUNIPER-PFE-MIB