System Fault Management C.07.10.08.
Contents System Fault Management C.07.10.08.01 Release Notes HP-UX 11i v3 March 2013 Release...............3 Introduction.........................................................................................................................3 SFM providers.....................................................................................................................4 EVWEB..............................................................................................................................
System Fault Management C.07.10.08.01 Release Notes HP-UX 11i v3 March 2013 Release Introduction SFM includes the following tools: • SFM providers • EVWEB • EMT NOTE: HP-UX need not be rebooted upon upgrade/install of this version.
SFM providers SFM providers are tools that gather information related to various hardware devices and report to the Common Interface Model Object Manager (CIMOM). Table 1 lists the SFM providers, and their respective functions Providers Functions BladeProvider and BladeStatusProvider Available on Blade servers, providing Blade inventory details and health status of blades current partition. EMDProvider Helps to query CER (Common Error Repository) for error metadata used only in SysFaultMgmt.
Table 1 lists the SFM providers, and their respective functions (continued) Providers Functions Field Replaceable Unit (FRU) instance provider Retrieves properties such as the serial number, part number, version, manufacturer and FRU name. ChassisProvider Provides information about fans, power supply, and AC input lines.
SFM is the default monitoring mode. However, you can switch to the OnlineDiag monitoring mode. For information on how to switch to the OnlineDiag mode, see the SFM Administrator's Guide at http://www.hp.com/go/hpux-diagnostics-docs The diagnostic mode will be set to SFM mode by default on updating SFM. This overrides any previous mode setting done manually on the system and needs to be restored. Verify the current diagnostic mode before and after the update/installation of the WBEM Management Bundle.
• QXCR1001228287 Problem: After upgrade of March 2009 OE version of SFM on a IA server to WBEMMgmtBundle C.01.01 version, the monitors are running, but in the /etc/opt/resmon/ peresistce file, the intermediate p.1* and p.2.* files for monitors restart still exist. Resolution: This problem is fixed. The p.* files are removed in post install scripts.
Features EVWEB offers the following features: • Provides both quick search and advanced search mechanisms to view events from the Event archive. • Provides both simple and advanced search mechanism to search for low level logs from the log viewer. • Generates a list of events in a printer-friendly format (GUI only). • Enables users with administrative privileges to create, modify, and delete indications.
Limitations • When an HP-advised subscription is copied to create or modify another subscription, the subscription criteria is not copied. However, only destinations are copied to the new subscription. • Event details displayed in EVWEB event viewer and embedded in the EVWEB email notification may not have similar readability or formatting as provided by the EMS event notification. However, this issue is not applicable to HP_DeviceIndication class indications.
Following is a limitation of EMT: • When you make a generic query to the CER, a huge amount of data is retrieved from the CER. However, this behavior may affect the performance of EMT.
◦ rx5670-4 ◦ rx6600 ◦ rx7620 ◦ rx7640 ◦ rx8620 ◦ rx8640 ◦ rx2800 i2 ◦ SD16A, SD32A, SD64A ◦ SD16B, SD32B, SD64B ◦ BL60p HP Server Blade ◦ BL860c HP Server Blade ◦ BL870c HP Server Blade ◦ BL860c i2, BL870c i2 & BL890c i2 ◦ Superdome 2 ◦ BL860c i4, BL870c i4, BL890c i4 ◦ rx2800 i4 SFM supports the following systems based on the Dual-Core Intel® Itanium® Processor 9100 series and running the HP-UX 11i v3 operating system: • rx7640 • rx8640 • SD16B • SD32B • SD64B Foll
• SysMgmtPlus version A.04.00, September 2010 release or later • OnlineDiag Version B.11.31.06.xx on HP 9000 systems only, September 2009 release or later EMS version A.04.20.31 STM version D.06.00 NOTE: • The listed versions of the software are the minimum supported requirements. Subsequent versions are compatible with this version of SFM unless otherwise noted.
Limitations and workarounds • Problem: The Field Replaceable Units (FRU's) that are erroneous and marked for deconfiguration, the health status on HP SMH will not be in synchronization with the health state on the Onboard Administrator (OA) homepage. Description: On HP Superdome 2, the FRU's on which errors are found, and Superdome 2 Analysis Engine has marked them for deconfiguration on the next reboot, the bad health status will not be reflected on the HP SMH page.
• 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.
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.
Following are the commands you must use to obtain the bundle, product, sub-product, and the fileset information about the SysFaultMgmt depot. The generated output are examples from HP 9000 systems: • Bundle $ swlist -s # SysFaultMgmt C.07.10.08.01 SysFaultMgmt.SFM-CORE C.07.10.08 SysFaultMgmt.SFMDB C.07.10.
Reporting defects You can report defects related to SFM by filing a request on QUIX. The name of the project is SysFaultMgmt. If you do not have access to QUIX, contact your local HP representative to file a defect on your behalf. Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com).
