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
D Working with 3PAR storage systems
Overview
3PAR Storage Systems have several value-add features. It is important to understand how SPM
handles management of environments using those features. See the following sections for an
explanation of these features.
Understanding how to import 3PAR arrays into SPM
Using the Import Array feature in the SPM 2.0 GUI, 3PAR arrays may be imported into SPM. This
in turn allows storage pools and volumes on the array to be imported. During the array import
wizard, a set of authentication credentials must be provided. SPM accesses the 3PAR array with
these credentials. The user name/password combination given determines what child resources
(storage pools and volumes) will be visible for importing, based on the access that the given user
is authenticated for. It is recommended that the user credentials selected have an Edit or Super
permission level on the array.
After importing the 3PAR array, storage pools may be imported. This step of the import wizard
shows a list of available storage pools. As mentioned above, this list is constrained by what the
authenticated user is permitted to access. Additionally, SPM constrains this further to only show
concrete pools and their derived pools. This means that the primordial pool and replica pools will
not be available to import. Note that SPM has no mechanism for creating storage pools on the
3PAR array.
After importing storage pools from the 3PAR array, volumes may be imported. The list of available
volumes is limited based on user access permissions, as well as some additional constraints imposed
by SPM. There are several classes of volumes that cannot be imported: admin volumes, snapshot
volumes, remote copy volumes, and volumes in a virtual domain will all be ignored by SPM’s
import wizard.
Understanding 3PAR capacity reporting
SPM tracks capacity for storage pools and volumes within its catalog. These capacity values are
used to generate candidates for storage provisioning. In order to understand the candidate
generation process, it is important to know what SPM tracks and how that relates to 3PAR’s modeling
of storage pools and volumes.
Storage pool capacity
At the storage pool level, SPM tracks physical capacity, committed capacity, and subscribed
capacity. Physical capacity is the total number of bytes that are physically allocated to the storage
pool. Committed capacity represents the space that has been allocated within the pool for all of
its volumes. Subscribed capacity is the total capacity for all the volumes contained in the pool.
Additionally there is a calculated value, available capacity, that is used when selecting candidate
pools for volume creation or growing.
Mapping these concepts onto the 3PAR resource model is complicated by 3PAR’s support of two
types of storage pools: concrete pools and Common Provisioning Groups (CPG).
In 3PAR concrete pools represent actual disk capacity in the system. There may be at most 3
concrete pools, each of which groups together hard disks of the same type; these concrete pools
are:
• all-FC for all fibre channel drives
• all-NL for all Nearline drives (SATA)
• all-SSD for all solid state drives
The sum of all concrete pools’ capacity represents the raw capacity of the entire 3PAR system.
3PAR volumes (a.k.a. virtual volumes) can be allocated directly from concrete pools. In 3PAR terms,
these are called legacy volumes because, from 3PAR InformOS v2.3.1 on, it is recommended to
allocate volumes from CPG (see next section). Concrete pools are not RAID-locked, which means
Overview 63