WBEM Profiles Guide

HP Record Log Profile
20 Version 1.1.0
9.9 Actions based on HP_CommonLogEntry.Actionable
In modular systems, management application can provide an option for repairing an event or not based
on the Actionable property value.
9.10 HP_CommonLogEntry.ReportingEntity
In a modular system, System Firmware on a particular partition could log an event related to some
component in that partition. This property will reflect the details about the System Firmware, which is the
actual entity that logged this event.
9.11 Actions based on HP_CommonLogEntry.ImpactedDomain
In modular systems, there will be one SEL (System Event Log) log for the entire Complex. There can be
multiple partitions in a Complex. Each partition is a separate system. Events that do not belong to the
local partition will have this property reflect “Complex (2)” and the events that are local to the partition will
reflect “System (4)”. ImpactedDomain property value can be used by management application to decide
on the actions to be taken.
9.12 Clear the Log
For the given instance HP_CommonRecordLog execute ClearLog() method. The implementation may
log an event indicating the log was cleared by the provider.
If a ClearLog() method also saves a soft copy of the log, LogBackupDays may be used to represent the
time a previously saved soft copy is retained. The most recent soft copy is saved indefinitely.
9.13 Determine if new entries have been added
Subscribe to the LogRecordIndication for the log of interest. When an indication is received, new entries
have been added or modified. Repairing an event may also cause the event to be modified. A client can
subscribe to receive indications via the standard WBEM subscription mechanisms and can use any
properties that are part of the HP_CommonLogEntryIndication class in the filter portion of the Query to
specify the set of indications it will receive. For example, if the client only wants to receive indications
when the PerceivedSeverity is Major (5) or Critical (6) and the Query Language was WQL, they could set
the Query property to "SELECT * FROM HP_CommonLogEntryIndication WHERE PerceivedSeverity >
5".
The general sequence of events for the client, CIMOM and provider for subscribing to, generating,
receiving and processing an indication would be as follows:
Client creates a subscription, consisting of a filter and handler instances and subscription
association between them
Client registers subscription with the CIMOM
Provider determines an indication needs to be sent when records are added or modified
Provider creates Indication instance
Provider fills in appropriate properties
Provider retrieves properties from device instance or log entries
Provider retrieves system properties from appropriate system class or log entries
Provider sends indication to CIMOM