HP Storage Provisioning Manager (SPM) version 2.3 User Guide

Sample configuration file

<?xml version="1.0"?>

<Configuration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xmlns:xsd="http://www.w3.org/2001/XMLSchema" Version="2.2" xmlns="urn:TPDStoragePlugin">

</OSPersonaMap>

</OSPersonaMap>

</OSPersonaMaps>

</ArrayPortWhiteList>

</ArrayPortWhiteLists>

</Configuration>

Working with HP 3PAR StoreServ Storage System active VLUNs and VLUN

templates

On HP 3PAR StoreServ Storage Systems, active VLUNs are the paths through which hosts that have

logged on to the fabric can see a given volume. VLUN templates are similar to “declarations” that

volumes are presented to hosts that are currently unknown to the array (for example, offline hosts).

SPM creates VLUN templates, which become active VLUNs when the host is powered on.

For more information, refer to the HP 3PAR StoreServ Storage System User Guide.

Working with autonomic groups

Autonomic groups are a unique feature of HP 3PAR StoreServ Storage Systems that allow storage

administrators to group volumes, hosts, or virtual domains together. Those groups (also known as

sets) allow batch operations on a collection of objects – for instance, presenting a volume to a set

of hosts in one operation – and provide a level of automation by automatically adjusting the way

volumes are exported when objects are added to or removed from sets. For more information,

please refer to the array user guide.

This version of SPM is not fully compatible with autonomic groups and it is recommended to not

use them on arrays managed by SPM. However autonomic groups can be used within the following

guidelines:

• Importing volumes that belong to one or more volume sets is supported. SPM will not reflect

the containment of those volumes in volume sets.

• Presenting volumes to hosts that belong to one or more host sets is supported. SPM will not

reflect the containment of those hosts in host sets.

• Importing volumes that are presented to one or more host sets is NOT supported: SPM will

not be able to reflect that presentation and doing so will lead to errors and inconsistencies

during requirement binding.

• Likewise, using non-SPM tools (for example, HP 3PAR Management Console or CLI) to present

an already-imported volume to a host set will result in unpredictable behavior during

requirement binding.

86 Working with HP 3PAR StoreServ Storage Systems