|
|
|
Configures the number of times that an agent-based measurement threshold must be exceeded for an alarm to be generated.
alarm-threshold-exceeded <count>
| Argument |
Description |
|---|---|
Number of times the threshold must be exceeded for an alarm to be generated. The valid range is 1–255. |
|
Must be in Chatter Configuration command mode.For information on how to access this mode, see Accessing and exiting command modes.
Configures the number of times that an agent-based measurement threshold must be exceeded for an alarm to be generated. This command applies to:
Absolute alarms are generated when tolerance thresholds are exceeded the number of times that you specify in this command.
Relative alarms are generated when the most recent results for a specific test show an abrupt increase or decrease. The thresholds for determining an “abrupt increase or decrease” are self-adjusting thresholds based on a statistical technique. Note that if the measurement remains near or outside the threshold, the threshold adjusts to reflect this changed norm. Once the threshold self-adjusts, the alarm clears even though the measurement itself has not changed. The steady state becomes the threshold value. This value can be higher or lower than the configured threshold.
The no command restores the default value of 10.
Note that you must balance the test rate with alarm sensitivity to meet your needs. For example, if the test rate is once per minute, and the zone hierarchy has 60 cells, all cells are tested once an hour. If you set the system to generate an alarm when the threshold is exceeded 10 times, the system will take 10 hours to generate an alarm for a cell.
To prevent a few spurious points from setting off an alarm, Avaya recommends that you set the system to generate an alarm when the threshold is exceeded no less than five times. Generally an alarm should indicate a persistent condition.
|
|
|