EXTREME-IP-SECURITY-MIB :: esAnomalyTcpFragmentReason

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › EXTREME-IP-SECURITY-MIB › esAnomalyTcpFragmentReason

esAnomalyTcpFragmentReason

Module: EXTREME-IP-SECURITY-MIB

OID (symbolic): EXTREME-IP-SECURITY-MIB::esAnomalyTcpFragmentReason

OID (numeric): 1.3.6.1.4.1.1916.1.34.2.19

Node type: OBJECT-TYPE

Type: TcpFragmentAnomalyReason

Access: accessible-for-notify

Description: TCP fragment anomaly reason code

What is esAnomalyTcpFragmentReason?

A coded reason for why a TCP packet was flagged by the fragment anomaly check: either the IP payload was smaller than the minimum valid TCP header size, or the packet's IP fragment offset indicated it was fragmented. Use it with esAnomalyTcpHdrSize to see the underlying data that triggered the trap.

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.1916extremeA3COM51-SS9000SX
1.3.6.1.4.1.1916.1extremeAgentEXTREME-BASE-MIB
Numeric OIDNameModule
1.3.6.1.4.1.1916.1.34extremeIpSecurityEXTREME-IP-SECURITY-MIB
1.3.6.1.4.1.1916.1.34.2extremeIpSecurityAnomalyTrapsEXTREME-IP-SECURITY-MIB
1.3.6.1.4.1.1916.1.34.2.19esAnomalyTcpFragmentReasonEXTREME-IP-SECURITY-MIB