Professional Documents
Culture Documents
Ionix - 300 006 378
Ionix - 300 006 378
6.1
Copyright 2008 - 2011 EMC Corporation. All rights reserved. Published in the USA. Published August 2011 EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. EMC2, EMC, EMC Centera, EMC ControlCenter, EMC LifeLine, EMC OnCourse, EMC Proven, EMC Snap, EMC SourceOne, EMC Storage Administrator, Acartus, Access Logix, AdvantEdge, AlphaStor, ApplicationXtender, ArchiveXtender, Atmos, Authentica, Authentic Problems, Automated Resource Manager, AutoStart, AutoSwap, AVALONidm, Avamar, Captiva, Catalog Solution, C-Clip, Celerra, Celerra Replicator, Centera, CenterStage, CentraStar, ClaimPack, ClaimsEditor, CLARiiON, ClientPak, Codebook Correlation Technology, Common Information Model, Configuration Intelligence, Connectrix, CopyCross, CopyPoint, CX, Dantz, Data Domain, DatabaseXtender, Direct Matrix Architecture, DiskXtender, DiskXtender 2000, Document Sciences, Documentum, elnput, E-Lab, EmailXaminer, EmailXtender, Enginuity, eRoom, Event Explorer, FarPoint, FirstPass, FLARE, FormWare, Geosynchrony, Global File Virtualization, Graphic Visualization, Greenplum, HighRoad, HomeBase, InfoMover, Infoscape, InputAccel, InputAccel Express, Invista, Ionix, ISIS, Max Retriever, MediaStor, MirrorView, Navisphere, NetWorker, OnAlert, OpenScale, PixTools, Powerlink, PowerPath, PowerSnap, QuickScan, Rainfinity, RepliCare, RepliStor, ResourcePak, Retrospect, RSA, SafeLine, SAN Advisor, SAN Copy, SAN Manager, Smarts, SnapImage, SnapSure, SnapView, SRDF, StorageScope, SupportMate, SymmAPI, SymmEnabler, Symmetrix, Symmetrix DMX, Symmetrix VMAX, TimeFinder, UltraFlex, UltraPoint, UltraScale, Unisphere, Viewlets, Virtual Matrix, Virtual Matrix Architecture, Virtual Provisioning, VisualSAN, VisualSRM, VMAX, VNX, VNXe, Voyence, VPLEX, VSAM-Assist, WebXtender, xPression, xPresso, YottaYotta, the EMC logo, and the RSA logo, are registered trademarks or trademarks of EMC Corporation in the United States and other countries. Vblock is a trademark of EMC Corporation in the United States. VMware is a registered trademark of VMware, Inc. in the United States and/or other jurisdictions. All other trademarks used herein are the property of their respective owners. For the most up-to-date regulatory document for your product line, go to the technical documentation and advisories section on the EMC online support website.
CONTENTS
Chapter 2
14 14 14 14 15 15 15 16 16 16 17 17 17 18 18 19 19 20 20 20 21 21 28 33 40 42 42 44 44 46
3
Contents
Extending file system, logical volume, or volume group ........... Selecting host to have access to replica................................... Configuring meta devices......................................................... Reviewing path details............................................................. Reviewing the allocation task .................................................. Deallocating storage ................................................................ Executing allocation and deallocation tasks ............................ Viewing task list with selected details...................................... Viewing commands associated with task action ...................... Zoning changes and zone names ............................................. Using SAN Manager AutoPath .................................................. Showing reserved devices ....................................................... Provisioning use cases .................................................................. Adding new host...................................................................... Adding storage to hosts or clustered hosts .............................. Adding storage to volume groups............................................. Extending logical volumes ....................................................... Extending file systems ............................................................. Extending striped logical volumes............................................ Prezoning to constrain paths ................................................... Using ARM active commands ................................................... Provisioning clusters ............................................................... Platform-specific configuration information ............................. Provisioning hosts discovered in the SAN ................................ Reducing number of outstanding tasks .................................... Working with mirrored fabrics ..................................................
48 49 50 52 54 55 64 66 67 68 70 72 72 73 73 73 73 74 76 76 76 77 77 80 81 81
Chapter 3
Troubleshooting
List of possible trouble conditions ................................................. Retrying a failed operation ....................................................... Host rescan failure................................................................... Determining why no devices were found .................................. Refreshing information in the console...................................... Disk count in VERITAS volume group ........................................ LUN IDs greater than 255 on a Symmetrix array........................ Matching allocation tasks to log files ............................................. 83 83 83 84 86 86 86 87
Chapter 4
Contents
Expand Solaris VERITAS Volume Manager storage with PowerPath on CLARiiON array.................................................................... 90 PowerPath reconfiguration....................................................... 90 Add disks to VERITAS disk groups or PowerPath volume groups 90 Expand VERITAS or PowerPath logical volumes ........................ 90 Expand VERITAS or UFS file systems......................................... 90 Expand Solaris file system on slice number 2........................... 90 Expand Windows 2000 or Windows 2003 volume .................... 90 Preventing Actions on a host.................................................... 91
Contents
PREFACE
As part of an effort to improve its product lines, EMC periodically releases revisions of its software and hardware. Therefore, some functions described in this document might not be supported by all versions of the software or hardware currently in use. The product release notes provide the most up-to-date information on product features. Contact your EMC representative if a product does not function properly or does not function as described in this document.
Note: This document was accurate at publication time. New versions of this document might be released on the EMC online support website. Check the EMC online support website to ensure that you are using the latest version of this document.
Audience
This guide is part of the EMC Ionix ControlCenter documentation set,and is intended for use by users of Storage Provisioning Services Organization.
CAUTION, used with the safety alert symbol, indicates a hazardous situation which, if not avoided, could result in minor or moderate injury.
NOTICE is used to address practices not related to personal injury. Note: A note presents information that is important, but not hazard-related. IMPORTANT An important notice contains information essential to software or hardware operation.
Preface
Typographical conventions
EMC uses the following type style conventions in this document: Normal
Used in running (nonprocedural) text for: Names of interface elements, such as names of windows, dialog boxes, buttons, fields, and menus Names of resources, attributes, pools, Boolean expressions, buttons, DQL statements, keywords, clauses, environment variables, functions, and utilities URLs, pathnames, filenames, directory names, computer names, links, groups, service keys, file systems, and notifications Used in running (nonprocedural) text for names of commands, daemons, options, programs, processes, services, applications, utilities, kernels, notifications, system calls, and man pages Used in procedures for: Names of interface elements, such as names of windows, dialog boxes, buttons, fields, and menus What the user specifically selects, clicks, presses, or types
Bold
Italic
Used in all text (including procedures) for: Full titles of publications referenced in text Emphasis, for example, a new term Variables Used for: System output, such as an error message or script URLs, complete paths, filenames, prompts, and syntax when shown outside of running text Used for specific user input, such as commands Used in procedures for: Variables on the command line User input variables Angle brackets enclose parameter or variable values supplied by the user Square brackets enclose optional values Vertical bar indicates alternate selections the bar means or Braces enclose content that the user must specify, such as x or y or z Ellipses indicate nonessential information omitted from the example
Courier
<> [] | {} ...
Preface
Technical support For technical support, go to EMC online support and select Support. On the Support page, you will see several options, including one to create a service request. Note that to open a service request, you must have a valid support agreement. Contact your EMC sales representative for details about obtaining a valid support agreement or with questions about your account.
Your comments
Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Send your opinions of this document to:
techpubcomments@emc.com
Preface
10
11
General information on page 14 describes supported platforms and what can be provisioned. Provisioning process: Best practices on page 15 describes how SPS can easily fit into the provisioning workflow that most companies use. Requests for storage that include reserving logical devices can be saved by less-experienced users, and the same requests can be reviewed, modified as necessary, and executed by more senior administrators. Configuring the environment for provisioning on page 19 explains how to configure Ionix ControlCenter to begin using SPS. This includes ensuring that servers are properly connected to storage area network (SAN) switches, agents are installed, logical devices are placed in storage pools, and storage policies created. Working with SPS in the Ionix ControlCenter Console on page 44 provides information about the different Ionix ControlCenter components used to allocate storage. These descriptions are brief; we assume that you will reference the online help system for detailed information. This section is intended to be a high-level overview of the SPS dialog boxes. Provisioning use cases on page 72 provides use case details, such as allocating storage to a new host, or extending file systems. Select from the use case of interest to find out how best to manage your storage. Troubleshooting on page 83 describes errors that may occur due to external forces such as servers that are shut down, administrators that use other applications that conflict with SPS, and normal errors due to malfunctioning hardware. In most cases, the errors may be examined and corrective action applied. Host Agent Actions on page 89 includes a short explanation of what commands are executed in the host actions on behalf of SPS.
12
General information ......................................................................................... Provisioning process: Best practices................................................................. Configuring the environment for provisioning ................................................... Working with SPS in the Ionix ControlCenter Console ........................................ Provisioning use cases .....................................................................................
14 15 19 44 72
13
General information
This section describes the supported platforms and required agents for SPS operations.
Thin devices can be allocated in two types of allocation tasks: Standard only or Standard and Remote types. BCV allocations of thin devices are not supported. Thin device allocations must not use non-thin devices in the same element of an allocation, i.e., an R1 element of an allocation cannot consist of both a thin device and a non-thin device. Extending a volume group, logical volume, or file system is not available to thin devices. Direct allocation of data devices in thin provisioning pools is not allowed, therefore data devices are not allowed in the SPS storage pools. Data devices are internal system devices and do not apply to SPS. SPS can deallocate thin devices.
14
Servers that are discovered by the Ionix ControlCenter Common Mapping Agent cannot have any host actions performed. However, logical devices may be allocated and presented to the host bus adapters (HBAs) that the FCC Agent discovered. Note that you first need to add the unassociated HBA port to the host. Symmetrix striped meta devices cannot be expanded, although concatenated meta devices can be.
Provisioning process
SPS will work with corporate operational provisioning processes that include various levels of approval. You can use the SPS CLI to integrate SPS directly with workflow or other software packages. Alternatively, you can track storage provisioning activity manually within software you use to manage the provisioning process. Within your internal tracking system, you should track activity such as host, application, and user contact names; desired storage capacity; and protection and replication policies (refer to Creating allocation and deallocation policies on page 33). After a request receives financial approval, the storage administrator would then receive and act on the approved request. The storage administrators activities might include, for example, moving logical devices to the storage pool of the business unit making the request, assuming you have organized storage pools by business-unit ownership.
16
Note: An administrator may be given permission to save provisioning tasks only. The task may be executed or moved once the provisioning request is approved by a senior administrator or the change control board. In addition, a senior administrator may edit the task for necessary changes.
Performance implications
There are performance implications when executing provisioning task lists. For example, multiple tasks to different hosts may cause mapping changes on the same Symmetrix array. To save time, you can move all tasks that require mapping actions for that array to the same task list. When you execute the task list, only one mapping session is needed for that array.
17
18
The Task List is rebuilt automatically. If there are problems, such as a logical device having been used even though it was reserved, you will have time to use the SPS wizard to edit the appropriate provisioning task in order to select a different logical device.
Physical environment
The following considerations apply to the physical environment: Note: Some functions require a minimum level of array microcode. Refer to the EMC ControlCenter Support Matrix on Powerlink for specific version information.
Fabric Ensure that hosts and storage systems are physically connected to the SAN fabric. The Fibre Channel Connectivity Agent must be used to discover all connectivity in the fabric. Host Types Windows 2000, Windows 2003, HP-UX, Sun Solaris, and AIX hosts are supported. Refer to the EMC ControlCenter Support Matrix on Powerlink to ensure that the HBA drivers are at the minimum supported revisions. VMware hosts For VMware hosts running ESX Server 3.0, SPS can allocate storage up to the point of the host bus adapter of the server. VMware Virtual Infrastructure Client 2.0 can then be used to pick up the storage that has been allocated to the server. TES (Topology Editing Service) and storage allocation: If using the TES to create user-defined (virtual) hosts, SPS can allocate storage to a virtual host (except with Solaris hosts). When the physical host is added to the SAN the storage will be available to the host; provided the correct host bus adapter details were used when creating the virtual host. A TES host can only be allocated on its own, you cannot do TES host and real host allocation in the same task. When allocating to a TES Solaris host, the user will have to manually enter values into the sd.conf file when it is added to the SAN. SPS cannot do this during allocation as the actual physical host didn't exist.
19
Symmetrix storage allocation types are "Primary Only" and "Primary & Local". Clariion storage allocation policies must have "Create New Storage Group" selected on. If allocating Clariion storage to the TES host, the user will have to bind the host to the Clariion Storage Group when the physical host is added to the SAN. This will make the devices visible from the host. StorageWorks TES allocations are not supported.
Array Types The supported arrays include Symmetrix, CLARiiON, and HP StorageWorks EMA with HSG80 controllers. In all cases, logical devices must be created ahead of time; SPS provides services to allocate those devices to (or deallocate from) supported hosts.
Licensing
The Automated Resource Manager (ARM) license is required for SPS.
Agents
The native agents for each of the storage arrays used for provisioning must be installed and operating, for example, Storage Agent for HP StorageWorks or Storage Agent for CLARiiON. SPS cannot allocate or deallocate storage on arrays discovered by the Storage Agent for SMI.
Solutions Enabler
Refer to the EMC ControlCenter Support Matrix on Powerlink for the minimum version of Solutions Enabler.
20
Multipath configurations
Support for multipathing varies with the storage array or software used to support it.
Table 1 Support for multipathing Multipath Array Symmetrix and CLARiiON StorageWorks Comments PowerPath 3.x and 4.x are supported in SPS. The policy field specifying the number of paths is used to configure devices. PowerPath will manage I/O to those devices over those paths. Version 5.2 supports a single path only.
The Fibre Channel Connectivity Agent must be installed to discover the fabric. Storage agents should be installed to discover and manage arrays. The Symmetrix SDM Agent should be installed to support LUN masking on Symmetrix arrays. Host agents should be installed on hosts requiring host actions.
Ionix ControlCenter displays the status of an agent through its icon. If you see the warning triangle on the agent icon, the agent is experiencing a problem. Note that there is some latency between the time an agent is started and the time that it appears active to the Ionix ControlCenter infrastructure.
Storage agents
The following sections describe special considerations for each of the required agents.
In order for SPS to work properly, the arrays must be fully discovered by the agents. In the Console tree panel, expand the Storage Systems folder to view all the available arrays.
If an array icon has a pink diamond in the upper-right corner, the array has not been fully discovered. Expect to see this icon when:
The Storage Agent for Symmetrix is not installed. The Storage Agent for Symmetrix has not fully discovered the array.
For a new installation, large arrays may take some time to discover, so wait until the diamond disappears from the array icon before beginning the provisioning process.
23
24
Host agents
A host agent must be installed on every host that will have host actions performed in the storage provisioning process. You can use the techniques described in Using Agent and Properties view on page 21 to verify the state of your agent. When the host agent is installed and has gathered information from the host, you will see information about your host in the tree. For example, the Adapters folder will contain your Fibre Channel adapters, the File Systems folder will display any mounted file systems, and the Volume Group folder will show all volume groups. If you see information about your file systems and volume groups, but you do not see your adapters, then you are likely using unsupported HBAs or drivers for the HBAs. Refer to the EMC ControlCenter Support Matrix on Powerlink to determine supported HBAs and drivers. If the host agent cannot discover your adapters, then you need to manually associate the HBA ports discovered by the FCC Agent to that host. However, you will not be able to perform host actions since the agent did not discover correct adapter numbers. Figure 6 on page 26 shows a fully discovered host.
25
26
27
Permissions
This section discusses user permissions and methods for preventing actions on a host.
28
User roles
SPS is designed to simplify provisioning. One level of administrator may be allowed to create provisioning tasks and reserve logical devices, while a second user role may edit and execute provisioning tasks. Permissions may be applied, per user, on certain hosts and certain storage pools. For example, one administrator may be authorized to save provisioning requests for e-mail hosts and storage pools, while another has permissions for Finance hosts and storage pools. A third user role is the storage administrator who can manage storage pools. The following permissions apply to allocation functionality. To manage storage pools, you need the following permission:
Allocation Administration Allows you to create a storage pool, populate a pool with devices, remove devices from a pool, and delete a pool.
To create and execute allocation tasks, you must have the following permissions for both the storage pool and hosts involved in the task:
Allocation Reservation Allows you to create and save allocation tasks only. Allocation Execution Allows you to execute allocation tasks.
Deallocation Administration To create a deallocation policy, you must have the Deallocation Administration permission for the Deallocation Policy object type. To edit a policy, you must have the permission for the specific policy or for the type. Deallocation Reservation To create or edit a deallocation task, you need the Deallocation Reservation permission for each host and array involved in the deallocation or for the Host and Array object types. Deallocation Execution To execute a deallocation task, you need the Deallocation Execution permission for each host and array involved in the deallocation task or for the Host and Array object types.
29
For convenience, you may drag an array into a newly created pool, in order to place all of the arrays currently configured logical devices in that pool. Other logical devices that are configured later would need to be explicitly added. Note: It may take up to five minutes to move a large storage array into a pool. To find out if and which storage pool a logical device belongs to, drag the device to a Properties view. New logical devices created by configuration tools are not automatically assigned to any pool, and therefore will not be used by SPS. Remember to manually place new logical devices into appropriate pools. One of the best ways to determine whether logical devices are used is to look at the Allocated field in Properties view for a logical device. Allocated devices will never be selected for a new provisioning request unless they are deallocated first. However, pools are not limited to unallocated devices. For example, you might add allocated devices to storage pools for reporting purposes. In addition, if you use pools to track ownership of storage, then you might add allocated devices to the pools of the business units or applications that own them. Use the Relationship view or dialog box to determine which devices belong to an application or business unit. Note: SPS is conservative about which devices it considers to be allocated. Devices that are partially discovered, for example, are labeled "Possibly Allocated" and are not available for allocation.
30
3. When the new storage pool appears in the folder, rename it, and then drag logical devices into the pool.
Array type
You can place each array in its own pool or create a pool containing arrays of the same type. This is often a good way to initially create pools. This allows storage policies (described in the next section) to be set by array types, and makes it easy to select
Configuring the environment for provisioning
31
pools in the policy. An array can also represent some of the types listed below, such as performance or cost. Newer arrays may be faster or cost more. Older arrays may be fully depreciated and cost less.
Ownership
You may organize your logical devices by pools that define ownership. This is an excellent way to reserve storage for an application that has prepaid for storage and has short-term plans to allocate storage. The storage administrator would place logical devices in the pool when financial approval is met in preparation for SPS to select the storage from a policy specifying that pool. Examples include separate pools for mail, file, and database applications.
Performance
Often, storage administrators buy small drives in order for one application to monopolize usage and get 100 percent of the I/O capability of that drive. You may want to place logical devices of this type into their own pool, and place logical devices split from very large drives into a lower-performance pool. An alternative method to high performance is to create RAID I/O devices. These devices may be placed in high-performance pools, and RAID 5 devices in lower-performing pools. Use the Properties view, and sort or filter by disk size. Then, use the Relationship dialog box (from the shortcut menu) to get the logical devices from the disks of a certain size. You can also use Properties view to sort logical devices by protection type (Configuration column).
Cost
You can create storage pools based on cost of storage, either from low-cost arrays or from logical devices split from very large drives, with a lower cost per megabyte.
Geography
You may want to place remote storage in its own pool for use in provisioning for disaster recovery. In many cases, data centers may be combined through fabrics even though they may be thousands of feet away. Segregate your storage pools in order to allocate storage to servers from local arrays. Remote Symmetrix arrays are discovered from the local Symmetrix array.
Combinations
Combine the above use cases in a pool hierarchy, as necessary, to help segregate logical devices of different characteristics.
32
33
34
Allow devices from multiple arrays Allows the allocated storage to include devices from multiple arrays of the same type. Enforce homogeneity of host OS on storage ports Specifies that hosts that are running the same operating system (OS) should access storage through a fixed set of front-end ports. With this option selected, SPS will filter out the following types of ports during path selection: Storage ports with allocated storage to multiple host operating system types Storage ports with allocated storage to a host running an OS that is different from the OS of the host being allocated SPS only considers the operating system type, not the operating system version. Pauses the execution of a task list between zoning changes. If a task list contains multiple zone set activations, SPS pauses the execution of the task list after each zone set activation to allow you to confirm the zoning changes before changes are made to the next zone set. In the tree and Task List Viewer, a Paused Task List icon indicates that the task list is paused. To resume the storage allocation task after you confirm the zoning changes, right-click the paused task list and select Resume Task List.
Symmetrix Only Add to SymAPI Device Group Adds all newly allocated devices, which were allocated using this policy, to an existing SymAPI (Solutions Enabler) device group. This attribute only applies to Symmetrix arrays. This attribute is selected automatically if the replica class is Local, but the attribute is optional if the replica class is Primary Only or Remote. If you select this option, you must create the device group and prepare it to receive devices before you run the Allocation Wizard. Specifies either meta devices or standard devices. Specifies meta devices only.
35
Table 2 Allocation Policy Editor dialog box options (2 of 3) Option If not found, create striped metas Description Tells the Allocation wizard to create striped meta devices if it cannot find existing meta devices that meet the parameters of the request. This option only applies to the Primary and Primary + Local replica classes. All created meta devices will have the same number of devices. SPS will only use unmapped devices for new meta devices. Creates meta devices with this number of devices. Specify a whole number greater than one. If you do not specify a value and you select At Least for Amount to Allocate on the first screen of the Allocation wizard, SPS always creates the minimum number of metas allowed (as specified in Requested # Metas on the first screen of the Allocation wizard), using the smallest possible devices. In this case, SPS ignores any maximum value specified for Requested # Metas. However, SPS makes metas from larger devices, rather than the smallest available devices, if using the larger devices reduces the number of zoning operations required to allocate the metas. If you do not specify a value and you select At Most or Range for Amount to Allocate on the first screen of the Allocation wizard, SPS attempts to locate the maximum amount requested (without exceeding it), using the smallest number of metas and choosing those with the smallest size members first. However, SPS creates more metas with fewer members if that comes closer to the maximum requested size. As described in the previous case, SPS makes metas from larger devices if creating metas from those devices reduces the number of zoning operations.
36
Table 2 Allocation Policy Editor dialog box options (3 of 3) Option Replica Class Description Indicates the type of replica device to be associated with the primary storage device. Click the Select Class button to display a dialog box that allows you specify a different replica class. Lets you specify a policy description. An editable summary table indicating the attributes of the primary and replica devices. (Click cells to select from listboxes of available choices.) The following attributes are shown: Storage Element Row-level indicator for the device attributes to follow. Storage Pool Storage pool from which devices should be taken. Storage Type Type of storage devices to choose from within the storage pool. Only Symmetrix arrays are allowed when the policy specifies local or remote replicas. RAID Level Type of RAID configuration associated with the device. # Paths Number of paths to create between the host and the storage. Create New Storage Group (CLARiiON only) Check to create a new storage group for CLARiiON allocations. This is required if you allocate a new CLARiiON array to an existing host, or if you allocate CLARiiON storage for a newly configured host. Mapped Devices Only (Symmetrix only) Constraint to select Symmetrix devices that are already mapped (no SDR action required). Zoned Storage Only Constraint to select storage that is currently zoned to the host. This usually means a storage array that is in use or preconfigured for use. This supports the requirement to keep applications inside one storage array. If you do not specify this, SPS can choose any storage in the pool, even if that storage array has never been zoned to (used by) the host. Disable Host Actions Specify this option to prevent any host actions during the allocation, such as rescanning, PowerPath operations, or actions on volume groups, logical volumes, and file systems.
37
38
Note: You can also create deallocation policies by clicking New on the first screen of the Deallocation wizard.
Table 3 Deallocation Policy Editor Controls (1 of 2) Control Policy Name Description Policy Name. This field is disabled if you accessed this dialog box by clicking the Edit button in the Deallocation wizard. The Storage Provisioning Service has one default deallocation policy. The first time you use the Deallocation wizard, this system-wide default policy appears in the Deallocation Policy field. If you choose another policy in the Deallocation wizard, that policy becomes your default policy. However, the system-wide default still appears for other users the first time they use the Deallocation wizard. Select this checkbox to make this policy the system-wide default.
Host Actions Disable host actions Before Executing Tasks: Rediscover host and fail or error Do not perform deallocation actions on hosts that use this policy. Before performing the deallocation task, rediscover the host and update the Repository. The Deallocation wizard indicates which host devices are currently in use by host file systems, databases, device groups, and so on. If a deallocation task encounters storage that is still in use by a host, the task fails. Note: If you retry a task list, SPS does not check again whether host devices are in use. If the task list succeeds this time, you may lose data on host file systems, databases, and so on that use deallocated devices. After Executing Tasks: Rediscover host Rediscover the host and update the Repository after completing the deallocation task. This keeps the Repository synchronized with changes that result from your deallocation task and prevents you and other users from seeing and acting on out-of-date data.
Array Actions Remove masking access rights Unmap storage device from front end Remove host access to storage ports for deallocated devices (for CLARiiON arrays, remove LUNs from storage groups). This action is always performed. Unmap devices from the array front-end ports that you specify in the Deallocation wizard. This action applies to Symmetrix devices only. This task is only performed if the device is no longer part of any path.
39
Table 3 Deallocation Policy Editor Controls (2 of 2) Control Remove from Symmetrix device group Delete device (CLARiiON) or dissolve meta device if not SRDF (for Symmetrix, requires unmap) Deallocate replica if primary deallocated Description If the device or replica belongs to a device group, remove it from the group. This task is only performed if the device is no longer part of any path. For CLARiiON arrays, delete deallocated devices. For Symmetrix arrays, dissolve meta devices after unmapping them (assuming the meta device is not an SRDF device). This task is only performed if a device is no longer part of any path. When a primary device on a Symmetrix is deallocated, remove any access rights a host has to local or remote replicas of that device. SPS treats a BCV as a replica, even after the BCV has been split from its standard device
Symmetrix rules
The following rules determine when Symmetrix standard devices can be selected for allocation tasks: Devices must be:
In the Ready state, and the Normal status. Unmapped or mapped to a SAN-connected Fibre Channel port and have no unmask records. In a storage pool specified by allocation policy used.
Mapped to ports that are considered direct attached, such as SCSI, ESCON, or Fibre Channel Arbitrated Loop. VDEV, SAV, VCMDB, SFS, DRV, or RAD devices because these are reserved or system devices. In a SYMAPI device or consistency group.
40
Note: In some cases, an unmapped logical device will retain its masking record if it is not removed, and therefore will not be selected as an available device. These entries must be removed in order to allocate the storage. Use the Masking dialog boxes or the Deallocation Wizard to make the device available for allocation.
False(default) ARM looks for any FA ports that are zoned/unzoned to the host(s)
and uses the port with the least number of storage devices already mapped to it.
True BCV devices are not mapped to FA ports that contain any R2 devices for the
host to which the allocation request is being made. In addition, BCV devices can be mapped to FA ports that contain standard devices for the host to which the allocation request is being made.
Refer to Reviewing path details on page 52 to view the dialog box for proposed path and port settings.
CLARiiON rules
The following rules apply to CLARiiON logical devices:
CLARiiON logical devices are available if the device is not assigned to a storage group, or if the device is in a storage group, but the storage group is not associated with a host. To allocate CLARiiON storage to a new host, you must first create an allocation policy and ensure that you select the Create New Storage Group option. This is required if you allocate a new CLARiiON array to an existing host, or if you allocate CLARiiON storage for a newly configured host.
Configuring the environment for provisioning
41
StorageWorks rules
Logical devices are available if they have no unmask records and device numbers are higher than the connection offset to the host.
42
Stop and restart the FCC Agent (refer to Updating host configurations on page 42 for more information on restarting agents). Rediscover the fabric where the host adapter is included.
To rediscover a fabric: 1. On the taskbar, click Monitoring. 2. On the menu bar, select Connectivity from the Discover menu. 3. The Search for Connectivity Devices dialog box appears. 4. Select a switch that is part of the fabric you want to rediscover. 5. A Rediscover button appears in the Details panel of the dialog box. 6. To rediscover the switch and all other switches in the fabric it is part of, select Discover fabric before clicking Rediscover. 7. To rediscover the switch only, clear the Discover fabric option before clicking the Rediscover button.
43
See if there is space available in the host instead of adding storage. Review array details from arrays connected to the host through the SAN. Drill down to storage ports to see if there are enough LUN slots available. Find available logical devices in the array or storage pool. Use the previous methods to help determine why SPS did not find available storage for a request.
44
3. Select Free Space from the Storage Allocation task menu. The Free Space view appears.
Once the display is populated, you can select other objects or drill down to narrow the field of inspection. Figure 14 shows the view drilled down to determine how much storage is associated with each port in the storage array.
45
The initial dialog box varies, depending on which of the four object types you selected. In Figure 16, a host has been selected.
46
47
Table 4 Options for the allocation initial dialog box Option Add Storage to Hosts Description If this host is a member of a cluster, you can add other members of the cluster by dragging them in from the Console. Each entry in the list will have access to the primary devices associated with the storage. Select from an existing list of allocation policies. You can also edit one of these policies or create a new one. Specify the amount of storage you want to allocate. By default, this is treated as the minimum value. To specify a maximum value or range of values, click More Options and select from the list. Click More Options to show these fields. Specify the minimum and maximum number of logical devices to be used. You may want to specify a maximum of one device for a large meta device. You may specify the minimum number of devices to provide improved performance. Click More Options or Fewer Options to hide or show the additional allocation parameters.
48
49
50
51
Figure 20 Details of Proposed Path Dialog Box with Properties File False (default) Setting
52
Figure 21 Details of Proposed Path dialog box with Properties file True Setting
Figure 22 on page 54 shows how the table appears after you click Show All. SPS provides a set of alternate paths as a convenience feature. Click Show All if you want to change to a different set of ports presented as alternatives. You can clear a proposed path, and then select an alternate path. In addition, you can clear a path if you decide to reduce the amount of storage allocated. Click Show Selected to remove the unselected paths from the display. Click Show Log to see how SPS chose the paths for your allocation request. If SPS could not find appropriate devices, the log provides details to help you analyze why. You should export the data from this dialog box and use the file for review purposes in your provisioning process, including review by change control boards.
53
54
For information about executing and managing tasks, refer to Executing allocation and deallocation tasks on page 64.
Deallocating storage
At times, you may have to deallocate storage, for example to:
Reclaim storage that was temporarily allocated to an application or department. Remove storage from a host that is being decommissioned. Migrate an application between hosts. Consolidate storage resources for increased efficiency.
Verifying that host file systems, logical volumes, or volume groups are no longer in use before devices that they use are deallocated.
55
Performing tasks that are often overlooked or forgotten when deallocating storage, such as removing masking access rights, removing Symmetrix devices from device groups, and deallocating replica devices when a primary device is deallocated (in your deallocation policy, you can choose which of these tasks is performed).
Deallocating storage with the Storage Provision Service removes the relationship between hosts or unidentified ports and the storage-array devices to which they have access. Table 5 lists starting points for some common deallocation tasks. Refer to Table 6 on page 57 for additional starting points and a list of paths that are presented for deallocation depending on your starting point.
Table 5 Starting points for deallocation tasks To deallocate... All devices from a host. All host devices using a particular HBA. A host device used by a particular application or department. A storage device from all hosts that have access to it. All hosts, HBAs, host devices, and storage devices within a user-defined group (such as an application group). Start the deallocation task here... Host HBA Host device Storage device User-defined group
Note: You can only deallocate Fibre Channel Fabric connected paths; you cannot use the Deallocation wizard to deallocate storage connected through SCSI or Fibre Channel Arbitrated Loop.
Deallocation process
The deallocation process through the Storage Provisioning Service includes these steps: 1. Assign deallocation permissions To deallocate storage, you must have permissions to create deallocation policies and to perform deallocation actions on the hosts and arrays involved in the deallocation. 2. Create deallocation policies These policies define the actions to be performed during a deallocation task, such as rediscovering a host, unmapping devices from the front end of a storage array, and dissolving meta devices.
56
3. Select an initial object in the Console Select a host, host device, host port, unidentified port, or storage device. 4. Start the service Select Deallocate from the Allocation menu or by right-clicking and selecting Allocation, Deallocate. 5. Confirm the objects and select a policy - Add or remove objects from the deallocation task and select a policy to use. 6. Select the paths to be deallocated Confirm the paths from host devices to storage devices that will be deallocated and add related paths if necessary. 7. Review the deallocation task Review the final proposed deallocations. 8. Execute immediately or later Add the task to a task list in the tree panel, and start it immediately or defer to a later time. The remainder of this section discusses certain aspects of the deallocation process in more detail.
Host port.
Table 6 Effects of Deallocation on Managed Objects (2 of 2) Selected Object Unidentified port Objects Affected by Deallocation Unidentified port. Paths Presented for Deallocation All paths from WWN of port to storage devices, based on masking, and all paths from those devices to other host devices. All paths from host device to its storage device, and all paths from those devices to other host devices. All paths from known host devices to storage device. All paths from WWNs of ports to storage device, based on masking. Refer to rows above to see which paths are presented for each object type.
Host device
Host device.
Storage device
Storage device.
User-defined group
All hosts, unidentified ports, host devices, and storage devices in the group.
58
The Deallocation wizard does not support the selected object. Refer to Table 6 on page 57 to see which objects are supported. The selected object is not part of any Fibre Channel-connected paths. Access to the selected object is not managed through masking access rights, or masking is disabled. You selected a storage device that is not mapped to any storage ports. You selected a storage device that is not exposed to any host ports through masking.
To determine whether a host has paths that can be deallocated, drag the host to a Path Details view. For a storage array device, use the Masking view.
59
On this screen, select the paths that you want to deallocate by clearing and selecting the checkboxes in the first column of the table. Use shift-click to select or clear a range of contiguous rows. For the objects you selected in the previous wizard screen, all paths between host devices and storage devices are selected.
You do not unintentionally jeopardize the reliability or performance of host logical objects, for example, reducing the paths between a database and its storage to a single path or corrupting a volume group by removing a logical volume. You do not leave paths intact for storage that you intend to completely deallocate. For example, if you intend to deallocate a storage device and did not select all the associated host devices.
60
Note: If a device is mapped with no masking records, it will not be displayed as a path. However, if the last masked path to a device is deallocated, and unmapping is specified in the deallocation policy, then the device will be unmapped from all ports on the array, including those not displayed in the Paths to Deallocate table.
61
In addition, some primary devices may have replicas that do not have paths and, therefore, do not appear on the Paths to Deallocate screen. After you click Next on this screen, the wizard lists those replicas in a dialog box. If you selected the Deallocate replicas if primary deallocated option, those replicas will also be deallocated. If you do not want to deallocate those replicas, edit the policy and clear this option. You can edit the policy from the previous or next wizard screen. If you selected the Delete device (CLARiiON) or dissolve meta device if not SRDF (for Symmetrix, requires unmap) option in the Deallocation policy, meta devices that are completely deallocated (all paths to the device are removed) will be dissolved. SRDF (R1 and R2) devices are not dissolved. If Deallocate replicas if primary deallocated is also selected, any replica meta devices that are completely deallocated are also dissolved. However, a replica that does not have any paths is only deallocated if its primary device is completely deallocated. To identify the primary device associated with a replica, drag the replica from the dialog box to an SRDF or TimeFinder view.
62
local BCV), ARM will remove the device from both the device groups. The deallocation will fail when attempting to remove the device from the R2 device group if that group was created and managed by a GNS. In Service Pack 4 and higher, ARM will not remove devices from the R2 device group as the R2 device group could be managed by GNS. In the above example, BCV to R2 will be removed from the R1 device group only and the GNS will automatically mirror the device group in R2 with the BCV removed.
63
If you do not want to deallocate those replicas, edit the deallocation policy and clear the Deallocate replicas if primary deallocated option. You can edit the policy from the first and last screens of the Deallocation wizard. To identify the primary device a replica is associated with, drag the replica to an SRDF or TimeFinder view. Although the wizard dissolves all masking and mapping relationships between hosts and storage devices, you still must perform some actions on the host to complete the deallocation process.
64
After an SPS task has been added to the task list, you can view properties for the task before, during, and after execution. Task Properties, as shown in the next section, provide provisioning action details that will be of interest to change control boards and senior administrators.
Task lists
The Ionix ControlCenter task list provides a means to defer tasks or lists of tasks for future execution. The advantages of deferring tasks include:
Allowing time for technical review or permissions. Ensuring execution time to accommodate shift changes (some allocation tasks may only be performed on a certain shift). Supporting the internal customer review process. Ensuring efficient operation by executing multiple actions from multiple requests in one session.
Task lists differ from scripts in that they execute one time only; they are not a repeated action like a backup batch file operation. You can monitor a task in the target panel, observing the execution of each step. A checkbox in the last dialog box in the Storage Provisioning Service triggers the Properties view for that task list, if immediately executing the new task. Note: Tasks remain in the tree panel until they are manually deleted. Figure 26 shows task lists in the Properties view. Note that some of the task lists have multiple tasks.
65
66
67
68
Figure 29 New Zoning Policy command and Zoning Policy Editor dialog box
To set the default zoning policy for a fabric, right-click the fabric and select Zoning, Set Default Zoning Policy. You can do this from within the Allocation wizard if necessary. SPS only applies a zoning policy if zone changes are needed to complete an allocation task. If two ports in an allocation path are already zoned, SPS does not verify that the ports are zoned according to the selected policy or modify the zone to satisfy the policy. For more information about zoning policies, refer to the online Help and the EMC ControlCenter Administration/User Guide.
Working with SPS in the Ionix ControlCenter Console
69
3. After the pair is selected, right-click the logical device or host and select Allocation, AutoPath.
70
71
3. Right-click a logical volume, and select Allocation, Extend Logical Volume. 4. The Extend Logical Volume dialog box appears. 5. Specify your required size increase. SPS determines the storage usage for this volume group and presents an allocation policy for review. If a question mark appears in the pool column, you will not be able to continue unless you select a storage pool. If the volume is striped, the minimum number of storage volumes will be the stripe column count. You will not be able to change this value. Note: This allocation may be larger than the request size. The following details how much of this storage is actually added to the file system or logical volume: For At most, increase the file system by no more than the specified size. For At least, increase the file system by no less than the specified lower bound. For Range, increase the file system by no less than the specified lower bound and no more than the upper bound.
74
5. An allocation policy is generated to match storage volumes used by the file system. The second screen shows the policy that will be used to query for devices. If a question mark appears in the pool column, you will not be able to continue unless you select a storage pool. You can also change the suggested pool or make other changes to the policy. Click Next when complete. 6. The third screen shows Path Details for the devices that will be added to the VERITAS volume that is being modified. You may manually override any of the suggestions. Click Next to continue. 7. The final screen is the summary screen that lets you review the provisioning request. You can choose to execute the request now or later. Note: SPS does not support extending file systems managed by VERITAS Volume Manager on Windows hosts.
75
9. The final screen lets you review the provisioning request. After review, you can choose to execute the request now or later.
1. Explore and find the volume that you want to extend or shrink. 2. Right-click the volume and select Allocation> Manually> Extend Logical/VERITAS Volume or Shrink Logical/VERITAS Volume. The Extend/Shrink a Logical Volume dialog box (AIX, HP-UX, or Solaris) appears and prompts you for new size information for the volume. To extend or reduce a volume group on a host using only storage resources that are currently configured on the host: 1. Explore and find the volume group. 2. Right-click the volume group and select Allocation, Manually, Extend Volume Group or Host, Reduce:
If you choose Extend, the Extend a Volume Group dialog box appears and allows you to specify the physical volumes that you want to add to the volume group. If you choose Reduce, the Reduce a Volume Group dialog box appears and allows you to specify the physical volumes that you want to remove from the volume group.
Provisioning clusters
Clusters can be provisioned in the same way a single host is provisioned. You must select the set of hosts initially, or drag the other hosts into the first SPS dialog box. In addition, a dialog box lets you select additional hosts for local snapshots or remote copies. Clusters require special maintenance beyond simply allocating the same storage to multiple hosts. There are often lists of storage that need to be maintained on all the servers, or volume manager configurations that need to be modified on each host.
77
For the safety of your server, SPS creates backups of previous sd.conf files. A rolling backup of 10 sd.conf files is saved so that you can easily revert to a previous version if you encounter any difficulty. A backup file is created for each LUN ID added.
78
reconfigure reboot (reboot -- -r) to present the devices to the host. If you do not use a blanket sd.conf file, a reboot is required to load the new sd.conf file parameters into the kernel. Note: Boot times are extended if a blanket sd.conf file is configured.
79
Unidentified ports are physical ports that are not associated with an adapter. They are
accessed in the Connectivity> Unidentified Ports folder in the tree panel. To identify an unidentified port with a user-defined object: 1. In the Console tree panel, expand Connectivity, Unidentified Ports. 2. Right-click an unidentified port, and select Topology> Associate Port. 3. The Associate wizard appears with the port WWN and vendor displayed. 4. Select a host from the list of user-defined objects, and click Next. 5. Select the container you want to identify with the unidentified port, and click Next. 6. On the final page of the wizard, review the fields that are to be set for the associated port and click Finished, or click Back to make changes. 7. Verify that a new adapter appears in the tree. Expand the Hosts folder, the host with which you associated the port, and then Adapters. Note: If you have mistakenly identified a port, you can use the Associate wizard to reidentify the port with the correct device.
80
81
82
CHAPTER 3 Troubleshooting
This chaper describes errors that may occur due to external forces such as servers that are shut down, administrators that use other applications that conflict with Storage Provisioning Services (SPS), and normal errors due to malfunctioning hardware. In most cases, the errors may be examined and corrective action applied. This chapter contains the following sections:
Solaris
If you allocate to Solaris, and the Rescan I/O action fails with the message:
Did not find any new devices.
The sd.conf was updated, and you need to reboot the host with the command:
Troubleshooting
83
Troubleshooting
reboot -- -r
HP-UX
If you allocate storage to HP-UX host devices, and the Rescan I/O action fails with the message: Could not match one or more allocated paths to any host devices. A Reboot of the host may be necessary. Perform the following procedure: 1. Issue the following commands on the host: ioscan -fnC disk
insf -e -C disk
2. In the Ionix ControlCenter Console, right-click the host and select Rediscover. After the rediscovery finishes, verify whether the new devices were allocated to the host. 1. In the Console tree panel, expand Hosts and then the host to which you want to allocate the storage. 2. Right-click the Host Devices folder and select Properties. If the new devices appear in the Properties view, right-click the task list and select Retry.
Windows 2000
Rescan will work depending on the HBA type and other conditions. Some HBAs that successfully rescan once will fail finding new logical devices on the second rescan. Reboot the host if the rescan action fails to discover the new devices.
84
Troubleshooting
To view the Allocation Request Details log, click Show Log on the Details of Proposed Path page of the Allocation wizard. A detailed analysis (called the Primary Analysis) appears at the bottom of the log. Scroll to the bottom of the Allocation Request Details dialog box to see the Primary Analysis. The analysis shows which candidate devices meet the constraints (such as RAID level or device size) of the allocation request. After you review the Primary Analysis to see which constraints prevented SPS from locating appropriate devices, you can modify your request. For example, you can:
Change the constraints on the first page of the wizard, such as the amount of storage you are requesting or the number of devices. Modify the constraints in the allocation policy, such as the RAID level, replication class, or whether meta devices must be used. Add devices to the storage pool used in this request. Ensure the new devices meet the constraints that caused this request to fail. Choose a different storage pool in the allocation policy. Choose a pool that contains devices that meet the constraints of the request.
At the top of the log, after the allocation request details, a list of the Storage Provisioning Service actions and results appears. Scroll through the list to see how SPS chose devices and paths for your allocation request (or, if the request failed, why it failed). The log refers to amounts and sizes of devices. To see the actual names of the devices SPS evaluated, click Details. You can also use the following methods to determine why the Allocation Wizard did not find requested devices.
Topology
Ensure that the chosen host is connected through a SAN using Topology view. You can verify that the storage type chosen in the topology is also connected to the same fabric.
Storage Pools
Use the Free Space view on the storage pool in the allocation policy. It will provide a table of available logical devices. You will then need to sort the table by the device type to match the RAID level in the policy. Also, you will need to verify that the storage type in the policy matches the arrays in the Storage column.
85
Troubleshooting
Ports
If ports do not have LUN ID slots available, then path selection might fail. You can use the Free Space view from the host and drill down to storage ports to see if there are available slots. Also, the Properties view for the port shows the number of devices on the port. In addition, certain hosts, like HP-UX, require appropriate port flag settings for the Symmetrix array.
Constraints
Disable storage policy constraints to see if available logical devices are selected. This will give you a clue as to where the problem might be. Each checkbox in the storage policy editor is considered a constraint.
Troubleshooting
Fibre Channel
87
Troubleshooting
88
List of actions................................................................................................... 89
List of actions
Bus rescan
Solaris and Windows 2000 bus rescans are performed for all SPS commands in order for the host to discover new logical devices presented.
Edit sd.conf
It is necessary to edit the Solaris disk configuration file, sd.conf, in order to add the new LUNs presented to the host. The system administrator will need to do a reconfiguration reboot if SPS adds an entry since in that case, the bus rescan will not discover the new disk. sd.conf is edited on every SPS configuration.
89
Expand Solaris VERITAS Volume Manager storage with PowerPath on CLARiiON array
If you have this configuration, refer to the following document on Powerlink for critical setup information: PowerPath and VERITAS Volume Manager (Solaris) with CLARiiON Storage Systems.
PowerPath reconfiguration
The PowerPath reconfiguration command is executed on those systems running PowerPath. This action is executed whenever storage is added to a host.
90
Policy Select the Disable Host Action option in the Allocation Policy Editor or Deallocation Policy Editor dialog box to prevent host actions. Host Based Edit the host agent configuration file (/usr/ecc/exec/msr520/msr.ini for Solaris and C:\ecc\exec\msr520\mnr.ini for Windows) to include the following lines:
# [[MNR]] Disable_SPS=YES #
This entry will prevent SPS from executing host functions, overriding values specified in the allocation or deallocation policy. This will prevent accidental actions from happening if the wrong policy is used.
List of actions
91
92