PDN-ADSL-LINE-EXT-MIB :: pdnAdslLineLdsf

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › PDN-ADSL-LINE-EXT-MIB › pdnAdslLineLdsf

pdnAdslLineLdsf

Module: PDN-ADSL-LINE-EXT-MIB

OID (symbolic): PDN-ADSL-LINE-EXT-MIB::pdnAdslLineLdsf

OID (numeric): 1.3.6.1.4.1.1795.2.24.2.6.24.1.1.1.10

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: Defines whether the line should be forced into the loop diagnostics mode by the near-end ATU on this line. ldsfMode0(1) - 0: Inhibits the near-end ATU from performing loop diagnostics mode procedures on the line. Loop diagnostic mode procedures may still be initiated by the far-end ATU. ldsModef1(2) - 1: Forces the near-end ATU to perform the loop diagnostics procedures.

The line needs to be forced to the L3 state (idle state) before it can be forced to the loop diagnostics mode. Only while the line power management state is the L3 state, the line can be forced into the loop diagnostics mode procedures.

The following are ways to force the line to the L3 state: (1) Set the ifAdminStatus to down.

When the loop diagnostics mode procedures are completed successfully, this object shall reset to ldsf0 and the line shall return to and remain in the L3 idle state. The loop diagnostics data shall be available at least until the line is forced to the L0 state. If the loop diagnostics procedures can't be completed successfully, then an Initialization Failure occurs. As long as loop diagnostics procedures are not completed successfully, attempts shall be made to do so, until the loop diagnostics mode is no longer forced on the line through this configuration parameter.

What is pdnAdslLineLdsf?

Forces or inhibits the near-end ATU from running loop diagnostics on this line: ldsfMode0(1) inhibits it (though the far end can still initiate diagnostics), while ldsfMode1(2) forces the near end to run them; the line must first be idled (L3) before this takes effect, and the object auto-resets to ldsfMode0 once diagnostics complete.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1795.2.24.2.6.24.1.1.1.10
snmpwalk -v2c -c public <target> PDN-ADSL-LINE-EXT-MIB::pdnAdslLineLdsf

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.1795.2.24.2.6.24.1.1.1.10.1
snmpget -v2c -c public <target> PDN-ADSL-LINE-EXT-MIB::pdnAdslLineLdsf.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.1795.2.24.2.6.24.1.1.1.10.1 i <value>

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> pdnAdslLineLdsf.1

Start monitoring Paradyne/Zhone ADSL2/ADSL2+ DSLAM and access equipment with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the PDN-ADSL-LINE-EXT-MIB::pdnAdslLineLdsf OID value, configure state conditions and alerts, and monitor any Paradyne/Zhone ADSL2/ADSL2+ DSLAM and access equipment from a single console.

OID Breakdown

Upper-level ancestors (11 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.1795pdynPDN-HEADER-MIB
1.3.6.1.4.1.1795.2pdn_mgmtPDN-HEADER-MIB
1.3.6.1.4.1.1795.2.24paradynePDN-HEADER-MIB
1.3.6.1.4.1.1795.2.24.2pdn_commonPDN-HEADER-MIB
1.3.6.1.4.1.1795.2.24.2.6pdn_interfacesPDN-HEADER-MIB
Numeric OIDNameModule
1.3.6.1.4.1.1795.2.24.2.6.24pdnAdslLineExtMIBPDN-ADSL-LINE-EXT-MIB
1.3.6.1.4.1.1795.2.24.2.6.24.1pdnAdslLineExtObjectsPDN-ADSL-LINE-EXT-MIB
1.3.6.1.4.1.1795.2.24.2.6.24.1.1pdnAdslLineExtTablePDN-ADSL-LINE-EXT-MIB
1.3.6.1.4.1.1795.2.24.2.6.24.1.1.1pdnAdslLineExtEntryPDN-ADSL-LINE-EXT-MIB
1.3.6.1.4.1.1795.2.24.2.6.24.1.1.1.10pdnAdslLineLdsfPDN-ADSL-LINE-EXT-MIB