OID reference

dosDefenseDebugMode

1.3.6.1.4.1.207.8.4.4.4.143.2

Description

The debugging options enabled for DoS defense. Output goes to the asynchronous port or telnet session that enabled debugging. The bit 'None(0)' indicates that no debugging is enabled. The bit 'Attack(1)' indicates that information about the start and finish of attacks is displayed. The bit 'Packet(2)' indicates that a…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.207.8.4.4.4.143 (dosDefense)
Node code
2
Node name
dosDefenseDebugMode
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.207.8.4.4.4.143.2
URN notation
urn:oid:1.3.6.1.4.1.207.8.4.4.4.143.2
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 207 8 4 4 4 143 2}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedtelesyn(207) mibObject(8) brouterMib(4) atRouter(4) modules(4) dosDefense(143) dosDefenseDebugMode(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedtelesyn(207) mibObjects(8) brouterMib(4) atRouter(4) modules(4) dosDefense(143) dosDefenseDebugMode(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedtelesyn(207) mibobjs(8) brouterMib(4) atRouter(4) modules(4) dosDefense(143) dosDefenseDebugMode(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ati(207) mibObject(8) brouterMib(4) atRouter(4) modules(4) dosDefense(143) dosDefenseDebugMode(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ati(207) mibObjects(8) brouterMib(4) atRouter(4) modules(4) dosDefense(143) dosDefenseDebugMode(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ati(207) mibobjs(8) brouterMib(4) atRouter(4) modules(4) dosDefense(143) dosDefenseDebugMode(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedTelesis(207) mibObject(8) brouterMib(4) atRouter(4) modules(4) dosDefense(143) dosDefenseDebugMode(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedTelesis(207) mibObjects(8) brouterMib(4) atRouter(4) modules(4) dosDefense(143) dosDefenseDebugMode(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedTelesis(207) mibobjs(8) brouterMib(4) atRouter(4) modules(4) dosDefense(143) dosDefenseDebugMode(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedTelesyn(207) mibObject(8) brouterMib(4) atRouter(4) modules(4) dosDefense(143) dosDefenseDebugMode(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedTelesyn(207) mibObjects(8) brouterMib(4) atRouter(4) modules(4) dosDefense(143) dosDefenseDebugMode(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedTelesyn(207) mibobjs(8) brouterMib(4) atRouter(4) modules(4) dosDefense(143) dosDefenseDebugMode(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) alliedtelesyn(207) mibObject(8) brouterMib(4) atRouter(4) modules(4) dosDefense(143) dosDefenseDebugMode(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) alliedtelesyn(207) mibObjects(8) brouterMib(4) atRouter(4) modules(4) dosDefense(143) dosDefenseDebugMode(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) alliedtelesyn(207) mibobjs(8) brouterMib(4) atRouter(4) modules(4) dosDefense(143) dosDefenseDebugMode(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) ati(207) mibObject(8) brouterMib(4) atRouter(4) modules(4) dosDefense(143) dosDefenseDebugMode(2)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/207/8/4/4/4/143/2
  • /ISO/Identified-Organization/6/1/4/1/207/8/4/4/4/143/2
  • /ISO/3/6/1/4/1/207/8/4/4/4/143/2
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/alliedtelesyn/mibObject/brouterMib/atRouter/modules/dosDefense/dosDefenseDebugMode
  • /iso/identified-organization/dod/internet/private/enterprise/alliedtelesyn/mibObjects/brouterMib/atRouter/modules/dosDefense/dosDefenseDebugMode
  • /iso/identified-organization/dod/internet/private/enterprise/alliedtelesyn/mibobjs/brouterMib/atRouter/modules/dosDefense/dosDefenseDebugMode
  • /iso/identified-organization/dod/internet/private/enterprise/ati/mibObject/brouterMib/atRouter/modules/dosDefense/dosDefenseDebugMode
  • /iso/identified-organization/dod/internet/private/enterprise/ati/mibObjects/brouterMib/atRouter/modules/dosDefense/dosDefenseDebugMode
  • /iso/identified-organization/dod/internet/private/enterprise/ati/mibobjs/brouterMib/atRouter/modules/dosDefense/dosDefenseDebugMode
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesis/mibObject/brouterMib/atRouter/modules/dosDefense/dosDefenseDebugMode
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesis/mibObjects/brouterMib/atRouter/modules/dosDefense/dosDefenseDebugMode
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesis/mibobjs/brouterMib/atRouter/modules/dosDefense/dosDefenseDebugMode
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesyn/mibObject/brouterMib/atRouter/modules/dosDefense/dosDefenseDebugMode
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesyn/mibObjects/brouterMib/atRouter/modules/dosDefense/dosDefenseDebugMode
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesyn/mibobjs/brouterMib/atRouter/modules/dosDefense/dosDefenseDebugMode
  • /iso/identified-organization/dod/internet/private/enterprises/alliedtelesyn/mibObject/brouterMib/atRouter/modules/dosDefense/dosDefenseDebugMode
  • /iso/identified-organization/dod/internet/private/enterprises/alliedtelesyn/mibObjects/brouterMib/atRouter/modules/dosDefense/dosDefenseDebugMode
  • /iso/identified-organization/dod/internet/private/enterprises/alliedtelesyn/mibobjs/brouterMib/atRouter/modules/dosDefense/dosDefenseDebugMode
  • /iso/identified-organization/dod/internet/private/enterprises/ati/mibObject/brouterMib/atRouter/modules/dosDefense/dosDefenseDebugMode
  • Additional combinations skipped.

SNMP properties

Value type
BITS
Maximum access defined by MIB
read-only
Status in MIB
current

Bit values

Bit positionName
0none
1packet
2attack
3packet-attack
4diagnostics
5packet-diagnostics
6attack-diagnostics
7packet-attack-diagnostics

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

dosDefenseDebugMode · current

dosDefenseDebugMode OBJECT-TYPE
			SYNTAX BITS
				{
				none(0),
				packet(1),
				attack(2),
				packet-attack(3),
				diagnostics(4),
				packet-diagnostics(5),
				attack-diagnostics(6),
				packet-attack-diagnostics(7)
				}
			MAX-ACCESS read-only
			STATUS current
			DESCRIPTION
				"The debugging options enabled for DoS defense.  Output goes
				to the asynchronous port or telnet session that enabled
				debugging.
				
				The bit 'None(0)' indicates that no debugging is enabled.
				
				The bit 'Attack(1)' indicates that information about the
				start and finish of attacks is displayed.
				
				The bit 'Packet(2)' indicates that a hexadecimal dump of
				the IP header of all suspect packets is displayed.
				
				The bit 'Diagnostics(3)' indicates that additional
				debugging and diagnostic messages may be displayed."
			::= { dosDefense 2 }

dosDefenseDebugMode · current

dosDefenseDebugMode OBJECT-TYPE
			SYNTAX BITS
				{
				none(0),
				packet(1),
				attack(2),
				packet/attack(3),
				diagnostics(4),
				packet/diagnostics(5),
				attack/diagnostics(6),
				packet/attack/diagnostics(7)
				}
			MAX-ACCESS read-only
			STATUS current
			DESCRIPTION
				"The debugging options enabled for DoS defense.  Output goes
				to the asynchronous port or telnet session that enabled
				debugging.
				
				The bit 'None(0)' indicates that no debugging is enabled.
				
				The bit 'Attack(1)' indicates that information about the
				start and finish of attacks is displayed.
				
				The bit 'Packet(2)' indicates that a hexadecimal dump of
				the IP header of all suspect packets is displayed.
				
				The bit 'Diagnostics(3)' indicates that additional
				debugging and diagnostic messages may be displayed."
			::= { dosDefense 2 }

Meaning

Descriptions

1 unique

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

The debugging options enabled for DoS defense. Output goes to the asynchronous port or telnet session that enabled debugging. The bit 'None(0)' indicates that no debugging is enabled. The bit 'Attack(1)' indicates that information about the start and finish of attacks is displayed. The bit 'Packet(2)' indicates that a hexadecimal dump of the IP header of all suspect packets is displayed. The bit 'Diagnostics(3)' indicates that additional debugging and diagnostic messages may be displayed.

Sources for this description

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

See 2 matching source records

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)2 records · 2 sources

Description 1

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

Status in source: current.

Names: dosDefenseDebugMode

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dosDefenseDebugMode",
    "OBJECT-TYPE",
    "SYNTAX",
    "BITS",
    "{",
    "none",
    "(",
    "0",
    ")",
    ",",
    "packet",
    "(",
    "1",
    ")",
    ",",
    "attack",
    "(",
    "2",
    ")",
    ",",
    "packet-attack",
    "(",
    "3",
    ")",
    ",",
    "diagnostics",
    "(",
    "4",
    ")",
    ",",
    "packet-diagnostics",
    "(",
    "5",
    ")",
    ",",
    "attack-diagnostics",
    "(",
    "6",
    ")",
    ",",
    "packet-attack-diagnostics",
    "(",
    "7",
    ")",
    "}",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The debugging options enabled for DoS defense. Output goes to the asynchronous port or telnet session that enabled debugging. The bit 'None(0)' indicates that no debugging is enabled. The bit 'Attack(1)' indicates that information about the start and finish of attacks is displayed. The bit 'Packet(2)' indicates that a hexadecimal dump of the IP header of all suspect packets is displayed. The bit 'Diagnostics(3)' indicates that additional debugging and diagnostic messages may be displayed.\"",
    "::=",
    "{",
    "dosDefense",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "BITS",
      [
        [
          "none",
          0
        ],
        [
          "packet",
          1
        ],
        [
          "attack",
          2
        ],
        [
          "packet-attack",
          3
        ],
        [
          "diagnostics",
          4
        ],
        [
          "packet-diagnostics",
          5
        ],
        [
          "attack-diagnostics",
          6
        ],
        [
          "packet-attack-diagnostics",
          7
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The debugging options enabled for DoS defense. Output goes to the asynchronous port or telnet session that enabled debugging. The bit 'None(0)' indicates that no debugging is enabled. The bit 'Attack(1)' indicates that information about the start and finish of attacks is displayed. The bit 'Packet(2)' indicates that a hexadecimal dump of the IP header of all suspect packets is displayed. The bit 'Diagnostics(3)' indicates that additional debugging and diagnostic messages may be displayed."
    ],
    null,
    null,
    null,
    null
  ]
}
dosDefenseDebugMode · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: dosDefenseDebugMode

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dosDefenseDebugMode",
    "OBJECT-TYPE",
    "SYNTAX",
    "BITS",
    "{",
    "none",
    "(",
    "0",
    ")",
    ",",
    "packet",
    "(",
    "1",
    ")",
    ",",
    "attack",
    "(",
    "2",
    ")",
    ",",
    "packet",
    "/",
    "attack",
    "(",
    "3",
    ")",
    ",",
    "diagnostics",
    "(",
    "4",
    ")",
    ",",
    "packet",
    "/",
    "diagnostics",
    "(",
    "5",
    ")",
    ",",
    "attack",
    "/",
    "diagnostics",
    "(",
    "6",
    ")",
    ",",
    "packet",
    "/",
    "attack",
    "/",
    "diagnostics",
    "(",
    "7",
    ")",
    "}",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The debugging options enabled for DoS defense. Output goes to the asynchronous port or telnet session that enabled debugging. The bit 'None(0)' indicates that no debugging is enabled. The bit 'Attack(1)' indicates that information about the start and finish of attacks is displayed. The bit 'Packet(2)' indicates that a hexadecimal dump of the IP header of all suspect packets is displayed. The bit 'Diagnostics(3)' indicates that additional debugging and diagnostic messages may be displayed.\"",
    "::=",
    "{",
    "dosDefense",
    "2",
    "}"
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.207)

Scott Holley

Siblings (4)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.207.8.4.4.4.143.1 dosDefenseStatus00
1.3.6.1.4.1.207.8.4.4.4.143.3 dosDefenseNumDebugPackets00
1.3.6.1.4.1.207.8.4.4.4.143.4 dosDefenseTable113
1.3.6.1.4.1.207.8.4.4.4.143.5 dosDefenseTraps22