OID reference
1.3.6.1.4.1.248.12.22.1.1.1.1
The Loopback ID is associated with Internal Interface number which will be generated when we create a loopback.
Identification
{1 3 6 1 4 1 248 12 22 1 1 1 1}
At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.
In HM2-PLATFORM-LOOPBACK-MIB, the row index hm2AgentLoopbackID is declared as Integer32. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.248.12.22.1.1.1.1.<hm2AgentLoopbackID>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.
A query example is omitted because the source variants do not establish compatible read access.
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.
hm2AgentLoopbackID OBJECT-TYPE
SYNTAX Integer32 (0..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Loopback ID is associated with Internal Interface number
which will be generated when we create a loopback."
::= { hm2AgentLoopbackEntry 1 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The Loopback ID is associated with Internal Interface number which will be generated when we create a loopback.
Belden, GarrettCom and Hirschmann IT official standalone MIBsHirschmann MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: hm2AgentLoopbackID
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"hm2AgentLoopbackID",
"OBJECT-TYPE",
"SYNTAX",
"Integer32",
"(",
"0",
".",
".",
"2147483647",
")",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"The Loopback ID is associated with Internal Interface number which will be generated when we create a loopback.\"",
"::=",
"{",
"hm2AgentLoopbackEntry",
"1",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"Integer32",
[
"integerSubType",
[
[
0,
2147483647
]
]
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The Loopback ID is associated with Internal Interface number which will be generated when we create a loopback."
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive. Hirschmann support.
Module: HM2-PLATFORM-LOOPBACK-MIB
See published definition above
{'IF-MIB': ['InterfaceIndex'], 'SNMPv2-TC': ['RowStatus'], 'HM2-TC-MIB': ['hm2PlatformMibs'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32'], 'INET-ADDRESS-MIB': ['InetAddressIPv4']}Related source files and packages:
Module: HM2-PLATFORM-LOOPBACK-MIB
{'IF-MIB': ['InterfaceIndex'], 'SNMPv2-TC': ['RowStatus'], 'HM2-TC-MIB': ['hm2PlatformMibs'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32'], 'INET-ADDRESS-MIB': ['InetAddressIPv4']}Same file in 069Qp00000juDofIAE.
Same file in 069Qp00000ju90HIAQ.
Same file in 069Qp00000ju8qbIAA.
Same file in 069Qp00000ju6wsIAA.
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.248.12.22.1.1.1.2 | hm2AgentLoopbackIfIndex | 0 | 0 | |
| 1.3.6.1.4.1.248.12.22.1.1.1.3 | hm2AgentLoopbackIPAddress | 0 | 0 | |
| 1.3.6.1.4.1.248.12.22.1.1.1.4 | hm2AgentLoopbackIPSubnet | 0 | 0 | |
| 1.3.6.1.4.1.248.12.22.1.1.1.5 | hm2AgentLoopbackStatus | 0 | 0 |