OID reference

hwBufModuleIndex

1.3.6.1.4.1.43.45.1.6.1.2.2.1.1

Description

Index of hwBufferTable. This integer is a uniq number to identify the buffer module. We recommand two Number Plans in this paper, Logical Number or Phisical Number. For the first case, hwBufferModuleIndex is a integer, range from 1 to the Maximum number, for example 1,2,3,4,5 ..., where 1 represents the first buffer m…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.43.45.1.6.1.2.2.1 (hwBufEntry)
Node code
1
Node name
hwBufModuleIndex
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.43.45.1.6.1.2.2.1.1
URN notation
urn:oid:1.3.6.1.4.1.43.45.1.6.1.2.2.1.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 43 45 1 6 1 2 2 1 1}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) a3Com(43) jv-mib(45) huawei(1) huaweiUtility(6) hwDevice(1) hwMem(2) hwBufTable(2) hwBufEntry(1) hwBufModuleIndex(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) a3com(43) jv-mib(45) huawei(1) huaweiUtility(6) hwDevice(1) hwMem(2) hwBufTable(2) hwBufEntry(1) hwBufModuleIndex(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) a3Com(43) jv-mib(45) huawei(1) huaweiUtility(6) hwDevice(1) hwMem(2) hwBufTable(2) hwBufEntry(1) hwBufModuleIndex(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) a3com(43) jv-mib(45) huawei(1) huaweiUtility(6) hwDevice(1) hwMem(2) hwBufTable(2) hwBufEntry(1) hwBufModuleIndex(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3Com(43) jv-mib(45) huawei(1) huaweiUtility(6) hwDevice(1) hwMem(2) hwBufTable(2) hwBufEntry(1) hwBufModuleIndex(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3com(43) jv-mib(45) huawei(1) huaweiUtility(6) hwDevice(1) hwMem(2) hwBufTable(2) hwBufEntry(1) hwBufModuleIndex(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) a3Com(43) jv-mib(45) huawei(1) huaweiUtility(6) hwDevice(1) hwMem(2) hwBufTable(2) hwBufEntry(1) hwBufModuleIndex(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) a3com(43) jv-mib(45) huawei(1) huaweiUtility(6) hwDevice(1) hwMem(2) hwBufTable(2) hwBufEntry(1) hwBufModuleIndex(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) a3Com(43) jv-mib(45) huawei(1) huaweiUtility(6) hwDevice(1) hwMem(2) hwBufTable(2) hwBufEntry(1) hwBufModuleIndex(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) a3com(43) jv-mib(45) huawei(1) huaweiUtility(6) hwDevice(1) hwMem(2) hwBufTable(2) hwBufEntry(1) hwBufModuleIndex(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) a3Com(43) jv-mib(45) huawei(1) huaweiUtility(6) hwDevice(1) hwMem(2) hwBufTable(2) hwBufEntry(1) hwBufModuleIndex(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) a3com(43) jv-mib(45) huawei(1) huaweiUtility(6) hwDevice(1) hwMem(2) hwBufTable(2) hwBufEntry(1) hwBufModuleIndex(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3Com(43) jv-mib(45) huawei(1) huaweiUtility(6) hwDevice(1) hwMem(2) hwBufTable(2) hwBufEntry(1) hwBufModuleIndex(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3com(43) jv-mib(45) huawei(1) huaweiUtility(6) hwDevice(1) hwMem(2) hwBufTable(2) hwBufEntry(1) hwBufModuleIndex(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) a3Com(43) jv-mib(45) huawei(1) huaweiUtility(6) hwDevice(1) hwMem(2) hwBufTable(2) hwBufEntry(1) hwBufModuleIndex(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) a3com(43) jv-mib(45) huawei(1) huaweiUtility(6) hwDevice(1) hwMem(2) hwBufTable(2) hwBufEntry(1) hwBufModuleIndex(1)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/43/45/1/6/1/2/2/1/1
  • /ISO/Identified-Organization/6/1/4/1/43/45/1/6/1/2/2/1/1
  • /ISO/3/6/1/4/1/43/45/1/6/1/2/2/1/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/a3Com/jv-mib/huawei/huaweiUtility/hwDevice/hwMem/hwBufTable/hwBufEntry/hwBufModuleIndex
  • /iso/identified-organization/dod/internet/private/enterprise/a3com/jv-mib/huawei/huaweiUtility/hwDevice/hwMem/hwBufTable/hwBufEntry/hwBufModuleIndex
  • /iso/identified-organization/dod/internet/private/enterprises/a3Com/jv-mib/huawei/huaweiUtility/hwDevice/hwMem/hwBufTable/hwBufEntry/hwBufModuleIndex
  • /iso/identified-organization/dod/internet/private/enterprises/a3com/jv-mib/huawei/huaweiUtility/hwDevice/hwMem/hwBufTable/hwBufEntry/hwBufModuleIndex
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3Com/jv-mib/huawei/huaweiUtility/hwDevice/hwMem/hwBufTable/hwBufEntry/hwBufModuleIndex
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3com/jv-mib/huawei/huaweiUtility/hwDevice/hwMem/hwBufTable/hwBufEntry/hwBufModuleIndex
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3Com/jv-mib/huawei/huaweiUtility/hwDevice/hwMem/hwBufTable/hwBufEntry/hwBufModuleIndex
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3com/jv-mib/huawei/huaweiUtility/hwDevice/hwMem/hwBufTable/hwBufEntry/hwBufModuleIndex
  • /iso/org/dod/internet/private/enterprise/a3Com/jv-mib/huawei/huaweiUtility/hwDevice/hwMem/hwBufTable/hwBufEntry/hwBufModuleIndex
  • /iso/org/dod/internet/private/enterprise/a3com/jv-mib/huawei/huaweiUtility/hwDevice/hwMem/hwBufTable/hwBufEntry/hwBufModuleIndex
  • /iso/org/dod/internet/private/enterprises/a3Com/jv-mib/huawei/huaweiUtility/hwDevice/hwMem/hwBufTable/hwBufEntry/hwBufModuleIndex
  • /iso/org/dod/internet/private/enterprises/a3com/jv-mib/huawei/huaweiUtility/hwDevice/hwMem/hwBufTable/hwBufEntry/hwBufModuleIndex
  • /iso/org/dod/internet/private/ldap-enterprise/a3Com/jv-mib/huawei/huaweiUtility/hwDevice/hwMem/hwBufTable/hwBufEntry/hwBufModuleIndex
  • /iso/org/dod/internet/private/ldap-enterprise/a3com/jv-mib/huawei/huaweiUtility/hwDevice/hwMem/hwBufTable/hwBufEntry/hwBufModuleIndex
  • /iso/org/dod/internet/private/vendor-objects/a3Com/jv-mib/huawei/huaweiUtility/hwDevice/hwMem/hwBufTable/hwBufEntry/hwBufModuleIndex
  • /iso/org/dod/internet/private/vendor-objects/a3com/jv-mib/huawei/huaweiUtility/hwDevice/hwMem/hwBufTable/hwBufEntry/hwBufModuleIndex
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
not-accessible
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.

In A3COM-HUAWEI-LswDEVM-MIB, the row index consists of these components in order:

  1. hwBufModuleIndex (INTEGER): one numeric subidentifier for the non-negative value.
  2. hwBufSize (INTEGER): one numeric subidentifier for the non-negative value.

An instance has the form .1.3.6.1.4.1.43.45.1.6.1.2.2.1.1.<hwBufModuleIndex>.<hwBufSize>. Use values present on the device and permitted by its MIB. Other definitions can differ.

A query example is omitted because the source variants do not establish compatible read access.

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

hwBufModuleIndex · current

hwBufModuleIndex   OBJECT-TYPE
    SYNTAX  INTEGER
    MAX-ACCESS  not-accessible
    STATUS  current
    DESCRIPTION
            "Index of hwBufferTable. This integer is a  uniq number to
             identify the buffer module. We recommand two Number Plans
             in this paper, Logical Number or Phisical Number. For the
             first case, hwBufferModuleIndex is a integer, range from 1 to
             the Maximum number, for example 1,2,3,4,5 ..., where 1
             represents the first buffer module, 2 represents the second
             buffer module, etc.  For the second case hwBufferModuleIndex
             represents physical card position (Shelf Number, Frame Number,
             Slot Number, SubSlotNumber) where the buffer module residing,
             for example, 0x01020304 represent the buffer module on the 4th
             subslot of the 3th slot of the 2nd frame of the 1st Shelf. "
    ::= { hwBufEntry  1 }

hwBufModuleIndex · current

hwBufModuleIndex   OBJECT-TYPE
    SYNTAX  INTEGER
    MAX-ACCESS  not-accessible
    STATUS  current
    DESCRIPTION
            "Index of hwBufferTable. This integer is a  uniq number to
             identify the buffer module. We recommand two Number Plans
             in this paper, Logical Number or Phisical Number. For the
             first case, hwBufferModuleIndex is a integer, range from 1 to
             the Maximum number, for example 1,2,3,4,5 ..., where 1
             represents the first buffer module, 2 represents the second
             buffer module, etc.  For the second case hwBufferModuleIndex
             represents physical card position (Shelf Number, Frame Number,
             Slot Number, SubSlotNumber) where the buffer module residing,
             for example, 0x01020304 represent the buffer module on the 4th
             subslot of the 3th slot of the 2nd frame of the 1st Shelf. "
    ::= { hwBufEntry  1 }

Meaning

Descriptions

1 unique

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

Index of hwBufferTable. This integer is a uniq number to identify the buffer module. We recommand two Number Plans in this paper, Logical Number or Phisical Number. For the first case, hwBufferModuleIndex is a integer, range from 1 to the Maximum number, for example 1,2,3,4,5 ..., where 1 represents the first buffer module, 2 represents the second buffer module, etc. For the second case hwBufferModuleIndex represents physical card position (Shelf Number, Frame Number, Slot Number, SubSlotNumber) where the buffer module residing, for example, 0x01020304 represent the buffer module on the 4th subslot of the 3th slot of the 2nd frame of the 1st Shelf.

Sources for this description

3Com MIB copies (LibreNMS/Observium Community)Netdisco MIB archive copies

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 13Com MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies1 record · 3 sources

Description 1

hwBufModuleIndex · current3Com MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies3 sources

Status in source: current.

Names: hwBufModuleIndex

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "hwBufModuleIndex",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Index of hwBufferTable. This integer is a uniq number to identify the buffer module. We recommand two Number Plans in this paper, Logical Number or Phisical Number. For the first case, hwBufferModuleIndex is a integer, range from 1 to the Maximum number, for example 1,2,3,4,5 ..., where 1 represents the first buffer module, 2 represents the second buffer module, etc. For the second case hwBufferModuleIndex represents physical card position (Shelf Number, Frame Number, Slot Number, SubSlotNumber) where the buffer module residing, for example, 0x01020304 represent the buffer module on the 4th subslot of the 3th slot of the 2nd frame of the 1st Shelf. \"",
    "::=",
    "{",
    "hwBufEntry",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER"
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Index of hwBufferTable. This integer is a uniq number to identify the buffer module. We recommand two Number Plans in this paper, Logical Number or Phisical Number. For the first case, hwBufferModuleIndex is a integer, range from 1 to the Maximum number, for example 1,2,3,4,5 ..., where 1 represents the first buffer module, 2 represents the second buffer module, etc. For the second case hwBufferModuleIndex represents physical card position (Shelf Number, Frame Number, Slot Number, SubSlotNumber) where the buffer module residing, for example, 0x01020304 represent the buffer module on the 4th subslot of the 3th slot of the 2nd frame of the 1st Shelf."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.43)

Jeremy Siegel

Siblings (3)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.43.45.1.6.1.2.2.1.2 hwBufSize00
1.3.6.1.4.1.43.45.1.6.1.2.2.1.3 hwBufCurrentTotal00
1.3.6.1.4.1.43.45.1.6.1.2.2.1.4 hwBufCurrentUsed00