BDCOM-INTERFACES :: bdlocIfInGiants

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsBDCOM-INTERFACESbdlocIfInGiants

bdlocIfInGiants

Module: BDCOM-INTERFACES

OID (symbolic): BDCOM-INTERFACES::bdlocIfInGiants

OID (numeric): 1.3.6.1.4.1.3320.2.2.1.1.11

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: Number of input packets which were larger then the physical media permitted.

What is bdlocIfInGiants?

This counter tallies input packets exceeding the media's maximum frame size, indicating fragmentation errors or protocol mismatches. Network teams use it to diagnose MTU issues. Example: bdlocIfInGiants = 3 indicates 3 oversized frames were received; if this count grows, it suggests an upstream device with an incorrect MTU setting or a corrupt frame checksum.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.3320.2.2.1.1.11
snmpwalk -v2c -c public <target> BDCOM-INTERFACES::bdlocIfInGiants

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.3320.2.2.1.1.11.1
snmpget -v2c -c public <target> BDCOM-INTERFACES::bdlocIfInGiants.1

Start monitoring BDCOM networking equipment (switches/routers) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the BDCOM-INTERFACES::bdlocIfInGiants OID value, configure state conditions and alerts, and monitor any BDCOM networking equipment (switches/routers) from a single console.

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.3320bdcomBDCOM-SMI
1.3.6.1.4.1.3320.2bdlocalBDCOM-SMI
Numeric OIDNameModule
1.3.6.1.4.1.3320.2.2bdlinterfacesBDCOM-INTERFACES
1.3.6.1.4.1.3320.2.2.1bdlifTableBDCOM-INTERFACES
1.3.6.1.4.1.3320.2.2.1.1bdlifEntryBDCOM-INTERFACES
1.3.6.1.4.1.3320.2.2.1.1.11bdlocIfInGiantsBDCOM-INTERFACES