CISCO-XDSL-LINE-MIB :: cXdslTestTrigger

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CISCO-XDSL-LINE-MIB › cXdslTestTrigger

cXdslTestTrigger

Module: CISCO-XDSL-LINE-MIB

OID (symbolic): CISCO-XDSL-LINE-MIB::cXdslTestTrigger

OID (numeric): 1.3.6.1.4.1.9.9.204.1.2.1.3

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: Starts, stops (aborts) a test in progress or clears the 
test results. The agent will only start a new test, if no
test is active on the targeted port. The value of this
object returns 'ready' when read, the value cannot be set
to 'ready'.
The cXdslTestTrigger value affects cXdslTestStatus as 
following:

     value   current TestStatus -->  new TestStatus
     -----   ------------------      --------------
     start   inactive/pass/fail/     active
             aborted
     stop    active                  aborted
     clear   pass/fail/aborted       inactive

All other combinations will result in error, for instance,
starting a test may fail due to a test already in progress.
Likewise, stopping a test NOT in progress will result in an
error.

The value of cXdslTestType, cXdslTestStatus and cXdslTestTime
will remain in the system until cleared or until the the agent
is reset.
When this object is set to 'clear' the test results are cleared,
cXdslTestType is set to none and cXdslTestStatus is set to
inactive. The 'old' test results will remain until completion
of a 'new' test if test results are not cleared 

What is cXdslTestTrigger?

This read-write object is the actual control lever that starts, stops, or clears a DSL diagnostic test, and per the desc reading it always returns ready(4), a value that can never actually be set. The agent will only honor a start(2) command if no test is currently active on that port. For example, after configuring cXdslTestType and cXdslTestTime, an admin sets cXdslTestTrigger to start(2) to actually launch the test, then later sets it to clear(3) to reset the results before running another.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.204.1.2.1.3
snmpwalk -v2c -c public <target> CISCO-XDSL-LINE-MIB::cXdslTestTrigger

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.204.1.2.1.3.1
snmpget -v2c -c public <target> CISCO-XDSL-LINE-MIB::cXdslTestTrigger.1

Set instance 1 (SNMPv2c):

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

Start monitoring Cisco routers/DSLAMs (xDSL line cards) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-XDSL-LINE-MIB::cXdslTestTrigger OID value, configure state conditions and alerts, and monitor any Cisco routers/DSLAMs (xDSL line cards) from a single console.

OID Breakdown

Upper-level ancestors (8 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.9ciscoCAT2600-MIB
1.3.6.1.4.1.9.9ciscoMgmtCISCO-SMI
Numeric OIDNameModule
1.3.6.1.4.1.9.9.204ciscoXdslLineMIBCISCO-XDSL-LINE-MIB
1.3.6.1.4.1.9.9.204.1ciscoXdslLineMIBObjectsCISCO-XDSL-LINE-MIB
1.3.6.1.4.1.9.9.204.1.2cXdslTestTableCISCO-XDSL-LINE-MIB
1.3.6.1.4.1.9.9.204.1.2.1cXdslTestEntryCISCO-XDSL-LINE-MIB
1.3.6.1.4.1.9.9.204.1.2.1.3cXdslTestTriggerCISCO-XDSL-LINE-MIB