The node the alert was posted on. The node number starts from 0. The maximum number of node is 32.
Sources for this description
HPE networking MIB copies (LibreNMS/Observium Community)
OID reference
1.3.6.1.4.1.12925.1.7.1.4
The node the alert was posted on. The node number starts from 0. The maximum number of node is 32.
Identification
{1 3 6 1 4 1 12925 1 7 1 4}
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 ThreeParMIB, the row index index 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.12925.1.7.1.4.<index>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.
Published row index: index.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.12925.1.7.1.4
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.
nodeID OBJECT-TYPE
SYNTAX Unsigned32 ( 0 .. 31 )
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The node the alert was posted on. The node number starts
from 0. The maximum number of node is 32."
::= { alertEntry 4 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The node the alert was posted on. The node number starts from 0. The maximum number of node is 32.
HPE networking MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: nodeID
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"nodeID",
"OBJECT-TYPE",
"SYNTAX",
"Unsigned32",
"(",
"0",
".",
".",
"31",
")",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"The node the alert was posted on. The node number starts from 0. The maximum number of node is 32.\"",
"::=",
"{",
"alertEntry",
"4",
"}"
],
"syntax_tree": [
[
"ApplicationSyntax",
"Unsigned32",
[
"integerSubType",
[
[
0,
31
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The node the alert was posted on. The node number starts from 0. The maximum number of node is 32."
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive. HPE networking support.
Module: ThreeParMIB
See published definition above
{'SNMPv2-TC': ['DisplayString', 'TEXTUAL-CONVENTION'], 'SNMPv2-SMI': ['enterprises', 'MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'OBJECT-IDENTITY', 'Integer32', 'Unsigned32', 'Counter64'], 'SNMPv2-CONF': ['AGENT-CAPABILITIES', 'OBJECT-GROUP', 'MODULE-COMPLIANCE', 'NOTIFICATION-GROUP']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.12925.1.7.1.1 | index | 0 | 0 | |
| 1.3.6.1.4.1.12925.1.7.1.2 | severity | 0 | 0 | |
| 1.3.6.1.4.1.12925.1.7.1.3 | timeOccurred | 0 | 0 | |
| 1.3.6.1.4.1.12925.1.7.1.5 | component | 0 | 0 | |
| 1.3.6.1.4.1.12925.1.7.1.6 | details | 0 | 0 | |
| 1.3.6.1.4.1.12925.1.7.1.7 | id | 0 | 0 | |
| 1.3.6.1.4.1.12925.1.7.1.8 | messageCode | 0 | 0 | |
| 1.3.6.1.4.1.12925.1.7.1.9 | state | 0 | 0 | |
| 1.3.6.1.4.1.12925.1.7.1.10 | serialNumber | 0 | 0 | |
| 1.3.6.1.4.1.12925.1.7.1.11 | catalogKey | 0 | 0 | |
| 1.3.6.1.4.1.12925.1.7.1.12 | detailedMessage | 0 | 0 | |
| 1.3.6.1.4.1.12925.1.7.1.13 | tier | 0 | 0 | |
| 1.3.6.1.4.1.12925.1.7.1.14 | sparePartNumber | 0 | 0 | |
| 1.3.6.1.4.1.12925.1.7.1.15 | sysName | 0 | 0 |