
Event ID
Message
Description
Contents of the
data dump
20
A Path Verification
request to a device
on
pseudo-LUN
that is
controlled by
DSM_name
has
failed.
This may indicate
a path failure.
A call to a DSM’s PathVerify
routine to a pseudo-LUN has
failed. This event occurs during
fi
nal initialization after PathVerify
has checked whether the device
can be reached through a newly
found path.
N/A
21
The internal state
of
device_object
is
inconsistent.
This
indicates potential
failures in this support.
MPIO is unable to run through its
maintained list of pseudo-LUNs.
N/A
22
A fail-over on
pseudo-LUN
was attempted, however
the attempt failed.
The
devices will be removed.
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.
N/A
23
All paths have failed.
Pseudo-LUN
will be
removed.
There are no available paths to
the pseudo-LUN. The device has
gone into total failure and will be
removed.
N/A
24
A PnP Operation rejected,
as
device
is not in a
state where the request
can be honored.
A PnP request for QueryRemove
was rejected because the device
is in the paging, hiber, or crash
dump path state.
N/A
25
Requests that were queued
to
pseudo-LUN
have failed
during resubmission.
An issued request from the
pseudo-LUN’s queue failed. This
always occurs when the device is
in the process of being removed.
Path ID used for
resubmission
32
DSM_name
failed to return
a Path to
pseudo-LUN
.
One of the following events
occurred during failover: MPIO’s
call to the DSMs InvalidatePath
failed; DSM did not return a new
path; DSM did not return a path
when MPIO called the LBGetPath
routine.
N/A
33
DSM_name
returned a bogus
path to
device
.
MPIO is unable to
fi
nd an
operational device-path pair
representation (device info) for the
path that the DSM wants to use
for the I/O to the device
Bogus Path ID
returned by DSM; if
the Path ID = NULL,
the DSM has failed
to return a path.
35
DSM_name
supplied an in-
valid ID for an operation
on
notification_type
.
MPIO received a DSMNoti
fi
cation
call, but is unable to map the
DSMID to a device.
DSM ID
36
An unknown DSM supplied
an invalid ID for an
operation on
pseudo-LUN
.
DSM called DSMSendRequest to
have MPIO send a request on its
behalf, but MPIO is unable to
fi
nd
the pseudo-LUN requested.
DSM ID
38
Multipathing driver event log messages
Содержание MPIO
Страница 10: ...10 About this guide ...
Страница 20: ...20 Support for load balancing in Failover Cluster Server environment for Windows Server 2008 ...
Страница 24: ...24 Support for load balancing in Microsoft Cluster Server environment for Windows Server 2003 ...
Страница 26: ...26 Adaptive Load balance ...
Страница 36: ...36 Software components ...
Страница 50: ...50 Troubleshooting ...