User's Manual

190 Monitoring and maintaining FSE
Triggered actions section of the configuration file
NOTE: The actions definitions provided in the configuration file are given only as an example, they are
not used by default. To use them, they have to be specified in the monitored items definitions section. For
more information, see section ”Monitored items definitions” on page 190.
Monitored items definitions
A monitored item definition section is marked by a string representing the item name
([MonitoredItem]). When specifying a monitored item name, pay attention to the following
requirements and limitations:
The name is case-sensitive.
If used for an HSM file system, the monitored item name should match the name of the corresponding
FSE partition as defined in the FSE partition configuration file.
You cannot use the name action, system, or mail for a monitored item name.
Each monitored item definition section defines the following:
the file system type of the monitored item
mount point (on Linux systems) or full path (on Windows systems) of the monitored item
critical and warning thresholds for the monitored item and the assigned actions — every threshold has
exactly one action assigned
A threshold defines the percentage of the used capacity on the monitored file system or on the FSE media
pool assigned to the monitored file system. Thus, the actions defined for any monitored file system are
started if the threshold set is crossed either on the monitored file system or on the assigned FSE media pool.
IMPORTANT: For a file system, the physically available space and not the space provided to users is
monitored. For example, on Linux platforms using Ext3 file systems, by default only 95% of the disk storage
space can be used by users of the file system, the rest is reserved for Linux operating system purposes. If an
HHM threshold is set to 90%, the defined action will start when there is only 5% of the space assigned by
the operating system to users left.
[action]
# action contains available actions to be taken in case a threshold is crossed.
# Two actions are predefined and will be used to send e-mails in case
# the threshold is crossed upwards (email_ge) or downwards (email_lt)
# free defined actions may follow here. Note that the action is called in
# a shell environment. The logfile will contain the output of the command.
# There are variable parameters being replaced at runtime :
# %%MOUNTPOINT%% will be replaced by the corresponding mountpoint
# %%HOST%% will be replaced by the HOST where the filesystem is located
# %%P-STATUS%% will be replaced by the partition status.
stopsystem-ge: fse --stop
umount-ge: mymount.sh %%MOUNTPOINT%% %%P-STATUS%%
mount-ge: mymount.sh %%MOUNTPOINT%% %%P-STATUS%%
clt-umount-ge: %%HOST%%:mymount.bat %%MOUNTPOINT%% %%P-STATUS%%
clt-mount-ge: %%HOST%%:mymount.bat %%MOUNTPOINT%% %%P-STATUS%%