Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
System Fault Management Administrator’s Guide: HP-UX 11i v2 > Chapter 1 Introduction

Architecture on PA-RISC and Itanium-based Systems

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

Figure 1-1 illustrates the architecture of SFM installed on a client system.

Figure 1-1 Block Diagram of SFM

Block Diagram of SFM

The sequence of events when a request is made for information of a managed resource is as follows:

  1. The CIMOM receives requests from the CMS for device information.

  2. The CIMOM converts the requests to a format that is deciphered by the SFM providers and directs the requests to the appropriate SFM provider, for example, the CPU Instance Provider.

  3. The SFM provider queries the associated hardware device for property information.

  4. The SFM provider returns the query information to the CIMOM.

  5. The CIMOM conveys the responses from the provider to the CMS.

    Information can be viewed using HP SIM on the remote system and HP SMH on the local system.

The sequence of events when an event is generated from an EMS monitor is as follows:

  1. The EMS Wrapper Provider receives events generated by the EMS monitors through the EMS framework.

  2. The provider converts these events into WBEM indications and reports these indications to the CIMOM.

  3. The CIMOM directs these indications to Evweb and to the CMS that has created subscriptions for indications. Evweb then stores the indications either in the Event Archive or in your E-mail box, or both, depending on your configuration.

    Indications can be viewed using HP SIM on the remote system and HP SMH on the local system.

The sequence of events if you choose to use the SFMIndicationProvider instead of the EMS monitors it substitutes, is as follows:

  1. The SFMIndicationProvider generates WBEM indications that are triggered by errors on devices that it monitors.

  2. The provider reports these WBEM indications to the CIMOM.

  3. The CIMOM directs these indications to Evweb and to the CMS that has created subscriptions for indications. Evweb then stores the indications either in the Event Archive or in your E-mail box, or both, depending on your configuration.

    Indications can be viewed using HP SIM on the remote system and HP SMH on the local system.

  4. The indications generated by the SFMIndicationProvider, and reported to the CIMOM, can also be directed to the EMS framework through the WBEM Wrapper Monitor. The WBEM Wrapper Monitor converts the WBEM indications into EMS events and directs them to the EMS framework.

    EMS clients can receive these events, along with the other events generated by the EMS monitors, through the EMS framework.

    NOTE:
    1. Only those indications that are generated by the SFMIndicationProvider can be directed to the EMS framework through the WBEM Wrapper Monitor. Indications generated by the EMS Wrapper Provider cannot be directed to the EMS framework.

    2. You can continue to receive all events from EMS Hardware Monitors through the EMS framework along with the indications on Evweb and CMS.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2008 Hewlett-Packard Development Company, L.P.