ADSL2-LINE-MIB :: adsl2PMLCurr15MFecs

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsADSL2-LINE-MIBadsl2PMLCurr15MFecs

adsl2PMLCurr15MFecs

Module: ADSL2-LINE-MIB

OID (symbolic): ADSL2-LINE-MIB::adsl2PMLCurr15MFecs

OID (numeric): 1.3.6.1.2.1.10.238.1.4.1.1.1.5

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Count of seconds during this interval where there was at least one FEC correction event for one or more bearer channels in this line. This parameter is inhibited during UAS or SES.

What is adsl2PMLCurr15MFecs?

This read-only counter measures how many seconds in the current 15-minute window experienced FEC (Forward Error Correction) activity on any bearer channel, indicating the modem is actively correcting errors. A moderate count is normal, but a count approaching 900 (all 15 minutes) signals a failing line. For example, a value of 120 means FEC was active for 120 out of 900 seconds (about 13% of the interval), suggesting noticeable line stress.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.10.238.1.4.1.1.1.5
snmpwalk -v2c -c public <target> ADSL2-LINE-MIB::adsl2PMLCurr15MFecs

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.10.238.1.4.1.1.1.5.1
snmpget -v2c -c public <target> ADSL2-LINE-MIB::adsl2PMLCurr15MFecs.1

Start monitoring ADSL2/ADSL2+ DSLAMs and CPE modems with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ADSL2-LINE-MIB::adsl2PMLCurr15MFecs OID value, configure state conditions and alerts, and monitor any ADSL2/ADSL2+ DSLAMs and CPE modems from a single console.

How to Use in IPNetwork Monitor

Select an ADSL2/ADSL2+ DSLAM or CPE modem 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 adsl2PMLCurr15MFecs 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 seconds during this interval where there was at least one FEC correction event for one or more bearer channels in this line. 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 (in seconds), 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.

OID Breakdown

Upper-level ancestors (7 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
1.3.6.1.2.1.10transmissionCHECKPOINT-MIB-2
Numeric OIDNameModule
1.3.6.1.2.1.10.238adsl2MIBADSL2-LINE-MIB
1.3.6.1.2.1.10.238.1adsl2ADSL2-LINE-MIB
1.3.6.1.2.1.10.238.1.4adsl2PMADSL2-LINE-MIB
1.3.6.1.2.1.10.238.1.4.1adsl2PMLineADSL2-LINE-MIB
1.3.6.1.2.1.10.238.1.4.1.1adsl2PMLineCurrTableADSL2-LINE-MIB
1.3.6.1.2.1.10.238.1.4.1.1.1adsl2PMLineCurrEntryADSL2-LINE-MIB
1.3.6.1.2.1.10.238.1.4.1.1.1.5adsl2PMLCurr15MFecsADSL2-LINE-MIB