OID reference
1.3.6.1.4.1.42359.2.2.2.3.1.4
Name of alarm object within a device based on YANG naming. Note that the granularity must be good enough to guarantee unique alarm states and relevant resource identification to the operator.
Identification
{1 3 6 1 4 1 42359 2 2 2 3 1 4}
At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.
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.
The displayed source records contain one distinct definition. Compare its source records.
alarmObject OBJECT-TYPE
SYNTAX OCTET STRING(SIZE(0..255))
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"Name of alarm object within a device based on YANG
naming. Note that the granularity must be good enough to
guarantee unique alarm states and relevant resource
identification to the operator."
::= { trapObjects 4 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Name of alarm object within a device based on YANG naming. Note that the granularity must be good enough to guarantee unique alarm states and relevant resource identification to the operator.
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: alarmObject
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"alarmObject",
"OBJECT-TYPE",
"SYNTAX",
"OCTET",
"STRING",
"(",
"SIZE",
"(",
"0",
".",
".",
"255",
")",
")",
"MAX-ACCESS",
"accessible-for-notify",
"STATUS",
"current",
"DESCRIPTION",
"\"Name of alarm object within a device based on YANG naming. Note that the granularity must be good enough to guarantee unique alarm states and relevant resource identification to the operator.\"",
"::=",
"{",
"trapObjects",
"4",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"OCTET STRING",
[
"octetStringSubType",
[
[
0,
255
]
]
]
],
null,
[
"MaxAccessPart",
"accessible-for-notify"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Name of alarm object within a device based on YANG naming. Note that the granularity must be good enough to guarantee unique alarm states and relevant resource identification to the operator."
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive.
Module: TRAPS-COMMON
See published definition above
{'SNMPv2-TC': ['TruthValue', 'DateAndTime'], 'VERSA-MIB': ['notifications'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString'], 'IANA-ITU-ALARM-TC-MIB': ['IANAItuEventType', 'IANAItuProbableCause']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.42359.2.2.2.3.1.1 | alarmIndex | 0 | 0 | |
| 1.3.6.1.4.1.42359.2.2.2.3.1.2 | alarmType | 0 | 0 | |
| 1.3.6.1.4.1.42359.2.2.2.3.1.3 | alarmDevice | 0 | 0 | |
| 1.3.6.1.4.1.42359.2.2.2.3.1.5 | alarmObjectOID | 0 | 0 | |
| 1.3.6.1.4.1.42359.2.2.2.3.1.6 | alarmSpecificProblem | 0 | 0 | |
| 1.3.6.1.4.1.42359.2.2.2.3.1.7 | alarmClass | 0 | 0 | |
| 1.3.6.1.4.1.42359.2.2.2.3.1.8 | alarmEventType | 0 | 0 | |
| 1.3.6.1.4.1.42359.2.2.2.3.1.9 | alarmProbableCause | 0 | 0 | |
| 1.3.6.1.4.1.42359.2.2.2.3.1.10 | alarmOrigTime | 0 | 0 | |
| 1.3.6.1.4.1.42359.2.2.2.3.1.11 | alarmTime | 0 | 0 | |
| 1.3.6.1.4.1.42359.2.2.2.3.1.12 | alarmSeverity | 0 | 0 | |
| 1.3.6.1.4.1.42359.2.2.2.3.1.13 | alarmHasClear | 0 | 0 | |
| 1.3.6.1.4.1.42359.2.2.2.3.1.14 | alarmText | 0 | 0 | |
| 1.3.6.1.4.1.42359.2.2.2.3.1.15 | tenantName | 0 | 0 | |
| 1.3.6.1.4.1.42359.2.2.2.3.1.16 | thresholdStatus | 0 | 0 | |
| 1.3.6.1.4.1.42359.2.2.2.3.1.17 | currentUtilization | 0 | 0 | |
| 1.3.6.1.4.1.42359.2.2.2.3.1.18 | alarmKey | 0 | 0 |