NETI-DTM-MIB :: dtmNodeStatus

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsNETI-DTM-MIBdtmNodeStatus

dtmNodeStatus

Module: NETI-DTM-MIB

OID (symbolic): NETI-DTM-MIB::dtmNodeStatus

OID (numeric): 1.3.6.1.4.1.2928.6.2.4.1.6.1

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: This object describes and controls the control function sub-system on the node.

up(1) The control function sub-system is fully functioning. This is the only state where it is possible to establish new channels. This is the only value possible to write to this object. When writing this value, the control function sub-system is forced to this state, which may result in all established channels to be removed or re-established.

recover(2) The control function sub-system is in the process of recovering the state of all channels after a node or control function sub-system failure, where it is When the process of recovering the channels is completed, the state will change to either up(1) if all channels state were successfully recovered, or limited(3) if the state of any channels failed to be recovered.

limited(3) The control function sub-system is not or has not been able to recover the state of all its channels after a node or control function sub-system failure. The already existing channels through the node may be fully functional, but it is not accepting any channel signaling. All link must be taken down for the control function sub-system to be able to assume a known state, which typically requires operator intervention. This state can be exited by writing up(1) to the object.

noControl(4) The control function sub-system is failing and is not responding. Signaling to the neighboring node is thus not possible. Already existing channels through the node may still be fully functional, but their state is not known. This state can be exited by writing up(1) to the object.

What is dtmNodeStatus?

This both reports and controls the state of the node's control-function sub-system: up (fully functioning, the only value an admin can write), recover (recovering channel state after a failure), limited (recovery incomplete, needs operator intervention), or noControl (control sub-system failing/unresponsive). Writing 'up' forces the sub-system back into service, which may tear down and re-establish all existing channels.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2928.6.2.4.1.6.1
snmpwalk -v2c -c public <target> NETI-DTM-MIB::dtmNodeStatus

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2928.6.2.4.1.6.1.1
snmpget -v2c -c public <target> NETI-DTM-MIB::dtmNodeStatus.1

Set instance 1 (SNMPv2c):

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

Start monitoring Net Insight DTM network elements with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the NETI-DTM-MIB::dtmNodeStatus OID value, configure state conditions and alerts, and monitor any Net Insight DTM network elements from a single console.

OID Breakdown

Upper-level ancestors (9 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.2928netinsightNETI-COMMON-MIB
1.3.6.1.4.1.2928.6netiExperimentalNETI-COMMON-MIB
1.3.6.1.4.1.2928.6.2netiExperimentalGenericNETI-COMMON-MIB
Numeric OIDNameModule
1.3.6.1.4.1.2928.6.2.4netiDTMMIBNETI-DTM-MIB
1.3.6.1.4.1.2928.6.2.4.1netiDTMMIBObjectsNETI-DTM-MIB
1.3.6.1.4.1.2928.6.2.4.1.6dtmNodeGroupNETI-DTM-MIB
1.3.6.1.4.1.2928.6.2.4.1.6.1dtmNodeStatusNETI-DTM-MIB