OID reference

fsRstDebugOption

1.3.6.1.4.1.2076.79.1.4

Description

This object is used to enable Debug Statements in the RSTP Module. A FOUR BYTE integer is used for enabling the level of debugging. Each BIT in the four byte integer represents a particular level of Debug. The mapping between the bit positions & the level of debug is as follows: 0 - Init and Shutdown Debug statements …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.2076.79.1 (dot1wFutureRst)
Node code
4
Node name
fsRstDebugOption
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.2076.79.1.4
URN notation
urn:oid:1.3.6.1.4.1.2076.79.1.4
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 2076 79 1 4}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 2076 futureRstMIB(79) dot1wFutureRst(1) fsRstDebugOption(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 2076 futureRstMIB(79) dot1wFutureRst(1) fsRstDebugOption(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 futureRstMIB(79) dot1wFutureRst(1) fsRstDebugOption(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 futureRstMIB(79) dot1wFutureRst(1) fsRstDebugOption(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) 2076 futureRstMIB(79) dot1wFutureRst(1) fsRstDebugOption(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) 2076 futureRstMIB(79) dot1wFutureRst(1) fsRstDebugOption(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 futureRstMIB(79) dot1wFutureRst(1) fsRstDebugOption(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 futureRstMIB(79) dot1wFutureRst(1) fsRstDebugOption(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 2076 futureRstMIB(79) dot1wFutureRst(1) fsRstDebugOption(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 2076 futureRstMIB(79) dot1wFutureRst(1) fsRstDebugOption(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 futureRstMIB(79) dot1wFutureRst(1) fsRstDebugOption(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 futureRstMIB(79) dot1wFutureRst(1) fsRstDebugOption(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) 2076 futureRstMIB(79) dot1wFutureRst(1) fsRstDebugOption(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) 2076 futureRstMIB(79) dot1wFutureRst(1) fsRstDebugOption(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 futureRstMIB(79) dot1wFutureRst(1) fsRstDebugOption(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 futureRstMIB(79) dot1wFutureRst(1) fsRstDebugOption(4)}
OID-IRI notation
  • /1/3/6/1/4/1/2076/79/1/4
  • /ISO/Identified-Organization/6/1/4/1/2076/79/1/4
  • /ISO/3/6/1/4/1/2076/79/1/4
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/2076/futureRstMIB/dot1wFutureRst/fsRstDebugOption
  • /iso/identified-organization/dod/internet/private/enterprises/2076/futureRstMIB/dot1wFutureRst/fsRstDebugOption
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/2076/futureRstMIB/dot1wFutureRst/fsRstDebugOption
  • /iso/identified-organization/dod/internet/private/vendor-objects/2076/futureRstMIB/dot1wFutureRst/fsRstDebugOption
  • /iso/org/dod/internet/private/enterprise/2076/futureRstMIB/dot1wFutureRst/fsRstDebugOption
  • /iso/org/dod/internet/private/enterprises/2076/futureRstMIB/dot1wFutureRst/fsRstDebugOption
  • /iso/org/dod/internet/private/ldap-enterprise/2076/futureRstMIB/dot1wFutureRst/fsRstDebugOption
  • /iso/org/dod/internet/private/vendor-objects/2076/futureRstMIB/dot1wFutureRst/fsRstDebugOption
  • /iso/iso-identified-organization/dod/internet/private/enterprise/2076/futureRstMIB/dot1wFutureRst/fsRstDebugOption
  • /iso/iso-identified-organization/dod/internet/private/enterprises/2076/futureRstMIB/dot1wFutureRst/fsRstDebugOption
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/2076/futureRstMIB/dot1wFutureRst/fsRstDebugOption
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/2076/futureRstMIB/dot1wFutureRst/fsRstDebugOption
  • /iso/iso-organization/dod/internet/private/enterprise/2076/futureRstMIB/dot1wFutureRst/fsRstDebugOption
  • /iso/iso-organization/dod/internet/private/enterprises/2076/futureRstMIB/dot1wFutureRst/fsRstDebugOption
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/2076/futureRstMIB/dot1wFutureRst/fsRstDebugOption
  • /iso/iso-organization/dod/internet/private/vendor-objects/2076/futureRstMIB/dot1wFutureRst/fsRstDebugOption

SNMP properties

Value type
Integer32
Maximum access defined by MIB
read-write
Status in MIB
current
Default value
0
Allowed ranges
0–524287

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.2076.79.1.4.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.

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

fsRstDebugOption · current

fsRstDebugOption OBJECT-TYPE
   SYNTAX      Integer32 (0..524287)
   MAX-ACCESS  read-write
   STATUS      current
   DESCRIPTION
      "This object is used to enable Debug Statements in the RSTP
      Module.

      A FOUR BYTE integer is used for enabling the level of debugging. 
      Each BIT in the four byte integer represents a particular 
      level of Debug. 

      The mapping between the bit positions & the level of debug is 
      as follows: 
      0 - Init and Shutdown Debug statements
      1 - Management Debug statements
      2 - Memory related Debug statements
      3 - BPDU related Debug statements
      4 - Event Handling Debug statements
      5 - Timer Module Debug statements
      6 - Port Information SEM Debug statements
      7 - Port Receive SEM Debug statements
      8 - Role Selection SEM Debug statements
      9 - Role Transition SEM Debug statements
     10 - State Transition SEM Debug statements
     11 - Protocol Migration SEM Debug statements
     12 - Topology Change SEM Debug statements
     13 - Port Transmit SEM Debug statements
     14 - Bridge Detection SEM Debug statements
     15 - All Failure Debug statements
     16 - Redundancy code flow Debug statements
     17 - State Machine variable changes Debug statements
     18 - Port Receive Pseudo Information SEM Debug statements

      The remaining bits are unused. Combination of debug levels are 
      also allowed.

      For example if the bits 0 and 1 are set, then the Debug
      statements related to Init-Shutdown and management 
      will be printed.

      The user has to enter the corresponding INTEGER VALUE for the
      bits set. For example if bits 0 and 1 are to be set, then user has
      to give the value for this object as 3.
      
      Setting the Debug Option to any value will cause the Trace Option
      to be set to 0 (i.e.) the Trace Option and Debug Option are mutually
      exclusive."
      DEFVAL  { 0 }
   ::= { dot1wFutureRst 4 }

fsRstDebugOption · current

fsRstDebugOption OBJECT-TYPE
   SYNTAX      Integer32 (0..524287)
   MAX-ACCESS  read-write
   STATUS      current
   DESCRIPTION
      "This object is used to enable Debug Statements in the RSTP
      Module.

      A FOUR BYTE integer is used for enabling the level of debugging. 
      Each BIT in the four byte integer, represents a particular 
      level of Debug. 

      The mapping between the bit positions & the level of debug is 
      as follows: 
      0 - Init and Shutdown Debug statements
      1 - Management Debug statements
      2 - Memory related Debug statements
      3 - BPDU related Debug statements
      4 - Event Handling Debug statements
      5 - Timer Module Debug statements
      6 - Port Information SEM Debug statements
      7 - Port Receive SEM Debug statements
      8 - Role Selection SEM Debug statements
      9 - Role Transition SEM Debug statements
     10 - State Transition SEM Debug statements
     11 - Protocol Migration SEM Debug statements
     12 - Topology Change SEM Debug statements
     13 - Port Transmit SEM Debug statements
     14 - Bridge Detection SEM Debug statements
     15 - All Failure Debug statements
     16 - Redundancy code flow Debug statements
     17 - State Machine variable changes Debug statements
     18 - Port Receive Pseudo Information SEM Debug statements

      The remaining bits are unused. Combination of debug levels are 
      also allowed.

      For example if the bits 0 and 1 are set, then the Debug
      statements related to Init-Shutdown and management 
      will be printed.

      The user has to enter the corresponding INTEGER VALUE for the
      bits set. For example if bits 0 and 1 are to be set then user has
      to give the value for this object as 3.
      
      Setting the Debug Option to any value will cause the Trace Option
      to be set to 0 (i.e.) the Trace Option and Debug Option are mutually
      exclusive."
      DEFVAL  { 0 }
   ::= { dot1wFutureRst 4 }

Meaning

Descriptions

2 unique

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

Description 1

This object is used to enable Debug Statements in the RSTP Module. A FOUR BYTE integer is used for enabling the level of debugging. Each BIT in the four byte integer represents a particular level of Debug. The mapping between the bit positions & the level of debug is as follows: 0 - Init and Shutdown Debug statements 1 - Management Debug statements 2 - Memory related Debug statements 3 - BPDU related Debug statements 4 - Event Handling Debug statements 5 - Timer Module Debug statements 6 - Port Information SEM Debug statements 7 - Port Receive SEM Debug statements 8 - Role Selection SEM Debug statements 9 - Role Transition SEM Debug statements 10 - State Transition SEM Debug statements 11 - Protocol Migration SEM Debug statements 12 - Topology Change SEM Debug statements 13 - Port Transmit SEM Debug statements 14 - Bridge Detection SEM Debug statements 15 - All Failure Debug statements 16 - Redundancy code flow Debug statements 17 - State Machine variable changes Debug statements 18 - Port Receive Pseudo Information SEM Debug statements The remaining bits are unused. Combination of debug levels are also allowed. For example if the bits 0 and 1 are set, then the Debug statements related to Init-Shutdown and management will be printed. The user has to enter the corresponding INTEGER VALUE for the bits set. For example if bits 0 and 1 are to be set, then user has to give the value for this object as 3. Setting the Debug Option to any value will cause the Trace Option to be set to 0 (i.e.) the Trace Option and Debug Option are mutually exclusive.

Sources for this description

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

See 1 matching source record

Description 2

This object is used to enable Debug Statements in the RSTP Module. A FOUR BYTE integer is used for enabling the level of debugging. Each BIT in the four byte integer, represents a particular level of Debug. The mapping between the bit positions & the level of debug is as follows: 0 - Init and Shutdown Debug statements 1 - Management Debug statements 2 - Memory related Debug statements 3 - BPDU related Debug statements 4 - Event Handling Debug statements 5 - Timer Module Debug statements 6 - Port Information SEM Debug statements 7 - Port Receive SEM Debug statements 8 - Role Selection SEM Debug statements 9 - Role Transition SEM Debug statements 10 - State Transition SEM Debug statements 11 - Protocol Migration SEM Debug statements 12 - Topology Change SEM Debug statements 13 - Port Transmit SEM Debug statements 14 - Bridge Detection SEM Debug statements 15 - All Failure Debug statements 16 - Redundancy code flow Debug statements 17 - State Machine variable changes Debug statements 18 - Port Receive Pseudo Information SEM Debug statements The remaining bits are unused. Combination of debug levels are also allowed. For example if the bits 0 and 1 are set, then the Debug statements related to Init-Shutdown and management will be printed. The user has to enter the corresponding INTEGER VALUE for the bits set. For example if bits 0 and 1 are to be set then user has to give the value for this object as 3. Setting the Debug Option to any value will cause the Trace Option to be set to 0 (i.e.) the Trace Option and Debug Option are mutually exclusive.

Sources for this description

Belden, GarrettCom and Hirschmann IT official standalone MIBs

See 1 matching source record

Evidence

Source records

2 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

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

Status in source: current.

Names: fsRstDebugOption

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsRstDebugOption",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "(",
    "0",
    ".",
    ".",
    "524287",
    ")",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This object is used to enable Debug Statements in the RSTP Module. A FOUR BYTE integer is used for enabling the level of debugging. Each BIT in the four byte integer represents a particular level of Debug. The mapping between the bit positions & the level of debug is as follows: 0 - Init and Shutdown Debug statements 1 - Management Debug statements 2 - Memory related Debug statements 3 - BPDU related Debug statements 4 - Event Handling Debug statements 5 - Timer Module Debug statements 6 - Port Information SEM Debug statements 7 - Port Receive SEM Debug statements 8 - Role Selection SEM Debug statements 9 - Role Transition SEM Debug statements 10 - State Transition SEM Debug statements 11 - Protocol Migration SEM Debug statements 12 - Topology Change SEM Debug statements 13 - Port Transmit SEM Debug statements 14 - Bridge Detection SEM Debug statements 15 - All Failure Debug statements 16 - Redundancy code flow Debug statements 17 - State Machine variable changes Debug statements 18 - Port Receive Pseudo Information SEM Debug statements The remaining bits are unused. Combination of debug levels are also allowed. For example if the bits 0 and 1 are set, then the Debug statements related to Init-Shutdown and management will be printed. The user has to enter the corresponding INTEGER VALUE for the bits set. For example if bits 0 and 1 are to be set, then user has to give the value for this object as 3. Setting the Debug Option to any value will cause the Trace Option to be set to 0 (i.e.) the Trace Option and Debug Option are mutually exclusive.\"",
    "DEFVAL",
    "{",
    "0",
    "}",
    "::=",
    "{",
    "dot1wFutureRst",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32",
      [
        "integerSubType",
        [
          [
            0,
            524287
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This object is used to enable Debug Statements in the RSTP Module. A FOUR BYTE integer is used for enabling the level of debugging. Each BIT in the four byte integer represents a particular level of Debug. The mapping between the bit positions & the level of debug is as follows: 0 - Init and Shutdown Debug statements 1 - Management Debug statements 2 - Memory related Debug statements 3 - BPDU related Debug statements 4 - Event Handling Debug statements 5 - Timer Module Debug statements 6 - Port Information SEM Debug statements 7 - Port Receive SEM Debug statements 8 - Role Selection SEM Debug statements 9 - Role Transition SEM Debug statements 10 - State Transition SEM Debug statements 11 - Protocol Migration SEM Debug statements 12 - Topology Change SEM Debug statements 13 - Port Transmit SEM Debug statements 14 - Bridge Detection SEM Debug statements 15 - All Failure Debug statements 16 - Redundancy code flow Debug statements 17 - State Machine variable changes Debug statements 18 - Port Receive Pseudo Information SEM Debug statements The remaining bits are unused. Combination of debug levels are also allowed. For example if the bits 0 and 1 are set, then the Debug statements related to Init-Shutdown and management will be printed. The user has to enter the corresponding INTEGER VALUE for the bits set. For example if bits 0 and 1 are to be set, then user has to give the value for this object as 3. Setting the Debug Option to any value will cause the Trace Option to be set to 0 (i.e.) the Trace Option and Debug Option are mutually exclusive."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      0
    ]
  ]
}
Records for description 2Belden, GarrettCom and Hirschmann IT official standalone MIBs1 record · 1 source

Description 2

fsRstDebugOption · currentBelden, GarrettCom and Hirschmann IT official standalone MIBs1 source

Status in source: current.

Names: fsRstDebugOption

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsRstDebugOption",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "(",
    "0",
    ".",
    ".",
    "524287",
    ")",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This object is used to enable Debug Statements in the RSTP Module. A FOUR BYTE integer is used for enabling the level of debugging. Each BIT in the four byte integer, represents a particular level of Debug. The mapping between the bit positions & the level of debug is as follows: 0 - Init and Shutdown Debug statements 1 - Management Debug statements 2 - Memory related Debug statements 3 - BPDU related Debug statements 4 - Event Handling Debug statements 5 - Timer Module Debug statements 6 - Port Information SEM Debug statements 7 - Port Receive SEM Debug statements 8 - Role Selection SEM Debug statements 9 - Role Transition SEM Debug statements 10 - State Transition SEM Debug statements 11 - Protocol Migration SEM Debug statements 12 - Topology Change SEM Debug statements 13 - Port Transmit SEM Debug statements 14 - Bridge Detection SEM Debug statements 15 - All Failure Debug statements 16 - Redundancy code flow Debug statements 17 - State Machine variable changes Debug statements 18 - Port Receive Pseudo Information SEM Debug statements The remaining bits are unused. Combination of debug levels are also allowed. For example if the bits 0 and 1 are set, then the Debug statements related to Init-Shutdown and management will be printed. The user has to enter the corresponding INTEGER VALUE for the bits set. For example if bits 0 and 1 are to be set then user has to give the value for this object as 3. Setting the Debug Option to any value will cause the Trace Option to be set to 0 (i.e.) the Trace Option and Debug Option are mutually exclusive.\"",
    "DEFVAL",
    "{",
    "0",
    "}",
    "::=",
    "{",
    "dot1wFutureRst",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32",
      [
        "integerSubType",
        [
          [
            0,
            524287
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This object is used to enable Debug Statements in the RSTP Module. A FOUR BYTE integer is used for enabling the level of debugging. Each BIT in the four byte integer, represents a particular level of Debug. The mapping between the bit positions & the level of debug is as follows: 0 - Init and Shutdown Debug statements 1 - Management Debug statements 2 - Memory related Debug statements 3 - BPDU related Debug statements 4 - Event Handling Debug statements 5 - Timer Module Debug statements 6 - Port Information SEM Debug statements 7 - Port Receive SEM Debug statements 8 - Role Selection SEM Debug statements 9 - Role Transition SEM Debug statements 10 - State Transition SEM Debug statements 11 - Protocol Migration SEM Debug statements 12 - Topology Change SEM Debug statements 13 - Port Transmit SEM Debug statements 14 - Bridge Detection SEM Debug statements 15 - All Failure Debug statements 16 - Redundancy code flow Debug statements 17 - State Machine variable changes Debug statements 18 - Port Receive Pseudo Information SEM Debug statements The remaining bits are unused. Combination of debug levels are also allowed. For example if the bits 0 and 1 are set, then the Debug statements related to Init-Shutdown and management will be printed. The user has to enter the corresponding INTEGER VALUE for the bits set. For example if bits 0 and 1 are to be set then user has to give the value for this object as 3. Setting the Debug Option to any value will cause the Trace Option to be set to 0 (i.e.) the Trace Option and Debug Option are mutually exclusive."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      0
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.2076)

Division Products

Siblings (20)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.2076.79.1.1 fsRstSystemControl00
1.3.6.1.4.1.2076.79.1.2 fsRstModuleStatus00
1.3.6.1.4.1.2076.79.1.3 fsRstTraceOption00
1.3.6.1.4.1.2076.79.1.5 fsRstRstpUpCount00
1.3.6.1.4.1.2076.79.1.6 fsRstRstpDownCount00
1.3.6.1.4.1.2076.79.1.7 fsRstBufferFailureCount00
1.3.6.1.4.1.2076.79.1.8 fsRstMemAllocFailureCount00
1.3.6.1.4.1.2076.79.1.9 fsRstNewRootIdCount00
1.3.6.1.4.1.2076.79.1.10 fsRstPortRoleSelSmState00
1.3.6.1.4.1.2076.79.1.11 fsRstOldDesignatedRoot00
1.3.6.1.4.1.2076.79.1.12 fsRstPortExtTable159
1.3.6.1.4.1.2076.79.1.13 fsRstDynamicPathcostCalculation00
1.3.6.1.4.1.2076.79.1.14 fsRstCalcPortPathCostOnSpeedChg00
1.3.6.1.4.1.2076.79.1.15 fsRstRcvdEvent00
1.3.6.1.4.1.2076.79.1.16 fsRstRcvdEventSubType00
1.3.6.1.4.1.2076.79.1.17 fsRstRcvdEventTimeStamp00
1.3.6.1.4.1.2076.79.1.18 fsRstRcvdPortStateChangeTimeStamp00
1.3.6.1.4.1.2076.79.1.19 fsRstBpduGuard00
1.3.6.1.4.1.2076.79.1.20 fsRstStpPerfStatus00
1.3.6.1.4.1.2076.79.1.21 fsRstStpPathCostType00