2 Requirements
This chapter provides information about Auto LUN requirements.
System requirements
To use Auto LUN, you need:
A P9500 storage system
A Remote Web Console client machine
Both Performance Monitor and Auto LUN
Volumes assigned to resource groups
You can create migration plans including volumes that belong to resource groups as source volumes
and target volumes. You may be unable to create migration plans depending on the use of Resource
Partition.
Table 1 Information about whether you can create migration plans when using Resource Partition
Resource groups where source
volumes belong
Resource groups are assigned to user
groups where you belong
Resource groups are not assigned to
user groups where you belong
CAUTION:
host. HP recommends that you specify volumes that are assigned to the resource group that can
be accessed from the host as source volumes and target volumes.
For details about resource groups, see the HP P9000 Provisioning for Open Systems User Guide
or the HP P9000 Provisioning for Mainframe Systems User Guide.
Source and target volume general requirements
The source and target volume should satisfy the following conditions:
Managed by the same P9500 storage system
Have the same emulation type and capacity. If the emulation type is not OPEN-V, both the
source and target volumes must be custom-sized (CV) volumes or normal volumes.
The LDEV IDs (LDKC:CU:LDEV) must have values between 00:00:00 and 00:FE:FF
Must be specified by LDEV ID, not VOLSER or port/TID/LUN
Supported and prohibited source and target volumes
The following list includes volumes and volume types that cannot be used as source or target
volumes for Auto LUN:
System disks
Quorum disks
Volumes being used by the host as command devices
IBM 3390 Concurrent Copy volumes
10
Requirements
Resource groups where target volumes belong
Resource groups are assigned to user
groups where you belong
Yes — you can create migration plans
No — you cannot create migration
plans
When you use the mainframe system, you can access one resource group from a
Resource groups are not assigned to
user groups where you belong
No — you cannot create migration
plans
No — you cannot create migration
plans