Shortcut Menu

Skip

Main Navigation

Choose your language


ActiveXperts Network Monitor supports SNMP based checks.It ships with free SNMP GET and SNMP TRAP utilities. It also offers many SNMP scripts (PowerShell and VBScript).

Use ActiveXperts Netork Monitor to monitor your virtualization servers, domains, computers and devices. It runs on a single Windows server, without agents required on the monitored systems. It has many built-in checks and also allows administrators to create custom checks using PowerShell, VBScript and SSH.


CISCO-PORT-STORM-CONTROL-MIB.mib object view, vendor Cisco

Introduction

Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers). This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.

ActiveXperts Network Monitor can import mib file CISCO-PORT-STORM-CONTROL-MIB and use it to monitor vendor specific OID's.

CISCO-PORT-STORM-CONTROL-MIB file content

Object view of CISCO-PORT-STORM-CONTROL-MIB:

Scalar Object
cpscThresholdEntry .1.3.6.1.4.1.9.9.362.1.1.1.1
A 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.
cpscActionEntry .1.3.6.1.4.1.9.9.362.1.1.2.1
An entry containing the storm control action configuration information. An entry is created for each interface that can support the storm control feature.
cpscNotificationThreshold .1.3.6.1.4.1.9.9.362.1.1.3
The 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.
cpscStatusEntry .1.3.6.1.4.1.9.9.362.1.2.1.1
A 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.
cpscHistoryEntry .1.3.6.1.4.1.9.9.362.1.2.2.1
A collection of storm control history entries per interface and per traffic type. The number of such entries available is implementation-dependent.
Tabular Object
cpscTrafficType .1.3.6.1.4.1.9.9.362.1.1.1.1.1
This 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).
cpscUpperThreshold .1.3.6.1.4.1.9.9.362.1.1.1.1.2
This 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.
cpscLowerThreshold .1.3.6.1.4.1.9.9.362.1.1.1.1.3
This 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.
cpscAction .1.3.6.1.4.1.9.9.362.1.1.2.1.1
This object represents the storm control action taken when the traffic of a particular type exceeds the configured upper threshold values.
cpscNotificationControl .1.3.6.1.4.1.9.9.362.1.1.2.1.2
This 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.
cpscStatus .1.3.6.1.4.1.9.9.362.1.2.1.1.1
This 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.
cpscCurrentLevel .1.3.6.1.4.1.9.9.362.1.2.1.1.2
This 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).
cpscSuppressedPacket .1.3.6.1.4.1.9.9.362.1.2.1.1.3
This 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.
cpscHistoryTrafficType .1.3.6.1.4.1.9.9.362.1.2.2.1.1
The traffic type corresponding to this storm history entry.
cpscHistoryIndex .1.3.6.1.4.1.9.9.362.1.2.2.1.2
A 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.
cpscHistoryStartTime .1.3.6.1.4.1.9.9.362.1.2.2.1.3
The value of sysUpTime when the storm event was declared on the interface for the particular traffic type, and storm control measures were taken.
cpscHistoryEndTime .1.3.6.1.4.1.9.9.362.1.2.2.1.4
The 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.
Table
cpscThresholdTable .1.3.6.1.4.1.9.9.362.1.1.1
A table of storm control threshold configuration entries.
cpscActionTable .1.3.6.1.4.1.9.9.362.1.1.2
A table of storm control action entries.
cpscStatusTable .1.3.6.1.4.1.9.9.362.1.2.1
A table of storm control status entries.
cpscHistoryTable .1.3.6.1.4.1.9.9.362.1.2.2
A 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.
Trap
cpscEvent .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.
Object Identifier
ciscoPortStormControlMIB .1.3.6.1.4.1.9.9.362
The MIB module for managing Cisco Port Storm Control.
ciscoPortStormControlMIBNotifs .1.3.6.1.4.1.9.9.362.0
ciscoPortStormControlMIBObjects .1.3.6.1.4.1.9.9.362.1
ciscoPortStormControlMIBConform .1.3.6.1.4.1.9.9.362.2
cpscConfigObjects .1.3.6.1.4.1.9.9.362.1.1
cpscStatusObjects .1.3.6.1.4.1.9.9.362.1.2
cpscNotificationsPrefix .1.3.6.1.4.1.9.9.362.0.1
ciscoPortStormControlMIBCompliances .1.3.6.1.4.1.9.9.362.2.1
ciscoPortStormControlMIBGroups .1.3.6.1.4.1.9.9.362.2.2
Group
cpscConfigurationGroup .1.3.6.1.4.1.9.9.362.2.2.1
A collection of objects to configure the Port Storm Control feature on a given interface.
cpscNotifConfigurationGroup .1.3.6.1.4.1.9.9.362.2.2.4
A collection of objects to configure notification information.
cpscNotificationGroup .1.3.6.1.4.1.9.9.362.2.2.3
A collection of notification objects for user with the cisco port storm control mib.
cpscStatusGroup .1.3.6.1.4.1.9.9.362.2.2.2
A collection of objects to provide storm control status on a given interface.
cpscStatisticsGroup .1.3.6.1.4.1.9.9.362.2.2.5
A collection of objects to provide storm control statistics information.
cpscHistoryGroup .1.3.6.1.4.1.9.9.362.2.2.6
A collection of objects to provide storm control history information on a given interface.