Troubleshooting Indication Providers

This section describes the techniques for troubleshooting the EMS Wrapper Provider.

Problem

Indications corresponding to events generated by the Event Monitoring Service (EMS) monitors, are not logged in the Events List.

Cause 1

CIMOM is not running.

Solution

Enter the following command at the HP-UX prompt:

# ps -eaf | grep cimserver

If the name cimserver is displayed in the output, the CIMOM is running properly. If cimserver is not displayed in the output, stop the CIMOM by entering the following command at the HP-UX prompt:

# cimserver -s

To restart the CIMOM, enter the following command at the HP-UX prompt:

# cimserver

Cause 2

The provider module is not registered.

Solution

To check whether the provider module is registered, and to check its status, enter the following command at the HP-UX prompt:

# cimprovider -l -s

MODULE                                  STATUS
SFMProviderModule                       OK
HPUX_ControlProviderModule              OK
ErrorMetadataProviderModule             OK
EMArchiveConsumerModule                 OK
FMDModule                               OK

If the status displayed is not OK, the provider module is not registered properly. To register the provider module, enter the following command at the HP-UX prompt:

# cimmof -nroot/PG-InterOp /opt/sfm/schemas/mof/SFMProvidersR.mof

If no errors messages are displayed, the provider module is registered properly. If errors are displayed, restart the CIMOM by entering the following command at the HP-UX prompt:

# cimserver

After the CIMOM restarts, enter the following command at the HP-UX prompt to register the provider module:

# cimmof -nroot/PG-InterOp /opt/sfm/schemas/mof/SFMProvidersR.mof

After the provider module is registered, create a link between the SFM providers and the CIMOM by entering the following command at the HP-UX prompt:

# ln -s /opt/sfm/lib/libsfmproviders.1 /opt/wbem/providers/lib/libsfmproviders.sl

To check whether the link is created, enter the following command at the /opt/wbem/providers/lib directory:

# ls

Following is a sample output indicating that the link is created:

# lrwxr-xr-x 1 root sys 30 Jan 12 6:56 libsfmproviders.sl -> /opt/sfm/lib/libsfmproviders.1

If the link is already present, the following error message appears:

# ln: /opt/wbem/providers/lib/libsfmproviders.sl exists

Cause 3

The provider is not registered under the module.

Solution

To check whether the provider is registered under a module, enter the following command at the HP-UX prompt:

# cimprovider -l -m SFMProviderModule

The following sample output indicates that the provider is registered under the module:

CPUProvider
CPUStatusProvider
EMSWrapperProvider
EventIndicationConsumer
MemoryProvider
MemoryStatusProvider
StateChangeIndicationProvider
ChassisProvider
CoolingStatusProvider
PowerStatusProvider
ThermalProvider
VoltageProvider

Cause 4

Subscriptions do not exist.

Solution

Create the following enumerateInstances_sub.xml file and save it in any location:

<?xml version="1.0" encoding="utf-8"?>
<CIM CIMVERSION="2.0" DTDVERSION="2.0">
 <MESSAGE ID="25000" PROTOCOLVERSION="1.0">
   <SIMPLEREQ>
    <METHODCALL NAME="EnumerateInstances">
      <LOCALNAMESPACEPATH>
        <NAMESPACE NAME="root"/>
        <NAMESPACE NAME="PG_InterOp"/>
      </LOCALNAMESPACEPATH>
      <IPARAMVALUE NAME="ClassName">
      <CLASSNAME NAME="CIM_IndicationSubscription"/>
      </IPARAMVALUE>
    </IMETHODCALL>
   </SIMPLEREQ>
 </MESSAGE>
</CIM>

To enumerate instances, enter the following command at the HP-UX prompt:

# wbemexec <full path>/enumerateInstances_sub.xml

The full path is the absolute path of the enumerateInstances_sub.xml file.

The output of this command indicates the presence of subscriptions, as shown in the following sample output:

<INSTANCENAME CLASSNAME="CIM_IndicationFilter">
<KEYBINDING NAME="CreationClassName">
<KEYVALUE VALUETYPE="string">
CIM_IndicationFilter
</KEYVALUE>
</KEYBINDING>
<KEYBINDING NAME="Name">
<KEYVALUE VALUETYPE="string">
EventConsumerFilter
</KEYVALUE>
</KEYBINDING>
<KEYBINDING NAME="SystemCreationClassName">
<KEYVALUE VALUETYPE="string">
CIM_ComputerSystem
</KEYVALUE>
</KEYBINDING>
<KEYBINDING NAME="SystemName">
<KEYVALUE VALUETYPE="string">
hpdst348
</KEYVALUE>
</KEYBINDING>
</INSTANCENAME>
</VALUE.REFERENCE>
</KEYBINDING>
<KEYBINDING NAME="Handler">
<VALUE.REFERENCE>
<INSTANCENAME CLASSNAME="CIM_IndicationHandlerCIMXML">
<KEYBINDING NAME="CreationClassName">
<KEYVALUE VALUETYPE="string">
CIM_IndicationHandlerCIMXML
</KEYVALUE>
</KEYBINDING>
<KEYBINDING NAME="Name">
<KEYVALUE VALUETYPE="string">
EventConsumerHandler
</KEYVALUE>
</KEYBINDING>
<KEYBINDING NAME="SystemCreationClassName">
<KEYVALUE VALUETYPE="string">
CIM_ComputerSystem
</KEYVALUE>
</KEYBINDING>
<KEYBINDING NAME="SystemName">
<KEYVALUE VALUETYPE="string">
hpdst348
</KEYVALUE>
</KEYBINDING>
</INSTANCENAME>
</VALUE.REFERENCE>
</KEYBINDING>
</INSTANCENAME>

Cause 5

The indication providers are not loaded properly.

Solution

To check whether the EMS Wrapper Provider is loaded properly, complete the following steps: