HP Storage Provisioning Manager (SPM) version 2.3 User Guide

• For initiators that are already mapped to the volume using MS, SPM deletes all MS presentations
and creates new HS presentation(s) that reflects the FC Host requirements of the service request.
• For initiators that are already mapped to the volume using HS, SPM keeps the existing HS
presentation if LUN numbers match or if a LUN number is not specified in the FC host
requirement. Otherwise, SPM deletes the existing HS presentation and replaces it with a new
one using the LUN number specified in the FC Host requirement.
NOTE: This behavior differs from SPM 1.3, which used MS presentations. By using HS
presentations, SPM always maps all ports of the array when presenting a volume (similar to the
approach used for P6000/EVA Storage Arrays). However, SPM will not attempt to present the
volume if it does not detect that at least one array port is connected to the same SAN as the
initiators.
Creating hosts on an HP 3PAR StoreServ Storage System
When SPM attempts to present a volume to an initiator, it first probes the array to detect whether
this initiator is known to the array. If it is not, a new host is created for that initiator. The name
given to that host will generally use the host name given in the requirements. If no host name is
specified, the host name will be “SPM_” followed by the WWN of the initiator. Host names that
begin with "LSM_" are provided to SPM by Matrix OE.
The HP 3PAR StoreServ Storage System may have hosts with multiple initiator ports. SPM may
create hosts with multiple initiator ports (for example, if the requirement specifies this). If an initiator
port is already referenced on the array, then a presentation request might indicate that the initiator
port's host grouping should change. This could happen if a single host contained two initiator ports
and the presentation request referenced one of the ports but not the other (meaning that the initiator
port should not be part of the host anymore). If these presentation requests would affect presentation
for another existing volume, SPM will not change the array's configuration, resulting in a
nonconformant service.
For example: Volume1 is presented to Host1 (WWN1) and SPM requests presentation of Volume2
to Host1 (WWN1, WWN2). Adding an initiator endpoint address to the
StorageHardwareIdCollection associated with WWN1 would mean that Volume1 would be
presented to WWN2, which is a side effect. SPM presentation changes will not generate side
effects.
Controlling HP 3PAR StoreServ Storage System port usage
Under normal circumstances, SPM makes use of all appropriate ports on an HP 3PAR storage
system once it has been imported into SPM. This behavior can be modified by adding appropriate
information to the 3PAR-specific configuration file stored in <SPM Installation
folder>/state/3par_storage/Configuration.xml which identifies which target ports
SPM may use (the ports to be used are said to be whitelisted). Changes to the configuration file
are read when SPM resynchronizes an array for which ports are whitelisted. SPM’s behavior when
the configuration file is changed and services have been activated is undefined.
SPM creates the configuration file automatically on startup. Users may choose to edit the existing
file after SPM is running.
A sample 3PAR-specific configuration file is shown below. Here are some guidelines regarding
the configuration file structure:
• The OSPersonaMaps element of the configuration file should not be altered without direction
from an HP representative.
• The ArrayPortWhiteLists element of the configuration file enables the user to configure
port usage for any 3PAR storage systems that will be imported into SPM.
• Each array will have a single ArrayPortWhiteList element specifying the array name
and the ports that SPM will be allowed to use. In the example below, the array named Fred
is allowed to use four ports with WWNs ending in 1, 2, 3, and 4.
Creating hosts on an HP 3PAR StoreServ Storage System 85