Dell - MD3000i - Printer-Friendly Format

Dell - MD3000i - Printer-Friendly Format Page 1 of 174
Dell Training Tool | MD3000i
Expand All Collapse All
•
•
Introduction
Welcome
Welcome
• Getting Started
•
•
Course Introduction
System Overview
Welcome
• Second Generation
• FW 07.35.38.60 This course is designed to teach the basics of the MD3000i iSCSI direct and network attached storage enclosure. The course is to be used in conjunction with th
• FW Ver. 07.35.31.XX
A08 RTS Dates: Americas - 08/31/2007 This image illustrates the MD3000i
◦ Firmware Upgrade
◦ Controller Departments: GSS L&D
Replacement
◦ Configuration Authors: John Ingle
Enhancements Ed Boehm
◦ Windows 2008 R2 David Spencer
◦ SLES 11
• FW Ver. 07.35.22.XX Contributing Sources:Dell
A07 GSS L&D
◦ FW Ver. PG Engineering
07.35.22.XX A07 Remote Installation teams
Overview
◦ New Features Contacting Dell: To contact Dell regarding issues with this training material, click the following link: Feedback.
■ New Features
Overview
■ Greater than Information in this document is subject to change without notice.
2TB LUN
Support ©2007 Dell Inc. All rights reserved. ™ Rev. A21
■ RAID 6
Support Reproduction in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.
■ IPV6 Support
For All Ports Trademarks used in this text: Dell, the DELL logo, and Dimension are trademarks of Dell Inc.; Intel, Pentium, and Celeron are registered trademarks of Intel Co
■ Smart BatteryCorporation.
(Smart BBU)
Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and names or their products. Dell Inc. disclaim
◦ Changes
■ Changes
Overview
■ Enhanced Printed 2/2/2011 12:22:48 PM MD3000i For Dell Employees Only
Load Expires 2/3/2011 12:22:48 PM Welcome This document is Dell Confidential
Balancing for
Multi-Path
Page Break Divider. Does not show when printed.
Drivers
■ New
Premium
Features
Getting Started
■ Firmware
Identification
and MDSM Using this Material
Version
■ MD The following sections provide information to help you effectively use this training material.
Firmware
Update
Utility Navigating the Material
■ Disk Group
Changes To navigate through this course, select topics using either the left navigation menu or the Previous/Next buttons at the top right corner of each page.
■ Disk
Metadata and This course is designed to be completed in the order in which the topics are presented. However, refresher training can be accomplished in any desired order.
Format
Changes
■ Simplex
Important Symbols
Controller
The following symbols are used to emphasize important notations in this material:
Replacement
■ Duplex
Controller A NOTE indicates important information that helps you make better use of your computer.
Replacement
■ Serial Shell
and Console A WARNING indicates either potential damage to hardware or loss of data and tells you how to avoid the problem.
Procedures
• Chassis A CAUTION indicates a potential for property damage, personal injury, or death. A Customer Experience (CE) Tip indicates important information
• Chassis 360
• Chassis Teardown
• Component Information Browser Requirements
• RAID Controller Module
◦ RAID Controller Dell's online courses are designed to work with Internet Explorer® 5.x and later, Netscape® versions 6.x and later, and Mozilla® 1.0.1. If you experience proble
Module Overview
◦ Enclosure Modes Additional Required Software
• Control Panel
• Bezel LEDs
• Physical Disks Adobe® Acrobat® (.pdf) files require Acrobat Reader®. You can download Acrobat Reader and get additional information from Adobe's website: http://www.a
file://C:\Users\Ironman\AppData\Local\Temp\Framework\Dell - MD3000i - Printer-Friendl... 2/3/2011

• Power Supply/Cooling
Fan Module LEDs
• Racking and Cabling Printed 2/2/2011 12:22:48 PM MD3000i For Dell Employees Only
• Racking Expires 2/3/2011 12:22:48 PM Getting Started This document is Dell Confidential
• Enclosure Cabling
◦ Host to MD3000i Page Break Divider. Does not show when printed.
Enclosure Cabling
◦ MD3000i to
MD1000 Enclosure
Expansion Cabling
Course Introduction
• Support Matrix
• Field-Replaceable Units The following sections provide general information about the course goal, objectives, delivery method, and prerequisites.
• RAID Controller Module
• Bezel Goal
• Physical Disks
• Physical Disk Blanks The goal of this course is to prepare you to effectively and efficiently troubleshoot technical issues with the PowerVault MD3000i.
• Control Panel
• Enclosure Midplane
• Power Supply/Cooling Objectives
Fan Modules
• System Management Second Generation PowerVault MD3000i
• System Architecture
• MDSM Compared to CLI The second generation objectives focus on what is new, and different about the second generation PowerVault MD3000i RAID controller firmware update and h
• MDSM Installation and
Host Configuration Given the information in this course and available tools, you will be able to:
◦ Windows Hosts
■ MDSM • identify the new features of the second generation PowerVault MD3000i firmware and software.
Installation • explain how to successfully migrate an MD3000 with all previous versions of firmware to the second generation firmware version without losing data.
■ iSCSI Host • identify what features have been enhanced with the release of second generation PowerVault MD3000i RAID controller firmware.
Configuration • explain how to successfully install and configure and PowerVault MD3000i in either a full or mixed IPv6 environment as well as an IPv4 environment, fo
using IPV4 • explain how to successfully configure the PowerVault MD3000i with RAID 6 LUNs.
■ iSCSI Host • explain how to successfully migrate a RAID5 LUN to a RAID 6 LUN without losing data.
Configuration • identify the requirements in order to successfully replace a Generation 2 or 1 controller on the PowerVault MD3000i.
using IPV6 • identify the differences between a first and second generation controller.
◦ RHEL Hosts • explain what happens when swapping a second generation PowerVault MD3000i RAID controller with a first generation PowerVault MD3000i controller
• MDSM Usage • explain what happens when repalcing a first generation PowerVault MD3000i controller with a second generation PowerVault MD3000i RAID controller
• Premium Features
◦ Comparison of NOTE:
Premium Features You will find all of the training information for the second generation of the PowerVault MD3000i RAID controller in the Generation 2 section of this onli
◦ Premium Feature -
Snapshot Virtual • New Features of the firmware update
Disk • Changes with the firmware update
◦ Premium Feature - • Troubleshooting information specific to the firmware update
Virtual Disk Copy • Firmware Update and Downrev Process
◦ Premium Feature
Recovery
Procedures First Generation PowerVault MD3000i
• SMcli Overview - The
Command Line Interface
Given the information in this course and available tools, you will be able to:
• SMcli - Command Line
Details • List the type and specifications of physical disks supported in the MD3000i Storage Array.
• Clustering • List the Field-Replaceable Units (FRU) used in the MD3000i Storage Array.
• Configuration Utility • Locate the removal/replacement procedures for all available FRUs.
• Overview • Demonstrate the proper cabling to be used.
• Launching the Utility • Name the functions and features of the MD3000i Storage Array and its components.
• Array Configuration • Describe the system architecture of the MD3000i Storage Array.
• Host Configuration • Describe the steps necessary to set up the iSCSI initiator
• Maintenance • Describe the steps necessary to initiate a iSCSI session
• Disk Operations and • Describe the steps necessary to set up CHAP on the host and storage array
Maintenance • Describe a host group.
• Configuration • List the steps necessary to create a host group.
Maintenance • List the steps necessary to create a disk group.
• Firmware Updates • List the steps necessary to create virtual disks within a disk group.
◦ Firmware and • List the steps necessary to perform host-to-virtual disk mapping.
NVSRAM • Describe the activation of the snapshot premium feature software.
◦ Physical Disk • Describe the activation of the virtual disk copy software.
Firmware • Describe the recovery procedure for the premium feature key.
• Service Tag Reset • Describe the recovery procedure for a lost or corrupted configuration.
Procedure • Describe the recovery procedure for an accidentally deleted virtual disk.
• Diagnosis and • Use the command line to accomplish routine as well as advanced configuration of the disk groups, virtual disks, and storage array.
Replacement of a • Describe the steps necessary to reset the administrator password from the serial interface.
Controller • Describe the steps necessary to collect and save the support files for troubleshooting.
• Upgrade a Simplex Array • Describe the steps necessary for the replacement of a RAID controller module.
to Duplex
• MD3000i Utilities
• SATA Support and Delivery Method
Procedures
• Product Positioning This original first generation curriculum was designed to be delivered by an instructor in a classroom setting. However, since the second generation curriculum
• Global Differences
• Configuration Changes
• SAS SATA II Hardware Prerequisites
• Firmware Update
• Single Controller SAS Technology
Replacement (DSP and MD3000 Basics
CRU)

Printed 2/2/2011 12:22:48 PM MD3000i For Dell Employees Only

Expires 2/3/2011 12:22:48 PM Course Introduction This document is Dell Confidential
System Overview
The MD3000i RAID Enclosure is a 3U external RAID storage array that is leveraged from the MD1000 chassis, and shares the same internal and back end arch
operating in either a single controller (simplex) or an active/active (duplex) redundant controller configuration. The MD3000i can be daisy-chained with up to tw
• Manual Controller The MD3000i enclosure supports up to fifteen 3.5" SAS physical disks and has redundant power supplies and fans in the base chassis. The MD3000i is also able
Replacement ports to provide true redundancy of the virtual disk paths. Either controller is able to take ownership of a virtual disk as changes in path availability dictate. Furt
• ESX 3.5 and 4.0 Best
Practices The MD3000i is positioned as the next evolution in iSCSI attached external storage. Because of its dual port external RAID controllers, and ability to switch-co
• Virtualization Support
• PowerVault VMware The MD3000i allows multiple servers access to a common, shared pool of storage without the cost and complexities of dealing with a storage infrastructure netw
Documentation and fabrics.
Media
• Diagnostic MD3000i Support Matrix
• Using the Support Bundle
and Logs
Click the link below for the latest systems support matrix information:
• Serial Shell and Console
MD3000i Support Matrix
Procedures
• Critical Events
• SNMP Alerts and Traps NOTE:
• Recovery Guru The support matrix at this link is updated once every 3 months only. This page will be updated with each new supported operating system (OS) release d
• Controller Log Collection
• Troubleshooting
• Hard Disk Drive
Troubleshooting
MD3000i RAID Enclosure Description
• Controller
Troubleshooting • iSCSI connected support for up to sixteen Windows®, Red Hat Linux, and SUSE Linux host servers via Fast or Gigabit Ethernet cables
• Virtual Disk Not on • Support for redundant or non-redundant configuration
Prefered Path • Two redundant, hot-pluggable active/active RAID controller modules
• Power Issues • Two redundant, hot-pluggable power supply/fan modules
• Cooling Issues • 512 MB of mirrored cache on each RAID controller module
• Log Reading • Battery backup in each RAID controller module that protects against cache data loss for up to 72 hours
• Recovery Guru • Online firmware updates for the RAID controller modules, NVSRAM, and physical disks
• MD3000/MD3000i Delta • Optional snapshot software
Knowledge Articles • Optional virtual disk copy
• Procedures • Multi-path failover for redundant configurations, which automatically reroutes I/O activity from a failed, offline, or removed RAID controller module to i
• Procedures - Setup and • Support for RAID levels 0, 1, 5, and 10
Usage • Support for 255 virtual disks with a maximum capacity of 2 TB each
• Tools and Utilities • Stripe element sizes of 8, 16, 32, 64, 128, 256, or 512 KB (default is 128 KB)
• Modular Disk Storage • 3U Enclosure with 15 3.5" SAS hard physical disk connectors
Manager Simulator • Physical disk support for 10 K and 15 K 3 Gbps SAS physical disks
• MD Utility and Analyzer • Integrated power supply/fan module
Tools • Activity LEDs for each slot
• Knowledge Check • Bi-color Status LEDs for each slot
• 2nd Gen Online KC • Support for up to two cascaded MD1000 enclosures for a total of 45 physical disks
• Release 2.1 Online KC
• Remote Installation
Resources
Operating System Support for iSCSI Host Servers
• Remote Install
Documentation Generation 2 - Firmware Version 07.xx.xx.xx
• Windows Install Video
• RHEL5 Install Video • Red Hat® Linux 5.2 Enterprise and Advanced Server, 32-bit and 64-bit
• VMware Install Video • Red Hat Linux 5.3 Enterprise and Advanced Server, 32-bit and 64-bit
• Appendixes • Solaris 10.6
• Course Outline
• Instructor Materials NOTE:
◦ PowerPoint All of the Operating Systems below are supported with Generation 2 firmware, but the Operating Systems above are only supported by Generation 2.
Presentations
◦ Classroom Setup Generation 1 - Firmware Version 06.xx.xx.xx
◦ Class Overview
◦ Class Outline
• Windows Server 2008 Web Edition, 32-bit and 64-bit version
• Useful Documents
• Windows Server 2008 Standard Edition, 32-bit and 64-bit version
• Document History
• Windows Server 2008 Enterprise Edition, 32-bit and 64-bit version
• Printer-Friendly Format
• Windows Server 2008 Datacenter Edition, 64-bit version
• Windows Server 2008 Small Business Edition, 64-bit version
• Windows Server 2008 Core Edition, 32-bit and 64-bit version
• Windows 2003 32-bit Standard Server and Enterprise Edition (SP1)
• Windows 2003 32-bit Standard Server and Enterprise Edition R2
• Windows 2003 64-bit Edition EM64T (SP1) & R2
• Red Hat® Linux 3.0 Update 6 Enterprise and Advanced Server, 32bit and 64bit
• Red Hat® Linux 4 Update 6 Enterprise and Advanced Server, 32bit and 64bit
• Red Hat® Linux 5 Update 1 (5.1) Enterprise and Advanced Server, 32bit and 64bit
• SUSE® Linux Enterprise Server 9 service pack 4 (x86-64)
• SUSE® Linux Enterprise Server 10 service pack 2(x86-64)
• VMWare® ESX 3.5 and 3.5i

NOTE:
Windows Server 2008 support requires controller firmware rev 06.70.15.60 and NVSRAM rev 67.08.90 or later.
Operating System Support for Management

MD3000i storage arrays can be configured and managed using the Modular Disk Storage Manager (MDSM) application. MDSM software can be run on an iSC
below.
• Windows Vista
• Windows XP Professional SP2
NOTE:
These operating systems are supported as a management station only.
They are not supported for iSCSI I/O attachment to the storage array.
Clustering Support
• Support for up to 16 node clusters with Windows 2008
• Support for up to 8 node clusters on Windows 2003 32-bit and R2
• Support for up to 8 node clusters on Windows 2003 EM64T and R2
Modular Disk Storage Manager

Modular Disk Storage Manager (MDSM) is the graphical user interface for the MD3000i Storage Array. MDSM software is used to create and manage multiple
MDSM also contains an optional event monitoring service that is used to send alerts when a critical problem with the storage array occurs and a command line i

Expires 2/3/2011 12:22:48 PM System Overview This document is Dell Confidential
FW 07.35.38.60
This firmware adds the following features to the MD 3000/i:
• Support for the coexistence of MD3000/i and MD32XX/i systems connected to the same host.
• Support and certification for ESX 4.1.
• Support and certification for Red Hat Enterprise Linux releases 4.9, 5.5 and SUSE Linux Enterprise 11 SP1.
NOTE:
Instructions on updating second generation firmware can be found here.
Coexistence with MD32xx/i

Coexistence with MD32xx/i is dependent on firmware levels of the storage systems, driver versions, and the operating system of the host.
This is a diagram of a host connected to a MD32xx and MD3000.

This is a diagram of a host connected to a MD32xxi and MD3000i.
NOTE:
The latest resource DVD for the MD32xxi has all the drivers necessary for coexistence for both SAS and ISCSI MDs. This version of the RDVD will be
Coexistence in a Windows Environment

Coexistence in Windows only requires the installation of the latest MD32xxi RDVD and the latest firmware for both arrays.
Coexistence in a Linux Environment

Ensure that both storage systems have the required firmware.
1. Insert and install the MD32xxi RDVD. The Host component is required for coexistence support and must be selected as a part of the installation procedur
2. Open a command (shell) prompt.
3. Navigate to the linux/coexistence directory on the resource media.
4. Run the following command to install:
./md_coexistence_util.sh install
5. Follow the on-screen instructions and answer the prompts according to the configuration you intend to deploy on the current host.
6. Reboot if requested.

Expires 2/3/2011 12:22:48 PM FW 07.35.38.60 This document is Dell Confidential
Firmware Upgrade
The release 2.1 firmware is displayed as version 07.35.31.60 within the storage array profile.
Upgrading to Release 2.1 Firmware

• Upgrading to the 07.35.31.60 firmware from within the same generation (i.e.; 07.xx.xx.xx) is performed using the process documented HERE.
NOTE:
It is possible to downgrade to a previous firmware as long as it is still in the same generation. You cannot downgrade to a previous generation.
• Upgrading to the 07.35.31.60 firmware from a previous generation (i.e.; 06.xx.xx.xx) is performed using the process documented HERE.
NOTE:
You can upgrade directly to 07.35.31.60 from a previous generation but you cannot downgrade back to a previous generation.

Expires 2/3/2011 12:22:48 PM Firmware Upgrade This document is Dell Confidential
Controller Replacement
Always replace the MD3000 RAID Controller hot while the system is up and operational to ensure that the firmware remains as established. Failure to do so cou
For full information on replacing a controller click HERE.


Expires 2/3/2011 12:22:48 PM Controller Replacement This document is Dell Confidential
Configuration Enhancements
This page lists the new configuration enhancements as part of release 2.1.
• Configurations with two MD3000s

• Battery Learn Cycle
• Creating Host to Virtual Disk Mappings
• Additional Disk Group and Virtual Disk Expansion information
• VD Copy is slow with SATA disks
Configurations with two MD3000s

The following images show supported configurations for connecting two MD3000s to 1 or 2 hosts.
WARNING:
These configurations are only supported with Second Generation firmware on the MD3000 storage arrays.
Single Host connected to Two MD3000 Storage Arrays
Image: Single Host connected to Two MD3000 Storage Arrays
Two Hosts connected to Two MD3000 Storage Arrays

Image: Two Hosts connected to Two MD3000 Storage Arrays
Battery Learn Cycle

In 2nd generation firmware systems, the cache offload battery undergoes a learn cycle every 13 weeks in order to condition the battery and ensure that it is in a g
VDs in the system. This might result in a temporary performance impact while the battery learn cycle is taking place. A learn cycle takes place at the following
• First time upgrade from 1st generation firmware to 2nd generation firmware
• Every 13 weeks.
The next scheduled learn cycle can be seen in the MD storage manager. This can be postponed by up to 7 days at a time through the GUI. The following SMcli
Creating Host to Virtual Disk Mappings

It is possible to create Host-to-Virtual Disk mappings to a host group or to a single host, even if that host is part of a host group. In the latter case, the mapped ho
Additional Disk Group and Virtual Disk Expansion information

Disk Group expansion can be achieved from the MD Storage Manager as well as through the CLI. It is only possible to add a single disk at a time (or two in the
Virtual disk expansion can be achieved through the CLI. The command to expand a virtual disk is as follows: set virtualDisk [VDname] addCapacity=sizetob
During disk group and virtual disk expansion operations, there is complete access to the virtual disks and disk group redundancy is maintained at all times. How
Refer to the User’s Guide for additional details on Disk Group and Virtual Disk expansion.
VD Copy is slow with SATA disks

A Virtual Disk Copy operation might take much longer when a new copy is created on SATA disks. This performance can be improved by first creating the virt

Expires 2/3/2011 12:22:48 PM Configuration Enhancements This document is Dell Confidential
Windows 2008 R2
Release 2.1 adds support and is required for Windows 2008 R2.
• Load Balancing in Windows 2008

• Setting up the iSCSI Initiator on Windows 2008 R2
Load Balancing in Windows 2008

Load balancing in Windows 2008 is provided by the MPIO driver under the MPIO tab. The only supported options for use with the MD3000/MD3000i are:
• Least Path Weight

• Least Queue Depth
Options like “Failover only”, “Round Robin” and “Least Blocks” may be visible but are not supported.

Load Balancing with the MD3000/MD3000i is only supported by using the settings under the MPIO tab and not under the “Session Connections” tab.
NOTE:
The settings located within the MPIO tab are for each individual LUN.
Navigating to the MPIO tab
1. Open the iSCSI initiator properties from the Control Panel in Windows 2008.
2.
Click the Targets tab.
iSCSI MPIO
3.
Select the Target. Click the Details button.
iSCSI MPIO
4.
From the Devices tab, Select a Device. Click the Advanced button.

Navigating to the MPIO tab

iSCSI MPIO
5.
Select the MPIO tab. Click OK when finished making any changes.
iSCSI MPIO
Setting up the iSCSI Initiator on Windows 2008 R2

Please refer to the Installation Guide for descriptions and detailed information.
Performing Target Disco

1.
Click Start > Programs > Microsoft iSCSI Initiator or Start > All Programs > Administrative Tools > iSCSI Initiator.
2.
Click the Discovery tab.
3.
Under Target Portals, click Discover Portal and enter the IP address or DNS name of the iSCSI port on the storage array.
4.
If the iSCSI storage array uses a custom TCP port, change the Port number. The default is 3260.
5.
Click Advanced and set the following values on the General tab:
• Local Adapter: Must be set to Microsoft iSCSI Initiator.

• Source IP: The source IP address of the host you want to connect with.
• Data Digest and Header Digest: Optionally, you can specify that a digest of data or header information be compiled during transmission to assist in

Performing Target Disco

• CHAP logon information: Leave this option unselected and do not enter CHAP information at this point, unless you are adding the storage array to
6. Click OK to exit the Advanced menu, and OK again to exit the Add Target Portals screen. To exit the Discovery tab, click OK.
If you plan to configure CHAP authentication, do not perform discovery on more than one iSCSI port at this point. Stop here and go to the next step, Step 4: Co
If you do not plan to configure CHAP authentication, repeat step 1 thorough step 6 (above) for all iSCSI ports on the storage array.
Configure CHAP Authentica

1.
Click Start > Programs > Microsoft iSCSI Initiator or Start > All Programs > Administrative Tools > iSCSI Initiator.
2.
If you are NOT using mutual CHAP authentication skip to the step 4 below.
3.
If you are using mutual CHAP authentication:
• click the Configuration tab

• select CHAP
• at Initiator CHAP secret, enter the mutual CHAP secret you entered for the storage array
4.
5.
Under Target Portals, select the IP address of the iSCSI port on the storage array and click Remove. The iSCSI port you configured on the storage array d
6.
Under Target Portals, click Discover Portal and re-enter the IP address or DNS name of the iSCSI port on the storage array (removed above).
7.
Click Advanced and set the following values on the General tab:
1. Local Adapter: Should always be set to Microsoft iSCSI Initiator.

2. Source IP: The source IP address of the host you want to connect with.
3. Data Digest and Header Digest: Optionally, you can specify that a digest of data or header information be compiled during transmission to assist in
4. CHAP logon information: Enter the target CHAP authentication username and secret you entered (for the host server) on the storage array.
5. Perform mutual authentication: If mutual CHAP authentication is configured, select this option.
NOTE:
IPSec is not supported.
8.
Click OK. If discovery session failover is desired, repeat step 5 and step 6 (in this step) for all iSCSI ports on the storage array. Otherwise, single-host por
NOTE:
If the connection fails, make sure that all IP addresses are entered correctly. Mistyped IP addresses are a common cause of connection problems.
Connect to the Target Stor

1.
Click Start > Programs Microsoft iSCSI Initiator or Start > All Programs > Administrative Tools > iSCSI Initiator.
2.
Click the Targets tab. If previous target discovery was successful, the iqn of the storage array should be displayed under Targets
3.
Click Connect.
4.
Select Automatically restore this connection when the system boots.
5.
Select Enable multi-path.
6.
Click Advanced and configure the following settings under the General tab:
• Local Adapter: Must be set to Microsoft iSCSI Initiator.

• Source IP: The source IP address of the host server you want to connect from.
• Target Portal: Select the iSCSI port on the storage array controller that you want to connect to.
• Data Digest and Header Digest: Optionally, you can specify that a digest of data or header information be compiled during transmission to assist in
• CHAP logon information: If CHAP authentication is required, select this option and enter the Target secret.
• Perform mutual authentication: If mutual CHAP authentication is configured, select this option.
NOTE:
IPSec is not supported.

Connect to the Target Stor

7.
Click OK.
To support storage array controller failover, the host server must be connected to at least one iSCSI port on each controller. Repeat step 3 through step 8 f
NOTE:
To enable the higher throughput of multipathing I/O, the host server must connect to both iSCSI ports on each controller, ideally from separate host-
between the controllers.
The Status field on the Targets tab should now display as Connected.
8.
Click OK to close the Microsoft iSCSI initiator.

Expires 2/3/2011 12:22:48 PM Windows 2008 R2 This document is Dell Confidential
SLES 11
Release 2.1 adds support for SLES 11.
• Linux Installation
• Installing the iSCSI Initiator on a SLES 11 System
• Supported File Systems in SLES 11
Linux Installation
During Linux OS installation, the installer will list all volumes that are discovered from MD3000/MD3000i, including virtual disks that are mapped to the host a
selected. The Universal Xport disk(s) cannot be selected for installation, otherwise it will result in non-responsiveness from the array.
Installing the iSCSI Initiator on a SLES 11 System

You can install the iSCSI initiator software on SUSE Linux Enterprise Server Version 11 systems either during or after operating system installation.
To install the iSCSI initiator during SLES 11 installation:

1. At the YaST Installation Settings screen, click Change.
2. Click Software, then select Search.
3. In the Search box, enter iscsi.
4. When the open-iscsi and yast2-iscsi-client modules are displayed, select them.
5. Click Accept.
6. If a dialog box regarding dependencies appears, click Continue and proceed with installation.
Installing the iSCSI initiator after SLES 11 installation:

1. Select Desktop > YaST > Software > Software Management.
2. Select Search.
3. In the Search box, enter iscsi.
4. When the open-iscsi and yast2-iscsi-client modules are displayed, select them.
5. Click Accept.
NOTE:
iSCSI boot of LUN through a target IPv6 address needs a workaround from Novell. Details please refer to document 7004216 on the Novell website.
Supported File Systems in SLES 11

The following file systems are supported with SLES 11: ext2, ext3, Reiserfs, vfat, bfs, XFS, msdos, umsdos and nfs

Expires 2/3/2011 12:22:48 PM SLES 11 This document is Dell Confidential
FW Ver. 07.35.22.XX A07 Overview

The purpose of the Second Generation section of the PowerVault MD3000i Training documentation is to:
• explain the new features of the second generation PowerVault MD3000i when compared to the first generation.
• explain what has changed with the second generation PowerVault MD3000i.
• explain how to troubleshoot issues with the second generation of the PowerVault MD3000i.

WIIFM - What's In It For Me

Gaining a complete knowledge and understanding of the new features and changes with the PowerVault MD3000i second generation will help you successfully
NOTE:
To see a complete listing of the objectives for the PowerVault MD3000i training documentation, please refer to the course introduction page of this docum

Expires 2/3/2011 12:22:48 PM FW Ver. 07.35.22.XX A07 Overview This document is Dell Confidential
New Features Overview

What is the second generation release of the PowerVault 3000i?
The second generation release of the PowerVault MD3000i:
• is second generation firmware and host software for the MD3000i.

• It adds various features including the following major features:
◦Greater than 2TB LUNs

◦RAID 6
◦IPv6 support for all iSCSI and management ports
◦Smart Battery (Smart BBU)
NOTE:
The features section of this training documentation contain detailed information about each of these major features.
• There is no change in the existing MD3000i hardware. Existing hardware can be upgraded to the 2nd generation firmware. The upgrade is one way only (
• After RTS, all shipped MD3000i systems and controllers will have second generation firmware.
NOTE:
Any existing first generation controllers in stock will not be upgraded.

Expires 2/3/2011 12:22:48 PM New Features Overview This document is Dell Confidential
Greater than 2TB LUN Support

With the second generation release of the PowerVault MD3000i firmware, LUNs can now be larger than 2 Terabytes.
• the size of the LUN is limited by number of disks in the RAID array.
• up to 45 disks can now be used in a RAID0 and 44 disks in a RAID 10. RAID 5 and RAID 6 are limited to a maximum of 30 disks. The table below bette
RAID Type Limit on the Number of Disks

RAID 0 45
RAID 10 44
RAID 5 30
RAID 6 30

Expires 2/3/2011 12:22:48 PM Greater than 2TB LUN Support This document is Dell Confidential
RAID 6 Support
With the second generation RAID controller firmware, Dell Engineering has enabled support for RAID 6 with the PowerVault MD3000i.
What is RAID 6?
RAID 6 (Striping With Dual Distributed Parity), provides data redundancy by using data striping in combination with distributed parity information. Similar to
maintains two disk blocks with parity information. The additional parity provides data protection in the event of two disk failures.
Some of the characteristics of RAID 6 iclude:
• RAID 6 requires a minimum of 5 disks

NOTE:
Although the industry standard permits creation of RAID 6 with four drives, the MD3000/MD3000i requires five. If one wants a configuration with
redundant drives, and thus increase the efficiency.
• Virtual Disks with RAID 6 can be created, migrated and adjusted the same way as other RAID types.
NOTE:
Note that disk groups cannot be migrated to PowerVault MD3000i arrays with first generation RAID controllers.
• a RAID 6 virtual disk are limited to a maximum of 30 physical disks.
The figure below illustrates RAID 6. In this figure the second set of parity drives are denoted by Q. The P drives follow the RAID 5 parity scheme. The parity b
needs to be generated for each write operation, there is a performance hit during write. Due to dual data protection, a RAID 6 VD can survive the loss of two dri
This image illustrates RAID 6, with five drives using a data stripe and a two parity stripes. Since RAID 6 has two parity stipes
up to two drives can fail without data loss.
Creating a RAID 6 Array Using MDSM
Creating a RAI
1. From the Summary Tab of MDSM, click the Configure tab.
From the Summary Tab of MDSM, click the Configure tab.
2. On the configure tabe of MDSM, click the Create Disk Groups and Virtual Disks option.
On the configure tabe of MDSM, click the Create Disk Groups and Virtual Disks
option.
3. An error message may be displayed stating that "No Hosts Have Been Configured." You can configure hosts later. Click ok, to continue.
An error message may be displayed stating that
4. You will now create a Disk Group for the RAID 6 array. Select the option, Disk Group: Create a new disk group using the unconfigured capacity in the st
You will now create a Disk Group for the RAID 6 array. Select the option, Disk Group: Create a new disk group using the unconfigured capacity in the storage
array.
5. Now you need to specify the name of the new Disk Group. Be specific, so that you will remember the name of the group in the future. You may use upto
Now you need to specify the name of the new Disk Group. Be specific, so that you will remember the name of the group in the
future.
6. Now you will choose the option for, "Automatic: Choose from a list of automatically generated physical disks and capacity options" and then click next to
Now you will choose the option for,
7. On this screen you will select the RAID type and overall capacity for the newly specified RAID Group. RAID 5 is the default option, used the pull down
On this screen you will select the RAID type and overall capacity for the newly specified RAID Group. RAID 5 is the default option, used the pull down menu to select RAID
6.
8. Once you have selected RAID 6, notice that the options for capacity have changed from a minimum of 3 drives to a minimum of 5 drives. Choose the 5 dr
Once you have selected RAID 6, notice that the options for capacity have changed from a minimum of 3 drives to a minimum of 5 drives. Choose the 5 drive option, or any other option to continue.
9. Now that you have selected the RAID type and the capacity (number of disks) for the RAID group, click finish. This will create the RAID group.
Now that you have selected the RAID type and the capacity (number of disks) for the RAID group, click finish. This will create the RAID
group.
10. MDSM will now report to you that the RAID group has been successfully created. Now you need to create a virtual disk or disks within your newly create
MDSM will now report to you that the RAID group has been successfully created. Now you need to create a virtual disk or disks within your newly created RAID group. Select the option
for
11. On this next screen you will set the new virtual disk's capacity, name of the virtual disk and virtual disk I/O characteristics. Use the defaults here unless yo
click next to continue.
On this next screen you will set the new virtual disk's capacity, name of the virtual disk and virtual disk I/O characteristics. Use the defaults here unless you want a specific configuration for the virtu
continue.

Creating a RAI
12. On this next screen you will set the new virtual disk's capacity, name of the virtual disk and virtual disk I/O characteristics. Use the defaults here unless yo
click next to continue.
On this next screen you will set the new virtual disk's capacity, name of the virtual disk and virtual disk I/O characteristics. Use the defaults here unless you want a specific configuration for the virtu
continue.
13. On this screen you will map the virtual disk to a host. You have two options, specify the host now (this can be i-SCSI hosts with the PowerVault MD3000
On this screen you will map the virtual disk to a host. You have two options, specify the host now (this can be i-SCSI hosts with the PowerVault MD3000i and SAS Hosts with the PowerVault MD300
disk.
14. MDSM will now state that the vitual disk has been successfully completed and will ask if you want to create another virtual disk. For our purposes we wil
MDSM will now state that the vitual disk has been successfully completed and will ask if you want to create another virtual disk. For our purposes we will select
No.
15. MDSM will now return to the default screen of the configure tab, click the Summary tab to return to it.
MDSM will now state that the vitual disk has been successfully completed and will ask if you want to create another virtual disk. For our purposes we will select
No.
16. On the Summary tab of MDSM you will notice that there is currently one Operation in Progress under the status section. The process currently in progress
Disk Groups and Virtual Disks section of the summary tab. Click Diskgroups and Virtual Disks link.
On the Summary tab of MDSM you will notice that there is currently one Operation in Progress under the status section. The process currently in progress, is the background initialization of the new
link.
17. On the Blink Disk Groups window, you will see the total unconfigured disk capacity (if physical disks are unassigned and available), and disk groups curr
On the Summary tab of MDSM you will notice that there is currently one Operation in Progress under the status section. The process currently in progress, is the background initialization of the new
link.
18. After expanding the disk group you will notice that the virtual disk is still being created, this is because the background initialization is still taking place.
After expanding the disk group you will notice that the virtual disk is still being created, this is because the background initialization is still taking
place.
19. Once the background initialization is complete, the virtual disk will return to the optimal state. From here the RAID 6 virtual disk is ready for use, if you h
Once the background initialization is complete, the virtual disk will return to the optimal state. From here the RAID 6 virtual disk is ready for use, if you have not done so already, you should map hos
System.

Expires 2/3/2011 12:22:48 PM RAID 6 Support This document is Dell Confidential
IPV6 Support For All Ports

With the second generation release of the MD3000i RAID controller firmware, IPv6 is now supported on all available ethernet ports (MD3000i Managemen
IPv6 is now supported on Linux. However, this is only supported on open-iSCSI initiators (SLES10 and RHEL5). In order to prevent login failures, IPv6 should

Expires 2/3/2011 12:22:48 PM IPV6 Support For All Ports This document is Dell Confidential
Smart Battery (Smart BBU)

What is Smart Battery?
The battery logic has been updated with the second generation firmware release of the PowerVault MD3000i. Smart battery allows the RAID controller to moni
NOTE:
With the Smart Battery technology, the age of the battery is no longer used to determine battery replacement. The battery uses a “learn cycle” to recalibrate
What is a Battery Learn Cycle?

Triggers
The battery will start a “battery learn cycle” at the following events:
• the first time the controller is powered up because a learn cycle has not run earlier.
• when a replacement battery module is installed.
• every 91 days (13 weeks), the controllers will initiate a learn cycle.
Actions
A battery learn cycle consists of the following actions:

1. charge of the RAID battery, if it is not fully charged.

2. the RAID battery is discharged to a preset threshold.
3. the RAID battery is charged back up until it is fully charged.
Events
The following events occur during a learn cycle:
1. approximately one hour prior to the next scheduled Battery Learn Cycle start, a MEL (Major Event Log) message will be generated.
2. an hour later the learn cycle starts and cache is disabled, both of these events are logged in MEL.
3. when the 24 hour threshold is crossed, a low battery capacity message is logged in MEL.
4. after a period of approximately 2 hours, the battery will hold enough charge to cross the 24 hour threshold again and a "battery capacity is sufficient" mes
5. with the learn cycle for battery completed, a MEL event will signal end of learn cycle.
6. finally the controller cache is re-enabled once the learn cycle is complete.
NOTE:
During a learn cycle, the system cache is turned off. Thus if I/O is taking place on the PowerVautl MD3000i, the cache being disabled can impact performa
Exceptions to Successful Battery Learn Cycle Completion

• If learn cycle is interrupted, an Incomplete battery learn cycle message will be logged in MEL. The next learn cycle is scheduled for 91 days later.
• If the maximum capacity learned is not sufficient to satisfy the 72 hour hold requirement, the following critical MEL event will be logged: Insufficient lea
• Other failures, like failure to charge will be logged in the same way they were logged in the 1st generation.
FAQs - Frequently Asked Questions

NOTE:
This information applies to Controller Firmware Version 07.35.xx.xx and higher.
What is Smart battery?

Smart battery allows the RAID controller to monitor different parameters on the cache offload batteries. It relies on a combination of hardware/firmware to mon
exchanged through a two wire interface between the controller and the battery module. Most of the data is programmed on the battery module during manufactu
How is the health of the battery assessed?

The first time the controller is powered up, a new battery module is installed or periodically, every 13 weeks, the controllers will initiate a learn cycle; the batter
that the battery is still capable of holding enough charge to guarantee the cache offload requirement of 72 hours that the RAID controller offers.
Previous versions of controller firmware relied solely on battery age and the ability of the battery to charge, to guarantee the 72 hour cache offload requirement.
What will I see during a learn cycle?

Approximately one hour prior to the next scheduled start of A learn cycle, the following informational event is reported in the Major Event Log (MEL): 0x7304
cache not enabled or was internally disabled. The controllers' cache will be disabled during the learn cycle.
Because the battery needs to be discharged, it will eventually cross the threshold where cache offload can only be guaranteed for a period of 24 hours. When thi
battery will hold enough charge to cross the 24 hour threshold again, registering the following event in the MEL: 0x730E Battery capacity is sufficient.
Is performance affected in any way?

If IOs are running performance will be affected while the controllers' cache is disabled. The duration of the complete learn cycle is typically around 15 hours, an
but will not generate a MEL entry. The current state of the cache can be verified through the GUI's Storage Array Profile.
How do I know there is a problem with my battery?

If a problem occurs during the learn cycle one the following critical event will be registered in the MEL: 0x730F Incomplete battery learn cycle. If the maximum
capacity. Other battery failures may also be reported, refer to the user guide for details.
Can I change a learn cycle schedule?

A learn cycle is automatically started the first time a controller is powered up or a new battery module is installed. The next instance of the learn cycle will be au
this to a day and time that will have the least impact on your applications. A learn cycle cannot be stopped or paused once it has started.
Scheduling a Learn Cycle

To schedule a Learn Cycle use the “change battery settings” link under the “tools” tab of MDSM (Modular Disk Storage Manager).
From the Change Battery Settings window, you can set the approximate day and time of the week that the next battery learn cycle starts.
NOTE:
This time is not exact, but correct to within 1 hour.

Expires 2/3/2011 12:22:48 PM Smart Battery (Smart BBU) This document is Dell Confidential

Changes Overview
What has Changed With the Second Generation Firmware?
With the PowerVault MD3000i second generation RAID controller firmware release, Dell Engineering has made the following changes:
• with implementation of Enhanced Load Balancing for the multi-path drivers.

• the addition of new Premium Feature Keys.
• with using the new MD Firmware Update Utility to upgrade from first to second generation firmware.
• the disk group creation process has changed.
• enhanced disk group migration.
• with revised disk metadata and format.
• with a new process for simplex controller replacement.
• with a new process for duplex controller replacement.
• changes to the serial shell and console procedures.
Customer Documentation
Customer documentation for first and second generation PowerVault MD3000i releases will be marginally different. Both generations customer documentation

Expires 2/3/2011 12:22:48 PM Changes Overview This document is Dell Confidential
Enhanced Load Balancing for Multi-Path Drivers

First Generation
Up until the release of the second generation PowerVault MD3000i RAID controller firmware, the only load balancing policy was Round Robin which behave
• selects the path based on the round robin policy and returns to the caller for sending I/O to the LUN.
• all paths are treated equally.
• is not optimal for mixed-host support since the host may have different bandwidth or transfer speeds.
Second Generation
The second generation firmware release adds new additional load-balancing policies, specifically:

• Least Path Weight
Features for the New Load Balancing Policies With Second Generation Firmware
Least Queue Depth
• selects a path based on least number of outstanding commands on the initiator port.
• treats large block request and small block request equally.
• turns into round robin if the number of outstanding commands are the same on each initiator port.
• can be used in mixed host port configurations.
Least Path Weight (Windows Only)

• Each data path to a virtual disk is assigned a weight factor.
• The path with the least path weight will be selected.
• If more than one path have the same weight, round robin will be used for these paths.
• Least Path Weight is mainly used to optimize performance for access through different data ports with different speeds.
• Also can be used to exclude data paths with frequent link errors.
• Not applicable to Linux. Linux does not have a user interface similar to windows WMI to access and specify path weight at run and boot time.
Supported and Default Load Balancing Policies Per Operating System
Operating System Policy Applied Per Device or Per Host Policies Supported for MD3000i
Windows Server 2008 per device allowed for both MD3000 and MD3000i Round Robin, Least Queue Depth, Least Path Weight
Windows Server 2003 per device allowed for iSCSI initiator associated devices only (MD3000i) Round Robin, Least Queue Depth, Least Path Weight
Linux RHEL 4 policy applied per host only (all devices for that host) Round Robin, Least Queue Depth
Linux RHEL 5 policy applied per host only (all devices for that host) Round Robin, Least Queue Depth
Linux SLES 9 policy applied per host only (all devices for that host) Round Robin, Least Queue Depth
Linux SLES 10 policy applied per host only (all devices for that host) Round Robin, Least Queue Depth

Linux - Setting Load Balance Policies

To make a persistent change (across reboots) use mpp.conf
1. Set the LoadBalancePolicy parameter in /usr/src/linuxrdac-09.03.0C06.0030/mpp.conf to:
◦ 0: Round Robin
◦ 1: Least Queue Depth
◦ Any other input value will be rejected
NOTE:
Remember Least Path Weight is not supported by any distribution of Linux, this Load Balancing Policy option is only available in Windows.
2. Changes only take effect after rebuilding RAMdisk image (mkinitrd) and rebooting.
To make a dynamic change

At the console, type :
1. mppUtil –o LoadBalancePolicy=0x0 for round robin

2. mppUtil –o LoadBalancePolicy=0x1 for least queue depth
You can save the settings for persistence by using the SaveSettings parameter as follows:
mppUtil –o LoadBalancePolicy=n, SaveSettings
This change is lost after reboot unless the setting is saved and the RAMdisk is rebuilt using mkinitrd.
Windows Server 2008 - Setting Load Balance Policies

In windows Server 2008 there are three processes that can be used to set the load balancing policy for the multipath driver: using the iSCSI Initiator Menu optio
Using the iSCSI Initiator Menu Options to Set Load Balancing Policy
Using the iSCSI I

1. From the start menu, select iSCSI Initiator.
From the start menu, select iSCSI Initiator.
2. The iSCSI Initiator Properties window appears, select the targets tab.
The iSCSI Initiator Properties window appears, select the targets

tab.
3. Select the Target from the list, and click the Details button.
Select the Target from the list, and click the Details
button.
4. The Target Properties window is displayed, with the sessions tab displayed. Select the Devices tab.
The Target Properties window is displayed, with the sessions tab displayed. Select the Devices
tab.
5. Select the Dell MD3000i SCSI Disk Device, and click the Advanced button.
Select the Dell MD3000i SCSI Disk Device, and click the Advanced
button.
6. The Device Details window is now revealed with the General tab displayed, select the MPIO tab.
The Device Details window is now reavealed with the General tab displayed, select the MPIO
tab.
7. On the MPIO tab you will be able to set the Load Balance Policy using the pull down menu.
On the MPIO tab you will be able to set the Load Balance Policy using the pull down
menu.
Six options are available to the Administrator, these are:
• Fail Over Only

• Round Robin
• Round Robin with Subset
• Weighted Paths
• Least Blocks
NOTE:
Remember Least Queue Depth is set as the Default option in Windows.
Using the Device Manager Menu Options to Set Load Balancing Policy

Using the Device M

1. From the Device Manager Snapin of Server Manager, expand Disk drives.
From the Device Manager Snapin of Server Manager, expand Disk

drives.
2. Select the Dell MD3000i Multi-Path Disk Device.
Select the Dell MD3000i Multi-Path Disk

Device.
3. Right click on the Dell MD3000i Multi-Path Disk Device, and select Properties.
Right click on the Dell MD3000i Multi-Path Disk Device, and select
Properties.
4. The Dell MD3000i Multi-Path Disk Device Properties windows is displayed. Select the MPIO tab.
The Dell MD3000i Multi-Path Disk Device Properties windows is displayed. Select the MPIO
tab.
menu.
Using the Disk Management Menu Options to Set Load Balancing Policy
Using the Disk Man

1. From the Disk Management Snapin of Server Manager, Select the MD3000i virtual disk volume.
From the Disk Management Snapin of Server Manager, Select the MD3000i virtual disk
volume..
2. Right click on the MD3000/MD3000i virtual disk volume, and select properties from the menu.
Right click on the MD3000/MD3000i virtual disk volume, and select properties from the
menu.
3. The General tab of the Dell MD3000i Multi-Path Disk Device Properties window is displayed. Select the MPIO tab.
The General tab of the Dell MD3000i Multi-Path Disk Device Properties window is displayed. Select the MPIO
tab.
menu.
Windows Server 2003 - Setting Load Balance Policies

On Windows 2003, the load balancing policy can only be changed through the iscsi initiator menu.
NOTE:
It is important to keep in mind the following when using Load Balancing with Multi-Path Drivers in windows:
• The path is chosen upon receipt of every virtual I/O request.

• Failover is possible in certain scenarios where a workable path cannot be found to the preferred controller.

Enhanced Load Balancing for Multi-
Expires 2/3/2011 12:22:48 PM This document is Dell Confidential
Path Drivers
New Premium Features

With the MD3000i RAID controller second generation firmware dell has added two new Premium Features:
• Enabling 16 to 32 Storage Partitions - This increases the number of partitions on an MD3000i from 16 to 32.
• 8 Snapshots
• 8 Virtual Disk Copies
This page provides more information about these Premium Feature Keys.
16 to 32 Storage Partitioning (PFK)

Storage partitioning enables host servers to share access to virtual disks in a storage array. A storage partition is a logical entity consisting of one or more virtual
server or host group, then define a host-to-virtual disk mapping.
When customers use this key, keep in mind the following:

• it can be used when running the iSCSI initiator in the guest OS to enable up to 32 virtual machines, but running the iSCSI initiator in the guest OS con
iSCSI initiator, 4 of the 32 storage partitions will be consumed.
• A better option may be to run the iSCSI initiator at the hypervisor layer, there is no need for additional partitions, because Running the iSCSI initiato
use the same single initiator. However, one problem with this type of solution is, hypervisors at this time do not officially support Multi-Path with iSCSI c
• This key does not allow for support of greater than 16 physical servers per MD3000i.
8 Snapshots (PFK)
Up to 8 Snapshots are now supported through a Premium Feature Key (PFK):
• Customers can purchase a 4 snapshot PFK or an 8 snapshot PFK.

• Customers with an existing 4 snapshot premium feature key can get the 8 snapshot PFK at a discounted price (equivalent to an upgrade).
• The total snapshots per system are limited to a maximum of 128 as with the first generation firmware.
8 Virtual Disk Copies (PFK)

The total virtual disk copies per system are limited to a maximum of 128 as with the first generation firmware.
Enabling These New Premium Feature Keys

The process to enable these new PFKs is identical to the way PFKs have been enabled in the past. Use the View/Enable Premium Features link on the Tools tab
This image illustrated the View/Enable Premium Features screen of MDSM. Here you can enable Premium Features.
Recovering These New Premium Feature Keys

The process to recover these New Premium Feature Keys is identical to the first generation PFK recovery process, please refer to the Premium Feature Recovery

Expires 2/3/2011 12:22:48 PM New Premium Features This document is Dell Confidential
Firmware Identification and MDSM Version

You can identify the firmware revision of the RAID controllers using in a MD3000i/MD3000 within MDSM by selecting the View Storage Array Profile link
configuration section of the RAID controllers tab.
Second generation firmware can be identified by a version number like this: 07.xx.xx.xx.

This image illustrates how to a RAID controller with Generation 2 firmware.
First generation firmware can be identified by a version number 06.xx.xx.xx.
This image illustrates how to a RAID controller with Generation 1 firmware.
First and Second Generation MDSM

The second generation MD storage manager will have a version number as 03.xx.xx.xx (see image below) as compared to the 1st generation MD Storage manag
You can determine the customer's MDSM version by invoking the About Modular Disk Storage Manager link on the support tab.
This image illustrates the about MDSM window.

Firmware Identification and MDSM
Version

MD Firmware Update Utility

"Second Generation" is a general description of the firmware that supports RAID 6, LUNs that are larger than two Terabytes, and smart battery (a battery modul
designated as 07.xx.xx.xx firmware, in contrast with the existing 06.xx.xx.xx Firmware Downloads firmware that may be referred to as "First Generation" firmw
upgrade the system so that it supports the new version 07.xx.xx.xx firmware.
• The MD Firmware Upgrade Utility is only used to upgrade from 1st generation firmware to 2nd generation firmware, once the MD3000/MD3000
• This upgrade must be performed as an offline task without any I/O.
• All volume configuration, premium features and host mappings will be preserved through the update process.
• This is a one-way upgrade. It is not possible to return to 1st generation firmware after starting this upgrade procedure without losing all data and configura
• The MD Firmware Upgrade Utility is installed along with the latest version of the MD Storage Manager. Both applications can be installed using the M
• MD Storage Manager can be used to perform all other firmware updates with the exclusion of the 1st generation to 2nd generation upgrade.
• The latest version of the MD Storage Manager can still be used to manage any MD3000/MD3000i running 1st generation firmware. However, the 2nd ge
different. In fact, a single host should NOT be connected to both a 1st gen and a 2nd gen array.
The utility helps ensure that any storage array you select for upgrade:
1. has a supported RAID controller module model and RAID controller module firmware version.
2. has no pre-existing condition that may prevent the upgrade from completing successfully.
3. has its configuration and event log saved prior to upgrade for later use, if required.
4. is offline for the minimum amount of time required.
Storage Array Status Reporting

Once the MD Firmware Update Utility has identified a storage array it will display the status of the array in the Status column, as shown in the image below.
This image illustrates the main window of the MD Firmware Update

Utility.
Possible Storage Array Status Indicators

Each storage array has a status, as indicated an icon and a text description. The following table contains all of the possible storage array statuses and their meani
Icon Status
The storage array cannot be upgraded for one or more reasons (see storage array conditions that prevent firmware
upgrade).
Not-upgradeable The storage array cannot b
There were no problems detected and you can upgrade the storage
array.
Upgradeable: Optimal There were no problems d
One or more problems were detected but the storage array can still be
upgraded.
Upgradeable: Needs Attention One or more problems we
Progress bar Downloading RAID Controller Module
The storage array has pending firmware that is ready for
activation.
Firmware pending The storage array has pen
The new RAID controller module firmware is activating (i.e. replacing the current
firmware).
Firmware activating The new RAID controller
The storage array has the required version of

firmware.
Firmware OK The storage array has the
Storage array status is

refreshing.
Refreshing Storage array status is refr
The utility is connecting to the storage

array.
Connecting The utility is connecting t
There was an error during the

operation.
Error There was an error during
The storage array cannot be

contacted.
Unresponsive The storage array cannot b
Storage Array Conditions Preventing Upgrades

Storage array conditions that prevent an upgrade from Generation 1 to Generation 2 may include:
• assigned physical disks that have failed.

• in-use hot spare physical disks.
• incomplete virtual disk groups that are missing associated physical disks.
• exclusive operations in progress for any virtual disk groups (such as defragmenting a disk group, copyback to a physical disk, initialization of a virtual dis
• missing virtual disks registered to the storage array.
• either RAID controller module in a state other than optimal.
• physical Disks with DACstores infringing on the 512MB space required for migration to the format supported by the new firmware.
• unsupported RAID controller module type.
• current unsupported firmware version. To avoid this issue make sure that the MD3000/MD3000i has 06.70.xx.xx firmware installed before attempting the
• storage partition(s) database corruption.
• data validation error.
In some cases, the array may be non-optimal but an upgrade will still be possible. It is recommended, but not required, to resolve the non-optimal condition befo

Expires 2/3/2011 12:22:48 PM MD Firmware Update Utility This document is Dell Confidential

Disk Group Changes

The procedure to create a Virtual Disk has been slightly modified. The procedures to create a Disk Group and a Virtual Disk are now separated on the Create Di
The image below illustrates how the Create Disk Groups and Virtual Disks window has split out the tasks of creating a Disk Group and a Virtual disk.
This image illustrates how the Create Disk Groups and Virtual Disks window has split out the tasks of creating a Disk Group and a Virtual
disk.
NOTE:
With this change in the procedure to create a virtual disk, you must create a disk group before you can create the virtual disk.
For more information about the procedure to create a virtual disk within a new disk group please refer to the RAID 6 Support page of this training document. He

Expires 2/3/2011 12:22:48 PM Disk Group Changes This document is Dell Confidential
Disk Metadata and Format Changes

The second generation firmware uses a revised metadata on the disks, with this revised metadata:
• space allocated is increased.

• the disk format is changed.
The MD Firmware Upgrade Utility updates the metadata on the disks to the new format during the upgrade. Once this upgrade is started, the process cannot be r

Expires 2/3/2011 12:22:48 PM Disk Metadata and Format Changes This document is Dell Confidential
Simplex Controller Replacement

With simplex controller configurations and the introduction of the Second Generations there are some considerations that must be made when replacing the RAI
• The Customer owns an older PowerVault MD3000/MD3000i using first generation firmware and if the customer needs to have the RAID controller repla
generation firmware on the replacement controller.
• If the customer owns a newer PowerVault MD3000/MD3000i using second generation firmware are there any considerations that must be made when rep
To address these two considerations and questions you must be aware of a change that is occuring to service stock.
All service stock replacement controllers will be at the second generation firmware level and will need to be downgraded to first generation firmware b
Now we can address these considerations and questions.
Customer Owns Older PowerVault MD3000/MD3000i, and Wants to Retain First Generation Firmw
The procedure to replace a failed controller in an MD3000i running first generation firmware in Simplex mode has changed. There are two methods to do this:
• The customer can download and install the latest 2nd generation version of the MD Storage manager on a management station. Once they connect to the c
they need using the standard firmware download procedure in MD Storage Manager. At this time, the array may appear to be disconnected but it is n
• If customer does not want to install the latest version of the MD Storage Manager, a separate standalone Utility will be available on support.dell.com that
NOTE:
The user will not lose any data or configuration information in the process of the downgrade
Customer Owns Newer Second Generation PowerVault MD3000/MD3000i with Simplex RAID Cont
In the case of a simplex configured second generation system, replace the controller and check the Dell Support site for any firmware updates. If a newer firmwa

Expires 2/3/2011 12:22:48 PM Simplex Controller Replacement This document is Dell Confidential
Duplex Controller Replacement

For an MD3000/MD3000i with a single failed controller in a duplex mode configuration, the following procedure should be used to replace the failed controller
1. Place the failed controller offline using MDSM.

2. Replace failed controller with the PowerVault on. (do not power down the system. If PowerVault is powered down, power it up and wait for POST (sodM
firmware levels and configuration.
NOTE:
Replacement Controllers can be at first (version 06.xx.xx.xx) or second (version 07.xx.xx.xx) generation firmware levels.
3. To verify that Automatic Code Synchronization was successful flashing the new replacement controller to the native controllers firmware levels and confi
1. Use MDSM and fireware version for both controllers in the the storage array profile, If both controllers firmware version is as expected, then Autom
2. If the firmware versions are different or not as expected, the ACS was not completed properly. In this case, The system will need to be upgraded or
the second generation firmware after the firmware update is complete.
Supported Controller Replacement Scenarios

Single First Generation Controller Single Second Generation Controller
First Generation Duplex System HOT swap the failed controller with replacement controller. HOT swap the failed controller with replacement controller
Second Generation Duplex System HOT swap the failed controller with replacement controller. HOT swap the failed controller with replacement controller
NOTE:
The options in the table above are the only supported mechanisms of replacing a failed controller in a dual controller (duplex) PowerVault MD3000/MD30
Dual Controller Failure Scenario

In the event that both controllers fail in a duplex mode configuration on a PowerVault MD3000/MD3000i, please use the following process to address the issue:
1. If both controllers in a system have failed, the customer will have to have an on-site Dell Service Provider perform the replacement.
2. The replacement of both controllers is not officially supported. Therefore, when you encounter this issue with a customer you need to escalate the issue to

Expires 2/3/2011 12:22:48 PM Duplex Controller Replacement This document is Dell Confidential
Serial Shell and Console Procedures

The process to use the serial console has changed.
• Serial Console is now protected by a password. The password is supportDell.

• The Serial Console access is now in the form of a menu. The menu will give access to all required functions for troubleshooting.
• The menu options available are.
1. Display IP Configuration
2. Change IP Configuration
3. Reset Storage Array (SYMbol) Password
4. Quit Menu
• Older serial shell commands are no longer available under 2nd generation firmware.
Accessing the Serial Shell
Accessing
1. Startup a terminal emulation program like putty, teraterm, minicom or hyperterminal using these terminal settings (115200-8-n-1).
NOTE:
Windows Server 2008 does not ship with hypertrm.exe and hypertrm.dll. Customers wanting to use hyperterminal in Server 2008, must copy these tw
2. Send a from the terminal shell. This is accomplished by <Ctrl><PAUSE/BREAK> within HyperTerminal or Putty, use <Ctrl><A><F> from within Min
3. When prompted for input within 5 seconds, press <S> for the service interface menu.
NOTE:
Only capital "S" works here, lowercase "s" will not be recognized for this command.
4. The user will then be prompted for a password. The Password is: supportDell
5. The menu options available are.
• 1) Display IP Configuration
• 2) Change IP Configuration
• 3) Reset Storage Array (SYMbol) Password
• Q) Quit Menu
Serial Shell Menu Option Detail

The following sections of this page will illustrate the each of the main menu options in the serial shell.
Display IP Configuration
Display IP Configuration displays the current IP configuration of the of the ethernet maintenance port for the RAID controller currently attached to the Serial Sh

This image illustrates the result of selecting option 1 of

the serial shell console menu options, Display IP
Configuration, which displays the currrent IP
configuration of the RAID controllers ethernet
management port.
Change IP Configuration
Change IP Configuration will ask the user a series of questions about the IP configuration, the responses will set the IP configuration schema for the maintenanc
This image illustrates the series of questions asked during the serial shell change IP
configuration function.
Reset Storage Array (Symbol) Password

This option allows the user to reset the Storage Array Password.
Using the Serial Shell to Troubleshoot Customer Issues

One of the greatest advantages to using serial shell during troubleshooting, is the ability to see each RAID controller on a PowerVault MD3000/MD3000i comp
servers and desktops knowing when devices are initialized during POST can help to determine a point of failure during troubleshooting. The link below contain
NOTE: sodMain complete.
MD3000i Captured P.O.S.T. Sequence
Other examples of when it would be a good idea to use the serial shell to troubleshoot issues is mainly around significant events that occur with a RAID control
• in a duplex configuration, when one of the controllers is being replaced, you should attach the serial cable to the good controller. In doing this when the re
ACS is the ability for a native duplex controller to flash or synchronize its firmware with a new rplcaement controller.
• when performing a firmware update during normal conditions, it may be helpful to view the serial shell information as the update progresses.
NOTE:
Even though the logs of the updates above can be pulled from the support bundle, the advantage of the serial shell in this case is realtime diagnosis. Finally
that you need.

Where Can I Find More Information on Serial Shell?

Please refer to the following livemeeting presentation on Serial Shell Troubleshooting Best Practices.
Serial Shell Troubleshooting Best Practices

Expires 2/3/2011 12:22:48 PM Serial Shell and Console Procedures This document is Dell Confidential
Chassis 360
Click here to open

Expires 2/3/2011 12:22:48 PM Chassis 360 This document is Dell Confidential
Chassis Teardown
Click here to open

Expires 2/3/2011 12:22:48 PM Chassis Teardown This document is Dell Confidential
RAID Controller Module Overview

The RAID array enclosure is connected to a host via two hot-pluggable RAID controller modules. The RAID controller modules are identified as RAID controll
iSCSI In port connectors which provide either a direct connection to the hosts, or connection by way of Ethernet switches. It is a requirement that the same cont

The iSCSI input connectors (iSCSI In) are adjacent to each other and are labeled 0 and 1. These ports are further identified by the raid controller in which they r
controller module connects to the enclosure midplane via the two midplane connectors on its internal (rear) panel.
The default IP addresses of the Ethernet connectors on the RAID Controllers are as follows:
• Controller 0
◦ Management Port - 192.168.128.101
◦ iSCSI Port 0,0 - 192.168.130.101
◦ iSCSI Port 0,1 - 192.168.131.101
• Controller 1
◦ iSCSI Port 1,0 - 192.168.130.102
◦ iSCSI Port 1,1 - 192.168.131.102
Once the default IP addresses have been set manually, they will remain at the new manually determined settings. If DHCP is used to provide IP addresses to the
The following image shows the back view of the dual port RAID Controller, the connections, and the LEDs.
This is a rear view of the RAID Controller for the MD3000i, showing its connectors and LED indicators, and their
purpose.
This table lists the engineering descriptions for the RAID Controller ports and indicators as shown in the previous image.
RAID Controller
Component
iSCSI In Ports 0 and 1 Provide iSCSI connection from the host to

• Green: Link is operating at 1000 Mbps

iSCSI In Port Link Speed / Activity
• Amber: Link is operating at 100 Mbps
Status LED
• Off: iSCSI connection is not active
• Green: Full-duplex mode

• Off: iSCSI connection is not active
iSCSI In Port Link Duplex Mode
NOTE:
Half-duplex mode is supported only
Battery Fault LED

• Amber: Battery backup unit or battery h
• Off: Battery backup unit and battery are
Cache Active LED

• Green: On-board controller memory con
• Off: On-board controller memory is emp
Controller Fault LED

• Amber: Controller fault detected
• Off: Controller is operating normally
Controller Power LED

• Green: Controller power is on
• Off: Controller is not powered
Ethernet Connector - Management Port Provides Ethernet (out-of-band) connectivi

Ethernet Link LED - Management Port
• Green: Ethernet connection is active
• Off: Ethernet connection is not active
Ethernet Speed LED - Management Port

• Green: Ethernet connection is operating

• Off: Ethernet connection is operating at
Debug Port Dell support only

SAS Out Port Cascade port to MD1000 expansion enclos

• Amber: Between 1 - 3 links (PHYs) are

SAS Link Fault LED • Green: All four links (PHYs) are connec
• Off: All links are down (no connection)
The Cache Battery Backup Module

The fully charged battery backup module will support 72 hours of cache retention if the system suddenly loses power to allow the system to recover the contents
takes place. The battery backup module is easily replaced in the RAID controller after removing the controller from the system chassis.
The following image shows the placement of the battery backup module within the RAID controller module.
This image shows the placement of the battery backup module in the RAID controller
module.
At RTS there is no battery learn/test cycle active on the controller. The battery is maintained with a float charge, which means the battery always appears fully c
up on that error.

Expires 2/3/2011 12:22:48 PM RAID Controller Module Overview This document is Dell Confidential
Enclosure Modes
The MD3000i operates with both controllers having access to their respective physical disk ports on all the physical disks in the enclosure at all times through th
status.

Expires 2/3/2011 12:22:48 PM Enclosure Modes This document is Dell Confidential
Control Panel
The MD3000i control panel provides LEDs to assist with troubleshooting; they are accessible through the front bezel. The control panel contains the Operationa
Operational Mode select switch has no effect.
NOTE:
MD1000s attached to the MD3000i must be set to Unified Mode.
WARNING:
The split mode LED and enclosure mode switch are not functional. However, if additional expansion enclosures are daisy chained to your system, the en
will cause the unit to not detect all drives and cause sporadic issues with dropping disks.
The following image shows the features of the MD3000i Control Panel module.

Image showing the Unified/Split Mode switch and the LEDs on the front of the MD3000i Control Panel module.
MD3000i Control P
LED Type LED Color
Split Mode Green No indication in the MD3000i RAID Enclosure
Power Green When lit, at least one power supply is supplying power
Enclosure status Steady amber The power is on, and the enclosure is in reset state
Steady blue The power is on, and the enclosure status is OK
Flashing blue The host server is identifying the enclosure
Flashing amber The enclosure is in fault state

Expires 2/3/2011 12:22:48 PM Control Panel This document is Dell Confidential
Bezel LEDs
The MD3000i has an optional lockable front bezel. The following image shows the features of the front bezel.
Image showing the features of the optional lockable front bezel
MD3000i Control P
LED Type LED Color
Split Mode Green Unused in the MD3000i RAID enclosure.
Power Green When lit, at least one power supply is supplying power
Enclosure status Steady amber The power is on, and the enclosure is in reset state
Steady blue The power is on, and the enclosure status is OK
Flashing blue The host server is identifying the enclosure
Flashing amber The enclosure is in fault state


Expires 2/3/2011 12:22:48 PM Bezel LEDs This document is Dell Confidential
Physical Disks
The MD3000i enclosure supports up to fifteen 3 Gb/s serial-attached SCSI (SAS) physical disks. Each physical disk is contained in its individual physical disk c
the enclosure. The factory configuration for the MD3000i requires a minimum of two physical disks for proper operation.
Supported Physical Disks

The following physical disks are supported in the MD3000i and its attached enclosures:
• SAS 3.5" 10 K RPM: 73 GB, 146 GB, 300 GB, 400 GB

• SAS 3.5" 15 K RPM: 36 GB, 73 GB, 146 GB, 300 GB
Physical Disk Slot Numbering

The following image shows the sequential numbering used for each disk slot in the MD3000i enclosure.
Image showing the sequential numbering used for each physical disk slot in the MD3000i enclosure.
Physical Disk Status LED

The following image shows the disk status LED.
Image showing the physical disk indicator

LED's.
This table describes the physical disk status indicator patterns.
Physical Disk Status Indicator Patterns

Status LED Description
Off Physical disk not yet discovered by host server or an unsupported disk is present
Steady Green Physical disk is online
Green flashing (250 milliseconds [ms]) Physical disk is being identified
Green flashing Physical disk rebuilding
On 400 ms
Off 100 ms
Amber flashing (125 ms) Physical disk failed
Flashing green, amber, and off Physical disk failure predicted (SMART)
Green 3 seconds, amber 3 seconds, and off 3 seconds Physical disk rebuild aborted
SMART Support
Self-Monitoring Analysis and Reporting Technology (SMART) allows physical disks to report errors and failures. SMART monitors the internal performance o
on a physical disk, you can replace or repair the physical disk without losing data. SMART-compliant physical disks have attributes for which data (values) can
Many mechanical failures and some electrical failures display some degradation in performance before failure. Numerous factors relate to predictable physical d
as seek error rate and excessive bad sectors.
Firmware on the RAID controller module uses SMART logic to evaluate the SAS physical disks in your array to predict or detect disk failure. The status LED o
failure.

RAID Controller Physical Disk States

The following table lists and describes the physical disk states that are recognized by the controller.
Physical Disk States Recognized by t

Status Mode
Optimal Unassigned The physical disk in the indicated slot is unused and available to be configure
Optimal Assigned The physical disk in the indicated slot is configured as part of a disk group.
Optimal Hot Spare Standby The physical disk in the indicated slot is configured as a hot spare.
Optimal Hot Spare In Use The physical disk in the indicated slot is in use as a hot spare within a disk gr
Failed Assigned, Unassigned, Hot Spare In Use, or Hot Spare Standby The physical disk in the indicated slot has been failed because of an unrecove
Replaced Assigned The physical disk in the indicated slot has been replaced and is ready to be, or
Pending Failure Assigned, Unassigned, Hot Spare In Use, or Hot Spare Standby A SMART error has been detected on the physical disk in the indicated slot.
(none) (none)) The indicated slot is empty, or the array cannot detect the physical disk.

Expires 2/3/2011 12:22:48 PM Physical Disks This document is Dell Confidential
Power Supply/Cooling Fan Module LEDs

The MD3000i features dual hot-swap power supply/cooling fan modules. Both modules must be used for proper cooling (3+1 fan redundancy). Although a sing
replacement is available. The fans in the defective supply will continue to run, powered by the other power supply through the common fan voltage bus.
The following image shows the power supply/cooling fan module LEDs.
Image showing the Power Supply/Cooling

Module LEDs.
Power Supply/Cooling F
LED Type LED Color
DC power Green
• On: DC output voltages are with
• Off: No power or voltages not w
Power supply/cooling fan module fault Amber

• On: DC output voltages are not w
• Off: No fault condition is presen
AC power Green
• On: AC input voltage is within s
• Off: No power or voltages not w
The following image shows the power supply/cooling fan modules installed in the MD3000i enclosure.
Image showing the hot-swap power/cooling modules installed in the MD3000i enclosure.

Power Supply/Cooling Fan Module

LEDs
Racking
This procedure outlines the steps for racking the MD3000i.
Racking
1.
Align the rail assembly to the appropriate mounting position in the rack.
Align the rail assembly to the desired mounting position in the rack.
2.
Line up the slide assembly mounting hooks with the square holes on the vertical rail.
Line up the slide assembly mounting hooks with the square hole on the vertical rail.
3.
Push down on the rail until the locking buttons pop out and click.
Push down on the rail until the locking button pops out and clicks.

Racking
4.
Repeat the procedure for the back side of the rail assembly.
Repeat the procedure for the back side of the rail assembly.
5.
Install the second rail assembly.
Install the second rail assembly.
6.
Place the back of the MD3000i on the rails, and slide the enclosure back until it locks into the rails.
Place the back of the MD3000i on the rails and slide the enclosure back until it locks into the
rails.
7.
Slide the enclosure all the way into the rack.

Racking
Slide the enclosure the rest of the way into the rack.
8.
Tighten the two thumbscrews to secure the MD3000i to the rack.
Tighten the two thumbscrew to secure the MD3000i to the rack.
9.
Place the front bezel on the MD3000i.
Place the front bezel on the MD3000i.

Expires 2/3/2011 12:22:48 PM Racking This document is Dell Confidential

Host to MD3000i Enclosure Cabling

Gigabit Ethernet to MD3000i Cabling
NOTE:
Always refer to the latest Dell PowerVault MD3000i documentation found on the Dell support site for the most up to date information concerning suppo
An Ethernet cable connects either directly to one of the iSCSI In connectors of one of the RAID Controllers or is connected through an Ethernet switch. Additio
allows enclosures to be cascaded. The following images and descriptions demonstrate supported cabling methods for various configurations of both redundant a
NOTE:
Cabling methods are not critical for specific RAID Controller Module iSCSI Ethernet inputs; i.e., a host may be connected to either of the iSCSI Etherne
However, if the host will only be connecting to a single controller, the preferred path for the volumes assigned to the host must be the same controller wi
Best Practice
As a best practice, the user should isolate the iSCSI network from the public LAN. If that is not possible, then increased security should be used, such as CHAP
Supported Cabling Configurations - Direct Attached

The following direct attached cabling configurations are supported with the MD3000i.
One Direct Attached Server - With One Gigabit Ethernet (GbE) Data Path to a Simplex Controller
The following image shows a single server with one GbE card cabled to one controller on a simplex MD3000i in a single path configuration. Loss of the single
This is an image showing one server connected to the MD3000i with a single,
non-redundant data path, and a management path.
Two Direct Attached Servers - Each With One GbE Data Path to a Simplex Controller
The following image shows two servers, each with one GbE card, cabled to one simplex controller. There are no secondary data inputs to the controllers from ei
clustering.

This image shows two servers, each with one GbE data path each, connected
to a simplex controller, with no redundant access to virtual disks.
Four Direct Attached Servers - Each with One GbE Data Path to Duplex Controllers
The following image shows four servers, each with one HBA, attached to the four inputs available on the two dual port controllers. In this instance, no server ha
This image shows four servers, each with one HBA, attached to the four inputs available when using the
dual port controllers. There is no redundancy of pathways for any server.
Two Direct Attached Servers With Redundant Pathways to Duplex Controllers

The following image shows two servers, each with a redundant connection to the duplex controller array.
This image shows two direct attached servers with redundant connections to a
duplex controller array.
Supported Cabling Configurations - Network Attached

Host servers can also be attached to the MD3000i through an IP storage area network (SAN) industry-standard 1GB Ethernet switch. By using an IP SAN "clou
the host to have a redundant connection to the network. However, if both connections are going to the same network, then only the individual connection will ha
The following network attached cabling configurations are supported with the MD3000i.

Up to 16 SAN-configured Hosts - Single Path Data - Simplex Controller

Each host can have single or dual data path connections to the 1Gb Ethernet switch, with each connection operating on a different logical subnetwork. In a singl
switch and the simplex controller, but no redundancy for the host GbE connection, the host GbE cable, or the GbE switch. This configuration is not supported fo
This image shows one to 16 hosts with non-redundant gigabit ethernet connections to a switch, which has
redundant connections to a simplex controller array.
Up to 16 SAN-configured Hosts - Dual Path Data - Simplex Controller

The scenario below shows a configuration with as many as 16 hosts, each with dual data paths, to a single switch. Each of the two host data paths is on a separat
The is an image of a configuration with as many as sixteen hosts, each with dual data paths on separate
subnets, to a simplex controller array.
Up to 16 SAN-configured Blade Hosts - Dual Path Data - Simplex Controller

The scenario below shows a configuration with as many as 16 blade-based hosts, each with dual data paths, to dual switches. Each of the two host data paths is o
clustering.
This is an image of a configuration with as many as sixteen blade hosts on dual switches, with each host
having dual data ports on separate subnets. This configuration is supported for clustering.

Up to 16 Dual SAN-configured Hosts - Dual Path Data - Duplex Controllers

Each host has a separate connection to redundant GbE switches, and to duplex controllers. In a switched-attached configuration, clusters and stand-alone servers
controllers.
This is an image showing up to sixteen hosts connected to duplex controllers through redundant gigabit
ethernet networks.

Expires 2/3/2011 12:22:48 PM Host to MD3000i Enclosure Cabling This document is Dell Confidential
MD3000i to MD1000 Enclosure Expansion Cabling

Up to two MD1000 expansion enclosures can be added to the MD3000i enclosure, for a total of 45 physical disks, provided that the MD1000 EMM BIOS and p
MD1000 expansion enclosures, must be powered down for expansion cabling.
WARNING:
This is a data-destructive operation for any data on the MD1000s that was created with a PERC5/E. The metadata format (DACstore) of configured physic
MD1000 enclosure from a PERC5/E to an MD3000i. The data must be backed up, confirmed, and restored to newly formed disk groups and virtual disks o
must be cleared before attaching to the MD3000i. This can be done by clearing the configuration, or deleting all logical drives and hot spares.
Required Conditions for Cascading

• Physical Disks in the MD1000(s) must be cleared of any configuration if previously attached to anything other than an MD3000 or MD3000i.
• EMM firmware on the MD1000 expansion enclosures must be version A03 or later. If the firmware is not A03 or later, the firmware must be updated.
• Cabling methodology described and pictured below.
Flashing the MD1000 Firmware

The following three methods are available for updating the MD1000 EMM firmware for use with the MD3000i. They are listed here in their order of desirability
1. If the MD1000 expansion enclosures are being migrated from use with a PERC5/E RAID Controller, the preferred method of update is to flash the EMMs
updated.
2. If a PERC5/E is not available for the update process, then the next most desirable course of action is to perform a field replacement of the EMMs.
3. If neither of the first two options are available, the firmware may be flashed using MDSM to download the firmware to the MD1000 EMMs.
1. Power down the MD3000i and cable only one MD1000 to the output of the MD3000i.
2. Each EMM will be individually flashed. Only insert one EMM at a time into the added MD1000 enclosure.
3. Add the MD1000 to the MD3000i, cabling from the output of the MD3000i to the one installed EMM on the MD1000. Power up the MD1000 encl
4. Power up the MD3000i and wait until the blue LED is lit indicating the enclosure is fully initialized.
5. In MDSM choose Download Firmware on the Support tab. Click Download Environmental (EMM) Card Firmware and choose the attached M
6. After the flash has completed, power down the MD3000i, followed by the MD1000.
7. Repeat this process until each EMM has been individually flashed.
8. After all EMMs have been flashed, power down all enclosures and cable the MD3000i and MD1000(s) as shown in the graphic below.
9. Power up the MD1000 expansion enclosures first and wait until the units are fully initialized.
10. Power up the MD3000i and, when the unit is fully initialized, use MDSM to manage the new enclosures and physical disks.
WARNING:
Do not make any configuration changes to the storage array while you are downloading the EMM firmware. Doing so could cause the firmware dow
Enclosure Power-Up Sequence

The following procedure should be followed for the power-up sequence of an MD3000i with attached MD1000 expansion enclosures.
1. Turn on the MD1000 expansion enclosure(s). Wait for the expansion status LED to light blue on each enclosure.
2. Turn on the MD3000i and wait for the status LED to indicate that the unit is ready:
◦ If the status LEDs light a solid amber, the MD3000i is still coming online.
◦ If the status LEDs are blinking amber, there is an error that can be viewed using MDSM.
◦ If the status LEDs light a solid blue, the MD3000i is ready.
3. After the MD3000i is online and ready, turn on any attached host systems.

The power-down sequence should done in the reverse order, with emphasis on a clean shutdown of the hosts and at least a ten second interval thereafter to insur
Cabling Method for Cascading the MD3000i to MD1000 Expansion Enclosures

The following images show the manner in which MD1000 expansion enclosures can be cascaded from an MD3000i enclosure.
Cabling Method for Cascading the Simplex MD3000i to MD1000 Expansion Enclosures
This is an image showing the maximum cascading configuration available with the MD3000i in simplex configuration.
This is an image showing the maximum cascading configuration available with the MD3000i in
simplex configuration.
Cabling Method for Cascading the Duplex MD3000i to MD1000 Expansion Enclosures
This is an image showing the maximum cascading configuration available with the MD3000i in duplex configuration.
This is an image showing the maximum cascading configuration available with the MD3000i in
duplex configuration.
Possible Issues Related to Cascading an MD3000i to an MD1000 with Unsupported EMMs

• The flash sequence for updating the MD3000i RAID Controllers to 1.1 will take considerably longer than normal to complete. The controllers will reboot
the flash process.
• If EMMs with less than A03 firmware are used in a cascaded configuration, the physical disks will not appear in the physical disk list.
• Flashing the firmware from less than A03 to A03 through MDSM is a much more lengthy process than usually seen in an EMM flash. The entire flash ma
flashed. The Start button is disabled until you select a firmware file. If you click Stop while a firmware download is in progress, the download completes
it did succeed, the upgraded enclosure will appear twice in the flash dialogue at both firmware levels. A cold reboot of the MD3000i is required to clear an
• If EMMs with less than firmware A03 are used in a cascade, the physical disks will not be seen in MDSM.

MD3000i to MD1000 Enclosure
Expansion Cabling

Support Matrix
THe link below contains the PowerVault MD3XXX Support Matrix, including information on supported software and hardware.
PowerVault MD3XXX Support Matrix

Expires 2/3/2011 12:22:48 PM Support Matrix This document is Dell Confidential
RAID Controller Module

The MD3000i RAID Enclosure may contain either one (simplex) or two (duplex) RAID Controller modules. Both modules are physically removed in the same
NOTE:
For single (simplex) RAID controller module replacements, refer to the Single Controller Replacement (DSP and CRU) procedure in the SATA Supp
This includes vital information on firmware upgrade requirements before starting a single RAID controller module replacement.
Removing the
1.
Gently lift up the orange handle spring lock on the controller to release the locking lever.
This image shows the action of lifting up the orange handled spring lock to release the locking
lever.
2.
Rotate the cam lever lock away from the unit.
This image shows the direction of rotation of the locking lever that releases the RAID Controller
module.
3.
Using the lever lock, pull the RAID Controller module out of the chassis.

Removing the
This image shows the RAID Controller Module being pulled from the bay.
4.
Reverse the previous steps to replace the RAID Controller module.
This procedure outlines the steps for removing and replacing the RAID Controller module battery assembly.
Removing the
1.
Using a Phillips screwdriver, remove the back screw retaining the steel cover over the battery compartment.
This image shows the removal of the rear retaining screw from the battery compartment.
2.
Remove the side screw retaining the steel cover over the battery compartment.
This image shows the removal of the side retaining screw from the battery compartment.
3.
Lift the battery cover up and away from the controller.

Removing the
This is an image showing the battery cover being removed.
4.
Loosen the blue captive screw.
This is an image showing the captive screw being loosened.
5.
Slide the battery assembly out and away from the controller.
This is an image showing the battery assembly being removed.
6.
Reverse the previous steps to replace the battery assembly.

Expires 2/3/2011 12:22:48 PM RAID Controller Module This document is Dell Confidential

Bezel
This procedure outlines the steps for removing and replacing the bezel.
1.
Push inward on the release tab on the left side of the bezel.
2.
Pull the bezel away from the enclosure front.
Lift the bezel away from the enclosure front.
3. Reverse the previous steps to replace the bezel.
This procedure outlines the steps for removing and replacing the bezel.
1.

2.
Pull the bezel away from the enclosure front.
Lift the bezel away from the enclosure front.
3. Reverse the previous steps to replace the bezel.

Expires 2/3/2011 12:22:48 PM Bezel This document is Dell Confidential
Physical Disks
This procedure outlines the steps for removing and replacing the physical disks.
WARNING:
If a physical disk is accidentally removed while it is online/active, wait at least 30 seconds before reinserting the disk. Failure to wait at least 30 seconds m
failed, and there is no I/O to the array, it must be failed using SMcli at the command line before removal.
Phys
1.
Before removing the physical disks, remove the front bezel.
2.
Squeeze the release mechanism on the front of the physical disk carrier, and rotate it downward to open the carrier handle.

Phys
Squeeze the release mechanism on the front of the physical disk carrier, and rotate it
downward to open the carrier handle.
3.
Carefully pull the physical disk carrier from its slot.
Carefully pull the physical disk carrier from its slot.
4.
Repeat steps 2 and 3 to remove the remaining physical disks.
Remove the remaining physical disks.
5. Reverse the previous steps to replace the physical disks.

Expires 2/3/2011 12:22:48 PM Physical Disks This document is Dell Confidential
Physical Disk Blanks

This procedure outlines the steps for removing and replacing the physical disk blanks.

Physical Disk Blanks

1.
Before removing the physical disk blanks, remove the front bezel.
2.
Push the tab on the bottom of the physical disk blank, and then pull the blank from the slot.
Push the tab on the bottom of the physical disk blank, and pull the blank from its slot.
3.
Remove the remaining physical disk blanks.
Remove the remaining physical disk blanks.
4. Reverse the previous steps to replace the physical disk blanks.

Expires 2/3/2011 12:22:48 PM Physical Disk Blanks This document is Dell Confidential
Control Panel
This procedure outlines the steps for removing and replacing the control panel.
Control Panel
1.
Before removing the control panel:
• Remove the front bezel.

• Remove all physical disks and physical disk blanks.
2.
Using a Torx T10 driver, remove all 16 screws from the front faceplate of the system.

Control Panel
Using a Torx T10 driver, remove all 16 screws from the front faceplate of the system.
3.
Remove the front faceplate from the system.
Remove the front faceplate from the system.
4.
Slide the control panel assembly straight out from its connector on the backplane.
Slide the control panel assembly straight out from its connector on the backplane.
5. Reverse the previous steps to replace the control panel.

Expires 2/3/2011 12:22:48 PM Control Panel This document is Dell Confidential
Enclosure Midplane
This procedure outlines the steps for removing and replacing the enclosure midplane.

Enclosure Midplane
1.
Before removing the enclosure midplane:
• Remove the front bezel.

• Remove all physical disks and physical disk blanks.
• Remove the control panel.
• Remove both RAID Controllers.
• Remove the primary and secondary power supply/cooling fan modules.
2.
Remove the four Phillips head screws securing the EMM/power supply cage.
Remove the four Phillips head screws holding the EMM/power supply cage in the enclosure.
3.
Slide the EMM/power supply cage out of the enclosure.
Slide the EMM/power supply cage out of the enclosure, and place it aside.
4.
From the back of the enclosure chassis, carefully remove the midplane from the enclosure.
Reach into the enclosure chassis from the back, carefully disconnect the enclosure midplane
from the control panel, and pull it out of the enclosure.

Enclosure Midplane
5. Reverse the previous steps to replace the enclosure midplane.

Expires 2/3/2011 12:22:48 PM Enclosure Midplane This document is Dell Confidential
Power Supply/Cooling Fan Modules

This procedure outlines the steps for removing and replacing the power supply/cooling fan modules.

1.
Using a Phillips head screwdriver, loosen the two captive screws securing the power supply/cooling fan module in the bay.
With a Phillips head screwdriver, loosen the two captive screws securing the power
supply/cooling fan module in the bay.
2.
Grasp the handle on the power supply/cooling fan module, and pull the module away from the bay.
The image shows the module being removed from the bay.
3.
Repeat the previous steps to remove the second power supply/cooling fan module.


This image shows the beginning of removing the other power supply.
4. Reverse the previous steps to replace the power supply/cooling fan modules.

Expires 2/3/2011 12:22:48 PM Power Supply/Cooling Fan Modules This document is Dell Confidential
System Architecture
The MD3000i RAID Enclosure is leveraged from the MD1000 chassis, using all the MD1000 components except for the EMMs, which are replaced by the iSCSI RAID
Controllers.
This is a block diagram of the MD3000i:
This is an image of the block diagram of the MD3000i.
The MD3000i RAID controller is capable of free-standing operation and will continue to operate in the event that the partner controller goes offline or is removed. Note in
the MD3000i Block Diagram above that each RAID controller module has an alternate SAS pathway from its SAS I/O Controller to the opposite controller's SAS expander.
In the event that a path to the peer controller has failed, the remaining controller will process the I/O to the physical disks owned by the peer over the same SAS connection
formerly used by the peer controller.
RAID Controller Failover Modes

Failover provides redundant access to the virtual disks owned by either RAID controller module on the storage array. Failover happens automatically (and transparently).
As a result, the host(s) never loses access through the preferred controller which owns the virtual disk.
Two failover modes are supported:
• Host-based Multi-Path I/O (MPIO) for Windows or MPP for Linux

• Controller-based Auto Virtual Disk Transfer (AVT)
NOTE:
Clustering requires simultaneous access from cluster nodes to shared storage. If you have clustering software installed on the host, automatic failback should be
disabled to prevent "ping-pong" with single-path failure.
NOTE:
If setting up a cluster host, the MD3000i Stand Alone to Cluster.reg file entry must be merged into the registry of each node. If re-configuring a cluster node to a

standalone host, the MD3000i Cluster to Stand Alone.reg file must be merged into the host registry. These registry files, which set up the host for correct failback
operation, are in the windows\utility directory of the MD3000i Resource CD.
Host-based uses a multi-path driver installed on the host server to access the storage array. If required, the multi-path driver will issue an explicit command to transfer
ownership from the RAID controller module that owns the virtual disk to its peer RAID controller module.
AVT is used only in single-port cluster solutions. I/O access to the Logical Unit Number (LUN) of a virtual disk causes failover. In AVT mode, firmware transfers
ownership of a virtual disk to the online RAID controller module. The alternate or backup node in a cluster takes over and issues I/O to the peer controller and moves the
virtual disk to itself.
Host Failover Software

Multi-path software installed on the host manages the I/O paths into the RAID controller modules in the storage array. If there is a problem on the data path to the preferred
RAID controller module, the multi-path software automatically re-routes the request from the hosts to the alternate, non-preferred RAID controller module in the storage
array. The host multi-path software instructs the alternate RAID controller module to assume ownership of all the virtual disks of the disabled controller and flushes its dirty
write cache (if any data remains), using the alternate RAID controller module. This occurs without the host detecting a problem.
To do this, the failover driver (an application or kernel-resident driver) positions itself between the SCSI driver and the rest of the operating system. This lets it monitor all
I/O traffic so it can quickly reroute it to the redundant path in the event of controller or path failure.
Access Virtual Disk

The storage management station must be able to locate and access your storage array using a logical unit number (LUN). It uses a special access virtual disk for this
purpose. The access virtual disk is the virtual disk in a network environment used for communication between the storage management software and the RAID controller
modules in a storage array. This virtual disk does not have any physical disks assigned to it. The access virtual disk uses a LUN address and appears to the storage
management station as either 16 or 20 MB of storage space (depending on the RAID level assigned on its associated disk group) unavailable for application data storage.
An access virtual disk uses a default LUN address of 31. For strict identification purposes, the access virtual disk also has a World Wide ID (WWID), which is a 64-bit
unique name based on Dell's IEEE identifier, and a 32-bit vendor-unique serial number. An access virtual disk must be registered with the host operating system using this
WWID.
WARNING:
Do not remove or modify the Access Virtual Disk. If the Access Virtual Disk is altered, the storage management station will lose management access to the storage
array until the Access Virtual Disk has been restored at the command line.

Expires 2/3/2011 12:22:48 PM System Architecture This document is Dell Confidential
MDSM Compared to CLI

The following tables show the overall functionality of the Modular Disk Storage Manager GUI and compare it to the command line interface (CLI). Many of the more
advanced, less used functions are only available within the CLI. The tables include:
• Storage Array Functions

• Mapping Functions
• Disk Group Functions
• Standard Virtual Disk Functions
• Snapshot Virtual Disk Functions
• Virtual Disk Copy Functions
• Controller Functions
• Physcial Disk Functions
• Other Functions
Storage Array Functions

Function GUI CLI
Manually add storage array Yes Yes
Automatic discovery of storage arrays Yes Yes
Remove storage array Yes Yes
Configure mail server and sender address Yes Yes
Configure email addresses Yes Yes
Configure SNMP traps Yes Yes
Rename storage array Yes Yes
Locate storage array Yes Yes
Save storage array configuration No Yes
Load storage array configuration No Yes
View profile of storage array Yes Yes
View Storage Array component information Yes - only via profile Yes
Automatic volume/hotspare creation Yes - fixed configurations Yes
View/enable premium feature Yes Yes - view via profile
Disable premium feature No Yes
Launch recovery guru Yes Yes - shows summary

Change RAID level No Yes

Manually add storage array Yes Yes
Set password Yes Yes
Change storage array media scan settings No Yes
Change failover alert delay No Yes
Place disk group online/offline No Yes
Synchronize controller clocks Yes Yes
Reset storage array configuration No Yes
Obtain software information (about) Yes N/A
Obtain overall help Yes N/A
Mapping Functions
Function GUI CLI
Configure host access (for hosts discovered via host context agent) Yes Yes
Manually define host group/host Yes Yes
Add a host port to an existing host Yes (see note below) Yes
Assign a host to virtual disk mapping Yes Yes
Remove/change a host to virtual disk mapping Yes Yes
Change individual host type Yes Yes
Remove host group, host, or host port Yes Yes
Rename host group or host Yes Yes
NOTE:
Add a host port to an existing host:
When applicable, a partition will be created as part of the mapping screen of the individual virtual disk creation wizard or if a user maps a virtual disk to a host in the
"assign a host-virtual disk" mapping interface. A storage partition is used when the first virtual disk is mapped to a particular host.
Disk Group Functions

Function GUI CLI
Locate disk group Yes Yes
Change disk group controller ownership Yes Yes
Change RAID level No Yes
Add free capacity/physical disks (DCE -dynamic capacity expansion) Yes Yes
Delete disk group Yes Yes
Place disk group online/offline No Yes
Check redundancy (recovery) No Yes
Revive disk group (recovery) No Yes
Defragment disk group No Yes
Standard Virtual Disk Functions

Function GUI CLI
Create an individual virtual disk using automatic physical disk choices Yes Yes
Create an individual virtual disk using specific physical disks manually selected Yes Yes
Change parameters (modification priority, cache, media scan, controller ownership, segment size) Only controller ownership Yes
Increase capacity (DVE - dynamic virtual disk expansion) No Yes
Delete virtual disk Yes Yes
Rename virtual disk Yes Yes
Yes - only
Display virtual disk properties Yes
via profile
Re-initialize virtual disk (recovery) No Yes
Recover virtual disk (recovery) No Yes
Snapshot Virtual Disk Functions

Function GUI CLI
Create a snapshot virtual disk Yes Yes
Disable a snapshot virtual disk Yes Yes
Re-create a snapshot virtual disk Yes Yes
Delete a snapshot virtual disk Yes Yes
Rename a snapshot virtual disk Yes Yes

Display snapshot virtual disk and snapshot repository properties Yes - only via profile Yes
Virtual Disk Copy Functions

Function GUI CLI
Create a virtual disk copy pair Yes Yes
Remove a virtual disk copy job Yes Yes
Re-copy a virtual disk copy pair Yes Yes
Stop a virtual disk copy operation Yes Yes
Change virtual disk copy read/write permissions Yes Yes
Change virtual disk copy priority Yes Yes
Controller Functions
Function GUI CLI
Locate Storage Array Yes Yes
Change controller network configuration Yes Yes
Display controller properties Yes - only via profile Yes
Download controller firmware (no staged feature) Yes Yes
Download controller firmware (staged feature) No Yes
Download controller NVSRAM Yes Yes
Activate controller firmware (for "pending/staged" configuration) No Yes
Run controller diagnostics Yes - only via support bundle Yes
Reset controller No Yes
Place controller online/offline Yes Yes
Place controller in service mode No Yes
Physical Disk Functions

Function GUI CLI
Locate physical disk Yes Yes
Locate physical disk tray Yes Yes
Automatically assign/unassign hot spares Yes Yes
Manually assign/unassign hot spares Yes Yes
Display physical disk properties Yes - only via profile Yes
Download physical disk firmware Yes Yes
Collect physical disk data Yes- only via support bundle Yes
Diagnose physical disk channels Yes - only via profile Yes
Re-initialize physical disk (recovery) No Yes
Fail physical disk (recovery) No Yes
Revive physical disk (recovery) No Yes
Reconstruct physical disk (recovery) No Yes
Other Functions
Function GUI CLI
Redistribute virtual disks back to original controller owners Yes Yes
Collect all support data (support bundle) Yes Yes
Download EMM Firmware Yes Yes
View persistent reservations Yes - only via support bundle Yes
Capture state information Yes - only via support bundle Yes
View unreadable sectors Yes - only via support bundle Yes
SAS-related diagnostics and platform support Yes - only via support bundle Yes
View event log Yes Yes

Expires 2/3/2011 12:22:48 PM MDSM Compared to CLI This document is Dell Confidential

MDSM Installation
Complete the following steps to install Modular Disk Storage Management (MDSM) on a host running a supported Windows operating system.
Installation of MDSM
1.
You must have administrative privileges to install MDSM on a Windows host.
• Insert the MD3000i Resource CD and navigate to the main menu.

• From the main menu, select install MD3000i Storage Software
Alternatively, locate and run the MDSM setup.exe program.
2. The setup program will check for the existence of the Microsoft iSCSI Initiator and the correct Storport hot-fix revision.
NOTE:
A minimum version of the Storport driver must be installed on the host server before installing the MD Storage Manager software. A hotfix with the
minimum supported version of the Storport driver is located in the \windows\Windows_2003_Server\hotfixes directory on the MD3000i Resource CD.
The MD Storage Manager installation will test for the minimum Storport version and will require you to install it before proceeding.
This is an image showing the installation installation screen advising the user to install the
store port hot fix if the server is to be used as an array host.
3.
The Micrososft iSCSI Initiator software should also be installed on a host before MDSM is installed. If the iSCSI initiator is not installed, at the end of the
installation the user will see a warning screen advising them to uninstall MDSM, install the iSCSI Initiator software, and then reinstall the MDSM host software.
This is an image of the warning popup window seen at the reboot phase of the installation if the user has
chosen to install the host software without the store port hot fix installed.
4.
When all the prerequisites are met, the user will be able to proceed normally with the software installation.
This is an image of the installation proceeding after all prerequisites have been met.
5.
The user will receive a popup window that requests that changes be made to the registry before proceeding. Clck OK.

This is an image of the popup window requesting the user to acknowledge with okay to install registry
changes for failover to work correctly.
6.
At the opening screen of installation choose the language from the list box and press Ok.
This image shows that at the opening screen of installation the user is
leaving the default selection of English and is clicking okay.
7.
At the Introduction screen click Next.
This image shows that at the Introduction screen the user should click
Next.
8.
In the License Agreement screen choose to accept the license agreement and click Next.
This image shows that at the license screen accept the license agreement
and click Next.
9.
Leave the default path for installation of the software and click Next.
This image shows the user leaving the default installation path selected
and clicking next.

10.
Select Typical (Full Installation) and then click Next.
This image shows the screen where the user should select Typical
Installation.
11.
Select the Automatically Start Monitor radio button if you require the the event monitor to be running on this host.
Otherwise, select the Do Not Automatically Start Monitorradio button.
NOTE:
You should configure only one system to automatically restart the event monitor. Running the event monitor on mulitple systems can cause multiple alert
notifications to be sent for the same error condition. Enabling event monitoring on only one system avoids this issue.
Click Next to continue.
This image shows the screen where the user selects automatically start
monitor.
12.
Click Install.
This image shows the screen where the user will click install.
13.
The user will see the following two screens during installation.
NOTE:
Note the lines in the second screen which show the installation and loading of the MPIO driver. This is done in every installation of the MDSM on a Windows
server. It is loaded regardless of whether the system has redundant pathways, and is not optional.

This is an image of a screen displayed during the installation.
This is an image of a screen displayed during the installation.
14.
Click Done to restart the system.
This image shows a HyperTerminal connection being named.
Discover and Install Your MD3000i Strorage Array

The default IP addresses of the management Ethernet connectors on the RAID Controllers are as follows:
• Controller 0
◦ iSCSI Port 0 - 192.168.130.101
◦ iSCSI Port 1 - 192.168.131.101
• Controller 1
◦ iSCSI Port 0 - 192.168.130.102
◦ iSCSI Port 1 - 192.168.131.102
NOTE:
By default, the MD3000i controller management ports will request a DHCP-assigned IP address. If these dynamically assigned addresses are not in the same
subnet as the management host, the automatic discovery process will not find the array. The discovery of arrays is only on the host's subnet through port 2463.
If a DHCP response is not acknowledged, the controller management ports will default to addresses shown above.
If the controller management ports have had IP addresses manually set, the units will no longer request DHCP addresses and will continue to operate at the
manually set addresses.
If you are trying to discover and manage an MD3000i array with unknown manually assigned IP addresses, follow the procedure towards the end of this page.
Discovery and Installation of MD3000i

1.
Launch the MDSM GUI. A window will immediately appear asking the user to choose between Automatic discovery or Manual. If the array is on the same subnet
as the host, you may select the option button for Automatic and click OK.
If the array management IP addresses have already been determined, you may select manual and insert the two controller IP addresses.


This is an image of the discovery option screen.
2.
The discovery screen will show a progress bar while performing discovery of out-of-band storage arrays. In-band storage management is not available until an iSCSI
session is set up and operating.
This is an image of the screen during the discovery process.
3.
At the end of the discovery process the user will need to close the discovery window. Click Close to close the window.
This is an image of the discovery window at the end of the discovery

process. Click close to close the window.
4.
When the MDSM interface is focused on an MD3000i, it will add a new management tab in the window, labelled "iSCSI."


This is an image of the GUI after the discovery of the I SCSI array, showing the additional management
tab.
5.
The newly discovered array can now be named for quicker and easier identification.
Click OK to continue
This is an image of the array being renamed.
Discovering Unknown Management Port IP Addresses

The automatic discovery process may fail if your MD3000i array has unknown manually configured management port IP address. Automatic discovery will work only if
the management port IP addresses are on the same subnet as the management host.
To discover the MD3000i management port IP addresses, follow these steps:
Management Port IP Address Discovery

1. Connect the MD3000i serial cable between the serial port of your host PC and the management serial port of controller 0 of your MD3000i array.
2.
Open Windows HyperTerminal and enter a connection name.
Then click OK.
This is an image of the array being renamed.
3.
Select the host com port to which the serial cable is attached.
Then click OK.


This image shows the com port selection in
HyperTerminal.
4.
Configure the port settings for the HyperTerminal session, as follows:
• Bits per second: 115200

• Data bits: 8
• Parity: None
• Stop bits: 1
• Flow control: None
This image shows the HyperTerminal settings.
5.
In the HyperTerminal session, press Control-B.You will then see the following screen.
This image shows the Boot Operations menu.
6.
Press Q and then Enter
at the screen prompt, type netCfgShow and then Enter


This image shows the
7.
The management port settings for this controller will be shown. These include the IP Address settings for the port.
Now connect the serial port to the management port on the other MD3000i controller.
Repeat these steps to discover the IP Address settings for the remaining controller.
This image shows the MD3000i controller management port settings.

Expires 2/3/2011 12:22:48 PM MDSM Installation This document is Dell Confidential
iSCSI Host Configuration using IPV4

Installation of the Microsoft iSCSI Initiator
NOTE:
Installation of the Microsoft iSCSI software initiator is integrated into Windows Server 2008. There is therefore no need to install a separate iSCSI software
initiator when using Windows Server 2008 iSCSI attached hosts.
These installation steps apply to Windows 2003 iSCSI hosts only.
Complete the following steps to install the Microsoft iSCSI Initiator software.
Installation of the iSCSI Initiator

1.
Obtain the latest version of the Microsoft iSCSI Initiator software from the Dell Support site. This should be version 2.06 or later. Start the installation with the
executable, which launches the wizard.


This is an image of the first screen of the initiator.
2.
The option boxes for the Initiator Service and the Software Initiator should already be checked. Both of these are needed.
WARNING:
The option box for Microsoft MPIO Multipathing Support for iSCSI must not be checked. MPIO will be installed with the MDSM software. The Device
Specific Module (DSM) has a specific interface needed for proper path failover of the MD3000i by MPIO. Installation of MPIO from this step will cause the
failure of the path failover software.
This is an image showing the proper selection of option boxes for the installation.
3.
Click the radio button for I Agree to accept the software licensing agreement. Click Next.
This is an image of the user accepting the licensing agreement.
4.
The installation of the initiator proceeds without user intervention.


This is an image of the installation proceeding.
5.
Click Finish.
This is an image of the last screen of the installation where the user will click finish.
Configuration of IPv4 iSCSI Host Connectivity

The following procedure shows the steps necessary to to configure IPv4 iSCSI host connectivity.

1.
Before you begin configuring iSCSI, you should fill out the iSCSI Configuration Worksheet, a sample piece of which is shown below.
This image shows a part of the I SCSI configuration worksheet, to be filled out before you begin.
2.
Set the iSCSI port IP addresses on the array.
From the iSCSI tab, click on Configure iSCSI Host Ports.
In this example, the server is directly connected to the array, so the iSCSI ports are being left at the default addresses.
iSCSI port 0 on Controller 0 defaults to 192.168.130.101. iSCSI port 0 on Controller 1 defaults to 192.168.130.102.


NOTE:
DHCP is supported on these ports, but fixed addresses are recommended.
This is an image showing the I SCSI host port IP addresses.
3.
The advanced settings are available for each port. Ethernet priority is based on IEEE standard 802.1p. The TCP listening port for iSCSI defaults to 3260. The default
listening port for an iSNS server is 3205. The Jumbo frames setting can be set for oversized Ethernet frames, up to 9000 bytes/frame (default is 1500). Ensure that
every component in the chain will properly support the size of jumbo frame chosen.
NOTE:
When jumbo frames are enabled, and the ICMP response is also enabled, the array can be pinged and appear reachable, while intervening incompatible
network equipment may drop the jumbo data frames.
This is an image of the advanced screen.
4.
Enable ICMP Ping response for setup purposes. It can be turned off afterwards, if preferred. Changing the status of this option box will reset all the iSCSI ports on
the array. If data transfer is in progress, it will be interrupted until an iSCSI session has been restored.


This is an image of the icmp option box being selected for setup purposes.
5.
Open a command line session and use the Ping command to check connectivity between the host and iSCSI ports configured on the storage array.
This is an image of the ping command being used to test connection between the host and the
array's I SCSI ports.
6.
On the Programs menu launch Microsoft iSCSI Initiator. Click the Discovery tab. Under Target Portals click Add.
This is an image of the user selecting the target portals tab and
clicking add.
7.
Enter the IP address or DNS name of the iSCSI port on the storage array. If the port number was changed from the default of 3260 in a previous step, set the new
port number here. Click Advanced to continue.
This is an image of the user entering the IP address of the iSCSI port on
the storage array, and, if necessary, also the port number if it has been
altered from the default of 3260. Click advanced to continue.
8.
In the Local Adapter dropdown box select Microsoft iSCSI Initiator..


This is an image of the user selecting the I SCSI initiator in the
dropdown box for local adapter.
9.
Enter the IP address of the host Ethernet NIC (source) that will be accessing this target port.
This is an image of the user selecting the IP address of the host's

adapter that will be accessing the target port entered previously.
10.
Do not set the CHAP logon information.
If CHAP is to be used, the CHAP secret should be configured on the array before setting it here.
Setting up CHAP authentication is covered later in this section.
Click OK to continue.
This is an image of the user selecting okay without setting the CHAP
secret.
11.
This is an image of the user clicking okay to continue.
12.
A successful connection between the host iSCSI port and the storage array is now shown in the Target Portals section.
Additional connections from network adapters to target portals can now be added if required.


This image shows successful connection between the host iSCSI port
and the storage array.
13.
Next, you will need to log onto the new connection.
In the Targets tab, click to select the target. Click Log On.
This image shows clicking Log on for the selected target.
14.
Click the Automatically restore this connection when the system boots check box if required.
Click the Enable Multi-Path check box if you are setting up connections for multiple Ethernet host ports.
Click Advanced.
NOTE:
The correct iSCSI multi-path software is installed along with the necessary host agent software, when the MDSM software is installed on an iSCSI host.
Installation of the MDSM host files is required for every iSCSI host attached to an MD3000i storage array.
This is image shows clicking on the Advanced option.
15.
In the Local adapter field, use the drop down menu to select Microsoft iSCSI Initiator
In the Source IP field, use the drop down menu to select the IP address of the network adaptor you wish to connect from.
In the Target Portal field, use the drop down manu to select the IP address of the iSCSI port on the storage array controller that you wish to connect to.


This is an image of completing the Advanced Settings information.
16.
This image shows clicking OK to continue.
17.
The information in the Targets tab will now show your iSCSI connection to the storage array.
Click on theDetails button
This image shows the iSCSI connection to the storage array.
18.
This screen shows all sessions are logged into the storage array.
In the example shown here, there are two sessions logged into the storage array.


This image shows the iSCSI sessions logged onto the storage array.
19.
Repeat steps 6 to 18 for all other iSCSI connections and sessions required between your host and the MD3000i.
20.
On the Configure tab in MDSM, click Configure Host Acess (Manual).
This is an image of the user configuring host acceess on the array.
21.
Enter the hostname and the type of operating system. Click Next.
NOTE:
Although Windows 2000 Server is listed as an operating system type in the drop down list, the OS is not supported on the MD3000i.
This is an image showing the user entering the hostname and operating system type. Click
next.
22.
Select the hostname in the list of known iSCSI intiators. Click Add to move the host into the Selected iSCSI initiators list on the right.
NOTE:
In Windows, the iSCSI initiator name can be found on the General tab of the iSCSI Initiator Properties window.


This is an image.
23.
This is an image of the user selecting next.
24.
Determine whether this host will share access to the same virtual disks as another host, for clustering purposes. Click Next.
This is an image showing the user selecting whether this host will share disks with another
host. Clustering software must be present to arbitrate between the hosts owning the disk
resources. Click next.
25.
Click Finish.


This is an image showing the user clicking finish.
iSCSI Authentication Using CHAPS

Configuration of Target and Initiator authentication using CHAPs and Mutual CHAPs is an important step in many iSCSI installations.
To configure authentication, use the following steps:
Setting Up iSCSI Authentication Using CHAPs

1.
2.
Set the target authentication. On the iSCSI tab, click Change Target Authentication.
This is an image showing the user selecting change target authentication.
3.
Select the level of CHAP authentication that will be used, by checking one or more option boxes. The levels of authentication are as follows:
• None only - no authentication is required for a host to connect to the storage array.
• Both None and CHAP - authentication is optional (both authenticated and non-authenticated hosts can connect to the storage array.
• CHAP only - authentication is required by all hosts.


This is an image showing the user selecting the level of authentication required.
In this scenario, only CHAP is chosen. Click CHAP Secret.

4.
Enter the CHAP secret into the text boxes. A random secret can also be chosen. Securely store the CHAP secret in a text file, as this secret must be entered during
the setup of CHAP on the hosts. If the secret is lost and another host needs to be added later, the secret will have to be reconfigured for all existing hosts. Click OK.
This is an image of the user entering the chap secret in both text
boxes and then clicking okay.
5.
Click OK.
This is an image of the user clicking okay.
6.
Click OK to exit the Change Target Authentication window.


This is an image of the user clicking okay, to exit the window.
7.
If a CHAP secret was installed on the storage array, the secret must now also be installed on the hosts. If a Mutual CHAP secret was installed, the initiators' secret
must be installed on the array. For the mutual secret to be set on the initiator, on the General tab in the iSCSI Initiator interface, click Secret. If a mutual secret was
not set up, skip this step.
This is an image.
8.
In the CHAP Secret Setup window, enter the Mutual CHAPsecret that was set on the array in MDSM. Click OK.
This is an image showing the user entering the CHAP secret and
clicking okay.
9.
Highlight the installed initiator-target portals that have been set up. Each one will now be reinstalled with the CHAP secret. Click Remove.
This is an image of the user removing the installed initiators so that

they can be reinstalled with the CHAP secret.


10.
Repeat the previous installation process shown in steps 7 through 10 above, with the exception that, for each installed portal, set the CHAP secret. Select the CHAP
Login Information option box, set the secret and click OK.
This is an image.
11.
Click OK to close the window. If discovery session failover is desired, repeat the previous step for all iSCSI ports on the storage array. Discovery session is the
timed re-validation of the CHAP authentication.
This is an image.
12.
On the iSCSI Initiator Properties window, click on the Targets tab. If the target discovery was successful, the iqn of the storage array should be listed under
Targets. The status will show Inactive. Click Log On.
This is an image of the user clicking on the targets tab and seeing the
iqn of the storage array with a status of inactive.
13.
Select Automatically restore this connection when the system reboots. Also, select Enable multi-path. Click Advanced.


This is an image of the user selecting to automatically restore the
connection when the system reboots, and enable multi path.
14.
Local Adapter must be set to Microsoft iSCSI Initiator; Source IP is the source IP address of the network adaptor you want to connect from; Target Portal is the
iSCSI port on the storage array controller you want to connect to; Data Digest and Header Digest are only for troubleshooting purposes; if CHAP is set, select
CHAP Logon Information and enter the CHAP secret; select Perform mutual authentication if mutual authentication is set on the array. Click OK.
This is an image of the user selecting all the parameters of operation

of the I SCSI session.
15.
Click OK to close this window.
This is an image showing the user clicking okay to close this

window.
16.
Repeat steps 26 to 31 for any remaining network adaptors to be configured for this host.
17.
On the Targets tab, click on Details.


This is an image of the user clicking on details on the targets tab.
18.
The two iSCSI sessions to the array can be seen in the Identifier window on the Sessions tab.
This is an image of the user clicking on the sessions tab to see the
two I SCSI sessions to the storage array.
Configuration of the iSCSI Initiator - Dual Path Data, Dual Controllers (Duplex)
The redundant network configuration with dual, independent Ethernet switches offers considerable flexibility in the physical placement of equipment, while maintaining
high availability and data path redundancy. As many as 16 hosts can be configured with dual path, redundant data paths to the storage array. In a redundant network
configuration, each iSCSI initiator on the host will be mapped to one portal on each of the storage array's controllers. In the direct attached scenario the default gateway is
not important. However, in the redundant SAN-attached configuration, if a host passes through a router the default gateway must be configured on each iSCSI portal on the
RAID Controllers.
The methods of configuring the IP addresses of the controllers are the same as in direct attached, and the configuration of the iSCSI initiators are the same. The differences
are that each host is cabled to redundant switches to provide the data pathways to each of the array controllers. Automatic discovery is limited to the local subnet when
installing hosts, so that manual discovery is the method of choice.

Expires 2/3/2011 12:22:48 PM iSCSI Host Configuration using IPV4 This document is Dell Confidential
iSCSI Host Configuration using IPV6

Configuration of IPv6 Enabled Windows 2008 iSCSI Host Connectivity
NOTE:
IPv6 is currently only supported for Windows 2008 iSCSI hosts. It requires controller firmware rev 06.70.15.60 and NVSRAM rev 67.08.90 or later.

The Microsoft iSCSI software initiator is integrated into Windows Server 2008. There is therefore no need to install a separate iSCSI software initiator.
The following procedure shows the steps necessary to configure IPv6 iSCSI host connectivity.
Configuration of the IPv6 Enabled iSCSI Host

1.
Before you begin configuring iSCSI, you should fill out the iSCSI Configuration Worksheet.
A sample worksheet is shown below.
This image shows part of the iSCSI configuration worksheet.
2.
You will need to configure the MD3000i storage array iSCSI ports with the correct IPv6 addresses.
From the iSCSI menu tab in the Modular Disk Storage Manager (MDSM), click on the Configure iSCSI Host Ports option
This image shows the selection of the configure iSCSI host port option in MDSM.
3.
From the iSCSI host port menu, select the first iSCSI port you wish to configure from the drop down menu.
This image show the selection of the iSCSI host port to be configured.
4.
Click the Enable IPv6 check box. Ensure that the Enable IPv4 check box is de-selected.
Next, click the IPv6 Settingsmenu tab


This is an image of the MDSM initial iSCSI host ports configuration screen.
IPv6 is being selected
5.
IPv6 addresses can be set manually or automatically.
As the host in this configuration is directly connected to the MD3000i storage array, the Obtain configuration automatically option is selected. A link-local IPv6
address will be assigned to the port. Link-local addresses will be unique for each interface on a LAN segment.
To configure a specific IPv6 address, select the Specify configuration option and enter the address.
This is an image of the MDSM IPv6 iSCSI port configuration screen. Obtain configuration automatically is
being selected.
6.
Advanced IPv6 settings are available for each port.
Click on Advanced IPv6 Settings button to configure the Ethernet priority or to enable VLAN support.
This is an image of the advanced IPv6

settings screen.
7.
Advanced host port settings are available for each port.
Click on Advanced Host Port Settings button to set up a custom listening port to enable jumbo Ethernet frames.
The TCP listening port for iSCSI defaults to 3260. The default listening port for an iSNS server is 3205.
The Jumbo frames setting can be set for oversized Ethernet frames, up to 9000 bytes/frame (default is 1500). Ensure that every component in the chain will properly
support the size of jumbo frame chosen.


This is an image of the advanced host ports settings screen.
8.
Repeat steps 3-7 above for any remaining iSCSI host ports that need configuring.
9.
Click the check box to Enable ICMP Ping responses for setup purposes. It can be turned off after the array setup is completed, if preferred. Changing the status of
this option box will reset all the iSCSI ports on the array. If data transfer is in progress, it will be interrupted until an iSCSI session has been restored.
NOTE:
Make note of the IP address assigned to each port. These will be needed for the following steps.
This image shows OK being selected to continue
10.
You will now see a warning message stating that the iSCSI ports will be reset if you continue.
Click Yes to continue.


This image shows Yes being selected to continue
11.
On your iSCSI host, open a command line session and type in the command netsh interface ipv6 show interface
A list of available interfaces is shown. The IDx column shows the ZoneID for each interface
Make a note of each Local Area Connection (LAN)and the associated ZoneID
This image shows the netsh interface ipv6 show interface CLI command.
12.
From the command line, type in the command netsh interface ipv6 show address
Make a note of the IPv6 address assigned to each Local Area Connection.
This image shows the netsh interface ipv6 show address CLI command.
13.
From the command line, type in the command ping [IPv6 address]%[ZoneID]
Replace [IPv6 address] with the IPv6 address for a connected LAN Ethernet port on your host and [ZoneID] with the relevant ZoneID for that port
A reply to the Ping command indicates correct connectivity between host and storage array.


This image shows the Ping CLI command.
14.
The iSCSI software initiator now needs to be configured for each iSCSI host to be attached to the MD3000i storage array.
From the Start menu, click Administrative Tools, and launch the Microsoft iSCSI Initiator.
Under Target Portals click Add.
This image shows launching the Microsoft iSCSI Initiator.
15.
If the Microsoft iSCSI Service is not running, you will see a warning message.
Click Yes to start the iSCSI Service.
This image shows clicking Yes to start the iSCSI service.
16.
The iSCSI Initiator will now start.
NOTE:
The Microsoft iSCSI Initiator included in Windows Server 2008 includes a tab for RADIUS (Remote Authentication Dial In User Service)support. This is
an AAA (Authentication, Authorization and Accounting) protocol used for controlling access to network resources.
Note that the MD3000i storage array does not support RADIUS authentication, hence this tab is not used.


This image shows the Microsoft iSCSI Initiator opening screen.
17.
Under Target Portals click Add Portal.
This image shows launching the Microsoft iSCSI Initiator.
18.
Enter the IPv6 address for your the first MD3000i iSCSI port that you wish to connect to.
Click Advanced
This image shows clicking Advanced.
19.


This image shows selecting the local adaptor option.
20.
In the Source IP field, use the drop down menu to select the IPv6 address of your first connected Ethernet port
This image shows selecting the target portal.
21.


22.
23.
A successful connection between the host iSCSI port and the storage array is now shown in the Target Portals section.
This image shows successful connection between the host

iSCSI port and the storage array.
24.
In the Targets tab, click on the target shown. Click Log On.


This image shows clicking Log on for the selected target.
25.
Click the Automatically restore this connection when the system bootscheck box if required.
Click Advanced.
NOTE:
The correct iSCSI multi-path software is installed, along with the necessary host agent software, when the MDSM software is installed on an iSCSI host.
Installation of the MDSM host files is required for every iSCSI host attached to an MD3000i storage array.
This is image shows clicking on the Advanced option.
26.
This is an image of selecting the Local adapter.
27.
In the Source IP field, use the drop down menu to select the IPv6 address of your connected Ethernet port


This image shows selecting the Source IP.
28.
In the Target Portal field, use the drop down menu to select the IPv6 address of the MD3000i iSCSI port to which your are connecting.
This image shows selecting the Target Portal.
29.


30.
31.
The information in the Targets tab will now show your iSCSI connection to the storage array.
This image shows the Persistent Targets tab of the iSCSI

Initiator.
32.
Repeat steps 14 to 28 for all other iSCSI connections between your host and the MD3000i.
33.
On the Configure tab in MDSM, click Configure Host Access (Manual) option.


This image shows selecting the Configure Host Access option in MDSM.
34.
Enter the hostname in the appropriate field and select the host type from the drop down menu.
Click Next.
This image shows entering the host name and selecting host type, then clicking next.
35.
Select the host from the list of known iSCSI intiators.
Click Add to move the host into the Selected iSCSI initiators list on the right.
This image shows clicking Add.
36.


This image shows clicking Next to continue.
37.
Determine whether this host will share access to the same virtual disks with another host (for clustering purposes).
Click Yes or No as appropriate.
This image shows clicking Next to continue.
38.
Click Finish.
This image shows clicking Finish.
39.
At the Configure Host Access completion window, click No if you have finished configuring host access.
If you have other hosts to configure, click Yes and repeat the steps above for additional hosts.


This image shows clicking the No option to conclude configuring host access.
40.
From the iSCSItab of MDSM, choose the View/End iSCSI Sessions option
This is image shows seleicting View/End iSCSI Sessions.
41.
You will now see the iSCSI sessions from your configured host to the storage array.
Click Close to exit
This is an image connected iSCSI sessions.
42.
Take a moment to look at the iSNS target discovery configuration page.
From the iSCSI tab, Click on the Change Target Discovery option


This image shows selecting Change Target Discovery.
43.
The Change target Discovery page shows the setup options for using iSNS.
Click the Use iSNS Server check box to allow the MD3000i to register with an iSNS server for target discovery.
Choose appropriate settings for either IPv4 or IPv6 configuration.
If you are not setting up iSNS, click Cancel to remove iSNS discovery options.
This is an image of the iSNS configuration screen.
iSCSI Authentication Using CHAPS

Configuration of Target and Initiator authentication using CHAPs and Mutual CHAPs is an important step in many iSCSI installations.
To configure authentication, use the following steps:

1.
From the iSCSI tab in MDSM, select the Change Target Authentication option.


This image shows selecting
2.
Click the CHAP Secret button
This image shows clicking CHAP Secret.
3.
Enter the CHAP secret into the text boxes. < br>A random secret can also be chosen.
NOTE:
Securely store the CHAP secret in a text file, as this secret must be entered during the setup of CHAP on the hosts. If the secret is lost and another host needs to
be added later, the secret will have to be reconfigured for all existing hosts.
This image shows entering a CHAP secret.
4.
Next, ensure the correct level of CHAP authentication is chosen by checking one or more option box.
The levels of authentication are as follows:
• None only - no authentication is required for a host to connect to the storage array.
• Both None and CHAP - authentication is optional (both authenticated and non-authenticated hosts can connect to the storage array.
• CHAP only - authentication is required by all hosts.
This image shows selection of authentication method and clicking OK to continue.


5.
6.
Mutual CHAPs authentication provides a slightly higher degree of security.
This requires the Initiator to authenticate the Target and the Target to authenticate the Initiator.
If Mutual CHAPs is to be configured, from the iSCSI tab in MDSM, choose the Enter Mutual Authentication Permissions option.
This image shows selecting the Enter Mutual Authentication Permissions option.
7.
Select the host that requires mutual authentication from the Select an Initiator field.
Click the CHAP Secret button.
This image shows selecting the Initiator and clicking the CHAP Secret button.
8.
Enter and confirm the CHAP secret for the selected host. CHAP secrets must be a minimum of 12 characters in length.
This image shows entering the host CHAP secret.


9.
10.
Next, you will need to configure the host for CHAPs or Mutual CHAPs authentication.
If Mutual CHAPs is required, a secret must be installed on the hosts iSCSI initiator.
From the General tab of the Microsoft iSCSI Initiator, click Secret.
This image shows clicking the Secret button on the iSCSI

Initiator General tab.
11.
Enter the iSCSI initiator's CHAP secret. This must be a min of 12 characters long. Click OK to continue
This image shows entering the CHAP secret and clicking OK

to continue.
12.
From the Discovery tab, select each target portal and click Remove.
This image shows removing all existing configured Target

Portals in the iSCSI Initiator Discovery tab.


13.
In the Targets tab, click Details.
This image shows clicking the Details button in the Targets tab.
14.
Select each target by clicking the check box beside the identifier.
Click Log off.
This image shows selecting target sessions and clicking Log

off.
15.
16.
In the Favorite Targets tab, select each target shown and click Remove.


This image shows selecting persistent targets and clicking
Remove.
17.
In the Discovery tab, click Add Portal.
This image shows clicking Add in the discovery tab.
18.
Enter the IPv6 address for your the first MD3000i iSCSI port that you wish to connect to.
This image shows clicking Advanced.
Click Advanced.
19.
In the Local adapter field, select Microsoft iSCSI Initiator
In the Source IP field, select the IP address for the host Ethernet port you are configuring.
Click the CHAP logon information check box.

In the Target Secret, enter the secret that you setup on your MD3000i storage array.
If you have setup mutual CHAPs, click the Perform mutual authentication check box.


This image shows completing fields in the Advanced Settings
box and clicking OK to continue.
20.
21.
You will now see the target portal to which you have connected
This image shows conncted target portals.
22.
From the Targets tab, select the target and click Log on.


This image shows clicking the Log on button in the Targets tab.
23.
Click the Automatically restore this connection when the system bootscheck box if required.
Click Advanced.
This image shows clicking the Advanced button.
24.
In the Local adapter field, select Microsoft iSCSI Initiator
In the Source IP field, select the IP address for the host Ethernet port you are configuring.
In the Target Portal field, select the target iSCSI port of the MD3000i storage array that you are connecting to.
Click the CHAP logon information check box.

In the Target Secret, enter the secret that you setup on your MD3000i storage array.
If you have setup mutual CHAPs, click the Perform mutual authentication check box.
This image shows completing the Advanced Settings screen

and clicking OK to continue.
25.


This image shoows clicking OK to continue.
26.
You will now see that you are logged onto and connected to the MD3000i target iSCSI port.
This image shows target connections between host and

storage array.
27.
Repeat steps 18 to 27 for all other iSCSI connections between your host and the MD3000i.
28.
In the Favorite Targets tab, you will now see all the connections that you have configured from your host to your MD3000i storage array that will automatically
restore when you reboot your host.
This image shows Persistent Targets that are now configured.
Configuration of the iSCSI Initiator - Dual Path Data, Dual Controllers (Duplex)
The redundant network configuration with dual, independent Ethernet switches offers considerable flexibility in the physical placement of equipment, while maintaining
high availability and data path redundancy. As many as 16 hosts can be configured with dual path, redundant data paths to the storage array. In a redundant network
configuration, each iSCSI initiator on the host will be mapped to one portal on each of the storage array's controllers. In the direct attached scenario the default gateway is
not important. However, in the redundant SAN-attached configuration, if a host passes through a router the default gateway must be configured on each iSCSI portal on the
RAID Controllers.
The methods of configuring the IP addresses of the controllers are the same as in direct attached, and the configuration of the iSCSI initiators are the same. The differences
are that each host is cabled to redundant switches to provide the data pathways to each of the array controllers. Automatic discovery is limited to the local subnet when
installing hosts, so that manual discovery is the method of choice.


Expires 2/3/2011 12:22:48 PM iSCSI Host Configuration using IPV6 This document is Dell Confidential
RHEL Hosts
Installation of the Red Hat Enterprise Linux (RHEL) iSCSI Initiator and the Modular Disk Storage
Manager Software
This procedure shows the steps necessary to install the RHEL iSCSI Initiator software and the Modular Disk Storage Management (MDSM) software and discover the
storage array.

Complete the following steps to install the iSCSI Initiator software.

1.
The Linux iSCSI initiator and all appropriate patches are installed using the MD3000i Resource CD. Red Hat and Novell have not picked up necessary changes to
the initiator that Dell has provided in the version distributed on the Resource CD. Insert the CD and follow the on-screen instructions to install. Rename the
file /etc/iscsi.conf to /etc/iscsi.conf.old. Then copy the file iscsi.conf_RHEL4u4 from the MD3000i resource cd to /etc/iscsi.conf.
This is an image showing the user replacing the / etc / iscsi.conf file with the one from the installation CD.
2.
Using VI, open the file / etc / iscsi.conf for editing.
This is an image showing V I being used to edit the file.
3.
Enter the IP addresses of the MD3000i RAID Controller ports as the DiscoveryAddress.
This is an image showing the insertion of the controller IP addresses as discovery address equals
entries.
4.
Start the iSCSI service, with service iscsi start.
This is an image showing the user starting the I SCSI service at the command line with service i scsi start.
5.
Set the iSCSI service to startup automatically on boot. Also, verify that it will start in run levels 3 and 5.
This is an image showing the verification that the I SCSI service will run under levels 3 and 5.
Installation and Configuration of MDSM on a Red Hat Linux Host

Complete the following steps to install and configure MDSM on a Red Hat Linux Host.

1.
Configure the NIC ports on the server to maintain the same IP address on reboot. Edit the settings with vi.
This is an image showing the user opening the configuration file for ethernet port eth 5.
2.
The edited file will resemble the following screenshot.
This is an image showing the approximate configuration appearance of the ethernet port.
3.
Perform the following steps to verify configuration.
This is an image showing the verification of the configuration of ethernet port 5.
4.
Insert the MD3000i Resource CD and run the install.sh script from the Linux folder.
This is an image showing the user launching the install shell on the CD from the command line.
5.
Choose option 4 - Install MD3000i Documentation and select the location for installation.

This is an image showing the user choosing option four to install the documentation.
6.
Return to the main menu and choose option 2 - Install MD3000i Storage Manager.
This is an image showing the user returning to the main menu and choosing option two, to install the
storage manager software.
7.
The installer will launch the GUI.
This is an image showing the installation continuing.
8.
Choose the language and click OK.
This is an image showing the gooey launch where the user chooses the language and selects
okay.
9.
Click Next.

This is an image showing the introduction screen where the user chooses next.
10.
Accept the license agreement and click Next.
This is an image showing the user accepting the license agreement and choosing next.
11.
Choose the installation directory and click Next.
This is an image showing the user selecting the installation directory and choosing next.
12.
Select Typical (Full Installation) and click Next.

This is an image showing the user selecting a typical installation and choosing next.
13.
A warning message will appear instructing the user to install the RDAC for multipath support. With this release the RDAC is now a DKMS package. It will be
installed using option 3 from the install script
This is an image showing the user being warned to install R DAC, however, it will be installed
later.
14.
Click Install.
This is an image showing the user confirming the choices made and selecting install.
15.
Installation continues.

This is an image showing the installation continuing.
16.
Click Done. Do not install the multi-path driver at this time. MPP will be installed later in this procedure.
This is an image showing the user clicking done at the end of the installation.
17. NOTE:
The array will default to requesting DHCP-assigned IP addresses for the management ports on the controllers. If the dynamically assigned addresses are not in
the same subnet with the management host, the discovery process will not find the array. The discovery of arrays is only on the host's subnet through port
2463. If a DHCP response is not acknowledged, the controllers will default to 192.168.128.101 for controller 0, and 192.168.128.102 for controller 1. Once the
units have had IP addresses manually set, the units will no longer request dynamic IP assignment and will continue to operate at the manually set addresses. If
these set addresses are not known, the IP addresses of the controllers will need to be retrieved with the password reset cable.
If the host is remotely connecting to the array, then a default gateway will be needed. If one is not present when this command is run, then the array should be
directly connected to the host and set on the same subnet as the storage to proceed with setup. The IP addresses can then be changed to suit the installation, and then
the host can be connected remotely. Using the same parameters for Hyperterminal that are used for password reset, issue the following command at the shell
interface.
-> netCfgShow
The response will appear with the following structure:
This is an image of the response seen in hyperterminal.
18.
Launch the MDSM GUI. A window should immediately appear asking the user to choose between Automatic discovery or Manual.

This is an image showing the launch of the gooey.
19.
If the array is on the same subnet as the host, you may select the option button for Automatic and click OK. In this scenario, we will choose Manual.
This is an image showing the user selecting manual discovery.
20.
Select Out-of-band management, and enter the IP addresses of the RAID Controllers' management ports. In-band storage management is not enabled until an
iSCSI session is set up and operating. Click Add.
NOTE:
After discovery, it is recommended that you reconfigure the out-of-band management IP addresses of the RAID controllers to be on your management
network. After changing them, you will need to rediscover the array at the new IP addresses.
This is an image showing the user entering the controller IP
addresses so the array can be discovered.
21.
Click No.
This is an image showing the screen where the user can select
whether to discover another array.

22.
On the iSCSI tab in MDSM, click on Configure iSCSI Host Ports.
This is an image showing the user clicking on configure i scsi host ports on the I SCSI tab of MDSM.
23.
Select each port on the raid controllers and enter the appropriate IP address for each to match the configuration set in the iscsi.conf file. Select Enable ICMP PING
responses for testing. It may be turned off later if desired. Click OK when complete.
This is an image of the user setting the IP addresses to match the addresses chosen for the
controllers during the I SCSI initiator installation.
24.
Start the iSCSI service at the command line with the command service iscsi start.
This is an image showing the user starting the I SCSI service from the command line.
25.
Restart the MDSM agent at the command line. Make sure to wait a few seconds for the start to complete. It should look similar to the screenshot below.

This is an image showing the user restarting the MDSM agent at the command line.
26.
Verify the iSCSI connections have been established using the command iscsi-ls.
This is an image showing the user verifying the I SCSI connections with the command I SCSI dash L
S.
27.
On the Configure tab in MDSM, select Configure Host Access (Automatic)
This is an image of the user selecting Configure host access automatic, on the configure
tab.
28.
Select the host name and move it to the right. Click ok to complete

This is an image showing the user selecting the host name and moving it to the right hand column, and
then clicking okay to complete.
29.
Install the RDAC software. Ensure the kernel-devel / kernel-smp-devel package is installed - rpm -qa | grep kernel Insert the MD3000i resource cd and run the
install.sh script from the linux folder.
This is an image showing the user isntalling the R DAC software.
30.
Choose option 3 - Install Multi-pathing driver. This will install the following packages:
• dkms-2.0.16-1 (This is not installed if it or a later version of DKMS is already present)

• iscsi_sfnet
• linuxrdac-99.01.B6.65-dkms
This is an image of the main menu on the resource CD.
This is an image shows the installation of the multipath driver.
31.
The dkms install of the RDAC driver installs the drivers, makes a new initrd, and modifies the grub.conf file to boot to the MPP kernel. Here is an example
grub.conf after the RDAC is installed.

This is an image showing an example grub dot conf file after R Dac has been installed.
32.
Reboot the host.
This is an image showing the host being rebooted.
33.
To test the installation, configure two Virtual Disks in MDSM and map them to the host. Use the hot_add utility to rescan for new devices. Verify the LUNs are
seen on one path using the SMdevices command.
This is an image showing the LUN paths.

Expires 2/3/2011 12:22:48 PM RHEL Hosts This document is Dell Confidential
MDSM Usage
This is detailed information about the MDSM user interface and methods used to manage the MD3000i Enclosure System for data storage.
Modular Disk Storage Manager (MDSM) Overview

MDSM is used to discover and manage multiple storage arrays. The software can be used on any host attached to the storage array, as well as on storage management
stations connected to the same sub-network. MDSM also contains an optional event monitoring service that is used to send alerts when a critical problem with the storage
array occurs and a command line interface (CLI) to access functions performed by MD Storage Manager.
The User Interface

The Storage Manager screen is divided into three parts:
• The Title Bar at the top of the screen displays the name of the application and the Dell logo.
• Beneath the Title Bar is the Array Selector, listing the MD3000i Storage Array that is currently selected. The icon next to the array's name indicates its condition.
You can choose another array by clicking the down-arrow next to the array's name and highlighting a different array in the drop-down list. Links to the right of the
array name let you add or remove arrays from the list of managed arrays. Links to the far right provide access to online help or close the Storage Manager.

• Beneath the Array Selector is the Content Area. Six tabs appear in this area to group the tasks you can perform on the selected array. When you click on a tab, the
Content Area displays links for the tasks you can perform. The following sections list some of the tasks you can perform under each tab.
These tabs appear in the Content Area:
1. Summary Tab - You can see:

◦ The status of a storage group.
◦ The hardware components in a storage group.
◦ Storage array capacity.
◦ Hosts, mappings, and storage partitions.
◦ Virtual disk groups and virtual disks.
◦ Links to online Help, FAQs, and an online tutorial.
2. Configure Tab - You can:
◦ Configure host access.
◦ Create a host group.
◦ Create hot spares.
◦ Create virtual disks.>
◦ Create snapshot virtual disks (if enabled).
◦ Create virtual disk copies (if enabled).
◦ Create host-to-virtual disk mappings.
3. Modify Tab - You can:
◦ Modify the host topology.
◦ Rename and delete virtual disks.
◦ Add free capacity to a disk group.
◦ Change virtual disk ownership and the preferred path of virtual disks.
◦ Modify a snapshot virtual disk.
◦ Manage virtual disk copies.
◦ Edit host-to-virtual disk mappings.
4. Tools Tab - You can:
◦ Rename a storage array.
◦ Set or change a password.
◦ View or enable premium features.
◦ Turn on indicator lights.
◦ Change enclosure ID numbers.
◦ Set or change enclosure tags.
◦ Set up e-mail alerts and SNMP alerts.
◦ Synchronize controller clocks, change the network configuration, or reset the battery age.
◦ Inherit system settings.
5. iSCSI Tab - You can:
◦ Change target authentication
◦ Enter mutual authentication permissions
◦ Change target identification
◦ Change target discovery
◦ Configure iSCSI host ports
◦ View/end iSCSI sessions
◦ View iSCSI statistics
6. Support Tab - You can:
◦ Recover from a failure.
◦ Gather support information.
◦ View the storage array profile.
◦ Download RAID controller, NVSRAM, and physical disk firmware.
◦ Manage RAID controllers.
◦ View online help.
The Access Virtual Disk

Each RAID controller in an MD3000i Storage Array maintains an access virtual disk. The host-agent software uses the access virtual disk to communicate management
requests and event information between the storage management station and the RAID controller module in an in-band-managed storage array. The access virtual disk is
used because the commands issued with in-band management require a destination SAS address at the controller to receive the commands. The access virtual disk is not
available for application data storage and is automatically created. The user has no role in actively creating this virtual disk. The default virtual disk is 31.
Out-of-Band and In-Band Management

You can manage a storage array through two different pathways:
• Out-of-band management - data is separate from commands and events, utilizing the Internet Protocol over the Ethernet management connection. For automatic array
discovery, the management software on the host will utilize port 2463 to locate arrays on the local subnet. Both discovery and out-of-band management utilize
software port 2463. Firewall ports should be enabled for port 2463 to allow remote administration of the array.
• In-band management - commands, events, and data are transferred across the iSCSI sessions after initiation.
NOTE:
Dell recommends using out-of-band management but in-band management may be optionally configured. To use automatic discovery for in-band management, the
management station must initially be on the same subnet as the MD3000i management ports. After initial setup the management station needs only to be able to reach
the in-band subnet.
Adding Storage Arrays

To add a storage array to MD Storage Manager, click the New link in the Array Selector area. A window is displayed that allows you to choose the automatic or manual
process to add a new storage array.
Automatic Discovery of Storage Arrays

The Automatic Discovery process sends out a broadcast message across the local subnet and adds any storage array that responds to the message. Out-of-band discovery of
the MD3000i will happen immediately. Out-of-band management of an MD3000i must be performed manually after an iSCSI session has been initiated.

Manual Addition of a Storage Array

Use Manual Addition if the storage array resides outside of the local subnet. This process requires specific identification information to manually add a storage array:
• To add a storage array that uses out-of-band management, specify the host name or IP address of each controller in the storage array .
• To add a storage array that uses in-band management, specify the host name or IP address of the host after an iSCSI session has been initiated.
Naming Storage Arrays

Each storage array should be assigned a unique name. A storage array name has a 30-character limit. All leading and trailing spaces are deleted from the name. A name can
consist of letters, numbers, and the special characters underscore (_), dash (-), and pound sign (#). No other special characters are allowed.
To locate a storage array:

1. Click the Tools tab.
2. Click the Blink link, and then click the Blink Storage Array or Enclosures link.
To rename the selected storage array:

1. Click the Tools tab.
2. Click the Rename Storage Array link.
3. Type a unique, meaningful name that is easy to understand and remember.
4. Click OK.
Removing Storage Arrays

You can remove a storage array from the list of managed arrays if you no longer want to manage it from a specific storage management station. Removing a storage array
does not affect the storage array or its data in any way. Removing a storage array simply removes it from the list of storage arrays that appear in the drop-down list in the
Array Selector. If a storage array is accidentally removed, it can be added again.
To remove a storage array:

1. Click the Remove link located to the right of the drop-down menu in the Array Selector.
2. Click OK in the Remove dialog box.
Setting Up Your Storage Array

The Perform Initial Setup Tasks link located on the Summary tab provides links to the basic steps you should follow when initially setting up a storage array in MD
Storage Manager.
1. Blink the storage array to physically locate it.

2. Rename the storage array for easy identification of the storage array.
3. Set a storage array password to prevent unapproved manipulation of the storage array.
NOTE:
Having a password on the storage array makes it more secure but may also make other routine tasks more difficult.
4. Set Up Alert Notifications - Enable e-mail and SNMP alerts to notify administrators about storage array conditions that require attention.
1. Configure Sender E-mail Settings - Provide the SMTP, e-mail address, and contact information MDSM uses to send e-mail alerts.
2. Add or Edit E-mail Addresses - Provide information about accounts that should receive e-mail-based alerts.
3. Set Up SNMP Alerts - Provide information about hosts that should receive SNMP-based alerts.
5. Configure Host Access for one or more hosts to access the storage array.
6. Configure storage array using either automatic configuration or manual configuration.
7. View and Enable Premium Features that were purchased for this storage array.
8. Change Network Configuration if needed.
Setting a Password on the Storage Array

MDSM asks for this password when an attempt is made to change the storage array configuration, such as when a virtual disk is created or deleted. View operations do not
require a password. If no password has been set then no challenge is issued.
To set, change, or remove a password:

1. Click the Tools tab, then click the Set or Change Password link.
2. To enter a new password where none exists:
1. Leave the Current password text box blank.
2. Enter the new password in the New password and Confirm new password text boxes.
3. To change a password
1. Enter the current password in the Current password text box.
2. Enter the new password in the New password and Confirm new password text boxes.
4. To remove a password:
1. Enter the current password in the Current password text box.
2. Leave the New password and Confirm new password text boxes blank.
5. To recover from a lost or forgotten password, refer to the Password Reset Procedure Reference in the Maintenance Section.
Configuring Alert Notifications

MDSM can send an alert for any condition on the storage array that requires attention, such as the failure of a storage array component or the occurrence of an adverse
environmental condition. Alerts can be sent as e-mail messages or as SNMP messages. Verify whether alerts are currently set by looking at the Alert status line in the Status
area of the Summary tab.

Configuring E-mail Alerts

To configure e-mail alerts, click the Tools tab and then click the Set up e-mail alerts link. The Content Area displays two links: Set Up Email Alerts and Set Up SNMP
Alerts.
NOTE:
These settings apply to all storage arrays currently managed by the management station.
To configure sender e-mail settings:

1. Click the Tools tab, then click the Set up e-mail alerts link.
2. Enter the following information:
1. Sender email address - the source email address that will be shown on the email
2. Mail (SMTP) server - The name of the Simple Mail Transfer Protocol (SMTP) gateway of the mail server from which e-mail alerts will be sent, e.g.
smtp.mycompany.com.
3. Recipient email address - enter each recipient name and click Add after each one. Click Save when recipient addresses are complete.
Configuring SNMP Alerts

The Management Information Base (MIB) for the MD3000i is copied to the client directory as part of a Full or Management Station installation selection.
DellMDStorageArray.mib can be compiled on an SNMP Management Console using the interface provided by the console.
1. Click the Tools tab, and then click the Set up SNMP Alerts link.
2. Enter the Community name. The community name is an ASCII string that identifies a known set of management consoles and is set by the network administrator in
the management console. The default community name is public.
3. Enter the Trap destination. The trap destination is the IP address or the host name of a management console that runs an SNMP service.
4. Click Add to add the management console to the Configured SNMP addresses list.
5. Repeat steps 2 through 4 until you have added all management consoles that should receive SNMP alerts.
6. Click OK.
NOTE:
You must install an SNMP service on every system included in the list of addresses configured to receive SNMP alerts. You do not have to install MDSM on a system
in order to display SNMP alerts. You need only install an appropriate SNMP service and application (such as the Dell IT Assistant).
Event Monitor
When enabled, 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 e-mail, SNMP trap messages, or both. For the most timely and continuous notification of events, enable the event
monitor on a management station that runs 24 hours a day. Enabling the event monitor on multiple systems or having a combination of an event monitor and MDSM active
can result in duplication of events.
Enabling and Disabling the Event Monitor
Microsoft Windows
1. Select 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. In the Service Status area, click Start . To stop the service, in the Service Status area, click Stop.
Linux OSes
At the command prompt, type SMmonitor start and press <Enter>. When the program startup begins, the system displays the following message: SMmonitor started. To
stop the service type SMmonitor stop and press <Enter>. The system displays the following message: Stopping Monitor process.

Expires 2/3/2011 12:22:48 PM MDSM Usage This document is Dell Confidential
Comparison of Premium Features

The Premium Features available with the MD3000 / MD3000i Storage Arrays include:
• Snapshot Copy - A snapshot virtual disk is a point-in-time image of a virtual disk in a storage array. It is not an actual virtual disk containing data; rather, it is a
reference to the data that was contained on a virtual disk at a specific time. A snapshot virtual disk is the logical equivalent of a complete physical copy. However,
you can create a snapshot virtual disk much faster than a physical copy, using less disk space.
• Virtual Disk Copy - When you create a virtual disk copy, you create a copy pair that has a source virtual disk and a target virtual disk on the same storage array.
When you start a virtual disk copy, all data is copied to the target virtual disk, and the source virtual disk permissions are set to read-only until the virtual disk copy is
complete
Here is a comparison of the Snapshot and Virtual Disk Copy Premium Features:
Comparison of Snapshot and Virtual Disk Copy

Snapshot Virtual Disk Copy
Description Point in time (PiT)copy on write Point in time full copy (clone) of the source data

• PiT backup images

• Operations where the data must be "frozen" at a particular point • Full PiT data for analysis, mining and testing without directly effecting the
Typical
in time. source's data or performance
Uses
• Data mining and analysis • Migrating data between storage tiers
• File restoration
• Instantaneous - when limited time is available for a full virtual

disk copy
Features • Less disk space then virtual disk copy Eliminates I/O contention on the primary virtual disk
• Mappable to any host
• Can be read from, or written to
Some performance strain due to processing against both the data

Performance No performance constraints once the copy is complete
source and table of pointers
Availability Recover source data in the event of corruption Recover source data in the event of corruption AND hardware failure
Fraction of the capacity of the source volume (approx. 20% of the
Copy size Same amount of capacity as the source data required
source capacity)

Expires 2/3/2011 12:22:48 PM Comparison of Premium Features This document is Dell Confidential
Premium Feature - Snapshot Virtual Disk

The Premium Feature Activation card is shipped in the same box as the MD3000 / MD3000i Storage Array. Follow the directions on the card to obtain a key file and to
enable the feature.
Here is a sample of the card; click to enlarge:
This is a
thumbnail
image of a
sample
Snapshot
Snapshot
The Snapshot feature provides a point in time (PiT) copy of a virtual disk. Its creation is near instantaneous and requires only a small amount of disk space. The snapshot
virtual disk appears and functions as a standard virtual disk. The virtual disk on which the snapshot is based, called the source virtual disk, must be a standard virtual disk in
the storage array. No I/O requests are permitted on the source virtual disk while the virtual disk snapshot is being created. Deleting a snapshot does not affect data on the
source virtual disk.
A snapshot repository virtual disk containing metadata and copy-on-write data is automatically created when a snapshot virtual disk is created. The only data stored in the
snapshot repository virtual disk is that which has changed since the time of the snapshot.
After the snapshot repository virtual disk is created, I/O write requests to the source virtual disk resume. Before a data block on the source virtual disk is modified,
however, the contents of the block to be modified are copied to the snapshot repository virtual disk for safekeeping. Because the snapshot repository virtual disk stores
copies of the original data in those data blocks, further changes to those data blocks write only to the source virtual disk. The snapshot 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, you specify where to create the snapshot repository virtual disk, its capacity, and other parameters. You can disable or delete the
snapshot virtual disk when you no longer need it, such as when using the snapshot as a means of capturing a backup, and the backup is now complete. If you disable a
snapshot virtual disk, you can re-create and reuse it the next time you perform a backup. If you delete a snapshot virtual disk, you also delete the associated snapshot
repository virtual disk.
Creating a Snapshot Virtual Disk

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. If 8 MB of free capacity is not available in the disk group of the source virtual disk, the Create Snapshot Virtual Disks feature defaults to the advanced path. In
the advanced path option, you can choose to place the snapshot repository virtual disk in another disk group or you can use unconfigured capacity on the storage array to
create a new disk group.
NOTE:
You can create concurrent snapshots of a source virtual disk on both the source disk group and on another disk group.
Before creating a Snapshot Virtual Disk, please note:
• These types of virtual disks are not valid source virtual disks: snapshot repository virtual disks, snapshot virtual disks, target virtual disks that are participating in a
virtual disk copy.
• You cannot create a snapshot of a virtual disk that contains unreadable sectors.
• You must satisfy the requirements of your host operating system for creating snapshot virtual disks. Failure to meet the requirements of your host operating system
results in an inaccurate point-in-time image of the source virtual disk or the target virtual disk in a virtual disk copy
If you want to use a snapshot regularly, such as for backups, use the Disable Snapshot and Re-create Snapshot options to reuse the snapshot. Disabling and re-creating
snapshots preserves the existing virtual disk-to-host mappings to the snapshot virtual disk.

Snapshot Parameters - Simple Path
Using the simple path, you can specify these parameters for your snapshot virtual disk:
• Snapshot Virtual Disk Name - A user-specified name that helps you associate the snapshot virtual disk to its corresponding snapshot repository virtual disk and
• 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.
Using the simple path, these defaults are used for the other parameters of a snapshot virtual disk:
• Capacity Allocation - The snapshot repository virtual disk is created using free capacity on the same disk group where the source virtual disk resides.
• Host-to-Virtual Disk Mapping - The default setting is Map now.
• Percent Full - When the snapshot repository virtual disk reaches the specified repository full percentage level, the event is logged in the Main Event Log (MEL). The
default snapshot repository full percentage level is 50 percent of the source virtual disk.
• Snapshot Repository Virtual Disk Full Conditions - When the snapshot repository virtual disk becomes full, you are given a choice of failing write activity to the
source virtual disk or failing the snapshot virtual disk.
Creating a Virtual Disk Using the Simple Path
NOTE:
Removing the drive letter of the associated virtual disk in Windows or unmounting the virtual disk in Linux will help to guarantee a stable copy of the virtual disk for
the Snapshot.
1. Stop all data access (I/O) activity to the source virtual disk before creating a snapshot to ensure that you capture an accurate point-in-time image of the source virtual
disk.
2. If you are running Windows, run the SMrepassist (replication assistance) utility from the command line in a DOS window. The SMrepassist utility is installed in
the /util/ directory of your host. It flushes the source virtual disk's cache before creating a snapshot. Use this syntax: SMrepassist -f <filesystem-identifier>
3. In MDSM, click the Configure tab, and then click the Create Snapshot Virtual Disks link.
4. The Additional Instructions dialog appears; click the Close button in this dialog to continue.
5. Click the plus sign (+) to the left of the disk group to expand it, then click the virtual disk from which you want to create a snapshot. Click the Next button. A No
Capacity Exists warning appears if there is not enough space in the disk group of the source virtual disk to create the snapshot.
6. On the Create Snapshot Virtual Disks - Select Path screen, select the Simple path.
NOTE:
A snapshot repository virtual disk requires 8 MB of free space. If the required free space is not available in the disk group of the source virtual disk, the Create
Snapshot Virtual Disks feature defaults to the Advanced path.
7. Click the Next button.
8. Type a name for the snapshot in the Snapshot virtual disk name text box.
9. Type a name for the snapshot repository virtual disk in the Snapshot repository virtual disk name text box.
11. Choose whether to map the virtual disk to a host (or host group) now or later:
To map now, click the Map now radio button, select a host or host group by clicking it, then assign a LUN.
To map later, click the Map later radio button.
12. Click the Finish button to create the snapshot virtual disk and the associated snapshot repository virtual disk.
13. After you have created one or more snapshot virtual disks, mount or reassign a drive letter of the source virtual disk.
14. If needed, assign host-to-virtual disk mapping between the snapshot virtual disk and the host operating system that accesses it.
NOTE:
In some cases, depending on the host type and any virtual disk manager software in use, the software prevents you from mapping the same host to both a source
virtual disk and its associated snapshot virtual disk.
15. If you are using a Linux-based system, run the hot_add utility to register the snapshot virtual disk with the host operating system.
Snapshot Parameters - Advanced Path
Use the advanced path to choose whether to place the snapshot repository virtual disk on free capacity or unconfigured capacity and to change the snapshot repository
virtual disk parameters. You can select the advanced path regardless of whether you use free capacity or unconfigured capacity for the snapshot virtual disk.
Using the advanced path, you can specify these parameters for your snapshot virtual disk:
• 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.
• Capacity Allocation - This parameter allows you to choose where to create the snapshot repository virtual disk. You can allocate capacity by using one of these
methods:
◦ Use free capacity on the same disk group where the source virtual disk resides.
◦ Use free capacity on another disk group.
◦ Use unconfigured capacity and create a new disk group for the snapshot repository virtual disk.
Dell recommends placing the snapshot repository virtual disk within the disk group of the source virtual disk. This ensures that if physical disks 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.
• Percent Full - When the snapshot repository virtual disk reaches the user-specified repository full percentage level, the event is logged in the Major Event Log
(MEL). The default snapshot repository full percentage level is 50% of the source virtual disk.
• Snapshot Repository Virtual Disk Full Conditions - You can choose whether to fail writes to the source virtual disk or fail the snapshot virtual disk when the snapshot
repository virtual disk becomes full.
• Host-to-Virtual Disk Mapping - Choose whether to map the snapshot virtual disk to a host or host group now or to map the snapshot virtual disk later. The default
setting is Map later.
Creating a Virtual Disk Using the Advanced Path
NOTE:
Removing the drive letter of the associated virtual disk in Windows or unmounting the virtual disk in Linux will help to guarantee a stable copy of the virtual disk for
the Snapshot.

1. Stop all data access (I/O) activity to the source virtual disk before creating a snapshot to ensure that you capture an accurate point-in-time image of the source virtual
disk.
2. If you are running Windows, run the SMrepassist (replication assistance) utility from the command line in a DOS window to flush the source virtual disk's cache.
Use this syntax: SMrepassist -f <filesystem-identifier>
3. In MDSM, click the Configure tab, and then click the Create Snapshot Virtual Disks link.
4. The Additional Instructions dialog appears; click the Close button in this dialog to continue.
5. Click the plus sign (+) to the left of the disk group to expand it, then click the virtual disk from which you want to create a snapshot. Click the Next button.
A No Capacity Exists warning appears if there is not enough space in the disk group of the source virtual disk to create the snapshot.
6. On the Create Snapshot Virtual Disks - Select Path screen, select the Advanced path.
8. Type a name for the snapshot in the Snapshot virtual disk name text box.
9. Type a name for the snapshot repository virtual disk in the Snapshot repository virtual disk name text box.
11. Choose whether to create the snapshot virtual disk from unconfigured capacity or free capacity.
To create the snapshot virtual disk from unconfigured capacity:
1. Click the Unconfigured capacity radio button, then click the Next button.
2. On the Create Snapshot Virtual Disks - Specify Capacity screen, choose a RAID level, then click the Next button.
To create the snapshot virtual disk from free capacity:

1. Click the Free capacity radio button.
2. Select a free capacity node, then click the Next button.
12. On the Create Snapshot Virtual Disks - Specify Repository Virtual Disk Capacity screen, enter how much space you want to allocate for the snapshot repository
virtual disk in the Specify capacity box, then click the Next button.
13. In the Notify me when the repository disk becomes x% full box, specify at what percentage MDSM should consider the snapshot repository virtual disk to be full.
14. Specify what should happen if the snapshot repository virtual disk becomes full.
Click the Fail the snapshot virtual disk radio button to leave the source disk available.
Click the Fail writes to the source virtual disk radio button to leave the snapshot virtual disk available and stop data from writing to the source virtual disk.
15. Choose whether to map the virtual disk to a host or host group now or later.
To map now, click the Map now radio button, select a host or host group by clicking it, then assign a virtual disk.
To map later, click the Map later radio button.
16. Click the Finish button to create the snapshot virtual disk and the associated snapshot repository virtual disk.
17. After you have created one or more snapshot virtual disks, mount or reassign a drive letter of the source virtual disk.
18. If needed, assign host-to-virtual disk mapping between the snapshot virtual disk and the host operating system that accesses it.
19. If you are using a Linux-based system, run the hot_add utility to register the snapshot virtual disk with the host operating system.
Specifying Snapshot Virtual Disk Names
Choose a name that helps you associate the snapshot virtual disk and snapshot repository virtual disk with its corresponding source virtual disk.
By default, the snapshot name is shown in the Snapshot virtual disk name field as:
<source-virtual disk-name>-<sequence-number>
where sequence-number is the chronological number of the snapshot relative to the source virtual disk.
The default name for the associated snapshot repository virtual disk that is shown in the Snapshot repository virtual disk field is:
<source-virtual disk-name>-R<sequence-number>
For example, if you are creating the first snapshot virtual disk for a source virtual disk called Accounting, the default snapshot virtual disk is Accounting-1, and the
associated snapshot repository virtual disk default name is Accounting-R1. The default name of the next snapshot virtual disk you create based on Accounting is
Accounting-2, with the corresponding snapshot repository virtual disk named as Accounting-R2 by default.
Whether you use the software-supplied sequence number that (by default) populates the Snapshot virtual disk name or the Snapshot repository virtual disk name field, the
next default name for a snapshot or snapshot repository virtual disk still uses the sequence number determined by the software. For example, if you give the first snapshot
of source virtual disk Accounting the name Accounting-8, and do not use the software-supplied sequence number of 1, the default name for the next snapshot of
Accounting is still Accounting-2. 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.
After you reach this limit in either the Snapshot virtual disk name or the Snapshot repository virtual disk name fields, the source virtual disk name is truncated enough to
append the sequence string.
Snapshot Repository Capacity

If you receive a warning that the capacity for the snapshot repository virtual disk is approaching its threshold, you can increase the capacity of a snapshot repository virtual
disk by using one of these methods:
• Use the free capacity available on the disk group of the snapshot repository virtual disk.
• Add unconfigured capacity to the disk group of the snapshot repository virtual disk. Use this option when no free capacity exists on the disk group.
You cannot increase the storage capacity of a snapshot repository virtual disk if the snapshot repository virtual disk has any one of these conditions:
• The virtual disk has one or more hot spares in use.

• The virtual disk has a status other than Optimal.
• Any virtual disk in the disk group is in any state of modification.
• The controller that has ownership of this virtual disk is currently adding capacity to another virtual disk. Each controller can add capacity to only one virtual disk at a
time.
• No free capacity exists in the disk group.
• No unconfigured capacity is available to add to the disk group.
To expand the snapshot repository virtual disk from MDSM:
1. Click the Modify tab, then click the Modify snapshot virtual disks link.
2. Click the Expand Snapshot Repository link.
3. Click the snapshot repository virtual disk you want to expand.
4. If necessary, you can add free capacity to the volume group by adding an unassigned physical disk. To add an unassigned physical disk:
1. Click the Add Drives button.
2. Select the capacity to add from the drop-down menu.
3. Click the Add button.

5. Enter the amount by which you want to expand the snapshot repository virtual disk in the Increase capacity by field
Click the Finish button to expand the capacity of the snapshot repository virtual disk.
Reusing Snapshot Virtual Disks
NOTE:
Before you create a new point-in-time image of a source virtual disk, stop any data access (I/O) activity and remove the drive letter of the associated virtual disk.
Disabling a Snapshot Virtual Disk
Disable a snapshot virtual disk when you:
• Do not need the snapshot now, but may again soon.

• Intend to re-create the snapshot at a later time and want to retain the associated snapshot repository virtual disk so that you do not need to create it again.
• Want to maximize storage array performance by stopping copy-on-write activity to the snapshot repository virtual disk.
The SMdevices utility displays the snapshot virtual disk in its output, even after the snapshot virtual disk is disabled.
To disable a snapshot virtual disk:
2. Click the Disable Snapshot Virtual Disks link.
3. Highlight the snapshot virtual disk to be disabled and click the Disable button beneath the list.
4. In the Confirm Disable Snapshot Virtual Disk dialog box, type yes and then click the OK button.
The snapshot virtual disk is disabled. The associated snapshot repository virtual disk does not change status, but copy-on-write activity to the disabled snapshot virtual disk
stops until the snapshot virtual disk is re-created.
Re-creating a Snapshot Virtual Disk
NOTE:
This action invalidates the current snapshot.
1. Click the Summary tab, then click the Disk Groups & Virtual Disks link to ensure that the snapshot virtual disk is in Optimal or Disabled status.
2. Follow any additional instructions needed for your operating system. Failure to follow these additional instructions can create unusable snapshot virtual disks.
4. Click the Re-create Snapshot Virtual Disks link.
5. Highlight the snapshot virtual disk to re-create and click the Re-Create button beneath the list.
6. In the Confirm Snapshot Virtual Disk Re-Creation dialog box, type yes and then click the OK button.
Re-creating a snapshot repository virtual disk uses the previously configured snapshot name and parameters.

Premium Feature - Snapshot Virtual
Disk
Premium Feature - Virtual Disk Copy

The Premium Feature Activation card is shipped in the same box as the MD3000 / MD3000i Storage Array. The customer should follow the directions on the card to obtain
a key file and to enable the feature.
Here is a sample of the card; click to enlarge:
This is a
thumbnail
image of a
sample
Virtual Disk
Virtual Disk Copy

When you create a virtual disk copy, you create a copy pair that has a source virtual disk and a target virtual disk on the same storage array. The source virtual disk is the
virtual disk that contains the data you want to copy. The source virtual disk services the host I/O read activity and stores the data until it is copied to the target virtual disk.
After the virtual disk copy is complete, the source virtual disk becomes available to host applications for write requests.
The source virtual disk can be a standard virtual disk, a snapshot virtual disk, or the source virtual disk of a snapshot virtual disk. When you start a virtual disk copy, all
data is copied to the target virtual disk, and the source virtual disk permissions are set to read-only until the virtual disk copy is complete.
NOTE:
The preferred method for creating a virtual disk copy is to copy from a snapshot virtual disk. This allows the original virtual disk used in the snapshot operation to
remain fully available for read/write activity while the snapshot is used as the source for the virtual disk copy operation.
Source Virtual Disk

When you create a virtual disk copy, a copy pair consisting of a source virtual disk and a target virtual disk is created on the same storage array. When a virtual disk copy is
started, data from the source virtual disk is copied completely to the target virtual disk.

Target Virtual Disk

When you start a virtual disk copy, the target virtual disk begins to build a copy of the data on the source virtual disk. You can choose whether to use an existing virtual
disk or create a new virtual disk as the target virtual disk. If you choose an existing virtual disk as the target, all data on the target is overwritten. A target virtual disk can be
a standard virtual disk or the source virtual disk of a failed or disabled snapshot virtual disk.
NOTE:
The target virtual disk capacity must be equal to or greater than the source virtual disk capacity.
When you begin the disk copy process, you must define the rate at which the copy is completed. Giving the copy process top priority will slightly impact I/O performance,
while giving it lowest priority will make the copy process take longer to complete. You can modify the copy priority while the disk 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. An attempt to directly create a virtual disk copy for an MSCS shared disk, rather than using a snapshot virtual disk, will fail with the following
error: The operation cannot complete because the selected virtual disk is not a source virtual disk candidate.
When creating a snapshot virtual disk, map the snapshot virtual disk to only one node in the cluster. Mapping the snapshot virtual disk to the host group or both nodes in the
cluster may cause data corruption by allowing both nodes to concurrently access data.
Virtual Disk Read/Write Permissions

After the virtual disk copy is complete, the target virtual disk automatically becomes read-only to the hosts. The target virtual disk rejects read and write requests while the
virtual disk copy operation has a status of Pending or In Progress or if the operation fails before completing the copy. Keep the target virtual disk Read-Only enabled if you
want to preserve the data on the target virtual disk for reasons such as the following:
• If you are using the target virtual disk for backup purposes.
• If you are using the data on the target virtual disk to copy back to the source virtual disk of a disabled or failed snapshot virtual disk.
If you decide not to preserve the data on the target virtual disk after the virtual disk copy is complete, change the write protection setting for the target virtual disk to
Read/Write.
Follow these steps to set the target virtual disk read/write permissions:
1. Click the Modify tab, and then click the Manage Virtual Disk Copies link.
2. Select one or more copy pairs in the table and click the Permissions button to the right of the table.
The Set Target Virtual Disk Permissions dialog box appears.
3. In the Set Target Virtual Disk Permissions dialog box select either Read-Only or Read/Write.
4. Click the OK button in the dialog box.
If you select Read-Only, write requests to the target virtual disk will be rejected. If you select Read/Write, the host can read and write to the target virtual disk after the
virtual disk copy is complete.
Virtual Disk Copy Restrictions

Restrictions apply to the source virtual disk, the target virtual disk, and the storage array. Before you perform any virtual disk copy tasks, adhere to these restrictions:
NOTE:
Before migrating a Virtual Disk Copy Disk Group to another array, enable the required premium features on the destination storage array. If a disk group is migrated
from a storage array that has a premium feature enabled and the destination array does not have the feature enabled, an Out of Compliance error message can be
generated. For specific procedures to correct the error, refer to the Recovery Guru.
• While a virtual disk copy has a status of In Progress, Pending, or Failed, the source virtual disk is available for read I/O activity only. After the virtual disk copy is
complete, read and write I/O activity to the source virtual disk are permitted.
• A virtual disk can be selected as a target virtual disk for only one virtual disk copy at a time.
• A virtual disk with a Failed status cannot be used as a source virtual disk or target virtual disk.
• A virtual disk with a Degraded status cannot be used as a target virtual disk.
• A virtual disk participating in a modification operation cannot be selected as a source virtual disk or target virtual disk. Modification operations include:
◦ Capacity expansion
◦ RAID-level migration
◦ Segment sizing
◦ Virtual disk expansion
◦ Defragmenting a virtual disk
Creating a Virtual Disk Copy

Use the Create Virtual Disk Copies feature on the Configure tab to create a full copy of a source virtual disk. This operation overwrites any existing data on the target
virtual disk. Once the virtual disk copy has started, all I/O activity to the source virtual disk is read-only. Any attempts to write to the source virtual disk fail until the
operation is complete.
1. Before you create a full copy of a source virtual disk, stop any data access (I/O) to the source virtual disk and the target virtual disk so that the source virtual disk has
a stable version of the data to be copied.
2. If the host to which the source virtual disk is mapped is running Windows:
1. Remove the drive letter from the target virtual disk (assuming the target virtual disk has previously been assigned a drive letter).
2. Run the SMrepassist utility on the host where the snapshot virtual disk is mounted to flush all the write buffers from the new physical disk. At the host prompt,
type SMrepassist -f <filename-identifier> and press <Enter>.
The write buffers for the physical disk are flushed.
3. If the host to which the source virtual disk is mapped is running Linux and the target virtual disk is mounted, dismount the target virtual disk.
4. Click the Configure tab, then click the Create Virtual Disk Copies link.
5. On the Select Source Virtual Disk page, select the virtual disk to copy (source virtual disk), and click Next.
NOTE:
If the virtual disk you select is not valid, an information dialog box appears explaining the types of virtual disks you can use as the source for a virtual disk
copy. Click the OK button to close this dialog box and select a different source virtual disk.

6. Choose the target virtual disk:

1. To use an existing virtual disk as the target, click the Use an existing virtual disk radio button and highlight the virtual disk of your choice in the list.
NOTE:
If you select a target virtual disk with a capacity similar to the source virtual disk, you reduce the risk of having unusable space on the target virtual disk
after the virtual disk copy is completed.
2. To create a new virtual disk for the target, click the Create a new virtual disk radio button. Type a name for this new target virtual disk in the text box.
7. Click the Next button at the bottom of the page.
8. Set the copy priority for the virtual disk copy and click the Next button. The source virtual disk, the target virtual disk, and the copy priority setting that you selected
appear on the Create virtual disk copies-Confirm Copy Settings dialog. The higher priorities allocate more resources to the virtual disk copy at the expense of the
storage array's performance.
9. If you approve of the parameters, type yes in the text box and click Finish to confirm the copy settings and start the virtual disk copy.
The Copy Started page appears, verifying that the virtual disk copy has started. This dialog also enables you to exit the Create virtual disk copies feature or create
another new virtual disk copy.
10. Based on whether you want to create another virtual disk copy or modify the one you just created, choose:
◦ Yes - Create a new virtual disk copy.
◦ No - Exit the Create virtual disk copies dialog.
◦ Manage Virtual Disk Copies - Recopy, stop the copy process, set permissions or priority, or remove virtual disk copies.
You can view the progress of a virtual disk copy in the Manage virtual disk copies page. For each copy operation in progress, the list displays a sliding scale in the Status
field showing the percentage of the operation that is complete. Once the virtual disk copy is complete, do this:
1. In Linux, if you created the target virtual disk with unconfigured capacity, run the hot_add utility.
2. If you created the target virtual disk with unconfigured capacity, you map the virtual disk to a host in order to use it.
3. Register the target virtual disk with the operating system before using the new virtual disk:
1. Enable write permission on the target virtual disk by either removing the virtual disk copy pair or explicitly setting write permission.
2. In Windows, assign a drive letter to the virtual disk.
3. In Linux, mount the virtual disk.
4. Enable I/O activity to the source virtual disk and the target virtual disk.
Setting Copy Priority

The Copy Priority setting defines how much of the storage array's resources are used to complete a virtual disk copy, rather than to fulfill I/O requests. Changing the copy
priorities sets the rate at which a virtual disk copy is completed. Five copy priority rates are available: lowest, low, medium, high, and highest.
You can change the copy priority for a virtual disk copy in the following circumstances:
• Before the virtual disk copy begins.

• While the virtual disk copy is in progress:
Click the Modify tab, then click the Manage Virtual Disk Copies link. Select an active copy operation, then click the Priority button to the right of the list of virtual
disk copies.
• When re-creating a virtual disk copy:
Click the Modify tab, then click the Manage Virtual Disk Copies link. Select a completed copy operation, then click the Re-copy button to the right of the list of
virtual disk copies.
Stopping a Virtual Disk Copy

You can stop a virtual disk copy operation that has an In Progress status, a Pending status, or a Failed status. Stopping a virtual disk copy that has a Failed status clears the
Needs Attention status displayed for the storage array.
When you stop a virtual disk copy, all mapped hosts have write access to the source virtual disk. If data is written to the source virtual disk, the data on the target virtual
disk no longer matches the data on the source virtual disk.
Follow these steps to stop a virtual disk copy:
1. Click the Modify tab, and then click the Manage virtual disk copies link.
2. Select the copy operation you wish to stop by clicking it and click the Stop button.
You can only select one copy operation at a time to be stopped.
3. Click Yes to stop the virtual disk copy.
Recopying a Virtual Disk

You can recopy a virtual disk when you have stopped a virtual disk copy and you want to start it again or when a virtual disk copy has failed. A recopy operation is simpler
to start than beginning again with selecting the target virtual disk. The Recopy option overwrites existing data on the target virtual disk and makes the target virtual disk
read-only to hosts. This option fails all snapshot virtual disks associated with the target virtual disk, if any exist. Follow these steps to start a recopy operation:
You can only select one copy operation at a time to be recopied.
2. Select the copy operation in the list displayed by the Manage Virtual Disk Copies page, and then click the Recopy button at the right of the list.
3. The Recopy dialog box appears. Set the copy priority.
4. Type yes, and then click OK.
Removing Copy Pairs

Removing copy pairs does not delete the data on the source virtual disk or target virtual disk. This merely breaks the copy relationship between the two virtual disks.
Removing copy pairs permanently removes any virtual disk copy-related information for the source virtual disk and target virtual disk in the Virtual Disk Properties and the
Storage Array Profile dialogs. Removing a virtual disk copy also permanently removes the Read-Only attribute for the target virtual disk.
When you remove a virtual disk copy from the storage array, the target write attribute for the target virtual disk is also removed. If the virtual disk copy is in "In Progress"
status, you must stop the virtual disk copy before you can remove the copy pair.
Follow these steps to remove a copy pair:

2. Select one or more copy pairs in the table, and click Remove.
The Remove Copy Pairs dialog appears.
3. Click Yes to remove the copy pair.

Expires 2/3/2011 12:22:48 PM Premium Feature - Virtual Disk Copy This document is Dell Confidential
Premium Feature Recovery Procedures

If a modification to the system or hardware renders a Premium Features Key unusable, then the following procedure should be followed to regain the use of those features.
The steps needed are the same as those for originally installing the feature keys.
You will need the Feature Activation Code from the Product Feature Key Booklet, the Service tag number, and the Feature Enable Identifier. You can find these items in
the Modular Disk Storage Manager console for the array on which you wish to install the Virtual Disk Copy feature. They can be reached from the View/enable premium
features link in the Tools tab.
Follow these steps to recover the license key for premium features:
1. Verify that your Modular Disk Storage Array is connected to the server and powered up, and that MDSM software is installed on your management server.
2. Go to http://www.md-storage.com/ (website owned by LSI, Inc.) and follow the website instructions to download the premium key file. The premium key file must
be downloaded to your system.
NOTE:
Dell recommends that you enter your e-mail address so that a backup copy of your Premium Feature Key file is sent to you for your records.
3. Enable Snapshot and Virtual Disk Copy in the Modular Disk Storage Manager console.
1. Click the Enable a feature link.
2. Enter the key file as prompted.
3. Ensure that the screen is updated to indicate that Snapshot and Virtual Disk Copy are now enabled.
If Snapshot or Virtual Disk Copy ever becomes disabled, an alert will be generated and you can access the web site and repeat this process.

Premium Feature Recovery
Procedures
SMcli Overview - The Command Line Interface

The Script Engine
The script engine is a utility built into the MDSM software that allows you to issue commands that perform specific actions for managing a storage array or returning
information about the status of a storage array. You can enter individual commands, or run script files when you need to perform operations more than once (such as
installing the same configuration on several storage arrays). A script file can be loaded and run from the command line interface. You can also run commands in an
interactive mode. Interactive mode enables you to connect to a specific storage array and rapidly enter a command, determine the effect on the storage array, and then enter
a new command.
The engine processes commands that configure and monitor a Storage Array. It processes them one at a time. The user may access the script engine using the system
management command line interface (SMcli) utility at an operating system prompt.
NOTE:
The SMcli command is installed under the client directory of the selected path during a management station install of the MDSM software.
You can use the script language commands to define and manage all aspects of a storage array, such as host topology, virtual disk configuration, and controller
configuration. The actual number of commands is large.
NOTE:
If an array password is set, commands that request information from the array can be successfully issued without the password, but changes to the configuration must
be accompanied by the password.
You can use the command line interface to perform the following functions:
• Directly access the script engine and run commands in interactive mode or using a script file.
• Create script command batch files to be run on multiple storage arrays when you need to install the same configuration on different storage arrays.
• Run script commands on a storage array directly connected to a host, a storage array connected to a host by an Ethernet, or a combination of both.
• Display configuration information about the storage arrays.
• Add storage arrays to and remove storage arrays from the management domain.
• Perform automatic discovery of all storage arrays attached to the local subnet.
• Add or delete Simple Network Management Protocol (SNMP) trap destinations and email alert notifications.
• Specify the mail server and sender email address or SMTP (Simple Mail Transport Protocol) server for alert notifications.
• Direct the output to a standard command line display or to a named file.

Access Pathways to the Script Engine

WARNING:
The command line interface is capable of damaging a configuration and causing loss of data if not used properly. Commands run as soon as you enter them. Some
commands can immediately delete configurations or data. Before using the command line interface, make sure you have backed up all data and saved the current
configuration.
The two pathways to access the script engine are interactive and scripted.
Interactive Access
The scripting engine may be accessed interactively from the command prompt. If you enter SMcli and a storage array name but do not specify CLI parameters, script
commands, or a script file, the command line interface begins running in interactive mode. Interactive mode enables you to run individual commands without prefixing the
commands with SMcli. You can enter a single command, view the results, and enter the next command without typing the complete SMcli string. Interactive mode is useful
for determining configuration errors and quickly testing configuration changes.
NOTE:
There are several caveats which apply to interactive access. The most important of these are that it gives the user no acknowledgement as to the completion of an
operation, and there is no error checking or error handling. For this reason the routine use of the interactive method is discouraged and the scripted method should be
used instead.
Scripted Access
The table below lists the general form of some script language commands and provides a definition of each command.
Examples of Script Language Command Structure and Function

Syntax Description
create object statement-data Creates an object of the specified type
delete object Deletes a previously created object
clear object statement-data Removes a relationship from between objects.
set object statement-data

Changes object attributes. All changes
are completed when the command returns.
show object statement-data

Writes information about the object
to the standard output file.
Command Line Interface Updates

Users of the command line interface should note the following information:
• If configuration of the MD3000 storage array is cleared using the clear storagearray configuration command, restart all attached hosts prior to reconfiguring
the storage array.
• When using the command-line interface to create host ports, ensure that the host type is specified in the command. If no host is specified, the default host is Windows
2000/Server 20003 Non-Clustered.
• The SMcli -d parameter shows all storage arrays that are currently discovered.
Using the Interface

The following examples show how to enter CLI commands on a command line. The examples show the syntax, form, and, in some examples, script commands. Examples
are shown for both Windows and Linux operating systems. The usage for the -c parameter varies depending on your operating system. On Windows operating systems, put
quotation marks (" ") around the script command following the -c parameter. On Linux operating systems, put single quotation marks (' ') around the script command
following the -c parameter. In addition, the use of additional double quotes within the command string requires the use of an escape character. The escape character is the
backslash <\>
. Each time a double quote is used within the command string the escape character must accompany it.
This example shows how to change the name of a storage array. The original name of the storage array is Payroll_Array. The new name is Finance_Array. The array is
being addressed by its name with in-band management, indicated by the -n. In-band management requires that the management station that issues the command must have
a SAS connection to the array. Otherwise, the command would be issued out-of-band, using the IP address of one of the RAID Controller Modules.
Windows
SMcli -n "Payroll_Array" -c "set storageArray userLabel=\"Finance_Array\";"
Linux
SMcli -n 'Payroll_Array' -c 'set storageArray userLabel="Finance_Array";'
This example shows how to display all storage arrays in the current configuration. The command in this example returns the host name of each storage array. If you also
want to know the IP address of each storage array in the configuration, add the -i parameter to the command.
SMcli -d -i
The next example shows the command to reset the service tag on an MD3000 enclosure. The name of the array is TRNG01A, the password on the array is password, and
the new service tag is 6MNL42P. Again, the array name requires double quotes, so that the escape character < \ > must be used immediately before each double quote.
SMcli -n TRNG01A -p password -c "set enclosure [0] serviceTag=\"6MNL42P"\";


SMcli Overview - The Command
Line Interface
SMcli - Command Line Details

Command Line Details
The following command line examples have been used successfully to perform operations on a storage array. These examples are provided as detailed usage guidelines for
commands that are used in the setup, operation and maintenance of the MD3000i storage array.
WARNING:
The command line interface is capable of damaging a configuration and causing loss of data if not used properly. Commands run as soon as you enter them. Some
commands can immediately delete configurations or data. Before using the command line interface make sure you have backed up all data and saved the current
configuration.
Addressing the Host by IP Address, Hostname, and Array Name

Commands can be directed towards a storage array in three very different ways.
In-Band
When addressing an in-band command to the array with the -n prefix, the command is not controller specific as to which controller might own an addressed object. For
example, the script statement might be:
SMcli -n TRNG05A -c "show allVirtualDisks";
Where TRNG05A is the storage array's name as created in the management software. The command will be processed without regard to the controllers' ownership of
objects or their IP addresses.
Out-of-Band - IP Address
For example, to address a create virtualdisk command to a specific controller by its IP address (out-of-band), the owner= statement refers to the controller being
addressed by that IP address. If owner=0 is used in the create statement and the command is being addressed to controller 1's IP address, then the command will fail with
the following error.
Error 1011 - A management connection to the RAID controller module in slot 0 must be defined to
complete this operation.
Out-of-Band - Hostname
The array may also be accessed by addressing the storage array by an array name that is referenced in DNS or in the hosts file. In that instance, the entry will refer to one of
the controllers, but not to both. If an entry is made in the DNS table that references the array name (hostname) to the primary controller, then commands addressed to that
storage array using the DNS identity will be directed towards the primary controller. This will create problems when addressing a command that refers to objects owned by
the other controller.
Storage Array Commands

This example shows the command to show detailed information about a storage array. Because this information is so detailed, the example also shows how to output the
information to a file. The filename was chosen to include the name of the array, the date, and that it is a profile text file.
SMcli 192.168.128.101 -c "show storagearray profile;" -o c:\Dell\TRNG01A-11-11-06-profile.txt
Virtual Disk Commands

The following examples have been used successfully to create, display properties, and modify the virtual disks and disk groups and their properties.
Create Virtual Disk - User-Assigned Physical Disks

When you create a new virtual disk and assign the physical disks to use, the MD Storage Manager software creates a new disk group. The RAID controller module
firmware assigns a disk group number to the new disk group. The following syntax is the general form of the command:
create virtualDisk physicalDisks=(enclosureID0,slotID0...enclosureIDn,slotIDn)

raidLevel=(0 | 1 | 5) userLabel="virtualDiskName" [capacity=virtualDiskCapacity
owner=(0 | 1) segmentSize=segmentSizeValue]
A practical example of this syntax is as follows:
SMcli 192.168.128.101 -c "create virtualDisk physicalDisks=(0,0 0,1 0,2) raidLevel=5

userLabel=\"SQLDB01\" capacity=7305610 owner=0 segmentSize=64";
NOTE:
The previous command shows the command being addressed to Controller 0 and the assigned owner will be Controller 0. If the command is directed at Controller 0
and the virtual disk is created with the owner being Controller 1, the command will fail.
Overall LUN Status

The following command shows the status of the virtual disks, and can be quite lengthy depending on the number and type of virtual disks on the storage array:

SMcli 192.168.128.101 -c "show allVirtualDisks";
Status of an Individual Virtual Disk

In this case, the virtual disk query is regarding a snapshot virtual disk. The size of the virtual disk (13 GB) reflects the size of the source virtual disk and not the actual space
on disk of the snapshot.
SMcli -n TRNG55A -c "show virtualdisk [\"SQLDB-1\"]";

Performing syntax check...
Syntax check complete.
Executing script...
VOLUME DETAILS
Snapshot virtual disk name: SQLDB-1
Virtual Disk world-wide identifier:
60:01:88:b0:00:30:2e:dd:00:00:07:07:45:c2:fa:99
Creation timestamp: 2/2/07 10:04 AM
Capacity: 13 GB
Status: Optimal
Preferred owner: RAID Controller Module in slot 1
Current owner: RAID Controller Module in slot 1
Associated source virtual disk (standard): SQLDB
Associated snapshot repository virtual disk: SQLDB-R1
Script execution complete.
SMcli completed successfully.
Disable/Enable Read and Write Cache - All Virtual Disks

At the SMcli command prompt, use the following command structure to disable or enable read and write cache:
smcli 192.168.128.101 -c "set allVirtualDisks readCacheEnabled=FALSE writeCacheEnabled=FALSE;"
Disable/Enable the Controller Cache Mirror

Cache mirroring is a key high availability feature in the MD3000, whereby each controller caches not only its own queued data, but also that of its peer controller.
Disabling cache mirroring can cause data loss or corruption. In the event of the failure of a controller, there is no backup copy of the cached data in the alternate controller's
cache memory. As a result, when the alternate controller attempts to recover on behalf of the failed controller, it will not have a backup copy of what was in cache when the
controller failed. Because the data writes have already been committed at the host level, the data is lost.
WARNING:
This method of performance enhancement should be avoided in any situation wherein the data cannot be quickly and easily recovered from another source. Turning
off cache mirroring will allow conditions that can result in data loss.
WARNING:
All I/O to the storage array should be halted and the hosts taken offline for this procedure.
At the SMcli command prompt, use the following command structure to disable or enable the cache mirror: set (allVirtualDisks | virtualDisk ["virtualDiskName"]
|.virtualDisks ["virtualDiskName1" ... "virtualDiskNamen"] | virtualDisk <wwid>) mirrorCacheEnabled=(TRUE | FALSE)
smcli -n TRNG01A -c "set allVirtualDisks mirrorCacheEnabled=TRUE";
Restore/Recreate a Deleted Access LUN

If the access LUN is deleted it can be recreated with the following syntax:
SMcli -n TRNG01A -c "set accessVirtualDisk logicalUnitNumber=31 hostGroup=defaultGroup;"
Show Progress of a Virtual Disk Initialization

Progress of a virtual disk initialization can be seen from the command line by the use of the following command, where TEST is the case-sensitive name of the virtual disk.
NOTE:
The value shown will reflect the point in time of the command issued. To see progress over time the command must be re-issued each time an update is needed.
C:\>SMcli -n TRNG55A -c "show virtualdisk [\"TEST\"] actionProgress";

Executing script...
Virtual Disk TEST

Action: Initialization
Percent Complete: 31%
Disk Group Commands

Show Disk Group Properties
NOTE:
When making a disk query, the preferred method is to query the storage array name in-band. If the command fails when addressed to a specific RAID Controller
Module, it may not own the virtual disk. Repeat the command, directing the command to the other controller.
To show the properties of a disk group use the following command syntax:

smcli 192.168.128.101 -c "show diskGroup [1]";

SMcli 192.168.128.101 -c "show diskGroup [1]";
Executing script...
DISK GROUP 1 (RAID 5)
Disk group status: Online
Physical Disk type: Serial Attached SCSI (SAS)
Enclosure loss protection: No
Current owner: RAID Controller Module in slot 0,1
Associated virtual disks and free capacities:
VIRTUAL DISK NAME CAPACITY
RAID5-1 7 GB
WOW 5 GB
Free Capacity 123.733 GB
Associated physical disks (in piece order):
ENCLOSURE SLOT
0 0
0 1
0 2
Set a Disk Group Offline

To disable (offline) a disk group, in this case disk group 3, use the following command syntax:
SMcli 192.168.128.101 -c "set Diskgroup [3] availability=offline";
Physical Disk Commands

The following commands have been tested and found to work properly with regard to physical disks.
Initialize a Physical Disk

To initialize (clear) a physical disk of metadata, use the following command:
smcli 192.168.128.101 -c "start physicalDisk [0,6] initialize";
Manually Fail a Physical Disk

SMcli 192.168.128.103 -p password -c "set physicaldisk [0,9] operationalstate=failed";
Executing script...
Premium Features Commands

Disable a Premium Feature in Order to Remove Non-compliance
When a storage array becomes non-compliant for a premium feature, the ability to engage the Enable a Premium Feature link is not always available. To make the link
available, the premium feature must first be disabled at the command line. Use the following syntax to disable premium features:
SMcli 192.168.128.101 -c "disable storagearray feature=snapshot";
...and / or,
SMcli 192.168.128.101 -c "disable storagearray feature=virtualdiskcopy";
After the premium feature has been disabled the Enable a Feature link will appear which allows the user to reload the feature key file and restore normal operation.
Force a Refresh in MDSM

Force a refresh of the MDSM GUI by using the net stop and start commands from the Windows command prompt, as follows:
C:\net stop smagent

The Modular Disk Storage Manager Agent service was stopped successfully.
C:\net start smagent
The Modular Disk Storage Manager Agent service is starting.
The Modular Disk Storage Manager Agent service was started successfully.

Expires 2/3/2011 12:22:48 PM SMcli - Command Line Details This document is Dell Confidential

Clustering
Unless stated otherwise, reference to the Windows OS on this page implies either Windows® Server 2003 Enterprise, Windows® Server 2003 Enterprise x64 Edition, or
Windows® Server 2003 R2 Enterprise Edition.
NOTE:
Dell does not support upgrades from a non-redundant cluster configuration to a redundant configuration.
NOTE:
Majority Node Set (MNS) Quorum resource type is not supported on the MD3000i.
Cluster Storage Management Software

Recommended practice is that the storage management agent be installed on the cluster nodes and a separate management station be used to manage the cluster nodes.
MDSM Client
The software runs on the management station to centrally manage the Dell™PowerVault MD3000i RAID enclosures. You can use Dell™ PowerVault Modular Disk
Storage Manager (MDSM) to perform tasks such as creating or managing RAID arrays, binding virtual disks, and downloading firmware.
MDSM Agent
This software resides on each cluster node to collect server-based topology data that can be managed by the MDSM Client.
Multi-Path Software
Multi-path software (the failover driver) is software on each cluster node that provides management of the redundant data path between the server and the RAID enclosure.
For the multi-path software to correctly manage a redundant path, the configuration must provide for redundant data path NICs and redundant cabling. 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 an alternate path so that the storage array continues to operate without interruption. In a topology with redundant Ethernet switches
and redundant pathways to each switch from the host, and redundant paths from each switch to both controllers, the MPIO driver will be sending I/O through both NICs in
round-robin fashion. Failure of one Ethernet path at the host will cause MPIO to send all the data through the other NIC. Failure of both of the pathways to a single
controller will cause MPIO to reroute the data through the other controller.
Failback Mode
To set the correct failback mode on each cluster node, you must merge the MD3000i Stand Alone to Cluster.reg file located in the windows\utility directory of the Dell
PowerVault MD3000i Resource CD into the registry of each node. These registry files enable correct failback operation on the host.
NOTE:
If you uninstall and reinstall the multi-path I/O software or MDSM, you must merge the MD3000i Stand Alone to Cluster.reg file into the registry again.
NOTE:
If you are reconfiguring a cluster node into a stand-alone host, you must merge the MD3000i Cluster to Stand Alone.reg file located in the windows\utility directory
of the Dell PowerVault MD3000i Resource CD into the host registry.
Advanced Features
• Snapshot Virtual Disk - captures point-in-time images of a virtual disk for backups or testing without affecting the contents of the source virtual disk.
NOTE:
When you are creating a snapshot virtual disk, map the snapshot virtual disk to only one node in the cluster. Mapping the snapshot virtual disk to the host group
or both nodes in the cluster may allow both nodes to access data concurrently, causing data corruption.
• Virtual Disk Copy - generates a full copy of data from the source virtual disk to the target virtual disk in a storage array. You can use this feature to back up data,
copy data from disk groups that use smaller capacity physical disks to disk groups using greater capacity physical disks, or restore snapshot virtual disk data to the
NOTE:
When you attempt to create a virtual disk copy of an MSCS cluster shared disk directly, the operation fails and displays this error message: The operation
cannot complete because the selected virtual disk is not a source virtual disk candidate. To create a virtual disk copy for an MSCS cluster shared disk, create a
snapshot of the disk, and then use the snapshot virtual disk as the source for the virtual disk copy. When you create the snapshot virtual disk, do not map the
snapshot virtual disk to a cluster node.
When you use these advanced features in a redundant cluster configuration, the automatic failback feature is disabled by default. Therefore, when a failed component is
repaired or replaced, the virtual disk(s) do not automatically transfer to the preferred controller. You can manually initiate a failback using MDSM Client or the Storage
Management Command Line Interface (SMcli).
If the cluster of shared disks fails, restore it from the target virtual disk, using one of these methods:
• Use Virtual Disk Copy to transfer the data from the target virtual disk back to the cluster shared disk.
• Un-assign the clustered shared disk from the host group and map the target virtual disk to the host group.
NIC Teaming
Network Interface Card (NIC) teaming combines two or more NICs to provide load balancing and/or fault tolerance. Dell supports cluster NIC teaming, but only in a public
network. NIC teaming is not supported in a private network. Use the same brand of NICs in a team, and do not mix brands of teaming drivers. NIC teaming is not supported
on host iSCSI initiators connecting to the MD3000i.

Configuring the System for Shared Storage

Configuring Host Access
1. Ensure that the Modular Disk Storage Manager Agent service is started on your cluster nodes.
2. Click the Configure tab and then click the Configure Host Access link to begin configuring host access. MDSM scans the array and displays a list of the hosts it
finds that have not yet been configured for access to the array.
3. Click View Hosts to see hosts that have already been configured.
To automatically configure a host for access to the storage array:
1. Click the Configure tab and then click the Configure Host Access link.
2. Select both the cluster nodes individually, or by clicking the Select All check box beneath the list.
3. Set the Host Type on each cluster node. Click the View Details button (next to the list) and choose the appropriate host type. For a non-redundant cluster host
configuration, select Windows MSCS Cluster - Single Path. For a redundant configuration with dual iSCSI initiators, select Windows 2000/Server 2003
Clustered.
4. Click OK to configure access to the array for the hosts you selected.
Creating a Host Group

1. On the Modify tab, click Modify Host Topology.
2. On the Modify Host Topology page, click Create Host Group.
3. On the Create Host Group page, type a name for the new host group in the text box.
4. In the Select Hosts to Add list, click the names of the first cluster node, and then click Add to the right of the list. The host moves to the Hosts in Group list.
5. Repeat Step 4 to add the second cluster node to the host group.
6. Click OK to create the host group.

Expires 2/3/2011 12:22:48 PM Clustering This document is Dell Confidential
Overview
The MD3000i Configuration Utility provides a consolidated approach for configuring MD3000i storage arrays and iSCSI host servers via a single wizard-driven interface.
The MD3000i Configuration Utility is available from the MD3000i Resource CD or as a standalone application that can be downloaded from http://www.support.dell.com/.
MD3000i Configuration Utility Requirements

• MD3000i Firmware v.06.50.32.60
• Administrative privileges for Windows
• Root privileges for Linux
• Host configuration on Windows based systems requires the Microsoft iSCSI initiator
• Host configuration requires the multi-path driver that is installed by either the "Host" or "Full" installation option of MDSM.
Supported Operating Systems

The MD3000i configuration utility is supported on the following operating systems
• Windows Server 2008 x64 Standard Edition

• Windows Server 2003 x64 Enterprise Edition R2
• Windows Server 2003 Enterprise Edition R2
• Windows Server 2003 x64 Standard Edition R2
• Windows Server 2003 Standard Edition R2
• Windows Server 2003 x64 Enterprise Edition
• Windows Server 2003 Enterprise Edition
• Windows Server 2003 Standard Edition
• Windows Server 2003 x64 Windows Storage Server
• Windows Server 2003 Windows Storage Server 32bit
• Enterprise Linux 4 x86
• Enterprise Linux 4 x86_64
• Enterprise Linux 5 x86
• Enterprise Linux 5 x86_64
• SuSE Linux ES 10 x86_64
• SuSE Linux ES 9 x86_64

Expires 2/3/2011 12:22:48 PM Overview This document is Dell Confidential

Launching the Utility

This procedure outlines the steps required to launch the MD3000i Configuration Utility from the Resouce CD. The utility is available on version 1.4 or later of the
MD3000i resource CD.
NOTE:
The primary means of launching the utility is from the menu presented from the Resource CD. However, there is also an MDconfig.bat file (Windows) and an
MDconfig.sh file (Linux), in the root of the Resource CD, that can launch the utility directly.
MD3000i Configuration Utility

1.
Insert the MD3000i Resource CD.
2.
Choose the MD3000i Configuration Utility option.
This is an image of the MD3000i Resource

CD.
3.
The initial configuration screen is displayed.
This is an image of the initial MDCU

screen.
4.
Once the wizard is launched, the MD3000i storage array and associated host servers can be configured.

Expires 2/3/2011 12:22:48 PM Launching the Utility This document is Dell Confidential
Array Configuration
Storage Array Configuration Overview
The overall process for storage array configuration using the MD3000i Configuration Utility is outlined in the following steps.
• Configure one or more MD3000i storage arrays

• Select a method to discover the storage arrays that are available for configuration
• Choose a storage array to configure
• Set a storage array name and password
• Configure the IP protocols and addresses for the iSCSI ports
• Configure the IP addresses for the management ports
• Specify the CHAP authentication method
• Apply the settings after reviewing a summary
• Save the configuration to a file for use when configuring hosts
NOTE:
In order to configure the storage array, the configuration utility requires network access to the management ports of the MD3000i. This means you must have a
properly functioning network infrastructure before you attempt to configure your storage array.
MD3000i Array Configuration

1.
The initial Confiuration Task screen displays three options;
• Array Configuration
• Host Configuration
• Update Configuration File
To configure the MD3000i storage array, choose Configure MD3000i.
This is an image of the MD3000i Configuration

Wizard.
2.
If you use another utility such as Modular Disk Storage Manager to modify the iSCSI connectivity settings of your storage array after the initial configuration
process, you can update the configuration files this utility generated with the most recent settings by using Update Configuration File option.
The Update Configuration File option is a manual method to synchronize the MD3000i configuration file with the physical MD3000i configuration, after the
physical MD3000i configuration has been updated by another tool such as Modular Disk Storage Manager.


3.
The Discover Storage Arrays screen is a continuation of the Obtain Available Storage Arrays screen. If you previously chose to discover new arrays instead of
loading them from a file or locating them from an iSCSI port, you will be presented with this screen.
To discover available storage arrays choose Discover New Arrays.

Wizard.
4.
Automatic discovery will query the local sub-network for all MD3000i storage arrays and may take several minutes to complete.
Manual discovery allows you to locate MD3000i storage arrays that are outside of the local sub-network. Manual discovery requires selecting whether your storage
array has a single controller (simplex) or dual controllers (duplex).
To perform an automatic discovery of storage arrays within the local subnet choose Automatic.
This is an image of the MDCU

screen.
5.
The Storage Array Configuration screen presents a list of all MD3000i storage arrays that were obtained from the discovery process. The Add and Remove buttons
can be used to modify the contents of the list. This is particularly useful to add arrays from multiple configuration files or to remove arrays you are not interested in
configuring.

screen.
6.
The Storage Array Name and Password screen prompts you to provide a name for your MD3000i storage array and provides the opportunity to specify an array
password. If you are setting up the storage array for the first time, there will not be an existing password.
An uninitialized storage array will have a default name of "Unnamed." Each storage array should be given a unique name, the maximum name length is 30
characters and can consist of letters, numbers, and the special characters underscore (_), minus (-), and pound sign (#). No other special characters are permitted.
MD3000i storage arrays can be configured with a password that will be required to modify their settings. For security reasons, a storage array will enter a "lockout"
state for 10 minutes if you fail to provide the correct password for ten attempts. The maximum password length is 30 characters.

screen.
7.
The iSCSI ports on your storage array support two protocols; IPv4 and IPv6. The management ports only support IPv4. Each protocol may be configured
automatically or manually.
8.
There must be a DHCP server available to receive the request and assign IP addresses. If there is not a DHCP server on your network, you will need to configure the
IP addresses manually.
Unlike IPv4, IPv6 has a built-in mechanism for devices to automatically configure themselves. Due to this capability, your storage array will automatically have a
local IP address assigned regardless of your choice for automatic configuration. This local IP address is not routable. Autoconfiguration is a process that allows your
storage array to communicate with the routers on your network to automatically configure routable and router IP addresses. It is typical for your storage array to
have multiple IPv6 addresses.

screen.
9.
Each management port that needs to be configured with an IP address will display the IPv4 Port Configuration screen. In addition to a text prompt with the name of
the port being configured, a diagram illustrating the management port is also shown.
You will only be prompted to enter an IP addresses if you previously chose to manually configure the management port.

screen.
10.
As you progress through the management ports, the diagram will update to reflect the IP addresses for the ports you have already entered.

screen.
11.
Each iSCSI port can be configured with an automatic or manual IP address.

screen.
12.
Controller 0 IN 0 is the first port to be configured.

screen.


13.
As you progress through the iSCSI ports, the diagram will update to reflect the IP addresses for the ports you have already entered.
Controller 0 IN 1 is the second port to be configured.

screen.
14.
Controller 1 IN 0 is the third port to be configured.

screen.
15.
Controller 1 IN 1 is the fourth port to be configured.

screen.
16.
The iSCSI ports can be manually configured with IPv6 addresses.

screen.
17.
If the iSCSI ports are configured with manual IPv6 addresses the iSCSI Port Configuration Screen is displayed twice for every iSCSI port; once for configuring an
IPv4 address and a second time for configuring an IPv6 address.

screen.
18.
Each port that needs to be configured with an IPv6 address will present the IPv6 Port Configuration screen. The Local IP address field may not be changed. You will
only be prompted to enter an IPv6 addresses if you previously chose to manually configure the port.

screen.
19.
CHAP (Challenge Handshake Authentication Protocol) is an optional iSCSI authentication method where the storage array (target) authenticates iSCSI initiators on
the host servers. Two types of CHAP are supported - target CHAP and mutual CHAP.
In target CHAP, the storage array authenticates all requests for access issued by the iSCSI initiator(s) on the host server(s) via a CHAP secret. To set up target
CHAP authentication, you enter a CHAP secret on the storage array, then configure each iSCSI initiator on the host server(s) to send that secret each time it attempts
to access the storage array. The target CHAP method will be used if you choose to configure CHAP with this utility. The length must be a minimum of 12 characters
and a maximum of 16 characters. The CHAP secret must use ACSII code characters with a decimal value between 32 and 126.

screen.
20.
Mutual CHAP requires the storage array to send a secret that is different than the target secret back to the iSCSI initiator. This is an advanced configuration option
and will require further setup outside the scope of MD3000i Configuration Utility.
21.
The summary screen provides you with an opportunity to review the settings you specified for the storage array in a consolidated manner before applying them.
After applying the configuration, you will no longer be able to go back and make changes for this array without restarting the process from the Select Storage Array
screen.

screen.
22.
The Save Configuration screen provides the opportunity to save the settings you specified for the storage array.
This option saves the settings you specified for an MD3000i storage array into a configuration file of your choice. These configuration files are primarily used to
expedite the host configuration process, but they may be also used to restore your storage array's iSCSI configuration.

screen.
23.
In order to have the configuration for all storage arrays easily available when you configure your hosts, Dell recommends that you save all storage arrays into a
single file by using the Append Configuration to Existing File option on the Save Configuration screen.
Dell also recommends that you save the configuration files generated during this process to a location that can be accessed from all hosts, such as a network share or
removable storage, so the MD3000i Configuration Utility can use the information to assist in the host configuration process.

screen.


24.
The Configure Additional Arrays screen provides the opportunity to configure addtional MD3000i storage arrays.

screen.
25.
The Configure Host Connectivity screen provides the opportunity to configure host server access to the MD3000i storage array.

screen.
26.
Once the array configuration has been completed the Configuration Utility displays the Finished screen.

screen.
27. NOTE:
If the MD3000i Configuration Utility fails to complete the required configuration, the Modular Disk Storage Management tool can be used to configure the
MD3000i Storage array.

Expires 2/3/2011 12:22:48 PM Array Configuration This document is Dell Confidential
Host Configuration
After you have completed configuring the MD3000i storage array, the next task is to run the MD3000i Configuration Utility on all hosts that will need to access the storage
arrays. It is not necessary to have a configuration file generated from the MD3000i configuration process, but having one can simplify the host configuration process.
Host Configuration Overview

The overall process for iSCSI initiator configuration using the MD3000i Configuration Utility is outlined in the following steps.
• Configure one or more hosts that will access the array(s)

• Select a method to obtain available storage arrays for connection
• Choose a storage array to connect to
• Specify the CHAP secret
• Select the iSCSI ports the host's initiator will use to login
• Repeat the process to connect to additional arrays
• Repeat these steps on each host that needs access to the storage array(s)
NOTE:
The option to configure a host will be disabled if the machine the utility is running on does not have an iSCSI initiator or the required driver components installed.
MD3000i Host Configuration

1.
To configure the host iSCSI initiator, choose Configure Host.

Wizard.
2.
The Load Saved Configuration option allows you to load MD3000i configuration information that has been previously saved using this utility.
The Discover New Arrays option allows you to discover storage arrays by connecting to the MD3000i management ports.
The Enter iSCSI Port IP Adress option allows you to enter one of the IP addresses of an MD3000i storage array's iSCSI ports, if the host does not have access to
the management ports nor a configuration file.
The configuration file that was saved during the MD3000i Array configuration can now be used, choose Load Saved Configuration and point the wizard to the
location of the previously saved .xml configuration file.

Wizard.
3.
The Storage Array Connection screen provides the opportunity to select a storage array for the host initiator to connect to.

screen.


4.
The Target Authentication screen provides the opportunity to configure target authentication on the host initiator if CHAP has been configured on the MD3000i
storage array.

screen.
5.
The Storage Array Login screen provides the opportunity to specify which ports on the MD3000i the initiator should log in to.

screen.
6.
The Connect to Additional Arrays screen provides the opportunity to configure connections to addtional MD3000i storage arrays.

screen.
7.
Once the host configuration has been completed the Configuration Utility displays the Finished screen.

screen.
8. NOTE:
If the MD3000i Configuration Utility fails to complete the required configuration, the host operating system can be used to configure the host initiator
connection.

Expires 2/3/2011 12:22:48 PM Host Configuration This document is Dell Confidential
Disk Operations and Maintenance

Virtual Disk Operations
The MD3000 / MD3000i RAID controllers perform several different routine disk maintenance operations to ensure the consistency of data on the physical disks.
Virtual Disk Initialization

Every virtual disk must be initialized. Up to four concurrent initializations can occur for the same RAID controller module.
Foreground Initialization
The RAID controller module firmware supports full foreground initialization for virtual disks. All access to the virtual disk is blocked during the initialization
process. During initialization, zeros (0x00) are written to every sector of the virtual disk. The virtual disk is available after the initialization is completed without
requiring a RAID controller module restart.
Background Initialization
The RAID controller module executes a background initialization when the virtual disk is created to establish parity, while allowing full host access to the virtual
disks. Background initialization does not run on RAID 0 virtual disks. The background initialization rate is controlled by MD Storage Manager. You must stop an
ongoing background initialization before you change the rate, or the rate change will not take effect. After you stop background initialization and change the rate, the
rate change will take effect when the background initialization restarts automatically.
NOTE:
Unlike initialization of virtual disks, background initialization does not clear data from the physical disks.
Consistency Check
A consistency check verifies the correctness of data in a redundant array (RAID levels 1, 5, and 10). For example, in a system with parity, checking consistency
means 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.
NOTE:
Dell recommends that you run data consistency checks on a redundant array at least once a month. This allows detection and automatic replacement of
unreadable sectors. Finding an unreadable sector during a rebuild of a failed physical disk is a serious problem, since the system does not have the redundancy
to recover the data.
Storage Array Media Scan

The media scan is a long-running operation that examines virtual disks to verify that data is accessible. The process finds media errors before normal read and write
activity is disrupted and reports errors to the event log. The RAID controller module uses the Read operation to perform verification on the space configured in
virtual disks and the space reserved by the controller for the metadata.

Errors discovered by the media scan include:
• Unrecovered media error - Data could not be read on the first attempt or on any subsequent attempts. For virtual disks with redundancy protection, data is
reconstructed, rewritten to the physical disk, and verified and the error is reported to the event log. For virtual disks without redundancy protection (RAID 0
virtual disks and degraded RAID 1 and RAID 5 virtual disks), the error is not corrected but is reported to the event log.
• 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 ten redundancy mismatches 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. For example, redundancy information
cannot be used to reconstruct the data on a degraded virtual disk. The error is reported to the event log.
Cycle Time
The media verification operation runs only on selected disk groups, independent of other disk groups. Cycle time is how long it takes to complete verification of the
metadata region of the disk group and all virtual disks in the disk group for which media verification is configured. The next cycle for a disk group starts
automatically when the current cycle completes. You can set the cycle time for a media verification operation between 1 to 30 days. The firmware throttles the
media verification I/O accesses to disks based on the cycle time.
The RAID controller module tracks the cycle for each disk group independent of other disk groups on the controller and creates a checkpoint. If the media
verification operation on a disk group is preempted or blocked by another operation on the disk group, the firmware resumes after the current cycle. If the media
verification process on a disk group is stopped due to a RAID controller module restart, the firmware resumes the process from the last checkpoint.
Changing Media Scan Settings
1. Click the Tools tab, then click the Change Media Scan Settings link.
2. Select the number of days allowed for the media scan to complete in the Scan duration (days) box.
NOTE:
Performing the media scan frequently may negatively impact the performance of other operations. Adjust scan duration based on the performance needs
of your storage array.
3. In the Select virtual disks to scan box, click the virtual disk you want to include in the media scan.
NOTE:
Press <Ctrl> and click to add more than one virtual disk to the media scan. Click the Select All button to include all virtual disks in the media scan.
4. Check the Scan selected virtual disks option box to enable scanning, then choose either the With consistency check or Without consistency check radio
button.
Consistency check enables parity data to be checked during the media scan.
5. Click OK to accept the updated media scan settings.
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, volume
initialization, or immediate availability formatting. If you want to perform another long-running operation, you should suspend the media scan.
NOTE:
A background media scan is the lowest priority of the long-running operations.
1. Click the Tools tab, then click the Change Media Scan Settings link.
2. Check the Suspend media scan option box.
3. Click OK to suspend media scanning.
Virtual Disk Operations Limit

The maximum number of active, concurrent virtual disk processes per controller is four. This limit is applied to the following virtual disk processes: background
initialization, foreground initialization, consistency check, rebuild, and copy back. If a redundant controller fails with existing virtual disk processes, the processes
on the failed controller are transferred to the peer controller. A transferred process is placed in a suspended state if there are four active processes on the peer
controller. The suspended processes are resumed on the peer controller when the number of active processes falls below four.
Disk Group Operations

RAID Level Migration
Over time, you may determine that characteristics of the initial RAID level you set initially are no longer appropriate for your enterprise. For example, you can add
fault-tolerant characteristics to a stripe set (RAID 0) by converting it to a RAID 5 set. Select the virtual disk that you want to change and select the type of RAID
level to which you want to migrate. MD Storage Manager provides information about RAID attributes to assist you in selecting the appropriate level. You can
perform a RAID level migration while the system is still running and without rebooting, which maintains data availability.
Segment Size Migration

Segment size refers to the amount of data (in kilobytes) that the RAID controller module writes on a single physical disk in a virtual disk before writing data on the
next physical disk. Valid values for the segment size are 8, 16, 32, 64, 128, 256, and 512 KB.
Dynamic segment size migration enables the segment size of a given virtual disk to be changed. A default segment size was set when the virtual disk was created,
based on such factors as the RAID level and expected usage. You can change the default value if actual usage does not match your needs.
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 to satisfy a single I/O. Using a single physical disk
for a single request frees other disks to service other requests, especially when you have multiple users accessing a database or storage environment.
• If you are using the virtual disk in a single-user, large I/O environment (such as for multimedia application storage), performance can be optimized when a
single I/O request is serviced with a single data stripe (the segment size multiplied by the number of physical disks in the disk group used for data storage). In
this case, multiple disks are used for the same request, but each disk is only accessed once.

Virtual Disk Capacity Expansion

When you configure a virtual disk, you select a capacity based on the amount of data you expect to store. For example, if a disk group will contain a virtual disk that
stores larger multimedia files and another virtual disk that stores smaller text files, the multimedia file virtual disk will obviously require more capacity. However,
you may need to eventually increase the virtual disk capacity for a standard virtual disk by adding free capacity to the disk group. This creates more unused space for
you to create new virtual disks, or to expand your existing virtual disks.
Disk Group Expansion

Because the storage array supports hot pluggable physical disks, you can add two physical disks at a time for each disk group while the storage array remains online.
Data remains accessible on virtual disk groups, virtual disks, and physical disks throughout the entire modification operation. The data and increased unused free
space are dynamically redistributed across the disk group. RAID characteristics are also reapplied to the disk group as a whole.
Disk Group Defragmentation

Defragmenting consolidates the free capacity in the disk group into one contiguous area. Defragmentation does not change the way in which the data is stored on the
virtual disks.
Disk Group Operations Limit

The maximum number of active, concurrent disk group processes per controller 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, and disk group defragmentation. If a redundant controller fails with
an existing disk group process, the process on the failed controller is transferred to the peer controller. A transferred process is placed in a suspended state if there is
an active disk group process on the peer controller. The suspended processes is resumed when the active process on the peer controller completes or is stopped.
NOTE:
If you try to start a disk group process on a controller that does not have an existing active process, the start attempt will fail if the first virtual disk in the disk
group is owned by the other controller and there is an active process on the other controller.
RAID Background Operations Priority

The controller supports a common configurable priority for the following RAID operations: background initialization, rebuild, copy back, virtual disk capacity
expansion, RAID level migration, segment size migration, disk group expansion, and disk group defragmentation. 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 will impact storage array performance. It is not advisable to set priority levels at the maximum level. Priority should also be
assessed in terms of impact to host access and time to complete an operation. For example, the longer a rebuild of a degraded virtual disk takes, the greater the
risk for potential secondary disk failure.
Virtual Disk Migration and Disk Roaming

Virtual disk migration is moving a virtual disk or a hot spare from one array to another by detaching the physical disks and re-attaching them to the new array. Disk
roaming is moving a physical disk from one slot to another on the same array.
Disk Migration
You can move virtual disks from one array to another without taking the target array offline. However, the disk group being migrated must be offline prior to
performing the disk migration. If the disk group is not offline prior to migration, the source array holding the physical and virtual disks within the disk group will
mark them as missing. However, the disk groups themselves will still be migrated to the target array.
An array can import a virtual disk only if it is in an optimal state. You can move virtual disks that are part of a disk group only if all members of the disk group are
being migrated. The virtual disks automatically become available after the target array has finished importing all the disks in the disk group.
When you migrate a physical disk or a disk group from one MD3000 / MD3000i array to another, the array you migrate to will recognize any data structures and/or
metadata you had in place on the migration source array. However, if you are migrating from another storage array, the MD3000 / MD3000i array will not recognize
the migrating metadata. In this case, the RAID controller will initialize the physical disks and mark them as unconfigured capacity.
Hot and Cold Migration

Use either of these methods to move disk groups and virtual disks:
• Hot virtual disk migration - Disk migration with the destination storage array power turned on.
• Cold virtual disk migration - Disk migration with the destination storage array power turned off.
NOTE:
To ensure that the migrating disk groups and virtual disks are correctly recognized when the target storage array has an existing physical disk, use hot virtual
disk migration.
Moving Physical Disks to the Destination Array for Migration

When inserting physical disk members into the destination storage array during hot virtual disk migration, wait for each inserted physical disk to be displayed in the
MD Storage Manager before inserting the next physical disk.
NOTE:
Without the delay between physical disk insertions, the storage array can become unstable and manageability is temporarily lost.

Migrating Virtual Disks from Multiple Storage Arrays into a Single Storage Array
When migrating virtual disks from multiple, different storage arrays into a single destination storage array, move all of the physical disks from the same storage
array as a set into the new destination storage array. Ensure that all of the physical disks from a storage array are migrated to the destination storage array before
starting migration from the next storage array.
NOTE:
If the physical disks are not moved as a set to the destination storage array, the newly relocated disk groups might not be accessible.
Migrating Virtual Disks to a Storage Array with No Existing Physical Disks

When migrating disk groups or a complete set of physical disks from a storage array to another storage array that has no existing physical disks, turn off the
destination storage array. After the destination storage array has been turned on and has successfully recognized the newly migrated physical disks, migration
operations can continue.
NOTE:
Disk groups from multiple storage arrays should 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.
Disk Roaming
Moving physical disks within an array is called disk roaming. The RAID controller module automatically recognizes the relocated physical disks and logically
places them in the proper virtual disks that are part of the disk group. Disk roaming is permitted whether the RAID controller module is either online or powered off.
NOTE:
The disk group must be offline before moving the physical disks.
Media Errors and Unreadable Sectors

If the RAID controller detects a media error while accessing data from a physical disk that is a member of a disk group with a redundant RAID level (RAID 1,
RAID 5 or RAID 10), the controller will try to recover the data from peer disks in the disk group and will use recovered data to correct the error. If the controller
encounters an error while accessing a peer disk, it is unable to recover the data and affected sectors are added to the unreadable sector log maintained by the
controller.
Other conditions under which sectors are added to the unreadable sector log include:
• A media error is encountered when trying to access a physical disk that is a member of a non-redundant disk group (RAID 0 or degraded RAID 1, RAID 5 or
RAID 10).
• An error is encountered on source disks during rebuild.
NOTE:
Valid data on an unreadable sector is no longer accessible.

Expires 2/3/2011 12:22:48 PM Disk Operations and Maintenance This document is Dell Confidential
Configuration Maintenance
The MD3000 / MD3000i RAID Storage Arrays store system configuration on the physical disks installed in the system. These physical disks are designated for
maintaining a consistent description of the array and all its disk groups and virtual disks, as well as device names and IP addresses.
It is important to understand that the storing of a configuration is not potentially destructive; however, the restoration of a configuration can be destructive, so
appropriate care must be taken when restoring a configuration.
MDSM uses a primary (emwdata_v0X.bin) and backup (emwback_v0X.bin) configuration file to store:
• A list of storage arrays and hosts included in the management domain. This list is automatically updated when Automatic Discovery, Add Device, Rescan, or
Remove Device option is performed.
• The name of the mail server you set to forward email to and configured email alert destinations.
• The sender's email addresses you set that will appear on every mail message sent to configured email alert destinations.
• Alert notification destination addresses you set for email and SNMP trap messages about individual storage systems in the management domain.
If these files are deleted, the system will automatically recreate them. When the command is issued to list the current configuration, the command line utility is
reading the emwdata_v0X.bin file. The command line can be used to see the parameters listed above, using the "-d" (display) instruction along with the desired
parameter.
This command will display the array name and the IP addresses of the two controllers: SMcli -d -i The -i parameter refers to the internet address. The command is
going to run in-band to an attached storage array. The output from the command will read the eemwback.v0X.bin file for the requested parameter and display it in
the screen response.


This screenshot shows the command query run to start the configuration:
This is an image of a screen shot showing the command query for the current configuration.
While this configuration information does provide several details of interest regarding the storage array, it is by no means as detailed as the level available in an
actual array configuration file. The configuration saved at the command line contains all the details needed to duplicate the entire structure of the array, except for
the user data stored on the virtual disks.
Save the Configuration to a File

NOTE:
When you write information to a file, the script engine does not check to determine if the file name already exists. If you choose the name of a file that already
exists, the script engine will write over the information in the file without warning.
After you have created a new configuration or if you want to copy an existing configuration for use on other storage arrays, you can save the configuration to a file.
To save the configuration, use the save storageArray configuration command. Saving the configuration creates a script file that you can run on the command line.
The following syntax is the general form of the command:
The configuration can be saved at the command line with this syntax:
save storageArray configuration file="filename" [(allconfig |globalSettings=(TRUE | FALSE)) |

virtualDiskConfigAndSettings=(TRUE | FALSE) | hostTopology=(TRUE | FALSE) |
lunMappings=(TRUE | FALSE)]
Where:
• file - Name of the file that contains the configuration values. You must put quotation marks (" ") around the file name.
• allConfig - Saves all of the configuration values to the file. (If you choose this parameter, all of the configuration parameters are set to TRUE.)
• globalSettings - Saves the global settings to the file. To save the global settings, set this parameter to TRUE. To prevent saving the global settings, set this
parameter to FALSE. The default value is TRUE.
• virtualDiskConfigAndSettings - Saves the virtual disk configuration settings and all of the global settings to the file. To save the virtual disk configuration
and global settings, set this parameter to TRUE. To prevent saving the virtual disk configuration and global settings, set this parameter to FALSE. The default
value is TRUE.
• hostTopology - Saves the host topology to the file. To save the host topology, set this parameter to TRUE. To prevent saving the host topology, set this
parameter to FALSE. The default value is FALSE.
• lunMappings - Saves the LUN mapping to the file. To save the LUN mapping, set this parameter to TRUE. To prevent saving the LUN mapping, set this
parameter to FALSE. The default value is FALSE.
NOTE:
In Windows the .scr file will be assumed to be a screen saver file.
Here is an example of the command:
SMcli 123.45.67.89 -c "save storagearray configuration file=\"c:\folder\storagearrayconfig1.txt\";"
WARNING:
Note that the script engine will not check for the presence of a file by the same name as the one specified in the command and will overwrite the file without
warning.
Restoring or Cloning a Configuration

By using the save storageArray configuration command, you can create a file to use to copy an existing configuration from one storage array to other storage arrays,
assuming compatible hardware. You can also use this file to restore an existing configuration that has become corrupted or to duplicate a customer configuration.
You can also copy an existing file to serve as a pattern from which you create a new script file by modifying portions of the original file. The default file extension
is .scr. You can also create a configuration file in a text editor and load it onto the array. The syntax must follow the expected construction and content.
WARNING:
Because the write zeros flag is on by default any pre-existing data on the storage array will not be preserved. The recover command can be used in place of
the create command, which turns off the write zeros flag that, in theory, allows the structure to be reloaded without destroying the data. The use of the recover
command can be seen in the Procedures area of the site.
The configuration can be loaded onto the array at the command line using the "-f" command, while tells the system to use the following file to set the parameters
listed in the file. When the system is being instructed to read from a file the filename is not enclosed in quotes as it is when writing to the file.
NOTE:
When instructing the array to load the configuration file, the file should be directed towards the array name rather than the IP address. When the file is directed
to the IP address of a controller and the controller is being instructed within the file to create a disk group or virtual disk to be owned by the other controller,
the command will fail. When the configuration file is being directed towards the array name the command to build disk groups and virtual disks on both
controllers will succeed. If the configuration must be loaded remotely, change the owner= statement to give ownership of all virtual disk resources to the
RAID Controller that will receive the command. The virtual disks can be reassigned after the configuration has been created.
The command is issued with the following syntax:

NOTE:
Path to the configuration file is assumed to be the root directory.
smcli -n ARRAYNAME -f scriptfile.txt

Expires 2/3/2011 12:22:48 PM Configuration Maintenance This document is Dell Confidential
Firmware and NVSRAM

When a RAID Controller module is replaced or needs to be upgraded, you can download and install the firmware packages separately or together. You need the
RAID Controller module firmware and NVSRAM files to properly use the storage management software and all of its features. The RAID Controllers use self-
leveling technology, so that a replacement controller will be automatically flashed to the current version on the system. However, when the firmware is found to be
out of date, the firmware can be easily flashed to a more recent version.
Firmware is the operating system that runs on the RAID Controller. It may be upgraded and enhanced to correct defects found or modify/add features. The
NVSRAM is a more static set of values that determine the operating parameters of the controller, and set behavior. It is expected that the NVSRAM will be updated
less frequently than the firmware.
During the installation, the multi-path driver maintains data access through one RAID Controller module while the other RAID Controller module firmware is
upgraded.
NOTE:
Use MDSM to verify that it lists both RAID Controller modules as optimal. Downloading firmware when either or both controllers are non-optimal will result
in unsynchronized firmware, and the installation will have to be repeated after restoring the RAID controller module(s) to optimal condition.
The firmware installation is available on the Support tab in MDSM. The software displays only those firmware files that are compatible. If one controller is
replaced, the assumption is made that the firmware should not be revised without customer intent. Therefore, a replacement controller with newer firmware will be
automatically flashed to match the firmware in the remaining controller, without regard to which is newer. If both controllers are replaced, the firmware of both is
set to the newest version available on the two controllers. The RAID Controller module holds dual redundant copies of the firmware in flash memory along with
recovery code. The firmware can run from either image, and the images are synchronized except during firmware download.
The NVSRAM and firmware can be upgraded in three ways:
• MDSM
• Command Line Interface (SMcli)
• Serial Port (advanced method)
The following table lists the steps required to flash the RAID Controller firmware and NVSRAM through MDSM.
NOTE:
Before you download the RAID controller module firmware or NVSRAM files, ensure that the appropriate multi-path driver is running on the host.
Previous Procedure Table not closed!
Flashing Firmware and NVSRAM on the Storage Array Through MDSM
1.
The current version of firmware can be seen by clicking on Storage Array Profile on the Summary tab in MDSM.
his is an image of the user selecting the storage array profile link on the summary tab.
2.
Both the firmware version and the NVSRAM version can be seen in the Summary window of the Storage Array Profile.


This is an image showing the firmware version and the NVSRAM version installed on the storage array.
3.
On the Support tab in MDSM, click Download Firmware.
This is an image of the MDSM Support tab showing the Download Firmware link.
4.
Click Download RAID Controller Module Firmware.
This is an image showing the link to download the RAID controller module firmware.
NOTE:
The application launches a window where the user can browse to the location of the firmware file.
5.
Click the file name, and then click OK.
This is an image of the select file window where the user can navigate to the firmware
file.


6.
Select the option to transfer the NVSRAM file with the firmware, and browse to select the file.
This is an image of the window showing the path to the firmware in

the upper text box and the checkbox for selecting the NVSRAM to
be downloaded also.
7.
Click Transfer to begin the download process.
This is an image showing the user clicking on the Transfer button

to begin the download.
8.
Click Yes to verify the download.


This is an image showing the verification window for downloading
the firmware.
NOTE:
The firmware installation may take up to 15 minutes.
9.
If the download fails, verify that the RAID controller modules' firmware matches in the RAID Controller Modules tab in the Storage Array Profile.
This is an image of the window indicating a firmware download error

that directs the user to the Storage Array Profile to see if the firmware
matches.
10.
Click Close to complete the firmware installation procedure.
This is an image of a firmware installation image showing

the download has completed successfully.

Expires 2/3/2011 12:22:48 PM Firmware and NVSRAM This document is Dell Confidential

Physical Disk Firmware

In the event that the physical disks have firmware-related limitations or performance issues, physical disk packages will be available to correct these issues. These
packages contain the latest firmware files for the physical disks along with an executable file that installs the firmware to the selected physical disks. Ensure that the
firmware files you select are compatible with the physical disks. Before downloading the firmware, you should back up your data by making a virtual disk copy to a
virtual disk located in a different disk group. In addition, do not make any configuration changes to the storage array such as creating virtual disks or defining hosts
during the download. Doing so could cause the firmware download to fail, and the physical disk(s) may be damaged and become unusable, making the data on the
disks inaccessible.
Only Dell-supported 3.0 Gbps SAS physical disks are supported in the storage enclosure. The RAID firmware looks for specific identifiers in all attached physical
disks to ensure they are valid. If the RAID controller module detects physical disks that are not validated by Dell in the SAS solution, such as unsupported SAS disk
or a SATA disk, the RAID controller module marks the disk as unsupported and places it in a Not Ready state.
Here are the steps to flash physical disk firmware:
Flashing Physical Disk Firmware

1.
On the Support tab of MDSM, click Download Firmware.
This is an image of the user clicking on the Download Firmware link in the Support screen.
2.
Click Download Physical Disk Firmware.
This is an image of the user clicking on the download physical disk firmware link.
NOTE:
The interface queries the physical disks and shows the versions of physical disk firmware that are present on the system.


Flashing Physical Disk Firmware
This is an image of the package selection screen for physical disk firmware.
NOTE:
Click the individual file to determine if the firmware file selected is compatible with a physical disk that is present. If the firmware highlighted is not
compatible with any physical disk installed, it will not let you proceed with that file.
This is an image of the user selecting an inappropriate firmware package in the package
selection window.
NOTE:
After you select an appropriate file, the firmware is installed on all physical disks in the system that require that firmware upgrade. You can then select
another firmware file that is compatible with other physical disk types present until the process is complete.

Expires 2/3/2011 12:22:48 PM Physical Disk Firmware This document is Dell Confidential
Service Tag Reset Procedure

In the event the backplane is replaced in an MD3000 / MD3000i, the service tag should be reset to the original configuration.
Reset Service Tag (Enclosure Tag) in Windows

NOTE:
Before performing this procedure, ensure that the MD3000 / MD3000i RAID Controller is seen as occupying enclosure 0. If not, the command must address
the enclosure number that the controllers occupy.

From the command line, type: C:\SMcli -n TRNG01A -c "set enclosure [0] serviceTag=\"6MNL42P"\";
Where:
• TRNG01A is the array name as seen in MDSM.

• enclosure [0] is the enclosure number.
• 6MNL42P is the service tag which is being replaced onto the unit.
NOTE:
If a password is set on the array, the password switch and password will prepend the command string, as in the following example.
C:\SMcli -n TRNG01A -p password -c "set enclosure [0] serviceTag=\"6MNL42P"\";
Verify that the command completes successfully. In MDSM, click Tools>Set or Change Enclosure Tags and verify that the correct service tag is seen. If the
window is already open, close it and reopen it and the new service tag should be seen immediately.
This is a screen shot of a service tag being changed in Windows®:
This is an image of a service tag replacement procedure being done using the command line interface.
Reset Service Tag (Enclosure Tag) in Linux

The command structure is identical with the exception that the set command uses single quote marks instead of double quote marks. For this reason the service tag
string does not need delimiters, but only the double quote marks, as in the following example:
SMcli -n TRNG01A -c 'set enclosure [0] serviceTag="6MNL42P";

Expires 2/3/2011 12:22:48 PM Service Tag Reset Procedure This document is Dell Confidential
Diagnosis and Replacement of a Controller

Always replace the MD3000 / MD3000i RAID Controller while the system is up and operational to ensure that the firmware remains as established. If the firmware
in the surviving controller is older than the firmware in the replacement controller, the replacement controller firmware should be leveled to match the surviving
controller.
However, when the controllers boot cold, or both reboot, a race condition ensues, in which the fastest controller to load becomes the master. The master controller
will level the peer controller to its firmware version. If a replacement controller with older firmware is installed with the array down, the possibility exists that the
controller with the older, and potentially smaller footprint firmware will load first. The result is that the older code will then level (backflash) the newer firmware in
the surviving controller. For this reason, it is recommended to always replace controllers hot. The replacement process should include taking the controller to be
replaced offline, so as to ensure that the surviving peer becomes the master. When the replacement controller is installed, it will automatically become the peer and
be firmware leveled by the master.
Diagnosis of a Controller
The diagnose controller command provides three tests that enable you to verify that a RAID controller module is functioning correctly:
• Read test
• Data loopback test
• Write test
The read test initiates a read command as it would be sent over an I/O data path. The read test compares data with a known, specific data pattern, checking for data
integrity and errors. If the read command is unsuccessful or the data compared is not correct, the RAID controller module is considered to be in error and is placed
offline.
Run the data loopback test only on RAID controller modules that have connections between the RAID controller module and the physical disks. The test passes data
through each RAID controller module physical disk-side channel out onto the loop and back again. Enough data is transferred to determine error conditions on the
channel. If the test fails on any channel, this status is saved so that it can be returned if all other tests pass.
The write test initiates a write command as it would be sent over an I/O data path to the diagnostics region on a specified physical disk. This diagnostics region is
then read and compared to a specific data pattern. If the write fails or the data compared is not correct, the RAID controller module is considered to be in error, and
it is failed and placed offline.
For best results, run all three tests at initial installation. Also, run the tests any time you make changes to the storage array or to components connected to the storage
array (such as hubs, switches, and host adapters).
The test results contain a generic, overall status message and a set of specific test results. Each test result contains the following information:

• Test (read/write/data loopback)

• Port (read/write)
• Level (internal/external)
• Status (pass/fail)
Events are written to the MEL when diagnostics are started and when testing is completed. These events help you to evaluate whether diagnostics testing was
successful or failed and the reason for the failure.
Performing the Diagnosis

From the Storage Management Command Line (SMcli), we will use the following syntax as an example:
NOTE:
Scripting mode is being used, so that the format of SMcli <host ipaddress> -c is used, rather than the interactive method. This command will run out-of-
band only. Using the array name will fail the command.
SMcli 192.168.128.112 -c "diagnose controller [0] loopbackPhysicalDiskChannel=allchannels testID=1";, as in the following screen shot.
This is an image of a screen shot showing the controller diagnosis using testID=1.
Where:
• The controller number of 0 or 1 must be in brackets

• loopbackPhysicalDiskChannel can be 1, 2, or allchannels
• testID is 1 for read, 2 for loopback, or 3 for write
Sample output of a loopback test.
Sample output of a write test.

Replacing/Removing a RAID Controller Module

When one RAID controller module fails, or is removed from the RAID enclosure, failover software on the host directs the alternate RAID controller module to
assume all controller responsibilities for the storage array. The virtual disks owned by the failed or removed RAID controller module are failed over to the surviving
controller and no data is lost.
Since host-based multi-path software is configured for automatic failback, once the RAID controller module is replaced, its data paths and virtual disks are restored
to their original RAID controller module.
Automatic failback occurs under the following conditions:
• Data is protected by dual redundant paths to the host.

• The host has multi-path failover software installed, and it is configured for auto failback.
• Failover occurred due to either RAID controller module lockdown, replacement, or path failover.
NOTE:
Do not power off the array enclosure to replace the RAID controller module. The existing controller will update the new RAID controller module's firmware to
match the existing RAID controller module during a hot replacement. If the RAID controller module is replaced with the array powered off, the new controller
could update the existing controller which potentially will not have the ideal firmware for your environment.
NOTE:
If attached hosts have non-redundant connections to the storage array, offlining a controller will make the disks accessed through that controller unavailable for
those hosts that are attached to that controller. Those hosts should be downed or I/O should be quiesced during this operation so that any write operations
attempted while the controller is offline do not time out.
Complete the following steps to place a RAID controller module offline or online.
Placing a RAID Controller Module Offline

1.
In MDSM click the Support tab, and then click Manage RAID Controller Modules.
his is an image of the MSDM showing the Support tab selected.
2.
In the Manage RAID Controller Modules window, click Place RAID Controller Module Online or Offline.
This is an image showing the Manage RAID Controller Modules selection.
3.
In the RAID Controller Module drop-down list, select the appropriate RAID Controller to bring offline, and then click OK.
NOTE:
You must select the proper RAID controller in this step. If you have to take the remaining controller offline in a system with a RAID Controller that is
malfunctioning but still online, you may disrupt client access to the system.
This is an image showing the selection of a RAID controller to be brought offline.
4.
Click Yes to confirm the process.


This is an image of the user selecting Yes in the
Confirm Place Offline Window.
5.
To verify that the controller has been placed offline, return to the Summary tab, and then click Storage Array Needs Attention.
This is an image showing the Status of Storage Array Needs Attention in the Summary window.
NOTE:
The Recovery Guru window opens. Read the additional information here if needed. In the Details window the Service Action (removal) allowed
option indicates Yes.
This is an image of the Recovery Guru window that is activated when clicking on the Storage
Array Needs Attention link.
6.
Disconnect each of the Ethernet cables and the SAS cable (if using enclosure expansion) from the controller, making sure to identify the original position of
each cable.
7.
Remove the RAID Controller Module and insert the replacement controller.


8.
Reconnect the Ethernet cables and SAS cable in their original configuration and observe that the link and power lights on the controller function normally.
9.
In the Place RAID Controller Module Online or Offline window, click OK to place the controller online.
This is an image of the Place RAID Controller Online or Offline window, where the user can see
the default option of placing the offline controller back online.
10.
Click Yes to continue through the warning that displays the message that placing the controller online makes it available for I/O operations.
This is an image of the Confirm Place Online window warning

the user that placing the controller online will make it available
for I/O operations.
11.
Click the Recheck button in the Recovery Guru.
NOTE:
The failure should no longer appear in the Summary area. It may take several minutes for the Storage array status on the Summary tab to return to
normal.
This is an image showing the Storage array status having returned to optimal after the RAID controller has
been placed back online.
12. Stop SMAgent. The net stop smagent command can be used at the command line. After the service has stopped, restart SMAgent with the net start
smagent command.

Diagnosis and Replacement of a
Controller

Upgrade a Simplex Array to Duplex

Simplex to Duplex Configuration Upgrade
Duplex systems (dual controllers) are designed and configured to be fully redundant with respect to controllers, non-I/O components, logical volume paths, and
physical disk paths. That is, if one of the aforementioned parts of the system fails, there is a redundant part to take its place and maintain system data availability.
Simplex systems are configured to operate with only one controller. There is no controller or physical disk path redundancy in this configuration. A simplex system
can be upgraded to a duplex system. The steps to accomplish this are outlined below. A simplex system will only boot with a controller in slot 0, and will not boot
with a single controller inserted into slot 1. A second controller, added to slot 1 in a simplex array, will be held in reset by the controller in slot 0 and will not come
online.
Simplex to Duplex Conversion Steps

Complete the following steps to upgrade an array from simplex to duplex controllers.
Upgrading an Array from Simplex to Duplex

1. NOTE:
A simplex system will only have enclosure expansion cabling from controller 0 to the next MD1000 enclosure's EMM in position 0. There will be no
connection to the EMMs in position 1, in any of the expansion cabling.
Partially insert the second controller and cable the redundant physical disk channel between the controller and expansion enclosures, if any are present. Do
not fully insert the second controller yet.
2. Using the SMcli command line, change the array mode to duplex:
SMcli 10.37.121.53 -c "set storageArray redundancyMode=duplex;"
Where the IP address is the IP address of the original controller in slot 0.

NOTE:
When the SMcli command completes, the array status will change to Needs attention. Disregard and proceed with these steps.
3.
Insert the redundant RAID Controller into slot 1. Allow the controller to boot, stabilize and show a green status LED.
4. Add the new management connection to MDSM with the following command:
SMcli 192.168.128.102 -c "set controller[b] ethernetPort[1] ipAddress=10.37.121.54

gatewayIPAddress=10.37.112.1 subnetMask=255.255.240.0";
Where IP Address 192.168.128.102 is the current IP address of the new controller, and 10.37.121.54 is the desired address.
NOTE:
The controller will boot looking for a DHCP server. If one is not available, then the controller will default to 192.168.128.102 (in the secondary
position). If the IP address of the second controller was set by DHCP but is not known, the password reset (serial) cable can be used to determine the
current IP address, with the netCfgShow command.
5.
Start the Modular Disk Storage Manager (MDSM). Click Add New Storage Array.
This is an image of the user adding a new storage array.
6.
Select Manual.


This is an image of the user selecting manual.
7.
Select Out-of-band management. Enter the IP addresses of the management ports of the two RAID controllers and click Add.
This is an image of the user select out of band, and entering the I P
addresses of the two RAID controllers.
8. NOTE:
The simplex controller does not have cache mirroring enabled, so that the user must now enable this attribute for each of the existing Virtual Disks. Any
new Virtual Disks created will automatically have this cache attribute enabled.
Using SMcli issue the following command to modify cache mirroring:
SMcli 10.37.121.53 -c "show allVirtualDisks";
The output will look similar to the screen shot. The red arrow notes the name of one of the virtual disks. Also shown, in the red circle, are the read and write
cache attributes. The write cache with mirroring will be enabled.
This is a partial image of the output generated for the show all virtual disks command.


9.
Use the SMcli command structure as follows to enable cache mirroring.
SMcli 10.37.121.53 -c "set virtualDisk [\"SQLDB\"] mirrorCacheEnabled=true";
10.
This command must be completed for every virtual disk. After the command completes successfully for each disk, re-run the show allVirtualDisks
command to verify that the cache attributes are enabled for each Virtual Disk. Write cache without batteries will remain disabled.
NOTE:
When the upgrade is complete, the non-volatile static RAM (NVSRAM) version of RAID controller 0 will continue to be reported in simplex mode
even though the RAID controller is actually running in duplex mode. Also, all the existing virtual disks will continue to be owned by controller 0. The
virtual disks will need to be redistributed, with a possible dependency on the type of host connectivity.

Expires 2/3/2011 12:22:48 PM Upgrade a Simplex Array to Duplex This document is Dell Confidential
MD3000i Utilities
Windows Utilities
• Uninstall MD Storage Manager.exe - The main install executable for removing the application. It is called as part of the standard Add/Remove procedure.
This file is not for direct customer execution.
• Modular Disk Storage Manager Client.exe - The executable that starts the client application. It is linked via the application icon.
• SMclient.bat - The batch file to start the client application. SMclient calls into the .jar file and typically is not for direct customer execution.
• SMcli.exe - The Command Line (CLI) Script utility, which is used to configure and monitor storage arrays by issuing commands from Windows command
prompts or a Linux operating system path.
• asyncRVMUtil.bat - A Command Line utility used to synchronize Asynchronous RVM mirrors. It is not applicable for the MD3000 / MD3000i, including
for potential future use.
• SMmonitor.exe - The Persistent Monitor Application, which is registered as a Windows Service. It is not for direct customer execution.
• SMsnapassist.exe - The utility used to map a Snapshot to a host. This utility may be the same as SMrepassist
• SMrepassist.exe - A Windows-only utility used to flush cache prior to a Virtual Disk Copy/Snapshot to a host
SMrepassist (replication assistance) is a host-based utility. Use this utility before and after you create a virtual disk copy on the Windows operating system.
Running SMrepassist ensures 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 also can use this utility to resolve duplicate signature problems for snapshot virtual disks. If you are running a Windows operating system, use the
SMrepassist utility to flush the source virtual disk's cache prior to creating a Snapshot.
SMrepassist is installed in the "util" directory of your host server installation. Run the utility from the command line in a DOS window on a host server
running Windows.
SMrepassist -f <filesystem-identifier>
Where -f flushes all the memory-resident data for the file system indicated by <filesystem-identifier>, and <filesystem-identifier> specifies a unique file
system in this syntax: drive-letter: <mount-point-path>
The file system might include only a drive letter or a drive letter and a mount point.
An error message appears in the command line when the utility cannot distinguish between:
◦ Source virtual disk and snapshot virtual disk (for example, if the snapshot virtual disk has been removed)
◦ Standard virtual disk and virtual disk copy (for example, if the virtual disk copy has been removed)
• SMdevices.bat> - Utility that displays the physical devices mapped to the host from the array. Includes information such as virtual disk names and RAID
controller module ownership information. This file calls dsmUtil.exe.
• NTSnapshot.bat - This is similar to SMsnapassist and SMrepassist and should be deprecated for the MD3000.
• SMagent.exe - Agent application that allows in-band management access to the Storage Array. It includes another thread that runs the Host Context Agent
service for topology discovery. SMagent is registered as a Windows Service and is not for direct customer execution.
• dsmUtil.exe - DSM utility to provide debugging and support for the DSM driver, which is part of MPIO. A README will be included with the utility.
• rdacInstall.exe - Utility used to install and remove the DSM, used by the installer to install the DSM. It is called as part of the standard Add/Remove
procedure. This file is not for direct customer execution.
Linux Utilities
• SMagent - Agent application that allows in-band management access to the Storage Array. It is registered as a daemon. It is not for direct customer execution.
• SMmonitor - The Persistent Monitor Application, which is registered as a daemon. It is not for direct customer execution.
• Uninstall_dellmdstoragemanager - Install script for removing the application. It is used by Add/Remove Programs.
• Genfileattributes - Script used by the MPP driver during install. It is not for customer execution.
• Genuniqueid - Script used by the MPP driver during install. It is not for customer execution.
• Hbacheck - Script used by the MPP driver during install. It is not for customer execution.
• mppSupport - Utility used by Support to gather information about the host and the configuration.
• mppUtil - Utility to provide debugging and support for the MPP driver. It is documented by a man page.
• mppBusRescan26 - Utility to rescan for new devices. It is documented by a man page.
• mppMkInitrd - Script used by the MPP driver during install. It is not for customer execution.


• mppUpdate26 - Utility to update the MPP driver configuration after a kernel change or HBA driver change. It is documented by a man page.
• setupSuSEBoot - Script used by the MPP driver during install on SuSE. It is not for customer execution.
• SMcli - The Command Line (CLI) Script utility, which is used to configure and monitor storage arrays by issuing commands from Windows command
prompts (C:\) or a Linux operating system path.
• SMclient - Batch file to start the client application.
• asyncRVMUtil - A Command Line utility used to synchronize Asynchronous RVM mirrors. It is not applicable for the MD3000 including for potential future
use.
• SMdevices - Utility that displays the physical devices mapped to the host from the array. Includes information such as virtual disk names and RAID
Controller module ownership information.
• Hot_add - Utility to scan for new devices. Calls mppBusRescan. This utility is for Linux operating systems only.

Expires 2/3/2011 12:22:48 PM MD3000i Utilities This document is Dell Confidential
Product Positioning
This page identifies the key feature changes in the "SATA Support on the MD3000x" program. All of these changes will be described in more detail later in this
Tech sheet.
Hardware Changes
• Enclosures can now contain SAS, SATA II or a mix of these physical disk types
• Disk groups can contain physical disks of one interface type only
• Hot Spare physical disks will not cross architectures
• Both interface types of physical disks are hot pluggable (SATA II requires interposers)
• Supports redundant path single HBA in Windows for MD3000
• Support for VMWare ESX3.5 & ESX3.5i from 1st December 2007
• SATA II physical disks are available in 250GB, 500GB, 750GB an 1TB capacities
NOTE:
A full list of PowerEdge Servers Supported can be found in the Support Matrix found at www.dell.com under Products ' PowerVault Storage ' MD3000x
Software Supported
Supported operating systems are as follows:
• Windows Server 2003

• Windows Storage Server 2003
• Windows Unified Data Storage Server 2003
• Windows 2000 SP4 Advanced Edition (MD3000 only)
• RHEL v3 (MD3000 only), 4 and 5
• SLES v9 and 10
• Windows XP and Vista (management stations only)
Supported iSCS Initiators are as follows (MD3000i only):
• Microsoft iSCSI Initiator 2.05

• RHEL v4 and 5
• SLES v9 and 10 SP1
NOTE:
For exact service pack and patch requirements check the support matrix found at www.dell.com under Products--->PowerVault Storage--->MD3000x

Expires 2/3/2011 12:22:48 PM Product Positioning This document is Dell Confidential
Global Differences
The procedure for a Simplex Controller replacement may be slightly different depending on region.
EMEA/APAC
A customer replacement/upgrade procedure is put in place allowing the customer to run the resource the CD and perform the necessary step to replace the controller.
Americas
The is no customer replacement procedure in place and this operation must be performed by a DSP.


Expires 2/3/2011 12:22:48 PM Global Differences This document is Dell Confidential
Configuration Changes
MD3000 Support of a single SAS HBA with redundant data paths.
In previous versions of the MD3000x implementation redundant data paths were only available using servers with 2 SAS HBA’s. This latest implementation allows
for single SAS HBA servers to have redundant data paths as shown in the diagram below. This is also the case for a single server.
Diagram showing previous

implementation
Figure: Previous implementation
Diagram showing SATA Dogs

implementation
Figure: SATA Dogs implementation

Expires 2/3/2011 12:22:48 PM Configuration Changes This document is Dell Confidential
SAS SATA II Hardware

Although we tend to think of SAS and SATA devices as separate technologies, SAS was designed from the beginning to provide some layer of interoperability with
SATA II devices. After all, data being send serially down a piece of cable from a spinning piece of metal can only be done in so many ways right? And it’s no
accident that the connectors for SAS and SATA II devices are almost identical.
In fact SATA physical drives are plug compatible with SAS physical drives, and SAS is able to tunnel SATA control data. It is therefore relatively easy to construct
a backplane which can support both types of physical disks natively.
It is with this in mind that this update provides the MD3000x enclosures with support for two physical disk types: Serial Attached SCSI (SAS) and Serial Advanced
Technology Attachment II (SATA).
To enable this cross-drive architecture in the MD3000x enclosures, a new physical drive caddy is used for the SATA physical disks, with an interposer card situated
between the physical disk and the backplane. This interposer card ensures that the SATA physical disks achieve the correct “porting” to communicate with the SAS
backplane.
Photo of SATA physical drive

caddy
Figure:SATA drive caddy
Photo of SATA physical drive caddy with interposer

removed
Figure:SATA drive caddy with interposer removed
NOTE:
Certain physical drive failures may require a replacement of the interposer card only. Detailed instructions on removal of the interposer card can be found
in the MD1000 training material.
As already mentioned, enclosures can now contain a mixture of SAS and SATA II physical disks, however, the user must be aware that a disk group must consist of
only one type. Furthermore, in the case of a failed disk in a disk group, the failed disk must be replaced with a disk of the same type. The management software
provided with the array will not allow creation of RAID storage using mixed drive types. This also means that any enclosures fitted with mixed physical disk types,
and using Hot Spares, require hot spares of both types to provide hot spare coverage for disk groups of either type.
All components in the connectivity chain from the SATA physical disks to the controllers will require a minimum firmware level discussed later in this Tech sheet.
As both SAS and SATA II physical disks are hot-pluggable, you may remove and insert disks without shutting down your enclosure remembering to follow the rules
below.
To ensure that physical disks are safely removed from and inserted into the MD3000x RAID storage arrays, follow these guidelines:
• Wait at least 60 seconds between removing a physical disk and inserting a replacement.
• When you pull a physical disk from a storage array to move it to a different slot, wait 60 seconds before inserting the physical disk into the new slot.
• Wait at least 60 seconds between the removal of physical disks from a storage array.
• Wait at least 60 seconds between the insertion of physical disks into a storage array.
In a large configuration, storage management software may take up to 10 seconds to detect hardware changes.

Expires 2/3/2011 12:22:48 PM SAS SATA II Hardware This document is Dell Confidential


Firmware Update
To enable SATA support on your RAID Controller Module you must be running a minimum firmware revision on the controller, NVSRAM and the SATA disk
itself. The following steps explain how to update the firmware from both a management station and from a host connecting to a RAID Controller Module.
NOTE:
The storage matrix found at support.dell.com under Products--->PowerVault Storage--->MD3000i in the Manuals section lists minimum supported
firmware revisions and supported SATA physical disks.
The following will be required for the upgrade:
1. The latest resource CD found at support.dell.com under Products--->PowerVault Storage--->MD3000x in the Drivers and Downloads section.
2. Latest firmware revisions as required
NOTE:
Firmware supporting the SATA physical disks must be ABOVE :
Storage Array: MD3000x
Controller Module firmware: 06.50.32.60
MD Storage Manager version: 02.50.G6.02
Updating RAID Controller Module Firmware from a Management Station

1. In MD Storage Manager click the support tab and choose the option to Gather Support Information
2. Using the latest version of the Resource CD (referred to above) run a pre-requisite check of the management station.
3. Update you version of MD Storage Manager if required
4. Stop all I/O to the enclosure
5. Using MD Storage Manager, update the MD3000i RAID controller firmware and NVSRAM by selecting Support--->Download Firmware--->Download
RAID Controller Module Firmware.
6. Select appropriate file locations for both the Firmware as well as NVSRAM update packages and click Transfer. When a successful download confirmation
message is displayed, the firmware and NVSRAM have been updated.
7. Update the MD Storage Manager for each management station connected to the MD3000i.
8. Use the resource CD to update all hosts connected to the MD3000x.
Updating RAID Controller Module Firmware from an attached host

1. Stop all I/O to the enclosure
2. In MD Storage Manager click the support tab and choose the option to Gather Support Information
3. Run a Pre-requisite check of your host server from the MD3000i Resource CD
4. Install updates as per the resource CD checks
5. Update the version of MD Manager installed on your Host station using the resource CD
6. Using MD Storage Manager, update the MD3000i RAID controller firmware and NVSRAM by selecting Support--->Download Firmware--->Download
RAID Controller Module Firmware.
7. Select appropriate file locations for both the Firmware as well as NVSRAM update packages and click Transfer. When a successful download confirmation
message is displayed, the firmware and NVSRAM have been updated.
8. Repeat steps 1-5 for each host and management station attached to the enclosure.
Updating SATA Disk Firmware

Before migrating SATA physical disks from a Dell PowerEdge Server or an MD1000 expansion enclosure to an MD3000x storage array enclosure you must ensure
that they are running a compatible firmware revision listed on the Storage Matrix.
NOTE:
For non-RBOD enclosures, SATA physical disk firmware can be upgraded using the SATA Disk Firmware Utility available from http://support.dell.com.
For RBOD enclosures the upgrade takes place through the MD Storage Manager utility, with the appropriate firmware wrapped for RBOD flashing.

Expires 2/3/2011 12:22:48 PM Firmware Update This document is Dell Confidential
Single Controller Replacement (DSP and CRU)

Because of the updated firmware requirements it is important that customer expectations are set correctly when replacing a Simple Controller in the MD3000i series.
The following information / access is required:
1. A notebook, workstation or server is required that can be connected to array via serial cable


2. A Simple Controller Replacement CD should be dispatched along with a serial cable and tech sheet (EMEA / APJ) or service kit (Americas). It is necessary to
run this CD to ensure that the new replacement controller is at the same firmware level as the customer’s original state.
CD artwork for the Simple Controller Replacement
3. The customer should be made aware of the length of time it requires to flash and reboot array if a firmware upgrade or downgrade is required on the new
replacement controller (20 minutes)
4. If the unit for service is in an unmanned Data Centre (where security guards open the doors for DSP, and lock them into DATA centre for the duration of the
repair:
◦ Tech support should advise customer of what the DSP is required to do to service the simplex controller.
◦ The tech should have the authority granted by the customer to connect a notebook, serial cable and run a CD to service.
◦ If customer does not allow tech to perform these activities then the customer needs to have an employee there authorized to perform service
◦ If customer will not allow the Dell DSP to run the CD in their environment (virus concerns), then the customer should download the ISO image from
our website so their systems can scan for virus, etc. This must be done in advance of DSP arrival.
◦ If customer refuses to allow outside software or outside notebooks to be connected to their array alternative would be CLI with serial shell access.
Customer must provide a host or notebook to attach to array to perform this task. DSP would escalate to ORC (Onsite Resource Centre) for step by step
instructions for CLI commands.
NOTE:
Because of these requirements tech support agents need to be aware that in there dispatch notes the DSP must be told that access to a notebook is required
when servicing a simplex controller

Single Controller Replacement (DSP
and CRU)
Manual Controller Replacement

In the event that a replacement RAID controller module in a simplex configuration does not complete boot (indicated by the enclosure status LED being solid amber
and the inability to connect to the controller via the MD Storage Manager), the firmware on the replacement controller will have to be updated.
Windows configurations - what you will need

• Windows based Laptop/Workstation/Server with functional COM1 serial port and Hyperterminal installed
• Serial cable
• Appropriate Firmware and NVSRAM files:
• For MD3000i without SATA support:

◦ Firmware version 06.50.32.60 (RC_6503260_1532.dlp)
◦ NVSRAM version 650890-906 (N1532-650890-906.dlp)
• For MD3000i with SATA support:
◦ Firmware version 06.70.10.60 (RC_6701060_1532.dlp)
◦ NVSRAM version 670890-901 (N1532-670890-901.dlp)
Before you begin

Ensure that the RAID controller module is in slot 0 in the MD3000i enclosure and ensure that you disconnect all Ethernet cables to the RAID controller module.
Connect the serial cable between the controller and COM1 of the computer that will be used to perform the update.
1. Go to start--->Programs--->Accessories--->Communications and run Hyperterminal.


2. Create a new connection in Hyperterminal using the COM1 port.
3. In the COM properties tab, set the “bits per second” to 115200 leaving the rest at default values.
4. Click on OK to connect to the MD3000i.
5. Power cycle the MD3000i enclosure.
6. Wait till you see a warning message indicating that the firmware does not match and giving the firmware version to be updated to.
(WARNING!!!!! This controller is not running the correct firmware release. SOD is now suspended. In order to prevent any configuration loss, you must
download x6…. Release)
7. Hit return to see the “--->” prompt.

8. Type serialDownload 32.
9. In Hyperterminal, go to Transfer--->Send File.
10. Browse and select the appropriate file. The firmware needs to be updated before the NVSRAM.
11. Set the protocol to 1K Xmodem.
12. Click on Send.
13. This procedure can take up to 40 minutes for the firmware.
14. Once the file is transferred, repeat steps 9-12 for the NVSRAM.
15. Type in sysReboot to reboot the RAID controller module.
16. Reconnect the Ethernet cables to the RAID controller module.
17. Disconnect the serial cable from the RAID controller module.
18. Connect to MD3000i enclosure using MD Storage Manager to ensure that update was successful.
Linux configurations - What you will need

Linux based Laptop/Workstation/Server with functional COM1 serial port and minicom installedminicom can be installed from the Red Hat or SLES installation
CDs. It is not installed in a default installation of the system.
• Serial cable
• Appropriate Firmware and NVSRAM files:
◦ For MD3000i without SATA support:
■ Firmware version 06.50.32.60 (RC_6503260_1532.dlp)
■ NVSRAM version 650890-906 (N1532-650890-906.dlp)
◦ For MD3000i with SATA support:
■ Firmware version 06.70.10.60 (RC_6701060_1532.dlp)
■ NVSRAM version 670890-901 (N1532-670890-901.dlp)
Before you begin:

Ensure that the RAID controller module is in slot 0 in the MD3000i enclosure and ensure that you disconnect all Ethernet cables to the RAID controller module.
Connect the serial cable between the controller and COM1 of the computer that will be used to perform the update
1. Open a Terminal window and type “minicom -s” to open minicom to the configuration menu.
2. Ensure that minicom is set correctly using the following steps:
◦ Use the arrow key to scroll down to “Serial Port Setup”.
◦ Ensure that the serial device is set to the correct COM port (usually ttyS0), BPS/Par/Bits is set to 115200 8N1 and Hardware Flow Control is set to Yes.
◦ Press the return key once you are done making changes.
◦ Save the setup and exit.
◦ Press Ctrl+A T to open the terminal settings.
◦ Ensure that “Terminal Emulation” is set to ANSI.
◦ Press the return key to return to the main screen.
3. Power cycle the MD3000i enclosure.
4. Wait till you see a warning message indicating that the firmware does not match and giving the firmware version to be updated to..
WARNING!!!!! This controller is not running the correct firmware release. SOD is now suspended. In order to prevent any configuration loss, you must
download x6…. Release)
5. Hit return to see the “--->” prompt.

6. Type serialDownload 32.
7. Type Ctrl+A S to open the Send File dialog.
8. Scroll down to choose the “XModem” protocol.
9. Browse and select the appropriate file. This can be done by using Goto and typing the absolute path of the directory containing the firmware files. You can
then tag the file using space and send the file by choosing “okay”.
10. If system times out, reboot the controllers and repeat steps 6 through 9.
11. This procedure can take up to 40 minutes for the firmware.
12. Repeat steps 6 through 9 and choose the NVSRAM file this time.
13. The firmware needs to be updated before the NVSRAM.
14. Type in sysReboot to reboot the RAID controller module.
15. Reconnect the Ethernet cables to the RAID controller module.
16. Disconnect the serial cable from the RAID controller module.
17. Connect to MD3000i enclosure using MD Storage Manager to ensure that update was successful.

Expires 2/3/2011 12:22:48 PM Manual Controller Replacement This document is Dell Confidential

ESX 3.5 and 4.0 Best Practices

Dell Engineering and Technical Support have created configurations guides for VMWare ESX 3.5 and 4.0 containing best practices. Please use these guides when
working with your customers.
VMWare ESX 3.5 Configuration and Deployment Guide

VMWare ESX 4.0 Configuration and Deployment Guide

Expires 2/3/2011 12:22:48 PM ESX 3.5 and 4.0 Best Practices This document is Dell Confidential
PowerVault VMware Documentation and Media

As you learned in this section, Dell provides customers the ability to deploy PowerVault storage to VMware ESX 3.5 generated virtual machines on PowerEdge
Servers. To learn more about how to deploy and configure this type of solution please review:
• Dell PowerVault Configuration Guide for VMware ESX/ESXi 3.5

• Engineering Brown Bag Presentation

PowerVault VMware Documentation
and Media
Using the Support Bundle and Logs

The presentation contained in the link below contins information about how to use the Support Bundle and Logs, when troubleshooting issues with the PowerVault
MD3000 / MD3000i.
Md3000/i Support Bundle Analysis

Expires 2/3/2011 12:22:48 PM Using the Support Bundle and Logs This document is Dell Confidential
Serial Shell and Console Procedures

The process to use the serial console has changed.
• Serial Console is now protected by a password. The password is supportDell.

• The Serial Console access is now in the form of a menu. The menu will give access to all required functions for troubleshooting.
• The menu options available are.
1. Display IP Configuration
2. Change IP Configuration
3. Reset Storage Array (SYMbol) Password
4. Quit Menu
• Older serial shell commands are no longer available under 2nd generation firmware.

1. Startup a terminal emulation program like putty, teraterm, minicom or hyperterminal using these terminal settings (115200-8-n-1).
NOTE:
Windows Server 2008 does not ship with hypertrm.exe and hypertrm.dll. Customers wanting to use hyperterminal in Server 2008, must copy these two
files from a Windows XP system.
2. Send a from the terminal shell. This is accomplished by <Ctrl><PAUSE/BREAK> within HyperTerminal or Putty, use <Ctrl><A><F> from within
Minicom on Linux systems.
3. When prompted for input within 5 seconds, press <S> for the service interface menu.
NOTE:
Only capital "S" works here, lowercase "s" will not be recognized for this command.
4. The user will then be prompted for a password. The Password is: supportDell
5. The menu options available are.
• 1) Display IP Configuration
• 2) Change IP Configuration
• 3) Reset Storage Array (SYMbol) Password


• Q) Quit Menu
Serial Shell Menu Option Detail

The following sections of this page will illustrate the each of the main menu options in the serial shell.
Display IP Configuration
Display IP Configuration displays the current IP configuration of the of the ethernet maintenance port for the RAID controller currently attached to the Serial Shell
terminal window as shown in the image below.
This image illustrates the result of selecting option 1 of

the serial shell console menu options, Display IP
Configuration, which displays the currrent IP
configuration of the RAID controllers ethernet
management port.
Change IP Configuration
Change IP Configuration will ask the user a series of questions about the IP configuration, the responses will set the IP configuration schema for the maintenance
port of the controller currently attached to the serial shell terminal. The image below illustrates the command and its question series.
This image illustrates the series of questions asked during the serial shell change IP
configuration function.
Reset Storage Array (Symbol) Password

This option allows the user to reset the Storage Array Password.

Using the Serial Shell to Troubleshoot Customer Issues

One of the greatest advantages to using serial shell during troubleshooting, is the ability to see each RAID controller on a PowerVault MD3000/MD3000i complete
the P.O.S.T. sequence. This process is quite similar to viewing the P.O.S.T. information for a server or a desktop. And as many technicians have found with servers
and desktops knowing when devices are initialized during POST can help to determine a point of failure during troubleshooting. The link below contains a text file
with a successful P.O.S.T. sequence for the PowerVault MD3000i. Successful completion of the P.O.S.T. sequence is indicated by the line (tRAID): NOTE:
sodMain complete.
MD3000i Captured P.O.S.T. Sequence
Other examples of when it would be a good idea to use the serial shell to troubleshoot issues is mainly around significant events that occur with a RAID controller.
These include but are not limited to:
• in a duplex configuration, when one of the controllers is being replaced, you should attach the serial cable to the good controller. In doing this when the
replacement controller is installed, you will be able to determine if ACS (Automatic Code Synchronization) has taken place and successfully completed.
Remember ACS is the ability for a native duplex controller to flash or synchronize its firmware with a new rplcaement controller.
• when performing a firmware update during normal conditions, it may be helpful to view the serial shell information as the update progresses.
NOTE:
Even though the logs of the updates above can be pulled from the support bundle, the advantage of the serial shell in this case is realtime diagnosis. Finally the
logs that are stored in the support bundle are very large and it may take some time for you to identify the section of each log that provides you the information
that you need.
Where Can I Find More Information on Serial Shell?

Please refer to the following livemeeting presentation on Serial Shell Troubleshooting Best Practices.
Serial Shell Troubleshooting Best Practices

Expires 2/3/2011 12:22:48 PM Serial Shell and Console Procedures This document is Dell Confidential
Critical Events
RAID Controller Module Thermal Shutdown
Enclosure management provides a feature which automatically shuts down the operating system, the server, and the enclosure when the temperature within the
storage enclosure reaches dangerous extremes. Thermal shutdown protects the data on the physical disks from corruption in the event of cooling system failure. The
temperature at which shutdown occurs is determined by the enclosure temperature probe's Minimum Failure Threshold and the Maximum Failure Threshold. These
thresholds are default settings that cannot be changed. If the temperature sensors on the backplane or RAID controller module detect a temperature exceeding these
thresholds, the controller issues a thermal shutdown command that shuts down the power supplies for the storage enclosure within five seconds. When the sensors
no longer detect an over-temperature condition, the storage enclosure restarts automatically.
NOTE:
Event reports describe the temperature probes as follows:
• Temp Probe 0 = RAID Controller 0

• Temp Probe 1 = RAID Controller 1
• Temp Probe 2 = Backplane
• Temp Probe 3 = Backplane
NOTE:
While the MD3000 / MD3000i uses the Recovery Guru popup whenever certain classes of events happen, the Major Event Log (MEL) contains a listing
of each alert.
These events can be further researched using DSN and find additional, updated information that may not be available in the Recovery Guru.
Critical Conditions
The storage array will generate a critical event if the RAID controller module detects a critical condition that could cause immediate failure of the enclosure and/or
loss of data. The storage array is in a critical condition if:
• More than one fan has failed.

• Any backplane temperature sensors in the critical range.
• Backplane/power supply failure.
When the enclosure is under critical condition, its enclosure status LED blinks amber.
NOTE:
If both RAID controller modules fail simultaneously, the enclosure cannot issue critical or noncritical event alarms for any enclosure component.

Noncritical Conditions
A noncritical condition is an event or status that will not cause immediate failure, but must be corrected to ensure continued reliability of the storage array. Examples
of noncritical events include:
• One power supply has failed.

• One cooling fan has failed.
• One RAID controller module in a redundant configuration has failed.
• A battery has failed or has been removed.
• A physical disk in a redundant virtual disk has failed.
When the enclosure is under non-critical condition, its enclosure status LED shows steady amber.

Expires 2/3/2011 12:22:48 PM Critical Events This document is Dell Confidential
SNMP Alerts and Traps

The MD3000 / MD3000i Storage Arrays are fully compatible with standardized SNMP trapping and alerting.
Setting SNMP Alerts

SNMP setup can be accomplished from both MDSM and the command line.
From the Command Line

Use the "-a" to add an SNMP trap destination or an email address alert destination. When adding an SNMP trap destination, the SNMP community is automatically
defined as the community name for the trap and the host is the IP address or Domain Name Server (DNS) host name of the system to which the trap should be sent.
The following example shows how to set the SNMP trap alert destination:
SMcli -a trap:public, 123.45.67.891 123.45.67.892
Where the:
• Trap destination is 123.45.67.891

• Storage array is 123.45.67.892
• Community name is public
From MDSM
To add a management console to the list of addresses configured to receive SNMP alerts:
NOTE:
The Management Information Base (MIB) for the storage array is copied to the client directory as part of a Full or Management Station installation selection.
DellMDStorageArray.mib can be compiled on an SNMP Management Console using the interface provided by the console.
1. Click the Tools tab, then click the Set up SNMP Alerts link.
2. Enter the Community name.
3. Enter the trap destination (hostname of the management console
4. Click Add to add the management console to the Configured SNMP addresses list.
5. Repeat steps 2 through 4 until you have added all management consoles that should receive SNMP alerts.
6. Click OK.

Expires 2/3/2011 12:22:48 PM SNMP Alerts and Traps This document is Dell Confidential
Recovery Guru
The Recovery Guru is a component of MDSM that diagnoses critical events on the storage array and recommends step-by-step recovery procedures for problem
resolution. You can access the Recovery Guru by clicking the Storage Array Needs Attention link on the Summary page or by clicking the Recover from failure
link on the Support page.
You can detect a problem using these indicators:
• Non-optimal status icons

• Alert notification messages sent to the appropriate destinations
• Hardware indicator lights
The status icons return to Optimal as problems are resolved.

Here is a list of links to all of the Recovery Guru screens and the problems each addresses:
Recovery Guru Screens and Their Descriptions

Title Description
Battery Nearing Expiration The battery in the RAID controller module is nearing its expiration date.
Battery Settings Mismatch The enclosure detected that both RAID controller modules do not have functioning batteries.
By-passed Physical Disk The EMM module detected the presence of a physical disk but is unable to communicate with the physical disk.
Data Rate Negotiation The automatic negotiation for the data rate on the specified port failed. The port is down and will not transfer any data.
Failed
Degraded Physical Disk A physical disk channel status was set to Degraded because of excessive I/O errors or at the instruction of a technician for diagnostic
Channel and support reasons.
Degraded Virtual Disk One or more physical disks failed or have been removed in a disk group, resulting in this disk group becoming degraded.
EMM Firmware Mismatch An expansion enclosure in the storage array contains EMM modules with different firmware versions.
EMM Module - Loss of Communication has been lost to one of the dual EMM modules in an expansion enclosure. The expansion enclosure has only one I/O
Communication path available.
EMM Hardware Type An expansion enclosure in the storage array contains different hardware EMM types.
Mismatch
Expansion Enclosure Limit The storage array detected an Out of Compliance status because it contains more than the allowed number of expansion enclosures.
Exceeded
Expansion Enclosure - An expansion enclosure with redundant channels lost redundancy and has only one channel available for I/O.
Loss of Path Redundancy
Failed Battery The battery in the RAID controller module failed.
Failed EMM Module An EMM module failed in an expansion enclosure.
Failed Fan Module A power supply/cooling fan module failed and must be replaced.
Failed I/O Host Card An I/O host card in one of the controllers is not functioning properly.
Failed or Degraded SAS A Serial Attached SCSI (SAS) port failed or is in a degraded state.
Port
Failed Physical Disk - An unassigned physical disk or a standby hot spare physical disk failed.
Unassigned or Standby Hot
Spare
Failed Physical Disk A physical disk channel has failed on a RAID controller module.
Channel on RAID
Controller Module
Failed Power A power supply/cooling fan module failed and must be replaced.
Supply/Cooling Fan
Module
Failed Snapshot Virtual Either the snapshot virtual disk's associated repository virtual disk is full or its associated source or repository virtual disk failed due
Disk to one or more physical disk failures on their respective disk groups.
Failed Virtual Disk - Physical disks were replaced in a failed virtual disk, but the virtual disk has not yet been initialized.
Awaiting Initialization
Failed Virtual Disk - One or more physical disks failed in a disk group causing the modification operation (for example, adding capacity) to be suspended.
During Modification
Failed Virtual Disk - One or more physical disks in a disk group failed or were removed, causing the associated virtual disks to fail.
Physical Disk Failure
Gold Key - Out of The enclosure detected an issue with the premium features implementation.
Compliance
Impending Physical Disk A physical disk is reporting internal errors that could cause the physical disk to fail. If this physical disk fails before you follow these
Failure (High Data recovery steps, the virtual disks in the disk group will fail and all data on the virtual disks will be lost.
Availability Risk)
Impending Physical Disk A physical disk is reporting internal errors that could cause it to fail. If this physical disk fails, the virtual disks in the disk group will
Failure (Medium Data become degraded.
Availability Risk)
Impending Physical Disk A physical disk is reporting internal errors that could cause the physical disk to fail. If the affected physical disk is unassigned, it will
Failure (Unassigned or not be available for virtual disk configuration. If the affected physical disk is a standby hot spare, it will not be available to take over
Standby Hot Spare) for a failed physical disk.
Incorrect Physical Disk A physical disk in the storage array has been replaced with a different technology than the original physical disk.
Type
Individual Physical Disk - The specified physical disk channel is experiencing intermittent errors along the path to a single or several physical disks.
Degraded Path
Maximum Temperature The maximum temperature of the enclosure has been exceeded. A fan failed, an obstruction is blocking the air flow to or from the
Exceeded enclosure, or the room temperature is too high.
Misconfigured Enclosure The expansion enclosure listed in the Recovery Guru Details area has been misconfigured.
Missing Virtual Disk The storage array detected that the physical disks associated with a virtual disk are no longer accessible. This can be the result of
removing all physical disks associated with a disk group or a loss of power to one or more enclosures.
Mixed Physical Disk Types The enclosure detected an unsupported configuration due to an unsupported mix of physical disk types.
- Out of Compliance


Nominal Temperature The safe operating temperature of the enclosure has been exceeded. A fan failed, an obstruction is blocking the air flow to or from the
Exceeded enclosure, or the room temperature is too high.
Offline Disk Group A disk group may have an Offline status for the following reasons:
• You manually placed the disk group Offline in preparation for moving the physical disks to another storage array (disk group
relocation). If this is the reason, do not follow these recovery steps. Instead, follow the instructions in the appropriate
documentation for moving physical disks.
• You placed the disk group offline from the Command Prompt
• You were performing a disk group relocation operation and inserted all of the physical disks in the destination storage array but
the disk group is still showing an Offline status.
Offline RAID Controller The RAID controller module was placed Offline. This could be caused by:
Module
• The RAID controller module failed a diagnostic test and was automatically placed Offline. The diagnostics are initiated
internally by the RAID controller module.
• The RAID controller module was manually placed Offline.
Physical Disk - Loss of A communication path with a physical disk has been lost.
Path Redundancy
Power Supply/Cooling Fan Power to one of the power supply/cooling fan modules has been lost.
Module - No Power Input
RAID Controller Module The RAID controller module listed in the Details area cannot determine the board identifier for the alternate RAID controller module
Board Identifier Cannot Be in this storage array.
Determined
RAID Controller Module The RAID controller module was manually placed in Service mode for diagnostic or recovery reasons at the instruction of a
In Service Mode technician.
RAID Controller Module A memory parity error was detected on a RAID controller module in this storage array.
Memory Parity Error
RAID Controller Module One of the RAID controller modules in this storage array is incompatible with the other RAID controller module.
Mismatch
RAID Controller Module A RAID controller module detected an unsupported cabling configuration.
Miswire
RAID Controller Submodel The submodel number associated with this RAID controller module was not set at the factory or it is not supported by the RAID
Not Supported controller module firmware.
Removed Battery The battery in the RAID controller module is not present, probably because a new RAID controller module was inserted without a
battery or the battery was not properly connected.
Removed EMM Module An EMM module has either been removed from the expansion enclosure or is present but is not seated properly.
Removed Fan Module A fan has been removed from the enclosure.
Removed Power A power supply/cooling fan module has been removed from an enclosure in the storage array.
Supply/Cooling Fan
Module
SAS Device Limit The storage array contains more than the allowed number of total expansion enclosures.
Exceeded
SAS Device Miswire The storage array contains an improper connection from the source enclosure to the expansion enclosure(s).
Snapshot Repository All of the repository virtual disk's available capacity has been used.
Virtual Disk Capacity -
Full
Snapshot Repository A snapshot repository virtual disk capacity exceeded a warning threshold level. If the repository virtual disk's capacity becomes full,
Virtual Disk Capacity - its associated snapshot virtual disk can fail.
Threshold Exceeded
Snapshot Virtual Disk The Snapshot Virtual Disk feature is out of compliance. This normally occurs if:
Feature - Out Of
Compliance • You migrated physical disks with Snapshot Virtual Disk feature data into a storage array and the feature is not enabled
• You migrated physical disks into a storage array already containing snapshot virtual disks and the addition of these snapshot
virtual disks now exceeds the total number of snapshot virtual disks allowed.
• You disabled the Snapshot Virtual Disk feature on a storage array where the feature is supported and you have existing snapshot
virtual disks present.
Storage Array Component One or both of the RAID controller modules in this storage array cannot communicate with the storage array component listed in the
- Loss of Communication Details area.
Uncertified Physical Disk An unsupported physical disk has been inserted into the storage array.
Uncertified EMM The storage array currently contains an expansion enclosure in which one or both of the EMMs are uncertified.
Unknown Failure Type The failure type cannot be determined.
Unreadable Sectors Unreadable sectors have been detected on one or more virtual disks.
Detected
Unreadable Sectors Log The Unreadable Sectors log has been filled to its maximum capacity.
Full
Unrecovered Interrupted The process of recovering from an interrupted write has failed. An interrupted write occurs when power fails or a RAID controller
Write module resets while there is data still in cache.
Unsupported Expansion Your storage array contains one or more unsupported expansion enclosures.
Enclosure


Virtual Disk - Hot Spare in One or more physical disks failed and hot spare physical disks automatically took over for the failed physical disks. The data on the
Use virtual disks is still accessible.
Virtual Disk Copy Feature The Virtual Disk Copy feature is out of compliance. This normally occurs if:
- Out Of Compliance
• You migrated physical disks with virtual disk copy data into a storage array where the feature is not enabled.
• You disabled the Virtual Disk Copy feature on a storage array where the feature is authorized and virtual disk copies are
present.
Virtual Disk Copy There was either a read error from this copy pair's source virtual disk or a write error to this copy pair's target virtual disk that caused
Operation Failed the copy operation to fail.
Virtual Disk Not On There is a problem accessing the RAID controller module listed in the Recovery Guru Details Area. Any virtual disks that have this
Preferred Path RAID controller module assigned as their preferred path will be moved to the non-preferred path (alternate RAID controller module).
This procedure will help you pinpoint the problem along the data path. Because the virtual disks will be moved to the alternate RAID
controller module, they should still be accessible; therefore, no action is required on the individual virtual disks. Possible causes
include:
• The RAID controller module failed a manually initiated diagnostic test and was placed Offline.
• The RAID controller module was manually placed Offline or is in Service Mode.
• There are disconnected or faulty cables.
• A host adapter failed.
• The storage array contains a defective RAID controller module.

Expires 2/3/2011 12:22:48 PM Recovery Guru This document is Dell Confidential
Controller Log Collection

You can generate support data for a storage array to help with remote troubleshooting and issue analysis. Follow these steps to collect storage array support data:
1. On the Support tab, click Gather Support Information.

2. Click Browse to display the Collect All Support Data dialog box.
3. In the Save in drop-down box, navigate to the location where you want the report saved.
4. Type a meaningful name in the File name text box, and then click Save. (A combination of array name and date is helpful in logging an issue over time.)
5. Click Start to save the compressed (zip) file containing support data to the location chosen above.

Expires 2/3/2011 12:22:48 PM Controller Log Collection This document is Dell Confidential
Hard Disk Drive Troubleshooting

The following document is meant to be used as a guide to troubleshooting the most common physical disk issues. The ideal way to do this would be to learn this
document thoroughly from the beginning to the end. However, that scenario will probably not pan out. The second best method would be to use this document in a
two pronged approach:
Hard Disk Drive Troubleshooting
1. Read and understand the “How to” sections of the document. These sections will help you understand some useful troubleshooting skills
2. A quick read through of the remaining document will give you an understanding of the most common issues and the troubleshooting techniques for them
The document can then be used as a quick reference guide for troubleshooting. Searching for specific Recovery Guru Events should lead you to the appropriate
sections. Engineering has provided some additional details where appropriate and these are shown in RED.

Expires 2/3/2011 12:22:48 PM Hard Disk Drive Troubleshooting This document is Dell Confidential
Controller Troubleshooting
This document is meant to be used as a guide to troubleshooting the most common controller issues. The ideal way to do this would be to learn this document
thoroughly from the beginning to the end. However, that scenario will probably not pan out. The second best method would be to use this document in a two
pronged approach:
Controller Troubleshooting
1. Read and understand the “How to” sections of the document. These sections will help you understand some useful troubleshooting skills.
2. A quick read through of the remaining document will give you an understanding of the most common issues and the troubleshooting techniques for them.

The document can then be used as a quick reference guide for troubleshooting. Searching for specific Recovery Guru Events should lead you to the appropriate
sections. Engineering has provided some additional details where appropriate and these are shown in RED.

Expires 2/3/2011 12:22:48 PM Controller Troubleshooting This document is Dell Confidential
Virtual Disk Not on Prefered Path

This link contains information about Prefered Path Configuration for the Dell PowerVault MD3000i for use in VMWare ESX/ESXi 3.5 Server Applications and
Microsoft Windows 2003/2008 Server Applications.
Prefered Path Configuration for the Dell PowerVault MD3000i

Expires 2/3/2011 12:22:48 PM Virtual Disk Not on Prefered Path This document is Dell Confidential
Power Issues
Watch for possible power issues based on the indications described in the following table.
Power Issues
Problem Action
• Enclosure-status indicators show a 1. Confirm that at least two drives are present in the enclosure; a minimum of two drives must be installed.
problem 2. Check the fault LEDs on the rear of the power supply to locate the faulty power supply.
• Power-supply fault indicators are lit 3. Turn off the enclosure and attached peripherals, and disconnect the enclosure from the electrical outlet.
4. Ensure that the power supply is properly installed by removing and reinstalling it.
5. If the problem is resolved, skip the rest of this procedure. If the problem persists, remove the faulty power
supply.
6. Install a new power supply.
CAUTION:
Power supply/cooling fan modules are hot-pluggable. The enclosure can operate on a single functioning power supply/cooling fan module; however, both
modules must be installed to ensure proper cooling. The fans in both supplies are powered by a common 5 volt bus. The fans in a failed power supply will
continue to operate as long as the power supply remains seated in the enclosure. A single power supply/cooling fan module can be removed, if necessary, from
the enclosure for up to five minutes, provided that the other module is functioning properly. After five minutes, the enclosure will overheat and may cause an
automatic thermal shutdown.
NOTE:
After installing a power supply/cooling fan module, allow several seconds for the enclosure to recognize the power supply and determine whether it is working
properly.

Expires 2/3/2011 12:22:48 PM Power Issues This document is Dell Confidential
Cooling Issues
Watch for possible cooling issues based on the indications described in the following table.
Cooling Issues
Problem Action
• MDSM issues a fan-related error message Ensure that none of the following conditions exist:
• Ambient temperature is too high

• External airflow is obstructed
• A power supply/cooling fan module has failed
Watch for possible fan issues based on the indications described in the following table.
Troubleshooting a Fan
Problem Action
• Enclosure-status indicator is amber • Check event logs for fan related issues
• MDSM issues a fan-related error message • Locate the malfunctioning fan


• Fan status indicator indicates a problem with • Ensure that a faulty power supply/cooling fan module is properly connected to the enclosure midplane
the fan until it is replaced
• If the problem is not resolved, install a new power supply/cooling fan module

Expires 2/3/2011 12:22:48 PM Cooling Issues This document is Dell Confidential
Log Reading
On this page you will find a presentation on MD3000/MD3000i log reading. Click on this link to download the zip file for the presentation. Once the file is
downloaded, extract the executable file and run it to view the presentation.

Expires 2/3/2011 12:22:48 PM Log Reading This document is Dell Confidential
Recovery Guru
The text found on the Recovery Guru pages is meant to provide a point of reference and assist the support technician know what the embedded MDSM Recovery
Guru information will report to the customer.
The Recovery Guru pages are meant simply as a reference to assist in knowing what the Recovery Guru will report and are not meant as a replacement to
troubleshooting (although they will vastly help). To view them, navigate to the MD3000 / MD3000i Recovery Guru training pages.

Expires 2/3/2011 12:22:48 PM Recovery Guru This document is Dell Confidential
MD3000/MD3000i Delta Knowledge Articles

When troubleshooting customer issues with the PowerVault MD3000 and MD3000i you should consider referring to the following Delta Knowledge articles for
posible solutions to your customer's issue:
1. Solution ID #74083 - MD3000 faulty DIMM on controller caused slow performance, controller panic and loss of management.
2. Solution ID #74371 - How to troubleshoot an MD3000 or MD3000i RAID controller that is in a reboot loop or panic condition.
3. Solution ID #74401 - How to change the management port settings on an MD3000/MD3000i using a serial connection.
To access the information in these Delta solutions, please navigate to kcs.dell.com, and search for the specific solution ID number.

MD3000/MD3000i Delta Knowledge
Articles
Procedures - Setup and Usage

Procedures List
The following procedures are structured and ordered in a manner that resembles the user's setup and operation experience. Maintenance and troubleshooting
procedures that approximate what personnel might see in a support role are also included.
1. Procedure 1 Installation of the Management Software, installation and configuration of the iSCSI initiator, along with management and discovery
of storage -
The following procedures show the steps necessary to install the Modular Disk Storage Manager (MDSM) software, install and configure the iSCSI initiator,
discover the MD3000i storage array and add hosts with Windows Server, Red Hat Linux, and SUSE Linux.
◦ MDSM installation and storage discovery Reference
◦ iSCSI host configuration for Windows (using IPv4) Reference
◦ iSCSI host configuration for Windows (using IPv6 on Windows 2008) Reference
◦ iSCSI host configuration for Red Hat Enterprise Linux Reference
2. Procedure 2 Reference Name the array, assign controller IP addresses, and synchronize the system clocks - This procedure shows the steps necessary
to name the array, assign IP addresses to the controllers, and synchronize the system clocks. The steps are also shown for adding SMcli.exe to the path
statement for ease of use at the command line.
3. Procedure 3 Reference Creation of Disk Groups and Virtual Disks - These procedures show the steps necessary to create Disk Groups and several types
of Virtual Disks. The procedures are identical for both the MD3000 and the MD3000i. Also shown are the steps for creating virtual disk slices on a disk


group's free space. It also shows the assignment of virtual disks to a host, using the "map now"and "map later" options, and the method of assigning the disks
under both circumstances. The procedure also shows the un-assignment of a virtual disk from a host.
4. Procedure 4 Reference Creation of Hot Spares - Automatic and Manual - This procedure shows the steps necessary to create hot spares, both
automatically and manually.
5. Procedure 5 Reference Setup of In-Band Management - This procedure shows the steps necessary to set up in-band management connections to the
MD3000i.
6. Procedure 6 - This procedure is currently unavailable.
7. Procedure 7 Reference Set and Reset the Administrator Password - This procedure shows the steps necessary to set or change the administrator password
in MDSM. It also shows the steps needed to reset a lost/forgotten administrator password through the PS/2 serial (debug) port.
8. Procedure 8 Reference Save, Clear, and Recreate the Storage Configuration - This procedure shows the steps necessary to save the storage array
configuration, as well as the steps to clear the configuration. It also shows the steps to recreate a storage configuration.
9. Procedure 9A Flash RAID Controller NVSRAM - This procedure shows the steps necessary to flash the firmware and NVSRAM on the RAID Controller.
Procedure 9B Flash Physical Disk Firmware - This procedure shows the steps necessary to flash the physical disk firmware.
10. Procedure 10 Reset Array Service Tag - This procedure shows the steps necessary to reset the service tag on the array after replacement of the backplane.
11. Procedure 11 Reference Battery Age Reset - This procedure shows the steps necessary to reset the battery age after replacing the battery in a controller.
12. Procedure 12 Reference Generate Key File and Enable Premium Features - This procedure shows the steps necessary to generate the activation key file
that enables the Premium Features on the array. It also shows the steps necessary to disable the premium features at the command line so the key file can be
reloaded and the premium features re-enabled.
13. Procedure 13 Reference Create a Snapshot of a Virtual Disk - This procedure shows the steps necessary to create a snapshot of a virtual disk, including
the creation of the repository drive.
14. Procedure 14 Reference Create a Virtual Disk Copy - This procedure shows the steps necessary to create a virtual disk copy and to modify its permissions
from read-only to read-write, so that the same host can mount the drive and modify the Windows disk signature.
15. Procedure 15 Reference Collection of Support Files - This procedure shows the steps necessary to perform the collection of Support files.
16. Procedure 16 Reference Recovery of Disk Groups and Virtual Disks - This procedure shows the command syntax used in SMcli to recover disk groups
and virtual disks. The recover command bypasses the "write-zeroes" function that is inherent in the "create virtualdisk" command.
17. Procedure 17 Reference Capacity Expansion of Disk Groups and Virtual Disks - This procedure shows the command syntax used in SMcli to expand the
capacity of a disk group, followed by the expansion of a virtual disk contained within that disk group.
18. Procedure 18 Reference Setup Email and SNMP - This procedure shows the steps necessary to setup email notification and SNMP.
19. Procedure 19 Reference Procedure for changing controller ownership of a Virtual Disk - This set of procedures demonstrates the steps necessary to
change the controller ownership of a Virtual Disk.

Expires 2/3/2011 12:22:48 PM Procedures - Setup and Usage This document is Dell Confidential
Modular Disk Storage Manager Simulator

This page contains the link to the files needed to install the simulator as well as the information needed to install and run it.
MDSM iSCSI Dual Port Simulator

To run the simulator, double-click on one of the bat files. To start the CLI, run SMcliBulldogSimulatorTopology_1_4pkg.bat (for example) in a terminal window,
after the Simulator/Demo has loaded. To connect, an example command would be:
SMcliBulldogSimulatorTopology_1_4pkg.bat localhost
If the simulator does not start, be sure that the Demo Configuration Editor is not running and there are not any other simulator windows running.
After the simulator has started, the user may wish to interact with it through the Command Line Interface. To start the CLI, run SMcliDell-
SimBP_Demo__DualPortpkg.bat in a terminal window after the Simulator has loaded. To connect, the command syntax would follow this structure: SMcliDell-
SimBP_Demo__DualPortpkg.bat localhost.
The zip file package can be downloaded at the link below.
• Simulator Zipfiles
Expand the files into a new directory folder and choose the appropriate simulator by selecting a .bat file.

Available Simulator Configurations
This is the topology simulated in version 1.4.
This is an image of the topology simulator 1 dot 4.



Modular Disk Storage Manager
Simulator
MD Utility and Analyzer Tools

Dell Engineering has created the MD Analyser tool for use when troubleshooting issues with the PowerVault MD3000 and MD3000i.
PowerVault MD Analyzer Tool
Dell Engineering has recorded some Microsoft LiveMeeting sessions focusing on the following tools:
• PowerVault MD Utility
• PowerVault MD Analyser

Expires 2/3/2011 12:22:48 PM MD Utility and Analyzer Tools This document is Dell Confidential
2nd Gen Online KC

When taking your test please be sure to follow these instructions
1. Kindly avoid using browser's Back / Forward buttons and shortcuts.

2. Do not use your browser's close button to close this window. Doing so will abandon your assessment session and your progress will be lost.
3. Please use the next or (if available) previous buttons to navigate the assessment and finish with no interruptions.
4. Never open multiple delivery sessions simultaneously. Doing so will abandon your assessment session and your progress will be lost.
Click here to take assessment
NOTE:
The Knowledge Check for the PowerVault MD3000i is the same as the Knowledge Check for the PowerVault MD3000. If you have completed and passed the
Knowledge Check for the PowerVault MD3000, the Dell Training tool will report that you have successfully taken this Knowledge Check and prevent you
from taking it again here.

Expires 2/3/2011 12:22:48 PM 2nd Gen Online KC This document is Dell Confidential

Release 2.1 Online KC

When taking your test please be sure to follow these instructions
1. Kindly avoid using browser's Back / Forward buttons and shortcuts.

2. Do not use your browser's close button to close this window. Doing so will abandon your assessment session and your progress will be lost.
3. Please use the next or (if available) previous buttons to navigate the assessment and finish with no interruptions.
4. Never open multiple delivery sessions simultaneously. Doing so will abandon your assessment session and your progress will be lost.
• Click here to take the assessment
NOTE:
The Knowledge Check for the PowerVault MD3000 is the same as the Knowledge Check for the PowerVault MD3000i. If you have completed and passed the
Knowledge Check for the PowerVault MD3000i, the Dell Training tool will report that you have successfully taken this Knowledge Check and prevent you
from taking it again here.

Expires 2/3/2011 12:22:48 PM Release 2.1 Online KC This document is Dell Confidential
Remote Install Documentation

This page is intended to provide the Remote Installation (RI) team members, and other interested internal parties, a quick place to go to reference critical documents
that have been found to be useful in the performance of remote installation duties. It is not an exhaustive resource, but is intended on being a dependable reference
point to obtain information on common tasks that the RI team may be involved in.
Policies and Procedures

The training site does not house, nor maintain, policies and procedures for the RI teams, but serves to provide dependable and useful technical and training
resources. If you need to determine your regional policies and procedure given a specific situation, please visit your region's Policies and Procedure website.
Key Remote Installation Technical References

The Dell Remote Installation team has identified the following documents as useful reference tools for performing remote installation tasks relating to the MD3000i
platform.
How To Set MD3000i Management IP Addresses With The Serial Cable
The MD3000i ESX VMware Deployment Guide
Red Hat Enterprise Linux 5 iSCSI Walk-through Guide document.
Remote Installation Videos

See the following pages for Adobe Captivate demonstration modules to watch the installation on different operating systems.

Expires 2/3/2011 12:22:48 PM Remote Install Documentation This document is Dell Confidential
Windows Install Video

The Dell Remote Installation team has created a video to assist you as a practical online Computer Based Training reference to help guide you through a 'virtual lab'
for performing remote installation procedures.
Pre-requisites
This video assumes that you have met the following prerequisites:
• Basic iSCSI Knowledge

• Basic Networking Knowledge
If you need to refresh your knowledge on these prerequisites, you may wish to visit the following training links:
• iSCSI Fundamentals
• Networking Fundamentals
Video Content
This video contains the following information covering installation procedures on the following topics/items:

1. Installing the MD3000i™ Software

2. Discovering the Array — Automatic Method
3. Discovering the Array — Manual Method
4. Renaming the Array
5. Configure Array Ethernet Management Ports
6. Setup Array Email Alerts
7. Set Array Password
Image of the Captivate 8. Configure Array iSCSI Host Ports
screen 9. Configure Host iSCSI Network Cards
10. Configure Host iSCSI Initiator — Windows™ 2003
11. Configure Host iSCSI Initiator — Windows™ 2008
12. iSCSI Initiator Configuration Utility
13. Configure Host Access
14. Configure Hot Spares
15. Create Disk Groups and Virtual Disks
16. Making a Virtual Disk Show up in the Host OS
Use the following link to download the Adobe™ Captivate™ training module video: MD3000i_Windows.zip
To view the video, download the file and uncompress on a local hard drive and run the executable (i.e., MD3000i_Windows.exe).

Expires 2/3/2011 12:22:48 PM Windows Install Video This document is Dell Confidential
RHEL5 Install Video

Pre-requisites
• Basic Linux Knowledge

• Implementing MD3000i forWindows Environment
Video Content
Click the image below to start the video in a new web browser window.
Image of the Captivate

screen
Use the following link to download the Adobe™ Captivate™ training module video: MD3000i_RHEL5.zip
To view the video, download the file and uncompress on a local hard drive and run the executable (i.e., MD3000i_RHEL5.exe).

Expires 2/3/2011 12:22:48 PM RHEL5 Install Video This document is Dell Confidential
VMware Install Video

Pre-requisites

• Basic VMware Knowledge

Video Content
Click the image below to start the video in a new web browser window.
Image of the Captivate

screen
Use the following link to download the Adobe™ Captivate™ training module video: MD3000i_VMware.zip
To view the video, download the file and uncompress on a local hard drive and run the executable (i.e., MD3000i_VMware.exe).

Expires 2/3/2011 12:22:48 PM VMware Install Video This document is Dell Confidential
MD3000i : Document Outline

Expires 2/3/2011 12:22:48 PM Course Outline This document is Dell Confidential
PowerPoint Presentations
The following documentation is used in a classroom environment.
• Presentation 1 - MD3000i Overview - This presentation shows the marketing position and features of the MD3000i.
• Presentation 2 - MD3000i - iSCSI - This presentation reviews essental information regarding the use and deployment of iSCSI.
• Presentation 3 - MD3000i Hardware - This presentation shows the hardware FRUs and describes their properties.
• Presentation 4 - MD3000i and MDSM Highlights and Deltas - This presentation describes the highlights and deltas between the MD3000 and the MD3000i.

Expires 2/3/2011 12:22:48 PM PowerPoint Presentations This document is Dell Confidential
Classroom Setup
Introduction
The MD3000i classroom training is designed to give the student a general understanding of how to setup, configure, and troubleshoot an MD3000i Storage Array.
Classroom Schedule
The training can be performed in any classroom that will accommodate the number of racked servers and storage arrays that will allow a maximum of two students
per array.
Classroom Setup Time Estimate
clock
Total time for this class setup is 6 to 8 hours;
the servers need to be imaged, and Ethernet cabling
needs to be organized, additional Ethernet switches
installed as needed, and any remaining configuration on
the arrays cleared.

The servers should be running Windows 2003 SP1.
The knowledge check was created in DTT as "PowerVault-MD3000i-NAS-DAS".
Objectives
The following is a list of terminal objectives for the class. This list can be printed out and handed to the students as an overall list of objectives for the class:
• Identify software and hardware used in a PowerVault MD3000i Storage Array.

• Install the software used in an MD3000i Storage Array.
• Installl and configure the Microsoft iSCSI initiator
• Configure the iSCSI target and initiator settings to allow access
• Troubleshoot software used in an MD3000i Storage Array and its attached hosts.
• Troubleshoot hardware used in an MD3000i Storage Array.
• Configure the MD3000i management software and discover the attached storage array.
• Create Disk Groups and create and name LUNs on the MD3000i.
• Assign LUNs to attached hosts or host groups.
• Create a hot spare.
• Upgrade firmware on the phyiscal disks, and RAID Controllers.
• Use the Premium Feature Keys to create a Virtual Disk Copy and a Snapshot.
• Use SMcli to save, modify and restore a configuration on the MD3000i.
Prerequisites
• Working knowledge of Microsoft Windows Server 2003®.
• Working knowledge of iSCSI
Materials Required
The following materials are required for each two-person station:
• 1 - Ethernet switch and cabling.

• 1 - PowerEdge server (8G or 9G) running Windows 2003® 64 bit, SP1.
• 1 - MD3000i Storage Array.
• 1 - laptop or desktop for RDP connection to the servers.
Course Preparation
Software Configuration Nodes
Have the Windows 2003 operating system installed. The students will load the software as the labs progress.
Cabling Diagram
The cabling shall be accomplished in accordance with the supported cabling configurations outlined and specified in the Training pages.
IP Addressing Scheme
IP addresses may be hard coded or DHCP may be used for all Ethernet ports other than the one used for RDP access. Hosts and storage arrays should be configured
to be on the same subnet for out-of-band discovery by management hosts.
Total Class Time Estimates
clock
Total time for the basics class is 16 hours.

Expires 2/3/2011 12:22:48 PM Classroom Setup This document is Dell Confidential
Class Overview
Introductions
clock
Total time for introductions is about 30 minutes.

Introduce yourself and then go around the class having the students introduce themselves.
You may want to have the students state their level of enterprise experience. You may also ask the students to state what they would like to get out of the class.
This information will help you as the instructor understand the class expectations as well as the students' level of experience. Additionally, this will break some of
the tension in the classroom and allow the student to get to know one another.
Class Overview
clock
Total time for introductions is about 10 minutes.
Provide the class with a quick overview of what the one day class will cover.
Class Overview
• Instructor and class participant introductions
• MD3000 Advancement Overview
• MD3000 Advancement presentation with labs.
Lab Station Overview

TIME:Total time for lab station overview is about 10 minutes.
Ask the students gather around a lab station and explain what hardware makes up each station, and how it is connected together.
Lab Station Configuration
Each table is a lab station.
List of items at each station (hosts and storage are remotely mounted):
• 2 PE1950 servers.
• One MD3000 array.

Expires 2/3/2011 12:22:48 PM Class Overview This document is Dell Confidential
Class Outline
All of the times listed after the PowerPoint are the total amount of time needed for each module.
Day One
Start with the overview PowerPoint.
Module One
Presentation Time Lab(s) Lab Time(s)
Install Microsoft STORport hotfix
Load driver for SAS5/E
Powerpoint Presentations: Install MDSM software
MD3000-01-Overview.ppt Discover the array out of band using netCfgShow
Number of Hours Number of Hours
MD3000-02-Hardware.ppt Name the Array
4 4
MD3000-03-Architecture.ppt Change IP addresses if needed
MD3000-04-MDSM.ppt Create Disk Groups and Virtual Disks
Assign VD ownership to host
Scan for new LUNs on host and format as drives
Day Two
Module Two
Presentation Time Lab(s) Lab Time(s)
Reset a lost administrator password
Presentation Number of Hours Gather the support files Number of hours
None N/A Flash the controller Firmware and NVSRAM 8
Save the array configuration to a file
Edit config file, creating an additional LUN


Change the segment size in the config file
Recover a deleted LUN

Expires 2/3/2011 12:22:48 PM Class Outline This document is Dell Confidential
Useful Documents
iSCSI SAN Best Practice Documentation
Click on the link below:
IP SAN Best Practice White Paper.

Expires 2/3/2011 12:22:48 PM Useful Documents This document is Dell Confidential
MD3000i : Document History

Document History
Date Owner Page
Requested By Reviewed By Approved By
Change
Date: 2011-01-05 Owner:Terry Thompson Page: 1_2Overview.asp

Requested By: David Spencer Reviewed By: Approved By: David Spencer
Changes: Added page regarding new firmware.
Date: 2010-06-09 Owner:David Spencer Pages: navigation.xml

RI_Documentation.asp
RI_Videos.asp
docinfo.xml
Requested By: Joseph Frederick Reviewed By: Approved By: David Spencer
Changes: Added remote installation information as provided by the RI team (video and doc reference).
Date: 2010-05-13 Owner:Brian Urbanek Page: ts_log_reading.asp

Requested By: Fusion Incident # Reviewed By: Approved By: David Spencer
16345234
Changes: Added presentation Log_reading.zip, by Eli Barthelman.
Date: 2010-02-09 Owner:Brian Urbanek Page: several pages

Requested By: Product Group Reviewed By: Approved By: Brian Urbanek
Changes: Several updates including support information
Date: 2009-09-16 Owner:Bruce Corbett Page: release_2_1.asp, release_2_1_w2k8.asp, release_2_1_sles11.asp,

release_2_1_fw.asp, release_2_1_CR.asp
Requested By: NPI Roadmap Reviewed By: Approved By: David Spencer
Changes: Added information and KC for release 2.1
Date: 2009-09-01 Owner:David Spencer Pages: navigation.xml

RecoveryGury.asp
Requested By: Beth Warner Reviewed By: Approved By: David Spencer
Jeff Glenn
Changes: Updated troubleshooting information with reference to the Recovery Gury training pages.
Date: 2009-06-01 Owner:David Spencer Page: navigation.xml

Requested By: Chris Berrean Reviewed By: Approved By: David Spencer


Document History
Date Owner Page
Change
Changes: SPM discovered that the material he had provided for Fusion #14686637 was not fully vetted by engineering. Removing reference to
ts_preferred_path.asp from navigation table; we will update once the accurate information is provided.
Date: 2009-05-27 Owner:David Spencer Pages: enclosure_cablin.asp

ts_preferred_path.asp
navigation.xml
Requested By: Chris Berrean Reviewed By: Approved By: David Spencer
Changes: Per request for WWSPM, IPS and the PV DAS/SAN Core Team via Fusion #14686637, added requested troubleshooting information and updated
cabling reference to externally available support matrix document.
Date: 2009-03-25 Owner:David Spencer Page: G2_RAID6.asp

Requested By: Bhagbat Mohapatra Reviewed By: Approved By: Tammy Perkins
Changes: Per Fusion ticket 14513815, clarified why RAID6 requires five drives with the PowerVault MD3000 and PowerVault 3000i.
Date: 2009-03-24 Owner:David Spencer Page: G2_simplex_replacement.asp

Requested By: Chris Berrean Reviewed By: Approved By: Tammy Perkins
Changes: Per Fusion ticket 14444543, Update to MD3000i pages to reflect need to update firmware after simplex replacement in case a newer firmware is
available.
Date: 2009-03-13 Owner:Mark Smith Page: system_overview.asp

Requested By: David Spencer Reviewed By: Approved By: Tammy Perkins
Changes: RHEL 5.3 support added. Link to support matrix and note added.
Date: 2009-03-02 Owner:Bruce Corbett Page: iSCSI_RAID_module.asp

Requested By: jason_ Reviewed By: GTAD Approved By: Tammy Perkins
burroughs@dell.com - fusion ticket Process
14339178
Changes: Added additional info regarding the iSCSI port layout on the RAID controller modules.
Date: 2008-12-17 Owner:Bruce Corbett Page: review.asp.asp

Requested By: David Spencer Reviewed By: Approved By: Tammy Perkins
Changes: Fixed the link for the Online Second Gen KC.
Date: 2008-12-03 Owner:Bruce Corbett Page: c_panel.asp

Requested By: Matthias Vogler - Fusion Reviewed By: Approved By: Tammy Perkins
Incident #13505688
Changes: Added a warning regarding the fucntionality of the mode select switch when attaching additional expansion enclosures.
Date: 2008-11-27 Owner:Mark Smith Page: iSCSI best practice ref doc added
Changes: Added Useful Documents page
Date: 2008-11-12 Owner:Brian Urbanek Page: Second Generation Section, and Virtualization Sections added
Changes: Added several pagess and in the Second Generation Section, and the Virtualization Section was added.
Date: 2008-07-03 Owner:Barry O Sullivan Page: Configuration Utility section added

Changes: Added Overiew, Launching the utility, array configuration and host configuration.
Date: 2008-02-28 Owner:Mark Smith Page: IPV6 support added. Windows 2008 and revised Linux support added
Requested By: Becky Wright Reviewed By: Jason Groce Approved By: David Spencer
Changes: Added IPV6 iSCSI setup and configuration. Added Windows 2008, revised Linux and revised clustering support.


Document History
Date Owner Page
Change
Date: 2008-02-27 Owner:Mark Smith and Page: need2know, global_differences, supported_configuration_changes,
Bruce Corbett supported_hardware, firmware_changes, simplex_controller_replacement,
single_controller_replacement
Requested By: David Spencer Reviewed By: Approved By:
Changes: Added info regarding SATA drive support to address single controller replacement issues.
Date: 2007-12-12 Owner:Jason Groce Page: System Overview

Requested By: Chris Berrean Reviewed By: Paul Fragale Approved By: Jesse Johns
Changes: Added VMWare to supported host.
Date: 2007-08-23 Owner:John Ingle Page: All

Requested By: Engineering Reviewed By: STS Approved By:
Editors/Engineering
Changes: Updates, rewording and corrections
Date: 2007-08-02 Owner:John Ingle Page: All

Requested By: PG Reviewed By: ETS Approved By:
Editors/Engineering
Changes: Initial Document Creation

Expires 2/3/2011 12:22:48 PM Document History This document is Dell Confidential

Previous
Copyright 1999-2008 Dell Inc. For Dell Employees and Dell Service Providers only.
inside.us.dell.com | Privacy Policy | About Dell | Contact Us | About Us

Dell - MD3000i - Printer-Friendly Format

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Dell - MD3000i - Printer-Friendly Format

Uploaded by

Copyright:

Available Formats

Dell - MD3000i - Printer-Friendly Format Page 1 of 174

Expand All Collapse All

file://C:\Users\Ironman\AppData\Local\Temp\Framework\Dell - MD3000i - Printer-Friendl... 2/3/2011

file://C:\Users\Ironman\AppData\Local\Temp\Framework\Dell - MD3000i - Printer-Friendl... 2/3/2011

Printed 2/2/2011 12:22:48 PM MD3000i For Dell Employees Only

Page Break Divider. Does not show when printed.

file://C:\Users\Ironman\AppData\Local\Temp\Framework\Dell - MD3000i - Printer-Friendl... 2/3/2011

Operating System Support for Management

Modular Disk Storage Manager

Printed 2/2/2011 12:22:48 PM MD3000i For Dell Employees Only

Page Break Divider. Does not show when printed.

Coexistence with MD32xx/i

This is a diagram of a host connected to a MD32xx and MD3000.

file://C:\Users\Ironman\AppData\Local\Temp\Framework\Dell - MD3000i - Printer-Friendl... 2/3/2011

This is a diagram of a host connected to a MD32xxi and MD3000i.

Coexistence in a Windows Environment

Coexistence in a Linux Environment

Printed 2/2/2011 12:22:48 PM MD3000i For Dell Employees Only

Page Break Divider. Does not show when printed.

Upgrading to Release 2.1 Firmware

Printed 2/2/2011 12:22:48 PM MD3000i For Dell Employees Only

Page Break Divider. Does not show when printed.

For full information on replacing a controller click HERE.

file://C:\Users\Ironman\AppData\Local\Temp\Framework\Dell - MD3000i - Printer-Friendl... 2/3/2011

Printed 2/2/2011 12:22:48 PM MD3000i For Dell Employees Only

Page Break Divider. Does not show when printed.

• Configurations with two MD3000s

Configurations with two MD3000s

Single Host connected to Two MD3000 Storage Arrays

Image: Single Host connected to Two MD3000 Storage Arrays

Two Hosts connected to Two MD3000 Storage Arrays

file://C:\Users\Ironman\AppData\Local\Temp\Framework\Dell - MD3000i - Printer-Friendl... 2/3/2011

Image: Two Hosts connected to Two MD3000 Storage Arrays

Battery Learn Cycle

Creating Host to Virtual Disk Mappings

Additional Disk Group and Virtual Disk Expansion information

VD Copy is slow with SATA disks

Printed 2/2/2011 12:22:48 PM MD3000i For Dell Employees Only

Page Break Divider. Does not show when printed.

• Load Balancing in Windows 2008

Load Balancing in Windows 2008

• Least Path Weight

file://C:\Users\Ironman\AppData\Local\Temp\Framework\Dell - MD3000i - Printer-Friendl... 2/3/2011

file://C:\Users\Ironman\AppData\Local\Temp\Framework\Dell - MD3000i - Printer-Friendl... 2/3/2011

Navigating to the MPIO tab

Setting up the iSCSI Initiator on Windows 2008 R2

Performing Target Disco

• Local Adapter: Must be set to Microsoft iSCSI Initiator.

file://C:\Users\Ironman\AppData\Local\Temp\Framework\Dell - MD3000i - Printer-Friendl... 2/3/2011

Performing Target Disco

Configure CHAP Authentica

• click the Configuration tab

1. Local Adapter: Should always be set to Microsoft iSCSI Initiator.

Connect to the Target Stor

• Local Adapter: Must be set to Microsoft iSCSI Initiator.

file://C:\Users\Ironman\AppData\Local\Temp\Framework\Dell - MD3000i - Printer-Friendl... 2/3/2011

Connect to the Target Stor

Printed 2/2/2011 12:22:48 PM MD3000i For Dell Employees Only

Page Break Divider. Does not show when printed.

Installing the iSCSI Initiator on a SLES 11 System

To install the iSCSI initiator during SLES 11 installation:

Installing the iSCSI initiator after SLES 11 installation:

Supported File Systems in SLES 11