HP StorageWorks XP48 Disk Array - Manual (Page 66)

Working With OS-Based Constraints 66
4-4-14 Ensuring Dynamic Link Manager Operations
In any of the following environments, if a Device Manager agent version 1.0 or later is installed on the host,
Provisioning Manager can display a list of volumes, including the unmanaged LUs, and can be used to specify
settings for the managed LUs:
• When the LU is manually excluded from the Dynamic Link Manager management
• When multi-path management software other than Dynamic Link Manager is also used
However, for an LU managed by a path manager other than Dynamic Link Manager, Provisioning Manager
cannot acquire the information managed by the path manager, such as the number of paths and data paths.
To specify LU settings in the above environment, check the following items:
• That the version of the Device Manager agent installed on the host that manages the target LU is
version 1.0 or later
• That the target LU is managed by Dynamic Link Manager
NOTE: Provisioning Manager treats all LUs that are added when file systems or device files are added or
expanded as being under the management of Dynamic Link Manager.
4-4-15 Deleting a Mount Point Directory
Even if a file system is deleted, the mount point remains. Use the OS command to manually delete the folder if
no longer necessary.
4-4-16 AIX ® File System and Device File Sizes
In AIX ® , when the file systems or device files are created, their sizes are smaller than the size of the volume
(LU). The reasons are as follows:
• Because one physical partition is reserved for the JFS log, the total size of the file systems or the device
files is smaller than the volume (LU) for the size of one physical partition.
• Because of a limit on the number of physical partitions within an LU (up to 1,016 physical partitions), the
maximum size of the file system and device file that can be created is 128 GB.
4-4-17 Notes on Changing the Software Configuration
For a host for which a host-setting operation has not finished (that is, for a host for which a suspended
operation exists in the operation log), do not change any of the software listed below by installing or uninstalling
them, or by changing the software version.
• OS
• File system
• Program prerequisite for Provisioning Manager
• Program related to Provisioning Manager
For specific software names, see system requirements, prerequisite programs and related programs described
in the manual HP StorageWorks XP Provisioning Manager Installation and Configuration Guide.
If you change any of the above software for a host for which a host-setting operation has not finished, that host-
setting operation cannot be guaranteed when it resumes from the operation log. Before you change any
software, see the operation log and make sure that all host-setting operations have finished.
4-4-18 Notes on Changing a Host Name
When you change the host name of a host machine, match the host name of the host machine with the host
management information of Device Manager, and then use Provisioning Manager.
If you update host information when the host name of the host machine and host management information of
Device Manager do not match, both the host name that existed from before the change and the one created
after the change are displayed in the host management window. In such a case, you might be unable to use
Provisioning Manager correctly.
4-5 Restrictions When the Host OS is Linux
The following sections describe restrictions and notes when the host OS is Linux.
For details about the maximum setting values for manual configuration, see Table 4-1 . in 4-7 .