sets the timestamp of SEL records written prior to a system boot record using the timestamp from
the boot record.
Configuring Thresholds
There are two basic types of threshold:
•
Range-based thresholds for which a variety of values can be set. Example uses: for
temperatures, voltages, and RPM-sensing fans.
•
State-based thresholds that have fixed values like OK or Critical. Example uses: for
rotation-sensing fan, chassis door, and memory array.
To Configure a Range-Based Threshold
Most voltage sensors, temperature sensors, and RPM-sensing fans have one, two, or four
configurable thresholds, depending on your server. Example thresholds are:
•
Upper Critical
•
Upper Noncritical
•
Lower Noncritical
•
Lower Critical
Some special sensors do not have configurable thresholds and are displayed for monitoring
purposes only.
You can customize the threshold value to suit your working environment.
You can specify what action should occur when the sensor detects that one of the threshold values
has been crossed (i.e., the sensor state changes).
•
Status Changed to OK
•
Status Changed to Upper Critical
•
Status Changed from OK to Upper Noncritical
•
Status Changed from Critical to Upper Noncritical
These thresholds and sensor state changes let you configure progressive responses in PIC to
increasingly serious hardware conditions. For example, noncritical thresholds might be configured
to emit a beep from the speaker and send a broadcast message, while critical thresholds might
require more serious actions, like a server shutdown.
To configure a range-based threshold:
1. On the PIC main window, click beside the sensor name in the navigation pane to see the list
of available sensors.
2. Select an entry from the list.
3. Change the threshold values as needed on the Sensor Settings tab page.
4. Click <Apply> for any changes made to the threshold value configurations.
5. If you want to change the event actions associated with threshold state change conditions,
make the changes on the Alert Actions tab page.
6. Click <Apply> for any changes made to the alert action configuration.
22