Hitachi NVM Navigator v03-07 User Manual page 303

op1
0x00 4******* 0030 02 0x 4-byte_BusDevFunc
0x00 4******* 0030 02 0x 4-byte_BusDevFunc 2-
0x00 ffffffff 0030 02
0x00 60000001 0030 02 0x0000 0000 0000 0001 0x01 The MMS could not define an
0x00 60000004 0030 02 0x0000 0000 0000 0001 0x01 The MMS could not define an
0x00 70000001 0030 02 0x0000 0000 0000 0001 0x01 The MMS could not define an
0x00 70000002 0030 02 0x0000 0000 0000 0001 0x01 The MMS could not define an
0x00 80000001 0031 02 0x0000 0000 0000 0000 0x01 The MMS could not activate
0x00 80000002 0031 02 0x0000 0000 0000 0000 0x01 The MMS could not activate
op2
0000 0000
byte_PortNum
2-byte_SlotNum
0x**** **** **** **** 0x01 Connection refused (MMS-
Troubleshooting
HVM Navigator User's Guide - Migration
op3 Message [interpretation]
0x01 The destination blade does
not have an installed shared
FC device
(Bus#:Dev#.Func# =
00:03.4) to define an LPAR.
[There is no FC able to be
defined at the destination.]
0x01 There is not enough vfcID on
the shared FC device (DST-
Slot = 6, DST-Port = 0,
Bus#:Dev#.Func# =
00:03.4) to define an LPAR.
[There is no free vfcID
required to define an FC at
the destination.]
DstHVM)
[Communication between
Migration Management
module (MMS) and server
blade was lost while defining
an LPAR.]
LPAR because the Virtual-
Console on the specified
LPAR has an unexpected
condition.
LPAR because the Virtual-
Console on the specified
blade not empty.
LPAR because the specified
processor group has not been
defined.
LPAR because the specified
processor group is busy.
the LPAR because there is
not enough CPU in the
destination blade.
[There is no free CPU
required to activate LPAR at
the destination.]
the LPAR because there is
not enough memory in the
destination blade.
[There is no free memory
required to activate LPAR at
the destination.]
Suggested action
Check if the destination
HVM has a physically
installed FC that
corresponds to the FC port
allocated to the source
LPAR.
Check if the FC port at the
destination has a free
vfcID.
Check for recovery of
connection and then retry
migration.
Check the setting of Virtual
COM consoles on source
and destination HVMs and
retry.
Check the setting of VC
number on the destination
HVM and retry.
Check the setting of
processor groups on the
destination HVM.
Check the condition on the
destination HVM and retry.
Reserve enough free
processors in the
destination HVM and then
retry migration.
Reserve enough amount of
free processor memory in
the destination HVM and
then retry migration.
6-37