HP Storage Provisioning Manager (SPM) Version 2.0 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.........................................................................................................
5 Storage service provisioning......................................................................28 Provisioning a storage service..................................................................................................29 Manually assigning a volume to a storage service.......................................................................30 Viewing a storage service........................................................................................................
7 Monitoring the storage catalog..................................................................49 Monitoring inventory levels......................................................................................................49 Monitoring and managing jobs................................................................................................49 Responding to storage services.................................................................................................
D Working with 3PAR storage systems............................................................63 Overview..............................................................................................................................63 Understanding how to import 3PAR arrays into SPM....................................................................63 Understanding 3PAR capacity reporting....................................................................................63 Storage pool capacity.............
Address.......................................................................................................................76 ZoningState......................................................................................................................76 NetworkEndpointKind........................................................................................................77 Example unmanaged SAN xml.................................................................................................
Name..........................................................................................................................86 Hostmode....................................................................................................................86 HostEndpoints...............................................................................................................86 MapItem..........................................................................................................................
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 Required Management Software 3PAR F200, 3PAR F400, 3PAR T400, 3PAR T800 InFormOS 2.3.1 MU5, InFormOS 3.1.
1. 2. 3. The storage administrator first configures the catalog and imports storage resources into the catalog. See Importing storage into the storage catalog. The storage architect creates storage service templates. HP Matrix Operating Environment allows a consumer (e.g. a server administrator) to create SPM storage service requests. HP Matrix OE communicates with SPM to find storage resources that match the requirements in that request and presents that storage to the administrator for use.
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 would 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.
6. 7. 8. To change the order in which the columns are displayed, highlight a column title and use the up and down arrow buttons (located below the Enabled Columns list) to move it to the preferred location. Repeat this procedure for each of the preferred columns on the left side the dialog box. Click OK to save these settings. Customize data size format The data size format can be customized to meet user preferences. 1. From the Tools menu, select Preferences. The Preferences dialog box appears. 2. 3.
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 v2 installation, the SPM catalog will be automatically upgraded if SPM v1 was previously installed.
Refer to the following list for information regarding the resources and how each should be installed and configured. This is a list of available resources, not required resources. Each environment will have a different set of required resources. • An HP EVA disk array must be installed and configured with HP P6000 Command View Software. SPM must be able to communicate, through TCP/IP, with the CV installation for all EVAs used. For more information see Working with EVA storage systems.
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.
be used to create the storage pools, and SPM should only be made aware of those storage pools which it is allowed to use. In this manner, SPM might manage only a subset of an array, and may allow on-demand provisioning in one storage pool, but not another. To manage an existing storage pool, see Managing storage pools. To import storage pools: 1. From the Navigation tree, select Storage Pools, then click Import Storage Pools at the bottom of the window.
4. 5. 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. On the Summary page, confirm the settings. To make changes, click Back to return to the previous wizard pages. When all settings are confirmed, click Finish. Importing a network To manage an existing network, see Managing networks. To import a network: 1.
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.
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. All templates must be based on a base template. 6. 7. Select the appropriate base template. Click Next. The Read–only Requirements screen appears.
4. If changes are required, click Edit Template at the bottom right. The Edit Template page appears. 5. 6. 7. Make the necessary edits to the template by clicking on each tab that is required. As each tab is completed, click Apply at the bottom right. When all changes have been completed, click OK. The template information screen appears. 8. If a template requires deletion, click Delete Template at the bottom right of the template information screen. The Delete Template verification screen appears. 9.
Requirements are matched against a service or service resources. The requirement is said to match or be satisfied if the service conforms to the requirement. Service requirements are of two types: • Scalar requirements – requirements which describe a single property, behavior, or policy • Requirement Groups – requirements which group or contain a set of other requirements All Of requirement The All Of requirement is a Requirements Group containing other requirements.
Fibre Channel Target Endpoint requirement Fibre Channel Target Endpoint is a Requirements Group containing the requirements describing a single Fibre Channel target endpoint. The Fibre Channel Target Endpoint members are described below: • Fibre Channel Endpoint WWN — Interface WWN • Fibre Channel Network — Network to which the target WWN is connected. • Fibre Channel Proxy Endpoint WWN — Network on which proxy WWN exists is the Network to which the interface WWN is connected.
2. 3. 4. specified within the Fibre Channel Host requirement groups. The presentations of the matching volumes will not be changed. If all Fibre Channel Host requirement groups contain Pre-presented=FALSE (or do not contain a Pre-presented requirement) in them, then the resulting services will be configured to be accessible by the hosts specified by the Fibre Channel Host requirements.
in situations where archiving processes are in place and have saved all necessary data before deleting the service. • Recycle — On service deactivation, if the storage volume’s presentation was changed, then the volume is unpresented. If the storage volume was created, then the storage volume will be deleted – destroying the data it contains – and the capacity is returned to its containing pool for future service provisioning requests. Any SAN zoning that was performed will be removed as well.
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 or not. Volume Committed Capacity requirement The Volume Committed Capacity requirement specifies the percentage of capacity which should be committed or allocated. The remainder of capacity is to be thinly provisioned.
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: • SAN connected volume service • 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.
NOTE: Services created through Matrix OE should not be deleted from SPM. Instead these services should be managed through Matrix OE. 1. . Access a specific storage service by following the steps in Viewing a storage service 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, will be 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.
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 host entries (Hosts tab) To view the host entries of an array: 1. In the Navigation tree, select Arrays.
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 Array.
Viewing storage pool volumes (Volumes tab) To view volumes of a storage pool: 1. In the Navigation tree, select Storage Pools. The list of available storage pools appears in the content pane. 2. From the content pane, select the appropriate storage pool. The properties for the selected storage pool are displayed. 3. Click the Volumes tab. A list of available volumes is displayed. Information for volumes that are managed by SPM is displayed.
Managing volumes Viewing and modifying volumes settings (Overview tab) To view or modify the basic settings of a volume: 1. In the Navigation tree, select Volumes under the Resources heading. The list of available volumes appears in the content pane. 2. From the content pane, select the appropriate volume. The properties for the selected volume are displayed. 3. Click the Overview tab. The basic settings are displayed. 4. To edit these settings, click Edit Volume. The Edit Volume window appears. 5.
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 volume To remove a volume: 1. In the Navigation tree, select Volumes. The list of available volumes appears in the content pane. 2. From the content pane, select the appropriate volume. The properties for the selected volume are displayed. 3. Click Remove Volume at the bottom of the window.
4. To edit these settings, click Edit Network. The Edit Network 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. When finished, click OK. Viewing network endpoints (Endpoints tab) The Endpoints tab shows two content panes. The top pane only shows network endpoints that are of interest to SPM and its users and not a complete view of the network.
To view zones of a network: 1. In the Navigation tree, select Networks under the Resources heading. The list of available networks appears in the content pane. 2. From the content pane, select the appropriate network. The properties for the selected network are displayed. 3. Click the Zones tab. The zone settings are displayed. NOTE: Select a zone in the list to view the endpoints in that zone.
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 that do not contain Zones that any SPM service depends on and also don’t contain any Endpoints that any other resource in SPM depends on can be removed from the catalog.
2. Click Create Role on the bottom right. The Create Role dialog box appears. 3. 4. Fill in the required information, noted by a red asterisk, on each tab of the dialog box (Overview, Privileges, Users and Groups, Security). 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. When creating a new role, these are assigned on the Privileges tab.
Grant permissions Permissions are granted to security groups within SPM to allow access control over services, templates, resources, roles, and other security groups. A list of available permissions is provided in the following table.
Viewing and modifying role settings (Overview tab) To view or modify the basic settings of a role: 1. In the Navigation tree, select Roles under the Administration heading. 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 the Overview tab. The basic settings are displayed. 4. To edit these settings, click Edit Role. The Edit Role window appears. 5.
Viewing and modifying role security settings (Security tab) To view or modify the security settings of a role: 1. In the Navigation tree, select Roles under the Administration heading. 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 the Security tab. The security settings are displayed. 4. To view the access control settings, click Access Control....
4. To edit these settings, click Edit Security Group. The Edit Security Group 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. When finished, click OK. Viewing and modifying security group access control settings (Access Control tab) To view the access control settings of a security group: 1.
6. 7. Select a user, group or role from the corresponding list. Click OK. The effective permissions for that user, group or role are displayed. Deleting a security group To delete a security group: 1. In the Navigation tree, select Security Groups under the Administration section. 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.
and the device then the resource is put into quarantine. This usually means something happened to the resource or catalog after the SPM catalog backup occurred that was lost on restore, and the admin may need to update the SPM catalog manually before the resource is safe to be brought out of quarantine. See the Backing up and restoring HP Insight Management 7.1 Central Management Server (Windows) White Paper, at http://www.hp.com/go/matrixoe/ docs, for more information on performing this process.
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.
To find Unresourced storage services: 1. From the Navigation tree, click on Storage Services. Look for any storage services with a value of Unresourced under the State header. NOTE: To see only Unresourced storage services, click the filter icon in the tool bar, then add a filter for State and select Unresourced. 2. Click the appropriate Unresourced storage service in the content pane. To activate the storage service normally: 1. Click the Configure Requirements button at the bottom of the screen.
4. 5. To change requirements, modify the values on the requirement pages (if any) or click Modify requirements (advanced) on the Choose Solution page. Select a solution from the list. Details about the solution, including the match status of each requirement, can be viewed by clicking the Details link on the solution. NOTE: If no solutions are listed, further modify the requirements or deactivate the storage service to search for solutions involving other resources. 6. 7. 8.
8 Support and other resources Related documentation The following documents provide related information: • HP Matrix Operating Environment 7.0 Release Notes • HP Matrix Operating Environment 7.0 Getting Started Guide • HP Insight Management 7.0 Installation and Configuration Guide • HP P6000 Command View Software User Guide • HP Matrix Operating Environment 7.0 Logical Server Management User Guide • HP Matrix Operating Environment 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 53) 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. 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. Under Operational Logs, click the appropriate file name. The file opens. Operational log entries can be copied for pasting content into another window on the desktop.
4. Save and close the file. 5. Using the Microsoft Services MMC, start SPM service. Issues with multiple SPM instances pointed to the same storage resources Symptom–Changes from one SPM server overwrite changes made on another SPM server. Possible cause–Both SPM servers are attempting to manage the same resources. Suggested action–Verify that each SPM server is managing distinct instances of the volume resources. Do not attempt to manage the same volume resources with both SPM servers.
The proper order for starting these services is to start the HP SPM Storage Module Service first. This should automatically start the HP SPM Storage Module J2EE Service. Once these services are running, then the HP Storage Provisioning Manager Service may be started.
BNA “All Programs” section. Verify that the CIMOM server is running. If not, configure and start it. Unmanaged SAN Unmanaged SAN cannot be imported Symptom–Unmanaged SAN fails to appear in the list of importable SANs Possible cause–Default comments as shipped with SPM were not removed from the XML file. Suggested action–Edit the unmanaged SAN XML file and verify that the XML default comments as shipped with SPM have been removed. Symptom–Unmanaged SAN fails to appear in the list of importable SANs.
B Working with Brocade Fibre Channel networks Minimum requirements Brocade’s Brocade Network Advisor (BNA) or Brocades Standalone SMI Agent are required as specified below. Refer to release notes to see 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.
create/destroy zones dynamically depending on the needs of the users and the constraints set in place by the storage administrator. NOTE: Manual zoning changes done by a storage admin via BNA's GUI will take priority over and cancel requests coming in via SPM and will result in SPM request failing.
Requirements When creating a Connectivity Service there are two use cases as follows: Standard Use Case In the standard case one or more FCInitiatorEndpoint requirements are given in conjunction with one or more FCTargetEndpoint requirements. For each and every endpoint requirement the sub requirement FCWWN is required. SPM will interpret these requirements as follows. SPM will check that all the given endpoints are on the same network.
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 Import Array feature in the SPM 2.0 GUI, EVA x400 and P6000 arrays may be imported into SPM. This in turn allows storage pools and volumes on the array to be imported.
Understanding EVA Storage System presentation, mapping, and masking EVA offers 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 2.0 GUI, 3PAR arrays may be imported into SPM. This in turn allows storage pools and volumes on the array to be imported.
legacy volumes can be assigned any supported RAID level. As explained later, this means SPM must report raw capacity for concrete pools. Common Provisioning Groups (CPG) are thin pools that are created within the scope of a concrete pool. Intitially, a CPG’s capacity is always 0. CPGs are RAID-locked, meaning that volumes provisioned in a CPG are always assigned the CPG’s RAID-level.
SPM capacity value 3PAR calculation (CPG based pools) Subscribed capacity Calculated as the sum of all volumes’ subscribed capacities. Hence SPM reports logical capacity. Available capacity The difference between the CPG’s physical capacity and its committed capacity. Volume capacity SPM tracks capacity and committed capacity for volumes, where capacity is the overall capacity of the volume in bytes and committed capacity is the number of bytes that have actually been reserved for the volume.
Exposing volume presentations in 3PAR Storage Systems 3PAR 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.
array, then a presentation request might indicate that the initiator port's host grouping should change. This could happen if a single host contained two initiator ports and the presentation request referenced one of the ports but not the other (meaning that the initiator port shouldn't be part of the host anymore). If these presentation requests would affect presentation for another existing volume, SPM will not change the array's configuration, resulting in a nonconformant service.
The main side effect of volume migration, particularly when automated, is that the parent pool will change as mentioned above and the raid level of the volume may change. As a result, allocated services that specify ‘UseResource’ or ‘RaidLevel’ requirements may become nonconformant. Importing a large number of volumes The SPM catalog can handle tens of thousands of objects. Importing those objects into the catalog in the first place, however, can be time consuming.
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 2.0 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.
F Working with unmanaged networks Overview This section specifies the format of the XML files used to describe the characteristics of unmanaged storage area networks (SANs) to SPM 2.0. Unmanaged SANs are SANs with which SPM cannot communicate. In order for a user of SPM to track connectivity within such SANs using SPM, the characteristics of the SANs are described in XML files which SPM will read. SPM 2.0 allows users to manage connectivity in a number of SANs.
XML file lifecycle The user must provide SPM with an XML file as described in this document which specifies the features of the unmanaged SANs. When there are changes to the state of the unmanaged SAN, the user must update the data in the XML file in order for the data within SPM to be consistent with the state of the SAN. When an unmanaged SAN becomes available, changes, or becomes unavailable, the user should manually make changes to the XML file describing that SAN.
Element ordering Within each XML element of the following XML Object Model, order of the sub-elements is important for an XML file to validate with respect to the schema definition file provided with SPM. XML object model The UML model illustrated below describes the structure of the XML objects within an XML file describing an unmanaged storage array. The elements of this model are described in more detail in subsequent sections.
NetworkResource A NetworkResource object represents a set of storage area networks known to SPM. Each NetworkResource object should represent networks from a single vendor. Property Type Description Network Sequence of Network Zero or more Network objects. Name String The name of this NetworkResource. DisplayName String The name for this NetworkResource (will be displayed in SPM). Description String A brief description of this network.
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. Zone A Zone object describes a zone within a SAN. Its name will be displayed in SPM.
NetworkEndpointKind NetworkEndPointKind is an enumerated type representing the implementation of the network for a SAN network endpoint. It has four possible values: FibreChannel, SerialAttachedScsi, Ethernet, and iSCSI. At this time, SPM supports only Fibre Channel networks. Example unmanaged SAN xml In this section we provided an annotated example of an XML file representing an unmanaged array. The example is provided in Courier font. Annotations are provided within the example as normal font.
G Working with unmanaged arrays Overview This section specifies the format of the xml files used to describe the characteristics of unmanaged storage arrays to SPM 2.0. 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 will read. SPM 2.0 allows 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. They are needed when one object must refer to another object within an XML file. SPM resources defined within an Unmanaged Array XML file (Arrays, Pools, and Volumes) are required to have a UUID identifier used within SPM to identify unique resources. UUIDs should not be reused within an instance of SPM.
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 Optional unique object identifier. HostmodeMap Sequence of MapItem objects Zero or more MapItem objects, mapping HostMode values to array host modes.
Resource Resource objects inherit from the Entity class, and define the UUID, DisplayName, ManagementURL, and Tags attribute. A Resource represents an entity that will be displayed and managed within SPM, including storage arrays, storage pools, and volumes. Property Type Description ObjectID String Optional unique object identifier. UUID String Required unique resource identifier. DisplayName String Name of this resource to be displayed in SPM.
Property Type Description 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. This value will be displayed on array import to describe the type of array being imported, and will be displayed in the array properties page.
Property Type Description 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 CommittedCapacity The CommittedCapacity of a StoragePool is represented by a long integer. It represents the number of bytes of storage from the pool allocated to volumes within the pool.
Property Type Description 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. Capacity The capacity of a Volume is represented by a long integer.
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. InitiatorEndpointObjectID The InitiatorEndpointObjectID is a string representing the ObjectID of a host that has been granted access to this volume. This is represented as an ObjectID rather than a reference to a StorageArrayHostEndpoint because XML does not allow circular references.
Name The name element is a string representing the name of this storage array port. This name will be used to identify this StorageArray within SPM. StorageArrayHostEndpoint This type inherits from the NetworkEndpoint type. It represents the ports on the array, and has no elements of its own. StorageArrayHostEntry A StorageArrayHostEntry represents a host known to SPM and served storage by the StorageArray referring to this object. StorageArrayHostEntry inherits from Entity.
HPUX HP-UX * Normal This HostmodeMap element specifies that SPM’s HPUX hostmode maps to the hostmode known as HP-UX on the storage array, and that all other hostmodes known to SPM map to the Normal mode on the storage array.
Vol 1 http://foo.fr/Pierre/p1/v1 The first storage pool contains two volumes. The first volume has a UUID, display name and management URL as specified above. It has no tags. 100000000 0 RL1 The first volume has a capacity of one hundred thousand bytes, a committed capacity of zero bytes, and a RAID level of PRaid1.
Normal Object-1 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. The host’s Fibre Channel address is specified.
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. application server A system that is hosting one or more applications and is running an operating system optimized for hosting applications. Storage may be direct attached (such as a storage server) or networked.
HP Operation Orchestration OO provides a comprehensive solution to Automate incident resolution, change orchestration and routine maintenance tasks in your data center. HP Matrix OE with infrastructure orchestration has an embedded version of OO to take advantage of the OO workflow engine capabilities. HP Storage Provisioning Manager SPM, the software application described in this document. I initiator An endpoint that consumes storage through a storage area network.
resource (n.) 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. 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 server In this document, a server refers to either an application server or a storage server.
unresourced Within SPM, a service is unresourced if it has not yet been activated or if it has been deactivated. 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.
Index Symbols R 3PAR Storage Systems, 63, 65, 66, 67 related documentation, 52 request nonconforming, 49 A array deleting, 35 managing, 33 S conventions document, 53 text symbols, 53 security catalog, 16 storage pool importing, 18 Subscriber's Choice, HP, 52 symbols in text, 53 D T data size format, 14 display columns, 13 document conventions, 53 documentation HP website, 52 providing feedback, 53 related, 52 technical support HP, 52 service locator website, 53 text symbols, 53 typographic conven
