Detailed Error Information Detected By Migration Management Server - Hitachi HVM Navigator V03-06 User Manual

Detailed error information detected by Migration Management
Server
Format
"EMG" op1 : op2 : don't_care : (op3) : "MMS" : message
•
"EMG": Fixed characters meaning error message.
•
"MMS": Fixed characters meaning Migration Management server.
•
don't_care: Values at this position are negligible.
•
op1: 1st operand that identifies error detail in hexadecimal code. See
Description.
•
op2: 2nd operand that identifies supplementary information in hexadecimal
code. See Description.
•
op3: 3rd operand that identifies reason in hexadecimal code. See
Description.
•
Message: Shows error detail in text. See Description.
Table 6-2 Error message detected by MMS
op1
0x00 00000001 0020 02
0x00 00000002 0020 02
0x00 00000003 0020 02 0x0000 0000 0000 0000 0x01 The specified blade is busy.
0x00 00000003 00A0 02 0x0000 0000 0000 0000 0x01 Specified NIC was not found.
0x00 00000003 00A5 02 0x0000 0000 0000 0000 0x01 Specified NIC was not found.
0x00 00000004 0020 02 0x0000 0000 0000 0000 0x01 The specified blade is busy.
0x00 00000005 00B0 02 0x0000 0000 0000 0000 0x01 Can not assign the same IP
op2
0x0000 0000 0000 0000 0x01 Connection refused (MMS-
Troubleshooting
HVM Navigator User's Guide - Migration
op3 Message [interpretation]
Blade)
[Migration Management
module (MMS) cannot
connect to specified server
blade.]
Please wait until another
migration is completed.
(Src-Blade)
(Dst-Blade)
Please wait until another
operation is completed.
for the source and the
Destination.
Suggested action
Check the following, make
corrections if necessary,
and then retry migration:
The specified server blade
(HVM) is up and running.
Communication to the IP
address of the specified
server blade is established.
Check if the same server
blade is specified as source
and destination.
Wait for completion of
preceding migration and
then retry migration.
Check if you set a migration
path properly on the source
server blade and retry.
Check the setting of a
migration path on the
destination server blade
and retry.
Wait for completion of
ongoing operation and then
retry migration.
Check the setting of a
migration path for source
and destination server
blades and set a different IP
addresses for each of them.
6-33