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 v1 > Chapter 1 Introduction

Architecture

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

Figure 1-1 “Block Diagram of SFM on PA-RISC-Systems” illustrates the architecture of SFM installed on a PA-RISC-based client system. The client system is managed by the CMS.

Figure 1-1 Block Diagram of SFM on PA-RISC-Systems

Block Diagram of SFM on PA-RISC-Systems

The following list describes the sequence of events when a request is made for information:

  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 following list describes the sequence of events when an event is generated from an EMS monitor:

  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.

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