OID reference

h3cSysIpeFileIndex

1.3.6.1.4.1.43.45.1.10.2.3.1.8.2.1.1

Description

There are two parts for the index depicted as follows: 31 15 0 +++++++++++++++++++++++++++++++++++ + physical index + IPE index + +++++++++++++++++++++++++++++++++++ From bit0 to bit15 (two bytes) is the IPE file index; IPE file Index is a monotonically increasing integer for the sole purpose of indexing events. When …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.43.45.1.10.2.3.1.8.2.1 (h3cSysIpeFileEntry)
Node code
1
Node name
h3cSysIpeFileIndex
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.43.45.1.10.2.3.1.8.2.1.1
URN notation
urn:oid:1.3.6.1.4.1.43.45.1.10.2.3.1.8.2.1.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cSystemMan(3) h3cSystemManMIBObjects(1) h3cSysIpeFile(8) h3cSysIpeFileTable(2) h3cSysIpeFileEntry(1) h3cSysIpeFileIndex(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cSystemMan(3) h3cSystemManMIBObjects(1) h3cSysIpeFile(8) h3cSysIpeFileTable(2) h3cSysIpeFileEntry(1) h3cSysIpeFileIndex(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cSystemMan(3) h3cSystemManMIBObjects(1) h3cSysIpeFile(8) h3cSysIpeFileTable(2) h3cSysIpeFileEntry(1) h3cSysIpeFileIndex(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cSystemMan(3) h3cSystemManMIBObjects(1) h3cSysIpeFile(8) h3cSysIpeFileTable(2) h3cSysIpeFileEntry(1) h3cSysIpeFileIndex(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cSystemMan(3) h3cSystemManMIBObjects(1) h3cSysIpeFile(8) h3cSysIpeFileTable(2) h3cSysIpeFileEntry(1) h3cSysIpeFileIndex(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cSystemMan(3) h3cSystemManMIBObjects(1) h3cSysIpeFile(8) h3cSysIpeFileTable(2) h3cSysIpeFileEntry(1) h3cSysIpeFileIndex(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cSystemMan(3) h3cSystemManMIBObjects(1) h3cSysIpeFile(8) h3cSysIpeFileTable(2) h3cSysIpeFileEntry(1) h3cSysIpeFileIndex(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cSystemMan(3) h3cSystemManMIBObjects(1) h3cSysIpeFile(8) h3cSysIpeFileTable(2) h3cSysIpeFileEntry(1) h3cSysIpeFileIndex(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cSystemMan(3) h3cSystemManMIBObjects(1) h3cSysIpeFile(8) h3cSysIpeFileTable(2) h3cSysIpeFileEntry(1) h3cSysIpeFileIndex(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cSystemMan(3) h3cSystemManMIBObjects(1) h3cSysIpeFile(8) h3cSysIpeFileTable(2) h3cSysIpeFileEntry(1) h3cSysIpeFileIndex(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cSystemMan(3) h3cSystemManMIBObjects(1) h3cSysIpeFile(8) h3cSysIpeFileTable(2) h3cSysIpeFileEntry(1) h3cSysIpeFileIndex(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cSystemMan(3) h3cSystemManMIBObjects(1) h3cSysIpeFile(8) h3cSysIpeFileTable(2) h3cSysIpeFileEntry(1) h3cSysIpeFileIndex(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cSystemMan(3) h3cSystemManMIBObjects(1) h3cSysIpeFile(8) h3cSysIpeFileTable(2) h3cSysIpeFileEntry(1) h3cSysIpeFileIndex(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cSystemMan(3) h3cSystemManMIBObjects(1) h3cSysIpeFile(8) h3cSysIpeFileTable(2) h3cSysIpeFileEntry(1) h3cSysIpeFileIndex(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cSystemMan(3) h3cSystemManMIBObjects(1) h3cSysIpeFile(8) h3cSysIpeFileTable(2) h3cSysIpeFileEntry(1) h3cSysIpeFileIndex(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cSystemMan(3) h3cSystemManMIBObjects(1) h3cSysIpeFile(8) h3cSysIpeFileTable(2) h3cSysIpeFileEntry(1) h3cSysIpeFileIndex(1)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/43/45/1/10/2/3/1/8/2/1/1
  • /ISO/Identified-Organization/6/1/4/1/43/45/1/10/2/3/1/8/2/1/1
  • /ISO/3/6/1/4/1/43/45/1/10/2/3/1/8/2/1/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysIpeFile/h3cSysIpeFileTable/h3cSysIpeFileEntry/h3cSysIpeFileIndex
  • /iso/identified-organization/dod/internet/private/enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysIpeFile/h3cSysIpeFileTable/h3cSysIpeFileEntry/h3cSysIpeFileIndex
  • /iso/identified-organization/dod/internet/private/enterprises/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysIpeFile/h3cSysIpeFileTable/h3cSysIpeFileEntry/h3cSysIpeFileIndex
  • /iso/identified-organization/dod/internet/private/enterprises/a3com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysIpeFile/h3cSysIpeFileTable/h3cSysIpeFileEntry/h3cSysIpeFileIndex
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysIpeFile/h3cSysIpeFileTable/h3cSysIpeFileEntry/h3cSysIpeFileIndex
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysIpeFile/h3cSysIpeFileTable/h3cSysIpeFileEntry/h3cSysIpeFileIndex
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysIpeFile/h3cSysIpeFileTable/h3cSysIpeFileEntry/h3cSysIpeFileIndex
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysIpeFile/h3cSysIpeFileTable/h3cSysIpeFileEntry/h3cSysIpeFileIndex
  • /iso/org/dod/internet/private/enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysIpeFile/h3cSysIpeFileTable/h3cSysIpeFileEntry/h3cSysIpeFileIndex
  • /iso/org/dod/internet/private/enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysIpeFile/h3cSysIpeFileTable/h3cSysIpeFileEntry/h3cSysIpeFileIndex
  • /iso/org/dod/internet/private/enterprises/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysIpeFile/h3cSysIpeFileTable/h3cSysIpeFileEntry/h3cSysIpeFileIndex
  • /iso/org/dod/internet/private/enterprises/a3com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysIpeFile/h3cSysIpeFileTable/h3cSysIpeFileEntry/h3cSysIpeFileIndex
  • /iso/org/dod/internet/private/ldap-enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysIpeFile/h3cSysIpeFileTable/h3cSysIpeFileEntry/h3cSysIpeFileIndex
  • /iso/org/dod/internet/private/ldap-enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysIpeFile/h3cSysIpeFileTable/h3cSysIpeFileEntry/h3cSysIpeFileIndex
  • /iso/org/dod/internet/private/vendor-objects/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysIpeFile/h3cSysIpeFileTable/h3cSysIpeFileEntry/h3cSysIpeFileIndex
  • /iso/org/dod/internet/private/vendor-objects/a3com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysIpeFile/h3cSysIpeFileTable/h3cSysIpeFileEntry/h3cSysIpeFileIndex
  • Additional combinations skipped.

SNMP properties

Value type
Integer32
Maximum access defined by MIB
not-accessible
Status in MIB
current
Allowed ranges
1–2147483647

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-SYS-MAN-MIB, the row index h3cSysIpeFileIndex is declared as Integer32. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.43.45.1.10.2.3.1.8.2.1.1.<h3cSysIpeFileIndex>. Use an index value actually 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

h3cSysIpeFileIndex · current

h3cSysIpeFileIndex OBJECT-TYPE
    SYNTAX Integer32 (1..2147483647)
    MAX-ACCESS not-accessible
    STATUS current
    DESCRIPTION
        "There are two parts for the index depicted as follows:

        31                15             0
        +++++++++++++++++++++++++++++++++++
        + physical index   +  IPE   index +
        +++++++++++++++++++++++++++++++++++

        From bit0 to bit15 (two bytes) is the IPE file index; IPE file Index
        is a monotonically increasing integer for the sole purpose of indexing
        events.  When it reaches the maximum value, an extremely unlikely
        event, the agent wraps the value back to 1 and may flush existing
        entries.

        From bit16 to bit31 (two bytes) is the physical index the same as the
        entPhysicalIndex specified in ENTITY-MIB.

        Any index beyond the above range will not be supported.

        If a file is added in, its h3cSysIpeFileIndex will be the maximum image
        ndex plus one.
        If the IPE file is removed, renamed, or moved from one place to
        another, its h3cSysIpeFileIndex is not reallocated.
        If the IPE file's content is replaced, its h3cSysIpeFileIndex will not
        change.
        "
    ::= { h3cSysIpeFileEntry 1 }

h3cSysIpeFileIndex · current

h3cSysIpeFileIndex OBJECT-TYPE
    SYNTAX Integer32 (1..2147483647)
    MAX-ACCESS not-accessible
    STATUS current
    DESCRIPTION
        "There are two parts for the index depicted as follows:

        31                15             0
        +++++++++++++++++++++++++++++++++++
        + physical index   +  IPE   index +
        +++++++++++++++++++++++++++++++++++

        From bit0 to bit15 (two bytes) is the IPE file index; IPE file Index
        is a monotonically increasing integer for the sole purpose of indexing
        events.  When it reaches the maximum value, an extremely unlikely
        event, the agent wraps the value back to 1 and may flush existing
        entries.

        From bit16 to bit31 (two bytes) is the physical index the same as the
        entPhysicalIndex specified in ENTITY-MIB.

        Any index beyond the above range will not be supported.

        If a file is added in, its h3cSysIpeFileIndex will be the maximum image
        ndex plus one.
        If the IPE file is removed, renamed, or moved from one place to
        another, its h3cSysIpeFileIndex is not reallocated.
        If the IPE file's content is replaced, its h3cSysIpeFileIndex will not
        change.
        "
    ::= { h3cSysIpeFileEntry 1 }

Meaning

Descriptions

1 unique

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

There are two parts for the index depicted as follows: 31 15 0 +++++++++++++++++++++++++++++++++++ + physical index + IPE index + +++++++++++++++++++++++++++++++++++ From bit0 to bit15 (two bytes) is the IPE file index; IPE file Index is a monotonically increasing integer for the sole purpose of indexing events. When it reaches the maximum value, an extremely unlikely event, the agent wraps the value back to 1 and may flush existing entries. From bit16 to bit31 (two bytes) is the physical index the same as the entPhysicalIndex specified in ENTITY-MIB. Any index beyond the above range will not be supported. If a file is added in, its h3cSysIpeFileIndex will be the maximum image ndex plus one. If the IPE file is removed, renamed, or moved from one place to another, its h3cSysIpeFileIndex is not reallocated. If the IPE file's content is replaced, its h3cSysIpeFileIndex will not change.

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 · 2 sources

Description 1

h3cSysIpeFileIndex · current3Com MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies2 sources

Status in source: current.

Names: h3cSysIpeFileIndex

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "h3cSysIpeFileIndex",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "(",
    "1",
    ".",
    ".",
    "2147483647",
    ")",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"There are two parts for the index depicted as follows: 31 15 0 +++++++++++++++++++++++++++++++++++ + physical index + IPE index + +++++++++++++++++++++++++++++++++++ From bit0 to bit15 (two bytes) is the IPE file index; IPE file Index is a monotonically increasing integer for the sole purpose of indexing events. When it reaches the maximum value, an extremely unlikely event, the agent wraps the value back to 1 and may flush existing entries. From bit16 to bit31 (two bytes) is the physical index the same as the entPhysicalIndex specified in ENTITY-MIB. Any index beyond the above range will not be supported. If a file is added in, its h3cSysIpeFileIndex will be the maximum image ndex plus one. If the IPE file is removed, renamed, or moved from one place to another, its h3cSysIpeFileIndex is not reallocated. If the IPE file's content is replaced, its h3cSysIpeFileIndex will not change. \"",
    "::=",
    "{",
    "h3cSysIpeFileEntry",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32",
      [
        "integerSubType",
        [
          [
            1,
            2147483647
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "There are two parts for the index depicted as follows: 31 15 0 +++++++++++++++++++++++++++++++++++ + physical index + IPE index + +++++++++++++++++++++++++++++++++++ From bit0 to bit15 (two bytes) is the IPE file index; IPE file Index is a monotonically increasing integer for the sole purpose of indexing events. When it reaches the maximum value, an extremely unlikely event, the agent wraps the value back to 1 and may flush existing entries. From bit16 to bit31 (two bytes) is the physical index the same as the entPhysicalIndex specified in ENTITY-MIB. Any index beyond the above range will not be supported. If a file is added in, its h3cSysIpeFileIndex will be the maximum image ndex plus one. If the IPE file is removed, renamed, or moved from one place to another, its h3cSysIpeFileIndex is not reallocated. If the IPE file's content is replaced, its h3cSysIpeFileIndex will not change."
    ],
    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.10.2.3.1.8.2.1.2 h3cSysIpeFileName00
1.3.6.1.4.1.43.45.1.10.2.3.1.8.2.1.3 h3cSysIpeFileSize00
1.3.6.1.4.1.43.45.1.10.2.3.1.8.2.1.4 h3cSysIpeFileLocation00