EXTREME-V2TRAP-MIB :: extremeRateLimitExceededTrapType

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › EXTREME-V2TRAP-MIB › extremeRateLimitExceededTrapType

extremeRateLimitExceededTrapType

Module: EXTREME-V2TRAP-MIB

OID (symbolic): EXTREME-V2TRAP-MIB::extremeRateLimitExceededTrapType

OID (numeric): 1.3.6.1.4.1.1916.4.1.0.7.1

Node type: OBJECT-TYPE

Type: INTEGER

Access: accessible-for-notify

Description: The trap condition being reported.

What is extremeRateLimitExceededTrapType?

This enumerated value reports which rate-limiting condition triggered the trap: exceededCIR(1) means the Committed Information Rate was exceeded, and droppedBytes(2) means bytes were actually dropped as a result. An admin uses this to distinguish a warning-level CIR breach from an event where traffic was actually discarded, helping prioritize investigation of QoS profile congestion. For example, seeing droppedBytes(2) alongside a high extremeExceededByteCount signals real traffic loss on that rate-limited flow, not just a threshold crossing.

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.4extremeV2TrapsEXTREME-BASE-MIB
Numeric OIDNameModule
1.3.6.1.4.1.1916.4.1extremeCoreSCTrapsEXTREME-V2TRAP-MIB
1.3.6.1.4.1.1916.4.1.0extremeCoreSCTrapPrefixEXTREME-V2TRAP-MIB
1.3.6.1.4.1.1916.4.1.0.7extremeRateLimitExceededTrapEXTREME-V2TRAP-MIB
1.3.6.1.4.1.1916.4.1.0.7.1extremeRateLimitExceededTrapTypeEXTREME-V2TRAP-MIB