| Description | This table provides information associated with each
processor. Thresholds are provided to control the
behavior of the following objects from the
cimrMsuTrafficTable table.
-- cimrMsuTrafficRateState
-- cimrMsuTrafficRate
-- cimrMsuTrafficSize
-- cimrMsuProcDurWarning
-- cimrMsuProcDurOverloaded
Any changes to these thresholds will cause a reset of
measurements which is indicated by cimrMsuProcReset
and cimrMsuProcResetTimestamp objects.
Notifications thresholds.
In order to generate notifications when MSU rate switch
states the customer must define traffic levels using the
following objects. When the global objects contain
non-zero values they will act as defaults to all entries
in table.
global:
- cimrMsuRateAcceptableThreshold
- cimrMsuRateWarningThreshold
- cimrMsuRateOverloadedThreshold
Per processor:
- cimrMsuProcAcceptableThreshold
- cimrMsuProcWarningThreshold
- cimrMsuProcOverloadedThreshold
The global thresholds only apply when all of the threshold
objects at instance level are set to zero. Set operations
against thresholds must be performed as single operation.
Calculation of cimrMsuTrafficRateState object is performed in
the following manner to only report significant changes
in traffic. In order to switch to a higher state the
traffic rate must equal or exceed the next higher
threshold. For example when current state is acceptable
the traffic must equal or exceed value specified by
warning-threshold to obtain warning state. In order to
switch to a lower state the traffic rate must be less than
the next lower threshold. For example when current state
is overloaded the traffic must drop below warning-threshold
to obtain warning state.
Example:
Acceptable-Threshold = 2000
Warning-Threshold = 2500
Overloaded-Threshold = 3000
Sample Rate Old State New State
------ ---- ---------- ----------
1 2000 Acceptable Acceptable
2 2500 Acceptable Warning
3 2200 Warning Warning
4 2000 Warning Acceptable
5 3000 Acceptable Overloaded
5 1000 Overloaded Acceptable |