SFM Release Notes for HP-UX 11i v3 September 2012

Workaround: Follow the steps given below before upgrading SFM to C.07.01.06.01 version.
◦ Disable SFMProviderModule using the following command:
# cimprovider -dm SFMProviderModule
• Problem: IPMI FRU calls fail when a blade with Monarch Management Processor is inserted
into a different slot.
Description: On HP Integrity BL860c i2, BL870c i2 & BL890c i2 Server Blades system, when
blades are moved across different slots in an enclosure, the inventory shown by enumerating
HP_Blade or the blade property page on HP SMH does not reflect the correct set of blades
on the system.
Workaround: This problem has the following two workarounds:
1. Use the Onboard Administrator to determine the total number of blades on the system.
2. Disable SFMProviderModule using the cimprovider -dm SFMProviderModule
command. Run mv /var/opt/sfm/data/sdrcache /tmp/sdrcache command to move
the sdrcache file and enable SFMProviderModule cimprovider -em
SFMProviderModule
• Problem: CIM_AlertIndication.NetworkAddresses does not contain all assigned IP addresses.
Description: Indication delivered by 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 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, 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 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
System Fault Management C.07.08.09.01 release notes HP-UX 11i v3 September 2012 release 11