OID reference
1.3.6.1.4.1.15004.3
The root object identifier from which MIBs produced by other companies may be placed. MIBs produced by other enterprises are typically implemented with the object identifiers as defined in the MIB, but if the MIB is deemed to be uncontrolelled, we may reroot the MIB at this subtree in order to have a controlled versio…
Identification
{1 3 6 1 4 1 15004 3}
The displayed source records contain one distinct definition. Compare its source records.
ruggedcomOtherEnterprises OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The root object identifier from which MIBs produced by other
companies may be placed. MIBs produced by other enterprises
are typically implemented with the object identifiers as defined
in the MIB, but if the MIB is deemed to be uncontrolelled, we may
reroot the MIB at this subtree in order to have a controlled
version."
::= { ruggedcom 3 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The root object identifier from which MIBs produced by other companies may be placed. MIBs produced by other enterprises are typically implemented with the object identifiers as defined in the MIB, but if the MIB is deemed to be uncontrolelled, we may reroot the MIB at this subtree in order to have a controlled version.
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: ruggedcomOtherEnterprises
{
"smi_kind": "OBJECT-IDENTITY",
"definition": [
"ruggedcomOtherEnterprises",
"OBJECT-IDENTITY",
"STATUS",
"current",
"DESCRIPTION",
"\"The root object identifier from which MIBs produced by other companies may be placed. MIBs produced by other enterprises are typically implemented with the object identifiers as defined in the MIB, but if the MIB is deemed to be uncontrolelled, we may reroot the MIB at this subtree in order to have a controlled version.\"",
"::=",
"{",
"ruggedcom",
"3",
"}"
],
"syntax_tree": [
[
"Status",
"current"
],
[
"DESCRIPTION",
"The root object identifier from which MIBs produced by other companies may be placed. MIBs produced by other enterprises are typically implemented with the object identifiers as defined in the MIB, but if the MIB is deemed to be uncontrolelled, we may reroot the MIB at this subtree in order to have a controlled version."
],
null
]
}Vendor MIB copy from the LibreNMS archive.
Module: RUGGEDCOM-MIB
See published definition above
{'SNMPv2-SMI': ['enterprises', 'MODULE-IDENTITY', 'OBJECT-IDENTITY']}Related source files and packages:
Same file in Observium Community.
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.15004.1 | ruggedcomExperiment | 0 | 0 | |
| 1.3.6.1.4.1.15004.2 | ruggedcomProducts | 10 | 21 | |
| 1.3.6.1.4.1.15004.4 | ruggedcomMgmt | 15 | 610 | |
| 1.3.6.1.4.1.15004.5 | ruggedcomTraps | 43 | 60 | |
| 1.3.6.1.4.1.15004.6 | ruggedcomAgentCapabilities | 15 | 119 |