OID reference

dtmNodeStatus

1.3.6.1.4.1.2928.6.2.4.1.6.1

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-s…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.2928.6.2.4.1.6 (dtmNodeGroup)
Node code
1
Node name
dtmNodeStatus
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.2928.6.2.4.1.6.1
URN notation
urn:oid:1.3.6.1.4.1.2928.6.2.4.1.6.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 2928 6 2 4 1 6 1}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) netinsight(2928) netiExperimental(6) netiExperimentalGeneric(2) netiDTMMIB(4) netiDTMMIBObjects(1) dtmNodeGroup(6) dtmNodeStatus(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) netinsight(2928) netiExperimental(6) netiExperimentalGeneric(2) netiDTMMIB(4) netiDTMMIBObjects(1) dtmNodeGroup(6) dtmNodeStatus(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) netinsight(2928) netiExperimental(6) netiExperimentalGeneric(2) netiDTMMIB(4) netiDTMMIBObjects(1) dtmNodeGroup(6) dtmNodeStatus(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) netinsight(2928) netiExperimental(6) netiExperimentalGeneric(2) netiDTMMIB(4) netiDTMMIBObjects(1) dtmNodeGroup(6) dtmNodeStatus(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) netinsight(2928) netiExperimental(6) netiExperimentalGeneric(2) netiDTMMIB(4) netiDTMMIBObjects(1) dtmNodeGroup(6) dtmNodeStatus(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) netinsight(2928) netiExperimental(6) netiExperimentalGeneric(2) netiDTMMIB(4) netiDTMMIBObjects(1) dtmNodeGroup(6) dtmNodeStatus(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) netinsight(2928) netiExperimental(6) netiExperimentalGeneric(2) netiDTMMIB(4) netiDTMMIBObjects(1) dtmNodeGroup(6) dtmNodeStatus(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) netinsight(2928) netiExperimental(6) netiExperimentalGeneric(2) netiDTMMIB(4) netiDTMMIBObjects(1) dtmNodeGroup(6) dtmNodeStatus(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) netinsight(2928) netiExperimental(6) netiExperimentalGeneric(2) netiDTMMIB(4) netiDTMMIBObjects(1) dtmNodeGroup(6) dtmNodeStatus(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) netinsight(2928) netiExperimental(6) netiExperimentalGeneric(2) netiDTMMIB(4) netiDTMMIBObjects(1) dtmNodeGroup(6) dtmNodeStatus(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) netinsight(2928) netiExperimental(6) netiExperimentalGeneric(2) netiDTMMIB(4) netiDTMMIBObjects(1) dtmNodeGroup(6) dtmNodeStatus(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) netinsight(2928) netiExperimental(6) netiExperimentalGeneric(2) netiDTMMIB(4) netiDTMMIBObjects(1) dtmNodeGroup(6) dtmNodeStatus(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) netinsight(2928) netiExperimental(6) netiExperimentalGeneric(2) netiDTMMIB(4) netiDTMMIBObjects(1) dtmNodeGroup(6) dtmNodeStatus(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) netinsight(2928) netiExperimental(6) netiExperimentalGeneric(2) netiDTMMIB(4) netiDTMMIBObjects(1) dtmNodeGroup(6) dtmNodeStatus(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) netinsight(2928) netiExperimental(6) netiExperimentalGeneric(2) netiDTMMIB(4) netiDTMMIBObjects(1) dtmNodeGroup(6) dtmNodeStatus(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) netinsight(2928) netiExperimental(6) netiExperimentalGeneric(2) netiDTMMIB(4) netiDTMMIBObjects(1) dtmNodeGroup(6) dtmNodeStatus(1)}
OID-IRI notation
  • /1/3/6/1/4/1/2928/6/2/4/1/6/1
  • /ISO/Identified-Organization/6/1/4/1/2928/6/2/4/1/6/1
  • /ISO/3/6/1/4/1/2928/6/2/4/1/6/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/2928/netiExperimental/netiExperimentalGeneric/netiDTMMIB/netiDTMMIBObjects/dtmNodeGroup/dtmNodeStatus
  • /iso/identified-organization/dod/internet/private/enterprise/netinsight/netiExperimental/netiExperimentalGeneric/netiDTMMIB/netiDTMMIBObjects/dtmNodeGroup/dtmNodeStatus
  • /iso/identified-organization/dod/internet/private/enterprises/2928/netiExperimental/netiExperimentalGeneric/netiDTMMIB/netiDTMMIBObjects/dtmNodeGroup/dtmNodeStatus
  • /iso/identified-organization/dod/internet/private/enterprises/netinsight/netiExperimental/netiExperimentalGeneric/netiDTMMIB/netiDTMMIBObjects/dtmNodeGroup/dtmNodeStatus
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/2928/netiExperimental/netiExperimentalGeneric/netiDTMMIB/netiDTMMIBObjects/dtmNodeGroup/dtmNodeStatus
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/netinsight/netiExperimental/netiExperimentalGeneric/netiDTMMIB/netiDTMMIBObjects/dtmNodeGroup/dtmNodeStatus
  • /iso/identified-organization/dod/internet/private/vendor-objects/2928/netiExperimental/netiExperimentalGeneric/netiDTMMIB/netiDTMMIBObjects/dtmNodeGroup/dtmNodeStatus
  • /iso/identified-organization/dod/internet/private/vendor-objects/netinsight/netiExperimental/netiExperimentalGeneric/netiDTMMIB/netiDTMMIBObjects/dtmNodeGroup/dtmNodeStatus
  • /iso/org/dod/internet/private/enterprise/2928/netiExperimental/netiExperimentalGeneric/netiDTMMIB/netiDTMMIBObjects/dtmNodeGroup/dtmNodeStatus
  • /iso/org/dod/internet/private/enterprise/netinsight/netiExperimental/netiExperimentalGeneric/netiDTMMIB/netiDTMMIBObjects/dtmNodeGroup/dtmNodeStatus
  • /iso/org/dod/internet/private/enterprises/2928/netiExperimental/netiExperimentalGeneric/netiDTMMIB/netiDTMMIBObjects/dtmNodeGroup/dtmNodeStatus
  • /iso/org/dod/internet/private/enterprises/netinsight/netiExperimental/netiExperimentalGeneric/netiDTMMIB/netiDTMMIBObjects/dtmNodeGroup/dtmNodeStatus
  • /iso/org/dod/internet/private/ldap-enterprise/2928/netiExperimental/netiExperimentalGeneric/netiDTMMIB/netiDTMMIBObjects/dtmNodeGroup/dtmNodeStatus
  • /iso/org/dod/internet/private/ldap-enterprise/netinsight/netiExperimental/netiExperimentalGeneric/netiDTMMIB/netiDTMMIBObjects/dtmNodeGroup/dtmNodeStatus
  • /iso/org/dod/internet/private/vendor-objects/2928/netiExperimental/netiExperimentalGeneric/netiDTMMIB/netiDTMMIBObjects/dtmNodeGroup/dtmNodeStatus
  • /iso/org/dod/internet/private/vendor-objects/netinsight/netiExperimental/netiExperimentalGeneric/netiDTMMIB/netiDTMMIBObjects/dtmNodeGroup/dtmNodeStatus
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
current

Enumerated values

ValueName
1up
2recover
3limited
4noControl

Using this OID with SNMP

At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.

snmpget [connection options] DEVICE .1.3.6.1.4.1.2928.6.2.4.1.6.1.0

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

The displayed source records contain one distinct definition. Compare its source records.

dtmNodeStatus OBJECT-TYPE
    SYNTAX      INTEGER {
                    up(1),
                    recover(2),
                    limited(3),
                    noControl(4) }
    MAX-ACCESS  read-write
    STATUS      current
    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."
    ::= { dtmNodeGroup 1 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

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.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

dtmNodeStatus · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: dtmNodeStatus

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dtmNodeStatus",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "up",
    "(",
    "1",
    ")",
    ",",
    "recover",
    "(",
    "2",
    ")",
    ",",
    "limited",
    "(",
    "3",
    ")",
    ",",
    "noControl",
    "(",
    "4",
    ")",
    "}",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "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.\"",
    "::=",
    "{",
    "dtmNodeGroup",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "up",
            1
          ],
          [
            "recover",
            2
          ],
          [
            "limited",
            3
          ],
          [
            "noControl",
            4
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "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."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.2928)

Carlsson Martin

Siblings (2)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.2928.6.2.4.1.6.2 dtmNodeRestartOnError00
1.3.6.1.4.1.2928.6.2.4.1.6.3 dtmNodeId00