OID reference
1.3.6.1.4.1.2076.114.1.2.4.1.7
The address of the next-hop specific to this entry. For most interfaces, this is identical to fsPimCmnIpMRouteNextHopGroup. NBMA interfaces, however, may have multiple next-hop addresses out a single outgoing interface.
Identification
{1 3 6 1 4 1 2076 114 1 2 4 1 7}
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.
fsPimStdIpMRouteNextHopAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The address of the next-hop specific to this entry. For
most interfaces, this is identical to fsPimCmnIpMRouteNextHopGroup.
NBMA interfaces, however, may have multiple next-hop
addresses out a single outgoing interface."
::= { fsPimStdIpMRouteNextHopEntry 7 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The address of the next-hop specific to this entry. For most interfaces, this is identical to fsPimCmnIpMRouteNextHopGroup. NBMA interfaces, however, may have multiple next-hop addresses out a single outgoing interface.
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)Belden, GarrettCom and Hirschmann IT official standalone MIBs
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: fsPimStdIpMRouteNextHopAddress
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"fsPimStdIpMRouteNextHopAddress",
"OBJECT-TYPE",
"SYNTAX",
"InetAddress",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"The address of the next-hop specific to this entry. For most interfaces, this is identical to fsPimCmnIpMRouteNextHopGroup. NBMA interfaces, however, may have multiple next-hop addresses out a single outgoing interface.\"",
"::=",
"{",
"fsPimStdIpMRouteNextHopEntry",
"7",
"}"
],
"syntax_tree": [
[
"row",
"InetAddress"
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The address of the next-hop specific to this entry. For most interfaces, this is identical to fsPimCmnIpMRouteNextHopGroup. NBMA interfaces, however, may have multiple next-hop addresses out a single outgoing interface."
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive.
Module: ARICENT-PIMCMN2-MIB
See published definition above
{'IF-MIB': ['InterfaceIndex'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'RowStatus', 'TruthValue', 'DisplayString'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Integer32', 'IpAddress', 'TimeTicks', 'Gauge32', 'Counter32', 'enterprises'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress']}Related source files and packages:
Module: ARICENT-PIMCMN2-MIB
{'IF-MIB': ['InterfaceIndex'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'RowStatus', 'TruthValue', 'DisplayString'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Integer32', 'IpAddress', 'TimeTicks', 'Gauge32', 'Counter32', 'enterprises'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.2076.114.1.2.4.1.2 | fsPimStdIpMRouteNextHopAddrType | 0 | 0 | |
| 1.3.6.1.4.1.2076.114.1.2.4.1.3 | fsPimStdIpMRouteNextHopGroup | 0 | 0 | |
| 1.3.6.1.4.1.2076.114.1.2.4.1.4 | fsPimStdIpMRouteNextHopSource | 0 | 0 | |
| 1.3.6.1.4.1.2076.114.1.2.4.1.5 | fsPimStdIpMRouteNextHopSourceMaskLen | 0 | 0 | |
| 1.3.6.1.4.1.2076.114.1.2.4.1.6 | fsPimStdIpMRouteNextHopIfIndex | 0 | 0 | |
| 1.3.6.1.4.1.2076.114.1.2.4.1.8 | fsPimStdIpMRouteNextHopPruneReason | 0 | 0 |