Five digit Element ID to be included in Event Message header. Must be unique network-wide.
Sources for this description
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
OID reference
1.3.6.1.4.1.4998.1.1.115.1.5.1.2
Five digit Element ID to be included in Event Message header. Must be unique network-wide.
Identification
{1 3 6 1 4 1 4998 1 1 115 1 5 1 2}
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.4998.1.1.115.1.5.1.2.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.
cadEvMsgElementId OBJECT-TYPE
SYNTAX Unsigned32(0..100000)
MAX-ACCESS read-write
STATUS current
DESCRIPTION "Five digit Element ID to be included in Event Message header.
Must be unique network-wide."
REFERENCE "'Cadant CMTS Requirements for PacketCable' requirement 4.2.0.0.2"
DEFVAL {100000}
::= { cadEvMsgMibBase 2 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Five digit Element ID to be included in Event Message header. Must be unique network-wide.
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: cadEvMsgElementId
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"cadEvMsgElementId",
"OBJECT-TYPE",
"SYNTAX",
"Unsigned32",
"(",
"0",
".",
".",
"100000",
")",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"Five digit Element ID to be included in Event Message header. Must be unique network-wide.\"",
"REFERENCE",
"\"'Cadant CMTS Requirements for PacketCable' requirement 4.2.0.0.2\"",
"DEFVAL",
"{",
"100000",
"}",
"::=",
"{",
"cadEvMsgMibBase",
"2",
"}"
],
"syntax_tree": [
[
"ApplicationSyntax",
"Unsigned32",
[
"integerSubType",
[
[
0,
100000
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Five digit Element ID to be included in Event Message header. Must be unique network-wide."
],
[
"REFERENCE",
"'Cadant CMTS Requirements for PacketCable' requirement 4.2.0.0.2"
],
null,
null,
[
"DEFVAL",
100000
]
]
}Vendor MIB copy from the Observium Community archive.
Module: CADANT-CMTS-PC-EVENTMSG-MIB
See published definition above
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'RowStatus', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'IpAddress', 'Unsigned32'], 'CADANT-CMTS-PACKETCABLE-MIB': ['cadPCMibObjects']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.4998.1.1.115.1.5.1.1 | cadEvMsgElementType | 0 | 0 | |
| 1.3.6.1.4.1.4998.1.1.115.1.5.1.3 | cadEvMsgMaxAge | 0 | 0 | |
| 1.3.6.1.4.1.4998.1.1.115.1.5.1.4 | cadEvMsgRetransTimer | 0 | 0 | |
| 1.3.6.1.4.1.4998.1.1.115.1.5.1.5 | cadEvMsgMaxRetry | 0 | 0 | |
| 1.3.6.1.4.1.4998.1.1.115.1.5.1.6 | cadEvMsgMaxBatchSize | 0 | 0 | |
| 1.3.6.1.4.1.4998.1.1.115.1.5.1.7 | cadEvMsgEnableFlag | 0 | 0 |