OID reference
1.3.6.1.4.1.641.6.5.1.1.2
The subnode of the device node that indicates the table the holds information about the item this alert refers to. For instance, if the alert is a hardware alert, this object should hold the value of '2', indicating that the alert is for a member of the device.hwInventoryTable. Common values of this would be 2 -> hwIn…
Identification
{1 3 6 1 4 1 641 6 5 1 1 2}
| Value | Name |
|---|---|
| 0 | unknown |
| 2 | hwInventoryTable |
| 3 | supplyInventoryTable |
| 4 | swInventoryTable |
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 LEXMARK-MPS-MIB, the row index consists of these components in order:
deviceIndex (Integer32): one numeric subidentifier for the non-negative value.deviceAlertIndex (Integer32): one numeric subidentifier for the non-negative value.An instance has the form .1.3.6.1.4.1.641.6.5.1.1.2.<deviceIndex>.<deviceAlertIndex>. Use values present on the device and permitted by its MIB. Other definitions can differ.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.641.6.5.1.1.2
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.
deviceAlertConfigTableNode OBJECT-TYPE
SYNTAX INTEGER {
unknown(0),
hwInventoryTable(2),
supplyInventoryTable(3),
swInventoryTable(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The subnode of the device node that indicates the table the holds
information about the item this alert refers to. For instance, if
the alert is a hardware alert, this object should hold the value of
'2', indicating that the alert is for a member of the
device.hwInventoryTable. Common values of this would be
2 -> hwInventoryTable
3 -> supplyInventoryTable
4 -> swInventoryTable"
::= { deviceAlertEntry 2 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The subnode of the device node that indicates the table the holds information about the item this alert refers to. For instance, if the alert is a hardware alert, this object should hold the value of '2', indicating that the alert is for a member of the device.hwInventoryTable. Common values of this would be 2 -> hwInventoryTable 3 -> supplyInventoryTable 4 -> swInventoryTable
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: deviceAlertConfigTableNode
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"deviceAlertConfigTableNode",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"unknown",
"(",
"0",
")",
",",
"hwInventoryTable",
"(",
"2",
")",
",",
"supplyInventoryTable",
"(",
"3",
")",
",",
"swInventoryTable",
"(",
"4",
")",
"}",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"The subnode of the device node that indicates the table the holds information about the item this alert refers to. For instance, if the alert is a hardware alert, this object should hold the value of '2', indicating that the alert is for a member of the device.hwInventoryTable. Common values of this would be 2 -> hwInventoryTable 3 -> supplyInventoryTable 4 -> swInventoryTable\"",
"::=",
"{",
"deviceAlertEntry",
"2",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"unknown",
0
],
[
"hwInventoryTable",
2
],
[
"supplyInventoryTable",
3
],
[
"swInventoryTable",
4
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The subnode of the device node that indicates the table the holds information about the item this alert refers to. For instance, if the alert is a hardware alert, this object should hold the value of '2', indicating that the alert is for a member of the device.hwInventoryTable. Common values of this would be 2 -> hwInventoryTable 3 -> supplyInventoryTable 4 -> swInventoryTable"
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive.
Module: LEXMARK-MPS-MIB
See published definition above
{'SNMPv2-TC': ['DateAndTime', 'DisplayString', 'TEXTUAL-CONVENTION'], 'SNMPv2-SMI': ['Counter32', 'Integer32', 'MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE'], 'Printer-MIB': ['PrtAlertCodeTC', 'PrtAlertTrainingLevelTC', 'PrtAlertSeverityLevelTC', 'PrtOutputPageDeliveryOrientationTC'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP'], 'LEXMARK-TC-MIB': ['UnitsTC', 'PaperSizeTC', 'PaperTypeTC', 'AdminStatusTC', 'StatusTC', 'KeyValueTC'], 'LEXMARK-ROOT-MIB': ['lexmark', 'lexmarkModules'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.641.6.5.1.1.1 | deviceAlertIndex | 0 | 0 | |
| 1.3.6.1.4.1.641.6.5.1.1.3 | deviceAlertConfigTableIndex | 0 | 0 | |
| 1.3.6.1.4.1.641.6.5.1.1.4 | deviceAlertSeverity | 0 | 0 | |
| 1.3.6.1.4.1.641.6.5.1.1.5 | deviceAlertCode | 0 | 0 | |
| 1.3.6.1.4.1.641.6.5.1.1.6 | deviceAlertDescription | 0 | 0 | |
| 1.3.6.1.4.1.641.6.5.1.1.7 | deviceAlertData | 0 | 0 | |
| 1.3.6.1.4.1.641.6.5.1.1.8 | deviceAlertTime | 0 | 0 | |
| 1.3.6.1.4.1.641.6.5.1.1.9 | deviceAlertSeverityLevel | 0 | 0 | |
| 1.3.6.1.4.1.641.6.5.1.1.10 | deviceAlertTrainingLevel | 0 | 0 | |
| 1.3.6.1.4.1.641.6.5.1.1.11 | deviceAlertPrtCode | 0 | 0 |