HP OneView for Microsoft System Center - Manual (Page 29)

Operational and usage issues
Alert notifications repeat the value displayed in Path, and the Path and Source values
appear to be swapped
In alert notifications for devices managed by HP:
•
The value for Source indicates the entity that generated the alert, such as the HP Insight
Management Agents.
•
The value for Path indicates the target server or device that is affected by the alert.
•
The actual value for Path is displayed twice, separated by a semicolon.
Sample alert notification:
Alert: HP Agentless Drive Array Controller degraded.
Source: ILOCN7134.usa.corp.net
Path: ENSCOM.EN.RM;ENSCOM.EN.RM
Last modified by: System
Last modified time: 2/23/2013 11:15:02 PM
Alert description: The drive array controller in 0 has a drive array partner
controller with serial number 0. This partner controller has a new status of 0.
(Partner Controller status values: 1=other, 2=ok, 3=generalFailure)
Researching state monitoring
HP servers that are not running Windows operating system software are monitored in the following
ways after you initially import this management pack:
•
Discovery and state monitoring
•
Event monitoring
The discovery and state monitoring displays the current state of the server. The event monitoring
displays historical alerts from the time that monitoring begins. After you initially configure server
monitoring, only discovery and state monitoring displays current issues. Resolve all current issues
on each server to use event monitoring.
The discovery and state monitoring provides the latest HP server inventory and state results to the
Operations console. This monitoring displays a near realtime state of the HP server, and provides
the state of each hardware subsystem (collection).
Event monitoring provides the best possible information for failed descriptions and failed
components. If event monitoring generates an alert on the Operations console, you must resolve
the issue immediately. Events are generated only once. If a state change was observed, look at
the Active Alerts view to find detailed information about the issue.
NOTE: For HP Agentless servers that use AMS, Network Monitors and Realtime Monitors are
supported only when AMS is running. If AMS is stopped and a Network interface event is generated,
the event is displayed, but SCOM might continue to show the status of server as healthy because
the server health is determined by the health monitors. In this case, resolve the event and verify
that AMS is running to ensure that the health status of the server is accurate.
Expected associated classes are not displaying in the Server State view or the Health
Collection view
By default, the Server State view and the Health Collection State view do not display the expected
associated class instances. The layout of the view can be different according to the installation
order of the management packs, the discovery results, and the user's console operation. To include
the associated classes and properties you want to see in each view, open the Personalize View
dialog box and select the associated class and properties to be included.
Operational and usage issues 29