ADSL2-LINE-MIB :: adsl2LineCmndConfLdsfFailReason

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsADSL2-LINE-MIBadsl2LineCmndConfLdsfFailReason

adsl2LineCmndConfLdsfFailReason

Module: ADSL2-LINE-MIB

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

OID (numeric): 1.3.6.1.2.1.10.238.1.1.1.1.5

Node type: OBJECT-TYPE

Type: Adsl2LdsfResult

Access: read-only

Description: The status of the recent occasion the Loop diagnostics mode forced (LDSF) was issued for the associated line. Possible values are: none(1) - The default value in case LDSF was never requested for the associated line. success(2) - The recent command completed successfully. inProgress(3) - The Loop Diagnostics process is in progress. unsupported(4) - The NE or the line card doesn't support LDSF. cannotRun(5) - The NE cannot initiate the command, due to a nonspecific reason. aborted(6) - The Loop Diagnostics process aborted. failed(7) - The Loop Diagnostics process failed. illegalMode(8) - The NE cannot initiate the command, due to the specific mode of the relevant line. adminUp(9) - The NE cannot initiate the command, as the relevant line is administratively 'Up'. tableFull(10) - The NE cannot initiate the command, due to reaching the maximum number of rows in the results table. noResources(11) - The NE cannot initiate the command, due to lack of internal memory resources.

What is adsl2LineCmndConfLdsfFailReason?

This read-only OID reports the outcome of the most recent loop diagnostics command: none (never run), success (completed OK), inProgress (still testing), or unsupported (not available on this line). Engineers check this before retrying diagnostics to understand why the previous attempt failed or to see if the test is still running. For example, if it shows inProgress(3), the modem is still running diagnostics; if success(2), the results are ready to analyze.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.10.238.1.1.1.1.5
snmpwalk -v2c -c public <target> ADSL2-LINE-MIB::adsl2LineCmndConfLdsfFailReason

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.10.238.1.1.1.1.5.1
snmpget -v2c -c public <target> ADSL2-LINE-MIB::adsl2LineCmndConfLdsfFailReason.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::adsl2LineCmndConfLdsfFailReason OID value, configure state conditions and alerts, and monitor any ADSL2/ADSL2+ DSLAMs and CPE modems from a single console.

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.1adsl2LineADSL2-LINE-MIB
1.3.6.1.2.1.10.238.1.1.1adsl2LineTableADSL2-LINE-MIB
1.3.6.1.2.1.10.238.1.1.1.1adsl2LineEntryADSL2-LINE-MIB
1.3.6.1.2.1.10.238.1.1.1.1.5adsl2LineCmndConfLdsfFailReasonADSL2-LINE-MIB