Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
 System Fault Management Administrator’s Guide: HP-UX 11i v2 > Chapter 6 Troubleshooting SFM

Troubleshooting Indication Providers
» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

spacerspacerspacer
spacer
spacer
  		 
 

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

NOTE: The SFMIndicationProvider is available on Itanium-based systems only. The SFMIndicationProvider generates WBEM indications only if you choose to use it. Otherwise, the EMS monitors generate EMS events. These events are converted into WBEM indications by 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
HP_UtilizationProviderModule            OK
HPVMProviderModule                      OK
EvwebIndicationProviderModule           OK
SFMProviderModule                       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:

On Itanium-based systems, enter:

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

On PA-RISC-based systems, enter:

# 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:

On Itanium-based systems:

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

On PA-RISC-based systems:

# 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 on Itanium-based systems indicates that the provider is registered under the module:

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

The following sample output on PA-RISC-based systems 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

Complete the following steps:

  1. Enter the following command at the HP-UX prompt to check if subscriptions exist:

    # Evweb subscribe -L -b external

    If subscriptions exist, contact your local HP support personnel. Otherwise, proceed to step 2

  2. If no subscriptions are displayed in the output, enter the following command at the HP-UX prompt to create subscriptions:

    # Evweb subscribe -C -n <subscription name> -e <severity> -v <device> -t <destination> -g <throttling configuration name>

  3. Enter the following command to check if the subscription is created:

    # Evweb subscribe -L -b internal

    If subscriptions are displayed in the output, subscriptions are successfully created. Indications start logging in the Events List when an event is generated. However, if indications do not start logging in the Events List, contact your local HP support personnel.

Cause 5

The indication providers are not loaded properly.

Solution

Determine the current monitoring mode by entering the following command at the HP-UX prompt:

# /opt/sfm/bin/sfmconfig -w -q

If the EMS Hardware Monitors are enabled, the following output displayed:

EMS hardware monitors are enabled & SysFaultMgmt is not monitoring any device.

If the SFMIndicationProvider is enabled, the following output is displayed:

EMS hardware monitors are disabled & SysFaultMgmt is monitoring devices.

  1. If the EMS Hardware Monitors are enabled, complete the following steps to check whether the EMS Wrapper Provider is loaded properly:

    1. Open the /var/opt/sfm/conf/FMLoggerConfig.xml file.

    2. Using an editor, change the severity of logs from WARNING to INFORMATIONAL.

    3. Enter the /opt/sfm/bin/sfmconfig command with the /var/opt/sfm/conf/FMLoggerConfig.xml option:

      # /opt/sfm/bin/sfmconfig -c /var/opt/sfm/conf/FMLoggerConfig.xml

    4. Enter the following command to generate a sample indication:

      # /etc/opt/resmon/lbin/send_test_event <monitor_name>

      For example:

      # /etc/opt/resmon/lbin/send_test_event disk_em

      Events generated by the disk_em monitor are translated into indications and reported to the CMS. You can view these indications in the Events List.

      NOTE: You can create sample indications using only those monitors that are supported on your system. For the list of monitors supported on your system, see the EMS Wrapper Provider Data Sheet posted at: http://docs.hp.com/en/diag

    5. Open the /var/opt/sfm/log/sfm.log file.

      NOTE: The /var/opt/sfm/log/sfm.log file is the file specified in the Target field of the FMLoggerConfig.xml file.

      Following is an example of how the sfm.log file is displayed when you change the logging level to INFORMATIONAL, indicating that the provider is loaded properly:

      04/19/04 03:36:32 EMSWrapper INFORMATIONAL 9596 Using port 49173
04/19/04 03:36:32 EMSWrapper INFORMATIONAL 9596 Provider Enabled
04/19/04 03:38:03 EMSWrapper INFORMATIONAL 9599 Registration for /storage/events/disks/default/0_0_0_2_0.6.0 Accepted. RequestID : 63700993
04/19/04 03:38:03 EMSWrapper INFORMATIONAL 9599 Registration for /system/events/chassis/chassis_log Accepted. RequestID : 64552961
04/19/04 03:38:03 EMSWrapper INFORMATIONAL 9599 Registration for
/system/events/core_hw/core_hw Accepted.
RequestID : 65404929

      Use the information available in the file to analyze the problem.

    6. When you complete testing, revert to the default severity settings in the FMLoggerConfig.xmlfile using a text editor. If you do not revert to the default settings, the logs consume more disk space.

  2. If the SFMIndicationProvider is enabled, complete the following steps to check whether the SFMIndicationProvider is loaded properly:

    1. Open the /var/opt/sfm/conf/FMLoggerConfig.xml file.

    2. Using an editor, change the severity of logs from WARNING to INFORMATIONAL.

    3. Enter the /opt/sfm/bin/sfmconfig command with the /var/opt/sfm/conf/FMLoggerConfig.xml option:

      # /opt/sfm/bin/sfmconfig -c /var/opt/sfm/conf/FMLoggerConfig.xml

    4. Enter the following command to generate a sample indication:

      # /opt/sfm/bin/sfmconfig -t -p

      Indications related to the processor are generated and reported to the CMS. You can view these indications in the Events List.

    5. Open the /var/opt/sfm/log/sfm.log file.

      NOTE: The /var/opt/sfm/log/sfm.log file is the file specified in the Target field of the FMLoggerConfig.xml file.

      Following is an example of how the sfm.log file is displayed when you change the logging level to INFORMATIONAL, indicating that the provider is loaded properly:

      04/19/04 03:36:32 EMSWrapper INFORMATIONAL 9596 Using port 49173
04/19/04 03:36:32 EMSWrapper INFORMATIONAL 9596 Provider Enabled
04/19/04 03:38:03 EMSWrapper INFORMATIONAL 9599 Registration for /storage/events/disks/default/0_0_0_2_0.6.0 Accepted. RequestID : 63700993
04/19/04 03:38:03 EMSWrapper INFORMATIONAL 9599 Registration for /system/events/chassis/chassis_log Accepted. RequestID : 64552961
04/19/04 03:38:03 EMSWrapper INFORMATIONAL 9599 Registration for
/system/events/core_hw/core_hw Accepted.
RequestID : 65404929

      Use the information available in the file to analyze the problem.

    6. When you complete testing, revert to the default severity settings in the FMLoggerConfig.xmlfile using a text editor. If you do not revert to the default settings, the logs consume more disk space.



Troubleshooting Instance Providers
  		 


Troubleshooting Evweb  
Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2008 Hewlett-Packard Development Company, L.P.