OID reference
1.3.6.1.4.1.3715.99.2.1.1.1.4
Rack number of the module. This can be used to identify the physical position of the module in the case where the agent manages modules that are in several racks.
Identification
{1 3 6 1 4 1 3715 99 2 1 1 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 TELESTE-COMMON-MIB, the row index moduleId is declared as INTEGER. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.3715.99.2.1.1.1.4.<moduleId>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.3715.99.2.1.1.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.
moduleRackNo OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS optional
DESCRIPTION
"Rack number of the module.
This can be used to identify the physical position of
the module in the case where the agent manages modules
that are in several racks."
::= { moduleEntry 4 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Rack number of the module. This can be used to identify the physical position of the module in the case where the agent manages modules that are in several racks.
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)Netdisco MIB archive copies
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: optional.
Names: moduleRackNo
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"moduleRackNo",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"ACCESS",
"read-write",
"STATUS",
"optional",
"DESCRIPTION",
"\"Rack number of the module. This can be used to identify the physical position of the module in the case where the agent manages modules that are in several racks.\"",
"::=",
"{",
"moduleEntry",
"4",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"optional"
],
[
"DESCRIPTION",
"Rack number of the module. This can be used to identify the physical position of the module in the case where the agent manages modules that are in several racks."
],
null,
null,
null,
null
]
}Vendor MIB copy from the LibreNMS archive.
Module: TELESTE-COMMON-MIB
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['IpAddress', 'Counter'], 'RFC1213-MIB': ['DisplayString'], 'TELESTE-ROOT-MIB': ['common', 'TPhysAddress', 'Uint16', 'DateAndTime']}Related source files and packages:
Vendor MIB copy from the Observium Community archive.
Module: TELESTE-COMMON-MIB
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['IpAddress', 'Counter'], 'RFC1213-MIB': ['DisplayString'], 'TELESTE-ROOT-MIB': ['common', 'TPhysAddress', 'Uint16', 'DateAndTime']}Related source files and packages:
Vendor MIB copy from the Netdisco archive.
Module: TELESTE-COMMON-MIB
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['IpAddress', 'Counter'], 'RFC1213-MIB': ['DisplayString'], 'TELESTE-ROOT-MIB': ['common', 'TPhysAddress', 'Uint16', 'DateAndTime']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.3715.99.2.1.1.1.1 | moduleId | 0 | 0 | |
| 1.3.6.1.4.1.3715.99.2.1.1.1.2 | moduleName | 0 | 0 | |
| 1.3.6.1.4.1.3715.99.2.1.1.1.3 | moduleHwType | 0 | 0 | |
| 1.3.6.1.4.1.3715.99.2.1.1.1.5 | moduleSlotNo | 0 | 0 |