 |
» |
|
|
 |
This section discusses the following topics: Error Management Technology (EMT)
EVWEB |  |
EVWEB is a component of SFM that enables you to administer and view WBEM indications generated on
the local system on which SFM is installed. For more information on
EVWEB, see “Evweb Overview”. EMT |  |
EMT is a component of SFM, which contains most errors that can
occur on the HP-UX 11i v3 system. You can view these error messages
using HP SMH on the local system. For more information on EMT, see “EMT Overview”. CIMUtil |  |
SFM introduces the CIMUtil command. Using CIMUtil, you can enumerate
instances related to various devices and create filters, handlers,
and subscriptions supported by SFM. For more information, view CIMUtil
manpage. See "man CIMUtil" IPMI Event Viewer |  |
Starting March 2009 release, the IPMI Event Viewer will be delivered
as part of SysFaultMgmt. In the earlier releases it was delivered
as part of Online Diagnostics bundle .IPMI Event Viewer is used to
display low-level system log information. Providers |  |
SFM providers are components of SFM that retrieve information
about the inventory on a system and the events that occur on the hardware
resources. SFM providers can be classified as instance providers or as indication providers. This section describes SFM providers. On request, an SFM instance provider dynamically queries the
local or remote system for the property information
described in Table 1-1 and reports
the information to the CIMOM. Table 1-1 Instance Providers | Instance Provider | Description |
|---|
| CPU | The CPU Instance Provider gathers the following types of information: Logical processor information, such as: Processor status information, including configuration
and deconfiguration, failure status, and active and inactive status
Physical processor chip information, such as chip
revisions and architecture revisions Location details, such as: Location attributes such as cabinet number, cell number,
slot number, and so on. Only information for filled slots is available.
The CPU Instance Provider depends on the EMS
Wrapper Provider to update the processor inventory. | | Memory | The Memory Instance Provider gathers the following types of
information: Memory module information, such as: Module status (for example, configuration status,
failure status)
The Memory Instance Provider depends on the EMS
Wrapper Provider to update the memory inventory. | | Environmental | The Environmental Instance Provider gathers information
about the following hardware components: | Filter Metadata (FMD) | The FMD Instance Provider does the following: Provides the ability to predefine a filter in a repository Ensures that chosen indications are logged to the
Event Archive Creates HP-advised subscriptions when SFM is installed
| | Firmware Revision | The Firmware Revision Provider retrieves the following types
of information: Management Processor (MP) firmware revision
| | DAS Provider | Starting with HP-UX 11i v3 March 2009 release, SFM does not monitor
information of storage disks or disk enclosures. However, inventory
details of direct attached storage disks and error monitoring is done
by DAS Provider For information, see HP-UX WBEM Direct
Attached Storage (DAS) Provider at the following location http://docs.hp.com/en/netsys.html#HP%20WBEM%20Providers | | Management Processor | Retrieves information about the management processor on the
system. | | Enclosure | The
Enclosure Instance Provider retrieves the following types of information: Onboard Administrator (OA) description
 |  |  |  |  | NOTE: The Enclosure Instance Provider is available on BL860c HP Server
Blade only. |  |  |  |  |
| | Temperature Sensor | The Temperature Sensor Provider retrieves the following types
of information: Describes properties such as sensor number, current
temperature reading, and temperature sensor status. Current temperature reading Temperature sensor status
| | Record Log | Enables
event analysis tools such as Web-Based Enterprise Services (WEBES)
to access details of indications generated by the SFMIndicationProvider
that are available in the SFM database, for event analysis. The provider
also supports MCA logs. Event analysis tools can access MCA log details
for event analysis.  |  |  |  |  | NOTE: There is no GUI for the Record Log Provider. You can only enumerate
instances using the CLI. |  |  |  |  |
| | ComputerSystem Chassis Provider | Retrieves
properties such as the serial number, product ID, and virtual Universally
Unique ID (UUID). It provides the following details related to the
physical system: The ComputerSystem Chassis Provider provides
the following details related to the logical server: These values are retained when an OS instance
is moved to another server. For a list of SFM indications
and their details, see the SFM Event Descriptions at: http://docs.hp.com/en/diag/sfm/sfm_summ.htm |
SFM includes three indication
providers, the EMS Wrapper Provider, SFMIndicationProvider, and the
Event Manager Common Information Model (EVM CIM) Provider. Table 1-2 describes the SFM indication
providers. Table 1-2 Indication Providers | Indication Provider | Description |
|---|
| EMS Wrapper Provider | The EMS Wrapper Provider does the following: Converts hardware events generated by the EMS Hardware
Monitors into WBEM indications. Reports the WBEM indications to the CIMOM. Using a
WBEM-based management application, such as HP SIM,
you can subscribe to and receive Event Monitoring Service (EMS) events
generated on a remote system. On the system on which SFM is installed,
you can use an SFM tool, called EVWEB, to view and administer events
through the HP SMH interface.
The following EMS Hardware Monitors are supported
on HP 9000 servers running the HP-UX 11i v3 operating system: Chassis Code (dm_chassis) Integrity Core Hardware Monitor(ia64_corehw) IPMI Forward Progress Log Monitor (fpl_em)
The following EMS Hardware Monitors are supported
on HP Integrity® servers running the HP-UX 11i v3 operating system: Corrected Platform Error Monitor (cpe_em) IPMI Forward Progress Log Monitor (fpl_em) Itanium Core Hardware Monitor(ia64_corehw) SCSI Disk Monitor (disk_em) Itanium Memory Monitor (memory_ia64)
For a list of WBEM indications and their details,
see the EMS Event Descriptions at: | EVM CIM Provider | The EVM CIM Provider
does the following: Converts hardware, software, and kernel events generated
by the EVM into WBEM indications. Reports the WBEM indications to the CIMOM. Using a
WBEM-based management application, such as HP SIM,
you can subscribe to and receive EVM events generated on a remote
system. On the system on which SFM is installed, you can use an SFM
tool, called EVWEB, to view and administer events through the HP SMH
interface.
| SFMIndicationProvider | The SFMIndicationProvider generates indications that
are compliant with the WBEM standards. On HP Integrity systems, it
replaces the following EMS monitors: On HP 9000 systems, it replaces the following
EMS monitors: You can choose to use either the SFMIndicationProvider
or the EMS monitors that it replaces, to monitor your hardware. The
remaining EMS monitors continue to function as usual irrespective
of whether you choose the SFMIndicationProvider or the EMS monitors
that it replaces. If you choose the SFMIndicationProvider, it does
the following: Generates WBEM indications equivalent to the events
that the monitors it replaces generate. Reports these WBEM indications to the CIMOM.
In the WBEM indication details, the provider name
displayed corresponds with the device to which the indication is related.
For example, if the name of the provider displayed in the event details
is MemoryIndicationProviderIA, the
event is related to memory. For a complete list of the names of providers
displayed in the WBEM indication details, in the SFM mode, see Table 4-2. The provider names
indicate the device to which the event is related. For
a list of WBEM indications and their details, see the EMS Event Descriptions
at: | MCA Indication Provider | The MCA Indication Provider generates an indication
when Machine Check Abort (MCA) logs are present due to an MCA. |
CIMOM identifies the SFM providers using SFMProviderModule. If a provider is not working properly, SFMProviderModule
stops all the SFM providers. Starting with the HP-UX 11i v3 February
2007 release, SFM includes the cron job. Every 15 minutes, the cron job
checks if SFMProviderModule is running. If SFMProviderModule is not
running, the cron job starts SFMProviderModule which in turn starts
all the providers.
|