PCUBE-SE-MIB :: txQueuesDroppedBytes

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › PCUBE-SE-MIB › txQueuesDroppedBytes

txQueuesDroppedBytes

Module: PCUBE-SE-MIB

OID (symbolic): PCUBE-SE-MIB::txQueuesDroppedBytes

OID (numeric): 1.3.6.1.4.1.5655.4.1.11.1.1.10

Node type: OBJECT-TYPE

Type: Counter64

Access: read-only

Description: Amount of dropped L3 bytes. This is valid only if the system is configured to count dropped bytes per TX queue.

What is txQueuesDroppedBytes?

The amount of Layer-3 bytes dropped from this transmit queue, valid only when the system is configured to count dropped bytes per TX queue. An admin uses this to quantify actual data loss from queue congestion on a specific traffic class, rather than just a percentage-utilization figure.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.5655.4.1.11.1.1.10
snmpwalk -v2c -c public <target> PCUBE-SE-MIB::txQueuesDroppedBytes

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.5655.4.1.11.1.1.10.1
snmpget -v2c -c public <target> PCUBE-SE-MIB::txQueuesDroppedBytes.1

Start monitoring Cisco SCE2000/SE100 Service Control Engine platforms with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the PCUBE-SE-MIB::txQueuesDroppedBytes OID value, configure state conditions and alerts, and monitor any Cisco SCE2000/SE100 Service Control Engine platforms from a single console.

How to Use in IPNetwork Monitor

Select a Cisco SCE2000/SE100 Service Control Engine platform 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 txQueuesDroppedBytes 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 amount of dropped L3 bytes. This is valid only if the system is configured to count dropped bytes per TX queue. 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 Counter64-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 (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.5655pcubePCUBE-SMI
1.3.6.1.4.1.5655.4pcubeWorkgroupPCUBE-SMI
Numeric OIDNameModule
1.3.6.1.4.1.5655.4.1pcubeSEObjsPCUBE-SE-MIB
1.3.6.1.4.1.5655.4.1.11txQueuesGrpPCUBE-SE-MIB
1.3.6.1.4.1.5655.4.1.11.1txQueuesTablePCUBE-SE-MIB
1.3.6.1.4.1.5655.4.1.11.1.1txQueuesEntryPCUBE-SE-MIB
1.3.6.1.4.1.5655.4.1.11.1.1.10txQueuesDroppedBytesPCUBE-SE-MIB