If the configuration file includes more than one line for a disk family, the interface software applies the threshold on each line independently from the threshold on any other line, even though the family or unit may be the same.
For example, if the configuration file contained the following two lines
FAMILY 5. FAMILY 10.
The interface software would send a message to Operations Sentinel and raise an alarm with the severity of Major (the default) when the available space crosses the 10% threshold. The same alarm is raised with the same severity and text when the available space crosses the 5 percent threshold.
To have the alarm text updated without raising a different alarm, the severity must change. Using the optional severity parameter allows you to set the severity explicitly. See Section 3.
family–name [threshold [severity]] [AREASIZE area-size].
family–name (index) [threshold [severity]] [AREASIZE area-size].
You can set severity to Critical, Major, Minor, or Warning. Operations Sentinel inserts the specified severity in the AVAILABLE SPACE message. See Section 4. If you omit the severity level or specify it incorrectly, it defaults to Major.
Example
The configuration file for the host RSA2 contains the following:
PACK1 5 CRITICAL. PACK1 10 MAJOR. PACK1.
When the available space on PACK1 drops to 9%, Operations Sentinel raises an alarm with the alarm ID RSA2PACK1 and Severity MAJOR.
If the available space drops to 4%, Operations Sentinel raises the same alarm; only this time, the severity is CRITICAL. If the available space rises to 5%, Operations Sentinel clears the alarm, and reraises the alarm with MAJOR severity. If the available space rises to 10%, Operations Sentinel clears the alarm.
In addition, since PACK1 is also specified without a threshold, the interface software reports the utilization of PACK1 for display in Operations Sentinel Console.