Hitachi HVM Navigator V03-06 User Manual page 296

op1
0x00 00000006 0020 02 0x0000 0000 0000 0000 0x01 The specified LPAR is
0x00 00000006 0040 02 0x0000 0000 0000 0000 0x01 Connection refused (MMS-
0x00 00000007 0020 02 0x0000 0000 0000 0000 0x01 LPAR Migration was canceled.
0x00 00000007 0040 02 0x0000 0000 0000 0000 0x01 Connection refused (MMS-
0x00 00000001 0060 02
0x00 00000001 0065 02
0x00 00002001 0080 02
0x00 00002003 0080 02
0x00 00002004 0080 02
0x00 00000001 0070 02 0x0000 0000 0000 0000 0x01 The specified LPAR is not
0x00 00000001 00A0 02 0x0000 0000 0000 0000 0x01 Invalid Migration Path was
0x00 00000001 00A5 02 0x0000 0000 0000 0000 0x01 Invalid Migration Path was
0x00 00000002 00A0 02 0x0000 0000 0000 0000 0x01 Get blade information failed.
0x00 00000002 00A5 02 0x0000 0000 0000 0000 0x01 Get blade information failed.
0x00 00002002 0080 02 0x0000 0000 0000 0000 0x01 The MMS could not accept a
6-34
op2
0x0000 0000 0000 0000 0x01 Connection refused (MMS-
Troubleshooting
HVM Navigator User's Guide - Migration
op3 Message [interpretation]
damaged (Migration LPAR).
Recover the LPAR.
SrcHVM)
Migration WWNs are already
used.
DstHVM)
Blade)
[Communication between
Migration Management
module (MMS) and server
blade was lost while
acquiring information from
server blade.]
found.
[Communication was lost
while acquiring information
from server blade.]
Specified (Src-Blade)
Specified (Dst-Blade)
(Src-Blade)
(Dst-Blade)
migration with a corrupted
LPAR.
[A blocked LPAR due to
corruption is not able to be
migrated.]
Suggested action
Recover the LPAR and
retry.
Check if the source HVM is
connected to the network
and retry.
Roll back the other LPAR
with the same Migration
WWNs as the migrated
LPAR.
Check if the destination
HVM is connected to the
network and retry.
Check for recovery of
connection and then retry
migration.
Check for recovery of
connection and then retry
migration.
Check the setting of a
migration path for the
source HVM.
Check the setting of a
migration path for the
destination HVM.
Take the following
measures.
(1)Check if HVM firmware
version and version of HVM
Navigator are compatible.
(2)Install HVM Navigator
again.
Take the following
measures.
(1)Check if HVM firmware
version and version of HVM
Navigator are compatible.
(2)Install HVM Navigator
again.
Inspect the status of the
LPAR and, if blocked, take
recovery actions on the
server blade (HVM).