installation and reference guide HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 family of Disk Arrays 3.02.00 (AA-RW7SL-TE, March 2009)

Contents of the data
dump
DescriptionMessage
Event
ID
N/A
A call to a DSM's PathVerify routine to
a pseudo-LUN has failed. This event
occurs during final initialization after
PathVerify has checked whether the
device can be reached through a newly
found path.
A Path Verification request to a
device on pseudo-LUN that is
controlled by DSM_name has
failed. This may indicate a path
failure.
20
N/A
MPIO is unable to run through its main-
tained list of pseudo-LUNs.
The internal state of device_ob-
ject is inconsistent. This indic-
ates potential failures in this
support.
21
N/A
A failover attempt on a pseudo-LUN has
failed. This indicates that the DSM did
not return a valid path after the call to
InvalidatePath.
A fail-over on pseudo-LUN was
attempted, however the attempt
failed. The devices will be re-
moved.
22
N/A
There are no available paths to the
pseudo-LUN. The device has gone into
total failure and will be removed.
All paths have failed. Pseudo-
LUN will be removed.
23
N/A
A PnP request for QueryRemove was
rejected because the device is in the
paging, hiber, or crash dump path state.
A PnP Operation rejected, as
device is not in a state where
the request can be honored.
24
Path ID used for resubmis-
sion
An issued request from the pseudo-
LUN’s queue failed. This always occurs
when the device is in the process of be-
ing removed.
Requests that were queued to
pseudo-LUN have failed during
resubmission.
25
N/A
One of the following events occurred
during failover: MPIO’s call to the DSMs
InvalidatePath failed; DSM did not re-
turn a new path; DSM did not return a
path when MPIO called the LBGetPath
routine.
DSM_name failed to return a Path
to pseudo-LUN .
32
Bogus Path ID returned
by DSM; if the Path ID =
NULL, the DSM has
failed to return a path
MPIO is unable to find an operational
device-path pair representation (device
info) for the path that the DSM wants to
use for the I/O to the device.
DSM_name returned a bogus path
to device .
33
DSM ID
MPIO received a DSMNotification call,
but is unable to map the DSM ID to a
device.
DSM_name supplied an invalid ID
for an operation on notifica-
tion_type .
35
DSM ID
DSM called DSMSendRequest to have
MPIO send a request on its behalf, but
MPIO is unable to find the pseudo-LUN
requested.
An unknown DSM supplied an inval-
id ID for an operation on
pseudo-LUN .
36
The type of notification
called by DSM
DSM_name has called DSMNotification
on a pseudo-LUN.
DSM_name is attempting an opera-
tion on pseudo-LUN . The Type is
noted in the dump data.
37
Multipathing driver event log messages44