OID reference

fsEoamTraceOption

1.3.6.1.4.1.2076.121.1.5

Description

This object is used to enable trace statements in Ethernat OAM module. A four byte integer is used for enabling the trace level. Each bit in the four byte integer represents a particular trace level. The mapping between the bit positions & the trace level is as follows: Bit 0 - Init and Shutdown traces Bit 1 - Managem…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.2076.121.1 (fsEoamSystem)
Node code
5
Node name
fsEoamTraceOption
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.2076.121.1.5
URN notation
urn:oid:1.3.6.1.4.1.2076.121.1.5
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 2076 121 1 5}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 2076 fseoam(121) fsEoamSystem(1) fsEoamTraceOption(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 2076 fseoam(121) fsEoamSystem(1) fsEoamTraceOption(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 fseoam(121) fsEoamSystem(1) fsEoamTraceOption(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 fseoam(121) fsEoamSystem(1) fsEoamTraceOption(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) 2076 fseoam(121) fsEoamSystem(1) fsEoamTraceOption(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) 2076 fseoam(121) fsEoamSystem(1) fsEoamTraceOption(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 fseoam(121) fsEoamSystem(1) fsEoamTraceOption(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 fseoam(121) fsEoamSystem(1) fsEoamTraceOption(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 2076 fseoam(121) fsEoamSystem(1) fsEoamTraceOption(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 2076 fseoam(121) fsEoamSystem(1) fsEoamTraceOption(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 fseoam(121) fsEoamSystem(1) fsEoamTraceOption(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 fseoam(121) fsEoamSystem(1) fsEoamTraceOption(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) 2076 fseoam(121) fsEoamSystem(1) fsEoamTraceOption(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) 2076 fseoam(121) fsEoamSystem(1) fsEoamTraceOption(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 fseoam(121) fsEoamSystem(1) fsEoamTraceOption(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 fseoam(121) fsEoamSystem(1) fsEoamTraceOption(5)}
OID-IRI notation
  • /1/3/6/1/4/1/2076/121/1/5
  • /ISO/Identified-Organization/6/1/4/1/2076/121/1/5
  • /ISO/3/6/1/4/1/2076/121/1/5
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/2076/fseoam/fsEoamSystem/fsEoamTraceOption
  • /iso/identified-organization/dod/internet/private/enterprises/2076/fseoam/fsEoamSystem/fsEoamTraceOption
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/2076/fseoam/fsEoamSystem/fsEoamTraceOption
  • /iso/identified-organization/dod/internet/private/vendor-objects/2076/fseoam/fsEoamSystem/fsEoamTraceOption
  • /iso/org/dod/internet/private/enterprise/2076/fseoam/fsEoamSystem/fsEoamTraceOption
  • /iso/org/dod/internet/private/enterprises/2076/fseoam/fsEoamSystem/fsEoamTraceOption
  • /iso/org/dod/internet/private/ldap-enterprise/2076/fseoam/fsEoamSystem/fsEoamTraceOption
  • /iso/org/dod/internet/private/vendor-objects/2076/fseoam/fsEoamSystem/fsEoamTraceOption
  • /iso/iso-identified-organization/dod/internet/private/enterprise/2076/fseoam/fsEoamSystem/fsEoamTraceOption
  • /iso/iso-identified-organization/dod/internet/private/enterprises/2076/fseoam/fsEoamSystem/fsEoamTraceOption
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/2076/fseoam/fsEoamSystem/fsEoamTraceOption
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/2076/fseoam/fsEoamSystem/fsEoamTraceOption
  • /iso/iso-organization/dod/internet/private/enterprise/2076/fseoam/fsEoamSystem/fsEoamTraceOption
  • /iso/iso-organization/dod/internet/private/enterprises/2076/fseoam/fsEoamSystem/fsEoamTraceOption
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/2076/fseoam/fsEoamSystem/fsEoamTraceOption
  • /iso/iso-organization/dod/internet/private/vendor-objects/2076/fseoam/fsEoamSystem/fsEoamTraceOption

SNMP properties

Value type
Integer32
Maximum access defined by MIB
read-write
Status in MIB
current
Default value
'00040000'H

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

fsEoamTraceOption · current

fsEoamTraceOption OBJECT-TYPE 
          SYNTAX      Integer32
          MAX-ACCESS  read-write 
          STATUS      current 
          DESCRIPTION 
             "This object is used to enable trace statements in  
              Ethernat OAM module. 
              A four byte integer is used for enabling the trace level.  
              Each bit in the four byte integer represents a particular  
              trace level.  
              The mapping between the bit positions & the trace level is  
              as follows:  
                  Bit 0 - Init and Shutdown traces 
                  Bit 1 - Management traces 
                  Bit 2 - Data Path traces 
                  Bit 3 - Control Plane traces 
                  Bit 4 - Packet Dump traces 
                  Bit 5 - Traces related to all resources except buffers 
                  Bit 6 - All Failure traces 
                  Bit 7 - Buffer allocation/release traces 
 
                  Bit 16 - EOAM Function Entry traces
                  Bit 17 - EOAM Function Exit traces
                  Bit 18 - EOAM Critical traces 
                  Bit 19 - EOAM Discovery traces 
                  Bit 20 - EOAM Remote loopback traces 
                  Bit 21 - EOAM Link monitoring module traces 
                  Bit 22 - EOAM MIB variable req/response traces 
                  Bit 23 - EOAM Remote Failure Indication traces 
                  Bit 24 - EOAM Multiplexer / Parser traces 
                  Bit 25 - EOAM Redundancy traces 
 
              The remaining bits are unused. Combination of levels are  
              also allowed. 
 
              For example if the bits 19 and 20 are set, then the trace 
              statement related to discovery and remote loopback related
              messages will be printed. 
 
              The user has to enter the corresponding integer value for the 
              bits set. For example if bits 8 and 9 are to be set ,then user
              has to give the value 0x300." 
       DEFVAL { '00040000'H }
          ::= { fsEoamSystem 5 }

fsEoamTraceOption · current

fsEoamTraceOption OBJECT-TYPE 
          SYNTAX      Integer32
          MAX-ACCESS  read-write 
          STATUS      current 
          DESCRIPTION 
             "This object is used to enable trace statements in  
              Ethernet OAM module. 
              A four byte integer is used for enabling the trace level.  
              Each bit in the four byte integer represents a particular  
              trace level.  
              The mapping between the bit positions & the trace level is  
              as follows:  
                  Bit 0 - Init and Shutdown traces 
                  Bit 1 - Management traces 
                  Bit 2 - Data Path traces 
                  Bit 3 - Control Plane traces 
                  Bit 4 - Packet Dump traces 
                  Bit 5 - Traces related to all resources except buffers 
                  Bit 6 - All Failure traces 
                  Bit 7 - Buffer allocation/release traces 
 
                  Bit 16 - EOAM Function Entry traces
                  Bit 17 - EOAM Function Exit traces
                  Bit 18 - EOAM Critical traces 
                  Bit 19 - EOAM Discovery traces 
                  Bit 20 - EOAM Remote loopback traces 
                  Bit 21 - EOAM Link monitoring module traces 
                  Bit 22 - EOAM MIB variable req/response traces 
                  Bit 23 - EOAM Remote Failure Indication traces 
                  Bit 24 - EOAM Multiplexer / Parser traces 
                  Bit 25 - EOAM Redundancy traces 
 
              The remaining bits are unused. Combination of levels are  
              also allowed. 
 
              For example if the bits 19 and 20 are set, then the trace 
              statement related to discovery and remote loopback related
              messages will be printed. 
 
              The user has to enter the corresponding integer value for the 
              bits set. For example if bits 8 and 9 are to be set, then user
              has to give the value 0x300." 
       DEFVAL { '00040000'H }
          ::= { fsEoamSystem 5 }

Meaning

Descriptions

2 unique

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

Description 1

This object is used to enable trace statements in Ethernat OAM module. A four byte integer is used for enabling the trace level. Each bit in the four byte integer represents a particular trace level. The mapping between the bit positions & the trace level is as follows: Bit 0 - Init and Shutdown traces Bit 1 - Management traces Bit 2 - Data Path traces Bit 3 - Control Plane traces Bit 4 - Packet Dump traces Bit 5 - Traces related to all resources except buffers Bit 6 - All Failure traces Bit 7 - Buffer allocation/release traces Bit 16 - EOAM Function Entry traces Bit 17 - EOAM Function Exit traces Bit 18 - EOAM Critical traces Bit 19 - EOAM Discovery traces Bit 20 - EOAM Remote loopback traces Bit 21 - EOAM Link monitoring module traces Bit 22 - EOAM MIB variable req/response traces Bit 23 - EOAM Remote Failure Indication traces Bit 24 - EOAM Multiplexer / Parser traces Bit 25 - EOAM Redundancy traces The remaining bits are unused. Combination of levels are also allowed. For example if the bits 19 and 20 are set, then the trace statement related to discovery and remote loopback related messages will be printed. The user has to enter the corresponding integer value for the bits set. For example if bits 8 and 9 are to be set ,then user has to give the value 0x300.

Sources for this description

Belden, GarrettCom and Hirschmann IT official standalone MIBs

See 1 matching source record

Description 2

This object is used to enable trace statements in Ethernet OAM module. A four byte integer is used for enabling the trace level. Each bit in the four byte integer represents a particular trace level. The mapping between the bit positions & the trace level is as follows: Bit 0 - Init and Shutdown traces Bit 1 - Management traces Bit 2 - Data Path traces Bit 3 - Control Plane traces Bit 4 - Packet Dump traces Bit 5 - Traces related to all resources except buffers Bit 6 - All Failure traces Bit 7 - Buffer allocation/release traces Bit 16 - EOAM Function Entry traces Bit 17 - EOAM Function Exit traces Bit 18 - EOAM Critical traces Bit 19 - EOAM Discovery traces Bit 20 - EOAM Remote loopback traces Bit 21 - EOAM Link monitoring module traces Bit 22 - EOAM MIB variable req/response traces Bit 23 - EOAM Remote Failure Indication traces Bit 24 - EOAM Multiplexer / Parser traces Bit 25 - EOAM Redundancy traces The remaining bits are unused. Combination of levels are also allowed. For example if the bits 19 and 20 are set, then the trace statement related to discovery and remote loopback related messages will be printed. The user has to enter the corresponding integer value for the bits set. For example if bits 8 and 9 are to be set, then user has to give the value 0x300.

Sources for this description

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

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 1Belden, GarrettCom and Hirschmann IT official standalone MIBs1 record · 1 source

Description 1

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

Status in source: current.

Names: fsEoamTraceOption

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsEoamTraceOption",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This object is used to enable trace statements in Ethernat OAM module. A four byte integer is used for enabling the trace level. Each bit in the four byte integer represents a particular trace level. The mapping between the bit positions & the trace level is as follows: Bit 0 - Init and Shutdown traces Bit 1 - Management traces Bit 2 - Data Path traces Bit 3 - Control Plane traces Bit 4 - Packet Dump traces Bit 5 - Traces related to all resources except buffers Bit 6 - All Failure traces Bit 7 - Buffer allocation/release traces Bit 16 - EOAM Function Entry traces Bit 17 - EOAM Function Exit traces Bit 18 - EOAM Critical traces Bit 19 - EOAM Discovery traces Bit 20 - EOAM Remote loopback traces Bit 21 - EOAM Link monitoring module traces Bit 22 - EOAM MIB variable req/response traces Bit 23 - EOAM Remote Failure Indication traces Bit 24 - EOAM Multiplexer / Parser traces Bit 25 - EOAM Redundancy traces The remaining bits are unused. Combination of levels are also allowed. For example if the bits 19 and 20 are set, then the trace statement related to discovery and remote loopback related messages will be printed. The user has to enter the corresponding integer value for the bits set. For example if bits 8 and 9 are to be set ,then user has to give the value 0x300.\"",
    "DEFVAL",
    "{",
    "'",
    "00040000",
    "'",
    "H",
    "}",
    "::=",
    "{",
    "fsEoamSystem",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32"
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This object is used to enable trace statements in Ethernat OAM module. A four byte integer is used for enabling the trace level. Each bit in the four byte integer represents a particular trace level. The mapping between the bit positions & the trace level is as follows: Bit 0 - Init and Shutdown traces Bit 1 - Management traces Bit 2 - Data Path traces Bit 3 - Control Plane traces Bit 4 - Packet Dump traces Bit 5 - Traces related to all resources except buffers Bit 6 - All Failure traces Bit 7 - Buffer allocation/release traces Bit 16 - EOAM Function Entry traces Bit 17 - EOAM Function Exit traces Bit 18 - EOAM Critical traces Bit 19 - EOAM Discovery traces Bit 20 - EOAM Remote loopback traces Bit 21 - EOAM Link monitoring module traces Bit 22 - EOAM MIB variable req/response traces Bit 23 - EOAM Remote Failure Indication traces Bit 24 - EOAM Multiplexer / Parser traces Bit 25 - EOAM Redundancy traces The remaining bits are unused. Combination of levels are also allowed. For example if the bits 19 and 20 are set, then the trace statement related to discovery and remote loopback related messages will be printed. The user has to enter the corresponding integer value for the bits set. For example if bits 8 and 9 are to be set ,then user has to give the value 0x300."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "'00040000'H"
    ]
  ]
}
Records for description 2Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 2

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

Status in source: current.

Names: fsEoamTraceOption

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsEoamTraceOption",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This object is used to enable trace statements in Ethernet OAM module. A four byte integer is used for enabling the trace level. Each bit in the four byte integer represents a particular trace level. The mapping between the bit positions & the trace level is as follows: Bit 0 - Init and Shutdown traces Bit 1 - Management traces Bit 2 - Data Path traces Bit 3 - Control Plane traces Bit 4 - Packet Dump traces Bit 5 - Traces related to all resources except buffers Bit 6 - All Failure traces Bit 7 - Buffer allocation/release traces Bit 16 - EOAM Function Entry traces Bit 17 - EOAM Function Exit traces Bit 18 - EOAM Critical traces Bit 19 - EOAM Discovery traces Bit 20 - EOAM Remote loopback traces Bit 21 - EOAM Link monitoring module traces Bit 22 - EOAM MIB variable req/response traces Bit 23 - EOAM Remote Failure Indication traces Bit 24 - EOAM Multiplexer / Parser traces Bit 25 - EOAM Redundancy traces The remaining bits are unused. Combination of levels are also allowed. For example if the bits 19 and 20 are set, then the trace statement related to discovery and remote loopback related messages will be printed. The user has to enter the corresponding integer value for the bits set. For example if bits 8 and 9 are to be set, then user has to give the value 0x300.\"",
    "DEFVAL",
    "{",
    "'",
    "00040000",
    "'",
    "H",
    "}",
    "::=",
    "{",
    "fsEoamSystem",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32"
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This object is used to enable trace statements in Ethernet OAM module. A four byte integer is used for enabling the trace level. Each bit in the four byte integer represents a particular trace level. The mapping between the bit positions & the trace level is as follows: Bit 0 - Init and Shutdown traces Bit 1 - Management traces Bit 2 - Data Path traces Bit 3 - Control Plane traces Bit 4 - Packet Dump traces Bit 5 - Traces related to all resources except buffers Bit 6 - All Failure traces Bit 7 - Buffer allocation/release traces Bit 16 - EOAM Function Entry traces Bit 17 - EOAM Function Exit traces Bit 18 - EOAM Critical traces Bit 19 - EOAM Discovery traces Bit 20 - EOAM Remote loopback traces Bit 21 - EOAM Link monitoring module traces Bit 22 - EOAM MIB variable req/response traces Bit 23 - EOAM Remote Failure Indication traces Bit 24 - EOAM Multiplexer / Parser traces Bit 25 - EOAM Redundancy traces The remaining bits are unused. Combination of levels are also allowed. For example if the bits 19 and 20 are set, then the trace statement related to discovery and remote loopback related messages will be printed. The user has to enter the corresponding integer value for the bits set. For example if bits 8 and 9 are to be set, then user has to give the value 0x300."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "'00040000'H"
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.2076)

Division Products

Siblings (4)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.2076.121.1.1 fsEoamSystemControl00
1.3.6.1.4.1.2076.121.1.2 fsEoamModuleStatus00
1.3.6.1.4.1.2076.121.1.3 fsEoamErrorEventResend00
1.3.6.1.4.1.2076.121.1.4 fsEoamOui00