EFM-CU-MIB :: efmCuPAFInErrors

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsEFM-CU-MIBefmCuPAFInErrors

efmCuPAFInErrors

Module: EFM-CU-MIB

OID (symbolic): EFM-CU-MIB::efmCuPAFInErrors

OID (numeric): 1.3.6.1.2.1.167.1.1.3.1.4

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The number of fragments that have been received across the gamma interface with RxErr asserted and discarded. This read-only counter is inactive (not incremented) when the PAF is unsupported or disabled. Upon disabling the PAF, the counter retains its previous value.

If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the 10P/2B PAF RX error register.

Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, defined in IF-MIB.

What is efmCuPAFInErrors?

This read-only counter tracks fragments received across the gamma interface with a receive-error flag set that had to be discarded, and it only increments while PAF (PME aggregation) is active. Rising values point to problems in the bonding/fragmentation layer specifically, distinct from ordinary line errors, and like other IF-MIB-style counters it can reset on device reinitialization.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.167.1.1.3.1.4
snmpwalk -v2c -c public <target> EFM-CU-MIB::efmCuPAFInErrors

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.167.1.1.3.1.4.1
snmpget -v2c -c public <target> EFM-CU-MIB::efmCuPAFInErrors.1

Start monitoring DSLAM/EFM access multiplexer or CPE (802.3ah EFM Copper, vendor-neutral IETF standard) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the EFM-CU-MIB::efmCuPAFInErrors OID value, configure state conditions and alerts, and monitor any DSLAM/EFM access multiplexer or CPE (802.3ah EFM Copper, vendor-neutral IETF standard) from a single console.

How to Use in IPNetwork Monitor

Select a DSLAM/EFM access multiplexer or CPE (802.3ah EFM Copper, vendor-neutral IETF standard) 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 efmCuPAFInErrors 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. The number of fragments that have been received across the gamma interface with RxErr asserted and discarded. 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 (6 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.2mgmtAXON-MIB
1.3.6.1.2.1mib_2AXON-MIB
Numeric OIDNameModule
1.3.6.1.2.1.167efmCuMIBEFM-CU-MIB
1.3.6.1.2.1.167.1efmCuObjectsEFM-CU-MIB
1.3.6.1.2.1.167.1.1efmCuPortEFM-CU-MIB
1.3.6.1.2.1.167.1.1.3efmCuPortStatusTableEFM-CU-MIB
1.3.6.1.2.1.167.1.1.3.1efmCuPortStatusEntryEFM-CU-MIB
1.3.6.1.2.1.167.1.1.3.1.4efmCuPAFInErrorsEFM-CU-MIB