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

Usage environments 2-39
HVM Navigator User's Guide - Migration
Application requirement for Concurrent Maintenance mode
Application requirements for Concurrent Maintenance mode are described in
this subsection.
Requirement of the LPAR to migrate
LPAR name
It is necessary that the following requirements are fulfilled.
– LPAR Name is not "NO_NAME".
–
No LPARs with the same name exist on the destination server blade.
Resources assigned to LPAR
It is necessary that the following requirements shown in the following table are
fulfilled.
Table 2-65 Requirements of resources assigned to LPAR
Item Requirement
CPU No requirement 1
Memory No limitation on memory size assigned to LPAR
Device USB When one or more USB devices are assigned, the USB devices are in
exclusive shared mode.
NIC
2
Only NIC ports in shared mode are assigned.
FC HBA Only FC HBA ports in shared mode are assigned.
Under 8 ports are assigned.
Notes:
1.
When an LPAR which physical processor numbers are specified and the processors are assigned to
the LPAR in dedicated mode is migrated, the same physical processor numbers may not be assigned
to the LPAR on the destination server blade. However, the same number of processors assigned to
the LPAR on the source server blade is assigned on destination server blade.
2. Migration might fail due to setting of shared NIC segments. For the detail, see "Note on assigning
NIC ports" in “Application requirements for Concurrent Maintenance mode” in "Usage
environments".
LPAR status
It is necessary that LPAR status is Act (Activated).
Table 2-66 Requirements of LPAR status
LPAR Status Migratable
Act(Activated) Yes
Dea(Deactivated) No
Fai(Failure) No
Concurrent Maintenance