OID reference

fsSnoopTraceOption

1.3.6.1.4.1.2076.105.2.2.1.11

Description

This object is used to enable trace statements in snooping 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: 0 - Data Path traces 1 - Control Plane traces 2 - Tx…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.2076.105.2.2.1 (fsSnoopInstanceConfigEntry)
Node code
11
Node name
fsSnoopTraceOption
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.2076.105.2.2.1.11
URN notation
urn:oid:1.3.6.1.4.1.2076.105.2.2.1.11
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 2076 105 2 2 1 11}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 2076 fssnoop(105) fsSnoopInst(2) fsSnoopInstanceConfigTable(2) fsSnoopInstanceConfigEntry(1) fsSnoopTraceOption(11)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 2076 fssnoop(105) fsSnoopInst(2) fsSnoopInstanceConfigTable(2) fsSnoopInstanceConfigEntry(1) fsSnoopTraceOption(11)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 fssnoop(105) fsSnoopInst(2) fsSnoopInstanceConfigTable(2) fsSnoopInstanceConfigEntry(1) fsSnoopTraceOption(11)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 fssnoop(105) fsSnoopInst(2) fsSnoopInstanceConfigTable(2) fsSnoopInstanceConfigEntry(1) fsSnoopTraceOption(11)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) 2076 fssnoop(105) fsSnoopInst(2) fsSnoopInstanceConfigTable(2) fsSnoopInstanceConfigEntry(1) fsSnoopTraceOption(11)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) 2076 fssnoop(105) fsSnoopInst(2) fsSnoopInstanceConfigTable(2) fsSnoopInstanceConfigEntry(1) fsSnoopTraceOption(11)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 fssnoop(105) fsSnoopInst(2) fsSnoopInstanceConfigTable(2) fsSnoopInstanceConfigEntry(1) fsSnoopTraceOption(11)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 fssnoop(105) fsSnoopInst(2) fsSnoopInstanceConfigTable(2) fsSnoopInstanceConfigEntry(1) fsSnoopTraceOption(11)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 2076 fssnoop(105) fsSnoopInst(2) fsSnoopInstanceConfigTable(2) fsSnoopInstanceConfigEntry(1) fsSnoopTraceOption(11)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 2076 fssnoop(105) fsSnoopInst(2) fsSnoopInstanceConfigTable(2) fsSnoopInstanceConfigEntry(1) fsSnoopTraceOption(11)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 fssnoop(105) fsSnoopInst(2) fsSnoopInstanceConfigTable(2) fsSnoopInstanceConfigEntry(1) fsSnoopTraceOption(11)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 fssnoop(105) fsSnoopInst(2) fsSnoopInstanceConfigTable(2) fsSnoopInstanceConfigEntry(1) fsSnoopTraceOption(11)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) 2076 fssnoop(105) fsSnoopInst(2) fsSnoopInstanceConfigTable(2) fsSnoopInstanceConfigEntry(1) fsSnoopTraceOption(11)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) 2076 fssnoop(105) fsSnoopInst(2) fsSnoopInstanceConfigTable(2) fsSnoopInstanceConfigEntry(1) fsSnoopTraceOption(11)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 fssnoop(105) fsSnoopInst(2) fsSnoopInstanceConfigTable(2) fsSnoopInstanceConfigEntry(1) fsSnoopTraceOption(11)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 fssnoop(105) fsSnoopInst(2) fsSnoopInstanceConfigTable(2) fsSnoopInstanceConfigEntry(1) fsSnoopTraceOption(11)}
OID-IRI notation
  • /1/3/6/1/4/1/2076/105/2/2/1/11
  • /ISO/Identified-Organization/6/1/4/1/2076/105/2/2/1/11
  • /ISO/3/6/1/4/1/2076/105/2/2/1/11
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/2076/fssnoop/fsSnoopInst/fsSnoopInstanceConfigTable/fsSnoopInstanceConfigEntry/fsSnoopTraceOption
  • /iso/identified-organization/dod/internet/private/enterprises/2076/fssnoop/fsSnoopInst/fsSnoopInstanceConfigTable/fsSnoopInstanceConfigEntry/fsSnoopTraceOption
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/2076/fssnoop/fsSnoopInst/fsSnoopInstanceConfigTable/fsSnoopInstanceConfigEntry/fsSnoopTraceOption
  • /iso/identified-organization/dod/internet/private/vendor-objects/2076/fssnoop/fsSnoopInst/fsSnoopInstanceConfigTable/fsSnoopInstanceConfigEntry/fsSnoopTraceOption
  • /iso/org/dod/internet/private/enterprise/2076/fssnoop/fsSnoopInst/fsSnoopInstanceConfigTable/fsSnoopInstanceConfigEntry/fsSnoopTraceOption
  • /iso/org/dod/internet/private/enterprises/2076/fssnoop/fsSnoopInst/fsSnoopInstanceConfigTable/fsSnoopInstanceConfigEntry/fsSnoopTraceOption
  • /iso/org/dod/internet/private/ldap-enterprise/2076/fssnoop/fsSnoopInst/fsSnoopInstanceConfigTable/fsSnoopInstanceConfigEntry/fsSnoopTraceOption
  • /iso/org/dod/internet/private/vendor-objects/2076/fssnoop/fsSnoopInst/fsSnoopInstanceConfigTable/fsSnoopInstanceConfigEntry/fsSnoopTraceOption
  • /iso/iso-identified-organization/dod/internet/private/enterprise/2076/fssnoop/fsSnoopInst/fsSnoopInstanceConfigTable/fsSnoopInstanceConfigEntry/fsSnoopTraceOption
  • /iso/iso-identified-organization/dod/internet/private/enterprises/2076/fssnoop/fsSnoopInst/fsSnoopInstanceConfigTable/fsSnoopInstanceConfigEntry/fsSnoopTraceOption
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/2076/fssnoop/fsSnoopInst/fsSnoopInstanceConfigTable/fsSnoopInstanceConfigEntry/fsSnoopTraceOption
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/2076/fssnoop/fsSnoopInst/fsSnoopInstanceConfigTable/fsSnoopInstanceConfigEntry/fsSnoopTraceOption
  • /iso/iso-organization/dod/internet/private/enterprise/2076/fssnoop/fsSnoopInst/fsSnoopInstanceConfigTable/fsSnoopInstanceConfigEntry/fsSnoopTraceOption
  • /iso/iso-organization/dod/internet/private/enterprises/2076/fssnoop/fsSnoopInst/fsSnoopInstanceConfigTable/fsSnoopInstanceConfigEntry/fsSnoopTraceOption
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/2076/fssnoop/fsSnoopInst/fsSnoopInstanceConfigTable/fsSnoopInstanceConfigEntry/fsSnoopTraceOption
  • /iso/iso-organization/dod/internet/private/vendor-objects/2076/fssnoop/fsSnoopInst/fsSnoopInstanceConfigTable/fsSnoopInstanceConfigEntry/fsSnoopTraceOption

SNMP properties

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

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: fsSnoopInstanceConfigInstId, fsSnoopInetAddressType.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.2076.105.2.2.1.11

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

fsSnoopTraceOption · current

fsSnoopTraceOption OBJECT-TYPE 
          SYNTAX      Integer32
          MAX-ACCESS  read-write 
          STATUS      current 
          DESCRIPTION 
             "This object is used to enable trace statements in  
              snooping 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:  
                      0 - Data Path traces
                      1 - Control Plane traces 
                      2 - Tx Traces 
                      3 - Rx Traces 
 
              The remaining bits are unused. Combination of levels are  
              also allowed. 
 
              For example if the bits 0 and 1 are set, then the trace 
              statement related to  Data Path and Control Plane
              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 3." 
          ::= { fsSnoopInstanceConfigEntry 11 }

fsSnoopTraceOption · current

fsSnoopTraceOption OBJECT-TYPE 
          SYNTAX      Integer32
          MAX-ACCESS  read-write 
          STATUS      current 
          DESCRIPTION 
             "This object is used to enable trace statements in  
              snooping 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:  
                      0 - Init and Shutdown traces 
                      1 - Management traces 
                      2 - Data Path traces 
                      3 - Control Plane traces 
                      4 - Packet Dump traces 
                      5 - Traces related to all resources except buffers 
                      6 - All Failure traces 
                      7 - Buffer allocation/release traces 
 
              The remaining bits are unused. Combination of levels are  
              also allowed. 
 
              For example if the bits 0 and 1 are set, then the trace 
              statement 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 3." 
          ::= { fsSnoopInstanceConfigEntry 11 }

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 snooping 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: 0 - Data Path traces 1 - Control Plane traces 2 - Tx Traces 3 - Rx Traces The remaining bits are unused. Combination of levels are also allowed. For example if the bits 0 and 1 are set, then the trace statement related to Data Path and Control Plane 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 3.

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 trace statements in snooping 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: 0 - Init and Shutdown traces 1 - Management traces 2 - Data Path traces 3 - Control Plane traces 4 - Packet Dump traces 5 - Traces related to all resources except buffers 6 - All Failure traces 7 - Buffer allocation/release traces The remaining bits are unused. Combination of levels are also allowed. For example if the bits 0 and 1 are set, then the trace statement 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 3.

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

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

Status in source: current.

Names: fsSnoopTraceOption

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsSnoopTraceOption",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This object is used to enable trace statements in snooping 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: 0 - Data Path traces 1 - Control Plane traces 2 - Tx Traces 3 - Rx Traces The remaining bits are unused. Combination of levels are also allowed. For example if the bits 0 and 1 are set, then the trace statement related to Data Path and Control Plane 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 3.\"",
    "::=",
    "{",
    "fsSnoopInstanceConfigEntry",
    "11",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32"
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This object is used to enable trace statements in snooping 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: 0 - Data Path traces 1 - Control Plane traces 2 - Tx Traces 3 - Rx Traces The remaining bits are unused. Combination of levels are also allowed. For example if the bits 0 and 1 are set, then the trace statement related to Data Path and Control Plane 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 3."
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 2Belden, GarrettCom and Hirschmann IT official standalone MIBs1 record · 1 source

Description 2

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

Status in source: current.

Names: fsSnoopTraceOption

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsSnoopTraceOption",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This object is used to enable trace statements in snooping 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: 0 - Init and Shutdown traces 1 - Management traces 2 - Data Path traces 3 - Control Plane traces 4 - Packet Dump traces 5 - Traces related to all resources except buffers 6 - All Failure traces 7 - Buffer allocation/release traces The remaining bits are unused. Combination of levels are also allowed. For example if the bits 0 and 1 are set, then the trace statement 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 3.\"",
    "::=",
    "{",
    "fsSnoopInstanceConfigEntry",
    "11",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32"
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This object is used to enable trace statements in snooping 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: 0 - Init and Shutdown traces 1 - Management traces 2 - Data Path traces 3 - Control Plane traces 4 - Packet Dump traces 5 - Traces related to all resources except buffers 6 - All Failure traces 7 - Buffer allocation/release traces The remaining bits are unused. Combination of levels are also allowed. For example if the bits 0 and 1 are set, then the trace statement 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 3."
    ],
    null,
    null,
    null,
    null
  ]
}

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.105.2.2.1.1 fsSnoopInstanceConfigInstId00
1.3.6.1.4.1.2076.105.2.2.1.2 fsSnoopInetAddressType00
1.3.6.1.4.1.2076.105.2.2.1.3 fsSnoopStatus00
1.3.6.1.4.1.2076.105.2.2.1.4 fsSnoopProxyReportingStatus00
1.3.6.1.4.1.2076.105.2.2.1.5 fsSnoopRouterPortPurgeInterval00
1.3.6.1.4.1.2076.105.2.2.1.6 fsSnoopPortPurgeInterval00
1.3.6.1.4.1.2076.105.2.2.1.7 fsSnoopReportForwardInterval00
1.3.6.1.4.1.2076.105.2.2.1.8 fsSnoopRetryCount00
1.3.6.1.4.1.2076.105.2.2.1.9 fsSnoopGrpQueryInterval00
1.3.6.1.4.1.2076.105.2.2.1.10 fsSnoopReportFwdOnAllPorts00
1.3.6.1.4.1.2076.105.2.2.1.12 fsSnoopOperStatus00
1.3.6.1.4.1.2076.105.2.2.1.13 fsSnoopSendQueryOnTopoChange00
1.3.6.1.4.1.2076.105.2.2.1.14 fsSnoopSendLeaveOnTopoChange00
1.3.6.1.4.1.2076.105.2.2.1.15 fsSnoopFilterStatus00
1.3.6.1.4.1.2076.105.2.2.1.16 fsSnoopMulticastVlanStatus00
1.3.6.1.4.1.2076.105.2.2.1.17 fsSnoopProxyStatus00
1.3.6.1.4.1.2076.105.2.2.1.18 fsSnoopQueryFwdOnAllPorts00
1.3.6.1.4.1.2076.105.2.2.1.19 fsSnoopFwdGroupsCnt00
1.3.6.1.4.1.2076.105.2.2.1.20 fsSnoopDebugOption00
1.3.6.1.4.1.2076.105.2.2.1.21 fsSnoopEnforceRouterAlert00