Administrator's and User's Guide for SFM HP-UX 11i v3 March 2012

Figure 1 Block Diagram of SFM
The following list describes the sequence of events when a request is made for information:
1. The CIMOM receives requests from the CMS for information about devices.
2. The CIMOM 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.
You can view the information 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. EVWEB and CMS subscriptions are created.
2. The EMS Wrapper provider receives events generated by the EMS monitors through the EMS
framework.
3. The provider converts these events into WBEM indications and reports these indications to the
CIMOM.
4. CIMOM directs these indications to the CMS that has created subscriptions for indications.
EVWEB retrieves the errors that occurred on the local system and stores the indications either
in the Event Archive or in your E-mail box, or both, depending on your configuration.
You can view indications 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. EVWEB and CMS subscriptions are created.
2. The SFMIndicationProvider generates WBEM indications that are triggered by errors on devices
that it monitors.
3. The provider reports these WBEM indications to the CIMOM.
16 Introduction