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

• Problem:CIM_AlertIndication.NetworkAddresses does not contain all assigned IP addresses.
Description: Indication delivered by SysFaultMgmt (System Fault Management) (SFM) does
not display all the IP addresses in NetworkAddresses property of CIM_AlertIndication class
when a new IP address is configured or an old IP address is changed at runtime.
Workaround: To reflect newly configured IP Addresses in SysFaultMgmt (System Fault
Management) (SFM) Indication, disable and enable SFMProviderModule using the following
commands
cimprovider -dm SFMProviderModule
cimprovider -em SFMProviderModule
• Problem: The firmware version of Management Processor firmware (MFW), given by MPProvider
and FirmwareRevisionProvider on HP Integrity rx2800 i2 server may be incorrect.
Description: The revision number (third field in':' separated version string) may be incorrect.
Workaround: Run the sysrev command from MP to get the correct MFW version
• Problem: The WBEM events do not get delivered to evweb.
Description: In an exceptional scenario, due to extreme stress condition, the database
component can get into a deadlock. In such cases, no events can be stored to database and
hence evweb cannot show any WBEM indication.
Workaround: Manually kill SFMProviderModule process and restart SFMProviderModule using
the following command:
cimprovider -em SFMProviderModule
• Problem: After OE install, SysFaultMgmt (System Fault Management) (SFM) generates harmless
warning messages in the install log file.
Description: The following messages are generated:
PGS04838: Warning: Class HP_CommonRecordLog already exists in the repository
PGS04838: Warning: Class HP_CommonLogRecord already exists in the repository
This message is written to the log when a module is registered to the class ahead of
SysFaultMgmt (System Fault Management) (SFM). This is a warning message which indicates
that the class is already registered.
cron may not be running - call your system administrator
warning: commands will be executed using /usr/bin/sh
The message cron may not be running is logged if the cron daemon does not run during
the install. The warning commands will be executed using /usr/bin/sh occurs if
the default login shell is not defined POSIX shell /usr/bin/sh. This is a warning from cron
that the POSIX shell is used to execute commands in the crontab file. If the login shell is set to
/usr/bin/sh in the /etc/passwd file, this error is not logged.
Workaround: You can safely ignore both these warning messages.
• Problem: The second lan interface configured on a server is not accessible for web browsing.
Description: When a second lan interface was configured on a server using a private subnet
used only for cluster heartbeat traffic, the “Launch SMH” button got the second lan interface’s
address but was not accessible for web browsing.
Workaround: Disable the second lan, restart SFMProviderModule, and configure the second
lan card. After configuring, do not restart the server, cimserver, and SFMProvider module.
16 SysFaultMgmt (System Fault Management) (SFM) release notes for September 2013 release