Home/Catalog/CISCO-PORT-STORM-CONTROL-MIB

CISCO-PORT-STORM-CONTROL-MIB

AI MIB Summary

The CISCO-PORT-STORM-CONTROL-MIB enables monitoring and configuration of broadcast, multicast, and unknown unicast traffic thresholds on Cisco switches to prevent network storms. It exposes specific counters for storm-triggered packet drops and current traffic rates to facilitate real-time interface anomaly detection and automated mitigation policy enforcement.

The MIB module for managing Cisco Port Storm Control.
Main OID:
ciscoPortStormControlMIB.1.3.6.1.4.1.9.9.362
32
Objects
Active
Status
5
Dependencies

Imported Objects

Objects

32 total
Object Name
ciscoPortStormControlMIBThe MIB module for managing Cisco Port Storm Control.
MODULE-IDENTITY
.1.3.6.1.4.1.9.9.362
ciscoPortStormControlMIBNotifs
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.362.0
cpscNotificationsPrefix
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.362.0.1
cpscEventThis 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.
NOTIFICATION-TYPE
.1.3.6.1.4.1.9.9.362.0.1.1
cpscEventRev1This 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.
NOTIFICATION-TYPE
.1.3.6.1.4.1.9.9.362.0.2
ciscoPortStormControlMIBObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.362.1
cpscConfigObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.362.1.1
cpscThresholdTableA table of storm control threshold configuration entries.
SEQUENCE OF CPortSCThresholdEntry
.1.3.6.1.4.1.9.9.362.1.1.1
cpscThresholdEntryA collection of storm control threshold configuration entries. Storm control can be configured for multiple traffic types on a given interface. One entry is created for each interface and the traffic type that can be monitored by the device.
CPortSCThresholdEntry
.1.3.6.1.4.1.9.9.362.1.1.1.1
cpscTrafficTypeThis object identifies a particular traffic type for which a management station desires to configure storm control on the given interface (which is identified by its ifIndex).
CPortStormControlTrafficType
.1.3.6.1.4.1.9.9.362.1.1.1.1.1
cpscUpperThresholdThis object represents the upper threshold of total amount of a particular traffic type that can be seen on a given interface, after which a storm event is declared and storm control action is taken. The value represents the traffic as a percentage of total bandwidth of the interface, in units of 0.01 %. For example, if a management station sets the value of cpscUpperThreshold.3.1 as 4000, it means the following: a) storm control is enabled on the interface with ifIndex = 3 for broadcast (1) packets b) if the broadcast traffic received per second on the interface is more than (4000*0.01 = 40%) of the total interface bandwidth, then the system will take storm control actions, as indicated by cpscAction.3 . It should be noted that setting the upper threshold value to anything other than 100% results in storm control being automatically enabled on the given interface, for the given traffic type. An implementation may not be able to support different threshold values for different traffic types, in which case changing the value for one traffic type will automatically result in the threshold value for other types also modified. The default value of this object is implementation- dependent.rw
INTEGER
.1.3.6.1.4.1.9.9.362.1.1.1.1.2
cpscLowerThresholdThis object represents the lower threshold of total amount of a particular traffic type. When a filter action (see cpscAction) is in effect on an interface because of a previous storm event, the value of this object determines when the system will stop the filter action. The value represents traffic as percent of total bandwidth of the interface, in units of 0.01 %. For example, if a broadcast(1) storm occurred on an interface with ifIndex 3, and the value of cpscLowerThreshold.3.1 is 2500 (25%), then the system will stop filtering broadcast traffic on that interface if it drops below 25% of the total bandwidth. This value will be ignored if a shutdown action is configured. The value of this object must be equal to or less than the value of the upper threshold specified by cpscUpperThreshold for the same entry. The default value of this object is implementation- dependent. On platforms that only support one threshold level for this traffic type and interface,this object is read-only and always has the same value of the corresponding cpscUpperThreshold for the same entry.rw
INTEGER
.1.3.6.1.4.1.9.9.362.1.1.1.1.3
cpscActionTableA table of storm control action entries.
SEQUENCE OF CPortSCActionEntry
.1.3.6.1.4.1.9.9.362.1.1.2
cpscActionEntryAn entry containing the storm control action configuration information. An entry is created for each interface that can support the storm control feature.
CPortSCActionEntry
.1.3.6.1.4.1.9.9.362.1.1.2.1
cpscActionThis object represents the storm control action taken when the traffic of a particular type exceeds the configured upper threshold values.rw
CPortStormControlActionType
.1.3.6.1.4.1.9.9.362.1.1.2.1.1
cpscNotificationControlThis object controls when a storm control notification will be generated. If the object is set to none(1), no notifications will be generated. A notification will be generated when a storm event is detected or cleared when the object is set to stormOccurred(2) or stormCleared(3) respectively. If the object is set to both(4), a notification will be generated both when a storm event is detected and cleared. NOTE: a) The default value of this object is none(1). b) Irrespective of the value of this object, the value of the global object cpscNotificationThreshold controls whether or not a notification will be generated at a given point.rw
Enumeration
.1.3.6.1.4.1.9.9.362.1.1.2.1.2
cpscNotificationThresholdThe value of object controls the global rate of storm control notifications generated by an entity per minute. A value of 0 indicates no limit, and the entity will generate notifications for each storm event as governed by the cpscNotificationControl for a given interface.rw
INTEGER
.1.3.6.1.4.1.9.9.362.1.1.3
cpscStatusObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.362.1.2
cpscStatusTableA table of storm control status entries.
SEQUENCE OF CPortSCStatusEntry
.1.3.6.1.4.1.9.9.362.1.2.1
cpscStatusEntryA collection of storm control status entries, one per interface and traffic type. An entry is created for each storm control capable interface and the traffic type with the storm control status information.
CPortSCStatusEntry
.1.3.6.1.4.1.9.9.362.1.2.1.1
cpscStatusThis object identifies the status of storm control on the interface (identified by ifIndex) corresponding to a particular traffic type (identified by cpscTrafficType). A value of inactive indicates that no storm control has been enabled on the interface for the traffic type.ro
CPortStormControlStatusType
.1.3.6.1.4.1.9.9.362.1.2.1.1.1
cpscCurrentLevelThis object identifies the current level of traffic of a particular type on a given interface, as a percentage of the total interface bandwidth. When storm control is inactive, the value is 10000, indicating the maximum level (100% of the particular traffic type is allowed to be received).ro
INTEGER
.1.3.6.1.4.1.9.9.362.1.2.1.1.2
cpscSuppressedPacketThis object represents the total number of packets of a particular traffic type that have been suppressed on a given interface by storm control filter action.ro
Counter64
.1.3.6.1.4.1.9.9.362.1.2.1.1.3
cpscHistoryTableA conceptual table to represent the history of storm events on an interface. Management station can use this to get information about the timeline of storm events as to when each event occurred, and when it ended.
SEQUENCE OF CPortSCHistoryEntry
.1.3.6.1.4.1.9.9.362.1.2.2
cpscHistoryEntryA collection of storm control history entries per interface and per traffic type. The number of such entries available is implementation-dependent.
CPortSCHistoryEntry
.1.3.6.1.4.1.9.9.362.1.2.2.1
cpscHistoryTrafficTypeThe traffic type corresponding to this storm history entry.
CPortStormControlTrafficType
.1.3.6.1.4.1.9.9.362.1.2.2.1.1
cpscHistoryIndexA number that uniquely identifies one storm control history entry for a given interface. The index starts at 1 and increases by 1. Although this MIB specification stipulates a maximum of 1K entries, the actual maximum number of history entries returned per interface is implementation-dependent. When the value of this index reaches the actual maximum number of entries supported by an implementation, it will wrap around to 1.
Integer32 (1..1024 )
.1.3.6.1.4.1.9.9.362.1.2.2.1.2
cpscHistoryStartTimeThe value of sysUpTime when the storm event was declared on the interface for the particular traffic type, and storm control measures were taken.ro
TimeStamp (SNMPv2-TC)
.1.3.6.1.4.1.9.9.362.1.2.2.1.3
cpscHistoryEndTimeThe value of sysUpTime when the storm ceased to exist and the interface was set to its previous normal state. If the interface was shutdown due to user configuration, then the value will be equal to the value of sysUpTime when the interface was shutdown. If the storm event continues to persist when this object is queried, the value returned will be 0.ro
TimeStamp (SNMPv2-TC)
.1.3.6.1.4.1.9.9.362.1.2.2.1.4
ciscoPortStormControlMIBConform
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.362.2
ciscoPortStormControlMIBCompliances
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.362.2.1
ciscoPortStormControlMIBGroups
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.362.2.2
CISCO-PORT-STORM-CONTROL-MIB - SNMP MIB Reference | MIBs Explorer