OID reference
1.3.6.1.4.1.11.2.26.7.3
This parameter controls leaking (redistribution) of routes from OSPF to RIP. If enabled, all routes learned via OSPF are advertised into RIP.
Identification
{1 3 6 1 4 1 11 2 26 7 3}
| Value | Name |
|---|---|
| 1 | enable |
| 2 | disable |
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.
ipLeakOspfToRip OBJECT-TYPE
SYNTAX INTEGER {
enable (1),
disable (2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This parameter controls leaking (redistribution) of routes
from OSPF to RIP. If enabled, all routes learned via OSPF
are advertised into RIP."
DEFVAL {disable}
::= { ipRouteLeaking 3 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
This parameter controls leaking (redistribution) of routes from OSPF to RIP. If enabled, all routes learned via OSPF are advertised into RIP.
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: ipLeakOspfToRip
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"ipLeakOspfToRip",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"enable",
"(",
"1",
")",
",",
"disable",
"(",
"2",
")",
"}",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"This parameter controls leaking (redistribution) of routes from OSPF to RIP. If enabled, all routes learned via OSPF are advertised into RIP.\"",
"DEFVAL",
"{",
"disable",
"}",
"::=",
"{",
"ipRouteLeaking",
"3",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"enable",
1
],
[
"disable",
2
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"This parameter controls leaking (redistribution) of routes from OSPF to RIP. If enabled, all routes learned via OSPF are advertised into RIP."
],
null,
null,
null,
[
"DEFVAL",
"disable"
]
]
}Module: HPE-IpRouter
See published definition above
{'HPE-IP': ['rip2Spec', 'ipRedundancy', 'ipRouteLeaking', 'ipRipFilter', 'rlIpRoutingProtPreference', 'rlOspf', 'ipSpec'], 'OSPF-MIB': ['ospfIfEntry', 'AreaID', 'RouterID', 'ospfVirtIfEntry'], 'RIPv2-MIB': ['rip2IfConfEntry'], 'SNMPv2-TC': ['DisplayString', 'RowStatus', 'TruthValue', 'TEXTUAL-CONVENTION'], 'SNMPv2-SMI': ['Unsigned32', 'Integer32', 'Counter32', 'IpAddress', 'MODULE-IDENTITY', 'OBJECT-TYPE']}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.
Module: HPE-IpRouter
{'HPE-IP': ['rip2Spec', 'ipRedundancy', 'ipRouteLeaking', 'ipRipFilter', 'rlIpRoutingProtPreference', 'rlOspf', 'ipSpec'], 'OSPF-MIB': ['ospfIfEntry', 'AreaID', 'RouterID', 'ospfVirtIfEntry'], 'RIPv2-MIB': ['rip2IfConfEntry'], 'SNMPv2-TC': ['DisplayString', 'RowStatus', 'TruthValue', 'TEXTUAL-CONVENTION'], 'SNMPv2-SMI': ['Unsigned32', 'Integer32', 'Counter32', 'IpAddress', 'MODULE-IDENTITY', 'OBJECT-TYPE']}Vendor MIB copy from the Observium Community archive. HPE networking support.
Module: HPE-IpRouter
{'HPE-IP': ['rip2Spec', 'ipRedundancy', 'ipRouteLeaking', 'ipRipFilter', 'rlIpRoutingProtPreference', 'rlOspf', 'ipSpec'], 'OSPF-MIB': ['ospfIfEntry', 'AreaID', 'RouterID', 'ospfVirtIfEntry'], 'RIPv2-MIB': ['rip2IfConfEntry'], 'SNMPv2-TC': ['DisplayString', 'RowStatus', 'TruthValue', 'TEXTUAL-CONVENTION'], 'SNMPv2-SMI': ['Unsigned32', 'Integer32', 'Counter32', 'IpAddress', 'MODULE-IDENTITY', 'OBJECT-TYPE']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.11.2.26.7.1 | ipLeakStaticToRip | 0 | 0 | |
| 1.3.6.1.4.1.11.2.26.7.2 | ipLeakStaticToOspf | 0 | 0 | |
| 1.3.6.1.4.1.11.2.26.7.4 | ipLeakRipToOspf | 0 | 0 | |
| 1.3.6.1.4.1.11.2.26.7.5 | ipLeakExtDirectToOspf | 0 | 0 |