OID reference
1.3.6.1.4.1.171.10.97.2.13.1.5
User can set this object to 1,2,3. 1 means that the system sending and receiving RIP version1 packets, 2 means that the system sending and receiving RIP version2 packets, 3 means that the system sending RIP version1 packets and receiving both RIP version1 and RIP version2 packets. If the system RIP interface configura…
Identification
{1 3 6 1 4 1 171 10 97 2 13 1 5}
| Value | Name |
|---|---|
| 1 | ripv1 |
| 2 | ripv2 |
| 3 | compatible |
At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.
snmpget [connection options] DEVICE .1.3.6.1.4.1.171.10.97.2.13.1.5.0
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.
myRipRecommendSetting OBJECT-TYPE
SYNTAX INTEGER{
ripv1(1),
ripv2(2),
compatible(3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"User can set this object to 1,2,3.
1 means that the system sending and receiving RIP version1 packets,
2 means that the system sending and receiving RIP version2 packets,
3 means that the system sending RIP version1 packets and receiving both
RIP version1 and RIP version2 packets.
If the system RIP interface configuration has been modified by user,this
object will be 4."
DEFVAL {3}
::={myRIPMIBObjects 5}
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
User can set this object to 1,2,3. 1 means that the system sending and receiving RIP version1 packets, 2 means that the system sending and receiving RIP version2 packets, 3 means that the system sending RIP version1 packets and receiving both RIP version1 and RIP version2 packets. If the system RIP interface configuration has been modified by user,this object will be 4.
D-Link official switch MIBsD-Link MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: myRipRecommendSetting
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"myRipRecommendSetting",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"ripv1",
"(",
"1",
")",
",",
"ripv2",
"(",
"2",
")",
",",
"compatible",
"(",
"3",
")",
"}",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"User can set this object to 1,2,3. 1 means that the system sending and receiving RIP version1 packets, 2 means that the system sending and receiving RIP version2 packets, 3 means that the system sending RIP version1 packets and receiving both RIP version1 and RIP version2 packets. If the system RIP interface configuration has been modified by user,this object will be 4.\"",
"DEFVAL",
"{",
"3",
"}",
"::=",
"{",
"myRIPMIBObjects",
"5",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"ripv1",
1
],
[
"ripv2",
2
],
[
"compatible",
3
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"User can set this object to 1,2,3. 1 means that the system sending and receiving RIP version1 packets, 2 means that the system sending and receiving RIP version2 packets, 3 means that the system sending RIP version1 packets and receiving both RIP version1 and RIP version2 packets. If the system RIP interface configuration has been modified by user,this object will be 4."
],
null,
null,
null,
[
"DEFVAL",
3
]
]
}Module: MY-RIP-MIB
See published definition above
{'MY-TC': ['ConfigStatus', 'MemberMap', 'IfIndex'], 'MY-SMI': ['myMgmt'], 'SNMPv2-TC': ['TruthValue', 'DisplayString', 'RowStatus', 'MacAddress'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Integer32', 'Counter32', 'IpAddress'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'P-BRIDGE-MIB': ['EnabledStatus'], 'Q-BRIDGE-MIB': ['VlanId']}Related source files and packages:
Vendor MIB copy from the Observium Community archive. D-Link support.
Module: DES7200-RIP-MIB
{'SNMPv2-TC': ['TruthValue', 'DisplayString', 'RowStatus', 'MacAddress'], 'DES7200-TC': ['ConfigStatus', 'MemberMap', 'IfIndex'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Integer32', 'Counter32', 'IpAddress'], 'DES7200-SMI': ['myMgmt'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'P-BRIDGE-MIB': ['EnabledStatus'], 'Q-BRIDGE-MIB': ['VlanId']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.171.10.97.2.13.1.1 | myRipEnable | 0 | 0 | |
| 1.3.6.1.4.1.171.10.97.2.13.1.2 | myRipUpdateTime | 0 | 0 | |
| 1.3.6.1.4.1.171.10.97.2.13.1.3 | myRipInvalidTime | 0 | 0 | |
| 1.3.6.1.4.1.171.10.97.2.13.1.4 | myRipHolddownTime | 0 | 0 | |
| 1.3.6.1.4.1.171.10.97.2.13.1.6 | myRipIfStatTable | 1 | 5 | |
| 1.3.6.1.4.1.171.10.97.2.13.1.7 | myRipIfConfTable | 1 | 9 | |
| 1.3.6.1.4.1.171.10.97.2.13.1.8 | myRipOffsetMetric | 0 | 0 | |
| 1.3.6.1.4.1.171.10.97.2.13.1.9 | myRipAdministrativeDistance | 0 | 0 | |
| 1.3.6.1.4.1.171.10.97.2.13.1.10 | myRipValidateUpdateSrcEnable | 0 | 0 | |
| 1.3.6.1.4.1.171.10.97.2.13.1.11 | myRipPassiveStatus | 0 | 0 | |
| 1.3.6.1.4.1.171.10.97.2.13.1.12 | myRipNextDueIn | 0 | 0 | |
| 1.3.6.1.4.1.171.10.97.2.13.1.13 | myRipIfOffsetTable | 1 | 6 | |
| 1.3.6.1.4.1.171.10.97.2.13.1.14 | myRipNetworkTable | 1 | 4 | |
| 1.3.6.1.4.1.171.10.97.2.13.1.15 | myRipNeighborTable | 1 | 3 |