OID reference
1.3.6.1.4.1.5504.18.5.7
1.This object contains an appropriate value to be used for BITSTORM-HP-160AlmEventSeqId when creating entries in the BITSTORM-HP-160AlmEventTable. 2.This indicates the next sequential number used by the Event log table. 3.When wrote to 0, this indicates almLogTable will be clear.
Identification
{1 3 6 1 4 1 5504 18 5 7}
The displayed source records contain one distinct definition. Compare its source records.
BITSTORM-HP-160AlmEventSeqIdNext OBJECT-TYPE
SYNTAX Integer32 ( 0 .. 65535 )
MAX-ACCESS read-only
STATUS current
DESCRIPTION "1.This object contains an appropriate value to
be used for BITSTORM-HP-160AlmEventSeqId when creating
entries in the BITSTORM-HP-160AlmEventTable.
2.This indicates the next sequential number used by the Event log table.
3.When wrote to 0, this indicates almLogTable will be clear."
::= { BITSTORM-HP-160AlmMgt 7 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
1.This object contains an appropriate value to be used for BITSTORM-HP-160AlmEventSeqId when creating entries in the BITSTORM-HP-160AlmEventTable. 2.This indicates the next sequential number used by the Event log table. 3.When wrote to 0, this indicates almLogTable will be clear.
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: BITSTORM-HP-160AlmEventSeqIdNext
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"BITSTORM-HP-160AlmEventSeqIdNext",
"OBJECT-TYPE",
"SYNTAX",
"Integer32",
"(",
"0",
".",
".",
"65535",
")",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"1.This object contains an appropriate value to be used for BITSTORM-HP-160AlmEventSeqId when creating entries in the BITSTORM-HP-160AlmEventTable. 2.This indicates the next sequential number used by the Event log table. 3.When wrote to 0, this indicates almLogTable will be clear.\"",
"::=",
"{",
"BITSTORM-HP-160AlmMgt",
"7",
"}"
]
}Vendor MIB copy from the Observium Community archive.
Module: BITSTORM-HP-160-MIB
See published definition above
{'IF-MIB': ['ifIndex', 'InterfaceIndex'], 'RFC-1212': ['OBJECT-TYPE'], 'SNMPv2-TC': ['PhysAddress', 'RowStatus', 'TAddress', 'TEXTUAL-CONVENTION', 'TruthValue'], 'ENTITY-MIB': ['PhysicalIndex', 'entPhysicalIndex'], 'SNMPv2-SMI': ['Integer32', 'IpAddress', 'Unsigned32', 'NOTIFICATION-TYPE', 'enterprises', 'MODULE-IDENTITY', 'OBJECT-TYPE']}Source data warning: Recovered from a file whose complete MIB does not parse. The original assignment and definition are preserved. Registration and implementation details may be inaccurate; consult the original file. Other damaged or unresolved declarations are not established registrations. The declaration also has invalid SMI syntax; its type constraints were not validated.
· Download BITSTORM-HP-160-MIBRelated source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.5504.18.5.1 | BITSTORM-HP-160AlmMain | 4 | 4 | |
| 1.3.6.1.4.1.5504.18.5.2 | BITSTORM-HP-160AlmProfileTable | 1 | 4 | |
| 1.3.6.1.4.1.5504.18.5.3 | BITSTORM-HP-160AlmCurrentTable | 1 | 7 | |
| 1.3.6.1.4.1.5504.18.5.4 | BITSTORM-HP-160AlmTable | 1 | 8 | |
| 1.3.6.1.4.1.5504.18.5.5 | BITSTORM-HP-160AlmSeqIdNext | 0 | 0 | |
| 1.3.6.1.4.1.5504.18.5.6 | BITSTORM-HP-160AlmEventTable | 1 | 7 | |
| 1.3.6.1.4.1.5504.18.5.8 | BITSTORM-HP-160AlmClear | 0 | 0 | |
| 1.3.6.1.4.1.5504.18.5.9 | BITSTORM-HP-160AlmEventClear | 0 | 0 |