Example outputs of the fse --status command
If software installation was successful, you should get the following (typical) outputs with the fse
Consolidated FSE system - FSE daemons running
FSE server - FSE daemons running
FSE client - FSE daemons running
Note that the actual process IDs (the numbers that follow the pid strings) will be different on your system.
Configuring and starting HSM Health Monitor
To use HSM Health Monitor, you need to configure it and start its daemon on the Linux systems that are included in the FSE implementation.
In a mixed or distributed FSE implementation, you need to start the HSM Health Monitor daemon on the consolidated FSE system or FSE server before starting the HSM Health Monitor daemon on the external FSE clients.
Configuring HSM Health Monitor
For details on configuration of the HSM Health Monitor utility, see the FSE user guide, chapter ”Monitoring and maintaining FSE”, section ”Low storage space detection”.
Starting the HSM Health Monitor daemon
To start the HSM Health Monitor daemon on the local system, invoke the following command:
# hhm start
Configuring and starting Log Analyzer
If you decide to use Log Analyzer for monitoring the log files, you need to configure it and start its daemons on the Linux systems on which you want to monitor the log files.
Configuring Log Analyzer
For details on configuration of the Log Analyzer utility, see the FSE user guide, chapter ”Monitoring and maintaining FSE”, section ”FSE log files”, subsection ”Monitoring and analyzing FSE log files”.
Starting the Log Analyzer daemon
To start the Log Analyzer daemons on the local system, depending on the event log file that you want to monitor, invoke the following commands:
#loganalyzer start
#loganalyzer_messages start
48 Installing FSE software