CUMULUS-COUNTERS-MIB :: l3v4InDiscards

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CUMULUS-COUNTERS-MIB › l3v4InDiscards

l3v4InDiscards

Module: CUMULUS-COUNTERS-MIB

OID (symbolic): CUMULUS-COUNTERS-MIB::l3v4InDiscards

OID (numeric): 1.3.6.1.4.1.40310.2.1.1.1.2

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Number of inbound IPv4 packets discarded by the routing engine.

What is l3v4InDiscards?

This value is a running counter of how many inbound IPv4 packets the switch's routing engine has discarded, rather than forwarded, since the counter last reset. An admin watches this counter for unexpected growth, which can indicate routing table misses, TTL expirations, or other Layer 3 forwarding problems affecting IPv4 traffic. For example, a counter that jumps sharply after a routing change might indicate packets are now hitting a route that leads nowhere valid.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.40310.2.1.1.1.2
snmpwalk -v2c -c public <target> CUMULUS-COUNTERS-MIB::l3v4InDiscards

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.40310.2.1.1.1.2.1
snmpget -v2c -c public <target> CUMULUS-COUNTERS-MIB::l3v4InDiscards.1

Start monitoring Cumulus Linux white-box switch (packet-discard counters) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CUMULUS-COUNTERS-MIB::l3v4InDiscards OID value, configure state conditions and alerts, and monitor any Cumulus Linux white-box switch (packet-discard counters) from a single console.

How to Use in IPNetwork Monitor

Select a Cumulus Linux white-box switch (packet-discard counters) 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 l3v4InDiscards 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. It reports the number of inbound IPv4 packets discarded by the routing engine. 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 between polls, since a rising count of errors, failures, or discards often points to a real underlying problem. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (7 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.40310cumulusMibCUMULUS-SNMP-MIB
Numeric OIDNameModule
1.3.6.1.4.1.40310.2sysSpecificCountersCUMULUS-COUNTERS-MIB
1.3.6.1.4.1.40310.2.1discardCountersCUMULUS-COUNTERS-MIB
1.3.6.1.4.1.40310.2.1.1discardCountersTableCUMULUS-COUNTERS-MIB
1.3.6.1.4.1.40310.2.1.1.1discardCountersEntryCUMULUS-COUNTERS-MIB
1.3.6.1.4.1.40310.2.1.1.1.2l3v4InDiscardsCUMULUS-COUNTERS-MIB