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
BNA “All Programs” section. Verify that the CIMOM server is running. If not, configure and start
it.
Unmanaged SAN
Unmanaged SAN cannot be imported
Symptom–Unmanaged SAN fails to appear in the list of importable SANs
Possible cause–Default comments as shipped with SPM were not removed from the XML file.
Suggested action–Edit the unmanaged SAN XML file and verify that the XML default comments as
shipped with SPM have been removed.
Symptom–Unmanaged SAN fails to appear in the list of importable SANs.
Possible cause–XML syntax errors or XML schema errors were detected.
Suggested action–Check SPM log to determine the syntax/schema validation error and correct it.
Symptom–Unmanaged SAN fails appears in the list of importable SANs but will not import.
Possible cause–Some editors leave another copy of the file in the folder with a different extension.
Suggested action–
1. Edit the unmanaged SAN XML file and verify that all XML content is correct, including the
format of XML and the opening and closing characters for XML entries.
2. Check the folder containing the unmanaged SAN XML file. Verify that there are no other files
in the folder with the same name but have an extension of “xml~”.
Unmanaged Zoned SAN goes offline after update
Symptom–After an unmanaged SAN is updated with a new zone, it goes offline and never returns.
Possible cause–The syntax of XML and/or entries may be unexpected.
Suggested action–Edit the unmanaged SAN XML file and verify that all XML content is correct,
including the format of the XML and the opening and closing characters for XML entries.
Unmanaged SAN 57