User guide

5 Troubleshooting
The following information is designed to help resolve some common operating issues that might
occur when using HP ProLiant PRO Management Pack. The troubleshooting issues are organized
into the following categories:
• “Configuration issues” (page 17)
• “Virtual Machine Manager 2008 issues” (page 18)
• “Operations Manager issues” (page 19)
Configuration issues
Monitoring hardware events
The HP ProLiant PRO Management Pack only monitors hardware events reported in HP ProLiant
servers. External HP storage devices and BladeSystem enclosures are not monitored by this
management pack. To monitor BladeSystem enclosures separately, download the HP BladeSystem
Management Pack.
Supported hosts
The HP ProLiant PRO Management Pack does not support Virtual Server 2005 and VMware hosts.
Alert notifications repeat value displayed in Path, and Path and Source values appear
to be swapped
In alert notifications for devices managed by HP:
• The Source value indicates the entity that generated the alert, such as the HP Insight
Management Agents.
• The Path value indicates the target server or device that is affected by the alert.
• The Path actual value is displayed twice, separated by a semicolon.
Sample alert notification:
Alert: HP Smart Array SAS/SATA Event Notification Service failed.
Source: HP Insight Management Agents
Path: bcalfe1b2cnet.mylab.net;bcalfe1b2cnet.mylab.net
Last modified by: System
Last modified time: 3/16/2011 5:01:02 PM
Alert description: The HP Insight Management Agents have failed;
the HP Smart Array SAS/SATA Event Notification service is not running.
Discovery problem
The HP ProLiant PRO Management Pack relies on multiple system infrastructures such as the
Operations Manager server, Operations Manager health service, Virtual Machine Manager 2008
server, Virtual Machine Manager 2008 agents, and Virtual Machine Manager PRO Management
Packs. If the configuration of any system is incorrect, the discovery process of the HP ProLiant PRO
Management Pack might fail.
The discovery process might be slow if you change a setting on any system. If you are in a
non-production environment and need to speed up the discovery process, use the following example
operation to test:
1. On the management console, locate the "Health Service" class instance to the managed host,
and then execute "Flush Health Service State and Cache."
This restarts the discovery process of all management packs on the managed host.
Configuration issues 17