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
NetworkEndpointKind
NetworkEndPointKind is an enumerated type representing the implementation of the network for
a SAN network endpoint. It has four possible values: FibreChannel, SerialAttachedScsi,
Ethernet, and iSCSI. At this time, SPM supports only Fibre Channel networks.
Example unmanaged SAN xml
In this section we provided an annotated example of an XML file representing an unmanaged
array. The example is provided in Courier font. Annotations are provided within the example
as normal font.
<?xml version="1.0" encoding="utf-8"?>
<SanResourceCollection xmlns="urn:SPM_SanResourceCollection_1">
<NetworkResource Name="Example Unmanaged Storage Network v0.0.1" DisplayName="Example Unmanaged Storage Network"
Description="Example unmanaged storage network.">
Every XML document must begin with the XML element indicating the XML version and the character
encoding. Every Unmanaged SAN XML file must begin with the SanResourceCollection root element.
This example specifies a namespace for use within SPM, and a single NetworkResource object.
<Network Name="Black Network" ZoningState="Zoned">
<Zone Name="Zone1">
<Endpoint Address="EE:FF:AA:BB:DD:00:EE:01" Kind="FibreChannel" />
<Endpoint Address="EE:FF:AA:BB:DD:00:EE:02" Kind="FibreChannel" />
<Endpoint Address="EE:FF:AA:BB:DD:00:EE:03" Kind="FibreChannel" />
</Zone>
<Endpoint Address="EE:FF:AA:BB:DD:00:EE:04" Kind="FibreChannel" />
<Endpoint Address="EE:FF:AA:BB:DD:00:EE:05" Kind="FibreChannel" />
</Network>
This NetworkResource contains a single Network, which in turn contains a single Zone and two
endpoint addresses outside of any zone. In all cases, these end points are FibreChannel end points.
</NetworkResource>
</SanResourceCollection>
This NetworkResource Definition is simplified to illustrate the nature of an Unmanaged SAN XML
file. This example contains a single network with a single zone, while multiple instances of those
elements are allowed, as specified above.
Example unmanaged SAN xml 77