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
Requirements
When creating a Connectivity Service there are two use cases as follows:
Standard Use Case
In the standard case one or more FCInitiatorEndpoint requirements are given in conjunction with
one or more FCTargetEndpoint requirements. For each and every endpoint requirement the sub
requirement FCWWN is required.
SPM will interpret these requirements as follows. SPM will check that all the given endpoints are
on the same network. Then it will check that each initiator can communicate with each of the targets
(the network is open, they are already zoned together, or zoning automation can take place to
put then in a zone together). However since we will be using the SIZ policy we will not check
connectivity between the initiator requirements only the initiator to all targets.
If the endpoints as described above can be connected or already are then one and only one
candidate is returned to signify that yes the desired endpoints requirements can be or are already
connected together.
Proxy Use Case
The proxy case is much like the standard case with a couple of caveats. First the sub requirement
FCProxyWWN is given in addition to the FCWWN for a FCInitiatorEndpoint requirement.
Since FCWWN doesn’t necessarily have to exist as of yet (for example, the host may not have
logged into the fabric as of yet). SPM will use the given FCProxyWWN requirement, which is the
WWN of another endpoint that has already logged into the fabric and is known to SPM (typically
this is the uplink port of a Blade enclosure, but could be any known port). The FCProxyWWN is
used to identify where the FCWWN will live once it is powered up and allows SPM to generate
candidates for it as if it already exists.
Unmanaged networks
SANs that have no automated management path from SPM (unmanaged network) can still be
imported into the SPM catalog. Using an unmanaged network is recommended for a small number
of storage devices only.
For additional information regarding unmanaged networks, please refer to Working with
unmanaged networks.
60 Working with Brocade Fibre Channel networks