RMON-MIB :: etherHistoryFragments

MIB Reference — IPNetwork Monitor

All MIBsRMON-MIBetherHistoryFragments

etherHistoryFragments

Module: RMON-MIB

OID (symbolic): RMON-MIB::etherHistoryFragments

OID (numeric): 1.3.6.1.2.1.16.2.2.1.12

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description:

The total number of packets received during this sampling interval that were less than 64 octets in length (excluding framing bits but including FCS

octets) had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error).

Note that it is entirely normal for etherHistoryFragments to increment. This is because it counts both runts (which are normal occurrences due to collisions) and noise hits.

What is etherHistoryFragments?

This object counts the total number of frames (less than 64 octets, including FCS checksum) received during a sampling interval that had either a bad Frame Check Sequence (CRC error) or misaligned bits. RMON collectors use this metric to identify Ethernet transmission quality issues or line noise that introduces bit errors. Fragment counts help network troubleshooters distinguish between collision-related undersized frames and damaged frames.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.16.2.2.1.12
snmpwalk -v2c -c public <target> RMON-MIB::etherHistoryFragments

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.16.2.2.1.12.1
snmpget -v2c -c public <target> RMON-MIB::etherHistoryFragments.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.2etherHistoryTableRFC1271-MIB
1.3.6.1.2.1.16.2.2.1etherHistoryEntryRFC1271-MIB
1.3.6.1.2.1.16.2.2.1.12etherHistoryFragmentsRMON-MIB