Ruggedcom ROX 2 Agent Capabilities - IF-MIB
Sources for this description
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
OID reference
1.3.6.1.4.1.15004.6.30.2.2
Ruggedcom ROX 2 Agent Capabilities - IF-MIB
Identification
{1 3 6 1 4 1 15004 6 30 2 2}
The displayed source records contain one distinct definition. Compare its source records.
ruggedcomIfAC01 AGENT-CAPABILITIES
PRODUCT-RELEASE "Ruggedcom ROX 2.4.1"
STATUS current
DESCRIPTION
"Ruggedcom ROX 2 Agent Capabilities - IF-MIB"
SUPPORTS IF-MIB
-- rfc2863.txt with rfc1229.txt extensions
INCLUDES { ifGeneralInformationGroup,ifVHCPacketGroup, ifCounterDiscontinuityGroup,
linkUpDownNotificationsGroup,ifFixedLengthGroup, ifHCFixedLengthGroup, ifPacketGroup, ifHCPacketGroup }
-- Future support to be added for: ifStackGroup2, ifRcvAddressGroup --
-- No support for these deprecated groups: ifGeneralGroup,ifTestGroup, ifStackGroup,ifOldObjectsGroup --
VARIATION ifIndex
DESCRIPTION
"A numbering scheme has been implemented to allow
one-to-one mapping between physical port values and
ifIndex interface values. Te value of ifIndex will be
{32*Logical Slot) + Port Number. Logical Slot values are
defined as: SM (0),LM1 to LM6 (1 to 6 respectively)"
VARIATION ifAdminStatus
SYNTAX INTEGER {
up(1),
down(2)
}
DESCRIPTION
"Support for the value 'testing(3)' is not implemented
per RFC 2863 compliance statement."
VARIATION ifPromiscuousMode
ACCESS read-only
DESCRIPTION
"Write access is not implemented per RFC 2863 compliance
statement. This mode is always 'false(1)'."
VARIATION ifAlias
DESCRIPTION
"String length is limited to 15 characters."
-- ---------------------------------------------------------------------- --
::= { ruggedcomIfACModule 2 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Ruggedcom ROX 2 Agent Capabilities - IF-MIB
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: ruggedcomIfAC01
{
"smi_kind": "AGENT-CAPABILITIES",
"definition": [
"ruggedcomIfAC01",
"AGENT-CAPABILITIES",
"PRODUCT-RELEASE",
[
"literal",
"22527567676564636f6d20524f5820322e342e3122"
],
"STATUS",
"current",
"DESCRIPTION",
"\"Ruggedcom ROX 2 Agent Capabilities - IF-MIB\"",
"SUPPORTS",
"IF-MIB",
"INCLUDES",
"{",
"ifGeneralInformationGroup",
",",
"ifVHCPacketGroup",
",",
"ifCounterDiscontinuityGroup",
",",
"linkUpDownNotificationsGroup",
",",
"ifFixedLengthGroup",
",",
"ifHCFixedLengthGroup",
",",
"ifPacketGroup",
",",
"ifHCPacketGroup",
"}",
"VARIATION",
"ifIndex",
"DESCRIPTION",
"\"A numbering scheme has been implemented to allow one-to-one mapping between physical port values and ifIndex interface values. Te value of ifIndex will be {32*Logical Slot) + Port Number. Logical Slot values are defined as: SM (0),LM1 to LM6 (1 to 6 respectively)\"",
"VARIATION",
"ifAdminStatus",
"SYNTAX",
"INTEGER",
"{",
"up",
"(",
"1",
")",
",",
"down",
"(",
"2",
")",
"}",
"DESCRIPTION",
"\"Support for the value 'testing(3)' is not implemented per RFC 2863 compliance statement.\"",
"VARIATION",
"ifPromiscuousMode",
"ACCESS",
"read-only",
"DESCRIPTION",
"\"Write access is not implemented per RFC 2863 compliance statement. This mode is always 'false(1)'.\"",
"VARIATION",
"ifAlias",
"DESCRIPTION",
"\"String length is limited to 15 characters.\"",
"::=",
"{",
"ruggedcomIfACModule",
"2",
"}"
],
"syntax_tree": [
[
"PRODUCT-RELEASE",
"Ruggedcom ROX 2.4.1"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Ruggedcom ROX 2 Agent Capabilities - IF-MIB"
],
null
]
}Vendor MIB copy from the Observium Community archive.
Module: RC-IF-MIB-AC
See published definition above
{'SNMPv2-SMI': ['MODULE-IDENTITY'], 'SNMPv2-CONF': ['AGENT-CAPABILITIES'], 'RUGGEDCOM-MIB': ['ruggedcomAgentCapability']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.15004.6.30.2.1 | ruggedcomIfAC | 0 | 0 |