HP StorageWorks XP Provisioning Manager User Guide (December 2005)

Working With OS-Based Constraints 54
4 Working With OS-Based Constraints
The following sections describe restrictions and notes on managing a host by using Provisioning Manager. The
restrictions and notes are given separately for each OS.
When adding a device file, or adding or expanding a file system for a host that is not recognizing any LUs, use
Device Manager to register the port WWN of the HBA for the host in advance. If no WWN is registered, no
volume will become selectable in the wizard step for selecting a volume, and you will be unable to continue
operations.
• Restrictions on Host Management (section
4-1 )
• Restrictions When the Host OS is Windows
®
(section 4-2 )
• Restrictions When the Host OS is Solaris™ (section 4-3 )
• Restrictions When the Host OS is AIX
®
(section 4-4 )
• Restrictions When the Host OS is Linux (section
4-5 )
• Restrictions When the Host OS is HP-UX (section 4-6 )
• Maximum Setting Values (section
4-7 )
4-1 Restrictions on Host Management
Some restrictions on host management apply regardless of the operating system involved, while others are
OS-specific.
4-1-1 Configuring Cluster Software
When you use the host management functionality to add, expand, or delete a file system, or add or delete a
device file, Provisioning Manager does not perform configuration of the cluster software. You must manually
configure the cluster software.
The cluster software that can use the file systems and device files created by the host management
functionality is as follows (note that it changes according to operating system):
• Windows
®
host OS: Microsoft
®
Cluster Server (MSCS)
• Solaris™ host OS: VERITAS™ Cluster Server
• AIX
®
host OS: HACMP
• Linux host OS: cluster software not supported
• HP-UX host OS: Serviceguard
4-2 Restrictions When the Host OS is Windows
®
The following sections apply when the host OS is Windows
®
. 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 the 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-2-1 Prerequisites for the Host
• The Device Manager agent
You must install a Device Manager agent on a host managed by Provisioning Manager. If a Device
Manager agent is not installed, the values for some items may not be displayed.
If the Provisioning Manager support functionality for the Device Manager agent is not installed, the values
for some items may not be displayed.
• diskpart.exe command line utility
Provisioning Manager contains functionality that requires the diskpart.exe command line utility
provided by Microsoft
®
. When the OS of the host managed by Provisioning Manager is Windows
®
2000,
you must obtain the diskpart.exe command line utility separately. You can download this utility from
the Microsoft
®
web site. Install diskpart.exe in the Windows-system-installation-directory \system32.
When the OS is Windows 2003, the diskpart.exe command line utility will be started in the