OID reference
1.3.6.1.4.1.11.2.129.7.1.3
Indicates that hop limit value used in router advertisement is an user configured value and not necessarily value that is used by router itself.
Identification
{1 3 6 1 4 1 11 2 129 7 1 3}
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.
rlIpv6RouterAdvertIsCurHopLimitUserConfigured OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Indicates that hop limit value used in router advertisement is
an user configured value and not necessarily value that is used by
router itself."
DEFVAL { false }
::= { rlIpv6RouterAdvertEntry 3 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Indicates that hop limit value used in router advertisement is an user configured value and not necessarily value that is used by router itself.
HPE networking MIB copies (LibreNMS/Observium Community)HPE Instant On official MIBs
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: rlIpv6RouterAdvertIsCurHopLimitUserConfigured
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"rlIpv6RouterAdvertIsCurHopLimitUserConfigured",
"OBJECT-TYPE",
"SYNTAX",
"TruthValue",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"Indicates that hop limit value used in router advertisement is an user configured value and not necessarily value that is used by router itself.\"",
"DEFVAL",
"{",
"false",
"}",
"::=",
"{",
"rlIpv6RouterAdvertEntry",
"3",
"}"
],
"syntax_tree": [
[
"row",
"TruthValue"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Indicates that hop limit value used in router advertisement is an user configured value and not necessarily value that is used by router itself."
],
null,
null,
null,
[
"DEFVAL",
"false"
]
]
}Module: HPE-IPv6
See published definition above
{'HPE-IP': ['ipSpec'], 'IF-MIB': ['InterfaceIndex', 'InterfaceIndexOrZero'], 'IP-MIB': ['ipAddressEntry', 'ipv6InterfaceEntry', 'ipNetToPhysicalEntry', 'ipv6RouterAdvertEntry'], 'HPE-MIB': ['nm'], 'SNMPv2-TC': ['TimeInterval', 'TruthValue', 'DisplayString', 'RowStatus'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Counter32', 'IpAddress', 'mib-2', 'Unsigned32', 'Counter64', 'zeroDotZero', 'Gauge32'], 'IANAifType-MIB': ['IANAtunnelType'], 'IP-FORWARD-MIB': ['inetCidrRouteEntry'], 'IANA-RTPROTO-MIB': ['IANAipRouteProtocol'], 'INET-ADDRESS-MIB': ['InetAddressPrefixLength', 'InetAddressType', 'InetAddress', 'InetAutonomousSystemNumber']}Same file in HPE Instant On 1960 2.6.0.73.
Same file in HPE Instant On 1960 2.7.0.103.
Same file in HPE Instant On 1930 2.6.0.73.
Same file in HPE Instant On 1960 2.8.1.35.
Vendor MIB copy from the Observium Community archive. HPE networking support.
Module: HPE-IPv6
{'HPE-IP': ['ipSpec'], 'IF-MIB': ['InterfaceIndex', 'InterfaceIndexOrZero'], 'IP-MIB': ['ipAddressEntry', 'ipv6InterfaceEntry', 'ipNetToPhysicalEntry', 'ipv6RouterAdvertEntry'], 'HPE-MIB': ['nm'], 'SNMPv2-TC': ['TimeInterval', 'TruthValue', 'DisplayString', 'RowStatus'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Counter32', 'IpAddress', 'mib-2', 'Unsigned32', 'Counter64', 'zeroDotZero', 'Gauge32'], 'IANAifType-MIB': ['IANAtunnelType'], 'IP-FORWARD-MIB': ['inetCidrRouteEntry'], 'IANA-RTPROTO-MIB': ['IANAipRouteProtocol'], 'INET-ADDRESS-MIB': ['InetAddressPrefixLength', 'InetAddressType', 'InetAddress', 'InetAutonomousSystemNumber']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.11.2.129.7.1.1 | rlIpv6RouterAdvertAdvIntervalOption | 0 | 0 | |
| 1.3.6.1.4.1.11.2.129.7.1.2 | rlIpv6RouterAdvertRouterPreference | 0 | 0 |