OID reference
1.3.6.1.4.1.11.2.98.2.3
The SNMPv2 over UDP over IPv6 transport domain, used when Multi-Instance Router is supported (more than one MIR instance exist). The corresponding transport address is of type RlSnmpUDPIpv6zMridAddress for scoped IPv6 addresses with a zone index.
Identification
{1 3 6 1 4 1 11 2 98 2 3}
The displayed source records contain one distinct definition. Compare its source records.
rlSnmpUdpIpv6zMridDomain OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The SNMPv2 over UDP over IPv6 transport domain, used when Multi-Instance Router
is supported (more than one MIR instance exist).
The corresponding transport address is of type RlSnmpUDPIpv6zMridAddress
for scoped IPv6 addresses with a zone index."
::= { rlSNMPDomains 3 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The SNMPv2 over UDP over IPv6 transport domain, used when Multi-Instance Router is supported (more than one MIR instance exist). The corresponding transport address is of type RlSnmpUDPIpv6zMridAddress for scoped IPv6 addresses with a zone index.
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: rlSnmpUdpIpv6zMridDomain
{
"smi_kind": "OBJECT-IDENTITY",
"definition": [
"rlSnmpUdpIpv6zMridDomain",
"OBJECT-IDENTITY",
"STATUS",
"current",
"DESCRIPTION",
"\"The SNMPv2 over UDP over IPv6 transport domain, used when Multi-Instance Router is supported (more than one MIR instance exist). The corresponding transport address is of type RlSnmpUDPIpv6zMridAddress for scoped IPv6 addresses with a zone index.\"",
"::=",
"{",
"rlSNMPDomains",
"3",
"}"
],
"syntax_tree": [
[
"Status",
"current"
],
[
"DESCRIPTION",
"The SNMPv2 over UDP over IPv6 transport domain, used when Multi-Instance Router is supported (more than one MIR instance exist). The corresponding transport address is of type RlSnmpUDPIpv6zMridAddress for scoped IPv6 addresses with a zone index."
],
null
]
}Module: HPE-SNMP-MIB
See published definition above
{'HPE-MIB': ['nm'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString', 'AutonomousType', 'RowStatus', 'TruthValue', 'TimeInterval'], 'SNMPv2-SMI': ['OBJECT-TYPE', 'MODULE-IDENTITY', 'TimeTicks', 'Integer32'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress'], 'SNMP-COMMUNITY-MIB': ['snmpTargetAddrExtEntry'], 'SNMP-FRAMEWORK-MIB': ['SnmpEngineID', 'SnmpAdminString'], 'SNMP-USER-BASED-SM-MIB': ['usmUserEntry']}Same file in HPE Instant On 1960 2.6.0.73.
Same file in HPE Instant On 1830 2.5.0.48.
Same file in HPE Instant On 1960 2.7.0.103.
Same file in HPE Instant On 1930 2.6.0.73.
Vendor MIB copy from the Observium Community archive. HPE networking support.
Module: HPE-SNMP-MIB
{'HPE-MIB': ['nm'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString', 'AutonomousType', 'RowStatus', 'TruthValue', 'TimeInterval'], 'SNMPv2-SMI': ['OBJECT-TYPE', 'MODULE-IDENTITY', 'TimeTicks', 'Integer32'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress'], 'SNMP-COMMUNITY-MIB': ['snmpTargetAddrExtEntry'], 'SNMP-FRAMEWORK-MIB': ['SnmpEngineID', 'SnmpAdminString'], 'SNMP-USER-BASED-SM-MIB': ['usmUserEntry']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.11.2.98.2.1 | rlSnmpUDPMridDomain | 0 | 0 | |
| 1.3.6.1.4.1.11.2.98.2.2 | rlSnmpUdpIpv6MridDomain | 0 | 0 |