Hitachi NVM Navigator v03-07 User Manual page 302

Migration manual
Table of Contents

Advertisement

op1
0x00 1******* 0030 02 0x0000 0000 0004 ffff
0x00 1******* 0030 02 0x0000 0000 000A ffff
0x00 1******* 0030 02 0x0000 0000 **** ffff
0x00 2******* 0030 02 0x0000 0000 0000 0000 0x01 The MMS could not define a
0x00 3******* 0030 02 0x 4-byte_VnicID 0001 2-
0x00 3******* 0030 02 0x 4-byte_VnicID 0002 2-
0x00 5******* 0030 02 0x 4-byte_VnicID 0003 2-
0x00 3******* 0030 02 0x 4-byte_VnicID ****
6-36
op2
byte_VnicNum
byte_VnicNum
byte_VnicNum
2-byte_VnicNum
Troubleshooting
HVM Navigator User's Guide - Migration
op3
Message [interpretation]
0x01 The MMS could not define an
LPAR because there is not
enough memory in the
destination blade.
0x01 The MMS could not define an
LPAR because the name of
the specified LPAR is
'NO_NAME'
0x01 The MMS could not define an
LPAR because the specified
LPAR has an unexpected
condition.
[Unable to define an LPAR at
the destination to have the
same configuration as the
source.]
USB port on an LPAR because
the specified USB has an
unexpected condition.
0x01 There is not enough VNIC
device#3 (Virtual NIC: 2a) to
define an LPAR.
[There is no NIC at the
destination corresponding to
the NIC at the source.]
0x01 The MMS could not define a
VNIC#3 (Virtual NIC: 2a) on
an LPAR because the
specified VNIC has VLAN IDs
which are not acceptable in
the destination blade.
[Unable to define an NIC at
the destination to have the
same VLAN configuration
settings as the source.]
0x01 The MMS could not define a
VNIC#3 (Virtual NIC: 2a) to
a promiscuous mode because
this mode is not acceptable
in the destination blade.
[Unable to define a VNIC at
the destination to have
promiscuous mode in the
same configuration as the
source.]
0x01 The MMS could not define an
LPAR because the specified
VNIC#3 (Virtual NIC: 2a) has
an unexpected condition.
[Unable to define a VNIC at
the destination to have the
same configuration as the
source.]
Suggested action
Reserve enough amount of
free memory in the
destination HVM and then
retry migration.
Rename the specified LPAR
to a unique name in the
system and then retry
migration.
Reserve enough amount of
free resource in the
destination and then retry
migration.
Check source and
destination LPAR
configurations and retry.
Inspect the physical
configuration of NIC (LAN
adapter) at the destination,
reconfigure it to meet that
of the source, and then
retry migration.
Inspect the physical
configuration of NIC (LAN
adapter) at the destination
as well as review the NIC
settings (VLAN mode and
VLAN ID) at the source,
reconfigure them to meet
each other, and then retry
migration.
Inspect the physical
configuration of NIC (LAN
adapter) at the destination
as well as review the NIC
setting (promiscuous mode)
at the source, reconfigure
them to meet each other,
and then retry migration.
Inspect the physical
configuration of NIC (LAN
adapter) at the destination,
reconfigure it to meet that
of the source, and then
retry migration.

Advertisement

Table of Contents
loading

Table of Contents