Hitachi HVM Navigator V03-06, User Manual, Page: 243 / 312

Usage notes 5-11
HVM Navigator User's Guide - Migration
Service ratio after migration
Migration functions of HVM Navigator carry the existing service ratio value,
which is used for allocation of shared CPU resources to an LPAR, from the
source LPAR to the destination LPAR as it is. Attention has to be paid, however,
that the service ratio value after the migration means the ratio relative to the
service ratios already allocated to the other LPARs on the same destination
HVM.
For example, even when the service ratio value at the source LPAR on HVM1
remains the same at the destination LPAR on HVM2, the CPU resource
allocated to the destination LPAR on HVM2 may not necessarily be the same as
the original CPU resource allocated to the source LPAR on HVM1. In order to
achieve optimum CPU resource allocation to the destination LPAR, a new
amount of CPU resource (service ratio) required for the destination LPAR must
be recalculated according to the settings of the destination HVM.
Migration of server with dedicated PCI device allocation
Under the current version, Migration functions of HVM Navigator do not
support migration of a server to which PCI devices are allocated in dedicated
scheduling mode. As a workaround, the device scheduling mode at the source
should be temporarily changed to shared mode prior to migration, and further
changed to dedicated mode at the destination after the migration. Be noted
that a change in the device scheduling mode requires restarting of HVM
system service.
Migration of MAC addresses
When an LPAR whose MAC address is changed in the Virtual NIC Assignment
on HVM Screen is transferred, the MAC address is not transferred.
So, do not have an LPAR migrate whose MAC address is changed.
Migration of WWPNs
Execution of Migration functions of HVM Navigator exchanges WWPNs between
the source HVM and the destination HVM. While WWPNs for the FC HBA ports
used by the source server are uniquely determined, WWPNs on the destination
server are randomly determined among unassigned WWPNs on the destination
HVM.
Where WWPNs are managed in association with hardware or vfcID, it should
be noted that such management becomes unusable by the introduction of
Migration functions of HVM Navigator. It is recommended that WWPNs are
managed in association with LPAR name (or server name) and port number.