HP Storage Provisioning Manager (SPM) Version 2.1 User Guide Abstract This guide provides information to successfully install, configure and manage HP Storage Provisioning Manager (SPM).
© Copyright 2010 - 2012 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...............................................................................................9 Data storage and SPM..............................................................................................................9 SPM environment......................................................................................................................9 Minimum requirements.........................................................................................................
Volume Capacity requirement..............................................................................................30 Volume Committed Capacity requirement..............................................................................30 Volume Creation Security Group requirement.........................................................................30 5 Storage service provisioning......................................................................31 Provisioning a storage service..................
Deleting a security group...............................................................................................49 Resynchronizing resources........................................................................................................49 Quarantining resources...........................................................................................................50 7 Monitoring the storage catalog..................................................................
Configuring SPM to communicate with SANs..............................................................................63 Importing a network................................................................................................................63 Managing networks................................................................................................................63 Connectivity services........................................................................................................
WWN patterns.............................................................................................................78 Creating an unmanaged network....................................................................................79 Importing an existing unmanaged network.......................................................................80 Unmanaged network management..................................................................................81 XML file lifecycle............................
ProductName...............................................................................................................92 Pools...........................................................................................................................92 Ports............................................................................................................................92 HostEntries.................................................................................................................
1 Introduction Data storage and SPM HP Storage Provisioning Manager (SPM) is a software tool that manages storage provisioning within the HP Matrix Operating Environment (Matrix OE). It provides a secure service-centric management interface to storage, enabling storage services to be resourced with available storage from the SPM catalog, and securely automating storage management tasks by interfacing directly with storage arrays and storage area networks.
Figure 1 Understanding the SPM environment The HP Matrix OE infrastructure orchestration capability works with SPM to provide storage services into that environment and automate several operations related to that storage. SPM has built in support for many arrays (HP EVA/P6000, HP 3PAR Storage Systems, and HP XP/P9500) as well as Brocade and HP fabric management software. For more information, see Minimum requirements.
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. Minimum requirements SPM supports the following managed storage systems: Storage System Model Firmware 3PAR F200, 3PAR F400, 3PAR T400, 3PAR T800 InFormOS 3.1.
is to request storage from SPM. The primary tasks, the associated roles, and the order in which tasks are performed are as follows: NOTE: For an explanation of the use models, see Data storage and SPM. NOTE: In addition to these roles, the following roles are defined in order to facilitate use of SPM with Matrix OE: Matrix Architect, Matrix Administrator, Matrix Service and Matrix User. 1. 2. 3. The storage administrator first configures the catalog and imports storage resources into the catalog.
Figure 2 Interaction between user roles NOTE: Although separate roles are listed, an organization may have one person perform multiple roles, or multiple people performing the same role. For example, a storage array management team and a SAN management team may each have a person acting as storage architect. The initial order of operations remains the same no matter who performs them. Roles can be customized to fit the specific needs of the organization and environment.
The Storage Services section of the Dashboard contains two tabs: Summary and Templates. The Summary tab provides basic information about current storage services, including Resourced, Unresourced and In Transition services. The Templates tab provides information on the quantity of each template being used. The Capacity section of the Dashboard provides details on the storage capacity being monitored by the SPM.
2 Getting started with SPM Installing SPM SPM is installed as part of the HP Matrix OE solution. You must have Microsoft® .NET 4.0 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.1 installation, if an SPM 1.x catalog exists, SPM attempts to automatically convert it to an SPM 2.1 catalog.
Importing XP arrays as managed arrays during an upgrade XP arrays can be imported as managed arrays when performing an upgrade by creating a credentials file named SMPCredentials.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.
Installation and configuration of HP Matrix OE, EVA storage systems, 3PAR Storage Systems, Brocade Network Advisor, and XP Storage Systems is beyond the scope of this document. NOTE: This information does not apply to unmanaged arrays or SANs. See Working with unmanaged arrays or Working with unmanaged networks for more information. If any other issues occur, refer to Troubleshooting for more information.
The goal is to resynchronize the state of the SPM catalog with the state of the storage services and volumes being managed. When SPM has populated the “Signature State” field of each volume, SPM switches to Manual Recovery mode. The user should take appropriate action based on the Signature State of each volume, which is found in SPM's volume list. The possible “Signature State” values of volumes imported into SPM after internal recovery is complete, and actions the user may choose to take are listed below.
Volumes to those services. For information on this process, see Manually assigning a volume to a storage service. When restoring from backup, SPM puts all volumes into quarantine, and the user must manually take them out of quarantine as appropriate. If the management signature is not present, is corrupt, or has changed since recovery, the user should manually inspect the volume to ensure it is safe to bring out of the quarantine state.
3 Importing storage into the storage catalog Only storage and networks imported into the catalog can be used to fulfill storage service requirements, with the exception of 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.
Importing a storage pool SPM supports arrays that use storage pools to segregate sections of disk storage. This can be useful when Matrix/SPM are only to use a portion of an array, or different permissions will be used for different portions of an array. The array management interface can be used to create the storage pools, and SPM should only be made aware of those storage pools which it is allowed to use.
2. 3. 4. On the Choose Storage Pools page, select the storage pools from which to import volumes and then click Next. On the Import Volumes page, select the volumes to import into the SPM catalog. On the Volume Properties page, type tag names and a select security group to be assigned to the imported volumes. To enter tags, type the tag name and click the + icon. When complete, click Next. NOTE: OE. 5.
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 have the ability to prohibit selected requirements from being specified by storage services.
2. Click Create Template on the bottom right. (Alternatively, right click on Templates under Storage Services and click Create Template.) The Create Template Wizard appears with some basic guidelines. NOTE: 3. This screen may be skipped in the future by selecting the checkbox at the bottom. Click Next. The Template Properties screen appears. 4. 5. Fill in the required information noted by a red asterisk, and any additional properties. Select a service type A selection of base templates appears.
View/edit/delete templates Once templates are created, a summary of their requirements and other details can be viewed or edited from the Dashboard. To view template details: 1. In the Navigation tree select Templates under Storage Services. The Templates page appears in the content pane. Any existing templates and their descriptions are visible. 2. Select the name of the template to view or edit. The template information screen appears. 3. 4.
Volume service The volume service provides a single volume from a storage array. SAN connectivity service The SAN connectivity service configures connectivity between endpoints in a SAN. Requirement types Service requirements are a specification of a property, behavior, or policy describing a goal state to which a service or the service resources are managed to conform.
Fibre Channel Initiator Endpoint requirement Fibre Channel Initiator Endpoint is a Requirements Group containing requirements describing a single Fibre Channel initiator endpoint of a host that is to access the storage service. The Fibre Channel Initiator Endpoint sub-requirements are described below: • Fibre Channel Endpoint WWN — Interface WWN • Fibre Channel Network — Network to which the initiator WWN is or will be logged into.
• Volume Access — Storage must be presented with access rights. When unspecified, Read-write is assumed. • Fibre Channel Initiator Endpoint — Storage must be presented to each host initiator endpoint specified (multiple may be specified to describe multiple endpoints per host) • Pre-presented — Causes the Host requirement group to only match against pre-presented storage rather than configuring presentation on matching storage.
Service Deactivation Policy requirement The Service Deactivation Policy requirement specifies the actions to be taken on deactivating the service. The available policies are: • No Action — On service deactivation, nothing is performed. All SAN zoning, volume data, and volume presentation are left as it was. Note that the server consuming the storage is still be able to access it after the service is deleted.
Storage Pool Subscription Ratio requirement The Storage Pool Subscription Ratio requirement specifies the ratio of subscribed capacity of a pool to its physical capacity which must exist in order to create or grow a volume within the pool. Because it is expressed as a ratio of the pool subscribed capacity, a value of “1” means no oversubscription is performed. A value of “2” means that new volumes are created in the pool up to twice the physical capacity of the pool. A value of “3” means triple, etc.
5 Storage service provisioning Storage services represent a set of requirements and, once 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: • Volume service • SAN connected volume service • SAN connectivity service NOTE: Matrix OE uses only the SAN connected volume service type.
NOTE: If there is a problem activating a service, it is still moved into the resourced state because the resources are committed to the service. The error will likely be reflected by the service being in a nonconformant state. Provisioning a storage service Storage services may be provisioned manually using the SPM GUI, or they can be provisioned automatically from Matrix OE (e.g.
5. On the Choose Solution screen, select a solution from the list provided. Toggle the view from List View to Table View using the selection buttons to the right of the search box. NOTE: If no solutions are provided to choose, then either the appropriate resource objects are not present in SPM or the requirements might conflict in some way that eliminates any viable candidates. The service requirements may also be changed on this screen.
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. Editing the configuration of a storage service To change the configuration (activation/reactivation, requirements, solution) of a storage service: NOTE: Services created through Matrix OE should not be edited from SPM.
2. Click Delete Service at the bottom of the storage service information screen. The Delete Service verification window appears. 3. Click Delete Service to delete or click Cancel if the user did not intend to delete the service. The Storage Services information screen appears.
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.
Viewing array ports (Ports tab) To view the ports of an array: 1. In the Navigation tree, select Arrays. The list of arrays appears in the content pane. 2. From the content pane, select the appropriate array. The properties for the selected array are displayed. 3. Click the Ports tab. Ports information is displayed, including the port address, name, and network. Viewing array targets (Targets tab) To view the targets of an array: 1. In the Navigation tree, select Arrays.
5. On the Capabilities 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. Viewing and modifying array security settings (Security tab) To view or modify the security settings of an array: 1. In the Navigation tree, select Arrays. The list of arrays appears in the content pane. 2. From the content pane, select the appropriate array.
2. From the content pane, select the appropriate storage pool. The properties for the selected storage pool are displayed. 3. Click the Overview tab. The basic settings are displayed, including the status and other identifying information. 4. To edit these settings, click Edit Storage Pool. The Edit Storage Pool window appears. 5. On the Overview tab, make any necessary changes. When all changes are complete, click Apply. If additional changes are required on other tabs, click the appropriate tab.
1. In the Navigation tree, select Storage Pools. The list of available storage pools appears in the content pane. 2. Select the appropriate storage pool from the content pane, then click Remove Storage Pool at the bottom of the screen. (Alternatively, right-click the storage pool in the content pane and select Remove Storage Pool.) The Remove Storage Pool verification screen appears. 3. Click Remove Storage Pool in the dialog box.
3. Click the Security tab. The current security settings are displayed. 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 Volume.
option Unknown is a bad state that requires the reconfiguration of the networking switches involved. This state is unusual but can sometimes occur on the underlying switches on the network as a result of incorrect configurations on part of the storage administrator when the network was originally configured and is not controlled by SPM. NOTE: For unmanaged networks, SPM uses the content of the unmanaged network XML file to determine the state of the network.
3. Click the Capabilities tab. The capability settings are displayed. 4. To edit these settings, click Edit Network. The Edit Network window appears. 5. On the Capabilities 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. Viewing and modifying network security settings (Security tab) To view or modify the security settings of a network: 1.
Managing security The SPM storage catalog contains all the entities—every service template, storage service, array, storage pool, volume, network, role, security group—the user adds to the catalog. Create security roles A set of default security roles is included with SPM that handle simple scenarios. This set can be changed or extended as desired.
Create security groups As part of the default security configuration, a Root Security Group (parent) and Consumer Group (child) are setup within the Security Groups content pane. The user is free to use, change or extend this set as desired. NOTE: Use the pre-defined Matrix OE security group to make resources (arrays, pools, volumes, networks, templates) available to Matrix OE. Security group creation is handled in the Security Groups section of Administration. 1.
Table 2 Permissions (continued) Access right Description Delete Resource Remove resources from the catalog Create Role Create new roles View Role View roles Modify Role Modify the properties of roles Delete Role Delete roles Create Security Group Create new security groups View Security Group View security groups Modify Security Group Modify the properties of security groups Delete Security Group Delete security groups Modify Security Modify item security group and access rights Take O
4. To edit these settings, click Edit Role. The Edit Role window appears. 5. On the Privileges 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. For additional information see Grant privileges. Viewing and modifying role users and groups (Users and Groups tab) To view or modify the users and groups assigned to a role: 1.
1. In the Navigation tree, select Roles under the Administration section. The list of available roles appears in the content pane. 2. From the content pane, select the appropriate role. The properties for the selected role are displayed. 3. Click Delete Role at the bottom of the window. (Alternatively, right-click the role and select Delete Role.) The Delete Role verification dialog box appears. 4. Click Delete Role in the verification box.
Viewing security group objects (Objects tab) To view the objects in a security group: 1. In the Navigation tree, select Security Groups under the Administration heading. The list of available security groups appears in the content pane. 2. From the content pane, select the appropriate security group. The properties for the selected security group are displayed. 3. Click the Objects tab. The objects in the security group are displayed. 4. Clicking on each object provides more detailed information.
1. In the Navigation tree, select Arrays. The list of arrays appears in the content pane. 2. In the bottom right-hand corner, click Resync All Arrays. The Resync All Arrays confirmation window appears. 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.
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 which are resourced, but for which the match between the service request and the storage service is not exact.
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. • Manually assigning a volume — Use the “Manually Assign Volume” action to directly assign an existing volume to the storage service, regardless of whether or not it fully meets the storage service requirements.
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 Configure Requirements at the bottom of the screen. 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 7.1 Release Notes • HP Matrix Operating Environment 7.1 Getting Started Guide • HP Matrix Operating Environment 7.1 Logical Server Management User Guide • HP Matrix Operating Environment 7.1 Infrastructure Orchestration User Guide • HP Insight Management 7.
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 55) Cross-reference links and email addresses Blue, underlined text: http://www.hp.
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.
Issues with multiple SPM servers managing the same volumes Symptom–Changes from one SPM server overwrite changes made on another SPM server. Possible cause–Both SPM servers are attempting to manage the same volumes. Suggested action–Verify that each SPM server is managing distinct volume resources. Do not attempt to manage the same volume resources with two or more SPM servers. Two SPM servers may manage the same arrays or pools.
running SPM. The command device may be checked using the p9000info/xpinfo tool available at the following location: http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp? lang=en=us=329290=5202488=5158164=1110=13=2=135=co-94081-2=18964=4309961 Using this tool should show the type of the CU/LDEV as OPEN-V-CM.
SPM may mark an array offline when a volume is deleted during on-demand provisioning Symptom–An array is incorrectly marked offline. 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.
Non-Brocade SAN environments must have unmanaged networks in SPM Storage administrators must provide SPM with information regarding SAN connectivity. In addition, for non-Brocade SAN environments, an unmanaged network must be created to communicate the SAN configuration to SPM as described in the HP Insight Management Installation and Configuration Guide at www.hp.com/go/matrixoe/docs. It may also be necessary to manually enter proxy WWNs. For more information, see “Proxy WWNs” (page 82).
Firmware for 3PAR storage systems 3PAR storage systems must have InForm OS 3.1.1 MU1 or higher installed in order to work properly with SPM. SPM does not allow 3PAR arrays with earlier versions to be imported into the SPM catalog. No matching candidates found Symptom–Requirements do not match the available catalog resources. Suggested action–Verify that the Matrix storage requirements are correct. Also verify available SPM catalog entries meet the requirements from Matrix.
1. 2. 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. 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.
B Working with Brocade Fibre Channel networks Minimum requirements Brocade Network Advisor 11.1.3 or HP B-Series Network Advisor 11.1.3 must be installed in order to manage Brocade based SAN environments. Refer to release notes for the complete supported device list. SAN Management Software Brocade Switch FOS/M-EOSc version HP B-Series Network Advisor 11.1.3 (Enterprise, Professional Plus, or SMI Agent Only) options FOS v5.0.x, v5.1.x, v5.2.x, v5.3.x, v6.0.x. v6.1.x, v6.2.x, v6.3.x, v6.4.x, v7.0.
Networks with a Zoning State of Zoned and Capability of Automated Zoning have zoning automated by SPM. SPM actively modifies the underlying networks to create/destroy zones dynamically depending on the needs of the users and the constraints set in place by the storage administrator. NOTE: • If a BNA user's zoning session overlaps with an SPM zoning session for the same fabric, then SPM's changes will fail and will be automatically retried by SPM.
Zone destruction Zones are destroyed when all Connectivity Services that depended on it are deactivated/removed. This only applies to SPM-created zones. Pre-existing zones are not affected. In either case, the zone is removed from SPM's storage catalog and is no longer visible in the GUI.
C Working with EVA storage systems HP P6000 EVA 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 EVA 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.
Understanding EVA Storage System presentation, mapping, and masking EVA 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.
D Working with 3PAR storage systems Overview 3PAR 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 3PAR arrays into SPM Using the Import Array feature in the SPM GUI, 3PAR arrays may be imported into SPM. This in turn allows storage pools and volumes on the array to be imported.
The sum of all concrete pools' capacity represents the raw capacity of the entire 3PAR system. 3PAR volumes (a.k.a. virtual volumes) can be allocated directly from concrete pools. In 3PAR terms, these are called legacy volumes because, from 3PAR InformOS v2.3.1 on, it is recommended to allocate volumes from CPG (see next section). Concrete pools are not RAID-locked, which means legacy volumes can be assigned any supported RAID level.
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.
IMPORTANT: SPM does not currently support virtual domains. When importing a 3PAR Storage System, select only users that have permission level super and belong to the All virtual domain. If after importing the 3PAR Storage System, a storage administrator moves hosts to a specific virtual domain using the 3PAR CLI and/or Graphical User Interface, subsequent automation in SPM might fail. For more information on virtual domains, refer to the storage system user guide.
Creating hosts on a 3PAR 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 will generally use the host name given in the requirements. If no host name is specified, the host name will be “SPM_” followed by the WWN of the initiator. Host names that begin with "LSM_" are provided to SPM by Matrix OE.
1. When the storage administrator manually re-syncs a volume, SPM will verify that the parent pool has not changed. If it has, SPM will either: a. Move the volume under the new pool if that pool is managed by SPM. b. Put the volume offline if the new pool is not managed by SPM. 2. During volume discovery for a given pool: SPM will detect volumes already managed by the catalog that were moved to or from the pool and re-syncs those volumes, thus falling back into case (1) above. 3.
E Working with HP P9000/XP Disk Array HP P9000/XP 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 P9000/XP array. Verify that a command device from the P9000/XP array is presented to the host running SPM.
Understanding P9000/XP disk array presentation, mapping, and masking In the HP P9000/XP disk array, volumes are presented through FC host ports, which SPM calls target ports, and host groups. A host group is a collection of initiator endpoints. Each initiator endpoint is a represented as a WWN. A host group is used to explicitly define a mapping and masking relationship between a specific volume and initiators included in the host group. Hierarchically, host groups are defined under array target ports.
Array model XP12000/10000 Maximum length supported in SPM 16 characters Default host group name if conflict encountered SPM * — Requires XP24000/20000 array running firmware version 60-08-XX or later to support 32 characters. Otherwise, host group names are limited to 16 characters. Backup and restore handling on XP volumes SPM does not offer full support for backup and restore of XP volumes by writing a management signature string to XP volumes managed by 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 is described in an XML file accessed by SPM.
one or more patterns consisting of a partial WWN and one or more asterisks used as wild cards within the partial WWN. For example, a network consisting of WWNs beginning with A or B would be described by two patterns, ‘A*' and ‘B*'. A network intended to claim all WWNs can be described by the pattern ‘*'. XML files generated by SPM may be edited outside SPM, but if such a file is edited to describe a zoned network, the file will no longer be editable within SPM.
Table 4 WWN pattern examples (continued) *12:34* *12:34* Any WWN containing the sequence 12:34 may be a part of a network containing this pattern. SPM respects colons specified by the user. 12::34* Error If a user specifies consecutive colons, SPM regards this as an improper pattern. 1:23:4* Error If a user specifies colons in a way that does not put two hexadecimal characters in each grouping, SPM regards this as an improper pattern.
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. The new network is imported into SPM and an XML file representing the network is saved in SPM's state folder. Importing an existing unmanaged network 1. 80 Select Import Networks from the Networks Pane.
2. Select the desired unmanaged network from the Import Networks screen, and complete the import performing the same steps used for a new unmanaged network. Unmanaged network management Once an unmanaged network has been created or imported, it can be edited later by selecting the network and selecting Edit Network in the Networks pane. Unmanaged networks can also be removed from SPM within the Networks pane.
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.
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. A Network with a ZoningState of Open may not contain any zones.
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. Within a NetworkResource, each Network must have a unique Name. Network names are case sensitive. ZoningState Each Network has a ZoningState, which is of the enumerated type ZoningState. The values involved may be Open or Zoned.
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. FibreChannel endpoint addresses are represented by their World Wide Name (WWN) in canonical form. These addresses are not case sensitive. ZoningState ZoningState is an enumerated type representing the state of a zone. It has two possible values: Open, and Zoned. A network may be in the Open state only if it has no zones.
FC network example without patterns
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 2.1. 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 2.1 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.
StorageArrayDefinition A StorageArrayDefinition is the root object within an unmanaged array XML file. Each such file must contain exactly one StorageArrayDefinition object. These objects define a class of storage arrays, and may define several instances of the class. Property Type Description ObjectID String Required unique object identifier. HostmodeMap Sequence of MapItem objects Zero or more MapItem objects, mapping HostMode values to array host modes.
“Unsupported” may be placed in the Value element of a MapItem to indicate that the RAID level indicated in the Index element of that MapItem is not supported by the StorageArray. RAIDLevel NoRAID, RAID0, RAID1, RAID1+0, RAID3, RAID4, RAID5 RAID5+0, RAID6, RAID6+0 Arrays The Arrays element of a StorageArrayDefinition contains a sequence of zero or more StorageArray objects. StorageArray objects are described in StorageArray.
ManagementURL, and Tags elements from the Resource class. See Resource for further discussion of these elements. Property Type Description ObjectID String Required unique object identifier. UUID String Unique resource identifier. DisplayName String Name displayed by SPM for this storage array. ManagementURL String URL for the management interface for this storage array. Tags Sequence of String User-specified tags for this storage array. ProductName String The array product model name.
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. SubscribedCapacity long The raw capacity of the storage pool already subscribed. CommittedCapacity long The raw capacity of the storage pool already committed. PhysicalCapacity long The raw physical capacity of the storage pool.
Volume Each Volume object represents a volume within a StoragePool. Like the StorageArray object, it inherits the DisplayName, ManagementURL, and Tags elements from the Resource class. See Resource for discussion of those elements. Property Type Description ObjectID String Required object unique identifier. UUID String Required unique resource identifier. DisplayName String Name used to display this resource. ManagementURL String URL for the management interface for this resource.
Property Type Description LUN Integer The logical unit number used by the host to represent this volume. InitiatorObjectID String The ObjectID of the initiator that has access to this volume. TargetPortObjectIDs Sequence of String The ObjectIDs of the array ports through which the host can access the volume. 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.
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.
between the indices of the objects and the values. Such lists appear in the RAIDMap and HostmodeMap fields of the StorageArrayDefinition. Property Type Description Index String The search key in the associative list. Value String The value associated with the search key. Example of an unmanaged array XML file Following is an 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.
P-1000 The following begins a list of storage arrays. In this example, it contains a single storage array, with UUID “UnMan-1”. This storage array has the specified display name, management URL, and product name. The tags “Secure” and “Leased” are applied to this storage array. ObjectIDs for resources may or may not be the same as their UUIDs. UUIDs are optional for Arrays and Pools, but required for Volumes.
The second volume contains a presentation that is not present in the first volume. This presentation specifies that the host called “Object-1” will be presented read/write access to the two ports called “Object-2” and “Object-3” from this storage array, and that it will use logical unit number zero to represent this volume.
This storage array contains a single host entry, indicating that it currently only serves a single host. The host entry contains a single initiator, which contains a single Hostendpoint. The host Fibre Channel address is specified. This StorageArray Definition is simplified to illustrate the nature of an Unmanaged Array XML file.
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).
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. BNA Brocade Network Advisor C catalog The repository of service requests, services, service groups, and resources managed by SPM.
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.
roles, security Within SPM, a security role is a set of constraints on access to resources and functions within the system that may be applied to one or more users of the system. S SAN Storage Area Network, usually referring to Fibre Channel technology in practice. server In this document, a server refers to either an application server or a storage server. service request A service request is the set of requirements sent to SPM which describes the type and amount of storage preferred.
W WWN World Wide Name. A unique 8-byte address used in a Fibre Channel storage network to identify each array and initiator. SPM uses the format xx:xx:xx:xx:xx:xx:xx:xx:xx to display these values. Z zone Within a Fibre Channel Storage Area Network, a zone is a subset of the endpoints on a network. Endpoints may only communicate with other endpoints that are in the same zone. Endpoints may be in multiple zones. zoned network FC networks that have zones are said to be zoned.
Index Symbols R 3PAR Storage Systems, 68, 70, 71, 72 related documentation, 54 request nonconforming, 51 A array deleting, 38 managing, 36 C conventions document, 55 text symbols, 55 D data size format, 14 display columns, 14 document conventions, 55 documentation HP website, 54 providing feedback, 55 related, 54 S security catalog, 17 security groups creating, 45 managing, 48 storage pool importing, 21 Subscriber's Choice, HP, 54 symbols in text, 55 T technical support HP, 54 service locator websit
