HP Storage Provisioning Manager (SPM) Version 2.3 User Guide Abstract This guide provides information to successfully install, configure and manage HP Storage Provisioning Manager (SPM).
© Copyright 2010 - 2013 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 Introduction.............................................................................................10 Data storage and SPM............................................................................................................10 SPM environment....................................................................................................................10 Minimum requirements............................................................................................................
Volume Creation Security Group requirement.........................................................................32 Volume Name Prefix requirement.........................................................................................32 5 Storage service provisioning......................................................................33 Provisioning a storage service..................................................................................................
Deleting a security group...............................................................................................53 Resynchronizing resources........................................................................................................53 Changing the resync interval...............................................................................................54 Quarantining resources...........................................................................................................
Importing resources............................................................................................................70 Cannot import HP XP/P9000 arrays into SPM...................................................................70 Cannot import EVA arrays into SPM.................................................................................70 Managed SAN......................................................................................................................
Presenting volumes on HP 3PAR StoreServ Storage Systems..........................................................84 Creating hosts on an HP 3PAR StoreServ Storage System.............................................................85 Controlling HP 3PAR StoreServ Storage System port usage...........................................................85 Working with HP 3PAR StoreServ Storage System active VLUNs and VLUN templates......................86 Working with autonomic groups...............................
Endpoint.........................................................................................................................100 Kind..........................................................................................................................101 Address.....................................................................................................................101 ZoningState..............................................................................................................
Address.....................................................................................................................111 Kind..........................................................................................................................111 StorageArrayPort.............................................................................................................112 Name........................................................................................................................
1 Introduction HP Storage Provisioning Manager (SPM) is a software solution that manages storage provisioning within the HP Matrix Operating Environment (Matrix OE). It provides a secure service-centric management interface to storage. It enables storage services to be resourced with new or existing volumes from a storage catalog, and securely automates storage management tasks by interfacing directly with storage arrays and SAN management software.
Figure 1 Understanding the SPM environment SPM 2.3 is bundled with HP Matrix Operating Environment 7.3. Matrix OE works with SPM to provide storage services into that environment and automate several operations related to that storage. SPM has built in support for HP 3PAR StoreServ Storage Systems, HP EVA/P6000 arrays, HP XP/P9500 arrays, and Brocade and HP fabric management software. For more information, see “Minimum requirements” (page 12).
NOTE: SPM does not support on-demand storage provisioning on XP storage systems. Additionally, management of XP storage systems through SPM requires Fibre Channel connectivity to the server running SPM. For more information, see “Working with HP P9000/XP Disk Array” (page 89). Minimum requirements SPM supports the following managed storage systems: Storage System Model Firmware HP 3PAR F200, HP 3PAR F400, HP 3PAR T400, HP 3PAR T800, HP 3PAR StoreServ 7000, HP 3PAR StoreServ 10000 HP 3PAR OS 3.1.
NOTE: • For more information and access to HP B-Series Network Adviser software, see HP B-series Management Software - Overview & Features. Download information can be found under “HP Support and Drivers.” • Brocade's legacy standalone SMI Agent is not supported by SPM. SPM will only support the SMI Agent installed via HP B-Series Network Advisor/Brocade Network Advisor installation packages as called out above. • For information on restrictions on using historical data collection with BNA 12.0.
Figure 2 Interaction between user roles Server Administrator Matrix Operating Environment (OE) Software Provision storage services Request storage services Expose storage templates Return services Storage Architect Configure storage service templates (policy) Configure security Storage Administrator Import storage resources Monitor resource utilization Monitor service conformance Storage Provisioning Manager (SPM) Consumer Can also provision storage services Automate storage configuration Storage
2 Getting started with SPM This chapter provides information on installing, configuring, and running SPM. Installing SPM SPM is installed as part of the HP Matrix OE solution. You must have Microsoft .NET 4.0 or .NET 4.5 installed on the Central Management Server to use the SPM software. See HP Insight Management Installation and Configuration Guide for more information. Upgrading from SPM v1.x At the end of the SPM 2.3 installation, if an SPM 1.
Importing HP XP/P9000 arrays as managed arrays during an upgrade HP XP/P9000 arrays can be imported as managed arrays when performing an upgrade by creating a credentials file named SPMCredentials.txt and placing this file in the /state folder. The SPMCredentials.txt file must be created and placed in the state folder before the upgrade is performed. The credentials file must have the following format: • A one line entry for each XP array.
software must be installed. For more information, see “Working with Brocade Fibre Channel networks” (page 72). Installation and configuration of HP Matrix OE, HP 3PAR StoreServ Storage Systems, HP EVA disk arrays, and HP XP/P9000 disk arrays is beyond the scope of this document. NOTE: This information does not apply to unmanaged arrays or SANs. For more information, see “Working with unmanaged networks” (page 92) or “Working with unmanaged arrays” (page 103).
The following procedure can be used to provide a certificate. 1. Import the new certificate (and the associated private key) into the Local Computer\ Personal (My)” certificate store as follows: a. Run certlm.msc. The certlm window is displayed. b. c. d. Right-click on the Personal\Certificates folder. Select All Tasks→Import Select the file containing the certificate file.
4. Stop the SPM service using the service manager, or type the following at command prompt: sc stop hpspm 5. Open the SPM configuration file, which is stored at the following location: /state/ApplicationConfig.xml 6. Paste the thumbprint obtained in step 3 into the SSLThumbprint configuration value in the file.
The Dashboard window contains the "Storage Services" and "Capacity" areas. The Navigation tree provides access to the other areas in the user interface. The Storage Services, Resources, and Administration subsections are contained in the tree. A link to Getting Started and Dashboard are also provided at the top of the Navigation tree. Select a subsection item from the Navigation tree (the left-most pane) to display that item in the content pane.
1. Select Tools→Preferences. The Preferences dialog box appears. 2. 3. Click Data Size Format.
Signature State Interpretation Possible Action Management signatures are supported on HP 3PAR StoreServ Storage Systems and HP P6000/EVA arrays. Not present with changes This indicates volumes mentioned in SPM's since recovery restored state that are not known to be managed by any instance of SPM since they do not have a management signature, and which had different properties recorded in the restored state than they have at recovery time.
3 Importing resources into the storage catalog Only storage and networks imported into the catalog can be used by SPM to fulfill storage service requirements, except for volumes created on-demand. SPM can automatically provision volumes from imported storage pools on arrays that are capable of on-demand provisioning. To import storage pools into the catalog, first import an array. Afterwards, volumes may optionally be imported if using the pre-provisioned use model.
If enabled by the checkbox at the bottom of the Summary page, the Import Storage Pool Wizard appears immediately after the array is imported. HP 3PAR StoreServ Storage System virtual domains HP 3PAR Virtual Domain software provides a user-based, restricted access system for managing storage resources. Using virtual domains, a user can be given private control of their storage resources, without the ability to see any other users' resources.
If enabled on the Summary page, the Import Volume Wizard appears immediately after the storage pools are imported. Importing a volume To manage an existing volume, see Managing volumes. Importing existing volumes from a storage pool allows SPM to use those volumes to fulfill storage service requirements. This step is required if you use the pre-provisioned use model. If you use only on-demand provisioning, it is not necessary to import existing volumes.
3. On the Provide Connection Information page, if applicable, enter the management server hostname, port, user name, and password into the appropriate fields. The hostname and port correspond to the location of the network device manager and the login information corresponds to the login for the network device manager. 4. 5. After entering the required information, click Next. On the Import Networks page, select the networks to import from the list and then click Next.
4 Storage service policy SPM allows storage architects to control storage service provisioning policy using templates. Templates dictate the types of requirements that consumers are allowed to or must add to any storage service that is based on the template. Templates can also contain read-only and default requirements that are automatically added to services. Templates can prohibit selected requirements from being specified by storage services.
All Of requirement The All Of requirement is a Requirements Group that contains other requirements. It specifies that all of the requirements contained within it must be satisfied in order for the All Of requirement to be satisfied. NOTE: Top-level service requirements are implicitly contained in an All Of requirement group. Any Of requirement The Any Of requirement is a Requirements Group that contains other requirements.
complete the endpoint specification. It is used to specify Fibre Channel SAN zoning service requirements. Host requirement Host is a Requirements Group that contains the sub-requirements describing access to a storage service for a single Fibre Channel host. Multiple Host requirements can be specified when a volume will be presented to multiple hosts. The Host subrequirements are described below. Each subrequirement is optional. • Host Entry Name —The default name of the host as it appears on the array.
3. 4. hosts specified by the Host requirements. SPM tries to configure the volume host mode, mapping, masking, and SAN zoning to allow the storage to be accessible from the host interfaces specified by the Host requirements. If no Host groups of any kind are specified, matching services are configured to be inaccessible by all hosts (unmasked, unmapped, and unzoned). Having a mixture of Host groups with Pre-presented=TRUE and Pre-presented=FALSE is not supported.
NOTE: In a Matrix OE environment, the policy should always be recycle. Other policies can cause unexpected behavior. Storage Capability requirement The Storage Capability requirement specifies the capabilities that a matching service must be able to perform after it is provisioned, subject to available capacity. If a capability is not specified as required, it is optional whether a provisioned service is able to perform the operation after it is provisioned.
Volume Capacity requirement The Volume Capacity requirement specifies the capacity, or size, of the storage service. The capacity is the storage size as advertised to the server, and may or may not be actually allocated on a storage array depending on whether thin provisioning is used. Volume Committed Capacity requirement The Volume Committed Capacity requirement specifies the percentage of capacity that should be committed or allocated. The remainder of capacity will be thinly provisioned.
5 Storage service provisioning Storage services represent a set of requirements and, when activated, a set of storage resources that meet those requirements. There are three types of storage services: Volume Service, SAN Connected Volume Service, and SAN Connectivity Service. For more information on service types, see: • SAN connected volume service • Volume service • SAN connectivity service NOTE: Matrix OE uses only the SAN connected volume service type.
NOTE: • A nonconformant service does not necessarily indicate that a host will not be able to access the volume. In addition, it does not mean that the volume will not meet actual IT needs. For example, a service could be nonconformant because it is larger than the maximum size set by the administrator. Nonconformance is merely an indication that the storage administrator should be aware of the state of the resources associated with the service and possibly take action to remedy the problem.
8. On the Configure Activation screen, there are three options to activate the service. • Activate now. • Schedule activation for a later time—Enter a specific date and time for the activation of the service. • Do not activate—Activation can be done at a later time from the Storage Services page using the Configure Requirements button. Make a selection and click Finish.
4. Click Finish to complete the process and close the Wizard. Viewing a storage service To view settings of a storage service: 1. In the Navigation tree, select Storage Services. The Storage Services page appears with a list of available storage services. 2. 3. 4. Select a service from the list to bring up the information tabs. Review storage service settings by selecting each tab: Overview, Requirements, Child Services, and Security. To exit, select another destination from the Navigation tree.
Deleting a storage service NOTE: A service in a resourced state cannot be deleted until it is deactivated. To delete a storage service: NOTE: Services created through Matrix OE should not be deleted from SPM. These services should be managed through Matrix OE. 1. 2. Access a specific storage service by following the steps in Viewing a storage service Click Storage Service Actions then select the Delete Service option. The Delete Service verification window appears. 3.
38 Storage service provisioning /> /> /> />
6 Managing storage catalog entities Managing storage catalog entities is the responsibility of the storage administrator and the storage architect. The storage administrator, in general, is responsible for resources such as arrays, storage pools, volumes and networks, and, to some degree, storage services. The roles, security groups and templates are generally owned by the storage architect. Tasks handled by the architect and administrator include adding, modifying, searching, and deleting these entities.
1. In the Navigation tree, select Arrays. The list of arrays appears in the content pane. 2. In the content pane, select the array. The properties for the selected array are displayed. 3. Click the Volumes tab. Information about array volumes that are managed by SPM is displayed. This includes the name of the storage pool containing the volume, tags, the volume capacity, and, optionally, the name of the storage service to which the volume is bound.
NOTE: Capabilities that the array does not support cannot be selected. If an array supports a capability but you would like SPM not to use it, deselect the check box. 1. In the Navigation tree, select Arrays. The list of arrays appears in the content pane. 2. In the content pane, select the array. The properties for the selected array are displayed. 3. Click the Capabilities tab. The current capabilities settings are displayed. 4.
2. Select the array in the content pane, click Array Actions then select the Remove Array option. The Remove Array(s) verification screen appears. 3. Click Remove Array in the dialog box. Managing storage pools To import a storage pool, see Importing a storage pool. Storage pools can be accessed from the Navigation tree under Resources. Viewing and modifying storage pool properties (Overview tab) To view or modify the basic settings of a storage pool: 1. In the Navigation tree, select Storage Pools.
4. To view the access control settings, click Access Control.... The Access Control window appears. 5. 6. To edit the access control settings, click Edit Array, then click Access Control.... Make the necessary changes and click OK. To view effective permissions, click Effective Permissions. The Effective Permissions window appears. When finished, click OK. 7. To edit additional security settings, click Edit Array. The Edit Array window appears. 8. On the Security tab, make any necessary changes.
1. In the Navigation tree, select Resources→Volumes. The list of available volumes appears in the content pane. 2. In the content pane, select the volume. The properties for the selected volume are displayed. 3. Click the Presentations tab. The presentation settings are displayed. NOTE: Select a presentation in the list to view the target ports associated with that presentation. Viewing and modifying volumes security settings (Security tab) To view or modify the security settings of a volume: 1.
Viewing and modifying network settings (Overview tab) The Overview tab displays the basic properties of the network: • Tags—Any tags that the administrator has added to the network. • Management URL—The URL at which the network device manager may be found. • UUID—The persistent unique identifier for the network (typically the Name of the Fabric). • Last Resync—The time at which the network was last resynchronized with the underlying network device manager.
The bottom pane shows additional components which are connected to the network. The name of the component as well as the component type are provided in the list. To view the components connected to a network: 1. In the Navigation tree, select Resources→Networks. The list of available networks appears in the content pane. 2. In the content pane, select the network. The properties for the selected network are displayed. 3. Click the Connected Arrays tab.
8. On the Security tab, make any necessary changes. When all changes are complete, click Apply. If additional changes are required on other tabs, click the appropriate tab. When finished, click OK. Removing a network Networks can be removed from the catalog if they do not contain zones on which a service depends and if they do not contain endpoints on which any resource in SPM depends.
2. Click Create Role. The Create Role dialog box appears. 3. Fill in the required information on each tab of the dialog box (Overview, Privileges, Users and Groups, and Security), then click OK. The new role appears in the Roles content pane. To view, modify, or delete roles, see Managing roles. Grant privileges Privileges are granted to the roles contained within SPM. They are assigned on the Privileges tab.
To view, modify, or delete security groups, see Managing security groups. Grant permissions Permissions are granted to security groups within SPM to allow access control over services, templates, resources, roles, and other security groups. For a list of available permissions, see Table 2 (page 49).
NOTE: The privileges for the Matrix roles have been pre-configured and should not be changed. Viewing and modifying role settings (Overview tab) To view or modify the basic settings of a role: 1. In the Navigation tree, select Administration→Roles. A list of available roles appears in the content pane. 2. In the content pane, select the role. The properties for the selected role are displayed. 3. Click the Overview tab. The basic settings are displayed. 4.
Viewing and modifying role security settings (Security tab) To view or modify the security settings of a role: 1. In the Navigation tree, select Administration→Roles. A list of available roles appears in the content pane. 2. In the content pane, select the role. The properties for the selected role are displayed. 3. Click the Security tab. The security settings are displayed. 4. To view the access control settings, click Access Control.... The Access Control window appears. 5. 6.
1. In the Navigation tree, select Administration→Security Groups. A list of available security groups appears in the content pane. 2. In the content pane, select the security group. The properties for the selected security group are displayed. 3. Click the Overview tab. The basic settings are displayed. 4. To edit these settings, click Security Group Actions then select the Edit Security Group option. The Edit Security Group window appears. 5. On the Overview tab, make any necessary changes.
2. In the content pane, select the security group. The properties for the selected security group are displayed. 3. Click the Effective Permissions tab. The current effective permissions are displayed. 4. Click Select to choose a user, group or role. The Select User, Group or Role dialog box appears. 5. 6. Search for a user, group or role by entering terms in the search box. Select a user, group or role from the corresponding list then click OK.
3. Click Resync All Arrays. The arrays are resynchronized and list of available arrays is displayed. NOTE: • This procedure resynchronizes all resources of the appropriate type when no items are selected. If any items are selected, the action resynchronizes only the selected items. • A single array can be resynchronized by right-clicking on it and selecting the resynchronize menu option.
overwritten at or after service deactivation until archive or aging processes outside of SPM have been done. • Manually set by the administrator—At any time the administrator can set or unset the quarantine state of a resource. This may be useful when performing maintenance or upgrades on a resource to ensure SPM does not attempt to perform automation on the resource during the maintenance window, or at any other time the administrator wants to prevent SPM from performing configuration of a resource.
NOTE: 3. You can skip this screen in the future by selecting the check box at the bottom. Click Next. The Template Properties screen appears. 4. 5. In the Template Properties screen, enter the required information noted by a red asterisk, and any additional properties. Select a service type. A selection of base templates appears. All templates must be based on a base template. 6. 7. Select the appropriate base template.
1. In the Navigation tree, select Storage Services→Templates. The Templates page appears in the content pane. Existing templates and their descriptions are displayed. 2. Select the name of the template to view or edit. The template information screen appears. 3. 4. Review the details and requirements of the template by clicking on the tabs at the top: Overview, Read-Only Requirements, Default Requirements, Requirement Types, Storage Services, Child Templates, and Security.
7 Monitoring the storage catalog Monitoring the storage catalog is primarily the responsibility of the storage administrator. Monitoring inventory levels To monitor the inventory of volume services available: NOTE: Nonconformant refers to items in the list that are resourced, but for which the match between the service request and the storage service is not exact.
model. It can also occur if a user has created a storage service but has chosen not to activate it yet. There are two options for bringing an Unresourced storage service into the Resourced state: • Using normal activation — Use the “Configure Requirements” action on the unresourced storage service to search for a solution and activate the service.
1. From the Navigation tree, click on Storage Services. Look for any storage services with a value of Nonconformant under the Conformance header. NOTE: To see only nonconformant storage services, click the filter icon in the tool bar, then add a filter for Conformant and select No. 2. 3. Click the appropriate nonconformant storage service in the content pane. Click Storage Service Actions and select the Configure Requirements option. The Provision Storage Service Wizard appears. 4. 5.
8 Support and other resources Related documentation The following documents provide related information: • HP Matrix Operating Environment Release Notes • HP Matrix Operating Environment Getting Started Guide • HP Matrix Operating Environment Logical Server Management User Guide • HP Matrix Operating Environment Infrastructure Orchestration User Guide • HP Insight Management Installation and Configuration Guide • Faster storage provisioning in the HP Matrix Operating Environment white paper You
HP websites For additional information, see the following HP websites: • http://www.hp.com • http://www.hp.com/service_locator • http://www.hp.com/support/manuals • http://www.hp.com/support/downloads • http://www.hp.com/go/matrixoe Typographic conventions Table 3 Document conventions Convention Element Blue text: Table 3 (page 62) Cross-reference links and email addresses Blue, underlined text: http://www.hp.
9 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
A Troubleshooting Viewing operational logs SPM maintains an operational log for the storage catalog, listing all operations performed and all error events and an audit log listing all operations and permissions events. All users can review the operational log using the following procedure: 1. Open a browser window and enter https://SPM_Server_Name_or_IP_Address:8000/logs. 2. To view operational logs or audit logs, click the appropriate file name. The file opens.
Required version of Brocade Network Advisor and HP B-Series Network Advisor A supported version of Brocade Network must be installed in order to manage Brocade-based SAN environments. For more information, see “Minimum requirements” (page 12). HP B-Series Network Advisor is available from the following website: http://h18006.www1.hp.com/products/storageworks/dc_fabricmgr/index.
Possible cause–If the directories containing the SPM Storage Module were manually deleted before the un-installer was executed, the un-installer does not complete its task, and subsequent attempts to re-install the SPM Storage Module will fail. Suggested action–The user must delete two registry keys from the Windows registry. Both are found in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\ Uninstall\.
Possible cause 1–The HP 3PAR StoreServ Storage System floating IP is not accessible from the Matrix Central Management Server. Suggested action 1–Ping the HP 3PAR StoreServ Storage System Node address. Verify that the HP 3PAR StoreServ Storage System Node IP Address is accessible from the Matrix Central Management Server. Possible cause 2–SMI-S is not active on the HP 3PAR StoreServ Storage System.
Modifying a catalog storage pool entry and unmasking the volume removes candidates Symptom–When modifying a catalog storage pool entry and unmasking the volume, storage candidates are not displayed in the Candidates drop-down menu in Matrix OE. Possible cause–By default, the “Masked” checkbox is selected and grayed out when you create a SAN Catalog Storage Entry on the Create SAN Storage Pool Entry screen of the Matrix OE visualization.
Possible cause–During on-demand provisioning, when a storage service is deactivated and the volume is deleted on the array, an error may occur that causes SPM to incorrectly mark the array as offline in its catalog. While the array is marked offline, SPM does not perform any provisioning or reconfiguration operations on the array even though the array is functioning properly.
Suggested action–SPM cannot use volumes assigned to hosts sets. To correct this, import and use volumes that are not assigned to host sets. For more information, see “Working with autonomic groups” (page 86). Services provisioned using HP 3PAR StoreServ Storage System may become nonconformant after upgrade to SPM 2.2 Symptom–When SPM is upgraded to 2.2, services connecting VMware hosts to HP 3PAR StoreServ Storage Systems become nonconformant. Suggested action–After the upgrade is complete: 1.
Managed SAN Managed SAN cannot be imported Symptom–Managed SAN import fails. Possible cause–A supported BNA or HP B-Series Network Advisor is not available or configured incorrectly. Suggested action–Verify that asupported BNA or HP B-Series Network Advisor is installed on the server that you are attempting use for SAN management. Verify that the SMI Agent is configured and is running. Suggested action–Ping the SAN Management server to verify that you can communicate with it via TCP/IP.
B Working with Brocade Fibre Channel networks Minimum requirements Brocade Network Advisor or HP B-Series Network Advisor must be installed in order to manage Brocade based SAN environments. For the supported Brocade Network Advisor software packages, see “Minimum requirements” (page 12). NOTE: • Brocade's legacy standalone SMI Agent is not supported by SPM. SPM will only support the SMI Agent installed via HP B-Series Network Advisor/Brocade Network Advisor installation packages as called out above.
instance if (1) all SPM instances import at most one network and (2) all SPM instances import the same network. NOTE: This restriction does not apply to HP B-series/Brocade Network Advisor version 12.0.2.
features. In either case SPM will handle the change automatically, as long as the fabric’s identify as tracked by Brocade’s Network Advisor, remains intact. Any change, regardless if it is a repair or re-configuration, that is severe enough to change the identity of the fabric as tracked by Brocade Network Advisor will require administrator intervention on SPM’s part to recover and will not be automatically handled Zoning policy SPM defaults to using the Single Initiator Zoning (SIZ) policy.
because the SIZ policy is being used, SPM does not check connectivity between the initiators only the initiator to all targets. • If the endpoints as described above can be connected or already are, then only one candidate is returned to signify that 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.
C Working with HP P6000/EVA disk arrays HP P6000/EVA disk arrays have several value-add features. It is important to understand how SPM handles management of environments using those features. The following sections describe these features. Understanding how to import HP P6000/EVA disk arrays into SPM Using the SPM Import Array feature, EVA x400 and P6000 arrays can be imported into SPM. This enables storage pools and volumes on the array to be imported.
properties in SPM or HP P6000 Command View Software. In the P6000/EVA, RAID levels are assigned to each volume. Allocated capacity grows when: • A fully provisioned volume is created, in which case necessary disk space is allocated to the disk group to account for the full size of the volume and RAID overhead. • A thin volume is allocated, a small amount of disk space is allocated to cover administrator space requirements • When a host writes to a thinly provisioned volume.
NOTE: SPM does not automatically create new folders under Host in the HP P6000 Command View Software. However, if the administrator has created host entries under folders, the existing folders and contained hosts are imported into SPM and can be referenced when specifying Fibre Channel host requirements. Refer to HP P6000 Command View Software documentation for more information about hosts and folders.
D Working with HP 3PAR StoreServ Storage Systems Overview HP 3PAR StoreServ 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 HP 3PAR StoreServ Storage Systems into SPM Using the Import Array feature in the SPM GUI, HP 3PAR StoreServ Storage Systems may be imported into SPM.
pools. In HP 3PAR terms, these are called legacy volumes because, from HP 3PAR OS v2.3.1 on, it is recommended to allocate volumes from CPGs (see next section). Concrete pools are not RAID-locked, which means legacy volumes can be assigned any supported RAID level. As explained later, this means SPM must report raw capacity for concrete pools. CPGs are thin pools that are created within the scope of a concrete pool. Intitially, a CPG's capacity is always 0.
SPM capacity value 3PAR calculation (CPG based pools) when a volume gets provisioned in a pool, that much capacity becomes unavailable for other pools). Committed capacity The logical capacity used by the CPG. This includes volumes as well as snapshot and admin space (for example, RAID overhead and cruft). Subscribed capacity Calculated as the sum of all volumes' subscribed capacities. Hence SPM reports logical capacity.
Understanding HP 3PAR StoreServ Storage System virtual domains HP 3PAR Virtual Domain software provides a user-based, restricted access system for managing storage resources. Using virtual domains, a user can be given private control of their storage resources, without the ability to see any other users' resources. Storage resources can be managed and provisioned as necessary. SPM represents HP 3PAR virtual domains in the form of separate "domain arrays”, one for each domain defined on the storage system.
Importing dynamic storage pool If a dynamic storage pool belongs to a virtual domain, it will be imported in its corresponding virtual domain array. If a dynamic storage pool does not belong to a virtual domain, it will be imported into the default array. Importing concrete pools Concrete pools such as all-FC or all-NL do not belong to any virtual domains, so they can only be imported into the default array.
Exposing volume presentations in HP 3PAR StoreServ Storage Systems HP 3PAR StoreServ Storage Systems present a volume in three ways: • Port Present (PP)—exposes a volume to any initiator through one host port on the array. • Host Sees (HS)—exposes a volume to one initiator through any array port. • Matched Set (MS)—exposes a volume to one initiator through one array port.
• For initiators that are already mapped to the volume using MS, SPM deletes all MS presentations and creates new HS presentation(s) that reflects the FC Host requirements of the service request. • For initiators that are already mapped to the volume using HS, SPM keeps the existing HS presentation if LUN numbers match or if a LUN number is not specified in the FC host requirement.
Sample configuration file PAGE 87Volume Migration With Adaptive Optimization And Peer Motion With HP 3PAR StoreServ Storage Systems, volumes may be migrated from tier to tier. Volume migration can be performed manually using the HP 3PAR Management Console or CLI, or it can be automated using licensed software such as Adaptive Optimization and Peer Motion. In either case, SPM must detect the changes and ensure that the catalog is updated to reflect the volume migration.
Deleting CPGs In the event a CPG was deleted, all volumes in the CPG end up being deleted, which is catastrophic as it results in data loss and inability for the application to access their volumes. Fixing this is beyond the scope of SPM, however, the storage administrator should: 1. Re-synchronize the corresponding pool in SPM 2. Re-synchronize all volumes in the pool.
E Working with HP XP/P9000 disk arrays HP XP/P9000 disk arrays have several value-added 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: Supported configurations SPM requires Fibre Channel connectivity to the HP XP/P9000 disk array. Verify that a command device from the HP XP/P9000 disk array is presented to the host running SPM.
All volumes created from a storage pool will inherit the RAID level from the pool. There is no RAID level for thinly provisioned pools.
required (multiple) target ports. When hosts are created by Matrix, the host name will be prefixed with the string “LSM_”. If no host name is specified in the service requirements or if there is a naming conflict with existing host groups, the name will be of the form “SPM_
F Working with unmanaged networks Overview This appendix specifies the usage and format of the XML files used to describe the characteristics of unmanaged storage area networks (SANs) to SPM. Unmanaged SANs are those with which SPM cannot communicate. In order for a user to track connectivity within such SANs using SPM, the characteristics of each SAN are described in an XML file accessed by SPM.
define them. SPM will place the files in the correct directory and will manage the files on behalf of the user. NOTE: Complex unmanaged networks: Files describing zoned networks cannot be edited in SPM. These types of files are under the control of the user, and it is recommended that only those with a thorough understanding of storage networks and XML edit these files. In the Matrix environment, networks are generally complex and therefore not editable within SPM.
Table 5 WWN pattern examples (continued) abcd* AB:CD* Any WWN begining with the sequence AB:CD may be a part of a network containing this pattern. SPM will add colons as necessary when they are not specified. *1:23:4* *1:23:4* Any WWN containing the sequence 1:23:4 may be a part of a network containing this pattern. SPM respects colons specified by the user. *12:34* *12:34* Any WWN containing the sequence 12:34 may be a part of a network containing this pattern.
3. Set the desired tags, security properties, and quarantine policy of the network, and click Next. The Summary screen is displayed. 4. If all is correct in the Summary page, click Finish. The new network is imported into SPM and an XML file representing the network is saved in SPM's state folder. Creating an unmanaged network 1. From the Networks pane, select Import Networks then New Unmanaged FC Storage Network. Click Next. The Provide Connection Information screen is displayed.
2. Enter the Network name and the Fibre Channel Address Patterns for the unmanaged network. Click Next. The Import Networks screen is displayed. 3. Select the unmanaged network just defined and click Next. The Network Properties screen is displayed. 4. Set the desired tags, security properties, and quarantine policy of the network, and click Next. The Summary screen is displayed. 5. If all is correct in the Summary page, click Finish.
Unmanaged network management Once a simple unmanaged network has been created or imported, it can be edited later by selecting the network in the Networks pane, and clicking Edit Nework in the Network Actions menu. You can also right-click the network and select Edit Network from the pop-up menu. Unmanaged networks can also be removed from SPM in the Networks pane. The XML files for networks removed from SPM remain in the SPM state folder, and networks removed from SPM can be re-imported at a later date.
Network names There is one restriction on the editing that may be performed on an unmanaged network XML file. The user may not simultaneously edit the names of more than one network in an unmanaged network XML file (more than one network may exist in a file constructed using the file format for SPM 2.0). If SPM detects that more than one network in an XML file has been renamed, it will mark those networks offline.
XML object model A UML model identifying the structure of the XML objects within an XML file describing an unmanaged network is shown in Figure 4 (page 99). The elements of this model are described in more detail in the following sections. Figure 4 Unmanaged network XML object model Network Network is the root object of an unmanaged network XML file. Only one network may appear in any given XML file. Network objects represent particular unmanaged SANs.
Endpoint Each Network contains a sequence of zero or more network endpoints. These endpoints may or may not also appear in one of the Zones contained by the Network. If an endpoint appears in a Zone contained by a Network, SPM adds that endpoint to the list of endpoints within the network. The endpoints in a Network must not appear in any other network, whether managed or unmanaged. Name Each Network has a name represented as a string. This name will be displayed when the network is imported into SPM.
Kind The Kind element of an Endpoint describes the network type of this connection. It is represented as a value from the NetworkEndpointKind enumerated type. Although the NetworkEndpointKind enumerated type mentions additional network types, SPM supports only Fibre Channel networks. Address The Address of an Endpoint is represented by a string that contains the network address in a format appropriate for the type of network described.
Example unmanaged SAN XML files The following two example XML files represent unmanaged networks. The first example represents a simple network that can be edited within SPM. The second example represents a slightly more complex network that cannot be edited within SPM. More complex networks will contain additional elements. An example can also be found in the folder \plugins\unmanaged_san\example.xml.
G Working with unmanaged arrays Overview This appendix specifies the format of the XML files used to describe the characteristics of unmanaged storage arrays to SPM. Unmanaged storage arrays are storage arrays with which SPM cannot communicate. In order for a user of SPM to track storage allocated within such arrays using SPM, the characteristics of the arrays are described in XML files which SPM reads. SPM enables users to manage allocation of storage in a number of storage arrays.
be unique across all Unmanaged Array XML files to be loaded in an instance of SPM. If there is a conflict, the file containing the second instance of the conflicting ObjectID will be ignored. Volumes defined within an Unmanaged Array XML file are required to have a UUID identifier used by SPM or its clients to identify unique resources. Arrays and Pools may have UUIDs, but UUIDs are not required for these objects. UUIDs should not be reused within an instance of SPM.
Figure 5 Unmanaged storage array XML object model Entity All objects in this model derive from the Entity class, and therefore they all have an ObjectID. An ObjectID is a string that contains a unique identifier. ObjectIDs must be unique across all XML files to be loaded by SPM. If there is a conflict, the second file containing the conflicting ObjectID will be ignored. ObjectIDs are optional except when an object must be referenced from another object in an XML file.
Property Type Description RAIDMap Sequence of MapItem objects Zero or more MapItem objects mapping device specific RAID identifiers to SPM specific RAID identifiers. MinimumLUNProvisionable Int The minimum logical unit number that can be provisioned by arrays within this definition. This is optional, and defaults to 0. MaximumLUNProvisionable Int The maximum logical unit number that can be provisioned by arrays within this definition. This is optional, and defaults to 1024.
an empty sequence of StorageArray objects, such a case is ignored by SPM. To be meaningful, a StorageArrayDefinition should contain at least one StorageArray object. Each StorageArray object represents one instance of the type of storage array described by the StorageArrayDefinition. Resource Resource objects inherit from the Entity class, and define the UUID, DisplayName, ManagementURL, and Tags attribute.
Property Type Description Tags Sequence of String User-specified tags for this storage array. ProductName String The array product model name. Pools Sequence of StoragePool Storage pools within this storage array. Ports Sequence of StorageArrayPort Ports provided by this storage array. HostEntries Sequence of StorageArrayHostEntry A list of host ports served by this storage array. ProductName Each storage array has a product name, which is a string value.
Property Type Description PhysicalCapacity long The raw physical capacity of the storage pool. RaidLevel String The RAID level of the storage array. DeviceRaidSpecificAvailableCapacity Sequence of MapItem Association between RAID levels and the amount of logical free space when using that RAID level. Volumes Volumes contained within this storage pool. Sequence of Volume SubscribedCapacity The SubscribedCapacity of a StoragePool is represented by a long integer.
Property Type Description DisplayName String Name used to display this resource. ManagementURL String URL for the management interface for this resource. Tags Sequence of String List of user-specified tags for this resource. Capacity long The raw capacity of the volume. CommittedCapacity long The raw committed capacity of the volume. RaidLevel String The RAID level of the volume. Presentations Sequence of VolumePresentation Associations between storage array ports and host ports.
Access The access to be granted to this volume, stored as a string. The value must be one of the following literals: NoAccess, ReadOnly, or ReadWrite. LUN The LUN is the logical unit number that the host will use to represent the volume the storage array is presenting to that host. InitiatorObjectID The InitiatorObjectID is a string representing the ObjectID of a host that has been granted access to this volume.
StorageArrayPort A StorageArrayPort represents a local port on the storage array containing this object. This type inherits from the NetworkEndpoint type. Property Type Description ObjectID String Required object unique identifier. Address String The network address of the network end point. Kind UnmanagedNetworkEndpointKind A literal describing the type of network. Name String The name of this storage array port.
Property Type Description InitiatorName String The name of this initiator. For Fibre Channel, this must be identical to the Address of the HostEndpoint contained within the HostEndpoints field.. HostEndpoints Sequence of HostEndpoint A list of HostEndpoint items for this initiator. For Fibre Channel, there should be only one. ProtocolKind This field indicates the storage protocol in use by this initiator.
Changing an unmanaged array to a managed array Sites that perform an upgrade from SPM 1.x to SPM 2.x may end up with an unmanaged array representing some of their storage resources. If this cannot be resolved by performing the upgrade a second time, it may be necessary to manually transition these storage resources from an unmanaged array to a managed array. Alternately, sites that have chosen to represent some arrays as unmanaged arrays may decide to make them managed at a later date.
ManagementURL fields provided in the XML file will be displayed as active links in the SPM GUI. The examples provided here are constructed for illustrative purposes. The correct URL structure for the array represented by the XML file should be inserted as appropriate.
RL5 Presentation-1 ReadWrite 0 Object-1 Object-2 Object-3 The second volume contains a presentation that is not present in the first volume.
Object-1 FibreChannel 00:00:00:00:00:00:02:23 Object-7 00:00:00:00:00:00:02:23 FibreChannel This storage array contains a single host entry, indicating that it currently only serves a single host.
H Units of measurement Storage is reported in bytes. There are three ways that storage vendors' management software reports storage capacity: binary units, decimal units, and binary with decimal units. Binary units have been proposed by the International Electrotechnical Commission (IEC) and adopted by the United States National Institute of Standards and Technology (NIST). Decimal units are part of the International System of units (SI).
I Additional tools This appendix provides information on tools available for use with SPM. SPM rezoning script If the port group chosen by SPM or specified by a port group requirement must be changed, a number of manual steps must be performed. To simplify this process, a Windows PowerShell script (SPMRezone.ps1) is provided to manage rezoning automatically.
treated as if all ports on the array are in a single group. These default groups are not named and cannot be specified in a port group requirement. • SPM can limit target port zoning by defining port groups for an array. When SPM provisions a new SAN Connected Volume (SCV) service presenting a volume on an array to an initiator using the automated zoning functionality, SPM creates a zone to connect the initiator to the array.
Table 6 (page 121) lists the parameters used with the SPMRezone.ps1 script. The port group and array name parameters are optional. If no port group is specified, SPM will use the least-used port algorithm to choose a new port group. Table 6 Rezoning script parameters Parameter Description -Port The tcp port number to use. The default is 8000. -Login A valid login name. If not included, the script prompts for a login name. -Password A valid password.
Glossary A application A client of a storage system, or a consumer of a storage service. array A physical storage device or an aggregate set of devices containing one or more storage pools that serves storage to clients and provides an application programming interface or a management console to allow an administrator to manage the storage provided by the device.
HP Storage Provisioning Manager SPM, the software application described in this document. I initiator An endpoint that consumes storage through a storage area network. These storage consumers initiate storage actions. L logical disk A partition or logical disk that may contain a file system or database or be used by a volume manager or hypervisor to present higher order volumes.
striping, which involves partitioning each drive's storage space into units. By placing data on multiple disks, I/O operations can overlap in a balanced way, improving performance. resource A storage catalog entity representing a storage resource. A resource provides a set of services. resourced Within SPM, a service is resourced if it has been activated and thus has been assigned resources.
V volume A logical drive provided by a storage pool that can be presented to a host system. volume service A type of service supported by SPM. It consists of a service providing a block based volume abstraction. All services are provided by resources. A volume service is provided by an array. W white list Within SPM, a white list is a list of target ports for a particular storage system that SPM is allowed to use.
Index A Adaptive Optimization, 87 array deleting, 41 managing, 39 B backup and restore, 21 BNA Historical Data Collection performance issues, 72 Brocade Fibre Channel networks, 72 configuring SPM to communicate with SANs, 72 Historical Data Collection performance, 72 managed networks, 73 minimum requirements, 72 C configuring SPM to communicate with SANs, 72 conventions document, 62 text symbols, 62 CPG deleting, 88 renaming, 87 customizing data size format, 20 customizing display columns, 20 D data size
N Nonconforming request, 58 O operational log, 64 P P6000/EVA storage systems backup and restore on, 78 capacity reporting, 76 creating hosts on, 77 host modes, 77 presentation, mapping, and masking, 77 Peer Motion, 87 permissions, 49 permissions settings, 49 post group configuration, 37 proxy WWNs, 98 R related documentation, 61 request nonconforming, 58 requirement types All Of, 28 Any Of, 28 Connected To Fibre Channel Endpoint, 28 Connected To Network, 28 Fibre Channel Initiator Endpoint, 28 Fibre Cha
names, 98 Network object, 99 NetworkEndpointKind object, 101 proxy WWNs, 98 simple, 92 WWN patterns, 93 XML file example, 102 XML file lifecycle, 97 XML object model, 99 Zone object, 100 ZoningState object, 101 unmanaged SANs see unmanaged networks upgrading from SPM v1.x, 15 upgrading from SPM v2.