Subscribe to Indications
ESXi 7.0 supports the following types of indications.
Indication | Description |
---|---|
OMC_IpmiAlertIndication
|
Sent whenever entries are added to the IPMI System Event Log, and whenever a sensor’s HealthState property becomes less healthy than previously seen. |
OMC_BatteryIpmiAlertIndication
|
Specializes OMC_IpmiAlertIndication. |
OMC_BIOSIpmiAlertIndication
|
Specializes OMC_IpmiAlertIndication. |
OMC_ChassisIpmiAlertIndication
|
Specializes OMC_IpmiAlertIndication. |
OMC_CoolingUnitIpmiAlertIndication
|
Specializes OMC_IpmiAlertIndication. |
OMC_DiskIpmiAlertIndication
|
Specializes OMC_IpmiAlertIndication. |
OMC_MemoryIpmiAlertIndication
|
Specializes OMC_IpmiAlertIndication. |
OMC_PowerIpmiAlertIndication
|
Specializes OMC_IpmiAlertIndication. |
OMC_ProcessorIpmiAlertIndication
|
Specializes OMC_IpmiAlertIndication. |
VMware_KernelIPChangedIndication
|
This indication is sent whenever the ESXi kernel IP address for the host has changed. |
To receive CIM indications, you must have a running process that accepts indication messages and logs them or otherwise acts on them, depending on your application. You can use a commercial CIM indication consumer to do this. If you choose to implement your own indication consumer, see the following documents:
- DMTF's CIM Event Model White Paper at http://www.dmtf.org/standards/documents/CIM/DSP0107.pdf
- DMTF's Indications Profile specification at http://www.dmtf.org/standards/published_documents/DSP1054.pdf
- CIM indication specifications from your server supplier that are specific to the server model
The indication consumer must operate with a known URL. This URL is used when instantiating the IndicationHandler object.
Similarly, you must know which indication class to monitor. This information is used when instantiating the IndicationFilter object.
This example shows how to instantiate the objects needed to register for indications.
This pseudocode depends on the pseudocode in Make a Connection to the CIMOM.
To subscribe to indications