HPN-ICF-STORM-CONSTRAIN-MIB

        The Storm-Constrain function is used to avoid the
packet-storm on a port.  Three types of flux can be
set observed respectively: broadcast, multicast and
unicast.  If an observed flux exceeds its upper limit,
this kind of flux will be recognized as over-upper-flux.
This kind of flux will be considered as normal-flux
until it falls below its lower limit.  If any type of
observed flux is over-upper-flux, the port will change
its status to controlled-status, that is to stop packet
forwarding to avoid storm.  Only when all the observed
fluxes are not over-upper-flux, will the port return to
normal(forwarding) status.
    
Source file
HPN-ICF-STORM-CONSTRAIN-MIB
Last revised
Identity
hpnicfStormConstrain
Base OID
1.3.6.1.4.1.11.2.14.11.15.2.66
Imported Objects
HPN-ICF-OID-MIB hpnicfCommon
RFC1213-MIB ifIndex
SNMPv2-SMI Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-IDENTITY (no object page) OBJECT-TYPE (no object page)
SNMPv2-TC RowStatus TEXTUAL-CONVENTION (no object page)
Net-SNMP examples using the hp MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'HPN-ICF-STORM-CONSTRAIN-MIB' -M '/opt/observium/mibs/hp:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'HPN-ICF-STORM-CONSTRAIN-MIB::hpnicfStormConstrain'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'HPN-ICF-STORM-CONSTRAIN-MIB' -M '/opt/observium/mibs/hp:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'HPN-ICF-STORM-CONSTRAIN-MIB::hpnicfStormConstrain'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (20)
.1.3.6.1.4.1.11.2.14.11.15.2.66
.1.3.6.1.4.1.11.2.14.11.15.2.66.1
Enumeration
.1.3.6.1.4.1.11.2.14.11.15.2.66.1.1
.1.3.6.1.4.1.11.2.14.11.15.2.66.1.2
.1.3.6.1.4.1.11.2.14.11.15.2.66.2
.1.3.6.1.4.1.11.2.14.11.15.2.66.2.1
.1.3.6.1.4.1.11.2.14.11.15.2.66.2.1.1
Enumeration
.1.3.6.1.4.1.11.2.14.11.15.2.66.2.1.1.1
.1.3.6.1.4.1.11.2.14.11.15.2.66.2.1.1.10
.1.3.6.1.4.1.11.2.14.11.15.2.66.2.1.1.11
Enumeration
.1.3.6.1.4.1.11.2.14.11.15.2.66.2.1.1.12
.1.3.6.1.4.1.11.2.14.11.15.2.66.2.1.1.2
.1.3.6.1.4.1.11.2.14.11.15.2.66.2.1.1.3
.1.3.6.1.4.1.11.2.14.11.15.2.66.2.1.1.4
.1.3.6.1.4.1.11.2.14.11.15.2.66.2.1.1.5
.1.3.6.1.4.1.11.2.14.11.15.2.66.2.1.1.6
.1.3.6.1.4.1.11.2.14.11.15.2.66.2.1.1.7
.1.3.6.1.4.1.11.2.14.11.15.2.66.2.1.1.8
.1.3.6.1.4.1.11.2.14.11.15.2.66.2.1.1.9
.1.3.6.1.4.1.11.2.14.11.15.2.66.3
Dependencies (7) 4 direct · 3 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Type Definitions (1)
Enumeration
none(1)
packetsPerSecond(2)
ratio(3)
bytesPerSecond(4)
kbitsPerSecond(5)
Notifications / Traps (2)
NameOIDDescription
.1.3.6.1.4.1.11.2.14.11.15.2.66.3.1
This trap message is generated when any type of the
flux exceeds its upper limit on a port.
.1.3.6.1.4.1.11.2.14.11.15.2.66.3.2
This trap message is generated when a flux which used
to overflow its upper limit, falls below its lower
limit on a port.