| Set the alarm type that may be sent. Options are Rising, Falling, and Both. |
| Rising or Both: If the first sample after this entry becomes valid is greater than or |
StartupAlarm | equal to the Rising Threshold, then a single rising alarm will be |
generated. | |
| Falling or Both: If the first sample after this entry becomes valid is less than or |
| equal to the Falling Threshold, then a single falling alarm will be |
| generated. |
|
|
Value | This field shows the value of the monitored data. |
|
|
Rising Threshold | RMON alarm rising threshold (0~4294967295). |
|
|
Falling Threshold | RMON alarm falling threshold (0~4294967295). |
|
|
| This index is used when a rising threshold is crossed. You must refer to the |
Rising Event Index | index of RMON Event table. If there is no corresponding entry in the Event table, |
| then no association exists. |
|
|
| This index is used when a falling threshold is crossed. You must refer to the |
Falling Event Index | index of RMON Event table. If there is no corresponding entry in the Event table, |
| then no association exists. |
|
|
Following figure shows an example of RMON alarm for ABSOLUTE sample type. As shown in the figure, the counting value keeps increasing. But when the value overflows, the system will count from zero again. The sample in T2 is the first one crossing the Rising Threshold, so an alarm occurs. No alarms will be generated afterwards unless the counting value overflows and count from zero again (the sample in T10 causes an alarm again).
- 200 -