OID reference
1.3.6.1.4.1.2.3.51.2.24.4.1.2
The port number of a port on this node. Note that this port number is 0-based, but since it is used as the table index (0 is not allowed), it will be presented as one more than the actual port number.
Identification
{1 3 6 1 4 1 2 3 51 2 24 4 1 2}
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 BLADE-MIB, the row index consists of these components in order:
scalableComplexNodePortSlot (INTEGER): one numeric subidentifier for the non-negative value.scalableComplexNodePortNum (INTEGER): one numeric subidentifier for the non-negative value.An instance has the form .1.3.6.1.4.1.2.3.51.2.24.4.1.2.<scalableComplexNodePortSlot>.<scalableComplexNodePortNum>. Use values present on the device and permitted by its MIB. Other definitions can differ.
Published row index: scalableComplexNodePortSlot, scalableComplexNodePortNum.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.2.3.51.2.24.4.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.
scalableComplexNodePortNum OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The port number of a port on this node. Note that this port
number is 0-based, but since it is used as the table index
(0 is not allowed), it will be presented as one more than the
actual port number."
::= { scalableComplexNodePortEntry 2 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The port number of a port on this node. Note that this port number is 0-based, but since it is used as the table index (0 is not allowed), it will be presented as one more than the actual port number.
IBM MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: mandatory.
Names: scalableComplexNodePortNum
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"scalableComplexNodePortNum",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"ACCESS",
"read-only",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"The port number of a port on this node. Note that this port number is 0-based, but since it is used as the table index (0 is not allowed), it will be presented as one more than the actual port number.\"",
"::=",
"{",
"scalableComplexNodePortEntry",
"2",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER"
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"The port number of a port on this node. Note that this port number is 0-based, but since it is used as the table index (0 is not allowed), it will be presented as one more than the actual port number."
],
null,
null,
null,
null
]
}Vendor MIB copy from the LibreNMS archive. IBM support.
Module: BLADE-MIB
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'RFC-1215': ['TRAP-TYPE'], 'RFC1155-SMI': ['enterprises', 'IpAddress']}Related source files and packages:
Same file in Observium Community.
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.2.3.51.2.24.4.1.1 | scalableComplexNodePortSlot | 0 | 0 | |
| 1.3.6.1.4.1.2.3.51.2.24.4.1.3 | scalableComplexNodePortRemChkSum | 0 | 0 | |
| 1.3.6.1.4.1.2.3.51.2.24.4.1.4 | scalableComplexNodePortRemNum | 0 | 0 | |
| 1.3.6.1.4.1.2.3.51.2.24.4.1.5 | scalableComplexNodePortStatus | 0 | 0 | |
| 1.3.6.1.4.1.2.3.51.2.24.4.1.6 | scalableComplexNodePortType | 0 | 0 |