Description: This table provides threshold information for each alarm that has user-defined thresholds.

Thresholds can be thought of as single or ranged. A single threshold is one in which an alarm is generated if a measurement falls below or rises above the threshold. For example, if we have a temperature threshold of 50 C, any temperature above this threshold will generate an alarm. A range in this case is not needed. However, common sense dictates that a value which cannot be represented by the hardware should not be used in a SET, so an upper range (or lower as the case may be) is still implied.

The settings in this table are specific for every CTA within a distributed system. They are also specific to a particular alarm type, represented by the alarm ID. Since there may be as many as two thresholds for an alarm (minimum and maximum), this must be accounted for also. Therefore, this table is indexed by the following:

- alarmThreshold4CTA - alarmThresholdalarmID - alarmThresholdIdx

If not applicable to a particular agent implementation, 'no such object' must be returned to any request within this table.

All alarms with a single threshold or simple linear ranged threshold can be completely described by the few basic objects in this table and the network manager can easily set up these thresholds properly. In this case, alarmThresholdPointerToValueLookupTableMainIndex is set to 0. For example, NodeX DL and UL RSSI alarms fall into this category.

For alarms with more complex threshold ranges or whose set values cannot describe them, the object, alarmThresholdPointerToValueLookupTableMainIndex points into alarmThresholdValueLookupTable where each allowed value is defined and described. These alarms include NodeX VSWR ratios, external alarm polarity, etc.