Dell PowerVault MD3200i and MD3220i Storage Arrays Owner’s Manual Regulatory Model: E03J Series and E04J Series Regulatory Type: E03J001 and E04J001
Notes, Cautions, and Warnings NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates potential damage to hardware or loss of data if instructions are not followed. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. ____________________ Copyright © 2015 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . About This Document . . . . . . . . . . . . . . . . . . 19 19 Inside the Box of the Dell PowerVault MD3200i Series Storage Array 19 MD3200i Series Storage Array . . . . . . . . . . . Dell PowerVault Modular Disk Storage Manager . Dell PowerVault Modular Disk Configuration Utility Other Information You May Need 2 . . . . . . . . . . . . Planning: About Your Storage Array . Overview . 20 20 20 . . . 23 . . . . . . . . . . .
RAID Controller Module Connectors and Features . . . 32 . . . . 34 . . . . . . . . . . . . . . . . 34 RAID Controller Module—Additional Features . Battery Backup Unit Storage Array Thermal Shutdown System Password Reset . . . . . . . . . 34 . . . . . . . . . . . . . . 35 . . . . . . . . . . . . . 35 . . . . . . . . . . . . . . . . . . 35 Cache Functions and Features . Cache Mirroring. Write-Back Cache . . . . . . . . . . . . . . . . . Write-Through Cache . 4 . . . . . . . . . . . . . .
Disk Group Operations. . . . . . . . . . . . . . . . . . RAID Level Migration . . . . . . . . . . . . . . . . Segment Size Migration . . . . . . . . . . . . . . 45 46 . . . . . . . . . . . . . . . 46 Disk Group Defragmentation . Disk Group Operations Limit . . . . . . . . . . . 46 . . . . . . . . . . . . 47 RAID Background Operations Priority . . . . . . . . . 47 . . . . . . . 48 Disk Migration . . . . . . . . . . . . . . . . . . . 48 Disk Roaming . . . . . . . . . . . . . . . . . . .
Array Management Window 6 . . . . . . . . . . . . 63 Configuration: About Your Storage Array 65 Out-of-Band and In-Band Management . Storage Arrays . . . . . . . . 65 . . . . . . . . . . . . . . . . . . . . . . 66 Adding Storage Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . 68 . . . . . . . . . . . . . . 69 Setting Up Your Storage Array Locating Storage Arrays Naming or Renaming Storage Arrays . Setting a Password . 66 . . . . . . . 70 . . . . . . . . . . . . . . . .
Creating CHAP Secrets . . . . . . . . . . . . . . . . . Target CHAP Secret 84 . . . . . . . . . . . . . . . 85 . . . . . . . . . . . . . . . . 85 Initiator CHAP Secret . Valid Characters for CHAP Secrets Changing the iSCSI Target Identification . . . . . . . . 85 . . . . . . . . 86 . . . . . 86 . . . . . . . . . . . . 87 Changing the iSCSI Target Discovery Settings Configuring the iSCSI Host Ports Advanced iSCSI Host Ports Settings . . . . . . . . . .
Removing a Host Group . Host Topology . . . . . . . . . . . . . . 100 . . . . . . . . . . . . . . . . . . 100 . . 101 . . . . . . . . . . . . . . . 102 Starting or Stopping the Host Context Agent . I/O Data Path Protection . Managing Host Port Identifiers . . . . . . . . . . . . 103 10 Configuration: Disk Groups and Virtual Disks 105 Creating Disk Groups and Virtual Disks . Creating Disk Groups . . . . . . . 105 . . . . . . . . . . . . . . . 106 Locating a Disk Group . . . . . . . . . . .
Enclosure Loss Protection . . . . . . . . . . . . . . . . Host-to-Virtual Disk Mapping . . . . . . . . . . . . . . Creating Host-to-Virtual Disk Mappings . . . . . . 126 128 129 Modifying and Removing Host-to-Virtual Disk Mapping 130 Changing Controller Ownership of the Virtual Disk 131 Removing Host-to-Virtual Disk Mapping . . . . . . 132 Changing the RAID Controller Module Ownership of a Disk Group 132 Changing the RAID Level of a Disk Group . . . . .
11 Configuration: Premium Feature—Snapshot Virtual Disks . . . . . . . . . . . . . . . . . . . . . 149 Scheduling a Snapshot Virtual Disk . . . . . . . . . . 150 Common Reasons for Scheduling a Snapshot Virtual Disk 150 Guidelines for Creating Snapshot Schedules . . 151 Enabling and Disabling Snapshot Schedules. . . 152 Creating a Snapshot Virtual Disk Using the Simple Path 152 About the Simple Path . . . . . . . . . . . . . .
12 Configuration: Premium Feature—Virtual Disk Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Types of Virtual Disk Copies . . . . . . . . . . . . . . . 174 Offline Copy . . . . . . . . . . . . . . . . . . . . . 174 Online Copy . . . . . . . . . . . . . . . . . . . . . 175 Creating a Virtual Disk Copy for an MSCS Shared Disk 176 . . . . . . . . . 176 . . . . . . . . . . . . . 177 . . . . . . . . . . . . . . 178 . . . . . . . . . . . . . . . . .
13 Configuration: Premium Feature—Upgrading to High-Performance-Tier . . . . . . . . . . . . . 187 14 Configuration: Device Mapper Multipath for Linux 189 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 . . . . . . . . . . . . . . . . 190 Using DM Multipathing Devices. Prerequisite Steps Device Mapper Configuration Steps . . . . . . . Linux Host Server Reboot Best Practices . . . . Important Information About Special Partitions 191 195 . 196 . . . . . . . . .
16 Management: Installing Array Components 211 Recommended Tools . . . . . . . . . . . . . . . . . . . 211 Front Bezel (Optional) . . . . . . . . . . . . . . . . . . 212 Removing the Front Bezel . . . . . . . . . . . . . 212 Installing the Front Bezel . . . . . . . . . . . . . . 212 . . . . . . . . . . . . . . . . . . . . . . . 213 Hard Drives. Removing a Hard-Drive Blank . . . . . . . . . . . 213 Installing a Hard-Drive Blank . . . . . . . . . . . . 214 . . . . . . . . . . . . . .
Backplane . . . . . . . . . . . . . . . . . . . . . . . Installing the Backplane 231 . . . . . . . . . . . . . 234 17 Management: Firmware Inventory Viewing the Firmware Inventory . . . . 235 . . . . . . . . . . . 235 18 Management: System Interfaces . Microsoft Services . 231 . . . . . . . . . . . . Removing the Backplane . . . . . . 237 . . . . . . . . . . . . . . . . . . 237 Virtual Disk Service . . . . . . . . . . . . . . . . Volume Shadow-Copy Service . . . . . . . . . .
Finding Nodes Using Go To . . . . . . . . . . . . . . . . . . . . . . 248 . . . . . . . . . . . . . . . . . . . . . . . 250 Recovering From an Unresponsive Storage Array Condition 251 Locating a Physical Disk. . . . . . . . . . . . 255 . . . . . . . . . . . . 256 . . . . . . . . . . . . . . . . . . . 257 Locating an Expansion Enclosure . Capturing the State Information . SMrepassist Utility 253 . . . . . . . . . . . . . . . . Unidentified Devices 258 . . . . . . . . . . . . . . . . . .
Troubleshooting a Wet Storage Array . Troubleshooting a Damaged Array . . . . . . . . 269 . . . . . . . . . . 270 Troubleshooting RAID Controller Modules Conditions . . . . . . . 271 . . . . . . . . . . . . . . . . . . . . 271 . . . . . . . . . . . . . . 271 . . . . . . . . . . . . . . . . . . . . 271 . . . . . . . . . . . . . . . . . . . . . 272 Invalid Storage Array . ECC Errors . PCI Errors Critical Conditions. . . . . . . . . . . . . . . . . Noncritical Conditions 21 Getting Help .
Contents 17
1 Introduction NOTE: Unless specified, MD3200i Series represents Dell PowerVault MD3200i and Dell PowerVault MD3220i storage arrays. WARNING: See the Safety, Environmental, and Regulatory Information document for important safety information before following any procedures listed in this document. About This Document This guide familiarizes you with the functions of the Dell PowerVault MD3200i Series storage array.
• Mounting rails (2) (optional) • MD3200i Series resource media • Rack Installation Instructions. • Getting Started With Your System (provides an overview of enclosure features, setting up your enclosure, and technical specifications). MD3200i Series Storage Array The Dell PowerVault MD3200i Series is a 2U rack-mounted external redundant array of independent disks (RAID) storage array capable of accommodating up to twelve 3.5" or twenty four 2.5" 6.0-Gbps SerialAttached SCSI (SAS) disks.
• The Deployment Guide provides installation and configuration instructions for both software and hardware. • The Storage Manager CLI Guide provides information about using the command line interface (CLI). • The Resource media contains all system management tools. • The Systems Support Matrix provides information on supported software and hardware for MD systems. The document is available at dell.com/support/manuals. • The Dell PowerEdge Cluster Documentation is available at dell.
22 Introduction
2 Planning: About Your Storage Array Overview The MD3200i Series storage array is designed for high availability, offering redundant access to data storage. It features support for both single and dual RAID controller configuration. The Dell PowerVault MD3200i storage array provides 1.0-Gbps 1000 BaseT connectivity to the host server and enables access to 32 physical hosts.
Hardware Features Front-Panel Features and Indicators Figure 2-1. Front-Panel Features and Indicators—Dell PowerVault MD3200i 1 2 3 4 5 6 Figure 2-2.
Figure 2-3. Front-Bezel Features and Indicators 1 2 3 Item Indicator, Button, or Connector 1 Enclosure status LED Icon Description The enclosure status LED lights when the enclosure power is on. Lights blue during normal operation. Blinks blue when a host server is identifying the enclosure or when the system identification button is pressed. Lights amber as enclosure boots or is reset.
Item Indicator, Button, or Connector Icon Description 3 Split mode LED This LED must be unlit as the split mode function is not supported by the MD3200i Series Storage Arrays. 4 System identification button The system identification button on the front control panel can be used to locate a particular enclosure within a rack. When the button is pushed, the system status indicators on the control panel and the RAID controller module(s) blink blue until the button is pushed again.
Back Panel Features and Indicators Figure 2-4.
Hard-Drive Indicator Patterns Figure 2-5.
Drive-Status Indicator Pattern Condition Off The physical disk is: • not yet discovered by the host server • is spun down for removal • not supported for the RAID controller module or is not in the physical disk slot NOTE: The drive status indicator remains off until all hard drives are initialized after system power is turned on. Drives are not ready for insertion or removal during this time.
Power Indicator Codes and Features Figure 2-6. Power Indicator Codes and Features 1 2 3 4 5 Item LED Type 1 DC power Icon Description The LED lights green when the DC output voltage is within the limit. If this LED is off, it indicates that the DC output voltage are not within the limit. 2 Power supply/cooling fan fault The LED lights amber when the DC output voltage is not within the limit or a fault with the fan is detected. If this LED is off, it indicates that no fault condition is present.
3 Planning: RAID Controller Modules RAID Controller Modules The RAID controller modules provide high-performance, advanced virtual disk configuration, and fault-tolerant disk subsystem management. Each RAID controller module contains 2 GB or 4 GB of mirrored cache for high availability and is protected by a battery powered cache offload mechanism. NOTE: The 4 GB mirrored cache is an optional feature.
RAID Controller Module Connectors and Features Figure 3-1. MD3200i Series iSCSI RAID Controller Module 1 8 3 2 9 10 11 4 5 12 13 14 15 16 6 17 7 18 19 Item Component Function 1 SAS OUT port Provides SAS connection for cabling to an expansion enclosure. 2 iSCSI IN port 0 Provides host-to-controller iSCSI 1Gbps Ethernet connection. 3 iSCSI IN port 1 Provides host-to-controller iSCSI 1Gbps Ethernet connection.
Item Component Function 8 SAS OUT port link/fault LED Lights green when all four links are connected. Lights amber when one to 3 links are disconnected. Off when all links in the port are disconnected or cable is disconnected. 9 iSCSI IN port link LED Lights green when ethernet connection at 1Gbps established. Off when there is no link. 10 Controller power LED Lights green when controller is turned on. Off when controller is not turned on.
Item Component Function 17 MAC address label Provides MAC addresses of iSCSI host ports and the management port. 18 Management port speed LED Lights green when ethernet connection is operating at 1000 Mbps. Lights amber when ethernet connection is operating at 100 Mbps. Off when ethernet connection is operating at 10 Mbps or is not active. 19 Management port activity LED Lights green when ethernet connection is active. Off when ethernet connection is not active.
Table 3-1. Shutdown Threshold Type Threshold Temperature Exceeding Event Description Nominal failure threshold A critical event is set Maximum failure threshold Shutdown of the system power supplies occurs within 3 minutes Shutdown threshold Shutdown of the system power supplies occurs within 5 seconds System Password Reset The storage array system password can be reset if it is forgotten. To reset the password, push and hold down the password reset switch for at least 5 seconds.
in order to increase controller performance. In dual-active controller configurations with Write-back Caching enabled, the write data is always mirrored to the cache of the second controller before completion status is issued to the host initiator. Write-Back Cache is enabled by default unless cache mirroring is disabled. Write-Through Cache In write-through cache, data is written to the physical disk before completion status is returned to the host operating system.
4 Planning: MD3200i Series Storage Array Terms and Concepts This chapter explains terms and concepts used for configuration and operation of MD3200i Series storage arrays. Physical Disks, Virtual Disks, and Disk Groups Physical disks in your storage array provide the physical storage capacity for your data. Before you can begin writing data to the storage array, you must configure the physical storage capacity into logical components, called disk groups and virtual disks.
NOTE: The MD3200i Series storage enclosure must contain at least two physical disks for proper operation. This is necessary because the physical disks are used to store configuration information. Physical Disk States Table 4-1 describes the various states of the physical disk, which are recognized by the storage array and reported in the MDSM application. Table 4-1.
Table 4-1. RAID Controller Physical Disk States (continued) Status Mode Description Physical Disk Status LED Offline Not applicable The physical disk has either been spun Green flashing down or had a rebuild aborted by user (3000 ms), Amber request. (3000 ms), and Off (3000 ms) Identify Assigned, The physical disk is being identified. Unassigned, Hot Spare in use, or Hot Spare standby N/A N/A Green flashing (250 ms) The indicated slot is empty, or the array cannot detect the physical disk.
Disk groups are always created in the unconfigured capacity of a storage array. Unconfigured capacity is the available physical disk space not already assigned in the storage array. Virtual disks are created within the free capacity of a disk group. Free capacity is the space in a disk group that has not been assigned to a virtual disk. Virtual Disk States The storage array recognizes the following virtual disk states. Table 4-2.
Each RAID level provides different performance and protection. You must select a RAID level based on the type of application, access, fault tolerance, and data you are storing. The storage array supports RAID levels 0, 1, 5, 6, and 10. The maximum number of physical disks that can be used in a disk group depends on the RAID level: • 192 for RAID levels 0, 1, and 10 • 30 for RAID levels 5 and 6.
is recommended for small databases or other applications that do not require large capacity. RAID 1 provides full data redundancy. For example accounting, payroll, or financial applications. RAID 5 RAID 5 uses parity and striping data across all physical disks (distributed parity) to provide high data throughput and data redundancy, especially for small random access.
The segment size or stripe element size specifies the size of data in a stripe written to a single disk. The storage array supports stripe element sizes of 8 KB, 16 KB, 32 KB, 64 KB, 128 KB, 256 KB, and 512 KB. The default stripe element size is 128 KB. Stripe width, or depth, refers to the number of disks involved in an array where striping is implemented. For example, a four-disk group with disk striping has a stripe width of four.
Consistency Check A consistency check verifies the correctness of data in a redundant array (RAID levels 1, 5, 6, and 10). For example, in a system with parity, checking consistency involves computing the data on one physical disk and comparing the results to the contents of the parity physical disk. A consistency check is similar to a background initialization. The difference is that background initialization cannot be started or stopped manually, while consistency check can.
Virtual Disk Operations Limit The maximum number of active, concurrent virtual disk processes per RAID controller module installed in the storage array is four. This limit is applied to the following virtual disk processes: • Background initialization • Foreground initialization • Consistency check • Rebuild • Copy back If a redundant RAID controller module fails with existing virtual disk processes, the processes on the failed controller are transferred to the peer controller.
When considering a segment-size change, two scenarios illustrate different approaches to the limitations: • If I/O activity stretches beyond the segment size, you can increase it to reduce the number of disks required for a single I/O. Using a single physical disk for a single request frees disks to service other requests, especially when you have multiple users accessing a database or storage environment.
Disk Group Operations Limit The maximum number of active, concurrent disk group processes per installed RAID controller module is one. This limit is applied to the following disk group processes: • Virtual disk RAID level migration • Segment size migration • Virtual disk capacity expansion • Disk group expansion • Disk group defragmentation If a redundant RAID controller module fails with an existing disk group process, the process on the failed controller is transferred to the peer controller.
The priority of each of these operations can be changed to address performance requirements of the environment in which the operations are to be executed. NOTE: Setting a high priority level impacts storage array performance. It is not advisable to set priority levels at the maximum level. Priority must also be assessed in terms of impact to host server access and time to complete an operation.
NOTE: Only disk groups and associated virtual disks with all member physical disks present can be migrated from one storage array to another. It is recommended that you only migrate disk groups that have all their associated member virtual disks in an optimal state. NOTE: The number of physical disks and virtual disks that a storage array supports limits the scope of the migration.
that has no existing physical disks. After the destination storage array is turned on and has successfully recognized the newly migrated physical disks, migration operations can continue. NOTE: Disk groups from multiple storage arrays must not be migrated at the same time to a storage array that has no existing physical disks. Use cold virtual disk migration for the disk groups from one storage array.
Host Server-to-Virtual Disk Mapping The host server attached to a storage array accesses various virtual disks on the storage array through its host ports. Specific virtual disk-to-LUN mappings to an individual host server can be defined. In addition, the host server can be part of a host group that shares access to one or more virtual disks. You can manually configure a host server-to-virtual disk mapping.
online and user-accessible. When the backup is completed, the snapshot virtual disk is no longer needed. You can create up to four snapshots per virtual disk. Snapshots are used to recover previous versions of files that have changed since the snapshot was taken. Snapshots are implemented using a copy-onwrite algorithm, which makes a backup copy of data the instant an error occurs. Data on a virtual disk is copied to the snapshot repository before it is modified.
Virtual Disk Copy Virtual disk copy is a premium feature to: • Back up data • Copy data from disk groups that use smaller-capacity physical disks to disk groups using greater capacity physical disks • Restore snapshot virtual disk data to the source virtual disk. Virtual disk copy generates a full copy of data from the source virtual disk to the target virtual disk in a storage array and can be performed either online or offline.
Virtual Disk Recovery You can use the Edit host server-to-virtual disk mappings feature to recover data from the backup virtual disk. This functionality enables you to unmap the original source virtual disk from its host server, then map the backup virtual disk to the same host server. Ensure that you record the LUN used to provide access to the source virtual disk. You need this information when you define a host server-to-virtual disk mapping for the target (backup) virtual disk.
The multi-path software identifies the existence of multiple paths to a virtual disk and establishes a preferred path to that disk. If any component in the preferred path fails, the multi-path software automatically re-routes I/O requests to the alternate path so that the storage array continues to operate without interruption. NOTE: Multi-path software available on the MD3200i series resource media.
Ownership can later be modified to balance workload according to actual usage. If virtual disk ownership is not manually balanced, it is possible for one controller to have the majority of the work, while the other controller is idle. Limit the number of virtual disks in a disk group. If multiple virtual disks are in a disk group, consider: • The impact each virtual disk has on other virtual disks in the same disk group. • The patterns of usage for each virtual disk.
• Least path weight with subset (Windows operating systems only)—The least queue depth with subset policy is also known as the least I/Os or least requests policy. This policy routes the next I/O request to a data path that has the least outstanding I/O requests queued. For this policy, an I/O request is simply a command in the queue. The type of command or the number of blocks that are associated with the command are not considered.
• RAID Controller modules • Virtual disks • Storage array totals NOTE: By default, all items are selected. b In Polling interval, select how often you want to update the performance statistics. NOTE: For an accurate elapsed time, do not use the Set RAID Controller Module Clocks option while using the Performance Monitor. Each time the polling interval elapses, the Performance Monitor queries the storage array again and updates the statistics in the table. 5 Click Start.
The Performance Monitor data provides information about how your storage array is performing. The data is presented in eight columns, which are described in this table. Use this data to make performance tuning decisions for your storage array. Table 4-3. Performance Monitor Table Description Column Headings Description Devices Controller, virtual disk or storage array total. Total IOs Cumulative IO’s per second from last start time. Read Percentage Percentage of cumulative IO’s that are READs.
60 Planning: MD3200i Series Storage Array Terms and Concepts
Configuration: Overview 5 Dell PowerVault Modular Disk Storage Manager (MDSM) online help contains information on how to use the MDSM application to perform the configuration and management tasks described in this document. You can access online help by clicking Help located at the top right corner of MDSM interface. For information on installing the MDSM, see the MD3200i and MD3220i Storage Array’s Deployment Guide at dell.com/support/manuals.
Enterprise Management Window The EMW provides high-level management of storage arrays. When you start MDSM, the EMW is displayed. The EMW has these tabs: • Devices tab—Provides information about the storage arrays. • Setup tab—Presents the initial setup tasks that guide you through adding storage arrays and configuring alerts. The Devices tab has a Tree view on the left side of the window that shows discovered storage arrays, unidentified storage arrays, and the status conditions for the storage arrays.
Inheriting the System Settings Use the Inherit System Settings option to import the operating system theme settings into the MDSM. Importing system theme settings affects features like font type, font size, color, and contrast in the MDSM. 1 Open the Inherit System Settings window in one of these ways: • Select Tools→ Inherit System Settings. • Select the Setup tab and click Inherit System Settings. 2 Select Inherit system settings for color and font. 3 Click OK.
• Logical tab—You can view the organization of the storage array by virtual disks, disk groups, free capacity nodes, and any unconfigured capacity for the storage array. • Physical tab—You can view the organization of the storage array by RAID controller modules, physical disks, and other hardware components. • Mappings tab—You can define the hosts, host groups, and host ports. You can change the mappings to grant virtual disk access to host groups and hosts and create storage partitions.
6 Configuration: About Your Storage Array Out-of-Band and In-Band Management You can manage a storage array in two ways: • Out-of-band management • In-band management Out-of-Band Management Using the out-of-band management method, data is separate from commands and events. Data travels through the host-to-controller interface, while commands and events travel through the management port Ethernet cables.
In-Band Management Using in-band management, commands, events, and data travel through the host-to-controller interface. Unlike out-of-band management, commands and events are mixed with data. NOTE: For detailed information on setting up in-band and out-of-band management see the Deployment Guide. When you add storage arrays by using this management method, you need to specify only the host name or IP address of the host.
NOTE: For Linux, set the default gateway so that broadcast packets are sent to 255.255.255.0. For Red Hat Enterprise Linux, if no gateway exists on the network, set the default gateway to the IP address of the NIC. NOTE: MDSM uses TCP/UDP port 2463 for communication to the MD Storage Array. Automatic Discovery of Storage Arrays The Automatic Discovery process sends out a broadcast message across the local subnetwork (subnet) and adds any storage array that responds to the message.
NOTE: When adding a storage array using in-band management with iSCSI, a session must first be established between the initiator on the host server and the storage array. For more information, see "Configuration: Using iSCSI" on page 83. NOTE: The host agent must be restarted before in-band management communication can be established. See "Starting or Restarting the Host Context Agent Software" on page 260. 3 Click Add.
• Configure the storage array—Create disk groups, virtual disks, and hot spare physical disks by using the Automatic configuration method or the Manual configuration method. For more information, see the PowerVault Modular Disk Storage Manager online help topics. • Map virtual disks—Map virtual disks to hosts or host groups. • Save configuration—Save the configuration parameters in a file that you can use to restore the configuration, or reuse the configuration on another storage array.
• In the AMW, select Storage Array→ Blink→ Storage Array. The LEDs blink on the physical disks in the storage array. 2 After locating the storage array, click OK. The LEDs stop blinking. 3 If the LEDs do not stop blinking, select Storage Array→ Blink→ Stop All Indications. A confirmation message is displayed. 4 Click OK. Naming or Renaming Storage Arrays Each storage array must be assigned a unique up to 30-character alphanumeric name.
5 Click Yes. The new storage array name is displayed in the Select storage array table. 6 Repeat step 2 through step 4 to name or rename additional storage arrays. NOTE: Avoid arbitrary names or names that may lose meaning in the future. Setting a Password You can configure each storage array with a password to protect it from unauthorized access. MDSM prompts for the password when an attempt is made to change the storage array configuration, such as, when a virtual disk is created or deleted.
6 Click OK. NOTE: You are not prompted for a password when you attempt to change the storage array configuration in the current management session. Password Guidelines Follow these guidelines when you create a password: • Use secure passwords for your storage array. A password must be easy for you to remember but difficult for others to determine. Consider using numbers or special characters in the place of letters, such as a 1 in the place of the letter I, or the at sign (@) in the place of the letter a.
Adding/Editing a Comment to an Existing Storage Array A descriptive comment, with an applicable storage array name, is a helpful identification tool. You can add or edit a comment for a storage array in the EMW only. To add or edit a comment: 1 In the EMW, select the Devices tab and select the relevant managed storage array. 2 Select Edit→ Comment. The Edit Comment dialog is displayed. 3 Type a 60-character comment. 4 Click OK.
Enabling Premium Features You can enable premium features on the storage array. To enable the premium features, you must obtain a feature key file specific to the premium feature that you want to enable from your storage supplier. To enable premium features: 1 From the toolbar in AMW, select Storage Array→ Premium Features. The Premium Features and Feature Pack Information window is displayed. 2 Select the relevant premium feature, and click Enable. The Select Feature Key File dialog is displayed.
2 Select or enter the percentage of unwritten data in the cache to trigger a cache flush in Start flushing. 3 Select or enter the percentage of unwritten data in the cache to stop a cache flush in progress in Stop flushing. 4 Select the appropriate Cache block size. A smaller cache size is a good choice for file-system use or databaseapplication use. A larger cache size is a good choice for applications that generate sequential I/O, such as multimedia.
3 Click OK. If you have set a password for the selected storage array, the Enter Password dialog is displayed. 4 Type the current password for the storage array. 5 Click OK. Configuring Alert Notifications MDSM can send an alert for any condition on the storage array that requires your attention. Alerts can be sent as e-mail messages or as Simple Network Management Protocol (SNMP) trap messages. You can configure alert notifications either for all the storage arrays or a single storage array.
To configure e-mail alerts: 1 Open the Configure Alerts dialog by performing one of these actions: • In the Tree view or the Table view on the Devices tab in the EMW, select a node, and then select Edit→ Configure Alerts. Go to step 3. • In the Setup tab in the EMW, select Configure Alerts. Go to step 2. 2 Select one of the following radio buttons to specify an alert level: • All storage arrays—Select this option to send an alert e-mail about events on all storage arrays.
• Adding an e-mail address—In Email address, type the e-mail address, and click Add. • Replacing an e-mail address—In the Configured email addresses area, select the e-mail address to be replaced, type the replacement e-mail address in Email address, and click Replace. • Deleting an e-mail address—In the Configured email addresses area, select the e-mail address, and click Delete.
• The e-mail addresses that you had previously configured are displayed in the Configured e-mail addresses area. • You must use fully qualified e-mail addresses, for example, name@mycompany.com. • You can configure multiple e-mail addresses before you click OK.
NOTE: The community name is an American Standard Code for Information Interchange (ASCII) string that identifies a known set of network management stations and is set by the network administrator. The default community name is the string “public”. The trap destination is the IP address or the host name of a computer running an SNMP management application. An example of a SNMP enabled management application is the Dell Management Console. For more information on Dell Management Console, see dell.
Battery Settings A smart battery backup unit (BBU) can perform a learn cycle. The smart BBU module includes the battery, a battery gas gauge, and a battery charger. The learn cycle calibrates the smart battery gas gauge so that it provides a measurement of the charge of the battery module. A learn cycle can only start when the battery is fully charged.
Setting the Storage Array RAID Controller Module Clocks You can use the Synchronize RAID Controller Module Clocks option to synchronize the storage array RAID controller module clocks with the storage management station. This option makes sure that the event timestamps written by the RAID controller modules to the Event Log match the event timestamps written to host log files. The RAID controller modules remain available during synchronization.
Configuration: Using iSCSI 7 Changing the iSCSI Target Authentication 1 In the AMW, select the Setup tab. 2 Select Manage iSCSI Settings. The Manage iSCSI Settings window is displayed and by default, the Target Authentication tab is selected. To change the authentication settings, select: • None—If you do not require initiator authentication. If you select None, any initiator can access the target.
Entering Mutual Authentication Permissions Mutual authentication or two-way authentication enables a client or a user to verify themselves to a host server and for the host server to validate itself to the user. This validation is accomplished in such a way that both parties are sure of the other’s identity. To add mutual authentication permissions: 1 In the AMW, select the Setup tab. 2 Select Manage iSCSI Settings. The Manage iSCSI Settings window is displayed. 3 Select the Mutual Authentication tab.
Initiator CHAP Secret The initiator CHAP secret is set on the host using the iSCSI initiator configuration program provided with the host operating system. If you are using the mutual authentication method, you must define the initiator CHAP secret when you set up the host. This must be the same CHAP secret that is defined for the target when defining mutual authentication settings. Target CHAP Secret If you are using CHAP secrets, you must define the CHAP secret for the target.
Changing the iSCSI Target Identification You cannot change the iSCSI target name, but you can associate an alias with the target for simpler identification. Aliases are useful because the iSCSI target names are not intuitive. Provide an iSCSI target alias that is meaningful and easy to remember. To change the iSCSI target identification: 1 In the AMW, select the Setup tab. 2 Select Manage iSCSI Settings. The Manage iSCSI Settings window is displayed. 3 Select the Target Identification tab.
• Select Specify Configuration, and type the IPv4 address to activate the target discovery. • Type the iSNS server IP address in the IPv6 settings area to activate the target discovery. After you manually enter an IP address, you can also click Advanced to configure the customized TCP listening ports. If you do not want to allow discovery sessions that are not named, select the Disallow un-named discovery sessions.
4 To use the IPv4 settings for the iSCSI host port, select Enable IPv4 and select the IPv4 Settings tab. 5 To use the IPv6 settings for the iSCSI host port, select Enable IPv6 and select the IPv6 Settings tab. 6 To configure the IPv4 and IPv6 settings: • To automatically configure the settings, select Obtain configuration automatically. This option is selected by default. • To manually configure the settings, select Specify configuration.
Advanced iSCSI Host Ports Settings NOTE: Configuring the advanced iSCSI host ports settings is optional. Use the advanced settings for the individual iSCSI host ports to specify the TCP frame size, the virtual LAN, and the network priority. Table 7-2. Advanced iSCSI Host Port Settings Setting Description Virtual LAN (VLAN) A method of creating independent logical networks within a physical network. Several VLANs can exist within a network. VLAN 1 is the default VLAN.
Viewing or Ending an iSCSI Session You may want to end an iSCSI session for the following reasons: • Unauthorized access—If an initiator whom you consider to not have access is logged on, you can end the iSCSI session. Ending the iSCSI session forces the initiator to log off the storage array. The initiator can log on if None authentication method is available.
Viewing iSCSI Statistics and Setting Baseline Statistics To view iSCSI statistics and set baseline statistics: 1 In the AMW toolbar, select Storage Array→ iSCSI→ Statistics. The View iSCSI Statistics window is displayed. 2 Select the iSCSI statistic type you want to view in the iSCSI Statistics Type area. You can select: • Ethernet MAC statistics • Ethernet TCP/IP statistics • Target (protocol) statistics 3 In the Options area, select: • Raw statistics—To view the raw statistics.
Edit, Remove, or Rename Host Topology If you give access to the wrong host or the wrong host group, you can remove or edit the host topology. To correct the host topology: Table 7-3. Host Topology Actions Desired Action Steps Move a host. 1 Click the Mappings tab. Move a host group. 2 Select the Host that you want to move, and then click Mappings→ Move. 3 Select a host group to move the host to and click OK. Manually delete the host, the host group. 1 Click the Mappings tab.
Configuration: Event Monitor 8 An event monitor is provided with Dell PowerVault Modular Disk Storage Manager (MDSM). The event monitor runs continuously in the background and monitors activity on the managed storage arrays. If the event monitor detects any critical problems, it can notify a host or remote system using email, Simple Network Management Protocol (SNMP) trap messages, or both.
Windows To enable or disable the event monitor: 1 Click Start→ Administrative Tools→ Services. or Click Start→ Settings→ Control Panel→ Administrative Tools→ Services. 2 From the list of services, select Modular Disk Storage Manager Event Monitor. 3 Select Action→ Properties. 4 To enable the event monitor, in the Service Status area, click Start. 5 To disable the event monitor, in the Service Status area, click Stop.
Configuration: About Your Host 9 Configuring Host Access Modular Disk Storage Manager (MDSM) software is comprised of multiple modules. One of these modules is the Host Context Agent. The host context agent is installed as part of the MDSM installation and runs continuously in the background.
• Create a host and assign an alias or user label. • Add or associate a new host port identifier to a particular host. • Change the host port identifier alias or user label. • Move or associate a host port identifier to a different host. • Replace a host port identifier with a new host port identifier. • Manually activate an inactive host port so that the port can gain access to host specific or host group specific LUN mappings. • Change the host port type to another type.
• Select the Mappings tab. Right-click the root node (storage array name), Default Group node, or Host Group node in the Topology pane to which you want to add the host, and select Define→ Host from the pop-up menu. The Specify Host Name window is displayed. 3 In Host name, enter an up to 30 character alphanumeric name. 4 Select the relevant option in Do you plan to use the storage partitions in this storage array? and click Next. The Specify Host Port Identifiers window is displayed.
The Preview window is displayed. 11 Click Finish. Removing Host Access To remove host access: 1 In the AMW, select the Mappings tab, select the host node in the Topology pane. 2 Perform one of these actions: • Select Mappings→ Remove. • Right-click the host node and select Remove from the pop-up menu. The Remove confirmation dialog is displayed. 3 Type yes. 4 Click OK. For more information, see the PowerVault Modular Disk Storage Manager online help topics.
• Right-click the storage array or the Default Group, and select Define→ Host Group from the pop-up menu. 4 Type the name of the new host group in Enter new host group name. 5 Select the appropriate hosts in the Select hosts to add area. 6 Click Add. NOTE: To remove hosts, select the hosts in the Hosts in group area, and click Remove. 7 Click OK. The host group is added to the storage array.
4 Click Yes. The host is moved to the selected host group with the following mappings: • The host retains the specific virtual disk mappings assigned to it. • The host inherits the virtual disk mappings assigned to the host group to which it is moved. • The host loses the virtual disk mappings assigned to the host group from which it was moved. Removing a Host Group To remove a host group: 1 In the AMW, select the Mappings tab, select the host node in the Topology pane.
• Changing a host type MDSM automatically detects these changes for any host running the host agent software. Starting or Stopping the Host Context Agent The host context agent discovers the host topology and starts and stops with the host. The topology discovered by the host context agent can be viewed by clicking Configure Host Access (Automatic) in the Configure tab in the MDSM.
4 Click Action→ Start. I/O Data Path Protection You can have multiple host-to-array connections for a host. Ensure that you select all the connections to the array when configuring host access to the storage array. NOTE: See the Deployment Guide for more information on cabling configurations. NOTE: For more information on configuring hosts see "Configuration: About Your Host" on page 95.
Managing Host Port Identifiers You can manage the host port identifiers that are added to the storage array. You can: • Add—Add or associate a new host port identifier to a particular host. • Edit—Change the host port identifier alias or user label. You can move (associate) the host port identifier to a new host. • Replace—Replace a particular host port identifier with another host port identifier. • Remove—Remove the association between a particular host port identifier and the associated host.
• Add by creating a new host port identifier—In New host port identifier, enter the name of the new host port identifier. 6 In User label, enter up to 30 character alphanumeric name. 7 In Associated with host, select the appropriate host or host group. 8 Select the host port identifier that you would like to manage from the list of host port identifiers in the Host port identifier information area.
10 Configuration: Disk Groups and Virtual Disks Creating Disk Groups and Virtual Disks Disk groups are created in the unconfigured capacity of a storage array, and virtual disks are created in the free capacity of a disk group. The maximum number of physical disks supported in a disk group is 30. The hosts attached to the storage array read and write data to the virtual disks. NOTE: Before you can create virtual disks, you must first organize the physical disks into disk groups and configure host access.
A disk group must be organized according to its related tasks and subtasks. For example, if you create a disk group for the Accounting Department, you can create virtual disks that match the different types of accounting transactions performed in the department: Accounts Receivable (AR), Accounts Payable (AP), internal billing, and so forth. In this scenario, the AR and AP virtual disks probably need more capacity than the internal billing virtual disk.
3 Type the name of the disk group (up to 30 characters) in Disk group name. 4 Select the appropriate Physical Disk selection choices, you can select: • Automatic, see step 6 • Manual, see step 9 5 Click Next. 6 For Automatic configuration, the RAID Level and Capacity window is displayed. 7 Select the appropriate RAID level in Select RAID level. You can select RAID levels 0, 1/10, 6, and 5.
Locating a Disk Group You can physically locate and identify all of the physical disks that comprise a selected disk group. An LED blinks on each physical disk in the disk group. To locate a disk group: 1 In the AMW, select the Logical tab. 2 Select the appropriate disk group and from the toolbar select Disk Group→ Blink. The LEDs for the selected disk group blink. 3 After locating the disk group, click OK. The LEDs stop blinking.
NOTE: Ensure that you create disk groups before creating virtual disks. To create virtual disks: 1 Choose one of these methods to start the Create Virtual Disk Wizard: • To create a virtual disk from unconfigured capacity in the storage array—On the Logical tab, select an Unconfigured Capacity node, and select Virtual Disk→ Create. Alternatively, you can right-click the Unconfigured Capacity node, and select Create Virtual Disk from the pop-up menu.
• Use recommended settings. • Customize settings. 6 Click Next. 7 In the Customize Advanced Virtual Disk Parameters window, select the appropriate Virtual Disk I/O characteristics type. You can select: • File system (typical) • Database • Multimedia • Custom NOTE: If you select Custom, you must select an appropriate segment size. 8 Select the appropriate Preferred RAID controller module ownership and click Next. The Specify Virtual Disk-to-LUN Mapping window is displayed.
2 Select a virtual disk. 3 In the toolbar, select Virtual Disk→ Change→ Modification Priority. The Change Modification Priority window is displayed. 4 Select one or more virtual disks. To select nonadjacent virtual disks, press click. To select adjacent virtual disks, press click. To select all of the available virtual disks, click Select All. Move the Select modification priority slider bar to the desired priority. 5 Click OK.
2 In the toolbar, select Virtual Disk→ Change→ Cache Settings. The Change Cache Settings window is displayed. 3 Select one or more virtual disks. To select nonadjacent virtual disks, press click. To select adjacent virtual disks, press click. To select all of the available virtual disks, click Select All. 4 In the Select cache properties area, you can select: • Enable read caching—to enable read caching. • Enable dynamic cache read prefetch—to enable dynamic cache read prefetch.
7 Click OK. Changing the Segment Size of a Virtual Disk You can change the segment size on a selected virtual disk. During this operation, I/O performance is affected, but your data remains available. Guidelines to proceed with changing the segment size: • You cannot cancel this operation after it starts. • Do not start this operation unless the disk group is in Optimal status. • MDSM determines the segment size transitions that are allowed.
The segment size modification operation begins. The virtual disk icon in the Logical pane shows an Operation in Progress status while the operation is taking place. NOTE: To view the progress or change the priority of the modification operation, select a virtual disk in the disk group, and select Virtual Disk→ Change→ Modification Priority. Changing the I/O Type You can specify the virtual disk I/O characteristics for the virtual disks that you are defining as part of the storage array configuration.
NOTE: If you selected the Custom option, select your preferred dynamic cache read prefetch setting (enabled/disabled) and segment size (8 KB to 512 KB). 2 Click OK. Choosing an Appropriate Physical Disk Type You can create disk groups and virtual disks in the storage array. You must select the capacity that you want to allocate for the virtual disk from either unconfigured capacity or free capacity available in the storage array.
Whenever the power is turned off and turned on again, all of the securityenabled physical disks change to a security locked state. In this state, the data is inaccessible until the correct security key is provided by a RAID controller module. You can view the self encrypting disk status of any physical disk in the storage array from the Physical Disk Properties dialog.
NOTE: If you have not created a security key for the storage array, the Create Security Key option is active. If you have created a security key for the storage array, the Create Security Key option is inactive with a check mark to the left. The Change Security Key option, the Save Security Key option, and the Validate Security Key option are now active. The Secure Physical Disks option is displayed in the Disk Group menu.
Creating a Security Key When you create a security key, it is generated by and securely stored by the array. You cannot read or view the security key. A copy of the security key must be kept on some other storage medium for backup in case of system failure or for transfer to another storage array. A pass phrase that you provide is used to encrypt and decrypt the security key for storage on other media. When you create a security key, you also provide information to create a security key identifier.
The pass phrase that you enter is masked. NOTE: Create Key is active only if the pass phrase meets the above mentioned criterion. 5 In Confirm pass phrase, re-enter the exact string that you entered in Pass phrase. Make a record of the pass phrase that you entered and the security key identifier that is associated with the pass phrase. You need this information for later secure operations. 6 Click Create Key.
To change the security key: 1 In the AMW toolbar, select Storage Array→ Physical Disk Security→ Change Security Key. The Confirm Change Security Key window is displayed. 2 Type yes in the text field, and click OK. The Change Security Key window is displayed. 3 In Secure key identifier, enter a string that becomes part of the secure key identifier. You may leave the text box blank, or enter up to 189 alphanumeric characters without white space, punctuation, or symbols.
Saving a Security Key You save an externally storable copy of the security key when the security key is first created and each time it is changed. You can create additional storable copies at any time. To save a new copy of the security key, you must provide a pass phrase. The pass phrase you choose does not need to match the pass phrase used when the security key was created or last changed. The pass phrase is applied to the particular copy of the security key you are saving.
Validate Security Key A file in which a security key is stored is validated through the Validate Security Key dialog. To transfer, archive, or back up the security key, the RAID controller module firmware encrypts (or wraps) the security key and stores it in a file. You must provide a pass phrase and identify the corresponding file to decrypt the file and recover the security key.
Before you complete this option, make sure that the physical disk that you have selected is the correct physical disk. You cannot recover any of the data that is currently on the physical disk. After you complete the secure erase procedure, the physical disk is available for use in another disk group or in another storage array. For more information on the secure erase procedure, see the PowerVault Modular Disk Storage Manager online help topics.
To assign or unassign hot spare physical disks: 1 In the AMW, select the Physical tab. 2 Select one or more physical disks. 3 Perform one of these actions: • Select Physical disk→ Hot Spare Coverage. • Right-click the physical disk and select Hot Spare Coverage from the pop-up menu. The Hot Spare Physical Disk Options window is displayed.
12 Type yes and click OK. Hot Spares and Rebuild A valuable strategy to protect data is to assign available physical disks in the storage array as hot spares. A hot spare adds another level of fault tolerance to the storage array. A hot spare is an idle, powered-on, stand-by physical disk ready for immediate use in case of disk failure.
Hot Spare Drive Protection You can use a hot spare physical disk for additional data protection from physical disk failures that occur in a RAID level 1, or RAID level 5 disk group. If the hot spare physical disk is available when a physical disk fails, the RAID controller module uses redundancy data to reconstruct the data from the failed physical disk to the hot spare physical disk.
CAUTION: Enclosure loss protection is not guaranteed if a physical disk has already failed in the disk group. In this situation, losing access to an expansion enclosure and consequently another physical disk in the disk group causes a double physical disk failure and loss of data. Enclosure loss protection is achieved when you create a disk group where all of the physical disks that comprise the disk group are located in different expansion enclosures. This distinction depends on the RAID level.
Table 10-2. Criteria for Enclosure Loss Protection (continued) RAID Level Criteria for Enclosure Loss Protection RAID level 1 Ensure that each physical disk in a mirrored pair is located in a different expansion enclosure. This enables you to have more than two physical disks in the disk group within the same expansion enclosure.
• Each host has its own LUN address space. MDSM permits the same LUN to be used by different hosts or host groups to access virtual disks in a storage array. • Not every operating system has the same number of LUNs available. • You can define the mappings on the Mappings tab in the AMW. See "Using the Mappings Tab" on page 96. Creating Host-to-Virtual Disk Mappings Guidelines to define the mappings: • An access virtual disk mapping is not required for an out-of-band storage array.
All defined hosts, host groups, and the default group is displayed in the list. NOTE: When configuring an iSCSI storage array, including the MD3200i or MD3220i, if a host or a host group is selected that does not have a SAS host bus adapter (SAS HBA) host port defined, a warning dialog is displayed. 5 In Logical unit number, select a LUN. The supported LUNs are 0 through 255. 6 Select the virtual disk to be mapped in the Virtual Disk area.
• Right-click the virtual disk, and select Change Mapping from the pop-up menu. 3 In Host group or host, select the appropriate host group or host. By default, the drop-down list shows the current host group or the host associated with the selected virtual disk. 4 In Logical unit number, select the appropriate LUN. The drop down list shows only the currently available LUNs that are associated with the selected virtual disk. 5 Click OK.
During a virtual disk copy, the same RAID controller module must own both the source virtual disk and the target virtual disk. Sometimes both virtual disks do not have the same preferred RAID controller module when the virtual disk copy starts. Therefore, the ownership of the target virtual disk is automatically transferred to the preferred RAID controller module of the source virtual disk.
associated source virtual disk. Changing the RAID controller module ownership of a virtual disk changes the preferred RAID controller module ownership of the virtual disk. During a virtual disk copy, the same RAID controller module must own both the source virtual disk and the target virtual disk. Sometimes both virtual disks do not have the same preferred RAID controller module when the virtual disk copy starts.
• The disk group must be in Optimal status before you can perform this operation. • Your data remains available during this operation. • If you do not have enough capacity in the disk group to convert to the new RAID level, an error message is displayed, and the operation does not continue. If you have unassigned physical disks, use the Disk Group>> Add Free Capacity (Physical Disks) option to add additional capacity to the disk group. Then retry the operation.
In this example, the mpath6 device contains two paths: -- /dev/sdf at Host 1, Channel 0, Target 0, LUN 2 --/dev/sde at Host 0, Channel 0, Target 0, LUN 2 3 Flush the multi-pathing device mapping using the following command: # multipath -f /dev/mapper/mapth_x where mapth_x is the device you want to delete. 4 Delete the paths related with this device using the following command: # echo 1 > /sys/block/sd_x/device/delete where sd_x is the SD node (disk device) returned by the multipath command.
Restricted Mappings Many hosts are able to map up to 256 logical unit numbers (LUNs) (0 to 255) per storage partition. However, the maximum number of mappings differs because of operating system variables, failover driver issues, and potential data problems. The hosts listed in the table have these mapping restrictions. If you try to map a virtual disk to a LUN that exceeds the restriction on these operating systems, the host is unable to access the virtual disk.
• You cannot move a host with a restricted host type into a storage partition that already has LUNs mapped that are greater than what is allowed by the restricted host type. For example, if you have a restricted host type that allows only LUNs up to 31, you cannot move that restricted host type into a storage partition that has LUNs greater than 31 already mapped. The Default Group on the Mappings tab has a default host type. You can change this type by selecting Storage Array→ Change→ Default Host Type.
a Change the RAID controller module ownership of a virtual disk—Go to step 2. b Change the RAID controller module ownership of a disk group—Go to step 3. 2 To change the RAID controller module ownership of a virtual disk, perform these steps: a Select the Logical tab. b Select the virtual disk. c Select Virtual Disk→ Change→ Ownership/Preferred Path. Alternatively, you can right-click the virtual disk and select Change→ Ownership/Preferred Path from the pop-up menu.
e Click Yes. The ownership of the disk group is changed. I/O to the disk group is now directed through this I/O path. You are finished with this procedure. NOTE: The disk group may not use the new I/O path until the multi-path driver reconfigures and recognizes the new path. This action usually takes less than 5 minutes. Changing the RAID Level of a Disk Group Use the Change→ RAID Level option to change the RAID level on a selected disk group.
Storage Partitioning A storage partition is a logical entity consisting of one or more virtual disks that can be accessed by a single host or shared among hosts that are part of a host group. The first time you map a virtual disk to a specific host or host group, a storage partition is created. Subsequent virtual disk mappings to that host or host group do not create another storage partition.
NOTE: You can include a secondary virtual disk in a storage partition. However, any hosts that are mapped to the secondary virtual disk has readonly access until the virtual disk is promoted to a primary virtual disk, or the mirror relationship is removed. Storage partitioning topology is the collection of elements, such as Default Group, host groups, hosts, and host ports shown as nodes in the Topology pane of the Mappings tab in the AMW. For more information, see "Using the Mappings Tab" on page 96.
5 Click Add. A message prompts you to confirm your selection. 6 To add the capacity to the disk group, click Yes. You can also use the Command Line Interface (CLI) on both Windows and Linux hosts to add free capacity to a disk group. After the capacity expansion is completed, additional free capacity is available in the disk group for creation of new virtual disks or expansion of existing virtual disks.
For more information, see the PowerVault Modular Disk Storage Manager online help topics. Disk Group Migration Disk group migration allows to you export a disk group so that you can import the disk group to a different storage array. You can also export a disk group so that you can store the data offline. NOTE: During the export process (before the disk group is imported) you lose access to the data on the exported disk group.
2 Stop all I/O and unmount or disconnect the file systems on the virtual disks in the disk group. 3 Back up the data on the virtual disks in the disk group. 4 Locate the disk group and label the physical disks. 5 Place the disk group offline. 6 Obtain blank physical disk modules or new physical disks. On the target storage array: 1 Verify that the target storage array has available physical disk slots. 2 Verify that the target storage array supports the physical disks that you import.
NOTE: Some settings cannot be imported during the import disk group procedure. The following settings are removed/cleared during the procedure: • Persistent reservations • Host-to-virtual disk mappings • Virtual disk copy pairs • Snapshot virtual disks and snapshot repository virtual disks • Remote mirror pairs • Mirror repositories Non-Importable Components Some components cannot be imported during the import disk group procedure.
• Recovered media error—Data could not be read by the physical disk on the first attempt but was successfully read on a subsequent attempt. Data is rewritten to the physical disk and verified and the error is reported to the event log. • Redundancy mismatches error—The first 10 redundancy mismatches that are found on the virtual disk are reported to the event log. • Unfixable error—Data could not be read and parity or redundancy information could not be used to regenerate the data.
8 Click OK. Suspending the Media Scan You cannot perform a media scan while performing another long-running operation on the disk drive such as reconstruction, copy-back, reconfiguration, virtual disk initialization, or immediate availability formatting. If you want to perform another long-running operation, you must suspend the media scan. NOTE: A background media scan is the lowest priority of the long-running operations.
148 Configuration: Disk Groups and Virtual Disks
11 Configuration: Premium Feature— Snapshot Virtual Disks NOTE: If you ordered this feature, you received a Premium Feature Activation card shipped in the same box as your Dell PowerVault MD storage array. Follow the directions on the card to obtain a key file and to enable the feature. NOTE: The snapshot feature allows up to 16 snapshots per LUN and 256 per array to be present at the same time. A snapshot virtual disk is a point-in-time image of a virtual disk in a storage array.
repository uses less disk space than a full physical copy, because the only data blocks that are stored in the snapshot repository virtual disk are those that have changed since the time of the snapshot. When you create a snapshot virtual disk, specify its location, capacity, schedule, and other parameters. You can disable or delete the snapshot virtual disk when it is not required. If you disable a snapshot virtual disk, you can recreate and reuse it the next time you perform a backup.
To implement this backup, select the first virtual disk and create a backup schedule that runs once a day, Monday through Friday, at a time between the end of the work day and 11PM. Do not select an end date. Apply the same schedule to the second virtual disk, then map the two snapshot virtual disks to your backup host server and perform your regular backup procedures. Remember to unmap the two resulting snapshot virtual disks before the next scheduled snapshot begins.
Enabling and Disabling Snapshot Schedules A scheduled snapshot operation can be temporarily suspended by disabling the schedule. When a schedule is disabled, the schedule timer continues to run but any scheduled snapshot operation do not occur. Scheduled Snapshot Icons Scheduled snapshots are displayed in the AMW using the following icons. Icon Description The schedule is enabled. Scheduled snapshots occurs. The schedule is disabled. Scheduled snapshots do not occur.
About the Simple Path Using the simple path, you can specify: • Snapshot Virtual Disk Name—A user-specified name that helps you associate the snapshot virtual disk to its corresponding snapshot repository virtual disk and source virtual disk. • Snapshot Repository Virtual Disk Name—A user-specified name that helps you associate the snapshot repository virtual disk to its corresponding snapshot virtual disk and source virtual disk.
NOTE: Mapping the snapshot virtual disk to the node that does not own the source virtual disk before the Snapshot enabling process is completed can result in the operating system mis-identifying the snapshot virtual disk. This, in turn, can result in data loss on the source virtual disk or an inaccessible snapshot.
2 In the AMW, select the Logical tab and select a valid source virtual disk. 3 Select Virtual Disk→ Snapshot→ Create. Alternatively, you can rightclick the source virtual disk and select Create Snapshot Virtual Disk from the pop-up menu. The Create Snapshot Virtual Disk Wizard - Introduction dialog is displayed. 4 Select Simple (Recommended) and click Next. The Specify Snapshot Schedule window is displayed. 5 Select Yes to set up a schedule for the new snapshot virtual disk creation.
13 To associate the mapping between the storage array name and the virtual disk name, run the host-based SMdevices utility. NOTE: If your operating system requires additional instructions, you can find those instructions in your operating system documentation.
– Dell recommends placing the snapshot repository virtual disk within the disk group of the source virtual disk. This ensures that if drives associated with the disk group are moved to another storage array, all the virtual disks associated with the snapshot virtual disk remain in the same group. • Snapshot Repository Virtual Disk Capacity—The snapshot repository virtual disk capacity is expressed as a percentage of the source virtual disk capacity (maximum 220 percent).
The destination of a snapshot repository virtual disk is determined based on the free capacity available in the disk group. A snapshot repository virtual disk requires a minimum 8 MB of free capacity. You can choose your preferred creation path—simple or advanced—if the disk group of the source virtual disk has the required amount of free space.
2 Using your Windows system, flush the cache to the source. At the host prompt, type SMrepassist -f and press . For more information, see "SMrepassist Utility" on page 257. 3 Remove the drive letter(s) of the source in Windows or unmount the virtual drive(s) in Linux to help guarantee a stable copy of the drive for the Snapshot. If this is not done, the snapshot operation reports that it has completed successfully, but the snapshot data is not updated properly.
3 Select Virtual Disk→ Snapshot→ Create. Alternatively, you can rightclick the source virtual disk and select Create Snapshot Virtual Disk from the pop-up menu. The Create Snapshot Virtual Disk Wizard - Introduction dialog is displayed. 4 Select Advanced, and click Next. The Specify Names window is displayed. 5 Enter the Snapshot visual disk name and the Snapshot repository virtual disk name and click Next. The Allocate Capacity window is displayed.
12 Click OK. 13 In the Mappings tab, assign mappings between the snapshot virtual disk and the host that accesses the snapshot virtual disk. 14 To register the snapshot virtual disk with the host operating system, run the host-based hot_add utility. 15 To associate the mapping between the storage array name and the virtual disk name, run the host-based SMdevices utility.
• The next available sequence number is based on the number of existing snapshots of a source virtual disk. If you delete a snapshot virtual disk, its sequence number becomes available again. • You must choose a unique name for the snapshot virtual disk and the snapshot repository virtual disks, or an error message is displayed. • Names are limited to 30 characters.
NOTE: You can add a maximum of two physical disks at one time to increase snapshot repository virtual disk capacity. To expand the snapshot repository virtual disk from MDSM: 1 In the AMW, select the Logical tab. 2 Select the snapshot repository virtual disk for which you want to increase the capacity. 3 Select Virtual Disk→ Increase Capacity. NOTE: If no free capacity or unconfigured capacity is available, the Increase Capacity option is disabled.
7 If unassigned physical disks are not available, do you have empty slots in the expansion enclosures? • Yes, there are empty slots—Insert new physical disks by using the information in the initial setup guide for your expansion enclosure. Go to step 9. • No, there are no empty slots—Install another expansion enclosure and additional physical disks. Use the information in the initial setup guides for your RAID controller module and your expansion enclosure. Go to step 9.
• Not all of the capacity that is added is used to increase the capacity of the snapshot repository virtual disk. On the Physical tab, the unassigned physical disks or unconfigured capacity that you added to increase the capacity of the snapshot repository virtual disk change to assigned physical disks. The new assigned physical disks are associated with the disk group of the snapshot repository virtual disk.
Preparing Host Servers to Re-create a Snapshot Virtual Disk NOTE: Before you create a new snapshot of a source virtual disk, stop any data access (I/O) activity or suspend data transfer to the source virtual disk and snapshot virtual disk to ensure that you capture an accurate snapshot of the source virtual disk. Close all applications, including Windows Internet Explorer, to make sure all I/O activity has stopped.
Re-creating Snapshot Virtual Disks You can re-create a snapshot virtual disk that you have previously disabled. CAUTION: Possible loss of data redundancy – If the snapshot virtual disk is in Optimal status, it is first disabled prior to being re-created. This action invalidates the current snapshot. Keep these important guidelines in mind when you re-create a snapshot virtual disk: • To re-create the snapshot virtual disks correctly, follow the instructions for your operating system.
The associated snapshot repository virtual disk must have sufficient capacity to process the rollback operation and the write operations from the host. At most, the snapshot repository virtual disk may need twice the size of the base disk, plus additional metadata space equaling approximately 1/1000th (that is, 0.1%) of the Base volume capacity. NOTE: Due to host server write operations, the content in the snapshot virtual disk may have changed since creation of the snapshot.
If an error occurs during the rollback, the operation is paused and the base virtual disk and snapshot virtual disk displays Needs Attention icons. The RAID controller module also logs the event to the Major Event Log (MEL). Follow the Recovery Guru procedure to correct the error and repeat the rollback operation.
2 Choose one: • Select the snapshot virtual disk, and select Virtual Disk→ Snapshot→ Rollback. • Right-click the snapshot virtual disk and select Rollback. The Confirm Rollback Snapshot Virtual Disk dialog is displayed. 3 In the Select rollback priority area, use the slider bar to set rollback priority. NOTE: If priority is set at the lowest rate, normal data write activity is highest priority and the rollback operation takes longer to complete.
Canceling a Snapshot Rollback WARNING: Risk of data loss: If you cancel a snapshot rollback in progress, the base virtual disk may remain in an unusable state and the snapshot virtual disk is displayed as failed in the MD storage management software. Therefore, do not cancel a snapshot rollback unless reliable recovery options exist for restoring the content of the base virtual disk. 1 In the array management window, select the Logical tab.
172 Configuration: Premium Feature—Snapshot Virtual Disks
12 Configuration: Premium Feature— Virtual Disk Copy NOTE: A virtual disk copy overwrites data on the target virtual disk. Before starting a virtual disk copy, ensure that you no longer need the data or back up the data on the target virtual disk. NOTE: If you ordered this feature, you received a Premium Feature Activation card that shipped in the same box as your Dell PowerVault MD storage array. Follow the directions on the card to obtain a key file and to enable the feature.
• Copying data for improved access—As your storage requirements for a virtual disk change, you can use a virtual disk copy to copy data to a virtual disk in a disk group that uses drives with larger capacity within the same storage array. Copying data for larger access capacity enables you to move data to greater capacity physical disks (for example, 61 GB to 146 GB).
the source virtual disk may be rejected by the storage array RAID controller modules and result in an error message. Make sure that the Read-Only attribute for the target virtual disk is disabled after the virtual disk copy is complete to prevent error messages from being displayed. Online Copy An online copy creates a point-in-time snapshot copy of any virtual disk within a storage array, while still allowing writes to the virtual disk when the copy is in progress.
Creating a Virtual Disk Copy for an MSCS Shared Disk To create a virtual disk copy for a Microsoft Cluster Server (MSCS) shared disk, create a snapshot of the virtual disk, and then use the snapshot virtual disk as the source for the virtual disk copy. NOTE: An attempt to directly create a virtual disk copy for an MSCS shared disk, rather than using a snapshot virtual disk, fails with the following error: The operation cannot complete because the selected virtual disk is not a source virtual disk candidate.
• To enable Read-Only permission, select Change→ Target Virtual Disk Permissions→ Enable Read-Only. NOTE: Write requests to the target virtual disk are rejected when the ReadOnly permission is enabled on the target virtual disk. • To disable Read-Only permission, select Change→ Target Virtual Disk Permissions→ Disable Read-Only. Virtual Disk Copy Restrictions Before you perform any virtual disk copy tasks, understand and adhere to the restrictions listed in this section.
Creating a Virtual Disk Copy CAUTION: Possible loss of data – Source virtual disks that are participating in a virtual disk copy are available for read I/O activity only while a virtual disk copy has a status of In Progress or Pending. Write requests are allowed after the virtual disk copy has completed.
Virtual Disk Copy and Modification Operations If a modification operation is running on a source virtual disk or a target virtual disk, and the virtual disk copy has a status of In Progress, Pending, or Failed, the virtual disk copy does not take place. If a modification operation is running on a source virtual disk or a target virtual disk after a virtual disk copy is created, the modification operation must complete before the virtual disk copy can start.
Preferred RAID Controller Module Ownership During a virtual disk copy, the same RAID controller module must own both the source virtual disk and the target virtual disk. If both virtual disks do not have the same preferred RAID controller module when the virtual disk copy starts, the ownership of the target virtual disk is automatically transferred to the preferred RAID controller module of the source virtual disk.
A virtual disk copy automatically makes the target virtual disk read-only to hosts. You may want to keep this attribute enabled to preserve the data on the target virtual disk. CAUTION: If you decide not to preserve the data on the target virtual disk after the virtual disk copy has completed, disable the Read-Only attribute for the target virtual disk. For more information on enabling and disabling the Read-Only attribute for the target virtual disk, see "Virtual Disk Read/Write Permissions" on page 176.
9 Type yes and click Finish. NOTE: Operation in Progress icons are displayed on the source virtual disk and the target virtual disk while the virtual disk copy has a status of In Progress or Pending. For more information, see the PowerVault Modular Disk Storage Manager online help topics.
2 In the table, select one or more copy pairs. 3 Select Change→ Copy Priority. The Change Copy Priority window is displayed. 4 In the Copy priority area, select the appropriate copy priority, depending on your system performance needs. NOTE: There are 5 copy priority rates available: lowest, low, medium, high, and highest. If the copy priority is set at the lowest rate, I/O activity is prioritized and the virtual disk copy takes longer.
Preparing Host Servers to Recopy a Virtual Disk NOTE: Before you create a new copy of a source virtual disk, stop any data access (I/O) activity or suspend data transfer to the source virtual disk (and, if applicable, the target disk) to ensure that you capture an accurate point-in-time image of the source virtual disk. Close all applications, including Windows Internet Explorer, to make sure all I/O activity has stopped.
Re-Copying a Virtual Disk You can use the Copy Manager to create a new virtual disk copy for a selected source virtual disk and a target virtual disk. Use this option when you have stopped a virtual disk copy and want to start it again or when a virtual disk copy has failed or completed. The virtual disk copy starts over from the beginning. • Possible loss of data—The re-copying operation overwrites existing data on the target virtual disk.
Removing Copy Pairs You can remove one or more virtual disk copies by using the Copy Manager. Any virtual disk copy-related information for the source virtual disk and the target virtual disk is removed from the Virtual Disk Properties and the Storage Array Profile dialogs. When you remove a virtual disk copy from the storage array, the Read-Only attribute for the target virtual disk is also removed.
13 Configuration: Premium Feature— Upgrading to High-PerformanceTier The High Performance Tier premium feature on an MD3200i Series array increases the performance of the system beyond that of a MD3200i Series array operating at the standard performance level. If this feature is ordered, a Premium Feature Activation card is placed in the box with the storage array. After reading the information below, follow the instructions on the card to obtain a key file and enable the feature.
188 Configuration: Premium Feature—Upgrading to High-Performance-Tier
14 Configuration: Device Mapper Multipath for Linux Overview The MD3200i Series storage array uses a Linux operating system software framework, known as Device Mapper (DM), to enable multipath capabilities on Linux Host Servers. The DM multipath functionality is provided by a combination of drivers and utilities. This chapter describes how to use those utilities to complete the process of enabling MD3200i Series storage array on a Linux system.
Using DM Multipathing Devices NOTE: Using or modifying any nodes other than the multipathing device nodes can result in array or file system problems, including loss of communication with the array and corruption of the file system. Avoid accessing any device other than the multipathing device.
NOTE: Any arrays configured with MDCU automatically adds to the list of Devices in the PowerVault Modular Disk Storage Manager Enterprise Management Window (EMW). Device Mapper Configuration Steps To complete the DM multipathing configuration and make storage available to the Linux host server: 1 Scan for virtual disks. See "Scan for newly added Virtual Disks" on page 191. 2 Display the multipath device topology. See "Display the multipath device topology using the multipath command" on page 192.
Display the multipath device topology using the multipath command The multipath command adds newly scanned and mapped virtual disks to the Device Mapper tables and creates entries for them in the /dev/mapper directory on the host server. These devices are the same as any other block devices in the host. To list all the multipath devices, run the following command: # multipath –ll The output must be similar to this example, which shows the output for one mapped virtual disk.
\_ round-robin 0 [prio=1][enabled] \_ 6:0:0:22 sdcl 69:144 [active][ghost] where: mpathb is the name of the virtual device created by device mapper. It is located in the /dev/mapper directory.
# ls The following are some examples of the general mapping formats: On RHEL hosts ,a partition node has the format /dev/mapper/mpathp, where is the alphabetic number for the multipathing device, is the partition number for this device. On SLES 11.x hosts, a partition node has the format /dev/mapper/mpath-part, where is letter(s) assigned to the multipathing device and is the partition number. On SLES 10.
Blacklist Local Drive in Multi-path Driver If your multipath drivers are connecting to storage area networks (SANs), it may be useful to be able to exclude or "blacklist" certain devices in your /etc/multipath.conf file. Blacklisting prevents the multipath driver from attempting to use those local devices. To blacklist a local drive or device: 1 Run the multipath -l command to determine the local drive or device WWID (World-Wide Identifier) or vendor/model string. 2 Edit the /etc/multipath.
2 Stop the Device Mapper multipath service # /etc/init.d/multipathd stop 3 Flush the Device Mapper multipath maps list to remove any old or modified mappings # multipath –F NOTE: The boot operating system drive may have an entry with the Device Mapper multipathing table. This is not affected by the multipath –F command. However, using #multipath –ll must not show any multipathing devices with model “MD3200i” or “MD3200i”.
Table 14-1. Useful Device Mapper Commands (continued) Command Descriptions multipath –f Flushes out Device Mapper for the specified multipathing device. Used if the underlying physical devices are deleted/unmapped. multipath –F Flushes out all unused multipathing device maps. rescan_dm_devs Dell provided script. Forces a rescan of the host SCSI bus and aggregates multipathing devices as needed. For use when: • LUNs are dynamically mapped to the hosts.
• After a failed path is restored on an MD3600i Series array, failback does not occur automatically because the driver cannot auto-detect devices without a forced rescan. Run the command rescan_dm_devs to force a rescan of the host server. This restores the failed paths enabling failback to occur. • Failback can be slow when the host system is experiencing heavy I/O. The problem is exacerbated if the host server is also experiencing very high processor utilization.
Question Answer I removed a LUN. But the multipathing mapping is still there. The multipathing device is still there after you remove the LUNs. Run multipath –f to remove the multipathing mapping. For example, if a device related with /dev/dm-1 is deleted, you must run multipath –f /dev/dm-1 to remove /dev/dm-1 from DM mapping table. If multipathing daemon is stopped/restarted, run multipath –F to flush out all stale mappings.
200 Configuration: Device Mapper Multipath for Linux
15 Management: Firmware Downloads Downloading RAID Controller and NVSRAM Packages A version number exists for each firmware file. The version number indicates whether the firmware is a major version or a minor version. You can use the Enterprise Management Window (EMW) to download and activate both the major firmware versions and the minor firmware versions. You can use the Array Management Window (AMW) to download and activate only the minor firmware versions. NOTE: Firmware versions are of the format aa.
Downloading Both RAID Controller and NVSRAM Firmware NOTE: I/O to the array can continue while you are upgrading RAID controller and NVSRAM firmware. NOTE: Dell recommends that the firmware and NVSRAM be upgraded during a maintenance period when the array is not being used for I/O. NOTE: The RAID enclosure must contain at least two disk drives in order to update the firmware on the controller. To download RAID controller and NVSRAM firmware in a single operation: 1 If you are using the EMW, go to step 9.
7 Click Transfer. Keep these guidelines in mind: – If the Transfer button is inactive, ensure that you either select an NVSRAM file or cleared the Transfer NVSRAM file with RAID controller module firmware. – If the file selected is not valid or is not compatible with the current storage array configuration, the File Selection Error dialog is displayed. Click OK to close it, and choose a compatible firmware or NVSRAM file. 8 In the Confirm Download dialog, click Yes. The download starts.
The Select File dialog is displayed. 13 Select the file to download. 14 Click OK. 15 If you want to download the NVSRAM file with the RAID controller module firmware, select Download NVSRAM file with firmware in the Select files area. Attributes of the firmware file are displayed in the Firmware file information area. The attributes indicate the version of the firmware file. Attributes of the NVSRAM file are displayed in the NVSRAM file information area.
2 Select Advanced→ Maintenance→ Download→ RAID Controller Module NVSRAM or Select the Support tab, and click Download Firmware. In Select download task, select Download RAID controller module NVSRAM and click OK. An error message is displayed. Click OK to close it and select a compatible file. 3 To locate the directory in which the file to download resides, click Select File. 4 Select the file to download in the File selection area and click OK.
NOTE: The Details pane shows the details of only one storage array at a time. If you select more than one storage array in the Storage array pane, the details of the storage arrays are not shown in the Details pane. 9 Click NVSRAM in the Download area. NOTE: If you select a storage array that cannot be upgraded, the NVSRAM button is disabled. The Download NVSRAM dialog is displayed. The current firmware version and the NVSRAM version of the selected storage arrays is displayed.
disk called DACstore. DACstore and the physical disk firmware enable easier reconfiguration and migration of the physical disks. The physical disk firmware performs these functions: • The physical disk firmware records the location of the physical disk in an expansion enclosure.
4 Navigate to the location of the packages and click OK. The selected package is added to the Packages to be transferred area. 5 Click Next. The Download Physical Disk Firmware - Select Physical Disks window is displayed. 6 In the Compatible Physical Disks tab, select the appropriate physical disks or Select all the physical disks. The Confirm Download dialog is displayed. 7 Type yes and click OK.
• In the AMW, select Advanced→ Maintenance→ Download→ EMM Firmware. • Select the Support tab, and click Download Firmware. In the dialog that is displayed, select the EMM firmware, and click OK. The Download Environmental (EMM) Firmware dialog is displayed. 2 In the Select enclosures area, either select each expansion enclosure to which you want to download firmware, or select Select All to select all of the expansion enclosures in the storage array.
• The download failed—The status of one expansion enclosure shows Failed and the remainder of the expansion enclosures show Canceled. Make sure that the new firmware file is compatible before attempting another firmware download. Self-Monitoring Analysis and Reporting Technology (SMART) Self-Monitoring Analysis and Reporting Technology (SMART) monitors the internal performance of all physical disk components to detect faults indicating the potential for physical disk failure.
16 Management: Installing Array Components Recommended Tools You may need the following items to perform the procedures in this section: • Key to the system keylock • #2 Phillips screwdriver • Wrist grounding strap Management: Installing Array Components 211
Front Bezel (Optional) Removing the Front Bezel 1 Using the system key, unlock the front bezel (if locked). 2 Lift up the release latch next to the keylock. 3 Rotate the left end of the bezel away from the front panel. 4 Unhook the right end of the bezel and pull the bezel away from the system. Figure 16-1. Removing and Installing the Front Bezel 1 2 3 4 1 bezel 2 keylock 3 release latch 4 hinge tab Installing the Front Bezel 1 Hook the right end of the bezel onto the chassis.
Hard Drives SAFETY: Models AMT, E03J, and E04J Models AMT, E03J, and E04J are intended for installation only in restricted access locations as defined in cl 1.2.7.3 of IEC 60950-1:2005. Depending on your configuration, your array either supports up to twenty four 2.5" SAS hard drives or up to twelve 3.5" SAS hard drives in internal drive bays. Hard drives are connected to a backplane through hard-drive carriers and can be configured as hot-swappable.
Figure 16-3. Removing and Installing a 2.5" Hard-Drive Blank (MD3220i Only) 1 1 2 hard-drive blank 2 release tab Installing a Hard-Drive Blank 1 If installed, remove the front bezel. See "Removing the Front Bezel" on page 212. 2 Insert the hard-drive blank into the drive bay until the blank is fully seated. 3 Close the handle to lock the blank in place. 4 If applicable, replace the front bezel. See "Installing the Front Bezel" on page 212.
2 From the Modular Disk Storage Manager (MDSM) software, prepare the drive for removal. Wait until the hard-drive indicators on the drive carrier signal that the drive can be removed safely. For more information, see your controller documentation for information about hot-swap drive removal. If the drive is online, the green activity/fault indicator flashes as the drive is powered down. When the drive indicators are off, the drive is ready for removal.
Installing a Hard Drive CAUTION: Many repairs may only be done by a certified service technician. You must only perform troubleshooting and simple repairs as authorized in your product documentation, or as directed by the online or telephone service and support team. Damage due to servicing that is not authorized by Dell is not covered by your warranty. Read and follow the safety instructions that came with the product.
Figure 16-5. Removing and Installing a Hard Drive Into a 3.
Figure 16-6. Removing and Installing a Hard Drive Into a 2.
Installing a Hard Drive Into a Hard-Drive Carrier 1 Insert the hard drive into the hard-drive carrier with the connector end of the drive at the back. See Figure 16-5. 2 Align the screw holes on the hard drive with the back set of holes on the hard-drive carrier. When aligned correctly, the back of the hard drive is flush with the back of the hard-drive carrier. 3 Attach the four screws to secure the hard drive to the hard-drive carrier.
5 Connect all the power cables to the array. 6 Turn on the array and the host server. Figure 16-7. Removing and Installing a RAID Controller Module Blank 1 1 release latch 2 RAID controller module blank Installing a RAID Controller Module Blank To install a RAID controller module blank: 1 Align the blank with the RAID controller module bay 2 Insert the blank into the chassis until it clicks into place.
Removing a RAID Controller Module CAUTION: Many repairs may only be done by a certified service technician. You must only perform troubleshooting and simple repairs as authorized in your product documentation, or as directed by the online or telephone service and support team. Damage due to servicing that is not authorized by Dell is not covered by your warranty. Read and follow the safety instructions that came with the product. 1 Disconnect the cables connected to the RAID controller module.
Installing a RAID Controller Module CAUTION: Many repairs may only be done by a certified service technician. You must only perform troubleshooting and simple repairs as authorized in your product documentation, or as directed by the online or telephone service and support team. Damage due to servicing that is not authorized by Dell is not covered by your warranty. Read and follow the safety instructions that came with the product.
Figure 16-9. Opening and Closing the RAID Controller Module 1 1 screws (2) 3 indent 2 3 2 RAID controller module Closing the RAID Controller Module CAUTION: Many repairs may only be done by a certified service technician. You must only perform troubleshooting and simple repairs as authorized in your product documentation, or as directed by the online or telephone service and support team. Damage due to servicing that is not authorized by Dell is not covered by your warranty.
RAID Controller Module Backup Battery Unit Removing the RAID Controller Module Backup Battery Unit CAUTION: Many repairs may only be done by a certified service technician. You must only perform troubleshooting and simple repairs as authorized in your product documentation, or as directed by the online or telephone service and support team. Damage due to servicing that is not authorized by Dell is not covered by your warranty. Read and follow the safety instructions that came with the product.
Installing the RAID Controller Module Backup Battery Unit CAUTION: Many repairs may only be done by a certified service technician. You must only perform troubleshooting and simple repairs as authorized in your product documentation, or as directed by the online or telephone service and support team. Damage due to servicing that is not authorized by Dell is not covered by your warranty. Read and follow the safety instructions that came with the product.
support team. Damage due to servicing that is not authorized by Dell is not covered by your warranty. Read and follow the safety instructions that came with the product. NOTE: If you remove a fully functioning power supply/cooling fan module, the fan speed in the remaining module increases significantly to provide adequate cooling. The fan speed decreases gradually when a new power supply/cooling fan module is installed. 1 Turn off the power supply/cooling fan module.
Figure 16-11.
Installing a Power Supply/Cooling Fan Module CAUTION: Many repairs may only be done by a certified service technician. You must only perform troubleshooting and simple repairs as authorized in your product documentation, or as directed by the online or telephone service and support team. Damage due to servicing that is not authorized by Dell is not covered by your warranty. Read and follow the safety instructions that came with the product.
Control Panel Removing the Control Panel 1 Turn off the array and host server. 2 Disconnect all the power cables connected to the array. 3 Remove the hard drives from: – slots 0 to 2 in PowerVault MD3200i – slots 0 to 5 in PowerVault MD3220i See "Removing a Hard Drive" on page 214. NOTE: Mark each hard drive with it’s slot position as you remove it. 4 Slide the control panel out of the chassis after: – Pushing the release tab toward the front of the array in PowerVault MD3200i. See Figure 16-13.
Figure 16-14. Removing and Installing the Control Panel-PowerVault MD3220i 1 2 1 release pin 2 control panel Installing the Control Panel 1 Align the control panel with the slot on the array. 2 Slide the control panel into the array until: – The release tab clicks into place in PowerVault MD3200i. See Figure 16-13. – The release pin clicks into place in PowerVault MD3220i. See Figure 16-14. 3 Replace the hard drives in their respective slots. See "Installing a Hard Drive" on page 216.
Backplane CAUTION: Many repairs may only be done by a certified service technician. You must only perform troubleshooting and simple repairs as authorized in your product documentation, or as directed by the online or telephone service and support team. Damage due to servicing that is not authorized by Dell is not covered by your warranty. Read and follow the safety instructions that came with the product. Removing the Backplane 1 Turn off the array and disconnect it from the electrical outlet.
Figure 16-15.
Figure 16-16. Removing and Installing the Backplane-PowerVault MD3200i 1 2 3 1 screws (5) 3 captive screw 2 backplane Figure 16-17.
Installing the Backplane 1 Align the holes on the backplane with the holes on the array. 2 Tighten the captive screw to secure the backplane to the chassis. See Figure 16-16 for PowerVault MD3200i or Figure 16-17 for PowerVault MD3220i. 3 Replace the screws that secure the backplane to the chassis. See Figure 16-16 for PowerVault MD3200i or Figure 16-17 for PowerVault MD3220i. 4 Align the slots on the RAID controller module/power supply cage with the tabs on the chassis. See Figure 16-15.
17 Management: Firmware Inventory A storage array is made up of many components, which may include RAID controller modules, physical disks, and enclosure management modules (EMMs). Each of these components contains firmware. Some versions of firmware are dependent on other versions of firmware. To capture information about all of the firmware versions in the storage array, view the firmware inventory.
236 Management: Firmware Inventory
18 Management: System Interfaces Microsoft Services Virtual Disk Service The Microsoft Virtual Disk Service (VDS) is a component of the Windows operating system. The VDS component utilizes third-party vendor specific software modules, known as providers, to access and configure third-party storage resources, such as MD3200i storage arrays. The VDS component exposes a set of application programming interfaces (APIs) that provides a single interface for managing disks and other storage hardware.
VSS attaches to the service and uses it to coordinate the creation of snapshot virtual disks on the storage array. VSS-initiated snapshot virtual disks can be triggered through backup tools, known as requestors. The VSS Provider Configuration Tool offers the following configuration options: • Snapshot Repository Virtual Disk Properties—This section contains a drop-down list for the RAID level and a field for entering source virtual disk capacity percentage for snapshot repositories.
19 Troubleshooting: Your Storage Array Software Start-Up Routine Look and listen during the array’s start-up routine for the indications described in Table 19-1. For a description of the front- and back-panel indicators, see "Planning: About Your Storage Array" on page 23. Table 19-1. Start-Up Routine Indications Look/Listen for Action Alert messages. See your storage management documentation. An unfamiliar constant scraping or grinding sound when you access a physical disk.
• On the Devices tab, in either the Tree view or the Table view, double-click a storage array. Alternatively, you can right-click a storage array and select Manage Storage Array from the pop-up menu. • On the Setup tab, select Manage a Storage Array. After the AMW is displayed, select the Physical tab to see the components in the storage array. A component that has a problem is indicated by a status icon. The status icons indicate the status of the components that comprise the storage array.
In the Table view, every managed storage array is listed once, regardless of the number of attachments it has in the Tree view. After the storage array is contacted by MDSM, an icon representing its hardware status is displayed. Hardware status can be Optimal, Needs Attention, or Fixing. If, however, all of the network management connections from the storage management station to the storage array shown in the Tree view are Unresponsive, the storage array status is represented as Unresponsive.
Table 19-3. Additional Status Icons Status Icon Adding a Storage Array Description The Contacting Storage Array icon is shown in the Tree view and Table view until the current status of each managed storage array is known. The Contacting Storage Array icon is shown in the EMW Status Bar and the AMW Status Bar and the tooltip shows Contacting Storage arrays. As each storage array is contacted, its current status is obtained and shown in the Tree view and Table view.
2 Enter a name for the support data file in Specify filename or click Browse to navigate to a previously saved file to overwrite an existing file. The suffix .zip is added automatically to the file if you do not specify a suffix for the file. 3 Enter the Execution summary. 4 Click Start. After all of the support files are gathered, they are archived using the file name that you specified. 5 Click OK.
Collecting the Physical Disk Data You can use the Collect Physical Disk Data option to collect log sense data from all the physical disks on your storage array. Log sense data consists of statistical information that is maintained by each of the physical disks in your storage array. Your Technical Support representative can use this information to analyze the performance of your physical disks and for troubleshooting problems that may exist.
The event log window shows two types of event views: • Summary view—Shows an event summary in a table form. • Detail view—Shows details about a selected event. To view the event log: 1 In the AMW, select Advanced→ Troubleshooting→ View Event Log. The Event Log is displayed. By default, the summary view is displayed. 2 To view the details of each selected log entry, select View details. A detail pane is added to the event log that contains detailed information about the log item.
• Alert notification messages that are sent to the appropriate destinations • Hardware indicator lights The status icons return to Optimal status as problems are resolved. Storage Array Profile The storage array profile provides a description of all of the components and properties of the storage array. The storage array profile also provides the option to save the storage array profile information to a text file.
b Type the term that you want to search for in the Find text box. If the term is located on the current tab, the term is highlighted in the storage array profile information. NOTE: The search is limited to the current tab. If you want to search for the term in other tabs, select the tab and click the Find button again. c Click the Find button again to search for additional occurrences of the term. 5 To save the storage array profile: a Click Save As.
2 Select View→ Associated Logical Elements. Alternatively, you can rightclick the virtual disk to open a pop-up menu and select View→ Associated Logical Elements. If you select a virtual disk that does not have logical associations with other virtual disks, the Associated Logical Elements option is disabled. NOTE: The View Associated Logical Elements dialog is displayed, which indicates the logical associations for the selected virtual disk.
• The node name and the RAID level • The node name and the virtual disk capacity To find nodes: 1 In the AMW, select View→ Find. 2 Based on the type of search, select one of these options, and go to the indicated step: • Search by name – see step 3. • Search by special criteria – see step 4. 3 Type the name of the node to be found in Find Node. See step 8.
b Type the capacity in the GB box. c Specify that the free capacity to be matched is less than, equal to, or greater than the capacity entered in the GB box. d Go to step 8. 8 Click Find Next. To see every node that matches the criteria, click Find Next repeatedly. If no matches are found, the Search Failed dialog is displayed. Click OK, and re-enter the search criteria. 9 To close the dialog, click Cancel.
4 Select View→ Go To→ Source Virtual Disk. The selection jumps to the associated source virtual disk in the Logical pane. 5 Select View→ Go To→ Target Virtual Disk. NOTE: If the source virtual disk has more than one associated target virtual disk, select the target virtual disk that you want from the list, and click OK. The selection jumps to the associated target virtual disk in the Logical pane.
• ping • ping 7 If the verification is successful, see step 8, if not, see step 9. 8 Remove the storage array with the Unresponsive status from the EMW, and select Add Storage Array to add the storage array again. 9 If the storage array does not return to Optimal status, check the Ethernet cables to make sure that there is no visible damage and that they are securely connected. 10 Make sure the appropriate network configuration tasks are performed.
19 If you have recently replaced or added the RAID controller module, restart the host context agent software so that the new RAID controller module is recognized. 20 If the problem still exists, make the appropriate host modifications, check with other administrators to see if a firmware upgrade was performed on the RAID controller module from another storage management station.
To locate the physical disk: 1 Select the Physical tab. 2 Select the physical disks that you want to locate. 3 Select Physical Disk→ Blink→ Physical Disk. The LEDs on the selected physical disks blink. 4 When you have located the physical disks, click OK. The LEDs stop blinking. If any other blink operations (Blink Disk Group, Blink Storage Array, Blink Physical Disk Ports, or Blink Expansion Enclosure) are currently being invoked from another storage management station, these LEDs also stop blinking.
Locating an Expansion Enclosure You can use the Blink option to physically locate and identify an expansion enclosure in the storage array. The LED activation varies according to the type of expansion enclosure that you have. • If you have an expansion enclosure with a white LED, the Blink Expansion Enclosure operation causes the white LED on the expansion enclosure to come on. The LED does not blink.
Capturing the State Information Use the Troubleshooting→ Capture State Information option to capture information about the current state of your storage array and save the captured information to a text file. You can then send the captured information to your Technical Support representative for analysis. Potential to cause an unresponsive storage array – The State Capture option can cause a storage array to become unresponsive to both the host and the storage management station.
SMrepassist Utility SMrepassist (replication assistance) is a host-based utility for Windows platforms. This utility is installed with MDSM. Use this utility before and after you create a virtual disk copy on a Windows operating system to ensure that all the memory-resident data for file systems on the target virtual disk is flushed and that the driver recognizes signatures and file system partitions. You can also use this utility to resolve duplicate signature problems for snapshot virtual disks.
Unidentified Devices An unidentified node or device occurs when MDSM cannot access a new storage array. Causes for this error include network connection problems, the storage array is turned off, or the storage array does not exist. NOTE: Before beginning any recovery procedure, make sure that the host context agent software is installed and running. If you started the host before the host was connected to the storage array, the host context agent software is not be able to find the storage array.
ping . If the network can access the host, continue to step c. If the network cannot access the host, go to step d. c Remove the host with the unresponsive status from the MDSM, and add that host again. If the host returns to optimal status, you have completed this procedure. d Make sure that the power to the host is turned on and that the host is operational. e If applicable, make sure that the host bus adapters are installed in the host.
5 Make sure that the controller firmware is compatible with MDSM on your management station. If the controller firmware was upgraded, the MDSM may not have access to the storage array. A new version of MDSM may be needed to manage the storage array with the new version of the controller firmware. If this problem exists, see dell.com/support. 6 Look to see if there is too much network traffic to one or more controllers.
or Click Start→ Administrative Tools→ Services. 2 In the Services dialog, select Modular Disk Storage Manager Agent. 3 If the modular disk storage manager agent is running, click Action→ Stop and wait approximately 5 seconds. 4 Click Action→ Start. Linux To start or restart the host context agent software in Linux, enter the following command at the prompt: SMagent start The SMagent software may take a little time to initialize. The cursor is shown, but the terminal window does not respond.
262 Troubleshooting: Your Storage Array Software
Troubleshooting: Your Array 20 Safety First—For you and Your Array CAUTION: Many repairs may only be done by a certified service technician. You must only perform troubleshooting and simple repairs as authorized in your product documentation, or as directed by the online or telephone service and support team. Damage due to servicing that is not authorized by Dell is not covered by your warranty. Read and follow the safety instructions that came with the product.
Troubleshooting Power Supply/Cooling Fan Module CAUTION: Many repairs may only be done by a certified service technician. You must only perform troubleshooting and simple repairs as authorized in your product documentation, or as directed by the online or telephone service and support team. Damage due to servicing that is not authorized by Dell is not covered by your warranty. Read and follow the safety instructions that came with the product.
Troubleshooting Array Cooling Problems CAUTION: Many repairs may only be done by a certified service technician. You must only perform troubleshooting and simple repairs as authorized in your product documentation, or as directed by the online or telephone service and support team. Damage due to servicing that is not authorized by Dell is not covered by your warranty. Read and follow the safety instructions that came with the product.
c Reseat the EMM module and wait for 30 seconds. See "Removing an EMM" in the MD1200 and MD1220 Storage Enclosures Hardware Owner's Manual. d Turn on the server. e Check the EMM status LED. f If the LED does not turn Green, replace the EMM. If the problem is not resolved, see "Getting Help" on page 273. • If EMM status LED is blinking amber (5 times per sequence), update the firmware to the latest supported firmware on both the EMMs.
Troubleshooting RAID Controller Modules CAUTION: Many repairs may only be done by a certified service technician. You must only perform troubleshooting and simple repairs as authorized in your product documentation, or as directed by the online or telephone service and support team. Damage due to servicing that is not authorized by Dell is not covered by your warranty. Read and follow the safety instructions that came with the product.
e Check the link status LED. If the link status LED is not green, replace the cables. If the problem is not resolved, see "Getting Help" on page 273. Troubleshooting Hard Drives CAUTION: Many repairs may only be done by a certified service technician. You must only perform troubleshooting and simple repairs as authorized in your product documentation, or as directed by the online or telephone service and support team. Damage due to servicing that is not authorized by Dell is not covered by your warranty.
Troubleshooting Array and Expansion Enclosure Connections 1 Verify that the RAID controller module port link status LED and the RAID controller module status LED are solid green for each port that is connected to a cable. If the LEDs are not solid green, see "Planning: RAID Controller Modules" on page 31. 2 Ensure that all the cables are attached correctly according to expansion enclosure mode you selected. 3 Turn off the server, storage array, and expansion enclosures.
• Hard drives • RAID controller modules • Power supply/cooling fan modules • Control panel • Backplane 3 Let the system dry thoroughly for at least 24 hours. 4 Reinstall the components you removed in step 2. 5 Connect all the cables and turn on the array. If the array does not start properly, see "Getting Help" on page 273. Troubleshooting a Damaged Array CAUTION: Many repairs may only be done by a certified service technician.
Troubleshooting RAID Controller Modules Conditions Certain events can cause a RAID controller module to fail and/or shut down. Unrecoverable ECC memory or PCI errors, or critical physical conditions can cause lockdown. If your RAID storage array is configured for redundant access and cache mirroring, the surviving controller can normally recover without data loss or shutdown. Typical hard controller failures are detailed in the following sections.
PCI Errors The storage array firmware can detect and only recover from PCI errors when the RAID controller modules are configured for redundancy. If a virtual disk uses cache mirroring, it fails over to its peer RAID controller module, which initiates a flush of the dirty cache. Critical Conditions The storage array generates a critical event if the RAID controller module detects a critical condition that could cause immediate failure of the array and/or loss of data.
Getting Help 21 Locating Your System Service Tag Your system is identified by a unique Express Service Code and Service Tag number. The Express Service Code and Service Tag are found on the front of the system by pulling out the information tag. This information is used by Dell to route support calls to the appropriate personnel. Contacting Dell NOTE: Dell provides several online and telephone-based support and service options.
Documentation Feedback If you have feedback for this document, write to documentation_feedback@dell.com. Alternatively, you can click on the Feedback link in any of the Dell documentation pages, fill up the form, and click Submit to send your feedback.
Index A Access Virtual Disk, 66 Advanced Feature Using Snapshot and Disk Copy Together, 54 Advanced Features, 50 Snapshot Repository Virtual Disk, 52 Snapshot Virtual Disks, 51 Advanced iSCSI Host Ports Settings, 89 Advanced Path, 156 Array Management Types In-Band Management, 66 Out-of-Band Management, 65 B backplane installing, 234 removing, 231 Battery Settings, 81 C Change Controller Ownership of the Virtual Disk, 131 I/O Type, 114 iSCSI Target Authentication, 83 iSCSI Target Identification, 86 RAID
Physical Disk Firmware, 206 RAID Controller and NVSRAM Firmware, 202 RAID Controller and NVSRAM Packages, 201 RAID controller module Firmware, 208 contacting Dell, 273 control panel installing, 230 removing, 229 Copy Manager, 180 D drive carrier hard drive, 216 Defining a Host, 96 Dell contacting, 273 Disk Group Creating, 106 Expansion, 141 Export, 143 Exporting, 143 Import, 144 Locating, 108 Migration, 143 Disk Group and Virtual Disk Expansion, 141 Disk Group Operations, 45 Defragmentation, 46 Expansio
Free Capacity, 142 front bezel installing, 212 removing, 212 Hot Spare Drive Protection, 126 Global Hot Spares, 125 Operation, 125 Hot Spares and Rebuild, 125 H hard drive drive carrier, 216 installing, 216 removing, 214 Hard-Drive Indicator Patterns, 28 Hardware Features Back panel features, 27 Front panel features, 24 Hard drive indicator patterns, 28 Power indicator codes, 30 Power supply and cooling fan features, 29 Host Group Adding, 99 Create, 98 Moving a Host, 99 Removing a host, 99 Removing a Host
Media Errors and Unreadable Sectors, 210 Media Scan Changing settings, 146 Suspending, 147 Microsoft Virtual Disk Service, 237 Volume Shadow-Copy Service, 237 Microsoft Services Virtual Disk Copy, 53 Physical Disks, 37 Erasing Secure, 122 Unlocking Secure, 122 Physical Disks, Virtual Disks, and Disk Groups, 37 Power Indicator Codes, 30 Power Supply and Cooling Fan Features, 29 Preferred RAID Controller Module Ownership, 180 Monitoring Performance, 57 Preparing Host Servers Simple path, 153 Multi-Path Pr
front bezel, 212 hard drive, 214 hard drive from a drive carrier, 216 power supply/cooling fan module, 225 Re-creating, 167 Starting or Stopping the Host Context Agent, 101 Removing Copy Pairs, 186 Storage Array RAID Controller Module Clocks, 82 Removing Host Access, 98 Storage Array Media Scan, 145 Restricted Mappings, 136 Storage Arrays, 66 Automatic Discovery, 67 Manual Addition, 67 S Safety, 19 safety, 263 Security Key Changing, 119 Creating, 118 Saving, 121 Segment Size, 42 Setting a Password,
Starting or Restarting the Host-Agent Software, 260 Start-Up Routine, 239 Storage Array Profile, 246 Storage Array Support Data, 242 Unidentified Devices, 258 Viewing the Logical Associations, 247 Viewing the Physical Associations, 248 troubleshooting, 263 connections, 269 cooling problems, 265 damaged enclosure, 270 external connections, 263 hard drives, 268 loss of communication, 263 power supply/cooling fan module, 264 startup failure, 263 wet enclosure, 269 U Unconfigured Capacity, 142 User Interface A
Virtual Disk Operations Limit, 45 Virtual Disk Ownership, 55 Virtual Disk States, 40 Virtual DiskCopy Target, 53 Virtual Disks and Disk Groups, 39 Index 281
282 Index
