Reproduction in any manner whatsoever without the written permission of Dell Inc. is strictly
forbidden.
Trademarks used in this text: Dell, the DELL logo, and PowerVault are trademarks of Dell Inc.; Intel
and Pentium are registered trademarks of Intel Corporation; SUSE is a registered trademark of Novell
Inc. in the United States and other countries; Microsoft, Windows, and Windows Server are either
registered trademarks or trademarks of Microsoft Corporation in the United States and other countries;
Red Hat and Red Hat Enterprise Linux are registered trademarks of Red Hat Inc. in the United States
and other countries.
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. disclaims any proprietary interest in trademarks and
trade names other than its own.
Step 5: Configure CHAP Authentication on the Storage Array (optional). . . . 47
Configuring Target CHAP Authentication on the Storage Array
Configuring Mutual CHAP Authentication on the Storage Array
. . . . . . 47
. . . . . . 48
Step 6: Configure CHAP Authentication on the Host Server (optional)
. . . . . 49
If you are using Windows Server 2003 or Windows Server 2008
GUI version
If you are using Windows Server 2008 Core Version
If you are using Linux Server
If you are using RHEL 5 or SLES 10 SP1
If you are using SLES10 SP1 via the GUI
Step 7: Connect to the Target Storage Array from the Host Server
If you are using Windows Server 2003 or Windows Server 2008 GUI
If you are using Windows Server 2008 Core Version
If you are using a Linux Server
Viewing the status of your iSCSI connections
This guide outlines the steps for configuring the Dell™ PowerVault™ Modular Disk 3000i
(MD3000i). The guide also covers installing the MD Storage Manager software, installing and
configuring the Microsoft
PowerVault MD3000i Resource CD. Other information provided includes system requirements,
storage array organization, initial software startup and verification, and discussions of utilities and
premium features.
MD Storage Manager enables an administrator to configure and monitor storage arrays for optimum
usability. MD Storage Manager operates on both Microsoft
systems and can send alerts about storage array error conditions by either e-mail or Simple Network
Management Protocol (SNMP). These alerts can be set for instant notification or at regular intervals.
System Requirements
Before installing and configuring the MD3000i hardware and MD Storage Manager software, ensure
that the operating system is supported and minimum system requirements are met. For more
information, refer to the Dell™ PowerVault™ MD3000i Support Matrix available on support.dell.com.
Management Station Hardware Requirements
A management station uses MD Storage Manager to configure and manage storage arrays across the
network. Any system designated as a management station must be an x86-based system that meets
the following minimum requirements:
•Intel® Pentium® or equivalent CPU (133 MHz or faster)
•128 MB RAM (256 MB recommended)
•120 MB disk space available
•Administrator or equivalent permissions
•Minimum display setting of 800 x 600 pixels with 256 colors (1024 x 768 pixels with 16-bit color
recommended)
®
iSCSI and Linux initiators, and accessing documentation from the
®
Windows® and Linux operating
Introduction7
Introduction to Storage Arrays
A storage array includes various hardware components, such as physical disks, RAID controller modules,
fans, and power supplies, gathered into enclosures. An enclosure containing physical disks accessed
through RAID controller modules is called a RAID enclosure.
One or more host servers attached to the storage array can access the data on the storage array. You can
also establish multiple physical paths between the host(s) and the storage array so that loss of any single
path (through failure of a host server port, for example) does not result in total loss of access to data on the
storage array.
The storage array is managed by MD Storage Manager software running either on a host server or a
dedicated management station. On a host server system, MD Storage Manager and the storage array
communicate management requests and event information directly via iSCSI ports. On a dedicated
management station, MD Storage Manager communicates with the storage array either through an
Ethernet connection on the RAID controller modules or via the host agent installed on the host server.
Using MD Storage Manager, you configure the physical disks in the storage array into logical components
called disk groups, then divide the disk groups into virtual disks. You can make as many disk groups and
virtual disks as your storage array configuration and hardware permit. Disk groups are created in the
unconfigured capacity of a storage array, while virtual disks are created in the free capacity of a disk
group.
Unconfigured capacity is comprised of the physical disks not already assigned to a disk group. When a
virtual disk is created using unconfigured capacity, a disk group is automatically created. If the only
virtual disk in a disk group is deleted, the disk group is also deleted. Free capacity is space in a disk group
that has not been assigned to a virtual disk.
Data is written to the physical disks in the storage array using RAID technology. RAID levels define the
way in which data is written to physical disks. Different RAID levels offer different levels of accessibility,
redundancy, and capacity. You can set a specified RAID level for each disk group and virtual disk on your
storage array.
You can also provide an additional layer of data redundancy by creating disk groups that have a RAID
level other than 0. Hot spares can automatically replace physical disks marked as Failed.
For more information on using RAID and managing data in your storage solution, see the Dell™ PowerVault™ Modular Disk Storage Manager User’s Guide.
8Introduction
Hardware Installation
This chapter provides guidelines for planning the physical configuration of your Dell™ PowerVault™
MD3000i storage array and for connecting one or more hosts to the array. For complete information
on hardware configuration, see the Dell™ PowerVault™ MD3000i Hardware Owner’s Manual.
Storage Configuration Planning
Consider the following items before installing your storage array:
•Evaluate data storage needs and administrative requirements.
•Calculate availability requirements.
•Decide the frequency and level of backups, such as weekly full backups with daily partial backups.
•Consider storage array options, such as password protection and e-mail alert notifications for error
conditions.
•Design the configuration of virtual disks and disk groups according to a data organization plan.
For example, use one virtual disk for inventory, a second for financial and tax information, and a
third for customer information.
•Decide whether to allow space for hot spares, which automatically replace failed physical disks.
•If you will use premium features, consider how to configure virtual disk copies and snapshot
virtual disks.
About the Enclosure Connections
The RAID array enclosure is connected to an iSCSI-enabled host server via one or two RAID
controller modules. The RAID controller modules are identified as RAID controller module 0 and
RAID controller module 1 (see the PowerVault MD3000i Hardware Owner’s Manual for more
information).
Each RAID controller module contains two iSCSI In port connectors that provide direct connections
to the host server or switches. iSCSI In port connectors are labeled In-0 and In-1(see the PowerVault MD3000i Hardware Owner’s Manual for more information).
Each MD3000i RAID controller module also contains an Ethernet management port and a SAS Out
port connector. The Ethernet management port allows you to install a dedicated management
station (server or standalone system). The SAS Out port allows you to connect the RAID enclosure
to an optional expansion enclosure (MD1000) for additional storage capacity.
Hardware Installation9
Cabling the Enclosure
You can connect up to 16 hosts and two expansion enclosures to the storage array.
To plan your configuration, complete the following tasks:
1
Evaluate your data storage needs and administrative requirements.
2
Determine your hardware capabilities and how you plan to organize your data.
3
Calculate your requirements for the availability of your data.
4
Determine how you plan to back up your data.
The iSCSI interface provides many versatile host-to-controller configurations. For the purposes of this
manual, the most conventional topologies are described. The figures in this chapter are grouped
according to the following general categories:
•Direct-attached solutions
•Network-attached (SAN) solutions
Redundancy vs. Nonredundancy
Nonredundant configurations, configurations that provide only a single data path from a host to the
RAID enclosure, are recommended only for non-critical data storage. Path failure from a failed or
removed cable, a failed NIC, or a failed or removed RAID controller module results in loss of host access
to storage on the RAID enclosure.
Redundancy is established by installing separate data paths between the host and the storage array, in
which each path is to different RAID controller modules. Redundancy protects the host from losing
access to data in the event of path failure, because both RAID controllers can access all the disks in the
storage array.
Direct-Attached Solutions
You can cable from the Ethernet ports of your host servers directly to your MD3000i RAID controller
iSCSI ports. Direct attachments support single path configurations (for up to four servers) and dual path
data configurations (for up to two servers) for both single and dual controller modules.
Single Path Data Configurations
With a single path configuration, a group of heterogeneous clients can be connected to the MD3000i
RAID controller through a single physical Ethernet port. Because there is only the single port, there is no
redundancy (although each iSCSI portal supports multiple connections). This configuration is
supported for both single controller and dual controller modes.
Figure 2-1 and Figure 2-2 show the supported nonredundant cabling configurations to MD3000i RAID
controller modules using the single path data configuration. Figure 2-1 shows a single controller array
configuration. Figure 2-2 shows how four standalone servers are supported in a dual controller array
configuration.
10Hardware Installation
Figure 2-1. One or Two Direct-Attached Servers (or Two-Node Cluster), Single-Path Data, Single Controller (Simplex)
2
1
Management traffic
3
5
4
1standalone (one or
two) host server
4MD3000i RAID
Enclosure (single
controller)
2two-node cluster3Ethernet
management port
5corporate, public or
private network
Hardware Installation11
Figure 2-2. Up to Four Direct-Attached Servers, Single-Path Data, Dual Controllers (Duplex)
1
Management traffic
2
4
3
1standalone (up to
four) host server
4corporate, public or
private network
2Ethernet management
port (2)
3MD3000i RAID
Enclosure (dual
controllers)
Dual Path Data Configuration
In Figure 2-3, up to two servers are directly attached to the MD3000i RAID controller module. If the host
server has a second Ethernet connection to the array, it can be attached to the iSCSI ports on the array’s
second controller. This configuration provides improved availability by allowing two separate physical
paths for each host, which ensures full redundancy if one of the paths fail.
12Hardware Installation
Figure 2-3. One or Two Direct-Attached Servers (or Two-Node Cluster), Dual-Path Data, Dual Controllers (Duplex)
1
5
1standalone (one or
two) host server
4MD3000i RAID
Enclosure (dual
controllers)
2two-node cluster3Ethernet
5corporate, public or
private network
2
3
4
management port
(2)
Network-Attached Solutions
You can also cable your host servers to the MD3000i RAID controller iSCSI ports through an IP storage
area network (SAN) industry-standard 1GB Ethernet switch. By using an IP SAN "cloud" Ethernet
switch, the MD3000i RAID controller can support up to 16 hosts simultaneously with multiple
connections per session. This solution supports either single- or dual-path data configurations, as well as
either single or dual controller modules.
Figure 2-4 shows how up to 16 standalone servers can be attached (via multiple sessions) to a single
MD3000i RAID controller module through a network. Hosts that have a second Ethernet connection to
the network allow two separate physical paths for each host, which ensures full redundancy if one of the
paths fail. Figure 2-5 shows how the same number of hosts can be similarly attached to a dual MD3000i
RAID controller array configuration.
Hardware Installation13
Figure 2-4. Up to 16 SAN-Configured Servers, Single-Path Data, Single Controller (Simplex)
1
2
3
5
4
1up to 16 standalone
host servers
4MD3000i RAID
Enclosure (single
controller)
2IP SAN (Gigabit
Ethernet switch)
5corporate, public or
private network
3Ethernet
management port
14Hardware Installation
Figure 2-5. Up to 16 Dual SAN-Configured Servers, Dual-Path Data, Dual Controllers (Duplex)
1
2
3
5
4
1up to 16 standalone
host servers
4MD3000i RAID
Enclosure (dual
controllers)
2IP SAN (dual Gigabit
Ethernet switches)
5corporate, public or
private network
3Ethernet
management port
(2)
Attaching MD1000 Expansion Enclosures
One of the features of the MD3000i is the ability to add up to two MD1000 expansion enclosures for
additional capacity. This expansion increases the maximum physical disk pool to 45 3.5" SAS and/or
SATA II physical disks.
As described in the following sections, you can expand with either a brand new MD1000 or an MD1000
that has been previously configured in a direct-attach solution with a PERC 5/E system.
NOTICE: Ensure that all MD1000 expansion enclosures being connected to the MD3000i are first updated to the
latest Dell MD1000 EMM Firmware (available from support.dell.com). Dell MD1000 EMM Firmware versions prior to
A03 are not supported in an MD3000i array; attaching an MD1000 with unsupported firmware causes an uncertified
condition to exist on the array. See the following procedure for more information.
Hardware Installation15
Expanding with Previously Configured MD1000 Enclosures
Use this procedure if your MD1000 is now directly attached to and configured on a Dell PERC 5/E
system. Data from virtual disks created on a PERC 5 SAS controller cannot be directly migrated to an
MD3000i or to an MD1000 expansion enclosure connected to an MD3000i.
NOTICE: If an MD1000 that was previously attached to PERC 5 SAS controller is used as an expansion enclosure
to an MD3000i, the physical disks of the MD1000 enclosure will be reinitialized and data will be lost. All data on the
MD1000 must be backed up before attempting the expansion.
Perform the following steps to attach previously configured MD1000 expansion enclosures to the MD3000i:
Back up all data on the MD1000 enclosure(s).
1
2
While the enclosure is still attached to the PERC 5 controller, upgrade the MD1000 firmware to
version A03 or above. Windows systems users can reference the
users can reference the
3
Before adding the MD1000 enclosure(s), make sure the MD3000i software is installed and up to date.
For more information, refer to the
support.dell.com
a
Install or update (to the latest version available on
.
DUP.bin
package.
Dell™ PowerVault™ MD3000i Support Matrix
support.dell.com
each host server. Install or update (to the latest version available on
multipath drivers on each host server. The multipath drivers are bundled with Modular Disk
Storage Management install. On Windows systems, the drivers are automatically installed when a
Full or Host selection is made.
b
Using the MD Storage Manager, update the MD3000i RAID controller firmware to the latest
version available on
Stop all I/O to the array and turn off affected host systems attached to the MD3000i.
b
Turn off the MD3000i.
c
Turn off the MD1000 enclosure(s).
5
Referencing the applicable configuration for your rack (Figure 2-1 through Figure 2-5), cable the
support.dell.com (Support→
) and the NVSRAM (
).
Download Firmware→
Support→
MD1000 enclosure(s) to the MD3000i.
DUP.exe
package; for Linux kernels,
available on
) the MD Storage Manager on
support.dell.com
Download RAID
Download Firmware→
) the
Download
16Hardware Installation
6
Turn on attached units:
a
Turn on the MD1000 expansion enclosure(s). Wait for the enclosure status LED to light blue.
b
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 the
MD Storage Manager.
•If the status LEDs light a solid blue, the MD3000i is ready.
c
After the MD3000i is online and ready, turn on any attached host systems.
7
After the MD1000 is configured as the expansion enclosure to the MD3000i, restore the data that was
backed up in step 1.
After they are online, the MD1000 enclosures are available for use within the MD3000i system.
Expanding with New MD1000 Enclosures
Perform the following steps to attach new MD1000 expansion enclosures to the MD3000i:
1
Before adding the MD1000 enclosure(s), make sure the MD3000i software is installed and up to date.
For more information, refer to the
support.dell.com
a
Install or update (to the latest version available on
.
each host server.
b
Install or update (to the latest version available on
each host server.
c
Using the MD Storage Manager, update the MD3000i RAID controller firmware
(
Support→Download Firmware→
NVSRAM (
2
Stop I/O and turn off all systems:
a
Stop all I/O to the array and turn off affected host systems attached to the MD3000i.
b
Turn off the MD3000i.
c
Turn off any MD1000 enclosures in the affected system.
3
Referencing the applicable configuration for your rack (Figure 2-1 through Figure 2-5), cable the
Support→
MD1000 enclosure(s) to the MD3000i.
Dell™ PowerVault™ MD3000i Support Matrix
support.dell.com
support.dell.com
Download RAID Controller Module Firmware
Download Firmware→
Download RAID Controller Module NVSRAM
available on
) the MD Storage Manager on
) the multipath drivers on
) and the
).
Hardware Installation17
4
Turn on attached units:
a
Turn on the MD1000 expansion enclosure(s). Wait for the enclosure status LED to light blue.
b
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 the
MD Storage Manager.
•If the status LEDs light a solid blue, the MD3000i is ready.
c
After the MD3000i is online and ready, turn on any attached host systems.
5
Using the MD Storage Manager, update all attached MD1000 firmware if it is out of date:
a
Select
b
Check the
Support→
Download Firmware→
Select All
check box so that all attached MD1000 enclosures are updated at the same
Download Environmental (EMM) Card Firmware
time (each takes approximately 8 minutes to update).
.
18Hardware Installation
Software Installation
The MD3000i Resource CD contains all documentation pertinent to MD3000i hardware and
MD Storage Manager software. It also includes software and drivers for both Linux and
Microsoft
The MD3000i Resource CD contains a readme.txt file covering changes to the software, updates,
fixes, patches, and other important data applicable to both Linux and Windows operating systems.
The readme.txt file also specifies requirements for accessing documentation, information regarding
versions of the software on the CD, and system requirements for running the software.
For more information on supported hardware and software for Dell™ PowerVault™ systems, refer to
the Dell™ PowerVault™ MD3000i Support Matrix located at support.dell.com.
Dell recommends installing all the latest updates available at support.dell.com.
System Assembly and Startup
Use the following procedure to assemble and start your system for the first time:
1
2
3
4
5
®
Windows® operating systems.
Install the NIC(s) in each host server that you attach to the MD3000i Storage Array, unless the
NIC was factory installed. For general information on setting up your IP addresses, see
for Configuring Your Network for iSCSI
Cable the storage array to the host server(s), either directly or via a switch.
Cable the Ethernet management ports on the storage array to either the management network
(iSCSI-attached host server) or dedicated management station (non-iSCSI).
Power on the storage array and wait for the status LED to turn blue.
Start up each host server that is cabled to the storage array.
.
Guidelines
Install the iSCSI Initiator Software (iSCSI-attached Host
Servers Only)
To configure iSCSI later in this document (see "Array Setup and iSCSI Configuration"), you must
install the Microsoft iSCSI initiator on any host server that will access your storage array before you
install the MD Storage Manager software.
NOTE: Windows Server® 2008 contains a built-in iSCSI initiator. If your system is running Windows
Server 2008, you do not need to install the iSCSI initiator as shown in this section. Skip directly to "Installing
MD Storage Software."
Software Installation19
Depending on whether you are using a Windows Server 2003 operating system or a Linux operating
system, refer to the following steps for downloading and installing the iSCSI initiator.
Installing the iSCSI Initiator on a Windows Host Server
1
Refer to the
Dell™ PowerVault™ MD3000i Support Matrix
on
support.dell.com
for the latest version
and download location of the Microsoft iSCSI Software Initiator software.
2
From the host server, download the iSCSI Initiator software.
3
Once the installation begins and the
Initiator Service
4
DO NOT select
NOTICE: Make sure the Microsoft MPIO Multitpathing Support for iSCSI option is NOT selected. Using this option
will cause the iSCSI initiator setup to function improperly.
5
Accept the license agreement and finish the install.
NOTE: If you are prompted to do so, reboot your system.
and
Software Initiator
Microsoft MPIO Multitpathing Support for iSCSI
Microsoft iSCSI Initiator Installation
.
.
setup panel appears, select
Installing the iSCSI Initiator on a Linux Host Server
Follow the steps in this section to install the iSCSI initiator on a Linux server.
NOTE: All appropriate Linux iSCSI initiator patches are installed using the MD3000i Resource CD during MD
Storage Manager Software installation.
Installing the iSCSI Initiator on a RHEL 4 System
You can install the iSCSI initiator software on Red Hat® Enterprise Linux® 4 systems either during or
after operating system installation.
To install the iSCSI initiator during RHEL 4 installation:
1
When the
to be installed
2
In the
Package Installation Defaults
Servers
option. Click
list, select the
Next
Network Servers
screen is displayed, select the
to go to the
Server applications.
3
Select the
4
Click OK, then
To install the iSCSI initiator after RHEL 4 installation:
1
From the desktop, click
Group Selection
2
In the
iscsi-initiator-utils - iSCSI daemon and utility programs
Next
to continue with the installation.
Applications→ System Settings→ Add Remove Applications
screen is displayed.
Servers
list, select the
Network Servers
Server applications.
20Software Installation
Package Group Selection
package and click
package and click
Details
Details
Customize the set of Packages
screen.
to display a list of Network
option.
. The
Package
to display a list of Network
3
Select the
4
Click
Installing the iSCSI Initiator on a RHEL 5 System
iscsi-initiator-utils - iSCSI daemon and utility programs
Close
, then
Update
.
NOTE: Depending upon your installation method, the system will ask for the required source to install the
package.
option.
You can install the iSCSI initiator software on Red Hat Enterprise Linux 5 systems either during or after
operating system installation. With this version of the Linux software, you can also elect to install the
iSCSI initiator after the operating system installation via the command line.
To install the iSCSI initiator during RHEL 5 installation:
1
When the
2
Click
3
Select
4
Click
5
Select the
6
Click OK, then
To install the iSCSI initiator after RHEL 5 installation:
1
From the desktop, select
Package Installation Defaults
Next
to go to the
Base System
Optional Packages
iscsi-initiator-utils
Next
Package Group Selection
, then select the
.
option.
to continue with the installation.
Applications→ Add/Remove Software
screen is displayed, select the
screen.
Base
option.
Customize now
. The
Package Manager
option.
screen is
displayed.
2
In the
Package Manager
3
Search for
4
When it is displayed, select the
5
Click
iscsi-initiator-utils
Apply
.
screen, select the
iscsi-initiator-utils
Search
.
tab.
option.
NOTE: Depending upon your installation method, the system will ask for the required source to install the
package.
NOTE: This method might not work if network access is not available to a Red Hat Network repository.
To install the iSCSI initiator after RHEL 5 installation via the command line:
Insert the RHEL 5 installation CD 1 or DVD. If your media is not automounted, you must manual
1
mount it. The
2
Run the following command:
iscsi-initiatorutils.rpm
file is located in the Server or Client subdirectory.