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

Table 23 Troubleshooting instance providers (continued)
Problem: Indications fulfilling the conditions defined in the HP-Known HP-Defined filters, are not logged in the Event
Archive.
SolutionCause
<NAMESPACE NAME="root"/>
<NAMESPACE NAME="cimv2"/>
</LOCALNAMESPACEPATH>
<IPARAMVALUE NAME="ClassName">
<CLASSNAME NAME="HP_KnownFilter"/>
</IPARAMVALUE>
</IMETHODCALL>
</SIMPLEREQ>
</MESSAGE>
</CIM>
To execute the file, enter the following command at the HP-UX prompt:
# wbemexec <full path>/EnumerateInstances.xml
The full path is the absolute path of the EnumerateInstances.xml file.
This recreates HP-Known filters and HP-Known subscriptions in the CIMOM
repository, and the indications start logging in the Event Archive.
Troubleshooting indication providers
This section describes the techniques for troubleshooting the EMS Wrapper provider and the Event
Manager Common Information Model (EVM CIM) provider.
Table 24 Troubleshooting indication providers
Problem: Only two IPMI events are logged in the evweb eventviewer when sfmconfig -t -a command is used
to log test events.
SolutionCause
To view test events to backbone, memory and processor,
reduce the usage of /var filesystem to less than 90% and
seed test events using sfmconfig -t -a command.
This occurs when there is an excessive usage of more than
90% of /var filesystem and oserrlogd stops writing into
osel files in the directory /var/opt/psb/oselogs.
Table 25 Troubleshooting indication providers
Problem: Indications corresponding to events generated by the Event Monitoring Service (EMS) monitors, are not logged
in the Events List.
SolutionCauses
Enter the following command at the HP-UX prompt:Cause 1
# ps -eaf | grep cimserverCIMOM is not running.
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
To check whether the provider module is registered, and to check its status, enter
the following command at the HP-UX prompt:
Cause 2
The provider module is not
registered. # cimprovider -l -s
MODULE STATUS
OperatingSystemModule OK
ComputerSystemModule OK
ProcessModule OK
IPProviderModule OK
SFMProviderModule Degraded
86 Troubleshooting SFM