CMM3-MIB :: txDropPkts

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCMM3-MIBtxDropPkts

txDropPkts

Module: CMM3-MIB

OID (symbolic): CMM3-MIB::txDropPkts

OID (numeric): 1.3.6.1.4.1.161.19.3.4.2.1.1.18

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: This counter is incremented every time a transmit packet is dropped due to lack of resources (e.g., transmit FIFO underflow), or an internal MAC sublayer transmit error not counted by in either the TxLateCollision or the TxExcessiveCollision counters.

What is txDropPkts?

This Counter32 object counts transmit packets dropped due to lack of resources, such as a transmit FIFO underflow, or an internal MAC-layer transmit error not already counted by the late-collision or excessive-collision counters. An admin diagnosing a port that isn't successfully sending all the traffic queued to it watches this counter for growth as a sign of an internal transmit resource constraint. For example, a heavily loaded port showing rising transmit drops would lead the admin to consider whether that port's traffic load exceeds what the switch can reliably transmit.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.161.19.3.4.2.1.1.18
snmpwalk -v2c -c public <target> CMM3-MIB::txDropPkts

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.161.19.3.4.2.1.1.18.1
snmpget -v2c -c public <target> CMM3-MIB::txDropPkts.1

Start monitoring cable headend hardware modules with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CMM3-MIB::txDropPkts OID value, configure state conditions and alerts, and monitor any cable headend hardware modules from a single console.

How to Use in IPNetwork Monitor

Select a cable headend hardware module 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 txDropPkts into the Find box to locate it in the OID tree, then select it and click OK. This counter is incremented every time a transmit packet is dropped due to lack of resources (e.g., transmit FIFO underflow), or an internal MAC sublayer transmit error not counted by in either the TxLateCollision or the TxExcessiveCollision counters. 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 (10 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.161motWHISP-GLOBAL-REG-MIB
1.3.6.1.4.1.161.19whispRootWHISP-GLOBAL-REG-MIB
1.3.6.1.4.1.161.19.3whispProductsWHISP-GLOBAL-REG-MIB
1.3.6.1.4.1.161.19.3.4whispCMMWHISP-GLOBAL-REG-MIB
Numeric OIDNameModule
1.3.6.1.4.1.161.19.3.4.2cmmSwitchCMM3-MIB
1.3.6.1.4.1.161.19.3.4.2.1cmmSwitchTableCMM3-MIB
1.3.6.1.4.1.161.19.3.4.2.1.1cmmSwitchEntryCMM3-MIB
1.3.6.1.4.1.161.19.3.4.2.1.1.18txDropPktsCMM3-MIB