HIRSCHMANN-MMP4-ROUTING-MIB :: hmAgentRouterOspfRFC1583CompatibilityMode

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › HIRSCHMANN-MMP4-ROUTING-MIB › hmAgentRouterOspfRFC1583CompatibilityMode

hmAgentRouterOspfRFC1583CompatibilityMode

Module: HIRSCHMANN-MMP4-ROUTING-MIB

OID (symbolic): HIRSCHMANN-MMP4-ROUTING-MIB::hmAgentRouterOspfRFC1583CompatibilityMode

OID (numeric): 1.3.6.1.4.1.248.15.2.4.11

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: From RFC2328: Controls the preference rules used in Section 16.4 when choosing among multiple AS-external-LSAs advertising the same destination. When set to 'enabled', the preference rules remain those specified by RFC 1583 ([Ref9]). When set to 'disabled', the preference rules are those stated in

Section 16.4.1, which prevent routing loops when AS- external-LSAs for the same destination have been originated from different areas. Set to 'enabled' by default.

In order to minimize the chance of routing loops, all OSPF routers in an OSPF routing domain should have RFC1583Compatibility set identically. When there are routers present that have not been updated with the functionality specified in Section 16.4.1 of this memo, all routers should have RFC1583Compatibility set to 'enabled'. Otherwise, all routers should have RFC1583Compatibility set to 'disabled', preventing all routing loops.

What is hmAgentRouterOspfRFC1583CompatibilityMode?

Controls which RFC's tie-breaking rules OSPF uses when choosing among multiple AS-external routes to the same destination: enable (default) uses the older RFC 1583 rules, disable uses the RFC 2328 Section 16.4.1 rules that prevent certain routing loops; the MIB stresses all routers in a domain should be set the same way to avoid loops.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.248.15.2.4.11
snmpwalk -v2c -c public <target> HIRSCHMANN-MMP4-ROUTING-MIB::hmAgentRouterOspfRFC1583CompatibilityMode

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.248.15.2.4.11.1
snmpget -v2c -c public <target> HIRSCHMANN-MMP4-ROUTING-MIB::hmAgentRouterOspfRFC1583CompatibilityMode.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.248.15.2.4.11.1 i <value>

Start monitoring Hirschmann Platform4 industrial switch/router with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the HIRSCHMANN-MMP4-ROUTING-MIB::hmAgentRouterOspfRFC1583CompatibilityMode OID value, configure state conditions and alerts, and monitor any Hirschmann Platform4 industrial switch/router from a single console.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.248hirschmannHIRSCHMANN-GENERIC-ERROR-MIB
1.3.6.1.4.1.248.15hmPlatform4HIRSCHMANN-MMP4-BASICL2-MIB
Numeric OIDNameModule
1.3.6.1.4.1.248.15.2hmPlatform4RoutingHIRSCHMANN-MMP4-ROUTING-MIB
1.3.6.1.4.1.248.15.2.4hmAgentRouterOspfConfigGroupHIRSCHMANN-MMP4-ROUTING-MIB
1.3.6.1.4.1.248.15.2.4.11hmAgentRouterOspfRFC1583CompatibilityModeHIRSCHMANN-MMP4-ROUTING-MIB