HiCommand Dynamic Link Manager (HDLM) for Windows Systems User's Guide (HIT5201-96001, January 2008)

316 Chapter 9 Messages
Message ID Message Details and Actions
KAPL02054-I aa...aa path(s) were successfully placed
Offline(C). The Offline request of
bb...bb
path(s) were registered.
cc...cc path(s) could
not be placed Offline(C).
Details
Indicates the number of the processed paths
when the offline request was registered during
the Reserve processing.
aa...aa: The number of paths that succeeded
in the offline processing (decimal number)
bb...bb: The number of paths for which the
offline request was registered (decimal number)
cc...cc: The number of paths failed in the
offline processing (decimal number)
Action
For the Path ID(s) of the failed path(s), see the
operation log. Click Refresh if you want to
check the registered path(s) in a batch job.
KAPL02055-I The target path(s) are already aa...aa. Details
The specified paths are already
Online/Offline(C), resulting from the
online/offline processing.
aa...aa: Online or Offline(C)
Action
Click Refresh to check the status of the path.
KAPL02058-E The configuration does not support the
simultaneous use of the load balancing and
cluster support functions.
Details
If a storage system for which persistent reserve
is not supported exists among the HDLM-
managed storage systems, the load balancing
function cannot be used in the cluster
environment.
Action
Make sure that all HDLM-managed storage
systems support persistent reserve. Contact
your storage system vendor or maintenance
company to check whether the storage systems
you are using support persistent reserve.
KAPL02061-W The getting PathInformation has been stopped
because the path configuration was changed
during HDLM GUI startup processing.
Details
The path information could not be acquired
because the configuration of paths was
changed during HDLM GUI startup processing.
Action
Click Refresh after you confirm the
reconfiguration of the path is not done.
KAPL02062-E The Refresh operation has been stopped
because the configuration of paths was
changed during the processing of the Refresh
operation.
Details
The information of the path could not be
acquired because the configuration of paths
was changed during the processing of the
Refresh operation.
Action
Click Refresh after you confirm the
reconfiguration of the path is not done.