OID reference
1.3.6.1.4.1.7244.2.23.1.1.1.1
The prefix associated with the loopback interface. The data type is used to model the Ipv6 address. It is a binary string of 16 octects in network byte-order. It specifies the IP address of loopback which will be in Ipv6 Format, generated using internal interface number.
Identification
{1 3 6 1 4 1 7244 2 23 1 1 1 1}
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.
agentLoopbackIpv6PrefixPrefix OBJECT-TYPE
SYNTAX Ipv6AddressPrefix
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The prefix associated with the loopback interface. The data type
is used to model the Ipv6 address. It is a binary string
of 16 octects in network byte-order. It specifies the IP
address of loopback which will be in Ipv6 Format, generated
using internal interface number."
::= { agentLoopbackIpv6PrefixEntry 1 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The prefix associated with the loopback interface. The data type is used to model the Ipv6 address. It is a binary string of 16 octects in network byte-order. It specifies the IP address of loopback which will be in Ipv6 Format, generated using internal interface number.
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: agentLoopbackIpv6PrefixPrefix
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"agentLoopbackIpv6PrefixPrefix",
"OBJECT-TYPE",
"SYNTAX",
"Ipv6AddressPrefix",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"The prefix associated with the loopback interface. The data type is used to model the Ipv6 address. It is a binary string of 16 octects in network byte-order. It specifies the IP address of loopback which will be in Ipv6 Format, generated using internal interface number.\"",
"::=",
"{",
"agentLoopbackIpv6PrefixEntry",
"1",
"}"
],
"syntax_tree": [
[
"row",
"Ipv6AddressPrefix"
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The prefix associated with the loopback interface. The data type is used to model the Ipv6 address. It is a binary string of 16 octects in network byte-order. It specifies the IP address of loopback which will be in Ipv6 Format, generated using internal interface number."
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive.
Module: IPV6-LOOPBACK-MIB
See published definition above
{'IPV6-TC': ['Ipv6AddressPrefix'], 'SNMPv2-TC': ['DisplayString', 'PhysAddress', 'TruthValue', 'RowStatus'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'Unsigned32', 'Integer32'], 'LOOPBACK-MIB': ['agentLoopbackID'], 'INET-ADDRESS-MIB': ['InetAddressPrefixLength'], 'QUANTA-SWITCH-MIB': ['switch']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.7244.2.23.1.1.1.2 | agentLoopbackIpv6PrefixPrefixLen | 0 | 0 | |
| 1.3.6.1.4.1.7244.2.23.1.1.1.3 | agentLoopbackIpv6PrefixStatus | 0 | 0 |