All MIBs › VDSL2-LINE-MIB › xdsl2LineCmndConfLdsf
xdsl2LineCmndConfLdsf
Module: VDSL2-LINE-MIB
OID (symbolic): VDSL2-LINE-MIB::xdsl2LineCmndConfLdsf
OID (numeric): 1.3.6.1.2.1.10.251.1.1.1.1.5
Node type: OBJECT-TYPE
Type: Xdsl2LineLdsf
Access: read-write
Description: Loop diagnostic state forced (LDSF). Defines whether the line should be forced into the loop diagnostics mode by the near-end xTU of this line. Note that a loop diagnostic may be initiated by the far-end xTU at any time.
Only when the xdsl2LineStatusPwrMngState object is in the 'l3' state and the xdsl2LineCmndConfPmsf object is in the 'l0orL2toL3' state, can the line be forced into loop diagnostic mode procedures. Upon successful completion of the loop diagnostic mode procedures, the Access Node shall set this object to 'inhibit', and xdsl2LineStatusPwrMngState will remain in the 'l3' state. The loop diagnostic data shall be available at least until xdsl2LineCmndConfPmsf is set to the 'l3toL0' state.
The results of the loop diagnostic procedure are stored in the tables xdsl2SCStatusTable, xdsl2SCStatusBandTable, and xdsl2SCStatusSegmentTable. The status of the loop diagnostic procedure is indicated by xdsl2LineCmndConfLdsfFailReason.
As long as loop diagnostic procedures are not completed successfully, attempts shall be made to do so, until the loop diagnostic mode is no longer forced on the line through this configuration parameter.
What is xdsl2LineCmndConfLdsf?
Forces the line into loop diagnostic mode so the modem measures and populates the xdsl2SCStatusTable/BandTable/SegmentTable results (line attenuation, SNR, Hlog per subcarrier) instead of running Showtime traffic. It only takes effect when the line is already in the L3 idle power state and xdsl2LineCmndConfPmsf is set to 'l0orL2toL3'; once diagnostics finish the agent resets this object to 'inhibit' and xdsl2LineCmndConfLdsfFailReason reports whether it succeeded.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.2.1.10.251.1.1.1.1.5 snmpwalk -v2c -c public <target> VDSL2-LINE-MIB::xdsl2LineCmndConfLdsf
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.2.1.10.251.1.1.1.1.5.1 snmpget -v2c -c public <target> VDSL2-LINE-MIB::xdsl2LineCmndConfLdsf.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.2.1.10.251.1.1.1.1.5.1 s <value>
Start monitoring vendor-neutral, standards-based MIB, DSL access multiplexers (DSLAMs), VDSL2/ADSL modems and routers (line up/down/template/diagnostic status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the VDSL2-LINE-MIB::xdsl2LineCmndConfLdsf OID value, configure state conditions and alerts, and monitor any vendor-neutral, standards-based MIB, DSL access multiplexers (DSLAMs), VDSL2/ADSL modems and routers (line up/down/template/diagnostic status) from a single console.
OID Breakdown
Upper-level ancestors (7 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.2 | mgmt | APERTUS-NPG-MIB |
| 1.3.6.1.2.1 | mib_2 | AXON-MIB |
| 1.3.6.1.2.1.10 | transmission | CHECKPOINT-MIB-2 |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.2.1.10.251 | vdsl2MIB | VDSL2-LINE-MIB |
| 1.3.6.1.2.1.10.251.1 | xdsl2Objects | VDSL2-LINE-MIB |
| 1.3.6.1.2.1.10.251.1.1 | xdsl2Line | VDSL2-LINE-MIB |
| 1.3.6.1.2.1.10.251.1.1.1 | xdsl2LineTable | VDSL2-LINE-MIB |
| 1.3.6.1.2.1.10.251.1.1.1.1 | xdsl2LineEntry | VDSL2-LINE-MIB |
| 1.3.6.1.2.1.10.251.1.1.1.1.5 | xdsl2LineCmndConfLdsf | VDSL2-LINE-MIB |