RMON2-MIB :: historyControlDroppedFrames

MIB Reference — IPNetwork Monitor

All MIBsRMON2-MIBhistoryControlDroppedFrames

historyControlDroppedFrames

Module: RMON2-MIB

OID (symbolic): RMON2-MIB::historyControlDroppedFrames

OID (numeric): 1.3.6.1.2.1.16.2.5.1.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description:

The total number of frames which were received by the probe and therefore not accounted for in the *StatsDropEvents, but for which the probe chose not to count for this entry for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this

collection.

This count does not include packets that were not counted because they had MAC-layer errors.

Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.

What is historyControlDroppedFrames?

This running count tracks network frames intentionally dropped by the probe during historical traffic collection due to resource shortage. Engineers monitor this to spot periods when the probe was too busy to capture full history. Rising values indicate collection gaps during peak traffic.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.16.2.5.1.1
snmpwalk -v2c -c public <target> RMON2-MIB::historyControlDroppedFrames

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.16.2.5.1.1.1
snmpget -v2c -c public <target> RMON2-MIB::historyControlDroppedFrames.1

OID Breakdown

Numeric OIDNameModule
1isoLANART-AGENT
1.3orgBIANCA-BRICK-PPP-MIB
1.3.6dodBIANCA-BRICK-PPP-MIB
1.3.6.1internetBIANCA-BRICK-PPP-MIB
1.3.6.1.2mgmtBKTEL-HFC862-BASE-MIB
1.3.6.1.2.1mib_2CHECKPOINT-MIB-2
1.3.6.1.2.1.16rmonLBHUB-BOOM-MIB
1.3.6.1.2.1.16.2historyLBHUB-BOOM-MIB
1.3.6.1.2.1.16.2.5historyControl2TableRMON2-MIB
1.3.6.1.2.1.16.2.5.1historyControl2EntryRMON2-MIB
1.3.6.1.2.1.16.2.5.1.1historyControlDroppedFramesRMON2-MIB