HP Storage Provisioning Manager (SPM) Version 2.0 User Guide
Table Of Contents
- HP Storage Provisioning Manager (SPM) Version 2.0 User Guide
- Contents
- 1 Introduction
- 2 Getting started with SPM
- 3 Importing storage into the storage catalog
- 4 Storage service policy
- Managing templates
- Service types
- Requirement types
- All Of requirement
- Any Of requirement
- Connected To Fibre Channel Endpoint requirement
- Connected To Network requirement
- Fibre Channel Initiator Endpoint requirement
- Fibre Channel Target Endpoint requirement
- Fibre Channel Host requirement
- Network Capability requirement
- RAID Level requirement
- Resource Existence requirement
- Service Deactivation Policy requirement
- Storage Capability requirement
- Storage Pool Available Capacity requirement
- Storage Pool Subscription Ratio requirement
- Storage Pool Volume Count requirement
- Tag requirement
- Use Resource requirement
- Volume Capacity requirement
- Volume Committed Capacity requirement
- Volume Creation Security Group requirement
- 5 Storage service provisioning
- 6 Managing storage catalog entities
- Managing arrays
- Viewing and modifying array properties (Overview tab)
- Viewing array storage pools (Storage Pools tab)
- Viewing array volumes (Volumes tab)
- Viewing array ports (Ports tab)
- Viewing array host entries (Hosts tab)
- Viewing and modifying array capabilities settings (Capabilities tab)
- Viewing and modifying array security settings (Security tab)
- Removing an array
- Managing storage pools
- Managing volumes
- Managing networks
- Managing security
- Resynchronizing resources
- Quarantining resources
- Managing arrays
- 7 Monitoring the storage catalog
- 8 Support and other resources
- A Troubleshooting
- Viewing operational logs
- Addressing common issues
- Storage Provisioning Manager issues
- SPM will not launch in browser
- The user is unable to login through the SPM user interface
- Issues with multiple SPM instances pointed to the same storage resources
- Cannot import 3PAR Storage Systems
- 3PAR SMI-S connection problems
- Service activation fails to present volumes on 3PAR arrays
- EVA arrays and/or XP arrays are marked as Offline when they appear to be functioning correctly outside of SPM
- HP Matrix OE storage pool issues
- Storage Provisioning Manager issues
- Backup and recovery
- Managed SAN
- Unmanaged SAN
- B Working with Brocade Fibre Channel networks
- C Working with EVA storage systems
- D Working with 3PAR storage systems
- Overview
- Understanding how to import 3PAR arrays into SPM
- Understanding 3PAR capacity reporting
- Understanding 3PAR Storage System volume creation/growth
- Understanding 3PAR Storage System virtual domains
- Exposing volume presentations in 3PAR Storage Systems
- Working with 3PAR Storage System host modes
- Presenting volumes on 3PAR Storage Systems
- Creating hosts on a 3PAR Storage System
- Working with 3PAR Storage System active VLUNs and VLUN templates
- Working with autonomic groups
- Volume migration (Tiering)
- Importing a large number of volumes
- Unique identification of common provisioning groups (CPG)
- E Working with HP P9000/XP Disk Array
- F Working with unmanaged networks
- G Working with unmanaged arrays
- H Units of measurement
- Glossary
- Index
![](/manual/hp/hp-consolidation-pack-for-hp-proliant-100-server-licenses/hp-storage-provisioning-manager-spm-version-20-user-guide/images/img-52.png)
Understanding P9000/XP disk array presentation, mapping, and masking
In the HP P9000/XP disk array, volumes are presented through FC host ports, which SPM calls
target ports, and host groups. A host group is a collection of initiator endpoints. Each initiator
endpoint is a represented as a WWN. A host group is used to explicitly define a mapping and
masking relationship between a specific volume and initiators included in the host group.
Hierarchically, host groups are defined under array target ports. This implies that an initiator can
exist in multiple host groups, but under different array target ports. Also, host group names are
case sensitive, i.e. Host1 and host1 are treated as two different host groups by P9000/XP and
SPM.
These host groups are called “host entries” in SPM, which tracks them as collections of initiator
endpoints. When a P9000/XP array is imported into SPM, its host group details are discovered
and equivalent host entries are created in SPM’s catalog. During storage service provisioning
automation, presentation update requests may reference hosts that map to the P9000/XP host
WWNs or new collections of initiator endpoints. SPM uses the host group’s initiator endpoint
addresses to relate the hosts to existing WWNs if possible. The presentation update may potentially
cause an un-present operation on the volume to clear its current presentation setting (i.e. to mask
the old presentation). Then, if necessary, host groups (WWNs) are created on the array on all the
specified target ports. Finally, the provider updates the results of the presentation operation to map
the volume to the appropriate host group. P9000/XP allows more than one initiator endpoints be
grouped in a host group.
SPM does not populate the “nickname” attribute of a host WWN in a host group.
Working with P9000/XP disk array host modes
HP P9000/XP disk arrays support a variety of host modes that depend on the operating system.
SPM supports creation of the following host modes for P9000/XP disk array.
SPM host modeP9000/XP host mode
Windows / Windows 2008Windows
LinuxStandard
HPUXHPUX
VmwareVmware
OpenVMSOpenVMS
Creating hosts on a P9000/XP disk array
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 group is created for that initiator, under
required (multiple) target ports. When hosts are created by Matrix, the host name will be prefixed
with the string “LSM_”. If no host name is specified in the service requirements or if there is a
naming conflict with existing host groups, the name will be of the form “SPM_<time in milliseconds>”
or “SPM_<unique identifier>. See table below for more detailed information. If SPM presents a
volume to an initiator that is already included in a host group on the array, and if that initiator
belongs to a multiple-initiator host, then all initiators for that host will be mapped to the volume.
This could potentially result in a non-conformant service.
HP P9000/XP disk array has constraints for maximum length of host group name that can be
created on the array. SPM supports following limits for maximum length for host group name.
Default host group name if conflict
encountered
Maximum length supported in SPMArray model
SPM_<time_in_ms>64 charactersP9500
SPM<unique_identifier>16 characters *XP24000/20000
70 Working with HP P9000/XP Disk Array