HIRSCHMANN-MMP4-ROUTING-MIB :: hmAgentRip2RcvBadPackets

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

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

hmAgentRip2RcvBadPackets

Module: HIRSCHMANN-MMP4-ROUTING-MIB

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

OID (numeric): 1.3.6.1.4.1.248.15.2.3.10.1.8

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: ......

What is hmAgentRip2RcvBadPackets?

A counter of malformed RIP packets received on this interface. The DESCRIPTION is a placeholder ('......') in the source MIB, so this reading is inferred from the object name and its Counter32 syntax; a rising count typically points to a misconfigured or incompatible RIP neighbor.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.248.15.2.3.10.1.8
snmpwalk -v2c -c public <target> HIRSCHMANN-MMP4-ROUTING-MIB::hmAgentRip2RcvBadPackets

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.248.15.2.3.10.1.8.1
snmpget -v2c -c public <target> HIRSCHMANN-MMP4-ROUTING-MIB::hmAgentRip2RcvBadPackets.1

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::hmAgentRip2RcvBadPackets OID value, configure state conditions and alerts, and monitor any Hirschmann Platform4 industrial switch/router from a single console.

How to Use in IPNetwork Monitor

Select a Hirschmann Platform4 industrial switch/router as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type hmAgentRip2RcvBadPackets into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The number of bad RIPv2 packets received. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

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.3hmAgentRouterRipConfigGroupHIRSCHMANN-MMP4-ROUTING-MIB
1.3.6.1.4.1.248.15.2.3.10hmAgentRip2InterfaceTableHIRSCHMANN-MMP4-ROUTING-MIB
1.3.6.1.4.1.248.15.2.3.10.1hmAgentRip2InterfaceEntryHIRSCHMANN-MMP4-ROUTING-MIB
1.3.6.1.4.1.248.15.2.3.10.1.8hmAgentRip2RcvBadPacketsHIRSCHMANN-MMP4-ROUTING-MIB