HP StorageWorks XP48 Disk Array - Manual (Page 58)

Working With OS-Based Constraints 58
4-2-12 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-2-13 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-2-14 Notes on Mounting a Folder in Windows ® 2000
When you assign multiple LUs to one host in Windows ® 2000, make sure that the folders you want to mount do
not have a parent-child relationship. If the folders have a parent-child relationship, you cannot correctly operate
a file system using Provisioning Manager. For example, if you mount the two folders H:\HPvM01 and
H:\HPvM01\HPvM02, you cannot operate the file system correctly. Instead, mount two folders such as, for
example, H:\HPvM01 and H:\HPvM02, which do not have a parent-child relationship.
The following describes how the program runs and what actions you should take if you mount folders that have
a parent-child relationship and attempt to operate a file system.
If a file system is added or expanded:
In the GUI window, an error (KARF62014-E) appears indicating that the file system does not exist. However, the
file system is added or expanded properly.
When the host information is updated, the file system information will be applied to the GUI window.
If a file system is deleted:
In the GUI window, an error (KARF62014-E) appears indicating that the file system does not exist, and the file
system is not deleted.
Delete the file system manually. Then, update the host information, and make sure that the file system has
been deleted.
4-3 Restrictions When the Host OS is Solaris™
The following sections describe restrictions that apply when the host OS is Solaris™. For details about the
maximum setting values for manual configuration, see
Table 4-1 in 4-7 .
WARNING! Make sure that you specify a unique port address for each port of storage devices in the same
zone. If the same port addresses exist in the same zone, the OS cannot identify the ports and may not
recognize the device files. In such a state, if you add a device file, add a file system, or expand a file system
from Provisioning Manager, the device file cannot be recognized and an error occurs.
4-3-1 Prerequisites for the Host
• The Device Manager agent
You must install the Device Manager agent on a host managed by Provisioning Manager. If the Device
Manager agent is not installed, the values for some items may not be displayed.