

Copyright © 2015 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. Dell™ and the Dell logo are trademarks of Dell Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies.
Rev. A01
2015 - 02



This document provides information about deploying Dell PowerVault MD3800f and MD3820f Fibre Channel storage arrays. The deployment process includes:
Other information includes system requirements, storage array organization, and utilities.
MDSM enables an administrator to configure and monitor storage arrays for optimum usability. The version of MDSM included on the PowerVault MD series resource media can be used to manage both the Dell PowerVault PowerVault MD3800f and MD3820f systems and the earlier PowerVault MD series storage arrays. MDSM is compatible with both Microsoft Windows and Linux operating systems.
Before installing and configuring the PowerVault MD3800f and MD3820f series hardware and software, ensure that the minimum system requirements are met, and the supported operating system is installed. For more information, see the Dell PowerVault MD34/38 Series Support Matrix at dell.com/support/ manuals.
A management station uses MDSM to configure and manage storage arrays across the network. For management station requirements, see Dell PowerVault MD34xx/38xx Series Support Matrix at dell.com/ support/manuals.
A storage array includes various hardware components, such as physical disks, RAID controller modules, fans, and power supplies, gathered into enclosures. The physical disks are accessed through the RAID controller modules.
One or more host servers attached to the storage array can access the data on the storage array. You can also establish multiple physical paths between the hosts and the storage array so that loss of any single path (for example, through failure of a host server port) does not result in loss of access to data on the storage array.
The storage array is managed by MDSM running on a:

Using MDSM, you can configure the physical disks in the storage array into logical components called disk groups or dynamic disk group and then divide the disk groups into virtual disks. Disk groups are created in the unconfigured capacity of a storage array. Virtual disks are created in the free capacity of a disk group.
Unconfigured capacity comprises physical disks not already assigned to a disk group. When a virtual disk is created using unconfigured capacity, a disk group or dynamic disk group is automatically created. If the only virtual disk in a disk group is deleted, the disk group is also deleted. Free capacity is space in a disk group that is not assigned to any virtual disk.
Data is written to the physical disks in the storage array using RAID technology. RAID levels define how data is written to physical disks. Different RAID levels offer different levels of accessibility, redundancy, and capacity. You can set a specified RAID level for each disk group and virtual disk on your storage array.
For more information about using RAID and managing data in your storage solution, see the Owner’s Manual at dell.com/support/manuals
You product documentation includes:

Dell provides several online and telephone-based support and service options. If you do not have an active Internet connection, you can find contact information on your purchase invoice, packing slip, bill, or Dell product catalog. Availability varies by country and product, and some services may not be available in your area. To contact Dell for sales, technical support, or customer-service issues:
a. Enter your system Service Tag in the Enter your Service Tag field. b. Click Submit.
The support page that lists the various support categories is displayed.
a. Select your product category. b. Select your product segment. c. Select your product.
The support page that lists the various support categories is displayed.
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. Alternatively, the information may be on a sticker on the chassis of the system. This information is used by Dell to route support calls to the appropriate personnel.

Before using this guide, ensure that you review the instructions in the documents:
Consider the following before installing your storage array:
The storage array is connected to a host using two hot-swappable RAID controller modules. The RAID controller modules are identified as RAID controller module 0 and RAID controller module 1. See the Owners Manual to know more about the functions of the different components of the storage controller.
The functions of the ports on each controller are described below:

Each PowerVault MD3800f and MD3820f series storage array can be expanded to a maximum of 120 (or 192, if enabled using Premium Feature activation) physical slots.
This section provides information about configuring Fibre Channel communication between the host server and the storage array. For basic setup information such as racking, power cabling, and recommended handling procedures, see the Getting Started Guide for your Storage Array at dell.com/ powervaultmanuals.
You can only cable the host server to the storage array via storage area network (SAN) using supported Fibre Channel switch(es).
The following steps shows the configuration order for connecting to a SAN. These steps assume you are setting up Fibre Channel storage for the first time.
To configure a Fibre Channel for connecting to a SAN:
For more information, see SAN-Attached Cabling Example and Remote Replication Cabling Example.
For more information, see Switch Zoning Guidelines.

In addition to this document, see the documentation provided with the HBA and Fibre Channel switch hardware for vendor-specific information required to complete Fibre-Channel setup on your storage array.
The storage array supports a specific set of Fibre Channel HBAs, each requiring a unique driver and firmware level. See the Dell PowerVault MD Series Support Matrix at dell.com/powervaultmanuals for a list of supported HBAs.
If an HBA is already installed on your host server, verify that it is supported in the Dell PowerVault MD Series Support Matrix. If the HBA is not listed, it should not be used to connect to the storage array.
For instructions about physically installing an HBA in your host server and loading supported drivers and firmware, see the documentation supplied with your HBA hardware.
A Fibre Channel switch allows you to connect multiple devices to the SAN without compromising bandwidth or data throughput. Switch zoning implemented on each Fibre Channel switch hardware component using the manufacturer’s embedded utility, allows you to divide port traffic between the host server and storage array to maintain the highest level of redundancy.
The following figure shows each connection to the host server(s) routed to an individual logical zone on the SAN. Two physical switches provide an alternate (redundant) data path to the storage array. If a single HBA, switch or RAID controller fails, the host server(s) can still access data on the storage array through one of the alternate paths provided by the switches.


Figure 1. Example of Switch Zoning on SAN on an MD38xxf-series Fibre-Channel Storage Array
There are several different switch zoning techniques used across various SANs. When configuring zoning with your storage array, using a 64 bit World Wide Name (WWN) to uniquely identify each component in your Fibre Channel switch fabric is recommended. An advantage of using WWN port zoning (also called soft zoning) is that it allows you to remove and/or replace cabling to and from the fabric without reconfiguring the existing zone logic.
When implemented on the Fibre Channel switch, port WWN zoning causes the host server to query the World Wide Identifier (WWID) name of all attached physical disks and/or expansion enclosures each time it accesses the switch fabric. By zoning specific ports on the host server(s), switch and storage array

together, the switch allows the host server to see only devices included in that zone, decreasing the amount of time it would otherwise take for the host server to query attached, but out-of-zone, devices.
The storage array imposes specific requirements that must be followed when setting up Fibre Channel switch zoning:
Setting up zoning on Fibre Channel switches varies greatly between manufacturers. For detailed information on how to set up zoning on your switch, see the manufacturer’s product documentation or technical support website.
Cabling the storage array depends on a number of factors such as:
The cabling diagrams shown here do not represent every supported cabling scenario but the concepts of redundancy and switch logic can be used to build your own configuration.
Non-redundant cabling configurations provide a single data path from host server(s) to the storage array. This type of configuration is only recommended for non-critical data storage. A path failure from a failed or removed cable, failed HBA, or failed or removed RAID controller module results in loss of host access to the storage array.
Redundant configurations establish separate data paths between the host server(s) and storage array. Each path is connected to separate RAID controller modules in the storage array. Redundancy protects

the host server(s) from losing access to data in the event of a path failure since both RAID controller modules can independently access all the physical disks in the storage array.
SAN-attached cabling configurations provide the highest level of redundancy and alternate-path connectivity between the host server and storage array. A SAN configuration using a Fibre Channel compatible switch fabric allows you to establish multiple redundant paths to data on the storage array.
The following figure shows a three-server, mixed HBA cabling configuration that uses two separate switch fabrics to establish multiple paths to the storage array. Port-to-port connections in each switch fabric/zone are detailed in the text boxes.


Figure 2. Three SAN-Attached Host Servers Connected to a Storage Array Using Multiple Paths
Switch Fabric A Switch Fabric B

Switch Fabric A Switch Fabric B
Remote Replication is a storage array premium feature that provides online, real-time replication of data between storage arrays. When this feature is activated, a dedicated port (port 3) on each RAID controller is reserved exclusively for Remote Replication traffic. No other data traffic is allowed on that port until the Remote Replication feature is deactivated. A dedicated zone on each Fibre Channel switch is also required.


Figure 3. Remote Replication Cabling
Switch Fabric A Switch Fabric B

Switch Fabric A Switch Fabric B
The following figure shows mixed configuration, that is SAS direct attached and host connectivity via the SAN (that is FC/Ethernet switch).


Figure 4. Mixed Environment
You can expand the capacity of your PowerVault MD3800i and MD3820i series storage array by adding PowerVault MD1200 series expansion enclosures. You can expand the physical disk pool to a maximum of 120 (or 192, if enabled using Premium Feature activation) physical disks using a maximum of seven expansion enclosures.
Use this procedure if your expansion enclosure is directly attached and configured with a Dell PowerEdge RAID Controller (PERC) H800 adapter. Data from virtual disks created on a PERC H800 adapter cannot be directly migrated to a storage array or an expansion enclosure connected to a storage array.

Windows systems users can reference the DUP.exe package and Linux kernel users can reference the DUP.bin package.
available at dell.com/support c. Using MDSM, click Tools → Upgrade RAID Controller Module Firmware → Enterprise
Management Window (EMW).
enclosure.
After the expansion enclosures are online, they can be accessed as a part of the storage array.
Perform the following steps to attach new PowerVault MD1200 series expansion enclosures to a PowerVault MD34xx/38xx series storage arrays:

b. Set up the PowerVault MD1200 series expansion enclosures. For information about setting up the
PowerVault MD1200 series expansion enclosures, see the Owner’s Manual at dell.com/support/ manuals. c. Using MDSM, update the RAID controller module firmware and NVSRAM to the latest versions
available on dell.com/support/manuals d. Click Tools → Upgrade RAID Controller Module Firmware from the Enterprise Management
Window (EMW).
a. Stop all I/O to the storage array and turn off affected host systems attached to the storage array. b. Turn off the storage array. c. Turn off any expansion enclosures in the affected system.
a. Connect the MiniSAS HD end of the supported SAS cabled to the SAS OUT Port 0 on the MD 1200 series expansion enclosure. b. Connect the other end of the SAS cable to the IN port on the MD 1200 series expansion
enclosure.
a. Turn on the expansion enclosures. Wait for the enclosure status LED to light blue. b. Turn on the storage array and wait for the status LED to indicate that the unit is ready:
a. From the EMW, select the enclosure that you want to update and enter the Array Management Window (AMW). b. Click Advanced → Maintenance → Download → EMM Firmware. c. Select Select All to update all the attached expansion enclosures simultaneously.

The Dell PowerVault MD series resource media contains software and drivers for both Linux and Microsoft Windows operating systems.
The root of the media contains a readme.txt file covering changes to the software, updates, fixes, patches, and other important data applicable to both Linux and Windows operating systems. The readme.txt file also specifies requirements for accessing documentation, information regarding versions of the software on the media, and system requirements for running the software.
For more information on supported hardware and software for Dell PowerVault systems, see the Dell PowerVault MD34xx/38xx Series Support Matrix at dell.com/support/manuals
The PowerVault MD series resource media provides features that include the core software, providers, and utilities. The core software feature includes the host-based storage agent, multipath driver, and Modular Disk Storage Manager (MDSM) application used to configure, manage, and monitor the storage array solution. The providers feature includes providers for the Microsoft Virtual Disk Service (VDS) and Microsoft Volume Shadow-Copy Service (VSS) framework.
If Dynamic Host Configuration Protocol (DHCP) is not used, during initial configuration of the management station, at least one network adapter must be configured on the same IP subnet as the storage array’s default management port (Controller 0 MGMT (port 1): 192.168.129.101 or Controller 1 MGMT (port 1): 192.168.129.102). After initial configuration, the management ports are configured using MDSM and the management station’s IP address can be changed back to the previous settings.
The PowerVault MD series resource media offers the following three installation methods:

Ensure that you read the Configuring Fibre Channel With the Dell PowerVault MD Series Storage Arrays document before continuing with this procedure.
Depending on your operating system, the installer may launch automatically. If the installer does not launch automatically, navigate to the root directory of the installation media (or downloaded installer image) and run the md_launcher.exe file. For Linux-based systems, navigate to the root of the resource media and run the autorun file.

The autorun script in the root of the resource media detects when there is no graphical environment running and automatically starts the installer in a text-based mode. This mode provides the same options as graphical installation with the exception of the MDCU specific options. The MDCU requires a graphical environment to operate.
To run silent installation on a Windows system:
If you ordered premium features, follow the instructions on the Premium Features card to install the additional features.

To upgrade from a previous version of the MDSM application, uninstall the previous version (see Uninstalling MD Storage Software), and then follow the instructions in this chapter to install the new version.

Before using the Dell PowerVault storage array for the first time, complete these initial configuration tasks in the order shown. These tasks are performed using the MD Storage Manager (MDSM) software.
After discovery is complete, a confirmation screen is displayed.
The Automatic Discovery option automatically discovers both in-band and out-of-band arrays and adds the storage arrays to the management domain. If the out-of-band or in-band connections shown on the summary page are not accurate, complete the following steps. For more information, see the Online Help.
a. To remove the array from the management domain, highlight the array and then click Remove link. b. To add an array, click New link.
In Linux, click the Manual button and click OK.

Enter the context of your task here (optional). This is where introductory content goes.
See the Owner’s Manual for information about each task and to perform the necessary configuration steps.
The following table lists the recommended configuration steps that can be accomplished using the Owner’s Manual.
Table 1. Initial Setup Tasks Dialog Box
Rename the storage array To provide a more meaningful name than the software-assigned label, Unnamed.
Set a storage array password To restrict unauthorized access. MDSM may ask for a password before changing the configuration or performing a destructive operation
Set up alert notifications To notify individuals (by email) and/or storage enterprise management consoles, such as Dell Management Console, (by SNMP) when a storage array component degrades or fails, or an adverse environmental condition occurs.
Set up email alerts
Set up SNMP alerts
Configure a storage array To create virtual disks and map them to hosts.
Task Purpose

Uninstalling MD Storage Software From Windows
The Uninstall Complete window is displayed.
The Uninstall Complete window is displayed.
If another directory was used during installation, navigate to that directory before beginning the uninstallation procedure.
When the uninstallation is complete, it goes back to the root prompt.

Load Balance Policy
Multi-path drivers select the I/O path to a virtual disk through a specific RAID controller module. When the multi-path driver receives a new I/O to process, the driver tries to find a path to the current RAID controller module that owns the virtual disk. If the path to the current RAID controller module that owns the virtual disk cannot be found, the multi-path driver migrates the virtual disk ownership to the secondary RAID controller module. When multiple paths to the RAID controller module that owns the virtual disk exist, you can choose a load balance policy to determine which path is used to process I/O. Multiple options for setting the load balance policies let you optimize I/O performance when mixed host interfaces are configured.
You can choose one of the following load balance policies to optimize I/O performance:
The round robin with subset I/O load balance policy routes I/O requests, in rotation, to each available data path to the RAID controller module that owns the virtual disks. This policy treats all paths to the RAID controller module that owns the virtual disk equally for I/O activity. Paths to the secondary RAID controller module are ignored until ownership changes. The basic assumption for the round-robin policy is that the data paths are equal. With mixed host support, the data paths might have different bandwidths or different data transfer speeds.
The least queue depth 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.
The least queue depth policy treats large block requests and small block requests equally. The data path selected is one of the paths in the path group of the RAID controller module that owns the virtual disk.
The least path weight policy assigns a weight factor to each data path to a virtual disk. An I/O request is routed to the path with the lowest weight value to the RAID controller module that owns the virtual disk.

If more than one data path to the virtual disk has the same weight value, the round robin with subset path selection policy is used to route I/O requests between the paths with the same weight value. The least path weight load balance policy is not supported on Linux operating systems.
Load balancing with the PowerVault MD series storage array can be done from the default round robin with subset by using either the:
Changing Load Balance Policies Using Windows Server Device Manager
Follow the steps to change the load balance policy using Windows Server device manager:
Changing Load Balance Policies Using Windows Server Disk Management
Follow the steps to change the load balance policy using disk management:
Linux only supports round robin based load balancing. For more information, see Round Robin With Subset.
VMware supports Asymmetric Logical Unit Access (ALUA). For more information on Most Recently Used (MRU) and Round Robin (RR) load balancing policies, see VMware documents.

Each storage controller can have up to four FC host ports. A small-form-factor pluggable (SFP+) module is used to connect a host port to a host or switch. The SFP+ module is inserted into the port, and then a fiber optic cable is inserted into the SFP+ module. The other end of the fiber optic cable is connected to an optical interface connector either in a FC HBA on a host or a switch. SFP+ modules are laser products.
The storage array requires SFP+ modules. SFP+ modules convert electrical signals to optical signals that are required for FC transmission to and from RAID controller modules. After installing the SFP+ modules, fiber-optic cables are used to connect the storage array to other FC devices. Before installing SFP+ modules and fiber-optic cables, read the following information:
To remove SFP+ modules:
See Working With SFP+ Modules and Fiber Optic Cables

To install SFP+ modules:
See Installing Fibre Channel Cables.

Before installing an FC cable, see Guidelines for Using Fiber Optic Cables.

Handling Static-Sensitive Components
Static electricity can damage memory modules, system boards, and other static-sensitive components. To prevent damaging the system, follow these precautions:
The Remote Replication premium feature provides online, real-time replication of data between storage arrays over a remote distance. In the event of a disaster or a catastrophic failure at one storage array, a second storage array can be promoted to take over responsibility for computing services. The Remote Replication premium feature requires a dedicated host port for replicating data between storage arrays. After the Remote Replication premium feature has been activated, one host I/O port on each RAID controller module is solely dedicated to replicating operations.
Data transfer performance is enhanced by maximizing bandwidth, which is the ability to process more I/O across more channels. Therefore, a configuration that maximizes the number of host channels and the number of drive channels available to process I/O maximizes performance. Faster processing speeds also maximize performance.
In addition to planning a topology that provides maximum performance, choose a RAID level that suits the planned applications.

While creating a topology for a RAID enclosure that contains only one RAID controller module, attach expansion enclosures that contain only one single environmental services monitor (ESM). Do not attach an expansion enclosure that contains two ESMs to a single-controller RAID enclosure.
Cabling is an important part of creating a robust storage array. Labeling the cables identifies system components and drive channels. System maintenance is easier when the cables are correctly identified. Label both ends of each cable. You can use adhesive office labels that are folded in half over the ends of each cable. Mark the labels with the port identifiers to which the cable is connected. Additional information can be provided by using color-coded cable straps (or ties) to group all cables associated with one component or drive channel.
If a component fails, the cables must be disconnected, the failed component replaced, and the cables reattached. Detailed labeling of the cables simplifies the component replacement process.
If you are adding a new expansion enclosure to an existing configuration, correctly labeled cables helps identify where to connect the new enclosure.
Pages referenced in this manual — manufacturer, support and downloads.
Owners and our team usually reply within a day — and your question helps the next person too.
Be the first to ask — other owners or our team will answer.