Detailed Error Information Detected By The Source Hvm - Hitachi NVM Navigator v03-07 User Manual

op1
0x00 00000000 0020 10 0x01
0x00 00000000 0030 10 0x01

Detailed error information detected by the source HVM

Format
"EMG" op1 : op2 : don't_care : (op3) : "MMS" : message

"EMG": Fixed characters meaning error message.

"SrcHVM": Fixed characters meaning the source HVM.

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-6 Error message detected by the source HVM
op1
0x 00000000 0200 30 06
0x 00000000 0200 40 06
0x 00000000 02aa 40 06
0x 00000000 02ab 40 06
0x 00000000 02ac 40 06
0x 00000000 02ad 40 06
0x 00000000 02ae 40 06
0x 00000000 02ab 30 06
0x 00000000 02ab 40 06
6-42
op3 Message [interpretation]
Connection refused (MMS-Blade IP=%s)
[Recovery operation terminated by a
network failure.]
Connection refused (MMS-Specified blade
IP=%s)
[Recovery operation terminated by a
network failure.]
op2
0x0000 0000 0000 0037 0x30 LPAR Migration was canceled.
0x0000 0000 0000 003d 0x30 LPAR Migration was canceled.
0x0000 0000 0000 0028
0x0000 0000 0000 0029
0x0000 0000 0000 16**
Troubleshooting
HVM Navigator User's Guide - Migration
Check for recovery of connection either
between the management server and the
specified server blade at the source or
between the management server and the
specified server blade at the destination;
then, retry recovery operation.
Check for recovery of connection
between the management server and the
specified server blade, and then retry
recovery operation.
op3 Message [interpretation]
LPAR deactivation was
detected.
Guest OS is in boot process
or FC-HBA Driver does not
support Concurrent
Maintenance.
0x30 LPAR Migration was canceled.
FC-HBA status is changing.
Suggested action
Suggested action
Activate the migrated LPAR
and retry.
Check Hitachi Fibre channel
driver versions on source
and destination server
blades and retry.
Execute the LPAR migration
again.