OID reference

fsErpsCtxtTraceInput

1.3.6.1.4.1.29601.2.40.1.1.1.5

Description

This object stores the trace option string input given by the user. To enable or disable particular trace, the user has to enter the corresponding string(given below) assigned for that. To enable or disable more than one trace, the user has to enter the corresponding strings with SPACE delimiter between each string. S…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.29601.2.40.1.1.1 (fsErpsContextEntry)
Node code
5
Node name
fsErpsCtxtTraceInput
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.29601.2.40.1.1.1.5
URN notation
urn:oid:1.3.6.1.4.1.29601.2.40.1.1.1.5
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 29601 2 40 1 1 1 5}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsErpsMIB(40) fsErpsContext(1) fsErpsContextTable(1) fsErpsContextEntry(1) fsErpsCtxtTraceInput(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsErpsMIB(40) fsErpsContext(1) fsErpsContextTable(1) fsErpsContextEntry(1) fsErpsCtxtTraceInput(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsErpsMIB(40) fsErpsContext(1) fsErpsContextTable(1) fsErpsContextEntry(1) fsErpsCtxtTraceInput(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsErpsMIB(40) fsErpsContext(1) fsErpsContextTable(1) fsErpsContextEntry(1) fsErpsCtxtTraceInput(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsErpsMIB(40) fsErpsContext(1) fsErpsContextTable(1) fsErpsContextEntry(1) fsErpsCtxtTraceInput(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsErpsMIB(40) fsErpsContext(1) fsErpsContextTable(1) fsErpsContextEntry(1) fsErpsCtxtTraceInput(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsErpsMIB(40) fsErpsContext(1) fsErpsContextTable(1) fsErpsContextEntry(1) fsErpsCtxtTraceInput(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsErpsMIB(40) fsErpsContext(1) fsErpsContextTable(1) fsErpsContextEntry(1) fsErpsCtxtTraceInput(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsErpsMIB(40) fsErpsContext(1) fsErpsContextTable(1) fsErpsContextEntry(1) fsErpsCtxtTraceInput(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsErpsMIB(40) fsErpsContext(1) fsErpsContextTable(1) fsErpsContextEntry(1) fsErpsCtxtTraceInput(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsErpsMIB(40) fsErpsContext(1) fsErpsContextTable(1) fsErpsContextEntry(1) fsErpsCtxtTraceInput(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsErpsMIB(40) fsErpsContext(1) fsErpsContextTable(1) fsErpsContextEntry(1) fsErpsCtxtTraceInput(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsErpsMIB(40) fsErpsContext(1) fsErpsContextTable(1) fsErpsContextEntry(1) fsErpsCtxtTraceInput(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsErpsMIB(40) fsErpsContext(1) fsErpsContextTable(1) fsErpsContextEntry(1) fsErpsCtxtTraceInput(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsErpsMIB(40) fsErpsContext(1) fsErpsContextTable(1) fsErpsContextEntry(1) fsErpsCtxtTraceInput(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsErpsMIB(40) fsErpsContext(1) fsErpsContextTable(1) fsErpsContextEntry(1) fsErpsCtxtTraceInput(5)}
OID-IRI notation
  • /1/3/6/1/4/1/29601/2/40/1/1/1/5
  • /ISO/Identified-Organization/6/1/4/1/29601/2/40/1/1/1/5
  • /ISO/3/6/1/4/1/29601/2/40/1/1/1/5
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/29601/2/fsErpsMIB/fsErpsContext/fsErpsContextTable/fsErpsContextEntry/fsErpsCtxtTraceInput
  • /iso/identified-organization/dod/internet/private/enterprises/29601/2/fsErpsMIB/fsErpsContext/fsErpsContextTable/fsErpsContextEntry/fsErpsCtxtTraceInput
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/29601/2/fsErpsMIB/fsErpsContext/fsErpsContextTable/fsErpsContextEntry/fsErpsCtxtTraceInput
  • /iso/identified-organization/dod/internet/private/vendor-objects/29601/2/fsErpsMIB/fsErpsContext/fsErpsContextTable/fsErpsContextEntry/fsErpsCtxtTraceInput
  • /iso/org/dod/internet/private/enterprise/29601/2/fsErpsMIB/fsErpsContext/fsErpsContextTable/fsErpsContextEntry/fsErpsCtxtTraceInput
  • /iso/org/dod/internet/private/enterprises/29601/2/fsErpsMIB/fsErpsContext/fsErpsContextTable/fsErpsContextEntry/fsErpsCtxtTraceInput
  • /iso/org/dod/internet/private/ldap-enterprise/29601/2/fsErpsMIB/fsErpsContext/fsErpsContextTable/fsErpsContextEntry/fsErpsCtxtTraceInput
  • /iso/org/dod/internet/private/vendor-objects/29601/2/fsErpsMIB/fsErpsContext/fsErpsContextTable/fsErpsContextEntry/fsErpsCtxtTraceInput
  • /iso/iso-identified-organization/dod/internet/private/enterprise/29601/2/fsErpsMIB/fsErpsContext/fsErpsContextTable/fsErpsContextEntry/fsErpsCtxtTraceInput
  • /iso/iso-identified-organization/dod/internet/private/enterprises/29601/2/fsErpsMIB/fsErpsContext/fsErpsContextTable/fsErpsContextEntry/fsErpsCtxtTraceInput
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/29601/2/fsErpsMIB/fsErpsContext/fsErpsContextTable/fsErpsContextEntry/fsErpsCtxtTraceInput
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/29601/2/fsErpsMIB/fsErpsContext/fsErpsContextTable/fsErpsContextEntry/fsErpsCtxtTraceInput
  • /iso/iso-organization/dod/internet/private/enterprise/29601/2/fsErpsMIB/fsErpsContext/fsErpsContextTable/fsErpsContextEntry/fsErpsCtxtTraceInput
  • /iso/iso-organization/dod/internet/private/enterprises/29601/2/fsErpsMIB/fsErpsContext/fsErpsContextTable/fsErpsContextEntry/fsErpsCtxtTraceInput
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/29601/2/fsErpsMIB/fsErpsContext/fsErpsContextTable/fsErpsContextEntry/fsErpsCtxtTraceInput
  • /iso/iso-organization/dod/internet/private/vendor-objects/29601/2/fsErpsMIB/fsErpsContext/fsErpsContextTable/fsErpsContextEntry/fsErpsCtxtTraceInput

SNMP properties

Value type
DisplayString
Maximum access defined by MIB
read-write
Status in MIB
current
Default value
"critical"
Allowed size (octets)
1–255

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition. The index encoding is not inferred here.

Published row index: fsErpsContextId.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.29601.2.40.1.1.1.5

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.

fsErpsCtxtTraceInput OBJECT-TYPE
    SYNTAX      DisplayString (SIZE(1..255))
    MAX-ACCESS  read-write 
    STATUS      current 
    DESCRIPTION 
      "This object stores the trace option string input given by the user. To 
       enable or disable particular trace, the user has to enter the 
       corresponding string(given below) assigned for that. To enable or 
       disable more than one trace, the user has to enter the corresponding 
       strings with SPACE delimiter between each string.

       Syntax:
          <enable/disable> <trace string1> <trace string2> ...

       For example, to enable the below traces
           - Start and Shutdown traces
           - Management traces

       The input string has to be:
              'enable init-shut mgmt'

       For example, to disable the below traces 
           - start and Shutdown traces and
           - Management traces

       The input string has to be:
              'disable start-shutdown mgmt'

       First string should be either enable or disable.

       The definition of input strings that can be given are:

       enable          - Enables the corresponding option,
       disable         - Disables the corresponding option,
       start-shutdown  - Start and Shutdown traces,
       mgmt            - Management traces,
       ctrl            - Control Plane traces,
       pkt-dump        - Packet Dump traces,
       resource        - Traces related to all resources except buffers,
       all-fail        - All Failure traces,
       buffer          - Buffer allocation/ release traces,
       critical        - Critical traces,

       By default, critical trace will be enabled."
    DEFVAL  { "critical" }
    ::= { fsErpsContextEntry 5 }

Meaning

Descriptions

1 unique

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

This object stores the trace option string input given by the user. To enable or disable particular trace, the user has to enter the corresponding string(given below) assigned for that. To enable or disable more than one trace, the user has to enter the corresponding strings with SPACE delimiter between each string. Syntax: <enable/disable> <trace string1> <trace string2> ... For example, to enable the below traces - Start and Shutdown traces - Management traces The input string has to be: 'enable init-shut mgmt' For example, to disable the below traces - start and Shutdown traces and - Management traces The input string has to be: 'disable start-shutdown mgmt' First string should be either enable or disable. The definition of input strings that can be given are: enable - Enables the corresponding option, disable - Disables the corresponding option, start-shutdown - Start and Shutdown traces, mgmt - Management traces, ctrl - Control Plane traces, pkt-dump - Packet Dump traces, resource - Traces related to all resources except buffers, all-fail - All Failure traces, buffer - Buffer allocation/ release traces, critical - Critical traces, By default, critical trace will be enabled.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)Belden, GarrettCom and Hirschmann IT official standalone MIBs

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), Belden, GarrettCom and Hirschmann IT official standalone MIBs1 record · 2 sources

Description 1

fsErpsCtxtTraceInput · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), Belden, GarrettCom and Hirschmann IT official standalone MIBs2 sources

Status in source: current.

Names: fsErpsCtxtTraceInput

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsErpsCtxtTraceInput",
    "OBJECT-TYPE",
    "SYNTAX",
    "DisplayString",
    "(",
    "SIZE",
    "(",
    "1",
    ".",
    ".",
    "255",
    ")",
    ")",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This object stores the trace option string input given by the user. To enable or disable particular trace, the user has to enter the corresponding string(given below) assigned for that. To enable or disable more than one trace, the user has to enter the corresponding strings with SPACE delimiter between each string. Syntax: <enable/disable> <trace string1> <trace string2> ... For example, to enable the below traces - Start and Shutdown traces - Management traces The input string has to be: 'enable init-shut mgmt' For example, to disable the below traces - start and Shutdown traces and - Management traces The input string has to be: 'disable start-shutdown mgmt' First string should be either enable or disable. The definition of input strings that can be given are: enable - Enables the corresponding option, disable - Disables the corresponding option, start-shutdown - Start and Shutdown traces, mgmt - Management traces, ctrl - Control Plane traces, pkt-dump - Packet Dump traces, resource - Traces related to all resources except buffers, all-fail - All Failure traces, buffer - Buffer allocation/ release traces, critical - Critical traces, By default, critical trace will be enabled.\"",
    "DEFVAL",
    "{",
    [
      "literal",
      "22637269746963616c22"
    ],
    "}",
    "::=",
    "{",
    "fsErpsContextEntry",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "DisplayString",
      [
        "octetStringSubType",
        [
          [
            1,
            255
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This object stores the trace option string input given by the user. To enable or disable particular trace, the user has to enter the corresponding string(given below) assigned for that. To enable or disable more than one trace, the user has to enter the corresponding strings with SPACE delimiter between each string. Syntax: <enable/disable> <trace string1> <trace string2> ... For example, to enable the below traces - Start and Shutdown traces - Management traces The input string has to be: 'enable init-shut mgmt' For example, to disable the below traces - start and Shutdown traces and - Management traces The input string has to be: 'disable start-shutdown mgmt' First string should be either enable or disable. The definition of input strings that can be given are: enable - Enables the corresponding option, disable - Disables the corresponding option, start-shutdown - Start and Shutdown traces, mgmt - Management traces, ctrl - Control Plane traces, pkt-dump - Packet Dump traces, resource - Traces related to all resources except buffers, all-fail - All Failure traces, buffer - Buffer allocation/ release traces, critical - Critical traces, By default, critical trace will be enabled."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "\"critical\""
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.29601)

Arpna Gupta

Siblings (9)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.29601.2.40.1.1.1.1 fsErpsContextId00
1.3.6.1.4.1.29601.2.40.1.1.1.2 fsErpsCtxtName00
1.3.6.1.4.1.29601.2.40.1.1.1.3 fsErpsCtxtSystemControl00
1.3.6.1.4.1.29601.2.40.1.1.1.4 fsErpsCtxtModuleStatus00
1.3.6.1.4.1.29601.2.40.1.1.1.6 fsErpsCtxtTrapStatus00
1.3.6.1.4.1.29601.2.40.1.1.1.7 fsErpsCtxtClearRingStats00
1.3.6.1.4.1.29601.2.40.1.1.1.8 fsErpsCtxtRowStatus00
1.3.6.1.4.1.29601.2.40.1.1.1.9 fsErpsCtxtVlanGroupManager00
1.3.6.1.4.1.29601.2.40.1.1.1.10 fsErpsCtxtProprietaryClearFS00