fpl_em(1m)fpl_em(1m)NAME
- monitors the IPMI Forward Progess Log (FPL) entries on the system
SYNOPSISDESCRIPTION
is the monitor for forward progress logs. The Intelligent Platform Man‐
agement Interface (IPMI) Forward Progress Log (FPL) monitor is designed
to monitor the IPMI FPL log entries on the system. IPMI is used by sys‐
tem firmware, the operating system, and other components to log both
hardware failures, warnings and forward progress during system boot.
The FPL Monitor reads all the FPL logs written to the file
/var/stm/logs/os/fpl.log.xx (where xx takes value from 00 to 24).
These logs are created by the IA64 core hardware monitor (ia64_corehw).
The ia64_corehw monitor reads the IPMI events from the Baseboard Man‐
agement Controller (BMC). It then logs the IPMI events in the
fpl.log.xx file in a circular fashion. An EMS event will be generated
by the FPL monitor for each IPMI E0 event which is defined in the event
database.
event monitoring requests are created using the Hardware Event Monitor‐
ing Request Manager (monconfig). Monitoring requests for status changes
caused by events are created using the Event Monitoring Service (EMS).
Both types of monitoring requests are handled by the EMS.
Options
does not support any options.
Resource Class Paths
Event Monitor /system/events/ipmi_fpl
Severity Levels
All hardware events are assigned a severity level by the monitor. These
severity levels reflect the potential impact of the event on system
operation. Monitoring requests are created based on the severity lev‐
els.
An event that will or has already caused data loss, system down
time, or other loss of service. Immediate action is required to
correct the problem. System operation will be impacted and nor‐
mal use of the hardware should not continue until the problem is
corrected. If ServiceGuard is installed and this is a critical
component, it will perform a package fail-over.
An event that may cause data loss, system down time, or other
loss of service if left uncorrected. The problem should be
repaired as soon as possible. System operation and normal use of
the hardware may be impacted. If ServiceGuard is installed and
this is a critical component, it will perform a package fail-
over.
An event that could escalate to a more serious condition if not
corrected. The problem should be repaired at a convenient time.
System operation should not be impacted and normal use of the
hardware can continue. If ServiceGuard
is installed, it will NOT perform a package fail-
over.
An event that will not likely escalate to a more serious condi‐
tion if let uncorrected. The problem can be repaired at a conve‐
nient time. System operation will not be interrupted and normal
use of the hardware can continue. If ServiceGuard is installed,
it will NOT perform a package fail-over.
An event that occurs as part of the normal operation of the
hardware. No action is required. If ServiceGuard is installed,
it will NOT perform a package fail-over.
Application Usage
This monitor will be deprecated on new server models. Please use System
Management Homepage (see hpsmh(1M)).
DEPENDENCIES
Event Monitoring Services (EMS) must be installed and running.
The ia64_corehw monitor must be installed and running to create the
fpl.log.xx files.
AUTHOR
was developed by HP.
FILES
Executable.
The resource dictionary for
Describes the location of various resources in the
resource hierarchy.
Monitor-specific configuration file containing default operational set‐
tings.
Multiple-view client configuration file containing default event-gener‐
ation settings.
Startup configuration file containing entries for all
monitoring requests.
Log file for all monitors using the Event Monitoring Service, including
Any errors are logged here.
SEE ALSOmonconfig(1m), EMS(5), psmmon(1m), ia64_corehw(1m)fpl_em(1m)
