HP-UX WBEM System Fault Management (SFM) Release Notes (September 2013)

In the case of a multi LAN environment configuration, do not restart any of the following:
◦ SFMProviderModule
◦ cimserver
◦ Server
• Problem: The events and user defined subscriptions (created using Evweb) are lost when
diagnostic products are upgraded on a DRD cloned disk.
Description: Prior to September 2012 release version of the diagnostics product, the postgres
7.4.2 version was supported. However version 8.4.8 is shipped from September 2012 release.
Due to the missing data compatibility between PostgreSQL version 7.4.2 (prior to September
2012) and 8.4.8 (September 2012 release or later), when the diagnostics products are
upgraded from prior to September 2012 release to September 2012 web release and later,
the postgres data needs to be migrated to 8.4.8 format. Data migration involves backup in
7.4.2 version using the pg_dumpall and restore in 8.4.8 version using the psql operations.
Both of these operations requires a running postgres service. But in the DRD environment there
is a limitation that no service can be run on the cloned disk when products are either installed
or upgraded. This limits diagnostics product upgrade steps from taking the backup of the
postgres 7.4.2 data. As a result, the data such as events, error records, and subscriptions
(created using Evweb) is lost during such circumstances.
Workaround: You can select any of the following two alternatives:
1. To install the product on the DRD cloned disk as a normal upgrade scenario. The scenario
will be same as fresh installation and user may refer to event.log for historical event data.
Also, the user has to recreate the user defined subscriptions (created using Evweb) at the
end of the installation.
2. To have a seamless migration of the data from postgres 7.4.2 version. In this case, the
user is required to perform the manual steps listed in the Installation scenarios of Postgres
8.4.8 guide at www.hp.com/go/hpux-diagnostics-sfm-docs.
• Problem: The slview does not provide details of IPMI events on Itanium 9500 based servers.
Description: The slview provides the ability to parse IPMI events logged in /var/stm/logs/
os/ file to get details of individual events. On the rx2800 i4, HP Integrity BL860c
i4, BL870c i4, and BL890c i4, the IPMI event details cannot be parsed by slview with
default parameters through command line or GUI interface provided through HP SMH.
Workaround: To view the IPMI events, follow the steps given below:
1. Specify the "-p" option with "0".
For example,
Example 1 slview -d -f /var/stm/logs/os/fpl.log.xx -p 0
2. On HP SMH, navigate to the Tools>>IPMI Event Viewer >> Event Viewer screen, and
select “0” for the “Platform:” fields instead of the default value.
NOTE: The properties such as Description, Cause, Action, Alert Level, and
Logged by fields of the output of slview using the “-p” option can be different from the
actual values for the rx2800 i4, HP Integrity BL860c i4, BL870c i4, and
BL890c i4. It is recommended to refer to the events generated by SysFaultMgmt using
the evweb eventviewer command or the event.log file for details of these events.
Limitations and workaround 17