XEDIA-ETHERNET-MIB :: xdot3StatsOutUnderflows

MIB Reference — IPNetwork Monitor · Updated October 02, 2026

All MIBs › XEDIA-ETHERNET-MIB › xdot3StatsOutUnderflows

xdot3StatsOutUnderflows

Module: XEDIA-ETHERNET-MIB

OID (symbolic): XEDIA-ETHERNET-MIB::xdot3StatsOutUnderflows

OID (numeric): 1.3.6.1.4.1.838.3.3.1.1.1.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: A count of frames not transmitted on a particular interface because of underflow. An underflow occurs when the driver does not keep up with the hardware's transmit speed in providing buffers.

What is xdot3StatsOutUnderflows?

Counts frames that failed to transmit on this interface because of a transmit underflow — the driver couldn't feed buffers to the hardware fast enough to keep up with its transmit speed. A rising count points to a host-side (driver/CPU) bottleneck rather than a wiring or remote-end problem.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.838.3.3.1.1.1.1
snmpwalk -v2c -c public <target> XEDIA-ETHERNET-MIB::xdot3StatsOutUnderflows

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.838.3.3.1.1.1.1.1
snmpget -v2c -c public <target> XEDIA-ETHERNET-MIB::xdot3StatsOutUnderflows.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> xdot3StatsOutUnderflows.1

Start monitoring Xedia multiservice access routers with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the XEDIA-ETHERNET-MIB::xdot3StatsOutUnderflows OID value, configure state conditions and alerts, and monitor any Xedia multiservice access routers from a single console.

How to Use in IPNetwork Monitor

Select a Xedia multiservice access 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 xdot3StatsOutUnderflows 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 a count of frames not transmitted on a particular interface because of underflow. 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.838xediaXEDIA-REG
1.3.6.1.4.1.838.3xediaMibsXEDIA-REG
Numeric OIDNameModule
1.3.6.1.4.1.838.3.3xediaEthernetMIBXEDIA-ETHERNET-MIB
1.3.6.1.4.1.838.3.3.1xdot3ObjectsXEDIA-ETHERNET-MIB
1.3.6.1.4.1.838.3.3.1.1xdot3StatsTableXEDIA-ETHERNET-MIB
1.3.6.1.4.1.838.3.3.1.1.1xdot3StatsEntryXEDIA-ETHERNET-MIB
1.3.6.1.4.1.838.3.3.1.1.1.1xdot3StatsOutUnderflowsXEDIA-ETHERNET-MIB