OID reference

fsMIIpDbTraceLevel

1.3.6.1.4.1.29601.2.48.1.5

Description

This object is used to enable trace statements in IP binding database 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 1 - Function entry traces BIT 2 - Fun…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.29601.2.48.1 (fsMIIpDbScalars)
Node code
5
Node name
fsMIIpDbTraceLevel
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.29601.2.48.1.5
URN notation
urn:oid:1.3.6.1.4.1.29601.2.48.1.5
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsMIIpdb(48) fsMIIpDbScalars(1) fsMIIpDbTraceLevel(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsMIIpdb(48) fsMIIpDbScalars(1) fsMIIpDbTraceLevel(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsMIIpdb(48) fsMIIpDbScalars(1) fsMIIpDbTraceLevel(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsMIIpdb(48) fsMIIpDbScalars(1) fsMIIpDbTraceLevel(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsMIIpdb(48) fsMIIpDbScalars(1) fsMIIpDbTraceLevel(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsMIIpdb(48) fsMIIpDbScalars(1) fsMIIpDbTraceLevel(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsMIIpdb(48) fsMIIpDbScalars(1) fsMIIpDbTraceLevel(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsMIIpdb(48) fsMIIpDbScalars(1) fsMIIpDbTraceLevel(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsMIIpdb(48) fsMIIpDbScalars(1) fsMIIpDbTraceLevel(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsMIIpdb(48) fsMIIpDbScalars(1) fsMIIpDbTraceLevel(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsMIIpdb(48) fsMIIpDbScalars(1) fsMIIpDbTraceLevel(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsMIIpdb(48) fsMIIpDbScalars(1) fsMIIpDbTraceLevel(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsMIIpdb(48) fsMIIpDbScalars(1) fsMIIpDbTraceLevel(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsMIIpdb(48) fsMIIpDbScalars(1) fsMIIpDbTraceLevel(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsMIIpdb(48) fsMIIpDbScalars(1) fsMIIpDbTraceLevel(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsMIIpdb(48) fsMIIpDbScalars(1) fsMIIpDbTraceLevel(5)}
OID-IRI notation
  • /1/3/6/1/4/1/29601/2/48/1/5
  • /ISO/Identified-Organization/6/1/4/1/29601/2/48/1/5
  • /ISO/3/6/1/4/1/29601/2/48/1/5
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/29601/2/fsMIIpdb/fsMIIpDbScalars/fsMIIpDbTraceLevel
  • /iso/identified-organization/dod/internet/private/enterprises/29601/2/fsMIIpdb/fsMIIpDbScalars/fsMIIpDbTraceLevel
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/29601/2/fsMIIpdb/fsMIIpDbScalars/fsMIIpDbTraceLevel
  • /iso/identified-organization/dod/internet/private/vendor-objects/29601/2/fsMIIpdb/fsMIIpDbScalars/fsMIIpDbTraceLevel
  • /iso/org/dod/internet/private/enterprise/29601/2/fsMIIpdb/fsMIIpDbScalars/fsMIIpDbTraceLevel
  • /iso/org/dod/internet/private/enterprises/29601/2/fsMIIpdb/fsMIIpDbScalars/fsMIIpDbTraceLevel
  • /iso/org/dod/internet/private/ldap-enterprise/29601/2/fsMIIpdb/fsMIIpDbScalars/fsMIIpDbTraceLevel
  • /iso/org/dod/internet/private/vendor-objects/29601/2/fsMIIpdb/fsMIIpDbScalars/fsMIIpDbTraceLevel
  • /iso/iso-identified-organization/dod/internet/private/enterprise/29601/2/fsMIIpdb/fsMIIpDbScalars/fsMIIpDbTraceLevel
  • /iso/iso-identified-organization/dod/internet/private/enterprises/29601/2/fsMIIpdb/fsMIIpDbScalars/fsMIIpDbTraceLevel
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/29601/2/fsMIIpdb/fsMIIpDbScalars/fsMIIpDbTraceLevel
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/29601/2/fsMIIpdb/fsMIIpDbScalars/fsMIIpDbTraceLevel
  • /iso/iso-organization/dod/internet/private/enterprise/29601/2/fsMIIpdb/fsMIIpDbScalars/fsMIIpDbTraceLevel
  • /iso/iso-organization/dod/internet/private/enterprises/29601/2/fsMIIpdb/fsMIIpDbScalars/fsMIIpDbTraceLevel
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/29601/2/fsMIIpdb/fsMIIpDbScalars/fsMIIpDbTraceLevel
  • /iso/iso-organization/dod/internet/private/vendor-objects/29601/2/fsMIIpdb/fsMIIpDbScalars/fsMIIpDbTraceLevel

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 scalar group. A scalar instance uses the suffix .0.

snmpget [connection options] DEVICE .1.3.6.1.4.1.29601.2.48.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.

The displayed source records contain one distinct definition. Compare its source records.

fsMIIpDbTraceLevel OBJECT-TYPE
        SYNTAX      Integer32
        MAX-ACCESS  read-write
        STATUS      current
        DESCRIPTION
            "This object is used to enable trace statements in IP binding
            database 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 1 - Function entry traces
                    BIT 2 - Function Exit traces
                    BIT 3 - Debug traces
                    BIT 4 - Failure traces
                    BIT 5 - Function arguments trace

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

            For example if the bits 1 and 2 are set, then the trace
            statement related to function entry and exit will be printed.

            The user has to enter the corresponding integer value for the
            bits set. For example if bits 1 and 2 are to be set ,then user
            has to give the value 6."
     ::= { fsMIIpDbScalars 5 }

Meaning

Descriptions

1 unique

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

This object is used to enable trace statements in IP binding database 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 1 - Function entry traces BIT 2 - Function Exit traces BIT 3 - Debug traces BIT 4 - Failure traces BIT 5 - Function arguments trace The remaining bits are unused. Combination of levels are also allowed. For example if the bits 1 and 2 are set, then the trace statement related to function entry and exit will be printed. The user has to enter the corresponding integer value for the bits set. For example if bits 1 and 2 are to be set ,then user has to give the value 6.

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

fsMIIpDbTraceLevel · 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: fsMIIpDbTraceLevel

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsMIIpDbTraceLevel",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This object is used to enable trace statements in IP binding database 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 1 - Function entry traces BIT 2 - Function Exit traces BIT 3 - Debug traces BIT 4 - Failure traces BIT 5 - Function arguments trace The remaining bits are unused. Combination of levels are also allowed. For example if the bits 1 and 2 are set, then the trace statement related to function entry and exit will be printed. The user has to enter the corresponding integer value for the bits set. For example if bits 1 and 2 are to be set ,then user has to give the value 6.\"",
    "::=",
    "{",
    "fsMIIpDbScalars",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32"
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This object is used to enable trace statements in IP binding database 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 1 - Function entry traces BIT 2 - Function Exit traces BIT 3 - Debug traces BIT 4 - Failure traces BIT 5 - Function arguments trace The remaining bits are unused. Combination of levels are also allowed. For example if the bits 1 and 2 are set, then the trace statement related to function entry and exit will be printed. The user has to enter the corresponding integer value for the bits set. For example if bits 1 and 2 are to be set ,then user has to give the value 6."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.29601)

Arpna Gupta

Siblings (4)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.29601.2.48.1.1 fsMIIpDbNoOfBindings00
1.3.6.1.4.1.29601.2.48.1.2 fsMIIpDbNoOfStaticBindings00
1.3.6.1.4.1.29601.2.48.1.3 fsMIIpDbNoOfDHCPBindings00
1.3.6.1.4.1.29601.2.48.1.4 fsMIIpDbNoOfPPPBindings00