Comparison of EMS-Based and WBEM-Based Hardware Diagnostics Solution

This section provides a comparison of the terminologies, hardware monitoring, and features in the EMS-based and WBEM-based hardware diagnostics solutions.

This section includes the following topics:

Terminologies Used in EMS-Based and WBEM-Based Solution

This section compares the terminologies used in the EMS-based and WBEM-based hardware diagnostics solution.

Table 1-1 Comparison of Terminologies Used in EMS-based and WBEM-based solution

Description	EMS-Based Solution	WBEM-Based Solution
The underlying structure or framework	Event Monitoring Service (EMS) framework, which supports hardware monitoring	Web-Based Enterprise Management (WBEM) environment, which aids management of large scale systems
An alert about the failure of a monitored hardware device	EMS event	WBEM indication
Components that monitor system hardware	EMS monitor	WBEM indication provider
Tools that provide information about devices, such as model number and serial number	Information Tools	SMH property pages
Expression to receive an event	EMS monitoring request	WBEM subscription
Library support for custom development	EMS Developer’s Toolkit	HP WBEM Services SDK

Comparison of EMS-Based and WBEM-Based Hardware Monitoring

This section outlines the architecture of the EMS-based and WBEM-based hardware monitoring solutions. It briefly explains the hardware monitoring process and differences in both the architecture.

Figure 1-1 “Architecture of EMS-Based and WBEM-Based Hardware Monitoring Solution” shows a comparison between EMS-based and WBEM-based hardware monitoring.

Figure 1-1 Architecture of EMS-Based and WBEM-Based Hardware Monitoring Solution

The hardware monitoring process for the EMS-based hardware diagnostics solution works in the following way:

The EMS Hardware Monitors constantly monitors the health of the server hardware.
If the monitor detects an error or an abnormal behavior on the resource it monitors, the monitor generates an event and communicates it to the EMS framework.
The EMS framework reports the event to the EMS clients.
The system administrator (or the HP service provider) corrects the problem and returns the hardware to its normal operating condition.

The hardware monitoring process for WBEM-based hardware diagnostics solution works in the following way:

The WBEM indication providers constantly monitors the health of the server hardware.
If the WBEM indication providers detect an error or abnormal behavior on the resource it monitors, the WBEM indication providers generate WBEM indications and passes this information to the HP WBEM Services Framework.
The HP WBEM Services Framework reports the WBEM indication to the WBEM clients.
The system administrator (or the HP service provider) corrects the problem and returns the hardware to its normal operating condition.

Comparison of Features Provided by WBEM-Based Solution Over EMS-Based Solution

This section compares the features available on both EMS-based and WBEM-based hardware diagnostics solution.

Table 1-2 Comparison of Features Provided by WBEM-Based Solution Over EMS-Based Hardware Diagnostics Solution

Features	WBEM-Based Hardware Monitoring	EMS-Based Hardware Monitoring
Viewing Event	SFM provides EVWEB (accessed within HP SMH) that enables you to view WBEM indications. Events associated with a particular device can be viewed on the “Events” tab of the HP SMH property page for that device.	OnlineDiag logs the EMS events in the `Event Log` file.
Sorting and filtering events based on device type, date-time, and age	SFM enables you to administer WBEM indications using EVWEB (available within HP SMH). This feature is also available through the command line interface.	OnlineDiag does not provide this feature. You can only view events present in the Event Log file. The events cannot be sorted or filtered based on any criteria.
Creating event monitoring requests	SFM enables you to create event monitoring requests using EVWEB. This feature is also available through CLI.	OnlineDiag provides Hardware Monitoring Request Manager (monconfig) utility using which you can create and manage event monitoring requests for all EMS Hardware monitors.
Viewing health status of system hardware	SFM provides this feature through HP SMH.	OnlineDiag does not provide this feature.
	You can add a new indication provider to the existing provider module. The WBEM services enable you to register the provider modules using the cimprovider. You need not restart the cimserver after registering the provider module.	OnlineDiag provides the monitor dictionary file, `/etc/opt/resmon/dictionary/<monitor_name>.dict`. You must edit the monitor dictionary file and restart EMS to load the monitor.
Employing Industry standard protocols	SFM operates within the WBEM environment.	OnlineDiag uses EMS, an HP proprietary protocol.
Displaying information on standards-compliant graphical and command-line system management applications	SFM displays information on standards-compliant graphical and command-line system management applications, such as HP SIM and HP SMH.	OnlineDiag displays information within the STM GUI, CLI and menu-based user interfaces.

Comparison of EMS-Based and WBEM-Based Hardware Diagnostics Solution

Technical documentation

» Table of Contents

» Glossary

» Index

Terminologies Used in EMS-Based and WBEM-Based Solution

Comparison of EMS-Based and WBEM-Based Hardware Monitoring

Comparison of Features Provided by WBEM-Based Solution Over EMS-Based Solution