Administrator's and User's Guide for SFM HP-UX 11i v3 April 2010

Table 6-5 Troubleshooting Instance Providers
Problem: Indications fulfilling the conditions defined in the HP-Known HP-Defined filters, are not logged in the Event
Archive.
SolutionCause
Create the following EnumerateInstances.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>
<IMETHODCALL NAME="EnumerateInstances">
<LOCALNAMESPACEPATH>
<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.
The HP-Known filters and HP-Known
subscriptions have been deleted from
the CIMOM.
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 6-6 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 IPMI test events in evweb eventviewer, reduce
the usage of /var filesystem to less than 80% and seed
test events using sfmconfig -t -a command.
This occurs when there is an excessive usage of more than
80% of /var filesystem and OserrlogD stops writing into
osel files.
90 Troubleshooting SFM