CISCO-PORT-STORM-CONTROL-MIB

        The MIB module for managing Cisco Port Storm Control.
    
Source file
CISCO-PORT-STORM-CONTROL-MIB
Last revised
Identity
ciscoPortStormControlMIB
Base OID
1.3.6.1.4.1.9.9.362
Imported Objects
CISCO-SMI ciscoMgmt
IF-MIB ifIndex
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter64 Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page)
SNMPv2-TC TEXTUAL-CONVENTION (no object page) TimeStamp TruthValue
Net-SNMP examples using the cisco 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 'CISCO-PORT-STORM-CONTROL-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-PORT-STORM-CONTROL-MIB::ciscoPortStormControlMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-PORT-STORM-CONTROL-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-PORT-STORM-CONTROL-MIB::ciscoPortStormControlMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (30)
.1.3.6.1.4.1.9.9.362
.1.3.6.1.4.1.9.9.362.0
.1.3.6.1.4.1.9.9.362.0.1
.1.3.6.1.4.1.9.9.362.1
.1.3.6.1.4.1.9.9.362.1.1
.1.3.6.1.4.1.9.9.362.1.1.1
.1.3.6.1.4.1.9.9.362.1.1.1.1
.1.3.6.1.4.1.9.9.362.1.1.1.1.1
0.01 PercentageInteger32
.1.3.6.1.4.1.9.9.362.1.1.1.1.2
0.01 PercentageInteger32
.1.3.6.1.4.1.9.9.362.1.1.1.1.3
.1.3.6.1.4.1.9.9.362.1.1.2
.1.3.6.1.4.1.9.9.362.1.1.2.1
.1.3.6.1.4.1.9.9.362.1.1.2.1.1
Enumeration
.1.3.6.1.4.1.9.9.362.1.1.2.1.2
Notifications per MinuteInteger32
.1.3.6.1.4.1.9.9.362.1.1.3
.1.3.6.1.4.1.9.9.362.1.2
.1.3.6.1.4.1.9.9.362.1.2.1
.1.3.6.1.4.1.9.9.362.1.2.1.1
.1.3.6.1.4.1.9.9.362.1.2.1.1.1
0.01 PercentageInteger32
.1.3.6.1.4.1.9.9.362.1.2.1.1.2
.1.3.6.1.4.1.9.9.362.1.2.1.1.3
.1.3.6.1.4.1.9.9.362.1.2.2
.1.3.6.1.4.1.9.9.362.1.2.2.1
.1.3.6.1.4.1.9.9.362.1.2.2.1.1
Integer32
.1.3.6.1.4.1.9.9.362.1.2.2.1.2
.1.3.6.1.4.1.9.9.362.1.2.2.1.3
.1.3.6.1.4.1.9.9.362.1.2.2.1.4
.1.3.6.1.4.1.9.9.362.2
.1.3.6.1.4.1.9.9.362.2.1
.1.3.6.1.4.1.9.9.362.2.2
Dependencies (7) 5 direct · 2 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
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. CISCO-SMIcisco
  3. SNMPv2-TCrfc
  4. IANAifType-MIBrfc
  5. SNMPv2-CONFrfc
  6. SNMPv2-MIBrfc
  7. IF-MIBrfc
  8. CISCO-PORT-STORM-CONTROL-MIBciscoselected
Type Definitions (3)
Enumeration
filter(1)
shutdown(2)
Enumeration
inactive(1)
forwarding(2)
trafficTypeFiltered(3)
allTrafficFiltered(4)
shutdown(5)
Enumeration
broadcast(1)
multicast(2)
unicast(3)
all(4)
Conformance Groups (7)
A collection of objects to configure the Port Storm
Control feature on a given interface.
.1.3.6.1.4.1.9.9.362.2.2.1
A collection of objects to provide storm control
status on a given interface.
.1.3.6.1.4.1.9.9.362.2.2.2
A collection of notification objects for user with
the cisco port storm control mib.
.1.3.6.1.4.1.9.9.362.2.2.3
A collection of objects to configure notification
information.
.1.3.6.1.4.1.9.9.362.2.2.4
A collection of objects to provide storm control
statistics information.
.1.3.6.1.4.1.9.9.362.2.2.5
A collection of objects to provide storm control
history information on a given interface.
.1.3.6.1.4.1.9.9.362.2.2.6
A collection of notification objects for user with
the cisco port storm control mib.
.1.3.6.1.4.1.9.9.362.2.2.7
Compliance Statements (2)

OID .1.3.6.1.4.1.9.9.362.2.1.1
The compliance statement for the cisco port storm
control MIB.
Required groups
mandatory cpscConfigurationGroup
optional cpscNotifConfigurationGroup This group is mandatory if the managed system supports
notifications for storm events.
optional cpscNotificationGroup This group is mandatory if the managed system supports
notifications for storm events.
optional cpscStatusGroup This group is mandatory if the storm control status
information is available in the managed system.
optional cpscStatisticsGroup This group is mandatory if the storm control statistics
information is available in the managed system.
optional cpscHistoryGroup This group is mandatory if the managed system maintains
such storm control history information.
Object refinements
ObjectAccessSyntaxDescription
cpscLowerThreshold readonly
Write access is not required.
cpscAction readonly
Write access is not required.

OID .1.3.6.1.4.1.9.9.362.2.1.2
Please enter description here
Required groups
mandatory cpscConfigurationGroup
optional cpscNotifConfigurationGroup This group is mandatory if the managed system supports
notifications for storm events.
optional cpscNotificationGroupRev1 This group is mandatory if the managed system supports
notifications for storm events.
optional cpscStatusGroup This group is mandatory if the storm control status
information is available in the managed system.
optional cpscStatisticsGroup This group is mandatory if the storm control statistics
information is available in the managed system.
optional cpscHistoryGroup This group is mandatory if the managed system maintains
such storm control history information.
Object refinements
ObjectAccessSyntaxDescription
cpscLowerThreshold readonly
Write access is not required.
cpscAction readonly
Write access is not required.
Notifications / Traps (2)
NameOIDDescription
cpscEvent deprecated
.1.3.6.1.4.1.9.9.362.0.1.1
This notification is sent by the implementation when
a storm event occurs on an interface with respect to
a particular traffic type.
cpscEvent is deprecated and replaced by cpscEventRev1.
.1.3.6.1.4.1.9.9.362.0.2
This notification is sent by the implementation when
a storm event occurs on an interface with respect to
a particular traffic type.
cpscEventRev1 deprecates cpscEvent to make it RFC 2578
compliant. According to section 8.5 of RFC 2578, the next
to last sub-identifier in the name of any newly-defined
notification must have the value zero.