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
Understanding EVA Storage System presentation, mapping, and masking
EVA offers provides a presentation model for managing host access to volumes. This model allows
for explicitly defined mapping and masking, based on specific Vdisk and host initiators. This
presentation model allows a volume to be accessed by initiators on available controller host ports.
The preferred controller may be automatically configured by the EVA system or may be set to a
preferred controller by the administrator. Internally, SPM tracks hosts as collections of initiator
endpoints. When an EVA array is imported into SPM, its host port WWNs are found and equivalent
host port entries are created in SPM’s catalog. During storage service provisioning automation,
presentation update requests may reference hosts that map to the EVA’s host entry or new collections
of initiator endpoints. SPM uses the hosts’ initiator endpoint addresses to relate the hosts to an
existing host entry on the array if possible. The presentation update may potentially cause a
unpresent operation on the volume to clear its current presentation setting (i.e. to mask the old
presentation). Then, if necessary, host entries are created on the array. Finally, the update results
in a presentation operation to map the volume to the appropriate host. EVA constrains host entries,
disallowing a particular initiator endpoint address to exist in more than one host entry. This means
that two volumes presented to the same initiator endpoint will reference the same host entry. This
means that a particular requested presentation change could affect presentation for another volume
if the request would modify the host entry. SPM looks for these kind of side effects and blocks them.
Working with EVA Storage System host modes
With the EVA system there is a one-to-one relationship between SPM host modes and EVA host
modes.
Creating hosts on an EVA 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 “LSM_” followed by the WWN of the initator if created by Matrix or “SPM_”
followed by the WWN of the initiator if created within SPM. SPM can show presentations that
contain hosts with multiple initiator ports, but when creating hosts, SPM always creates a host with
a single initiator port. If SPM must present a volume to an initiator that is already referenced 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.
NOTE: SPM does not allow creation of new folders under Host in the HP P6000 Command View.
However, if the administrator has created host entries under folders, the existing folders and
contained hosts will be imported into SPM and can be referenced when specifying Fibre Channel
host requirements. Please refer to HP P6000 Command View documentation for more information
about hosts and folders.
62 Working with EVA storage systems